CN112671672A - Application flow control method, device, equipment and readable storage medium - Google Patents
Application flow control method, device, equipment and readable storage medium Download PDFInfo
- Publication number
- CN112671672A CN112671672A CN202011492035.3A CN202011492035A CN112671672A CN 112671672 A CN112671672 A CN 112671672A CN 202011492035 A CN202011492035 A CN 202011492035A CN 112671672 A CN112671672 A CN 112671672A
- Authority
- CN
- China
- Prior art keywords
- application
- traffic
- background
- traffic information
- exited
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 71
- 230000005540 biological transmission Effects 0.000 claims description 58
- 238000004891 communication Methods 0.000 description 7
- 230000007547 defect Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000013210 evaluation model Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000003062 neural network model Methods 0.000 description 1
- 239000013598 vector Substances 0.000 description 1
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application discloses an application flow control method, an application flow control device, application flow control equipment and a readable storage medium, wherein the application flow control method comprises the following steps: the method comprises the steps of obtaining first flow information of foreground application, determining whether the foreground application is in a easy-to-jam state or not based on the first flow information, obtaining second flow information and idle flow information of each background application if the foreground application is in the easy-to-jam state, and selecting a target application from each background application to exit based on the second flow information and the idle flow information. The application solves the technical problem that the running of the intelligent large-screen foreground application is blocked.
Description
Technical Field
The present application relates to the field of smart home technologies, and in particular, to a method, an apparatus, a device, and a readable storage medium for controlling application traffic.
Background
With the rapid development of the intelligent large screen technology, the intelligent large screen can meet the requirement that a plurality of applications in a foreground and a background run simultaneously, when background applications occupy most of flow, foreground application running is relatively blocked, at present, the background process is generally released by manually finishing the background process by a user or finished by an application APP (system manager) to ensure that the foreground application can run smoothly, but because the user generally perceives that the foreground application runs blocked, the background process is manually finished to release the flow, at the moment, a foreground application interface is relatively blocked, the user is difficult to quickly finish the background process through manual operation, and the problem that the foreground application runs blocked cannot be well solved.
Disclosure of Invention
The application mainly aims to provide an application flow control method, an application flow control device, application flow control equipment and a readable storage medium, and aims to solve the technical problem that an intelligent large-screen foreground application runs unsmooth in the prior art.
In order to achieve the above object, the present application provides an application traffic control method, where the application traffic control method is applied to an application traffic control device, and the application traffic control method includes:
acquiring first traffic information of foreground application, and determining whether the foreground application is in a stuck-prone state or not based on the first traffic information;
if yes, second flow information and idle flow information of each background application are obtained;
and selecting a target application from the background applications to quit based on the second traffic information and the idle traffic information.
The present application further provides an application flow control device, the application flow control device is a virtual device, and the application flow control device is applied to an application flow control apparatus, the application flow control device includes:
the determining module is used for acquiring first traffic information of foreground application and determining whether the foreground application is in a easy-to-jam state or not based on the first traffic information;
the acquisition module is used for acquiring second traffic information and idle traffic information of each background application if the first traffic information and the idle traffic information are the same;
and the selecting and exiting module is used for selecting the target application from the background applications to exit based on the second traffic information and the idle traffic information.
The present application further provides an application traffic control device, where the application traffic control device is an entity device, and the application traffic control device includes: a memory, a processor and a program of the application traffic control method stored on the memory and executable on the processor, the program of the application traffic control method when executed by the processor being operable to implement the steps of the application traffic control method as described above.
The present application also provides a readable storage medium having stored thereon a program for implementing an application traffic control method, which when executed by a processor implements the steps of the application traffic control method as described above.
Compared with the technical means that the background process is manually finished by a user to release flow or the background process is finished by applying an APP (application), so as to ensure that foreground application can smoothly run, the technical means that the background process is manually finished by the user to release flow or the background process is finished by applying the APP is provided, wherein the foreground application is already in a stuck state when the background process is manually finished by the user or the background process is finished by applying the APP, and the user is required to operate in the stuck state when the background process is finished, so that the foreground application can still be in the stuck state within a period of time, the application firstly obtains first flow information of the foreground application, determines whether the foreground application is in an easy-to-stuck state based on the first flow information, and further realizes early warning on whether the foreground application is about to be in the stuck state, and if so, acquiring second flow information and idle flow information of each background application, and selecting a target application from each background application to quit based on the second flow information and the idle flow information, that is, when the foreground application is in the easy-to-jam state, finding out the background application with relatively more occupied flow from each background application through the second flow information and the idle flow information to close, thereby realizing automatic release of the occupied flow of the background application, ensuring that the foreground application cannot be converted from the easy-to-jam state to the jam state, overcoming the technical defects that the foreground application is already in the jam state when the background process is released by manually finishing the background process by a user or the background process is finished by the application APP, the foreground application needs to operate in the jam state when the process is finished, and further leading the foreground application to still be in the jam state within a period of time, therefore, the running smoothness of the foreground application is improved, and the foreground application cannot be jammed during running.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art to obtain other drawings without inventive exercise.
Fig. 1 is a schematic flow chart of a first embodiment of a flow control method applied in the present application;
fig. 2 is a schematic flow chart of a second embodiment of a flow control method applied in the present application;
fig. 3 is a schematic device structure diagram of a hardware operating environment according to an embodiment of the present application.
The objectives, features, and advantages of the present application will be further described with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
In a first embodiment of an application traffic control method of the present application, referring to fig. 1, the application traffic control method includes:
step S10, acquiring first traffic information of foreground application, and determining whether the foreground application is in easy-to-jam state based on the first traffic information;
in this embodiment, it should be noted that the application flow control method is applied to an intelligent large screen, the foreground application is an application running in a foreground of the intelligent large screen, for example, a video type application, and the first flow information includes a foreground application data transmission speed, where the foreground application data transmission speed is an upload and download speed required by the foreground application when the foreground application runs.
Acquiring first traffic information of a foreground application, and determining whether the foreground application is in an easy-to-jam state or not based on the first traffic information, specifically, acquiring a foreground application data transmission speed and a network bandwidth speed of the foreground application, further calculating a ratio of the foreground application data transmission speed in the network bandwidth speed, acquiring a foreground application traffic ratio, further determining whether the foreground application traffic ratio is greater than a preset foreground application traffic ratio threshold value or not, if so, determining that the foreground application is in the easy-to-jam state, otherwise, determining that the foreground application is not in the easy-to-jam state, wherein if needing to be described, if the foreground application is in the easy-to-jam state, the probability of the foreground running jam is higher.
Additionally, in another possible implementation, the step of obtaining first traffic information of a foreground application and determining whether the foreground application is in a cockayment-prone state based on the first traffic information may be further implemented by:
collecting the application type of foreground application, the foreground application data transmission speed, the background application data transmission speed and the network bandwidth speed, inputting feature representation data which is composed of the application type, the foreground application data transmission speed, the background application data transmission speed and the network bandwidth speed into a preset stuck evaluation model, and identifying whether the foreground application is in a stuck state or not, wherein the feature representation data comprises feature representation vectors which can be obtained by splicing the coding information of the application type, the foreground application data transmission speed coding information, the background application data transmission speed coding information and the network bandwidth speed coding information, the preset stuck evaluation model is a pre-trained neural network model and is used for carrying out secondary classification on the current state of the foreground application, the classification of the two classifications corresponding to the current state of the foreground application is a stuck state classification and a non-stuck state classification.
Further, in step S10, the first traffic information includes foreground application data transmission speed,
the step of determining whether the foreground application is in a stuck-prone state based on the first traffic information comprises:
step A10, if the data transmission speed of the foreground application is greater than a preset data transmission speed threshold, determining that the foreground application is in the easy-to-jam state; or
Step a20, if the foreground application data transmission speed is not greater than the preset data transmission speed threshold, determining that the foreground application is not in the easy-to-jam state.
In this embodiment, it should be noted that, if the foreground application is in an easy-to-jam state, the probability of the foreground running being stuck is relatively high, and if the foreground application is not in the easy-to-jam state, the probability of the foreground running being stuck is relatively low, the preset data transmission speed threshold is a data transmission speed threshold set based on the network bandwidth speed of the current network environment, for example, assuming that the network bandwidth speed is 100M per second, the preset data transmission speed threshold may be set to 10% of the network bandwidth speed, that is, 10M per second, and the higher the proportion of the network bandwidth speed occupied by the foreground application data transmission data is, the more easy the foreground running is.
Further, in step S10, the first traffic information includes a data transmission speed fluctuation value,
the step of determining whether the foreground application is in a stuck-prone state based on the first traffic information comprises:
step B10, if the data transmission speed fluctuation value is greater than a preset idle data transmission speed threshold value, determining that the foreground application is in the easy-to-jam state; or
Step B20, if the foreground application data transmission speed is not greater than the preset data transmission speed threshold, determining that the foreground application is not in the easy-to-jam state.
In this embodiment, if the fluctuation value of the data transmission rate is not greater than the preset idle data transmission rate threshold, determining that the foreground application is not in the stuck-prone state, in particular, acquiring idle traffic, wherein the idle traffic is an unoccupied data transmission rate in the network bandwidth speed, and further calculates a preset idle data transmission rate threshold value based on a product of a preset weight value and the idle traffic, determines whether the data transmission rate fluctuation value is greater than the preset idle data transmission rate threshold value, wherein the data transmission speed fluctuation value is a difference value between a maximum data transmission speed and a minimum data transmission speed when the foreground application performs data transmission, if yes, indicating that the maximum data transmission speed of the foreground application during data transmission occupies more network bandwidth speed, and further judging that the foreground application is in the easy-to-jam state; if not, the maximum data transmission speed of the foreground application during data transmission occupies less network bandwidth speed, and then the foreground application is judged not to be in the easy-to-jam state.
Step S20, if yes, second traffic information and idle traffic information of each background application are obtained;
in this embodiment, it should be noted that the second traffic information includes background application traffic during the running of each background application, where the background application traffic is a data transmission speed required by the running of the background application for uploading and downloading, the idle traffic information is idle traffic, and the idle traffic is an unoccupied data transmission speed in a network bandwidth speed.
Step S30, based on the second traffic information and the idle traffic information, selecting a target application from each of the background applications to exit.
In this embodiment, based on the second traffic information and the idle traffic information, a target application is selected from each background application for exiting, and specifically, each background application traffic is sequenced to select a background application traffic to be exited from each background application traffic, for example, background application traffic ranked first three may be ranked from large to small, and background application traffic ranked first three is selected as background application traffic to be exited, and then background application traffic to be exited that is higher than the idle traffic is used as the target application traffic, and a target application corresponding to the target application traffic is exited, that is, the target application is exited to release traffic occupied by the background application, so that the foreground application is prevented from being stuck.
Compared with the technical means that the background process is manually finished by a user to release flow or the background process is finished by an application APP to ensure that foreground application can smoothly run in the prior art, the embodiment of the application needs to explain that the foreground application is already in a stuck state when the background process is manually finished by the user to release flow or the background process is finished by the application APP, and needs to operate in the stuck state when the background process is finished, so that the foreground application still can be in the stuck state within a period of time, firstly, first flow information of the foreground application is obtained, and whether the foreground application is in the easy-to-stuck state is determined based on the first flow information, so that early warning whether the foreground application is about to be in the stuck state is realized, and if so, acquiring second flow information and idle flow information of each background application, and selecting a target application from each background application to quit based on the second flow information and the idle flow information, that is, when the foreground application is in the easy-to-jam state, finding out the background application with relatively more occupied flow from each background application through the second flow information and the idle flow information to close, thereby realizing automatic release of the occupied flow of the background application, ensuring that the foreground application cannot be converted from the easy-to-jam state to the jam state, overcoming the technical defects that the foreground application is already in the jam state when the background process is released by manually finishing the background process by a user or the background process is finished by the application APP, the foreground application needs to operate in the jam state when the process is finished, and further leading the foreground application to still be in the jam state within a period of time, therefore, the running smoothness of the foreground application is improved, and the foreground application cannot be jammed during running.
Further, referring to fig. 2, according to the first embodiment of the present application, the step of selecting a target application from each background application to exit based on the second traffic information and the idle traffic information includes:
step S31, acquiring network bandwidth speed, and selecting background applications to be exited from each background application based on the network bandwidth speed and the second traffic information;
in this embodiment, a network bandwidth speed is obtained, background applications to be exited are selected from the background applications based on the network bandwidth speed and the second traffic information, specifically, the network bandwidth speed is obtained, a traffic proportion of each background application traffic in the network bandwidth speed is calculated, a target traffic proportion exceeding a preset traffic proportion threshold is selected from the traffic proportions based on each traffic proportion, and the background application corresponding to the target traffic proportion is used as the background application to be exited.
Further, in step S31, the second traffic information at least includes a background application traffic,
the step of selecting the background application to be exited from among the background applications based on the network bandwidth speed and the second traffic information includes:
step S311, calculating the application traffic ratio corresponding to each background application based on the network bandwidth speed and each background application traffic;
in this embodiment, based on the network bandwidth speed and each background application traffic, an application traffic ratio corresponding to each background application is calculated, specifically, a ratio between each background application traffic and the network bandwidth speed is calculated, and an application traffic ratio corresponding to each background application is obtained.
Step S312, based on the traffic ratio of each application, selecting the background application to be exited from each background application.
In this embodiment, the background application to be exited is selected from each background application based on each application traffic proportion, specifically, a target application traffic proportion is selected from each application traffic proportion based on the size of each application traffic proportion, and the background application corresponding to the target application traffic proportion is used as the background application to be exited.
Step S32, respectively determining whether each background application to be exited needs to be exited based on the idle traffic information and the second traffic information;
in this embodiment, it should be noted that the idle traffic information includes idle traffic, and the second traffic information at least includes application traffic to be exited of a background application to be exited.
Respectively determining whether each background application to be exited needs to be exited or not based on the idle traffic information and the second traffic information, specifically, respectively comparing the traffic of each application to be exited with the idle traffic to obtain a size comparison result, and respectively determining whether each background application to be exited needs to be exited or not based on the size comparison result.
Further, in step S32, the idle traffic information includes network idle traffic, the second traffic information at least includes application traffic to be exited,
the step of respectively determining whether each background application to be exited needs to be exited based on the idle traffic information and the second traffic information includes:
step S321, if the application traffic to be exited is greater than the network idle traffic, determining that the background application to be exited corresponding to the application traffic to be exited needs to be exited; or
In this embodiment, it should be noted that the network idle traffic is traffic that is not occupied by an application.
If the application traffic to be exited is greater than the network idle traffic, determining that the background application to be exited corresponding to the application traffic to be exited needs to be exited, specifically, if the application traffic to be exited is greater than the network idle traffic, proving that the application traffic to be exited is relatively high, that is, the background application to be exited corresponding to the application traffic to be exited occupies too much traffic, and further determining that the background application to be exited corresponding to the application traffic to be exited needs to be exited, so as to release the traffic occupied by the background application to be exited.
Step S322, if the application traffic to be exited is not greater than the network idle traffic, determining that the background application to be exited corresponding to the application traffic to be exited does not need to be exited.
In this embodiment, if the application traffic to be exited is not greater than the network idle traffic, it is determined that the background application to be exited corresponding to the application traffic to be exited does not need to be exited, specifically, if the application traffic to be exited is not greater than the network idle traffic, it is verified that the application traffic to be exited is low, that is, the traffic occupied by the background application to be exited corresponding to the application traffic to be exited is low, and it is determined that the background application to be exited corresponding to the application traffic to be exited does not need to be exited.
Further, in step S32, the idle traffic information includes wireless network idle traffic, the second traffic information at least includes application traffic to be exited,
the step of respectively determining whether each background application to be exited needs to be exited based on the idle traffic information and the second traffic information includes:
step C10, acquiring a wireless network fluctuation value, and calculating a safety flow threshold value based on the wireless network idle flow and the wireless network fluctuation value;
in this embodiment, it should be noted that, when the network is a wireless network, the network has a high possibility of fluctuation, and the wireless network fluctuation value is a difference between the maximum traffic of the wireless network and the minimum traffic of the wireless network, for example, assuming that the peak value of the wireless network is 50M per second and the valley value is 47M per second, the wireless network fluctuation value is 3M per second.
The method comprises the steps of obtaining a wireless network fluctuation value, calculating a safety flow threshold value based on the wireless network idle flow and the wireless network fluctuation value, specifically, obtaining the wireless network fluctuation value, calculating a difference value between the wireless network idle flow and the wireless network fluctuation value, obtaining the safety idle flow, further calculating a product between the safety idle flow and a preset weight coefficient, and obtaining the safety flow threshold value.
Step C20, if the application traffic to be exited is greater than the safety traffic threshold, determining that the background application to be exited corresponding to the application traffic to be exited needs to be exited; or
In this embodiment, if the application traffic to be exited is greater than the safety traffic threshold, it is determined that the background application to be exited corresponding to the application traffic to be exited needs to be exited, specifically, if the application traffic to be exited is greater than the safety traffic threshold, it is verified that the application traffic to be exited is relatively high, that is, the background application to be exited corresponding to the application traffic to be exited occupies too much traffic, and it is determined that the background application to be exited corresponding to the application traffic to be exited needs to be exited, so as to release the traffic occupied by the background application to be exited.
Step C30, if the application traffic to be exited is not greater than the safety traffic threshold, determining that the background application to be exited corresponding to the application traffic to be exited does not need to be exited.
In this embodiment, if the application traffic to be exited is not greater than the safety traffic threshold, it is determined that the background application to be exited corresponding to the application traffic to be exited does not need to be exited, specifically, if the application traffic to be exited is not greater than the safety traffic threshold, it is verified that the application traffic to be exited is relatively low, that is, the traffic occupied by the background application to be exited corresponding to the application traffic to be exited is relatively low, and it is determined that the background application to be exited corresponding to the application traffic to be exited does not need to be exited.
It should be noted that, in this embodiment, a safety traffic threshold is calculated based on the wireless network idle traffic and the wireless network fluctuation value, and then based on the safety traffic threshold, whether the background application to be exited needs to be exited is determined, and then a network fluctuation factor is added to a decision factor for determining whether the background application to be exited needs to be exited, so that a decision for determining whether the background application to be exited needs to be exited is more accurate.
And step S33, if yes, taking the background application to be exited that needs to be exited as the target application, and exiting the target application.
In this embodiment, if yes, the background application to be exited, which needs to be exited, is taken as the target application, and an exit command is sent to control the intelligent large screen to exit the background application to be exited.
The embodiment provides a method for selecting a target application from each background application, and after selecting the target application, the target application can be quitted, and when the foreground application is in the easy-to-jam state, the target application can be quitted by the second flow information and the idle flow information, finding out background applications occupying more traffic from each background application to close the background applications, further, the automatic release of the occupied flow of the background application is realized, so as to ensure that the foreground application is not converted from the easy-to-jam state to the jam state, and in order to overcome the defect that when the background process is released by the manual termination of the background process by a user or the background process is terminated by the application APP in the prior art, the foreground application is already in the stuck state, and when the background process is finished, the user is required to operate in the stuck state, and further lays a foundation for the technical defect that the foreground application still stays in a stuck state for a period of time.
Referring to fig. 3, fig. 3 is a schematic device structure diagram of a hardware operating environment according to an embodiment of the present application.
As shown in fig. 3, the application flow control apparatus may include: the processor 1001, for example, a CPU, a memory 1005, and a communication bus 1002, and the application flow control device may be a display terminal such as a smart television, a smart phone, and the like. The communication bus 1002 is used for realizing connection communication between the processor 1001 and the memory 1005. The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a memory device separate from the processor 1001 described above.
Optionally, the application flow control device may further include a rectangular user interface, a network interface, a camera, an RF (Radio Frequency) circuit, a sensor, an audio circuit, a WiFi module, and the like. The rectangular user interface may comprise a Display screen (Display), an input sub-module such as a Keyboard (Keyboard), and the optional rectangular user interface may also comprise a standard wired interface, a wireless interface. The network interface may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface).
Those skilled in the art will appreciate that the application flow control device configuration shown in fig. 3 does not constitute a limitation of the application flow control device and may include more or fewer components than shown, or some components may be combined, or a different arrangement of components.
As shown in fig. 3, a memory 1005, which is a kind of computer storage medium, may include therein an operating system, a network communication module, and an application flow control method program. The operating system is a program that manages and controls the hardware and software resources of the device, supporting the application flow control method program and the execution of other software and/or programs. The network communication module is used for realizing communication among the components in the memory 1005 and communication with other hardware and software in the application flow control method system.
In the application traffic control apparatus shown in fig. 3, the processor 1001 is configured to execute an application traffic control method program stored in the memory 1005, and implement the steps of the application traffic control method described in any one of the above.
The specific implementation of the application flow control device of the present application is substantially the same as the embodiments of the application flow control method, and is not described herein again.
The embodiment of the present application provides an application flow control device, application flow control device is applied to application flow control equipment, application flow control device includes:
the determining module is used for acquiring first traffic information of foreground application and determining whether the foreground application is in a easy-to-jam state or not based on the first traffic information;
the acquisition module is used for acquiring second traffic information and idle traffic information of each background application if the first traffic information and the idle traffic information are the same;
and the selecting and exiting module is used for selecting the target application from the background applications to exit based on the second traffic information and the idle traffic information.
Optionally, the determining module is further configured to:
if the data transmission speed of the foreground application is greater than a preset data transmission speed threshold value, judging that the foreground application is in the easy-to-jam state; or the like, or, alternatively,
and if the foreground application data transmission speed is not greater than the preset data transmission speed threshold value, judging that the foreground application is not in the easy-to-jam state.
Optionally, the determining module is further configured to:
if the data transmission speed fluctuation value is larger than a preset idle data transmission speed threshold value, judging that the foreground application is in the easy-to-jam state; or the like, or, alternatively,
and if the data transmission speed fluctuation value is not greater than the preset idle data transmission speed threshold value, judging that the foreground application is not in the easy-to-jam state.
Optionally, the opt-out module is further configured to:
acquiring a network bandwidth speed, and selecting background applications to be exited from each background application based on the network bandwidth speed and the second traffic information;
respectively determining whether each background application to be quitted needs to be quitted or not based on the idle traffic information and the second traffic information;
and if so, taking the background application to be quitted which needs to be quitted as the target application, and quitting the target application.
Optionally, the opt-out module is further configured to:
if the application traffic to be quitted is larger than the network idle traffic, judging that the background application to be quitted corresponding to the application traffic to be quitted needs to be quitted; or the like, or, alternatively,
and if the application traffic to be quitted is not larger than the network idle traffic, judging that the background application to be quitted corresponding to the application traffic to be quitted does not need to be quitted.
Optionally, the opt-out module is further configured to:
calculating the application traffic ratio corresponding to each background application based on the network bandwidth speed and each background application traffic;
and selecting the background application to be quitted from each background application based on the traffic occupation ratio of each application.
Optionally, the opt-out module is further configured to:
acquiring a wireless network fluctuation value, and calculating a safety flow threshold value based on the wireless network idle flow and the wireless network fluctuation value;
if the application traffic to be quitted is larger than the safety traffic threshold value, judging that the background application to be quitted corresponding to the application traffic to be quitted needs to be quitted; or the like, or, alternatively,
and if the application traffic to be exited is not larger than the safety traffic threshold value, determining that the background application to be exited corresponding to the application traffic to be exited does not need to be exited.
The specific implementation of the application flow control device of the present application is substantially the same as that of the above-mentioned embodiments of the application flow control method, and is not described herein again.
The present application provides a readable storage medium, which stores one or more programs, where the one or more programs are also executable by one or more processors to implement the steps of the application traffic control method described in any one of the above.
The specific implementation of the readable storage medium of the present application is substantially the same as that of the embodiments of the application traffic control method, and is not described herein again.
The above description is only a preferred embodiment of the present application, and not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings, or which are directly or indirectly applied to other related technical fields, are included in the scope of the present application.
Claims (10)
1. An application flow control method, characterized in that the application flow control method comprises:
acquiring first traffic information of foreground application, and determining whether the foreground application is in a stuck-prone state or not based on the first traffic information;
if yes, second flow information and idle flow information of each background application are obtained;
and selecting a target application from the background applications to quit based on the second traffic information and the idle traffic information.
2. The application traffic control method of claim 1, wherein the first traffic information includes a foreground application data transmission speed, and the step of determining whether the foreground application is in a stuck-prone state based on the first traffic information includes:
if the data transmission speed of the foreground application is greater than a preset data transmission speed threshold value, judging that the foreground application is in the easy-to-jam state; or the like, or, alternatively,
and if the foreground application data transmission speed is not greater than the preset data transmission speed threshold value, judging that the foreground application is not in the easy-to-jam state.
3. The application flow control method according to claim 1, wherein the first traffic information includes a data transmission speed fluctuation value, and the step of determining whether the foreground application is in a stuck-prone state based on the first traffic information includes:
if the data transmission speed fluctuation value is larger than a preset idle data transmission speed threshold value, judging that the foreground application is in the easy-to-jam state; or the like, or, alternatively,
and if the data transmission speed fluctuation value is not greater than the preset idle data transmission speed threshold value, judging that the foreground application is not in the easy-to-jam state.
4. The application traffic control method according to claim 1, wherein the step of selecting a target application from among the background applications for exiting based on the second traffic information and the idle traffic information comprises:
acquiring a network bandwidth speed, and selecting background applications to be exited from each background application based on the network bandwidth speed and the second traffic information;
respectively determining whether each background application to be quitted needs to be quitted or not based on the idle traffic information and the second traffic information;
and if so, taking the background application to be quitted which needs to be quitted as the target application, and quitting the target application.
5. The application traffic control method of claim 4, wherein the idle traffic information comprises network idle traffic, the second traffic information comprises at least application traffic to exit,
the step of respectively determining whether each background application to be exited needs to be exited based on the idle traffic information and the second traffic information includes:
if the application traffic to be quitted is larger than the network idle traffic, judging that the background application to be quitted corresponding to the application traffic to be quitted needs to be quitted; or the like, or, alternatively,
and if the application traffic to be quitted is not larger than the network idle traffic, judging that the background application to be quitted corresponding to the application traffic to be quitted does not need to be quitted.
6. The application traffic control method of claim 4, wherein the second traffic information includes at least a background application traffic,
the step of selecting the background application to be exited from among the background applications based on the network bandwidth speed and the second traffic information includes:
calculating the application traffic ratio corresponding to each background application based on the network bandwidth speed and each background application traffic;
and selecting the background application to be quitted from each background application based on the traffic occupation ratio of each application.
7. The application traffic control method of claim 4, wherein the idle traffic information comprises wireless network idle traffic, the second traffic information comprises at least application traffic to exit,
the step of respectively determining whether each background application to be exited needs to be exited based on the idle traffic information and the second traffic information includes:
acquiring a wireless network fluctuation value, and calculating a safety flow threshold value based on the wireless network idle flow and the wireless network fluctuation value;
if the application traffic to be quitted is larger than the safety traffic threshold value, judging that the background application to be quitted corresponding to the application traffic to be quitted needs to be quitted; or the like, or, alternatively,
and if the application traffic to be exited is not larger than the safety traffic threshold value, determining that the background application to be exited corresponding to the application traffic to be exited does not need to be exited.
8. A usage flow control device, comprising:
the determining module is used for acquiring first traffic information of foreground application and determining whether the foreground application is in a easy-to-jam state or not based on the first traffic information;
the acquisition module is used for acquiring second traffic information and idle traffic information of each background application if the first traffic information and the idle traffic information are the same;
and the selecting and exiting module is used for selecting the target application from the background applications to exit based on the second traffic information and the idle traffic information.
9. An application flow control device, characterized in that the application flow control device comprises: a memory, a processor, and a program stored on the memory for implementing the application flow control method,
the memory is used for storing a program for realizing the application flow control method;
the processor is configured to execute a program implementing the application traffic control method to implement the steps of the application traffic control method according to any one of claims 1 to 7.
10. A readable storage medium having a program for implementing an application traffic control method stored thereon, the program being executed by a processor to implement the steps of the application traffic control method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011492035.3A CN112671672B (en) | 2020-12-16 | 2020-12-16 | Application flow control method, device, equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011492035.3A CN112671672B (en) | 2020-12-16 | 2020-12-16 | Application flow control method, device, equipment and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112671672A true CN112671672A (en) | 2021-04-16 |
| CN112671672B CN112671672B (en) | 2023-12-08 |
Family
ID=75404359
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011492035.3A Active CN112671672B (en) | 2020-12-16 | 2020-12-16 | Application flow control method, device, equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112671672B (en) |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107172489A (en) * | 2017-05-12 | 2017-09-15 | 深圳Tcl数字技术有限公司 | TV applications software refreshing method, TV and computer-readable recording medium |
| WO2017166617A1 (en) * | 2016-03-31 | 2017-10-05 | 乐视控股（北京）有限公司 | Terminal control method and apparatus, and electronic device |
| CN107800651A (en) * | 2017-10-31 | 2018-03-13 | 广东欧珀移动通信有限公司 | Closing application program method, apparatus, storage medium and electronic equipment |
| CN108829444A (en) * | 2018-05-29 | 2018-11-16 | 努比亚技术有限公司 | A kind of method that background application is automatically closed, terminal and computer storage medium |
| WO2018232074A1 (en) * | 2017-06-16 | 2018-12-20 | Alibaba Group Holding Limited | Method, system, and device for network control |
| WO2019080732A1 (en) * | 2017-10-25 | 2019-05-02 | Oppo广东移动通信有限公司 | Network management method and related products |
| CN110032267A (en) * | 2018-01-10 | 2019-07-19 | 广东欧珀移动通信有限公司 | Information processing method, device, mobile terminal and computer readable storage medium |
| CN110825458A (en) * | 2019-11-06 | 2020-02-21 | 深圳传音控股股份有限公司 | Background application cleaning method and device and computer readable storage medium |
| CN110868693A (en) * | 2019-11-20 | 2020-03-06 | 深圳传音控股股份有限公司 | Application program flow control method, terminal device and storage medium |
| WO2020180167A1 (en) * | 2019-03-07 | 2020-09-10 | 삼성전자 주식회사 | Electronic device and method for controlling application thereof |
| WO2020233511A1 (en) * | 2019-05-23 | 2020-11-26 | 腾讯科技（深圳）有限公司 | Application starting method and apparatus, computer device and storage medium |
| CN112035249A (en) * | 2020-08-24 | 2020-12-04 | Tcl海外电子（惠州）有限公司 | Application program network proportion adjusting method and device and storage medium |
-
2020
- 2020-12-16 CN CN202011492035.3A patent/CN112671672B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017166617A1 (en) * | 2016-03-31 | 2017-10-05 | 乐视控股（北京）有限公司 | Terminal control method and apparatus, and electronic device |
| CN107172489A (en) * | 2017-05-12 | 2017-09-15 | 深圳Tcl数字技术有限公司 | TV applications software refreshing method, TV and computer-readable recording medium |
| WO2018232074A1 (en) * | 2017-06-16 | 2018-12-20 | Alibaba Group Holding Limited | Method, system, and device for network control |
| WO2019080732A1 (en) * | 2017-10-25 | 2019-05-02 | Oppo广东移动通信有限公司 | Network management method and related products |
| CN107800651A (en) * | 2017-10-31 | 2018-03-13 | 广东欧珀移动通信有限公司 | Closing application program method, apparatus, storage medium and electronic equipment |
| CN110032267A (en) * | 2018-01-10 | 2019-07-19 | 广东欧珀移动通信有限公司 | Information processing method, device, mobile terminal and computer readable storage medium |
| CN108829444A (en) * | 2018-05-29 | 2018-11-16 | 努比亚技术有限公司 | A kind of method that background application is automatically closed, terminal and computer storage medium |
| WO2020180167A1 (en) * | 2019-03-07 | 2020-09-10 | 삼성전자 주식회사 | Electronic device and method for controlling application thereof |
| WO2020233511A1 (en) * | 2019-05-23 | 2020-11-26 | 腾讯科技（深圳）有限公司 | Application starting method and apparatus, computer device and storage medium |
| CN110825458A (en) * | 2019-11-06 | 2020-02-21 | 深圳传音控股股份有限公司 | Background application cleaning method and device and computer readable storage medium |
| CN110868693A (en) * | 2019-11-20 | 2020-03-06 | 深圳传音控股股份有限公司 | Application program flow control method, terminal device and storage medium |
| CN112035249A (en) * | 2020-08-24 | 2020-12-04 | Tcl海外电子（惠州）有限公司 | Application program network proportion adjusting method and device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112671672B (en) | 2023-12-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109240576B (en) | Image processing method and device in game, electronic device and storage medium | |
| CN112272239B (en) | Edge calculation method and device, intelligent terminal and computer readable storage medium | |
| CN111240837A (en) | Resource allocation method, device, terminal and storage medium | |
| CN108881781B (en) | Method and device for determining resolution in video call process | |
| CN107943570B (en) | Application management method and device, storage medium and electronic equipment | |
| CN104767809A (en) | Downloading control method and system | |
| CN114968509A (en) | Task execution method and device | |
| CN109783337B (en) | Model service method, system, apparatus and computer readable storage medium | |
| CN112511576A (en) | Internet of things data processing system and data processing method | |
| CN114398173A (en) | Resource allocation method and device and electronic equipment | |
| CN112235814B (en) | Cloud SIM card wireless network optimization method, terminal device and server device | |
| CN113342505A (en) | Thread identification method, thread identification device, storage medium and electronic equipment | |
| CN112671672A (en) | Application flow control method, device, equipment and readable storage medium | |
| CN112600897A (en) | Multi-user access control method and device for intelligent equipment | |
| CN111787602A (en) | Terminal power saving method, terminal and readable storage medium | |
| CN109274991B (en) | Memory management method and system of smart television | |
| CN112073820B (en) | Method and device for pre-starting television application program and computer readable storage medium | |
| CN113271228B (en) | Bandwidth resource scheduling method, device, equipment and computer readable storage medium | |
| CN115987790A (en) | Upgrading method, device and equipment based on position information and storage medium | |
| CN112675535B (en) | Display interface adjusting method, device, network equipment and storage medium | |
| CN112527407B (en) | Application starting method, terminal and computer readable storage medium | |
| CN111813213A (en) | Power saving method, terminal and readable storage medium | |
| CN108307060B (en) | Electronic equipment, fall protection method and related product | |
| CN113595814A (en) | Message delay detection method and device, electronic equipment and storage medium | |
| CN110597637A (en) | System resource scheduling method, device and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |