WO2001038996A9 - Procede et systeme d'ajustement de largeur de bande isochrone sur un bus - Google Patents

Procede et systeme d'ajustement de largeur de bande isochrone sur un bus

Info

Publication number
WO2001038996A9
WO2001038996A9 PCT/US2000/042429 US0042429W WO0138996A9 WO 2001038996 A9 WO2001038996 A9 WO 2001038996A9 US 0042429 W US0042429 W US 0042429W WO 0138996 A9 WO0138996 A9 WO 0138996A9
Authority
WO
WIPO (PCT)
Prior art keywords
portal
bus
talker
listener
portals
Prior art date
Application number
PCT/US2000/042429
Other languages
English (en)
Other versions
WO2001038996A1 (fr
Inventor
David V James
Bruce Fairman
David Hunter
Hisato Shima
Original Assignee
Sony Electronics Inc
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
Priority claimed from US09/531,075 external-priority patent/US6539450B1/en
Application filed by Sony Electronics Inc filed Critical Sony Electronics Inc
Priority to AU36438/01A priority Critical patent/AU3643801A/en
Publication of WO2001038996A1 publication Critical patent/WO2001038996A1/fr
Publication of WO2001038996A9 publication Critical patent/WO2001038996A9/fr

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/40065—Bandwidth and channel allocation
    • 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/40091—Bus bridging
    • 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
    • H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462—LAN interconnection over a bridge based backbone
    • H04L12/4625—Single bridge functionality, e.g. connection of two networks over a single bridge
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/64—Hybrid switching systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical routing

Definitions

  • the present invention relates generally to audio, video, and audio /video interconnected systems for home and office use. More particularly, the present invention relates to a method and system for adjusting isochronous bandwidth allocations in a digital bus system.
  • A/V consumer electronic audio /video
  • digital A/V applications such as consumer A/V device control and signal routing and home networking
  • AV/C audio/video control
  • Typical computer systems solve the bandwidth problem by increasing the bandwidth of the system bus to handle all of these forms, types and amount of data.
  • the system bus has become more clogged with information other than information directly utilized and needed by the main processor.
  • a first bus commonly referred to as a memory bus
  • a second bus is used for communications between peripheral devices such as graphics systems, disk drives, or local area networks.
  • a bus bridge is utilized to "bridge,” and thereby couple, the two buses together.
  • IEEE 1394 standard serial bus implemented by IEEE Std 1394-1995, Standard For A High Performance Serial Bus, August 30, 1996 (hereinafter "IEEE 1394 standard”) and related other 1394 standards.
  • the IEEE 1394 standard is an international standard for implementing a high-speed serial bus architecture, which supports both asynchronous and isochronous format data transfers.
  • the IEEE 1394 standard defines a bus as a non- cyclic interconnect, consisting of bus bridges and nodes. Within a non-cyclic interconnect, devices may not be connected together so as to create loops. Within the non-cyclic interconnect, each node contains an AN/C device, and bus bridges serve to connect buses of similar or different types.
  • the primary task of a bridge is to allow data to be transferred on each bus independently without demonstrating performance of the bus, except when traffic crosses the bus bridge to reach the desired destination on the other bus.
  • the bridge is configured to understand and participate in the bus protocol of each of the buses.
  • Multi-bus systems are known to handle the large amounts of information being utilized.
  • communication between buses and devices on different buses is difficult.
  • a bus bridge may be used to interface I/O buses to the system's high-performance processor/memory bus.
  • the CPU may use a 4-byte read and write transaction to initiate DMA transfers.
  • the DMA of a serial bus node When activated, the DMA of a serial bus node generates split-response read and write transactions which are forwarded to the intermediate system backbone bus which also implements serial bus services.
  • the host-adapter bridge may have additional features mandated by differences in bus protocols.
  • the host bus may not directly support isochronous data transfers.
  • the host-adapter bridge may enforce security by checking and translating bridge-bound transaction addresses and may often convert uncached I/O transactions into cache-coherent host-bus transaction sequences.
  • IEEE 1394 standard serial bus Each time a new device or node is connected or disconnected from an IEEE 1394 standard serial bus, the entire bus is reset and its topology is reconfigured.
  • the IEEE 1394 standard device configuration occurs locally on the bus without the intervention of a host processor. In the reset process, three primary procedures are typically performed; bus initialization, tree identification, and self identification.
  • bus initialization In the reset process, three primary procedures are typically performed; bus initialization, tree identification, and self identification.
  • a single node must first be established as the root node during the tree identification process in order for the reconfiguration to occur.
  • Isochronous data connections have one talker and one or more listeners.
  • the talker broadcasts audio, video, or any other data format. Both the talker and listener are nodes on the digital bus system.
  • Isochronous data is routed by channel numbers from the talker to the listener. The channel numbers are assigned to the data connections dynamically.
  • Each listener has an associated controller that sets up the isochronous connection between the talker and listener.
  • the controllers signal the bus bridges (through their associated portals) to expect data having a certain bandwidth.
  • the bandwidth allocated for the data being broadcast by the talker must be increased or decreased because the data format changes. For example, a talker may broadcast highly compressed video data at 25 megabits per second and then begin broadcasting lightly compressed video requiring 50 megabits per second of bandwidth.
  • the change in bandwidth could, of course, be signaled by immediately transmitting the data packets at the higher bandwidth.
  • the bus bridges can detect the larger packets and requested additional bandwidth from the bus portals. However, this may result in fewer data channels being transmitted through the digital bus system. These digital bus systems allowed talkers to simply begin sending larger packets to the listener.
  • a bandwidth change indication is generally broadcast over the entire bus system.
  • a reliable broadcast mechanism for sending the bandwidth change indication is difficult to implement since all nodes may not receive the indication. These missed nodes will not return an error message to the digital bus system.
  • a widely broadcast message tends to flood the bus system with messages causing data congestion.
  • talkers do not know the bus addresses of controllers because numerous bus connections (one for each listener) may be associated with a specific talker, and each listener may be associated with a distinct controller.
  • a method of adjusting the bandwidth allocated for isochronous data traffic on an interconnected data bus uses an isochronous resource manager (IRM) located on a bus bridge to sense a bandwidth change request from a talker.
  • the IRM instigates a bandwidth adjustment associated with the bandwidth change request to one or more bus bridge portals.
  • Figure 1 is a block diagram of one embodiment for an interconnect topology
  • Figure 2 is a block diagram of a device of Figure 1;
  • Figure 3 is a block diagram of one embodiment for a 1394 standard bus bridge system
  • Figure 4 is a block diagram of one embodiment for a 1394 bus bridge topology
  • Figure 5 is a block diagram of one embodiment for a looped bus bridge topology
  • FIG. 6 is a block diagram of one embodiment for bus bridge components
  • FIG. 7 is a block diagram of one embodiment for bus bridge isochronous transfer
  • FIG. 8 is a block diagram of another embodiment for bus bridge isochronous transfer
  • Figure 9 is a block diagram of another embodiment for bus bridge isochronous transfer using a mechanism of partially overlaid bus connections.
  • Figure 10 is a flow diagram of one embodiment for adjusting the bandwidth allocations on interconnected data buses.
  • a method and system for adjusting the bandwidth allocated for isochronous data traffic on an interconnected data bus uses an isochronous resource manager (IRM) located on a bus bridge to sense a bandwidth change request from a talker.
  • the IRM instigates a bandwidth adjustment associated with the bandwidth change request to one or more bus bridge portals. As the request is disseminated throughout the bus, bandwidth allocations are adjusted at each portal until the listener controller is reached.
  • IRM isochronous resource manager
  • FIG. 1 is a block diagram of one embodiment for an interconnect topology 100.
  • server 102 is connected to a wide area network (WAN) 110 and to a bus bridge 170.
  • the bus bridge is interconnected to a number of audio, video, and/or audio/video devices, 120, 130, 140, 150, and 160.
  • the devices (120-160) are connected to bus bridge 170 via the IEEE 1394 standard serial bus.
  • Server 102 may be any device that is capable of connection to both a bus bridge 170 and wide area network 110, such as, for example, a personal computer or a set-top box.
  • network 110 may be a wide area network, such as, for example, the Internet, or a proprietary network such as America Online®, CompuServe®, Microsoft Network®, or Prodigy®.
  • WAN 110 may be a television communications network.
  • Server 102 includes a network interface which communicates with WAN 110.
  • Topology 100 includes high speed serial bus 180a and 180.
  • serial bus 180 is the IEEE 1394 standard serial bus.
  • Topology 100 includes various consumer electronic devices 120-160 connected via the high speed serial bus 180 to bus bridge 170.
  • the consumer electronic devices 120-160 may include, for example, a printer, additional monitor, a video camcorder, an electronic still camera, a video cassette recorder, digital speakers, a personal computer, an audio actuator, a video actuator, or any other consumer electronic device that includes a serial interface which complies with a serial interface standard for networking consumer electronic devices — for example, the IEEE 1394 standard.
  • Topology 100 may be contained within a home or office.
  • Bus bridge 170 is used to connect devices 120-160 in which devices 120-160 may be physically located within different rooms of the home or office.
  • any comrnunication media may be used such as radio frequency (RF) communication or the like.
  • FIG 2 is a block diagram of a device 120.
  • device 120 may be a laser printer, digital camera, set-top box, or any other appropriate consumer electronic device capable of being connected via a high speed serial bus 180.
  • the device 120 includes a controller 202, memory 208, and I/O 210, all connected via bus 215.
  • Memory 208 may include, for example, read only memory (ROM), random access memory (RAM), and /or non-volatile memory.
  • I/O 210 provides connection with wide area network 110, bus bridge 170, and another peripheral device (130-160).
  • I/O 210 is a serial bus interface that complies with a serial interface standard for networking with consumer electronic devices (120-161) and bus bridge 170 within topology 100.
  • the serial bus interface and topology 100 may use the IEEE 1394 standard serial bus.
  • I/O 210 provides for receiving signals from and transmitting signals to other consumer electronic devices (130-160) or bus bridge 170.
  • Memory 208 provides temporary storage for voice and data signal transfers between outside network 110 and topology 100.
  • memory 208 may buffer digital voice and data signals received by I/O 210 from WAN 110 before signals are transmitted onto IEEE 1394 standard bus 180.
  • Controller 202 controls various operations of device 120. Controller 202 monitors and controls the traffic through the device 120 to and from topology 100 and WAN 110.
  • Device 120 I/O 210 may have one or more physical ports.
  • a single port device discontinues the bus along the given branch of the bus, whereas devices with two or more ports allow continuation of the bus.
  • Devices with multiple ports permit a daisy chained bus topology, even though the signaling environment is point-to-point. That is, when a multi-port node receives a packet of data, the data is detached and retransmitted to the necessary port as indicated within the data. The configuration is performed dynamically as new devices are attached and /or removed from bus 180.
  • the 1394 standard bus protocol is designed to support peer-to-peer transfers between devices. This allows serial bus devices to transfer data between themselves without intervention from a computer system or host system. This allows high throughput between devices without affecting the performance of the computer system. Thus, a video camera may be set up to transfer between itself and a video cassette recorder without accessing a computer system.
  • FIG 3 is a block diagram of one embodiment for a 1394 standard bridge bus system 400.
  • system 400 includes bridge 402 which connects two or more buses 408 and 410.
  • Bus 408 and 410 may be the same or different types of buses.
  • bus 408 may be a 1394 standard serial bus and bus 410 may be a different high performance bus.
  • the 1394 standard bus architecture limits the number of nodes or devices 310 on a bus 263 and supports multiple bus systems via bus bridge 402.
  • CSR control and status register
  • ISO/IEC 13213 ANSI/IEEE 1212
  • CSR Information systems-Control and Status Registers
  • Microcomputer Buses defines the 1394 standard bus addressing structure, which allows approximately 2 16 nodes (404, 406, 412-420).
  • the CSR standard defines their registry, their functionality, and, where appropriate, where they appear in the address space.
  • Figure 3 is the simplest instance of a bus topology in which the net has one bus bridge.
  • Figure 4 illustrates a net that may have more than one bus bridge and, when so structured, is hierarchical in nature.
  • Figure 5 illustrates a network whose physical topology may have loops, but whose loops are electronically disabled to generate a hierarchical structure.
  • a collection of multiple buses connected through a bus bridge is referred to as a "net”.
  • FIG 4 is a block diagram of one embodiment for a 1394 bridge bus topology 500.
  • topology 500 has one prime portal 504 and one or more alpha portals 506 and 508.
  • the primary bus 525 has exactly one prime portal 504 and the secondary buses 527, 529, 531, 533, and 535 have exactly one alpha portal each — 506, 508 and 510.
  • Each bus 525-535 may have any number of secondary portals.
  • An alpha portal is on the path to a prime portal. Any portal not a prime portal or an alpha portal is a secondary portal.
  • the prime portal or the alpha portal may be referred to as a primary portal.
  • the bridge portal with the largest portal ID identifier is elected to become the prime portal 504.
  • the bridge portal with the smallest portal ID identifier is elected to become the prime portal 504.
  • Each portal appears as a node on its attached bus.
  • the bus with the prime portal 504 is termed the primary bus 525 and other buses 527-535 are termed secondary buses. On secondary buses 527-535, the bridge portal that leads to the primary bus 525 is called the alpha portal (506, 508).
  • any node within the interconnect may be accessed by its unique 16-bit node identification address.
  • the node identification address contains the bus ID and the local ID components. Referring to Figure 4, the bus identification IDs of nodes 512-524 are indicated by the letters a, b, and c and the local ID is indicated by the numbers 0-4.
  • Alpha portal 504 is responsible for rejecting missed address asynchronous data packets by accepting these requests and returning error reporting responses.
  • the previous and current prime and alpha portal identifiers are used to classify nodes when an interconnect topology changes, and the alpha portal is the isochronous clock reference for other nodes on the bus.
  • Bus bridge topology 500 may change and be established dynamically during operation of bus bridge system 500.
  • the bus bridge topology 500 is established during net refresh.
  • portals selectively route packets.
  • Asynchronous routing tables are stable until topology 500 changes during a net refresh or net reset operation.
  • Asynchronous routing tables are dynamic and are changed by their asynchronous connect and disconnect operations of the protocols.
  • FIG. 5 is a block diagram of one embodiment for a looped bus bridge topology 600.
  • portal 606 may be added to the topology 600 forming a loop.
  • a path exists from a0-b4 through cO back to aO.
  • the redundant portal 606 is disabled so that a hierarchical bus bridge topology remains.
  • cyclical net topologies may be allowed.
  • software routines may partially activate the redundant bridge 606 and allow a shortest path routing between nodes. For example, traffic between bus a 605 and bus c 615 may be efficiently routed without introducing deadlocks.
  • FIG 6 is a block diagram of one embodiment for bus bridge components 700.
  • bus bridge components 700 are maintained within each portal in which bus "a" to bus “b” components 702 and bus “b” to bus “a” components 704 are independently maintained.
  • Components 700 also contains shared microprocessor and RAM 706.
  • Asynchronous and isochronous packet transfers may not acquire a bus at the same time. Therefore, asynchronous packets are placed in request queues 708, 720 and response queues 710, 722. The asynchronous packets are selected for transfer at times when isochronous packets are not being transferred. Isochronous packets are received and time stamped 712, 724. Time gates 718, 730 release the isochronous packets 714, 726, together with common isochronous packet (CIP) headers 716, 728, at fixed times. Routing tables select which asynchronous and isochronous packets are accepted and queued for adjacent bus delivery.
  • CIP isochronous packet
  • Topologies may share physical buffer space rather than implementing physical distinct stacks subject to the following: bus "a" to bus “b” and bus “b” to bus “a” queues operate independently, response processing is never blocked by queued requests, and asynchronous subactions and isochronous packets are forwarded independently. Topologies may block a request behind the previously queued response without generating potential deadlocks; however, requests and responses are processed independently.
  • Isochronous routing decisions are made by checking the isochronous packet's channel number. Accepted packets are converted and retransmitted on the adjacent bus with newly assigned channel numbers, speeds, and CIP-header and, when a CIP-header is provided, time-stamp parameters 716, 728 from the CIP- header. CIP-headers may be pre-appended to some isochronous packets to further describe their format and function and desired presentation time. When the packets incur delays while traversing through a bridge, then presentation time must be adjusted to compensate for this delay. CIP headers are defined in ISO/IEC 61883 specification. Isochronous packets received in cycle n are forwarded to the adjacent bus in cycle n+k where k is an implementation dependent constant.
  • Messages may be passed around one bus or pass through a bridge by writing to a standardized message location 732, 734, 736, 738 on a bridge's portal. This allows bus-interconnect topologies to be restored while freezing, or discarding when necessary, previously queued subactions.
  • Distribution of clock-sync information 740, 742 from the primary-bus source is performed by placing calibration information in isochronous-clock pseudo queues before forwarding this information to the clock master on the adjacent portal.
  • clock-sync information flows from the primary bus downward, so that only one clock-sync pseudo queue may be required.
  • each node has two node ID addresses: physical ID address and virtual ID address.
  • a physical node ID has a 3FF 16 valued bus ID; a virtual node ID has smaller bus ID addresses.
  • all nodes are accessed through their physical addresses.
  • the physical address is used to configure the node and the virtual address is normally used thereafter.
  • Directed-asynchronous routing decisions are made by checking the destination ID addresses of pass-through packets. Accepted packets are directly routed to the bridge's opposing port.
  • an asynchronous quarantine is maintained which selectively enables forwarding of a request sub-action based on the local identification of a bus-local requester.
  • a set of legacy bits identifies local nodes which requires specific processing of sourced requests and returning responses.
  • FIG 7 is a block diagram of one embodiment for bus bridge isochronous transfer.
  • isochronous connections involve one talker 802 and one or more multiple listener 804/controller 806 pairs. Isochronous packets are accepted based on the current channel identification and are retransmitted on the adjacent bus with a new channel ID.
  • a controller 806 establishes an isochronous connection. The isochronous connection enables communication between talker 802 and listener 804. An isochronous connection may be made between a single talker 802 and multiple listeners 804.
  • Isochronous non-overlaid connections proceed as follows: controller 806 sends a message to the final portal 810a in the path towards listener 804. If necessary, portal 810a forwards the message to the first portal on the path between the listener 804 and talker 802 (in this case, portal 808a).
  • Portal 808a acquires isochronous resources from IRM 825 on its bus. IRM may be located within portal 808a or any other node. The message is forwarded towards the talker bus 805, which results in the message being received by portal 808b.
  • Portal 808b acquires the isochronous resources in IRM 825 and updates the oPCR within talker 802. The message is forwarded back toward listener 804, which results in it being received by portal 808a.
  • Portal 808a updates the iPCR on listener 804 so that it listens to the correct channel.
  • Portal 808a forwards a message-complete indicator to controller 806.
  • a disconnect message is sent from controller to portal 810b.
  • Portal 810b forwards the message to portal 808a which updates the iPCR on listener 804 and releases the IRM resources associated with bus 807.
  • the message is forwarded to portal 808b.
  • the oPCR of talker 802 is updated in order to stop transmission.
  • Portal 808b updates the IRM resources associated with bus 805.
  • a completion message is then sent from portal 808b to controller 806.
  • controller 806 sends a disconnect message toward listener 810a, which results in the message being received by portal 810a.
  • Portal 810a forwards the message to portal 808a (the talker side portal of listener 804).
  • Portal 808a forwards the message towards talker 802, which results in the message being received by portal 808b.
  • Portal 808b updates the oPCR of talker 802 in order to stop transmission.
  • Portal 808b accesses IRM 825 to release isochronous channel and bandwidth resources associated with bus 805.
  • Portal 808b forwards the message toward listener 804, which results in the message being received by portal 808a.
  • Portal 808a updates the iPCR of listener 804 in order to stop listener 804 from listening.
  • Portal 808a updates the IRM isochronous resources associated with bus 807.
  • Portal 808a then sends a completion message to controller 806.
  • FIG 8 is a block diagram of another embodiment for a bus bridge isochronous transfer.
  • Talker 902 is connected by controller 906 to listener 904.
  • controller 906 may be on the talker bus 905, listener bus 915, or other bus.
  • Each listener 904 is associated with a controller 906.
  • the controller 906 may be the same or different for the various listeners 904.
  • the connection message from controller 906 is processed by portal 912a in which it is found to have the same stream ID. This allows the new listener to listen to the perversely established channel.
  • a disconnect message is sent from controller 906 towards listener 904, which results in the message being received by portal 912a.
  • Portal 912a updates the iPCR of listener 904 in order for listener 904 to stop listening.
  • Portal 912a decrements its use count and returns a completion message to controller 906.
  • Messages are exchanged between the talker 902 and listener's controller 906 when a change in the bandwidth allocated for isochronous data traffic is requested. For example, a change in bandwidth may be requested when a talker 902, sending highly compressed isochronous video data, begins sending lightly compressed isochronous video data to a listener 904. The increased data rate of video requires an increase in the allocated bandwidth for isochronous traffic of the bus reaching the talker.
  • the message from the talker 902 to the listener's controller follows the same data path used when the isochronous connection was originally established.
  • the system uses the isochronous data path as a way of multicast distributing of both asynchronous messages as well as isochronous data. There may be multiple listeners and each listener may be associated with a distinct controller.
  • FIG. 9 is a block diagram of another embodiment for bus bridge isochronous transfer using a mechanism of partially overlaid bus connections.
  • partially overlaid isochronous connections or disconnections involve one talker 1002 and one or more multiple listener 1024/controller 1006 pairs.
  • a partially overlaid isochronous connection connects a listener to a talker through an existing connection. For example, connecting listener 1024 to the portal 1016 enables listener 1024 to listen to the talker 1002 because portal 1016 is already connected to talker 1002.
  • the partially overlaid isochronous disconnection removes a listener from a previously established connection.
  • Isochronous partially overlaid connections proceed as follows: controller 1006 sends a content message to the listener bus 1012b.
  • Listener bus portal is also the listener's talker-path portal.
  • the talker-path portal 1002b accesses IRM, which could be on any node, to acquire isochronous bandwidth and channels.
  • portal 1002b forwards the content message to portal 1002a.
  • portal 1002b detects matching stream identifications, it increases its use count.
  • Portal 1002a subsequently returns a message to portal 1002a indicating which channel the listener 1024 should listen.
  • Portal 1002b updates the iPCR within listener 1024.
  • Portal 1002b sends a message of connection completion to controller 1006.
  • isochronous partially overlaid disconnection proceeds as follows: controller 1006 forwards a content message to listener 1024 via portal 1002b for disconnection or stop listening. When portal 1002b receives the content message, portal 1002b writes the iPCR within the listener 1024. Next, portal 1002b releases bus 1005, channel, and bandwidth. Portal 1002b subsequently forwards the content message to portal 1002a, which stops listening. Portal 1002a forwards the content message to portal 1012a in which the portal 1012a decrements use count. A message of disconnection completion is forwarded to controller 1006.
  • isochronous partially overlaid disconnection proceeds as follows: controller 1006 forwards a content message to listener 1024 in which listener 1024 stops listening. The message is forwarded to talker 1002. When portal 1012a receives the message, it decrements use count and sends the message toward listener 1024 in which portal 1002a receives the message first. Once the message is received, portal 1002a stops listening and forwards the message to portal 1002b. After portal 1002b receives the message, it writes iPCR within listener 1024 and subsequently releases bus 1005 and IRM resources. After releasing the resources, portal 1002b sends a completion message to controller 1006.
  • Bandwidth adjustment messages do not require any additional routing tables, since the messages flow through bus bridges in the same manner that communication connections are initially established. Furthermore, bus bridge portals need no modification to handle bandwidth adjustment requests, since the requests are handled by controllers.
  • the oPCR of talker 1002 indicates the current bandwidth allocated for isochronous data on the talker 1002 bus.
  • the oPCR is updated to reflect the new bandwidth.
  • talker 1002 senses that more bandwidth will be needed. By updating its oPCR, the talker 1002 requests from IRM 1012c that the bandwidth be increased for bus transactions. IRM 1012c senses a change in bandwidth as indicated by the updated oPCR and instigates a series of message transactions. The message transactions indicating a bandwidth change are sent from the talker 1002 towards the listener portal 1002b, through any intermediary portals 1012a, 1016a, 1002a. The listener portal 1002b forwards the message to the listener controller 1006. Finally, the listener controllers re-establish the talker 1002 - to - listener 1024 connection with the revised bandwidth parameters. The same flow occurs between talker 1002 and listener 1004.
  • Talker 1002 is connected via talker bus 1005 with IRM 1012c.
  • the IRM 1012c is located in bus bridge talker portal 1012b.
  • the IRM 1012c may be an independent node connected to any point on the data bus.
  • the IRM 1012c detects the bandwidth change when it is accessed by the talker bus transaction.
  • IRM 1012c is connected via portals 1012a, 1016a, and 1016b with controller 1006.
  • the bus bridge identifies the data packet using the packet's unique stream identifier.
  • a listener portal 1002b also stores the stream identity of the data stream between talker 1002 and listener 1024 in a pilot proxy.
  • the pilot proxy stores the comrnunication channel identity of the data stream out of the talker 1002 and the channel of the data stream into the listener.
  • the talker portal 1012b allocates the bandwidth required or de-allocates the bandwidth released by the request.
  • the talker portal 1012b also records which node requested the bandwidth change.
  • Talker portal 1012b maintains knowledge of which controller and listeners are paired together— that is which controller initially set-up the listener connection.
  • Controller 1006 acquires any bandwidth required from the talker portal 1012b.
  • the talker portal 1012b informs neighboring intermediary portals of the bandwidth change via a listener tag.
  • the listener tag keeps track of all the bus addresses of the controllers as well as the addresses of listeners.
  • IRM 1012c is connected via intermediary bus 1015 with another listener 1004, and intermediary portal 1012a. As with the talker portal 1012b, intermediary portal 1012a allocates the bandwidth required or released by the bandwidth change request generated by talker 1002. Intermediary controllers adjust the bandwidth of the data bus it controls via the intermediary portal. Thus, the IRM 1012c sends the bandwidth change request to all components between the talker 1002 and listener 1024 that use the information. In one embodiment, multiple listeners may exist, where each listener may be associated with a distinct controller. Each controller would update its bandwidth allocations as described above. Thus all controllers between the talker 1002 and listener 1024 are informed of the bandwidth changes.
  • Intermediary bus 1015 is connected via listener portal 1002b, intermediary portals 1002a, 1016a, and listener portal 1002b with listener bus 1025.
  • listener portal 1002b allocates the bandwidth required or released by the bandwidth change request generated by talker 1002.
  • Listener controller 1006 adjusts the bandwidth of the data bus it controls via the listener portal 1002b.
  • the listener portal 1002b stores the bus address of listener 1024 and controller 1006.
  • One listener tag is stored in the listener portal 1002b.
  • the listener tag identifies the node identity of listener 1024, the node identity of the controller 1006, and the plug identity of the listener 1024.
  • the listener portal 1002b also stores the stream identity of the data stream between talker 1002 and listener 1024 in a pilot proxy.
  • the pilot proxy stores the communication channel identity of the data stream out of the talker 1002 and the channel of the data stream into the listener.
  • controller 1006 Upon receipt of the bandwidth change request, controller 1006 initiates a standard reconnection or disconnection procedure, with the revised bandwidth parameters as discussed above. Thus, if the controller 1006 is unable to acquire the bandwidth, standard error messages are generated, just as if the controllers were unable to acquire the bandwidth during initialization of the bus connections. Furthermore controller 1006 determines how much additional bandwidth is necessary. Until controller 1006 negotiates new bandwidth parameters with their respective bus bridges, the bus bridges enforce the old bandwidth parameters.
  • FIG. 10 is a flow diagram of one embodiment for adjusting the bandwidth allocations on interconnected data buses.
  • a brief overview of the techniques include the talker 1002 sensing that more bandwidth will be needed. By updating its oPCR, the talker 1002 requests from IRM 1012c that the bandwidth be increased for bus transactions. IRM 1012c senses a change in bandwidth as indicated by the updated oPCR and instigates a series of message transactions. The message transactions indicating a bandwidth change are sent from the talker 1002 towards the listener controller 1006, through any intermediary portals 1012a, 1016a. The listener portal 1002b forwards the message to the listener controller 1006. Finally the listener controllers re-establish the talker 1002 - to - listener 1024 connection with the revised bandwidth parameters.
  • talker 1002 requests a bandwidth change from IRM 1012c.
  • this bandwidth adjustment request is passed on to a talker portal 1012b.
  • the talker portal 1012b determines if the next portal on the bus is the listener portal 1002b. If the next portal is not the listening portal, processing continues at processing block 1140. If the next portal is the listener portal, processing continues at processing block 1160.
  • talker portal 1012b informs the intermediary portal of the bandwidth change.
  • the bandwidth change request is passed to controller 1040 associated with the intermediary portal.
  • talker portal 1012b informs the listener of the bandwidth change.
  • listener controller 1006 acquires any additional bandwidth required from the listener portal 1002b.
  • listener 1006 returns an acknowledgment to the talker 1002.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)

Abstract

L'invention concerne un procédé et un système d'ajustement de largeur de bande attribuée au trafic de données isochrones sur un bus de données mis en interconnexion. Le système fait appel à un gestionnaire de ressources isochrones (1012c) installé sur une passerelle de bus, afin de pouvoir déceler une demande de changement de largeur de bande émanant de tel ou tel locuteur (1002). Le gestionnaire de ressources isochrones procède à un ajustement de largeur de bande correspondant à la demande de changement de largeur de bande destinée à un ou plusieurs portails de passerelle de bus (1012).
PCT/US2000/042429 1999-11-29 2000-11-29 Procede et systeme d'ajustement de largeur de bande isochrone sur un bus WO2001038996A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU36438/01A AU3643801A (en) 1999-11-29 2000-11-29 Method and system for adjusting isochronous bandwidths on a bus

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US16795899P 1999-11-29 1999-11-29
US60/167,958 1999-11-29
US09/531,075 2000-03-18
US09/531,075 US6539450B1 (en) 1998-11-29 2000-03-18 Method and system for adjusting isochronous bandwidths on a bus

Publications (2)

Publication Number Publication Date
WO2001038996A1 WO2001038996A1 (fr) 2001-05-31
WO2001038996A9 true WO2001038996A9 (fr) 2002-08-01

Family

ID=26863659

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/042429 WO2001038996A1 (fr) 1999-11-29 2000-11-29 Procede et systeme d'ajustement de largeur de bande isochrone sur un bus

Country Status (2)

Country Link
AU (1) AU3643801A (fr)
WO (1) WO2001038996A1 (fr)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6539450B1 (en) 1998-11-29 2003-03-25 Sony Corporation Method and system for adjusting isochronous bandwidths on a bus
EP1263172A3 (fr) * 2001-05-29 2002-12-18 Thomson Licensing S.A. Méthode pour contrôler des ressources d'un lien dans un réseau de transmission
FI20011257A0 (fi) * 2001-06-13 2001-06-13 Nokia Corp Menetelmä väylän mukauttamiseksi ja väylä
KR100982173B1 (ko) * 2001-11-23 2010-09-15 톰슨 라이센싱 브리지를 포함하는 통신 네트워크에서의 연결을 관리하는방법 및 디바이스
KR101224594B1 (ko) * 2005-04-28 2013-01-22 삼성전자주식회사 브리지 랜에서의 보장 서비스 방법 및 장치
US7698492B2 (en) * 2005-04-28 2010-04-13 Samsung Electronics Co., Ltd. Guaranteed services method and apparatus in bridged LAN

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1996041274A1 (fr) * 1995-06-07 1996-12-19 Advanced Micro Devices, Inc. Bus de donnees pouvant etre reconfigure de façon dynamique
JP3271493B2 (ja) * 1995-09-26 2002-04-02 ヤマハ株式会社 ネットワークおよびデータ伝送方法
US5754807A (en) * 1995-11-20 1998-05-19 Advanced Micro Devices, Inc. Computer system including a multimedia bus which utilizes a separate local expansion bus for addressing and control cycles
DE19636381C1 (de) * 1996-09-09 1998-03-12 Ibm Bus mit anforderungsabhängiger Anpassung der in beiden Richtungen zur Verfügung stehenden Bandbreite
US6185632B1 (en) * 1998-10-19 2001-02-06 Hewlett-Packard Company High speed communication protocol for IEEE-1394 including transmission of request and reply writes to a datagram-FIFO-address to exchange commands to end a job

Also Published As

Publication number Publication date
AU3643801A (en) 2001-06-04
WO2001038996A1 (fr) 2001-05-31

Similar Documents

Publication Publication Date Title
US6539450B1 (en) Method and system for adjusting isochronous bandwidths on a bus
US6389547B1 (en) Method and apparatus to synchronize a bus bridge to a master clock
US6445711B1 (en) Method of and apparatus for implementing and sending an asynchronous control mechanism packet used to control bridge devices within a network of IEEE STD 1394 serial buses
US6950394B1 (en) Methods and systems to transfer information using an alternative routing associated with a communication network
US5991831A (en) High speed serial communications link for desktop computer peripherals
US6728821B1 (en) Method and system for adjusting isochronous bandwidths on a bus
US6631415B1 (en) Method and system for providing a communication connection using stream identifiers
US6374316B1 (en) Method and system for circumscribing a topology to form ring structures
EP0930747A1 (fr) Système à bus série IEEE-1394 utilisant une table de correspondences pour identifier des noeuds ayant des caractéristiques nécessaires pour établir des connexions isochrones
US6810452B1 (en) Method and system for quarantine during bus topology configuration
EP1124357B1 (fr) Procédé et dispositif de communication entre un premier et un second réseau
EP1327328B1 (fr) Procede permettant de connecter plusieurs bus de communication par des liaisons sans fil
US6647446B1 (en) Method and system for using a new bus identifier resulting from a bus topology change
US6910090B1 (en) Maintaining communications in a bus bridge interconnect
US6286067B1 (en) Method and system for the simplification of leaf-limited bridges
US6751697B1 (en) Method and system for a multi-phase net refresh on a bus bridge interconnect
US6584539B1 (en) Method and system for message broadcast flow control on a bus bridge interconnect
WO2001038996A9 (fr) Procede et systeme d'ajustement de largeur de bande isochrone sur un bus
US6502158B1 (en) Method and system for address spaces
US6633943B1 (en) Method and system for the simplification of leaf-limited bridges
WO2001042877A2 (fr) Procede et systeme destines a ameliorer la largeur de bande dans un pont de bus
WO2000057263A1 (fr) Procede et systeme de regeneration globale multiphase sur une interconnexion bus-pont
EP1769607B1 (fr) Procede de creation d'un tableau d'informations specifiques de stations dans un reseaux de stations distribuees, et station reseau destinee a la mise en oeuvre de ce procede
WO2001038951A2 (fr) Procede et systeme permettant de circonscrire une topologie pour former des structures annulaires
WO2000057289A1 (fr) Procede et systeme de commande du debit de diffusion de messages sur une interconnexion de pont de bus

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
AK Designated states

Kind code of ref document: C2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: C2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

COP Corrected version of pamphlet

Free format text: PAGES 1/10-10/10, DRAWINGS, REPLACED BY NEW PAGES 1/10-10/10; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP