EP2950203B1 - Verfahren zur identifikation eines anwendungsszenarios, stromverbrauchverwaltungsverfahren und -vorrichtung und endgerät - Google Patents

Verfahren zur identifikation eines anwendungsszenarios, stromverbrauchverwaltungsverfahren und -vorrichtung und endgerät Download PDF

Info

Publication number
EP2950203B1
EP2950203B1 EP14879273.2A EP14879273A EP2950203B1 EP 2950203 B1 EP2950203 B1 EP 2950203B1 EP 14879273 A EP14879273 A EP 14879273A EP 2950203 B1 EP2950203 B1 EP 2950203B1
Authority
EP
European Patent Office
Prior art keywords
characteristic data
application program
application
scenario
application scenario
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP14879273.2A
Other languages
English (en)
French (fr)
Other versions
EP2950203A1 (de
EP2950203A4 (de
Inventor
Wenchao Wang
Yaocang JIA
Jing Zhu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of EP2950203A1 publication Critical patent/EP2950203A1/de
Publication of EP2950203A4 publication Critical patent/EP2950203A4/de
Application granted granted Critical
Publication of EP2950203B1 publication Critical patent/EP2950203B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26—Power supply means, e.g. regulation thereof
    • G06F1/32—Means for saving power
    • G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3058—Monitoring arrangements for monitoring environmental properties or parameters of the computing system or of the computing system component, e.g. monitoring of power, currents, temperature, humidity, position, vibrations
    • G06F11/3062—Monitoring arrangements for monitoring environmental properties or parameters of the computing system or of the computing system component, e.g. monitoring of power, currents, temperature, humidity, position, vibrations where the monitored property is the power consumption
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/04—Processing captured monitoring data, e.g. for logfile generation
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
    • G06F9/45516—Runtime code conversion or optimisation
    • G06F9/4552—Involving translation to a different instruction set architecture, e.g. just-in-time translation in a JVM
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Definitions

  • the present invention relates to the field of data processing technologies, and specifically, to an application scenario identification method, a power consumption management method, an apparatus, and a terminal device.
  • a principle of the solution is that: a central processing unit (CPU), a graphics processing unit (GPU), and a liquid crystal display (LCD) are controlled after different application scenarios are identified, thereby completing control on power consumption of the terminal device.
  • CPU central processing unit
  • GPU graphics processing unit
  • LCD liquid crystal display
  • a specific monitoring process may be that: A system application programming interface (API) related to a hardware operation is monitored by using a kernel; when it is detected that a kernel event occurs, that is, invoking of the system API occurs, then hardware use information is analyzed, and scenario information is obtained; and then, hardware power consumption is determined, and power consumption is controlled.
  • API application programming interface
  • a kernel monitoring event is related to a bottom layer, and several different upper-layer scenarios may be corresponding to one or more bottom-layer events of a same series. In this case, it is not accurate enough to identify an application scenario, which affects user experience.
  • Embodiments of the present invention are defined by the claims.
  • a method for identifying an application scenario of a terminal device is provided, so as to relatively accurately identify an application scenario of a terminal device, thereby improving user experience of the terminal device.
  • a method for managing power consumption of a terminal device is provided, so as to relatively accurately determine a power consumption control policy, thereby improving user experience of the terminal device.
  • a method for identifying an application scenario of a terminal device including:
  • the characteristic data of the application program includes static characteristic data and dynamic characteristic data; and the analyzing an application program running on a terminal device by means of compilation to obtain characteristic data of the application program includes:
  • the method further includes:
  • the method further includes:
  • a method for managing power consumption of a terminal device including:
  • the characteristic data of the application program includes static characteristic data and dynamic characteristic data; and the analyzing an application program running on a terminal device by means of compilation to obtain characteristic data of the application program includes:
  • the method further includes:
  • the method further includes:
  • the method further includes:
  • the characteristic data of the application program includes static characteristic data and dynamic characteristic data
  • the first acquiring unit includes:
  • the identification apparatus further includes a first receiving unit, where
  • a power consumption management apparatus including:
  • the characteristic data of the application program includes static characteristic data and dynamic characteristic data; and the second acquiring unit includes:
  • the power consumption management apparatus further includes:
  • the power consumption management apparatus further includes a second receiving unit, where
  • a terminal device including a screen component and a processor, where
  • a terminal device including a screen component and a processor, where
  • an application program running on a terminal device is analyzed by means of compilation to obtain characteristic data of the application program; and application scenario information corresponding to the characteristic data of the application program is determined from a scenario characteristic data set according to the characteristic data of the application program, where the scenario characteristic data set includes a correspondence between multiple types of application scenario information and characteristic data of multiple application programs, and the application scenario information corresponding to the characteristic data of the application program is used to indicate an application scenario currently used for the terminal device.
  • an application program running on the terminal device is analyzed by means of compilation to obtain characteristic data of the application program. Because characteristic data of an application program is more likely to be unique in describing a corresponding application scenario, application scenario information corresponding to the characteristic data of the application program is relatively accurate. Therefore, according to the application scenario identification method provided in the embodiments, an application scenario of a terminal device can be relatively accurately identified, thereby further improving user experience of the terminal device.
  • an application program running on a terminal device is analyzed by means of compilation to obtain characteristic data of the application program; application scenario information corresponding to the characteristic data of the application program is determined from a scenario characteristic data set according to the characteristic data of the application program; where the scenario characteristic data set includes a correspondence between multiple types of application scenario information and characteristic data of multiple application programs, and the application scenario information corresponding to the characteristic data of the application program is used to indicate an application scenario currently used for the terminal device; and a power consumption control policy corresponding to the application scenario information is determined from a control policy set according to the application scenario information, where the control policy set includes a correspondence between the multiple types of application scenario information and multiple power consumption control policies.
  • an application program running on the terminal device is analyzed by means of compilation to obtain characteristic data of the application program. Because characteristic data of an application program is more likely to be unique in describing a corresponding application scenario, application scenario information corresponding to the characteristic data of the application program is relatively accurate, and further a power consumption control policy corresponding to the application scenario information is also relatively accurate. Therefore, according to the power consumption management method provided in the embodiments, an application scenario of a terminal device can be relatively accurately identified, so that a power consumption control policy is relatively accurately determined, thereby further improving user experience of the terminal device.
  • Embodiments of the present invention provide a method for identifying an application scenario of a terminal device, so as to relatively accurately identify an application scenario of a terminal device, thereby improving user experience of the terminal device.
  • the embodiments of the present invention further provide a method for managing power consumption of a terminal device, so as to relatively accurately determine a power consumption control policy, thereby improving user experience of the terminal device.
  • the embodiments of the present invention further provide a corresponding apparatus and terminal device. Details are separately described in the following.
  • FIG. 1 and FIG. 2 are schematic structural diagrams of a terminal device according to embodiments of the present invention.
  • FIG. 1 and FIG. 2 are used as examples to introduce a logical structure of a computing node applied in an application scenario identification method or a power consumption management method provided in the embodiments of the present invention.
  • the computing node may be a terminal device, and the terminal device may specifically be a smartphone.
  • a hardware layer of the terminal device includes a central processing unit (CPU), a graphics processing unit (GPU), and the like.
  • the hardware layer of the terminal device may further include a storage, an input/output device, a memory, a memory controller, a network interface, and the like, where the input device may include a keyboard, a mouse, a touchscreen, and the like, and the output device may include a display device, such as a liquid crystal display (LCD), a cathode ray tube (CRT), and a holographic, a projector.
  • a display device such as a liquid crystal display (LCD), a cathode ray tube (CRT), and a holographic, a projector.
  • An operating system such as Android or Firefox OS
  • some application programs may run on the hardware layer.
  • the Android system is used as an example in FIG. 1 to introduce a software system architecture of the terminal device, where a core library is a core part of the operating system and includes an appearance manager, a media framework, a relational database, a 2G graphics engine library, a Web browser engine, a kernel library, a virtual machine (for example, a Dalvik Virtual Machine), and the like. Identification of an application scenario and determining of a power consumption control policy that are described in this embodiment of the present invention may be implemented at a virtual machine (for example, a Dalvik Virtual Machine).
  • the virtual machine analyzes an application program running on the terminal device by means of compilation to obtain characteristic data of the application program; determines, from a scenario characteristic data set according to the characteristic data of the application program, application scenario information corresponding to the characteristic data of the application program, where the scenario characteristic data set includes a correspondence between multiple types of application scenario information and characteristic data of multiple application programs, and the application scenario information corresponding to the characteristic data of the application program is used to indicate an application scenario currently used for the terminal device; determines, from a control policy set according to the application scenario information, a power consumption control policy corresponding to the application scenario information, where the control policy set includes a correspondence between the multiple types of application scenario information and multiple power consumption control policies; generates a corresponding power consumption control instruction according to the power consumption control policy corresponding to the application scenario information; and transfers the power consumption control instruction to a kernel (that is, a Linux kernel in FIG. 1 ), so that power consumption control is performed by the kernel on corresponding hardware (for example, a CPU, a GPU, or a display device) of the kernel.
  • the terminal device further includes a drive layer, a framework layer, and an application layer
  • the drive layer may include a CPU drive, a GPU drive, a display controller drive, and the like
  • the framework layer may include a browser engine, a layout engine, a file parser, and the like
  • the application layer may include multiple application programs, such as a home screen, a media player, and a browser.
  • the Firefox OS system is used as an example in FIG. 2 to introduce a software system architecture of the terminal device, where a core library is a core part of the operating system and includes an appearance manager, a media framework, a relational database, a user interface, a voice manager, and the like.
  • a core library is a core part of the operating system and includes an appearance manager, a media framework, a relational database, a user interface, a voice manager, and the like.
  • the terminal device further includes a drive layer, a framework layer, and an application layer, where the drive layer may include a CPU drive, a GPU drive, a display controller drive, and the like.
  • the framework layer may include a browser engine, a layout engine, a file parser, a JavaScript engine, and the like. The identification of an application scenario and the determining of a power consumption control policy that are described in this embodiment of the present invention may be implemented at the JavaScript engine.
  • the JavaScript engine analyzes an application program running on the terminal device by means of compilation to obtain characteristic data of the application program; determines, from a scenario characteristic data set according to the characteristic data of the application program, application scenario information corresponding to the characteristic data of the application program, where the scenario characteristic data set includes a correspondence between multiple types of application scenario information and characteristic data of multiple application programs, and the application scenario information corresponding to the characteristic data of the application program is used to indicate an application scenario currently used for the terminal device; determines, from a control policy set according to the application scenario information, a power consumption control policy corresponding to the application scenario information, where the control policy set includes a correspondence between the multiple types of application scenario information and multiple power consumption control policies; generates a corresponding power consumption control instruction according to the power consumption control policy corresponding to the application scenario information; and transfers the power consumption control instruction to a kernel (that is, a Linux kernel in FIG. 2 ), so that power consumption control is performed by the kernel on corresponding hardware (for example, a CPU, a GPU, or a display device) of
  • the application layer may include multiple application programs, such as a home screen, a media player, and a browser.
  • an application program running on a terminal device is analyzed by means of compilation to obtain characteristic data of the application program; application scenario information that corresponds to or matches the characteristic data of the application program and is used to indicate an application scenario currently used for the terminal device is determined according to a scenario characteristic data set, so as to resolve intelligent identification of an application scenario of a terminal device (for example, a smartphone), and achieve that: an identification method can be applied in different platforms, for example, can be applied in an operating system of a smartphone, such as Android or Firefox OS, and a same identification method may be used for different operating systems, and power consumption management control on a terminal device (for example, a smartphone) based on a highly refined scenario can further be completed.
  • an embodiment of a method for identifying an application scenario of a terminal device includes the following steps: 101. Analyze an application program running on a terminal device by means of compilation to obtain characteristic data of the application program.
  • all application programs that already exist such as a game program, a video program, a WeChat program, an SMS message program, a call program, and a payment program.
  • a running application program refers to a running program that has been started by a user, for example, after the user triggers starting of WeChat, the WeChat program is a running program. Alternatively, multiple application programs may run at the same time. Characteristic data of an application program refers to one or more functions that are included in the application program. Alternatively, the one or more functions may also be understood as a set of functions that are included in the application program.
  • the scenario characteristic data set may be stored in a file, or may be stored in a database. It should be understood that the application scenario identification method in this embodiment of the present invention is based on the scenario characteristic data set, which facilitates an upgrade and features high scalability. For example, if an application scenario is to be added, in the prior art, a ROM in a system needs to be updated; however, according to the present invention, only a scenario characteristic data set (for example, a scenario characteristic data file) needs to be updated without restarting a system, and therefore, user experience of a terminal user is better.
  • a scenario characteristic data set for example, a scenario characteristic data file
  • the scenario characteristic data set is determined in advance by a developer by performing a large quantity of tests.
  • the application scenario information may be an identifier of an application scenario, which indicates an application scenario currently used for the terminal device, for example, a WeChat scenario, a game scenario, or a video scenario.
  • Table 1 Correspondence between application scenario information and characteristic data of an application program
  • Application scenario information Characteristic data of an application program Game scenario information Characteristic data of a game program
  • WeChat scenario information Characteristic data of a WeChat program SMS message scenario information Characteristic data of an SMS message program
  • Call scenario information Characteristic data of a call program Payment scenario information Characteristic data of a payment program
  • Table 1 is only an example for illustration, there may be more correspondences between application scenario information and characteristic data of application programs, which are not listed one by one herein.
  • an application program running on a terminal device is analyzed by means of compilation to obtain characteristic data of the application program; and application scenario information corresponding to the characteristic data of the application program is determined from a scenario characteristic data set according to the characteristic data of the application program, where the scenario characteristic data set includes a correspondence between multiple types of application scenario information and characteristic data of multiple application programs, and the application scenario information corresponding to the characteristic data of the application program is used to indicate an application scenario currently used for the terminal device.
  • an application program running on the terminal device is analyzed by means of compilation to obtain characteristic data of the application program. Because characteristic data of an application program is more likely to be unique in describing a corresponding application scenario, application scenario information corresponding to the characteristic data of the application program is relatively accurate. Therefore, the application scenario identification method provided in this embodiment of the present invention can relatively accurately identify an application scenario of a terminal device, thereby further improving user experience of the terminal device.
  • the characteristic data of the application program includes static characteristic data and dynamic characteristic data.
  • an application program includes one or more functions, and the one or more functions may be compiled by using different languages; however, each function is used to support normal use of one function in an application scenario.
  • an application program corresponding to the WeChat scenario includes a function supporting a voice chat, a function supporting a text chat, and a function supporting browsing of Moments.
  • the one or more functions and the any function in this embodiment of the present invention all refer to the function itself or functions themselves, for example, a function that is compiled by using a C++ or Java language.
  • a frequently invoked function may be understood as the dynamic characteristic data of the application program, where a frequency of the invoking may be represented by a specific numeric value. For example, a threshold of 5 times one hour is set. If the function has been invoked for more than 5 times within one hour, it may be considered that the function is the dynamic characteristic data. For example, in the WeChat scenario, if a function supporting browsing of Moments is frequently invoked and the function becomes a hotspot function, the function supporting browsing of Moments is considered as the dynamic characteristic data.
  • static characteristic data is the same but dynamic characteristic data is different; therefore, an application scenario determined by combining the static characteristic data and the dynamic characteristic data is the most accurate.
  • a news client is used as an example, where the news client includes text news and video news.
  • Static characteristic data of the text news and static characteristic data of the video news are all obtained from an application program of the news client; therefore, obtained static characteristic data is the same.
  • a frequently invoked function of the text news may be a function A in the static characteristic data
  • a frequently invoked function of the video news may be a function B in the static characteristic data, where a text news scenario may be accurately distinguished from a video news scenario according to the function A and the function B. Therefore, in this embodiment of the present invention, an application scenario used for a terminal device is identified by combining static characteristic data and dynamic characteristic data, which can improve an accuracy rate of identifying an application scenario used for a terminal device.
  • the method may further include:
  • an update or an upgrade of the scenario characteristic data set can be implemented merely by storing, in the scenario characteristic data set, application scenario information of the newly added application scenario and corresponding characteristic data of an application program, which accelerates a speed of a data update or upgrade.
  • the method may further include:
  • application scenario information and characteristic data that corresponds to the application programs may be directly deleted from the scenario characteristic data set, thereby saving memory space.
  • an embodiment of a method for managing power consumption of a terminal device includes the following steps: 201. Analyze an application program running on a terminal device by means of compilation to obtain characteristic data of the application program.
  • step 201 For a process of step 201, reference may be made to step 101 for understanding, and details are not described herein again.
  • step 202 For a process of step 202, reference may be made to step 102 for understanding, and details are not described herein again.
  • the scenario characteristic data set may be stored in a file, or may be stored in a database.
  • the control policy set may be stored in a file, or may be stored in a database.
  • the control policy set is also determined in advance by a developer by performing a large quantity of tests, and is preset on the terminal device. For each piece of application scenario information, there is a corresponding power consumption control policy.
  • an application program running on a terminal device is analyzed by means of compilation to obtain characteristic data of the application program; application scenario information corresponding to the characteristic data of the application program is determined from a scenario characteristic data set according to the characteristic data of the application program, where the scenario characteristic data set includes a correspondence between multiple types of application scenario information and characteristic data of multiple application programs, and the application scenario information corresponding to the characteristic data of the application program is used to indicate an application scenario currently used for the terminal device; and a power consumption control policy corresponding to the application scenario information is determined from a control policy set according to the application scenario information, where the control policy set includes a correspondence between the multiple types of application scenario information and multiple power consumption control policies.
  • an application program running on the terminal device is analyzed by means of compilation to obtain characteristic data of the application program. Because characteristic data of an application program is more likely to be unique in describing a corresponding application scenario, application scenario information corresponding to the characteristic data of the application program is relatively accurate, and further a power consumption control policy corresponding to the application scenario information is also relatively accurate. Therefore, the power consumption management method provided in the embodiments of the present invention can relatively accurately identify an application scenario of a terminal device, so as to accurately determine a power consumption control policy, thereby improving user experience of the terminal device.
  • the characteristic data of the application program includes static characteristic data and dynamic characteristic data.
  • an application program includes one or more functions, and the one or more functions may be compiled by using different languages; however, each function is used to support normal use of one function in an application scenario.
  • an application program corresponding to the WeChat scenario needs to include a function supporting a voice chat, a function supporting a text chat, and a function supporting browsing of Moments.
  • the one or more functions and the any function in this embodiment of the present invention all refer to the function or functions, for example, a function that is compiled by using a C++ or Java language.
  • a frequently invoked function may be understood as the dynamic characteristic data of the application program, where a frequency of the invoking may be represented by a specific numeric value. For example, a threshold of 5 times one hour is set. If the function has been invoked for more than 5 times within one hour, it may be considered that the function is the dynamic characteristic data. For example, in the WeChat scenario, if a function supporting browsing of Moments is frequently invoked and the function becomes a hotspot function, the function supporting browsing of Moments is considered as the dynamic characteristic data.
  • static characteristic data is the same but dynamic characteristic data is different; therefore, an application scenario determined by combining the static characteristic data and the dynamic characteristic data is the most accurate.
  • a news client is used as an example, where the news client includes text news and video news.
  • Static characteristic data of the text news and static characteristic data of the video news are all obtained from an application program of the news client; therefore, static characteristic data obtained is the same.
  • a frequently invoked function of the text news may be a function A in the static characteristic data
  • a frequently invoked function of the video news may be a function B in the static characteristic data, where a text news scenario may be accurately distinguished from a video news scenario according to the function A and the function B. Therefore, in this embodiment of the present invention, an application scenario used for a terminal device is identified by combining static characteristic data and dynamic characteristic data, which can improve an accuracy rate of identifying an application scenario used for a terminal device.
  • the method may further include:
  • the method may further include:
  • a developer may extract corresponding characteristic data of an application program for the newly added application scenario; determine a corresponding power consumption control policy; and then only need to deliver, to a terminal device by using a server, application scenario information of the newly added application scenario, the corresponding characteristic data of an application program, and the corresponding power consumption control policy.
  • the terminal device stores, in the scenario characteristic data set, the application scenario information of the newly added application scenario and the corresponding characteristic data of an application program; and stores, in the control policy set, the application scenario information of the newly added application scenario and the corresponding power consumption control policy, which accelerates a speed of upgrading of characteristic data of a newly added application scenario and a power consumption control policy.
  • the method may further include:
  • application scenario information of a specified application scenario and corresponding characteristic data of an application program when some application programs are no longer used, application scenario information of a specified application scenario and corresponding characteristic data of an application program, and the application scenario information of the specified application scenario and a corresponding power consumption control policy may be respectively deleted directly from the scenario characteristic data set and the control policy set according to a deleting instruction.
  • Characteristic data of an application program and a power consumption control policy in this embodiment of the present invention are determined in advance by a developer by performing a large quantity of tests; a correspondence between characteristic data of an application program and application scenario information, and a correspondence between a power consumption control policy and the application scenario information are established and respectively stored in a scenario characteristic data set and a control policy set; and the scenario characteristic data set and the control policy set are prestored or dynamically loaded in the terminal device.
  • FIG. 5 For a process in which a developer extracts characteristic data of an application program in a test phase, reference may be made to FIG. 5 for understanding.
  • an Android system is used as an example.
  • An application program used in a terminal device runs on a dalvik virtual machine.
  • the dalvik virtual machine first uses a dx tool to convert a running application program APK file into a dex file, so that Java bytecode is translated into a bytecode form of the dalvik virtual machine; and finally interpreted, or executed by means of just-in-time compilation (JIT) by the virtual machine.
  • JIT just-in-time compilation
  • the dex file is divided into seven parts, where a Method field records a method of a Java level or a system API that is invoked by the application program. Either the method of the Java level or the system API is a function, and Method information is read by using the dx tool, where the Method information actually is a set of one or more functions, and static characteristic data of the application program can be obtained.
  • a running manner after the Dalvik introduces JIT is as follows: The virtual machine starts running in a manner of interpretation and execution, and begins to collect statistics of a frequency of invoking one or more functions in the Method information. When a frequency of invoking any function exceeds a preset upper limit, a compiler thread is started for starting compilation.
  • the any function may be acquired by means of JIT, and dynamic characteristic data of the application program, that is, trace information in FIG. 5 , is obtained.
  • Table 2a Table of application scenario information, characteristic data of an application program, and a corresponding power consumption control policy
  • Application scenario information Characteristic data of an application program
  • Power consumption control policy Game scenario information Characteristic data of a game program Improve an LCD refresh rate and reduce a GPU working frequency
  • Video scenario information Characteristic data of a video program Improve an LCD refresh rate and reduce a GPU working frequency
  • WeChat scenario information Characteristic data of a WeChat program Reduce a GPU working frequency
  • SMS message scenario information Characteristic data of an SMS message program Reduce GPU and CPU working frequencies
  • Call scenario information Characteristic data of a call program Reduce a GPU working frequency and an LCD refresh rate
  • Payment scenario information Characteristic data of a payment program Improve an LCD refresh rate and reduce a GPU working frequency
  • Table 2a is used only as an example for illustration herein, and actually, a correspondence among application scenario information, characteristic data of an application program, and a power consumption control policy may also be set in another implementation manner, for example, the following Table 2b-1 and Table 2b-2.
  • Table 2b-1 Table of application scenario information and corresponding characteristic data of an application program
  • Table 2b-2 Table of application scenario information and a corresponding power consumption control policy
  • Application scenario information Power consumption control policy Game scenario information Improve an LCD refresh rate and reduce a GPU working frequency
  • Video scenario information Improve an LCD refresh rate and reduce a GPU working frequency
  • Payment scenario information Improve an LCD refresh rate and reduce a GPU working frequency
  • FIG. 6 For a process of combining a construction phase and a running phase, reference may be made to FIG. 6 for understanding.
  • the developer runs an application program in a test device
  • the test device analyzes the running application program
  • characteristic data of the application program is extracted according to a process shown in FIG. 5
  • a power consumption control policy is made for the extracted characteristic data of the application program.
  • Table 2a For a correspondence between characteristic data of an application program and a power consumption control policy, reference may be made to Table 2a for understanding.
  • an embodiment of an application scenario identification apparatus 30 includes:
  • a first acquiring unit 301 analyzes an application program running on a terminal device by means of compilation to obtain characteristic data of the application program; and a first scenario characteristic data set managing unit 302 determines, from a scenario characteristic data set according to the characteristic data that is of the application program and is acquired by the first acquiring unit 301, application scenario information corresponding to the characteristic data of the application program, where the scenario characteristic data set includes a correspondence between multiple types of application scenario information and characteristic data of multiple application programs, and the application scenario information corresponding to the characteristic data of the application program is used to indicate an application scenario currently used for the terminal device.
  • an application program running on the terminal device is analyzed by means of compilation to obtain characteristic data of the application program. Because characteristic data of an application program is more likely to be unique in describing a corresponding application scenario, application scenario information corresponding to the characteristic data of the application program is relatively accurate. Therefore, the application scenario identification apparatus provided in this embodiment of the present invention can relatively accurately identify an application scenario of a terminal device, thereby further improving user experience of the terminal device.
  • the first acquiring unit 301 includes:
  • static characteristic data is the same but dynamic characteristic data is different; therefore, an application scenario determined by combining the static characteristic data and the dynamic characteristic data is the most accurate.
  • a news client is used as an example, where the news client includes text news and video news.
  • Static characteristic data of the text news and static characteristic data of the video news are all obtained from an application program of the news client; therefore, static characteristic data obtained is the same.
  • a frequently invoked function of the text news may be a function A in the static characteristic data
  • a frequently invoked function of the video news may be a function B in the static characteristic data, where a text news scenario may be accurately distinguished from a video news scenario according to the function A and the function B. Therefore, in this embodiment of the present invention, an application scenario used for a terminal device is identified by combining static characteristic data and dynamic characteristic data, which can improve an accuracy rate of identifying an application scenario used for a terminal device.
  • the identification apparatus 30 further includes a first receiving unit 303, where
  • an update or an upgrade of the scenario characteristic data set can be implemented merely by storing, in the scenario characteristic data set, application scenario information of the newly added application scenario and corresponding characteristic data of an application program, which accelerates a speed of a data update or upgrade.
  • application scenario information and characteristic data that corresponds to the application programs may be directly deleted from the scenario characteristic data set, thereby saving memory space.
  • an embodiment of a power consumption management apparatus 40 includes:
  • a second acquiring unit 401 analyzes an application program running on a terminal device by means of compilation to obtain characteristic data of the application program; a second scenario characteristic data set managing unit 402 determines, from a scenario characteristic data set according to the characteristic data that is of the application program and is acquired by the second acquiring unit 401, application scenario information corresponding to the characteristic data of the application program, where the scenario characteristic data set includes a correspondence between multiple types of application scenario information and characteristic data of multiple application programs, and the application scenario information corresponding to the characteristic data of the application program is used to indicate an application scenario currently used for the terminal device; and a control policy set management unit 403 determines, from a control policy set according to the application scenario information determined by the second scenario characteristic data set managing unit 402, a power consumption control policy corresponding to the application scenario information, where the control policy set includes a correspondence between the multiple types of application scenario information and multiple power consumption control policies.
  • an application program running on the terminal device is analyzed by means of compilation, and characteristic data of the application program is acquired. Because characteristic data of an application program is more likely to be unique in describing a corresponding application scenario, application scenario information corresponding to the characteristic data of the application program is relatively accurate, and further a power consumption control policy corresponding to the application scenario information is also relatively accurate. Therefore, the power consumption management apparatus provided in this embodiment of the present invention can relatively accurately identify an application scenario of a terminal device, so as to relatively accurately determine a power consumption control policy, thereby further improving user experience of the terminal device.
  • the second acquiring unit 401 includes:
  • static characteristic data is the same but dynamic characteristic data is different; therefore, an application scenario determined by combining the static characteristic data and the dynamic characteristic data is the most accurate.
  • a news client is used as an example, where the news client includes text news and video news.
  • Static characteristic data of the text news and static characteristic data of the video news are all obtained from an application program of the news client; therefore, static characteristic data obtained is the same.
  • a frequently invoked function of the text news may be a function A in the static characteristic data
  • a frequently invoked function of the video news may be a function B in the static characteristic data, where a text news scenario may be accurately distinguished from a video news scenario according to the function A and the function B. Therefore, in this embodiment of the present invention, an application scenario used for a terminal device is identified by combining static characteristic data and dynamic characteristic data, which can improve an accuracy rate of identifying an application scenario used for a terminal device.
  • the power consumption management apparatus 40 further includes:
  • the power consumption management apparatus 40 further includes a second receiving unit 406, where
  • an update or an upgrade of the scenario characteristic data set can be implemented merely by storing, in the scenario characteristic data set, application scenario information of the newly added application scenario and corresponding characteristic data of an application program, which accelerates a speed of a data update or upgrade.
  • application scenario information of a specified application scenario and corresponding characteristic data of an application program when some application programs are no longer used, application scenario information of a specified application scenario and corresponding characteristic data of an application program, and the application scenario information of the specified application scenario and a corresponding power consumption control policy may be respectively deleted directly from the scenario characteristic data set and the control policy set according to a deleting instruction, thereby saving memory space.
  • an embodiment of a terminal device 10 includes a screen component 11 and a processor 12, where
  • processor 12 for a working mechanism of the processor 12 in this embodiment, reference may be made to the description in the foregoing method embodiments; and a function of the processor 12 may be specifically implemented according to the methods in the foregoing method embodiments; and for a specific implementation process of the processor 12, reference may be made to relevant description of the foregoing method embodiments, and details are not described herein again.
  • an application program running on the terminal device is analyzed by means of compilation to obtain characteristic data of the application program; and application scenario information corresponding to the characteristic data of the application program is determined from a scenario characteristic data set according to the characteristic data of the application program, where the scenario characteristic data set includes a correspondence between multiple types of application scenario information and characteristic data of multiple application programs, and the application scenario information corresponding to the characteristic data of the application program is used to indicate an application scenario currently used for the terminal device.
  • an application program running on the terminal device is analyzed by means of compilation to obtain characteristic data of the application program. Because characteristic data of an application program is more likely to be unique in describing a corresponding application scenario, application scenario information corresponding to the characteristic data of the application program is relatively accurate. Therefore, the terminal device provided in this embodiment of the present invention can relatively accurately identify an application scenario of the terminal device, thereby further improving user experience of the terminal device.
  • FIG. 15 another embodiment of a terminal device 20 according to an embodiment of the present invention includes a screen component 21 and a processor 22, where
  • processor 22 for a working mechanism of the processor 22 in this embodiment, reference may be made to the description in the foregoing method embodiments; and a function of the processor 22 may be specifically implemented according to the methods in the foregoing method embodiments; and for a specific implementation process of the processor 22, reference may be made to relevant description of the foregoing method embodiments, and details are not described herein again.
  • an application program running on the terminal device is analyzed by means of compilation to obtain characteristic data of the application program; application scenario information corresponding to the characteristic data of the application program is determined from a scenario characteristic data set according to the characteristic data of the application program, where the scenario characteristic data set includes a correspondence between multiple types of application scenario information and characteristic data of multiple application programs, and the application scenario information corresponding to the characteristic data of the application program is used to indicate an application scenario currently used for the terminal device; and a power consumption control policy corresponding to the application scenario information is determined from a control policy set according to the application scenario information, where the control policy set includes a correspondence between the multiple types of application scenario information and multiple power consumption control policies.
  • an application program running on the terminal device is analyzed by means of compilation to obtain characteristic data of the application program. Because characteristic data of an application program is more likely to be unique in describing a corresponding application scenario, application scenario information corresponding to the characteristic data of the application program is relatively accurate, and further a power consumption control policy corresponding to the application scenario information is also relatively accurate. Therefore, the terminal device provided in this embodiment of the present invention can relatively accurately identify an application scenario of a terminal device, so as to relatively accurately determine a power consumption control policy, thereby further improving user experience of the terminal device.
  • FIG. 16 shows a structure of a terminal device 600 according to an embodiment of the present invention.
  • the terminal device 600 includes: at least one processor 601, at least one network interface 604 or another user interface 603, a memory 605, and at least one communications bus 602.
  • the communications bus 602 is configured to implement connection communication between these components.
  • the user interface 603 optionally included in the terminal device 600 includes a display (for example, a touchscreen, an LCD, a CRT, a holographic, or a projector), a keyboard, or a click device (for example, a mouse, a trackball, a touch panel, or a touchscreen).
  • the memory 605 may include a read-only memory and a random access memory and provides an instruction and data for the processor 601, and a part of the memory 605 may further include a non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the memory 605 stores the following elements: executable modules or data structures, or subsets thereof, or extended sets thereof:
  • the processor 601 is specifically configured to: when the application program is running, parse the application program, acquire one or more functions from the application program to serve as the static characteristic data, where the one or more functions are included in the application program, and are used to support normal use of one or more application functions in the application scenario currently used for the terminal device; and when a frequency of invoking any function in the one or more functions exceeds a preset threshold, determine that the any function is the dynamic characteristic data.
  • an application program running on the terminal device is analyzed by means of compilation to obtain characteristic data of the application program; and application scenario information corresponding to the characteristic data of the application program is determined from a scenario characteristic data set according to the characteristic data of the application program, where the scenario characteristic data set includes a correspondence between multiple types of application scenario information and characteristic data of multiple application programs, and the application scenario information corresponding to the characteristic data of the application program is used to indicate an application scenario currently used for the terminal device.
  • an application program running on the terminal device is analyzed by means of compilation to obtain characteristic data of the application program. Because characteristic data of an application program is more likely to be unique in describing a corresponding application scenario, application scenario information corresponding to the characteristic data of the application program is relatively accurate. Therefore, the terminal device provided in this embodiment of the present invention can relatively accurately identify an application scenario of the terminal device, thereby further improving user experience of the terminal device.
  • the processor 601 is further configured to: determine, from a control policy set according to the application scenario information, a power consumption control policy corresponding to the application scenario information, where the control policy set includes a correspondence between the multiple types of application scenario information and multiple power consumption control policies.
  • the processor 601 is further configured to implement power consumption control on corresponding hardware of the terminal device 600 according to the power consumption control policy corresponding to the application scenario information, where the corresponding hardware of the terminal device 600 includes one or more of: a screen component (for example, a display, specifically, a touchscreen), a processor (for example, a CPU or a GPU), and the like.
  • a screen component for example, a display, specifically, a touchscreen
  • a processor for example, a CPU or a GPU
  • the terminal device 600 may further execute the methods in the embodiments in FIG. 3 to FIG. 6 , and details are not described herein again in this embodiment of the present invention.
  • the terminal device in this embodiment of the present invention analyzes an application program running on the terminal device by means of compilation to obtain characteristic data of the application program. Because characteristic data of an application program is more likely to be unique in describing a corresponding application scenario, application scenario information corresponding to the characteristic data of the application program is relatively accurate, and further a power consumption control policy corresponding to the application scenario information is also relatively accurate. Therefore, the terminal device 600 provided in this embodiment of the present invention can relatively accurately identify an application scenario of a terminal device, so as to relatively accurately determine a power consumption control policy, thereby further improving user experience of the terminal device.
  • Embodiments of the present invention further relate to a terminal device 100, an application scenario identification method, and a power consumption management method.
  • the terminal device 100 may be a mobile phone, a tablet computer, a personal digital assistant (PDA), a point of sales (POS), a vehicle-mounted computer, or the like.
  • PDA personal digital assistant
  • POS point of sales
  • vehicle-mounted computer or the like.
  • FIG. 17 shows a schematic structural diagram of a terminal device 100 according to an embodiment of the present invention.
  • the terminal device 100 in this embodiment of the present invention includes a first memory 120, a processor 160, and an input unit 130, where the first memory 120 stores a scenario characteristic data set preset by the terminal device.
  • the scenario characteristic data set includes a correspondence between multiple types of application scenario information and characteristic data of multiple application programs, and application scenario information corresponding to characteristic data of an application program is used to indicate an application scenario currently used for the terminal device.
  • the input unit 130 is configured to: receive an operation of starting, by a user, an application program; and generate a starting instruction.
  • the processor 160 is configured to: run the application program; analyze an application program running on the terminal device by means of compilation to obtain characteristic data of the application program; and determine, from the scenario characteristic data set according to the characteristic data of the application program, application scenario information corresponding to the characteristic data of the application program, where the scenario characteristic data set includes a correspondence between multiple types of application scenario information and characteristic data of multiple application programs, and the application scenario information corresponding to the characteristic data of the application program is used to indicate an application scenario currently used for the terminal device.
  • the terminal device 100 may further includes a second storage 121, where the second storage 121 may be configured to store a control policy set, and the control policy set includes a correspondence between the multiple types of application scenario information and multiple power consumption control policies.
  • the processor 160 is further configured to: determine, from the control policy set according to the application scenario information, a power consumption control policy corresponding to the application scenario information; and generate a corresponding power consumption control instruction according to the power consumption control policy corresponding to the application scenario information.
  • the second storage 121 may be an external storage of the terminal device 100, and the first memory 120 may be a memory of the terminal device 100.
  • the first memory 120 may be one of: a non-volatile random access memory (NVRAM), a dynamic random access memory (DRAM), a static random access memory (SRAM), a flash memory, and the like; and the second storage 121 may be a hard disk, an optical disc, a USB disk, a floppy disk, a tape drive, or the like.
  • the input unit 130 may be configured to receive application scenario information of a newly added application scenario, corresponding characteristic data of an application program, and a corresponding power consumption control policy.
  • the processor 160 is further configured to: store, in the scenario characteristic data set in the first memory 120, the application scenario information of the newly added application scenario and the corresponding characteristic data of an application program; and store, in the control policy set in the second storage 121, the application scenario information of the newly added application scenario and the corresponding power consumption control policy.
  • the input unit 130 may be configured to receive an instruction of deleting characteristic data of an application program of a specified application scenario and a corresponding power consumption control policy.
  • the processor 160 is further configured to delete, from the scenario characteristic data set stored in the first memory 120, application scenario information of the specified application scenario and corresponding characteristic data of an application program.
  • the processor 160 is further configured to delete, from the control policy set stored in the second storage 121, the application scenario information of the specified application scenario and a corresponding power consumption control policy.
  • the input unit 130 may include a touch control panel 131.
  • the touch control panel 131 also referred to as a touchscreen, can collect a touch operation of the user on or near the touch control panel 131 (for example, an operation of the user on the touch control panel 131 or near the touch control panel 131 by using any proper object or accessory, such as a finger or a stylus), and drive a corresponding connection apparatus according to a preset program.
  • the touch control panel 131 may include two parts: a touch detection apparatus and a touch controller.
  • the touch detection apparatus detects a touch position and direction of the user, detects a signal generated from a touch operation, and transfers the signal to the touch controller; and the touch controller receives touch information from the touch detection apparatus, converts the touch information into coordinates of a touch point, sends the coordinates of a touch point to the processor 160, and can receive and execute a command sent by the processor 160.
  • the touch control panel 131 may be implemented by using multiple types such as a resistive type, a capacitive type, an infrared type, and a surface acoustic wave type.
  • the input unit 130 may further include another input device 132, where the another input device 132 may include but is not limited to one or more of: a physical keyboard, a functional button (such as a volume control button or a switch button), a trackball, a mouse, and a joystick.
  • a functional button such as a volume control button or a switch button
  • a trackball such as a mouse
  • a joystick such as a joystick
  • the terminal device 100 may further include a display unit 140, where the display unit 140 may be configured to display information input by a user or information provided for a user and various menu interfaces of the terminal device 100.
  • the display unit 140 may include a display panel 141, and optionally, the display panel 141 may be configured in a form of an liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.
  • LCD liquid crystal display
  • OLED organic light-emitting diode
  • the touch control panel 131 covers the display panel 141, so as to form a touch display screen 142.
  • the touch display screen 142 detects a touch operation on or near the touch display screen 142, the touch operation is transferred to the processor 160 to determine a type of a touch event, and afterwards, the processor 160 provides a corresponding visual output on the touch display screen 142 according to the type of the touch event.
  • the touch display screen 142 includes an application program interface display area 143 and a common control display area 144.
  • a manner of arranging the application program interface display area 143 and the common control display area 144 is not limited, and may be an arrangement manner that can distinguish two display areas, for example, arranging up and down or arranging side by side.
  • the application program interface display area 143 may be used to display an interface of an application program, where each interface may include at least one interface element such as an icon of an application program and/or a widget desktop control; or the application program interface display area 143 may be an empty interface that does not include any content.
  • the common control display area 144 is used to display a control with a relatively high usage rate, for example, an icon of an application program, such as a setting button, an interface number, a scroll bar, or a phone book icon.
  • the processor 160 is a control center of the terminal device 100 and is connected to each part of the entire mobile phone by using various interfaces and lines, and executes various functions of the terminal device 100 and processes data by running or executing a software program and/or a module that is stored in the first memory 120 and invoking data stored in the second storage 121, so as to perform overall monitoring on the terminal device 100.
  • the processor 160 may include one or multiple processing units.
  • an application program running on the terminal device is analyzed by means of compilation to obtain characteristic data of the application program; and application scenario information corresponding to the characteristic data of the application program is determined from a scenario characteristic data set according to the characteristic data of the application program, where the scenario characteristic data set includes a correspondence between multiple types of application scenario information and characteristic data of multiple application programs, and the application scenario information corresponding to the characteristic data of the application program is used to indicate an application scenario currently used for the terminal device.
  • an application program running on the terminal device is analyzed by means of compilation to obtain characteristic data of the application program. Because characteristic data of an application program is more likely to be unique in describing a corresponding application scenario, application scenario information corresponding to the characteristic data of the application program is relatively accurate. Therefore, the terminal device provided in this embodiment of the present invention can relatively accurately identify an application scenario of the terminal device, thereby further improving user experience of the terminal device.
  • an application program running on the terminal device is analyzed by means of compilation to obtain characteristic data of the application program. Because characteristic data of an application program is more likely to be unique in describing a corresponding application scenario, application scenario information corresponding to the characteristic data of the application program is relatively accurate, and further a power consumption control policy corresponding to the application scenario information is also relatively accurate. Therefore, the terminal device provided in this embodiment of the present invention can relatively accurately identify an application scenario of a terminal device, so as to relatively accurately determine a power consumption control policy, thereby further improving user experience of the terminal device.
  • the program may be stored in a computer readable storage medium.
  • the storage medium may include: a ROM, a RAM, a magnetic disk, an optical disc, or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Quality & Reliability (AREA)
  • Computing Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Mining & Analysis (AREA)
  • Stored Programmes (AREA)
  • Telephone Function (AREA)
  • Power Sources (AREA)

Claims (8)

  1. Verfahren zum Identifizieren eines Anwendungsszenarios einer Endgeräteeinrichtung, umfassend:
    Analysieren (101) eines Anwendungsprogramms, das auf einer Endgeräteeinrichtung ausgeführt wird, mittels Kompilierung, um charakteristische Daten des Anwendungsprogramms zu erhalten, wobei das Anwendungsprogramm eine oder mehrere Funktionen beinhaltet, die eine oder die mehreren Funktionen kompiliert werden und sich die charakteristischen Daten eines Anwendungsprogramms auf die eine oder die mehreren Funktionen beziehen, die in dem Anwendungsprogramm enthalten sind; und
    Bestimmen (102), aus einem szenariocharakteristischen Datensatz gemäß den charakteristischen Daten des Anwendungsprogramms, von Anwendungsszenarioinformationen entsprechend den charakteristischen Daten des Anwendungsprogramms, wobei der szenariocharakteristische Datensatz im Voraus bestimmt wird, in einer Datei oder einer Datenbank gespeichert wird und eine Korrespondenz zwischen mehreren Typen von Anwendungsszenarioinformationen und charakteristischen Daten von mehreren Anwendungsprogrammen umfasst, und die Anwendungsszenarioinformationen, die den charakteristischen Daten des Anwendungsprogramms entsprechen, zum Angeben eines Anwendungsszenarios verwendet werden, das gegenwärtig für die Endgeräteeinrichtung verwendet wird.
  2. Verfahren nach Anspruch 1, wobei die charakteristischen Daten des Anwendungsprogramms statische charakteristische Daten und dynamische charakteristische Daten umfassen; und
    wobei das Analysieren eines Anwendungsprogramms, das auf einer Endgeräteeinrichtung ausgeführt wird, mittels Kompilierung, um charakteristischen Daten des Anwendungsprogramms zu erhalten, Folgendes umfasst:
    wenn das Anwendungsprogramm ausgeführt wird, Analysieren des Anwendungsprogramms mittels Kompilierung, um eine oder mehrere Funktionen aus dem Anwendungsprogramm zu erhalten, die als die statischen charakteristische Daten dienen sollen, wobei die eine oder die mehreren Funktionen in dem Anwendungsprogramm enthalten sind und zum Unterstützen des normalen Gebrauchs einer oder mehrerer Anwendungsfunktionen in dem Anwendungsszenario, das gegenwärtig für die Endgeräteeinrichtung verwendet wird, verwendet werden; und
    wenn eine Häufigkeit des Aufrufens einer Funktion in der einen oder den mehreren Funktionen eine voreingestellte Schwelle überschreitet, Bestimmen, dass die Funktion die dynamischen charakteristischen Daten ist.
  3. Verfahren nach Anspruch 1 oder 2, wobei das Verfahren ferner Folgendes umfasst:
    Empfangen von Anwendungsszenarioinformationen eines neu hinzugefügten Anwendungsszenarios und von entsprechenden charakteristischen Daten eines Anwendungsprogramms; und
    Speichern der Anwendungsszenarioinformationen des neu hinzugefügten Anwendungsszenarios und der entsprechenden charakteristischen Daten eines Anwendungsprogramms in dem szenariocharakteristischen Datensatz.
  4. Verfahren nach Anspruch 1 oder 2, wobei das Verfahren ferner Folgendes umfasst:
    Empfangen einer Anweisung zum Löschen von charakteristischen Daten eines Anwendungsprogramms eines spezifizierten Anwendungsszenarios; und
    Löschen, aus dem szenariocharakteristischen Datensatz, von Anwendungsszenarioinformationen der spezifizierten Anwendungsszenarios und von entsprechenden charakteristischen Daten eines Anwendungsprogramms.
  5. Anwendungsszenario-Identifikationsvorrichtung (30), umfassend:
    eine Erfassungseinheit (301), die ausgelegt ist zum Analysieren eines Anwendungsprogramms, das auf einer Endgeräteeinrichtung ausgeführt wird, mittels Kompilierung, um charakteristische Daten des Anwendungsprogramms zu erhalten, wobei das Anwendungsprogramm eine oder mehrere Funktionen beinhaltet, die eine oder die mehreren Funktionen kompiliert werden und sich die charakteristischen Daten eines Anwendungsprogramms auf die eine oder die mehreren Funktionen beziehen, die in dem Anwendungsprogramm enthalten sind; und
    eine Szenariocharakteristischer-Datensatz-Verwaltungseinheit (302), die ausgelegt ist zum Bestimmen, aus einem szenariocharakteristischen Datensatz gemäß den charakteristischen Daten des Anwendungsprogramms, die durch die Erfassungseinheit erfasst werden, von Anwendungsszenarioinformationen entsprechend den charakteristischen Daten des Anwendungsprogramms, wobei der szenariocharakteristische Datensatz im Voraus bestimmt wird, in einer Datei oder einer Datenbank gespeichert wird und eine Korrespondenz zwischen mehreren Typen von Anwendungsszenarioinformationen und charakteristischen Daten von mehreren Anwendungsprogrammen umfasst und die Anwendungsszenarioinformationen, die den charakteristischen Daten des Anwendungsprogramms entsprechen, zum Angeben eines Anwendungsszenarios verwendet werden, das gegenwärtig für die Endgeräteeinrichtung verwendet wird.
  6. Identifikationsvorrichtung (30) nach Anspruch 5, wobei die charakteristischen Daten des Anwendungsprogramms statische charakteristische Daten und dynamische charakteristische Daten umfassen; und die Erfassungseinheit (301) Folgendes umfasst:
    eine Erfassungsuntereinheit (3011), die, wenn das Anwendungsprogramm ausgeführt wird, ausgelegt ist zum Analysieren des Anwendungsprogramms mittels Kompilierung, um eine oder mehrere Funktionen aus dem Anwendungsprogramm zu erhalten, die als die statischen charakteristischen Daten dienen sollen, wobei die eine oder die mehreren Funktionen in dem Anwendungsprogramm enthalten sind und zum Unterstützen des normalen Gebrauchs einer oder mehrerer Anwendungsfunktionen in dem Anwendungsszenario, das gegenwärtig für die Endgeräteeinrichtung verwendet wird, verwendet werden; und
    eine Bestimmungsuntereinheit (3012), die, wenn eine durch die Erfassungsuntereinheit (3011) erfasste Häufigkeit des Aufrufens einer Funktion in einer oder mehreren Funktionen eine voreingestellte Schwelle überschreitet, ausgelegt ist zum Bestimmen, dass die Funktion die dynamischen charakteristischen Daten ist.
  7. Identifikationsvorrichtung (30) nach Anspruch 5 oder 6, wobei die Identifikationsvorrichtung (30) ferner eine Empfangseinheit (303) umfasst, wobei die Empfangseinheit (303) ausgelegt ist zum Empfangen von Anwendungsszenarioinformationen eines neu hinzugefügten Anwendungsszenarios und von entsprechenden charakteristischen Daten eines Anwendungsprogramms; und die Szenariocharakteristischer-Datensatz-Verwaltungseinheit (302) ferner ausgelegt ist zum Speichern der Anwendungsszenarioinformationen des neu hinzugefügten Anwendungsszenarios und der entsprechenden charakteristischen Daten eines Anwendungsprogramms, die durch die Empfangseinheit (303) empfangen werden, in dem szenariocharakteristischen Datensatz.
  8. Identifikationsvorrichtung (30) nach Anspruch 7, wobei
    die Empfangseinheit (303) ferner ausgelegt ist zum Empfangen einer Anweisung zum Löschen von charakteristischen Daten eines Anwendungsprogramms eines spezifizierten Anwendungsszenarios; und
    die Szenariocharakteristischer-Datensatz-Verwaltungseinheit (302) ferner ausgelegt ist zum Löschen, aus dem szenariocharakteristischen Datensatz gemäß der durch die Empfangseinheit (303) empfangenen Anweisung, von Anwendungsszenarioinformationen der spezifizierten Anwendungsszenarios und von entsprechenden charakteristischen Daten eines Anwendungsprogramms.
EP14879273.2A 2014-03-27 2014-10-17 Verfahren zur identifikation eines anwendungsszenarios, stromverbrauchverwaltungsverfahren und -vorrichtung und endgerät Active EP2950203B1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410119905.0A CN103984538B (zh) 2014-03-27 2014-03-27 应用场景的识别方法、功耗管理方法、装置及终端设备
PCT/CN2014/088793 WO2015143865A1 (zh) 2014-03-27 2014-10-17 应用场景的识别方法、功耗管理方法、装置及终端设备

Publications (3)

Publication Number Publication Date
EP2950203A1 EP2950203A1 (de) 2015-12-02
EP2950203A4 EP2950203A4 (de) 2016-09-07
EP2950203B1 true EP2950203B1 (de) 2020-04-22

Family

ID=51276532

Family Applications (1)

Application Number Title Priority Date Filing Date
EP14879273.2A Active EP2950203B1 (de) 2014-03-27 2014-10-17 Verfahren zur identifikation eines anwendungsszenarios, stromverbrauchverwaltungsverfahren und -vorrichtung und endgerät

Country Status (7)

Country Link
US (1) US9813297B2 (de)
EP (1) EP2950203B1 (de)
JP (1) JP6195182B2 (de)
KR (1) KR101790190B1 (de)
CN (1) CN103984538B (de)
TW (1) TWI529524B (de)
WO (1) WO2015143865A1 (de)

Families Citing this family (47)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10699261B2 (en) 2010-03-02 2020-06-30 Shopkeep Inc. System and method for remote management of sale transaction data
US9317844B2 (en) 2010-03-02 2016-04-19 Shopkeep.Com, Inc. System and method for remote management of sale transaction data
CN103984538B (zh) 2014-03-27 2017-04-26 华为技术有限公司 应用场景的识别方法、功耗管理方法、装置及终端设备
US11610197B1 (en) 2014-04-30 2023-03-21 Wells Fargo Bank, N.A. Mobile wallet rewards redemption systems and methods
US11461766B1 (en) 2014-04-30 2022-10-04 Wells Fargo Bank, N.A. Mobile wallet using tokenized card systems and methods
US11288660B1 (en) 2014-04-30 2022-03-29 Wells Fargo Bank, N.A. Mobile wallet account balance systems and methods
US9652770B1 (en) 2014-04-30 2017-05-16 Wells Fargo Bank, N.A. Mobile wallet using tokenized card systems and methods
US10445739B1 (en) 2014-08-14 2019-10-15 Wells Fargo Bank, N.A. Use limitations for secondary users of financial accounts
TWI536150B (zh) * 2014-11-03 2016-06-01 緯創資通股份有限公司 電子裝置及其溫度控制方法
CN104598008B (zh) * 2014-12-30 2017-07-11 中科创达软件股份有限公司 安卓设备的功耗控制方法
CN106155655A (zh) * 2015-04-03 2016-11-23 阿里巴巴集团控股有限公司 一种应用程序的管理方法和装置
WO2017094263A1 (ja) * 2015-12-04 2017-06-08 日本電気株式会社 ログ分析システム、方法およびプログラム
CN105528055B (zh) * 2015-12-30 2018-11-23 小米科技有限责任公司 运行对象的处理方法及装置
CN107027143A (zh) * 2016-01-29 2017-08-08 中国移动通信集团贵州有限公司 一种信息获取方法和装置
CN106095592B (zh) * 2016-05-31 2021-08-24 Oppo广东移动通信有限公司 一种前景应用程序场景同步方法及装置、系统
CN106201679A (zh) * 2016-06-28 2016-12-07 联想(北京)有限公司 信息处理方法及电子设备
US10348604B2 (en) * 2017-02-01 2019-07-09 International Business Machines Corporation Monitoring a resource consumption of an application
CN106919400A (zh) * 2017-03-10 2017-07-04 广东欧珀移动通信有限公司 一种移动终端的显示场景识别方法、装置及移动终端
CN107422835A (zh) * 2017-08-03 2017-12-01 四川长虹通信科技有限公司 一种终端视频播放场景自适应节能方法及装置
CN107577536A (zh) * 2017-08-31 2018-01-12 广东欧珀移动通信有限公司 应用优化方法及相关产品
CN107621981A (zh) * 2017-09-06 2018-01-23 广东欧珀移动通信有限公司 资源配置方法及相关产品
CN107797868B (zh) * 2017-10-31 2020-09-25 Oppo广东移动通信有限公司 资源调整方法及装置
CN107861603A (zh) * 2017-10-31 2018-03-30 广东欧珀移动通信有限公司 功耗控制方法及设备
CN108037999A (zh) 2017-12-06 2018-05-15 广东欧珀移动通信有限公司 资源配置方法及相关产品
CN108170252B (zh) * 2017-12-26 2020-05-05 中国联合网络通信集团有限公司 一种终端节电方法及装置
CN110018861B (zh) * 2018-01-08 2023-05-05 视联动力信息技术股份有限公司 一种应用程序的消息提示方法和装置
CN108989547B (zh) * 2018-06-20 2021-03-16 Oppo广东移动通信有限公司 发光控制方法、装置、终端及存储介质
CN109144649B (zh) * 2018-08-22 2020-12-29 Oppo广东移动通信有限公司 图标的显示方法、装置、终端及存储介质
US12254463B1 (en) 2018-08-30 2025-03-18 Wells Fargo Bank, N.A. Biller directory and payments engine architecture
US12045809B1 (en) 2018-08-30 2024-07-23 Wells Fargo Bank, N.A. Biller consortium enrollment and transaction management engine
CN111065114B (zh) * 2018-10-17 2021-12-28 华为技术有限公司 节能管理方法、装置及存储介质
CN109669528B (zh) * 2018-12-20 2021-06-04 Oppo广东移动通信有限公司 终端的处理组件控制方法、装置、计算机设备及存储介质
CN109726303A (zh) * 2018-12-28 2019-05-07 维沃移动通信有限公司 一种图像推荐方法和终端
CN111382768B (zh) * 2018-12-29 2023-11-14 华为技术有限公司 多传感器数据融合方法和装置
CN109992315B (zh) * 2019-04-09 2022-03-25 Oppo广东移动通信有限公司 触摸屏控制方法、装置、终端及存储介质
CN109992348A (zh) * 2019-04-10 2019-07-09 Oppo广东移动通信有限公司 界面显示方法、装置、终端及存储介质
CN110086938A (zh) * 2019-04-29 2019-08-02 百度在线网络技术（北京）有限公司 投屏显示的控制方法、系统、电子设备及计算机可读介质
US11551190B1 (en) 2019-06-03 2023-01-10 Wells Fargo Bank, N.A. Instant network cash transfer at point of sale
CN112825539B (zh) * 2019-11-20 2022-10-14 联发科技股份有限公司 硬件管理方法及相关联的机器可读介质、电子设备
CN111191720B (zh) * 2019-12-30 2023-08-15 中国建设银行股份有限公司 一种业务场景的识别方法、装置及电子设备
US11671361B2 (en) * 2020-05-11 2023-06-06 Arista Networks, Inc. Centralized management and distributed enforcement of policies for network segmentation
CN113613074B (zh) * 2021-07-27 2023-08-18 Oppo广东移动通信有限公司 直播场景检测方法、装置、终端及存储介质
US12229735B1 (en) 2021-08-17 2025-02-18 Wells Fargo Bank, N.A. Multi-modal parameterization of digital tokens involving multiple entities in defined networks
CN115996451A (zh) * 2021-10-19 2023-04-21 北京小米移动软件有限公司 通信功耗确定方法、装置、电子设备及存储介质
CN113656258B (zh) * 2021-10-20 2022-02-01 深圳市瑞荣达电子有限公司 基于互联网的智能蓝牙耳机用场景分析管控系统
US11995621B1 (en) 2021-10-22 2024-05-28 Wells Fargo Bank, N.A. Systems and methods for native, non-native, and hybrid registration and use of tags for real-time services
CN115649083A (zh) * 2022-10-27 2023-01-31 重庆长安汽车股份有限公司 基于车机的场景识别及功耗策略规划方法、系统及设备

Family Cites Families (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000222057A (ja) 1999-01-29 2000-08-11 Toshiba Corp 情報処理システムおよび自動停止時間の最適化方法
US6901522B2 (en) 2001-06-07 2005-05-31 Intel Corporation System and method for reducing power consumption in multiprocessor system
US20030014742A1 (en) 2001-07-09 2003-01-16 Sasken Communication Technologies Limited Technique for compiling computer code to reduce energy consumption while executing the code
EP1313012A1 (de) 2001-11-15 2003-05-21 Texas Instruments France Java DSP-Beschleunigung durch Bytekodeoptimierung
US7278136B2 (en) 2002-07-09 2007-10-02 University Of Massachusetts Reducing processor energy consumption using compile-time information
TWI237793B (en) 2004-03-12 2005-08-11 Abit Comp Corp Method for automatically changing configured values of hardware in computer system in accordance with executing application program
US7904893B2 (en) 2004-03-17 2011-03-08 Marvell International Ltd. Power and/or energy optimized compile/execution
TW200538910A (en) 2004-05-31 2005-12-01 Acer Inc Power management system and method for computer system
US8041968B2 (en) * 2007-01-04 2011-10-18 Apple Inc. Power management for driving display with baseband portion when application portion is in low power mode
CN100517180C (zh) * 2007-06-01 2009-07-22 惠州市Tcl电脑科技有限责任公司 一种智能电源管理方法和系统
US8538484B2 (en) * 2009-08-14 2013-09-17 Google Inc. Providing a user with feedback regarding power consumption in battery-operated electronic devices
US20110154309A1 (en) 2009-12-22 2011-06-23 Apple Inc. Compiler with energy consumption profiling
CN102148805B (zh) * 2010-02-09 2015-04-08 华为技术有限公司 特征匹配方法和装置
US9325929B2 (en) * 2010-04-29 2016-04-26 Ati Technologies Ulc Power management in multi-stream audio/video devices
US9098333B1 (en) * 2010-05-07 2015-08-04 Ziften Technologies, Inc. Monitoring computer process resource usage
CN102156530B (zh) * 2010-09-30 2013-08-28 华为终端有限公司 移动终端的功耗管理方法和装置
WO2012071989A1 (zh) * 2010-11-29 2012-06-07 北京奇虎科技有限公司 基于机器学习的程序识别方法及装置
KR20120064446A (ko) 2010-12-09 2012-06-19 삼성전자주식회사 컴퓨팅 시스템 상의 바이트코드의 분기 처리 장치 및 방법
CN102098392B (zh) 2011-01-25 2014-03-19 中兴通讯股份有限公司 一种便携式终端的节能装置和方法
JP5598375B2 (ja) 2011-02-22 2014-10-01 富士通株式会社 プログラムに含まれるコードをメモリ領域に割り当てる割当方法及びその方法を実行するメモリシステム
JP2013045373A (ja) * 2011-08-25 2013-03-04 Fujitsu Ltd 情報処理装置、制御プログラム及び制御方法
JP5085780B2 (ja) 2011-11-25 2012-11-28 京セラ株式会社 携帯端末及びその制御方法
US9164803B2 (en) * 2012-01-20 2015-10-20 Microsoft Technology Licensing, Llc Background task resource control
CN102779257B (zh) * 2012-06-28 2015-10-07 北京奇虎科技有限公司 一种Android应用程序的安全检测方法及系统
CN103544088A (zh) * 2013-09-30 2014-01-29 东莞宇龙通信科技有限公司 一种检测终端功耗异常的方法及装置
US9652362B2 (en) 2013-12-06 2017-05-16 Qualcomm Incorporated Methods and systems of using application-specific and application-type-specific models for the efficient classification of mobile device behaviors
CN103984538B (zh) * 2014-03-27 2017-04-26 华为技术有限公司 应用场景的识别方法、功耗管理方法、装置及终端设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
TW201537343A (zh) 2015-10-01
KR101790190B1 (ko) 2017-10-25
TWI529524B (zh) 2016-04-11
JP6195182B2 (ja) 2017-09-13
US9813297B2 (en) 2017-11-07
EP2950203A1 (de) 2015-12-02
EP2950203A4 (de) 2016-09-07
WO2015143865A1 (zh) 2015-10-01
KR20150128671A (ko) 2015-11-18
CN103984538B (zh) 2017-04-26
CN103984538A (zh) 2014-08-13
JP2016527578A (ja) 2016-09-08
US20150333964A1 (en) 2015-11-19

Similar Documents

Publication Publication Date Title
EP2950203B1 (de) Verfahren zur identifikation eines anwendungsszenarios, stromverbrauchverwaltungsverfahren und -vorrichtung und endgerät
US10990644B2 (en) Systems and methods for contextual vocabularies and customer segmentation
EP3343378B1 (de) Vorrichtungsbasierte visuelle testautomation
US20230409182A1 (en) Rule-based user interface layout rearrangement
JP2021511592A (ja) アプリケーションプログラム処理方法、装置、記憶媒体及びコンピュータデバイス
KR102193404B1 (ko) 상호작용 개발 환경으로부터의 소프트웨어 아티팩트의 점진적 컴파일링 기법
US11221881B2 (en) Computer resource leak detection
CN104850296B (zh) 显示页面内容的方法及装置
CN113032273B (zh) 一种应用程序的调试方法、装置、计算机设备和存储介质
CN103927198A (zh) 一种软件清理方法及装置
WO2014194654A1 (en) Method and apparatus for page view switching
US10552233B2 (en) Application convergence method and apparatus
CN111330280A (zh) 游戏中的数据处理方法、装置、存储介质与电子设备
US20140365960A1 (en) Method and apparatus for page view switching
CN107077319A (zh) 基于语音控制的位置定位方法、装置、用户设备及计算机程序产品
CN111385661B (zh) 语音控制全屏播放的方法、装置、终端及存储介质
CN112988265B (zh) 小程序处理方法、小程序处理装置、设备、介质和产品
CN113110846A (zh) 一种环境变量的获取方法及装置
US12235759B2 (en) Pointer-based sharing of a data structure between threads
CN119292619A (zh) 应用程序处理方法、装置、设备及介质
CN115700468A (zh) 用于应用程序的地址跳转方法及装置、计算机设备和介质
CN121210183A (zh) 超时处理方法、装置、存储介质和电子设备
CN118963864A (zh) 应用程序的业务数据处理方法、装置、设备及介质
WO2025025528A1 (zh) 应用程序控制方法、装置
EP4649400A1 (de) Instrumentenbasierte erkennung von unerwünschter algorithmischer komplexität eines verfahrens

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20150730

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

A4 Supplementary search report drawn up and despatched

Effective date: 20160808

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 11/30 20060101ALI20160802BHEP

Ipc: G06F 9/445 20060101ALI20160802BHEP

Ipc: H04L 12/26 20060101ALI20160802BHEP

Ipc: G06F 1/32 20060101ALI20160802BHEP

Ipc: G06F 9/455 20060101ALI20160802BHEP

Ipc: G06F 9/44 20060101AFI20160802BHEP

Ipc: H04L 12/24 20060101ALI20160802BHEP

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: HUAWEI TECHNOLOGIES CO., LTD.

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20170426

DAX Request for extension of the european patent (deleted)
REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602014064309

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G06F0009440000

Ipc: G06F0008710000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 12/24 20060101ALI20191030BHEP

Ipc: G06F 1/32 20190101ALI20191030BHEP

Ipc: H04L 12/26 20060101ALI20191030BHEP

Ipc: G06F 9/455 20180101ALI20191030BHEP

Ipc: G06F 9/44 20180101ALI20191030BHEP

Ipc: G06F 11/30 20060101ALI20191030BHEP

Ipc: G06F 9/445 20180101ALI20191030BHEP

Ipc: G06F 8/71 20180101AFI20191030BHEP

Ipc: G06F 1/3203 20190101ALI20191030BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20191205

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602014064309

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1261010

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200515

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20200422

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200824

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200723

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200722

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200822

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1261010

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200422

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200722

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602014064309

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20210125

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201017

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20201031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201031

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201031

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201017

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200422

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20250904

Year of fee payment: 12

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20250908

Year of fee payment: 12

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20250902

Year of fee payment: 12