Method and system for a communication network

Abstract

A method for controlling a communication link between a first physical layer device and a second physical layer device in a communication network of a platform is provided. The method comprises: accessing, at the first physical layer device, a first data register, wherein the first data register comprises one or more data values indicative of a failure status of the first physical layer device; accessing a second data register, wherein the second data register comprises one or more data values indicative of a failure status of the second physical layer device; evaluating a signal quality of the communication link; controlling the communication link at the first physical layer device in accordance with the one or more data values of the first data register, the one or more data values of the second data register, and the signal quality.

Description

Technical Field

[0001] This invention relates to methods and systems for use in communication networks. Specifically, the methods and systems described herein relate to the operation of communication links in communication networks. Background Technology

[0002] Modern vehicles are equipped with increasingly sophisticated sensors, onboard computers, and other types of hardware. These devices are controlled by a central electronic control unit (ECU), which acts as the vehicle's brain. The ECU acquires sensor data and communicates commands with other devices via an in-vehicle network (IVN).

[0003] Centralized ECU control minimizes the computational complexity of nodes in an IVN because individual devices don't need to perform data analysis to determine their next action. However, safe vehicle operation depends on the proper functioning of the network to ensure that the correct instructions are received from the ECU at the nodes. Summary of the Invention

[0004] The purpose of this invention is to provide a method for controlling the communication link between a first physical layer device and a second physical layer device in a communication network (such as a vehicle network).

[0005] The above and other objectives are achieved through the features of the independent claim. Other implementations are apparent from the dependent claims, the description, and the drawings.

[0006] According to a first aspect, a method is provided for controlling a communication link between a first physical layer device and a second physical layer device in a communication network of a platform. The method includes: at the first physical layer device, accessing a first data register, wherein the first data register includes one or more data values ​​indicating a fault state of the first physical layer device; accessing a second data register, wherein the second data register includes one or more data values ​​indicating a fault state of the second physical layer device; evaluating the signal quality of the communication link; and controlling the communication link at the first physical layer device based on the one or more data values ​​of the first data register, the one or more data values ​​of the second data register, and the signal quality.

[0007] According to the method described in the first aspect, a fault status of the communication link between PHY devices in the communication network is established based on information locally stored or determined by one of the PHY devices.

[0008] According to a second aspect, a node in a communication network of a platform is provided. The node includes a physical layer device, wherein the physical layer device includes: a first data register for storing data indicating a fault state of the physical layer device; and a second data register for storing data indicating a fault state of a second physical layer device communicating with the physical layer device via a communication link. The physical layer device is configured to: access one or more data values ​​stored in the first register; access one or more data values ​​stored in the second register; evaluate the signal quality of the communication link between the physical layer device and the second physical layer device; and control the communication link based on the one or more data values ​​in the first data register, the one or more data values ​​in the second data register, and the signal quality.

[0009] According to a third aspect, an ECU for a communication network of a platform is provided. The electronic control unit includes: a processor; and a memory communicatively coupled to the processor. The memory stores instructions, when implemented on the processor, that cause the processor to receive a fault state of a communication link in the communication network; determine an operating mode of the platform at the ECU based on the fault state of the communication link; and control the platform to operate in the determined operating mode.

[0010] In one implementation, evaluating signal quality includes comparing the signal-to-noise ratio of the communication link with a predetermined threshold.

[0011] In one implementation, controlling the communication link at the first physical layer device includes restarting the communication link at the first physical layer device in response to determining that the signal-to-noise ratio is less than the predetermined threshold.

[0012] The method according to the first and second implementations can be used to determine whether the signal quality is at an acceptable level and to take appropriate action when the signal quality is below an acceptable level.

[0013] In another implementation, controlling the communication link includes operating the first physical layer device in a fail-safe mode in response to determining that at least one of the data values ​​of the first data register or the second data register indicates a fault in the first physical layer device or the second physical layer device.

[0014] In another implementation, operating the device in fail-safe mode includes suspending operations on the first physical layer device.

[0015] The method may be to operate the communication network in response to detecting that either of a pair of PHY devices in the communication link is malfunctioning.

[0016] In another implementation, the method includes determining whether the communication link is active.

[0017] In another implementation, the method includes restarting the communication link after a period of time.

[0018] The method can be used to restore a PHY device that is malfunctioning due to a temporary or transient fault, but in which the communication link between the PHY device and its link partner remains valid.

[0019] In another implementation, the method includes outputting a fault status indicating a permanent fault in the communication link in response to determining that the communication link is inactive.

[0020] In another implementation, the method includes transmitting the fault status of the communication link to another node in the communication network.

[0021] In another implementation, the other node includes an ECU.

[0022] In another implementation, the method includes: determining the operating mode of the platform at the ECU based on the fault state of the communication link; and controlling the platform to operate in the determined operating mode.

[0023] In another implementation, the method includes establishing a backup communication link in the communication network in response to receiving a fault state indicating a permanent fault.

[0024] The method provides a way to ensure safe operation of a vehicle, wherein the communication link in the vehicle network has been permanently failed.

[0025] In another implementation, the method includes: determining one or more other data values ​​indicating a fault state of the first physical layer device or the second physical layer device; and writing the one or more other data values ​​into the first data register or the second data register.

[0026] These and other aspects of the invention will be apparent from one or more embodiments described below. Attached Figure Description

[0027] To gain a more complete understanding of the invention and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which:

[0028] Figure 1 A schematic diagram of a communication network provided as an example;

[0029] Figure 2 A schematic diagram of nodes in a communication network provided as an example;

[0030] Figure 3 A schematic diagram of a communication network provided as an example;

[0031] Figure 4 A block diagram illustrating a method for controlling communication links in a communication network, provided as an example.

[0032] Figure 5 A block diagram of a method for a communication network provided as an example;

[0033] Figure 6 A simplified schematic diagram of a computing system provided as an example. Detailed Implementation

[0034] Exemplary embodiments will be described in full detail below to enable those skilled in the art to embody and implement the systems and processes described herein. It is important to understand that embodiments may be provided in many alternative forms and should not be construed as limited to the examples listed herein.

[0035] Therefore, while various modifications and alternative forms may be taken in the embodiments, specific embodiments are illustrated in the accompanying drawings and described in detail below as examples. We do not intend to limit the specific forms disclosed. Rather, all modifications, equivalents, and alternatives falling within the scope of the appended claims should be included. Throughout all the drawings and appropriate detailed descriptions, elements of the exemplary embodiments are consistently designated by the same reference numerals.

[0036] The terminology used herein to describe embodiments is not intended to be limiting. The terms “a” and “the” are singular because they refer to a single entity, but their use in this document should not preclude the presence of more than one entity. In other words, unless the context clearly indicates otherwise, an element referenced in the singular may be one or more in number. It should also be understood that the terms “comprises,” “comprising,” “includes,” and / or “including”, when used herein, specify the presence of the stated feature, item, step, operation, element, and / or component, but do not preclude the presence or addition of one or more other features, items, steps, operations, elements, components, and / or groups thereof.

[0037] Unless otherwise defined, all terms used herein (including technical and scientific terms) shall be interpreted in accordance with the conventions of the art. Furthermore, it should be understood that, unless explicitly defined herein, commonly used terms shall also be interpreted in accordance with the conventions of the relevant field and shall not be interpreted in an idealized or overly formal sense.

[0038] Figure 1This is a schematic diagram of a communication network 100 provided as an example. The communication network 100 includes a first node 105 and a second node 110. The first node 105 and the second node 110 communicate through a communication channel 115.

[0039] Based on the examples described herein, communication network 100 can form part of an IVN. Communication network 100 can be used to enable communication between ECUs, including engine control modules (ECMs), power train control modules (PCMs), lights, sensors, airbags, safety features, steering control, braking systems, and other vehicle components.

[0040] Each of nodes 105 and 110 includes physical layer devices 120 and 125, referred to herein as PHY devices. PHY devices 120 and 125 are used to implement physical layer operations according to the Open Systems Interconnection (OSI) model. Specifically, PHY devices 120 and 125 are used to transmit and receive data across the physical medium provided by communication channel 115.

[0041] Each PHY device 120, 125 is communicatively coupled to a microcontroller 130, 135. In this example, the microcontrollers 130, 135 may be implemented as a digital signal processor (DSP) and / or a central processing unit (CPU). The microcontrollers 130, 135 are used to implement at least the data link layer operation according to the OSI model. The data link layer provides node-to-node data transmission and defines the protocols for establishing and terminating connections between two physically connected devices. The data link layer can be subdivided into a medium access control (MAC) layer that controls how devices gain access to the physical medium and the right to transmit data, and a logical link control (LLC) layer that encapsulates the network layer protocols and controls error checking and frame synchronization.

[0042] The OSI model is represented in 140. Figure 1 As described herein, 140 includes a physical layer 145 implemented by PHY devices 120 and 125, a data link layer 150 (also referred to herein as layer 2), and is implemented by microcontrollers 130 and 135, a network layer 155, a transport layer 160, a session layer 165, a presentation layer 170, and an application layer 175. In some cases, in addition to layer 2 operations, microcontrollers 130 and 135 may be used to implement operations from one or more higher layers 180.

[0043] When PHY device 120 receives data, it converts the analog signal from communication channel 115 into a digital signal, which can be interpreted as a bitstream by microcontroller 130. Conversely, PHY device 120 can receive data bits to be transmitted from microcontroller 130 and convert these bits into analog signals for transmission to PHY device 125 via communication channel 115. Microcontroller 130 encapsulates the data in frames according to data link layer protocols, where frames include a header and data packets.

[0044] Figure 2 This is a schematic diagram of node 200 provided as an example. Node 200 includes a microcontroller 210 and a PHY device 220, similar to... Figure 1 The microcontrollers 130 and 135 and the PHY devices 120 and 125 of nodes 105 and 110 are shown.

[0045] PHY device 220 includes control logic 230. Control logic 230 is configured to execute instructions for performing physical layer operations within PHY device 220. Control logic 230 is communicatively coupled to memory register 240. Memory register 240 may include machine-readable instructions for control logic 230. PHY device 220 also includes logic component 250 configured to implement a physical encoding sublayer that interfaces with the MAC sublayer implemented by microcontroller 210 and a physical media attachment sublayer that interfaces directly with the physical media provided by the communication channel. Logic component 250 can execute instructions under the control of control logic 230 to perform symbol encoding, decoding, transmission, and reception of data via communication channel 260.

[0046] exist Figure 2 In this configuration, control logic 230 is communicatively coupled to operations, administration, and management (OAM) encoding module 260 and OAM decoding module 270. OAM encoding module 260 is configured to insert OAM data into the bitstream from microcontroller 210. Specifically, an OAM word comprising multiple OAM bits can be inserted into frames received from microcontroller 210. The OAM word may include data bits used for communication between PHY devices at communication network nodes. OAM decoding module 270 is configured to extract OAM bits from the bitstream received by logic component 250 from communication channel 260.

[0047] Based on the examples described herein, an OAM word may include a global message transmitted to all PHY devices across all nodes in a communication network. In the example, an OAM word may include a local message exchanged between a pair of PHY devices in a communication network. In the example, an OAM word may include an "on-demand query" message, which includes an information request from one PHY device to another. All PHY devices in the communication network implement instructions to decode and interpret the message and perform actions based on the message as needed, such as sending data to a link partner or performing actions on a node in response to an on-demand query.

[0048] PHY device 220 also includes a local PHY status register 280. The local PHY status register 280 is communicatively coupled to control logic 230. As described in the example herein, a fault may occur at the physical layer. The local PHY status register 280 is configured to store data indicating a fault state of PHY device 220.

[0049] As a result of the tests performed at node 200, control logic 230 can read and write data indicating fault status to local register 280. In the example, tests may include a near-end physical coding sublayer (PCS) loopback test indicating whether the PCS of PHY device 220 is functioning correctly. A near-end physical medium attachment (PMA) loopback test indicates whether the PMA sublayer of PHY device 220 is functioning correctly. A far-end loopback test indicates whether cables and connectors are functioning correctly. A cable short-circuit or open-circuit test indicates circuit condition. An undervoltage supply test can determine low-voltage conditions. In some cases, tests can be initiated and / or controlled from higher layers in the network stack.

[0050] PHY device 220 also includes a remote PHY status register 290. The remote PHY status register 290 is communicatively coupled to control logic 230. According to an example, the remote PHY status register 290 may store data indicating a fault state of one or more other PHY devices communicating with PHY device 220.

[0051] According to the example, data from registers 280 and 290 can be transmitted to a link partner communicating with node 200. The contents of registers 280 and 290 can be received and / or transmitted to the link partner using OAM words. In the example, PHY device 220 also includes a global register ( Figure 2 (Not shown in the image), this global register includes data related to network status and other relevant information such as whether nodes are out of order.

[0052] Figure 3This is a schematic diagram of a communication network 300 provided as an example. The communication network 300 can be configured for applications similar to... Figure 1 The communication network 100 shown is part of the IVN of a vehicle or other platform.

[0053] Figure 3 The communication network 300 shown includes an ECU 305. The ECU 305 may be an engine control module, a transmission control module, a transmission control module, a brake control module, a central control module, a central timing module, a general electronic module, a body control module, a suspension control module, a control unit or control module, or any other form of ECU.

[0054] The communication network 300 also includes sensors 310, 315, and 320. Sensors 310, 315, and 320 may include cameras, radar, GPS, or any other type of sensor for a vehicle. The ECU 305 includes a central processing unit 325, which is configured to receive sensor data from sensors 310, 315, and 320 via the communication network 300 and to perform actions in response to the sensor data.

[0055] exist Figure 3 In the example shown, the communication network 300 also includes a brake control module 330. The brake control module 330 is configured to control the brakes using data received from the ECU 305 via the communication network 300. For example, if the sensor 320 is a camera that detects obstacles in front of the vehicle, the central processing unit 325 can cause the generation of a control signal and transmit the control signal to the brake control module 330 to actuate the brakes.

[0056] exist Figure 3 In the example shown, each of sensors 310, 315, 320, ECU 305, and brake control module 330 includes components similar to those previously described and Figure 2 The PHY devices 220 shown are PHY devices 335, 340, 345, 350, and 355. Furthermore, each of nodes 305, 310, 315, 320, and 330 is integrated into a microcontroller, processor, or similar... Figure 2 A higher level network layer (layer 2 or higher) is implemented in the microcontroller 210 shown.

[0057] The communication network 300 also includes network switches 360 and 365. Network switch 360 includes PHY devices 361, 362, and 363, which are connected to the communication links of ECU 305, network switch 370, and sensor 320, respectively. Similarly, network switch 370 includes PHY devices 371, 372, 373, and 374, which are connected to the communication links of network switch 360, brake control module 330, sensor 310, and sensor 315, respectively.

[0058] Network switches 360 and 370 are Layer 2 devices that use MAC addresses to connect different devices in communication network 300 to forward data at the data link layer. Specifically, network switches 360 and 370 may include a microcontroller to perform data link layer operations, but they are not configured to perform higher-level operations, such as network layer operations involving TCP / IP protocols. In other words, network switches 360 and 365 are "dumb" switches, ignoring the processing of higher-level packets in the network stack.

[0059] Figure 3 The PHY devices 335, 340, 345, 350, 355, 361, 362, 363, 371, 372, 373, and 374 shown can communicate with each other using OAM operations. Specifically, global messages can be transmitted to all PHY devices, and local messages can be transmitted between link partners in OAM words. For example, PHY device 372 in switch 370 can transmit local OAM messages to its link partner PHY device 355 in brake control module 330. PHY device 350 can be controlled to transmit global messages in OAM words to all PHY devices.

[0060] In vehicle-mounted networks such as the 300 communication network, faults may occur at the physical layer, thereby compromising the vehicle's normal safety functions. For example, in... Figure 3 In the network shown, ECU 305 can receive indications of obstacles in the road ahead and send braking commands to brake control module 330. If any of the PHY devices 372 and 355, or the communication link between PHY devices 372 and 355, fails, the braking command will not be received, and the vehicle will not stop.

[0061] Figure 4 This is a block diagram of a method 400 for controlling the communication link between a first PHY device and a second PHY device in a communication network. Method 400 can... Figure 3 This is implemented in the communication network 300 shown. For example, method 400 can be executed between PHY devices 372 and 355.

[0062] In block 410, method 400 includes accessing a first data register that includes one or more data values ​​indicating a fault state of a first physical layer device. According to the example, when method 400 is implemented by PHY device 372, PHY device 372 can access its own local PHY status register to obtain data indicating a fault state of PHY device 372. In the example, the data may include data from near-end PCS loopback tests, near-end PMA loopback tests, far-end loopback and / or cable short-circuit or open-circuit tests and / or undervoltage power supply tests performed with PHY device 355.

[0063] In block 420, method 400 includes accessing a second data register that includes one or more data values ​​indicating a fault state of a second physical layer device. For example, when method 400 is implemented by PHY device 372, PHY device 372 may access a remote PHY status register that includes data indicating a fault state of PHY device 355.

[0064] In block 430, method 400 includes evaluating the signal quality of the communication link. Figure 3 In this example, PHY device 372 can evaluate the signal quality of the communication link with PHY device 355. In this example, evaluating signal quality may include comparing the signal-to-noise ratio of the communication link with a predetermined threshold.

[0065] In block 440, method 400 includes controlling a communication link at a first physical layer device based on one or more data values ​​of a first data register, one or more data values ​​of a second data register, and signal quality. According to an example, controlling the communication link at the first physical layer device includes restarting the communication link at the first physical layer device in response to determining that the signal-to-noise ratio is less than a predetermined threshold.

[0066] According to one example, controlling the communication link includes operating the first physical layer device in a fail-safe mode in response to determining that at least one of the data values ​​in a first data register or a second data register indicates a fault in the first physical layer device or the second physical layer device.

[0067] For example, the data value in the remote PHY status register of PHY device 372 can indicate that the PMA sublayer of PHY device 355 is not working. In this case, PHY device 372 can operate in fail-safe mode. According to the example, operating in fail-safe mode can include suspending operations at the PHY device.

[0068] In the example, method 400 may further include determining whether the communication link is valid, i.e., whether data is still being communicated between the PHY devices. If communication remains active, the PHY devices may restart the link after a period of time, as the failure may be temporary or transient. Otherwise, if the communication link is inactive, the PHY devices may output data indicating a permanent failure.

[0069] In some cases, the fault status of the PHY device and / or communication link can be transmitted back to the ECU 305 to allow the ECU 305 to take further action. In some cases, the ECU 305 can switch to a different operating mode in response to data received from the PHY device in the communication link. For example, if a link fails between PHY devices 372 and 355, PHY device 372 can transmit this information back to the ECU 305, which can then decide whether to operate the vehicle in fail-safe or backup mode. This could include, for example, establishing a backup link to the brake control module 330.

[0070] As an example, the local and remote PHY status registers of all PHY devices can be updated periodically, for example, when a PHY device performs tests with other PHY devices in the network. PHY devices can use the OAM function to communicate data from their registers to each other. Therefore, all PHY devices can store the latest copy of health information related to their link partners in the network.

[0071] Figure 5 A block diagram of method 500 provided as an example. Method 500 can be used in conjunction with other examples and methods described herein, particularly with... Figure 4 The methods shown in 400 are used in combination. Method 500 can be used in... Figure 2 This is implemented in PHY devices such as PHY device 220 shown.

[0072] Method 500 can be used to determine the PHY device's response to a fault based on its overall health status. Health status can be assessed by continuously monitoring the relevant local and remote PHY status registers of the local PHY device, as well as the signal quality of the communication link between the local and remote PHY devices.

[0073] Based on the example described herein, a four-level classification {1, –1, –2, –3} can be used to represent different health states of PHY devices and connections based on whether the health status is good (1) or whether there is a transient fault (–1), temporary fault (–2), or permanent fault (–3). In the example, the health status can be stored in a dedicated health status register in the PHY device.

[0074] When the health status is "+1", the data values ​​in the local PHY status register and the remote PHY status register indicate that the PHY device is working normally, the signal quality is good, and the overall health status is good.

[0075] A health status of "-1" indicates that the local and remote PHY devices are functioning correctly, but the signal quality is deteriorating and has fallen below a threshold. In this case, the fault is transient, as the signal quality may improve.

[0076] A health status indicator of "-2" is given if at least one data value in the local and / or remote PHY status registers indicates a problem with one of the PHY devices. This may occur when the data received by a PHY device is incorrect, but the link between the PHY devices remains valid. In this case, the fault may be transient and can be repaired after a period of time.

[0077] A health status indicator is "-3" if at least one data value in the local and / or remote PHY status registers indicates a problem with one of the PHY devices and there is no active link between the PHYs. In this case, the fault is permanent and may be due to power loss, insufficient voltage, permanent contact loss in cables or connectors, or a short circuit or break in the cable.

[0078] In box 510, the method includes determining whether the health status of the PHY device is good. In other words, whether the health status is +1 according to the above classification. If so, the PHY device continues to monitor the PHY status register and link quality.

[0079] If not, then in block 520, the PHY device determines whether the fault is transient based on the health status, i.e., whether the health status is -1. If yes, then in block 530, the PHY device determines whether the signal quality improves after a short period of time. If the signal quality improves after a short period of time, the PHY device can return the health status to +1 to indicate that the link quality is good, and the register indicates that the PHY device has no problem.

[0080] If the fault is not transient or the signal quality does not improve after a short period of time, the PHY device operates in fail-safe mode in block 540. If not, in block 550, the PHY device determines whether the fault is temporary, i.e., whether the health state is -2. If yes, in block 560, the PHY device waits for a random time interval for the temporary fault to resolve. If no, in block 570, the PHY device determines whether the fault is permanent, i.e., whether the health state is -3. If the fault is permanent, in block 580, the link is repaired. In some cases, this may include physically repairing the link or rerouting data via a different link. In block 590, the communication link is restarted when the health state returns to +1.

[0081] The method described in this paper enables the PHY device to establish its fault status and connection to another network node. This health status information can be sent back to the ECU, allowing the ECU to take appropriate action. The method utilizes PHY layer OAM messaging technology and testing. This reduces latency and processing power, and provides a convenient method for monitoring PHY devices for functional safety in automotive networks.

[0082] The invention is described in conjunction with flowcharts and / or block diagrams of methods, apparatus, and systems provided in the examples of the invention. Although the flowcharts above show a specific execution sequence, the execution sequence may differ from that described. A block described in conjunction with one flowchart may be combined with a block described in conjunction with another flowchart. In some examples, some blocks in the flowcharts may not be necessary and / or additional blocks may be added. It should be understood that each flowchart and / or block in the flowcharts and / or block diagrams, as well as combinations of flowcharts and / or diagrams in the flowcharts and / or block diagrams, can be implemented by the machine-readable instructions described herein.

[0083] For example, the machine-readable instructions can be executed by a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to implement the functions described in the specific embodiments and figures. Specifically, a processor or processing device can execute the machine-readable instructions. Therefore, modules of the device can be implemented by a processor that executes machine-readable instructions stored in memory, or by a processor that operates according to instructions embedded in logic circuitry. The term "processor" should be interpreted broadly to include CPUs, processing units, logic units, or sets of programmable gates, etc. These methods and modules can be executed by a single processor or partitioned by multiple processors. Such machine-readable instructions can also be stored in a computer-readable storage device that can instruct a computer or other programmable data processing device to operate in a specific mode.

[0084] Such machine-readable instructions can also be loaded onto a computer or other programmable data processing device to cause the computer or other programmable data processing device to perform a series of operations to generate computer-implemented processing instructions, so that the instructions executed on the computer or other programmable device will provide operations for implementing the functions specified by the flow in the flowchart and / or the boxes in the block diagram.

[0085] Figure 6 This is a block diagram of a computing system 600 that can be used to implement the methods, apparatus, and systems disclosed herein. A particular device may utilize all or only a subset of the components shown, and the degree of integration between devices may vary. Furthermore, a device may include multiple component instances, such as multiple processing units, processors, memory, transmitters, and receivers. The computing system 600 includes a processing unit 602. The processing unit includes a central processing unit (CPU) 614, a graphics processing unit (GPU) 616, and memory 608, and may also include a mass storage device 604 connected to a bus 618, a video adapter 610, and an I / O interface 612.

[0086] Bus 618 can be one or more of several bus architectures of any type, including a memory bus or memory controller, a peripheral bus, or a video bus. CPU 614 and GPU 616 can include any type of electronic data processor. Memory 608 can include any type of non-transitory system memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or combinations thereof. In an embodiment, memory 508 may include ROM used at power-on and DRAM storing programs and data used during program execution.

[0087] Mass storage 604 may include any type of non-transitory storage device for storing data, programs, and other information, and making such data, programs, and other information accessible via bus 618. Mass storage 604 may include one or more of solid-state drives, hard disk drives, disk drives, or optical disk drives.

[0088] Video adapter 610 and I / O interface 612 provide interfaces to couple external input and output devices to processing unit 602. Examples of input and output devices, as shown, include a display 620 coupled to video adapter 610 and a mouse, keyboard, and printer 622 coupled to I / O interface 612. Other devices may be coupled to processing unit 602, and additional or fewer interface cards may be used. For example, a serial interface such as Universal Serial Bus (USB) (not shown) may be used to provide interfaces to external devices.

[0089] The processing unit 602 also includes one or more network interfaces 606, which may include wired links such as Ethernet cables and / or wireless links for accessing nodes or different networks. The network interface 606 allows the processing unit 602 to communicate with remote units via a network. For example, the network interface 606 may provide wireless communication via one or more transmitters / transmit antennas and one or more receivers / receive antennas. In one embodiment, the processing unit 602 is coupled to a local area network 624 or a wide area network for processing data and communicating with other processing units, the Internet, or remote devices such as remote storage facilities.

[0090] Although the invention and its advantages have been described in detail, it should be understood that various changes, substitutions and modifications can be made to the invention without departing from the spirit and scope of the invention as defined in the appended claims.

[0091] This invention may be embodied in other specific apparatuses and / or methods. The described embodiments are to be considered illustrative rather than restrictive in all respects. In particular, the scope of the invention is indicated by the appended claims rather than by the description and drawings herein. All modifications falling within the equivalent meaning and scope of the claims should be included within their scope.

Claims

1. A method for establishing a communication link between a first physical layer device and a second physical layer device in a communication network for a control platform, characterized in that, The method includes, at the first physical layer device: Access a first data register, wherein the first data register includes one or more data values ​​indicating a fault state of the first physical layer device; Access a second data register, wherein the second data register includes one or more data values ​​indicating the fault state of the second physical layer device; Assess the signal quality of the communication link; The communication link at the first physical layer device is controlled based on the one or more data values ​​of the first data register, the one or more data values ​​of the second data register, and the signal quality.

2. The method according to claim 1, characterized in that, Evaluating the signal quality includes comparing the signal-to-noise ratio of the communication link with a predetermined threshold.

3. The method according to claim 2, characterized in that, The control of the communication link at the first physical layer device includes restarting the communication link at the first physical layer device in response to determining that the signal-to-noise ratio is less than the predetermined threshold.

4. The method according to claim 1, characterized in that, The control of the communication link includes operating the first physical layer device in a fail-safe mode in response to determining that at least one of the data values ​​in the first data register or the second data register indicates a fault in the first physical layer device or the second physical layer device.

5. The method according to claim 4, characterized in that, Operating the device in fail-safe mode includes suspending operations on the first physical layer device.

6. The method according to claim 4, characterized in that, It also includes determining whether the communication link is active.

7. The method according to claim 6, characterized in that, This includes restarting the communication link after a period of time.

8. The method according to claim 6, characterized in that, This includes outputting a fault status indicating a permanent fault in the communication link in response to determining that the communication link is inactive.

9. The method according to claim 8, characterized in that, It also includes transmitting the fault status of the communication link to another node in the communication network.

10. The method according to claim 9, characterized in that, The other node includes the electronic control unit (ECU).

11. The method according to claim 10, characterized in that, include: Based on the fault status of the communication link, determine the operating mode of the platform at the ECU; Control the platform to operate in a defined operating mode.

12. The method according to claim 8, characterized in that, It also includes establishing a backup communication link in the communication network in response to receiving a fault status indicating a permanent fault.

13. The method according to claim 1, characterized in that, include: Determine one or more other data values ​​that indicate the fault status of the first physical layer device or the second physical layer device; Write the one or more other data values ​​into the first data register or the second data register.

14. A node in a communication network of a platform, characterized in that, The nodes include: Physical layer device, the physical layer device comprising: A first data register is used to store data indicating the fault status of the physical layer device; The second data register is used to store data indicating the fault status of the second physical layer device that communicates with the physical layer device via the communication link. The physical layer device is used for: Access one or more data values ​​stored in the first data register; Access one or more data values ​​stored in the second data register; Evaluate the signal quality of the communication link between the physical layer device and the second physical layer device; Based on the one or more data values ​​of the first data register and the one or more data values ​​of the second data register The data values ​​and the signal quality control the communication link.

15. The node according to claim 14, characterized in that, The physical layer device is used to compare the signal-to-noise ratio of the communication link with a predetermined threshold.

16. The node according to claim 15, characterized in that, In order to control the communication link, the physical layer device is configured to restart the communication link in response to determining that the signal-to-noise ratio is less than the predetermined threshold.

17. The node according to claim 14, characterized in that, In order to control the communication link, the physical layer device is configured to operate in a fail-safe mode in response to determining that at least one of the data values ​​in the first data register or the second data register indicates a fault in the physical layer device or the second physical layer device.

18. The node according to claim 14, characterized in that, The physical layer device is used to determine whether the communication link is active.

19. The node according to claim 18, characterized in that, The physical layer device is used to restart the communication link after a period of time.

20. An electronic control unit (ECU) for a communication network in a platform, characterized in that, The electronic control unit is used to perform the method according to any one of claims 1 to 13 of this application, and the electronic control unit includes: processor; A memory communicatively coupled to the processor, wherein the memory stores instructions, when implemented on the processor, The above instructions cause the processor to: Receive the fault status of the communication link in the communication network; Based on the fault status of the communication link, determine the operating mode of the platform at the ECU; Control the platform to operate in a defined operating mode.

Images