Source: http://www.google.com/patents/US6724763?dq=5572193
Timestamp: 2014-07-30 21:18:02
Document Index: 265948626

Matched Legal Cases: ['art 403', 'art 403', 'art 413', 'art 413', 'art 403', 'art 403']

Patent US6724763 - Network system - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign in<nobr>Advanced Patent Search</nobr>PatentsA packet passed to an IEEE 1394 bus is received by a packet receiver (421) and stored into a packet buffer (422). Source and destination IDs from the packet buffer (422) are supplied to a comparison/calculation circuit (428) which are also supplied with ID values from a subnetwork routing register (425),...http://www.google.com/patents/US6724763?utm_source=gb-gplus-sharePatent US6724763 - Network systemAdvanced Patent SearchPublication numberUS6724763 B1Publication typeGrantApplication numberUS 09/259,685Publication dateApr 20, 2004Filing dateMar 1, 1999Priority dateMar 6, 1998Fee statusLapsedAlso published asDE69941318D1, EP0948167A2, EP0948167A3, EP0948167B1Publication number09259685, 259685, US 6724763 B1, US 6724763B1, US-B1-6724763, US6724763 B1, US6724763B1InventorsHisaki HiraiwaOriginal AssigneeSony CorporationExport CitationBiBTeX, EndNote, RefManPatent Citations (7), Referenced by (3), Classifications (12), Legal Events (5) External Links: USPTO, USPTO Assignment, EspacenetNetwork systemUS 6724763 B1Abstract A packet passed to an IEEE 1394 bus is received by a packet receiver (421) and stored into a packet buffer (422). Source and destination IDs from the packet buffer (422) are supplied to a comparison/calculation circuit (428) which are also supplied with ID values from a subnetwork routing register (425), bus routing register (426) and node IDs register (427). The comparison/calculation circuit (428) will judge, based on such signals, whether the packet is to be transferred, and when it decides that the packet is to be transferred, will activate the output signal and open a gate (423) to transmit the packet to an inner fabric (401).
Recently, networking many computers and their peripheral devices or AV devices connected to each other has become more and more popular. Each of the devices connected in the network system is called a �node� and incorporates an interface for connection thereof to the network system.
A signal channel designed in conformity to the serial interface standard IEEE 1394 may be used as the transmission control signal channel. Under the standard IEEE 1394, one bus 301 may have a maximum of 63 nodes connected thereto. When more than 63 nodes are to be connected in one bus 301, more than one bus 301 has to be provided and such buses must be connected to each other with bridges 302. The standard IEEE 1394 prescribes that a large-scale network may be organized using a maximum of 1,023 buses. Also under the IEEE 1394, interconnection of the buses and bus ID assignment should be done automatically. The procedure of the bus ID assignment is called a �configuration�. When a bus or buses is added to or deleted from an existing network system, the configuration is started and executed on the entire network system.
rte is also defined to be 0 and 1 in addition to 2 and 3. Briefly, rte=0 means �disable�, rte=1 means �reserve�, rte=2 means lower≦D≦upper, and rte=3 means D<lower and upper<D. When rte=0, no packet will be transferred.
SUMMARY OF THE INVENTION It is therefore an object of the present invention to provide a network system in which less configuration is required when the bus topology has changed.
BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 shows the construction of a conventional network system;
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Referring now to FIG. 3, there is schematically illustrated an embodiment of a network system according the present invention. The network system is generally indicated with a reference numeral 1, of which the construction will be described herebelow. The network system is formed from many computers and their peripheral devices or AV devices connected to each other. In the network system 1, each of the devices incorporates an interface for connection thereof Each of the devices will be referred to as �node� hereinafter.
A packet is to be transferred mainly in three modes as will be shown below. A first mode of them is a �bus broadcast to transmit a packet to all nodes in one bus�, the second one is a �global broadcast to transmit a packet to all nodes in a network system, and the third is a �unicast to transmit a packet to a single node�. These destinations are identified with IDs of a packet as shown in Table 1.
The packet input part of the portal 550 in the first bridge 400, is similar to the packet input part 403 1 shown in FIG. 13. A packet having of a subnetwork ID #1, bus ID #1 and physical ID #y in its destination ID field is received by the packet receiver 421 and stored in the packet buffer 422. A packet delivered from the packet buffer 422 and having a subnetwork ID #1 and bus ID #1 in its destination ID field is supplied to the comparison/calculation circuit 428 which is also supplied with ID values from the subnetwork routing register 425 and bus routing register 426 of the packet input part 403 i of the portal 550 carry flags as shown in FIG. 19. Namely, when each of these registers has 32 flag storage locations having address ID #0, #1, #2, #3, . . . #31, name �0123 . . . 31�, a flag �1� is set as each of the address IDs so as to correspond to bus and subnetwork IDs in the destination ID field of a destination to which a packet transfer is allowed. In the bus routing register 426, a flag is set in a location �0101 . . . 1� as indicated with BR. In the subnetwork routing register 425, a flag is set in a location �0110 . . . 1� as indicated with SR. Thus, receiving an ID value corresponding to the flag location, the comparison/calculation circuit 428 will be able to judge whether the packet is to be transferred. When the comparison/calculation circuit 428 decides that the packet is to be transferred, it will open the gate 423 to transmit the packet stored in the packet buffer 422 to the inner fabric 401.
Note that in the portal 552 in the first bridge 400 1 connecting the buses 510 and 530, the register BR in the packet input part thereof has a content �0010 . . . 0� while the register SR has a content �0000 . . . 0�. In this case, the comparison/calculation circuit 428 will decide that the packet is not to be transferred and not open the gate 423. The second bridge 400 2 will not pass the packet.
In the portal 554, the register BR in the packet input part thereof has a content �0110 . . . 1� while the register SR has a content �0010 . . . 1�. Thus, the comparison/calculation circuit will decide that the packet is not to be transferred and will not open the gate. The second bridge 400 3 will not pass the packet.
The packet input part of the portal 558 in the second bridge 410 1 is similar in construction to the packet input part 413 i shown in FIG. 16. A packet having a subnetwork ID #1, bus ID #1 and physical ID #y in the destination ID field thereof is received by the packet receiver 441 and stored into the packet buffer 442. A subnetwork ID from the packet buffer 442, being �1�, is supplied to the comparison/calculation circuit 447 which is also supplied with an ID value from the subnetwork routing inport register 445. The register 445 of the packet input part 413 i in the portal 558 carries flags as shown in FIG. 19. Namely, the register SR has a content �0100 . . . 1�. Therefore, the comparison/calculation circuit 447 will decide that the packet is to be transferred, and opens the gate 443 to transmit the packet stored in the packet buffer 442 to the inner fabric 411.
The portal 655 forms the first bridge 400 5 connecting the buses 610 and 620, and comprises a packet input part similar in construction to the packet shown in FIG. 13. It includes a register BR having a content �0100 . . . 1� and a register SR having a content �0000 . . . 1�. Therefore, the comparison/calculation circuit will decide that the packet is to be transferred, and open the gate 423 to transmit the packet to the inner fabric 401.
First, the portal 550 in the first bridge 400 1 has a packet input part similar in construction to the packet input part 403 i shown in FIG. 13. A packet having a subnetwork ID #3, bus ID #0 and physical ID #y in the destination ID field thereof is received by the packet receiver 421 and stored into the packet buffer 422. A packet from the packet buffer 422 having a subnetwork ID #3 and bus ID #0 in the destination ID field thereof is supplied to the comparison/calculation circuit 428 which is also supplied with ID values from the subnetwork routing register 425 and bus routing register 426. The two registers 425 and 426 of the packet input part 403 i in the portal 550 carry flags as shown in FIG. 19. Namely, the register BR has a flag contains �0101 . . . 1� while the register SR has a flag content �0111 . . . 1�. Therefore, the comparison/calculation circuit 428 decides that the packet is to be transferred, and opens the gate 423 to transmit the packet stored in the packet buffer 422 to the inner fabric 401. Since the operations of the portals 551, 552 and 554 are the same as mentioned above, they will not be described any longer.
The portal 561 in the bus 520 has a packet input part similar in construction to that shown in FIG. 16 except that the subnet routing register 445 is a subnet routing inport register 445. The register SRI has a flag content �0101 . . . 1� as shown in FIG. 20. Therefore, the comparison/calculation circuit 447 will open the gate 443 to transmit the packet to the inner fabric 411.
Note that the packet output parts of the portals 658 and 855, respectively, are similar in construction to the packet output part shown in FIG. 18, and acquire the packet from the inner fabric 411 into the packet buffer 451. A packet from this packet buffer 451 having a subnetwork ID in the destination ID field thereof is supplied to the comparison/calculation circuit 455 which is also supplied with a signal from the subnetwork routing outport register 454. In the network system in FIG.20, the register SR in the portal 658 has a flag content �0100 . . . 1� and the register SR in the portal 855 has a flag content �0001 . . . 1�.
First, it is judged at step S1 whether the subnetwork and bus IDs in the destination ID field of a received packet is �0�1f�. When it is decided that the IDs are not �0�1f�, the operation goes to step S2. At this step S2, it is judged whether the subnetwork ID in the destination ID field and that in the node IDs field of the packet are equal to each other. If it is decided that they are not equal to each other, the operation goes to step S3. It is judged at this step S3 whether the bus ID in the destination ID field and that in the node IDs field of the packet are equal to each other. When it is decided that they are equal to each other, the operation goes to step S4 and the packet is not transferred.
If it is decided at step S1 that the subnetwork and bus IDs in the destination ID field are �0�1f�, the operation goes to step S8 where it is judged whether the subnetwork and bus IDs in the destination ID field are �0�1f�. When it is decided that they are not �0�1f�, the operation goes to step S9 where it is judged whether the physical ID in the destination ID field is �0�3f�. When it is decided that the physical ID is �0�3f�, the operation goes to step S10 where the bus routing register content �0�1f� is 1. If it is decided that the register content is 1, the operation goes to step S7. The packet is delivered to the inner fabric from which it is transmitted from the portal on the opposite side.
When it is decided at step S8 that the subnetwork and bus IDs are �0�1f� or when it is decided at step S9 that the physical ID is not �0�3f�, the operation goes to step S4 and the packet is not transferred.
When it is judged at step S10 that the bus routing register content �0�1f� is not 1, the operation goes to step S11 where it is judged whether the subnetwork routing register content �0�1f� is 1. If the register content is 1, the operation goes to step S7 and the packet is delivered to the inner fabric from which the packet is transmitted from the portal on the opposite side. When it is decided that the register content is not 1, the operation goes to step S4 and the packet is not transferred.
First, it is judged at step S21 whether the subnetwork and bus IDs in the destination ID field of a received packet is �0�1f�. When it is decided that the IDs are not �0�1f�, the operation goes to step S22. At this step S22, it is judged whether the subnetwork routing inport register content and the subnetwork ID in the destination ID field of the packet are equal to each other. If it is decided that they are not equal to each other, the operation goes to step S23 and the packet is not transferred. When it is decided that they are equal to each other, the operation goes to step S24 and the packet is delivered to the inner fabric.
On the other hand, if it is decided at step S21 that the subnetwork and bus IDs are �0�1f�, the operation goes to step S25. At this step S25, it is judged whether the subnetwork and bus IDs in the destination ID field are �0�1f�. If it is decided that they are not �0�1f�, the operation goes to step S26 where it is judged whether the physical ID in the destination ID field of the packet is �0�3f�. If it is decided that the physical ID is �0�3f�, the operation goes to step S27 where it is judged whether the subnetwork routing inport register content �0�1f� is 1. When it is judged that it is 1, the operation goes to step S24 and the packet is transferred to the inner fabric.
On the other hand, if it is decided at step S25 that the subnetwork and bus IDs are �0�1f�, if it is decided at step S26 that the physical ID is not �0�3f� or if it is decided at step S27 that the subnetwork routing inport register content is not 1, the operation goes to S23 and the packet is not transferred.
First at step S31, it is judged whether the subnetwork and bus IDs in the destination ID field of a received packet are �0�1f�. If it is decided that they are not �0�1f�, the operation goes to step S32 where it is judged whether the subnetwork routing outport register content and the subnetwork ID in the destination ID field of the packet are equal to each other. If it is decided that they are not equal, the operation goes to step S33 and nothing is done.
On the other hand, if it is decided at step S31 that the subnetwork and bus IDs are �0�1f�, the operation goes to step S34 where it is judged whether the subnetwork routing outport register content �0�1f� is 1. When it is decided that the subnetwork routing outport register content �0�1f� is not 1, the operation goes to step S33 and nothing is done.
If it is decided at step S32 that the subnetwork routing output register content is equal to the subnetwork ID in the destination ID field of the packet, the operation goes to S35 and the packet is transmitted from the portal to the bus. Also when it is decided at step S34 that the register content �0�1f� is 1, the operation goes to step S35 and the packet is transmitted from the portal to the bus.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5018137 *Oct 16, 1990May 21, 1991Digital Equipment CorporationTransparent load sharing for parallel networksUS5088090 *Jan 31, 1990Feb 11, 1992Rad Network Devices Ltd.Routing system to interconnect local area networksUS5214646 *Nov 13, 1991May 25, 1993Amnon YacobySystem and method for interconnecting local area networksUS5504747 *Mar 3, 1993Apr 2, 1996Apple Computer, Inc.Economical payload stream routing in a multiple-ring networkUS5515513 *Mar 23, 1995May 7, 1996Digital Equipment CorporationDisposition filtering of messages using a single address and protocol table bridgeUS6266728 *Jan 19, 1999Jul 24, 2001Sony CorporationNetwork system having a bridge that assigns identification numbers to buses connected as a tree and that reserves some identification numbersUSRE33426 *Jul 13, 1989Nov 6, 1990Hitachi, Ltd.Multi-network system* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7995898 *Apr 25, 2006Aug 9, 2011Sony CorporationAudio relay apparatus and audio relay methodUS8014408 *Sep 13, 2002Sep 6, 2011Koninklijke Philips Electronics N.V.Network with several subnetworksUS8594106Jul 21, 2011Nov 26, 2013Koninklijke Philips N.V.Network with several subnetworks* Cited by examinerClassifications U.S. Classification370/401International ClassificationH04L12/56, G06F13/00, H04L12/64, H04L12/46, H04L12/40Cooperative ClassificationH04L12/462, H04L12/40091, H04L49/90European ClassificationH04L49/90, H04L12/46B7, H04L12/40F6Legal EventsDateCodeEventDescriptionJun 12, 2012FPExpired due to failure to pay maintenance feeEffective date: 20120420Apr 20, 2012LAPSLapse for failure to pay maintenance feesDec 5, 2011REMIMaintenance fee reminder mailedSep 26, 2007FPAYFee paymentYear of fee payment: 4Mar 1, 1999ASAssignmentOwner name: SONY CORPORAITON, JAPANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HIRAIWA, HISAKI;REEL/FRAME:009807/0353Effective date: 19990223RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google