QNX operation system network auto configuration
A network of computers communicate with each other and with a single system manager computer in accordance with the QNX operating system to perform a series of related tasks. When computers at a number of sites running the operating system boot up, they have resident software that will read a hardwa...
Gespeichert in:
| Hauptverfasser: | , |
|---|---|
| Format: | Patent |
| Sprache: | eng |
| 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 | Lewis, Howard Fry, Rick A |
| description | A network of computers communicate with each other and with a single system manager computer in accordance with the QNX operating system to perform a series of related tasks. When computers at a number of sites running the operating system boot up, they have resident software that will read a hardware configuration switch that is external to the computer. After reading the switch, the hardware node ID is used as the host ID portion of the IP address. Once a network computer is configured with the correct IP address, communication with other computers on the network can begin. Each QNX node will access the System Manager hard disk to access executables and files using the SMB (Server Message Block) file sharing protocol. If the hardware node ID does not match the current software logic node ID as specified by the QNX system, then the proper QNX files will be retrieved from the System Manager and the QNX node will then reboot itself. At this point, each QNX node will execute the proper software by utilizing the unique logic node ID as a reference to load software to the node. |
| format | Patent |
| fullrecord | <record><control><sourceid>uspatents_EFH</sourceid><recordid>TN_cdi_uspatents_grants_07051093</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>07051093</sourcerecordid><originalsourceid>FETCH-uspatents_grants_070510933</originalsourceid><addsrcrecordid>eNrjZNAP9ItQyC9ILUosyczPUyiuLC5JzVXISy0pzy_KVkgsLclXSM7PS8tML4Wo4GFgTUvMKU7lhdLcDApuriHOHrqlxQWJJal5JcXx6UWJIMrA3MDU0MDS2JgIJQAsWyw-</addsrcrecordid><sourcetype>Open Access Repository</sourcetype><iscdi>true</iscdi><recordtype>patent</recordtype></control><display><type>patent</type><title>QNX operation system network auto configuration</title><source>USPTO Issued Patents</source><creator>Lewis, Howard ; Fry, Rick A</creator><creatorcontrib>Lewis, Howard ; Fry, Rick A ; Lockheed Martin Corporation</creatorcontrib><description>A network of computers communicate with each other and with a single system manager computer in accordance with the QNX operating system to perform a series of related tasks. When computers at a number of sites running the operating system boot up, they have resident software that will read a hardware configuration switch that is external to the computer. After reading the switch, the hardware node ID is used as the host ID portion of the IP address. Once a network computer is configured with the correct IP address, communication with other computers on the network can begin. Each QNX node will access the System Manager hard disk to access executables and files using the SMB (Server Message Block) file sharing protocol. If the hardware node ID does not match the current software logic node ID as specified by the QNX system, then the proper QNX files will be retrieved from the System Manager and the QNX node will then reboot itself. At this point, each QNX node will execute the proper software by utilizing the unique logic node ID as a reference to load software to the node.</description><language>eng</language><creationdate>2006</creationdate><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktopdf>$$Uhttps://image-ppubs.uspto.gov/dirsearch-public/print/downloadPdf/7051093$$EPDF$$P50$$Guspatents$$Hfree_for_read</linktopdf><link.rule.ids>230,308,776,798,881,64012</link.rule.ids><linktorsrc>$$Uhttps://image-ppubs.uspto.gov/dirsearch-public/print/downloadPdf/7051093$$EView_record_in_USPTO$$FView_record_in_$$GUSPTO$$Hfree_for_read</linktorsrc></links><search><creatorcontrib>Lewis, Howard</creatorcontrib><creatorcontrib>Fry, Rick A</creatorcontrib><creatorcontrib>Lockheed Martin Corporation</creatorcontrib><title>QNX operation system network auto configuration</title><description>A network of computers communicate with each other and with a single system manager computer in accordance with the QNX operating system to perform a series of related tasks. When computers at a number of sites running the operating system boot up, they have resident software that will read a hardware configuration switch that is external to the computer. After reading the switch, the hardware node ID is used as the host ID portion of the IP address. Once a network computer is configured with the correct IP address, communication with other computers on the network can begin. Each QNX node will access the System Manager hard disk to access executables and files using the SMB (Server Message Block) file sharing protocol. If the hardware node ID does not match the current software logic node ID as specified by the QNX system, then the proper QNX files will be retrieved from the System Manager and the QNX node will then reboot itself. At this point, each QNX node will execute the proper software by utilizing the unique logic node ID as a reference to load software to the node.</description><fulltext>true</fulltext><rsrctype>patent</rsrctype><creationdate>2006</creationdate><recordtype>patent</recordtype><sourceid>EFH</sourceid><recordid>eNrjZNAP9ItQyC9ILUosyczPUyiuLC5JzVXISy0pzy_KVkgsLclXSM7PS8tML4Wo4GFgTUvMKU7lhdLcDApuriHOHrqlxQWJJal5JcXx6UWJIMrA3MDU0MDS2JgIJQAsWyw-</recordid><startdate>20060523</startdate><enddate>20060523</enddate><creator>Lewis, Howard</creator><creator>Fry, Rick A</creator><scope>EFH</scope></search><sort><creationdate>20060523</creationdate><title>QNX operation system network auto configuration</title><author>Lewis, Howard ; Fry, Rick A</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-uspatents_grants_070510933</frbrgroupid><rsrctype>patents</rsrctype><prefilter>patents</prefilter><language>eng</language><creationdate>2006</creationdate><toplevel>online_resources</toplevel><creatorcontrib>Lewis, Howard</creatorcontrib><creatorcontrib>Fry, Rick A</creatorcontrib><creatorcontrib>Lockheed Martin Corporation</creatorcontrib><collection>USPTO Issued Patents</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>Lewis, Howard</au><au>Fry, Rick A</au><aucorp>Lockheed Martin Corporation</aucorp><format>patent</format><genre>patent</genre><ristype>GEN</ristype><title>QNX operation system network auto configuration</title><date>2006-05-23</date><risdate>2006</risdate><abstract>A network of computers communicate with each other and with a single system manager computer in accordance with the QNX operating system to perform a series of related tasks. When computers at a number of sites running the operating system boot up, they have resident software that will read a hardware configuration switch that is external to the computer. After reading the switch, the hardware node ID is used as the host ID portion of the IP address. Once a network computer is configured with the correct IP address, communication with other computers on the network can begin. Each QNX node will access the System Manager hard disk to access executables and files using the SMB (Server Message Block) file sharing protocol. If the hardware node ID does not match the current software logic node ID as specified by the QNX system, then the proper QNX files will be retrieved from the System Manager and the QNX node will then reboot itself. At this point, each QNX node will execute the proper software by utilizing the unique logic node ID as a reference to load software to the node.</abstract><oa>free_for_read</oa></addata></record> |
| fulltext | fulltext_linktorsrc |
| identifier | |
| ispartof | |
| issn | |
| language | eng |
| recordid | cdi_uspatents_grants_07051093 |
| source | USPTO Issued Patents |
| title | QNX operation system network auto configuration |
| url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-02-05T18%3A33%3A46IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-uspatents_EFH&rft_val_fmt=info:ofi/fmt:kev:mtx:patent&rft.genre=patent&rft.au=Lewis,%20Howard&rft.aucorp=Lockheed%20Martin%20Corporation&rft.date=2006-05-23&rft_id=info:doi/&rft_dat=%3Cuspatents_EFH%3E07051093%3C/uspatents_EFH%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 |