Browse Prior Art Database

Intra-Oral (IO) Camera Scan History Review With Roll Back

IP.com Disclosure Number: IPCOM000250492D
Publication Date: 2017-Jul-25
Document File: 5 page(s) / 246K

Publishing Venue

The IP.com Prior Art Database

Abstract

In one example implementation, each capture by the IO camera generates a single view containing a fixed mesh, e.g., 3D contour image, with a unique identifier (ID). In this case, scan history review and roll back function can be performed using IDs. In one case, scan history can be done by hide and/or show some meshes through IDs.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 55% of the total text.

DisclosureTitle Intra-Oral (IO) camera Scan History Review With Roll Back

In one example implementation, each capture by the IO camera generates a single view

containing a fixed mesh, e.g., 3D contour image, with a unique identifier (ID). In this case, scan

history review and roll back function can be performed using IDs. In one case, scan history can

be done by hide and/or show some meshes through IDs.

The following Figures show details of this functionality implementation.

Scan history review:

(i) Move slide bar to show the scan history review.

(ii) Roll backward:

(iii) Click operation/selected button (e.g., OK button) to go to current scan data.

In another example implementation, each capture by the IO camera generates point clouds to

store capture data. In the scan history, points in the point cloud may be insert, update, merge,

and/or delete during captures. In one implementation, the world space coordinate system can

be partitioned (e.g., averagely) into some blocks (e.g., 20mm*20mm*20mm), and convert the

points in a block to a mesh with unique identification (ID).

Preferably, each point in the point clouds has an attribute (capture ID) to recode the capture

time and/or capture order. The capture ID is used as the relative capture time or order. When

reviewing history in this case, compute which points should be appear or disappear by

comparing the capture ID, and then trigger point events to refresh meshes.

For example, suppose there are N count of capture IDs, and a user move the slide bar to

review the capture ID s less then M; then, all points with capture ID larger then M should

disappear.

Further, the scan history can only trigger changed point events by increment to avoid trigger

duplicate...