Multi-entity resource, security, and service management in edge computing deployments
US-2021144517-A1 · May 13, 2021 · US
US12556597B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12556597-B2 |
| Application number | US-202318393236-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 21, 2023 |
| Priority date | Sep 8, 2021 |
| Publication date | Feb 17, 2026 |
| Grant date | Feb 17, 2026 |
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.
Methods, apparatus, systems, and articles of manufacture are disclosed to improve webservers using dynamic load balancers. An example method includes identifying a first and second data object type associated with media and with first and second data objects of the media. The example method also includes enqueuing first and second event data associated with the first and second data object in a first and second queue in first circuitry in a die of programmable circuitry. The example method further includes dequeuing the first and second event data into a third and fourth queue associated with a first and second core of the programmable circuitry, the first circuitry separate from the first core and the second core. The example method additionally includes causing the first and second core to execute a first and second computing operation based on the first and second event data in the third and fourth queues.
Opening claim text (preview).
What is claimed is: 1 . A method comprising: selecting first circuitry of programmable circuitry based on a proximity order of the first circuitry to at least one of a first core or a second core of the programmable circuitry, the first circuitry separate from the first core and the second core; enqueueing first event data associated with a first data object in a first queue in the first circuitry and enqueueing second event data associated with a second data object in a second queue in the first circuitry, the first data object and the second data object associated with a request for media; dequeuing the first event data into a third queue and dequeuing the second event data into a fourth queue, the third queue associated with the first core, the fourth queue associated with the second core; and causing the first core to execute a first computing operation based on the first event data in the third queue and causing the second core to execute a second computing operation based on the second event data in the fourth queue. 2 . The method of claim 1 , wherein the media is associated with a Hypertext Transfer Protocol request, the programmable circuitry includes a third core, and including extracting, with the third core, at least one of a data header or a data payload from the Hypertext Transfer Protocol request. 3 . The method of claim 1 , wherein the programmable circuitry includes a third core, the first data object is a video object and the second data object is an audio object, the media includes a text object, and including: enqueueing third event data associated with the text object in a fifth queue in the first circuitry; dequeuing the third event data into a sixth queue associated with the third core; and causing the third core to execute a third computing operation based on the third event data in the sixth queue. 4 . The method of claim 1 , wherein the programmable circuitry includes a third core, and including selecting the first circuitry with the third core. 5 . The method of claim 1 , wherein the programmable circuitry includes a third core and second circuitry, the first circuitry is on a first die of the programmable circuitry and the second circuitry is on a second die of the programmable circuitry, and including: querying, with the third core, the second circuitry for availability to enqueue the first event data and the second event data; and selecting, with the third core, the first circuitry to enqueue the first event data and the second event data after a determination that the second circuitry is unavailable based on a response from the second circuitry to the query. 6 . The method of claim 1 , wherein the first circuitry is on a first socket of the programmable circuitry, the first core and the second core are on the first socket, the programmable circuitry includes a third core and second circuitry, the third core and the second circuitry are on a second socket of the programmable circuitry, the first socket is different from the second socket, and including: querying, with the third core, the second circuitry for availability to enqueue the first event data and the second event data; and selecting, with the third core, the first circuitry to enqueue the first event data and the second event data after a determination that the second circuitry is unavailable based on a response from the second circuitry to the query. 7 . An apparatus comprising: interface circuitry; instructions; and programmable circuitry to operate based on the instructions to: select first circuitry of the programmable circuitry based on a proximity order of the first circuitry to at least one of a first core or a second core of the programmable circuitry, the first circuitry separate from the first core and the second core; enqueue first event data associated with a first data object in a first queue in the first circuitry and enqueue second event data associated with a second data object in a second queue in the first circuitry, the first data object and the second data object associated with a request for media; dequeue the first event data into a third queue and dequeue the second event data into a fourth queue, the third queue associated with the first core, the fourth queue associated with the second core; and cause the first core to execute a first computing operation based on the first event data in the third queue and cause the second core to execute a second computing operation based on the second event data in the fourth queue. 8 . The apparatus of claim 7 , wherein the media is associated with a Hypertext Transfer Protocol request, the programmable circuitry includes a third core to extract at least one of a data header or a data payload from the Hypertext Transfer Protocol request. 9 . The apparatus of claim 7 , wherein the programmable circuitry includes a third core, the first data object is a video object and the second data object is an audio object, the media includes a text object, and the programmable circuitry is to: enqueue third event data associated with the text object in a fifth queue in the first circuitry; dequeue the third event data into a sixth queue associated with the third core; and cause the third core to execute a third computing operation based on the third event data in the sixth queue. 10 . The apparatus of claim 7 , wherein the programmable circuitry includes a third core to select the first circuitry. 11 . The apparatus of claim 7 , wherein the programmable circuitry includes a third core and second circuitry, the first circuitry is on a first die of the programmable circuitry and the second circuitry is on a second die of the programmable circuitry, and the programmable circuitry is to: query, with the third core, the second circuitry for availability to enqueue the first event data and the second event data; and select, with the third core, the first circuitry to enqueue the first event data and the second event data after a determination that the second circuitry is unavailable based on a response from the second circuitry to the query. 12 . The apparatus of claim 7 , wherein the first circuitry is on a first socket of the programmable circuitry, the first core and the second core are on the first socket, the programmable circuitry includes a third core and second circuitry, the third core and the second circuitry are on a second socket of the programmable circuitry, the first socket is different from the second socket, and the programmable circuitry is to: query, with the third core, the second circuitry for availability to enqueue the first event data and the second event data; and select, with the third core, the first circuitry to enqueue the first event data and the second event data after a determination that the second circuitry is unavailable based on a response from the second circuitry to the query. 13 . The apparatus of claim 7 , wherein the programmable circuitry is to determine that the media is an elephant flow based on a determination that the media is associated with a single session and the single session is associated with a network connection that has run for a time period that satisfies a threshold. 14 . At least one non-transitory computer readable medium comprising instructions to cause programmable circuitry to at least: select first circuitry of the programmable circuitry based on a proximity order of the first circuitry to at least one of a first core or a second core of the programmable circuitry, the first circuitry separate from the first core and the second core; enqueue first event data associated with a first data
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70) · CPC title
Message passing systems or structures, e.g. queues · CPC title
Queue · CPC title
Individual queue per QOS, rate or priority · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.