A 10BASE-T1S network fault rapid positioning method and system

Abstract

The application belongs to the technical field of vehicle-mounted networks, and discloses a 10BASE-T1S network fault rapid positioning method and system. The method comprises the following steps: a fault management sublayer is constructed, the fault management sublayer comprises a master node and each slave node; the master node receives a health frame sent by each slave node according to a preset period, and the master node constructs a node sequence mapping table when receiving the health frame; a fault suspicious interval is determined according to a fault preliminary judgment result; sequence breakpoint analysis comprises single-node breakpoint analysis, continuous node breakpoint analysis and sequence jump abnormality analysis; a target fault node is determined; the type of the target fault node is determined based on a self-checking feedback result; and a hierarchical recovery strategy is executed according to the type of the fault node. The application realizes accurate fault type determination, has high troubleshooting efficiency, and does not require manual intervention for fault recovery, has small bandwidth occupation, and avoids the problems of uncontrolled bandwidth occupation and fixed polling frequency.

Description

Technical Field

[0001] This invention relates to the field of vehicle network technology, specifically to a 10BASE-T1S network fault rapid location method and system, electronic device, and storage medium. Background Technology

[0002] Based on the application characteristics of 10BASE-T1S networks (IEEE 802.3cg standard) in new energy vehicle / fleet scenarios, traditional technologies often have the following problems: 1) Fault types cannot be accurately distinguished: Traditional shared bus networks can only detect "communication interruption" phenomena, but cannot distinguish whether it is a node hardware failure (such as chip damage, power abnormality), protocol layer failure (such as program crash), or a local failure of the bus transmission medium (such as cable damage between nodes), resulting in confusion in the troubleshooting direction.

[0003] 2) The scope of fault location is unclear: In the mainstream daisy chain topology of 10BASE-T1S, an abnormality of a certain node may cause communication interruption of downstream nodes. The existing PLCA (Physical Layer Link Coordination) mechanism can only mark "unresponsive nodes", but cannot determine whether the source of the fault is the node itself or the upstream transmission path. It is necessary to disassemble and investigate node by node, which takes up to minutes.

[0004] 3) Conflict between real-time performance and network load: If high-frequency full polling is used to detect faults, it will occupy the limited 10Mbps bandwidth of 10BASE-T1S (especially in multi-node fleet scenarios), affecting the data transmission of core business such as power control and ADAS; if the polling frequency is reduced, the fault detection latency will exceed the 10ms real-time requirement of the vehicle network.

[0005] 4) Fault recovery relies on manual intervention: Existing technologies lack automatic isolation and network self-healing capabilities after fault location, requiring maintenance personnel to power off and restart or replace nodes on-site, resulting in long downtime for new energy vehicles and severely limiting fleet maintenance efficiency.

[0006] The aforementioned problems result in low efficiency in troubleshooting shared bus nodes, high maintenance costs, and an inability to meet the real-time and reliability requirements of in-vehicle networks. Summary of the Invention

[0007] In order to overcome the shortcomings of the prior art, the purpose of this invention is to provide a method, system and electronic equipment for rapid fault location in 10BASE-T1S networks, which can accurately determine the fault type, have high troubleshooting efficiency, and require no manual intervention for fault recovery, adapt to the health frame period and have low bandwidth consumption.

[0008] To address the aforementioned problems, the first aspect of this invention discloses a method for rapid fault location in a 10BASE-T1S network, comprising the following steps: A fault management sublayer is constructed within the protocol framework of the 10BASE-T1S network. The fault management sublayer includes a master node and each slave node. The master node receives health frames sent by each slave node according to a preset period. The health frame includes at least: node unique identification information, dynamic sequence count information, and status code field. The master node assigns a unique reference sequence number to each slave node and builds a node sequence mapping table when receiving a health frame; Based on the node sequence mapping table, sequence breakpoint analysis is performed to generate a preliminary fault judgment result, and the suspected fault interval is determined according to the preliminary fault judgment result; the sequence breakpoint analysis includes single node breakpoint analysis, continuous node breakpoint analysis, and sequence jump anomaly analysis. A topology-weighted round-robin narrowing algorithm is applied to the suspected fault interval to progressively narrow down the fault location range and identify the target fault node. The master node sends a diagnostic frame to the target faulty node to trigger the target faulty node to perform a self-check, and determines the type of faulty node to which the target faulty node belongs based on the self-check feedback result; A tiered recovery strategy is executed based on the type of faulty node.

[0009] Optionally, the fault node type includes soft fault nodes and hard fault nodes; the hierarchical recovery strategy includes soft fault self-healing recovery and hard fault isolation recovery; the soft fault self-healing recovery includes performing a remote reset and restart operation on the soft fault node; the hard fault isolation recovery includes performing a node isolation operation on the hard fault node and performing dynamic network topology reconstruction, and synchronously updating the PLCA polling table when performing the node isolation operation so that communication scheduling skips the hard fault node.

[0010] Optionally, the status code field is used to characterize the running status and fault precursor information of the slave node, including but not limited to one of power abnormality, signal attenuation, and protocol abnormality.

[0011] Optionally, the topology-weighted round-robin ablation algorithm includes: Weights are calculated for each slave node in the suspected fault range, and the weight of each slave node is related to the topology hop count from each node to the master node. The priority of performing binary round-robin investigation is determined based on the calculated weights, and binary round-robin investigation is performed step by step according to the priority until the target fault node is identified.

[0012] Optionally, before executing the tiered recovery strategy, the following steps are included: A network logical topology is constructed, which is formed based on logical node identifiers. The logical node identifiers are mapped to physical node identifiers. Based on the network logical topology, the PLCA polling scheduling logic is logically reconstructed to form a new logical communication path structure, thereby realizing the logical communication path reconstruction. When a target faulty node is detected to be in an abnormal state but has not met the physical isolation conditions, the master node configures the communication scheduling sequence to bypass the abnormal node based on the result of logical communication path reconstruction. This allows business data communication to bypass the abnormal node at the logical scheduling level, thereby maintaining communication continuity without interrupting the physical connection structure of the network.

[0013] Optionally, when the system detects that the health frame delay of the target fault node exceeds the preset threshold continuously but is not continuously lost, the diagnostic frame can still respond normally and PLCA polling can still be completed, the system determines that the target fault node is in an abnormal operating state, but has not met the physical isolation conditions, and does not perform node isolation operation.

[0014] Optionally, the weight calculation for each slave node in the suspected fault interval includes: For each slave node within the suspected fault interval, obtain its topology hop count to the master node, and construct a node weight mapping model based on the topology hop count to generate the topology weight value corresponding to each slave node.

[0015] A second aspect of this invention discloses a 10BASE-T1S network fault rapid location system, comprising: The construction unit is used to construct a fault management sublayer within the protocol framework of the 10BASE-T1S network, wherein the fault management sublayer includes a master node and each slave node; A health unit is used by the master node to receive health frames sent by each slave node according to a preset period. The health frame includes at least: node unique identification information, dynamic sequence count information, and status code field. The mapping unit is used by the master node to assign a unique reference sequence number to each slave node and to build a node sequence mapping table when receiving a health frame. The initial judgment unit is used to perform sequence breakpoint analysis based on the node sequence mapping table, generate a preliminary fault judgment result, and determine the suspected fault interval based on the preliminary fault judgment result; the sequence breakpoint analysis includes single node breakpoint analysis, continuous node breakpoint analysis, and sequence jump anomaly analysis. The investigation unit is used to perform a topology-weighted round-robin narrowing investigation algorithm on the suspected fault interval, gradually narrowing the fault location range and identifying the target fault node; The self-test unit is used by the master node to send a diagnostic frame to the target fault node to trigger the target fault node to perform a self-test, and to determine the fault node type to which the target fault node belongs based on the self-test feedback result. The recovery unit is used to execute a graded recovery strategy based on the type of the faulty node.

[0016] A third aspect of the present invention discloses an electronic device, comprising: a memory storing executable program code; a processor coupled to the memory; the processor calling the executable program code stored in the memory to execute the 10BASE-T1S network fault rapid location method disclosed in the first aspect of the present invention.

[0017] A fourth aspect of the present invention discloses a computer-readable storage medium storing a computer program, wherein the computer program causes a computer to execute the 10BASE-T1S network fault rapid location method disclosed in the first aspect of the present invention.

[0018] Compared with the prior art, the beneficial effects of the embodiments of the present invention are as follows: 1. Significantly improved fault location efficiency: Single-node fault location time ≤ 10ms (traditional full polling requires 100-500ms), continuous node fault location time ≤ 20ms, and location accuracy 100% (verified based on triple identification and self-test data). Taking a 128-node fleet network as an example, the maximum number of checks required is only 7 (2^7=128), far lower than the 128 checks required by traditional node-by-node checks.

[0019] 2. Controllable network load: The bandwidth utilization rate of healthy frames is ≤0.5% (calculated with 128 nodes, 128μs period, and 64 bytes per frame: 128×64×8 / (10^6×128×10^-6)=512kbps, which only accounts for 5.12% of the 10Mbps bandwidth. It can be reduced to below 0.5% after dynamic adjustment). It does not affect core services such as power control and ADAS (which require bandwidth utilization ≤10%).

[0020] 3. Improved fault self-healing capability: More than 80% of soft faults can be automatically recovered with a recovery time of ≤50ms; hard fault isolation time is ≤2ms, and network communication interruption time is reduced to 1 / 20 of the traditional solution, meeting the "99.999% reliability" requirement of vehicle network.

[0021] 4. Significantly reduced operation and maintenance costs: The troubleshooting time for fleet operation and maintenance personnel is reduced by 80%, and labor costs are reduced by more than 40%; through the fault early warning mechanism (status code field), the incidence of sudden failures can be reduced by 30%, avoiding vehicle downtime losses due to node failures.

[0022] 5. Excellent compatibility and scalability: The fault management sublayer is fully compatible with the IEEE 802.3cg standard, requiring no modification to the 10BASE-T1S physical layer chip, and can be deployed simply through software upgrades; it supports dynamic addition and removal of nodes (the master node automatically updates the sequence mapping table), adapting to fleet networks of different sizes with 2-128 nodes.

[0023] 6. Dual-path self-healing network architecture: Without changing the physical network structure, communication path reconstruction is achieved through logical structure modeling and scheduling reconstruction. During the fault recovery phase, a continuity guarantee mechanism for uninterrupted communication is achieved, forming a dual-path self-healing network architecture with the physical isolation recovery mechanism, which combines logical recovery and physical recovery in parallel and collaboratively. Attached Figure Description

[0024] Figure 1 This is a flowchart illustrating a method for rapid fault location in a 10BASE-T1S network according to an embodiment of the present invention. Figure 2 This is a schematic diagram of the structure of a 10BASE-T1S network fault rapid location system provided in an embodiment of the present invention; Figure 3 This is a schematic diagram of the structure of an electronic device disclosed in an embodiment of the present invention. Detailed Implementation

[0025] This specific embodiment is merely an explanation of the embodiments of the present invention and is not intended to limit the embodiments of the present invention. After reading this specification, those skilled in the art can make modifications to this embodiment without contributing any inventive step, but as long as they are within the scope of the claims of the embodiments of the present invention, they are protected by patent law.

[0026] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the protection scope of the embodiments of the present invention.

[0027] The term "comprising" and any variations thereof in the specification and claims of this application are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such process, method, product or device.

[0028] In embodiments of the present invention, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" or "for example" in embodiments of the present invention should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0029] Example 1 Please refer to Figure 1-3 As shown, a method for rapid fault location in a 10BASE-T1S network is as follows: Figure 1 As shown, it includes the following steps: Step S110: Construct a fault management sublayer within the protocol framework of the 10BASE-T1S network. The fault management sublayer includes a master node and each slave node. In this embodiment, the present invention constructs a fault management sublayer within the protocol framework of the 10BASE-T1S network. The fault management sublayer is embedded in the protocol stack structure as a management and control layer independent of the basic data communication function layer, and is used to realize network operation status perception, fault monitoring, diagnosis control and recovery scheduling functions.

[0030] In specific implementation, the fault management sublayer can adopt a master-slave control structure, including one master node and multiple slave nodes. The master node serves as the fault management control center node, which is used to perform network-wide status aggregation, fault analysis and decision-making, scheduling control, and recovery strategy distribution. Each slave node serves as a controlled management node, which is used to perform status reporting, self-diagnosis, control command response, and local execution operations.

[0031] In terms of protocol structure, the fault management sublayer logic is embedded on the 10BASE-T1S protocol communication layer and works in conjunction with the PLCA (Physical Layer Collision Avoidance) scheduling mechanism. By extending the management and control signaling channel without changing the underlying physical communication mechanism, parallel transmission of management and control information and business data communication is achieved.

[0032] By constructing the fault management sublayer, the network forms an independent management and control plane outside the original communication function layer, realizing the endogenous integration of network status awareness, fault identification, location analysis and recovery control functions within the protocol system, thereby avoiding the structural complexity and system coupling risks brought about by external control systems.

[0033] Step S120: The master node receives health frames sent by each slave node according to a preset period. The health frame includes at least: node unique identifier information, dynamic sequence count information, and status code field. The status code field is used to characterize the running status and fault precursor information of the slave node. The fault precursor information includes, but is not limited to, one of the following: power failure, signal attenuation, and protocol failure.

[0034] In this implementation, the present invention employs a "triple-identification health frame" to achieve accurate characterization and traceability of node status, as detailed below: Innovative Frame Structure: The health frame uses 4B / 5B encoding (compliant with the 10BASE-T1S physical layer specification), with a frame length of 64 bytes (the minimum Ethernet frame length to avoid transmission conflicts). It contains three core parts: a unique node hardware identifier (6 bytes after MAC), a dynamic sequence counter, and a status code field. The status code field (4 bits) can identify 8 types of fault precursors (such as power voltage fluctuations, bus signal attenuation, etc.), realizing "fault early warning" rather than just "fault alarm".

[0035] Step S130: The master node assigns a unique reference sequence number to each slave node and constructs a node sequence mapping table when receiving a health frame; the node sequence mapping table records the sequence count status and timestamp information of each slave node; In this embodiment, the sequence counting rule is as follows: The master node (coordinator, Node ID=0) assigns a unique "baseline sequence number" to each slave node during network initialization (e.g., 1001 for node 1, 1002 for node 2, and so on). When a slave node sends a health frame every cycle (default 128μs, synchronized with the PLCA beacon cycle), it increments the count based on the baseline sequence number (e.g., 1001-1 for the first frame of node 1, 1001-2 for the second frame). This forms a node sequence mapping table when receiving health frames, allowing the master node to locate abnormal nodes through the triple mapping of "node identifier - baseline sequence - incremented count", avoiding the address conflict problem of traditional single sequence counting.

[0036] Adaptive transmission strategy: The health frame transmission period can be dynamically adjusted by the master node according to the network load (128μs when the load is ≤30%, and 256μs when the load is 30%-70%). It is synchronized to all nodes through the "period configuration field" in the PLAC beacon frame to ensure that health detection does not affect the transmission of core services.

[0037] Step S140: Perform sequence breakpoint analysis based on the node sequence mapping table to generate a preliminary fault judgment result, and determine the suspected fault interval based on the preliminary fault judgment result; the sequence breakpoint analysis includes single node breakpoint analysis, continuous node breakpoint analysis, and sequence jump anomaly analysis; In this embodiment, the master node performs joint analysis on the health frame sequence count information and timestamp information of each slave node based on the node sequence mapping table. Through single node breakpoint analysis, continuous node breakpoint analysis, and sequence jump anomaly analysis, when sequence count anomalies and time continuity anomalies are detected, a preliminary fault judgment result is generated. Based on the topological association relationship of the abnormal nodes, a fault suspicion interval is constructed to limit the scope of subsequent fault investigation and location processing.

[0038] For example, the suspected fault range determined based on the initial fault assessment results includes: The node with the sequence anomaly is taken as the central node; the network expands to both sides based on the network topology, and the interval boundary is constructed according to the anomaly correlation weight; a set of continuous node intervals is formed, and the set of continuous node intervals is used as the interval of suspected fault.

[0039] In one specific embodiment, after receiving health frames periodically sent by each slave node, the master node constructs a node sequence mapping table based on the node's unique identifier information, dynamic sequence count information, and timestamp information in the health frame. The node sequence mapping table is used to record the base sequence number, current sequence count value, received timestamp, and sequence change status information corresponding to each slave node.

[0040] The master node performs time consistency analysis and continuity detection on the health frame sequence data of each slave node based on the node sequence mapping table. Specifically, this includes: performing continuity verification on the sequence count value of a single slave node, determining whether the current sequence count value and the previous sequence count value satisfy a continuous increasing relationship, and performing time consistency detection on the time interval between adjacent health frames; when both abnormal sequence count and abnormal time interval are detected, the node is marked as having a sequence breakpoint abnormality.

[0041] Furthermore, the master node performs correlation analysis on the sequence status of multiple slave nodes based on the network topology. When multiple adjacent slave nodes experience sequence breakpoint anomalies within the same time window, the anomaly is determined to belong to the continuous node sequence anomaly pattern, thereby identifying potential link-level fault characteristics. At the same time, abnormal jump patterns of sequence count values ​​are detected, including non-incremental jumps, large-span jumps, and backoff anomalies, to eliminate the influence of synchronization disturbances or transient interference factors on the judgment results.

[0042] Through the above sequence analysis and processing, the master node generates a structured preliminary fault assessment result. This preliminary fault assessment result includes at least preliminary fault type information, fault confidence level information, and predicted fault impact range information. Based on this preliminary fault assessment result and in conjunction with the network topology, the master node uses the node with the detected sequence breakpoint anomaly as the central node and extends its association towards adjacent nodes in the topology to construct a continuous set of nodes. This continuous set of nodes forms a suspected fault interval, used to limit the scope of subsequent fault investigation and location processing, thereby reducing the overhead of full network scanning and improving fault location efficiency.

[0043] As a specific implementation, the master node maintains a real-time node sequence mapping table. This table dynamically records the latest accumulated count and received timestamp information of each node. Through single-node breakpoint analysis, consecutive node breakpoint analysis, and sequence jump anomaly analysis, triple breakpoint analysis enables rapid identification of the fault range, as detailed below: Single node breakpoint analysis: If the cumulative count of a node has not been updated for three consecutive cycles, while the sequences of its upstream and downstream nodes are normal, it is determined to be an "isolated node failure" (such as damage to the node's own hardware).

[0044] Continuous node breakpoint analysis: If a sequence breakpoint occurs in node N and all downstream nodes (N+1, N+2...), and only the upstream node is normal, it is determined that "the transmission link between node N and the upstream is faulty" or "the fault of node N causes downstream interruption". The fault range is initially narrowed down to "node N and its access point".

[0045] Sequence jump anomaly analysis: If the node's cumulative count does not increase continuously (e.g., jumps from 1001-5 to 1001-7), it is determined to be a "node soft failure" (e.g., the program freezes and causes frame loss), rather than complete offline.

[0046] Step S150: Execute the topology weighted round-robin narrowing algorithm on the suspected fault interval to gradually narrow down the fault location range and determine the target fault node; Optionally, the topology-weighted round-robin ablation algorithm includes: Step S1501: Calculate the weight of each slave node in the suspected fault interval. The weight of each slave node is related to the topology hop count from each node to the master node. Determine the priority of performing binary round-robin investigation based on the calculated weight. Perform binary round-robin investigation step by step according to the priority until the target fault node is identified.

[0047] In this embodiment, to address the low efficiency of traditional full polling, this embodiment designs a hybrid shortening strategy of "binary search + topology weight" based on the 10BASE-T1S daisy-chain topology characteristics, reducing fault location time from seconds to milliseconds, as detailed below: Initial range locking: Based on the sequence breakpoint analysis results, the suspected fault range (such as node 3-node 8) is determined. The master node sends a "silent command" to all nodes in this range to suspend their health frame transmission and avoid interference with the investigation.

[0048] Topology-weighted binary search troubleshooting: The master node prioritizes polling "topology-critical nodes" (such as midpoint nodes and bus branch nodes) within the suspected range. These nodes have higher weight values ​​than ordinary nodes (weight = 1 / number of hops from the node to the master node). For example, if the suspected range is nodes 3-8, node 5 (midpoint) is polled first. If node 5 responds normally, the fault range is narrowed down to 6-8; if there is no response, node 4 (midpoint of 3-5) is polled further, and so on. Each poll can reduce the troubleshooting range by more than 50%.

[0049] In one specific embodiment, after obtaining the suspected fault interval, the master node performs topology weight calculation processing on each slave node within the suspected fault interval. The topology weight is used to characterize the hierarchical position of each slave node relative to the master node in the network topology and the probability of fault association. The weight is generated in association with the topology hop count between each slave node and the master node.

[0050] Specifically, the weight calculation for each slave node in the suspected fault interval includes: For each slave node within the suspected fault interval, obtain its topology hop count to the master node, and construct a node weight mapping model based on the topology hop count to generate the topology weight value corresponding to each slave node.

[0051] Specifically, the master node obtains the topology hop count Hi between each slave node and the master node based on the network topology structure, and uses the topology hop count as the basic parameter for weight calculation. The node weight value Wi is constructed through a preset weight mapping function, such as using an inverse proportional mapping relationship or a hierarchical mapping relationship, so that the node with the smaller topology hop count corresponds to the higher weight, and the node with the larger topology hop count corresponds to the lower weight, thereby forming a node priority weight distribution model.

[0052] After obtaining the weight values ​​of each slave node, the master node sorts the set of nodes within the suspected fault interval based on the weights, forming a priority sequence for investigation, and constructs a binary round-robin investigation strategy model accordingly. The binary round-robin investigation strategy model, guided by weight distribution, divides the suspected fault interval into multiple sub-intervals according to the weight distribution characteristics, and prioritizes performing round-robin investigation processing on the high-weight sub-intervals.

[0053] During the binary polling troubleshooting process, the master node first selects the node corresponding to the median weight or the center node of the high-weight interval as the initial polling node. It obtains the node's running status feedback information by sending diagnostic frames to the corresponding node, and performs a binary division on the current interval based on the feedback results. The abnormally associated interval is retained as the new troubleshooting interval, while the interval without abnormalities is removed from the troubleshooting scope. Subsequently, the weight-guided binary polling troubleshooting process is repeated in the new troubleshooting interval to gradually narrow the fault troubleshooting scope until the troubleshooting interval is converged to a single node or the smallest set of nodes, thereby determining the target fault node.

[0054] Through the aforementioned binary polling investigation mechanism guided by topology weights, a progressively convergent localization process is achieved, moving from interval-level fault location to precise node-level localization.

[0055] Step S160: The master node sends a diagnostic frame to the target fault node to trigger the target fault node to perform a self-check, and determines the fault node type to which the target fault node belongs based on the self-check feedback result; In this embodiment, after the target node is located, the master node sends a "diagnostic frame" to trigger the node's self-test. The node returns self-test data of the physical layer (such as differential signal amplitude and terminal resistance value) and the protocol layer (such as program running status). The master node combines this data with the health frame history to accurately determine the fault type (such as hardware / software / link) and thus determine the fault node type.

[0056] Step S170: Execute a graded recovery strategy according to the fault node type.

[0057] Optionally, the fault node type includes soft fault nodes and hard fault nodes; the hierarchical recovery strategy includes soft fault self-healing recovery and hard fault isolation recovery; the soft fault self-healing recovery includes performing a remote reset and restart operation on the soft fault node; the hard fault isolation recovery includes performing a node isolation operation on the hard fault node and performing dynamic network topology reconstruction, and synchronously updating the PLCA polling table when performing the node isolation operation so that communication scheduling skips the hard fault node.

[0058] In this embodiment, a tiered fault recovery and network self-healing mechanism is adopted. After locating the fault, the master node executes a differentiated recovery strategy according to the fault type, achieving "network self-healing without manual intervention," as detailed below: Soft fault self-healing: For soft fault nodes such as program freezes, the master node sends a "reset command" to trigger a hot restart of the node. After restarting, the sequence count synchronization is automatically restored, and the recovery time is ≤50ms.

[0059] Hard fault isolation and recovery: For nodes with hardware damage or link failure, the master node sends an "isolation command" to put the node into a low-power sleep state (disconnecting its bus driver), and at the same time updates the PLCA polling table through "dynamic topology reconstruction" to skip the target faulty node and ensure normal communication for other nodes. If it is a daisy chain end node, the master node automatically controls adjacent nodes to enable backup terminating resistors (120Ω) to eliminate the influence of signal reflection.

[0060] Simultaneously, operational coordination is implemented: the master node uploads the target fault node ID, type, location, and recovery status to the fleet operation and maintenance platform in real time, generating a visualized fault work order. This supports remote monitoring and precise work order dispatch, avoiding the problem that operation and maintenance data lacks visualization support, fault information is only stored in the form of scattered logs, there is no unified health status mapping and fault tracing mechanism, and it is impossible to provide the fleet operation and maintenance platform with an accurate node health profile.

[0061] As another embodiment, prior to executing the tiered recovery strategy, the following is included: Step S1700: Construct a network logical topology structure, which is formed based on logical node identifiers. The logical node identifiers and physical node identifiers form a mapping relationship. Based on the network logical topology structure, the PLCA polling scheduling logic is logically reconstructed to form a new logical communication path structure, thereby realizing the logical communication path reconstruction. In this step, the virtual topology mapping table is used to establish a mapping relationship between the physical node identifier and the logical node identifier of the slave node, and based on the mapping relationship, a network logical topology structure is constructed to form a logical communication structure model independent of the physical communication link connection relationship.

[0062] The master node reconstructs the PLCA polling scheduling logic based on the network logical topology. By rearranging the polling order, adjusting the node access priority, or reconstructing the communication scheduling sequence, a new logical communication path structure is constructed without changing the physical communication link connection relationship, thus realizing the logical communication path reconstruction.

[0063] When a target faulty node is detected to be in an abnormal state but has not met the physical isolation conditions, the master node configures the communication scheduling sequence to bypass the abnormal node based on the result of logical communication path reconstruction. This allows business data communication to bypass the abnormal node at the logical scheduling level, thereby maintaining communication continuity without interrupting the physical connection structure of the network.

[0064] In one specific embodiment, when the system detects that the health frame delay of the target node exceeds the preset threshold continuously but is not continuously lost, the diagnostic frame can still respond normally and the PLCA polling can still be completed, the system determines that the node is in an abnormal operating state but has not reached the physical isolation condition. At this time, the node isolation operation is not performed, but the logical topology reconstruction and logical bypass communication mechanism are triggered to maintain the continuity of network communication.

[0065] The logical communication path reconstruction and logical detour communication processes do not perform physical link disconnection, physical reconnection, node hardware switching, or link structure change operations. They are only implemented by updating the virtual topology mapping table, the network logical topology model, and the PLCA polling scheduling logic parameters. This allows the logical layer network structure reconstruction to be completed during the recovery execution phase, forming a dual-path recovery mechanism that combines the logical recovery path with the physical recovery path.

[0066] In the above implementation process, without changing the physical network structure, communication path reconstruction is achieved through logical structure modeling and scheduling reconstruction. During the fault recovery phase, a continuous communication guarantee mechanism is achieved without interruption. This, together with the physical isolation recovery mechanism, forms a dual-path self-healing network architecture that combines logical recovery and physical recovery in parallel and collaboratively.

[0067] Specifically, when the system detects that the health frame delay of the target fault node exceeds the preset threshold continuously but is not continuously lost, the diagnostic frame can still respond normally and PLCA polling can still be completed, the system determines that the target fault node is in an abnormal operating state, but has not met the physical isolation conditions, and does not perform node isolation operation.

[0068] In practice, the preset thresholds may include one or more of the following: health frame period offset threshold, health frame loss rate threshold, sequence count continuity threshold, diagnostic frame response delay threshold, PLCA collision rate threshold, and link quality parameter threshold.

[0069] For example, when the health frame delay of the target faulty node continuously exceeds the health frame period offset threshold and the health frame loss rate threshold, the target node is determined to be in an abnormal state but has not met the physical isolation condition. For instance, the health frame period offset threshold is set to exceed 1.5–2 times the baseline period for N consecutive times (N is a natural number, 3–8), and the health frame loss rate threshold is set to 15%–30%.

[0070] In practical implementation, the health frames of this invention adopt 4B / 5B encoding and DME (Differential Manchester) modulation, fully conforming to the 10BASE-T1S physical layer encoding specification. Frame transmission and reception can be achieved through existing PHY chips without custom hardware. The fault management sublayer and PLCA mechanism work in parallel. Independent frame type identifiers (0xFFFF for health frames, 0xFFFE for diagnostic frames) avoid conflicts with service frames, ensuring strong protocol compatibility. The main node (vehicle gateway) of this invention adopts a mainstream ARM Cortex-A53 architecture MCU (computing power ≥ 1GHz), and uses a sequence mapping table maintenance (128 node data, approximately 1KB storage space) and a topology weighted ablation algorithm (complexity O(log n)). The computation time for n) is ≤1ms, far below the 10ms real-time requirement, ensuring hardware computing power. The linear structure of the mainstream 10BASE-T1S daisy-chain topology of this invention provides natural convenience for "shrinkage troubleshooting". The node hop count can be automatically recorded through the access order during initialization, without the need for additional ranging hardware. Dynamic termination resistor control can be implemented by driving relays through GPIO pins, which is maturely applied in the field of vehicle bus and adapts to topology characteristics. The 128μs health frame transmission period of this invention is synchronized with the PLACA beacon period to avoid bus contention. The diagnostic frame adopts the highest priority arbitration mechanism (based on 10BASE-T1S priority encoding), which can preempt the transmission of ordinary service frames to ensure the real-time performance of fault troubleshooting.

[0071] In another embodiment, the method of the present invention further includes: Step S180: After locating the target fault node, construct a multi-source consistency judgment model based on health frame status information, diagnostic frame feedback information, service data statistics, PLCA conflict statistics, and link quality parameter information. The multi-source consistency judgment model is used to perform consistency verification on the identified target fault node to generate a consistency evaluation result, wherein the consistency evaluation result is used to characterize the credibility level of the target fault node location result. Based on the consistency assessment results, the failure determination results of the target fault node are subjected to consistency correction processing. The consistency correction processing is only used to correct the failure type determination results and does not re-execute the target fault node location process.

[0072] Example 2 This invention discloses a 10BASE-T1S network fault rapid location system, such as... Figure 2 As shown, Figure 2 It is a 10BASE-T1S network fault rapid location system, including: Construction unit 210 is used to construct a fault management sublayer within the protocol framework of the 10BASE-T1S network, the fault management sublayer including a master node and each slave node; Health unit 220 is used by the master node to receive health frames sent by each slave node according to a preset period. The health frame includes at least: node unique identification information, dynamic sequence count information and status code field. The mapping unit 230 is used by the master node to assign a unique reference sequence number to each slave node and to build a node sequence mapping table when receiving a health frame. The initial judgment unit 240 is used to perform sequence breakpoint analysis based on the node sequence mapping table, generate a preliminary fault judgment result, and determine the suspected fault interval based on the preliminary fault judgment result; the sequence breakpoint analysis includes single node breakpoint analysis, continuous node breakpoint analysis, and sequence jump anomaly analysis. The investigation unit 250 is used to perform a topology weighted round-robin narrowing investigation algorithm on the suspected fault interval, gradually narrowing the fault location range and determining the target fault node; The self-test unit 260 is used by the master node to send a diagnostic frame to the target fault node to trigger the target fault node to perform a self-test, and to determine the fault node type to which the target fault node belongs based on the self-test feedback result. Recovery unit 270 is used to execute a graded recovery strategy according to the type of the faulty node.

[0073] Example 3 Please see Figure 3 , Figure 3 This is a schematic diagram of the structure of an electronic device disclosed in an embodiment of the present invention. For example... Figure 3 As shown, the electronic device may include: Memory 310 storing executable program code; Processor 320 coupled to memory 310; The processor 320 calls the executable program code stored in the memory 310 to execute some or all of the steps in the 10BASE-T1S network fault rapid location method in Embodiment 1.

[0074] This invention discloses a computer-readable storage medium storing a computer program that causes a computer to perform some or all of the steps in a 10BASE-T1S network fault rapid location method according to Embodiment 1.

[0075] This invention also discloses a computer program product, wherein when the computer program product is run on a computer, the computer performs some or all of the steps in the 10BASE-T1S network fault rapid location method in Embodiment 1.

[0076] This invention also discloses an application publishing platform, which is used to publish computer program products. When the computer program products are run on a computer, the computer performs some or all of the steps in the 10BASE-T1S network fault rapid location method in Embodiment 1.

[0077] In various embodiments of the present invention, it should be understood that the sequence number of each process does not necessarily imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0078] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; they can be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0079] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0080] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-accessible memory. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several requests to cause a computer device (which can be a personal computer, server, or network device, specifically a processor in the computer device) to execute some or all of the steps of the methods described in the various embodiments of the present invention.

[0081] In the embodiments provided by this invention, it should be understood that "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information.

[0082] Those skilled in the art will understand that some or all of the steps in the various methods of the embodiments described can be implemented by a program instructing related hardware. This program can be stored in a computer-readable storage medium, including read-only memory (ROM), random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), one-time programmable read-only memory (OTPROM), electrically-Erasable Programmable Read-Only Memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, disk storage, magnetic tape storage, or any other computer-readable medium capable of carrying or storing data.

[0083] The foregoing has provided a detailed description of a 10BASE-T1S network fault rapid location method, apparatus, electronic device, and storage medium disclosed in the embodiments of the present invention. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A method for rapid fault location in a 10BASE-T1S network, characterized in that, It includes the following: A fault management sublayer is constructed within the protocol framework of the 10BASE-T1S network. The fault management sublayer includes a master node and each slave node. The master node receives health frames sent by each slave node according to a preset period. The health frame includes at least: node unique identification information, dynamic sequence count information, and status code field. The master node assigns a unique reference sequence number to each slave node and builds a node sequence mapping table when receiving a health frame; Based on the node sequence mapping table, sequence breakpoint analysis is performed to generate a preliminary fault judgment result, and the suspected fault interval is determined according to the preliminary fault judgment result; the sequence breakpoint analysis includes single node breakpoint analysis, continuous node breakpoint analysis, and sequence jump anomaly analysis. A topology-weighted round-robin narrowing algorithm is applied to the suspected fault interval to progressively narrow down the fault location range and identify the target fault node; the topology-weighted round-robin narrowing algorithm includes: Weights are calculated for each slave node in the suspected fault range, and the weight of each slave node is related to the number of topological hops from each slave node to the master node. The priority of performing binary round-robin investigation is determined according to the calculated weights, and binary round-robin investigation is performed step by step according to the priority until the target fault node is identified. The master node sends a diagnostic frame to the target faulty node to trigger the target faulty node to perform a self-check, and determines the type of faulty node to which the target faulty node belongs based on the self-check feedback result; A tiered recovery strategy is executed based on the type of faulty node.

2. The method for rapid fault location in 10BASE-T1S networks according to claim 1, characterized in that, The fault node types include soft fault nodes and hard fault nodes; the hierarchical recovery strategy includes soft fault self-healing recovery and hard fault isolation recovery. The soft fault self-healing recovery includes performing a remote reset and restart operation on the soft fault node; The hard fault isolation and recovery includes performing node isolation operations on hard fault nodes and dynamically reconstructing the network topology. During the node isolation operation, the PLCA polling table is updated synchronously so that communication scheduling skips hard fault nodes.

3. The method for rapid fault location in 10BASE-T1S networks according to claim 1, characterized in that, The status code field is used to characterize the running status and fault precursor information of the slave node. The fault precursor information includes one of the following: power failure, signal attenuation, and protocol failure.

4. The method for rapid fault location in 10BASE-T1S networks according to claim 2, characterized in that, Before implementing the tiered recovery strategy, the following steps are included: A network logical topology is constructed, which is formed based on logical node identifiers. The logical node identifiers are mapped to physical node identifiers. Based on the network logical topology, the PLCA polling scheduling logic is logically reconstructed to form a new logical communication path structure, thereby realizing the logical communication path reconstruction. When a target faulty node is detected to be in an abnormal state but has not met the physical isolation conditions, the master node configures the communication scheduling sequence to bypass the abnormal node based on the result of logical communication path reconstruction. This allows business data communication to bypass the abnormal node at the logical scheduling level, thereby maintaining communication continuity without interrupting the physical connection structure of the network.

5. The method for rapid fault location in 10BASE-T1S networks according to claim 4, characterized in that, When the health frame delay of the target fault node is detected to exceed the preset threshold continuously but is not continuously lost, the diagnostic frame can still respond normally and PLCA polling can still be completed, the target fault node is determined to be in an abnormal operating state, but the physical isolation condition has not been met, and node isolation operation is not performed.

6. The method for rapid fault location in a 10BASE-T1S network according to claim 4, characterized in that, The weight calculation for each slave node in the suspected fault range includes: For each slave node within the suspected fault interval, obtain its topology hop count to the master node, and construct a node weight mapping model based on the topology hop count to generate the topology weight value corresponding to each slave node.

7. A 10BASE-T1S network fault rapid location system, characterized in that, It includes: The construction unit is used to construct a fault management sublayer within the protocol framework of the 10BASE-T1S network, wherein the fault management sublayer includes a master node and each slave node; A health unit is used by the master node to receive health frames sent by each slave node according to a preset period. The health frame includes at least: node unique identification information, dynamic sequence count information, and a status code field. The mapping unit is used by the master node to assign a unique reference sequence number to each slave node and to build a node sequence mapping table when receiving a health frame. The initial judgment unit is used to perform sequence breakpoint analysis based on the node sequence mapping table, generate a preliminary fault judgment result, and determine the suspected fault interval based on the preliminary fault judgment result; the sequence breakpoint analysis includes single node breakpoint analysis, continuous node breakpoint analysis, and sequence jump anomaly analysis. The investigation unit is used to perform a topology-weighted round-robin narrowing investigation algorithm on the suspected fault interval, gradually narrowing the fault location range and determining the target fault node; the topology-weighted round-robin narrowing investigation algorithm includes: calculating the weight of each slave node in the suspected fault interval, the weight of each slave node being associated with the topology hop count from each slave node to the master node; determining the priority of performing binary round-robin investigation based on the calculated weight, and performing binary round-robin investigation step by step according to the priority until the target fault node is determined; The self-test unit is used by the master node to send a diagnostic frame to the target fault node to trigger the target fault node to perform a self-test, and to determine the fault node type to which the target fault node belongs based on the self-test feedback result. The recovery unit is used to execute a graded recovery strategy based on the type of the faulty node.

8. An electronic device, characterized in that, It includes: a memory storing executable program code; a processor coupled to the memory; the processor calling the executable program code stored in the memory to execute the 10BASE-T1S network fault rapid location method according to any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, It stores a computer program, wherein the computer program causes the computer to execute the 10BASE-T1S network fault rapid location method according to any one of claims 1-6.

Images