US20050047352A1 - Method for identifying devices in a communication network and device for implementing said method - Google Patents

Method for identifying devices in a communication network and device for implementing said method Download PDF

Info

Publication number
US20050047352A1
US20050047352A1 US10/964,190 US96419004A US2005047352A1 US 20050047352 A1 US20050047352 A1 US 20050047352A1 US 96419004 A US96419004 A US 96419004A US 2005047352 A1 US2005047352 A1 US 2005047352A1
Authority
US
United States
Prior art keywords
node
nodes
child
port
network
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.)
Abandoned
Application number
US10/964,190
Inventor
Nicolas Burdin
Helmut Buerklin
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to US10/964,190 priority Critical patent/US20050047352A1/en
Publication of US20050047352A1 publication Critical patent/US20050047352A1/en
Abandoned legal-status Critical Current

Links

Images

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
    • H04L12/40052—High-speed IEEE 1394 serial bus
    • H04L12/40078—Bus configuration
    • 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

Abstract

In a 1394 bus, during the bus reset procedure, nodes exchange some Self-id packets. The invention presents a method for a node to build the topology of the bus from the information contained in the Self-id packets. Once the node has collected all the Self-id packets, the node goes over nodes to separate parent nodes (with at least one child) and children nodes (with no child). Then by going over nodes from the smallest Phy-id to the root, one can attribute which node is connected to every port of a given node.

Description

    BACKGROUND OF THE INVENTION
  • The present invention relates to the field of communication networks, especially of the home automation type and relates more particularly to a process for identifying apparatus of a home automation network after a bus reinitialization, as well as to an apparatus for implementing the process.
  • The IEEE 1394 bus defined in the document ‘IEEE Std 1394-1995 High Performance Bus, 1996-08-30’ describes a serial bus for digital transmission allowing the connection of apparatus also referred to as ‘nodes’. Certain nodes comprise a fixed identification number which is unique to them and which is termed the ‘EUI’. Furthermore, a second identifier or ‘physical address’ is associated with each apparatus during the bus initialization phases. This second identifier is referenced as the ‘Physical_ID’ in the above-mentioned document and may change for one and the same apparatus at the whim of the bus reinitializations, following for example the connection of a new node or the disconnection of an existing node.
  • An example of reinitialization and of a process for allocating physical addresses is given in appendix E, sections 3.1 to 3.3 of the IEEE document.
  • Now, following a reinitialization, a node does not know the physical addresses of the other nodes connected to the bus, but only some of the identifiers EUI of these nodes. So that a node can find another node whose identifier EUI it knows, a reading of each identifier EUI must be performed at the level of each apparatus until the sought-after identifier is obtained, assuming that the node has not been disconnected.
  • This method of recognizing nodes is slow and generates traffic.
  • A purpose of the invention is to remedy the drawbacks of the method advocated in the prior art.
    • BRIEF SUMMARY OF THE INVENTION
  • The subject of the invention is a process for identifying nodes in a communication network, each node being provided with at least one port for connection to the network, characterized in that it comprises the steps of:
      • allocating a first unique address to each node of the network according to a given process,
      • allocating a second unique address to each node of the network after a reinitialization of the said network,
      • following a reinitialization, establishing a correspondence table comprising the relation between the first and the second address of a node.
  • According to a particular embodiment, the process furthermore comprises the step of determining the set of nodes which are present in the network before reinitialization and not present in the network after reinitialization, and/or the step of determining the set of nodes which are present in the network after reinitialization, but not present in the network before reinitialization.
  • According to a particular embodiment, the said step of establishing the correspondence table comprises for each port of each node the steps of determining:
      • the presence of a node connected to this port before and after reinitialization, and as appropriate, the writing of the pair of addresses before and after reinitialization into the said table,
      • the presence of a node connected to this port before reinitialization and node absence after reinitialization,
      • the presence of a node connected to this port after reinitialization and node absence before reinitialization.
  • According to a particular embodiment, the step of allocating the unique addresses comprises the step of sending over the network via each node of the network information giving its unique address in the network and for each of its ports the information item according to which a port is connected to a node termed the “father” node, to a node termed the “child” node or whether it is not connected.
  • According to a particular embodiment, the node intended to determine the correspondence table determines on the basis of the information received from the other nodes linked to the network during the step of allocating the unique addresses, the tree structure of the network before and after reinitialization.
  • The subject of the invention is also an apparatus intended to be linked to a communication network characterized in that it comprises:
      • means for participating in obtaining a unique address of a node of this apparatus in the network following a reinitialization;
      • means for determining and storing the topology of the network before and after a reinitialization of the network;
      • means for establishing a correspondence table between the unique addresses of the nodes of the network before and after the said reinitialization on the basis of the topologies of the network.
    BRIEF DESCRIPTION OF THE DRAWINGS
  • Other characteristics and advantages of the present invention will emerge from the description of the illustrative embodiment which follows, taken by way of non-limiting example, with reference to the appended figures in which:
  • FIG. 1 is a diagram of a topology of a network,
  • FIG. 2 is a flowchart of a process for determining topology,
  • FIG. 3 is a flowchart of a process for creating a table of correspondence between the addresses of apparatus before and after a reinitialization,
  • FIG. 4 is a diagram of a topology of the network of FIG. 1, after modification and reinitialization,
  • FIG. 5 is a block diagram of a node able to be connected to the network.
    • DETAILED DESCRIPTION OF THE INVENTION
  • To simplify the description, the same references will be used in the figures to denote the elements fulfilling identical functions.
  • According to the present illustrative embodiment, a node possesses one or more bidirectional ports via which it can be connected to other nodes. Not all the ports of a node are necessarily used in a given configuration. The connections are such that they do not form any loop, thus constituting a tree structure. A node is the child of another node, the latter being referred to as the father, if it is connected directly to the latter and if it is more distant than its father from the root, the latter being a node chosen by any process whatsoever.
  • It should be noted that a physical apparatus can comprise several distinct nodes.
  • FIG. 1 represents an illustrative bus comprising six nodes, referenced from A to F. Following a reinitialization of the bus, each node possesses only the item of information according to which it is linked to a single other node (the first node is then referred to as a ‘leaf’) or to more than one node (‘branch’). Each node firstly determines, for each of its ports, whether they are connected to a parent node (‘Parent port’), to a child node (‘Child port’) or whether they are not connected. The ports of each node are numbered in ascending order.
  • An illustrative process allowing this identification and the solving of any conflicts is described in section 3.7.3.1.2 and in appendix E, section 3.2 of the IEEE document.
  • Secondly, a unique physical address must be associated with each node connected to the bus. An autoidentification mechanism, an example of which is described in section 3.7.3.1.3 and in appendix E, section 3.3, is then implemented. This process allows each node to determine, for itself, its physical address, by accounting for data packets of a certain type (so-called ‘Self_ID’ packets) transmitted by the nodes over the bus. The autoidentification process can be summarized thus: the root node hands over to the node connected to its port having the smallest number and waits for this node, as well for all the ‘child’ nodes which are connected to it to be identified, before passing to the next port. When the root has reviewed all its ports, it is also identified. When a node takes over, it hands over in succession to its child nodes, in the order of its ports. When a node does not possess any children, it is identified by transmitting an appropriate packet over the bus.
  • For a node, identification consists in transmitting a data packet containing the physical address of the node, when it is its turn and when all its child nodes have been identified. The address of a node is equal to the last address transmitted in a packet over the bus, incremented by one unit. The first node conventionally has the address ‘0’.
  • The autoidentification packet also contains the category of each of the ports of the node which is identified. A packet may contain an item of information relating to four ports. If a node possesses more than four ports, then it must send several autoidentification packets.
  • In FIG. 1, the physical addresses determined by virtue of the autoidentification process have been labelled alongside the references A to F. The digits inside each frame representing a node indicate the port numbers.
  • Following the implementing of the two processes mentioned above, the following information is available:
    TABLE 1
    Node Parent Ports Child Ports Ports not linked
    0 2 — 0, 1
    1 0 — 1
    2 0 — —
    3 1 0, 2 —
    4 1 — 0
    5 — 0, 1, 3 2
  • This table lists the nodes 0, 1, 2, 3, 4 and 5 of the network 20 of FIG. 1. In this table, the nodes are identified by their physical addresses. The information contained in table 1 is contained in the autoidentification packets.
  • It is possible, for any entity connected to the network, to construct the topology of the network from the information contained in Table 1. With respect to the contents of this table, the missing information item which fully determines the topology is that which indicates which node is connected to the ‘child’ ports of the ‘parent’ nodes.
  • According to the present embodiment, this item of information is determined by virtue of the following topology determination process:
      • 1. Partitioning of the nodes into two sets, the first termed the “set of parents” comprising the nodes which have at least one child and the other termed the “set of children” comprising the nodes which have no child.
      • 2. The node having the smallest physical address in the “set of parents” is taken into consideration.
      • 3. The nodes of the “set of children” having a physical address smaller than that of the node taken into consideration in point 2 are taken into consideration. Among them, only the N nodes having the largest addresses are taken into consideration, N being the number of ‘child’ ports of the node of point 2. The ‘child’ ports of the node of point 2 are associated in the order of their ascending numbers with the child nodes determined in the previous sentence, likewise taken in the order of their ascending physical addresses.
      • 4. Elimination of the “set of parents” of the node taken into account in point 2, and transfer to the “set of children”. Elimination of the child nodes of this node from the “set of children”.
      • 5. As long as the “set of parents” is not empty, repeat the steps in order starting from point 2.
  • This process is illustrated by the flowchart of FIG. 2 and is based on the process for allocating the physical addresses. Indeed, according to this process, the physical address allocated to a node is necessarily larger than that of the ‘child’ nodes which are attached thereto, these ‘child’ nodes sending their autoidentification packets before the ‘father’ node to which they are connected. Only the number of nodes corresponding to the number of ports to be associated is taken into account since there may be nodes with a smaller address which are not directly connected to the ‘father’ node, but to one of the ‘child’ nodes. Moreover, the order in which the ports of the ‘father’ node are considered during autoidentification is repeated when associating a port with a child node.
  • Table 2 indicates for the network of FIG. 1 the iterations of the process for determining the topology:
    TABLE 2
    Set of Set of
    Description parents children Results
    Start 3, 5 0, 1, 2, 4
    The parent with the smallest address 5 0, 3, 4 Node 1 is connected to port 0 of node 3.
    is 3. 3 has two children. The two Node 2 is connected to port 2 of node 3.
    largest children with an address less
    than 3 are 2 and 1.
    The parent with the smallest address — — Node 0 is connected to port 0 of node 5.
    is 5. 5 has three children. The three Node 3 is connected to port 1 of node 5.
    largest children with an address less Node 4 is connected to port 3 of node 5.
    than 5 are 4, 3 and 0.
    The “set of parents” is empty; the
    connection tree is established.
  • Following a reinitialization of the bus, the three processes mentioned above are implemented. The topology of the bus, as defined in the two tables above and represented by FIG. 1, is therefore available.
  • According to the invention, the table of correspondence of the physical addresses of the nodes before and after initialization is established.
  • The information known at this instant by the node implementing the process is as follows:
      • the topology before and after reinitialization,
      • the old and the new physical address of the node which will implement the process described below.
  • It should be observed that the shifting of a node gives rise to two reinitializations, one related to the disconnection of the node, the other to the connection for example to another location. It should also be observed that the connected or disconnected node may itself already be connected to other nodes belonging for example initially to another network. We then speak of connection or disconnection of a branch.
  • For each port, the following cases may arise:
      • a node with address X was connected to the port before reinitialization, a node with address Y is connected after reinitialization: the new address of the node X is Y;
      • the node with address X attached to the port before reinitialization has disappeared from the network, as have all the ‘child’ nodes of the node X;
      • the node with address Y has been attached to the port since reinitialization. ‘Child’ nodes are, as appropriate, connected to the node Y.
  • The process for establishing the correspondence table checks each of these cases for each port of each node. This process is illustrated by the flowchart of FIG. 3. It comprises a procedure, termed ‘ProcessNode’, which must be supplied with two parameters: ‘Old’ and ‘New’, which are respectively the old and new addresses of the node implementing the process. When either one respectively of these variables has the value NOADDRESS, this indicates, if ‘Old’ possesses this value that the node taken into consideration did not exist in the old topology, and if ‘New’ possesses this value that the node no longer exists in the new topology.
  • The procedure is called a first time by a node, the root according to the present illustrative embodiment. The procedure is recursive and calls itself until the desired table of correspondences is determined.
  • Moreover, two sets of nodes are considered, namely the set of added nodes, and the set of deleted nodes which will contain respectively the old addresses of the nodes disconnected with respect to the old topology and the new addresses of the newly detected nodes. Stated otherwise, these sets contain all the nodes having no corresponding counterpart in the ‘past’ or the ‘future’, with respect to the reinitialization.
  • The process of establishing the correspondence table is as follows:
      • 1. If “Old” is different from NOADDRESS, go to step 6.
      • 2. Take the first port of the node identified by the ‘New’ parameter.
      • 3. If a ‘child’ node (with an address Z) is connected to this port, add the ‘New’ address to the set of added nodes and call ProcessNode (NOADDRESS, Z).
      • 4. Repeat step 3 for all the ports of the node.
      • 5. Go to step 13.
      • 6. Put the relation between “Old” and “New” in the correspondence table.
      • 7. Take the first port of the node considered.
      • 8. If no ‘child’ node is connected to this port, neither in the old topology nor in the new topology, go to step 12.
      • 9. If no ‘child’ node is connected to this port in the new topology, but a node was connected thereto in the old topology, add the old number of the ‘child’ node together with its children to the “eliminated node” set and go to step 12.
      • 10. If no ‘child’ node was connected to this port in the old topology, add the new number (Z) of the child node to the set of added nodes and call ProcessNode (NOADDRESS, Z).
      • 11. Otherwise (that is to say if a child node was and still is connected to the port), call ProcessNode (old number of the child node, new number of the child node).
      • 12. Process the other ports of the node (from step 8).
      • 13. End of processing.
  • Steps 1 to 5 correspond to the processing of a node which has newly appeared in the network (the old address has the value NOADDRESS). Steps 6 to 13 correspond to the processing of a node possessing an old and a new address. The ProcessNode procedure is never called when a node has disappeared from the network: this is a particular case processed at step 9 level.
  • A change of topology of the network of FIG. 1 will be taken by way of example to illustrate the above process. For the example to be complete, two changes (one connection and one disconnection of nodes) will be introduced here artificially, although in practice this would give rise to two separate reinitializations. The two modifications are chosen in such a way as to avoid the particular cases in which the process would fail.
  • Represented in FIG. 1 is the network before reinitialization. Ports with numbers 0, 1, 3 of the root node A are linked to ports 2, 1, 1 of the respective nodes B, C, D. B and D have no children, whereas ports 0, 2 of C are linked respectively to the respective ports 0, 0 of nodes E, F.
  • Node A is chosen as root node as regards the allocating of addresses.
  • Node F is deleted and node G is introduced, linked by its port number 0 to port number 0 of node D.
  • Represented in FIG. 4 is the network after reinitialization. Ports 0, 1 of node C are linked respectively to ports 0, 1 of respective nodes E and A. E has no children whereas A has two children B and D. Ports 0, 3 of A are linked to ports 2, 1 of nodes B, D. B has no children whereas port 0 of D is linked to port 0 of node G.
  • Node C is chosen as root node as regards the allocating of addresses.
  • Within the framework of the example, it is assumed that the process for establishing the table of correspondences is implemented by node A. It is implemented by each apparatus of the network desiring to establish the correspondence table, given that the presence within the network of nodes which do not use the process does not disturb the running of the latter.
  • Table 3 below is a table translating the implementation of the process for establishing the table of correspondence for the numbers of the nodes giving the state of the nodes after reinitialization, their old and new addresses as well as the old addresses of the nodes eliminated from the network and the new addresses of the nodes added. The level of recursivity corresponds to the number of calls of the ProcessNode procedure by itself.
  • Node A knows that it was the node with address 5 before reinitialization and that it has become node 4 thereafter, starts the process by calling the ProcessNode procedure (5, 4):
    TABLE 3
    Node processed,
    Level of
    recursivity, Step Correspondence Node Node
    of the process Comments table added eliminated
    A, 0 Call ProcessNode(5, 4)
    A, 1, 1 True, then go to step 6
    A, 1, 6 We know that node 5 has become node 4 5->4
    A, 1, 7 The first port of node A bears the number 0 5->4
    A, 1, 8 Test false 5->4
    A, 1, 9 Test false 5->4
    A, 1, 10 Test false 5->4
    A, 1, 11 In port 0, the old address of the node 5->4
    was 0 and the new address is 1: call
    ProcessNode(0, 1)
    B, 2, 1 True, hence go to step 6 5->4
    B, 2, 6 We know that node 0 has become node 1 5->4, 0->1
    B, 2, 7 The first port of B is 0 5->4, 0->1
    B, 2, 8 True, hence go to step 12 5->4, 0->1
    B, 2, 12 True, the next port of B is port 1, go to step 8 5->4, 0->1
    B, 2, 8 True, hence go to step 12 5->4, 0->1
    B, 2, 12 True, the next port is port 2, go to step 8 5->4, 0->1
    B, 2, 8 True, go to step 12 5->4, 0->1
    B, 2, 12 False 5->4, 0->1
    B, 2, 13 All the ‘child’ nodes of node B have been 5->4, 0->1
    processed, return to A, 1, 12
    A, 1, 12 True, the second port of node A bears the 5->4, 0->1
    number 1, go to point 8
    A, 1, 8 False 5->4, 0->1
    A, 1, 9 False 5->4, 0->1
    A, 1, 10 False 5->4, 0->1
    A, 1, 11 In port 1, the old address of the node 5->4, 0->1
    was 3 and the new address is 5: call
    ProcessNode(3, 5)
    C, 2, 1 True, go to step 6 5->4, 0->1
    C, 2, 6 We know that node 3 has become node 5 5->4, 0->1, 3->5
    C, 2, 7 The first port of C is 0 5->4, 0->1, 3->5
    C, 2, 8 False 5->4, 0->1, 3->5
    C, 2, 9 False 5->4, 0->1, 3->5
    C, 2, 10 False 5->4, 0->1, 3->5
    C, 2, 11 In port 0, the old address of the node was 1 5->4, 0->1, 3->5
    and the new address is 0: call ProcessNode(1,
    0)
    E, 3, 1 True, go to step 6 5->4, 0->1, 3->5
    E, 3, 6 We know that node 1 has become node 0 5->4, 0->1, 3->5,
    1->0
    E, 3, 7 The first port of node E is 0 5->4, 0->1, 3->5,
    1->0
    E, 3, 8 True, go to step 12 5->4, 0->1, 3->5,
    1->0
    E, 3, 12 True, the second port of E is 1, go to step 8 5->4, 0->1, 3->5,
    1->0
    E, 3, 8 True, go to step 12 5->4, 0->1, 3->5,
    1->0
    E, 3, 12 False 5->4, 0->1, 3->5,
    1->0
    E, 3, 13 All the child nodes of node E are processed, 5->4, 0->1, 3->5,
    return to point C, 2, 12 1->0
    C, 2, 12 True, the second port of C is 1, go to step 8 5->4, 0->1, 3->5,
    1->0
    C, 2, 8 True, go to step 12 5->4, 0->1, 3->5,
    1->0
    C, 2, 12 True, process port 2 and go to step 8 5->4, 0->1, 3->5,
    1->0
    C, 2, 8 False 5->4, 0->1, 3->5,
    1->0
    C, 2, 9 True, there was a node with address 2 in 5->4, 0->1, 3->5, 2
    port 2 of node C before reinitialization, there 1->0
    is no longer one in this port after
    reinitialization, hence this node as well as its
    child nodes are eliminated
    C, 2, 12 False 5->4, 0->1, 3->5, 2
    1->0
    C, 2 , 13 All the children of node C are processed, 5->4, 0->1, 3->5, 2
    return to step A, 1, 12 1->0
    A, 1, 12 True, the third port of C is 2, go to step 8 5->4, 0->1, 3->5, 2
    1->0
    A, 1, 8 True, go to step 12 5->4, 0->1, 3->5, 2
    1->0
    A, 1, 12 True, the fourth port of C is 3, go to step 8 5->4, 0->1, 3->5, 2
    1->0
    A, 1, 8 False 5->4, 0->1, 3->5, 2
    1->0
    A, 1, 9 False 5->4, 0->1, 3->5, 2
    1->0
    A, 1, 10 False 5->4, 0->1, 3->5, 2
    1->0
    A, 1, 11 In port 3, the old address of node D 5->4, 0->1, 3->5, 2
    was 4 and the new address is 3: call 1->0
    ProcessNode(4, 3)
    D, 2, 1 True, go to step 6 5->4, 0->1, 3->5, 2
    1->0
    D, 2, 6 We know that the node with address 4 has 5->4, 0->1, 3->5, 2
    become the node with address 3 1->0, 4->3
    D, 2, 7 The first port is 0 5->4, 0->1, 3->5, 2
    1->0, 4->3
    D, 2, 8 False 5->4, 0->1, 3->5, 2
    1->0, 4->3
    D, 2, 9 False 5->4, 0->1, 3->5, 2
    1->0, 4->3
    D, 2, 10 True, we have detected that this node G 5->4, 0->1, 3->5, 2 2
    is new, we must therefore process all the 1->0, 4->3
    children of G so as to incorporate them into
    the set of added nodes: call
    ProcessNode(NOADDRESS, 2)
    G, 3, 1 False 5->4, 0->1, 3->5, 2 2
    1->0, 4->3
    G, 3, 2 The first port of G is 0 5->4, 0->1, 3->5, 2 2
    1->0, 4->3
    G, 3, 3 False 5->4, 0->1, 3->5, 2 2
    1->0, 4->3
    G, 3, 4 False 5->4, 0->1, 3->5, 2 2
    1->0, 4->3
    G, 3, 5 Go to step 13 5->4, 0->1, 3->5, 2 2
    1->0, 4->3
    G, 3, 13 All the child nodes of node G are processed, 5->4, 0->1, 3->5, 2 2
    return to step D, 2, 11 1->0, 4->3
    D, 2, 11 False 5->4, 0->1, 3->5, 2 2
    1->0, 4->3
    D, 2, 12 True, the second port of D is 1, go to step 8 5->4, 0->1, 3->5, 2 2
    1->0, 4->3
    D, 2, 8 True, go to step 12 5->4, 0->1, 3->5, 2 2
    1->0, 4->3
    D, 2, 12 False 5->4, 0->1, 3->5, 2 2
    1->0, 4->3
    D, 2, 13 All the child nodes of node D are processed, 5->4, 0->1, 3->5, 2 2
    return to A, 1, 12 1->0, 4->3
    A, 1, 12 False 5->4, 0->1, 3->5, 2 2
    1->0, 4->3
    A, 1, 13 All the child nodes of node A are processed, 5->4, 0->1, 3->5, 2 2
    the process has therefore terminated 1->0, 4->3
  • Thus, after implementing the above process, the results of which are made explicit in Table 3, we know that:
      • node F numbered 2 before reinitialization has been eliminated,
      • node G numbered 2 after reinitialization has been added,
      • a correspondence table indicating for each node other than F and G their number before and after reinitialization: for example, apparatus C was node 3 before reinitialization and has become node 5 thereafter.
  • FIG. 5 is a block diagram of a node 10 comprising a single port. This node is for example a ‘DVD’ type optical disk reader. Node 10 is connected to the serial 1394 bus bearing the reference 11 across a physical interface 12 and a linking circuit 13. The latter is linked to the internal parallel bus 14 of the node 10. A microprocessor 15 or equivalent device ensures the management of the node, which also comprises a circuit for managing the inputs/outputs 16, as well as a memory 17. These last three elements are also linked to the parallel bus 14.
  • Typically, the microprocessor takes on board the implementation of the autoidentification process, as well as of the processes for determining the topology of the network and for establishing the table of correspondences. The information regarding the topology before and after reinitialization, which is obtained according to the present example from the autoidentification packets, as well as the correspondence table are stored for example in the memory 17.

Claims (5)

1-7. (canceled).
8. Method for a node in a network of interconnected nodes to build the network topology, the network being organized in a tree, where each node has at least one communication port, each port being connected to a parent node, a child node or being unconnected, each node possessing a physical identifier from zero to the number of nodes in the network minus one, the root of the tree having the highest physical identifier, the node possessing for each node of the network its physical identifier, and its connection ports with the information whether each port is connected to a parent node, a child node or is unconnected, comprising at least the following steps:
separating the parent nodes consisting in nodes with at least one port connected to a child, from the child nodes consisting in nodes with no port connected to a child;
processing each parent node from the node having the smallest physical identifier to the root and attributing the child nodes with the smallest physical identifier to ports of the considered node connected to a child;
suppressing the attributed child nodes from the child nodes set; and
adding a processed parent node to the child nodes set if it has a parent port.
9. Method according to claim 8 wherein the network is an IEEE 1394 bus.
10. Apparatus to be connected to a network of interconnected apparatus wherein each apparatus comprises at least one connection port, the network being organized in a tree, each port being connected to a parent apparatus, a child apparatus or being unconnected, each apparatus in the network having a physical identifier from zero to the number of apparatus in the network minus one, the root of the tree having the highest physical identifier, the apparatus possessing for each node of the network its physical identifier, and its connection ports with the information whether each port is connected to a parent node, a childe node or is unconnected, the apparatus comprising:
means for separating the parent nodes consisting in nodes with at least one port connected to a child, from the child nodes consisting in nodes with no port connected to a child; and
means for processing parent nodes from node having the smallest physical identifier to the root and for each parent node, attributing the child nodes with the smallest physical identifier to ports of the considered node connected to a child and adding the processed parent node to the child nodes set if it has a parent port while suppressing the attributed child nodes from the child nodes set.
11. Apparatus according to claim 10, wherein the network is an IEEE 1394 bus.
US10/964,190 1998-05-26 2004-10-12 Method for identifying devices in a communication network and device for implementing said method Abandoned US20050047352A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US10/964,190 US20050047352A1 (en) 1998-05-26 2004-10-12 Method for identifying devices in a communication network and device for implementing said method

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
FR9806624 1998-05-26
FR9806624A FR2779301B1 (en) 1998-05-26 1998-05-26 METHOD FOR IDENTIFYING DEVICES IN A COMMUNICATION NETWORK AND APPARATUS FOR IMPLEMENTING
US09/317,796 US6870818B1 (en) 1998-05-26 1999-05-24 Method for identifying devices in a communication network and device for implementing said method
US10/964,190 US20050047352A1 (en) 1998-05-26 2004-10-12 Method for identifying devices in a communication network and device for implementing said method

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/317,796 Continuation US6870818B1 (en) 1998-05-26 1999-05-24 Method for identifying devices in a communication network and device for implementing said method

Publications (1)

Publication Number Publication Date
US20050047352A1 true US20050047352A1 (en) 2005-03-03

Family

ID=9526729

Family Applications (2)

Application Number Title Priority Date Filing Date
US09/317,796 Expired - Lifetime US6870818B1 (en) 1998-05-26 1999-05-24 Method for identifying devices in a communication network and device for implementing said method
US10/964,190 Abandoned US20050047352A1 (en) 1998-05-26 2004-10-12 Method for identifying devices in a communication network and device for implementing said method

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09/317,796 Expired - Lifetime US6870818B1 (en) 1998-05-26 1999-05-24 Method for identifying devices in a communication network and device for implementing said method

Country Status (6)

Country Link
US (2) US6870818B1 (en)
EP (1) EP0961453B1 (en)
JP (1) JP2000083037A (en)
CN (1) CN1121107C (en)
DE (1) DE69937925T2 (en)
FR (1) FR2779301B1 (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050033894A1 (en) * 2002-01-25 2005-02-10 Dieter Haupt Physical layer circuit and interface circuit
US20060056318A1 (en) * 2004-09-16 2006-03-16 Samsung Electronics Co., Ltd Home network system using IEEE 1394 and node configuration method thereof
WO2007030195A2 (en) * 2005-09-06 2007-03-15 Motorola, Inc. Method and apparatus for removing phantom children in an ad-hoc communication system
EP2782294A1 (en) * 2013-03-18 2014-09-24 Fujitsu Limited Information processing apparatus and method for generating coupling information
US11528159B2 (en) * 2017-09-04 2022-12-13 Somfy Activites Sa Method of automatic configuration of network address of a communicating element forming part of a home-automation system, associated network interface, communicating element and home-automation system

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2779301B1 (en) * 1998-05-26 2000-07-21 Thomson Multimedia Sa METHOD FOR IDENTIFYING DEVICES IN A COMMUNICATION NETWORK AND APPARATUS FOR IMPLEMENTING
WO2000069123A1 (en) * 1999-05-11 2000-11-16 Sony Corporation Network connection recognizing method and network-connected terminal device
US7916723B2 (en) * 2000-03-03 2011-03-29 Adtran, Inc. Automatic network topology identification by nodes in the network
US7545755B2 (en) * 2000-03-03 2009-06-09 Adtran Inc. Routing switch detecting change in session identifier before reconfiguring routing table
JP2004514322A (en) * 2000-11-09 2004-05-13 コーニンクレッカ　フィリップス　エレクトロニクス　エヌ　ヴィ System and method for connecting a node to a network via a non-network compliant link
US7245632B2 (en) * 2001-08-10 2007-07-17 Sun Microsystems, Inc. External storage for modular computer systems
FR2828568A1 (en) 2001-08-10 2003-02-14 Thomson Licensing Sa Method for discovering a network topology following a network reset, i.e. for identifying other peripherals connected to a network, whereby each peripheral carries out network exploration as a function of an assigned parameter
JP3630418B2 (en) 2002-09-11 2005-03-16 三菱電機株式会社 Network communication equipment
FR2854016A1 (en) * 2003-04-17 2004-10-22 Thomson Licensing Sa Reset messages transmitting method for use in communication network, involves transmitting reset messages of one bus to another other bus, when number of nodes is changed and number of nodes is not increased or decreased
KR100526609B1 (en) * 2003-07-09 2005-11-08 삼성전자주식회사 Data transmission system, data transmission method, data processing device and pointer device
US7444396B2 (en) 2003-08-29 2008-10-28 Sun Microsystems, Inc. Transferring system identities
US7389411B2 (en) 2003-08-29 2008-06-17 Sun Microsystems, Inc. Secure transfer of host identities
JP4437832B2 (en) * 2005-02-23 2010-03-24 パイオニア株式会社 Information relay device, information relay method, information relay program, and information recording medium
JP4681472B2 (en) * 2006-02-24 2011-05-11 富士通株式会社 Topology information collection program, topology information collection device, and topology information collection method
US8040823B2 (en) * 2007-01-08 2011-10-18 Industrial Technology Research Institute Method and system for network data transmitting

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5394556A (en) * 1992-12-21 1995-02-28 Apple Computer, Inc. Method and apparatus for unique address assignment, node self-identification and topology mapping for a directed acyclic graph
US5724517A (en) * 1994-09-27 1998-03-03 International Business Machines Corporation Method for generating a topology map for a serial bus
US5784557A (en) * 1992-12-21 1998-07-21 Apple Computer, Inc. Method and apparatus for transforming an arbitrary topology collection of nodes into an acyclic directed graph
US5883621A (en) * 1996-06-21 1999-03-16 Sony Corporation Device control with topology map in a digital network
US6157972A (en) * 1997-12-05 2000-12-05 Texas Instruments Incorporated Apparatus and method for processing packetized information over a serial bus
US6199119B1 (en) * 1994-12-19 2001-03-06 Apple Computer, Inc. Method and apparatus for the addition and removal of nodes from a common interconnect
US6870818B1 (en) * 1998-05-26 2005-03-22 Thomson Licensing S.A. Method for identifying devices in a communication network and device for implementing said method

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2649574B1 (en) * 1989-07-04 1991-10-18 Rce Sa COMMUNICATION NETWORK BETWEEN USER EQUIPMENT
AU620994B2 (en) * 1989-07-12 1992-02-27 Digital Equipment Corporation Compressed prefix matching database searching
US5715475A (en) * 1994-12-29 1998-02-03 Intel Corporation Topological identification and initialization of a system for processing video information
US5764930A (en) * 1996-04-01 1998-06-09 Apple Computer, Inc. Method and apparatus for providing reset transparency on a reconfigurable bus
US6065052A (en) * 1996-07-01 2000-05-16 Sun Microsystems, Inc. System for maintaining strongly sequentially ordered packet flow in a ring network system with busy and failed nodes
US6332159B1 (en) * 1996-12-04 2001-12-18 Canon Kabushiki Kaisha Data communication system, apparatus and controlling method thereof
US6298405B1 (en) * 1997-02-14 2001-10-02 Canon Kabushiki Kaisha Data communication system, printing system and data communication apparatus
US6298406B1 (en) * 1997-10-24 2001-10-02 Sony Corporation Method of and apparatus for detecting direction of reception of bus packets and controlling direction of transmission of bus packets within an IEEE 1394 serial bus node
US6160796A (en) * 1998-01-06 2000-12-12 Sony Corporation Of Japan Method and system for updating device identification and status information after a local bus reset within a home audio/video network
US6038625A (en) * 1998-01-06 2000-03-14 Sony Corporation Of Japan Method and system for providing a device identification mechanism within a consumer audio/video network
US6052750A (en) * 1998-01-06 2000-04-18 Sony Corporation Of Japan Home audio/video network for generating default control parameters for devices coupled to the network, and replacing updated control parameters therewith

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5394556A (en) * 1992-12-21 1995-02-28 Apple Computer, Inc. Method and apparatus for unique address assignment, node self-identification and topology mapping for a directed acyclic graph
US5784557A (en) * 1992-12-21 1998-07-21 Apple Computer, Inc. Method and apparatus for transforming an arbitrary topology collection of nodes into an acyclic directed graph
US5724517A (en) * 1994-09-27 1998-03-03 International Business Machines Corporation Method for generating a topology map for a serial bus
US6199119B1 (en) * 1994-12-19 2001-03-06 Apple Computer, Inc. Method and apparatus for the addition and removal of nodes from a common interconnect
US6954787B2 (en) * 1994-12-19 2005-10-11 Apple Computer, Inc. Method and apparatus for the addition and removal of nodes from a common interconnect
US5883621A (en) * 1996-06-21 1999-03-16 Sony Corporation Device control with topology map in a digital network
US6157972A (en) * 1997-12-05 2000-12-05 Texas Instruments Incorporated Apparatus and method for processing packetized information over a serial bus
US6870818B1 (en) * 1998-05-26 2005-03-22 Thomson Licensing S.A. Method for identifying devices in a communication network and device for implementing said method

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050033894A1 (en) * 2002-01-25 2005-02-10 Dieter Haupt Physical layer circuit and interface circuit
US7346073B2 (en) * 2002-01-25 2008-03-18 Thomson Licensing Physical layer circuit and interface circuit
US20060056318A1 (en) * 2004-09-16 2006-03-16 Samsung Electronics Co., Ltd Home network system using IEEE 1394 and node configuration method thereof
WO2007030195A2 (en) * 2005-09-06 2007-03-15 Motorola, Inc. Method and apparatus for removing phantom children in an ad-hoc communication system
US20070066308A1 (en) * 2005-09-06 2007-03-22 Oleg Andric Method and apparatus for removing phantom children in an ad-hoc communication system
WO2007030195A3 (en) * 2005-09-06 2007-07-12 Motorola Inc Method and apparatus for removing phantom children in an ad-hoc communication system
KR100941325B1 (en) * 2005-09-06 2010-02-11 모토로라 인코포레이티드 Method and apparatus for removing phantom children in an ad-hoc communication system
EP2782294A1 (en) * 2013-03-18 2014-09-24 Fujitsu Limited Information processing apparatus and method for generating coupling information
US9632962B2 (en) 2013-03-18 2017-04-25 Fujitsu Limited Information processing apparatus and method for generating coupling information
US11528159B2 (en) * 2017-09-04 2022-12-13 Somfy Activites Sa Method of automatic configuration of network address of a communicating element forming part of a home-automation system, associated network interface, communicating element and home-automation system

Also Published As

Publication number Publication date
FR2779301B1 (en) 2000-07-21
CN1237055A (en) 1999-12-01
CN1121107C (en) 2003-09-10
JP2000083037A (en) 2000-03-21
DE69937925T2 (en) 2009-01-02
US6870818B1 (en) 2005-03-22
EP0961453A1 (en) 1999-12-01
EP0961453B1 (en) 2008-01-09
FR2779301A1 (en) 1999-12-03
DE69937925D1 (en) 2008-02-21

Similar Documents

Publication Publication Date Title
US6870818B1 (en) Method for identifying devices in a communication network and device for implementing said method
JP2713226B2 (en) Automatic IP address generation method in network
CN1402480B (en) Method for managing address of medium access control bridge, and said bridge
US8018861B2 (en) Method and device for allocating at least one routing identifier to at least one bridge in a network
CN110545229B (en) Message sending method and device in VXLAN axis networking mode
JP2000165417A (en) Network configuration method and network management node
US6310858B1 (en) Frame relay system
US7197039B2 (en) Bridge apparatus with entries reduced in filtering database and network using the same
AU611068B2 (en) System for internetwork communication between local area networks
US20020152341A1 (en) Method and system for generating multiple self-ID packets on the 1394 bus using a standard PHY chip
US10187365B2 (en) Method for exchanging numerical data frames and associated communication system
CN115242839B (en) Method and device for cascade data transmission of Internet of things, electronic equipment and storage medium
US20190268239A1 (en) Bgp logical topology generation method, and device
CN113595937B (en) Message sending method and device and switching network chip
US11108680B2 (en) Dynamic routing method in a network of connected objects
US20030210709A1 (en) Method and apparatus for transmitting to an upper layer of information included in a packet
JP2763394B2 (en) Communication control device
JP2004072160A (en) Switching method and apparatus, and computer program
US20090031045A1 (en) Information relay device, information relay method, information relay program and information recording medium
JPH0353631A (en) Communication frame repeater
JP3683411B2 (en) Virtual LAN system and network management method applied to virtual LAN system
JP4611974B2 (en) Method for transferring an IEEE 1394 bus reinitialization message and apparatus for performing such a method
CN114915576A (en) Method and system for identifying terminal equipment at router
CN113645008A (en) Message protocol overtime retransmission method and system based on linked list
JPH06169309A (en) Confirmation system for circuit setting information of multiplex system

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION