Patent Description:
<CIT> discloses a system for pairing a wireless ultrasound probe and an ultrasound scanner. <CIT> discloses an ultrasonic probe. <CIT> discloses a sensor.

To ensure proper operation of a given ultrasound probe, probe specific information issued by a manufacturer can be referenced by an operator during use. However, this information can be lost or separated from its corresponding ultrasonic probe, potentially incurring delays during its retrieval from a manufacturer.

The present invention is defined in the independent claims <NUM> and <NUM>. Optional embodiments are defined in the dependent claims. In general, systems and methods are provided for communication with testing systems, such as ultrasound probes.

In one example a testing system is provided and can include a sensor and a radiofrequency (RF) tag mounted on the sensor. The RF tag can be configured to store sensor information and to wirelessly transmit at least a portion of the sensor information in response to receipt of a request for sensor information.

The RF tag can have a variety of configurations. In one example, the RF tag can be configured to receive sensor information from the sensor for storage. Sensor information received from the sensor can include an operating time of the sensor. In another example, the RF tag can be configured to receive sensor information for storage from a data source external to the testing system. Sensor information received from a data source external to the testing system can include, for example, a unique identifier of the sensor, a sensor certificate, a sensor datasheet, a calibration due date for the sensor, and/or test orders for the sensor.

In another example, the transmitted sensor information can be a link to a network resource storing at least one of a unique identifier of the sensor, a sensor certificate, a sensor datasheet, a calibration due date for the sensor, test orders for the sensor, and/or an operating time of the sensor.

In other aspects, an ultrasound testing system is provided and can include an ultrasound probe and a radiofrequency (RF) tag. The RF tag can be configured to store probe information regarding the ultrasound probe and to wirelessly transmit at least a portion of the probe information in response to receipt of a near-field communication from an authorized source.

The RF tag can have a variety of configurations. In one example, the RF tag can be configured for passive operation. In another example, the RF tag can be mounted to a housing of the ultrasound probe. In another example, the RF tag can be configured for read-only storage of at least a portion of the probe information.

In another example, the RF tag can be configured to receive probe information from the ultrasonic probe for storage. The probe information received from the ultrasonic probe can include, for example, an operating time of the ultrasound probe.

In another example, the authorized near-field communication can be received from a portable computing device. The probe information can include at least one of a unique identifier of the ultrasound probe, an ultrasound probe certificate, an ultrasound probe datasheet, a calibration due date for the ultrasound probe, and/or test orders for the ultrasound probe.

Methods for communicating with an ultrasound testing system are also provided. In one example, a method can include causing a portable computing device to transmit a first near-field communication to a radiofrequency (RF) tag that can store probe information regarding an ultrasound probe, where the first near-field communication can request at least a portion of probe information stored by the RF tag and where the portable computing device receives a second near-field communication that can include at least a portion of the requested probe information.

In another example, the probe information can include at least one of a unique identifier of the sensor, a sensor certificate, a sensor datasheet, a calibration due date for the sensor, test orders for the sensor, and/or an operating time of the sensor.

In another example, the probe information can include an operating time of the ultrasound probe.

In another example, the requested probe information can include a link to a network resource storing at least one of a unique identifier of the sensor, an ultrasound probe certificate, an ultrasound probe datasheet, a calibration due date for the ultrasound probe, test orders for the ultrasound probe, and/or an operating time of the ultrasound probe.

In other aspects, the method can include causing the portable computing device to transmit a third communication to the network resource requesting the probe information corresponding to the link. The portable computing device can receive a fourth communication that includes the probe information corresponding to the link.

In another example, the RF tag can be mounted to the ultrasonic probe.

Certain exemplary embodiments will now be described to provide an overall understanding of the principles of the structure, function, manufacture, and use of the systems, devices, and methods disclosed herein. One or more examples of these embodiments are illustrated in the accompanying drawings. Those skilled in the art will understand that the systems, devices, and methods specifically described herein and illustrated in the accompanying drawings are non-limiting exemplary embodiments and that the scope of the present invention is defined solely by the claims. The features illustrated or described in connection with one exemplary embodiment may be combined with the features of other embodiments. Such modifications and variations are intended to be included within the scope of the present invention.

Manufacturers of testing systems, such as ultrasound probes, can provide customers with a variety of information for use during operation and maintenance of their testing system. This information can detail capabilities of the testing system and maintenance schedules, among others, and can be specific to a given testing system. However, this information is commonly issued in paper form and can be easily lost after purchase of the sensor. In some instances, when information for a testing system is lost, use of the testing system can be delayed while an owner or operator of the testing system identifies the specific testing system and contacts the manufacturer to obtain duplicate copies of the information. Accordingly, a testing system is provided that enables sensor information to be electronically stored and wirelessly communicated to a user upon request. Other embodiments are within the scope of the disclosed subject matter.

Embodiments of testing systems are discussed herein with reference to ultrasonic probes. However, embodiments of the disclosure can be employed with any testing system without limit, such as X-ray, computed tomography (CT), magnetic resonance imaging (MRI), eddy current, and nuclear inspection systems.

<FIG> illustrates one exemplary embodiment of an operating environment <NUM> that includes a testing system <NUM> configured to communicate with a portable computing device <NUM>. As discussed in detail below, the testing system <NUM> can include a sensor <NUM> and a radiofrequency (RF) tag <NUM>. The RF tag <NUM> can be configured to store sensor information regarding the sensor <NUM> and to wirelessly communicate at least a portion of the sensor information to the portable computing device <NUM> upon request. The portable computing device <NUM> can be configured to allow an operator to obtain selected sensor information from the RF tag <NUM> and display it on the portable computing device <NUM>. The portable computing device <NUM> can also be configured to retrieve additional sensor information from external sources <NUM>, such as a sensor manufacturer, via a network <NUM>. Thus, sensor information can be retrieved in the field by the portable computing device <NUM> for use in operating the testing system <NUM>.

<FIG> illustrates one exemplary embodiment of a testing system in the form of a sensor <NUM> that can be used in the operating environment <NUM> of <FIG>. As shown, the sensor <NUM> includes a housing <NUM> defining a cavity <NUM> having one or more sensing elements <NUM> disposed therein, and a sensor interface <NUM> mounted within or disposed on the housing <NUM>. The sensor <NUM> also includes the RF tag <NUM> disposed thereon for communicating with the portable computing device <NUM>. As shown in <FIG>, the RF tag <NUM> can be secured to an outer surface of the housing <NUM>. However, alternative embodiments of the testing system (not shown) can position the RF tag at other locations for enabling sensor information to be stored and communicated to an operator. In one aspect, at least a portion of the RF tag can be positioned within the sensor cavity. In another aspect, the RF tag can be mounted on various devices (e.g., other than the housing) located proximate to or distanced from the sensor.

The housing <NUM> can have any shape and can be formed from any material suitable for housing the sensing element(s) <NUM>. The sensor <NUM> can be an ultrasonic sensor and the sensing element(s) <NUM> can be one or more of ultrasonic transmitters, ultrasonic receivers, ultrasonic transducers, and combinations thereof.

The sensor interface <NUM>, schematically shown in <FIG>, can be operatively coupled to the sensing element(s) <NUM> and can include one or more input devices <NUM>, a display <NUM>, and a counter <NUM>. The input devices <NUM> can be actuatable objects (e.g., knobs, buttons, switches, etc.) that allow an operator of the sensor <NUM> to activate and/or adjust various operating parameters for the sensing elements <NUM>, the display <NUM>, and/or the counter <NUM> during use. The display <NUM> can receive and display, in real-time, sensor measurements (e.g., acoustic signals) acquired by the sensing element(s) <NUM> from a test structure. The counter <NUM> can measure use of the sensor <NUM> (e.g., hours of operation).

The sensor <NUM> can also include one or more memory devices (not shown) for storing measurements acquired by the sensor <NUM> (e.g., by the sensing elements <NUM> and/or the counter <NUM>). As discussed in greater detail below, the sensor interface <NUM> can also be configured to communicate with the RF tag <NUM> for storing sensor information.

<FIG> is a top down view of one exemplary embodiment of the RF tag <NUM> in greater detail, including a substrate <NUM>, an antenna <NUM>, and a microchip <NUM>. As shown, the substrate <NUM> can be formed as a generally planar shape that receives the antenna <NUM> and the microchip <NUM> on one surface. An opposing surface of the substrate <NUM> can include an attachment mechanism (e.g., an adhesive, a portion of a hook and loop fastener, etc.) capable of securing the RF tag <NUM> to a surface of the housing <NUM>. The substrate <NUM> can be formed from a material capable of withstanding selected service conditions (e.g., temperature, stress, chemical compatibility, etc.). Examples of substrate materials can include, but are not limited to, polymers and papers.

The antenna <NUM> can include loops or coils of conductive metal wire in electrical communication with the microchip <NUM>, and it can be configured for receipt and transmission RF waves. As an example, the antenna <NUM> can be configured to receive and transmit RF waves having frequencies ranging between about <NUM> to about <NUM>. In certain embodiments, the antenna <NUM> can be configured to receive and transmit RF waves at frequencies less than about <NUM>, which can allow penetration through most objects to facilitate communication with devices lacking line of sight with the RF tag <NUM>. These frequency ranges are merely exemplary, and other frequencies can be used e.g., about <NUM> to about <NUM> THz.

The microchip <NUM> can be an integrated circuit including a processor and a non-volatile memory (not shown) configured to store sensor information. The microchip memory can be a read only memory device, a read-write memory device, and combinations thereof. RF waves received by the antenna <NUM> can contain commands for storage of sensor information by the microchip memory or transmission of sensor information stored by the microchip memory. Accordingly, the microchip processor can also be configured to process these commands.

In certain embodiments, the microchip <NUM> can be configured to only process commands received from an authorized source. As an example, the microchip <NUM> can employ one or more authentication protocols to verify whether a given communication received by the RF tag <NUM> is from an authorized source.

Embodiments of the RF tag <NUM> can be configured to operate passively. In this configuration, the RF tag <NUM> can transmit sensor information only in response to requests from authorized sources. As an example, electrical currents can be induced within the antenna <NUM> upon receipt of RF waves. At least a portion of this current can be employed to power operation of the microchip <NUM> and transmission of RF waves by the antenna <NUM>. Accordingly, embodiments of the RF tag <NUM> can omit an internal power source. However, alternative embodiments of the RF tag can be configured to operate actively and transmit sensor information or other information absent requests from authorized sources. Embodiments of the RF tag configured for active operation can also include a power source (not shown) electrically coupled to the microchip and the antenna, such as a battery.

Embodiments of the RF tag <NUM> can also transmit RF waves according to any of a variety of wireless communication protocols. Examples of wireless communication protocols can include, but are not limited to, radiofrequency identification (RFID), near field communication (NFC), Wi-Fi®, and Bluetooth®.

<FIG> is a front view illustrating an exemplary embodiment of a portable computing device in the form of a smartphone device <NUM> for use with the testing system <NUM> of <FIG>. The device <NUM> can include a processor (not shown), a display <NUM>, and a transceiver <NUM>. The processor can execute applications providing one or more selectable user interface objects <NUM> (e.g., 406A, 406B, 406C) for presentation by the display <NUM>. The transceiver <NUM> can be configured for communication with the RF tag <NUM> and other communication networks (e.g., the network <NUM>) according to any communication protocols supported by the RF tag <NUM> and the network <NUM>. As discussed in greater detail below, in certain embodiments, an operator can select any of the user interface objects <NUM> to command the RF tag <NUM> to transmit sensor information corresponding to the selected user interface objects <NUM> to the device <NUM>. An operator can also select any of the user interface objects <NUM> to command the RF tag <NUM> to receive and update sensor information provided by the device <NUM>. Sensor information received from the RF tag <NUM> can be further displayed to an operator on the display <NUM> and/or stored for later viewing on the display <NUM>. While the illustrated device <NUM> is a smartphone, embodiments of the portable computing device can also include tablet computers, laptops, personal digital assistants (PDAs), wearable computing devices (e.g., watches), and the like.

<FIG> is a diagram illustrating embodiments of sources for storing sensor information and communicating with the RF tag <NUM>. As shown, sensor information can be transmitted to the RF tag <NUM> from a variety of authorized sources for storage, such as the portable computing device <NUM>, the sensor <NUM>, and external sources <NUM>. In one embodiment, the external sources <NUM> can include, but are not limited to, any computing devices external to the testing system <NUM> (e.g., RF readers). These external sources <NUM> can be operated under the authority of a sensor manufacturer, a sensor owner, a sensor operator, and/or designates thereof (e.g., repair centers). External sources <NUM> can also include network resources accessible via the network <NUM>, such as websites and databases, that maintain sensor information.

Examples of sensor information can include one or more of the following, in any combination:.

The sensor information can be transmitted to the RF tag <NUM> for storage in a variety of forms. As an example, one or more of the sensor specific information can be stored in its entirety by the RF tag110. In another embodiment, one or more of the sensor specific information can be stored in a summarized form that occupies less memory storage than its entirety. As another example, one or more of the sensor information can be stored as a link (e.g., a hyperlink). The link can specify a network resource (e.g., a website, a database, etc.) from which the portable computing device <NUM> can retrieve the corresponding sensor information in its entirety and/or in summarized form. The network resource can be any of the external sources <NUM> discussed herein. This link can occupy less memory storage than either the entirety of the sensor information or the sensor information in summarized form. As another example, each of the sensor information can be stored as any combination of the above.

In certain embodiments, one or more of the sensor information can be provided to the RF tag <NUM> for storage prior to sale or use of the sensor <NUM> in the field. As an example, manufacturers can store unique identifiers, certificates, datasheets, and sensor setups on the RF tag <NUM> prior to sale of the sensor <NUM>. As another example, owners or operators can store test orders and calibration due dates on the RF tag <NUM> prior to use of the sensor <NUM> in the field. As another example, an owner or operator of the sensor can employ the sensor interface <NUM> to store an operating time of the sensor <NUM> on the RF tag <NUM> during and/or after use of the sensor <NUM> in the field. As another example, sensor operators can employ the portable computing device <NUM> to update a sensor information stored by the RF tag before, during, or after use of the sensor <NUM> in the field.

<FIG> is a diagram illustrating one exemplary embodiment of a method <NUM> for communicating with the testing system <NUM> (e.g., the RF tag <NUM>) for retrieval and storage of sensor information. In certain embodiments, the testing system <NUM> can include an ultrasonic probe as the sensor <NUM>. However, the method is exemplary only and not limiting. The method can be altered, e.g., by having operations added, removed, or rearranged.

As shown in <FIG>, the method <NUM> can include operations <NUM>-<NUM>. In operation <NUM>, the portable computing device <NUM> can receive a selection regarding sensor information to be retrieved from the RF tag <NUM>. The portable computing device <NUM> can display a selectable list of sensor information options (e.g., user interface objects <NUM>). Example options can include, but are not limited to, any of the sensor information discussed herein, alone or in combination with a form of the sensor information (e.g., a sensor information in its entirety, a sensor information summary, a sensor information link). The options can be based upon a default list or prior communication(s) with the RF tag <NUM> that establish its stored sensor information. Upon receipt of the selection by an operator of the testing system <NUM>, the method <NUM> moves to operation <NUM>. In an alternative embodiment, not shown, the portable computing device can select a default list of sensor information without operator input (e.g., all sensor information stored by the RF tag).

In certain embodiments, the RF tag <NUM> can store more than one document for a given type of sensor information. As an example, sensor setup information can be stored by the RF tag <NUM> in multiple documents, each of which can be suitable for use under different testing conditions (e.g., materials, testing environments, etc.). Under this circumstance, the portable computing device <NUM> can provide a selectable list of sensor information options (e.g., user interface objects <NUM>) for each of the multiple documents stored by the RF tag <NUM>.

In operation <NUM>, the portable computing device <NUM> can transmit a first communication to the RF tag <NUM> requesting at least a portion of the sensor information stored by the RF tag <NUM>. In an embodiment, the first communication can be a near field communication requesting sensor information corresponding to the option(s) selected by an operator in operation <NUM>.

In operation <NUM>, the portable computing device <NUM> can receive a second communication from the RF tag <NUM> in response to the first communication. The second communication can be a near field communication including one or more of the requested sensor information. As an example, the RF tag <NUM> can conduct a search of its memory and return any stored sensor information corresponding to the requested sensor information in the second communication.

In operation <NUM>, any of the requested sensor information contained within the second communication can be displayed and/or optionally stored by the portable computing device <NUM>.

In an embodiment, the second communication can include one or more of the sensor information in the form of a link. As discussed above, the link can be a hyperlink specifying a network resource (e.g., a website and/or database of external sources <NUM>) and path storing one or more of the sensor information.

In operation <NUM>, the portable computing device <NUM> can transmit a third communication to the network resource, via the network <NUM>, requesting the sensor information corresponding to the link. As an example, an operator can select the link received in the second communication using the portable computing device <NUM>. In another embodiment, the portable computing device <NUM> can detect the link within the second communication and automatically transmit the third communication to the network resource without operator intervention.

In operation <NUM>, the portable computing device <NUM> can receive a fourth communication containing the sensor information requested in operation <NUM> from the network resource via the network <NUM>.

In operation <NUM>, any of the requested sensor information contained within the response from the network resource can be displayed and/or optionally stored, by the portable computing device <NUM>. In an embodiment, if none of the requested sensor information is stored by the RF tag <NUM>, the method can subsequently return to operation <NUM>, allowing an operator to select sensor information to be retrieved from the RF tag <NUM>. By default, if none of requested sensor information is stored by the RF tag <NUM>, the second communication can include a link (e.g., a hyperlink) containing a unique identifier of the sensor <NUM>. An operator can subsequently select the link using the portable computing device <NUM>, to retrieve any sensor information associated with the sensor <NUM> from the network resource, as discussed above.

<FIG> is a diagram illustrating another exemplary embodiment of a method <NUM> for updating sensor information, including operations <NUM>-<NUM>. In an embodiment, the updated sensor information can be an updated certificate for the sensor <NUM>. As an example, a given sensor <NUM> can be sold by a manufacturer in different versions, where each sensor version can have a different set of certifications and where a sensor of one version can be upgraded to another version by purchase of additional certificates. Accordingly, as discussed below, the method <NUM> can be employed to update the sensor certificate stored by the RF tag <NUM> with one or more new certificates.

In operation <NUM>, the portable computing device <NUM> can send a request for updated sensor information to the network resource. As an example, transmission of the request can be performed in response to operator selections input using of the portable computing device <NUM>. The request can include a unique identifier for the sensor <NUM>, received by the portable computing device <NUM> prior to the transmission in operation <NUM>. In certain embodiments, the portable computing device <NUM> can receive the unique identifier from the RF tag <NUM> according to the method <NUM>, as discussed above.

In operation <NUM>, a response to the request for updated sensor information can be received by the portable computing device <NUM> from the network resource. As an example, the response can contain one or more updated sensor information corresponding to the requested updated sensor information.

In operation <NUM>, following receipt of the response, the portable computing device <NUM> can transmit the received updated sensor information to the RF tag <NUM> for storage.

Exemplary technical effects of the methods, systems, and devices described herein include, by way of non-limiting example, near field communication suitable for retrieval and storage of sensor information from testing devices including sensors such as ultrasonic probes.

The subject matter described herein can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structural means disclosed in this specification and structural equivalents thereof, or in combinations of them. The subject matter described herein can be implemented as one or more computer program products, such as one or more computer programs tangibly embodied in an information carrier (e.g., in a machine readable storage device), or embodied in a propagated signal, for execution by, or to control the operation of data processing system (e.g., a programmable processor, a computer, or multiple computers). A program can be stored in a portion of a file that holds other programs or data, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code).

The processes and logic flows can also be performed by, and system of the subject matter described herein can be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, (e.g., EPROM, EEPROM, and flash memory devices); magnetic disks, (e.g., internal hard disks or removable disks); magneto optical disks; and optical disks (e.g., CD and DVD disks).

The subject matter described herein can be implemented in a computing system that includes a back end component (e.g., a data server), a middleware component (e.g., an application server), or a front end component (e.g., a client computer having a graphical user interface or a web browser through which a user can interact with an implementation of the subject matter described herein), or any combination of such back end, middleware, and front end components.

Accordingly, a value modified by a term or terms, such as "about" and "substantially," are not to be limited to the precise value specified.

Claim 1:
An ultrasound testing system (<NUM>), comprising:
an ultrasound probe (<NUM>);
a radiofrequency (RF) tag (<NUM>); and
an authorized source (<NUM>) configured to send authenticated commands to the RF tag (<NUM>);
wherein the RF tag (<NUM>) is characterized by being configured to:
store a unique identifier of the ultrasound probe and probe information regarding the ultrasound probe including an ultrasound probe certificate comprising permissions for the use of the ultrasound probe (<NUM>);
wirelessly transmit the unique identifier and at least a portion of the probe information in response to receipt of a near-field communication from the authorized source (<NUM>) for one or more new certificates to update the ultrasound probe certificate; and
receive from the authorized source (<NUM>) a link to a network resource storing the one or more certificates.