Apple, Inc. v. Motorola, Inc. et al

Filing 97

Declaration of Carlos A. Rodriguez filed by Defendants Motorola Mobility, Inc., Motorola, Inc. re: 96 Claims Construction Initial Brief, 95 Motion Requesting Claims Construction (Attachments: # 1 Exhibit 1 - Patent No. 6,275,983, # 2 Exhibit 2 - Patent No. 5,969,705, # 3 Exhibit 3 - Patent No. 5,566,337, # 4 Exhibit 4 - Patent No. 5,455,599, # 5 Exhibit 5 - Patent No. 6,424,354, # 6 Exhibit 6 - Reissued Patent No. RE 39,486, # 7 Exhibit 7 - Patent No. 5,929,852, # 8 Exhibit 8 - Patent No. 5,946,647, # 9 Exhibit 9 - Patent No. 5,481,721, # 10 Exhibit 10 - Patent No. 6,493,002, # 11 Exhibit 11 - Patent No. 6,175,559, # 12 Exhibit 12 - Patent No. 5,490,230, # 13 Exhibit 13 - Patent No. 5,319,712, # 14 Exhibit 14 - Patent No. 5,572,193, # 15 Exhibit 15 - Excerpts from '983 Patent Prosecution History, # 16 Exhibit 16 - Excerpts from '354 Patent Prosecution History, # 17 Exhibit 17 - Excerpts from '486 Patent Prosecution History, # 18 Exhibit 18 - Excerpts from '230 Patent Prosecution History, # 19 Exhibit 19 - Apple's Infringement Contentions Claim Chart for '983 Patent, # 20 Exhibit 20 - Apple's Infringement Contentions Claim Chart for '705 Patent, # 21 Exhibit 21 - Apple's Infringement Contentions Claim Chart for '337 Patent, # 22 Exhibit 22 - Apple's Infringement Contentions Claim Chart for '599 Patent, # 23 Exhibit 23 - Apple's Infringement Contentions Claim Chart for '354 Patent, # 24 Exhibit 24 - Apple's Infringement Contentions Claim Chart for '486 Patent, # 25 Exhibit 25 - Apple's Infringement Contentions Claim Chart for '852 Patent, # 26 Exhibit 26 - Apple's Infringement Contentions Claim Chart for '647 Patent, # 27 Exhibit 27 - Apple's Infringement Contentions Claim Chart for '721 Patent, # 28 Exhibit 28 - Apple's Infringement Contentions Claim Chart for '002 Patent, # 29 Exhibit 29 - Excerpts from NeXTSTEP Object-Oriented Programming and the Objective C Language, # 30 Exhibit 30 - July 30, 2010 ITC Order Construing Terms of Asserted Claims in Inv. No. 337-TA-704, # 31 Exhibit 31 - April 4, 2011 Joint Motion to Amend Filed in ITC Inv. No. 337-TA-710, # 32 Exhibit 32 - Excerpts from '002 Patent Prosecution History, # 33 Exhibit 33 - Patent No. 5,588,105, # 34 Exhibit 34 - Patent No. 5,659,693, # 35 Exhibit 35 - Henderson & Card Article, # 36 Exhibit 36 - Patent No. 5,202,961, # 37 Exhibit 37 - Patent App. No. 08/316,237) (Hansen, Scott)

EXHIBIT 16

Docket No.

Applicant(s):
Serial No.:
Filed:
For:

Matheny, et al.OLDce:P006
09/287,172 -K 4hAOI
April 1, 1999
MENU STATE SYSTEM

Gro'up Art Unit:
Examiner:

AMENDMENT

3048-7037

2672

M. Luu

40G

Ij,

Honorable Commissioner

no/%VCalm 0 0

of Patents and Trademarks
Washington, D.C. 20231

o10
-

Sir:
In response to the Examiner's Office action of April 24, 2001, please amend the
application as follows.
IN THE CLAIMS
Please add/nw claims 57 to 85, as follows:

&

*PN
(NEW)
A method for operating a com.puter-implemented event notification system for
propagating, among a plurality of objects, events representing changes in the objects, the
operating method comprising the steps of:
(a)
creating, on behalf of a receiver object, connection information representing the
receiver object's interest in, and an associated object method for, receiving notification of a
change to a source object;
(b)
registering the connection information using a connection object;
(c)
creating an event representing a change in the source object, responsive to the

change in the source object; and

(d)
notifying the receiver object of the event by invoking the associated object
method for receiving notification registered using the connection objct only if the event
in formation corresponds to an interest registered on behalf of the receiver object.
(NEW)
The operating method of claim3 %l wherein the connection object is associated
with status information, the operating method further comprising the step of:
(b.1I) using the connection information in the connection object to configure the status
information to represent whether the notifying step (d) is activated or inactivated.
iomation is
~NW)
The operating method of claimt%tweei h oneto
asocaed with a notification type corresponding to a connection object method, the operating
method fuirther comprising the step of:

26130_1LDOCV

serial No.: 09/287,172

2

Docket No. 3048-7037

(c.f1) invoking the connection object method corresponding to the notification type
specified by thd connection information in the connection object.

'6Q. (NEW)

1q2'

The operating method of claim 5-,wherein:
each of a notification type plurality corresponds to a unique- connection object method
different from the connection object method corresponding to another of the notification type
plurality.

16,. (NEW)
'The operating method of claimNfurther comprising the step of:
(c.1.1) invoking a connection object metqad responsible for using the connection
information in the connection object to modify a 'name associated with the receiver object.
6.(NEW)
The operating method of claim
frther comprising the step of:
(c. 1.1) invoking a connection object method responsible for using the connection
information in the connection object to modify a graphic associated with the receiver object.

,31r

\.(NEW)

35W

The operating method of claimiN~ flurther comprising the step of:
(c. 1.1) invoking a connection object method responsible for using the connectioh
information in the connection object to create or mhodify' data associated with the receiver object.
(NEW)
The operating method of claimAi further comprising the step of:
(c.1. 1) invoking a connection object method responsible for using the connection
teconnection object to read data associated with the receiver object.

M\4W)

3?

The operating method of claimgX further comprising the step of:
invoking a connection object method responsible for using the connection
(c.1.2)
information in the connection object to execute an undo function associated with the receiver
The operating method of claim fi further comprising the step of:
invoking a connection object method responsible for using the connection
information in the connection object to execute a redo function associated wit the receiver
object.
A method for operating a computer-implemented event notification system for
MQ~W)
propagating, among a plurality o-fobjects, events representing changes in the objects, the
operating method comprising the steps of:
(a)
creating, on behalf of a receiver object, connection information representing the
receiver object's interest in, and an associated object method far, receiving notification of a
change to a source abject:
(b)
registering the connection information using a connection object;
(c)
creating an event representing a change in the-source object, responsive to the
change in the source object;
(d)
notifNying the receiver object of the event by invoicing the associated abject
method for receiving notification registered using the connection object only if the event
information corresponds to an interest registered on behalf of the receiver object; and
(e)
using the connection information in the connection object to configure status
information to enable the notifying step (d).I

26130 vI

. §erialNo.: 09/297,172

SeriaNo.:09/28,172Docket
No. 3048-7037

#ItEW) A method for operating a computer-implemented event notification system for
propagating, among a plurality of objects, events represetiting changes in the objects, the
operating method comprising the steps of: .
(a)
creating, on behalf of a receiver object, connection information representing the
receiver object's interest in, and an associated object method far, receiving notification of a
change to a source object;
(b)
registering the connection information using a connection object;
(c)
creating an event representing a change in the source object, responsive to the
change in the source object;
(d)
notifying the receiver object of the event by invoking the associated object
method for receiving notification registered using the connection obj eat only if the event
information corresponds to an interest registered on behalf of the receiver object; and
(e)
using the connection information in the connection object to configure status
information to disable the notifying step (d).
J' INEW)
A method for operating a computer-implemented event notification system for
propagating, among a plurality of objects, events representing changes in the objects, the
operating method comprising the steps of:
(a)
creating, on behalf of a receiver object, connection information representing the
receiver object's interest in, and an associated object method for, receiving notification of a
change to a source object;
(b)
registering the connection information using a connection object;
(c)
creating an event representing a change in the source obj ect, responsive to the
change in the source object;
(d)
notii3'ing the receiver object of the event by invoking the associated abject
method for receiving notification registered using the connection object only if the event
information corresponds to an interest registered on behalf of the receiver object;
said connection information being associated with a notification type corresponding to a
connection object method;
(e)
invoking the connection object method corresponding to the notification type
specified by the connection information in the connection object;
each of a notification typylurality corresponding to the same single connection object
method; and
(f)
transferring notification type information between two objects.

Q.(NEW)

The operating method of claim N,~ further comprising the step of:
(c. 1.1i) invoking a connection object method responsible for using the connection
infornation in the connection object to modify a name associated with the receiver object.

*5.4

\.(NEW)
The operating method of claim.N ftirther comprising the step of:,
(c. 1.1) invoking a connection object method responsible for using the connection
information in the connection object to modify a graphic icon associated with the receiver object.

q(J I

LkI

'5. (NEMW)
The operating method of claimXQ fuirther comprising the step of:
(c. 1.1) invoking a connection object method responsible for using the connection
information in the connection object to read data associated with the receiver object.

26130 Ai

Serial'No.: 09/287,172

DocketNo. 3048-7037

The operating method of claim$ further comprising the step of:
,Z,(NE)>4
(c. 1.1) invoking a connection object method responsible for using the connection
information in the connection object to create or modify data associated with the receiver object.
J .

Wi.

X (NEW)
The operating method of claim/wherein the data associated with the receiver
object includes descriptive textual data.
OF?.
D4'
,((NEW) The operating method of claim'W3 -further comprising the step of:
(c. 1.2) invoking a connection object method responsible for using the connection
information in the connection object to execute an undo function associated with the receiver
object.
;.6. (NEW)
The operating method of claimXTfurther comprising the step of:
(c.1 .2) invoking a connection object method responsible for using the connection
information in the connection object to execute a redo function associated with the receiver
object.

.51

7W, (NEW)
A method for operating a computer-implemented event notification system for
propagating, among a plurality of objects, events representing changes in the objects, the
operating method comprising the steps of:
(a)
creating, on behalf of a receiver object, connection information representing the
receiver object's interest in, and an associated object method for, receiving notification of a
change to a source obj eat;
(b)
registering the connection information with a notifier object;
(c)
creating an event representing a change in the source object, responsive to the
change in the source object; and
(d)
notifying the receiver object of the event by invoking the associated object
method for receiving notification registered with the notifier object only if the event information
corresponds to an interest registered on behalf of the receiver object.

A8. (NW)

The operating method of claim X, wherein the notifier object is associated with

status information, the operating method further comprising.thc step of:
(b,i) using the connection information in the notifier object to configure the status
information to make the notifyingjstep (d) active or passive.

157/

9S.

The operating method of claim 41, wherein the connection information is
A9 (NEW)
associated with a notification type corresponding to a notifier object method, the operating
method further comprising the step of:
(c. 1) invoking the notifiei object method corresponding to the notification type
specified by the connection information in the notifier object.

53

fl(NEW)
The operating method of claimfld wherein a notification type plurality all
correspond to the same single notifier object method, the operating method further comprising
the step of:
transferring notificationi type information between two objects.

Sa-,

4 .Rr (NEW)

26130 vi

The operating method of claim

53

7'P further comprising the step of:

Serial'No.:.09/287,172

SeriaNo.:9/28,172Docket
No. 3048-7037

invoking a notifier object method responsible for using the connection
information in the notifier object to create or modify data associated with the receiver object.
The operating method of claimn. further comprising the step of:
S(NEW)
(c. 1.1 invoking a notifier object method responsible for using the connection
information in the notifli object to read data associated with the receiver object.
A-Ir(NEW)
attribute.

The operating method of claimOV'wherein the event has an associated type

6rd,

&7
creating isIniitdb h
step (c)
The operating method of claim Xwherein the
W.(NW)
notifier abject.
creating step (c) is initiated by the
S7
The operating method of claim -7.wherein the
-. (NEW)
source object.

REMARKS
I.

STATU S OF THE CLAIMS
L7
Claims:2 to 56 remain in the case and new claims 57 toS85 are added tothe case.

II.

THE El(AMINER'S REJECTION OF THE CLAIMS

Claims ~7 to 56 are rejected under 35 US.C §111, first paragraph as containing subject
as
matter which w~ not described in the specification in such a way as to reasonably convey to one
skilled in the rellevant art that thr inventors, at the time the application was filed, had posession
of the claimed i rivention.
Ill.

THE A] PPLICANT'S RESPONSE

The Applicant respectflully requests that the Examiner withdraw this rejection, in view of
the flil disclosure of the invention-in the specification of the application, as filed.
[Al Rejection of claims 48 to 56
The Examiner has rejected claims 48 to 56 on the basis that the following limitations in
the claims are not shown in the specification or the figures. Regarding claim 48, the Examiner
specifically asks:
Ill] What is "a consumer object"?
[2] What is "a supplier object"?
[3] What is "a channel object"?

26130Avi

Serial'No;: 09/287,172

Docket o 0873
Dce No. 3048-7037

[4] Where in the drawings does it show "notifying the consumer object of the event by
invoking the associated object method for receiving notification registered with the
channel object only if the event information corresponds to an interest registered on
behilf of the consumer object"?
In response, the Applicant repeats Claim 48 here, which reads as follows:
48. A method for operating a computer-implemented event notification system for propagating
among a plurality of objects, events representing changes in the objects, the operating method
comprising the steps of:
(a) creating, on behalf of a consumer object, connection information representing the
consumer object's interest in, and an associated object method for, receiving notification of a
change to a supplier object;
(b) registering the connection information with a channel object;
(c) creating an event representing a change in the supplier object, responsive to the change in
the supplier object; and
(d) notifying the consumer object of the event by invoking the associated object method
for receiving notification registered with the channel object only if the event Information
corresponds to an interest registered on behalf of the consumer object
The Applicant will point out where these elements may be found in the Applicants
specifi6akion.
11

-

The notification framework is disclosed at Page 2, line I to page 3, line 26; page 23, lines
24; and page 28$, line 15 to page 3 1, lineS8, and in Figure 18.
(1] The "consumer object" is "the receiver object" disclosed at page 28, lines 28-29 and

31.
[2] The "supplier object" is "source object" disclosed at page 28, line 24-25
[3] The "channel object" is "notifier object" disclosed at page 28, line 27. The "notifier
objects" and "connection objects" in the specification on page 28, both relate to the "channel
object" in Claim 48. Claim 48 also refers to "connection information" which is contained within
"connection objects" disclosed at page 28, line 29.
[4] The "notifying the consumer object..." is disclosed in the specification at page 30, line
I to page 3 1, line 8 and in Figure IS. They disclose that the connection object is registered with a
notifier object signifying that the connection object has responsibility for one or more receiver
objects which have a general interest in events generated by the source object. The connection
objects, in turn, have more specialized information about which of the events generated by a
source object are of particular .interest to each of the receiver objects for which it is responsible.
This is disclosed at in association with Figure 18.

26130 vi

*

Serial'No.: 09/287,172

7

Docket No. 3048-7037

The specification at page 30, line I to page 31, lineS8 discloses that the invention is based
on the concept of a notification framework that provides a mechanism for propagating change
information between objects. The framework allows receiver objects to express interest in, and
receive notification about changes to source objects in which they have an interest. A standard
interface is provided for classes that provide notification to receiver objects. Notifier classes
enable receiver objects to register their connection objects for receiving notification of events
from a particular source object. The notifier objects (instantiated from the notifier classes)
register a list of connection objects, each connection object corresponding to one or more
receiver objects. The connection object dispatches the notification from the notifier objects to
the specific receiver objects that have identified to the connection object an interest in specific
events. These connection objects allow specialization of how notifications are delivered to
different classes of receivers. This is disclosed in association with Figure 18.
[BI Rejection of claims 27 to 47
The Examiner has rejected claims 27 to 47 on the basis that the following limitations in
the claims are not shown in the specification or the figures.
Regarding Claim 27
Regarding claim 27, the Examiner specifically asks:
(1] What is "a first object"?
[2] What is "an associated object"?
[3] What is "a second object"?
[4] What is "a connection object"?
(5] Where in the specification and drawings does it show " creating, on behalf of a first
abject, connection information representing the first object's interest in, and an associated
object method for, receiving notification of a change to a second object"?
[6] Where in the specification and drawings does it show " notifying the first object of the
event by invoking the associated object method for receiving notification registered with
the connection object onlykif the event information corresponds to an interest registered
on behalf of the first object"
In response, the Applicant repeats Claim 27 here, which reads as follows:
27.
A method for operating a computer-implemented event notification system for
propagating, among a plurality ofobjects, events representing changes in the objects, the
operating method comprising the steps of:
(a)
creating, on behalf of a first object, connection information representing the
first object's interest in, and an associated object method for, receiving notification of a
change to a second object;
(b)
registering the connection information with a connection object;
(c)
creating an event representing a change in the second object, responsive to the
change in the second objection; and
(d)
notifying the first object of the event by invoking the associated object
method for receiving notification registered with the connection object only if the event
Information corresponds to an interest registered on behalf of the first object.
26130 v1

Senal'No.: 09/287,172

SeriaNo.:09/28,172Docket
Na. 3048-703 7

The Applicant will point out where these elements may be found in the Applicant's
specification.
El] "a first object" is "the receiver object" disclosed at page 28, lines 28-29 and 31.
[2] "an associated object method" is "the appropriate method of the notification receiver
.. the function block 1880, the notification receiver takes the appropriate action" disclosed at
at
page 30, line 32 to page 3 1, line 1.
(3] "a second object" is the "source object" disclosed at page 28, line 24-25
(4] "a connection object" is the 'connection object" disclosed at page 28, line 29.

(5] " creating, on behalf of a first object, connection information representing the
first object's interest in, and an associated object method for, receiving notification of a
change to a second object" is disclosed at Page 2, line I to page 3, line 26; page 23, lines 11 24; and page 28, line 15 to page 3 1, lineS8, and in Figure 18. The "connection information" is
contained within "connection objects" disclosed at page 28, line 29. The specification at page 30,
line 1 to page 3 1, line 8 and Figure 18 disclose that the connection object is registered with a
notifier object signif$'ing that the connection object has responsibility for one or more receiver
objects which have a general interest in events generated by the source object. The connection
objects, in turn, have more specialized information about which of the events generated by a
source object are ofparticular interest to each of the receiver objects for which.it is responsible.
This is disclosed at in association with Figure 18.
[61 "notifying the first object of the event by invoking the associated object method
for receiving notification registered with the connection object only If the event information
corresponds to an interest registered on behalf of the first object" is disclosed at Page 2, line
I to page 3, line 26; page 23, lines 11 -24; and page 28, line 15 to page 31, line 8, and in Figure
18. The specification at page 30, line i to page 31, line 8 discloses that the invention is based on
the concept of a notification framework that provides a mechanism for propagating change
information between objects. The framework allows receiver objects to express interest in, and
receive notification about changes to source objects in which they have an interest. A standard
interface is provided for classes that provide notification to receiver objects. Notifier classes
enable receiver objects to register their connection objects for receiving notification of events
from a particular source object. The notifier objects (instantiated from the notifier classes)
register a list of connection objects, each connection object corresponding to one or more
receiver objects. The connection object dispatches the notification from the notifier objects to
the specific receiver objects that have identified to the connection object an interest in specific
events. These connection objects allow specialization of how notifications are delivered to
different classes of receivers. This is disclosed in association with Figure 18.
Regarding Claim 30
Regarding claim 30, the Examiner specifically asks: Where in the specification and
drawings does it show "each of a notification type plurality corresponds to a unique connection

26130 Y1

,Serial'No.: 09/287,172

Dce o 3048-7037
DocketNo. 0873

object method different from the connection object method corresponding to another of the
notification type plurality"?9
In response, the Applicant repeats Claim 30 here, which reads as follows:
.30.

The operating method of claim 29 wherein:
each of a notification type plurality corresponds to a unique connection object method
different from the connection object method corresponding to another of the notification type
plurality.
The Applicant will point out where this element may be found in the Applicant's
specification.
Page 28, lines 24 to 34 describe the notifier classes providing notification source objects
with the means to manage lists of clients and dispatch notifications to those clients. Connection
objects provide the dispatch of notifications from the notifier to specific notification receiver
objects. These objects allow specialization of how notifications are delivered to different classes
of receivers. This is in conjunction with the disclosure in Figure 18. In addition, page 2, line 24
to page 3, line 4 discloses this feature.
Still further, page 59, lines 20 to 34 discloses that the connection dispatches the
notification to the appropriate method of the notification receiver. This disclosed method
performs the work, i.e., the connection object method associated with a particular function calls
the corresponding method in the receiver object to do the work.
Regarding Claim 37
Regarding claim 37, the Examiner specifically asks: Where in the specification and
drawings does it show:
[1] "lan event listener object"?
[2] "an event source object"?
[3] "la connection object"?
[4] "notifying the event listener object of the event by invoking the associated object
method for receiving notification registered with the connection object only if the event
information corresponds to an interest registered on behalf of the event listener object"
In response, the Applicant.repeats Claim 37 here, which reads as follows:
37.
A method for operating a computer-implemented event notification system for
propagating, among a plurality of objects, events representing changes in the objects, the
operating method comprising the steps of:
(a)
creating, on behalf of an event listener object, connection information
representing the event listener object's interest in, and an associated object method for, receiving
notification of a change to an event source object;
(b)
registering the connection information with a connection object;
(c)
creating an event representing a change in the event source object, responsive to
the change in the event source object; and

26130 vI

-Serial No.: 09/287,172

Dce o 3048-7037
DocketNo. 0873

(d)
notifying the event listener object of the event by invoking the associated
object method for receiving notification registered with the connection object only if the
event information corresponds to an Interest registered on behalf of the event listener
object.
The Applicant will point out where this element may be found in the Applicants
specification.
[1] "an event listener object" is "the receiver object" disclosed at page 28, lines 28-29 and
31.
[2] "an event source object" is the "source object" disclosed at page 28, line 24-25.
[3] "a connection object" is the "connection object" disclosed at page 28, line 29.
[4] "notifying the event listener abject of the event by invoking the associated object
method for receiving notification registered with the connection object only if the event
information corresponds to an interest registered on behalf of the event listener object" is
disclosed in the specification at page 30, line I to page 31, line 8 and in Figure 18. They disclose
that the connection object is registered with a notifier object signifying that the connection
object has responsibility for one or mare receiver objects which have a general interest in events
generated by the source object. The connection objects, in turn, have more specialized
information about which of the events generated by a source object are of particular interest to
each of the receiver objects for which it is responsible. This is disclosed at in association with
Figure 18.
The specification at page 30, line 1 to page 31, line 8 discloses that the invention is based
on the concept of a notification framework that provides a mechanism for propagating change
information between objects. The framework allows receiver objects to express interest in, and
receive notification about changes to source objects in which they have an interest. A standard
interface is provided for classes that provide notification to receiver objects. Notifier classes
enable receiver objects to register their connection objects for receiving notification of events
from a particular source object. The notifier objects (instantiated from the notifier classes)
register a list of connection objects, each connection object corresponding to one or more
receiver objects. The connection object dispatches the notification from the notifier objects to

the specific receiver objects that have identified to the connection object an interest in specific
events. These connection objects allow specialization of how notifications are delivered to

different classes of receivers, This is disclosed in association with Figure 18.
By the above remarks, the Applicant believes all of the issues raise by the Examiner have
been resolved. Accordingly, the Applicant respectfully requests the Examiner's reconsideration
of the claims, allow the claims and pass the case to issue.

26130 v]

Serial No.: 09/287,172

Seril No: 0/287172Docket
No. 3048-7037

The Assistant Commissioner is hereby authorized to charge any additional fees which
may be required for the timely consideration of this amendment under 37 C.F.R. §§ 1.16, ,or
credit any overpayment to Deposit Account No. 13-4503, Order No. 3048-7037.
Respectfully submitted,
MORGAN &FINNEGAN, L.L.P.
Dated:

SENDER'S ADDRESS:
Morgan & Finnegan L.L.P.
1775 Eye Street, N.W. Suite 400
Washington, D.C. 20006

26 130 v1

, / -h_ O
gi tH 'I
V s oneti 26,279
R
No.
0
tor'
20 5 -7887 -Telephone
202-857-7929 - Facsimile

'#

-z

76

Z!

Docket No. 3048-7037

IN THE UNITED STATES PATENT AND TRADEMARK nMVRC

Applicant(s): Matheny et a].
2

Serial No.: 09/287.172GruAtUn;26
Examiner: M. Lu

Filed: April 1, 99
For:

MENU STATE SYSTEM
PETITION AND FEE FOR EXTENSION OF TIME (37 C-PKR. A1,l36(aM)

Chno,0 g Cent"er

Commissioner for Patents
Washington, D.C. 20231
Sir:

I1. This Is a petition for an extension of time for responding to the official action mailed 04124/01.
2.

The communication in connection with the matter for which this extension is requested
is filed herewith.
has been fled on

3.

Q

-

Applicant(s) is/are entitled to Small Entity Status.
LIStatement has already been tiled

4.

Total Months

Fee for Other

Fee for

ReQestd
tanSmal EftSmallEn
a. II
b.two
C.three
d.four
e.five
f.

5.
6.

El
Zi

Q

onp month
months
months
months
months

$110.00
$390.00
$890.00
$1,390.00
$1,890.00

An extension for~ months has already been secured for filing the above-identified
communication and the fee paid therefor of $ _ is deducted from the total fee due for
the total months of extension now requested. The fee for this extension
($ ..... J, minus the fee previously paid ($
) equals $
(total fee due).
Acheck In the amount of $-

to cover the extension fee is attached.

Charge fee to Deposit Account No.U13Z45D. Order No. 3049Z703
THIS SHEET IS ATTACHED.
MIfl 00000002 134500 09287172
08/22/2001 RD
01 FN115B
110.00 CH$
27106 v1

$55.00
$195.00
$445.00
$695.00
$945.00

A DUPLICATE COPY OF

28

Docket No. 3048-7037
7.

The Commissioner is hereby authorized to charge any additional fees which may be required by
this paper, or credit any overpayment to Deposit Account No. 13A50O. Order No. 3048-7Of7.
A DUPLICATE COPY OF THIS SHEET IS ATTACHED.
Respectfully submitted,
MORGAN & PINNCAN L.L.P.

Dated:

__

__

c__

__k_

(2U)0-7929 Facsimile
CORRESPONDENCE ADDRESS:
MORGAN & FINNEGAN, L.L.P.
345 Park Avenue
New York, NY 10154-0053

2
27106 v I