Automatic naming and configuration of replacement electronic devices

Automatically configure replacement devices by performing local discovery processes and topological hash calculations on the bus connector, solving complex and time-consuming problems of manual configuration, enabling fast and flexible device replacement and configuration, reducing downtime and expertise demand.

CN119032546APending Publication Date: 2024-11-26SCHNEIDER ELECTRIC USA INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380033524.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-12
Filing Date
2023-04-11
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

In modern computing environments, the process of manually configuring replacement electronic devices is complicated and time-consuming, especially in environments where rapid replacement and minimization of downtime is required. The prior art is difficult to effectively manage the replacement and configuration of electronic devices, resulting in production bottlenecks and Costs increase.

Method used

By performing a local discovery process on the bus connector, identifying the bus devices in the subnet, submitting an Internet protocol address request, obtaining an IP address, and calculating topological hash based on the device identification, automatically configuring the bus connector to realize device name and configuration information Mapping reduces dependence on bus device processing and storage capacity.

Benefits of technology

The ability to automatically naming and configure replacement devices is realized, reducing the need for manual configuration, shortening downtime, improving the flexibility and efficiency of device replacement, and reducing dependence on expertise and tools.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119032546A_ABST
    Figure CN119032546A_ABST
Patent Text Reader

Abstract

A method performed by a bus coupler of a sub-network coupled to one or more local sub-networks of the entire network includes performing a local discovery process for discovering and identifying one or more bus devices included in the sub-network. The method further includes submitting an Internet Protocol (IP) address request to obtain an IP address of the bus coupler, receiving the IP address of the bus coupler at the bus coupler in response to the IP address assignment request, submitting a configuration request for configuration information associated with a device name of the bus coupler, receiving the configuration information in response to the configuration request, and transmitting the configuration information to the bus coupler. And configuring the at least one feature of the bus coupler using the configuration information, wherein the device name is based on the identification of the respective one or more bus devices obtained by the discovery process.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. patent application serial number 17 / 718,743, filed on April 12, 2022, entitled “AUTOMATIC NAMING AND CONFIGURATION OF AREPLACEMENT ELECTRONIC DEVICE,” the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to electronic rapid device replacement, and more particularly, to techniques for automatically naming and configuring a replacement electronic device. Background Art

[0004] As the number of interconnected electronic devices continues to grow, it becomes increasingly important to effectively manage the replacement of electronic devices and the configuration of new electronic devices. Although engineers have historically been required to manually configure replacement electronic devices, this practice is very cumbersome and inefficient in environments with a large number of interconnected electronic devices. In addition, as the configurability and flexibility of electronic devices increase, the configuration of these devices becomes more complex and often requires expertise and tools to configure. These difficulties are exacerbated in environments where downtime needs to be minimized for business reasons. For example, a large amount of downtime in a factory environment can create bottlenecks on assembly lines and delay production schedules, resulting in significant costs to the business. As another example, a long downtime of an electronic device that hosts website components for a large retailer can cause the retailer to lose a large amount of sales and customer goodwill. Therefore, in modern computing environments, relying on engineers to manually configure all replacement devices has become increasingly problematic and, in some cases, infeasible. Summary of the invention

[0005] The objects and advantages of the exemplary embodiments described below will be set forth and become apparent in the following description. Additional advantages of the illustrated embodiments will be realized and obtained by the devices, systems, and methods particularly pointed out in the written description and claims thereof and in the accompanying drawings. To achieve these and other advantages, and in accordance with the objects of the illustrated embodiments, in one aspect, a method is disclosed that is performed by a bus coupler of a sub-network connected to one or more sub-networks of an entire network. The method includes performing a local discovery process for discovering and identifying one or more bus devices included in the sub-network, submitting an Internet Protocol (IP) address request by the bus coupler via the entire network and outside the sub-network to obtain an IP address for the bus coupler, receiving the IP address of the bus coupler in response to the IP address allocation request, submitting a configuration request for configuration information associated with a device name of the bus coupler via the entire network and outside the sub-network by the bus coupler, wherein the device name is based on the identification of the corresponding one or more bus devices obtained through the discovery process, receiving configuration information in response to the configuration request, and configuring at least one feature of the bus coupler using the configuration information.

[0006] In one or more embodiments, the method may further include calculating a topological hash at the bus coupler by applying a hash function to the identification of the corresponding one or more bus devices, wherein the device name is based on the topological hash.

[0007] In one or more embodiments, the one or more bus devices may include a plurality of bus devices, and the method further includes combining identifications of the corresponding plurality of bus devices, wherein a hash function may be applied to the combination.

[0008] In one or more embodiments, combining the identifications of the plurality of bus devices may include concatenating the identifications of the corresponding plurality of bus devices in a predefined order.

[0009] In one or more embodiments, the corresponding multiple bus device identifiers can be spliced ​​together based on the order in which the bus devices corresponding to the corresponding identifiers are discovered, based on the topology of the sub-network, based on the information included in the corresponding identifiers, and / or based on the connections between the discovered bus devices.

[0010] In one or more embodiments, the identification of one or more bus devices may include one or more business references.

[0011] In one or more embodiments, a path to a server servicing the configuration request may be provided in response to the address request and the configuration request may be submitted using the path.

[0012] In one or more embodiments, the configuration information may also be associated with a network name of the bus connector, where the network name may be a name that identifies the bus connector, and the network name may be used by network devices located outside the sub-network that are connected to the entire network for network discovery requests and identification of the bus connector.

[0013] In one or more embodiments, the method may further include verifying the configuration information, wherein once the configuration information is verified, at least one feature of the bus coupler may be configured.

[0014] In one or more embodiments, configuring at least one feature of the bus coupler may further include configuring at least one of (i) network connection information and (ii) application-specific configuration information for the bus coupler.

[0015] In one or more embodiments, the method may further include determining, by the bus coupler, that the bus coupler needs to be configured or reconfigured, wherein in response to determining that the bus coupler needs to be configured or reconfigured, the bus coupler may initiate performing a discovery process, submitting an address request, and / or submitting a configuration request.

[0016] According to another aspect of the present disclosure, a method performed by a fast device replacement (FDR) server is disclosed. The method includes receiving a configuration request from a bus connector of a subnetwork of one or more subnetworks via an entire network connected to one or more subnetworks. The configuration request is provided outside the subnetwork and requests configuration information associated with a device name of the bus connector, wherein the device name is based on an identification of the corresponding one or more bus devices obtained by a local discovery process, and the local discovery process is used to discover and identify the corresponding one or more bus devices included in the subnetwork. The method also includes accessing a mapping of the device name of each bus connector of the corresponding one or more subnetworks to the configuration information of the bus connector. The device name of each bus connector is based on the identification of the corresponding one or more bus devices obtained by a previously performed discovery process, which is performed locally within the subnetwork of the bus connector for discovering and identifying the corresponding one or more bus devices included in the subnetwork. The method also includes providing configuration information mapped to the device name in the configuration request in response to the configuration request.

[0017] In one or more embodiments, the method may further include determining that the bus coupler requires configuration or reconfiguration, wherein in response to determining that the bus coupler requires configuration or reconfiguration, the FDR server may access the mapping and provide a configuration response.

[0018] In one or more embodiments, the device name may be based on a topological hash calculated at the bus coupler by applying a hash function to the identification of the corresponding one or more bus devices.

[0019] In one or more embodiments, the one or more bus devices may include a plurality of bus devices, wherein the hash function may be applied to a combination of identifications of the corresponding plurality of bus devices.

[0020] In one or more embodiments, the combination of identifications may be a concatenation of identifications in a predetermined order, wherein the concatenation of identifications may be based on an order in which bus devices corresponding to respective identifications are discovered, based on a topology of a sub-network, based on information included in respective identifications, and / or based on connections between discovered bus devices.

[0021] In one or more embodiments, the mapping may also map the device name to a network name of the bus coupler, where the network name may be a name identifying the bus coupler and may be used by network devices outside the sub-network connected to the overall network for network discovery requests and identification of the bus coupler.

[0022] In one or more embodiments, the bus coupler may use the configuration information to configure at least one feature of the bus coupler, including at least one of (i) network connection information and (ii) application-specific configuration information.

[0023] According to other aspects of the present disclosure, a bus connector for a sub-network connected to one or more sub-networks of an entire network is provided. The bus connector includes a memory configured to store instructions and one or more processing devices arranged to communicate with the memory, wherein the one or more processing devices are configured to perform a local discovery process for discovering and identifying one or more bus devices included in the sub-network when executing the instructions, submit an Internet Protocol (IP) address request via the entire network and outside the sub-network to obtain an IP address of the bus connector; receive the IP address of the bus connector in response to the IP address allocation request, submit a configuration request for configuration information associated with a device name of the bus connector via the entire network and outside the sub-network, wherein the device name is based on the identification of the corresponding one or more bus devices obtained through the discovery process, receive configuration information in response to the configuration request, and configure at least one feature of the bus connector using the configuration information.

[0024] In one or more embodiments, the one or more bus devices may include multiple bus devices, and when executing the instructions, the one or more processing devices may also be configured to combine the identifications of the corresponding multiple bus devices and apply a hash function to the combined identifications, wherein the device name may be based on a topological hash.

[0025] According to another aspect of the present disclosure, an FDR server is disclosed. The FDR server includes a memory configured to store instructions and one or more processing devices arranged to communicate with the memory. The one or more processing devices are configured to receive a configuration request from a bus connector of a sub-network of one or more sub-networks via an entire network connected to one or more sub-networks when executing the instructions, access a mapping of a device name of each bus connector of the corresponding one or more sub-networks to configuration information of the bus connector, and provide configuration information in response to the configuration request. The configuration request is provided outside the sub-network and requests configuration information associated with the device name of the bus connector, wherein the device name is based on an identification of the corresponding one or more bus devices obtained by a local discovery process, and the local discovery process is used to discover and identify the corresponding one or more bus devices included in the sub-network. The device name of each bus connector is based on the identification of the corresponding one or more bus devices obtained by a previously executed discovery process, which is locally executed within the sub-network of the bus connector for discovering and identifying the corresponding one or more bus devices included in the sub-network.

[0026] In one or more embodiments, the one or more bus devices may include a plurality of bus devices, and the device name may be based on a topological hash calculated at the bus coupler by applying a hash function to a combination of identifications of the corresponding plurality of bus devices.

[0027] According to another aspect of the present disclosure, an industrial network system is provided. As disclosed, the industrial network system includes a bus connector connected to a sub-network of one or more sub-networks of the entire network, and an FDR server as disclosed.

[0028] These and other features of the systems and methods of the subject disclosure will become more readily apparent to those skilled in the art from the following detailed description of the preferred embodiments taken in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] A more detailed description of the disclosure briefly summarized above can be obtained by reference to various embodiments, some of which are shown in the accompanying drawings. Although the drawings illustrate selected embodiments of the disclosure, these drawings are not to be considered limiting of its scope, as the disclosure may admit to other equally effective embodiments.

[0030] Figure 1 is a block diagram illustrating an example industrial network system according to one or more embodiments of the present disclosure;

[0031] Figure 2 It is shown Figure 1 A block diagram of a portion of an industrial network system is shown;

[0032] Figure 3is a flow chart illustrating an example method performed by a bus coupler of an industrial network system according to one or more embodiments of the present disclosure;

[0033] Figure 4 is a flowchart illustrating an example method performed by a rapid device replacement server of an industrial network system according to one or more embodiments of the present disclosure; and

[0034] Figure 5 is a flow chart illustrating another example method performed by a fast device replacement server according to one or more embodiments of the present disclosure. DETAILED DESCRIPTION

[0035] Wherever possible, identical reference numerals have been used to designate identical elements that are common to the figures. However, elements disclosed in one embodiment may be beneficially utilized on other embodiments without specific recitation.

[0036] As the number of interconnected electronic devices continues to grow, efficient and reliable device replacement services become increasingly important. In many modern computing environments, it becomes impractical to rely entirely on technicians / maintenance personnel to manually replace electronic devices because (among other reasons) manual configuration of replacement electronic devices can be a time-consuming process and may require special tools or specific multidisciplinary technical expertise and knowledge. Although traditional solutions exist for automatically configuring replacement devices within industrial network systems, such solutions may require a rigid network topology for devices connected to the entire network system using data communications, where the network topology is relative to the entire network system. That is, a replacement device can only be configured using such a traditional system when the replacement device is in exactly the same position as the device being replaced in a static overall network topology.

[0037] It is also noted that the use of bus devices to assist in the automatic configuration of replacement devices in an industrial network system is not appropriate where the bus devices are low-level electronic devices, which are simple devices with limited processing and / or memory resources. The processing and / or memory resources of the bus devices may be too limited to assist in the automatic configuration of replacement devices, such as the bus coupler to which the bus devices are connected. The bus devices may also not be able to communicate data with the entire network system and may be limited to local communications within a sub-network having only the bus coupler and the bus devices connected to the bus coupler via the sub-network.

[0038] While conventional solutions are generally considered satisfactory for their intended purposes, implementing a static network topology associated with an entire network system is not always satisfactory or even feasible, and there remains a need in the art for an FDR service that allows flexibility in network topology for replacement of electronic devices included in the network topology, and an FDR service that can be provided regardless of the computing and storage capacity of bus devices included in the industrial network system.

[0039] Thus, the embodiments described herein provide techniques for automatically naming and configuring replacement devices for a bus coupler using information based on a discovery process that is limited to a subnetwork of replacement devices that include a bus coupler (referred to herein as a bus coupler) and one or more bus devices locally connected to the bus coupler. In doing so, the embodiments described herein can minimize downtime for the replacement device, in large part by facilitating automatic transfer of setup and configuration parameters to the replacement device that are independent of the processing or storage capacity of the bus device, and allowing flexible connection of the bus coupler and its replacement device to the overall data communications network of the industrial network system. This flexibility allows the bus coupler and its replacement device to freely use different ports (e.g., Ethernet ports) or have different neighbors on the overall data communications network of the industrial network system.

[0040] Potential advantages and benefits may include minimizing or eliminating the need for manual configuration (e.g., by an engineer) for placing a replacement device into service, and eliminating the need for a user to know and track the network name of the device being replaced. In addition, embodiments may reduce the likelihood of user error when setting the network name for a bus coupler, and may avoid the need for a user to manually configure a replacement device.

[0041] The illustrated embodiments are now described more fully with reference to the accompanying drawings, wherein like reference numerals represent similar structural / functional features. The illustrated embodiments are not limited in any way to what is shown, as the illustrated embodiments described below are merely exemplary and may be implemented in various forms as understood by those skilled in the art. Therefore, it should be understood that any structural and functional details disclosed herein should not be interpreted as limiting, but merely as a basis for claims and claims. In addition, the terms and phrases used herein are not intended to be limiting, but rather to provide an understandable description of the illustrated embodiments.

[0042] Turning descriptively now to the drawings, wherein like reference numerals refer to like elements throughout the several views, Figure 11 is a block diagram illustrating an exemplary industrial network system 100 in which the embodiments illustrated below may be implemented. The industrial network system 100 includes a PLC 110 and one or more bus couplers 104(1)-104(m) (collectively referred to as bus couplers 104) that communicate data with a data communication bus 112 via a network 120. The network 120 provides an overall network to which each of the bus couplers 104(1)-104(m) may be connected. The bus couplers 104(1)-104(m) may be initially installed bus couplers or replacement bus couplers.

[0043] The network 120 represents any suitable data communication network, examples of which include, but are not limited to, a local area network (LAN), a wide area network (WAN), an IEEE 802.11 wireless network, a Wi-Fi network, a router, a hub, a switch, a server computer, and / or a combination thereof, etc. The communication link between devices (e.g., a fieldbus device 106, a bus device 106, a fieldbus device 106, or a PLC 110 and the network 120) can be a hardwired link, a wireless link, or a combination of hardwired or wireless links. In the example shown, the network 120 is implemented using the Ethernet protocol, and the bus coupler 104 is not limited to using a specific Ethernet port when replaced.

[0044] The industrial network system 100 also includes one or more sub-networks 102 having bus couplers 104, each of which is locally connected to one or more bus devices 106 via a sub-bus 108. The bus devices 106 are not directly connected to any network or device outside of their sub-network. For example, bus couplers 104(1)-104(m) are connected to sub-buses 108(1)-108(m). The automatic replacement process does not use direct communication between any bus device 106 and the data communication bus 112 or network 120, and does not require the bus devices 106 to process or store information associated with the automatic replacement process.

[0045] In one or more embodiments, one or more (or all) bus devices 106 may be connected to the data communication bus 112 only through their locally connected bus couplers 104. In addition, one or more (or all) bus devices 106 may have limited processing and memory capabilities such that they are unable to participate in the automatic replacement process.

[0046] In one or more embodiments, one or more bus devices 106 can be connected to the data communication bus 112 independently of their associated bus couplers 104, and / or can have processing and / or greater storage capacity. Even so, however, the automatic replacement process is performed independently of the bus device's ability to communicate data with the data communication bus 112 or network 120, and independently of any greater processing and / or storage capacity, even if either or both are present.

[0047] The PLC 110 is shown as including an IP address allocation server 118 and an FDR server 118. One or both of the IP address allocation server 118 and the FDR server 118 may be integrated with the PLC 110, or may be separate from the PLC 110 (e.g., may have its own IP address, housing, processor), and may be directly connected to the PLC 110, or may access the bus connector 104(i) and the PLC 110 via the network 120.

[0048] It should be understood that the illustrated embodiments discussed below are preferably software algorithms, programs, codes or logic resident on a computer usable medium having control logic for enabling execution on a machine having a computer processor. The machine typically includes a memory configured to provide an output of the execution of a computer algorithm or program.

[0049] As used herein, the term "software" is meant to be synonymous with any code or program that can be in a processor of a host computer, regardless of whether the implementation is in hardware, firmware, or as a software computer product available on a disk, memory storage device, or downloaded from a remote machine. The embodiments described herein include such software to implement the above equations, relationships, and algorithms. Based on the above embodiments, those skilled in the art will appreciate more features and advantages of the illustrated embodiments. Therefore, the illustrated embodiments are not limited by what has been specifically shown and described, except as indicated by the appended claims.

[0050] Figure 2 is a block diagram showing an industrial network system 100 having a PLC 110, a bus coupler 104(i) (where 1≤i≤m), and a bus device 106(j) (where 1≤j≤n) connected to the bus coupler 104(i) via a sub-bus 108(i). Figure 2 The bus coupler 104 ( i ) shown in FIG. 1 is shown as an example replacement bus coupler that replaces a previous bus coupler (which may be an initially installed bus coupler or may also be a replacement bus coupler).

[0051] The PLC 110 and the bus coupler 104(1) communicate via a data communication bus 112, which may be connected to a network 120. The PLC 110 includes one or more computer processors 202, a memory 204, an input module 206, an output module 210, a network interface controller 210, and an IP address assignment logic 214. Generally, the input module 206 represents a device that provides input to the PLC 110. Such input may be provided, for example, in the form of a digital input or an analog signal. In the case of an analog signal, the input module 206 may include circuitry for converting the analog signal into a logic signal that may be processed by the processor 202. The output module 210 generally converts the logic signal from the processor 202 into a digital or analog value for controlling an output device. The memory 204 may store a dedicated program logic 206, an IP address assignment server 116, and an FDR server. Generally, the dedicated program logic 206 represents software logic that performs various dedicated operations depending on the type of environment of the industrial network system 100. For example, a PLC device 110 in an industrial automation environment may perform different specialized operations than a PLC device 110 in a fulfillment center environment.

[0052] The data store 220 includes a device name mapping 222 and a configuration profile set 224. The device name mapping 222 generally represents a data structure that maps a device name to configuration information stored in the configuration profile set 224. For example, the device name mapping 222 can represent a table within a database (e.g., having a first column for a device name, a second column for a configuration information identifier, and rows storing each mapping between a device name and a configuration information identifier). However, more generally, any type of mapping between a device name and configuration information can be used, consistent with the functionality described herein. The configuration profile set 224 can include multiple configuration profiles, each having configuration information mapped to a configuration information identifier. The configuration information identifier in the device name mapping 222 can be used to access the appropriate configuration information stored in the configuration profile set 224.

[0053] In general, the bus connector 104 (i) represents a computing device used for real-time distributed control within the industrial network system 100. In the depicted embodiment, the bus connector 104 (i) acts as a management device for the bus devices 106, which are typically lower-level devices (e.g., motor starters, power devices, sensor devices, etc.). For example, the bus connector 104 (i) can coordinate the execution of operations by controlling the actions of one or more bus devices 106. As another example, the bus connector 104 (i) can collect data (e.g., sensor data) from the bus devices 106, and can process and aggregate the data for subsequent transmission to the PLC 110. The PLC 110 can generally perform higher-level management functions and can manage the bus connector 104 (i) as well as other bus connectors (not shown) within the industrial network system 100.

[0054] The bus coupler 104(i) includes a processor 252, a memory 254, a network interface controller 264, and a communication interface 266. The memory 254 includes program logic 256, a fast device replacement (FDR) control module 258, dedicated configuration information 260, and network configuration information 262. Generally, the program logic 256 represents dedicated program logic to perform one or more functions that have been assigned to the bus coupler 104(i). For example, the bus coupler 104(i) may be configured to perform operations in an industrial automation environment that may be different from the operations performed by the bus coupler 104(i) in other computing environments, and thus the program logic 256 may vary depending on the type of environment in which the bus coupler 104(i) is deployed.

[0055] In the depicted embodiment, the bus device 106(j) includes a processor 282, a memory 284, and a communication interface 290. The memory 284 contains program logic 286, which in turn contains a dedicated interface (API) 288. The API 288 can facilitate the execution of tasks assigned to the bus device 106, such as reporting or storing sensed data, activating switches, etc. The bus device 106(j) cannot communicate with the data communication bus 112 or the network 140 except via its communication interface 290, the sub-bus 108(i), and the bus coupler 104(i). For example, the bus device 106(j) shown in the example does not include a network interface controller, such as the network interface controller 264 or 212. Even if the bus device 106(j) includes a network interface controller, this is not required to request configuration information.

[0056] The communication interface 290 provides local data communication only within the sub-network 102, which includes only devices connected to the sub-bus 108(i), including the bus coupler 104(i) and other bus devices 106(1)-106(n) connected to the sub-bus 108(i). Each bus coupler 104(i) communicates with its own sub-network 102, which includes one or more bus devices 106(1)-106(n), via its communication interface 266. When a bus coupler 104(i) is connected to its corresponding sub-bus 108(i) as a replacement device, it can use the discovery process described below to discover each bus device 106(1)-106(j) connected to the sub-bus 108(i). In one or more embodiments, each sub-network 102 can be mutually exclusive with respect to other sub-networks so that no device is included in more than one sub-network.

[0057] Any general-purpose computer system used in various embodiments of the present disclosure can be, for example, a general-purpose computer with a general-purpose computer processor. For example, processors 202, 252, and 282 can include processors based on Intel Pentium processors, Motorola PowerPC, Sun UltraSPARC, HP PA-RISC processors, or any other type of processors. Typically, processors 202, 252, and 282 represent any suitable processor, including commercially available processors, such as the well-known Pentium processors available from Intel Corporation. Many other processors are also available. Such processors typically execute an operating system (not shown), which can be, for example, but not limited to Microsoft Windows, Apple macOS, Solaris, UNIX, or Linux. Many other operating systems can be used.

[0058] Memories 204, 254, and 284 generally represent any suitable form of addressable computer memory. For example, memories 204, 254, and 284 may represent volatile memory (e.g., static random access memory (SRAM)) and / or non-volatile memory (e.g., flash memory). More generally, any suitable form of memory device may be used, consistent with the functionality described herein. Typically, a processor and an operating system together define a computer platform for which applications in high-level programming languages ​​are written. It should be understood that embodiments of the present disclosure are not limited to specific computer system platforms, processors, operating systems, or networks. In addition, it will be apparent to those skilled in the art that the present disclosure is not limited to specific programming languages ​​or computer systems. In addition, it should be understood that other suitable programming languages ​​and other suitable computer systems may also be used.

[0059] One or more parts of the computer system (except the internal part of the local subnet) can be distributed on one or more computer systems connected to the communication network. For example, as described above, the computer system that determines the available power capacity can be far away from the system manager. These computer systems can also be general-purpose computer systems. For example, various aspects of the present disclosure can be distributed in one or more computer systems configured to provide services (e.g., servers) to one or more client computers or perform overall tasks as part of a distributed system. For example, various aspects of the present disclosure can be performed on a client-server or multi-layer system, which includes components distributed in one or more server systems, which perform various functions according to various embodiments of the present disclosure. These components can be executable, intermediate (e.g., IL) or interpreted (e.g., Java) code that communicates on a communication network (e.g., the Internet) using a communication protocol (e.g., TCP / IP). For example, one or more database servers can be used to store device data, such as expected power consumption, which is used to design a layout associated with an embodiment of the present disclosure.

[0060] The bus coupler 104 is communicatively coupled to the bus devices 106 of the same sub-network 102 through its communication interface 266 and the communication interface 290 of each bus device 106. For example, the bus coupler 104 and the bus devices 106 may be connected in any topology, such as in a daisy chain fashion to form a linear network topology, or any of a ring, star, bus, mesh, tree, or hybrid topology. Many different configurations and network topologies are contemplated, and more generally, any suitable configuration and topology may be used, consistent with the functionality described herein.

[0061] The FDR control module 258 may be pre-installed on the bus coupler 104, such as at the time of manufacture, or alternatively, the bus coupler 104 may be updated or retrofitted to include the FDR control module 258 configured to provide the disclosed functionality. Similarly, the IP allocation server 116 and / or the FDR server 118 may be pre-loaded on the PLC 110, such as at the time of manufacture, or alternatively, the PLC 110 may be updated or retrofitted to include the IP allocation server 116 and / or the FDR server 118, each configured to provide the disclosed functionality.

[0062] According to one embodiment, the FDR control module 258 may determine that the bus coupler 104(i) needs to be configured (or reconfigured) based on a determination that the bus coupler 104(i) has been added (e.g., as a replacement device) to a computing environment such as the industrial network system 100 and / or at least one feature of the bus coupler 104(i) is not configured or misconfigured for its current environment. For example, when a bus coupler is moved from a different computing environment (or a different logical location in a computing environment) to its current location, the hypothetical bus coupler may be misconfigured for its current environment. In such an example, the FDR control module 258 may determine that the configuration information of the bus coupler does not match its current physical configuration. For example, if the configuration information of the bus coupler specifies that it is connected to bus devices A, B, and C, but its FDR control module 258 detects that the bus coupler is currently connected to bus devices X, Y, and Z (e.g., through a network discovery process), the FDR control module 258 may determine that the bus coupler is misconfigured for its current physical configuration.

[0063] Once the FDR control module 258 of the bus connector 104(i) determines that the bus connector 104(i) needs to be configured (or reconfigured, for example, due to a change or upgrade to its subnet), it can then initiate the appropriate phase of the replacement process, including a discovery phase, an IP address allocation phase, or submission of a reconfiguration request.

[0064] A discovery phase may be initiated to discover and identify one or more bus devices 106 included in the sub-network 102 of the bus coupler 104(i) and connected to the sub-bus 108(i). In general, the discovery phase may use a number of different device discovery protocols to discover and identify the bus devices 106 included in the sub-network 102 of the bus coupler 104(i). The discovery operation typically uses simple communication techniques that require minimal processing and storage capabilities, such as broadcast messages and replies to the source of the broadcast messages. In an example discovery phase, bus devices 106 in the same sub-network as the bus coupler 104(i) respond to the broadcast discovery request with their identification. As non-limiting examples, the FDR control module 258 may perform a network service device profile (DPWS) discovery process or a link layer discovery protocol (LLDP) discovery process to discover and identify the bus devices 106 of the sub-network of the bus coupler 104(i). More generally, any suitable discovery operation may be utilized, consistent with the functionality described herein.

[0065] The FDR control module 258 can combine the identifications of the discovered bus devices 106 into a combined identification and apply a hashing algorithm to the combined identification to generate a topological hash. If only one bus device 106 is found in the corresponding sub-network, the combined identification will include the identification of the discovered bus device 106. In one or more embodiments, the combined identification is a concatenation of the identifications provided by the discovery process.

[0066] The identities of the discovered bus devices 106 can be sorted before being spliced ​​so that they are spliced ​​in a repeatable order. For example, but not limited to a combination based on a specific technology, the identities can be sorted based on the following items: the order of each corresponding bus device 106 relative to the topology of the corresponding sub-network 102, the order in which the corresponding bus devices 106 are discovered, the information included in the corresponding identity, the connection between the corresponding bus devices 106, the location information about the corresponding bus devices 106, the level of the corresponding bus devices 106, the function of the corresponding bus devices, the priority, or other types of device information about the corresponding bus devices.

[0067] The identification of the bus device 106 can be a business reference, such as a directory name, such as TPRST009 or TPRST025 or a designated name. In some cases, there may be more than one sub-network 102, each sub-network 102 including bus devices 106 with the same business reference, and these bus devices 106 have the same topology (meaning that the same type of bus devices 106 are connected in the same way within their sub-networks 102), which may cause two or more bus connectors 104 to have the same combined identification and topology hash. This may be problematic. To avoid this problem, the bus devices 106 in the industrial network system 100 can be assigned unique identifications, such as by appending a suffix to a common business reference (e.g., a directory name). For example, the suffix can be a serial number of the corresponding bus device 106 or a number that increases for each different bus device 106.

[0068] In the example, the bus coupler 104 can be connected to four bus devices 106, which have directory names TPRST009, TPRST009, TPRST025, and TPRST025, respectively. The bus devices 106 have respective serial numbers 00012, 00013, 00014, and 00015. The FDR control module 258 of the bus coupler 104 concatenates the directory name and serial number of each bus device 106 to form its identification. By combining all bus device identifications based on an order related to the topology of the bus devices to form a combined identification TPRST00900012 TPRST00900013 TPRST02500014 TPRST02500015, a unique string is created for the topology of a particular sub-network 102. The FDR control module 258 of the bus coupler 104 then creates a hash topology of the combined identification, such as a 16-character MD5 hash (which would be F4DBD1028ECC7079), and uses it as the device name of the bus coupler 104 .

[0069] The FDR control module 258 of the bus coupler 104 (i) can then initiate the IP address allocation phase of the replacement process. The IP address allocation phase includes the FDR control module 258 submitting an IP address request to the IP address allocation server 116 to allocate an IP address to the bus coupler 104 (i). The IP address allocation server 116 can be a DHCP server. The address request can be a broadcast request (called discovery for DHCP). The IP address allocation server 116 responds to the address request by allocating an available IP address to the bus coupler 104 (i), which can be an IP address different from the previous bus coupler 104 replaced by the bus coupler 104 (i). The ability to dynamically allocate IP addresses avoids the need for static IP addresses or a static topology for the entire network. In addition, if necessary, for example, when the IP address allocation server 116 and the FDR server 118 have different IP addresses, the IP address allocation server 116 can provide a path (e.g., IP address and / or routing) for communicating with the FDR server 118.

[0070] Using the path and / or IP address of the FDR server 118 (whether known to the FDR control module 258 or received from the IP address allocation server 116), the FDR control module 258 can send a configuration request to the FDR server 118. The configuration request includes a topology hash and either requests an initial installation of the original bus coupler 104, or requests configuration information for a replacement bus coupler, e.g. Figure 2 Bus connector 104(i) is shown.

[0071] When the FDR server 118 receives a configuration request, the FDR server 118 can determine whether the configuration request is for an initial installation of an original bus coupler 104 in the industrial network system 100, or for a configuration or reconfiguration, such as due to a replacement process. This determination can be made by an indication in the configuration request and / or by the FDR server determining whether the hash topology has already been mapped to the configuration information, which is not the case during the first installation.

[0072] The determination that the configuration request is associated with an initial installation can prompt the FDR server 118 to obtain the identity of the bus coupler 104 (i) that sent the configuration request and automatically request the configuration information (and optional network name) for the obtained identity from a pre-configured mapping of identities to configuration information stored in the data store 220. The identity can be automatically sent with the first configuration, or can be requested by the FDR server 118. The identity can be any unique identifier for configuring the original bus coupler 104 (i), which can be a descriptive network name or other identifier. The pre-configured mapping of identities to configuration mappings can be pre-configured, for example, during the manufacturing or system design phase. Communication between the FDR server and the bus coupler 104 (i) can be performed using DHCP transactions.

[0073] The FDR server 118 may also obtain a topology hash from the original bus coupler 104(i) and store the topology hash in a data store 220 mapped to the configuration information of the bus coupler 104(i). This mapping may be used by future replacement devices with the same topology hash. The topology hash of the replacement device may be used as a key to access the configuration information and (optionally) the network name for the replacement device.

[0074] Optionally, a specified network name (previously stored or newly entered) may be included in the configuration information and / or mapped to the topology hash. The network name of the bus coupler 104 is a name that can be used to identify or discover the bus coupler 104 to other devices (e.g., other bus couplers 104) connected to the network 120 or to a user. The network name may be a descriptive name that is meaningful to the user.

[0075] The mapping of the topological hash to the configuration information and identification and / or network name of the bus coupler may be performed within the firmware of the PLC 110, such as the firmware of the FDR server 118. For example, the firmware may be configured to request the identification and / or network name and the topological hash from the bus coupler 114(i) and then map this information together into the data store 220, which may be referenced later.

[0076] When it is determined that the configuration request is for configuration or reconfiguration, such as when the bus coupler 104(i) is a replacement device, the bus coupler 104(i) is installed in a particular sub-network 102 and replaces a previous bus coupler 104 installed in the sub-network 102, where the previous bus coupler 104 may be the original bus coupler 104 or a different replacement bus coupler. Upon receiving the configuration request, the FDR server 118 may perform a lookup in the device name map 222 using the topology hash specified in the configuration request to determine the configuration information corresponding to the topology hash from the configuration profile set 224. The FDR server 118 may then return the corresponding configuration information to the FDR control module 258 (e.g., using the network 140).

[0077] Once the configuration information is received, the FDR control module 258 may use the configuration information to configure, for example, but not limited to, the dedicated configuration information 260 and the network configuration information 262 on the bus coupler 104. In one embodiment, the FDR control module 258 is configured to perform a validation operation on the received configuration information before using the configuration information to configure the bus coupler 104. For example, the bus coupler 104 may store (e.g., in the memory 254) data specifying the device type of the bus coupler 104, and the FDR control module 258 may verify that the device type information specified in the received configuration information matches the device type stored on the bus coupler 104. As another example, the configuration information may specify the number and type information of the connected bus devices, and the FDR control module 258 may verify that the device type of the bus devices 106 in the sub-network 102 of the bus coupler matches the corresponding device type specified in the configuration information. However, more generally, any suitable form of validation operation may be performed, consistent with the functionality described herein.

[0078] Possible advantages include an improved rapid device replacement process that provides faster device replacement relative to conventional solutions and reduces or eliminates the need for manual user intervention during the replacement process. In addition, the IP addresses used by the entire network can be dynamic, and the bus device 106 does not need to store information about the bus coupler 104 in its sub-network and does not need to have the ability to communicate bidirectionally with the bus coupler. Instead, the bus device 106 only needs to be able to participate in the discovery phase of the replacement process in order to be discovered and identified.

[0079] It is worth noting that while the depicted embodiment illustrates a PLC device 110 connected to a bus coupler, which in turn manages a plurality of bus couplers 104, each of which can manage one or more bus devices 106, such an architecture is provided for illustrative purposes only and not for limitation. However, more generally, it is contemplated that the embodiments described herein can be implemented in any similar environment, with any computing device replacing the PLC device 110, the bus coupler 104, and the bus device 106.

[0080] Reference now Figure 3-5 , a flowchart showing an exemplary implementation of various exemplary embodiments is shown. Note that Figure 3-5 The order of the frames shown in the embodiment is not essential, so in principle, various frames may not be executed in the order shown or may be executed in parallel. In addition, some frames may be skipped, different frames may be added or replaced, or selected frames or frame groups may be executed in a separate application following the embodiments described herein.

[0081] Figure 3 A flow chart illustrating an example method performed by a bus coupler of a sub-network coupled to one or more sub-networks of an overall network 102 of an industrial network system, such as bus coupler 104 coupled to sub-network 102 of network 120, sub-network 102 being provided as Figure 1 The entire network of the industrial network system 100 is shown. At block 301, according to one or more embodiments, it is determined that a bus coupler needs to be configured.

[0082] At block 302, a local discovery process is performed for discovering and identifying bus devices included in a sub-network. The local discovery process may be limited to the sub-network and allow the bus coupler to discover and identify only bus devices in the sub-network.

[0083] At block 304, an IP address request is submitted across the network and outside the subnet. The IP address request assigns an IP address to the bus coupler. At block 306, an IP address for the bus coupler is received in response to the IP address assignment request.

[0084] At block 308, a configuration request for configuration information associated with a device name of the bus coupler is submitted across the network and outside the sub-network. The device name is based on an identification of the corresponding one or more bus devices obtained by the discovery process.

[0085] At block 310, configuration information is received in response to a configuration request. At block 312, at least one feature of the bus coupler is configured using the configuration information.

[0086] Figure 4 The figure shows an FDR server (eg Figure 1 Flowchart of an example method performed by the FDR server 218 of the industrial network system 100 shown in FIG. 401 , according to one or more embodiments, it is determined that a bus coupler needs to be configured or reconfigured.

[0087] At block 402, a configuration request is received from a bus coupler of a sub-network. The bus coupler may be equivalent in structure and function to Figure 1 The bus connector 104 of the sub-network 102 of the industrial network system 100 is shown. The configuration request is received outside the sub-network via the entire network connected to one or more sub-networks. The entire network can be equivalent to Figure 1 The network 120 is shown. The configuration request requests configuration information associated with a device name of the bus coupler, wherein the device name is based on an identification of the corresponding one or more bus devices obtained by a discovery process performed locally within the sub-network, the discovery process being used to discover and identify the corresponding one or more bus devices included in the sub-network.

[0088] At block 404, a map is accessed, wherein the map maps a device name of each bus coupler of the corresponding one or more sub-networks to configuration information of the bus coupler. The device name of each bus coupler is based on an identification of the corresponding one or more bus devices obtained by a previously performed discovery process, the discovery process being performed locally within the sub-network of the bus coupler to discover and identify the corresponding one or more bus devices included in the sub-network. At block 406, configuration information is provided in response to the configuration request.

[0089] Reference Figure 5 , refer to Figure 4 Blocks 401, 402, 404, and 406 are described. After executing blocks 401 and 502, it is determined at block 502 whether the bus coupler is initially installed. If it is determined that the bus coupler has been installed before, operations 404 and 406 are performed. If it is determined at block 502 that this is an initial installation, the method continues at block 504. At block 504, an identification of the bus coupler that sent the configuration request is obtained. At block 506, pre-configured configuration information (and optional network name) is requested for the identification. At block 508, the configuration information (and optional network name) is mapped to a device name.

[0090] In the above, reference is made to various embodiments. However, the scope of the present disclosure is not limited to the specifically described embodiments. On the contrary, any combination of the described features and elements, whether or not related to different embodiments, is considered to implement and practice the contemplated embodiments. In addition, although the embodiments may achieve advantages over other possible solutions or prior art, whether a given embodiment achieves a particular advantage does not limit the scope of the present disclosure. Therefore, the foregoing aspects, features, embodiments and advantages are merely illustrative and are not considered to be elements or limitations of the appended claims unless expressly stated in the claims.

[0091] Various embodiments disclosed herein may be implemented as systems, methods, or computer program products. Thus, various aspects may take the form of a fully hardware embodiment, a fully software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, which are generally referred to herein as "circuits," "modules," or "systems." Additionally, various aspects may take the form of a computer program product contained in one or more computer-readable media having computer-readable program code embodied thereon.

[0092] Any combination of one or more computer-readable media may be utilized. The computer-readable medium may be a non-transitory computer-readable medium. The non-transitory computer-readable medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared or semiconductor system, device or apparatus, or any suitable combination of the foregoing. More specific examples (non-exhaustive list) of non-transitory computer-readable media may include the following: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, fiber optic cable, RF, etc. , or any suitable combination of the foregoing.

[0093] Computer program code for performing the operations of various aspects of the present disclosure may be written in any combination of one or more programming languages. In addition, such computer program code may be executed using a single computer system or by multiple computer systems that communicate with each other (e.g., using a local area network (LAN), a wide area network (WAN), the Internet, etc.). Although various features are described above with reference to flowcharts and / or block diagrams, it will be understood by those of ordinary skill in the art that each block of the flowcharts and / or block diagrams and the combination of blocks in the flowcharts and / or block diagrams may be implemented by computer logic (e.g., computer program instructions, hardware logic, a combination of the two, etc.). Typically, computer program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device. In addition, executing such computer program instructions using a processor produces a machine that is capable of performing the functions or actions specified in the flowcharts and / or block diagram blocks.

[0094] The flow charts and block diagrams in the accompanying drawings illustrate the possible architectures, functions and / or operations of various embodiments of the present disclosure. In this regard, each frame in the flow chart or block diagram may represent a module, a code segment or a code portion, which includes one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions annotated in the frame may not appear in the order annotated in the figure. For example, the two frames shown in succession can actually be performed substantially simultaneously, or these frames can sometimes be performed in reverse order, depending on the functions involved. It will also be noted that each frame in the block diagram and / or flow chart illustration and the combination of frames in the block diagram and / or flow chart illustration can be implemented by a system based on dedicated hardware or a combination of dedicated hardware and computer instructions that performs a specified function or action.

[0095] It should be understood that the above description is intended to be illustrative rather than limiting. After reading and understanding the above description, many other implementation examples are apparent. Although the present disclosure describes specific examples, it should be appreciated that the systems and methods of the present disclosure are not limited to the examples described herein, but can be implemented by modification within the scope of the appended claims. Therefore, the description and drawings should be considered illustrative rather than restrictive. Therefore, the scope of the present disclosure should be determined with reference to the full scope of the appended claims and the equivalents of these claims.

Claims

1. A method performed by a bus coupler of a sub-network of one or more sub-networks, the sub-network being coupled to an overall network, the method comprising: Performing a local discovery process for discovering and identifying one or more bus devices included in the sub-network; submitting, by the bus coupler, an Internet Protocol (IP) address request across the entire network and external to the subnetwork to obtain an IP address for the bus coupler; In response to the IP address allocation request, receiving, by the bus coupler, an IP address of the bus coupler; submitting, by the bus coupler, via the entire network and external to the sub-network, a configuration request for configuration information associated with a device name of the bus coupler, wherein the device name is based on an identification of the corresponding one or more bus devices obtained through a discovery process; receiving the configuration information in response to the configuration request; and At least one characteristic of the bus coupler is configured using the configuration information. 2 . The method of claim 1 , further comprising computing a topological hash at the bus coupler by applying a hash function to identifications of the corresponding one or more bus devices, wherein the device name is based on the topological hash.

3. The method of claim 2, wherein the one or more bus devices comprises a plurality of bus devices, the method further comprising combining identifications of the corresponding plurality of bus devices, wherein the hash function is applied to the combining. 4 . The method according to claim 3 , wherein combining the identifications of the plurality of bus devices comprises concatenating the identifications of the corresponding plurality of bus devices in a predefined order.

5. The method according to claim 4, wherein the identifications of the corresponding multiple bus devices are spliced ​​based on the order in which the bus devices corresponding to the corresponding identifications are discovered, based on the topology of the sub-network, based on the information included in the corresponding identifications, and / or based on the connections between the discovered bus devices. The method of claim 1 , wherein the identification of the one or more bus devices comprises one or more business references.

7. The method of claim 1, wherein in response to the address request, a path to a server that services the configuration request is provided, and the configuration request is submitted using the path.

8. The method of claim 1 , wherein the configuration information is further associated with a network name of the bus connector, wherein the network name is a name used to identify the bus connector, and the network name is used by a network device located outside the sub-network that is connected to the entire network for network discovery requests and identification of the bus connector.

9. The method of claim 1, further comprising validating the configuration information, wherein once the configuration information is validated, the at least one feature of the bus coupler is configured.

10. The method of claim 1, wherein configuring at least one characteristic of the bus coupler further comprises: The bus coupler is configured with at least one of: (i) network connection information and (ii) application-specific configuration information.

11. The method according to claim 1 further includes determining, by the bus connector, that the bus connector needs to be configured or reconfigured, wherein in response to determining that the bus connector needs to be configured or reconfigured, the bus connector initiates a discovery process, submits the address request, and / or submits the configuration request.

12. A method comprising: receiving, by a fast device replacement (FDR) server via an entire network coupled to one or more sub-networks, a configuration request from a bus coupler of a sub-network of the one or more sub-networks, wherein the configuration request is provided external to the sub-network and requests configuration information associated with a device name of the bus coupler, wherein the device name is based on an identification of the corresponding one or more bus devices obtained by a local discovery process for discovering and identifying the corresponding one or more bus devices included in the sub-network; Accessing, by the FDR server, a mapping of a device name of each bus coupler of the corresponding one or more sub-networks to configuration information of the bus coupler, wherein the device name of each bus coupler is based on an identification of the corresponding one or more bus devices obtained by a previously performed discovery process, the discovery process being performed locally within the sub-network of the bus coupler for discovering and identifying the corresponding one or more bus devices included in the sub-network; and In response to a configuration request, the configuration information mapped to the device name in the configuration request is provided by the FDR server.

13. The method of claim 12, further comprising determining that the bus coupler requires configuration or reconfiguration, wherein in response to determining that the bus coupler requires configuration or reconfiguration, the FDR server accesses the mapping and provides the configuration response.

14. The method of claim 12, wherein the device name is based on a topological hash calculated at the bus coupler by applying a hash function to an identification of the corresponding one or more bus devices.

15. The method of claim 14, wherein the one or more bus devices comprises a plurality of bus devices, wherein the hash function is applied to a combination of identifications of the corresponding plurality of bus devices.

16. The method of claim 15, wherein the combination of the identifiers is to concatenate the identifiers in a predefined order, wherein the concatenation of the identifiers is based on the order in which bus devices corresponding to the corresponding identifiers are discovered, based on the topology of the sub-network, based on the information contained in the corresponding identifiers, and / or based on the discovered connections between the bus devices.

17. The method of claim 12, wherein the mapping further maps the device name to a network name of the bus connector, wherein the network name is a name used to identify the bus connector, and the network name is used by network devices located outside the sub-network that are connected to the entire network for network discovery requests and identification of the bus connector.

18. The method of claim 12, wherein the configuration information is usable by the bus coupler to configure at least one feature of the bus coupler, including at least one of (i) network connection information and (ii) application specific configuration information.

19. A bus coupler for connecting a sub-network to one or more sub-networks of a whole network, the bus coupler comprising: a memory configured to store instructions; and One or more processing devices arranged to communicate with the memory, wherein the one or more processing devices, when executing the instructions, are configured to: Performing a local discovery process for discovering and identifying one or more bus devices included in the sub-network; submitting an Internet Protocol (IP) address request across the entire network and external to the subnetwork to obtain an IP address for the bus coupler; In response to the IP address allocation request, receiving an IP address of the bus coupler; submitting, via the entire network and external to the sub-network, a configuration request for configuration information associated with a device name of a bus coupler, wherein the device name is based on an identification of the corresponding one or more bus devices obtained through a discovery process; receiving the configuration information in response to the configuration request; and At least one characteristic of the bus coupler is configured using the configuration information.

20. The bus coupler of claim 19, wherein the one or more bus devices comprises a plurality of bus devices, and the one or more processing devices when executing the instructions are further configured to: combining identifications of corresponding plurality of bus devices; and A hash function is applied to the combined identification, wherein the device name is based on the topological hash.

21. A fast device replacement (FDR) server, comprising: a memory configured to store instructions; and One or more processing devices arranged to communicate with the memory, wherein the one or more processing devices, when executing the instructions, are configured to: receiving, via an entire network coupled to the one or more sub-networks, a configuration request from a bus coupler of a sub-network of the one or more sub-networks, wherein the configuration request is provided external to the sub-network and the configuration request requests configuration information associated with a device name of the bus coupler, wherein the device name is based on an identification of the corresponding one or more bus devices obtained through a local discovery process for discovering and identifying the corresponding one or more bus devices included in the sub-network; accessing a mapping of a device name of each bus coupler of the corresponding one or more sub-networks to configuration information of the bus coupler, wherein the device name of each bus coupler is based on an identification of the corresponding one or more bus devices obtained by a previously performed discovery process, the discovery process being performed locally within the sub-network of the bus coupler for discovering and identifying the corresponding one or more bus devices included in the sub-network; and The configuration information is provided in response to the configuration request.

22. The FDR server of claim 21, wherein the one or more bus devices include a plurality of bus devices, and the device name is based on a topological hash calculated at a bus connector by applying a hash function to a combination of identifications of the corresponding plurality of bus devices.

23. An industrial network system, comprising: A bus connector for a sub-network of one or more sub-networks, the sub-network being connected to the entire network, the bus connector comprising: a memory configured to store instructions; and One or more processing devices arranged to communicate with the memory, wherein the one or more processing devices, when executing the instructions, are configured to: Performing a local discovery process for discovering and identifying one or more bus devices included in the sub-network; submitting an Internet Protocol (IP) address request across the entire network and external to the subnetwork to obtain an IP address for the bus coupler; In response to the IP address allocation request, receiving an IP address of the bus coupler; submitting, via the entire network and external to the sub-network, a configuration request for configuration information associated with a device name of a bus coupler, wherein the device name is based on an identification of the corresponding one or more bus devices obtained through a discovery process; receiving the configuration information in response to the configuration request; and Using the configuration information to configure at least one characteristic of the bus coupler Fast Device Replacement (FDR) server, including: A second memory configured to store a second instruction; and one or more second processing devices arranged to communicate with the second memory, wherein the one or more second processing devices, when executing the second instruction, are configured to: receiving a configuration request from a bus coupler via the entire network; accessing a mapping of a device name of each bus coupler of the corresponding one or more sub-networks to configuration information of the bus coupler, wherein the device name of each bus coupler is based on an identification of the corresponding one or more bus devices obtained by a previously performed discovery process, the discovery process being performed locally within the sub-network of the bus coupler for discovering and identifying the corresponding one or more bus devices included in the sub-network; and In response to the configuration request, configuration information mapped to the device name is provided in the configuration request.