Abstract: A fluorescence immunochromatographic detection card and a preparation method therefor and usage thereof is disclosed. The fluorescence immunochromatographic detection card comprises a treatment liquid A, a treatment liquid B, and a detection card. The treatment liquid A contains an antibody 15C4 that is coupled with a fluorescent microsphere. The treatment liquid B contains an antibody 13G12 that is coupled with biotin. The detection card comprises a detection line area and a quality control line area, and a streptavidin detection T line is fixed in the detection area, and an antibody quality control C line is immobilized in the quality control line area. The preparation method comprises: (1) formulating the treatment liquid A; (2) formulating the treatment liquid B; and (3) drawing the line on the detection card.

Abstract: Computer servers configured to perform digital image processing are discloses herein. In one embodiment, upon receiving a transcription command, a computer server performs text recognition based on patterns in a digital image to generate digital text data corresponding to the digital image. The computer server can then determine a content format of the digital text data based on the imported digital image and automatically apply the determined content format to the generated digital text data. The digital data can then be inserted into an electronic document.

Abstract: In various embodiments, RFID events are stored in a normalized format on mobile device configured by metadata pushed by a centralized data hub. RFID events are pre-processes with filtering logic by a mobile interrogator/reader before being inserted into tables of a local relational database on the mobile device when the mobile device cannot otherwise communicate collected events to the centralized data hub. The metadata provides a simple, efficient, and standard interface for persisting the RFID events such that local access from applications on the mobile device is provided.

Abstract: Communication from applications may be carried in XML-based events through sockets, Web services, JMS, HTTP, telnet channels, and the like to an OPC client. The OPC client may include an event engine configured to process the XML-based events, and convert them to appropriate COM/DCOM API invocations. In some embodiments, the OPC client buffers collected data from the COM/DCOM API, and transmits the buffered data in an XML event to an application based on a subscription time schedule and/or value condition. The OPC client allows service oriented event-driven applications to interact with industry devices remotely via the open architecture provided by the OPC specification using a business level language syntax.

Abstract: In various embodiments, RFID events are stored in a normalized format on mobile device configured by metadata pushed by a centralized data hub. RFID events are pre-processes with filtering logic by a mobile interrogator/reader before being inserted into tables of a local relational database on the mobile device when the mobile device cannot otherwise communicate collected events to the centralized data hub. The metadata provides a simple, efficient, and standard interface for persisting the RFID events such that local access from applications on the mobile device is provided.

Abstract: In various embodiments, RFID events are pre-processes with filtering logic by a mobile interrogator/reader before being inserted into tables of a local relational database on the mobile device when the mobile device cannot otherwise communicate collected events to a centralized data hub. The RFID events are stored in a normalized format that provides a simple, efficient, and standard interface for persisting the RFID events such that local access from applications on the mobile device is provided.

Abstract: Communication from applications may be carried in XML-based events through sockets, Web services, JMS, HTTP, telnet channels, and the like to an OPC client. The OPC client may include an event engine configured to process the XML-based events, and convert them to appropriate COM/DCOM API invocations. In some embodiments, the OPC client buffers collected data from the COM/DCOM API, and transmits the buffered data in an XML event to an application based on a subscription time schedule and/or value condition. The OPC client allows service oriented event-driven applications to interact with industry devices remotely via the open architecture provided by the OPC specification using a business level language syntax.

Abstract: In various embodiments, RFID events are pre-processes with filtering logic by a mobile interrogator/reader before being inserted into tables of a local relational database on the mobile device when the mobile device cannot otherwise communicate collected events to a centralized data hub. The RFID events are stored in a normalized format that provides a simple, efficient, and standard interface for persisting the RFID events such that local access from applications on the mobile device is provided.