Patent Grant
9885672
The present disclosure is directed generally to methods and systems for evaluating mobile phones and other consumer electronic devices and, more particularly, to methods and systems associated with detecting screen covers on such devices.
It is often necessary to visually evaluate a mobile device (e.g., a smartphone or tablet) to identify cracks or other defects in the mobile device. For example, pricing the mobile device, assessing the mobile device for possible repair, and evaluating the mobile device for warranty coverage may all require identification of any cracks in the mobile device. Individualized manual inspection of mobile devices for cracks is slow, cumbersome, and can yield inconsistent results. Current automated methods for detecting cracks in other contexts are often over-inclusive resulting in high rates of false-positive crack indications. Accordingly, there is a need for improved methods and systems for automatically detecting cracks in mobile devices.
The following disclosure describes systems and methods for automated visual inspection and evaluation of electronic devices. In particular, at least some embodiments of the present technology enable automatic detection of screen covers (alternatively known as screen protectors) on electronic devices. Screen covers have been discovered to produce telling artifacts in digital images. These artifacts include, for example, an abundance of lines that are aligned either horizontally (i.e., parallel to the long edge of the device screen) or vertically (i.e., parallel to the short edge of the device screen), an abundance of lines in the corner regions of the device, and anomalies associated with the presence of bubbles. These artifacts can be exploited to automatically analyze an image of a front side of an electronic device to detect the presence of a screen cover. This can be useful because screen covers tend to interfere with other types of automated device evaluation. For example, edges of screen covers have been discovered to be a source of false-positive crack indications in conventional processes for automated evaluation of electronic devices.
In one embodiment, line segments in an image of an electronic device are automatically identified using machine vision. Next, the angles of the identified line segments can be calculated, including determining the amount of line segments aligned within a predetermined range of a vertical orientation (e.g., within 5 degrees of vertical, within 3 degrees of vertical, etc.) and the amount of line segments aligned within a predetermined range of a horizontal orientation (e.g., within 5 degrees of horizontal, within 3 degrees of horizontal, etc.). If the amount of identified vertical line segments, the amount of identified horizontal line segments, or a combination of these amounts exceeds a predetermined threshold, then the presence of a screen cover is indicated. In addition or alternatively, the amount of line segments located within corner portions of the image is determined, and, if this amount exceeds a predetermined threshold (e.g., over 50% of the identified lines are located in the corner regions), then the presence of a screen cover is indicated or confirmed. Furthermore, the amount of image segments including bright spots associated with the presence of bubbles can be determined, and, if this amount exceeds a predetermined threshold, then the presence of a screen cover is indicated or confirmed.
Certain details are set forth in the following description and in
The accompanying Figures depict embodiments of the present technology and are not intended to be limiting of the scope of the present technology. The sizes of various depicted elements are not necessarily drawn to scale, and these various elements may be arbitrarily enlarged to improve legibility. Component details may be abstracted in the Figures to exclude details such as the position of components and certain precise connections between such components when such details are unnecessary for a complete understanding of how to make and use the invention.
In the Figures, identical reference numbers may identify identical, or at least generally similar, elements. To facilitate the discussion of any particular element, the most significant digit or digits of any reference number may refer to the Figure in which that element is first introduced. For example, element 101 is first introduced and discussed with reference to
Detection of Screen Covers on Electronic Device Screens
The imaging device 101 includes a processing component 111, a memory 213, input and output components 115 and 117, and a power component 125. The imaging device 101 further includes an image sensor 127, associated optics 129, and an illumination source 131. A communication component 119 of the imaging device 101 includes a wired connection 123 and a wireless transceiver 121. The computing device 105 can include several components similar to components of the imaging device 101. For example, the computing device 105 can include a processing component 133, memory 135 (which can store an operating system 137, applications 139, and data 141), along with input 143 and output 145 components and a power component 153. A communication component 147 of the computing device 105 includes a wired connection 151 and a wireless transceiver 147. These features of the imaging device 101 and the computing device 105 are described in more detail below in the context of a routine for detecting screen covers in accordance with an embodiment of the present technology.
In some embodiments, the routine first performs a crack detection routine before proceeding to detecting the presence or absence of a screen cover. If there are no cracks found during the crack detection routine, then the screen cover detection process can be bypassed or omitted. If there are cracks found during the crack detection subroutine, then the routine can proceed to detect the presence of a screen cover. As described in more detail below, certain cracks identified during the crack detection process may be attributable to the screen cover rather than genuine cracks. The routine can also first perform a brightness check to determine the average brightness of non-cracked regions of the screen. This brightness level can be compared to the average brightness for that particular model of electronic device. If the brightness level is higher than the average for that model of electronic device by some threshold amount (e.g., at least 10% brighter), then a screen cover is more likely to be present. Accordingly, some or all of the thresholds discussed in more detail below can be adjusted (e.g., loqw in view of the increased likelihood of a screen cover in these circumstances. In some embodiments, the routine can prompt the user to indicate whether a screen cover is present. If the user indicates that a screen cover is present (e.g., input via a touch screen interface, etc.), then some or all of the thresholds discussed in more detail below can be adjusted (e.g., lowered) in view of the increased likelihood of a screen cover in these circumstances.
Prior to proceeding with block 203 to detect a screen cover, the routine 200 can first analyze the image for possible glints that are indicative of true cracks. If such glints are found, then the screen cover detection process can be bypassed and the electronic device 103 can be graded accordingly. For example, the image can be analyzed by counting up all pixels above some threshold value (e.g., above 140 brightness units in a 0-255 range, greater than 150, 160, 170, etc.). If the number of high-brightness pixels is above some threshold number (e.g., greater than 20, 40, 60, 80, etc.), then a glint is identified. Such a high-brightness glint is likely due to an actual crack in the screen of the electronic device 103 reflecting light into the camera, and accordingly the screen cover detection process can be bypassed. Alternatively, the routine 200 can continue to block 203 without first performing this check for glints.
In block 203, the routine 200 applies a line detector to the non-screen periphery of the electronic device image (e.g., a Canny edge detector and/or other suitable image processing algorithms configured to detect line segments). The line detector can be applied to the screen as well as non-screen portions of the image. The output of this line segment detector may indicate cracks in the device screen as well as certain other features that may appear similar to as cracks. For example, these other features can include the perimeter of a screen cover, smudges, fingerprints, reflections, light scratches, etc.
In block 205, the routine 200 calculates the amount of identified line segments that are horizontal. The image of the electronic device can be rotated as needed until the device is square with respect to perpendicular axes (e.g., a horizontal axis that runs parallel to the long edge of the electronic device and a vertical axis that runs parallel to the short edge of the electronic device when the electronic device is positioned with its screen facing the imaging device). For each of the identified line segments from block 203, the routine 200 can assign an orientation vector corresponding to the general direction along which the line segment (or portion of the line segment) is aligned. For example, a given line segment may be oriented at 10 degrees with respect to the horizontal axis. If the orientation of the line segment is within a predetermined angular range of the horizontal axis, then the routine 200 identifies the line segment as “horizontal.” The predetermined angular range can vary in different embodiments. For example line segments can be considered horizontal if they are within 10 degrees of the horizontal axis, within 5 degrees, within 4 degrees, within 2 degrees, within 1 degrees, or less. The routine 200 then calculates the amount of identified line segments that are horizontal. In at least some embodiments, the routine 200 counts the number of pixels that fall within line segments that have been identified as horizontal. This pixel count can then be divided by the total number of pixels that fall within any of the identified line segments, resulting in a ratio of horizontal line segments to total line segments for the electronic device screen.
In block 207, the routine calculates the amount of identified line segments that are vertical. This process can be generally similar to the process followed in block 205 for calculating the amount of identified line segments that are horizontal. For example, for each line segment identified in block 203, the routine can identify the line segment as “vertical” if the orientation of the line segment is within a predetermined angular range of the vertical axis. As noted above, this predetermined range can vary, such as within 10 degrees of the vertical axis, within 5 degrees, within 4 degrees, within 2 degrees, within 1 degrees, or less. The routine 200 then calculates the amount of identified line segments that are vertical. In at least some embodiments, the routine 200 counts the number of pixels that fall within line segments that have been identified as vertical. This pixel count may then be divided by the total number of pixels that fall within any of the identified line segments, resulting in a ratio of vertical line segments to total line segments for the electronic device screen. In some embodiments, the routine counts as vertical or horizontal only those lines that exceed a predetermined threshold distance, e.g., at least 35 pixels, at least a number of pixels corresponding to approximately ¼″ of the screen, or other suitable threshold distance.
In decision block 209, the routine 200 determines whether the amount of vertical and/or horizontal line segments are above a predetermined threshold. For example, the routine 200 can assess whether the identified line segment are “mostly” horizontal or “mostly” vertical by evaluating whether the ratio of horizontal line segments to total line segments or the ratio of vertical line segments to total line segments exceeds the predetermined threshold. The predetermined threshold can vary in different embodiments, for example if the horizontal ratio or the vertical ratio exceeds 0.25, 0.5, 0.75, or more, the routine 200 determines that the identified line segments are primarily horizontal or primarily vertical, as the case may be. In this case, the routine 200 proceeds to block 211 and indicates the presence of a screen cover. This indication can be provided as input to another process, for example evaluating the electronic device for possible purchase. This indication can be conveyed to a user, for example via a display screen coupled to the computing device 105. For example, the user can be asked to remove the screen cover and re-initiate the process. As noted above, the threshold value for the horizontal ratio or the vertical ratio can be lowered in instances in which the electronic device had an unusually high brightness value in non-cracked regions (indicating an increased likelihood of a screen cover) or if a user indicated that screen cover is present.
If, in block 209, the routine 200 determines that the amount of vertical and/or horizontal line segments is not above the predetermined threshold (i.e., that the identified line segments are not primarily horizontal or primarily vertical), then the routine 200 proceeds to block 213 and calculates the amount of identified line segments in corner regions. Corner regions of the electronic device can be defined as those regions falling within a predetermined distance of both a top edge and a side edge or a bottom edge. In other embodiments, the corner regions can be defined as 4 quarter-circular regions, each with a center positioned corresponding to the physical corners of the electronic device. The space encompassed by the corner regions can vary in different embodiments. In one embodiment, each corner region is defined by the area that is within 5 cm of a horizontal edge of the electronic device and within 5 cm of a vertical edge of the electronic device. In other embodiments, these distances can vary, for example within 10 cm, within 4 cm, within 3 cm, or less.
For each of the identified line segments from block 203, the routine 200 can determine whether the line segment (or any portion of the line segment) falls within one of the designated corner regions. In one embodiment, the routine 200 counts the number of pixels that fall within line segments that have been assessed as falling within the corner regions. In some embodiments, this pixel count is divided by the total number of pixels that fall within any of the identified line segments, resulting in a ratio of corner line segments to total line segments for the electronic device screen.
In decision block 215, the routine determines whether the corner line segments exceeds a predetermined threshold. For example, the routine 200 can assess whether the identified line segments are “mostly” corner line segments by evaluating whether the ratio of corner line segments to total line segments exceeds the predetermined threshold. The predetermined threshold can vary in different embodiments, for example if the corner ratio exceeds 0.25, 0.5, 0.75, or more, the routine 200 determines that the identified line segments are primarily corner line segments. In this case, the routine 200 proceeds to block 211 and indicates the presence of a screen cover. If the routine 200 determines that the identified line segments are not primarily corner line segments (i.e., the ratio of corner line segments does not exceeds the predetermined threshold), then the routine 200 proceeds to block 217. As noted above, the threshold value for the corner ratio can be lowered in instances in which the electronic device had an unusually high brightness value in non-cracked regions (indicating an increased likelihood of a screen cover) or if a user indicated that screen cover is present.
In block 217, the routine 200 identifies any bubbles in the image. Bubbles in the image can be indicative of a screen cover even if the identified horizontal, vertical, and corner line segments did not exceed the thresholds indicated in decision blocks 209 and 215. Any suitable technique can be used to identify bubbles in the image. In one example, identifying bubbles proceeds by evaluating slices or other segments of the image separately from one another, with the slices divided along lines that run parallel to the short axis of the electronic device. In some embodiments, each slice can be approximately 10 pixels wide, or the total number of slices can be approximately 80, though these numbers can vary depending on the resolution of the image, the size of the electronic device, and other factors. If a given slice contains too few pixels (e.g., the slice corresponds to a region of the electronic device in which the majority of the slice is masked from analysis, such as a slice that would overlap the home button), then the slice is excluded from analysis. Next, for each slice, the routine can determine whether the number of high-brightness pixels exceeds a predetermined threshold. “High-brightness pixels” can be, for example, any pixels exceeding a predetermined brightness threshold, for example over 170 brightness units when the entire image has been normalized to an average brightness of 140 brightness units. In one example, if there are more than 15 high-brightness pixels in a given slice, then the bubble detection process can terminate, as this indicates a likely actual crack. If there are not more than 15 high-brightness pixels (i.e., less than the predetermined threshold number of high-brightness pixels) in any of the slices, then the bubble detection routine proceeds.
In some embodiments, the routine looks for bubbles or indicators of bubbles inside the screen region of the device first, for example excluding top, bottom, and side regions of the device external to the screen region. If bubbles are not found in the screen region, then the routine can look for bubbles or indicators of bubbles in top, bottom, and/or side regions of the device outside of the screen region. As noted above, a crack detection routine can be performed before the screen cover detection routine begins. If the number of identified cracks exceeds a predetermined threshold (e.g., more than 75 cracks identified), then the routine can bypass the bubble detection steps. This can mitigate the risk that a badly cracked phone would be improperly classified as having bubbles due to the effect of multiple cracks blurring into white regions when the image is blurred. In some embodiments, the bubble detection routine is only performed on devices of a particular predetermined size, for example excluding tablets or other devices having screens larger than some predetermined threshold (e.g., greater than 5″ screen, greater than 6″, greater than 7″, etc.). In other embodiments, the bubble detection routine can be applied to devices of all sizes.
Next, the bubble detection routine can blur each slice and calculate the average brightness and the standard deviation of brightness for each slice. Blurring the image can prevent the bubble detector from inappropriately labeling thin cracks as bubbles. For each blurred slice, the routine then can compute the ratio of disproportionally bright pixels to total pixels in that slice. Here, “disproportionally bright pixels” can be defined as any pixels that exceed the average brightness of the blurred slice by a predetermined amount, for example more than 5% above the average brightness of the blurred slice, more than 30% above the average brightness of the blurred slice, etc. The ratio of such disproportionally bright pixels to the total pixels in a given blurred slice is calculated. For each individual slice, a bubble is indicated if (1) the ratio of disproportionally bright pixels to total pixels in the blurred slice exceeds some threshold (e.g., greater than 2), and (2) if the standard deviation falls within a predetermined range (e.g., more than 4 and less than 40). This first criteria indicates that there is a bubble-like brightness in the slice and the second criteria excludes those slices in which artifacts may be skewing the results, for example the glass is too smooth indicating an anomalous image or there are genuine cracks or a plurality of slits that skew the result. In some embodiments, only one or the other of these two criteria are used to determine if a bubble is indicated. For example, if the ratio of disproportionally bright pixels to total pixels in the blurred slice exceeds some threshold, then a bubble is indicated in the slice. Separately, if the standard deviation falls within a predetermined range (e.g., more than 4 and less than 40), then a bubble is indicated in the slice.
In decision block 219, the routine determines whether the identified bubbles exceed a predetermined threshold. For example, the routine 200 can assess whether the number of slices with bubbles that were identified, if any, in block 217 exceeds a predetermined threshold (e.g., greater than 3 slices). If so, the routine 200 can proceed to block 211 to indicate the presence of a screen cover. If the routine 200 determines that the number of bubbles identified in block 217 falls below a predetermined threshold, then the routine 200 ends.
If the routine 200 proceeds with evaluating an electronic device screen and finds that the vertical and/or horizontal line segments do not exceed the predetermined threshold, that the corner line segments do not exceed the predetermined threshold, and that there are no identified bubbles, then either there is no screen cover present, or if there is a screen cover present, it is unlikely to be contributing a large number of false positive cracks identified by the line segment detection algorithm. If there is no screen cover present, then a device evaluation process can continue with evaluating the condition of the device screen. Similarly, if there is a screen cover present but it has produced few or no false cracks, then a device evaluation process can continue with evaluating the condition of the device screen without artifacts attributable to a screen cover skewing the evaluation.
Image 315 is an image of a second electronic screen 317 device with a screen cover. The screen 317 includes a plurality of cracks or crack-like artifacts 319 (e.g., a line resulting from the outer edge of a screen cover). Image 321 shows the output of the edge detector algorithm applied to the first image 315 (as described above with respect to block 203), in which line segments 319 have been identified. Image 323 shows the identified line segments 325 that are confined to the corner regions of the electronic device (as described above with respect to block 213). In this case, the corner line segments 325 exceed the predetermined threshold (as described above with respect to block 213), so the presence of a screen cover is indicated.
In at least some embodiments, the routine further assesses a condition of the electronic device after determining the presence or absence of a screen cover, such as to evaluate lines detected in the image other than lines associated with a screen cover. For example, to determine whether the screen is cracked, the routine can determine an amount of the identified line segments that are not determined to be horizontal, vertical, or corner line segments. These line segments are more likely to correspond to actual cracks in the screen and accordingly can be counted or otherwise used to evaluate the condition of the screen. In some embodiments, more weight is given to such line segments that are farther from the perimeter of the device (i.e., nearer to a center of the screen) than to those line segments that are closer to the perimeter of the device (i.e., farther from the center of the device screen). In another embodiment, determining whether the screen is cracked includes determining which line segments of the identified line segments are not horizontal, vertical, or corner line segments, and giving more weight to such line segments that are farther from being vertical or horizontal than to such line segments that are nearer to being vertical or horizontal.
Computing Environment
Referring again to
The electronic device 103 can be, for example, a smartphone, a tablet, a laptop, a handheld gaming device, a media player, or any such device that has a screen or other surface that may suffer cracks or similar defects. Although many embodiments of the present technology are described herein in the context of mobile phones, aspects of the present technology are not limited to mobile phones and generally apply to other consumer electronic devices. Such devices include, as non-limiting examples, all manner of mobile phones; smartphones; handheld devices; personal digital assistants (PDAs); MP3 or other digital music players; tablet, notebook, ultrabook and laptop computers; e-readers; all types of cameras; GPS devices; set-top boxes and other media players; VoIP phones; universal remote controls; wearable computers; and larger consumer electronic devices, such as desktop computers, TVs, projectors, DVRs, game consoles, etc.
The computing device 105 can be a desktop computer or another suitable device. The computing device 105 is configured to receive images of the electronic device 103 from the imaging device 101 and to automatically analyze the images to detect the presence of screen covers as well as cracks or other defects. In some embodiments, the computing device 105 is remote from the imaging device 101 and can be in communication via the communications link 109. In other embodiments, the computing device 105 is connected to the imaging device 101 via a hardwire connection, or in certain embodiments the imaging device 101 and the computing device 105 are integrated into the same machine. The computing device 105 is also in communication with the database 107 which can store data used in automatically analyzing the images of the electronic device 103. The database 107 may also store the results of the automatic analysis of the images, other data about the electronic device 103, etc.
In the illustrated embodiment, various devices including the imaging device 101 and the computing device 105 exchanges information with one another via the communication link 109. Although the communication link 109 can include a publicly available network (e.g., the Internet with a web interface), a private communication link (e.g., an intranet or other network) can also be used. Moreover, in various embodiments the imaging device 101 is connected to a host computer (not shown) that facilitates the exchange of information between the imaging device 101, the computing device 105, remote computers, mobile devices, etc.
In the illustrated embodiment, the imaging device 101 includes the processing component 111 that controls operation of the imaging device 101 in accordance with computer-readable instructions stored in memory 113. The processing component 111 may include any logic processing unit, such as one or more central processing units (CPUs), graphics processing units (GPUs), digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The processing component 111 may be a single processing unit or multiple processing units in an electronic device or distributed across multiple devices. Aspects of the present technology can be embodied in a special purpose computing device or data processor that is specifically programmed, configured, or constructed to perform one or more of the computer-executable instructions explained in detail herein. Aspects of the present technology can also be practiced in distributed computing environments in which functions or modules are performed by remote processing devices that are linked through a communications network, such as a local area network (LAN), wide area network (WAN), or the Internet. In a distributed computing environment, modules can be located in both local and remote memory storage devices.
The processing component 111 is connected to memory 113, which can include a combination of temporary and/or permanent storage, and both read-only memory (ROM) and writable memory (e.g., random access memory or RAM), writable non-volatile memory such as flash memory or other solid-state memory, hard drives, removable media, magnetically or optically readable discs, nanotechnology memory, biological memory, and so forth. As used herein, memory does not include a transitory propagating signal per se. The memory 213 includes data storage that contains programs, software, and information, such as an operating system and data. Imaging device 101 operating system and data can include software and databases configured to control imaging device 101 components, process images, communicate and exchange data and information with remote computers and other devices, etc.
The imaging device 101 further includes input components 115 that can receive input from user interactions and provide input to the processing component 111, typically mediated by a hardware controller that interprets the raw signals received from the input device and communicates the information to the processing component 111 using a known communication protocol. Examples of an input component 115 include touchpad, a keyboard (with physical or virtual keys), a pointing device (such as a mouse, dial, or eye tracking device), a touchscreen that detects contact events when it is touched by a user, a microphone that receives audio input, etc. The imaging device 101 can also include various other input components 115 such as GPS or other location determination sensors, motion sensors, wearable input devices with accelerometers (e.g. wearable glove-type input devices), biometric sensors (e.g., fingerprint sensors), light sensors, card readers (e.g., magnetic stripe readers or memory card readers) or the like.
The processing component 111 is also connected to one or more various output components 117, e.g., directly or via a hardware controller. The output devices can include a display on which text and graphics are displayed. The display can be, for example, an LCD, LED, or OLED display screen, an e-ink display, a projected display (such as a heads-up display device), and/or a display integrated with a touchscreen that serves as an input device as well as an output device that provides graphical and textual visual feedback to a user. The output components 117 can also include a speaker for playing audio signals, haptic feedback devices for tactile output such as vibration, etc. In some implementations, a speaker and microphone are implemented by a combined audio input-output device.
In the illustrated embodiment, the imaging device 101 further includes one or more communication components 119. The communication components can include, for example, a wireless transceiver 121 (e.g., one or more of a Wi-Fi transceiver; Bluetooth transceiver; near-field communication (NFC) device; wireless modem or cellular radio utilizing GSM, CDMA, 3G and/or 4G technologies; etc.) and/or a wired network connection 123 (e.g., one or more of an Ethernet port, cable modem, FireWire cable, Lightning connector, universal serial bus (USB) port, etc.). The communication components 119 are suitable for communication between the imaging device 101 and other local and/or remote devices, e.g., the computing device 105, directly via a wired or wireless peer-to-peer connection and/or indirectly via the communication link 109 (which can include the Internet, a public or private intranet, a local or extended Wi-Fi network, cell towers, the plain old telephone system (POTS), etc.). For example, the wireless transceiver 121 of the imaging device 101 can connect to a wireless transceiver 149 of the computing device via the wireless connection. The imaging device 101 further includes power 125, which can include battery power and/or facility power for operation of the various electrical components associated with the imaging device 101.
The imaging device 101 further includes the image sensor 127, optics 129, and illumination source 131. The image sensor 127 can be, for example, a CCD sensor, a CMOS sensor, or any other type of image sensor or array of sensors. The image sensor 127 can be aligned with optics 129, for example one or more lenses, filters, or other optical elements, configured to orient and modulate incoming light before it reaches the image sensor 127. The illumination source 131 can be configured to direct illumination towards the field of view of the imaging device 101, and can be any type of light source, for example LEDs, fluorescent bulbs, etc. In some embodiments, the illumination source 131 includes multiple different types of light sources which can be individually activated, for example infrared, ultraviolet, broadband, etc.
The computing device 105 includes several components similar to those in the imaging device 101. In the illustrated embodiment, the computing device 105 includes a processing component 133 that controls operation of the computing device 105 in accordance with computer-readable instructions stored in memory 135. The processing component 133 may be any logic processing unit, such as one or more central processing units (CPUs), graphics processing units (GPUs), digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The processing component 133 may be a single processing unit or multiple processing units in an electronic device or distributed across multiple devices. The processing component 133 is connected to memory 135, which includes data storage that contains programs, software, and information, such as an operating system 137, application programs 139, and data 141. The operating system 137 can include, for example, Windows®, Linux®, Android™, iOS®, and/or an embedded real-time operating system. The application programs 139 and data 141 can include software and databases configured to control computing device 105 components, process and evaluate images received from the imaging device 101, communicate and exchange data and information with remote computers and other devices, etc.
The computing device 105 can include input components 143, such as a keyboard (with physical or virtual keys), a pointing device (such as a mouse, joystick, dial, or eye tracking device), a touchscreen, a microphone, and a camera for still photograph and/or video capture. The computing device 105 can also include various other input components 143 such as GPS or other location determination sensors, motion sensors, wearable input devices with accelerometers (e.g. wearable glove-type input devices), biometric sensors (e.g., fingerprint sensors), light sensors, card readers (e.g., magnetic stripe readers or memory card readers) and the like.
The processing component 133 can also be connected to one or more various output components 145, e.g., directly or via a hardware controller. The output devices can include a display such as an LCD, LED, or OLED display screen (such as a desktop computer screen, handheld device screen, or television screen), an e-ink display, a projected display (such as a heads-up display device), and/or a display integrated with a touchscreen that serves as an input device as well as an output device that provides graphical and textual visual feedback to the user. The output devices can also include a speaker for playing audio signals, haptic feedback devices for tactile output such as vibration, etc.
In the illustrated embodiment, computing device 105 further includes one or more communication components 147. The communication components can include, for example, a wireless transceiver 149 (e.g., one or more of a Wi-Fi transceiver; Bluetooth transceiver; near-field communication (NFC) device; wireless modem or cellular radio utilizing GSM, CDMA, 3G and/or 4G technologies; etc.) and/or a wired network connector port 251 (e.g., one or more of an Ethernet port, cable modem, FireWire cable, Lightning connector, universal serial bus (USB) port, etc.). The communication components 147 are suitable for communication between the computing device 105 and other local and/or remote computing devices, e.g., the imaging device 101 via a wired or wireless peer-to-peer connection and/or indirectly via the communication link 109. For example, the wireless transceiver 149 of the computing device 105 can connect to the wireless transceiver 121 of imaging device 101, and/or the wired connector port 151 of the computing device 105 can connect to the wired connector port 123 of the imaging device 101. The computing device 105 further includes power 153, which can include battery power and/or facility power for operation of the various electrical components associated with the computing device 105.
Unless described otherwise, the construction and operation of the various components shown in
Kiosk Environment
In some embodiments, the routines described herein can be carried out using a kiosk that includes an imaging device (e.g., the imaging device 101) therein. In some embodiments, the kiosk can perform some or all of the functions performed by the computing device 105 described above, for example processing and evaluating images received from the imaging device 101. The kiosk can include, for example, a processing component and memory storing instructions that, when executed by the processing component, perform operations such as the routine 200 described above.
In the illustrated embodiment, the kiosk 400 is a floor-standing self-service kiosk configured for use by a user 401 (e.g., a consumer, customer, etc.) to recycle, sell, and/or perform other operations with a mobile phone or other consumer electronic device. In other embodiments, the kiosk 400 can be configured for use on a countertop or a similar raised surface. Although the kiosk 400 is configured for use by consumers, in various embodiments the kiosk 400 and/or various portions thereof can also be used by other operators, such as a retail clerk or kiosk assistant to facilitate the selling or other processing of mobile phones and other electronic devices.
In the illustrated embodiment, the kiosk 400 includes a housing 402 that is approximately the size of a conventional vending machine. The housing 402 can be of conventional manufacture from, for example, sheet metal, plastic panels, etc. A plurality of user interface devices are provided on a front portion of the housing 402 for providing instructions and other information to users, and/or for receiving user inputs and other information from users. For example, the kiosk 400 can include a display screen 404 (e.g., a liquid crystal display (“LCD”) or light emitting diode (“LED”) display screen, a projected display (such as a heads-up display or a head-mounted device), and so on) for providing information, prompts, etc., to users. The display screen 404 can include a touch screen for receiving user input and responses to displayed prompts. In addition or alternatively, the kiosk 400 can include a separate keyboard or keypad for this purpose. The kiosk 400 can also include an ID reader or scanner 412 (e.g., a driver's license scanner), a fingerprint reader 414, and one or more cameras 416 (e.g., digital still and/or video cameras, identified individually as cameras 416a-c). The kiosk 400 can additionally include output devices such as a label printer having an outlet 410, and a cash dispenser having an outlet 418. Although not identified in
A sidewall portion of the housing 402 can include a number of conveniences to help users recycle or otherwise process their mobile phones. For example, in the illustrated embodiment the kiosk 400 includes an accessory bin 428 that is configured to receive mobile device accessories that the user wishes to recycle or otherwise dispose of. Additionally, the kiosk 400 can provide a free charging station 426 with a plurality of electrical connectors 424 for charging a wide variety of mobile phones and other consumer electronic devices.
In the illustrated embodiment, the inspection plate 544 is configured to translate back and forth (on, e.g., parallel mounting tracks) to move an electronic device, such as the mobile phone 550, between a first position directly behind the access door 406 and a second position between an upper chamber 530 and an opposing lower chamber 532. Moreover, in this embodiment the inspection plate 544 is transparent, or at least partially transparent (e.g., formed of glass, Plexiglas, etc.) to enable the mobile phone 550 to be photographed and/or otherwise optically evaluated from all, or at least most viewing angles (e.g., top, bottom, sides, etc.) using, e.g., one or more cameras, mirrors, etc. mounted to or otherwise associated with the upper and lower chambers 530 and 532. When the mobile phone 550 is in the second position, the upper chamber 530 can translate downwardly to generally enclose the mobile phone 550 between the upper chamber 530 and the lower chamber 532. The upper chamber 530 is operably coupled to a gate 538 that moves up and down in unison with the upper chamber 530.
In some embodiments, the kiosk 400 includes the imaging device 101 disposed within the upper hood 530. The imaging device 101 can be used as described above to facilitate visual inspection of the mobile phone 550 in order to detect the presence of a screen cover over the screen, and depending on that determination, proceeding to evaluate the screen for cracks. The upper chamber 530 and/or the lower chamber 532 can also include one or more magnification tools, scanners (e.g., bar code scanners, infrared scanners, etc.) or other imaging components (not shown) and an arrangement of mirrors (also not shown) to view, photograph and/or otherwise visually evaluate the mobile phone 550 from multiple perspectives. In some embodiments, one or more of the cameras and/or other imaging components discussed above can be movable to facilitate device evaluation. For example, as noted above with respect to
The kiosk 400 can be used in a number of different ways to efficiently facilitate the recycling, selling and/or other processing of mobile phones and other consumer electronic devices. Referring to
Referring next to
After the visual and electronic analysis of the mobile phone 550, the user is presented with a phone purchase price via the display screen 404. If the user declines the price (via, e.g., the touch screen), a retraction mechanism (not shown) automatically disconnects the connector 542 from the mobile phone 550, the door 406 opens, and the user can reach in and retrieve the mobile phone 550. If the user accepts the price, the door 406 remains closed and the user may be prompted to place his or her identification (e.g., a driver's license) in the ID scanner 412 and provide a thumbprint via the fingerprint reader 414. As a fraud prevention measure, the kiosk 400 can be configured to transmit an image of the driver's license to a remote computer screen, and an operator at the remote computer can visually compare the picture (and/or other information) on the driver's license to an image of the person standing in front of the kiosk 400 as viewed by one or more of the cameras 416a-c (
As those of ordinary skill in the art will appreciate, the foregoing routines are but some examples of ways in which the kiosk 400 can be used to recycle or otherwise process consumer electronic devices such as mobile phones. Although the foregoing example is described in the context of mobile phones, it should be understood that the kiosk 400 and various embodiments thereof can also be used in a similar manner for recycling virtually any consumer electronic device, such as MP3 players, tablet computers, PDAs, and other portable devices, as well as other relatively non-portable electronic devices such as desktop computers, printers, devices for implementing games, entertainment or other digital media on CDs, DVDs, Blu-ray, etc. Moreover, although the foregoing example is described in the context of use by a consumer, the kiosk 400 in various embodiments thereof can similarly be used by others, such as a store clerk, to assist consumers in recycling, selling, exchanging, etc. their electronic devices.
The disclosed technology also includes the disclosures of U.S. patent application Ser. No. 14/498,763, titled “METHODS AND SYSTEMS FOR PRICING AND PERFORMING OTHER PROCESSES ASSOCIATED WITH RECYCLING MOBILE PHONES AND OTHER ELECTRONIC DEVICES,” filed by the applicant on Sep. 26, 2014; U.S. patent application Ser. No. 14/500,739, titled “MAINTAINING SETS OF CABLE COMPONENTS USED FOR WIRED ANALYSIS, CHARGING, OR OTHER INTERACTION WITH PORTABLE ELECTRONIC DEVICES,” filed by the applicant on Sep. 29, 2014; U.S. patent application Ser. No. 14/873,158, titled “WIRELESS-ENABLED KIOSK FOR RECYCLING CONSUMER DEVICES,” filed by the applicant on Oct. 1, 2015; U.S. patent application Ser. No. 14/873,145, titled “APPLICATION FOR DEVICE EVALUATION AND OTHER PROCESSES ASSOCIATED WITH DEVICE RECYCLING,” filed by the applicant on Oct. 1, 2015; U.S. patent application Ser. No. 14/506,449, titled “SYSTEM FOR ELECTRICALLY TESTING MOBILE DEVICES AT A CONSUMER-OPERATED KIOSK, AND ASSOCIATED DEVICES AND METHODS,” filed by the applicant on Oct. 3, 2014; U.S. patent application Ser. No. 14/925,357, titled “SYSTEMS AND METHODS FOR RECYCLING CONSUMER ELECTRONIC DEVICES,” filed by the applicant on Oct. 28, 2015; U.S. patent application Ser. No. 14/925,375, titled “METHODS AND SYSTEMS FOR FACILITATING PROCESSES ASSOCIATED WITH INSURANCE SERVICES AND/OR OTHER SERVICES FOR ELECTRONIC DEVICES,” filed by the applicant on Oct. 28, 2015; U.S. patent application Ser. No. 14/964,963, titled “METHODS AND SYSTEMS FOR PROVIDING INFORMATION REGARDING COUPONS/PROMOTIONS AT KIOSKS FOR RECYCLING MOBILE PHONES AND OTHER ELECTRONIC DEVICES,” filed by the applicant on Dec. 10, 2015; U.S. patent application Ser. No. 14/568,051, titled “METHODS AND SYSTEMS FOR IDENTIFYING MOBILE PHONES AND OTHER ELECTRONIC DEVICES,” filed by the applicant on Dec. 11, 2014; U.S. patent application Ser. No. 14/966,346, titled “SYSTEMS AND METHODS FOR RECYCLING CONSUMER ELECTRONIC DEVICES,” filed by the applicant on Dec. 11, 2015; U.S. patent application Ser. No. 14/598,469, titled “METHODS AND SYSTEMS FOR DYNAMIC PRICING AND PERFORMING OTHER PROCESSES ASSOCIATED WITH RECYCLING MOBILE PHONES AND OTHER ELECTRONIC DEVICES,” filed by the applicant on Jan. 16, 2015; U.S. patent application Ser. No. 14/660,768, titled “SYSTEMS AND METHODS FOR INSPECTING MOBILE DEVICES AND OTHER CONSUMER ELECTRONIC DEVICES WITH A LASER,” filed by the applicant on Mar. 17, 2015; U.S. patent application Ser. No. 14/663,331, titled “DEVICE RECYCLING SYSTEMS WITH FACIAL RECOGNITION,” filed by the applicant on Mar. 19, 2015; U.S. provisional application No. 62/169,072, titled “METHODS AND SYSTEMS FOR VISUALLY EVALUATING ELECTRONIC DEVICES,” filed by the applicant on Jun. 1, 2015; U.S. provisional application No. 62/202,330, titled “METHODS AND SYSTEMS FOR INSPECTING MOBILE DEVICES AND OTHER CONSUMER ELECTRONIC DEVICES WITH ROBOTIC ACTUATION,” filed by the applicant on Aug. 7, 2015; U.S. patent application Ser. No. 15/057,707, titled “METHODS AND SYSTEMS FOR RECORDING INTERACTIONS WITH A SYSTEM FOR PURCHASING MOBILE PHONES AND OTHER ELECTRONIC DEVICES,” filed by the applicant on Mar. 1, 2016; U.S. patent application Ser. No. 14/873,158, titled “WIRELESS-ENABLED KIOSK FOR RECYCLING CONSUMER DEVICES,” filed by the applicant on Oct. 1, 2015; U.S. patent application Ser. No. 14/873,145, titled “APPLICATION FOR DEVICE EVALUATION AND OTHER PROCESSES ASSOCIATED WITH DEVICE RECYCLING,” filed by the applicant on Oct. 1, 2015; U.S. patent application Ser. No. 14/925,357, titled “SYSTEMS AND METHODS FOR RECYCLING CONSUMER ELECTRONIC DEVICES,” filed by the applicant on Oct. 28, 2015; U.S. patent application Ser. No. 14/925,375, titled “METHODS AND SYSTEMS FOR FACILITATING PROCESSES ASSOCIATED WITH INSURANCE SERVICES AND/OR OTHER SERVICES FOR ELECTRONIC DEVICES,” filed by the applicant on Oct. 28, 2015; U.S. patent application Ser. No. 14/934,134, titled “METHODS AND SYSTEMS FOR EVALUATING AND RECYCLING ELECTRONIC DEVICES,” and U.S. patent application Ser. No. 14/967,183, titled “SYSTEMS AND METHODS FOR RECYCLING CONSUMER ELECTRONIC DEVICES,” filed Dec. 11, 2015, each of which is incorporated herein by reference in its entirety. All of the patents and patent applications listed above are commonly owned by the applicant of the present application, and they along with any other patents or patent applications identified herein are incorporated herein by reference in their entireties.
While the Internet is shown, a private network, such as an intranet may likewise be used herein. The network may have a client-server architecture, in which a computer is dedicated to serving other client computers, or it may have other architectures such as peer-to-peer, in which one or more computers serve simultaneously as servers and clients. A database or databases, coupled to the server computer(s), stores much of the web pages and content exchanged between the user computers. The server computer(s), including the database(s), may employ security measures to inhibit malicious attacks on the system and preserve the integrity of the messages and data stored therein (e.g., firewall systems, message encryption and/or authentication (e.g., using transport layer security (TLS) or secure socket layers (SSL)), password protection schemes, encryption of stored data (e.g., using trusted computing hardware), and the like).
One skilled in the relevant art will appreciate that the concepts of the invention can be used in various environments other than location based or the Internet. In general, a display description may be in HTML, XML or WAP format, email format or any other format suitable for displaying information (including character/code-based formats, algorithm-based formats (e.g., vector generated), and bitmapped formats). Also, various communication channels, such as local area networks, wide area networks, or point-to-point dial-up connections, may be used instead of the Internet. The system may be conducted within a single computer environment, rather than a client/server environment. Also, the user computers may comprise any combination of hardware or software that interacts with the server computer, such as television-based systems and various other consumer products through which commercial or noncommercial transactions can be conducted. The various aspects of the invention described herein can be implemented in or for any e-mail environment.
Although not required, aspects of the invention are described in the general context of computer-executable instructions, such as routines executed by a general-purpose data processing device, e.g., a server computer, wireless device or personal computer. Those skilled in the relevant art will appreciate that aspects of the invention can be practiced with other communications, data processing, or computer system configurations, including Internet appliances, hand-held devices (including personal digital assistants (PDAs)), wearable computers, all manner of cellular or mobile phones (including Voice over IP (VoIP) phones), dumb terminals, media players, gaming devices, multi-processor systems, microprocessor-based or programmable consumer electronics, set-top boxes, network PCs, mini-computers, mainframe computers, and the like. Indeed, the terms “computer,” “server,” “host,” “host system,” and the like, are generally used interchangeably herein, and refer to any of the above devices and systems, as well as any data processor. Input devices may include a touchpad, keyboard and/or a pointing device such as a mouse. Other input devices are possible such as a microphone, joystick, pen, game pad, scanner, digital camera, video camera, and the like. The data storage devices may include any type of computer-readable media that can store data accessible by a computer, such as magnetic hard and floppy disk drives, optical disk drives, magnetic cassettes, tape drives, flash memory cards, digital video disks (DVDs), Bernoulli cartridges, RAMs, ROMs, smart cards, etc. Indeed, any medium for storing or transmitting computer-readable instructions and data may be employed, including a connection port to a network such as a local area network (LAN), wide area network (WAN) or the Internet.
Aspects of the invention can be embodied in a special purpose computer or data processor that is specifically programmed, configured, or constructed to perform one or more of the computer-executable instructions explained in detail herein. While aspects of the invention, such as certain functions, are described as being performed exclusively on a single device, the invention can also be practiced in distributed environments where functions or modules are shared among disparate processing devices, which are linked through a communications network, such as a Local Area Network (LAN), Wide Area Network (WAN), or the Internet. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
Aspects of the invention may be stored or distributed on tangible computer-readable media, including magnetically or optically readable computer discs, hard-wired or preprogrammed chips (e.g., EEPROM semiconductor chips), nanotechnology memory, biological memory, or other data storage media. The data storage devices may include any type of computer-readable media that can store data accessible by a computer, such as magnetic hard and floppy disk drives, optical disk drives, magnetic cassettes, tape drives, flash memory cards, DVDs, Bernoulli cartridges, RAM, ROMs, smart cards, etc. Indeed, any medium for storing or transmitting computer-readable instructions and data may be employed, including a connection port to a network such as a LAN, WAN, or the Internet. Alternatively, computer implemented instructions, data structures, screen displays, and other data under aspects of the invention may be distributed over the Internet or over other networks (including wireless networks), on a propagated signal on a propagation medium (e.g., an electromagnetic wave(s), a sound wave, etc.) over a period of time, or they may be provided on any analog or digital network (packet switched, circuit switched, or other scheme). The terms “memory” and “computer-readable storage medium” include any combination of temporary, persistent, and/or permanent storage, e.g., ROM, writable memory such as RAM, writable non-volatile memory such as flash memory, hard drives, solid state drives, removable media, and so forth, but do not include a propagating signal per se.
The above Detailed Description of examples and embodiments of the invention is not intended to be exhaustive or to limit the invention to the precise form disclosed above. While specific examples for the invention are described above for illustrative purposes, various equivalent modifications are possible within the scope of the invention, as those skilled in the relevant art will recognize. References throughout the foregoing description to features, advantages, or similar language do not imply that all of the features and advantages that may be realized with the present technology should be or are in any single embodiment of the invention. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present technology. Thus, discussion of the features and advantages, and similar language, throughout this specification may, but do not necessarily, refer to the same embodiment. Furthermore, the described features, advantages, and characteristics of the present technology may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that the present technology can be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the present technology.
Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the invention can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further implementations of the invention.
Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like, are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof, means any connection or coupling, either direct or indirect, between two or more elements; the coupling or connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.
The teachings of the invention provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various examples described above can be combined to provide further implementations of the invention. Some alternative implementations of the invention may include not only additional elements to those implementations noted above, but also may include fewer elements. Further any specific numbers noted herein are only examples—alternative implementations may employ differing values or ranges.
While the above description describes various embodiments of the invention and the best mode contemplated, regardless how detailed the above text, the invention can be practiced in many ways. Details of the system may vary considerably in its specific implementation, while still being encompassed by the present disclosure. As noted above, particular terminology used when describing certain features or aspects of the invention should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the invention with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the invention to the specific examples disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the invention encompasses not only the disclosed examples, but also all equivalent ways of practicing or implementing the invention under the claims.
From the foregoing, it will be appreciated that specific embodiments of the invention have been described herein for purposes of illustration, but that various modifications may be made without deviating from the spirit and scope of the various embodiments of the invention. Further, while various advantages associated with certain embodiments of the invention have been described above in the context of those embodiments, other embodiments may also exhibit such advantages, and not all embodiments need necessarily exhibit such advantages to fall within the scope of the invention. Accordingly, the invention is not limited, except as by the appended claims. Although certain aspects of the invention are presented below in certain claim forms, the applicant contemplates the various aspects of the invention in any number of claim forms. Accordingly, the applicant reserves the right to pursue additional claims after filing this application to pursue such additional claim forms, in either this application or in a continuing application.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3808439 | Renius | Apr 1974 | A |
| 4248334 | Hanley et al. | Feb 1981 | A |
| 4519522 | McElwee | May 1985 | A |
| 4715709 | Sekine et al. | Dec 1987 | A |
| 4821118 | Lafreniere | Apr 1989 | A |
| 4870357 | Young et al. | Sep 1989 | A |
| 4878736 | Hekker et al. | Nov 1989 | A |
| 4927051 | Falk et al. | May 1990 | A |
| 4951308 | Bishop et al. | Aug 1990 | A |
| 5027074 | Haferstat | Jun 1991 | A |
| 5077462 | Newell et al. | Dec 1991 | A |
| 5091773 | Fouche et al. | Feb 1992 | A |
| 5105149 | Tokura | Apr 1992 | A |
| 5216502 | Katz | Jun 1993 | A |
| 5280170 | Baldwin | Jan 1994 | A |
| 5339096 | Beaufort et al. | Aug 1994 | A |
| 5419438 | Squyres et al. | May 1995 | A |
| 5436554 | Decker | Jul 1995 | A |
| 5570920 | Crisman et al. | Nov 1996 | A |
| 5572444 | Lentz et al. | Nov 1996 | A |
| 5610710 | Canfield et al. | Mar 1997 | A |
| 5717780 | Mitsumune et al. | Feb 1998 | A |
| 5747784 | Walter et al. | May 1998 | A |
| 5775806 | Allred | Jul 1998 | A |
| 5839058 | Phillips et al. | Nov 1998 | A |
| 5920338 | Katz | Jul 1999 | A |
| 5949901 | Nichani et al. | Sep 1999 | A |
| 5965858 | Suzuki et al. | Oct 1999 | A |
| 5966654 | Croughwell et al. | Oct 1999 | A |
| 5987159 | Nichani | Nov 1999 | A |
| 5988431 | Roe | Nov 1999 | A |
| 6029851 | Jenkins et al. | Feb 2000 | A |
| 6041229 | Turner | Mar 2000 | A |
| 6181805 | Koike et al. | Jan 2001 | B1 |
| 6228008 | Pollington et al. | May 2001 | B1 |
| 6259827 | Nichani | Jul 2001 | B1 |
| 6264104 | Jenkins et al. | Jul 2001 | B1 |
| 6330354 | Companion et al. | Dec 2001 | B1 |
| 6330958 | Ruskin et al. | Dec 2001 | B1 |
| 6393095 | Robinson | May 2002 | B1 |
| 6462644 | Howell et al. | Oct 2002 | B1 |
| 6529837 | Kang | Mar 2003 | B1 |
| 6535637 | Wootton et al. | Mar 2003 | B1 |
| 6573886 | Lehtinen | Jun 2003 | B1 |
| 6587581 | Matsuyama et al. | Jul 2003 | B1 |
| 6595684 | Casagrande et al. | Jul 2003 | B1 |
| 6633377 | Weiss et al. | Oct 2003 | B1 |
| 6667800 | Larsson et al. | Dec 2003 | B1 |
| 6754637 | Stenz | Jun 2004 | B1 |
| 6758370 | Cooke et al. | Jul 2004 | B2 |
| 6798528 | Hartman | Sep 2004 | B1 |
| 6822422 | Sagawa | Nov 2004 | B2 |
| 6842596 | Morii et al. | Jan 2005 | B2 |
| 6854656 | Matsumori | Feb 2005 | B2 |
| 7069236 | Tsunenari | Jun 2006 | B1 |
| 7076449 | Tsunenari et al. | Jul 2006 | B2 |
| 7178720 | Strubbe et al. | Feb 2007 | B1 |
| 7234609 | DeLazzer et al. | Jun 2007 | B2 |
| 7251458 | O'Connell | Jul 2007 | B2 |
| 7268345 | Schultz | Sep 2007 | B2 |
| 7334729 | Brewington | Feb 2008 | B2 |
| 7520666 | Pevzner et al. | Apr 2009 | B2 |
| 7567344 | LeBlanc et al. | Jul 2009 | B2 |
| 7646193 | Suzuki et al. | Jan 2010 | B2 |
| 7649450 | Campion et al. | Jan 2010 | B2 |
| 7702108 | Amon et al. | Apr 2010 | B2 |
| 7735125 | Alvarez et al. | Jun 2010 | B1 |
| 7761331 | Low et al. | Jul 2010 | B2 |
| 7783379 | Beane et al. | Aug 2010 | B2 |
| 8010402 | Sharma et al. | Aug 2011 | B1 |
| 8019588 | Wohlberg et al. | Sep 2011 | B1 |
| 8025229 | Hammond et al. | Sep 2011 | B2 |
| 8031930 | Wang et al. | Oct 2011 | B2 |
| 8107243 | Guccione et al. | Jan 2012 | B2 |
| 8112325 | Foy et al. | Feb 2012 | B2 |
| 8195511 | Bowles et al. | Jun 2012 | B2 |
| 8254883 | Uchida | Aug 2012 | B2 |
| 8266008 | Siegel et al. | Sep 2012 | B1 |
| 8463646 | Bowles et al. | Jun 2013 | B2 |
| 8718717 | Vaknin et al. | May 2014 | B2 |
| 8743215 | Lee | Jun 2014 | B1 |
| 8824136 | Interian, III | Sep 2014 | B1 |
| 9043026 | Lien et al. | May 2015 | B2 |
| 9582101 | Chang | Feb 2017 | B2 |
| 9595238 | Won | Mar 2017 | B2 |
| 20010039531 | Aoki | Nov 2001 | A1 |
| 20020014577 | Ulrich et al. | Feb 2002 | A1 |
| 20020035515 | Moreno | Mar 2002 | A1 |
| 20020067184 | Smith et al. | Jun 2002 | A1 |
| 20020087413 | Mahaffy et al. | Jul 2002 | A1 |
| 20020129170 | Moore et al. | Sep 2002 | A1 |
| 20020157033 | Cox | Oct 2002 | A1 |
| 20020162966 | Yoder | Nov 2002 | A1 |
| 20020186878 | Hoon et al. | Dec 2002 | A1 |
| 20030006277 | Maskatiya et al. | Jan 2003 | A1 |
| 20030036866 | Nair et al. | Feb 2003 | A1 |
| 20030061150 | Kocher | Mar 2003 | A1 |
| 20030146898 | Kawasaki et al. | Aug 2003 | A1 |
| 20030170529 | Sagawa | Sep 2003 | A1 |
| 20030197782 | Ashe et al. | Oct 2003 | A1 |
| 20030204289 | Banerjee et al. | Oct 2003 | A1 |
| 20040012825 | Tesavis | Jan 2004 | A1 |
| 20040114153 | Andersen et al. | Jun 2004 | A1 |
| 20040141320 | Bock et al. | Jul 2004 | A1 |
| 20040150815 | Sones et al. | Aug 2004 | A1 |
| 20040156557 | Van Der Weij | Aug 2004 | A1 |
| 20040156667 | Berger et al. | Aug 2004 | A1 |
| 20040186744 | Lux | Sep 2004 | A1 |
| 20040205015 | DeLaCruz | Oct 2004 | A1 |
| 20040235513 | O'Connell | Nov 2004 | A1 |
| 20040242216 | Boutsikakis | Dec 2004 | A1 |
| 20040262521 | Devitt et al. | Dec 2004 | A1 |
| 20050128551 | Yang | Jun 2005 | A1 |
| 20050143149 | Becker et al. | Jun 2005 | A1 |
| 20050167620 | Cho et al. | Aug 2005 | A1 |
| 20050187657 | Hashimoto et al. | Aug 2005 | A1 |
| 20050216120 | Rosenberg et al. | Sep 2005 | A1 |
| 20050222690 | Wang et al. | Oct 2005 | A1 |
| 20050231595 | Wang et al. | Oct 2005 | A1 |
| 20050240958 | Nguyen et al. | Oct 2005 | A1 |
| 20060038114 | Cofer et al. | Feb 2006 | A9 |
| 20060167580 | Whittier | Jul 2006 | A1 |
| 20060184379 | Tan et al. | Aug 2006 | A1 |
| 20060195384 | Bauer et al. | Aug 2006 | A1 |
| 20060229108 | Cehelnik | Oct 2006 | A1 |
| 20060235747 | Hammond et al. | Oct 2006 | A1 |
| 20060261931 | Cheng | Nov 2006 | A1 |
| 20060271431 | Wehr et al. | Nov 2006 | A1 |
| 20060279307 | Wang et al. | Dec 2006 | A1 |
| 20060280356 | Yamagishi | Dec 2006 | A1 |
| 20070013124 | Graef et al. | Jan 2007 | A1 |
| 20070057815 | Foy et al. | Mar 2007 | A1 |
| 20070129906 | Stoecker et al. | Jun 2007 | A1 |
| 20070133844 | Waehner et al. | Jun 2007 | A1 |
| 20070140310 | Rolton et al. | Jun 2007 | A1 |
| 20070150403 | Mock et al. | Jun 2007 | A1 |
| 20070205751 | Suzuki et al. | Sep 2007 | A1 |
| 20070263099 | Motta et al. | Nov 2007 | A1 |
| 20070281734 | Mizrachi | Dec 2007 | A1 |
| 20080004828 | Mizrachi | Jan 2008 | A1 |
| 20080027581 | Saether et al. | Jan 2008 | A1 |
| 20080033596 | Fausak et al. | Feb 2008 | A1 |
| 20080097770 | Low et al. | Apr 2008 | A1 |
| 20080109746 | Mayer | May 2008 | A1 |
| 20080111989 | Dufour et al. | May 2008 | A1 |
| 20080149720 | Colville | Jun 2008 | A1 |
| 20080177598 | Davie | Jul 2008 | A1 |
| 20080207198 | Juric | Aug 2008 | A1 |
| 20080231113 | Guccione et al. | Sep 2008 | A1 |
| 20080255901 | Carroll et al. | Oct 2008 | A1 |
| 20080256008 | Kwok | Oct 2008 | A1 |
| 20080281691 | Pearson et al. | Nov 2008 | A1 |
| 20080296374 | Gonen et al. | Dec 2008 | A1 |
| 20080303915 | Omi | Dec 2008 | A1 |
| 20080306701 | Zhong et al. | Dec 2008 | A1 |
| 20090051907 | Li et al. | Feb 2009 | A1 |
| 20090078775 | Giebel et al. | Mar 2009 | A1 |
| 20090079388 | Reddy | Mar 2009 | A1 |
| 20090095047 | Patel et al. | Apr 2009 | A1 |
| 20090184865 | Valo et al. | Jul 2009 | A1 |
| 20090190142 | Taylor et al. | Jul 2009 | A1 |
| 20090207743 | Huq et al. | Aug 2009 | A1 |
| 20090244285 | Chathukutty | Oct 2009 | A1 |
| 20090247133 | Holmen et al. | Oct 2009 | A1 |
| 20090251815 | Wang et al. | Oct 2009 | A1 |
| 20090262341 | Konopa et al. | Oct 2009 | A1 |
| 20090265035 | Jenkinson et al. | Oct 2009 | A1 |
| 20090299543 | Cox et al. | Dec 2009 | A1 |
| 20090312009 | Fishel | Dec 2009 | A1 |
| 20090321511 | Browne | Dec 2009 | A1 |
| 20100005004 | Hudak et al. | Jan 2010 | A1 |
| 20100063894 | Lundy | Mar 2010 | A1 |
| 20100088192 | Bowles et al. | Apr 2010 | A1 |
| 20100110174 | Leconte | May 2010 | A1 |
| 20100115887 | Schroeder et al. | May 2010 | A1 |
| 20100147953 | Barkan | Jun 2010 | A1 |
| 20100157280 | Kusevic et al. | Jun 2010 | A1 |
| 20100161397 | Gauthier et al. | Jun 2010 | A1 |
| 20100169231 | Bowles et al. | Jul 2010 | A1 |
| 20101085506 | Wolff | Jul 2010 | |
| 20100219234 | Forbes | Sep 2010 | A1 |
| 20100228676 | Librizzi et al. | Sep 2010 | A1 |
| 20100235198 | Fini et al. | Sep 2010 | A1 |
| 20100237854 | Kumhyr et al. | Sep 2010 | A1 |
| 20100262481 | Baker et al. | Oct 2010 | A1 |
| 20110043628 | Yun | Feb 2011 | A1 |
| 20110060641 | Grossman et al. | Mar 2011 | A1 |
| 20110067520 | Ihrke et al. | Mar 2011 | A1 |
| 20110235853 | Bowles et al. | Sep 2011 | A1 |
| 20120016518 | Saario et al. | Jan 2012 | A1 |
| 20120029985 | Wilson et al. | Feb 2012 | A1 |
| 20120030097 | Hagan et al. | Feb 2012 | A1 |
| 20120054113 | Jayaraman et al. | Mar 2012 | A1 |
| 20120063501 | Aguren | Mar 2012 | A1 |
| 20120078413 | Baker, Jr. | Mar 2012 | A1 |
| 20120116928 | Gventer et al. | May 2012 | A1 |
| 20120116929 | Gventer et al. | May 2012 | A1 |
| 20120117001 | Gventer et al. | May 2012 | A1 |
| 20120127307 | Hassenzahl | May 2012 | A1 |
| 20120146956 | Jenkinson | Jun 2012 | A1 |
| 20120191562 | Bowles et al. | Jul 2012 | A1 |
| 20120235812 | De Mello et al. | Sep 2012 | A1 |
| 20120254046 | Librizzi et al. | Oct 2012 | A1 |
| 20130006713 | Haake et al. | Jan 2013 | A1 |
| 20130046611 | Bowles et al. | Feb 2013 | A1 |
| 20130046699 | Bowles et al. | Feb 2013 | A1 |
| 20130124426 | Bowles et al. | May 2013 | A1 |
| 20130126741 | Srivastava et al. | May 2013 | A1 |
| 20130144797 | Bowles et al. | Jun 2013 | A1 |
| 20130173434 | Hartman | Jul 2013 | A1 |
| 20130181935 | McKenzie | Jul 2013 | A1 |
| 20130191236 | Bowles | Jul 2013 | A1 |
| 20130198089 | Bowles | Aug 2013 | A1 |
| 20130198144 | Bowles | Aug 2013 | A1 |
| 20130226679 | Bowles | Aug 2013 | A1 |
| 20130253700 | Carson et al. | Sep 2013 | A1 |
| 20130275314 | Bowles | Oct 2013 | A1 |
| 20130284805 | Kraft et al. | Oct 2013 | A1 |
| 20130290146 | West et al. | Oct 2013 | A1 |
| 20130297388 | Kyle, Jr. et al. | Nov 2013 | A1 |
| 20140012643 | Behrisch | Jan 2014 | A1 |
| 20140067710 | Gventer et al. | Mar 2014 | A1 |
| 20140143161 | Ahn | May 2014 | A1 |
| 20140156883 | Bowles | Jun 2014 | A1 |
| 20140214505 | Shuster-Arechiga et al. | Jul 2014 | A1 |
| 20140347473 | Wolff et al. | Nov 2014 | A1 |
| 20150006281 | Takahashi | Jan 2015 | A1 |
| 20150066677 | Bowles et al. | Mar 2015 | A1 |
| 20150120485 | Nash | Apr 2015 | A1 |
| 20150278529 | Cho | Oct 2015 | A1 |
| 20160091549 | Snook et al. | Mar 2016 | A1 |
| 20160092849 | Cirannek et al. | Mar 2016 | A1 |
| 20160098688 | Hunt et al. | Apr 2016 | A1 |
| 20160098689 | Bowles et al. | Apr 2016 | A1 |
| 20160098690 | Silva et al. | Apr 2016 | A1 |
| 20160125367 | Bowles et al. | May 2016 | A1 |
| 20160125548 | Bowles et al. | May 2016 | A1 |
| 20160132840 | Bowles et al. | May 2016 | A1 |
| 20160171456 | Bowles | Jun 2016 | A1 |
| 20160171544 | Heminger et al. | Jun 2016 | A1 |
| 20160171575 | Bowles et al. | Jun 2016 | A1 |
| 20160210648 | Cirannek | Jul 2016 | A1 |
| 20160269401 | Saito et al. | Sep 2016 | A1 |
| 20160275460 | Ploetner et al. | Sep 2016 | A1 |
| 20160275518 | Bowles et al. | Sep 2016 | A1 |
| 20170083886 | Silva et al. | Mar 2017 | A1 |
| 20170169401 | Beane et al. | Jun 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 1365479 | Aug 2002 | CN |
| 2708415 | Jul 2005 | CN |
| 1864088 | Nov 2006 | CN |
| 1957320 | May 2007 | CN |
| 200965706 | Oct 2007 | CN |
| 102246384 | Nov 2011 | CN |
| 202351953 | Jul 2012 | CN |
| 202394296 | Aug 2012 | CN |
| 102654927 | Sep 2012 | CN |
| 102812500 | Dec 2012 | CN |
| 102930642 | Feb 2013 | CN |
| 102976004 | Mar 2013 | CN |
| 103198562 | Jul 2013 | CN |
| 103226870 | Jul 2013 | CN |
| 203242065 | Oct 2013 | CN |
| 103440607 | Dec 2013 | CN |
| 103544772 | Jan 2014 | CN |
| 203408902 | Jan 2014 | CN |
| 103662541 | Mar 2014 | CN |
| 103679147 | Mar 2014 | CN |
| 203520502 | Apr 2014 | CN |
| 203588366 | May 2014 | CN |
| 105513201 | Apr 2016 | CN |
| 1168253 | Jan 2002 | EP |
| 1703436 | Sep 2006 | EP |
| 2167553 | May 1986 | GB |
| 7112801 | May 1995 | JP |
| 7334583 | Dec 1995 | JP |
| 2000121564 | Apr 2000 | JP |
| 2002019147 | Jan 2002 | JP |
| 2002183286 | Jun 2002 | JP |
| 2002259528 | Sep 2002 | JP |
| 2002302252 | Oct 2002 | JP |
| 2002324264 | Nov 2002 | JP |
| 2002358354 | Dec 2002 | JP |
| 2003139516 | May 2003 | JP |
| 2003242243 | Aug 2003 | JP |
| 2003264007 | Sep 2003 | JP |
| 2003267509 | Sep 2003 | JP |
| 2004021569 | Jan 2004 | JP |
| 2004288143 | Oct 2004 | JP |
| 2004303102 | Oct 2004 | JP |
| 2004341681 | Dec 2004 | JP |
| 2006127308 | May 2006 | JP |
| 2006195814 | Jul 2006 | JP |
| 2006227764 | Aug 2006 | JP |
| 2006260246 | Sep 2006 | JP |
| 2007141266 | Jun 2007 | JP |
| 2007179516 | Jul 2007 | JP |
| 2007265340 | Oct 2007 | JP |
| 2008522299 | Jun 2008 | JP |
| 2008293391 | Dec 2008 | JP |
| 2007086725 | Apr 2009 | JP |
| 2009245058 | Oct 2009 | JP |
| 2009250971 | Oct 2009 | JP |
| 2010177720 | Aug 2010 | JP |
| 2012058932 | Mar 2012 | JP |
| 2013033361 | Feb 2013 | JP |
| 2013037441 | Feb 2013 | JP |
| 2013531823 | Aug 2013 | JP |
| 20000064168 | Nov 2000 | KR |
| 20130085255 | Jul 2013 | KR |
| 20140037543 | Mar 2014 | KR |
| 115096 | Mar 2001 | WO |
| 205176 | Jan 2002 | WO |
| WO-225613 | Mar 2002 | WO |
| 239357 | May 2002 | WO |
| 3012717 | Feb 2003 | WO |
| 3014994 | Feb 2003 | WO |
| 2004021114 | Mar 2004 | WO |
| 2004114490 | Dec 2004 | WO |
| 2005008566 | Jan 2005 | WO |
| 2005101346 | Oct 2005 | WO |
| 2006058601 | Jun 2006 | WO |
| 2006080851 | Aug 2006 | WO |
| WO-2007066166 | Jun 2007 | WO |
| 9128176 | Oct 2009 | WO |
| 2009128173 | Oct 2009 | WO |
| 2009129526 | Oct 2009 | WO |
| 2010040116 | Apr 2010 | WO |
| 2010128267 | Nov 2010 | WO |
| 2010128315 | Nov 2010 | WO |
| 2011131016 | Oct 2011 | WO |
| 2012138679 | Oct 2012 | WO |
| 2013074819 | May 2013 | WO |
| WO-2014075055 | May 2014 | WO |
| 2015022409 | Feb 2015 | WO |
| Entry |
|---|
| 2006 Florida Statutes Title XXXIII, Chapter 538, Sections 538.03 and 538.04, 7 pages. |
| Aftermarket Cellular Accessories, “Cellular Phone Model Identification,” retrieved from http://web/archive.org/web/20060328064957/http://aftermarketcellular.com/ic/identification.html on Mar. 16, 2014, published Mar. 28, 2006, 3 pages. |
| Altec Lansing User's Guide 2007, 8 pages. |
| Bussiness Wire, “The World's First Office Photography Machine” at CES 2008 Launched by Ortery Technologies, Jan. 7, 2008, 3 pages. |
| CNET, “Tackling LCD “burn ins”, and dead/stick Pixels”, published Sep. 2, 2009, retrieved from http://www.cnet.com/news/tackling-lcd-burn-ins-and-deadstuck-pixels/. |
| Evgenii Masunov, Mar. 25, 2010, http://www.appleinsider.ru/news/ipone-obladaet-luchshim-tachskrinom-provereno—robotom.html, 4 pages. |
| Geekanoids, You Tube Video, “Apple iPhone 3GS Unboxing and Review”, uploaded on Jun. 19, 2009, retrieved from http://www.youtube.com/watch?v=GCEi9QAeDqk on Sep. 2, 2009. |
| GSM Arena Glossary, “LCD (Liquid Crystal Display”, retrieved from http://www.gsmarena.com/glossary.php3?term=lcd on Apr. 28, 2016, 1 page. |
| Lambert, Emily, “Use It Up, Wear It Out”, Forbes 175.5 (2005): 77-78. Business Source Complete. Web. Jan. 6, 2015, 3 pages. |
| Littleton Partners with Donations Ink (Jan. 19, 2006) US Fed News Service, Including US State News. Web. Jan. 6, 2015, 1 page. |
| MobileGazette.com, “2006 in Review: The Good, The Bad and the Ugly”, published Dec. 2006, retrieved from http://www.mobilegazette.com/2006-review-06x12x22.htm on Nov. 11, 2015. |
| PC World, “Wipe Your Cell Phone's Memory Before Giving it Away”, published Jan. 2006, retrieved from http://www.washingtonpost.com/wp-dyn/content/article/2006/01/30/AR2006013001144.html on Nov. 10, 2015. |
| Perng et al., “A Novel Vision System for CRT Panel Auto-Inspection”, Proceedings of the 2005 IEEE International Conference on Mechatronics, Jul. 10-12, 2005, pp. 4. |
| Perng et al., “A Novel Vision System for CRT PaNnel Auto-Inspection”, Journal of the Chinese Institute of Industrial Engineers, vol. 24, No. 5, pp. 341-350 (2007). |
| Rawson, Chris, “TUAW: 25 Ways to Check the Hardware on Your iPhone 4”, published Aug. 12, 2010, retrieved at http://www.tuaw.com/2010/08/13/hardware-test-your-iphone-4/ on Feb. 28, 2014. |
| Rehg et al. “Vision for a Smart Kiosk” IEEE, Computer Society Conference on Computer Vision and Pattern Recognition (1997). |
| Rolf Steinhilper “Remanufacturing: The Ultimate Form of Recycling”, Fraunhofer IRBVerlag, 1998, parts 1-3, http://www.reman.org/Publications—main.htm. |
| SimplySellular, “Get Cash for your Old Cell Phone”, published Apr. 2, 2010, retrieved from http://simplysellular.com/conditions.php on Jan. 6, 2015, 2 pages. |
| Wilson, Doug, “Liquid Crystal Display (LCD) Inspection System”, National Instruments Case Study, available May 10, 2009, retrieved from http://sine.ni.com/cs/app/cod/p/id/cs-345 on Jan. 5, 2015, 2 pages. |
| Yahoo Answers, “What is a Clean ESN?” published Jun. 23, 2009, retrieved from http://web.archive.org/web/20090623215042/http://answers.yahoo.com/question/inde,8020US?qid=20080318061012AANFRco on Apr. 3, 2014. |
| Co-Pending U.S. Appl. No. 15/130,851 of Forutanpour, B. et al., filed Apr. 15, 2016. |
| Co-Pending U.S. Appl. No. 15/195,828 of Forutanpour, B. et al., filed Jun. 28, 2016. |
| Co-Pending U.S. Appl. No. 15/630,508 of Silva, J. et al., filed Jun. 22, 2017. |
| Co-Pending U.S. Appl. No. 15/630,539 of Bowles, M. et al., filed Jun. 22, 2017. |
| Investopedia: What's the difference between weighted average accounting and FIFO/LILO accounting methods? Aug. 19, 2010. Accessed via archive.org [https://web.archive.org/web/20100819200402/http://www.investopedia.com/ask/answers/09/weighted-average-fifo-lilo-accounting.asp]. |
| Number | Date | Country | |
|---|---|---|---|
| 20170356857 A1 | Dec 2017 | US |
