CN117203945A - Method and system for a communication network - Google Patents

Method and system for a communication network Download PDF

Info

Publication number
CN117203945A
CN117203945A CN202180097478.9A CN202180097478A CN117203945A CN 117203945 A CN117203945 A CN 117203945A CN 202180097478 A CN202180097478 A CN 202180097478A CN 117203945 A CN117203945 A CN 117203945A
Authority
CN
China
Prior art keywords
physical layer
layer device
communication link
data
data register
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202180097478.9A
Other languages
Chinese (zh)
Inventor
苏扬·潘迪
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of CN117203945A publication Critical patent/CN117203945A/en
Pending legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40Bus networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40Bus networks
    • H04L2012/40267Bus for use in transportation systems
    • H04L2012/40273Bus for use in transportation systems the transportation system being a vehicle

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 the following steps: at the first physical layer device, accessing a first data register, wherein the first data register includes one or more data values indicative of a failure state of the first physical layer device; accessing a second data register, wherein the second data register includes one or more data values indicative of a failure state of the second physical layer device; evaluating the signal quality of the communication link; the communication link at the first physical layer device is controlled 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

Method and system for a communication network
Technical Field
The present invention relates to a method and a system for a communication network. In particular, the methods and systems described herein relate to operation of communication links in a communication network.
Background
Modern vehicles are lined with increasingly complex sensors, on-board computers, and other types of hardware devices. These devices are controlled by a central electronic control unit (Electronic Control Unit, ECU), which acts as the brain of the vehicle. The ECU acquires sensor data and performs instruction communication with other devices through an In-Vehicle Network (IVN).
The use of ECU centralized control minimizes the computational complexity of the nodes in the IVN because the individual devices do not have to perform data analysis to determine their next operation. However, the safe operation of the vehicle depends on the normal running of the network to ensure that the correct instructions are received from the ECU at the node.
Disclosure of Invention
It is an object of the present invention to provide a method for controlling a communication link between a first physical layer device and a second physical layer device in a communication network, such as an in-vehicle network.
The above and other objects are achieved by the features of the independent claims. Other implementations are apparent in the dependent claims, the description and the drawings.
According to a first aspect, 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 the following steps: at the first physical layer device, accessing a first data register, wherein the first data register includes one or more data values indicative of a failure state of the first physical layer device; accessing a second data register, wherein the second data register includes one or more data values indicative of a failure state of the second physical layer device; evaluating the signal quality of the communication link; the communication link at the first physical layer device is controlled 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.
According to the method of the first aspect, a failure state of a communication link between PHY devices in a communication network is established based on information stored or determined locally by one of the PHY devices.
According to a second aspect, a node in a communication network of a platform is provided. The node comprises a physical layer device, wherein the physical layer device comprises: a first data register for storing data indicative of a failure state of the physical layer device; a second data register for storing data indicative of a failure state of a second physical layer device in communication with the physical layer device over a communication link. The physical layer device is configured to: accessing one or more data values stored in the first register; accessing one or more data values stored in the second register; evaluating signal quality of a communication link between the physical layer device and the second physical layer device; the communication link is controlled in dependence upon 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.
According to a third aspect, an electronic control unit (electronic control unit, ECU) for a communication network of a platform is provided. The electronic control unit includes: a processor; a memory communicatively coupled to the processor. The memory stores instructions that, when implemented on the processor, cause the processor to receive a failure state of a communication link in the communication network; determining an operating mode of the platform at the ECU based on the fault condition of the communication link and controlling the platform to operate in the determined operating mode.
In one implementation, the evaluating signal quality includes comparing a signal-to-noise ratio of the communication link to a predetermined threshold.
In one implementation, the 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.
The method according to the first and second implementation forms may be used to determine whether the signal quality is at an acceptable level and take appropriate action when the signal quality is below the acceptable level.
In another implementation, the 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 failure at the first physical layer device or the second physical layer device.
In another implementation, the operating the device in the fail-safe mode includes suspending operation on the first physical layer device.
The method may be to operate the communication network in response to detecting that any one of a pair of PHY devices in the communication link is malfunctioning.
In another implementation, the method includes determining whether the communication link is active.
In another implementation, the method includes restarting the communication link after a period of time has elapsed.
The method may be used to restore a communication link where a temporary or transient failure causes the PHY device to function improperly, but the communication link between the PHY device and the link partner is still valid.
In another implementation, the method includes outputting a fault state indicating a permanent fault in the communication link in response to determining that the communication link is not active.
In another implementation, the method includes transmitting the fault condition of the communication link to another node of the communication network.
In another implementation, the other node comprises an electronic control unit (Electronic Control Unit, ECU).
In another implementation, the method includes: determining an operating mode of the platform at the ECU based on the fault condition of the communication link; the platform is controlled to operate in a determined mode of operation.
In another implementation, the method includes establishing a backup communication link in the communication network in response to receiving a fault condition indicating a permanent fault.
The method provides a method of safe operation of a vehicle, wherein a communication link in an on-board network has permanently failed.
In another implementation, the method includes: determining one or more other data values indicative of a failure state of the first physical layer device or the second physical layer device; the one or more other data values are written to the first data register or the second data register.
These and other aspects of the invention are apparent from and will be elucidated with reference to one or more embodiments described hereinafter.
Drawings
For a more complete understanding of the present invention, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:
FIG. 1 is a schematic illustration of a communication network provided by one example;
FIG. 2 is a schematic diagram of a node of a communication network provided by one example;
FIG. 3 is a schematic diagram of a communication network provided by one example;
FIG. 4 is a block diagram of a method for controlling a communication link in a communication network provided by one example;
FIG. 5 is a block diagram of a method for a communication network provided by one example;
FIG. 6 is a simplified schematic diagram of a computing system provided by one example.
Detailed Description
The exemplary embodiments will be described in sufficient detail to enable those of ordinary skill in the art to embody and implement the systems and procedures described herein. It is important to understand that the embodiments can be provided in many alternative forms and should not be construed as being limited to only the examples set forth herein.
Thus, while the embodiments may be modified and take various alternative forms, specific embodiments are shown in the drawings and will be described in detail below by way of example. We do not intend to limit the particular forms disclosed. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the scope of the appended claims. Elements of the exemplary embodiments are consistently indicated by the same reference numerals throughout the drawings and the appropriate detailed description.
The terminology used herein to describe the embodiments is not intended to be limiting in scope. "A" or "an" or "the" is singular in the sense of having a single indicator, but use of the singular in this document does not exclude the presence of more than one indicator. In other words, elements referred to in the singular may be one or more in number unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used herein, specify the presence of stated features, items, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, items, steps, operations, elements, components, and/or groups thereof.
Unless otherwise defined, all terms (including technical and scientific terms) used herein should be interpreted as usual in the art. Furthermore, it will be further understood that terms, such as those commonly used herein, should be interpreted as having a meaning that is not necessarily intended to be interpreted in an idealized or overly formal sense unless expressly so defined herein.
Fig. 1 is a schematic diagram of a communication network 100 provided by one example. The communication network 100 comprises a first node 105 and a second node 110. The first node 105 and the second node 110 communicate via a communication channel 115.
According to the examples described herein, the communication network 100 may form part of an in-vehicle network (IVN). The communication network 100 may be used to enable communication between electronic control units (electronic control unit, ECU) and the like, including engine control modules (engine control module, ECM), driveline control modules (power train control module, PCM), lights, sensors, airbags, safety features, steering control, braking systems, and other vehicle components.
Each of the nodes 105, 110 includes a physical layer device 120, 125, referred to herein as a PHY device. The PHY devices 120, 125 are configured to implement physical layer operations according to the open systems interconnection (Open Systems Interconnection, OSI) model. In particular, PHY devices 120, 125 are used to transmit and receive data across the physical medium provided by communication channel 115.
Each PHY device 120, 125 is communicatively coupled to a microcontroller 130, 135. In an example, the microcontrollers 130, 135 may be implemented as a digital signal processor (digital signal processor, DSP) and/or a central processing unit (central processing unit, CPU). The microcontrollers 130, 135 are configured to implement at least data link layer operations according to the OSI model. The data link layer provides node-to-node data transfer and defines the protocols that establish and terminate connections between two physically connected devices. The data link layer can be subdivided into a medium access control (Medium access control, MAC) layer that controls how devices gain access to the physical medium and permission to transmit data, and a logical link control (Logical link control, LLC) layer that encapsulates the network layer protocols, and controls error checking and frame synchronization.
A representation 140 of the OSI model is depicted in fig. 1. The representation 140 includes a physical layer 145 implemented by the PHY devices 120, 125, a data link layer 150, also referred to herein as layer 2, and is implemented by the microcontrollers 130, 135, a network layer 155, a transport layer 160, a session layer 165, a representation layer 170, and an application layer 175. In some cases, microcontrollers 130, 135 may be used to implement operations from one or more higher layers 180 in addition to layer 2 operations.
When the PHY device 120 receives the data, the PHY device 120 converts the analog signal from the communication channel 115 to a digital signal that can be interpreted by the microcontroller 130 as a code stream. Instead, PHY device 120 may receive data bits to be transmitted from microcontroller 130 and convert the bits to analog signals for transmission to PHY device 125 over communication channel 115. The microcontroller 130 encapsulates the data in frames according to a data link layer protocol, wherein the frames include a header of bits and a data packet.
Fig. 2 is a schematic diagram of a node 200 provided in one example. Node 200 includes a microcontroller 210 and a PHY device 220, similar to microcontrollers 130, 135 and PHY devices 120, 125 of nodes 105, 110 shown in fig. 1.
PHY device 220 includes control logic 230. Control logic 230 is configured to execute instructions for performing physical layer operations in PHY device 220. Control logic 230 is communicatively coupled to memory registers 240. Memory registers 240 may include machine-readable instructions for control logic 230. PHY device 220 further includes a logic component 250 configured to implement a physical coding sublayer that interfaces with a MAC sublayer implemented by microcontroller 210 and a physical medium attachment sublayer that interfaces directly with a physical medium provided by a communication channel. Logic component 250 may execute instructions under the control of control logic 230 to perform symbol encoding, decoding, transmission, and reception of data over communication channel 260.
In fig. 2, control logic 230 is communicatively coupled to Operations, administration, and maintenance (OAM) encoding module 260 and OAM decoding module 270. The OAM coding module 260 is arranged to insert OAM data into the code stream from the microcontroller 210. Specifically, an OAM word including a plurality of OAM bits may be inserted into a frame received from microcontroller 210. The OAM word may include data bits communicated between PHY devices at the communication network node. OAM decoding module 270 is arranged to extract OAM bits from the code stream received by logic component 250 from communication channel 260.
According to examples described herein, an OAM word may include a global message that is transmitted to all PHY devices across all nodes in a communication network. In an example, the OAM word may include a native message exchanged between a pair of PHY devices in the communication network. In an example, the OAM word may include an "on demand query" message that includes a request for information from one PHY device to another PHY device. All PHY devices in the communication network implement instructions to decode and interpret the messages and perform actions on the messages as needed, such as sending data to link partners or performing actions on nodes in response to on-demand queries.
PHY device 220 also includes a local PHY status register 280. The local PHY status register 280 is communicatively coupled to the control logic 230. According to the examples described herein, the failure may occur at the physical layer. The local PHY status register 280 is configured to store data indicative of a fault condition of the PHY device 220.
As a result of the node 200 performing the test, the control logic 230 may read and write data indicative of the fault condition to the local register 280. In an example, the test may include a near-end physical coding sublayer (Physical Coding Sublayer, PCS) loopback test that indicates whether the PCS of PHY device 220 is operational. The near-end physical medium attachment (Physical Medium Attachment, PMA) loop-back test indicates whether the PMA sublayer of the PHY device 220 is operating properly. The distal loop indicates whether the cable and connector are functioning properly. The cable short or open test indicates a circuit condition. The under-voltage power supply test may determine a low voltage condition. In some cases, testing may be initiated and/or controlled from higher layers in the network stack.
PHY device 220 also includes a remote PHY status register 290. Remote PHY status register 290 is communicatively coupled to control logic 230. According to an example, remote PHY status register 290 may store data indicating a fault status of one or more other PHY devices in communication with PHY device 220.
According to an example, data from registers 280, 290 may be transmitted to a link partner in communication with node 200. The contents of registers 280, 290 may be received and/or transmitted to a link partner using OAM words. In an example, PHY device 220 also includes global registers (not shown in fig. 2) that include data related to network status and other relevant information as to whether the nodes are out of order.
Fig. 3 is a schematic diagram of a communication network 300 provided by an example. The communication network 300 may form part of an in-vehicle network (IVN) for a vehicle or other platform similar to the communication network 100 shown in fig. 1.
The communication network 300 shown in fig. 3 includes an ECU 305. The ECU 305 may be an engine control module, a driveline control module, a transmission control module, a brake 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.
The communication network 300 further comprises sensors 310, 315, 320. The sensors 310, 315, 320 may include cameras, radar, GPS, or any other type of sensor for a vehicle. The ECU 305 comprises a central processing unit 325, the central processing unit 325 being arranged to receive sensor data from the sensors 310, 315, 320 via the communication network 300 and to perform actions in response to the sensor data.
In the example shown in fig. 3, the communication network 300 further includes a brake control module 330. The brake control module 330 is configured to control the brake actuators via data received from the ECU 305 via the communication network 300. For example, where the sensor 320 is a camera that detects an obstacle ahead of the vehicle, the central processing unit 325 may cause a control signal to be generated and transmitted to the brake control module 330 to actuate the brakes.
In the example shown in fig. 3, each of the sensors 310, 315, 320, ECU 305, and brake control module 330 includes a PHY device 335, 340, 345, 350, 355 similar to the PHY device 220 described previously and shown in fig. 2. In addition, each of the nodes 305, 310, 315, 320, 330 implements a higher level network layer (layer 2 or higher) in a microcontroller, processor, or microcontroller 210 similar to that shown in fig. 2.
The communication network 300 also includes network switches 360, 365. The network switch 360 includes PHY devices 361, 362, 363 that are connected to the communications links of the ECU 305, the network switch 370, and the sensor 320, respectively. Similarly, network switch 370 includes PHY devices 371, 372, 373, 374 that are connected to the communication links of network switch 360, brake control module 330, sensor 310, and sensor 315, respectively.
The network switches 360, 370 are layer 2 devices that use MAC addresses to connect different devices in the communication network 300 to forward data at the data link layer. In particular, the network switches 360, 370 may include microcontrollers to perform data link layer operations, but they are not configured to perform higher layer operations, such as network layer operations involving the TCP/IP protocol. In other words, the network switches 360, 365 are "dumb" switches that are not visible to the processing of higher data packets in the network stack.
The PHY devices 335, 340, 345, 350, 355, 361, 362, 363, 371, 372, 373, 374 shown in fig. 3 may communicate with each other using OAM operations. In particular, global messages may be transmitted to all PHY devices, and local messages may be transmitted in OAM words between link partners. For example, PHY device 372 in switch 370 may transmit a local OAM message to its link partner PHY device 355 in the brake control module 330. PHY device 350 may be controlled to transmit the global message in the OAM word to all PHY devices.
In an in-vehicle network such as the communication network 300, a malfunction may occur in the physical layer, thereby deteriorating normal security functions of the vehicle. For example, in the network shown in fig. 3, the ECU 305 may receive an indication of an obstacle in the road ahead and send a brake command to the brake control module 330. If either of the PHY devices 372, 355 or the communication link between PHY device 372 and PHY device 355 fails, no brake command is received and the vehicle does not stop.
Fig. 4 is a block diagram of a method 400 for controlling a communication link between a first PHY device and a second PHY device in a communication network. The method 400 may be implemented in the communication network 300 shown in fig. 3. For example, method 400 may be performed between PHY devices 372, 355.
In block 410, the method 400 includes accessing a first data register including one or more data values indicative of a failure state of a first physical layer device. According to an example, when method 400 is implemented by PHY device 372, PHY device 372 may access its own local PHY status register to obtain data indicative of the failure state of PHY device 372. In an example, the data may include data from a near-end PCS loopback test, a near-end PMA loopback test, a far-end loopback and/or cable short or open circuit test, and/or an under-voltage power supply test performed with PHY device 355.
In block 420, the method 400 includes accessing a second data register including one or more data values indicative of a failure 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 status of PHY device 355.
In block 430, the method 400 includes evaluating a signal quality of the communication link. In fig. 3, PHY device 372 may evaluate the signal quality of the communication link with PHY device 355. In an example, evaluating the signal quality may include comparing a signal-to-noise ratio of the communication link to a predetermined threshold.
In block 440, the method 400 includes controlling a 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. 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.
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 of the first data register or the second data register indicates a failure at the first physical layer device or the second physical layer device.
For example, a data value in a remote PHY status register of PHY device 372 may indicate that a PMA sublayer of PHY device 355 is not operational. In this case, PHY device 372 may operate in a fail-safe mode. According to an example, operating in the fail-safe mode may include suspending operation at the PHY device.
In an example, the method 400 may further include determining whether the communication link is active, i.e., whether data is still being communicated between PHY devices. If the communication is still active, the PHY device may restart the link after a period of time because the failure may be temporary or transient. Otherwise, if the communication link is inactive, the PHY device may output data indicating that a permanent failure exists.
In some cases, a failure state of the PHY device and/or the communication link may be transmitted back to the ECU 305 to allow the ECU 305 to take further action. In some cases, the ECU 305 may switch to a different mode of operation in response to data received from the PHY devices in the communication link. For example, if the link between PHY devices 372, 355 fails, PHY device 372 may transmit this information back to ECU 305, and ECU 305 may then decide to operate the vehicle in a fail-safe or backup mode. This may include, for example, establishing a backup link to the brake control module 330.
According to an example, the local and remote PHY status registers of all PHY devices may be updated periodically, such as by the PHY device performing a test with other PHY devices in the network. PHY devices may communicate data from registers to each other using OAM functions. Thus, all PHY devices may store up-to-date copies of health information related to link partners in their networks.
Fig. 5 is a block diagram of a method 500 provided by an example. The method 500 may be used in conjunction with other examples and methods described herein, and in particular with the method 400 shown in fig. 4. The method 500 may be implemented in a PHY device such as the PHY device 220 shown in fig. 2.
The method 500 may be used to determine a response of a PHY device to a fault based on the overall health status. Health may be assessed by continuously monitoring the local PHY status registers associated with the local PHY device and the remote PHY status registers and the signal quality of the communication link between the local and remote PHY devices.
According to examples described herein, the four-layer classification {1, -2, -3} may be used to represent different health states of PHY devices and connections depending on whether the health state is good (1) or whether there is a transient fault (-1), a temporary fault (-2), or a permanent fault (-3). In an example, the health status may be stored in a dedicated health status register in the PHY device.
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 functioning properly, and the signal quality is good, indicating that the overall health status is good.
The health status is "-1" if the values in the local and remote PHY status registers indicate that the local and remote PHY devices are working properly, but the signal quality is decreasing and has been less than the threshold. In this case, the failure is instantaneous, as the signal quality may improve.
Health status indicates "-2" if at least one data value in the local and/or remote PHY status registers indicates that one of the PHY devices is in problem. The data received at the PHY devices may be incorrect, but the link between the PHY devices is still valid. In this case, the fault may be transient and may be repaired after a time interval has elapsed.
Health status indicates "-3" if at least one data value in the local and/or remote PHY status registers indicates that one of the PHY devices is problematic and there is no active link between PHYs. In this case, the fault is permanent, possibly due to power loss, insufficient voltage, permanent contact loss of the cable or connector, or a short circuit or break of the cable.
In block 510, the method includes determining whether the health of the PHY device is good. In other words, according to the above classification, the health condition is +1. If so, the PHY device continues to monitor the PHY status register and link quality.
If not, in block 520, the PHY device determines if the fault is a transient fault based on the health status, i.e., if the health status is a-1. If so, in block 530, the PHY device determines whether the signal quality improves after a brief period of time has elapsed. If the signal quality improves after a short time, the PHY device may 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.
If the fault is not transient or the signal quality does not improve after a short period of time has elapsed, then in block 540 the PHY device operates in a fail-safe mode. If not, in block 550, the PHY device determines whether the fault is a temporary fault, i.e., whether the health status is-2. If so, in block 560, the PHY device waits for a random time interval for temporary failover. If not, in block 570, the PHY device determines whether the fault is permanent, i.e., whether the health status is-3. If the failure is permanent, then in block 580 the link is repaired. In some cases, this may include physically repairing the link or rerouting the data through a different link. In block 590, the communication link is restarted when the health status returns to +1.
The methods described herein cause a PHY device to establish a failure state of the PHY device and a connection with another network node. This health status information may be sent back to the ECU so that the ECU may take appropriate action. The methods described herein utilize PHY layer OAM messaging techniques and testing. This reduces latency and processing power and provides a convenient method for PHY device monitoring for in-vehicle network function security.
The present invention is described in connection with flowchart and/or block diagrams of methods, apparatus and systems according to examples of the invention. Although the above-described flowcharts show a particular order of execution, the order of execution may vary from that described. Blocks described in connection with one flowchart may be combined with blocks described in connection with another flowchart. In some examples, some blocks of the flowchart may not be necessary and/or additional blocks may be added. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or diagrams in the flowchart illustrations and/or block diagrams, can be implemented by machine-readable instructions.
For example, the machine-readable instructions may be executed by a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to implement the functions as described in the detailed description and figures. In particular, a processor or processing device may execute the machine-readable instructions. Thus, the modules of the apparatus may be implemented by a processor executing machine-readable instructions stored in a memory, or a processor operating in accordance with instructions embedded in logic circuitry. The term "processor" should be broadly interpreted to include a CPU, a processing unit, a logic unit, a set of programmable gates, and the like. The methods and modules may be performed by a single processor or may be divided by multiple processors. Such machine-readable instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular mode.
Such machine-readable instructions may also be loaded onto a computer or other programmable data processing apparatus to cause the computer or other programmable apparatus to perform a series of operations to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart flow and/or block diagram block or blocks.
Fig. 6 is a block diagram of a computing system 600 that may be used to implement the methods, devices, 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. Further, the device may include multiple component instances, e.g., multiple processing units, processors, memories, transmitters, receivers. The computing system 600 includes a processing unit 602. The processing units include a central processing unit (central processing unit, CPU) 614, a graphics processing unit (graphics processing unit, GPU) 616, memory 608, and may also include a mass storage device 604 connected to bus 618, video adapter 610, and I/O interface 612.
Bus 618 may be one or more of any type of several bus architectures including a memory bus or memory controller, a peripheral bus, or a video bus. The CPU 614 and GPU 616 may comprise any type of electronic data processor. Memory 608 may include any type of non-transitory system memory, such as static random access memory (static random access memory, SRAM), dynamic random access memory (dynamic random access memory, DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or a combination thereof. In an embodiment, the memory 508 may include ROM for use at power-on and DRAM for storing programs and data for use when executing programs.
Mass memory 604 may include any type of non-transitory storage device for storing and making accessible via bus 618 data, programs, and other information. The mass storage 604 may include one or more of a solid state drive, a hard disk drive, a magnetic disk drive, or an optical disk drive, etc.
Video adapter 610 and I/O interface 612 provide interfaces to couple external input and output devices to processing unit 602. As shown, examples of input and output devices include a display 620 coupled to the video adapter 610 and a mouse, keyboard, printer 622 coupled to the I/O interface 612. Other devices may be coupled to the processing unit 602 and may utilize additional or fewer interface cards. For example, a serial interface such as a universal serial bus (Universal Serial Bus, USB) (not shown) may be used to provide the interface to an external device.
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 to access nodes or different networks. The network interface 606 allows the processing unit 602 to communicate with remote units over a network. For example, the network interface 606 may provide wireless communications via one or more transmitters/transmit antennas and one or more receivers/receive antennas. In one embodiment, the processing unit 602 is coupled with a local area network 624 or wide area network for processing data and communicating with other processing units, the Internet, or remote storage facilities, among other remote devices.
Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention as defined by the appended claims.
The present invention may be embodied in other specific apparatus and/or methods. The described embodiments are to be considered in all respects only as illustrative and not restrictive. In particular, the scope of the invention is indicated by the appended claims rather than by the description and drawings herein. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims (20)

1. 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, the method comprising, at the first physical layer device:
accessing a first data register, wherein the first data register includes one or more data values indicative of a failure state of the first physical layer device;
accessing a second data register, wherein the second data register includes one or more data values indicative of a failure state of the second physical layer device;
evaluating the signal quality of the communication link;
the communication link at the first physical layer device is controlled 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.
2. The method of claim 1, wherein evaluating the signal quality comprises comparing a signal-to-noise ratio of the communication link to a predetermined threshold.
3. The method of claim 2, wherein the controlling the communication link at the first physical layer device comprises 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 of claim 1, wherein the controlling the communication link comprises 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 failure at the first physical layer device or the second physical layer device.
5. The method of claim 4, wherein operating the device in a fail-safe mode comprises suspending operation on the first physical layer device.
6. The method of claim 4, further comprising determining whether the communication link is active.
7. The method of claim 6, comprising restarting the communication link after a period of time has elapsed.
8. The method of claim 6, comprising outputting a fault condition indicating a permanent fault in the communication link in response to determining that the communication link is inactive.
9. The method of claim 8, further comprising transmitting the fault condition of the communication link to another node of the communication network.
10. The method according to claim 9, wherein the other node comprises an electronic control unit (Electronic Control Unit, ECU).
11. The method according to claim 10, comprising:
determining an operating mode of the platform at the ECU based on the fault condition of the communication link;
the platform is controlled to operate in a determined mode of operation.
12. The method of claim 8, further comprising establishing a backup communication link in the communication network in response to receiving a fault condition indicating a permanent fault.
13. The method according to claim 1, characterized in that it comprises:
determining one or more other data values indicative of a failure state of the first physical layer device or the second physical layer device;
the one or more other data values are written to the first data register or the second data register.
14. A node in a communication network of a platform, the node comprising:
a physical layer device, the physical layer device comprising:
a first data register for storing data indicative of a failure state of the physical layer device;
a second data register for storing data indicative of a failure state of a second physical layer device in communication with the physical layer device over a communication link,
wherein the physical layer device is configured to:
accessing one or more data values stored in the first register;
accessing one or more data values stored in the second register;
evaluating signal quality of a communication link between the physical layer device and the second physical layer device;
the communication link is controlled in dependence 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.
15. The node of claim 14, wherein the physical layer device is configured to compare a signal-to-noise ratio of the communication link to a predetermined threshold.
16. The node of claim 14, wherein 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 of claim 14, wherein to control the communication link, the physical layer device is to operate 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 failure exists at the first physical layer device or the second physical layer device.
18. The node of claim 14, wherein the physical layer device is configured to determine whether the communication link is active.
19. The node of claim 18, wherein the physical layer device is configured to restart the physical link after a period of time has elapsed.
20. An electronic control unit (electronic control unit, ECU) for a communication network in a platform, the electronic control unit comprising:
a processor;
a memory communicatively coupled to the processor, wherein the memory stores instructions that, when implemented on the processor, cause the processor to:
receiving a failure state of a communication link in the communication network;
determining an operating mode of the platform at the ECU based on the fault condition of the communication link;
the platform is controlled to operate in a determined mode of operation.
CN202180097478.9A 2021-04-26 2021-04-26 Method and system for a communication network Pending CN117203945A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2021/060780 WO2022228639A1 (en) 2021-04-26 2021-04-26 Method and system for a communications network

Publications (1)

Publication Number Publication Date
CN117203945A true CN117203945A (en) 2023-12-08

Family

ID=75690292

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202180097478.9A Pending CN117203945A (en) 2021-04-26 2021-04-26 Method and system for a communication network

Country Status (2)

Country Link
CN (1) CN117203945A (en)
WO (1) WO2022228639A1 (en)

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3340552B1 (en) * 2016-12-22 2020-03-18 Nxp B.V. Phy transceiver with adaptive tx driver and method of operating thereof
US10462155B2 (en) * 2017-03-17 2019-10-29 Cylance Inc. Electronic control unit protection framework using security zones
US20200072889A1 (en) * 2018-09-05 2020-03-05 Nxp B.V. Physical layer device and method for performing physical layer operations in a communications network

Also Published As

Publication number Publication date
WO2022228639A1 (en) 2022-11-03

Similar Documents

Publication Publication Date Title
CN110535667B (en) Method and apparatus for selectively waking up a communication node in a vehicle network
KR102589373B1 (en) Method and apparatus for wakeup of communication node in automotive network
CN111343085B (en) Routing system and method of vehicle-mounted CAN bus gateway
KR102286050B1 (en) Method for preventing diagnostic errors in vehicle network and apparatus for the same
CN112003772B (en) Communication system and communication control method
US8306004B2 (en) Communication network system having high-ranking network and low-ranking networks, interchange terminal connecting high-ranking network and low-ranking network, microcomputer controlling connection between transmission line of low-ranking network and transmission line of high-ranking network, and communication transmitter-receiver connected with transmission line of low-ranking network and transmission line of high-ranking network
KR102355092B1 (en) Operation method of communication node for diagnosing in vehicle network
JP2003229875A (en) Method for recognizing data transmission error in can controller, can controller, program, recording medium, and control device
CN103023713A (en) System and method for testing a communications network having a central bus guardian (CBG)
KR20160096526A (en) Method for diagnosing network and apparatus for the same
CN111614531B (en) Method, medium, and monitoring device for monitoring a LIN node
CN111919422A (en) Method for operating an ethernet on-board network of a motor vehicle, control unit and ethernet on-board network
CN113572673A (en) Bus-based non-inductive switching redundant communication implementation method and system
JP5019983B2 (en) In-vehicle communication system, relay device, and communication method
CN112583786B (en) Method for alarming, transmitter device and receiver device
Armbruster et al. Ethernet-based and function-independent vehicle control-platform: motivation, idea and technical concept fulfilling quantitative safety-requirements from ISO 26262
CN117203945A (en) Method and system for a communication network
CN115733729B (en) Communication fault processing method, system and equipment
CN116266803A (en) Device for a controller area network
US11863468B2 (en) Control of ethernet link-partner GPIO using OAM
JP2019186644A (en) On-vehicle communication system, on-vehicle communication device, communication program, and communication method
WO2022228638A1 (en) Method and system for a communications network
JP7205439B2 (en) electronic controller
CN115277299B (en) Synchronous loop communication system suitable for cascading converter topology
JP2018157268A (en) Transmitter and receiver

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination