Device detection method and apparatus

Abstract

The present disclosure discloses a device detection method and device, and relates to the technical field of computers. The device detection method comprises the following steps: determining target detection scene information according to a scene selection operation triggered by a user on an application page; determining at least one unmanned vehicle as a target vehicle according to a vehicle selection operation triggered by the user on the application page; in response to a device detection operation triggered by the user on the application page, sending a device detection instruction to the target vehicle to start a device detection process corresponding to the target detection scene information; and receiving a device detection result returned by the target vehicle. Through the above method, the learning cost of the user for unmanned vehicle detection is reduced, the detection efficiency of the unmanned vehicle is improved, the detection requirements of different detection scenes can be met, and the applicability of the unmanned vehicle device detection is improved.

Description

Technical Field

[0001] The present disclosure relates to the field of computers, and in particular to a device detection method and apparatus. Background Art

[0002] In many application scenarios, unmanned vehicles require equipment testing. For example, after the production of an unmanned vehicle or after vehicle maintenance, the software and hardware equipment on the unmanned vehicle need to be tested.

[0003] In related technologies, workers can only perform equipment inspections on one unmanned vehicle at a time. Furthermore, before conducting an unmanned vehicle inspection, workers must enter a command code to activate the vehicle-side inspection tool, which places high demands on the staff and is difficult to use. Furthermore, related technologies only allow for a limited number of fixed inspection items, failing to meet actual inspection needs. Summary of the Invention

[0004] A technical problem to be solved by the present disclosure is to provide a solution whereby users can start the inspection process of at least one unmanned vehicle by simply performing simple page operations, thereby reducing the learning cost for users to conduct vehicle inspections, improving the efficiency of unmanned vehicle inspections, and meeting the inspection requirements of different inspection scenarios, thereby improving the applicability of unmanned vehicle equipment inspections.

[0005] According to a first aspect of the present disclosure, a device detection method is proposed, which is applied to a user terminal, including: determining target detection scene information based on a scene selection operation triggered by a user on an application page; determining at least one unmanned vehicle as a target vehicle based on a vehicle selection operation triggered by the user on the application page; sending a device detection instruction to the target vehicle in response to the device detection operation triggered by the user on the application page to start a device detection process corresponding to the target detection scene information; and receiving a device detection result returned by the target vehicle.

[0006] In some embodiments, sending a device detection instruction to the target vehicle includes: determining whether a network connection has been established with the target vehicle; if a network connection has been established with the target vehicle, sending a device detection instruction to the target vehicle; if a network connection has not been established with the target vehicle, displaying a network prompt message to the user, and after the user completes the operation of establishing a network connection with the target vehicle based on the network prompt message, sending a device detection instruction to the target vehicle.

[0007] In some embodiments, sending a device detection instruction to the target vehicle includes: determining whether the target vehicle has a historical detection record in a target detection scenario; and sending a device detection instruction to the target vehicle if the target vehicle does not have a historical detection record in the target detection scenario.

[0008] In some embodiments, it also includes: when the target vehicle has a historical detection record in the target detection scenario, displaying a prompt information of the existence of the historical detection record to the user; after receiving the user's confirmation instruction to re-detect the target vehicle, sending a device detection instruction to the target vehicle; after receiving the user's confirmation instruction not to re-detect the target vehicle, not sending the device detection instruction to the target vehicle.

[0009] In some embodiments, the method further includes: if the target vehicle has a historical detection record in a target detection scenario, not sending a device detection instruction to the target vehicle.

[0010] In some embodiments, the method further includes: after determining the target detection scenario, switching to an interactive page corresponding to the target detection scenario, so as to interact with the user based on the interactive page corresponding to the target detection scenario.

[0011] In some embodiments, before sending a device detection instruction to the target vehicle, the model information of the target vehicle is obtained; if the model information of the target vehicle is successfully obtained, the model information of the target vehicle and the target detection scene information are carried in the device detection instruction.

[0012] In some embodiments, obtaining the vehicle model information of the target vehicle includes: sending a vehicle model query request to a cloud server; and receiving the vehicle model information of the target vehicle returned by the cloud server.

[0013] In some embodiments, when the target detection scenario is an unmanned vehicle calibration detection scenario, the device detection process corresponding to the target detection scenario information includes a connectivity detection process of the unmanned vehicle's on-board equipment.

[0014] In some embodiments, the connectivity detection process of the unmanned vehicle's onboard equipment includes connectivity detection items of at least one of the following devices: unmanned vehicle's onboard camera, unmanned vehicle's onboard radar, vehicle-side control system, onboard GPS sensor, and onboard inertial sensor.

[0015] According to the second aspect of the present disclosure, a device detection method is also proposed, which is applied to an unmanned vehicle, including: receiving a device detection instruction sent by a user terminal, wherein the device detection instruction carries target detection scene information; according to the device detection instruction, starting a device detection process corresponding to the target detection scene information; and sending the device detection result to the user terminal.

[0016] According to the third aspect of the present disclosure, a device detection apparatus is also proposed, which is arranged in a user terminal and includes: a first determination module, configured to determine target detection scene information according to a scene selection operation triggered by a user on an application page; a second determination module, configured to determine at least one unmanned vehicle as a target vehicle according to a vehicle selection operation triggered by a user on the application page; an instruction sending module, configured to send a device detection instruction to the target vehicle in response to the device detection operation triggered by the user on the application page, so as to start a device detection process corresponding to the target detection scene information; and a result receiving module, configured to receive the device detection result returned by the target vehicle.

[0017] According to the fourth aspect of the present disclosure, a device detection device is also proposed, which is arranged in an unmanned vehicle and includes: an instruction receiving module, configured to receive a device detection instruction sent by a user terminal, wherein the device detection instruction carries target detection scene information; a detection start module, configured to start a device detection process corresponding to the target detection scene information according to the device detection instruction; and a result sending module, configured to send the device detection result to the user terminal.

[0018] According to a fifth aspect of the present disclosure, a device detection apparatus is further proposed, comprising: a memory; and a processor coupled to the memory, wherein the processor is configured to execute the device detection method as described above based on instructions stored in the memory.

[0019] According to a sixth aspect of the present disclosure, a computer-readable storage medium is further proposed, on which computer program instructions are stored, and when the instructions are executed by a processor, the above-mentioned device detection method is implemented.

[0020] Compared with the related art, in the embodiment of the present disclosure, the target detection scene information is determined according to the user's page operation on the application page, and at least one unmanned vehicle is determined as the target vehicle according to the vehicle selection operation triggered by the user on the application page. In response to the device detection operation triggered by the user on the application page, a device detection instruction is sent to the target vehicle to start the device detection process corresponding to the target detection scene information, and the device detection result returned by the target vehicle is received. These steps reduce the user's learning cost for unmanned vehicle detection, have good ease of use, improve the detection efficiency of unmanned vehicles, and can meet the detection requirements of different detection scenarios, thereby improving the applicability of unmanned vehicle equipment detection.

[0021] Other features and advantages of the present disclosure will become apparent from the following detailed description of exemplary embodiments of the present disclosure with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0023] The present disclosure can be more clearly understood from the following detailed description with reference to the accompanying drawings, in which:

[0024] Figure 1 Schematic diagram of a device detection method according to some embodiments of the present disclosure.

[0025] Figure 2 The present invention is a flowchart of sending a device detection instruction to a target vehicle according to some embodiments of the present disclosure.

[0026] Figure 3 The present invention is a flowchart of sending a device detection instruction to a target vehicle according to other embodiments of the present disclosure.

[0027] Figure 4 Schematic diagram of a device detection method according to some embodiments of the present disclosure.

[0028] Figure 5 Schematic diagram of the structure of a device detection apparatus according to some embodiments of the present disclosure.

[0029] Figure 6 Schematic diagram of the structure of a device detection apparatus according to other embodiments of the present disclosure.

[0030] Figure 7 Schematic diagram of the structure of a device detection apparatus according to some further embodiments of the present disclosure.

[0031] Figure 8 Schematic diagram of the structure of a computer system according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0032] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that unless otherwise specifically stated, the relative arrangement of components and steps, numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present disclosure.

[0033] At the same time, it should be understood that for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.

[0034] The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the present disclosure, its application, or uses.

[0035] Technologies, methods and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, such technologies, methods and equipment should be considered part of the authorization specification.

[0036] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not limiting. Therefore, other examples of the exemplary embodiments may have different values.

[0037] It should be noted that like reference numerals and letters refer to like items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0038] In order to make the objectives, technical solutions and advantages of the present disclosure more clearly understood, the present disclosure is further described in detail below in conjunction with specific embodiments and with reference to the accompanying drawings.

[0039] Figure 1 FIG. 1 is a flow chart of a device detection method according to some embodiments of the present disclosure. Figure 1 As shown, the device detection method of the embodiment of the present disclosure is applied to a user terminal, comprising the following steps:

[0040] Step S110: determining target detection scene information according to a scene selection operation triggered by the user on the application page.

[0041] The user terminal's application page is provided with an interactive control for selecting a scene. The user can select a scene by operating the interactive control. After detecting the user's scene selection operation, the user terminal determines the target detection scene information based on the user's scene selection operation.

[0042] The user terminal supports multiple detection scenarios, and different detection scenarios correspond to different device detection processes. In some embodiments, the detection scenarios supported by the user terminal include: vehicle calibration detection scenario, vehicle maintenance detection scenario. If the user selects the vehicle calibration detection scenario, the information of the vehicle calibration detection scenario is used as the target detection scenario information; if the user selects the vehicle maintenance detection scenario, the information of the vehicle maintenance detection scenario is used as the target detection scenario information. During specific implementation, the detection scenarios supported by the user terminal can be expanded according to needs.

[0043] Step S120: According to the vehicle selection operation triggered by the user on the application page, at least one unmanned vehicle is determined as the target vehicle.

[0044] The user terminal's application page features an interactive control for selecting a vehicle. The user can select a vehicle by operating this interactive control. After detecting the user's vehicle selection operation, the user terminal determines the target vehicle based on the user's vehicle selection operation. For example, if the user selects unmanned vehicle A, unmanned vehicle A will be the target vehicle; if the user selects unmanned vehicles B and C, unmanned vehicles B and C will be the target vehicles.

[0045] In the disclosed embodiments, the order in which steps S110 and S120 are executed is not specifically limited. In some embodiments, the interactive controls for selecting a scene and the interactive controls for selecting a vehicle are located on the same page. The user can select a scene first and then a vehicle, or select a vehicle first and then a scene. Accordingly, step S110 can be executed first and then step S120, or step S120 can be executed first and then step S110.

[0046] In other embodiments, the interactive controls for selecting a scene and the interactive controls for selecting a vehicle are located on different pages. When the interactive controls for selecting a scene are located on the previous page and the interactive controls for selecting a vehicle are located on the next page, step S110 is performed first, followed by step S120. When the interactive controls for selecting a vehicle are located on the previous page and the interactive controls for selecting a scene are located on the next page, step S120 is performed first, followed by step S110.

[0047] Step S130: In response to the device detection operation triggered by the user on the application page, a device detection instruction is sent to the target vehicle to start a device detection process corresponding to the target detection scenario information.

[0048] The user terminal's application page contains an interactive control for triggering device detection. The user can trigger the device detection operation by operating this interactive control. After detecting the user's device detection operation, the user terminal sends a device detection instruction to the target vehicle. For example, if the target vehicle is a single unmanned vehicle, after the user triggers the device detection operation for that vehicle, the device detection instruction is sent to that unmanned vehicle. If there are multiple unmanned vehicles, after the user triggers the device detection operation for multiple unmanned vehicles, the device detection instruction is sent to all of them.

[0049] After receiving the device detection instruction from the user terminal, the target vehicle initiates the device detection process corresponding to the target detection scenario information. In some embodiments, a correspondence between the detection scenario and the device detection process is preconfigured. Exemplarily, this correspondence includes: a detection scenario identifier and a corresponding device detection process identifier. In these embodiments, after receiving the device detection instruction from the user terminal, the target vehicle can query this correspondence based on the target detection scenario information carried in the device detection instruction to determine the device detection process corresponding to the target detection scenario information.

[0050] In some embodiments, when the target detection scenario is a self-driving vehicle calibration detection scenario, the device detection process corresponding to the target detection scenario information includes a connectivity detection process for the self-driving vehicle's onboard devices. For example, the connectivity detection process for the self-driving vehicle's onboard devices includes connectivity detection items for at least one of the following devices: the self-driving vehicle's onboard camera, the self-driving vehicle's onboard radar, the vehicle-side control system, the onboard GPS sensor, and the onboard inertial sensor.

[0051] Step S140: Receive the equipment detection result returned by the target vehicle.

[0052] After the target vehicle completes the device detection process, the device detection result is sent to the user terminal. The user terminal receives the device detection result returned by the target vehicle.

[0053] In the disclosed embodiment, the above process allows users to initiate the device detection process for multiple unmanned vehicles with a simple page operation. This not only reduces the user's learning cost for unmanned vehicle detection, improves ease of use, enhances the user experience, and improves the efficiency of unmanned vehicle detection. Furthermore, the above process can meet users' device detection needs for different detection scenarios, improve the applicability of unmanned vehicle device detection, and further enhance the user experience.

[0054] Figure 2 The present invention is a flowchart of sending a device detection instruction to a target vehicle according to some embodiments of the present disclosure. Figure 2 This is a detailed description of step S130. Figure 2 As shown, the process includes:

[0055] Step S131: Detecting a device detection operation triggered by a user on an application page.

[0056] The user terminal's application page is provided with an interactive control for triggering device detection. The user can trigger the device detection operation by operating the interactive control. After the user's device detection operation is detected, step S132 is executed.

[0057] Step S132: Determine whether a network connection has been established with the target vehicle.

[0058] If the judgment result of step S132 is yes, execute step S135; if the judgment result of step S132 is no, execute step S133.

[0059] Step S133: Displaying network connection prompt information to the user.

[0060] For example, a network prompt message such as “Not connected to the vehicle-side network” or “Not connected to the vehicle numbered XXX” is displayed on the user terminal.

[0061] Step S134: In response to the user's networking operation based on the networking prompt information, a network connection is established with the target vehicle.

[0062] In some embodiments, the user, prompted by the connection prompt, connects to the vehicle-side network using the interactive controls on the application page. For example, the user selects the target vehicle's vehicle-side wireless network on the application page and enters the corresponding password. After verifying that the password entered by the user is correct, a network connection is established with the target vehicle.

[0063] In some embodiments, when displaying each vehicle-side wireless network, not only the name of the vehicle-side wireless network is displayed, but also the information of the corresponding vehicle is displayed, such as the license plate information presented in text form, and / or, the vehicle appearance information presented in picture form, etc.

[0064] Step S135: Sending a device detection instruction to the target vehicle.

[0065] After determining that a network connection has been established with the target vehicle, or after establishing a network connection with the target vehicle through steps S133 and S134, a device detection instruction is sent to the target vehicle to start a device detection process corresponding to the target detection scenario information.

[0066] In the embodiment of the present disclosure, by determining whether a network connection has been established with the target vehicle, if the network connection has been established with the target vehicle, a device detection instruction is directly sent to the target vehicle without the need to perform the network connection operation again, thereby reducing resource consumption during the device detection process.

[0067] Figure 3 The present invention is a flowchart of sending a device detection instruction to a target vehicle according to other embodiments of the present disclosure. Figure 3 This is a detailed description of step S130. Figure 3 As shown, the process includes:

[0068] Step S131 ′: detecting a device detection operation triggered by a user on an application page.

[0069] The user terminal's application page is provided with an interactive control for triggering device detection. The user can trigger the device detection operation by operating the interactive control. After the user's device detection operation is detected, step S132' is executed.

[0070] Step S132 ′: determine whether the target vehicle has any historical detection records in the target detection scenario.

[0071] In some embodiments, the user terminal sends a historical detection record query request to the cloud server and receives a query result corresponding to the historical detection record query request from the cloud server. If the query result indicates that the target vehicle has a historical detection record in the target detection scenario, the judgment result of step S132' is yes; if the query result indicates that the target vehicle has no historical detection record in the target detection scenario, the judgment result of step S132' is no.

[0072] If the judgment result of step S132 ′ is yes, step S133 ′ is executed; if the judgment result of step S132 ′ is no, step S135 ′ is executed.

[0073] Step S133 ′: displaying a prompt message indicating the existence of the historical detection record to the user.

[0074] For example, prompt information indicating the existence of historical inspection records such as “Vehicle No. XXX has been inspected” or “Inspection records for this vehicle already exist” is displayed on the user terminal.

[0075] In some embodiments, the user terminal is also provided with an interactive control for viewing historical detection records. The user can view the detailed information of the historical detection records by operating the interactive control, so that the user can decide whether to re-inspect the target vehicle by analyzing the historical detection records.

[0076] Step S134 ′: determining whether a user instruction to confirm re-detection of the target vehicle is received.

[0077] If the judgment result of step S134 ′ is yes, step S135 ′ is executed; if the judgment result of step S134 ′ is no, the process ends.

[0078] Step S135 ′: Sending a device detection instruction to the target vehicle.

[0079] After it is determined in step S132' that the target vehicle has no historical detection record in the target detection scenario, or after it is determined in step S134' that a user confirmation instruction to re-detect the target vehicle is received, a device detection instruction is sent to the target vehicle.

[0080] In the disclosed embodiment, by determining whether the target vehicle has been detected and performing different operations based on different judgment results, it is possible to avoid unnecessary repeated detection of unmanned vehicles, improve detection efficiency, and help improve the user experience in unmanned vehicle equipment detection.

[0081] Figure 4 FIG. 1 is a flow chart of a device detection method according to other embodiments of the present disclosure. Figure 4As shown, the device detection method in the embodiment of the present disclosure includes:

[0082] Step 401: The user performs a scene selection operation on the user terminal.

[0083] The application page of the user terminal is provided with an interactive control for selecting a scene. The user can select a scene by operating the interactive control.

[0084] The user terminal supports multiple detection scenarios. In some embodiments, the detection scenarios supported by the user terminal include: vehicle calibration detection scenario, vehicle maintenance detection scenario. During specific implementation, the detection scenarios supported by the user terminal can be expanded according to needs.

[0085] In some embodiments, different scene controls are set for different scenarios, and users can select a scene by clicking the corresponding scene control. For example, for a vehicle calibration and inspection scene, a calibration and inspection scene control is set; for a vehicle maintenance and inspection scene, a maintenance and inspection scene control is set.

[0086] Step 402: The user terminal determines target detection scene information.

[0087] In this step, the user terminal determines the target detection scene information according to the scene selection operation performed by the user on the application page, wherein the target detection scene information includes the target detection scene identifier.

[0088] For example, when the user selects the vehicle calibration detection scene, the information of the vehicle calibration detection scene is used as the target detection scene information; when the user selects the vehicle maintenance detection scene, the information of the vehicle maintenance detection scene is used as the target detection scene information.

[0089] Step 403: The user terminal switches to the interactive page corresponding to the target detection scene information.

[0090] In the embodiment of the present disclosure, different interactive pages are set for different detection scenarios. After the target detection scenario information is determined in step 402, the interactive page corresponding to the target detection scenario information is switched to so as to perform subsequent operations based on the interactive page corresponding to the scenario.

[0091] Step 404: The user performs a vehicle selection operation on the user terminal.

[0092] The interactive page corresponding to the target detection scene information has an interactive control for selecting a vehicle. Users can select a vehicle by operating the interactive control.

[0093] Step 405: The user terminal determines at least one unmanned vehicle as a target vehicle.

[0094] In this step, the user terminal determines at least one unmanned vehicle as the target vehicle based on the user's vehicle selection operation. For example, if the user selects unmanned vehicle A, unmanned vehicle A will be the target vehicle; if the user selects unmanned vehicles B and C, unmanned vehicles B and C will be the target vehicles.

[0095] Step 406: The user performs a device detection operation on the user terminal.

[0096] The interactive page corresponding to the target detection scene information has interactive controls for triggering device detection. Users can trigger the device detection operation by operating the interactive controls.

[0097] Step 407: The user terminal obtains the model information of the target vehicle.

[0098] After detecting the user's device detection operation, the user terminal obtains the target vehicle's model information. The target vehicle's model information includes the target vehicle's model identification. In addition, the target vehicle's model information may also include information such as the configuration of onboard sensors.

[0099] In some embodiments, the user terminal sends a vehicle model query request to the cloud server, where the vehicle model query request includes a vehicle identifier such as the target vehicle's license plate number. The cloud server retrieves the target vehicle's model information from a storage system based on the vehicle model query request. If the cloud server retrieves the target vehicle's model information, it sends it to the user terminal. The user terminal receives the target vehicle's model information returned by the cloud server and then executes step 408. Optionally, if the cloud server fails to retrieve the target vehicle's model information, it returns a failed acquisition prompt message, such as "The target vehicle's model information does not exist," to the user terminal. The user terminal receives and displays the failed acquisition prompt message, terminating the current process, i.e., not executing steps 408 and subsequent steps such as step 409. By storing information such as the unmanned vehicle's model in the cloud server, the user terminal's storage resources occupied by vehicle equipment detection can be reduced, thereby optimizing the device detection control process.

[0100] For example, the vehicle model information stored in the cloud server is shown in Table 1. Assuming that the license plate number of the target vehicle carried in the vehicle model query request is 00001, by querying the stored information shown in Table 1, the vehicle model information of the target vehicle can be determined as follows: the vehicle model identifier is 1, and the onboard sensors of this vehicle model are 4 radars, 4 surround-view cameras, and 2 traffic light cameras.

[0101] Table 1

[0102]

[0103]

[0104] In other embodiments, the user terminal queries the model information of the target vehicle locally. After the model information of the target vehicle is obtained locally, step 408 is executed. If the model information of the target vehicle is not obtained locally, a model query request is sent to the server, and the model information of the target vehicle is returned by the server.

[0105] Step 408: The user terminal generates a device detection instruction that carries vehicle type information and target detection scenario information.

[0106] In some embodiments, before step 408, the user terminal further includes determining whether there is a historical detection record corresponding to the target detection scenario and the model information of the target vehicle, and the determination result is negative. In addition, if there is a historical detection record corresponding to the target detection scenario and the model information of the target vehicle, the current process is terminated, that is, steps 408 and subsequent steps such as step 409 of the current process are not executed.

[0107] Step 409: The user terminal sends a device detection instruction to the unmanned vehicle.

[0108] In some embodiments, the user terminal determines whether a network connection has been established with the target vehicle. If a network connection has been established with the target vehicle, the user terminal sends a device detection instruction to the target vehicle. If a network connection has not been established with the target vehicle, a network connection prompt is displayed to the user. After the user completes the operation of establishing a network connection with the target vehicle based on the network connection prompt, the device detection instruction is sent to the target vehicle.

[0109] Step 410: The unmanned vehicle starts the equipment detection process.

[0110] In some embodiments, a pre-set relationship between detection scenarios, vehicle models, and device detection processes is established. In this step, the unmanned vehicle queries this relationship based on the target detection scenario information and vehicle model information carried in the device detection instruction to determine the device detection process corresponding to the target detection scenario information and vehicle model information, and then initiates the device detection process.

[0111] In some embodiments, when the target detection scenario is an unmanned vehicle calibration detection scenario, the device detection process corresponding to the target detection scenario information includes a connectivity detection process for the unmanned vehicle's onboard equipment. For example, in the unmanned vehicle calibration detection scenario, the device connectivity detection process corresponding to a certain vehicle model includes the following connectivity detection items: vehicle-side system, inertial sensor (IMU), global positioning system (GPS) sensor, 5 radars (located on the top, front, rear, left, and right sides of the vehicle respectively), 4 surround-view cameras (located on the front, rear, left, and right sides of the vehicle respectively), 4 streaming cameras (located on the front, rear, left, and right sides of the vehicle respectively), 2 traffic light cameras (located on the left and right sides of the vehicle respectively), left headlight, right headlight, left turn signal, right turn signal, reverse light, front bumper, rear bumper, router, display, chassis, etc.

[0112] In step 410, the unmanned vehicle can test various detection items through the system process. For example, in the device connectivity detection process, the unmanned vehicle can test the connectivity of sensors such as radar and camera through the system process.

[0113] Step 411: The unmanned vehicle sends the device detection result to the user terminal.

[0114] After the unmanned vehicle completes the device detection process, it sends the device detection results to the user terminal. The user terminal receives the device detection results returned by the target vehicle.

[0115] After receiving the device detection results, the user terminal displays them. For example, in a device connectivity test, the user terminal displays the device connectivity test results for each target vehicle one by one. The device connectivity test results for each target vehicle include: the detection item and the detection result of the detection item (normal connection or disconnection).

[0116] In some embodiments, taking into account the possibility that detection failure may occur due to factors such as network failure, in view of this, the user terminal also supports displaying prompt information such as the cause of detection failure error in the case of detection failure. For example, the detection failure prompt information is displayed in the form of a pop-up box. After the user clicks the pop-up box, he can click to view the detailed error cause, such as "grpc network timeout", "dual-machine communication failed, please shut down and restart, and operate again", and "Please contact the administrator to confirm whether this version of the tool supports this model", etc. Among them, for the case of detection failure caused by grpc network timeout, the error cause can be further subdivided. For example, the grpc network timeout is subdivided into: detection of router connectivity timeout, detection of front-stream camera connectivity timeout, detection of rear-stream camera connectivity timeout, detection of left turn signal connectivity timeout, detection of right turn signal connectivity timeout, timeout in obtaining chassis error code, etc.

[0117] In the disclosed embodiments, the above steps implement a new device detection process. This process allows users to initiate device detection for multiple unmanned vehicles with a simple page operation. This not only reduces the learning cost for users to perform unmanned vehicle detection, improves ease of use, enhances the user experience, and increases the efficiency of unmanned vehicle detection. Furthermore, the above process can meet users' detection needs for different detection scenarios and different vehicle models, improving the applicability of unmanned vehicle device detection and further enhancing the user experience.

[0118] Figure 5 FIG. 1 is a schematic diagram of the structure of a device detection apparatus according to some embodiments of the present disclosure. Figure 5 As shown, the device detection apparatus of the embodiment of the present disclosure is set in the user terminal, and includes: a first determination module 510, a second determination module 520, an instruction sending module 530, and a result receiving module 540.

[0119] The first determination module 510 is configured to determine target detection scene information according to a scene selection operation triggered by the user on the application page.

[0120] The application page of the user terminal is provided with an interactive control for selecting a scene. The user can select a scene by operating the interactive control. After detecting the user's scene selection operation, the first determination module 510 determines the target detection scene information according to the user's scene selection operation.

[0121] The user terminal supports multiple detection scenarios, and different detection scenarios correspond to different device detection processes. In some embodiments, the detection scenarios supported by the user terminal include: vehicle calibration detection scenario, vehicle maintenance detection scenario. When the user selects the vehicle calibration detection scenario, the first determination module 510 uses the information of the vehicle calibration detection scenario as the target detection scenario information; when the user selects the vehicle maintenance detection scenario, the first determination module 510 uses the information of the vehicle maintenance detection scenario as the target detection scenario information. During specific implementation, the detection scenarios supported by the user terminal can be expanded according to needs.

[0122] The second determination module 520 is configured to determine at least one unmanned vehicle as a target vehicle according to a vehicle selection operation triggered by the user on the application page.

[0123] The user terminal's application page includes an interactive control for selecting a vehicle. The user can select a vehicle by operating this interactive control. After detecting the user's vehicle selection operation, the second determination module 520 determines the target vehicle based on the user's vehicle selection operation. For example, if the user selects unmanned vehicle A, the second determination module 520 selects unmanned vehicle A as the target vehicle; if the user selects unmanned vehicles B and C, the second determination module 520 selects unmanned vehicles B and C as the target vehicles.

[0124] In the disclosed embodiments, the order in which the first and second determination modules are invoked is not specifically limited. In some embodiments, the interactive controls for selecting a scene and the interactive controls for selecting a vehicle are located on the same page. The user can select a scene first and then a vehicle, or a vehicle first and then a scene. Accordingly, the first determination module can be invoked first and then the second determination module, or the second determination module can be invoked first and then the first determination module.

[0125] In other embodiments, the interactive controls for selecting a scene and the interactive controls for selecting a vehicle are located on different pages. When the interactive controls for selecting a scene are located on the previous page and the interactive controls for selecting a vehicle are located on the next page, the first determination module is called first and then the second determination module is called. When the interactive controls for selecting a vehicle are located on the previous page and the interactive controls for selecting a scene are located on the next page, the second determination module is called first and then the first determination module is called.

[0126] The instruction sending module 530 is configured to send a device detection instruction to the target vehicle in response to a device detection operation triggered by the user on the application page, so as to start a device detection process corresponding to the target detection scenario information.

[0127] The user terminal's application page includes an interactive control for triggering device detection. The user can trigger the device detection operation by operating this interactive control. Upon detecting the user's device detection operation, the instruction sending module 530 sends the device detection instruction to the target vehicle. For example, if the target vehicle is a single unmanned vehicle, after the user triggers the device detection operation for that vehicle, the instruction sending module 530 sends the device detection instruction to that unmanned vehicle. If the target vehicle is multiple unmanned vehicles, after the user triggers the device detection operation for multiple unmanned vehicles, the instruction sending module 530 sends the device detection instruction to all of them.

[0128] After receiving the device detection instruction from the user terminal, the target vehicle starts the device detection process corresponding to the target detection scenario information. In some embodiments, the correspondence between the detection scenario and the device detection process is pre-configured. Exemplarily, the correspondence includes: a detection scenario identifier and a corresponding device detection process identifier. In these embodiments, after receiving the device detection instruction from the user terminal, the target vehicle can query the correspondence based on the target detection scenario information carried by the device detection instruction to determine the device detection process for the target detection scenario information. After the target vehicle completes the device detection process, it sends the device detection results to the user terminal.

[0129] In some embodiments, the instruction sending module 530 is also configured to: after detecting the device detection operation triggered by the user on the application page, determine whether a network connection has been established with the target vehicle; if a network connection has been established with the target vehicle, send a device detection instruction to the target vehicle; if a network connection has not been established with the target vehicle, display a network prompt message to the user, and after the user completes the operation of establishing a network connection with the target vehicle based on the network prompt message, send a device detection instruction to the target vehicle.

[0130] In the above embodiment, by determining whether a network connection has been established with the target vehicle, if the network connection has been established with the target vehicle, a device detection instruction is directly sent to the target vehicle without the need to perform a network connection operation again, thereby reducing resource consumption during the device detection process.

[0131] In some embodiments, the instruction sending module 530 is also configured to: determine whether the target vehicle has a historical detection record in a target detection scenario; if the target vehicle does not have a historical detection record in a target detection scenario, send a device detection instruction to the target vehicle; if the target vehicle has a historical detection record in a target detection scenario, display a prompt message to the user that there is a historical detection record; after receiving an instruction from the user to confirm re-detection of the target vehicle, send a device detection instruction to the target vehicle; after receiving an instruction from the user to confirm not to re-detect the target vehicle, do not send a device detection instruction to the target vehicle.

[0132] In the above embodiment, by determining whether the target vehicle has been detected and performing different operations based on different judgment results, unnecessary repeated detection of unmanned vehicles can be avoided, detection efficiency can be improved, and the user experience in unmanned vehicle equipment detection can be improved.

[0133] In some embodiments, the device detection apparatus further includes: an acquisition module configured to acquire the target vehicle's vehicle model information; and an instruction generation module configured to, upon successful acquisition of the target vehicle's vehicle model information, include the target vehicle's vehicle model information and target detection scenario information in a device detection instruction. Instruction sending module 530 is configured to, in response to a device detection operation triggered by a user on an application page, send a device detection instruction to the target vehicle to initiate a device detection process corresponding to the target detection scenario information and the target vehicle's vehicle model information.

[0134] In the above embodiment, the acquisition module and the instruction generation module can meet the needs of equipment testing in different testing scenarios and different vehicle models, further improving the applicability of the equipment testing process.

[0135] The result receiving module 540 is configured to receive the device detection result returned by the target vehicle.

[0136] In the disclosed embodiments, the above device allows users to initiate the device detection process for multiple unmanned vehicles with a simple web interface operation. This not only reduces the learning cost for users to conduct unmanned vehicle detection, improves ease of use, enhances the user experience, and improves the efficiency of unmanned vehicle detection. Furthermore, the above process can meet the user's detection needs for different detection scenarios and different vehicle models, improves the applicability of unmanned vehicle device detection, and further enhances the user experience.

[0137] Figure 6 FIG. 1 is a schematic diagram of the structure of a device detection apparatus according to other embodiments of the present disclosure. Figure 6 As shown, the equipment detection device of the embodiment of the present disclosure is set on an unmanned vehicle, including: an instruction receiving module 610, a detection starting module 620, and a result sending module 630.

[0138] The instruction receiving module 610 is configured to receive a device detection instruction sent by a user terminal, wherein the device detection instruction carries target detection scenario information.

[0139] Unmanned vehicles support a variety of inspection scenarios, each with its own corresponding device inspection process. In some embodiments, these scenarios include vehicle calibration and vehicle maintenance. These scenarios can be expanded based on specific needs during implementation.

[0140] The detection starting module 620 is configured to start a device detection process corresponding to the target detection scenario information according to the device detection instruction.

[0141] In some embodiments, a correspondence between a detection scenario and a device detection process is pre-set. In these embodiments, the detection initiation module 620 queries the correspondence based on the target detection scenario information carried in the device detection instruction to determine the device detection process corresponding to the target detection scenario information, and then initiates the device detection process.

[0142] In other embodiments, the device detection instruction carries not only the target detection scenario information but also the target vehicle model information. Furthermore, in these embodiments, a correspondence between the detection scenario, the vehicle model, and the device detection process is pre-set. In these embodiments, the detection initiation module 620 queries this correspondence based on the target detection scenario information and the vehicle model information carried in the device detection instruction to determine the device detection process corresponding to the target detection scenario information and the vehicle model information, and then initiates the device detection process.

[0143] In some embodiments, when the target detection scenario is a self-driving vehicle calibration detection scenario, the device detection process corresponding to the target detection scenario information includes a connectivity detection process for the self-driving vehicle's onboard devices. For example, the connectivity detection process for the self-driving vehicle's onboard devices includes connectivity detection items for at least one of the following devices: the self-driving vehicle's onboard camera, the self-driving vehicle's onboard radar, the vehicle-side control system, the onboard GPS sensor, and the onboard inertial sensor.

[0144] The result sending module 630 is configured to send the device detection result to the user terminal.

[0145] In the disclosed embodiments, the above device can meet user needs for device testing in various detection scenarios and for various vehicle types, improving the applicability of unmanned vehicle device testing. Users can initiate the device testing process for multiple unmanned vehicles with a simple interface operation on the user terminal. This not only reduces the learning cost for users to conduct unmanned vehicle testing, improves the user experience, but also increases the efficiency of unmanned vehicle testing.

[0146] Figure 7 is a block diagram illustrating a device detection apparatus according to some other embodiments of the present disclosure.

[0147] like Figure 7 As shown, device detection apparatus 700 includes a memory 710 and a processor 720 coupled to the memory 710. Memory 710 is configured to store instructions for executing embodiments corresponding to the device detection method. Processor 720 is configured to execute the device detection method according to any of the embodiments of the present disclosure based on the instructions stored in memory 710.

[0148] Figure 8 is a block diagram illustrating a computer system for implementing some embodiments of the present disclosure.

[0149] like Figure 8 As shown, computer system 800 may be implemented as a general-purpose computing device. Computer system 800 includes memory 810, processor 820, and bus 830 that connects various system components.

[0150] The memory 810 may include, for example, a system memory, a non-volatile storage medium, and the like. The system memory may store, for example, an operating system, application programs, a boot loader, and other programs. The system memory may include volatile storage media, such as random access memory (RAM) and / or cache memory. The non-volatile storage medium may store, for example, instructions for executing at least one of the corresponding embodiments of the device detection method. Non-volatile storage media include, but are not limited to, disk storage, optical storage, flash memory, and the like.

[0151] The processor 820 may be implemented using a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, or discrete hardware components such as discrete gates or transistors. Accordingly, each module, such as the first determination module and the second determination module, may be implemented by a central processing unit (CPU) executing instructions in a memory for executing corresponding steps, or by dedicated circuits for executing corresponding steps.

[0152] The bus 830 may use any of a variety of bus architectures, including, but not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, and a Peripheral Component Interconnect (PCI) bus.

[0153] Computer system 800 may also include input / output interfaces 840, a network interface 850, a storage interface 860, and the like. These interfaces 840, 850, and 860, as well as memory 810 and processor 820, may be connected via bus 830. Input / output interfaces 840 provide connection interfaces for input / output devices such as a display, mouse, and keyboard. Network interface 850 provides connection interfaces for various networked devices. Storage interface 860 provides connection interfaces for external storage devices such as floppy disks, USB flash drives, and SD cards.

[0154] Here, various aspects of the present disclosure are described with reference to flowcharts and / or block diagrams of methods, devices, and computer program products according to embodiments of the present disclosure. It should be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks, can be implemented by computer-readable program instructions.

[0155] These computer-readable program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable device to produce a machine, so that the processor executes the instructions to produce means for implementing the functions specified in one or more blocks in the flowcharts and / or block diagrams.

[0156] These computer-readable program instructions may also be stored in a computer-readable memory, which cause the computer to operate in a specific manner to produce an article of manufacture, including instructions for implementing the functions specified in one or more blocks in the flowcharts and / or block diagrams.

[0157] The present disclosure can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects.

[0158] The equipment detection method and device in the above embodiments can reduce the user's learning cost for unmanned vehicle detection, improve ease of use, improve the detection efficiency of unmanned vehicles, and meet the detection requirements of different detection scenarios, thereby improving the applicability of unmanned vehicle equipment detection.

[0159] Thus far, the device detection method and apparatus according to the present disclosure have been described in detail. To avoid obscuring the concept of the present disclosure, some details known in the art have not been described. Based on the above description, those skilled in the art will fully understand how to implement the technical solutions disclosed herein.

Claims

1. A device detection method, applied to a user terminal, comprising: Determine target detection scene information based on the scene selection operation triggered by the user on the application page; According to the vehicle selection operation triggered by the user on the application page, at least one unmanned vehicle is determined as the target vehicle; In response to a device detection operation triggered by a user on an application page, determining whether the target vehicle has a historical detection record in a target detection scenario; If there is no historical detection record for the target vehicle under the target detection scenario, sending a device detection instruction to the target vehicle to start a device detection process corresponding to the target detection scenario information; Receiving a device detection result returned by the target vehicle; Also includes: If the target vehicle has a historical detection record in a target detection scenario, not sending a device detection instruction to the target vehicle; or, If the target vehicle has a historical detection record in a target detection scenario, a prompt message indicating the existence of the historical detection record is displayed to the user; after receiving an instruction from the user to confirm re-detection of the target vehicle, a device detection instruction is sent to the target vehicle; after receiving an instruction from the user to confirm not to re-detect the target vehicle, the device detection instruction is not sent to the target vehicle.

2. The device detection method according to claim 1, wherein: Sending a device detection instruction to the target vehicle includes: Determining whether a network connection has been established with the target vehicle; When a network connection has been established with the target vehicle, sending a device detection instruction to the target vehicle; In the case where a network connection is not established with the target vehicle, a network prompt message is displayed to the user, and after the user completes an operation of establishing a network connection with the target vehicle based on the network prompt message, a device detection instruction is sent to the target vehicle.

3. The device detection method according to claim 1, further comprising: After determining the target detection scenario, switch to the interaction page corresponding to the target detection scenario to interact with the user based on the interaction page corresponding to the target detection scenario.

4. The device detection method according to claim 1, further comprising: Before sending a device detection instruction to the target vehicle, obtaining the model information of the target vehicle; When the model information of the target vehicle is successfully acquired, the model information of the target vehicle and the target detection scene information are carried in the device detection instruction.

5. The device detection method according to claim 4, wherein: Obtaining the target vehicle's model information includes: Send a vehicle model query request to the cloud server; Receive the target vehicle model information returned by the cloud server.

6. The device detection method according to claim 1, wherein: When the target detection scenario is an unmanned vehicle calibration detection scenario, the device detection process corresponding to the target detection scenario information includes a connectivity detection process of the unmanned vehicle's on-board equipment.

7. The device detection method according to claim 6, wherein the connectivity detection process of the unmanned vehicle-mounted device includes connectivity detection items of at least one of the following devices: Unmanned vehicle-mounted camera, unmanned vehicle-mounted radar, vehicle-side control system, vehicle-mounted GPS sensor, and vehicle-mounted inertial sensor.

8. A device detection device, provided in a user terminal, comprising: A first determination module is configured to determine target detection scene information according to a scene selection operation triggered by a user on an application page; A second determination module is configured to determine at least one unmanned vehicle as a target vehicle based on a vehicle selection operation triggered by a user on the application page; an instruction sending module configured to, in response to a device detection operation triggered by a user on an application page, determine whether the target vehicle has a historical detection record under a target detection scenario; and, if the target vehicle does not have a historical detection record under the target detection scenario, send a device detection instruction to the target vehicle to initiate a device detection process corresponding to the target detection scenario information; A result receiving module is configured to receive the device detection result returned by the target vehicle; Wherein, the instruction sending module is further configured to: If the target vehicle has a historical detection record in a target detection scenario, not sending a device detection instruction to the target vehicle; or If the target vehicle has a historical detection record in a target detection scenario, a prompt message indicating the existence of the historical detection record is displayed to the user; after receiving an instruction from the user to confirm re-detection of the target vehicle, a device detection instruction is sent to the target vehicle; after receiving an instruction from the user to confirm not to re-detect the target vehicle, the device detection instruction is not sent to the target vehicle.

9. A device detection apparatus, comprising: Memory; as well as A processor coupled to the memory, wherein the processor is configured to execute the device detection method according to any one of claims 1 to 7 based on instructions stored in the memory.

10. A computer-readable storage medium having computer program instructions stored thereon, wherein when the instructions are executed by a processor, the device detection method according to any one of claims 1 to 7 is implemented.

Images