Language selection

Search

Patent 2180039 Summary

Third-party information liability

Some of the information on this Web page has been provided by external sources. The Government of Canada is not responsible for the accuracy, reliability or currency of the information supplied by external sources. Users wishing to rely upon this information should consult directly with the source of the information. Content provided by external sources is not subject to official languages, privacy and accessibility requirements.

Claims and Abstract availability

Any discrepancies in the text and image of the Claims and Abstract are due to differing posting times. Text of the Claims and Abstract are posted:

  • At the time the application is open to public inspection;
  • At the time of issue of the patent (grant).
(12) Patent: (11) CA 2180039
(54) English Title: TRANSMITTING ENCODED DATA ON UNRELIABLE NETWORKS
(54) French Title: TRANSMISSION DE DONNEES CODEES SUR DES RESEAUX NON FIABLES
Status: Term Expired - Post Grant Beyond Limit
Bibliographic Data
(51) International Patent Classification (IPC):
  • H04L 1/22 (2006.01)
  • H04L 1/08 (2006.01)
  • H04L 7/00 (2006.01)
(72) Inventors :
  • GUTMAN, MICHAEL (United States of America)
  • HLUCHYJ, MICHAEL G. (United States of America)
  • PASCO-ANDERSON, JAMES A. (United States of America)
(73) Owners :
  • GENERAL ELECTRIC CAPITAL CORPORATION
(71) Applicants :
(74) Agent: GOWLING WLG (CANADA) LLP
(74) Associate agent:
(45) Issued: 1999-01-12
(22) Filed Date: 1990-12-24
(41) Open to Public Inspection: 1991-06-30
Examination requested: 1996-12-30
Availability of licence: N/A
Dedicated to the Public: N/A
(25) Language of filing: English

Patent Cooperation Treaty (PCT): No

(30) Application Priority Data:
Application No. Country/Territory Date
458,769 (United States of America) 1989-12-29

Abstracts

English Abstract


Information encoded by data compression (or another data encoding
technique, e.g. encryption, requiring synchronization between the encoder (12a)
and decoder (22b) is transmitted over an unreliable network (16) by checking
for transmission errors after decoding. If an error is detected, the encoder (12a)
is reset, using a reset protocol, which may operate over an unreliable reverse
channel (16) by using a timer (46) to generate further reset requests when the
receiver does not acknowledge them in a timely fashion.


French Abstract

De l'information codée par compression de données (ou une autre technique de codage de données, p. ex. chiffrement, nécessitant la synchronisation entre le codeur (12a) et le décodeur (22b) est transmise sur un réseau non fiable (16), les erreurs de transmission étant vérifiées après décodage. Si une erreur est détectée, le codeur (12a) est réinitialisé, conformément à un protocole de réinitialisation qui peut fonctionner sur un canal de retour non fiable (16) en utilisant un temporisateur (46) pour générer d'autres demandes de réinitialisation lorsque le récepteur ne produit pas d'accusé de réception en temps voulu.

Claims

Note: Claims are shown in the official language in which they were submitted.


THE EMBODIMENTS OF THE INVENTION IN WHICH AN EXCLUSIVE
PROPERTY OR PRIVILEGE IS CLAIMED ARE DEFINED AS FOLLOWS:
1. A method for transmitting encoded data across
unreliable networks, said encoding being of a type in
which encoding and decoding are synchronized, said method
comprising the steps of:
encoding said data using a data encoding method;
transmitting said encoded data across said
unreliable network;
receiving and decoding said data;
subsequently detecting any errors introduced by said
unreliable network and resetting said encoding method
upon said detection of errors; and at intervals,
periodically resynchronizing said encoding method at
frame boundaries;
2. The method of claim 1 wherein the step of resetting
said encoding method includes the steps of:
transmitting a reset request code sequence over a
reverse channel upon said detection of errors, wherein
said reset request code sequence initiates the resetting
of an encoder; and
transmitting a reset acknowledgement code sequence
over said unreliable network to acknowledge reception of
said reset request code sequence, wherein said reset
acknowledgement code sequence initiates the resetting of
a decoder.

3. The method of claim 1, wherein:
said unreliable network further includes a plurality
of nodes so arranged that a plurality of paths exist
between at least some nodes between which said method is
practiced; and wherein
at least one node may communicate with more than one
node at a time using different encoding methods to
communicate with at least two different nodes.
4. A method for transmitting encoded data across
unreliable networks, said encoding being of a type in
which encoding and decoding are synchronized, said method
comprising the steps of:
encoding said data using a data encoding method;
transmitting said encoded data across said
unreliable network;
receiving and decoding said data; and at intervals,
periodically resynchronizing said encoding method at
frame boundaries.
5. The method of claim 4 wherein the resynchronization
of said encoding method occurs at every frame boundary.
6. The method of claim 4 wherein said unreliable
network includes a plurality of nodes so arranged that a
plurality of paths exist between at least some nodes
between which said method is practised.
7. The method of claim 6 wherein at least one node may
communicate with more than one node at a time.

8. The method of claim 4 wherein said data encoding
comprises data compression.
9. The method of claim 4 wherein said data encoding
comprises encryption.
10. The method of claim 4 further comprising error
correction in which there is selective retransmission of
frames.
11. The method of claim 10 wherein said step of
periodically resynchronizing is used on a first set of
paths in said network and wherein a reset method is used
on a second set of paths different from said first set,
said reset method comprising the steps of:
encoding said data using a data encoding method;
transmitting said encoded data across said second
set of paths in said unreliable network;
receiving and decoding said data;
subsequently detecting any errors introduced by said
second paths; and
resetting said encoding method upon said detection
of errors.
12. The method of claim 4 wherein the resynchronization
of said encoding method comprises the steps of:
resetting said encoding method; and
transmitting a reset acknowledgement code sequence
over said unreliable network to initiate the resetting of
a decoder.

Description

Note: Descriptions are shown in the official language in which they were submitted.


~ '''O91/1~289 2 1 ~ O 0 3 ~ PCT/US90/07472
._
TRA~SMITTING F~NcoDF~n DATA ON UNRFT~I~RT~ NFTWORK~
~ckground of the Invent;on
This invention relates to communication systems
and in particular to the application of data encoding
techniques, such as data compression, to unreliable
networks.
Packet-switched digital co nication networks
allow digital systems to communicate with each other. They
typically include several nodes which may transmit, receive
or forward data. ~ata to be transmitted are loaded into
frames, along with a destination address which determines
which node is to receive the frame. The frames are sent
from one node to another either directly or via a series of
intermediate nodes. The comm~n;cation channel established
between nodes in a network is known as a virtual circuit.
Packet-switched data may be transmitted over a
reliable network, in which error recovery is built into the
network. For example, an error checking system, such as
CRC error checking, may be provided ~etween the nodes of a
network. In this arrangement, whenever a receiving node
detects an error in a received frame, it requests
retransmission of that frame from the sending node.
In some protocols, the sender retransmits every
frame that has been transmitted since the last error upon
discovery of that error. This type of protocol is called
"go-back-n". Alternatively, the sender may simply
retransmit those frames that are in error. This type of
protocol is called ~'selective retransmission."
On some networks, especially those with low
error rates, no error recovery is included. On these
"unreliable networks", the end systems are left to recover
from any errors over the network as they see fit.
Typically, the receiving end system will use a reverse
channel to acknowledge the reception of frames to the
sending end system. Frames that are not received are not

W09lt10289 2 1 ~ O 0 3 9 PCT/US90/07472
acknowledged, and frames that are received with errors
initiate error recovery procedures. The frames are then
retransmitted by the sender. In these "unreliable
networks", increased data throughput is often achieved by
having the network nodes simply drop frames when errors are
~ detected, without attempting error recovery. The end
systems have the task of detecting the loss of frames, and
requesting retransmission.
It is advantageous to perform data compression
on data that are sent through the network, as this reduces
the amount of data to be sent through the network. This is
usually accomplished by sending the data over a reliable
network, i.e., one in which error recovery is provided
inside of the data compression encoding and decoding.
Other forms of data encoding are also useful,
such as scrambling or encryption. These operations are
also usually accomplished by sending the encoded data over
a reliable network.
Many powerful data encoding methods need to
remain synchronized. This synchronization can be broken
when a frame is received containing errors or is lost
altogether. Adaptive and variable field length data
encoding are two methods that require synchronization. In
adaptive compression, the vocabularies used to encode and
decode a compressed frame change as a function of the data
being sent. The vocabulary at the encoder and the
vocabulary at the decoder must remain synchronized. An
error will usually affect the vocabulary of the receiver
and cause it to decode all subsequent frames erroneously.
In variable field length systems, errors may cause data to
be interpreted using different field lengths than those
with which the data were intended to be decoded. These
data encoding methods will usually continue to operate
erroneously if they are not resynchronized and will often
tend to progress to a state where all data are received
erroneously.

Q 3 ~
, ~.~
The resynchronization of the decoder can be achieved by resetting each
of them to the same predetermined state. This predetermined state could be
fixed or could change with time.
SummarY of the Invention
In accordance with the present invention, there is provided a method for
transmitting encoded data across unreliable networks. The encoding is of a type
in which encoding an decoding are synchronized. The data is encoded using
a data encoding method. The encoded data is ll~lsnlilled across the unreliable
network. The data is then received and decoded. At intervals, the encoding
method is periodically resynchronized at frame boundaries.
In a preferred embodiment, any errors introduced by the unreliable
network is detected, and the encoding method is reset upon the detection of
errors.
The invention has the advantage of allowing synchronized encoding of
data over an unreliable channel in an essentially transparent fashion. This is
done despite the tendency of error propagation in synchronized data encoding
methods. In fact, the invention takes advantage of this tendency in order to
provide detection of out-of-
. ~

WO91/10289 2 1 ~ O 0 3 ~ PCT/~iS90/074,2
-- 4
sequence frames. Hence, in the case of data compression,
an unreliable network can be provided with enhanced
throughput. Data compression and other methods may thus be
used without the expense of a network error recovery system
in addition to what the end systems are already using.
Other advantages and features of the invention
will become apparent from the following description of the
preferred embodiment, and from the claims.
DescrLption of the Preferred Fmho~im~nt
Fig. l is a block diagram of a prior art
network.
Fig. 2 is a block diagram of a prior art data
encoding method as applied to the network of Fig. l.
Fig. 3 is a block diagram of the data encoding
method of the invention.
Fig. 4 is a schematic outline of an illustrative
comml1nication network as is known in the art.
Fig. 5 is a block diagram of a full-duplex
encoder-decoder pair.
Fig. 6 is a flow chart of the data encoding
reset protocol phases. -
Fig. 7 is a chart of an error being correctedusing the data encoding reset protocol of the invention and
its effect on the data frames.
Fig. 8 is a chart of an error being corrected
where the reset request is lost due to an error on the
reverse channel.
Fig. 9 is a diagram illustrating the propagation
of frames through a channel using periodic reset.
In a simple reliable network (Fig. l), the
network, itself, incorporates error recovery. End system 6
(source S) applies data to network 8, which is made
reliable ~y elements of procedure 13, 17 and error
detection blocks 14, 20, the operation of which is well
known in the art. Error detection information, such as a

~091/10289 2 1 8 0 0 3 ~ PCT/US90/07472
- 5 -
cyclic redundancy code (CRC), is added to the encoded data
by error detection code generator 14. The resulting data
are transmitted across channel 16, which may be a virtual
circuit in a network, such as the one indicated by X or Y
in the network shown schematically in Fig. 4. Within this
channel 16, errors are randomly introduced in the data.
These errors may arise from a variety of sources, such as
crosstalk, induced spikes, or power line surges.
Errors introduced in transmitting the data over
the channel 16 are detected (using the error detection
information) by error detector 20, which, in conjunction
with the receiving end's elements of procedure 17, causes a
request for retransmission to be sent to the transmitting
end's elements of procedure 13 over a reverse channel (not
shown in Fig. 1). In some networks, the elements of
procedure and error recovery blocks shown in Fig. 1 are
repeated at numerous nodes along the virtual circuit (Fig.
4).
If no errors are detected, the received data are
passed on to the end system 6 at the destination. The
source 10 may thus send data and expect them to arrive at
the destination 24 with no errors, though some of the data
may have to be retransmitted between network nodes during
this process.
Referring to Fig. 2, the usual prior art method
of incorporating data compression into a network system is
to add an encoder 12 before the transmission end's elements
of procedure 13, and to add a decoder 22 after the
receiving end's elements of procedure 17.
In this approach, the source 10 applies data to
be transmitted to the encoder 12 which encodes these data
using a data encoding algorithm. This algorithm may be a
data compression algorithm such as an adaptive data
compression algorithm, or it may be another type of
algorithm, such as an encryption algorithm. These methods
of data encoding are well known in the art.

WO91/l0289 2 1 8 0 0 3 q PCTt~S90/07~72
The encoded data are passed on to the
transmitting end's elements of procedure 13 and error
detection code generator 14 which adds error detection
information and transmits the data over channel 16 where
errors may be introduced.
Error detector 20 receives the transmitted data
and checks them for errors. If errors are detected, the
receiving end's elements of procedure 17 will request
retransmission of the data as described above. Thus, the
decoder 22 will always receive data free of channel errors,
will always remain in synchronization with the encoder 12,
and will decode these data and pass them on to the
destination 24.
The preferred embodiment of the invention is
structured differently, as may be seen in Fig. 3. The
elements of procedure 13, 17 and error detection blocks 14,
20 are moved outside of the network system 8, and reside in
the end systems 6. The data compression encoder 12 and
decoder 22 remain within the network system 8, but error
detection blocks lS, 21 have been added outside of the
encoder and decoder. A second error detection code
generator 15 (e.g., a CRC generator) is ahead of encoder 12
at the transmitting end. A second error detector 21 is
downstream of the decoder 22.
Within the transmitting end system 6, source 10
applies data to the transmitting end's elements of
procedure 13, which passes the data on to the error
detection code generator 14, which, in turn, introduces
error detection information into the data.
The data are then passed to the network system
8, where a second error detectior code generator 15,'this
one, a part of the encoding system, introduces further
error detection information into the data. The data are
then encoded in encoder 12 and transmitted over channel 16
At the receiving end, the data are decoded in
decoder 22. Errors introduced on channel 16 may be present

WO91/10289 ~ 2 1 8 0 0 3 9 PCT~US90/~7472
-- 7
in the data and, if so, the decoded data will also contain
errors. In using data encoding methods that require
synchronization, errors will typically cause more errors,
which will, in turn, cause further errors, and very quickly
the decoder will be generating a stream of completely
erroneous data. In the case of adaptive data compression,
this arises because the vocabulary used to decode the data
is dependent on the data themselves, and once it is flawed
it decodes the data incorrectly. This erroneously decoded
data leads to a more flawed vocabulary, which leads to more
erroneously decoded data, and so on. It should also be
noted that, because the data compression is continuous
across frames ~i.e. the vocabulary is not reset for each
frame), missing or out-of-sequence frames will also be
decoded incorrectly.
Received data is also supplied to error detector
20 in the end system 6 at the destination, which works in
conjunction with the receiving end's elements of procedure
17 to require retransmission of erroneous frames, in the
conventional way. ~owever, before retransmission may
occur, the data encoding method must be reset, otherwise
the retransmitted frames would be decoded erroneously. To
this end, decoding error detector 21 sends a reset request
to encoder 12 over a reverse channel.
The relationship between a channel and its
reverse channel is illustrated in Fig. 5. Referring to
this figure, it can be seen that encoder 12a encodes data
to be sent across channel 16 to be decoded by decoder 22b.
At the same time, encoder 12b may encode data to be sent
across channel 16' to be decoded by decoder 22a. Channel
16' is the reverse channel for channel 16, and vice-versa.
This reverse channel 16' is used by the decoding error
detector 21 to send reset requests when an error is
detected in the data decoded by decoder 22b.
As the reverse channel is also unreliable, an
error-tolerant reset protocol is used for the reset

WO9l/10289 21 aoo3s PCT/US90/07472
-- 8 --
operation. Referring to Figs. 6 and 7, this protocol is
initiated when an erroneous frame 52 is detected at the
decoder 22b. When this error18 is detected (at 40 in Fig.
6), the decoder 22b of site B starts a timer 46 and causes
the encoder 12b to send a reset request codeword 42 over
channel 16'. This codeword 42 is received by decoder 22a
which instructs the encoder 12a to reset its data encoding
algorithm. In addition to resetting itself, the encoder
12a also acknowledges reception of the reset request
codeword 42 by inserting a reset acknowledgement codeword
44 in a frame 50. This frame is sent over channel 16 to
decoder 22b which then stops the timer 48 and resets its
data decoding algorithm. At this point, the decoder-
encoder pair are resynchronized and they are ready to
communicate properly with one another, beginning with the
data following the reset acknowledgement codeword 44.
If an error18' occurs on the reverse channel 16',
as shown in Fig. 8, and thus the decoder 22a does not
receive the reset request codeword 42, the encoder 12a will
not reset itself, and will fail to send a reset
acknowledgement codeword 44. This situation is detected by
site B when the reset acknowledgement codeword 44 has not
been received before the timer expires 49. When the timer
expires 49, a second reset request codeword 54 is sent over
channel 16' to decoder 22a. The reset operation then
proceeds as described above.
Note that if an error18 occurs in the forward
channel 16 and prevents the decoder 22b from receiving the
reset acknowledgement codeword 44, the timer will also
expire and a second reset request codeword 54 will be sent.
It should also be noted that errors may occur in successive
reset request codewords or reset acknowledgement codewords,
or in a combination of the two, and that the decoder 22b
will keep sending reset request codewords until the whole
protocol has been satisfied. Thus the protocol is capable
of resetting the data encoding despite the occurrence of

WO91/10289 2 1 ~ O 0 3 ~ PCT/~iS90/07472
g
channel errors on forward channel 16 or reverse channel
16'.
A network equipped with the invention will
perform data encoding and provide the advantages inherent
to this type of data encoding in a way that is transparent
to the end systems using the network. If errors occur on
the network, they will appear no different from errors that
would otherwise occur on an unreliable network, because the
network is capable of resetting its data encoding before
retransmission is started. Thus error propagation due to
loss of synchronization will be limited to those frames
that were sent prior to the retransmission.
The fact that the data encoding is continuous
across frames allows the data encoding to recover in the
case of an out-of-sequence or missing frame, as well.
Also, false resets may be generated, meaning a
reset request (or reset acknowledgement) is generated when
it is not needed. These false resets will typically mean
only a momentary loss of compression efficiency, e.g., as
the data compression algorithm relearns its vocabulary.
Error detection capability may be enhanced by
the data encoding, and may also be used as an additional
mechanism of error detection. For example, some algorithms
destroy much of the data following an error. This enhances
the error detection capabilities of the error detection
algorithms as, in general, their detection reliability
increases as the number of errors in a frame increases.
Furthermore, in this type of algorithm one can periodically
include a control codeword in the data at the encoder. If
such a control codeword is then found to be absent at the
decoder, an error is detected. It is also possible to
detect illegal codewords in the data to be decoded, since
in most algorithms there exist codewords which cannot
appear in a valid sequence of codewords. The presence of
such a codeword signals an error.

WO 91/10289 21 aoo3s PCT/US90/07472
-
-- 10 --
If go-back-n retransmission is used, there will
be no degradation in network performance, as one error will
cause that frame and all subsequent frames to be
retransmitted. If selective retransmission is being
S performed, then the fact that the data encoding errors may
propagate into subsequent frames until the data encoding is
reset may cause some otherwise unnecessary frame
retransmissions. But these may be offset by advantages
inherent in the data encoding. For example, the amount of
increased throughput of a network which uses a data
compression algorithm may be much more significant than
that lost in extra retransmissions.
Longer channels take longer to reset, as the
reset request codeword and the reset acknowledgement
lS codeword must each propagate through the length of the
channel. It can thus be advantageous, when selective
retransmission is being used, to simply reset the data
encoding periodically, independent of any errors. In this
way, the most time that is ever spent while the decoder is
out of synchronization with the channel is the time between
resets, which can be set to be shorter than the round-trip
time of the network. As a special case of this periodic
reset, if the frames are sufficiently long, it may be
desirable to reset the encoder and decoder at the beginning
of each frame. This has the advantage that no vocabulary
needs to be stored between frames.
The time between resets, however, is constralned
by the data encoding method. An adaptive data compression
algorithm, for example, may not become efficient until it
has accumulated a certain vocabulary, and hence increased
frequency of resets may reduce compression efficiency.
Networks where it is advantageous to use periodic resets
are those in which a>m/2, where m is the minimal reset
interval that still provides acceptable data encoding
performance, and a is the round trip equivalent of the
data. The minimal reset interval m is typically on the

WO 9IJ10289 2 1 8 0 n 3 9 PCT/~S90/07472
order of a few kilobytes for an adaptive data compression
algorithm.
The use of periodic reset is shown in Fig. 9.
In this illustrated case, the data encoding is reset every
nine frames, by sending frames 50 that include a reset ack
codeword 44 every nine frames. The round trip equivalent
of this illustrative channel is thirty-two frames. Using
periodic reset is advantageous in this case, as single
errors will only affect the decoding of at most nine
frames, which is fewer than the thirty-two that would be
affected using a reset protocol.
In some networks, it is advantageous to use a
combination of the two techniques. In shorter paths within
the network, the reset protocol would be the most
advantageous, whereas longer ones would benefit from
periodic reset. In a system which uses both techniques,
the choice of reset methods is made based on the
configurations of the channel once the routing of the
channel from node to node has been decided. For example,
in Fig. 4, the X channel which passes via nodes a, b, c and
d might use the reset protocol, while the Y channel passing
via a longer path might use periodic resets.
In communication networks, it is not uncommon
for several nodes to be communicating with the same node,
and thus the decoding timers would have to be duplicated.
In this type of situation, a way to reduce complexity is to
use the same timer for all decoders at once. If a reset
request codeword or a reset acknowledgement codeword is
lost, and the timer expires, a second reset request
codeword is sent on all of the channels waiting for a reset
acknowledgement codeword, until the protocol is satisfied.
This system is useful if the number of channels is not too
large relative to the error rates on each channel.
Other embodiments are within the scope of the
following claims. For example, the data encoding error
detection (15, 21) and end system error detection (1~, 20)

WO91/10289 2 1 ~ O 0 3 ~ PCT/US90~07472
....... .
- 12 -
might be combined, to reduce system complexity, but in
practice, it is generally preferable to keep these
functions separate, as it is better not to constrain the
end systems to a specific type of error detection. In this
way, a network which includes data encoding may be used
with different types of end systems, as long as they are
designed to operate over unreliable channels. Although it
would, in principle, be possible to build data encoding
into the end systems 6, anà thus avoid the need for
separate error detection and reset capability for the
encoding process, it is also generally preferable not to do
so. By leaving data encoding to the network system, the
expense and complexity of encoding need not be incurred in
portions of the network where it is not cost effective.
For example, data compression tends to be cost effective
only on the backbone network and not the local portions of
a network.

Representative Drawing
A single figure which represents the drawing illustrating the invention.
Administrative Status

2024-08-01:As part of the Next Generation Patents (NGP) transition, the Canadian Patents Database (CPD) now contains a more detailed Event History, which replicates the Event Log of our new back-office solution.

Please note that "Inactive:" events refers to events no longer in use in our new back-office solution.

For a clearer understanding of the status of the application/patent presented on this page, the site Disclaimer , as well as the definitions for Patent , Event History , Maintenance Fee  and Payment History  should be consulted.

Event History

Description Date
Inactive: IPC expired 2022-01-01
Inactive: IPC assigned 2013-01-30
Inactive: IPC assigned 2013-01-30
Inactive: IPC expired 2013-01-01
Inactive: IPC removed 2012-12-31
Inactive: Expired (new Act pat) 2010-12-24
Inactive: Office letter 2005-07-25
Inactive: Correspondence - Transfer 2005-06-21
Letter Sent 2005-02-24
Letter Sent 2005-02-24
Grant by Issuance 1999-01-12
Pre-grant 1998-08-21
Inactive: Final fee received 1998-08-21
Inactive: Received pages at allowance 1998-05-13
Letter Sent 1998-03-12
Notice of Allowance is Issued 1998-03-12
Notice of Allowance is Issued 1998-03-12
Inactive: Application prosecuted on TS as of Log entry date 1998-03-03
Inactive: Status info is complete as of Log entry date 1998-03-03
Inactive: Approved for allowance (AFA) 1998-02-25
All Requirements for Examination Determined Compliant 1996-12-30
Request for Examination Requirements Determined Compliant 1996-12-30
Application Published (Open to Public Inspection) 1991-06-30

Abandonment History

There is no abandonment history.

Maintenance Fee

The last payment was received on 

Note : If the full payment has not been received on or before the date indicated, a further fee may be required which may be one of the following

  • the reinstatement fee;
  • the late payment fee; or
  • additional fee to reverse deemed expiry.

Please refer to the CIPO Patent Fees web page to see all current fee amounts.

Owners on Record

Note: Records showing the ownership history in alphabetical order.

Current Owners on Record
GENERAL ELECTRIC CAPITAL CORPORATION
Past Owners on Record
JAMES A. PASCO-ANDERSON
MICHAEL G. HLUCHYJ
MICHAEL GUTMAN
Past Owners that do not appear in the "Owners on Record" listing will appear in other documentation within the application.
Documents

To view selected files, please enter reCAPTCHA code :



To view images, click a link in the Document Description column. To download the documents, select one or more checkboxes in the first column and then click the "Download Selected in PDF format (Zip Archive)" or the "Download Selected as Single PDF" button.

List of published and non-published patent-specific documents on the CPD .

If you have any difficulty accessing content, you can call the Client Service Centre at 1-866-997-1936 or send them an e-mail at CIPO Client Service Centre.


Document
Description 
Date
(yyyy-mm-dd) 
Number of pages   Size of Image (KB) 
Description 1998-02-04 12 542
Claims 1998-02-04 3 73
Claims 1998-05-13 3 91
Cover Page 1998-12-31 1 41
Abstract 1991-06-30 1 13
Cover Page 1996-09-30 1 17
Description 1991-06-30 12 527
Claims 1991-06-30 3 81
Drawings 1991-06-30 3 76
Representative drawing 1998-12-31 1 5
Commissioner's Notice - Application Found Allowable 1998-03-12 1 165
Correspondence 1998-08-21 1 29
Correspondence 1998-03-12 1 103
Correspondence 1998-05-13 5 137
Fees 1999-09-24 1 29
Fees 2000-10-05 1 28
Correspondence 2004-12-01 1 20
Correspondence 2005-07-25 1 16
Fees 1996-09-24 1 58
Fees 1996-06-27 1 61