Bundling data transfers and employing tail optimization protocol to manage cellular radio resource utilization
US-9220066-B2 · Dec 22, 2015 · US
US10135939B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10135939-B2 |
| Application number | US-201514795326-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 9, 2015 |
| Priority date | Jan 14, 2013 |
| Publication date | Nov 20, 2018 |
| Grant date | Nov 20, 2018 |
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 and apparatus for sending a delivery notification of a network application-related product are provided. The method includes: selecting a delivery executing server in advance from multiple delivery servers of an application; acquiring quality of service information of the delivery executing server of the application; judging, according to a predefined judging rule, whether the quality of service information meets a requirement; and if the requirement is met, retaining the delivery executing server unchanged; otherwise, setting another delivery server of the application as a delivery executing server; and sending a delivery notification to a current delivery executing server of the application upon detecting the delivery notification of the application to be sent.
Opening claim text (preview).
What is claimed is: 1. A method for sending a delivery notification of a network application-related product, wherein a first delivery server is selected in advance from multiple delivery servers of an application as a delivery executing server, and the method comprises: acquiring quality of service information of the first delivery server of the application; judging, according to a predefined judging rule, whether the quality of service information meets a requirement; and if the requirement is met, retaining the first delivery server as a current delivery executing server; otherwise, setting a second delivery server of the application as the current delivery executing server to replace the first delivery server thereby reducing data, error rate in a delivery process; and sending a delivery notification to the current delivery executing server of the application upon detecting the delivery notification of the application to be sent; wherein the quality of service information comprises at least one of a delivery failure rate, a delivery delay rate, and a jitter rate of the delivery failure rate; the judging rule comprises: if the delivery failure rate is greater than a predefined failure rate threshold, the delivery delay rate is greater than a predefined delay rate threshold, and the jitter rate of the delivery failure rate is greater than a predefined jitter rate threshold, judging that the quality of service information does not meet the requirement; otherwise, judging that the quality of service information meets the requirement. 2. The method according to claim 1 , wherein the acquiring quality of service information of the first delivery server of the application comprises: acquiring the quality of service information of the first delivery server of the application according to a predefined first detection period. 3. The method according to claim 1 , wherein if the quality of service information does not meet the requirement, after the setting a second delivery server of the application as the current delivery executing server to replace the first delivery server, the method further comprises: locking the first delivery server whose quality of service information does not meet the requirement for predefined locking duration T. 4. The method according to claim 3 , further comprising: judging, when duration within which the first delivery server is locked reaches T, whether the first delivery server meets a predefined switchback condition; and if the switchback condition is met, setting the first delivery server as the current delivery executing server of the to replace the second delivery server application; otherwise, retaining the second delivery server as the current delivery executing server. 5. The method according to claim 4 , wherein the judging, when duration within which the first delivery server is locked reaches T, whether the first delivery server meets a predefined switchback condition comprises: after the duration within which the first delivery server is locked reaches T, sending a predefined number of delivery notifications of the application to the first delivery server for processing; and if a delivery failure rate for processing, by the first delivery server, the predefined number of delivery notifications of the application is not greater than a predefined first failure rate threshold, judging that the first delivery server meets the predefined switchback condition; otherwise, judging that the delivery server does not meet the predefined switchback condition. 6. The method according to claim 4 , wherein the judging, when duration within which the first delivery server is locked reaches T, whether the first delivery server meets a predefined switchback condition comprises: after the duration within which the first delivery server is locked reaches T, sending delivery notifications of the application to the first delivery server for processing within a predetermined duration; and if a delivery failure rate for processing, by the first delivery server, the delivery notifications of the application within the predetermined duration is not greater than a predefined second failure rate threshold, judging that the first delivery server meets the predefined switchback condition; otherwise, judging that the first delivery server does not meet the predefined switchback condition. 7. The method according to claim 1 , further comprising: selecting an executing proxy server in advance from proxy servers; acquiring, according to a predefined second detection period, a network connection failure rate of the executing proxy server; judging whether the network connection failure rate is greater than a predefined network connection failure rate threshold; and if the network connection failure rate is greater than the predefined network connection failure rate threshold, setting another proxy server as an executing proxy server; otherwise, retaining the executing proxy server unchanged; and the sending a delivery notification to the current delivery executing server of the application upon detecting the delivery notification of the application to be sent comprises: sending, upon detecting the delivery notification of the application to be sent, the delivery notification to the current delivery executing server of the application by using a current executing proxy server. 8. An apparatus for sending a delivery notification of a network application-related product, comprising: one or more processors; and a non-transitory computer-readable storage medium storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: selecting a first delivery server in advance from multiple delivery servers of an application as a delivery executing server; acquiring quality of service information of the first delivery server of the application; judging, according to a predefined judging rule, whether the quality of service information meets a requirement; and if the requirement is met, retaining the first delivery server as a current delivery executing server unchanged; otherwise, setting a second delivery server of the application as the current delivery executing server thereby reducing data error rate in a delivery process; and sending a delivery notification to the current delivery executing server of the application upon detecting the delivery notification of the application to be sent; wherein the quality of service information comprises at least one of a delivery failure rate, a delivery delay rate, and a jitter rate of the delivery failure rate; the judging rule comprises: if the delivery failure rate is greater than a predefined failure rate threshold, the delivery delay rate is greater than a predefined delay rate threshold, and the jitter rate of the, delivery failure rate is greater than a predefined jitter rate threshold, judging that the quality of service information does not meet the requirement; otherwise, judging that the quality of service information meets the requirement. 9. The apparatus according to claim 8 , wherein the acquiring quality of service information of the first delivery server of the application comprises acquiring the quality of service information of the first delivery server of the application according to a predefined first detection period. 10. The apparatus according to claim 8 , wherein the operations further comprise: after setting a second delivery server of the application as the current delivery executing server to replace the first delivery server, locking the first delivery server whose quality of service information does not meet the requirement for predefined locking duration T.
Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF] · CPC title
Jitter · CPC title
Provision for limiting connection, or expenditure · CPC title
by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade · CPC title
Low balance or limit reached · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.