Control methods, devices, equipment, chips, media and software products

By configuring information to determine the control strategy for target events, the rate and level of log generation can be flexibly controlled, which solves the problems of response lag and task timeout caused by insufficient terminal device resources and achieves efficient resource utilization.

CN123114886APending Publication Date: 2026-11-17BEIJING X RING TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611256888.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-18
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

During operation, terminal devices have limited resources and cannot withstand the continuous overhead of writing operation logs, resulting in response lag and task processing timeouts.

Method used

By configuring information to determine the control strategy corresponding to the target event, the generation rate and level of the runtime log can be flexibly controlled to avoid unnecessary memory consumption.

Benefits of technology

Effective management of operation log generation avoids resource waste and ensures the normal operation of terminal devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123114886A_ABST
    Figure CN123114886A_ABST
Patent Text Reader

Abstract

This disclosure provides a control method, apparatus, device, chip, medium, and program product, relating to the field of chip control technology. In this method, in response to a target event triggered by a target object, a target control strategy corresponding to the target event is determined. The target control strategy is used to instruct and restrict the target object from generating target type operation logs. The target object is controlled according to the target control strategy to adapt to the dynamic changes in the target object's operating scenario, save the target object's memory resources, and avoid situations such as response lag and task processing timeouts.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of chip control technology, and in particular to a control method, apparatus, device, chip, medium, and program product. Background Technology

[0002] Terminal devices generate corresponding operation logs during operation. However, due to the limited internal resources of terminal devices (such as storage and computing resources), they are usually unable to withstand the continuous writing overhead of operation logs, which may cause terminal devices to experience lag, task processing timeouts, and other issues. Summary of the Invention

[0003] To overcome the problems existing in related technologies, this disclosure provides a control method, apparatus, device, chip, medium, and program product.

[0004] According to a first aspect of the present disclosure, a control method is provided, comprising: in response to a target object triggering a target event, determining a target control policy corresponding to the target event; the target control policy being used to instruct the target object to restrict the generation of runtime logs of a target type; and controlling the target object according to the target control policy.

[0005] As can be seen, the embodiments of this disclosure can execute the target control strategy corresponding to the target event when the target object triggers the target event, so as to adapt to the dynamic changes of the target object's running scenario. Furthermore, since the target control strategy is used to instruct and restrict the target object from generating target-type running logs, it can save the target object's memory resources and avoid situations such as response lag and task processing timeouts.

[0006] According to a first aspect of this disclosure, in some embodiments, determining a target control strategy corresponding to a target event includes: Based on the configuration information, determine the target control policy corresponding to the target event; the configuration information includes the correspondence between events and control policies.

[0007] As can be seen, since the configuration information includes the correspondence between events and control strategies, the embodiments of this disclosure can determine the target control strategy corresponding to the target event through the configuration information. Thus, when the target object triggers different events, different control strategies can be adopted to adapt to the dynamic changes in the target object's operating scenario.

[0008] According to a first aspect of this disclosure, in some embodiments, the configuration information further includes a correspondence between events and event triggering conditions; the control method provided in the embodiments of this disclosure further includes: obtaining the running log of a target object; and, according to the configuration information, determining that the target object triggers a target event corresponding to the target triggering condition in response to the running log of the target object satisfying the target triggering condition.

[0009] As can be seen, since the configuration information also includes the correspondence between events and event triggering conditions, the embodiments of this disclosure can automatically identify whether the target object triggers the target event based on the configuration information and the running log, laying the foundation for subsequently determining the target control strategy corresponding to the target event.

[0010] According to a first aspect of this disclosure, in some embodiments, the target triggering condition includes at least one of the following: the target object's running log includes a preset sequence of log events; the running parameter information included in the target object's running log satisfies the preset parameter condition.

[0011] As can be seen, the embodiments disclosed herein provide specific criteria for determining whether the running log triggers the target triggering condition.

[0012] According to a first aspect of this disclosure, in some embodiments, the target control strategy includes the log level of the target type's runtime log under the target event; controlling the target object according to the target control strategy includes: Based on the log level, the generation rate of runtime logs for the target object of the target type is controlled.

[0013] As can be seen, the embodiments of this disclosure can control the generation rate of runtime logs based on log levels. Furthermore, the log level corresponding to the same runtime log can be different under different events; therefore, the same runtime log can correspond to different generation rates under different events. This allows for differentiated control of the runtime log generation rate based on events, making the management and control of runtime logs more flexible and precise.

[0014] According to a first aspect of this disclosure, in some embodiments, the generation rate of runtime logs of a target type generated by a target object is controlled according to the log level, including: in response to a preset relationship between the log level and a preset log level, controlling the target object to stop generating runtime logs of the target type.

[0015] As can be seen, the embodiments of this disclosure can control the target object to stop generating target type runtime logs when the log level and the preset log level meet the preset relationship. In this way, unnecessary memory occupation of the target object can be avoided, and runtime logs corresponding to log levels outside the preset relationship can still be generated normally.

[0016] According to a first aspect of this disclosure, in some embodiments, controlling the generation rate of runtime logs of a target type generated by a target object based on the log level includes: determining a target generation rate corresponding to the log level; and controlling the generation rate of runtime logs of the target type generated by the target object to be less than or equal to the target generation rate.

[0017] As can be seen, the embodiments of this disclosure can perform differentiated rate control on operation logs of different log levels, thereby achieving flexible control over the generation of operation logs.

[0018] According to a first aspect of this disclosure, in some embodiments, the method further includes: generating configuration information, or receiving configuration information sent by a configuration device.

[0019] As can be seen, the embodiments of this disclosure can obtain configuration information in a variety of ways, providing a data foundation for subsequently determining the target control strategy corresponding to the target event based on the configuration information.

[0020] According to a first aspect of this disclosure, in some embodiments, generating configuration information includes: obtaining historical operation logs; the historical operation logs are operation logs generated by the target object in a historical time period; determining a first time period based on the historical operation logs; the first time period is a time period in which the target object's generation rate of historical operation logs is greater than or equal to the upper limit of the generation rate; determining a second time period based on the first time period; the end time of the second time period is earlier than or equal to the start time of the first time period; and generating configuration information based on the historical operation logs and the second time period.

[0021] As can be seen, the first time period in this embodiment is the period when the target object's historical log generation rate is abnormal, and the second time period determined based on the first time period is the period before the target object's historical log generation rate becomes abnormal. Therefore, the configuration information generated based on the historical log and the second time period can reflect the information included in the historical log before the generation rate became abnormal. In this way, when the target object runs subsequently, it can determine the target event to be triggered and execute the corresponding target control strategy based on the target trigger conditions in the configuration information matched with the log before the log generation rate becomes abnormal. This can save the target object's memory resources and avoid situations such as response lag and task processing timeouts.

[0022] According to a first aspect of this disclosure, in some embodiments, generating configuration information based on historical operation logs and a second time period includes: determining a target log event sequence based on at least one target log event, and generating configuration information based on the target log event sequence; the at least one target log event is a log event in the historical operation log corresponding to the second time period; and / or, generating configuration information based on target operation parameter information; the target operation parameter information is the operation parameter information of the target object included in the historical operation log within the second time period.

[0023] As can be seen, the embodiments of this disclosure can generate configuration information based on the target log event sequence and / or the target running parameter information. In this way, before the subsequent target object generates running logs at an abnormal rate, it can determine whether the target object has triggered a target event by detecting whether the running log includes the target log event sequence and / or whether the running parameter information meets the preset parameter conditions. This allows for the determination of whether to take appropriate control strategies for the target object, thereby saving the target object's memory resources and preventing situations such as response lag and task processing timeouts from occurring.

[0024] According to a second aspect of this disclosure, a control device is provided for performing the control method described in the first aspect and any one thereof.

[0025] According to a third aspect of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to execute the executable instructions to implement the control method described in the first aspect and any one thereof.

[0026] According to a fourth aspect of the present disclosure, a chip is provided, the chip including a processing unit and an interface circuit, the processing unit acquiring program instructions through the interface circuit, the program instructions being executed by the processing unit, the processing unit being used to execute the control method described in the first aspect and any one thereof.

[0027] According to a fifth aspect of the present disclosure, a non-transitory computer-readable storage medium is provided, which, when instructions in the storage medium are executed by a processor, enables the processor to perform the control method described in the first aspect and any one thereof.

[0028] According to a sixth aspect of the present disclosure, a computer program product is provided, including a computer program that, when executed by a processor, can implement the control method described in the first aspect and any one thereof.

[0029] It should be understood that the beneficial effects achieved by the control device described in the second aspect, the electronic device described in the third aspect, the chip described in the fourth aspect, the non-transitory computer-readable storage medium described in the fifth aspect, and the computer program product described in the sixth aspect can be referred to the beneficial effects of the first aspect and any of its embodiments, which will not be repeated here.

[0030] Furthermore, the above general description and the following detailed description are exemplary and explanatory only, and do not limit this disclosure. Attached Figure Description

[0031] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0032] Figure 1 This is a flowchart illustrating a control method according to some embodiments of the present disclosure; Figure 2 This is a schematic diagram illustrating a process for determining a target object and triggering a target event according to some embodiments of the present disclosure; Figure 3 This is a schematic diagram illustrating a process for generating configuration information according to some embodiments of the present disclosure; Figure 4 This is a schematic diagram illustrating the structure of a control device according to some embodiments of the present disclosure; Figure 5 This is a schematic diagram illustrating the structure of a control system according to some embodiments of the present disclosure; Figure 6 This is a block diagram illustrating an electronic device 600 according to some embodiments of the present disclosure; Figure 7 This is a block diagram illustrating a chip according to some embodiments of the present disclosure. Detailed Implementation

[0033] Some embodiments of this disclosure will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. Various changes, modifications, and equivalents of the methods and apparatus described herein will become apparent upon understanding this disclosure. For example, the order of operations described herein is merely illustrative and is not limited to those orders set forth herein, but can be changed as will become apparent upon understanding this disclosure, except for operations that must be performed in a particular order. Furthermore, for clarity and brevity, descriptions of features known in the art may be omitted.

[0034] The embodiments described in the following examples of this disclosure are not representative of all embodiments consistent with this disclosure. Rather, they are merely examples of methods and apparatus consistent with some aspects of this disclosure as detailed in the appended claims.

[0035] During operation, terminal devices generate corresponding operation logs. These logs record key behavioral trajectories, operating parameters, and various abnormal event information along the terminal device's operating timeline. They serve as data for performing operations such as function verification, system debugging, and fault location on the terminal device.

[0036] However, due to the limited internal resources of terminal devices (e.g., storage and computing resources), they often struggle to withstand the continuous high-intensity overhead of writing operation logs. For example, when a terminal device malfunctions or operates under high load, the amount of operation logs generated often explodes within a very short period. This sudden surge of logs can easily exhaust the already strained internal resources of the terminal device, leading to issues such as device lag and task timeouts. Therefore, effectively managing the generation of operation logs for terminal devices while ensuring their normal operation, in order to avoid excessive consumption of their internal resources, is a pressing issue that needs to be addressed.

[0037] In one related technology, developers can configure the on / off states of various operation log switches on the terminal device before it leaves the factory, based on their existing experience. Once the configuration takes effect, it will be permanently locked throughout the entire operational lifecycle of the terminal device. That is, regardless of whether the terminal device is in idle standby, high-load business processing, or abnormal emergency scenarios, the on / off states of various operation log switches will not be adjusted.

[0038] However, due to the extremely complex and unpredictable usage scenarios faced by terminal devices in actual operation, the types of operational logs that are truly valuable for reference may vary in different scenarios. Therefore, fixed switch configurations cannot adapt to the dynamic changes in the usage scenarios of terminal devices. For example, an operational log that is turned off in one usage scenario may be a key clue for locating intermittent faults in another usage scenario, and fixed switch configurations cannot dynamically respond to such changes. Furthermore, if too many operational log switches are turned on for the sake of conservatism, the terminal device will continuously generate a large number of redundant logs during daily steady-state operation, consuming the already limited internal resources of the terminal device and causing unnecessary resource overhead.

[0039] Figure 1 This is a flowchart illustrating a control method according to some embodiments of the present disclosure. The control method shown in the embodiments of the present disclosure can be applied to terminal devices with control functions. For example, portable computers (such as mobile phones), tablet computers, laptops, personal computers (PCs), wearable electronic devices (such as smartwatches), augmented reality (AR) / virtual reality (VR) devices, smart cockpits, in-vehicle computers (vehicle systems), smart vehicles (or smart cars), and other terminal devices with control functions. The embodiments of the present disclosure do not impose any special limitations on the specific form of the terminal device.

[0040] Furthermore, the control method shown in this disclosure can also be applied to chips with control functions, such as application processor (AP) chips. This disclosure does not impose any special limitations on the specific type of chip.

[0041] The control methods illustrated in some embodiments of this disclosure will be described in detail below, with terminal devices as the executing entity.

[0042] See also Figure 1 The control method provided in this embodiment may include the following steps S101-S102: S101: In response to a target event triggered by a target object, determine the target control strategy corresponding to the target event.

[0043] The target control strategy is used to instruct and restrict the target object from generating target type operation logs. The target object can be the terminal device itself, or a chip (e.g., a communication processor (CP) chip, etc.) or functional module in the terminal device used to generate operation logs, etc., which is not limited in the embodiments of this disclosure.

[0044] In some embodiments, configuration information may include a correspondence between events and event triggering conditions; see [link to documentation]. Figure 2 The terminal device can obtain the running log of the target object; based on the configuration information, in response to the running log of the target object meeting the target triggering condition, it determines that the target object triggers the target event corresponding to the target triggering condition.

[0045] The configuration information can be pre-stored in the terminal device or generated by an external configuration device and sent to the terminal device. This disclosure does not impose any special restrictions on this.

[0046] Specifically, the target object's runtime log can record key behavioral trajectories, runtime parameters, and various abnormal event information along the runtime timeline. After obtaining the target object's runtime log, the terminal device can analyze the log based on the configuration information to determine whether the log meets a certain event triggering condition defined in the configuration information. Since the configuration information defines the correspondence between event triggering conditions and events, when it is determined that the runtime log meets a certain event triggering condition, the terminal device can identify that event triggering condition as the target triggering condition and determine the event corresponding to the target triggering condition as the target event; that is, it is determined that the target object has triggered the target event.

[0047] If it is determined that a target object triggers a target event, the terminal device can further determine the target control policy corresponding to the target event. The target control policy is used to instruct the target object to restrict the generation of runtime logs of the target type.

[0048] If it is determined that the target object has not triggered the target event, the terminal device can continue to obtain the operation logs generated during the operation of the terminal device, and compare the operation logs with the configuration information to determine whether the target object has triggered the target event.

[0049] As can be seen, the terminal device can automatically identify whether the target object has triggered a target event based on the target object's runtime log. After confirming that the target object has triggered a target event, it further determines the target control strategy corresponding to the target event, providing a basis for subsequent control of the target object based on the target control strategy. Furthermore, since different events in the configuration information correspond to different event triggering conditions and different control strategies, when the target object triggers different events, the generation of the target object's runtime log can be controlled according to different control strategies, thereby adapting to the dynamic changes in the target object's runtime scenario.

[0050] In some embodiments, the target triggering condition includes at least one of the following: the target object's running log includes a preset sequence of log events; the running parameter information included in the target object's running log satisfies the preset parameter condition.

[0051] The preset log event sequence may include one or more log events arranged in the order of their generation.

[0052] Specifically, the target object can continuously generate log events during its operation, and the target object's runtime log can include these log events. Log events can reflect the specific actions or state changes that occurred to the target object at a certain moment.

[0053] When a terminal device obtains the running log of a target object, it can parse the running log, extract the various log events included therein, and determine whether there is an event sequence in the running log that matches a preset log event sequence based on the extracted log events.

[0054] For example, a preset log event sequence may include a first log event, a second log event, and a third log event, arranged sequentially according to their generation time. After obtaining the target object's runtime log, the terminal device can parse the runtime log, extract each log event included, and sort the extracted log events according to their generation time. If the extracted log events contain a first log event, a second log event, and a third log event appearing sequentially, and their order of appearance matches the order of the first, second, and third log events in the preset log event sequence, then the terminal device can determine that the target object's runtime log includes the preset log event sequence. If any one of the first, second, and third log events is missing from the extracted log events, or if the order of appearance of the first, second, and third log events does not match the order of the first, second, and third log events in the preset log event sequence, then the terminal device can determine that the target object's runtime log does not include the preset log event sequence.

[0055] Operational parameter information refers to various status parameters generated by the target object during operation. For example, operational parameter information may include hardware status parameters such as chip temperature, power consumption mode, and operating frequency of the target object, as well as communication status parameters such as signal strength, bit error rate, and connection status of the target object. This disclosure does not limit such information.

[0056] Preset parameter conditions refer to the judgment conditions set in advance for the operating parameter information, such as chip temperature being greater than or equal to a temperature threshold, signal strength being less than or equal to a signal strength threshold, etc., which are not limited in the embodiments disclosed herein.

[0057] Specifically, after obtaining the operation log of the target object, the terminal device can extract the operation parameter information of the target object during operation from the operation log and determine whether the extracted operation parameter information meets preset parameter conditions. If the operation parameter information meets the preset parameter conditions, the terminal device can determine that the operation parameter information included in the target object's operation log meets the preset parameter conditions. If the operation parameter information does not meet the preset parameter conditions, the terminal device can determine that the operation parameter information included in the target object's operation log does not meet the preset parameter conditions.

[0058] In this embodiment of the disclosure, if the target triggering condition only includes the item that the running log includes a preset log event sequence, the terminal device only needs to determine whether the running log includes the preset log event sequence to determine whether the running log meets the target triggering condition. If the target triggering condition only includes the item that the running parameter information meets the preset parameter condition, the terminal device only needs to determine whether the running parameter information in the running log meets the preset parameter condition to determine whether the running log meets the target triggering condition. If the target triggering condition includes both the item that the running log includes a preset log event sequence and the item that the running parameter information meets the preset parameter condition, the terminal device needs to determine whether the running log includes the preset log event sequence and whether the running parameter information in the running log meets the preset parameter condition. Only when both conditions are met can the terminal device determine that the running log meets the target triggering condition.

[0059] In this way, the terminal device can flexibly and comprehensively determine whether the target object's runtime log meets the target triggering conditions from different dimensions based on the specific content included in the target triggering conditions, thereby improving the accuracy and flexibility of target event identification. Furthermore, since the target triggering conditions can include at least one of log event sequences and runtime parameter information, the terminal device can flexibly configure the specific content of the target triggering conditions according to the actual application scenario to adapt to the identification needs of different types of target events. For example, for some types of target events, identification can be performed solely based on the log event sequence; for other types of target events, identification can be performed solely based on runtime parameter information; and for target events requiring higher identification accuracy, identification can be performed comprehensively based on both the log event sequence and runtime parameter information. This improves the flexibility of target event identification.

[0060] In some embodiments, step S101, determining the target control policy corresponding to the target event, may include: determining the target control policy corresponding to the target event based on configuration information; the configuration information includes the correspondence between events and control policies.

[0061] Specifically, the configuration information can record the correspondence between events and control policies. That is, the configuration information can configure corresponding control policies for one or more events. Each event can correspond to one control policy. Different events can correspond to the same control policy or different control policies. This disclosure does not impose any special restrictions on this.

[0062] Furthermore, after determining that a target object has triggered a target event, the terminal device can obtain configuration information and, based on the correspondence between events and control policies recorded in the configuration information, determine the control policy corresponding to the target event as the target control policy. For example, the configuration information may include the correspondence between a first event and a first control policy, and the correspondence between a second event and a second control policy. If the terminal device determines that the target event is the first event, it can determine the first control policy as the target control policy based on the correspondence between events and control policies in the configuration information. If the terminal device determines that the target event is the second event, it can determine the second control policy as the target control policy based on the correspondence between events and control policies in the configuration information.

[0063] In this way, the terminal device can quickly and accurately determine the target control strategy corresponding to the target event based on the pre-configured correspondence in the configuration information, providing a foundation for subsequent control of the target object according to the target control strategy. Furthermore, since different events in the configuration information can correspond to different control strategies, different control strategies can be applied when the target object triggers different events, thus adapting to the dynamic changes in the target object's operating scenario.

[0064] S102: Control the target object according to the target control strategy.

[0065] In some embodiments, the target object may be a first chip (e.g., a CP chip) in a terminal device used to generate operation logs, and the terminal device may control the target object according to the target control policy through a built-in second chip (AP chip).

[0066] For example, the second chip can determine the target control strategy corresponding to the target event in response to a target object triggering a target event. Then, the second chip can generate corresponding control instructions based on the target control strategy. These control instructions instruct the first chip to perform corresponding control actions according to the target control strategy. After generating the control instructions, the second chip can send them to the first chip. Upon receiving the control instructions from the second chip, the first chip can parse the control instructions and execute the control actions corresponding to the parse results. For example, it can restrict the first chip from generating runtime logs of a target type.

[0067] In some embodiments, the second chip and the first chip may communicate using a communication interface inside the terminal device, such as a serial peripheral interface, a universal asynchronous transceiver, or other interfaces suitable for inter-chip communication. This disclosure does not impose any special limitations on this.

[0068] In some embodiments, the second chip and the first chip can communicate using a pre-agreed instruction format. For example, the second chip can encapsulate the target control strategy into an AT format control instruction that the first chip can parse and execute, and send the AT format control instruction to the first chip to instruct the first chip to perform corresponding control actions according to the target control strategy.

[0069] As can be seen, in this embodiment of the present disclosure, when the terminal device determines that a target object has triggered a target event, it can respond to the target object triggering the target event, determine the target control policy corresponding to the target event, and control the target object according to the target control policy. Since the target control policy is used to instruct the target object to restrict the generation of target-type runtime logs, the terminal device can restrict the target object from generating target-type runtime logs by controlling the target object according to the target control policy. In this way, the target object can dynamically adjust the way runtime logs are generated based on the triggered event, avoiding the waste of internal resources caused by continuously generating runtime logs when it is not necessary to generate a large amount of runtime logs.

[0070] Furthermore, since the target control strategy is determined based on the target event, different target events can correspond to different control strategies. Therefore, when the target object triggers different target events, the generation of runtime logs can be limited according to different control strategies, thus adapting to the dynamic changes in the target object's needs under different runtime scenarios. This effectively saves the target object's memory resources, avoids response lag and task timeouts caused by the continuous generation of large amounts of runtime logs, and ensures the normal operation of the target object.

[0071] In some embodiments, the target control strategy includes the log level of the target type's runtime log under the target event; the above step S102, controlling the target object according to the target control strategy, may include: controlling the generation rate of the target object's runtime log of the target type according to the log level.

[0072] Log levels are used to indicate the severity and detail of runtime logs. Different log levels reflect the varying importance and level of detail of the information recorded in the runtime logs. For example, log levels can include debug level, information level, warning level, and error level. Debug level runtime logs record detailed debugging information during the target object's execution, such as function calls, variable values, and execution paths. They contain the most information but have relatively low value, typically used for debugging and problem localization during the development phase. Information level runtime logs record key status information and normal operation records during the target object's execution, such as task startup, configuration loading, and operation completion. They contain a moderate amount of information and are used to understand the target object's runtime status. Warning level runtime logs record abnormal situations that occur during the target object's execution. These abnormal situations may affect the target object's performance or functionality but have not yet caused task failure; examples include excessive resource consumption and exceeding the retries limit. Error-level runtime logs can record error events that occur during the execution of a target object. These error events may cause abnormal functionality or task failure of the target object, such as initialization failure, communication timeout, memory allocation failure, etc. They contain the least amount of information but are the most valuable, serving as a key basis for locating the cause of the failure.

[0073] When a target object triggers a target event, the terminal device can control the generation rate of the target type's runtime logs based on the log level of the target type's runtime logs. For example, when the log level is debug, since debug-level runtime logs contain the most information, the terminal device can control the target object to generate runtime logs of that type at a higher generation rate to obtain sufficient detailed information for problem analysis. When the log level is error, since error-level runtime logs contain the least amount of information but have the highest value, the terminal device can control the target object to generate runtime logs of that type at a lower generation rate, retaining only the most critical error information and avoiding the consumption of internal resources due to the generation of a large number of low-value logs.

[0074] It is understood that the above description regarding generating runtime logs at a higher generation rate for debug levels and at a lower generation rate for error levels is merely an exemplary illustration of the embodiments of this disclosure and does not constitute a limitation on the embodiments of this disclosure. In other embodiments, when the log level is debug level, the terminal device can also control the target object to generate debug level runtime logs at a lower generation rate to save internal resources; when the log level is error level, the terminal device can also control the target object to generate error level runtime logs at a higher generation rate to obtain richer error context information. Different log levels can correspond to different generation rates, and the magnitude relationship of the generation rates corresponding to different log levels can be configured according to actual application scenarios and needs; the embodiments of this disclosure do not impose special limitations in this regard.

[0075] In other words, the terminal device can determine the target generation rate of a certain type of operation log based on the log level corresponding to that target control policy, and control the target object to generate the operation log at a rate less than or equal to the target generation rate. For example, if the log level corresponding to a certain type of operation log in the target control policy is debug level, the terminal device can determine the target generation rate corresponding to debug level as a first rate and control the target object to generate the operation log of that target type at a rate less than or equal to the first rate. If the log level corresponding to the target type of operation log in the target control policy is error level, the terminal device can determine the target generation rate corresponding to error level as a second rate and control the target object to generate the operation log of that target type at a rate less than or equal to the second rate. The first rate and the second rate can be the same or different, and this embodiment does not impose any special restrictions on this.

[0076] In this way, terminal devices can flexibly control the generation rate of operation logs according to different log levels, ensuring the recording of key information while avoiding the consumption of internal resources due to the generation of a large number of low-value logs, thus achieving fine-grained control over the generation rate of operation logs.

[0077] In some embodiments, controlling the generation rate of target type runtime logs generated by the target object based on the log level may include: controlling the target object to stop generating target type runtime logs in response to the log level satisfying a preset relationship with a preset log level.

[0078] The preset log level can be a pre-set log level threshold for the target type of runtime log. The preset log level can be used to determine whether the log level of the target type of runtime log meets the condition for stopping generation. The preset relationship can refer to a certain size or range relationship between the log level and the preset log level, such as the log level being less than or equal to the preset log level, the log level being greater than or equal to the preset log level, the log level being equal to the preset log level, or the log level belonging to a preset log level range, etc. This disclosure does not impose any special limitations on this.

[0079] If the terminal device determines that the log level and the preset log level meet the preset relationship, it can control the target object to stop generating runtime logs of that target type.

[0080] Specifically, after determining the log level of the target object's runtime log, the terminal device can obtain a preset log level and determine whether a preset relationship is satisfied between the current log level and the preset log level. If the log level and the preset log level satisfy the preset relationship, the terminal device can determine that a stop operation needs to be performed on the runtime log generation for that target type, and control the target object to stop generating runtime logs for that target type. If the log level and the preset log level do not satisfy the preset relationship, the terminal device can determine that a stop operation does not need to be performed on the runtime log generation for that target type, and control the target object to continue generating runtime logs for that target type.

[0081] For example, the preset log level can be set to the information level, and the preset relationship can be set to log level less than or equal to the preset log level. If the target type's runtime log has a debug level, since the debug level is less than the information level (meaning the log level and the preset log level satisfy the preset relationship), the terminal device can control the target object to stop generating runtime logs of the target type at the debug level. If the target type's runtime log has a warning level or an error level, since both the warning level and the error level are greater than the information level (meaning the log level and the preset log level do not satisfy the preset relationship), the terminal device can control the target object to continue generating runtime logs of the target type at the warning level and the error level.

[0082] For example, the preset log level can be set to the warning level, and the preset relationship can be set to the log level being greater than or equal to the preset log level. If the target type's runtime log has an error level, since the error level is greater than the warning level (meaning the log level and the preset log level satisfy the preset relationship), the terminal device can control the target object to stop generating runtime logs of the target type at the error level. If the target type's runtime log has a debug level, information level, or warning level, since the debug level, information level, and warning level are all less than or equal to the warning level (meaning the log level and the preset log level do not satisfy the preset relationship), the terminal device can control the target object to continue generating runtime logs of the target type at the debug level, information level, and warning level.

[0083] For example, the preset log level can be set to the information level, and the preset relationship can be set to the log level equal to the preset log level. If the target type's runtime log has an information level, since the information level equals the preset log level (i.e., the log level and the preset log level satisfy the preset relationship), the terminal device can control the target object to stop generating runtime logs of the target type at the information level. If the target type's runtime log has a debug level, a warning level, or an error level, since none of these log levels equal the preset log level (i.e., the log level and the preset log level do not satisfy the preset relationship), the terminal device can control the target object to continue generating runtime logs of the target type at the debug level, warning level, and error level.

[0084] In this way, the terminal device can flexibly determine the range of log levels that need to be stopped from being generated based on the specific settings of the preset log levels and preset relationships, and control the target object to stop generating runtime logs of the target type corresponding to the log levels that satisfy the preset relationships. Since only runtime logs corresponding to the log levels that satisfy the preset relationships are stopped from being generated, while runtime logs corresponding to other log levels can still be generated normally, it is possible to stop the generation of low-value runtime logs to save the internal resources of the target object, while ensuring the complete recording of high-value runtime logs, thus providing effective data support for subsequent problem analysis and fault location of the target object.

[0085] In some embodiments, controlling the generation rate of runtime logs of the target type generated by the target object according to the log level may include: determining the target generation rate corresponding to the log level; and controlling the generation rate of runtime logs of the target type generated by the target object to be less than or equal to the target generation rate.

[0086] The target generation rate refers to the maximum allowed generation rate of runtime logs of that target type for a target object, corresponding to the log level. Different log levels can correspond to different target generation rates. For example, the debug level can correspond to the first target generation rate, the information level to the second target generation rate, the warning level to the third target generation rate, and the error level to the fourth target generation rate. The first, second, third, and fourth target generation rates can be the same or different, and this disclosure does not impose any limitations.

[0087] After determining the log level of the target object's runtime log, the terminal device can determine the corresponding target generation rate based on that log level. For example, if the log level is debug, the terminal device can determine the target generation rate corresponding to debug as the first target generation rate. If the log level is informational, the terminal device can determine the target generation rate corresponding to informational as the second target generation rate. If the log level is warning, the terminal device can determine the target generation rate corresponding to warning as the third target generation rate. If the log level is error, the terminal device can determine the target generation rate corresponding to error as the fourth target generation rate.

[0088] After determining the target generation rate, the terminal device can control the target object to generate runtime logs of that target type at a rate less than or equal to the target generation rate. For example, if the terminal device determines that the target generation rate corresponding to the debug level is the first target generation rate, then the terminal device can control the target object to generate runtime logs of the target type for the debug level at a rate less than or equal to the first target generation rate. If the terminal device determines that the target generation rate corresponding to the error level is the fourth target generation rate, then the terminal device can control the target object to generate runtime logs of the target type for the error level at a rate less than or equal to the fourth target generation rate.

[0089] It should be noted that the target generation rate for different log levels can be configured according to the actual application scenario and requirements. For example, in scenarios where a large amount of debugging information is needed to locate problems, the target generation rate for the debug level can be configured higher to ensure that enough detailed information can be obtained. In scenarios where only serious errors need to be addressed, the target generation rate for the error level can be configured moderately to ensure that error information is completely recorded. This disclosure does not impose any special restrictions on the specific values ​​of the target generation rate for different log levels or the relationship between the target generation rates for different log levels.

[0090] In this way, the upper limit of the generation rate of runtime logs can be flexibly controlled according to different log levels. While ensuring that runtime logs corresponding to each log level can be generated on demand, it avoids excessive occupation of the internal resources of the target object due to excessive generation rate of runtime logs, and achieves fine-grained control over the generation rate of runtime logs.

[0091] In some embodiments, the control method provided in this disclosure may further include: generating configuration information, or receiving configuration information sent by a configuration device.

[0092] The configuration device can be a device independent of the terminal device, such as a server, personal computer or other device with data processing capabilities. This disclosure does not impose any special restrictions on the specific type of configuration device.

[0093] Specifically, the terminal device can generate configuration information automatically according to preset rules or algorithms and store the generated configuration information in the terminal device for use in subsequent steps. Alternatively, the terminal device can also receive configuration information sent by a configuration device. In this case, the configuration device can generate configuration information and send it to the terminal device. After receiving the configuration information from the configuration device, the terminal device can store the configuration information in the terminal device for use in subsequent steps.

[0094] It should be noted that the terminal device can choose to use one method to generate configuration information and the method to receive configuration information sent by the configuration device, or they can be used in combination. This disclosure does not impose any special restrictions on this. That is, the terminal device can independently generate configuration information and directly use the self-generated configuration information in subsequent steps. The terminal device can also simply receive configuration information sent by an external configuration device and directly use the received configuration information in subsequent steps. Furthermore, the terminal device can modify or supplement the received configuration information based on the configuration information sent by the external configuration device and use the modified or supplemented configuration information in subsequent steps. This disclosure does not impose any special restrictions on the specific implementation method of the terminal device obtaining configuration information.

[0095] In this way, terminal devices can obtain configuration information through multiple methods, improving the flexibility of configuration information acquisition. Furthermore, since the configuration information can be pre-stored in the terminal device, when it is necessary to determine the target control strategy corresponding to the target event based on the configuration information later, the terminal device can directly call the stored configuration information for matching and determination, without needing to temporarily generate configuration information when the target event is triggered. This improves the response speed and execution efficiency of the control method, providing a data foundation for subsequently determining the target control strategy corresponding to the target event based on the configuration information.

[0096] In some embodiments, Figure 3 This is a schematic diagram illustrating a process for generating configuration information according to some embodiments of the present disclosure. Figure 3 As shown, the above-mentioned generation of configuration information may include the following steps S301-S304: S301: Get historical running logs.

[0097] Among them, the historical running log is the running log generated by the target object in a historical period.

[0098] Specifically, the terminal device can retrieve historical operation logs from its own storage space. The operation logs generated by the target object during operation can be stored in the terminal device's storage space. When the terminal device needs to generate configuration information, it can read the operation logs generated by the target object in historical periods from this storage space as historical operation logs.

[0099] Terminal devices can also obtain historical operation logs from external devices. External devices can store operation logs generated by the target object during historical periods, and terminal devices can obtain these historical operation logs through a communication connection with the external device. This disclosure does not impose any special restrictions on the specific method by which the terminal device obtains historical operation logs.

[0100] It should be noted that the historical time period can be a fixed time range preset by the terminal device, such as the most recent hour, the most recent day, or the most recent week. Alternatively, the historical time period can be a time range dynamically determined by the terminal device based on the actual application scenario; for example, the terminal device can determine the historical time period based on the current time and a preset time length. This disclosure does not impose any special restrictions on the specific method of determining the historical time period.

[0101] Understandably, the acquired historical operation logs can include logs from the target object under normal conditions as well as logs from the target object under abnormal conditions. Historical operation logs record the target object's key behavioral trajectories, operational parameters, and various abnormal event information within a historical period. This information reflects the target object's operational status and patterns within that historical period. By analyzing and processing the historical operation logs, the terminal device can extract feature information used to generate configuration information. Thus, configuration information can be subsequently generated based on these historical operation logs, ensuring that the generated configuration information reflects the target object's operational characteristics within the historical period and provides a basis for identifying target events during subsequent operation.

[0102] S302: Determine the first time period based on historical operation logs.

[0103] The first time period is defined as the period in which the target object's historical log generation rate is greater than or equal to the upper limit of the generation rate. The upper limit of the generation rate can be a pre-set threshold for the target object's log generation rate. This upper limit is used to determine whether the target object's log generation rate within a historical time period is abnormal. When the target object's log generation rate within a certain time period is greater than or equal to the upper limit, it can be considered that the target object's log generation rate within that time period is high, and an anomaly may exist during that period. When the target object's log generation rate within a certain time period is less than the upper limit, it can be considered that the target object's log generation rate within that time period is within the normal range.

[0104] Specifically, after acquiring historical operation logs, the terminal device can determine the first time period based on these logs. The first time period refers to the period during which the target object's generation rate of historical operation logs is greater than or equal to the upper limit of the generation rate. The terminal device can perform time-series analysis on the historical operation logs, dividing them into multiple time periods based on their generation time, and calculating the generation rate within each time period. After calculating the generation rate for each time period, the terminal device can compare the generation rate within each time period with the upper limit of the generation rate. If the generation rate within a certain time period is greater than or equal to the upper limit of the generation rate, the terminal device can determine that time period as the first time period. If the generation rate within a certain time period is less than the upper limit of the generation rate, the terminal device can determine that time period is not the first time period.

[0105] It is understood that the first time period may include one or more time periods. For example, there may be multiple time periods in the historical operation log where the generation rate is greater than or equal to the upper limit of the generation rate. The terminal device may determine each of these time periods as the first time period. Alternatively, if the generation rate of multiple adjacent time periods is greater than or equal to the upper limit of the generation rate, the terminal device may merge these adjacent time periods into a continuous first time period. This disclosure does not impose any special restrictions on the specific method of determining the first time period.

[0106] In this way, the terminal device can determine the time period with an abnormal generation rate in the historical operation logs, i.e., the first time period, based on the generation rate of the historical operation logs. Since the first time period reflects the time period when the target object has a high generation rate within the historical time period, these time periods may be associated with certain events triggered by the target object. Therefore, determining the first time period can provide a basis for generating configuration information subsequently.

[0107] In some embodiments, after obtaining the historical operation logs, the historical operation logs can be preprocessed to determine the first time period based on the preprocessed historical operation logs.

[0108] Preprocessing can refer to actions such as cleaning and marking of historical operation logs.

[0109] Specifically, after acquiring historical operation logs, the terminal device can clean the logs, removing invalid characters and standardizing the timestamps. Invalid characters can refer to garbled characters, incorrectly formatted characters, or other characters that are meaningless for subsequent analysis. Timestamp standardization involves converting timestamps of different formats in the historical operation logs into a preset standard time format to facilitate subsequent time series analysis and period segmentation of the historical operation logs.

[0110] The terminal device can also mark the cleaned historical operation logs, identify key events in the logs, and assign corresponding log levels to these key events. Key events refer to events with specific meaning that occur during the operation of the target object, such as network entry events, cell handover events, and physical layer synchronization failure events. Log levels can include debug level, information level, warning level, and error level. The terminal device can identify key events from the historical operation logs according to preset marking rules and mark the corresponding log entries for these key events with the appropriate log levels. This allows for subsequent determination of the first and second time periods based on the marked historical operation logs, and the generation of configuration information.

[0111] Understandably, the preprocessed historical operation logs have a unified format and standardized timestamps, and key events have been marked. This allows for subsequent analysis of the historical operation logs, enabling time series analysis and feature extraction based on the unified format and marked key events, thereby improving the accuracy and efficiency of the analysis and providing an accurate data foundation for determining the first and second time periods and generating configuration information.

[0112] S303: Determine the second time period based on the first time period.

[0113] The end time of the second period is earlier than or equal to the start time of the first period. The second period can refer to a period in the historical operation log that precedes the first period. In other words, the second period is located entirely before the first period on the timeline.

[0114] Specifically, after determining the first time period, the terminal device can determine a second time period preceding the first time period based on its position on the timeline. For example, the terminal device can determine a time period in the historical operation log that starts earlier than the first time period as the second time period. Alternatively, the terminal device can determine a time period in the historical operation log that starts earlier than the first time period but is adjacent to its start time. Yet another example is that the terminal device can determine a time period in the historical operation log that starts earlier than the first time period and whose duration meets a preset duration requirement as the second time period. This embodiment of the present disclosure does not impose any special limitations on the specific method of determining the second time period.

[0115] It should be noted that the second time period can be immediately adjacent to the first time period, or there can be a certain time interval between them; this embodiment does not impose any special restrictions on this. The duration of the second time period can be the same as or different from the duration of the first time period; this embodiment also does not impose any special restrictions on this.

[0116] Understandably, the target object's operational state may undergo a series of changes before certain events occur, and these changes will be reflected in the target object's operational logs. The historical operational logs within the second time period, preceding the first time period, can reflect the target object's state changes before the generation rate anomaly, and these state changes may be associated with the events that triggered the generation rate anomaly within the first time period. Therefore, identifying the second time period helps to pinpoint the stage of state changes preceding the generation rate anomaly.

[0117] In this way, the terminal device can determine the second time period before the first time period based on the first time period, and focus the analysis scope on the time period before the period of abnormal generation rate. Subsequently, configuration information can be generated based on the historical operation logs within the second time period, so that the generated configuration information can reflect the state changes of the target object before the abnormal generation rate, and provide a basis for the target object to identify target events in advance during subsequent operation.

[0118] S304: Generate configuration information based on historical operation logs and the second time period.

[0119] In conjunction with the foregoing embodiments, the configuration information may include the correspondence between events and event triggering conditions, as well as the correspondence between events and control policies. Therefore, the terminal device can analyze the log information corresponding to the second time period in the historical operation logs, extract the features included in the log information within the second time period, and generate configuration information based on the extracted features.

[0120] Specifically, the terminal device can retrieve log information corresponding to the second time period from historical operation logs. Since the second time period precedes the first time period, the historical operation logs within the second time period can reflect the state changes of the target object before the abnormal generation rate. The terminal device can analyze the historical operation logs within the second time period, extract feature information from the logs, and generate event triggering conditions based on the extracted feature information. The terminal device can establish a correspondence between the generated event triggering conditions and the corresponding events and store it in the configuration information. Furthermore, the terminal device can configure corresponding control policies for each event, and also store the correspondence between events and control policies in the configuration information.

[0121] It is understood that the correspondence between event triggering conditions and events, and between events and control strategies, in the configuration information can be set and adjusted according to actual application scenarios and needs. For example, different event triggering conditions and different control strategies can be configured for different types of target events. This disclosure does not impose special restrictions on the specific content and format of the configuration information.

[0122] In this way, the terminal device can generate configuration information based on historical operation logs and the second time period. This configuration information reflects the log characteristics of the target object before the abnormal generation rate, providing a basis for the target object to match the event triggering conditions in the configuration information according to the operation log during subsequent operation. Since the generated configuration information includes the correspondence between events and event triggering conditions, as well as the correspondence between events and control policies, the terminal device can quickly determine whether the target object has triggered the target event and determine the corresponding target control policy after obtaining the target object's operation log, thereby improving the execution efficiency of subsequent control methods.

[0123] In some embodiments, step S304 above, generating configuration information based on historical operation logs and the second time period, may include: determining a target log event sequence based on at least one target log event, and generating configuration information based on the target log event sequence; the at least one target log event is a log event in the historical operation log corresponding to the second time period; and / or, generating configuration information based on target operation parameter information; the target operation parameter information is the operation parameter information of the target object included in the historical operation log within the second time period.

[0124] Specifically, the terminal device can retrieve log events corresponding to the second time period from historical operation logs and identify these log events as at least one target log event. After retrieving at least one target log event, the terminal device can determine a target log event sequence based on these events. The target log event sequence can include one or more target log events arranged in chronological order of their generation. For example, the terminal device can extract multiple log events from historical operation logs within the second time period, sort these events according to their generation order, and determine the resulting sequence as the target log event sequence. After determining the target log event sequence, the terminal device can generate configuration information based on it. For example, the terminal device can use the target log event sequence as an event triggering condition, establish a correspondence between the triggering condition and the corresponding event, and store this correspondence in the configuration information. Thus, when the terminal device subsequently retrieves the operation logs of the target object, it can determine whether the target object has triggered the corresponding event by checking whether the operation logs include the target log event sequence.

[0125] The terminal device can also obtain the target object's operating parameter information for the second time period from historical operation logs and identify this operating parameter information as the target operating parameter information. The operating parameter information may include hardware status parameters such as the target object's chip temperature, power consumption mode, and operating frequency, as well as communication status parameters such as signal strength, bit error rate, and connection status. After obtaining the target operating parameter information, the terminal device can generate configuration information based on it. For example, the terminal device can use the target operating parameter information as a component of the event triggering condition, establish a correspondence between the event triggering condition and the corresponding event, and store it in the configuration information. In this way, after subsequently obtaining the target object's operation logs, the terminal device can determine whether the target object has triggered the corresponding event by checking whether the operating parameter information in the operation logs meets the preset parameter conditions.

[0126] It should be noted that the terminal device can generate configuration information based on the target log event sequence, the target operating parameter information, or both. This embodiment does not impose any special limitations on this. When the terminal device generates configuration information based on both the target log event sequence and the target operating parameter information, the event triggering conditions in the configuration information can simultaneously include preset parameter conditions corresponding to both the target log event sequence and the target operating parameter information.

[0127] Understandably, since both the target log event sequence and the target runtime parameter information originate from historical runtime logs within the second time period, which precedes the first time period of abnormal generation rate, the configuration information generated based on the target log event sequence and / or target runtime parameter information can reflect the target object's state characteristics before the abnormal generation rate. Thus, after obtaining the target object's runtime logs, subsequent terminal devices can determine in advance whether the target object has triggered a target event, based on whether the runtime logs include the target log event sequence and / or whether the runtime parameter information meets preset parameter conditions, before the runtime log generation rate reaches its upper limit. This allows for the early execution of corresponding control strategies, preventing an abnormal increase in the runtime log generation rate. Consequently, this further conserves the target object's internal resources and prevents issues such as response lag and task timeouts.

[0128] In some embodiments, the configuration device may also generate configuration information. For a description of how the configuration device generates configuration information, please refer to the description of how the terminal device generates configuration information described above; it will not be repeated here.

[0129] In some embodiments, those skilled in the art can also set configuration information according to actual needs and store the configuration information in the terminal device or configuration device so that the terminal device can call the configuration information in the future. This disclosure does not limit this.

[0130] Figure 4 This is a schematic diagram illustrating the structure of a control device according to some embodiments of the present disclosure. Figure 4 As shown, the control device 400 provided in this embodiment may include: The control strategy determination module 401 is used to determine the target control strategy corresponding to the target event in response to the target event triggered by the target object; the target control strategy is used to indicate restrictions on the target object to generate target type runtime logs; The control module 402 is used to control the target object according to the target control strategy.

[0131] Optionally, the control strategy determination module 401 is specifically used to: determine the target control strategy corresponding to the target event based on the configuration information; the configuration information includes the correspondence between the event and the control strategy.

[0132] Optionally, the configuration information also includes the correspondence between events and event triggering conditions; the control strategy determination module 401 is specifically used to: obtain the running log of the target object; and, based on the configuration information, determine the target object to trigger the target event corresponding to the target triggering condition in response to the running log of the target object meeting the target triggering condition.

[0133] Optionally, the target triggering condition includes at least one of the following: the target object's running log includes a preset sequence of log events; the running parameter information included in the target object's running log meets the preset parameter conditions.

[0134] Optionally, the target control strategy includes the log level of the target type's runtime log under the target event; the control module 402 is specifically used to: control the generation rate of the target type's runtime log generated by the target object according to the log level.

[0135] Optionally, the control module 402 is specifically used to: control the target object to stop generating target type runtime logs in response to the log level satisfying a preset relationship with the preset log level.

[0136] Optionally, the control module 402 is specifically used to: determine the target generation rate corresponding to the log level based on the log level; and control the generation rate of the target object for the target type of runtime log to be less than or equal to the target generation rate.

[0137] Optionally, the control strategy determination module 401 is specifically used to: generate configuration information, or receive configuration information sent by the configuration device.

[0138] Optionally, the control strategy determination module 401 is specifically used for: obtaining historical operation logs; the historical operation logs are the operation logs generated by the target object in a historical period; determining a first period based on the historical operation logs; the first period is the period in which the target object's generation rate of historical operation logs is greater than or equal to the upper limit of the generation rate; determining a second period based on the first period; the end time of the second period is earlier than or equal to the start time of the first period; and generating configuration information based on the historical operation logs and the second period.

[0139] Optionally, the control strategy determination module 401 is specifically used to: determine a target log event sequence based on at least one target log event, and generate configuration information based on the target log event sequence; the at least one target log event is a log event in the historical operation log corresponding to the second time period; and / or, generate configuration information based on target operation parameter information; the target operation parameter information is the operation parameter information of the target object included in the historical operation log in the second time period.

[0140] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0141] Figure 5 This is a schematic diagram illustrating the structure of a control system according to some embodiments of the present disclosure. Figure 5 As shown, some embodiments of this disclosure illustrate a control system 500 that may include: The first chip, 501, is used to generate runtime logs; The second chip 502 is used to perform some or all of the steps in the control method provided in the embodiments of the present disclosure.

[0142] Since the second chip can execute some or all of the steps in the control method provided in the above-described embodiments of the present disclosure, the control system provided in the present disclosure can achieve some or all of the beneficial effects that the control method provided in the above-described embodiments of the present disclosure can achieve. Therefore, the beneficial effects that the control system provided in the present disclosure can achieve will not be described again here.

[0143] Figure 6 This is a block diagram illustrating an electronic device 600 according to some embodiments of the present disclosure. For example, the electronic device 600 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0144] See Figure 6 The electronic device 600 may include one or more of the following components: a processing component 602, a memory 604, a power component 606, a multimedia component 608, an audio component 610, an input / output (I / O) interface 612, a sensor component 614, and a communication component 616.

[0145] Processing component 602 typically controls the overall operation of electronic device 600, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 602 may include one or more processors 620 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 602 may include one or more modules to facilitate interaction between processing component 602 and other components. For example, processing component 602 may include a multimedia module to facilitate interaction between multimedia component 608 and processing component 602.

[0146] Memory 604 is configured to store various types of data to support the operation of electronic device 600. Examples of such data include instructions for any application or method operating on electronic device 600, contact data, phonebook data, messages, pictures, videos, etc. Memory 604 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0147] Power component 606 provides power to various components of electronic device 600. Power component 606 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic device 600.

[0148] Multimedia component 608 includes a screen that provides an output interface between the electronic device 600 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 608 includes a front-facing camera and / or a rear-facing camera. When the electronic device 600 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0149] Audio component 610 is configured to output and / or input audio signals. For example, audio component 610 includes a microphone (MIC) configured to receive external audio signals when electronic device 600 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 604 or transmitted via communication component 616. In some embodiments, audio component 610 also includes a speaker for outputting audio signals.

[0150] I / O interface 612 provides an interface between processing component 602 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0151] Sensor assembly 614 includes one or more sensors for providing state assessments of various aspects of electronic device 600. For example, sensor assembly 614 can detect the on / off state of electronic device 600, the relative positioning of components such as the display and keypad of electronic device 600, changes in position of electronic device 600 or a component of electronic device 600, the presence or absence of user contact with electronic device 600, orientation or acceleration / deceleration of electronic device 600, and temperature changes of electronic device 600. Sensor assembly 614 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 614 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 614 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.

[0152] Communication component 616 is configured to facilitate wired or wireless communication between electronic device 600 and other devices. Electronic device 600 can access wireless networks based on communication standards, such as WiFi, 3G, 4G, 5G, other communication standards, or combinations thereof. In some embodiments of this disclosure, communication component 616 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In some embodiments of this disclosure, communication component 616 further includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0153] In some embodiments of this disclosure, the electronic device 600 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0154] In some embodiments of this disclosure, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 604 including instructions, which can be executed by a processor 620 of an electronic device 600 to perform the control method described above. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0155] In some embodiments of this disclosure, a computer program product is also provided, including a computer program that, when executed by a processor, implements the control method provided in the embodiments of this disclosure described above.

[0156] Some embodiments of this disclosure also provide a chip, such as Figure 7 As shown, the chip includes at least one processor 701 and at least one interface circuit 702. The processor 701 and the interface circuit 702 are interconnected via lines. For example, the interface circuit 702 can be used to receive signals from other devices (e.g., the memory of an electronic device). As another example, the interface circuit 702 can be used to send signals to other devices (e.g., the processor 701). Exemplarily, the interface circuit 702 can read instructions stored in memory and send those instructions to the processor 701. When the instructions are executed by the processor 701, the electronic device can perform the steps in the above embodiments. Of course, the chip system may also include other discrete devices, and some embodiments of this disclosure do not specifically limit this.

[0157] In some embodiments of this disclosure, the interface circuit 702 can acquire data, program instructions, and / or information from the internal storage area of ​​the chip system; it can also acquire data, program instructions, and / or information from outside the chip system.

[0158] Optionally, the chip system may also include memory for storing necessary computer programs and data.

[0159] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented through hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this application.

[0160] It should be understood that, unless otherwise specifically indicated, features of various embodiments of this disclosure described herein can be combined with each other. As used herein, the term “and / or” includes any one of the relevant listed items and any combination of any two or more; similarly, “at least one of…” includes any one of the relevant listed items and any combination of any two or more.

[0161] Although terms such as “first,” “second,” and “third” may be used herein to describe various components, parts, regions, layers, or sections, these components, parts, regions, layers, or sections are not limited to these terms. Rather, these terms are used only to distinguish one component, part, region, layer, or section from another. Therefore, without departing from the teachings of the examples described herein, the first component, part, region, layer, or section mentioned in the examples may also be referred to as the second component, part, region, layer, or section. Furthermore, the terms “first” and “second” are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as “first” or “second” may explicitly or implicitly include at least one of that feature. In the description herein, “a plurality” means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0162] Furthermore, the term “exemplary” is used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as “exemplary” is not necessarily to be construed as advantageous compared to other aspects or designs. Rather, the use of the term “exemplary” is intended to present the concept in a concrete manner. As used herein, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless otherwise specified or clear from the context, “X applies A or B” is intended to mean any of the natural inclusive arrangements. That is, “X applies A or B” satisfies any of the foregoing instances if X applies A; X applies B; or both X applies A and B. Additionally, unless otherwise specified or clear from the context to refer to the singular form, the articles “a” and “an” as used in this application and the appended claims are generally understood to mean “one or more.”

[0163] Similarly, although this disclosure has been shown and described with respect to one or more implementations, equivalent variations and modifications will occur to those skilled in the art upon reading and understanding this specification and the accompanying drawings. This disclosure includes all such modifications and variations and is limited only by the scope of the claims. In particular, with respect to the various functions performed by the components described above (e.g., elements, resources, etc.), unless otherwise indicated, the terminology used to describe such components is intended to correspond to any component (functionally equivalent) that performs the specific function of the described component, even if structurally not equivalent to the disclosed structure. Furthermore, although specific features of this disclosure may have been disclosed with respect to only one of several implementations, such features may be combined with one or more other features of other implementations, as may be desired and advantageous to any given or particular application. Moreover, with regard to the terms “comprising,” “owning,” “having,” “having,” or variations thereof as used in the detailed description or claims, such terms are intended to be inclusive in a manner similar to the term “including.”

[0164] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0165] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A control method, characterized in that, include: In response to a target event triggered by a target object, the target control strategy corresponding to the target event is determined; The target control policy is used to instruct the target object to restrict the generation of target type runtime logs; The target object is controlled according to the target control strategy.

2. The control method according to claim 1, characterized in that, The determination of the target control strategy corresponding to the target event includes: Based on the configuration information, the target control strategy corresponding to the target event is determined; the configuration information includes the correspondence between the event and the control strategy.

3. The control method according to claim 2, characterized in that, The configuration information also includes the correspondence between events and event triggering conditions; the method further includes: Obtain the runtime logs of the target object; Based on the configuration information, in response to the target object's runtime log meeting the target triggering condition, it is determined that the target object triggers the target event corresponding to the target triggering condition.

4. The control method according to claim 3, characterized in that, The target triggering condition includes at least one of the following: The target object's runtime log includes a preset sequence of log events; The running log of the target object includes running parameter information that meets preset parameter conditions.

5. The control method according to any one of claims 1-4, characterized in that, The target control strategy includes the log level of the target type's runtime log under the target event; controlling the target object according to the target control strategy includes: Based on the log level, the generation rate of the target type of runtime logs for the target object is controlled.

6. The control method according to claim 5, characterized in that, The step of controlling the generation rate of runtime logs of the target type for the target object based on the log level includes: In response to the log level satisfying a preset relationship with the preset log level, the target object is controlled to stop generating runtime logs of the target type.

7. The control method according to claim 5, characterized in that, The step of controlling the generation rate of runtime logs of the target type for the target object based on the log level includes: Based on the log level, determine the target generation rate corresponding to the log level; Control the generation rate of the target object's runtime logs for the target type to be less than or equal to the target generation rate.

8. The control method according to any one of claims 2-4, characterized in that, Also includes: The configuration information is generated, or the configuration information is received from the configuration device.

9. The control method according to claim 8, characterized in that, The generation of the configuration information includes: Obtain historical operation logs; the historical operation logs are the operation logs generated by the target object during historical time periods; Based on the historical operation logs, a first time period is determined; the first time period is the period in which the target object generates the historical operation logs at a rate greater than or equal to the upper limit of the generation rate. Based on the first time period, a second time period is determined; the end time of the second time period is earlier than or equal to the start time of the first time period. The configuration information is generated based on the historical operation logs and the second time period.

10. The control method according to claim 9, characterized in that, The step of generating the configuration information based on the historical operation logs and the second time period includes: Based on at least one target log event, a target log event sequence is determined, and the configuration information is generated based on the target log event sequence; the at least one target log event is a log event in the historical operation log corresponding to the second time period; and / or, The configuration information is generated based on the target operating parameter information; the target operating parameter information is the operating parameter information of the target object in the second time period included in the historical operating log.

11. A control device, characterized in that, Used to perform the control method according to any one of claims 1-10.

12. An electronic device, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to execute the executable instructions to implement the control method as described in any one of claims 1-10.

13. A chip, characterized in that, The chip includes a processing unit and an interface circuit. The processing unit obtains program instructions through the interface circuit, and the program instructions are executed by the processing unit. The processing unit is used to execute the control method as described in any one of claims 1-10.

14. A non-transitory computer-readable storage medium, characterized in that, When the instructions in the storage medium are executed by the processor, the processor is able to perform the control method as described in any one of claims 1-10.

15. A computer program product, characterized in that, It includes a computer program that, when executed by a processor, enables the control method as described in any one of claims 1-10.