A topological network and management method

Abstract

The present application proposes a topology network and management method, wherein the master node device and the common node device are used to perform initialization operation after power-on, so that the master node device determines the dynamic address of each node device in the topology network; after the initialization operation is completed, the master node device and the common node device are also used to perform enumeration operation based on the dynamic address of each node device in the topology network, so that the master node device obtains the port attribute of each node device in the topology network; after the enumeration operation is completed, the master node device and the common node device are also used to perform configuration operation based on the port attribute of each node device in the topology network, so as to complete the setting of the virtual channel configuration table of each node device in the topology network; after the configuration operation is completed, the master node device and the common node device are also used to perform data transmission based on the virtual channel configuration table. After the configuration operation is completed, the topology network can operate stably and efficiently.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a topological network and a management method thereof. 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] In-car audio networks are very important for improving the driving experience of car passengers, and even directly affect the driver's operating judgment. How to build a stable and efficient in-car audio network 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 management 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 master node device and the common node device are used to perform an initialization operation after power-on, so that the master node device determines the dynamic address of each node device in the topology network;

[0008] After the initialization operation is completed, the master node device and the common node device are further used to perform an enumeration operation based on the dynamic address of each node device in the topology network, so that the master node device obtains the port attributes of each node device in the topology network;

[0009] After the enumeration operation is completed, the master node device and the common node device are further used to perform configuration operations based on the port attributes of each node device in the topology network to complete the setting of the virtual channel configuration table of each node device in the topology network;

[0010] Wherein, the virtual channel configuration table includes virtual channel descriptors for data transmission at each port in the node device, and the virtual channel descriptors include corresponding port and / or data location information;

[0011] After the configuration operation is completed, the master node device and the common node device are further used to perform data transmission based on the virtual channel configuration table.

[0012] In a second aspect, an embodiment of the present application provides a topology network management method, which is applied to a topology network, wherein the topology network includes a master node device and at least one ordinary node device, wherein the master node device and the at least one ordinary node device are connected in sequence, and the topology network management method includes:

[0013] After being powered on, the master node device and the common node device perform an initialization operation so that the master node device determines the dynamic address of each node device in the topology network;

[0014] After the initialization operation is completed, the master node device and the common node device perform an enumeration operation based on the dynamic address of each node device in the topology network, so that the master node device obtains the port attribute of each node device in the topology network;

[0015] After the enumeration operation is completed, the master node device and the common node device perform configuration operations based on the port attributes of each node device in the topology network to complete the setting of the virtual channel configuration table of each node device in the topology network;

[0016] Wherein, the virtual channel configuration table includes virtual channel descriptors for data transmission at each port in the node device, and the virtual channel descriptors include corresponding port and / or data location information;

[0017] After the configuration operation is completed, the master node device and the common node device perform data transmission based on the virtual channel configuration table.

[0018] Compared with the prior art, a topological network and management method provided by an embodiment of the present application includes a master node device and at least one common node device, wherein the master node device and the at least one common node device are connected in sequence; the master node device and the common node device are used to perform an initialization operation after power-on, so that the master node device determines the dynamic address of each node device in the topological network; after the initialization operation is completed, the master node device and the common node device are also used to perform an enumeration operation based on the dynamic address of each node device in the topological network, so that the master node device obtains the port attributes of each node device in the topological network; after the enumeration operation is completed, the master node device and the common node device are also used to perform a configuration operation based on the port attributes of each node device in the topological network, so as to complete the setting of the virtual channel configuration table of each node device in the topological network; wherein the virtual channel configuration table contains virtual channel descriptors for data transmission at each port in the node device, and the virtual channel descriptors include corresponding port and / or data location information; after the configuration operation is completed, the master node device and the common node device are also used to perform data transmission based on the virtual channel configuration table. After the configuration operation is completed, the topological network can operate stably and efficiently. In a topology network consisting of serial or ring connections through differential lines, a frame structure is constructed for data transmission, and data forwarding is controlled through a virtual channel configuration table to efficiently utilize the bandwidth of serial transmission.

[0019] 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

[0020] 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.

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

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

[0023] Figure 3 A schematic diagram of the structure of a node device provided in an embodiment of the present application;

[0024] Figure 4 A schematic diagram of a configuration process provided for an embodiment of the present application;

[0025] Figure 5A schematic diagram of the data format sent by each node device corresponding to the virtual channel descriptor shown in Table 5 provided in an embodiment of the present application;

[0026] Figure 6 An example diagram of an enumeration process provided in an embodiment of the present application;

[0027] Figure 7 A schematic diagram of the topology network management method flow provided in an embodiment of the present application.

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

[0029] 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.

[0030] 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.

[0031] 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.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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.

[0036] This application embodiment provides a topology network. Please refer to Figure 1 and Figure 2 , Figure 1 A schematic diagram of the structure of a vehicle serial topology network provided in an embodiment of the present application, Figure 2 A schematic diagram of the structure of a ring topology network provided in an embodiment of the present application.

[0037] 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 at least one common node device 12 are connected in sequence. Optionally, any two node devices can be connected via a differential signal line.

[0038] 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.

[0039] Alternatively, if Figure 2As 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.

[0040] It should be noted that the use of serial connection and ring connection for networking can reduce the number of connection lines. At the same time, data is received and forwarded by node devices, avoiding the problem of poor signal quality in long-distance transmission.

[0041] 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.

[0042] It should be understood that Figure 1 and Figure 2 The topology network shown can be, but is not limited to, an automotive audio network (AAN). When it is an automotive audio network, other devices connected to the common node device 12 through the local port can be, but are not limited to, data acquisition sensors, 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.

[0043] Optionally, in the vehicle audio network, each node device extracts data transmitted by the vehicle audio and sensor data transmission network, converts it into other formats, and outputs it through other data interface forms; or converts data input in other data interface forms into vehicle audio and sensor data and transmits it to the vehicle audio network.

[0044] Optionally, the node device is a general term for devices connected to the vehicle audio network via differential lines, including a master node device 11, a common node device 12, and a standby node device, etc. The node device can convert the data stream transmitted by the local interface to the vehicle audio network for long-distance two-way transmission.

[0045] Please refer to Figure 3 , Figure 3 A schematic diagram of the structure of a node device provided in an embodiment of the present application. Figure 3As shown in the figure, each node device contains multiple device ports, such as PORT1 to PORT8 in the figure. The function of the device port is determined by the function of each node device. The device port number is fixed for each device. The device port is divided into bus port and local port. The bus port is a bidirectional differential serial data port, which performs control operations and data transmission by passing control frames and data frames encoded by bidirectional Manchester encoding. Figure 1 and Figure 2 As shown, the bus port is connected to other node devices through the vehicle audio network. The local interface is connected to other devices. For example Figure 3 A is the upstream port in the bus port, and B is the downstream port in the bus port.

[0046] Specifically, Figure 3 PORT1 is the upstream input port, used to receive message frames transmitted by the upstream device; PORT2 is the downstream output port, used to send message frames to the downstream device; PORT3 is the downstream input port, used to receive message frames transmitted by the downstream device, and PORT4 is the upstream output port, used to send message frames to the upstream device.

[0047] PORT5 is used to transmit audio data to the audio device (Audio) so that the audio device can play the received audio data; PORT6 is used to receive data transmitted by the audio device. PORT7 is used to transmit data to the radio (Broadcasting), and PORT8 is used to receive data transmitted by the radio (Broadcasting).

[0048] Of course, the node device may also be provided with a port for connecting a sensor for data collection, so as to receive the data collected by the sensor.

[0049] It should be understood that there is only one master node device 11 in the topology network (e.g., in-vehicle audio network). After each node device completes the initialization operation, the master node device 11 will actively query the device descriptors of other node devices through enumeration operations, and based on this information, configure the virtual channel configuration table of other node devices through configuration operations. The master node device 11 will insert the master node timestamp information into the data frame it sends. Other ordinary node devices correct the clocks in their respective node devices based on the master node timestamp information.

[0050] After the system is powered on, the common node device 12 initiates an initialization operation to the downstream port to verify that there is a node device connected to the downstream port. At the same time, after receiving a response from the downstream port, it responds to the initialization operation of the upstream port. The common node device 12 responds to the enumeration operation initiated by the master node device 11 and feeds back the device descriptor of the current device to the master node device 11. When the master node device 11 and the non-adjacent common node device 12 perform enumeration operations and device descriptor feedback, it needs to be completed through the routing of the common node devices between the two.

[0051] In the topology network provided in the embodiment of the present application, two data frame structures are defined for data transmission, namely control frames and data frames.

[0052] Optionally, control frames are used during initialization operations, enumeration operations, and configuration operations. The transmission of control frames does not depend on the audio transmission frequency, which can greatly improve the efficiency of control information interaction. The data frame includes a timestamp information segment, a broadcast data segment, and a non-broadcast data segment. The ordinary node device 12 can calibrate the local clock through the timestamp of the master node device 11 to ensure the low-latency characteristics of data transmission. The broadcast data segment can transmit sensor data in time-division multiplexing during the audio data transmission process. At the same time, the uplink broadcast data segment can also be reused for interrupt information uplink transmission. For each node device, multiple ports are defined. The data received by each port is distributed or merged through the control of the virtual channel configuration table.

[0053] Please refer to Table 1 and Table 2 below. Table 1 below shows a possible control frame format.

[0054]

[0055] Table 1

[0056] The following table 2 is a structural description of the control frame shown in Table 1.

[0057]

[0058]

[0059] Table 2 refers to Table 3 and Table 4 below. Table 3 below shows a possible data frame format.

[0060]

[0061] Table 4 below Table 3 is a structural description of the data frame shown in Table 3.

[0062]

[0063]

[0064] Table 4

[0065] Regarding how to complete the configuration of the topology network to ensure stable and efficient operation of the topology network, the embodiment of the present application also provides a possible implementation method, please refer to the following.

[0066] The master node device 11 and the common node device 12 are used to perform initialization operations after power-on, so that the master node device 11 determines the dynamic address of each node device in the topology network.

[0067] Optionally, through the initialization operation, the master node device 11 can also determine the number of node devices in the topology network.

[0068] After the initialization operation is completed, the master node device 11 and the common node device 12 are further used to perform enumeration operations based on the dynamic addresses of each node device in the topology network, so that the master node device obtains the port attributes of each node device in the topology network.

[0069] After the enumeration operation is completed, the master node device 11 and the common node device 12 are further used to perform configuration operations based on the port attributes of each node device in the topology network to complete the setting of the virtual channel configuration table of each node device in the topology network.

[0070] The virtual channel configuration table includes virtual channel descriptors for data transmission at various ports in the node device, and the virtual channel descriptors include corresponding port and / or data location information.

[0071] Optionally, the virtual channel descriptor also includes a corresponding virtual channel number, and the data location information indicates a storage location of the data to be extracted corresponding to the virtual channel descriptor in the data frame.

[0072] After the configuration operation is completed, the master node device 11 and the common node device 12 are further used to perform data transmission based on the virtual channel configuration table.

[0073] It should be understood that the virtual channel configuration table configured in each node device is used to control data forwarding and efficiently utilize the bandwidth of the serial data line.

[0074] In an optional implementation manner, the master node device 11 is further configured to generate a corresponding virtual channel descriptor based on the port attributes of each node device in the topology network.

[0075] Please refer to Table 5, which is a description of a possible virtual channel descriptor.

[0076]

[0077]

[0078] Table 5

[0079] Optionally, each node device is provided with a corresponding virtual channel descriptor. The virtual channel descriptor includes a corresponding port, data location information and a corresponding virtual channel number. The data starting position and data length in the table are used together to describe the data location information. The data corresponding to the virtual channel is transmitted from the source port to the target port.

[0080] It should be noted that the source port number and the destination port number in Table 5 may be, but are not limited to, the reference port number. Figure 3 The ports in the node device shown.

[0081] It should be understood that the virtual channel descriptor of the master node device 11 itself can be directly stored in the corresponding virtual channel configuration table without being transmitted to other node devices. In order to implement the virtual channel configuration of other devices, the virtual channel descriptors of other ordinary nodes 12 need to be sent to the corresponding ordinary nodes. Please refer to the following for details.

[0082] The master node device 11 is also used to send a configuration request frame to the target node device. The configuration request frame includes the address information of the target node device and the virtual channel descriptor of at least one target node device. The target node device is any common node device 12 .

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

[0084] When the ordinary node device 12 receives the configuration request frame transmitted by the main node device 11, it parses the target address information, that is, the address information of the target node device. If the target address information matches its own address, it performs configuration based on the configuration request frame. If it does not match, it forwards the configuration request frame to the downstream device through the downstream port.

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

[0086] Please refer to Table 6 and Table 7 below. Table 6 below shows a possible configuration request frame structure.

[0087]

[0088]

[0089] Table 7 below Table 6 is a structural description of the configuration request frame shown in Table 6.

[0090]

[0091] Please refer to Table 8 for Table 7. Table 8 is a structural description of a virtual channel configuration table provided in an embodiment of the present application.

[0092]

[0093]

[0094] Table 8

[0095] As shown in Table 6, payload byte 1 to payload byte N-1 are used to record the virtual channel configuration table corresponding to the target node device. Referring to Table 8, it can be seen that every 5 bytes represent a virtual channel descriptor. Affected by the number of payload bytes, the number of virtual channel descriptors contained in the virtual channel configuration table of a single transmission is limited. For example, in one configuration operation, at most three virtual channels can be configured.

[0096] When the total number of virtual channels to be configured in the target node device is greater than the upper limit of the number of single configurations, the virtual channel configuration can be performed multiple times.

[0097] The target node device 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.

[0098] 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.

[0099] In order to ensure that the virtual channel configuration can be completed accurately, the embodiment of the present application also provides an optional implementation method, please refer to the following.

[0100] The configuration request frame also includes the total number of virtual channels to be configured of the target node device, for example, the number recorded in payload byte 0 of the configuration request frame.

[0101] The target node device is also used to feed back a configuration response confirmation frame to the master node device 11 after receiving the configuration request frame, wherein the configuration response confirmation frame includes the address information of the target node device, the address information of the master node device and the configuration status identifier.

[0102] When other ordinary node devices 12 receive the configuration response confirmation frame fed back by the target node device, they will forward the configuration response confirmation frame based on the target address, that is, the address information of the master node device 11, so that the master node device 11 can obtain the configuration response confirmation frame fed back by the target node device.

[0103] The purpose of the configuration response confirmation frame is only to prompt the master node device 11 to issue a new configuration request based on the remaining unconfigured virtual channel descriptors; the configuration status indicator indicates that the configuration is completed (for example, the remaining unconfigured number is 0) or the configuration is incomplete (for example, the remaining unconfigured number is not equal to 0).

[0104] Of course, the configuration status indicator may also directly indicate the remaining unconfigured quantity.

[0105] Please refer to Table 9 and Table 10 below. Table 9 below shows a possible configuration response confirmation frame structure.

[0106]

[0107]

[0108] Table 9

[0109] Table 10 below is a structural description of the configuration response confirmation frame shown in Table 9.

[0110]

[0111] Table 10

[0112] The master node device 11 is also used to, after receiving the configuration response confirmation frame, if it is determined that the configuration status identifier indicates that the virtual channel configuration of the target node device is not completed, generate a new configuration request frame based on the remaining virtual channel descriptors of the target node device, and send the new configuration request frame to the target node device until the configuration status identifier in the received configuration response confirmation frame indicates that the virtual channel configuration of the target node device is completed.

[0113] Optionally, refer to Figure 4 , Figure 4 A schematic diagram of a configuration process provided in an embodiment of the present application. Figure 4 As shown, when the common node device 12 receives the configuration request frame, if the target address does not match, it will forward the configuration request frame through the downstream port, and if it matches, it will generate a configuration response confirmation frame. Similarly, the common node device 12 will also forward the configuration response confirmation frame, so that the master node device 11 can obtain the configuration response confirmation frame fed back by all common node devices 12. It should be noted that Figure 4 The addresses shown in are for example only and are not limiting.

[0114] In an optional implementation, after the configuration operation is completed, data frames can be transmitted between node devices. When the data sent by the master node device to the bus is ready, the data frame transmission can be initiated. As shown in Tables 3 and 4, data bits 0 to 31 in the data frame are specially reserved for broadcast data. The data frame may also carry non-broadcast data, such as data corresponding to each virtual channel. Specifically, the data corresponding to different virtual channels are stored in different positions in the data frame. Specifically, data placement can be performed based on the data location information corresponding to the virtual channel descriptor.

[0115] Optionally, non-broadcast data transmission includes but is limited to 6 possible forms. Please refer to Table 11, which is a description of non-broadcast data transmission types and configurations.

[0116]

[0117] Table 11

[0118] It should be noted that there is no data defined in the virtual channel configuration table for type 1 and type 2 transmission.

[0119] If the data from the 32nd bit in the data frame needs to be forwarded to other ports, it needs to be defined in the virtual channel configuration table. The virtual channel configuration table is configured by the master node device 11 to each common node device 12. Each common node device 12 forwards data according to the configuration of the virtual channel configuration table. Figure 1 and Figure 3 For example, each common node device 12 has local audio input and output. In the application, the virtual channel descriptor shown in Table 5 indicates that common node device No. 2 and common node device No. 1 play the 32-bit audio sent by the master node device 11, and common node device No. 3 plays the 16-bit audio collected by common node device No. 1. The 32-bit audio collected by common node device No. 2 and common node device No. 3 is transmitted to the master node device 11.

[0120] Specifically, please refer to Figure 5 , Figure 5 A schematic diagram of the data format sent by each node device corresponding to the virtual channel descriptor shown in Table 5 provided in an embodiment of the present application.

[0121] like Figure 5As shown, the master node device 11 sends a data frame through the downstream port, and the upstream input port (source port number 1) of the ordinary node device No. 1 12 receives the data frame. It should be understood that the data frame does not include the target address information and is non-directional data. The upstream input port of the ordinary node device No. 1 12 corresponds to the virtual channel 0 of the ordinary node device No. 1 12, and the corresponding data starting position is 32 bits and the data length is 32 bits. The ordinary node device No. 1 12 extracts the target data corresponding to the starting position of 32 bits and the data length of 32 bits in the received data frame, and sends the target data to the target port number 5 corresponding to the virtual channel 0 of the ordinary node device No. 1 12. In one embodiment, the ordinary node device No. 1 12 will also send out the data frame after deleting its corresponding target data through its downstream port, so that the ordinary node device No. 2 12 receives the data frame, and its sending process is the same as that of the ordinary node device No. 1 12, until it reaches the ordinary node device No. 3 at the end.

[0122] Please continue to refer to Figure 5 The common node device 12 will also upload data according to each virtual channel descriptor in the corresponding virtual channel configuration table. The process is the same as the sending process and will not be described in detail here.

[0123] In an optional implementation, the common node device 12 is also used to determine whether a target descriptor exists based on the virtual channel configuration table stored therein when the target port receives non-directional data (data frame in the embodiment of the present application); if so, the received data is processed based on the target descriptor; if not, the received data is sent to the default matching port of the target port.

[0124] The target port is any port of a common node device, and the target descriptor is a virtual channel descriptor including the target port.

[0125] Optionally, the received data is processed based on the target descriptor, specifically including:

[0126] Extract the data corresponding to the target descriptor in the current data frame (ie, the target data), and determine whether the current data frame has data corresponding to other virtual channel descriptors. If so, send the extracted data frame through the default matching port of the target port.

[0127] Optionally, after extracting the data corresponding to the target descriptor in the current data frame, the extracted data is deleted in the current data frame, and a forward shift and padding operation is performed on the data corresponding to other virtual channel descriptors to obtain an extracted data frame.

[0128] Optionally, other virtual channel descriptors are virtual channel descriptors corresponding to other ports.

[0129] The target data corresponding to the target descriptor is extracted from the received data frame, and then the target data is sent to the target port number corresponding to the target descriptor, and the data frame after deleting the target data is sent out through the downstream port.

[0130] Alternatively, the data received by the local port (source port number in the target descriptor) is added to the upstream data frame according to the convention of the target descriptor and sent out through the upstream port.

[0131] Optionally, regarding how to implement the enumeration operation, the present application embodiment also provides a possible implementation method, please refer to Figure 6 , Figure 6 An example diagram of an enumeration process provided for an embodiment of the present application. Figure 6 The enumeration request frame and enumeration response confirmation frame shown are control frames.

[0132] After the initialization operation is completed, the master node device 11 initiates enumeration request operations to each common node device 12 or backup master node device in turn, that is, sends enumeration request frames. Each enumeration request frame contains a dynamic address or static address of a common node device 12, so each enumeration request operation is only for one node device.

[0133] When a node device receives an enumeration request frame from an 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 When the current node device sends an enumeration response timeout frame to the upstream port.

[0134] When the node device receives the enumeration 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 enumeration response confirmation frame of each ordinary node device 12. It should be noted that the enumeration response confirmation frame also includes the source address and the destination address.

[0135] Please refer to Table 12 and Table 13 below. Table 12 below shows a possible enumeration request frame structure.

[0136]

[0137] Table 12

[0138] Table 13 below is a structural description of the enumeration request frame shown in Table 12.

[0139]

[0140] Table 13

[0141] Please refer to Table 14 and Table 15 below. Table 14 below shows a possible enumeration response waiting frame structure.

[0142]

[0143] Table 14 and Table 15 are structural descriptions of the enumeration response wait frame shown in Table 16.

[0144]

[0145] Table 16 refers to Table 17 and Table 18 below. Table 17 below shows a possible enumeration response confirmation frame structure.

[0146]

[0147] Table 18 below Table 17 is a structural description of the enumeration response confirmation frame shown in Table 17.

[0148]

[0149] Table 18 needs to explain that the enumeration response confirmation frame includes the device descriptor of the node device. The device descriptor is shown in Table 19.

[0150]

[0151] Table 19

[0152] When performing enumeration operations, the maximum number of bytes that can be returned by the enumeration response confirmation frame to the device descriptor is 15 bytes, and the device descriptors of at most 5 ports can be returned at a time. When the master device node finds that the number of ports responded by a node device does not match the number of ports in the subsequent node descriptor, the master node device should send an enumeration request frame again, with the payload byte 0 being 2, indicating that the enumeration operation continues. The accessed node device will continue to feed back the node descriptors of the remaining ports to the master node device through the enumeration response confirmation frame.

[0153] Please refer to Table 20 and Table 21. Table 20 is a list of port types and Table 21 is a list of port characteristics.

[0154]

[0155] Table 20

[0156]

[0157]

[0158] Table 21

[0159] It should be understood that the device descriptor includes the port attributes of each node device, such as the port number, port type, and port characteristics.

[0160] In summary, the embodiment of the present application provides a topology network, including a master node device and at least one common node device, the master node device and at least one common node device are connected in sequence; the master node device and the common node device are used to perform an initialization operation after power-on, so that the master node device determines the dynamic address of each node device in the topology network; after the initialization operation is completed, the master node device and the common node device are also used to perform an enumeration operation based on the dynamic address of each node device in the topology network, so that the master node device obtains the port attributes of each node device in the topology network; after the enumeration operation is completed, the master node device and the common node device are also used to perform a configuration operation based on the port attributes of each node device in the topology network to complete the setting of the virtual channel configuration table of each node device in the topology network; wherein the virtual channel configuration table contains virtual channel descriptors for data transmission at each port in the node device, and the virtual channel descriptors include corresponding port and / or data location information; after the configuration operation is completed, the master node device and the common node device are also used to perform data transmission based on the virtual channel configuration table. After the configuration operation is completed, the topology network can operate stably and efficiently. In a topology network consisting of serial or ring connections through differential lines, a frame structure is constructed for data transmission, and data forwarding is controlled through a virtual channel configuration table to efficiently utilize the bandwidth of serial transmission.

[0161] The present application also provides a topology network management method, which can be applied to but not limited to Figure 1 and Figure 2 For more information, please refer to the topology shown in the figure. Figure 7 , the topology network management method includes: S101, S102, S103 and S104, which are specifically described as follows.

[0162] S101, after being powered on, the master node device and the common node device perform an initialization operation so that the master node device determines the dynamic address of each node device in the topology network.

[0163] S102, after the initialization operation is completed, the master node device and the common node devices perform enumeration operations based on the dynamic addresses of each node device in the topology network, so that the master node device obtains the port attributes of each node device in the topology network.

[0164] S103, after the enumeration operation is completed, the master node device and the common node device perform configuration operations based on the port attributes of each node device in the topology network to complete the setting of the virtual channel configuration table of each node device in the topology network.

[0165] The virtual channel configuration table includes virtual channel descriptors for data transmission at various ports in the node device, and the virtual channel descriptors include corresponding port and / or data location information.

[0166] S104, after the configuration operation is completed, the master node device and the common node device perform data transmission based on the virtual channel configuration table.

[0167] In an optional implementation, S103 includes: the master node device generates a corresponding virtual channel descriptor based on the port attributes of each node device in the topology network.

[0168] The master node device sends a configuration request frame to the target node device. The configuration request frame includes address information of the target node device and a virtual channel descriptor of at least one target node device. The target node device is any common node device.

[0169] After receiving the configuration request frame, the target node device sets the virtual channel configuration table stored therein based on the virtual channel descriptor in the configuration request frame.

[0170] In an optional implementation, the configuration request frame further includes the total number of virtual channels to be configured of the target node device, and S103 further includes:

[0171] After receiving the configuration request frame, the target node device feeds back a configuration response confirmation frame to the master node device, wherein the configuration response confirmation frame includes the address information of the target node device, the address information of the master node device, and a configuration status identifier.

[0172] After receiving the configuration response confirmation frame, if the master node device determines that the configuration status identifier indicates that the virtual channel configuration of the target node device is not completed, it generates a new configuration request frame based on the remaining virtual channel descriptors of the target node device and sends the new configuration request frame to the target node device until the configuration status identifier in the received configuration response confirmation frame indicates that the virtual channel configuration of the target node device is completed.

[0173] In an optional embodiment, the topology network management method also includes: when the ordinary node device receives non-directional data at the target port, it determines whether there is a target descriptor based on the virtual channel configuration table stored therein; if so, it processes the received data based on the target descriptor; if not, it sends the received data to the default matching port of the target port; wherein the target port is any port of the ordinary node device, and the target descriptor is the virtual channel descriptor containing the target port.

[0174] Optionally, processing the received data based on the target descriptor includes extracting data corresponding to the target descriptor in the current data frame, and determining whether the current data frame contains data corresponding to other virtual channel descriptors; if so, sending the extracted data frame through the default matching port of the target port.

[0175] Optionally, after extracting the data corresponding to the target descriptor in the current data frame, the extracted data is deleted in the current data frame, and a forward shift and padding operation is performed on the data corresponding to other virtual channel descriptors to obtain an extracted data frame.

[0176] It should be noted that the topology network management method provided in this embodiment can perform the functions and uses 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, please refer to the corresponding contents in the above embodiment.

[0177] 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.

[0178] 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 master node device and the common node device are used to perform an initialization operation after power-on, so that the master node device determines the dynamic address of each node device in the topology network; After the initialization operation is completed, the master node device and the common node device are further used to perform an enumeration operation based on the dynamic address of each node device in the topology network, so that the master node device obtains the port attributes of each node device in the topology network; After the enumeration operation is completed, the master node device and the common node device are further used to perform configuration operations based on the port attributes of each node device in the topology network to complete the setting of the virtual channel configuration table of each node device in the topology network; The virtual channel configuration table includes virtual channel descriptors for data transmission at each port in the node device, the virtual channel descriptors include corresponding ports and data location information, and the data location information indicates the storage location of the data to be extracted corresponding to the virtual channel descriptors in the data frame; After the configuration operation is completed, the master node device and the common node device are further used to perform data transmission based on the virtual channel configuration table.

2. The topological network according to claim 1, characterized in that: The master node device is also used to generate a corresponding virtual channel descriptor based on the port attributes of each node device in the topology network; The master node device is further used to send a configuration request frame to the target node device, wherein the configuration request frame includes the address information of the target node device and at least one virtual channel descriptor of the target node device, and the target node device is any common node device; The target node device 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.

3. The topological network according to claim 2, characterized in that: The configuration request frame also includes the total number of virtual channels to be configured of the target node device; The target node device is further configured to feed back a configuration response confirmation frame to the master node device after receiving the configuration request frame, wherein the configuration response confirmation frame includes the address information of the target node device, the address information of the master node device, and a configuration status identifier; The master node device is also used to, after receiving the configuration response confirmation frame, if it is determined that the configuration status identifier indicates that the virtual channel configuration of the target node device is not completed, generate a new configuration request frame based on the remaining virtual channel descriptors of the target node device, and send the new configuration request frame to the target node device until the configuration status identifier in the received configuration response confirmation frame indicates that the virtual channel configuration of the target node device is completed.

4. The topological network according to claim 1, characterized in that: The common node device is further used for determining whether a target descriptor exists based on the virtual channel configuration table stored therein when the target port receives non-directional data; if so, processing the received data based on the target descriptor; if not, sending the received data to a default matching port of the target port; The target port is any port of the common node device, and the target descriptor is a virtual channel descriptor including the target port.

5. The topological network according to claim 4, characterized in that: Processing the received data based on the target descriptor includes extracting data corresponding to the target descriptor in the current data frame, and determining whether the current data frame has data corresponding to other virtual channel descriptors. If so, the extracted data frame is sent through the default matching port of the target port.

6. The topological network according to claim 5, characterized in that: After extracting the data corresponding to the target descriptor in the current data frame, the extracted data is deleted in the current data frame, and the data corresponding to other virtual channel descriptors are shifted forward and filled to obtain the extracted data frame.

7. The topological network according to claim 1, characterized in that: The topology network is a serial topology network, the downstream port of the master node device is connected to the upstream port of the first common node device, the upstream port of the i-th common node device is connected to the downstream port of the i-1-th common node device, and the downstream port of the n-th common node device is left floating, 2≤i≤n, n is the number of the common node devices.

8. The topological network according to claim 1, characterized in that: The topology network is a ring topology network, the downstream port of the master node device is connected to the upstream port of the first ordinary node device, the upstream port of the i-th ordinary node device is connected to the downstream port of the i-1-th ordinary node device, and the downstream port of the n-th ordinary node device is connected to the upstream port of the master node device, 2≤i≤n, n is the number of the ordinary node devices.

9. A topology network management method, characterized in that: Applied to a topological network, the topological 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, and the topological network management method includes: After being powered on, the master node device and the common node device perform an initialization operation so that the master node device determines the dynamic address of each node device in the topology network; After the initialization operation is completed, the master node device and the common node device perform an enumeration operation based on the dynamic address of each node device in the topology network, so that the master node device obtains the port attribute of each node device in the topology network; After the enumeration operation is completed, the master node device and the common node device perform configuration operations based on the port attributes of each node device in the topology network to complete the setting of the virtual channel configuration table of each node device in the topology network; The virtual channel configuration table includes virtual channel descriptors for data transmission at each port in the node device, the virtual channel descriptors include corresponding ports and data location information, and the data location information indicates the storage location of the data to be extracted corresponding to the virtual channel descriptors in the data frame; After the configuration operation is completed, the master node device and the common node device perform data transmission based on the virtual channel configuration table.

10. The topology network management method according to claim 9, characterized in that: The step of performing configuration operations on the master node device and the common node device based on the port attributes of each node device in the topology network includes: The master node device generates a corresponding virtual channel descriptor based on the port attributes of each node device in the topology network; The master node device sends a configuration request frame to the target node device, wherein the configuration request frame includes address information of the target node device and a virtual channel descriptor of at least one of the target node devices, and the target node device is any common node device; After receiving the configuration request frame, the target node device sets the virtual channel configuration table stored therein based on the virtual channel descriptor in the configuration request frame.

11. The topology network management method according to claim 10, characterized in that: The configuration request frame also includes the total number of virtual channels to be configured of the target node device, and the master node device and the common node device perform configuration operations based on the port attributes of each node device in the topology network, and further includes: After receiving the configuration request frame, the target node device feeds back a configuration response confirmation frame to the master node device, wherein the configuration response confirmation frame includes the address information of the target node device, the address information of the master node device, and a configuration status identifier; After receiving the configuration response confirmation frame, if the master node device determines that the configuration status identifier indicates that the virtual channel configuration of the target node device is not completed, it generates a new configuration request frame based on the remaining virtual channel descriptors of the target node device, and sends the new configuration request frame to the target node device until the configuration status identifier in the received configuration response confirmation frame indicates that the virtual channel configuration of the target node device is completed.

12. The topology network management method according to claim 9, characterized in that: The topology network management method further includes: When the common node device receives non-directional data at the target port, it determines whether there is a target descriptor based on the virtual channel configuration table stored therein, and if so, processes the received data based on the target descriptor; if not, it sends the received data to the default matching port of the target port; The target port is any port of the common node device, and the target descriptor is a virtual channel descriptor including the target port.

13. The topology network management method according to claim 12, characterized in that: Processing the received data based on the target descriptor includes extracting data corresponding to the target descriptor in the current data frame, and determining whether the current data frame has data corresponding to other virtual channel descriptors. If so, the extracted data frame is sent through the default matching port of the target port.

14. The topology network management method according to claim 13, characterized in that: After extracting the data corresponding to the target descriptor in the current data frame, the extracted data is deleted in the current data frame, and the data corresponding to other virtual channel descriptors are shifted forward and filled to obtain the extracted data frame.

Images