Fetching topologies using timestamp-callback map
US-12184500-B1 · Dec 31, 2024 · US
US11973652B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11973652-B2 |
| Application number | US-201917286553-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 21, 2019 |
| Priority date | Dec 21, 2018 |
| Publication date | Apr 30, 2024 |
| Grant date | Apr 30, 2024 |
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.
Disclosed is a field detection device designed to be connected to at least one access point of a fieldbus network via at least one interface. The field detection device is designed to initiate or execute, for each of at least two connection protocols, an associated query in at least one fieldbus segment of the fieldbus network and to detect which field devices and fieldbus components in said at least one fieldbus segment can be accessed via the connection protocol in question. Furthermore, the field detection device is designed to provide a connection directory in which at least one connection protocol is specified for each field device and for each fieldbus component of a set of field devices and fieldbus components of the at least one fieldbus segment, by means of which connection protocol the field device in question or the fieldbus component in question can be accessed.
Opening claim text (preview).
The invention claimed is: 1. A field detection device, comprising: at least one fieldbus interface; a central processing unit; and a memory associated with the central processing unit; wherein the field detection device is designed to be connected to at least one access point of a fieldbus network via the at least one fieldbus interface, wherein the field detection device is further designed to initiate or execute, for each of at least two connection protocols, an associated query in at least one fieldbus segment of the fieldbus network and to detect which field devices and fieldbus components in said at least one fieldbus segment can be accessed by means of the connection protocol in question, wherein the field detection device is further designed to provide a connection directory in which at least one connection protocol is specified for each field device and for each fieldbus component of a set of field devices and fieldbus components of the at least one fieldbus segment by means of which connection protocol the field device in question or the fieldbus component in question can be accessed, and wherein in the connection directory at least one access path is specified in each case for a field device or a fieldbus component and a connection protocol supported by this field device or fieldbus component via which a field operating device can access the field device or the fieldbus component. 2. The field detection device according to claim 1 , characterized by at least one of the following: at least one connection protocol is specified in the connection directory for each field device and for each fieldbus component of the at least one fieldbus segment by means of which protocol the field device in question or the fieldbus component in question can be accessed; and in the connection directory, all connection protocols which have been checked by the field detection device and by means of which the field device in question or the fieldbus component in question can be accessed are specified for each field device and for each fieldbus component of the set of field devices and fieldbus components of the at least one fieldbus segment. 3. The field detection device according to claim 1 , characterized by at least one of the following: the field detection device is designed to transmit the connection directory in full or in part to a field operating device upon a request of the field operating device; the field detection device is designed to exchange data with the fieldbus network via the at least one access point; the connection protocols are Ethernet-based connection protocols; the connection protocols comprise at least one fieldbus protocol; the connection protocols comprise at least one Industrial Ethernet protocol; and the connection protocols comprise at least one of: Profinet, HTTP, TCP UA, OPC UA, CDI_TCP, EtherNet/IP, HART-IP. 4. The field detection device according to claim 3 , wherein the field detection device is designed to establish test connections on a trial basis under a specific connection protocol for the field devices and fieldbus components of the at least one fieldbus segment and thus to determine whether a field device in question or a fieldbus component in question supports the connection protocol in question. 5. The field detection device according to claim 1 , characterized by at least one of the following: the field detection device is designed to establish connections with the fieldbus network via at least two access points; the field detection device is designed to establish at least one wireless connection with at least one first access point of the fieldbus network; and the field detection device is designed to establish at least one wired connection to at least one second access point of the fieldbus network. 6. The field detection device according to claim 1 , characterized by at least one of the following: connection possibilities for field devices and fieldbus components of the fieldbus network are arranged in the connection directory grouped by field devices or fieldbus components; the connection possibilities for field devices and fieldbus components of the fieldbus network are grouped in the connection directory according to one of the following: IP addresses of the field devices or fieldbus components, MAC addresses of the field devices or fieldbus components, tags of the field devices or fieldbus components; in the connection directory, at least one of the following is specified for a field device or a fieldbus component: an IP address, a MAC address, a tag; and topology information is maintained by the field detection device, and the field detection device is designed to determine a suitable access path to a field device or a fieldbus component and to a particular connection protocol based on the topology information. 7. The field detection device according to claim 1 , characterized in that in the connection directory in each case at least one access point is specified for a field device or a fieldbus component and a connection protocol supported by this field device or the fieldbus component by means of which access point a connection to the field device or the fieldbus component can be established. 8. The field detection device according to claim 1 , characterized by at least one of the following: the field detection device is designed to update the connection directory in accordance with a prespecifiable time scheme; the field detection device is designed to repeat, for the at least two connection protocols, the query as to which field devices and fieldbus components of the at least one fieldbus segment can be accessed by means of the connection protocol in question in accordance with a prespecifiable time scheme and to update the connection directory using the found results; the field detection device is only designed to provide the connection directory to a field operating device and is not designed to establish connections to field devices and fieldbus components of the fieldbus network; the field detection device is not designed to establish connections between a field operating device and a field device or a fieldbus component of the fieldbus network; and the field detection device is configured as a standalone separate device which is designed to be connected to a fieldbus network. 9. The field detection device according to claim 1 , characterized by any of the following: the field detection device is designed to execute the query as to which field devices and fieldbus components can be accessed by means of a respective connection protocol only within the at least one fieldbus segment; and the field detection device is designed such that the query as to which field devices and fieldbus components can be accessed by means of a connection protocol in question extends beyond the at least one fieldbus segment via gateway devices to additional fieldbus segments of the fieldbus network. 10. The field detection device according to claim 1 , characterized by at least one of the following: the field detection device is designed to provide an internet server via which field devices and fieldbus components of the fieldbus network can be accessed by means of the HTTP protocol; the field detection device is designed to provide an internet server with links to internet sites and internet services of field devices and fieldbus components of the fieldbus network; and the field detection device is designed to provide the OPC UA standard with an OPC UA information model which contains connection information to field devices and/or fieldbus components. 11. The field detection device according to claim 1 , wherein the field detection d
Discovery or management of network topologies · CPC title
Interoperability with other network applications or services · CPC title
Query processing · CPC title
Selecting an access point · CPC title
Field device · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.