LATENCY-BASED PLACEMENT OF CLOUD COMPUTE INSTANCES WITHIN COMMUNICATIONS SERVICE PROVIDER NETWORKS
Techniques for launching compute instances on cloud provider network substrate extensions deployed within communications service provider networks are described. A service of a cloud provider network receives a request to launch a compute instance from a customer, the request including a latency req...
Gespeichert in:
Hauptverfasser: | , , , , , |
---|---|
Format: | Patent |
Sprache: | eng ; fre ; ger |
Schlagworte: | |
Online-Zugang: | Volltext bestellen |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
container_end_page | |
---|---|
container_issue | |
container_start_page | |
container_title | |
container_volume | |
creator | PARULKAR, Ishwardutt DUNSMORE, Devlin Roarke GUPTA, Diwakar QUINN, Michael Phillip PROCK, Leslie Andrew ELISSAIOS, Georgios |
description | Techniques for launching compute instances on cloud provider network substrate extensions deployed within communications service provider networks are described. A service of a cloud provider network receives a request to launch a compute instance from a customer, the request including a latency requirement. A provider substrate extension is selected to host the compute instance from a plurality of provider substrate extensions of the cloud provider network based at least in part on the latency requirement. The plurality of plurality of provider substrate extensions are connected to a communications service provider network and controlled at least in part by the service of the cloud provider network via a connection through the communications service provider network. A message is sent to cause the selected provider substrate extension to launch the compute instance for the customer. |
format | Patent |
fullrecord | <record><control><sourceid>epo_EVB</sourceid><recordid>TN_cdi_epo_espacenet_EP4049139A1</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>EP4049139A1</sourcerecordid><originalsourceid>FETCH-epo_espacenet_EP4049139A13</originalsourceid><addsrcrecordid>eNqNysEKgkAQgGEvHaJ6h3kBIdGLx20ccUhnl91R6SQW2ylKsPcngh6g03_4_m1ybY2S4CU9mUAVuNYgdSQKtgZsbV8B2s71SsAS1AhSgJG1YflC1wujUbYSIJAfGAmctwNX5EFIR-vPYZ9s7vNjjYdfdwnUpNikcXlNcV3mW3zG90SuOBZllpcmy_9YPrqfNCg</addsrcrecordid><sourcetype>Open Access Repository</sourcetype><iscdi>true</iscdi><recordtype>patent</recordtype></control><display><type>patent</type><title>LATENCY-BASED PLACEMENT OF CLOUD COMPUTE INSTANCES WITHIN COMMUNICATIONS SERVICE PROVIDER NETWORKS</title><source>esp@cenet</source><creator>PARULKAR, Ishwardutt ; DUNSMORE, Devlin Roarke ; GUPTA, Diwakar ; QUINN, Michael Phillip ; PROCK, Leslie Andrew ; ELISSAIOS, Georgios</creator><creatorcontrib>PARULKAR, Ishwardutt ; DUNSMORE, Devlin Roarke ; GUPTA, Diwakar ; QUINN, Michael Phillip ; PROCK, Leslie Andrew ; ELISSAIOS, Georgios</creatorcontrib><description>Techniques for launching compute instances on cloud provider network substrate extensions deployed within communications service provider networks are described. A service of a cloud provider network receives a request to launch a compute instance from a customer, the request including a latency requirement. A provider substrate extension is selected to host the compute instance from a plurality of provider substrate extensions of the cloud provider network based at least in part on the latency requirement. The plurality of plurality of provider substrate extensions are connected to a communications service provider network and controlled at least in part by the service of the cloud provider network via a connection through the communications service provider network. A message is sent to cause the selected provider substrate extension to launch the compute instance for the customer.</description><language>eng ; fre ; ger</language><subject>CALCULATING ; COMPUTING ; COUNTING ; ELECTRIC DIGITAL DATA PROCESSING ; PHYSICS</subject><creationdate>2022</creationdate><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://worldwide.espacenet.com/publicationDetails/biblio?FT=D&date=20220831&DB=EPODOC&CC=EP&NR=4049139A1$$EHTML$$P50$$Gepo$$Hfree_for_read</linktohtml><link.rule.ids>230,308,776,881,25543,76293</link.rule.ids><linktorsrc>$$Uhttps://worldwide.espacenet.com/publicationDetails/biblio?FT=D&date=20220831&DB=EPODOC&CC=EP&NR=4049139A1$$EView_record_in_European_Patent_Office$$FView_record_in_$$GEuropean_Patent_Office$$Hfree_for_read</linktorsrc></links><search><creatorcontrib>PARULKAR, Ishwardutt</creatorcontrib><creatorcontrib>DUNSMORE, Devlin Roarke</creatorcontrib><creatorcontrib>GUPTA, Diwakar</creatorcontrib><creatorcontrib>QUINN, Michael Phillip</creatorcontrib><creatorcontrib>PROCK, Leslie Andrew</creatorcontrib><creatorcontrib>ELISSAIOS, Georgios</creatorcontrib><title>LATENCY-BASED PLACEMENT OF CLOUD COMPUTE INSTANCES WITHIN COMMUNICATIONS SERVICE PROVIDER NETWORKS</title><description>Techniques for launching compute instances on cloud provider network substrate extensions deployed within communications service provider networks are described. A service of a cloud provider network receives a request to launch a compute instance from a customer, the request including a latency requirement. A provider substrate extension is selected to host the compute instance from a plurality of provider substrate extensions of the cloud provider network based at least in part on the latency requirement. The plurality of plurality of provider substrate extensions are connected to a communications service provider network and controlled at least in part by the service of the cloud provider network via a connection through the communications service provider network. A message is sent to cause the selected provider substrate extension to launch the compute instance for the customer.</description><subject>CALCULATING</subject><subject>COMPUTING</subject><subject>COUNTING</subject><subject>ELECTRIC DIGITAL DATA PROCESSING</subject><subject>PHYSICS</subject><fulltext>true</fulltext><rsrctype>patent</rsrctype><creationdate>2022</creationdate><recordtype>patent</recordtype><sourceid>EVB</sourceid><recordid>eNqNysEKgkAQgGEvHaJ6h3kBIdGLx20ccUhnl91R6SQW2ylKsPcngh6g03_4_m1ybY2S4CU9mUAVuNYgdSQKtgZsbV8B2s71SsAS1AhSgJG1YflC1wujUbYSIJAfGAmctwNX5EFIR-vPYZ9s7vNjjYdfdwnUpNikcXlNcV3mW3zG90SuOBZllpcmy_9YPrqfNCg</recordid><startdate>20220831</startdate><enddate>20220831</enddate><creator>PARULKAR, Ishwardutt</creator><creator>DUNSMORE, Devlin Roarke</creator><creator>GUPTA, Diwakar</creator><creator>QUINN, Michael Phillip</creator><creator>PROCK, Leslie Andrew</creator><creator>ELISSAIOS, Georgios</creator><scope>EVB</scope></search><sort><creationdate>20220831</creationdate><title>LATENCY-BASED PLACEMENT OF CLOUD COMPUTE INSTANCES WITHIN COMMUNICATIONS SERVICE PROVIDER NETWORKS</title><author>PARULKAR, Ishwardutt ; DUNSMORE, Devlin Roarke ; GUPTA, Diwakar ; QUINN, Michael Phillip ; PROCK, Leslie Andrew ; ELISSAIOS, Georgios</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-epo_espacenet_EP4049139A13</frbrgroupid><rsrctype>patents</rsrctype><prefilter>patents</prefilter><language>eng ; fre ; ger</language><creationdate>2022</creationdate><topic>CALCULATING</topic><topic>COMPUTING</topic><topic>COUNTING</topic><topic>ELECTRIC DIGITAL DATA PROCESSING</topic><topic>PHYSICS</topic><toplevel>online_resources</toplevel><creatorcontrib>PARULKAR, Ishwardutt</creatorcontrib><creatorcontrib>DUNSMORE, Devlin Roarke</creatorcontrib><creatorcontrib>GUPTA, Diwakar</creatorcontrib><creatorcontrib>QUINN, Michael Phillip</creatorcontrib><creatorcontrib>PROCK, Leslie Andrew</creatorcontrib><creatorcontrib>ELISSAIOS, Georgios</creatorcontrib><collection>esp@cenet</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>PARULKAR, Ishwardutt</au><au>DUNSMORE, Devlin Roarke</au><au>GUPTA, Diwakar</au><au>QUINN, Michael Phillip</au><au>PROCK, Leslie Andrew</au><au>ELISSAIOS, Georgios</au><format>patent</format><genre>patent</genre><ristype>GEN</ristype><title>LATENCY-BASED PLACEMENT OF CLOUD COMPUTE INSTANCES WITHIN COMMUNICATIONS SERVICE PROVIDER NETWORKS</title><date>2022-08-31</date><risdate>2022</risdate><abstract>Techniques for launching compute instances on cloud provider network substrate extensions deployed within communications service provider networks are described. A service of a cloud provider network receives a request to launch a compute instance from a customer, the request including a latency requirement. A provider substrate extension is selected to host the compute instance from a plurality of provider substrate extensions of the cloud provider network based at least in part on the latency requirement. The plurality of plurality of provider substrate extensions are connected to a communications service provider network and controlled at least in part by the service of the cloud provider network via a connection through the communications service provider network. A message is sent to cause the selected provider substrate extension to launch the compute instance for the customer.</abstract><oa>free_for_read</oa></addata></record> |
fulltext | fulltext_linktorsrc |
identifier | |
ispartof | |
issn | |
language | eng ; fre ; ger |
recordid | cdi_epo_espacenet_EP4049139A1 |
source | esp@cenet |
subjects | CALCULATING COMPUTING COUNTING ELECTRIC DIGITAL DATA PROCESSING PHYSICS |
title | LATENCY-BASED PLACEMENT OF CLOUD COMPUTE INSTANCES WITHIN COMMUNICATIONS SERVICE PROVIDER NETWORKS |
url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-23T13%3A37%3A44IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-epo_EVB&rft_val_fmt=info:ofi/fmt:kev:mtx:patent&rft.genre=patent&rft.au=PARULKAR,%20Ishwardutt&rft.date=2022-08-31&rft_id=info:doi/&rft_dat=%3Cepo_EVB%3EEP4049139A1%3C/epo_EVB%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_id=info:pmid/&rfr_iscdi=true |