Signal processing board for extending functionality of medical imaging systems and devices

Abstract

A computing system includes a plurality of signal processing boards configured to perform operations. An operation performed by a first signal processing board of the signal processing boards includes receiving a data signal from an image sensor of a medical device removably connected to the computing system, determining whether to route the data signal to a second signal processing board or a third signal processing board of the signal processing boards based on information associated with the image sensor, the information including a characteristic associated with the data signal indicating a native or non-native support by the computing system, and providing the data signal to the third signal processing board based on the determination of the non-native support. The third signal processing board is an expansion board removably connected to the computing system and configured to perform operations including manipulating the data signal and providing the manipulated data signal to the second signal processing board for processing.

Description

Cross-references to related applications

[0001] This application claims priority to U.S. Provisional Application No. 63 / 626,553, filed January 30, 2024, which is incorporated herein by reference in its entirety. Technical Field

[0002] Various embodiments of this disclosure generally relate to systems and methods for processing signals transmitted from medical devices, and more specifically to a controller having multiple processing boards and a related method for routing signals to appropriate boards for processing, the controller including removably connected expansion boards that provide functionality for processing signals not natively supported by the controller. Background Technology

[0003] For example, imaging-capable medical devices (such as endoscopes or other similar devices) may include one or more image sensors configured to capture raw images of a target region within a body cavity. Once the raw images are captured, the medical device can be configured to transmit the corresponding data signals to a controller to which the medical device is connected for processing. Different types or models of medical devices may contain different types of image sensors (e.g., image sensors manufactured by different imaging sensor manufacturers). Additionally, certain types of medical devices that include multiple image sensors may include different types of image sensors. Summary of the Invention

[0004] According to some aspects, the technology described herein relates to a computing system. An example computing system includes a plurality of signal processing boards configured to perform operations including: receiving, by a first signal processing board, data signals from an image sensor of a medical device removably connected to the computing system; determining, by the first signal processing board, whether to route the data signals to a second or third signal processing board among the plurality of signal processing boards based on information associated with the image sensor, the information including one or more features associated with the data signals indicating whether they are natively supported or not natively supported by the computing system; providing the data signals to the third signal processing board by the first signal processing board based on the determination that they are not natively supported, wherein the third signal processing board is an expansion board removably connected to the computing system; manipulating the data signals by the third signal processing board; and providing the manipulated data signals to the second signal processing board by the third signal processing board for processing.

[0005] In any of the example computing systems described herein, information associated with the image sensor includes whether the data signal has a first data format or a second data format. When the data signal has the first data format, the data signal is provided to the third signal processing board by the first signal processing board, and manipulating the data signal includes converting the data signal from the first data format to the second data format. In some examples, information associated with the image sensor includes the data signal type of the data signal, and one or more communication methods or protocols used by the image sensor to transmit the data signal.

[0006] In some aspects, the second signal processing board includes low-speed differential inputs and high-speed differential inputs, and manipulating the data signal includes routing the data signal to a specific input of either the low-speed or high-speed differential inputs of the second signal processing board. In other aspects, manipulating the data signal includes modifying or altering the data signal to generate the manipulated data signal. Modifying or altering the data signal to generate the manipulated data signal includes at least one of the following: converting the data signal from a first data format to a second data format; converting the data signal from a first signal type to a second signal type; adjusting the length of the data signal; or adjusting the strength of the data signal. In some examples, the operation further includes, by the first signal processing board, determining one or more functions to be implemented by the third signal processing board to manipulate the data signal.

[0007] In other respects, in response to the medical device being connected to the computing system, information associated with the image sensor is received from the memory of the medical device.

[0008] In a further aspect, the data signal is a first data signal, the transmitter is associated with the medical device, and the operation further includes: receiving a second data signal from the transmitter by the first signal processing board; determining, based on one or more characteristics associated with the second data signal, to transmit the second data signal to the third signal processing board; manipulating the second data signal by the third signal processing board; and providing the manipulated second data signal to the second signal processing board for processing by the third signal processing board. In some examples, the third signal processing board is configured to enable bidirectional data transmission between the transmitter and the computing system.

[0009] In some aspects, manipulating the data signal includes performing one or more of a plurality of manipulation functions, and the third signal processing board further includes a switching circuit system configured to facilitate a combination of the plurality of manipulation functions. In some examples, the third signal processing board further includes an authentication circuit system configured to, when the third signal processing board is connected to the computing system, facilitate the verification by the first signal processing board of the authenticity of the third signal processing board to be used in the computing system. In other examples, the third signal processing board further includes one or more illumination elements configured to indicate the connection status of the third signal processing board with the computing system.

[0010] In other respects, the data signal is a first data signal, the image sensor is a first image sensor, and the operation further includes: receiving a second data signal from a second image sensor, different from the first image sensor, by the first signal processing board; determining, by the first signal processing board, whether to route the second data signal to the second signal processing board or the third signal processing board based on information associated with the second image sensor, the information including one or more features associated with the second data signal indicating whether they are natively supported or not natively supported by the computing system; and, based on the determination that they are natively supported, providing the second data signal to the second signal processing board for processing by the first signal processing board.

[0011] According to other aspects, the technology described herein relates to a controller. An example controller includes an interface board, a motherboard, and an expansion board removably connected to the controller. The interface board is configured to: in response to a medical device connecting to the controller, receive information associated with an image sensor of the medical device, the information including one or more characteristics associated with data signals generated and transmitted by the image sensor; classify the data signals as non-motherboard supported based on the information; and route the incoming data signals received from the image sensor to the expansion board using the classification; and wherein the expansion board is configured to: manipulate the incoming data signals to generate manipulated data signals; and provide the manipulated data signals to the motherboard for processing.

[0012] In any example controller described herein, the information associated with the image sensor further includes information identifying the hardware of the image sensor, and one or more characteristics associated with the data signal include one or more of the following: the data format of the data signal, the signal type of the data signal, or one or more communication methods or protocols used to transmit the data signal. In some aspects, to manipulate the incoming data signal, the expansion board is configured to: route the incoming data signal to a specific input of the motherboard; convert the incoming data signal from a first data format to a second data format; convert the incoming data signal from a first signal type to a second signal type; adjust the length of the incoming data signal; or adjust the strength of the incoming data signal.

[0013] According to a further aspect, the technology described herein relates to a method performed by a controller. An example method includes: receiving information associated with an image sensor of a medical device removably connected to the controller by a first signal processing board of the controller, the information including one or more characteristics associated with data signals generated and transmitted by the image sensor; classifying the data signal by the first signal processing board as either natively supported or non-natively supported by the controller; and determining by the first signal processing board, based on the classification, whether to route the incoming data signal received from the image sensor to a second or third signal processing board of the controller; wherein, when the data signal is classified as natively supported by the controller, the first signal processing board provides the incoming data signal to the second signal processing board for processing; and wherein, when the data signal is classified as non-natively supported by the controller: the first signal processing board provides the incoming data signal to the third signal processing board, wherein the third signal processing board is an extension board removably connected to the controller; manipulating the incoming data signal by the third signal processing board; and providing the manipulated incoming data signal to the second signal processing board for processing by the third signal processing board.

[0014] In any of the example methods described herein, manipulating the incoming data signal includes one or more of the following: routing the incoming data signal to a specific input of a second signal processing board; converting the incoming data signal from a first data format to a second data format; converting the incoming data signal from a first signal type to a second signal type; adjusting the length of the incoming data signal; or adjusting the strength of the incoming data signal.

[0015] It should be understood that the foregoing general description and the following detailed description are exemplary and illustrative only, and do not limit the claimed and disclosed embodiments. As used herein, the terms “comprising,” “including,” “having,” or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article of manufacture, or apparatus that comprises a list of elements may include not only those elements but also other elements not expressly listed or inherent to such process, method, article of manufacture, or apparatus. The term “exemplary” is used in the sense of “example” rather than “ideal.” The term “distal” refers to a direction away from the operator / towards the treatment site, and the term “proximal” refers to a direction towards the operator. The term “about” or similar terms (e.g., “substantially”) include values ​​+ / - 10% of the stated value. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate various exemplary embodiments and, together with the explanatory sections, serve to explain the principles of the disclosed embodiments.

[0017] Figure 1 An example environment is described in which a medical imaging system, including an expansion board for signal processing, can be implemented according to one or more aspects.

[0018] Figure 2 Describes based on one or more aspects Figure 1 A block diagram of an example expansion board is depicted in the image.

[0019] Figure 3 An example method for routing data signals based on one or more aspects is described.

[0020] Figure 4 An example path for routing data signals is described based on one or more aspects.

[0021] Figure 5 An example of a computer is described based on one or more aspects. Detailed Implementation

[0022] As briefly mentioned above, imaging-capable medical devices (such as endoscopes or other similar devices) may include one or more image sensors configured to capture raw images of a target area within a body cavity during a medical procedure. Once the raw images are captured, the medical device can be configured to transmit the corresponding data signals to a controller to which the medical device is connected for processing. Different types or models of medical devices may contain different types of image sensors (e.g., image sensors manufactured by different imaging sensor manufacturers). Additionally, certain types of medical devices that include multiple image sensors may include different types of image sensors.

[0023] Image sensor manufacturers are increasingly developing unique, and in some cases proprietary, signaling schemes for transmitting data signals from their image sensors to receivers (such as components of a controller). The ongoing development of new signaling schemes introduces unpredictability when planning what type of electronic hardware or design to implement to enable the controller to support the processing of data signals from a variety of currently available and future (e.g., yet-to-be-developed) image sensors.

[0024] Additionally, to support multiple different image sensors from one or more medical devices simultaneously connected to the controller, while minimizing the number of conductors on the medical devices, complex analog-to-digital switching may be utilized. However, this type of complex switching may only be implemented with known technologies (e.g., known image sensors).

[0025] Therefore, conventional controllers are typically designed to include specific hardware and / or software configured to process data signals associated with one or more types of image sensors that (i) are currently available or known and (ii) are intended to be integrated into medical devices that can be connected to the controller for use during medical procedures. Without significant modifications or redesign, such conventional controllers may not be able to handle the processing of data signals received from future image sensors or other types of image sensors that were not previously considered or supported (e.g., which may use different types of data signals or data signaling schemes).

[0026] Therefore, aspects of this disclosure relate to a plug-in or expansion board that can be removably connected to a controller, and logic implemented by the controller to route data signals to the expansion board when appropriate. For example, the routing logic may be implemented by an interface board of the controller. When a medical device is connected to the controller, the interface board may receive information associated with the image sensor of the medical device. This information may include one or more characteristics associated with data signals generated and transmitted by the image sensor, such as data format, data signal type, communication method and / or protocol, and other information. The interface board may use this information to classify the data signals as either natively supported or not natively supported by the controller.

[0027] Native support classification indicates whether a data signal can be processed by the controller's native or main processor (e.g., the motherboard). Therefore, when a data signal is classified as natively supported, the interface board can proceed to route any incoming data signal from the image sensor to the motherboard. Alternatively, when a data signal is classified as non-natively supported, the interface board can proceed to route any incoming data signal from the image sensor to an expansion board. An expansion board can be configured or can be enabled to process incoming data signals (e.g., provide extended functionality to the controller). The expansion board can process and / or manipulate the incoming data signals to generate manipulated data signals, for example, those that can be processed by the main processing board, and provide the manipulated data signals to the motherboard. The expansion board can be modular, having various hardware (such as additional switching circuitry and / or signal processing circuitry) that can be added to facilitate the processing or manipulation of non-natively supported data signals.

[0028] The expansion board and routing logic enable the controller to support a wider range of data formats, data signal types, communication methods, and / or protocols, and thus support a variety of different image sensor types for medical devices (e.g., image sensor types beyond those initially intended for use with the controller). Furthermore, assuming the expansion board can be removably connected to the controller, it can be interchanged with other expansion boards or replaced by new ones to allow the controller to support different or future-developed image sensor types. In various aspects, the expansion board can be positioned on the controller in a location easily accessible to field service technicians to facilitate its installation and / or removal, as well as other service-related activities.

[0029] Furthermore, multiplexing can be used for both data signals classified as natively supported and data signals classified as non-natively supported, allowing multiple data signals to be transmitted to the controller simultaneously through a single communication channel.

[0030] Now refer to the attached diagram, Figure 1 An exemplary environment 100 is depicted according to one or more aspects. Components of environment 100 may include a medical device 102, a controller 110, a display device 120, an optional transmitter 122, an optional server-side system 130, and / or a network 140, one or more of these components being able to communicate with each other via the network. While for each of the medical device 102, controller 110, display device 120, optional transmitter 122, and optional server-side system 130, Figure 1 Only one is shown, but environment 100 may include multiple components for one or more of these components.

[0031] Medical device 102 may be removably connected to controller 110 and used to perform diagnostic and / or interventional medical procedures on a patient. Medical device 102 may be an endoscope, another type of endoscope such as a bronchoscope, ureteroscope, duodenoscope, gastroscope, endoscopic ultrasound (“EUS”), colonoscope, laparoscope, arthroscope, cystoscope, aspiration endoscope, sheath or catheter, or other similar medical devices with imaging capabilities.

[0032] Medical device 102 may include imaging system 104. Imaging system 104 may include at least one image sensor 106 and at least one light source 108. Image sensor 106 and / or light source 108 may be located at the distal end of medical device 102 (e.g., at the distal tip of medical device 102). Image sensor 106 may be a specific image sensor type. For example, image sensor 106 may include hardware associated with a manufacturer. Based on this hardware, image sensor 106 may be configured to generate data signals of a specific data signal type (e.g., analog and / or digital). Additionally, image sensor 106 may be configured to transmit the generated data signals using specific communication methods and / or communication protocols.

[0033] For illustrative purposes, image sensor 106 may be configured to capture raw images (e.g., in the form of image signals) during a medical procedure when the distal end of medical device 102 is inserted into a patient's body cavity and navigates through the body cavity to a target area. Image sensor 106 can then transmit the image signals to controller 110 for processing. Image sensor 106 may include one or more cameras, endoscopic viewing elements, or optical components, and other similar devices. As described in more detail below, in some examples, image sensor 106 may communicate using digital or analog communication methods (e.g., transmitting image signals). Example digital communication methods may use differential pairs to transmit low-voltage differential signaling. Although... Figure 1 The imaging system 104 of the medical device 102 is shown only as having one image sensor 106; however, in other examples, the imaging system 104 may include multiple image sensors 106, and specifically image sensors 106 of different image sensor types. Additionally or alternatively, although Figure 1 Only one medical device 102 connected to controller 110 is shown, but in other examples, multiple medical devices 102 with the same or different types of image sensors 106 may be connected to controller 110.

[0034] The light source 108 can be configured to illuminate an area of ​​the patient's body (e.g., a target area) during a medical procedure to facilitate imaging of the target area by the image sensor 106. The light source 108 may include one or more LEDs, incandescent light sources, fiber optics, and / or other illuminators.

[0035] Medical device 102 can be connected to controller 110 via a wired connection. For example, medical device 102 can be connected to the controller via an umbilical cable attached to a connector of medical device 102 and a connector of controller 110. In some examples, and as described above, controller 110 can be configured to support the connection and operation of at least two medical devices 102 simultaneously. Among other components, controller 110 may include one or more components configured to function as a video processor or signal processor (e.g., a receiver) for data signals transmitted by medical device 102. For example, controller 110 may include an interposer board 112, an interface board 114, a main board 116, and / or an expansion board 118.

[0036] Each of processing boards 114, 116, and 118 can be relied upon for different functions related to the routing and / or processing of data signals transmitted by medical device 102. The data signals may correspond to, for example, raw images or image streams (e.g., video) of a target area captured by image sensor 106 of medical device 102 in association with a medical procedure. The data signals may initially be received by intermediate board 112 and then routed from intermediate board 112 to interface board 114. In some respects, intermediate board 112 may be bypassed (or omitted in practice, though shown), and the data signals may initially be received by interface board 114.

[0037] Based on the data signal classification operation performed by the interface board 114, the interface board 114 can be configured to route data signals to one of the main board 116 or the expansion board 118 for further processing via branching or switching components of the interface board 114. The main board 116 can be configured to further process data signals received directly from the interface board 114 or processed or manipulated data signals received from the expansion board 118 to generate image data for output to the operator (e.g., via the display device 120).

[0038] Based on the interface board 114 determining that the data signal received from the medical device 102 is natively supported, the transmission of the data signal from the interface board 114 to the motherboard 116 can occur via a first routing path (also referred to as a "native branch"). The native support classification can instruct the motherboard 116 of the controller 110 to be configured or capable of processing the data signal received from the medical device 102 without any hardware modifications. However, in some instances, software or field-programmable gate array (FPGA) updates may be required. In some examples, the hardware of the motherboard 116 can be configured to support data signals from any known image sensor type incorporated within the medical device 102, which is intended to be connected to the controller 110 for use during medical procedures.

[0039] Based on the determination by interface board 114 that the data signal received from medical device 102 is classified as non-natively supported, the transmission of the data signal from interface board 114 to expansion board 118 may occur via a second routing path (also referred to as a "future branch"). A non-natively supported classification may indicate that the hardware of mainboard 116 of controller 110 is not configured or is unable to process the data signal received from medical device 102. However, the hardware of expansion board 118 may be configured or may be able to process such data signals (e.g., providing extended functionality to controller 110). In other words, expansion board 118 may provide the necessary hardware modifications to controller 110 so that controller 110 can process data signals classified as non-natively supported by, for example, routing the data signal to expansion board 118 for manipulation and / or processing and then sending it to mainboard 116. In some examples, updates to the hardware of expansion board 118 (e.g., updates to the processing circuitry or FPGA code) may be necessary to implement signal processing. Additionally or alternatively, software modifications and / or updates may be made to mainboard 116 to support data signal processing performed by the hardware of expansion board 118. In other examples, when expansion board 118 includes optional processor and memory (see...) Figure 2 When the expansion board 118 is configured to store software for execution, the software can be updated and / or modified as needed to support data signal processing.

[0040] Therefore, the expansion board 118 and the routing logic implemented by the interface board 114 enable the controller 110 to support a wider range of data signal types, communication methods, and / or protocols, and thus support a variety of different image sensor types for medical devices (e.g., image sensor types beyond those originally intended to be used with the controller 110). Additionally, the expansion board 118 can be removably connected to one or more components within the controller 110. Therefore, the expansion board 118 can be interchangeable or replaced by new expansion boards 118 to enable the controller 110 to support future technological advancements. Further descriptions of the interface board 114, expansion board 118, and mainboard 116 are provided below.

[0041] Furthermore, multiplexing can be used for both data signals classified as natively supported and data signals classified as non-natively supported, allowing multiple data signals (digital or analog) generated by medical device 102 to be simultaneously transmitted to controller 110 through a single communication channel. For example, multiple data signals can be combined or merged into a composite signal for transmission through a single communication channel.

[0042] Interface board 114 may be a first signal processing board of controller 110. In some examples, interface board 114 may be a printed circuit board assembly (PCBA). Interface board 114 may include at least one memory and at least one processor. In some examples, the at least one processor may be an FPGA configured to execute various instructions stored in at least one memory, including instructions associated with routing logic of branching or switching components of interface board 114. Using this logic, interface board 114 may be configured to classify data signals received from medical device 102 as natively supported or non-natively supported. Classification may be based at least in part on information received from medical device 102 when medical device 102 is connected to controller 110. For example, at least one processor of interface board 114 may be configured to receive information (e.g., stored in the memory of medical device 102) that includes at least information associated with image sensor 106 of medical device 102.

[0043] Information associated with image sensor 106 may include information identifying the hardware of image sensor 106, such as manufacturer, model, or other similar identifiers used to indicate the type of image sensor. In some examples, the identifier may further indicate an associated chip (e.g., a bridging chip) manufactured by the manufacturer for use in conjunction with the image sensor to facilitate decoding (e.g., format conversion) of signals generated by image sensor 106, as described in more detail below. Information associated with image sensor 106 may also include information identifying characteristics of data signals received from image sensor 106, such as the type and format of the generated data signals, and the communication method and / or communication protocol used to transmit the generated data signals. Example data signal types may include analog signals and / or digital signals. Example data formats may include proprietary or standard formats for image and / or video data. Example communication protocols may include analog communication protocols (e.g., for transmitting analog signals) or digital communication protocols (e.g., for transmitting digital signals). An example digital communication protocol may include a low-voltage differential signaling (LVDS) communication protocol using differential pairs. Differential pairs can be used in different configurations to facilitate connectivity between controller 110 and different types of medical devices 102, including medical devices 102 with single or multiple image sensors 106. LVDS communication protocols may include, for example, Positive Emitter Coupled Logic (PECL) or Scalable Low Voltage Signaling (SLVS). Other example communication protocols may include the Mobile Industrial Processor Interface (MIPI) communication protocol and other known or future communication protocols.

[0044] If, based on the received information, the interface board 114 classifies the data signal received from the image sensor 106 of the medical device 102 as natively supported by the controller 110, then the interface board 114 can route the data signal to the motherboard 116 for further processing. If, based on the received information, the interface board 114 classifies the data signal received from the medical device 102 as not natively supported by the controller 110, then the interface board 114 can route the data signal to the expansion board 118 for further processing and manipulation.

[0045] Additionally, in some examples, interface board 114 can be configured to determine one or more functions to be performed by expansion board 118 (e.g., the type of manipulation to be performed by expansion board 118).

[0046] Mainboard 116 may be a second signal processing board of controller 110. In some examples, mainboard 116 may be a PCBA. Mainboard 116 may include at least one memory and at least one processor. In some examples, the at least one processor may be an FPGA configured to execute various instructions stored in at least one memory, including instructions associated with image processing. In some aspects, the at least one processor of mainboard 116 may include one or more inputs, such as low-speed differential inputs and high-speed differential inputs. Low-speed differential inputs may support processing of data signals that do not require high data throughput, high data transfer rates, and / or high data bandwidth. High-speed differential inputs may support processing of data signals that require high data throughput, high data transfer rates, and / or high data bandwidth. For example, low-speed differential inputs may be limited to 1.2 gigabits per second (Gbps) per data channel. Therefore, high-speed differential inputs may support any data signal processing that requires more than 1.2 Gbps per data channel. The upper limit of high-speed differential inputs may be variable (e.g., depending on the transceiver ports of the FPGA of mainboard 116). As a non-restricted example, the upper limit can be greater than 6 Gbps.

[0047] When the data signals generated and transmitted by the image sensor 106 of the medical device 102 are classified as natively supported by the controller 110, the motherboard 116 can be configured to directly receive any incoming data signals transmitted by the image sensor 106 from the interface board 114. Alternatively, when the data signals generated and transmitted by the image sensor 106 of the medical device 102 are classified as not natively supported by the controller 110, the motherboard 116 can be configured to receive manipulated data signals from the expansion board 118, as discussed in detail below. The motherboard 116 can be configured to further process the data signals and / or manipulated data signals to generate image or video data, thereby providing it for display to the operator of the medical device 102 (e.g., via display device 120).

[0048] Expansion board 118 can be a third signal processing board for controller 110. In some examples, expansion board 118 can be a PCBA. See reference... Figure 2In more detail, expansion board 118 may include at least a processing circuitry system (including an FPGA) configured to process or manipulate non-natively supported data signals. In some examples, expansion board 118 may include one or more components or sub-components (e.g., third-party components) manufactured by an entity different from the manufacturer of expansion board 118 and / or controller 110. One example third-party component may include a chip (e.g., a bridging chip) manufactured by the manufacturer of image sensor 106, which is used in conjunction with image sensor 106 to facilitate decoding (e.g., format conversion) of signals generated by image sensor 106, as described in detail below.

[0049] When the data signal generated and transmitted by the image sensor 106 of the medical device 102 is classified as not natively supported by the controller 110, the expansion board 118 can be configured to receive any incoming data signal transmitted by the image sensor 106 from the interface board 114. For example, the expansion board 118 can receive data signals via a second routing path or a future branch.

[0050] Expansion board 118 can be removably connected to controller 110. For example, expansion board 118 can be interchangeable or replaceable. Alternatively, expansion board 118 can be a modular processing board capable of supporting various hardware updates or additions that enable controller 110 to process different types of data signals that can be categorized as not natively supported. For example, expansion board 118 can be configured to manipulate data signals received from interface board 114 and route the manipulated data signals to mainboard 116 for processing, as described above.

[0051] In some examples, the manipulated data signal can be routed to either the low-speed differential input or the high-speed differential input of the motherboard 116. In other examples, the expansion board 118 can route the manipulated data signal to both the low-speed and high-speed differential inputs of the motherboard 116. In some aspects, the manipulation of the data signal performed by the expansion board 118 can simply be routing the data signal received from the medical device 102 to the low-speed differential input and / or the high-speed differential input. In other aspects, the manipulation can further include modification or alteration of the original data signal received from the medical device 102. (Refer to the following...) Figure 2 A more detailed description of expansion board 118 and its capabilities is provided.

[0052] Based on the signal processing capabilities of each of the interface board 114, the motherboard 116, and the expansion board 118, these components are described herein as signal processing boards (e.g., a first signal processing board, a second signal processing board, and a third signal processing board, respectively). For example, each of the interface board 114, the motherboard 116, and the expansion board 118 can be configured to perform one or more functions on data signals. The term signal processing board is not intended to refer to any specific processing component of each of the interface board 114, the motherboard 116, and the expansion board 118.

[0053] Optional transmitter 122 may be a component of medical device 102 or another medical device associated with or used in conjunction with medical device 102 for sending and receiving data signals (e.g., sending to and receiving from controller 110). As an example, optional transmitter 122 may be a transmitter of an ultrasound device configured to send and / or receive ultrasound signaling in digital format. As another example, optional transmitter 122 may be a transmitter of a sensor device configured to send and / or receive thermal, pressure, or chemical information associated with a target area. As yet another example, the transmitter may be a transmitter of a device for fluorescence lifetime capture and / or real-time navigation technologies configured to send and / or receive a universal clock. Another example may include optional transmitter 122 being a transmitter of a therapeutic device configured to send and / or receive signals with therapeutic indications, including high-frequency signals (e.g., 300 kHz to 500 kHz) or signals designed to drive therapeutic applications (such as lasers or similar applications). These signals can be used to perform therapeutic functions, such as tissue ablation, protein denaturation, and cauterization.

[0054] In some examples, the optional transmitter 122 may be coupled to or integrated with the medical device 102. For example, the optional transmitter 122 may be located in one or more working channels at the distal end of the medical device 102. In other examples, for example, the optional transmitter 122 may be a separate device delivered to a target area (e.g., located inside the patient) via the medical device 102 or other means. In still other examples, the optional transmitter 122 may be a separate device located outside the patient.

[0055] Optional transmitter 122 may be configured to send data signals to controller 110 for processing. Additionally or alternatively, optional transmitter 122 may be configured to receive data signals from controller 110. For example, in addition to acting as a receiver of data signals, expansion board 118 of controller 110 may also have the capability to act as a transmitter. In some examples, controller 110 may be configured to receive and process data signals transmitted by optional transmitter 122. For example, data signals received from optional transmitter 122 may be routed to intermediate board 112, from intermediate board 112 to interface board 114, and from interface board 114 to expansion board 118 for further processing. As described above, in some examples, intermediate board 112 may be bypassed. Expansion board 118 may include the hardware (and optional software) required to manipulate data signals from optional transmitter 122 and transmit the manipulated data signals to motherboard 116 for output via display device 120. Additionally or alternatively, controller 110 may be configured to generate data signals and send data signals to optional transmitter 122. For example, the expansion board 118 of the controller 110 may include one or more capabilities or functions of a transmitter device, and the optional transmitter 122 may include one or more capabilities or functions of a receiver device. Therefore, the expansion board 118 can enable bidirectional data flow or transmission between the optional transmitter 122 and the controller 110.

[0056] Display device 120 can be configured to display data associated with one or more of medical device 102, controller 110, and / or optional transmitter 122. For example, the displayed data may include processed images and / or information. Displaying processed images and / or information can help the operator of medical device 102 visually navigate to and / or more clearly identify features of interest within a target area associated with a medical procedure. Display device 120 may include one or more combinations of monitors, computing device screens, touchscreen displays, etc. In some examples, display device 120 may be a separate device from controller 110, communicatively coupled to controller 110 via wired and / or wireless connections. In other examples, display device 120 may be a display or screen of controller 110 itself.

[0057] Optional server-side system 130 may include one or more remote image processing systems configured to perform at least a portion of image processing (e.g., to conserve local resources of controller 110, and specifically its motherboard 116, when network connectivity is available via network 140). Additionally or alternatively, optional server-side system 130 may include a data storage system for storing image data generated by controller 110. In some examples, at least one of the data storage systems may include a Picture Archiving and Communication System (PACS) that stores image data, as well as other types of imaging data from various imaging modalities (e.g., ultrasound, magnetic resonance imaging, nuclear medicine imaging, positron emission tomography, computed tomography, mammography, digital radiography, histopathology, etc.). Further, optional server-side system 130 may include an endoscopy report writer system configured to facilitate report generation based on image data.

[0058] One or more components of environment 100 can communicate with each other via a wired or wireless network (such as network 140). Network 140 can be an electronic network. Network 140 can include a wide area network (“WAN”), a local area network (“LAN”), a personal area network (“PAN”), a cellular network (e.g., 3G network, 4G network, 5G network, etc.), etc. In other examples, one or more components of environment 100 can communicate and / or connect to the network via a universal serial bus (USB) or other similar local low-latency connection or direct wireless protocol. Components of environment 100 can be connected via the network using one or more standard communication protocols, enabling components to send and receive communications with each other across the network.

[0059] Despite the various components in Environment 100 Figure 1 While depicted as separate components, it should be understood that in some embodiments, a component or part of a component in environment 100 may be integrated with or incorporated into one or more other components. For example, optional transmitter 122 may be integrated with medical device 102, and / or display device 120 may be integrated with controller 110. In some embodiments, the operation or aspects of one or more of the components discussed above may be distributed across one or more other components. Any suitable arrangement and / or integration of various systems and devices in environment 100 may be used.

[0060] It should be understood that the technology based on this disclosure is suitable for any medical imaging system, including controllers capable of supporting and operating different types of medical devices, including various types of image sensors. It should also be understood that the examples above are merely illustrative. The techniques and methods described in this disclosure can be adapted to any suitable activity.

[0061] Figure 2 A block diagram of an expansion board 118 is depicted according to one or more aspects. The expansion board 118 may include one or more lighting elements 250, an optional memory 254, an optional processor 255, and multiple circuit systems 256. The lighting elements 250 may include one or more light-emitting diodes (LEDs) 252. The circuit systems 256 may include a signal processing circuit system 258, an authentication circuit system 260, and / or a switching circuit system 262.

[0062] Expansion board 118 may be removably connected to or removably mounted in controller 110. In some examples, expansion board 118 may be removably mounted at interface board 114. For example, expansion board 118 may be physically and / or electrically coupled to interface board 114. In other examples, expansion board 118 may be removably mounted at intermediary board 112.

[0063] To support different types of image sensors 106, medical devices 102, or transmitters 122 beyond those initially intended for use with controller 110, and / or to support future technological developments yet to be known, expansion board 118 may be replaceable with different or new expansion boards 118, including hardware and / or software configured to or capable of supporting associated data signal processing, and / or interchangeable with such expansion board. Additionally, expansion board 118 may support hardware and / or software updates. In some examples, hardware and / or software updates can be performed in the field (e.g., at the location of controller 110). To facilitate field service, expansion board 118 may be positioned within controller 110 where it can be easily accessed by field service technicians for installation and / or removal. For example, expansion board 118 may be removably connected to controller 110 in the field by a field service technician as a hardware upgrade (e.g., by replacing the currently connected expansion board 118 with a new expansion board 118). Alternatively, controller 110 can be replaced by a new controller 110 that has been removably connected or installed with a new expansion board 118.

[0064] During installation, LED 252 can indicate a successful physical and electrical connection between expansion board 118 and controller 110. For example, LED 252 can emit one or more light pulses as a visual cue to confirm that expansion board 118 has been correctly installed. Additionally, in some examples, expansion board 118 can be designed such that the connection between expansion board 118 and controller 110 is not misaligned or insufficient. Furthermore, expansion board 118 can be designed to allow installation to be performed using one hand, thereby facilitating field service.

[0065] Optional memory 254 may be or include electrically erasable programmable read-only memory (EEPROM). Optional memory 254 may be configured to store parameters and other instructions for data signal processing. The stored parameters may differ from those received from the memory of medical device 102 when medical device 102 is connected to controller 110, as described in detail below. Additionally or alternatively, optional memory 254 may be configured to store information for authentication of expansion board 118. Optional processor 255 may be a microcontroller, for example, configured to execute instructions for data signal processing stored in optional memory 254. Optional processor 255 may communicate with (e.g., to control) one or more of circuit systems 256.

[0066] The signal processing circuitry system 258 may include an FPGA configured to perform operations associated with processing or manipulating data signals routed from interface board 114 to expansion board 118. For example, one or more of a plurality of manipulation functions may be performed to manipulate the data signals. Thus, expansion board 118 can typically provide additional functionality without requiring redesign of the hardware of interface board 114, mainboard 116, or controller 110.

[0067] One example type of manipulation function may include routing data signals to low-speed differential inputs and / or high-speed differential inputs of motherboard 116. In other words, expansion board 118 may provide a pass-through connection (e.g., without modifying or altering the data signals), but may route certain data signals received from interface board 114 to low-speed differential inputs and / or high-speed differential inputs of motherboard 116. Another example type of manipulation function, which may be performed in conjunction with or independently of the above routing, may include modification or alteration of the data signals.

[0068] One example modification may include converting the data format of a data signal from a first data format to a second data format. The first data format may be a proprietary image and / or video format or another similar format incompatible with motherboard 116. The second data format may be a standard image and / or video format compatible with motherboard 116 (e.g., capable of being processed by it). Expansion board 118 may include one or more chips, such as one or more bridge chips corresponding to a specific type of image sensor 106, to facilitate the conversion of proprietary image and / or video formats of image sensor 106 to standard image and / or video formats. Another example modification may include changing the signal type of a data signal from a first signal type to a second signal type (e.g., from an analog signal to a digital signal or vice versa). Further example modifications may include adjusting the signal length and / or adjusting the signal strength. For example, expansion board 118 may be configured to add a retimer or signal conditioner to the data line to adjust the electrical length or input signal strength of the data signal.

[0069] In some examples, the signal processing circuitry 258 may be hard-coded with logic or instructions to determine which type of manipulation (e.g., routing and / or modification, and what type of modification) to perform as part of data signal processing. In other examples, this determination may be performed by the software and / or firmware of the interface board 114 and / or the motherboard 118, and the signal processing circuitry 258 may be controlled based on this determination. In a further example, when the expansion board 118 includes an optional memory 254 and an optional processor 255, the optional processor 255 may be configured to execute instructions stored in the optional memory 254 based on this determination.

[0070] Signal processing circuitry 258 can be further configured to control the operation of switching circuitry 262. Switching circuitry 262 can enable different combinations of one or more of the aforementioned operational functions of expansion board 118. For example, one switch of switching circuitry 262 can route LVDS data to the high-speed differential input of motherboard 116. The same switch can be used to route other data signals to a retimer and then to the low-speed differential input of motherboard 116. Other switches of switching circuitry 262 can be used to facilitate the routing and / or processing of data signals associated with other components in environment 100, such as data signals from optional transmitter 122 or from components of medical device 102 other than image sensor 106.

[0071] The authentication circuitry 260 enables the controller 110 to detect whether the expansion board 118 is valid upon installation. For example, one or more processors of the interface board 114 can be configured to check the authenticity of the expansion board 118 via the authentication circuitry 260 to confirm that the expansion board 118 is genuine or valid. For example, the authentication circuitry 260 can communicate with the encryption memory device of the expansion board 118 (e.g., optional memory 254) and facilitate the provision of a key from the encryption memory device to the interface board 114. At least one processor of the interface board 114 can be able to read the key to confirm that the expansion board 118 is genuine or valid.

[0072] Figure 3 An exemplary method 300 for routing data signals is depicted according to one or more aspects. In some examples, one or more steps or decisions of method 300 may be performed by an interface board 114 of controller 110. At step 302, interface board 114 may be configured to receive information from medical device 102. In some examples, the information may be received when medical device 102 is connected to controller 110. For example, during an initialization phase triggered by the connection of medical device 102 to controller 110, the received information may be included in one or more initialization signals received from medical device 102. This information may be stored in and accessed from the memory of medical device 102 for transmission via the initialization signals.

[0073] Initialization signals may include information related to or associated with the image sensor 106 of the medical device 102. For example, this information may include information identifying the hardware of the image sensor 106, such as manufacturer, model, or other similar identifiers used to indicate the type of image sensor. This information may also include information identifying characteristics of the data signals received from the image sensor 106, such as the type or format of the generated data signal, and the communication method and / or communication protocol used to transmit the generated data signal. Example data signal types may include analog and / or digital signals. Example data formats may include proprietary or standard formats for image and / or video data. Example communication protocols may include analog communication protocols (e.g., for transmitting analog signals) or digital communication protocols (e.g., for transmitting digital signals). One example digital communication protocol may include an LVDS communication protocol using differential pairs. Differential pairs can be used in different configurations to facilitate connectivity of the controller 110 to different types of medical devices 102, including medical devices 102 having one or more image sensors 106. LVDS communication protocols may include, for example, PECL or SLVS. Other example communication protocols may include the Mobile MIPI communication protocol and other known or future communication protocols.

[0074] In the example where multiple medical devices 102 are connected to the controller 110, information can be received from each medical device 102 such that information relating to a corresponding image sensor 106 of each medical device 102 is received. Additionally or alternatively, when any one or more medical devices 102 connected to the controller 110 include multiple image sensors 106, information relating to each of the image sensors 106 of the respective medical device 102 can be received as part of the information at step 302.

[0075] At step 304, interface board 114 can classify the data signals from medical device 102, specifically image and / or video data signals generated and transmitted by image sensor 106, based on the information received at step 302. The data signals can be classified as either natively supported by controller 110 or not. This classification can be used by interface board 114 to determine whether to route the data signals to mainboard 116 or expansion board 118 for further processing upon receipt.

[0076] Native support classification can indicate that at least the hardware of the motherboard 116 of the controller 110 is configured or capable of processing data signals received from the image sensor 106 of the medical device 102 without any modifications. However, in some instances, software or field-programmable gate array (FPGA) updates may be required. Therefore, based on native support classification, the interface board 114 can determine to route the data signal to the motherboard 116 when a data signal is received.

[0077] A non-native support classification may indicate that the hardware of the mainboard 116 of controller 110 is not configured or is unable to process data signals received from medical device 102. However, the hardware of expansion board 118 may be configured or may be able to process such data signals (e.g., to provide extended functionality to controller 110). In other words, expansion board 118 may provide the necessary hardware modifications to controller 110 so that controller 110 can process data signals classified as non-natively supported by, for example, routing data signals to expansion board 118 for manipulation and / or processing and then sending them to mainboard 116.

[0078] At decision 306, interface board 114 can determine whether a data signal is classified as natively supported based on the classification performed at step 304. This classification can indicate a routing path or branch through which the data signal is to be provided, as described in detail below with respect to steps 307 and 308. In some examples, the classification and / or the routing path or branch indicated by the classification can be stored in association with image sensor 106, such that when an incoming data signal is received from image sensor 106, the incoming data signal can be routed based on the stored classification and / or routing path. In examples where multiple medical devices 102 are connected to controller 110 and / or one or more medical devices 102 connected to controller 110 include multiple image sensors 106, the classification and / or the routing path indicated by the classification for each image sensor 106 can be stored in association with image sensor 106. This storage can facilitate routing, particularly when an operator switches between using medical device 102 and / or the image sensor 106 of a given medical device 102 during a medical procedure.

[0079] If, at decision 306, the data signal is classified as natively supported, method 300 proceeds to step 307. At step 307, once the incoming data signal is received from medical device 102, it is provided to motherboard 116 for further processing (e.g., for generating images and / or video for output via display device 120). For example, interface board 114 may route the data signal to motherboard 116 based on native support classification when it receives the incoming data signal via intermediate board 112 or directly (if intermediate board 112 is bypassed).

[0080] Otherwise, if at decision 306 the data signal is classified as non-natively supported, method 300 proceeds to step 308. At step 308, once the incoming data signal is received from medical device 102, it is provided to expansion board 118 for manipulation. For example, interface board 114 may route the incoming data signal to expansion board 118 based on the non-native support classification when it receives the incoming data signal via intermediate board 112 or directly (if intermediate board 112 is bypassed). See reference... Figure 2 As described in detail, the operations performed by the expansion board 118 of example types may include routing incoming data signals to low-speed differential inputs and / or high-speed differential inputs of the motherboard 116, and / or modifying or altering the incoming data signals. Example modifications or alterations may include converting the data format or signal type of the data signals, adjusting the signal length, and / or adjusting the signal strength.

[0081] At step 310, expansion board 118 may be configured to provide manipulated data signals to motherboard 116 for further processing (e.g., for generating images and / or videos for output via display device 120). In some examples, expansion board 118 may be configured to route manipulated data signals to low-speed differential inputs and / or high-speed differential inputs of motherboard 116.

[0082] Although Figure 3 Method 300 described herein describes steps and / or decisions performed by interface board 114 for routing data signals received from medical device 102, and more specifically its image sensor 106; however, the same or similar steps may also be performed for data signals received from optional transmitter 122. For example, at step 302, interface board 114 may be configured to receive information from optional transmitter 122 and may repeat at least one or more of steps or decisions 304, 306, 308, and 310 based on the data signals received from optional transmitter 122. For example, the data signals may be classified as non-natively supported and provided to expansion board 118 for manipulation.

[0083] Therefore, some aspects may include classification-based routing of data signals. The method 300 described above is provided only as an example and may include... Figure 3 The steps and / or decisions described herein are fewer, different, or arranged differently compared to additional steps and / or decisions.

[0084] Figure 4 Two exemplary paths for routing data signals are depicted based on one or more aspects. For example, interface board 114 may be configured to route data signal 403 received from image sensor 106 of medical device 102 along one of a first path 400 or a second path 402. Determining whether to route data signal 403 via the first path 400 or the second path 402 may be based on a classification performed by interface board 114 to categorize data signals (such as data signal 403) generated by and transmitted by image sensor 106 (or alternatively, optional transmitter 122) as either natively supported or non-natively supported by controller 110, as referenced. Figure 3 Detailed description.

[0085] For illustrative purposes, data signal 403 may be received by intermediate board 112 from image sensor 106 of medical device 102 (or alternatively, transmitter 122). Data signal 403 can then be transmitted from intermediate board 112 to interface board 114. In other examples, intermediate board 112 may be bypassed, and data signal 403 may be received directly by interface board 114.

[0086] Based on natively supported classification, data signal 403 can be transmitted along the first path 400 to the motherboard 116 for further processing. Alternatively, based on a non-natively supported classification, data signal 403 can be transmitted along the second path 402 to the expansion board 118. The expansion board 118 can be configured to manipulate data signal 403 to generate manipulated data signal 406, and provide manipulated data signal 406 to the motherboard 116 for further processing.

[0087] The motherboard 116 can be configured to process data signal 403 or manipulated data signal 406 to generate and output processed image or video data, which can then be displayed to the operator of the medical device 102 via display device 120.

[0088] Figure 5 An example of a computer 500 is described based on one or more aspects. Figure 5 This is a simplified functional block diagram of a computer 500 according to an exemplary embodiment of the present disclosure, the computer being configured to perform... Figures 1 to 4 The device depicted or described with respect to these figures represents a process, step, or operation. For example, computer 500 may be configured as one or more of the following: medical device 102, controller 110, intermediate board 112, interface board 114, expansion board 118, motherboard 116, display device 120, optional transmitter 122, optional server-side system 130, and / or another device or component according to an exemplary aspect of this disclosure. In various aspects, any system herein may be or include computer 500, which includes, for example, a data communication interface 520 for packet data communication. Computer 500 may communicate with one or more other computers, for example, using an electronic network 525 (e.g., via data communication interface 520). Electronic network 525 may include wired or wireless networks, such as those similar to... Figure 1 The network 140 is depicted in the text.

[0089] Computer 500 may also include a central processing unit (“CPU”) in the form of one or more processors 502 for executing program instructions 524. In some examples, the processor may include an FPGA. Program instructions 524 may include instructions for performing data signal routing logic, data signal processing or manipulation, and / or image processing.

[0090] Computer 500 may include an internal communication bus 508. Computer 500 may also include a drive unit 506 (such as read-only memory (ROM), hard disk drive (HDD), solid-state drive (SDD), etc.) that can store data on a computer-readable medium 522 (e.g., a non-transitory computer-readable medium), although computer 500 may receive programming and data via network communication. Computer 500 may also have a memory 504 (such as random access memory (RAM)) storing instructions 524 for performing the techniques presented herein. However, it should be noted that in some aspects, instructions 524 may be temporarily or permanently stored within other modules of computer 500 (e.g., processor 502 and / or computer-readable medium 522). Computer 500 may also include user input and output devices 512 and / or a display 510 for connection to input and / or output devices such as a keyboard, mouse, touchscreen, monitor, display, etc. Various system functions may be implemented in a distributed manner on multiple similar platforms to distribute the processing load. Alternatively, these systems may be implemented by appropriately programming a single computer hardware platform.

[0091] The program aspect of this technology can be considered a "product" or "artifact" typically in the form of executable code and / or associated data carried or embodied on a type of machine-readable medium. "Storage" media includes any or all of the tangible memory of computers, processors, etc., or their associated modules (such as various semiconductor memories, tape drives, disk drives, etc.), which can provide non-transitory storage for software programming at any time. All or part of the software can sometimes be communicated via the Internet or various other telecommunications networks. Such communication, for example, enables the loading of software from one computer or processor into another. Therefore, another type of medium that can carry software elements includes light waves, radio waves, and electromagnetic waves, such as physical interfaces between local devices, used via wired and optical terrestrial networks, and via various air links. Physical elements carrying such waves (such as wired or wireless links, optical links, etc.) can also be considered as media carrying software. As used herein, unless limited to non-transitory tangible "storage" media, terms such as "computer or machine-readable medium" refer to any medium involved in providing instructions to a processor for execution.

[0092] While the principles of this disclosure have been described herein with reference to illustrative examples of specific applications, it should be understood that this disclosure is not limited thereto. Those skilled in the art and those who have received the teachings provided herein will recognize that additional modifications, applications, and substitutions of equivalents fall within the scope of the examples described herein. Therefore, the invention should not be considered limited to the foregoing description.

Claims

1. A computing system, comprising: Multiple signal processing boards are configured to perform operations including: The first signal processing board among the plurality of signal processing boards receives data signals from the image sensor of a medical device removably connected to the computing system; The first signal processing board determines, based on information associated with the image sensor, whether to route the data signal to a second or third signal processing board among the plurality of signal processing boards, the information including one or more features associated with the data signal that indicate whether they are natively supported or not natively supported by the computing system; Based on the determination that it is not natively supported, the first signal processing board provides the data signal to the third signal processing board, wherein the third signal processing board is an expansion board that is removably connected to the computing system; The data signal is manipulated by the third signal processing board; and The manipulated data signal is provided to the second signal processing board by the third signal processing board for processing.

2. The computing system as described in claim 1, wherein, Information associated with the image sensor includes whether the data signal has a first data format or a second data format.

3. The computing system as described in claim 2, wherein, When the data signal has the first data format, the data signal is provided to the third signal processing board by the first signal processing board, and wherein manipulating the data signal includes converting the data signal from the first data format to the second data format.

4. The computing system as described in claim 2, wherein, Information associated with the image sensor includes the data signal type of the data signal, and one or more communication methods or protocols used by the image sensor to transmit the data signal.

5. The computing system as described in any one of the preceding claims, wherein, The second signal processing board includes a low-speed differential input terminal and a high-speed differential input terminal, and manipulating the data signal includes routing the data signal to a specific input terminal of the low-speed differential input terminal or the high-speed differential input terminal of the second signal processing board.

6. The computing system as described in any of the preceding claims, wherein, Manipulating the data signal includes modifying or altering the data signal to generate the manipulated data signal.

7. The computing system of claim 6, wherein, Modifying or altering the data signal to generate the manipulated data signal includes at least one of the following: Convert the data signal from a first data format to a second data format; Convert the data signal from a first signal type to a second signal type; Adjust the length of the data signal; or Adjust the strength of the data signal.

8. The computing system as described in any of the preceding claims, wherein, The operation further includes: The first signal processing board determines one or more functions to be implemented by the third signal processing board to manipulate the data signal.

9. The computing system as claimed in any of the preceding claims, wherein, In response to the medical device being connected to the computing system, information associated with the image sensor is received from the memory of the medical device.

10. The computing system as claimed in any of the preceding claims, wherein, The data signal is a first data signal, the transmitter is associated with the medical device, and the operation further includes: The first signal processing board receives the second data signal from the transmitter. The first signal processing board determines, based on one or more characteristics associated with the second data signal, to transmit the second data signal to the third signal processing board. The second data signal is manipulated by the third signal processing board; and The manipulated second data signal is provided to the second signal processing board by the third signal processing board for processing.

11. The computing system of claim 10, wherein, The third signal processing board is configured to enable bidirectional data transmission between the transmitter and the computing system.

12. The computing system as claimed in any of the preceding claims, wherein, Manipulating the data signal includes performing one or more of a plurality of manipulation functions, and the third signal processing board further includes a switching circuit system configured to facilitate a combination of the plurality of manipulation functions.

13. The computing system as claimed in any of the preceding claims, wherein, The third signal processing board further includes an authentication circuit system configured to, when the third signal processing board is connected to the computing system, facilitate the determination by the first signal processing board of the authenticity of the third signal processing board to be used in the computing system.

14. The computing system as claimed in any of the preceding claims, wherein, The third signal processing board further includes one or more illumination elements configured to indicate the connection status of the third signal processing board with the computing system.

15. The computing system as claimed in any of the preceding claims, wherein, The data signal is a first data signal, the image sensor is a first image sensor, and the operation further includes: The first signal processing board receives a second data signal from a second image sensor, which is different from the first image sensor. The first signal processing board, based on information associated with the second image sensor, determines whether to route the second data signal to the second signal processing board or the third signal processing board, the information including one or more features associated with the second data signal indicating whether they are natively supported or not natively supported by the computing system; and Based on the determination that it is natively supported, the first signal processing board provides the second data signal to the second signal processing board for processing.

Images