Characteristic switching method and related device

Abstract

The characteristic switching method and the related device provided by the embodiments of the present application relate to the terminal technical field. The method comprises the following steps: when the Bluetooth earphone is configured with a first characteristic, the electronic device can control the Bluetooth earphone to switch to a second characteristic; during the characteristic switching process, the Bluetooth earphone can be switched from the first characteristic to a basic function first, and then switched from the basic function to the second characteristic; the version of the added basic function is used to reduce the version incompatibility problem in the different characteristic switching processes; in this way, the version package of different characteristics can be installed in the Bluetooth earphone, different characteristic functions can be realized in the same Bluetooth earphone, the functions of the Bluetooth earphone are enriched, and the use experience of the user is improved.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to feature switching methods and related equipment. Background Technology

[0002] Resource-constrained devices have limited performance. For example, their computing power, storage space, battery life, and network bandwidth are all limited.

[0003] Resource-constrained devices include, for example, Bluetooth headsets. Bluetooth headsets can support Low Delay Audio Codec (LDAC) features to enable high-quality audio playback for users. Bluetooth headsets can also support Low Energy Audio (LEA) features to reduce power consumption and extend the duration of audio playback.

[0004] However, in most implementations, due to performance limitations, Bluetooth headsets can only deploy one of the features: LDAC or LEA. For example, Bluetooth headset A supports LDAC, resulting in higher audio quality, but its battery life is shorter. Conversely, Bluetooth headset B supports LEA, offering longer battery life, but its audio quality is lower, leading to a poorer user experience. Summary of the Invention

[0005] This application provides a feature switching method and related device, which are applied in the field of terminal technology. For resource-constrained devices, different feature versions of packages can be installed on the resource-constrained device, thereby enabling different feature functions on the same resource-constrained device, enriching the functionality of the resource-constrained device and improving the user experience.

[0006] In a first aspect, embodiments of this application propose a feature switching method applied to a first device. The method includes: displaying a first interface when the first device and the second device establish communication; the first device is used to manage the second device; the first interface is an application interface for managing the second device; the first interface includes a first control; wherein the first control is used to instruct the second device to perform feature switching, and the first control represents that the second device is configured with a first feature; the first device is different from the second device.

[0007] This scenario can correspond to Figure 5 , Figure 6 or Figure 7The scenario is illustrated. Specifically, the first device can be a device used to manage resource-constrained devices, and the second device can be a resource-constrained device. The first and second devices establish communication, including but not limited to: Bluetooth connection, network connection, near field communication (NFC) connection, etc. The first interface can be, for example... Figure 5 The interface shown in c is or Figure 7 The interface shown in Figure 'a'; the application used to manage the second device may be, for example, a device management application; the first control may be, for example... Figure 5 The feature switching control 503 in the interface shown in Figure c is... Figure 7 The feature switching control 701 in the interface shown in Figure 'a'. The first feature can be a feature that resource-constrained devices can support, such as the LEA feature.

[0008] A trigger operation is received for the first control; the trigger operation for the first control is used to instruct the second device to switch from the first feature to the second feature.

[0009] The second feature can be any feature other than the first feature that a resource-constrained device can support. The triggering operation for the first control could, for example, be used to instruct the Bluetooth headset to switch from the LEA feature to the LDAC feature.

[0010] Based on the trigger operation on the first control, the second device is instructed to switch from the first feature to the third feature, and then instructed to switch from the third feature to the second feature; wherein, the third feature is a feature that supports the second device to run basic functions; the first feature and the second feature are both features that run extended functions based on the third feature, and the first feature and the second feature are different.

[0011] The third characteristic can be a basic functional characteristic supported by resource-constrained devices. For example, the third characteristic can be a basic audio playback function characteristic corresponding to the compatible version package in this embodiment. In this embodiment, the third characteristic is a basic functional characteristic, while the first and second characteristics are advanced functions supported by the basic function. For example, the first and second characteristics are LEA and LDAC characteristics, respectively. During the switching process, the first device controls the second device to switch from one advanced characteristic to a basic functional characteristic, and then from a basic functional characteristic to another advanced characteristic. Using a version package of basic functions for transition during the upgrade process can effectively reduce scenarios where the first and second characteristics are incompatible.

[0012] The second interface is displayed; the second interface includes a first control, and the first control represents that the second device is configured with a second feature.

[0013] The second interface can be, for example... Figure 6 The interface shown in d or Figure 7The interface shown in 'c'; the first control can be Figure 6 The feature switching control 503 in the interface shown by d, or Figure 7 The feature switching control 701 in the interface shown in Figure c. This feature switching control indicates switching to the second feature; for example, both feature switching controls 503 and 701 indicate that the Bluetooth headset is configured with the LDAC feature.

[0014] In this way, when using resource-constrained devices, the device can be switched between two or more features, allowing the same resource-constrained device to support more features, thus enriching the functionality of the resource-constrained device and improving the user experience.

[0015] In one possible implementation, the first device includes an electronic device, the second device includes a Bluetooth headset, and the first and second features are different audio encoding methods; the first feature includes Bluetooth Low Energy (LEA) features or Low Latency Audio Codec (LDAC) features; the second feature includes LADC features or LEA features; the third feature is a feature that supports the Bluetooth headset to operate basic functions, which include at least one of the following: basic Bluetooth connectivity functions, basic audio decoding functions, and basic audio playback functions.

[0016] In this embodiment, the resource-constrained device can be a Bluetooth headset, and the device for managing the Bluetooth headset can be an electronic device. The first and second characteristics can be characteristics supported by the Bluetooth headset, such as audio encoding methods, where the first characteristic is LEA and the second characteristic is LDAC; or the first characteristic is LDAC and the second characteristic is LEA. The third characteristic can be a characteristic of the basic audio function corresponding to the compatible version package in this embodiment.

[0017] In this way, when using Bluetooth headphones, users can switch between two or more features, allowing the same Bluetooth headphones to support more features, enriching the functionality of Bluetooth headphones and improving the user experience.

[0018] In one possible implementation, instructing the second device to switch from a first feature to a third feature based on a trigger operation on the first control includes: obtaining a first version number of a first feature version package from the Bluetooth headset based on the trigger operation on the first control; wherein the first feature version package is used to support the Bluetooth headset running the first feature; the first version number is less than or equal to the actual version number of the first feature version package; downloading a third feature version package from an over-the-air (OTA) server based on the first version number and an identifier of the third feature version package; wherein the identifier of the third feature version package is used to indicate that the version package type returned by the OTA server is a third feature version package; the third feature version package is used to support the Bluetooth headset running the third feature; the version number of the third feature version package is greater than the first version number; sending the third feature version package to the Bluetooth headset and instructing the Bluetooth headset to install the third feature version package.

[0019] This process can be referenced. Figure 13 The relevant descriptions in steps S1307-S1310 are as follows. The identifier of the third feature version package can be, for example, type=ALL; the version package type can include the first feature version package, the second feature version package, and a compatible version package, etc. It is understood that during feature switching, the Bluetooth headset can return a first version number after virtually downgrading the first feature version package to the electronic device. The electronic device can then request to download a compatible version package from the OTA server based on the first version number. The version number of the compatible version package returned by the OTA server is greater than the first version number. In this way, during version upgrades, virtual downgrading controls the Bluetooth headset's upgrade path to upgrade from a lower version to a higher version, thereby reducing scenarios where version upgrades fail due to limited upgrade paths.

[0020] In one possible implementation, the first feature version package is compatible with the third feature version package; the first version number of the first feature version package includes the minimum version number of the first feature version package; and the version number of the third feature version package includes the maximum version number of the third feature version package.

[0021] In this embodiment, the first feature version package and the compatible version package are compatible, so that when the Bluetooth headset is upgraded from the first feature version package to the compatible version package, no incompatibility issues will occur. The first version number can be the minimum version number of the first feature version package; the version number of the compatible version package can be the maximum version number of the compatible version package. This increases the probability that the version number of the compatible version package is greater than the first version number, thereby increasing the success rate of upgrading from the first feature version package to the compatible version package.

[0022] In one possible implementation, instructing the second device to switch from the third feature to the second feature includes: downloading a second feature version package from an OTA server based on the version number of the third feature version package and the identifier of the second feature version package; wherein the identifier of the second feature version package is used to indicate that the version package type returned by the OTA server is a second feature version package; the second feature version package is used to support the Bluetooth headset to run the second feature; the version number of the second feature version package is greater than the version number of the third feature version package; sending the second feature version package to the Bluetooth headset and instructing the Bluetooth headset to install the second feature version package.

[0023] This process can correspond to Figure 13 The relevant descriptions in steps S1311-S1313 are as follows. The second feature can be, for example, the LDAC feature, with the second feature version package identified as type=LDAC; the second feature can also be, for example, the LEA feature, with the second feature version package identified as type=LEA. It is understood that during feature switching, the electronic device can request to download the second feature version package from the OTA server based on the version number of the compatible version package. The version number of the second feature version package returned by the OTA server is greater than the version number of the compatible version package. In this way, during version upgrades, the upgrade path of the Bluetooth headset is controlled to upgrade from a lower version to a higher version, reducing scenarios where version upgrades fail due to limited upgrade paths; the upgrade process from the first feature version package to the compatible version package, and then from the compatible version package to the second feature version package is completed, thereby enabling the control of the Bluetooth headset to switch from the first feature to the second feature.

[0024] In one possible implementation, the third feature package is compatible with the second feature package; the version number of the second feature package includes the maximum version number of the second feature package.

[0025] In this embodiment, the second feature version package is compatible with the compatible version package. This ensures that the Bluetooth headset will not encounter incompatibility issues when upgrading from the compatible version package to the second feature version package. The version number of the second feature version package can be the maximum version number of the second feature version package. This increases the probability that the version number of the second feature version package is greater than the version number of the compatible version package, thereby increasing the success rate of upgrading from the compatible version package to the second feature version package.

[0026] In one possible implementation, receiving a trigger operation for the first control includes receiving a click operation for the first control.

[0027] In this embodiment, the feature switching method is applicable to dual-feature switching in resource-constrained devices. This process can correspond to... Figure 7 The illustrated embodiment; the first control may be, for example... Figure 7 The feature switching control 701 is shown in the interface shown in Figure a.

[0028] In this way, when Bluetooth headphones support dual-feature switching, electronic devices can provide users with an entry point to switch Bluetooth headphone features through feature switching controls, making it easier for users to operate; Bluetooth headphones can switch between two features, providing users with a richer listening experience.

[0029] In one possible implementation, receiving a trigger operation for the first control includes: receiving a click operation for the first control; after receiving the trigger operation for the first control, it further includes: displaying a third interface; the third interface includes a second control and a third control, the second control corresponding to a first characteristic and the third control corresponding to a second characteristic; the second control is in a selected state and the third control is in an unselected state; and receiving a selection operation for the third control.

[0030] In this embodiment, the feature switching method is applicable to multi-feature switching in resource-constrained devices. This process can correspond to... Figure 5 The illustrated embodiment; the first control may be, for example... Figure 5 The feature switching control 503 in the interface shown in Figure c. The third interface can be, for example... Figure 5 In the interface shown by d, the second control can be, for example, the LEA selection box 506, and the third control can be, for example, the LDAC selection box 507; the selection operation for the third control can be, for example, in Figure 6 The operation of clicking the LDAC selection box 507 in the interface shown in a is shown in the figure.

[0031] It should be noted that this application embodiment only uses two features as an example to illustrate the feature switching method. However, in practical applications, electronic devices can also control Bluetooth headsets to switch between three, four, or even more features. This application embodiment will not provide further examples for this. In addition, dual features can also be applied to this scenario, and this application embodiment does not limit this application.

[0032] In this way, when Bluetooth headsets support multiple feature switching, electronic devices can provide users with an entry point to switch Bluetooth headset features through feature switching controls, making it easier for users to operate; Bluetooth headsets can switch between multiple features, providing users with a richer listening experience.

[0033] In one possible implementation, after receiving the trigger operation for the first control, the method further includes: sending a query request to the OTA server, the query request instructing the OTA server to query whether the second feature version package and the third feature version package are included; and receiving the query results returned by the OTA server.

[0034] This process can correspond to Figure 13The relevant descriptions in steps S1314-S1305 of the illustrated embodiment. During feature switching, the electronic device can first query the OTA server to see if it includes an available compatible version package and a second feature version package; if the OTA server includes both, subsequent updates are performed; if the OTA server does not include either, subsequent updates are not performed. This improves update efficiency and reduces unnecessary resource consumption.

[0035] In one possible implementation, the method further includes: displaying a fourth interface if the query results indicate that the OTA server includes a second feature version package and a third feature version package; the fourth interface includes a first prompt message, which prompts the user that the Bluetooth headset is switching from the first feature to the second feature.

[0036] The fourth interface can be Figure 6 The interface shown in b, or Figure 7 The interface shown in b is an example. The first prompt message could be, for example, prompt message 601. In this way, the electronic device can inform the user that a feature switch is in progress and that they need to wait a moment.

[0037] In one possible implementation, the method further includes: displaying a fifth interface if the query results indicate that the OTA server does not contain a second feature version package or a third feature version package; the fifth interface includes a second prompt message, which is used to inform the user that the feature switching failed and that the second feature version package does not exist in the OTA server.

[0038] The fifth interface can correspond to Figure 12 The interface shown; the second prompt message could be, for example, prompt message 1201. In this way, the electronic device can inform the user that the feature cannot be switched at present through the second prompt message.

[0039] Secondly, this application proposes a feature switching method applied to a server. The server maintains multiple first feature version packages, second feature version packages, and / or third feature version packages for a second device. The first feature version package supports the second device in running a first feature, the second feature version package supports the second device in running a second feature, and the third feature version package supports the second device in running a third feature. The third feature is a feature that supports the second device in running basic functions. Both the first and second features are extended functions based on the third feature, and the first and second features are different. The method includes: after receiving a download request from the first device, sending the second feature version package and the third feature version package to the first device. The first device manages the second device. The download request is issued by the first device after establishing communication with the second device, based on a trigger operation on a first control. The trigger operation on the first control is used to instruct the second device to switch from the first feature to the second feature.

[0040] The server can be used to publish various types of version packages, such as an OTA server. The second device can be a resource-constrained device, and the first device can be a device used to manage resource-constrained devices. The first feature can be a feature that the resource-constrained device can support, such as the LEA feature. The second feature can be a feature that the resource-constrained device can support other than the first feature, such as the LDAC feature. The third feature can be a basic functional feature supported by the resource-constrained device; for example, the third feature can be the feature of the basic audio playback function corresponding to the compatible version package in this embodiment.

[0041] Download requests can be used to instruct the OTA server to return the corresponding version package. For example, in this embodiment of the application, when a second device is configured with a first feature and needs to switch from the first feature to the second feature, a download request can be used to instruct the OTA server to return a compatible version package and a version package of the second feature.

[0042] In this way, the server can provide the first device with various version packages for upgrading the second device, such as second feature version packages and compatibility version packages, so as to switch the second device from the first feature to the second feature through version upgrades and enrich the functionality of the second device.

[0043] In one possible implementation, the server includes an OTA server; the first device includes an electronic device; the second device includes a Bluetooth headset; the first feature and the second feature are different audio encoding methods; the first feature includes Bluetooth Low Energy (LEA) feature or Low Latency Audio Codec (LDAC) feature; the second feature includes LADC feature or LEA feature; the third feature is a feature that supports the Bluetooth headset to operate basic functions, which include at least one of the following: basic Bluetooth connection function, basic audio decoding function, and basic audio playback function.

[0044] In this embodiment, the resource-constrained device can be a Bluetooth headset, and the device for managing the Bluetooth headset can be an electronic device. The first and second characteristics can be characteristics supported by the Bluetooth headset, such as audio encoding methods, where the first characteristic is LEA and the second characteristic is LDAC; or the first characteristic is LDAC and the second characteristic is LEA. The third characteristic can be a characteristic of the basic audio function corresponding to the compatible version package in this embodiment.

[0045] In this way, the OTA server can provide Bluetooth headsets with various types of version packages, such as first feature version packages, second feature version packages, and compatibility version packages. Subsequent electronic devices can control the Bluetooth headset to switch between two or more features through version upgrades, enabling the same Bluetooth headset to support more features, enriching the functionality of the Bluetooth headset and improving the user experience.

[0046] In one possible implementation, after receiving a download request from a first device, a second feature version package and a third feature version package are sent to the first device; this includes: after receiving a first download request from the first device, sending a third feature version package to the first device; the first download request includes an identifier of the third feature version package and a first version number of the first feature version package; the identifier of the third feature version package is used to indicate the download of the third feature version package; the version number of the third feature version package is greater than the first version number; the first version number is less than or equal to the actual version number of the first feature version package in the second device; after receiving a second download request from the first device, sending a second feature version package to the first device; the second download request includes an identifier of the second feature version package and a version number of the third feature version package; the identifier of the second feature version package is used to indicate the download of the second feature version package; the version number of the second feature version package is greater than the version number of the third feature version package.

[0047] This process can correspond to Figure 13 The relevant descriptions in steps S1308-S1312.

[0048] In this way, the OTA server can return a compatible version package and a second feature version package to the electronic device in sequence, so that the electronic device can smoothly switch the Bluetooth headset from the first feature to the second feature.

[0049] In one possible implementation, the first feature version package is compatible with the third feature version package, and the second feature version package is compatible with the third feature version package; the first version number includes the minimum version number of the first feature version package; the version number of the second feature version package includes the maximum version number of the second feature version package; and the version number of the third feature version package includes the maximum version number of the third feature version package.

[0050] In this way, the first feature version package is compatible with the compatible version package, and the second feature version package is compatible with the compatible version package, which can reduce incompatibility scenarios during the version upgrade process and improve the success rate of the version upgrade. In addition, by controlling the version number before the upgrade to be less than the version number after the upgrade, the success rate of the version upgrade can also be improved. This, in turn, improves the success rate of the Bluetooth headset switching from the first feature to the second feature.

[0051] In one possible implementation, before sending the third feature version package to the first device, the method further includes: receiving a query instruction sent by the first device; responding to the query instruction, querying and returning a query result to the first device; the query result is used to indicate whether the OTA includes the second feature version package and the third feature version package.

[0052] This process can correspond to Figure 13 The relevant descriptions in steps S1304 and S1305 are provided. In this way, querying the version package to be updated in advance can improve update efficiency and reduce unnecessary resource consumption.

[0053] Thirdly, embodiments of this application provide a feature switching method applied to a second device. The method includes: after establishing communication with a first device, receiving a second feature version package and a third feature version package sent by the first device; wherein the second device is configured with a first feature version package, which supports the second device in running a first feature, the second feature version package is used to support the second device in running a second feature, and the third feature version package is used to support the second device in running a third feature; the third feature is a feature that supports the second device in running basic functions; the first feature and the second feature are both features that are extended functions based on the third feature, and the first feature and the second feature are different; upgrading from the first feature version package to the third feature version package; and upgrading from the third feature version package to the second feature version package.

[0054] The first device can be a device used to manage resource-constrained devices, and the second device can be a resource-constrained device.

[0055] The first characteristic can be a characteristic that a resource-constrained device can support, such as the LEA characteristic; the second characteristic can be a characteristic that a resource-constrained device can support other than the first characteristic, such as the LDAC characteristic; the third characteristic can be a basic functional characteristic supported by the resource-constrained device, for example, the third characteristic can be the basic audio playback function characteristic corresponding to the compatible version package in the embodiments of this application.

[0056] In this embodiment, the third feature is a basic functional feature, while the first and second features are advanced features supported by the basic features. For example, the first and second features are the LEA feature and the LDAC feature, respectively. During the switching process, the second device can first switch from one advanced feature to a basic functional feature, and then switch from a basic functional feature to another advanced feature. Using a version package of the basic features for transition during the upgrade process can effectively reduce scenarios where the first and second features are incompatible.

[0057] In this way, when using a resource-constrained device, the device switches between two or more features, enabling the same resource-constrained device to support more features, enriching the functionality of the resource-constrained device and improving the user experience.

[0058] In one possible implementation, the first device includes an electronic device, the second device includes a Bluetooth headset, and the first and second features are different audio encoding methods; the first feature includes Bluetooth Low Energy (LEA) features or Low Latency Audio Codec (LDAC) features; the second feature includes LADC features or LEA features; the third feature is a feature that supports the Bluetooth headset to operate basic functions, which include at least one of the following: basic Bluetooth connectivity functions, basic audio decoding functions, and basic audio playback functions.

[0059] In this embodiment, the resource-constrained device can be a Bluetooth headset, and the device for managing the Bluetooth headset can be an electronic device. The first and second characteristics can be features supported by the Bluetooth headset, such as audio encoding methods; for example, the first characteristic might be LEA and the second characteristic might be LDAC; or the first characteristic might be LDAC and the second characteristic might be LEA. The third characteristic can be a feature of the basic audio function corresponding to the compatible version package in this embodiment. Thus, when using the Bluetooth headset, it can switch between two or more characteristics, allowing the same Bluetooth headset to support more features, enriching the functionality of the Bluetooth headset and improving the user experience.

[0060] In one possible implementation, before receiving the second and third feature version packets from the first device, the method further includes: sending a first version number of the first feature version packet to the electronic device, wherein the first version number is less than or equal to the actual version number of the first feature version packet in the Bluetooth headset; wherein the first version number is used to obtain the third feature version packet, and the version number of the third feature version packet is greater than the first version number. In this way, during version upgrades, virtual downgrading is used to control the upgrade path of the Bluetooth headset to upgrade from a lower version to a higher version, thereby reducing scenarios where version upgrades fail due to limited upgrade paths.

[0061] Fourthly, embodiments of this application provide a feature switching method applied to a system, the system including an electronic device, a Bluetooth headset, and an OTA server, the electronic device being used to manage the Bluetooth headset; the method includes: the electronic device establishing communication with the Bluetooth headset; the electronic device displaying a first interface (e.g., a device management interface); the first interface being an application interface for managing the Bluetooth headset (e.g., a device management application); the first interface including a first control (e.g., a feature switching control); wherein the first control is used to instruct the Bluetooth headset to perform feature switching, the first control representing that the Bluetooth headset is configured with a first feature; the first feature includes an LEA feature or an LDAC feature; the electronic device receiving a trigger operation (e.g., a feature switching operation) on the first control; The trigger operation on the first control is used to indicate a switch from the first feature to the second feature; the second feature includes the LADC feature or the LEA feature; the electronic device sends a query request to the OTA server; in response to the query request, the OTA server queries whether a second feature version package and a third feature version package are included, and returns the query result to the electronic device; the second feature version package is used to support the Bluetooth headset to run the second feature, and the third feature version package is used to support the Bluetooth headset to run the third feature; the third feature is a feature that supports the Bluetooth headset to run basic functions, which include at least one of the following: basic Bluetooth connection function, basic audio decoding function, and basic audio playback function; the second feature version package and the third feature version package are compatible; the query result indicates the OTA server to switch to the second feature. When server A includes both a second feature version package and a third feature version package, the electronic device sends a feature switching command to the Bluetooth headset. This command indicates a switch from the first feature to the second feature. In response to the feature switching command, the Bluetooth headset sends the first version number of the first feature version package to the electronic device. The first feature version package supports the Bluetooth headset operating the first feature. The first version number is less than or equal to the actual version number of the first feature version package in the Bluetooth headset. The first feature version package and the third feature version package are compatible. The electronic device sends the first version number and the identifier of the third feature version package to the OTA server. The identifier of the third feature version package indicates the download of the third feature version package. The electronic device receives the third feature returned by the OTA server. The electronic device receives a first feature version package and sends a third feature version package to the Bluetooth headset; the version number of the third feature version package is greater than the version number of the first feature version package; the Bluetooth headset upgrades from the first feature version package to the third feature version package; the electronic device sends the version number of the third feature version package and the identifier of the second feature version package to the OTA server; the identifier of the second feature version package is used to indicate the download of the second feature version package; the electronic device receives the second feature version package returned by the OTA server and sends the second feature version package to the Bluetooth headset; the version number of the second feature version package is greater than the version number of the third feature version package; the Bluetooth headset upgrades from the third feature version package to the second feature version package; the Bluetooth headset reconnects to the application on the electronic device used to manage the Bluetooth headset; the electronic device displays a second interface;The second interface includes the first control, and the first control indicates that the Bluetooth headset is equipped with a second feature.

[0062] This process can correspond to Figure 13 The illustrated embodiment demonstrates how, when using a Bluetooth headset, users can switch between two or more features, allowing the same Bluetooth headset to support more features, thus enriching its functionality and enhancing the user experience.

[0063] Fifthly, embodiments of this application provide an electronic device including a processor and a memory, the memory being used to store computer execution instructions, and the processor being used to execute the computer execution instructions stored in the memory to perform the methods described in the first aspect or any possible implementation of the first aspect.

[0064] In a sixth aspect, embodiments of this application provide a server, including a processor and a memory, wherein the memory is used to store computer execution instructions, and the processor is used to run the computer execution instructions stored in the memory to perform the methods described in the second aspect or any possible implementation thereof.

[0065] In a seventh aspect, embodiments of this application provide a Bluetooth headset, including a processor and a memory, wherein the memory is used to store computer execution instructions, and the processor is used to execute the computer execution instructions stored in the memory to perform the methods described in the third aspect or any possible implementation of the third aspect.

[0066] Eighthly, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions that, when executed on a computer, cause the computer to perform the methods described in the first, second, or third aspects, or to perform the methods described in any possible implementation of the first, second, or third aspects.

[0067] Ninthly, embodiments of this application provide a computer program product including a computer program, which, when the computer program is run, causes the computer program to be executed by a processor to implement the methods described in the first, second, or third aspects, or causes the computer program to be executed by a processor to implement the methods described in any possible implementation of the first, second, or third aspects.

[0068] Tenthly, this application provides a chip or chip system including at least one processor and a communication interface. The communication interface and the at least one processor are interconnected via a circuit. The at least one processor is used to run computer programs or instructions to perform the methods described in the first, second, or third aspects, or to perform the methods described in any possible implementation of the first, second, or third aspects. The communication interface in the chip can be an input / output interface, a pin, or a circuit, etc.

[0069] In one possible implementation, the chip or chip system described above in this application further includes at least one memory storing instructions. The memory can be an internal storage unit of the chip, such as a register or cache, or it can be a storage unit of the chip itself (e.g., read-only memory, random access memory, etc.).

[0070] It should be understood that the fourth to tenth aspects of this application correspond to the technical solutions of the first to third aspects of this application, and the beneficial effects obtained by each aspect and the corresponding feasible implementation are similar, and will not be repeated here. Attached Figure Description

[0071] Figure 1 A schematic diagram illustrating a possible scenario where electronic devices utilize the dual characteristics of Bluetooth headsets;

[0072] Figure 2 A schematic diagram of ROM storage space for Bluetooth headsets supporting different single and dual features in possible implementations;

[0073] Figure 3 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application;

[0074] Figure 4 This is a schematic diagram of the structure of a Bluetooth headset provided in an embodiment of this application;

[0075] Figure 5 A schematic diagram of an interface for a feature switching method provided in an embodiment of this application;

[0076] Figure 6 A schematic diagram of an interface for a feature switching method provided in an embodiment of this application;

[0077] Figure 7 A schematic diagram of an interface for another feature switching method provided in an embodiment of this application;

[0078] Figure 8 This application provides schematic diagrams illustrating various types of version packages in its embodiments.

[0079] Figure 9This is a schematic diagram illustrating the compatibility of switching between LEA and LDAC features provided in the embodiments of this application.

[0080] Figure 10 This is a schematic diagram illustrating the compatibility of switching between LEA and LDAC features after adding a compatible version package, as provided in this embodiment of the application.

[0081] Figure 11 A flowchart illustrating a feature switching method provided in an embodiment of this application;

[0082] Figure 12 A schematic diagram of the interface when feature switching fails, provided in an embodiment of this application;

[0083] Figure 13 A flowchart illustrating a feature switching method provided in an embodiment of this application;

[0084] Figure 14 This is a schematic diagram of a feature switching device provided in an embodiment of this application. Detailed Implementation

[0085] To facilitate a clear description of the technical solutions in the embodiments of this application, some terms and technologies involved in the embodiments of this application will be briefly introduced below:

[0086] 1. Resource-constrained devices: These are electronic devices with limitations in computing power, storage space, battery life, network bandwidth, etc. These devices typically operate under limited hardware resources and energy consumption. Examples of resource-constrained devices include: IoT devices (such as smart sensors and smart home devices), embedded systems (such as medical devices and industrial control systems), mobile devices (such as smartphones and tablets), and Bluetooth devices (such as wireless headphones and fitness trackers).

[0087] 2. LDAC Features: LDAC is an audio codec technology designed for high-resolution audio transmission via Bluetooth. LDAC supports higher bitrates, such as 990kbps, providing sound quality close to wired audio connections. LDAC features are suitable for wireless audio devices with high sound quality requirements, such as high-end wireless headphones and speaker systems. By transmitting more audio data at high bandwidth, LDAC effectively enhances the wireless audio experience.

[0088] 3. LEA Feature: Low-power audio is part of Bluetooth technology and is mainly used to improve the efficiency of audio transmission while maintaining low power consumption, enabling electronic devices running LEA features to have a long battery life.

[0089] 4. Other terms

[0090] In the embodiments of this application, terms such as "first" and "second" are used to distinguish identical or similar items with the same function and basis. For example, "first chip" and "second chip" are used only to distinguish different chips and do not limit their order. Those skilled in the art will understand that terms such as "first" and "second" do not limit the quantity or execution order, and that "first" and "second" do not necessarily imply that they are different.

[0091] It should be noted that, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0092] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, a--c, bc, or abc, where a, b, and c can be single or multiple.

[0093] 5. Electronic equipment

[0094] The electronic devices in this application embodiment may include handheld devices, vehicle-mounted devices, etc., capable of controlling resource-constrained devices. For example, some electronic devices include: mobile phones, tablets, PDAs, laptops, mobile internet devices (MIDs), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, terminal devices in 5G networks, or future evolution of public land mobile communication networks. Terminal devices in a mobile network (PLMN), etc., are not limited to this in the embodiments of this application.

[0095] Figure 1 The diagram illustrates a possible implementation scenario where an electronic device utilizes the dual features of a Bluetooth headset. Figure 1 As shown:

[0096] In a possible implementation, taking a resource-constrained device like a Bluetooth headset as an example, the features could be audio features, such as LDAC and LEA features. A single Bluetooth headset can support one audio feature. Bluetooth headset A can support LDAC features, while Bluetooth headset B can support LEA features.

[0097] After Bluetooth headset A establishes communication with the electronic device, the user can use Bluetooth headset A to play high-quality audio, but Bluetooth headset A has a short standby time. After Bluetooth headset B establishes communication with the electronic device, the user can also use Bluetooth headset B to play audio for extended periods, but the audio quality is generally lower. In other words, when the user wants to listen to high-quality audio, Bluetooth headset A can be used; when the user wants to listen to audio for a longer period, Bluetooth headset B can be used. Users need to manually switch between Bluetooth headset A and Bluetooth headset B to meet their different audio needs, which is rather cumbersome.

[0098] To address the aforementioned issues, LDAC and LEA features can be integrated into a single Bluetooth headset. However, some problems still exist even after integrating the two features, such as... Figure 2 As shown:

[0099] Resource-constrained devices may include read-only memory (ROM), which can be a type of memory used to store firmware and immutable data. The ROM of a resource-constrained device has a storage limit, which can be the maximum storage capacity of the ROM.

[0100] The ROM of a Bluetooth headset can be used to store firmware resources, configuration data, and audio processing algorithms, etc. The amount of data stored in the Bluetooth headset is less than the maximum storage capacity of the ROM. For example, in... Figure 2 In the diagram, the rectangle corresponding to Bluetooth headset A represents the amount of data stored in its ROM, including basic audio function code and the LDAC algorithm. Similarly, the rectangle corresponding to Bluetooth headset B represents the amount of data stored in its ROM, including basic audio function code and the LEA algorithm. Since LDAC's high-resolution audio transmission requires more ROM space to store related firmware and configuration data, the amount of data stored in the ROM of Bluetooth headset A can be greater than the amount of data stored in the ROM of Bluetooth headset B.

[0101] Bluetooth headset C can be a Bluetooth headset that integrates LEA features and LDAC functionality. The rectangle corresponding to Bluetooth headset C represents the amount of data stored in the ROM of Bluetooth headset C, such as the code for basic audio functions, LDAC algorithm, and LEA algorithm.

[0102] Understandably, during the configuration of Bluetooth headsets, in order to improve the utilization of ROM storage space and reduce hardware costs, the amount of data stored in the Bluetooth headset's ROM is often controlled to be slightly less than the maximum storage capacity of the ROM. For example, in Figure 2In the example, the data volume in the ROM of both Bluetooth headset A and Bluetooth headset B is slightly less than the maximum storage capacity of the ROM. This means that, when using Bluetooth headsets with equivalent configurations to simultaneously implement LEA and LDAC features, Bluetooth headset C requires more ROM storage space than its maximum ROM capacity, resulting in insufficient hardware ROM in Bluetooth headset C.

[0103] Furthermore, integrating both features into a single Bluetooth headset may present several challenges. For instance, after integration, the headset may simultaneously run both the LEA and LDAC algorithms during use. Since the LDAC feature has high data transmission requirements, the headset's power consumption will significantly increase. High power consumption can also reduce battery life. Additionally, if the hardware ROM in the Bluetooth headset is insufficient, the performance of hardware such as the ROM needs to be improved, thereby increasing costs.

[0104] In view of this, embodiments of this application provide a feature switching method that enables switching between multiple features on the same resource-constrained device. For example, the resource-constrained device can be a Bluetooth headset, and the multiple features can be LEA and LDAC features. Different types of version packages can be deployed in the Bluetooth headset, such as LEA version packages, LDAC version packages, and compatible version packages. The compatible version package can be a version package that does not contain LEA or LDAC features. When the LDAC version package is deployed, the Bluetooth headset can support high-quality audio playback; when the LEA version package is deployed, the Bluetooth headset can support long battery life. The compatibility between the LEA and LDAC versions can be maintained through the compatible version package. Thus, without increasing hardware costs, the effect of switching between multiple features can be achieved on a resource-constrained device through software upgrades, providing users with richer feature functions and improving the user experience.

[0105] To better understand the embodiments of this application, the structures of the electronic device and Bluetooth headset of this application are described below:

[0106] Figure 3A schematic diagram of the electronic device is shown. The electronic device may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, antenna 1, antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a subscriber identification module (SIM) card interface 195, and an embedded secure element (eSE) 196, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0107] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device. In other embodiments of this application, the electronic device may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0108] Processor 110 may include one or more processing units, such as an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors. In this embodiment, processor 110 can be used to execute processes related to controlling Bluetooth headset feature upgrades, such as controlling the Bluetooth headset to switch from a first feature to a second feature, or from a second feature back to a first feature.

[0109] The wireless communication function of electronic devices can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

[0110] The mobile communication module 150 can provide wireless communication solutions, including 2G / 3G / 4G / 5G, for use in electronic devices. In this embodiment, the electronic device can establish a communication connection with an OTA server via the mobile communication module 150 to download version packages related to Bluetooth headset upgrades from the OTA server.

[0111] The wireless communication module 160 can provide solutions for wireless communication applications in electronic devices, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies.

[0112] In this embodiment, the electronic device can establish a communication connection with an OTA server via the wireless communication module 160 to download version packages related to Bluetooth headset upgrades from the OTA server. The wireless communication module 160, for example, supports WLAN technology. The electronic device can also establish a communication connection with a Bluetooth headset via the wireless communication module 160 to send version packages related to Bluetooth headset upgrades to the Bluetooth headset. The wireless communication module 160, for example, supports BT technology.

[0113] Electronic devices achieve display functions through GPUs, displays (194), and application processors.

[0114] The display screen 194 is used to display images, videos, etc. In this embodiment, the display screen 194 can be used to display, for example... Figures 5 to 7 The interface shown provides users with a visual interface for controlling the switching of Bluetooth headset features.

[0115] Electronic devices can implement audio functions such as music playback and recording through audio modules 170, speakers 170A, receivers 170B, microphones 170C, headphone jacks 170D, and application processors.

[0116] The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 170 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 170 may be located in the processor 110, or some functional modules of the audio module 170 may be located in the processor 110. In this embodiment, the audio module 170 can be used to transmit audio data to a Bluetooth headset. Subsequently, if the Bluetooth headset is configured with LEA characteristics, the Bluetooth headset can play audio data with LEA characteristics; if the Bluetooth headset is configured with LDAC characteristics, the Bluetooth headset can play audio data with LDAC characteristics.

[0117] Touch sensor 180K, also known as a "touch device," can be disposed on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also known as a "touchscreen." In this embodiment, touch sensor 180K can sense and recognize trigger operations on feature switching controls, thereby instructing the electronic device to control the Bluetooth headset to switch features.

[0118] The structure of the Bluetooth headset according to an embodiment of this application will be described below. Figure 4 A schematic diagram of a Bluetooth headset is shown. The Bluetooth headset may include at least one processor 201, at least one memory 202, a wireless communication module 203, an audio module 204, a power module 205, and an input / output interface 206, etc. The processor may include one or more interfaces for connecting to other components of the Bluetooth headset. The Bluetooth headset is stored in a charging case.

[0119] The memory 202 can be used to store program code, such as program code for switching Bluetooth headset features.

[0120] The processor 201 can be used to execute the above application code and call relevant modules to implement the Bluetooth headset multi-feature switching function in the embodiments of this application.

[0121] The wireless communication module 203 can be used to support data exchange between Bluetooth headsets and other electronic devices or headset boxes via wireless communication technology, such as BT, WLAN (like Wi-Fi), Zigbee, FM, NFC, IR, or general 2.4G / 5G wireless communication technology.

[0122] In some embodiments, the wireless communication module 203 can be a Bluetooth chip. The Bluetooth headset can use this Bluetooth chip to pair with and establish a wireless connection with the Bluetooth chips of other electronic devices, enabling wireless communication and service processing between the Bluetooth headset and other electronic devices. In this embodiment, the Bluetooth headset can use the wireless communication module 203 to interact with the wireless communication module 160 of the electronic device to obtain a version package for feature switching.

[0123] The audio module 204 can be used to manage audio data and enable the input and output of audio streams for the Bluetooth headset. For example, the audio module 204 can obtain audio streams from or transmit audio streams to the wireless communication module 203, enabling functions such as making and receiving calls, playing music, activating / deactivating the voice assistant of the electronic device connected to the headset, and receiving / sending user voice data through the Bluetooth headset. The audio module 204 may include a speaker (or earpiece, receiver) assembly for outputting audio streams, a microphone (or microphone), and microphone recording circuitry that works with the microphone.

[0124] In this embodiment, the audio module 204 can be used to process audio data sent by the electronic device. For example, if the Bluetooth headset is equipped with an LDAC version package, the audio module 204 can perform LDAC processing on the audio data to obtain and output high-quality audio. If the Bluetooth headset is equipped with an LEA version package, the audio module 204 can perform LEA processing on the audio data to reduce power consumption and extend the standby time of the Bluetooth headset.

[0125] Multiple input / output interfaces 206 can be used to provide a wired connection for charging or communication between the Bluetooth headset and the earphone case. In this embodiment, to improve the stability and security of the Bluetooth headset during feature switching, the Bluetooth headset can be placed in the earphone case when different feature versions are installed.

[0126] Additionally, the Bluetooth headset may include a sensor 207. For example, the sensor 207 may be a proximity sensor, a near light sensor, a bone conduction sensor, and / or a touch sensor, etc.

[0127] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on Bluetooth headsets. They may have more... Figure 2The Bluetooth headset may show more or fewer components, or it may combine two or more components, or it may have different component configurations. For example, the outer surface of the Bluetooth headset may also include components such as a button 208, indicator lights (which can indicate battery level, incoming / outgoing calls, pairing mode, etc.), a display screen (which can display relevant information to the user), and a dustproof mesh (which can be used with the earpiece). The button 208 may be a physical button or a touch button (used in conjunction with a touch sensor), and is used to trigger operations such as power on, power off, pause, play, record, start pairing, and reset.

[0128] Let's combine the following... Figures 5-7 The application scenarios of the control method provided in the embodiments of this application will be described.

[0129] Bluetooth headsets can establish a communication connection with electronic devices to enable data interaction between the headset and the electronic device. For example, a Bluetooth headset can establish a Bluetooth channel with an electronic device, and then the two can establish an asynchronous connectionless (ACL) link to transmit audio data, which can be music. Alternatively, they can establish a synchronous connection oriented (SCO) link to transmit audio data, which can be voice calls.

[0130] After establishing communication, the Bluetooth headset can play audio from the electronic device. For example, if the Bluetooth headset is currently configured with the LEA version package, upon receiving audio data from the electronic device, it can process the audio data into low-power audio data based on the LEA algorithm, thereby extending the headset's usage time. As another example, if the Bluetooth headset is currently configured with the LDAC version package, upon receiving audio data from the electronic device, it can process the audio data into high-quality audio data based on the LDAC algorithm to enhance the user's listening experience.

[0131] Taking the switching of Bluetooth headphones from LEA features to LDAC features as an example, Figure 5 In scenario 'a', the Bluetooth headphones can play audio with LEA characteristics. In some scenarios, users may want to listen to high-quality audio. In this case, users can switch the Bluetooth headphones to LDAC characteristics.

[0132] It should be noted that in some embodiments, the electronic device can control the Bluetooth headset to switch characteristics even when the Bluetooth headset is not playing audio. In other embodiments, when the Bluetooth headset is playing audio, the electronic device can first pause the audio playback and then control the Bluetooth headset to switch characteristics. In still other embodiments, the electronic device can also control the Bluetooth headset to switch characteristics even when the Bluetooth headset is playing audio. This application does not impose any limitations on these embodiments.

[0133] In this embodiment, the entry point for switching features can be set in a device management application, such as a smart space application. When a trigger operation is received on the desktop targeting the device management application icon, the electronic device can display, as shown below. Figure 5 The interface shown in b; Figure 5 The interface shown in b can include management cards for one or more connected devices. For example, the interface displays Bluetooth headset card 501.

[0134] The Bluetooth headset card 501 can be used to manage and configure the Bluetooth headset. The Bluetooth headset card 501 may include the Bluetooth headset's identifier (e.g., device name, device model, etc.), battery information for both the Bluetooth headset and its charging case, and an icon of the Bluetooth headset.

[0135] The Bluetooth earphones can be labeled as such as "Bluetooth Earphones D"; the battery information for the Bluetooth earphones and charging case can be such as "Left Bluetooth Earphone 90% battery", "Right Bluetooth Earphone 90% battery", and "Charging Case 76% battery".

[0136] exist Figure 5 In the interface shown in b, when a trigger operation is received for the Bluetooth headset card 501, the electronic device can display the device management interface of the Bluetooth headset D, such as... Figure 5 The interface shown in c is shown in the image. Figure 5 In the interface shown in c, the electronic device can display the prompt message 502 and controls for one or more settings.

[0137] For example, the prompt message 502 can be used to indicate the connection status between the Bluetooth headset and the electronic device, as well as the battery information of each component of the Bluetooth headset; for example, the prompt message 502 can be "Connected; left Bluetooth headset battery 90%; right Bluetooth headset battery 90%; earphone case battery 75%".

[0138] The device includes controls for one or more settings, such as an equalizer (EQ) sound effect control, a feature switching control 503, a shortcut control, a firmware update control 504, a headphone finder control, and a user guide control. The EQ sound effect control can be used to switch between sound effects such as original, bass, treble, and vocals. The feature switching control 503 can be used to switch audio features in the Bluetooth headset, such as LDAC and LEA features. For example, the feature switching control 503 can be used to instruct the Bluetooth headset to switch from LEA to LDAC features, or vice versa. The shortcut control can be used to set up gesture operations for managing audio, such as gestures for answering / hanging up calls, play / pause, and skipping tracks. The firmware update control 504 can be used to upgrade the Bluetooth headset version, such as upgrading a lower LEA version package to a higher one, or upgrading a lower LDAC version package to a higher one. The headphone finder control can be used to quickly locate the headset by ringing. The user guide control can help users quickly understand how to set up the Bluetooth headset.

[0139] This application embodiment illustrates the feature switching process using a feature switching control included in the device management interface of a Bluetooth headset as an example. In practical applications, the feature switching control can also be set in, for example, the firmware update function or other functions; for example, in Figure 5 As shown in Figure c, when a trigger operation is received for the firmware update control 504, the electronic device can display the current version and multiple updatable versions; the current version may be, for example, the LEA version, and the updatable versions may be, for example, the latest LDAC version and the latest LEA version, etc. This application embodiment does not limit the location of the feature switching control.

[0140] See also Figure 5 As shown in the interface c, after receiving a trigger operation on the feature switching control 503, the electronic device can enter the following state: Figure 5 The feature switching interface is shown as d in the figure. Figure 5 The interface shown as d may include a feature switching pop-up window 505, which can be used to switch features. The feature switching pop-up window 505 may include a close control 508 and selection boxes for multiple features. These selection boxes may include, for example, a LEA selection box 506 and an LDAC selection box 507. The selection boxes may have selected and unselected states. For example, if the LEA selection box 506 is selected and the LDAC selection box 507 is unselected, it indicates that the Bluetooth headset is currently using the LEA feature.

[0141] In some embodiments, the feature switching pop-up window 505 may also include prompts for LEA and LDAC. The LEA prompts can help users understand the LEA feature, and the LDAC prompts can help users understand the LDAC feature.

[0142] It should be noted that this application embodiment uses a pop-up window as an example to illustrate the process of displaying multiple features. In practical applications, electronic devices can also enter a full-screen interface for feature switching through the feature switching control 503, where users can perform feature switching operations. This application embodiment does not impose any limitations on this.

[0143] The process of switching the features of an electronic device to Bluetooth headphones can be as follows: Figure 6 As shown:

[0144] After entering the feature switching interface, the electronic device can display, as follows: Figure 6 The interface shown in Figure 'a'. Figure 6 The interface shown in Figure 'a' may include a feature switching pop-up window 505, in which the LEA selection box is selected and the LDAC selection box is unselected. When a trigger operation is received for the LDAC selection box 507, the electronic device can enter... Figure 6 The interface shown in b is shown in the image.

[0145] exist Figure 6 In the interface shown in b, the electronic device can display a prompt message 601, which can be used to prompt the user that a feature is currently being switched.

[0146] Optionally, in some embodiments, the electronic device controls the Bluetooth headset to update different feature versions of the package to configure different features for the Bluetooth headset. To improve the stability and security of the version update process, when a trigger operation is received for the LDAC selection box 507 in the unselected state, the electronic device can prompt the user to put the Bluetooth headset back into the earphone case. After detecting that the Bluetooth headset is placed in the earphone case, the electronic device can display prompt message 601.

[0147] After the feature switching is complete, the electronic device can display as follows: Figure 6 The interface shown in c is shown in the image. Figure 6 The interface shown in c may include a feature switching pop-up window 505; in the feature switching pop-up window 505, the LEA selection box 506 is unselected and the LDAC selection box 507 is selected, indicating that the Bluetooth headset is currently using the LDAC feature.

[0148] exist Figure 6In the interface shown in c, when a trigger operation is received for the close control 508, or a trigger operation is received in the blank area outside the pop-up window, the electronic device can close the feature switching pop-up window 505 and display as shown in the image. Figure 6 The interface shown in d is as follows. Figure 6 In the interface shown as d, the feature switching control 503 indicates that the Bluetooth headset's current feature is LDAC. After receiving audio data from the electronic device, the Bluetooth headset can process the audio data into LDAC-enabled audio data, improving the audio quality.

[0149] It should be noted that the above embodiments use the example of an electronic device controlling a Bluetooth headset to switch from LEA to LDAC characteristics to illustrate the characteristic switching process. In practical applications, the electronic device can also control a Bluetooth headset to switch from LDAC to LEA characteristics, and this switching process is similar. Figure 5 , Figure 6 The scenarios shown are similar, and will not be described again in the embodiments of this application.

[0150] It should be noted that in this embodiment, the Bluetooth headset may support dual-feature or multi-feature switching. When the Bluetooth headset supports multi-feature switching, the electronic device may display more feature controls in, for example, the feature switching pop-up window 505, and the electronic device may also control the Bluetooth headset to switch to audio features other than LEA and LDAC features. This embodiment does not impose any limitations on this.

[0151] In this way, electronic devices can control Bluetooth headsets to switch between dual or multiple characteristics, so that the same Bluetooth headset can play audio with multiple characteristics, providing users with a richer listening experience.

[0152] Figure 7 This illustration shows another feature switching interface diagram provided in an embodiment of this application; as shown Figure 7 As shown:

[0153] Taking the LEA feature currently configured in Bluetooth headsets as an example, after receiving a trigger operation for Bluetooth headset card 501, the electronic device can display as follows: Figure 7 The interface shown in Figure 'a' is... Figure 7 The interface shown in Figure 'a' includes a feature switching control 701. The feature switching control 701 can represent the current feature as the LEA feature, and the feature switching control 701 can be used to indicate switching from the current feature to another feature.

[0154] Upon receiving a trigger operation on the feature switching control 701, the electronic device may display as follows: Figure 7 The interface shown in b is in Figure 7 In the interface shown in b, the electronic device can display prompt message 601; Figure 7 The interface shown in b can be referenced. Figure 6 The relevant description of the interface shown in b is not repeated here.

[0155] After the switch is complete, the electronic device can display... Figure 7 The interface shown in c is... Figure 7 The interface shown in c includes a feature switching control 701; the feature switching control 701 can indicate that the current feature is LDAC feature. After receiving audio data from the electronic device, the Bluetooth headset can process the audio data into LDAC feature audio data to improve the audio quality of the Bluetooth headset.

[0156] It is understood that when a Bluetooth headset supports dual-feature switching, the electronic device can control the Bluetooth headset to switch between two features via a single control (e.g., feature switching control 701). For example, if the Bluetooth headset is configured with the LEA feature, in response to a trigger operation on the feature switching control 701, the electronic device controls the Bluetooth headset to switch to the LDAC feature. As another example, if the Bluetooth headset is configured with the LDAC feature, in response to a trigger operation on the feature switching control 701, the electronic device controls the Bluetooth headset to switch to the LEA feature. The embodiments of this application may also involve switching between other two features, and this is not limited.

[0157] In this way, electronic devices can control Bluetooth headphones to switch between dual characteristics, so that the same Bluetooth headphones can play audio with two different characteristics, providing users with a richer auditory experience.

[0158] It should be noted that in this embodiment, the Bluetooth headset can support dual-feature or multi-feature switching. The feature switching process can be achieved through an update package. The update package can be a software update package pushed to the electronic device by an over-the-air (OTA) server via a wireless communication network. In this embodiment, the update package can be a software update package for updating the Bluetooth headset.

[0159] Taking Bluetooth headsets supporting dual-feature switching as an example, when releasing a version package for the Bluetooth headset, the OTA server can release different types of version packages for different features. For example, the OTA server can mark the version package with a feature identifier (type), which can be used to indicate the features supported by the version package. For example, in this embodiment, the version package for the Bluetooth headset used to implement dual-feature switching may include: an LEA version package, an LDAC version package, and a compatible version package.

[0160] For example, the structures of the LEA version package, LDAC version package, and compatible version package can be as follows: Figure 8 As shown:

[0161] Versioning features may include LEA features, LDAC features, and compatibility (also known as ALL) features.

[0162] For example, an LEA version package can be a version package marked with an LEA identifier (e.g., type=LEA); the ROM package in the LEA version package can be used to support Bluetooth headsets to run LEA features.

[0163] The LDAC version package can be a version package marked with the LDAC identifier (e.g., type=LDAC); the ROM package in the LDAC version package can be used to support Bluetooth headsets to run LDAC features.

[0164] Compatible versions are those marked with the ALL identifier (e.g., type=ALL); the ROM package within the compatible version can be used to ensure the basic functions of the Bluetooth headset. Basic functions may include at least one of the following: basic Bluetooth connectivity, basic audio decoding, and basic audio playback.

[0165] In this embodiment, the compatible version package is compatible with the LEA version package; and the compatible version package is compatible with the LDAC version package. However, this embodiment does not require compatibility between the LDAC version package and the LEA version package.

[0166] In this embodiment, the electronic device can control the Bluetooth headset to update from the LDAC version package to the LEA version package; alternatively, it can control the Bluetooth headset to update from the LEA version package to the LDAC version package. During feature switching, a compatible version package can serve as a transition to reduce compatibility issues between different feature version packages.

[0167] The following is combined with Figure 9 and Figure 10 The reasons for introducing the compatible version package in the embodiments of this application are explained.

[0168] Figure 9 This is a compatibility diagram of the LDAC version package and the LEA version package in this embodiment of the application, without adding a compatible version package, as shown below. Figure 9 As shown:

[0169] Taking the LEA version package, which includes three versions: LEA1, LEA2, and LEA3, and the LDAC version package, which includes three versions: LDAC 1, LDAC 2, and LDAC 3, as examples: The version number of the LEA1 version package is lower than the version number of the LEA2 version package, and the version number of the LEA2 version package is lower than the version number of the LEA3 version package. Similarly, the version number of the LDAC 1 version package is lower than the version number of the LDAC 2 version package, and the version number of the LDAC 2 version package is lower than the version number of the LDAC 3 version package.

[0170] For example, taking the current release of the LEA3 version package by the OTA server as an example, when releasing the LEA3 version package, the OTA server must follow the rules of backward compatibility to ensure that the LEA3 version package is compatible with the LEA2 and LEA1 version packages. This ensures that the new version (LEA3 version package) can run normally in the existing system environment, and that the operating environment of the old versions (LEA1 and LEA2 version packages) can accept and correctly process the new version package. For example, when a Bluetooth headset is configured with the LEA1 or LEA2 version package, the electronic device can control the Bluetooth headset to update to the LEA3 version package.

[0171] Furthermore, the Bluetooth headset can achieve dual-feature switching functionality, allowing the electronic device to control the Bluetooth headset to update from the LEA version package to the LDAC version package, or vice versa. In this case, the OTA server needs to ensure compatibility between the new LEA3 version package and various LDAC version packages. For example, when the Bluetooth headset is configured with the LDAC 1 version package, the electronic device can control the Bluetooth headset to update to the LEA3 version package; or, when the Bluetooth headset is configured with the LDAC 2 version package, the electronic device can control the Bluetooth headset to update to the LEA3 version package; or, when the Bluetooth headset is configured with the LDAC 3 version package, the electronic device can control the Bluetooth headset to update to the LEA3 version package.

[0172] Therefore, when an OTA server releases a new version marked with a feature identifier, it needs to consider not only the compatibility between the new version and the old versions with the same features, but also the compatibility between the new version and different versions with different features.

[0173] Understandably, with version updates and upgrades, the compatibility relationship between LEA and LDAC version packages becomes increasingly complex. Achieving compatibility between various LEA and LDAC version packages on the OTA server is quite challenging. For example, when releasing a new version, the OTA server needs to conduct extensive compatibility testing to ensure that Bluetooth headsets do not experience configuration or compatibility issues during version switching. Furthermore, releasing a new version requires designing and implementing reliable systems and processes for firmware upgrades to ensure that Bluetooth headsets can smoothly switch between different versions. Finally, releasing a new version requires providing users with corresponding services to help them resolve problems encountered during each version upgrade.

[0174] The same problem exists when the LDAC version package is released on the OTA server, and will not be described again in this embodiment.

[0175] To simplify the complexity of compatibility issues during the release process described above, this application embodiment may introduce a compatible version package. Figure 10 This is a compatibility diagram of the LEA version package and the LDAC version package when a compatible version package is added, as shown in the embodiments of this application. Figure 10 As shown:

[0176] Taking the LEA version package, which includes three versions: LEA1, LEA2, and LEA3, and the LDAC version package, which includes three versions: LDAC 1, LDAC 2, and LDAC 3, as an example; the version number of the LEA1 version package is lower than the version number of the LEA2 version package, and the version number of the LEA2 version package is lower than the version number of the LEA3 version package; the version number of the LDAC 1 version package is lower than the version number of the LDAC 2 version package, and the version number of the LDAC 2 version package is lower than the version number of the LDAC 3 version package.

[0177] See Figure 10 Taking the release of the LEA3 version package by an OTA server as an example, when releasing the LEA3 version package, the OTA server must follow the rules of backward compatibility, ensuring compatibility between the LEA3 version package and the LEA2 and LEA1 version packages. This ensures that the new version (LEA3 version package) can run normally in the existing system environment, and that the operating environment of the older versions (LEA1 and LEA2 version packages) can accept and correctly process the new version package. For example, when the Bluetooth headset is version LEA1 or LEA2, the electronic device can control the Bluetooth headset to update to version LEA3.

[0178] Furthermore, the Bluetooth headset supports dual-feature switching, allowing the electronic device to control the Bluetooth headset's updates from the LEA version package to the LDAC version package, or vice versa. When switching from LEA to LDAC features, the OTA server needs to ensure compatibility between the newly released LEA3 version package and compatible version packages, but does not need to consider compatibility between the newly released LEA3 version package and various LDAC version packages.

[0179] Understandably, when releasing LDAC 1, LDAC 2, or LDAC 3 versions, the OTA server ensured compatibility between these versions and the compatible versions. Therefore, when releasing the LEA3 version, it is compatible with the compatible versions, and the compatible versions are compatible with all LDAC versions. This satisfies the feature switching requirements between the LEA3 version and various LDAC versions.

[0180] For example, if an OTA server releases an LEA3 version package, and the current Bluetooth headset is running LDAC 3, when switching from the LDAC 3 version package to the LEA3 version package, the headset can first update from the LDAC 3 version package to a compatible version package, and then update from the compatible version package to the LEA3 version package. The process of switching from the LDAC 2 or LDAC 1 version package to the LEA3 version package is similar and will not be elaborated here.

[0181] and Figure 9 In comparison, it can be seen that adding compatible version packages reduces the number of compatibility issues that new versions need to satisfy when updating LDAC or LEA version packages. That is, when designing a new version, only compatibility with older versions with the same features and compatibility with compatible version packages needs to be considered. Therefore, the OTA server needs to perform fewer compatibility tests when releasing a new version, the system and process for firmware upgrades are simplified accordingly, and users experience fewer problems caused by incompatibility when upgrading Bluetooth headset versions, resulting in an improved user experience.

[0182] It should be noted that, in this embodiment of the application, the OTA server is more able to control the compatibility between the compatible version package and the LDAC version package or the LEA version package because:

[0183] Compatibility packages typically contain only the system's basic functionalities to improve their stability and versatility. These basic functionalities are common to all feature packages (such as LDAC and LEA packages). Therefore, while maintaining the stability of these basic functionalities, compatibility packages provide a relatively common foundation for all feature packages. Furthermore, compatibility packages are usually designed modularly, allowing different features (such as LDAC and LEA features) to be added or removed as independent modules. This modular design also enables compatibility packages to be flexibly integrated with different feature packages without affecting their basic and feature functionalities. Therefore, compatibility packages are more likely to be compatible with LEA and LDAC packages.

[0184] Based on this, in this embodiment of the application, when the OTA server releases a new version of the Bluetooth headset suitable for dual-feature switching, the OTA server identifies the features of the version package. In addition, the OTA server also pre-releases a compatible version package to facilitate switching between dual-feature version packages.

[0185] The following is combined with Figures 11-13 The execution flow of the control method in the embodiments of this application will be described.

[0186] Figure 11 A flowchart illustrating the feature switching method provided in an embodiment of this application is shown, as follows: Figure 11 As shown:

[0187] For example, in S1101, the OTA server publishes a first feature version package, a second feature version package, and / or a compatible version package.

[0188] The first feature version package may be, for example, the LEA version package, and the second feature version package may be, for example, the LDAC version package; or, the first feature version package may be, for example, the LDAC version package, and the second feature version package may be, for example, the LEA version package.

[0189] Information regarding the definitions and structures of LEA, LDAC, and compatible version packages can be found in [link to documentation]. Figure 8 The embodiments shown are not described in detail here.

[0190] It should be noted that the LEA version package, LDAC version package, and compatible version package shown in the embodiments of this application are applicable to Bluetooth headsets with dual-feature switching. The feature version package for regular Bluetooth headsets released by the OTA server may differ from the feature version package in the embodiments of this application; wherein, a regular Bluetooth headset may, for example, be a Bluetooth headset that only supports the LEA feature or a Bluetooth headset that only supports the LDAC feature. The difference lies in the fact that, in the embodiments of this application, the OTA server needs to consider the compatibility of the feature version package with the compatible version package when releasing the feature version package; while the feature version package for regular Bluetooth headsets only needs to be compatible with older versions of the same feature. Therefore, the LEA version package and LDAC version package for dual-feature Bluetooth headsets are different from the LEA version package or LDAC version package for regular Bluetooth headsets.

[0191] S1102. After the Bluetooth headset establishes communication with the electronic device, the Bluetooth headset can use the first feature to play audio data; wherein, the Bluetooth headset is configured with a version package of the first feature.

[0192] After a Bluetooth headset establishes communication with an electronic device, the Bluetooth headset can receive and play audio data from the electronic device.

[0193] The Bluetooth headset's configuration package could be, for example, an LEA (Leadership in Audio) package, allowing the headset to play audio data based on LEA features. Alternatively, the Bluetooth headset's configuration package could be, for example, an LDAC (Learning from Dedicated Audio) package, allowing the headset to play audio data based on LDAC features.

[0194] It should be noted that the Bluetooth headset shown in the embodiments of this application can be a Bluetooth headset that supports dual-feature switching or multi-feature switching.

[0195] S1103, The electronic device receives a feature switching operation; wherein, the feature switching operation can be used as a trigger operation to instruct the Bluetooth headset to switch from the first feature to the second feature.

[0196] After connecting to a Bluetooth headset, the electronic device can obtain the headset's configuration information. For example, the electronic device can access, for instance, the Bluetooth headset card 501. Figure 5 The device management interface shown in 'c'; the configuration information of the Bluetooth headset may include the version package identifier, for example, the electronic device can obtain the LEA feature of the Bluetooth headset.

[0197] Feature switching operations may include: in Figure 5 In the interface shown in Figure c, a trigger operation is received for the feature switching control 503; the following is displayed: Figure 5 The interface shown in d; in the feature switching pop-up 505, a trigger operation is received for the selection box 507 of LDAC in the unselected state.

[0198] Alternatively, feature switching operations may include: in Figure 7 In the interface shown in Figure a, a trigger operation is received for the feature switching control 701.

[0199] The feature switching operation can also be an operation used to instruct the Bluetooth headset to switch from the second feature to the first feature. For example, if the first feature is the LEA feature and the second feature is the LDAC feature, the feature switching operation is an operation to instruct the Bluetooth headset to switch from the LDAC feature to the LEA feature, which is similar to the process described above (not shown in the figure), and will not be repeated here.

[0200] In this embodiment of the application, the feature switching operation can also be other forms of operation, and this embodiment of the application does not limit it.

[0201] S1104. In response to the feature switching operation, the electronic device queries the OTA server for the second feature version package and the compatible version package.

[0202] In response to a feature switching operation, the electronic device can check if there is an available version package to be updated, for example, by querying the OTA server for a second feature version package and a compatible version package.

[0203] For example, when switching from LEA features to LDAC features, the electronic device can query the OTA server to see if it includes LDAC version packages and compatible version packages; when switching from LDAC features to LEA features, the electronic device can query the OTA server to see if it includes LEA version packages and compatible version packages.

[0204] Understandably, when the OTA server releases a second feature version package and a compatible version package, the electronic device can find these packages on the OTA server. However, in some scenarios, due to network connectivity issues, OTA server malfunctions, unreleased packages, or removal of the packages, the electronic device may not be able to find these packages on the OTA server.

[0205] Therefore, if a second feature version package and a compatible version package are found, the electronic device may continue to step S1105. If no second feature version package and a compatible version package are found, the electronic device may continue to step S1110.

[0206] S1105. If the second feature version package and the compatible version package are found, the electronic device downloads the second feature version package and the compatible version package from the OTA server.

[0207] The electronic device downloads the second feature version package and the compatibility version package from the OTA server. For example, if the Bluetooth headset currently supports the LEA feature, the electronic device can download the LDAC version package and the compatibility version package from the OTA server.

[0208] S1106 The Bluetooth headset obtains a compatible version package from the electronic device and upgrades from the first feature version package to a compatible version package.

[0209] It is understandable that the compatible version package is compatible with the first feature version package; therefore, when the Bluetooth headset is upgraded from the first feature version package to the compatible version package, the Bluetooth headset can be updated smoothly and continue to operate normally, and the functionality and performance of the Bluetooth headset will not be affected by the incompatibility between the two.

[0210] S1107: The Bluetooth headset receives a second feature version package from the electronic device and upgrades from the compatible version package to the second feature version package.

[0211] Similarly, the compatible version package is compatible with the second feature version package; therefore, when the Bluetooth headset is upgraded from the compatible version package to the second feature version package, the Bluetooth headset can switch to the second feature smoothly.

[0212] It should be noted that in some embodiments, during the version switching process for a dual-feature Bluetooth headset, the Bluetooth headset may trigger the version upgrade process shown in the embodiments of this application. For example, after the electronic device receives a trigger operation instructing the Bluetooth headset to switch from the first feature to the second feature, the Bluetooth headset may receive a feature switching instruction from the electronic device; the feature switching instruction is used to instruct the switch from the first feature to the second feature. Then, the Bluetooth headset sends an instruction to the electronic device to update a compatible version package, instructing the electronic device to download the compatible version package from the OTA server. And, after upgrading to the compatible version package, the Bluetooth headset sends an instruction to the electronic device to update a second feature version package, instructing the electronic device to download the second feature version package from the OTA server.

[0213] In other embodiments, during the version switching process for a dual-feature Bluetooth headset, the electronic device may also trigger the version upgrade process shown in the embodiments of this application. For example, the electronic device may download a compatible version package and a second feature version package from an OTA server according to a trigger operation that instructs the Bluetooth headset to switch from the first feature to the second feature. Then, the electronic device may send the compatible version package to the Bluetooth headset and instruct the Bluetooth headset to update to the compatible version package; and the electronic device may send the second feature version package to the Bluetooth headset and instruct the Bluetooth headset to update to the second feature version package. The embodiments of this application do not limit the main device executing the version update process.

[0214] Furthermore, in this embodiment, the electronic device may obtain the second feature version package and the compatible version package before step S1106. Alternatively, the electronic device may obtain the second feature version package before step S1106 and the compatible version package before step S1107. This embodiment does not restrict the order in which the version packages are obtained.

[0215] S1108, Electronic device displays Bluetooth headset switched to second feature.

[0216] For example, taking the second characteristic as an LDAC characteristic, see [link to relevant documentation]. Figure 6 In the illustrated embodiment, after the feature switching is completed, the electronic device can display, for example... Figure 6 The interface shown in c is or Figure 6 The interface shown in 'd' is an example. Figure 6 In the interface shown in c, the LDAC selection box 507 is selected; for example, Figure 6 In the interface shown in d, the feature switching control 503 can indicate that the current feature of the Bluetooth headset is LDAC feature.

[0217] Or see Figure 7 In the illustrated embodiment, after the feature switching is completed, the electronic device can display, for example... Figure 7The interface shown in c; the feature switching control 701 in this interface can indicate that the current feature of the Bluetooth headset is LDAC feature.

[0218] S1109, Bluetooth headsets use the second feature to play audio data.

[0219] After switching to the second feature, the Bluetooth headset can process the audio data received from the electronic device using the algorithm of the second feature, thereby enabling the audio played by the Bluetooth headset to have the second feature.

[0220] It should be noted that this application embodiment uses the example of controlling a Bluetooth headset to switch from a first feature to a second feature to illustrate the feature switching process. In practical applications, it is also possible to control the Bluetooth headset to switch back from the second feature to the first feature. This application embodiment will not elaborate on this.

[0221] At this point, Bluetooth headphones can switch from the first feature to the second feature. It should be understood that Bluetooth headphones can also switch back from the second feature to the first feature. In the same Bluetooth headphones, users can use both the first and second features, which improves the cost-effectiveness of Bluetooth headphones and provides users with a richer listening experience.

[0222] Optionally, after step S1104, the method further includes:

[0223] S1110. If the second feature version package or a compatible version package cannot be found, the electronic device displays a prompt message.

[0224] In this embodiment, situations where the LDAC version package or a compatible version package cannot be found may include: network connection problems, OTA server failure, the version package not being released, or the version package being removed. In such cases, the electronic device can prompt the user with a message indicating that it cannot switch to the second feature.

[0225] For example, Figure 12 The diagram shows an interface schematic of a feature switching process provided in an embodiment of this application.

[0226] Users can perform feature switching operations, such as instructing Bluetooth headphones to switch from LEA features to LDAC features. Figure 6 In the interface shown in Figure a, in response to the triggering operation of the LDAC selection box 507, the electronic device can send a request to the OTA server to query the LDAC version package and the compatible version package. If the OTA server includes the LDAC version package and the compatible version package, the electronic device can display as shown in Figure a. Figure 6 The interface shown in b is shown in the image.

[0227] Alternatively, if the LDAC version package or a compatible version package is not included in the OTA server, the electronic device may display... Figure 12 The interface shown is... Figure 12 The interface shown includes a pop-up window 1201, which may include a prompt message 1202. The prompt message 1202 can be used to inform the user that the Bluetooth headset cannot switch to the LDAC version. For example, the prompt message 1202 could be "The current server does not have an LDAC version. Please stay tuned." This embodiment of the application does not limit the specific form of the prompt message 1202.

[0228] In this way, if feature switching is not possible, the electronic device can inform the user that the Bluetooth headset supports feature switching, but feature switching is not currently possible; the user can continue to use the dual features of the Bluetooth headset after the feature version is released or re-released.

[0229] The following is combined with Figure 13 right Figure 11 The process in the illustrated embodiment will be further explained; such as Figure 13 As shown:

[0230] For example, in S1301, the electronic device establishes communication with the Bluetooth headset.

[0231] Electronic devices can establish a Bluetooth channel with Bluetooth headsets to enable data transmission between the electronic devices and Bluetooth headsets.

[0232] S1302. The electronic device displays the device management interface of the Bluetooth headset; wherein, the device management interface includes a feature switching control, which can indicate that the Bluetooth headset supports a first feature.

[0233] Bluetooth headset device management interface can be, for example Figure 6 The interface shown in d, or Figure 7 The interface shown in 'c' is an example. The feature switching control can be feature switching control 503 (suitable for dual-feature switching or multi-feature switching) or feature switching control 701 (suitable for dual-feature switching). The second feature can be, for example, an LDAC feature or a LEA feature. Taking LDAC as an example, in... Figure 6 In the interface shown by d, the feature switching control 503 indicates that the Bluetooth headset's current feature is LDAC; or, in Figure 7 In the interface shown in c, the feature switching control 701 indicates that the current feature of the Bluetooth headset is LDAC feature.

[0234] Optionally, after the Bluetooth headset and electronic device are connected, the electronic device can obtain the device information of the Bluetooth headset, such as the device name, device type, manufacturer information, and supported features. For a conventional Bluetooth headset, the supported features information may indicate that the headset supports a single feature, such as LEA or LDAC. For a dual-feature Bluetooth headset, the supported features information may indicate that the headset supports multiple features, such as LEA and LDAC, with the current feature being either LEA or LDAC. The electronic device can determine whether the Bluetooth headset supports feature switching based on the supported features information. The electronic device can also make this determination based on other information (such as the device type and manufacturer information of the Bluetooth headset), which is not limited in this embodiment.

[0235] When the Bluetooth headset supports dual or multiple features, the electronic device can control the headset to switch features. However, if the Bluetooth headset does not support dual or multiple features, the electronic device may not display the feature switching control in the headset's device management interface, or the feature switching control may be grayed out. The electronic device will not proceed with subsequent steps.

[0236] S1303, The electronic device receives a feature switching operation.

[0237] The process can be referred to in the relevant description in step S1103, and will not be repeated here.

[0238] S1304. In response to the feature switching operation, the electronic device sends a query request to the OTA server.

[0239] A query request can be used to instruct the OTA server to check whether the second feature version package and the compatible version package are included. The query request may include an identifier for the second feature version package (e.g., if the second feature is LDAC, the identifier is type=LDAC; or if the second feature is LEA, the identifier is type=LEA) and an identifier for the compatible version package (type=ALL).

[0240] S1305. In response to the query request, the OTA server queries whether the second feature version package and the compatible version package are included, and returns the query results to the electronic device.

[0241] The query results are used to indicate whether the OTA server includes the second feature version package and the compatibility version package.

[0242] S1306. If the query result indicates that the OTA server includes a second feature version package and a compatible version package, the electronic device sends a feature switching instruction to the Bluetooth headset; the feature switching instruction can be used to instruct the Bluetooth headset to switch from the first feature to the second feature.

[0243] The feature switching command corresponds to the feature switching operation triggered by the user. For example, if the feature switching operation is used to instruct the Bluetooth headset to switch from a first feature to a second feature, then the feature switching command can be used to instruct the Bluetooth headset to switch from the first feature to the second feature; if the feature switching operation is used to instruct the Bluetooth headset to switch from the second feature to the first feature, then the feature switching command can be used to instruct the Bluetooth headset to switch from the second feature to the first feature.

[0244] Optionally, if the query results indicate that the OTA server does not include the second feature version package and the compatible version package, the electronic device may perform, for example, step S1110.

[0245] S1307. In response to the feature switching command, the Bluetooth headset sends a first version number of the first feature version packet to the electronic device; the first version number is less than or equal to the actual version number of the first feature version packet.

[0246] The real version number can be understood as the version number of the first feature version package currently configured in the Bluetooth headset; the first version number can be understood as the virtual version number of the first feature version package in the Bluetooth headset, and the first version number is less than or equal to the real version number. The first version number can be a version number that is virtually downgraded from the real version number of the first feature version package. For example, the first version number can be the initial version number of the first feature version package (also known as the minimum version number or the lowest version number).

[0247] It is understandable that users can periodically update the Bluetooth headset version using their electronic devices during use. Therefore, the actual version number of the first feature version package in the Bluetooth headset is often greater than the first version number. In some embodiments, the actual version number of the first feature version package may be equal to the first version number even if the electronic device does not upgrade the Bluetooth headset. This application does not impose any limitations on this.

[0248] It should be noted that in this embodiment, the first version number being less than or equal to the actual version number may include: the first version number being less than or equal to the actual version number; the release time of the first version number being later than or equal to the release time of the actual version number, etc. Taking the first feature as an LEA feature as an example, see [link to relevant documentation]. Figure 10 The actual version number can be, for example, LEA1, LEA2, or LEA3; the first version number can be, for example, LEA1.

[0249] After the electronic device sends a feature switching command to the Bluetooth headset, the Bluetooth headset can return the feature version information to the electronic device to instruct the electronic device to obtain the corresponding version of the compatible version package from the OTA server. For example, the version number of the compatible version package is greater than the first version number.

[0250] It should be noted that, in this embodiment, the Bluetooth headset can virtually downgrade the actual version number of the first feature version package to ensure that when the electronic device requests a compatible version package from the OTA, the version number of the first feature version package is lower than the version number of the compatible version package. It should be understood that during software and firmware upgrades, forward compatibility is generally required, meaning the new version can handle the data formats and functions of the old version. Upgrading from a lower version to a higher version is more stable and reliable, so downgrading from a higher version to a lower version may be limited.

[0251] For example, Bluetooth headsets can be configured with firmware logic, such as allowing upgraded versions to be higher than the current version, to restrict version downgrades during the upgrade process. The device management application of the electronic device can manage the Bluetooth headset's version update process, restricting downgrade operations through application logic. And / or, the OTA server may have policies configured to restrict downgrades, such as only allowing the provision of version packages higher than the current Bluetooth headset version to the electronic device.

[0252] In these situations, Bluetooth headsets may not be able to upgrade from any feature version to a compatible version at will; for example, if the first feature is the LEA feature, and the LEA version package version number in the Bluetooth headset is LEA3; if the LEA3 version number is greater than the version number of the compatible version package, then the upgrade path from the latest version of the LEA version package to the compatible version package in the Bluetooth headset will be restricted.

[0253] Therefore, in this embodiment of the application, during the Bluetooth headset version update process, it is necessary to virtually downgrade the current version package in the Bluetooth headset so that the current version package is at a lower version and the compatible version package is at a higher version, thereby smoothly upgrading from a lower version to a higher version, and controlling the Bluetooth headset to switch from the first feature version package to the compatible version package.

[0254] It should be noted that, due to the backward compatibility limitation that the version package can be downgraded from a higher version to a lower version, in this embodiment of the application, downgrading the first feature version package from the real version number to the first version number can be a virtual downgrade process of the version number, rather than the Bluetooth headset being downgraded from the first feature version package of the real version number to the first feature version package of the first version number; that is, during the virtual downgrade process, the first feature version package in the Bluetooth headset does not change.

[0255] The virtual downgrade process may include: during multiple upgrades, the Bluetooth headset may record one or more version information of the first feature version package; the Bluetooth headset may find a first version number in one or more version information, the first version number being less than or equal to the actual version number; the Bluetooth headset may send the first version number to the electronic device.

[0256] For example, if the first feature is LEA, the actual version number is LEA3, and the Bluetooth headset includes LEA3, LEA2, and LEA1, then the first version number can be either LEA2 or LEA1. Alternatively, if the actual version number is LEA1, and the Bluetooth headset includes LEA1, then the first version number is LEA1.

[0257] Understandably, to increase the probability that the version number after virtual downgrading is lower than the version number of the compatible version package, the first version number can be set to the initial version number of the first feature version package. For example, when the first feature is the LEA feature, the first version number can be LEA1; when the first feature is the LDAC feature, the first version number can be LDAC 1. In practical applications, the first version number can also be any other version number that is less than the actual version number but greater than the minimum version number, and this application embodiment does not impose any restrictions on this.

[0258] S1308. The electronic device sends the first version number and the identifier of the compatible version package to the OTA server.

[0259] The compatibility package identifier can be used to instruct the OTA server to return a compatible version package; for example, tpye=ALL. The first version number is used to indicate the current version number, so that the OTA server can issue a higher version of the compatible version package.

[0260] The electronic device can send a download request to the OTA server to instruct the OTA server to return a version package. Specifically, in step S1308, the electronic device can send a first download request to the OTA server, which may include a first version number and an identifier of a compatible version package.

[0261] S1309. The electronic device receives the compatible version package returned by the OTA server and sends the compatible version package to the Bluetooth headset; wherein the version number of the compatible version package is greater than the first version number.

[0262] The OTA receives an identifier for a compatible version package from the electronic device. The OTA server can then query the compatible version package in the OTA server based on this identifier. The version number of the compatible version package must be greater than the first version number.

[0263] In some embodiments, to ensure that the version number of the compatible version package is greater than the first version number, the OTA server can query the maximum version of the compatible version package (also known as the latest version, highest version, etc.). If the maximum version of the compatible version package is found, the electronic device can obtain the compatible version package of the maximum version returned by the OTA server. In some embodiments, the OTA server can return a download link for downloading the compatible version package, and the electronic device can download the compatible version package based on the download link.

[0264] The S1310 Bluetooth headset has been upgraded from the first feature version package to the compatibility version package.

[0265] Electronic devices can send a compatible version package to Bluetooth headsets via the Bluetooth channel. Once the Bluetooth headsets receive the compatible version package, they can upgrade from the first feature version package to the compatible version package.

[0266] It's understandable that the process involves the Bluetooth headset upgrading from the first feature version package with the actual version number to a compatible version package, rather than upgrading from the first feature version package with the first version number to a compatible version package. The virtual downgraded first version number is only used during the process of the electronic device downloading the compatible version package from the OTA server to avoid restrictions on the download path of the compatible version package.

[0267] Because the OTA server controls the compatibility of the compatibility package with the first specific version package of any version before releasing the compatibility package, the Bluetooth headset can be directly upgraded from the first specific version package to the compatibility package after it receives the compatibility package, and no compatibility issues will occur in this process.

[0268] S1311. After the Bluetooth headset is upgraded to a compatible version package, the electronic device sends the version number of the compatible version package and the identifier of the second feature version package to the OTA server.

[0269] The identifier for the second feature version package can be used to instruct the OTA server to return a second feature version package; the identifier for the second feature version package can be, for example, type=LEA or type=LDAC. The version number of the compatible version package is used to indicate the current version number, so that the OTA server can issue a higher version of the second feature version package.

[0270] After the upgrade is complete, the Bluetooth headset can send an upgrade completion message to the electronic device. The electronic device can then proceed with subsequent processes, such as obtaining the second feature version package and instructing the Bluetooth headset to upgrade to the second feature version package.

[0271] It should be noted that in step S1311, the electronic device may send a second download request to the OTA server. The second download request may include the version number of the compatible version package and the identifier of the second feature version package.

[0272] S1312. The electronic device receives the second feature version packet returned by the OTA server and sends the second feature version packet to the Bluetooth headset; the version number of the second feature version packet is greater than the version number of the compatible version packet.

[0273] Understandably, to avoid restrictions on the download path of the second feature version package, embodiments of this application can control the version number of the second feature version package to be greater than the version number of the compatible version package. For example, the version number of the second feature version package can be the maximum version number of the second feature version package. Furthermore, the version package with the maximum version number can also provide users with more new features, thereby improving the user experience.

[0274] Understandably, when an OTA server releases a new version of the first feature package and / or the second feature package, it can ensure that the version number of the first feature package and / or the second feature package is greater than the maximum version number of the compatible package. This design allows for a virtual downgrade from any feature package to a compatible package, satisfying the upgrade path from a lower to a higher version. Similarly, when upgrading from a compatible package to another feature package, the maximum version number of that other feature package must be greater than the maximum version number of the compatible package, thus enabling a smooth upgrade from the compatible package to the second feature package.

[0275] It should be noted that when a Bluetooth headset is upgraded to a compatible version package, it can be upgraded to either the first or second feature package. Therefore, after the Bluetooth headset is configured with a compatible version package, the electronic device needs to send an identifier for the second feature package to the OTA server to instruct the OTA server whether to return the first or second feature package.

[0276] The S1313 Bluetooth headset has been upgraded from the compatibility version package to the second feature version package.

[0277] The process can be referred to in the relevant description in step S1310, and will not be repeated here.

[0278] S1314, An application for managing Bluetooth headsets in an electronic device that allows Bluetooth headsets to reconnect to other devices.

[0279] The application used to manage Bluetooth headsets can be a device management application as described in the embodiments of this application, such as a smart space application.

[0280] During the Bluetooth headset upgrade process, the Bluetooth headset can disconnect from the electronic device, and reconnect to the electronic device after the Bluetooth headset upgrade is completed.

[0281] In this embodiment, during the firmware upgrade process, the Bluetooth headset can disconnect from the device management application in the electronic device. This is because the firmware upgrade process requires restarting the headset's system or entering a specific upgrade mode to ensure complete transmission of upgrade data, reduce external interference during the upgrade process, and ensure the security and stability of the upgrade process. After the upgrade is complete, the Bluetooth headset can automatically restart and attempt to reconnect to the previously paired device (e.g., the electronic device).

[0282] S1315. The electronic device displays the device management interface of the Bluetooth headset; wherein, the device management interface includes a feature switching control, which can indicate that the Bluetooth headset supports a second feature.

[0283] Bluetooth headset device management interface can be, for example Figure 5 The interface shown in c, or Figure 7 The interface shown in Figure 'a'. The feature switching control can be feature switching control 503 (this control is suitable for dual-feature switching or multi-feature switching) or feature switching control 701 (this control is suitable for dual-feature switching). The first feature can be, for example, the LEA feature or the LDAC feature. Taking the LEA feature as an example, in... Figure 5 In the interface shown in c, the feature switching control 503 indicates that the Bluetooth headset's current feature is LEA; or, in Figure 7 In the interface shown in Figure 'a', the feature switching control 701 indicates that the current feature of the Bluetooth headset is the LEA feature.

[0284] It should be noted that in the embodiments of this application, the electronic device can also control the Bluetooth headset to switch from the second feature back to the first feature. This process can refer to the above steps and will not be repeated here.

[0285] Thus, electronic devices can control Bluetooth headsets to switch between features, allowing the same Bluetooth headset to extend multiple features, thereby providing users with a variety of features and enhancing their listening experience.

[0286] It should be noted that, in this application embodiment, the resource-constrained device is a Bluetooth headset, the device for managing the resource-constrained device is an electronic device, and the first and second characteristics are LEA and LDAC characteristics, or LDAC and LEA characteristics, as an example to illustrate the characteristic switching method shown in this application embodiment. In practical applications, both the resource-constrained device and the device for managing the resource-constrained device can be other devices, and the first and second characteristics are characteristics related to the resource-constrained device. This application embodiment will not elaborate further on this.

[0287] It should be noted that the module names involved in the embodiments of this application can all be defined as other names, as long as they can achieve the function of each module, and no specific restrictions are placed on the module names.

[0288] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in the embodiments of this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0289] The feature switching method of the present application embodiments has been described above. The apparatus for executing the above method provided in the present application embodiments is described below. Those skilled in the art will understand that the methods and apparatus can be combined and referenced with each other, and the related apparatus provided in the present application embodiments can execute the steps in the above feature switching method.

[0290] like Figure 14 As shown, the feature switching device 1400 can be used in communication equipment, circuits, hardware components, or chips. The feature switching device includes a display unit 1401 and a processing unit 1402. The display unit 1401 supports the display steps performed by the feature switching device 1400; the processing unit 1402 supports the information processing steps performed by the feature switching device 1400.

[0291] In a possible implementation, the feature switching device 1400 may also include a communication unit 1403. Specifically, the communication unit supports the feature switching device 1400 in performing data transmission and data reception steps. The communication unit 1403 may be an input or output interface, pin, or circuit, etc.

[0292] In a possible embodiment, the feature switching device may further include a storage unit 1404. The processing unit 1402 and the storage unit 1404 are connected via a line. The storage unit 1404 may include one or more memories, which may be devices in one or more devices or circuits used for storing programs or data. The storage unit 1404 may exist independently and be connected to the processing unit 1402 of the feature switching device via a communication line. Alternatively, the storage unit 1404 may be integrated with the processing unit 1402.

[0293] Storage unit 1404 may store computer-executable instructions for the methods in the terminal device, so that processing unit 1402 executes the methods in the above embodiments. Storage unit 1404 may be a register, cache, or RAM, etc., and storage unit 1404 may be integrated with processing unit 1402. Storage unit 1404 may be a read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions, and storage unit 1404 may be independent of processing unit 1402.

[0294] The feature switching method provided in this application can be applied to electronic devices with communication functions. Electronic devices include terminal devices, and the specific device form of the terminal device can be referred to the above-mentioned descriptions, which will not be repeated here.

[0295] This application provides a terminal device, which includes a processor and a memory; the memory stores computer execution instructions; the processor executes the computer execution instructions stored in the memory, causing the terminal device to perform the above-described method.

[0296] This application provides a chip. The chip includes a processor, which is used to call a computer program in memory to execute the technical solutions in the above embodiments. Its implementation principle and technical effects are similar to those in the related embodiments described above, and will not be repeated here.

[0297] This application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program. When the computer program is executed by a processor, it implements the methods described above. The methods described in the above embodiments can be implemented wholly or partially by software, hardware, firmware, or any combination thereof. If implemented in software, the functionality can be stored as one or more instructions or code on or transmitted over the computer-readable medium. The computer-readable medium can include computer storage media and communication media, and can also include any medium that can transfer a computer program from one place to another. The storage medium can be any target medium accessible by a computer.

[0298] In one possible implementation, a computer-readable medium may include RAM, ROM, compact disc read-only memory (CD-ROM) or other optical disc storage, disk storage or other magnetic storage devices, or any other medium targeted to carry or to store the required program code in the form of instructions or data structures, and accessible by a computer. Furthermore, any connection is appropriately referred to as a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used herein, disks and optical discs include optical discs, laser discs, optical discs, Digital Versatile Discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while optical discs optically reproduce data using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0299] This application provides a computer program product, which includes a computer program that, when run, causes a computer to perform the above-described method.

[0300] This application describes embodiments of methods, apparatus (systems), and computer program products according to embodiments of this application with reference to flowchart illustrations and / or block diagrams. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processing unit of a general-purpose computer, special-purpose computer, embedded processor, or other programmable device to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing device, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0301] The above detailed embodiments further illustrate the purpose, technical solution, and beneficial effects of the embodiments of this application. It should be understood that the above are merely specific embodiments of the embodiments of this application and are not intended to limit the protection scope of the embodiments of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solutions of the embodiments of this application should be included within the protection scope of the embodiments of this application.

Claims

1. A feature switching method, characterized in that, Applied to a first device, the method includes: When the first device and the second device establish communication, a first interface is displayed; the first device is used to manage the second device; the first interface is an application interface for managing the second device; the first interface includes a first control; wherein, the first control is used to instruct the second device to switch features, and the first control indicates that the second device is configured with a first feature; the first device is different from the second device; the first device includes an electronic device, and the second device includes a Bluetooth headset; A trigger operation is received for the first control; the trigger operation for the first control is used to instruct the second device to switch from the first feature to the second feature; the first feature and the second feature are different audio encoding methods; the first feature includes Bluetooth Low Energy (LEA) feature or Low Latency Audio Codec (LDAC) feature; the second feature includes LADC feature or LEA feature; Based on the trigger operation of the first control, the second device is instructed to switch from the first feature to the third feature, and then instructed to switch from the third feature to the second feature; both the first feature and the second feature are features of extended functions that run based on the third feature; the third feature is a feature that supports the Bluetooth headset to run basic functions, and the basic functions include at least one of the following: basic Bluetooth connection function, basic audio decoding function, and basic audio playback function; The second interface is displayed; the second interface includes the first control, and the first control represents that the second device is configured with the second feature; The step of instructing the second device to switch from the first feature to the third feature based on a trigger operation on the first control includes: Based on the trigger operation for the first control, a first version number of the first feature version package is obtained from the Bluetooth headset; wherein, the first feature version package is used to support the Bluetooth headset to run the first feature; the first version number is less than or equal to the actual version number of the first feature version package; the third feature version package is downloaded from the OTA server based on the first version number and the identifier of the third feature version package; wherein, the identifier of the third feature version package is used to indicate that the version package type returned by the OTA server is the third feature version package; the third feature version package is used to support the Bluetooth headset to run the third feature; the version number of the third feature version package is greater than the first version number; the third feature version package is sent to the Bluetooth headset, and the Bluetooth headset is instructed to install the third feature version package; The instruction to switch the second device from the third feature to the second feature includes: The second feature version package is downloaded from the OTA server according to the version number of the third feature version package and the identifier of the second feature version package; wherein, the identifier of the second feature version package is used to indicate that the version package type returned by the OTA server is the second feature version package; the second feature version package is used to support the Bluetooth headset to run the second feature; the version number of the second feature version package is greater than the version number of the third feature version package; the second feature version package is sent to the Bluetooth headset, and the Bluetooth headset is instructed to install the second feature version package.

2. The method according to claim 1, characterized in that, The first feature version package is compatible with the third feature version package; the first version number of the first feature version package includes the minimum version number of the first feature version package; the version number of the third feature version package includes the maximum version number of the third feature version package.

3. The method according to claim 1, characterized in that, The third feature version package is compatible with the second feature version package; the version number of the second feature version package includes the maximum version number of the second feature version package.

4. The method according to any one of claims 1-3, characterized in that, The receipt of a trigger operation for the first control includes: receiving a click operation for the first control.

5. The method according to any one of claims 1-3, characterized in that, The receipt of a trigger operation for the first control includes: A click operation was received for the first control; After receiving the trigger operation for the first control, the method further includes: A third interface is displayed; the third interface includes a second control and a third control, the second control corresponds to the first feature, and the third control corresponds to the second feature; the second control is in a selected state, and the third control is in an unselected state; A selection operation was received for the third control.

6. The method according to any one of claims 1-3, characterized in that, After receiving a trigger operation for the first control, the method further includes: Send a query request to the OTA server, the query request being used to instruct the OTA server to query whether the second feature version package and the third feature version package are included; Receive the query results returned by the OTA server.

7. The method according to claim 6, characterized in that, Also includes: If the query results indicate that the OTA server includes both the second feature version package and the third feature version package, a fourth interface will be displayed. The fourth interface includes a first prompt message, which is used to prompt the user that the Bluetooth headset is switching from the first feature to the second feature.

8. The method according to claim 6, characterized in that, Also includes: If the query results indicate that the OTA server does not include the second feature version package or the third feature version package, the fifth interface will be displayed. The fifth interface includes a second prompt message, which is used to inform the user that the feature switching failed and that the second feature version package does not exist in the OTA server.

9. A feature switching method, characterized in that, The application is to a server, wherein the server maintains multiple first feature version packages, second feature version packages, and / or third feature version packages for a second device; the first feature version package is used to support the second device in running the first feature, the second feature version package is used to support the second device in running the second feature, and the third feature version package is used to support the second device in running the third feature; Both the first feature and the second feature are features of extended functions that operate based on the third feature; the method includes: Upon receiving a download request from the first device, the system sends the second feature version package and the third feature version package to the first device. The first device manages the second device. The download request is issued by the first device after establishing communication with the second device, based on a trigger operation on the first control. The trigger operation on the first control instructs the second device to switch from the first feature to the second feature. The server includes an OTA server. The first device includes an electronic device, and the second device includes a Bluetooth headset. The first feature and the second feature are different audio encoding methods. The first feature includes Bluetooth Low Energy (LEA) or Low Latency Audio Codec (LDAC). The second feature includes LADC or LEA. The third feature is a feature that supports the Bluetooth headset's basic functions, which include at least one of the following: basic Bluetooth connectivity, basic audio decoding, and basic audio playback. The step of sending the second feature version package and the third feature version package to the first device after receiving the download request from the first device includes: Upon receiving a first download request from the first device, the third feature version package is sent to the first device; the first download request includes an identifier of the third feature version package and a first version number of the first feature version package; the identifier of the third feature version package is used to indicate the download of the third feature version package; the version number of the third feature version package is greater than the first version number; the first version number is less than or equal to the actual version number of the first feature version package in the second device; upon receiving a second download request from the first device, a second feature version package is sent to the first device; the second download request includes an identifier of the second feature version package and a version number of the third feature version package; the identifier of the second feature version package is used to indicate the download of the second feature version package; the version number of the second feature version package is greater than the version number of the third feature version package.

10. The method according to claim 9, characterized in that, The first feature version package is compatible with the third feature version package, and the second feature version package is compatible with the third feature version package; the first version number includes the minimum version number of the first feature version package; the version number of the second feature version package includes the maximum version number of the second feature version package. The version number of the third feature package includes the maximum version number of the third feature package.

11. The method according to claim 9 or 10, characterized in that, Before sending the third feature version packet to the first device, the method further includes: Received the query command sent by the first device; In response to the query command, a query result is queried and returned to the first device; the query result is used to indicate whether the OTA includes the second feature version package and the third feature version package.

12. A feature switching method, characterized in that, Applied to a second device, the method includes: After establishing communication with the first device, the second device receives a second feature version packet and a third feature version packet sent by the first device. The second device is configured with a first feature version packet, which supports the second device in running the first feature. The second feature version packet supports the second device in running the second feature, and the third feature version packet supports the second device in running the third feature. Both the first and second features are extended functionalities based on the third feature. The first device includes an electronic device, and the second device includes a Bluetooth headset. The first and second features are different audio encoding methods. The first feature includes a Bluetooth Low Energy (LEA) feature or a Low Latency Audio Codec (LDAC) feature. The second feature includes a Low-Latency Audio Codec (LADC) feature or an LEA feature. The third feature supports the Bluetooth headset in operating basic functions, which include at least one of the following: basic Bluetooth connectivity, basic audio decoding, and basic audio playback. Upgrade from the first feature version package to the third feature version package; and upgrade from the third feature version package to the second feature version package; Before receiving the second feature version packet and the third feature version packet sent by the first device, the method further includes: The device sends a first version number of the first feature version package to the electronic device, wherein the first version number is less than or equal to the actual version number of the first feature version package in the Bluetooth headset; wherein the first version number is used to obtain the third feature version package, and the version number of the third feature version package is greater than the first version number; the third feature version package is downloaded by the first device from an over-the-air (OTA) server based on the first version number and the identifier of the third feature version package; the identifier of the third feature version package is used to indicate that the version package type returned by the OTA server is the third feature version package; the second feature version package is downloaded by the first device from the OTA server based on the version number of the third feature version package and the identifier of the second feature version package; the identifier of the second feature version package is used to indicate that the version package type returned by the OTA server is the second feature version package; the version number of the second feature version package is greater than the version number of the third feature version package.

13. A feature switching method, characterized in that, The system is applied to a system including an electronic device, a Bluetooth headset, and an OTA server, wherein the electronic device is used to manage the Bluetooth headset; the method includes: The electronic device establishes communication with the Bluetooth headset; The electronic device displays a first interface; the first interface is an application interface for managing the Bluetooth headset; the first interface includes a first control; wherein, the first control is used to instruct the Bluetooth headset to switch features, and the first control indicates that the Bluetooth headset is configured with a first feature; the first feature includes an LEA feature or an LDAC feature; The electronic device receives a trigger operation on the first control; the trigger operation on the first control is used to indicate a switch from the first feature to a second feature; the second feature includes a LADC feature or a LEA feature; The electronic device sends a query request to the OTA server; In response to the query request, the OTA server queries whether a second feature version package and a third feature version package are included, and returns the query result to the electronic device; the second feature version package is used to support the Bluetooth headset to run the second feature, and the third feature version package is used to support the Bluetooth headset to run the third feature; the third feature is a feature that supports the Bluetooth headset to run basic functions, and the basic functions include at least one of the following: basic Bluetooth connection function, basic audio decoding function, and basic audio playback function; the second feature version package and the third feature version package are compatible; If the query result indicates that the OTA server includes the second feature version package and the third feature version package, the electronic device sends a feature switching instruction to the Bluetooth headset, the feature switching instruction being used to indicate switching from the first feature to the second feature; In response to the feature switching command, the Bluetooth headset sends a first version number of a first feature version package to the electronic device; the first feature version package is used to support the Bluetooth headset in running the first feature; the first version number is less than or equal to the actual version number of the first feature version package in the Bluetooth headset; the first feature version package and the third feature version package are compatible; The electronic device sends the first version number and the identifier of the third feature version package to the OTA server; the identifier of the third feature version package is used to indicate the download of the third feature version package; The electronic device receives the third feature version packet returned by the OTA server and sends the third feature version packet to the Bluetooth headset; the version number of the third feature version packet is greater than the first version number; The Bluetooth headset is upgraded from the first feature version package to the third feature version package; The electronic device sends the version number of the third feature version package and the identifier of the second feature version package to the OTA server; the identifier of the second feature version package is used to indicate the download of the second feature version package; The electronic device receives the second feature version packet returned by the OTA server and sends the second feature version packet to the Bluetooth headset; the version number of the second feature version packet is greater than the version number of the third feature version packet. The Bluetooth headset is upgraded from the third feature version package to the second feature version package; The Bluetooth headset reconnects to the electronic device's application for managing the Bluetooth headset; The electronic device displays a second interface; the second interface includes the first control, and the first control indicates that the Bluetooth headset is configured with the second feature.

14. An electronic device, characterized in that, include: Processor and memory; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the electronic device to perform the method as described in any one of claims 1-5.

15. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-13.

16. A chip system, characterized in that, It includes at least one processor and a communication interface, the communication interface and the at least one processor being interconnected via a line, the at least one processor being configured to run a computer program or instructions to perform the method as described in any one of claims 1-13.

17. A computer program product, characterized in that, Includes a computer program that, when run, causes a computer to perform the method as described in any one of claims 1-13.

Images