Network service plan design
US-9858559-B2 · Jan 2, 2018 · US
US10306014B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10306014-B2 |
| Application number | US-201615376153-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 12, 2016 |
| Priority date | Apr 17, 2015 |
| Publication date | May 28, 2019 |
| Grant date | May 28, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method for controlling quality of service, including receiving an application programming interface (API) call request that a user terminal is triggered to send when an application (APP) is being used, where the API call request carries a user identifier of the APP and an identifier of the APP, acquiring a quality of service control policy of the APP according to the identifier of the APP and the user identifier of the APP, and controlling, according to the quality of service control policy of the APP, quality of service of a user indicated by the user identifier. Hence, quality of service control can be provided for an APP that registers with an API management device, which improves the APP development efficiency.
Opening claim text (preview).
What is claimed is: 1. A method for controlling quality of service, wherein the method is applied to an application programming interface (API) management device that provides an open API for an application (APP), and wherein the method comprises: receiving a registration request of the APP; receiving a first search indication identifier and a correspondence between a subscriber category of the APP and a quality of service control policy of the APP, wherein the first search indication identifier is used to indicate a necessity of searching an application server for a correspondence between a user identifier of the APP and the subscriber category of the APP; registering the APP according to the registration request; storing, in the API management device, the first search indication identifier and the correspondence between the subscriber category of the APP and the quality of service control policy of the APP; receiving an API call request that a user terminal is triggered to send when the APP is being used, wherein the API call request carries the user identifier of the APP and an identifier of the APP; acquiring the quality of service control policy of the APP according to the identifier of the APP and the user identifier of the APP by: acquiring, according to the identifier of the APP and the user identifier of the APP, the subscriber category that is of the APP and corresponding to the user identifier of the APP; and acquiring, according to the subscriber category of the APP, the quality of service control policy that is of the APP and corresponding to the subscriber category of the APP; and controlling, according to the quality of service control policy of the APP, quality of service of a user indicated by the user identifier. 2. The method of claim 1 , wherein before receiving the API call request, the method further comprises: receiving a correspondence between the user identifier of the APP and the subscriber category of the APP and a correspondence between the subscriber category of the APP and the quality of service control policy of the APP; and storing, in the API management device, the correspondence between the user identifier of the APP and the subscriber category of the APP and the correspondence between the subscriber category of the APP and the quality of service control policy of the APP. 3. The method of claim 2 , wherein acquiring the subscriber category of the APP comprises: acquiring, from cache data, the subscriber category that is of the APP and corresponding to the user identifier of the APP when the cache data of the correspondence between the user identifier of the APP and the subscriber category of the APP exists in a cache area of the API management device; and acquiring, from the correspondence that is between the user identifier of the APP and the subscriber category of the APP and already stored in a non-cache area, the subscriber category that is of the APP and corresponding to the user identifier of the APP when the cache data of the correspondence between the user identifier of the APP and the subscriber category of the APP does not exist in the cache area of the API management device, and wherein acquiring the quality of service control policy of the APP comprises: acquiring, from the cache area, the quality of service control policy that is of the APP and corresponding to the subscriber category of the APP when the subscriber category of the APP is acquired from the cache area; and acquiring, from the non-cache area, the quality of service control policy that is of the APP and corresponding to the subscriber category of the APP when the subscriber category of the APP is acquired from the non-cache area. 4. The method of claim 1 , wherein acquiring the subscriber category of the APP comprises: acquiring, from cache data, the subscriber category that is of the APP and corresponding to the user identifier of the APP when the cache data of the correspondence between the user identifier of the APP and the subscriber category of the APP exists in a cache area of the API management device; sending a search request to the application server according to the first search indication identifier when the cache data of the correspondence between the user identifier of the APP and the subscriber category of the APP does not exist in the cache area of the API management device, wherein the search request carries the user identifier of the APP, and wherein the user identifier of the APP is used by the application server to search for the subscriber category that is of the APP and corresponding to the user identifier of the APP; and receiving a search response message sent by the application server, wherein the search response message carries the subscriber category of the APP, and wherein acquiring the quality of service control policy of the APP comprises: acquiring, from the cache area, the quality of service control policy that is of the APP and corresponding to the subscriber category of the APP when the subscriber category of the APP is acquired from the cache area; and acquiring, from a non-cache area, the quality of service control policy that is of the APP and corresponding to the subscriber category of the APP when the subscriber category of the APP is acquired from the application server. 5. The method of claim 1 , wherein before receiving the API call request, the method further comprises: receiving a second search indication identifier and a correspondence between the user identifier of the APP and the subscriber category of the APP, wherein the second search indication identifier is used to indicate a necessity of searching an application server for a correspondence between the subscriber category of the APP and the quality of service control policy of the APP; and storing, in the API management device, the second search indication identifier and the correspondence between the user identifier of the APP and the subscriber category of the APP. 6. The method of claim 5 , wherein acquiring the subscriber category of the APP comprises: acquiring, from cache data, the subscriber category that is of the APP and corresponding to the user identifier of the APP when the cache data of the correspondence between the user identifier of the APP and the subscriber category of the APP exists in a cache area of the API management device; and acquiring, from the correspondence that is between the user identifier of the APP and the subscriber category of the APP and already stored in a non-cache area, the subscriber category that is of the APP and corresponding to the user identifier of the APP when cache data of the correspondence between the user identifier of the APP and the subscriber category of the APP does not exist in the cache area of the API management device, and wherein acquiring the quality of service control policy of the APP comprises: acquiring, from the cache area, the quality of service control policy that is of the APP and corresponding to the subscriber category of the APP when the subscriber category of the APP is acquired from the cache area; sending a search request to the application server according to the second search indication identifier when the subscriber category of the APP is acquired from the non-cache area, wherein the search request carries the subscriber category of the APP, and wherein the subscriber category of the APP is used by the application server to search for the quality of service control policy that is of the APP and corresponding to the subscriber category of the APP; and receiving a search response message sent by the application server, wherein the search response message carries the quality of service control policy of the APP. 7. The method of claim 1 , wherein before receiv
Responding to QoS · CPC title
Electricity · mapped topic
related to network traffic · CPC title
Electricity · mapped topic
Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.