EP1336278A1 - System and method for connecting nodes to a network via non-network compliant link - Google Patents

System and method for connecting nodes to a network via non-network compliant link

Info

Publication number
EP1336278A1
EP1336278A1 EP01994004A EP01994004A EP1336278A1 EP 1336278 A1 EP1336278 A1 EP 1336278A1 EP 01994004 A EP01994004 A EP 01994004A EP 01994004 A EP01994004 A EP 01994004A EP 1336278 A1 EP1336278 A1 EP 1336278A1
Authority
EP
European Patent Office
Prior art keywords
node
network
physical layer
nodes
standard physical
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.)
Withdrawn
Application number
EP01994004A
Other languages
German (de)
French (fr)
Inventor
Takashi Sato
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.)
Koninklijke Philips NV
Original Assignee
Koninklijke Philips Electronics NV
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 Koninklijke Philips Electronics NV filed Critical Koninklijke Philips Electronics NV
Publication of EP1336278A1 publication Critical patent/EP1336278A1/en
Withdrawn legal-status Critical Current

Links

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/40097—Interconnection with other networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • 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
    • 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

Definitions

  • the present invention is related to the invention disclosed in United States Patent Application Serial Number [Docket No. PHA 23414] filed June 8, 1998, entitled “METHOD OF CONNECTING MULTIPLE WIRELESS DEVICES TO A NETWORK.”
  • This patent application is commonly assigned to the assignee of the present invention.
  • the disclosure of this related patent application is hereby incorporated herein by reference for all purposes as if fully set forth herein.
  • the present invention is directed to a system and method for connecting nodes to a communications network, and more specifically, to a system and method for connecting nodes via non-network compliant links without using a bridge concept. It is a common practice to connect electronic devices in a network.
  • a typical example is a network of computers in which each computer in the network is capable of communicating with the other computers in the network.
  • Network devices usually communicate over an information bus that conforms to an established standard such as the IEEE 1394 standard.
  • the IEEE 1394 standard is a particularly useful standard for high performance bus interconnection of computer peripherals and consumer electronics. It is also useful for transmission of high-speed digital video data.
  • a bridge circuit is an electronic circuit that is capable of connecting two or more electronic buses. If a bridge circuit is capable of connecting only two electronic buses, it is called a "two portal bridge.” In order for electronic devices or applications to communicate across bridges, they must communicate according to the appropriate bridge protocol. Electronic devices or applications that are capable of communicating across bridges are said to be “bridge aware.” Electronic devices that are not “bridge aware” will not work across a bridge except as a simple responder device. Older electronic devices that are not “bridge aware” are sometimes referred to as "legacy" devices.
  • the present invention generally comprises a system and method for connecting network nodes via non-network compliant links without using a bridge concept.
  • the system of the invention comprises a network standard physical layer in a first node that is capable of representing more than one node, and at least one non-network compliant node that is capable of sending instructions to the network standard physical layer in the first node to tell the network standard physical layer how many nodes to represent.
  • Appendix means any device, system or part thereof that controls at least one operation, such a device may be implemented in hardware, firmware or software, or some combination of at least two of the same. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.
  • FIG. 1 illustrates a block diagram of an exemplary network communications system
  • Fig. 2 illustrates a block diagram of two nodes of the exemplary network communication system shown in Fig. 1;
  • FIG. 3 illustrates a block diagram of an exemplary network communications system that communicates in accordance with an advantageous embodiment of the present invention
  • Fig. 4 illustrates a block diagram of two nodes of the exemplary network communications systems shown in Fig. 3;
  • Fig. 5 illustrates a set of three self identification packets showing the format of self identification packets that are used by an IEEE 1394 Standard communications bus;
  • Fig. 6 illustrates a chart that identifies fields in the self identification packets shown in Fig. 5;
  • Fig. 7 illustrates a first exemplary network communications system having an exemplary bus topology
  • Fig. 8 illustrates a second exemplary network communications system having a node that is capable of programming an IEEE 1394 Standard physical layer to represent three nodes;
  • Fig. 9 illustrates a self identification packet for each of the three nodes represented by the node in Fig. 8 that is capable of programming an IEEE 1394 Standard physical layer;
  • Fig. 10 illustrates a third exemplary network communications system having a node that is capable of programming an IEEE 1394 Standard physical layer to represent three nodes;
  • Fig. 11 illustrates a self identification packet for each of the three nodes represented by the node in Fig. 10 that is capable of programming an IEEE 1394 Standard physical layer;
  • Fig. 12 illustrates a fourth exemplary network communications system having
  • Fig. 13 illustrates a self identification packet the node in Fig. 12 that represents no additional nodes
  • Fig. 14 is a flow diagram illustrating the operation of an advantageous embodiment of the present invention in an exemplary network communications system.
  • Figs. 1 through 14 discussed below, and the various embodiments set forth in this patent document to describe the principles of the system and method of the present invention are by way of illustration only and should not be construed in any way to limit the scope of the invention.
  • the present invention is integrated into, and is used in connection with, a network communications system.
  • the present invention will be described as a system and method for connecting network nodes via non-network compliant links without using a bridge concept. It is important to realize that the method of the present invention is not limited to a network communications system. Those skilled in the art will readily understand that the principles of the present invention may also be successfully applied in any similar type of network system.
  • a network communications system is employed for illustration purposes only.
  • Fig. 1 illustrates a block diagram of an exemplary communications system 100.
  • Communications system 100 comprises network 105 (network "X"), which in turn comprises a plurality of network nodes 110 and node 120 (node “A” or “bridge portal”).
  • Communications system 100 also comprises node 130 (node “B”), node 140 (node “C”), node 150 (node “D”), and node 160 (node “E”).
  • a “node” in communications system 100 is defined to be any device that is capable of producing, processing, utilizing, or transmitting information.
  • Node 130 is capable of wireless communication with node 140, and with node 150, and with node 160.
  • Wireless communication in communications system 100 is defined to be the communication of information through space (i.e., not through wires or similar conduits) by an energy propagation mode (e.g., radio frequency (RF), infrared (IR), sonic energy) that is capable of carrying the information being communicated.
  • Node 140, node 150, and node 160 each include, in addition to an information processing device, a transceiver (not shown) for wireless communication with node 130.
  • Node 140, node 150, and node 160 are each capable of coordinating the local flow of information between their respective information processing devices and their respective transceivers.
  • node 140, node 150, and node 160 each include, in addition to a transceiver, a transducer (not shown) for propagating the energy of the energy propagation mode used for wireless communication with node 130.
  • node 130 includes, in addition to an information processing device, a transceiver (shown in Fig. 2 as transceiver 210) for wireless communication with the transceivers of node 140, node 150, and node 160.
  • transceiver 2 shown in Fig. 2 as transceiver 210
  • transducer 2 for propagating the energy of the energy propagation mode used for wireless communication with node 140, node 150, and node 160.
  • Node 130, node 140, node 150, and node 160 each communicate using the same wireless protocol.
  • the nodes of network 105 (network "X") each communicate using the same network protocol.
  • the network protocol of network 105 can be any standardized network protocol, the network protocol that is most commonly used is the IEEE 1394 standard.
  • the IEEE 1394 standard is described in detail in the publication IEEE Standard 1394-1995, "IEEE Standard for a High Performance Serial Bus” dated August 30, 1996, which is hereby incorporated into this document by reference for all purposes.
  • wireless protocol nodes 130, 140, 150, and 160 are able to communicate using the network protocol used by network 105, then the wireless protocol nodes 130, 140, 150, and 160 are said to be "network compliant.” If the wireless protocol nodes 130, 140, 150, and 160 are not able to communicate using the network protocol used by network 105, then the wireless protocol nodes 130, 140, 150, and 160, are said to be "non-network compliant" and the links between wireless protocol node 130 and wireless protocol nodes 140, 150, and 160, are said to be "non-network-compliant" links.
  • the network protocol of network 105 is the IEEE 1394 standard, and that wireless protocol nodes 130, 140, 150, and 160, are non-network compliant nodes.
  • the information In order for information to be communicated from node 130 (a non-network compliant node) to network 105, the information must be converted from the wireless protocol of node 130 to the network protocol of network 105.
  • Fig. 2 illustrates a block diagram of node 120 and node 130.
  • Node 130 comprises wireless link 205 and transceiver 210.
  • Transceiver 210 comprises a conventional transceiver that is well known in the art. The type of transceiver 210 that is chosen depends upon the energy propagation mode that is chosen for wireless communication.
  • Wireless link 205 comprises a conventional wireless link that is well known in the art. Wireless link 205 converts information signals that are received from nodes 140, 150, and 160 to a format that is compatible with node 120. Wireless link 205 also converts signals received from node 120 to a format that is compatible with transceiver 220 and nodes 140, 150, and 160. Wireless link 205 also exchanges timing and control signals with node 120 to coordinate the transfer of information to and from nodes 140, 150, and 160. Wireless link 205 is coupled to controller 215. Controller 215 executes software instructions contained in memory 220 to perform the format conversions.
  • Node 120 comprises 1394.1 Standard physical layer 225 and 1394.1 Standard link layer 230.
  • Physical layer 225 and link layer 230 are functional logic elements the operation of which are described in IEEE publication P1394.1 Draft 0.11 entitled “P1394.1 Draft Standard for High Performance Serial Bus Bridges” dated September 24, 2000, which is hereby incorporated into this document by reference for all purposes.
  • Physical layer 225 comprises exemplary bus ports 245, 250, and 255 for physical connection to a common bus on which 1394 Standard nodes communicate (i.e., network nodes 110). Physical layer 225 also ensures that only one node at a time transmits information on the common bus. Physical layer 225 also converts the format of information received from link layer 230 to the 1394 Standard. Link layer 230 formats communications received from physical layer 225 into a format that can be received by wireless link layer 205. Link layer 230 is coupled to controller 235. Controller 235 executes software instructions contained in memory 240 to perform the format conversions. To be compatible with network 105 it is necessary for node 120 to support the common network physical layer.
  • Node 120 identifies itself to network 105 by broadcasting a set of self identification ("Self ID") packets after each bus reset. A bus reset occurs after each change in network topology.
  • Physical layer 225 is implemented in hardware in order to carry out operations in both the analog and the digital domain. During the identification process physical layer 225 broadcasts a set of Self ID packets (one to four packets, depending upon the number of its bus ports) that associates physical layer 225 with a single node. In other words, physical layer 225 can represent only one node. With respect to communications system 100, node 120 can represent only one of the wireless nodes 140, 150, and 160 to network 105.
  • Fig. 3 illustrates a block diagram of an exemplary network communications system 300 that communicates in accordance with an advantageous embodiment of the present invention.
  • the present invention comprises device 320 (device "A") having a new type of programmable 1394 Standard physical layer 425 (shown in Fig. 4) that can represent more than one node.
  • the new type of 1394 Standard physical layer 425 broadcasts more than one set of Self ID packets.
  • Each set of Self ID packets represents a single node.
  • Physical layer 425 of the present invention may represent a fixed number of nodes or a variable number of nodes.
  • the present invention also comprises device 330 (device "B").
  • device 330 is a wireless device. It is understood, however, that in other advantageous embodiments of the present invention, device 330 may be a wired device.
  • Device 330 is capable of sending instructions to physical layer 425 of device 320 to set the number of nodes that physical layer 425 represents.
  • device 330 comprises controller 415 and memory 420. Controller 415 is capable of executing computer instructions stored in memory 420 to send instructions to physical layer 425 of device 320 to set the number of nodes that physical layer 425 represents.
  • Device 330 is capable of causing physical layer 425 to represent any number of nodes (up to a maximum of sixty three (63) nodes).
  • device 330 sends instructions to device 320 to cause physical layer 425 to represent three nodes instead of one node.
  • Physical layer 425 generates multiple Self ID packets by incrementing the physical identification number in a first Self ID packet to create a second Self ID packet, a third Self ID packet, and so on. As will be explained more fully below, physical layer 425 also makes necessary adjustments to other fields in the Self ID packets, such as port status fields.
  • wireless device 330 detects wireless nodes 140, 150, and 160.
  • Wireless device 330 sends instructions to physical layer 425 of device 320 to create three nodes (node 340 identified as "P", node 350 identified as "Q”, and node 360 identified as "R") instead of one node (node 120).
  • Node 340 represents node 140
  • node 350 represents node 150
  • node 360 represents node 160. It therefore appears to network 105 that there are three nodes (node 340, node 350, and node 360) associated with device 320.
  • Programmable link layer 430 of device 320 can receive all the packets that are to be delivered to nodes 340, 350, and 360.
  • programmable link layer 430 receives the request packets via programmable physical layer 425.
  • Wireless device 330 receives those packets and forwards them to the corresponding nodes 140, 150, or 160.
  • the response is returned to device 320.
  • Programmable link layer 430 of device 320 generates the response packet to the requester, with the corresponding source node identification (i.e., node 340, node 350, or node 360) in the packet. If node 140, node 150, or node 160 do not communicate using the same protocol as network 105, device 330 applies the necessary protocol conversion to communications between device 320 and device 330.
  • device 320 behaves as if there were three nodes in its place (i.e., node 140, node 150, and node 160).
  • Legacy devices and other devices on network 105 can communicate with any one of the nodes 140, 150, or 160 via a non-network compliant link (e.g., a wireless link).
  • a non-network compliant link e.g., a wireless link.
  • device 320 comprises controller 435 and memory 440 and device 330 comprises controller 415 and memory 420.
  • controller 415 and memory 420 in device 330 is capable of performing its function plus the function of controller 435 and memory 440 in device 320.
  • controller 435 and memory 440 in device 320 is capable of performing its function plus the function of controller 415 and memory 420 in device 330.
  • Fig. 5 illustrates three self identification (Self ID) packets showing the format of self identification packets that are used by an IEEE 1394 Standard communications bus.
  • Self ID packet 510 is designated as "SELF ID PACKET NUMBER 0."
  • Self ID packet 520 is designated as “SELF ID PACKET NUMBER 1.”
  • Self ID packet 530 is designated as "SELF ID PACKET NUMBER 2.”
  • the chart in Fig. 6 identifies some of the fields that are contained within the self identification packets 510, 520, and 530.
  • the designation "phy_ID” is the physical node identifier of the node
  • the designation "sp” is the speed capability of the node
  • the designation "pwr” is the power class of the node
  • the designations "pO” through “pi 5" identify the port connection status for each of the ports connected to the physical node.
  • the packets each consist of sixty four (64) bits.
  • the second thirty two (32) bits are set to be the logical inverse of the first thirty two (32) bits.
  • the second set of thirty two (32) bits are labeled "logical inverse of first quadlet” in Fig. 5. If the first thirty two (32) bits do not match the complement of the second thirty two (32) bits, the entire packet is ignored.
  • FIG. 7 illustrates a first exemplary network communications system having an exemplary bus topology.
  • Each circle in Fig. 7 represents a node and the number within each circle represents the physical identifier of the node.
  • the physical identifier for node 700 is the number 0.
  • the root node i.e., the highest node in the network
  • node 708 and its physical identifier is the number 8.
  • a node that has another node directly beneath it is referred to as a "parent" node.
  • the node directly beneath a parent node is referred to as a "child" node.
  • the physical identifiers are assigned so that a parent node sends out a Self ID packet after all of its children nodes have finished sending a Self ID packet with a unique physical identifier.
  • Each of the nodes in the network shown in Fig. 7 is a physical node.
  • Fig. 8 illustrates a second exemplary network communications system comprising node 806 that is capable of programming an IEEE 1394 Standard physical layer in accordance with the principles of the present invention.
  • Node 806 depends from node 808.
  • Node 808 comprises a programmable 1394 Standard physical layer and a programmable 1394 link layer of the type shown in node 320 of Fig. 4.
  • Node 806 comprises controller 415 and memory 420 of the type shown in node 330 of Fig. 4.
  • Controller 415 of node 806 is capable of executing computer instructions stored in memory 420 to send instructions to physical layer 425 of node 808 to set the number of nodes that physical layer 425 represents.
  • Node 806 can have any number of physical ports up to twenty six (26) ports.
  • node 806 has only two (2) physical ports.
  • Node 806 represents three active nodes. They are node 804 ("node 4"), node 805 ("node 5"), node 806 ("node 6").
  • Node 806 has two physical ports and one virtual port.
  • Node 804 and node 805 have only virtual ports.
  • node 806 sends one self ID packet for each node that it represents.
  • node 806 generates and sends three sets of self ID packets.
  • Self ID packet number "0" for virtual node 804, and for virtual node 805, and for node 806 are shown in Fig. 9.
  • Self ID packet 910 is designated as "SELF ID PACKET NUMBER 0" for node 804.
  • Self ID packet 920 is designated as "SELF ID PACKET NUMBER 0" for node 805.
  • Self ID packet 930 is designated as "SELF ID PACKET NUMBER 0" for node 806.
  • the topology of the three nodes 804, 805, and 806 in this example is shown as a daisy chain. It is understood, however, that the nodes may have any topology supported by the IEEE 1394 Standard as long as the Self ID packets represent that topology.
  • node 806 When it is ' the turn of node 806 to send out a Self ID packet, node 806 starts by sending a virtual Self ID packet for "node 4" (node 804). This is because the last observed Self ID was for "node 3" (node 803).
  • the Self ID packet 910 for node 804 has the phy_ID field set equal to four (4) and "pO" port connect status is set equal to "10b" (one zero binary). As shown in the chart in Fig. 6, this means that node 804 is active and is connected to a parent node (i.e., node 805).
  • Node 806 then sends a virtual Self ID packet for "node 5" (node 805).
  • the Self ID packet 920 for node 805 has the phy_ID field set equal to five (5).
  • the phy_ID field has been incremented by one to change the phy_ID field from four to five.
  • the "pO" port connect status is set equal to "10b" (one zero binary) to indicate that node 805 is active and is connected to a parent node (i.e., node 806).
  • the "pi " port connect status is set equal to "1 lb" (one one binary) to indicate that node 805 is also active and connected to a child node (i.e. node 804).
  • Node 806 is capable of repeating the process by incrementing the phy_ID field for each successive node and sending a Self ID packet for that node.
  • n there will be (n-2) such packets where "n" is the number of nodes that node 806 represents. In this example, the value of "n" is three. Therefore, only one Self ID packet is sent out (i.e., the packet for node 805).
  • node 806 sends out a Self ID packet for the last node that node 806 represents (i.e., node 806 itself).
  • the Self ID packet 930 for node 806 has the phy_ID field set equal to six (6).
  • the phy_ID field has been incremented by one to change the phy_ID field from five to six.
  • the "pO" port connect status is set equal to "10b" (one zero binary) to indicate that node 806 is active and is connected to a parent node (i.e., node 808).
  • the "pi" port connect status is set equal to "01b" (zero one binary) to indicate that port one is not active (i.e., connected to nothing).
  • the "p2" port connect status is set equal to "1 lb" (one one binary) to indicate that node 806 is also active and connected to a child node (i.e. node 805).
  • the "gap_count” field and the “sp” field are common to all of the Self ID packets.
  • the "pwr” field (the "power class” field) is set only for the last Self ID packet sent by node 806.
  • the "speed capability” field and the "power class” field represent the actual capability of the physical hardware layer.
  • Fig. 10 illustrates a third exemplary network communications system comprising node 1004 that is capable of programming an IEEE 1394 Standard physical layer in accordance with the principles of the present invention.
  • Node 1004 depends from node 1005.
  • Node 1005 comprises a programmable 1394 Standard physical layer and a programmable 1394 link layer of the type shown in node 320 of Fig. 4.
  • Node 1004 comprises controller 415 and memory 420 of the type shown in node 330 of Fig. 4.
  • Controller 415 of node 1004 is capable of executing computer instructions stored in memory 420 to send instructions to physical layer 425 of node 1005 to set the number of nodes that physical layer 425 represents.
  • Node 1004 can have any number of physical ports up to twenty six (26) ports. In this example, however, node 1004 has only two (2) physical ports. Node 1004 represents three active nodes. They are node 1002 ("node 2"), node 1003 ("node 3"), node 1004
  • Node 4" has two physical ports and one virtual port. Node 1002 and node 1003 have only virtual ports.
  • node 1004 sends one self ID packet for each node that it represents.
  • node 1004 generates and sends three sets of self ID packets.
  • Self ID packet number "0" for virtual node 1002, and for virtual node 1003, and for node 1004 are shown in Fig. 11.
  • Self ID packet 1110 is designated as "SELF ID PACKET NUMBER 0" for node 1002.
  • Self ID packet 1120 is designated as "SELF ID PACKET NUMBER 0" for node 1003.
  • Self ID packet 1130 is designated as "SELF ID PACKET NUMBER 0" for node 1004.
  • the topology of the three nodes 1002, 1003, and 1004, in this example is shown as a daisy chain. It is understood, however, that the nodes may have any topology supported by the IEEE 1394 Standard as long as the Self ID packets represent that topology.
  • node 1004 When it is the turn of node 1004 to send out a Self ID packet, node 1004 starts by sending a virtual Self ID packet for "node 2" (node 1002). This is because the last observed Self ID was for "node 1" (node 1001).
  • the Self ID packet 1110 for node 1002 has the phy_ID field set equal to two (2) and "pO" port connect status is set equal to "10b" (one zero binary). As shown in the chart in Fig. 6, this means that node 1002 is active and is connected to a parent node (i.e., node 1003). ' Node 1004 then sends a virtual Self ID packet for "node 3" (node 1003).
  • the Self ID packet 1120 for node 1003 has the phy_ID field set equal to three (3).
  • the phy_ID field has been incremented by one to change the phy D field from two to three.
  • the "pO" port connect status is set equal to "10b" (one zero binary) to indicate that node 1003 is active and is connected to a parent node (i.e., node 1004).
  • the "pi” port connect status is set equal to "1 lb" (one one binary) to indicate that node 1003 is also active and connected to a child node (i.e. node 1002).
  • Node 1004 is capable of repeating the process by incrementing the phy_ID field for each successive node and sending a Self ID packet for that node.
  • node 1004 sends out a Self ID packet for the last node that node 1004 represents (i.e., node 1004 itself).
  • the Self ID packet 1130 for node 1004 has the phy_ID field set equal to four (4).
  • the phyJD field has been incremented by one to change the phy_ID field from three to four.
  • the "pO" port connect status is set equal to "10b" (one zero binary) to indicate that node 1004 is active and is connected to a parent node (i.e., node 1005).
  • the "pi” port connect status is set equal to "1 lb” (one one binary) to indicate that port one is active and connected to a child node (i.e. node 1001).
  • the " ⁇ 2" port connect status is set equal to "1 lb” (one one binary) to indicate that node 1004 is active and connected to a child node (i.e. node 1003).
  • Fig. 12 illustrates a fourth exemplary network communications system comprising node 1202 that is capable of programming an IEEE 1394 Standard physical layer in accordance with the principles of the present invention.
  • Node 1202 depends from node 1203.
  • Node 1203 comprises a programmable 1394 Standard physical layer and a programmable 1394 link layer of the type shown in node 320 of Fig. 4.
  • Node 1202 comprises controller 415 and memory 420 of the type shown in node 330 of Fig. 4.
  • Controller 415 of node 1202 is capable of executing computer instructions stored in memory 420 to send instructions to physical layer 425 of node 1203 to set the number of nodes that physical layer 425 represents. This example illustrates how node 1202 may be set to represent zero (0) nodes. As shown in Fig.
  • the link-on bit (bit L) in self identification packet 1310 is set equal to zero.
  • the link-on bit When the link-on bit is set, the node has active link and transaction layers. Setting the link-on bit to zero disables the link-on bit so that node 1202 behaves as a repeater node.
  • the "pO" port connect status of node 1202 is set equal to "10b" (one zero binary) to indicate that node 1202 is active and is connected to a parent node (i.e., node 1203).
  • the "pi” port connect status is set equal to "lib” (one one binary) to indicate that node 1202 is active and connected to a child node (i.e. node 1201).
  • the "p2" port connect status is set equal to "01b" (zero one binary) to indicate that that port two is not active (i.e., connected to nothing).
  • Fig. 14 is a flow diagram illustrating the operation of an advantageous embodiment of the present invention in an exemplary network communications system.
  • the first step comprises providing a network standard physical layer that is capable of representing more than one mode (step 1410).
  • the network standard may comprise a 1394 Standard.
  • the next step comprises sending instructions to the network standard physical layer from at least one non-network compliant mode to set the number of modes that the network standard physical layer represents (step 1420).
  • the final step comprises representing that number of modes in the network standard physical layer (step 1430).

Abstract

For use in a network having multiple nodes, there is disclosed a system and method for connecting nodes to a network via non-network compliant links. The system comprises a network standard physical layer in a first node that is capable of representing more than one node, and at least one non-network compliant node that is capable of sending instructions to the network standard physical layer in the first node to tell the network standard physical layer how many nodes to represent. The system and method of the present invention provides at least one network compliant node that is capable of representing multiple non-network compliant nodes in the network.

Description

SYSTEM AND METHOD FOR CONNECTING NODES TO A NETWORK VIA NON-NETWORK COMPLIANT LINK
The present invention is related to the invention disclosed in United States Patent Application Serial Number [Docket No. PHA 23414] filed June 8, 1998, entitled "METHOD OF CONNECTING MULTIPLE WIRELESS DEVICES TO A NETWORK." This patent application is commonly assigned to the assignee of the present invention. The disclosure of this related patent application is hereby incorporated herein by reference for all purposes as if fully set forth herein.
The present invention is directed to a system and method for connecting nodes to a communications network, and more specifically, to a system and method for connecting nodes via non-network compliant links without using a bridge concept. It is a common practice to connect electronic devices in a network. A typical example is a network of computers in which each computer in the network is capable of communicating with the other computers in the network. Network devices usually communicate over an information bus that conforms to an established standard such as the IEEE 1394 standard. The IEEE 1394 standard is a particularly useful standard for high performance bus interconnection of computer peripherals and consumer electronics. It is also useful for transmission of high-speed digital video data.
A bridge circuit is an electronic circuit that is capable of connecting two or more electronic buses. If a bridge circuit is capable of connecting only two electronic buses, it is called a "two portal bridge." In order for electronic devices or applications to communicate across bridges, they must communicate according to the appropriate bridge protocol. Electronic devices or applications that are capable of communicating across bridges are said to be "bridge aware." Electronic devices that are not "bridge aware" will not work across a bridge except as a simple responder device. Older electronic devices that are not "bridge aware" are sometimes referred to as "legacy" devices.
As the use of a particular bridge standard becomes more widespread and a particular bridge technology matures, more devices will appear that have been designed to be "bridge aware" for that bridge technology. In the case of the IEEE 1394 communications bus, the IEEE 1394 technology is not yet fully matured. There are many existing devices that are not "bridge aware" for the IEEE 1394 communications bus. These devices will be in use and will be on the market for many years.
There is a need in the art for a system and method for providing technology that will permit a device that is not "bridge aware" to send signals across a boundary between two separate networks. Specifically, there is a need in the art for a system and method for connecting network nodes via non-network compliant links without using a bridge concept.
The present invention generally comprises a system and method for connecting network nodes via non-network compliant links without using a bridge concept.
In an advantageous embodiment of the present invention, the system of the invention comprises a network standard physical layer in a first node that is capable of representing more than one node, and at least one non-network compliant node that is capable of sending instructions to the network standard physical layer in the first node to tell the network standard physical layer how many nodes to represent.
It is a primary object of the present invention to provide a system and method for enabling non-network compliant devices to be connected to a network.
It is another object of the present invention to provide a network standard physical layer that is capable of representing more than one node.
It is an additional object of the present invention to provide a non-network compliant node that is capable of sending instructions to a network standard physical layer to tell the network standard physical layer how many nodes to represent.
It is another object of the present invention to provide a network compliant node that is capable of representing multiple non-network compliant nodes in the network.
The foregoing has outlined rather broadly the features and technical advantages of the present invention so that those skilled in the art may better understand the Detailed Description of the Invention that follows. Additional features and advantages of the invention will be described hereinafter that form the subject of the claims of the invention. Those skilled in the art should appreciate that they may readily use the conception and the specific embodiment disclosed as a basis for modifying or designing other structures for carrying out the same purposes of the present invention. Those skilled in the art should also realize that such equivalent constructions do not depart from the spirit and scope of the invention in its broadest form.
Before undertaking the Detailed Description of the Invention, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document: the terms "include" and "comprise" and derivatives thereof, mean inclusion without limitation; the term "or," is inclusive, meaning and/or; the phrases "associated with" and "associated therewith," as well as derivatives thereof, may mean to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, or the like; and the term "controller," "processor," or
"apparatus" means any device, system or part thereof that controls at least one operation, such a device may be implemented in hardware, firmware or software, or some combination of at least two of the same. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.
For a more complete understanding of the present invention, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, wherein like numbers designate like objects, and in which:
Fig. 1 illustrates a block diagram of an exemplary network communications system; Fig. 2 illustrates a block diagram of two nodes of the exemplary network communication system shown in Fig. 1;
Fig. 3 illustrates a block diagram of an exemplary network communications system that communicates in accordance with an advantageous embodiment of the present invention; Fig. 4 illustrates a block diagram of two nodes of the exemplary network communications systems shown in Fig. 3;
Fig. 5 illustrates a set of three self identification packets showing the format of self identification packets that are used by an IEEE 1394 Standard communications bus;
Fig. 6 illustrates a chart that identifies fields in the self identification packets shown in Fig. 5;
Fig. 7 illustrates a first exemplary network communications system having an exemplary bus topology; Fig. 8 illustrates a second exemplary network communications system having a node that is capable of programming an IEEE 1394 Standard physical layer to represent three nodes;
Fig. 9 illustrates a self identification packet for each of the three nodes represented by the node in Fig. 8 that is capable of programming an IEEE 1394 Standard physical layer;
Fig. 10 illustrates a third exemplary network communications system having a node that is capable of programming an IEEE 1394 Standard physical layer to represent three nodes; Fig. 11 illustrates a self identification packet for each of the three nodes represented by the node in Fig. 10 that is capable of programming an IEEE 1394 Standard physical layer;
Fig. 12 illustrates a fourth exemplary network communications system having
* a node that represents no additional nodes; Fig. 13 illustrates a self identification packet the node in Fig. 12 that represents no additional nodes; and
Fig. 14 is a flow diagram illustrating the operation of an advantageous embodiment of the present invention in an exemplary network communications system.
Figs. 1 through 14, discussed below, and the various embodiments set forth in this patent document to describe the principles of the system and method of the present invention are by way of illustration only and should not be construed in any way to limit the scope of the invention. In the descriptions of the advantageous embodiments that follow, the present invention is integrated into, and is used in connection with, a network communications system. The present invention will be described as a system and method for connecting network nodes via non-network compliant links without using a bridge concept. It is important to realize that the method of the present invention is not limited to a network communications system. Those skilled in the art will readily understand that the principles of the present invention may also be successfully applied in any similar type of network system. In the descriptions that follow, a network communications system is employed for illustration purposes only.
Fig. 1 illustrates a block diagram of an exemplary communications system 100. Communications system 100 comprises network 105 (network "X"), which in turn comprises a plurality of network nodes 110 and node 120 (node "A" or "bridge portal"). Communications system 100 also comprises node 130 (node "B"), node 140 (node "C"), node 150 (node "D"), and node 160 (node "E"). A "node" in communications system 100 is defined to be any device that is capable of producing, processing, utilizing, or transmitting information. Node 130 is capable of wireless communication with node 140, and with node 150, and with node 160. "Wireless communication" in communications system 100 is defined to be the communication of information through space (i.e., not through wires or similar conduits) by an energy propagation mode (e.g., radio frequency (RF), infrared (IR), sonic energy) that is capable of carrying the information being communicated. Node 140, node 150, and node 160 each include, in addition to an information processing device, a transceiver (not shown) for wireless communication with node 130. Node 140, node 150, and node 160 are each capable of coordinating the local flow of information between their respective information processing devices and their respective transceivers. In addition, node 140, node 150, and node 160 each include, in addition to a transceiver, a transducer (not shown) for propagating the energy of the energy propagation mode used for wireless communication with node 130.
Similarly, node 130 includes, in addition to an information processing device, a transceiver (shown in Fig. 2 as transceiver 210) for wireless communication with the transceivers of node 140, node 150, and node 160. Node 130 also includes a transducer (not shown) for propagating the energy of the energy propagation mode used for wireless communication with node 140, node 150, and node 160.
Node 130, node 140, node 150, and node 160 each communicate using the same wireless protocol. The nodes of network 105 (network "X") each communicate using the same network protocol. Although the network protocol of network 105 can be any standardized network protocol, the network protocol that is most commonly used is the IEEE 1394 standard. The IEEE 1394 standard is described in detail in the publication IEEE Standard 1394-1995, "IEEE Standard for a High Performance Serial Bus" dated August 30, 1996, which is hereby incorporated into this document by reference for all purposes.
If the wireless protocol nodes 130, 140, 150, and 160 are able to communicate using the network protocol used by network 105, then the wireless protocol nodes 130, 140, 150, and 160 are said to be "network compliant." If the wireless protocol nodes 130, 140, 150, and 160 are not able to communicate using the network protocol used by network 105, then the wireless protocol nodes 130, 140, 150, and 160, are said to be "non-network compliant" and the links between wireless protocol node 130 and wireless protocol nodes 140, 150, and 160, are said to be "non-network-compliant" links.
For purposes of describing the present invention, assume that the network protocol of network 105 is the IEEE 1394 standard, and that wireless protocol nodes 130, 140, 150, and 160, are non-network compliant nodes. In order for information to be communicated from node 130 (a non-network compliant node) to network 105, the information must be converted from the wireless protocol of node 130 to the network protocol of network 105.
Fig. 2 illustrates a block diagram of node 120 and node 130. Node 130 comprises wireless link 205 and transceiver 210. Transceiver 210 comprises a conventional transceiver that is well known in the art. The type of transceiver 210 that is chosen depends upon the energy propagation mode that is chosen for wireless communication. Wireless link 205 comprises a conventional wireless link that is well known in the art. Wireless link 205 converts information signals that are received from nodes 140, 150, and 160 to a format that is compatible with node 120. Wireless link 205 also converts signals received from node 120 to a format that is compatible with transceiver 220 and nodes 140, 150, and 160. Wireless link 205 also exchanges timing and control signals with node 120 to coordinate the transfer of information to and from nodes 140, 150, and 160. Wireless link 205 is coupled to controller 215. Controller 215 executes software instructions contained in memory 220 to perform the format conversions.
Node 120 comprises 1394.1 Standard physical layer 225 and 1394.1 Standard link layer 230. Physical layer 225 and link layer 230 are functional logic elements the operation of which are described in IEEE publication P1394.1 Draft 0.11 entitled "P1394.1 Draft Standard for High Performance Serial Bus Bridges" dated September 24, 2000, which is hereby incorporated into this document by reference for all purposes.
Physical layer 225 comprises exemplary bus ports 245, 250, and 255 for physical connection to a common bus on which 1394 Standard nodes communicate (i.e., network nodes 110). Physical layer 225 also ensures that only one node at a time transmits information on the common bus. Physical layer 225 also converts the format of information received from link layer 230 to the 1394 Standard. Link layer 230 formats communications received from physical layer 225 into a format that can be received by wireless link layer 205. Link layer 230 is coupled to controller 235. Controller 235 executes software instructions contained in memory 240 to perform the format conversions. To be compatible with network 105 it is necessary for node 120 to support the common network physical layer. Node 120 identifies itself to network 105 by broadcasting a set of self identification ("Self ID") packets after each bus reset. A bus reset occurs after each change in network topology. Physical layer 225 is implemented in hardware in order to carry out operations in both the analog and the digital domain. During the identification process physical layer 225 broadcasts a set of Self ID packets (one to four packets, depending upon the number of its bus ports) that associates physical layer 225 with a single node. In other words, physical layer 225 can represent only one node. With respect to communications system 100, node 120 can represent only one of the wireless nodes 140, 150, and 160 to network 105.
Fig. 3 illustrates a block diagram of an exemplary network communications system 300 that communicates in accordance with an advantageous embodiment of the present invention. The present invention comprises device 320 (device "A") having a new type of programmable 1394 Standard physical layer 425 (shown in Fig. 4) that can represent more than one node. The new type of 1394 Standard physical layer 425 broadcasts more than one set of Self ID packets. Each set of Self ID packets represents a single node. Physical layer 425 of the present invention may represent a fixed number of nodes or a variable number of nodes.
The present invention also comprises device 330 (device "B"). In the present example, device 330 is a wireless device. It is understood, however, that in other advantageous embodiments of the present invention, device 330 may be a wired device. Device 330 is capable of sending instructions to physical layer 425 of device 320 to set the number of nodes that physical layer 425 represents. In the advantageous embodiment of the present invention shown in Fig. 4, device 330 comprises controller 415 and memory 420. Controller 415 is capable of executing computer instructions stored in memory 420 to send instructions to physical layer 425 of device 320 to set the number of nodes that physical layer 425 represents. Device 330 is capable of causing physical layer 425 to represent any number of nodes (up to a maximum of sixty three (63) nodes).
In communications system 300 device 330 sends instructions to device 320 to cause physical layer 425 to represent three nodes instead of one node. Physical layer 425 generates multiple Self ID packets by incrementing the physical identification number in a first Self ID packet to create a second Self ID packet, a third Self ID packet, and so on. As will be explained more fully below, physical layer 425 also makes necessary adjustments to other fields in the Self ID packets, such as port status fields. In communications system 300, wireless device 330 detects wireless nodes 140, 150, and 160. Wireless device 330 sends instructions to physical layer 425 of device 320 to create three nodes (node 340 identified as "P", node 350 identified as "Q", and node 360 identified as "R") instead of one node (node 120). Node 340 represents node 140, node 350 represents node 150, and node 360 represents node 160. It therefore appears to network 105 that there are three nodes (node 340, node 350, and node 360) associated with device 320.
Programmable link layer 430 of device 320 can receive all the packets that are to be delivered to nodes 340, 350, and 360. When a device on network 105 sends request packets to nodes 340, 350, or 360, programmable link layer 430 receives the request packets via programmable physical layer 425. Wireless device 330 receives those packets and forwards them to the corresponding nodes 140, 150, or 160. When wireless device 330 receives the response, the response is returned to device 320. Programmable link layer 430 of device 320 generates the response packet to the requester, with the corresponding source node identification (i.e., node 340, node 350, or node 360) in the packet. If node 140, node 150, or node 160 do not communicate using the same protocol as network 105, device 330 applies the necessary protocol conversion to communications between device 320 and device 330.
From the point of view of network 105, device 320 behaves as if there were three nodes in its place (i.e., node 140, node 150, and node 160). Legacy devices and other devices on network 105 can communicate with any one of the nodes 140, 150, or 160 via a non-network compliant link (e.g., a wireless link). In this manner the present invention enables non-network compliant devices to be connected to a network without using a bridge concept.
In the advantageous embodiment of the present invention shown in Fig. 4, device 320 comprises controller 435 and memory 440 and device 330 comprises controller 415 and memory 420. It is noted that in alternate advantageous embodiments of the present invention, a single controller and an associated memory may be used to practice the invention. In particular, in one alternate advantageous embodiment, controller 415 and memory 420 in device 330 is capable of performing its function plus the function of controller 435 and memory 440 in device 320. In another alternate advantageous embodiment, controller 435 and memory 440 in device 320 is capable of performing its function plus the function of controller 415 and memory 420 in device 330.
Some advantageous embodiments of the present invention will now be discussed in more detail. Fig. 5 illustrates three self identification (Self ID) packets showing the format of self identification packets that are used by an IEEE 1394 Standard communications bus. Self ID packet 510 is designated as "SELF ID PACKET NUMBER 0." Self ID packet 520 is designated as "SELF ID PACKET NUMBER 1." Self ID packet 530 is designated as "SELF ID PACKET NUMBER 2." The chart in Fig. 6 identifies some of the fields that are contained within the self identification packets 510, 520, and 530.
As may be seen by referring to Fig. 6, the designation "phy_ID" is the physical node identifier of the node, the designation "sp" is the speed capability of the node, the designation "pwr" is the power class of the node, and the designations "pO" through "pi 5" identify the port connection status for each of the ports connected to the physical node. The packets each consist of sixty four (64) bits. The second thirty two (32) bits are set to be the logical inverse of the first thirty two (32) bits. The second set of thirty two (32) bits are labeled "logical inverse of first quadlet" in Fig. 5. If the first thirty two (32) bits do not match the complement of the second thirty two (32) bits, the entire packet is ignored. Fig. 7 illustrates a first exemplary network communications system having an exemplary bus topology. Each circle in Fig. 7 represents a node and the number within each circle represents the physical identifier of the node. For example, the physical identifier for node 700 is the number 0. The root node (i.e., the highest node in the network) is node 708 and its physical identifier is the number 8. A node that has another node directly beneath it is referred to as a "parent" node. The node directly beneath a parent node is referred to as a "child" node. The physical identifiers are assigned so that a parent node sends out a Self ID packet after all of its children nodes have finished sending a Self ID packet with a unique physical identifier. Each of the nodes in the network shown in Fig. 7 is a physical node.
Fig. 8 illustrates a second exemplary network communications system comprising node 806 that is capable of programming an IEEE 1394 Standard physical layer in accordance with the principles of the present invention. Node 806 depends from node 808. Node 808 comprises a programmable 1394 Standard physical layer and a programmable 1394 link layer of the type shown in node 320 of Fig. 4. Node 806 comprises controller 415 and memory 420 of the type shown in node 330 of Fig. 4. Controller 415 of node 806 is capable of executing computer instructions stored in memory 420 to send instructions to physical layer 425 of node 808 to set the number of nodes that physical layer 425 represents. Node 806 can have any number of physical ports up to twenty six (26) ports. In this example, however, node 806 has only two (2) physical ports. Node 806 represents three active nodes. They are node 804 ("node 4"), node 805 ("node 5"), node 806 ("node 6"). Node 806 has two physical ports and one virtual port. Node 804 and node 805 have only virtual ports.
During the self identification process node 806 sends one self ID packet for each node that it represents. In this example, node 806 generates and sends three sets of self ID packets. Self ID packet number "0" for virtual node 804, and for virtual node 805, and for node 806 are shown in Fig. 9. Self ID packet 910 is designated as "SELF ID PACKET NUMBER 0" for node 804. Self ID packet 920 is designated as "SELF ID PACKET NUMBER 0" for node 805. Self ID packet 930 is designated as "SELF ID PACKET NUMBER 0" for node 806. The topology of the three nodes 804, 805, and 806 in this example is shown as a daisy chain. It is understood, however, that the nodes may have any topology supported by the IEEE 1394 Standard as long as the Self ID packets represent that topology.
When it is'the turn of node 806 to send out a Self ID packet, node 806 starts by sending a virtual Self ID packet for "node 4" (node 804). This is because the last observed Self ID was for "node 3" (node 803). As shown in Fig. 9, the Self ID packet 910 for node 804 has the phy_ID field set equal to four (4) and "pO" port connect status is set equal to "10b" (one zero binary). As shown in the chart in Fig. 6, this means that node 804 is active and is connected to a parent node (i.e., node 805).
Node 806 then sends a virtual Self ID packet for "node 5" (node 805). As shown in Fig. 9, the Self ID packet 920 for node 805 has the phy_ID field set equal to five (5). The phy_ID field has been incremented by one to change the phy_ID field from four to five. The "pO" port connect status is set equal to "10b" (one zero binary) to indicate that node 805 is active and is connected to a parent node (i.e., node 806). The "pi " port connect status is set equal to "1 lb" (one one binary) to indicate that node 805 is also active and connected to a child node (i.e. node 804).
Node 806 is capable of repeating the process by incrementing the phy_ID field for each successive node and sending a Self ID packet for that node. In general, there will be (n-2) such packets where "n" is the number of nodes that node 806 represents. In this example, the value of "n" is three. Therefore, only one Self ID packet is sent out (i.e., the packet for node 805).
Lastly, node 806 sends out a Self ID packet for the last node that node 806 represents (i.e., node 806 itself). The Self ID packet 930 for node 806 has the phy_ID field set equal to six (6). The phy_ID field has been incremented by one to change the phy_ID field from five to six. The "pO" port connect status is set equal to "10b" (one zero binary) to indicate that node 806 is active and is connected to a parent node (i.e., node 808). The "pi" port connect status is set equal to "01b" (zero one binary) to indicate that port one is not active (i.e., connected to nothing). The "p2" port connect status is set equal to "1 lb" (one one binary) to indicate that node 806 is also active and connected to a child node (i.e. node 805). The "gap_count" field and the "sp" field (the "speed capability" field) are common to all of the Self ID packets. The "pwr" field (the "power class" field) is set only for the last Self ID packet sent by node 806. The "speed capability" field and the "power class" field represent the actual capability of the physical hardware layer.
Fig. 10 illustrates a third exemplary network communications system comprising node 1004 that is capable of programming an IEEE 1394 Standard physical layer in accordance with the principles of the present invention. Node 1004 depends from node 1005. Node 1005 comprises a programmable 1394 Standard physical layer and a programmable 1394 link layer of the type shown in node 320 of Fig. 4. Node 1004 comprises controller 415 and memory 420 of the type shown in node 330 of Fig. 4. Controller 415 of node 1004 is capable of executing computer instructions stored in memory 420 to send instructions to physical layer 425 of node 1005 to set the number of nodes that physical layer 425 represents.
Node 1004 can have any number of physical ports up to twenty six (26) ports. In this example, however, node 1004 has only two (2) physical ports. Node 1004 represents three active nodes. They are node 1002 ("node 2"), node 1003 ("node 3"), node 1004
("node 4"). Node 1004 has two physical ports and one virtual port. Node 1002 and node 1003 have only virtual ports.
During the self identification process node 1004 sends one self ID packet for each node that it represents. In this example, node 1004 generates and sends three sets of self ID packets. Self ID packet number "0" for virtual node 1002, and for virtual node 1003, and for node 1004 are shown in Fig. 11. Self ID packet 1110 is designated as "SELF ID PACKET NUMBER 0" for node 1002. Self ID packet 1120 is designated as "SELF ID PACKET NUMBER 0" for node 1003. Self ID packet 1130 is designated as "SELF ID PACKET NUMBER 0" for node 1004. The topology of the three nodes 1002, 1003, and 1004, in this example is shown as a daisy chain. It is understood, however, that the nodes may have any topology supported by the IEEE 1394 Standard as long as the Self ID packets represent that topology.
When it is the turn of node 1004 to send out a Self ID packet, node 1004 starts by sending a virtual Self ID packet for "node 2" (node 1002). This is because the last observed Self ID was for "node 1" (node 1001). As shown in Fig. 11, the Self ID packet 1110 for node 1002 has the phy_ID field set equal to two (2) and "pO" port connect status is set equal to "10b" (one zero binary). As shown in the chart in Fig. 6, this means that node 1002 is active and is connected to a parent node (i.e., node 1003). ' Node 1004 then sends a virtual Self ID packet for "node 3" (node 1003). As shown in Fig. 11 , the Self ID packet 1120 for node 1003 has the phy_ID field set equal to three (3). The phy_ID field has been incremented by one to change the phy D field from two to three. The "pO" port connect status is set equal to "10b" (one zero binary) to indicate that node 1003 is active and is connected to a parent node (i.e., node 1004). The "pi" port connect status is set equal to "1 lb" (one one binary) to indicate that node 1003 is also active and connected to a child node (i.e. node 1002).
Node 1004 is capable of repeating the process by incrementing the phy_ID field for each successive node and sending a Self ID packet for that node. In general, there
* will be (n-2) such packets where "n" is the number of nodes that node 1004 represents. In this example, the value of "n" is three. Therefore, only one Self ID packet is sent out (i.e., the packet for node 1003).
Lastly, node 1004 sends out a Self ID packet for the last node that node 1004 represents (i.e., node 1004 itself). The Self ID packet 1130 for node 1004 has the phy_ID field set equal to four (4). The phyJD field has been incremented by one to change the phy_ID field from three to four. The "pO" port connect status is set equal to "10b" (one zero binary) to indicate that node 1004 is active and is connected to a parent node (i.e., node 1005). The "pi" port connect status is set equal to "1 lb" (one one binary) to indicate that port one is active and connected to a child node (i.e. node 1001). The "ρ2" port connect status is set equal to "1 lb" (one one binary) to indicate that node 1004 is active and connected to a child node (i.e. node 1003).
Fig. 12 illustrates a fourth exemplary network communications system comprising node 1202 that is capable of programming an IEEE 1394 Standard physical layer in accordance with the principles of the present invention. Node 1202 depends from node 1203. Node 1203 comprises a programmable 1394 Standard physical layer and a programmable 1394 link layer of the type shown in node 320 of Fig. 4. Node 1202 comprises controller 415 and memory 420 of the type shown in node 330 of Fig. 4. Controller 415 of node 1202 is capable of executing computer instructions stored in memory 420 to send instructions to physical layer 425 of node 1203 to set the number of nodes that physical layer 425 represents. This example illustrates how node 1202 may be set to represent zero (0) nodes. As shown in Fig. 13, the link-on bit (bit L) in self identification packet 1310 is set equal to zero. When the link-on bit is set, the node has active link and transaction layers. Setting the link-on bit to zero disables the link-on bit so that node 1202 behaves as a repeater node.
The "pO" port connect status of node 1202 is set equal to "10b" (one zero binary) to indicate that node 1202 is active and is connected to a parent node (i.e., node 1203). The "pi" port connect status is set equal to "lib" (one one binary) to indicate that node 1202 is active and connected to a child node (i.e. node 1201). The "p2" port connect status is set equal to "01b" (zero one binary) to indicate that that port two is not active (i.e., connected to nothing).
Fig. 14 is a flow diagram illustrating the operation of an advantageous embodiment of the present invention in an exemplary network communications system. The first step comprises providing a network standard physical layer that is capable of representing more than one mode (step 1410). The network standard may comprise a 1394 Standard. The next step comprises sending instructions to the network standard physical layer from at least one non-network compliant mode to set the number of modes that the network standard physical layer represents (step 1420). The final step comprises representing that number of modes in the network standard physical layer (step 1430). Although the present invention has been described in detail with respect to the illustrative example of a communications system, those skilled in the art should understand that they can make various changes, substitutions and alterations herein without departing from the spirit and scope of the invention in its broadest form.

Claims

CLAIMS:
1. For use in a network (105) having multiple nodes (110, 320), a system (320, 330) for connecting nodes to said network (105) via non-network compliant links comprising: a network standard physical layer (425) in a first node (320) capable of representing more than one node (340, 350, 360); and at least one non-network compliant node (330) coupled to said first node (320), wherein said at least one non-network compliant node (330) is capable of sending instructions to said network standard physical layer (425) in said first node (320) to set the number of nodes that said network standard physical layer (425) represents.
2. The system (320, 330) for connecting nodes to said network (105) as claimed in Claim 1 wherein said network standard physical layer (425) comprises a programmable
1394 Standard physical layer (425).
3. The system (320, 330) for connecting nodes to said network (105) as claimed in Claim 1 wherein said at least one non-network compliant node (330) that is capable of sending instructions to said network standard physical layer (425) in said first node (320) to set the number of nodes that said network standard physical layer (425) represents comprises: a controller (415) capable of executing computer instructions to send instructions to said network standard physical layer (425) in said first node (320) to set the number of nodes that said network standard physical layer (425) represents.
4. The system (320, 330) for connecting nodes to said network (105) as claimed in Claim 1 wherein said at least one non-network compliant node (330) is capable of sending to said network standard physical layer (425) a self identification packet (510, 520, 530) for each node (340, 350, 360) that said at least one non-network compliant node (330) represents.
5. The system (320, 330) for connecting nodes to said network (105) as claimed in Claim 4 wherein said at least one non-network compliant node (330) is capable of adding network node information to said self identification packet (510, 520, 530) for each node (340, 350, 360) that said at least one non-network compliant node (330) represents.
6. The system (320, 330) for connecting nodes to said network (105) as claimed in Claim 5 wherein said network node information comprises one of: physical node identifier, speed capability, power class, port connection status, and link-on status bit.
7. The system (320, 330) for connecting nodes to said network (105) as claimed in Claim 1 wherein said at least one non-network compliant node (330) is capable of sending to said network standard physical layer (425) a self identification packet (510, 520, 530) that indicates that said at least one non-network compliant node (330) represents zero additional nodes.
8. The system (320, 330) for connecting nodes to said network (105) as claimed in Claim 1 wherein said first node (320) comprises a network standard link layer (430).
9. The system (320, 330) for connecting nodes to said network (105) as claimed in Claim 7 wherein said network standard link layer (430) comprises a programmable 1394
Standard link layer (430).
10. A network (105) having multiple nodes (110, 320) capable of connecting nodes to said network (105) via non-network compliant links comprising: a first node (320) capable of representing more than one node (340, 350, 360) comprising a programmable 1394 Standard physical layer (425) and a programmable 1394
Standard link layer (430); and at least one non-network compliant node (330) coupled to said first node
(320), wherein said at least one non-network compliant node (330) is capable of sending instructions to said programmable 1394 Standard physical layer (425) in said first node (320) to set the number of nodes that said programmable 1394 Standard physical layer (425) represents.
11. For use in a network (105) having multiple nodes (110, 320), a method for connecting nodes to said network (105) via non-network compliant links comprising the steps of: providing a network standard physical layer (425) in a first node (320) of said network (105), wherein said network standard physical layer (425) is capable of representing more than one node (340, 350, 360); sending instructions to said network standard physical layer (425) from at least one non-network compliant node (330) to set the number of nodes that said network standard physical layer (425) represents; and representing more than one node (340, 350, 360) in said network standard physical layer (425).
EP01994004A 2000-11-09 2001-11-02 System and method for connecting nodes to a network via non-network compliant link Withdrawn EP1336278A1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US70926900A 2000-11-09 2000-11-09
US709269 2000-11-09
PCT/EP2001/012904 WO2002039677A1 (en) 2000-11-09 2001-11-02 System and method for connecting nodes to a network via non-network compliant link

Publications (1)

Publication Number Publication Date
EP1336278A1 true EP1336278A1 (en) 2003-08-20

Family

ID=24849142

Family Applications (1)

Application Number Title Priority Date Filing Date
EP01994004A Withdrawn EP1336278A1 (en) 2000-11-09 2001-11-02 System and method for connecting nodes to a network via non-network compliant link

Country Status (5)

Country Link
EP (1) EP1336278A1 (en)
JP (1) JP2004514322A (en)
KR (1) KR20020069244A (en)
CN (1) CN1411645A (en)
WO (1) WO2002039677A1 (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1406414A1 (en) * 2002-09-12 2004-04-07 Thomson Licensing S.A. Method and device for connection of a device to a wireless network
WO2006015266A2 (en) * 2004-07-30 2006-02-09 Meshnetworks, Inc. System and method for effecting the secure deployment of networks
JP4628045B2 (en) 2004-08-31 2011-02-09 ソニー株式会社 Recording / reproducing apparatus and recording / reproducing method
US20090175252A1 (en) 2006-04-07 2009-07-09 Nxp B.V. System and method for connecting nodes to a heterogeneous network without using a bridge concept

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3442593B2 (en) * 1996-11-20 2003-09-02 株式会社東芝 Network connection device and network connection method
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
FR2779301B1 (en) * 1998-05-26 2000-07-21 Thomson Multimedia Sa METHOD FOR IDENTIFYING DEVICES IN A COMMUNICATION NETWORK AND APPARATUS FOR IMPLEMENTING
JP3922817B2 (en) * 1998-06-30 2007-05-30 株式会社東芝 Communication node and communication terminal

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO0239677A1 *

Also Published As

Publication number Publication date
KR20020069244A (en) 2002-08-29
JP2004514322A (en) 2004-05-13
CN1411645A (en) 2003-04-16
WO2002039677A1 (en) 2002-05-16

Similar Documents

Publication Publication Date Title
US6445691B2 (en) Wireless coupling of standardized networks and non-standardized nodes
US5784648A (en) Token style arbitration on a serial bus by passing an unrequested bus grand signal and returning the token by a token refusal signal
US6445690B2 (en) Wireless coupling of incompatible nodes via a virtual network
JP3262767B2 (en) IEEE 1394 virtual network generation method and controller thereof
US5467351A (en) Extendible round robin local area hub network
US6738843B2 (en) Method and system for generating multiple self-ID packets on the 1394 bus using a standard PHY chip
JPS6343444A (en) Local area network with multinode bus topology
US6609172B1 (en) Breaking up a bus to determine the connection topology and dynamic addressing
JP4195027B2 (en) Repeater device supporting a plurality of protocols and control method for protocol conversion in the repeater device
EP1391085B1 (en) Method for managing a communication network comprising wireless links with more than two wireless devices
EP1336278A1 (en) System and method for connecting nodes to a network via non-network compliant link
US8213443B2 (en) Network system
KR20040076283A (en) Physical layer circuit and interface circuit
US20090175252A1 (en) System and method for connecting nodes to a heterogeneous network without using a bridge concept
JP2008526061A (en) Repeater node for network
EP1547321B1 (en) Method for determining a parent portal in a wireless network and corresponding portal device
EP1249974B1 (en) Method and communication node for topology correction
KR100433761B1 (en) Ring Topology Network Design Method using Token Ring Medium Access Control Method and Full-Duplex Fast Ethernet Method
JPH11215132A (en) Device and method for processing information and distribution medium
CN1965539A (en) Method for providing a table of station-specific information in a network of distributed stations, and network station for carrying out the method
Tsurumi et al. The μBTRON Bus: Functions and Applications Ken Sakamura Department of Information Science, Faculty of Science, University of Tokyo Kazushi Tamai, Katuya Tanaka, Shigeo Tsunoda Fourth Laboratory, Applied Electronics R & D Laboratories, Yamaha Corporation
Bus C. Medium Access Control Methods
JPS60201759A (en) Data transmission system
JPH01198138A (en) Connection confirming system for complex type local area network

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20030610

AK Designated contracting states

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

17Q First examination report despatched

Effective date: 20041103

17Q First examination report despatched

Effective date: 20041103

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20070824