Application service configuration system
US-2017104629-A1 · Apr 13, 2017 · US
US9906453B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9906453-B2 |
| Application number | US-201514979757-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 28, 2015 |
| Priority date | Nov 13, 2015 |
| Publication date | Feb 27, 2018 |
| Grant date | Feb 27, 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.
An escalated expedited forwarding system, for modifying per hop behavior of one or more Expedited Forwarding (EF) packets for a session in a communication network, the system comprising: a memory; a processor coupled to the memory storing processor executable instructions which when executed by the processor causes the processor to perform operations comprising: determining, by an escalated expedited forwarding system, at least one of latency, jitter and average jitter associated with the one or more EF packets for the session; marking, by the escalated expedited forwarding system, one or more EF packets based on the at least one of latency, jitter and average jitter; and modifying, by the escalated expedited forwarding system, the per hop behavior of the one or more marked EF packets.
Opening claim text (preview).
What is claimed is: 1. A method for modifying per hop behavior of one or more Expedited Forwarding (EF) packets for a session in a communication network, the method comprises: determining, by an escalated expedited forwarding system, at least one of latency, jitter and average jitter associated with the one or more EF packets for the session; marking, by the escalated expedited forwarding system, one or more EF packets with Escalated Expedited Forwarding (EEF) marking in response to determining EF packet congestion based on the determined at least one of latency, jitter and average jitter, wherein the EEF marked packets are EF packets that are delayed during transmission based on the determined EF packet congestion; and modifying, by the escalated expedited forwarding system, the per hop behavior of the one or more marked EF packets in response to the EEF marking by: sequencing the one or more EEF marked packets of the session to provide precedence to the one or more EEF marked packets over all non-marked one or more packets during transmission of the one or more marked EF packets in the communication network; and erasing the one or more EEF marked packets, if an ingress queue for the one or more EEF marked packets exceed a pre-defined value, wherein the modification changes the transmission behavior of the one or more marked EF packets. 2. The method of claim 1 wherein determining at least one of latency, jitter and average jitter associated with the one or more EF packets is based on monitoring of round trip time (RTT) associated with the one or more EF packets for the session for a preconfigured time interval. 3. The method of claim 1 , wherein latency is determined based on comparison of average of the monitored RTT and a preconfigured latency threshold. 4. The method of claim 1 , wherein jitter is determined based on comparison of difference of maximum monitored RTT and minimum monitored RTT with a preconfigured jitter threshold. 5. The method of claim 1 , wherein the average jitter is determined based on comparison of difference between current RTT average and previous RTT average with a preconfigured average-jitter threshold. 6. The method of claim 1 , wherein marking the one or more EF packets further comprises changing an IP header type of service of the one or more EF packets. 7. The method of claim 6 , wherein narking the one or more Expedited Forwarding packets further comprises changing a six-bit Differentiated Services Code Point field of the IP header of the one or more Expedited Forwarding packets from an Expedited Forwarding marking to the Escalated Expedited Forwarding marking, and wherein the method further comprises changing the six-bit Differentiated Services Code Point field of the IP header of the one or more marked Expedited Forwarding packets from the Escalated Expedited Forwarding marking to the Expedited Forwarding marking once the Expedited Forwarding packet congestion becomes absent. 8. An escalated expedited forwarding system, for modifying per hop behavior of one or more Expedited Forwarding (EF) packets for a session in a communication network, the system comprising: a memory; a processor coupled to the memory storing processor executable instructions which when executed by the processor causes the processor to perform operations comprising: determining at least one of latency, jitter and average jitter associated with the one or more EF packets for the session; marking one or more EF packets with Escalated Expedited Forwarding (EEF) marking in response to detecting EF packet congestion based on the determined at least one of latency, jitter and average jitter, wherein the EEF marked packets are EF packets that are delayed during transmission based on the determined EF packet congestion; and modifying the per hop behavior of the one or more EF packets in response to the EEF marking by: sequencing the one or more EEF marked packets of the session to provide precedence to the one or more EEF marked packets over all non-marked one or more packets during transmission of the one or more marked EF packets in the communication network; and erasing the one or more EEF marked packets, if an ingress queue for the one or more EEF marked packets exceed a pre-defined value, wherein the modification changes the transmission behavior of the one or more marked EF packets. 9. The system of claim 8 , wherein the at least one of latency, jitter and average jitter associated with the one or more EF packets is determined based on monitoring of round trip time (RTT) associated with the one or more EF packets for the session for a preconfigured time interval. 10. The system of claim 8 , wherein latency is determined based on comparison of the monitored RTT-average and a preconfigured latency threshold RTT. 11. The system of claim 8 , wherein jitter is determined based on comparison of difference of maximum monitored RTT and minimum monitored RTT with a preconfigured jitter threshold. 12. The system of claim 8 , wherein the average jitter is determined based on comparison of difference between current RTT average and previous RTT average with a preconfigured average jitter threshold. 13. The system of claim 8 , wherein the one or more EF packets are marked by changing an IP header type of service of the one or more EF packets. 14. The system of claim 8 , wherein the one or more Expedited Forwarding packets are marked by changing a six-bit Differentiated Services Code Point field of the IP header of the one or more Expedited Forwarding packets from an Expedited Forwarding marking to the Escalated Expedited Forwarding marking, and wherein the executable instructions, when executed by the processor, further cause the processor to change the six-bit Differentiated Services Code Point field of the IP header of the one or more marked Expedited Forwarding packets from the Escalated Expedited Forwarding marking to the Expedited Forwarding marking once the Expedited Forwarding packet congestion becomes absent.
Round trip delays · CPC title
Interaction among intermediate nodes, e.g. hop by hop · CPC title
ensuring sequence integrity, e.g. using sequence numbers · CPC title
by discarding or delaying data units, e.g. packets or frames · CPC title
in combination with information about buffer occupancy at either end or at transit nodes · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.