CN112533246A - Monitoring system and method for frequent network requests of intelligent equipment - Google Patents
Monitoring system and method for frequent network requests of intelligent equipment Download PDFInfo
- Publication number
- CN112533246A CN112533246A CN202011422756.7A CN202011422756A CN112533246A CN 112533246 A CN112533246 A CN 112533246A CN 202011422756 A CN202011422756 A CN 202011422756A CN 112533246 A CN112533246 A CN 112533246A
- Authority
- CN
- China
- Prior art keywords
- application
- network request
- network
- accumulated
- requests
- 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 56
- 238000012544 monitoring process Methods 0.000 title claims abstract description 36
- 230000002159 abnormal effect Effects 0.000 claims abstract description 41
- 238000004458 analytical method Methods 0.000 claims description 32
- 238000009826 distribution Methods 0.000 claims description 12
- 230000001186 cumulative effect Effects 0.000 claims description 4
- 230000008569 process Effects 0.000 abstract description 17
- 230000008439 repair process Effects 0.000 abstract description 11
- 230000000694 effects Effects 0.000 abstract description 5
- 238000012545 processing Methods 0.000 description 8
- 238000005457 optimization Methods 0.000 description 7
- 238000004140 cleaning Methods 0.000 description 6
- 238000013500 data storage Methods 0.000 description 6
- 230000003203 everyday effect Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000007639 printing Methods 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 3
- 238000007405 data analysis Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000000737 periodic effect Effects 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000005611 electricity Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
-
- 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
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Abstract
The invention discloses a monitoring system and a method for frequent network requests of intelligent equipment, wherein the monitoring system comprises the following steps: when RRC is released every time, counting the application triggering the network request in the RCC, and generating an RRC counting result; adding one to the accumulated network request times of the application triggering the network request in the RCC; when the accumulated network request times of any application are larger than the preset maximum request times and the abnormal network request times of the application are larger than the preset maximum abnormal times, the application is marked as a problem application, and the problem application and the network request data thereof are pushed to the specified external equipment. The invention has the technical effects that: by analyzing the network request times of the application, the problem application with abnormal power consumption on the network request is found, and a problem application developer is informed to process and repair the problem application, so that the searching speed of the problem application with abnormal power consumption on the network request is increased, and the power consumption is further saved.
Description
Technical Field
The invention relates to network communication, in particular to a monitoring system and a monitoring method for frequent network requests of intelligent equipment.
Background
With the increasing popularity and abundance of functions of telephone watches, the watches are only built-in applications and a large number of third-party applications are introduced. Due to different strategies of the introduced third-party application, many applications can keep alive in the background or have own heartbeat. Therefore, under the condition that the watch is not used, the electricity is consumed up quickly due to a plurality of background network requests, the endurance of the telephone watch is greatly influenced, and the word of the product is influenced.
At present, no method is available for monitoring the type of application, the conventional means is that customers complain about fast power consumption, logs of problem machines are obtained through a specific method for power consumption analysis, and as few log printing information is available in network requests, the log printing information is difficult to analyze and position to which application frequently triggers the network requests, packet grabbing is needed to discover the type of application, the efficiency is low, the problem analysis and positioning are difficult, the problem solution period is long, and the application is passive. At present, the method is to forcibly close down the application by a background, and since a background keep-alive mechanism is not designed by five aspects, the application is completely stopped, and meanwhile, many applications are automatically pulled up or a daemon process automatically pulls up the application through a special path even if the system forcibly closes down the application, so that the application is frequently forcibly closed down and restarted. In addition, the traffic is consumed by monitoring the application, but the method that the application triggers the RRC each time and does not send much data to cause traffic monitoring cannot identify the application, that is, frequent network requests for the application cause that the power consumption cannot be pre-warned and monitored.
Disclosure of Invention
In order to solve the technical problem, the invention provides a monitoring system and a monitoring method for frequent network requests of intelligent equipment, wherein the specific solution is as follows:
one aspect provides a monitoring system for frequent network requests of intelligent equipment devices, including:
the RCC counting module is used for counting the application triggering the network request in the RCC at the current time when the RRC is released every time, and generating an RRC counting result;
the data statistics module is used for adding one to the accumulated network request times of the application triggering the network request in the RCC;
and the problem application output module is used for marking the application as a problem application and pushing the problem application and the network request data thereof to a specified external device when the accumulated network request times of any application are greater than the preset maximum request times and the abnormal network request times of the application are greater than the preset maximum abnormal times.
In the technical scheme, through the analysis of the network request times of the application, the problem application with abnormal power consumption on the network request is found, and then a developer of the problem application is informed to process and repair the problem application, so that the technical problems of low efficiency and difficult analysis and positioning problem in the prior art are solved, the searching speed of the problem application with abnormal power consumption on the network request is increased, and the power consumption is reduced.
Preferably, the problem application output module is deployed in the cloud;
the system further comprises an interval generation module, which is used for periodically transmitting all the accumulated network request times of the application to the cloud end and resetting all the accumulated network request times to be zero.
According to the technical scheme, data are periodically uploaded, data cleaning is carried out simultaneously, and the number of times of network requests is accumulated and returned to zero, so that the data volume uploaded every time is greatly reduced, timely useless data processing is realized, and resources consumed by data storage are reduced.
Further preferably, the period of the interval data uploading module is one day.
Preferably, the problem application report generating module is configured to generate an analysis report of the problem application according to the network request data of the problem application, and push the analysis report to a specified external device.
Preferably, the system further comprises a network request distribution reporting module, configured to generate a network request distribution report according to all the network request data of the application, and push the analysis report to a specified external device.
On the other hand, the invention provides a monitoring method for frequent network requests of intelligent equipment, which comprises the following steps:
when RRC is released every time, counting the application triggering the network request in the RCC, and generating an RRC counting result;
adding one to the accumulated network request times of the application triggering the network request in the RCC according to the RRC statistical result;
when the accumulated network request times of any application are larger than the preset maximum request times and the abnormal network request times of the application are larger than the preset maximum abnormal times, the application is marked as a problem application, and the problem application and the network request data thereof are pushed to the specified external equipment.
In the technical scheme, through the analysis of the network request times of the application, the problem application with abnormal power consumption on the network request is found, and then a developer of the problem application is informed to process and repair the problem application, so that the technical problems of low efficiency and difficult analysis and positioning problem in the prior art are solved, and the searching speed of the problem application with abnormal power consumption on the network request is increased.
Preferably, the adding one to the accumulated network request times of the application triggering the network request in the RCC of this time includes:
and when a specified period point is reached, transmitting all the accumulated network request times of the application to a cloud end, and resetting all the accumulated network request times to be zero.
According to the technical scheme, data are periodically uploaded, data cleaning is carried out simultaneously, and the number of times of network requests is accumulated and returned to zero, so that the data volume uploaded every time is greatly reduced, timely useless data processing is realized, and resources consumed by data storage are reduced.
Further preferably, the period of the interval data uploading module is one day.
Preferably, the method further comprises the following steps: and generating an analysis report of the problem application according to the network request data of the problem application, and pushing the analysis report to a specified external device.
Preferably, the method further comprises the following steps: and generating a network request distribution report according to all the applied network request data, and pushing the analysis report to a specified external device.
The invention at least comprises the following technical effects:
(1) by analyzing the network request times of the application, finding the problem application with abnormal power consumption on the network request and informing a developer of the problem application to process and repair the problem application, the technical problems of low efficiency and difficult analysis and positioning problems in the prior art are solved, and the finding speed of the problem application with abnormal power consumption on the network request is increased.
(2) By periodically uploading data and simultaneously clearing data and zeroing accumulated network request times, the data volume uploaded every time is greatly reduced, timely processing of useless data is realized, and resources consumed by data storage are reduced.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
FIG. 1 is a schematic structural view of example 1 of the present invention;
FIG. 2 is a schematic structural diagram of example 2 of the present invention;
FIG. 3 is a schematic structural diagram according to embodiment 3 of the present invention;
FIG. 4 is a schematic structural diagram according to embodiment 4 of the present invention;
FIG. 5 is a schematic structural view of example 5 of the present invention;
FIG. 6 is a schematic structural view of example 6 of the present invention;
fig. 7 is a schematic structural diagram of embodiment 7 of the present invention.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. However, it will be apparent to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
For the sake of simplicity, the drawings only schematically show the parts relevant to the present invention, and they do not represent the actual structure as a product. In addition, in order to make the drawings concise and understandable, components having the same structure or function in some of the drawings are only schematically depicted, or only one of them is labeled. In this document, "one" means not only "only one" but also a case of "more than one".
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
In addition, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not intended to indicate or imply relative importance.
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following description will be made with reference to the accompanying drawings. It is obvious that the drawings in the following description are only some examples of the invention, and that for a person skilled in the art, other drawings and embodiments can be derived from them without inventive effort.
Example 1:
as shown in fig. 1, this embodiment provides a monitoring system for frequent network requests of smart device devices, including:
the RCC counting module (1) is used for counting the application triggering the network request in the RCC at the current time when RRC is released every time, and generating an RRC counting result;
the data statistics module (2) is used for adding one to the accumulated network request times of the application triggering the network request in the RCC;
and the problem application output module (3) is used for marking the application as a problem application and pushing the problem application and the network request data thereof to a specified external device (6) when the accumulated network request times of any application are greater than the preset maximum request times and the abnormal network request times of the application are greater than the preset maximum abnormal times.
In the traditional technology, because network requests have few log printing information and are difficult to analyze and position to which application frequently triggers the network requests, packet capturing is needed to find that the type of application is not only inefficient, but also difficult to analyze and position problems, long in problem solving period and passive, even though the application is forcibly closed through the background, the background keep-alive mechanism can not completely stop the application due to the five-door method, meanwhile, many applications have the phenomenon that automatic pull-up or daemon process automatically pulls up through a special way even if the system forcibly shuts down the applications, so that frequent forced shutdown and restart are caused, if the traffic is consumed by the monitoring application, but a method that one type of application triggers the RRC every time and does not send much data to cause traffic monitoring cannot identify the type of application, namely, the power consumption caused by frequent network requests of the type of application cannot be early warned and monitored.
Therefore, in this embodiment, instead of monitoring the traffic, the accumulated number of network requests in the RRC is monitored, specifically, each time the RRC is released, the applications making network requests in the RRC are monitored, for example, in the current RRC procedure, A, B, C three applications are involved, the accumulated number of network requests of A, B, C three applications is 998, 999 and 1000 respectively, and it is explained that A, B, C makes network requests of 998, 999 and 1000 times respectively in the previous RRC procedure, and then since A, B, C three applications all make network requests, 1 is added to the accumulated number of network requests of A, B, C three applications respectively, which indicates that in the current RRC connection, A, B, C all make network requests, the accumulated number of network requests is currently 999, 1000 and 1001 respectively, and assuming that the maximum number of requests is 1000, the maximum abnormal number is 100, now, since the cumulative network request number of the C is greater than 1000, and the number of the abnormal network request number is greater than 100, that is, the C application is determined as the problem application, and the C application should be optimized, the C application is transmitted to the specified device, that is, the device of the developer, and the developer is informed that "the application frequently makes network requests and should be optimized", and then the developer analyzes the application, and performs optimization and repair.
According to the method and the device, the problem application with abnormal power consumption on the network request is found by analyzing the network request times of the application, and then the developer of the problem application is informed to process and repair the problem application, so that the technical problems of low efficiency and difficulty in analyzing and positioning problems in the prior art are solved, and the searching speed of the problem application with abnormal power consumption on the network request is increased.
Example 2:
as shown in fig. 2, the present embodiment provides a monitoring system for frequent network requests of an intelligent device based on embodiment 1, where the problem application output module is deployed in a cloud;
the system further comprises an interval generation module (4) which is used for periodically transmitting all the accumulated network request times of the application to the cloud end and resetting all the accumulated network request times to be zero.
Since the number of times of requesting the network in the RRC from the start to the end of the application is relatively complex on one hand, and is not suitable for data analysis and processing on the other hand, in this embodiment, a periodic method is adopted, that is, data is periodically uploaded, data cleaning and zeroing of the number of times of accumulating network requests are performed at the same time, and further, the data uploaded each time is only related to the data in the period, so that the workload is greatly reduced.
Meanwhile, it is further preferable that the period of the interval data uploading module is one day.
In this embodiment, the amount of the network request of each application is obtained at a fixed point every day, generally at 7 points every day, and the amount of the network request of all applications from the previous 7 points to the current 7 points is obtained, from the updating and running periods of the applications themselves, the period of one day can just reflect the running process of one application, the running condition of the application about the network request can be effectively collected, and meanwhile, when the intelligent device is started for the first time, data uploading is also performed.
According to the embodiment, data are periodically uploaded, data cleaning is carried out simultaneously, and the number of times of network requests is accumulated to zero, so that the data volume uploaded each time is greatly reduced, timely useless data processing is realized, and resources consumed by data storage are reduced.
Example 3:
as shown in fig. 3, this embodiment is based on embodiment 1, and the problem application report generating module (5) is configured to generate an analysis report of the problem application according to network request data of the problem application, and push the analysis report to a specified external device (6).
In the actual application process, the developer is simply told that "the application has a problem" is equal to what does not told to the developer, so in the embodiment, the developer is not only told that "the application has a problem" but also told that "the application has a problem", so in the actual application process, the network request data of the problem application is analyzed to generate a corresponding analysis report and send the corresponding analysis report to the developer, so that the developer is told what problem the application has.
Preferably, the system further comprises a network request distribution reporting module, configured to generate a network request distribution report according to network request data of all the applications, and push the analysis report to a specified external device (6).
In the preferred embodiment, the developer is not only told what question you are about the application, but also what the average is for the normal case or what we are now, thus providing guidance to the developer's optimization activities.
Example 4:
as shown in fig. 4, the present embodiment provides a method for monitoring frequent network requests of an intelligent device, including:
s1: when RRC is released every time, counting the application triggering the network request in the RCC, and generating an RRC counting result;
s2: adding one to the accumulated network request times of the application triggering the network request in the RCC;
s4: when the accumulated network request times of any application are larger than the preset maximum request times and the abnormal network request times of the application are larger than the preset maximum abnormal times, marking the application as a problem application;
s6: and pushing the problem application and the network request data thereof to the specified external equipment.
In the traditional technology, because network requests have few log printing information and are difficult to analyze and position to which application frequently triggers the network requests, packet capturing is needed to find that the type of application is not only inefficient, but also difficult to analyze and position problems, long in problem solving period and passive, even though the application is forcibly closed through the background, the background keep-alive mechanism can not completely stop the application due to the five-door method, meanwhile, many applications have the phenomenon that automatic pull-up or daemon process automatically pulls up through a special way even if the system forcibly shuts down the applications, so that frequent forced shutdown and restart are caused, if the traffic is consumed by the monitoring application, but a method that one type of application triggers the RRC every time and does not send much data to cause traffic monitoring cannot identify the type of application, namely, the power consumption caused by frequent network requests of the type of application cannot be early warned and monitored.
Therefore, in this embodiment, instead of monitoring the traffic, the accumulated number of network requests in the RRC is monitored, specifically, each time the RRC is released, the applications making network requests in the RRC are monitored, for example, in the current RRC procedure, A, B, C three applications are involved, the accumulated number of network requests of A, B, C three applications is 998, 999 and 1000 respectively, and it is explained that A, B, C makes network requests of 998, 999 and 1000 times respectively in the previous RRC procedure, and then since A, B, C three applications all make network requests, 1 is added to the accumulated number of network requests of A, B, C three applications respectively, which indicates that in the current RRC connection, A, B, C all make network requests, the accumulated number of network requests is currently 999, 1000 and 1001 respectively, and assuming that the maximum number of requests is 1000, the maximum abnormal number is 100, now, since the cumulative network request number of the C is greater than 1000, and the abnormal network request number is greater than 100, that is, the C application is determined as a problem application, and the C application should be optimized, the C application is transmitted to a designated device, that is, a device of a developer, and the developer is informed that "the application frequently makes network requests and should be optimized", and then the developer analyzes the application, and performs optimization and repair.
According to the method and the device, the problem application with abnormal power consumption on the network request is found by analyzing the network request times of the application, and then the developer of the problem application is informed to process and repair the problem application, so that the technical problems of low efficiency and difficulty in analyzing and positioning problems in the prior art are solved, and the searching speed of the problem application with abnormal power consumption on the network request is increased.
Example 5:
as shown in fig. 5, the present embodiment provides a method for monitoring frequent network requests of an intelligent device, including:
s1: when RRC is released every time, counting the application triggering the network request in the RCC, and generating an RRC counting result;
s2: adding one to the accumulated network request times of the application triggering the network request in the RCC;
s3: and when a specified period point is reached, transmitting all the accumulated network request times of the application to a cloud end, and resetting all the accumulated network request times to be zero.
S4: when the accumulated network request times of any application are larger than the preset maximum request times and the abnormal network request times of the application are larger than the preset maximum abnormal times, marking the application as a problem application;
s6: and pushing the problem application and the network request data thereof to the specified external equipment.
Since the number of times of requesting the network in the RRC from the start to the end of the application is relatively complex on one hand, and is not suitable for data analysis and processing on the other hand, in this embodiment, a periodic method is adopted, that is, data is periodically uploaded, data cleaning and zeroing of the number of times of accumulating network requests are performed at the same time, and further, the data uploaded each time is only related to the data in the period, so that the workload is greatly reduced.
Meanwhile, it is further preferable that the period of the interval data uploading module is one day.
In this embodiment, the amount of the network request of each application is obtained at a fixed point every day, generally at 7 points every day, and the amount of the network request of all applications from the previous 7 points to the current 7 points is obtained, from the updating and running periods of the applications themselves, the period of one day can just reflect the running process of one application, the running condition of the application about the network request can be effectively collected, and meanwhile, when the intelligent device is started for the first time, data uploading is also performed.
According to the embodiment, data are periodically uploaded, data cleaning is carried out simultaneously, and the number of times of network requests is accumulated to zero, so that the data volume uploaded each time is greatly reduced, timely useless data processing is realized, and resources consumed by data storage are reduced.
Example 6:
as shown in fig. 6, the present embodiment provides a method for monitoring frequent network requests of an intelligent device, including:
s1: when RRC is released every time, counting the application triggering the network request in the RCC, and generating an RRC counting result;
s2: adding one to the accumulated network request times of the application triggering the network request in the RCC;
s3: when a specified period point is reached, transmitting all the accumulated network request times of the application to a cloud end, and resetting all the accumulated network request times to be zero; the period of the interval data uploading module is one day.
S4: when the accumulated network request times of any application are larger than the preset maximum request times and the abnormal network request times of the application are larger than the preset maximum abnormal times, marking the application as a problem application;
s5: and generating an analysis report of the problem application according to the network request data of the problem application, and pushing the analysis report to a specified external device.
S6: and pushing the problem application and the network request data thereof to the specified external equipment.
In the actual application process, the developer is simply told that "the application has a problem" is equal to what does not told to the developer, so in the embodiment, the developer is not only told that "the application has a problem" but also told that "the application has a problem", so in the actual application process, the network request data of the problem application is analyzed to generate a corresponding analysis report and send the corresponding analysis report to the developer, so that the developer is told what problem the application has.
Preferably, it further comprises S7: and generating a network request distribution report according to all the applied network request data, and pushing the analysis report to a specified external device.
In the preferred embodiment, the developer is not only told what question you are about the application, but also what the average is for the normal case or what we are now, thus providing guidance to the developer's optimization activities.
Example 7:
as shown in fig. 7, the present embodiment provides a method for monitoring frequent network requests of an intelligent device, including:
s1: and acquiring how many applications in the RRC trigger network requests each time when the RRC is released, counting the accumulated times of the application network requests and writing the accumulated times into a database.
And S2, starting up for 7 am the next day or the first time on the next day, and detecting whether the application network request data collected yesterday is uploaded to the server or not and emptying the server if the application network request data is not uploaded to the server. And counting the application network request times again.
And S3, the server background judges the number of network requests of each device on the same day of application according to a strategy, if the number is greater than a preset value, if the number is 1000, the mark is that the network requests are abnormal, and if the number of the network requests of the application on the same day is greater than the preset value, if the number is ten percent of the activation amount of the application on the same day, the application has the behavior of network request abnormality and generates an early warning report to be pushed to developers, and meanwhile, the applications are sequenced according to the number of the network requests and then a network request number distribution report of each application is generated to be pushed to the developers.
And S4, after receiving the frequent network request early warning push, the developer starts to intervene to analyze, repair, optimize and the like the problems. After receiving the network request frequency distribution report, the developer analyzes whether the report has the application with optimized network request frequency, and then makes corresponding strategy adjustment.
Therefore, in this embodiment, instead of monitoring the traffic, the accumulated number of network requests in the RRC is monitored, specifically, each time the RRC is released, the applications making network requests in the RRC are monitored, for example, in the current RRC procedure, A, B, C three applications are involved, the accumulated number of network requests of A, B, C three applications is 998, 999 and 1000 respectively, and it is explained that A, B, C makes network requests of 998, 999 and 1000 times respectively in the previous RRC procedure, and then since A, B, C three applications all make network requests, 1 is added to the accumulated number of network requests of A, B, C three applications respectively, which indicates that in the current RRC connection, A, B, C all make network requests, the accumulated number of network requests is currently 999, 1000 and 1001 respectively, and assuming that the maximum number of requests is 1000, the maximum abnormal number is 100, now, since the cumulative network request number of the C is greater than 1000, and the number of the abnormal network request number is greater than 100, that is, the C application is determined as a problem application, the C application should be optimized, and then, by 7 o' clock of one day, the C application and related data thereof are transmitted to a specified device, that is, a device of a developer, and the developer is informed that "the application frequently makes network requests and should be optimized", and then the developer analyzes the application, and performs optimization and repair.
Finally, through two reports, the developer is not only told that "your application has problems", but also what the average level of your application is, and thus what the developer's optimization activities are.
In this embodiment, the network request times of each application are monitored by counting how many times the application triggers the network request each day by a method of acquiring how many applications in the RRC trigger the network request each time the RRC is released. The difficulty of analysis is reduced, the labor cost is reduced, the problem repairing period is shortened, and the method is particularly remarkable for products with larger user base numbers. And inserting the counted network request times and the data information into a database. And reporting the data to the background of the server under the condition that the network is available again at 7 am or when the computer is started for the first time every day, so that the data loss is avoided. The background server judges whether the number of the times of the application network requests of each device, which is marked as abnormal network requests, is larger than a preset value (such as 1000) according to the collected times of the application network requests of each device, and judges whether the number of the times of the application network requests, which are marked as abnormal network requests, is larger than the preset value (such as ten percent of the active quantity of the application day), generates an application frequent network request report and pushes the application frequent network request report to developers to warn the application frequent network requests. The efficiency of power consumption problem analysis is improved, the problem solving period is shortened, and the phenomenon of large-scale power consumption is avoided, so that the public praise and the user experience of the product are influenced. And the background service generates an application network request frequency distribution report according to the network request frequency sequence to monitor the network request process. The optimization of the application network request times is facilitated, so that the power is saved, the cruising ability of the product is improved, the quality of the product is improved, and the user experience is improved.
The invention realizes that:
(1) by analyzing the network request times of the application, finding the problem application with abnormal power consumption on the network request and informing a developer of the problem application to process and repair the problem application, the technical problems of low efficiency and difficult analysis and positioning problems in the prior art are solved, and the finding speed of the problem application with abnormal power consumption on the network request is increased.
(2) By periodically uploading data and simultaneously clearing data and zeroing accumulated network request times, the data volume uploaded every time is greatly reduced, timely processing of useless data is realized, and resources consumed by data storage are reduced.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (10)
1. A monitoring system for frequent network requests of intelligent equipment devices is characterized by comprising:
the RCC counting module is used for counting the application triggering the network request in the RCC at the current time when the RRC is released every time, and generating an RRC counting result;
the data statistics module is used for adding one to the accumulated network request times of the application triggering the network request in the RCC according to the RRC statistics result;
and the problem application output module is used for marking the application as a problem application and pushing the problem application and the network request data thereof to a specified external device when the accumulated network request times of any application are greater than the preset maximum request times and the abnormal network request times of the application are greater than the preset maximum abnormal times.
2. The monitoring system for frequent network requests of intelligent equipment devices according to claim 1, wherein the problem application output module is deployed in a cloud;
the system further comprises an interval generation module, which is used for periodically transmitting all the accumulated network request times of the application to the cloud end and resetting all the accumulated network request times to be zero.
3. The system for monitoring frequent network requests of intelligent equipment devices according to claim 2, wherein the period of the interval data uploading module is one day.
4. The monitoring system for frequent network requests of intelligent devices according to any one of claims 1 to 3, wherein the problem application report generating module is configured to generate an analysis report of the problem application according to the network request data of the problem application, and push the analysis report to a designated external device.
5. The monitoring system for frequent network requests of intelligent equipment devices according to any one of claims 1 to 3, further comprising a network request distribution reporting module, configured to generate a network request distribution report according to network request data of all the applications, and push the analysis report to a specified external device.
6. A monitoring method for frequent network requests of intelligent equipment is characterized by comprising the following steps:
when RRC is released every time, counting the application triggering the network request in the RCC, and generating an RRC counting result;
adding one to the accumulated network request times of the application triggering the network request in the RCC according to the RRC statistical result;
when the accumulated network request times of any application are larger than the preset maximum request times and the abnormal network request times of the application are larger than the preset maximum abnormal times, marking the application as a problem application;
and pushing the problem application and the network request data thereof to the specified external equipment.
7. The method for monitoring frequent network requests of intelligent equipment devices according to claim 6, wherein adding one to the cumulative number of network requests of the application triggering the network request in the RCC of this time comprises:
and when a specified period point is reached, transmitting all the accumulated network request times of the application to a cloud end, and resetting all the accumulated network request times to be zero.
8. The method for monitoring frequent network requests of intelligent equipment devices according to claim 7, wherein the period of the interval data uploading module is one day.
9. The method for monitoring frequent network requests of intelligent equipment devices according to any one of claims 6 to 8, further comprising: and generating an analysis report of the problem application according to the network request data of the problem application, and pushing the analysis report to a specified external device.
10. The method for monitoring frequent network requests of intelligent equipment devices according to any one of claims 6 to 8, further comprising: and generating a network request distribution report according to all the applied network request data, and pushing the analysis report to a specified external device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011422756.7A CN112533246B (en) | 2020-12-08 | 2020-12-08 | Monitoring system and method for frequent network requests of intelligent equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011422756.7A CN112533246B (en) | 2020-12-08 | 2020-12-08 | Monitoring system and method for frequent network requests of intelligent equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112533246A true CN112533246A (en) | 2021-03-19 |
| CN112533246B CN112533246B (en) | 2024-03-15 |
Family
ID=74998269
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011422756.7A Active CN112533246B (en) | 2020-12-08 | 2020-12-08 | Monitoring system and method for frequent network requests of intelligent equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112533246B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116033333A (en) * | 2022-08-31 | 2023-04-28 | 荣耀终端有限公司 | Method for determining position information, electronic device and readable storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104038929A (en) * | 2014-05-09 | 2014-09-10 | 宇龙计算机通信科技(深圳)有限公司 | Network access anomaly identification method and network access anomaly identification device |
| CN109766242A (en) * | 2018-12-29 | 2019-05-17 | 云智慧（北京）科技有限公司 | Monitoring method, device and system based on mobile user side and storage medium |
| CN111193609A (en) * | 2019-11-20 | 2020-05-22 | 腾讯科技（深圳）有限公司 | Application abnormity feedback method and device and application abnormity monitoring system |
| CN111722993A (en) * | 2020-06-16 | 2020-09-29 | 广东小天才科技有限公司 | Method and system for monitoring abnormal power consumption of communication terminal, terminal device and storage medium |
-
2020
- 2020-12-08 CN CN202011422756.7A patent/CN112533246B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104038929A (en) * | 2014-05-09 | 2014-09-10 | 宇龙计算机通信科技(深圳)有限公司 | Network access anomaly identification method and network access anomaly identification device |
| CN109766242A (en) * | 2018-12-29 | 2019-05-17 | 云智慧（北京）科技有限公司 | Monitoring method, device and system based on mobile user side and storage medium |
| CN111193609A (en) * | 2019-11-20 | 2020-05-22 | 腾讯科技（深圳）有限公司 | Application abnormity feedback method and device and application abnormity monitoring system |
| CN111722993A (en) * | 2020-06-16 | 2020-09-29 | 广东小天才科技有限公司 | Method and system for monitoring abnormal power consumption of communication terminal, terminal device and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116033333A (en) * | 2022-08-31 | 2023-04-28 | 荣耀终端有限公司 | Method for determining position information, electronic device and readable storage medium |
| CN116033333B (en) * | 2022-08-31 | 2023-10-17 | 荣耀终端有限公司 | Method for determining position information, electronic device and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112533246B (en) | 2024-03-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108156006B (en) | Buried point data reporting method and device and electronic equipment | |
| US7509343B1 (en) | System and method of collecting and reporting system performance metrics | |
| CN112311617A (en) | Configured data monitoring and alarming method and system | |
| CN106940677A (en) | One kind application daily record data alarm method and device | |
| CN101098260A (en) | Distributed equipment monitor management method, equipment and system | |
| CN113783931B (en) | Data aggregation and analysis method for Internet of things | |
| CN111881011A (en) | Log management method, platform, server and storage medium | |
| CN111538563A (en) | Event analysis method and device for Kubernetes | |
| CN112751726A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN110231998B (en) | Detection method and device for distributed timing task and storage medium | |
| CN114356499A (en) | Kubernetes cluster alarm root cause analysis method and device | |
| CN110795264A (en) | Monitoring management method and system and intelligent management terminal | |
| CN112533246A (en) | Monitoring system and method for frequent network requests of intelligent equipment | |
| CN111061588A (en) | Method and device for locating database abnormal source | |
| US6665822B1 (en) | Field availability monitoring | |
| CN111858274A (en) | Stability monitoring method for big data scoring system | |
| CN115525392A (en) | Container monitoring method and device, electronic equipment and storage medium | |
| CN116089247A (en) | Micro-service index early warning method and device based on index threshold and big data analysis | |
| CN110011845A (en) | Log collection method and system | |
| CN113742400A (en) | Network data acquisition system and method based on self-adaptive constraint conditions | |
| CN113079063A (en) | Offline judgment method, system and device for charging device and computer storage medium | |
| CN113377611A (en) | Business processing flow monitoring method, system, equipment and storage medium | |
| CN113034201A (en) | Real-time early warning method, system and computer based on advertisement putting process | |
| CN112328463A (en) | Log monitoring method and device | |
| CN108829563B (en) | Alarm method and alarm device |
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 |