Gate status confirmation system, gate status confirmation method, and communication device
The system addresses packet stagnation issues in TSN hubs by verifying gate settings through packet exchange and time difference calculations, ensuring efficient and error-free packet transmission.
Patent Information
- Application Number
- JP2021049816
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-03-24
- Publication Date
- 2024-11-13
- Estimated Expiration
- 2041-03-24
AI Technical Summary
In TSN-compatible communication devices, individual gate settings between TSN hubs can lead to packet stagnation if not correctly set, risking delays and potential packet loss.
A system and method for checking the status of gates by sending packets between communication devices to calculate the time difference based on Meanpath values and actual reception times, allowing for confirmation of gate settings.
Enables detection of errors in gate settings, ensuring timely packet transmission and reducing packet loss by confirming the status of gates between TSN hubs.
Smart Images

Figure 0007582004000001 
Figure 0007582004000002 
Figure 0007582004000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a communication device equipped with the "IEEE802.1AS (gPTP)" function and the "IEEE802.1Qbv (traffic scheduling)" function of TSN (Time-Sensitive Networking). [Background technology]
[0002] TSN, described in Patent Document 1 and Non-Patent Document 1, is a network technology that enables interoperability between industrial networks and IT networks that extend standard Ethernet (registered trademark), and is composed of multiple standards such as "IEEE802.1AS" and "IEEE802.1Qbv."
[0003] 1. IEEE802.1AS The "IEEE802.1AS" standard is abbreviated as "gPPT." Time synchronization packets using this "gPTP" function are different from normal PTP time synchronization packets in that they are L2 layer and can only use the "PtoP (between adjacent devices)" transparency function.
[0004] Specifically, time synchronization of the "gPTP function" goes through the "PtoP (between adjacent devices)" TWO step as shown in Figure 1, and the transmission time D (Meanpath) is calculated using Equation 1.
[0005] Equation (1): Transmission time D = (T4-T3) + (T2-T1) / 2 = (T4-T1) - (T3-T2) / 2 Figure 2 shows the difference between time synchronization by PTP's ONE step and the above-mentioned TWO step, using the "SYNC" message as an example. That is, in the "ONE step", the "T1" timestamp information is set in the "SYNC" message packet and sent.
[0006] On the other hand, in the TWO step, "T1" is set in the "Follow_UP" message packet rather than the "SYNC message" packet and sent (the same applies to the "Pdelay_Resp_Follow_UP" message).
[0007] Then, the elapsed time (t1) from "T1" is calculated using Equation 2, which takes into account the delay in reception time (t3-T2) based on Figure 2, and the time correction between the master and slave is performed from the time difference between "t1" and "t3".
[0008] Equation (2): Elapsed time (t1) = T1 + D + (t3 - T2) 2. IEEE802.1Qbv The IEEE802.1Qbv time-aware scheduler divides communication on an Ethernet network into fixed-length, repeating time cycles, and configures time slices within these cycles that are assigned to one or more of the eight Ethernet priorities (the "traffic scheduling" function).
[0009] This allows guaranteed and uninterruptible traffic classes to be granted exclusive use of the Ethernet transmission medium for a limited time.The basic concept is Time Division Multiple Access (TDMA), which allows time-critical communications to be separated from non-critical background traffic by establishing virtual communications channels for specific periods of time. [Prior art documents] [Patent documents]
[0010] [Patent Document 1] Patent Publication No. 2020-107943 [Non-patent literature]
[0011] [Non-Patent Document 1] “Overview and implementation of “TSN” that integrates IT and OT networks”, [online], retrieved on March 3, 2021, Internet<URL:http:ednjapan.com / edn / arrticies / 1803 / 23 / news014.html> Summary of the Invention [Problem to be solved by the invention]
[0012] TSN-compatible communication devices (switching hubs: hereafter referred to as TSN hubs) are equipped with the "gPTP" function and the "traffic scheduling" function.
[0013] This enables time synchronization between TSN hubs and sets up traffic scheduling (hereinafter referred to as "gates") for packet transmission that is staggered by the distance between the TSN hubs and the time required to pass through the TSN hubs, making it possible to transmit priority packets without delay even under high load.
[0014] However, since gates are configured individually by each TSN hub, there was a risk of packets being stalled if the gates between all TSN hubs were not configured correctly.
[0015] Therefore, an object of the present invention is to propose a method for detecting errors in gate settings by checking the gate status between TSN-compatible communication devices. [Means for solving the problem]
[0016] (1) One aspect of the present invention is a system for checking the status of a gate that defines a schedule for packet transmission set in a TSN-compatible communication device, the system comprising: The communication device that initiates the confirmation transmits a packet to and from the other communication device that is arbitrarily selected as the target of the confirmation, Obtain gate information describing the "Meanpath value" between the two communication devices and the actual reception time to the other communication device; Calculate the time difference between the ideal reception time based on the "Meanpath value" described in the gate information and the actual reception time, The state of the gate is confirmed based on the time difference.
[0017] (2) Another aspect of the present invention is a method for checking the status of a gate that defines a schedule for packet transmission set in a TSN-enabled communication device, the method comprising: A step in which one of the communication devices which initiates the confirmation transmits a packet back and forth between the communication device and the other communication device which is arbitrarily selected as the subject of the confirmation, thereby acquiring gate information in which a "Meanpath value" between the two communication devices is described and an actual reception time to the other communication device; The method is characterized by having a step of calculating a time difference between an ideal reception time based on a "Meanpath value" described in the gate information and the actual reception time, and confirming a state of the gate based on the calculated time difference.
[0018] (3) Yet another aspect of the present invention is a TSN-compatible communication device, A function for checking the gate status that defines the schedule for TSN packet transmission in other arbitrarily selected communication devices, By sending a packet back and forth to another communication device that is arbitrarily selected as the target of the confirmation, gate information describing the "Meanpath value" between the two communication devices and the actual reception time to the other communication device are obtained; Calculate the time difference between the ideal reception time based on the "Meanpath value" described in the gate information and the actual reception time, The state of the gate is confirmed based on the time difference. Effect of the Invention
[0019] According to the present invention, it is possible to check the gate status between TSN hubs, making it possible to detect errors in gate settings, etc. [Brief description of the drawings]
[0020] [Figure 1] Schematic diagram of TSN time synchronization (gPTP). [Diagram 2] A schematic diagram showing the difference between the ONE step and the TWO step. [Diagram 3] Network configuration diagram of a TSN hub. [Figure 4] Schematic showing an example of a gate configuration within a TSN hub. [Diagram 5] FIG. 2 is a transmission path diagram of a gate confirmation packet and a gate information packet of the gate status confirmation system according to the embodiment of the present invention. [Figure 6] FIG. 4 is an explanatory diagram showing the generation of gate information. [Figure 7] FIG. 13 is an explanatory diagram showing the processing performed when a gate status confirmation request is made. [Figure 8] FIG. 11 is an explanatory diagram showing the processing performed when responding to a gate status confirmation response. [Figure 9] FIG. 11 is an explanatory diagram showing the gate confirmation process of the same. [Figure 10] A flowchart showing the main processing of TSN packet transfer in the "gPTP" task. [Figure 11] A flowchart showing the gate confirmation packet reception processing of the "gPTP" task. [Figure 12] 13 is a flowchart showing a gate management main process of the gate management task of the embodiment; [Figure 13] 4 is a flowchart showing gate information receiving processing according to the embodiment; [Figure 14] 13 is a flowchart showing the gate status confirmation request process of the embodiment; [Figure 15] 4 is a flowchart showing the gate status confirmation response process of the first embodiment; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0021] The following describes a gate status confirmation system according to an embodiment of the present invention. This gate status confirmation system can confirm whether a gate for packet transmission for each class set on a TSN hub is operating normally between any TSN hubs.
[0022] As an example, consider the network shown in Figure 3. This network is made up of TSN hubs 1 to 7. These TSN hubs 1 to 7 are equipped with the TSN "IEEE802.1AS (gPTP)" function and "IEEE802.1Qbv (traffic scheduling)" function.
[0023] Therefore, time synchronization is possible between TSN hubs 1 to 7 using the "gPTP" function, and the "gPTP" ports of each TSN hub 1 to 7 are configured with a traffic scheduling function that takes into account the transmission delay between TSN hubs 1 to 7 (hereinafter, traffic scheduled to the "gPTP" ports inside the TSN hub will be referred to as a gate.)
[0024] In Figure 3, the "Roman numerals + TSN hub numbers" between TSN hubs 1 to 7 represent the "Meanpath" values in the arrow directions between TSN hubs 1 to 7. That is, "≡-1" and "≡-2" represent the "Meanpath" values between TSN hubs 1 and 2, "≡-1" and "≡-2" represent the "Meanpath" values between TSN hubs 2 and 3, “≡―1” and “≡―2” indicate the “Meanpath” values between TSN hubs 3 and 4, “≡―1” and “≡―2” indicate the “Meanpath” value between TSN hubs 2 and 5. “≡―1” and “≡―2” indicate the “Meanpath” value between TSN hubs 5 and 6. “≡―1”·“≡―2” indicates the “Meanpath” value between TSN hubs 6 and 7.
[0025] 4 shows an example of a gate function using the TSN hub 6. In this example, the TSN hub 6 can set "Priority 0 to 7" (hereinafter referred to as "Qpri0 to 7") of a "Queue" as a gate 14, and can transmit data in the order of the set "Qpri0 to 7" with priority for a certain period of time.
[0026] For example, when "Qpri5" of gate 14 is open, a packet of "Queue5" that enters "gPTP" port 11 of TSN hub 6 is forwarded to "gPTP" port 12, but if "Qpri" of another gate 14 is open, the packet is not forwarded and is put into a waiting state until the next time "Qpri5" of gate 14 opens. Note that TSN hubs 1, 2, 4 to 7 also have the same gate function.
[0027] "Qpri" of gates 14 of TSN1 to 7 works in conjunction with time synchronization (gPTP), so packets corresponding to "Qpri" can be transmitted without stress even under high load conditions.
[0028] However, if the "Qpri" of the gate 14 of each TSN hub 1-7 is not set correctly, it will take a long time to open the "Qpri" of the gate 14 for each TSN hub 1-7, which may cause packet loss in the worst case. Therefore, the gate status confirmation system checks the gate status by the following operation.
[0029] <Gate status check operation> TSN hubs 1 to 7 arranged on the network in Figure 3 check the gate status between any of TSN hubs 1 to 7 when "gPTP" time synchronization and gate settings are functioning.
[0030] As an example, the overall operation of the system when checking the gate status from TSN hub 1 to TSN hub 7 will be described with reference to Figures 6 to 9. Here, TSN hubs 1 to 7 each include a "gPTP" task 21 and a gate management task 23.
[0031] 6 to 9, 21a and 23a indicate the "gPTP" task 21 and the gate management task 23 of the TSN hub 1 that starts checking the gate status. 21b and 23b indicate the "gPTP" task 21 and the gate management task 23 of the TSN hub 7 that is the target (end) of checking the gate status. (1) First, the "gPTP" task 21a sets the "ID" of the TSN hub 7 (see Figure 6) and sets the execution flag.
[0032] Then, a gate confirmation packet is sent from TSN hub 1 using “gPTP” port 12 to TSN hub 7 via TSN hubs 2, 5, and 6, as shown by arrow R1 in Figure 5.
[0033] At this time, the "gPTP" task 21 of TSN hubs 2, 5, and 6 adds its own "ID" and the "Meanpath value" of the packet input port (receiving port) 11 to the data section 25 (see Figure 6) of the received gate confirmation packet, and forwards it to the next TSN hub.
[0034] That is, "TSN hub 2 → TSN hub 5", "TSN hub 5 → TSN hub 6", The packet is forwarded in the order of "TSN Hub 6 → TSN Hub 7." Finally, when TSN Hub 7 receives the gate state confirmation packet, the "gPTP" task 21b generates the gate information 26 in FIG.
[0035] In more detail, when the gate status confirmation packet is received by TSN hub 7, data portion 25 contains the "IDs of TSN hubs 2, 5, and 6" and the "Meanpath value" on the packet input port 11 side for each "ID."
[0036] Then, the "gPTP" task 21b adds its own "ID" and the "Meanpath value" for each of its packet input ports to the information in the data part 25, thereby generating gate information 26 that describes the "Meanpath values" between TSN hubs 1, 2, 5 to 6.
[0037] After creating this gate information 26, the "gPTP" task 21b issues a gate information notification to the gate management task 23b in the TSN hub 7. The gate management task 23b that receives this gate information notification generates a gate information packet that describes the gate information 26. The generated gate information packet is transmitted to TSN1 via TSN6, 5, and 2, as shown by the arrow R2 in FIG.
[0038] (2) Next, the gate management task 23a in the TSN hub 1 acquires the gate information 26 from the gate information packet and stores the acquired gate information 26. The gate management task 23a also generates a dummy packet (gate state confirmation request packet) for gate state confirmation for the TSN hub 7, as shown in Fig. 7. The generated gate state confirmation request packet is sent to the TSN hub 7 via the route indicated by the arrow R1, including the transmission time.
[0039] When the TSN hub 7 receives this gate status confirmation request packet, the gate management task 23b calculates the reception time of the gate status confirmation request packet of the TSN hub 7. Here, the TSN hubs 1 to 7 are time-synchronized by "gPTP", and the reception time is calculated based on the transmission and reception times synchronized by "gPTP". A specific calculation method uses the formula (3) in Figs. 7 and 8.
[0040] After calculating the reception time, the gate management task 23b sends a gate status confirmation response packet containing the reception time, the destination ID (TSN Hub 1), and the source ID (TSN Hub 7) to TSN Hub 1 via the route indicated by arrow R2.
[0041] (3) When the TSN hub 1 receives the gate state acknowledgement packet, as shown in Fig. 8, the gate management task 23a calculates the ideal reception time of the TSN hub 7 based on the gate information 26. A specific calculation method uses the formula (4) in Fig. 8.
[0042] Furthermore, the gate management task 23a obtains the time difference between the ideal reception time and the reception time (actual reception time) of the gate status confirmation response packet. Since the time difference obtained here is affected by the gate shift set in the TSN hubs 1 to 7, the actual reception time deviates from the ideal reception time by the gate shift. After that, the gate management task 23a presents the gate information 26 and the time difference by outputting them to a screen or file on a computer such as an administrator.
[0043] (4) After that, the “gPTP” task 21a and the gate management task 23a of the TSN hub 1 check the gate status of the TSN hubs 2, 5, and 6 in the same manner as the TSN hub 7 (by sending a gate status confirmation request packet and a gate status confirmation response packet back and forth), as shown in FIG. 9, and output the confirmation result 30. At this time, the ideal reception time of TSN hubs 2, 5, and 6 can be calculated from gate information 26, so transmission of gate information packets is omitted. Also, in confirmation result 30, the time difference with TSN hub 7, which is the confirmation target (destination), is displayed first, and then the time differences with TSN hubs 2, 5, and 6 are displayed in order. Here, if it is determined that the time difference with TSN hub 7 is small, the time differences with TSN hubs 2, 5, and 6 are treated as only a reference.
[0044] On the other hand, if it is determined that the time difference with TSN hub 7 is large, it is possible to quickly detect the location of the problematic gate by checking the time differences with TSN hubs 2, 5, and 6. The size of the time difference can be automatically detected by setting a threshold value in advance. For example, if the time difference between TSN hubs 7, 2, 5, and 6 exceeds a threshold value, it may be automatically detected that the time difference of TSN hub 7 is large.
[0045] <<Internal processing of TSN hub>> As described above, when checking the gate status from TSN hub 1 to TSN hub 7, TSN packet forwarding main process in Figure 10 Gate confirmation packet reception process in Figure 11 Gate management main process in Figure 12 Gate information reception process in Figure 13 · Gate status confirmation request processing in Figure 14 Gate status confirmation response process in Figure 15 is executed.
[0046] The TSN packet transfer main process and gate confirmation packet reception process are executed by the "gPTP" task 21. On the other hand, the gate management main process, gate information reception process, gate status confirmation request process, and gate status confirmation response process are executed by the gate management task 23.
[0047] (1) TSN packet forwarding main processing The TSN packet forwarding main process will be explained with reference to Figure 10. This process is started when an administrator or other person uses a command to input the following data A and B and writes them to the gate information definition file. A: ID of the destination TSN hub (the TSN hub to be checked) B: Gate start confirmation flag (= TRUE) S01: The "gPTP" task 21 of the TSN hub reads the gate definition file and sets the data A and B as internal data of the TSN hub.
[0048] S02: The "gPTP" task 21 checks whether to start checking the gate status by referring to its own gate check start flag. If the flag is set as a result of the check, the process proceeds to S03 to start checking the gate status. On the other hand, if the flag is not set, the process proceeds to S06.
[0049] For example, in the case of "gPTP" 21a of TSN hub 1, the gate confirmation start flag is set, so proceed to S06. On the other hand, in the case of "gPTP" task 21b of SN hubs 2, 5, 6, and 7, the gate start flag is not set, so proceed to S06.
[0050] S03 to S05: The “ID” of the TSN hub that starts checking the gate status and the “ID” of the TSN hub that is the target (end) of the check (the “ID” of the destination TSN hub) are set in the gate information (S03).
[0051] After that, a gate confirmation packet is generated (S04) and sent from the "gPTP" port 11 to the TSN hub to be confirmed (S05). For example, in the case of "gPTP" 21a of TSN hub 1, a gate confirmation packet with TSN hub 7 as the destination "ID" is generated and sent.
[0052] S06, S07: If a TSN hub other than the sender of S05 receives the TSN packet (S06), the "gPTP" task 21 of that TSN hub checks whether the TSN packet is a gate confirmation packet (S07).
[0053] If the result of the check is that it is a gate confirmation packet, the process proceeds to gate confirmation packet reception processing in S08, otherwise the process proceeds to existing TSN packet reception processing in S09. For example, the "gPTP" task 21b of TSN hubs 2, 5, 6, and 7 receives the gate confirmation packet sent from TSN hub 1 and proceeds to gate confirmation packet reception processing in S08.
[0054] (2) Gate confirmation packet reception process The gate confirmation packet reception process in S08 will be described in detail with reference to Fig. 11. This process is executed by the "gPTP" task 21 of the TSN hub that received the gate confirmation packet as described above.
[0055] S11 to S13: When the process starts, the "gPTP" task 21 obtains the "ID" of the TSN hub to be confirmed from the received packet (gate confirmation packet) of S06 (S11).
[0056] After that, the acquired "ID" is compared with the "ID" of the own TSN hub (S12) to check whether they are the same (S13). If they are not the same, proceed to S14, but if they are the same, proceed to S16. For example, if the TSN hubs are 2, 5, and 6, proceed to S14, and if the TSN hub is 7, proceed to S16.
[0057] S14, S15: The processing here is performed by intermediate TSN hubs such as TSN hubs 2, 5, and 6 that relay the gate confirmation packet.
[0058] First, the "ID" of its own TSN hub and the "Meanpath" value on the receiving port 11 side of S06 are added to the data portion (received information) 25 of the received packet (gate confirmation packet) of S06 (S14).
[0059] Next, a gate confirmation packet is created based on the added reception information and transmitted from a "gPTP" port 12 other than the reception port (S15). For example, TSN hub 2 transmits to TSN hub 5, TSN hub 5 transmits to TSN hub 6, and TSN hub 6 transmits to TSN hub 7.
[0060] S16 to S18: The processes here are executed by a TSN hub such as the TSN hub 7 that is the target of checking the gate status.
[0061] That is, the data portion 25 of the received packet of S06 is saved as gate information (S16), and the "ID" of its own TSN hub and the "Meanpath" value on the receiving port 11 side of S06 are added to the saved gate information (S17).
[0062] Thereafter, a gate information notification (gate confirmation reception notification) is transmitted to the gate management task 23 (S18). For example, the "gPTP" task 21b of the TSN hub 7 transmits a gate information notification to the gate management task 23b.
[0063] (3) Gate management main processing The gate management main process will be described in detail with reference to Fig. 12. This process is executed by the gate management task 23 of the TSN hub.
[0064] S21, S22: That is, when the process starts, the gate management task 23 checks whether there is a gate information notification in S18 (S21, S22). If there is a gate information notification as a result of the check, the process proceeds to S23, whereas if there is no such notification, the process proceeds to S25.
[0065] S23, S24: The gate management task 23 generates a gate information packet based on the received gate information notification (S23), and transmits the generated gate information packet to the TSN hub that started the confirmation (S24). For example, the gate management task 23b of the TSN hub 7 transmits the gate information packet to the TSN hub 1.
[0066] S25, S26: The gate management task 23 receives the TSN packet of S06 (S25), and checks whether or not a gate information packet has been received (S26). If the check result shows that a gate information packet has been received, the process proceeds to gate information reception processing of S27, and if not, the process proceeds to S28.
[0067] S28 to S30: The gate management task 23 checks whether the received packet in S25 is a gate state confirmation packet (S28).
[0068] If the result of the check is that the packet is a gate status check request packet, the process proceeds to gate status check request processing in S29, and if not, the process proceeds to S30.
[0069] In S30, it is confirmed whether the packet received in S25 is a gate state acknowledgement packet. If it is found to be a gate state acknowledgement packet, the process proceeds to gate state acknowledgement processing in S31, but if not, the process ends.
[0070] (4) Gate information reception processing The gate information receiving process in S27 will be described in detail with reference to FIG.
[0071] S41 to S43: When the process starts, the gate management task 23 acquires the "ID" of the TSN hub that starts the confirmation from the data portion 25 of the received packet of S25 (S41).
[0072] Thereafter, the acquired "ID" is compared with the "ID" of the own TSN hub (S42). If the comparison result shows that the "ID" is the same, the process proceeds to S44, but if not, the process ends (S43).
[0073] S44, S45: The gate management task 23 saves the data portion 25 (only after the addition in S14) of the received packet as gate information (S44), and obtains the ID of the TSN hub to be confirmed from the saved gate information (S45).
[0074] Thereafter, a gate status confirmation request packet is generated (S46), and the generated gate status confirmation request packet is sent to the TSN hub of the "ID" to be confirmed (S47), thereby completing the process.
[0075] For example, the gate management task 23a of TSN1 obtains the “ID” of the TSN hub 7 from the stored gate information, generates a gate status confirmation request packet, and transmits the generated gate status confirmation request packet to the TSN hub 7.
[0076] (5) Gate status confirmation request processing The gate status confirmation request process in S29 will be described in detail with reference to FIG.
[0077] S51 to S53: When the process starts, the gate management task 23 acquires the ID of the destination TSN hub from the data portion 25 of the received packet of S25 (S51).
[0078] Thereafter, the acquired "ID" is compared with the "ID" of the own TSN hub (S52). If the comparison result shows that the "ID" is the same, the process proceeds to S54, but if not, the process ends (S53).
[0079] S54 to S57: The gate management task 23 calculates the reception time of the received packet of S25 (S54). After this calculation, the "ID" of the source TSN hub is obtained from the data portion 25 of the received packet (S55), and a gate status confirmation response packet describing the reception time is generated (S56).
[0080] The gate status confirmation response packet generated here is sent to the TSN hub having the “ID” of S55 (S57), and the process ends. For example, the gate management task 23b of the TSN hub 7 calculates the reception time of the gate status confirmation request packet (see formula (1) in FIG. 7 and FIG. 8), and sends the calculated reception time to the TSN hub 1 as a gate status confirmation response packet.
[0081] (6) Gate status confirmation response processing The gate state confirmation response process in S31 will be described in detail with reference to FIG.
[0082] S61: When processing starts, the gate management task 23 obtains the TSN hub reception time, the source TSN hub "ID", and the destination TSN hub "ID" from the data portion 25 of the received packet of S25.
[0083] S62: Calculate the ideal reception time to the TSN hub of the source “ID” acquired in S61. For example, the gate management task 23a of TSN hub 1 calculates the ideal reception time to TSN 7 based on the “Meanpath” value of the gate information saved in S44 (see formula (2) in FIG. 8).
[0084] S63, S64: The time difference between the reception time acquired in S61 and the ideal reception time calculated in S62 is calculated (S63). The time difference calculated here and the gate information saved in S44 are output, and the result of the gate status check is output (S64).
[0085] S65-S68: The "ID" of the next destination TSN hub (TSN hub to be checked) is obtained (S65). After that, the gate information saved in S44 is referenced to check whether or not there is a TSN hub next to the "ID" obtained in S65 (S66).
[0086] As a result of the check, if the gate status exists, a gate status check request packet is created (S67), and the created gate status check request packet is sent to the TSN hub having the "ID" of the destination (check target) (S68).
[0087] For example, for TSN hubs 2, 5, and 6, if gate information is created in TSN 7, the ideal reception time of S62 can be calculated, so a gate status confirmation request packet is sent without sending a gate confirmation packet by "gPTP" task 21a.
[0088] This gate status confirmation system makes it possible to check the status of all gates between any selected TSN hubs. Therefore, the legitimacy of the gates between TSN hubs can be determined, and problem areas such as gate setting errors can be easily detected.
[0089] At this time, the creation of gate information (Fig. 10 and Fig. 12) and confirmation of gate status (Fig. 12 to Fig. 15) are executed in separate tasks 21 and 23, so the impact on the actual TSN processing is reduced. In particular, if gate information is created in TSN 7, it is only necessary to confirm the gate status for TSN hubs 2, 5, and 6, so the processing burden is also reduced in this respect.
[0090] The present invention is not limited to the above embodiment, and can be modified and implemented within the scope of the claims. For example, the present invention is not limited to checking the gate status from TSN hub 1 to TSN hub 7, and can check the gate status between any TSN hubs. The network configuration is not limited to that shown in FIG. 3, and may be any network configured with TSN hubs. [Explanation of symbols]
[0091] 1~7…TSN Hub 11,12…Port 14…Gate 21, 21a, 21b… “gPTP” tasks 23, 23a, 23b…Gate management tasks 25...Data portion of gate status confirmation packet 26…Gate Information 30...Confirmation result
Claims
1. A system for checking the status of a gate that defines a schedule for packet transmission set in a TSN-enabled communication device, comprising: The communication device that initiates the confirmation transmits a packet to and from the other communication device that is arbitrarily selected as the target of the confirmation, Obtain gate information describing the "mean path value" between the two communication devices and the actual reception time to the other communication device; Calculate the time difference between the ideal reception time based on the "Meanpath value" described in the gate information and the actual reception time, A gate status confirmation system, characterized in that the status of the gate is confirmed based on the time difference.
2. The intermediate communication device that transfers the first packet transmitted from one of the communication devices to the other communication device adds the "Meanpath value" of the receiving port to the data portion of the packet, The other communication device that lastly receives the first packet returns gate information in which the "Meanpath" value on the reception port side is added to the data portion to the one communication device, one of the communication devices transmits a second packet including a transmission time to the other of the communication devices after receiving the reply; The other communication device that has received the second packet calculates an actual reception time based on a transmission / reception time of the second packet, and returns the calculated actual reception time to the one communication device; On the other hand, the communication device calculates the time difference between the ideal reception time based on the "Meanpath" value described in the gate information after receiving the reply and the actual reception time of the reply.
2. The gate information confirmation system according to claim 1.
3. Sending a second packet to the intermediate communication device; The intermediate communication device that has received the second packet calculates the actual reception time based on a transmission / reception time of the second packet, and returns the calculated actual reception time to the one of the communication devices; After receiving the reply, one of the communication devices calculates the time difference between the ideal reception time at the intermediate communication device based on the "Meanpath" value described in the gate information and the actual reception time.
3. The gate information confirmation system according to claim 2.
4. 4. The gate status confirmation system according to claim 1, wherein the gate status is confirmed depending on the magnitude of the time difference.
5. The communication devices are time-synchronized using TSN's "gPTP" The actual reception time is calculated based on the synchronized time.
5. The gate information confirmation system according to claim 1,
6. 1. A method for verifying the status of a scheduled gate for packet transmission configured in a TSN-enabled communication device, comprising: A step in which one of the communication devices initiating the confirmation transmits a packet back and forth between the communication device and the other communication device arbitrarily selected as the subject of the confirmation, thereby acquiring gate information describing a "mean path value" between the two communication devices and an actual reception time to the other communication device; A step of calculating a time difference between an ideal reception time based on a "Meanpath value" described in the gate information and the actual reception time, and confirming a state of the gate based on the calculated time difference; A gate state confirmation method comprising the steps of:
7. A TSN-enabled communication device, a function for checking a gate state that defines a schedule for packet transmission of the TSN in another arbitrarily selected communication device; By sending a packet back and forth to another arbitrarily selected communication device that is the subject of the confirmation, gate information describing a "mean path value" between the two communication devices and an actual reception time to the other communication device are obtained, Calculate the time difference between the ideal reception time based on the "Meanpath value" described in the gate information and the actual reception time, A communication device that checks the state of the gate based on the time difference.
8. A "gPTP" task that transmits a first packet to another communication device and obtains the gate information from a reply from the other communication device; a gate management task of transmitting a second packet including a transmission time to another of the communication devices, and calculating the time difference when an actual reception time based on the transmission and reception time of the second packet is received from the other of the communication devices; 8. The communication device according to claim 7, further comprising:
9. The gate management task transmits the second packet to each intermediate communication device that forwards the first packet; If an actual reception time based on the transmission and reception time of the second packet is returned from the intermediate communication device, Calculate the time difference between the ideal reception time at the intermediate communication device based on the "Meanpath" value of the gate information and the actual reception time of the returned message.
9. The communication device according to claim 8.
10. Another communication device according to claim 8, a "gPTP" task that, upon receiving the first packet, returns gate information describing the "Meanpath" value of the port on which the first packet was received; a gate management task that, upon receiving the second packet, calculates the actual receiving time and returns the calculated time; A communication device comprising:
11. 10. The intermediate communication device of claim 9, a "gPTP" task that, when receiving the first packet, adds the "Meanpath value" of the port on which the first packet is received to the data portion of the first packet and transfers the first packet to another communication device; a gate management task that, upon receiving the second packet, calculates the actual receiving time and returns the calculated time; A communication device comprising:
12. Time is synchronized by TSN's "gPTP", The actual reception time is calculated based on the synchronized time. A communication device according to any one of claims 7 to 11.
Citation Information
Patent Citations
Network condition monitoring method
JP2012134614A
Time division schedule adjusting method
JP2020107943A
Methods, systems, and computer readable media for testing time sensitive network (TSN) elements
US20180309655A1
