Systems and methods for controlling data transmission on a network
By configuring periodic counters and parameters on 10Base-T1S network devices, a timetable is created to control data transmission, solving the network latency problem and achieving efficient data transmission.
Patent Information
- Application Number
- CN202510910183.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2025-05-14
- Filing Date
- 2025-07-02
- Publication Date
- 2026-11-17
AI Technical Summary
In a 10Base-T1S network, when multiple nodes transmit Ethernet frames through the 10Base-T1S data bus, delays may occur, which slows down the transmission speed of critical frames. Existing physical layer conflict avoidance methods have failed to effectively solve this problem.
By installing software, firmware, or hardware on each network device, configuring periodic counters and parameters, creating schedules to control data transmission opportunities, and using modulus and offset equations to determine transmission timing, high-priority devices are ensured to transmit first.
It effectively avoids data transmission conflicts, improves network transmission efficiency, reduces latency, and ensures timely transmission of key frames.
Smart Images

Figure CN123123057A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to a method for controlling data transmission over a network using a schedule based on a local periodic counter. Background Technology
[0002] In a 10Base-T1S network, multiple nodes are connected to a physical transmission medium called the 10Base-T1S data bus. During a communication cycle, the nodes transmit Ethernet frames with data payloads to each other via the 10Base-T1S data bus. The node with node ID 0 sends a beacon to the other nodes to initiate a given communication cycle. Each node has a transmission opportunity in ascending order of its given node ID, and each node may have unused transmission opportunities when it has no Ethernet frames to transmit. The communication cycle method used for communication between the multiple nodes is called Physical Layer Collision Avoidance (PLCA). PLACA helps multiple nodes avoid simultaneously transmitting Ethernet frames via the 10Base-T1S data bus, thus preventing transmission collisions. Due to the number of nodes connected to the physical transmission medium and the size of the Ethernet frames to be transmitted from a single node via the 10Base-T1S data bus, latency can occur in a 10Base-T1S network, which can slow down the transmission of critical Ethernet frames to multiple nodes. In the worst-case latency scenario, in a 10Base-T1S network with multiple nodes labeled as node ID 0 to node ID n, after node ID i (any one of the multiple nodes) transmits an Ethernet frame, node ID i must wait for nodes ID i+1 to node ID i-1 to have the opportunity to transmit Ethernet frames through the 10Base-T1S network before it can have the opportunity to transmit Ethernet frames again.
[0003] Therefore, while the current 10Base-T1S network has achieved its intended purpose, a new and improved system and approach are still needed to control the opportunity for multiple nodes to transmit data over the 10Base-T1S bus. Summary of the Invention
[0004] A system of one or more computers can be configured to perform specific operations or actions by installing software, firmware, hardware, or combinations thereof on the system, which, in operation, cause or induce the system to perform actions. One or more computer programs can be configured to perform specific operations or actions by including instructions that, when executed by a data processing device, cause the device to perform the action. One general aspect includes a method for controlling data transmission over a network. The method further includes providing a network bus for transmitting data over the network. The method also includes providing a plurality of network devices, each of which is electrically connected to the network bus, and each of which has a network controller, and each network controller is programmed to: implement a cycle counter on each of the network devices, assign a plurality of network device parameters to each of the network devices, and create a schedule for transmitting data by each of the network devices, wherein the schedule indicates whether each of the network devices can transmit data, and wherein the schedule allows each of the network devices to transmit data based on the cycle counter and the plurality of network device parameters. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform actions of the method.
[0005] The implementation may include one or more of the following features. The method for assigning multiple network device parameters may further include assigning modulo values. Assigning multiple network device parameters may further include assigning offset values. Creating a schedule for transmitting data by each of the multiple network devices may further include determining whether the following equation is true (cc... i +o i )mod m i =0, where: cc i = Periodic counter; o i = offset value; and m i = Modulus value. Creating a schedule for data transmission by each of multiple network devices can also include selecting m. i and o i The value of allows only a predetermined number of network devices to transmit data within a single cycle. Allocating multiple network device parameters may also include allocating a mode depth value. The mode depth value is determined based on a sequence of bits. Allocating multiple network device parameters may also include using the formula pn. i =(cc i mod pd i +1 determines the pattern number, where cc i = Periodic counter; o i =Offset value; pd i = Pattern depth value. When pdi The pnth bit sequence i When an index equals 1, the schedule allows each of multiple high-priority network devices to transmit data. Implementations of the technology may include hardware, methods or processes, or computer software on a computer-accessible medium.
[0006] One general aspect includes a system for controlling data transmission over a network. The system also includes a network bus for transmitting data over the network. The system further includes a plurality of network devices, each electrically connected to the network bus, and each of the network devices having a network controller, wherein each network controller is programmed to: implement a cycle counter on each of the network devices, assign a plurality of network device parameters to each of the network devices, and create a schedule for transmitting data by each of the network devices, wherein the schedule indicates whether each of the network devices can transmit data, and wherein the schedule allows each of the network devices to transmit data based on the cycle counter and the plurality of network device parameters. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform actions of the method.
[0007] The implementation may include one or more of the following features. A system for assigning parameters to multiple network devices may further include assigning modulo values. Assigning multiple network device parameters may further include assigning offset values. Creating a schedule for transmitting data by each of the multiple network devices may further include determining whether the following equation is true (cc). i +o i )mod m i =0, where: cc i = Periodic counter; o i =Offset value; m i = Modulus value. Creating a schedule for data transmission by each of multiple network devices can also include selecting m. i and o i The value of allows only a predetermined number of network devices to transmit data within a single cycle. Allocating multiple network device parameters may also include allocating a mode depth value. The mode depth value is determined based on a sequence of bits. Allocating multiple network device parameters may also include using the formula pn. i =(cc i mod pd i +1 determines the pattern number, where cc i = Periodic counter; o i = offset value; and pd i = Pattern depth value. When pd iThe pnth bit sequence i When an index equals 1, the schedule allows each of multiple high-priority network devices to transmit data. Implementations of the technology may include hardware, methods or processes, or computer software on a computer-accessible medium.
[0008] One general aspect includes a method for controlling data transmission over a network. The method further includes providing a network bus for transmitting data over the network. The method also includes providing a plurality of network devices, each of which is electrically connected to the network bus, and each of the plurality of network devices having a network controller, and each network controller being programmed to: implement a cycle counter on each of the plurality of network devices, assign a plurality of network device parameters, including modulus values and offset values, to each of the plurality of network devices, and determine whether the following equation is true (cc... i +o i )mod m i =0, where: cc i = Periodic counter; o i = offset value; and m i = Modular value, creating a schedule for data transmission by each of a plurality of network devices, wherein the schedule indicates whether each of the plurality of network devices can transmit data, and wherein the schedule allows each of the plurality of network devices to transmit data based on a period counter and parameters of the plurality of network devices. Other embodiments of this aspect include a corresponding computer system, apparatus, and computer program recorded on one or more computer storage devices, each configured to perform actions of the method.
[0009] Further applicability will become apparent from the description provided herein. It should be understood that the specification and specific examples are for illustrative purposes only and are not intended to limit the scope of this disclosure. Attached Figure Description
[0010] The accompanying drawings described herein are for illustrative purposes only and are not intended to limit the scope of this disclosure in any way.
[0011] Figure 1 This is a schematic diagram of a network for scheduling transmission opportunities for each of a plurality of nodes along a 10Base-T1S data bus, according to an exemplary embodiment.
[0012] Figure 2 This is a flowchart illustrating the transmission sequence of multiple Ethernet frames from corresponding nodes of a plurality of nodes on a 10Base-T1S data bus according to an exemplary embodiment;
[0013] Figure 3This is a diagram of multiple communication cycles of multiple nodes on a 10Base-T1S data bus according to an exemplary embodiment;
[0014] Figure 4 This is a table illustrating a first exemplary embodiment of the transmission opportunities of multiple nodes relative to a local period counter using modular arithmetic-based scheduling according to an exemplary embodiment;
[0015] Figure 5 This is a table illustrating a second exemplary embodiment of the transmission opportunities of multiple nodes relative to a local period counter using modular arithmetic scheduling according to an exemplary embodiment; and
[0016] Figure 6 This is a table illustrating exemplary embodiments of transmission opportunities for multiple nodes relative to a local periodic counter, using a repetitive mode scheduling according to exemplary embodiments. Detailed Implementation
[0017] The following description is merely exemplary in nature and is not intended to limit this disclosure, its application, or its uses.
[0018] Reference Figure 1 This diagram illustrates a network 10 used to schedule transmission opportunities for each of a plurality of nodes 12 along a 10Base-T1S data bus 14. The network 10 typically includes a 10Base-T1S data bus 14, a plurality of nodes 12, and an Ethernet switch 16.
[0019] The 10Base-T1S data bus 14 provides Ethernet communication for multiple nodes 12 via transmission medium 18 using IEEE 802.3cg-2019 Clause 147 - Physical Layer (commonly referred to as 10Base-T1S). The 10Base-T1S data bus 14 enables multiple nodes 12 to communicate with each other without using an Ethernet switch 16. The 10Base-T1S data bus 14 uses a frequency range of 1 MHz to 20 MHz. The 10Base-T1S data bus 14 typically includes transmission medium 18.
[0020] The transmission medium 18 is the hardware that carries bidirectional Ethernet communication between multiple nodes 12, allowing multiple nodes 12 to send and receive communication information via the 10Base-T1S data bus 14. In a non-limiting example, the transmission medium 18 may be a twisted-pair cable with a characteristic differential impedance of 100 ohms and a tolerance of ±15%. The twisted-pair cable has an insertion loss mask of less than 15 dB in the frequency range of the 10Base-T1S data bus 14, ensuring that the transmission medium 18 can carry 10 megabits per second (Mbps) of data without using error correction algorithms to recover data errors caused by signal loss or signal reflection.
[0021] Multiple nodes 12 are devices that can exchange intra-frame data via a 10Base-T1S data bus 14. In a non-limiting list of examples, each of the multiple nodes 12 can be an Engine Control Unit (ECU), an infotainment controller, a climate control module, a sensor, an actuator, a Programmable Logic Controller (PLC), a motor controller, or a Human-Machine Interface (HMI) panel. It should be understood that the 10Base-T1S data bus 14 employs a multi-point topology, thereby allowing up to eight nodes of the multiple nodes 12 to communicate with each other along the 10Base-T1S data bus 14 when conforming to IEEE 802.3cg Section 147. Each of the multiple nodes 12 includes a microcontroller 20, an Ethernet controller 22, a Physical Layer (PHY layer) transceiver 24, a connector interface 26, and a power supply 28.
[0022] The microcontroller 20 is a non-general-purpose electronic control device having a pre-programmed digital computer or processor 30, memory 32, transceiver 34, and multiple input and output ports 36. The processor 30 may be a custom or commercially available processor, a central processing unit (CPU), a graphics processing unit (GPU), an auxiliary processor among several processors associated with the microcontroller 20, a semiconductor-based microprocessor (in the form of a microchip or chipset), a combination of microprocessors, or generally a device for executing instructions. The memory 32 is used to store data such as control logic, software applications, instructions, computer code, data, lookup tables, etc. The memory 32 includes any type of media that can be accessed by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, compact disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media include media that can permanently store data and media that can store and subsequently overwrite data, such as rewritable optical discs or erasable memory devices. Computer code includes any type of program code, including source code, object code, and executable code. Processor 30 is configured to execute code or instructions.
[0023] Transceiver 34 is configured to wirelessly communicate with hotspots using Wi-Fi protocols under the IEEE 802.11x standard. Transceiver 34 is also configured to wirelessly communicate using cellular data communication under GSMA standards (e.g., SGP.02, SGP.22, SGP.32, etc.). Suitablely, corresponding nodes from the plurality of nodes 12 may also include embedded universal integrated circuit cards (eUICCs) configured to store at least one cellular connectivity profile, such as an embedded subscriber identity module (eSIM) profile. Transceiver 34 is also configured to communicate via personal area networks (e.g., Bluetooth), near-field communication (NFC), and / or any other type of radio frequency communication.
[0024] Multiple input and output ports 36 can receive input data from at least one sensor of a corresponding node and transmit the input data to the processor. Multiple input and output ports 36 can also receive output data from the processor 30 and transmit the output data to at least one sensor of a corresponding node. Multiple input and output ports 36 are configured to wirelessly communicate with at least one sensor of a corresponding node via a transceiver 34 or via a wired connection using a Universal Serial Bus (USB).
[0025] The microcontroller 20 may also include one or more application programs. An application program is a software program configured to perform a specific function or a set of functions. An application program may include one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The application program may be stored in memory 32 or in additional or separate memory.
[0026] The microcontroller 20 communicates electrically with at least one sensor of a corresponding node. In one exemplary embodiment, the electrical communication is established using, for example, a CAN network, a FLEXRAY network, a local area network (e.g., WiFi, Ethernet, etc.), a Serial Peripheral Interface (SPI) network, etc. It should be understood that various additional wired and wireless technologies and communication protocols used for communicating with the microcontroller 20 are within the scope of this disclosure. The microcontroller 20 also communicates with other nodes in the plurality of nodes 12 via Ethernet-based communication provided by the Media Access Control (MAC) layer 38 and the PHY layer 24 of each of the plurality of nodes 12.
[0027] Ethernet controller 22 is the hardware that manages MAC layer 38 and interfaces with PHY layer 24 to transmit Ethernet frames via 10Base-T1S data bus 14. Ethernet controller 22 has address filtering logic that filters received Ethernet frames based on MAC address data within the Ethernet frame. In a non-limiting example list, Ethernet controller 22 communicates with microcontroller 20 using a host interface, which may be a Serial Peripheral Interface (SPI), a memory-mapped bus, a parallel interface, or a Peripheral Component Interconnect Express (PCIe). In a non-limiting example list, Ethernet controller 22 receives and sends Ethernet frames to PHY layer 24 via Media Independent Interface (MII) or Reduced Media Independent Interface (RMII). Ethernet controller 22 may have flow control logic using pause frames, which allow a corresponding node to pause or slow down Ethernet frames received from other nodes among the plurality of nodes 12 to avoid buffer overflows, Ethernet frame loss, or other congestion. The Ethernet controller 22 has a MAC layer 38, a transmit first-in-first-out (FIFO) buffer 40, a receive FIFO buffer 42, an interrupt controller 44, and a direct memory access (DMA) controller 46.
[0028] MAC layer 38 is hardware that generates Ethernet frames containing data payloads generated by software stored in memory 32 and executed by microcontroller 20, adds a corresponding Ethernet frame header to each received Ethernet frame, and forwards each received Ethernet frame to PHY layer 24. MAC layer 38 can also receive Ethernet frames from PHY layer 24, whereby MAC layer 38 then removes the corresponding Ethernet frame header from each received Ethernet frame before transmitting each received Ethernet frame to PHY layer 24. The Ethernet frame header may include a preamble, a start frame delimiter (SFD), a destination MAC address, a source MAC address, the data type within the Ethernet frame, and the payload length of the Ethernet frame. It should be understood that, in the non-limiting list of examples, MAC layer 38 may be within microcontroller 20, which communicates with Ethernet controller 22 via SPI or PCIe.
[0029] The transmit FIFO buffer 40 enables Ethernet frames to be buffered from the MAC layer 38 to the PHY layer 24. The transmit FIFO buffer 40 allows for the transmission scheduling of Ethernet frames coordinated by the Physical Layer Collision Avoidance (PLCA) sublayer 48, where Ethernet frames are held until a transmission opportunity is signaled.
[0030] The receive FIFO buffer 42 enables the Ethernet controller 22 to temporarily store Ethernet frames received from the PHY layer 24 and separates the time spent receiving frames from the time spent by the processor 30 of the microcontroller 20 reading the data payload within the Ethernet frame. The receive FIFO buffer 42 ensures that complete Ethernet frames can be stored within the Ethernet controller 22 when communication between the Ethernet controller 22 and the microcontroller 20 is interrupted or unavailable.
[0031] Interrupt controller 44 is hardware that generates interrupt signals to notify the processor 30 of microcontroller 20 of activity or state changes, including but not limited to Ethernet frame reception, Ethernet frame transmission completion, buffer overflow or underload, link state changes, or detected errors. In a non-limiting list of examples, interrupt controller 44 signals the processor 30 using multiple status registers or event flags corresponding to a specific activity. Interrupt controller 44 may support interrupt masking and priority ordering, thereby allowing the processor 30 to enable or disable multiple status registers or event flags corresponding to a specific activity.
[0032] The DMA controller 46 is optional hardware of the Ethernet controller 22, allowing the Ethernet controller 22 to autonomously transfer Ethernet frames between the transmit FIFO buffer 40, the receive FIFO buffer 42, and the memory 32 without the need for processor 30 activity. The DMA controller 46 can operate using multiple descriptors that can define source or destination addresses, transfer lengths, and control flags to indicate how Ethernet frame transfers should be performed between the transmit FIFO buffer 40, the receive FIFO buffer 42, and the memory 32. The DMA controller 46 can support burst transmission of Ethernet frames, allowing multiple bytes of data to be transferred in a single continuous operation.
[0033] In the non-limiting example list, PHY layer 24 is hardware that converts Ethernet frames received from MAC layer 38 into analog electrical signals via MII or RMII for transmission over transmission medium 18. PHY layer 24 also converts the analog signals received from transmission medium 18 into Ethernet frames represented in digital bits for transmission to MAC layer 38. PHY layer 24 employs a multipoint topology of a 10Base-T1S data bus, allowing multiple nodes 12 to share the same transmission medium 18. PHY layer 24 supports half-duplex communication, meaning that each of the multiple nodes 12 is allocated its own transmission opportunity, coordinated by PLCA sublayer 48. In the non-limiting example list, PHY layer 24 ensures that each end of transmission medium 18 is terminated with a resistor matched to the impedance of transmission medium 18 via a programmable register within PHY layer 24 or an external passive resistor located at each of the multiple nodes 12 at both ends of the 10Base-T1S data bus 14. PHY layer 24 may have adaptive equalizers and signal shaping circuitry to adjust the analog electrical signals transmitted by PHY layer 24 to compensate for signal loss and signal reflection. PHY layer 24 has a PLCA sublayer 48.
[0034] The PLCA sublayer 48 is hardware that coordinates when each of the multiple nodes 12 has a transmission opportunity, meaning that the corresponding node can transmit Ethernet frames via the 10Base-T1S data bus 14 according to IEEE 802.3cg Section 148. The PLCA sublayer 48 also helps prevent data collisions between Ethernet frames transmitted by different nodes. The PLCA sublayer 48 helps to: prevent data collisions, initiate communication cycles on the 10Base-T1S data bus 14 by sending beacons from the node with node ID 0 to the multiple nodes 12, and provide transmission opportunities for each of the multiple nodes 12 to transmit Ethernet frames chronologically via the 10Base-T1S data bus 14 based on the node ID of each corresponding node. It should be understood that the node ID of each corresponding node can be configured in the software configuration of the corresponding node, during hardware bundling of the corresponding node, or through a management interface (e.g., Management Data Input / Output (MDIO) commands standardized in IEEE 802.3 Sections 22 / 45 or SPI commands passed to the PHY layer 24).
[0035] Connector interface 26 is a physical port for each of the plurality of nodes 12, connecting each of the plurality of nodes 12 to the transmission medium 18. In a non-limiting list of examples, connector interface 26 may be an M12 X-Coded connector, an M12D-Coded connector, a Fachkreis Automobil (FAKRA) connector, a Japan Solderless Terminal (JST) connector, or a Molex connector.
[0036] Power supply 28 provides electrical energy to each of the plurality of nodes 12, thereby powering the components of each of the plurality of nodes 12, including the microcontroller 20, PHY layer 24, and MAC layer 38 of each respective node. Power supply 28 has an input power connector 50, a voltage regulator 52, and a plurality of capacitors 54. Input power connector 50 accepts electrical energy from an external power source (i.e., a battery, a direct current (DC) rail, or a wall adapter) to power the components of the respective node. In a non-limiting list of examples, input power connector 50 may be a jack, a JST connector, a screw terminal, a mini connector, or a plurality of pin headers. Voltage regulator 52 converts the unregulated or high-voltage electrical energy accepted by input power connector 50 into stable or low-voltage electrical energy to power the components of the respective node. In a non-limiting list of examples, voltage regulator 52 may be a low dropout regulator (LDO) or a buck converter.
[0037] Multiple capacitors 54 consist of different types of capacitors that perform corresponding functions when power is supplied to the respective nodes. In a non-limiting list of examples, multiple capacitors 54 may include multiple bypass capacitors, multiple large-capacity capacitors, multiple regulator stabilizing capacitors, and multiple electromagnetic interference (EMI) capacitors. The multiple bypass capacitors provide local charge storage for the components of the respective nodes and filter out high-frequency voltage fluctuations along the electrical path of the power supply 28 supplying power to the components of the respective nodes. The multiple large-capacity capacitors store electrical energy and supply it to the components of the respective nodes in the event of sudden load changes or current surges. The multiple regulator stabilizing capacitors maintain voltage stability of the electrical energy flowing through the electrical path of the power supply 28 and prevent voltage regulator 52 from oscillating. The multiple EMI capacitors filter out high-frequency voltage fluctuations by diverting high-voltage fluctuations through the multiple EMI capacitors and into the ground plane of the respective nodes.
[0038] Ethernet switch 16 is a bridge that can be used to connect 10Base-T1S data bus 14 to a larger Ethernet network to enable communication between multiple nodes 12 along the 10Base-T1S data bus 14 and the larger Ethernet network. In a non-limiting list of examples, the larger Ethernet network may include a Central Electronic Control Unit (ECU), a Time-Sensitive Networking (TSN) domain, external networks (i.e., cloud gateways and Internet of Things (IoT) interfaces), and other data buses using 100Base-TX, 100Base-T, 100Base-T1, or Ethernet / IP systems.
[0039] It should be understood that network 10, as defined in IEEE 802.3cg Clause 147, may support burst mode functionality, where indicative nodes from multiple nodes 12 may transmit more than one Ethernet frame during a transmission opportunity within a pre-configured time period. When burst mode functionality is enabled, MAC layer 38 determines when to transmit an Ethernet frame from transmit FIFO buffer 40 to PHY layer 24, whether there are Ethernet frames available for transmission, and uses a burst timer to determine when the pre-configured time period has elapsed to stop Ethernet frame transmission. PHY layer 24 monitors the elapsed time of a transmission opportunity and terminates the transmission opportunity when the pre-configured maximum duration of the transmission opportunity has been exceeded. DMA controller 46 (if present) assists in rapidly loading Ethernet frames into transmit FIFO buffer 40 to ensure that the transmission frequency of Ethernet frames is maintained when burst mode is enabled.
[0040] Reference Figure 2 The flowchart 58 illustrates the transmission sequence of multiple Ethernet frames 56 from corresponding nodes among multiple nodes 12 on a 10Base-T1S data bus 14, generally indicated by reference numeral 58. The flowchart 58 includes functional software blocks 60, queuing blocks 62, scheduling blocks 64, and transmission blocks 66.
[0041] Functional software block 60 is software stored in memory 32 and executed by microcontroller 20, which generates a corresponding data payload to be loaded into each of the plurality of Ethernet frames 56. Each data payload is associated with a corresponding priority level (i.e., low latency or best-effort) determined by functional software block 60. In a non-limiting list of examples, each data payload may have data based on sensor data, control signals, or network service messages from microcontroller 20. Once the appropriate node receives a transmission opportunity, the data payload of each of the plurality of Ethernet frames 56 is passed to MAC layer 38, which generates and associates a corresponding MAC header for each data payload, thereby formalizing the plurality of Ethernet frames 56. In an exemplary embodiment, an Ethernet frame with a low-latency data payload is a low-latency Ethernet frame, and an Ethernet frame with a best-effort data payload is a best-effort Ethernet frame. It should be understood that in another exemplary embodiment, in addition to low latency and best-effort (i.e., medium latency), there may be further priority levels for each of the plurality of Ethernet frames 56. Then, multiple Ethernet frames 56 are passed to queue block 62.
[0042] Queuing block 62 receives multiple Ethernet frames 56 from functional software block 60, which are organized and stored in multiple queues 68. The multiple queues 68 have corresponding priority titles from highest to lowest priority, determining which of the multiple Ethernet frames 56 will be stored in each of the multiple queues 68. In an exemplary embodiment, the multiple queues 68 include a low-latency queue 70 with the highest priority title for storing the Ethernet frames of functional software block 60 determined to be low-latency Ethernet frames. The exemplary embodiment also includes a best-effort queue 72 with the lowest priority title for storing the Ethernet frames of functional software block 60 determined to be best-effort Ethernet frames. In another exemplary embodiment, the number of queues in the multiple queues 68 is as many as the priority levels of the multiple Ethernet frames 56, where each queue has a corresponding priority title from highest to lowest priority. It should be understood that when any of the multiple Ethernet frames 56 is not held in the multiple queues 68, the corresponding node rejects the transmission opportunity because the corresponding node has no available Ethernet frames to transmit.
[0043] Multiple Ethernet frames 56 are stored in multiple queues 68 until a transmission opportunity for the corresponding node is presented in order based on node ID within a given communication period, and whether the corresponding node is allowed to transmit Ethernet frames during the given communication period based on scheduling block 64. When the corresponding node is allowed to transmit, the Ethernet frames in the queue top index of the multiple queues 68 with the highest available priority title are transmitted to PHY layer 24. Then, the transmission of Ethernet frames through transmission medium 18 is performed by transmission block 66.
[0044] It should also be understood that network 10, as defined in IEEE 802.1Q Clause 8.6.8.4, may support Credit-Based Traffic Shaping (CBTS), which uses a credit counter in each of multiple queues 68 to regulate when each of the multiple nodes 12 can transmit Ethernet frames. When CBTS is enabled, the credit counter in the corresponding queue of the multiple queues 68 accumulates at a pre-configured idle rate when the corresponding node is not transmitting Ethernet frames through transmission medium 18. When the corresponding node has a transmission opportunity and the credit counter of the corresponding queue has a value greater than zero, the corresponding node transmits the Ethernet frame in the corresponding queue to PHY layer 24 and then to transmission medium 18, while simultaneously decrementing the value of the credit counter at a pre-configured transmission rate. When the credit counter drops to zero or below zero, the corresponding node terminates the transmission of Ethernet frames until the corresponding node has another transmission opportunity and the value of the credit counter accumulates back above zero.
[0045] Scheduling block 64 determines when a transmission opportunity for the corresponding node will occur. Scheduling block 64 can use one of several scheduling methods to determine when a transmission opportunity for the corresponding node will occur based on the latency requirements of multiple Ethernet frames determined by the designer of network 10. These scheduling methods include modular arithmetic-based scheduling and repetitive pattern scheduling (which will be described in further detail below).
[0046] Scheduling block 64 transmits trigger signal 73 to queuing block 62, which initiates a process to determine which of the multiple Ethernet frames 56 from multiple queues 68 will be passed to transport block 66 for transmission via transport medium 18 as late as possible (hereinafter referred to as the delayed submission principle). Given that functional software block 60 continuously and asynchronously passes Ethernet frames to queuing block 62, the delayed submission principle allows the appropriate node to determine which of the multiple Ethernet frames 56 is most suitable for transmission. It should be understood that the delayed submission principle should help queuing block 62 select and prepare the best Ethernet frame to be transmitted to transport block 66, while also ensuring that transmission opportunities are not missed because the best Ethernet frame has not yet been determined.
[0047] Transport block 66 is a function of MAC layer 38 and PHY layer 24, which prepares and transmits multiple Ethernet frames 56 via transport medium 18 for reception by other nodes among the multiple nodes 12. After the corresponding node receives a transmission opportunity from scheduling block 64, in a non-limiting example list, MAC layer 38 passes the Ethernet frame loaded into transmit FIFO buffer 40 to PHY layer 24 via MII or RMII. PHY layer 24 then encodes the Ethernet frame into a physical signaling format suitable for 10Base-T1S for transmission via transport medium 18. In a non-limiting example list, the physical signaling format used for transmission via transport medium 18 is Pulse Amplitude Modulation with three levels (PAM3).
[0048] It should be understood that different configurations exist in which queuing block 62 and scheduling block 64 can be implemented between software stored in memory 32 and executed by microcontroller 20 and the hardware components of 10Base-T1S data bus 14, MAC layer 38, and PHY layer 24. In a non-limiting exemplary embodiment, when implemented in software executed by microcontroller 20, queuing block 62 can be a location in memory 32, and when implemented in the hardware components of MAC layer 38, queuing block 62 can reside in multiple buffers. In a non-limiting exemplary embodiment, scheduling block 64 can be implemented in software executed by microcontroller 20 when a bit in a hardware register indicates the start of a communication cycle that can be cleared by writing that bit using software or by generating an interrupt associated with an interrupt generated by interrupt controller 44 using software. In a non-limiting exemplary embodiment, when implemented in the hardware components of PHY layer 24, scheduling block 64 can be implemented in PLCA sublayer 48. According to embodiments, both queuing block 62 and scheduling block 64 can be implemented in the software executed by microcontroller 20, or both can be implemented in the hardware components of 10Base-T1S data bus 14, MAC layer 38, and PHY layer 24. According to embodiments, when scheduling block 64 is implemented in the hardware components of 10Base-T1S data bus 14, MAC layer 38, and PHY layer 24, queuing block 62 can also be implemented in the software executed by microcontroller 20, and vice versa. It should also be understood that functional software block 60 is always implemented in the software executed by microcontroller 20, while transmission block 66 is always implemented in PHY layer 24, PLCA sublayer, and transmission medium 18.
[0049] In an exemplary embodiment where queuing block 62 or scheduling block 64 is implemented in software executed by microcontroller 20, the hardware of 10Base-T1S data bus 14, MAC layer 38, or PHY layer 24 has the function of notifying microcontroller 20 when a beacon is transmitted via 10Base-T1S data bus 14. In an exemplary embodiment where scheduling block 64 is implemented in hardware components of 10Base-T1S data bus 14, MAC layer 38, and PHY layer 24, scheduling methods implemented from multiple scheduling methods are implemented in discrete logic of hardware components that only contain simple operators (e.g., modulo operator, increment operator, comparison operator, etc.).
[0050] Reference Figure 3 The diagram illustrates multiple communication cycles 74 of multiple nodes 12 on a 10Base-T1S data bus 14. Each communication cycle of the 10Base-T1S data bus 14 occurs when each of the multiple nodes 12 has the opportunity to transmit an Ethernet frame to other nodes in the multiple nodes 12 via the 10Base-T1S data bus 14. Each communication cycle of the 10Base-T1S data bus 14 is initiated when a beacon from the node with node ID 0 among the multiple nodes 12 is transmitted to the multiple nodes 12 via the transmission medium 18. It should be understood that 10Base-T1S has a multi-ID feature, where at least one of the multiple nodes 12 can have more than one node ID. In an exemplary embodiment, there are five nodes among the multiple nodes 12 with node IDs 0, 1, 2, 3, and 4. It should be understood that in an exemplary embodiment, due to the multi-ID feature, the node with node ID 0 among the multiple nodes 12 also has node ID 5. The multi-ID feature allows nodes with node IDs 0 and 5 to transmit beacons to multiple nodes 12 via transmission medium 18, and provides two transmission opportunities to transmit Ethernet frames to multiple nodes 12 via transmission medium 18 within one communication cycle.
[0051] Each of the plurality of nodes 12 has a local cycle counter 76 for tracking a plurality of communication cycles 74. The local cycle counter 76 is a counter within each of the plurality of nodes 12 that tracks the number of communication cycles the corresponding node has participated in. The local cycle counter 76 is initialized to 0 and increments by a value of 1 each time the corresponding node receives a beacon from the node with node ID 0. It should be understood that nodes among the plurality of nodes 12 can be enabled or disabled after the first communication cycle has started. It should also be understood that, in the exemplary embodiment, although each of the plurality of nodes 12 has its own local cycle counter, the local cycle counter 76 is shown as a single local cycle counter because the local cycle counter 76 in each of the enabled plurality of nodes 12 is equal to each other.
[0052] After the first communication cycle has started, one of the nodes 12 may also need to be reset. Node ID 0, which transmits under different node IDs using the 10Base-T1S multi-ID feature, can periodically send a reset request to the enabled nodes among the multiple nodes 12 via transmission medium 18. The reset request instructs the node with node ID 0 to communicate with the enabled nodes among the multiple nodes 12 to reset its respective local cycle counter to 0. The reset request allows the local cycle counter of each of the multiple nodes 12 that has been enabled or whose corresponding processor 30 has been reset after the first communication cycle has started to synchronize with each of the local cycle counters of the enabled multiple nodes 12. It should be understood that each cell in the multiple communication cycles 74 with a value corresponds to the node ID of the node among the multiple nodes 12 that has a transmission opportunity during the communication cycle tracked by the local cycle counter 76.
[0053] In an exemplary embodiment, the local cycle counter 76 of each of the plurality of nodes starts from a value of 4, indicating that each of the plurality of nodes 12 has had four transmission opportunities since the initialization of the local cycle counter 76. Then, the node with node ID 0 sends a beacon to the plurality of nodes 12 through the transmission medium 18, thereby incrementing the local cycle counter 76 of each of the plurality of nodes 12 to a value of 5, initiating a fifth communication cycle. During the fifth communication cycle, nodes with node IDs 1, 2, and 4 transmit Ethernet frames through the transmission medium 18, while nodes with node IDs 0 and 3 reject their transmission opportunities. Then, the fifth communication cycle ends, with the node with node ID 0 sending a beacon and the local cycle counter 76 in each node incrementing by 1 to a value of 6, initiating a sixth communication cycle.
[0054] The sixth communication cycle is performed similarly to the fifth communication cycle, wherein some of the multiple nodes 12 transmit Ethernet frames via transmission medium 18 during their respective transmission opportunities, while some of the multiple nodes 12 refuse their transmission opportunities. In an exemplary embodiment, during the sixth communication cycle, the 10Base-T1S multi-ID feature is enabled in the node with node ID 0, thereby allowing the node with node ID 0 to also have a transmission opportunity in the case of node ID 5. When the node with node ID 0 also has a transmission opportunity in the case of node ID 5, the node with node ID 5 will transmit via transmission medium 18, thereby indicating a reset request to the enabled multiple nodes 12, causing the local cycle counter of each of the multiple nodes 12 to be reset to a value of 0. When the node with node ID 0 transmits another beacon, the local cycle counter 76 increments by 1 and starts the first communication cycle, followed by the second communication cycle.
[0055] It should be understood that, in another exemplary embodiment, when a node with node ID 0 receives a reset request from any of the plurality of nodes 12, the local cycle counter 76 may increment to a value of 100. After the value of the local cycle counter 76 reaches 100, once the next communication cycle is initiated, the local cycle counter 76 in each of the enabled plurality of nodes 12 is reset to a value of 1. It should also be understood that, in another exemplary embodiment, the frequency with which a node with node ID 0 sends a reset request under another node ID using the 10Base-T1S multi-ID feature may occur frequently after a communication cycle is completed, or it may not occur at all in all 100 communication cycles tracked using the local cycle counter 76.
[0056] Reference Figure 4 The diagram shows a first table 78, which represents a first exemplary embodiment of transmission opportunities for a plurality of nodes 12 relative to a local cycle counter 76 using modulo-based scheduling. Each column of the first table 78 represents a plurality of nodes 12, and each row of the first table 78 represents a value of the local cycle counter 76 that increments from the top to the bottom of the first table 78.
[0057] Modular scheduling is configured in scheduling block 64 and allows multiple nodes 12 (hereinafter referred to as low-latency nodes) that transmit only low-latency, high-priority Ethernet frames or a combination of low-latency Ethernet frames and best-effort Ethernet frames to have one transmission opportunity per communication cycle of the 10-base-T1S data bus 14, while limiting the transmission opportunities per communication cycle for multiple nodes 12 (hereinafter referred to as best-effort nodes) that transmit only best-effort, low-priority Ethernet frames. This feature of limiting the transmission opportunities of best-effort nodes by modular scheduling reduces the worst-case latency of low-latency node transmissions by decreasing the number of nodes with transmission opportunities per communication cycle, thereby providing each low-latency node with shorter communication cycles and more frequent transmission opportunities. Modular scheduling receives a set of modularly calculated network device parameters 80 to assist in determining whether a particular node among the multiple nodes 12 has a transmission opportunity within a communication cycle.
[0058] The modulo operation of multiple network device parameters 80 is configured within the functional software block 60, and indicates to the scheduling block 64 whether each of the multiple nodes 12 has a priority level (e.g., low latency and best-effort) for each of the multiple nodes 12. Each of the multiple network device parameters in the modulo operation of multiple network device parameters 80 corresponds to a single node among the multiple nodes 12. Each of the multiple network device parameters has a modulus value (m). i ) and an offset value (o i ).
[0059] Modular-based scheduling receives multiple network device parameters 80 from the set of modular operation parameters and corresponding multiple network device parameters from the local period counter 76, and inputs them into the modular operation equation (cc). i +o i )mod m i =0 determines which of the multiple nodes 12 should receive a transmission opportunity within a given communication period. It should be understood that cc i This represents the value of the local cycle counter 76 during a given communication cycle, m. i and o i This refers to the multiple network device parameters 80 corresponding to one of the multiple nodes in the modular operation. When the modular operation equation is true, the scheduling based on the modular operation determines that one of the multiple nodes 12 corresponding to the input multiple network device parameters has a transmission opportunity within a given communication period. When the modular operation equation is false, the scheduling based on the modular operation determines that one of the multiple nodes 12 corresponding to the input multiple network device parameters does not have a transmission opportunity within a given communication period.
[0060] In the first exemplary embodiment, the plurality of nodes 12 have six nodes, and the group modulo operation of the plurality of network device parameters 80 has a plurality of network device parameters: m i =1,o i =0 (corresponding to nodes with ID 0 and ID 1); m i =4,o i =3 (corresponding to node with ID 2); m i =4, o i =2 (corresponding to node with ID 3); m i =4,o i =1 (corresponding to node with ID 4); and m i =4,o i =0 (corresponding to node ID 5). It should be understood that the configuration of multiple network device parameters 80 in this modulo operation indicates that nodes with ID 0 and ID 1 are low-latency nodes, while nodes with ID 2, ID 3, ID 4, and ID 5 are best-effort nodes.
[0061] In the first exemplary embodiment, after inputting the corresponding multiple network device parameters into the modular arithmetic equation, when the value of the local cycle counter 76 is 1, nodes with ID 0, ID 1, and ID 2 have one transmission opportunity (represented by "X" in the corresponding cell of the first table 78). When the value of the local cycle counter 76 is 2, nodes with ID 0, ID 1, and ID 3 have one transmission opportunity. When the value of the local cycle counter 76 is 3, nodes with ID 0, ID 1, and ID 4 have one transmission opportunity. When the value of the local cycle counter 76 is 4, nodes with ID 0, ID 1, and ID 5 have one transmission opportunity. Then, the communication cycle pattern is repeated, wherein low-latency nodes have one transmission opportunity per communication cycle, while best-effort nodes have one transmission opportunity every four communication cycles.
[0062] It should be understood that, in one alternative exemplary embodiment, when following IEEE 802.3cg guideline 147, the configuration of the modulo operation of multiple network device parameters 80 can indicate up to eight low-latency nodes and up to eight best-effort nodes, provided that no more than eight nodes out of the multiple nodes 12 are present. In another alternative exemplary embodiment, when not following IEEE 802.3cg guideline 147, the multiple nodes 12 can have more than eight nodes, meaning there can be more than eight low-latency nodes and more than eight best-effort nodes. It should also be understood that, while in the first exemplary embodiment, the configuration of the modulo operation of multiple network device parameters 80 limits the number of multiple nodes 12 with transmission opportunities in a given communication cycle to three, in an alternative embodiment, the configuration of the modulo operation of multiple network device parameters 80 can allow up to all enabled nodes out of the multiple nodes 12 to have one transmission opportunity in a given communication cycle. It should also be understood that, although in the first exemplary embodiment the configuration of the group of modulo operations on multiple network device parameters 80 treats each best-effort node fairly, thereby allowing each best-effort node to have one transmission opportunity every four communication cycles, in an alternative exemplary embodiment the configuration of the group of modulo operations on multiple network device parameters 80 may allow a particular best-effort node to have more transmission opportunities than other best-effort nodes within the same number of communication cycles.
[0063] Reference Figure 5The diagram illustrates a second table 82, which represents a second exemplary embodiment of the transmission opportunities of a plurality of nodes 12 relative to a local cycle counter 76 using modulo-based scheduling. Each column of the second table 82 represents a plurality of nodes 12, and each row of the second table 82 represents the value of the local cycle counter 76, incremented from the top to the bottom of the second table 82. In the second exemplary embodiment, the modulo-based scheduling receives a set of modulo-based multiple network device parameters 80 to assist in determining whether a particular node among the plurality of nodes 12 has a transmission opportunity within a given communication cycle. It should be understood that in the second exemplary embodiment, each modulo-based multiple network device parameter from the set of modulo-based multiple network device parameters 80 has a different m compared to the first exemplary embodiment. i and o i Value configuration.
[0064] In the second exemplary embodiment, the plurality of nodes 12 have six nodes, and the group modulo operation of the plurality of network device parameters 80 has a plurality of network device parameters: m i =1,o i =0 (corresponding to the node with ID 0); m i =2,o i =1 (corresponding to the node with ID 1); m i =4,o i =3 (corresponding to node with ID 2); m i =2,o i =0 (corresponding to node with ID 3); m i =2,o i =0 (corresponding to node with ID 4); and m i =4,o i =1 (corresponding to node ID 5). It should be understood that the configuration of multiple network device parameters 80 in this group of modulo operations indicates that node ID 0 is a low-latency node, node ID 1, node ID 3 and node ID 4 are medium-latency nodes, and node ID 2 and node ID 5 are best-effort nodes.
[0065] In the second exemplary embodiment, after inputting the corresponding multiple network device parameters into the modular arithmetic equation, when the value of the local cycle counter 76 is 1, nodes with ID 0, ID 1, and ID 2 have one transmission opportunity (represented by "X" in the corresponding cell of the second table 82). When the value of the local cycle counter 76 is 2, nodes with ID 0, ID 3, and ID 4 have one transmission opportunity. When the value of the local cycle counter 76 is 3, nodes with ID 0, ID 1, and ID 5 have one transmission opportunity. When the value of the local cycle counter 76 is 4, nodes with ID 0, ID 3, and ID 4 have one transmission opportunity. The communication cycle pattern is then repeated, wherein low-latency nodes have one transmission opportunity per communication cycle, medium-latency nodes have one transmission opportunity every other communication cycle, and each best-effort node has one transmission opportunity every four communication cycles.
[0066] It should be understood that, in one alternative exemplary embodiment, when following IEEE 802.3cg 147 guidelines, the configuration of the modulo operation of multiple network device parameters 80 can indicate up to eight low-latency nodes, up to eight medium-latency nodes, and up to eight best-effort nodes, as long as the number of nodes in the plurality of nodes 12 does not exceed eight. In another alternative exemplary embodiment, when not following IEEE 802.3cg 147 guidelines, the plurality of nodes 12 can have more than eight nodes, meaning there can be more than eight low-latency nodes, more than eight medium-latency nodes, and more than eight best-effort nodes. It should also be understood that, while the configuration of the modulo operation of multiple network device parameters 80 in the second exemplary embodiment limits the number of nodes 12 with transmission opportunities in a given communication period to three, in an alternative embodiment, the configuration of the modulo operation of multiple network device parameters 80 can allow up to all enabled nodes in the plurality of nodes 12 to have one transmission opportunity in a given communication period.
[0067] It should also be understood that, while in the second exemplary embodiment, the configuration of the group of modulo operations on multiple network device parameters 80 treats each medium-latency node and each best-effort node fairly, thereby allowing each medium-latency node to have one transmission opportunity every one communication cycle and each best-effort node to have one transmission opportunity every four communication cycles, in an alternative exemplary embodiment, the configuration of the group of modulo operations on multiple network device parameters 80 may allow a particular medium-latency node and best-effort node to have more transmission opportunities than other medium-latency nodes and best-effort nodes, respectively, within the same number of communication cycles. It should be understood that, while in the second exemplary embodiment there are three categories of nodes (low latency, medium latency, and best-effort), in an alternative exemplary embodiment there may be more or fewer categories of nodes corresponding to the priority levels of the data payloads determined in functional software block 60.
[0068] In an alternative exemplary embodiment where the burst mode feature of 10Base-T1S is enabled, the modulo-based scheduling also initializes the burst limit integer for each of the plurality of nodes 12 to a pre-configured value received from the functional software block 60. The burst limit integer is a value that limits the number of Ethernet frames a given node among the plurality of nodes 12 can transmit during its transmission opportunity. It should be understood that enabling the burst mode feature while scheduling transmission opportunities for the plurality of nodes 12 using modulo-based scheduling does not preclude any node scheduled to have a transmission opportunity within a given communication period from obtaining that opportunity.
[0069] In an alternative exemplary embodiment of CBTS with 10Base-T1S enabled, based on modular arithmetic scheduling, in a non-limiting example, the value of the credit counter can be increased or decreased at the start of a communication cycle based on the number of Ethernet frames transmitted or the cumulative size of the data payload of Ethernet frames transmitted from the corresponding queue corresponding to the credit counter.
[0070] Reference Figure 6 The diagram shows a third table 84, which illustrates an exemplary embodiment of transmission opportunities for multiple nodes 12 relative to a local cycle counter 76 using repetitive pattern scheduling. The third table 84 has three large columns representing the multiple nodes 12. Each large column has a modulus column 86 and a transmission column 88. The modulus column 86 shows the result of the modulo operation of the repetitive pattern equation, and the transmission column 88 indicates whether a corresponding node among the multiple nodes 12 has a transmission opportunity within a given communication cycle. Each row of the third table 84 represents the value of the local cycle counter 76, incremented from the top to the bottom of the third table 84.
[0071] The repetitive mode scheduling configuration is in scheduling block 64 and allows low-latency nodes one transmission opportunity per communication cycle of the 10Base-T1S data bus 14, while limiting the transmission opportunities for best-effort nodes per communication cycle. This feature of repetitive mode scheduling, which limits the transmission opportunities of best-effort nodes, reduces the worst-case latency of low-latency node transmissions by decreasing the number of nodes with transmission opportunities per communication cycle, thereby providing each low-latency node with shorter communication cycles and more frequent transmission opportunities. The repetitive mode scheduling receives a set of multiple network device parameters 90 for repetitive mode to help determine whether a particular node among the multiple nodes 12 has a transmission opportunity within a communication cycle.
[0072] The set of multiple network device parameters 90 in the repeating pattern are parameters configured within the functional software block 60 and indicate the priority level of each of the multiple nodes 12 (e.g., low latency and best-effort) to the scheduling block 64. Each of the multiple network device parameters in the set of multiple network device parameters 80 corresponds to a single node among the multiple nodes 12. Each repeating pattern multiple network device parameter has a pattern depth configuration parameter (pd). i This parameter indicates the number of communication cycles performed before the transmission opportunity pattern from a single node repeats from multiple nodes 12. Multiple network device parameters for each repeating pattern also have pd. i A bit sequence, represented as integers (i.e., (0, 0, 1)) stored separately in each index. It should be understood that pd i The number of individual indices of a bit sequence is equal to pd. i The value (i.e., when pd) i When pd equals 3, i The bit sequence has 3 separate indices. It should also be understood that, in an alternative exemplary embodiment, pd i A sequence of bits, in the unrestricted list of examples, can be represented as a bit field, a floating-point number, a double, or another data type.
[0073] Repetitive mode scheduling receives the corresponding multiple repetitive mode network device parameters from the set of multiple repetitive mode network device parameters 90 and the local period counter 76, and inputs them into the repetitive mode equation (cc). i mod pd i )+1=pn i In this process, it is determined which of the multiple nodes 12 should receive a transmission opportunity within a given communication period. It should be understood that cc i This represents the value of the local cycle counter 76 during a given communication cycle, while pn i This represents the pd of a single node from multiple nodes 12. i The index of the corresponding bit sequence corresponds to the pattern number. When pdi The pnth bit of the bit sequence i When the index equals 1, the repeating pattern scheduling determines that one of the multiple nodes 12, corresponding to the input repeating pattern multiple network device parameters, has one transmission opportunity within a given communication cycle. When pd i The pnth bit of the bit sequence i When an index is not equal to 1, the repeating pattern scheduling determines that one of the multiple nodes 12 corresponding to the multiple network device parameters of the input repeating pattern has no transmission opportunity within a given communication period.
[0074] In an exemplary embodiment, the plurality of nodes 12 have three nodes, and the set of repeating pattern plurality of network device parameters 90 has the following repeating pattern plurality of network device parameters: pd i =1, pd i The bit sequence of the bits is represented as (1), corresponding to the node with ID 0; pd i =3, pd i The bit sequence of the bit is represented as (1,1,0), corresponding to the node with ID 1; and pd i =3, pd i The bit sequence is represented as (0,0,1), corresponding to node ID 2. It should be understood that the configuration of multiple network device parameters 80 in this modulo operation indicates that node ID 0 is a low-latency node, node ID 1 is a medium-latency node, and node ID 2 is a best-effort node.
[0075] In an exemplary embodiment, after inputting the parameters of multiple network devices corresponding to the repetition pattern into the repetition pattern equation, when the value of the local period counter 76 is 0, the pn of node with ID 0, node with ID 1, and node with ID 2... i They are 1, 1, and 1 respectively. This corresponds to pd for each of the multiple nodes 12. i The pnth bit of the bit sequence i There are three indices, namely the pd of the node with ID 0, the node with ID 1, and the node with ID 2. i The first index of the bit sequence is 1, 1, and 0 respectively. This is because the pd corresponds to the node with ID 0 and the node with ID 1. i The pnth bit of the bit sequence i Each index equals 1, therefore the node with ID 0 and the node with ID 1 have one transmission opportunity within a communication cycle in which the value of the local cycle counter 76 is 1 (represented by "X" in the corresponding cell of the third table 84).
[0076] When the value of the local cycle counter 76 is 1, the pn of node with ID 0, node with ID 1, and node with ID 2 i They are 1, 2, and 2 respectively. And each of the multiple nodes 12 corresponds to pd.i The pnth bit of the bit sequence i There are three indices, namely the pd of the node with ID 0, the node with ID 1, and the node with ID 2. i The first index of the bit sequence is 1, 1, and 0 respectively. This is because the pd corresponds to the node with ID 0 and the node with ID 1. i The pnth bit of the bit sequence i The index is equal to 1, therefore the node with ID 0 and the node with ID 1 have one transmission opportunity. When the value of the local cycle counter 76 is 2, the pn of the nodes with ID 0, ID 1, and ID 2... i They are 1, 3, and 3 respectively. And the corresponding pd for each of the multiple nodes 12. i The pnth bit of the bit sequence i There are three indices, namely the pd of the node with ID 0, the node with ID 1, and the node with ID 2. i The first index of the bit sequence is 1, 0, and 1 respectively. This is because the pd corresponding to the node with ID 0 and the node with ID 2... i The pnth bit of the bit sequence i The index is equal to 1, so the node with ID 0 and the node with ID 2 have one transmission opportunity. Then the communication cycle pattern repeats, where the node with ID 0 has one transmission opportunity per communication cycle, the node with ID 1 has two consecutive transmission opportunities every three communication cycles, and the node with ID 2 has one transmission opportunity every three communication cycles.
[0077] It should be understood that, in one alternative exemplary embodiment, when following IEEE 802.3cg 147 guidelines, the configuration of the set of repeating mode network device parameters 90 can indicate up to eight low-latency nodes, up to eight medium-latency nodes, and up to eight best-effort nodes, provided that the number of nodes in the plurality of nodes 12 does not exceed eight. In another alternative exemplary embodiment, when not following IEEE 802.3cg 147 guidelines, the plurality of nodes 12 can have more than eight nodes, meaning there can be more than eight low-latency nodes, more than eight medium-latency nodes, and more than eight best-effort nodes. It should also be understood that, while the configuration of the set of repeating mode network device parameters 90 in the exemplary embodiment limits the number of the plurality of nodes 12 that can have a transmission opportunity in a given communication cycle to two, in one alternative embodiment, the configuration of the set of repeating mode network device parameters 90 can allow up to all enabled nodes in the plurality of nodes 12 to have a transmission opportunity once in a given communication cycle.
[0078] It should also be understood that in an alternative exemplary embodiment where there are three or more nodes among the plurality of nodes 12, the configuration of the plurality of network device parameters 90 in this set of repeating patterns can provide a particular medium-latency node and a best-effort node with more transmission opportunities in the same number of communication cycles than other medium-latency nodes and best-effort nodes, respectively. It should be understood that although there are three categories of nodes (low latency, medium latency, and best-effort) in the exemplary embodiment, in an alternative exemplary embodiment, there may be more or fewer categories of nodes corresponding to the priority levels of the data payloads determined in functional software block 60.
[0079] In an alternative exemplary embodiment where the burst mode feature of 10Base-T1S is enabled, the repetitive mode scheduling also initializes the burst limit integer of each of the plurality of nodes 12 to a pre-configured value received from the functional software block 60. It should be understood that enabling the burst mode feature while repetitive mode scheduling schedules transmission opportunities for the plurality of nodes 12 does not preclude any node scheduled to have a transmission opportunity within a given communication period from obtaining a transmission opportunity.
[0080] In an alternative exemplary embodiment of enabling 10Base-T1S CBTS, repeating mode scheduling, in a non-limiting example, may increase or decrease the value of the credit counter based on the number of Ethernet frames transmitted or the cumulative size of the data payload of Ethernet frames transmitted from the corresponding queue corresponding to the credit counter at the start of a communication cycle.
[0081] The scheduling block 64 of this disclosure offers several advantages. One such advantage is the implementation of modular arithmetic-based scheduling and repetitive mode scheduling, which reduces the worst-case latency of network 10 and 10Base-T1S data bus 14 by reducing the number of nodes 12 with transmission opportunities in any given communication cycle. The implementation of modular arithmetic-based scheduling and repetitive mode scheduling enables shorter communication cycles and ensures that low-latency nodes always have frequent transmission opportunities. Another such advantage is that it allows the configuration of the set of modular arithmetic network device parameters 80 and the set of repetitive mode network device parameters 90 via functional software block 60, thereby enabling flexibility and customizability in determining the frequency at which specific nodes among the nodes 12 receive transmission opportunities based on the needs of network 10. Yet another such advantage is the implementation of a local cycle counter 76 to help scheduling block 64 determine which of the nodes 12 has a transmission opportunity in any given communication cycle.
[0082] The description in this disclosure is merely exemplary in nature, and variations thereof without departing from the spirit and scope of this disclosure are intended to fall within its scope. Such variations should not be considered as departing from the spirit and scope of this disclosure.
Claims
1. A method for controlling data transmission over a network, the method comprising: Provide a network bus for transmitting data on the network; A plurality of network devices are provided, each of which is electrically connected to the network bus, and each of the plurality of network devices has a network controller, wherein each network controller is programmed to: Implement a period counter on each of the plurality of network devices; Assign multiple network device parameters to each of the plurality of network devices; A schedule is created for transmitting data by each of the plurality of network devices, wherein the schedule indicates whether each of the plurality of network devices can transmit data, and wherein the schedule allows each of the plurality of network devices to transmit data based on the period counter and the parameters of the plurality of network devices.
2. The method according to claim 1, wherein, Assigning parameters to multiple network devices also includes assigning modulo values.
3. The method according to claim 2, wherein, Assigning parameters for multiple network devices also includes assigning offset values.
4. The method according to claim 3, wherein, Creating a schedule for transmitting data by each of the plurality of network devices also includes determining whether the following equation is true (cc i +o i )mod m i =0, where: cc i = Periodic counter; o i = Offset value; and m i = Modulus value.
5. The method according to claim 4, wherein, Creating a schedule for transmitting data by each of the plurality of network devices also includes selecting m i and o i The value of allows only a predetermined number of network devices to transmit data within a single cycle.
6. The method according to claim 1, wherein, Assigning parameters for multiple network devices also includes assigning mode depth values.
7. The method according to claim 6, wherein, The pattern depth value is determined based on a sequence of bits.
8. The method according to claim 7, wherein, Assigning parameters to multiple network devices also includes using the formula pn i =(cc i mod pd i +1 determines the pattern number, where: cc i = Periodic counter; pd i = Pattern depth value; and pn i = Pattern number.
9. The method according to claim 8, wherein, When pd i The pnth bit sequence i When an index equals 1, the timetable allows each of the multiple high-priority network devices to transmit data.
10. A system for controlling data transmission over a network, the system comprising: A network bus for transmitting data on the network; A plurality of network devices, each of which is electrically connected to the network bus, and each of which has a network controller, wherein each network controller is programmed to: Implement a period counter on each of the plurality of network devices; Assign multiple network device parameters to each of the plurality of network devices; A schedule is created for transmitting data by each of the plurality of network devices, wherein the schedule indicates whether each of the plurality of network devices is capable of transmitting data, and wherein the schedule allows each of the plurality of network devices to transmit data based on the period counter and the parameters of the plurality of network devices.
