CN113452553A - Content distribution network flow limiting method and system - Google Patents
Content distribution network flow limiting method and system Download PDFInfo
- Publication number
- CN113452553A CN113452553A CN202110680127.2A CN202110680127A CN113452553A CN 113452553 A CN113452553 A CN 113452553A CN 202110680127 A CN202110680127 A CN 202110680127A CN 113452553 A CN113452553 A CN 113452553A
- Authority
- CN
- China
- Prior art keywords
- strategy
- time
- limiting
- preset
- flow limiting
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 41
- 238000001514 detection method Methods 0.000 claims abstract description 44
- 230000009286 beneficial effect Effects 0.000 abstract description 3
- 230000002354 daily effect Effects 0.000 description 3
- 230000001133 acceleration Effects 0.000 description 2
- 230000003203 everyday effect Effects 0.000 description 2
- 230000003111 delayed effect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/658—Incremental updates; Differential updates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/32—Flow control; Congestion control by discarding or delaying data units, e.g. packets or frames
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a content distribution network flow limiting method and a system, belonging to the technical field of OTA (over the air) upgrading, wherein the method comprises the following steps: step S1, receiving a detection request, and acquiring a flow limiting strategy from a cache according to the detection request; step S2, analyzing the flow limiting strategy according to the preset strategy analysis rule to obtain the number of detectable devices limited by the flow limiting strategy within a preset limiting time; step S3, obtaining the number of devices detected within the preset time limit, and determining whether to respond to the detection request according to the number of devices detected within the preset time limit and the size of the number of devices that can be detected. The beneficial effects of this technical scheme lie in: the number of the detectable devices in a period of time is limited, so that the CDN flow is controlled, and the problem that the CDN flow is suddenly increased to cause network blockage and the payment cannot be carried out is avoided.
Description
Technical Field
The invention relates to the technical field of OTA (over the air) upgrading, in particular to a content distribution network flow limiting method and system.
Background
Over-the-air programming (OTA) is a method of distributing new firmware, applications, configurations, and even updating encryption keys for devices. When the internet of things equipment carries out OTA upgrading on line, CDN flow can be generated when a Content Delivery Network (CDN) is used for acceleration, namely the Network acceleration can generate a data usage amount, the usage amount in the period is counted up in a period, and the CDN flow is similar to the Network flow usage amount.
With the development of the internet, users pay more attention to the browsing speed and effect of websites when using the network, but as the number of netizens increases, the network access path is too long, so that the access quality of users is seriously affected. Especially when the link between the user and the website is congested by sudden large flow data, the poor access quality is a more troubling problem for the areas where the users of the internet in different places are increasing rapidly. Therefore, the CDN is used more and more rapidly, and the generated CDN traffic is also increased, which leads to a problem that the CDN traffic exceeds standard but the user cannot pay in the OTA upgrade process.
Disclosure of Invention
Aiming at the problems in the prior art, a content distribution network flow limiting method and a content distribution network flow limiting system are provided, aiming at solving the problem that the content distribution network flow exceeds the standard but the user can not pay in the OTA upgrading process, and the OTA flexible upgrading is completed by reasonably limiting a preset number of devices through a flow limiting strategy.
The content distribution network flow limiting method comprises the following steps:
step S1, receiving a detection request, and obtaining the flow limiting strategy from the cache according to the detection request;
step S2, analyzing the flow limiting strategy according to a preset strategy analysis rule to obtain the number of detectable devices limited by the flow limiting strategy within a preset limiting time;
step S3, obtaining the number of detected devices within the preset time limit, and determining whether to respond to the detection request according to the number of detected devices within the preset time limit and the size of the detectable device number.
Preferably, the step S1 specifically includes:
step S11, receiving the detection request, and analyzing the detection request to obtain the version ID of the equipment which sends the detection request and needs to be upgraded;
step S12, obtaining the traffic limitation policy corresponding to the version ID from the cache according to the version ID.
Preferably, in step S1, the method further includes:
and if the flow limiting strategy is not acquired from the cache, the flow of the content distribution network is not limited currently, and the detection request is responded.
Preferably, the method further comprises the following steps:
and acquiring the effective flow limiting strategy from the database at intervals of a first preset time, and storing the effective flow limiting strategy into the cache.
Preferably, the latest effective traffic limitation policy obtained from the database at every first preset time overrides the original traffic limitation policy in the cache.
Preferably, the method further comprises the following steps:
setting the expiration time of a second preset time for the cache;
and deleting the flow limiting strategy stored in the cache from the cache every second preset time.
Preferably, the second preset time is slightly longer than the first preset time.
Preferably, the traffic limitation policy includes mode, whether or not to limit outside of a time period, time, number of devices detectable to limit.
Preferably, the method further comprises the following steps:
when the flow limiting strategy is modified, the modified flow limiting strategy is stored in the database, and the number of detected devices in the preset limiting time which is counted originally is not emptied;
and when the flow limiting strategy is deleted, clearing the number of the detected devices within the preset limiting time which is originally counted.
Preferably, the obtaining of the effective flow restriction policy from the database at every first preset time specifically includes:
acquiring current time;
and comparing the time included in the flow limiting strategy in the database with the current time to obtain the effective flow limiting strategy.
Preferably, the method further comprises the following steps:
selecting a corresponding strategy type through a strategy configuration interface by a user, and configuring corresponding parameters for the strategy type to generate the flow limiting strategy;
storing the generated flow limitation strategy in the database.
The present invention also provides a content distribution network traffic limiting system, for implementing the content distribution network traffic limiting method, the system includes:
the first obtaining unit is used for obtaining the effective flow limiting strategy from the database at intervals of a first preset time and storing the effective flow limiting strategy into the cache;
a receiving unit, configured to receive a detection request;
the second obtaining unit is connected with the receiving unit and used for obtaining the flow limiting strategy from the cache according to the detection request;
the analysis unit is connected with the acquisition unit and used for analyzing the flow limiting strategy according to a preset strategy analysis rule to obtain the number of detectable devices limited by the flow limiting strategy within a preset limiting time;
and the comparison unit is connected with the analysis unit and used for acquiring the number of the detected devices within the preset limit time and comparing the number of the detected devices within the preset limit time with the number of the detectable devices.
The technical scheme of the invention has the beneficial effects that:
the method and the system for limiting the flow of the content delivery network are provided, different flow limiting strategies are stored in a database, the time, the detectable equipment number and the detected equipment number in the same time in the flow limiting strategies are compared to limit the detectable equipment number in a period of time, so that idle and busy scheduling is realized, the CDN flow is controlled, the problem that the CDN flow is suddenly increased to cause network blockage and cannot be paid is solved, the upgrading result of the equipment is flexibly controlled according to the flow limiting strategies, the flow consumption is controlled, and the cost is further saved.
Drawings
Fig. 1 is a flow chart illustrating a content distribution network traffic limiting method according to a preferred embodiment of the present invention;
FIG. 2 is a schematic flow chart of step S1 according to the preferred embodiment of the present invention;
fig. 3 is a block diagram of a content distribution network traffic limiting system according to a preferred embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the embodiments and features of the embodiments may be combined with each other without conflict.
The invention is further described with reference to the following drawings and specific examples, which are not intended to be limiting.
Referring to fig. 1-3, the present invention provides a content delivery network traffic limiting method, which belongs to the technical field of OTA upgrade, and as shown in fig. 1, the method includes:
step S1, receiving a detection request, and obtaining a traffic restriction policy from the cache 2 according to the detection request;
step S2, analyzing the flow limiting strategy according to a preset strategy analysis rule to obtain the number of detectable devices limited by the flow limiting strategy within a preset limiting time;
step S3, obtaining the number of devices detected within the preset time limit, and determining whether to respond to the detection request according to the number of devices detected within the preset time limit and the size of the number of devices that can be detected.
Specifically, each time a detection request enters, after a version is detected, a corresponding key in read is iot: flow: limit: policy: $ id }: data for $ deltaId, where deltaId refers to the version Id that needs to be upgraded; if the corresponding path in the cache 2 is empty, it indicates that the CDN flow is not currently restricted; if the corresponding path in the cache 2 is not empty, the flow restriction policy is analyzed, and the corresponding field is analyzed according to a predetermined policy analysis rule.
Further, the value of the traffic limitation policy is $ { mode }: $ outside time period whether or not to restrict }: $ time }: $ limit, type is string.
$ mode }: 0 represents daily; 1 represents per hour;
$ outside time period whether or not to restrict }: 0 represents outside the time period without limitation; 1 represents an out of time limit;
$ time }: 0 represents the whole day; 1700-2300 represents 17 to 23 points of the day;
$ limit number }: -1 represents no numerical limitation; non-negative or non-zero means that the number of devices detectable is limited in time, typically by a limit of < 1000.
In step S2, the traffic limitation policy is parsed according to a preset policy parsing rule, where the preset policy parsing rule specifically includes:
if there is a time-segment limit in the flow restriction policy: within the time period range, resolving the mode and the limit number; outside the time period: "out of time limit" is resolved.
If there is no time period limitation in the flow limitation strategy: it means default to 0 point-24 points, and then "limit number" is parsed.
In step S3, if the detected number of devices is less than the detectable number of devices, the detection request is responded to indicate that there is a remaining amount of the detected version for the devices to download and upgrade within the preset limit time.
As a preferred embodiment, as shown in fig. 2, step S1 specifically includes:
step S11, receiving the detection request, and analyzing the detection request to obtain the version ID of the equipment which sends the detection request and needs to be upgraded;
step S12, obtaining the traffic limitation policy corresponding to the version ID from the cache 2 according to the version ID.
Furthermore, the extracted traffic restriction policy may be analyzed after the traffic restriction policy is extracted from the database 1, and the analyzed field is stored in the cache 2, and then, after the detection request is received, the policy is directly extracted from the cache without performing an analysis process.
In a preferred embodiment, step S1 further includes:
if the traffic restriction policy is not obtained from the cache 2, it indicates that the content delivery network traffic is not currently restricted, and responds to the detection request.
Specifically, if the detection request is received, but the cache 2 does not have a valid traffic restriction policy, which indicates that the content distribution network traffic is not limited currently, any number of devices can detect the version to download and upgrade, and respond to the detection request to notify the device sending the detection request to download and upgrade the version.
As a preferred embodiment, the method further comprises:
and acquiring the effective flow limiting strategy from the database 1 at intervals of a first preset time, and storing the effective flow limiting strategy into a cache Redis.
As a preferred embodiment, the latest valid traffic limitation policy obtained from the database 1 every first preset time overrides the original traffic limitation policy in the cache 2.
Specifically, after the information of the traffic restriction policy is read and analyzed from the database 1, the information is stored in the cache redis for being read and used by other interfaces, and since the expiration time of the redis is 4 minutes, the latest effective traffic restriction policy is read from the database 1 every 3 minutes and stored in the redis, thereby covering the policy in the redis. If the strategy is invalid, waiting for 4 minutes until the redis data is expired.
As a preferred embodiment, the method further comprises:
setting the expiration time of a second preset time for the cache 2;
the traffic limitation policy stored in the cache 2 is deleted from the cache 2 every second preset time.
In a preferred embodiment, the second predetermined time is slightly longer than the first predetermined time.
Specifically, in this embodiment, the second preset time is 4 minutes, the first preset time is 3 minutes, that is, the effective flow restriction policy is obtained from the database 1 every 3 minutes; the traffic limitation policy stored in the cache 2 is removed from the cache 2 every 4 minutes.
As a preferred embodiment, the flow restriction policy includes mode, whether to restrict outside of a time period, time, number of devices detectable to restrict.
As a preferred embodiment, the method further comprises:
when the flow limiting strategy is modified, the modified flow limiting strategy is stored in the database 1, and the number of detected devices in the originally counted preset limiting time is not emptied;
and when the flow limiting strategy is deleted, clearing the number of the detected devices within the originally counted preset limiting time.
Specifically, when the original strategy is modified, the number of devices detected per hour/day counted before is not emptied; when the original strategy is deleted, the counted number of devices detected per hour/day before is emptied. For example: the original strategy is that the number of devices to be detected is set to 50 every day, if 50 devices are currently detected. After the flow limiting strategy is modified, at this time, the number of the detectable devices is set to 40, the previous 50 detection records are not emptied, but the new devices still cannot detect the flow limiting strategy;
assuming that the original strategy is that the number of detectable devices per day is set to 50, if 50 devices are currently available for detection. After the flow limiting strategy is modified, the number of the detectable devices is set to 60, the previous 50 detection records are not emptied, and at most 10 new devices can detect the flow limiting strategy;
however, if the original policy is directly deleted, and the new policy is reset to 60 devices detectable every day, then the original statistical detection records of 50 detected devices are emptied, and at this time, 60 new devices can detect the devices.
Further, when the traffic limitation policy is modified, not only the number of limitations of the detectable device may be modified, but also other parameters, such as mode, whether or not to limit outside the time period, and time, may be modified.
As a preferred embodiment, the obtaining of the effective flow restriction policy from the database 1 at intervals of a first preset time specifically includes:
acquiring current time;
the time included in the traffic restriction policy in the database 1 is compared with the current time to obtain an effective traffic restriction policy.
Specifically, in this embodiment, when the traffic limitation policy in the database 1 is extracted in the cache 2, it is determined whether the current time of the extraction time is within the effective time of the traffic limitation policy, so as to determine whether the current policy is effective.
As a preferred embodiment, the method further comprises:
a user selects a corresponding strategy type through a strategy configuration interface and configures corresponding parameters for the strategy type to generate a flow limiting strategy;
the generated flow restriction policy is stored in the database 1.
Specifically, the policy configuration interface includes four policy types: idle time detection, daily limitation, hour limitation and delayed scheduling;
to illustrate by way of example: the first strategy is idle detection, and the value is 0: 1: 0000-1700: -1; it means that only versions within the idle time range (00: 00-17: 00) can be detected for downloading and upgrading;
the second strategy is daily restriction
Number of detectable devices per day: 1314
The effective time is as follows: 2021-05-02-2021-05-10
Extracting a value: 0: 0: 0: 1314;
strategy three is an hourly restriction
Number of detectable devices per hour: 1314
The effective time is as follows: 2021-05-02 to 2021-05-10; 09: 12: 21-11: 12: 21
Extracting a value: 1: 0: 0912-1112: 1314;
and (4) strategy four: delay scheduling (Busy, need to schedule backwards)
Busy period limit detection number: 1314
The effective time is as follows: 17: 00-24: 00
Extracting a value: 0: 0: 1700-2400: 1314;
the limit detection number and the effective time in each strategy can be set according to actual requirements, and after the setting is completed, the value of the corresponding flow limit strategy can be generated according to the set parameters.
The present invention also provides a content distribution network traffic limiting system, for implementing the content distribution network traffic limiting method as described above, as shown in fig. 3, the system includes:
a first obtaining unit 3, configured to obtain an effective traffic restriction policy from the database 1 every first preset time, and store the effective traffic restriction policy in the cache 2;
a receiving unit 4, configured to receive a detection request;
a second obtaining unit 5, connected to the receiving unit 4, configured to obtain the traffic restriction policy from the cache 2 according to the detection request;
the analysis unit 6 is connected with the second acquisition unit 5 and is used for analyzing the flow restriction policy according to a preset policy analysis rule to obtain the number of detectable devices limited by the flow restriction policy within a preset limit time;
and the comparing unit 7 is connected with the analyzing unit 6 and is used for acquiring the number of the detected devices within the preset limit time and comparing the number of the detected devices within the preset limit time with the number of the detectable devices.
The technical scheme of the invention has the beneficial effects that:
the method and the system for limiting the flow of the content delivery network are provided, different flow limiting strategies are stored in a database, the time, the detectable equipment number and the detected equipment number in the same time in the flow limiting strategies are compared to limit the detectable equipment number in a period of time, so that idle and busy scheduling is realized, the CDN flow is controlled, the problem that the CDN flow is suddenly increased to cause network blockage and cannot be paid is solved, the upgrading result of the equipment is flexibly controlled according to the flow limiting strategies, the flow consumption is controlled, and the cost is further saved.
While the invention has been described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention.
Claims (12)
1. A content distribution network traffic limiting method, the method comprising:
step S1, receiving a detection request, and obtaining the flow limiting strategy from a cache according to the detection request;
step S2, analyzing the flow limiting strategy according to a preset strategy analysis rule to obtain the number of detectable devices limited by the flow limiting strategy within a preset limiting time;
step S3, obtaining the number of detected devices within the preset time limit, and determining whether to respond to the detection request according to the number of detected devices within the preset time limit and the size of the detectable device number.
2. The method for restricting content delivery network traffic according to claim 1, wherein the step S1 specifically includes:
step S11, receiving the detection request, and analyzing the detection request to obtain the version ID of the equipment which sends the detection request and needs to be upgraded;
step S12, obtaining the traffic limitation policy corresponding to the version ID from the cache according to the version ID.
3. The content distribution network traffic limiting method according to claim 1, wherein in step S1, the method further comprises:
and if the flow limiting strategy is not acquired from the cache, the flow of the content distribution network is not limited currently, and the detection request is responded.
4. The content distribution network traffic limiting method according to claim 1, further comprising:
and acquiring the effective flow limiting strategy from the database at intervals of a first preset time, and storing the effective flow limiting strategy into the cache.
5. The method as claimed in claim 4, wherein the latest valid traffic limitation policy is obtained from the database every other first predetermined time, and the latest valid traffic limitation policy is overwritten on the original traffic limitation policy in the cache.
6. The content distribution network traffic limiting method according to claim 4, further comprising:
setting the expiration time of a second preset time for the cache;
and deleting the flow limiting strategy stored in the cache from the cache every second preset time.
7. The content distribution network traffic limiting method of claim 6, wherein the second predetermined time is slightly longer than the first predetermined time.
8. The content distribution network traffic limiting method of claim 1, wherein the traffic limiting policy comprises a mode, whether or not to limit outside a time period, a time, and a number of devices detectable to limit.
9. The content distribution network traffic limiting method according to claim 1, further comprising:
when the flow limiting strategy is modified, the modified flow limiting strategy is stored in a database, and the number of detected devices in the preset limiting time which is counted originally is not emptied;
and when the flow limiting strategy is deleted, clearing the number of the detected devices within the preset limiting time which is originally counted.
10. The method for restricting the traffic of the content distribution network according to claim 4, wherein the obtaining of the effective traffic restriction policy from the database at intervals of a first preset time specifically includes:
acquiring current time;
and comparing the time included in the flow limiting strategy in the database with the current time to obtain the effective flow limiting strategy.
11. The content distribution network traffic limiting method according to claim 1, further comprising:
selecting a corresponding strategy type through a strategy configuration interface by a user, and configuring corresponding parameters for the strategy type to generate the flow limiting strategy;
storing the generated flow limitation strategy in a database.
12. A content distribution network traffic limiting system for implementing the content distribution network traffic limiting method according to any one of claims 1 to 11, the system comprising:
the first obtaining unit is used for obtaining the effective flow limiting strategy from the database at intervals of a first preset time and storing the effective flow limiting strategy into the cache;
a receiving unit, configured to receive a detection request;
the second obtaining unit is connected with the receiving unit and used for obtaining the flow limiting strategy from the cache according to the detection request;
the analysis unit is connected with the second acquisition unit and used for analyzing the flow limiting strategy according to a preset strategy analysis rule to obtain the number of detectable devices limited by the flow limiting strategy within a preset limiting time;
and the comparison unit is connected with the analysis unit and used for acquiring the number of the detected devices within the preset limit time and comparing the number of the detected devices within the preset limit time with the number of the detectable devices.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110680127.2A CN113452553A (en) | 2021-06-18 | 2021-06-18 | Content distribution network flow limiting method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110680127.2A CN113452553A (en) | 2021-06-18 | 2021-06-18 | Content distribution network flow limiting method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113452553A true CN113452553A (en) | 2021-09-28 |
Family
ID=77811819
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110680127.2A Pending CN113452553A (en) | 2021-06-18 | 2021-06-18 | Content distribution network flow limiting method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113452553A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114257598A (en) * | 2021-12-17 | 2022-03-29 | 北京金堤科技有限公司 | Resource downloading method and device, storage medium and electronic equipment |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014059838A1 (en) * | 2012-10-18 | 2014-04-24 | 中兴通讯股份有限公司 | Method and device for adjusting quality of service policy |
| WO2018010011A1 (en) * | 2016-07-13 | 2018-01-18 | Blackberry Limited | Updating firmware at enterprise devices |
| CN109412959A (en) * | 2018-09-10 | 2019-03-01 | 广州小鹏汽车科技有限公司 | A kind of vehicle OTA upgrading Current limited Control mthods, systems and devices |
| CN110535776A (en) * | 2019-07-09 | 2019-12-03 | 中移（杭州）信息技术有限公司 | Gateway current-limiting method, device, gateway, system and storage medium |
| CN111078241A (en) * | 2018-10-22 | 2020-04-28 | 成都鼎桥通信技术有限公司 | OTA (over the air) upgrading method and device |
| CN111988817A (en) * | 2020-06-29 | 2020-11-24 | 百度在线网络技术（北京）有限公司 | Control method and device for OTA data packet issuing flow |
| CN112486535A (en) * | 2020-11-27 | 2021-03-12 | 红石阳光（北京）科技股份有限公司 | Remote upgrading method and system for NB-IoT (NB-IoT) equipment |
| CN112596768A (en) * | 2020-12-16 | 2021-04-02 | 珠海格力电器股份有限公司 | Device updating method and device, storage medium and electronic device |
-
2021
- 2021-06-18 CN CN202110680127.2A patent/CN113452553A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014059838A1 (en) * | 2012-10-18 | 2014-04-24 | 中兴通讯股份有限公司 | Method and device for adjusting quality of service policy |
| WO2018010011A1 (en) * | 2016-07-13 | 2018-01-18 | Blackberry Limited | Updating firmware at enterprise devices |
| CN109412959A (en) * | 2018-09-10 | 2019-03-01 | 广州小鹏汽车科技有限公司 | A kind of vehicle OTA upgrading Current limited Control mthods, systems and devices |
| CN111078241A (en) * | 2018-10-22 | 2020-04-28 | 成都鼎桥通信技术有限公司 | OTA (over the air) upgrading method and device |
| CN110535776A (en) * | 2019-07-09 | 2019-12-03 | 中移（杭州）信息技术有限公司 | Gateway current-limiting method, device, gateway, system and storage medium |
| CN111988817A (en) * | 2020-06-29 | 2020-11-24 | 百度在线网络技术（北京）有限公司 | Control method and device for OTA data packet issuing flow |
| CN112486535A (en) * | 2020-11-27 | 2021-03-12 | 红石阳光（北京）科技股份有限公司 | Remote upgrading method and system for NB-IoT (NB-IoT) equipment |
| CN112596768A (en) * | 2020-12-16 | 2021-04-02 | 珠海格力电器股份有限公司 | Device updating method and device, storage medium and electronic device |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114257598A (en) * | 2021-12-17 | 2022-03-29 | 北京金堤科技有限公司 | Resource downloading method and device, storage medium and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104462978B (en) | A kind of method and apparatus of application program rights management | |
| US6976251B2 (en) | Intelligent update agent | |
| US10489476B2 (en) | Methods and devices for preloading webpages | |
| US8566527B2 (en) | System and method for usage analyzer of subscriber access to communications network | |
| CN111290696B (en) | Flow control method and device for application program component | |
| CN103810176A (en) | Pre-fetching accessing method and device of webpage information | |
| CN111695032A (en) | Method and device for recommending function based on user operation record | |
| CN103677864A (en) | Method for upgrading software and terminal | |
| CN105245567B (en) | A kind of processing updates the method and server system of request | |
| CN106254404A (en) | Application software authority recommends methods, devices and systems | |
| CN113806651B (en) | Data caching method, device, server and storage medium | |
| CN109714393A (en) | A kind of method and device that application program is recommended | |
| CN109688094B (en) | Suspicious IP configuration method, device, equipment and storage medium based on network security | |
| CN113452553A (en) | Content distribution network flow limiting method and system | |
| CN111416883B (en) | Address query method, device, terminal and computer readable storage medium | |
| CN108073408B (en) | System updating method and device of self-service terminal | |
| CN111132132A (en) | Traffic management method and device and terminal equipment | |
| CN105763616B (en) | Resource downloading method and device | |
| CN108520401B (en) | User list management method, device, platform and storage medium | |
| CN107707621B (en) | A kind of method and device for realizing intelligent buffer | |
| CN113067886A (en) | Database three-layer correlation auditing method and device, computer equipment and storage medium | |
| US7778660B2 (en) | Mobile communications terminal, information transmitting system and information receiving method | |
| CN112632083A (en) | Method, device and equipment for updating index data | |
| US20090037493A1 (en) | Method and device for updating an object with copyright attribute | |
| CN111314446B (en) | Resource updating method, device, server and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210928 |
|
| RJ01 | Rejection of invention patent application after publication |