Power control method and device, equipment and program product

Abstract

The invention discloses a power control method and device, equipment and a program product, and the method comprises the steps: determining an operation parameter, and determining a target scene type based on the operation parameter; wherein the target scene type at least comprises one or more of the following items: a non-call scene type; a call scene type; a network high-power mode scene type; a Bluetooth high-power mode scene type; acquiring a rollback parameter corresponding to the target scene type; and performing power control processing based on the rollback parameter.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, in particular to a power control method and device, electronic equipment and computer program product. BACKGROUND

[0002] Wireless communication technology is widely used in modern mobile devices, aiming to realize the cooperative work between multiple communication systems. In the multi-system coexistence scenario, how to reasonably allocate and control the transmit power of each system to meet the specific absorption rate (SAR) has become one of the key problems to improve the system performance.

[0003] The related technology allocates the maximum power that can be used by each specific frequency band under each system by setting the power ratio of cellular, Wi-Fi and Bluetooth (BT).

[0004] However, due to the lack of support for multi-system concurrent scenarios, and the inability to fine-tune power control according to different frequency bands and antenna characteristics, it is difficult to adapt flexibly in different device configurations and use environments, affecting the overall communication performance and compliance. SUMMARY

[0005] The embodiments of the present application provide a power control method and device, equipment and program product, which can effectively improve the TX performance of Wi-Fi / BT under weak signal conditions, and ensure the best communication performance under the premise of meeting the SAR compliance.

[0006] The technical scheme of the embodiments of the present application is as follows: In a first aspect, the embodiments of the present application provide a power control method, which comprises: determining a running parameter, and determining a target scene type based on the running parameter; wherein the target scene type comprises at least one or more of the following: a non-call scene type; a call scene type; a network high power mode scene type; and a Bluetooth high power mode scene type; obtaining a fallback parameter corresponding to the target scene type; performing power control processing based on the fallback parameter.

[0007] In a second aspect, the embodiments of the present application provide a power control device, which comprises: A determination unit is configured to determine a running parameter, and determine a target scene type based on the running parameter; wherein the target scene type comprises at least one or more of the following: a non-call scene type; a call scene type; a network high power mode scene type; and a Bluetooth high power mode scene type; An obtaining unit is configured to obtain a fallback parameter corresponding to the target scene type. The determining unit is further configured to determine the MTPL of the wireless communication based on the back-off parameter.

[0008] In a third aspect, an electronic device is provided, which includes a processor and a memory storing processor-executable instructions that, when executed by the processor, implement the method of the first aspect.

[0009] In a fourth aspect, a computer program product is provided, which includes a computer program or instructions that, when executed by a processor, implement the method of the first aspect.

[0010] The embodiments of the present application provide a power control method and device, equipment and program product, determine a running parameter, and determine a target scene type based on the running parameter; wherein the target scene type includes at least one or more of the following: a non-call scene type; a call scene type; a network high-power mode scene type; a Bluetooth high-power mode scene type; obtain a back-off parameter corresponding to the target scene type; and perform power control processing based on the back-off parameter. As can be seen, in the embodiments of the present application, the corresponding target scene type can be determined through real-time monitoring of the running parameter, and the target scene type can include a call and a non-call scene type, and can also include a network, a Bluetooth high-power mode scene type and other multiple scenes; then the back-off parameter corresponding to the target scene type can be obtained, and power control processing is performed according to the back-off parameter. That is, the present application can subdivide the scene based on the real-time determined running condition, and set the back-off parameter corresponding to multiple scenes, so as to use the back-off parameter suitable for multiple scenes to complete power control for different scenes. This way can effectively improve the transmit (TX) performance of Wi-Fi / BT under weak signal conditions, and ensure the best communication performance under the premise of meeting SAR compliance. BRIEF DESCRIPTION OF DRAWINGS

[0011] Figure 1 Schematic diagram of the power control method Figure 1 ; Figure 2 Schematic diagram of the power control method Figure 2 ; Figure 3 Schematic diagram of the power control method Figure 3 ; Figure 4 Schematic diagram of the power control method implementation process provided by the embodiments of the present application Figure 1 ; Figure 5 Schematic diagram of the mapping relationship between the pre-set scene and the back-off parameter provided by the embodiments of the present application Figure 1 ; Figure 6This is a schematic diagram illustrating the mapping relationship between pre-set scenarios and fallback parameters proposed in the embodiments of this application. Figure 2 ; Figure 7 This is a schematic diagram illustrating the implementation of the power control method proposed in the embodiments of this application. Figure 1 ; Figure 8 This is a schematic diagram of the power control method proposed in the embodiments of this application. Figure 2 ; Figure 9 This is a schematic diagram of the power control method proposed in the embodiments of this application. Figure 3 ; Figure 10 This is a schematic diagram of the power control method proposed in the embodiments of this application. Figure 1 ; Figure 11 This is a schematic diagram of the power control method proposed in the embodiments of this application. Figure 2 ; Figure 12 This is a schematic diagram illustrating the implementation of the power control method proposed in the embodiments of this application. Figure 4 ; Figure 13 This is a schematic diagram of the composition of the power control device proposed in the embodiments of this application; Figure 14 This is a schematic diagram of the composition structure of the electronic device proposed in the embodiments of this application. Detailed Implementation

[0012] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only for explaining the differences between the applications and are not intended to limit the application. Furthermore, it should be noted that, for ease of description, only the parts that differ from the relevant applications are shown in the accompanying drawings.

[0013] Wireless communication technology is widely used in modern mobile devices, aiming to enable collaborative operation between various communication standards (such as cellular, Wi-Fi, Bluetooth, etc.). In scenarios where multiple standards coexist, how to rationally allocate and control the transmission power of each standard to meet SAR requirements has become one of the key issues in improving system performance.

[0014] The proposed technology proposes a joint Smart SAR scheme that shares maximum available power by setting the power ratio of cellular, Wi-Fi, and Bluetooth, and relies on the Reserve Margin parameter for power reservation calculation. Specifically, it allocates the maximum power available for each standard's corresponding frequency band by setting the power ratio of cellular, Wi-Fi, and Bluetooth.

[0015] like Figure 1As shown, this is a combined cellular and Wi-Fi / BT configuration. During the Global Config process, the configuration items and their meanings (values) are as follows: `version` is the system version identifier, with a value of 23, used to distinguish different versions' functions or compatibility. `oem_id` is the unique identifier of the original equipment manufacturer (OEM), with a value of 12648430, commonly used for device traceability or inter-manufacturer collaboration. `power_class` is the power level, with a value of 2, possibly related to the device's power consumption, transmit power, and other technical parameters. `voice_call_exp_mode` is the voice call extension mode, with a value of "Time-Averaged," which may involve signal processing strategies for voice calls (such as time-based signal averaging algorithms). `volte_data_throttling_control` is VoLTE (Voice over LTE) data traffic control, with a value of "ON," indicating that data traffic in VoLTE scenarios is limited or managed. `vnr_data_throttling_control` is VNR (depending on the specific scenario, such as virtual network operators) data traffic control, with a value of "ON," indicating that VNR-related data traffic is controlled. wlan_bt_control is the joint control of WLAN (Wireless Local Area Network) and Bluetooth. The value "ON" indicates that the collaborative management function of WLAN and Bluetooth (such as resource scheduling, interference avoidance, etc.) is enabled.

[0016] like Figure 2 As shown, the power ratio of each standard is set through Reserve Margin. Among them, for groups such as HeadDSI, Minimum Reserve Margin, BT Config, and NTNConfig, the configuration items and values ​​are displayed in the "Antenna Group 0 / 1 / 2" column under each group.

[0017] like Figure 3 As shown, when setting up cellular / Wi-Fi / BT DSI scenarios, the SAR fallback mechanism only supports single-mode power fallback, and is mainly set for two scenarios: cellular earpiece on or off, without considering the complex scenario requirements of multi-mode concurrent transmission.

[0018] Therefore, it can be seen that currently, when implementing power control, there are only two scenarios: cellular earpiece on and off. This setting relies entirely on Qualcomm's Reserve Margin calculation for cellular and Wi-Fi / BT power settings. However, this Reserve Margin cannot distinguish between different frequency bands and different antennas of cellular and Wi-Fi / BT for customized settings, resulting in different power requirements of different antennas under different standards and frequency bands.

[0019] It is evident that the lack of support for concurrent multi-standard scenarios and the inability to perform fine-grained power control based on different frequency bands and antenna characteristics make it difficult to adapt flexibly to different device configurations and usage environments, thus affecting overall communication performance and compliance.

[0020] To address the aforementioned issues, embodiments of this application provide a power control method, apparatus, device, and program product. This method determines operating parameters and, based on these parameters, determines a target scenario type. The target scenario type includes at least one or more of the following: a non-call scenario; a call scenario; a network high-power mode scenario; and a Bluetooth high-power mode scenario. The method obtains fallback parameters corresponding to the target scenario type and performs power control processing based on these fallback parameters. Therefore, in embodiments of this application, the corresponding target scenario type can be determined through real-time monitoring of operating parameters. This target scenario type can include both call and non-call scenarios, as well as various scenarios such as network and Bluetooth high-power mode scenarios. Then, fallback parameters corresponding to the target scenario type can be obtained, and power control processing can be performed based on these fallback parameters. In other words, this application can subdivide scenarios based on real-time determined operating conditions and set fallback parameters corresponding to multiple scenarios. This allows for power control using fallback parameters applicable to various scenarios, effectively improving the TX performance of Wi-Fi / BT under weak signal conditions and ensuring optimal communication performance while meeting SAR compliance requirements.

[0021] For ease of understanding, the technical terms used in this application are explained below: 1) SAR (Specific Absorption Rate): This measures the degree of energy absorption by the human body when exposed to an electromagnetic field. In wireless communication devices, SAR is an important indicator for assessing the safety of the device for humans. When multiple wireless standards transmit simultaneously, the transmission power of each standard must be adjusted according to SAR limits to ensure compliance with safety standards.

[0022] 2) DSI (Device State Index): Used to identify the current working scenario of the terminal. Different DSI values ​​correspond to different power back-off strategies and maximum transmission power limits (MTPL). By setting different DSI values, the transmit power of different wireless modules can be flexibly controlled in different usage scenarios.

[0023] 3) HPM (High Power Mode): A special operating mode in which certain wireless modules (such as Wi-Fi or Bluetooth) can increase their transmission power under specific conditions to cope with weak signal environments, thereby improving the user experience.

[0024] 4) MTPL (Maximum Transmission Power Limit): This refers to the maximum transmit power that a wireless module can use in a specific scenario while meeting SAR compliance requirements. MTPL is dynamically adjusted according to the current scenario to achieve reasonable power allocation and optimized use.

[0025] 5) Relationship between AP (Application Processor) and Modem: The AP is responsible for running the operating system and applications, while the Modem is responsible for wireless communication functions. They communicate via the system bus. The AP can send commands to the Modem based on detected scene information to adjust the power parameters of the wireless module.

[0026] 6) RSRP (Reference Signal Received Power): This parameter is used to evaluate the signal strength of a cellular network. RSRP is commonly used in cellular networks to reflect the strength of the reference signal received by the user equipment.

[0027] 7) RSSI (Received Signal Strength Indicator): This parameter is used to evaluate the signal strength of the Wi-Fi / BT module. RSSI is widely used in Wi-Fi and Bluetooth to indicate the strength of the received signal.

[0028] 8) SNR (Signal-to-Noise Ratio): An important parameter for measuring signal quality, representing the ratio of useful signal to background noise. The higher the SNR, the better the signal quality, and the more beneficial it is to improving communication performance.

[0029] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0030] One embodiment of this application provides a power control method that can be applied to a power control device or electronic device, and can also be applied to any terminal that includes a power control device or electronic device.

[0031] In some embodiments, the power control methods provided in the various embodiments of this application can be executed by a baseband chip of a power control device or an electronic device. That is, in some implementations, the power control methods in the various embodiments of this application can be executed by a baseband chip.

[0032] In some embodiments, the execution entity of the power control method provided in the various embodiments of this application may be the application processor (AP) and modem in the terminal device. That is, the power control method in the various embodiments of this application may be executed by the AP, by the modem, or by interaction between the AP and the modem.

[0033] For example, in some embodiments, the application processor (AP) and modem are two core components in a mobile device, working together to enable the device's intelligence and network connectivity. Taking a smartphone as an example, the AP is the "brain" of the smartphone, integrating multiple functions such as the CPU, GPU, image signal processor (ISP), and communication module into a single chip. Its main role is to drive the operating system, run applications, and process all core data. The modem is the "signal translator," responsible for converting digital signals to analog signals to enable communication between the device and the network. It completes data transmission through modulation (encoding digital signals into analog signals) and demodulation (restoring digital signals from analog signals).

[0034] For example, in some embodiments, the modem can be integrated into the access point (AP) or exist as a standalone chip. The AP handles most functions (such as running the system and processing images), while the modem focuses on communication (such as dialing and internet access). The two work together via communication methods such as AT command sets or PCIe interfaces.

[0035] The following description uses a power control device as an example to illustrate the power control method proposed in the embodiments of this application.

[0036] In the embodiments of this application, Figure 4 This is a schematic diagram of the implementation process of the power control method proposed in the embodiments of this application. Figure 1 ,like Figure 4 As shown, the power control method may include the following steps: Step 401: Determine the operating parameters and determine the target scenario type based on the operating parameters; wherein, the target scenario type includes at least one or more of the following: non-call scenario type; call scenario type; network high-power mode scenario type; Bluetooth high-power mode scenario type.

[0037] In the embodiments of this application, the first device may first determine the operating parameters, and then further determine the target scene type based on the operating parameters.

[0038] In some embodiments, operating parameters can be used to characterize the real-time state and real-time operation of the first device. The current motion parameters can be obtained through real-time monitoring of preset functional modules within the first device.

[0039] In the embodiments of this application, when determining the operating parameters, the preset functional modules can be monitored in real time to obtain the operating parameters.

[0040] In some embodiments, the preset functional modules include at least one or more of the following: earpiece module; communication module (e.g., cellular module); network module (e.g., Wi-Fi module); Bluetooth module.

[0041] In some embodiments, a preset functional module refers to a functional unit configured and invoked in the first device. Preset functional modules include, but are not limited to, a handset module, a communication module, a network module, and a Bluetooth module. Each of the preset functional modules is responsible for monitoring the associated hardware or communication status and outputting the operating parameters generated by this monitoring.

[0042] For example, in some embodiments, the earpiece module may include, but is not limited to, a microphone and a speaker. Real-time monitoring of the earpiece module can determine whether the first device is in a call state. For example, the earpiece module can be activated by detecting the usage of the microphone and speaker.

[0043] For example, in some embodiments, key metrics in cellular communication, such as signal-to-noise ratio (SNR) and reference signal received power (RSRP), can be obtained through real-time monitoring of the communication module. SNR represents the ratio of the received signal to background noise; a higher value indicates a clearer signal. RSRP measures the strength of the cellular signal; a higher value indicates better signal quality.

[0044] For example, in some embodiments, Wi-Fi signal strength can be determined by real-time monitoring of the network module, where the quality of the wireless network can be reflected by the Received Signal Strength Indication (RSSI). The Received Signal Strength Indication (RSSI) is typically represented as a negative number; the closer the value is to 0, the stronger the wireless network signal.

[0045] For example, in some embodiments, connection quality can be determined by real-time monitoring of the Bluetooth module. Specifically, RSSI can be used to assess connection quality, thereby determining whether the Bluetooth device is at a considerable distance or in an environment with significant signal interference.

[0046] In some embodiments, the operating parameters may include at least one or more of the following: the status parameters of the earpiece module; the SNR of the communication module; the RSRP of the communication module; the RSSI of the network module; and the RSSI of the Bluetooth module.

[0047] In other words, in the embodiments of this application, the operating parameters may include a set of key data obtained by real-time monitoring of preset functional modules.

[0048] In some embodiments, operating parameters may be used to describe the current communication state and / or operating state and / or connection state of the first device.

[0049] In some embodiments, a network module typically refers to a wireless communication module such as Wi-Fi; a communication module refers to a baseband module used for mobile communication, such as a 4G communication module or a 5G communication module.

[0050] In some embodiments, the target scenario type includes at least one or more of the following: non-call scenario type; call scenario type; network high-power mode scenario type; Bluetooth high-power mode scenario type.

[0051] For example, in some embodiments, a non-call scenario type can be understood as a scenario type in which the call function is not used, and a call scenario type can be understood as a scenario type in which the call function is used.

[0052] For example, in some embodiments, the network high-power mode scenario type can be understood as the scenario type in which the transmission power of Wi-Fi needs to be increased.

[0053] For example, in some embodiments, the Bluetooth High Power Mode scenario type can be understood as a scenario type in which the transmission power of Bluetooth needs to be increased.

[0054] In the embodiments of this application, when determining the target scenario type based on operating parameters, if the status parameter of the earpiece module indicates that the earpiece is turned on, the target scenario type is determined to be a call scenario type.

[0055] In the embodiments of this application, when determining the target scenario type based on operating parameters, if the status parameter of the earpiece module indicates that the earpiece is off, the target scenario type is determined to be a non-call scenario type.

[0056] In some embodiments, the status parameters of the earpiece module can be used to indicate whether the earpiece is on or off. Specifically, if the status parameters of the earpiece module indicate that the earpiece is on, that is, the earpiece module is detected to be in an on state, then it can be assumed that a call is in progress, and the target scenario type can be determined as a call scenario type.

[0057] In some embodiments, if the status parameter of the earpiece module indicates that the earpiece is off, that is, the earpiece module is detected to be in a closed state, then the target scenario type can be determined to be a non-call scenario type.

[0058] In the embodiments of this application, the specific scenario of entering a high-power network mode can be identified by comprehensively judging multiple wireless communication parameters (such as the signal strength RSSI of the network module, the received signal strength RSRP of the communication module, and the signal-to-noise ratio SNR). This multi-dimensional detection mechanism, which comprehensively judges multiple wireless communication parameters, can more accurately reflect the communication environment state of the first device, thereby triggering a corresponding power adjustment strategy.

[0059] In the embodiments of this application, when determining the target scenario type based on operating parameters, if the RSSI of the network module is less than a first threshold, and the RSRP of the communication module is greater than a second threshold and the SNR of the communication module is greater than a third threshold, the target scenario type is determined to be a network high-power mode scenario type.

[0060] In some embodiments, the network high-power mode scenario type can be determined by combining the RSSI of the network module, the RSRP of the communication module, and the SNR of the communication module. Specifically, the RSSI of the network module can be used to determine the Wi-Fi signal strength, while the RSRP and SNR of the communication module can be used to determine the cellular signal strength.

[0061] In some embodiments, the first threshold, the second threshold, and the third threshold can be preset values, and this application does not specifically limit the specific values ​​of the first threshold, the second threshold, and the third threshold.

[0062] In some embodiments, after comparing the RSSI of the network module, the RSRP of the communication module, and the SNR of the communication module with the corresponding first threshold, second threshold, and third threshold, respectively, if the RSSI of the network module is less than the first threshold, it can be determined that the Wi-Fi is in a weak signal scenario. If the RSRP of the communication module is greater than the second threshold and the SNR of the communication module is greater than the third threshold, it can be determined that the cellular signal is strong. That is, by combining the RSSI of the network module, the RSRP of the communication module, and the SNR of the communication module, it can be determined that the current Wi-Fi is in a weak signal and the cellular signal is strong, allowing the Wi-Fi signal strength to be improved by increasing the Wi-Fi transmission power, thereby determining the target scenario type as a network high-power mode scenario type.

[0063] For example, in some embodiments, assuming the first threshold is -75, the second threshold is -110, and the third threshold is 10, then if the Wi-Fi RSSI is under weak signal conditions, such as Wi-Fi RSSI < -75, and the cellular is under strong signal conditions, such as cellular RSRP > -110 and cellular SNR > 10, then it can be determined that the high-power scenario of switching to Wi-Fi is allowed, that is, the target scenario type is determined to be the network high-power mode scenario type.

[0064] In other words, in some embodiments, if the RSSI of the network module is lower than a first threshold (e.g., -75dBm), it indicates that the current signal strength of the network module is considered weak; simultaneously, if the RSRP of the communication module is higher than a second threshold (e.g., -110dBm) and the SNR of the communication module is higher than a third threshold (e.g., 10dB), it indicates that the current signal quality of the communication module is considered good. In this case, the network module is allowed to increase its transmit power without affecting the overall security and compliance of the device. At this time, the current scenario is determined to be a high-power network mode, and a corresponding power management strategy is adopted.

[0065] Therefore, this application demonstrates that by real-time acquisition of signal quality indicators from preset functional modules and setting reasonable threshold ranges, it is possible to determine whether a special scenario is in effect. For example, if the communication module signal is strong (high RSRP, high SNR) while the network module signal is weak (low RSSI), in order to ensure the transmission performance of the network module, it will enter high-power mode (HPM) to increase the network module's transmission power, thereby enhancing connection stability and data transmission efficiency.

[0066] In the embodiments of this application, the key to the scene detection mechanism lies in using multi-parameter collaborative judgment to avoid misjudgments that may be caused by a single indicator. For example, a low RSSI of the network module alone may not be sufficient to accurately determine whether to enter a high-power mode, as other interference factors may also exist. However, by combining the strong signal status on the communication module side, it can be reasonably inferred that the current communication environment is relatively stable and suitable for power optimization adjustments.

[0067] In the embodiments of this application, when determining the target scenario type based on operating parameters, if the RSSI of the Bluetooth module is less than the fourth threshold, and the RSRP of the communication module is greater than the second threshold and the SNR of the communication module is greater than the third threshold, the target scenario type is determined to be the Bluetooth high power mode scenario type.

[0068] In some embodiments, the Bluetooth high-power mode scenario type can be determined by combining the RSSI of the Bluetooth module, the RSRP of the communication module, and the SNR of the communication module. Specifically, the RSSI of the Bluetooth module can be used to determine the Bluetooth signal strength, while the RSRP and SNR of the communication module can be used to determine the cellular signal strength.

[0069] In some embodiments, the fourth threshold, the second threshold, and the third threshold can be preset values, and this application does not specifically limit the specific values ​​of the fourth threshold, the second threshold, and the third threshold.

[0070] In some embodiments, after comparing the RSSI of the Bluetooth module, the RSRP of the communication module, and the SNR of the communication module with the corresponding fourth threshold, second threshold, and third threshold, respectively, if the RSSI of the Bluetooth module is less than the fourth threshold, it can be determined that Bluetooth is in a weak signal scenario. If the RSRP of the communication module is greater than the second threshold and the SNR of the communication module is greater than the third threshold, it can be determined that the cellular signal is strong. That is, by combining the RSSI of the Bluetooth module, the RSRP of the communication module, and the SNR of the communication module, it can be determined that the current Bluetooth is in a weak signal and the cellular signal is strong, allowing the Bluetooth signal strength to be improved by increasing the Bluetooth transmission power, thereby determining the target scenario type as the Bluetooth high-power mode scenario type.

[0071] For example, in some embodiments, assuming the fourth threshold is -75, the second threshold is -110, and the third threshold is 10, then if the Bluetooth RSSI is in a weak signal state, such as Bluetooth RSSI < -75, and the cellular is in a strong signal state, such as cellular RSRP > -110 and cellular SNR > 10, then it can be determined that the high-power scenario of Bluetooth is allowed to be switched to, that is, the target scenario type is determined to be the network high-power mode scenario type.

[0072] In other words, in some embodiments, if the RSSI of the Bluetooth module is below a fourth threshold (e.g., -75dBm), it indicates that the current signal strength of the Bluetooth module is considered weak; simultaneously, if the RSRP of the communication module is above a second threshold (e.g., -110dBm) and the SNR of the communication module is above a third threshold (e.g., 10dB), it indicates that the current signal quality of the communication module is considered good. In this case, the Bluetooth module is allowed to increase its transmission power without affecting the overall security and compliance of the device. At this point, the current scenario is determined to be a high-power network mode, and a corresponding power management strategy is adopted.

[0073] Therefore, this application demonstrates that by real-time acquisition of signal quality indicators from preset functional modules and setting reasonable threshold ranges, it is possible to determine whether a special scenario is in effect. For example, if the communication module signal is strong (high RSRP, high SNR) while the Bluetooth module signal is weak (low RSSI), in order to ensure the transmission performance of the Bluetooth module, it will enter high-power mode (HPM) to increase the Bluetooth module's transmission power, thereby enhancing connection stability and data transmission efficiency.

[0074] In the embodiments of this application, the key to the scene detection mechanism lies in using multi-parameter collaborative judgment to avoid misjudgments that may be caused by a single indicator. For example, a low RSSI of the Bluetooth module alone may not be sufficient to accurately determine whether to enter high-power mode, as other interference factors may also exist. However, by combining the strong signal status on the communication module side, it can be reasonably inferred that the current communication environment is relatively stable and suitable for power optimization adjustments.

[0075] In some embodiments, the RSSI mentioned above refers to Received Signal Strength Indication, used to measure the signal strength received by the relevant device. For example, a lower RSSI of the Bluetooth module indicates poorer connection quality, which may affect the stability of audio transmission.

[0076] In some embodiments, the RSRP involved in the above scheme is the reference signal received power, which can reflect the strength of the signal transmitted by the base station in the cellular network. The higher the value, the stronger the signal.

[0077] In some embodiments, the SNR involved in the above scheme is the signal-to-noise ratio, which represents the ratio of useful signal to background noise. The higher the value, the better the communication quality.

[0078] In summary, this application accurately identifies whether a high-power mode (network high-power mode or Bluetooth high-power mode) has been entered by comprehensively judging multiple parameters such as the RSSI of the network module, the RSSI of the Bluetooth module, and the RSRP and SNR of the communication module. This allows for further dynamic adjustment of the Wi-Fi / BT's transmission power. For example, under the premise of good communication module signal, higher transmission power can be provided to the Wi-Fi / BT, effectively improving the communication performance of the Wi-Fi / BT in weak signal environments.

[0079] Therefore, in the embodiments of this application, the state parameters of the earpiece module are used to determine whether the current state is in a call; the SNR and RSRP of the communication module can be used to evaluate cellular signal quality; the RSSI value of the network module can be used to evaluate Wi-Fi signal strength; and the RSSI value of the Bluetooth module can be used to evaluate the quality of the Bluetooth connection. The state parameters of the earpiece module, the SNR and RSRP of the communication module, the RSSI of the network module, and the RSSI of the Bluetooth module together constitute the basic criteria for judging the current scenario. By comprehensively analyzing the state parameters of the earpiece module, the SNR and RSRP of the communication module, the RSSI of the network module, and the RSSI of the Bluetooth module, the specific usage environment of the terminal can be accurately identified, and a scenario processing strategy suitable for that specific usage environment can be selected.

[0080] In the embodiments of this application, by real-time monitoring of preset functional modules and obtaining comprehensive operating parameters, the current communication scenario of the first device can be more accurately determined, thereby dynamically adjusting the transmission power of relevant modules. This method can effectively improve the TX performance of Wi-Fi / BT under weak signal conditions.

[0081] Step 402: Obtain the rollback parameters corresponding to the target scene type.

[0082] In the embodiments of this application, after determining the operating parameters and determining the target scene type based on the operating parameters, the first device can further obtain the rollback parameters corresponding to the target scene type.

[0083] In the embodiments of this application, when obtaining the fallback parameters corresponding to the target scene type, the fallback parameters corresponding to the target scene type can be determined based on the pre-set mapping relationship between scenes and fallback parameters.

[0084] In the embodiments of this application, the fallback parameters corresponding to non-call scenario types include at least a first MTPL; the fallback parameters corresponding to call scenario types include at least a second MTPL; the fallback parameters corresponding to network high-power mode scenario types include at least a third MTPL of the communication module and / or a fourth MTPL of the network module; and the fallback parameters corresponding to Bluetooth high-power mode scenario types include at least a fifth MTPL of the communication module and / or a sixth MTPL of the Bluetooth module.

[0085] Exemplary, in some embodiments, such as Figure 5 As shown, the pre-set mapping relationship between scenarios and fallback parameters can be represented as the correspondence between target scenario types and fallback parameters. For example, assuming the target scenario type is a non-call scenario, the corresponding fallback parameters may include the first MTPL of the communication module; assuming the target scenario type is a call scenario, the corresponding fallback parameters may include the second MTPL of the communication module; assuming the target scenario type is a network high-power mode scenario, the corresponding fallback parameters may include the third MTPL of the communication module and / or the fourth MTPL of the network module; assuming the target scenario type is a Bluetooth high-power mode scenario, the corresponding fallback parameters may include the fifth MTPL of the communication module and / or the sixth MTPL of the Bluetooth module.

[0086] Exemplary, in some embodiments, such as Figure 6 As shown, the pre-set mapping relationship between scenarios and fallback parameters can be represented as the correspondence between the identifier of the target scenario type and the fallback parameters. For example, assuming the target scenario type is a non-call scenario type, represented by identifier DSI4, the corresponding fallback parameters may include the first MTPL of the communication module; assuming the target scenario type is a call scenario type, represented by identifier DSI5, the corresponding fallback parameters may include the second MTPL of the communication module; assuming the target scenario type is a network high-power mode scenario type, represented by identifier DSI2, the corresponding fallback parameters may include the third MTPL of the communication module and / or the fourth MTPL of the network module; assuming the target scenario type is a Bluetooth high-power mode scenario type, represented by identifier DSI3, the corresponding fallback parameters may include the fifth MTPL of the communication module and / or the sixth MTPL of the Bluetooth module.

[0087] In some embodiments, MTPL (Maximum Transmit Power Limit) refers to the maximum transmit power allowed for one or more wireless modules (such as communication modules, network modules, and Bluetooth modules) while meeting SAR specifications. In this application, MTPL can be adaptively adjusted according to different Scenario Status Indicators (DSIs).

[0088] In some embodiments, a mapping relationship between scene types and fallback parameters can be preset. This mapping relationship refers to a pre-defined table or configuration file that binds different scene types (such as call scene type, non-call scene type, Wi-Fi high-power mode scene type, Bluetooth high-power mode scene type, etc.) to their corresponding power control fallback parameters.

[0089] In some embodiments, by mapping the scene type to the fallback parameters, the corresponding fallback parameters can be automatically loaded according to the currently monitored scene type (target scene type), thereby enabling dynamic adjustment of the transmission power under different standards (such as cellular, Wi-Fi, Bluetooth).

[0090] In the embodiments of this application, for non-call scenario types, based on the pre-set mapping relationship between scenarios and fallback parameters, it can be determined that the corresponding fallback parameters include the first MTPL.

[0091] In some embodiments, non-call scenario type typically refers to no voice call being made. In such scenarios, there is no need to consider the quality and stability of voice communication, so a lower MTPL of the communication module can be allocated, and there is no need to make appropriate backoff to the transmit power of the Wi-Fi module (network module) and Bluetooth module.

[0092] For example, in some embodiments, when the handset is off, DSI4 mode is enabled (i.e., the target scenario type is a non-call scenario type), and the MTPL of the communication module is set to a lower value, such as the first MTPL.

[0093] In some embodiments, even when the earpiece is off, it may still be in a high-power demand state using the network module or Bluetooth module. In this case, different MTPL values ​​can be loaded depending on whether the network module or Bluetooth module is in HPM mode, i.e., further judgment can be made for the high-power mode and the corresponding fallback parameters can be determined.

[0094] For example, in some embodiments, when the handset is off, if the network module RSSI is determined to be weak, a higher network module MTPL can be enabled to improve uplink transmission performance, while the MTPL of the communication module can be appropriately reduced to maintain SAR compliance.

[0095] In the embodiments of this application, for the call scenario type, based on the pre-set mapping relationship between the scenario and the fallback parameters, it can be determined that the corresponding fallback parameters include the second MTPL.

[0096] In some embodiments, the call scenario type refers to a scenario used for voice calls. In such scenarios, to ensure the quality and stability of voice communication, a higher MTPL (Media Transmission Power Level) can be prioritized, and the transmit power of the Wi-Fi and Bluetooth modules can be appropriately backed up.

[0097] For example, in some embodiments, when the handset is on, DSI5 mode is enabled (i.e., the target scenario type is a call scenario type), and the MTPL of the communication module is set to a higher value, such as the second MTPL.

[0098] For example, in some embodiments, when the earpiece is on, the transmission power of the network module and the Bluetooth module can also be limited to avoid signal interference and ensure clear and smooth voice calls.

[0099] In the embodiments of this application, for network high-power mode scenario types, based on the pre-set mapping relationship between scenarios and fallback parameters, it can be determined that the corresponding fallback parameters include the third MTPL of the communication module and / or the fourth MTPL of the network module.

[0100] In some embodiments, the network high-power mode scenario type refers to entering the Wi-Fi high-power mode scenario type when the cellular signal is strong and the Wi-Fi signal is weak, in order to improve the MTPL of the network module.

[0101] For example, in some embodiments, if the cellular signal is strong and the Wi-Fi signal is weak, and DSI2 mode is enabled (i.e., the target scenario type is a network high-power mode scenario), then the MTPL of the communication module can be set to the third MTPL, and / or the MTPL of the network module (Wi-Fi module) can be set to the fourth MTPL. Ultimately, this can significantly enhance the transmission capability of the network module while ensuring cellular communication quality.

[0102] In the embodiments of this application, for Bluetooth high power mode scenario types, based on the pre-set mapping relationship between scenario and fallback parameters, it can be determined that the corresponding fallback parameters include the fifth MTPL of the communication module and / or the sixth MTPL of the Bluetooth module.

[0103] In some embodiments, the Bluetooth high-power mode scenario type refers to entering the Bluetooth high-power mode scenario type when the cellular signal is strong and the Bluetooth signal is weak, in order to improve the MTPL of the Bluetooth module.

[0104] For example, in some embodiments, if the cellular signal is strong and the Bluetooth signal is weak, and DSI3 mode is enabled (i.e., the target scenario type is Bluetooth high-power mode), then the MTPL of the communication module can be set to the fifth MTPL, and / or the MTPL of the Bluetooth module can be set to the sixth MTPL. Ultimately, this can significantly enhance the transmission capability of the Bluetooth module while ensuring cellular communication quality.

[0105] Therefore, in the embodiments of this application, the appropriate fallback parameter (MTPL parameter) for the current communication state (target scenario type) is dynamically selected based on the mapping relationship between scenario type and fallback parameter. This allows for flexible adaptation to different communication needs and optimization of the wireless module's transmit power configuration. For example, it can improve the performance of Wi-Fi and Bluetooth modules when they are in weak signal conditions.

[0106] For example, in some embodiments, in the Wi-Fi HPM scenario type (network high power mode scenario type), the MTPL of the Wi-Fi module can be appropriately increased in order to improve the connection performance under weak signal conditions.

[0107] For example, in some embodiments, in a call scenario, the TX power of the communication module is prioritized, while the power of the Wi-Fi module and the Bluetooth module is limited.

[0108] Step 403: Perform power control processing based on backoff parameters.

[0109] In the embodiments of this application, after obtaining the fallback parameters corresponding to the target scene type, the first device can further perform power control processing based on the fallback parameters.

[0110] In the embodiments of this application, when performing power control processing based on fallback parameters, in non-call scenario types, the communication module is power controlled according to the first MTPL.

[0111] In the embodiments of this application, when performing power control processing based on fallback parameters, the communication module is power controlled according to the second MTPL under the call scenario type.

[0112] In the embodiments of this application, when performing power control processing based on fallback parameters, in the network high-power mode scenario, the communication module is power controlled according to the third MTPL, and / or the network module is power controlled according to the fourth MTPL.

[0113] In the embodiments of this application, when performing power control processing based on fallback parameters, in the Bluetooth high power mode scenario, the communication module is power controlled according to the fifth MTPL, and / or the Bluetooth module is power controlled according to the sixth MTPL.

[0114] For example, in some embodiments, in non-call scenario types, the MTPL of wireless communication can be determined according to a first MTPL, that is, the power control of the communication module can be performed according to the first MTPL.

[0115] For example, in some embodiments, when performing power control processing based on fallback parameters, one implementation is as follows: the AP sends a broadcast oplus.wifi.stsar.action.SETHPM, which carries a DSI scenario value, such as DSI4 corresponding to a non-call scenario type. After receiving the DSI scenario value sent by the AP, the modem sets the MTPL (first MTPL) corresponding to DSI4 to the maximum power of the communication module.

[0116] For example, in some embodiments, in a call scenario, the MTPL of wireless communication can be determined according to a second MTPL, that is, the power control of the communication module can be performed according to the second MTPL.

[0117] For example, in some embodiments, when performing power control processing based on fallback parameters, one implementation is as follows: the AP sends a broadcast oplus.wifi.stsar.action.SETHPM, which carries a DSI scenario value, such as DSI5 corresponding to the call scenario type. After receiving the DSI scenario value sent by the AP, the modem sets the MTPL (second MTPL) corresponding to DSI5 to the maximum power of the communication module.

[0118] For example, in some embodiments, under the network high-power mode scenario type, the MTPL of the communication module can be determined according to the third MTPL, that is, the power control of the communication module is performed according to the third MTPL; and / or, the MTPL of the network module can be determined according to the fourth MTPL, that is, the power control of the network module is performed according to the fourth MTPL.

[0119] For example, in some embodiments, when performing power control processing based on fallback parameters, one implementation is as follows: the AP sends a broadcast oplus.wifi.stsar.action.SETHPM, which carries a DSI scenario value, such as DSI2 corresponding to the network high-power mode scenario type. After receiving the DSI scenario value sent by the AP, the modem sets the MTPL (third MTPL and fourth MTPL) corresponding to DSI2 to the maximum power of the communication module and the maximum power of the network module, respectively.

[0120] For example, in some embodiments, in the Bluetooth high power mode scenario, the MTPL of the communication module can be determined according to the fifth MTPL, that is, the power control of the communication module is performed according to the fifth MTPL; and / or, the MTPL of the Bluetooth module can be determined according to the sixth MTPL, that is, the power control of the Bluetooth module is performed according to the sixth MTPL.

[0121] For example, in some embodiments, when performing power control processing based on fallback parameters, one implementation is as follows: the AP sends a broadcast oplus.wifi.stsar.action.SETHPM, which carries a DSI scenario value, such as DSI3 corresponding to the Bluetooth high power mode scenario type. After receiving the DSI scenario value sent by the AP, the modem sets the MTPL (fifth MTPL and sixth MTPL) corresponding to DSI3 to the maximum power of the communication module and the maximum power of the Bluetooth module, respectively.

[0122] In other words, in this application, the transmission power requirements for each wireless module (such as cellular, Wi-Fi, and Bluetooth) vary depending on the usage scenario. For example, in non-call scenarios, the stability and speed of data transmission are of greater concern, so the transmission power of Wi-Fi or Bluetooth can be appropriately increased. In call scenarios, the quality of cellular communication should be prioritized to avoid interference that could cause call interruptions, so the transmission power of the communication module should be increased.

[0123] For example, in some embodiments, a non-call scenario refers to any scenario where the user is not in a voice call state, such as data browsing, video playback, or gaming. In a non-call scenario, a higher transmit power can be selected to improve data transmission efficiency. For instance, in a non-call scenario, using a first MTPL configuration means that the wireless communication module (cellular module) can operate under relatively relaxed conditions, thereby improving transmission rate and connection stability.

[0124] For example, in some embodiments, the call scenario type refers to a scenario where a voice call is in progress. In this scenario, the transmission power of Wi-Fi / BT should be limited to avoid interfering with cellular signals and thus affecting call quality. For instance, in a call scenario, using a second MTPL configuration prioritizes the stability and clarity of cellular communication.

[0125] For example, in some embodiments, the network high-power mode scenario is a data transmission scenario that typically occurs when Wi-Fi signals are weak and cellular signals are strong. In this case, to ensure Wi-Fi connection stability, the MTPL of each module can be adjusted. The Wi-Fi module can use higher transmit power, while the communication module correspondingly reduces its power to meet SAR compliance requirements. For instance, in network high-power mode, the communication module uses a third MTPL, and the Wi-Fi module uses a fourth MTPL, resulting in a moderate decrease in cellular power and an increase in Wi-Fi module power, thereby improving Wi-Fi performance without violating SAR restrictions.

[0126] For example, in some embodiments, the Bluetooth high-power mode scenario is a data transmission scenario suitable for situations where the Bluetooth signal is weak and the cellular signal is strong. For instance, when a Bluetooth headset is placed in a locker while exercising in a gym, its signal is blocked. In this case, the Bluetooth module enters high-power mode, increasing its transmission power to maintain the connection. For example, in Bluetooth high-power mode, the communication module uses the fifth MTPL, and the Bluetooth module uses the sixth MTPL, thereby increasing the Bluetooth transmission power and improving Bluetooth performance without violating SAR limits.

[0127] In other words, in the embodiments of this application, under different scenarios (target scenario types), the transmit power of each module is dynamically adjusted according to a preset MTPL value to ensure optimal communication performance while meeting SAR compliance. Specifically, the dynamic MTPL adjustment mechanism under these multiple scenarios effectively balances the power among the wireless modules, significantly improving communication performance in specific scenarios while ensuring SAR compliance, especially when Wi-Fi and Bluetooth signals are weak, thus ensuring optimal communication performance while meeting SAR compliance.

[0128] In summary, this embodiment achieves intelligent power management in various usage environments by differentiating MTPL settings for different scenarios and flexibly adjusting them in conjunction with backoff parameters. The method proposed in this embodiment not only improves the stability and efficiency of wireless communication but also effectively reduces power consumption and SAR risk, providing terminal devices with a more intelligent and personalized communication experience.

[0129] The power control method proposed in this application can be implemented in one way: real-time monitoring of whether the terminal's cellular and Wi-Fi / BT are enabled and the corresponding RSRP / RSSI / SNR, thereby adopting the MTPL of the corresponding DSI to ensure that the cellular and Wi-Fi / BT use a better MTPL. For example, in a single-cellular scenario, if the cellular is in a call state, then call scenario DSI5 is enabled, and the cellular uses a higher MTPL; in a Wi-Fi HPM scenario, DSI2 is enabled, and the MTPL power preset by DSI2 is set to the corresponding antennas of the Wi-Fi and cellular frequency bands; in a BT HPM scenario, DSI3 is enabled, and the MTPL power preset by DSI3 is set to the corresponding antennas of the Wi-Fi and cellular frequency bands; in the remaining scenarios, DSI4 is enabled, and the MTPL power preset by DSI4 is set to the corresponding antennas of the cellular and Wi-Fi / BT frequency bands.

[0130] Another implementation of the power control method proposed in this application is as follows: Real-time monitoring of whether the terminal's cellular and Wi-Fi / BT are enabled and their corresponding RSRP / RSSI / SNR, thereby adopting the MTPL of the corresponding DSI to ensure that the cellular and Wi-Fi / BT use a better MTPL. For example, in a single-cellular scenario, if the cellular is in a call state, then call scenario DSI5 is enabled, and the cellular uses a higher MTPL; if it is in a non-call state, and Wi-Fi and BT are not enabled (i.e., a non-call scenario), then call scenario DSI4 is enabled, and the preset MTPL power of DSI4 is set to the corresponding antennas of the cellular and Wi-Fi / BT frequency bands; in a Wi-Fi HPM scenario, DSI2 is enabled, and the preset MTPL power of DSI2 is set to the corresponding antennas of the Wi-Fi and cellular frequency bands; in a BT HPM scenario, DSI3 is enabled, and the preset MTPL power of DSI3 is set to the corresponding antennas of the Wi-Fi and cellular frequency bands.

[0131] For example, such as Figure 7 As shown, in a single-cell scenario, the current terminal is registered in the N41 frequency band, with TX / PRX ANT0 and TX1:ANT6. The current N41 RSRP is -110dBm and the TX power is 25dBm. Using the power control method proposed in this application, the MTPL of DSI5 is selected, which is 25-15+3=13dBm. To achieve SAR compliance, the TX of cellular N41 ANT0 and 6 is limited to 13dBm.

[0132] For example, such as Figure 8As shown, in the Wi-Fi HPM scenario, the cellular registration N41 RSRP is -105, SNR is 15, and ANT0,6 loads the default DSI4 with a TX MTPL of 25-18+3 = 10dBm; the Wi-Fi 5G RSSI is -76, and the default DSI4 ANT5 TXMTPL is 21-4.6 = 16.4dBm. Due to the weak Wi-Fi signal, the low TX power causes effective stuttering. By using the power control method proposed in this application embodiment, the Wi-Fi HPM loads DSI2, switching the DSI of Wi-Fi 5G ANT5 to DSI2, thereby increasing the MTPL to 21dBm, improving the uplink TX power, and optimizing the effective performance.

[0133] For example, such as Figure 9 As shown, in the BT HPM scenario, the cell is registered with N41 ANT0,6, and the maximum TX transmit power is 25-18+3=10dBm. The default loaded DSI4 BT TX MTPL=27-8.5=18.5dBm. Through the power control method proposed in this application embodiment, after selecting DSI3, the TX MTPL value is 27 because no power back-off is required, which effectively improves the BT transmit power and reduces the music stuttering problem.

[0134] In summary, the power control method proposed in this application effectively identifies whether the cellular network and Wi-Fi / BT are enabled, as well as the values ​​of cellular RSRP / SNR and Wi-Fi / BT RSSI. It selects the Wi-Fi / BT HPM mode to switch to a mode that prevents or reduces the power reduction of Wi-Fi / BT, thereby increasing TX MTPL. This effectively improves the transmission power of Wi-Fi / BT under weak signal conditions, ensuring the TX power of the cellular network while improving the uplink user experience of Wi-Fi / BT.

[0135] This application provides a power control method that determines operating parameters and, based on these parameters, determines a target scenario type. The target scenario type includes at least one or more of the following: a non-call scenario; a call scenario; a network high-power mode scenario; and a Bluetooth high-power mode scenario. The method involves obtaining fallback parameters corresponding to the target scenario type and performing power control processing based on these fallback parameters. Therefore, in this application, the target scenario type can be determined through real-time monitoring of operating parameters. This target scenario type can include both call and non-call scenarios, as well as various scenarios such as network and Bluetooth high-power mode scenarios. Then, fallback parameters corresponding to the target scenario type can be obtained, and power control processing can be performed based on these fallback parameters. In other words, this application can subdivide scenarios based on real-time determined operating conditions and set fallback parameters corresponding to multiple scenarios. This allows for power control using fallback parameters applicable to various scenarios, effectively improving the TX performance of Wi-Fi / BT under weak signal conditions and ensuring optimal communication performance while meeting SAR compliance requirements.

[0136] Based on the above embodiments, another embodiment of this application proposes a power control method that can identify the target scene type and load corresponding backoff parameters according to the real-time monitored operating parameters, and dynamically adjust the maximum transmission power limit (MTPL) of wireless communication.

[0137] The power control method provided in the embodiments of this application can be executed by an electronic device, which can be an AP and a Modem in a terminal device. That is, the power control method in each embodiment of this application can be executed by an AP, or by a Modem, or can be executed interactively between the AP and the Modem.

[0138] The power control method provided in this application determines operating parameters and, based on these parameters, determines a target scenario type. The target scenario type includes at least one or more of the following: a non-call scenario type; a call scenario type; a network high-power mode scenario type; and a Bluetooth high-power mode scenario type. The method obtains fallback parameters corresponding to the target scenario type and performs power control processing based on these fallback parameters. This not only ensures SAR compliance but also improves the transmission performance of Wi-Fi / BT under weak signal conditions, while also taking into account the TX capability of cellular communication.

[0139] For example, in some embodiments, the operating parameters include, but are not limited to, parameters such as RSRP and SNR of cellular signals and RSSI of Wi-Fi / BT signals in actual implementation.

[0140] For example, when a user is making a video call on their mobile phone, if the cellular signal RSRP is detected to be -85dBm and the SNR is 20dB, and Wi-Fi is not enabled, then the user is determined to be in a call scenario. For example, if a user connects to a Wi-Fi hotspot but the signal is weak, and the system detects that the Wi-Fi RSSI is -76dBm and the cellular signal is strong, it may enter the network high-power mode scenario.

[0141] In some embodiments, the identification of the target scenario type plays a decisive role in the selection of subsequent power control strategies. Different target scenario types correspond to different backoff parameters, thereby ensuring SAR compliance while optimizing communication performance. For example, in a call scenario, the system prioritizes cellular communication power, while in a Wi-Fi high-power mode scenario, the system allows the Wi-Fi module to increase its transmission power to improve transmission quality under weak signal conditions.

[0142] In some embodiments, the fallback parameter refers to the power limit value that each wireless module (such as cellular, Wi-Fi, BT) should adhere to under a specific target scenario type. The fallback parameter is pre-configured, and different fallback parameter values ​​are set in conjunction with different DSIs (target scenario types).

[0143] For example, in the DSI4 target scenario type, the maximum transmission power limit (MTPL) of the Wi-Fi module's wireless communication may be 16.4 dBm; while in the DSI2 (Wi-Fi high power mode scenario type) target scenario type, the maximum transmission power limit (MTPL) of the Wi-Fi module's wireless communication may be increased to 21 dBm.

[0144] In some embodiments, the backoff parameters directly affect the setting of the final maximum transmission power limit (MTPL) for wireless communication. By presetting different backoff parameters for different target scenario types, dynamic adjustment of the wireless module's transmit power can be achieved while ensuring SAR compliance, thereby improving overall communication efficiency.

[0145] In some embodiments, the maximum transmission power limit (MTPL) for wireless communication is typically calculated as the original maximum power minus the fallback parameter value. For example, if the original maximum power of a Wi-Fi module is 21 dBm, and a fallback parameter of 4.6 dB is set under the DSI4 target scenario type, then the MTPL for wireless communication of the Wi-Fi module is 16.4 dBm; while under the DSI2 target scenario type, if the fallback parameter of the Wi-Fi module is set to 0 dB, then the MTPL for wireless communication of the Wi-Fi module is 21 dBm. Similarly, for communication modules, the MTPL for wireless communication of the communication module will also be dynamically adjusted according to the target scenario type and the fallback parameter.

[0146] In some embodiments, by setting back parameters, the transmission power of the wireless module can be flexibly adjusted under different target scenario types. This ensures that SAR complies with relevant regulations and standards, and improves the communication capabilities of Wi-Fi / BT in weak signal environments, ultimately achieving significant optimization of communication performance.

[0147] The power control method provided in this application, compared with the related technology which only considers the two scenarios of earpiece being on and off, adds more usage scenarios (application scenarios) to optimize the power usage of Wi-Fi / BT (such as the high power mode of Wi-Fi and BT).

[0148] In some embodiments, for high-power Wi-Fi scenarios (network high-power scenario type), power adjustment and control can be achieved through the following solutions: 1.1 Scene detection: When it is found that the Wi-Fi RSSI is under weak signal conditions, such as RSSI < -75 (first threshold, the first threshold is an empirical value and can be adjusted according to the project), and the cellular network is under strong signal conditions, such as RSRP > -110 (second threshold, the second threshold is an empirical value and can be adjusted according to the project) and SNR > 10 (third threshold, the third threshold is an empirical value and can be adjusted according to the project), a broadcast oplus.wifi.stsar.action.SETHPM is sent to configure Wi-Fi to enter HPM; 1.2 When the notification broadcast is received, if the value brought down by the broadcast is 1, then it is necessary to set the DSI corresponding to Wi-Fi HPM, such as DSI2; 1.3 Obtain the pre-set joint SAR backoff parameters. For example, in the DSI2 scenario, if the Wi-Fi TX power is increased, the SAR backoff needs to be reduced. 1.4 The modem receives the DSI scene value sent by the AP, such as DSI2, and sets the MTPL corresponding to DSI2 to the maximum power of Wi-Fi. This Wi-Fi power is greater than the power of the normal DSI4, thus ensuring that the Wi-Fi power is greater under weak Wi-Fi signal and strong cellular signal conditions.

[0149] In some embodiments, for high-power scenarios of BT (Bluetooth high-power scenario type), power adjustment and control can be achieved through the following solutions: 2.1 Scene detection: When it is found that the BT RSSI is under weak signal conditions, such as RSSI<-75 (the third threshold, which is an empirical value and can be adjusted according to the project), and the cell is under strong signal conditions, such as RSRP>-110 (the second threshold, which is an empirical value and can be adjusted according to the project) and SNR>10 (the third threshold, which is an empirical value and can be adjusted according to the project), a broadcast oplus.bt.stsar.action.SETHPM is sent to set the BT to enter HPM; 2.2 When the notification broadcast is received, if the value brought down by the broadcast is 1, it is necessary to set the DSI corresponding to BTHPM, such as DSI3; 2.3 Obtain the pre-set joint SAR backoff parameters. For example, for the DSI3 scenario, if the BTTX power is increased, the SAR backoff needs to be reduced. 2.4 The Modem receives the DSI scene value sent by the AP, such as DSI3, and sets the MTPL corresponding to DSI3 to the maximum power of BT. This BT power is greater than the power of normal DSI4, thus ensuring that the BT power is greater when the BT signal is weak or the cellular signal is strong.

[0150] In some embodiments, for call scenario types, i.e., when the scenario corresponding to the earpiece being turned on is DSI5, the Wi-Fi / BT power can be rolled back normally to ensure the cellular TX power.

[0151] In some embodiments, for non-call scenarios, i.e., when the earpiece is determined to be off, the corresponding scenario is DSI4, the Wi-Fi / BT power can be rolled back normally to ensure the cellular TX power.

[0152] like Figure 10As shown in this application, the DSI scenario settings for cellular / Wi-Fi / BT are illustrated. Specifically, for RF test scenarios in single-transmission / multi-transmission scenarios, the core focus is on the power performance of the SAR sensor and receiver states under different test scenarios (WLAN, BT, NR-ULNRAD) and antenna groups (Antenna Group 0, Antenna Group 1, Antenna Group 2). The specific structure and meaning are as follows: 1. Table header and grouping logic Single-transmit / multi-transmit scenario: Define the radio frequency transmission mode (single-transmit or multi-transmit, i.e., a single radio frequency link or multiple links transmitting simultaneously).

[0153] RF test scenario: Focusing on the transmission and reception characteristics of RF signals, power distribution needs to be analyzed in conjunction with the "SAR test scenario".

[0154] State ID: A unique identifier for the test scenario, used to distinguish different test conditions.

[0155] Receiver status: The operating status of the receiver, reflecting the power characteristics of the radio frequency signal receiving stage.

[0156] SAR sensor status: The operating status of the SAR sensor, used to monitor the absorption of radio frequency radiation by the human body. Its power performance is directly related to the compliance of SAR testing.

[0157] 2. Test Scenario and Power Data The system is categorized into three major radio frequency scenarios: WLAN, BT, and NR-ULNRAD. Within each scenario, the power values ​​(usually in dBm) are displayed as Antenna Group 0, Antenna Group 1, and Antenna Group 2.

[0158] WLAN scenario: State numbers 13, 10, 13.10, 14, 15, and 14.15 correspond to different test conditions. Power values ​​(such as 21.0, 0.0, 0.5, etc.) reflect the transmit / receive power distribution of WLAN RF under each antenna group.

[0159] BT scenario: State numbers 13, 10, and 1 correspond to Bluetooth RF tests, and power values ​​(such as 27.0, 8.5, 20.0, etc.) reflect the power performance of Bluetooth under each antenna group.

[0160] NR-ULNRAD scenario: state numbers 41, 0.6, 0.7, and 5.7 correspond to 5G uplink (NR-UL) or specific RF tests. Power values ​​(such as 25.0, 18.0, 15.0, etc.) reflect the power characteristics of 5G uplink RF under each antenna group.

[0161] Therefore, this application effectively ensures the user experience of Wi-Fi / BT under weak signal conditions by increasing the TX power. For example, the Wi-Fi enhancement solution can be applied to concert scenarios, allowing a mobile phone to provide a Wi-Fi hotspot for another mobile phone. The BT enhancement solution can be applied when a user's mobile phone is placed in a locker and the user is moving around in the gym; the BT enhancement solution can also be applied to playing music via Bluetooth in places with severe interference, such as airports and high-speed rail stations.

[0162] like Figure 11 As shown in the embodiments of this application, the power control method can be applied to a power control system, which may include a monitoring module, a data module, and a processing module. The specific working content and collaborative process of each module are as follows: (1) Monitoring module: The monitoring module monitors the frequency band information and RSRP of the terminal's cellular network in real time, and then determines whether the earpiece is currently on; at the same time, it determines whether Wi-Fi / BT is enabled. If enabled, it reads the RSSI of Wi-Fi / BT and feeds back different status information to the processing module for corresponding processing.

[0163] (2) Data module: The data module stores the pre-set DSI and corresponding backoff power, that is, it stores the pre-set mapping relationship between the scene and the backoff parameters.

[0164] The mapping relationship between scenarios and fallback parameters may include, but is not limited to: DSI2 of Wi-Fi HPM and power fallback for various standards and frequency bands; DSI3 of BT HPM and power fallback for various standards and frequency bands; DSI and corresponding fallback power for scenarios where the handset is off during a call; and DSI and corresponding fallback power for scenarios where the handset is on during a call.

[0165] (3) Processing module: The processing module receives data from the detection module and uses the data in the data module to set the corresponding MTPL.

[0166] When it is detected that Wi-Fi HPM mode needs to be set, the corresponding DSI for Wi-Fi HPM is invoked, and the MTPL for the corresponding standard, frequency band, and antenna is enabled. When it is detected that BT HPM mode needs to be set, the corresponding DSI for BT HPM is invoked, and the MTPL for the corresponding standard, frequency band, and antenna is enabled. When it is detected that the earpiece is turned on, the earpiece's DSI and the corresponding MTPL for the corresponding standard, frequency band, and antenna are enabled. The remaining scenario is when the earpiece is turned off and Wi-Fi / BT HPM mode is not entered, in which case the DSI for the normal earpiece-off mode and the corresponding MTPL for the corresponding standard, frequency band, and antenna are enabled.

[0167] The power control method provided in this application identifies whether a Wi-Fi / BT HPM scene has been entered, loads the corresponding DSI and MTPL values ​​for the scene, ensures the TX performance of Wi-Fi / BT under weak signal conditions, and also takes into account the TX performance of cellular devices. This ensures the TX performance of both cellular and Wi-Fi / BT devices, improves the TX transmission performance of Wi-Fi / BT devices under weak signal conditions, avoids uplink transmission anomalies caused by power limitation, and also ensures the TX performance of cellular devices in call scenarios and under weak cellular signal conditions, providing users with a high-quality communication experience.

[0168] like Figure 12 As shown, the power control method provided in this application embodiment may include the following steps: Step 1201: Real-time detection of terminal status.

[0169] Step 1202: Determine if it is a call scenario. If yes, proceed to step 1203; otherwise, proceed to step 1204.

[0170] Step 1203: Load the MTPL corresponding to the call scenario. For example, enable call scenario DSI5 and load the MTPL corresponding to DSI5.

[0171] Step 1204: Determine if Wi-Fi is turned on. If yes, proceed to step 1205; otherwise, proceed to step 1208.

[0172] Step 1205: Determine if the Wi-Fi high-power scenario is met? If yes, proceed to step 1206; otherwise, proceed to step 1208.

[0173] In some embodiments, if (Wi-Fi RSSI < -75) && (Cellular RSRP > -110 || SNR > 10) are simultaneously satisfied, then the Wi-Fi high-power scenario is determined to be satisfied.

[0174] Step 1206: Send WIFI HPM broadcast.

[0175] Step 1207: Load the MTPL corresponding to the high-power Wi-Fi scenario. For example, enable DSI2 and load the MTPL corresponding to DSI2.

[0176] Step 1208: Determine if BT is open. If yes, proceed to step 1209; otherwise, proceed to step 1212.

[0177] Step 1209: Determine if the BT high-power scenario is met? If yes, proceed to step 1210; otherwise, proceed to step 1212.

[0178] In some embodiments, if (BT RSSI < -75) && (cellular RSRP > -110 || SNR > 10) are satisfied simultaneously, then the BT high-power scenario is determined to be satisfied.

[0179] Step 1210: Send BT HPM broadcast.

[0180] Step 1211: Load the MTPL corresponding to the BT high-power scenario. For example, enable DSI3 and load the MTPL corresponding to DSI3.

[0181] Step 1212: Load the MTPL corresponding to other scenarios. For example, enable DSI4 and load the MTPL corresponding to DSI4.

[0182] In some embodiments, the status of the terminal's cellular network, Wi-Fi / BT is detected in real time, and corresponding processing is performed.

[0183] In some embodiments, if it is detected that the current situation is a call scenario, i.e., a handset-on scenario, then the DSI5 of the scenario and the MTPL value of the corresponding frequency band of the cell are loaded. In some embodiments, if Wi-Fi is detected to be currently enabled and the conditions (Wi-Fi RSSI < -75) && (Cellular RSRP > -110 || SNR > 10) are met, it indicates that the current Wi-Fi signal is weak and the cellular signal is strong. Wi-FiHPM processing needs to be started and the MTPL corresponding to DSI2 needs to be loaded.

[0184] In some embodiments, if it is detected that BT is currently enabled and (BT RSSI<-75)&&(Cellular RSRP>-110 || SNR>10) are satisfied, it indicates that the current signal is weak BT signal and strong cellular signal, and BT HPM processing needs to be started to load the MTPL corresponding to DSI3.

[0185] In some embodiments, the remaining scenario is the default case where the earpiece is turned off, and the MTPL corresponding to DSI4 is loaded.

[0186] In other words, this application can determine whether the current situation is a call scenario. If it is a call scenario, the TX communication performance of the cellular network needs to be guaranteed. If it is a Wi-Fi / BT HPM scenario, the Wi-Fi / BT TX needs to be at a higher transmission power to ensure the TX performance of Wi-Fi / BT under weak signal conditions. The application provides cellular and Wi-Fi / BT with more suitable TX power for specific scenarios, effectively providing users with a better user experience.

[0187] The power control method proposed in this application can be implemented in one way: real-time monitoring of whether the terminal's cellular and Wi-Fi / BT are enabled and the corresponding RSRP / RSSI / SNR, thereby adopting the MTPL of the corresponding DSI to ensure that the cellular and Wi-Fi / BT use a better MTPL. For example, in a single-cellular scenario, if the cellular is in a call state, then call scenario DSI5 is enabled, and the cellular uses a higher MTPL; in a Wi-Fi HPM scenario, DSI2 is enabled, and the MTPL power preset by DSI2 is set to the corresponding antennas of the Wi-Fi and cellular frequency bands; in a BT HPM scenario, DSI3 is enabled, and the MTPL power preset by DSI3 is set to the corresponding antennas of the Wi-Fi and cellular frequency bands; in the remaining scenarios, DSI4 is enabled, and the MTPL power preset by DSI4 is set to the corresponding antennas of the cellular and Wi-Fi / BT frequency bands.

[0188] Another implementation of the power control method proposed in this application is as follows: Real-time monitoring of whether the terminal's cellular and Wi-Fi / BT are enabled and their corresponding RSRP / RSSI / SNR, thereby adopting the MTPL of the corresponding DSI to ensure that the cellular and Wi-Fi / BT use a better MTPL. For example, in a single-cellular scenario, if the cellular is in a call state, then call scenario DSI5 is enabled, and the cellular uses a higher MTPL; if it is in a non-call state, and Wi-Fi and BT are not enabled (i.e., a non-call scenario), then call scenario DSI4 is enabled, and the preset MTPL power of DSI4 is set to the corresponding antennas of the cellular and Wi-Fi / BT frequency bands; in a Wi-Fi HPM scenario, DSI2 is enabled, and the preset MTPL power of DSI2 is set to the corresponding antennas of the Wi-Fi and cellular frequency bands; in a BT HPM scenario, DSI3 is enabled, and the preset MTPL power of DSI3 is set to the corresponding antennas of the Wi-Fi and cellular frequency bands.

[0189] For example, such as Figure 7 As shown, in a single-cell scenario, the current terminal is registered in the N41 frequency band, with TX / PRX ANT0 and TX1:ANT6. The current N41 RSRP is -110dBm and the TX power is 25dBm. Using the power control method proposed in this application, the MTPL of DSI5 is selected, which is 25-15+3=13dBm. To achieve SAR compliance, the TX of cellular N41 ANT0 and 6 is limited to 13dBm.

[0190] For example, such as Figure 8As shown, in the Wi-Fi HPM scenario, the cellular registration N41 RSRP is -105, SNR is 15, and ANT0,6 loads the default DSI4 with a TX MTPL of 25-18+3 = 10dBm; the Wi-Fi 5G RSSI is -76, and the default DSI4 ANT5 TXMTPL is 21-4.6 = 16.4dBm. Due to the weak Wi-Fi signal, the low TX power causes effective stuttering. By using the power control method proposed in this application embodiment, the Wi-Fi HPM loads DSI2, switching the DSI of Wi-Fi 5G ANT5 to DSI2, thereby increasing the MTPL to 21dBm, improving the uplink TX power, and optimizing the effective performance.

[0191] For example, such as Figure 9 As shown, in the BT HPM scenario, the cell is registered with N41 ANT0,6, and the maximum TX transmit power is 25-18+3=10dBm. The default loaded DSI4 BT TX MTPL=27-8.5=18.5dBm. Through the power control method proposed in this application embodiment, after selecting DSI3, the TX MTPL value is 27 because no power back-off is required, which effectively improves the BT transmit power and reduces the music stuttering problem.

[0192] In summary, the power control method proposed in this application effectively identifies whether the cellular network and Wi-Fi / BT are enabled, as well as the values ​​of cellular RSRP / SNR and Wi-Fi / BT RSSI. It selects the Wi-Fi / BT HPM mode to switch to a mode that prevents or reduces the power reduction of Wi-Fi / BT, thereby increasing TX MTPL. This effectively improves the transmission power of Wi-Fi / BT under weak signal conditions, ensuring the TX power of the cellular network while improving the uplink user experience of Wi-Fi / BT.

[0193] The power control method proposed in this application is a joint SAR scheme that further subdivides the scenario to provide a higher TX MTPL for weak Wi-Fi / BT signals, thereby ensuring the performance of Wi-Fi / BT.

[0194] The specific implementation of the segmented scenario schemes proposed in the embodiments of this application is not specifically limited. For example, it is also possible to achieve the purpose of segmenting the platform for non-joint SAR schemes, such as adding joint DSI of cellular + WIFI + BT.

[0195] This application provides a power control method that determines the corresponding target scenario type through real-time monitoring of operating parameters. This target scenario type can include various scenarios such as call and non-call scenarios, as well as network and Bluetooth high-power mode scenarios. Then, fallback parameters corresponding to the target scenario type can be obtained, and power control processing can be performed based on these fallback parameters. In other words, this application can subdivide scenarios based on real-time determined operating conditions and set fallback parameters corresponding to multiple scenarios. This allows for power control tailored to different scenarios using fallback parameters applicable to various scenarios. This approach can effectively improve the TX performance of Wi-Fi / BT under weak signal conditions, ensuring optimal communication performance while meeting SAR compliance requirements.

[0196] Based on the above embodiments, in another embodiment of this application... Figure 13 This is a schematic diagram of the composition structure of the power control device proposed in the embodiments of this application, as shown below. Figure 13 As shown, the power control device 110 proposed in this application embodiment may include: The determining unit 1101 is used to determine operating parameters and determine the target scenario type based on the operating parameters; wherein the target scenario type includes at least one or more of the following: non-call scenario type; call scenario type; network high-power mode scenario type; Bluetooth high-power mode scenario type; The acquisition unit 1102 is used to acquire the rollback parameters corresponding to the target scene type; The determining unit 1101 is also used to determine the MTPL of wireless communication based on the backoff parameters.

[0197] In the embodiments of this application, further, Figure 14 This is a schematic diagram of the composition structure of the electronic device proposed in the embodiments of this application, such as... Figure 14 As shown, the electronic device 120 proposed in this application embodiment may include a processor 1201, a memory 1202, a communication interface 1203, and a bus 1204 for connecting the processor 1201, the memory 1202 and the communication interface 1203.

[0198] In the embodiments of this application, the processor 1201 can be at least one of the following: Application-Specific Integrated Circuit (ASIC), Digital Signal Processor (DSP), Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), Field-Programmable Gate Array (FPGA), Central Processing Unit (CPU), Controller, Microcontroller, and Microprocessor. It is understood that for different devices, the electronic device used to implement the above-mentioned processor function can also be other types, and this application embodiment does not specifically limit this. The electronic device 120 may also include a memory 1202, which can be connected to the processor 1201. The memory 1202 is used to store executable program code, which includes computer operation instructions. The memory 1202 may include high-speed RAM memory and may also include non-volatile memory, such as at least two disk drives.

[0199] In embodiments of this application, bus 1204 is used to connect communication interface 1203, processor 1201, and memory 1202, as well as the mutual communication between these devices.

[0200] In practical applications, the aforementioned memory 1202 can be volatile memory, such as random-access memory (RAM); or non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid-state drive (SSD); or a combination of the above types of memory, and provide instructions and data to the processor 1201.

[0201] Furthermore, in the embodiments of this application, the processor 1201 is used to determine operating parameters and determine a target scenario type based on the operating parameters; wherein, the target scenario type includes at least one or more of the following: non-call scenario type; call scenario type; network high-power mode scenario type; Bluetooth high-power mode scenario type; obtain fallback parameters corresponding to the target scenario type; and perform power control processing based on the fallback parameters.

[0202] Furthermore, in the embodiments of this application, the functional modules can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional module.

[0203] If the integrated unit is implemented as a software functional module and is not sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this embodiment, in essence, or the part that contributes to related technologies, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the method of this embodiment. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0204] This application provides a computer-readable storage medium having a program stored thereon, which, when executed by a processor, implements the power control method described above.

[0205] Specifically, the program instructions corresponding to a power control method in this embodiment can be stored on storage media such as optical discs, hard disks, and USB flash drives. When the program instructions corresponding to a power control method in the storage media are read or executed by an electronic device, the following steps are included: Determine the operating parameters, and determine the target scenario type based on the operating parameters; wherein the target scenario type includes at least one or more of the following: non-call scenario type; call scenario type; network high-power mode scenario type; Bluetooth high-power mode scenario type; Obtain the fallback parameters corresponding to the target scene type; Power control is performed based on backoff parameters.

[0206] This application also provides a computer program product.

[0207] In some embodiments, the computer program product may include a computer program or instructions.

[0208] In some embodiments, the computer program product can be applied to the computer device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the computer device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0209] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of hardware embodiments, software embodiments, or embodiments combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

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

[0211] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in the implementation flow diagram. Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0212] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0213] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application.

Claims

1. A power control method, characterized in that, The method includes: Determine the operating parameters, and determine the target scenario type based on the operating parameters; wherein the target scenario type includes at least one or more of the following: non-call scenario type; call scenario type; network high-power mode scenario type; Bluetooth high-power mode scenario type; Obtain the fallback parameters corresponding to the target scene type; Power control processing is performed based on the backoff parameters.

2. The method according to claim 1, characterized in that, The determination of operating parameters includes: The preset functional modules are monitored in real time to obtain the operating parameters; in, The preset functional modules include at least one or more of the following: earpiece module; communication module; network module; Bluetooth module; The operating parameters include at least one or more of the following: The status parameters of the earpiece module; The signal-to-noise ratio (SNR) of the communication module; The reference signal received power RSRP of the communication module; The received signal strength indicator (RSSI) of the network module; The RSSI of the Bluetooth module.

3. The method according to claim 2, characterized in that, Determining the target scene type based on the operating parameters includes: When the status parameters of the earpiece module indicate that the earpiece is on, the target scenario type is determined to be the call scenario type; or, When the status parameter of the earpiece module indicates that the earpiece is off, the target scenario type is determined to be the non-call scenario type.

4. The method according to claim 2, characterized in that, Determining the target scene type based on the operating parameters includes: If the RSSI of the network module is less than a first threshold, and the RSRP of the communication module is greater than a second threshold and the SNR of the communication module is greater than a third threshold, then the target scenario type is determined to be the network high-power mode scenario type.

5. The method according to claim 2, characterized in that, Determining the target scene type based on the operating parameters includes: If the RSSI of the Bluetooth module is less than the fourth threshold, and the RSRP of the communication module is greater than the second threshold and the SNR of the communication module is greater than the third threshold, then the target scenario type is determined to be the Bluetooth high-power mode scenario type.

6. The method according to any one of claims 2-5, characterized in that, The step of obtaining the fallback parameters corresponding to the target scene type includes: Based on the pre-set mapping relationship between scenarios and fallback parameters, determine the fallback parameters corresponding to the target scenario type; in, The fallback parameters corresponding to the non-call scenario type include at least the first maximum transmission power limit (MTPL). The fallback parameters corresponding to the call scenario type include at least the second MTPL; The fallback parameters corresponding to the network high-power mode scenario type include at least the third MTPL of the communication module and / or the fourth MTPL of the network module; The fallback parameters corresponding to the Bluetooth high power mode scenario type include at least the fifth MTPL of the communication module and / or the sixth MTPL of the Bluetooth module.

7. The method according to claim 6, characterized in that, The power control processing based on the backoff parameters includes: In the non-call scenario, the communication module is power controlled according to the first MTPL; and / or, In the aforementioned call scenario type, power control of the communication module is performed according to the second MTPL; and / or, In the network high-power mode scenario, the communication module is power controlled according to the third MTPL, and / or the network module is power controlled according to the fourth MTPL; In the Bluetooth high-power mode scenario, the communication module is power controlled according to the fifth MTPL, and / or the Bluetooth module is power controlled according to the sixth MTPL.

8. A power control device, characterized in that, The power control device includes: A determining unit is configured to determine operating parameters and, based on the operating parameters, determine a target scenario type; wherein the target scenario type includes at least one or more of the following: non-call scenario type; call scenario type; network high-power mode scenario type; Bluetooth high-power mode scenario type; The acquisition unit is used to acquire the rollback parameters corresponding to the target scene type; The determining unit is also used to determine the MTPL of wireless communication based on the backoff parameters.

9. An electronic device, characterized in that, The electronic device includes a processor and a memory storing processor-executable instructions, which, when executed by the processor, implement the method as described in any one of claims 1-7.

10. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or the instructions are executed by the processor, the method of any one of claims 1-7 is implemented.

Images