A topological network and communication processing method

Abstract

The present application proposes a topology network and communication processing method, including a main node device and at least one ordinary node device, the main node device and the at least one ordinary node device are connected in sequence; the target node device is used to, when receiving a control request frame transmitted by an upstream port, feed back a response waiting frame to the upstream port at intervals of a first preset time, until a response confirmation frame or a response timeout frame is fed back to the upstream port, so as to avoid the upstream device from mistakenly judging that the response of the target node device has timed out; the target node device is also used to, after sending a control request frame through a downstream port, determine that the response of the downstream device has timed out if a response frame fed back by the downstream port is still not received within a second preset time interval, and feed back a response timeout frame through the upstream port to accurately obtain the response status of the downstream device.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a topological network and a communication processing method. Background Art

[0002] With the development of society, the types of electronic devices are becoming more and more abundant. In many scenarios, a single electronic device will not be able to meet the needs of users, and multiple electronic devices need to be combined into a topological network. Under the coordination of the topological network, multiple electronic devices work together. Taking the automotive audio network (AAN, Automotive Audio Network) in the topological network as an example, the automotive audio network is a serial communication network used to interconnect car audio devices. It connects the head unit (Head Unit), digital microphone, radio, power amplifier (PA) and emergency call (E-Call / Telematics) module and other automotive electronic devices in series.

[0003] The in-vehicle audio network consists of multiple nodes, and serial communication is performed between the multiple nodes. How to ensure that the serial communication is orderly and stable has become a difficult problem that technicians in this field continue to pay attention to. Summary of the invention

[0004] The purpose of the present application is to provide a topology network and a communication processing method to at least partially improve the above problems.

[0005] In order to achieve the above purpose, the technical solution adopted in the embodiment of the present application is as follows:

[0006] In a first aspect, an embodiment of the present application provides a topology network, the topology network comprising a master node device and at least one common node device, the master node device and the at least one common node device being connected in sequence;

[0007] The target node device is used for feeding back a response waiting frame to the upstream port every first preset time period when receiving a control request frame transmitted by the upstream port, until feeding back a response confirmation frame or a response timeout frame to the upstream port;

[0008] Wherein, the target node device is any common node device;

[0009] The target node device is further configured to determine that the downstream device response has timed out if no response frame fed back by the downstream port is received within a second preset time interval after sending the control request frame through the downstream port, and feed back a response timeout frame through the upstream port;

[0010] The response frame is any one of a response waiting frame, a response confirmation frame and a response timeout frame.

[0011] In a second aspect, an embodiment of the present application provides a topology network communication processing method, which is applied to a topology network, wherein the topology network includes a master node device and at least one common node device, and the master node device and the at least one common node device are connected in sequence;

[0012] When receiving the control request frame transmitted by the upstream port, the target node device feeds back a response waiting frame to the upstream port every first preset time period until feeding back a response confirmation frame or a response timeout frame to the upstream port;

[0013] Wherein, the target node device is any common node device;

[0014] After the target node device sends the control request frame through the downstream port, if it still does not receive a response frame fed back by the downstream port within a second preset time, it determines that the downstream device response has timed out, and feeds back a response timeout frame through the upstream port;

[0015] The response frame is any one of a response waiting frame, a response confirmation frame and a response timeout frame.

[0016] Compared with the prior art, a topology network and communication processing method provided by an embodiment of the present application includes a master node device and at least one ordinary node device, which are connected in sequence; the target node device is used to, upon receiving a control request frame transmitted by an upstream port, feed back a response waiting frame to the upstream port at intervals of a first preset time period, until a response confirmation frame or a response timeout frame is fed back to the upstream port, so as to avoid the upstream device from mistakenly judging that the response of the target node device has timed out; the target node device is also used to, after sending a control request frame through a downstream port, determine that the response of the downstream device has timed out if no response frame is received from the downstream port within a second preset time period, and feed back a response timeout frame through the upstream port to accurately obtain the response status of the downstream device.

[0017] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0019] Figure 1 A schematic diagram of the structure of a serial topology network provided in an embodiment of the present application;

[0020] Figure 2 A schematic diagram of the structure of a ring topology network provided in an embodiment of the present application;

[0021] Figure 3 A schematic diagram of the initialization process provided in an embodiment of the present application;

[0022] Figure 4 A schematic diagram of the enumeration process provided in the embodiment of the present application;

[0023] Figure 5 Another schematic diagram of the enumeration process provided in the embodiment of the present application;

[0024] Figure 6 A schematic diagram of the AANCD access process provided in an embodiment of the present application;

[0025] Figure 7 Another schematic diagram of the AANCD access process provided in the embodiment of the present application;

[0026] Figure 8 A schematic diagram of the configuration process provided in the embodiment of the present application;

[0027] Fig. 9 Another schematic diagram of the configuration process provided in the embodiment of the present application;

[0028] Fig.10 A flowchart of a topology network communication processing method provided in an embodiment of the present application.

[0029] In the figure: 11-main node device; 12-ordinary node device. DETAILED DESCRIPTION

[0030] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various different configurations.

[0031] Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the present application for which protection is sought, but merely represents selected embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0032] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. At the same time, in the description of this application, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0033] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0034] In the description of the present application, it should be noted that the terms "upper", "lower", "inside", "outside", etc. indicate orientations or positional relationships based on the orientations or positional relationships shown in the accompanying drawings, or are the orientations or positional relationships in which the product of the application is usually placed when in use. They are only for the convenience of describing the present application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the present application.

[0035] In the description of this application, it is also necessary to explain that, unless otherwise clearly specified and limited, the terms "disposed" and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be an indirect connection through an intermediate medium, or it can be the internal communication of two elements. For ordinary technicians in this field, the specific meanings of the above terms in this application can be understood according to specific circumstances.

[0036] In conjunction with the accompanying drawings, some embodiments of the present application are described in detail below. In the absence of conflict, the following embodiments and features in the embodiments can be combined with each other.

[0037] In order to overcome the above problems, the present application embodiment provides a topology network. Figure 1 and Figure 2 , Figure 1 A schematic diagram of the structure of a serial topology network provided in an embodiment of the present application, Figure 2A schematic diagram of the structure of a ring topology network provided in an embodiment of the present application.

[0038] like Figure 1 and Figure 2 As shown, the topology network includes a master node device 11 and at least one common node device 12. The master node device 11 and the at least one common node device 12 are connected in sequence, specifically, they can be connected through a differential bus.

[0039] Alternatively, if Figure 1 As shown, the topology network is a serial topology network, and the downstream port of the master node device 11 is connected to the first common node device 12 (ie Figure 1 The upstream port of the ith ordinary node device 12 is connected to the downstream port of the i-th ordinary node device 12, and the nth ordinary node device 12 (i.e. Figure 1 The downstream port of the No. 3 ordinary node device) is left unconnected, 2≤i≤n, and n is the number of ordinary node devices.

[0040] Alternatively, if Figure 2 As shown, the topology network is a ring topology network, and the downstream port of the master node device 11 is connected to the first common node device 12 (ie Figure 2 The upstream port of the ith ordinary node device 12 is connected to the downstream port of the i-th ordinary node device 12, and the nth ordinary node device 12 (i.e. Figure 2 The downstream port of the ordinary node device No. 3 in the network is connected to the upstream port of the master node device 11, 2≤i≤n, and n is the number of ordinary node devices.

[0041] It should be understood that the downstream device proposed in the present application solution is a device connected to the downstream port of the node, and the upstream device is a device connected to the upstream port of the node. For example, the first common node device 12 is the upstream device of the second common node device 12.

[0042] It should be noted that Figure 1 and Figure 2 In the description, n=3 is taken as an example, but it is not limited thereto.

[0043] It should be understood that Figure 1 and Figure 2 The topology network shown can be, but is not limited to, an in-vehicle audio network. When it is an in-vehicle audio network, other devices connected to the common node device 12 through the local port can be, but are not limited to, digital microphones, radios, power amplifiers (PA), and emergency calls (E-Call / Telematics). The main control device connected to the master node device 11 through the local port can be, but is not limited to, a head unit.

[0044] It should be understood that the topology network (such as a car audio network) provided in the embodiment of the present application includes multiple node devices, and multiple node devices communicate serially. In order to ensure that the serial communication of the topology network is orderly and stable, the embodiment of the present application provides a possible implementation method, please refer to the following.

[0045] Assume that any node device is a target node device, which can be a main node device 11 or a common node device 12.

[0046] The target node device is used to feed back a response waiting frame to the upstream port every first preset time period when receiving a control request frame transmitted by the upstream port, until feeding back a response confirmation frame or a response timeout frame to the upstream port.

[0047] It should be understood that by feeding back the response waiting frame to the upstream port, a response timeout between the target node device and the upstream device can be avoided, and misjudgment of the state of the target node device by the upstream device can be avoided.

[0048] In an optional embodiment, the control request frame includes a target address, such as an enumeration request frame or a configuration request frame. After receiving the control request frame, the target node device determines whether the target address therein matches the target node device's own address (dynamic address or static address). If so, the target node device executes the instruction corresponding to the control request frame. If not, the target node device forwards the control request frame through its downstream port, transmits it to the downstream device, and waits for feedback from the downstream device.

[0049] In an optional implementation, the control request frame does not include a target address, such as an initialization request frame, and the target node device executes the instruction corresponding to the control request frame and does not need to forward the control request frame.

[0050] The target node device is also used to determine that the downstream device response has timed out if no response frame is received from the downstream port within a second preset time after sending a control request frame through the downstream port, and to feed back a response timeout frame through the upstream port.

[0051] The response frame is any one of a response waiting frame, a response confirmation frame and a response timeout frame.

[0052] Optionally, the target node device restarts the timing after receiving the response waiting frame fed back by the downstream port. If no response frame fed back by the downstream port is received within the second preset time period, it is determined that the downstream device response has timed out, and a response timeout frame is fed back through the upstream port, thereby completing the status monitoring of the downstream device.

[0053] In one embodiment, when the upstream device receives a response waiting frame fed back by the downstream device, it enters a waiting state. When the upstream device receives a response timeout frame fed back by the downstream device, it continues to forward the response timeout frame upstream, or triggers a control request frame retransmission operation, or triggers a node device detection operation.

[0054] In an optional embodiment, when the target node device receives a response confirmation frame transmitted by the downstream port, if the response confirmation frame contains a target address, such as an enumeration response confirmation frame or a configuration response confirmation frame, and the target address does not match the address of the target node device, it is forwarded through the upstream port until it is transmitted to the node device corresponding to the target address, such as the master node device 11.

[0055] In an optional embodiment, when the target node device receives a response confirmation frame transmitted by a downstream port, if the response confirmation frame contains the dynamic address of the downstream device and does not contain the target address, such as an initialization response confirmation frame, the dynamic address of the target node device is determined based on the dynamic address of the downstream device, and then an initialization response confirmation frame corresponding to the target node device is generated, and the newly generated initialization response confirmation frame is sent through the upstream port.

[0056] In an optional implementation, the response timeout frame may include a source address (e.g., the address of the node device that generates the response timeout frame) and a target address (the address of the master node device 11). When the node device receives the response timeout frame, it determines whether the target address matches. If not, it forwards it through the upstream port until it is transmitted to the master node device 11, so that the master node device 11 can learn the specific device of the response timeout.

[0057] In an optional implementation, the control request frame is an initialization request frame, the response frame is an initialization response frame, the initialization response frame is an initialization response waiting frame or an initialization response confirmation frame, and the initialization response confirmation frame includes the dynamic address of the target node device. The initialization request frame is used to prompt the downstream device to determine its corresponding dynamic address based on the address information of the device connected to its downstream port, and report it through the upstream port. For details, please refer to Figure 3 , Figure 3 A schematic diagram of the initialization process provided for an embodiment of the present application.

[0058] like Figure 3 As shown, the master node device 11 and the common node device 12 are used to send initialization request frames through the downstream ports after being powered on.

[0059] It should be understood that after any node device in the topology network is powered on, it sends a control frame containing initialization information, namely, an initialization request frame, through its downstream port. All node devices on the bus must send an initialization request frame within TSTART time after the system is powered on, and be ready to respond to the initialization response frame, which includes an initialization response wait frame and an initialization response confirmation frame.

[0060] The common node device 12 is also used to determine its own dynamic address according to the feedback result when obtaining the feedback result of the initialization request frame.

[0061] The feedback result includes a downstream port response timeout or a downstream port being unconnected or an initialization response confirmation frame of a downstream device, and the initialization response confirmation frame of the downstream device includes a dynamic address of the downstream device.

[0062] The common node device 12 is also used to generate a corresponding initialization response confirmation frame according to its own dynamic address, and transmit the generated initialization response confirmation frame to the upstream device through the upstream port.

[0063] It should be understood that the ordinary node device 12 uses a layer-by-layer progressive method, and eventually a downstream device of the master node device 11 (such as ordinary node device No. 1 12) feeds back an initialization response confirmation frame to the master node device 11.

[0064] The master node device 11 is further configured to determine the number of node devices in the topology network and the dynamic address of each node device based on the dynamic address of the downstream device after receiving the initialization response confirmation frame of the corresponding downstream device.

[0065] After powering on, each node device directly notifies the downstream device to confirm initialization without waiting for the broadcast message of the master node device 11, so that the total number of common node devices on the bus and their device addresses can be quickly and stably inferred, shortening the initialization time. Because the dynamic address allocation method is adopted, the problem of system initialization failure caused by static address conflicts caused by node addition and deletion can also be solved.

[0066] In an optional implementation, the master node device 11 and the common node device 12 are deployed with a response timer, and the response timer is used for timing.

[0067] In an optional embodiment, the target node device is also used to determine that the downstream port response has timed out if the initialization response frame of the corresponding downstream device is not received within a second preset time after sending the initialization request frame through the downstream port, generate an initialization response confirmation frame, and send the initialization response confirmation frame through the upstream port.

[0068] For example, Figure 3 The ordinary node device No. 3 12 in the waiting time is the second preset time length (TTIMEOUT ), still no initialization response waiting frame or initialization response confirmation frame is received, at this time No. 3 ordinary node device 12 can determine that the downstream port response has timed out, and can determine that its corresponding dynamic address is the first agreed address.

[0069] Optionally, after sending the initialization request frame through the downstream port, the common node device 12 starts its local response timer and starts timing. If no initialization response frame is received when the response timer times out the second preset time, it is determined that the downstream port response has timed out. If within the second preset time, the common node device 12 receives the initialization response waiting frame fed back by the downstream device, it resets its local response timer and restarts timing. If within the second preset time, the common node device 12 receives the initialization response confirmation frame fed back by the downstream device, it can stop timing and obtain the dynamic address of the downstream device based on the initialization response confirmation frame fed back by the downstream device.

[0070] In order to avoid timeouts between downstream devices and upstream devices, the present application embodiment also provides an optional implementation method, please refer to Figure 3 .

[0071] The target node device is also used to receive the initialization request frame transmitted by the upstream device, and then send a first preset time (T DEFER ), feeds back an initialization response waiting frame to the corresponding upstream device until the generated initialization response confirmation frame is transmitted to the upstream device through the upstream port.

[0072] like Figure 3 As shown, after receiving the initialization request frame and before feeding back the initialization response confirmation frame, the ordinary node device No. 2 12 and the ordinary node device No. 1 12 send a first preset time interval (T DEFER ), feeds back an initialization response waiting frame to the corresponding upstream device to prevent the upstream device from determining that its downstream port response has timed out.

[0073] Optionally, after the node device receives the initialization request frame from its upstream port, the local response timer is started. The response timer reaches the first preset response timer duration (T DEFER ), and the node device does not receive an initialization response confirmation frame from the downstream port, the node device sends an initialization response wait frame from the upstream port.

[0074] In an optional embodiment, the control request frame is an enumeration request frame, the response frame is an enumeration response frame, the enumeration response frame is any one of an enumeration response waiting frame, an enumeration response confirmation frame and an enumeration response timeout frame, the enumeration request frame includes a target address and a source address, the enumeration response timeout frame includes a target address and a source address, and the enumeration response confirmation frame includes a target address and a source address. The target address in the enumeration request frame is the address (dynamic address or static address) of any common node device 12, and the source address in the enumeration request frame is the address (dynamic address or static address) of the master node device. The target address in the enumeration response confirmation frame is the source address in the enumeration request frame, and the source address in the enumeration response confirmation frame is the target address in the enumeration request frame. The target address in the enumeration response timeout frame is the source address in the enumeration request frame, and the source address in the enumeration response timeout frame is the address of the node device that determines the response timeout of the downstream device.

[0075] Optionally, the enumeration request frame is used to enable the node device to feed back a corresponding device descriptor to the master node device 11 .

[0076] In an optional implementation, after the initialization operation is completed, the master node device 11 sequentially initiates an enumeration request operation to each common node device 12 or backup master node device, i.e., sends an enumeration request frame. Each enumeration request frame contains a dynamic address or a static address of a common node device 12, so each enumeration request operation is only for one node device.

[0077] When the target node device receives an enumeration request frame from the upstream port and the dynamic address matches, it immediately sends an enumeration response confirmation frame; otherwise, it forwards the enumeration request frame to the downstream port and starts the waiting timer and timeout timer. DEFER When the timeout timer reaches T TIMEOUT -, the target node device sends an enumeration response timeout frame to the upstream port.

[0078] When the target node device receives the enumeration response confirmation frame from the downstream port, it determines whether the dynamic address matches. If it does not match, it is forwarded through the upstream port so that the master node device 11 can obtain the enumeration response confirmation frame of each ordinary node device 12. It should be noted that the enumeration response confirmation frame also contains the source address and the target address. The enumeration response confirmation frame includes the device descriptor of the corresponding node. It should be understood that the device descriptor includes the port attributes of the node device, such as the port number, port type, and port characteristics, etc., which can be used for subsequent virtual channel configuration.

[0079] Please refer to Figure 4 and Figure 5 , Figure 4 A schematic diagram of the enumeration process provided in the embodiment of the present application, Figure 5 Another schematic diagram of the enumeration process provided in the embodiment of the present application. Figure 4 and Figure 5 As shown, in an optional implementation, the target node device is used to feed back an enumeration response wait frame to the corresponding upstream device every first preset time period after receiving the enumeration request frame transmitted by the upstream device, until the generated enumeration response confirmation frame is transmitted to the upstream device through the upstream port.

[0080] When receiving the enumeration request frame with the target address = 1, the ordinary node device No. 1 12 and the ordinary node device No. 2 12 send a request to the target address of the enumeration request frame ... at a first preset time length (T DEFER ) will feed back an enumeration response wait frame to the upstream port to prevent the upstream device from mistakenly believing that its response has timed out.

[0081] In an optional embodiment, the target node device is also used to determine that the downstream port response has timed out if the enumeration response frame of the corresponding downstream device is not received within a second preset time after sending an enumeration request frame through the downstream port, generate an enumeration response timeout frame, and send the enumeration response timeout frame through the upstream port.

[0082] Please continue to refer to Figure 4 and Figure 5 , assuming that the target node device is ordinary node device No. 2 12, after ordinary node device No. 2 forwards the enumeration request frame through the downstream port, it starts its local response timer and starts timing. If the response timer exceeds the second preset time (T TIMEOUT ), if no enumeration response frame is received, it is determined that the downstream port response has timed out. An enumeration response timeout frame can be generated, in which the source address is the address of the ordinary node device No. 2 12 = 2, and the destination address = 0. When the ordinary node device No. 3 12 receives the enumeration response timeout frame, it forwards it. When the master node device 11 receives the enumeration response timeout frame, it can be determined that the ordinary node device No. 1 has timed out.

[0083] If within the second preset time length, the ordinary node device 12 No. 2 receives the enumeration response waiting frame fed back by the downstream device, it resets its local response timer and restarts the timing. If within the second preset time length, the ordinary node device 12 receives the enumeration response confirmation frame fed back by the downstream device, it can stop timing and forward the enumeration response confirmation frame fed back by the downstream device through its upstream port.

[0084] After the enumeration operation is completed, the master node device 11 accesses the Auto Audio Network Configuration Data (AANCD) in the common node device 12 through the data transmission operation of the control frame. Each node device contains an Auto Audio Network Configuration Data (AANCD) that meets the specified requirements.

[0085] In an optional implementation, the control request frame is an AANCD request frame, the response frame is an AANCD response frame, the AANCD response frame is any one of an AANCD response waiting frame, an AANCD response confirmation frame, and an AANCD response timeout frame, the AANCD request frame includes a target address and a source address, the AANCD response timeout frame includes a target address and a source address, and the AANCD response confirmation frame includes a target address and a source address. The target address in the AANCD request frame is the address (dynamic address or static address) of any common node device 12, and the source address in the AANCD request frame is the address (dynamic address or static address) of the master node device. The target address in the AANCD response confirmation frame is the source address in the AANCD request frame, and the source address in the AANCD response confirmation frame is the target address in the AANCD request frame. The target address in the AANCD response timeout frame is the source address in the AANCD request frame, and the source address in the AANCD response timeout frame is the address of the node device that determines the timeout of the downstream device response.

[0086] Optionally, the AANCD request frame is used to enable the master node device 11 to obtain the AANCD offset address and AANCD configuration data of each node device.

[0087] In an optional implementation, after the enumeration operation is completed, the master node device 11 initiates an AANCD request operation to each common node device 12 or backup master node device in turn, that is, sends an AANCD request frame. Each AANCD request frame contains a dynamic address or a static address of a common node device 12, so each AANCD request operation is only for one node device.

[0088] When the target node device receives an AANCD request frame from the upstream port and the dynamic address matches, it sends an AANCD response confirmation frame; otherwise, it forwards the AANCD request frame to the downstream port and starts the waiting timer and timeout timer. DEFER When the timeout timer reaches T TIMEOUT When the target node device sends an AANCD response timeout frame to the upstream port.

[0089] When the target node device receives the AANCD response confirmation frame from the downstream port, it determines whether the dynamic address matches. If not, it is forwarded through the upstream port so that the master node device 11 can obtain the AANCD response confirmation frame of each ordinary node device 12. It should be noted that the AANCD response confirmation frame also includes the source address and the target address.

[0090] Optionally, the AANCD response confirmation frame includes an AANCD offset address and AANCD configuration data.

[0091] Please refer to Figure 6 and Figure 7 , Figure 6 A schematic diagram of the AANCD access process provided in an embodiment of the present application is provided. Figure 7 Another schematic diagram of the AANCD access process provided in the embodiment of the present application. Figure 6 and Figure 7 As shown, in an optional implementation, the target node device is used to feed back an AANCD response wait frame to the corresponding upstream device every first preset time period after receiving the AANCD request frame transmitted by the upstream device, until the generated AANCD response confirmation frame is transmitted to the upstream device through the upstream port.

[0092] When receiving the AANCD request frame with the target address = 1, the ordinary node device No. 1 12 and the ordinary node device No. 2 12 send a request to the target address of the AANCD request frame every first preset time length (T DEFER ) will feed back the AANCD response waiting frame to the upstream port to prevent the upstream device from mistakenly believing that its response has timed out.

[0093] In an optional embodiment, the target node device is also used to determine that the downstream port response has timed out if the AANCD response frame from the corresponding downstream device is not received within a second preset time after sending the AANCD request frame through the downstream port, generate an AANCD response timeout frame, and send the AANCD response timeout frame through the upstream port.

[0094] Please continue to refer to Figure 6 and Figure 7 , assuming that the target node device is the ordinary node device No. 2 12, after the ordinary node device No. 2 forwards the AANCD request frame through the downstream port, it starts its local response timer and starts timing. If the response timer exceeds the second preset time (T TIMEOUT), if no AANCD response frame is received, it is determined that the downstream port response has timed out. An AANCD response timeout frame can be generated, in which the source address is the address of ordinary node device No. 2 12 = 2, and the destination address = 0. When ordinary node device No. 3 12 receives the AANCD response timeout frame, it forwards it. When the master node device 11 receives the AANCD response timeout frame, it can be determined that ordinary node device No. 1 has timed out.

[0095] If within the second preset time length, the ordinary node device 12 No. 2 receives the AANCD response waiting frame fed back by the downstream device, it resets its local response timer and restarts the timing. If within the second preset time length, the ordinary node device 12 receives the AANCD response confirmation frame fed back by the downstream device, it can stop timing and forward the AANCD response confirmation frame fed back by the downstream device through its upstream port.

[0096] Please refer to Table 1 and Table 2 below. Table 1 below shows a possible AANCD request frame structure.

[0097]

[0098] Table 1

[0099] The following Table 2 is a structural description of the AANCD request frame shown in Table 1.

[0100]

[0101]

[0102] Table 2

[0103] In an optional implementation, the control request frame is a control request frame, the response frame is a configuration response frame, the configuration response frame is any one of a configuration response waiting frame, a configuration response confirmation frame, and a configuration response timeout frame, the configuration request frame includes a target address and a source address, the configuration response timeout frame includes a target address and a source address, and the configuration response confirmation frame includes a target address and a source address. The target address in the configuration request frame is the address (dynamic address or static address) of any common node device 12, and the source address in the configuration request frame is the address (dynamic address or static address) of the master node device. The target address in the configuration response confirmation frame is the source address in the configuration request frame, and the source address in the configuration response confirmation frame is the target address in the configuration request frame. The target address in the configuration response timeout frame is the source address in the configuration request frame, and the source address in the configuration response timeout frame is the address of the node device that determines the response timeout of the downstream device.

[0104] Optionally, the configuration request frame is used to enable each node device to complete the virtual channel configuration.

[0105] In an optional implementation, after the enumeration operation is completed, the master node device 11 sequentially initiates a configuration request operation to each common node device 12 or backup master node device, that is, sends a configuration request frame. Each configuration request frame contains a dynamic address or a static address of a common node device 12, so each configuration request operation is only for one node device.

[0106] Optionally, the master node device 11 sends a configuration request frame through its downstream port, where the configuration request frame includes address information of the node device to be configured and a virtual channel descriptor of at least one node device to be configured, and the node device to be configured is any common node device 12 .

[0107] Optionally, the address information of the node device to be configured may be a dynamic address determined during the initialization process, or may be a static address, which is not limited here.

[0108] When the ordinary node device 12 receives the configuration request frame transmitted by the main node device 11, it parses the target address information therein, that is, the address information of the node device to be configured. If the target address information matches its own address, it performs configuration based on the configuration request frame. If they do not match, the configuration request frame is forwarded to the downstream device through the downstream port.

[0109] Optionally, the master node device 11 generates a corresponding virtual channel configuration table based on the virtual channel descriptor corresponding to the node device to be configured, and transmits the virtual channel configuration table to the node device to be configured via a configuration request frame. The virtual channel configuration table includes at least one virtual channel descriptor corresponding to the node device to be configured.

[0110] Please refer to Table 3, which is a structural description of a virtual channel configuration table provided in an embodiment of the present application.

[0111]

[0112] Table 3

[0113] The node device to be configured is further configured to set the virtual channel configuration table stored therein based on the virtual channel descriptor in the configuration request frame after receiving the configuration request frame.

[0114] Optionally, the virtual channel configuration table in the configuration request frame is obtained and stored as its own virtual channel configuration table. Alternatively, the virtual channel descriptor in the configuration request frame is parsed and the stored virtual channel configuration table is updated. The virtual channel configuration table is used to distribute and / or merge the data obtained by the data node.

[0115] Optionally, during the configuration process, when the target node device receives a configuration request frame from the upstream port and the dynamic address matches, it immediately sends a configuration response confirmation frame; otherwise, it forwards the configuration request frame to the downstream port and starts the waiting timer and timeout timer. When the waiting timer reaches T DEFER When the timeout timer reaches T TIMEOUT When the target node device sends a configuration response timeout frame to the upstream port.

[0116] When the target node device receives the configuration response confirmation frame from the downstream port, it determines whether the dynamic address matches. If not, it is forwarded through the upstream port so that the master node device 11 can obtain the configuration response confirmation frame of each ordinary node device 12. It should be noted that the configuration response confirmation frame also includes the source address and the target address.

[0117] Please refer to Figure 8 and Fig. 9 , Figure 8 A schematic diagram of the configuration process provided in the embodiment of the present application is provided. Fig. 9 Another schematic diagram of the configuration process provided in the embodiment of the present application. Figure 8 and Fig. 9 As shown, in an optional implementation, the target node device is used to feed back a configuration response waiting frame to the corresponding upstream device every first preset time period after receiving the configuration request frame transmitted by the upstream device, until the generated configuration response confirmation frame is transmitted to the upstream device through the upstream port.

[0118] When receiving the configuration request frame with the target address = 1, the ordinary node device No. 1 12 and the ordinary node device No. 2 12 send a request to the client device 100 at a first preset time interval (T DEFER ) will feed back a configuration response wait frame to the upstream port to prevent the upstream device from mistakenly believing that its response has timed out.

[0119] In an optional implementation, the target node device is also used to determine that the downstream port response has timed out if the configuration response frame of the corresponding downstream device is not received within a second preset time after sending a configuration request frame through the downstream port, generate a configuration response timeout frame, and send the configuration response timeout frame through the upstream port.

[0120] Please continue to refer to Figure 8 and Fig. 9 , assuming that the target node device is ordinary node device No. 2 12, after ordinary node device No. 2 forwards the configuration request frame through the downstream port, it starts its local response timer and starts timing. If the response timer exceeds the second preset time (T TIMEOUT), if no configuration response frame is received, it is determined that the downstream port response has timed out. A configuration response timeout frame can be generated, in which the source address is the address of ordinary node device No. 2 12 = 2, and the destination address = 0. When ordinary node device No. 3 12 receives the configuration response timeout frame, it forwards it. When the master node device 11 receives the configuration response timeout frame, it can be determined that ordinary node device No. 1 has timed out.

[0121] If within the second preset time length, the ordinary node device 12 No. 2 receives the configuration response waiting frame fed back by the downstream device, it resets its local response timer and restarts the timing. If within the second preset time length, the ordinary node device 12 receives the configuration response confirmation frame fed back by the downstream device, it can stop timing and forward the configuration response confirmation frame fed back by the downstream device through its upstream port.

[0122] To summarize, an embodiment of the present application provides a topology network, including a master node device and at least one ordinary node device, which are connected in sequence; the target node device is used to, upon receiving a control request frame transmitted by an upstream port, feed back a response waiting frame to the upstream port at intervals of a first preset time period, until a response confirmation frame or a response timeout frame is fed back to the upstream port, so as to avoid the upstream device from mistakenly judging that the response of the target node device has timed out; the target node device is also used to, after sending a control request frame through a downstream port, determine that the response of the downstream device has timed out if no response frame is received from the downstream port within a second preset time period, and feed back a response timeout frame through the upstream port to accurately obtain the response status of the downstream device.

[0123] The present application embodiment also provides a topology network communication processing method, which can be applied to but not limited to the above topology network. Fig.10 , Fig.10 A schematic diagram of a flow chart of a topology network communication processing method provided in an embodiment of the present application. Specifically, the topology network communication processing method includes: S101 and S102, which are described in detail as follows.

[0124] S101, when receiving a control request frame transmitted by an upstream port, the target node device feeds back a response waiting frame to the upstream port every first preset time period until feeding back a response confirmation frame or a response timeout frame to the upstream port.

[0125] The target node device is any common node device.

[0126] S102, after the target node device sends a control request frame through the downstream port, if it still does not receive a response frame fed back by the downstream port within a second preset time period, it determines that the downstream device response has timed out, and feeds back a response timeout frame through the upstream port.

[0127] The response frame is any one of a response waiting frame, a response confirmation frame and a response timeout frame.

[0128] It should be noted that the topology network communication processing method provided in this embodiment can perform the functions and purposes shown in the above topology network embodiment to achieve the corresponding technical effects. For the sake of brief description, for parts not mentioned in this embodiment, reference can be made to the corresponding contents in the above embodiments.

[0129] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

[0130] It will be apparent to those skilled in the art that the present application is not limited to the details of the exemplary embodiments described above, and that the present application can be implemented in other specific forms without departing from the spirit or essential features of the present application. Therefore, the embodiments should be considered exemplary and non-limiting in all respects, and the scope of the present application is defined by the appended claims rather than the above description, and it is intended that all changes falling within the meaning and scope of the equivalent elements of the claims be included in the present application. Any reference numeral in a claim should not be considered as limiting the claim to which it relates.

Claims

1. A topological network, characterized in that: The topology network includes a master node device and at least one common node device, and the master node device and the at least one common node device are connected in sequence; The target node device is used for feeding back a response waiting frame to the upstream port every first preset time period when receiving a control request frame transmitted by the upstream port, until feeding back a response confirmation frame or a response timeout frame to the upstream port; Wherein, the target node device is any common node device; The target node device is further configured to determine that the downstream device response has timed out if no response frame fed back by the downstream port is received within a second preset time interval after sending the control request frame through the downstream port, and feed back a response timeout frame through the upstream port; The response frame is any one of a response waiting frame, a response confirmation frame and a response timeout frame.

2. The topological network according to claim 1, characterized in that: The control request frame is an initialization request frame, the response frame is an initialization response frame, the initialization response frame is an initialization response waiting frame or an initialization response confirmation frame, and the initialization response confirmation frame includes the dynamic address of the target node device; The target node device is also used to determine that the downstream port response has timed out if the corresponding downstream device's initialization response frame is not received within a second preset time after sending an initialization request frame through the downstream port, generate the initialization response confirmation frame, and send the initialization response confirmation frame through the upstream port.

3. The topological network according to claim 2, characterized in that: The target node device is also used to feed back an initialization response waiting frame to the corresponding upstream device every first preset time after receiving the initialization request frame transmitted by the upstream device, until the generated initialization response confirmation frame is transmitted to the upstream device through the upstream port.

4. The topological network according to claim 1, characterized in that: The control request frame is an enumeration request frame, the response frame is an enumeration response frame, the enumeration response frame is any one of an enumeration response wait frame, an enumeration response confirmation frame and an enumeration response timeout frame, the enumeration request frame includes a target address and a source address, the enumeration response timeout frame includes a target address and a source address, and the enumeration response confirmation frame includes a target address and a source address; The target node device is used to feed back an enumeration response waiting frame to the corresponding upstream device every first preset time after receiving the enumeration request frame transmitted by the upstream device, until the generated enumeration response confirmation frame is transmitted to the upstream device through the upstream port.

5. The topological network according to claim 4, characterized in that: The target node device is also used to determine that the downstream port response has timed out if the enumeration response frame of the corresponding downstream device is not received within a second preset time after sending the enumeration request frame through the downstream port, generate the enumeration response timeout frame, and send the enumeration response timeout frame through the upstream port.

6. The topological network according to claim 1, characterized in that: The control request frame is an AANCD request frame, the response frame is an AANCD response frame, the AANCD response frame is any one of an AANCD response waiting frame, an AANCD response confirmation frame and an AANCD response timeout frame, the AANCD request frame includes a target address and a source address, the AANCD response timeout frame includes a target address and a source address, and the AANCD response confirmation frame includes a target address and a source address; The target node device is used to feed back an AANCD response waiting frame to the corresponding upstream device every first preset time after receiving the AANCD request frame transmitted by the upstream device, until the generated AANCD response confirmation frame is transmitted to the upstream device through the upstream port.

7. The topological network according to claim 6, characterized in that: The target node device is also used to determine that the downstream port response has timed out if the AANCD response frame of the corresponding downstream device is not received within a second preset time after sending the AANCD request frame through the downstream port, generate the AANCD response timeout frame, and send the AANCD response timeout frame through the upstream port.

8. The topological network according to claim 1, characterized in that: The control request frame is a configuration request frame, the response frame is a configuration response frame, the configuration response frame is any one of a configuration response waiting frame, a configuration response confirmation frame and a configuration response timeout frame, the configuration request frame includes a target address and a source address, the configuration response timeout frame includes a target address and a source address, and the configuration response confirmation frame includes a target address and a source address; The target node device is used to feed back a configuration response waiting frame to the corresponding upstream device every first preset time after receiving the configuration request frame transmitted by the upstream device, until the generated configuration response confirmation frame is transmitted to the upstream device through the upstream port.

9. The topological network according to claim 8, characterized in that: The target node device is also used to determine that the downstream port response has timed out if the configuration response frame of the corresponding downstream device is not received within a second preset time after sending the configuration request frame through the downstream port, generate the configuration response timeout frame, and send the configuration response timeout frame through the upstream port.

10. A topology network communication processing method, characterized in that: Applied to a topology network, the topology network includes a master node device and at least one common node device, the master node device and the at least one common node device are connected in sequence; When receiving the control request frame transmitted by the upstream port, the target node device feeds back a response waiting frame to the upstream port every first preset time period until feeding back a response confirmation frame or a response timeout frame to the upstream port; Wherein, the target node device is any common node device; After the target node device sends the control request frame through the downstream port, if it still does not receive a response frame fed back by the downstream port within a second preset time, it determines that the downstream device response has timed out, and feeds back a response timeout frame through the upstream port; The response frame is any one of a response waiting frame, a response confirmation frame and a response timeout frame.

Images