Failure mode identification and reporting
When a software component is starting (305), such as but not limited to a task or a subtask, the component pushes (310) its identification (ID) onto a stack. The component then executes (315) its other instructions. If the component completes its instructions so that it can terminate normally (320),...
Gespeichert in:
| Hauptverfasser: | , , , , , , , , |
|---|---|
| Format: | Patent |
| Sprache: | eng |
| 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 | SEVILMIS TARKAN AGARWAL JANAK MADHUSUDAN KAPADIA ARSHISH CYRUS SHAH HARDIK JOSE TITTU LUKIYANOV MAXIM IRIMESCU GHEORGHITA CLARK STEPHEN JOHN LINGANNAPETA SREEKANTH |
| description | When a software component is starting (305), such as but not limited to a task or a subtask, the component pushes (310) its identification (ID) onto a stack. The component then executes (315) its other instructions. If the component completes its instructions so that it can terminate normally (320), then it pops (325) the stack, which removes its ID from the stack. If the component fails, such as by not being able to complete its instructions, then it will not be able to pop the stack so its ID will remain in the stack. Another software process can then read the IDs in the stack to identify (330) which components have failed and can automatically take a specified action (335), such as by sending an email message to, sending a text message to, or calling by telephone, a person or persons responsible for that software component. |
| format | Patent |
| fullrecord | <record><control><sourceid>epo_EVB</sourceid><recordid>TN_cdi_epo_espacenet_US9104561B2</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>US9104561B2</sourcerecordid><originalsourceid>FETCH-epo_espacenet_US9104561B23</originalsourceid><addsrcrecordid>eNrjZNB0S8zMKS1KVcjNT0lVyExJzSvJTMtMTizJzM9TSMxLUShKLcgvKsnMS-dhYE1LzClO5YXS3AwKbq4hzh66QAXxqcUFicmpeakl8aHBloYGJqZmhk5GxkQoAQDFliia</addsrcrecordid><sourcetype>Open Access Repository</sourcetype><iscdi>true</iscdi><recordtype>patent</recordtype></control><display><type>patent</type><title>Failure mode identification and reporting</title><source>esp@cenet</source><creator>SEVILMIS TARKAN ; AGARWAL JANAK MADHUSUDAN ; KAPADIA ARSHISH CYRUS ; SHAH HARDIK ; JOSE TITTU ; LUKIYANOV MAXIM ; IRIMESCU GHEORGHITA ; CLARK STEPHEN JOHN ; LINGANNAPETA SREEKANTH</creator><creatorcontrib>SEVILMIS TARKAN ; AGARWAL JANAK MADHUSUDAN ; KAPADIA ARSHISH CYRUS ; SHAH HARDIK ; JOSE TITTU ; LUKIYANOV MAXIM ; IRIMESCU GHEORGHITA ; CLARK STEPHEN JOHN ; LINGANNAPETA SREEKANTH</creatorcontrib><description>When a software component is starting (305), such as but not limited to a task or a subtask, the component pushes (310) its identification (ID) onto a stack. The component then executes (315) its other instructions. If the component completes its instructions so that it can terminate normally (320), then it pops (325) the stack, which removes its ID from the stack. If the component fails, such as by not being able to complete its instructions, then it will not be able to pop the stack so its ID will remain in the stack. Another software process can then read the IDs in the stack to identify (330) which components have failed and can automatically take a specified action (335), such as by sending an email message to, sending a text message to, or calling by telephone, a person or persons responsible for that software component.</description><language>eng</language><subject>CALCULATING ; COMPUTING ; COUNTING ; ELECTRIC DIGITAL DATA PROCESSING ; PHYSICS</subject><creationdate>2015</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=20150811&DB=EPODOC&CC=US&NR=9104561B2$$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=20150811&DB=EPODOC&CC=US&NR=9104561B2$$EView_record_in_European_Patent_Office$$FView_record_in_$$GEuropean_Patent_Office$$Hfree_for_read</linktorsrc></links><search><creatorcontrib>SEVILMIS TARKAN</creatorcontrib><creatorcontrib>AGARWAL JANAK MADHUSUDAN</creatorcontrib><creatorcontrib>KAPADIA ARSHISH CYRUS</creatorcontrib><creatorcontrib>SHAH HARDIK</creatorcontrib><creatorcontrib>JOSE TITTU</creatorcontrib><creatorcontrib>LUKIYANOV MAXIM</creatorcontrib><creatorcontrib>IRIMESCU GHEORGHITA</creatorcontrib><creatorcontrib>CLARK STEPHEN JOHN</creatorcontrib><creatorcontrib>LINGANNAPETA SREEKANTH</creatorcontrib><title>Failure mode identification and reporting</title><description>When a software component is starting (305), such as but not limited to a task or a subtask, the component pushes (310) its identification (ID) onto a stack. The component then executes (315) its other instructions. If the component completes its instructions so that it can terminate normally (320), then it pops (325) the stack, which removes its ID from the stack. If the component fails, such as by not being able to complete its instructions, then it will not be able to pop the stack so its ID will remain in the stack. Another software process can then read the IDs in the stack to identify (330) which components have failed and can automatically take a specified action (335), such as by sending an email message to, sending a text message to, or calling by telephone, a person or persons responsible for that software component.</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>2015</creationdate><recordtype>patent</recordtype><sourceid>EVB</sourceid><recordid>eNrjZNB0S8zMKS1KVcjNT0lVyExJzSvJTMtMTizJzM9TSMxLUShKLcgvKsnMS-dhYE1LzClO5YXS3AwKbq4hzh66QAXxqcUFicmpeakl8aHBloYGJqZmhk5GxkQoAQDFliia</recordid><startdate>20150811</startdate><enddate>20150811</enddate><creator>SEVILMIS TARKAN</creator><creator>AGARWAL JANAK MADHUSUDAN</creator><creator>KAPADIA ARSHISH CYRUS</creator><creator>SHAH HARDIK</creator><creator>JOSE TITTU</creator><creator>LUKIYANOV MAXIM</creator><creator>IRIMESCU GHEORGHITA</creator><creator>CLARK STEPHEN JOHN</creator><creator>LINGANNAPETA SREEKANTH</creator><scope>EVB</scope></search><sort><creationdate>20150811</creationdate><title>Failure mode identification and reporting</title><author>SEVILMIS TARKAN ; AGARWAL JANAK MADHUSUDAN ; KAPADIA ARSHISH CYRUS ; SHAH HARDIK ; JOSE TITTU ; LUKIYANOV MAXIM ; IRIMESCU GHEORGHITA ; CLARK STEPHEN JOHN ; LINGANNAPETA SREEKANTH</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-epo_espacenet_US9104561B23</frbrgroupid><rsrctype>patents</rsrctype><prefilter>patents</prefilter><language>eng</language><creationdate>2015</creationdate><topic>CALCULATING</topic><topic>COMPUTING</topic><topic>COUNTING</topic><topic>ELECTRIC DIGITAL DATA PROCESSING</topic><topic>PHYSICS</topic><toplevel>online_resources</toplevel><creatorcontrib>SEVILMIS TARKAN</creatorcontrib><creatorcontrib>AGARWAL JANAK MADHUSUDAN</creatorcontrib><creatorcontrib>KAPADIA ARSHISH CYRUS</creatorcontrib><creatorcontrib>SHAH HARDIK</creatorcontrib><creatorcontrib>JOSE TITTU</creatorcontrib><creatorcontrib>LUKIYANOV MAXIM</creatorcontrib><creatorcontrib>IRIMESCU GHEORGHITA</creatorcontrib><creatorcontrib>CLARK STEPHEN JOHN</creatorcontrib><creatorcontrib>LINGANNAPETA SREEKANTH</creatorcontrib><collection>esp@cenet</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>SEVILMIS TARKAN</au><au>AGARWAL JANAK MADHUSUDAN</au><au>KAPADIA ARSHISH CYRUS</au><au>SHAH HARDIK</au><au>JOSE TITTU</au><au>LUKIYANOV MAXIM</au><au>IRIMESCU GHEORGHITA</au><au>CLARK STEPHEN JOHN</au><au>LINGANNAPETA SREEKANTH</au><format>patent</format><genre>patent</genre><ristype>GEN</ristype><title>Failure mode identification and reporting</title><date>2015-08-11</date><risdate>2015</risdate><abstract>When a software component is starting (305), such as but not limited to a task or a subtask, the component pushes (310) its identification (ID) onto a stack. The component then executes (315) its other instructions. If the component completes its instructions so that it can terminate normally (320), then it pops (325) the stack, which removes its ID from the stack. If the component fails, such as by not being able to complete its instructions, then it will not be able to pop the stack so its ID will remain in the stack. Another software process can then read the IDs in the stack to identify (330) which components have failed and can automatically take a specified action (335), such as by sending an email message to, sending a text message to, or calling by telephone, a person or persons responsible for that software component.</abstract><oa>free_for_read</oa></addata></record> |
| fulltext | fulltext_linktorsrc |
| identifier | |
| ispartof | |
| issn | |
| language | eng |
| recordid | cdi_epo_espacenet_US9104561B2 |
| source | esp@cenet |
| subjects | CALCULATING COMPUTING COUNTING ELECTRIC DIGITAL DATA PROCESSING PHYSICS |
| title | Failure mode identification and reporting |
| url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-06T19%3A37%3A04IST&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=SEVILMIS%20TARKAN&rft.date=2015-08-11&rft_id=info:doi/&rft_dat=%3Cepo_EVB%3EUS9104561B2%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 |