Patent Application
20130253308
1. Field of the Disclosure
The present disclosure relates to improved techniques, systems and machine readable programs for magnetic resonance imaging.
2. Description of Related Art
Traditionally NMR/MRI/MRS studies have always incorporated pulses of radiofrequency (rf) radiation. The role of the rf pulses is to excite the system under investigation into a temporary state of non equilibrium magnetization. As the system relaxes back to equilibrium it emits radiation which can then be used to form images and/or extract information of scientific or diagnostic value such as physical state of the system, quantity of a given molecule, diffusion coefficients, spectroscopic identification, etc. A variety of rf pulse sequences designed to extract information of one kind or another in this manner are well described in the literature. However, there are limits as to the amount of rf energy a patient under examination can be exposed to, commonly referred to as specific absorption ratio or “SAR” limits. There is also a continuing need in the MRI art for advances that can increase the speed of imaging, require less data storage and improve image quality. The present disclosure provides solutions for these problems.
Advantages of the present disclosure will be set forth in and become apparent from the description that follows. Additional advantages of the disclosure will be realized and attained by the methods and systems particularly pointed out in the written description and claims hereof, as well as from the appended drawings.
To achieve these and other advantages and in accordance with the purpose of the disclosure, as embodied herein, in one embodiment, the disclosure provides a method of performing a magnetic resonance protocol. The method includes providing a magnetic resonance device including (i) a main magnet for providing a background magnetic field along a first direction, (ii) at least one radio-frequency coil, and (iii) at least one gradient coil that can be controlled to define at least one region of interest. The method further includes defining a region of interest, introducing a sample to be studied into the region of interest and inducing electromagnetic feedback between the nuclear magnetization of at least one set of nuclei within the sample and at least one nearby resonant coil to cause the vector direction of the nuclear magnetization of the at least one set of nuclei to rotate to a desired angle with respect to the first direction of the background magnetic field to generate at least one electromagnetic pulse of transverse magnetization MXY. The method further includes detecting the pulse of transverse magnetization with the at least one radio-frequency coil.
In some implementations, the method can further include processing information obtained from a plurality of pulses of transverse magnetization to produce at least one of (i) an image, (ii) dynamic flow data, (iii) perfusion data, (iii) spectroscopic identity of chemical species, (iv) physiological data, or (v) metabolic data. In some embodiments, the electromagnetic feedback can be induced at least in part by substantially eliminating the presence of a gradient magnetic field in the at least one region of interest. The region of interest can include, for example, at least one voxel, and the at least one gradient coil can be adapted and configured to apply a magnetic field gradient in at least one of three mutually orthogonal directions. The electromagnetic feedback can be induced at least in part by selectively tuning the resonant coil to a predetermined resonant frequency.
In further implementations, the method can further include applying a RF pulse to the sample in order to at least partially invert the nuclear magnetization of the at least one set of nuclei prior to the inducing step. In some embodiments, the magnetization vector of the at least one set of nuclei can be directed substantially entirely anti-parallel to the first direction of the background magnetic field. The background magnetic field can be, for example, about 1.0 Tesla, about 1.5 Tesla, about 2.0 Tesla, about 2.5 Tesla, about 3.0 Tesla, about 4.0 Tesla, about 5.0 Tesla, about 6.0 Tesla, about 7.0 Tesla, about 8.0 Tesla, about 9.0 Tesla, about 10.0 Tesla or greater or less, in any desired increment of 0.1 Tesla. The vector direction of the nuclear magnetization of the at least one set of nuclei can be permitted to fully align with the first direction of the background magnetic field when the pulse is generated. If desired, the vector direction of the nuclear magnetization of the at least one set of nuclei can be permitted to partially align with the first direction of the background magnetic field when the pulse is generated. If desired, the method can further include generating a plurality of pulses of transverse magnetization from the at least one set of nuclei by permitting the vector direction of the nuclear magnetization of the at least one set of nuclei to progressively and discretely approach full alignment with the first direction of the background magnetic field with each succeeding pulse of transverse magnetization.
In some implementations, the inducing step can include inducing electromagnetic feedback between the nuclear magnetization of a plurality of sets of nuclei in at least two discrete, separated physical locations within the object and at least one nearby resonant coil to cause the vector direction of the nuclear magnetizations of each set of nuclei to rotate to a desired angle with respect to the first direction of the background magnetic field to generate the at least one electromagnetic pulse of transverse magnetization.
In some implementations, at least one of the at least one radio frequency coil and the at least one gradient coil is a local coil. Moreover, at least one of the at least one radio frequency coil and the at least one gradient coil can be integrated into the magnetic resonance system. If desired, the at least one radio frequency coil can be a whole body coil, and can be used at background fields in excess of 3.0 Tesla. If desired, the at least one radio frequency coil can be a whole body phased array transmit/receive coil system having a plurality of coils that can selectively transmit and receive rf pulses of transverse magnetization. Moreover, the at least one radio frequency coil can be a local phased array transmit/receive coil system having a plurality of coils that can selectively transmit and receive rf pulses of transverse magnetization. If desired, the at least one radio frequency coil can further include a plurality of local gradient coils for locally controlling the gradient magnetic field. If desired, the at least one gradient field coil can include a plurality of gradient field coils integrated into the magnetic resonance system, even if local gradient field coils are provided.
In some implementations, the method can further include providing an agent wherein one or more nuclei have been hyperpolarized. The method can still further include inverting the vector direction of the polarization of the hyperpolarized nuclei to be at least partially anti-parallel to the direction of the magnetic field of the magnetic resonance device. The method can further include introducing the agent into the region of interest, inducing electromagnetic feedback between the nuclear magnetization of the hyperpolarized nuclei and the at least one nearby resonant coil to cause the vector direction of the nuclear magnetization to rotate to a desired angle with respect to the first direction of the background magnetic field to generate at least one electromagnetic pulse of transverse magnetization, and detecting the pulse of transverse magnetization with the at least one radio-frequency coil.
In further implementations, a method for inverting the vector direction of at least one set of nuclei contained in a sample is provided. The method includes providing a controller, providing a power source operably coupled and controlled by the controller, providing an electromagnet in operable communication with the power source and controller, disposing a sample having nuclei to be inverted into a sample chamber in electromagnetic communication with the electromagnet, operating the controller to actuate the power source to induce an electromagnetic pulse in the electromagnet to orient the vector direction of nuclei of a sample situated in the sample chamber, and operating an injector assembly to direct the sample into a magnetic resonance system. The sample can be directed into a patient disposed in the magnetic resonance system. The method can further include conducting a MR study while the hyperpolarized material is disposed in the patient to produce at least one of (i) an image, (ii) dynamic flow data, (iii) perfusion data, (iii) physiological data, and (v) metabolic data.
In accordance with further aspects, the disclosure provides systems for performing a magnetic resonance protocol. The system can include a magnetic resonance device including (i) a main magnet for providing a background magnetic field along a first direction, (ii) at least one radio-frequency coil, and (iii) at least one gradient coil that can be controlled to define at least one region of interest. The system can further include means for defining a region of interest, means for introducing a sample to be studied into the region of interest and means for inducing electromagnetic feedback between the nuclear magnetization of at least one set of nuclei within the sample and at least one nearby resonant coil to cause the vector direction of the nuclear magnetization of the at least one set of nuclei to rotate to a desired angle with respect to the first direction of the background magnetic field to generate at least one electromagnetic pulse of transverse magnetization MXY. The method can still further include means for detecting the pulse of transverse magnetization with the at least one radio-frequency coil.
In some implementations the system can further include means for processing information obtained from a plurality of pulses of transverse magnetization to produce at least one of (i) an image, (ii) dynamic flow data, (iii) perfusion data, (iii) spectroscopic identity of chemical species, (iv) physiological data, and (v) metabolic data. If desired, electromagnetic feedback can be induced at least in part by substantially eliminating the presence of a gradient magnetic field in the at least one region of interest by controlling the at least one gradient coil. The region of interest can include at least one voxel, and the at least one gradient coil is adapted and configured to apply a magnetic field gradient in at least one of three mutually orthogonal directions. Electromagnetic feedback can be induced at least in part by selectively tuning the at least one rf coil to a predetermined resonant frequency. The system can selectively and controllably apply a RF pulse to the sample in order to at least partially invert the nuclear magnetization of the at least one set of nuclei prior to the inducing step. In some embodiments, the system can be adapted to direct the magnetization vector of the at least one set of nuclei substantially entirely anti-parallel to the first direction of the background magnetic field. The background magnetic field can be, for example, about 1.0 Tesla, about 1.5 Tesla, about 2.0 Tesla, about 2.5 Tesla, about 3.0 Tesla, about 4.0 Tesla, about 5.0 Tesla, about 6.0 Tesla, about 7.0 Tesla, about 8.0 Tesla, about 9.0 Tesla, about 10.0 Tesla or greater or less, in any desired increment of 0.1 Tesla. The system can be adapted to permit the vector direction of the nuclear magnetization of the at least one set of nuclei to fully align with the first direction of the background magnetic field when the pulse is generated. In some embodiments, the system can be adapted to permit the vector direction of the nuclear magnetization of the at least one set of nuclei to partially align with the first direction of the background magnetic field when the pulse is generated. If desired, the system can be further adapted to selectively and controllably generate a plurality of pulses of transverse magnetization at different times from the at least one set of nuclei by permitting the vector direction of the nuclear magnetization of the at least one set of nuclei to progressively and discretely approach full alignment with the first direction of the background magnetic field with each succeeding pulse of transverse magnetization.
In some implementations, the system can be adapted to induce electromagnetic feedback between the nuclear magnetization of a plurality of sets of nuclei in at least two discrete, separated physical locations within the object and at least one nearby resonant coil to cause the vector direction of the nuclear magnetizations of each set of nuclei to rotate to a desired angle with respect to the first direction of the background magnetic field to generate the at least one electromagnetic pulse of transverse magnetization. In some embodiments, at least one of the at least one radio frequency coil and the at least one gradient coil can be a local coil. At least one of the at least one radio frequency coil and the at least one gradient coil can be integrated into the magnetic resonance system. The at least one radio frequency coil can be a whole body coil. The at least one radio frequency coil can be a whole body phased array transmit/receive coil system having a plurality of coils that can selectively transmit and receive rf pulses of transverse magnetization. The at least one radio frequency coil can be a local phased array transmit/receive coil system having a plurality of coils that can selectively transmit and receive rf pulses of transverse magnetization. At least one radio frequency coil can further include a plurality of local gradient coils for locally controlling the gradient magnetic field. The at least one gradient field coil can include a plurality of gradient field coils integrated into the magnetic resonance system, as well as one or more local gradient coils, if desired.
In some implementations, the system can further include a container containing an agent wherein one or more nuclei have been hyperpolarized, means for inverting the vector direction of the polarization of the hyperpolarized nuclei to be at least partially anti-parallel to the direction of the magnetic field of the magnetic resonance device, means for introducing the agent into the region of interest, means for inducing electromagnetic feedback between the nuclear magnetization of the hyperpolarized nuclei and the at least one nearby resonant coil to cause the vector direction of the nuclear magnetization to rotate to a desired angle with respect to the first direction of the background magnetic field to generate at least one electromagnetic pulse of transverse magnetization, and means for detecting the pulse of transverse magnetization with the at least one radio-frequency coil.
The disclosure provides a device for inverting the vector direction of at least one set of nuclei contained in a sample. The device includes a controller, a power source operably coupled and controlled by the controller, an electromagnet in operable communication with the power source and controller, a sample chamber in electromagnetic communication with the electromagnet, wherein the controller is adapted and configured to operate the power source to induce an electromagnetic pulse in the electromagnet to orient the vector direction of nuclei of a sample situated in the sample chamber, and an injector assembly to direct the sample into a magnetic resonance system. In some implementations, the device can be adapted to direct the agent into a patient disposed in the magnetic resonance system. The device can further include means for conducting a MR study while the hyperpolarized material is disposed in the patient to produce at least one of (i) an image, (ii) dynamic flow data, (iii) perfusion data, (iii) physiological data, and (v) metabolic data.
The disclosure further provides processor-readable computer programs stored on a tangible non-transient medium for operating a magnetic resonance protocol on a magnetic resonance device including, for example, (i) a main magnet for providing a background magnetic field along a first direction, (ii) at least one radio-frequency coil, and (iii) at least one gradient coil that can be controlled to define at least one region of interest. The program can include instructions to facilitate definition of a region of interest, instructions for inducing electromagnetic feedback between the nuclear magnetization of at least one set of nuclei within the sample and at least one nearby resonant coil to cause the vector direction of the nuclear magnetization of the at least one set of nuclei to rotate to a desired angle with respect to the first direction of the background magnetic field to generate at least one electromagnetic pulse of transverse magnetization MXY, and instructions to facilitate processing signals received arising from the pulse of transverse magnetization with the at least one radio-frequency coil.
The computer program can further include instructions for processing information obtained from a plurality of pulses of transverse magnetization to produce at least one of (i) an image, (ii) dynamic flow data, (iii) perfusion data, (iii) spectroscopic identity of chemical species, (iv) physiological data, and (v) metabolic data. The program can further include instructions to induce electromagnetic feedback by substantially eliminating the presence of a gradient magnetic field in the at least one region of interest by controlling the at least one gradient coil. The region of interest can include at least one voxel, and the program can include instructions to cause the at least one gradient coil to apply a magnetic field gradient in at least one of three mutually orthogonal directions. The program can include instructions to induce electromagnetic feedback at least in part by selectively tuning the at least one rf coil to a predetermined resonant frequency. The program can similarly include instructions to cause the system to selectively and controllably apply a RF pulse to the sample in order to at least partially invert the nuclear magnetization of the at least one set of nuclei prior to inducing the electromagnetic feedback.
In some implementations, the computer program can include instructions to cause the magnetic resonance system to direct the magnetization vector of the at least one set of nuclei substantially entirely anti-parallel to the first direction of the background magnetic field. Similarly, the computer program can include instructions to cause the magnetic resonance system to permit the vector direction of the nuclear magnetization of the at least one set of nuclei to fully align with the first direction of the background magnetic field when the pulse is generated. The computer program can include instructions to cause the magnetic resonance system to permit the vector direction of the nuclear magnetization of the at least one set of nuclei to partially align with the first direction of the background magnetic field when the pulse is generated.
In further implementations, the computer program can further include instructions to cause the magnetic resonance system to selectively and controllably generate a plurality of pulses of transverse magnetization at different times from the at least one set of nuclei by permitting the vector direction of the nuclear magnetization of the at least one set of nuclei to progressively and discretely approach full alignment with the first direction of the background magnetic field with each succeeding pulse of transverse magnetization. The computer program can similarly include instructions to cause the magnetic resonance system to induce electromagnetic feedback between the nuclear magnetization of a plurality of sets of nuclei in at least two discrete, separated physical locations within the object and at least one nearby resonant coil to cause the vector direction of the nuclear magnetizations of each set of nuclei to rotate to a desired angle with respect to the first direction of the background magnetic field to generate the at least one electromagnetic pulse of transverse magnetization.
In some implementations, the computer program can include instructions to cause the magnetic resonance system to operate at least one radio frequency coil and at least one gradient coil that is a local coil. The computer program can include instructions to cause the magnetic resonance system to operate at least one radio frequency coil and at least one gradient coil that is integrated into the magnetic resonance system. The computer program can include instructions to operate a radio frequency coil that is a whole body phased array transmit/receive coil system having a plurality of coils that can selectively transmit and receive rf pulses of transverse magnetization. If desired, the computer program can include instructions to operate a radio frequency coil that is a local phased array transmit/receive coil system having a plurality of coils that can selectively transmit and receive rf pulses of transverse magnetization. The computer program can similarly include instructions to operate at least one radio frequency coil that further includes a plurality of local gradient coils for locally controlling the gradient magnetic field.
In some implementations, the computer program can include instructions to control a system to invert the vector direction of the polarization of hyperpolarized nuclei to be at least partially anti-parallel to the direction of the magnetic field of the magnetic resonance device. The computer program can include instructions for introducing the hyperpolarized nuclei with inverted magnetization into a region of interest in a sample to be examined in a magnetic resonance study. In some embodiments, the computer program can further include instructions to cause the magnetic resonance system to induce electromagnetic feedback between the nuclear magnetization of the hyperpolarized nuclei and the at least one nearby resonant coil to cause the vector direction of the nuclear magnetization to rotate to a desired angle with respect to the first direction of the background magnetic field to generate at least one electromagnetic pulse of transverse magnetization, and means for processing signals arising from the pulse of transverse magnetization with the at least one radio-frequency coil.
The disclosure further provides processor-readable computer programs stored on a tangible non-transient medium for operating a device for inverting the vector direction of at least one set of nuclei contained in a sample including a controller, a power source operably coupled and controlled by the controller, an electromagnet in operable communication with the power source and controller, and a sample chamber in electromagnetic communication with the electromagnet. The program includes instructions to cause the controller to operate the power source to induce an electromagnetic pulse in the electromagnet to orient the vector direction of nuclei of a sample situated in the sample chamber. In some implementations, the device further includes an injector assembly to direct the sample into a magnetic resonance system, and the computer program further includes instructions to cause the injector assembly to direct the sample into the magnetic resonance system. If desired, the computer program can further include instructions to facilitate production of at least one of (i) an image, (ii) dynamic flow data, (iii) perfusion data, (iii) physiological data, and (v) metabolic data from data generated by processing the pulse.
It is to be understood that the foregoing general description and the following detailed description are exemplary and are intended to provide further explanation of the disclosed embodiments. The accompanying drawings, which are incorporated in and constitute part of this specification, are included to illustrate and provide a further understanding of the disclosed methods and systems. Together with the description, the drawings serve to explain principles of the disclosure.
Reference will now be made in detail to the present preferred embodiments of the disclosure, examples of which are illustrated in the accompanying drawings. The methods and corresponding steps of the disclosed embodiments will be described in conjunction with the detailed description of the system.
The applicant has developed techniques and related systems and computer programs that, under certain circumstances, allow MR studies to be carried out with a minimum of rf pulses or without requiring the subject to be exposed to rf pulses at all. This provides a number of significant advantages. Firstly, the exposure of the subject to rf radiation is minimized or removed altogether. This is especially important when the subject is a living creature such as is the case during an in vivo MRI/MRS procedure. Secondly, applicant's approach can improve overall signal to noise (SNR) levels. Thirdly, removing the requirement for rf pulses allows for the MR machine itself to be produced less expensively, particularly if a whole body rf coil is integrated into the device. Other follow on benefits from this novel approach will be described below.
It is one object of this disclosure to provide exemplary methods, systems and computer programs whereby certain MR studies—in particular, but not limited to, MRS studies incorporating hyperpolarized nuclei, may be carried out without subjecting the sample of the studies to any rf pulses. In accordance with a preferred embodiment, studies can be carried out on nuclei that have been hyperpolarized outside the MR magnet in which the NMR/MRI/MRS study normally takes place. Also in accordance with a preferred embodiment, the hyperpolarized nuclei can have had their magnetization vector inverted so that at least some portion of it is directed anti-parallel to the direction of the magnetic field of the MR magnet. In the most preferred embodiment, the magnetization vector is directed entirely anti-parallel to the direction of the magnetic field of the MR magnet.
It is another object of this disclosure to provide exemplary methods whereby MR studies may be carried out while subjecting the sample to a minimum of rf pulses. In accordance with a preferred embodiment, nuclei within a sample are inverted using a single rf pulse. Preferably the inversion is sufficient so that some portion of their nuclear magnetization is directed anti-parallel to the direction. Most preferably the magnetization vector is directed entirely anti-parallel to the direction of the magnetic field of the MR magnet.
In Radiation Damping (RD), precessing nuclear magnetization induces a current in any nearby resonant coil or coils; if the induced current is large enough it in itself produces a non negligible magnetic field MRD. If the nuclear magnetization vector is pointing at any angle with respect to the main magnetic field MRD torques the nuclear magnetization back to equilibrium more rapidly than would otherwise be the case (
A related phenomenon to RD is that of “superradiance” (SR) which can be thought of as an extreme form of RD. In circumstances where interaction between the nuclear magnetization and the NMR probe is sufficiently large the anti-parallel magnetization is inherently unstable. Any amount of noise produces a perturbation of the anti-parallel magnetization into the transverse plane, this in turn produces a large torquing field which further drives the anti-parallel magnetization back to equilibrium. The result is a rapid and coherent collapse of any anti-parallel magnetization; this produces a pulse of transverse magnetization that can be detected by the MR probe. Conditions for RD can be expressed mathematically:
[2T2ημ0ργ2Q(h/2π)I]P˜1 Equation 1:
And conditions for SR are
[2T2ημ0ργ2Q(h/2π)I]P>>1 Equation 2:
T2=spin-spin relaxation time of the nuclei
η=filling factor
γ=gyro magnetic ratio of the nuclei
Q=the quality factor of the resonant coil (the NMR probe)
And other variables have their usual definition.
In Equation 1 P is the nuclear polarization. In conventional MR studies, where thermal equilibrium is generally assumed, P is a function of the ambient magnetic field, temperature of the sample, and gamma of the nuclei in question. Traditionally, RD and SR have tended therefore to be only observed for studies carried out at relatively high fields. However improvements in probe quality Q have made RD more common even at lower fields. For example, superconducting technology has been employed to manufacture coils with Qs as high as 4400 for in vivo studies. Probes with this level of quality factor can be expected to make radiation damping a significant factor even at relatively low fields of 1.5 Tesla.
Applicant has discovered that, under certain circumstances, the pulse(s) resulting from creating RD or SR conditions can be used to produce images, spectroscopic identity, dynamic flow data, and other information of interest. This can be done using a single pulse or multiple pulses as desired. Applicant has further discovered that, by controlling conditions necessary for RD or SR pulse formation, information can be obtained from samples in a spatially or temporally controlled manner. Applicant has discovered that the signal to noise of an RD or SR pulse can exceed that of a conventional MR study carried out on an otherwise identical sample (
In the case of a study incorporating hyperpolarized nuclei, the nuclear polarization can not only be greatly enhanced ex vivo but its magnetic vector may be oriented at will. In a particular embodiment, the magnetization vector of a group of HP nuclei may be oriented to be anti-parallel to the magnetic field of an MR device. For example, this can be done by using standard NMR techniques to rotate the magnetization of the hyperpolarized nuclei to the desired vector; this can be done prior to the HP nuclei entering the subject so that the subject itself is not exposed to any rf radiation (
Applicant has discovered that, under certain circumstances, the pulse resulting from RD or SR can be controlled so as to produce transverse magnetization (Mxy) from longitudinal magnetization (Mz)—without the use of additional rf pulses. This results from the feedback mechanism described above which nutates any Mz into the transverse plane. By controlling the conditions under which RD or SR can occur the feedback can be terminated at any point so as to produce single or multiple pulses of Mxy at any desired angular orientation to the main magnetic field. This can then be used to produce an image and/or spectroscopic information, dynamic flow data and other information of interest.
Production of an image traditionally requires many pulses, each designed to extract some amount of spatial information from the sample. To do this from a single or limited number of inverted magnetization pulses requires that the conditions for producing an RD or SR pulse be carefully controlled. In particular, it is desirable to use only a portion of the total inverted magnetization from a sample to produce a pulse from a localized volume in space. Applicant has discovered methods of producing RD or SR in a localized volume in space. In a preferred embodiment, this is done by turning off/on, increasing/decreasing or changing in sign a local magnetic field gradient or gradients. Other embodiments for this include manipulating the probe Q (e.g., by detuning the coil selectively), frequency, and/or changing the parameters of the ambient magnetic field.
In the case where the gradient is sufficiently large such that T2* (where T2* represents the time it takes for any Mxy to dephase due to the action of the gradient) is larger than TRD (where TRD represents the time it takes to nutate any Mz into Mxy due to the action of the RD field) an RD cannot take place as any transverse magnetization is dephased faster than the time it takes to form a pulse. In such an instance any Mz remains “locked in” and undisturbed on time scales t<<T1. However the Mz is also unobservable as only Mxy can be detected in an MR study.
If the gradient is lowered such that T2*˜TSR RD can take place. Applicant has discovered that the transition from the non RD to the RD regime can be quite sharp, allowing the criteria for pulse production to be carefully controlled. By suppressing the gradient in a given region of space, a pulse can be produced that originates from a predefined spatial location. It can therefore be assigned a definite spatial value which is essential to creating a resolved image.
Traditionally RD has been suppressed by using a gradient or gradients that are temporally structures—that is, that turn on/off in time. This suppresses or permits RD from the entire volume located within the field of the resonant coil. Applicant has discovered that gradients can be spatially structured to allow RD to progress in one part of a volume and suppressed in others. By careful manipulation of the nearby current coils the gradient can be made to be zero or very low—sufficiently low to permit RD—in one voxel or other region of interest (e.g., comprising multiple voxels) while remaining large enough to deter RD in the remaining fraction of the volume. By detecting the signal resulting from RD from that one voxel its spatial location and spin content can be determined; the region of zero gradient can then be moved to produce signal from other voxels so as to produce sufficient information to construct an image. This can be done sequentially or in parallel to speed image production.
When the gradient field is suppressed in a local voxel such that the total gradient=0 or is very low, a RD or SR pulse can propagate. This causes any local Mz to nutate into the transverse plane and produce Mxy. Mxy is precessing at the Larmor frequency and hence can be detected by the MR pick up coils. Local conditions can be adjusted—as a non exclusive example, by turning on/off a local gradient—so as to nutate only part of the local Mz into the xy plane. In this manner additional Mz is available to produce pulses at a later time should that be desirable. Or all of the local Mz can be used up in a single pulse. The spatial identity of the pulse can be determined in a number of manners. As a non exclusive example, this can be done by associating the zero point of the local gradient with a definite point or points in x,y,z. For example, the gradient field can be set to about zero for individual voxels spaced from one another in order to speed data acquisition by engaging in parallel data collection.
Local voxel or voxels of zero or very low gradient field can be produced and moved about in space by adjusting currents in nearby shim coils that are typically part of any MR imaging system. Thus an entire image can be built by manipulating the shim coils. Multiple voxels can be produced contemporaneously for example by causing the shim coils to have a time dependent current I0 cos(wt) rather than a static current I0. By adjusting the current frequency in various shims multiple local voxels of zero or low gradient can be produced either permanently or temporarily as desired. If desired, a local coil can be provided surrounding or adjacent to a particular body part (e.g., a head/shoulder coil for neurovascular imaging, a back coil, knee coil, breast coil, etc.) that includes the capability to receive MXY pulses and that can optionally apply rf pulses and/or gradient fields to provide a further means for control of the local gradient field in the region of interest.
Using this approach can have particular advantages and benefits. First, applicant has discovered that SNR can be higher for an RD or SR pulse than for a Fourier Transform of a pulse produced by rf excitation. SNR increase can theoretically be as much as 2×, although lower values (still in excess of what could be achieved even with a 90 degree rotation) can be expected when conditions for RD or SR are not well produced.
Because Mxy is only produced in a region of low or zero gradient, motion artifacts that plague traditional MR imaging can be reduced. Motion artifacts are produced when spins move in the high gradient fields used to produce images in traditional MR. As the spins move in the gradient they lose phase information which leads to image blurring. Producing pulses only in the region of low or zero gradient can be expected to suppress this phenomenon. Also, pulses from RD or SR are inherently phase randomized so there cannot be build up of phase errors as the image is produced voxel by voxel.
Applicant has further discovered that the phase of any Mx converted via RD or SR from local Mz can be distinguished from the phase of spins outside the local voxel. This allows the use of phase locked loops or similar methods to amplify the Mx signal arising from spins in the local voxel of interest.
Occasionally it is desirable to extract local T2 information while producing an MR image or carrying out other kinds of MR studies. T2 mapping can provide contrast between different types of tissue in particular between spins in solid dense matter such as bone and that in surrounding tissue.
Applicant has discovered that T2 contrast can be provided using the proposed technique. As a non exclusive example, this can be done by adjusting the Q of the resonant coil used to nutate any Mz into Mxy. Assuming a low or zero gradient, by increasing Q, the time for an RD or SR pulse to propagate can be made faster than local T2. Conversely, lowering Q can cause T2 to be faster than the time required to produce an RD or SR pulse. In this circumstance no pulse can propagate. Thus regions of different T2's can be distinguished by controlling the local field gradient and adjusting the Q of the pick up coil.
The above described techniques can all be used in conjunction with standard imaging methodologies. For example, slice selective frequency encoding can be used to derive 2D information, with the above technique providing third dimensional information.
Applicant has discovered that, by careful manipulation of external parameters such as but not limited to field gradient, probe frequency, or external field, controlled amounts of Mz can be transformed into Mxy. The transverse magnetization can then be processed using standard Fourier Transform techniques to yield spectroscopic and other information. That is, once Mxy has been produced by nutating Mz using an RD or SR pulse it is no different from Mxy produced using an rf pulse and all of the same Mxy manipulations well known in the art should be available to the operator.
Applicant has discovered ways to produce multiple pulses of Mxy out of a single batch of Mz. As a non exclusive example, this can be done by turning on/off a gradient. With the gradient off magnetization begins to nutate out of the Mz direction into the transverse plane. By re-establishing the gradient the nutation process can be cut off at any time producing a desired amount of Mxy and preserving some Mz for later pulses if desired. The presence of the gradient quickly dephases the Mxy. However its spectra information can be obtained using a number of techniques well described in the art. For example a spin echo can be produced by causing the local gradient to be inverted; the resulting echo is picked up in the coil and can be processed using standard FT techniques to produce spectra and other information of interest.
In studies incorporating hyperpolarization nuclei, a select group of nuclei has its nuclear polarization greatly increased over its thermal equilibrium Boltzmann value. Typically this is done in an ex vivo apparatus; examples include a DNP polarizer with a dissolution device, a PHIP polarizer, or a brute force polarizer. Particularly suitable techniques are described in U.S. Pat. No. 6,651,459, U.S. patent application Ser. No. 12/193,536, filed Aug. 18, 2008 and U.S. patent application Ser. No. 12/879,634, filed Sep. 10, 2010. The foregoing patent and patent applications are incorporated by reference herein in their entireties for any purpose whatsoever.
The vector direction of the enhanced nuclear polarization can be manipulated in a number of ways. In certain hyperpolarization methods it is possible to in situ arrange that the polarization have a given vector with respect to the vector direction of the main analyzing magnetic field. An alternative is to direct the hyperpolarized nuclei into an MR enabled device located in the stray field of the main magnet, simple rf pulses can then be used to invert the magnetization to any desired angle. Most preferably this angle is 180 degrees with respect to the main field but other angles can be used, as desired.
Applicant has discovered that inverted magnetization can be maintained subsequent to these steps and during introduction of the HP nuclei to the subject. For example, various Q spoiling techniques can be used to minimize interaction between the nuclear magnetization and the probe thus deterring conditions necessary for the formation of an SR pulse. Another alternative is to maintain a gradient during this time; as described above the effect of the gradient is to destroy any transverse magnetization and thus keep an SR pulse from propagating.
Information from the HP nuclei can be obtained in the manner described above without the subject ever being exposed to any rf radiation.
Traditional MR spectroscopy requires very large magnetic fields. The large field is used to provide as much separation in frequency space as possible so that nuclei with different chemical shifts may be separately identified.
Applicant has discovered that using the proposed technique it may be possible to carry out certain spectroscopic studies employing analyzing fields lower than those traditionally employed by MR. The basis of this is that, in circumstances where the nuclear polarization is produced without regard to the field of the analyzing magnet, the time required to produce an SR pulse from a given set of nuclei does not depend on the value of the external field. A sample containing nuclei with different spectroscopic identities will produce distinct SR pulses at separable times.
Exemplary MRI Scanner Systemization
An exemplary magnetic resonance system is depicted in
A whole body gradient coil assembly 30 includes x, y, and z-coils mounted along the bore 12 for generating gradient magnetic fields, Gx, Gy, and Gz. Preferably, the gradient coil assembly is a self-shielded gradient coil that includes primary x, y, and z-coil assemblies 32 potted in a dielectric former and secondary x, y, and z-coil assemblies 34 that are supported on a bore defining cylinder of the vacuum Dewar 20. A whole body radio frequency coil 36 can be mounted inside the gradient coil assembly 30. A whole body radio frequency shield 38, e.g., copper mesh, can be mounted between the whole body RF coil 36 and the gradient coil assembly 30. If desired, an insertable radio frequency coil 40 can be removably mounted in the bore in an examination region defined around an isocenter of the magnet 10. In the embodiment of
With continuing reference to
If hyperpolarized materials are to be used as a part of the study, a hyperpolarizer 120 can be provided, or hyperpolarized material can be provided from a remote location and transported to the imaging site in a transport Dewar or other transfer container or agent chamber, 112. The hyperpolarized material can then be disposed in a container within a device 110 for inverting the vector direction of at least one set of nuclei contained in the sample. The device 110 includes a control unit 116 including a controller and power source operably coupled to and controlled by the controller and an electromagnet 114 in operable communication with the power source and controller in the control unit 116. The sample chamber 112 is placed in electromagnetic communication with the electromagnet 114. The controller is adapted and configured to operate the power source to induce an electromagnetic pulse in the electromagnet to orient the vector direction of nuclei in the sample situated in the sample chamber, such as to a 180 degree inversion, or the like An injector assembly 118 is further provided to direct the sample into a patient or other object situated in the magnetic resonance system.
RD/SR signals received by the coil 40 are demodulated by a digital receiver 66 and stored in a data memory 68. The data from the data memory are reconstructed by a reconstruction or array processor 70 into a volumetric image representation that is stored in an image memory 72. If a phased array is used as the receiving coil assembly, the image can be reconstructed from the coil signals. A video processor 74 under operator control converts selected portions of the volumetric image representation into slice images, projection images, perspective views, or the like as is conventional in the art for display on the video monitor.
Typically, a user or users, e.g., 633a, which may be people or groups of users and/or other systems, may engage information technology systems (e.g., computers) to facilitate operation of the system and information processing. In turn, computers employ processors to process information; such processors 603 may be referred to as central processing units (CPU). One form of processor is referred to as a microprocessor. CPUs use communicative circuits to pass binary encoded signals acting as instructions to enable various operations. These instructions may be operational and/or data instructions containing and/or referencing other instructions and data in various processor accessible and operable areas of memory 629 (e.g., registers, cache memory, random access memory, etc.). Such communicative instructions may be stored and/or transmitted in batches (e.g., batches of instructions) as programs and/or data components to facilitate desired operations. These stored instruction codes, e.g., programs, may engage the CPU circuit components and other motherboard and/or system components to perform desired operations. One type of program is a computer operating system, which, may be executed by CPU on a computer; the operating system enables and facilitates users to access and operate computer information technology and resources. Some resources that may be employed in information technology systems include: input and output mechanisms through which data may pass into and out of a computer; memory storage into which data may be saved; and processors by which information may be processed. These information technology systems may be used to collect data for later retrieval, analysis, and manipulation, which may be facilitated through a database program. These information technology systems provide interfaces that allow users to access and operate various system components.
In one embodiment, the MKT™ controller 601 may be connected to and/or communicate with entities such as, but not limited to: one or more users from user input devices 611; peripheral devices 612, components of the magnetic resonance system; an optional cryptographic processor device 628; and/or a communications network 613. For example, the MKT™ controller 601 may be connected to and/or communicate with users, e.g., 633a, operating client device(s), e.g., 633b, including, but not limited to, personal computer(s), server(s) and/or various mobile device(s) including, but not limited to, cellular telephone(s), smartphone(s) (e.g., iPhone®, Blackberry®, Android OS-based phones etc.), tablet computer(s) (e.g., Apple iPad™, HP Slate™, Motorola Xoom™, etc.), eBook reader(s) (e.g., Amazon Kindle™, Barnes and Noble's Nook™ eReader, etc.), laptop computer(s), notebook(s), netbook(s), gaming console(s) (e.g., XBOX Live™, Nintendo® DS, Sony PlayStation® Portable, etc.), portable scanner(s) and/or the like.
Networks are commonly thought to comprise the interconnection and interoperation of clients, servers, and intermediary nodes in a graph topology. It should be noted that the term “server” as used throughout this application refers generally to a computer, other device, program, or combination thereof that processes and responds to the requests of remote users across a communications network. Servers serve their information to requesting “clients.” The term “client” as used herein refers generally to a computer, program, other device, user and/or combination thereof that is capable of processing and making requests and obtaining and processing any responses from servers across a communications network. A computer, other device, program, or combination thereof that facilitates, processes information and requests, and/or furthers the passage of information from a source user to a destination user is commonly referred to as a “node.” Networks are generally thought to facilitate the transfer of information from source points to destinations. A node specifically tasked with furthering the passage of information from a source to a destination is commonly called a “router.” There are many forms of networks such as Local Area Networks (LANs), Pico networks, Wide Area Networks (WANs), Wireless Networks (WLANs), etc. For example, the Internet is generally accepted as being an interconnection of a multitude of networks whereby remote clients and servers may access and interoperate with one another.
The MKT™ controller 601 may be based on computer systems that may comprise, but are not limited to, components such as: a computer systemization 602 connected to memory 629.
Computer Systemization
A computer systemization 602 may comprise a clock 630, central processing unit (“CPU(s)” and/or “processor(s)” (these terms are used interchangeable throughout the disclosure unless noted to the contrary)) 603, a memory 629 (e.g., a read only memory (ROM) 606, a random access memory (RAM) 605, etc.), and/or an interface bus 607, and most frequently, although not necessarily, are all interconnected and/or communicating through a system bus 604 on one or more (mother)board(s) 602 having conductive and/or otherwise transportive circuit pathways through which instructions (e.g., binary encoded signals) may travel to effect communications, operations, storage, etc. Optionally, the computer systemization may be connected to an internal power source 686; e.g., optionally the power source may be internal. Optionally, a cryptographic processor 626 and/or transceivers (e.g., ICs) 674 may be connected to the system bus. In another embodiment, the cryptographic processor and/or transceivers may be connected as either internal and/or external peripheral devices 612 via the interface bus I/O. In turn, the transceivers may be connected to antenna(s) 675, thereby effectuating wireless transmission and reception of various communication and/or sensor protocols; for example the antenna(s) may connect to: a Texas Instruments WiLink WL1283 transceiver chip (e.g., providing 802.11n, Bluetooth 3.0, FM, global positioning system (GPS) (thereby allowing MKT™ controller to determine its location)); Broadcom BCM4329FKUBG transceiver chip (e.g., providing 802.11n, Bluetooth 2.1+EDR, FM, etc.); a Broadcom BCM4750IUB8 receiver chip (e.g., GPS); an Infineon Technologies X-Gold 618-PMB9800 (e.g., providing 2G/3G HSDPA/HSUPA communications); and/or the like. The system clock typically has a crystal oscillator and generates a base signal through the computer systemization's circuit pathways. The clock is typically coupled to the system bus and various clock multipliers that will increase or decrease the base operating frequency for other components interconnected in the computer systemization. The clock and various components in a computer systemization drive signals embodying information throughout the system. Such transmission and reception of instructions embodying information throughout a computer systemization may be commonly referred to as communications. These communicative instructions may further be transmitted, received, and the cause of return and/or reply communications beyond the instant computer systemization to: communications networks, input devices, other computer systemizations, peripheral devices, and/or the like. Of course, any of the above components may be connected directly to one another, connected to the CPU, and/or organized in numerous variations employed as exemplified by various computer systems.
The CPU comprises at least one high-speed data processor adequate to execute program components for executing user and/or system-generated requests. Often, the processors themselves will incorporate various specialized processing units, such as, but not limited to: integrated system (bus) controllers, memory management control units, floating point units, and even specialized processing sub-units like graphics processing units, digital signal processing units, and/or the like. Additionally, processors may include internal fast access addressable memory, and be capable of mapping and addressing memory 629 beyond the processor itself; internal memory may include, but is not limited to: fast registers, various levels of cache memory (e.g., level 1, 2, 3, etc.), RAM, etc. The processor may access this memory through the use of a memory address space that is accessible via instruction address, which the processor can construct and decode allowing it to access a circuit path to a specific memory address space having a memory state. The CPU may be a microprocessor such as: AMD's Athlon, Duron and/or Opteron; ARM's application, embedded and secure processors; IBM and/or Motorola's DragonBall and PowerPC; IBM's and Sony's Cell processor; Intel's Celeron, Core (2) Duo, Itanium, Pentium, Xeon, and/or XScale; and/or the like processor(s). The CPU interacts with memory through instruction passing through conductive and/or transportive conduits (e.g., (printed) electronic and/or optic circuits) to execute stored instructions (i.e., program code) according to conventional data processing techniques. Such instruction passing facilitates communication within the MKT™ controller and beyond through various interfaces. Should processing requirements dictate a greater amount speed and/or capacity, distributed processors (e.g., Distributed MKT™ embodiments), mainframe, multi-core, parallel, and/or super-computer architectures may similarly be employed. Alternatively, should deployment requirements dictate greater portability, smaller Personal Digital Assistants (PDAs) may be employed.
Depending on the particular implementation, features of the MKT™ implementations may be achieved by implementing a microcontroller such as CAST's R8051XC2 microcontroller; Intel's MCS 51 (i.e., 8051 microcontroller); and/or the like. Also, to implement certain features of the MKT™ embodiments, some feature implementations may rely on embedded components, such as: Application-Specific Integrated Circuit (“ASIC”), Digital Signal Processing (“DSP”), Field Programmable Gate Array (“FPGA”), and/or the like embedded technology. For example, any of the MKT™ component collection (distributed or otherwise) and/or features may be implemented via the microprocessor and/or via embedded components; e.g., via ASIC, coprocessor, DSP, FPGA, and/or the like. Alternately, some implementations of the MKT™ may be implemented with embedded components that are configured and used to achieve a variety of features or signal processing.
Depending on the particular implementation, the embedded components may include software solutions, hardware solutions, and/or some combination of both hardware/software solutions. For example, MKT™ features discussed herein may be achieved through implementing FPGAs, which are a semiconductor devices containing programmable logic components called “logic blocks”, and programmable interconnects, such as the high performance FPGA Virtex series and/or the low cost Spartan series manufactured by Xilinx. Logic blocks and interconnects can be programmed by the customer or designer, after the FPGA is manufactured, to implement any of the MKT™ features. A hierarchy of programmable interconnects allow logic blocks to be interconnected as needed by the MKT™ system designer/administrator, somewhat like a one-chip programmable breadboard. An FPGA's logic blocks can be programmed to perform the function of basic logic gates such as AND, and XOR, or more complex combinational functions such as decoders or simple mathematical functions. In most FPGAs, the logic blocks also include memory elements, which may be simple flip-flops or more complete blocks of memory. In some circumstances, the MKT™ may be developed on regular FPGAs and then migrated into a fixed version that more resembles ASIC implementations. Alternate or coordinating implementations may migrate MKT™ controller features to a final ASIC instead of or in addition to FPGAs. Depending on the implementation all of the aforementioned embedded components and microprocessors may be considered the “CPU” and/or “processor” for the MKTT™.
Power Source
The power source 686 may be of any standard form for powering small electronic circuit board devices such as the following power cells: alkaline, lithium hydride, lithium ion, lithium polymer, nickel cadmium, solar cells, and/or the like. Other types of AC or DC power sources may be used as well. In the case of solar cells, in one embodiment, the case provides an aperture through which the solar cell may capture photonic energy. The power cell 686 is connected to at least one of the interconnected subsequent components of the MKT™ thereby providing an electric current to all subsequent components. In one example, the power source 686 is connected to the system bus component 604. In an alternative embodiment, an outside power source 686 is provided through a connection across the I/O 608 interface. For example, a USB and/or IEEE 1394 connection carries both data and power across the connection and is therefore a suitable source of power.
Interface Adapters
Interface bus(ses) 607 may accept, connect, and/or communicate to a number of interface adapters, conventionally although not necessarily in the form of adapter cards, such as but not limited to: input output interfaces (I/O) 608, storage interfaces 609, network interfaces 610, and/or the like. Optionally, cryptographic processor interfaces 627 similarly may be connected to the interface bus. The interface bus provides for the communications of interface adapters with one another as well as with other components of the computer systemization. Interface adapters are adapted for a compatible interface bus. Interface adapters conventionally connect to the interface bus via a slot architecture. Conventional slot architectures may be employed, such as, but not limited to: Accelerated Graphics Port (AGP), Card Bus, (Extended) Industry Standard Architecture ((E)ISA), Micro Channel Architecture (MCA), NuBus, Peripheral Component Interconnect (Extended) (PCI(X)), PCI Express, Personal Computer Memory Card International Association (PCMCIA), and/or the like.
Storage interfaces 609 may accept, communicate, and/or connect to a number of storage devices such as, but not limited to: storage devices 614, removable disc devices, and/or the like. Storage interfaces may employ connection protocols such as, but not limited to: (Ultra) (Serial) Advanced Technology Attachment (Packet Interface) ((Ultra) (Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE), Institute of Electrical and Electronics Engineers (IEEE) 1394, fiber channel, Small Computer Systems Interface (SCSI), Universal Serial Bus (USB), and/or the like.
Network interfaces 610 may accept, communicate, and/or connect to a communications network 613. Through a communications network 613, the MKT™ controller is accessible through remote clients 633b (e.g., computers with web browsers) by users 633a. Network interfaces may employ connection protocols such as, but not limited to: direct connect, Ethernet (thick, thin, twisted pair 10/100/1000 Base T, and/or the like), Token Ring, wireless connection such as IEEE 802.11a-x, and/or the like. Should processing requirements dictate a greater amount speed and/or capacity, distributed network controllers (e.g., Distributed MKTT™), architectures may similarly be employed to pool, load balance, and/or otherwise increase the communicative bandwidth required by the MKT™ controller. A communications network may be any one and/or the combination of the following: a direct interconnection; the Internet; a Local Area Network (LAN); a Metropolitan Area Network (MAN); an Operating Missions as Nodes on the Internet (OMNI); a secured custom connection; a Wide Area Network (WAN); a wireless network (e.g., employing protocols such as, but not limited to a Wireless Application Protocol (WAP), I-mode, and/or the like); and/or the like. A network interface may be regarded as a specialized form of an input output interface. Further, multiple network interfaces 610 may be used to engage with various communications network types 613. For example, multiple network interfaces may be employed to allow for the communication over broadcast, multicast, and/or unicast networks.
Input Output interfaces (I/O) 608 may accept, communicate, and/or connect to user input devices 611, peripheral devices 612, cryptographic processor devices 628, and/or the like. I/O may employ connection protocols such as, but not limited to: audio: analog, digital, monaural, RCA, stereo, and/or the like; data: Apple Desktop Bus (ADB), IEEE 1394a-b, serial, universal serial bus (USB); infrared; joystick; keyboard; midi; optical; PC AT; PS/2; parallel; radio; video interface: Apple Desktop Connector (ADC), BNC, coaxial, component, composite, digital, Digital Visual Interface (DVI), high-definition multimedia interface (HDMI), RCA, RF antennae, S-Video, VGA, and/or the like; wireless transceivers: 802.11a/b/g/n/x; Bluetooth; cellular (e.g., code division multiple access (CDMA), high speed packet access (HSPA(+)), high-speed downlink packet access (HSDPA), global system for mobile communications (GSM), long term evolution (LTE), WiMax, etc.); and/or the like. One typical output device may include a video display, which typically comprises a Cathode Ray Tube (CRT) or Liquid Crystal Display (LCD) based monitor with an interface (e.g., DVI circuitry and cable) that accepts signals from a video interface, may be used. The video interface composites information generated by a computer systemization and generates video signals based on the composited information in a video memory frame. Another output device is a television set, which accepts signals from a video interface. Typically, the video interface provides the composited video information through a video connection interface that accepts a video display interface (e.g., an RCA composite video connector accepting an RCA composite video cable; a DVI connector accepting a DVI display cable, etc.).
User input devices 611 often are a type of peripheral device 612 (see below) and may include: card readers, dongles, finger print readers, gloves, graphics tablets, joysticks, keyboards, microphones, mouse (mice), remote controls, retina readers, touch screens (e.g., capacitive, resistive, etc.), trackballs, trackpads, sensors (e.g., accelerometers, ambient light, GPS, gyroscopes, proximity, etc.), styluses, and/or the like.
Peripheral devices 612, such as other components of the MR system, including signal generators in communication with RF coils, receivers in communication with RF coils, the gradient coil system, main magnet system and the like may be connected and/or communicate to I/O and/or other facilities of the like such as network interfaces, storage interfaces, directly to the interface bus, system bus, the CPU, and/or the like. Peripheral devices may be external, internal and/or part of the MKT™ controller. Peripheral devices may also include: antenna, audio devices (e.g., line-in, line-out, microphone input, speakers, etc.), cameras (e.g., still, video, webcam, etc.), dongles (e.g., for copy protection, ensuring secure transactions with a digital signature, and/or the like), external processors (for added capabilities; e.g., crypto devices 628), force-feedback devices (e.g., vibrating motors), network interfaces, printers, scanners, storage devices, transceivers (e.g., cellular, GPS, etc.), video devices (e.g., goggles for functional imaging, for example, monitors, etc.), video sources, visors, and/or the like. Peripheral devices often include types of input devices (e.g., cameras).
Cryptographic units such as, but not limited to, microcontrollers, processors 626, interfaces 627, and/or devices 628 may be attached, and/or communicate with the MKT™ controller. A MC68HC16 microcontroller, manufactured by Motorola Inc., may be used for and/or within cryptographic units. The MC68HC16 microcontroller utilizes a 16-bit multiply-and-accumulate instruction in the 16 MHz configuration and requires less than one second to perform a 512-bit RSA private key operation. Cryptographic units support the authentication of communications from interacting agents, as well as allowing for anonymous transactions. Cryptographic units may also be configured as part of CPU. Equivalent microcontrollers and/or processors may also be used. Other commercially available specialized cryptographic processors include: the Broadcom's CryptoNetX and other Security Processors; nCipher's nShield, SafeNet's Luna PCI (e.g., 7100) series; Semaphore Communications' 40 MHz Roadrunner 184; Sun's Cryptographic Accelerators (e.g., Accelerator 6000 PCIe Board, Accelerator 500 Daughtercard); Via Nano Processor (e.g., L2100, L2200, U2400) line, which is capable of performing 500+ MB/s of cryptographic instructions; VLSI Technology's 33 MHz 6868; and/or the like.
Memory
Generally, any mechanization and/or embodiment allowing a processor to affect the storage and/or retrieval of information is regarded as memory 629 (or 68, 72, etc.). However, memory is a fungible technology and resource, thus, any number of memory embodiments may be employed in lieu of or in concert with one another. It is to be understood that the MKT™ controller and/or a computer systemization may employ various forms of memory 629. For example, a computer systemization may be configured wherein the functionality of on-chip CPU memory (e.g., registers), RAM, ROM, and any other storage devices are provided by a paper punch tape or paper punch card mechanism; of course such an embodiment would result in an extremely slow rate of operation. In a typical configuration, memory 629 will include ROM 606, RAM 605, and a storage device 614. A storage device 614 may be any conventional computer system storage. Storage devices may include a drum; a (fixed and/or removable) magnetic disk drive; a magneto-optical drive; an optical drive (i.e., Blueray, CD ROM/RAM/Recordable (R)/ReWritable (RW), DVD R/RW, HD DVD R/RW etc.); an array of devices (e.g., Redundant Array of Independent Disks (RAID)); solid state memory devices (USB memory, solid state drives (SSD), etc.); other processor-readable storage mediums; and/or other devices of the like. Thus, a computer systemization generally requires and makes use of memory.
Component Collection
The memory 629 may contain a collection of program and/or database components and/or data such as, but not limited to: operating system component(s) 615 (operating system); information server component(s) 616 (information server); user interface component(s) 617 (user interface); Web browser component(s) 618 (Web browser); database(s) 619; mail server component(s) 621; mail client component(s) 622; cryptographic server component(s) 620 (cryptographic server) and/or the like (i.e., collectively a component collection). These components may be stored and accessed from the storage devices and/or from storage devices accessible through an interface bus. Although non-conventional program components such as those in the component collection, typically, are stored in a local storage device 614, they may also be loaded and/or stored in memory such as: peripheral devices, RAM, remote storage facilities through a communications network, ROM, various forms of memory, and/or the like.
Operating System
The operating system component 615 is an executable program component facilitating the operation of the MKT™ controller. Typically, the operating system facilitates access of I/O, network interfaces, peripheral devices, storage devices, and/or the like. The operating system may be a highly fault tolerant, scalable, and secure system such as: Apple Macintosh OS X (Server); AT&T Plan 9; Be OS; Unix and Unix-like system distributions (such as AT&T's UNIX; Berkley Software Distribution (BSD) variations such as FreeBSD, NetBSD, OpenBSD, and/or the like; Linux distributions such as Red Hat, Ubuntu, and/or the like); and/or the like operating systems. However, more limited and/or less secure operating systems also may be employed such as Apple Macintosh OS, IBM OS/2, Microsoft DOS, Microsoft Windows 2000/2003/3.1/95/98/CE/Millenium/NT/Vista/XP (Server), Palm OS, and/or the like. An operating system may communicate to and/or with other components in a component collection, including itself, and/or the like. Most frequently, the operating system communicates with other program components, user interfaces, and/or the like. For example, the operating system may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. The operating system, once executed by the CPU, may enable the interaction with communications networks, data, I/O, peripheral devices, program components, memory, user input devices, and/or the like. The operating system may provide communications protocols that allow the MKT™ controller to communicate with other entities through a communications network 613. Various communication protocols may be used by the MKT™ controller as a subcarrier transport mechanism for interaction, such as, but not limited to: multicast, TCP/IP, UDP, unicast, and/or the like.
Information Server
An information server component 616 is a stored program component that is executed by a CPU. The information server may be a conventional Internet information server such as, but not limited to Apache Software Foundation's Apache, Microsoft's Internet Information Server, and/or the like. The information server may allow for the execution of program components through facilities such as Active Server Page (ASP), ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, Common Gateway Interface (CGI) scripts, dynamic (D) hypertext markup language (HTML), FLASH, Java, JavaScript, Practical Extraction Report Language (PERL), Hypertext Pre-Processor (PHP), pipes, Python, wireless application protocol (WAP), WebObjects, and/or the like. The information server may support secure communications protocols such as, but not limited to, File Transfer Protocol (FTP); HyperText Transfer Protocol (HTTP); Secure Hypertext Transfer Protocol (HTTPS), Secure Socket Layer (SSL), messaging protocols (e.g., America Online (AOL) Instant Messenger (AIM), Application Exchange (APEX), ICQ, Internet Relay Chat (IRC), Microsoft Network (MSN) Messenger Service, Presence and Instant Messaging Protocol (PRIM), Internet Engineering Task Force's (IETF's) Session Initiation Protocol (SIP), SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE), open XML-based Extensible Messaging and Presence Protocol (XMPP) (i.e., Jabber or Open Mobile Alliance's (OMA's) Instant Messaging and Presence Service (IMPS)), Yahoo! Instant Messenger Service, and/or the like. The information server provides results in the form of Web pages to Web browsers, and allows for the manipulated generation of the Web pages through interaction with other program components. After a Domain Name System (DNS) resolution portion of an HTTP request is resolved to a particular information server, the information server resolves requests for information at specified locations on the MKT™ controller based on the remainder of the HTTP request. For example, a request such as http://123.124.125.126/myInformation.html might have the IP portion of the request “123.124.125.126” resolved by a DNS server to an information server at that IP address; that information server might in turn further parse the http request for the “/myInformation.html” portion of the request and resolve it to a location in memory containing the information “myInformation.html.” Additionally, other information serving protocols may be employed across various ports, e.g., FTP communications across port 21, and/or the like. An information server may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the information server communicates with the MKT™ database 619, operating systems, other program components, user interfaces, Web browsers, and/or the like.
Access to the MKT™ database may be achieved through a number of database bridge mechanisms such as through scripting languages as enumerated below (e.g., CGI) and through inter-application communication channels as enumerated below (e.g., CORBA, WebObjects, etc.). Any data requests through a Web browser are parsed through the bridge mechanism into appropriate grammars as required by the MKT™. In one embodiment, the information server would provide a Web form accessible by a Web browser. Entries made into supplied fields in the Web form are tagged as having been entered into the particular fields, and parsed as such. The entered terms are then passed along with the field tags, which act to instruct the parser to generate queries directed to appropriate tables and/or fields. In one embodiment, the parser may generate queries in standard SQL by instantiating a search string with the proper join/select commands based on the tagged text entries, wherein the resulting command is provided over the bridge mechanism to the MKT™ as a query. Upon generating query results from the query, the results are passed over the bridge mechanism, and may be parsed for formatting and generation of a new results Web page by the bridge mechanism. Such a new results Web page is then provided to the information server, which may supply it to the requesting Web browser.
Also, an information server may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.
User Interface
Computer interfaces in some respects are similar to automobile operation interfaces. Automobile operation interface elements such as steering wheels, gearshifts, and speedometers facilitate the access, operation, and display of automobile resources, and status. Computer interaction interface elements such as check boxes, cursors, menus, scrollers, and windows (collectively and commonly referred to as widgets) similarly facilitate the access, capabilities, operation, and display of data and computer hardware and operating system resources, and status. Operation interfaces are commonly called user interfaces. Graphical user interfaces (GUIs) such as the Apple Macintosh Operating System's Aqua, IBM's OS/2, Microsoft's Windows 2000/2003/3.1/95/98/CE/Millenium/NT/XP/Vista/7 (i.e., Aero), Unix's X-Windows (e.g., which may include additional Unix graphic interface libraries and layers such as K Desktop Environment (KDE), mythTV and GNU Network Object Model Environment (GNOME)), web interface libraries (e.g., ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, etc. interface libraries such as, but not limited to, Dojo, jQuery(UI), MooTools, Prototype, script.aculo.us, SWFObject, Yahoo! User Interface, any of which may be used and) provide a baseline and means of accessing and displaying information graphically to users.
A user interface component 617 is a stored program component that is executed by a CPU. The user interface may be a conventional graphic user interface as provided by, with, and/or atop operating systems and/or operating environments such as already discussed. The user interface may allow for the display, execution, interaction, manipulation, and/or operation of program components and/or system facilities through textual and/or graphical facilities. The user interface provides a facility through which users may affect, interact, and/or operate a computer system. A user interface may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the user interface communicates with operating systems, other program components, and/or the like. The user interface may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.
Web Browser
A Web browser component 618 is a stored program component that is executed by a CPU. The Web browser may be a conventional hypertext viewing application such as Microsoft Internet Explorer or Netscape Navigator. Secure Web browsing may be supplied with 128 bit (or greater) encryption by way of HTTPS, SSL, and/or the like. Web browsers allowing for the execution of program components through facilities such as ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, web browser plug-in APIs (e.g., FireFox, Safari Plug-in, and/or the like APIs), and/or the like. Web browsers and like information access tools may be integrated into PDAs, cellular telephones, and/or other mobile devices. A Web browser may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the Web browser communicates with information servers, operating systems, integrated program components (e.g., plug-ins), and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. Of course, in place of a Web browser and information server, a combined application may be developed to perform similar functions of both. The combined application would similarly affect the obtaining and the provision of information to users, user agents, and/or the like from the MKT™ enabled nodes. The combined application may be nugatory on systems employing standard Web browsers.
Mail Server
A mail server component 621 is a stored program component that is executed by a CPU 603. The mail server may be a conventional Internet mail server such as, but not limited to sendmail, Microsoft Exchange, and/or the like. The mail server may allow for the execution of program components through facilities such as ASP, ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, CGI scripts, Java, JavaScript, PERL, PHP, pipes, Python, WebObjects, and/or the like. The mail server may support communications protocols such as, but not limited to: Internet message access protocol (IMAP), Messaging Application Programming Interface (MAPI)/Microsoft Exchange, post office protocol (POP3), simple mail transfer protocol (SMTP), and/or the like. The mail server can route, forward, and process incoming and outgoing mail messages that have been sent, relayed and/or otherwise traversing through and/or to the MKTT™.
Access to the MKT™ mail may be achieved through a number of APIs offered by the individual Web server components and/or the operating system.
Also, a mail server may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses.
Mail Client
A mail client component 622 is a stored program component that is executed by a CPU 603. The mail client may be a conventional mail viewing application such as Apple Mail, Microsoft Entourage, Microsoft Outlook, Microsoft Outlook Express, Mozilla, Thunderbird, and/or the like. Mail clients may support a number of transfer protocols, such as: IMAP, Microsoft Exchange, POP3, SMTP, and/or the like. A mail client may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the mail client communicates with mail servers, operating systems, other mail clients, and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses. Generally, the mail client provides a facility to compose and transmit electronic mail messages.
Cryptographic Server
A cryptographic server component 620 is a stored program component that is executed by a CPU 603, cryptographic processor 626, cryptographic processor interface 627, cryptographic processor device 628, and/or the like. Cryptographic processor interfaces will allow for expedition of encryption and/or decryption requests by the cryptographic component; however, the cryptographic component, alternatively, may run on a conventional CPU. The cryptographic component allows for the encryption and/or decryption of provided data. The cryptographic component allows for both symmetric and asymmetric (e.g., Pretty Good Protection (PGP)) encryption and/or decryption. The cryptographic component may employ cryptographic techniques such as, but not limited to: digital certificates (e.g., X.509 authentication framework), digital signatures, dual signatures, enveloping, password access protection, public key management, and/or the like. The cryptographic component will facilitate numerous (encryption and/or decryption) security protocols such as, but not limited to: checksum, Data Encryption Standard (DES), Elliptical Curve Encryption (ECC), International Data Encryption Algorithm (IDEA), Message Digest 5 (MD5, which is a one way hash function), passwords, Rivest Cipher (RC5), Rijndael, RSA (which is an Internet encryption and authentication system that uses an algorithm developed in 1977 by Ron Rivest, Adi Shamir, and Leonard Adleman), Secure Hash Algorithm (SHA), Secure Socket Layer (SSL), Secure Hypertext Transfer Protocol (HTTPS), and/or the like. Employing such encryption security protocols, the MKT™ may encrypt all incoming and/or outgoing communications and may serve as node within a virtual private network (VPN) with a wider communications network. The cryptographic component facilitates the process of “security authorization” whereby access to a resource is inhibited by a security protocol wherein the cryptographic component effects authorized access to the secured resource. In addition, the cryptographic component may provide unique identifiers of content, e.g., employing and MD5 hash to obtain a unique signature for an digital audio file. A cryptographic component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. The cryptographic component supports encryption schemes allowing for the secure transmission of information across a communications network to enable the MKT™ component to engage in secure transactions if so desired. The cryptographic component facilitates the secure accessing of resources on the MKT™ and facilitates the access of secured resources on remote systems; i.e., it may act as a client and/or server of secured resources. Most frequently, the cryptographic component communicates with information servers, operating systems, other program components, and/or the like. The cryptographic component may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.
The MKT™ Database
The MKT™ database component 619 may be embodied in a database and its stored data. The database is a stored program component, which is executed by the CPU; the stored program component portion configuring the CPU to process the stored data. The database may be a conventional, fault tolerant, relational, scalable, secure database such as Oracle or Sybase. Relational databases are an extension of a flat file. Relational databases consist of a series of related tables. The tables are interconnected via a key field. Use of the key field allows the combination of the tables by indexing against the key field; i.e., the key fields act as dimensional pivot points for combining information from various tables. Relationships generally identify links maintained between tables by matching primary keys. Primary keys represent fields that uniquely identify the rows of a table in a relational database. More precisely, they uniquely identify rows of a table on the “one” side of a one-to-many relationship.
Alternatively, the MKT™ database may be implemented using various standard data-structures, such as an array, hash, (linked) list, struct, structured text file (e.g., XML), table, and/or the like. Such data-structures may be stored in memory and/or in (structured) files. In another alternative, an object-oriented database may be used, such as Frontier, ObjectStore, Poet, Zope, and/or the like. Object databases can include a number of object collections that are grouped and/or linked together by common attributes; they may be related to other object collections by some common attributes. Object-oriented databases perform similarly to relational databases with the exception that objects are not just pieces of data but may have other types of functionality encapsulated within a given object. If the MKT™ database is implemented as a data-structure, the use of the MKT™ database 619 may be integrated into another component such as the MKT™ component 635. Also, the database may be implemented as a mix of data structures, objects, and relational structures. Databases may be consolidated and/or distributed in countless variations through standard data processing techniques. Portions of databases, e.g., tables, may be exported and/or imported and thus decentralized and/or integrated.
In one embodiment, the database component 619 includes several tables 619a-j. A Users (e.g., operators and physicians) table 619a may include fields such as, but not limited to: user_id, ssn, dob, first_name, last_name, age, state, address_firstline, address_secondline, zipcode, devices_list, contact_info, contact_type, alt_contact_info, alt_contact_type, and/or the like to refer to any type of enterable data or selections discussed herein. The Users table may support and/or track multiple entity accounts. A Clients table 619b may include fields such as, but not limited to: user_id, client_id, client_ip, client_type, client_model, operating_system, os_version, app_installed_flag, and/or the like. An Apps table 619c may include fields such as, but not limited to: app_ID, app_name, app_type, OS_compatibilities_list, version, timestamp, developer_ID, and/or the like. A Patients table for patients associated with an entity administering the magnetic resonance system 619d may include fields such as, but not limited to: patient_id, patient_name, patient_address, ip_address, mac_address, auth_key, port_num, security_settings_list, and/or the like. An MR Studies table 619e may include fields such as, but not limited to: study_id, study_name, security_settings_list, study_parameters, rf_sequences, gradient_sequences, coil_selection, imaging_mode, and/or the like. An RF sequences table 619f including a plurality of different rf pulse sequences may include fields such as, but not limited to: sequence_type, sequence_id, tip_angle, coil_selection, power_level, and/or the like. A gradient sequences table 619g may include fields relating to different gradient field sequences such as, but not limited to: sequence_id, Gx, Gy, Gz, Gxy, Gxz, Gyz, Gxyz, field_strength, time_duration, and/or the like. A raw MR data table 619h may include fields such as, but not limited to: study_id, time_stamp, file_size, patient_id, rf_sequence, body_part_imaged, slice_id, and/or the like. A Images table 619i may include fields such as, but not limited to: image_id, study_id, file_size, patient_id, time_stamp, settings, and/or the like. A Payment Legers table 619j may include fields such as, but not limited to: request_id, timestamp, payment_amount, batch_id, transaction_id, clear_flag, deposit_account, transaction_summary, patient_name, patient_account, and/or the like.
In one embodiment, user programs may contain various user interface primitives, which may serve to update the MKT™ platform. Also, various accounts may require custom database tables depending upon the environments and the types of clients the MKT™ system may need to serve. It should be noted that any unique fields may be designated as a key field throughout. In an alternative embodiment, these tables have been decentralized into their own databases and their respective database controllers (i.e., individual database controllers for each of the above tables). Employing standard data processing techniques, one may further distribute the databases over several computer systemizations and/or storage devices. Similarly, configurations of the decentralized database controllers may be varied by consolidating and/or distributing the various database components 619a-j. The MKT™ system may be configured to keep track of various settings, inputs, and parameters via database controllers.
The MKT™ database may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the MKT™ database communicates with the MKT™ component, other program components, and/or the like. The database may contain, retain, and provide information regarding other nodes and data.
The MKT™ Components
The MKT™ component 635 is a stored program component that is executed by a CPU. In one embodiment, the MKT™ component incorporates any and/or all combinations of the aspects of the MKT™ systems discussed in the previous figures. As such, the MKT™ component affects accessing, obtaining and the provision of information, services, transactions, and/or the like across various communications networks.
The MKT™ component may transform raw data collected by the magnetic resonance system into at least one of (i) an image, (ii) dynamic flow data, (iii) perfusion data, (iii) spectroscopic identity of chemical species, (iv) physiological data, or (v) metabolic data, among other things. In one embodiment, the MKT™ component 635 takes inputs (e.g., digitized representations of MXY signals produced by RD or SR pulses, and transforms the inputs via various components of the system, into outputs (e.g., (i) an image, (ii) dynamic flow data, (iii) perfusion data, (iii) spectroscopic identity of chemical species, (iv) physiological data, or (v) metabolic data, among other things).
The MKT™ component enabling access of information between nodes may be developed by employing standard development tools and languages such as, but not limited to: Apache components, Assembly, ActiveX, binary executables, (ANSI) (Objective-) C (++), C# and/or .NET, database adapters, CGI scripts, Java, JavaScript, mapping tools, procedural and object oriented development tools, PERL, PHP, Python, shell scripts, SQL commands, web application server extensions, web development environments and libraries (e.g., Microsoft's ActiveX; Adobe AIR, FLEX & FLASH; AJAX; (D)HTML; Dojo, Java; JavaScript; jQuery(UI); MooTools; Prototype; script.aculo.us; Simple Object Access Protocol (SOAP); SWFObject; Yahoo! User Interface; and/or the like), WebObjects, and/or the like. In one embodiment, the MKT™ server employs a cryptographic server to encrypt and decrypt communications. The MKT™ component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the MKT™ component communicates with the MKT™ database, operating systems, other program components, and/or the like. The MKT™ may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.
Distributed MKT™ Embodiments
The structure and/or operation of any of the MKT™ node controller components may be combined, consolidated, and/or distributed in any number of ways to facilitate development and/or deployment. Similarly, the component collection may be combined in any number of ways to facilitate deployment and/or development. To accomplish this, one may integrate the components into a common code base or in a facility that can dynamically load the components on demand in an integrated fashion.
The component collection may be consolidated and/or distributed in countless variations through standard data processing and/or development techniques. Multiple instances of any one of the program components in the program component collection may be instantiated on a single node, and/or across numerous nodes to improve performance through load-balancing and/or data-processing techniques. Furthermore, single instances may also be distributed across multiple controllers and/or storage devices; e.g., databases. All program component instances and controllers working in concert may do so through standard data processing communication techniques.
The configuration of the MKT™ controller will depend on the context of system deployment. Factors such as, but not limited to, the budget, capacity, location, and/or use of the underlying hardware resources may affect deployment requirements and configuration. Regardless of if the configuration results in more consolidated and/or integrated program components, results in a more distributed series of program components, and/or results in some combination between a consolidated and distributed configuration, data may be communicated, obtained, and/or provided. Instances of components consolidated into a common code base from the program component collection may communicate, obtain, and/or provide data. This may be accomplished through intra-application data processing communication techniques such as, but not limited to: data referencing (e.g., pointers), internal messaging, object instance variable communication, shared memory space, variable passing, and/or the like.
If component collection components are discrete, separate, and/or external to one another, then communicating, obtaining, and/or providing data with and/or to other component components may be accomplished through inter-application data processing communication techniques such as, but not limited to: Application Program Interfaces (API) information passage; (distributed) Component Object Model ((D)COM), (Distributed) Object Linking and Embedding ((D)OLE), and/or the like), Common Object Request Broker Architecture (CORBA), Jini local and remote application program interfaces, JavaScript Object Notation (JSON), Remote Method Invocation (RMI), SOAP, process pipes, shared files, and/or the like. Messages sent between discrete component components for inter-application communication or within memory spaces of a singular component for intra-application communication may be facilitated through the creation and parsing of a grammar. A grammar may be developed by using development tools such as lex, yacc, XML, and/or the like, which allow for grammar generation and parsing capabilities, which in turn may form the basis of communication messages within and between components.
For example, a grammar may be arranged to recognize the tokens of an HTTP post command, e.g.:
where Value1 is discerned as being a parameter because “http://” is part of the grammar syntax, and what follows is considered part of the post value. Similarly, with such a grammar, a variable “Value1” may be inserted into an “http://” post command and then sent. The grammar syntax itself may be presented as structured data that is interpreted and/or otherwise used to generate the parsing mechanism (e.g., a syntax description text file as processed by lex, yacc, etc.). Also, once the parsing mechanism is generated and/or instantiated, it itself may process and/or parse structured data such as, but not limited to: character (e.g., tab) delineated text, HTML, structured text streams, XML, and/or the like structured data. In another embodiment, inter-application data processing protocols themselves may have integrated and/or readily available parsers (e.g., JSON, SOAP, and/or like parsers) that may be employed to parse (e.g., communications) data. Further, the parsing grammar may be used beyond message parsing, but may also be used to parse: databases, data collections, data stores, structured data, and/or the like. Again, the desired configuration will depend upon the context, environment, and requirements of system deployment.
For example, in some implementations, the MKT™ controller may be executing a PHP script implementing a Secure Sockets Layer (“SSL”) socket server via the information server, which listens to incoming communications on a server port to which a client may send data, e.g., data encoded in JSON format. Upon identifying an incoming communication, the PHP script may read the incoming message from the client device, parse the received JSON-encoded text data to extract information from the JSON-encoded text data into PHP script variables, and store the data (e.g., client identifying information, etc.) and/or extracted information in a relational database accessible using the Structured Query Language (“SQL”). An exemplary listing, written substantially in the form of PHP/SQL commands, to accept JSON-encoded input data from a client device via a SSL connection, parse the data to extract variables, and store the data to a database, is provided below:
Also, the following resources may be used to provide example embodiments regarding SOAP parser implementation:
and other parser implementations:
http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/indexjsp?topic=/com.ibm.IBMDI.doc/referenceguide259.htm
all of which are hereby expressly incorporated by reference.
In order to address various issues and advance the art, the entirety of this application for MKT™ APPARATUSES, METHODS AND SYSTEMS (including the Cover Page, Title, Headings, Field, Background, Summary, Brief Description of the Drawings, Detailed Description, Claims, Abstract, Figures, Appendices and/or otherwise) shows by way of illustration various embodiments in which the claimed inventions may be practiced. The advantages and features of the application are of a representative sample of embodiments only, and are not exhaustive and/or exclusive. They are presented only to assist in understanding and teach the claimed principles. It should be understood that they are not representative of all disclosed embodiments. As such, certain aspects of the disclosure have not been discussed herein. That alternate embodiments may not have been presented for a specific portion of the invention or that further undescribed alternate embodiments may be available for a portion is not to be considered a disclaimer of those alternate embodiments. It will be appreciated that many of those undescribed embodiments incorporate the same principles of the invention and others are equivalent. Thus, it is to be understood that other embodiments may be utilized and functional, logical, organizational, structural and/or topological modifications may be made without departing from the scope and/or spirit of the disclosure. As such, all examples and/or embodiments are deemed to be non-limiting throughout this disclosure. Also, no inference should be drawn regarding those embodiments discussed herein relative to those not discussed herein other than it is as such for purposes of reducing space and repetition. For instance, it is to be understood that the logical and/or topological structure of any combination of any program components (a component collection), other components and/or any present feature sets as described in the figures and/or throughout are not limited to a fixed operating order and/or arrangement, but rather, any disclosed order is exemplary and all equivalents, regardless of order, are contemplated by the disclosure. Furthermore, it is to be understood that such features are not limited to serial execution, but rather, any number of threads, processes, services, servers, and/or the like that may execute asynchronously, concurrently, in parallel, simultaneously, synchronously, and/or the like are contemplated by the disclosure. As such, some of these features may be mutually contradictory, in that they cannot be simultaneously present in a single embodiment. Similarly, some features are applicable to one aspect of the invention, and inapplicable to others. In addition, the disclosure includes other inventions not presently claimed. Applicant reserves all rights in those presently unclaimed inventions including the right to claim such inventions, file additional applications, continuations, continuations in part, divisions, and/or the like thereof. As such, it should be understood that advantages, embodiments, examples, functional, features, logical, organizational, structural, topological, and/or other aspects of the disclosure are not to be considered limitations on the disclosure as defined by the claims or limitations on equivalents to the claims. It is to be understood that, depending on the particular needs and/or characteristics of a MKT™ individual and/or enterprise user, database configuration and/or relational model, data type, data transmission and/or network framework, syntax structure, and/or the like, various embodiments of the MKT™ may be implemented that enable a great deal of flexibility and customization.
All statements herein reciting principles, aspects, and embodiments of the disclosure, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future, i.e., any elements developed that perform the same function, regardless of structure.
Descriptions herein of circuitry and method steps and computer programs represent conceptual embodiments of illustrative circuitry and software embodying the principles of the disclosed embodiments. Thus the functions of the various elements shown and described herein may be provided through the use of dedicated hardware as well as hardware capable of executing software in association with appropriate software as set forth herein.
In the disclosure hereof any element expressed as a means for performing a specified function is intended to encompass any way of performing that function including, for example, a) a combination of circuit elements and associated hardware which perform that function or b) software in any form, including, therefore, firmware, microcode or the like as set forth herein, combined with appropriate circuitry for executing that software to perform the function. Applicants thus regard any means which can provide those functionalities as equivalent to those shown herein.
Similarly, it will be appreciated that the system and process flows described herein represent various processes which may be substantially represented in computer-readable media and so executed by a computer or processor, whether or not such computer or processor is explicitly shown. Moreover, the various processes can be understood as representing not only processing and/or other functions but, alternatively, as blocks of program code that carry out such processing or functions.
The methods, systems, computer programs and mobile devices of the present disclosure, as described above and shown in the drawings, among other things, provide for improved magnetic resonance methods, systems and machine readable programs for carrying out the same. It will be apparent to those skilled in the art that various modifications and variations can be made in the devices, methods, software programs and mobile devices of the present disclosure without departing from the spirit or scope of the disclosure. Thus, it is intended that the present disclosure include modifications and variations that are within the scope of the subject disclosure and equivalents.
This application claims the benefit of priority of and is a continuation of International Patent Application No. PCT/US2012/30384, filed Mar. 23, 2012, which in turn claims the benefit of priority to U.S. Provisional Patent Application Ser. No. 61/466,500, filed Mar. 23, 2011 and U.S. Provisional Patent Application Ser. No. 61/522,076, filed Aug. 10, 2011. The disclosure of each of the aforementioned patent applications is incorporated by reference herein in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/US2012/030384 | Mar 2012 | US |
| Child | 13623759 | US |
