US 5,694,555 AGrant

Method and Apparatus for Exchanging Data, Status, and Commands Over an Hierarchical Serial Bus Assembly Using Communication Packets

Issue Date:1997-12-02

•18 Claims

•28 Drawing Sheets

Abstract

Circuitry and complementary logic are provided to a bus controller, a number of 1:n bus signal distributors, and a number of bus interfaces of an hierarchical bus assembly for conducting data communication transactions between bus agents interconnected to the hierarchical bus assembly. The hierarchical serial bus assembly is used to serially interface a number of isochronous and asynchronous peripherals to the system unit of a computer system. These circuitry and complementary logic of the serial bus elements implement a number of elemental packets and a number of transaction protocols, employing a master/slave model of transaction flow control. Data communication transactions are conducted using the elemental packets and in accordance to the transaction protocols. In some embodiments, these circuitry and complementary logic of the serial bus elements are also used to conduct connection management transactions between the serial bus elements. The connection management transactions are conducted in like manner as the data communication transactions.

Metadata

Assignee

Intel Corporation

Inventors

Jeff Charles Morriss
Shaun Knoll
Puthiya Kottal Nizar
Richard M. Haslam
Ajay V. Bhatt
Sudarshan Bala Cadambi

Application Information

Application Number:US 6198635

Filing Date:1996-03-19

Priority Date:1994-10-31

Art Unit:235

Classifications

IPC:

G06F 1300

Field of Search:

395280;285;309

Patent Drawings (28 sheets)

Description

Background of the Invention

1. Field of the Invention

The present invention relates to the field of computer systems. More specifically, the present invention relates to serial buses for connecting peripherals to the system units of computer systems, including the associated controllers and interfaces.

2. Background Information

A number of interrelated considerations is making it desirable to have a single, relatively fast, bi-directional, isochronous, low-cost, and dynamically configurable serial bus for simultaneously connecting isochronous as well as asynchronous peripherals to the system unit of a desktop computer system. Isochronous peripherals are peripherals that generate real time natural data such as voice, motion video, and the like. These interrelated considerations include:

Connection of the Telephone to the Desktop Computer

It is expected that the merging of computing and communication will be the basis of the next generation of productivity applications on desktop computers. The movement of machine oriented and human oriented data types from one location or environment to another depends on ubiquitous and cheap connectivity. Unfortunately, the computing and communication industries have evolved independently. As a result, a wide range of desktop computer and telephone interconnects have to be supported.

Ease of Use

The lack of flexibility in reconfiguring desktop computers has been acknowledged as its Achilles heel to it's further development. The combination of user friendly graphical interfaces and the hardware and software mechanisms associated with the new generation of system bus architectures have made desktop computers less confrontational and easier to reconfigure. However, from the enduser point of view, the desktop computer's I/O interfaces such as serial/parallel ports, keyboard/mouse/joystick interfaces, still lack the attributes of plug and play or too limiting in terms of the type of I/O devices that can be live attached/detached.

Port Expansion

The addition of external peripherals to desktop computers continues to be constrained by port availability. The lack of a bi-directional, low-cost, low to mid speed peripheral bus has held back the proliferation of peripherals like telephone/fax/modem adapters, answering machines, scanners, personal digital assistants (PDA), keyboards, mouses, etc. Existing interconnects are optimized for one or two point products. As each new function or capability is added to the desktop computer, typically a new interface has been defined to address this need.

In other words, this desired serial bus is expected to provide low cost simultaneous connectivity for the relatively low speed 10-100 kbps interactive devices such as keyboard, mouse, stylus, game peripherals, virtual reality peripherals, and monitors, as well as the moderate speed 500-5000 kbps isochronous devices such as ISDN, PBX, POTS, and other audio devices. A multiplicity of both types of devices are expected to be connected and active at the same time, and yet the latter type of devices are provided with guaranteed latencies and bandwidths. Furthermore, the devices are expected to be hot attached and detached, with the serial interface being able to dynamically reconfigure itself without interrupting operation of the desktop computer system.

There are several technologies that are commonly considered to be serial buses for connecting peripherals to system units of computer systems. Each of these buses is designed to handle a specific range of communications between system units and peripherals. Particular examples of these buses include:

Apple.RTM. Desktop Bus (ADB): ADB is a proprietary bus of Apple Computer Inc. It is a minimalist serial bus that provides a simple read/write protocol to up to 16 devices. Only basic functions are required of the controller and interface hardware. Thus, the implementation cost is expected to be low. However, ADB supports data rates only up to 90 kbps, just enough to communicate with asynchronous desktop devices such as keyboards and mouses. It is not capable of simultaneously supporting the moderate speed isochronous devices discussed earlier.

Access.bus (A.b): A.b is developed by the Access.bus Industry Group. It is based on the I.sup.2 C technology of Philips Corporation and a software model of Digital Equipment Corporation (DEC). A.b is also designed primarily for asynchronous devices such as keyboards and mouses. However A.b is generally considered to be more versatile than ADB. A.b's protocol has well defined specifications for dynamic attach, arbitration, data packets, configuration and software interface. Moderate amount of functions are required of the controller and interface hardware. Thus, the implementation cost is only marginally competitive for the desired desktop application. While addressing is provided for up to 127 devices, the practical loading is limited by cable lengths and power distribution considerations. Revision 2.2 specifies the bus for 100 kbps operation, but the technology has headroom to go up to 400 kbps using the same separate clock and data wires. However, at 400 kbps, A.b still falls short in meeting the requirements of the moderate speed isochronous devices.

IEEE's P1394 Serial Bus Specification (aka FireWire): FireWire is a high performance serial bus. It is designed primarily for hard disk and video peripherals, which may require bus bandwidth in excess of 100 Mbps. It's protocol supports both isochronous and asynchronous transfers over the same set of 4 signal wires, broken up as differential pairs of clock and data signals. Thus, it is capable of simultaneously meeting the requirements of low speed interactive as well as moderate speed isochronous devices. However, elaborate functions are required of the controller and interface hardware, rendering FireWire to be non-price competitive for the desired desktop application. Moreover, the first generation of devices, based on FireWire's specification, are only just becoming available in the market.

The Concentration Highway Interface (CHI): CHI is developed by American Telephone & Telegraph Corporation (AT&T) for terminals and digital switches. It is a full duplex time division multiplexed serial interface for digitized voice transfer in a communication system. The protocol consists of a number of fixed time slots that can carry voice data and control information. The current specification supports data transfer rates up to 4,096 Mbps. The CHI bus has 4 signal wires: Clock, Framing, Receive Data, and Transmit Data. Both, the Framing and the Clock signals are generated centrally (i.e. PBX switch). Thus, it is also capable of simultaneously meeting the requirements of low speed interactive as well as the moderate speed isochronous devices. Similar to FireWire, elaborate functions are also required of the controller and interface hardware. As a result, CHI is also non-price competitive for the desired desktop application.

As will be disclosed in more detail below, the present invention provides the desired serial bus assembly, including its associated controller, bridging connectors and interfaces, that advantageously overcomes the limitations of the prior art serial buses in a novel manner.

Summary of the Invention

The present invention includes circuitry and complementary logic provided to a bus controller, a number of 1:n bus signal distributors, and a number of bus interfaces of an hierarchical bus assembly for conducting data communication transactions between bus agents interconnected to the hierarchical bus assembly. The hierarchical serial bus assembly is used to serially interface a number of isochronous and asynchronous peripherals to the system unit of a computer system. These circuitry and complementary logic of the serial bus elements implement a number of elemental packets and a number of transaction protocols, employing a master/slave model of transaction flow control. Data communication transactions are conducted using the elemental packets and in accordance to the transaction protocols. In some embodiments, these circuitry and complementary logic of the serial bus elements are also used to conduct connection management transactions between the serial bus elements. The connection management transactions are conducted in like manner as the data communication transactions.

Typically, the bus controller is disposed in the system unit, and interconnected to a number of 1:n bus signal distributors and a number of bus interfaces. The bus interfaces are disposed in the connecting peripherals, one bus interface per connecting peripheral. The peripherals, through their bus interfaces, are generally connected to the system unit, through the bus controller, using one or more of the bus signal distributors. A bus interface is always a termination point. Only a bus signal distributor may have one or more bus signal distributor(s) and/or bus interface(s) connected upstream to it. Together, the system unit, the serial bus elements, and the peripherals form an hierarchy of interconnected devices.

A connecting peripheral may be an isochronous or an asynchronous peripheral. Typically, the isochronous peripherals operate with data rates in the range of 500-5000 kbps, whereas the asynchronous peripherals operate with data rates in the range of 10-100 kbps. Furthermore, a connecting peripheral may be a multi-function peripheral, i.e. multiple functions being mapped to a single bus connection point serviced by a single bus interface.

The elemental packets include a token packet, a handshake packet, and a data packet. Each packet includes a packet identifier identifying the packet type and nature of the packet. Preferably, each packet further includes a leading sync field to aid the interconnected devices in receiving the packet. The transaction protocols include protocols for transactions between the system unit and any one of the functions of the interconnected peripherals, between any two functions of the interconnected peripherals, and between the system unit and any one of the interconnected devices. The elemental packets and transaction protocols are adaptable for data communication as well as connection management transactions employing the master/slave model of flow control.

In embodiments where the various devices are physically interconnected together using low cost two signal wire cables, and electrical signals are propagated between the interconnected devices over the two signal wires in a differential manner, preferably the beginning and the end of a packet is denoted by the "fault" condition of zero difference. In embodiments where the interconnected devices jointly implement geographical addressing for the devices and logical addressing for the functions of the interconnected peripherals, the elemental packets and the transaction protocols further support transactions conducted in either the geographical address space or the logical address space.

Brief Description of Drawings

The present invention will be described by way of exemplary embodiments, but not limitations, illustrated in the accompanying drawings in which like references denote similar elements, and in which:

FIG. 1 illustrates an exemplary computer system incorporating the serial bus teachings of the present invention;

FIG. 2 illustrates one embodiment of the serial bus assembly of FIG. 1 in further detail;

FIG. 3 illustrates a master/slave model of flow control employed by the present invention for serially interfacing the interconnected peripherals to the system unit and controlling transaction flows;

FIG. 4 illustrates a frame based polling schedule of the present invention implemented by some embodiments for polling the slave "devices";

FIG. 5 illustrates geographical and logical addressing of the present invention implemented by some embodiments for addressing serial bus elements and functions of bus agents;

FIG. 6 illustrates the essential elements of communication packets of the present invention implemented by some embodiments for conducting transactions employing the master/slave model of flow control;

FIG. 7 illustrates one embodiment of the cables physically connecting the serial bus elements under the present invention;

FIGS. 8-9 illustrate one embodiment of the bus controller of the present invention including its associated software;

FIGS. 10-11 illustrate one embodiment of the 1:n bus signal distributor of the present invention including its port circuitry;

FIGS. 12-13 illustrate one embodiment of the bus interface of the present invention including its connector circuitry;

FIGS. 14a-14b illustrate one embodiment of the elemental packets of the present invention;

FIG. 15 illustrates one embodiment of the packet identifiers of the elemental packets including the packet types they identify;

FIGS. 16a-16c and 17a-17d illustrate one embodiment of the packet fields of the packet identifiers and their corresponding meanings;

FIGS. 18a-18c illustrate one embodiment of connection management transaction protocols;

FIGS. 19a-19k illustrate one embodiment of data communication transaction protocols;

FIG. 20 illustrates one embodiment of a state machine provided to the bus controller for implementing the above described protocols;

FIG. 21 illustrates one embodiment of a state machine provided to a bus signal distributor for implementing the above described protocols;

FIG. 22 illustrates one embodiment of a state machine provided to a bus interface for implementing the above described protocols.

Detailed Description

In the following description for purposes of explanation, specific numbers, materials and configurations are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to one skilled in the art that the present invention may be practiced without the specific details. In other instances, well known systems are shown in diagrammatic or block diagram form in order not to obscure the present invention.

Hierarchical Serial Bus Assembly for Serially Interfacing Isochronous and Asynchronous Peripherals to a System Unit of a Computer System

Referring now to FIG. 1, a block diagram illustrating an exemplary computer system incorporating the serial bus teachings of the present invention is shown. Exemplary computer system 10 comprises system unit 12 having serial bus controller 14 of the present invention, 1:n bus signal distributors 18 of the present invention, each having n+1 ports 24, and peripherals 16 having bus interfaces 22 of the present invention. Peripherals 16 are coupled to bus controller 14 of system unit 12 through 1:n bus signal distributors 18 and preferably cables 20. Collectively, bus controller 14, bus signal distributors 18, bus interfaces 22, and cables 20 form a serial bus assembly 26 interconnecting bus agents, i.e. system unit 12 and peripherals 16 to each other.

Cables 20 are preferably low cost two signal wires cables 48 and 50 (as illustrated in FIG. 7). However, cable 20 are capable of supporting data transfer rates up to 5 Mbps. Furthermore, when such low cost cables 20 are employed, electrical signals are preferably propagated over the two signal wires 48 and 50 between the interconnected devices 14, 18 and 22 in a differential manner. For examples, a negative voltage differential represents a 1-bit and a positive voltage differential represents a 0-bit. Electrical signals are preferably also used to signal a number of information. For further description of electrical signaling, see U.S. patent application, Ser. No. 08/332,337, entitled Method And Apparatus For Serial Bus Elements Of An Hierarchical Serial Bus To Electrically Represent Data And Control States To Each Other, which is hereby fully incorporated by reference.

Except for bus controller 14, system unit 12 is intended to represent a broad category of system units of computer systems whose constitutions and functions are well known, and will not be otherwise further described. Similarly, except for bus interfaces 22, peripherals 16 are intended to represent a broad category of desktop peripherals, such as keyboards, mouses, monitors, speakers, microphone, telephones, whose constitutions and functions are also well known, and will not be otherwise further described either. Bus controller 14, bus signal distributors 18 and bus interfaces 22 will be described in more detail below with additional references to the remaining figures.

FIG. 2 illustrates one embodiment of the serial bus assembly of FIG. 1 in further detail. For this embodiment, serial bus assembly 26' includes serial bus controller 14, standalone 1:n bus signal distributor 18a, integrated 1:n bus signal distributor 18b, and bus interfaces 22a-22f. The serial bus assembly 26' interconnects bus agents telephone 16a, compound keyboard 16b including keyboard, pen and mouse functions, monitor circuitry 16c of monitor 28, speakers 16d-16e and microphone 16f to system unit 12. Together, the system unit 12, the serial bus elements 14, 18a-18b and 22a-22f, and the interconnected peripherals 16a-16f form an hierarchy of interconnected devices.

Under the present invention, a bus interface 22a-22f is always a termination point. Only a bus signal distributor, e.g. 18a, may have one or more bus signal distributors, e.g. 18b, and/or one or more bus interfaces, e.g. 22a, coupled upstream to it. For the purpose of this disclosure, upstream means "towards the bus controller". Thus, except for the degenerate case where the serial bus assembly 26 has only one connecting peripheral 16, typically it is a bus signal distributor, such as 18a, that is connected upstream to the bus controller 14.

Furthermore, under the present invention, a connecting peripheral may be an isochronous peripheral, such as telephone 16a, speakers 16d-16e, and microphone 16f, or asynchronous peripherals, such as compound keyboard 16b and monitor 16c. The isochronous peripherals may operate with a data transfer rate as high as 5 Mbps, while the asynchronous peripherals may operate with a data transfer rate as high as 100 kbps. Furthermore, a connecting peripheral 16a-16f may be a multiple function peripheral, i.e. multiple functions mapping to a single bus connection point serviced by a bus interface, e.g. 22b. Similarly, although not shown, the system unit 12 may support multiple clients.

FIG. 3 illustrates a master/slave model of flow control employed by the present invention for serially interfacing the interconnected peripherals to the system unit and controlling transaction flow. As illustrated, the bus controller 14, the signal bus distributors 18, and the bus interfaces 22 cooperate to implement the master/slave model of flow control. The bus controller 14 serves as the master, and the signal bus distributors 18 as well as the bus interfaces 22 behave as slave devices to the bus controller 14.

Under the master/slave model, the bus controller 14 provides flow control for all data communication transactions between the bus agents at their respective operating speeds. The bus interfaces 22 engage in data communication transactions on behalf of the functions of the peripherals 16. However, the bus interfaces 22 accept or transmit data only if they have been authorized or instructed (aka "polled") to do so by the bus controller 14. The bus signal distributors 18 serve strictly as signal distributors. They are merely transparent conduits when data communication transactions are conducted by the bus controller 14 and the bus interfaces 22 on behalf of the bus agents. Thus, the bus signal distributors 18 never actively participate in data communication transactions, accept data or respond with data.

The bus controller 14 systematically polls the functions of the interconnected peripherals 16 through their bus interfaces 22 for data communication transactions in accordance to a polling schedule which guarantees latencies and bandwidths to the isochronous functions of the interconnected peripherals 16. Polling of the isochronous functions of the interconnected peripherals 16 for data communication transactions are prioritized over for all other polling and as frequent as they are necessary to meet the guaranty. Polling of the asynchronous functions of the interconnected peripherals 16 through their bus interfaces 22 for data communication transactions are scheduled around the polling of the isochronous functions of the interconnected peripherals 16 for data communication transactions. Preferably, the polling schedule is dynamically adapted to the interconnected peripherals 16 actually present.

In some embodiments, the bus controller 14, the bus signal distributors 18 and the bus interfaces 22 further engage in connection management transactions employing the same master/slave model for flow control. Similarly, the bus controller 14 provides flow control for conducting the connection management transactions at the serial bus elements' respective operating speeds. The bus signal distributors 18 and the bus interfaces 22 respond to the connection management transactions, replying with control/status information as appropriate. The bus controller 14, during operation, polls the bus signal distributors 18 and the bus interfaces 22 for such transactions. Polling of the bus signal distributors 18 and the bus interfaces 22 for connection management transactions are also scheduled around polling of the isochronous functions of the interconnected peripherals 16 for data communication transactions. Preferably, the expanded polling schedule is also dynamically adapted to the serial bus elements actually present.

FIG. 4 illustrate a frame based polling scheduling of the present invention implemented by some embodiments for conducting the various transactions employing the master/slave model of flow control. As illustrated, the polling schedule 30, also referred to a super frame, comprises of a number of sub-schedules 32, also referred to as soft frames. An isochronous function 34a or 34b of an interconnected peripheral 16 is polled as frequent as it is necessary in one or more soft flames 32 of the super frame 30 to guarantee its latency and bandwidth. However, an asynchronous function 36a or 36b is polled only once in one soft frame 32 of the super frame 30 for data communication transaction. Similarly, an interconnected device 38a or 38b is also polled only once in one soft frame 32 of the super frame 30 for connection management transaction.

Preferably, all isochronous functions 34a-34b are polled within a first percentage portion (P1) of a soft frame 32 to ensure the latency and bandwidth guaranties are met. Isochronous functions that cannot be accommodated within P1 are preferably rejected for insufficient capacity. The upper delimiter (M1) of P1 is also referred to as the isochronous watermark. Similarly, all polling are preferably performed within a second percentage portion (P2) of a soft frame 32 to ensure reliability of operation. Multiple soft frames 32 are employed if necessary to accommodate all asynchronous function and serial bus element polling. The upper delimiter (M2) of P2 is also referred to as the frame watermark.

Various manners in which such frame based polling schedule may be dynamically generated and updated, are described in the copending application, Ser. No. 08/331,727, entitled Method And Apparatus For Dynamically Generating And Maintaining Frame Based Polling Schedules That Guaranty Latencies And Bandwidths To Isochronous Functions, which is hereby fully incorporated by reference.

FIG. 5 illustrates geographical and logical addressing of the present invention implemented by some embodiments for addressing the serial bus elements and functions of bus agents. For ease of explanation, the same exemplary serial bus assembly of FIG. 2 is used. However, the bus controller 14 is labeled as Host, also referred to as Hub0. The bus signal distributors 18a-18b are labeled as Hub1 and Hub2. The peripherals 16a-16f including their corresponding bus interfaces 22a-22f are jointly labeled as Node0 through Node6. The functions of peripherals 16a-16f are labeled as FN0, FN1, etc.

As illustrated, the serial bus elements and functions of the bus agents are assigned geographical as well as logical addresses (GEO ADDR & LOG ADDR) of a geographical and a logical address space. More specifically, the Hubs 14, 18a-18b and the Nodes 22a-22f are assigned GEO ADDRes, whereas the functions of the Nodes 16a-16f are assigned LOG ADDRes. Preferably, the Hub identity as well as the upstream port of the Hub may be inferred from the GEO ADDR of a Hub 14, and 18a-18b, and the connecting Hub as well as the connecting port of the connecting Hub may be inferred from the GEO ADDR of a Node 22a-22f. In one embodiment, the LOG ADDRes are assigned to the functions of the Nodes 16a-16f in a chronological manner.

For examples, in the illustrated exemplary application, Hub1 and Hub2 18a and 18b are assigned the GEO ADDRes of "Hub1:Port0" and "Hub2:Port0" respectively, identifying the Hubs 18a and 18b as "Hub1" and "Hub2" respectively, and in each case, the upstream port being "Port0". Node1 and Node4 22b and 22e are assigned the GEO ADDRes of "Hub1:Port2" and "Hub2:Port3" respectively, identifying the connecting Hubs 18a and 18b as "Hub1" and "Hub2" respectively, and the connecting ports of connecting Hubs 18a and 18b as "Port2" and "Port3" respectively. The functions of Node1 16b are assigned the LOG ADDRes of "LA1", "LA2" and "LA3", whereas the function of Node4 16e is assigned the LOG ADDR of "LA6".

Preferably, the GEO ADDRes and the LOG ADDRes are dynamically assigned at power on or reset, and updated in response to live detachment of interconnected devices or attachment of additional devices, by the bus controller 14 in cooperation with the bus signal distributors 18 and the bus interfaces 22. A particular implementation of such dynamic connection management is described in the copending application, Ser. No. 08/332,375, entitled Method And Apparatus For Dynamically Determining And Managing Connection Topology Of An Hierarchical Serial Bus Assembly, which is hereby fully incorporated by reference.

For these embodiments, the GEO ADDRes are used to conduct connection management transactions among the serial bus element, whereas the LOG ADDRes are used to conduct data communication transactions among the functions of the bus agents The separation of the two types of transactions into the two separate address spaces facilitate dynamic connection management of the serial bus elements, without having to interrupt services to the functions of the bus agents.

FIG. 6 illustrates the essential elements of communication packets of the present invention implemented by some embodiments for conducting the various transactions employing the master/slave model of flow control. For these embodiments, packet identifiers 44 are employed to differentiate control packets from data packets. Control packets are packets employed by the bus controller 14 to authorize or instruct the bus signal distributors 18 and the bus interfaces 22 to engage in transactions. Control packets may also include packets employed by the bus signal distributors 18 and the bus interfaces 22 to acknowledge authorizations or instructions from the bus controller 14. Furthermore, addresses 46 are employed as appropriate to identify the transaction parties. As will be appreciated that under the master/slave model of flow control, the bus controller 14 as a transaction participant may often be inferred, and therefore its address may be omitted.

Preferably, transaction flow, such as from bus controller 14 to a function, from a first function to a second function, may be inferred from the packet identifiers 44. Preferably, either geographical or logical addresses 46, i.e. "HubX:PortY" or "LAz", may be specified to accommodate those embodiments that support connection management transactions and implement both types of addresses.

A particular implementation of employing such communication packets to conduct the various transactions will be described in more detail below.

FIGS. 8-9 illustrate one embodiment of the bus controller of the present invention. In this embodiment, the bus controller 14 includes a control state machine and circuitry 52, control/status registers 54, data buffers 56, and bus controller software services 58. The control/status registers 54 are used to store the various control and status data. For examples, the serial bus elements present, their interconnection topology, the functions of the various interconnected peripherals, the geographical addresses assigned to the serial bus elements, the logical addresses assigned to the functions of the interconnected peripherals. The data buffers 56 are used to buffer the data of the data communication transactions between the bus agents. The control state machine and circuitry 52 operates the hardware, controlling data communication transactions and employing the above described master/slave model of flow control, under the programming of the bus controller software services 58. For some embodiments, the control state machine and circuitry 52 further operates the hardware, controlling connection management transactions, implementing the master/slave model of flow control with frame based polling schedule, employing geographical and logical addressing, supporting communication packet based transactions, and/or inference of data and control states from states of the propagation electrical signals. In particular, the control and state machine circuitry 52 causes the bus controller 14 to cooperate with the bus signal distributors 18 and the bus interfaces 22, and conduct the various transactions using the elemental packets and protocols of the present invention, which will be described in more detail below.

The bus controller software services 58 program the control state machine and circuitry 52 responsive to the operating system 60 and other software such as device and configuring software 62 and 64 of the system unit 12. In particular, the services include connection management such as detection of serial bus elements present, detection of their interconnection topology, detection of the functions of the interconnected peripherals, and assignment of the geographical and logical addresses. The services further include transaction management such as generation and maintenance of the polling schedule, polling of the serial bus elements and functions of the bus agents, acknowledgment of certain responses of the serial bus elements and functions of the bus agents, and exchange of data with functions of the bus agents.

For a more detailed descriptions of the bus controller hardware and the bus controller software services 58, refer to the incorporated by reference copending applications, Ser. Nos. 08/332,375, 08/331,727, and 08/332,337. It should be noted that the allocation of functions to the hardware and software services of the bus controller 14 is implementation dependent. The present invention may be practiced with any number of allocations, ranging from minimal hardware usage to minimal employment of software services.

FIGS. 10-11 illustrate one embodiment of the bus signal distributor of the present invention. The illustrated embodiment is a 1:7 bus signal distributor 18' having control circuitry 66, control registers 68, and 8 ports 24. Port 0 24 is used to connect the bus signal distributor 18' upstream to the bus controller 14 or another bus signal distributor 18. Ports 1-7 are used to connect up to a total of 7 bus signal distributors 18 and/or bus interfaces 22 to itself. The control registers 68 are used to store its own control and status information such as whether a port 24 has a bus interface 22 connected to it or not, and whether the port 24 is turned ON/OFF. The control circuitry 66 operates the bus signal distributor 18' responsive to instructions from the bus controller 14. In particular, the control circuitry 66 causes the bus signal distributor 18 to cooperate with the bus controller 14, and conduct the various transactions using the elemental packets and protocols of the present invention, which will be described in more detail below.

In embodiments where the low cost two signal wire cables 20 are used to interconnect the serial bus elements, and electrical signals are preferably propagated in a differential manner, each port 24 comprises two differential amplifiers 70 and 72 for generating the differential signals. Preferably, each port 24 further having two resistors 74 coupled to ground as shown, pulling the signals on the two wires to ground, thereby allowing the absence or presence of a connected bus interface 22 to be discernible. The appropriate values of resistors 74 may be determined empirically depending on individual implementations.

For a more detailed descriptions of the control circuitry 64 and its cooperative relationship with the bus controller 14, refer to the incorporated by reference copending application, Ser. No. 08/332,375.

FIGS. 12-13 illustrate one embodiment of the bus interfaces of the present invention. For this embodiment, the bus interface 22 comprises control circuitry 80, control/status registers 82, a Hub interface 84 and two FIFOs 76-78, a Receive FIFO 76 and a Send FIFO 78. Receive and Send FIFOs 76-78 are used to stage the receive and send data for data communication transactions. The control/status registers 68 are used to store its own control and status information such as its assigned geographical address, functions of its "host" peripheral, and their assigned logical addresses. The control circuitry 66 operates the bus interface 22 on behalf of the "host" peripheral and the "host" peripheral's functions, responsive to authorizations and instructions from the bus controller 14. In particular, the control circuitry 80 causes the bus interface 22 to cooperate with the bus controller 14, and conduct the various transactions using the elemental packets and protocols of the present invention, which will be described in more detail below.

In embodiments where the low cost two signal wire cables 20 are used to interconnect the serial bus elements, and electrical signals are preferably propagated in a differential manner, the connector interface 84 comprises two differential amplifiers 86 and 88 for generating the differential signals. Preferably, the connector interface 84 further includes two resistors 90 coupled to Vcc as shown, pulling the signals on the two wires to Vcc complementary to the port circuitry of a connecting bus signal distributor 18. The appropriate values of resistors 90 may also be determined empirically depending on individual implementations.

For a more detailed description of the bus interface 22, refer to the incorporated by reference copending applications, Ser. Nos. 08/332,375, 08/331,727, and 08/332,337.

Data Communication Transactions and Connection Management Transactions

Having now described the hierarchical serial bus assembly 26 and the manner its element cooperate to serially interface the isochronous and asynchronous peripherals 16 to the system unit 12 of the exemplary computer system 10, the elemental packets and protocols employed under the present invention to conduct the various transactions will now be described in detail.

FIGS. 14a-14b illustrate one embodiment of the elemental packets of the present invention. As shown, the elements packets include token packets 502-506, handshake packets 508 and data packets 510-512. For embodiments that support geographical addressing and logical addressing, different packet formats are provided for geographically addressed token packets 502 and logically addressed token packets 504-506. Furthermore, separate packet formats are provided for logically addressed host-function token packet 504 and logically addressed function-function token packet 506. Similarly, different packet formats are provided for geographically addressed data packets 510 and logically addressed data packets 512.

Each packet 502-512 includes a leading Sync field to facilitate receipt of the packet 502-512 by a serial bus element. Each packet 502-512 further includes a packet identifier field (PID) for identifying the packet type and the nature of the packet. Each token/data packet 502-506 or 510-512 further includes at least one geographic/logical address identifying the recipient serial bus element. A geographically addressed data packet 510 further includes an Offset field identifying a specific storage location of the recipient serial bus element, whereas a logically addressed data packet 512 further includes a Source field identifying the source serial bus element. Each data packet 510-512 further includes a data length field and the data themselves. Lastly, a logically addressed data packet 512 may further include a CRC check field.

FIG. 15 illustrates one embodiment of the packet identifiers of the elemental packets including the packet types they identify. For the illustrated embodiment, each packet identifier (PID) includes a packet type field (PT) and a parameter field (PF). In one embodiment, PT is 3 bits wide, identifying exemplary packet types, such as logical data packet (LOGD), geographical data packet (GEOD). FIGS. 16a-16c and 17a-17d illustrate one embodiment of the packet fields of the packet identifiers and their corresponding meanings. In one embodiment, PF is also 3 bits wide, identifying exemplary meanings, such as receive buffer cannot accept data (RCVNACK) for a handshake packet, enable port N (PENB) for a geographically addressed token packet, global function reset for a logically addressed token packet, isochronous block data packet for a logically addressed function to function token packet, host source packet for a geographically addressed host to function token packet, assign geographical address for a geographically addressed data packet, and perform CRC check for a logically addressed data packet.

FIGS. 18a-18c illustrate one embodiment of connection management transaction protocols. As shown, for the illustrated embodiment, connection management transaction protocols include a non-responsive geographical transfer protocol 518, a responsive geographical write transfer protocol 520, and a responsive geographical read transfer protocol 522. Under the non-responsive geographical transfer protocol 518, the bus controller 14 broadcasts a non-responsive geographical token packet. Each interconnected bus signal distributor 18 or bus interface 22 decodes the token packet and provides no response. Under the responsive geographical write transfer protocol 520, the bus controller 14 broadcasts a geographical token packet having a destination address. Each bus signal distributor 18 or bus interface 22 decodes the token packet. If the addressed bus signal distributor 18 or bus interface 22 can accept data, it transmits an acknowledgment handshake packet. The bus controller 12 decodes the acknowledgment handshake packet, and sends the data. The addressed bus signal distributor 18 or bus interface 22 then accepts the data. Under the responsive geographical read transfer protocol 522, the bus controller 14 broadcasts a geographical token packet having a destination address. Each bus signal distributor 18 or bus interface 22 decodes the token packet. If the addressed bus signal distributor 18 or bus interface 22 can send data, it transmits the data. The bus controller 12 then accepts the data.

FIGS. 19a-19k illustrate one embodiment of data communication transaction protocols. As shown, for the illustrated embodiment, data communication transaction protocols include host-function transfer protocols for sending and accepting data, with or without CRC checking, 524-534, host sending attention request protocol 536, and function-function transfer protocols for sending and accepting data, with or without CRC checking 538. For example, under the host-function accept data no CRC checking protocol 524, the bus controller 14 broadcasts a logically addressed token packet having a destination address. Each function decodes the token packet. If the function can accept data, it transmits an acknowledgment handshake packet. The bus controller 12 decodes the acknowledgment handshake packet, and sends the data. The function then accepts the data. As a further example, under the host sending attention request protocol 536, the bus controller 14 broadcasts a logically addressed token packet having a destination address. Each function decodes the token packet. The function then transmits a NULL or ATTN handshake packet. The bus controller 12 decodes the NULL or ATTN handshake packet. As yet another example, under the host-function accept data no CRC checking protocol 538, the bus controller 14 broadcasts a logically addressed token packet having a source and a destination address. Each function decodes the token packet. The source function waits for an acknowledgment handshake packet, whereas if the destination function can accept data, it transmits an acknowledgment handshake packet to the source function. The source function decodes the acknowledgment handshake packet, and sends the data. The destination function then accepts the data.

FIG. 20 illustrates one embodiment of a state machine 600 provided to the bus controller 14 for implementing the above described protocols. State machine 600 comprises ten states 602-620 and twenty seven state transitional rules or events (EV1-EV27).

At power on or reset (EV1), state machine 600 enters idle state 602, and stays in idle state 602, as long as there is no transaction to be conducted among bus controller 14, bus signal distributor 18, and bus interfaces 22 (including the functions interfaced), and it is not time to poll the next bus signal distributor 18, bus interface 22 or function (EV2).

On the other hand, if it is time to poll, and there is at least one transaction to be performed (EV3, EV12 or EV19), state machine 600 enters either the state of authorizing a transaction from the bus controller 14 to a function, state 604, or authorizing a transaction from a function to bus controller 14, state 610, or authorizing a transaction between two functions, state 616, depending on the nature of the transaction to be performed.

While in state 604, state machine 600 authorizes a function to receive data from bus controller 14. State machine 600 then either stays in the state if a reply with respect to the readiness of the function to accept data has not been received, and time for receiving the reply has not expired (EV4), or returns to idle state 602 if the function replies that it cannot accept data, or time for receiving reply has expired (EV5), or enters the state of sending control/status or data 606, if the function replies to the effect that it is ready to accept data (EV6).

While in state 606, state machine 600 sends data to the destination function. State machine 600 then either stays in the state if indication denoting whether CRC checking is to be performed has not been output yet, and time for outputting the indication has not expired (EV7), or returns to idle state 602 if indication denoting no CRC checking has been output, or time for outputting the indication has expired (EV8), or enters the state of waiting for CRC acknowledgment 608 if indication denoting CRC has been output.

While in state 608, state machine 600 waits for the CRC checking results. State machine 600 either stays in the state if the destination function has not replied with either CRC pass or failed, and time for reply has not expired (EV10), or returns to idle state 602 if the destination function has replied with either CRC pass or CRC failed, or time for reply has expired (EV11).

While in state 610, state machine 600 authorizes a source function to send data to bus controller 14. State machine 600 then either stays in the state if the source function has provided neither data or a null, and time for providing data/null has not expired (EV13), or returns to idle state 602 if the source function has provided a null, or time for providing data or a null has expired (EV14), or enters the state of receiving control/status or data 612, if the source function has provided a data packet (EV15).

While in state 612, state machine 600 completes the transaction. State machine 600 then either stays in the state if source function has output an indication on whether CRC checking is necessary or not, and time for outputting the indication has not expired (EV16), or returns to idle state 602 if the source function has output an indication of no CRC checking, or time for outputting the indication has expired (EV18), or enters the state of issuing CRC acknowledgment 614 if the source function has outputting an indication of CRC checking (EV17).

While in state 614, state machine 600 issues the CRC acknowledgment and then returns to idle state 602.

While in state 616, state machine 600 authorizes a source function to send data to a destination function. State machine 600 then either stays in the state if the destination function has not responded with a "can accept data" or "cannot accept data" response, and time for providing the response has not expired (EV20), or returns to idle state 602 if the destination function responded with "cannot accept data" or time to respond has expired (EV22), or enters the state waiting for data 618, if the destination function responded with "can accept data" (EV21).

While in state 618, state machine 600 waits for data transfer from the source function to the destination function to complete. State machine 600 then either stays in the state if indication for CRC or no CRC checking has not been output by the source function, and time for outputting such indication has not expired (EV23), or returns to idle state 602 if indication for no CRC checking has been output, or time for outputting the indication has expired (EV25), or enters the state of issuing CRC acknowledgment 620 if indication for CRC checking has been output by the source function (EV24).

While in state 620, state machine 600 monitors for issuance of a CRC acknowledgment by the destination function. State machine 600 stays in the state if the destination function has not output either CRC pass or CRC failed, and time for outputting CRC pass/failed has not expired (EV26), or returns to idle state 602 if the destination function has output either CRC pass or failed (EV27). Particular examples of states include authorizing a node to send data to host 604, and a node receiving control/status data from host 612. Particular examples of transitional events include sending of a host-function token packet (EV12), receiving an acknowledgment handshake packet from an addressed function (EV21). For complete definition of the states 602-620 and the transitional rules/events (EV1-EV27), refer to the enclosed Appendices.

FIG. 21 illustrates one embodiment of a state machine 630 provided to a bus signal distributor 18 for implementing the above described protocols. State machine 630 comprises four states 632-638 and six state transitional rules or events (EV1-EV6). At power on or reset (EV1), state machine 630 enters idle state 632. State machine 630 either stays in idle state 632 if bus signal distributor 18 is not addressed (geographically) (EV2). Otherwise, state machine 630 either enters the state of sending control/status, state 634, or the state of sending receive acknowledgment, state 636, if bus signal distributor 18 is addressed (geographically), depending on the reason it is addressed (geographically).

State machine 630 enters state 634 if it receives a query/configuration verify request (EV3). While in state 634, bus signal distributor 18 replies with the requested information, and then returns to idle state 632. State machine 630 enters state 636 if it receives an instruction from bus controller 14 to receive control/status (EV4). While in state 634, bus signal distributor 18 replies with an acknowledgment, and then enters the state of receiving control/status, state 638. While in state 634, state machine 603 either remains in the state if it has not received the control/status from bus controller 14, and time to receive the control/status has not expired (EV5), or returns to idle state 632 if the control/status has been received or the time to receive has expired (EV6). Particular examples of states include sending of control/status data packet to host 634, and sending an acknowledgment handshake packet to host 636. Particular examples of transitional events include receipt of port enabling geographical token packet (EV3), and receipt of a geographical data packet (EV4). For complete definition of the states 632-638 and the transitional rules/events (EV1-EV4), refer to the enclosed Appendices.

FIG. 22 illustrates one embodiment of a state machine 640 provided to a bus interface 22 for implementing the above described protocols. State machine 640 comprises nine states 642-658 and fifteen state transitional rules or events (EV1-EV15). At power on or reset (EV1), state machine 640 enters idle state 642. State machine 640 either stays in idle state 642 if bus interface 22 is not addressed (logically) for transactions or addressed (logically) but no response is required (EV2). Otherwise, state machine 640 either enters the state of sending control/status or data, state 644, or the state of sending null/attention, state 646, or the state of sending "cannot accept data", state 648, or the state of sending "can accept data", state 650, or the state of waiting for a "can accept data" reply, state 658, if bus interface 22 is addressed (logically), depending on the reason it is addressed (logically).

State machine 640 enters state 644 if it is addressed (logically) for a function to bus controller 14 transaction, and the addressed function is ready to transmit (EV3). While in state 644, bus interface 22 sends the requested control/status or data, and then returns to idle state 642. State machine 640 enters state 646 if it is addressed for a function to bus controller 14 transaction and the addressed function is not ready to transmit (EV4). While in state 646, bus interface 22 sends a null/attention reply, and then returns to idle state 642.

State machine 640 enters state 648 if it is addressed for a bus controller 14 to function transaction and the addressed function cannot accept data (EV5). While in state 648, bus interface 22 sends a "cannot accept data" reply, and then returns to idle state 642. State machine 640 enters state 650 if it is addressed for a bus controller 14 to function transaction and the addressed function "can accept data" (EV6). While in state 650, bus interface 22 sends a "can accept data" reply, and then enters the state of receiving data, state 652.

While at state 652, state machine 640 receives data. State machine 640 either remains in the state if bus controller 14 has not output an indication for CRC or no CRC checking, and time for outputting the indication has not expired (EV7), or returns to idle state 642 if all data has been received, or time for receiving data has expired (EV8), or enters the state of sending CRC pass, state 654, if CRC pass is to be replied, and time to reply has not expired (EV9), or enters the state of sending CRC failed, state 656, if CRC failed is to be replied, and time to reply has not expired (EV10).

State machine 640 enters state 658 if bus interface 22 is addressed (logically) as a source for a function to function transaction (EV11). While in state 658, state machine 640 remains in the state if no "can accept data" or "cannot accept date" has been received, and time for receiving the reply has not expired (EV12), or simply returns the idle state 642 if either the destination function replied with "cannot accept data", or time for receiving the reply has expired (EV13), or returns to idle state 642 after sending null/attention first if the destination function replied with "can accept data" but the source function is not ready to transmit, and time for sending data has not expired (EV14), or returns to idle state 642 after sending control/status or data first if the destination function replied with "can accept data", the source function is ready to transmit, and time for sending the reply has not expired (EV15). Particular examples of states include sending a Null/Attn response to host 646, and accepting data 652. Particular examples of transitional events include timeout or end of data packet (EV8), and timeout or receipt of acknowledgment handshake packet (EV13). For complete definition of the states and the transitional rules/events (EV1-EV15), refer to the enclosed Appendices.

Thus, a method and apparatus for exchanging data, status and commands between serial bus elements of an hierarchy serial bus assembly using communication packets has been described. For additional information about the method and apparatus of the present invention, refer to the enclosed Appendices.

While the present invention has been described in terms of the above embodiments, those skilled in the art will recognize that the invention is not limited to the embodiments described. The method and apparatus of the present invention can be practiced with modification and alteration within the spirit and scope of the appended claims. The description is thus to be regarded as illustrative instead of limiting on the present invention.

Claims

What is claimed is:

1. A bus controller comprising logic for serially formulating and transmitting token packets of at least a first and a second type to one or more bus signal distributors and one or more bus interfaces, each of the bus interfaces being disposed in a peripheral having one or more functions, for serially authorizing management and data transactions with selected ones of the bus signal distributor(s), the bus interface(s) and the function(s), the bus controller, the one or more bus signal distributors and the one or more bus interfaces being coupled to each other in an hierarchical tree like manner, with each bus interface directly coupled to a bus signal distributor, and each bus signal distributor coupled another bus signal distributor, except for one of the one or more bus signal distributors, which is directly coupled to the bus controller, the management transactions being used for dynamically configuring the bus controller, the one or more bus signal distributors and the one or more bus interfaces in accordance with the manner in which the bus controller, the one or more bus signal distributors and the one or more bus interfaces are coupled to each other, each token packet having identification information identifying whether the token packet is of the first or the second type, and first address information, each token packet of the first type being used to authorize either one of the one or more bus signal distributors or one of the one or more bus interfaces to conduct a management transaction with the bus controller, and the first address information of each token packet of the first type being decoded in a partitioned manner including a first portion for identifying a bus signal distributor, and a second portion for identifying either the identified bus signal distributor as the authorized bus signal distributor, or a bus interface coupled to the identified bus signal distributor as the authorized bus interface, each token packet of the second type being used to authorize a first function to conduct a data transaction with the bus controller, and the first address information of each token packet of the second type being decoded in an unpartitioned manner for identifying the first authorized function.

2. The bus controller as set forth in claim 1, wherein the bus controller further comprises logic for serially exchanging data packets of a first type with the authorized bus signal distributors/interfaces and data packets of a second type with the authorized functions, each data packet having identification information identifying whether the data packet is of the first or the second type, and second address information, the second address information of each data packet of the first type being decoded in the first partitioned manner for identifying the authorized bus signal distributor/interface, and the second address information of each data packet of the second type being decoded in the second unpartitioned manner for identifying the authorized function.

3. The bus controller as set forth in claim 1, wherein the identification information of each token packet identifies the token packet as the first, the second or a third type instead, and each token packet further includes second address information, the bus controller further comprises logic for serially formulating and transmitting token packets of the third type to the functions for serially authorizing data transactions to be conducted between selected twos of the functions, both the first and the second address information of each token packet of the third type being decoded in the second unpartitioned manner for identifying two functions as the authorized functions of the data transaction.

4. The bus controller as set forth in claim 3, wherein the bus controller further comprises logic for serially exchanging data packets of a first type with the authorized bus signal distributors/interfaces and data packets of a second type with the authorized functions, each data packet having identification information identifying whether the data packet is of the first or the second type, and at least third address information, the at least third address information of each data packet of the first type being decoded in the first partitioned manner for identifying the authorized bus signal distributor/interface, and the at least third address information of each data packet of the second type being decoded in the second unpartitioned manner for identifying at least one function as the authorized function.

5. A bus signal distributor comprising logic for serially receiving token packets of at least a first and a second type from a bus controller, and forwarding the received token packets to zero or more other bus signal distributors coupled to the bus signal distributor and/or zero or more bus interfaces coupled to the bus signal distributor, each of the bus interfaces being disposed in a peripheral having one or more functions, for serially facilitating authorization by the bus controller of management and data transactions between the bus controller and selected ones of the bus signal distributor(s), the bus interface(s) and the function(s), each bus interface being directly coupled to a bus signal distributor, which in turn is coupled upstream to either another bus signal distributor or the bus controller, the management transactions being used for dynamically configuring the bus controller, the one or more bus signal distributors and the one or more bus interfaces in accordance with the manner in which the bus controller, the one or more bus signal distributors and the one or more bus interfaces are coupled to each other; each token packet having identification information identifying whether the token packet is of the first or the second type, and first address information, each token packet of the first type being used to authorize either one of the bus signal distributors or one of the one or more bus interfaces to conduct a management transaction with the bus controller, end the first address information of each token packet of the first type being decoded in a partitioned manner including a first portion for identifying a bus signal distributor, and a second portion for identifying either the identified bus signal distributor as the authorized bus signal distributor or a bus interface coupled to the identified bus signal distributor as the authorized bus interface, each token packet of the second type being used to authorize a function to conduct a data transaction with the bus controller, and the first address information of each token packet of the second type being decoded in an unpartitioned manner for identifying the first authorized function.

6. The bus signal distributor as set forth in claim 5, wherein the bus signal distributor further comprises logic for serially exchanging data packets of a first type with the bus controller, and facilitating exchanges of data packets of the first type between the bus controller and other authorized bus signal distributors/interfaces, as well as data packets of a second type between the bus controller and the authorized functions, each data packet having identification information identifying whether the data packet is of the first or the second type, and second address information, the second address information of each data packet of the first type being decoded in the first manner for identifying the authorized bus signal distributor/interface, and the second address information of each data packet of the second type being decoded in the second unpartitioned manner for identifying the authorized function.

7. The bus signal distributor as set forth in claim 5, wherein the identification information of each token packet identifies the token packet as the first, the second or a third type; and each token packet further includes second address information, the bus signal distributor further comprises logic for serially receiving and forwarding token packets of the third type to the functions for serially facilitating authorization by the bus controller for data transactions between the first authorized function and a second authorized function, both the first and the second address information of each token packet of the third type being decoded in the second unpartitioned manner for identifying two authorized functions.

8. The bus signal distributor as set forth in claim 7, wherein the bus signal distributor further comprises logic for serially exchanging data packets of a first type with the bus controller, and facilitating exchanges of data packets of the first type between the bus controller and other authorized bus signal distributors/interfaces, as well as data packets of a second type between the bus controller and the authorized functions or between authorized functions, each data packet having identification information identifying whether the data packet is of the first or the second type, and at least third address information, the at least third address information of each data packet of the first type being decoded in the first partitioned manner for identifying the bus signal distributor or an authorized bus interface, and the at least third address information of each data packet of the second type being decoded in the second unpartitioned manner for identifying at least one authorized function.

9. A bus interface comprising logic for serially receiving token packets of at least a first and a second type from a bus controller, each of the bus interfaces being disposed in a peripheral having one or more functions, for serially facilitating authorization by the bus controller of management and data transactions between the bus controller and selected ones of the bus interface(s) and the function(s), each bus interface being directly coupled to a bus signal distributor, which in turn is coupled upstream to either another bus signal distributor or the bus controller, the management transactions including configuration transactions for dynamically configuring the bus interface, the bus signal distributor(s), and the bus controller in accordance with the manner in which the bus interface, the bus signal distributor(s) and the bus controller are coupled to each other, each token packet having identification information identifying whether the token packet is of the first or the second type, and first address information, each token packet of the first type being used to authorize either the bus signal distributor or the bus interface to conduct a management transaction with the bus controller, and the first address information of each token packet of the first type being decoded in a partitioned manner including a first portion for identifying the bus signal distributor, and a second portion for identifying either the identified bus signal distributor as the authorized bus signal distributor, or the bus interface as the authorized bus interface, each token packet of the second type being used to authorize a function to conduct a data transaction with the bus controller, and the first address information of each token packet of the second type being decoded in an unpartitioned manner for identifying the first authorized function.

10. The bus interface as set forth in claim 9, wherein the bus signal distributor further comprises logic for serially exchanging data packets of a first type with the bus controller, or facilitating exchanges of data packets of a second type between the bus controller and the authorized functions, each data packet having identification information identifying whether the data packet is of the first or the second type, and second address information, the second address information of each data packet of the first type being decoded in the first partitioned manner for identifying the bus signal distributor/interface, and the second address information of each data packet of the second type being decoded in the second unpartitioned manner for identifying the authorized function.

11. The bus interface as set forth in claim 9, wherein the identification information of each token packet identifies the token packet as the first, the second, or a third type, and each token packet further includes second address information, the bus interface further comprises logic for serially receiving token packets of the third type for serially facilitating authorization by the bus controller for data transactions between the authorized functions, both the first and the second address information of each token packet of the third type being decoded in the second unpartitioned manner for identifying two authorized functions.

12. The bus interface as set forth in claim 11, wherein the bus interface further comprises logic for serially exchanging data packets of a first type with the bus controller, or facilitating exchanges of data packets of a second type between the bus controller and authorized functions, and between authorized functions, each data packet having identification information identifying whether the data packet is of the first or the second type, and at least third address information, the at least third address information of each data packet of the first type being decoded in the first partitioned manner for identifying the bus interface, and the at least third address information of each data packet of the second type being decoded in the second unpartitioned manner for identifying at least one authorized function.

13. In a computer system having a bus controller, at least one bus signal distributor, and at least one peripheral, wherein each peripheral has a bus interface and at least one function, each bus interface being coupled to a bus signal distributor, and each bus signal distributor being coupled to another bus signal distributor, except for one of the at least one bus signal distributor which is coupled to the bus controller, a method for operating the computer system, the method comprising the steps of: a) authorizing a management transaction with either a bus signal distributor or a bus interface to dynamically configure the bus signal distributor/interface in accordance with the manner in which the bus signal distributor/interface is coupled, the authorization is provided using a token packet of a first type by the bus controller, or authorizing a data transaction with a function using a token packet of a second type by the bus controller, the token packet having identification information identifying whether the token packet is of the first type or the second type, and the token packet further having first address information of either a first type or a second type, wherein if the token packet is of the first type, the first address information is decoded in a partitioned manner including a first portion for identifying a bus signal distributor, and a second portion for identifying either the identified bus signal distributor as the authorized bus signal distributor, or a bus interface coupled to the identified bus signal distributor as the authorized bus interface, and if the token packet is of the second type, the first address information is decoded in an unpartitioned manner for identifying a first function as the first authorized function; b) receiving the token packet by the at least one bus signal distributor and the at least one bus interface in a serial manner in accordance to the manner they are coupled to each other, with each of the at least one receiving signal distributor forwarding the token packet to each of the other bus signal distributor/interface coupled to the receiving bus signal distributor; and c) notifying one of the at least one function by one of the at least one receiving bus interface if the token packet is of the second type, the notified function being the addressee of the token packet of the second type and a function of the notifying bus interface's peripheral.

14. The computer system as set forth in claim 13, wherein the method further comprises the steps of: d) transmitting either a data packet of a first type to an authorized bus signal distributor/interface or a data packet of a second type to an authorized function by the bus controller, the data packet having identification information identifying whether the data packet is of the first or the second type, the data packet further having second address information of either a first type decoded in the first partitioned manner for identifying the authorized bus signal distributor/interface if the data packet is of the first type, or a second type decoded in the second unpartitioned manner for identifying the authorized function if the data packet is of the second type; e) receiving the data packet by the at least one bus signal distributor and the at least one bus interface in a serial manner in accordance to the manner they are coupled to each other, with each of the at least one receiving signal distributor forwarding the data packet to each of the other bus signal distributor/interface coupled to the receiving bus signal distributor; and f) notifying one of the at least one function by one of the at least one receiving bus interface if the data packet is of the second type, the notified function being the addressee of the data packet of the second type and a function of the notifying bus interface's peripheral.

15. The computer system as set forth in claim 13, wherein the method further comprises the steps of: d) transmitting a data packet of a first type to the bus controller by an authorized bus signal distributor/interface or transmitting a data packet of a second type to the bus controller by an authorized function, the data packet having identification information identifying whether the data packet is of the first or the second type, the data packet further having second address information of a first type decoded in the first partitioned manner for identifying the bus controller, or a second type decoded in the second unpartitioned manner for identifying the bus controller; e) receiving the data packet by the transmitting function's bus interface, and forwarding the data packet to the bus interface's coupled bus signal distributor, if the data packet is of the second type; f) receiving the data packet by zero or more intervening ones of the at least one bus signal distributor in a serial manner in accordance to the manner they are coupled, with each of the receiving bus signal distributor forwarding the data packet to the upstream bus signal distributor; and g) receiving the data packet by the bus signal distributor coupled to the bus controller and forwarding the data packet to the bus controller.

16. The computer system as set forth in claim 13, wherein the computer system has at least two peripherals, each of the at least two peripherals having a bus interface and at least one function; the method further comprises the steps of: d) authorizing a data transaction between two functions of two of the at least two peripherals using a token packet of a third type by the bus controller, the token packet having identification information identifying the token packet as being of the third type, and the token packet further having second address information of the second type decoded in the second unpartitioned manner for identifying the two authorized functions; e) receiving the token packet of the third type by the at least one bus signal distributor and the at least two bus interfaces in a serial manner in accordance to the manner they are coupled to each other, with each of the at least one receiving signal distributor forwarding the token packet of the third type to each of the other bus signal distributor/interface coupled to the receiving bus signal distributor; and f) notifying two functions of the at least two peripherals by two of the at least two receiving bus interfaces, the two notified functions being the addressees of the token packet of the third type and functions of the notifying bus interfaces' peripherals.

17. The computer system as set forth in claim 16, wherein the method further comprises the steps of: g) transmitting either a data packet of a first type to an authorized bus signal distributor/interface by the bus controller or a data packet of a second type to a first authorized function by either the bus controller or a second authorized function, the data packet having identification information identifying whether the data packet is of the first or the second type, the data packet further having address information of either the first type decoded in the first partitioned manner for identifying the authorized bus signal distributor/interface if the data packet is of the first type, or the second type decoded in the second unpartitioned manner for identifying the second authorized function if the data packet is of the second type; h) receiving the data packet by the at least one bus signal distributor and the at least one bus interface in a serial manner in accordance to the manner they are coupled to each other, with each of the at least one receiving signal distributor forwarding the data packet to each of the other bus signal distributor/interface coupled to the receiving bus signal distributor; and i) notifying one of the at least two functions by one of the at least two receiving bus interfaces if the data packet is of the second type, the notified function being the addressee of the data packet of the second type and a function of the notifying bus interface's peripheral.

18. The computer system as set forth in claim 16, wherein the method further comprises the steps of: g) transmitting a data packet of the first type to the bus controller by an authorized bus signal distributor/interface or transmitting a data packet of the second type to either the bus controller or the first authorized function by the second authorized function; e) receiving the data packet by the transmitting second function's bus interface, and forwarding the data packet to the bus interface's coupled bus signal distributor, if the data packet is of the second type; f) receiving the data packet by zero or more intervening ones of the at least one bus signal distributor in a serial manner in accordance to the manner they are coupled, with each of the receiving bus signal distributor forwarding the data packet to the other bus signal distributor/interface coupled to the receiving bus signal distributor; and g) receiving the data packet by either the bus signal distributor coupled to the bus controller and forwarding the data packet to the bus controller, or by the bus interface disposed on the peripheral of the first authorized function and notifying the first authorized function.

Patent Citations (38)

Patent	Date	Inventor
US3245045	1966-04-01	Randlev
US3916387	1975-10-01	Woodrum
US3932841	1976-01-01	Deerfield et al.
US4070704	1978-01-01	Calle et al.
US4092491	1978-05-01	Frazer
US4409656	1983-10-01	Andersen et al.
US4606052	1986-08-01	Hirzel et al.
US4660141	1987-04-01	Ceccon et al.
US4689740	1987-08-01	Moelands et al.
US4713834	1987-12-01	Brahm et al.
US4748346	1988-05-01	Emori
US4885742	1989-12-01	Yano
US4912633	1990-03-01	Schweizer et al.
US4914650	1990-04-01	Sriram
US4984190	1991-01-01	Katori et al.
US5001707	1991-03-01	Kositpaiboon
US5063574	1991-11-01	Moose
US5130983	1992-07-01	Heffner, III
US5173939	1992-12-01	Abadi et al.
US5179670	1993-01-01	Farmwald et al.
US5237690	1993-08-01	Bealkowski et al.
US5257160	1993-10-01	Yokohama et al.
US5269011	1993-12-01	Yannai et al.
US5282202	1994-01-01	Bernstein et al.
US5317597	1994-05-01	Eisele
US5341480	1994-08-01	Wasserman et al.
US5361261	1994-11-01	Edem et al.
US5379384	1995-01-01	Solomon
US5386567	1995-01-01	Lien et al.
US5388213	1995-02-01	Oppenheimer et al.
US5394556	1995-02-01	Oprescu
US5418478	1995-05-01	Van Brunt et al.
US5440181	1995-08-01	Gruender, Jr. et al.
US5440556	1995-08-01	Edem et al.
US5446765	1995-08-01	Leger
US5463620	1995-10-01	Sriram
US5463624	1995-10-01	Hogg et al.
US5483518	1996-01-01	Whetsel

Non-Patent Literature (11)

Concentration Highway Interface (CHI), AT&T Microelectronics Interface Specification, Nov. 1990 (DS90-124SMOS).
ATA/ANSI 878.1, Version 1.9 (59 Sheets), Copyright 1992 ARCNET Trade Association.
Globecom '92: IEEE Global Telecommunications Conference; Sriram "Methodologies For Bandwidth Allocation, Transmission Scheduling, And Congestion Avoidance In Broadband ATM" 1992.
Globecom '90: IEEE Global Telecommunications Conference; Aicardi, et al. "Adaptive Bandwidth Assignments In A TDM Network With Hybrid Frames", pp. 41-42 1990.
Local Computer Networks, 1991 16th Conference, Issued 13 Mar. 1991, R. Bolla et al, "A traffic control strategy for a DQDB-type MAN", pp. 195-196 1991.
Wireless Communications, Selected Topics, Int'l conference 1992, issued Feb. 1992, K. S. Natarajan, "A hybrid medium access Protocol for Wireless LANS", pp. 134-136.
IEEE Transactions on Communications, Z. Zhang et al, "Bounds on the mean system-size and Delay for a movable-boundary integrated circuit and packet switched communications" 1994 No Month of Publication Given to Establish Whether it was before/after Applicants Filing Date.
Globecom '92: IEEE Global Telecommunications Conference; Bolla et al. "A Neutral Strategy For Optimal Multiplexing Of Circuit-And Packet-Switched Traffic," 1992 p. 1992.

Abstract

Description