Control method, data transmission method, first electronic equipment and control system

Abstract

The embodiment of the invention provides a control method which is applied to first electronic equipment, the first electronic equipment can be in communication connection with a target device, the target device is not supported by a firmware interface system of the first electronic equipment, and the method comprises the steps that in response to a target event, the firmware interface system is controlled to be in a target mode, the first electronic equipment is used for communicating with second electronic equipment in the target mode; in the target mode, first data is obtained from the second electronic equipment, and the first data is data capable of enabling the target device to be supported by the firmware interface system; and starting the firmware interface system based on the first data. The embodiment of the invention further provides a data transmission method, the first electronic equipment and a control system.

Description

Technical Field

[0001] The present disclosure relates to a control method, a data transmission method, a first electronic device, and a control system. Background Art

[0002] During the use and maintenance of electronic devices, users sometimes upgrade or add hardware to them based on their needs, such as adding a discrete graphics card to a computer motherboard to improve performance. However, these newly added devices are often not supported by the electronic device, resulting in the device not functioning properly. Summary of the Invention

[0003] A first aspect of the present disclosure provides a control method, applied to a first electronic device, wherein the first electronic device is capable of communicating with a target device, and the target device is not supported by a firmware interface system of the first electronic device, the method comprising:

[0004] In response to a target event, controlling the firmware interface system to be in a target mode, wherein the first electronic device is used to communicate with a second electronic device in the target mode;

[0005] obtaining, in the target mode, the first data from the second electronic device, the first data being data enabling the target device to be supported by the firmware interface system;

[0006] Based on the first data, the firmware interface system is started.

[0007] According to an embodiment of the present disclosure, the first electronic device includes a control element, which is a physical switch and / or a software switch, and is configured to:

[0008] In the on state, controlling the firmware interface system to be in a target mode, so that the first electronic device is used to communicate with the second electronic device to obtain the first data;

[0009] In a closed state, controlling the firmware interface system to be in an initialization mode, so that the firmware interface system loads target data, wherein the target data includes first data;

[0010] In response to the target event, controlling the firmware interface system to be in target mode includes:

[0011] In response to the control element being in the on state, the firmware interface system is controlled to be in the target mode.

[0012] According to an embodiment of the present disclosure, obtaining the first data includes:

[0013] Sending first information to the second electronic device, where the first information at least includes device identification information corresponding to the first electronic device;

[0014] acquiring the first data based on a first mapping relationship table stored in the second electronic device;

[0015] The first mapping relationship table at least includes a mapping relationship between the device identification information of the first electronic device and the first data.

[0016] According to an embodiment of the present disclosure, the first data is generated based on device identification information of the target apparatus; or,

[0017] The first data is generated based on device identification information of the target apparatus and second information, where the second information is information generated based on a user portrait and / or information pre-input by the user.

[0018] According to an embodiment of the present disclosure, after obtaining the first data, the method includes:

[0019] storing the first data in a first data list, where the first data list is used to store the first data and second data, where the second data is data that enables the target device to be supported by the firmware interface system, and the second data is different from the first data;

[0020] The starting the firmware interface system based on the first data includes:

[0021] Acquire first data from the first data list, and start the firmware interface system based on the first data;

[0022] In the case that starting the firmware interface system fails, the second data is obtained from the first data list, and the firmware interface system is started.

[0023] A second aspect of the present disclosure provides a data transmission method, applied to a second electronic device, wherein the second electronic device is communicatively connected to a first electronic device, the first electronic device is communicatively connected to a target device, and a firmware interface system of the first electronic device does not support the target device. The method includes:

[0024] In response to obtaining a communication request initiated by the first device in the target mode, establishing a communication connection with the first electronic device;

[0025] First data is sent to the first electronic device, where the first data is data that enables the target device to be supported by the firmware interface system, so that the first electronic device starts the firmware interface system based on the first data.

[0026] A third aspect of the present disclosure provides a first electronic device capable of communicating with a target device that is not supported by a firmware interface system of the first electronic device. The electronic device includes:

[0027] A control module, configured to control the firmware interface system to be in a target mode in response to a target event, wherein the first electronic device is configured to communicate with a second electronic device in the target mode;

[0028] An obtaining module, configured to obtain the first data from the second electronic device in the target mode, wherein the first data is data enabling the target device to be supported by the firmware interface system;

[0029] A configuration module is configured to start the firmware interface system based on the first data.

[0030] According to an embodiment of the present disclosure, the control module is a physical switch and / or a software switch, and the control module is used to:

[0031] In the on state, controlling the firmware interface system to be in a target mode, so that the first electronic device is used to communicate with the second electronic device to obtain the first data;

[0032] In the closed state, the firmware interface system is controlled to be in an initialization mode, so that the firmware interface system loads target data, where the target data includes first data.

[0033] The fourth aspect of the present disclosure also provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the control method or data transmission method as described above.

[0034] A fifth aspect of the present disclosure provides a non-volatile storage medium storing computer-executable instructions, which, when executed, are used to implement the control method or data transmission method described above.

[0035] A sixth aspect of the present disclosure provides a computer program, which includes computer-executable instructions, and the instructions are used to implement the control method or data transmission method described above when executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] For a more complete understanding of the present disclosure and its advantages, reference will now be made to the following description taken in conjunction with the accompanying drawings, in which:

[0037] Figure 1The application scenarios of the control method and the data transmission method according to the embodiments of the present disclosure are schematically shown;

[0038] Figure 2 The flowchart of the control method according to the embodiment of the present disclosure is schematically shown;

[0039] Figure 3A Schematically shows a schematic diagram of a physical switch according to an embodiment of the present disclosure;

[0040] Figure 3B A schematic diagram of a software switch according to an embodiment of the present disclosure is schematically shown;

[0041] Figure 4 The flowchart of the data transmission method according to the embodiment of the present disclosure is schematically shown;

[0042] Figure 5 Schematically shows a block diagram of a first electronic device according to an embodiment of the present disclosure;

[0043] Figure 6 Schematically shows a block diagram of a second electronic device according to an embodiment of the present disclosure;

[0044] Figure 7 Schematically shows a block diagram of an electronic device according to an embodiment of the present disclosure;

[0045] Figure 8 A block diagram of a control system according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0046] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are merely exemplary and are not intended to limit the scope of the present disclosure. In the detailed description below, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0047] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise," "include," etc. used herein indicate the presence of the features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0048] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0049] When expressions such as "at least one of A, B, and C, etc." are used, they should generally be interpreted in accordance with the meaning commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to systems having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, and C, etc.). When expressions such as "at least one of A, B, or C, etc." are used, they should generally be interpreted in accordance with the meaning commonly understood by those skilled in the art (for example, "a system having at least one of A, B, or C" should include but is not limited to systems having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, and C, etc.). Those skilled in the art should also understand that any transitional conjunctions and / or phrases indicating two or more optional items, whether in the specification, claims, or drawings, should be understood to provide the possibility of including one, either, or both of these items. For example, the phrase "A or B" should be understood to include the possibilities of "A" or "B", or "A and B".

[0050] The accompanying drawings show some block diagrams and / or flow charts. It should be understood that some blocks in the block diagrams and / or flow charts, or combinations thereof, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when these instructions are executed by the processor, they can create a device for implementing the functions / operations described in the block diagrams and / or flow charts.

[0051] Therefore, the techniques of the present disclosure can be implemented in the form of hardware and / or software (including firmware, microcode, etc.). In addition, the techniques of the present disclosure can take the form of a computer program product on a computer-readable medium having stored thereon instructions, which can be used by or in conjunction with an instruction execution system. In the context of the present disclosure, a computer-readable medium can be any medium that can contain, store, convey, propagate, or transmit instructions. For example, a computer-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. Specific examples of computer-readable media include: magnetic storage devices, such as magnetic tape or hard disk drives (HDDs); optical storage devices, such as compact disks (CD-ROMs); memory, such as random access memory (RAM) or flash memory; and / or wired or wireless communication links.

[0052] In related technologies, the firmware interface systems of electronic devices typically only support hardware devices from a pre-defined list of qualified vendors. When users install non-certified hardware, the firmware interface system fails to recognize the new device during startup, causing the system to repeatedly reboot and fail to boot properly. This situation often occurs when a third-party graphics card or storage device is added to a computer motherboard. Due to a lack of corresponding driver support data, the electronic device will repeatedly reboot during the power-on self-test phase and will not boot completely.

[0053] To address this issue, users can create a new firmware interface system to support the added device. However, since the user's electronic device is currently unable to fully boot, the firmware interface system upgrade cannot be performed directly. The user can only remove the added device, enable the electronic device to boot normally, complete the firmware interface system upgrade, and then reinstall the added device on the motherboard. This process requires users to repeatedly disassemble and remove the device, which is cumbersome, time-consuming, and labor-intensive, resulting in low efficiency.

[0054] In view of this, an embodiment of the present disclosure provides a control method, which is applied to a first electronic device, by controlling the firmware interface system to enter the target mode to obtain data supporting the target device from the second electronic device and start the firmware interface system, so that the target device can be supported by the first electronic device, the first electronic device can be turned on and used normally, and the user does not need to repeatedly disassemble and assemble the target device.

[0055] Figure 1 The application scenarios of the control method and data transmission method according to the embodiment of the present disclosure are schematically shown. It should be noted that, Figure 1 The examples shown are merely examples of scenarios in which the embodiments of the present disclosure can be applied, to help those skilled in the art understand the technical content of the present disclosure, but do not mean that the embodiments of the present disclosure cannot be used in other devices, systems, environments or scenarios.

[0056] like Figure 1 As shown, the application scenario 100 may include a first electronic device 101, a second electronic device 102, and a network 103. The network 103 is a medium for providing a communication link between the first electronic device 101 and the second electronic device 102. The network 103 may include various connection types, such as wired or wireless communication links or fiber optic cables.

[0057] The user can use the first electronic device 101 to interact with the second electronic device 102 via the network 104 to receive or send messages, etc. The first electronic device 101 may be installed with a network module to interact with the second electronic device 102 via the network 103 .

[0058] The first electronic device 101 may run a firmware interface system. The firmware interface system may be the first software program that runs when the electronic device starts up, responsible for initializing the hardware devices and loading the operating system. The degree of support provided by the firmware interface system to the hardware devices may affect the normal startup and operation of the first electronic device 101.

[0059] For a computer / server-type first electronic device 101, the firmware interface support system may be a Basic Input / Output System (BIOS), a Unified Extensible Firmware Interface (UEFI), Coreboot / Libreboot, etc. For an embedded device / IoT device-type first electronic device 101, the firmware interface support system may be a bootloader, RTOS underlying firmware, or manufacturer-customized firmware. For a mobile device-type first electronic device 101, the firmware interface support system may be Fastboot (Android devices), iBoot / iBEC (iOS devices), etc. For a game console / consumer-type first electronic device 101, the firmware interface support system may be CFE, U-Boot / Pmon, or a manufacturer-specific bootloader. For an industrial control / automation-type first electronic device 101, the firmware interface support system may be PLC runtime firmware, FPGA / CPLD configuration firmware, etc.

[0060] The first electronic device 101 can be physically connected to the target device by internal or external connection, so that the first electronic device 101 can communicate with the target device. The target device may refer to a device that needs to be supported by the first electronic device 101 but is not currently recognized by its firmware interface system, such as a graphics card, an independent sound card, a memory, a RAID control card, an FPGA acceleration card, a high-precision sensor, a medical image acquisition card, etc. Internal connection means that the target device is installed inside the first electronic device 101 by removing the outer shell, for example, through a fixed interface or slot on the motherboard. External connection means that the target device is connected to the first electronic device 101 through an external interface.

[0061] The second electronic device 102 can be used to store or obtain the first data. The second electronic device 102 can be a server that provides various services, such as a background management server that provides support for websites browsed by users using the electronic device (for example only). The background management server can analyze, store, and perform other processing on received data such as user requests.

[0062] It is understandable that the firmware interface system in the first electronic device 101 cannot support the target device installed on the first electronic device 101 before the implementation of the embodiment of the present disclosure.

[0063] It should be noted that the control method provided in the embodiments of the present disclosure can generally be applied to the first electronic device 101, and accordingly, the control device and system provided in the embodiments of the present disclosure can be provided in the first electronic device 101. The data transmission method provided in the embodiments of the present disclosure can generally be applied to the second electronic device 102, and accordingly, the data transmission device and system provided in the embodiments of the present disclosure can be provided in the second electronic device 102.

[0064] It should be understood that Figure 1 The number of electronic devices in the embodiment is merely illustrative. Any number of electronic devices may be provided as required. For example, a third electronic device may be provided, through which a user inputs data and the data is stored in the second electronic device 102.

[0065] Figure 2 The flowchart of the control method according to the embodiment of the present disclosure is schematically shown.

[0066] like Figure 2 As shown, the control method 200 is applied to a first electronic device, and the control method 200 includes operations S210 to S230.

[0067] In operation S210 , in response to a target event, the firmware interface system is controlled to be in a target mode.

[0068] According to embodiments of the present disclosure, a target event may refer to a specific event that triggers the first electronic device to control the firmware interface system to enter target mode, such as a user-initiated operation-related event, a setting state-related event, an external signal-related event, etc. For example, a user-initiated operation-related event may include a user pressing a specific key, a user sending a command through an external device, etc. For example, a setting state-related event may include the first electronic device detecting the connection of a target device, the first electronic device failing to start up, etc. For example, an external signal-related event may include receiving a specific signal from a second electronic device, etc.

[0069] According to an embodiment of the present disclosure, target mode can be an operating state entered by the firmware interface system of the first electronic device in response to a target event. In target mode, the first electronic device switches from attempting to interact with the target device to communicating with the second electronic device. The first electronic device and the second electronic device can communicate by shutting down other functions or interfaces and only initializing the necessary components that can be started online, thereby achieving the function of only communicating with the second electronic device, thereby ensuring a communication connection with the second electronic device and secure transmission of the first data.

[0070] According to an embodiment of the present disclosure, communication between the first electronic device and the second electronic device can be carried out wirelessly (such as Wi-Fi, Bluetooth, etc.) or wired (such as USB, Ethernet, etc.), and can be set according to the interface capabilities and communication requirements of the first electronic device and the second electronic device. The embodiment of the present disclosure does not impose any restrictions on this.

[0071] According to embodiments of the present disclosure, a firmware interface system may be a key software or system component in a first electronic device, primarily responsible for managing and supporting communication and interaction with hardware devices. The firmware interface system may have a pre-defined list of qualified vendors and only support hardware devices on that list. Prior to implementing embodiments of the present disclosure, the target device was not included in that list of hardware devices.

[0072] For example, the firmware interface system may be a basic input / output system or a unified extensible firmware interface on a mainboard of the first electronic device.

[0073] In operation S220, first data is obtained from the second electronic device in the target mode.

[0074] According to an embodiment of the present disclosure, the first data may be data that enables the target device to be supported by the firmware interface system. The first data may include necessary information to enable the firmware interface system to identify and support the target device. The first data may include a driver, configuration parameters, compatibility data, etc. For example, if the target device is a new graphics card, the first data may include the graphics card driver so that the firmware interface system of the first electronic device can support the graphics card.

[0075] According to an embodiment of the present disclosure, the second electronic device can be an electronic device capable of providing data supported by the firmware interface system of the target device, that is, the first data. The second electronic device can store, generate, or obtain the first data. For example, the second electronic device can be an external storage device storing the first data, a server that provides the first data via network communication, etc.

[0076] It is understandable that when the second electronic device is a server that can provide the first data through network communication, the user can upload the first data or related data used to generate the first data to the server through the first electronic device or the third electronic device.

[0077] In operation S230 , the firmware interface system is started based on the first data.

[0078] According to an embodiment of the present disclosure, after the firmware interface system is in target mode and obtains first data from the second electronic device, the obtained first data is used to perform relevant operations on the firmware interface system to achieve normal startup of the firmware interface system.

[0079] According to an embodiment of the present disclosure, after acquiring the first data, the firmware interface system performs a series of initialization and configuration operations based on the first data. For example, the system loads the driver program contained in the first data into the firmware interface system's memory, and adjusts the firmware interface system's identification and interaction methods with the target device based on configuration parameters to ensure that the firmware interface system can communicate and exchange data normally with the target device. After completing these operations, the firmware interface system can start normally, enabling the first electronic device to recognize and support the target device, thereby achieving normal startup and operation.

[0080] According to the embodiment of the present disclosure, the compatibility problem of the firmware interface system with unsupported hardware is solved by establishing an external device (second electronic device) collaboration mechanism. First, the target event triggers the mode switch, and the firmware interface system is placed in a special working state that communicates with the second electronic device. This target mode can ensure that the first electronic device interacts with the trusted data source during the critical startup phase, and ensures the safe transmission of the first data. In the target mode, the first data is obtained from the second electronic device in a targeted manner. The first data is not stored locally but comes from an external dedicated second electronic device, breaking through the limitation that traditional firmware only relies on locally pre-stored driver data. Finally, the obtained first data is directly applied to the startup process of the firmware interface system. The user does not need to remove the target device from the first electronic device to achieve dynamic adaptation of unsupported hardware.

[0081] The following references Figure 3A and Figure 3B An application scenario of an embodiment of Figure 2The method shown is further explained.

[0082] Figure 3A A schematic diagram of a physical switch according to an embodiment of the present disclosure is schematically shown. Figure 3B The figure schematically shows a software switch according to an embodiment of the present disclosure.

[0083] like Figure 3A As shown, the host 300A of the first electronic device includes a control element, which is a physical switch 310A. The physical switch 310A can be a hardware component that uses mechanical contacts to connect and disconnect a circuit or switch its state, providing a physically isolated operation mode to prevent false triggering. For example, the physical switch 310A can be a toggle switch or a push-type self-locking switch. The user can manually change the state of the physical switch.

[0084] like Figure 3B As shown, the interface 300B of the first electronic device has a control element, which is a software switch 310B. The software switch 310B is a virtual control that switches states through a graphical interface or system instructions. In one example, the software switch 310B can be displayed when the first electronic device is turned on. Specifically, it can be integrated into the startup interface, displayed through the startup management program, or configured using a startup application loaded by the operating system.

[0085] It is understandable that the control element may also be a combination of the software switch 310B and the hardware switch 310A, and the specific compatibility setting may be set according to actual conditions.

[0086] Integration into the startup interface can mean that the developer integrates the software switch 310B into the system startup interface of the first electronic device. For example, a dedicated option or page is added to the BIOS or UEFI setup interface of the first electronic device for displaying and operating the software switch 310B. When the first electronic device is powered on, the user can press a specific key (such as F2 or Delete) to enter the startup interface before entering the operating system, and then find and operate the software switch 310B within the startup interface.

[0087] Displaying via the boot manager may mean that the first electronic device uses the boot manager to control the system's boot process. Developers can add functionality for displaying and operating software switch 310B within the boot manager. When the first electronic device is powered on, the boot manager runs first. The user can then see software switch 310B in the boot manager's interface and operate it as needed.

[0088] The startup application loaded by the operating system can mean that if the operating system of the first electronic device supports automatically running a specific application upon startup, the developer can develop a dedicated application to display and operate the software switch 310B. During the startup process of the first electronic device, the operating system will automatically load this application, and the user can operate the software switch 310B in the application interface. For example, on a smartphone, a startup app can be developed and the software switch 310B can be set in the app interface.

[0089] According to an embodiment of the present disclosure, the control element can control the firmware interface system to be in a target mode when in the on state, so that the first electronic device is used to communicate with the second electronic device to obtain the first data.

[0090] For example, when the user turns the physical switch 310A to the on position or sets the software switch 310B to the on state in the graphical interface, the first electronic device enters the target mode and starts communicating with the second electronic device to obtain the first data.

[0091] According to an embodiment of the present disclosure, the control element can control the firmware interface system to be in an initialization mode in a closed state, so that the firmware interface system loads target data, where the target data includes first data.

[0092] For example, when the user turns the physical switch 310A back to the off position, or sets the software switch 310B to the off state in the graphical interface, the first electronic device will switch to the initialization mode, load the target data, etc., to prepare for the normal operation of the firmware interface system.

[0093] In some embodiments, when physical switch 310A is detected to be in the on state or software switch 310B is detected to be activated, the communication module of the firmware interface system is configured to establish a connection with the second electronic device and suspend access rights to the local storage device. In this target scenario, the first electronic device obtains the first data from the second electronic device via a wired or wireless communication protocol. After completing the acquisition of the first data, physical switch 310A is switched off or software switch 310B is turned off, and the firmware interface system returns to initialization mode.

[0094] According to the embodiment of the present disclosure, by introducing a control element, a controllable switching of the operating mode of the firmware interface system is achieved. In the on state, the control element forces the firmware interface system to enter the target mode. At this time, the first electronic device and the second electronic device establish a directional communication channel to ensure that the first data stored externally can be accurately obtained, thereby avoiding the startup failure problem caused by the automatic loading of local incompatible data in the initialization phase of the firmware interface system. In the off state, the control element restores the initialization mode, allowing the firmware interface system to load the target data stored locally, taking into account the compatibility requirements of the conventional startup process and the target device. By concretizing the mode switching mechanism as a physical / software dual-mode switch, it not only meets the user's selective demand for the operating mode, but also enhances the system security through the physical isolation characteristics of the hardware switch, preventing misoperation from causing mode confusion. By combining clear mode division with active user control, the firmware compatibility conflict problem when an unsupported target device is connected is effectively solved.

[0095] According to an embodiment of the present disclosure, the first electronic device may send first information to the second electronic device; and obtain first data based on the first mapping relationship table stored in the second electronic device.

[0096] In some embodiments, the first information sent by the first electronic device to the second electronic device includes at least device identification information corresponding to the first electronic device. By sending the first information including the device identification information, the first electronic device indicates its identity to the second electronic device so that the second electronic device can search for and provide corresponding first data based on the identity information.

[0097] The device identification information may be a unique identifier of the first electronic device, which is used to uniquely determine the identity of the first electronic device, such as the serial number, model code, MAC address, etc. of the device.

[0098] In some embodiments, the second electronic device stores a first mapping relationship table, which includes at least a mapping relationship between device identification information of the first electronic device and the first data. In other words, the first mapping relationship table can be an association table that associates device identification information of different first electronic devices with corresponding first data that enables the target device to be supported by the firmware interface system.

[0099] For example, the first electronic device is a computer, and the second electronic device is a server that provides hardware drivers and compatibility data. When a user installs a third-party graphics card (target device) on the computer that is not supported by the current firmware interface system, first data supporting the graphics card needs to be obtained. In this case, the computer (the first electronic device) sends a first message containing its own device identification information (such as the computer model and motherboard serial number) to the server (the second electronic device). After receiving this message, the server searches its stored first mapping table for an entry corresponding to the device identification information. This mapping table records the mapping between different computer models and motherboard serial numbers and the first data of various corresponding hardware devices. Once the server finds a match, it obtains the first data supporting the third-party graphics card and sends it to the computer. After receiving the first data, the computer can activate the firmware interface system based on this data, thereby implementing support for the third-party graphics card.

[0100] According to an embodiment of the present disclosure, a mapping mechanism between device identification information and first data is established to ensure that a first electronic device can accurately obtain firmware interface data adapted to a target device. First, by sending a first message containing device identification information, the second electronic device can identify the device model and hardware configuration based on the unique identifier, thus avoiding data matching errors. Subsequently, data retrieval is performed based on a pre-stored first mapping table. This mapping table, through a strong association between the device identification and the first data, ensures that the obtained first data is fully compatible with the target device.

[0101] According to an embodiment of the present disclosure, the first data may be generated based on the device identification information of the target device. The device identification information of the target device is a unique identifier of the hardware device, such as the model and serial number of a graphics card, or the manufacturer code and product number of a storage device. This information can uniquely determine the type, specifications, and basic characteristics of the target device.

[0102] For example, when the target device is a graphics card of a specific model, the second electronic device can search and extract first data such as a driver and compatibility settings corresponding to the graphics card model from the database according to the model information of the graphics card.

[0103] According to an embodiment of the present disclosure, the first data may be generated based on device identification information of the target apparatus and second information, where the second information is information generated based on a user portrait and / or information pre-entered by the user.

[0104] In some embodiments, a user profile can be a comprehensive description of various aspects of a user's characteristics, behaviors, preferences, and so on. Based on the user profile, information such as the user's usage habits and hardware performance requirements can be understood. For example, if the user profile indicates that the user frequently engages in graphic design, then when generating the first data, adjustments can be made to optimization settings related to graphic design to provide hardware devices such as graphics cards with driver parameters and configuration information that are more suitable for graphics processing.

[0105] In some embodiments, the user can actively input some information related to the target device, such as the user's special setting requirements for the target device, usage scenarios, etc. For example, when using a third-party storage device, the user can inform in advance that the storage device is mainly used to store a large number of video files. The second electronic device can then generate first data that is more suitable for video storage and access based on this information.

[0106] For example, for a specific model of graphics card, not only can the basic driver be obtained based on the graphics card model, but also the first data containing game optimization driver parameters and configuration information can be generated based on the user's high requirements for game performance in the user portrait and the user's pre-entered settings for enabling specific game optimization functions.

[0107] According to an embodiment of the present disclosure, the first data may be stored in a first data list, the first data may be acquired from the first data list, and the firmware interface system may be started based on the first data.

[0108] In some embodiments, the first data list may be a container specifically used to store data, and may exist in a storage medium of the first electronic device, such as a hard disk or a memory.

[0109] In some embodiments, the first data list is used to store first data and second data, where the second data also enables the target device to be supported by the firmware interface system, but the second data is different from the first data. For example, the first data may be basic support data for the target device obtained through a specific method (such as from a second electronic device), while the second data may be locally available data that supports the target device, a different version or a different source, or support data optimized for a specific scenario.

[0110] According to an embodiment of the present disclosure, if the startup of the firmware interface system based on the first data fails, it means that there may be some problems with the first data, such as incomplete data, incompatibility with the current system environment, etc. At this time, the second data can be obtained from the first data list, and then the second data can be used to start the firmware interface system. For example, the system will switch to using the locally available second data to re-initialize and configure the firmware interface system. By trying to use different data to start the firmware interface system, the probability of successful startup is increased, and the fault tolerance and reliability of the system are increased. Even if the first data cannot start the system normally, you can still try to use the second data to ensure that the target device can eventually be supported by the firmware interface system.

[0111] For example, the first electronic device is a computer, and the target device is a newly installed graphics card. The computer obtains first data (such as the latest graphics card driver and related configuration files) from the second electronic device and stores it in a first data list. Simultaneously, the computer also locally stores second data (such as an older version of the graphics card driver). When starting the firmware interface system, the computer first attempts to use the first data to initialize the graphics card driver and related configurations to support the normal operation of the graphics card. If, for some reason (such as compatibility issues between the first data and the current operating system version), starting the firmware interface system using the first data fails, the computer will obtain the second data from the first data list and use the older version of the driver to initialize the graphics card, potentially successfully starting the firmware interface system and enabling the graphics card to be recognized and used.

[0112] Figure 4 The flowchart of the data transmission method according to the embodiment of the present disclosure is schematically shown.

[0113] like Figure 4 As shown, the data transmission method 400 is applied to a second electronic device, and the data transmission method 400 includes operations S410 to S420.

[0114] In operation S410, in response to obtaining a communication request initiated by the first device in the target mode, a communication connection is established with the first electronic device.

[0115] According to an embodiment of the present disclosure, the second electronic device responds to a communication request initiated by the first electronic device in target mode. As previously described, when the control element (physical switch and / or software switch) of the first electronic device is turned on, the firmware interface system enters target mode, at which point the first electronic device initiates a communication request to the second electronic device. After receiving the communication request, the second electronic device establishes a communication connection with the first electronic device. This established communication connection enables data transmission between the first and second electronic devices.

[0116] In operation S420, first data is transmitted to the first electronic device so that the first electronic device boots up a firmware interface system based on the first data.

[0117] According to an embodiment of the present disclosure, a second electronic device sends first data to a first electronic device. The first data is data that enables a target device to be supported by the firmware interface system of the first electronic device. After receiving the first data, the first electronic device can activate the firmware interface system based on the data, thereby enabling the firmware interface system to support the target device. The target device can then operate normally on the first electronic device, meeting the user's usage requirements.

[0118] According to the disclosed embodiments, a second electronic device actively responds to a request from a first electronic device in target mode, establishing a directional communication link and ensuring reliable data transmission. This direct initialization of the firmware interface system occurs by sending the first data required for the firmware interface system to identify the target device. This target-mode-triggered data transmission mechanism ensures the security of the firmware update process while also enabling adaptation to unsupported target devices.

[0119] In some embodiments, the second electronic device receives the first information sent by the first electronic device, and based on the first information, sends a first mapping relationship table or first data to the first electronic device, wherein the first mapping relationship table includes at least a mapping relationship between the device identification information of the first electronic device and the first data.

[0120] In some embodiments, the second electronic device may receive information pre-input by the user to generate first data based on information generated by the user portrait and / or information pre-input by the user.

[0121] Figure 5 A block diagram of a first electronic device according to an embodiment of the present disclosure is schematically shown.

[0122] like Figure 5 As shown, the first electronic device 500 includes a control module 510 , an acquisition module 520 and a configuration module 530 .

[0123] The control module 510 is used to control the firmware interface system to be in target mode in response to the target event, in which the first electronic device is used to communicate with the second electronic device. In one embodiment, the control module 510 can be used to perform the operation S210 described above, which will not be repeated here.

[0124] The obtaining module 520 is used to obtain first data from the second electronic device in the target mode, where the first data is a number that enables the target device to be supported by the firmware interface system. In one embodiment, the obtaining module 520 can be used to perform the operation S220 described above, which will not be repeated here.

[0125] The configuration module 530 is used to start the firmware interface system based on the first data. In one embodiment, the configuration module 530 can be used to perform the operation S230 described above, which will not be repeated here.

[0126] According to an embodiment of the present disclosure, the control module 510 is a physical switch and / or a software switch. The control module 510 is configured to: in an on state, control the firmware interface system to be in a target mode, enabling the first electronic device to communicate with the second electronic device to obtain the first data; and in an off state, control the firmware interface system to be in an initialization mode, enabling the firmware interface system to load target data, wherein the target data includes the first data. In response to a target event, controlling the firmware interface system to be in the target mode includes: in response to the control element being in the on state, controlling the firmware interface system to be in the target mode.

[0127] According to an embodiment of the present disclosure, obtaining the first data includes: sending first information to a second electronic device, the first information including at least device identification information corresponding to the first electronic device; obtaining the first data based on a first mapping relationship table stored in the second electronic device; wherein the first mapping relationship table includes at least a mapping relationship between the device identification information of the first electronic device and the first data.

[0128] According to an embodiment of the present disclosure, the first data is generated based on the device identification information of the target device; or, the first data is generated based on the device identification information of the target device and second information, and the second information is information generated based on the user portrait and / or information pre-entered by the user.

[0129] According to an embodiment of the present disclosure, the device 500 also includes: a storage module for storing the first data in a first data list, the first data list is used to store the first data and the second data, the second data is data that enables the target device to be supported by the firmware interface system, and the second data is different from the first data; based on the first data, starting the firmware interface system includes: obtaining the first data from the first data list, and starting the firmware interface system based on the first data; in the event that the firmware interface system fails to start, obtaining the second data from the first data list and starting the firmware interface system.

[0130] Figure 6 A block diagram of a second electronic device according to an embodiment of the present disclosure is schematically shown.

[0131] like Figure 6 As shown, the second electronic device 600 includes a communication module 610 and a sending module 620 .

[0132] The communication module 610 is configured to establish a communication connection with the first electronic device in response to obtaining a communication request initiated by the first device in the target mode. In one embodiment, the communication module 610 may be configured to perform the operation S410 described above, which will not be described in detail herein.

[0133] The sending module 620 is configured to send first data to the first electronic device. The first data is data that enables the target device to be supported by the firmware interface system, so that the first electronic device activates the firmware interface system based on the first data. In one embodiment, the sending module 620 can be configured to perform operation S420 described above, which will not be repeated here.

[0134] According to the embodiments of the present invention, any number of modules, sub-modules, units, and sub-units, or at least part of the functions of any number of them, can be implemented in one module. According to the embodiments of the present invention, any one or more of the modules, sub-modules, units, and sub-units can be split into multiple modules for implementation. According to the embodiments of the present invention, any one or more of the modules, sub-modules, units, and sub-units can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware in any other reasonable way of integrating or packaging the circuit, or can be implemented in any one of the three implementation methods of software, hardware, and firmware, or in any appropriate combination of any of them. Alternatively, according to the embodiments of the present invention, one or more of the modules, sub-modules, units, and sub-units can be at least partially implemented as a computer program module, which can perform the corresponding functions when the computer program module is executed.

[0135] For example, any number of the control module 510, the acquisition module 520, and the configuration module 530 can be combined into a single module, or any one of these modules can be split into multiple modules. Alternatively, at least part of the functionality of one or more of these modules can be combined with at least part of the functionality of other modules and implemented in a single module. According to an embodiment of the present disclosure, at least one of the control module 510, the acquisition module 520, and the configuration module 530 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented in hardware or firmware through any other reasonable means of circuit integration or packaging, or can be implemented in any one of the three implementation methods of software, hardware, and firmware, or any appropriate combination of any of these. Alternatively, at least one of the control module 510, the acquisition module 520, and the configuration module 530 can be at least partially implemented as a computer program module that, when executed, can perform the corresponding function.

[0136] Figure 7 A block diagram of an electronic device suitable for implementing the control method or data transmission described above according to an embodiment of the present disclosure is schematically shown. Figure 7 The electronic device shown is only an example and should not limit the functions and scope of use of the embodiments of the present disclosure.

[0137] like Figure 7 As shown, the electronic device 700 according to an embodiment of the present disclosure includes a processor 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage portion 708 into a random access memory (RAM) 703. The processor 701 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 701 may also include onboard memory for caching purposes. The processor 701 may include a single processing unit or multiple processing units for performing different actions of the method flow according to the embodiment of the present disclosure.

[0138] Various programs and data required for the operation of the electronic device 700 are stored in the RAM 703. The processor 701, ROM 702, and RAM 703 are connected to each other via a bus 704. The processor 701 performs various operations of the method flow according to the embodiment of the present disclosure by executing the programs in the ROM 702 and / or RAM 703. It should be noted that the programs may also be stored in one or more memories other than the ROM 702 and RAM 703. The processor 701 may also perform various operations of the method flow according to the embodiment of the present disclosure by executing the programs stored in one or more memories.

[0139] According to an embodiment of the present disclosure, electronic device 700 may further include an input / output (I / O) interface 705, which is also connected to bus 704. Electronic device 700 may also include one or more of the following components connected to I / O interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including devices such as a cathode ray tube (CRT), liquid crystal display (LCD), and speakers; a storage section 708 including a hard disk; and a communication section 709 including a network interface card such as a LAN card or modem. Communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to I / O interface 705 as needed. Removable media 711, such as a magnetic disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed in drive 710 as needed, so that computer programs read from the removable media can be installed into storage section 708 as needed.

[0140] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments, or may exist independently and not be incorporated into the device / apparatus / system. The computer-readable storage medium carries one or more programs, and when executed, implements the method according to the embodiments of the present disclosure.

[0141] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, and may include, for example, but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 702 and / or RAM 703 described above, and / or one or more memories other than ROM 702 and RAM 703.

[0142] The embodiments of the present disclosure also include a computer program product, which includes a computer program containing program code for executing the method shown in the flowchart. When the computer program product is executed in a computer system, the program code is used to cause the computer system to implement the control method or data transmission method provided by the embodiments of the present disclosure.

[0143] The computer program executes the above functions defined in the system / device of the embodiment of the present disclosure when the processor 701 executes the computer program. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0144] In one embodiment, the computer program may be stored on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may be transmitted and distributed in the form of a signal on a network medium, downloaded and installed via the communication portion 709, and / or installed from a removable medium 711. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to wireless, wired, or any suitable combination thereof.

[0145] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 709, and / or installed from a removable medium 711. When the computer program is executed by the processor 701, the above-described functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the systems, devices, means, modules, units, etc. described above can be implemented by computer program modules.

[0146] Figure 8 A block diagram of a control system according to an embodiment of the present disclosure is schematically shown.

[0147] like Figure 8As shown, a control system 800 according to an embodiment of the present disclosure includes a first electronic device 810 and a second electronic device 820 .

[0148] The first electronic device 810 is capable of communicating with a target device, and the target device is not supported by the firmware interface system of the first electronic device. The first electronic device is used to respond to a target event and control the firmware interface system to be in target mode. In target mode, the first electronic device is used to communicate with the second electronic device.

[0149] The second electronic device 820 is configured to establish a communication connection with the first electronic device in response to a communication request initiated by the first device in target mode; and send first data to the first electronic device, where the first data is data that enables the target device to be supported by the firmware interface system.

[0150] The first electronic device 810 is further configured to obtain first data from the second electronic device in the target mode; and start the firmware interface system based on the first data.

[0151] According to embodiments of the present disclosure, program code for executing the computer programs provided by embodiments of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computer programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C," or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving a remote computing device, the remote computing device can be connected to the user computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (e.g., via the Internet using an Internet service provider). The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of the systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, program segment, or a part for code, and the part of the above-mentioned module, program segment, or code comprises one or more executable instructions for realizing the logical function of the regulation. It should also be noted that in some alternative implementations, the function annotated in the box can also occur in a sequence different from that annotated in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the function involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart, can be realized by a dedicated hardware-based system that performs the function or operation of the regulation, or can be realized by a combination of dedicated hardware and computer instructions.

[0152] Those skilled in the art will appreciate that the features described in the various embodiments and / or claims of this disclosure may be combined and / or coupled in various ways, even if such combinations and / or couplings are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure may be combined and / or coupled in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or couplings are intended to fall within the scope of this disclosure.

Claims

1. A control method, applied to a first electronic device, wherein the first electronic device is capable of communicating with a target device, and the target device is not supported by a firmware interface system of the first electronic device, the method comprising: In response to a target event, controlling the firmware interface system to be in a target mode, wherein the first electronic device is used to communicate with a second electronic device in the target mode; obtaining, in the target mode, the first data from the second electronic device, the first data being data enabling the target device to be supported by the firmware interface system; Based on the first data, the firmware interface system is started.

2. The control method according to claim 1, wherein: The first electronic device includes a control element, which is a physical switch and / or a software switch, and is configured to: In the on state, controlling the firmware interface system to be in a target mode, so that the first electronic device is used to communicate with the second electronic device to obtain the first data; In a closed state, controlling the firmware interface system to be in an initialization mode, so that the firmware interface system loads target data, wherein the target data includes first data; In response to the target event, controlling the firmware interface system to be in target mode includes: In response to the control element being in the on state, the firmware interface system is controlled to be in the target mode.

3. The control method according to claim 1, wherein: The obtaining of the first data includes: Sending first information to the second electronic device, where the first information at least includes device identification information corresponding to the first electronic device; acquiring the first data based on a first mapping relationship table stored in the second electronic device; The first mapping relationship table at least includes a mapping relationship between the device identification information of the first electronic device and the first data.

4. The control method according to claim 1, wherein: The first data is generated based on the device identification information of the target apparatus; or, The first data is generated based on device identification information of the target apparatus and second information, where the second information is information generated based on a user portrait and / or information pre-input by the user.

5. The control method according to claim 1, wherein: After obtaining the first data, the method includes: storing the first data in a first data list, where the first data list is used to store the first data and second data, where the second data is data that enables the target device to be supported by the firmware interface system, and the second data is different from the first data; The starting the firmware interface system based on the first data includes: Acquire first data from the first data list, and start the firmware interface system based on the first data; In the case that starting the firmware interface system fails, the second data is obtained from the first data list, and the firmware interface system is started.

6. A data transmission method, applied to a second electronic device, wherein the second electronic device is communicatively connected to a first electronic device, and the first electronic device is communicatively connected to a target device, and the firmware interface system of the first electronic device does not support the target device, the method comprising: In response to obtaining a communication request initiated by the first device in the target mode, establishing a communication connection with the first electronic device; First data is sent to the first electronic device, where the first data is data that enables the target device to be supported by the firmware interface system, so that the first electronic device starts the firmware interface system based on the first data.

7. A first electronic device capable of communicating with a target device that is not supported by a firmware interface system of the first electronic device, the electronic device comprising: A control module, configured to control the firmware interface system to be in a target mode in response to a target event, wherein the first electronic device is configured to communicate with a second electronic device in the target mode; An obtaining module, configured to obtain the first data from the second electronic device in the target mode, wherein the first data is data enabling the target device to be supported by the firmware interface system; A configuration module is configured to start the firmware interface system based on the first data.

8. The first electronic device according to claim 7, wherein: The control module is a physical switch and / or a software switch, and is used to: In the on state, controlling the firmware interface system to be in a target mode, so that the first electronic device is used to communicate with the second electronic device to obtain the first data; In the closed state, the firmware interface system is controlled to be in an initialization mode, so that the firmware interface system loads target data, where the target data includes first data.

9. A first electronic device capable of communicating with a target device that is not supported by a firmware interface system of the first electronic device, the electronic device comprising: Memory, used to store programs; A processor, configured to execute the program, wherein the program is configured to: In response to a target event, controlling the firmware interface system to be in a target mode, wherein the first electronic device is used to communicate with a second electronic device in the target mode; obtaining, in the target mode, the first data from the second electronic device, the first data being data enabling the target device to be supported by the firmware interface system; Based on the first data, the firmware interface system is started.

10. A control system comprising: a first electronic device capable of being communicatively connected with a target device, wherein the target device is not supported by a firmware interface system of the first electronic device, wherein the first electronic device is configured to control the firmware interface system to be in a target mode in response to a target event, wherein the first electronic device is configured to communicate with a second electronic device in the target mode; The second electronic device is configured to establish a communication connection with the first electronic device in response to a communication request initiated by the first device in the target mode; and send first data to the first electronic device, the first data being data that enables the target device to be supported by the firmware interface system; The first electronic device is further configured to obtain first data from the second electronic device in the target mode; and start the firmware interface system based on the first data.

Images