Cabin area controller upgrading test device and method

Abstract

The invention discloses a cabin area controller upgrading test device and method. The device comprises a cabin area controller, an initialization unit, a control unit, a switch switching unit and a power supply unit. The first input end of the switch switching unit is connected with the initialization unit, the second input end of the switch switching unit is connected with the control unit, and the output end of the switch switching unit is connected with the cabin domain controller; the switch switching unit is used for controlling the on-off between the initialization unit and the cabin domain controller; the control unit is used for sending a test signal to the cabin domain controller and switching the cabin domain controller from an initial setting state to a test setting state; the first end of the power supply unit is connected with the cabin area controller, the second end of the power supply unit is connected with the control unit, the power supply unit is used for supplying power to the cabin area controller based on the first control signal sent by the control unit, the structure is compact, the cost is low, the stability and the reliability are higher, and the system is suitable for a laboratory environment where a large number of OTA tests need to be repeatedly carried out.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of upgrade testing, in particular to a cockpit domain controller upgrade testing device and method. BACKGROUND

[0002] Under the current development trend of automobile intelligence, the software function iteration and stability of the intelligent cockpit domain controller as the core component of the vehicle infotainment system increasingly rely on Over The Air (OTA) technology to realize upgrade. In order to ensure the reliability and user experience of the upgrade process, the OTA process must be fully tested.

[0003] The current common automatic testing method mainly relies on Android Debug Bridge (ADB) instructions to simulate screen clicking behavior in a software manner to trigger the upgrade task. In order to facilitate repeated testing, some setting switches are usually forced to remain in the on state in the test version, but this is completely different from the safety setting that the user will turn off by default after completing the upgrade in the actual mass production version, which cannot truly simulate the actual use scenario of the end user, thereby covering up various potential problems that may occur, and severely limiting the effectiveness and coverage of the test. SUMMARY

[0004] In order to solve the technical problem that the existing cockpit domain controller upgrade testing device cannot truly simulate the actual use scenario of the end user, the present application provides a cockpit domain controller upgrade testing device and method. By additionally setting an initialization unit and a switch switching unit, the initialization unit is connected to the cockpit domain controller by the switch switching unit before testing, so that the cockpit domain controller can be switched to the initialization setting after power-on, and then the control unit is connected to the cockpit domain controller by the switch switching unit for testing and switching to the test state, realizing the complete restoration of the real scenario used by the user, which can expose various problems that only occur in this environment, greatly improving the effectiveness and coverage of the test. At the same time, the pure hardware level upgrade testing device no longer relies on the software instruction simulation method that needs to keep ADB on, and has compact structure, low cost, higher stability and reliability, and is suitable for laboratory environment that needs to repeatedly perform a large number of OTA tests.

[0005] In the first aspect, the embodiments of the present application provide a cockpit domain controller upgrade testing method, which comprises a cockpit domain controller, an initialization unit, a control unit, a switch switching unit and a power supply unit; the cockpit domain controller comprises a test setting state and an initial setting state; The first input end of the switch switching unit is connected with the initialization unit, the second input end is connected with the control unit, and the output end is connected with the cabin domain controller; the switch switching unit is used for controlling the on-off between the initialization unit and the cabin domain controller; the control unit is used for sending a test signal to the cabin domain controller, and switching the cabin domain controller from an initial setting state to a test setting state; The first end of the power supply unit is connected with the cabin domain controller, and the second end is connected with the control unit, and is used for supplying power for the cabin domain controller based on the first control signal sent by the control unit; In the case that the power supply unit supplies power for the cabin domain controller and the cabin domain controller is in the connected state with the initialization unit, the cabin domain controller reads the initialization file stored in the initialization unit, and switches the cabin domain controller from the test setting state to the initial setting state.

[0006] In an optional embodiment, the initialization unit includes a U disk, and the U disk stores the initialization file, and the initialization file is used for switching the cabin domain controller to the initial setting state.

[0007] In an optional embodiment, the switch switching unit includes a first host computer and a relay; the first host computer is in communication connection with the relay, sends a switching signal to the relay, and controls the cabin domain controller to be connected with the U disk or the control unit.

[0008] In an optional embodiment, the cabin domain controller includes a plurality of different test setting states and a plurality of corresponding initial setting states; The initialization unit includes a second host computer and an initialization simulator; The second host computer is in communication connection with the initialization simulator, sends different generation signals to the initialization simulator, and is used for making the initialization simulator generate initialization files corresponding to the different generation signals; the initialization files corresponding to the different generation signals are used for switching the plurality of different test setting states to the plurality of corresponding initial setting states.

[0009] In an optional embodiment, the initial setting state represents that the ADB switch of the cabin domain controller is in an open state, and the test setting state represents that the ADB switch is in a closed state.

[0010] In an optional embodiment, the number of the cabin domain controllers is configured to be multiple, and the number of the switch switching units is also configured to be multiple; The first input ends of the plurality of switch switching units are respectively connected with the initialization unit, the output ends of the plurality of switch switching units are respectively connected with the plurality of cabin domain controllers, and the second input ends of the plurality of switch switching units are connected with the control unit; The power supply unit is connected with the plurality of cabin domain controllers, and supplies power for the plurality of cabin domain controllers based on the first control signal of the control unit.

[0011] In a second aspect, the embodiments of the present application provide a cockpit domain controller upgrade test method, applied to the cockpit domain controller upgrade test device in the first aspect, comprising: The switch switching unit is connected with the cockpit domain controller and the initialization unit; The control unit sends a first control signal to the power supply unit to control the power supply unit to supply power to the cockpit domain controller; The cockpit domain controller reads the initialization file stored in the initialization unit; The cockpit domain controller switches from the self-test setting state to the initial setting state based on the initialization file; The switch switching unit is connected with the cockpit domain controller and the control unit; The control unit sends a test signal to the cockpit domain controller; The cockpit domain controller performs upgrade test based on the test signal and switches from the initial setting state to the test setting state.

[0012] In an optional embodiment, the initial setting state represents that the ADB switch of the cockpit domain controller is in an open state, and the test setting state represents that the ADB switch is in a closed state; the initialization file includes ADB switch state information. The cockpit domain controller switches from the self-test setting state to the initial setting state based on the initialization file, comprising: The cockpit domain controller parses and obtains the ADB switch state information in the initialization file; The cockpit domain controller switches the ADB switch from the closed state to the open state based on the ADB switch state information.

[0013] In an optional embodiment, the initialization unit includes a second host computer and an initialization simulator. Before the cockpit domain controller reads the initialization file stored in the initialization unit, further comprising: The second host computer receives a setting switching instruction input by a user; the setting switching instruction includes a setting switch to be initialized; The second host computer generates a generated signal corresponding to the setting switching instruction, and sends the generated signal to the initialization simulator; The initialization simulator generates an initialization file corresponding to the setting switch based on the generated signal.

[0014] In an optional embodiment, the initial setting state represents that the ADB switch of the cockpit domain controller is in an open state, and the test setting state represents that the ADB switch is in a closed state; the test signal includes an ADB instruction. The cockpit domain controller performs upgrade test based on the test signal and switches from the initial setting state to the test setting state, comprising: The cockpit domain controller performs an upgrade test by clicking the corresponding location on the cockpit domain controller screen using ADB commands. After the upgrade test is completed, the cockpit domain controller switches from the initial setting state to the test setting state.

[0015] Thirdly, embodiments of this application provide an electronic device, which includes a processor and a memory. The memory stores at least one instruction, at least one program, code set, or instruction set. The processor loads and executes the at least one instruction, at least one program, code set, or instruction set to implement the cockpit domain controller upgrade test method of the second aspect.

[0016] Fourthly, embodiments of this application provide a computer-readable storage medium storing at least one instruction or at least one program, wherein the at least one instruction or at least one program is loaded and executed by a processor to implement the cockpit domain controller upgrade test method of the second aspect.

[0017] Fifthly, embodiments of this application provide a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the cockpit domain controller upgrade testing method of the second aspect.

[0018] The technical solution provided in this application has the following technical effects: The cockpit domain controller upgrade testing device of this application includes a cockpit domain controller, an initialization unit, a control unit, a switch unit, and a power supply unit. The cockpit domain controller includes a test setting state and an initial setting state. The first input terminal of the switch unit is connected to the initialization unit, the second input terminal is connected to the control unit, and the output terminal is connected to the cockpit domain controller. The switch unit is used to control the connection and disconnection between the initialization unit and the cockpit domain controller. The control unit is used to send a test signal to the cockpit domain controller to switch the cockpit domain controller from the initial setting state to the test setting state. The first terminal of the power supply unit is connected to the cockpit domain controller, and the second terminal is connected to the control unit. It is used to supply power to the cockpit domain controller based on the first control signal sent by the control unit. When the power supply unit supplies power to the cockpit domain controller and the cockpit domain controller and the initialization unit are connected, the cockpit domain controller reads the initialization file stored in the initialization unit and switches the cockpit domain controller from the test setting state to the initial setting state. In this embodiment, by additionally setting an initialization unit and a switch switching unit, the initialization unit is connected to the cockpit domain controller before testing using the switch switching unit. This allows the cockpit domain controller to switch to the initialization setting after power-on. Then, the switch switching unit connects the controller to the cockpit domain controller for testing and switches to the test state. This fully replicates the real-world user scenario and exposes various problems that only occur in this environment, greatly improving the effectiveness and coverage of the test. At the same time, the pure hardware-level upgrade test device no longer relies on software command simulation methods that require keeping ADB enabled. It has a compact structure, low cost, higher stability and reliability, and is suitable for laboratory environments that require repeated and extensive OTA testing. Attached Figure Description

[0019] To more clearly illustrate the technical solutions and advantages in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a schematic diagram of a cockpit domain controller upgrade testing device provided in an embodiment of this application. Figure 1 ; Figure 2 This is a schematic diagram of a cockpit domain controller upgrade testing device provided in an embodiment of this application. Figure 2 ; Figure 3 This is a schematic diagram of a cockpit domain controller upgrade testing device provided in an embodiment of this application. Figure 3 ; Figure 4This is a flowchart illustrating a cockpit domain controller upgrade testing method provided in an embodiment of this application. Figure 1 ; Figure 5 This is a flowchart illustrating a cockpit domain controller upgrade testing method provided in an embodiment of this application. Figure 2 ; Figure 6 This is a flowchart illustrating a method for generating an initialization file according to an embodiment of this application; Figure 7 This is a hardware structure block diagram of a server for a cockpit domain controller upgrade testing method provided in an embodiment of this application.

[0021] Figure label: 101. Cockpit Domain Controller; 102. Initialization Unit; 112. Second Host Computer; 122. Initialization Simulator; 103. Control Unit; 104. Switching Unit; 114. First Host Computer; 124. Relay; 105. Power Supply Unit. Detailed Implementation

[0022] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0023] It should be noted that the term "an embodiment" or "embodiment" in the specification of the embodiments of this application refers to a specific feature, structure, or characteristic that can be included in at least one implementation of this application. It should be understood that in the specification, claims, and accompanying drawings of the embodiments of this application, the terms "upper," "lower," "top," "bottom," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the drawings, and are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation on this application. The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined with "first" and "second" may explicitly or implicitly include one or more of that feature. Moreover, the terms "first," "second," etc., are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, in the description of this embodiment, unless otherwise stated, "a plurality of" means two or more. Additionally, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, for example, a process, method, system, or product that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0024] It should be understood that when a device or component is referred to as being "on," "adjacent to," or "connected to" other devices or components, it may be directly on, adjacent to, or connected to other devices or components, or there may be intervening devices or components. Conversely, when a device or component is referred to as being "directly on," "directly adjacent to," or "directly connected to" other devices or components, there are no intervening devices or components. It should be understood that although the terms first, second, third, etc., may be used to describe various components, areas, layers, and / or parts, these components, areas, layers, and / or parts should not be limited by these terms. These terms are only used to distinguish one component, area, layer, or part from another component, area, layer, or part. Therefore, without departing from the teachings of this application, the first component, area, layer, or part discussed below may be referred to as the second component, area, layer, or part. And the discussion of the second component, area, layer, or part does not imply that the first component, area, layer, or part necessarily exists in this application.

[0025] To make the objectives, technical solutions, and advantages disclosed in the embodiments of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are merely illustrative of the embodiments of this application and are not intended to limit the embodiments of this application.

[0026] This application provides a cockpit domain controller upgrade testing device. Figure 1 This is a schematic diagram of a cockpit domain controller upgrade testing device provided in an embodiment of this application. Figure 1 ,like Figure 1 As shown, the cockpit domain controller upgrade test device includes a cockpit domain controller 101, an initialization unit 102, a control unit 103, a switch switching unit 104, and a power supply unit 105.

[0027] In this embodiment, the cockpit domain controller 101 includes an initial setup state and a test setup state.

[0028] The initial setup state refers to the state where the software environment of the cockpit domain controller 101 is completely consistent with the mass-production version delivered to the end user. Taking the Android Debug Bridge (ADB) debugging permission setting as an example, in the initial setup state, the ADB setting is off by default. All other user preference settings and system parameters are at factory default values. This state is designed to accurately simulate the pristine environment when a real user first starts the vehicle cockpit system. It is a reliable and unique starting point for every Over-The-Air (OTA) upgrade test, ensuring the authenticity and repeatability of the test scenario.

[0029] Test setup state refers to the system state that allows the execution of OTA upgrade process tests. In the test setup state, the system may contain temporary configurations necessary to trigger the upgrade process or allow specific debugging operations. This state is a temporary state during the test.

[0030] like Figure 1 As shown, the first input terminal of the switch switching unit 104 is connected to the initialization unit 102, the second input terminal is connected to the control unit 103, and the output terminal is connected to the cockpit domain controller 101. The switch switching unit 104 is used to control the connection and disconnection between the initialization unit 102 and the cockpit domain controller 101. The control unit 103 is used to send a test signal to the cockpit domain controller 101, switching the cockpit domain controller 101 from the initial setting state to the test setting state.

[0031] In the first state, the first input terminal of the switch switching unit 104 is connected to the initialization unit 102, and the output terminal is connected to the cockpit domain controller 101, so that the cockpit domain controller 101 is connected to the initialization unit 102 and can perform initialization operations.

[0032] In the second state, the second input terminal of the switch switching unit 104 is connected to the control unit 103, and the output terminal is connected to the cockpit domain controller 101, so that the cockpit domain controller 101 is connected to the initialization unit 102 and can perform test operations.

[0033] In one possible embodiment, the power supply unit 105 is a programmable power supply, with its first end connected to the cockpit domain controller 101 and its second end connected to the control unit 103, for supplying power to the cockpit domain controller 101 based on a first control signal sent by the control unit 103.

[0034] When the power supply unit 105 supplies power to the cockpit domain controller 101 and the cockpit domain controller 101 is connected to the initialization unit 102, the cockpit domain controller 101 can read the initialization file stored in the initialization unit 102 and switch the cockpit domain controller 101 from the self-test setting state to the initial setting state.

[0035] In this embodiment, by additionally setting an initialization unit 102 and a switch switching unit 104, the initialization unit 102 is connected to the cockpit domain controller 101 using the switch switching unit 104 before testing. This allows the cockpit domain controller 101 to be switched to the initialization setting after power-on. Then, the switch switching unit 104 connects the controller to the cockpit domain controller 101 for testing and switches to the test state. This fully replicates the real-world user scenario and exposes various problems that only occur in this environment, greatly improving the effectiveness and coverage of the test. At the same time, the pure hardware-level upgrade test device no longer relies on software command simulation methods that require keeping ADB enabled. It has a compact structure, low cost, higher stability and reliability, and is suitable for laboratory environments that require repeated and extensive OTA testing.

[0036] Continue as Figure 2 As shown, in an optional embodiment, the initialization unit 102 includes a USB flash drive containing an initialization file, which is used to switch the cockpit domain controller 101 to the initial setting state.

[0037] Figure 2 This is a schematic diagram of an upgrade and testing device for a cockpit domain controller 101 provided in an embodiment of this application. Figure 3In one optional embodiment, the switch switching unit 104 includes a first host computer 114 and a relay 124. The first host computer 114 and the relay 124 are communicatively connected. The first host computer 114 sends a switching signal to the relay 124 to control the cockpit domain controller 101 to connect to the USB flash drive or to the control unit 103.

[0038] In one optional embodiment, the initial setup state indicates that the ADB switch of the cockpit domain controller 101 is in the on state, and the test setup state indicates that the ADB switch is in the off state.

[0039] In another alternative embodiment, the cockpit domain controller 101 includes multiple different test setting states and multiple corresponding initial setting states, with the ADB switch being one of the multiple settings.

[0040] The initialization unit 102 includes a second host computer 112 and an initialization simulator 122. The initialization simulator 122 can generate different initialization files. The second host computer 112 is connected to the initialization simulator 122 and sends different generation signals to the initialization simulator 122 to enable the initialization simulator 122 to generate initialization files corresponding to different generation signals. The initialization files corresponding to different generation signals are used to switch multiple different test setting states to multiple corresponding initial setting states.

[0041] Specifically, the initialization simulator 122 includes a main control chip, a communication interface module for communicating with the second host computer 112 and the cockpit domain controller 101, and a storage module. The storage module can be configured as a Flash memory, which pre-stores various different configuration file templates. The main control chip listens for instructions sent by the second host computer 112, selects the corresponding configuration file according to the instructions, switches the contents of its simulated USB storage device to that file, waits for the cockpit domain controller 101 to read it, and switches the corresponding settings to the initial mode.

[0042] Figure 3 This is a schematic diagram of an upgrade and testing device for a cockpit domain controller 101 provided in an embodiment of this application. Figure 4 In one optional embodiment, the number of cockpit domain controllers 101 is configured to be multiple, and the number of switch switching units 104 is also configured to be multiple.

[0043] The first input terminals of the multiple switch switching units 104 are respectively connected to the initialization unit 102, the output terminals of the multiple switch switching units 104 are respectively connected to the multiple cockpit domain controllers 101, and the second input terminals of the multiple switch switching units 104 are connected to the control unit 103.

[0044] The power supply unit 105 is connected to multiple cockpit domain controllers 101 and supplies power to the multiple cockpit domain controllers 101 based on the first control signal of the control unit 103.

[0045] With the above settings, parallel testing of multiple cockpit domain controllers 101 can be achieved, effectively improving testing efficiency.

[0046] The following describes a specific embodiment of a cockpit domain controller upgrade testing method according to this application. Figure 1 This is a flowchart illustrating a cockpit domain controller upgrade testing method provided in an embodiment of this application. Figure 4 This specification provides method operation steps as shown in the embodiments or flowcharts, but based on conventional or non-inventive labor, more or fewer operation steps may be included. The order of steps listed in the embodiments is merely one possible execution order among many and does not represent the only execution order. In actual system or server products, the methods shown in the embodiments or drawings can be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment). Specifically, as shown in the embodiments or drawings... Figure 5 As shown, this method, applied to a cockpit domain controller upgrade testing device, may include: S201: The switch switching unit connects the cockpit domain controller and the initialization unit.

[0047] S202: The control unit sends a first control signal to the power supply unit to control the power supply unit to supply power to the cockpit domain controller.

[0048] S203: The cockpit domain controller reads the initialization file stored in the initialization unit.

[0049] S204: The cockpit domain controller switches from self-test setting state to initial setting state based on the initialization file.

[0050] S205: Switching unit connects the cockpit domain controller and control unit.

[0051] S206: The control unit sends a test signal to the cockpit domain controller.

[0052] S207: The cockpit domain controller performs upgrade testing based on test signals and switches from the initial setting state to the test setting state.

[0053] Figure 2 This is a flowchart illustrating a cockpit domain controller upgrade testing method provided in an embodiment of this application. Figure 6 The method may include: S301: The switch switching unit connects the cockpit domain controller and the initialization unit.

[0054] Specifically, the first host computer sends a switching signal to the relay to control the cockpit domain controller to connect to the USB flash drive.

[0055] S302: The control unit sends a first control signal to the power supply unit to control the power supply unit to supply power to the cockpit domain controller.

[0056] In this embodiment of the application, the control unit sends a first control signal to the programmable power supply, causing the power supply unit to supply power to the cockpit domain controller.

[0057] S303: The cockpit domain controller reads the initialization file stored in the initialization unit.

[0058] In this embodiment of the application, the cockpit domain controller reads the initialization file stored in the USB flash drive after power-on.

[0059] S304: The cockpit domain controller switches from self-test setting state to initial setting state based on the initialization file.

[0060] In one optional embodiment, the initial setup state indicates that the ADB switch of the cockpit domain controller is in the ON state, and the test setup state indicates that the ADB switch is in the OFF state. The ADB switch status information is initialized.

[0061] In one optional embodiment, the cockpit domain controller switches from a self-test setting state to an initial setting state based on an initialization file, including: S3041: The cockpit domain controller parses and obtains the ADB switch status information from the initialization file.

[0062] S3042: The cockpit domain controller switches the ADB switch from the off state to the on state based on the ADB switch status information.

[0063] S305: Switching unit connects the cockpit domain controller and control unit.

[0064] Specifically, the first host computer sends a switching signal to the relay to control the connection between the cockpit domain controller and the control unit.

[0065] S306: The control unit sends a test signal to the cockpit domain controller.

[0066] S307: The cockpit domain controller performs upgrade testing based on test signals and switches from the initial setting state to the test setting state.

[0067] In this embodiment, the control unit sends a test signal to the cockpit domain controller, and the cockpit domain controller performs OTA testing based on the test signal.

[0068] In an alternative embodiment, the test signal includes an ADB command.

[0069] In one optional embodiment, the cockpit domain controller performs upgrade testing based on test signals and switches from an initial setup state to a test setup state, including: S3071: The cockpit domain controller performs an upgrade test by clicking the corresponding location on the cockpit domain controller screen using ADB commands.

[0070] S3072: After the upgrade test is completed, the cockpit domain controller switches from the initial setting state to the test setting state.

[0071] Through the above steps, the initialization unit is connected to the cockpit domain controller using a switch unit before testing. This allows the cockpit domain controller to be switched to the initialization setting after power-on. Then, the control unit is connected to the cockpit domain controller using the switch unit for testing. The system is then switched to test mode, fully replicating the real-world user scenario. This exposes various problems that only occur in this environment, greatly improving the effectiveness and coverage of the test. At the same time, the pure hardware-level upgrade test device no longer relies on software command simulation methods that require ADB to be enabled. It has a compact structure, low cost, and higher stability and reliability, making it suitable for laboratory environments that require repeated and extensive OTA testing.

[0072] In one alternative embodiment, the initialization unit includes a second host computer and an initialization simulator, the initialization simulator being used to simulate the generation of different initialization files. Figure 7 This is a flowchart illustrating a method for generating an initialization file according to an embodiment of this application. Before the cockpit domain controller reads the initialization file stored in the initialization unit, the method further includes: S401: The second host computer receives the setting switching command input by the user.

[0073] In one alternative embodiment, the setting switching instruction includes a setting switch that needs to be initialized.

[0074] S402: The second host computer generates the generation signal corresponding to the setting switching command and sends the generation signal to the initialization simulator.

[0075] S403: Initialize the simulator to generate the initialization file corresponding to the setting switch based on the generated signal.

[0076] The user inputs a setting switching command, specifying the setting switch that needs to be switched between the initialization state and the test state. The second host computer can generate the corresponding generation signal according to the specified setting switch and send the generation signal to the initialization simulator. The initialization simulator can generate the corresponding initialization file and read the initialization file when the cockpit domain controller is powered on.

[0077] Through the above steps, this embodiment realizes the on-demand and dynamic generation of initialization files, which greatly improves the flexibility and automation of testing. Testers do not need to manually prepare and replace multiple storage devices. They only need to select the configuration through the host computer interface, and the system can automatically complete the preparation of the initialization environment.

[0078] The apparatus and method embodiments in this application are based on the same application concept.

[0079] The methods and embodiments provided in this application can be executed on a computer terminal, server, or similar computing device. Taking running on a server as an example, Figure 7 This is a hardware structure block diagram of the server for a cockpit domain controller upgrade testing method provided in an embodiment of this application. Figure 7 As shown, the server 500 can vary significantly due to different configurations or performance. It may include one or more central processing units (CPUs) 510 (CPUs 510 may include, but are not limited to, microprocessors such as MCUs or programmable logic devices such as FPGAs), a memory 530 for storing data, and one or more storage media 520 (e.g., one or more mass storage devices) for storing application programs 523 or data 522. The memory 530 and storage media 520 may be temporary or persistent storage. The program stored in the storage media 520 may include one or more modules, each module may include a series of instruction operations on the server. Furthermore, the CPU 510 may be configured to communicate with the storage media 520 and execute the series of instruction operations stored in the storage media 520 on the server 500. Server 500 may also include one or more power supplies 560, one or more wired or wireless network interfaces 550, one or more input / output interfaces 540, and / or one or more operating systems 521, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.

[0080] The input / output interface 540 can be used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of server 500. In one example, the input / output interface 540 includes a network interface controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the input / output interface 540 may be a radio frequency (RF) module used for wireless communication with the Internet.

[0081] Those skilled in the art will understand that Figure 7 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, server 500 may also include components that are more... Figure 7 The more or fewer components shown, or having the same ​ The different configurations shown.

[0082] This application provides an electronic device, which includes a processor and a memory. The memory stores at least one instruction, at least one program, code set, or instruction set. The processor loads and executes the at least one instruction, at least one program, code set, or instruction set to implement the above-described data processing method.

[0083] Embodiments of this application also provide a computer-readable storage medium, which can be disposed in a server to store at least one instruction, at least one program, code set, or instruction set related to implementing a cockpit domain controller upgrade test method in the method embodiment. The at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the above-described cockpit domain controller upgrade test method.

[0084] Optionally, in this embodiment, the storage medium may be located at at least one of the multiple network servers in a computer network. Optionally, in this embodiment, the storage medium may include, but is not limited to, various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0085] As can be seen from the embodiments of the cockpit domain controller upgrade testing method provided in this application, in this application, the switch switching unit connects the cockpit domain controller and the initialization unit; the control unit sends a first control signal to the power supply unit to control the power supply unit to supply power to the cockpit domain controller; the cockpit domain controller reads the initialization file stored in the initialization unit; the cockpit domain controller switches from the test setting state to the initial setting state based on the initialization file; the switch switching unit connects the cockpit domain controller and the control unit; the control unit sends a test signal to the cockpit domain controller; the cockpit domain controller performs upgrade testing based on the test signal and switches from the initial setting state to the test setting state. In this embodiment, by additionally setting an initialization unit and a switch switching unit, the initialization unit is connected to the cockpit domain controller before testing using the switch switching unit. This allows the cockpit domain controller to switch to the initialization setting after power-on. Then, the switch switching unit connects the controller to the cockpit domain controller for testing and switches to the test state. This fully replicates the real-world user scenario and exposes various problems that only occur in this environment, greatly improving the effectiveness and coverage of the test. At the same time, the pure hardware-level upgrade test device no longer relies on software command simulation methods that require keeping ADB enabled. It has a compact structure, low cost, higher stability and reliability, and is suitable for laboratory environments that require repeated and extensive OTA testing.

[0086] It should be noted that the order of the embodiments described above is merely for descriptive purposes and does not represent the superiority or inferiority of the embodiments. Furthermore, specific embodiments have been described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims can be performed in a different order than that shown in the embodiments and still achieve the desired result. Additionally, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0087] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the device embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0088] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0089] The above description is only a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A cockpit domain controller upgrade testing device, characterized in that, It includes a cockpit domain controller, an initialization unit, a control unit, a switch switching unit, and a power supply unit; the cockpit domain controller includes a test setting state and an initial setting state; The first input terminal of the switch switching unit is connected to the initialization unit, the second input terminal is connected to the control unit, and the output terminal is connected to the cockpit domain controller; the switch switching unit is used to control the connection and disconnection between the initialization unit and the cockpit domain controller; the control unit is used to send a test signal to the cockpit domain controller to switch the cockpit domain controller from the initial setting state to the test setting state; The first end of the power supply unit is connected to the cockpit domain controller, and the second end is connected to the control unit, for supplying power to the cockpit domain controller based on the first control signal sent by the control unit; When the power supply unit supplies power to the cockpit domain controller and the cockpit domain controller is connected to the initialization unit, the cockpit domain controller reads the initialization file stored in the initialization unit and switches the cockpit domain controller from the test setting state to the initial setting state.

2. The cockpit domain controller upgrade testing device according to claim 1, characterized in that, The initialization unit includes a USB flash drive containing the initialization file, which is used to switch the cockpit domain controller to the initial setting state.

3. The cockpit domain controller upgrade testing device according to claim 2, characterized in that, The switch unit includes a first host computer and a relay; the first host computer is communicatively connected to the relay, and sends a switching signal to the relay to control the cockpit domain controller to connect to the USB flash drive or to the control unit.

4. The cockpit domain controller upgrade testing device according to claim 1, characterized in that, The cockpit domain controller includes multiple different test setting states and multiple corresponding initial setting states; The initialization unit includes a second host computer and an initialization simulator; The second host computer communicates with the initialization simulator and sends different generation signals to the initialization simulator to cause the initialization simulator to generate initialization files corresponding to the different generation signals; the initialization files corresponding to the different generation signals are used to switch multiple different test setting states to multiple corresponding initial setting states.

5. The cockpit domain controller upgrade testing device according to claim 1, characterized in that, The initial setup state indicates that the ADB switch of the cockpit domain controller is in the on state, and the test setup state indicates that the ADB switch is in the off state.

6. The cockpit domain controller upgrade testing system according to claim 1, characterized in that, The number of cockpit domain controllers is configured to be multiple, and the number of switch switching units is also configured to be multiple; The first input terminals of the plurality of switch switching units are respectively connected to the initialization unit, the output terminals of the plurality of switch switching units are respectively connected to the plurality of cockpit domain controllers, and the second input terminals of the plurality of switch switching units are connected to the control unit; The power supply unit is connected to multiple cockpit domain controllers and supplies power to the multiple cockpit domain controllers based on the first control signal of the control unit.

7. A cockpit domain controller upgrade testing method, characterized in that, The cockpit domain controller upgrade test apparatus according to any one of claims 1-6 comprises: The switch unit is connected to the cockpit domain controller and the initialization unit; The control unit sends the first control signal to the power supply unit to control the power supply unit to supply power to the cockpit domain controller; The cockpit domain controller reads the initialization file stored in the initialization unit; The cockpit domain controller switches from the test setting state to the initial setting state based on the initialization file; The switch unit connects the cockpit domain controller and the control unit; The control unit sends the test signal to the cockpit domain controller; The cockpit domain controller performs an upgrade test based on the test signal and switches from the initial setting state to the test setting state.

8. The cockpit domain controller upgrade testing method according to claim 7, characterized in that, The initial setup state indicates that the ADB switch of the cockpit domain controller is in the on state, and the test setup state indicates that the ADB switch is in the off state; the initialization file includes ADB switch status information; The cockpit domain controller switches from the test setting state to the initial setting state based on the initialization file, including: The cockpit domain controller parses and obtains the ADB switch status information in the initialization file; The cockpit domain controller switches the ADB switch from the off state to the on state based on the ADB switch status information.

9. A cockpit domain controller upgrade testing method according to claim 7, characterized in that, The initialization unit includes a second host computer and an initialization simulator; Before the cockpit domain controller reads the initialization file stored in the initialization unit, the method further includes: The second host computer receives a setting switching command input by the user; the setting switching command includes a setting switch that needs to be initialized; The second host computer generates a generation signal corresponding to the setting switching command and sends the generation signal to the initialization simulator; The initialization simulator generates the initialization file corresponding to the setting switch based on the generated signal.

10. A cockpit domain controller upgrade testing method according to claim 7, characterized in that, The initial setup state indicates that the ADB switch of the cockpit domain controller is in the on state, and the test setup state indicates that the ADB switch is in the off state; the test signal includes ADB commands; The cockpit domain controller performs upgrade testing based on the test signal and switches from the initial setting state to the test setting state, including: The cockpit domain controller performs an upgrade test by clicking the corresponding location on the cockpit domain controller screen based on the ADB command. After the upgrade test is completed, the cockpit domain controller switches from the initial setting state to the test setting state.

Images