EVENT AGGREGATION FOR BACKGROUND WORK EXECUTION
Systems, methods, and apparatus for separately managing foreground work and background work. In some embodiments, an operating system may identify at least one foreground component and at least one background component of a same application or different applications, and may manage the execution of...
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 | KISHAN, Arun U PULAPAKA, Hari PROBERT, David B GEFFLAUT, Alain F NEVES, Richard K SCHWARTZ, James A., Jr |
| description | Systems, methods, and apparatus for separately managing foreground work and background work. In some embodiments, an operating system may identify at least one foreground component and at least one background component of a same application or different applications, and may manage the execution of the components differently. For example, the operating system may receive a request that at least one background component of an application be executed in response to at least one event. In response to detecting an occurrence of the at least one event, the operating system may determine whether at least one first condition set by the application is satisfied and whether at least one second condition set by the operating system is satisfied, and may execute the at least one background component when it is determined that the at least one first and second conditions are satisfied following the occurrence of the at least one event. |
| format | Patent |
| fullrecord | <record><control><sourceid>epo_EVB</sourceid><recordid>TN_cdi_epo_espacenet_EP2751674B1</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>EP2751674B1</sourcerecordid><originalsourceid>FETCH-epo_espacenet_EP2751674B13</originalsourceid><addsrcrecordid>eNrjZNB3DXP1C1FwdHcPcnV3DPH091Nw8w9ScHJ09nYP8g_1c1EI9w_yVnCNcHUOBcnyMLCmJeYUp_JCaW4GBTfXEGcP3dSC_PjU4oLE5NS81JJ41wAjc1NDM3MTJ0NjIpQAAMq8Jcg</addsrcrecordid><sourcetype>Open Access Repository</sourcetype><iscdi>true</iscdi><recordtype>patent</recordtype></control><display><type>patent</type><title>EVENT AGGREGATION FOR BACKGROUND WORK EXECUTION</title><source>esp@cenet</source><creator>KISHAN, Arun U ; PULAPAKA, Hari ; PROBERT, David B ; GEFFLAUT, Alain F ; NEVES, Richard K ; SCHWARTZ, James A., Jr</creator><creatorcontrib>KISHAN, Arun U ; PULAPAKA, Hari ; PROBERT, David B ; GEFFLAUT, Alain F ; NEVES, Richard K ; SCHWARTZ, James A., Jr</creatorcontrib><description>Systems, methods, and apparatus for separately managing foreground work and background work. In some embodiments, an operating system may identify at least one foreground component and at least one background component of a same application or different applications, and may manage the execution of the components differently. For example, the operating system may receive a request that at least one background component of an application be executed in response to at least one event. In response to detecting an occurrence of the at least one event, the operating system may determine whether at least one first condition set by the application is satisfied and whether at least one second condition set by the operating system is satisfied, and may execute the at least one background component when it is determined that the at least one first and second conditions are satisfied following the occurrence of the at least one event.</description><language>eng ; fre ; ger</language><subject>CALCULATING ; COMPUTING ; COUNTING ; ELECTRIC DIGITAL DATA PROCESSING ; PHYSICS</subject><creationdate>2019</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=20190508&DB=EPODOC&CC=EP&NR=2751674B1$$EHTML$$P50$$Gepo$$Hfree_for_read</linktohtml><link.rule.ids>230,308,780,885,25564,76547</link.rule.ids><linktorsrc>$$Uhttps://worldwide.espacenet.com/publicationDetails/biblio?FT=D&date=20190508&DB=EPODOC&CC=EP&NR=2751674B1$$EView_record_in_European_Patent_Office$$FView_record_in_$$GEuropean_Patent_Office$$Hfree_for_read</linktorsrc></links><search><creatorcontrib>KISHAN, Arun U</creatorcontrib><creatorcontrib>PULAPAKA, Hari</creatorcontrib><creatorcontrib>PROBERT, David B</creatorcontrib><creatorcontrib>GEFFLAUT, Alain F</creatorcontrib><creatorcontrib>NEVES, Richard K</creatorcontrib><creatorcontrib>SCHWARTZ, James A., Jr</creatorcontrib><title>EVENT AGGREGATION FOR BACKGROUND WORK EXECUTION</title><description>Systems, methods, and apparatus for separately managing foreground work and background work. In some embodiments, an operating system may identify at least one foreground component and at least one background component of a same application or different applications, and may manage the execution of the components differently. For example, the operating system may receive a request that at least one background component of an application be executed in response to at least one event. In response to detecting an occurrence of the at least one event, the operating system may determine whether at least one first condition set by the application is satisfied and whether at least one second condition set by the operating system is satisfied, and may execute the at least one background component when it is determined that the at least one first and second conditions are satisfied following the occurrence of the at least one event.</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>2019</creationdate><recordtype>patent</recordtype><sourceid>EVB</sourceid><recordid>eNrjZNB3DXP1C1FwdHcPcnV3DPH091Nw8w9ScHJ09nYP8g_1c1EI9w_yVnCNcHUOBcnyMLCmJeYUp_JCaW4GBTfXEGcP3dSC_PjU4oLE5NS81JJ41wAjc1NDM3MTJ0NjIpQAAMq8Jcg</recordid><startdate>20190508</startdate><enddate>20190508</enddate><creator>KISHAN, Arun U</creator><creator>PULAPAKA, Hari</creator><creator>PROBERT, David B</creator><creator>GEFFLAUT, Alain F</creator><creator>NEVES, Richard K</creator><creator>SCHWARTZ, James A., Jr</creator><scope>EVB</scope></search><sort><creationdate>20190508</creationdate><title>EVENT AGGREGATION FOR BACKGROUND WORK EXECUTION</title><author>KISHAN, Arun U ; PULAPAKA, Hari ; PROBERT, David B ; GEFFLAUT, Alain F ; NEVES, Richard K ; SCHWARTZ, James A., Jr</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-epo_espacenet_EP2751674B13</frbrgroupid><rsrctype>patents</rsrctype><prefilter>patents</prefilter><language>eng ; fre ; ger</language><creationdate>2019</creationdate><topic>CALCULATING</topic><topic>COMPUTING</topic><topic>COUNTING</topic><topic>ELECTRIC DIGITAL DATA PROCESSING</topic><topic>PHYSICS</topic><toplevel>online_resources</toplevel><creatorcontrib>KISHAN, Arun U</creatorcontrib><creatorcontrib>PULAPAKA, Hari</creatorcontrib><creatorcontrib>PROBERT, David B</creatorcontrib><creatorcontrib>GEFFLAUT, Alain F</creatorcontrib><creatorcontrib>NEVES, Richard K</creatorcontrib><creatorcontrib>SCHWARTZ, James A., Jr</creatorcontrib><collection>esp@cenet</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>KISHAN, Arun U</au><au>PULAPAKA, Hari</au><au>PROBERT, David B</au><au>GEFFLAUT, Alain F</au><au>NEVES, Richard K</au><au>SCHWARTZ, James A., Jr</au><format>patent</format><genre>patent</genre><ristype>GEN</ristype><title>EVENT AGGREGATION FOR BACKGROUND WORK EXECUTION</title><date>2019-05-08</date><risdate>2019</risdate><abstract>Systems, methods, and apparatus for separately managing foreground work and background work. In some embodiments, an operating system may identify at least one foreground component and at least one background component of a same application or different applications, and may manage the execution of the components differently. For example, the operating system may receive a request that at least one background component of an application be executed in response to at least one event. In response to detecting an occurrence of the at least one event, the operating system may determine whether at least one first condition set by the application is satisfied and whether at least one second condition set by the operating system is satisfied, and may execute the at least one background component when it is determined that the at least one first and second conditions are satisfied following the occurrence of the at least one event.</abstract><oa>free_for_read</oa></addata></record> |
| fulltext | fulltext_linktorsrc |
| identifier | |
| ispartof | |
| issn | |
| language | eng ; fre ; ger |
| recordid | cdi_epo_espacenet_EP2751674B1 |
| source | esp@cenet |
| subjects | CALCULATING COMPUTING COUNTING ELECTRIC DIGITAL DATA PROCESSING PHYSICS |
| title | EVENT AGGREGATION FOR BACKGROUND WORK EXECUTION |
| url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2024-12-18T15%3A21%3A53IST&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=KISHAN,%20Arun%20U&rft.date=2019-05-08&rft_id=info:doi/&rft_dat=%3Cepo_EVB%3EEP2751674B1%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 |