CN106506817A - Flow monitoring method, device and terminal equipment - Google Patents

Abstract

The disclosure is directed to a kind of flow monitoring method, device and terminal unit.The method includes：Obtain customer flow information；According to the flow restriction grade that the customer flow information estimates user, so that third party application is according to flow restriction level adjustment resource loading strategy.The scheme of the disclosure so that third party application can improve user experience according to the flow restriction level adjustment resource loading strategy that estimates.

Description

Flow monitoring method, device and terminal equipment

technical field

The present disclosure relates to the technical field of mobile communication, and in particular to a traffic monitoring method, device and terminal equipment.

Background technique

At present, all mobile terminals have mobile Internet access functions, and major operators have launched various business data traffic packages. With the reduction of traffic charges by operators, more and more people choose to use traffic to access the mobile Internet.

Contents of the invention

In order to overcome the problems existing in related technologies, the present disclosure provides a flow monitoring method, device and terminal equipment.

According to a first aspect of an embodiment of the present disclosure, a flow monitoring method is provided, including:

Obtain user traffic information;

The traffic restriction level of the user is estimated according to the user traffic information, so that the third-party application adjusts the resource loading strategy according to the traffic restriction level.

Optionally, the acquisition of user traffic information includes:

The user flow information is obtained according to the created system interface or through SMS query, wherein the created system interface includes a flow query interface and/or an operator interface.

Optionally, the acquiring user traffic information according to the created system interface includes:

Obtain the current user's remaining traffic information through the created system interface periodically or according to user requests.

Optionally, the method further includes: re-determining the traffic restriction level of the user according to the remaining traffic information of the current user.

Optionally, the traffic restriction level is determined in the following manner:

determining as an unlimited level when the remaining flow is greater than a first set threshold; or,

Determine the limit level when the remaining flow is greater than the second set threshold and less than or equal to the first set threshold; or,

When the remaining flow is less than or equal to the second set threshold, it is determined as a strictly restricted level.

Optionally, the method also includes:

Outputting the estimated traffic restriction level of the user to a third-party application program through the system interface; or,

The estimated traffic restriction level of the user is checked or acquired by the third-party application program through the system interface.

According to a second aspect of an embodiment of the present disclosure, a flow monitoring device is provided, including:

An information acquisition module, configured to acquire user traffic information;

The traffic analysis module is configured to estimate the user's traffic restriction level according to the user traffic information, so that the third-party application program can adjust the resource loading strategy according to the traffic restriction level.

Optionally, the information acquisition module includes:

The first acquisition submodule is configured to acquire user traffic information according to the created system interface, wherein the created system interface includes a traffic query interface and/or an operator interface; or,

The second obtaining sub-module is used to obtain user traffic information through SMS query.

Optionally, the information obtaining module obtains the remaining traffic information of the current user through the created system interface periodically or according to user requests.

Optionally, the device also includes:

An analyzing and updating module, configured to re-determine the traffic restriction level of the user according to the remaining traffic information of the current user.

Optionally, the traffic analysis module or the analysis update module determines the traffic restriction level according to the following manner:

determining as an unlimited level when the remaining flow is greater than a first set threshold; or,

Determine the limit level when the remaining flow is greater than the second set threshold and less than or equal to the first set threshold; or,

When the remaining flow is less than or equal to the second set threshold, it is determined as a strictly restricted level.

Optionally, the device also includes:

An interaction module, configured to output the estimated traffic restriction level of the user to a third-party application program through the system interface; or, the third-party application program views or obtains the estimated traffic restriction level through the system interface User traffic restriction level.

According to a third aspect of the embodiments of the present disclosure, there is provided a terminal device, including:

processor and memory for storing processor-executable instructions;

Wherein, the processor is configured as:

Obtain user traffic information;

The user's traffic restriction level is estimated according to the user traffic information, so that the third-party application program can adjust the resource loading strategy according to the traffic restriction level.

The technical solutions provided by the embodiments of the present disclosure may include the following beneficial effects:

The disclosure can obtain user traffic information, and then estimate the user's traffic restriction level according to the user traffic information, so that the third-party application program can adjust the resource loading strategy according to the traffic restriction level, so that the third-party application program does not need to carry out the resource loading strategy by itself. Traffic management, resource loading strategy adjustments can be made according to traffic usage prompts.

In the present disclosure, the user flow information can be acquired according to the created system interface or through SMS query, wherein the created system interface includes a flow query interface and/or an operator interface, so that the user flow information can be obtained in a variety of different ways.

The disclosure can periodically obtain the remaining flow information of the current user through the created system interface or according to user requests, and can also re-determine the flow restriction level of the user according to the remaining flow information of the current user, so as to realize dynamic adjustment of the flow restriction level.

The present disclosure may determine the traffic restriction level according to the following manner: when the remaining traffic is greater than the first set threshold, it is determined as an unlimited level; or, when the remaining traffic is greater than the second set threshold and less than or equal to the first set threshold; or, determine as a strict restriction level when the remaining flow is less than or equal to the second set threshold.

In the present disclosure, the estimated traffic restriction level of the user may be output to a third-party application program through the system interface; or, the third-party application program may view or obtain the estimated user traffic restriction level through the system interface. Traffic restriction level.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure.

Description of drawings

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

Fig. 1 is a flowchart of a flow monitoring method according to an exemplary embodiment of the present disclosure.

Fig. 2 is another flowchart of a flow monitoring method according to an exemplary embodiment of the present disclosure.

Fig. 3 is a block diagram of a flow monitoring device according to an exemplary embodiment of the present disclosure.

Fig. 4 is another block diagram of a flow monitoring device according to an exemplary embodiment of the present disclosure.

Fig. 5 is a structural block diagram of a terminal device according to an exemplary embodiment of the present disclosure.

Fig. 6 is a structural block diagram of a device according to an exemplary embodiment of the present disclosure.

detailed description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatuses and methods consistent with aspects of the present disclosure as recited in the appended claims.

The terminology used in the present disclosure is for the purpose of describing particular embodiments only, and is not intended to limit the present disclosure. As used in this disclosure and the appended claims, the singular forms "a", "the", and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It should also be understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

In related technologies, if the user's monthly traffic exceeds the rated value of the package, the traffic exceeding the rated value of the package is charged according to the excess traffic, and the price charged according to the excess traffic is higher. Although the application program in the mobile terminal can send SMS instructions to the operator to query and read the traffic information returned by the operator (such as sending CXYL to 10086, 10086 will return a text message containing traffic information), or it can also specifically access the operator interface to query. However, generally third-party applications have their own services, and will not specifically access the operator interface for query or send query SMS commands. Based on this, the present disclosure provides a traffic monitoring method, so that the third-party application program can adjust the resource loading strategy according to the traffic usage prompt without performing traffic management by itself, so as to improve the user experience.

Fig. 1 is a flowchart of a flow monitoring method according to an exemplary embodiment of the present disclosure.

As shown in Figure 1, the method can be applied to terminal equipment, including the following steps:

In step 101, user traffic information is acquired.

The user traffic information obtained therein may include, for example, package traffic and remaining traffic, or may include package traffic and usage traffic, and the like.

In step 102, the traffic restriction level of the user is estimated according to the user traffic information, so that the third-party application adjusts the resource loading strategy according to the traffic restriction level.

The estimated traffic restriction level of the user may include, for example, an unlimited level, a restricted level, and a strictly restricted level, but is not limited thereto.

It can be seen from this embodiment that the disclosure can obtain user traffic information, and then estimate the user's traffic restriction level according to the user traffic information, so that the third-party application program can adjust the resource loading strategy according to the traffic restriction level, so that the first The third-party application does not need to manage the traffic itself, but can adjust the resource loading strategy according to the traffic usage prompt.

Fig. 2 is another flowchart of a flow monitoring method according to an exemplary embodiment of the present disclosure. FIG. 2 describes aspects of the present disclosure in more detail relative to FIG. 1 .

As shown in Figure 2, the method can be applied to a terminal device, including the following steps:

In step 201, user traffic information is acquired according to the created system interface or through SMS query.

The present disclosure can obtain user traffic information by means of SMS query in related methods, for example, send a text message command to an operator number, and obtain user traffic information by analyzing traffic text messages returned by the operator. The user traffic information obtained therein may include package traffic and remaining traffic information, or may include package traffic and usage traffic information, for example.

In the present disclosure, user traffic information may also be acquired according to the created system interface, where the created system interface includes a traffic query interface and/or an operator interface. Among them, the remaining flow information of the current user can be obtained periodically through the created system interface or according to the user's request.

For example, the terminal system of the present disclosure can set a traffic query interface, and a third-party application program can send a traffic query request to the terminal system to query traffic through the traffic query interface. After receiving the traffic query request, the terminal system can then query the operator through the operator interface flow. If only the traffic query interface or carrier interface is configured, you can also directly use the traffic query interface or carrier interface to query traffic. The terminal system can send the imsi (International Mobile Subscriber Identification Number, International Mobile Subscriber Identification Number) number or terminal number of the terminal sim (Subscriber Identification Module, customer identification module) card to the operator through the operator interface, and the operator receives the imsi number or terminal number, return the package traffic and remaining traffic of this imsi number or terminal number, or the package traffic and usage traffic to the terminal.

In step 202, the traffic restriction level of the user is estimated according to the user traffic information.

This step estimates the user's traffic restriction level according to the user traffic information, so that the third-party application can adjust the resource loading strategy according to the traffic restriction level.

This disclosure can classify users according to the traffic level of the package, and divide them into a set number of categories. For example, it can be divided into 5 categories but not limited to this:

a. The category of traffic tyrants, the traffic is >=10GB; b. The category of large traffic users, the traffic is 3-10GB; c. The category of normal traffic, the traffic is 600MB-3GB; d. The category of small traffic, the traffic is 30MB-600MB; e . Traffic poor category, traffic <= 30MB.

Therefore, according to the package traffic in the obtained traffic information, the traffic level of the terminal can be determined. For example, if the package traffic is 15GB>=10GB, it belongs to the category of traffic tyrants. category.

It should be noted that the traffic volume of all end users can be counted on the server side as big data for analysis, divided into several groups according to the number of people, for example, 5 groups, and each group takes the lowest traffic as the classification threshold, and then notifies the terminal of the traffic level classification. It should be noted that the above threshold for classification can be adjusted according to big data.

In the present disclosure, the usage flow can be determined according to the package flow and remaining flow in the flow information, or the remaining flow can be determined according to the package flow and usage flow in the flow information; the daily average usage can be determined according to the usage flow and usage time ; Determine the estimated usage based on the stated average daily usage and remaining time.

For example, based on the package traffic, usage traffic and remaining traffic, the daily traffic consumption of the user this month can be calculated, and then it can be calculated whether the user will exceed the package traffic this month. For example, by querying the operator, you can know that the user's package this month is 1GB and the remaining traffic is 400MB. You can determine that the usage traffic is 1GB-400MB=600MB, and you can know the day of the month. If it is the 20th, then This month’s daily traffic consumption = (1GB-400MB)/20 days=30MB/day, and the remaining 10 days will use 30MB/day*10 days=300MB<remaining traffic 400MB, that is, it will not exceed the package traffic.

With reference to the above analysis, the present disclosure can classify the estimated traffic restriction level of the user into the following types according to the remaining traffic but not limited thereto:

When the remaining traffic is greater than the first set threshold, such as 3G, it is determined as an unlimited level, and it is recommended not to limit resource loading, and various resources can be loaded freely, such as automatically playing music, video or loading pictures, etc.; or, in the remaining traffic When it is greater than the second set threshold, such as 30MB, and is less than or equal to the first set threshold, such as 3G, it is determined as a restriction level, and a slight resource loading restriction can be suggested, such as not automatically playing music, video or loading pictures, etc.; or, in the remaining When the traffic is less than or equal to the second set threshold, for example, 30 MB, it is determined as a strictly restricted level, and it is recommended to prohibit resource loading, such as not loading any music, video or pictures. Wherein, each threshold can be adjusted according to the situation.

In step 203, the estimated traffic restriction level of the user is output to a third-party application program through the system interface, or the third-party application program checks or obtains the estimated user traffic limit level through the system interface. traffic restriction level.

In this step, the estimated traffic restriction level of the user may be actively output to a third-party application program, or the third-party application program may actively view or obtain the estimated traffic restriction level of the user.

After the third-party application obtains the estimated traffic restriction level of the user, it can adjust the resource loading policy according to the traffic restriction level, such as not automatically playing music, video or loading pictures, or not loading any music, video or pictures.

It should be noted that, in addition to outputting the traffic restriction level to the third-party application for reference, data such as the user's traffic level, remaining traffic size, and whether the traffic will be exceeded can also be sent to the third-party application at the same time.

It can be seen from this embodiment that the present disclosure can obtain user traffic information through the traffic query interface of the terminal system, estimate the user's traffic restriction level according to the user traffic information, and send it to a third-party application program or have the third-party application program actively View or obtain, so that the third-party application can adjust the resource loading strategy according to the obtained traffic usage prompt without performing traffic management by itself.

Corresponding to the aforementioned embodiments of the method for implementing application functions, the present disclosure also provides a flow monitoring device and corresponding embodiments.

Fig. 3 is a block diagram of a flow monitoring device according to an exemplary embodiment of the present disclosure.

The device may be set in a terminal device. Referring to FIG. 3 , a flow monitoring device may include: an information acquisition module 31 and a flow analysis module 32 .

The information acquiring module 31 is configured to acquire user traffic information.

The user traffic information obtained therein may include, for example, package traffic and remaining traffic, or may include package traffic and usage traffic, and the like.

The traffic analysis module 32 is configured to estimate the traffic restriction level of the user according to the user traffic information acquired by the information acquisition module 31, so that the third-party application can adjust the resource loading policy according to the traffic restriction level.

The estimated traffic restriction level of the user may include, for example, an unlimited level, a restricted level, and a strictly restricted level, but is not limited thereto.

It can be seen from this embodiment that the disclosure can obtain user traffic information, and then estimate the user's traffic restriction level according to the user traffic information, so that the third-party application program can adjust the resource loading strategy according to the traffic restriction level, so that the first The third-party application does not need to manage the traffic itself, but can adjust the resource loading strategy according to the traffic usage prompt.

Fig. 4 is another block diagram of a flow monitoring device according to an exemplary embodiment of the present disclosure.

The device may be set in a terminal device. Referring to FIG. 4 , a flow monitoring device may include: an information acquisition module 31 , a flow analysis module 32 , an analysis update module 33 , and an interaction module 34 .

Wherein, the functions of the information acquisition module 31 and the traffic analysis module 32 can refer to the description of FIG. 3 .

Wherein, the information acquisition module 31 includes: a first acquisition sub-module 311 or a second acquisition sub-module 312 .

The first obtaining sub-module 311 is configured to obtain user traffic information according to the created system interface, wherein the created system interface includes a traffic query interface and/or an operator interface.

The second acquisition sub-module 312 is configured to acquire user traffic information through SMS query.

Wherein, the information obtaining module 31 may obtain the remaining flow information of the current user periodically through the created system interface or according to the user's request.

The analyzing and updating module 33 is configured to re-determine the traffic restriction level of the user according to the remaining traffic information of the current user.

Wherein, the flow analysis module 32 or the analysis update module 33 can determine the flow restriction level in the following manner: when the remaining flow is greater than the first set threshold, it is determined as an unlimited level; or, when the remaining flow is greater than the second set threshold threshold and is less than or equal to the first set threshold, it is determined as the restriction level; or, when the remaining flow is less than or equal to the second set threshold, it is determined as the strict restriction level.

For example, when the remaining traffic is greater than the first set threshold, such as 3G, it is determined to be an unlimited level, it may be suggested that no resource loading restrictions be imposed, and various resources can be loaded freely, such as automatically playing music, videos or loading pictures, etc.; or, in When the remaining traffic is greater than the second set threshold, such as 30MB, and is less than or equal to the first set threshold, such as 3G, it is determined as a restriction level, and a slight resource loading restriction can be suggested, such as not automatically playing music, video or loading pictures, etc.; or, When the remaining traffic is less than or equal to the second set threshold, for example, 30 MB, it is determined as a strictly restricted level, and it is recommended to prohibit resource loading, such as not loading any music, video or pictures. Wherein, each threshold can be adjusted according to the situation.

The interaction module 34 is configured to output the estimated traffic restriction level of the user to a third-party application through the system interface; or, the third-party application checks or obtains the estimate through the system interface The traffic restriction level of the user.

For the implementation process of the functions and effects of each unit in the above device, please refer to the implementation process of the corresponding steps in the above method for details, and will not be repeated here.

As for the device embodiment, since it basically corresponds to the method embodiment, for related parts, please refer to the part description of the method embodiment. The device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place , or can also be distributed to multiple network elements. Part or all of the modules can be selected according to actual needs to achieve the purpose of the disclosed solution. It can be understood and implemented by those skilled in the art without creative effort.

Fig. 5 is a structural block diagram of a terminal device according to an exemplary embodiment of the present disclosure.

Referring to FIG. 5, the terminal device may include: a processor 501 and a memory 502 for storing instructions executable by the processor 501;

Wherein, the processor 501 is configured as:

Obtain user traffic information;

The user's traffic restriction level is estimated according to the user traffic information, so that the third-party application program can adjust the resource loading strategy according to the traffic restriction level.

It should also be noted that for other programs stored in the memory 502 , refer to the description in the foregoing method flow for details, and details are not repeated here. The processor 501 is also configured to execute other programs stored in the memory 502 .

Fig. 6 is a structural block diagram of a device according to an exemplary embodiment of the present disclosure.

Referring to FIG. 6, for example, the device 600 may be a mobile phone with a routing function, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, and the like.

Device 600 includes one or more of the following components: processing component 602, memory 604, power supply component 606, multimedia component 608, audio component 610, input/output (I/O) interface 612, sensor component 614, and communication component 616.

Processing component 602 generally controls the overall operations of device 600, such as those associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 602 may include one or more processors 620 to execute instructions to complete all or part of the steps of the above method. Additionally, processing component 602 may include one or more modules that facilitate interaction between processing component 602 and other components. For example, processing component 602 may include a multimedia module to facilitate interaction between multimedia component 608 and processing component 602 .

The memory 604 is configured to store various types of data to support operations at the device 600 . Examples of such data include instructions for any application or method operating on device 600, contact data, phonebook data, messages, pictures, videos, and the like. The memory 604 can be implemented by any type of volatile or non-volatile storage device or their combination, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Magnetic or Optical Disk.

The power supply component 606 provides power to various components of the device 600 . Power components 606 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for device 600 .

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

The audio component 610 is configured to output and/or input audio signals. For example, the audio component 610 includes a microphone (MIC) configured to receive external audio signals when the device 600 is in operation modes, such as call mode, recording mode and voice recognition mode. Received audio signals may be further stored in memory 604 or sent via communication component 616 . In some embodiments, the audio component 610 also includes a speaker for outputting audio signals.

The I/O interface 612 provides an interface between the processing component 602 and a peripheral interface module. The peripheral interface module may be a keyboard, a click wheel, a button, and the like. These buttons may include, but are not limited to: a home button, volume buttons, start button, and lock button.

Sensor assembly 614 includes one or more sensors for providing status assessments of various aspects of device 600 . For example, the sensor component 614 can detect the open/closed state of the device 600, the relative positioning of components, such as the display and the keypad of the device 600, the sensor component 614 can also detect the position change of the device 600 or a component of the device 600, and the user Presence or absence of contact with device 600 , device 600 orientation or acceleration/deceleration and temperature change of device 600 . The sensor assembly 614 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact. Sensor assembly 614 may also include optical sensors, such as CMOS or CCD image sensors, for use in imaging applications. In some embodiments, the sensor component 614 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.

Communication component 616 is configured to facilitate wired or wireless communications between device 600 and other devices. The device 600 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 616 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 616 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wide Band (UWB) technology, Bluetooth (BT) technology and other technologies.

In an exemplary embodiment, device 600 may be programmed by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation for performing the methods described above.

In an exemplary embodiment, there is also provided a non-transitory computer-readable storage medium including instructions, such as the memory 604 including instructions, which can be executed by the processor 620 of the device 600 to implement the above method. For example, the non-transitory computer readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

A non-transitory computer-readable storage medium, when the instructions in the storage medium are executed by the processor of the terminal device, the terminal device can execute the traffic monitoring method, the method includes:

Obtain user traffic information;

The user's traffic restriction level is estimated according to the user traffic information, so that the third-party application program can adjust the resource loading strategy according to the traffic restriction level.

Other embodiments of the present disclosure will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. The present disclosure is intended to cover any modification, use or adaptation of the present disclosure. These modifications, uses or adaptations follow the general principles of the present disclosure and include common knowledge or conventional technical means in the technical field not disclosed in the present disclosure. . The specification and examples are to be considered exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It should be understood that the present disclosure is not limited to the precise constructions which have been described above and shown in the drawings, and various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (13)

1. A method of flow monitoring, comprising:

acquiring user flow information;

and estimating the flow limit level of the user according to the user flow information so as to adjust a resource loading strategy by a third-party application program according to the flow limit level.

2. The method of claim 1, wherein the obtaining user traffic information comprises:

and acquiring user flow information according to a created system interface or in a short message query mode, wherein the created system interface comprises a flow query interface and/or an operator interface.

3. The method of claim 2, wherein the obtaining user traffic information according to the created system interface comprises:

and acquiring the residual flow information of the current user periodically or according to a user request through the created system interface.

4. The method of claim 3, further comprising:

and re-determining the flow limit level of the user according to the residual flow information of the current user.

5. The method according to any of claims 1 to 4, characterized in that the flow restriction level is determined according to the following way:

determining as an unlimited level when the residual flow is greater than a first set threshold; or,

determining the residual flow as a limiting level when the residual flow is greater than a second set threshold and less than or equal to the first set threshold; or,

and determining the residual flow rate to be a strict limiting level when the residual flow rate is less than or equal to the second set threshold value.

6. The method according to any one of claims 2 to 4, further comprising:

outputting the estimated flow restriction level of the user to a third-party application program through the system interface; or,

and viewing or acquiring the estimated flow restriction level of the user by the third-party application program through the system interface.

7. A flow monitoring device, comprising:

the information acquisition module is used for acquiring user flow information;

and the flow analysis module is used for predicting the flow limit level of the user according to the user flow information so as to adjust a resource loading strategy by a third-party application program according to the flow limit level.

8. The apparatus of claim 7, wherein the information obtaining module comprises:

the first acquisition submodule is used for acquiring user flow information according to a created system interface, wherein the created system interface comprises a flow inquiry interface and/or an operator interface; or,

and the second acquisition sub-module is used for acquiring the user traffic information in a short message query mode.

9. The apparatus of claim 8, wherein:

the information acquisition module acquires the residual flow information of the current user periodically or according to a user request through the created system interface.

10. The apparatus of claim 9, further comprising:

and the analysis updating module is used for re-determining the flow limit level of the user according to the residual flow information of the current user.

11. The apparatus according to any one of claims 7 to 10, wherein:

the traffic analysis module or the analysis update module determines a traffic limit level according to:

determining as an unlimited level when the residual flow is greater than a first set threshold; or,

determining the residual flow as a limiting level when the residual flow is greater than a second set threshold and less than or equal to the first set threshold; or,

and determining the residual flow rate to be a strict limiting level when the residual flow rate is less than or equal to the second set threshold value.

12. The apparatus of any one of claims 8 to 10, further comprising:

the interaction module is used for outputting the estimated flow restriction level of the user to a third-party application program through the system interface; or the third-party application program views or acquires the estimated flow restriction level of the user through the system interface.

13. A terminal device, comprising:

a processor and a memory for storing processor-executable instructions;

wherein the processor is configured to:

acquiring user flow information;

and estimating the flow limit level of the user according to the user flow information so that a third-party application program can adjust a resource loading strategy according to the flow limit level.