Claims
- 1. An asynchronous control mechanism packet including an address value corresponding to a target device on a target bus, a designation and instructional information, wherein the designation within the asynchronous control mechanism packet causes a bridge device coupled to the target device and the target bus to intercept the packet and utilize the instructional information to perform one or more control tasks specified by the designation and the instructional information.
- 2. The asynchronous control mechanism packet as claimed in claim 1 wherein the designation is included within an extended transaction code field within the asynchronous control mechanism packet.
- 3. The asynchronous control mechanism packet as claimed in claim 1 wherein the designation is included within a transaction code field within the asynchronous control mechanism packet.
- 4. The asynchronous control mechanism packet as claimed in claim 1 wherein the designation is included within an address offset value within the asynchronous control mechanism packet.
- 5. The asynchronous control mechanism packet as claimed in claim 1 wherein the instructional information specifies a type of transaction and the control tasks to be performed.
- 6. The asynchronous control mechanism packet as claimed in claim 1 wherein the asynchronous control mechanism packet is initiated by a controlling device.
- 7. The asynchronous control mechanism packet as claimed in claim 1 wherein the asynchronous control mechanism packet is not forwarded to the target device.
- 8. The asynchronous control mechanism packet as claimed in claim 1 wherein the designation and instructional information instruct the bridge device to establish an isochronous connection between a talker device and a listener device.
- 9. The asynchronous control mechanism packet as claimed in claim 8 wherein each bridge device within a route between the talker device and the listener device intercept the asynchronous control mechanism packet and allocate resources necessary to establish the isochronous connection between the talker device and the listener device.
- 10. The asynchronous control mechanism packet as claimed in claim 9 wherein the talker device and the listener device are coupled within a network of buses that substantially complies with a version of an IEEE Std 1394 standard.
- 11. A method of effecting control of a bridge device coupled to a target device on a target bus comprising the steps of:
a. sending an asynchronous control mechanism packet directed to the target device which includes an address value corresponding to the target device, a designation and instructional information; b. receiving the asynchronous control mechanism packet at the bridge device; and c. utilizing the instructional information to perform one or more control tasks specified by the designation and the instructional information.
- 12. The method as claimed in claim 11 wherein the asynchronous control mechanism packet is not forwarded to the target device.
- 13. The method as claimed in claim 11 wherein the designation is included within an extended transaction code field within the asynchronous control mechanism packet.
- 14. The method as claimed in claim 11 wherein the designation is included within a transaction code field within the asynchronous control mechanism packet.
- 15. The method as claimed in claim 11 wherein the designation is included within an address offset value within the asynchronous control mechanism packet.
- 16. The method as claimed in claim 11 wherein the step of utilizing establishes an isochronous connection between a talker device and a listener device.
- 17. The method as claimed in claim 16 wherein the steps of sending, receiving and utilizing are performed by each bridge device within a route between the talker device and the listener device and further wherein each of the bridge devices within the route allocate resources necessary to establish the isochronous connection between the talker device and the listener device.
- 18. The method as claimed in claim 17 wherein the talker device and the listener device are coupled within a network of buses that substantially complies with a version of an IEEE Std 1394 standard.
- 19. A method of establishing an isochronous connection between a talker device and a listener device within a network of buses, wherein bridge devices are coupled between buses within the network of buses, the method comprising the steps of:
a. sending an asynchronous control mechanism packet from an initiating device directed to a selected one of the talker device and the listener device, wherein the asynchronous control mechanism packet includes an address value corresponding to the selected one of the talker device and the listener device and a designation specifying that the packet is an asynchronous control mechanism packet; b. receiving the asynchronous control mechanism packet at a current bridge device within the route between the talker device and the listener device; c. allocating resources necessary to establish the isochronous connection between the talker device and the listener device; d. determining if the current bridge device is a final bridge device within the route; e. passing the asynchronous control mechanism packet on to a next bridge device and repeating steps b-d if it is determined that the current bridge device is not the final bridge device within the route; and f. sending a control message to the initiating device if it is determined that the current bridge device is the final bridge device within the route.
- 20. The method as claimed in claim 19 wherein the asynchronous control mechanism packet is not forwarded to the selected one of the talker device and the listener device.
- 21. The method as claimed in claim 19 wherein the designation is included within an extended transaction code field within the asynchronous control mechanism packet.
- 22. The method as claimed in claim 19 wherein the designation is included within a transaction code field within the asynchronous control mechanism packet.
- 23. The method as claimed in claim 19 wherein the designation is included within an address offset value within the asynchronous control mechanism packet.
- 24. The method as claimed in claim 19 wherein the network of buses substantially complies with a version of an IEEE Std 1394 standard.
- 25. A bridge device configured for coupling between two or more buses of devices comprising:
a. a first portal interface configured for coupling to and communicating with a first bus of devices; b. a second portal interface configured for coupling to and communicating with a second bus of devices; and c. a detecting and control circuit coupled to the first portal interface and the second portal interface for detecting when the first portal interface and the second portal interface receive an asynchronous control mechanism packet directed to a target device, wherein the asynchronous control mechanism packet includes an address value corresponding to the target device, a designation and instructional information and further wherein the detecting and control circuit performs one or more control tasks specified by the designation and the instructional information.
- 26. The bridge device as claimed in claim 25 wherein the designation is included within an extended transaction code field within the asynchronous control mechanism packet.
- 27. The bridge device as claimed in claim 25 wherein the designation is included within a transaction code field within the asynchronous control mechanism packet.
- 28. The bridge device as claimed in claim 25 wherein the designation is included within an address offset value within the asynchronous control mechanism packet.
- 29. The bridge device as claimed in claim 25 wherein the one or more control tasks performed by the detecting and control circuit establish an isochronous connection between a talker device and a listener device.
- 30. The bridge device as claimed in claim 25 wherein the bridge device and the two or more buses substantially comply with a version of an IEEE Std 1394 standard.
- 31. A network of devices coupled together by two or more buses, wherein bridge devices within the network couple different buses of devices to each other, each of the bridge devices comprising:
a. a first portal interface configured for coupling to and communicating with a first bus of devices; b. a second portal interface configured for coupling to and communicating with a second bus of devices; and c. a detecting and control circuit coupled to the first portal interface and the second portal interface for detecting when the first portal interface and the second portal interface receive an asynchronous control mechanism packet directed to a target device, wherein the asynchronous control mechanism packet includes an address value corresponding to the target device, a designation and instructional information and further wherein the detecting and control circuit performs one or more control tasks specified by the designation and the instructional information.
- 32. The network of devices as claimed in claim 31 wherein the designation is included within an extended transaction code field within the asynchronous control mechanism packet.
- 33. The network of devices as claimed in claim 31 wherein the designation is included within a transaction code field within the asynchronous control mechanism packet.
- 34. The network of devices as claimed in claim 31 wherein the designation is included within an address offset value within the asynchronous control mechanism packet.
- 35. The network of devices as claimed in claim 31 wherein the one or more control tasks performed by the detecting and control circuit establish an isochronous connection between a talker device and a listener device.
- 36. The network of devices as claimed in claim 31 wherein the network of devices substantially complies with a version of an IEEE Std 1394 standard.
RELATED APPLICATIONS
[0001] This application claims priority under 35 U.S.C. §119(e) of the co-pending U.S. provisional application Serial No. 60/130,886 filed on Apr. 23, 1999 and entitled “Network Bridging System And Method.” The provisional application Serial No. 60/130,886 filed on Apr. 23, 1999 and entitled “Network Bridging System And Method” is also hereby incorporated by reference.
Provisional Applications (1)
|
Number |
Date |
Country |
|
60130886 |
Apr 1999 |
US |
Continuations (1)
|
Number |
Date |
Country |
Parent |
09556080 |
Apr 2000 |
US |
Child |
10189671 |
Jul 2002 |
US |