Patent Description:
An interactive white board usually has multiple channel modules, such as an Android module and a PC module. Therefore, when using different channel modules, it is necessary to send touch data to a corresponding module.

In the prior art, a usual way is to set a USB-Switch switch between a channel module and a processor. <FIG> is a schematic diagram of a system for distributing touch data in the prior art. As shown in <FIG>, distribution channels for touch data in this example include a PC module channel, an Android module channel, and external channels HD, MI/DP/VGA, etc. The touch device is configured to generate the touch data, and the Android master chip controls on-off between the USB-Switch and each channel.

In the above example, the Android master chip uses an MCU to control the USB-Switch to disconnect and reconnect D+/D- data lines of a USB bus. However, once performing the reconnection, there is unnecessary time-consuming, resulting in unavailability of the touch device for a period of time. The interactive white board needs to re-enumerate hardware USB plugging and unplugging, which usually takes <NUM> to <NUM> seconds. During this time period, the interactive white board does not recognize the touch device, and the touch device cannot be operated. <CIT> discloses a touch TV and controlling method and device thereof to.

solve the existing technology problem of using a touch screen to realize the function controlling of the touch TV itself. <CIT>provides a data processing method and apparatus, reducing abnormal control caused by packet loss. <CIT> discloses a touch panel system, compensating touch information between certain touch position and next position.

With regard to the problem in the prior art that there is excessive time consumption due to the necessity of re-enumerating a touch device when a touch display channel is switched through a switch, no effective solution has been proposed yet.

At least some embodiments of the present application provide a data processing method, device and system for an interactive white board, and an interactive white board, so as to at least solve the technical problem in the prior art that there is excessive time consumption due to the necessity of re-enumerating a touch device when a touch display channel is switched through a switch.

According to one aspect of one of embodiments of the present application, there is provided an interactive white board, including all the features of appended claim <NUM>.

Optionally, the interactive white board further includes: a second control unit connected in series with the first control unit, where the second control unit is also connected to multiple second channel modules through corresponding display channels; where the first control unit is further configured to send the second touch data to the second control unit when the display channel corresponding to the second touch data is a display channel of any second channel module, so as to enable the second control unit to send the touch data to the corresponding display channel.

According to another aspect of one of the embodiments of the present application, there is also provided a data processing method for an interactive white board, including all the features of appended claim <NUM>.

Optionally, enumerating the touch device; selecting data generated by the touch device out of the received data according to a device identifier of the touch device; and selecting, according to characteristic information of touch data, the touch data out of the data generated by the touch device as the first one touch data.

Optionally, a display channel has a corresponding identifier, determining, according to the current display channel of the interactive white board, an identifier for marking the first touch data; and marking the first touch data according to the identifier to generate the second touch data.

Optionally, detecting whether the display channel changes, where the display channel changes when the interactive white board switches a channel module; in case the display channel changes, detecting whether a last set of touch data before the display channel changes is in its integrity; if the last set of touch data before the display channel changes is not in its integrity, using supplement points to supplement an end point of the last set of touch data before the display channel changes and a start point of a first set of touch data after the display channel changes, where the supplement points are first touch points after the display channel changes.

Optionally, acquiring a target bit corresponding to the current display channel of the interactive white board, where the identifier includes multiple bits, and each bit corresponds to a channel module; setting a value of the target bit in the identifier to be opposite to a value of a remaining bit to obtain the identifier for marking the first touch data.

Optionally, using the first touch data to drive an input subsystem; and responding to the first touch data.

According to another aspect of the embodiments of the present application, there is also provided a data processing method for an interactive white board, which includes: receiving second touch data sent by a device processor, where the second touch data includes an identifier corresponding to a current display channel of the interactive white board; reading the identifier and determining the current display channel; and distributing the second touch data to a channel module corresponding to the current display channel.

Optionally, sending the second touch data to a data queue of the channel module; and sequentially distributing the second touch data in the data queue to the channel module.

According to another aspect of one of the embodiments of the present application, there is also provided a data processing device for an interactive white board, including: a first receiving module, configured to receive first touch data generated by a touch device; an adding module, configured to mark the first touch data according to a current display channel of the interactive white board to obtain second touch data, where the second touch data includes an identifier corresponding to the current display channel; and a sending module, configured to send the second touch data to a control unit, where the control unit is also configured to distribute the second touch data to the corresponding channel module according to the identifier.

According to another aspect of one of the embodiments of the present application, there is also provided a data processing device for an interactive white board, including: a second receiving module, configured to receive second touch data sent by a device processor, where the second touch data includes an identifier corresponding to a current display channel of the interactive white board; a reading module, configured to read the identifier and determine the current display channel; and a distributing module, configured to distribute the second touch data to a channel module corresponding to the current display channel.

According to another aspect of one of the embodiments of the present application, a storage medium is also provided. The storage medium includes all the features of appended claim <NUM>.

According to another aspect of one of the embodiments of the present application, a processor is also provided, comprising all the features of appended claim <NUM>.

In at least some of the embodiments of the present application, touch data is marked to enable a control unit to distribute the touch data to a corresponding channel module, and thus a connection relationship between the channel module and the control unit can be maintained, without the requirement of disconnection and reconnection through a switch. Therefore, after the interactive white board is turned on again, there is no need to re-enumerate the USB device, thereby solving the problem in the prior art that there is excessive time consumption due to the necessity of re-enumerating a touch device when a touch display channel is switched through a switch. Moreover, the touch device can be used immediately after the display channel is switched, which improves user comfort.

The drawings described herein are used to provide a further understanding of the application and constitute a part of the application. Exemplary embodiments of the application and description thereof are used to explain the application, and do not constitute an improper limitation of the application. In the attached drawings:.

In order to enable those skilled in the art to better understand the solutions of the application, the technical solutions in the embodiments of the application will be clearly and completely described below in conjunction with the drawings in the embodiments of the application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments.

It should be noted that the terms "first" and "second" in the description and claims of the application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific sequence or sequence. It should be understood that data used in this way is interchangeable under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any variation of them are intended to cover non-exclusive inclusions. For example, processes, methods, systems, products, or devices that include a series of steps or units are not necessarily limited to those clearly listed steps or units, but may include other steps or units that are not clearly listed or that are inherent to these processes, methods, products, or devices.

According to an embodiment of the present application, an embodiment of an interactive white board is provided. <FIG> is a schematic diagram of an interactive white board according to an embodiment of the present application. As shown in <FIG>, the system includes:.

A touch box <NUM>, configured to generate first touch data.

Optionally, the touch device may have functions such as electromagnetic touch, infrared touch, and capacitive touch. When a user operates the touch device, the touch device generates first touch data.

A device processor <NUM>, connected to the touch device, and configured to mark the first touch data according to a current display channel to obtain second touch data, where the second touch data includes an identifier corresponding to the current display channel.

Optionally, the above device processor is a master processor of the system, which can be a processing chip, such as an Android master chip. The channel module can be a PC module, an Android module, an external module, etc., and the current display channel can be one or multiple in number. The interactive white board usually displays two systems at the same time, that is, the current display channel is two in number. For example, for an interactive white board with a sidebar, the sidebar can display the content output by the display channel of the device processor (that is, the master chip of the interactive white board, running an Android system), and the master interface can display the content output by the external display channel.

In an optional embodiment, the channel module has a corresponding identifier, the device processor may add the identifier of the channel module to the received first touch data for the first control unit to recognize, and the marked touch data is the second touch data.

A first control unit <NUM>, connected to the device processor, and is configured to distribute the second touch data to the display channel corresponding to the identifier in the second touch data.

Optionally, after receiving the second touch data, the first control unit reads the identifier therein and determines, according to the identifier, the channel module to which the second touch data needs to be distributed.

In the above solution, there is no need to switch the communication relationship between the control unit and the channel module through the USB switch. Instead, the control unit distributes the touch data to the corresponding channel module according to the identifier.

Multiple first channel modules <NUM>, connected to the first control unit through corresponding data display channels, and are configured to receive the second touch data.

Optionally, the distribution of the touch data is controlled by the first control unit, and the first channel modules directly maintain connection relationships with the first control unit and only need to wait for the touch data.

It can be seen from the above that, in the above-mentioned embodiment of the present application, touch data is marked to enable a control unit to distribute the touch data to a corresponding channel module, and thus a connection relationship between the channel module and the control unit can be maintained, without the requirement of disconnection and reconnection through a switch. Therefore, after the interactive white board is turned on again, there is no need to re-enumerate the USB device, thereby solving the problem in the prior art that there is excessive time consumption due to the necessity of re-enumerating a touch device when a touch display channel is switched through a switch. Moreover, the touch device can be used immediately after the display channel is switched, which improves user comfort.

Optionally, according to the above embodiments of the present application, the above system also includes:.

<FIG> is a schematic diagram of an optional interactive white board according to an embodiment of the present application. As shown in <FIG>, the touch device is connected to the master chip, and the Android master chip (master processor) is connected to MCU1 (first control unit), MCU1 is connected to module A and module B (multiple first channel modules). At the same time, MCU1 is also connected in series with MCU2 (second control unit), and MCU2 is connected with module C and module D (multiple second channel modules). When the identifier of the touch data is an identifier corresponding to module A or module B, MCU1 distributes the touch data to module A or module B. When the identifier of the touch data is an identifier corresponding to module C or module D, MCU1 distributes the touch data to MCU2, and MCU2 distributes it to module C or module D.

It should be noted that this embodiment is applied to an example scenario where one control unit is cascaded, also, more control units can be cascaded in this solution.

According to an embodiment of the present application, an embodiment of a data processing method for an interactive white board is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system with a set of computer executable instructions, for example. Moreover, although a logical sequence is shown in the flowchart, in some cases, the steps shown or described may be performed in an order different from that here.

<FIG> is a flowchart of a data processing method for an interactive white board according to an embodiment of the present application. The data processing method for the interactive white board provided in this embodiment can be applied to the interactive white board in Embodiment <NUM>. As shown in <FIG>, the method includes the following steps:
Step S402: Receiving first touch data generated by a touch device.

Optionally, the steps in this embodiment may be executed by the device processor. The aforementioned touch device may have functions such as electromagnetic touch, infrared touch, and capacitive touch. When the user operates the touch device, the touch device generates first touch data.

Step S404: Marking the first touch data according to a current display channel of the interactive white board to obtain second touch data, where the second touch data includes an identifier corresponding to the current display channel.

Optionally, the channel module can be a PC module, an Android module, an external module, etc. In an optional embodiment, the marking the first touch data may be adding an identifier corresponding to the current display channel to the first touch data, where the adding position may be an identification bit in the data header of the first touch data, and the identification bit is configured to hold the identifier.

Step S406: Sending the second touch data to a control unit, where the control unit is further configured to distribute the second touch data to the corresponding display channel according to the identifier.

In the above steps, the device processor distributes the constructed second touch data to the control unit, and the control unit distributes the second touch data according to the identifier.

In an optional embodiment, after receiving the second touch data, the control unit reads the identification bit of the second touch data, and distributes the second touch data to a corresponding channel module according to the corresponding relationship between the identifier and the channel module.

It can be seen from the above that, in the above embodiments of the present application, first touch data generated by a touch device is received, and the first touch data is marked according to a current display channel of a channel module currently running on the interactive white board to obtain second touch data, where the second touch data includes an identifier corresponding to the current display channel, and the second touch data is sent to a control unit, where the control unit is further configured to distribute the second touch data to the corresponding channel module according to the identifier. Through marking the touch data to enable a control unit to distribute the touch data to a corresponding channel module, a connection relationship between the channel module and the control unit can be maintained without the requirement of disconnection and reconnection through a switch. Therefore, after the interactive white board first enumerates the touch device when it is turned on, there is no need to re-enumerate the USB device, thereby solving the technical problem in the prior art that there is excessive time consumption due to the necessity of re-enumerating a touch device when a touch display channel is switched through a switch. Moreover, the touch device can be used immediately after the display channel is switched, which improves user comfort.

Optionally, according to the embodiment of the present application, the receiving the first touch data generated by the touch device includes:
Step S4021: Enumerating the touch device.

Optionally, part of an HID-CORE file can be driven by an HID (Human Interface Device) to enumerate the touch device.

Step S4023: Selecting data generated by the touch device out of the received data according to a device identifier of the touch device.

Optionally, the above-mentioned device identifier may include a PID/VID (vendor ID/product ID, manufacturer ID/product ID), where different USB devices have different PIDs/VIDs, therefore, the device processor can identify the data from the touch device according to the PID/VID.

Step S4025: Selecting, according to characteristic information of touch data, the touch data out of the data generated by the touch device as the first touch data.

Optionally, the above-mentioned characteristic information includes a report ID and a data length. The report ID is configured to indicate the type of data. Therefore, the device processor can select out the touch data according to the type of data as the first touch data.

Optionally, according to the foregoing embodiment of the present application, the channel module has a corresponding identifier, and the marking the first touch data according to the current display channel of the interactive white board to obtain the second touch data includes:
Step S4041: Determining, according to the current display channel of the interactive white board, an identifier for marking the first touch data.

In an optional embodiment, the device processor is pre-stored with a corresponding relationship between the display channel and the identifier, and the device processor can determine its identifier after determining the current display channel of the interactive white board.

Step S4043: Marking the first touch data according to the identifier to generate the second touch data.

In an optional embodiment, the identifier of the first touch data may be carried in the header of the data packet of the first touch data.

Optionally, according to the embodiment of the present application, before determining the identifier for marking the first touch data according to the current display channel, the method further includes:
Step S4045: Detecting whether the display channel changes, where the display channel changes when the interactive white board switches a channel module.

Optionally, when the user switches the channel module, the display channel of the interactive white board changes. In an optional embodiment, taking a smart interactive white board as an example, the smart interactive white board has multiple types of channel modules, such as an Android module and a PC module, so as to provide multiple types of systems. When using the smart interactive white board, the user can perform system switching. When the user performs the system switching, the device processor detects that the display channel changes.

Step S4047: In case the display channel changes, detecting whether a last set of touch data before the display channel changes is in its integrity.

Optionally, the last set of data before the display channel changes is data about the last touch event before the display channel changes. A set of touch events has a flow of down-move-move. In case the data about the set of touch events is in its integrity, it includes a start point data packet (down point data packet), a control point data packet (multiple move point data packets), and an end point data packet (up point data packet); and in case the touch events lack the start point data packet or the end point data packet, the touch data is not in its integrity.

In an optional embodiment, the smart interactive white board is still taken as an example. The smart interactive white board is currently running on the Android system, and the user is operating the touch screen. When the user has not lifted his finger, the smart interactive white board switches to the Windows system according to an instruction. In this case, the last set of touch events in the Android system does not have the up point data packet, and the Windows system does not have the down point data packet in the first set of touch events, and thus the two sets of touch events are not in their integrity.

Step S4049: If the last set of touch data before the display channel changes is not in its integrity, using supplementary points to supplement an end point of the last set of touch data before the display channel changes and a start point of the first set of touch event after the display channel changes, where the supplementary points are first touch points after the display channel changes.

Optionally, although the first set of touch events after the display channel changes does not have the down point data packet, the touch device can still receive the touch data, so the touch data of the first touch point received after the touch device is switched is used as both the up point data packet of the last set of touch events before the display channel changes and the down point data packet of the first set of touch events after the display channel is switched, so as to complement the two sets of touch events which are not in their integrity.

<FIG> is a flowchart of processing first touch data by a device processor according to an embodiment of the present application. The above solution will be described below with reference to <FIG>.

Step S52: Detecting whether the display channel changes. In case that the display channel changes, proceed with step S53, otherwise proceed with step S55.

Step S53: Supplementing a data packet according to status of touch points.

Optionally, for the above step, the data packet may be supplemented in a manner as described in step S4049, so that the touch events before and after the display channel changes are completely supplemented.

Step S54: Updating the identifier according to the updated display channel.

In the above steps, since the channel module is switched, the display channel needs to be updated. Each channel module corresponds to a different identifier. Therefore, the identifier of the updated channel module and the first touch data are used together to construct the second touch data.

Step S55: Constructing the second touch data according to the identifier of the unchanged display channel.

Step S56: Outputting the second touch data having the identifier.

In the above step S56, the second touch data is output to the control unit, and is distributed by the control unit to the corresponding channel module according to the identifier.

Optionally, according to the above embodiment of the present application, the determining, according to the current display channel of the interactive white board, the identifier for marking the first touch data includes:
Step S40411: Acquiring a target bit corresponding to the current display channel of the interactive white board, where the identifier includes multiple bits, and each bit corresponds to a channel module.

In an optional embodiment, the identifier may be one byte, which includes eight bits, and the data of each bit may indicate the corresponding channel module. The target bit is a currently running channel module, i.e., a channel module that needs to receive the touch data.

It should be noted that if there are many channel modules, the identifier can be set to two bytes usable by <NUM> channel modules.

In step S40413: Setting a value of the target bit in the identifier to be opposite to a value of a remaining bit to obtain the identifier for marking the first touch data.

In the above step S40413, if the value of the remaining bit is <NUM>, the value of the target bit may be <NUM>, and if the value of the remaining bit is <NUM>, the data of the target bit may be <NUM>. After each bit in the identifier is set to a corresponding value, the identifier of the first touch data is obtained.

In an optional embodiment, as shown in <FIG>, the identifier is of <NUM> byte (<NUM> bits), each bit represents the output of one module, the <NUM>-th bit represents a USB bypass of module A; the <NUM>-st bit represents a USB bypass of module B, and so on.

When modules A, B, C, and D all need touch data, set the identifier to 0x0F (hexadecimal number, the corresponding binary is <NUM>), and the MCU judges whether to output USB touch data according to the identification bit.

In the case that only module A needs the touch data, the identifier is set to 0x01 (hexadecimal number, the corresponding binary is <NUM>), and the MCU determines whether to output USB touch data according to the identification bit.

Optionally, according to the above embodiment of the present application, after enumerating the touch device, the method further includes:
Step S4010: Using the first touch data to drive an input subsystem.

Optionally, the above input subsystem may be an INPUT subsystem in a system processor, which is configured to manage a touch event received by the interactive white board.

Step S4012: Responding to the first touch data.

In the above step S4012, the first touch data reads the touch event from the system processor and executes it.

<FIG> is a data interaction diagram of an optional touch event according to an embodiment of the present application. The data flow of the touch event will be described below with reference to <FIG>. Touch data circulates in the touch device, Android master chip (device processor), MCU (control unit), and module/external channel (channel module).

Step S61: The touch device reports data.

Optionally, when the user operates on the touch device, the touch data is generated.

Step S62: An HID (Human interface device) drives part of HID-CORE original data.

Optionally, the above step S62 is used to enumerate the touch device.

Step S63: Select a USB device as the touch device according to a PID/VID.

Optionally, the device processor can be connected to a variety of USB devices, and each USB device has a corresponding PID (Product, product ID) and VID (Product, manufacturer ID), so the touch device can be identified by the PID/VID.

Step S64: Select out the touch data according to a report ID and a data length.

In the above steps, the report ID and the data length are the characteristic information of the touch data, and the Android master chip selects the touch data out of various data according to the data characteristic of the touch data.

Step S65: Process the touch data according to current channel information.

Optionally, the current channel information is channel information of the currently running channel module, and each channel module corresponds to a corresponding identifier. Therefore, step S65 may be determining the identifier of the current channel, and adding the identifier of the current channel as a data header to the touch data. The specific processing flow can be shown in <FIG>.

Step S66: Output the touch data to the MCU.

After step S65, the Android master chip sends the touch data added with the identifier to the MCU, and the MCU performs distribution to the channel module.

Step S67: Receive data of the touch device.

In the above step S67, the MCU receives the touch device data transmitted by the Android master chip.

Step S68: Distribute a sending queue to the USB according to the identifier.

Optionally, each channel module has a corresponding sending queue. In the above steps, the MCU extracts an identifier from the touch data, determines, according to the identifier, a channel module to which the identifier needs to be sent, and then sends the touch data to the sending queue of the channel module so that each channel module that needs touch data can receive the touch data, while a channel module that does not need touch data will not receive the touch data.

Step S69: Each USB detects whether there is data in the sending queue, and sends it if the data exists.

Optionally, the display channel of each channel module has a corresponding sending queue for storing the received touch events, and the touch events in the sending queue are sent to the channel module in sequence according to the received order.

Step S610: The module receives the touch data and performs a touch response.

Step S611: The touch event drives the INPUT subsystem.

Optionally, the aforementioned INPUT subsystem is configured to manage a touch event received by the Android master chip.

Step S612: The Android system responds to the touch event.

According to an embodiment of the present application, an embodiment of a data processing method for an interactive white board is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system with a set of computer executable instructions, for example. Moreover, although a logical sequence is shown in the flowchart, in some cases, the steps shown or described may be performed in an order different from that.

<FIG> is a flowchart of a data processing method for an interactive white board according to an embodiment of the present application. The data processing method for the interactive white board provided in this embodiment can be applied to the interactive white board in Embodiment <NUM>. As shown in <FIG>, the method includes the following steps:
Step S702: Receiving second touch data sent by a device processor, where the second touch data includes an identifier corresponding to a current display channel of the interactive white board.

Optionally, the steps in this embodiment may be executed by the first control unit in Embodiment <NUM>. The second touch data is generated by the device processor according to the identifier of the currently running channel module and the first touch data.

Step S704: Reading the identifier and determining the current display channel.

Specifically, due to the corresponding relationship between the identifier and the display channel, the control unit may determine the channel module corresponding to the touch data according to the identifier.

Step S706: Distributing the second touch data to a channel module corresponding to the current display channel.

After obtaining the second touch data, the channel module can respond to the second touch data.

It can be seen from the above that, in the foregoing embodiment of the present application, second touch data sent by a device processor is received, where the second touch data includes an identifier corresponding to a current display channel; the identifier is read and the current display channel is determined; and the second touch data is distributed to a channel module corresponding to the current display channel. According to the above solution, touch data is marked to enable a control unit to distribute the touch data to a corresponding channel module, and thus a connection relationship between the channel module and the control unit can be maintained without the requirement of disconnection and reconnection through a switch. Therefore, after the interactive white board first enumerates the touch device when it is turned on, there is no need to re-enumerate the USB device, thereby solving the technical problem in the prior art that there is excessive time consumption due to the necessity of re-enumerating a touch device when a touch display channel is switched through a switch. Moreover, the touch device can be used immediately after the display channel is switched, which improves user comfort.

Optionally, according to the foregoing embodiment of the present application, the distributing the second touch data to the channel module corresponding to the current display channel includes:
Step S7061: Sending the second touch data to a data queue of the channel module.

Step S7063: Sequentially distributing the second touch data in the data queue to the channel module.

According to an embodiment of the present application, an embodiment of a data processing device for an interactive white board is provided. <FIG> is a schematic diagram of a data processing device for an interactive white board according to an embodiment of the present application. As shown in <FIG>, the device includes:.

According to an embodiment of the present application, a storage medium is provided. The storage medium includes a stored program, where when the program is running, an interactive white board in which the storage medium is located is controlled to perform the following steps: receiving first touch data generated by a touch device; marking the first touch data according to a current display channel of the interactive white board to obtain second touch data, where the second touch data includes an identifier corresponding to the current display channel; and sending the second touch data to a control unit, where the control unit is further configured to distribute the second touch data to the corresponding display channel according to the identifier.

According to an embodiment of the present application, a processor is provided. The processor is configured to run a program, where the program executes the following steps when the program is running: receiving first touch data generated by a touch device; and marking the first touch according to a current display channel of an interactive white board to obtain second touch data, where the second touch data includes an identifier corresponding to the current display channel; and sending the second touch data to a control unit, where the control unit is further configured to distribute the second touch data to the corresponding display channel according to the identifier.

The serial numbers of the foregoing embodiments of the present application are only for description, and do not represent superiority of the embodiments.

In the above-mentioned embodiments of the present application, the description of each embodiment has its own focus. For parts that are not described in detail in an embodiment, reference may be made to related descriptions of other embodiments.

In the several embodiments provided in the present application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of the units can be a logical function division, and there can be other divisions in actual implementation, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, units or modules, and may be in electrical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple units.

In addition, the functional units in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the part that contributes to the prior art or all or part of the technical solutions can be embodied in the form of a software product, and the computer software product is stored in a storage medium which includes several instructions enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage media includes: a U disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a mobile hard disk, a magnetic disk or an optical disk and other media on which program codes can be stored.

The above description is only preferred embodiments of the present application. It should be pointed out that for those of ordinary skill in the art, without departing from the principle of the present application, several improvements and modifications can be made.

Claim 1:
An interactive white board, comprising: a touch device (<NUM>), a device processor (<NUM>), a first control unit (<NUM>), and multiple first channel modules (<NUM>), wherein the touch device (<NUM>) is connected to the device processor (<NUM>), the device processor (<NUM>) is connected to the touch device (<NUM>) and the first control unit (<NUM>), and the first control unit (<NUM>) is connected to the device processor (<NUM>) and the multiple first channel modules (<NUM>), wherein:
the touch device (<NUM>), is configured to generate first touch data and send the first touch data to the device processor (<NUM>);
the device processor (<NUM>), is configured to mark the first touch data according to a current display channel to generate second touch data and send the second touch data to the first control unit (<NUM>), wherein the second touch data comprises an identifier corresponding to the current display channel;
the first control unit (<NUM>), is configured to distribute the second touch data to a corresponding one of the multiple first channel modules (<NUM>) according to the identifier corresponding to the current display channel; and
the first channel modules (<NUM>), is configured to receive the second touch data and and make a touch response,
characterized in that the device processor (<NUM>) is further configured to, prior to determining the identifier for marking the first touch data according to the current display channel of the interactive white board, perform the following steps:
detecting whether the display channel changes, wherein the display channel changes when the interactive white board switches a channel module;
if the display channel changes, detecting whether a last set of touch data before the display channel changes is in its integrity; and
if the last set of touch data before the display channel changes is not in its integrity, using supplementary points to supplement an end point of the last set of touch data before the display channel changes and a start point of a first set of touch data after the display channel changes, wherein the supplementary points are first touch points after the display channel changes.