SYSTEM AND METHOD FOR DIRECT DEVICE COMMUNICATION WITH DIAGNOSIS AND PROVISIONING - Patent application

Abstract

A system and method for diagnostics and provisioning of mobile devices is provided. The system communicates directly with the mobile device hardware, providing connectivity for diagnostics and other functions such as device erasure, without requiring an application to first be installed on the mobile device. In this manner, information such as detailed product identification, merchant identification, and diagnostic information can be quickly obtained from the mobile device to perform diagnostics and erasure for efficiently returning used devices to the stream of commerce.

Description

[Technical Field]

[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims the full benefit of and priority to U.S. Provisional Patent Application No. 62 / 899,616, entitled "System and Method for Direct Device Communication with Diagnostics and Provisioning," filed September 12, 2019, the disclosure of which is incorporated by reference in its entirety for all purposes.

[0002] The present application relates to a system and method for diagnosing the operational state of, and related provisioning for, mobile devices. More particularly, the system and method provide for the assessment of functionality and performance parameters, as well as the rapid and reliable erasure of information stored on such mobile devices, via a direct communication interface to mobile device components. [Background technology]

[0003] Today, mobile devices are widely used, and an increasing number of people are utilizing such devices in their daily lives. As used herein, the term "mobile device" generally refers to any electronic device capable of being moved from place to place. Examples of such mobile devices include, but are not limited to, mobile phones (more commonly known as "cell phones"), smart watches, smart jewelry, personal digital assistants (PDAs), digital cameras, intelligent devices for the "Internet of Things" ("IoT"), drone devices, mobile subscriber communication devices, tablet computers, media players, smart vehicles, laptop computers, and devices equipped with wireless intelligent agents such as Alexa®, Google Voice, Siri®, and Cortana®. Driven by the desire for improved equipment and functionality, consumers purchase millions of mobile devices, such as mobile phones, each year to replace worn-out, broken, partially functional, or slow-performing devices, or simply to acquire the latest products based on consumer loyalty or to show off new models to friends and acquaintances. Meanwhile, as newly released mobile devices are equipped with more and more features and capabilities, the prices of such devices have risen rapidly, creating a secondary market for used but still functional mobile devices, and an industry has developed to process and recycle used mobile devices, either by refurbishing and reselling them in a usable condition, or by separating inoperable devices into valuable components or scrap.

[0004] Processors of used mobile devices (also referred to herein as "recyclers") face the challenge of accepting mobile devices, such as used cell phones, whose functionality and operating condition are unknown, assessing the functional condition of such devices, securely wiping all previous user data from the cell phones, and, if necessary, performing any necessary repairs. Due to competitive market conditions and the low profit margins created by pricing recycled mobile devices, efficiency in the assessment, diagnosis, and erasure process is paramount. Recyclers must quickly assess the type of device, its operating condition, and perform any necessary reprovisioning, such as flashing and erasing, of the mobile device in the most efficient manner possible to ensure that recycled devices are returned to the stream of commerce as quickly as possible.

[0005] In traditional mobile phone recycling processes, recyclers attempt to connect mobile devices to a power / data source, such as a USB or Lightning port, and, if the device is not password-protected but is protected via Mobile Device Management (“MDM”) or a cloud-based remote activation / locking scheme, such as Find My iPhone (“FMIP”), the recycler attempts to install an application on the mobile device that can be used for diagnostics and / or device erasure. However, simply assessing the device type or device state (e.g., whether locked or subject to MDM) can be problematic for devices received in an unknown or partially operational state (and may require access to costly third-party databases to determine activation / locking status). Furthermore, installing such applications on used mobile devices is time-consuming and may be impossible if the used mobile device has a cracked / broken display or is otherwise not fully functional enough to interact with the device (e.g., to verify permission to function for downloaded applications). Additionally, some mobile devices may be delivered with fully discharged batteries, and a time-consuming battery charging process may be required to restore such discharged devices to an initial operating state before the devices can be processed through a device recycler's assessment / diagnosis / erasure process.

[0006] In addition to mobile device recyclers, retail organizations such as mobile carriers (also known as mobile telephone service providers) also face the need to quickly assess, diagnose, and / or erase mobile devices brought in by customers at retail stores or kiosks. To provide such services, carriers are sometimes faced with purchasing and configuring expensive hardware to diagnose mobile phones at each retail store or kiosk. Furthermore, even with existing test systems or data transfer hardware, carriers have had to require the mobile device to be unlocked and have a minimally functional display in order to perform diagnostics and other functions on the mobile device.

[0007] In summary, there is a need to provide a system and method for diagnosing and re-provisioning (such as reflashing or securely erasing) mobile phones and other mobile devices, among other things, without first installing an application on the device. Furthermore, what is needed is a system and method that supports the diagnosis and provisioning of mobile devices using hardware that is commonly available at retail stores. Summary of the Invention [Means for solving the problem]

[0008] The following technical disclosure is representative and is for illustrative purposes only and does not necessarily limit the claimed invention.

[0009] In one aspect, an embodiment of the present invention communicates directly with the mobile device hardware via a serial or USB-type connection, enabling relevant information to be obtained from the device without the need for an initial installation of an application on the mobile device. In various embodiments of the present invention, described more fully below, detailed product, merchant, and status information can be rapidly obtained from the mobile device even when the mobile device's display is not functioning or the mobile device's battery is discharged. Furthermore, diagnostic and certain provisioning operations can be performed by a host system connected to the mobile device without requiring the installation of an application on the mobile device. Furthermore, in various embodiments, mobile carriers can perform analysis and mobile device provisioning at a retail store without requiring the purchase of additional hardware other than a computer system configured to operate the methods of the present invention in conjunction with the interface cable described herein. At the retail store or kiosk, the mobile device can be attached to a test system via a USB cable, and a web browser configured with a plug-in can be run on the retailer / kiosk's computer or tablet to perform diagnostic testing and / or provisioning of the connected mobile device in accordance with the aspects of the present invention described herein.

[0010] In additional embodiments of the present invention, advanced analysis, diagnostics, and provisioning functions such as erasure can be performed over a serial connection established between the mobile device and the host system without requiring a user or test system to first install an application on the mobile device. Furthermore, various embodiments allow for diagnostics and provisioning of the mobile device without rooting or jailbreaking the mobile device from a factory default state.

[0011] In one implementation, the electronic system is interfaced to the mobile unit under test via a cable, such as a serial cable, or more preferably, a USB-compatible cable. In additional embodiments, the interconnecting cable may utilize an element designed to modify the voltage / current characteristics flowing between the cable and the mobile device under test to activate specific functions within the circuitry (e.g., within a chipset or controller) comprising the mobile device. In yet another embodiment, the interconnecting cable is a USB On-The-Go (OTG)-compatible cable, and the element is connected intermediate the identification (ID) and ground (GND) pins. In additional embodiments, the element has a fixed resistance. In yet another embodiment, the resistance of the element may be variable through manual techniques, such as manually adjusting a potentiometer, or through automated techniques, such as by changing the resistance via an interface to a digital potentiometer or an interface to analog semiconductor components integrated with the cable. As noted above, these embodiments utilizing an element with a fixed or variable resistance are in addition to the preferred embodiment of a standard USB cable (including with a pull-up resistor, if one is provided).

[0012] The present invention provides a method including electrically connecting a mobile device to a USB port of a host system, uniquely identifying the USB port and the type of mobile device attached to the USB port, adjusting the electrical performance of the USB port based on the identified device type and desired functionality, identifying a current state of the mobile device, establishing a serial connection between the mobile device and the host system, and performing diagnostic and device provisioning functions on the mobile device. The electrical performance of the USB port may be changed, for example, by adjusting resistance in a USB cable between the mobile device and the host system. The device state of the mobile device may be switched in response to identifying that the current device state of the mobile device is not one of a recovery mode or a download mode. In another aspect, the method further includes providing power to the mobile device via a USB cable connected between the host system and the mobile device. In yet another aspect, identifying the current state of the mobile device further includes determining a data connection type available to the mobile device. In yet another aspect, the serial connection between the mobile device and the host system includes one of a USB protocol and an RS-232 protocol. Additionally, aspects of the invention may include obtaining, from the mobile device, serial numbers of components installed on the mobile device and determining that the components are components originally installed on the mobile device. Any number and type of identifying information may be obtained for components installed in the mobile device. One embodiment includes obtaining a list of serial numbers of components installed on the mobile device and determining (e.g., via a database lookup) for each such installed component whether each respective component was originally installed when the mobile device was manufactured.Additional aspects include determining the resale value of the mobile device based at least on whether each component was originally installed at the time of manufacture of the mobile device, and in yet another embodiment, planning repairs or upgrades of the mobile device based at least on whether each component was originally installed at the time of manufacture of the mobile device.

[0013] Another embodiment of the present invention may include a system comprising a host system having a processor, a memory electrically coupled to the processor, a storage device coupled to the processor, a user interface electrically coupled to the processor, and a USB port connection coupled to the processor. The memory may further be configured with software that, when executed, performs the following steps: electrically connecting a mobile device to a USB port of the host system; uniquely identifying the USB port and the type of mobile device attached to the USB port; adjusting the electrical performance of the USB port based on the identified device type and desired functionality; identifying the current state of the mobile device; establishing a serial connection between the mobile device and the host system; and performing diagnostic and device provisioning functions on the mobile device. The electrical performance of the USB port may be changed, for example, by adjusting resistance in a USB cable between the mobile device and the host system. The device state of the mobile device may be switched in response to identifying that the current device state of the mobile device is not one of recovery mode or download mode. In another aspect, the steps performed by the system of the present invention further include providing power to the mobile device via a USB cable connected between the host system and the mobile device. In yet another aspect, identifying the current state of the mobile device further includes determining a data connection type available to the mobile device. In yet another aspect of the invention, the serial connection between the mobile device and the host system includes one of a USB protocol and an RS-232 protocol. Additionally, aspects of the invention may include obtaining, from the mobile device, a serial number of a component installed in the mobile device and determining that the component is an originally installed component of the mobile device. Any number and types of identification information may be obtained for components installed in the mobile device.One embodiment includes obtaining a list of serial numbers of components installed on the mobile device and, for each such installed component, determining (e.g., via a database lookup) whether each respective component was originally installed when the mobile device was manufactured. Additional aspects include determining a resale value of the mobile device based at least on whether each respective component was originally installed when the mobile device was manufactured, and in yet another embodiment, planning a repair or upgrade of the mobile device based at least on whether each respective component was originally installed when the mobile device was manufactured.

[0014] A more complete understanding of the present invention may be obtained by reference to the detailed description and claims when considered in conjunction with the following illustrative figures. [Brief explanation of the drawings]

[0015] [Figure 1] FIG. 1 is a schematic diagram of one embodiment of the system of the present invention. [Figure 1A] FIG. 1A is a schematic diagram of one embodiment of a system of the present invention including a resistive element electrically coupled to a serial cable of the present invention. [Figure 1B] FIG. 1B is a schematic diagram of one embodiment of the system of the present invention in which multiple mobile devices can be simultaneously serviced by a host system. [Figure 2] FIG. 2 shows an example flow diagram of steps used to implement aspects of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0016] One embodiment of the present invention can be understood in the context of FIGS. 1, 1A, 1B, and 2 as follows. System 100 (or alternatively, 100A in FIG. 1A) shown in FIG. 1 performs steps to perform diagnostics on a device under test 120 (also referred to herein as “mobile device 120”) electrically connected to a host system 105 via cable 110 (or 110A in the case of FIG. 2). Cable 110 or 110A may consist of or further include a USB cable. Cable 110, 110A, or 110B may also optionally include a customized cable to accommodate various features required for serial communication in the present invention. FIG. 1B illustrates system 100B in which multiple mobile devices 120B1-120B2 are connected via cables 110B1-110B5, respectively, to a USB hub 106 shown as part of host system 105. Those skilled in the relevant art will recognize that USB hub 106 may be internally connected within host system 105, or may be a separate component interfaced to host system 105 and then connected to mobile devices 120B1-120B5 as shown. Those skilled in the art will also recognize that while five mobile devices are shown connected to host system 105, fewer or more devices may be interfaced based on the intended size of the processing organization operating host system 105. Host system 105 may include a computing device having custom or conventional components, such as a processor, local memory such as RAM, non-volatile memory such as flash memory, long-term memory such as a hard disk or solid-state drive, a network adapter, and any number of input and / or output devices, such as a keyboard, mouse, monitor, touchscreen, microphone, speaker, motion sensor, orientation sensor, infrared sensor, temperature sensor, humidity sensor, current sensor, light sensor, voltage sensor, current sensor, a USB hub as shown in FIG. 1B, and others.In one embodiment, the host system 105 may comprise a laptop or tablet computer configured to communicate with a mobile device 120 (such as a mobile phone) via an electrical communication implemented cable 110 (such as a USB cable).

[0017] The various memories of the computing devices can readily store one or more computer instructions, such as software code and / or software programs, executable by a processor to perform the methods of the present invention. The computing devices may include processors embedded within personal computers, servers, mobile phones, smartphones, tablet computers, kiosks, handheld computers, vehicle-mounted computers, etc. Furthermore, the databases, systems, and / or components of the present technology may include any combination of databases, systems, and / or components in one or multiple locations. Each database, system, and / or component of the present technology may include any appropriate security features, such as firewalls, access codes, encryption, decryption, compression, decompression, etc.

[0018] The technology may be embodied as a method, system, device, and / or computer program product, for example, within a mobile device diagnostic and provisioning system. Accordingly, the technology may take the form of an entirely software embodiment, an entirely hardware embodiment, or an embodiment combining both software and hardware aspects. Furthermore, the technology may take the form of a computer program product on a computer-readable storage medium having computer-readable, non-transitory program code embodied in the storage medium. Any suitable computer-readable storage medium may be utilized, including any combination of hard disks, solid-state drives, CD-ROMs, flash memory, optical storage devices, magnetic storage devices, USB memory devices, any suitable transient or non-transitory memory system, and the like. The technology may include downloadable and / or cloud-based, non-downloadable computer program products and / or methods.

[0019] Software and / or software elements according to various aspects of the technology may be implemented using any programming, scripting, or computer language or standard, such as, for example, AJAX, C, C++, Java, JavaScript, FORTRAN, COBOL, assembly, binary machine code, PERL, Python, Ruby, Extensible Markup Language (XML), PHP, CSS, or other programming and / or scripting languages, whether software or firmware, or whether now known or hereafter developed. Furthermore, the technology may be used in conjunction with computing devices running any operating system, such as any version of Windows, MacOS, OS / 2, BeOS, Linux, UNIX, Symbian, RaspbianOS, OSX, tvOS, watchOS, Tizen OS, Android, iOS, AndroidWear, or other operating systems, whether now known or hereafter developed.

[0020] Additionally, the technology may employ any number of conventional techniques for data transmission, signal transmission, data processing, network control, etc. Computing devices according to various aspects of the technology may communicate with each other over one or more telecommunications networks. A telecommunications network may comprise a collection of end nodes, links, and any intermediate nodes connected to enable communication (including transmission of data) over distances between the end nodes. In some embodiments, an end node may comprise a computing device. A telecommunications network may include any suitable communications system, such as the Internet, an intranet, an extranet, a WAN, a LAN, WiFi, Bluetooth, Zigbee, Z-Wave, satellite communications, cellular radio networks, wireless networks, telephone networks, cable networks, etc. Additionally, computing devices according to various aspects of the technology may communicate over telecommunications networks using TCP / IP, HTTP, HTTPS, FTP, IPX, AppleTalk, IP-6, NetBIOS, OSI, serial communications protocols (including RS-232), and / or any number of existing or future protocols. A telecommunications network may simply be referred to as a network.

[0021] Cable 110 may comprise a USB cable having connectors compatible with version 2.0, 3.x (i.e., any desired implementation of USB3), or other industry-standard USB implementations, or any desired cable for establishing a connection with mobile device 120. Furthermore, cable 110 may incorporate an interface compatible with mobile device 120 for establishing electrical communications between host system 105 and mobile device 120. This interface may include, but is not limited to, a USB miniport, a USB microport, a Lightning port, a Thunderbolt® port, an Apple 30-pin port, a serial port, or any desired port. In various embodiments, as shown in FIG. 2 , a fixed or variable resistor 130A may be integrated into or electrically coupled to cable 110A to enable specific protocols to be invoked within the hardware of mobile device 120. In some embodiments, host system 105 may control the resistor 130A applied to cable 110A by varying a signal applied to control line 133A.

[0022] Mobile device 120 may be electrically connected to host system 105 at any convenient time, such as during step 295 shown in FIG. 2. Because mobile device 120 is powered via cable 110 (or 110A or 110B, depending on the configuration), diagnostics and provisioning can still be performed on mobile device 120 even when the battery state of mobile device 120 is in a mixed discharged state. In a preferred embodiment, no applications are installed on mobile device 120, although installing applications on mobile device 120 may be desirable if necessary to perform certain functions. However, in various embodiments of the present invention, a comprehensive set of diagnostic, provisioning, and erasure functions are implemented without requiring the installation of any applications at any step in the process.

[0023] Referring to FIG. 2 , host system 105 scans 201 the host system for available USB ports. If a USB port on host system 105 is damaged and unresponsive, this process can identify the failed port and report it to the end user of system 100. In this way, the end user can be made aware that a particular USB port is problematic, thereby reducing end user guesswork and avoiding unnecessary calls to technical support. Next, host system 105 scans 202 for any USB hubs that may be attached, since USB hubs can cause problems if not properly identified before being configured and tested. This step 202 results in avoiding data corruption and restore errors (among other failures). An embodiment of the present invention then scans 203 the host system to determine whether the host system has USB 2.0 or USB 3.x ports, since certain device types may require one USB type or the other to establish and operate a serial connection, as defined in the examples below. The host system 105 then uniquely identifies 205 which particular USB port the mobile device under test is attached to, which is particularly important when operation is set up to handle multiple mobile devices simultaneously in a manner similar to that shown in Figure 1B (multiple mobile devices 120B1-120B5 connected to the host system 105).

[0024] As a next step, the host system 105 uniquely identifies 206 all attached mobile devices that include a particular operating system, e.g., the Android® operating system. In other embodiments, all attached iOS® mobile devices may be uniquely identified. In yet other embodiments, any device having a desired type of operating system may be uniquely identified. By identifying mobile devices configured with a particular operating system configuration, subsequent processing steps can be tailored to the specific operating system requirements of each attached mobile device, allowing for large numbers of devices, even hundreds or thousands, to be processed simultaneously.

[0025] In one aspect, the electrical characteristics of each mobile device connected to the host system 105 are profiled 207, and, if necessary, the electrical performance of the USB port to which each mobile device is connected is adjusted within a desired range based on the device type and desired functionality. For example, the amount of available current flowing between the mobile device and the connected host system can be metered to ensure the mobile device receives the appropriate amperage (and the appropriate supply voltage) required by the mobile device to perform its requested function. In various embodiments, the electrical operating characteristics of a particular USB port of the present invention may be programmatically adjusted to maintain electrical parameters (e.g., amperes, volts, watts) within a desired range. Alternatively, or in addition, the resistor 130A in the USB cable 110A may be adjusted manually or via a control signal 133A provided by the host system 105A. As a further example, USB-C devices are prone to excessive power consumption, which must be programmatically controlled when handling a large number of devices at once, or when only one mobile device is connected to the host system but the port is not properly electrically coupled.

[0026] Embodiments of the present invention next identify 208 the current device / boot state of the connected mobile device 120 without interacting with the operating system installed on the mobile device 120. Such states may include, for example, a charging-only state, DFU, recovery mode, boot OS, demo mode, or other states. Depending on the current state (or mode) of the mobile device 120, various actions may be taken to switch the state of the mobile device 120, continue processing, or report to a system user. For example, if the device is in recovery mode or download mode, this step may identify the device mode and trigger software executed by the host system 105 to perform subsequent tasks without human intervention. The steps performed in this step 208 and subsequent steps may be tailored to the operating system installed on the particular mobile device 120. For example, if the mobile device 120 is an iOS®-installed device and is in device firmware update mode (“DFU”), aspects of the present invention may perform certain actions to bring the mobile device 120 out of DFU mode. Furthermore, once the mode of the mobile device 120 is identified, the wake-up state of the mobile device 120 is then determined, with this determination being made in part based on the type of device.

[0027] As an advantage over prior approaches, performing state / mode identification step 208 allows for proper identification of mobile devices previously deemed broken or malfunctioning, or that could not be identified in production-scale device recycling. As a result of this step, all available data connection types for mobile device 120 are identified for further processing. After step 208, diagnostic operations may be performed at any desired time, such as step 211A, described below.

[0028] In another aspect of the present invention, access to the connected mobile device 120 is established 209 using a serial communication protocol, such as a USB protocol or an RS-232 protocol. For certain device types, a serial connection must be established to allow devices configured with AOS, Tizen® OS, MacOS®, Windows® OS, BBOS, WindowsPhone® OS, PebbleOS, FireOS®, or Symbian® OS operating systems to interoperate with the host system 105 to perform the steps of the present invention. Those skilled in the relevant art will recognize that numerous serial protocols exist, and any desired serial protocol may be utilized for any desired purpose in implementing the present invention. In yet a further aspect, once the serial connection is established, electronic access 210 to the mobile device 120 is established, allowing the host system 105 to scan and control the mobile device 120 regardless of the operating system installed on the mobile device 120, thereby extracting data from the mobile device 120 without requiring special measures or the prior installation of applications on the mobile device 120. In the next aspect of FIG. 2, a high-level logic validation step 211 is performed to enable verification that all previous steps have been completed successfully, that data from the mobile device 120 is properly accessible, and that the mobile device 120 is ready to accept commands from the host system 105 and corresponding steps in the software executing in the application running on the host system 105.

[0029] Get initial information and pairing status

[0030] After high-level logic validation 211 is performed, aspects of the present invention corresponding to diagnostics and device provisioning may be performed 211A, or such diagnostics and device provisioning may be performed after completion of process 200 or at any other desired time relative to process 200. For example, merchant ID and product ID values ​​may first be read from mobile device 102. Data obtained from mobile device 120 via cable 110 (or 110A or 110B) must be further decoded to extract and identify product ID information. A carrier ID (i.e., an identifier for the mobile service operator provider that provided service to the mobile device) may be obtained from mobile device 120 during or after this step. Additionally, a “pairing status” determination may be obtained from mobile device 120, particularly because some mobile devices, such as smartwatches, may not be repaired or recycled unless they have previously been paired with a particular mobile device and the pairing has been removed. As part of assessing pairing status, aspects of the present invention determine what SIM card is installed in mobile device 120 and / or whether an eSIM is utilized. In this step, information from the SIM / eSIM card can be obtained and a determination can be made regarding the last valid network, from which aspects of the invention determine which SIM the device was last operating over. Knowing the carrier is valuable information to recyclers (and retailers) because a mobile device 120 may be more valuable if it was previously associated with a particular carrier.

[0031] Determine the lock state

[0032] Aspects of the present invention may also determine the lock status of mobile device 120. In various embodiments, mobile device 120 is examined to determine all possible lock states of the device, whether they are pin lock, passcode lock, mobile device management (“MDM”) lock, Find My iPhone (“FMIP”) activation lock, or other types of lock. In various embodiments, aspects of the present invention are able to diagnose and provision even when some lock states still exist on the mobile device. On the other hand, some lock states may indicate that further processing for a particular mobile device should be immediately suspended. For example, if an iOS-based mobile device is locked by an FMIP activation lock, the device may be quickly identified and testing may cease (potentially saving extensive diagnostics and lookups through third-party databases to determine FMIP status). Also, as part of this step, a determination may be made as to whether mobile device 120 has been jailbroken (in the case of iOS) or rooted (in the case of Android). In many situations, recyclers do not want to repair previously jailbroken or rooted mobile phones due to the potential for residual malware remaining on such devices. Therefore, early identification of a jailbroken and / or rooted condition can save the recycler time in performing diagnostics and erasure attempts.

[0033] Get general information from your mobile device

[0034] In yet another embodiment, general information is obtained from the mobile device and logged within the host system 105, provided the device remains accessible based on its lock state. Such general information may include, among other things, information valuable to device recyclers or retailers, such as the device's registered model number, color, product name, IMEI, operating system version number, firmware version number, serial number, memory size, rooted / jailbroken status (as described above), and carrier ID / carrier code. In one aspect, a first set of information may be obtained from an Android®-based mobile device 120 without ADB running, and a larger second set of information may be obtained if ADB is launched on the mobile device 120 in accordance with embodiments of the present invention. In another aspect, a complete identification of over 20,000 parameters on an iOS®-based mobile device may be obtained in accordance with embodiments of the present invention, without first installing an application on the iOS®-based mobile device. Once obtained from the mobile device 120 by the host system 105, the general information is stored for presentation to the end user or for use in further processing certain diagnostic or provisioning steps.

[0035] Automatic diagnosis extraction and identification

[0036] Many types of mobile devices perform periodic internal diagnostics and store the results of those diagnostics within the mobile device in various ways, including in diagnostic logs. These “auto-diagnostic” test result logs are typically inaccessible to end users and may be difficult to understand in their encoded format, but once read and decoded, contain information that can quickly indicate the functional status of the mobile device to a device recycler or end user. Furthermore, such information can indicate components that require repair or adjustment, thereby guiding the recycler's refurbishment plan. In various aspects of the present invention, information obtained from logs stored within mobile device 120 is retrieved and decoded by host system 105, and these logs are utilized to determine whether various features of mobile device 120 are operating within normal parameters based on expected operating criteria stored within the mobile device's 120 operating system.

[0037] For embodiments in which the iOS® operating system is installed on the mobile device 120, a list of device “entitlements” is obtained by the host system 105 from the firmware of the mobile device 120, which “entitlements” provide a list of information, features, and commands that a particular mobile device 120 may be instructed to perform or report. In this manner, a list of potential capabilities is determined by examining the firmware of the mobile device 120, thereby providing a ready set of diagnostic and provisioning functions for use by the mobile device. By analyzing the list of possible commands and reports available for a particular mobile device 120, efficiency in the diagnostic process is achieved by limiting operations and information gathering to available functions and reports based on the specific configuration of the mobile device 120. In various embodiments, data can be extracted, decoded, and decompiled based on certain mapping information obtained from the firmware of the mobile device 120. Such extracted and decoded information can identify acceptable diagnostic ranges of device performance, enabling the configuration of diagnostic software. Without such information, diagnostic testers often must make guesses at acceptable performance value ranges, potentially resulting in incomplete or non-comprehensive device testing. Additionally, efficiency for recyclers and retailers is improved by early identification of "hard stop" conditions, such as a power-lock condition, that renders the device 120 inaccessible for further diagnostics, provisioning, or recycling.

[0038] Depending on the device type / operating system type, certain custom actions may be performed by aspects of the present invention. For example, in the case of an Android®-based device 120, certain diagnostic information and commands may optionally be obtained and / or executed by invoking the Android® Debug Bridge (“ADB”) via commands sent from the host system 105 over a serial connection between the host system 105 and the mobile device 120 (e.g., via cable 110), allowing operating system-based information to be obtained and commands to be executed on the mobile device 120 without the need to install an application on the mobile device 120. In various embodiments described below, the ADB may be manually invoked by a user of the host system 105, or for certain types of mobile devices 120, the ADB may be autonomously invoked by software on the host system 105.

[0039] Device provisioning

[0040] Commands can be executed against the mobile device 120 to prepare it for resale or reuse, or otherwise process it for ultimate disposal. One such function can include device erasure, which can be accomplished by invoking a built-in erasure algorithm utilized by the operating system to completely erase the mobile device. In traditional approaches, a recycler or retailer typically installs an application on the mobile device 120 to perform the erasure, but this process can be extremely time-consuming compared to a native device erasure initiated by the host system 105 via the host system's interface to the mobile device 120. Erasure of the mobile device 120 can be authenticated by any desired technique, such as fingerprinting the mobile device's memory, invoking the device's native erasure software, causing the erasure to occur, and then re-pairing the mobile device 120 with the host system 105 and verifying that the fingerprinted memory is no longer present in the mobile device 120.

[0041] Presenting diagnostic data

[0042] The information obtained from the mobile device 120 is processed and presented, for example, via a user interface, to an operator of the host system 105. In various embodiments, the operator of the host system 105 can select how much information is presented, in what arrangement, and in what particular content and order.

[0043] The above-described process steps of the present invention may be performed directly, partially, or after the illustrated process 200 has terminated 212. Prior to termination 212, various aspects of the present invention may perform a device data cleanup process 212 to quickly and administratively clean up the host system 105 to remove unnecessary data, logs, or information. This process 212 may be performed after each completion of mobile device processing or at the end of a batch device processing session.

[0044] Embodiments of the Invention: Feature Set 1

[0045] As described above, various diagnostic functions and provisioning processes can be performed on the mobile device 120. In a first aspect, the set of features provided by embodiments of the present invention includes, but is not limited to, the following six features:

[0046] 1. Serial Connection for Advanced Diagnostics and Provisioning: In one aspect of the present invention, a serial connection is established between the host system 105 and the mobile device 120, which provides a mechanism for low-level access to hardware components and firmware. Establishing such a serial connection allows access to a rich set of device diagnostic information and built-in commands on the mobile device without first requiring the installation of an application on the mobile device.

[0047] 2. DFU Eraser Implementation: For iOS®-based devices, an improved erasure process can be invoked by the host system 105 commanding the mobile device 120 to enter DFU mode and invoking an erasure algorithm on the mobile device 120. Such an erasure provides a faster, more thorough mode of erasure, which may then pair the mobile device 120 and search registry events to determine if there is a recorded “delete” event, and the results of the erasure validation may be presented in an erasure certificate uniquely associated with the particular mobile device 120 that was erased.

[0048] 3. MDM Detection: Aspects of the present invention provide Mobile Device Management (“MDM”) detection that allows for early identification of devices that may have an MDM lock enabled. If such devices are in an inaccessible or other non-reconfigurable mode, early identification of the MDM mode allows for quick completion of diagnostic testing and identifies devices for reprocessing, saving recyclers time and improving efficiency.

[0049] 4. eSIM Erasure: Mobile devices (particularly those using the iOS® operating system) are increasingly incorporating embedded subscriber information modules for network authentication. Aspects of the present invention enable the host system 105 to instruct the mobile device 120 to initiate an eSIM (or alternatively, a SIM) erasure, configuring the device for use by a new purchaser and removing the previous user's information (and potentially personally identifiable information, or "PII") from the mobile device 120 before the mobile device 120 is returned to the stream of commerce.

[0050] 5. Skip iOS® UI Setup: Some mobile devices, particularly those utilizing the iOS® operating system, require that an application be “trusted” via user input before certain functions, such as installing and launching an application on the mobile device, can be performed. To provide such trust input, the mobile device 120 typically must be accessible to the user. Furthermore, on newly configured / flashed devices, the setup process is often lengthy, requiring user input of information such as Wi-Fi authentication, region of operation, and user trust input. In various embodiments of the present invention, the host system 105, via its connection to the mobile device 120, saves significant time during the diagnostic and provisioning process by providing functionality to skip the typical iOS® UI setup process on the mobile device 120, thereby allowing further operations, such as trusting an application, to be performed with minimal delay.

[0051] 6. Serial Component Identification and OEM Component Configuration: Embodiments of the present invention, via the host system 105's connection to the mobile device 120, enable the host system 105 to obtain a list of the serial numbers of components installed on the mobile device 120 and determine via a database lookup whether such components are original OEM components or aftermarket components installed after initial manufacture. This information enables mobile recyclers to more accurately determine the value of devices for resale, particularly iOS®-configured devices, and to plan for any necessary upgrades or repairs to components currently installed on the mobile device 120. Along with the serial component identification, a carrier ID may also be obtained and verified for a particular mobile device 120.

[0052] Embodiments of the Invention: Feature Set 2

[0053] As described above, various diagnostic functions and provisioning processes can be performed on the mobile device 120. In a second aspect, the feature set provided by embodiments of the present invention includes, but is not limited to, the following four features:

[0054] 1. Android® Fast Erase with Validation: For Android®-configured mobile devices, in embodiments of the present invention, “native” Android® commands are executed remotely by first invoking the mobile device's ADB mode of operation via user input. By executing erasure algorithms already present on the mobile device 120, the erasure process completes much faster than previous processes that required first installing an application on the mobile device 120. Connectivity between the host system 105 and the mobile device 120 is maintained during the erasure, and after the erasure is complete, the storage on the mobile device 120 is read by the host system 105 to verify whether the erasure was successful. In embodiments of the present invention, upon determining that the erasure was successful, an erasure certificate uniquely associated with the mobile device 120 can be generated to verify the erasure to the next user of the mobile device 120.

[0055] 2. Automatic ADB Quick Erase with Validation: Similar to the Android® Quick Erase with Validation described above, aspects of the present invention first launch the Android® Debug Bridge without user input, thereby allowing the mobile device 120's native erasure tools to erase data from the mobile device 120. For devices that support this option, this embodiment provides a more efficient approach because it does not require the user to manually launch ADB before running the native erasure algorithm on the mobile device 120. As above, after the erasure is complete, the host system 105 reads storage on the mobile device 120 to verify whether the erasure was successful. In embodiments of the present invention, upon determining that the erasure was successful, an erasure certificate uniquely associated with the mobile device 120 can be generated to verify the erasure to the next user of the mobile device 120.

[0056] 3. Extracting Device Configuration Fingerprints: In various situations, it may be useful for a particular recycler, mobile carrier, or other entity to understand the exact configuration of hardware and software installed on a particular mobile device. In embodiments of the present invention, the connection between the host system 105 and the mobile device 120 is utilized to generate a comprehensive manifest, or “fingerprint,” of the mobile device hardware and software. This configuration manifest / fingerprint can then be compared, for example, to a desired “golden” manifest to determine whether the mobile device complies with the minimum standards required to operate within a particular network or to determine whether the device meets other minimum functional performance metrics. In various embodiments, core device details and information can be obtained without first installing an application on the mobile device 120.

[0057] 4. Android® Diagnostics: In various embodiments, automated diagnostics similar to those described above are first performed on Android® devices, while rapid diagnostics can be performed on mobile device 120 by host system 105 regardless of whether applications have been installed on mobile device 120 first.

[0058] Embodiments of the present invention: Feature Set 3

[0059] As noted above, various diagnostic functions and provisioning processes can be performed on the mobile device 120. In a third aspect, a set of features provided by embodiments of the present invention includes, but is not limited to, the following two features:

[0060] 1. Automatically Enabling Android® Debug Bridge (ADB) Mode for Certain Devices: In various embodiments of the present invention, some mobile device types can be instructed by the host system 105 to automatically enable ADB mode to support advanced diagnostic and provisioning capabilities without user intervention. By providing quick access to ADB enablement functionality, aspects of the present invention significantly streamline the diagnostic process by allowing diagnostic and provisioning functions to occur with minimal or no user intervention and without first installing an application on the mobile device.

[0061] 2. Apple Watch® Error Indicator Mitigation: When an error occurs, such as during an Apple Watch® update, the watch's operating system may display a red exclamation point; in this mode, the watch is unable to continue normal operation. For mobile device recyclers, this error condition previously represented a hard stop in the recycling process, with the watch typically being disassembled or discarded. In various aspects of the invention, an Apple Watch® displaying a red exclamation point is interfaced to a connection fixture that connects to a test system, such as host system 105, which, in embodiments of the invention, can clear the red exclamation point error state and perform functions on the mobile watch, such as reading the watch's memory to determine if data was previously stored in the watch, and obtaining diagnostic information about watch components, such as the watch's crown or battery.

[0062] The specific implementations shown and described herein are illustrative of the present invention and its best mode and are not otherwise intended to limit the scope of the present invention in any way. Indeed, for the sake of brevity, conventional data storage, data transmission, and other functional aspects of the system may not be described in detail. The methods shown in the various figures may include more, fewer, or other steps. Moreover, steps may occur in any suitable order without departing from the scope of the invention. Furthermore, the connecting lines shown in the various figures are intended to represent typical functional relationships and / or physical couplings of the various components. Many alternative or additional functional relationships or physical connections may exist in a practical system.

[0063] Changes and variations may be made to the disclosed embodiments without departing from the scope of the invention. These and other changes or variations are intended to be included within the scope of the present invention, as expressed in the following claims, which represent non-limiting embodiments of the invention.

Claims

1. electrically connecting the mobile device to a USB port of a host system; uniquely identifying the USB port and the device type of the mobile device attached to the USB port; adjusting the electrical performance of the USB port based on the identified device type and the particular function to be activated; identifying a current device state of the mobile device; establishing a serial connection between the mobile device and the host system; performing diagnostic and device provisioning functions on the mobile device; Obtaining a list of serial numbers of components installed on the mobile device; For each of the installed components, determining whether the respective component was originally installed during manufacture of the mobile device; A method comprising:

2. 10. The method of claim 1, wherein the method includes, in response to identifying that a current device state of the mobile device is not one of a recovery mode or a download mode, switching the device state of the mobile device from the identified device state to an operational device state.

3. 10. The method of claim 1, further comprising providing power to the mobile device via a USB cable connected between the host system and the mobile device.

4. 10. The method of claim 1, wherein identifying a current device state of the mobile device further comprises determining a data connection type available to the mobile device.

5. 10. The method of claim 1, wherein the serial connection between the mobile device and the host system includes one of a USB protocol and an RS-232 protocol.

6. 10. The method of claim 1, further comprising determining a resale value of the mobile device based at least on whether each component was originally installed at the time of manufacture of the mobile device.

7. 10. The method of claim 1, further comprising: scheduling repairs or upgrades to the mobile device based at least on whether each component was originally installed when the mobile device was manufactured.

8. 1. A system comprising a host system having a processor, a memory electrically coupled to the processor, a storage device coupled to the processor, a user interface electrically coupled to the processor, and a USB port connection coupled to the processor, the memory further configured with software that, when executed, electrically connecting a mobile device to a USB port of the host system; uniquely identifying the USB port and the device type of the mobile device attached to the USB port; adjusting the electrical performance of the USB port based on the identified device type and the particular function to be activated; identifying a current device state of the mobile device; establishing a serial connection between the mobile device and the host system; performing diagnostic and device provisioning functions on the mobile device; obtaining a list of serial numbers of components installed on the mobile device; For each of the installed components, determining whether the respective component was originally installed during manufacture of the mobile device; A system characterized by:

9. 10. The system of claim 8, wherein the system includes, in response to identifying that a current device state of the mobile device is not one of a recovery mode or a download mode, switching a device state of the mobile device from the identified device state to an operational device state.

10. 10. The system of claim 8, further comprising providing power to the mobile device via a USB cable connected between the host system and the mobile device.

11. 10. The system of claim 8, wherein identifying a current device state of the mobile device further comprises determining a data connection type available to the mobile device.

12. 10. The system of claim 8, wherein the serial connection between the mobile device and the host system includes one of a USB protocol and an RS-232 protocol.

13. 10. The system of claim 8, further comprising determining a resale value of the mobile device based at least on whether each component was originally installed at the time of manufacture of the mobile device.

14. 10. The system of claim 8, further comprising: scheduling repairs or upgrades for the mobile device based at least on whether each component was originally installed when the mobile device was manufactured.

Images