Remote diagnostics of computing equipment
Through the remote diagnostic system, users can submit diagnostic information and feedback through devices such as laptops without directly accessing the game console, and remote servers can analyze and remediate it, solving the complicated and low submission of diagnostic information in the existing technology. Effective problems improve the efficiency of troubleshooting and user experience.
Patent Information
- Application Number
- CN202080010126.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-01-26
- Filing Date
- 2020-01-04
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2040-01-04
AI Technical Summary
Existing computing device diagnostic programs are cumbersome and inefficient when submitting diagnostic information and feedback, especially when users cannot access the game console, resulting in a lack of diagnostic information that may prevent error corrections and remediation and affect the user experience.
It provides a remote diagnostic system, allowing users to upload feedback information by registering multiple computing devices, using laptops and other devices, and remote servers collect and analyze diagnostic information, combine user feedback and device data to generate diagnostic records, and automatically execute remedial measures.
It enables users to effectively submit feedback and diagnostic information from other computing devices, simplifies the diagnostic process, reduces the negative impact of user experience, and improves the efficiency and accuracy of troubleshooting.
Smart Images

Figure CN113330425B_ABST
Abstract
Description
Background Art
[0001] Diagnostics of computing devices generally involve determining the operating condition or state of software, hardware, firmware, or other types of components of computing devices. Diagnostic programs can often facilitate diagnostic capabilities of computing devices. For example, during normal boot-up of a desktop computer, a basic input / output system ("BIOS") embedded power-on self-test ("POST") program can be automatically executed to verify the integrity of hardware components in the desktop computer before allowing deployment of an operating system. In another example, diagnostic programs can also be executed on demand to determine the root cause of, for example, when a computing device fails. Summary of the invention
[0002] This Summary is provided to introduce some concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
[0003] Although diagnostic programs can provide diagnostic information for solving operational problems of computing devices, submitting diagnostic information and corresponding descriptions can sometimes be cumbersome and inefficient. For example, a user may have multiple computing devices, such as smart phones, laptop computers, desktop computers, game consoles, smart TVs, etc. For example, when a user experiences a problem on a game console, a diagnostic program on the game console can be executed by the user to generate diagnostic information. The generated diagnostic information can then be submitted to technical support or other suitable entities for troubleshooting. However, using the soft keyboard on the game console to enter a description or feedback of the operational problem experienced can be cumbersome and inefficient. Similarly, in some cases, the user may not be able to access the game console when writing a description or feedback. Therefore, even if the user can easily type feedback on, for example, a laptop computer and submit the feedback from the laptop computer to technical support, the user may not be able to submit diagnostic information of the game console from the laptop computer. Therefore, the difficulty of submitting feedback and diagnostic information above may prevent the user from submitting anything. The lack of submitted diagnostic information can cause delays in error correction or other appropriate remedies for the operational problem experienced, and therefore can have a negative impact on the user experience of the computing device.
[0004] Several embodiments of the disclosed technology are directed to implementing a diagnostic system on a remote server to allow user-initiated collection of diagnostic information from computing devices by using different computing devices. In some embodiments, the diagnostic system may include a software application that is configured to allow a user to register multiple computing devices corresponding to a user account. Thus, in the above example, a user may use a user account to register one or more of a smartphone, a laptop, a desktop computer, a game console, and a smart TV.
[0005] The user can then initiate a feedback process about a registered computing device in the registered computing devices by using another registered computing device in the registered computing devices. For example, in the above example, the user can log in to the user account via a laptop computer using a suitable certificate. In response, the diagnostic system can be configured to transmit and draw all registered computing devices on the user interface of the laptop computer when authenticating the user based on the certificate. The diagnostic system can then be configured to provide the user with an option to select a computing device in the registered computing devices, such as a game console, for providing feedback. For example, the diagnostic system can be configured to provide an input field for a text of a description or feedback of an operational problem of a game console received from the user. The user can use the user interface on the laptop computer to write a description, and then transmit the description in the feedback package related to the game console to the diagnostic system at the remote server via a computer network (e.g., the Internet).
[0006] In some implementations, the feedback package may include data representing a user identity (e.g., a user login name, a user email, etc.), a description from the user received from an input field, and a device identity (e.g., a serial number of a game console). In other implementations, the feedback package may also include data representing credentials for remotely accessing the game console, such as passwords, access codes, etc. In further implementations, the user may provide such credentials and / or other suitable device information during device registration or at other suitable times. Data representing such device information may then be stored on a remote server or other suitable storage location accessible by the diagnostic system.
[0007] When receiving the feedback packet, the diagnostic system can be configured to parse the feedback packet and determine that the feedback packet received from the laptop computer is actually for the game console. In response, the diagnostic system can be configured to issue a remote command to the game console to perform one or more diagnostic programs on the game console. In some implementations, the diagnostic system can be configured to analyze the submitted description and / or other suitable information to determine which areas or components of the game console are to be tested. For example, when the description indicates that the game console cannot be started, the diagnostic system can be configured to test one or more of the BIOS, operating system, power supply or other suitable hardware / software components of the game console. In another example, when the description indicates that the game console does not have a network connection, the diagnostic system can be configured to test one or more of the network interface card (" NIC"), NIC driver and / or other suitable network components of the game console.
[0008] When the execution of the diagnostic program on the game console is completed, the diagnostic system can be configured to retrieve or otherwise receive the appropriate diagnostic information generated during the execution of the diagnostic program from the game console. The diagnostic system can then be configured to combine or aggregate the description received from the laptop computer and the diagnostic information from the game console into a database record (referred to herein as a "diagnostic record"). In some embodiments, the diagnostic system can also receive metadata about the time when the user, various computing devices and / or feedback are archived, and connect these metadata with the diagnostic information from the game console. The diagnostic system can then store the diagnostic record in a database together with the data representing the combined description and diagnostic information for further processing, record keeping and / or other suitable purposes.
[0009] In certain embodiments, the diagnostic system can also configure or program the game console for additional diagnosis and / or other relevant information.For example, the diagnostic system can be configured to program the game console to prompt the user to provide additional diagnostic information, screenshots or other suitable data when the user subsequently accesses the game console.In other embodiments, the diagnostic system can also be configured to analyze the description in conjunction with the retrieved diagnostic information to determine the root cause of the reported game console problem and automatically apply remedial action to the game console.For example, the diagnostic system can be configured to analyze feedback and diagnostic information and determine that the operating system on the game console has collapsed.In response, the diagnostic system can be configured to issue a restart command that causes the game console to restart.In another example, the diagnostic system can be configured to determine that the network interface card on the game console has failed.In response, the diagnostic system can be configured to provide a message for replacing the network interface card on the game console to the user.
[0010] Therefore, several embodiments of the disclosed technology can allow for the effective submission of feedback from a first computing device while allowing remote diagnostic information collection from a second computing device. Unlike other diagnostic systems, user feedback on problems with a second computing device can be submitted using a first computing device. The first computing device may include hardware / software components that facilitate prepared input from a user, for example, via typing, voice recognition, or other suitable input technologies. Upon receiving user feedback from the first computing device, a diagnostic system at a remote server can trigger remote collection of diagnostic information for the second computing device. The diagnostic information collected from the second computing device can then be aggregated or "aligned" with the feedback received from the first computing device as a diagnostic record of the problem reported by the second computing device. Therefore, even when the user does not have physical access to the second computing device, technical problems on the second computing device can be easily submitted, diagnosed, and / or remedied. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] Figure 1A-1E is a schematic diagram of a computing system that implements remote diagnostics of computing devices in a distributed computing system during certain stages of operation in accordance with an embodiment of the disclosed technology.
[0012] Figure 2 An embodiment of the disclosed technology is shown. Figures 1A to 1E A schematic diagram of certain hardware / software components of a collection engine of a computing system.
[0013] Figure 3 A schematic diagram illustrating an example schema for diagnostic logging according to an embodiment of the disclosed technology.
[0014] Figure 4A and Figure 4B A flow chart illustrating a remote diagnostic process for a computing device according to an embodiment of the disclosed technology is shown.
[0015] Figure 5 Is applicable to Figure 1A-1E A computing device that is a component of a distributed computing system. DETAILED DESCRIPTION
[0016] Certain embodiments of computing systems, devices, components, modules, routines, and processes for remote diagnosis of computing devices in a computing system are described below. In the following description, specific details of the components are included to provide a thorough understanding of certain embodiments of the disclosed technology. Those skilled in the relevant art will also understand that the disclosed technology may have additional embodiments or may be used without the following references. Figure 1A-Figure 5 The described embodiments are practiced in the context of several details.
[0017] As used herein, "diagnosis" generally refers to the practice or technology of determining the current status or state of the hardware / software components of a computing device. A "diagnostic command" generally refers to a computing command configured to trigger the execution of a diagnostic program on a computing device. For example, a diagnostic command can be the file name (or a portion thereof) of a corresponding diagnostic program. The diagnostic program can be configured to perform a series of operations that test the functionality of the hardware / software components of a computing device. An example diagnostic program is a BIOS embedded power-on self-test program. The execution of the diagnostic program can generate diagnostic information having data representing the current status or state of the hardware / software components of a computing device.
[0018] Submitting diagnostic information with corresponding descriptions from certain computing devices can be cumbersome and inefficient. For example, using a soft keyboard on a game console to enter a description or feedback of an operational problem can be cumbersome and inefficient. Likewise, in some cases, a user may not have access to the game console when writing a description or feedback. Therefore, even if a user can easily type feedback on, for example, a laptop computer, the user may not be able to submit diagnostic information for the game console from the laptop computer. Therefore, submitting feedback and diagnostic information can be difficult. This difficulty can prevent the user from submitting anything. The lack of submitted diagnostic information can cause delays in error correction or other appropriate remedies for experienced operational problems, and can therefore have a negative impact on the user experience of the computing device.
[0019] Several embodiments of the disclosed technology are directed to implementing a diagnostic system on a remote server to allow for user-initiated collection of diagnostic information from computing devices by using different computing devices. In certain embodiments, the diagnostic system may allow a user to select a computing device from a plurality of registered computing devices and provide descriptions or feedback on operational issues on the different computing devices. The diagnostic system on the remote server may then be configured to remotely trigger the execution of a diagnostic program on the selected computing device and receive diagnostic information. The diagnostic system may then combine or align the received diagnostic information from the selected computing device and descriptions from other computing devices into a diagnostic record for further processing. In this way, a user may effectively and easily submit feedback on operational issues of a selected computing device from other computing devices, as described below with reference to Figure 1A-Figure 5 Described in more detail.
[0020] Figure 1A-1E is a schematic diagram of a computing system that implements remote diagnostics of computing devices in a distributed computing system during certain stages of operation in accordance with an embodiment of the disclosed technology. Figure 1A-1EIn other figures of this article, each software component, object, class, module and routine can be a computer program, step or process written in source code with C, C++, C#, Java and / or other suitable programming languages. Components can include but are not limited to one or more modules, objects, classes, routines, attributes, processes, threads, executable files, libraries or other components. Components can be source code or binary form. Components can include source code aspects (e.g., classes, attributes, steps, routines) before compilation, compiled binary units (e.g., libraries, executable files), or artificial products (e.g., objects, processes, threads) that are instantiated and used at runtime. In certain embodiments, the various components and modules described below can be implemented with actors. In other embodiments, the generation of applications and / or related services can also be implemented using monolithic applications, multi-layer applications or other suitable components.
[0021] Components within the system can take different forms within the system. As an example, a system including a first component, a second component, and a third component can include, but is not limited to, a system including a first component having an attribute as a source code, a second component as a binary compiled library, and a third component as a thread created at runtime. A computer program, step, or process can be compiled into an object, an intermediate code, or a machine code and presented for execution by one or more processors of a personal computer, a network server, a laptop computer, a smart phone, and / or other suitable computing devices. Similarly, a component can include a hardware circuit.
[0022] Those of ordinary skill in the art will recognize that hardware can be thought of as petrified software, and software can be thought of as liquefied hardware. As just one example, the software instructions in a component can be burned into a programmable logic array circuit, or can be designed as a hardware circuit with an appropriate integrated circuit. Likewise, hardware can be emulated by software. Various implementations of source code, intermediate code, and / or object code and related data can be stored in a computer memory, which includes a read-only memory, a random access memory, a magnetic disk storage medium, an optical storage medium, a flash memory device, and / or other suitable computer-readable storage medium that does not include a propagating signal.
[0023] like Figure 1A As shown, the distributed computing system 100 may include a computer network 104 interconnecting a plurality of client devices 102 (respectively shown as first, second, third, and fourth client devices 102a-102d) of corresponding users 101 and one or more remote servers (referred to herein as "remote servers 106" for brevity) interconnected to a data repository 108. Although specific components of the distributed computing system 100 are described in detail in detail, the distributed computing system 100 may be described in detail in detail. Figure 1A, but in other embodiments, the distributed computing system 100 may also include additional and / or different components. For example, in addition to or in place of Figure 1A , distributed computing system 100 may include additional network storage devices, utility infrastructure, and / or other suitable components.
[0024] The computer network 104 may include an intranet, a wide area network, the Internet, or other suitable types of networks. In some implementations, the computer network 104 may include one or more physical network devices that interconnect the client devices 102 and the remote servers 106. Examples of such physical network devices may include network routers, switches, firewalls, load balancers, or other suitable network components that are operably coupled in a hierarchical, flat, "mesh" or other suitable topology. In other embodiments, the computer network 104 may include the Internet.
[0025] Remote server 106 can be configured to host and provide access to diagnostic system 150 (described later) for user 101 and other users (not shown) via computer network 104. In some embodiments, remote server 106 may include one or more physical servers located in a data center. In other embodiments, remote server 106 may include one or more virtual machines, containers or other suitable virtualized computing components hosted on one or more physical servers. In further embodiments, remote server 106 may include other suitable types of computing facilities.
[0026] The client devices 102 may each include a computing device that facilitates user 101 to access the diagnostic system 150 hosted and provided on the remote server 106 via the computer network 104. For example, in the illustrated embodiment, the client devices 102 include a desktop computer 102a, a game console 102b, a laptop computer 102c, and a smart phone 102d. In other embodiments, the client devices 102 may also include a smart TV, a tablet computer, and / or other suitable computing devices. Although for illustration purposes only, the client devices 102 are not shown in FIG. Figure 1A Only one user 101 is shown in FIG. 1 , but in other embodiments, the distributed computing system 100 may facilitate any suitable number of users 101 accessing the diagnostic system 150 provided by the server 106 .
[0027] In some embodiments, user 101 may register client devices 102 to correspond to a user account at diagnostic system 150. For example, user 101 may create a user account at diagnostic system 150 and add various client devices 102 as client devices 102 of user 101. In other examples, client devices 102 may be registered to user 101 when, for example, user 101 activates the client device through the user account. In further examples, user 101 may not register one or more client devices 102, but rather provide access to one or more client devices 102 for remote collection of diagnostic information on an ad hoc basis, as described in more detail below.
[0028] One or more of the client devices 102 may be configured to provide a user interface 120 that easily facilitates user input of descriptions of operational issues or feedback associated with another client device 102. For example, Figure 1A As shown, a first client device 102a (e.g., a desktop computer) may execute appropriate instructions to provide a web browser 120, which is configured to provide a web page 121 as a user interface for receiving a description or feedback of another client device 102 of the user 101. In the illustrated example, the web page 121 may include an address bar 122 containing a web address (e.g., "www.feedback.com") and a body portion 123 containing the content of the web page 121. In the illustrated implementation, the web page 121 may provide a login page to the user 101. The login page may include input fields 125 for a user name (e.g., "John Wick") and a password (e.g., "*****"), and a login button 125'. Upon receiving actuation of the login button 125' (as represented by a cursor 126), the first client device 102a may be configured to transmit the received login data 160 to the diagnostic system 150 for further processing.
[0029] like Figure 1A As shown, the diagnostic system 150 may include an authenticator 152, a collection engine 154, a record processor 156, and an optional remediation controller 158 that are operably coupled to each other. Figure 1A Specific components of the diagnostic system 150 are shown in FIG. 1 , and in other embodiments, in addition to or in place of Figure 1A In addition to the components shown in , the diagnostic system 150 may also include interfaces, input / output, network services, and / or other suitable types of components. In further embodiments, Figure 1AOne or more of the components shown in FIG. 1 may be hosted on other servers (not shown) instead of the remote server 106. For example, in some implementations, the remediation controller 158 may be hosted and provided by a remediation server (not shown) instead of the remote server 106.
[0030] Authenticator 152 may be configured to authenticate user 101 as corresponding to a user account based on received login data 160. Upon authenticating user 101, authenticator 152 may allow other components of diagnostic system 150 to provide additional services to user 101. In the illustrated embodiment, authenticator 152 is configured to authenticate user 101 based on a password received from user 101. In other embodiments, authenticator 152 may also be configured to authenticate user 101 using a multi-operation authentication technique or other suitable technique. In further embodiments, authenticator 152 may be omitted from diagnostic system 150 and instead hosted on or provided by an authentication server or service, such as Active Directory authentication provided by Microsoft Corporation of Redmond, Washington. Serve.
[0031] Upon authenticating user 101, in some embodiments, authenticator 152 may indicate to collection engine 154 that user 101 has been authenticated to the corresponding user account. In response, collection engine 154 may be configured to retrieve appropriate device information 111 from data repository 108. In some embodiments, device information 111 may include data representing a list of client devices 102 that have been registered to the user account. Collection engine 154 may then transmit the list of client devices 102 to first client device 102a for presentation to user 101. For example, Figure 1B As shown, web page 121 may output a list of client devices 102 as "John's desktop computer," "John's laptop computer," "John's phone," and "game console." Web page 121 may also provide interface elements, such as Figure 1B The selection button 127 is shown for selecting one or more of the client devices 102 listed for providing feedback. In the illustrated example, "Game Console" is selected (as indicated by the cursor 126'). In other embodiments, the collection engine 154 can be configured to query the user 101 for identifying one of the client devices 102 for providing feedback (e.g., the second client device 102b).
[0032] like Figure 1CAs shown, when a user selection of “Game Console” is received on web page 121, web page 121 may be configured to provide another input field 128 for receiving a description or feedback of one or more operational issues of the selected client device. In the illustrated example, a second client device 102b, i.e., “Game Console,” is selected. Thus, user 101 may then type or otherwise enter a brief description in input field 128, i.e., “The game console won’t even start. I checked the power cord. It’s plugged in and has power. Please help.” Upon completion of entering the description, user 101 may actuate submit button 129 (as indicated by cursor 126”) to transmit feedback package 162 to collection engine 154 via computer network 104.
[0033] In some implementations, the feedback package 162 may include data representing the user identity of the user 101 (e.g., user login name, user email, etc.), the description of the input field 128 received from the user 101, and the device identity (e.g., the serial number of a "game console"). In other implementations, the feedback package 162 may also include data representing credentials for remote access to the selected client device 102d, such as a password, access code (passcode), etc. In further implementations, the user 101 may provide such credentials and / or other suitable device information during device registration or other suitable time. The data representing such device information may then be stored on the remote server 106, the data storage device 108, or other suitable storage location accessible by the diagnostic system 150.
[0034] Upon receiving the feedback packet 162, the collection engine 154 may be configured to parse the feedback packet 162 and determine that the feedback packet 162 received from the first client device 102a (i.e., a desktop computer) is intended for the second client device 102b (i.e., a gaming console). This determination may be based on a device identity, description, or other suitable information included in the feedback packet 162. In response, the collection engine 154 may be configured to issue a diagnostic command 164 to the second client device 102b for executing one or more diagnostic procedures thereon.
[0035] In some implementations, the collection engine 154 may be configured to analyze the description and / or other suitable information submitted in the feedback package 162 to determine which areas or components of the second client device 102b are to be tested. In the illustrated example, the description indicates that the game console cannot be started. Thus, the collection engine 154 may be configured to issue diagnostic commands 164 to test one or more of the BIOS, operating system, power supply, or other suitable hardware / software components of the game console. In another example, when the description indicates that the game console has no network connection, the collection engine 154 may be configured to issue diagnostic commands 164 to test one or more of the network interface card ("NIC"), NIC driver, and / or other suitable network components of the game console.
[0036] Upon receiving the diagnostic command 164, the second client device 102b, i.e., the game console, can then execute one or more suitable diagnostic programs (not shown) to generate corresponding diagnostic information 166. The diagnostic information 166 may include data representing the current state / condition of the tested hardware / software component, the test results of the hardware / software component, the error code associated with the hardware / software component, and / or other suitable information. The second client device 102b can then transmit the diagnostic information 166 to the diagnostic system 150 via the computer network 104. In some embodiments, the collection engine 154 can also configure or program the second client device 102b (i.e., the game console) for additional diagnostics and / or other relevant information. For example, the collection engine 154 can be configured to program the game console to prompt the user 101 to attach diagnostic information, screenshots, or other suitable data when the user 101 subsequently accesses the game console. Upon receiving the diagnostic information 166, the collection engine 154 may forward both the feedback packet 162 received from the first client device 102a and the diagnostic information 166 received from the second client device 102b to the record processor 156. Figure 2 Example modules of collection engine 154 are described in more detail.
[0037] In response to receiving the feedback packet 162 received from the first client device 102a and the diagnostic information 166 received from the second client device 102b, the record processor 156 can be configured to combine or "align" the feedback packet 162 received from the first client device 102a and the diagnostic information 166 received from the second client device 102b into the diagnostic record 110. In some embodiments, this combination may include inserting data representing information from the feedback packet 162 and the diagnostic information 166 into different fields of the database record. Figure 3An example database record schema is described in more detail. In other embodiments, other suitable data merging techniques may be used to achieve the combination.
[0038] Thus, several embodiments of the disclosed technology can allow for efficient submission of feedback from a first computing device 102a while allowing remote diagnostic information collection from a second computing device 102b. Unlike other diagnostic systems, user feedback about problems with the second computing device 102b can be submitted using the first computing device 102a, which can provide user feedback more efficiently. Upon receiving user feedback from the first computing device 102a, the diagnostic system 150 at the remote server 106 can trigger remote collection of diagnostic information 166 of the second computing device 102a. The diagnostic information 166 collected from the second computing device 102b can then be aggregated or combined with the feedback received from the first computing device 102a as a diagnostic record 110 for the reported problem of the second computing device 102b. In this way, technical problems on the second computing device 102b can be easily submitted, diagnosed, and / or remedied even when the user 101 does not have physical access to the second computing device 102b.
[0039] In some embodiments, the diagnostic system 150 may include an optional remediation controller 158 configured to analyze the description in the feedback packet 162 in conjunction with the received diagnostic information 166 to determine the root cause of the reported problem with the second client device 102b (i.e., the game console) and automatically apply remedial actions to the game console. Figure 1E As shown, the remediation controller 158 can be configured to analyze the feedback packet 162 and the diagnostic information 166 and determine that the operating system on the game console has crashed. In response, the remediation controller 158 can be configured to issue a remediation command (e.g., a restart command) that causes the game console to restart. In another example, the remediation controller 158 can be configured to determine that the network interface card on the game console fails. In response, the remediation controller 158 can be configured to provide a message to the user 101 on any one of the first to fourth client devices 102a-102d, for replacing the network interface card on the game console.
[0040] Figure 2 An embodiment of the disclosed technology is shown. Figures 1A to 1E A schematic diagram of certain hardware / software components of the collection engine 154 of the computing system. Figure 2 As shown, the collection engine 154 may include an analysis module 157 and a command module 159 operatively coupled to each other. In other embodiments, the collection engine 154 may also include a network, a database, or other suitable types of modules.
[0041] In some embodiments, the analysis module 157 may be configured to analyze the received feedback packet 162 to determine one or more of the following: (i) the client device 102 to be tested ( Figure 1A ), (ii) the area of the client device 102 to be tested, and (iii) one or more diagnostic procedures to be performed by the client device 102. In one implementation, the analysis module 157 can be configured to perform the foregoing analysis based on machine learning. In other implementations, the analysis module 157 can be configured to perform the foregoing analysis based on, for example, a user 101 ( Figure 1A ), an administrator (not shown) or other appropriate entity configured rules (not shown) to perform the aforementioned analysis. In other embodiments, the analysis module 157 can be configured to analyze and determine other appropriate parameters.
[0042] The command module 159 may be configured to determine one or more diagnostic commands 164 corresponding to the determined one or more diagnostic procedures to be executed by the client device 102. In some implementations, the command module 159 may be configured to generate a batch command having a plurality of diagnostic commands 164 in sequence. In other embodiments, the command module 159 may be configured to generate a plurality of diagnostic commands 164 without being restricted by the order of execution. In further embodiments, the command module 159 may be configured to generate the diagnostic command 164 by consulting an external source (e.g., a third-party website) or via other suitable techniques.
[0043] Figure 3 The embodiment according to the disclosed technology is shown Figure 1D Schematic diagram of an example schema 170 of a diagnostic record 110. Figure 3 As shown, the example schema 170 may include multiple data fields. In the illustrated example, the schema 170 may include a user ID field 172, a device ID field 173, a user feedback field 174, one or more diagnostic data fields 175, and a remedial action field 176. The user ID field 172 may be configured to contain a user ID field 172 representing the user 101 ( Figure 1A ). The device ID field 173 may be configured to contain data representing the identity of the selected client device 102 ( Figure 1A ). User feedback field 174 may be configured to contain data representing any text, image, voice, or other suitable type of input from user 101 related to an operational problem with client device 102. Diagnostic data field 175 may be configured to contain data representing diagnostic information 166 ( Figure 1D). The remedial action field 176 can be configured to contain data representing one or more of the remedial action performed, the date / time of the remedial action performed, and the result of the remedial action being performed. In other examples, the schema 170 can also include additional and / or different fields (not shown).
[0044] Figure 4A and 4B A flowchart of a remote diagnostic process for a computing device according to an embodiment of the disclosed technology is shown. Figures 1A-1E While the operations of the processes are described in the context of a distributed computing system, in other embodiments, the processes may also be implemented in computing systems having additional and / or different components.
[0045] like Figure 4A As shown, process 200 may include, at stage 202, receiving data from a first device, and the data represents feedback to an operational problem of a second device. In one embodiment, such data may be received via a web page, as described above with reference to Figure 1A and 1B In other embodiments, such data may be received via other suitable communication channels. Process 200 may then include triggering a remote diagnostic operation on the second device at stage 204. Figure 4B Example operations for triggering a remote diagnostic operation are described. Process 200 may then include generating a diagnostic record for the second device at stage 206. Figure 1D Example operations for generating a diagnostic record are described. Process 200 may then include an optional operation of remotely triggering a remedial action on the second device at stage 208, as described above with reference to Figure 1E as described.
[0046] like Figure 4B As shown, triggering a remote diagnostic operation may include analyzing the feedback at stage 212 and determining a command at stage 214, as described above with reference to Figure 1C The operation may then include, at stage 216, outputting the determined command to, for example, Figure 1A The client device 102 in.
[0047] Figure 5 Is applicable to Figure 1A-1E The computing device 300 may be adapted to include certain components of the distributed computing system 100. For example, the computing device 300 may be adapted to include certain components of the distributed computing system 100. Figure 1A-1E The computing device 300 may include a client device 102 or a remote server 106. In a very basic configuration 302, the computing device 300 may include one or more processors 304 and a system memory 306. A memory bus 308 may be used for communication between the processor 304 and the system memory 306.
[0048] Depending on the desired configuration, processor 304 may be of any type, including but not limited to a microprocessor (μP), a microcontroller (μC), a digital signal processor (DSP), or any combination thereof. Processor 304 may include a multi-level cache, such as a level 1 cache 310 and a level 2 cache 312, a processor core 314, and registers 316. Example processor core 314 may include an arithmetic logic unit (ALU), a floating point unit (FPU), a digital signal processing core (DSP core), or any combination thereof. Example memory controller 318 may also be used with processor 304, or in some implementations, memory controller 318 may be an internal part of processor 304.
[0049] Depending on the desired configuration, system memory 306 may be of any type, including but not limited to volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof. System memory 306 may include an operating system 320, one or more applications 322, and program data 324. The basic configuration 302 described in Figure 5 The components are illustrated by those within the inner dashed line.
[0050] The computing device 300 may have additional features or functions and additional interfaces to facilitate communication between the basic configuration 302 and any other devices and interfaces. For example, a bus / interface controller 330 may be used to facilitate communication between the basic configuration 302 and one or more data storage devices 332 via a storage device interface bus 334. The data storage device 332 may be a removable storage device 336, a non-removable storage device 338, or a combination thereof. Examples of removable storage devices and non-removable storage devices include magnetic disk devices such as floppy disk drives and hard disk drives (HDDs), optical disk drives such as compact disk (CD) drives or digital versatile disk (DVD) drives, solid state drives (SSDs), and tape drives, etc. Example computer storage media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer-readable instructions, data structures, program modules, or other data. The term "computer-readable storage medium" or "computer-readable storage device" does not include propagation signals and communication media.
[0051] System memory 306, removable storage device 336, and non-removable storage device 338 are examples of computer-readable storage media. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other storage technology, CD-ROM, digital versatile disks (DVD) or other optical storage devices, magnetic cassettes, magnetic tape, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by computing device 300. Any such computer-readable storage media can be part of computing device 300. The term "computer-readable storage media" does not include propagating signals and communication media.
[0052] The computing device 300 may also include an interface bus 340 for facilitating communication from various interface devices (e.g., output devices 342, peripheral interfaces 344, and communication devices 346) to the basic configuration 302 via the bus / interface controller 330. Example output devices 342 include a graphics processing unit 348 and an audio processing unit 350, and the output devices may be configured to communicate with various external devices such as a display or speakers via one or more A / V ports 352. Example peripheral interfaces 344 include a serial interface controller 354 or a parallel interface controller 356, and the peripheral interfaces may be configured to communicate with external devices such as input devices (e.g., keyboards, mice, pens, voice input devices, touch input devices, etc.) or other peripheral devices (e.g., printers, scanners, etc.) via one or more I / O ports 358. Example communication devices 346 include a network controller 360, which may be arranged to facilitate communication with one or more other computing devices 362 over a network communication link via one or more communication ports 364.
[0053] A network communication link can be an example of a communication medium. Communication media can generally be embodied as computer-readable instructions, data structures, program modules or other data in a modulated data signal, such as a carrier wave or other transmission mechanism, and can include any information transfer medium. A "modulated data signal" can be a signal having one or more of its characteristics set or changed in a manner that encodes information into the signal. As an example and not limitation, communication media can include wired media, such as a wired network or a direct wired connection, and wireless media, such as acoustic, radio frequency (RF), microwave, infrared (IR) and other wireless media. The term computer-readable medium used herein can include storage media and communication media.
[0054] The computing device 300 may be implemented as part of a small portable (or mobile) electronic device, such as a cell phone, a personal digital assistant (PDA), a personal media player device, a wireless network viewing device, a personal headset device, an application-specific device, or a hybrid device including any of the above functionality. The computing device 300 may also be implemented as a personal computer including both laptop and non-laptop configurations.
[0055] It can be understood from the foregoing that specific embodiments of the present disclosure have been described herein for illustrative purposes, but various modifications may be made without departing from the present disclosure. In addition, many elements of an embodiment may be combined with other embodiments to supplement or replace elements of other embodiments. Therefore, the present technology is not subject to restrictions other than the appended claims.
Claims
1. A method for performing remote diagnosis in a computing system having a first computing device, a second computing device, and a remote server coupled to each other via a computer network, the method include: transmitting, from the first computing device to the remote server, data representing user feedback reporting an operational problem associated with the second computing device; as well as In response to receiving the data representing the operational problem associated with the second computing device, transmitting, from the remote server, a diagnostic command to the second computing device via the computer network; executing, at the second computing device, the diagnostic command from the remote server to generate diagnostic information, and transmitting the generated diagnostic information to the remote server; as well as Upon receiving the data representing the generated diagnostic information from the second computing device, at the remote server, combining the data from the first computing device representing user feedback reporting the operational problem with the generated diagnostic information from the second computing device; as well as The combined data is stored in a data repository as a database record corresponding to the reported operational problem of the second computing device from the first computing device.
2. The method according to claim 1, further comprising: include: In response to receiving the data indicative of user feedback reporting the operational problem associated with the second computing device, at the server: analyzing the received data representing user feedback reporting the operational problem to determine one or more diagnostic operations to be performed on the second computing device; as well as The diagnostic commands corresponding to the one or more diagnostic operations to be performed by the second computing device are determined.
3. The method according to claim 1, in: Receiving the data representing user feedback reporting the operational issue associated with the second computing device, in addition to the data representing user feedback reporting the operational issue, further comprises, receiving from the first computing device data representing credentials for remotely accessing the second computing device; and Transmitting the diagnostic command includes transmitting the diagnostic command and the data representing the certificate to the second computing device.
4. The method according to claim 1, further comprising: include: receiving, from the first computing device, data representing login information corresponding to a user account at the remote server; In response to receiving the data representing the login information, authenticating the received login information; upon authenticating the received login information, transmitting from the remote server to the first computing device data representing a list of computing devices registered to the user account, the list including both the first computing device and the second computing device; A selection of the second computing device and the data reporting the operational issue associated with the second computing device are received from the first computing device.
5. A method for performing remote diagnosis in a computing system having a first computing device, a second computing device, and a remote server coupled to each other via a computer network, the method include: receiving, at the remote server, from the first computing device, data representing user feedback reporting an operational problem associated with the second computing device; as well as In response to receiving the data indicative of the operational problem associated with the second computing device, transmitting, from the remote server, a diagnostic command to the second computing device, the diagnostic command triggering the second computing device to generate diagnostic information by performing one or more diagnostic operations; receiving, at the remote server, data representing the generated diagnostic information from the second computing device; as well as in response to receiving the data representing the generated diagnostic information from a second computing device, combining the data representing the user feedback reporting the operational problem from the first computing device with the generated diagnostic information from the second computing device; as well as The combined data is stored in a data repository as a database record corresponding to the reported operational problem of the second computing device from the first computing device.
6. The method according to claim 5, further comprising: include: In response to receiving the data indicative of user feedback reporting the operational problem associated with the second computing device, analyzing the received data representing user feedback reporting the operational problem to determine the one or more diagnostic operations to be performed on the second computing device; as well as The diagnostic commands corresponding to the one or more diagnostic operations are determined.
7. The method according to claim 5, in: receiving the data representing user feedback reporting the operational problem associated with the second computing device includes, in addition to the data representing user feedback reporting the operational problem, receiving from the first computing device data representing credentials for remotely accessing the second computing device; and Transmitting the diagnostic command includes transmitting the diagnostic command and the data representing the certificate to a second computing device.
8. The method according to claim 5, further comprising: include: In response to receiving the data representing the generated diagnostic information from the second computing device, determining, at the remote server, a remedial action for the second computing device corresponding to the operational problem; as well as A remediation command is transmitted from the remote server to the second computing device, the remediation command triggering the determined remedial action on the second computing device to resolve the operational problem reported from the first computing device.
9. The method according to claim 5, further comprising: include: In response to receiving the data representing the generated diagnostic information from the second computing device, determining, at the remote server, a remedial action for the second computing device corresponding to the operational issue based on the database record.
10. The method according to claim 5, further comprising: include: receiving, from the first computing device, data representing login information corresponding to a user account at the remote server; as well as In response to receiving said data representing said login information, authenticating the received login information; as well as Upon authenticating the received login information, data representing a list of computing devices registered to the user account is transmitted from the remote server to the first computing device, the list including both the first computing device and the second computing device.
11. The method according to claim 5, further comprising: include: receiving, from the first computing device, data representing login information corresponding to a user account at the remote server; as well as In response to receiving said data representing said login information, authenticating the received login information; upon authenticating the received login information, transmitting from the remote server to the first computing device data representing a list of computing devices registered to the user account, the list including both the first computing device and the second computing device; and A selection of the second computing device and the data reporting the operational issue associated with the second computing device are received from the first computing device.
12. The method according to claim 5, further comprising: include: In response to receiving the data representing the generated diagnostic information from the second computing device, configuring, by the remote server, the second computing device to: provide additional diagnostic information upon a subsequent access of the second computing device by a user; as well as Upon receiving the additional diagnostic information from the second computing device, the database record is modified to include the received additional diagnostic information.
13. The method according to claim 5, further comprising: include: Perform one or more of the following operations on the database record: Remove personally identifiable information; reviewing said data received reporting said operational problem; translating the received data reporting the operational problem from a first language into a second language; creating an error report corresponding to the second computing device; Preventing the database records from being queried by users; or A copy of the database record is forwarded to an additional computing device for further processing.
14. A remote server in a computing system having a first computing device and a second computing device coupled to the remote server via a computer network, the remote server include: processor; as well as a memory operably coupled to the processor, the memory containing instructions executable by the processor to cause the remote server to: receiving, from the first computing device, data representing user feedback reporting an operational problem associated with the second computing device; as well as upon receiving, from the first computing device, the data representing the user feedback reporting an operational problem associated with the second computing device, transmitting a diagnostic command from the remote server to the second computing device via the computer network, the diagnostic command triggering the second computing device to generate diagnostic information by performing one or more diagnostic operations; as well as Upon receiving data representing the generated diagnostic information from the second computing device, the data representing the user feedback reporting the operational problem from the first computing device is combined with the generated diagnostic information from the second computing device, and the combined data is stored in a data repository as a database record corresponding to the operational problem of the second computing device reported from the first computing device.
15. The remote server of claim 14, wherein the memory includes additional instructions executable by the processor to cause the remote server to: Upon receiving the data indicative of user feedback reporting the operational problem associated with the second computing device, analyzing said received data reporting said operational problem to determine said one or more diagnostic operations to be performed on said second computing device; and The diagnostic commands corresponding to the one or more diagnostic operations are determined.
16. The remote server according to claim 14, in: The data received from the first computing device also includes credentials for remotely accessing the second computing device; as well as Transmitting the diagnostic command includes transmitting the diagnostic command along with the data representing the credential to the second computing device.
17. The remote server of claim 14, wherein the memory includes additional instructions executable by the processor to cause the remote server to: Upon receiving the data representing the generated diagnostic information from the second computing device, A remedial action for a second computing device corresponding to the operational problem is determined, and a remedial command is transmitted to the second computing device, the remedial command triggering the determined remedial action for the second computing device to resolve the operational problem reported from the first computing device.
18. The remote server of claim 14, wherein the memory includes additional instructions executable by the processor to cause the remote server to: Upon receiving the data representing the generated diagnostic information from a second computing device, determining, at the remote server, a remedial action for the second computing device corresponding to the operational issue based on the generated database record.
19. The remote server of claim 14, wherein the memory includes additional instructions executable by the processor to cause the remote server to: Receiving, from the first computing device, data representing login information corresponding to a user account at the remote server ; as well as In response to receiving said data representing said login information, authenticating the received login information; as well as Upon authenticating the received login information, data representing a list of computing devices registered to the user account is transmitted from the remote server to the first computing device, the list including both the first computing device and a second computing device.
20. The remote server of claim 14, wherein the memory includes additional instructions executable by the processor to cause the remote server to: Receiving, from the first computing device, data representing login information corresponding to a user account at the remote server ; as well as In response to receiving said data representing said login information, authenticating the received login information; upon authenticating the received login information, transmitting from the remote server to the first computing device data representing a list of computing devices registered to the user account, the list including both the first computing device and a second computing device; and A selection of the second computing device and the data reporting the operational issue associated with the second computing device are received from the first computing device.
