Processing method and processing device

CN115202754BActive Publication Date: 2026-07-03LENOVO (BEIJING) LTD

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
LENOVO (BEIJING) LTD
Filing Date
2022-06-30
Publication Date
2026-07-03

Smart Images

  • Figure CN115202754B_ABST
    Figure CN115202754B_ABST
Patent Text Reader

Abstract

This application provides a processing method and apparatus, wherein the method includes: in response to satisfying a trigger condition, starting a first application, the first application being an application capable of running in a pre-operating system environment; controlling the first application to perform a target operation corresponding to a target request to achieve a first function different from a second function, wherein the second function includes at least the function of initializing the pre-operating system environment; wherein at least the storage location of the first data used to achieve the first function is different from the storage location of the second data used to achieve the second function.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of processing, and more particularly to a processing method and processing apparatus. Background Technology

[0002] In related technologies, after an electronic device is powered on, it starts the Basic Input / Output System (BIOS), which performs hardware self-tests and initialization. In addition, the BIOS can also perform other functions, such as setting a power-on password and performing non-core functions (auxiliary functions) like BIOS version upgrades. Currently, all of these functions are implemented by the BIOS itself, which increases the processing burden on the BIOS. Summary of the Invention

[0003] The technical solution provided in this application is:

[0004] This application provides a processing method, including:

[0005] In response to the fulfillment of a trigger condition, a first application is launched, wherein the first application is an application capable of running in a pre-operating system environment;

[0006] The first application is controlled to perform a target operation corresponding to the target request, so as to achieve a first function that is different from the second function, wherein the second function includes at least the function of initializing the pre-operating system environment;

[0007] Wherein, at least the first data used to implement the first function is stored in a different location than the second data used to implement the second function.

[0008] In the above scheme, responding to a triggering condition includes at least one of the following:

[0009] In response to the completion of the initialization operation for the accessed mobile device, it is determined that the triggering condition is met;

[0010] In response to the completion of the initialization operation of the storage component where the first application resides, it is determined that the triggering condition is met; or,

[0011] In response to receiving at least one target request, it is determined that the triggering condition is met, wherein the target request is capable of performing a first function that is distinct from the second function.

[0012] In the above scheme, the target request includes at least one of the following:

[0013] Requests to update, restore, or configure the basic input system of electronic devices;

[0014] A request for troubleshooting of electronic equipment;

[0015] A request to update or repair the hardware or software of an electronic device;

[0016] Requests for leasing or asset management of electronic equipment;

[0017] A request to securely process interactive data from electronic devices;

[0018] Requests for customized services to be output by electronic devices.

[0019] The above plan also includes:

[0020] Verify the extended properties of the basic input / output system of electronic devices;

[0021] If the basic input / output system can be expanded, the first application can be controlled to perform the corresponding target operation to achieve the first function;

[0022] If the basic input / output system cannot be expanded, the first application is controlled to perform the corresponding target operation to achieve the third function, wherein the third function is implemented independently of the basic input / output system.

[0023] In the above scheme, controlling the first application to execute the target operation corresponding to the target request to achieve the first function includes:

[0024] Display the interface information of the first application, the interface information including option information for implementing different functions;

[0025] Based on the operation of the option information, a corresponding first function is executed, the first function being implemented based on the standard or protocol between the first application and the basic input / output system and the program components included in the basic input / output system.

[0026] In the above scheme, controlling the first application to execute the target operation corresponding to the target request to achieve the first function includes:

[0027] If it is determined that the basic input / output system can be expanded, an interface is provided for receiving a target operation to implement a corresponding first function based on the target operation obtained through the interface, wherein the interface may or may not belong to the electronic device, and the first function is implemented based on a standard or protocol between the first application and the basic input / output system and the program components included in the basic input / output system.

[0028] In the above scheme, controlling the first application to execute the target operation corresponding to the target request to achieve the first function includes:

[0029] If it is determined that the mobile device connected to the electronic device is configured with an interface capable of receiving the target operation, the target operation is obtained through the interface of the mobile device to achieve the corresponding first function.

[0030] In the above scheme, executing the corresponding first function based on the operation on the option information includes at least one of the following:

[0031] If the operation is a file option operation, perform a functional operation to download or upgrade at least one of the application, firmware, and driver;

[0032] If the operation is an operation on the asset management option or lease management option of the electronic device, at least the interface information for performing asset management or lease management shall be output;

[0033] If the operation is to trigger the setting of the basic input / output system, at least the setting interface of the basic input / output system shall be output, wherein at least some of the setting items in the setting interface are from the first application;

[0034] If the operation involves invoking a target tool, at least the corresponding target tool should be launched for the user to use.

[0035] The above plan also includes:

[0036] The configuration information of the electronic device is updated based on the settings information of the settings interface of the basic input / output system that operates on the output of the first application.

[0037] This application also provides a processing apparatus, including:

[0038] A startup unit is configured to start a first application in response to a trigger condition being met, wherein the first application is an application capable of running in a pre-operating system environment;

[0039] A control unit is used to control the first application to perform a target operation corresponding to the target request, so as to realize a first function that is different from the second function, wherein the second function includes at least the function of initializing the pre-operating system environment;

[0040] Wherein, at least the first data used to implement the first function is stored in a different location than the second data used to implement the second function.

[0041] The processing method and processing apparatus of this application, wherein the method includes: in response to satisfying a trigger condition, starting a first application, the first application being an application capable of running in a pre-operating system environment; controlling the first application to perform a target operation corresponding to a target request to achieve a first function different from a second function, wherein the second function includes at least the function of initializing the pre-operating system environment; wherein at least the storage location of the first data used to achieve the first function is different from the storage location of the second data used to achieve the second function.

[0042] By storing the second data used to implement core BIOS functions and the first data used to implement non-core functions separately, the independence of the data is maintained, preventing mutual interference. The first application can be used to implement non-core BIOS functions, thus not affecting the normal operation of these functions. This application's technical solution provides technical support for the normal implementation of non-core BIOS functions.

[0043] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this application, nor is it intended to limit the scope of this application. Other features of this application will become readily apparent from the following description. Attached Figure Description

[0044] The above and other objects, features, and advantages of exemplary embodiments of this application will become readily apparent from the following detailed description taken in conjunction with the accompanying drawings. Several embodiments of this application are illustrated in the drawings by way of example and not limitation, in which:

[0045] In the accompanying drawings, the same or corresponding reference numerals indicate the same or corresponding parts.

[0046] Figure 1 This paper illustrates the implementation flow of the processing method according to an embodiment of the present application. Figure 1 ;

[0047] Figure 2 This paper illustrates the implementation flow of the processing method according to an embodiment of the present application. Figure 2 ;

[0048] Figure 3 This paper illustrates the implementation flow of the processing method according to an embodiment of the present application. Figure 3 ;

[0049] Figure 4 This paper illustrates the implementation flow of the processing method according to an embodiment of the present application. Figure 4 ;

[0050] Figure 5 This paper illustrates the implementation flow of the processing method according to an embodiment of the present application. Figure 5 ;

[0051] Figure 6 A schematic diagram of the composition structure of the processing device according to an embodiment of this application is shown;

[0052] Figure 7 A schematic diagram of the composition structure of an electronic device according to an embodiment of this application is shown. Detailed Implementation

[0053] To make the objectives, features, and advantages of this application more apparent and understandable, the technical solutions in 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 skilled in the art without creative effort are within the scope of protection of this application.

[0054] It's understandable that if hardware self-test and initialization are considered the core functions of BIOS (equivalent to UEFI), then other functions that BIOS can perform besides these core functions are considered non-core or auxiliary functions. Non-core or auxiliary functions include, but are not limited to: password settings, BIOS setup interface, electronic device mode settings, configuration of related components and drivers within electronic devices, firmware version upgrades, and modification of the system time of electronic devices. In practical applications, any function that BIOS can perform besides hardware self-test and initialization can be considered an auxiliary function; these will not be listed exhaustively.

[0055] In related technologies, the aforementioned functions of the BIOS are implemented through a BIOS program embedded in a storage component such as a read-only memory (ROM) on the motherboard of the electronic device. On the one hand, both core and non-core functions are implemented by the BIOS itself, which increases the processing burden on the BIOS. On the other hand, the storage of the BIOS program that implements core and non-core functions on the ROM also occupies the BIOS's storage space, increasing the cost of the electronic device.

[0056] This application provides a processing method, as shown in the figure, the method includes:

[0057] S101: In response to a trigger condition being met, start a first application, wherein the first application is an application that can run in a pre-operating system environment;

[0058] In this step, the first application is used to achieve the first function, and the first application is an application that can run in a pre-operating system environment. The first application can be an existing application, utilizing an existing application to achieve the first function. Alternatively, the first application can be an additional application set up to achieve the first function.

[0059] Considering that there are usually multiple non-core functions, multiple first applications can be set up to implement each non-core function. Each first application can implement one of the multiple non-core functions. In implementation, a corresponding first application can be set up for each first function. When a certain non-core function is to be implemented, the system determines whether to launch the first application corresponding to the desired non-core function based on whether the trigger condition is met. If the trigger condition is met, the first application corresponding to the desired non-core function is launched in response to the trigger condition.

[0060] The first application can also be a single application. In this case, the first application can be considered a composite application that can be used to implement various non-core functions. To enable the same application (the first application) to implement various non-core functions, the first application can display an interface that provides options for implementing different non-core functions. Different non-core functions are implemented based on the operation of different options.

[0061] In this solution, the first application is launched based on a trigger condition. Furthermore, trigger conditions are pre-set; when a trigger condition is met, the first application is launched. A trigger condition can be any condition that can trigger the launch of the first application. There can be multiple trigger conditions, or there can be only one. As long as at least one of the multiple trigger conditions is met, the first application can be launched.

[0062] A pre-operating system (Pre-OS) can be a system that runs on an electronic device before, during, or after the operating system (OS) of the electronic device. Because a BIOS can run before the operating system (OS) of an electronic device, such as Windows or Linux, the pre-operating system environment can, in practice, be a system environment at the BIOS or UEFI stage. The first application of the technical solution in this application is an application that can run in a BIOS or UEFI environment.

[0063] S102: Control the first application to execute the target operation corresponding to the target request, so as to realize the first function that is different from the second function, wherein the second function includes at least the function of initializing the pre-operating system environment; wherein the storage location of the first data used to realize the first function is different from that of the second data used to realize the second function.

[0064] In this step, the second function is the core function of the BIOS. The core function is the aforementioned hardware self-test and initialization function, including power-on, initialization, reporting hardware status, and loading the bootloader.

[0065] It is understandable that when implementing the first function using the first application, the program code for the first function needs to be used to implement the first function. The startup and operation of the first application both require certain program code support. Based on this, the first data used to implement the first function in this solution includes the program code of the first application, the program code used to support or implement the startup and operation of the first application, and the program code that implements non-core functions.

[0066] The second data can be considered as program code that implements the core functions of the BIOS. In this application, the second data is stored in an electronic device, specifically in the ROM of the motherboard, while the first data is stored in a mobile device. The electronic device or its ROM is considered the storage location for the second data, and the mobile device is considered the storage location for the first data, thereby achieving different storage locations for the first data that implements the first function and the second data that implements the second function.

[0067] The first application can also be installed on a mobile device that is different from the electronic device. In the case where the first application is installed on the mobile device, the first data is stored in the mobile device, and the second data is stored in the electronic device, the electronic device, in response to a trigger condition being met, starts the first application installed on the mobile device and controls the first application to perform the target operation corresponding to the target request to implement the non-core functions of the BIOS. Thus, the processing logic shown in S101-S102 can be deployed in the electronic device.

[0068] In this solution, non-core BIOS functions are implemented by a first application, while core BIOS functions are implemented by the BIOS itself. Compared to related technologies where both core and non-core BIOS functions are implemented by the BIOS, this solution effectively reduces the processing burden on the BIOS. When non-core BIOS functions are needed, the first application is launched and used to implement the non-core functions, provided the triggering conditions are met. This approach is easy to implement in engineering and offers high reliability.

[0069] Considering that storing both the first and second data in the BIOS program's storage space—ROM—would inevitably occupy a large amount of BIOS storage space, to reduce the occupation of BIOS storage space and alleviate the burden on the ROM, the second data can be kept in its original storage location and still stored in the ROM of the electronic device. Alternatively, the first data can be stored in a different storage location than the ROM of the electronic device. For example, the second data can be stored in a mobile device, which can be a device with ROM, hard disk, Flash memory, etc., or it can be a combination of ROM, hard disk, and Flash memory. Storing the first data used to implement non-core functions in an external device (mobile device) reduces the occupation of BIOS storage space and lowers the cost of the electronic device.

[0070] In layman's terms, in this solution, to ensure the BIOS program, which performs core BIOS functions, has exclusive access to the ROM of the electronic device, the primary data for implementing non-core BIOS functions needs to be moved to an external device for storage. This separates the data for the two different functions, ensuring that using one set of data does not affect the other, thus providing good independence.

[0071] The target request can be a request that enables non-core BIOS functions. This includes, but is not limited to: requests for BIOS updates, recovery, or configuration; requests to launch diagnostic, monitoring, and / or recovery tools; requests to download applications; requests to download firmware; requests for interface coordination; requests to deploy BIOS services; requests to recycle electronic devices; and requests to modify BIOS configuration items. Correspondingly, the target operation includes, but is not limited to: performing BIOS updates, recovery, or configuration; launching diagnostic, monitoring, and / or recovery tools and performing diagnostic, monitoring, and / or recovery operations based on the launched tools; downloading applications; downloading firmware; performing interface coordination; performing deployment operations; performing recycling operations; and modifying BIOS configuration items.

[0072] Based on this, the first function can be considered to include, but is not limited to, the following: BIOS update, recovery, or configuration functions; functions for diagnosing whether the hard drive, memory, etc., are faulty (fault handling functions); functions for monitoring machine performance parameters (fault handling functions); functions for recovering from abnormal to normal (fault handling functions); functions for downloading applications, downloading firmware, interface coordination, and other software and hardware update or coordination functions; deployment functions; recycling functions; functions for modifying BIOS configuration items, etc.

[0073] In S101-S102, non-core BIOS functions can be implemented based on the control of a first application that can run in the BIOS environment. Furthermore, these non-core BIOS functions are implemented based on the first application performing target operations on target requests. While the core BIOS functions can be implemented, the first application can also be used to implement non-core BIOS functions, thus not affecting the normal use of both core and non-core BIOS functions. In addition, storing the second data used to implement the core BIOS functions and the first data used to implement the non-core functions separately maintains the independence between the data. Removing the first data for non-core functions from the BIOS storage space and storing it in another storage location can significantly reduce the BIOS storage space occupied.

[0074] The electronic devices in this solution include, but are not limited to, the following: terminals or servers. Terminals include, but are not limited to, mobile phones, tablets, all-in-one computers, desktop computers, smart speakers, smartwatches, etc. Servers include general-purpose servers, cloud servers, etc. Mobile devices are portable terminals or servers, such as mobile phones, tablets, smartwatches, etc.

[0075] The execution entity for S101 to S102 is preferably an electronic device. Preferably, a mobile device has a first application installed, first data is stored in the mobile device, and second data is stored in the electronic device. In response to a trigger condition being met, the electronic device starts the first application installed in the mobile device and controls the first application to perform the target operation corresponding to the target request to implement non-core functions of the BIOS. Thus, the non-core functions of the BIOS are implemented using the first application.

[0076] The above solution, based on the utilization of the first application, implements non-core BIOS functions without affecting their normal operation. Core BIOS functions are implemented when the electronic device enters the BIOS phase. This provides a new technical support for the implementation of both core and non-core BIOS functions.

[0077] As an optional solution in this application, such as Figure 2 As shown in S101', S101 responds to a trigger condition by including at least one of the following:

[0078] (1) In response to the completion of the initialization operation of the accessed mobile device, determine that the triggering condition is met.

[0079] Mobile devices can be encrypted or unencrypted. If the mobile device is encrypted, it can be a portable storage device such as a USB flash drive, external hard drive, or other storage device. In the case of encryption, completing the initialization process for the connected mobile device can be achieved by the electronic device successfully decrypting the mobile device.

[0080] When the mobile device is not an encrypted device, the initialization operation for the accessed mobile device can be completed by either establishing a communication connection between the mobile device and the electronic device, or by establishing a communication connection between the mobile device and the electronic device and authenticating the mobile device by the electronic device.

[0081] The electronic device responds by completing the initialization operation on the connected mobile device and determining that the triggering conditions are met. The electronic device then launches a first application installed on the mobile device, controls the first application to run, and controls the first application to execute the target operation corresponding to the target request to achieve the first function. In this case, the executing entity of the method logic in this scheme can specifically be the electronic device.

[0082] (2) In response to the completion of the initialization operation of the storage component where the first application is located, determine that the triggering condition is met;

[0083] When the first application is installed on a mobile device, the storage component where the first application resides can be the mobile device itself. During the BIOS phase of the electronic device, the device can perform self-tests and initializations on its own hardware, as well as on the storage component of the first application connected to the device. Upon completion of the self-test and initialization operations, the electronic device determines that the trigger conditions are met. In response to the met trigger conditions, it starts the first application installed on the mobile device and controls the first application to execute the target operation corresponding to the target request, thereby implementing the non-core functions of the BIOS.

[0084] (3) In response to receiving at least one target request, determine that the triggering condition is met, wherein the target request can perform a first function that is different from the second function.

[0085] Since there are many target requests, when at least one target request is generated, the electronic device responds to the generated target request, determines that the triggering condition is met, and starts the first application.

[0086] In addition to the requests mentioned above, the target request may include, but is not limited to: requests for lease management; requests for asset management; requests for data security processing (such as encryption and security authentication); and other requests that require customized services.

[0087] The above description illustrates that the first application in this application starts based on certain triggering conditions, which can avoid problems caused by incorrect startup. This improves the usability of non-core BIOS functions.

[0088] As an alternative approach, the target request in this application includes, but is not limited to, at least one of the following:

[0089] Requests to update, restore, or configure the basic input system of electronic devices; such as updating or restoring the BIOS version; reconfiguring the system time of electronic devices from the BIOS; and controlling the switching of input / output devices of electronic devices.

[0090] Requests to troubleshoot electronic devices; such as handling errors in the central processing unit (CPU) or hard drive of electronic devices; restoring electronic devices from a black screen and power-off state to a normal state;

[0091] Requests to update or repair the hardware and software of electronic devices; for example, to update or repair the software in the operating system (OS) of an electronic device; or to repair the hardware of an electronic device.

[0092] Requests for leasing or asset management of electronic equipment; such as saving or updating the accounts and passwords of all users using the electronic equipment; or saving or updating confidential data of reasonable users, such as the accounts and passwords assigned to each reasonable user for logging into a system or platform; or saving or updating data generated during the leasing process, such as the costs, leasing time, and leasing unit information of the leased factory.

[0093] Requests to securely process interactive data from electronic devices; for example, encrypting and storing important data generated by electronic devices so that password authentication is required before use.

[0094] Requests for customized services from electronic devices. These are personalized needs implemented by the user. For example, the user may have configured the BIOS settings to require a BIOS password before entering the BIOS. Or, the electronic device may only be allowed to launch the first application after the first application installed on it has been successfully decrypted.

[0095] If we consider the above requests as various types of requests, then there can be multiple first applications, each implementing the first function corresponding to a specific request within that type of request. When one of the requests meets the triggering condition, multiple first applications can be launched, including the one that implements the first function corresponding to that type of request.

[0096] For example, if a request is generated to update, restore, or configure the BIOS of an electronic device, a first application capable of performing the BIOS update, restore, or configuration is launched from among a plurality of first applications.

[0097] As described above, the technical solution of this application utilizes the first application to implement multiple non-core BIOS functions. This method of implementing non-core BIOS functions based on the control of the first application avoids occupying BIOS storage space and reduces resource burden. It also ensures the normal implementation of non-core BIOS functions.

[0098] Since it is impossible to list all the above-mentioned requests, any reasonable ones are within the scope of protection of this application.

[0099] The aforementioned target requests can be various requests obtained after the electronic device is powered on; or they can be requests obtained after the electronic device enters the OS.

[0100] Corresponding to the aforementioned target requests, the executable target operations and the first functionalities they implement are as follows:

[0101] Performs target operations to update, restore, or configure the basic input system of electronic devices, enabling the function of updating, restoring, or configuring the BIOS.

[0102] Perform the target operation to handle the fault, thus realizing the function of handling the fault.

[0103] Perform the target operation to update or repair the software and hardware of electronic devices, and realize the function of updating or repairing software and hardware.

[0104] Perform the target operations for leasing or asset management of electronic equipment to achieve the functions of leasing or asset management.

[0105] This function performs the target operation of securely processing interactive data from electronic devices.

[0106] Perform customized target operations to achieve customized functions.

[0107] This application provides various target operations to achieve different functions based on different target requests. The non-core BIOS functions provided by this solution are rich and diverse.

[0108] In the aforementioned solutions, non-core functions such as updating, restoring, or configuring the BIOS of electronic devices require the cooperation of the BIOS. In certain application scenarios, functions such as troubleshooting electronic devices, updating or repairing the hardware and software of electronic devices, managing the rental or assets of electronic devices, securely processing the interactive data of electronic devices, and providing customized services to electronic devices can be achieved without the cooperation of the BIOS.

[0109] As an optional method, such as Figure 3 As shown, the method further includes:

[0110] S301: Verify the extended attributes of the basic input / output system of an electronic device;

[0111] This step checks whether the electronic device's BIOS supports functional expansion. From a technical perspective, it checks whether the BIOS supports interaction with the primary application.

[0112] S302: If the basic input / output system can be expanded, control the first application to perform the corresponding target operation to achieve the first function;

[0113] If the BIOS can support interaction with the first application, it means that the BIOS supports functional expansion and controls the first application to perform the corresponding target operation to achieve the function that requires BIOS cooperation.

[0114] S303: If the basic input / output system cannot be expanded, control the first application to perform the corresponding target operation to achieve the third function, wherein the third function is not dependent on the basic input / output system.

[0115] If the BIOS cannot support interaction with the first application, it means that the BIOS does not support the extension of functions and controls the first application to perform the corresponding target operation to achieve the function that can be achieved without the cooperation of the BIOS.

[0116] In S301 to S303, functions requiring BIOS collaboration can be implemented by controlling the first application, provided the BIOS supports expansion. Conversely, functions that do not require BIOS collaboration but are not core BIOS functions can be implemented by controlling the first application, provided the BIOS does not support expansion. This approach, based on the BIOS's expandability, enables the normal implementation of both BIOS-required and non-BIOS-required functions.

[0117] As an optional method, such as Figure 4 As shown, the scheme for controlling the first application to execute the target operation corresponding to the target request to achieve the first function includes:

[0118] S401: Display the interface information of the first application, the interface information including option information for implementing different functions;

[0119] Taking the first application as an example, when the electronic device launches the first application, the interface information of the first application is displayed, and the interface information provides option information such as icons that can realize different functions.

[0120] Examples include icons for implementing BIOS update, recovery, or configuration functions; icons for implementing fault handling functions; icons for implementing software and hardware update or repair functions; icons for implementing secure processing of interactive data; and icons for implementing customized services.

[0121] These icons can be displayed sequentially in the first application's interface, such as from top to bottom or bottom to top. Alternatively, they can be displayed in different levels, with one icon at each level, and some overlap between levels. Multi-functional icons designed for BIOS update, recovery, or configuration functions can be displayed in a multi-level collapsed format. For example, the first level icon might be a multi-functional icon providing BIOS update, recovery, or configuration functions. After the user selects this icon, the second level of icons appears, containing three sub-icons that sequentially implement the BIOS update, recovery, and configuration functions for the user to choose from.

[0122] S402: Execute a corresponding first function based on the operation of the option information, the first function being implemented based on the standard or protocol between the first application and the basic input / output system and the program components included in the basic input / output system.

[0123] The electronic device receives the user's selection of an icon and implements the function corresponding to the selected icon. Based on the standard or protocol between the first application and the BIOS, the electronic device calls the BIOS program component capable of implementing the first function and the program code (first data) stored in the mobile device, uses the program component to run the program code, and thus implements the first function.

[0124] The standard or protocol between the first application and the BIOS is the standard or protocol that can be supported between the first application and the BIOS. This standard or protocol can be... Figure 5 Industry standards or vendor standards in the BIOS, IFID (domain) Specification, ODR (vendor) Specification, and FWTAG Specification in the BIOS field.

[0125] In S401 to S402, functions can be selected based on the interface information of the first application. With the support of standards or protocols between the first application and the basic input / output system, non-core BIOS functions are implemented. The interface intuitively displays the externally provided non-core BIOS functions, improving the user experience. Based on protocols or standards, the BIOS program components ensure the smooth implementation of non-core BIOS functions.

[0126] In the aforementioned scheme, executing the corresponding first function based on the operation on the option information includes at least one of the following:

[0127] If the operation is a file selection operation, perform a function operation to download or upgrade at least one of the application, firmware, and driver; for example, in the interface presented by the first application, select the file of the application, firmware, and driver to be downloaded or upgraded to realize the function of downloading or upgrading the application, firmware, and driver.

[0128] If the operation pertains to asset management or lease management options on an electronic device, at least interface information for performing asset management or lease management should be output. For example, in the interface presented by the first application, selecting an asset management or lease management option will output interface information for performing asset management or lease management, such as displaying an interface for editing asset or lease information. Within this interface, operations such as adding, deleting, and modifying asset or lease information can be performed.

[0129] If the operation triggers the setup of the Basic Input / Output System (BIOS), at least the BIOS setup interface is output, wherein at least some of the settings in the setup interface come from the first application. For example, if the BIOS settings option is selected in the interface presented by the first application, the first application outputs the BIOS setup interface, such as the BIOS setup interface. The setup interface provides settings such as BIOS version updates, BIOS version restoration, and system time configuration. Based on the selection of these settings, functions such as BIOS version updates, restoration, and system time reset can be performed. The setup interface also includes any other conceivable BIOS settings.

[0130] It is understood that the BIOS setup interface described above presents settings data that enable non-core BIOS functions. An interface presenting settings data that enable core BIOS functions can also be considered a BIOS setup interface. Settings data enabling non-core BIOS functions can be presented through a first application. Settings data enabling core BIOS functions can be presented through the first application or through the electronic device's own BIOS interface. The first application's interface can simultaneously display both settings data enabling non-core BIOS functions and settings data enabling core BIOS functions. Users can select the appropriate settings data based on their actual needs.

[0131] If the user selects a setting item to implement the core functions of the BIOS in the interface of the first application, then the technical solution of this application can not only implement the non-core functions of the BIOS based on the control of the first application, but also implement the core functions of the BIOS.

[0132] The settings data that enable the core functions of the BIOS include, but are not limited to, the following: the range of hardware that needs to perform a power-on self-test, and the self-test status of the hardware within that range.

[0133] If the operation involves invoking a target tool, at least the corresponding target tool should be launched for user access. For example, in the interface presented by the first application, the diagnostic tool ( Figure 5The device must be launched with at least one of the following tools: a diagnostic tool (SMBiosTool), a monitoring tool (SMBiosTool), and a recovery tool (RecoveryTool). The diagnostic tool is used to diagnose the hard drive and memory of the electronic device; the monitoring tool is used to monitor the CPU usage of the electronic device; and the recovery tool is used to restore the electronic device from a black screen state to a normal state. Additionally, there is a write / erase tool for erasing and rewriting hard drive data. Any reasonable tool is within the scope of this application.

[0134] In the aforementioned solution, the corresponding functions are implemented based on the operation of the option information included in the interface of the first application, which enables the normal implementation of non-core BIOS functions. This improves the ease of use in implementing non-core BIOS functions.

[0135] In one alternative approach, the configuration information of the electronic device is updated based on the settings information of the settings interface of the basic input / output system acting on the output of the first application.

[0136] The configuration information of electronic devices can be any information that can be configured in the BIOS, such as the status of the electronic device and the system time. The status of the electronic device includes states S0 to S5. S0 is the operating state of the electronic device. S1 is the POS (Power on Suspend) state of the electronic device. S2 is the running / stopped state. S4 is the STD (Suspend to Disk) state. S5 is the completely off state with zero power consumption. If the first application and the BIOS support the above protocols or standards, the status of the electronic device can be set or updated based on the settings or updates for the electronic device's status information output by the first application's BIOS setup interface, such as the BIOS setup interface.

[0137] The settings or changes to the different states of electronic devices can be communicated to the BIOS via different transmission channels, enabling synchronized updates of BIOS settings. This provides a new approach to setting or changing BIOS settings.

[0138] The system time of electronic devices can be configured in the BIOS. When the first application and the BIOS support the above-mentioned protocols or standards, the system time of electronic devices can be set or updated based on the addition or updating of the system time setting information of electronic devices on the BIOS setup interface output by the first application, such as the BIOS setup interface.

[0139] Assuming the basic input / output system (PIS) is expandable, the aforementioned scheme for controlling the first application to execute a target operation corresponding to a target request to achieve a first function includes: providing an interface for receiving the target operation, and implementing the corresponding first function based on the target operation obtained through the interface. The interface may or may not belong to the electronic device. The first function is implemented based on a standard or protocol between the first application and the PIS and the program components included in the PIS. This can be understood as follows: the electronic device has audio input / output interfaces, image input / output interfaces, and string input / output interfaces (such as a keyboard interface). Users can request to execute BIOS updates, recovery or configuration functions, request fault handling, or request software or hardware updates or repairs—non-core BIOS functions—through audio, image, and keyboard input. Further, when triggering conditions are met, the first application is launched. Based on the target request generated by the user through audio, image, and keyboard input, the electronic device calls a BIOS program component capable of implementing the first function corresponding to the target request and program code stored in the mobile device corresponding to the target request. The program component runs the program code, thereby implementing the non-core function requested by the user.

[0140] Electronic devices can also reuse the audio input / output, image input / output, and string input / output interfaces of other electronic devices as their own interfaces. When a user receives a target request from another electronic device via audio, image, or keyboard input—for example, a request to upgrade the device's hardware or software via audio or keyboard input—the electronic device generates a corresponding target operation based on this request. The electronic device then calls a BIOS program component capable of implementing the first function corresponding to the target request and the corresponding program code stored in the mobile device. The program component executes the program code, thereby implementing the non-core function requested by the user.

[0141] In the aforementioned solution, the target operation can be acquired based on the interface of an electronic device or other electronic devices that can be reused by the electronic device, thereby realizing the non-core functions of the BIOS. This provides a new technical support for realizing the non-core functions of the BIOS.

[0142] When the keyboard interface is activated, the keyboard can be configured with different backlighting effects. The interface of the first application provides setting data for setting or updating keyboard backlighting effects. Based on the setting data presented in the first application interface, and based on the user's settings or updates to the setting data, different backlighting effects can be selected for the keyboard. Furthermore, different keys on the keyboard have multiple selectable backlighting effects. The interface of the first application provides setting data for setting or updating the backlighting effects of each key. Based on the user's settings or updates to the backlighting effects of each key, different backlighting effects can be selected for the key. This improves the user experience.

[0143] As an alternative approach, the aforementioned scheme of controlling the first application to execute the target operation corresponding to the target request to achieve the first function includes: if it is determined that the mobile device connected to the electronic device is configured with an interface capable of receiving the target operation, the target operation is obtained through the interface of the mobile device to achieve the corresponding first function. That is, when the mobile device connected to the electronic device is configured with an audio input / output interface, an image input / output interface, and a string input / output interface capable of receiving the target operation, the user inputs the first function they wish to achieve through audio, image, and keyboard input. For example, the user inputs a target request to upgrade the hardware and software of the electronic device through audio input or keyboard input. Based on the target request, a target operation to upgrade the hardware and software is generated to achieve the function of upgrading the hardware and software of the electronic device.

[0144] In the aforementioned solution, the target operation can be acquired based on the interface of the mobile device connected to the electronic device, thereby realizing the non-core functions of the BIOS. This provides a new technical support for realizing the non-core functions of the BIOS.

[0145] Combination Figure 5 The technical solution of this application will be further explained.

[0146] exist Figure 5 In the application scenario shown, a first application (APP) is installed on a mobile device. First data, used to implement non-core BIOS functions, is stored on the mobile device. Second data, used to implement core BIOS functions, is stored on the electronic device. Specifically, the first application can be an APP conforming to the Unified Extensible Firmware Interface (UEFI) specification. Both the APP and the electronic device's BIOS support the UEFI specification or protocol (extensible protocols, such as...). Figure 5 The StandardExtensibleProtocol (SEP) is based on UEFI specifications or protocols. APP can run in the BIOS environment, and BIOS has extensible properties (BIOS supports extensibility).

[0147] like Figure 5As shown, the BIOS of an electronic device can perform power-on, hardware self-test and initialization, load the bootloader, report hardware status, and switch from the BIOS to the OS of the electronic device after the electronic device is powered on.

[0148] In related technologies, modifying or setting non-core BIOS functions requires the electronic device to enter the BIOS system and configure these functions through the setup interface provided by the BIOS. This means the electronic device's ROM must store both the program code implementing the core BIOS functions and the program code implementing the non-core functions, undoubtedly increasing the burden on storage resources.

[0149] In this application scenario, the program code implementing the core BIOS functions is still stored in the ROM of the electronic device. The program code implementing non-core BIOS functions is moved to an external storage location, such as a mobile device, to reduce the storage resource usage of the electronic device. After the program code implementing non-core BIOS functions is moved to an external storage location, the following method can be used to configure or modify these functions.

[0150] When the electronic device is powered on, a mobile device is connected or plugged into the device. The system checks if the device's BIOS supports expansion. If not, the process ends. If yes, the process continues. Because the mobile device has an encryption password, the electronic device needs to decrypt it. Successful decryption indicates that the initialization of the connected mobile device is complete. In response to the completion of the initialization of the connected mobile device, the electronic device determines that the triggering conditions for launching the app are met and triggers the app to launch. The app is then guided into the BIOS environment of the electronic device using the device's bootloader, allowing the app to run within the BIOS environment. The app's ability to run in the BIOS environment is due to the support for protocols or specifications such as industry / Vendor standard and IFID Specification between the app and the BIOS.

[0151] The APP running in the BIOS environment outputs an interface for users to select different non-core functions. This interface includes multiple options: options for updating, restoring, or configuring the BIOS; options for troubleshooting; options for upgrading hardware and software; options for leasing or asset management; options for data security processing; and options for providing customized services.

[0152] Users can select the options they need based on their actual situation. Users can request this by entering an audio message such as "Please select the BIOS update option" or by typing "Select the BIOS update option" into the interface via the keyboard.

[0153] For example, taking the selection of the option to update the BIOS as an example, this selection operation can be regarded as a target request. Based on this target request, the electronic device calls the BIOS program component in the electronic device that can realize the function of updating the BIOS version, and the program code stored in the mobile device that can realize the function of updating the BIOS version. The program component runs the program code, thereby realizing the non-core function requested by the user. Among them, the BIOS program component can be provided by the BIOS kernel (KernalBIOS).

[0154] For example, taking the selection of the BIOS configuration option as an example, the selection operation can be regarded as a target request. Based on the target request, the electronic device calls the BIOS program component in the electronic device that can implement the BIOS option configuration function, and the program code stored in the mobile device that can implement the BIOS option configuration function. The program component runs the program code, thereby realizing the non-core function requested by the user.

[0155] For example, taking the option to upgrade the hardware and software as an example, if a file of an application to be updated is selected, the selection operation can be regarded as a target request. Based on the target request, the electronic device calls the BIOS program component in the electronic device that can realize the download function of the application, and the program code stored in the mobile device that can realize the download function of the application. The program component runs the program code, thereby realizing the non-core function requested by the user.

[0156] As can be seen from the above, by using the technical solution of this application, the second data used to implement the core functions of the BIOS and the first data used to implement non-core functions are stored separately in two different devices, maintaining the independence of the data and preventing mutual interference. Removing the first data used to implement non-core BIOS functions from the BIOS storage space and storing it in another location can significantly reduce the amount of BIOS storage space occupied.

[0157] Furthermore, by storing the primary data for implementing non-core BIOS functions in other storage locations, these non-core BIOS functions can be implemented based on the control of applications running within the BIOS environment, thus ensuring the normal operation of these functions without affecting their functionality. This application provides technical support for the normal implementation of non-core BIOS functions.

[0158] The advantages of the technical solution in this application also include:

[0159] 1) It greatly reduces the space occupied by BIOS storage, allowing electronic device motherboards to store BIOS core code with a smaller ROM, which can effectively reduce hardware costs.

[0160] 2) It can expand more non-core BIOS functions because the program code that implements non-core functions is moved to other storage locations. Therefore, the program code that implements non-core functions is not limited by capacity or space, and the code executes more smoothly.

[0161] 3) By utilizing the first application, more security and customization functions can be provided to users, offering high flexibility. The flexible selection of mobile devices can avoid the problem of excessive costs caused by the purchase of mobile devices.

[0162] 4) The app can run in the BIOS environment without relying on the OS. Based on the app running in the BIOS environment, non-core BIOS functions can be implemented normally and smoothly.

[0163] 5) The technical solution of this application supports industry-standard communication protocols between the APP and BIOS, making it highly versatile and widely portable and usable. For BIOS function development, it offers high development efficiency and significant economic benefits.

[0164] This application also provides a processing apparatus, such as... Figure 6 As shown, the device includes: a starting unit 601 and a control unit 602; wherein,

[0165] The startup unit 601 is configured to start a first application in response to a trigger condition being met, wherein the first application is an application capable of running in a pre-operating system environment;

[0166] Control unit 602 is used to control the first application to perform a target operation corresponding to the target request, so as to realize a first function that is different from the second function, wherein the second function includes at least the function of initializing the pre-operating system environment;

[0167] Wherein, at least the first data used to implement the first function is stored in a different location than the second data used to implement the second function.

[0168] In an alternative embodiment, the apparatus further includes a determining unit for:

[0169] In response to the completion of the initialization operation for the accessed mobile device, it is determined that the triggering condition is met;

[0170] In response to the completion of the initialization operation of the storage component where the first application resides, it is determined that the triggering condition is met; or,

[0171] In response to receiving at least one target request, it is determined that the triggering condition is met, wherein the target request is capable of performing a first function that is distinct from the second function.

[0172] In one alternative, the target request includes at least one of the following:

[0173] Requests to update, restore, or configure the basic input system of electronic devices;

[0174] A request for troubleshooting of electronic equipment;

[0175] A request to update or repair the hardware or software of an electronic device;

[0176] Requests for leasing or asset management of electronic equipment;

[0177] A request to securely process interactive data from electronic devices;

[0178] Requests for customized services to be output by electronic devices.

[0179] In an alternative embodiment, the device further includes a verification unit for verifying extended properties of the basic input / output system of the electronic device;

[0180] The control unit 602 is used for:

[0181] If the basic input / output system can be expanded, the first application can be controlled to perform the corresponding target operation to achieve the first function;

[0182] If the basic input / output system cannot be expanded, the first application is controlled to perform the corresponding target operation to achieve the third function, wherein the third function is implemented independently of the basic input / output system.

[0183] In one alternative embodiment, the control unit 602 is configured to:

[0184] Display the interface information of the first application, the interface information including option information for implementing different functions;

[0185] Based on the operation of the option information, a corresponding first function is executed, the first function being implemented based on the standard or protocol between the first application and the basic input / output system and the program components included in the basic input / output system.

[0186] In one alternative embodiment, the control unit 602 is configured to:

[0187] If it is determined that the basic input / output system can be expanded, an interface is provided for receiving a target operation to implement a corresponding first function based on the target operation obtained through the interface, wherein the interface may or may not belong to the electronic device, and the first function is implemented based on a standard or protocol between the first application and the basic input / output system and the program components included in the basic input / output system.

[0188] In one alternative embodiment, the control unit 602 is configured to:

[0189] If it is determined that the mobile device connected to the electronic device is configured with an interface capable of receiving the target operation, the target operation is obtained through the interface of the mobile device to achieve the corresponding first function.

[0190] In one alternative embodiment, the control unit 602 is configured to:

[0191] If the operation is a file option operation, perform a functional operation to download or upgrade at least one of the application, firmware, and driver;

[0192] If the operation is an operation on the asset management option or lease management option of the electronic device, at least the interface information for performing asset management or lease management shall be output;

[0193] If the operation is to trigger the setting of the basic input / output system, at least the setting interface of the basic input / output system shall be output, wherein at least some of the setting items in the setting interface are from the first application;

[0194] If the operation involves invoking a target tool, at least the corresponding target tool should be launched for the user to use.

[0195] In one alternative embodiment, the control unit 602 is configured to update the configuration information of the electronic device based on the setting information of the basic input / output system setting interface acting on the first application output.

[0196] It should be noted that the processing device in this application embodiment solves the problem in a similar way to the aforementioned processing method. Therefore, the implementation process, implementation principle, and beneficial effects of the processing device can all be found in the description of the implementation process and implementation principle of the aforementioned method, and repeated details will not be repeated.

[0197] According to embodiments of this application, this application also provides an electronic device and a readable storage medium.

[0198] Figure 7A schematic block diagram of an example electronic device 800 that can be used to implement embodiments of this application is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the application described and / or claimed herein.

[0199] like Figure 7 As shown, device 800 includes a computing unit 801, which can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) 802 or a computer program loaded from storage unit 808 into random access memory (RAM) 803. RAM 803 may also store various programs and data required for the operation of device 800. The computing unit 801, ROM 802, and RAM 803 are interconnected via bus 804. Input / output (I / O) interface 805 is also connected to bus 804.

[0200] Multiple components in device 800 are connected to I / O interface 805, including: input unit 806, such as keyboard, mouse, etc.; output unit 807, such as various types of monitors, speakers, etc.; storage unit 808, such as disk, optical disk, etc.; and communication unit 809, such as network card, modem, wireless transceiver, etc. Communication unit 809 allows device 800 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0201] The computing unit 801 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 801 performs the various methods and processes described above, such as processing methods. For example, in some embodiments, the processing method may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 808. In some embodiments, part or all of the computer program may be loaded and / or installed on device 800 via ROM 802 and / or communication unit 809. When the computer program is loaded into RAM 803 and executed by the computing unit 801, one or more steps of the processing method described above may be performed. Alternatively, in other embodiments, the computing unit 801 may be configured to perform processing methods by any other suitable means (e.g., by means of firmware).

[0202] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0203] The program code used to implement the methods of this application may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing device, such that when executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0204] In the context of this application, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0205] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0206] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0207] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.

[0208] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A processing method, comprising: In response to the fulfillment of a trigger condition, a first application is launched. The first application is an application that can run in a pre-operating system environment. The first application is program code for non-core functions of the BIOS. Control the first application to execute the target operation corresponding to the target request, so as to realize the first function that is different from the second function, wherein the second function includes at least the function of initializing the pre-operating system environment, and the first function is a non-core function that can be further realized when implementing the core functions of BIOS; Wherein, at least the first data used to implement the first function is stored in a different location than the second data used to implement the second function; The method further includes: Verify the extended properties of the basic input / output system of electronic devices; If the basic input / output system can be expanded, the first application can be controlled to perform a corresponding target operation to achieve a first function, the first function being implemented based on the standard or protocol between the first application and the basic input / output system and the program components included in the basic input / output system; If the basic input / output system cannot be expanded, the first application is controlled to perform the corresponding target operation to achieve the third function, wherein the third function is implemented independently of the basic input / output system.

2. The method according to claim 1, wherein, In response to a triggering condition being met, at least one of the following is included: In response to the completion of the initialization operation for the accessed mobile device, it is determined that the triggering condition is met; In response to the completion of the initialization operation of the storage component where the first application is located, it is determined that the triggering condition is met; or, In response to receiving at least one target request, it is determined that the triggering condition is met, wherein the target request is capable of performing a first function that is distinct from the second function.

3. The method according to claim 2, wherein, The target request includes at least one of the following: Requests to update, restore, or configure the basic input system of electronic devices; A request for troubleshooting of electronic equipment; A request to update or repair the hardware or software of an electronic device; Requests for leasing or asset management of electronic equipment; A request to securely process interactive data from electronic devices; Requests for customized services to be output by electronic devices.

4. The method according to any one of claims 1 to 3, wherein, The control of the first application to execute the target operation corresponding to the target request to achieve the first function includes: Display the interface information of the first application, the interface information including option information for implementing different functions; The first function is executed based on the operation of the option information.

5. The method according to any one of claims 1 to 3, wherein, The control of the first application to execute the target operation corresponding to the target request to achieve the first function includes: If it is determined that the basic input / output system can be expanded, an interface for receiving target operations is provided to implement a corresponding first function based on the target operations obtained through the interface, wherein the interface may or may not belong to the electronic device.

6. The method according to any one of claims 1 to 3, wherein, The control of the first application to execute the target operation corresponding to the target request to achieve the first function includes: If it is determined that the mobile device connected to the electronic device is configured with an interface capable of receiving the target operation, the target operation is obtained through the interface of the mobile device to achieve the corresponding first function.

7. The method according to claim 4, wherein, Execute a corresponding first function based on the operation on the option information, including at least one of the following: If the operation is a file option operation, perform a functional operation to download or upgrade at least one of the application, firmware, and driver; If the operation is an operation on the asset management option or lease management option of the electronic device, at least the interface information for performing asset management or lease management shall be output; If the operation is to trigger the setting of the basic input / output system, at least the setting interface of the basic input / output system shall be output, wherein at least some of the setting items in the setting interface are from the first application; If the operation involves invoking a target tool, at least the corresponding target tool should be launched for the user to use.

8. The method according to claim 7, further comprising: The configuration information of the electronic device is updated based on the settings information of the settings interface of the basic input / output system that operates on the output of the first application.

9. A processing apparatus, comprising: A startup unit is used to start a first application in response to a trigger condition being met. The first application is an application that can run in a pre-operating system environment. The first application is program code for non-core functions of the BIOS. The control unit is used to control the first application to execute the target operation corresponding to the target request, so as to realize the first function that is different from the second function. The second function includes at least the function of initializing the pre-operating system environment, and the first function is a non-core function that can be further realized when the core functions of BIOS are implemented. Wherein, at least the first data used to implement the first function is stored in a different location than the second data used to implement the second function; The device also includes a verification unit for verifying the extended properties of the basic input / output system of the electronic device. The control unit is configured to control the first application to perform a corresponding target operation to achieve a first function if the basic input / output system can be expanded. The first function is implemented based on a standard or protocol between the first application and the basic input / output system and the program components included in the basic input / output system. If the basic input / output system cannot be expanded, the first application is controlled to perform the corresponding target operation to achieve the third function, wherein the third function is implemented independently of the basic input / output system.