ES2788140B2 - DISTRIBUTED PHOTOBIOMODULATION THERAPY, SYSTEM AND METHOD - Google Patents

Description

DESCRIPTION

DISTRIBUTED PHOTOBIOMDULATION THERAPY SYSTEM

CROSS REFERENCE TO RELATED APPS

This application claims priority from US Provisional Application No. 62/653,846, entitled "Distributed Photobiomodulation Therapy System and Method", filed April 6, 2018.

Th is application is related to the following applications: International Application No. PCT/US2015/015547, entitled “Sinusoidal drive system and method for phototherapy,” filed on February 12, 2015; International Application No. PCT/US2016/058064, titled “Flexible 3D Printed Circuit Board with Redundant Interconnects,” filed October 21, 2016; and US application no. 16/377,192 , entitled " Distributed Photobiomodulation Therapy Devices and Methods , Biofeedback , and Communication Protocols , " filed April 6 , 2019 .

Each of the foregoing applications and patents is incorporated herein by reference in its entirety.

BACKGROUND

field of invention

This invention relates to biotechnology for health and medical applications, including photobiomodulation, phototherapy, and photobiomodulation therapy (PBT).

related art discussion

Biophotonics is the biomedical field concerned with the electronic control of photons, that is, light, and their interaction with living cells and tissues. Biophotonics includes surgery, imaging, biometrics, disease detection, and photobiomodulation (PBM). Photobiomodulation therapy (PBT), also known as phototherapy, is the controlled application of photons of light, typically infrared, visible, and ultraviolet light, to invoke photobiomodulation for medical therapeutic purposes including combating injury, disease, pain, and discomfort. of the immune system. More specifically, PBT involves subjecting cells and tissues undergoing treatment to a stream of photons of specific wavelengths of light, either continuously or in repeated discontinuous pulses to control the energy transfer and absorption behavior of cells and tissues. alive.

FIGURE . 1 illustrates elements of a PBT system capable of operating with continuous or pulsed light including an LED controller 1 that controls and activates the LEDs as a source of photons 3 emanating from an LED pad 2 on tissue 5 for the patient. Although a human brain is shown as tissue 5, any organ, tissue, or physiological system can be treated using PBT. Before and after, or during the treatment, a doctor or clinician 7 can adjust the treatment by controlling the setting of the LED controller 1 according to the observations of the LED controller 1.

Although there are many potential mechanisms, as shown in FIGURE .2 , it is generally accepted that the dominant photobiological process 22 responsible for photobiomodulation during PBT treatment using red and infrared light occurs within the mitochondria 21 , an organelle present in each eukaryotic cell 20 comprising both plants and animals, including birds, mammals, horses and humans. . According to current knowledge, the photobiological process 22 involves a photon 23 impinging on a cytochrome-c oxidase (CCO) molecule 24 , which acts as a battery charger increasing cellular energy content by transforming adenosine monophosphate (AMP) into a higher energy adenosine diphosphate (ADP) molecule, and convert the ADP molecule into an even higher energy adenosine triphosphate (ATP) molecule. In the process of increasing the energy stored in an AMP - to - ADP - to - ATP charging sequence 25, the cytochrome-c oxidase molecule 24 acts as a battery charger with the ATP molecule 26 acting as a cellular storage battery. of energy, a process that could be considered animal “photosynthesis”. The cytochrome-c oxidase molecule 24 is also capable of converting energy from glucose resulting from the digestion of food into fuel in the ATP loading sequence 25, or through a combination of digestion and photosynthesis. To drive cell metabolism, the ATP molecule 26 can release energy 29 through a process of unloading from ATP to ADP to AMP 28. Energy 29 is then used to drive protein synthesis, including the formation of catalysts, enzymes , DNA polymerase, and other biomolecules.

Another aspect of the photobiological process 22 is that the cytochrome-c oxidase molecule 24 is a scavenger of a nitric oxide (NO) molecule 27, an important signaling molecule in neuronal communication and angiogenesis, the growth of new arteries and capillaries. . Illumination of the cytochrome-c oxidase 24 molecule in treated cells during PBT releases the NO 27 molecule in the vicinity of injured or infected tissue, thereby increasing blood flow and oxygen delivery to the treated tissue, accelerating the healing, tissue repair and the immune response.

To perform PBT and stimulate cytochrome-c oxidase molecule 24 to absorb photon energy 23, the intermediate tissue between the light source and the light-absorbing tissue cannot block or absorb the light. As illustrated in FIG . 3, the spectrum of Molecular absorption of electromagnetic radiation (EMR) by human tissue is illustrated in a graph 40 of the absorption coefficient versus the wavelength of electromagnetic radiation A (measured in nm). Shown in FIGURE. 3 are the relative absorption coefficient s of oxygenated hemoglobin (curve 44a), deoxyg enated hemoglobin (curve 44b), cytochrome c (curves 41a, 41b), water (curve 42) and fats and lipids (curve 43) as a function of the wavelength of light. As illustrated, deoxygenated hemoglobin (curve 44b) and also oxygenated hemoglobin, ie blood (curve 44a) strongly absorb light in the red part of the visible spectrum, especially for wavelengths less than 650 nm. At longer wavelengths in the infrared portion of the spectrum, ie above 950 nm, EMR is absorbed by water (H ² O) shown as curve 42. At wavelengths between 650 nm and 950 nm, human tissue is essentially transparent, as illustrated by transparent. optical window 45.

Apart from absorption by fats and lipids (curve 43), EMR comprising photons 23 of wavelengths A within the transparent optical window 45, is directly absorbed by cytochrome-c oxidase (curves 41aa, 41b). Specifically, cytochrome-c oxidase molecule 24 absorbs the infrared portion of the spectrum represented by curve 41b unimpeded by water or blood. A secondary absorption tail for cytochrome-c oxidase (curve 41a), illuminated by light in the red part of the visible spectrum, is partially blocked by the absorption properties of deoxygenated hemoglobin (curve 44b), limiting any response. photobiological for deep tissue but still. activated in epithelial tissue and cells. FIGURE. 3 thus shows that PBT for skin and internal organs and tissues requires different treatments and wavelengths of light, red for skin and infrared for internal organs and tissues.

Present photon release systems

To achieve maximum energy coupling into tissue during PBT, it is important to design a consistent delivery system to consistently and evenly illuminate tissue with photons. While early attempts to use filtered lamps, lamps are extremely hot and uncomfortable for patients, can potentially burn patients and physicians, and are extremely difficult in maintaining uniform illumination during treatment for extended durations. The lamps also suffer from short lifespans, and if they are built with rarefied gases, they can also be expensive to replace on a regular basis. Due to the filters, the lamps must get very hot to achieve the required photon flux to achieve efficient therapy in reasonable treatment durations. Unfiltered lamps, like the sun, actually offer too broad a spectrum and limit the effectiveness of the photons by simultaneously stimulating beneficial and unwanted chemical reactions, some of which involve harmful rays, especially in the ultraviolet portion of the spectrum. electromagnetic. Long periods of exposure to ultraviolet light are also known to increase the risk of getting cancer because ultraviolet light damages DNA. In the infrared spectrum, prolonged exposure to far-infrared electromagnetic radiation and heat can cause skin dryness and premature aging by destroying elastin and collagen.

Alternatively, lasers have been and continue to be used to perform PBT, generally referred to by the term LLLT, an acronym for "Low Level Laser Therapy". Unlike lamps, lasers risk burning the patient, not through heat, but by exposing the tissue to intense concentrated optical power, also known as ablation. To avoid that problem, special care must be taken that the laser light is limited in its output power and that excessively high currents are not accidentally produced that produce dangerous light levels. A second, more practical problem arises from the small "spot size" of a laser, the illuminated area. Because a laser illuminates a small focused area, it is difficult to treat large organs, muscles, or tissues and it is much easier for an overwhelming condition to arise.

Another problem with laser light is that its "coherence", which prevents a laser beam from spreading out, makes it more difficult to cover large areas during treatment. Studies reveal that there is no additional inherent benefit of PBT using coherent light. On the one hand, bacterial, plant, and animal life evolved and naturally absorb scattered, non-coherent light, because coherent light does not occur naturally from any known light source. Second, the The first two layers of epithelial tissue already destroy any optical coherence, so the coherence of an incident laser beam is rapidly lost as it is absorbed in human or animal tissue.Laser manufacturers have promoted the premise that patterns of Optical interference from laser light called "specks" arising from backscatter enhance therapeutic efficacy, but no scientific evidence has been provided to support such marketing-motivated claims.

Furthermore, the optical spectrum of a laser is too narrow to fully excite all of the beneficial chemical and molecular transitions required to achieve a highly efficient PBT. The limited spectrum of a laser, typically a range of ±1 nm around the central wavelength value of the laser, makes it difficult to adequately drive all of the necessary beneficial chemical reactions in PBT. It is difficult to cover a range of frequencies with a narrow bandwidth optical source. For example, referring back to FIGURE. 3, The chemical reactions of chromophores (light-absorbing molecules) involved in making the absorption spectra CCO um (curve 41b) are clearly different from the reactions that give rise to the absorption tail (curve 41a). Assuming that the absorption spectra of both regions are shown to be beneficial, it is difficult to cover this wide range with an optical source that has a wavelength spectrum only 2 nm wide.

Just as sunlight has an excessively broad spectrum of wavelengths, which photobiologically excites many chemical reactions in competition with many EMR wavelengths, some even harmful, the wavelength spectrum of laser light is too narrow and does not stimulate sufficient chemical reactions to achieve full efficacy in phototherapeutic treatment. . This topic is discussed in greater detail in a related application titled "Phototherapy System and Process Including a Programmable Waveform Dynamic LED Driver" by Williams et al. (US Application No. 14/073,371), now US Patent No. 9,877,361, issued January 23, 2018, which is incorporated herein by reference.

To deliver PBT by exciting the full range of wavelengths in the transparent optical window 45, i.e. the full width of approximately 650 nm to 950 nm, even if four different wavelength light sources are employed to span the range, each light source would require a bandwidth nearly 80 nm wide. This is more than an order of magnitude wider than the bandwidth of a laser light source. This range is simply too wide for lasers to cover practically. Today, LEDs are commercially available to emit a wide range of light spectrums from the deep infrared to the ultraviolet portion of the electromagnetic spectrum. With bandwidths of ±30 nm to ±40 nm, it is much easier to cover the desired spectrum with center frequencies located in the red, long red, short near-infrared (NIR), and mid-NIR portions of the spectrum, e.g., 670 nm , 750nm, 810nm and 880nm.

Photobiomodulation therapy (PBT) is clearly distinguished from photo-optic therapy. As the picture shows. 4 A, PBT involves direct stimulation of tissue 5 with photons 3 emitted by the LED pad 2. Tissue 5 may not be related to the eyes and may comprise organs associated with the endocrine and immune systems, such as kidneys, liver, glands, lymph nodes etc or the musculoskeletal system, such as muscles, tendons, ligaments, and even bones. PBT also directly treats and repairs neurons, including peripheral nerves, the spinal cord, as well as (as shown) the brain 5 and brainstem. Transcranial PBT treatment penetrates the skull and shows rapid and significant therapeutic benefits in concussion recovery and repair of damage caused by mild traumatic brain injury (mTBI). In other words, PBT energy is absorbed by chromophores in cells not associated with the optic nerve. Photo-optic therapy, by contrast, involves exciting the retina with colored light or images to invoke a cognitive or emotional response or to help synchronize the body's circadian rhythms with its around. In such cases, the image 12 from the light source 12 stimulates the optic nerve in the eye 11 to send electrical signals, ie neural impulses, to the brain 5.

Several rudimentary tests highlight the many huge differences between PBT and photo-optic therapy. For one, photo-optic therapy only works on the eyes, while PBT affects any cell, including internal organs and brain cells. In photo-optic therapy, light is directed into light perception cells (photo-transduction), which in turn results in the generation of electrical signals that are carried to the brain, where as PBT stimulates chemical, ionic, electrons and thermal transport within the treated cells and tissues, without the need for signal transduction to the brain. The effect is local and systemic without the help of the brain. For example, blind patients respond to PBT but not to photo-optic therapy. Another distinction between photo-optic therapy and PBT is illustrated in FIGURE. 4 B. In the case of sight, that is, photo-optic stimulation or vision, the combination of red light 15A and blue light 15B emanating from the light source 14, once received by the eye 11 sends a signal electrical 9 to brain 5, which perceives the color of the incident light as purple. In reality, violet/purple light has a much shorter wavelength than blue or red light and as such comprises photons with higher energy than red 15A light or blue 15B light. In the case of PBT, cell 16 and the mitochondria 17 contained within it will respond photochemically to light source 14 as if it were emitting red 15A and blue 15B light (which it really is), and will not respond as if violet light were present. . Only short-wavelength true purple light emitted from a violet or ultraviolet light source can produce a photobiomodulation response to purple light. In other words, mitochondria and cells are not "fooled" by mixing different colored light like the eye and brain are. In conclusion, photooptic stimulation is very different from photobiomodulation. As such, techniques and developments in the art of photo-optic therapy cannot be considered applicable or relevant to PBT.

As a side note, the etymological ambiguity in the nomenclature led researchers to change the original references using the Catholic term 'phototherapy' or PT to the more modern currently accepted term 'photobiomodulation therapy' or PBT. The term phototherapy has been used generically to refer to any therapeutic application of light, including (i) photo-optic therapy that involves visual stimulation, (ii) photobiomodulation therapy or PBT that involves cell modulation, and (iii) photodynamic therapy or PDT that activates a injected chemical. or ointment applied with light to stimulate a chemical reaction. An equally broad term 'photochemistry', the chemical reactions stimulated by light, also ambiguously refers to any and all of the above treatments. So while photochemistry and phototherapy have broad meaning today, PBT, PDT, and photo-optic therapy have specific, non-overlapping interpretations.

As another source of confusion, the term LLLT was originally intended to stand for 'low level laser therapy' to distinguish lasers operated at low power levels (sometimes called 'cold' lasers in the popular press) from lasers that They operate at high power for tissue ablation and surgery. With the advent of LED-based therapies, some authors combined the nomenclature of LED and laser-based therapies into "low-level light therapy", with the same acronym LLLT. This unfortunate action caused much confusion in the published art and indiscriminately blurred the distinction of two very different photon delivery systems. A "low level" laser is safe for eyes and burns only because it operates at low levels. If a cold laser is deliberately or accidentally turned up to a higher level so that it is no longer 'cold', it can cause severe burns or blindness in milliseconds. By contrast, LEDs always operate at low levels and cannot operate at high optical power densities. At any power level, LEDs can cause blindness. And while LEDs can overheat by running too much current through them for extended periods, they can't cause instantaneous burns or ablate tissue the way an ultimate can. As such, the term low level light is meaningless in reference to an LED. Accordingly, throughout this application, the acronym LLLT will only refer to laser PBT, which stands for Low Level Laser Therapy, and will not be used to refer to LED PBT.

Current photobiomodulation therapy systems

Photobiomodulation therapy systems of the current state of the art, shown by example system 50 in FIGURE. 5 , comprises the controller 51, electrically connected to two sets of LED panels. Specifically, output A of controller 51 is connected via cable 53a to a first set of LED pads comprising an electrically interconnected LED pad 52b. LED pads 52a and 52c are optionally connected to LED pad 52b via electrical jumpers 54a and 54b to create a first set of LED pads that function as a single LED pad comprising more than 600 LEDs and covering a treatment area exceeding the 600 cm2. Similarly, output B of controller 51 is connected via a cable 53b to a second set of LED pads comprising an electrically interconnected LED pad 52e. LED pads 52d and 52f are optionally connected to LED pad 52d via electrical jumpers 54c and 54d to create a second set of LED pads that function as a single LED pad comprising more than 600 LEDs and covering a treatment area exceeding the 600 cm2.

In the system shown, controller 51 not only generates the signals to control the LEDs within the pads, but also provides a power source for drive the LEDs. The electrical power delivered from the driver 51 to the LED pads is substantial, typically 12 W for two sets of three pads each. An exemplary electrical schematic of the system is shown in FIGURE. 6 A, where the controller 61 includes an SMPS 65 switching power supply used to convert 120 V AC to 220 V AC mains 64 power into at least two regulated DC voltage sources, i.e., 5 V for control and logic, and a higher voltage VLED supply used to power the LED strings on the LED pads. Typical voltages for VLEDs range from 24V to 40V depending on the number of LEDs connected in series. To facilitate algorithmic control, the microcontroller (pC) 67 executes dedicated software in response to user command input on the touch screen LCD panel 66. The result is a series of pulses output in some alternating pattern on the A outputs of logic buffers 68a and 68b used to drive the red and near-infrared (NIR) LEDs on the LED pads connected to output A. A similar arrangement is included for output B using its own dedicated logic buffers, but where pC 67 can manage and control outputs A and B simultaneously.

The signal at output A is then routed to one or more LED pads 62 via shield cable 63 comprising high current lines, GND ground 69a, 5V supply line 69b and ^led V supply line 69c, as well as such as LED control signal line 70a for control of driving on NIR LEDs 71a through 71m, and LED control signal line 70b for control of driving on red LEDs 72a through 72m. Control signal lines s 70a and 70b, in turn, activate the base terminals of bipolar junction transistor s 73a and 73b, respectively, the transistors operating as switches to turn the corresponding strings of LEDs on and off. When the input to either bipolar transistor is low, i.e. biased to ground, there is no base current or collector current flow and the LED string remains dark. When the input to either bipolar transistor is high, ie biased to 5 V, base current flows and correspondingly collector current flows, lighting the LEDs in the corresponding LED string. LED current flow is established by the LED turn-on voltages and by current-limiting resistors 74a or 74b. The use of resistors to set LED brightness is not preferred because any variation in LED voltage, either from manufacturing stochastic variability or variations in temperature during operation, will result in a change in LED brightness. . The result is poor uniformity in LED brightness across an LED pad, from LED pad to LED pad, and from one manufacturing batch to the next. An improvement in maintaining LED brightness uniformity can be obtained by replacing resistors 74a and 74b with fixed value constant current sources or sinks 75a and 75b, as shown in FIGURE. 6 b.

The physical connection between the PBT controller 61 and the LED pads 62, over the shielded cable 63, can also be described as two communication stacks that interact in the language of the 7 Layer Open Source Initiative or the OSI model of 7 layers. As the picture shows. 7 , the PBT driver 61 can be represented as the stack 80 comprising the application layer-7, the PBT driver operating system called LightOS v1. In operation, the application layer transfers data to the physical layer or layer 1 PHY comprising logical buffers. The stack 80 unidirectionally sends electrical signals 82 to the PHY-1 layer, i.e., the LED chain drivers, in the communication stack 81 of the passive LED pad 62.

Because the electrical signals comprise simple digital pulses, stray impedances in cable 63 can affect the integrity of the communication signal and the operation of the LED pad. As the picture shows..

8 , as the sent square wave electrical signal 82 can be significant and distorted in the received waveform 83 including reduced magnitude and duration 84a, slow rise times 84b, voltage spikes 84c, oscillations 84d, and loops ground 89 affecting the ground 84e signal bounce. Cable parasites responsible for these disturbances include power line series resistances 87a to 87c and inductances 86a to 86c, and interconductor capacitances 85a to 85e. Other effects may include ground loop conduction 89 and antenna effects 88.

Another disadvantage of using simple electrical signal connections between the PBT controller 61 and the LED pads is that the PBT system cannot confirm whether the peripheral connected to the cable 63 is in fact a qualified LED pad or an invalid load. For example, incorrect LED configurations that do not correspond to the PBT driver, as shown in FIGURE. 9 , will result in either inadequate or excessive LED current. Specifically, as shown in icon 91, too many LEDs in series will result in a high voltage drop with little or no LED illumination. Conversely, as shown in icon 92, too few LEDs connected in series can cause excess current, overheating, and possible burn hazards to the patient.

Non-LED power loads from the PBT 61 controller may damage the peripheral, the controller, or both. This is particularly problematic because a pin on the output of the PBT driver supplies high voltage of 20V or more, exceeding the 5V rating of most semiconductors and causing permanent damage to integrated circuits. Inductive loads represented by icon 94 can cause surge voltage spikes that can damage the controller. Loads containing motors such as disk drives or fans can cause excessive and damaging inrush currents. Shorted wires or shorted electrical loads, as shown in icon 93 , may cause fires. Connecting a battery to the PBT 61 controller, as shown by icon 96, can result in excessive current and risk of fire. Either vercharging or subjecting a chemical cell to a surge also has the potential to cause intense fire or even an explosion. Unknown electrical charges , shown with the 95 icon , represent unspecified risks. Especially problematic is any connection between the PBT 61 controller and an electrical power source such as a generator, car battery, or UPS, the result of which can include complete destruction of the system and extreme fire hazard. In FIGURE. 9 Icons are intended to represent a class of electrical loads, but should not be considered as a specific circuit.

Other problems arise when mismatched LED pads are connected to the same output. For example, in FIG. 10 two different LED pads 62 and 79, powered by a common wire 63, share ground connections 69a, 5V supply 69b, ^LED high voltage V supply 69c, LED visible light control signal ^vv 70a and control signal of near infrared ^nir LEDs 70b. As shown, LED pad 62 includes current sinks 75a and 75b and switches 73a and 73b driving corresponding LEDs 71a through 71m which has a visible light wavelength ^Av and LEDs 72a through 72m which has a length near-infrared A-wave A ^nir . Alternatively, the LED pad 79 includes the same current sinks 75a and 75b and switches 73a and 73b, but different wavelength LED units, specifically LEDs 76a through 76m that have a visible light wavelength. A ^v2 and the LEDs 77a through 77m which has a near infrared of wavelength A ^nir2 . None of the LED strings has the same light wavelength as the other LED strings. For example, A ^v may comprise red light, while A ^v2 may comprise blue light. Similarly, A ^nir may comprise 810 nm radiation, while A ^v2 may comprise 880 nm. In operation, the parallel connection of the red and blue LEDs driven by LED signal ^v 70a means that a treatment for red light could inadvertently generate blue light. Similarly, paralleling the 810nm and 880nm LEDs driven by the 70a ^nir LED signal means that a treatment for one wavelength NIR LED could inadvertently drive a different wavelength.

Another problem arises when two or more LED pads are connected to both LED outputs at the same time, as shown in FIGURE. 11 A. As shown, the PBT 51 driver has two outputs, Output A and Output B. These outputs are designed to drive separate sets of LED pads. As shown, Output A is connected to LED pad 52d via cable 53a. Output B is connected to LED pad 52e via wire 53b and is also connected via jumper 54d to LED pad 52f. However, accidentally jumper 54c connects LED pad 52e to LED 52d and therefore shorts output A to output B. The electrical impact of shorting outputs A and B together depends on the treatment program being run. FIGURE.

11B illustrates the case where both the A and B outputs of the buffer 100 control the red/visible light output, specifically the buffers 101a and 101c are active at the same time. As shown, the outputs are shorted across electrical leads 102a to LED pad 105a, through connector 104a to LED pad 105b, and finally through connector 103a. In operation, the frequency and pulse patterns of the two outputs are asynchronous, which means that any combination of high and low output biases can occur. If the pull-up transistors are too strong, the output buffers can be destroyed in another ; otherwise, alternating power signals may cause the LEDs to stay on with a high duty factor causing overheating and a potential burn hazard to the patient.

In FIGURE. 11C , buffer 101a on output A is powering the red LEDs on LED pads 105a and 105b while buffer 101d on output B is powering the NIR LEDs on LED pads 105a and 105b as well. Although the independent operation of the red and NIR LEDs does not present an electrical problem, simultaneous driving of the red and NIR LEDs will cause the LED pad to overheat, which could damage the pad and possibly burn the patient. This overpower condition is illustrated by the waveforms shown in FIGURE. 11 D where the power P v of the conductive visible LEDs displayed by waveform 110 has a Pave average power of 113, and the Pnir power of the NIR LEDs displayed by waveform 111 has a Pave average power of 114. Collectively , the aggregate power 112 waveform has an average power 115 of magnitude 2Pave.

On current LED pads, overheating for any reason is problematic because there is no temperature protection. As the picture shows. 12 Even if LED pad 109 does ave temperature sensing h, with one-way data flow 82 on wire 63 there is no way for LED pad 109 to inform PBT controller 61 of an over-temperature condition or to suspend. the performance.

As described above, the limitations of current PBT systems above are numerous, impacting PBT system utility, functionality, security, and expandability. These limitations include the following issues:

• Electrical "signal" communication to the LED pad: The signals from the PBT driver to the LED pads are simple digital pulses, not differential communication between a pair of bus transceivers. These signals are sensitive to common mode noise and ground loops that affect the magnitude and duration of the pulses that control LED operation. as simple electrical pulses, the system also lacks error checking capability, so faults cannot be corrected or even detected.

• Unidirectional Signal Flow from PBT Driver to LED Pad – With unidirectional data flow, PBT drivers cannot authenticate any LED Pad connected to their output, nor once connected can they monitor a pad's health status. One-way data also prevents feedback of an LED pad's status or reporting of other pad information to the main PBT controller.

• Inability to detect a short on misconnection of multiple pads: Due to user error, the misconnection of two outputs of a PBT controller to the same LED pad(s), ie, an inadvertent short between two outputs, means that both outputs are driving the same LED strings. This misconnection error can damage the LED driver circuitry, lead to overheating of the LED, risk of patient burns, and possible fire.

• Inability to Identify Approved LED Pads or Certified Manufacturers – Failing to identify the pedigree of an LED pad, a PBT system will unknowingly activate any LED connected to it, including illegal, counterfeit, or imitation LED pads. Driving pads not manufactured or certified by the system specifier or manufacturer have unknown consequences ranging from loss of functionality and reduced effectiveness to safety risks. Commercially, the marketing and sale of counterfeit and imitation LED pads also deprives IP-licensed PBT device dealers of legal revenue.

• Inability to identify a connected device as an LED pad – no ability to confirm if a device connected to a PBT controller output is an LED pad (rather than a completely unrelated peripheral such as a speaker, battery, motor, etc. .), Connection of an unauthorized electrical load to the output of a PBT system will invariably damage the fixture, the PBT controller, or both. When an unknown electrical load is activated, the high voltage present on the controller's output pins during operation also presents a fire hazard.

• Inability to Identify Power Sources – The inability of a PBT controller to identify its output's connection to a power source (such as AC power adapters, batteries, car power, or generators) represents a real safety risk, so the power supply contained in the PBT driver competes with the power supply external. Interconnecting two different power supplies can result in excessive currents, voltages, power dissipation, or uncontrolled oscillations that can damage the external power supply, the PBT driver, or both.

• Inability to control or limit the output current of the controller - connecting a shorted load, such as a damaged pad, a short cable, or any load that has a high input current (such as a motor) presents a high current hazard. and possibly a fire hazard. Inductive loads like solenoids can also momentarily create excessive voltages that damage low voltage components.

• Inability to detect batteries connected to the output of a PBT system - Connecting a battery pack to the output of a PBT system has the potential to damage the battery pack, accidentally charge the battery with the wrong charging conditions, and result in overvoltage, overcurrent, or overheat conditions in electrochemical cells. Improper charging of wet chemical or acid batteries has the potential for acid or electrolyte leakage. Improper charging of lithium ion batteries can cause overheating, fire, and even explosion.

• Inability to detect overheat conditions on LED Pads - Overheating an LED Pad risks patient discomfort and burns, pad damage, and in extreme cases, the possibility of fire.

• Inability to identify LED configuration within an LED pad – Unable to identify series-parallel array configuration of LEDs in an LED pad, PBT controller unable to determine if pad is compatible with PBT system or even if LED operation is possible. For example, too few LEDs connected in series can damage LEDs with too much voltage. Too many LEDs connected in series will result in dim or no lighting. Too many parallel strings of LEDs can cause excessive total pad current and consequently overheating, as well as large voltage drops across the interconnects, poor light uniformity across an LED pad, and possible damage to the LED conductive traces. the PCB.

• Inability to identify the types of LEDs contained within an LED pad – unable to detect what wavelength LEDs are on a pad, a PBT system has no means of matching their programming schedules. treatment with the LED array or to select the correct wavelength LEDs for each. specific waveform in the treatment protocol. • PBT driver outputs are limited to a fixed number of control signals – With only one or two control signals per output, current PBT drivers are incapable of driving three, four, or more different wavelengths of LEDs within the same pad with different excitation patterns. • Limited Mobility – In today's medical grade PBT systems, connecting a central PBT controller to the LED pads requires cable connections. While these connected PBT systems are generally acceptable in hospital applications (and possibly clinical settings), in military, paramedical, and consumer applications it is not useful to limit mobility with cables or wires.

• Incapable of waveform synthesis – PBT systems lack the technology to drive LEDs with any waveform other than square wave pulses. Pulsed square wave operation limits LED lighting patterns to one frequency operation at a time. Since pulse rate affects energy coupling to specific tissue types, a single-frequency PBT system can only optimally treat one tissue type at a time, extending required therapy time and patient/insurance cost. . The analysis also reveals that square wave pulses waste energy, producing harmonics that are not necessarily beneficial for therapy. LED unit using sinusoids, chords, triangle waves, sawtooth waveforms, noise bursts, or audio samples requires complex waveform synthesis within the LED pad. Although host PBT drivers must have sufficient computational power to synthesize such waveforms, the ability is not beneficial because the signal cannot be delivered over long cables without suffering significant waveform distortion. Unfortunately, the LED pads cannot perform the task. Using cheap discrete components, today's LED pads are incapable of any waveform synthesis, not to mention that the communication protocols needed to remotely select or change the synthesized waveform do not exist.

• Distribution of New LED Driver Algorithms – Current PBT systems lack the ability to download software updates from a database or server to fix software bugs or install new treatment algorithms.

• Inability to capture and record real-time patient biometric data – Current PBT systems lack the ability to collect biometric data such as brain waves, blood pressure, blood sugar, blood oxygen, and other biometric data during a treatment or capacity to integrate this collected data into the treatment file record.

• Inability to collect real-time images of the treatment area – Current PBT systems lack the means to measure or image tissue during treatment. The systems also lack the ability to store still and video images or to match the images to the treatment time of a PBT session.

• Inability for users ( clinicians) to create new treatment algorithms: Current PBT systems lack the ability for users, such as clinicians or researchers, to create new algorithms or combine existing treatments to form specific complex therapy treatments, for example, optimize an excitation sequence to activate injected stem cells (useful for accelerating stem cell differentiation and reducing rejection risks).

• Electronic Documentation Distribution – Current PBT systems cannot distribute or update any documentation electronically. It would be beneficial if the distribution of FDA notices or rulings, as well as errata and updates to PBT therapy and operating manuals, treatment guidelines, and other documentation could be provided electronically to all users of the PBT system. Currently, this capability is not available on any medical device.

• Treatment Tracking – Current PBT systems cannot track treatment usage history, capture system usage in a treatment record, and upload the treatment record to a server. Lacking real-time treatment records via network connectivity, the widespread commercial adoption of PBT systems by physicians, hospitals, clinics, and spas is problematic. Without uploaded usage logs, today's PBT systems cannot support revenue sharing leasing business models because the les sor is unable to verify the Headquarters system usage file. Similarly, hospitals and clinics cannot confirm the use of PBT systems for insurance audits and fraud prevention. In pay-as-you-go SaaS (Software as a Service) payment models, the PBT service agent cannot confirm a customer's usage history.

• Electronic Prescribing – Currently, no physical medicine device, including PBT systems, is capable of securely transferring and distributing prescriptions on a medical device.

• Remote Disablement – Today, no PBT system is capable of disabling device operation in the event of non-payment or theft to stop black market trading.

• Location Tracking – Today, no PBT system is capable of tracking the location of a stolen PBT system to track down the thieves.

• Secure Communication – Since current PBT systems use electrical signals instead of packet-based communication to control LED pads, hacking and direct measurement of communication between a host PBT system and LED pad is trivial and lacks security. some. Furthermore, PBT systems today lack any provision for Internet communication and security methods necessary to prevent content piracy and thwart identity theft in accordance with HEPA regulations. In the future, encryption alone is expected to be inadequate to secure data communication over the Internet. In such cases, connectivity to hyper-secure private networks will also be required.

In summary, the architecture of current PBT systems is completely outdated and requires a completely new system architecture, new control methods, and new communication protocols to facilitate an effective, flexible, versatile, and safe solution for providing photobiomodulation therapy.

SUMMARY OF THE INVENTION

In the photobiomodulation therapy (PBT) process of this invention, patterns (eg, pulse sequences of square waves, sine waves, or combinations thereof) of electromagnetic radiation (EMR) having one or more wavelengths are defined. , or spectral bands of wavelengths, are introduced into a living organism (for example, a human or an animal) using a distributed system that comprises two or more distributed components or "nodes" that communicate using a bus or transceiver to send instructions or files between constituent components. The radiation is typically within the infrared or visible portions of the EMR spectrum, although ultraviolet light can sometimes be included.

Single wavelength EMR can be used, or the pattern can include EMR having two, three or more wavelengths. Rather than consisting of radiation of a single wavelength, EMR can include spectral bands of radiation, often represented as a range of wavelengths centered on one wavelength. center, for example, A ± AA. Pulses or waveforms may be separated by spaces, during which no radiation is generated, the trailing edge of one pulse or waveform may temporarily coincide with the leading edge of the next pulse, or the pulses may overlap such that the radiation of two or more wavelengths (or spectral bands of wavelengths) can be generated simultaneously.

In one embodiment, the distributed PBT system's components comprise a PBT controller and one or more smart LED pads that communicate using a one-way serial data bus sending data, files, instructions, or executable code from the PBT controller to the smart LED pads. In a second embodiment, the components of the distributed PBT system comprise a PBT controller and one or more smart LED pads that communicate via a bi-directional data bus or a transceiver through which the PBT controller can send data, files, instructions, or executable code. to smart LED. pad, and conversely, the smart LED pad can return data to the PBT controller related to the operating status of the pad or patient condition, including LED pad configuration data, program status, fault conditions , skin temperature or other sensor data. Another sensor may include two-dimensional temperature maps, two-dimensional or three-dimensional ultrasound images, or may comprise biometric data such as pH, humidity, blood oxygen, blood sugar or skin impedance, etc., which in turn can be optionally used to change the treatment conditions, that is, to operate in a closed biofeedback loop.

In one embodiment, the EMR is generated by light emitting diodes (LEDs) arranged in series "strings" connected to a common power source. Each string of LEDs may comprise LEDs designed to generate radiation of a single wavelength or band of wavelengths in response to a defined constant or time-varying current. The LEDs may be embedded in a flexible pad designed to fit snugly against the skin surface of a human body, allowing the target tissue or organ to be exposed to a uniform pattern of radiation. Power can be supplied to each smart pad from a cable connecting the LED pad to the PBT driver, or alternatively the LED can be supplied from a separate power source. In an alternative embodiment, semiconductor laser diodes can be used instead of LEDs configured in an array to create a uniform pattern of radiation, or alternatively mounted on a handheld wand to create a small point or area of concentrated radiation.

In the distributed PBT system described in this document, each of the LED strings is controlled by an LED driver, which in turn is controlled by a microcontroller contained within the smart LED pad. The LED pad microcontroller communicates with another microcontroller or computer comprising the PBT controller via a communication bus, which may include wired connectivity such as USB, RS232, HDMI, I2C, SMB, Ethernet, or proprietary formats and protocols. communication methods, or may alternatively, comprise wireless media and protocols including Bluetooth, WiFi, WiMax, cellular radio using 2G, 3G, 4G/LTE or 5G protocols, or other proprietary communication methods.

Using a display, keyboard, or other input device connected to the PBT controller, a physician or clinician can select the particular algorithm (process sequence) that is appropriate for the condition or disease being treated. Instructions are then communicated from the PBT controller via the wired or wireless data bus to one or more smart LED pads that tell the pad's microcontroller when to start or stop a PBT treatment and specify which treatment to perform.

In a data stream embodiment, the PBT controller sends a stream of data packets specifying LED drive waveforms including when an LED is told to conduct current and the magnitude of the current. the current to drive. The flow instructions sent by the controller are selected from a "pattern library" of algorithms, each of which defines a particular processing sequence of pulses or waveforms from the EMR generated by the LED strings. Upon receiving the data packets via the data bus, the smart LED pad stores the instruction in memory, then starts "playing" the streaming data file, that is, it drives the LEDs according to the received instructions . During streaming playback, bus communication from the PBT Controller to the Smart LED Panel may be interrupted to accommodate system security checks or to allow the Smart LED Panel to report its status or upload sensor data to the PBT Controller.

Unlike prior art PBT systems, in the described distributed PBT system, the PBT controller does not constantly send instructions to the smart LED pads. During intervals when the PBT Controller is silent, either listening to the bus or receiving data from the Smart LED Pads, each Smart LED Pad must operate autonomously and independently of the PBT Controller and the other LED Pads connected to it. data bus or communication. grid. This means that the PBT controller must send enough data to the smart LED pad to be stored in the pad's memory buffer to support seamless LED playback operation until the next data file can be delivered.

In another embodiment, the PBT controller delivers a complete playback file to the smart LED panel that defines the entire execution sequence of a PBT treatment or session. In this method, the file is delivered before playback starts, ie before processing is executed. As soon as the file is loaded into the Smart LED Pad's memory, the local microcontroller built into the pad can execute playback according to the file's instructions. The transferred replay file may comprise (i) an executable code file that includes the entirety of all LED activation waveform instructions, (ii) a passive replay file that defines the treatment durations and settings to be interpreted by executable code comprising LED rendering software, or (iii) data files comprising waveform primitives which are subsequently combined in a manner prescribed by the LED pad microcontroller to control the LED lighting pattern and executing a treatment or PBT session.

In the last two examples, the executable code needed to interpret the playback file, ie the Player LED, must be loaded into the Smart LED before playback begins. This LED Player can be loaded onto the LED Smart Pad at the time a user instructs the PBT Controller to start therapy, or it can be loaded onto the Smart Pad at an earlier date, for example when the LED Pad is programmed during manufacturing or at that time. the PBT controller turns on and establishes that the smart LED pad is connected to the local area network of the controller. In cases where the LED player file is pre-loaded onto a smart LED pad and stored in non-volatile memory for extended periods, the distributed PBT system should include provisions to check whether the loaded software is still up to date or has been upgraded. become obsolete. If the system detects that the LED player is up to date, the LED playback can start immediately. Alternatively, if the PBT controller detects that the LED player is outdated, expired, or simply not up to date, the PBT controller can download the new executable code from the LED player either immediately or by first obtaining user approval. In some cases, processing with outdated LED player executable code may cause incorrect playback or system malfunction. In such cases, the PBT controller may forcibly suspend its operation of the smart pad LED player until the software download and update is executed.

The ability of an LED pad to function independently and autonomously for a defined time distinguishes the LED pad as "intelligent" compared to passive LED pads. The passive, contrasting, LED pads they are limited to responding only to the real-time signals sent from the PBT controller, where any break in communication will immediately result in a break in the operation of the LED pad, affecting the LED pulse train or waveform. In other words, the bus communication between the PBT controller and one or more smart LED pads can be thought of as a packet-switched local area network (LAN).

Another key feature of the revealed distributed PBT system is its autonomous security systems: protection and security functions that operate on each smart LED pad independently of the PBT controller. Specifically in network-connected professional medical devices, security systems must continue to function without failure even when network connectivity is lost. As a key feature of this invention, during operation, each smart LED pad regularly executes a safety related subroutine to ensure that the software is operating normally and that dangerous conditions do not exist. The SE smart LED pad's built-in protection features include a software related “blink timer” sub routine, a watchdog timer, surge protection, LED current balance, and overheat protection. Autonomous security features involve firmware comprising the smart LED pad's local operating system (referred to herein as LightPadOS) stored in non-volatile memory and executed by the embedded microcontroller present within each smart LED pad.

Upon receiving an instruction to start therapy, the LightPadOS for a specific pad starts a software timer and at the same time resets and starts a hardware counter on the microcontroller. The LightPadOS then launches the executable code to perform a PBT treatment executed as a streaming data file or as an LED player (playing a specific playback file) in sync with a program-forward counter. The program counter advances at a defined frequency as defined by either a shared system clock or a specific precision time reference from one or more Smart LED Pads. Such time references can be established using an RC relaxation oscillator, an RLC resonant tank oscillator, a crystal oscillator, or an oscillator based on a micromechanical machine. In this way, pulses with nanosecond precision can be used to synthesize square wave pulses, sine waves, and other waveforms that vary in frequency and duration. The synthesized waveforms are used to drive variable waveform LED strings in selected patterns according to defined algorithms.

During program execution, both the software blink timer and the hardware-based watchdog timer continue to count in synchrony with the program counter time base. When the blink timer reaches a certain predefined time (referred to here as blink interval), for example 30 seconds, the software timer generates an interrupt signal sent to the local control of the LightPadOS pad which suspends the treatment program counter and begins an “interrupt service routine” or ISR. The ISR then performs cleaning functions, which may include reading the temperature from one or more sensors on the smart LED pad, sending the temperature data through the transceiver to the PBT controller, and simultaneously compare the highest measured temperature with a defined range If the temperature exceeds a warning level, a warning flag is also generated and communicated to the PBT controller as a request for the system to take some action, for example to reduce the LED duty cycle (on time per cycle) to lower the pad temperature or to discontinue treatment.

However, if the highest measured temperature exceeds a predetermined safety threshold, the Smart LED Pad immediately suspends execution of the treatment program and simultaneously sends a message via the transceiver to the PBT controller. Unless the PBT is reset, the Overheat Smart LED Pad will remain off indefinitely. Thus, if an overheat condition occurs while the PBT controller is unavailable or malfunctioning, or if the network or communication bus is busy or unavailable, the default condition is to stop treatment.

During ISR, the Smart LED Pad can perform other safety tests, for example, checking for excessive input voltages as a result of a power supply failure, excessive currents as a result of an internal pad short, or detecting moisture. excessive resulting from sweat or water in contact with the smart LED. pad, possibly resulting in a missing or improperly applied sanitary barrier between the patient and the LED pad. In either case, the malfunctioning smart LED pad first suspends operation and then sends a message to the PBT controller informing the distributed system of the failure. In such a case, the other LED pads can continue to function independently (even if one pad has stopped working) or alternatively, all smart LED pads can be turned off simultaneously (either by the PBT controller or via direct pad-to-pad communications). ). After the ISR is complete, the control returns to performing the PBT treatment by resetting the program counter, resetting the software blink timer, and resetting the watchdog timer.

In the event of a software execution failure, either in the LED playback executable code or in the ISR subroutine, the program counter will not resume operation and the blink timer will not be reset or reset. If the watchdog timer reaches its full count without resetting (for example, at 31 seconds) without resetting, then software execution has failed. A watchdog timer instantly generates an interrupt flag that suspends program execution on the offending LED pad and sends a fault message to the PBT controller and, optionally, the other LED pads. As such, a software failure always defaults to a non-operational state for the malfunctioning LED pad to ensure patient safety even in the absence of network connectivity.

Apart from the standalone security features, in another embodiment, the described distributed PBT system includes centralized protection of the networked components managed by the PBT controller. Specifically, the PBT operating system that runs on the PBT driver, referred to herein as LightOS, includes a number of protection provisions including the ability to detect whether a component connected to the network or communication bus is a component. authorized or a fraud. If a user attempts to connect a light panel or other component to the PBT controller's network that cannot pass a prescribed authentication process, the component will be denied network access. The PBT controller's LightOS operating system can prohibit unauthorized access in a variety of ways, including shutting down the entire distributed system until the offending device is removed, not sending any data packets to the rogue device's IP address, or encrypting commands so that they are not recognized by the unauthorized component.

To effect multi-layer secure communication in the disclosed distributed PBT system, the PBT Controller Operating System (LightOS) and the Smart LED Pads Operating System (LightPadOS) comprise parallel communication stacks using consistent protocols and shared secrets not discernible for a device operator, hackers or unauthorized developers. As such, the distributed PBT system functions as a protected network communication with the ability to enforce security at any number of communication layers, including data link layer 2, network layer 3, network layer 4, transport, session layer 5, presentation layer 6, or application layer 7. For example, a numerical code installed and cryptographically hidden in both a PBT controller and a smart LED pad, i.e. a shared secret, can be used to confirm the authenticity of a network-connected smart LED pad without ever divulging the key. . In an LED panel validation method executed on the data link layer 2, the controller PBT passes a random number to the smart LED panel through the network or communication bus. In response, the microcontroller in the LED pad decrypts its copy of the shared secret key (numeric code), merges it with the received random number, then performs a cryptographic hash of the concatenated number. The smart LED pad then openly returns the cryptographic hash value over the same transceiver link.

At the same time, the PBT controller performs an identical operation by decrypting its own copy of the shared secret (numerical code), fusing it with the generated random number it sent to the LED panel, and then performing a cryptographic hash on the concatenated number. The PBT controller then compares the received and locally generated hash values. If the two numbers match, the pad is authentic, that is, it is "authorized" to connect to the network. The aforementioned authentication algorithm can be executed on any layer 1 PHY and/or layer 2 data-link connection over any data bus or packet-switched network, including USB, Ethernet, WiFi, or cellular radio connections. In the case of a WiFi connection, the data link can also be established using WPA2, a WiFi Protected Access Protocol.

For 'admin' and security tracking purposes, the authorization date and time (and, where available, GPS location) of the authenticated component is stored in non-volatile memory and optionally uploaded to a server. The benefit of employing secure communication and AAA (authentication, authorization, management) validation of all connected components in the distributed PBT system is crucial to ensuring security and protecting against the intentional connection of uncertified and potentially insecure imposter devices. In this way, imposter devices cannot be controlled by the distributed PBT system. AAA validation also protects against accidental connection of devices that are not designed to function as part of the PBT system, such as lithium-ion battery packs, unapproved power supplies, speakers, disk drives, motor controllers, lasers, etc. high power class III and IV, and other potential hazards not related to the PBT system.

The security of distributed PBT system using a packet-switched network (such as Ethernet or WiFi) can also be improved using dynamic addressing at network layer 3 and dynamic port assignment at data transport layer 4. In operation of a PBT controller not connected to the Internet or any other local area network, the PBT controller generates a dynamic IP address and a dynamic port address, then broadcasts the address to the other devices connected to the network to which the pads Smart LEDs respond with their own dynamic IP addresses and their own dynamic port addresses. In the event that the distributed PBT system is in contact with a router or the Internet, a Dynamic Host Configuration Processor (DHCP) is used to assign dynamic IP addresses. Similarly, a remote procedure call (RPC) is used to perform dynamic port number assignment. Since dynamic IP addresses and dynamic ports change every time a device connects to a network, the cyber attack surface is reduced. Additional security of L yesterday-4 can be added using TLS 'transport layer security', IPSec security protocol, or other protocols.

Once the components of a distributed PBT system are established through layer 2 authentication and port address assignments, and layer 3 and layer-4 networking, the distributed PBT system is ready to execute the treatments. Once the PBT controller receives a 'start' command from the user, the PBT processing begins with an exchange of encryption keys or digital certificates between the PBT controller and the network-connected smart LED pads to establish a layer-5 session. . Once the session is opened, the PBT controller and smart LED pad maintain their secure link during file and command exchange until treatment is completed or terminated. Additional network security can be realized using either presentation layer 6 or application layer 7 encryption.

As revealed, the network-connected distributed PBT system functions as a single unified virtual machine (VM) capable of reliably and safely performing photobiomodulation therapy using multiple smart LED pads offering • No waveform distortion resulting from cable parasites • Bi-directional communication between the PBT controller and the smart LED pad

• Ability to detect a misconnection short of multiple pads • Ability to identify approved LED pads or certified manufacturers • Ability to identify a connected device as a smart LED pad

• Ability to identify power sources and to control their operating voltage

• Ability to control and limit the driver's LED current

• Ability to detect batteries and prevent their connection to the output of a PBT system

• Ability to detect over-temperature conditions on the LED pads

• Ability to identify the LED pattern within an LED pad.

• Ability to identify LED types and configuration contained within a smart n LED pad

• Ability to independently control multiple outputs • Ability to perform distortion-free waveform synthesis within a smart LED pad

• Ability to distribute new LED driver algorithms to smart LED pads

• Ability to capture and record patient biometric data in real time

• Ability to collect real-time images of treatment area • Support the ability of users (physicians) to create new treatment algorithms.

• Ability to support the electronic distribution of documentation.

• Ability to monitor treatment

• Ability to manage the distribution of electronic prescriptions.

• Ability to support a remote control connected to the network

• Ability to track the location of PBT systems • Ability to perform secure communication between components

In another embodiment, the described distributed PBT system comprises a three-stage waveform generation involving digital waveform synthesis, PWM pulse generation, and a dynamic multiplexed multi-channel LED driver capable of producing square, triangle, and square waveforms. sawtooth and sinusoidal. Waveforms can comprise a single periodic function or a string of multiple frequency components.

In another embodiment, the described waveform generator can generate chords based on a prescribed key and frequency scale, eg, a chord comprising two, three, or four different frequencies, including noise filtering. LED driving waveforms can also be produced from audio samples or by combining chords from scalable audio primitive waveforms of variable resolution and frequency. Waveforms can be stored in libraries based on synth parametric waveforms, PWM waveforms, and PWM chords, including major, minor, diminished, augmented, octave, and inversion chords. The software-controlled LED driver includes I/O mapping (multiplexing), dynamic current control, and various programmable dynamic current references.

In another embodiment, a distributed PBT system comprises multiple sets of smart LED pads controlled from a multi-channel PBT control station. centralized. An optional WiFi PBT remote control is included for easy local start-start and pause control. In yet another embodiment, the PBT controller comprises an application running on a mobile device or smartphone that controls the smart LED pads. The mobile app includes intuitive UI/UX control and biofeedback screen. The app can also connect to the Internet or a PBT server as a therapy database. In another embodiment, the PBT system comprises a set of fully autonomous LED pads programmed via the network.

The distributed PBT system can also be used to control mouthpiece-mounted LEDs to combat gum inflammation and periodontal disease or to activate individual earpiece-mounted LEDs inserted into the nose or ears to kill bacterial inflections in mouthpieces. sinus cavities. A variation of the individual LED buttons can be used as "dots" placed on acupuncture points.

The aforementioned distributed PBT system is not limited to activation of LEDs, but can be used to activate any energy emitter located next to a patient to inject energy into living tissue, including coherent light from a laser, or emit fields time-varying magnetic (magnetotherapy), electric microcurrents (electrotherapy), ultrasonic energy, infrasound, far infrared electromagnetic radiation, or any combination thereof.

In one such embodiment, a handheld LED or laser wand comprises a large area main unit and pivoting handle, an integral temperature sensor, a battery charger, a step-up (boost) voltage regulator, and an integral security system. as a proximity switch. In yet another embodiment, a magnetotherapy device comprises a coil implemented on a multilayer printed circuit board used to generate time-varying magnetic fields. The magnet therapy device can be implemented on a pad or on a wand. Magnetotherapy, used to reduce inflammation and pain in joints m a and be operated independently or in combination with PBT.

Another version of the manual wand includes a modulated voice coil that works like a vibrator, applying pressure to muscles and tissue at infrasonic frequencies, i.e. below 10 Hz, similar to massage therapy but with deeper penetration. Infrasound therapy, which is used to reduce muscle relaxation and improve flexibility and range of motion, can be operated independently or in combination with PBT.

In another embodiment, an ultrasound therapy device comprises a flexible PCB with one or more modulated piezoelectric transducers in the 20 kHz to 4 MHz ultrasound band. The piezoelectric transducer pad may also include pulse-modulated LEDs in the audio spectrum. . In a combined device app Ultrasound-LED, ultrasound is employed to break up scar tissue with PBT used to improve circulation and remove dead cells thereafter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGURE. 1 illustrates a PBT system operating under the control of a therapist. FIGURE. 2 illustrates the photobiomodulation of mitochondria.

FIGURE. 3 illustrates the optical absorption spectra of various biomaterials.

FIGURE. 4 A contrasts the differences between photo-optic therapy and photobiomodulation therapy.

FIGURE. 4B illustrates photochemical stimulation of intracellular organelle mitochondria by combined wavelength.

FIGURE. 5 represents a distributed PBT system with an active LED pad. FIGURE. 6 A is a schematic representation of a PBT system with passive LED pads using current limiting resistors.

FIGURE. 6B is a schematic representation of a PBT system with passive LED pads using current control.

FIGURE. 7 is a network description of a PBT system with active LED pads using only layer-1 physical communication (PHY).

FIGURE. 8 is an equivalent circuit of a communication cable and its impact on electrical signals.

FIGURE. 9 is an iconic representation of the interconnection of a photobiomodulation therapy system with unqualified or inappropriate electrical accessories or LED pads.

FIGURE. 10 depicts a photobiomodulation therapy system that activates different LED pads with a common set of electrical signals.

FIGURE. 11A illustrates an incorrect "output shorting" connection of two PBT LED system outputs to a common LED pad.

FIGURE. 11B illustrates a short output connection that drives strings of red LEDs with more than one competing control signal.

FIGURE. 11C illustrates a shorted output connection that simultaneously drives the NIR and Red LEDs on the same LED pad with overlapping or simultaneous control signals.

FIGURE. 11D illustrates the power output waveforms for a shorted output connection that simultaneously drives the NIR and Red LEDs on the same LED pad with overlapping or simultaneous control signals.

FIGURE. 12 is a PBT system that lacks temperature sensing, protection, or feedback.

FIGURE. 13 represents a distributed PBT system with an active LED pad. FIGURE. 14 is a schematic illustration of a distributed PBT system with a smart (active) LED pad.

FIGURE. 15 is a network illustration of a PBT system with smart ("active") LED pads using an OSI 3-layer stack.

FIGURE. 16 is a flowchart of an LED pad authentication sequence.

FIGURE. 17 illustrates a block diagram of an active LED pad with identity data recording.

FIGURE. 18 illustrates a block diagram of an active LED pad with LED configuration register.

FIGURE. 19 is a schematic representation of an n exemplary LED matrix and drive electronics comprising three wavelength LEDs.

FIGURE. 20A is a schematic representation of a low side switched current control element or "current sink" that drives an LED array comprising "m" LEDs.

FIGURE. 20B is a schematic representation of a current sink-type switched low-side LED driver comprising an N-channel MOSFET and a current sense gate bias circuit with reference current input Iref.

FIGURE. 20C is a schematic representation of an example and low current type side of the LED driver implementation switching sink comprising a current mirror sensor, a transconducting NCE amplifier bias circuit with current input reference I ref and a transmission gate with digital input.

FIGURE. 21A is a schematic representation of an exemplary multi-channel current reference generator with DAC current trim resistor.

FIGURE. 21B is a schematic representation of an example and reference multi-channel current generator with DAC MOSFET gate useful current widths.

FIGURE. 21C is a schematic representation of an example and calculated multi-channel reference current generator with DAC and arithmetic-logic-input unit comprising target and calibration reference input current streams.

FIGURE. 22A is a schematic representation of a single sided high switched current- control element or "current source" driving a serial string of LEDs comprising LEDs "m".

FIGURE. 22B is a schematic representation of a current source type switched high-side LED driver comprising a P-channel MOSFET and a current sense gate bias circuit with reference current input (-Iref).

FIGURE. 22C is a schematic representation of an example and type of high side switching current supply LED driver implementation comprising a current mirror sensor, a transconductance amplifier bias circuit with current input reference (-I ^ref ) and a transmission gate with digital input.

FIGURE. 23A is a schematic representation of a high-side current control element or "current source" that drives an array of LEDs comprising LEDs "m" with a low-side N-channel MOSFET digital enable.

FIGURE. 23B is a schematic representation of a current-source-type high-side LED driver comprising a P-channel MOSFET and a current-sense gate-bias circuit with reference current input (-I ^ref ) that drives a current-sense gate bias circuit. LED string in series with a low-side N-channel MOSFET digital enable.

FIGURE. 23C is a schematic representation of an exemplary current source type high side LED driver implementation and comprising a current mirror sensor, a transconductance amplifier bias circuit with reference current input (-I ^ref ) that drives a string of LEDs connected in series with a low-side digital channel N-MOSFET enable.

FIGURE. 24 is a flowchart describing a master-slave, LED drive based data transmission.

FIGURE. 25 illustrates real-time data transfer to an LED pad via packet transfer over USB.

FIGURE. 26A illustrates a just-in-time or "JIT" sequential data transfer method for a flux-based LED drive.

FIGURE. 26B illustrates a transfer-ahead-and-change method for a current base unit LED.

FIGURE. 26C compares JIT versus the transfer-ahead-and-shift method of the LED unit.

FIGURE. 27 is a flowchart of LED pad stand-alone pad playback using unencrypted files.

FIGURE. 28 illustrates the storage of executable code files on an active LED pad.

FIGURE. 29A illustrates an exemplary n treatment protocol comprising three PBT "sessions" each constituting three sequential treatment algorithms.

FIGURE. 29B illustrates instances AND treatments, each illustrating an on/off LED control sequence of praises and durations.

FIGURE. 30 illustrates an Arndt-Schultz biphasic dose response model for PBT.

FIGURE. 31 illustrates a 4 layer serial bus based LightOS communication protocol stack.

FIGURE. 32 illustrates the preparation of encrypted packets from the PBT processing file.

FIGURE. 33 illustrates the preparation of encrypted packets from a PBT session file. FIGURE. 34 illustrates the active decryption and storage of the LED pad of an incoming encrypted packet.

FIGURE. 35 is a flowchart of LED pad standalone pad playback using post-transfer file decryption.

FIGURE. 36 illustrates the storage of ciphertext files on an active LED pad.

FIGURE. 37 is an LED pad stand-alone pad playback flowchart using on-the-fly decryption during playback.

FIGURE. 38 is a file comparison between bulk file decryption before playback and on-the-fly decryption during playback.

FIGURE. 39 illustrates downloading files from an LED player to an LED pad.

FIGURE. 40 is a flowchart describing the operation of a "waveform synthesizer" module.

FIGURE. 41 is a flowchart describing the operation of a "PWM player" module.

FIGURE. 42 is a flowchart describing the operation of an "LED driver" module.

FIGURE. 43 is a block diagram showing waveform generation using a waveform synthesizer, PWM player, and LED driver modules.

FIGURE. 44 is a block diagram showing details of the operation of the waveform synthesizer, including synthesis via a unit function generator or primitive processor.

FIGURE. 45 illustrates examples of unit function generated waveforms, including constant, sawtooth, triangle, sinusoidal, and sinusoidal string waveforms.

FIGURE. 46 is a functional description of a synthesizer summing node and autoranging operation used in waveform synthesis.

FIGURE. 47 illustrates examples of variable frequency sine waves and blended chords thereof.

FIGURE. 48A illustrates a countercurrent based sinusoidal synthesis system capable of blending chords over ten octaves with independent weighting and autorange functionality.

FIGURE. 48B illustrates chord synthesis of two sine waves using a counter-based sine synthesis system.

FIGURE. 48C illustrates chord synthesis of three sine waves using a counter-based sine synthesis system.

FIGURE. 49 is a block diagram of a counter-based sinusoidal chord synthesizer using a single sinusoidal primitive with 24-point angle resolution.

FIGURE. 50 is an example of chord synthesis of two sine waves using a single fixed resolution primitive.

FIGURE. 51 A is an example of three-sine wave chord synthesis using a single fixed-resolution sine primitive.

FIGURE. 51B illustrates exemplary sine waves and combined chords using a single fixed-resolution sine primitive that highlights quantization noise.

FIGURE. 52 A is an example of three sine wave chord synthesis using multiple scaled resolution sine primitives.

FIGURE. 52B illustrates exemplary sine waves and chords combined using multiple scaled resolution sine primitives to completely eliminate quantization noise.

FIGURE. 52 C is a comparison between the scaled resolution and fixed resolution sine wave synthesis of a combined chord of three sine waves.

FIGURE. 53 is a block diagram of a counter-based sinusoidal chord synthesizer using scaled resolution sinusoidal primitives and four clock scale ranges.

FIGURE. 54 is a block diagram of a universal primitive sinusoidal chord synthesizer applicable to any resolution sinusoidal primitive.

FIGURE. 55A illustrates the UI/UX interface for establishing a global key for sine-chord synthesis based on equal musical scales and a fourth 8th note-based key.

FIGURE. 55B illustrates the UI/UX interface for setting a global key for sine and chord synthesis based on other scales and a fourth 8th note-based key.

FIGURE. 56 illustrates the UI/UX interface for setting a global key for sine and chord synthesis based on a custom frequency.

FIGURE. 57 A is a block diagram of an algorithmic chord constructor for triad/quadruple synthesis of musical chords (with an optional 1 octave note), including major, minor, augmented, and diminished chords.

FIGURE. 57 B illustrates the UI/UX interface for a custom triad chord builder with an optional 1 octave note.

FIGURE. 58 A illustrates signal compression in three-sine sum synthesis without autoranging function.

FIGURE. 58 B compares three-sine sum synthesized waveforms with and without autorange amplification.

FIGURE. 59 is a functional illustration of a PWM generator function used in the waveform synthesizer.

FIGURE. 60 illustrates examples of non-sinusoidal generated waveforms and their corresponding PWM representations.

FIGURE. 61 A illustrates the operation of the PWM player's chopping function. FIGURE. 61B illustrates a schematic functional equivalent of a pulse width modulator used in the PWM player.

FIGURE. 62 ill us Treats ab blocking diagram of the action of the LED driver .

FIGURE. 63 A illustrates the constitutive waveforms of a square wave generated by a PWM player with a duty factor of 50% and an average LED current of 10 mA.

FIGURE. 63B illustrates the constituent waveforms for a square wave generated by a PWM player with a duty factor of 20% and an average LED current of 10 mA.

FIGURE. 63 C illustrates the constituent waveforms for a square wave generated by a PWM player with a duty factor of 95% and an average LED current of 10 mA.

FIGURE. 63 D illustrates the constituent waveforms of a square wave PWM player generated with 50% duty factor and an average LED current of 10 mA subsequently stepping up to 13 mA.

FIGURE. 63 E illustrates the constitutive waveforms of a square wave generated by an LED driver with a duty factor of 50% and an average LED current of 10 mA.

FIGURE. 63F illustrates the constitutive waveforms of a sine wave generated by an ADC (Analog-to-Digital Converter) LED driver with an average LED current of 10 mA.

FIGURE. 63G illustrates the constitutive waveforms of an audio sample generated by a guitar string pluck LED driver ADC (analog-to-digital converter) with an average LED current of 10 mA.

FIGURE. 63H illustrates the constitutive waveforms of an audio sample generated by the ADC (analog-to-digital converter) of a cymbal crash LED driver with an average LED current of 10 mA.

FIGURE. 64A illustrates the constitutive waveforms of a PWM synthesized sine wave with an average LED current of 10 mA.

FIGURE. 64B illustrates the constitutive waveforms of a PWM synthesized sine wave with an average LED current of 10 mA which was later increased to 13 mA.

FIGURE. 64C illustrates the constituent waveforms of a PWM synthesized audio sample comprising a chord of sine waves with an average LED current of 10 mA.

FIGURE. 64D illustrates the constitutive waveforms of a PWM synthesized triangle wave with an average LED current of 10 mA.

FIGURE. 64E illustrates the constituent waveforms of a PWM synthesized audio sample comprising a guitar string pluck with an average LED current of 10 mA.

FIGURE. 64F illustrates the constituent waveforms for a PWM synthesized audio sample comprising a cymbal crash with an average LED current of 10 mA.

FIGURE. 65 illustrates the constitutive waveforms of a PWM synthesized sine wave with an average LED current of 10mA subsequently boosted to 13mA cut by a PWM player.

FIGURE. 66 illustrates downloading a playback file to an LED pad.

FIGURE. 67 illustrates an LED playback data file comprising a playback ID file, synthesizer parameter file, primitives file, PWM player file, LED driver file, and components thereof.

FIGURE. 68 is a schematic analog view of the firmware used to control the clock of the PWM player 0 ref.

FIGURE. 69 is comprises the communication stack for an Ethernet based distributed PBT system.

FIGURE. 70 comprises the communications stack for a WiFi-based distributed PBT system.

FIGURE. 71A is a block diagram of a WiFi communication enabled PBT controller for distributed PBT systems.

FIGURE. 71B is a block diagram of a WiFi communication enabled LED pad for distributed PBT systems.

FIGURE. 72 is a multi-user distributed PBT system and communications network. FIGURE. 73 comprises the communication stacks for a distributed cellular phone based PBT system.

FIGURE. 74 illustrates a distributed PBT system using a cell phone app and WiFi based control.

FIGURE. 75 is a UI/UX menu for PBT control using a mobile device application program.

FIGURE. 76 is a top and bottom cross-sectional view of a handheld PBT wand for LED or laser therapy.

FIGURE. 77 is a block diagram of a portable PBT wand for LED or laser therapy.

FIGURE. 78 is a bottom, cross-sectional view of a PBT wand eye-safety system for laser PBT using capacitive contact sensing.

FIGURE. 79 is a schematic of a laser PBT eye safety system using capacitive contact detection.

FIGURE. 80 is a schematic of a distributed system laser PBT control circuit. FIGURE. 81A is a cross section, top view, and side view of a self-contained smart LED pad with an integrated switch.

FIGURE. 81B is a flowchart describing the program change sequence of a self-contained smart LED pad.

FIGURE. 82 is the cross section of a rigid flex PCB.

FIGURE. 83 is an explosion diagram of planar magnetism used in a magnetotherapy pad.

FIGURE. 84 is a side view of a flat magnet magnet therapy pad.

FIGURE. 85 is a top view of a flat magnet magnet therapy pad.

FIGURE. 86 is a schematic of a distributed system magnetotherapy control circuit.

FIGURE. 87 is a cross section of a magnetic therapy pad using discrete magnetism.

FIGURE. 88A is a magnetic therapy pad comprising an array of electromagnets.

FIGURE. 88B is a magnetic therapy pad comprising a series of electromagnets and permanent magnets.

FIGURE. 88C is a magnet therapy pad comprising an array of stacked hybrid electromagnet electromagnets and permanent magnets.

FIGURE. 88D is a magnetotherapy pad comprising a series of stacked permanent magnet electromagnets and hybrid electromagnets.

FIGURE. 89 is a portable magnetic therapy device compatible with a distributed system.

FIGURE. 90 is a plan view and a cross-sectional view of a U-shaped PBT periodontal mouthpiece.

FIGURE. 91 is a side view of the manufacturing steps for manufacturing a U-shaped PBT periodontal mouthpiece.

FIGURE. 92A is a side view of the manufacturing steps for making an H-shaped PBT periodontal mouthpiece.

FIGURE. 92B is a side view of a fabricated H-shaped periodontal PBT mouthpiece.

FIGURE. 93 shows the bonding process in the fabrication of an H-shaped PBT periodontal mouthpiece.

FIGURE. 94 illustrates the circuit diagram of a periodontal PBT nozzle.

FIGURE. 95 illustrates the circuit diagram of an ultrasonic PBT pad combined with H-bridge unit.

FIGURE. 96 illustrates the circuit diagram of an ultrasonic PBT pad combined with a current sink device.

FIGURE. 97 comprises perspective views of a combined ultrasonic PBT pad

DESCRIPTION OF THE INVENTION

In order to overcome the aforementioned limitations, the existing generation PBT systems face a completely new system architecture in required. Specifically, the generation of sine and chordal waveforms combining sine waves should occur in close proximity to the LEDs being driven to avoid significant distortion of the wiring waveform. Such design criteria forces to relocate the waveform synthesis, away from the PBT driver and inside the LED pad. To achieve this seemingly minor division of duties is in fact a significant design change and requires converting the LED pad from a component passive to an active system or "smart" LED pad. While a passive LED pad contains only an LED array, power sources, and switches, a smart LED pad must integrate a microcontroller, volatile and non-volatile memory, communication transceiver or bus interface, LED drive electronics, and the LED matrix. Due to the need for long wiring or wireless operation, the time reference for the microcontroller must also be relocated to the LED pad. Essentially, each smart LED pad becomes a small computer that, once given instructions, is capable of independently producing LED drive patterns.

So instead of using a centralized PBT controller that produces and distributes electrical signals to passive LED pads, the new architecture is "distributed," comprising a network of electronics that operate autonomously and lack centralized real-time control. This distributed PBT system, the first of its kind, requires the invitation of Smart LED Pads, a therapeutic light delivery system whereby the LED pads perform all the necessary calculations to generate dynamic LED excitation patterns and safely execute the LED activation accordingly. In distributed PBT operation, the role of the PBT controller is drastically reduced to that of a UI/UX interface, allowing the user to select treatments or therapy sessions from available protocol libraries and start, pause, or end treatments. This lack of central hardware control is virtually unheard of in medical devices because ISO13485, IEC and FDA regulations require, for safety reasons, the ability to control hardware at all times. As such, the implementation of effective security systems on distributed hardware of medical equipment requires a new and innovative approach where security functions must be carried out locally and communicated system-wide. Such a security protocol must be specified, designed, verified, validated, and documented in accordance with FDA design standards and international security standards.

Another implication of a distributed PBT system with smart LED pads is the replacement of electrical signal communication with command-based instructions comprising data packets. Such command-based communication involves the design and development of a private packet-switched communication network between distributed system components, tailoring digital communication to meet the unique and stringent requirements of medical device control. Packet routing, security, and data payloads must be designed to prevent hacking or system malfunction, and must carry all the information needed to perform all the necessary PBT operations.

Implementing a distributed PBT system with smart LED pads involves two sets of interrelated innovations. In this application, the operation of the smart LED pad is described, including time-based LED drive patterns delivered by streaming or file transfer. This disclosure also considers waveform generation on the pad through a three-step process of waveform synthesis, PWM player operation, and dynamic LED drive, as well as necessary security features. In the related US Application No. 16/377,192, entitled "Distributed Photobiomodulation Therapy Devices and Methods, Biofeedback and Communication Protocols Therefor," the hierarchical stack data communication and control protocol is disclosed.

In the distributed PBT systems described in this paper, LED playback can be controlled using a time-based instruction sequence (referred to as continuous transmission) or by command-based waveform generation and synthesis. In either case, the data packets carry the drive pattern of the LED digitally in their payload. In operation, through a graphical interface, a user or therapist selects a treatment or a PBT therapy session and agrees to start the treatment. The command is then packaged, i.e. prepared, formatted, compressed and stuffed into a communication packet and delivered via serial peripheral communication bus, LAN, broadband connection, WiFi, fiber or other media to one or more smart LED pads. Although the payload data carried in each data packet is digital comprising bits arranged as octets or hexadecimal words, the actual communication medium is analog, comprising differential analog signals, radio waves, or modulated light.

In wired communication, the communication bus typically uses electrical signals comprising analog differential waveforms modulated at a specific rate known as the symbol rate or baud rate (https://en.wikipedia.org/wiki/Symbol_rate) . Each symbol can comprise a frequency or a code of a defined duration. Detection of each sequential symbol is immune to distortions caused by reactive parasites in a cable or by noise sources, and thus overcomes all the problems associated with the transmission of digital pulse signals in prior art PBT implementations. . In WiFi communication, incoming serial data is divided and transmitted into small packets across multiple frequency subbands, known as OFDM, i.e. Orthogonal Frequency Division Multiplexing to achieve high symbol rate and low data rate. bit bug. Similar frequency division methods are used in Fiber Channel and DOCSIS communication to achieve high symbol rates. Because each transmitted symbol is capable of representing multiple digital states, the serial bus data bit rate, for Therefore, greater than the symbol rate of the media is. The effective bit data rate (https://en.wikipedia.org/wiki/List_of_device_bit_rates) of several of the most common serial and wireless communication protocols above 50 MB/s are summarized below for reference:

In response to a user's commands, the PBT controller converts the instructions into communication data packets, which are subsequently sent to all connected, qualified LED pads. The LED pads receive the instructions and respond accordingly, starting a therapy session or performing other tasks. Due to high-bandwidth communication, the user experience of the PBT system is that the treatment was instantaneous, that is, users perceive a real-time UI/UX response even though the system operation was actually performed. as a sequence of communication between devices and autonomous tasks. .

The described distributed PBT system involves multiple interacting components, each performing a dedicated function or functions within the decentralized system. The number of unique components integrated into the system affects the overall complexity of the system and impacts the sophistication of the communication protocol, that is, the "language" used in communication between devices. Various components of the disclosed distributed PBT system may include:

• A user interface comprising a central PBT controller or mobile application used to execute UI/UX based commands and send instructions over the communications network.

• Smart LED pads that perform dynamic photobiomodulation therapy treatments with local excitation pattern generation on the pad and waveform synthesis, and optionally with integrated sensors or imaging capability.

• Computer servers accessible via the Internet or private communication networks used to retain and distribute PBT treatments, sessions and protocols, or to upload patient response data, case studies or clinical trials and associated files (eg ., MRIs, X-rays, blood tests) .

• Optional therapeutic accessories, such as laser wands or ultrasound therapy pads.

• Optional biometric sensors (eg, EEG sensors, ECG monitors, blood oxygen, blood pressure, blood sugar, etc.) used to capture and upload patient samples or real-time data.

• Computer peripherals, including high-definition and touch screens, keyboards, mice, speakers, headphones, etc.

By combining or excluding various components in the PBT system, a variety of performance and system costs can be tailored for a wide range of users covering hospitals and clinics, and extending to individual users and consumers, spas, estheticians, sports trainers and athletes, as well as professional mobile apps for paramedics, police officers or military medics. Since PBT components use a voltage greater than 5 V, care is taken in the design described to prevent a user from accidentally connecting a USB peripheral to a high voltage (12 V to 42 V) connection or bus.

LED Control in Distributed PBT Systems

A basic implementation of a distributed PBT system, shown in FIGURE.

13 , includes three components: a PBT controller 120, a power supply 121, and a single smart LED pad 123 with an intermediate USB cable 122 . FIGURE. 14 illustrated A block diagram of an example and distributed PBT system^ application, including a PBT controller and transceiver bus 131, in eo smarter LED pads 337, a USB cable 136, and an external power supply 'brick' 132. Although power supply block 132 is shown as a discrete component in the illustration, in systems where the PBT controller and bus transceiver 131 use a hardwired connection to the smart LED pads 337, the power supply can be included inside the PBT controller and transceiver instead of using a separate component. As shown, the PBT controller and bus transceiver 131 includes a pC or MPU main microcontroller 134, an LCD touch screen 133, nonvolatile memory 128, volatile memory 129, a bus interface 135, and a clock 124 that operates on a system clock. 197 at a rate of 0sys. Clock and memory elements are shown separately from the main MPU 134, to represent its function and are not intended to describe a specific embodiment or partition of components. RTC real time clock (not shown) can also be included with the PBT 131 controller. RTC is an extremely low power consumption clock that runs continuously and synchronizes to international time standards or network time whenever possible.

The main MPU 134 construction may comprise a fully integrated single-chip microcontroller or microprocessor-based module, optionally containing the main system clock 124, bus interface 135, and portions of non-volatile memory 128 and memory. 129 volatile. Any number of partitions is possible including the use of various silicon integrated circuits (ICs), system-on-chip (SOC) integration, system-in-package (SIP), or as modules. For example, volatile memory 129 may comprise dynamic random access memory (DRAM) or static random access memory (SRAM). This memory may be fully or partially integrated within the main MPU 134 or may be realized by separate integrated circuits. Similarly, nonvolatile memory 128 may comprise electrically erasable programmable random access memory (E2 PROM) or "flash" memory, which may be fully or partially integrated within MPU 111. Within nonvolatile PBT 131 controller High-Capacity Data storage can also be accomplished using on-the-go storage media such as optical discs (CD/DVDs), magnetic hard disk drives (HDDs), and even network connections to cloud storage.

The role of non-volatile data storage ge 128 within the PBT 131 controller is multi-purpose including storage for the main operating system, referred to herein as LightOS, as well as for holding libraries of PBT treatment programs and sessions , usually stored in encrypted form for security reasons. Non-volatile memory 128 can also be used to capture treatment records, upload data from sensors and possibly retain treatment metadata. In contrast to its non-volatile counterpart, the role of volatile memory 129 in the PBT controller 131 is primarily that of notepad memory, holding data temporarily while calculations are performed. For example, when preparing a PBT session comprising a sequence of separate PBT processings, the encrypted processing algorithms must first be decrypted, assembled into a PBT session, re-encrypted, and then assembled into a communication packet ready for network transport. The volatile memory stores the data content during the assembly process of the communication package.

Another consideration in a distributed PBT system is the power distribution needed to power the PBT driver and LED pads. Options include the following:

• Power on the PBT controller using an internal power supply, then power the LED pads via the communication bus, • Power the PBT controller with an external power supply (brick), then power the LED pads via of the communication bus,

• Power the PBT driver using an internal power supply and power the LED pads using their own dedicated external power supply or supplies (bricks),

• Power the PBT controller with an external power supply (block) and the LED pads with their own dedicated external power supply or supplies (blocks).

In the example shown, the external power supply block 132 powers the entire PBT system, providing 5 V to the ICs and V ^led to the LED strings. USB cable 136 carries transceiver data symbols from PBT controller interface bus 135 and transceiver bus 131 to LED pad bus 338 interface 337. USB cable 136 also supplies power; specifically ground (GND), 5V, and V ^led to pad 337 smart LEDs, typically carried by copper conductors of lower resistance and thicker than the signal lines of the cable. LED pad 337 comprises a pC pad 339, an interface bus 338, volatile memory RAM (for example, SRAM or DRAM) 334a, a non-volatile memory (for example, EEPROM or flash) NV-RAM 334b, a memory reference clock time 333, LED drivers 335, and an LED array 140. The LED drivers include lude switched current sinks 140, 141, and others (not shown), typically one current sink for each LED string. LED matrix 140 includes a string of LEDs connected in string 142a to 142m to generate light of wavelength Ai, a string of series-connected LEDs 143a to 143m to generate light of wavelength A ² , and typically other strings of LEDs (not shown).

The memory within the LED pad 337 which includes both volatile memory 334a and non-volatile memory 334b is similar to the semiconductor memory used in PBT controller 131 except that the total capacity may be less and preferably consumes less power. The memory in the LED pad 337 must include semiconductor solutions due to the risk of mechanical shock and breakage of mobile media storage to integrate fragile data storage into the LED pad 337. Specifically, the virtual memory 334a (labeled as RAM) in The LED pad 337 can include dynamic random access memory (DRAM), or static random access memory (SRAM) that can be fully or partially integrated within the PC pad 339. In the LED pad, virtual memory is useful for storing data that is not they need to be retained except during use such as LED stream files, LED player files, and LED playback files. The advantage of only temporarily retaining the executable code needed to perform the current PBT treatment (and not the entire library of treatments), is that the memory capacity and cost within the LED pad 337 can be greatly reduced compared to that of the PBT controller 131. It also has the advantage of making it difficult to reverse engineer and copy the treatment programs because every time power to the LED pad 337 is removed, all data is lost.

Nonvolatile memory 334b may comprise electrically erasable programmable random access memory (E2PROM) or "flash" memory, which may be integrated in whole or in part within the pC pad 339. Nonvolatile memory 334b (labeled as NV-RAM) is preferably used to store firmware that does not change frequently, such as the operating system for the LED pad, herein referred to as LightPadOS, together with manufacturing data, including pad identification data, i.e. the LED pad ID register and manufacturing related LED configuration data. Non-volatile memory 334b may also be used to retain user records of treatments that have been performed. Low cost design for LED pads is another important economic consideration because a PBT driver is often sold with multiple LED pads, up to 6 or 8 per system. To reduce the overall cost of memory, it is beneficial to concentrate memory, especially non-volatile memory, in the PBT controller where there is a single device, and to minimize the memory contained within each LED pad, which occurs in multiple instances per system. . .

In operation, user command input on the LCD touch screen 133 of the PBT controller 131 is interpreted by the main MPU 134, which in response retrieves treatment files stored in non-volatile memory 128 and transfers these files across the USB bus interface 135, via USB cable 136 to bus interface 338 within LED smart pad 337. Treatment files, once transferred, are temporarily stored in volatile memory 334a. Pad pC 339, operating in accordance with LightPadOS operating systems stored in non-volatile memory 334b, then interprets treatments stored in volatile RAM 334a and drives LED drivers 335 according to the LED drive patterns of the selected treatment, where LED Matrix 336 illuminates strings of various wavelength LEDs in the desired manner. Because the PBT controller 131 and LED pad 337 operate using their own dedicated clocks 297 and 299, the distributed PBT system operates asynchronously at two different clock frequencies, specifically Osys and Opad respectively.

Since the two systems operate with different clock speeds, the communication between the PBT controller 131 and the LED panel 337 occurs asynchronously, that is, without a common synchronized clock. Asynchronous communication supports a wide range of serial bus communication protocols, including USB 136 as shown, or Ethernet, WiFi, 3G/LTE, 4G, and DOCSIS-3. Although a synchronous clock version of a distributed PBT system, ie one with a shared clock, is technically possible, synchronous operation offers no performance or efficiency advantage over its asynchronous counterpart. Also, high-frequency clock distribution over long cables is problematic due to clock drift, phase lags, pulse distortions, and more.

The architecture of FIG. 14 comprising a distributed PBT system that has two or more microcontrollers or computer "brains" represents a fundamental architectural change in PBT systems that otherwise typically comprise an all-in-one panel with integral controller or an active PBT controller that drives passive LED panels. It should be known to those skilled in the art that, rather than being a separate hardware device, a PBT controller may alternatively comprise a portable or desktop personal computer, a computer server, an application program running on a mobile device, such as a tablet or smartphone, or any other host device capable of running computer software, such as a game console, IoT device, or more. Examples of such alternative embodiments are shown throughout the application.

As the picture shows. 15 , the PBT operation can be interpreted as a communication sequence used to control hardware operations. Using an open system application or OSI representation, the PBT controller 120 contains a communication stack 147 comprising an application layer 7, a layer 2 data link, and a physical layer 1. Within the PBT controller 120, application layer 7 is implemented using a custom operating system for photobiomodulation referred to herein as LightOS. The instructions received by the LightOS user praise are transmitted to the layer 2 data link layer and together with the PHY layer 1 communicate via the USB protocol using USB 332 differential signals to the corresponding PHY layer - 1 of the communication stack 148 resident in smart LED pad 123. So, although the electrical signals comprise layer-1 communications, the USB data constructs behave as if the PBT controller and smart LED pad communicated on layer-2 with packets arranged in time as USB data "frames". Once the communication stack 148 receives a USB packet, the information is transferred to the application layer 7 run by a resident LED pad operating system referred to herein as LightPadOS. As long as the LightOS of the PBT controller and the LightPadOS operating system of the smart LED pad are designed to communicate and execute instructions in a self-consistent manner, the bi-directional link between the communication stacks 147 and 148 works as a virtual machine in the application layer, that is, the distributed layer. The device behaves the same as if it were a single piece of hardware.

To ensure that components can exchange information and execute instructions at a high level of abstraction, i.e. in the application layer and above, it is important that both operating systems LightOS and LightPadOS are developed with a parallel structure using the same methods. and encryption and security protocols. in any given layer. This criteria includes adopting common shared secrets, running predefined validation sequences (required for components joining the system's private network), running common encryption algorithms, and more.

To ensure that the two components can initiate communication and perform tasks, the PBT controller must first establish whether the LED pad is indeed a manufacturer-approved, system-validated component. This test, called "authentication" is shown in the flowchart in FIGURE. 16 in two parallel sequences, one occurring within LightOS operating as the “host”, the other occurring within LightPadOS operating as the “client”. As shown, upon completing the establishment of a physical U SB connection, i.e. insert 150, the controller's LightOS operating system begins a subroutine 151a called "LightPad Installation" while at the same time the LED pad's LightPadOS operating system starts a subroutine 151b. In the first step 152a, used to determine if the client is a power source (and reject it if it is), the PBT controller performs check 158 to verify if the USB D+ and D- pins are shorted. If these data pins are shorted, according to the USB standard, the peripheral is a power supply and not an LED panel, so the connection is rejected by the system, authentication is terminated, and LightOS informs the user that the peripheral is not is a valid component and to unplug it immediately. If the pins are not shorted, then the LightPadOS installation approval process can continue.

In steps 153a and 135b, the two devices negotiate the maximum data rate that each can reliably understand and communicate. Once the communication data rate is established, the symmetric authentication processes 154a and 154b begin. During "symmetric authentication", in step 154a, the LightOS first queries the LightPadOS to determine if the LED pad 123 is a valid manufacturer-approved device by verifying the data stored in the LED pad's identity data register 144 . In the reflected authentication process of step 154b, the LED pad 123 confirms that the PBT controller is a valid device with a valid manufacturing identification approved for use with the LED pad 123 . In this exchange, certain encrypted security credentials and manufacturer identification data, including the serial number, manufacturing code, and GUD identification number, change hands to ensure that both the PBT 120 driver and the LED Pad smart 123 are from the same manufacturer (or are licensed as approved device). If authorization fails, the LightOS host informs the user that the LED pad is not approved for use on the system and instructs the user to remove it. If LightOS cannot authenticate the LED panel 123, then the PBT controller 120 will break communication with the peripheral. Conversely, if the peripheral's LightPadOS cannot determine the authenticity of the PBT controller 120, then the LED pad 123 will ignore the instructions of the PBT controller 120. Only if symmetric authentication is confirmed can operation continue.

Any number of authentication methods can be used to establish a private network and approve a device's connection to the private network. These methods may involve symmetric or asymmetric encryption and key exchange, employing 'certificate authority'-based identity confirmation through the exchange of digital CA certificates, or exchanging cryptographic hash data to confirm that a device has the same shared secrets, which means it was produced by a qualified manufacturer. For example, a numeric code installed and cryptographically hidden in both a PBT controller and a smart LED pad, i.e. a shared secret, can be used to confirm the authenticity of a connected smart LED pad. to the network without even divulging the key. In one of these LED pad validation methods executed at data link layer 2, the PBT controller passes a random number to the smart LED pad via the network or communication bus. In response, the microcontroller in the LED panel decrypts its copy of the shared secret (numerical code), merges it with the received random number, and then performs a cryptographic hash operation on the concatenated number. The smart LED pad then openly returns the cryptographic hash value over the same transceiver link.

At the same time, the PBT controller performs an identical operation by decrypting its own copy of the shared secret (numerical code), fusing it with the generated random number it sent to the LED panel, and then performing a cryptographic hash on the concatenated number. The PBT controller then compares the received and locally generated hash values. If the two numbers match, the pad is authentic, that is, it is "authorized" to connect to the network. The aforementioned authentication algorithm can be executed on any PHY layer 1 and/or data link 2 connection over any data bus or packet switched network, including USB, Ethernet, WiFi or cellular radio connections. In the case of a WiFi connection, the data link can also be established using the WPA2 WiFi Protected Access protocol.

For 'admin' and security tracking purposes, the authorization date and time (and, where available, GPS location) of the authenticated component is stored in non-volatile memory and optionally uploaded to a server. The benefit of employing secure communication and AAA (authentication, authorization, management) validation of all connected components in the distributed PBT system is crucial to ensuring security and protecting against the intentional connection of uncertified and potentially insecure imposter devices. In this way, imposter devices cannot be controlled by the distributed PBT system. AAA validation also protects against accidental connection of devices that are not designed to function as part of the PBT system, such as lithium-ion battery packs, unapproved power supplies, speakers, disk drives, motor controllers, lasers, etc. high power class III and IV, and other potential hazards not related to the PBT system.

The security of a distributed PBT system using a packet-switched network (such as Ethernet or WiFi) can also be enhanced by dynamic addressing at network layer 3 and dynamic port assignment at data transport layer 4. In operation of a PBT controller not connected to the Internet or any other local area network, the PBT controller generates a dynamic IP address and a dynamic port address, then broadcasts the address to the other devices connected to the network to which the LED pads smart devices respond with their own dynamic IP addresses and their own dynamic port addresses. In the event that the distributed PBT system is in contact with a router or the Internet, a Dynamic Host Configuration Processor (DHCP) is used to assign dynamic IP addresses. Similarly, a remote procedure call (RPC) is used to perform dynamic port number assignment. Since dynamic IP addresses and dynamic ports change every time a device connects to a network, the cyber attack surface is reduced. Additional Layer 4 security can be added using TLS transport layer security, IPSec security protocol, or other protocols. Once the Smart LED Pad is connected to the network, additional information such as LED configuration data can be exchanged to authorize the component to function as part of the distributed PBT system.

In step 155a, the LightOS requests LED configuration information from the LED pad. In step 155b, the LightPadOS responds by relaying the information within the configuration register 145 of the LED panel 123 to the PBT controller 120. In addition to containing a detailed description of the LED matrix, the configuration file also specifies the manufacturer's specification for the maximum, minimum and target voltage required to power the LED strings in the matrix. The configuration file also specifies the required minimum current needed to drive the LEDs. If there is more than one LED pad connected to the output, LightOS requests and receives the same information from each connected LED pad, that is, it scans the entire network of connected devices.

In step 156a, the LightOS inspects the voltage requirements of each pad and compares the value to the output voltage range of the high voltage power supply. In PBT drivers using a high voltage power supply capable of a fixed VLED output voltage, the LightOS operating system will confirm that this voltage falls within the specified voltage range of each LED pad from Vmin to Vmax. The system will also check to confirm that the total current required for all "n" LED strings does not exceed the current rating of the supply (although this is generally not a concern, current checking is included to support low-power PBT device designs). cost to the consumer with limited power).

If in step 156a, the power supply's output meets the operating range of each connected LED pad, i.e., Vmin ^ V ^led ^ Vmax, then the PBT controller 120 will enable the high power supply. voltage V ^led . Optionally in step 156b the PBT controller 120 may inform the LED pad 123 of the chosen supply voltage which is stored in non-volatile memory 334b, documenting the last supply voltage supplied to the LED pad ( useful when inspecting for quality issues and field failures). In the case of If the PBT controller 120 employs a programmable voltage power supply, the LightOS operating system will select the best voltage based on the VOperating Target of the LED pad 123, as stored in the pad's LED configuration register 145. If the target voltages do not match, the LightOS operating system will choose a voltage for the V ^led as a compromise of the various reported target voltages. The term "high voltage" in this context means a voltage between 19.5 V minimum and 42 V maximum. Common supply voltages include 20V, 24V, or 36V. Even after the V ^led is enabled, this high voltage is not connected to the output jack or supplied to the LED pads until a treatment is selected and started. the therapy.

During the authentication process and in the case of user inquiries, the PBT controller 120 must request information about the manufacture of the LED pad. This data is beneficial for complying with medical device traceability regulations and debugging quality or field failures or processing return merchandise authorizations (RMAs). FIGURE. 17 illustrates an example of the type of product manufacturing information included in the "LED pad identity data record" 144 stored in the non-volatile memory 334b of the LED pad. This data may include the manufacturer's part number, manufacturer's name, unit serial number, a manufacturing code linked to a UN-specific pedigree or manufacturing history description, Globally Unique Device Identification (GUDID) specified by the US FDA.

[https://accessgudid.nlm.nih.gov/about-gudid] and, as appropriate, a related 510(k) number. The registry can also optionally include country-specific codes for importing the device and other customs-related information, for example, export license numbers or free trade certificates. This record is stored in non-volatile memory 334b during manufacture. The LED pad identity data record 144 also includes security credentials (such as encryption keys) used in the authentication process. Security credentials can be static as installed during manufacturing, or they can be dynamically rewritten each time the LED Pad authenticates, or alternatively rewritten after a prescribed number of valid authentications.

As described, during the authentication process, the PBT controller 120 collects information regarding the LED configuration of each connected LED panel. As the picture shows. 18 , the pad's LED configuration information is stored in the non-volatile memory 334b of the LED pad in the "LED configuration register" 145, written during the manufacturing process of the pad. The register stores the number of LED strings "n" and description information specific to the LEDs in the string, including the wavelength of LEDs A and the number "m" of LEDs connected in series in each string. In operation, this LED string information is used to match an LED treatment to a specific type of LED pad. For example, treatments designed solely to activate red LEDs will not work if an LED pad containing blue or green LEDs is attached. A user's UI/UX, i.e. menu options on the PBT controller's touch screen are adjusted according to the LED pads attached to the system. If the corresponding LED pads are not connected, the menu selections that require that type of pad are grayed out or hidden.

LED configuration register 145 is essentially a tabular description of the circuit schematic of an LED pad. Referring to a schematic of FIGURE. 19 depicting a part of an LED panel comprising an LED driver 335 with an LED driver circuit 160 and current sinks 161a to 161c, and an LED matrix 336, whereby

• String #1 in LED configuration register 145 describes string 162a comprising six series-connected near-infrared LEDs of wavelength A ¹ = 810 nm driven by current sink 161 carrying a current I ^led1 .

• String #2 in LED configuration register 145 describes string 163a comprising four series-connected red LEDs of wavelength A ² = 635 nm driven by current sink 161b carrying current ILED ² .

• String #3 in LED configuration register 145 describes string 164a comprising four series-connected blue LEDs of wavelength A ³ = 450 nm driven by current sink 161c carrying current ILED3.

• String #4 in LED Configuration Register 145 describes string 162b comprising six series-connected near-infrared LEDs of wavelength A ¹ = 810 nm driven by current sink 161a carrying current I ^led4 = I ^led1 .

• String #5 in LED configuration register 145 describes string 163b comprising four series-connected red LEDs of wavelength A ² = 635 nm driven by current sink 161b carrying current ILED5 = ILED2.

• String # ⁶ in LED configuration register 145 describes string 164b comprising four series-connected blue LEDs of wavelength A ³ = 450 nm driven by current sink 161c carrying current ILED6 = ILED3.

The foregoing is intended to exemplify, without limitation, the data format of the LED configuration register 145 and its corresponding schematic equivalent, not to represent a specific design. In particular, the number of LED strings "n" and the number of series-connected LEDs in a given string "m" contained within the LED pad are likely to exceed the numbers shown in this example. In practice, the number of LEDs in the various strings may be identical or may differ from string to string. For example, a pad of LEDs may include 15 strings comprising fourteen LEDs in series or 210 LEDs. These LEDs can be arranged in three groups of five LED strings each; one third NIR, one third red and one third blue. Each type of LED can be configured with 5 parallel strings and 14 series connected LEDs, that is, three 14s5p arrays.

LED configuration register 18 also includes the minimum and maximum operating voltage s for the LED pad. For proper operation of the LED, the power supply voltage V ^led must exceed the minimum voltage specification Vmin of the LED pad to ensure uniform illumination, but to prevent damage from excessive voltage or heat, the power supply voltage supply must not exceed the specified maximum voltage Vmax. In other words, the supply voltage value acceptable to power the LED pad must meet the criteria Vmin < V ^led ^ Vmax . The manufacturer's specified value of Vmin, stored in LED configuration register 145, is enforced on a statistical basis to exceed the highest voltage string of LEDs on the LED pad to ensure that as long as the criteria of Vmin < V ^led is maintained Higher string tension pads will still be fully lit when playing. If the Vmin voltage is specified too low, on some LED pads individual LED strings may be dimmer than others during treatment. Poor gloss uniformity negatively affects treatment efficacy by limiting the maximum and mean power of a PBT treatment and reducing the total energy (dose) of a treatment.

The highest voltage string on an LED pad is determined by both design and stochastic voltage variability in LED manufacturing. Each LED string consists of series-connected LEDs m, where each LED has its own unique forward driving voltage V Vfx , where x varies from 1 am , and where the total string voltage is the sum of these individual LED voltages I Vfx . The higher voltage could occur in a string comprising fewer series-connected LEDs with higher-voltage LEDs, or it could occur in a string comprising a greater number of low-voltage LEDs. A manufacturer of LED pads must employ statistical sampling data of LED forward voltages on a lot-to-lot basis to ensure that no LED pad is manufactured with an LED string voltage that exceeds the specified value of Vmin.

Although less precise, the power supply must be capable of supplying a minimum required average current Imin to light all the LEDs of a particular color (wavelength) at once. Generally, in a two-wavelength LED pad, 50% of the n strings of LEDs can be conducting at the same time. Whereas on a tri-color LED pad, it's likely that only one of the three LED wavelengths will light at a time to prevent overheating, a worst-case guess of 2/3rd (67%) of the n- sequences can be used to calculate the maximum current. The maximum current in LEDs conducting in continuous operation, in the worst case, will not exceed 30 mA per string, ie I ^led ^ 30 mA. Using this worst case assumption, a pad with n=30, 2/3rd of the strings lit at the same time, and with I ^led ^30mA will require a value of Imin=30(2/3)(30mA)= 600mA.

The Imax value specified in LED configuration register 145 is not a description of the maximum current flowing in the LEDs, but a description of the maximum safe current at 50% duty factor in the conductive pad traces. This current includes the current flowing in the LED pad's own LED strings plus any current carried through the LED pad to another LED pad. The specification is included to prevent operation of the pad where significant voltage drops occur in the LED pad power lines causing heating, malfunction, electromigration, or metal melting. One possible design guideline for the PCB of an LED pad is to use copper conductors capable of carrying more than twice their current rating, which means that the pad can safely carry its own current and the current of another LED at the same time. An additional design guard band of 5 = 25% is included as a safety margin. For example, if Imin = 600 mA, then using a 25% guard band, Imax = 2Imin (1+ 5) = 1500 mA . Configuration register 145 also includes the mirror ratio a used to convert the reference current Iref to the I ^led string current (or vice versa) according to the ratio I ^led = a Iref. If different relations are used for each channel, the table can be modified accordingly to include a ¹ , a ² , a ³ ... where I ^led1 = a ¹ Iren , I ^led2 = a ² Iret ² , and so on.

Referring again to FIGURE. 19 , the current I ^led1 in each string of NIR LEDs is controlled by a dedicated series-connected current sink 161a, which conducts on-state current in proportion to Iren. The current I ^led2 in each red LED string is controlled by a dedicated series-connected current sink 161b, which conducts the on-state current in proportion to I f The current I ^led3 in each blue LED string is controlled by a sink dedicated current 161c connected in series, which drives on-state current in proportion to I f The current control device connected in series with each string of LEDs can be connected to the cathode side as a current "sink" as shown in FIGURE. 20 A, or connected to the anode side of the LED string as a current "source" as shown in FIGURE. 22 A. In the current sink 161a and current source 200a implementations, the current LED I flowing in the current control device and LED string 165 or 201 respectively is controlled by a reference current analog Iref and a digital enable pulse En. The origin of these two signals in a distributed PBT system is discussed later in this application. (Note: The terms "current source" and "current sink" are well known in the art because they refer to a component that provides or receives ("sinks") a current whose magnitude is relatively unaffected by the magnitude of the current. voltage across the component.)

FIGURE. 20B illustrates an idealized current sink block representation diagram 161a showing a current sense and gate drive control element 166 of an n-channel MOSFET 167. The MOSFET (or alternatively a junction transistor bipolar) keeps the current controlled while sustaining the voltage across its drain to source terminals. Gate bias is provided by current sensing and control element 166 to maintain a constant current despite variations in drain-to-source voltage. FIGURE.

20C illustrates an implementation of the described constant current sink where the n-channel current mirror MOSFETs 168a and 168b sense the I current ^led . The ratio p of the gate width of MOSFET 168b to the gate width of MOSFET 168a is less than one, which means that the current in the current mirror MOSFET 168b is a small fraction of, but in a precise proportion, the current of charge in the current. mirror MOSFET 168a (I ^led ). This measured current, reflected by a current mirror comprising the p-channel unit MOSFET 169a and 169b having matched gate widths Wp , transforms the sense current from a ground current referenced to a 5 V supply current. with PI ^led magnitude reference. The differential “error” signal AIerr comprising the difference between Iref and PI ^led is then proportionally amplified and converted into a voltage V ^g by transconductance amplifier 170 and fed to the gate of the current control element, i.e. MOSFET 167, forming a closed loop feedback path. In operation, the transconductance gain G m results in a gate bias V ^g which drives its error signal AIerr to zero, thus forcing Iref = PI ^led . For convenience, we redefine p = 1/a so that we can express the transfer function of the current source as I ^led = a Iref. the same stream of reference is distributed to all LED strings within the same LED pad to ensure uniform brightness across all LEDs.

In the switched current sink, the digital inverter 171 and an analog transmission gate comprising the p-channel MOSFET 172 and the grounded n-channel MOSFET 173 perform the digital enable function of the En input, controlling the gate of the switched current. n-channel current sink MOSFET 167. Specifically, when the enable signal En is high, the output of inverter 171 is to ground, turning on the transmit gate 172 of the p-channel MOSFET and turning off the n-channel MOSFET 173. Because the p-channel has a gate connected to ground, it is biased in a fully on condition, that is, its linear region, and behaves like a resistor, passing the analog voltage V ^g from the output of the transconductance amplifier 170 to the n-channel current sink gate 167. Conversely, when the enable signal En is low (digital 0), the output of the inverter 171 connected to the p-channel transmit gate MOSFET 172 is biased to 5 V, and the n-channel is turned off, disconnecting the gate of n-channel current sink MOSFET 167 from the transconductance amplifier output 170. At the same time, the n-channel MOSFET 172 is turned on, pulling from the gate of the current sink MOSFET 167 to ground and turning off the current sink MOSFET 167, that is, I ^led = 0. In conclusion, the circuit of FIG. 20C represents a circuit for implementing a switching controlled current sink. When the current sink is enabled (En = digital 1), the current sink conducts and carries a controlled current I ^led = aIref. When the current sink is off (En = digital 0), the current sink is off and the I LED = 0.

Similarly, current source 200a of FIG. 22 A can be realized using P-channel current mirror MOSFETs to source a controlled current from the 5V supply to the anode of the LED string 201. FIG. 22B illustrates a block diagram representation of this idealized current source 200a showing a current sensing and control element 202 that drives the gate of a p-channel MOSFET 203 . The MOSFET 203 (or alternatively a bipolar junction transistor) keeps the current in check while sustaining the voltage across its drain to source terminals. Gate bias is provided by current sensing and control element 202 to maintain a constant current despite variations in drain-to-source voltage.

FIGURE. 22C illustrates an implementation of the described constant current source, where the P-channel current mirror MOSFETs 204a and 204b sense the load current I ^led . The ratio between the gate width of the MOSFET 204b and the gate width of the MOSFET 204A is p, where p < 1, which means that the current in the MOSFET 204b of the mirror is a small fraction, but in a precise proportion, of the charging current of the LED. This measured current representing a current referenced to the high voltage supply of V ^led of magnitude PI ^led is then input to the differential transconductance amplifier 206 and compared to the reference current Iref, a current also reflected on the voltage supply rail. high voltage of V ^led . The differential “error” signal ?Ierr comprising the difference between Iref and PI ^led is then amplified and proportionally converted to a voltage - V ^g by transconductance amplifier 206 and fed to the gate of the current control element, P-channel. of current source MOSFET 203, forming a closed-loop feedback path.In operation, the gain Gm of the transconductance amplifier 206 results in a gate bias -V ^g which drives its error signal AIerr to zero, thus forcing Iref = PI ^led For convenience, we redefine p = 1/a so we can express the current source transfer function as I ^led = aIref The same reference current is distributed to all LED strings within the same pad of LEDs to ensure uniform brightness across all LEDs.

In the switching current source implementation as shown, digital inverters 211a and 211b and an analog drive gate comprising a P-channel MOSFET 207 and a P-channel MOSFET 208 connected with V ^led perform the digital enable function. of input En, driving the gate of current source p-channel MOSFET 203. Specifically, when the enable signal En is high, the output of inverter 211a is on ground and the output of inverter 211b is at 5 V , Turning on the high voltage level shift N-channel MOSFET 210a and turning off the high voltage level shift N-channel MOSFET 210b. With the high voltage level shift of n-channel MOSFET 210a in its on state, current is conducted through resistor 209a pulling the gate of the transmit-gate p-channel MOSFET 207 down to a voltage near ground and turning on the transistor. Because the P-channel MOSFET 207 has a gate biased close to ground, the device operates in its linear region, i.e., fully on, behaving like a resistor and passing the analog voltage -V ^g from the output of the transconductance amplifier. 206 to the p-channel current source gate MOSFET 203 . Simultaneously, since the high-voltage level-shift n-channel MOSFET 210b is turned off, no current flows in resistor 209b, and the gate voltage of the p-channel pull-up MOSFET 208 is tied to its source, that is, to the V ^led , and the transistor is off. As such, whenever the p-channel current source MOSFET 203 is on, the p-channel pull MOSFET 208 is off and has no effect on the gate voltage of the channel MOSFET 203 source. -p.

Conversely, when the enable signal En is low (digital 0), the output of inverter 211b is biased to ground, disconnecting the high level offset channel N. MOSFET voltage 210a. Because the high voltage level shift n-channel MOSFET 210a is off, no current flows in resistor 209a, and the gate voltage of the p-channel transmit gate MOSFET 207 is biased to V ^led turning off the transmit gate of the p-channel MOSFET 207 and disconnecting the output of the transconductance amplifier 205 from the current source gate of the p-channel 203. At the same time, the n-channel MOSFET 210b is turned on, driving current into resistor 209b and pulling the gate of the p-channel pull-up MOSFET 208 close to ground and turning the MOSFET 208 on. With the p-channel pull-up MOSFET 208 on, the source gate 203 p-channel current is biased to V ^led , so the current source is biased and I ^led = 0. In conclusion, the circuit of FIG. 22C depicts a circuit for implementing a switched controlled current source. When the current sink is enabled (En = digital 1), the current sink conducts and carries a controlled current I ^led = aIref. When the current sink is off (En = digital 0), the current sink is off and the I LED = 0.

It should be noted that the implementation of the current sink circuit in FIG.

20C is essentially a low voltage circuit. The only component that requires a specification capable of surviving the high voltage V ^led supply is the N-channel current sink MOSFET 167. This is not the case with the current source circuit of FIGURE. 22C, which requires MOSFETs with high drain-to-source blocking capacitance in the off-state, and especially P-channel current-source MOSFET 203 which must drive a controlled current while simultaneously maintaining a high voltage, i.e., the current-source MOSFET current should exhibit a wide area of safe operation free from snapback and hot carrier reliability concerns. Of particular concern is the maximum gate-to-source voltage rating of the p-channel MOSFETs 207 and 208, ie, V ^gsp (max). To avoid damaging the gate oxide of these devices, the values of resistors 209a and 209b must be chosen carefully so as not to produce an on-state gate drive that exceeds V ^gsp (max) of the devices. As a precaution, a Zener diode can be included across the gate to the source terminals of MOSFETs 207 and 208, respectively, to set the maximum gate bias to a safe level. In some integrated circuit processes, fabricated high-voltage P-channel transistors can optionally use a thicker "high-voltage" gate, but this option depends on the wafer foundry used to produce the IC.

FIGURE. 23 A illustrates another method of achieving a switched current source. In this case, the analog current control circuit is separate from the digital enable function, so the LED string 201 is connected in series between the controlled current source 200A and an N-channel enable MOSFET 212 connected to land.

The block diagram of this circuit, shown in FIG. 23B , illustrates that the embodiment of an ideal current source includes the current detection and control circuit 202 and the high voltage p-channel current source MOSFET 203. The circuit implementation of a "low side switched" current source is considerably simpler than that of the fully integrated switched current source of FIGURE. 22 C. As shown, the current sense remains unchanged, using a current sense mirror comprising P-channel MOSFETs 204a and 204b, a current reference mirror comprising p-channel MOSFETs 205a and 205b, and a differential input transconductance amplifier 206. In this implementation, all high-voltage level shifting, transmit gate, and gate drive circuitry are completely eliminated and replaced by a single connected n-channel MOSFET 212 to ground driven by low voltage gate drive inverters 221a and 211b.

In the high voltage current source circuits of both FIGURE. 22 C and FIGURE. 23 C, the required reference current is a current sink current referenced to ground —Iref. Since most current references source current rather than sink it, a source-to-sink current mirror is required. This mirror is represented by an n-channel MOSFET 213a connected to the threshold with a current reference input Iref mirrored by an n-channel MOSFET 213b to produce a current sink reference current -Iref used to power the current sink MOSFET. p-channel current mirror referenced to V ^led 205b. It should be understood that the opposite of the circuit shown in FIG. 23 C uses a high voltage p-channel MOSFET and level shift circuit for the enable function and a grounded current sink for current control. But, in general, a high-side switched current sink has no specific advantage over the fully integrated current-switched sink shown in FIGURE. 20 C and is therefore not described in this application.

In all of the circuits mentioned above, the control of the LED current depends on a common reference current. To achieve the precision required to control the brightness of the LED, the reference current Iref requires active clipping during manufacturing. A method to cut the reference current, using resistors, is shown in the FIGURE. 21A . The Irero reference current is determined by the threshold-connected p-channel MOSFET 180a in series with resistor 181. The threshold connection refers to a MOSFET with its gate connected to its drain to create a two-terminal device where V ^gs = V ^ds . The term "threshold" is used because it represents the voltage at which a rapid increase in drain current occurs, to a voltage close to the threshold voltage Vt p of the device, ie V ^gs = V ^ds « Vt. So the current in the Channel MOSFET 180a=p is approximately irefo« (5V -Vtp) / Ro. This reference current is mirrored to other reference MOSFETs 180b through 180e of identical construction and gate width by a shared gate connection to produce multiple matching reference currents Irefi, iref ² , iref ³ , iref ⁴ and more. The mismatch of the gate widths Wpo = Wpi = Wp ² = Wp ³ = Wp ⁴ etc. is not a significant source of variability compared to the variability of the resistor R or in the resistor of the integrated circuit 181. To be able to electrically trim circuit for compensating for manufacturing variations, iref resistance adjustment circuit 182 includes an array of switched resistors 184a, 184b...184n with corresponding resistors ^R1 , ^R2 ...Rn that can be electrically connected in parallel with the resistor 181 (or not) depending on whether the n-channel MOSFETs 184a, 184b...184n are biased into a conducting state by gate drivers 185a, 185b...185n respectively. For each transistor turned on, its corresponding resistor is placed in parallel with resistor 181, reducing the effective resistance Ro and increasing the magnitude of the current irefo. Said clipping method is a unidirectional clipping down on resistance and up on current, which means that the starting value is the highest resistance and lowest current. In manufacturing, the LED current is measured and the combination of the trim MOSFETs turning on and off is adjusted by changing the digital value calibration register 186 until the target current is reached, whereby the contents of the trim register calibration 186 is written to non-volatile memory. Although this method describing switched parallel resistors represents a resistor matching method, an alternative method involves series-connected resistors shorted together by conducting MOSFETs. In this series tuning method, the resistor value with all MOSFETs off starts at the highest value with the lowest current, and the current increases as tuning progresses and the MOSFETs turn on to short more resistors.

Figure. 21B illustrates an alternative clipping method using MOSFET gate width scaling. As in the resistance reference circuit of FIGURE. 21A , in this reference circuit, a reference current irefo carried by a threshold-connected p-channel MOSFET 18oa is reflected to multiple outputs via MOSFETs 18ob to 18oe of identical size.

Unlike the previous case, however, a bandgap reference circuit 19o with a bandgap Vbandgap output produces the reference current. The bandgap voltage is converted to a current by a series resistor and reflected to the threshold-connected current mirror n-channel MOSFET 192a with gate width Wn to reflect the MOSFET 192b with gate width YWn to produce the reference current irefo. The temperature dependent output voltage Vbandgap(T) of the bandgap voltage reference 190 can be designed to largely compensate for the temperature variation of resistor 191 so that ^y [Vbandgap(T)/ ^R0 (T)] = Irera where ^Iref0 becomes constant with temperature. Clipping is produced by changing the effective gate width of the p-channel MOSFET 180a by paralleling any number of threshold-connected MOSFETs 193a, 193b...193n, having the respective gate widths Wpx ¹ , Wpx ² .. Wpxn according to the digital on/off state of p-channel MOSFET switches 194a, 194b. 194n, which are controlled by digital inverters 195a, 195b. 195n. If, for example, MOSFET 194b is turned on by inverter 195b, then MOSFET 193b is essentially in parallel with p-channel MOSFET 180a and the current mirror gate width increases from Wp ⁰ to a larger value (Wp ⁰ + Wpx ² ). The larger gate width of the MOSFET pair connected to the threshold means that less voltage is needed to carry the same reference current, so the current in the output reference currents is reduced. In other words, the current mirror ratio between Irero and If , for example, changes from a ratio [Wp ³ / Wp ⁰ ] to a smaller ratio [Wp ³ / (Wp ⁰ + Wpx ² )], which means that the output current died with active clipping. As such, the trim is unidirectional starting with the highest output current when the trim MOSFETs are off and decreasing as more transistors are connected in parallel. At manufacturing, the LED current is measured and the combination of trim MOSFETs turning on and off is adjusted by changing the digital value calibration register 186 until the target current is reached, where the contents of calibration register 186 they are written in non-volatiles. memory.

To vary the reference current and thus the LED current dynamically, the reference current value can be changed digitally by overwriting calibration register 186 with dynamic data by adjusting or modulating the LED brightness, but doing so is a disadvantage as it loses precision. achieved by a calibration reference fit during manufacture. This problem is overcome by the dynamically programmable reference circuit in FIGURE. 21C, comprising two reference stream registers - the aforementioned Iref calibration register 186, and a separate target reference dynamic current register 199a unique to a specific PBT treatment. The dynamic target reference current 199a varies with time, whereas the calibration table does not. In this regard, the data in the calibration table 186 can be considered as a fixed offset from the data in the dynamic target reference current register 199a. The two registers are easily combined using simple subtraction performed by the ALU 198 logic arithmetic unit to produce a balanced dynamic driving current register, specifically “Iref input word 199b”. This digital word is used to drive a digital-to-digital converter 197. analog (D/A) converter, a digital-to-analog converter that generates an analog voltage in function of its digital input. While accuracy can vary from 8-bit to 24-bit resolution, 16-bit DACs, commonly available on many microcontrollers, produce 1,024 combinations - ample resolution for any waveform synthesis required. As shown, the output voltage of the D/A converter VDAC is converted to current via resistor 191 and reflected across n-channel MOSFETs 192a and 192b to produce the reference current Iren , where Iren « P [(V ^dac -Vtn)/R ⁰ ]. This reference current is mirrored by the threshold-connected p-channel MOSFET 180a and the paired MOSFETs 180b, 180c, 180d, 180e... to produce the corresponding current reference outputs Iren, I f Iref ³ , I f and so on. successively. The D/A converter 197 may also comprise a "current output" D/A converter, which produces an analog current instead of producing a voltage. In such cases, the value of the resistor 191 is not important and can even be eliminated.

Once the components of a distributed PBT system are established through layer-2 authentication and layer-3 and layer-4 network and port address assignments, and LED pad configuration data is exchanged, the distributed PBT system is ready to run the treatments. Once the PBT controller receives a user 'start' command, the PBT processing begins with an exchange of encryption keys or digital certificates between the PBT controller and the network-connected smart LED pads to establish a layer-5 session. . Once the session is opened, the PBT controller and smart LED pad maintain their secure link during file and command exchange until treatment is completed or terminated. Additional network security can be realized using either presentation layer-6 or application layer-7 encryption. The execution of a PBT treatment begins using the file reproduction or data transmission methods, described below.

Data transmission in distributed PBT systems

By incorporating all of the LED driver circuitry into one LED pad, as shown in FIGURE above. 18 , the PBT driver in a distributed PBT system need not be concerned with how the pad is able to select specific LED strings, how the LED current is controlled, or the methods used to pulse or modulate the driving of the LEDs. Instead, the PBT controller performs the user interface tasks and prepares the driving instructions for the selected treatment. These driving instructions can be transferred from the PBT driver to the LED pad in two ways. In one method, software called an LED player is first installed on the pad, which is subsequently used to interpret and execute the treatment, and secondly a set of instructions called a playback file is transferred, instructing executable code from the LED player what to do. An alternative approach is for the PBT to send a transmission file.

In master-slave data transmission, a series of LED instructions are sent sequentially and continuously to tell the LEDs when to turn on and off. Similar to a streaming audio file, the data transfer from the PBT controller to the smart LED panel must occur before a particular step is executed. The packets of entry instructions, sent in successive pieces, must be kept at the forefront of the execution of the treatment; otherwise, the treatment will be stopped for lack of instructions. This process is illustrated in the flowchart in FIGURE. 24 showing LightOS operations occurring on the PBT controller host and LightPadOS operations occurring in conjunction on the smart LED pad client. Specifically, after selecting a therapy session 250, the controller and panel operating systems begin execution 251a and 251b of the selected session 250 . At step 252a and at time t ¹ the LightOS transfers a 1st treatment segment to the LED pad, where at step 252b the LightPadOS executes the 1st treatment segment. At step 253a and at time t ² LightOS transfers a 22nd treatment segment to the LED pad, where on at step 253B the LightPadOS executes the 2nd treatment segment. At step 254a and at time t ³ LightOS transfers a 3rd processing segment to the LED pad, where at step 254b the LightPadOS executes the 3rd processing segment, and so on. Finally at step 256a at time tn LightOS transfers a nth treatment segment to the LED pad, where at step 256b the LightPadOS executes the nth treatment segment, after which the two sessions 257a and 257b end.

USB data packet transfer and instruction execution during the master-slave stream is shown in the example in FIGURE. 25. Preparation of treatment instruction 260a occurs while the red LED is off, beginning with LED instruction 261 represented by a hexadecimal code that represents an example "LED on" instruction. Instruction 261 is then embedded as the payload in for a USB packet, the combination of the payload, instruction 261, with a header 262. In step 263 the packet is then transmitted 263 from the PBT controller to the LED pad. Instruction 261 is extracted and decoded into bits 264, which describe which LEDs should be turned on and which are not.Th post bits are then loaded into an LED high 265 and executed at a time 266 when the red LED curr ent changes from OFF to ON , start a timer to prepare and load the next instruction to turn off all LEDs The switching of the red LEDs is illustrated by an off-on transition 267a and an on-off transition 267b in the graph at the bottom of the page. FIGURE. 25 .

The execution of transmission instructions can be performed using two techniques, the just-in-time (JIT) sequential transfer method and the transfer method anticipated and change. In the sequence transfer method! JIT shown in FIGURE.

26A , the serial packet data stream 272 transmitted from the PBT controller to the smart LED pad is interpreted by the decoder 270 according to the decoding table 271 resulting in two outputs to a color change register 279a and a time shift register 279b, respectively. Each sequential interval contains the interval activation and deactivation time. The elapsed time is calculated one interval at a time as the shift register advances sequentially, for example t ⁵ = t ⁴ + ( ton ⁴ + f ). The process is executed using a first-in, first-out algorithm, where only the first frame of shift register data 277 drives the LED driver 278. All subsequent and waiting frames in the queue, all previous frames , once executed, are discarded. The corresponding color change register in data frame 277 specifies which LEDs are lit by LED driver 278. For example, the [red|blue|NIR1|NIR2] register that has a bit sequence 0100 will light only blue LEDs. , 1000 will drive only the red LEDs, and 0011 will activate the NIR1 and NIR2 LEDs. The resulting optical output includes red pulses 275a, blue pulses 275b, NIR1 pulses 275c and NIR2 pulses 275d, and simultaneous NIR1 and NIR2 pulses 275e. In this method, the shift register advances at a variable rate, speeding up or slowing down based on the values of ton and W .

In the transfer-ahead-and-change method, it is shown in FIGURE.

26B , decoder 270 simultaneously outputs four separate bit streams, 275a, 275b, 275c, and 275D for driving the red, blue, NIR1, and NIR2 LEDs, clocked against a fixed frequency clock. To extend the illumination duration of an LED, the On status bit is repeated for the entire duration. In the transfer-by-and-shift method, a file containing the lighting pattern is transferred to the LED pad and decoded prior to LED playback.

FIGURE. 26C contrasts the JI T sequential transfer method to the transfer-ahead-and-displacement method. While the JIT method decodes the color register of four LED 279s and drives them for a specified interval until the color register changes, in the transfer-forward-and-change method, the transfers are successively decoded in sequences of four bits and are stored and then played back in sequence. nce from memory. In either method, data transmission has the advantage that the LED pad does not require much memory to store treatment data. It has the disadvantage that the transmission requires a constant data flow from the PBT driver to the LED panel.

An alternative approach is to transfer a full, complete playback file from the PBT controller to the Smart LED Pad prior to starting LED therapy. Shown in the flowchart of FIGURE. 27, this operation involves two parallel operations, one executed by the LightOS operating system within the PBT controller host, the other executed by the LightPadOS within the LED pad client. As shown, after the transfer program is archived, execution occurs autonomously within the LED pad without intervention from the PBT controller. After the program is selected in step 300, the replay file for driving the LED sequence is transferred from the server to the client. The LED pad receives the transfer of the file in step 302, then in step 303 it unpacks the file, stripping the file's layer-2 MAC data such as header, checksum bits, etc. to extract the payload data and load it into volatile memory. as static RAM. This process is graphically illustrated in FIGURE. 28 where incoming USB packets 310 are transmitted via a physical medium such as USB to a bus interface 338 of the smart LED pad 337. Once received, the payload 311 is extracted and then unpacked (step 312), executing any decompression or file format required to create the executable code 313. The executable code 313 is subsequently stored in volatile memory 334a. The executable code 313 is self-sufficient to run on top of the LightPadOS operating system without the need for any other files or subroutines other than the LED pad operating system and contains the hard-coded data of the 314 algorithms employed in PBT therapy. , either a single treatment or a complete PBT session . This code could be done, for example, in C+ or any other common programming language.

Going back to the FIGURE. 27 , once the replay file is unpacked and stored in RAM at step 303, at step 304b, the LightPadOS informs the host PBT controller that it is ready to start the session. Once the user confirms that they are ready by selecting the treatment start button 309, in steps 304a the session execution command is enabled starting at step 305a, where the session start command is sent to the LED panel. LightPadOS responds in step 305b by initiating treatment by executing treatment algorithm 314. As treatment progresses, the LED pad occasionally reports its status (step 306b) to the host PBT controller, including time, temperature, or other information. relevant to the program status, which the PBT of the controller can display in step 306a. If an LED pad fault condition occurs, then interrupt service routine 307b on LightPadOS and 307a on LightOS to communicate and possibly negotiate what to do about the condition causing the interrupt. For example, if during the session, the LED pads disconnect and then reconnect incorrectly, the session will stop, inform the user of the connection error, and instruct them how to correct the failure. Once the fault is corrected, the interrupt routine is closed and processing resumes until at step 308b the LED pad informs the host PBT controller that the treatment program has been completed. In response, at session termination step 308a, the PBT controller informs the user that the session or treatment has been completed.

In this discussion, the term "treatment" is defined as a single therapeutic procedure, typically 20 minutes in duration and designed to invoke photobiomodulation in a specific tissue or organ type. Furthermore, a "session" comprises a sequential series of treatments. As the picture shows. 29A , for example, a therapeutic protocol for recovering from injury (for example, treating a sprained and cut ankle from a bicycle accident), may involve three "injury" sessions 315a, 315b, and 315c performed successively every other day, where each session involves the sequential therapy of three successive treatments comprising different algorithms that vary in light wavelengths, power levels, modulation frequencies, and durations. For example, the 315th PBT session, referred to as "inflammation," is intended to speed healing by accelerating (but not eliminating) the inflammation phase of the healing process. Session 315a comprises a sequence of three steps 314a, 314f and 314b comprising algorithms 23, 43 and 17 respectively. Session 315b, titled "infection", shown in FIGURE. 29B comprises a sequence of three steps 314c, 314b and 314g comprising algorithms 49, 17 and 66 respectively. Note that treatment 314b comprising algorithm 17 was used in both the inflammation and infection sessions. Session 315c titled "cure" comprises a sequence of three steps 314g, 314h and 314g comprising algorithms 66, 12 and 66 respectively. Note that treatment algorithm 66 was used once in infection session 315b and twice in cure session 315c.

The sequence of steps of performing sessions for inflammation, infection, and healing together make up the 316 injury protocol, first accelerating the inflammatory phase of healing involving fibroblasts and collagen scaffolding, cell apoptosis, and phagocytosis, then combating secondary microbial infections. opportunistically trying to colonize the wound. Finally, once the inflammation subsides and all infection is cleared, the final step in the injury protocol promotes wound healing by improving the thermodynamics and energy delivery needed to fuel healthy tissue regrowth. The 316 injury protocol does not employ daily therapy sessions, but intentionally spreads the first three sessions over a five-day period. Instead of daily therapy, the need to intervene on days off is explained by graph 317, which is shown in FIGURE. 30 , which describes a generalized biphasic dose-response model in accordance with the work of Arndt-Schultz [https://en.wikipedia.org/wiki/Arndt%E2%80%93Schulz_rule]. According to Wikipedia, the "Arndt-Schulz rule or Schulz's law" is an observed law about the effects of drugs or poisons in various concentrations. He affirms that for each substance: small doses stimulate; moderate doses inhibit; large doses kill. Due to a large number of exceptions in pharmacology, for example when a small dose of drug does nothing at all, the theory has evolved into its modern counterpart "hormesis", but the underlying principle remains the same, that in medicine there is an optimal treatment dose. beyond which the efficacy of treatment is reduced or recovery may be inhibited.

Despite controversy over the results of pharmacological studies, the biphasic model in "energy medicine" has been reconfirmed by numerous studies ranging from carcinoma radiotherapy to photobiomodulation. For example, in cancer therapy, a small dose of radiation cannot adequately kill cancer cells, whereas a large dose of radiation is toxic and can quickly kill the patient, much faster than leaving the cancer untreated.Adapting the biphasic model to photobiomodulation, Graph 317 represents a representation pseudo-3D of PBT conditions where the x-axis represents treatment time, the orthogonally projected y-axis describes the power density of the PBT treatment measure in W/cm2, and the vertical z-axis measures effective energy dose in J/cm2 or eV/cm2, ie, the product of power and time and scaled by the observed magnitude of photobiomodulation, the otherwise observed treatment efficacy. Topographically, the chart appears as two coastlines, a mountain range, and an inland valley. As shown for low-dose treatments known as sub-threshold doses, the treatment has inadequate power, ie, rate of energy delivery, to do anything. Similarly, for very short periods, no matter what the power level, not enough energy is delivered to invoke photobiomodulation. In other words, too fast or too little energy does not invoke photobiomodulation.

For a combination of moderate power densities and durations, stimulation occurs resulting in a peak response curve for power densities or total energy doses above this level, the beneficial PBT response and treatment efficacy decrease rapidly and they can even inhibit healing. Of course, lasers of excessively powerful levels can cause burns, tissue damage, and ablation (cutting). And while LEDs are incapable of the power densities of lasers, they can still run at high currents and cause overheating. However, these treatment conditions occur well beyond the power levels and energy doses shown on the chart. The graph on the right from case study [1] confirms the dose (fluence) dependence of PBT efficacy is independent of Hasic bip with a trough response at 1 J/cm2, a peak response at 2 J/cm2 benefits, the reduction at 10 J/cm2 and inhibition at 50 J/cm2. The inhibition means that the impact of PBT treatment was worse than doing nothing. For this reason, along with concerns about patient safety and comfort, PBT treatments must be spread out over time and limited in potency and dose (duration).

Data security in distributed PBT systems

To effect multi-layer secure communication in the disclosed distributed PBT system, the PBT Controller Operating System (LightOS) and the Smart LED Pads Operating System (LightPadOS) comprise parallel communication stacks using consistent protocols and shared secrets not discernible for a device operator, hackers or unauthorized developers. As such, the distributed PBT system functions as a protected communication network with the ability to enforce security at any number of communication layers, including data link layer-2, network layer-3, network layer-4 transport during configuration and layer-5 in session. layer-6 presentation, or layer-7 application during operation.

As described, “treatments, sessions, and protocols” define sequences of photoexcitation patterns and operating parameters including LED wavelength, pattern modulation and frequency, treatment durations, and LED intensity (brightness), together determining instantaneous power, mean power, therapeutic dose (total energy) and, ultimately, therapeutic efficacy. To discourage copying or duplication, these streams must be stored and communicated securely, using encryption and other methods. Although some data security methods and related security credentials can be run as part of the application, i.e. on LightOS and LightPadOS, an additional level of security can be achieved by including a layer-5 "presentation" in the communication stack of the host PBT controller and any network connected smart LED pad clients.

The presentation layer is represented schematically in FIGURE. 31 , where the PBT controller 120 includes OSI communication stack 330 comprising application layer-6, presentation layer-5, data link layer-2 and physical layer-1. As stated above, within the PBT controller 120, the layer-6 application is implemented using the PBT-specific operating system called "LightOS". In operation, the execution of the LightOS layer-6 program results in actions that require communication with the smart LED pad. These actions are encrypted at Presentation Layer-5 and then passed to lower level communication layers in encrypted form, ie as ciphertext. Specifically, the ciphertext that is transmitted to the Layer 2 data link layer is packed, that is, it is converted into a series of communication packets comprising a clear header and a ciphertext payload according to a particular communication protocol like USB, I2C, FireWire, then communicated through the PHY 1 physical layer to the LED panel. For example, PHY layer-1 can communicate using the USB protocol using differential USB signals 332 to the corresponding layer-1 PHY of the communication stack 331 resident within the smart LED pad 123. So, although the electrical signals comprise layer-1 communications, the USB data constructs behave as if the PBT controller and smart LED pad were communicating at Layer 2 with the packets timed as USB data "frames".

Once the communication stack 331 receives a USB packet, the ciphertext payload is extracted and transferred to presentation layer 5 where it is decrypted and converted to plaintext. The plain text file is passed to layer 6 of the application, where it is executed by the LED pad's LightPadOS operating system. As long as the LightOS of the PBT controller and the LightPadOS operating system of the smart LED pad are designed to communicate and execute instructions in a self-consistent manner, the bi-directional link between the communication stacks 330 and 331 works as a virtual machine at application layer -7 , which means that the distributed device behaves in the same way as if it were a single piece of hardware and at the presentation layer to perform bidirectional encryption and decryption. In this way, data can be transferred between the PBT controller and the smart LED pad. However, to prevent copying of the source code, the treatment library is stored in an encrypted form. For added security, the encryption key used to store the algorithms is different from the key used for communication. Therefore, before a treatment file can be communicated securely, it must first be decrypted.

The process for preparing, communicating and executing an encrypted treatment is schematically represented in FIGURE. 32, where via a graphical UI 341, a user chooses a treatment 342 from a library of encrypted algorithms 340. The encrypted algorithm 17 is decrypted using the system key 343 by converting the ciphertext to plaintext and restoring the unencrypted treatment. 344. In the encryption process 345 the plain text file of algorithm 17 is re-encrypted using the encryption key 346 exchanged with the smart LED pad client. The resulting ciphertext 347 comprising the re-encrypted algorithm 17 is then packaged 348 and transmitted 349 using USB or other appropriate communication medium.

In addition to treatment data, the same method can be used to prepare and transfer PBT session data from the PBT Controller to the LED Pad. This process is shown in the schematic of FIG. 33 where through a graphical UI 351, a user chooses a session 352 built from a library of encrypted algorithms 340, in the example shown comprising three encrypted algorithms. Using the system encryption key, the ciphertext is decrypted 353 by converting the ciphertext to plaintext . The three are text files below, merged 354 and E NCrypted using 356 encryption key exchanged with smart pad LED cli ent. The resulting ciphertext 357 comprising the encrypted scrambled algorithm is packed 358 and transmitted 359 using USB or other appropriate communication medium.

As the picture shows. 34 , incoming data packets 359 received by bus interface 228 at LED pad 337 are first processed to strip packet headers extracting payload 360. pC pad 339 then decompresses 361 to extract the encrypted blended algorithm 362. The ciphertext is then decrypted 363 using the key exchange to extract the plaintext file 364 comprising the processing algorithm or, in the cases of a session file, the combined algorithm. Algorithm or combined algorithm 366 comprises executable code 365 in volatile memory 334a. Since the treatment is stored in RAM, any power outage will erase the file, making it difficult to copy the unencrypted executable code. As the picture shows. 35 , stand-alone pad playback of the PBT sequence with post-transfer (pre-play) mass decryption involves user selection of the session 300 transferring 301 the encrypted file which once received 302 by the pad LED is decrypted 390 and is loaded into RAM. In step 304b, the LightPadOS informs the host PBT controller that it is ready to start the session. Once the user confirms that they are ready by selecting the treatment start button 309, in steps 304a the session execution command is enabled starting at step 305a, where the session start command is sent to the LED panel. LightPadOS responds at step 305b by initiating treatment by executing treatment algorithm 314. As treatment progresses, the LED pad occasionally reports its status 306b to the host PBT controller, including time, temperature, or other status information. relevant programs, and which PBT driver you can use. to show in step 305a. If an LED pad fault condition occurs, then interrupt service routine 307b on LightPadOS and 307a on LightOS to communicate and possibly negotiate what to do about the condition causing the interrupt. Once the fault is corrected, the interrupt routine is closed and processing resumes until at step 308b the LED pad informs the host PBT controller that the processing program is complete. In response, at session termination step 308a, the PBT controller informs the user that the session or treatment has been completed.

Even higher security can be achieved by storing the algorithm on the LED pad in its encrypted form. As the picture shows. 36 , incoming packets 359 received by bus interface 338 on LED pad 337 are processed to extract payload 360, subsequently decompressed 361 and then stored as ciphertext 368 in volatile memory 334a. The file is played at the time the user starts the session by decrypting the file during playback while the file is running, that is, during standalone playback. This process, known as "on the fly" decryption playback, is illustrated in the flowchart in FIGURE. 37 . The process is identical to the bulk crack process flow shown in FIGURE. 35 except that after the LED pad receives the 302 sequence file, the next step is to simply unzip and, as needed, unzip the 303 file, but not unzip it. During playback at step 391, the ciphertext is read from volatile SRAM and executed on the fly, ie, as playback progresses.

FIGURE. 38 contrasts volume discounting and play-on-the-fly methods. In a bulk decryption, the entire replay file 368 stored in ciphertext is read from volatile memory, decrypted 363 to extract the plaintext instruction set 365 and executed to replay 392 the entire file. In contrast, in decryption-on-the-fly replay, a portion 368a of the stored replay file is read and decrypted 365a and then executed 392a by adding the new plaintext instructions to the replay buffer. Meanwhile, another section of the ciphertext 368a is read from volatile memory, decrypted 363 to retrieve the plaintext executable files 165b, and then executed 392b by adding this file to the end of the playlist.

Distributed PBT System with LED Pad Player

Although JIT or transfer-ahead-and-shift-based data streaming for LED drive control can be used to control an LED pad in a distributed PBT system, real-time data delivery over the network The communication link connecting the PBT controller and one or more LED pads becomes problematic when more sophisticated algorithms are required. Even when high-bandwidth communication is available, the transmission of multi-MHz digital data or clock signals represents a dubious method of command and control, especially in security-focused applications such as medical devices. An alternative made possible by the disclosed distributed PBT system is to employ a two-step process to activate the LEDs, first to download an "LED player" to the LED pads, then to download an "LED playback file" that defines the PBT treatment. specific or PBT session to be performed. In this method as described, the execution of the LED unit is done autonomously within the smart pad based on commands from the PBT controller. Because the LED driver is local within the LED pad, advanced functions such as waveform synthesis and sine driver can be realized. If more than one treatment or session is performed, it is only necessary to download the new “LED playback” file again. You can keep the original LED player.

The first step in smart LED pad playback is to download the LED player from the PBT driver onto the LED pad. In a similar way to the streaming file transfer process shown in FIGURE. 36 , the download process shown in FIGURE. 39 involves transferring a 480 encrypted playback file from the PBT controller to the smart LED panel. The download process involves the encrypted LED Player file 480a being decrypted 363 with a system key and then re-encrypted 370 with the LED Pad (client) key 356 to create an encrypted LED Player file 480b. This encrypted text is then transmitted to the smart LED pad where the payload is extracted and decompressed 361 by the decryption n 363 and stored in volatile memory 482. The downloaded LED content player includes waveform synthesizer 483, player of PWM 484, the LED driver 485.

Waveform synthesis is algorithmic generation of excitation patterns, such as sine waves and sine wave chords, but it can also generate triangle waves, sawtooth waves, and play back audio samples. The operation of the waveform synthesizer 483 shown in FIGURE. 40 implies that the waveform synthesizer 483 converts its input, parametric waveform file 486 with system clock 0sys to produce the synth waveform f(t) represented as the synth output data table 489 , that is, it comprises the table of functions f(t) paired with the elapsed time. The PWM generator 555 then converts the function table to a high-frequency PWM pulse train 490 to produce a synthesizer output file 488 that includes the synthesized waveform 491 embedded in the PWM output 490. Depending on the algorithm , the 483 waveform synthesizer can also use 487 waveform primitives. Although the synthesizer can be realized in hardware, for waveforms up to 20 kHz, i.e. within the audio range, it can be easily implemented using software. For example, from 0.5 to 1.0 ms , the value of f(t) = 0.6545. The ^ ^p [f(t)] process converts the function f(t) into a PWM pulse train of on time and off time, where the output is high (on) for 65.45% of the specified range. , that is, from 0.500 to 0.827 ms and has a low state (off) from 0.827 to 1,000 ms. So, the time duration ton = 0.827 - 0.500 ms = 0.327 ms, and the idle time duration W = 0.500 -0.327 = 0.173. In other words, the value f(t) is the work factor D during the period, where D = ton / T ^pwm and where T ^pwm = ton W .

Since the duty factor D is an analog value limited between 0% and 100%, then, for convenience, f(t) is limited to any value between 0.0000 and 1.0000. If f(t) is allowed to exceed 1,000, then the value must be scaled by the maximum value of the function, i.e. f(t) = [f(t)unscaled) / f(t)max] or the form waveform will be clipped to the value 1,000 per the process [f(t)] . The PWM clock frequency called the symbol rate clock 0sym is given by 0sym = 1/T ^pwm . The symbol rate is derived from the system clock 0sys and must exceed the highest frequency waveform f(t) that is synthesized, or described mathematically as 0sys > Osym > f(t). The following table describes the time intervals where tx = (x - 1)T ^pwm by dividing each 500 ms interval into its start time tx (on) and tx (off).

The second process in the LED player is the PWM P layer function 484 shown in FIGURE. 41 , which, in response to its PWM input parametrics 491 and reference clock 0ref processes the synth out data file 488 to produce PWM player outputs 493a and 493b. In operation, the PWM player 484 generates a train of pulse width modulated (PWM) pulses Gpulse(t) 492 comprising the algebraic product Gsynth(t) • Gpulse(t). The Gpulse(t) waveform comprises a repeating pulse consisting of a duration ton = DT ^pwm and off for a duration W = (1 - D)T ^pwm .

Although the PWM player function can be done in hardware, it is easily done in software. Described in pseudo-logic code in terms of a fast counter yx (incremented every cycle), then:

If (t > ^x T ^pwm ) AND (t<((x+D) T ^pwm ))

Then OUT = Gsynth(t)

elseOUT = 0

which means that in each cycle of duration T ^pwm since time ^x T ^pwm ^ t < ( ^x T ^pwm + DT ^pwm ) the output of the PWM player is equal in magnitude to the input (in state), and for an interval ( ^x T ^pwm + DT ^pwm ) ^ t < (x+1) T ^pwm the output of the PWM player is connected to ground, a digital “0”. By cutting the Gsynth (t) input with the PWM Gpulse (t), the 493rd waveform output is digital with an equivalent value of Gsynth(t) • Gpulse(t).The underlying waveform is shown superimposed on top of the pwM signal 494. Although typically the PWM player 484 only outputs a single digital waveform, it can produce more than one output as needed.For example, in the example shown, although output 493a includes the multiplicative combination of two PWM pulses, output 493b is identical to Gpulse(t), which which means that Gsynth(t) = 1. PWM Player 484 can also output a time-invariant constant value Gsynth(t) • Gpulse(t) = 1.

The third step in the operation of the LED Player is the 485 LED Controller. As the picture shows. 42 , the 485 LED controller synchronized with the 0 ret reference clock combines the parameters of the 495 controller with the output of the 484 PWM player to produce the 497 LED transmission. Unlike the 483 waveform synthesizer and 484 PWM player, which outputs digital signals, the output of the 485 LED driver is analog. Using controller parameters 495, a programmable reference current 496 with magnitude aIref(t) is generated and multiplied by the PWM player output 484, specifically Gsynth(t) • Gpulse(t) to produce output 497 comprising aIref (t) • Gsynth (t) • Gpulse (t). The output waveform I ^led shown in graph 498 reveals a waveform that varies in time, specifically sinusoidal, digitally pulsed, and varied in current over time. Although the PWM player 484 can generate a single output as an input to the LED driver 485, it is also possible to provide two or more different outputs if necessary. Such cases could be useful, for example, in large PBT systems where many sites are required to treat each body part uniquely, ie with good tissue specificity.

The entire LED rendering process is summarized in the FIGURE example.

43 sequentially using the waveform synthesizer 483, the PWM player 484 and the LED controller 485 to generate the LED control flow 497 . Unlike prior art methods, LED activation in the disclosed distributed PBT system is generated entirely within one LED pad while advantageously keeping all treatment libraries and control of the PBT system in a separate, common PBT controller. and other than the LED pad(s). The waveform generation process uses a system clock of frequency 0sys produced within the LED to perform its tasks, thus eliminating the need to distribute high-speed clocks over long lines. To ensure synchronization of the PWM 484 player and the 485 LED driver with the 483 waveform synthesizer, the system clock 0sys is divided using software or hardware counters to produce the reference clock 0 ref. As such, the playback of LEDs within a given LED pad is fully synchronous. While both the 493 waveform synthesizer and 484 PWM player output digital PWM signals that comprise repeated transitions between digital states 0 and 1 of variable duration, the output of the LED driver is analog capable of driving LED brightness in any way. including, but not limited to, square waves, sine waves, sine wave chords, triangle waves, sawtooth waves, acoustic or electronic music audio samples, cymbal sound audio samples, and other sources of noise and at any frequency within the audio spectrum from 20 Hz to 20 kHz, that is, from the 0th to the 9th musical octave. It also produces modulating LED driving in the infrasound range, i.e. in the -1 st and -2 nd octaves, for example, down to 0.1 Hz, or to drive LEDs with direct current (0 Hz), i.e. providing continuous wave (CW) operation.

It should be noted that since each pad independently communicates asynchronously with the PBT controller, and since each LED pad generates its own internal time reference for LED playback, strictly speaking, the disclosed distributed PBT is an asynchronous system. That being said, due to the high clock speeds, precision time references, and high-speed communication network, the time mismatch between the LED pads is in the microsecond range, imperceptible in camera control. UI and UX responsiveness and has no impact on the effectiveness of PBT.

Waveform Synthesis in Distributed PBT Systems

In distributed PBT systems, one PBT controller will control many smart LED pads, eg 3, 6 or more. Due to the number of smart LED pads required, economic considerations dictate limiting the complexity of the LED pads, specifically the cost and processing power of the ^P 339 pad. Also, to manage product costs, the Total memory within an LED pad must also be limited. Limited in computing power and memory, waveform synthesis within an LED pad in a distributed PBT system requires several criteria to be met:

• The amount of data transferred or stored on the LED pad should be limited.

• Calculations performed on the LED pad should preferably comprise simple arithmetic calculations such as addition and subtraction, avoiding complex iterative processes such as functions, matrix operations, etc., a unless absolutely unavoidable and even then infrequently.

• Calculations must be performed in real time with minimal energy or heating consumption.

[f (t)] para producir el archivo de salida de sintetizador 488. La salida de sintetizador 488 comprende un archivo PWM digital numéricamente equivalente a la tabla de salida de sintetizador 489 representada gráficamente como Gsynth (t) 490.The detailed operation of the waveform synthesizer 483 is illustrated in FIGURE. 44 where an input file comprising the parameters of the waveform synthesizer 486 once loaded into the waveform synthesizer 483 selects a synthesis method 550 used to calculate a function f(t) 553, either using the generator function unit 551 or processor primitive 487, all performed in synchrony with the system clock 0sys. In the case of waveform synthesis, the primitive processor 487 requires access to detailed waveform descriptions, specifically the waveform primitives 487. The resulting function f(t) 553 comprises Cartesian pairs of time t versus f(t) graphically illustrated in function table 554. Function table 554 is then converted to time-varying digital data by PWM generator 555 using the process

[f(t)] to produce the synthesizer output file 488. The synthesizer output 488 comprises a digital PWM file numerically equivalent to the synthesizer output table 489 graphically represented as Gsynth(t) 490.

Waveform synthesis with unitary function generator

The operation of the unitary function generator 551 is illustrated in FIGURE.

45 involves selecting a mathematical function and then calculating the value of the function a number of times to generate function table 554. These functions are known as "unit" functions because they have analog values limited to real numbers between 0.0000 and 1.0000. An example of a unitary function in the time-varying function f(t) = 1, or "constant" is shown in graph 560. Another function, a unitary sawtooth shown in graph 561 is described by the equation f(t) = MOD(tf, 1) where (tf) is the argument of the modulo function and 1 is the base , which means that the function is a linear decimal fraction between 0 and 1. For any number over a multiple of 1, the modulo function returns the remainder, for example if (tf ) = 2.4 then MOD(2,4) = 0.4 In a sawtooth, functions increase to one, then back to zero and repeat.Another function that accelerates up to one and ramps back down to zero symmetrically is the triangle of waves shown in graph 562 which is given by the equation f(t) = 1 - 2 • ABS [ MOD ( tf, 1) - 0.5] .

The synthesis of a single sine wave or a string of three or more sine waves of frequencies fa, fb, fc, and relative magnitudes Aa, Ab, Ac, respectively, can be described by the equation f (t) = Aa (0.5+ 0.5[Aa sin (2ntfa)+Ab sin (2ntfb)+Ac sin (2ntfc)]/[(Aa+Ab+Ac)]) 0.5(1-Aa).. This mathematical process shown in FIGURE. 46 mixes three sine waves 564, 565, and 566 with gain 580, 581, and 582 respectively, summed in a 583 digital mixer using linear addition of digital words.

Digital addition, the arithmetic addition of binary, octal, or hexadecimal numbers, is identical to addition of decimal numbers, except that the numbers comprise binary representations or binary equivalents of numbers, i.e. base two (b2), base eight (b8 ) or base sixteen (b16), instead of base ten (b10). Although digital addition can be performed using dedicated devices, the resident Arithmetic Logic Unit (ALU) within the LED pad's microcontroller function can easily perform the tasks required in binary mathematics. Converting numbers s to another base, then adding them in the alternate base, and converting back to base 10 produces identical results. This equivalence principle is shown in the following example table for the sum of three numbers in different bases. In the context of waveform synthesis, the numbers being added represent the instantaneous values of three sine waves at a given time, added to produce a digital sum of the three numbers. For illustrative purposes, the values of the sine wave have been increased ten times, that is, where Axfx (0) and where Ax = 10 for x = 1 to 3. For example, at a specific time t ¹ , the value of the functions fa(0)) = 1; fb(0)) = 0.5; and fc(0)) = 0.5. In a case where the gain factors are evenly weighted, that is, where Aa = 10, Ab = 10, and A c = 10, then the sum 10 ( I fx (0)) = 20. To convert this number into a function unit, the resulting sum must be scaled to a fractional number between a result between 0.000 and 1.000, a task performed by the 584 autoranging function.

For each tx time point, dividing Ax ( I fx (tx)) by the sum of the gain multipliers (Aa Ab Ac) provides an average of the combined chord. In the case of even weighting, that is, where Ax = 10, the sum of these gain factors (Aa Ab Ac ) = 30. Applied to the above sum, autoranging scaling converts the sum of 20 to the number autorange scaling 20/30 = 0.666 , the same number obtained by averaging three numbers that have instantaneous values of 1.0; 0.5 and 0.5. The autoranging function also works when sine waves are combined with non-uniform weighting, where one or more frequency components of the wave sinusoidal dominate the mix. For example, a mix in which Aa is 20% of the total, Ab is 40%, and Ac = 40% yields the following mix of signals from the

In this case (Aa+Ab+Ac) = 100 while g(t) = 70, so the output of the autoranging function is 0.7. The autoranging function employs a positive multiplier Aa > 0 used to scale the signal to compensate for magnitude compression. Because the scalar Aa changes not only the function but also changes its average value, the DC offset correction term 0.5 (1 - Aa) is added to the sum of sine waves to re-center the mean function back up to 0.5 .

FIGURE. 47 illustrates various sine waves and sine wave chords made according to the unit function generator. In the examples shown, three sine waves one octave apart (ie fc = 2fb = 4fa) are generated with various gain factors to produce a variety of complex functions. The gain factors [Aa, Ab, Ac] control the mix or "blend" of frequency components. Because the components are averaged, the gain factors can be any positive real number. However, for convenience, the three factors can be scaled in percentages. In some cases, the weighting factors are zero, which means that the particular frequency sine wave is absent from the mix. For example, in graph 564, [Aa, Ab, Ac] = [1, 0, 0] so only the sinusoid fa is present. Similarly, in graph 565 where [Aa, Ab, Ac] = [0, 1, 0], only the half-octave sinusoid fby is present in graph 566 where [Aa, Ab, Ac] = [0, 0, 1], only the highest octave sinusoid is present.

The figure also illustrates a variety of blended chords. Graph 567 shows a uniformly weighted combination of frequency sinusoids fa and fb, graph 568 represents a uniform weighted combination of frequency sinusoids fa and fb, and graph 569 represents a uniform weighted combination of frequency fb and fc sinusoids. Unevenly mixed blends of a sine wave with two 2/3rd frequency weighting fa and 1/3rd frequency sine wave fb are shown in the graph 570 . Three sine wave mixes include the evenly weighted 572 chord and the 571 unequally weighted sine wave where [Aa, Ab, Ac] = [0,2; 0.4; 0.4]. The algebraic computation of sin(0) where 0 = fxt for x = a, b, c... requires the computation of a power series [http://www2.clarku.edu/~djoyce/trig/compute.html ] for each evaluation sin(0)

(fat)3 (fat)5 (fat)7 (fat)9 (fat)11 (fat)13

sin(fat) = _(fat) 3! 5! 7! 9! eleven! 13!

(fbt)3 _{, (fbt)5} (fbt)7 . (fbt)9 (fbt)11 . (fbt)13

sin(fbt) = (fbt) 3! 5! 7! 9! eleven! 13!

(fct)3 , (fct)5 (fct)7 , (fct)9 (fct)11 , (fct)13

sin(fct) = (fct) * *

3! 5! - 7! 9! - eleven! 13!

where! = n • (n - 1) • (n - 2) ... 3 • 2 • 1. Note that the same method can be used to produce cosine waveforms, which are no more than since the waves phase shifted by 90°. To produce a three sine chord wave Ax ( I fx (tx)) with the highest frequency of the sine wave at the 9th octave, approximately 20 kHz, with 360 degree accuracy requires all of the above calculations along with PWM generation [f(t)] should occur at a rate of 7.2 MHz, that is, within 138 ns. This approach is computationally intensive, wasting compute cycles and burning power, especially when synthesizing high-frequency waves.

Waveform Synthesis with Primitives Processor

An alternative method, much less computationally intensive and better suited to the limited computing power of the LED pad pP 339, is the use of a table query that evaluates a function. For periodic functions, the value of the function in regular period increments, eg, in fixed angles or fixed percentages, can be precomputed and loaded into tables referred to herein as function "primitives". For example, since the value of a sin(0) depends on the angle of its argument 0 where

sin0° = 0

sin 15° = (V6 - V2)/4

without 30° = 1/2

without 45° = V2/2

without 60° = V3/2

sin 75° = (V6 V2)/4

without 90° = 1

Since the sine function is periodic, there is no reason to recalculate the same values each time the sin(0) evaluation is required. In such a case, the use of a lookup table is potentially beneficial.

Lookup tables, however, face several fundamental obstacles: For one thing, the table can only return a value from the function in the same input condition for which it was previously computed, that is, with the same argument. J UST because the table contains the value of sin(45°) does not mean that you know the value of sin(22°). In a subroutine call to a lookup table, the input argument is not likely to match its available arguments unless the two are developed together to ensure that they use the same values. Another issue in using lookup tables is the rigid equation problem, the realization of high-resolution synthesis waveforms across many orders of magnitude of frequency. For example, if a 20 kHz (9th octave) sinusoid is synthesized using PWM methods with 16-bit precision, the required sample rate is (20,000 Hz)(162) = 1,310,726,000 Hz or approximately 1.3 GHz. If in the same simulation, an infrasound excitation pattern at 0.1Hz (-2nd octave) is added to the chord, the period of the low frequency wave component is T = 1/f = 1/ (0.1 Hz) = 10 sec. This means that to maintain the required 9th octave resolution while synthesizing a single 10 second infrasound wave requires a table of (1.3GHz)(10sec) = 13 billion data points. Such a large data table not only requires too much time to transfer from PBT driver to smart LED panel, but also requires too much memory.

To solve the problem of hard quotes while ensuring matching arguments between subroutine calls and lookup tables, an inventive method described in this paper uses predefined periodic waveform primitives, such as sine waves or linear functions ( scalars), combined with a series of counters. share a common numerical base, for example base 2. The term “primitives” as used here means tabulate time independent description of a waveform - one where the waveform is described using specified arguments relative to the period of the function of T and not in absolute time. For example, in linear functions such as a sawtooth wave, entering a rectilinear (Cartesian) argument into the lookup table returns a single value. In a linear sawtooth unit going from 0 to 1 over a period T, the input p is unitless, where at 25% of T the function "saw(p)" has a value of 0.25, at 78 % of T the function saw(p ) has a value 0.78, etc. To accommodate repeated loops, it is beneficial to express the argument input "p" using the modulo function MOD(argument, limit) where MOD(p, 1) for positive inputs returns a bounded value between 0 and 1, ie the remainder after division by the largest integer multiple of the limit. For example MOD(0.78, 1) = 0.78, MOD (5.78, 1) = 0.78 and MOD(z.78, 1) = 0.78 for any value of z. As such, only data covering one period T is required to describe any repeating waveform.

The same function applies to polar coordinates. The evaluation of sin(MOD(0, 360°)) produces a repeating sequence of values between sin(0°) and sin(359.99...°). At 360° the entire cycle is repeated because sin(MOD(360°, 360°)) = sin(0°). Note that in actual code or spreadsheets, the angle 0 arguments of sin or any other trigonometric function are expressed in radians, not degrees, but the principle of the modulo function and its application remain the same. themselves. Using the modulo function in the manner described, the size of a lookup table for any periodic function can be limited to a single period, reducing the size of the table dramatically. The number of data pairs in each lookup table is therefore equal to the principal resolution £ providing a one-to-one correspondence between a 0x input to a lookup table and its output fx where for any eighth x, the 0x ratio = £x fx describes the transformation performed by the lookup table subroutine call .

Although these function primitives comprise a collection of time-independent states that describe a mathematical function, waveform synthesis requires their combination with oscillators comprising digital or analog clocks to produce a time-varying waveform. Specifically for rectilinear functions of period T, such as triangle or sawtooth waves, the argument x can be expressed as x = t/T, and for sine waves, chord sine waves, and other trigonometric unit functions 0 = tf. In either case, a time source is required to transform a primitive time-independent waveform into a time-varying function. One of these implementations to generate a range of time sources, represented algorithmically in FIGURE. 48 A, combines a series of binary (+2) digital counters 590 to 598 that generate ten synchronous clock frequencies 0g to 00 from a common clock, specifically symbol clock frequency 0sym has a programmable frequency. The clocks are then used to synthesize periodic functions such as sine waves in the audio spectrum having the corresponding frequencies fg in the ninth octave to f ⁰ in the zero octave, and mix them in various combinations as desired. The same methods, not shown, can be used to generate infrasound, ie oscillating waveforms below 20 Hz, and also (providing a suitable transducer is used) ultrasound comprising frequencies above 20 kHz.

During synthesis, each clock is converted to a time-varying waveform f(t) using a periodic function lookup table, e.g., sine wave, sine wave strings, triangle waves, sawtooth waves , etc. Each clock is paired with the waveform it creates, eg 08 uses the lookup table sine wave 618 with primitive resolution £8 to generate the sine wave frequency f8, 03 uses the sine wave 613 lookup table with primitive resolution ^£3 to generate the sine wave frequency f ³ and ^{0 1} uses the sine wave lookup table for sine wave 611 with primitive resolution ^£1 to generate the frequency of sine wave 0 , where

f8 = 08 / £8

f3 = 03 / ^£3

f1 = 01 / £1

and in general fx = 0x / £x. Then, in operation, the 10-octave waveform summation implementation primitive processor 552 uses nine binary counters 598 to 590 to generate ten clock frequencies comprising input 09 = 0sym and clocks 08 to ^{0 0} to drive. the corresponding sine wave lookup tables 619 to 610 to synthesize f ⁹ to f ⁰ sine waves.

The mixing process involves selecting various sine wave combinations using octave data switches 609 through 600, mixing the selected sine wave components in a digital mixer summing node 630 where the components are weighted in varying percentages by digital gain amplifiers 620. to 629. The combined sum is scaled by autoranging function 631 in the range 0.000 to 1.000. Although the processor primitives can be implemented in hardware or with hardware controlled firmware, the function can be fully emulated using software where mixer 630 is executed digitally using binary addition, and the 631 autoranging function can be performed using binary mathematics. Run one of several division algorithms (https://en.wikipedia.org/wiki/Division_algorithm). To avoid performing unnecessary operations, primitives- processor 552 only executes operations on sele Cted octave switches 600-609.

Using the method shown in FIG. 48 A and described above, running primitives on the 552 processor performs the wide-bandwidth waveform synthesis and chord building over three decades of frequency, i.e. ten octaves, spanning a frequency range of 20 Hz to 20,000 Hz, using only table lookups and a series of counters. The described method is computationally efficient and requires a minimum of memory or computational power to execute and, unlike the unitary function generator 551 of FIG. 44 , does not imply a real-time evaluation of power series. A key feature of the synthesizer in generating wide-bandwidth algorithmic waveforms is the role of the accountant's operation. Together, counters 599-500 generate ten octaves of clock frequencies that are used as inputs to the corresponding lookup tables 619-610. Because each octave is fed by its own specific clock frequency, the number of points in the corresponding table and the memory required to perform the The table is limited to the required precision of that specific octave and does not involve data used in other frequency bands. In this way, the described combination of counters and lookup tables overcomes the aforementioned rigid equation problem. To further minimize computational intensity and avoid unnecessary calculations, lookup table subroutine calls are limited to only the tables selected by the octave switches.

To avoid aliasing and phase shift distortions, the counter cascade 698 to 590 is synchronized to a common clock called symbol rate 0 sym output of tuner (counter) 599. For convenience, the symbol rate is sym is equivalent to to the ⁹ clock signal for 9th octave waveform synthesis, but this relationship is arbitrary. Any symbol rate greater than the PWM resolution of the highest synthesized frequency, where 0sym s £sym fmax will suffice. The counter cascade can be done by hardware or software. Although a ripple counter can be used, a synchronous counter is preferred to avoid clock phase shift. A ripple counter is a counter cascade where the output of each counter stage is instantly available at the same time the next stage is entered. Due to the propagation delay through each counter stage, the outputs of the higher frequency clocks change state before the lower frequency clocks. Thus, the state changes "curly s " down the cascade, where the first clock ^{0 9} changes state, followed a moment later by 08 and then ^{0 7} , 06, ^{0 5} , etc. rippling like a wave across the surface of a pond.

By contrast, a synchronous counter works synchronously, where although the digital counter takes time to ripple through the counter chain, the outputs only change at the same time as a timing clock pulse. In this way, the ripple of the signal through the counter cascade is invisible to the user. More specifically, whether implemented in hardware or software, a synchronous counter works like a wave counter but with a D-type flip-flop [https://en.wikipedia.org/wiki/Flipflop_(electronics)] outputs locked. The D flip-flop retains its previous state until it is enabled by a latch signal with the corresponding truth table, that is, the high or low state of the data input is copied to the latch output only when the clock clock sync goes high, after which the sync clock can return low and the flip flop output will remain locked in any state on the D input at the time of the last sync clock pulse until the sync occurs. next sync pulse. During that interval between clock pulses, the output of each counter stage can change without the transition appearing on the counter output. To avoid clutter in the schematic, counters 599 through 590 can represent a synchronous counter without explicitly picting the D of the latch flip-flop or a ny synchronization clock input. To ensure that the clock transitions ripple completely through the counter cascade before updating the state of the clock outputs ^{0 9} to ^{0 0} , the synchronization clock pulse is derived from the frequency clock state transition lowest synthesized, in this example represented as ^{0 0} .

The symbol rate 0sym feeds the counter cascade is generated from the system clock rate 0sys using a 599 programmable counter “tuner”. The symbol clock rate 0sys is generated to produce a maximum output frequency fmax a a resolution £sym. The primitive resolution value £sym is a programmable input to tuner 599 that can be changed depending on the waveform synthesis being performed. The numeric variable £sym, referred to herein as "primitive symbol resolution" is defined as the resolution of the highest synthesized frequency where £sym = 0sym / fmax has a value that can range from 24 to 65,536 depending on the required synthesis precision. For example, selecting £sym = 96 in sine wave synthesis means that po the highest-pitched sine wave of the synthesizer is related to the symbol clock frequency by the relationship 0sym = £sym fmax = 96 fmax where 90° of arc uses 24 points, one point every 3.75°. In operation s procedure uner 599 produces the entire cascade of frequencies derived from and tuned with the symbol clock 0sym rate. The resolution of the £sym need not match the resolution of the lower octave lookup tables. Different levels of precision £x may be used for lookup tables 619 to 600 or, alternatively, the same precision lookup table may be used to generate some or all of the required frequency components. Alternatively, the same lookup table can be used for each generated sine wave. In such cases, each sine wave frequency fx has identical precision £ ⁹ = £s = £ ⁷ ... £ ¹ = £ ⁰ .

Because the entire counter cascade is driven from a common symbol clock frequency 0sym the exact frequency ratio of the synthesized waveforms is precisely defined by the counter frequency 0x and the corresponding lookup table resolution Sx . Although this relationship is shown using binary counters ( divide by 2 ) , there is no restriction as to what the divisor of the counter can be. It is convenient to divide by two because it is equivalent to halving the frequency, equivalent in musical scales to an octave or twelve semitones. However, counters can use any cascading combination of counters, each with different divisors. Alternatively, programmable counters can be employed, where the count is loaded into the counter. Furthermore, since the counters operate at fixed clock rates and complete a full oscillation period at each points x data points, i.e. a full cycle of a lookup table, then the relative time and phase are precisely known. of any two periodic functions. Given, for example, two sine waves having frequencies fx and fy where

fx = 4>x / Sx

fy = 0y / Sy

then the frequency ratio of the waveforms is given by

f x _ ^ x K y

fy ^ y K x

This relationship is illustrative that frequency scaling can be done by changing the 0x clock or changing the Sx resolution of the lookup table. For example, if presenting a constant search resolution is used when Sx = Sy = 24, then the ratio of frequencies fx/fy of the synthesized sine waves depends only on the ratio of clock rates 0x/Oy

In such cases, a clock frequency ratio of 0x/ Oy = 4, results in two sine waves of the same note but two octaves apart, for example, the musical note A at 1760 Hz in the 6th octave and the note musical A in 440Hz in the 43 octave. FIGURE. 48 B illustrates a dual waveform sine summing example where only the 6th and 4th octave switches 606 and 604 are enabled and used to access data in the lookup sine wave tables. 616 and 614 each having a primitive resolution £6 = £ ⁴ = 24. The outputs were amplified b digital gain and amplifiers 626 and 624 were then mixed in digital summing node 630 to produce a mix ed in the form of output wave. In operation, tuner (counter) 599 generates symbol clock 0 sym from system clock 0 sys . The cascade of ^2 counters 598, 597, and 596 divides the clock symbol 0sym to produce ^6th octave clock 06 and by counters 595 and 594 to generate 4th octave clock 04.

The resulting 2-sine wave chord is given by the sum

g(t) = 0.5 0.5[Aa sin (f ⁶ t) A ⁴ sin ft)] = 0.5+0.5[Aa sin (0sym t/192) A ⁴ sin (0sym t/768 )]

The multiplier 0.5 0.5 [periodic expression] is used to scale the maximum magnitude of the sine wave from ±0.0 to ±0.5 centered on a zero average value. The 0.5 adder shifts the curve up by 0.5 to span a positive range between 0.000 and 1.000. By allowing octave commutator 601 as shown in FIGURE. 48 C, the components of the 611 lookup table driven by clock ^{0 1} are added to the chord. Clock ^{0 1} is generated from clock ^{0 4} using counters 593, 592, and 591. The aggregate 1 st octave frequency component is given by

and the resulting 3-sine wave chord is given by the sum

g(t) = 0.5+0.5[A6 sin ft) A ⁴ sin ft) A ¹ sin ( ft)] = 0.5+0.5[A6 sin (0sym t/192) A ⁴ sin (0sym t /768) A ¹ syn (0sym t/6144)]

As described, the above synthesis method uses a single primitive waveform to simultaneously generate two or three sine wave strings.

Additional details of the operation of the primitive processor are illustrated in the single chord synthesis primitive illustrated in FIGURE. 49 . As shown, the tuner 599 comprises two counters: the system clock counters 640 and the c symbol lock counter 641. The system clock counter is a counter that converts the system clock pC having a frequency 0sys to a reference clock frequency 0ref at a convenient fixed frequency (eg 5 MHz). The symbol clock counter then converts 0ref to the symbol clock frequency 0sym used to define the reference frequency of the counter cascade for sinusoidal synthesis. In the example shown, counters 598 through 593 comprise binary counters, generating multiple sinusoidal frequencies each one octave apart, as described in the table above. Inspect the ion disclosures further for a binary counter cascade:

• The 0x clock rate in each octave is a multiple of 2 of the 0sym symbol rate.

• The frequency fx of each octave is a multiple of 2 of the maximum synthesized frequency fmax which is, without limitation, illustrated in the 9th octave of the musical scale.

• The relationship between the symbol clock frequency 0sym and the maximum synthesized frequency fmax is determined by £sym, the resolution of the highest frequency synthesized waveform. The multiplicative product fmax £sym = 0sym sets the highest clock frequency in the counter cascade.

• The relationship between the clock frequency of symbol 0x and the synthesized frequency fx in each octave x is determined by £x the primitive resolution of the waveform in that octave.

Since all of the relationships between clock speeds and frequencies in a single cascade of binary counter primitives comprise precise ratios to other frequencies present in the processor primitive, setting the frequency and resolution of any one synthesized waveform from frequency fx y x automatically determines the frequency of each synthesized frequency and clock in the entire counter cascade, including the symbol rate 0sym and the maximum frequency fmax. The frequency scale of the primitive process is summarized in the following table:

In this regard, the disclosed primitive processor represents a "tuned" system in which the entire multi-octave synthesizer is set to a single "key" frequency analogous to tuning a monophonic musical instrument to a single note or key, for example, an instrument tuned in the key of A. For this reason, the operation of the symbol clock counter 641 is set by two parameters, namely fkey selection 642 and lookup table 645 having primitive resolution $sym . As shown, lookup table 645, stored in volatile or non-volatile memory within the LED pad, is selected by some identifier such as hexadecimal code 643, or some equivalent binary code 644 thereof.

Since the entire synthesizer is tuned in multiples of octaves, the choice of fkey select input 642 is arbitrary. For added convenience, digital tuning can be based on international tone frequency standards. For example, the pitch "A" above middle C in the fourth octave has a frequency of 440 Hz. This 440 Hz pitch is considered the general tuning standard for musical pitch [https://en.wikipedia.org /wiki/A440_(pitch_standard)]. Known as A440, A ⁴ , or the Stuttgart field, it is classified as ISO-16 by the International Organization for Standardization. Adapting this standard for the primitive processor, the synthesizer is described as being tuned to a specific key by choosing a note or frequency in the fourth octave.

Specifically, the "key select" input 642 sets the note or frequency in the ^43rd octave to which the entire synthesizer is tuned. If the maximum synthesized frequency is chosen to be in the 9th octave of the audio spectrum and we arbitrarily select the 4th octave as the frequency input range for tuning the synthesizer, then the 9th octave and the fourth octave differ in 5th octaves. Since 25 = 32, it means that fmax = f ⁹ = 32f4 and adjust according to the key select 642 the maximum frequency fmax = 32fkey . Given 0sym = £sym fmax then 0sym = £sym (32fkey). For example, setting “select key” to 440 Hz (standard A above middle C) where f ⁴ = 440Hz and where fmax = 32 fkey = 32(440Hz) = 14,080 Hz automatically scales the entire spectrum of available synthesized frequencies. until f ⁹ = 14,080 Hz, f 8 = 7,040 Hz, fr = 3,520 Hz, fa = 1,760 Hz, f ⁵ = 880 Hz, f ⁴ = 4400 Hz, f ³ = 220 Hz, f ² = 110 Hz, fi = 55 Hz, f ⁰ = 22.5 Hz, and fi = 11.25 Hz. If fkey is set to middle D, all fx synthesized frequencies will also be multiples of D. Or if fkey is set to middle A# , all binary synthesized frequencies they will also be multiples of A# Synthesis of sine waves other than multiples of octaves will be discussed later in this description.

Referring again to the implementation of the primitive processor in FIGURE. 49 , lookup table 645 comprises an n exemplary primitive description of a sine wave with a 24-point resolution. This primitive tabular description of a sin e wave is independent of time, relying solely on the sin argument of sin(0) as input. After selecting the fkey of the primitive processor with the key, select 642, for example, to be 440Hz, and the resolution £sym is set by selecting the waveform table of primitives 645 to be £sym = 24, then the clock frequency of the symbol 0sym and the corresponding period Tsym is given by

Osym = Ssym(32fkey) = 24(32)(440Hz) = 337,920Hz,

Tsym = 1/ Osym = 1/(337,920 Hz) = 2.96 qs

This symbol rate corresponds to a maximum synthesized frequency fmax in the ninth octave where fmax = f ⁹ = 0sym/£sym = (337.920 Hz)/24 = 14.080 Hz with a corresponding period T ⁹ = 1/f9 = 71.02 qs qs which is also equivalent to Tsym £sym = (2.9592... qs)(24) = 71.02 qs.

By establishing a time reference used in the binary counter cascade, the time-independent sine primitive table 645 is transformed into a time-based description of the function 646a, specifically g(t). The same clock symbol of clock 0sym is the time base for generation clocks 06 and ^{0 4} used to synthesize 6th and 4th octave sinusoids 647a and 648a, specifically

06 = 0sym /8 = (337,920 Hz)/8 = 42,240 Hz, having a period 1/06 = 1/(42,240 Hz) =23.67 qs

04 = 0sym /32 = (337,920 Hz)/32 = 10,560 Hz having a period 1/04 = 1/(10,560 Hz) = 94.79 qs

These clocks are used to synthesize two synchronous sine waves having frequencies f ⁶ and f ⁴ with the following frequencies

f ⁶ = 06^6 = (42,240 Hz)/24 = 1,760 Hz with a corresponding period T ⁶ = 1/f6 = 568 ps f ⁴ = ^{0 4 ^ 4} = (10,560 Hz)/24 = 440 Hz with a corresponding period T ⁴ = 1 f = 2,273 ps

In the prescribed manner, sine waves of equal resolution but different frequency can be synthesized with a common clock and a single primitive waveform. In other words, the primitive table sets the waveform while the resolution £ and the timers determine the frequencies of the generated sine waves. The following sample table shows the relationship between the argument of the sinusoidal function ⁰ measured in degrees (or in radians), the normalized unit sine wave function 0.5 0.5sin(0), and the times corresponding to the states of the sinusoids that oscillate at frequencies fmax in the ninth octave, f ⁶ in the sixth octave and f ⁴ in the fourth octave.

Although the table reveals a detailed pattern between 0° and 90°, for the sake of brevity, the detailed 15° descriptions of the other three quadrants are redundant and have been excluded (because the sinusoid is a symmetric function, all four quadrants can be constructed from the data of a quadrant). The time required to complete the 360° cycle of a sine wave, that is, the period T, depends on the frequency of the sine wave. For example, according to the above calculations, sine waves having frequencies f ⁹ , f ⁶ , and f ⁴ comprise periods of 71 ps, 568 ps, and 2273 ps respectively. Specifically the value of the function 0.5 0.5sin(0) = 1 when the argument 0 = 90° = n / 2. The period of the sine wave T occurs four times this duration, when 0 = 360° = 2n. For example, a 6th octave sine wave tuned in the key of A requires 142 ps to complete one quarter of its cycle, so its period is T ⁶ = 4(142.05) = 569.2 ps.

FIGURE. 50 illustrates the described chord synthesis combining two sine waves using a single waveform primitive, using clocks generated from a binary cascading counter, the time-independent time-based waveform primitive, in this example with a resolution £sym = £x = 24 (not shown), transforms time-based sine wave tables 647 and 648 into a key of D comprising frequencies of f ⁶ = 1.168 Hz and f ⁴ = 292 respectively. The component sine waves are then increased or decreased in amplitude by digital gain amplifiers 626 and 624 having gain multipliers A ⁶ and A ⁴ performed arithmetically using digital multiplication operations. The two sine waves are then mixed by digital adder node 630 to produce the sum g(t) where...

g(t) = A ⁶ [0.5 0.5 sin(f ⁶ t)] A ⁴ [0.5 0.5 sin(f ⁴ t)]

= 0.5[A ⁶ + A4] 0.5 [A6 sin(f ⁶ t) A4 sin(f ⁴ t)]

Using a weighted average with a divisor (A ⁶ + A ⁴ ) produces...

During averaging, the term [A ⁶ + A ⁴ ] does not affect the offset 0.5 because it appears in both the numerator and denominator of the fraction change of the mean value of the function. The second purpose of the autoranging function, that is, to maximize the sine component by A at full scale, actually changes the average of the function. For To avoid changing the average value of 0.5, the autoranging function described in this document uses an additive correction factor 0.5 (1- Aa)

Auto Range [g(t)] = 0.5 ^0.5Aa [A f ⁶ t) A ⁴ sin(f

[A6+A4] ⁶ sin( ⁴ t)]

= A 0.5 ^0.5 [A Aa)

[A6+A4] ⁶ sin(f ⁶ t) A ⁴ sin(f ⁴ t)] (0.5 - 0.5

0.5A,

OT [A sin(ft)] 0.5(1 - Aa) [A6+A4] ^{6 6} t) A ⁴ sin(f ⁴

= A g(t) 0.5(1-A a )

[A6 A4]

As described, the sum g(t) is scaled by the autoranging function 631 using the scalar [Aa / (A ⁶ + A ⁴ )] which performs a weighted average of the sine wave components together with digital multiplication by the gain factor Aa. The resulting time-varying waveform f(t) 553 shown in tabular form 649 describes a chord 655 of two sine waves of frequencies f ⁶ and f ⁴ that have an average value of 0.5 and the ability to maximize the amplitude of the periodic function in the range of 0.000 to 1.000 without clipping or distortion. The PWM generator 555 then processes f(t) via the PWM transform 0 ^p [f(t)] producing synthesizer output data 488 comprising a string 499 of PWM data, called the synthesizer Gsynth(t). Unlike f(t) which is analog, the Gsynth(t) is digital in amplitude and switches between a ⁰ (low) and ¹ (high) state as a sequential series of pulses, incorporating analog information into its pulse widths. variables.

One problem that arises from the disclosed synthesis method is quantization noise. Although no single sine wave does not suffer from this problem, when two or more sine waves are added, noise appears in the waveform. This source of noise is illustrated in FIGURE. 51 A, where a cascade of binary counters 596 to 593 is used to produce three clocks 06, ⁰⁵ , ⁰⁴ , each with half the frequency of its input. Using a fixed primitive resolution of £ = 24, the resulting sine waves at frequencies f ⁶ , f ⁵ , and f ⁴ are shown in tabular form in data table 651. Inspection reveals that although the data for frequency f ⁶ have a only- to a correspondence with clock time ^{0 6} , the other frequencies do not change as quickly. For example, for both t = 0.1727 and t = 0.1784, the data value of the sine wave f ⁵ remains constant at 0.7500 even though the sine wave f ⁶ changes. Similarly, for the lower frequency sine wave f ⁴ , the data output over the interval from t = 0.1427 to 0.2497 remains constant at 0.6294, even though the data f ⁶ changes four times.

The impact of using a fixed resolution primitive with different clock speeds is shown in FIGURE. 51 B, where during a fixed time interval a variety of curves are contrasted. During the time shown, the sine wave of frequency f ⁶ shown in graph 652 is free of digitizing noise. In contrast, the sine wave of frequency f ⁵ generated by 06 /2£ shown in graph 653 exhibits a small but noticeable degree of noise. The sine wave f ⁴ in graph 654 two octaves below f ⁶ , ie where f ⁴ = 06 / £4 at £ = 24, shows substantial noise. The noise problem is manifested in the two-sine chord in graph 655 combining f ⁶ and f ⁵ and even more exaggerated in graph 656 illustrating the sinusoidal sum of the frequencies f ^{5 and} f ⁴ .

A solution to this problem is illustrated in FIGURE. 52 A where three different frequencies f6 , f ⁵ and f ⁴ are generated from a common clock frequency 06 . Instead of scaling the clock rate, the resolution is scaled, using higher resolution primitives to generate lower sine frequencies. Specifically in lookup table 616, £6 = 24 while in lookup table 615 the primitive resolution doubles to ^£5 = 2£6 = 48 and similarly ^£4 = 4£6 = 96 in lookup table 614. The resulting waveforms have frequencies

f6 = 06 /£6

f5 = 06 /£5 = 06 /(2£6)

f4 = 06 /£4 = 06 /(4£6)

As such, the sinusoidal frequencies f6, ^f5, and ^f4 generated from a common clock 06 are all factors of two of each other as shown in table 661. Thus, the time steps are constant for all generated frequencies. . The resulting curves shown in FIG. 52 B, including sine waves 662, 623, and 624, as well as chords 665 and 666, show no signs of quantization errors at this resolution. The frequency ratio of any two sine waves using this method remains accurate because previously defined criteria

holds when 0x = 0y.

This method, referred to herein as scaled summation primitive 660, is contrasted with a single summation primitive 650 for a chord mixing three synthesized sine waves in FIGURE. 52 C. On the single addition block diagram primitive 650, the sine wave-looking tables 616, 615 and 614 are identical in their resolution £ = 24 but are fed by three different clocks 0 6 , 0 5 = 0 6 /2, and 0 4 = 0 6 /4, generated from a binary cascade counter. A time graph of the resulting 659 chord shows significant digitizing noise. In contrast, the scaled primitive addition 660 employs a common clock 0 6 to drive three different resolution lookup tables 616, 615, and 614 with increasing resolutions £ x = 24, 48, and 96 for x = 6, 5, and 4 in the order correspondent . The resulting 669 waveform shows no signs of digitizing noise at this resolution.

To limit the maximum size of the primitive lookup tables, the audio spectrum can be divided into bands, for example, upper, mid and lower scales and also an infrasonic band (i.e. below 20 Hz) for zero and octaves. negative. Such an approach is employed in the four-rank scaled synthesis primitive block diagram shown in FIGURE. 53. In this exemplary primitive processor, tuner 599 includes system clock counter 640 and symbol clock counter 641 that converts system clock 0 sys to a fixed reference frequency 0 ref , eg, 5 MHz, and where the symbol counter produces a clock frequency where 0 sym is defined by the ratio 0 sym /0 ref = (32£f key ) / (5 MHz) according to the key select input 642, a note or key in the fourth octave. In the counter cascade comprising tuner 590, and three divide by counters 8672, 673 and 674, four frequencies are cogenerated to produce the clocks 0 sym , 0 6 = 0 sym /8, 0 3 = 0 sym /64, and 0 0 = 0 sym /512. Although counters 672 through 6734 each comprise a three-stage binary cascade counter, for the sake of brevity they have been represented as simple ^8 counters.

The highest frequency clock in the cascade, the clock symbol 0 sym , is used to synthesize sine waves in four bands. In the upper band 0 sym is used to generate sine waves f ⁹ , f 8 and f ⁷ according to selectors 609, 608 and 607 respectively. If a selector switch is enabled, the clock pulse for 0 sym is passed to the corresponding sine wave lookup table 699, 698 or 697 to produce f ⁹ , f 8 and f ⁷ sine waves as desired.

Specifically, the 699 sine wave with resolution £ ⁹ = 24, if enabled, produces an f ⁹ sine wave with frequency f ⁹ = 0 sym / £ ⁹ . This sine wave has a frequency 32 times the f key select key frequency and 1/24 th of the symbol frequency 0 sym . On the same upper scale, the 698 sine wave with resolution £ 8 = 48, if enabled, produces an f 8 sine wave with frequency f 8 = 0 sym / £ 8 = 0 sym / (2 £ ⁹ ). This sine wave has a frequency 16 times the f key select key frequency and 1/48 th of the symbol frequency 0 sym . Similarly, the 697 sine wave with resolution £ ⁷ = 96, if enabled, produces an f ⁷ sine wave with frequency f ⁷ = 0 sym /£ ⁷ = 0 sym /(4 £ ⁹ ). This sine wave has a frequency of 8 times the f key select the key frequency and 1/96th of the symbol frequency 0sym. Since the generation of sinusoids with frequencies f ⁹ , f8 , and f ⁷ comes from the same clock frequency 0sym, their waveform synthesis employs the same time increments, thus avoiding the aforementioned problem of within-scale digitizing error. superior .

The same clock 0sym is also divided by 8 in counter 672 to produce a lower rate clock 06 used for sinusoidal synthesis of f6 , f ⁵ , and f ⁴ on the midrange scale. If an n and selector switch 606, 605 and 604 is enabled, the clock pulse comprising 06 = 0sym /8 is passed to the corresponding sine wave lookup table 696, 695 or 694 to produce sine waves f6, f ⁵ , and f ⁴ as desired. Specifically, sine wave 696 with resolution £6 = 24, if enabled, produces a sine wave f6 with frequency f6 = 06 /£s = 0sym /(8£6). This si wave has a frequency four times the fkey select key frequency and 1/192nd of the symbol frequency 0sym. On the same half scale, the 695 sine wave with resolution £ ⁵ = 48, if enabled, produces an f ⁵ sine wave with frequency f ⁵ = 06 /£ ⁵ = 0sym /(16£6). T your sine wave has a frequency of 2 times the selection fkey of the fundamental frequency and 1/384th of the symbol frequency 0sym. Similarly, the 694 sine wave with resolution £ ⁴ = 96, if enabled, produces an f ⁴ sine wave with frequency f ⁴ = 06 /£ ⁴ = 0sym /(32 £6). This sine wave has a frequency equal to the selection frequency of the fkey and 1/768th of the frequency of the symbol 0sym. Since the generation of sinusoids with frequencies f6, f ⁵ and f ⁴ comes from the same clock frequency 06 = 0sym /8, the waveform synthesis uses the same time increments, so within the middle scale avoids the previously mentioned problem of scanning error.

To generate the sinusoid f ³ , f ² , and f ¹ on the lower scale, clock 06 is divided by 8 in counter 673 to produce a lower frequency clock 03. If any selector switches 603, 602, and 601 are enabled, the clock pulse comprising 03=0sym/64 is passed to the corresponding sine wave lookup table 693, 692 or 691 to produce f ³ , f ² and 0 sine waves as desired. Specifically, the 693 sine wave with resolution £ ³ = 24, if enabled, produces an f ³ sine wave with frequency f ³ = 03 /£ ³ = 0sym /(64£ ^í ). This sine wave has a frequency f ³ of 1/2th of the fkey selection frequency and 1/1536th of the symbol frequency 0sym. On the same lower scale, the 692 sine wave with resolution £ ² = 48, if enabled, produces an f ² sine wave with frequency f ² = 03/£2 = 0sym/(128£3). This sine wave has a frequency of 1/4th of the frequency select key fkey and 1/3.072th of the symbol frequency 0sym Similarly, sine wave 691 with resolution £ ¹ = 96, if enabled, produces 1/8th sinusoidal 0 with a frequency 0 = 03 /£ = 0sym/(256 £ ³ ). This sine wave It has a frequency of 1/8th of the fkey frequency selection key and 1/6.144th of the 0sym symbol frequency. Because the generation of sinusoids with frequencies f ³ , f ² and 0

¹ comes from the same clock frequency 03 = 0sym /64, the waveform synthesis uses the same time increments, so within the lower scale the previously mentioned problem of digitizing error is avoided.

The counter cascade can also be used to generate an infrasonic drive of the LEDs, that is, sine waves with frequencies less than 20 Hz. As shown, the output of the divide-by-8674 counter having a clock frequency of 00 = 0sym /512, if chosen with selector 600 produces a sine wave f ⁰ with a resolution £ ⁰ = 24 where the generated frequency is given by f ⁰ = 00 / £ ⁰ = 0sym / (512^). Using the above principles, the scaling concept can be extended to produce two lower infrasound frequencies f ^-1 and f ^-2 (as desired) by including two additional sinusoidal lookup tables with respective resolutions 48 and 96 driven by 00 clock.

In the above discussion, the use of time increments comprising constant intervals minimizes quantization noise, but requires higher resolution and higher resolution lookup tables which increase the memory capacity required within an LED pad.

As long as a lookup table has the required number of data points, a single table can be used to generate multiple octaves of data from a single clock. For example, a table of 24,576 points can be used to synthesize sine waves spanning 11 octaves with an angle precision of 0.0146484375° per data point. Combining a 337.920 Hz clock with an 11 octave universal primitive table, frequencies can be generated, for example, in the key-of-A ranging from f ⁹ = 0sym/£sym = 14.080 Hz in the 9th octave below at 13.75 Hz in the -1 st octave (including A at 440 Hz). This example is illustrated in the 4th column of the table below. Using the same symbol clock rate, i.e. in the same table column, if the number of synthesized frequencies is reduced to just 7 octaves, the size of the universal primitive data table is reduced to 1,536 data points which They span a range from 14,080 Hz in the 9th down octave to f ³ = 220 Hz.

Alternatively, using the same 7 octave universal primitive table, the covered frequency band can be shifted using a lower symbol clock rate. For example, as shown in the 5th column of the following table, with the clock rate symbol 0sym =168.960 Hz, a 1.536 data point universal primitive can cover a range from 7.040 Hz in the 8th octave down to 110 Hz in the 2nd octave. By reducing the size of the table and decreasing the symbol clock, a compromise in the frequency range of the sine wave and the size of the data table is also possible. Referring to the 6th column of the table below, a symbol clock rate of 0sym = 42,240 Hz can generate sine waves from 1,760 Hz in the 6th octave to 55 Hz in the 1st octave using a look-up table with only 768 data points.

The waveform synthesis process using universal primitive synthesis is shown in FIGURE. 54 where tuner 599 generates a programmable symbol clock 0sym = Oref /(32 £ fkey) according to key selection 642, transforming the clock into one or more sine waves varying in frequency, eg from f ⁹ and fo using universal primitive table 677, then combined according to digital gain amplifiers 678 with programmable gains Ax and summed in mixer 630 to produce g(t). As shown for each synthesized synth wave, the conversion from 0sym clock to time-based sine table 679 depends on the “£Resolution Selection” input 675 and the available resolution options. Table 676 is shown for, without limitation , demonstrate the table resolutions available from a minimum of 12 points up to a 16-bit resolution with 65,536 data points.The number of data points in the sine wave look-up table 677 determines the maximum resolution available.

In waveform synthesis using a universal primitive table, the same table is used to generate any sine wave with a precision equal to or less than the table's precision. For example, if the resolution of the 677 table is 96 points, that is, 3.75° increments, the same table can be used to generate sine waves with 48, 24, or 12 points, the higher the resolution, the less will be the synthesized frequency.

Various frequency sine waves are synthesized by searching the data for each angle or by skipping angles systematically. For example, in the following table, using a symbol clock with frequency 0sym = 224.256 Hz with rows 00, 04, 08, 0C, 10... results in a sine wave of 5,672 Hz while selecting each row in the table produces a 1.168 Hz sine wave.

Key selection and custom waveform synthesis

As described above, because periodic waveform generation involves a cascading counter with fixed multiples of frequency, the waveform synthesizer waveforms is essentially "tuned" to a specific key. The user interface (UI) and the resulting operation (UX or user experience) are shown in FIGURE. 55A, where a user selects the “Choose a key” menu 701 which facilitates key selection for various “musical scales”, “Physiological” (medical reported frequencies) scales, “C custom scales”, including manual entry, and “ Other” scales. It also includes a provision to return to the "default" balance settings. Selecting the "musical" setting brings up the "ENTER A KEY" menu 702. Choosing a note selects a predefined scale that will be loaded into the LED panel at the "f key select" input 641 running from the C means 261.626 Hz to B means 493.883 Hz. as stored in table 703. If a means is selected, then 703 will transfer the value of "A" 440 Hz into symbol clock counter 642 in accordance with 0 sym /O ref = (32 £ f key )/(5 MHz) generating a symbol rate O sym = (32 £ f key ) from which various frequency sine waves based on this scale are synthesized, e.g. f ⁹ = 0 sym / £ ⁹ . Below is a table of exemplary frequencies per octave for a variety of tunings shown below for musical keys C through F (https://en.wikipedia.org/wiki/Scientific_pitch_notation). The scales shown are called "equal temperament" tuning.

Below is a table of exemplary frequencies per octave for a variety of tunings for the musical keys of F# / Gk to B. The scales shown are called “equal temperament”.

Another option in the 701 user interface menu is the "Other" selection, other scales can be used to modulate the LEDs. These scales, including Pythagorean, Just Major, Mean-tone, and Werckmeister, shown in the table below, share the frequency of Middle C at 261.626 Hz with the even-tempered scale, but differ in the relative frequency ratio s between the scales. twelve semitones spanning one octave. For example, in an even-tempered scale, the pitch of A ⁴ above middle C is set to 440 Hz, but in other scales it ranges from 436.05 Hz to 441.49 Hz.

In custom mode, the user interface (UI) and the resulting operation (UX user experience) are shown in FIGURE. 55 B, where a user selects the "SELECT A KEY" menu 701 and selects "OTHERS" by bringing up the "SELECT A SCALE" menu 700. The user then selects an alternate tuning from the menu - Pythagoras, Solo Major, Midtone, and Werckmeister , opening the submenu 702 titled ENTER A KEY. Once the key (note) is selected, the frequency is selected from the tuning table below and loaded into key register 641 "fkey key select", which is subsequently transferred to the LED pad and finally load on the symbol clock counter 642. For example, the "A" key is selected from the Werckmeister scale, then the value of "A" at 437.05 Hz will be loaded into the symbol clock counter 642 according to 0sym/0ref= (32£fkey) / (5MHz). Consequently, the symbol counter generates a symbol rate 0sym = (32 £fkey) from which various frequency sine waves based on this scale are synthesized, eg fg = 0sym / £ ⁹ . Since the fundamental frequency fkey is used to generate then 0 sym then the entire nine octave scale is adjusted accordingly. For example, if fkey = f ⁴ is set to 437.05 Hz, then f ⁵ = 2f4 = 874.1 Hz, f6 = 4f4 = 1,748.2 Hz, etc.

And although the scales vary across the octave, they all agree with each other for frequency C. For example, the fifth octave C ⁵ frequencies shown in the table below are shown for comparison purposes, they all agree at f ⁵ = 525.25 Hz = ² f ⁴ . The notation used by the Pythagorean, major-solo, and half-tone scales differs slightly of the Werckmeister and even-tempered scales in the use of sharps # and flats k Although the exact tuning differences in PBT efficacy are not well characterized, scientific studies have confirmed the therapeutic efficacy of PBT treatments It clearly depends on the frequency. If in the user interface menu 701, the "Physio" item is selected, the frequency ranges reported in these medical studies as being therapeutically beneficial are used for the value of the f key . Otherwise, instead, the Custom button shown in FIGURE. 56 is selected in menu 701, a UX response comprising the custom menu 704 "ENTER A KEY" will appear. By entering a number on the keyboard, for example, 444 Hz as shown, and pressing the DONE button, the f key select register 641 is loaded with the custom key value 444 Hz and transferred to the f key generator. symbols 642. This value is then used to calculate the symbol clock rate using the symbol clock counter 642 according to the relationship 0 sym / 0 ref = (32 £ f key ) / (5 MHz) to produce an output 0 sym = (32 £ f key ).

The described PBT system is also capable of generating excitation patterns comprising a chord of three frequencies within the same octave, i.e. a triad, and optionally with an additional frequency such as a seventh or an octave higher than the root note of the chord. chord. A block diagram of an algorithmic chord builder is shown in FIGURE. 57A, where the tuner 590 configured in accordance with the selection f key 642 produces a symbol clock with frequency 0 sym = (32 £ f key ) which is fed to the chord construction algorithm 680. The chord construction, in turn , uses well-known mathematical relationships to generate the frequency components of several common chord types according to the "Octave, Chord, and Blend Selection" 681 entry selected from the Chord Builder 688 menu. Triad chords include selection of the 8th of the root note on which the chord will be built, and the type of chord to be implemented, i.e. major, minor, diminished, augmented, or custom. Quad chords include a 7th , a minor 7th , a major 7th , or any of the aforementioned triads with an added note one octave above the root. The relative amplitude or “mix” of the component frequencies is also specified in Table 688 which comprises the volume of the chord's root note, its third, fifth, and optionally a 7 th or note one octave above the root .

In operation, the chord construction algorithm 680 uses a scaled fraction of the symbol clock 0 sym to drive four lookup tables 682b, 684, 683, and 682a to synthesize four sine waves with a root fundamental at frequency fj f , a third at a frequency fj ³ , a fifth at a frequency fj ⁵ and a higher note either a seventh or a note one octave higher than the root (depending on the selection) with a fjt frequency. The three or four frequencies are then combined according to digital gain amplifiers 685A, 686, 687, and 685B with gains Ajf, Aj ³ , Aj ⁵ , and Ajt t respectively, and mixed in summing node 630 to create g(t ).

The exact frequencies of the notes in the chord depend on the selected octave value 681 and the select fkey value 642, ie the pitch or key of the binary cascading counters. Together, these synth settings determine the frequency or root note, also known as the root of the chord. The remaining notes in the chord are calculated as a ratio to the fundamental frequency of the chord according to the following table describing the frequency ratio of common musical chords ( https://pages.mtu.edu/~suits/chords. html ):

Although the chord builder can be a library item used in preset treatments and sessions, chords can also be created using a UI menu as shown in the FIGURE example. 57 B where a chord can be selected from the SELECT A CHORD menu 705 including major, minor, diminished, augmented, diminished, custom, 7th, minor 7th and all 7th chords. Selecting a custom chord opens the BUILD A CHORD 706 menu where the user can select the octave of the chord, the root note of the chord, the 3rd note i.e. the next higher note, the 5th note i.e. the third highest note and, optionally, whether to include a note one octave above the root note. Once the root note is selected, the 3rd, 5th, and 1 octave notes are arranged monotonically in rising frequency, even if the notes extend into the next octave higher. The second and third inversion of any chord must be entered as a custom chord using the lowest pitched note as the root note of the chord. Notes are evenly weighted in volume unless otherwise adjusted with the up and down arrows. Once the parameters are entered, after a timeout period or as indicated by other means, such as a double screen tap, the parameters are formatted in the data table 688 and finally transferred to the algorithm block of chord construction 680 within the smart LED pads where the sine wave See tables 677, digital gain stages 678 and mixer 630 create g(t). In the event that another menu item is selected from menu 705 SELECT A CHORD, a different sub-menu (not shown) will open which will allow the user to select the octave and relative amplitude mix of the constituent frequency components. The submenu, however, does not allow the user to change the notes as the relative frequencies present in a minor, major, diminished, etc. chord. are precisely defined.

Returning to the block diagram of the synthesizer in FIGURE. 44 , regardless of the synthesized waveform or how it was created, the g(t) waveform must be processed to create f(t) 553 limiting its range between 0.000 and 1.000 for the PWM generator 555 to realize the value in PWM function transform factor [f(t)] required to create the 488 synthesizer output file. Since the maximum duty factor of a PWM modulated pulse is 100%, that is, one for the full clock cycle, then a PWM representation of data greater than 1,000 is not possible. As such, the PWM transform is limited to 0% < ^ ^p [f(t)] < 100%, and thus 0.000 < f(t) < 1.000. The AutoRange operation 584 averages the function g(t), while limiting the range of the data yf(t) to the unit function, that is, between 0.000 and 1.000.

An example of this function is illustrated in FIGURE. 58 A, the sum of sine waves 662, 663, and 664 results in the 669 chord. Although each of the sine waves spans the full range of 0.000 to 1.000, the sum of sine waves in the 669 chord does not encompass the full extension of a unit function. As such, the mathematical average of the chord, specifically 0.5, remains constant but the time-varying periodic function does not extend the full range of 0.5 ± 0.5. As the picture shows. 58 B, the 669 chord alone spans from 0.13 to 0.87 representing 74.4% of the full range. To increase the amplitude of the time-varying component, the averaging function is amplified by the scalar Aa. By setting Aa = 1.344, the 669 curve rises to the full range as shown in the 689 chord. To avoid a change in the average value of the function, the correction term 0.5 (1 - Aa) is included to keep the function centered at 0.5 to avoid clipping. The result is a unitary function f(t) having a mean value of 0.5 with a full-scale periodic function having the same time-varying frequency dynamic components as the synthesized waveform g(t).

FIGURE. 59 illustrates the process by which the PWM generator function 555 converts the unit function f(t) 553 into the synthesizer output file 488 describing the PWM synthesizer Gsynth(t) 490 waveform. As shown , function table 554 contains a description of the time to versus the value of the function f(t) at each time increment. For example, at to = 5 ps the function f (t) = 0.5 and remains at that value until at t ⁰ = 10 ps the value of the function changes to f(t) = 0.8. The output of the transformation 0 ^p [f(t)] changes this time dependent table into a 489 PWM table where at time ton = 5.00 ps the state goes high, i.e. the LEDs turn on and the time to = 5.10 ps the LEDs turn off until at the moment to = 5.20 the LEDs turn on again. Given that the LEDs were on from time 5.00 to 5.10 for a duration of 0.10 ps and the period T = 1/0x until the LEDs turn on again is 5.00 to 5.20, or a duration of 0.20 ps, then the duty factor of the pulse at D = A to / T = 10 ps / 20 ps = 0.50 or 50%, then the duty factor is equal to the function f(t) = 0.5 during this interval and up to the time to = 10 ps when the duty factor changes to 0.8 or 80%. The resulting synthesizer output file 488 is graphically illustrated in PWM pulse string 675.

Examples of PWM output 490 using the transformation 0 ^p [f(t)] for a variety of non-sinusoidal functions are shown in FIGURE. 60 including PWM bitstream 670 for a constant function 560 where f(t) = 1,000, PWM bitstream 671 for a sawtooth function 561, and PWM bitstream 672 for a triangle function 562. The same PWM transformation 0 ^p [f(t)] can be used to encode audio samples of any audio sample, including simple tones like a triangle, strings like a guitar or violin, complex tones like a cymbol crash, or music.

PWM player operation

Reviewing the block diagram of FIGURE. 43 , the Gsynth(t) = 0 ^p [f(t)] output of the waveform synthesizer 483 is the input of the PWM player 484. The PWM player then combines the Gsynth(t) synthesizer with the Gpulse waveform. (t) 492 to produce a chain of 493 pulses. The function of the PWM player is twofold:

• To generate an audio spectrum PWM pulse chain Gpulse(t) with a dynamically controlled duty factor D ^pwm .

• To perform a dynamic "gate", ie to block or pass the contents of Gsynth(t) depending on the state of Gpulse(t).

The truth table for the above function can be described in logical pseudocode as

If Gpulse(t) = 1

Then PWM Player OUT = Gsynth(t)

Else PWM Player OUT = 0

Since Gpulse(t) comprises a string of PWM pulses, the waveform alternates between logic high and logic low states. Specifically, whenever the function Gpulse(t) = 1, that is, the PWM pulse 492 is in its high or logic "1" state, the digital state of the Gsynth(t) is accurately reproduced on the output of the PWM player. 484. For example when Gpulse(t) = 1 then if Gsynth(t) = 1 the output of the PWM player 484 is high and if Gsynth(t) = 0 then the output of the PWM player 484 is low. However, whenever the function Gpulse(t) = 0, that is, the PWM pulse 492 is in its low or logic "0" state, the digital state of the Gsynth(t) is forced to zero, ignoring the state of the entrance. Gsynth(t). Logically, this function is the same as the AND gate. Mathematically, it is equivalent to digital multiplication where the output of the 492 PWM player is given by the product Gsynth(t) • Gpulse(t) . The actual implementation of the PWM player 492 may be accomplished in hardware, software/firmware, or some combination thereof.

Illustrated schematically in FIGURE. 61 A, PWM player 484 comprises PWM clock counter 710, pulse width modulator 711, digital inverters 712A and 712b, and AND gate 713. Inputs to PWM player 491 include clock reference 0 ret, 488 synth output and 491 PWM player parameters. In operation, the 0 ret = 5 MHz reference clock provides a time reference with period Tref = 0.20 ps as an input to the PWM counter 710, generating a 0 ^pwm = 20 kHz clock. W ith of a period T ^pwm = 5 ps, 250 times more than the reference clock 0ret period, the 711 pulse width modulator generates a sequence of PWM pulses 492 variable duration ton = D ^pwm T ^pwm does according to table 714 is defined in the PWM parametric input of player 491. For example, in table 714 from 0 to 180 seconds, the Gpulse(t) is pulsed at a frequency of 2,836 Hz with a duty factor of 60%, then after which the pulse rate changes to 584 Hz. At time t = 360 sec, the pulse rate returns to 2.836 Hz. In terms of the 492 pulse string, during the interval 0 to 180 seconds, the period T ^pwm = 0.43 ms and the on time, the portion of the period that the pulse is in its high state, is given by ton = D ^pwm T ^pwm = (60%)(0.43 ms) = 0.26 ms.

The off portion of the pulse is given by toff = T ^pwm - ton = (0.43 ms) - (0.26 ms) = 17 ms. When the pulse rate changes to 584 Hz, the period increases to 1.712 ms with a trigger time of 1.027 ms. As such, pulse string 492 is dynamically generated by pulse width modulator 711 according to the dynamic conditions specified in table 491. The output of PWM player 484 shown as a gated PWM pulse string 493 includes the output built-in 494 waveform from the waveform synthesizer.

The operation of the 711 pulse width modulator essentially comprises two sequential counters, one to count the on time and the other to count the off time, where Gpulse(t) = 1 during the interval ton and Gpulse(t) = 0 during the toff interval. In pseudo-logic code, the operation of the pulse width modulator 711 can be described by defining the following subroutine.

Start the loop of the "Pulse Width Modulator" subroutine:

Load Registers Pulse Width Modulator [At, T ^pwm , ton]

clear counters

Start of pulse count (1/0ref)

loop start

If Count (1/ 0ref) > At, exit the subroutine

Further

Define toff = (T ^pwm — ton)

Set Gpulse=1

Count pulses (1/0 ^pwm ) up to ton

Reset Gpulse=0

Count pulses (1/0 ^pwm ) for toff

loop end

The above subroutine titled "Pulse Width Modulator" is a software pseudocode description that performs the same function as block 711, i.e., executes a loop for an interval At comprising alternating digital pulses at logic state 1 during the duration ton and a logic 0 state for a duration (T ^pwm — ton) repeatedly until the clock count Tref = 1/Or exceeds At. The variables [At, T ^pwm , ton] are loaded into the subroutine from the sequence defined in table 714 or pwM player parameters 49 as shown in the following exemplary executable pseudocode where table queries are specified by the value in the (row, column) pair, i.e. table(row, column) where Row is a defined variable:

Executable code "Back pain treatment"

Load Table [PWM Player Parametrics]

set row = 0

loop start

Set At = table((Row 1), 1) - table(Row, 1)

Set T ^pwm = table(Row, 4)

Set ten = table(Row, 5)

If ^Tpwm = 1

Then

Execution Finished

Further

Call subroutine pulse width modulator [At, T ^pwm , ton] Increment row by 1

loop end

As described, the executable pseudocode above repeatedly reads table 714 loading data into the subroutine called Pulse Width Modulator with arguments for its duration At, the pulse period T ^pwm , and the PWM pulse time ton, incrementing the row number after completing each cycle. For example, starting Row = 0, then At is calculated by the difference of the time in the second row and the first row entries in the first column of the table, i.e. where table(2,1) = 180 seconds and where table (1,1 ) = 0, therefore At = 180 sec in the first loop of the code. Similarly, in the first row and 4th column, the data for the PWM period is T ^pwm = table(1,4) = 0.43ms, and in the first row and 5th column, the data for the PWM once is t on = table(1, 5) = 0.26 ms. At the end of the loop, the row number is incremented from 1 to 2, so new data is read from the second row where At = [table(3,1) - table(2,1)] = [360 s - 180 s] = 180 s, T ^pwm = table(2, 4) = 1.712 ms, and ten = table(2, 5) = 1.027 ms. This process continues until a null entry is found for T ^pwm , that is, T ^pwm = table(Row, 4) = 0. At that point, program execution is complete. Thus, as demonstrated, the functions of the PWM Player 484 and Pulse Width Modulator 711 can be performed using software or hardware, or some combination thereof.

For example, the PWM Player 484 function is schematically represented in FIGURE. 61 B consisting of set/reset flip-flop or S/R latch 720, ton and W counters 721 and 722, AND gates 723 and 724, inverter 725, pull-up resistor 733, as well as ton and toff registers 726 and 727. In In operation, pull-up resistor 733 is activated at the S input of S/R latch 720 which sets output Q to a logic high or "1" state. the flank Ascending this logical transition from 0 to 1 activates the load function of the counter 721 by copying the data from the register 726 into the counter. The logic high state of output Q is also an input to AND gate 723, and its reverse state, the output of inverter 725, presents a logic "0" input to AND gate 724.

As such, clock pulses from clock 0 ^pwm are routed through AND gate 723 to toff counter 721 but blocked by AND gate 724 from reaching toff counter 722. Therefore, toff counter 721 counts up. back for a while ton. During its countdown, the counter output 721 remains in a logic "0" state and has no effect on the S/R latch 720. At the same time, missing a clock input suspends counter operation. toff 722. Referring to the associated timing diagrams, during this interval from Tx to (Tx ton ), PWM clock 0 ^pwm 728 continues to count, reset signal 729 comprising input R to S/R latch 720 remains low, array signal 730 comprising input S to S/R latch 720 remains low (except for a start pulse not shown), and output Gpulse(t) 731 remains high.

Once ton counter 721 completes its ton interval countdown, the counter output momentarily goes high as shown by reset pulse 734. The rising edge at the R input of S/R latch 720 resets output Q to "0 " logic and disables the 0 ^pwm clock so that it passes through the AND gate 723 and drives the close counter 721 ton. At the same time, the falling edge of the Q output causes a rising edge at the inverter output 725 activating a loading data from toff register 727 into toff counter 722. The logic high input to AND gate 724 enables routing of the 0 ^pwm clock to toff counter 722. Referring to the associated timing diagrams, during this interval of (Tx ton) to (Tx T ^pwm ), 0 ^pwm clock 728 continues to count, reset signal 729 comprising input R to S/R latch 720 remains low (except for reset pulse 734 at start of interval), set signal 730 comprising input S to S/R latch 720 remains low, and output Gpulse(t) 731 remains low. Once the toff counter counts down to zero after a toff interval, its output generates a short trim pulse 732 that switches the Q output of S/R latch 720 back to a logic "1" state, loading the value current ton register 726 in ton counter 721 and restart the whole process.

As shown, the output of Gpulse 731 alternates between a logic high state for a time ton = D ^pwm T ^pwm to a logic low state for a time toff = (1 - D ^pwm )T ^pwm . Each time a set pulse 732 is activated, the current value of ton register 726 is loaded into the ton counter 721. Similarly, each time a reset pulse 734 is activated, the current value of t off register 727 is loaded. load on the toff counter 722. In this way, the PWM player parameter file 491 can dynamically change the frequency and the duty factor of the PWM player producing a waveform identical to its equivalent software implementation. Note that the resistor 733 used to pull the S input to S/R latch 720 high during startup has a high resistance and cannot overcome the toff counter logic low state output 722 once startup is complete and power to the circuits has stabilized.

In conclusion, in the PWM player, the fPWM frequency and a corresponding duty factor D ^pwm change with time according to a specific playback file, thus defining a PWM sequence of pulses of different durations of ton and W. Note that the pulse frequency f ^pwm = 1/T ^pwm of the pulse width modulator is less in frequency than the 0 ^pwm = 20 kHz clock used to control the modulator. Also, the PWM frequency fpwM is well below the 0sym oversampled clock used by in the PWM generator ^ ^p [f(t)] in the waveform synthesizer block, i.e. 1/^sym >> 1/0PWM ^f PWM.

LED Driver Operation

The third stage in a distributed PBT system LED player is the LED driver circuit. Referring to FIG. 43 , the function if the 485 LED driver is to convert its Gsynth(t) • Gpulse(t) input together with an optional 496 time-dependent reference current into one or more analog control signals, ie, 497 LED drive flux The added signal equal to aIref(t) • Gsynth(t) • Gpulse(t) is then used to control the current in numerous LED strings as illustrated by example waveform 498.

On the block diagram of the 485 LED driver in FIG. 62 , a greater detail of the operation of the LED driver is shown. Although the illustration shows two PWM pulse string inputs IN ¹ 493 and IN ² 750 and only two outputs for the 743a and 743b drive LED strings, it will be understood by those skilled in the art of PBT that any number of synthesized waveforms, e.g. example of 1 to 16 may be required, and the number of LED strings may vary from n = 1 to 36 strings (or even more on large fixtures), although for smaller LED pads the number of strings will likely vary from 8 to 24. It is also understood that the number of series-connected LEDs "m" can vary from string to string for such a long time that full series connection does not require voltages greater than V ^led to function properly.

As shown, the 485 LED driver contains two buffers per input, for example, where IN ¹ requires 744a and 744b inverters and IN ² requires 745a and 745b inverters, as well as a 710 PWM clock counter, LED pad driver 747, various output channels I ^led1 , I ^{led 4} ,... where each channel includes a source or sink of controlled current, and optionally includes a D/A converter and a data register I ref associated. For example, the output I ^ledi as shown includes a controlled current sink 740 that drives an LED string 743a, a D/A converter 741a that produces the reference current lren , and an associated data register lren 742a. Similarly, output I ^led4 includes a controlled current sink 740d driving an LED string 743d, a D/A converter 741d producing the reference current I f , and an associated I f data register 742d. The optional crosspoint matrix 746 is used to dynamically assign, ie map, inputs IN ¹ , IN ² , etc. to the outputs I ^led1 , I ^led2 , I ^led3 , I ^led4 , l ^led5 ... as required. Aside from its PWM waveform inputs, the Gsynth(t) • Gpulse(t) 485 LED Driver also requires the 749 LED Driver parameter file and reference clock 0 ref.

In operation, input waveforms are assigned to output channels that dynamically control the current for the assigned LED strings. For example, waveform 493 is input to IN ¹ and then assigned via crosspoint switch 746 to digital input En to current sink 740a and other channels (not shown). As detailed in the accompanying legend, the blackened circle on the crossover switch indicates a closed switch, ie a connection, while an open circle indicates no connection, ie an open circuit. Similarly, waveform 750 is input to IN ² and then mapped via crosspoint switch 746 to digital input IN ² to current sink 740d and other channels (not shown). At the same time, as synchronized by the PWM clock 0 ^pwm , the analog signal lren is supplied to the current sink 740a and the analog signal I f is supplied to the current sink 740d. Current s I ren and I ref ⁴ are set by the digital value s loaded into a I ^ref1 and I I ^ref4 register 742a and 742d and by the corresponding D/A converter s 741a and 741d . The resulting 748A and 748d control waveforms of the currents I ^led1 = alren and I I ^led4 = alref ⁴ . The design, implementation and operation of current sinks (or alternatively current sources) are described in the examples in the FIGURES. 20 A at 23 C. The LED Driver function can also be specified and executed using software in two steps, first by mapping the inputs to the outputs, eg.

Set "I/O Mapping" where

IN ¹ = IN ²

In4= IN ¹

In5 = IN ²

Although it is possible to change this mapping dynamically, it is more likely that the mapping will be executed only once per treatment and will not change during the entire treatment. In many cases, only one input is used. The executable code for the current current of each channel can be set to a constant value

Set "Output Currents" where

I ^{led i} = 20mA

I ^led 4 = 20mA

I ^led 5 = 20 mA

During factory calibration, an error term or Icalib curve is stored in nonvolatile memory for each channel, eg, where Icalib ¹ = 1.04 mA, Icalib ⁴ = -0.10 mA, I calib ⁴ = 0.90 mA. The LED pad also stores a value of the mirror ratio a, eg where a = 1 /p = 1,000,000 which means that a milliamp output current requires a corresponding microamp reference current. Before playback begins, the pad | ^j C calculates and stores the values of I ref for each channel where

Iref values are stored in the digital equivalent form in Iref registers 742a, 742d, 742e, etc. in volatile memory before program execution. If the target LED current value changes, the register value can be overwritten prior to program execution, or dynamically "on the fly" as treatment progresses. For example, using executable pseudocode, the dynamic LED unit can comprise

Executable code "Back pain treatment"

Load table "drive" [LED Drive Parametrics]

Load "calib" table [LED Calibration]

Set to = LED Configuration [row, column]

set row = 0

loop start

Set At = table "unit" ((Row 1), 1) - table "unit" (Row, 1)

If At = 0

Then

end execution

Further

Set

I ref ¹ = [table "drive" (Row, 2) table "calib" (1,1)] / a

I ref ⁴ = [table "drive"(Row, 5) table "calib"(4,1)] / a

I ref ⁴ = [table "drive" (Row, 6) table "calib" (5,1)] / to Count (1 / 0 ^pwm ) pulses to table "drive" ((Row 1), 1) Increment row in 1

loop end

During execution, the Iref value for each channel is set by an [I ^led + Icalib ] / a where I ^led1 = “drive” (Row, 2), I ^led4 = “drive” (Row, 5), etc. and where column 2 cells contain the current LED drive data for I ^led2 , column 5 contains I ^led4 data, etc. The row value is used to define various intervals for a treatment, for example up to 540 sec carry out 20 mA and thereafter carry 23 mA.

If all channels carry the same current, the channel-specific columns can be removed from the table and replaced by a single column, as shown below.

The program can also call a function instead of a table, for example in the Headache Treatment example

Executable code "Headache Treatment"

Load "calib" table [LED Calibration]

Set to = LED Configuration [row, column]

Set fLED = 5.5

Start of pulse count (1/0ref )

set t = 0

loop start

Set t = t (1/ 0ef )

if t > tfinal

Then

Set Iref = 0

Further

Setting I ^led (t) = [20mA] [0.5 0.5sin (2nfLED t)]

Set "Reference currents per channel"

Iref ¹ = [I ^led (t) table "calib"(1,1)]/a

Iref ⁴ = [I ^led (t) table "calib"(4,1)]/a

Iref ⁴ = [I ^led (t) table "calib"(5,1)]/a

loop end

In the example above, the 20 mA sine wave is generated by a mathematical function for the reference current I ^led (t) with a defined frequency, say 5.5 Hz, using the clock Iref (or optionally a multiple of the clock). same). The desired output current I ^led (t) in each instance is corrected on a channel-by-channel basis by the calibration table data before being converted by the mirror ratio a into the corresponding Iren reference current registers 742a, 742, 742e, etc According to the “Set t = t (1/0ref)” instruction, each loop at time t is incremented by a duration (1/0ef ) and the sum is stored in the variable t, thus overwriting the previous value. As such, the variable t acts like a clock that increments with each cycle of the program. The clock continues counting and repeatedly generates the sine wave with a fixed periodicity of T ^led = 1/E ^ed until the terminal condition t > tfinal is met.

LED player in distributed PBT system

In the LED playback operation of FIG. 43 , the waveform synthesizer sequence 483, PWM player 484, and LED driver 485 produce the LED drive stream 497. In playback operation, waveform synthesis is performed at a frequency of 0sym clock significantly above the audio frequency spectrum, i.e. where 0sym >> 20 kHz, while the PWM 0 ^{pwm clock} used by the 484 PWM player and the LED O ^led clock used by the LED player 485s operate in the audio spectrum where 0 ^pwm ^20kHz and 0 ^led ^20kHz. In short, the operations of the LED player involve

• Generate a time-dependent analog unit function f(t) either mathematically using a unit function generator or using a primitive processor based on an oversampled lookup table.

• Conversion of the unit function f (t) into a PWM pulse flow using the transformation Gsynth (t) = 0 ^p [f (t)] .

• Generation of an audio spectrum PWM pulse chain G pulse (t).

• Gating, ie, logically ANDing, the Gsynth(t) with the PWM pulse chain Gpulse(t) to produce a Gsynth(t) • Gpulse(t) multiplicative unit function output.

• Driving LEDs with time-varying analog current aI ref (t) pulsed by the output function of the LED player unit whereby the I LED = aIref (t) • Gsynth (t) • Gpulse (t).

Figures 63 through 65 illustrate examples that demonstrate the versatility of the described LED player for a variety of waveforms.

FIGURE. 63 A illustrates a constant function f(t) = 1761 that results in a constant time-invariant Gsynth waveform 762 where 0 ^p [f (t)] = 100%. The constant 0 ^p [f(t)] is then multiplied by the PWM pulse string 773a with D=50% producing the pulse string 774a comprising Gsynth(t)•Gpulse(t). Multiplied by a constant reference 781a to source 20 mA, the resulting waveform I ^led = aIref(t) • Gsynth(t) • Gpulse(t) comprises a 20 mA peak square wave 802a with a duty factor of 50 % and an average current of 10 mA.

FIGURE. 63B illustrates a function f(t) = 1 constant 761 that results in a constant time-invariant Gsynth waveform 762 where 0 ^p [f(t)] = 100%. The constant 0 ^p [f(t)] is then multiplied by the PWM pulse string 773b with D=20% producing the pulse string 774b having a synth value Gsynth(t) • Gpulse(t). Multiplied by a constant ref 781b rence to generate 50 mA, T he resulting waveform I ^led = aIref (t) • Gsynth (t) • Gpulse (t) comprises a 20 mA peak 802b square wave with a duty factor of 20% and an average current of 10 mA.

FIGURE. 63 C illustrates a function f(t) = 1 constant 761 that results in a constant time-invariant Gsynth waveform 762 where 0 ^p [f(t)] = 100%. The constant 0 ^p [f(t)] is then multiplied by the PWM pulse string 773c with D=95% producing the pulse string 774c comprising Gsynth(t) • Gpulse(t). Multiplied by a constant refers 781C to generate 10.6 mA, t the resulting waveform I ^led = aIref(t) • Gsynth(t) • Gpulse(t) comprises a 10.6 mA peak 802C square wave with 95 factor working % and an average current of 10 mA.

FIGURE. 63 D illustrates a function f(t) = 1 constant 761 that results in a constant time-invariant G synth waveform 762 where ^ ^p [f(t)] = 100%. The constant ^ ^p [f(t)] is then multiplied by the PWM pulse string 773a with D=50% producing the pulse string 774a with a value G synth (t) • G pulse (t). Multiplied by a 781d reference step to generate 20 mA 25% step-up at 25 mA., T he resulting waveform I ^led = aI ref (t) • G synth (t) • G pulse (t) comprises a square 20 Peak mA wave 802c with 50% duty factor and 10mA average current ramping up to a maximum 25mA square wave with 50% duty factor and 112.5mA average current.

FIGURE. 63 E illustrates a function f(t) = 1 constant 761 that results in a constant time-invariant G synth waveform 762 where ^ ^p [f(t)] = 100%. The constant ^ ^p [f(t)] is then multiplied by a constant value 771 with D = 100% producing a constant value 772 where G synth (t) • G pulse (t) = 100%. Multiplied by pulsed reference 782 to generate a 20 mA square wave, T he resulting waveform I ^led = aI ref (t) • G synth (t) • G pulse (t) comprises a 20 mA peak square wave 802a with the duty factor of 50% and an average current of 10 mA.

FIGURE. 63 F illustrates a function f(t) = 1 constant 761 that results in a constant time-invariant G synth waveform 762 where ^ ^p [f(t)] = 100%. The constant ^ ^p [f(t)] is then multiplied by a constant value 771 with D = 100% producing a constant value 772 where G synth (t) • G pulse (t) = 100%. Multiplied by the 783 sine reference to generate a 20 mA sine wave. The resulting waveform I ^led = aI ref (t) • G synth (t) • G pulse (t) comprises a 20 mA 803a sine wave with an average current of 10 mA.

FIGURE. 63 G illustrates a function f(t) = 1 constant 761 that results in a constant time-invariant G synth waveform 762 where ^ ^p [f(t)] = 100%. The constant ^ ^p [f(t)] is multiplied by a constant value 771 with D = 100% producing a constant value 772 where G synth (t) • G pulse (t) = 100%. Multiplied by the 784a sample from analog to digital to generate a plucked guitar string with a maximum value of 20 mA. The resulting waveform I ^led = aI ref (t) • G synth (t) • G pulse (t) comprises a 20mA 804A sample with an average current of 10mA.

FIGURE. 63H illustrates a function f(t) = 1 constant 761 which results in a constant time-invariant G synth waveform 762 where ^ ^p [f(t)] = 100%. The constant ^ ^p [f(t)] is multiplied by a constant value 771 with D = 100% producing a constant value 772 where G synth (t) • G pulse (t) = 100%. Multiplied by the 784b analog-to-digital sample to generate a cymbal sound with a maximum value of 20 mA, the resulting waveform I ^led = aI ref (t) • G synth (t) • G pulse (t) comprises a 20 mA sample 804b with an average current of 10 mA.

FIGURE. 64A illustrates a sinusoidal function 763 of f(t) = sin(ft) which results in a synthesizer Gsynth = ^ ^p [f(t)] as a continuously varying PWM pulse string waveform 764 with a synthesizer T of defined period. The PWM string ^ ^p [f(t)] is multiplied by a constant value 771 with D = 100% producing a digital pulse string comprising Gsynth(t) • Gpulse(t) comprising a PWM representation 775 of a sine wave . Multiplied by a constant 781a reference to source 20mA, the resulting waveform I ^led = aI ref(t) • Gsynth(t) • Gpulse(t) comprises a maximum 20mA 803a sine wave with 50% average current of 10 mom.

FIGURE. 64B illustrates a sinusoidal function 763 where f(t) = sin(ft), resulting in Gsynth = ^ ^p [f(t)] as a continuously varying PWM pulse string waveform 764 with a definite period synthesizer T . The PWM string ^ ^p [f(t)] is multiplied by a constant value 771 with D = 100% producing a digital pulse string Gsynth(t) • Gpulse(t) comprising a PWM representation 775 of a sine wave. Multiplied by a 781d reference step to generate 20 mA 25% boost at 25 mA. The resulting waveform I ^led = aIref(t) • Gsynth(t) • Gpulse(t) comprises a 20 mA sine wave 803b peak with 50% average current of 10 mA rising to a maximum sine wave of 25 mA with 50% average current of 112.5 mA.

FIGURE. 64C illustrates a chord of sinusoids 763 transformed by Gsynth = ^ ^p [f(t)] into a continuously variable PWM pulsestring waveform 764 with a definite period T synthesizer. The PWM string ^ ^p [f(t)] is multiplied by a constant value 771 with D = 100% producing a Gsynth(t) • Gpulse(t) digital pulse string comprising a 776 PWM representation of a sine wave chord . Multiplied by a constant 781a reference to source 20mA, the resulting waveform I ^led = aIref(t) • Gsynth(t) • Gpulse(t) comprises a 20mA string of 803c sine waves with 50% average current of 10mA.

FIGURE. 64 D illustrates a sawtooth waveform 763 transformed by Gsynth = ^ ^p [f(t)] into a periodically varying PWM pulse string waveform 767 with a definite period synthesizer T. The PWM string ^ ^p [f(t)] is multiplied by a constant value 771 with D = 100% producing a digital pulse string Gsynth(t) • Gpulse(t) comprising a PWM 777 representation of a sawtooth waveform . Multiplied by a constant 781a reference to source 20 mA, the resulting waveform I ^led = aIref (t) • Gsynth(t) • Gpulse (t) comprises a 20 mA 804 sawtooth waveform with 50% average current of 10mA.

FIGURE. 64 E illustrates an audio sample of a guitar string 768a transformed by Gsynth = ^ ^p [f(t)] into a periodically varying PWM pulsechain waveform 769a with a definite period Tsynth. The PWM string ^ ^p [f(t)] is multiplied by a constant value 771 with D = 100% producing a string of digital pulses G synth (t) • G puiso (t) comprising a PWM 779a representation of a sawtooth wave. Multiplied by a constant 781a reference to source 20mA, the resulting waveform I ^led = aI ref (t) • G synth (t) • G pulse (t) comprises a 20mA 805a audio sample with 50% current 10mA average.

FIGURE. 64F illustrates an audio sample of a guitar string 768a transformed by G synth = ^ ^p [f(t)] into a periodically varying PWM pulse string waveform 769a with a defined duration. The PWM string ^ ^p [f(t)] is multiplied by a constant value 771 with D = 100% producing a digital pulse string G synth (t) • G pulse (t) comprising a PWM representation 779a of a string of guitar. Multiplied by a constant 781a reference to source 20mA, the resulting waveform I ^led = aI ref (t) • G synth (t) • G pulse (t) comprises a 20mA 805a audio sample with 50% current 10mA average.

FIGURE. 64G illustrates an audio sample of a cymbal crash 768b transformed by G synth = ^ ^p [f(t)] into a periodically varying PWM pulse chain waveform 769b with a defined duration. The PWM string ^ ^p [f(t)] is multiplied by a constant value 771 with D = 100% producing a string of digital pulses G synth (t) • G pulse (t) comprising a PWM representation 779b of a shock of cymbals. Multiplied by a constant reference 781a to source 20mA, the resulting waveform I ^led = aI ref (t) • G synth (t) • G pulse (t) comprises a 20mA audio sample 805b with 50% current 10mA average.

FIGURE. 65 illustrates a sinusoidal function 763 where f(t) = sin(ft), resulting in G synth = ^ ^p [f(t)] as a continuously variable PWM pulse chain waveform 764 with a T synth of defined period. The PWM string ^ ^p [f(t)] is multiplied by a PWM pulse 77 1d of a fixed period with D = 67% producing a digital pulse string G synth (t) • G pulse (t) comprising a representation PWM cut 778 of a sine wave closed by a lower frequency PWM pulse. Multiplied by a const 781a ant reference to generate 30 mA, the resulting waveform I ^led = aI ref (t) • G synth (t) • G pulse (t) comprises a 30 mA chord of 803e sine waves with an average current of 10mA.

In order to run PBT treatments, first the LED player is downloaded from the PBT driver into the LED pad, followed by the specific LED playback file to be executed. Once the LED Player is downloaded, there is no need to reload the LED Player each time a new treatment is selected. New playback files can be loaded repeatedly and new treatments or sessions can be run as long as the player remains in the volatile memory of the LED panel. However, turning off the PBT system or disconnecting an LED pad from the PBT controller erases the LED player software from the volatile memory of the LED pad and must be re-installed on the pad before an LED playback file and treatment or session can be run. begin. Although the program wipe problem can be avoided by storing the LED player file in non-volatile memory, for security reasons, it is preferable to write the program in volatile memory, such as SRAM or DRAM rather than on the non-volatile EEPROM or flash memory. Thus, any attempt to reverse engineer the contents of the program is lost with a power outage, and the hacker's efforts to extract the program are thwarted by the immediate loss of the executable code.

As the picture shows. 66 , the LED playback file 830 containing payload data 831 is transferred to volatile memory 832. The payload is decompressed to extract the waveform primitives 487 and waveform synthesizer parameters 486 loaded into the waveform synthesizer 833, PWM playback parameters 491 loaded into the PWM player 834, and LED controller parameters 749 loaded into the LED controller 835. An example of payload data content 831 is shown in FIGURE. 67 including the contents of waveform primitives 487, waveform synthesizer parameters 486, PWM player parameters 491 and LED driver parameters 749. The waveform synthesizer parameters 486 comprise the information necessary to execute a specific treatment or session, ie, an instruction file. The general instructions file for waveform synthesis includes the following:

• The waveform synthesis method used by the file, ie function synthesis or primitive synthesis.

• The tuning (key) of the program, ie the setting of the fkey register for synthesis. Available PBT synthesis keys comprise predefined binary multiples of a 4th note octave, the harmonic multiples generated spanning the audio spectrum from 9th to -1st octaves. Scales include default, musical, physiological, other, and custom. While the default and musical scales are balanced; The “Other ” submenu includes alternate tunings such as Werckmeister, Pythagoras, Just-Major, and tone scale meanings. The "physio" physiological scale is based on empirically derived scales derived from observation. The “custom” user interface / user experience allows the user to manually set the fkey value as a 4th octave frequency (entered in Hertz rather than per note) and passes this frequency to the fkey register.

• The waveform sequence to be synthesized, including the duration of each waveform "step" in the synthesis. A completion code is included at the end of the program to indicate that the treatment or session is complete

• If the synthesis of functions is used, the mathematical expression of each function and its frequency f . Available periodic waveforms using function synthesis include constant sine, sawtooth, triangle, and single frequency waveforms.

• If primitive synthesis is used, each primitive subroutine call includes the fx frequency and resolution of the primitive's playback subroutine. The available primitive-based waveform subroutine calls include constants, sawtooth, triangle, sine waves, or audio samples. Primitive-based sine chord synthesis is also available using a "chord builder" subroutine.

• The chord builder subroutines include specifying the chord construction method and the octaves and notes present. Chord construction algorithms include "octave" synthesis and "tri/quad" chord synthesis.

• In octave synthesis, any chord can be described by its octave component numbers "Oct" (a number from 1 to 9 describing the fx frequency made according to the fkey register setting) along with the corresponding primitive resolution of each octave £x and mix Ax. In a tri/quad chord builder, three or four fixed-resolution sine wave notes spanning a single octave can be combined using adjustable amplitude set by gain Ax. Available chord triads include major, minor, diminished, augmented, each of which includes an optional fourth note 1 octave above the chord root. Alternatively a fourth note can be added to form a 7th chord, specifically a quad note chord that has a 7th, major 7th, and minor 7th construction. A "custom" chord allows the generation of any three-note chord spanning an octave, even in dissonance, with an option for a fourth note 1 octave above the root of the chord.

• All Chord Builder outputs can be scaled to increase the periodic chord amplitude using digital gain Aa without changing the 0.5 mean value of the unit function.

• All waveform synthesizer outputs represent unitary functions, that is, they have analog values between 0.000 and 1.000 converted into PWM pulse strings with a duty factor between 0% and 100%. Any synthesized waveform outside this range will be spoofed.

In operation, only the waveform primitives 486 required by a playback file specified by the waveform synthesizer parametrics 487 are downloaded to an LED pad. The downloadable primitive library 487 includes a selection of sine wave primitives in various resolutions £, for example using 24, 46, 96, 198 or 360 point or 16 bit resolution. In the sample library, it also includes 24-point triangle and sawtooth waveform descriptions, although other resolutions can be included without limitation. Other library components, for example with £ = 96, involve chords including double or octave chords comprising two sin-e waves one octave apart from f and 2f, two octaves apart from f and 4f, or possibly four octaves apart in f and 16f, or five octaves apart at f and 32f.

Other options include three-octave chords like [f, 2f, 4f] that span two octaves; [f, 2f, 8f] or [f, 4f, 8f] spanning three octaves, or for example, four octaves with [f, 2f, 16f], [f, 4f, 16f] or [f, 8f, 16f] . Other triads include major, minor, diminished, and augmented chords, for example, [ f , 1.25f , 1.5f], [ f , 1.2f , 1.5f ], [f , 1.2 f , 1.444f]. Triads can be modified into quadruple chords by including a note one octave above the root.

The PWM player parameter file 491 includes settings for constant or pulse mode. In pulse mode, the playback file comprises a sequence of PWM frequencies fpwM and a corresponding duty factor D ^pwm versus playback time, thus defining a PWM sequence of pulses of variable durations ton and W Note that the frequency de pukse fpwM of the puse width modulator is less in frequency than the 0 ^pwm = 20 kHz clock used to drive the modulator. To conclude, in PWM player operation, the PWM frequency fpwM is not fixed by varies with the playback schedule specified in the PWM parametric file 491. Although the fpWM frequency can be as high as 0 ^pwm clock in most cases is less, so that fpWM ^ 0 ^pwm . Also, the fpWM frequency is in the audio spectrum, well below the 0sym oversampled clock in the supersonic range used by in the PWM generator ^p[f(t)] in the waveform synthesizer block, i.e., mathematically as fpwM^ 0 ^pwm << 1/0sym .

In the LED driver parametric 749, the drive function digital PWM inputs INx are mapped to the current sink enable Eny . For example, input IN ¹ is assigned to the current sink enable of channel 4 In ⁴ , input IN ² is assigned to the current sink enable In ¹ and In ⁵ (not shown) for channels 1 and 5 etc The current LED control comprises a file playback of alref versus time. The Iref value for each channel is set by the output of each corresponding D/A converter, which can comprise a constant, a periodic function, or an audio sample. Alternatively, a D/A converter can be used to supply the reference current for all output channels with the same function or constant value.

Initiation of playback in distributed PBT systems

After downloading the LED player and the LED playback file to an LED pad, playback is enabled by a start signal 840 and a PBT system timing control which can be implemented in software or using the exemplary circuit from the FIGURE. 68 including start/stop latch 842 comprising a set/reset or S/R type flip-flop, interrupt latch 843, system clock counter PBT 640, one-time start 848, AND logic gates 845 and 846, and OR logic gates 846 and 847. The two-input AND gate 845 acts as a system clock enabling the 0osc oscillator to the LED player, closed by start and control signals 840 and 841, and a variety of interrupts, specifically a intermittent timeout 844, a watchdog timer 845, or an overheat indicator 846.

At startup, a trigger 848 generates a pulse that immediately drives the output of OR gate 846 high. At the same time the firing signal triggers the S input set of latch interrupts 843 and its output Q high. When the user input "s pie" 840 is selected it pulses the latch start/stop Q output 846 high in a positive direction pattern. With the Q outputs of start/stop latch 846 and interrupt latch 843 high, then AND gate 845 is enabled. As such, oscillator 0osc is sent to the PWM player as clock 0sys, and divided by counter 640 as reference clock 0 ref.

The "pause" selection 841 generates a pulse that resets the start/stop latch output 842 to zero and suspends playback. Playback remains blocked until "start" 840 is selected canceling the pause command. As such, the start/stop latch 842 starts and stops the execution of the program. In the event that an interrupt occurs for whatever reason, i.e. if any of the inputs to OR gate 647 go high, the PR gate output will also go high thereby resetting the Q output of interrupt latch 843 to zero . With its low Q output the s output of the Y gates 846 and 845 also go low, disconnecting cl ock 0osc from the LED player and suspension treatment. This condition will persist until the cause of the interrupt is removed, the inputs to OR gate 647 are reset low, and a system restore pulse is sent to the S input of interrupt latch 843. For example, if a condition occurs of overtemperature, the temperature indicator will rise 846 and disable LED pad operation until normal temperatures return and the fault indicator is reset.

A unique security feature of the disclosed distributed PBT system is the blink timer. This timer works within the Smart LED Pad itself and is not dependent on the PBT controller. At regular intervals on the pC pad, for example every 20 or 30 seconds, the program counter interrupts the operation to execute an interrupt service routine (ISR). During this interval, the blink timeout flag is set to logic 1 while the LightPadOS software runs a security check regarding the LED pad's electrical connections, any priority messages or file updates, file parity checks, files, etc. Once the blink interrupt routine has completed, the blink timeout is reset to zero, the hardware watchdog timer is reset, and program execution returns to the main routine. After completing the ISR, the pC pad generates a system restore pulse to interrupt latch 843 and program operation is restarted. If the software has frozen for any reason, the program will not resume and the pad's LED strips will remain off. Otherwise, the LED Pad will resume operation after a defined interval, eg 2 seconds.

Another failure mode involves software frozen while the LEDs are on and emitting light. If the condition persists, the LEDs may overheat and present a burn hazard to the patient. To prevent dangerous conditions from arising, a hardware watchdog timer (independent of software for operation) counts down in parallel to the software program counter. If the software timer is frozen in a power-on state, the watchdog timer will not be reset and the watchdog timer will time out generating an 844 blink timeout interrupt and interrupting the operation of the PBT system until the condition is resolved. of failure.

In this way, the described distributed PBT system can be used to control the operation of the LED pad remotely. Additionally, the methods described in this paper can be adapted to drive multiple smart LED pads simultaneously from a common PBT controller.

Component communication through distributed PBT systems

Implementing the required communication between components in a distributed PBT system requires a complex communication network and a dedicated protocol designed to accommodate the combination of real-time data transfers and file-based, some of which are tied to security systems. According to FDA regulations, safety is an important consideration in the design of medical devices. In distributed systems, this concern is compounded by the autonomous operation of components. In the event that communication between devices in the distributed PBT fails or is interrupted, safety systems cannot malfunction. The topic of communication, safety, sensing, and biofeedback is discussed in greater detail in a related patent titled "Distributed Photobiomodulation Therapy Communication Devices, Methods, and Protocols," filed concurrently as a continuation-in-part application (CIP) of this patent.

As described, the delivery of LightOS data packets in a distributed PBT system can be achieved using a 4-layer communication protocol running over a wired bus such as USB, I2C, SMBus, FireWire, Lightening, and other wired communication media. However, if the distributed PBT system communication is over Ethernet, WiFi, over the phone over cellular networks (such as 3G/LTE, 4G, or 5G), or if the data is passed through a public router, the Communication cannot be done exclusively through the MAC address, that is, a layer 1 and layer 2 communication stack is not enough to execute the routing of data through the network.

For example, FIG. 69, the PBT controller 1000 communicates over Ethernet 1002 to the smart LED pad 1003 using a 7-layer OSI compliant communication stack, specifically where the PBT controller 1000 communication stack 1005 includes PHY Layer-1 and Data Link. Layer-2 running the Ethernet communication protocol over Differential Ethernet Signals 1004; network layer-3 and transport layer-4 that perform network communication in accordance with TCP/IP (Transfer Communication Protocol over Internet Protocol Network), and application layers defined by the LightOS operating system that comprise Session Layer-5 for authentication, Presentation Layer-6 for security (encryption/decryption), and Application Layer 7 for PBT system control and therapy. The communication stack 1006 of the LED light pad 1006 includes the corresponding layer-1 and layer-2 protocols for Ethernet and layer-3 and layer-4 for TCP/IP, along with layers 5 to 7 defined by LightPadOS. In peer-to-peer communication, that is, for communications that do not involve an IP router, the Ethernet connection 1002 operates as a private network over network layer 3. The LightPadOS smart LED pad operating system is a subset of LightOS and, therefore, they can communicate with each other as a single virtual machine (VM) despite being physically separated from each other.

Using the described 7-layer OSI communication stack, network communication in the described PBT system can be easily adapted to WiFi wireless communication. In the distributed PBT system shown in FIG. 70, the WiFi-enabled PBT driver 1010 powered by the power supply 1011 communicates via the WiFi signal 1012 to the smart LED pad 1013 using OFDM radio signals 1015 in accordance with IEEE standards for 802.11. WiFi communication protocols may include 802.11a, 802.1b, 802.11g, 8012.11n or 802.11ac or other related versions, depending on the chipsets used in the 1013 Smart LED Panel. The 1090 PBT controller can support the superset of all standard Wi-Fi protocols. Because WiFi cannot carry power, the 1093 Smart LED Pad must be powered via USB cable 1014b powered by AC/DC converter and DC power supply (block) 1014a or USB storage battery (not it shows). WiFi communication occurs through the full 7-layer OSI communication stack 10 16 present in the PBT controller 101 0 connected to the communication stack 101 7 present in the smart LED pad 101 3.

In operation, a WiFi radio shown in FIGURE. 71A converts wired communication link 1025 (eg, PCI, USB, Ethernet) to microwave radio 1024 by translating access MAC 1020a to radio access point 1020b using interface circuitry and related firmware 1022. In operation, signals from communication link 1108 pass communication stack 1021a as PHY signals 1119 a where the format is converted by interface 1022 to PHY 1119 b signals on WiFi communication stack 1021b and on radios 1026a through 1026n operating on various frequencies radio signals transmitted by a multiband antenna array for microwave communication 1024. In operation, the communication stack 1021a transfers the data 1023a in accordance with the layer-2 data link communication protocol where the interface circuitry and firmware 1022 converts them to WiFi data 1023b according to the layer-2 data link of the communication stack 1021b formatted for radios 1026a to 1026n This WiFi radio in turn connects to the PBT controller 131 to 135 also connected to Ethernet 2017 and USB 1028.

In FIGURE. 71B the same 1024 WiFi radio communicates with the 337 Smart LED Pad via the 1030 wired data link using PCI, USB, or Ethernet protocols to the 338 communication interface. This interface can also connect to other devices or sensors via USB 1033 and Ethernet 1032. An example of a distributed PBT communication network is shown in FIGURE. 72 where the 1052 WiFi Router communicates with the 1053, 1054, and 1055 Smart LED Pads over WiFi links 1012a, 1012b, and 102c, and the 1050 Central Control LCD UI/UX with System Control Window 1051a and Patient Window 1051b over the 1012b WiFi link. He The system also includes an inventive component, 1056 PBT WiFi Remote Control, useful for a nurse to start a treatment in a patient's room without the need to switch back to the 1050 central control LCD UI/UX screen.

With wireless connectivity, the PBT controller can be replaced by an application program running on a mobile device such as a cell phone, tablet, or laptop. For example, in FIG. 73 Cellular phone 1100 running PBT controller application software (eg, PBT “Light app”) connects to cell tower 1705 via cellular network 1704, eg, 3G/LTE, 4G, and 5G. Mobile phone antenna 1705 in turn connects to the Internet 1706 by Ethernet, fiber, or other means. The 1700 cell phone running the aforementioned Light app also connects to the 1701 Smart LED Pad using 1702 WiFi, where the 1701 Smart LED Pad is powered by the 1703a AC adapter and 1703 b cable. The 7-layer OSI communication stack 1714 of the radio tower 1707 uses mobile network data packets to connect with the Light application communication stack 1709 running on the cellular phone 1700. In turn, the Light application it also uses the 1709 7-layer communication stack to connect to the 1701 smart LED pad comprising the 1708 communication stack. As shown, the PBT communication stack 1709 mixes two 7-layer communication stacks, one for dialogue with the cell tower communication stack 1707 1705 and through the router to the Internet 1706 and a cloud-based server. (not shown), and another to connect to the 1701 Smart LED Pad and 1708 Communication Stack, where only Light Application Layer 7 bridges the two. In this way, the mobile phone 1700 running the aforementioned Light application functions as a PBT controller that communicates separately with a cloud-based computer server (not shown) via the Internet 1706 and with the smart LED pad 1708 but without relinquishing local control.

Because layer-1 PHY and layer-2 Data Link are not shared for layer-1 to layer-6 communication, the communication stack of the cell tower 1707 cannot directly access the communication stack of the cell tower. 1708 Smart LED Pad. Instead, only the Application-7 layer within the communication stack 1709 bridges the two communication networks. The application may comprise a dedicated Light application, which, like LightPadOS, functions as a reduced instruction set version of the LightOS operating system used in the dedicated hardware PBT controllers described above. In essence, the Light app emulates the operation of LightOS by facilitating PBT control functionality and its touchscreen-based control UI/UX. The Light app is made as software designed to run on the operating system used on the respective mobile device. For example, on smartphones and On tablets, the Light app is built to run on Android or iOS while on laptops, the Light app is built to run on MacOS, Windows, Linux, or UNIX. The conversion of the source code, the basic logic and function of the Light application, into executable code tailored to run on a specific platform is a conversion process called a "compiler".

The translation of source code into compiled code is therefore platform-specific, which means that multiple versions of the software must be distributed each time a hotfix, patch, or new version of the software is produced. The operation of a distributed PBT system based on a mobile device is shown in FIGURE. 74, where the mobile device 1100 hosts the Light app with control UI/UX interface 1130 to control the smart LED pads 1119a and 1119b via WiFi 1102. The mobile device can also connect to the Internet and cellular networks using the cellular link 1104 eg via 3G / LTE, 4G and 5G protocols.

An example of software control of PBT system operation is shown in example display 1120 in FIGURE. 75, where the UI/UX screen titled "choose a session" includes the treatment menu 1121 along with buttons for an "extended session" 1122 to increase the time of a PBT treatment. “Select a LED Pad” 1122 is used to pair the mobile device with specific smart LED pads. As shown, selecting the De-Stress treatment opens a second "Running" screen 1130 for monitoring an ongoing treatment showing the name 1131 of the treatment, for canceling 1132 or pausing 1133 a treatment. The window also displays the time 1134 remaining in the treatment, the step progress bar 1135, the treatment progress bar 1136 and the biofeedback 1137.

Boost other distributed components

The PBT controller can be used to control therapy devices other than LEDs. These peripheral components can include PBT laser wands and systems, autonomous LED pads programmed over a distributed PBT system, magnetotherapy pads and wands, LED masks, LED caps, LED ear and nose headsets, and more. LED Face Masks, Head Caps, and LED Beds are simply multi-zone PBT systems using unique LED delivery systems. Therefore, the electrical control is identical to the aforementioned PBT system as described. Generally speaking, the aforementioned distributed PBT system is not limited to LED activation, but can be used to activate any energy emitter placed next to a patient in order to inject energy into living tissue, including coherent light. of a laser, or the emission of variable magnetic energy in time. fields (magnetic therapy), electrical microcurrents (electrotherapy), ultrasonic energy, infrasound, far infrared electromagnetic radiation, or any combination thereof.

Because distributed therapeutic systems such as PBT laser, thermotherapy, magnetotherapy, and ultrasound therapy use different power emitters than LEDs, they require some modification to activate the power emitters using the described PBT controller. Some examples of adaptation of the disclosed PBT system for alternative therapies are described below:

PBT laser systems- FIGURE. 76 illustrates a portable PBT device or "wand" useful for laser PBT therapy. As shown, hand wand 1150 includes barrel arm 1153 with LCD1160 and control buttons 1161a and 1162b. The bottom of the barrel handle also includes a USB port 1162 needed to charge the 1166 battery. The barrel handle connects to a 1152 gimbal to the 1151 PBT header with clear faceplate 1154 containing the PCB 1155 with lasers 1156 and 1157 along with sensors 1158. An inventive feature is a circular conductive blade 1159 that is used to detect skin contact to avoid illumination of lasers unless the unit is in contact with tissue.

The block diagram of the portable PBT therapy block diagram of FIGURE. 77 includes pad pC 1181, clock 1183, volatile memory 1185, non-volatile memory 1184, and communication interface 1182 and Bluetooth 1190. Pad pC communicates via data bus 1187 to control UI 1177 with buttons 1161a and 1161b, UX display controller 1176 with 1160 LCD, 1174 laser controller and security system. As shown, the 1174 laser controller drives the 1156 and 1157 laser diodes. At the same time, the 1175 security system interface uses the 1188 contact blade signal and 1189 temperature sensor signals. The 1174 laser controller works with one 1173 laser power supply with one 1172 lithium-ion battery via 1171 battery charger and regulator powered by 1186 USB input.

The details of the safety sensors are shown in the FIGURE. 78 include heat measurement 1200 with diode PN 1202 (terminals A and K) and contact sheets 1159 with capacitors 1201a and 120b that form a closed circuit that conducts alternating current through a patient's tissue via the terminals C and C'. FIGURE. 79 illustrates a laser PBT portable security system that includes oscillator 1220, touch sensor capacitors 1201a and 1201b, and sense resistor 1221 along with differential amplifier 1222, low-pass filter 1223, comparator 1225, and reference. voltage oscillator 1224. In operation, voltage oscillator 1220 Vosc injects a fosc frequency into the series at the voltage divider formed between resistor 1221 and the series connection of capacitors 1201a and 1201b and a resistor 1221. At the frequency of fosc Switching, series-connected capacitors exhibit an equivalent impedance Z and drop a network voltage between nodes C and C' of V ^z = (Z ^c • lave) while the voltage drop across resistor 1221 is V ^r = R • wash . Equating the two equations V ^r = Vosc R / (RZ ^c ) ie, when the contact sheet sensor 1159 is not in contact with the patient's skin, the value of Z ^c is large and V ^r approaches zero. In such a case, the output of the differential amplifier is less than Vref , the temperature independent voltage reference voltage 1224. As such, the output of the eye safety comparator 1225 is grounded and the laser driver is inhibited. If the sensor sheet comes in contact with the skin, the AC impedance Z ^c drops significantly where, after removing the AC signal by low-pass filter 1223, the average DC voltage across resistor 1221 is higher. than V ref , thereby switching the output of the eye safety comparator to a logic high and sending a contact detection enable signal 1228 to the pC laser. Similarly, the temperature sensor 1202 is processed by the temperature protection circuit 1231a. If an overheat condition occurs, the 1232 overtemp flag is sent to the pC laser and the input to the logic and gate goes low, disabling the 1174 laser controller. In the absence of an overheat condition, then the overheat detection is acknowledged. contact 1228 provided and then logic gate 1226 will pass the digital value of PWM controller output 493, that is, laser controller 1174 is enabled.

FIGURE. 80 illustrates an exemplary schematic of a two channel laser controller. As shown, the PBT 1240 laser controller is similar to the aforementioned LED controller comprising of the 1181 pC laser, 1182 communication interface, 1183 clock, 1184 non-volatile memory, and 1185 volatile memory. Protection functions include protection against overheating 1131a with sensor 1202 together with eye protection 1131b. The fault signals and output from the pC laser PWM player are input into logic gates 1228a and 1228b, then buffered by two pairs of serial inverters 1247 and 1246. The output is fed to the digital inputs of the pC lasers. digital current sinks 1256 and 1257 in the 1174 laser controller. The 1245 dual output D/A converter is also used to control the analog value of the lLaser ¹ and kaser ² currents when the current sinks are conducting.

Controlled current sink 1256 is used to drive the string of lasers 1156a through 1156n with wavelength A ¹ . The 1257 controlled current sink is used to drive the string of lasers 1157a through 1157n with wavelength A ² in the 1242 laser array. The laser strings are powered by the output supply voltage V ^hv of the switching regulator. 1241 boost type comprising input capacitor 1265 PWM controller 1260, low power DMOSFET 1262, inductor 1261, Schottky rectifier 1263 and output capacitor 1264 with voltage feedback to controller 1260 PWM. Input to the 1241 laser power supply is supplied by the 1172 Lithium-Ion battery and 1171 USB Power Input battery charger. After 2. 5 - regulated voltage output V is also the output of battery charger 1171 and filter capacitor 1266 to power the components of the laser PBT control circuit 1240. If a higher voltage is required, the V ^hv power output used to drive the laser array can also be used to supply the PBT control of the laser after the boost converter is running.

Self-contained LED Pads for Photobiomodulation Therapy – Another peripheral compatible with the distributed PBT system are self-contained LED pads which are used in applications when a PBT controller or cell phone is not available or inconvenient to deliver emergency treatments, for example, in a battlefield or in a plane crash in a mountainous place. In operation, a single button located on the self-contained LED pad is used to select treatment. In general, there is no UX screen available for information. A Nd Although autonomous LED pads operate “autonomous” (i.e., by themselves) during therapy treatments, during manufacturing they are connected to part of a distributed PBT system to load their applicable programs and to confirm their successful operation.

The PBT software programs loaded on the LED pads vary depending on the markets and applications for which they are intended. For example, treatment programs uploaded to LED pads at a ski resort may include treatments for concussion (a common ski injury), while those used by paramedics may focus on treating injuries such as lacerations or Burns. In sports facilities and tennis clubs, self-contained LED pads for muscle and joint pain may be more common. In military applications, the primary field application is to slow or prevent the spread of infection in a gunshot or shrapnel wound.

The electrical design of the intelligent LED 337 of FIG. 14 is equally applicable stand-alone LED operation, except for the addition of a button to control power on/off and program selection. During programming, the entire PBT system is present, including power brick 132, PBT controller 131, USB cable 136, and stand-alone smart LED pad 337. In programming, the PBT controller configures the LED pad by uploading manufacturing data and downloading a PBT player and the preload LED playback files as needed. A portable scheduling system can also be used to reschedule pads once sold or deployed in the field, allowing the customer to reuse their inventory to accommodate various types of disasters, eg freezing in the winter, antiviral treatments in a disease outbreak or pandemic. , lung damage from the release of a nerve agent by a terrorist, etc.

The important factor in a self-contained LED pad is that the cost should be controlled using a standard design, i.e. using a common manufacturing flow and bill of materials (material construction) of the product for all applications and markets, and then using software downloads to customize the generic product. in a specific version of the application. In FIGURE. 1 shows an example of a general purpose pad. FIGURE. 81A comprising a self-contained pre-programmed LED smart pad shown top view 1281, underside view 1284, and side view including a single USB socket 1198. Cross section 1280 includes rigid PCB 1288; 1289 flexible PCB, 1991 and 1292 LEDs, 1290 sensor, and 1299 control switch. The 1281 LED polymeric pad cover includes the 1295 openings and 1296 cavity, the 1288 thin portion for the 1298 switch, and the 1287 protective clear plastic. 1280 LED Pad includes 1281 Flexible Polymer Top Cover with 1283 Ridge, 1284 Flexible Polymer Lower Cover with 1285 Ridge.

As described, self-contained LED pads do not use a display, radio link, or remote control, and therefore offer a limited number of preloaded treatment programs, typically one to five options as illustrated in FIGURE. 81B. As shown, a stand-alone LED pad in its off state 1257a will change to state 1257b after pressing switch 1293 once. After selecting this state after a short period of time, the treatment will start using the "Treatment 1" program. If you press the button a second time, the program will advance to state 1257c and "Treatment 2" will begin. Similarly, each time the button is pressed, the program advances to the next treatment 3, 4, and 5 displayed as the corresponding states 1257d, 1257e, and 1257f. Pressing switch 1293 a sixth time returns the standalone LED pad to the off state 1297a.

Pulsed LED Thermotherapy – Similar to visible light and near-infrared in photobiomodulation therapy, thermotherapy is the application of far-infrared, typically comprising wavelengths from 1 pm to 100 pm. Thermotherapy includes spas, heating pads, and heating body wraps. According to Wikipedia, the therapeutic effects of heat include “increasing the extensibility of collagenous tissues; decreased joint stiffness; reduce pain; relieve muscle spasms; reduce inflammation, edema and aids in the post-acute healing phase; and increased blood flow. Increased blood flow to the affected area provides protein, nutrients, and oxygen for better healing." It also speeds up waste delivery metabolism and carbon dioxide. Heat therapy is also useful for improving muscle spasms, myalgia, fibromyalgia, contractures, bursitis,

While the therapeutic claims overlap with those offered by PBT, the physical mechanism of thermotherapy is considerably different. Unlike PBT, which imparts photons absorbed by molecules to stimulate chemical reactions that would not otherwise occur, i.e. photobiomodulation, in thermotherapy, heat absorbed by tissues and water accelerates rates of molecular vibration to accelerate reactions. ongoing chemical reactions. However, since according to Einstein's relation E = hc / A the energy of a photon is inversely proportional to its wavelength, the energy of 3 pm far infrared radiation is only 20 to 20% of that of red and of NIR PBT. This energy difference is significant, since the lowest energy is insufficient to break chemical bonds or transform the molecular structure. As such, thermotherapy is generally considered symptomatic relief without the associated accelerated healing manifestation in PBT. Penetration depths for far-infrared sources less than 3 pm (i.e., type B IR) exhibit greater penetration depths than longer wavelengths, and are therefore preferred over long-wavelength sources.

The aforementioned PBT system can be adapted for thermotherapy by replacing visible light and NIR LEDs with LEDs in the far IR spectrum. LEDs are generally limited to wavelengths of 12 pm or less as described in "Far Infrared Radiation (FIR): Its Biological Effects and Medical Applications",

^{Photonics Lasers Med} ., Vol. 1, no. 4, November 2012, pp. 255-266: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3699878/ by F. Vatansever and MR Hamblin. By tuning the crystal structure of compound III-V superlattice semiconductors for smaller bandwidths, LEDs operating in a far-IR spectrum have been achieved at wavelengths up to 8.6 pm (see "Emitting diode of InAs/GaSb superlattice light with maximum emission at a wavelength of 8.6 pm", IEEE J. Quant. Elect., vol. 47, no. 1, Jan 2011, pp. 5-54). Therefore, the PBT system used to drive the NIR LEDs described in this paper can be easily adapted to suit FIR LEDs by simply swapping the NIR LEDs for their longer wavelength counterparts.The diving circuit can be used identically using pulsed or sinusoidal waveforms Due to the long wavelengths, excitation frequencies below 100 Hz are more suitable to ensure uniform emission of far-infrared radiation Even at lower frequencies, for example, below 10 Hz, the FIR LEDs in a pad can be scanned row by row to produce a massage like an undulating wave through each pad, successively stimulating vasodilation in a systematic pattern through the tissue treaty. Optionally, the near-infrared LEDs for PBT and the far-infrared LED for thermotherapy can be combined into a smart pad and can be activated simultaneously or alternately in time.

^{M agne tor p y} - Magnetotherapy (MT) is an alternative medicine therapy in which injured tissue is subjected to magnetic fields. The influence of fixed magnetic fields on tissue is doubtful and is generally considered pseudo-medicine, pseudo-medicine, fringe medicine and even quackery, US FDA some studies have concluded permanent magnet magnetotherapy medical claims are fully supported by the results of science and clinical studies and prohibits the marketing of any magnet therapy product using medical claims (https://en.wikipedia.org/wiki/Magnet therapy). Contradictory claims suggest that pulsed magnetic fields exhibit a therapeutic effect because living tissue contains a large number of free ions and even electrically balanced molecules (such as water), which act as dipoles due to the direction of their charges. When subjected to an oscillating magnetic field, molecules are repelled and attracted according to their electrical charge in a manner similar to images made by magneto-resonant imaging (MRI), except that excitation occurs at lower frequencies. This type of magnetic therapy is commonly known as pulsed magnetotherapy or PMT.

The reported effects of PMT are largely analgesic, including muscle relaxation, improvement of local blood circulation, and vasodilation; anti-inflammatory effects; pain relief through local release of in dorphins; and beneficial effects on cellular membrane action potentials. The mechanism of action is believed to be primarily electrochemical rather than thermal, essentially acting catalytically by accelerating ongoing chemical reaction rates. Reported PMT pulse frequencies vary across the entire audio and infrasound spectrum from 20 kHz seeded down to less than 1 Hz. From the published literature, it is impossible to determine the accuracy of these reported claims or to determine the efficacy of PMT treatment. pulsed magnetotherapy. In addition, PMT carries certain risks. In particular, PMT is contraindicated in the case of tumors and has a safety risk of affecting pacemaker function.

In accordance with this invention, a pulsed magnetotherapy system can be realized by reusing the described PBT system by replacing the optical components with electromagnets and adapting the activation circuitry contained in the smart pad or wand. Optionally, the LEDs for PBT can be activated in combination with magnetic emitters, either simultaneously or alternately in time. In the case of driving an electromagnet array, the electromagnet array must be mounted on a plate of three-dimensionally flexible printed circuit board (or 3D PCB) similar to that used here for LED arrays and described in USPTO application number 14/919,594 entitled "Flexible 3D Printed Circuit Board with Redundant Interconnects", incorporated herein by reference The rigid-flex PCB is necessary to adjust the orientation of numerous electromagnets at a 90° angle (i.e., a right angle) to the patient's tissue being treated without mechanically damaging the solder joints between the flexible PCB and the Rigid Electromagnets The rigid and flexible PCB provides a perfect solution for achieving reliable 3D flexibility.

FIGURE. 82 illustrates a rigid-flex PCB with bare copper interconnects. As shown, the flexible PCB comprises an insulating layer 1303 sandwiched by metallic layers 1301 and 1302 typically comprising patterned copper. In some parts of the cross section shown and in other parts (not shown in this specific cross section), this flexible PCB is sandwiched in the middle of a rigid PCB comprising insulating layers 1304 and 1305 and laminated with metal stamped layers 1311 and 1312 In general, the flexible PCB metal layers 1301 and 1302 are thinner than the rigid PCB metal layers 1311 and 1312. The cross section is for illustrative purposes. The exact pattern of each layer in a cross section depends on the location and the circuit being implemented. As shown, metal through 1307 is used to connect metal layers 1301 through 1311 and through 1308 is used to connect metal layers 1302 through 1312. A fully buried through 1306 is used to connect the layers flexible metal 1301 and 1302.

Protective layers comprising a coating of polyimide, silicone or other scratch protection material are used to seal the rigid and flexible parts of the PCB. As shown, the 1304 insulator protects the 1301 metal layer and the 1305 insulator protects the 1302 metal layer completely sealing the flexible PCB from moisture and the risk of mechanically induced scratches. On the rigid part of the PCB, the patterned insulating layer 1313 shields a part of the metal layer 1311 and the non-patterned insulating layer 1314 completely shields the metal layer 1312. Some parts of the metal layers 1311 remain unprotected for the purpose of soldering. components on the rigid PCB.

As shown, the electrical interconnection of the various metal layers within a given rigid PCB, between rigid PCBs, and within flexible PCBs can be accomplished without the need for wires, connectors, or solder joints, using conductive vias 1306, 1307, and 1308 . These conductive pathways comprise conductive columns of metal or other low resistance materials formed perpendicular to the various metal layers and can penetrate two or more metal layers to facilitate multilevel connectivity and non-planar electrical topologies, that is, circuits where conductors must cross each other without turning electrically. shorted.

In PMT pads, the function of the rigid part of the rigid-flex PCB described can be used in various ways. In one case, discrete electromagnetic, permanent magnet, and permanent magnet/electromagnet stacks can be mounted on the rigid part of the rigid-flex PCB. Alternatively, the PCB interconnects can be used to form a toroid which when combined with through-hole magnetic material forms a planar magnetic structure. An exemplary arrangement of a planar magnetic toroid is illustrated in the explosion diagram in FIGURE. 83 where metal conductive layers 1311, 1301, 1302, and 1312 form a circular torus surrounding a magnetic core 1316. Each circular conductor in a given layer is rotated relative to the metal layer below it so that the conductive pathways metal 1307, 1306, and 1308 are capable of interconnecting the layers in a manner in which current flows counterclockwise in each layer located in each plane of the PCB, for example, in the plane that crosses the rigid PCB 1320. This structure It is further detailed in the FIGURE. 84 in which the rigid-flex PCB forms the layers of the toroid surrounding magnetic core 1316. To prevent short circuits between the conductive layers and the iron magnetic core, the magnetic core 1316 can be insulated from conductive layers 1311, 1301, 1302 , and 1302 by insulator 1315. The resulting top view is shown in FIGURE. 85 in planar cross section crossing rigid PCB 1320 and interconnect flexible PCB 1321. As illustrated, circular-shaped conductor 1302 encircles magnetic core 1316 while connecting to an overlying conductive layer via via 1306 and it is also connected to an underlying conductive layer via a via 1308.

An example circuit used to drive the PMT is illustrated in FIGURE. 86 comprising the PMT 1340 controller; 1341 electromagnet driver; 1363 electromagnet power supply; and electromagnet matrix 1350; together with the 1360 battery charger, the 1361 Li-Ion battery and a USB connector. Similar to a smart LED pad or laser wand circuit, the PMT 1340 controller includes the PMT pC 1181, clock 1183, non-volatile memory 1134, volatile memory 1135, communication interface 1182, and Bluetooth or WiFi radio link 1190. The output of PMT digital pulse pCs 1181 are activated by logic AND gates 128a, 1228b and, optionally, others (not shown) to facilitate overheat protection 1131a. The AND gate outputs are buffered by dual inverter chains 1346 and 1347 to drive the digital input of programmable current sinks 1342 and 1343, respectively. Controlled current sinks 1342 and 1343 control the magnitude and waveform of electromagnetic currents I ^em1 and I ^em2 flowing through electromagnets 1352 and 1353 in response to its digital inputs and also controlled by the analog reference current derived from the outputs of the 1345 D/A converter.

Freewheeling diodes 1354 and 1355 are included to prevent high voltage spikes whenever the current sinks are turned off rapidly by recirculating the inductor current until the stored energy of the electromagnet is consumed E ^l = 0.5LI 2 or until the sink of current conducts the current again. Capacitors 1356 and 1357 are used to filter out switching noise, or optionally to intentionally tank the coil inductance and oscillate at a resonant frequency of fLC = 1/(2n SQRT (LC)). The power to drive the V ^em electromagnets is derived from switching the power supply circuit, either a boost converter to increase the voltage or a Buck converter to reduce it. Alternatively, since current sinks 1343 and 1343 control inductor current anyway, the voltage regulator can be removed.

Although the operation of a switching regulator is well known in the art, an exemplary boost converter is included here as a power source for electromagnet 1363 for illustrative purposes. In operation, the PWM controller 1365 turns on the power MOSFET 1366 by allowing the current in the boost inductor 1369 to rise for a fixed fraction of a switching period after which the power MOSFET 1366 turns off. The interruption of conduction in the MOSFET causes the drain voltage of the power MOSFET 1366 to rise instantaneously, forward-biasing Schottky diode 1367 and charging capacitor 1368 to a voltage V ^em . A capacitor voltage feedback signal is then "feed back" to the 1365 PWM controller allowing the controller to determine if the output voltage is below or above its target voltage.

If the voltage is below the target, the pulse width over time is stretched to be a larger percentage D = on / (t on off) = (t on / T ^pwm ) of the next T PWM clock period, i.e. D increases allowing the average current in the 1369 inductor to increase and driving the output voltage V ^em higher. If, on the other hand, the output voltage is too high, the duty factor D, i.e. the turn-on time of the 1366 MOSFET will be reduced, allowing the current in the 1369 inductor to gradually decrease over several switching cycles. and therefore allow the output voltage to drop. By continually adjusting its duty factor D and pulse width (the turn-on time of the 1366 MOSFET), the output voltage is regulated to a constant value by virtue of voltage feedback. Therefore, the regulation process of a switching regulator operating at switching frequency and period T ^pwm is called PWM, which stands for pulse width modulation. The function of the output capacitor 1368 is to filter the output voltage while the input capacitor 1364 is It is used to prevent noise back injection into the power supply and to stabilize the power network. As shown, the output voltage of the switching converter and regulator is higher than its input, i.e. V ^em > Vbat, so the converter is called a boost converter. However, if the desired electromagnet driver voltage is less than the battery voltage VEM < Vbat , then a step-down or buck converter is required. Topologically, making a buck converter requires only a minor modification to the boost converter circuit by rearranging the same components by turning the three components connected to the common node to the right, i.e., replacing the 1367 Schottky diode with the 1369 inductor, replacing the 1366 MOSFET power with 1367 Schottky, and replacing the 1369 inductor with the 1366 power MOSFET.

Alternatively, instead of employing planar Magnetics to make the electromagnet, a pre-assembled or discrete electromagnet module can be employed. As the picture shows. 87 , surface mount discrete electromagnet 1351 including magnetic core 1376 and coil wire wound 1375 is attached as a surface mount component to the rigid part of a rigid-flex PCB by soldering metal feet1 1359A and 1359b to two distinct segments of conductive layer and electrically insulated 1311a and 1311b of the same conductive layer of copper. As illustrated, insulated conductor segments 1311a then connect to lower conductor layer 1312 via patterned pathways 1309a, 1306a, and 1310a. In this way, a separate discrete electromagnet can be placed on top of each rigid PCB to form an array as shown in the cross section of FIGURE. 88 A, specifically where the discrete electromagnet 1351a is mounted on a rigid PCB 1348a, which is connected to a rigid PCB 1348b through the flexible PCB portion 1349a; the 1351b discrete electromagnet is mounted on a 1348b rigid PCB, which is connected to a 1348c rigid PCB through the 1349b flexible PCB part; and where the discrete electromagnet 1351c is mounted on a rigid PCB 1348c, which is connected to other rigid PCBs (not shown) through the flexible PCB portion 1349c.

As such a design, each magnet 1351a, 1351b, 1351c, etc. The matrix is an electromagnet and can be electronically controlled to vary its magnetic field in accordance with the above PMT circuitry in response to the PMT playback generated from the PMT controller 1340. The waveforms can produce continuous, pulsed, or sinusoidal variations in the magnetic field of all the electromagnets in the array, or alternatively, they can involve activating the electromagnets individually and in some sequence to form a special pattern or magnetic wave across of the PMT pad, for example, generate a wavy magnet. field wave row by row across the pad or across a series of pads. In other cases, some Electromagnets may be biased to produce a constant magnetic field, while others are modulated to produce a time-varying magnetic field.

In an alternative embodiment, some electromagnets can be replaced by electromagnets to combine a mixture of constant and time-varying magnetic fields. For example, in FIG. 88B, previously electromagnet 13511b (shown above in FIG. 88A) is replaced by a permanent magnet 1370a attached to rigid PCB 1348b while electromagnets 1351a and 1351c remain unchanged. In FIGURE. 88C, rigid PCB 1348b drives a stack of an electromagnet 1351d and an underlying permanent magnet 1370b or alternatively in FIGURE. 88D, rigid PCB 1348b drives a stack of an electromagnet 1351e and a superimposed permanent magnet 1370c. In such cases, the performance of the electromagnet improves (or alternatively reduces the magnetic field produced by the stacked permanent magnet).

The PMT apparatus can also be adapted for use as a portable magnet therapy device or 1450 wand as shown in FIGURE. 89 consisting of a 1458 Barrel Handle with 1460 UX Display, 1461b push buttons to control operation and program selection, 1461a On/Off Button, 1643 Battery and 1462 USB Connector. The 1458 Barrel Handle connects to the Magnetic Head Unit 1453 via moving gimbal 1452. Magnetic head unit 1453 includes an electromagnet 1455 comprising a ferrite core 1457 and a coil 1556 mounted on PCB 1454 together with control circuitry. If operated as part of a distributed system, the communication link from the 1450 Portable Magnetic Therapy Wand to a PBT controller can be via USB, WiFi, or possibly Bluetooth. As a stand-alone device, the 1462 USB connector is used to program the wand during manufacturing by connecting it to a PBT controller.

^{Periodontal LEDPBT Mouthpiece} – Although PBT can be performed through the cheeks to treat gum disease, another option is to inject light directly into the patient's mouth using lasers or LEDs in the near-infrared spectrum and blue. This device is small and should fit comfortably in the mouth. As a stand-alone therapy device, the device must use a lightweight software client capable of running only a few pre-programmed algorithms. Alternatively, the device may employ data transmission from a user control module using a low power 802.11ah Wi-Fi, Bluetooth or wired connection. The User Control Module communicates with the PBT Controller and works the same as a Smart LED Pad Controller, except that its output does not activate the LEDs within a Pad, but is instead transmitted to the LED Nozzle as a passive electrical signal. so that no processing is processed. PE rformed inside the nozzle.

An example of such a periodontal PBT appliance is shown in the three-dimensional perspective drawing of FIGURE. 90 comprising a molded mouthpiece 1500 including a horseshoe-shaped part covering the teeth and gums 1503, two LEDs of different wavelengths 1504 and 1505 covering the horseshoe-shaped part (where the locations 1506 identify the position of the LEDs not visible in the 3D perspective drawing), electric cable 1501 and control unit 1502 with connector for power supply or optionally for bus communication. The corresponding cross section reveals a U-shaped cross section surrounding the tine 1510 comprising a rigid and flex PCB assembly with 1513 flex PCB, 1515 rigid PCB base, and 1513 LED. Instead of attempting to clean the teeth, the nozzle it is designed to position LEDs 1513 to be located near the gums 1512 adjacent to tooth 1511. The LEDs may comprise red, infrared, blue, or violet LEDs to combat inflammation and periodontal disease. The U-shaped assembly is contained within a thin silicone grommet molded around the rigid and flexible PCB.

The construction of the mouthpiece with a U-shaped cross section designed to cover and treat a single jaw (either the upper or the lower jaw but not both) is shown in FIGURE. 91 comprising a rigid PCB part 1513 and wings 1514 flexible PCB. As shown immediately after SMT fabrication, the 1513a LEDs are mounted on 1514 flexible wings and, optionally, the 1513z LED is mounted on 1515 rigid PCB. During PCB Surface Mount Technology (SMT) assembly, Rigid-flex PCBs must accommodate high-volume automated assembly that requires component pick-and-place and smooth solder temperature profiles during reflow. It is important that the printed circuit board stays flat during the mounting of the SMT. Although the rigid and flex parts of the PCB are secured in the same plane during pick and place, the rigid-flex PCB does not need to be linear, but can be placed in a rubber-shaped horseshoe pattern, so that there is no unnecessary flexing of the flexible PCB or added stress that can later cause breakage. After surface mounting, the flex wings 1514 are bent perpendicular to the rigid base 1515 of the U-shaped PCB and then molded into a clear silicone grommet 1516 that covers the rigid-flex PCB.

The same process can be adapted to make an H-shaped mouthpiece useful for simultaneously using PBT tre in the upper and lower jaws. The method shown in FIG. 92A uses the same manufacturing process as described for the aforementioned U-shaped nozzle, except that after PCB assembly, two separate pieces are electrically and physically joined together to produce the H-shaped nozzle. As shown, two PCBs, one comprising Rigid PCB 1515a, Flexible PCB 1514a, LED 1513a and optional LEDs 1513z, and a second comprising rigid PCB 1515b, flexible PCB 1514b, LEDs 1513b and optional LEDs 1513y are linked together. In the bonding process, rigid PCBs 1515a and 1515b are soldered together to electrically and mechanically form a multilayer PCB 1517 as shown in FIGURE. 92B. As such, the mouthpiece can treat the upper and lower gums simultaneously.

The junction of the rigid PCBs 1515a and 1515b is shown in FIGURE. 93 illustrating conductive surfaces 1518b and 1518d on top of rigid PCB 1515b are soldered to corresponding conductive surfaces 1518a and 1518c below rigid PCB 1515a to establish electrical connectivity between the upper and lower PCBs and to provide mechanical support and rigidity to the nozzle. Optionally, the through hole through s 1519a and 1519b filled with silver solder paste can be fused to form a continuous through hole extending through the upper rigid PCB 1515a and lower rigid PCB 1515b.

The circuit for the PBT periodontal mouthpiece is shown in FIGURE. 94. Since high voltages are not allowed in the patient's mouth, the input voltage V ⁱⁿ must be reduced is regulated to a lower voltage V ^led via the LDO 1520 low-dropout linear regulator. Filter capacitors 1521 and 1522 are included to stabilize the regulator and to filter input and output transients respectively. Under the control of the unit's microcontroller 1535 running programs stored in volatile and nonvolatile memory 1536a and 1526b according to the clock 1534 and time reference 1531, signals from the microcontroller are used to independently drive power sources. programmable current signals 1524a and 1524b with control signals 1537a and 1537b.

The signals can be used to digitally turn the LEDs on and off, or alternatively to program the carried current or synthesize a periodic waveform such as a sine wave. The current from the current source 1524a is reflected into the NPN bipolar transistor 1525a to control the current in the NPN bipolar transistor 1526a and therefore the current in the LEDs 1504a and 1504b and identically control the current in the LEDs 1504c and 150d, all in accordance with the program execution of the microcontroller 1535. Similarly, the current from the current source 1524b is reflected to the NPN bipolar transistor 1525b to control the current in the NPN bipolar transistor 1526b and thus thus, the current in LEDs 1505a and 1505b and similarly in LEDs 1505c and 1505d according to the program execution of the microcontroller 1535. In this way, the LED current can be controlled using a minimum number of components to save space. Therefore, the miniaturized controller circuitry can be housed in the enclosure 1502 shown in FIGURE. 90.

Ultrasound Therapy - T dispensing PBT system, as described is also applicable to driving piezoelectric transducers to ultrasound products in the frequency range of the range from 100 kHz to 4 MHz. The dominant therapeutic mechanism of action for ultrasound therapy It is vibratory, good for breaking up scar tissue and causing heating with good deep penetration. The driving algorithms can be similar to those used in sinusoidal driving of LEDs described herein, including digital (pulsed) and sinusoidal driving. The described distributed PBY is capable of performing ultrasonic therapy independently or in combination with PBT. Using the described system, ultrasound transducers can also be combined with LED arrays to break up scar tissue using ultrasound, and to remove it using PBT accelerated phagocytosis.

In FIGURE . 1 shows an implementation of a combined ultrasound PBT therapy system or USPBT pad . FIGURE. 95 comprising microcontroller 1557 executing programs stored in volatile and non-volatile memory 1558a and 1558b according to clock 1556 and time reference 1553, signals from the microcontroller are used to independently drive an H-bridge comprising MOSFETs low-side N-channel MOSFETs 1563a and 1563b and high-side P-channel MOSFETs 1564a and 1564b driving the piezoelectric ultrasound transducer 1562. The H-bridge is powered by a regulated supply voltage V ^pz generated by the DC/DC converter. 1550 with input capacitor 1551, output capacitor 1552, and optionally an inductor (not shown).

High side MOSFETs 1564a and 1564b are driven by level shift driver circuits 1566a and 1566b. Similarly, low-side MOSFETs 1563a and 1563b are driven by low-side snubbers 1565a and 1565b. In operation, the half-bridge formed by the low side N-channel MOSFET 1564a and the high-side P-channel 1563a is out of phase with the half-bridge formed by the low-side N-channel MOSFET 1564b and the high-side P-. channel 1563b. W high-side when P-channel 1564a MOSFET is on and conducting, then low-side 1563a N-channel is off and Vx = V ^pz . At the same time, the high-side P-channel MOSFET 1564b is off, then the low-side N-channel 1563b is on and conducting, so Vy = 0 during which current flows from V to Vy. In the next half cycle, the current flow reverses from Vy to Vx . In operation, the two half-bridges are phase-shifted by inverter 1567 in response to the output of qC pad 1557. The output of the half-bridge is bi-directional and has an absolute magnitude ±V ^pz . The output of qC pad 1557 is also used to drive an LED matrix 1561 via the LED driver 1560 described above.

In an alternate embodiment shown in FIG. 96, a programmable array of current sinks replaces the half-bridge in driving multiple piezoelectric transducers. As shown, pC pad 1557 sends a digital magnitude to D/A converter 1573 used to control the current drawn by current sinks 1576 and 1575 through the corresponding piezoelectric transducers 1562a and 1562b, respectively. The piezoelectric currents I ^pz1 and P ^z2 are digitally pulsed by converters 1571 and 1572 to control the frequency of the generated ultrasound.

An example of a USPBT pad is shown in FIGURE. 97 comprising a smart LED pad shown with a top view 1581, a bottom view 1584, and a side view including a single USB connector 1598. Cross section 1580 includes rigid PCB 1588; 1589 flex PCB, 1591 LED, 1590 sensor, and 1592a and 1592b piezo transducers. LED 1581 Polymeric Pad Cover includes openings 1595 and pocket 1596, and protective clear plastic 1587. LED 1580 Pad includes top c on 1581 flexible polymer with 1583 overhang, lower 1684 flexible polymer with 1585 overhang.

Optionally, the LEDs for PBT can be activated in combination with the ultrasonic piezoelectric emitters, either simultaneously or alternately in time. The combined application of ultrasonic and photobiomodulation therapy (herein referred to as USPBT) is useful for breaking up scar tissue using ultrasound and using PBT to accelerate the removal of dead cells.

Infrasound Therapy – Infrasound therapy is analogous to tissue massage, except that it occurs at very low frequencies below the audio spectrum, typically from 20 Hz down to 1 Hz or less. The actuator to create low frequencies must be relatively large, for example, 10 cm in diameter, and is therefore very suitable for inclusion in a rod similar to the one in the FIGURE. 89 except that the electromagnet is replaced by a speaker-like voice coil driver, except that the moving part attaches to a plunger or membrane that pushes the treated tissue at very low frequencies. Therefore, the described PBT system is directly compatible to support ultrasound peripherals. Infrasound provides a deep tissue massage and low frequencies useful for improving range of motion and muscle elasticity. Optionally, the LEDs for PBT can be activated in combination with the infrasonic moving coil actuator, either simultaneously or alternately in time.

PBT LED Buds for Nose/Ears - Although PBT can be performed transcranially, another option is to inject light directly into the nose or ears using lasers or LEDs in the near, infrared, and blue spectrum. Such as device is small. as autonomous therapy device, the device must use a lightweight software client capable of running only a few pre-programmed algorithms. Alternatively, the device may employ data transmission from a user control module using a low power 802.11ah Wi-Fi, Bluetooth or wired connection. The User Control Module is a communication toe, the PBT driver works identically to the driver of a smart LED pad, except that its output does not drive the LEDs within a pad, but is instead transmitted to the LED buttons. as a passive electrical signal so that no processing takes place. inside the buds. Therefore, the described PBT system is directly compatible to support PBT LED buttons for ear and nose treatments. Another benefit of intranasal and intraaural (ie, in the ear) PBT is its ability to kill pathogens and bacteria that infect sinus cavities.

^{LEDPBT Acupuncture Points} : Another small size LED source is a small LED or laser "dot", a coin-sized pad that is placed on the body over acupuncture points. This device is It is small and has no space for battery power. The device can use data transmission from a User Control Module using a low-power 802.11ah Wi-Fi, Bluetooth, or wired connection. The User Control Module is a communication toe, the PBT driver works the same as the driver of a smart LED pad, except that its output does not activate the LEDs within a pad, but rather is transmitted to the LED/laser dots as a passive electrical signal so that no processing is done within the spots.Therefore, the described PBT system is directly compatible to support LED PBT buttons for LED acupuncture points.

^{Blu e to o th Headphones} – Although not medically therapeutic, in relaxation applications, music can be streamed to the headphones via Bluetooth synchronized with the PBT treatment waveforms. Given the waveform synthesis capability of the disclosed PBT system, it is capable of supporting synchronized music and PBT treatments.

CLAIM (EN

1. A phototherapy system comprising:

a first string of light emitting diodes (LEDs), said first string of LEDs comprising a plurality of LEDs adapted to generate electromagnetic radiation (EMR) including radiation of a first wavelength A1;

a first channel controller coupled to said first string of LEDs for controlling an electrical current through said first string of LEDs;

a first microcontroller comprising a library of patterns, said library of patterns stores at least one algorithm, said at least one algorithm defines a processing sequence for controlling said first string of LEDs, said algorithm specifying a frequency f1 of EMR pulses emitted by said plurality of LEDs, a duty factor of said EMR pulses emitted by said plurality of LEDs, and a magnitude of said current through said first string of LEDs; and

a pad comprising said first string of LEDs, said first string of LEDs being positioned on said pad to allow said EMR to be irradiated towards a living organism when said pad is placed adjacent to said living organism, said pad comprising a second microcontroller for controlling autonomously said first string of LEDs.

Claims (12)

1. A phototherapy system comprising: a first string of light emitting diodes, LEDs, said first string of LEDs comprising a plurality of LEDs adapted to generate electromagnetic radiation, EMR, including radiation of a first wavelength A ¹ ; a first LED driver coupled to said first LED string for controlling an electrical current through said first LED string; a photobiotherapy controller, PBT, said a PBT controller comprising a main microcontroller, a communication interface and a digital clock, said PBT controller storing a pattern library, said pattern library comprising one or more algorithms, each algorithm defining a process sequence for controlling said first chain of LEDs, said algorithm specifying a frequency f ¹ of EMR pulses emitted by said plurality of LEDs, a duty factor of said EMR pulses emitted by said plurality of LEDs and a magnitude of said current through said first chain of LEDs; and a pad comprising said first string of LEDs, said first LED driver, a pad microcontroller and a pad memory, said first string of LEDs is positioned on said pad to allow said EMR to be irradiated into a living organism when said pad is placed adjacent to said living organism, said pad microcontroller being connected to the pad memory and to said first LED driver, said pad memory storing at least one of said algorithms for use by said pad microcontroller in control autonomously from said first chain of LEDs. The system according to claim 1, wherein the pad microcontroller is capable of controlling a current in each string of LEDs. The system according to claim 2, wherein the pad comprises an array of LEDs, said array of LEDs comprising a first string of LEDs and a second string of LEDs, the first string of LEDs and the second string of LEDs comprising a group of LEDs connected in series, and wherein the LEDs in a first LED string are capable of emitting light of a first wavelength and the LEDs in a second LED string are capable of emitting light of a second wavelength, said second wavelength is different from the first wavelength. The system according to claim 3, further comprising a second LED driver coupled to said second string of LEDs, and wherein each first and second LED driver comprises a MOSFET, a current sensor and a control element, each of said MOSFET, current sensor and control element is connected in series with the LEDs in said LED chain, said current sensor and control element are connected to a source of enable pulses for turning said MOSFET on and off and to a source reference current for controlling a level of said current in said MOSFET when said MOSFET is on. The system according to claim 4, wherein said source of a reference current for a first string of LEDs comprises a first reference MOSFET and a source of a reference current for a second string of LEDs comprises a second reference MOSFET, each of said first and second reference MOSFETs are connected in a current mirror arrangement with a third MOSFET connected to the threshold. The system according to claim 5, further comprising a tuning network connected to said third threshold-connected MOSFET. The system according to claim 5, further comprising a digital-analog, D/A converter, an output of said D/A converter that controls the magnitude of a current in said third MOSFET connected to the threshold. The system according to claim 1, further comprising a communication link between said PBT controller and said D/A converter, wherein the communication link comprises a USB cable or other wired communication means. The system according to claim 8, wherein the communication link comprises a conductor for supplying power to the LED pad. The system according to claim 1, wherein the PBT controller comprises a first clock and the LED pad comprises a second clock, said second clock being out of sync with said first clock. The system of claim 1, wherein the LED comprises a device identification register, said device identification register is stored in non-volatile memory and comprises data for use by the PBT controller to authenticate the identity of the pad of LEDs. The system according to claim 1, wherein the LED pad comprises a memory containing data for controlling the LED drivers in accordance with a selected PBT treatment.