Patent Grant
10171184
The present disclosure relates generally to the field of electronic device testing systems and more specifically to the field of electronic device testing equipment for testing smart phones and tablets.
Automatic system level testing (ASLT) can be any testing assembly that performs a test on a semiconductor wafer or die, or a device such as a solid-state drive or a smart phone. ASLT assemblies may be used to execute automated tests that quickly perform measurements and generate test results that can then be analyzed. An ASLT assembly may be anything from a computer system coupled to a meter, to a complicated automated test assembly that may include a custom, dedicated computer control system and many different test instruments that are capable of automatically testing electronics parts, semiconductor wafer testing (such as system-on-chip (SOC) testing) or testing devices such as smart phones. ASLT systems both reduce the amount of time spent on testing devices to ensure that the device functions as designed and serve as a diagnostic tool to determine the presence of faulty components within a given device before it reaches the consumer.
ASLT systems to test smart phones, for example, are required at both the point of sale and at the production facilities. Currently, if a user experiences a problem with their phone and brings it into a retail facility, there are no systems in place to exhaustively test the hardware and software on the phone to determine the source of the problem with a high degree of accuracy. Some retail facilities have the capability of performing some basic software testing of the phone, however, no retail facility has the ability to perform a complete hardware and software test on the phone and to test all the functions on the phone automatically. Accordingly, the phone either needs to be returned and replaced, which over time can result in substantial costs to the manufacturer. Alternatively, if the phone cannot be returned or replaced for any reason, the customer ends up dissatisfied if the problems with the phone are not easily diagnosed and fixed.
In some cases, the problem with the phone cannot be diagnosed at the retail facility. This is referred to as a No Trouble Found (NTF) or No Fault Found (NFF) condition. In such cases, the phone is sent to a repair center where a battery of tests are performed to determine if there is any issue. Currently, even the repair centers do not have a satisfactory solution to automatically test all the hardware and software functions on a smart phone.
While some software testing methodologies are in place, typically, a person has to manually test many of the device's hardware and software functions to ensure that the device is working adequately. Further, even if the device is repaired, there is no traceability for the repair work performed or any fully automated method for verifying that the repair work was performed satisfactorily. A person has to manually test the device to ensure that the device is working properly. Accordingly, the repair and test methodologies currently in place are subjective and not foolproof. Any errors in the repair or verification process will cost the manufacturers more money and result in customer dissatisfaction. Further, sending the phone to a repair center will almost always leave a customer dissatisfied as most customers cannot afford to be without their smart device for an extended period of time.
Additionally, the production facilities at which the phones are manufactured also do not currently have any mechanisms in place for complete hardware and software automated testing of the phone devices. Most of the functional testing that takes place before the phones are packaged is manual and, accordingly, it is error-prone and expensive. Further, the cost and susceptibility to error of the manual test processes currently in place is increasing as the feature-set on the devices increases.
Accordingly, a need exists for an automated tester system that can address the problem of testing phones, e.g., smart phones at retail facilities, repair centers, and production facilities. What is needed is an automated tester system that can automatically perform a wide range of hardware and software functional tests on a smart phone.
Embodiments of the present invention provide a tester system (hereinafter referred to as the “Smart Box”) that allows a user to perform a series of hardware and software tests in a closed and controlled environment, thus eliminating subjectivity of manual testing. Embodiments of the present invention are also optimized for speed and configured to test the major features of the phone in a short duration of time. Further, embodiments of the present invention transmit all test data to a centralized server enabling mobile operators to track feature issues, model issues, geographic and/or store issues. Accordingly, embodiments of the present invention are enabled for global analytics.
In one embodiment, the Smart Box is a box-shaped apparatus comprising robotics that allows the smart device to be moved in the x, y and z directions. Further, the apparatus comprises a stylus that can also move in the x, y and z directions and be used to actuate buttons on the smart device. In one embodiment of the present invention the smart device moves in the x and y direction while the stylus moves in the z direction. Accordingly, embodiments of the present invention are configured to allow the stylus and mobile device the mobility so that the stylus can make contact with the device at any location on the device to interface therewith.
In one embodiment, a user can place the smart device inside the Smart Box and use a computer connected to the Smart Box to select one or more tests to be applied to the device. The test software on the computer interacts with Smart Box to engage the smart device under test and the robotics of the Smart Box to exercise the various functions of the smart device. Each test is performed and compared against pass/fail criteria. A pass/fail determination is made and the following test is performed. In one embodiment, reports are automatically generated reporting the results of the various tests and sent to the cloud server.
In one embodiment, an automatic system level testing (ASLT) system for testing smart devices is disclosed. The system comprises a system controller operable to be coupled to a smart device, wherein the system controller comprises a memory comprising test logic and a processor and an enclosure comprising a plurality of components. The plurality of components comprise: (a) a robotic arm comprising a stylus; (b) a platform comprising a device holder, wherein the device holder is operable to hold the smart device inserted therein; and (c) a wireless access point. The processor is configured to automatically control the smart device and the plurality of components in accordance with the test logic, and wherein the processor is further configured to: (a) control the smart device to activate a wireless mode therein; (b) receive wireless signals from the wireless access point using the smart device; (c) retrieve wireless scan results from the smart device; and (d) analyze the wireless scan results to determine wireless functionality for the smart device.
In one embodiment, an automatic system level testing (ASLT) system for testing smart devices is disclosed. The system comprises a system controller operable to be coupled to a smart device, wherein the system controller comprises a memory comprising test logic and a processor, and further the system comprises an enclosure comprising a plurality of components, wherein the plurality of components comprise: (a) a robotic arm comprising a stylus attached thereo, wherein the stylus is operable to manipulate the smart device to simulate human interaction therewith; and (b) a platform comprising a device holder attached thereo, wherein the device holder is operable to hold the smart device inserted therein, wherein the platform is operable to rotate in a x-z plane and a y-z plane. The processor is configured to automatically control the smart device and the plurality of components in accordance with the test logic, and further wherein the processor is configured to: (a) retrieve metadata from a plurality of sensors on said smart device; and (b) transmit the metadata to the system controller.
In one embodiment, an automatic system level testing (ASLT) system for testing smart devices is disclosed. The system comprises: (a) a system controller coupled to a smart device, wherein the system controller comprises a memory comprising test logic and a processor; (b) an enclosure comprising a plurality of components, the plurality of components comprising: (i) a robotic arm comprising a stylus attached thereto; (ii) a platform comprising a device holder attached thereto, wherein the device holder is operable to hold the smart device; and (iii) an external programmable LED. The processor is configured to automatically control the smart device and the plurality of components in accordance with the test logic, and wherein the processor is further configured to: (a) control the smart device to activate an auto-brightness mode; (b) control the external programmable LED to turn to full brightness mode; and (c) analyze light intensity metadata from the smart device responsive to the brightness mode.
In one embodiment, an automatic system level testing (ASLT) system for testing smart devices is disclosed. The system comprises a system controller operable to be coupled to a smart device, wherein the system controller comprises a memory comprising test logic and a processor and the system further comprises an enclosure comprising a plurality of components, wherein the plurality of components comprise: (a) a robotic arm comprising a stylus affixed thereto; and (b) a platform comprising a device holder affixed thereto, wherein the device holder is operable to hold the smart device. The processor is configured to automatically control the smart device and the plurality of components in accordance with the test logic, and wherein the processor is further configured to: (a) control the smart device to activate GPS mode; (b) receiving GPS and location results from the smart device; and (c) analyzing the GPS and location results received from the smart device to determine GPS functionality for the smart device.
In one embodiment, a method of testing a smart device in a testing system is presented. The method comprises registering a model of a smart device inserted into the testing system, wherein the testing system comprises: (a) a system controller operable to be coupled with the smart device, wherein the system controller comprises a memory comprising test logic and a processor; and (b) an enclosure, wherein the enclosure comprises a plurality of components, the plurality of components comprising: (i) a robotic arm comprising a stylus, wherein the stylus is operable to manipulate the smart device to simulate human interaction therewith; and (ii) a platform comprising a device holder, wherein the device holder is operable to receive a smart device inserted there into. The method further comprises: (a) controlling the smart device and the plurality of components in accordance with the test logic; (b) controlling the smart device to activate a GPS mode; (c) receiving GPS and location results from the smart device; and (d) analyzing the GPS and location results received from the smart device to determine GPS functionality for the smart device.
The following detailed description together with the accompanying drawings will provide a better understanding of the nature and advantages of the present invention.
In the figures, elements having the same designation have the same or similar function.
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. While the embodiments will be described in conjunction with the drawings, it will be understood that they are not intended to limit the embodiments. On the contrary, the embodiments are intended to cover alternatives, modifications and equivalents. Furthermore, in the following detailed description, numerous specific details are set forth in order to provide a thorough understanding. However, it will be recognized by one of ordinary skill in the art that the embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail as not to unnecessarily obscure aspects of the embodiments.
Notation and Nomenclature Section
Some regions of the detailed descriptions which follow are presented in terms of procedures, logic blocks, processing and other symbolic representations of operations on data bits within a computer memory. These descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. In the present application, a procedure, logic block, process, or the like, is conceived to be a self-consistent sequence of steps or instructions leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, although not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated in a computer system.
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussions, it is appreciated that throughout the present invention, discussions utilizing the terms such as “analyzing,” “reading,” “receiving,” “controlling,” “analyzing,” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
The description below provides a discussion of computers and other devices that may include one or more modules. As used herein, the term “module” or “block” may be understood to refer to software, firmware, hardware, and/or various combinations thereof. It is noted that the blocks and modules are exemplary. The blocks or modules may be combined, integrated, separated, and/or duplicated to support various applications. Also, a function described herein as being performed at a particular module or block may be performed at one or more other modules or blocks and/or by one or more other devices instead of or in addition to the function performed at the described particular module or block. Further, the modules or blocks may be implemented across multiple devices and/or other components local or remote to one another. Additionally, the modules or blocks may be moved from one device and added to another device, and/or may be included in both devices. Any software implementations of the present invention may be tangibly embodied in one or more storage media, such as, for example, a memory device, a floppy disk, a compact disk (CD), a digital versatile disk (DVD), or other devices that may store computer code.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of the present invention. As used throughout this disclosure, the singular forms “a,” “an,” and “the” include plural reference unless the context clearly dictates otherwise. Thus, for example, a reference to “a module” includes a plurality of such modules, as well as a single module, and equivalents thereof known to those skilled in the art.
The Methodology of Using the Various Capabilities of the Smart Box to Perform Testing of Other Functionality of the Smart Device
Embodiments of the present invention provide a tester system (hereinafter referred to as the “Smart Box”) that allows a user to perform a series of hardware and software tests in a closed and controlled environment, thus eliminating subjectivity of human testing. Embodiments of the present invention can be optimized for speed configured to test the major features of the phone (or tablet) in a short duration of time. Further, embodiments of the present invention transmit all test data to a centralized server enabling mobile operators to track feature issues, model issues, geographic and/or store issues. Accordingly, embodiments of the present invention are enabled for global analytics.
In one embodiment, the Smart Box is a box-shaped apparatus comprising a robotic arm that allows the smart device to be moved in the x, y and z directions. Further, the apparatus comprises a stylus attached to the robotic arm that can also move in the x, y and z directions and be used to actuate buttons on the smart device. In one embodiment of the present invention the smart device moves in the x and y direction while the stylus moves in the z direction. Accordingly, embodiments of the present invention are configured to allow the stylus and mobile device the mobility so that the stylus can make contact with the device at any location on the device.
In one embodiment, a user can place the smart device inside the Smart Box and use a computer connected to the Smart Box to select one or more tests to be applied to the device. The test software on the computer interacts with Smart Box to engage the smart device under test and the robotics of the Smart Box to exercise the various functions of the smart device. Each test is performed and compared against pass/fail criteria. A pass/fail determination is made and the subsequent test is performed. In one embodiment, reports are automatically generated reporting the results of the various tests and sent to the cloud server.
Embodiments of the present invention are advantageous because they help reduce No Trouble Found (NTF)/No Fault Found (NFF) occurrences at both point of sale, repair center and production facilities by executing simple automated functional and specification tests on devices. Embodiments of the present invention leverage digital and physical robotics automation to test for problem scenarios in a controlled environment. Further, embodiments of the present invention implement test automation platforms to orchestrate problem scenarios, thereby leveraging the Smart Box's robotic test enclosure combined with robust test emulators. The Smart Box platform further targets a low-cost scalable profile with a simple and easy to use experience targeted at point of sale and repair center end users.
Embodiments of the present invention also help to isolate quality issues and classify true failures. By automating the testing process, human subjectivity is eliminated, thereby, standardizing the test process. Further, embodiments of the present invention provide a mechanism to verify and validate repairs, thereby, ensuring consistency and accuracy. Accordingly, the cost to manufacturers is decreased, device returns are decreased and customer satisfaction is increased. Further, embodiments of the present invention capture end-user experience metrics allowing performance to be tracked over time.
Devices that have no detectable faults can readily be determined using the Smart Box technology thereby avoiding costly repair/diagnostic outsourcing. Also, if a device is faulty, the fault or defect can efficiently and automatically be determined using the Smart Box technology versus time consuming and error prone manual testing techniques. Also, intermittent faults can more accurately be detected. By removing manual testing steps, device testing can be made more efficient, more effective and more reproducible. Also, test results over many devices can more easily be compiled for archiving and analysis purposes.
The test automation software running on computer 130 can be, for example, the QUIKSTRESS™ testing platform for lab and live testing which, among other things, allows testers of smart devices to easily record macros and have them play-back across different models and manufacturers. As will be explained below, the test automation software, e.g., QUIKSTRESS, etc. can be designed to identify and troubleshoot customer-experience issues at the point of sale, and to reduce the No Fault Found (NFF) devices at the repair centers to save costs for both OEMs and operators.
In one embodiment, when an end user connects to the Smart Box 110 using computer system 130 after placing the device to be tested in the Smart Box 110, user interface 120 will begin to guide the user through a series of options for conducting the requisite tests. In one embodiment, the various tests can be grouped into different categories, e.g., tests associated with the display, the audio, the battery, sensors, camera, and keypad, etc. as shown in user interface 120. Other exemplary categories may also test the touch screen, physical buttons, gyro and accelerometer.
The user can select either one or all of the tests to execute within a certain category. Alternatively, the user can select all the tests within all categories to execute at the same time. The test automation software running on computer 130 will determine the tests that can be executed simultaneously versus the tests that are to be executed serially. Upon user selection, the tests will then execute and provide conclusive and actionable results.
Embodiments of the present invention allow information to be communicated from the smart device and components within Smart Box 240 to system controller 240 while the smart device is being tested and for commands to flow from the system controller back to the smart device. For example, the smart device being tested may be used to take a picture of a physical reference image and the information could be communicated to system controller 230 to determine if it matches the reference image stored in memory to determine if the camera on the smart device is functioning properly. Embodiments of the present invention are, therefore, capable of manipulating the smart device both physically and through software, and are also able to collect diagnostic information in real-time using the system controller to determine if the smart device is functioning normally.
In one embodiment, the physical features/instrumentation of the Smart Box include the enclosure 315, the robotic elements, the sensors and instruments, the plate that holds the smart device DUT and the electronics to interface with and drive testing of the DUT. This case includes the robotic mechanisms for holding and automatically moving the DUT and for automatically physically interfacing with the touch screen and other physical buttons of the DUT to simulate human interaction therewith.
As will be explained in further detail below, this case includes the various Smart Box sensors that detect output from the DUT such as a camera, a microphone, a flash detector, wireless signal detectors, interfaces to read the contents of the DUT memory, and interfaces to pick up signals from the audio jack, etc. The case also includes the various instruments that can stimulate the DUT, such as a speaker, a wireless signal broadcaster, external speaker, motion devices on the plate that holds the DUT, a robotic stylus, a USB charger interconnect, a wireless charger device, etc. This case also includes the logic, that can be integrated with the Smart Box, or external thereto, for performing the actual testing and automated control of the physical elements/robotic elements/instruments of the Smart Box, e.g., using the QUIKSTRESS software.
In one embodiment, the Smart Box 300 comprises an image plate 350. The image plate comprises a physical reference image that is fixed inside of the Smart Box and can be used to test the front and rear camera functionality of the smart device. In one embodiment, the physical reference image can comprise a color chart. In one embodiment, a separate image plate can be used for each of the front and rear cameras. Reference images identical to the physical reference image 350 can be stored in an image library within the automated tester software running on terminal 130.
The smart device 355 and the Smart Box 300 can be controlled via an appropriate communication protocol (e.g., USB, Wi-Fi etc.) using the tester software running on terminal 130. The software launches and controls the camera application on smart device 355. The software also controls the smart device 355 and the robotics (e.g. stylus 385, smart plate or platform 345) to move and position the smart device 355 in an appropriate location relative to the image plate 350. The software also activates the camera on the smart device to capture an image (using either the front or the back camera or both simultaneously if the Smart Box is equipped with multiple image plates). The software can also be configured to retrieve the image from the smart device camera and compare the retrieved image with the reference image stored on terminal 130 to determine if the camera passes or fails the test. In one embodiment, the comparison threshold for determining a pass or fail is user configurable.
In one embodiment, Smart Box 300 comprises a custom phone holder 310. The custom phone holder is customizable and can be customized for all the different models of smart devices. Because each smart device has a different form factor, a customizable phone holder is required to accommodate the various form factors. In order to test a different smart device (e.g., switching from testing an iPhone to a Samsung phone), the custom phone holder 310 in Smart Box 300 would need to be swapped out. In one embodiment, the custom phone holder 310 may be affixed to the plate or platform 345 using one of several means (e.g., clamps, screws, dowels, etc.)
In a different embodiment, the smart plate 345 and custom holder 310 are designed and manufactured as a single unit with each model of smart device requiring a different plate unit. Accordingly, in one embodiment, the entire plate 345 is swapped out in order to test a different model phone. In one embodiment, the Smart Box can comprise a robotic arm that can automatically swap out a smart plate if a user sends a command from terminal 130 to test a different model phone.
In one embodiment, the plate 345 is configured to move in the x-y direction while the stylus 385 (and the robotic arm attached thereto) moves in the z direction. Also the smart plate 345 can be configured to rotate so as to alternate the phone 355 between a portrait and landscape orientation. In one embodiment, the smart plate 345 may also be configured to tilt in the theta-x and theta-y directions as well.
In one embodiment, Smart Box 300 comprises a stylus 385. The stylus 385 can be a capacitive stylus with a soft tip similar to those used by hand on touch-screen devices as an alternative to finger touch. The stylus 385 can be controlled by the robotics within Smart Box 300. For example, the stylus 385 can be attached to a robotic arm that allows movement in the z plane. As mentioned previously, the Smart Box 300 has a mechanism to allow at least three-dimensional movement of the smart device under test and sensors relative to each other. In one embodiment, the smart device is placed a stage (or smart plate 345) that can move in the X-Y dimensions while the stylus 385 and other sensors are mounted on an arm moving in the Z dimension. In a different embodiment, the robotic arm and the stylus attached thereto can move in all three x, y and z planes.
In one embodiment, Smart Box comprises an external camera 360. It should be noted that in different embodiments, the Smart Box can also comprise multiple cameras. External camera 360 can be a high resolution camera operable to take high resolution pictures of any sized smart device. The camera 360 can be mounted in a fixed position within the Smart Box and is connected to and controlled by the tester software on terminal 130. The camera 360 can be used to take pictures of the DUT display during one of the several tests using the camera, e.g., a touch-screen test implementation. Alternatively, the camera 360 can be used to take pictures of calibration-related images as part of a robotic calibration process run by the Smart Box and test automation software. In a different embodiment, the camera 360 can move in the z direction and be adjusted to accommodate different sized smart device screens.
In one embodiment, the Smart Box 300 comprises two audio capture devices 370 and 395, an external microphone 330, an audio dampening module 340, and an external speaker 390 that are used to test the various audio features of the smart device. In different embodiments, either more or less audio capture devices or speakers may be available. The audio capture devices 370 and 395, in one embodiment, may be connected to the tester automation software through a USB or Wi-Fi connection (or any other appropriate protocol). The audio capture devices may be able to both source and capture high quality stereo audio. Sourcing can be done through a 3.5 mm stereo output, while capture is done through a 3.5 mm stereo input or ¼″ microphone input for instance. The audio capture devices can be used, for example, to test the speaker phone capability on the smart device and to test the sound quality through the microphone jack on the smart device.
In one embodiment, the speaker 390 and microphone 330 connect to the audio capture devices and are positioned in a relatively close position to the speakers and microphones on the smart device. The speakers and microphone are used to test the receiver and headset/microphone jack on the smart device respectively. In one embodiment, the Smart Box also comprises a 3.5 mm audio signal splitter to split the headphone and microphone inputs. The splitter splits a 4-connector plug that is plugged into the jack on the smart device into a 3-connector jack for stereo device output and a 2-connector jack for mono device input.
In one embodiment, the automation test software integrates mobile voice quality testing modules. For example, the test software can integrate POLQA, a software library includes perceptual measurement software that calculates audio quality by comparing a degraded file to a reference file. POLQA is standardized by the International Telecommunication Union (ITU-T) and using the POLQA library allows the test automation software to determine the quality of the audio files received from the smart device in accordance with an industry standard.
In one embodiment, the Smart Box can also include an audio dampening module 340 to mitigate any noise issues and provide audio insulation for the Smart Box enclosure 315. In most embodiments, the enclosure encloses the Smart Box on all sides in order to minimize noise. The front door, however, can be removable as shown in
In one embodiment, the Smart Box 300 also comprises an external accelerometer 320. The accelerometer can be mounted on the smart plate 345 and connected to the system controller (e.g., automation software running on terminal 130) to be used for monitoring vibrations.
In one embodiment, the Smart Box comprises an external programmable light source (not shown in
In one embodiment, the Smart Box can also comprise an external light sensor or meter (not shown in
In one embodiment, the Smart Box may include a capacitive object (not shown in
In one embodiment, the Smart Box may also include a fingerprint device (not shown in
In one embodiment, Smart Box 300 can also comprise a powered USB hub 370. The USB hub 370 can provide power to the various components of the Smart Box, e.g., microphone, audio capture devices, etc. However, the present invention is not limited to simply USB powered devices but also encompasses other methods of providing power and communicating with the various components of the Smart Box.
The Smart Box 420 comprises integrated robotics for x and y direction movements of the smart plate 345. It also includes integrated stylus finger 385 that can move in the z direction. The Smart Box may also comprise fixed reference images, e.g., images on image plate 350.
The Smart Box can also comprise a powered USB that is used to power an external camera, external audio capture and generator devices (e.g., speakers and microphones), external light sensor, external light source, external proximity device, and an external finger print device.
As also shown in
The USB hub 541 is used to supply power to the various external components within the Smart Box and the smart devices 510A-C. For example, the USB hub powers the lights 551, the dual audio capture and generator devices 552 and 555, the accelerometer 554, the microphone 553, the Bluetooth dongle 520, and the speaker 556 can all be powered using the USB hub 541. Further, the USB hub 541 is also operable to communicate information between the various components and the test automation software on system controller 540. This configuration is advantageous because it allows embodiments of the present invention to stress the phone physically while being in communication with the automation software on system controller 540 at the same time. For example, the stylus and the smart device 510A may be interacting physically at the same time as an application package is being downloaded to smart device 510A from the test software to stress the memory or CPU.
In one embodiment, each custom phone holder 765 will have its own device code and this information will be communicated to the system controller in order to determine what type of device 770 is placed into the custom phone holder. For example, the custom phone holder can be equipped with a QR code, which is communicated to the system controller.
As mentioned previously, in one embodiment, the smart plate 715 and the custom holder 765 constitute a single unit having a unique QR code. This QR code can be communicated to the system controller via USB or Wi-Fi. In another embodiment, the smart plate (or base plate) 715 can comprise dowels for affixing the custom holder 765 onto the smart plate.
The system controller can use the QR code to determine device specifications, e.g., thickness of device, diagonal length of screen, etc. and to calibrate the phone. For example, the robotics may be used to touch a single point on the screen using the stylus and use the information from the contact to determine where the smart device is positioned relative to the stylus and other components. In other words, the QR code and robotics in combination with the system controller can be used to perform an x-y calibration on the phone to determine its precise location. Once the x-y calibration is performed and the corners of the device are located, the system controller can determine where the various physical and soft buttons, e.g., Home button are on the device. Once a device is calibrated, its information can be saved in a calibration file on system controller and retrieved the next time the same device is tested.
In one embodiment, the calibration information can be communicated to other components within the Smart Box that interface with the smart device. For example, once the diagonal length of the screen is determined through the calibration process, the stylus can be programmed by the system controller to adjust to the screen size of the smart device.
The calibration information and device specifications can then be used by the robotics within the Smart Box to actuate either on or off-screen buttons on the smart device. For example, when the device specifics are known, the stylus can be programmed to actuate the Home button on the smart device.
Accordingly, embodiments of the present invention can drive the smart device from the system controller through the USB or Wi-Fi connection. In one embodiment, the system controller draws information from the smart device, e.g., metadata regarding information being displayed on the smart device screen. Subsequently, using the calibration information, the metadata, and device specifications, the system controller can determine the location for active regions on the touch screen panel, soft buttons and physical buttons on the smart device screen. This information can be translated to an X-Y coordinate or location for the robotics to interact physically with the smart device.
In one embodiment, the Smart Box can comprise actuators 780 (also controlled by the system controller) or servos used to activate buttons on the smart device. For example, actuators can be used to activate the volume buttons, ring silent switch, and/or the wake/sleep button. The actuators can either be moulded into the smart plate itself or they can be outside the plate and configurable. In one embodiment, the stylus 385 itself can also be programmed by the system controller to activate the buttons.
In one embodiment, actuators or servos may be used to insert the power cable into the phone. Accordingly, the custom phone holder should be able to hold the device physically secure so that the power cable into the smart device. The actuators may either be built into the custom phone holder itself or be external. Similarly, with the audio connections, e.g., headphones, microphone, etc., actuators may be built into the phone holder in order to plug in the various connections.
In one embodiment, in order to reduce human intervention and further automate the testing process, the Smart Box 300 can be equipped with a robotic arm that places the smart device into the custom phone holder.
In one embodiment, the smart plate underneath the custom holder can rotate in order to switch the device from portrait to landscape mode. Also, in one embodiment, the smart plate can comprise hinges that allow it to rotate around the x or y-axes in order to test the gravity sensors and gyro functionality of the smart device.
In one embodiment, the smart plate can have a temperature sensor built into it. The temperature sensor can, for example, measure the heat emanating from the device using infrared technology. Also, the smart plate can have a heating or cooling element built into it to artificially raise or lower the temperature of the smart device to determine its operating specifications.
In one embodiment, the smart plate can also have a vibration sensor built into it. The vibration sensor allows the vibrate feature of the smart device to be tested.
As explained above, embodiments of the present invention are advantageous because they allow a) physical interaction with the phone using (e.g. using a stylus, sound, light, etc.; b) automated control of the phone using a system controller and an appropriate communication protocol (e.g., USB or WiFi); c) application packages installed in the system controller that stress the phone; and d) comprise external sensors that monitor the phone, e.g., audio, camera, accelerometer, etc. The below series of figures and flowcharts provide an illustration of the manner in which embodiments of the present invention perform the various tests on a smart device.
Testing the Smart Device Touch Screen
At step 902, a reference image is stored in the memory of system controller 820. At step 904, communication is established between the system controller 820 and the smart device 830, and also between the system controller 820 and the robotics 850 within the Smart Box. In one embodiment, this communication is performed using USB, Wi-Fi or any other suitable protocol. The communication, in one embodiment, can flow through USB hub 810.
At step 906, a sketchpad application is launched on the smart device. In other embodiments, different applications may be used for testing the touch screen.
At step 908, the robotics 850 (e.g., stylus 840, smart plate etc.) and the smart device are controlled to draw test images on the smart device touch screen.
At step 910, the sketched image is retrieved from the smart device.
Finally, at step 912, the retrieved image is compared with the reference image stored in the system controller memory for similarity to determine if the device passed or failed the test.
As mentioned above, embodiments of the present invention advantageously allow robotic components within the Smart Box to physically interact with the phone while the smart device is being manipulated through software and information is being retrieved from the smart device for analysis using a system controller.
Further, embodiments of the present invention can advantageously test the entire screen by making contact with all areas of the screen using the stylus to ensure that all the pixels on the screen are functioning properly. This eliminates human error and is more efficient that prior methods of testing screens on smart devices that required active human interaction and contact.
Also, in one embodiment, the stylus can be used to draw various shapes on the device screen to test for on-screen lineation and multi-spot touching. For example, the stylus can be used to trace a circle or draw a square and the information can be captured by the system controller to determine if the touch screen is functioning properly. The stylus can also be used to test gesture recognition functionality on the touch screen.
At step 1102, a reference image is stored or resides in the memory of system controller 1020. At step 1104, communication is established between the system controller 1020 and the smart device 1030, and also between the system controller 1020 and the robotics 1050 within the Smart Box. In one embodiment, this communication is performed using USB, Wi-Fi or any other suitable protocol. The communication, in one embodiment, can flow through USB hub 1010.
At step 1106, a sketchpad application or other graphics application is launched on the smart device. In other embodiments, different applications may be used for testing the touch screen.
At step 1108, communication is established between the system controller and the external camera 1040.
At step 1110, the robotics 1050 (e.g., stylus 1060, smart plate etc.) and the smart device are controlled to draw test images on the smart device touch screen.
At step 1112, the external camera 1040 is controlled by the system controller to take a picture of the touch screen on the smart device.
At step 1114, the sketched image is retrieved from the external camera.
Finally, at step 1116, the retrieved image is compared with the reference image stored in the system controller memory for similarity to determine if the device passed or failed the test.
Testing the Cameras on the Smart Device
At step 1302, a reference image is stored or resides in the memory of system controller 1210. This reference image is an instantiation of the physical reference image present on the image plate(s) 1250 within the Smart Box. In one embodiment, the Smart Box comprises a single image plate and the smart plate 345 is flipped to test both the front and rear camera using the same physical reference image. In a different embodiment, the Smart Box comprises two discrete image plates (one above the smart plate for testing the front facing camera and one below the smart plate for testing the rear facing camera) (as shown in
At step 1304, communication is established between the system controller 1210 and the smart device 1220, and also between the system controller and the robotics 1290 within the Smart Box. In one embodiment, this communication is performed using USB, Wi-Fi or any other suitable protocol. The communication, in one embodiment, can flow through USB hub 1240.
At step 1306, a default camera application is launched on the smart device. In other embodiments, different applications that use the camera may be used for testing the touch screen also.
At step 1308, the system controller controls the smart device and robotics to move and position the smart device relative to the physical reference image so that the front camera can obtain a clear picture of the physical reference image above the smart plate and so the rear camera can obtain a clear picture of the physical reference image below the smart plate.
At step 1310, the camera(s) on the smart device are activated to take an image of the image plate(s).
At step 1312, the image or images taken by the camera(s) can be retrieved from the smart device using the system controller.
Finally, at step 1314, the retrieved image is compared with the reference image stored in the system controller memory to determine if the device passed or failed the test.
In one embodiment, the flash on the camera can also be tested as part of the camera test performed by the Smart Box. Typically, a sensor within the Smart Box would be able to detect if the flash on the camera is functioning. As discussed previously, the Smart Box can also comprise an external light sensor or meter to measure light intensity from the smart device (e.g., flash and display light intensity). In addition, the external camera within the Smart Box can also be used during the flash test. The camera can be configured to test the sensitivity of the flash. During testing, the flash can either be driven using an Application Programming Interface (API) or it can be activated by navigating through the user interface using the stylus.
In one embodiment, the fixed reference images within the Smart Box can comprise color charts. By capturing images of the color charts and transmitting them to the system controller, embodiments of the present invention can test the smart device cameras for color, blurriness and orientation.
Testing the Audio Components on the Smart Device
At step 1502, a reference audio file is stored in the memory of system controller 1490.
At step 1504, communication is established between the system controller 1490 and the smart device 1410, and also between the system controller and the robotics 1450 (e.g. stylus 1440) within the Smart Box. In one embodiment, this communication is performed using USB, Wi-Fi or any other suitable protocol. The communication, in one embodiment, can flow through USB hub 1470.
At step 1506, audio device 1420 and speaker 1430 is controlled using the system controller.
At step 1508, the system controller is used to control the smart device and the robotics to move and position the smart device in an appropriate position relative to the speaker 1430.
At step 1510, an audio receiver application on the smart device is launched. At step 1512, the reference audio file is played using audio device 1420 and speaker 1430.
At step 1514, the system controller stop recording the audio on the smart device and retrieves the file from the smart device. At step 1516, the retrieved audio file is compared with the reference audio file stored in the system controller memory to determine if the device passed or failed the test. In one embodiment, the POLQA library can be used to perform the file comparison and determine a pass/fail condition.
At step 1702, a reference audio file is stored or resides in the memory of system controller 1650.
At step 1704, communication is established between the system controller and the smart device 1610, and also between the system controller and the robotics 1620 (e.g. stylus 1630) within the Smart Box. In one embodiment, this communication is performed using USB, Wi-Fi or any other suitable protocol. The communication, in one embodiment, can flow through USB hub 1640.
At step 1706, audio device 1670 is controlled using the system controller.
At step 1708, the system controller is used to control the smart device and the robotics to automatically insert an audio cable 1660 into the headset/microphone jack of the smart device. In one embodiment, an audio cable can be plugged into the audio jack of the smart device automatically using commands sent from the system controller to a servo on the smart plate or custom holder.
At step 1710, an audio receiver application on the smart device is launched. At step 1712, the reference audio file is played using audio device 1670.
At step 1714, the system controller stops recording the audio on the smart device and retrieves the file from the smart device. At step 1716, the retrieved audio file is compared with the reference audio file stored in the system controller memory to determine if the device passed or failed the test. In one embodiment, the POLQA library can be used to perform the file comparison and determine a pass/fail condition.
At step 1718, the audio cable is removed from the smart device using a servo or actuator on the custom holder on the smart plate under the control of the system controller.
At step 1902, a reference audio file is stored or resides in the memory of system controller 1870.
At step 1904, communication is established between the system controller and the smart device 1810, and also between the system controller and the robotics 1820 (e.g. stylus 1830) within the Smart Box. In one embodiment, this communication is performed using USB, Wi-Fi or any other suitable protocol. The communication, in one embodiment, can flow through USB hub 1880.
At step 1906, audio device 1850 and external Smart box microphone 1860 are controlled using the system controller.
At step 1908, the system controller is used to control the smart device and the robotics to position the smart device in an appropriate position relative to the microphone 1860.
At step 1910, a reference audio file is placed on the smart device using the system controller. At step 1912, the audio device 1850 is controlled using the system controller to start recording.
At step 1914, the smart device is controlled to play the reference audio file. Subsequently, at step 1916, the recording is stopped and the captured audio file is retrieved from the audio device 1850.
At step 1918, the retrieved audio file is compared with the reference audio file stored in the system controller memory to determine if the device passed or failed the test. In one embodiment, the POLQA library can be used to perform the file comparison and determine a pass/fail condition.
At step 2102, a reference audio file is stored or resides in the memory of system controller 2050.
At step 2104, communication is established between the system controller and the smart device 2010, and also between the system controller and the robotics 2020 (e.g. stylus 2030) within the Smart Box. In one embodiment, this communication is performed using USB, Wi-Fi or any other suitable protocol. The communication, in one embodiment, can flow through USB hub 2040.
At step 2106, audio device 2070 is controlled using the system controller.
At step 2108, the system controller is used to control the smart device and the robotics to automatically insert an audio cable 2060 into the headset/microphone jack of the smart device. In one embodiment, an audio cable can be plugged into the audio jack of the smart device automatically using commands sent from the system controller to a servo on the smart plate or custom holder.
At step 2110, a reference audio file is placed on the smart device using the system controller. At step 2112, the audio device 2050 is controlled using the system controller to start recording.
At step 2114, the smart device is controlled to play the reference audio file. Subsequently, at step 2116, the recording is stopped and the captured audio file is retrieved from the audio device 2050 and digitized.
At step 2118, the retrieved audio file is compared with the reference audio file stored in the system controller memory to determine if the device passed or failed the test. In one embodiment, the POLQA library can be used to perform the file comparison and determine a pass/fail condition.
At step 2120, the audio cable is removed from the smart device using a servo or actuator on the custom holder on the smart plate under the control of the system controller.
At step 2302, a reference audio file is stored or resides in the memory of system controller 2250.
At step 2304, communication is established between the system controller and the smart device 2220. In one embodiment, this communication is performed using USB, Wi-Fi or any other suitable protocol. The communication, in one embodiment, can flow through USB hub 2240.
At step 2306, audio device 2230 and microphone 2210 is controlled using the system controller. At step 2308, the smart device is controlled to dial a live test number.
At step 2310, the external microphone 2210 and audio device 2230 are used to listen for recorded audio transmitted from the smart device to verify that the live call was established.
At step 2312, the audio transmitted from the smart device through the microphone is captured by the audio device 2230 and delivered to the system controller.
At step 2314, the dB level of the audio is used to verify that audio is detected. In one embodiment, POLQA software can be used to verify the audio according to audio POLQA standards.
At step 2316, the retrieved audio file is compared with the reference audio file stored in the system controller memory to determine if the device passed or failed the test. In one embodiment, the POLQA library can be used to perform the file comparison and determine a pass/fail condition.
At step 2502, a reference audio file is stored or resides in the memory of system controller 2470.
At step 2504, communication is established between the system controller and the smart device 2420 and between the system controller and the robotics 2440 (e.g., stylus 2450). In one embodiment, this communication is performed using USB, Wi-Fi or any other suitable protocol. The communication, in one embodiment, can flow through USB hub 2410.
At step 2506, audio device 2430, speaker 2480, and microphone 2485 is controlled using the system controller. At step 2508, the smart device is controlled to launch an audio record application on the smart device using the system controller.
At step 2510, the external speaker in the Smart Box is controlled to play an over the air (OTA) audio signal. At step 2512, the smart device is controlled to start recording the audio signal played by the external speaker. At step 2514, the smart device is controlled to stop the recording after the audio completes and to play back the recording.
At step 2516, the external microphone 2485 is controlled to capture the playback audio onto audio device 2430 and transmitting it to the system controller. Finally, at step 2518, the retrieved audio file is compared with the reference audio file stored in the system controller memory to determine if the device passed or failed the test. In one embodiment, the POLQA library can be used to perform the file comparison and determine a pass/fail condition.
Vibration Test
At step 2702, the system controller 2640 communicates with and controls the smart device 2650. At step 2704, the external accelerometer 2685 located near the smart device is also controlled using the system controller.
At step 2706, the smart device is controlled to activate vibration mode in order to make the smart device vibrate. At step 2708, the external accelerometer is used to capture the x, y, z vibration data and signature from the vibrating smart device. In one embodiment, the accelerometer can obtain this information from the smart plate on which the smart device rests or from the custom holder into which the smart device fits. This information is transmitted back to the system controller through the USB hub.
At step 2710, the system controller analyzes the signature to determine a pass or fail condition.
The vibration feature of the phone can be tested in other ways in different embodiments. In one embodiment, the smart device's internal accelerometer data can be analyzed during vibration using the system controller. In other words, the smart device could be set on vibrate mode and metadata from the internal accelerometer on the phone while it is vibrating can be used by the system controller to determine if the vibrate feature is functioning adequately.
In a different embodiment, the vibrate mode can also be verified by analyzing the frequency of the vibration using the Smart Box audio testing capabilities. In other words, one of the audio capture devices can capture the sound of the smart device vibrating and the system controller can analyze the sound to determine if the vibrate feature is functioning adequately.
Auto-Brightness Test
At step 2902, the system controller 2840 communicates with and controls the smart device 2850. At step 2904, the external programmable LEDs 2810 is also controlled using the system controller.
At step 2906, the smart device is controlled to activate the auto-brightness mode on the smart device. At step 2908, the LEDs are turned to full brightness and the light intensity data is read from the smart device. At step 2910, the LEDs are turned off by the system controller and the light intensity data is reading using the smart device. At step 2912, the light intensity data is transmitted to the system controller and analyzed to determine a Pass/Fail condition.
In one embodiment, the same methodology as illustrated in
Bluetooth Test
At step 3102, the system controller 3040 communicates with and controls the smart device 3050. At step 3104, the Bluetooth Access Point 3010 is also controlled using the system controller.
At step 3106, the smart device is controlled to activate and deactivate the Bluetooth mode. At step 3108, Bluetooth signals are received from the Bluetooth Access point 3010 using the smart device. At step 3110, the Bluetooth scan results are read in by the system controller from the smart device.
At step 3112, the Bluetooth scan results are analyzed by the system controller to determine a Pass/Fail condition.
In one embodiment, a similar methodology to above is also used to test the Near Field Communications (NFC) functionality of the smart device.
Wi-Fi Test
At step 3302, the system controller 3240 communicates with and controls the smart device 3250. At step 3304, the Wi-Fi Access Point 3210 is also controlled using the system controller.
At step 3306, the smart device is controlled to activate and deactivate the Wi-Fi mode. At step 3308, Wi-Fi signals are received from the Wi-Fi Access point 3210 using the smart device. At step 3310, the Wi-Fi scan results are read in by the system controller from the smart device.
At step 3312, the Wi-Fi scan results are analyzed by the system controller to determine a Pass/Fail condition.
GPS Test
At step 3502, the system controller 3440 communicates with and controls the smart device 3450. At step 3504, the smart device is controlled to activate and deactivate the GPS mode on the smart device. At step 3506, the GPS and location results are read from the smart device using the system controller. At step 3508, the GPS scan and location results are analyzed by the system controller to determine a Pass/Fail condition.
Other Tests
In different embodiments, the Smart Box can be configured to test various other features of the smart device.
In one embodiment, for example, the Smart Box can be configured to test the gravity sensor on the smart device. Using the x-y-z movement capability of the Smart Box robotics, the smart device can be manipulated up/down, sideways, and rotated to verify the phone's gravity sensor.
In one embodiment, the Smart Box can be configured to test the light sensor on the smart device. Using the Smart Box integrated camera and light source, the light sensor on the smart device can be verified. For example, the light source can be used to activate or deactivate the light sensor on the smart device while the camera can be used to capture images and transmit information to the system controller, wherein the system controller can analyze the images to ensure proper functioning of the smart device.
In one embodiment, the Smart box can be configured to test the proximity sensor on the smart device. Using the x-y-z movement capability of the Smart Box robotics, an object, e.g., the stylus can be brought in close proximity with the smart device. To determine if the proximity sensor is functioning properly, the system controller will test whether the display screen deactivates when the object is brought into close proximity to the screen of the smart device and then re-activates again when the object is moved further away from the screen.
In one embodiment, the Smart Box can be configured to test the smart device's gyroscope sensor. Using the x-y-z movement capability of the Smart Box robotics and the rotation features, the smart device can be manipulated in multiple axes. The system controller can retrieve metadata from the smart device as it is being manipulated to determine the proper functionality of the gyroscope sensor.
In one embodiment, the Smart Box can be configured to test the smart device's compass. Using the x-y-z movement capability of the Smart Box robotics and the rotation features, the smart device can be rotated and the compass output can be monitored by the system controller. The system controller can retrieve metadata from the smart device as it is being rotated to determine the proper functionality of the compass.
As mentioned above, in one embodiment, the Smart Box can be configured to test the various physical buttons on the smart device. For example, either the stylus or another actuator similar to the stylus can be configured to test the smart device's volume up and down buttons, menu buttons, back buttons, and home buttons. The stylus, for example, can be used to depress or activate any physical key on the smart device. The metadata from the operation is communicated to the system controller from the smart device and/or stylus and the system controller determines if the smart device is functioning properly.
In one embodiment, the Smart Box can be configured to test the radio functionality on the smart device. The smart device can be controlled to tune the device FM chip to a station and verify that a radio signal is received. Typically, an FM generator on the production floor can be used to perform this test. The system controller is operable to tune the FM radio on the smart device to a desired frequency. Further, the audio devices in the Smart Box can be configured to capture the output of the smart device and transmit it to the system controller, which verifies that the FM audio signal is detected.
In one embodiment, the Smart Box can be used to determine the battery status and if the smart device is charging properly. For example, the Smart Box can be used to determine if the charging icon appears on the screen when power is plugged in. By way of further example, the Smart Box can also be programmed to determine the amount of charge being held by the battery and the temperature conditions. Further, one of the USB stations in the USB Hub can be configured to monitor power supply current flowing to the smart device. In one embodiment, the Smart Box has current monitoring integrated into the USB cabling that verifies the correct charging amperage being supplied to the phone.
In one embodiment, the Smart Box is operable to determine the SD card slot functionality of the smart device. For example, the Smart Box can be used to determine the ability of the smart device to test the capacity of the SD card, to read and write to the SD card, and to delete files from the SD card. In one embodiment, the Smart Box robotics can be used to automatically insert the SD card into the smart device and the system controller can then control the smart device to either read from or write to the SD card. In one embodiment, the system controller can be configured to verify the SD capacity.
In one embodiment, the system controller can be configured to retrieve all the smart device information when the smart device is plugged into the smart plate. For example, the system controller can be configured to retrieve the IMEI, the model, the make, and other data regarding the smart device when the smart device is plugged in.
In one embodiment, the Smart Box is operable to determine the SIM card functionality of the smart device. For example, the Smart Box robotics in conjunction with the system controller can be used to insert and remove the SIM card from the smart device. Further, the system controller can be used to verify that the smart device reads the SIM card successfully.
In one embodiment, the Smart Box is operable to the test the On The Go (OTG) feature on the smart device. For example, the robotics in the Smart Box may plug the OTG cable into the smart device. The system controller can then be used to verify OTG functionality.
In one embodiment, the Smart Box is operable to test the ROM on the smart device. The system controller can read from and write to the ROM to verify its functionality.
In one embodiment, the Smart Box can be integrated with a wireless charger that can be used to test the wireless charging capability of the smart device. The Smart Box robotics can place the smart device on a wireless charger and the system controller can be used to verify that the smart device is charging.
In one embodiment, the Smart Box can be used to perform fingerprint recognition. The robotic stylus can be integrated with a capacitive touch capability in order to test the fingerprint sensor on the smart device. The system controller can communicate with the stylus and the smart device to verify functionality.
In one embodiment, the Smart Box can be used to test the device pedometer. The Smart Box integrated movement capability (e.g., using the robotics) can be used to manipulate the smart device in a similar way to jogging. The system controller can read the metadata from the smart device and the pedometer to verify functionality.
In one embodiment, the audio generation and capture capabilities of the Smart Box can also be combined with the audio analysis abilities of the system controller (e.g. using QUIKSTRESS and POLQA) to verify the smart device speech recognition capability.
Testing Multiple Devices Simultaneously
In the embodiment illustrated in
Further, as discussed above, the Smart Box 3600 can also comprise an external speaker 3620, a Bluetooth Access point 3630, a microphone 3610, a LED light strip 3640, audio generating and capturing devices 3650, and a USB Hub 3680 that communicates with a system controller, e.g., laptop 3690. Laptop 3690 can run test automation software, e.g., QUIKSTRESS that can be used to control the smart devices and the components within the Smart Box 3600. In one embodiment, smart plate 3655 can be equipped with multiple custom phone holders into which the devices can be inserted for testing. In a different embodiment, a phone holder design such as the one illustrated in
In one embodiment, the multiple phones can be inserted or fitted into a daughter carrier 3750. The daughter carrier slides in and out of the mother carrier 3740. The operator can typically pre-load the multiple phones onto the daughter carrier, slide it into the mother carrier, which in turn makes the USB connections using USB ports 3760. The operator can then activate the system controller to run the tests on the smart devices at the click of a button. While the smart devices are being tested, the operator is then free to pre-load another daughter carrier and also prepare it for testing. Accordingly, this embodiment allows several phones to be tested in an efficient and speedy fashion.
Running Diagnostics Using Smart Box
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as may be suited to the particular use contemplated.
This application claims priority from U.S. Provisional Application No. 62/088,319, filed Dec. 5, 2014, the entire disclosure of which is incorporated herein by reference. The present application is related to U.S. Pat. No. 8,737,980, filed Sep. 27, 2012, entitled “End to end Application Automatic Testing,” naming Dinesh Doshi, Artun Kutchuk, Deepa Jagannatha, and Ramesh Parmar as inventors. This patent is incorporated herein by reference in its entirety and for all purposes. The present application is related to U.S. patent application Ser. No. 14/949,526, filed Nov. 23, 2015, entitled “SMART BOX FOR AUTOMATIC FEATURE TESTING OF SMART PHONES AND OTHER DEVICES,” naming Derek Dipterans, Ira Eventual, Keith Scab and Raton Ketchup as inventors. That application is incorporated herein by reference in its entirety and for all purposes. The present application is also related to U.S. patent application Ser. No. 14/949,551, filed Nov. 23, 2015, entitled “SMART BOX FOR AUTOMATIC FEATURE TESTING OF SMART PHONES AND OTHER DEVICES,” naming Derek Dipterans, Ira Eventual, Keith Scab and Raton Ketchup as inventors. That application is incorporated herein by reference in its entirety and for all purposes. The present application is further related to U.S. patent application Ser. No. 14/949,576, filed Nov. 23, 2015, entitled “SMART BOX FOR AUTOMATIC FEATURE TESTING OF SMART PHONES AND OTHER DEVICES,” naming Derek Dipterans, Ira Eventual, Keith Scab and Raton Ketchup as inventors. That application is incorporated herein by reference in its entirety and for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3082374 | Buuck | Mar 1963 | A |
| 6522995 | Conti et al. | Feb 2003 | B1 |
| 7810001 | Zhou et al. | Oct 2010 | B2 |
| 8054221 | Luong | Nov 2011 | B1 |
| 8283933 | Dasnurkar | Oct 2012 | B2 |
| 8310385 | Dasnurkar | Nov 2012 | B2 |
| 8325614 | Poon et al. | Dec 2012 | B2 |
| 8433953 | Gaudette et al. | Apr 2013 | B1 |
| 8577813 | Weiss | Nov 2013 | B2 |
| 8737980 | Doshi et al. | May 2014 | B2 |
| 8856539 | Weiss | Oct 2014 | B2 |
| 8983394 | Deforge et al. | Mar 2015 | B2 |
| 9065556 | Popescu et al. | Jun 2015 | B2 |
| 9100826 | Weiss | Aug 2015 | B2 |
| 9116873 | Majumdar et al. | Aug 2015 | B2 |
| 9185675 | Chen et al. | Nov 2015 | B2 |
| 9253242 | Macalet et al. | Feb 2016 | B2 |
| 9446519 | Gray et al. | Sep 2016 | B2 |
| 9469037 | Matthews et al. | Oct 2016 | B2 |
| 9481084 | Park | Nov 2016 | B2 |
| 9530137 | Weiss | Dec 2016 | B2 |
| 9544910 | Delsol et al. | Jan 2017 | B2 |
| 9596166 | Iyer et al. | Mar 2017 | B2 |
| 9652077 | Jenkinson | May 2017 | B2 |
| 10025883 | Paule et al. | Jul 2018 | B2 |
| 20020116507 | Manjure et al. | Aug 2002 | A1 |
| 20040012529 | Teshirogi et al. | Jan 2004 | A1 |
| 20050083068 | Clarridge et al. | Apr 2005 | A1 |
| 20070281684 | Parmar et al. | Dec 2007 | A1 |
| 20080081608 | Findikli | Apr 2008 | A1 |
| 20080263410 | Mittal et al. | Oct 2008 | A1 |
| 20080313313 | Doshi et al. | Dec 2008 | A1 |
| 20090112505 | Engel | Apr 2009 | A1 |
| 20090249284 | Antosz et al. | Oct 2009 | A1 |
| 20090265035 | Jenkinson et al. | Oct 2009 | A1 |
| 20090312009 | Fishel | Dec 2009 | A1 |
| 20100113011 | Gregg | May 2010 | A1 |
| 20100240317 | Giles | Sep 2010 | A1 |
| 20110025337 | Morrow | Feb 2011 | A1 |
| 20110151863 | Shaw et al. | Jun 2011 | A1 |
| 20110178766 | York | Jul 2011 | A1 |
| 20110293840 | Newkirk et al. | Dec 2011 | A1 |
| 20120131515 | Rice | May 2012 | A1 |
| 20120139571 | Nickel et al. | Jun 2012 | A1 |
| 20120146956 | Jenkinson | Jun 2012 | A1 |
| 20120280934 | Ha et al. | Nov 2012 | A1 |
| 20120282891 | Mohammed et al. | Nov 2012 | A1 |
| 20120300649 | Parmar et al. | Nov 2012 | A1 |
| 20130078983 | Doshi et al. | Mar 2013 | A1 |
| 20130183898 | Strid | Jul 2013 | A1 |
| 20130227348 | Stephenson et al. | Aug 2013 | A1 |
| 20130294255 | Olgaard et al. | Nov 2013 | A1 |
| 20130345864 | Park | Dec 2013 | A1 |
| 20140111484 | Welch et al. | Apr 2014 | A1 |
| 20140122009 | Meiyappan | May 2014 | A1 |
| 20140305224 | Zhang et al. | Oct 2014 | A1 |
| 20140379935 | Venkatasubramaniam et al. | Dec 2014 | A1 |
| 20140380281 | McLaughlin | Dec 2014 | A1 |
| 20150003505 | Lusted et al. | Jan 2015 | A1 |
| 20150297991 | Mahlmeister et al. | Oct 2015 | A1 |
| 20160044520 | Iyer et al. | Feb 2016 | A1 |
| 20160134737 | Pulletikurty | May 2016 | A1 |
| 20160187876 | Diperna et al. | Jun 2016 | A1 |
| 20160187877 | Diperna et al. | Jun 2016 | A1 |
| 20180048555 | Doshi et al. | Feb 2018 | A1 |
| 20180049050 | Doshi et al. | Feb 2018 | A1 |
| 20180049051 | Doshi et al. | Feb 2018 | A1 |
| 20180049052 | Doshi et al. | Feb 2018 | A1 |
| 20180049054 | Doshi et al. | Feb 2018 | A1 |
| 20180316443 | Diperna et al. | Nov 2018 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20160192213 A1 | Jun 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62088319 | Dec 2014 | US |
