Multiplex communications – Communication techniques for information carried in plural... – Combining or distributing information via time channels
Reexamination Certificate
1996-03-07
2003-02-11
Ton, Dang (Department: 2666)
Multiplex communications
Communication techniques for information carried in plural...
Combining or distributing information via time channels
C370S389000
Reexamination Certificate
active
06519268
ABSTRACT:
FIELD OF THE INVENTION
The present invention relates to the field of automatically managing data transfer operations between an application and a bus structure. More particularly, the present invention relates to the field of automatically generating transactions necessary to complete an asynchronous data transfer operation between an application and a bus structure.
BACKGROUND OF THE INVENTION
The IEEE 1394 standard, “P1394 Standard For A High Performance Serial Bus,” Draft 8.01v1, Jun. 16, 1995, is an international standard for implementing an inexpensive high-speed serial bus architecture which supports both asynchronous and isochronous format data transfers. Isochronous data transfers are real-time transfers which take place such that the time intervals between significant instances have the same duration at both the transmitting and receiving applications. Each packet of data transferred isochronously is transferred in its own time period. An example of an ideal application for the transfer of data isochronously would be from a video recorder to a television set. The video recorder records images and sounds and saves the data in discrete chunks or packets. The video recorder then transfers each packet, representing the image and sound recorded over a limited time period, during that time period, for display by the television set. The IEEE 1394 standard bus architecture provides multiple channels for isochronous data transfer between applications. A six bit channel number is broadcast with the data to ensure reception by the appropriate application. This allows multiple applications to simultaneously transmit isochronous data across the bus structure. Asynchronous transfers are traditional data transfer operations which take place as soon as possible and transfer an amount of data from a source to a destination.
The IEEE 1394 standard provides a high-speed serial bus for interconnecting digital devices thereby providing a universal I/O connection. The IEEE 1394 standard defines a digital interface for the applications thereby eliminating the need for an application to convert digital data to analog data before it is transmitted across the bus. Correspondingly, a receiving application will receive digital data from the bus, not analog data, and will therefore not be required to convert analog data to digital data. The cable required by the IEEE 1394 standard is very thin in size compared to other bulkier cables used to connect such devices. Devices can be added and removed from an IEEE 1394 bus while the bus is active. If a device is so added or removed the bus will then automatically reconfigure itself for transmitting data between the then existing nodes. A node is considered a logical entity with a unique address on the bus structure. Each node provides an identification ROM, a standardized set of control registers and its own address space.
The IEEE 1394 standard defines a protocol as illustrated in FIG.
1
. This protocol includes a serial bus management block
10
coupled to a transaction layer
12
, a link layer
14
and a physical layer
16
. The physical layer
16
provides the electrical and mechanical connection between a device or application and the IEEE 1394 cable. The physical layer
16
also provides arbitration to ensure that all devices coupled to the IEEE 1394 bus have access to the bus as well as actual data transmission and reception. The link layer
14
provides data packet delivery service for both asynchronous and isochronous data packet transport. This supports both asynchronous data transport, using an acknowledgement protocol, and isochronous data transport, providing real-time guaranteed bandwidth protocol for just-in-time data delivery. The transaction layer
12
supports the commands necessary to complete asynchronous data transfers, including read, write and lock. The serial bus management block
10
contains an isochronous resource manager for managing isochronous data transfers. The serial bus management block
10
also provides overall configuration control of the serial bus in the form of optimizing arbitration timing, guarantee of adequate electrical power for all devices on the bus, assignment of the cycle master, assignment of isochronous channel and bandwidth resources and basic notification of errors.
To initialize an isochronous transfer, several asynchronous data transfers may be required to configure the applications and to determine the specific channel which will be used for transmission of the data. Once the channel has been determined, buffers are used at the transmitting application to store the data before it is sent and at the receiving application to store the data before it is processed. In some peripheral implementations, it is desirable for the peripheral to transfer large amounts of data using a large number of asynchronous transactions. In order to generate these transactions quickly and efficiently, it is not practical to require a general purpose CPU or microcontroller to construct each request packet.
What is needed is an asynchronous data pipe that provides automated generation of transactions necessary to complete an asynchronous data transfer operation, without requiring supervision by an API and the processor of an application.
SUMMARY OF THE INVENTION
An asynchronous data pipe (ADP) automatically generates transactions necessary to complete asynchronous data transfer operations for an application over a bus structure. The ADP includes a register file which is programmed by the application. The register file allows the application to program requirements and characteristics for the data transfer operation. The register file includes the bus speed, transaction label, transaction code, destination node identifier, destination offset address, length of each data packet, packet counter, packet counter bump field, control field and a status field. After the register file is programmed and initiated by the application, the ADP automatically generates the read or write transactions necessary to complete the data transfer operation over the appropriate range of addresses, using the information in the register file as a template for generating the transactions and headers. The ADP automatically increments the value in the destination offset address field for each transaction according to the length of each data packet, unless an incrementing feature has been disabled, signalling that the transactions are to take place at a single address. The packet counter value represents the number of transactions remaining to be generated. The packet counter value is decremented after each packet of data is transferred. The packet counter bump field allows the application to increment the packet counter value by writing to the packet counter bump field.
Multiple ADPs can be included within a system for managing multiple asynchronous data transfer operations. In such a system, each ADP has its own unique transaction label value or range of values. A multiplexer is coupled to each ADP for multiplexing the transactions and data packets from the ADPs onto the bus structure. A demultiplexer is also coupled to each ADP for receiving signals and data packets from the bus structure and routing them to the appropriate ADP, using the transaction code and transaction label values.
REFERENCES:
patent: 3836722 (1974-09-01), Muller et al.
patent: 3906484 (1975-09-01), Melvin, Jr. et al.
patent: 4218756 (1980-08-01), Fraser
patent: 4379294 (1983-04-01), Sutherland et al.
patent: 4395710 (1983-07-01), Einolf, Jr. et al.
patent: 4409656 (1983-10-01), Andersen et al.
patent: 4493021 (1985-01-01), Agrawal et al.
patent: 4633392 (1986-12-01), Vincent et al.
patent: 4641307 (1987-02-01), Russell
patent: 4739323 (1988-04-01), Miesterfeld et al.
patent: 4857910 (1989-08-01), Baunach
patent: 4897783 (1990-01-01), Nay
patent: 4972470 (1990-11-01), Farago
patent: 4998245 (1991-03-01), Tanaka et al.
patent: 5008879 (1991-04-01), Fischer et al.
patent: 5117070 (1992-05-01), Ueno et al.
patent: 5191418 (1993-03-01), Tran
patent: 5276684 (1994-01-01), Pearson
Haverstock & Owens LLP
Ton Dang
LandOfFree
Asynchronous data pipe for automatically managing... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Asynchronous data pipe for automatically managing..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Asynchronous data pipe for automatically managing... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3164648