Serial communication network with multiple branches

Abstract

The present disclosure relates to a serial communication network (300) comprising: a plurality of branches (302), wherein each branch (302) comprises a plurality of network nodes (304) which are interconnected in a daisy chain configuration and configured to communicate with each other according to a wired communication protocol for serial communication, wherein the plurality of network nodes (304) in a branch (302) are connected according to a linear daisy chain topology and configured for bidirectional communication, or wherein the plurality of network nodes (304) in a branch (302) are connected according to a ring daisy chain topology and configured for unidirectional communication; and a master control unit (310) which is common to the plurality of branches (302) and communicatively coupled with at least one network node (304, 306) of each branch (302) of the plurality of branches (302), wherein the network node (304) of at least one branch (302) is configured to support a plurality of physical modes of communication according to the wired communication protocol for serial communication.

Description

Technical Field

[0001] This disclosure generally relates to a serial communication network for wired communication, the serial communication network comprising multiple branches, each branch having multiple network nodes, wherein at least one node of each branch is communicatively coupled to a master control unit shared by the multiple branches. Background Technology

[0002] Typically, many applications rely on the interaction between interconnected devices that work together to provide a specific function. An example of such a system is the so-called "smart surface," a novel human-machine interface (HMI) particularly suitable for the automotive and industrial sectors. In a smart surface, hundreds of light-emitting diodes (LEDs) are controlled to dynamically and adaptively display information to the user, and sensors and actuators allow for the capture of user input and commands. In systems comprising many interconnected devices, communication protocols can regulate data transmission between devices, ensuring reliable communication and avoiding potential conflicts. Specifically, in systems including sensors, actuators, light-emitting devices, etc., data transmission between devices can be achieved via wired connections (e.g., via a single wire or via multiple wires), allowing connected devices to communicate according to wired communication protocols that define the rules for data transmission. Therefore, improvements in the architecture and communication strategies used for wired communication can be particularly significant for the further development of several technologies. Attached Figure Description

[0003] In the accompanying drawings, similar reference numerals in different views generally refer to the same parts. The drawings are not necessarily drawn to scale, but generally focus on illustrating the principles of the invention. In the following description, various aspects of the invention are described with reference to the following drawings, wherein:

[0004] Figure 1A and Figure 1B A system with a daisy-chain network topology is illustrated schematically according to various aspects;

[0005] Figure 2A The network nodes are illustrated in a schematic diagram according to various aspects;

[0006] Figure 2B An exemplary configuration of network nodes based on various aspects is illustrated schematically;

[0007] Figure 2C An exemplary configuration of the input / output ports of a network node is illustrated schematically according to various aspects;

[0008] Figure 2D An exemplary configuration of electrical wires connected to network nodes is shown schematically, according to various aspects.

[0009] Figure 3A A serial communication network for wired communication, including multiple branches, is illustrated schematically according to various aspects.

[0010] Figure 3B The main control unit of the serial communication network is shown in schematic form according to various aspects;

[0011] Figure 3C The diagram illustrates a local master node for a serial communication network from various perspectives.

[0012] Figure 3D A bridging node for a serial communication network is illustrated schematically, based on various aspects.

[0013] Figure 4A A schematic message flow diagram is shown, showing the relationships between branches, including the local master node, based on various aspects.

[0014] Figure 4B A schematic message flow diagram is shown, showing the association of branches, including bridging nodes, with respect to various aspects.

[0015] Figures 5A to 5D Exemplary configurations of branches for a serial communication network are illustrated schematically, according to various aspects; and

[0016] Figures 6A to 6C An exemplary configuration of a serial communication network according to various aspects is illustrated schematically. Detailed Implementation

[0017] The following detailed description is taken with reference to the accompanying drawings, which illustrate specific details and aspects in which the invention can be practiced. These aspects are described in sufficient detail to enable those skilled in the art to practice the invention. Other aspects may be utilized, and structural, logical, and electrical changes may be made, without departing from the scope of the invention. The aspects are not necessarily mutually exclusive, as some aspects may be combined with one or more other aspects to form new aspects. The aspects are described in conjunction with methods, and the aspects are described in conjunction with devices (e.g., serial communication networks, network nodes, communication circuits). However, it should be understood that the aspects described in conjunction with methods can be similarly applied to devices, and the aspects described in conjunction with devices can be similarly applied to methods.

[0018] Typically, networks of interconnected devices connected via wired links and communicating with each other according to wired communication protocols play a vital role in various applications, such as lighting systems and sensor systems. For example, emerging lighting applications in automotive environments require increasingly interconnected and individually controllable light sources. These sources need to be controlled with low latency and high precision under a wide range of operating conditions, particularly since temperature can cause significant changes in display color. Other applications, such as “smart surfaces,” require combining multiple LEDs (hundreds) along with sensor and / or actuator elements for the human-machine interface. In these applications, data is periodically sent and retrieved from LEDs and other nodes to provide a good user experience.

[0019] Against this backdrop, numerous communication protocols have been defined over the years to control data transmission between networked devices. Broadly speaking, communication protocols can be divided into two main categories: parallel or serial. Parallel interfaces allow the transmission of multiple bits in parallel, while serial interfaces operate at a lower data rate (e.g., transmitting one bit at a time). However, compared to parallel architectures, serial communication for wired networks can be implemented with simpler setups (e.g., using a single wire, or typically fewer wires compared to parallel communication) and at a lower cost. Therefore, serial communication can be particularly important for wired network systems involving a large number of interconnected devices.

[0020] Various options exist for serial network topologies, exemplarily for the physical and / or logical arrangement of nodes forming a communication network. A network topology can describe one or more available paths for signals to travel through a network of interconnected nodes. In this context, the term "network node" can describe an electronic device that is part of the network. Thus, a "network node" can be an electronic device that includes communication circuitry to enable communication with other electronic devices (other nodes) that are part of the network. A "network node" can also include any suitable circuitry that implements additional functions (e.g., for performing specific functions or operations). As an example, considering a network of lighting fixtures, a network node can include light-emitting circuitry configured to emit light. As another example, considering a network of sensor devices, a network node can include sensing circuitry configured to sense (or detect) specific physical quantities (such as temperature, light, mechanical vibration, etc.). "Network node" may also be simply referred to as a "node" herein. It should be understood that the various aspects relating to a "network node" described herein are applicable to the electronic device constituting that network node, and various aspects relating to the electronic device constituting a "network node" are applicable to that network node.

[0021] A simple topology is the so-called "point-to-point topology," where exactly two nodes are directly connected to each other (in other words, linked together). Another example could be a "star topology," where each peripheral network node is connected to the central network node via a separate transmission line. Another example could be a "bus topology," where network nodes are connected to a common transmission line (exemplarily, a common bus). In a "bus topology," several network nodes are connected on the same line, providing parallel connectivity between network nodes. Other examples could be "tree topologies" or "mesh topologies." A so-called "hybrid topology," combining two or more topology types, can also be provided.

[0022] In this context, a favorable network topology for interconnecting electronic devices is the so-called "daisy-chain topology" (see also...). Figure 1A and Figure 1B In a daisy-chain configuration, network nodes can be connected to form a series of nodes, wherein each network node can be connected to one or two other network nodes via a point-to-point connection, for example, to a previous node and / or a subsequent node in a serially connected node.

[0023] A daisy-chain topology can be linear, where the first node connects to the second, the second to the third, the third to the fourth, and so on, until the final node in the series is reached. Therefore, a linear configuration can be a bidirectional network configuration where each network node connects to the next node in the series (exemplarily, in a line or chain), and communication runs through the connected nodes in the series and then returns along the same path. In this configuration, the first and last nodes are not directly connected.

[0024] As another example, a "daisy-chain topology" can have a "ring configuration" such that the first node connects to the second node, the second node connects to the third node, the third node connects to the fourth node, and so on, with the final node in the series connecting back to the first node. The "ring configuration" can therefore define a loop-back network, where network nodes are connected in series, and the last node connects back to the first node, so communication runs in one direction through the sequence of nodes and then loops back to the first node. In a ring topology, the first and last nodes are interconnected, so each network node can connect to two other nodes.

[0025] A daisy-chain topology enables a cost-effective and scalable architecture for providing networks configured for serial communication. In particular, compared to other configurations, a daisy-chain topology can be implemented with fewer terminals and fewer connections, thus providing a cost- and resource-efficient implementation. In this disclosure, depending on the context, the reference to "daisy-chain" can be applied accordingly to both linear chain topologies and ring chain topologies.

[0026] Therefore, wired networks with daisy-chain topologies and based on serial communication are attractive for applications where space and cost are likely to be key considerations. Within this framework, improved communication strategies for such networks can lead to more cost-effective and resource-efficient operation, thereby facilitating the integration of such systems in a variety of application scenarios.

[0027] Typically, there are many communication protocols for managing wired serial communication. As is common to many communication protocols, wired serial communication can involve one network node acting as the "master node" and one or more other network nodes acting as "secondary nodes".

[0028] In this context, the term "primary" can be used to describe a network node configured to control the operation of other network nodes (exemplarily, corresponding electronic devices). Thus, a "primary node" can be configured to manage the transmission and reception of data in the network; for example, a "primary node" can be configured to transmit data to one or more other "secondary nodes" and can be configured to request data transmission from one or more other "secondary nodes." A "primary node" can be understood as a device configured to instruct the operation of one or more "secondary nodes" (e.g., provide instructions prompting the execution of one or more operations). The term "primary node" may also be referred to herein as a "master node," "controller node," "leader node," or "host node." In some aspects, a "primary node" may also be referred to herein as an electronic control unit (ECU). As an example, a "primary node" may include a microcontroller or any other suitable processing circuitry (e.g., a field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), etc.) to control other nodes, for example, to transmit instructions to other nodes.

[0029] The term "secondary node" can be used to describe a network node configured to be instructed by another network node, exemplarily, by a "master node". A "secondary node" can be a network node configured to receive instructions and respond to those instructions (e.g., not performing any active data transmission without prompting from the master node). In some aspects, a "secondary node" can be configured to transmit data (e.g., various types of information) at the request of the master node. A "secondary node" may also be referred to herein as a "slave node", "peripheral node", "follower node", or "responder node".

[0030] Typically, wired communication protocols for serial communication define a set of rules for controlling data transmission between network nodes. Therefore, wired communication protocols for serial communication can define the types of commands that can be sent / received, the response types to different commands, the timing of data transmission (e.g., synchronous or asynchronous), the communication layer, the encoding type of data transmission, etc. As is well known in the art, the type of node-to-node connection and the communication circuitry of the nodes can be adjusted according to the communication protocol on which the nodes are configured.

[0031] Examples of communication protocols used for wired serial communication may include an internal integrated circuit bus (I... 2 C) Agreements (e.g., pursuant to Article I of the Act of 1 October 2021) 2 C-bus specification and user manual version 7.0), Serial Peripheral Interface (SPI) protocol, 1-wire or one-wire protocol, Controller Area Network (CAN) protocol, Ethernet protocol and / or microwire protocol.

[0032] For example, there exists a range of known LED drivers that use various bus systems (primarily XX based on the CAN physical layer); however, these drivers only support a limited number of nodes (e.g., 100 to 200). Other exemplary LED drivers can be arranged in a serial chain and communicate via a unidirectional SPI-like bus. These nodes form a shift register-like structure, where data packets are pushed in until all units have received their data. However, this protocol only allows for a single function and lacks any diagnostic modes. Another protocol is the ISELED protocol for serial node chains, which supports more nodes (approximately 4000) but uses the same bus for all connections.

[0033] Recently, another communication protocol for wired serial communication, known as the Open Systems Protocol (OSP), has been defined. OSP can be used in various implementations and has broad applicability. In a common implementation, OSP can be used in the context of a single microprocessor (as the "master node") and multiple smart light-emitting diode (LED) devices (as "secondary nodes"). OSP defines system architectures, instruction sets, and data structures tailored to devices interconnected in a daisy-chain network topology, thus enabling robust and efficient data transmission in such networks.

[0034] This disclosure relates to a system architecture for a wired-based serial communication network. Specifically, the architecture proposed herein may include multiple daisy-chained network nodes organized into multiple independent branches coupled to a common master control unit. Exemplarily, the network described herein may include a master control unit communicatively coupled to a node (e.g., a master node or bridging node) in each branch to centrally control the operation of the branches in the network.

[0035] The configuration with multiple independent branches provides an architecture that can be easily scaled to include a large number of network nodes (e.g., up to one thousand nodes per branch). Compared to scenarios where all network nodes are connected in a single chain, having separate branches allows for lower latency control of network operation. Furthermore, the proposed architecture simplifies setup and installation (e.g., in terms of cabling), allowing for more localized node placement without the need for cabling to connect all nodes in a single chain. In some respects, the proposed architecture can support one thousand nodes in a branch with low latency and individual addressability. Moreover, the proposed architecture achieves ease of use, improved electromagnetic compatibility, and low integration effort (e.g., for installation in vehicles).

[0036] This disclosure describes a system comprising a plurality of individually controllable and readable nodes (e.g., LEDs, sensors, etc.) for applications such as ambient lighting and / or human-machine interfaces in motor vehicles. The proposed system includes a plurality of nodes that can be configured for bidirectional communication, thereby enabling time- and resource-efficient transmission of information within the network. Furthermore, the network nodes can be equipped with diagnostic capabilities, allowing for rapid response in the event of potential failures.

[0037] Common architectures typically employ parallel communication buses, such as Controller Area Network (CAN) and Controller Area Network Flexible Data Rate (CAN-FD). However, these buses cannot handle more than approximately 200 nodes. Standard protocols also incur significant overhead, reducing overall communication efficiency and increasing latency. Simpler protocols are fast but only operate in one direction and lack the necessary diagnostic capabilities. This disclosure relates to a lighting system that supports up to 1000 nodes per branch, features a fast update rate, and provides comprehensive diagnostic capabilities.

[0038] Depending on various aspects, the serial communication network includes multiple branches, each branch including: multiple network nodes (e.g., including a master node and multiple secondary nodes), wherein the multiple network nodes are interconnected in a daisy-chain configuration, wherein the multiple network nodes are configured to communicate with each other according to a wired communication protocol for serial communication, wherein the multiple network nodes are connected according to a linear daisy-chain topology and configured for bidirectional communication, or wherein the multiple network nodes are connected according to a ring daisy-chain topology and configured for unidirectional communication; and a master control unit shared by the multiple branches and communicatively coupled to at least one network node (e.g., a master node) of each of the multiple branches.

[0039] In the proposed configuration, the main control unit and the branch network nodes can communicate with each other bidirectionally. For example, the main control unit can send data to the network nodes, and the network nodes can send data to the main control unit. This configuration allows the main control unit to provide instructions for controlling the behavior of the network nodes in the branch, and also allows the main control unit to receive information about the network nodes in the branch. For example, the network nodes can send diagnostic information to the main control unit, such as diagnostic information representing the temperature at the branch, the voltage at the branch, faults in the nodes, etc. Therefore, the main control unit can receive updated information about potential emergencies in the branch and take appropriate corrective actions, such as interrupting the voltage supply to the branch or its nodes, sending alarms to users, etc.

[0040] In a preferred configuration, network nodes in a branch (e.g., at least one branch, or each branch) can be configured to support multiple physical modes for wired communication. In this context, the term "physical mode" is used herein in the sense commonly understood in the art to describe the physical manner in which signals are transmitted from one network node to another. Exemplarily, a "physical mode" can describe how a network node utilizes the physical layer to communicate with another network node. Therefore, a "physical mode" can include transmission parameters related to the physical transmission of signals. Configurations in which network nodes are configured to enable multiple physical modes enhance layout flexibility, for example, allowing for the customization of a specific physical mode used at a particular location in the chain by considering system factors (e.g.,, as an example, a particular location in a host device where a particular wiring or voltage value is more suitable).

[0041] In a preferred configuration, network nodes can be configured to communicate with each other according to an Open Systems Protocol (OSP), such as OSIRE® E3731i - Open Systems Protocol 1.0, Application Guide AN162, July 6, 2023. The OSP protocol is particularly well-suited for managing communication in daisy-chain networks (e.g., in a daisy chain of light-emitting elements) and therefore constitutes the most relevant use case for the proposed readout strategy. Using the OSP protocol facilitates the provision of complex lighting systems, such as those in vehicles.

[0042] Therefore, in this disclosure, specific reference may be made to serial communication networks in which network nodes are configured to communicate with each other according to Open Systems Protocol (OSP). Concepts and terminology relating to OSP may be used hereinafter. However, it should be understood that the various aspects described herein can be broadly applied to other types of wired communication protocols for serial communication. Furthermore, some examples may relate to specific wired communication protocols (e.g., specific versions or releases of a wired communication protocol), but it should be understood that the examples provided herein can be similarly applied to various other wired communication protocols or other versions / releases of wired communication protocols, whether existing or not yet established.

[0043] Furthermore, in a preferred configuration, network nodes in a serial communication network (e.g., at least one branch, such as each branch) may include one or more light-emitting elements (e.g., one or more light-emitting diodes (LEDs)). Exemplarily, the proposed architecture can be particularly advantageous for nodes in a daisy chain of RGB LEDs for efficient operation. This arrangement can, for example, provide “smart surfaces” for (e.g., in vehicles). However, it should be understood that the configuration proposed herein can be applied to any suitable type of network node, for example, to network nodes configured to perform any suitable function.

[0044] In a preferred configuration, the multi-branch network configured as described herein can be used in vehicles, for example, to provide ambient lighting inside the vehicle, lighting outside the vehicle, smart surfaces, etc. The vehicle can be a motor vehicle (particularly a car) or other types of motor vehicles (e.g., motorcycles, trucks, vans, etc.). In some aspects, the vehicle may include one or more multi-branch networks configured as described herein. The proposed architecture enables the individual control of a large number of nodes, thereby enhancing the system's flexibility, which is particularly important for ambient lighting in motor vehicles. For example, a large number of individually addressable LED nodes with low latency enable smooth animation. As another example, rapid feedback from sensors or rapid response in error conditions is ensured through bidirectional communication.

[0045] However, it should be understood that the multi-branch network proposed in this paper can also be used for other types of applications. As another example, the multi-branch network can be used in (smart) homes, for example, to provide ambient lighting in rooms or buildings, or to provide distributed monitoring of the environment (e.g., temperature) and adaptive adjustment of lighting based on the environment.

[0046] Figure 1A and Figure 1B A network 100 is illustrated schematically according to various aspects, comprising multiple network nodes arranged in a daisy-chain topology. Typically, network 100 may include multiple network nodes 102 arranged in a daisy-chain configuration. Exemplarily, network nodes 102 may be connected to form a series of network nodes, such that each network node 102 is connected to one or two other network nodes 102, and data transmission within the network may include data propagating from one network node 102 in the chain to the next node. In this respect, network 100 may have a “linear” daisy-chain topology (e.g., ...). Figure 1A Configuration 100a is shown in the figure) or a "ring" daisy chain topology (as shown in the figure). Figure 1B (As shown in configuration 100b).

[0047] According to a “linear” daisy-chain topology, the first node 104 can be connected to the second node 106a, the second node 106a can be connected to the third node 106b, and so on, until the last node 106d is reached. As mentioned above, in this configuration, the last node 106d and the first node 104 are not directly connected, and communication between the nodes can be bidirectional, allowing information to flow from the first node 104 to the last node 106d, and from the last node 106d to the first node 104.

[0048] According to a "ring" daisy-chain topology, the first node 104 can be connected to the second node 106a, the second node 106a can be connected to the third node 106b, and so on, until the last node 106d is reached. As mentioned above, in this configuration, the last node 106d and the first node 104 can be directly connected, providing a loop arrangement. In this configuration, communication between nodes can be unidirectional, allowing information to flow from the first node 104 to the last node 106d, and then the information loops back from the last node 106d to the first node 104.

[0049] Networks with linear daisy-chain topology and serial communication networks with ring daisy-chain topology can be collectively referred to as networks. Figure 1A and Figure 1B The exemplary configuration shown in the figure illustrates a network 100 with five nodes 102, but it should be understood that network 100 may include any suitable number of nodes.

[0050] Depending on various aspects, network node 102 may include a master node 104 and one or more slave nodes 106a-106d (exemplarily, master node 104 and one or more secondary nodes 106a-106d), for example, multiple secondary nodes 106a-106d. As previously described, master node 104 may manage communication within network 100. For example, master node 104 may include control circuitry 108 configured to control communication within network 100 (e.g., configured to control data transmission on a daisy chain of network node 102). Exemplarily, control circuitry 108 may be configured to transmit messages along the chain of secondary nodes 106a-106d and prompt one or more secondary nodes 106a-106d to respond. Master node 104 may also include communication circuitry 112 to send data to / receive data from the chain of secondary nodes 106a-106d. As an exemplary implementation, master node 104 may be a microcontroller or include a microcontroller, such as a microcontroller unit (MCU). In some aspects, master node 104 may be the only node within network 100. In some aspects, master node 104 may also be connected to a backbone network.

[0051] Typically, each network node 102 may have a corresponding address associated with it. The node's "address" can be a unique identifier for that node 102 and allows messages to be passed to that node 102. For example, a message propagating along a chain of nodes 102 may include an address field that includes the address of the node 102 to which the message is addressed. Upon receiving a message, node 102 can compare the message's address field with its own address, and if the message addresses that node 102, it executes the instructions contained in the message; if the message addresses another node 102, it propagates the message further along the chain.

[0052] Depending on various aspects, each network node 102 can know its corresponding position in the sequence of network nodes 102. Referring to secondary nodes 106a-106d, secondary node 106a connected to primary node 104 can be the initial node of the sequence of secondary nodes, secondary node 106d can be the final node of the sequence of secondary nodes (exemplarily, line termination node EOL), and other secondary nodes 106b, 106c can be intermediate nodes between the initial node and the final node. Each secondary node 106a-106d can know its position in the sequence, for example, at position one, two, three, etc., up to the final position.

[0053] Depending on the circumstances, adjacent network nodes 102 may be interconnected via wired connection 110. In this regard, the terms "adjacent" or "nearby" may be used to describe network nodes 102 that are in consecutive positions within the sequence of network nodes 102 (exemplarily, logically adjacent network nodes 102), without implying a spatial relationship between network nodes 102. Within this framework, considering a node 102 as a reference point, the terms "next" or "following" may be used to describe another node 102 that is adjacent to the reference node and located downstream along the chain relative to the data transmission direction. Thus, a message can propagate from the reference node to the next node, then to another next node, and so on. Correspondingly, the terms "previous" or "previously" may be used to describe another node 102 that is adjacent to the reference node and located upstream along the chain relative to the data transmission direction. Thus, data can propagate from the previous node to the reference node.

[0054] Wired connection 110 may include one or more wires that electrically connect one network node 102 to one or more adjacent network nodes 102. Exemplarily, wired connection 110 may include one or more conductive lines (e.g., conductive wires or conductive traces). Exemplarily, wired connection 110 may be a serial bus to which network nodes 102 are connected in a chain. The number of conductive lines in wired connection 110 may be adjusted according to the communication protocol used by the network nodes 102 for communication. In a preferred configuration, wired connection 110 between adjacent nodes 102 may include exactly two conductive lines. A configuration with two conductive lines allows for the implementation of the OSP protocol and is therefore particularly suitable for data transmission in a daisy-chain network 100. However, it should be understood that wired connection 110 may typically include any suitable number of conductive lines, such as one, two, three, four, etc. In some aspects, wired connection 110 may include up to four conductive lines.

[0055] Depending on various aspects, network node 102 can be configured to communicate with each other according to a wired communication protocol used for serial communication (referred to herein as the underlying communication protocol). For example, network node 102 can be configured to transmit data along a chain of nodes according to rules and parameters defined by the wired communication protocol.

[0056] As previously mentioned, in a preferred configuration, network nodes 102 can be configured to communicate with each other according to an Open Systems Protocol (OSP), because such a specific protocol enables robust communication in daisy-chain networks (particularly for optical transmitters). However, it should be understood that the aspects described herein can be broadly applied to the configuration of network nodes 102 communicating according to another type of wired communication protocol used for serial communication.

[0057] Generally, the details of Open Systems Protocol (OSP) are known in the art. This document provides a brief overview to introduce aspects relevant to this disclosure. The OSP protocol may include a five-layer architecture: the application software layer, the application-specific protocol layer, the network layer, the data link layer (DLL), and the physical layer (PHY). The network layer may define the instruction conventions used to interpret data. The DLL may describe the frame format and encoding of messages according to the OSP protocol. Messages may also be referred to as "telegrams." The PHY layer may control the actual transmission across the physical medium (exemplarily, communication via a wired connection).

[0058] The OSP protocol can include various physical modes, exemplarily various communication modes, namely Low Voltage Differential Signaling (LVDS) mode, Line-Terminal (EOL) mode or Microcontroller (MCU) mode, One-Way Single-Ended (USE) mode, which can also be called CAN mode (where CAN is an abbreviation for Controller Area Network). Considering the configuration of network nodes communicating according to the OSP protocol, aspects of this disclosure can be applied to each possible communication mode. In the OSP protocol, communication is message-based, and messages can have a frame format. A frame can include different fields, namely a preamble, address, Payload Size Indicator (PSI), instruction, payload, and Cyclic Redundancy Check (CRC). The fields of a frame can have different lengths (in bits), and the message length can be variable (e.g., up to 12 bytes). For example, the preamble can be 4 bits long. The address can be 10 bits long and can indicate the address of the target node addressed by the message. The PSI can be 3 bits long and can indicate the length of the payload in bytes. The instruction can be 7 bits long and can be device-specific. The payload can have a variable length of 0 to 64 bits, as indicated by the PSI. CRC can be 8 bits long and can be included in the checksum calculated on the complete message excluding the CRC field. In this article, the message "field" may also be referred to as the message "part".

[0059] According to the OSP protocol, the master node can identify the device type of each node in the chain. In this regard, each node can have its own read-only identifier (e.g., 32 bits long). This read-only identifier can include information representing the node / device, such as device type (e.g., light-emitting circuit, sensor, etc.), manufacturer, component identifier, and component version.

[0060] Figure 2A The network node 200 is illustrated schematically according to various aspects. For example, Figure 2A An electronic device configured to function as a network node in a serial communication network is shown. Therefore, network node 200 can be a configuration of network node 102 of network 100 (e.g., secondary nodes 106a-106d). It should be understood that the representation of network node 200 can be simplified for illustrative purposes, and network node 200 (electronic device) may include additional components relative to the illustrated components. In this document, "electronic device" may also be referred to as an electronic module.

[0061] Typically, network node 200 may include communication circuitry 202 configured to enable network node 200 to communicatively couple with another electronic device (exemplarily, with another network node). Communication circuitry 202 may be configured to control the voltage level at a wired connection between network node 200 and the other network node to encode data in voltage level modulation. Communication circuitry 202 may include communication hardware 238 and processor 240. Processor 240 may be configured to control communication hardware 238 to implement communication at the physical layer, for example, to control / define the voltage level at the wired connection. Processor 240 may also be configured to interpret (e.g., decode) messages received at network node 200 and generate appropriate response messages to be transmitted using communication hardware 238. Where appropriate, the configuration of communication circuitry 202 of network node 200 referred to herein may accordingly refer to the configuration of communication hardware 238 (physical layer) and / or processor 240 (logical layer). As an exemplary implementation, processor 240 may be a microprocessor. For example, the communication circuit 202 may be an integrated circuit (IC) configured to enable communication to / from network node 200.

[0062] Communication circuit 202 can be configured to receive, interpret, and send messages according to a wired communication protocol (e.g., OSP protocol). In some aspects, communication circuit 202 can be configured to detect communication errors, such as identifying errors along the chain. For example, communication circuit 202 can be configured to perform communication diagnostics, such as identifying possible communication problems (e.g., incomplete messages, missing addresses, etc.) by interpreting received messages or parts of received messages.

[0063] In some respects, a first voltage level (e.g., a high voltage level) at a wired connection can be associated with logic "1", and a second voltage level (e.g., a low voltage level) at a wired connection can be associated with logic "0". However, it should be understood that the definitions of logic "1" and logic "0", and the type of signal modulation associated with them, can be arbitrary (e.g., other examples of modulation may include signal amplitude, signal frequency, signal period, etc.). A high voltage level can be understood as a signal with a voltage higher than a voltage threshold. A low voltage level can be understood as a signal with a voltage lower than a voltage threshold. As a numerical example only, a high voltage level can be 1V, and a low voltage level can be 0V. Considering the configuration according to the OSP protocol, network node 200 can support logic levels of 3.3V and 5V.

[0064] As an exemplary implementation, communication circuitry 202 may include (as part of communication hardware 238) one or more switching elements (e.g., one or more transistors) to selectively connect or disconnect the conductive path between the wired connection and ground, and / or selectively connect or disconnect the conductive path between the wired connection and the supply voltage. Processor 240 may be configured to control one or more switching elements to define the voltage level at the wired connection.

[0065] Depending on various aspects, network node 200 may include multiple input / output ports 206, 208, and communication circuitry 202 may be coupled to input / output ports 206, 208. In operation, network node 200 may receive data via first input / output ports 206, 208 and output data via second input / output ports 206, 208. The direction of data propagation may vary based on the daisy-chain network configuration and the node to which the data is addressed. Exemplarily, each input / output port 206, 208 may be configured to be coupled to a wired connection (e.g., to one or more conductive wires), and communication circuitry 202 may be coupled to the wired connection via input / output ports 206, 208. Exemplary configurations of input / output ports 206, 208 will be provided in [the document / details]. Figure 2C As described in the text.

[0066] Network node 200 may also include functional circuitry 204 configured to implement the primary functions of network node 200. Exemplarily, network node 200 may typically be designed to perform some operation, and communication circuitry 202 may allow network node 200 to interconnect with other network nodes to collaborate with other devices to utilize its operation. In some aspects, network node 200 may also exclude any functional circuitry 204 and include only communication circuitry 202 to enable message propagation within a chain of nodes.

[0067] In some aspects, the communication circuit 202 and the functional circuit 204 can be integrated on the same substrate, such as on the same printed circuit board. For example, the network node 200 can be a monolithic device in which the communication circuit 202 and the functional circuit 204 are integrated (e.g., within a housing).

[0068] Depending on the intended use of network node 200, functional circuitry 204 can have any suitable configuration and include any suitable components. In a preferred configuration, such as... Figure 2BAs shown, network node 200b may include (as functional circuit 204b) a light-emitting circuit, such as driver circuit 210 and one or more light-emitting elements 212. Driver circuit 210 may be configured to control the light emission of one or more light-emitting elements 212. Driver circuit 210 may be configured to implement any suitable driving scheme, such as current dimming, pulse width modulation (PWM), PWM dimming, pulse duration modulation (PDM), etc.

[0069] In principle, the light-emitting element 212 can be of any suitable type. In the context of integrated circuits, the light-emitting element can be a light-emitting diode or includes a light-emitting diode (LED) (e.g., one or more light-emitting elements 212 may include at least one LED). As another example, the light-emitting element 212 can be a laser diode or includes a laser diode, such as an edge-emitting laser diode or a vertical-cavity surface-emitting laser diode.

[0070] The light-emitting element 212 (e.g., an LED) can be configured to emit light with a predefined wavelength, such as the visible light range (e.g., about 380 nm to about 700 nm), the infrared and / or near-infrared range (e.g., about 700 nm to about 5000 nm), or the ultraviolet range (e.g., about 100 nm to about 400 nm). In some aspects, the light-emitting element 212 can be configured to emit light in different wavelength ranges. For example, the first light-emitting element 212 can be configured to emit light in a first wavelength range (e.g., a first color, such as blue), the second light-emitting element 212 can be configured to emit light in a second wavelength range (e.g., a second color, such as red), and the third light-emitting element 212 can be configured to emit light in a third wavelength range (e.g., a third color, such as green), etc.

[0071] It should be understood that, in other respects, electronic devices used as nodes in a daisy-chain network may include different types of functional circuitry 204. As another example, network node 200 may include (as functional circuitry 204) sensor circuitry configured to sense physical quantities such as temperature, humidity, light, vibration, force, touch, etc. In this configuration, functional circuitry 204 may also include a sensor controller to control the operation of the sensing circuitry, such as prompting the execution of sensing measurements, collecting data, etc. For example, the sensing circuitry may include a transimpedance amplifier and an analog-to-digital converter to convert analog measurements into digital representations. In some aspects, the sensing circuitry may include a buffer (e.g., a register) to temporarily store sensor data until the sensor data is requested / retrieved, for example, via the network's master node or master control circuitry.

[0072] Functional circuit 204 can be communicatively coupled to communication circuit 202. Therefore, communication circuit 202 (e.g., processor 240) can be configured to transmit instructions (instructions received from the network's master node) to functional circuit 204 and / or receive information from functional circuit 204. For example, communication circuit 202 can receive status information from functional circuit 204, such as representations of operating parameters, representations of the current operating state (e.g., active, idle), results of sensing processes, etc.

[0073] Depending on various aspects, network node 200 may also include a memory (not shown). This memory can be configured to store data and instructions for the operation of network node 200. For example, the memory can be configured to store communication parameters for communication circuit 202 to communicate via a wired connection. As another example, the memory can be configured to store instructions for operating functional circuit 204. As yet another example, the memory can be configured to store production-related data, such as calibration data (e.g., optical calibration data in the case of a light-emitting node). Data in the memory can be transmitted by network node 200 upon request (e.g., when the network's master node or master control unit receives a corresponding request).

[0074] Depending on various aspects, network node 200 may also include diagnostic circuitry configured to sense one or more operating parameters of network node 200 and determine the occurrence of potential fault conditions of network node 200. For example, the diagnostic circuitry may be part of integrated circuit 202. For instance, the diagnostic circuitry may include a temperature sensor configured to sense the temperature of network node 200 and generate an alarm signal in overheating conditions, such as when the sensed temperature is within a predefined alarm range (e.g., when the sensed temperature is greater than a predefined threshold temperature). As another example, the diagnostic circuitry may include a voltage sensor configured to sense the voltage at network node 200 and generate an alarm signal in overvoltage conditions, such as when the sensed voltage is within a predefined alarm range (e.g., when the sensed voltage is greater than a predefined threshold voltage).

[0075] Figure 2CAn exemplary configuration of input / output ports 206c and 208c of network node 200 is shown. Depending on various aspects, network node 200 may include two identical input / output ports 206c and 208c, each port including two input / output pins 214, 216, 218, and 220. This configuration can provide communication according to the OSP protocol or according to other protocols using input / output ports with two input / output pins. However, it should be understood that, in other aspects, input / output ports 206 and 208 of network node 200 may have different configurations depending on the specific communication protocol used.

[0076] Two configurations are available. The first configuration 200c-1 provides symmetrical alignment, where the first input / output pin 214 of the first input / output port 206c can be coupled to the corresponding first input / output pin 218 of the second input / output port 208c, and the second input / output pin 216 of the first input / output port 206c can be coupled to the corresponding second input / output pin 220 of the second input / output port 208c. This symmetrical configuration can be provided considering OSP protocols, for example, when implementing inter-node connections via LVDS.

[0077] The second configuration 200c-2 can provide cross alignment, wherein the first input / output pin 214 of the first input / output port 206c can be coupled to the second input / output pin 220 of the second input / output port 208c, and the second input / output pin 216 of the first input / output port 206c can be coupled to the first input / output pin 218 of the second input / output port 208c. Considering the OSP protocol, for example, when inter-node connections are implemented via USE mode (or CAN mode), a cross configuration can be provided.

[0078] Figure 2D An exemplary configuration for connecting network node 200d to conductive lines 222, 224, 226, and 228 is shown. As shown, a first input / output pin 214 of a first input / output port can be connected to a first conductive line 222, a second input / output pin 216 of a first input / output port can be connected to a second conductive line 224, a first input / output pin 218 of a second input / output port can be connected to a third conductive line 226, and a second input / output pin 220 of a second input / output port can be connected to a fourth conductive line 228.

[0079] The conductive lines 222, 224, 226, and 228 associated with each of pins 214, 216, 218, and 220 can be connected to pull-up or pull-down resistors, as shown in 230, where the first transmission line 222 is connected to the pull-up resistor and the second transmission line 224 is connected to the pull-down resistor, and as shown in 232, where the third transmission line 226 is connected to the pull-up resistor and the fourth transmission line 228 is connected to the pull-down resistor. This configuration is, of course, given for illustrative purposes, and the polarity of the pins and corresponding lines can be reversed as needed in a given embodiment. The resistance values ​​of the various pull-up and pull-down resistors depend at least on the type of signal encoding used, the magnitude of the supply voltage, and the voltage range used for signal transmission. As a numerical example only, the pull-up and pull-down resistors can each be approximately 10 kΩ. This resistor can couple conductive lines 222, 224, 226, 228 to a power supply voltage 234 (exemplarily, to a power supply terminal configured to be coupled to a power supply) and / or to ground 236 (exemplarily, to a ground terminal), thereby enabling modulation of the voltage level at conductive lines 222, 224, 226, 228.

[0080] As described above, various aspects of this disclosure may relate to an architecture comprising multiple branches. In this respect, each branch may generally be as follows: Figure 1A or Figure 1B The network is configured as in network 100. For example, each branch can be a sub-network of the architecture, such as a sub-network dedicated to a specific function or associated with a specific location within the host device. Various sub-networks can be communicatively coupled to a master control unit that acts as a central command point for multiple sub-networks, thereby coordinating the behavior of the branches and ensuring efficient and structured operation.

[0081] The proposed architecture can include subnetworks with identical configurations, such as subnetworks with either a linear daisy-chain topology or a ring daisy-chain topology. Alternatively, the proposed architecture can include subnetworks with different topologies; for example, one subnetwork may have a linear daisy-chain topology while another subnetwork may have a ring daisy-chain topology. This architectural flexibility facilitates its integration into complex systems, such as vehicles.

[0082] The general aspects of the proposed architecture will combine Figures 3A to 3D This will be described. Different scenarios of data transmission to branches and from branches will be combined. Figure 4A and Figure 4B The discussion will proceed. Possible configurations for each branch will be combined. Figures 5A to 6C Let's have a discussion.

[0083] Figure 3AA serial communication network 300 as proposed herein is illustrated. The serial communication network 300 may include multiple branches 302 and a master control unit 310 shared by the multiple branches 302. In the exemplary configuration of FIG3, the serial communication network 300 may include a first branch 302-1, a second branch 302-2, and an Nth branch 302-N. Typically, the serial communication network 300 may include any suitable number of branches 302, such as two, three, four, five, ten, or more than ten. The serial communication network 300 may also be simply referred to herein as network 300. A branch (e.g., branch 302) may also be referred to herein as a subnetwork or a portion of the network.

[0084] Network 300 can be used in any suitable host device, where branches 302 are located in different positions within the host device or used to perform different functions within the host device. In a preferred configuration, network 300 can be used in a vehicle (e.g., an automobile) to provide, for example, ambient lighting, smart surfaces, signaling functions, etc. Depending on various aspects, a vehicle (e.g., an automobile) may include one or more networks 300. In this scenario, the main control unit 310 may be the central control unit of the vehicle, while the branches 302 may be arranged in different parts of the vehicle, such as in the doors, the interior of the vehicle (e.g., for ambient lighting), the dashboard, the exterior of the vehicle (e.g., for external signals), etc. It should be understood that use in a vehicle is likely the most relevant use case for the proposed architecture, but network 300 can, in principle, be integrated into other types of systems or devices.

[0085] The configuration of branch 302 will be Figures 5A to 6C This will be discussed in further detail. In short, branch 302 may include multiple network nodes 304. The network nodes 304 in branch 302 are configured in a daisy chain (in other words, in a daisy chain topology), for example, a linear daisy chain configuration / topology (such as...). Figure 1A (in the middle) or circular daisy chain configuration / topology (such as...) Figure 1B (The branches 302) are interconnected. In a simple configuration, all branches 302 can have the same daisy-chain topology; for example, all branches 302 can have a linear daisy-chain topology, or all branches 302 can have a circular daisy-chain topology. In other aspects, to customize the architecture according to specific system conditions, branches 302 can have different daisy-chain topologies. In such other scenarios, at least one branch 302 (e.g., the first branch 302-1, or the first plurality of branches) can have a linear daisy-chain topology, and at least one other branch 302 (e.g., the second branch 302-2, or the second plurality of branches) can have a circular daisy-chain topology.

[0086] The network node 304 of branch 302 may include a network node 306 that interfaces branch 302 with main control unit 310, and a plurality of secondary nodes 308. Exemplarily, main control unit 310 is communicatively coupled to at least one network node 306 of each branch 302. In this disclosure, the network node in branch 302 that is communicatively coupled to main control unit 310 may be referred to as an "interface node," "coupled node," or "input / output node."

[0087] In the configuration of Figure 3, the interface node 306, which is communicatively coupled to the main control unit 310, is shown as the first or initial node of the chain in branch 302. However, it should be understood that, in principle, the interface node 306 can be positioned anywhere suitable within the daisy chain. Various possible configurations of the interface node 306 can be provided, such as as a local master node or as a bridging node, which will... Figure 3C and Figure 3D We will discuss this in further detail later.

[0088] In each branch 302, network nodes 304 are configured to communicate with each other according to a wired communication protocol for serial communication. Therefore, branch 302 may include a wired connection 312 between nodes 304. The wired connection 312 may include one or more conductive lines (e.g., multiple conductive lines) that couple two network nodes 304 to each other. For example, the wired connection 312 may include exactly two conductive lines. Each network node 304 may include communication circuitry 314 configured to perform wired communication via the wired connection 312 coupled to the node 304, for example, as... Figure 2D As discussed in the article.

[0089] As described above, in the preferred configuration, the network nodes 304 in branch 302 can be configured to communicate with each other according to the OSP protocol, but the aspects discussed regarding network 300 can be broadly applied to other wired communication protocols for serial communication. In the preferred configuration, the network nodes 304 in each branch 302 can therefore be configured to communicate with each other according to the OSP protocol. In other possible configurations, the network nodes 304 in different branches 302 can communicate according to different wired communication protocols for serial communication.

[0090] Furthermore, in a preferred configuration, at least one branch 302 may include a branch configured to be Figure 2B Network node 304 (e.g., secondary node 308) of network node 200b, for example, branch 302 may include a node having driver circuitry and one or more light-emitting elements (e.g., one or more LEDs). However, it should be understood that the aspects discussed regarding “network 300” can be broadly applied to other types of nodes (e.g., sensors, actuators, etc.).

[0091] For example, at least one branch 302 (e.g., a first branch 302-1, or a first plurality of branches) may include a plurality of light-emitting nodes as network nodes 304 (e.g., as secondary nodes 308). Another branch 302 (e.g., a second branch 302-2, or a second plurality of branches) may include a plurality of sensor nodes as network nodes 304. Yet another branch 302 (e.g., an Nth branch 302-N, or a third plurality of branches) may include a plurality of actuator nodes as network nodes 304, and so on. It should be understood that a “hybrid configuration” may also be provided, wherein branches 302 include different types of network nodes, exemplarily including network nodes configured to perform different functions. For example, a branch 302 may include one or more light-emitting nodes and one or more sensor nodes, or, as another example, a branch 302 may include one or more sensor nodes and one or more actuator nodes.

[0092] The proposed architecture enables the management of a large number of nodes 304 within each branch 302. The specific number of nodes 304 in each branch 302 can then be freely adapted to system requirements. Typically, a branch 302 can include 2 to 1000 network nodes 304, for example, 10 to 700 network nodes 304, or even 50 to 500 network nodes 304. In some aspects, a branch 302 can include more than 500 network nodes 304, for example, more than 700 network nodes 304, for example, more than 900 network nodes 304, or even 1000 network nodes 304.

[0093] In the proposed architecture, the main control unit 310 can act as a central coordinator for operating branches 302, thereby enabling the network nodes 304 in each branch 302 to operate in a coordinated and efficient manner. The main control unit 310 may include processing circuitry configured to receive information (data) from each branch 302, process the received information, and control the network nodes 304 of the branch 302 accordingly. In this document, the main control unit 310 may also be referred to as a main processor, central control unit, branch control unit (BCU), or simply control circuitry. Considering its installation in a vehicle, the main control unit 310 may also be referred to as a vehicle control unit.

[0094] In the proposed architecture, bidirectional communication is possible between the main control unit 310 and each branch 302. For example, the main control unit 310 and the corresponding interface nodes 306 of the branches 302 that are communicatively coupled to the main control unit 310 can be configured to perform bidirectional communication with each other; in other words, they can be configured to communicate with each other in a bidirectional manner. Therefore, the interface node 306 of each branch 302 can be configured to receive data from the main control unit 310 and transmit (in other words, send) data to the main control unit 310.

[0095] The corresponding interface nodes 306 of the main control unit 310 and the branch 302 can be communicatively coupled to each other via a wired connection 316. In some aspects, the wired connection 316 coupling the branch 302 to the main control unit 310 can be of a different type than the wired connection 312 within the branch 302. This configuration takes into account the fact that the main control unit 310 can be configured to perform multiple functions within a host device (e.g., in a vehicle), and therefore can be configured to communicate according to a wired communication protocol different from the wired communication protocol used within the branch 302.

[0096] In other words, considering branch 302, network nodes 304 in branch 302 can be configured to communicate with each other according to a first serial communication protocol for wired communication, and interface nodes 306 in branch 302 can be configured to communicate with the main control unit 310 according to a second serial communication protocol for wired communication. The first serial communication protocol may be different from the second serial communication protocol. As an example, the first serial communication protocol may be OSP. As an example, the second serial communication protocol may be one of the following: CAN protocol, Local Interconnect Network (LIN) protocol, Ethernet protocol, etc.

[0097] Accordingly, considering branch 302, the wired connection 312 between nodes 304 within branch 302 can be configured to support a first serial communication protocol, and the wired connection 316 between interface node 306 of branch 302 and main control unit 310 can be configured to support a second serial communication protocol. Therefore, the wired connection 312 within branch 302 can differ from the wired connection 316 between branch 302 and main control unit 310, for example, in terms of the number of conductive lines, communication components (e.g., resistors, capacitors), etc. For example, the wired connection 316 between branch 302 and main control unit 310 can be a bus for the second communication protocol, such as a standard automotive bus, such as a CAN bus, LIN bus, Ethernet bus, etc. For example, all branches 302 can be coupled to the same bus, which is coupled to main control unit 310.

[0098] Considering the configuration with different communication protocols, the communication circuit 314 of the interface node 306 of branch 302 may include: a first part configured to communicate according to a first communication protocol (with the network node 308 coupled to the interface node 306); and a second part configured to communicate according to a second communication protocol (with the main control unit 310). However, it should be understood that a configuration in which the main control unit 310 uses the same wired communication protocol as the internal communication in branch 302 and communicates with branch 302 via the same type of wired connection may also be provided.

[0099] It should be understood that, for the purpose of explanation, Figure 3A The representations in the diagram can be simplified, and network 300 may include additional components relative to those shown. As an example, network 300 may include a power source or may be configured to be coupled to a power source. The power source may be configured to supply power (e.g., voltage) to the network nodes 304 of branch 302. As an example, the power source may be configured to supply a voltage from 1V to 50V to each node 304; for example, the power source may be configured to supply 12V, 24V, or 48V to each network node 304. In this configuration, each network node 304 may also include a power port coupled to a power line for receiving power from the power source.

[0100] As another example, network 300 may include a clock generator or may be configured to be coupled to a clock generator. The clock generator may be configured to transmit a clock signal to network node 304 of branch 302. Network node 304 (e.g., communication circuitry 314) may use the clock signal to time communication with one or more adjacent network nodes 304, for example, to control signal levels (voltage levels) on conductive lines according to timing defined by the clock signal.

[0101] Figure 3B A block diagram schematic of a master control unit 320 for use in network 300 is shown according to various aspects. Exemplarily, the master control unit 320 may be an exemplary configuration of the master control unit 310. It should be understood that... Figure 3B The configuration described herein is exemplary, and the main control unit may include additional, fewer, or alternative components. Typically, the main control unit 320 may include a processor 322, a memory 324, communication circuitry 326, and software 328 to perform the functions described herein.

[0102] Processor 322 can be configured to generate instructions for instructing the operation of network node 304 of branch 302, and to transmit these instructions via communication circuitry 326. For example, processor 322 can generate instructions specific to target branch 302 or specific to target node 304 within branch 302. As another example, processor 322 can generate instructions for all branches 302 (or a subset comprising multiple branches 302), for example, to initialize operations at startup. For example, memory 324 can store a set of possible instructions that processor 322 retrieves for transmission to branch 302.

[0103] Processor 322 can also be configured to receive data from branch 302, such as data representing operations at branch 302, the state of branch 302, the state of node 304, etc. Processor 322 can store the received data in memory 324, for example, to create a log for network 300. Processor 322 can also process the received data to analyze the state of network 300. For example, processor 322 can receive data indicating a fault in branch 302 or node 304 of branch 302, and can generate corresponding instructions, such as stopping the operation of branch 302 or node, setting different operating parameters for branch 302 or node 304, sending alarm signals to users, etc. Processor 322 can execute programming contained in software 328 to perform analysis of the data received from branch 302. For example, memory 324 can be configured to store software 328 to be executed by processor 322.

[0104] Communication circuit 326 can be configured to enable wired communication between the main control unit 320 and the interface node 306 of the branch 302. Therefore, communication circuit 326 may include communication hardware to enable a wired connection with interface node 306. For example, the communication hardware may include multiple input / output ports, resistors, capacitors, switches (e.g., transistors), etc., to perform wired communication. In some aspects, the main control unit 320 may also include communication circuitry for wireless communication, such as for communicating with other types of devices (e.g., within a vehicle).

[0105] As mentioned above, interface node 306 of branch 302 can have different configurations. Typically, interface node 306 can be configured as the master node (see...). Figure 3C For example, interface node 306 can be configured as a local master node of branch 302, or as a bridging node that has no leadership function and only acts as a "translator" between master control unit 310 and network node 304 of branch 302 (see [link to relevant documentation]). Figure 3D In this respect, the interface nodes 306 of different branches 302 can be configured in the same way or in different ways.

[0106] In one exemplary configuration, the interface node 306 of each branch 302 can be configured as a master node, which controls the operation of the secondary nodes 308 of the branch 302. As another exemplary configuration, the interface node 306 of each branch 302 can be configured as a bridging node, which converts messages using the wired communication protocol of the future autonomous control unit 310 into messages according to the wired communication protocol of the network node 304 of the branch 302. As yet another exemplary configuration, one or more branches 302 may include interface nodes 306 configured as master nodes, and one or more other branches 302 may include interface nodes 306 configured as bridging nodes.

[0107] Figure 3C The interface node configured as master node 330 is shown, and Figure 3D An interface node configured as bridging node 360 ​​is shown. For example, the master node 330 and bridging node 360 ​​could be configured as interface node 306 of branch 302.

[0108] Typically, the master node 330 and / or bridge node 360 ​​may include communication circuitry 332, 362, processing circuitry 334, 364, and input / output ports 340, 342, 370, 372. In some aspects, the communication circuitry 332, 362 may be configured to communicate according to two different communication protocols, for example, one to the master control unit 310 / slave master control unit 310, and another to the secondary node 308 of branch 302 / slave secondary node 308. Therefore, the communication circuitry 332, 362 may be configured to enable communication coupling between the master node 330 or bridge node 360 ​​and at least one secondary network node 308, and also communication coupling with the master control unit 310. Although not shown, in some aspects, the master node 330 and / or bridge node 360 ​​may also include memory.

[0109] Therefore, communication circuits 332 and 362 can be configured to implement first communication according to a first communication protocol (e.g., OSP) used in branch 302, and also to implement second communication according to a second communication protocol used by the main control unit 310. Exemplarily, communication circuits 332 and 362 may include first circuit portions 336 and 366, configured to perform first communication with one or more network nodes 308 of branch 302 according to the first communication protocol. Communication circuits 332 and 362 may also include second circuit portions 338 and 368, configured to perform second communication with the main control unit 310 according to the second communication protocol.

[0110] Therefore, the first circuit portions 336, 366 may include one or more components to control or define the input / output ports 340, 370 (e.g., at one or more conductive lines, such as...) where nodes 330, 360 are coupled to or will be coupled to the sub-network node 308. Figure 2D The voltage level at the location described in the document. The second circuit portions 338, 368 may include one or more components to control or define the voltage level at the input / output ports 342, 372 (e.g., at one or more conductive lines) where nodes 330, 360 are coupled to or therewith the main control unit 310.

[0111] Therefore, the first circuit portions 336 and 366 can be configured to perform first communication using first communication parameters, such as: a first timing (e.g., synchronous or asynchronous), a first encoding, a first voltage level defining a logic level, a first message structure, a first data rate, etc. The second circuit portions 338 and 368 can be configured to perform second communication using second communication parameters, such as: a second timing, a second encoding, a second voltage level defining a logic level, a second message structure, a second data rate, etc. One or more of the first communication parameters may differ from the corresponding second communication parameters.

[0112] Therefore, communication circuits 332 and 362 can be configured to convert the physical layer of the communication protocol of the main control unit 310 to the physical layer of the communication protocol of the branch 302, or to convert the physical layer of the communication protocol of the branch 302 to the physical layer of the communication protocol of the main control unit 310. The physical layer can be different in one or more layer parameters, such as the number of conductive lines, the type of conductive lines, the layout of input / output pins, voltage, etc.

[0113] The specific configurations of the first and second circuit sections 336, 338, 366, 368 and the input / output ports 340, 342, 370, 372 can be adapted according to the communication protocol. In this regard, the number of pins, the type and / or number of resistors, the type and / or number of switching elements, etc., can be adapted according to the first and second communication protocols. Considering the OSP protocol, as per... Figure 2C The input / output ports 340, 370 discussed for coupling with the secondary network node 308 may include two input / output pins for coupling with two conductive lines.

[0114] In some respects, the hardware of circuit portions 332, 362 may be specific to a communication protocol. For example, the first circuit portions 336, 366 may include hardware components capable of communicating using a first communication protocol, and the second circuit portions 338, 368 may include hardware components capable of communicating using a second communication protocol.

[0115] Moving to the configuration of the interface node as master node 330, master node 330 can be configured to control (e.g., instruct) the operation of secondary network node 308 of branch 302. Exemplarily, processing circuitry 334 can be configured to generate instructions for secondary network node 308 and cause these instructions to be transmitted to secondary network node 308 via communication circuitry 332. Exemplarily, master node 330 can be configured to act as a branch master node capable of bidirectional communication with master control unit 310 and also capable of generating instructions for instructing the operation of secondary node 308.

[0116] Therefore, the processing circuitry 334 of the master node 330 can be configured to control communication within the network branch 302, for example, to control data transmission on a daisy chain of network nodes 308. Exemplarily, the processing circuitry 334 can be configured to cause messages to propagate along the chain of secondary nodes 308 and prompt responses from one or more of the secondary nodes 308. As described above, the master node 330 may be a microcontroller or include a microcontroller to perform control over the secondary network nodes 308.

[0117] In this configuration, the master node 330 can be configured to receive messages 350 from the master control unit 310 and generate one or more instructions for controlling the operation of the secondary node 308 based on the messages 350 received from the master control unit 310. The master node 330 can also be configured to cause the generated instructions to propagate along a daisy chain of secondary nodes 308. Exemplarily, the master node 330 can be configured to translate messages from the master control unit (e.g., including instructions with high-level abstractions) into specific instructions for local operations of branch 302. As an example, messages from the master control unit may include abstract instructions such as "initialization operation," and the master node 330 can be configured to generate specific instructions for implementing the "initialization operation" (e.g., powering on, setting voltage levels, performing diagnostic procedures, etc.).

[0118] As shown in the figure, the master node 330 (e.g., its communication circuitry 332) can be configured to receive a (first) message 350 from a master control unit, execute a process 352 on the message 350 (at processing circuitry 334), and generate a (other) second message 354 addressing the secondary node 308 based on the process 352 on the first message 350. The process 352 may include, for example, interpreting a (first) instruction contained in the first message 350 and generating one or more (second) instructions addressing the secondary node 308 based on the processing of the first instruction. As another example, the process 352 may include interpreting a (first) information request contained in the first message 350 and generating one or more (second) information requests addressing the secondary node 308 based on the processing of the first information request.

[0119] In some aspects, processing 352 may include converting instructions contained in message 350 of the future autonomous control unit 310 into branch-specific instructions (low-level instructions) to control the operation of one or more of the sub-network nodes 308, thereby implementing the instructions contained in message 350.

[0120] As an example, the second message 354 may include the address of the target secondary node 308, for example, to control the operation of a specific node 308 or to retrieve information from a specific node 308 (exemplarily, prompting a response from the secondary node 308). For example, as Figure 3C As shown, the second message 354 may include multiple second messages, such as message 354(1) addressing to the first node 308, message 354(2) addressing to the second node 308, and message 354(N) addressing to the Nth node 308. As another example, the second message 354 may address all the secondary nodes 308, for example, to control the common operation of the secondary nodes 308 or to retrieve information from all the secondary nodes 308.

[0121] As described above, communication between the master control unit 310 and the interface node (as master node 330) can be bidirectional. Therefore, master node 330 can be configured to generate a message addressing master control unit 310 and transmit that message to master control unit 310. The content of this message can include any suitable information, depending on the initial instructions from master control unit 310. For example, the message can include information about the operation of secondary node 308 (e.g., operation status, operation parameters, etc.). As another example, the message can include confirmation that the instructions from master control unit 310 have been successfully executed and completed.

[0122] In some respects, the master node 330 can be configured to control the operation of the secondary network nodes 308 independently of the master control unit 310, for example, even in the absence of a corresponding message / instruction from the master control unit 310. In this scenario, in addition to receiving and processing instructions from the master control unit 310, the master node 330 can also be configured to autonomously instruct the operation of the secondary nodes 308. This configuration can improve the efficiency of branch operations by allowing the master node 330 to operate locally without waiting for corresponding prompts from the master control unit 310.

[0123] The operations that the master node 330 can perform independently of the master control unit 310 can be relatively low-complexity operations, or preparatory operations for functions to be performed by the secondary node 308. For example, the master node 330 can locally decide and autonomously perform some (simple) tasks without contacting the master control unit 310, such as running a temperature stabilization program, instructing node 308 to perform calibration, performing color-to-PWM calculations, etc.

[0124] Depending on various aspects, the master node 330 and the directly adjacent secondary node 308 coupled to the master node 330 can be configured to communicate with each other using Manchester encoding. Exemplarily, the master node 330 and the directly adjacent secondary node 308 in the chain can be connected via a single-ended bus, and the master node 330 can communicate data to the secondary node 308 using a single-wire Manchester-encoded signal. This configuration facilitates operation at the master node 330 and simplifies the circuit configuration at the secondary node 308. Exemplarily, the communication circuit 332 of the master node 330 can be configured to encode the signal to be transmitted according to Manchester encoding, and the communication circuit 314 of the secondary node 308 can be configured to decode the received signal according to Manchester encoding. Details of Manchester encoding and Manchester-encoded signals are known in the art.

[0125] Moving to the configuration of the interface node as bridge node 360, bridge node 360 ​​can be configured to convert messages from the master control unit 310 into messages according to the communication protocol used within branch 302, without interpreting the data contained in the messages. For example, bridge node 360 ​​can simply forward messages from the master control unit 310 in a format that the secondary network node 308 can interpret, without taking any action based on the content of the messages. For instance, bridge node 360 ​​can act as an "interpreter" between the master control unit 310 and the secondary network node 308 of the branch. Considering the OSP context, bridge node 360 ​​(e.g., its processing circuitry 364) can extract the payload portion of the message and forward the instructions to the secondary node 308. In this scenario, the actions / instructions performed by the master node of branch 302 are instead performed by the master control unit 310. For example, with the interface node configured as bridge node 360, branch 302 may not have a master node 330 (local master node).

[0126] In this scenario, the communication circuit 362 of the bridging node 360 ​​can be configured to provide a bridging interface between two different communication protocols, thereby acting as an "interpreter" or "translator" between the branch 302 and the main control unit 310. In this regard, the communication circuit 362 can be configured to receive a first message 380-1 from the main control unit 310 configured according to a wired communication protocol. The processing circuit 364 can perform processing 382 to transform the first message 380-1 into a second message 380-2 configured according to another wired communication protocol of the branch 302. The information contained in the first message 380-1 may correspond to the information contained in the second message 380-2 (e.g., instructions), and the format of the messages differs according to their respective wired communication protocols.

[0127] Considering bidirectional communication, the opposite scenario may also occur. Therefore, the communication circuit 362 can be configured to receive a second message 380-2 configured according to the wired communication protocol of branch 302, and transform the second message 380-2 into a first message 380-1 configured according to the wired communication protocol of the main control unit 310, for example, to transmit data to the main control unit 310.

[0128] Therefore, processing circuitry 364 can be configured to extract information from first message 380-1 and embed the extracted information into second message 380-2, exemplarily, into a structure compatible with the second communication protocol; or, processing circuitry 364 can be configured to extract information from second message 380-2 and embed the extracted information into first message 380-1, exemplarily, into a structure compatible with the first communication protocol. Considering the OSP context, processing circuitry 364 can extract information from first message 380-1 and embed the extracted information into the payload portion of an OSP message for transmission to network node 308.

[0129] As discussed regarding the primary node 330, message 380-2 sent to the secondary network node 308 may include multiple messages, for example, each message addressing a specific secondary network node 308. For example, as... Figure 3D As shown, the second message 380-2 may include multiple second messages, such as message 380-2(1) addressing the first node 308, message 380-2(2) addressing the second node 308, message 380-2(N) addressing the Nth node 308, etc. As another example, the second message 380-2 may address all the secondary nodes 308, for example, to control the common operation of the secondary nodes 308 or to retrieve information from all the secondary nodes 308.

[0130] In one possible configuration where interface node 306 is the master node 330 and / or interface node 306 is the bridge node 360, the network node 304 of branch 302 can be configured to support multiple physical modes. For example, at least one branch 302, more than one branch 302, or each branch 302's network node 304 can be configured to support multiple physical modes. Exemplarily, the branch's network node 304 (e.g., the corresponding communication circuit 414) can be configured to support multiple different physical modes for propagating information along the chain. Exemplarily, network node 304 can be configured to communicate with one or more adjacent network nodes 304 using one of the multiple possible physical modes for communication. For example, the selection of which physical mode to use can be based on instructions received at network node 304 (e.g., from the network's master control unit 310, or from the branch's local master node 330). The availability of multiple physical modes enhances deployment flexibility by customizing communication types according to system requirements.

[0131] For example, network node 304 can be configured to communicate via a wired connection based on any suitable combination of signal levels at the conductive line to achieve a selected physical mode. For example, consider Figure 2D In the configuration, network node 304 can be configured to control one or more pull-up and pull-down resistors based on the selected physical mode. The physical mode selection can be accomplished using specific combinations of pull-up and pull-down resistors on each of the two communication lines. Each port of network node 304 can support different physical modes.

[0132] A specific physical mode can be defined based on the desired configuration of branch 302 (e.g., based on the desired communication protocol to be used in branch 302). Some examples are provided below that are specifically designed for use with the OSP protocol; however, it should be understood that the physical modes described herein can also be used with other communication protocols, and network node 304 can be configured to support additional, fewer, or alternative physical modes.

[0133] Depending on various aspects, network node 304 (e.g., secondary node 308) can be configured to receive instructions (from the master control unit 310 or from the local master node 330) indicating the physical mode to be selected for communication. Network node 304 can be configured to select the indicated physical mode and perform communication (with other network nodes 304) according to the selected physical mode. The selected physical mode can define the physical manner in which data is transmitted from the secondary network node 304.

[0134] Depending on various aspects, one or more network nodes 304 (e.g., in one branch 302, multiple branches 302, or each branch 302) may have hard-coded physical modes. For example, hard-coding defines a single physical mode available to the one or more network nodes 304, for example, to enforce a preferred data communication method taking system factors into account. Hard-coding may be provided, for example, for dedicated secondary nodes 308 used in specific locations (e.g., MCU-to-OSP nodes and OSP-to-OSP nodes, etc.), where the choice of physical mode is hard-coded by design. In some aspects, a standard physical mode may exist that is supported by all network nodes 304 in branch 302, and a preferred mode can be switched to via instruction.

[0135] As an example, network node 304 supports / can select multiple physical modes, including: single-ended bidirectional mode, differential mode, line-terminated (EOL) mode, and single-line unidirectional mode.

[0136] The single-ended bidirectional mode (also known as MCU mode) can provide only the connection between the master node 330 and the adjacent secondary node 308 for branch 302. Exemplarily, this mode can be limited to the connection between the local master node and the first slave node. According to the single-ended bidirectional mode, data (from master node 330) can be transmitted to secondary node 308 using a single wire and Manchester encoding (to simplify the integrated circuit of secondary node 308). In the opposite direction (from secondary node 308 to master node 330), clock and data transmission are used (to enable efficient use of a standard controller). As an alternative connection type between master node 330 and the adjacent secondary node 308, a standard SPI or Universal Asynchronous Receiver / Transmitter (UART) bus can be used.

[0137] Differential mode can be the preferred mode for communication between the two secondary nodes 308 in branch 302. Communication between the two secondary nodes 308 can utilize a differential signaling scheme, where data is encoded using the voltage difference between two lines. For clock and data recovery, Manchester encoding is used to further encode the information, for example. This is the preferred mode for communication between the two secondary nodes 308 to minimize electromagnetic interference.

[0138] Single-wire unidirectional mode allows the use of additional transceiver units to convert single-ended signals into certain other signaling technologies (see...). Figure 5C and Figure 5D For example, this mode can be used to bridge longer distances between two secondary nodes 308 by using a pair of CAN-FD transceivers and a CAN physical connection.

[0139] EOL mode can signal to secondary node 308 that the node is the last node in the daisy chain. This information allows the message to propagate along the chain, enabling the last node (in the case of a linear chain) to send the message back or (in the case of a loopback configuration) to forward the message to the master node.

[0140] Figure 4A A message flow diagram 400 is shown to illustrate an exemplary message flow in branch 302, which includes a master node 330 that acts as an interface node between the master control unit 310 and the master node 330. As described above, the master control unit 310 can send a first message 350 to the master node 330. For example, the master control unit 310 (e.g., the master BCU) can send instructions to the local branch master node 330, such as higher-level abstractions (e.g., “Start System”, “Play Animation #1”, “Set Color Mode #5”, etc.), which can be adapted to functions implemented through secondary nodes 308 (e.g., light emission, sensing, etc.). For example, considering an automotive context, the master control unit 310 can send instructions via a standard automotive bus.

[0141] The master node 330 can perform processing 352 on the first message 350 (e.g., an instruction) to generate a second message 354 based on the content of the first message 352. For example, the master node 330 can translate an instruction from the master control unit 310 into a separate instruction for a secondary node 308 in branch 302. In an exemplary configuration, the master node 330 can generate multiple second messages 354, such as one second message 354 for each secondary node 308. These second messages 354 include specific instructions for the target node 308 and also include the address of the target node 308. The type of instruction can depend on the type of node 308 and the type of communication protocol used. As an example, considering "start system" as an instruction from the master control unit 310, one or more second messages 354 can include instructions such as "send initialization → wait for response → check the number of nodes → load calibration → set default values," for example, considering an OSP context.

[0142] Secondary node 308 can receive instructions from primary node 330 and execute corresponding functions based on these instructions. For example, if message 354 is not addressed to node 308, secondary node 308 can simply forward the message further along the chain (until the message reaches the target node 308) without performing any further action. Exemplarily, node 308 can forward messages not targeted to a specific node from one port to another (allowing the message to propagate along the chain). If node 308 receives a message for itself, its circuitry can analyze the message and execute any instructions contained within it. If the instructions prompt a response, node 308 can generate a response message for primary node 330 and propagate that response message along the chain to primary node 330.

[0143] In the exemplary flowchart 400, the master node 330 can generate a first message 354(1) addressed to the first node 308-1 (exemplarily, an adjacent node 308 in the chain). Upon receiving the first message 354(1), the first node 308-1 can execute the instructions in the message and, if prompted, generate a first response message 356(1) and pass the first response message 356(1) to the master node 330. The master node 330 can further generate a Nth message 354(N) addressed to the Nth node 308-N. In this scenario, the first node 308-1 (and other nodes) simply forwards the Nth message 354(N) without analyzing its content (except for the address portion) and without executing the instructions contained in the message 354(N). The Nth node 308-N can receive the Nth message 354(N), execute the instructions, and, if prompted, generate a Nth response message 356(N) for the interface node 506.

[0144] Therefore, the communication circuit 314 of the secondary node 308 can enable the response messages 356(1) and 356(N) to be transmitted to the primary node 330. For example, after the response messages 356(1) and 356(N) have been generated, the communication circuit 314 of the working secondary node 308 can initiate the transmission of the response messages 356(1) and 356(N) along a daisy chain until the response messages 356(1) and 356(N) reach the primary node 330. Considering a linear daisy chain, the response messages 356(1) and 356(N) can propagate backward along the chain, while in a circular daisy chain, the response messages 356(1) and 356(N) can propagate forward and then loop back to the primary node 330 from the last node.

[0145] Therefore, the secondary node 308 that generates response messages 356(1) and 356(N) can transmit response messages 356(1) and 356(N) to the adjacent node 308 (via wired connection 312, according to a wired communication protocol, such as OSP). The adjacent node 308 can receive response messages 356(1) and 356(N), determine that response messages 356(1) and 356(N) are addressed to the master node 330, and forward response messages 356(1) and 356(N) along the chain toward the master node 330. The forwarding of response messages 356(1) and 356(N) can be repeated until response messages 356(1) and 356(N) reach the master node 330.

[0146] The type of instruction addressed to secondary node 308 can be adapted in any suitable manner, such as according to the desired operation to be performed at secondary node 308. For example, the instruction may cause secondary node 308 to initiate its function (e.g., emission, sensing process, etc.). For example, the instruction may cause secondary node 308 to operate using certain parameters (e.g., a voltage, a light intensity, the duration of a sensing process, etc.). As another example, the instruction may cause secondary node 308 to stop its operation or report a diagnostic indicating a possible fault at node 308.

[0147] The content of response messages 356(1) and 356(N) from secondary node 308 to primary node 330 can vary depending on prompts from primary node 330 and instructions from master control circuit 310. For example, response messages 356(1) and 356(N) may include values ​​of operating parameters of node 308, such as operating temperature, operating voltage, intensity of emitted light, etc. As another example, response messages 356(1) and 356(N) may include the results of sensing processes performed by the node, such as instantaneous values ​​of sensed measurements, average values ​​over time, etc. As another example, response messages 356(1) and 356(N) may include the operating state of node 308, such as sleep, idle, working, measuring, emitting light, etc. As another example, response messages 356(1) and 356(N) may include the condition of node 308, for example, to indicate that a fault or potential fault exists at node 308.

[0148] The master node 330 can prompt for an individual response from a single target secondary node 308, or it can prompt for a collective response from all secondary nodes 308, depending on the desired operation and / or the initial instructions from the master control unit. As described above, the master node 330 can also send data (message 358) to the master control unit 310.

[0149] Figure 4BA message flow diagram 450 is shown to illustrate an exemplary message flow in branch 302, which includes a bridging node 360 ​​serving as an interface node with the main control unit 310. As described above, the main control unit 310 may send a first message 380-1 configured according to the wired communication protocol of the main control unit to the bridging node 360. For example, the main control unit 310 (e.g., the main BCU) may use an automotive standard bus to send a message / instruction with a sequence of instructions as a payload (e.g., "Send Initialization → Wait for Response → Check Number of Nodes → Load Calibration → Set Defaults") to the branch bridging node 360. For example, the automotive standard bus may be an Ethernet bus.

[0150] Bridge node 360 ​​can extract instructions from first message 380-1 and insert them into second message 380-2 according to the wired communication protocol (e.g., OSP) of branch 302. Exemplarily, bridge node 360 ​​extracts the payload and sends each instruction as a separate message (e.g., using OSP) to the nodes in the attached branch 302. For example, bridge node 360 ​​can send message 380-2(1) to first node 308-1... and send Nth message 380-2(N) to Nth node 308(N).

[0151] If prompted, the secondary node 308 can generate a response message for the master control unit 310, such as a first response message 384-2(1) from the first node 308-1, an Nth response message 384-2(N) from the Nth node 308-N, etc. One or more response messages from one or more secondary nodes 308 can be configured according to the wired communication protocol of branch 302, and the bridging node 360 ​​can convert one or more response messages into response messages 384-1(1), 384-1(N) according to the wired communication protocol of the master control unit 310. For example, the bridging node 360 ​​can package incoming messages (e.g., OSP messages) from the secondary nodes 308 into response frames to be sent to the master control unit 310.

[0152] Each secondary network node 308 can receive / send messages to the bridging node 360 ​​according to the communication protocol (e.g., OSP) of the branch 302. (See also: Regarding...) Figure 4AThe receiving / sending discussed may include forwarding messages that are not targeted at / addressed to a specific node from one port to another (allowing the message to propagate along the chain). If node 308 receives a message for node 308, node 308 analyzes the message and executes the instructions included therein. If a response is required, node 308 prepares and sends this response back to bridge node 360. Unlike the case of master node 330, bridge node 360 ​​does not interpret data or make decisions locally (e.g., autonomously running a temperature stabilization sequence). Instead, all decisions are made at the master control unit 310.

[0153] Figures 5A to 5D Exemplary configurations 500a-500d for branch 500 (exemplarily, sub-network 500) used in the proposed architecture are shown. Exemplarily, configurations 500a-500d for branch 500 can be exemplary implementations of branch 302 of network 300. Typically, as... Figure 5A and Figure 5C As shown in configurations 500a and 500c, branch 500 can be configured according to a linear daisy-chain topology in which network nodes are configured for bidirectional communication. Alternatively, as Figure 5B and Figure 5D As shown in configurations 500b and 500d, branch 500 can be configured according to a ring daisy-chain topology in which network nodes are configured for unidirectional communication.

[0154] In a linear daisy-chain topology, each network node can be configured to send data to and receive data from adjacent network nodes 308, allowing information to propagate from interface node 306 (master node 330 or bridge node 360) to the end of the chain, and then back through the chain to interface node 306 (for further forwarding to master control unit 310). In a ring daisy-chain topology, each network node 308 can be configured to receive data only from previous nodes 308 in the chain and send data only to subsequent nodes 308 in the chain. Considering interface node 306 (master node 330 or bridge node 360) as the initial node of the chain, the final node 308 can then couple back to interface node 306, allowing information to propagate from interface node 306 to the end of the chain, and then back through the loopback connection to interface node 306 (for further forwarding to master control unit 310).

[0155] like Figure 5A and Figure 5BAs shown, in a simple configuration, the network nodes 306 and 308 of branch 500 can be integrated on a single substrate 502. Exemplarily, network nodes 306 and 308 can be arranged (e.g., formed on) the same substrate 502. Substrate 502 can be, for example, a rigid substrate. As another example, substrate 502 can be a flexible substrate, for example, to facilitate the arrangement of branch 500 in more complex geometries within a host device. As an example, substrate 502 can be a printed circuit board (PCB).

[0156] like Figure 5C and Figure 5D As shown, in other respects, the network nodes 306 and 308 of branch 500 can be integrated on multiple separate substrates 502-1 and 502-2. Consider... Figure 5C and Figure 5D In the exemplary configuration, a first subset of network nodes 306, 308 can be arranged on a first substrate 502-1 (e.g., a first PCB), and a second subset of network nodes 308 can be arranged on a second substrate 502-2 (e.g., a second PCB). This configuration can facilitate the expansion of the number of nodes in a branch by providing a “modular” arrangement in which additional nodes (e.g., additional secondary nodes 308) can be provided in a simple manner by coupling additional substrates to the existing chain.

[0157] like Figure 5C and Figure 5D As shown, interface node 306 and one or more secondary nodes 308 (e.g., a first plurality of secondary nodes 308) can be integrated on the first substrate 502-1. One or more other secondary nodes 308 (e.g., a second plurality of secondary nodes 308) can be integrated on the second substrate 502-2. Optionally, other secondary nodes 308 can be integrated on a third substrate, and so on.

[0158] Considering the multi-branch architecture (e.g., network 300), these branches can be configured in the same or different ways in terms of integration on the substrate. For example, all branches 302 in network 300 may include network nodes 304 integrated on the same (corresponding) substrate 502. As another example, all branches 302 in network 300 may include network nodes 304 integrated on multiple (corresponding) substrates 502-1, 502-2. As yet another example, at least one branch 302 may include network nodes 304 integrated on the same (single) substrate 502, and at least one other branch 302 may include network nodes 304 integrated on multiple substrates 502-1, 502-2.

[0159] In configurations 500c and 500d having multiple substrates 502-1 and 502-2, the branch 500 may further include transceiver elements on each substrate 502-1 and 502-2 to enable communication coupling between branch portions on different substrates 502-1 and 502-2. For example, the branch 500 may include a first transceiver element 504-1 on the first substrate 502-1 and a second transceiver element 504-2 on the second substrate 502-2 (and a third transceiver element, etc., on a third substrate). The first transceiver element 504-1 and the second transceiver element 504-2 may be coupled to each other via a wired connection 506 to enable data transmission between network nodes 306 and 308 on the first substrate 502-1 and network node 308 on the second substrate 502-2. Transceiver elements 504-1 and 504-2 may be, by way of example, transceiver nodes including transceiver circuitry to send data to and receive data from network node 308.

[0160] For example, the first transceiver element 504-1 may be coupled to the last network node 308 in the chain in the first substrate 502-1. The first transceiver element 504-1 may also be coupled to a second transceiver element 504-2, and the second transceiver element 504-2 may also be coupled to a first node in the chain in the second substrate 502-2. Thus, the first transceiver element 504-1 can propagate information to the second transceiver element 504-2 for further propagation along the chain.

[0161] Based on the topology of branch 500, the wired connection 506 between transceiver elements 504-1 and 504-2 can support bidirectional communication (in... Figure 5C (in) or one-way communication (in) Figure 5D (In the middle). Transceiver elements 504-1 and 504-2 can communicate with each other using the same protocol as network nodes 306 and 308, or they can communicate with each other using different wired communication protocols. When using different protocols, the wired connection 506 between transceiver elements 504-1 and 504-2 can have a different configuration than the wired connection 312 between nodes 306 and 308 in the branch (or the connection between a node and transceiver elements 504-1 and 504-2). Considering that transceiver elements 504-1 and 504-2 do not need to interpret data or add information to data, using different protocols for transceiver elements 504-1 and 504-2 can provide a simpler but more efficient configuration.

[0162] Therefore, transceiver elements 504-1 and 504-2 (and wired connection 506) can be configured according to a communication protocol used for inter-board communication. In a preferred configuration, transceiver elements 504-1 and 504-2 can be configured as CAN transceivers, for example, as CAN-FD transceivers. In this scenario, transceiver elements 504-1 and 504-2 can be configured to communicate with each other via a CAN bus using a CAN protocol (e.g., CAN-FD protocol).

[0163] Figures 6A to 6C Exemplary configurations of serial communication networks 600a, 600b, and 600c are shown. Exemplarily, Figures 6A to 6C An exemplary implementation of network 300 is shown. It should be understood that the aspects discussed with respect to network 300 can be applied to networks 600a, 600b, and 600c in a corresponding manner, and the aspects discussed with respect to networks 600a, 600b, and 600c can also be applied to network 300 in a corresponding manner.

[0164] Figure 6A A network 600a is shown comprising multiple branches (first branch 602a-1 and second branch 602a-2), wherein an interface node coupled to the main control unit 310 is a master node 330 that controls the operation of secondary nodes 308 of the branches. For example, one or more master nodes 330 may be coupled to the main control unit 310 via a standard automotive bus (e.g., CAN, LIN, Ethernet, etc.).

[0165] As an example, the master node 330 can be coupled to an adjacent network node 308 (the first network node 308 in the chain) via a single-ended bus to simplify the operation of the master node 330. Bidirectional differential signaling can be provided between the secondary network nodes 308 to minimize electromagnetic interference. As shown, branch 602a-2 may include transceiver elements 504-1, 504-2 (e.g., CAN-FD) to couple branch portions arranged on different substrates. For example, a single-wire unidirectional mode can be implemented to integrate transceiver nodes in the chain. As an exemplary configuration, transceiver elements 504-1, 504-2 can communicate with each other via a CAN bus.

[0166] Therefore, for example, configuration 600a may include a master control unit 310 (BCU) connected via some standard bus to one or more branch control units 330 (acting as branch master nodes), which are connected (e.g., via OSP) to a number of slave nodes arranged in a serial chain (daisy chain), wherein there is a bidirectional communication line between each pair of participating nodes. Node 308 may support different physical modes and message / message-based communication protocols (e.g., OSP) with low overhead and diagnostic capabilities.

[0167] Figure 6B A network 600b is shown, comprising multiple branches (first branch 602b-1 and second branch 602b-2). The interface node coupled to the main control unit 310 is a bridge node 360, which acts as a translator between the bus connecting the main control unit 310 to the bridge node and the bus connecting the nodes in branches 602b-1 and 602b-2. The aspects discussed regarding network 600a can be applied correspondingly. Figure 6B Configuration.

[0168] Therefore, for example, configuration 600b may include a master control unit 310 (BCU) that is connected via some standard bus to one or more branch control units 360 (acting as bridges). These branch control units 360 (e.g., via OSP) are connected to a number of slave nodes arranged in a serial chain (daisy chain), where there is a bidirectional communication line between each pair of participating nodes. Node 308 may support different physical modes and message / packet-based communication protocols (e.g., OSP) with low overhead and diagnostic capabilities.

[0169] Figure 6C It shows the corresponding Figure 6A The configured network 600c has branches 602c-1 and 602c-2 in a ring topology. As mentioned above, the ring mode allows for faster communication within the chain because the master node 330 does not have to wait for a response to a previous instruction before issuing the next one.

[0170] Therefore, for example, configuration 600c may include a master control unit 310 (BCU) connected via some standard bus to one or more branch control units 360 (acting as master nodes 330, or bridging nodes 360 not shown), which (e.g., via OSP) are connected to a number of slave nodes arranged in a serial chain (daisy chain), with a unidirectional communication line between each pair of participating nodes in the serial chain. Network 600c also includes a loopback communication line that directly connects the last node in the chain to the branch control unit. Node 308 may support different physical modes and message / packet-based communication protocols (e.g., OSP) with low overhead and diagnostic capabilities.

[0171] As used herein, the terms “processor,” “processing circuit,” or “control circuit” can be understood as any type of technical entity that allows the processing of data. Data can be processed according to one or more specific functions that the processor / control circuit can perform. Furthermore, the processor / processing circuit / control circuit used herein can be understood as any type of circuit, such as any type of analog or digital circuit. Therefore, a processor / processing circuit / control circuit can be or includes analog circuits, digital circuits, mixed-signal circuits, logic circuits (e.g., hard-wired logic circuits or programmable logic circuits), microprocessors, central processing units (CPUs), graphics processing units (GPUs), digital signal processors (DSPs), field-programmable gate arrays (FPGAs), integrated circuits, application-specific integrated circuits (ASICs), etc., or any combination thereof. It should be understood that any two (or more) of the processors / processing circuits / control circuits described in detail herein can be implemented as a single entity with equivalent functionality, and conversely, any single processor / processing circuit / control circuit described in detail herein can be implemented as two (or more) independent entities with equivalent functionality.

[0172] In this document, the term "connection" can be used relative to terminals, integrated circuit elements, devices, etc., to refer to an electrical connection. This can include direct or indirect connections, where an indirect connection may only include additional structures in the current path that do not affect the substantial function of the circuit or device. The term "conductive connection" as used herein describes an electrical connection between one or more terminals, devices, areas, contacts, etc., and can be understood as a conductive connection having, for example, ohmic behavior, such as a conductive connection provided by metal or degenerate semiconductor in the absence of a pn junction in the current path. The term "coupling" as used herein is used in the same manner as the term "connection."

[0173] In this document, the term "terminal" can be used to describe a location (e.g., a point) or structure of a device or device element that can provide a signal (e.g., an analog signal, such as current or voltage) and / or can be connected to another device or element. Exemplarily, a terminal can be a location or structure that is electrically connected to a device or element. A terminal may also be referred to herein as a port, pin, contact, or contact point.

[0174] In this document, the terms "path," "electrical path," or "conductive path" can be used to describe a conductive connection between two or more components. In some respects, a path can be understood as a conductive line (or trace) along which a signal (in some respects, current or voltage) can travel, for example, from a first component connected to the path to a second component connected to the path, or from a second component connected to the path to a first component connected to the path. The term path can describe a direct path or an indirect path, wherein an indirect path may include only additional structures in the path that do not affect the substantial function of the circuit or device (exemplarily, do not affect the signal traveling along the path).

[0175] As used herein, signals indicating, representing, or representing values ​​or other information (e.g., instructions) may be digital or analog signals that encode or otherwise communicate values ​​or other information in a manner that can be decoded by the component receiving the signal and / or cause a response action in the component receiving the signal (e.g., in a secondary device receiving instructions from a master device, or in a master device receiving data from a secondary device).

[0176] As used herein, “memory” is understood to be a computer-readable medium (e.g., a non-transitory computer-readable medium) capable of storing data or information for retrieval. Therefore, references to “memory” included herein can be understood to refer to volatile or non-volatile memory, including random access memory (RAM), read-only memory (ROM), flash memory, solid-state storage, magnetic tape, hard disk drive, optical disk drive, etc., or any combination thereof. Registers, shift registers, processor registers, data buffers, etc., are also included in the term “memory” herein.

[0177] In this document, the word "exemplary" is used to mean "as an example, instance, or illustration." Any embodiment or design described herein as "exemplary" is not necessarily to be construed as superior to other embodiments or designs.

[0178] The phrases “at least one” and “one or more” can be understood to include numerical quantities greater than or equal to one (e.g., one, two, three, four, [...] etc.). The phrase “at least one” relating to a group of elements can be used herein to mean at least one element from a group consisting of these elements. For example, the phrase “at least one of…” relating to a group of elements can be used herein to mean: one of the listed elements, multiple of one of the listed elements, multiple individual listed elements, or multiple multiples of individual listed elements.

[0179] Unless otherwise stated, the term "subset" in relation to a set of elements can be understood as including a number equal to or greater than 1 and less than the total number of implicit elements. For example, consider a set of ten elements; a "subset" of this set could include one, two, three, four, five, six, seven, eight, or nine elements. Therefore, the term "subset" in relation to a set can describe a "proper subset" of the set, such that all elements of the subset belong to the set, but at least one element of the set does not belong to the subset.

[0180] All abbreviations defined in the foregoing specification also apply to all claims contained herein.

[0181] Although the invention has been specifically shown and described with reference to particular aspects, those skilled in the art will understand that various changes in form and detail may be made without departing from the spirit and scope of the invention as defined by the appended claims. Therefore, the scope of the invention is indicated by the appended claims and is thus intended to cover all variations falling within the equivalent meaning and scope of the claims.

[0182] List of reference numerals

[0183] 100 Network

[0184] 100a Network Topology

[0185] 100b Network Topology

[0186] 102 network nodes

[0187] 104 Master Nodes

[0188] 106a secondary node

[0189] 106b secondary node

[0190] 106c secondary node

[0191] 106d sub-node

[0192] 108 control circuit

[0193] 110 Wired connection

[0194] 112 Communication Circuit

[0195] 200 network nodes

[0196] 200b network node

[0197] 200c-1 Network Node

[0198] 200c-2 Network Node

[0199] 200d network nodes

[0200] 202 Communication Circuit

[0201] 204 Functional Circuit

[0202] 204b Functional Circuit

[0203] 206 Input / Output Ports

[0204] 206c Input / Output Ports

[0205] 208 Input / Output Ports

[0206] 208c Input / Output Ports

[0207] 210 Driver Circuit

[0208] 212 Light-emitting element

[0209] 214 Input / Output Pins

[0210] 216 Input / Output Pins

[0211] 218 Input / Output Pins

[0212] 220 Input / Output Pins

[0213] 222 Conductive wire

[0214] 224 conductive wire

[0215] 226 Conductive wire

[0216] 228 Conductive wire

[0217] 230 Resistor Arrangement

[0218] 232 Resistor Arrangement

[0219] 234 Power Terminal

[0220] 236 Grounding terminal

[0221] 238 Communication Hardware

[0222] 240 processor

[0223] 300 Serial Communication Network

[0224] 302 branch

[0225] 302-1 First Branch

[0226] 302-2 Second Branch

[0227] 302-N Branch N

[0228] 304 network node

[0229] 306 Interface Node

[0230] 308 sub-nodes

[0231] 308-1 First Node

[0232] 308-N Nth node

[0233] 310 Main Control Unit

[0234] 312 Wired connection

[0235] 314 Communication Circuit

[0236] 316 Wired connection

[0237] 320 Main Control Unit

[0238] 322 processor

[0239] 324 memory

[0240] 326 Communication Circuit

[0241] 328 Software

[0242] 330 Master Nodes

[0243] 332 Communication Circuit

[0244] 334 Processing Circuit

[0245] 336 First Communication Section

[0246] 338 First Communication Section

[0247] 340 Input / Output Ports

[0248] 342 Input / Output Ports

[0249] 350 First News

[0250] 352 processing

[0251] 354 Second Message

[0252] 354(1) Messages for the first node

[0253] 354(2) Messages for the second node

[0254] 354(N) Messages for the Nth node

[0255] 356(1) First Response Message

[0256] 356(N) Nth Response Message

[0257] 358 Response Message

[0258] 360 Master Node

[0259] 362 Communication Circuit

[0260] 364 Processing Circuit

[0261] 366 First Communication Section

[0262] 368 First Communication Section

[0263] 370 Input / Output Ports

[0264] 372 Input / Output Ports

[0265] 380-1 First News

[0266] 380-2 Second Message

[0267] 380-2(1) Messages for the first node

[0268] 380-2(2) Messages for the second node

[0269] 380-2(N) Messages for the Nth node

[0270] 382 processing

[0271] 384-1(1) First Response Message

[0272] 384-2(1) First Response Message

[0273] 384-1(N) Nth Response Message

[0274] 384-2(N) Nth Response Message

[0275] 400 Message Flow Graph

[0276] 450 Message Flow Graph

[0277] 500 branches

[0278] 500a First Configuration

[0279] 500b Second Configuration

[0280] 500c Third Configuration

[0281] 500d Fourth Configuration

[0282] 502 base plate

[0283] 504-1 First Transceiver

[0284] 504-2 Second Transceiver

[0285] 506 Wired connection

[0286] 600a Serial Communication Network

[0287] 600b serial communication network

[0288] 600c Serial Communication Network

[0289] 602a-1 First Branch

[0290] 602b-1 First Branch

[0291] 602c-1 First Branch

[0292] 602a-2 Second Branch

[0293] 602b-2 Second Branch

[0294] 602c-2 Second Branch

Claims

1. A serial communication network (300), comprising: Multiple branches (302), wherein each branch (302) includes: Multiple network nodes (304) are interconnected in a daisy-chain configuration and configured to communicate with each other according to a wired communication protocol for serial communication. In one branch (302), multiple network nodes (304) are connected according to a linear daisy-chain topology and configured for bidirectional communication, or in another branch (302), multiple network nodes (304) are connected according to a ring daisy-chain topology and configured for unidirectional communication; and A main control unit (310) is shared by the plurality of branches (302) and is communicatively coupled to at least one network node (304, 306) of each of the plurality of branches (302). In this embodiment, at least one branch (302) of the network node (304) is configured to support multiple physical modes of communication according to a wired communication protocol for serial communication.

2. The serial communication network (300) according to claim 1. in, The main control unit (310) and the corresponding network nodes (304, 306) of each branch (302) that are communicatively coupled to the main control unit (310) are configured to communicate with each other in a bidirectional manner.

3. The serial communication network (300) according to claim 1 or 2. in, For at least one branch (302), the network nodes (304) in the at least one branch (302) are configured to communicate with each other according to a first serial communication protocol for wired communication, and In this configuration, network nodes (304, 306) of at least one branch (302) that are communicatively coupled to the main control unit (310) are configured to communicate with the main control unit (310) according to a second serial communication protocol for wired communication, which is different from the first serial communication protocol for wired communication.

4. The serial communication network (300) according to any one of claims 1 to 3. in, For at least one branch (302), the network nodes (304) in the at least one branch (302) are arranged on a plurality of substrates (502-1, 502-2) that are separated from each other.

5. The serial communication network (300) according to claim 4. in, The at least one branch (302) further includes a first transceiver element (504-1) disposed on a first substrate (502-1) of the plurality of substrates (502-1, 502-2) and a second transceiver element (504-2) disposed on a second substrate (502-2) of the plurality of substrates (502-1, 502-2). The first transceiver element (504-1) and the second transceiver element (504-2) are communicatively coupled to each other, and The at least one branch (302) includes a first plurality of network nodes (304) arranged on the first substrate (502-1) and a second plurality of network nodes (304) arranged on the second substrate (502-2).

6. The serial communication network (300) according to any one of claims 1 to 5. in, At least one network node (304) of at least one branch (302) has a hard-coded physical mode for communicating according to a wired communication protocol for serial communication.

7. The serial communication network (300) according to any one of claims 1 to 6. in, For at least one branch (302), the network node (306) of the at least one branch (302) that is communicatively coupled to the main control unit (310) is configured as a master node (330), and the other network nodes (304) of the branch (302) are configured as secondary nodes (308). The master node (330) is configured to instruct the operation of the secondary node (308).

8. The serial communication network (300) according to claim 7. in, The master node (330) is configured as follows: Receive message (350) from the main control unit (310), and Based on the message (350) received from the main control unit (310), one or more instructions are generated for controlling the operation of the secondary node (308).

9. The serial communication network (300) according to claim 8. in, The message (350) includes one or more first instructions, and The master node (330) is configured to generate one or more second instructions for controlling the operation of the secondary node (308) based on the one or more first instructions. The one or more second instructions are instructions of a lower level than the one or more first instructions.

10. The serial communication network (300) according to any one of claims 7 to 9. in, The master node (330) is also configured to independently receive messages (350) from the master control unit (310) to instruct one or more of the operations of the secondary nodes (308).

11. The serial communication network (300) according to any one of claims 7 to 10. in, The master node (330) is a microcontroller or includes a microcontroller.

12. The serial communication network (300) according to any one of claims 1 to 11. in, For at least one branch (302), the network node (306) of the at least one branch (302) that is communicatively coupled to the main control unit (310) is configured as a bridging node (360), and the other network nodes (304) of the branch (302) are configured as secondary nodes (308). The bridging node (360) is configured as follows: Receive a first message (380-1) from the main control unit (310) according to the second serial communication protocol for wired communication. Without interpreting the content of the first message (380-1), the first message (380-1) is transformed into a second message (380-2) according to a first serial communication protocol for wired communication; and This causes the second message (380-2) to propagate to the sub-network node (308).

13. The serial communication network (300) according to any one of claims 1 to 12. in, For at least one branch (302), the network nodes (304) are configured to communicate with each other according to the Open Systems Protocol. Preferably, in each branch (302), the network nodes (304) are configured to communicate with each other according to the Open Systems Protocol.

14. The serial communication network (300) according to any one of claims 1 to 13. in, For at least one branch (302), at least one network node (304) includes one or more light-emitting elements (212) and a driver circuit (210) configured to control the light emission made by the one or more light-emitting elements (212). Preferably, the one or more light-emitting elements (212) include one or more light-emitting diodes.

15. A vehicle comprising one or more serial communication networks (300) according to any one of claims 1 to 14.

Images