CN117176498A - Topology network and communication processing method - Google Patents
Topology network and communication processing method Download PDFInfo
- Publication number
- CN117176498A CN117176498A CN202211287852.4A CN202211287852A CN117176498A CN 117176498 A CN117176498 A CN 117176498A CN 202211287852 A CN202211287852 A CN 202211287852A CN 117176498 A CN117176498 A CN 117176498A
- Authority
- CN
- China
- Prior art keywords
- frame
- response
- node device
- upstream
- port
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000004891 communication Methods 0.000 title claims abstract description 20
- 238000003672 processing method Methods 0.000 title claims abstract description 13
- 230000004044 response Effects 0.000 claims abstract description 316
- 238000011144 upstream manufacturing Methods 0.000 claims abstract description 127
- 238000012790 confirmation Methods 0.000 claims description 28
- 238000000034 method Methods 0.000 description 22
- 230000008569 process Effects 0.000 description 19
- 238000010586 diagram Methods 0.000 description 18
- 230000003068 static effect Effects 0.000 description 12
- 230000009471 action Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 208000033748 Device issues Diseases 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/42—Loop networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5046—Resolving address allocation conflicts; Testing of addresses
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Small-Scale Networks (AREA)
Abstract
The application provides a topology network and a communication processing method, comprising main node equipment and at least 1 common node equipment, wherein the main node equipment and the at least 1 common node equipment are connected in sequence; the target node device is configured to, when receiving a control request frame transmitted by the upstream port, feed back a response waiting frame to the upstream port every a first preset duration until the upstream port feeds back a response acknowledgement frame or a response timeout frame, so as to avoid that the upstream device misjudges that the response of the target node device is timeout, and after sending the control request frame through the downstream port, if the response frame fed back by the downstream port is still not received after a second preset duration is spaced, determine that the response of the downstream device is timeout, and feed back the response timeout frame through the upstream port, so as to accurately obtain the response state of the downstream device.
Description
Technical Field
The present application relates to the field of communications, and in particular, to a topology network and a communication processing method.
Background
With the development of society, the variety of electronic devices is becoming more and more abundant. In many scenarios, a single electronic device will not meet the needs of a user, and multiple electronic devices need to be combined into a topology network, and under the coordination of the topology network, the multiple electronic devices work cooperatively. Taking a car audio network (AAN, automotive Audio Network) in a topology network as an example, the car audio network is a serial communication network for interconnection between car audio devices, and a topology network of car electronics such as a tandem car jack Unit (Head Unit), a digital microphone, a radio, a Power Amplifier (PA), and an emergency Call/technology module.
The vehicle-mounted audio network consists of a plurality of nodes, serial communication is carried out among the plurality of nodes, and how to ensure orderly and stable serial communication becomes a problem which is continuously focused by the person skilled in the art.
Disclosure of Invention
The present application aims to provide a topology network and a communication processing method, which at least partially improve the above problems.
In order to achieve the above object, the technical scheme adopted by the embodiment of the application is as follows:
in a first aspect, an embodiment of the present application provides a topology network, where the topology network includes a master node device and at least 1 common node device, where the master node device and the at least 1 common node device are sequentially connected;
the target node device is used for feeding back a response waiting frame to the upstream port every a first preset duration 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 one common node device;
the target node device is further configured to determine that the response of the downstream device is overtime and feedback a response overtime frame through the upstream port if the response frame fed back by the downstream port is still not received after the control request frame is sent through the downstream port for a second preset duration;
Wherein, the response frame is any one of a response waiting frame, a response confirmation frame and a response timeout frame.
In a second aspect, an embodiment of the present application provides a topology network communication processing method, which is applied to a topology network, where the topology network includes a master node device and at least 1 common node device, and the master node device and the at least 1 common node device are sequentially connected;
when receiving a control request frame transmitted by an upstream port, the target node equipment feeds back a response waiting frame to the upstream port every a first preset duration until a response confirmation frame or a response timeout frame is fed back to the upstream port;
wherein the target node device is any one common node device;
after the target node device sends a control request frame through the downstream port, if a response frame fed back by the downstream port is still not received for a second preset time interval, determining that the response of the downstream device is overtime, and feeding back the response overtime frame through the upstream port;
wherein, the response frame is any one of a response waiting frame, a response confirmation frame and a response timeout frame.
Compared with the prior art, the topology network and the communication processing method provided by the embodiment of the application comprise main node equipment and at least 1 common node equipment, wherein the main node equipment and the at least 1 common node equipment are connected in sequence; the target node device is configured to, when receiving a control request frame transmitted by the upstream port, feed back a response waiting frame to the upstream port every a first preset duration until the upstream port feeds back a response acknowledgement frame or a response timeout frame, so as to avoid that the upstream device misjudges that the response of the target node device is timeout, and after sending the control request frame through the downstream port, if the response frame fed back by the downstream port is still not received after a second preset duration is spaced, determine that the response of the downstream device is timeout, and feed back the response timeout frame through the upstream port, so as to accurately obtain the response state of the downstream device.
In order to make the above objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic structural diagram of a serial topology network according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a ring topology network according to an embodiment of the present application;
FIG. 3 is a schematic diagram of an initialization process according to an embodiment of the present application;
FIG. 4 is a schematic diagram of an enumeration process according to an embodiment of the present application;
FIG. 5 is another schematic diagram of an enumeration process according to an embodiment of the present application;
FIG. 6 is a schematic diagram of an AANCD access process according to an embodiment of the present application;
FIG. 7 is another schematic diagram of an AANCD access process according to an embodiment of the present application;
FIG. 8 is a schematic diagram of a configuration process according to an embodiment of the present application;
FIG. 9 is another schematic diagram of a configuration process according to an embodiment of the present application;
fig. 10 is a flow chart of a topology network communication processing method according to an embodiment of the present application.
In the figure: 11-a master node device; 12-ordinary node device.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments of the present application. The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the application, as presented in the figures, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only to distinguish the description, and are not to be construed as indicating or implying relative importance.
It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
In the description of the present application, it should be noted that, directions or positional relationships indicated by terms such as "upper", "lower", "inner", "outer", etc., are directions or positional relationships based on those shown in the drawings, or those conventionally put in use in the application, are merely for convenience of description and simplification of the description, and do not indicate or imply that the apparatus or elements referred to must have a specific orientation, be constructed and operated in a specific orientation, and thus should not be construed as limiting the present application.
In the description of the present application, it should also be noted that, unless explicitly specified and limited otherwise, the terms "disposed", "connected" and "connected" are to be construed broadly, and may be, for example, fixedly connected, detachably connected or integrally connected; can be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium, and can be communication between two elements. The specific meaning of the above terms in the present application will be understood in specific cases by those of ordinary skill in the art.
Some embodiments of the present application are described in detail below with reference to the accompanying drawings. The following embodiments and features of the embodiments may be combined with each other without conflict.
In order to overcome the above problems, embodiments of the present application provide a topology network. Referring to fig. 1 and fig. 2, fig. 1 is a schematic structural diagram of a serial topology network according to an embodiment of the present application, and fig. 2 is a schematic structural diagram of a ring topology network according to an embodiment of the present application.
As shown in fig. 1 and 2, the topology network includes a master node device 11 and at least 1 common node device 12, and the master node device 11 and the at least 1 common node device 12 are sequentially connected, specifically, may be connected through a differential bus.
Optionally, as shown in fig. 1, the topology network is a serial topology network, the downstream port of the master node device 11 is connected to the upstream port of the first common node device 12 (i.e. the 1 st common node device in fig. 1), the upstream port of the i-th common node device 12 is connected to the downstream port of the i-1 st common node device 12, the downstream port of the n-th common node device 12 (i.e. the 3 rd common node device in fig. 1) is suspended, and i is equal to or greater than 2 and equal to n, where n is the number of the common node devices.
Alternatively, as shown in fig. 2, the topology network is a ring topology network, the downstream port of the master node device 11 is connected to the upstream port of the first common node device 12 (i.e., the No. 1 common node device in fig. 2), the upstream port of the i-th common node device 12 is connected to the downstream port of the i-1-th common node device 12, the downstream port of the n-th common node device 12 (i.e., the No. 3 common node device in fig. 2) is connected to the upstream port of the master node device 11, and i.ltoreq.n is 2.ltoreq.n, where n is the number of common node devices.
It should be understood that, in the present application, the downstream device is a device connected to a downstream port of a node, and the upstream device is a device connected to an upstream port of the node. For example, the No. 1 ordinary node apparatus 12 is an upstream apparatus of the No. 2 ordinary node apparatus 12.
Note that n=3 is taken as an example in fig. 1 and 2, but this is not a limitation.
It should be understood that the topology network shown in fig. 1 and 2 may be, but is not limited to, a car audio network, and when it is a car audio network, other devices to which the general node device 12 is connected through a local port may be, but is not limited to, a digital microphone, a radio, a Power Amplifier (PA), and an emergency Call (E-Call/technology). The master device to which the master node device 11 is connected through the local port may be, but not limited to, a Head Unit (Head Unit).
It should be understood that the topology network (e.g., the vehicle audio network) provided in the embodiment of the present application includes a plurality of node devices, and serial communication is performed between the plurality of node devices. In order to ensure orderly and stable serial communication of the topology network, the embodiment of the application provides a possible implementation manner, please refer to the following.
Any node device is assumed to be a target node device, and may be the master node device 11 or the normal node device 12.
And the target node equipment is used for feeding back a response waiting frame to the upstream port every a first preset duration when receiving the control request frame transmitted by the upstream port, until feeding back a response confirmation frame or a response timeout frame to the upstream port.
It should be understood that by feeding back a response waiting frame to the upstream port, the situation that a response timeout occurs between the target node device and the upstream device is avoided, and misjudgment of the upstream device on the state of the target node device is avoided.
In an alternative implementation manner, the control request frame includes a target address, for example, an enumeration request frame or a configuration request frame, after receiving the control request frame, the target node device determines whether the target address is matched with the self address (dynamic address or static address) of the target node device, if so, the target node device executes an instruction corresponding to the control request frame, if not, the target node device forwards the control request frame through a downstream port thereof, transmits the control request frame to the downstream device, and waits for the downstream device to feed back.
In an alternative embodiment, the control request frame does not include a target address, for example, is 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.
The target node device is further configured to determine that the response of the downstream device is overtime after the control request frame is sent through the downstream port, if the response frame fed back by the downstream port is still not received for a second preset duration, and feed back the response overtime frame through the upstream port.
Wherein the response frame is any one of a response waiting frame, a response confirmation frame and a response timeout frame.
Optionally, the target node device restarts timing after receiving the response waiting frame fed back by the downstream port, if the response frame fed back by the downstream port is not received for the second preset duration, determining that the response of the downstream device is overtime, and feeding back the response overtime frame through the upstream port, thereby completing the state monitoring of the downstream device.
In one embodiment, when the upstream device receives a response waiting frame fed back by the downstream device, the upstream device enters a waiting state, and when the upstream device receives a response timeout frame fed back by the downstream device, the upstream device continues to forward the response timeout frame, or triggers a control request frame retransmission operation, or triggers a node device detection operation.
In an alternative embodiment, when the target node device receives the response acknowledgement frame transmitted by the downstream port, if the response acknowledgement frame includes a target address, for example, an enumeration response acknowledgement frame or a configuration response acknowledgement frame, and the target address does not match the address of the target node device, forwarding is performed through the upstream port until the response acknowledgement frame is transmitted to the node device corresponding to the target address, for example, the master node device 11.
In an alternative embodiment, when the target node device receives the response acknowledgement frame transmitted by the downstream port, if the response acknowledgement frame includes the dynamic address of the downstream device and does not include the target address, for example, the initialization response acknowledgement frame, the dynamic address of the target node device is determined based on the dynamic address of the downstream device, so as to generate an initialization response acknowledgement frame corresponding to the target node device, and the newly generated initialization response acknowledgement frame is sent through the upstream port.
In an alternative embodiment, the response timeout frame may include a source address (e.g., the address of the node device that generated the response timeout frame) and a destination address (e.g., the address of the master node device 11). When the node device receives the response timeout frame, judging whether the target addresses are matched or not, if not, forwarding through the upstream port until the target addresses are transmitted to the master node device 11, so that the master node device 11 can acquire the specific device with the response timeout.
In an alternative embodiment, 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 acknowledgement frame, and the initialization response acknowledgement frame contains a dynamic address of the target node device. The initialization request frame is used for prompting the downstream equipment to determine the corresponding dynamic address based on the address information of the equipment connected with the downstream port, and reporting the dynamic address through the upstream port. Specifically, referring to fig. 3, fig. 3 is a schematic diagram illustrating an initialization process according to an embodiment of the application.
As shown in fig. 3, the master node device 11 and the normal node device 12 are configured to transmit an initialization request frame through a downstream port after power-up.
It should be appreciated that after any node device in the topology network is powered up, a control frame containing initialization information, i.e. an initialization request frame, is sent through its downstream port. All node devices on the bus must issue an initialization request frame within TSTART time after the system is powered up and be ready to respond to an initialization response frame including an initialization response wait frame and an initialization response acknowledge frame.
The common node device 12 is further configured to determine its own dynamic address according to the feedback result when the feedback result of the initialization request frame is obtained.
The feedback result comprises a response timeout of the downstream port or an initialization response confirmation frame of the downstream port or the downstream device, wherein the initialization response confirmation frame of the downstream device comprises a dynamic address of the downstream device.
The generic node device 12 is further configured to generate a corresponding initialization response acknowledgement frame according to its own dynamic address, and transmit the generated initialization response acknowledgement frame to the upstream device through the upstream port.
It should be understood that the normal node device 12 finally has the downstream device (e.g., the normal node device 1) of the master node device 11 feeding back the initialization response acknowledgement frame to the master node device 11 in a layer-by-layer progressive manner.
The master node device 11 is further configured to determine, after receiving the initialization response acknowledgement frame of the corresponding downstream device, the number of node devices in the topology network and the dynamic addresses of the respective node devices based on the dynamic addresses of the downstream devices.
After each node device is powered on, the downstream device is directly informed to carry out initialization confirmation, and the broadcast message of the main node device 11 does not need to be waited, so that the total number of common node devices and the device addresses of the common node devices on the bus can be rapidly and stably inferred, and the initialization time is shortened. Because the dynamic address allocation mode is adopted, the problem of system initialization failure caused by static address conflict due to node addition and deletion can be solved.
In an alternative embodiment, the master node device 11 and the regular node device 12 are deployed with a response timer for timing.
In an optional implementation manner, the target node device is further configured to, after sending the initialization request frame through the downstream port, determine that the downstream port response is timeout if the initialization response frame of the corresponding downstream device is not received beyond the second preset duration, generate an initialization response acknowledgement frame, and send the initialization response acknowledgement frame through the upstream port.
For example, the common node apparatus No. 3 12 in fig. 3 waits for the second preset time period (T TIMEOUT ) After that, the initialization response waiting frame or the initialization response confirmation frame is not received yet, and at this time, the No. 3 ordinary node device 12 may determine that the downstream port response is overtime, and may determine that the dynamic address corresponding to the downstream port response is the first contracted address.
Optionally, after sending the initialization request frame through the downstream port, the common node device 12 starts its local response timer to start counting, and if any initialization response frame is not received when the response timer counts more than the second preset duration, determines that the response of the downstream port is overtime. If the normal node device 12 receives the initialization response waiting frame fed back by the downstream device within the second preset duration, resets its local response timer, and restarts timing. If the normal node device 12 receives the initialization response confirmation frame fed back by the downstream device within the second preset duration, the timing may be stopped, and the dynamic address of the downstream device may be obtained based on the initialization response confirmation frame fed back by the downstream device.
In order to avoid the time-out of the downstream device and the upstream device, an alternative implementation manner is further provided in the embodiment of the present application, and refer to fig. 3 specifically.
The target node device is further configured to, after receiving the initialization request frame transmitted by the upstream device, perform a first predetermined period (T DEFER ) And feeding 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.
As shown in fig. 3, the No. 2 ordinary node device 12 and the No. 1 ordinary node device 12, before receiving the initialization request frame and without feeding back the initialization response acknowledgement frame, every first preset time period (T DEFER ) Feeding back an initialization response waiting frame to the corresponding upstream equipment to avoid the upstream equipment to identify the downstream end thereofThe mouth response times out.
Optionally, after the node device receives the initialization request frame from its upstream port, a local response timer is started. The response timer reaches a first preset time period (T DEFER ) And the node device does not receive the initialization response acknowledgement frame from the downstream port, and the node device issues an initialization response wait frame from the upstream port.
In an alternative implementation, 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 destination address in the enumeration request frame is the address (dynamic address or static address) of any one of the common node devices 12, and the source address in the enumeration request frame is the address (dynamic address or static address) of the master node device. The destination address in the enumeration response confirm frame is the source address in the enumeration request frame, and the source address in the enumeration response confirm frame is the destination address in the enumeration request frame. The destination 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 determining that the downstream device response times out.
Optionally, the enumeration request frame is used to cause the node device to feed back the corresponding device descriptor to the master node device 11.
In an alternative implementation, after the initialization operation is finished, the master node device 11 sequentially initiates an enumeration request operation to each of the common node devices 12 or the backup master node device, that is, sends an enumeration request frame. Each enumeration request frame contains a dynamic or static address of a generic node device 12, so each enumeration request operation is directed to only one node device.
When the target node equipment receives an enumeration request frame from an upstream port and the dynamic addresses are matched, an enumeration response confirmation frame is immediately sent; otherwise, forwarding enumeration request frame to downstream port and starting wait timer anda timeout timer. At the wait timer reaching T DEFER When the destination node device sends an enumeration response waiting frame to the upstream port. At the time out timer reaching T TIMEOUT -upon transmission of an enumeration response timeout frame by the target node device to the upstream port.
When the target node device receives the enumeration response acknowledgement frame from the downstream port, it determines whether the dynamic addresses match. If not, forwarding is performed through the upstream port so that the master node device 11 may obtain an enumeration response acknowledgement frame to each of the regular node devices 12. Note that the enumeration response acknowledgement frame also contains a source address and a destination address. The enumeration response acknowledgement frame includes a device descriptor of the corresponding node. It should be appreciated that the device descriptor includes port attributes of the node device, such as port number, port type, and port characteristic wait, which may be used for subsequent virtual channel configuration.
Referring to fig. 4 and fig. 5, fig. 4 is a schematic diagram of an enumeration process according to an embodiment of the present application, and fig. 5 is another schematic diagram of an enumeration process according to an embodiment of the present application. As shown in fig. 4 and fig. 5, in an alternative implementation, the target node device is configured to, after receiving an enumeration request frame transmitted by an upstream device, feed back an enumeration response waiting frame to a corresponding upstream device every a first preset duration, until the generated enumeration response acknowledgement frame is transmitted to the upstream device through an upstream port.
The common node device No. 1 12 and the common node device No. 2 12, upon receiving an enumeration request frame with a target address=1, every first preset time period (T DEFER ) An enumeration response waiting frame is fed back to the upstream port, so that the upstream device is prevented from mistaking the response overtime.
In an optional implementation manner, after the destination node device is further configured to send an enumeration request frame through the downstream port, if the enumeration response frame of the corresponding downstream device is not received beyond the second preset duration, determine that the downstream port response is overtime, generate an enumeration response overtime frame, and send the enumeration response overtime frame through the upstream port.
With continued reference to fig. 4 and 5, assume that the target node device is set for common node No. 2 After the device 12, the number 2 common node device 12 forwards the enumeration request frame through the downstream port, starts its local response timer, starts to count, and if the response timer counts more than the second preset time period (T TIMEOUT ) If any enumeration response frame is not received, determining that the downstream port response is overtime. An enumeration response timeout frame may be generated in which the source address is address=2 and the destination address=0 of the number 2 ordinary node device 12. The No. 3 ordinary node device 12 forwards the enumeration response timeout frame when it is received, and the master node device 11 may determine that the No. 1 ordinary node device has a response timeout when it is received.
If the number 2 common node device 12 receives the enumeration response waiting frame fed back by the downstream device within the second preset duration, resetting its local response timer, and restarting to count. If the common node device 12 receives the enumeration response acknowledgement frame fed back by the downstream device within the second preset duration, timing may be stopped, and the enumeration response acknowledgement frame fed back by the downstream device may be forwarded through the upstream port.
After the completion of the enumeration operation, the master node device 11 accesses the in-vehicle audio network configuration data area (Auto Audio Network Configuration Data, AANCD) within the ordinary node device 12 by the data transmission operation of the control frame. Each node device contains an in-vehicle audio network configuration data area (AANCD) meeting regulatory requirements.
In an alternative embodiment, 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 acknowledgement frame, and an AANCD response timeout frame, the AANCD request frame includes a destination address and a source address, the AANCD response timeout frame includes a destination address and a source address, and the AANCD response acknowledgement frame includes a destination address and a source address. The destination address in the AANCD request frame is the address (dynamic address or static address) of any one of the common node devices 12, and the source address in the AANCD request frame is the address (dynamic address or static address) of the master node device. The destination address in the AANCD response acknowledgement frame is the source address in the AANCD request frame, and the source address in the AANCD response acknowledgement frame is the destination address in the AANCD request frame. The destination 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 response timeout of the downstream device.
Alternatively, the AANCD request frame is used to cause the master node device 11 to acquire AANCD offset addresses and AANCD configuration data of the respective node devices.
In an alternative implementation, after the enumeration operation is finished, the master node device 11 sequentially initiates an AANCD request operation to each of the normal node devices 12 or the backup master node device, that is, sends an AANCD request frame. Each AANCD request frame contains a dynamic or static address of one generic node device 12, so each AANCD request operation is directed to only one node device.
When the target node equipment receives the AANCD request frame from the upstream port and the dynamic addresses are matched, an AANCD response confirmation frame is sent; otherwise, the AANCD request frame is forwarded to the downstream port and a wait timer and a timeout timer are started. At the wait timer reaching T DEFER And when the target node equipment transmits an AANCD response waiting frame to the upstream port. At the time out timer reaching T TIMEOUT And the target node equipment transmits an AANCD response timeout frame to the upstream port.
When the target node device receives the AANCD response acknowledgement frame from the downstream port, judging whether the dynamic addresses are matched. If not, forwarding is performed through the upstream port so that the master node device 11 can acquire the AANCD response acknowledgement frame to each of the ordinary node devices 12. The AANCD response acknowledgement frame also includes a source address and a destination address.
Optionally, the AANCD response acknowledgement frame includes an AANCD offset address and AANCD configuration data.
Referring to fig. 6 and fig. 7, fig. 6 is a schematic diagram of an AANCD access process provided by an embodiment of the present application, and fig. 7 is another schematic diagram of an AANCD access process provided by an embodiment of the present application. As shown in fig. 6 and fig. 7, in an alternative embodiment, the target node device is configured to, after receiving the AANCD request frame transmitted by the upstream device, feedback an AANCD response waiting frame to the corresponding upstream device every a first preset duration, until the generated AANCD response acknowledgement frame is transmitted to the upstream device through the upstream port.
The No. 1 ordinary node device 12 and the No. 2 ordinary node device 12, upon receiving the AANCD request frame with the target address=1, every first preset time period (T DEFER ) An AANCD response waiting frame is fed back to the upstream port to avoid that the upstream device misdeems the response to be overtime.
In an optional implementation manner, the target node device is further configured to, after sending the AANCD request frame through the downstream port, determine that the downstream port has responded and has timed out if the corresponding AANCD response frame of the downstream device is not received beyond the second preset duration, generate an AANCD response timeout frame, and send the AANCD response timeout frame through the upstream port.
With continued reference to fig. 6 and 7, assuming that the target node device is the No. 2 normal node device 12, the No. 2 normal node device 12 starts its local response timer after forwarding the AANCD request frame through the downstream port, starts to count, if the response timer counts more than the second preset time period (T TIMEOUT ) If any AANCD response frame is not received, determining that the downstream port response is overtime. An AANCD response timeout frame may be generated in which the source address is address=2 of the No. 2 normal node device 12 and the destination address=0. The No. 3 normal node device 12 forwards the AANCD response timeout frame when it is received, and the master node device 11 can determine that the No. 1 normal node device has a response timeout when it is received.
If the AANCD response waiting frame fed back by the downstream device is received by the common node device No. 2 in the second preset duration, resetting its local response timer, and restarting to count. If the normal node device 12 receives the AANCD response acknowledgement frame fed back by the downstream device within the second preset duration, the timing may be stopped, and the AANCD response acknowledgement frame fed back by the downstream device may be forwarded through the upstream port.
Referring to tables 1 and 2 below, table 1 below shows one possible AANCD request frame structure.
TABLE 1
Table 2 below is a structural description of the AANCD request frame shown in table 1.
TABLE 2
In an alternative embodiment, 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 acknowledgement 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 acknowledgement frame includes a target address and a source address. The destination address in the configuration request frame is the address (dynamic address or static address) of any one of the common node devices 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 acknowledgement frame is the source address in the configuration request frame, and the source address in the configuration response acknowledgement frame is the target address in the configuration request frame. The target address in the response timeout frame is configured as the source address in the configuration request frame, and the source address in the response timeout frame is configured as the address of the node device determining the response timeout of the downstream device.
Optionally, the configuration request frame is used to enable each node device to complete virtual channel configuration.
In an alternative implementation, after the enumeration operation is finished, the master node device 11 sequentially initiates a configuration request operation to each of the common node devices 12 or the backup master node device, i.e. sends a configuration request frame. Each configuration request frame contains a dynamic or static address of one generic node device 12, so each configuration request operation is directed to only one node device.
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 at least 1 virtual channel descriptor of the node device to be configured, and the node device to be configured is any one of the common node devices 12.
Alternatively, the address information of the node device to be configured may be a dynamic address determined in the initialization process, or may be a static address, which is not limited herein.
When receiving the configuration request frame transmitted by the master node device 11, the common node device 12 analyzes the target address information, namely the address information of the node device to be configured, if the target address information is matched with the address of the node device to be configured, the configuration is performed based on the configuration request frame, and if the target address information is not matched with the address of the node device to be configured, the configuration request frame is forwarded to the downstream device through the downstream port.
Alternatively, 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 transmitting the virtual channel configuration table to the node equipment to be configured through the configuration request frame. The virtual channel configuration table contains at least one virtual channel descriptor corresponding to the node device to be configured.
Referring to table 3, table 3 is a structural description of a virtual channel configuration table according to an embodiment of the present application.
TABLE 3 Table 3
The node device to be configured is further configured to set a virtual channel configuration table stored in the node device to be configured based on the virtual channel descriptor in the configuration request frame after receiving the configuration request frame.
Optionally, the virtual channel configuration table in the configuration request frame is acquired and stored as a virtual channel configuration table of its own. Or, the virtual channel descriptor in the configuration request frame is analyzed, and the stored virtual channel configuration table is updated. The virtual channel configuration table is used for distributing and/or combining the data acquired by the data nodes.
Optionally, in the configuration process, when the target node device receives the configuration request frame from the upstream port and the dynamic addresses match, immediately sending a configuration response acknowledgement frame; otherwise, forwarding the configuration request frame to the downstream port and starting a wait timer and a timeout timer. At the wait timer reaching T DEFER And when the configuration response waiting frame is transmitted to the upstream port by the target node equipment. At the time out timer reaching T TIMEOUT And when the configuration response timeout frame is transmitted to the upstream port by the target node equipment.
When the target node device receives the configuration response confirmation frame from the downstream port, whether the dynamic addresses match or not is judged. If not, forwarding is performed through the upstream port so that the master node device 11 can acquire the configuration response acknowledgement frame to each of the ordinary node devices 12. It should be noted that the configuration response acknowledgement frame also includes a source address and a destination address.
Referring to fig. 8 and 9, fig. 8 is a schematic diagram of a configuration process provided in an embodiment of the present application, and fig. 9 is another schematic diagram of a configuration process provided in an embodiment of the present application. As shown in fig. 8 and 9, in an alternative embodiment, the target node device is configured to, after receiving the configuration request frame transmitted by the upstream device, feedback a configuration response waiting frame to the corresponding upstream device every a first preset duration, until the generated configuration response acknowledgement frame is transmitted to the upstream device through the upstream port.
The No. 1 ordinary node device 12 and the No. 2 ordinary node device 12, upon receiving the configuration request frame with the target address=1, every first preset time period (T DEFER ) The configuration response waiting frame is fed back to the upstream port, so that the upstream device is prevented from mistaking the response overtime.
In an optional implementation manner, the target node device is further configured to, after sending the configuration request frame through the downstream port, determine that the downstream port has responded to the timeout if the corresponding configuration response frame of the downstream device is not received beyond the second preset duration, generate a configuration response timeout frame, and send the configuration response timeout frame through the upstream port.
With continued reference to fig. 8 and 9, assuming that the target node device is the No. 2 ordinary node device 12, the No. 2 ordinary node device 12 starts its local response timer after forwarding the configuration request frame through the downstream port, starts to count, if the response timer counts more than the second preset time period (T TIMEOUT ) If any configuration response frame is not received, determining that the downstream port response is overtime. A configuration response timeout frame may be generated in which the source address is address=2 of the No. 2 ordinary node device 12 and the destination address=0. The No. 3 ordinary node device 12 forwards the configuration response timeout frame when it is received, and the master node device 11 can determine that the No. 1 ordinary node device has response timeout when it is received.
If the common node device No. 2 receives the configuration response waiting frame fed back by the downstream device within the second preset duration, the local response timer is reset, and the timing is restarted. If the common node device 12 receives the configuration response acknowledgement frame fed back by the downstream device within the second preset duration, the timing may be stopped, and the configuration response acknowledgement frame fed back by the downstream device may be forwarded through the upstream port.
In summary, the embodiment of the present application provides a topology network, which includes a master node device and at least 1 common node device, where the master node device and the at least 1 common node device are sequentially connected; the target node device is configured to, when receiving a control request frame transmitted by the upstream port, feed back a response waiting frame to the upstream port every a first preset duration until the upstream port feeds back a response acknowledgement frame or a response timeout frame, so as to avoid that the upstream device misjudges that the response of the target node device is timeout, and after sending the control request frame through the downstream port, if the response frame fed back by the downstream port is still not received after a second preset duration is spaced, determine that the response of the downstream device is timeout, and feed back the response timeout frame through the upstream port, so as to accurately obtain the response state of the downstream device.
The embodiment of the application also provides a topology network communication processing method which can be applied to the topology network but is not limited to the topology network. Referring to fig. 10, fig. 10 is a flowchart illustrating a topology network communication processing method according to an embodiment of the application. Specifically, the topology network communication processing method includes: s101 and S102 are specifically described below.
S101, when receiving a control request frame transmitted by an upstream port, the target node equipment feeds back a response waiting frame to the upstream port every a first preset duration until a response confirmation frame or a response timeout frame is fed back to the upstream port.
The target node equipment is any common node equipment.
S102, after the target node equipment sends the control request frame through the downstream port, if the response frame fed back by the downstream port is still not received for a second preset time interval, determining that the response of the downstream equipment is overtime, and feeding back the response overtime frame through the upstream port.
Wherein the response frame is any one of a response waiting frame, a response confirmation frame and a response timeout frame.
It should be noted that, the topology network communication processing method provided in this embodiment may perform the functional use shown in the above topology network embodiment, so as to achieve the corresponding technical effect. For a brief description, reference is made to the corresponding parts of the above embodiments, where this embodiment is not mentioned.
The above description is only of the preferred embodiments of the present application and is not intended to limit the present application, but various modifications and variations can be made to the present application by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application.
It will be evident to those skilled in the art that the application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned.
Claims (10)
1. The topology network is characterized by comprising a main node device and at least 1 common node device, wherein the main node device and the at least 1 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 a first preset duration 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 one common node device;
the target node device is further configured to determine that the response of the downstream device is overtime and feedback a response overtime frame through the upstream port if the response frame fed back by the downstream port is still not received after the control request frame is sent through the downstream port for a second preset duration;
wherein, the response frame is any one of a response waiting frame, a response confirmation frame and a response timeout frame.
2. The topological network of claim 1, wherein 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 acknowledgement frame, and the initialization response acknowledgement frame contains a dynamic address of the target node device;
and the target node device is further configured to determine that the response of the downstream port is overtime after the initialization request frame is sent through the downstream port, if the initialization response frame of the corresponding downstream device is not received beyond a second preset duration, generate the initialization response confirmation frame, and send the initialization response confirmation frame through the upstream port.
3. The topology network of claim 2, wherein the target node device is further configured to, after receiving the initialization request frame transmitted by the upstream device, feed back an initialization response waiting frame to the corresponding upstream device every a first preset duration until the generated initialization response acknowledgement frame is transmitted to the upstream device through the upstream port.
4. The topological network of claim 1, wherein 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 acknowledgement 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 acknowledgement frame includes a target address and a source address;
the target node device is configured to, after receiving an enumeration request frame transmitted by an upstream device, feed back an enumeration response waiting frame to a corresponding upstream device every a first preset duration until the generated enumeration response acknowledgement frame is transmitted to the upstream device through an upstream port.
5. The topology network of claim 4, wherein the target node device is further configured to determine a downstream port response timeout after sending an enumeration request frame through the downstream port, if an enumeration response frame of a corresponding downstream device is not received beyond a second preset duration, generate the enumeration response timeout frame, and send the enumeration response timeout frame through the upstream port.
6. The topology network of claim 1, wherein 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 wait frame, an AANCD response acknowledge frame, and an AANCD response timeout frame, the AANCD request frame includes a destination address and a source address, the AANCD response timeout frame includes a destination address and a source address, and the AANCD response acknowledge frame includes a destination address and a source address;
and the target node device is used for feeding back an AANCD response waiting frame to the corresponding upstream device every a 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.
7. The topology network of claim 6, wherein said target node device is further configured to, after sending an AANCD request frame via a downstream port, determine that a downstream port response times out if a corresponding AANCD response frame of the downstream device is not received beyond a second preset duration, generate said AANCD response timeout frame, and send said AANCD response timeout frame via an upstream port.
8. The topology network of claim 1, wherein 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 wait frame, a configuration response acknowledgement frame, and a configuration response timeout frame, the configuration request frame contains a target address and a source address, the configuration response timeout frame contains a target address and a source address, and the configuration response acknowledgement frame contains a target address and a source address;
And the target node device is used for feeding back a configuration response waiting frame to the corresponding upstream device every a first preset duration 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 topology network of claim 8, wherein said target node device is further configured to, after sending a configuration request frame via a downstream port, determine that a downstream port has responded to a timeout if a configuration response frame of a corresponding downstream device has not been received beyond a second predetermined duration, generate said configuration response timeout frame, and send said configuration response timeout frame via an upstream port.
10. The topology network communication processing method is characterized by being applied to a topology network, wherein the topology network comprises a main node device and at least 1 common node device, and the main node device and the at least 1 common node device are connected in sequence;
when receiving a control request frame transmitted by an upstream port, the target node equipment feeds back a response waiting frame to the upstream port every a first preset duration until a response confirmation frame or a response timeout frame is fed back to the upstream port;
Wherein the target node device is any one common node device;
after the target node device sends a control request frame through the downstream port, if a response frame fed back by the downstream port is still not received for a second preset time interval, determining that the response of the downstream device is overtime, and feeding back the response overtime frame through the upstream port;
wherein, the response frame is any one of a response waiting frame, a response confirmation frame and a response timeout frame.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211287852.4A CN117176498A (en) | 2022-10-20 | 2022-10-20 | Topology network and communication processing method |
| PCT/CN2023/119998 WO2024082907A1 (en) | 2022-10-20 | 2023-09-20 | Topological network and communication processing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211287852.4A CN117176498A (en) | 2022-10-20 | 2022-10-20 | Topology network and communication processing method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117176498A true CN117176498A (en) | 2023-12-05 |
Family
ID=88940060
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211287852.4A Pending CN117176498A (en) | 2022-10-20 | 2022-10-20 | Topology network and communication processing method |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN117176498A (en) |
| WO (1) | WO2024082907A1 (en) |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8223660B2 (en) * | 2007-04-18 | 2012-07-17 | Rockstar Bidco Lp | Failure notification in a network having serially connected nodes |
| JP2013168712A (en) * | 2012-02-14 | 2013-08-29 | Kyocera Corp | Relay device and communication control method |
| JP2016032274A (en) * | 2014-07-30 | 2016-03-07 | 株式会社デンソー | Gateway unit |
| CN106899472B (en) * | 2017-04-19 | 2019-12-10 | 广州睿嵌电子技术有限公司 | One-way ring network controller and use method thereof |
| WO2020068095A1 (en) * | 2018-09-28 | 2020-04-02 | Hewlett-Packard Development Company, L.P. | Master/slave communication |
| CN112671835B (en) * | 2020-12-07 | 2022-08-09 | 深圳市晨北科技有限公司 | Request processing method, device, system and storage medium |
-
2022
- 2022-10-20 CN CN202211287852.4A patent/CN117176498A/en active Pending
-
2023
- 2023-09-20 WO PCT/CN2023/119998 patent/WO2024082907A1/en unknown
Also Published As
| Publication number | Publication date |
|---|---|
| WO2024082907A1 (en) | 2024-04-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9838221B2 (en) | Base station deployment configuration method for base station, base station, and server | |
| EP2958275B1 (en) | Limp-home operation of audio video bridging networks | |
| CN111555953B (en) | Remote diagnosis method, device and system based on vehicle-mounted Ethernet and TSP (Total suspended particulate) server | |
| CN107517438B (en) | Method for requesting sharing of Bluetooth device, electronic device and computer storage medium | |
| WO2020063742A1 (en) | Resource allocation method and apparatus in device-to-device communication | |
| WO2017036373A1 (en) | Group call service processing method, terminal and core network element | |
| KR100575011B1 (en) | Use of energy bursts for wireless networks | |
| US8855693B2 (en) | Method and apparatus for controlling wireless devices | |
| CN117176498A (en) | Topology network and communication processing method | |
| WO2021056794A1 (en) | Method and apparatus for sending measurement report, and terminal and storage medium | |
| CN101632261B (en) | Full mesh rates transaction in a network | |
| CN111541771A (en) | Internet of things communication method, device and system and computer readable storage medium | |
| US11612007B2 (en) | Low power dissipation Bluetooth mesh network system and communication method | |
| CN115174528A (en) | Equipment address control method, device and system | |
| CN112995095B (en) | Data processing method, device and computer readable storage medium | |
| CN111447126B (en) | Ethernet bus communication method, device, robot, equipment and computer readable storage medium | |
| WO2016197917A1 (en) | Flow entry issuing method, flow entry storage method, relevant apparatus and system | |
| CN117221033A (en) | Topological network and dynamic address initialization method | |
| CN114902614A (en) | Management device, identification information distribution method for in-vehicle device, in-vehicle system, and data structure | |
| WO2014187366A1 (en) | Method and device for paging terminals | |
| JP2012109831A (en) | Communication system | |
| US20230014413A1 (en) | Access control method and apparatus, and communication system | |
| CN105491622B (en) | The methods, devices and systems of wireless network parameter configuration | |
| JP3432449B2 (en) | Communication control apparatus and method | |
| JP2008125009A (en) | Network monitoring system, information processing apparatus, network monitoring method and program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |