Yehoon commited on
Commit
ffc28b3
·
verified ·
1 Parent(s): d39aa59

Add files using upload-large-folder tool

Browse files
This view is limited to 50 files because it contains too many changes.   See raw diff
Files changed (50) hide show
  1. applicant/12976306.xml +258 -0
  2. applicant/15171192.xml +2 -0
  3. prior_art/09780035.xml +0 -0
  4. prior_art/10522933.xml +22 -0
  5. prior_art/10545100.xml +15 -0
  6. prior_art/10546583.xml +78 -0
  7. prior_art/10553926.xml +0 -0
  8. prior_art/10577294.xml +31 -0
  9. prior_art/10581087.xml +0 -0
  10. prior_art/10592554.xml +0 -0
  11. prior_art/10597291.xml +335 -0
  12. prior_art/10711736.xml +0 -0
  13. prior_art/10880754.xml +545 -0
  14. prior_art/10897695.xml +109 -0
  15. prior_art/10903798.xml +19 -0
  16. prior_art/10911159.xml +112 -0
  17. prior_art/10922650.xml +0 -0
  18. prior_art/10926801.xml +627 -0
  19. prior_art/10953863.xml +65 -0
  20. prior_art/10979005.xml +35 -0
  21. prior_art/10993882.xml +33 -0
  22. prior_art/11012499.xml +0 -0
  23. prior_art/11016221.xml +502 -0
  24. prior_art/11035472.xml +705 -0
  25. prior_art/11038590.xml +0 -0
  26. prior_art/11047958.xml +21 -0
  27. prior_art/11065197.xml +634 -0
  28. prior_art/11066622.xml +350 -0
  29. prior_art/11068608.xml +376 -0
  30. prior_art/11097034.xml +29 -0
  31. prior_art/11102007.xml +284 -0
  32. prior_art/11103971.xml +325 -0
  33. prior_art/11111107.xml +530 -0
  34. prior_art/11120656.xml +0 -0
  35. prior_art/11124751.xml +25 -0
  36. prior_art/11125207.xml +0 -0
  37. prior_art/11127704.xml +157 -0
  38. prior_art/11128970.xml +897 -0
  39. prior_art/11132658.xml +107 -0
  40. prior_art/11140114.xml +82 -0
  41. prior_art/11141171.xml +348 -0
  42. prior_art/11146897.xml +1 -0
  43. prior_art/11153123.xml +37 -0
  44. prior_art/11163737.xml +16 -0
  45. prior_art/11184301.xml +42 -0
  46. prior_art/11198620.xml +0 -0
  47. prior_art/11200898.xml +579 -0
  48. prior_art/11207865.xml +68 -0
  49. prior_art/11211134.xml +37 -0
  50. prior_art/11221522.xml +490 -0
applicant/12976306.xml ADDED
@@ -0,0 +1,258 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>12976306</doc-number>
8
+ <date>2010-12-22</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <boundary-data type="header">784-103 (SH-37973-US-DMC)</boundary-data>
14
+ <heading id="h-1">DOCUMENT INFORMATION TRANSMISSION METHOD AND APPARATUS</heading>
15
+ <heading id="h-2">PRIORITY</heading>
16
+ <p id="p-1" num="1">
17
+ <boundary-data type="line-number">5 </boundary-data>
18
+ This application claims priority under 35 U.S.C. <confidence value="5">§</confidence>
19
+ 119(a) to a Korean Patent Application No. 10-2009-0136223, filed on December <part-num-ref name="Korean Patent Application No. 10-2009-0136223, filed on December">31,</part-num-ref>
20
+ <part-num-ref name="Korean Patent Application No. 10-2009-0136223, filed on December 31,">2009,</part-num-ref>
21
+ in the Korean Intellectual Property Office, the entire disclosure of which is incorporated herein by reference. </p>
22
+ <heading id="h-3">BACKGROUND OF THE INVENTION</heading>
23
+ <p id="p-2" num="2">
24
+ <boundary-data type="line-number">10 </boundary-data>
25
+ 1. Field of the <confidence value="5">I</confidence>
26
+ nvention The present invention relates generally to a document information transmission scheme, and more particularly, to a document information transmission <boundary-data type="line-number">
27
+ <confidence value="5">1</confidence>
28
+ 5 </boundary-data>
29
+ method and apparatus to transmit information about a document, on which a user is currently working, to another object. </p>
30
+ <p id="p-3" num="3">2. Descri<confidence value="8">p</confidence>
31
+ tion of the Related Art Bookmarking has been widely used to store an address of a specific site <boundary-data type="line-number">20 </boundary-data>
32
+ during web browsing, so that a desired web page can be easily accessed later. </p>
33
+ <p id="p-4" num="4">Recently, the use of Internet services in portable devices using a touch input scheme on small screens has increased. In such portable devices, to store an address of a web page currently being browsed, a bookmarking button is usually clicked in a toolbar or a side menu above the browser. However, in a portable device having a <boundary-data type="line-number">25 </boundary-data>
34
+ small screen and limited input means, the user needs to perform several clicks and manipulate a separate menu. </p>
35
+ <p id="p-5" num="5">Moreover, to transmit information about a document on which the user is currently working using an application other than a web browser to another application or another object, the user must first store the document and then use an <boundary-data type="line-number">30 </boundary-data>
36
+ open or insertion menu function in the other application, which is troublesome to perform in a portable device. </p>
37
+ <boundary-data type="header">
38
+ <confidence value="7">1</confidence>
39
+ </boundary-data>
40
+ <boundary-data type="header">784-103 (SH-37973-US-DMC)</boundary-data>
41
+ <heading id="h-4">SUMMARY OF THE INVENTION</heading>
42
+ <p id="p-6" num="6">
43
+ <page-break num="2"/>
44
+ The present invention provides a document information transmission method and apparatus to transmit information about a document to another object in a <boundary-data type="line-number">5 </boundary-data>
45
+ simple way when a user opens and views the document or edits the document. </p>
46
+ <p id="p-7" num="7">According to an aspect of the present invention, there is provided a document information transmission method including, upon sensing a touch or click input on an opened document, recognizing the sensed input as an information transmission command for the document, and, upon sensing a release input on a target object, <boundary-data type="line-number">10 </boundary-data>
47
+ transmitting information about the document to the target object. </p>
48
+ <p id="p-8" num="8">The transmitting of the information may include determining information to be transmitted to the target object according to a type of the target object.</p>
49
+ <p id="p-9" num="9">The document information transmission method may further include switching an event mode to a transmission mode for transmitting the information about the <boundary-data type="line-number">15 </boundary-data>
50
+ document. </p>
51
+ <p id="p-10" num="10">The switching of the event mode may include switching the event mode to the transmission mode when the target object to which the information about the document is to be transmitted is selected or opened.</p>
52
+ <p id="p-11" num="11">The recognizing the sensed input as the information transmission command <boundary-data type="line-number">20 </boundary-data>
53
+ may include, upon sensing the touch or click input, generating and displaying a movable object for temporarily storing the information about the document, and, upon sensing a move or drag input, moving the movable object. </p>
54
+ <p id="p-12" num="12">The opened document may be a web page.</p>
55
+ <p id="p-13" num="13">The transmitting of the information may include storing an address of the web <boundary-data type="line-number">25 </boundary-data>
56
+ page in a bookmark list if the target object is the bookmark list. </p>
57
+ <p id="p-14" num="14">The transmitting of the information may include generating a snap shot of the document and storing the snap shot in a clip board if the target object is the clip board.</p>
58
+ <p id="p-15" num="15">The transmitting of the information may include inserting document content <boundary-data type="line-number">30 </boundary-data>
59
+ into a document which is currently being edited by a document editor if the target object is the document editor. </p>
60
+ <p id="p-16" num="16">The transmitting of the information may include storing a file corresponding to the document in a folder if the target object is the folder.</p>
61
+ <boundary-data type="header">
62
+ <confidence value="8">2</confidence>
63
+ </boundary-data>
64
+ <boundary-data type="header">784-103 (SH-37973-US-DMC)</boundary-data>
65
+ <p id="p-17" num="17">
66
+ <page-break num="3"/>
67
+ The transmitting of the information may include instructing a text message transmission application to transmit document content to a phone number corresponding to a phone directory item on which the release input is sensed, if the target object is the phone directory. </p>
68
+ <p id="p-18" num="18">
69
+ <boundary-data type="line-number">5 </boundary-data>
70
+ According to another aspect of the present invention, there is provided a document information transmission apparatus including a touch screen for inputting and outputting information and a controller for, upon sensing a touch or click input on an opened document, recognizing the sensed input as an information transmission command for the document, and upon sensing a release input on a target object, <boundary-data type="line-number">10 </boundary-data>
71
+ transmitting information about the document to the target object. </p>
72
+ <heading id="h-5">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
73
+ <p id="p-19" num="19">The above and other features and advantages of the present invention will <boundary-data type="line-number">15 </boundary-data>
74
+ become more apparent by describing in detail embodiments thereof with reference to the attached drawings in which: </p>
75
+ <p id="p-20" num="20">FIG. 1 is a block diagram of a document information transmission apparatus according to an embodiment of the present invention;</p>
76
+ <p id="p-21" num="21">FIG. 2 is a flowchart illustrating a document information transmission method <boundary-data type="line-number">20 </boundary-data>
77
+ according to an embodiment of the present invention; </p>
78
+ <p id="p-22" num="22">FIGs. 3 through <part-num-ref name="through">6</part-num-ref>
79
+ are diagrams illustrating screens in which an address of a web page is transmitted directly to a bookmark bar, according to an embodiment of the present invention; </p>
80
+ <p id="p-23" num="23">FIG. 7 is a diagram illustrating a screen in which a snap shot of a web page is <boundary-data type="line-number">25 </boundary-data>
81
+ transmitted directly to a clipboard, according to an embodiment of the present invention; and FIG. 8 is a diagram illustrating a screen in which content of a text document is transmitted directly to a phone directory, according to an embodiment of the present invention. </p>
82
+ <p id="p-24" num="24">
83
+ <boundary-data type="line-number">
84
+ <confidence value="88">30</confidence>
85
+ </boundary-data>
86
+ </p>
87
+ <heading id="h-6">DETAILED DESCRIPTION OF EMBOD<confidence value="8">I</confidence>
88
+ MENTS OF THE PRESENT INVENTION </heading>
89
+ <p id="p-25" num="25">Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.</p>
90
+ <boundary-data type="header">
91
+ <confidence value="8">3</confidence>
92
+ </boundary-data>
93
+ <boundary-data type="header">784-103 (SH-37973-US<confidence value="5">-</confidence>
94
+ DMC) </boundary-data>
95
+ <p id="p-26" num="26">
96
+ <page-break num="4"/>
97
+ FIG. 1 is a block diagram of a document information transmission apparatus <part-num-ref name="document information transmission apparatus">100</part-num-ref>
98
+ according to an embodiment of the present invention. </p>
99
+ <p id="p-27" num="27">Referring to FIG. 1, the document information transmission apparatus <part-num-ref name="document information transmission apparatus">100</part-num-ref>
100
+ may include a touch screen <part-num-ref name="touch screen">110</part-num-ref>
101
+ for inputting and outputting information and a <boundary-data type="line-number">5 </boundary-data>
102
+ controller <part-num-ref name="controller">120</part-num-ref>
103
+ for processing information which is input through the touch screen <part-num-ref name="touch screen">110</part-num-ref>
104
+ and outputting the processing result through the touch screen <part-num-ref name="touch screen">110.</part-num-ref>
105
+ The document information transmission apparatus <part-num-ref name="document information transmission apparatus">100</part-num-ref>
106
+ may further include a communication unit <part-num-ref name="communication unit">130</part-num-ref>
107
+ for communicating with an external server or a network. The communication unit <part-num-ref name="communication unit">130</part-num-ref>
108
+ may be a device for receiving a web page through communication with a <boundary-data type="line-number">10 </boundary-data>
109
+ web server, or accessing a mobile communication network according to an embodiment of the present invention. The controller <part-num-ref name="controller">120,</part-num-ref>
110
+ upon sensing a touch input or a click input on a document displayed through the touch screen <part-num-ref name="touch screen">110,</part-num-ref>
111
+ recognizes the sensed input as an information transmission command for the document, and upon sensing a release input on a target object, transmits information <boundary-data type="line-number">15 </boundary-data>
112
+ about the document (or document information) to the target object. If an event mode is a normal mode, the touch or click input is recognized as a normally used event; whereas if the event mode is a transmission mode, the touch or click input is recognized as the information transmission command for transmitting the document information to the target object, that is, an external object. Detailed functions and <boundary-data type="line-number">20 </boundary-data>
113
+ operations<confidence value="5">,</confidence>
114
+ and various embodiments of the controller <part-num-ref name="controller">120</part-num-ref>
115
+ will be described below with reference to FIGs. 2 through <part-num-ref name="through">8.</part-num-ref>
116
+ </p>
117
+ <p id="p-28" num="28">FIG. 2 is a flowchart illustrating a document information transmission method according to an embodiment of the present invention.</p>
118
+ <p id="p-29" num="29">Referring to FIG. 2, a predetermined application is already executed by the <boundary-data type="line-number">25 </boundary-data>
119
+ controller <part-num-ref name="controller">120</part-num-ref>
120
+ in the document information transmission apparatus <part-num-ref name="document information transmission apparatus">100.</part-num-ref>
121
+ Once a touch or click input is sensed on a document that is opened on the application, the sensed input is recognized as an information transmission command for transmitting document information to a target object in operation <part-num-ref name="target object in operation">210.</part-num-ref>
122
+ Herein, the document is not limited to a specific format, and may be in any format including one or more <boundary-data type="line-number">30 </boundary-data>
123
+ images, texts, and/or charts, and the term 'application' refers to software capable of showing the document. </p>
124
+ <p id="p-30" num="30">When the application is a web browser, a web page at a Uniform Resource Locator (URL) address requested by a user may be displayed by the web browser.</p>
125
+ <p id="p-31" num="31">When the user's touch or click input is sensed on the web page, it is recognized as <boundary-data type="header">
126
+ <confidence value="8">4</confidence>
127
+ </boundary-data>
128
+ <page-break num="5"/>
129
+ <boundary-data type="header">784-103 (S<confidence value="45">F-</confidence>
130
+ 37973-US-DMC) </boundary-data>
131
+ an information transmission command for transmitting information about the currently browsed web page to another object. The information about the web page may include the URL address, a title, and a favorite icon ("favicon<confidence value="5">"</confidence>
132
+ ) of the web page, content included in the web page, files forming the web page, and a keyword <boundary-data type="line-number">5 </boundary-data>
133
+ included in meta information. </p>
134
+ <p id="p-32" num="32">The event mode is classified into a normal mode and a transmission mode.</p>
135
+ <p id="p-33" num="33">Thus, in the normal mode, the touch or click input may be recognized as a normally used event such as a document edition command, a link selection command, a panning command, or a scroll command; whereas in the transmission mode, the <boundary-data type="line-number">10 </boundary-data>
136
+ touch or click input may be recognized as an information transmission command for fixing the document. Switching to the transmission mode may be performed by a specific input from the user. For example, when the user selects or opens a target object to which the document information is to be transmitted, or inputs a specific gesture, the event mode is switched to the transmission mode. When the <boundary-data type="line-number">15 </boundary-data>
137
+ document whose information is to be transmitted is a web page, the web page is not moved and is fixed in the transmission mode, even if there is a panning input from the user. </p>
138
+ <p id="p-34" num="34">Once a release input is sensed on the target object in succession to the touch or click input, the document information is transmitted to the target object in <boundary-data type="line-number">20 </boundary-data>
139
+ operation <part-num-ref name="target object in operation">220.</part-num-ref>
140
+ The information of the document information that is to be transmitted may be determined depending on the type of target object. For example, when the target object is a phone directory or a text message transmission application, document content may be transmitted in a text format through a text message to a selected phone number. When the target object is a clip board, a <boundary-data type="line-number">25 </boundary-data>
141
+ snap shot of the document is generated and stored in the clip board. The snap shot may be a screen capture of the document. When the target object is a document editor, document content are transmitted to be inserted into the document which is being edited by the document editor. When the target object is a folder, a file forming the document is transmitted to be stored in the folder. When the target <boundary-data type="line-number">30 </boundary-data>
142
+ object is a bookmark list, an address, a title, and/or a favicon of a web page, or other information for configuring a bookmark, the information is transmitted to and stored in the bookmark list. </p>
143
+ <boundary-data type="header">
144
+ <confidence value="8">5</confidence>
145
+ </boundary-data>
146
+ <boundary-data type="header">784-103 (SH-37973-US-DM<confidence value="66">C)</confidence>
147
+ </boundary-data>
148
+ <p id="p-35" num="35">
149
+ <page-break num="6"/>
150
+ FIGs. 3 through <part-num-ref name="through">6</part-num-ref>
151
+ are diagrams illustrating screens in which an address of a web page is transmitted directly to a bookmark bar, according to an embodiment of the present invention. </p>
152
+ <p id="p-36" num="36">Referring to FIG. 3, when a user opens a bookmark bar <part-num-ref name="bookmark bar">310</part-num-ref>
153
+ in a browser <boundary-data type="line-number">5 </boundary-data>
154
+ including information about a web page <part-num-ref name="web page">300</part-num-ref>
155
+ currently being browsed, an event mode is switched from the normal mode to the transmission mode, such that the web page <part-num-ref name="web page">300</part-num-ref>
156
+ is fixed. The bookmark bar <part-num-ref name="bookmark bar">310</part-num-ref>
157
+ stores favicons <part-num-ref name="stores favicons">311</part-num-ref>
158
+ and addresses <part-num-ref name="and addresses">312</part-num-ref>
159
+ of web pages previously stored by the user. When the web page <part-num-ref name="web page">300</part-num-ref>
160
+ is fixed, even if a link included in the web page <part-num-ref name="web page">300</part-num-ref>
161
+ is selected, the web page <part-num-ref name="web page">300</part-num-ref>
162
+ is not moved to another <boundary-data type="line-number">10 </boundary-data>
163
+ web page corresponding to the selected link, and even if there is a panning input, the web page <part-num-ref name="web page">300</part-num-ref>
164
+ is not moved. </p>
165
+ <p id="p-37" num="37">Referring to FIG. 4, upon generation of a touch input on the web page <part-num-ref name="web page">300,</part-num-ref>
166
+ it is recognized that the user desires to transmit information about the web page <part-num-ref name="web page">300.</part-num-ref>
167
+ </p>
168
+ <p id="p-38" num="38">At this time, a movable object <part-num-ref name="movable object">410</part-num-ref>
169
+ for temporarily storing the information about the <boundary-data type="line-number">
170
+ <confidence value="66">15</confidence>
171
+ </boundary-data>
172
+ web page <part-num-ref name="web page">300</part-num-ref>
173
+ is generated and displayed, and the movable object <part-num-ref name="movable object">410</part-num-ref>
174
+ includes a favicon <part-num-ref name="favicon">420</part-num-ref>
175
+ of the web page <part-num-ref name="web page">300</part-num-ref>
176
+ to indicate that the movable object <part-num-ref name="movable object">410</part-num-ref>
177
+ contains the information about the currently browsed web page <part-num-ref name="currently browsed web page">300.</part-num-ref>
178
+ Since the target object is the bookmark bar <part-num-ref name="bookmark bar">310<confidence value="5">,</confidence>
179
+ </part-num-ref>
180
+ the information to be transmitted is determined as the address and favicon <part-num-ref name="address and favicon">420</part-num-ref>
181
+ of the web page <part-num-ref name="web page">300.</part-num-ref>
182
+ </p>
183
+ <p id="p-39" num="39">
184
+ <boundary-data type="line-number">20 </boundary-data>
185
+ Referring to FIG. 5, the movable object <part-num-ref name="movable object">410</part-num-ref>
186
+ moves above the bookmark bar <part-num-ref name="bookmark bar">310</part-num-ref>
187
+ according to a move or drag input from the user. Referring to FIG. 6, the release input is sensed on the bookmark bar <part-num-ref name="bookmark bar">310,</part-num-ref>
188
+ that is, the target object, and the information about the web page <part-num-ref name="web page">300</part-num-ref>
189
+ of the movable object <part-num-ref name="movable object">410</part-num-ref>
190
+ is transmitted to the bookmark bar <part-num-ref name="bookmark bar">310.</part-num-ref>
191
+ The movable object <part-num-ref name="movable object">410</part-num-ref>
192
+ disappears from the screen, and finally <boundary-data type="line-number">25 </boundary-data>
193
+ a new bookmark item <part-num-ref name="new bookmark item">610</part-num-ref>
194
+ including the favicon <part-num-ref name="favicon">420</part-num-ref>
195
+ and an address <part-num-ref name="address">620</part-num-ref>
196
+ for the current web page <part-num-ref name="current web page">300</part-num-ref>
197
+ is added to the bookmark bar <part-num-ref name="bookmark bar">310.</part-num-ref>
198
+ </p>
199
+ <p id="p-40" num="40">FIG. 7 is a diagram illustrating a screen in which a snap shot of a web page is transmitted directly to a clipboard, according to an embodiment of the present invention.</p>
200
+ <p id="p-41" num="41">
201
+ <boundary-data type="line-number">30 </boundary-data>
202
+ Referring to FIG. 7, the target object is a clip board <part-num-ref name="clip board">720.</part-num-ref>
203
+ Once the user clicks a web page <part-num-ref name="web page">710,</part-num-ref>
204
+ a movable object <part-num-ref name="movable object">711</part-num-ref>
205
+ is generated to transmit information about the web page <part-num-ref name="web page">710,</part-num-ref>
206
+ and the movable object <part-num-ref name="movable object">711</part-num-ref>
207
+ is moved to the clip board <part-num-ref name="clip board">720</part-num-ref>
208
+ and then the release input is generated to drop the movable object <part-num-ref name="movable object">711</part-num-ref>
209
+ onto the clip <boundary-data type="header">
210
+ <confidence value="8">6</confidence>
211
+ </boundary-data>
212
+ <page-break num="7"/>
213
+ <boundary-data type="header">784<confidence value="5">-</confidence>
214
+ 103 (SH-37973-US-DMC) </boundary-data>
215
+ board <part-num-ref name="clip board">720,</part-num-ref>
216
+ whereby the snap shot of the web page <part-num-ref name="web page">710</part-num-ref>
217
+ is stored in the clip board <part-num-ref name="clip board">720.</part-num-ref>
218
+ </p>
219
+ <p id="p-42" num="42">Accordingly, the user can transmit information about a web page, such as an address of the web page, to another object only with a mouse click or touch input <boundary-data type="line-number">5 </boundary-data>
220
+ during web browsing without a keyboard input. </p>
221
+ <p id="p-43" num="43">FIG. 8 is a diagram illustrating a screen in which content of a text document is transmitted directly to a phone directory, according to an embodiment of the present invention.</p>
222
+ <p id="p-44" num="44">Referring to FIG. 8, an application, notepad <part-num-ref name="application, notepad">810,</part-num-ref>
223
+ is opened on a screen <part-num-ref name="screen">800.</part-num-ref>
224
+ </p>
225
+ <p id="p-45" num="45">
226
+ <boundary-data type="line-number">10 </boundary-data>
227
+ The user edits a text document by using notepad <part-num-ref name="text document by using notepad">810.</part-num-ref>
228
+ The user also selects and opens a friend list <part-num-ref name="friend list">830</part-num-ref>
229
+ which is similar to a phone directory. Once the user selects the friend list <part-num-ref name="friend list">830,</part-num-ref>
230
+ which is the target object, the event mode is switched from the normal mode to the transmission mode. Thus, when the touch or click input is generated on the opened text document, it is recognized as the information <boundary-data type="line-number">15 </boundary-data>
231
+ transmission command rather than as an event for editing the text document. In this state, information to be transmitted to the target object is determined as content of the text document, considering the type of the target object. In the transmission mode, once the touch or click input is sensed on the text document, a movable object <part-num-ref name="movable object">820</part-num-ref>
232
+ for temporarily storing the content of the text document is generated and <boundary-data type="line-number">20 </boundary-data>
233
+ displayed. When the user moves the object <part-num-ref name="object">820</part-num-ref>
234
+ to a friend item <part-num-ref name="friend item">840</part-num-ref>
235
+ of the friend list <part-num-ref name="friend list">830</part-num-ref>
236
+ and then generates the release input, the content of the text document are transmitted to the friend item <part-num-ref name="friend item">840.</part-num-ref>
237
+ As a result of the transmission, a text message transmission program is instructed to transmit the content of the text document to a phone number corresponding to the friend item <part-num-ref name="friend item">840.</part-num-ref>
238
+ </p>
239
+ <p id="p-46" num="46">
240
+ <boundary-data type="line-number">25 </boundary-data>
241
+ After generating and storing a text document, the user can immediately transmit content of the text document to a desired person merely with a mouse click or touch input, without having to open a text message transmission menu and select the stored text document. </p>
242
+ <p id="p-47" num="47">While the present invention has been shown and described with reference to <boundary-data type="line-number">30 </boundary-data>
243
+ embodiments thereof, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein. Accordingly, the spirit of the present invention may be understood by the following claims, and equal or equivalent modifications thereof fall within the scope of the spirit of the present invention. In addition, a system according to the present invention can be <boundary-data type="header">
244
+ <confidence value="8">7</confidence>
245
+ </boundary-data>
246
+ <page-break num="8"/>
247
+ <boundary-data type="header">784-103 (SH-37973-US-DMC)</boundary-data>
248
+ embodied as a computer-readable code on a computer-readable recording medium. </p>
249
+ <p id="p-48" num="48">The recording medium may be any kind of recording device storing data that is readable by a computer. Examples of the recording medium include Read-Only Memory (R<confidence value="5">O</confidence>
250
+ M), Random Access Memory (RAM), C<confidence value="5">D</confidence>
251
+ -ROMs, magnetic tapes, floppy <boundary-data type="line-number">5 </boundary-data>
252
+ disks, and optical data storage devices. The computer-readable recording medium can also be distributed over a network of coupled computer systems so that the computer-readable code is stored and executed in a decentralized fashion. </p>
253
+ <boundary-data type="header">
254
+ <confidence value="8">8</confidence>
255
+ </boundary-data>
256
+ </description>
257
+ </us-patent-application>
258
+
applicant/15171192.xml ADDED
@@ -0,0 +1,2 @@
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?><uspat:SpecificationDocument xmlns:uscom="urn:us:gov:doc:uspto:common" xmlns:uspat="urn:us:gov:doc:uspto:patent" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:com="http://www.wipo.int/standards/XMLSchema/ST96/Common" xmlns:pat="http://www.wipo.int/standards/XMLSchema/ST96/Patent" uscom:vendorName="VASTEC" uscom:createDateTime="2018-10-12T21:19:07Z" com:st96Version="V2_1" com:ipoVersion="US_V7_1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent Patent/V7_1/Schema/USPatent/Document/SpecificationDocument_V7_1.xsd" com:documentFileName="15171192.10-12-2018.JN6HOH98RXEAPX1.SPEC.XML" com:id="JN6HOH98RXEAPX1">
2
+ <uspat:DocumentMetadata com:id="ID0000001"><uscom:DocumentCode>SPEC</uscom:DocumentCode><uscom:ApplicationNumberText uscom:electronicText="15171192">15171192</uscom:ApplicationNumberText><com:PageTotalQuantity>1</com:PageTotalQuantity><uscom:ParagraphTotalQuantity>6</uscom:ParagraphTotalQuantity><uscom:OfficialDate>2018-10-12</uscom:OfficialDate></uspat:DocumentMetadata><?PageStart number='1'?><uscom:P com:pNumber="1" com:id="p-1">27753-50002US App. No.: 15/171,192</uscom:P><uscom:Heading com:id="h-1">AMENDMENTS TO THE SPECIFICATION</uscom:Heading><uscom:P com:pNumber="2" com:id="p-2">Please amend the title as follows:</uscom:P><uscom:P com:pNumber="3" com:id="p-3">Device, method, and graphical user interface for manipulating application windows <com:U>of virtual desktops</com:U></uscom:P><uscom:P com:pNumber="4" com:id="p-4">Please add the following paragraphs following the title.</uscom:P><uscom:Heading com:id="h-2">CROSS-REFERENCE TO RELATED APPLICATIONS</uscom:Heading><uscom:P com:pNumber="5" com:id="p-5" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">This application claims priority to U.S. Provisional Patent App. No. 62/172,160, filed on June 7, 2015.</uscom:P><uscom:P com:pNumber="6" com:id="p-6"><uscom:PartName com:idrefs="PN-00001">Amendment </uscom:PartName><uscom:PartNumber com:id="PN-00001">2</uscom:PartNumber></uscom:P></uspat:SpecificationDocument>
prior_art/09780035.xml ADDED
The diff for this file is too large to render. See raw diff
 
prior_art/10522933.xml ADDED
@@ -0,0 +1,22 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>10522933</doc-number>
8
+ <date>2008-06-10</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <p id="p-1" num="1">Atty's 23158 Pat. App. 10/522,933 </p>
14
+ <heading id="h-1">SPECIFICATION AMENDMENTS</heading>
15
+ <p id="p-2" num="2">Please replace the specification on file with the clean version of the specification attached hereto. Also attached is a marked version of the specification showing with underlining, strikeout, and/or bracketing the changes embodied in the clean version. No new matter whatsoever has been added.</p>
16
+ <p id="p-3" num="3">
17
+ <confidence value="8">-</confidence>
18
+ <confidence value="8">2</confidence>
19
+ - 23158AM2.WPD </p>
20
+ </description>
21
+ </us-patent-application>
22
+
prior_art/10545100.xml ADDED
@@ -0,0 +1,15 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <pat:SpecificationDocument xmlns:pat="urn:us:gov:doc:uspto:patent" xmlns="urn:us:gov:doc:uspto:patent" xmlns:ent="urn:us:gov:doc:uspto:enterprise" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:tbl="http://www.oasis-open.org/tables/exchange/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:com="http://www.wipo.int/standards/XMLSchema/Common/1" pat:instanceFileName="10545100.04-06-2015.I86I1F2XPXXIFW3.SPEC.xml" pat:id="I86I1F2XPXXIFW3" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XMLSchema/V1_3/SpecificationDocument_1_0.xsd">
3
+ <pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001">
4
+ <pat:ApplicationHeaderDetails><pat:ApplicationNumber>10545100</pat:ApplicationNumber></pat:ApplicationHeaderDetails>
5
+ <pat:PageTotalQuantity>1</pat:PageTotalQuantity>
6
+ <pat:ParagraphTotalQuantity>3</pat:ParagraphTotalQuantity>
7
+ </pat:DocumentHeaderDetails>
8
+ <pat:MailRoomDate>2015-04-06</pat:MailRoomDate>
9
+ <pat:Specification pat:id="Specification">
10
+ <?PageStart number="1"?>
11
+ <pat:P pat:id="p-1" pat:pNumber="1">Serial No. 10/545,100 Amendments to the S<pat:OCRConfidenceData pat:levelNumber="5">p</pat:OCRConfidenceData>ecification:</pat:P>
12
+ <pat:P pat:id="p-2" pat:pNumber="2">Please amend paragraph <pat:OCRConfidenceData pat:levelNumber="66">[0</pat:OCRConfidenceData>001] as follows:</pat:P>
13
+ <pat:P pat:id="p-3" pat:pNumber="3"><pat:OCRConfidenceData pat:levelNumber="5">[</pat:OCRConfidenceData>0001<pat:OCRConfidenceData pat:levelNumber="5">]</pat:OCRConfidenceData> This application is a <pat:PartName pat:idref="PN-00001">national phase entry under </pat:PartName><pat:PartNumber pat:id="PN-00001">35</pat:PartNumber> <pat:PartName pat:idref="PN-00002">U.S.C. <pat:OCRConfidenceData pat:levelNumber="5">§</pat:OCRConfidenceData> </pat:PartName><pat:PartNumber pat:id="PN-00002">371</pat:PartNumber> of International Patent Application PCT/US2004/003852, filed February 11, 2004, published in English as International Patent Publication No. WO 2004/072259 on August 26, 2004, which claims prior<pat:OCRConfidenceData pat:levelNumber="65">it</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="85">to</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="6">.</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="666666">Patent</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="855">App</pat:OCRConfidenceData>lication No. 60/446<pat:OCRConfidenceData pat:levelNumber="6668">,429</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="4">f</pat:OCRConfidenceData>iled <pat:OCRConfidenceData pat:levelNumber="24">Fe</pat:OCRConfidenceData>bru<pat:OCRConfidenceData pat:levelNumber="248">ary</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="555">11.</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="6">2</pat:OCRConfidenceData>003<pat:OCRConfidenceData pat:levelNumber="5">,</pat:OCRConfidenceData> the entire contents of which is hereby incorporated herein by this reference.</pat:P>
14
+ <pat:Heading pat:id="h-1"><pat:OCRConfidenceData pat:levelNumber="8">2</pat:OCRConfidenceData></pat:Heading>
15
+ </pat:Specification></pat:SpecificationDocument>
prior_art/10546583.xml ADDED
@@ -0,0 +1,78 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>10546583</doc-number>
8
+ <date>2009-02-24</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <heading id="h-1">IN THE SPECIFICATION</heading>
14
+ <p id="p-1" num="1">Page 4, lines 1-16, please amend as follows:</p>
15
+ <p id="p-2" num="2">DE-A<confidence value="4">1</confidence>
16
+ -101 49 <part-num-ref name="">148</part-num-ref>
17
+ describes aqueous coating compositions based on organic film- <confidence value="5885">form</confidence>
18
+ ing agent, fine inorganic particles and lubricant or/and organic corrosion inhibitor, which, in spite of the absence of chromium compounds, produced outstanding results of corrosion resistance, adhesive strength and shapability, inter alia on Ga<confidence value="422515">l-vah+</confidence>
19
+ <confidence value="12">°4</confidence>
20
+ GALVALUME<confidence value="2">*</confidence>
21
+ (55<confidence value="5">%</confidence>
22
+ Aluminum-Zinc alloy coating sheet and strips <confidence value="222222">eeated</confidence>
23
+ <confidence value="88">sh</confidence>
24
+ eet <confidence value="655515">steel}</confidence>
25
+ steel sheets, but nevertheless still showed an inadequate corrosion resistance of an organic film of about <part-num-ref name="organic film of about">1</part-num-ref>
26
+ <confidence value="25">[m</confidence>
27
+ layer thickness on hot-galvanized, electrolytically galvanized, <confidence value="684885644222154">Galvalume@-coa4</confidence>
28
+ ed GALVALUME<confidence value="2">@</confidence>
29
+ -coated or <confidence value="8858552266">Galfan@-ee</confidence>
30
+ ate<confidence value="5">d</confidence>
31
+ GALFAN<confidence value="2">*</confidence>
32
+ (alloy coating containing 95<confidence value="5">%</confidence>
33
+ zin<confidence value="8">c</confidence>
34
+ , 5<confidence value="5">%</confidence>
35
+ aluminum and specific quantities of rare earth metals products)-coated metallic strips, that is to say on metallic surfaces which are difficult to protect against corrosion. The compositions, their constituents and the properties of the raw materials and coatings of this publication are expressly included in this Application. </p>
36
+ <p id="p-3" num="3">Page 46, lines 4-21, please amend as follows:</p>
37
+ <p id="p-4" num="4">It is easily possible here to employ the polymeric, optionally chromate-free coating according to the invention without prior application of an additional pretreatment layer, so that an outstanding permanent protection of the metallic surfaces, and in particular on A<confidence value="4">l</confidence>
38
+ Si, ZnAl, such as <confidence value="22442">Gafn@</confidence>
39
+ GALFA<confidence value="52">N*</confidence>
40
+ , AlZn, such as Ga<confidence value="561555282">lveal+me@</confidence>
41
+ GALVALUME<confidence value="14">R'</confidence>
42
+ , ZnFe, Z<confidence value="5">n</confidence>
43
+ Ni, such as <confidence value="22222222222">Galvanaeia@</confidence>
44
+ GALVANNEAL<confidence value="2">*</confidence>
45
+ and other Zn alloys as metallic coatings or Al and Zn coatings, is possible, which can be achieved by application of a polymer-containing coating. Moreover, the coating according to the invention has also proved particularly suitable for metallic surfaces which are highly susceptible to corrosion, such as those of iron and steel alloys, in particular on <boundary-data type="header">
46
+ <confidence value="68888">60168</confidence>
47
+ 488 <confidence value="4">1</confidence>
48
+ <confidence value="8">2</confidence>
49
+ </boundary-data>
50
+ <page-break num="2"/>
51
+ cold-rolled steel, it then being advantageous to add at least one corrosion inhibitor to the aqueous composition. Flash rust formation during drying of the treatment liquid on cold-rolled steel (CRS) can be suppressed by this means. </p>
52
+ <p id="p-5" num="5">Page 47, lines 7-15, please amend as follows:</p>
53
+ <p id="p-6" num="6">The polymeric and largely or completely chromate-free coating ac<confidence value="8">c</confidence>
54
+ ording to the invention furthermore has the advantage that especially at a layer thickness in the range from 0.5 to <part-num-ref name="range from 0.5 to">3</part-num-ref>
55
+ <confidence value="2185">ptm-</confidence>
56
+ it is transparent and light-coloured, so that the metallic character and the typical structure e.g. of a galvanized or a Ga<confidence value="56141155">lvlawne@</confidence>
57
+ GALVALU<confidence value="66">ME</confidence>
58
+ <confidence value="1">"</confidence>
59
+ surface can still be seen accurately and unchanged or virtually unchanged through the coating. Furthermore, such thin coatings can also be welded without problems. </p>
60
+ <p id="p-7" num="7">Page 50, lines 9-21, please amend as follows:</p>
61
+ <p id="p-8" num="8">For preparation of aqueous concentrates, at least one partly hydrolysed silane was aged for at least two weeks and optionally also thereby hydrolyzed <confidence value="565466142">hyde-ysed</confidence>
62
+ . Thereafter, a metal chelate according to table <part-num-ref name="metal chelate according to table">1</part-num-ref>
63
+ was added. The concentrates were then diluted with water, and an agent which adapts the pH, such as ammonia, was optionally added in order to obtain ready-to- use treatment liquids. In each case <part-num-ref name="pH, such as ammonia, was optionally added in order to obtain ready-to- use treatment liquids. In each case">3</part-num-ref>
64
+ metal sheets of hot-galvanized steel or of Ga<confidence value="5">l</confidence>
65
+ <confidence value="411182">a1ane@</confidence>
66
+ GALVALUME<confidence value="225">""'</confidence>
67
+ steel sheet were then brought into contact by rolling on and drying on the corresponding treatment liquid at 25<confidence value="1">°</confidence>
68
+ C. The metal sheets treated in this way were dried here at <part-num-ref name="metal sheets treated in this way were dried here at">
69
+ <confidence value="85">90</confidence>
70
+ </part-num-ref>
71
+ C. PMT and then tested for their corrosion protection. </p>
72
+ <boundary-data type="header">
73
+ <confidence value="722">601</confidence>
74
+ <confidence value="1">I</confidence>
75
+ 68488.1 3 </boundary-data>
76
+ </description>
77
+ </us-patent-application>
78
+
prior_art/10553926.xml ADDED
The diff for this file is too large to render. See raw diff
 
prior_art/10577294.xml ADDED
@@ -0,0 +1,31 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>10577294</doc-number>
8
+ <date>2006-04-29</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <p id="p-1" num="1">EXPRESS MAIL LABEL NO. EL 977021505 U<confidence value="5">S</confidence>
14
+ PU<confidence value="585885">030110</confidence>
15
+ Customer No. <part-num-ref name="US PU030110 Customer No.">24498</part-num-ref>
16
+ Amendments to the Specification Please add the following new paragraph at page <part-num-ref name="following new paragraph at page">1,</part-num-ref>
17
+ line 3: </p>
18
+ <p id="p-2" num="2">This application claims the benefit, under <part-num-ref name="benefit, under">35</part-num-ref>
19
+ U.S.C. <confidence value="6">§</confidence>
20
+ <part-num-ref name="U.S.C. §">365</part-num-ref>
21
+ of International Application PCT/US2003/035492, filed November <part-num-ref name="of International Application PCT/US2003/035492, filed November">5,</part-num-ref>
22
+ <part-num-ref name="of International Application PCT/US2003/035492, filed November 5,">2003</part-num-ref>
23
+ which was published in accordance with PCT Article 21(2) on May <part-num-ref name="which was published in accordance with PCT Article 21(2) on May">26,</part-num-ref>
24
+ <part-num-ref name="which was published in accordance with PCT Article 21(2) on May 26,">2005</part-num-ref>
25
+ in English. </p>
26
+ <p id="p-3" num="3">
27
+ <confidence value="8">2</confidence>
28
+ </p>
29
+ </description>
30
+ </us-patent-application>
31
+
prior_art/10581087.xml ADDED
The diff for this file is too large to render. See raw diff
 
prior_art/10592554.xml ADDED
The diff for this file is too large to render. See raw diff
 
prior_art/10597291.xml ADDED
@@ -0,0 +1,335 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>10597291</doc-number>
8
+ <date>2006-07-19</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <boundary-data type="header">WO 2005/077447 PCT/AU200<confidence value="68555">5/000</confidence>
14
+ 174 </boundary-data>
15
+ <heading id="h-1">SESSION-BY-SESSION ADJUSTMENT OF A DEVICE FOR TREATING SLEEP</heading>
16
+ <heading id="h-2">DISORDERED BREATHING</heading>
17
+ <p id="p-1" num="1">Field of the Invention <confidence value="666666">[0001]</confidence>
18
+ This application claims the benefit of United States provisional application No. </p>
19
+ <p id="p-2" num="2">60/543,491 filed on February 11, 2004. The invention relates to devices for treatment of sleep disordered breathing (S<confidence value="5">D</confidence>
20
+ B). More specifically, the invention relates to a device for detecting S<confidence value="5">D</confidence>
21
+ B events in the presence of a continuous positive airway pressure and determining an appropriate adjustment to the airway pressure in response to detected <confidence value="86">SD</confidence>
22
+ B events. </p>
23
+ <p id="p-3" num="3">Background of the Invention [0002] The present invention relates to the diagnosis and treatment of partial or complete upper airway occlusion, a condition in which the upper airway collapses, particularly under the reduced pressure generated by inhalation. This is most likely to happen during unconsciousness, sleep or anesthesia.</p>
24
+ <p id="p-4" num="4">[0003] A particular application of the present invention is to the diagnosis and/or treatment of snoring and sleep apnea. Sleep apnea is characterized by complete occlusion of the upper airway passage during sleep while snoring is characterized by partial occlusion. An obstructive sleep apnea sufferer repeatedly chokes on their tongue and soft palate throughout an entire sleep period, resulting in lowered arterial blood oxygen levels and poor quality of sleep. It should be realized that although the following specification discusses sleep apnea in detail, the present invention also applies to the diagnosis and treatment of other forms of upper airway disorders.</p>
25
+ <p id="p-5" num="5">[0004] The application of continuous positive airway pressure (<confidence value="5">C</confidence>
26
+ PAP) has been used as a means of treating the occurrence of obstructive sleep apnea. The patient is connected to a positive pressure air supply by means of a mouth and nose mask, nose mask only or nasal prongs. The air supply breathed by the patient is at all times at <boundary-data type="header">
27
+ <confidence value="888">-1-</confidence>
28
+ </boundary-data>
29
+ <page-break num="2"/>
30
+ <boundary-data type="header">WO 2005/077447 PC<confidence value="668">T/A</confidence>
31
+ U2005/00<confidence value="55">01</confidence>
32
+ <confidence value="88">74</confidence>
33
+ </boundary-data>
34
+ slightly greater than atmospheric pressure. For example, therapuetic pressures will typically be within the range of <part-num-ref name="range of">4</part-num-ref>
35
+ cmH2<confidence value="4">0</confidence>
36
+ to <part-num-ref name="cmH20 to">20</part-num-ref>
37
+ cmH2<confidence value="4">O</confidence>
38
+ . It has been found that the application of continuous positive airway pressure (CPAP) provides what can be described as a "pneumatic splint", supporting and stabilizing the upper airway and thus eliminating the occurrence of upper airway occlusions. It is effective in eliminating both snoring and obstructive sleep apnea, and in many cases is effective in treating central and mixed apnea. </p>
39
+ <p id="p-6" num="6">[0005] The airway pressure required for effective CPAP therapy differs from patient to patient. In order to discover the airway pressure which is most effective for a particular individual, the practice has been for the patient to undergo two sleep studies at an appropriate observation facility such as a hospital, clinic or laboratory. The first night is spent observing the patient in sleep and recording selected parameters such as oxygen saturation, chest wall and abdominal movement, air flow, expired <confidence value="585">CO2</confidence>
40
+ , E<confidence value="588">CG,</confidence>
41
+ EEG, EMG and eye movement. This information can be interpreted to diagnose the nature of the sleep disorder and confirm the presence or absence of apnea and, where present, the frequency and duration of apneic episodes and extent and duration of associated oxygen desaturation. Apneas can be identified as obstructive, central or mixed. The second night is spent with the patient undergoing nasal <confidence value="5">C</confidence>
42
+ PAP therapy. </p>
43
+ <p id="p-7" num="7">When apnea is observed, the <confidence value="5">C</confidence>
44
+ PAP setting is increased to prevent apneas. The pressure setting at the end of the sleep period, i.e., the maximum used, is deemed to be the appropriate setting for that patient. </p>
45
+ <p id="p-8" num="8">[0006<confidence value="5">]</confidence>
46
+ For a given patient in a given physical condition, various stages of sleep will require different minimum pressures to prevent occlusions. Furthermore, these various pressures will, in fact, vary from day to day depending upon the patient's physical condition, for example, nasal congestion, general tiredness, and effects of drugs such as alcohol, as well as the patient's sleeping posture. Thus the appropriate pressure found in the laboratory is necessarily the maximum of all these minimum pressures for that particular night and is not necessarily the ideal pressure for all occasions nor for every night. It will generally be higher than necessary for most of the night. </p>
47
+ <boundary-data type="header">
48
+ <confidence value="888">-2-</confidence>
49
+ </boundary-data>
50
+ <boundary-data type="header">WO 2005/077447 PCT/A<confidence value="5">U</confidence>
51
+ 2005/0001<confidence value="88">74</confidence>
52
+ </boundary-data>
53
+ <p id="p-9" num="9">
54
+ <page-break num="3"/>
55
+ [0007] Also, a patient must be able to operate a CPAP system to deliver appropriate airway pressure at home where their general physical condition or state of health may be quite different from that in the sleep clinic, and will certainly vary from day to day. The patient's physical condition often improves due to CPAP therapy. It is often the case that after a period of therapy the necessary airway pressure can be reduced by some amount while still preventing the occurrence of obstructive sleep apnea. </p>
56
+ <p id="p-10" num="10">[0008] The long term effects of <confidence value="5">C</confidence>
57
+ PAP therapy are unknown so it is desirable to keep the airway pressure as low as practicable, particularly if a patient requires long term treatment. Lower airway pressures also result in a lower face mask pressure which is generally more comfortable for the patient. It has been found that <confidence value="5">C</confidence>
58
+ PAP induces patients to swallow and this inducement to swallow can be reduced by lowering the airway pressure. Thus it is desirable to use the lowest practicable airway pressure that is effective in preventing airway occlusion during CPAP therapy for the comfort and possibly the long term safety of the patient. Also, a lower airway pressure requires less energy consumption and a less complex and therefore less expensive apparatus, which is also generally quieter. </p>
59
+ <p id="p-11" num="11">[0009] Low airway pressures are also desirable before and during the early stage of each sleep period as the increased comfort of an initially lower airway pressure allows the patient to more easily fall asleep. When a patient undergoing <confidence value="5">C</confidence>
60
+ PAP opens their mouth with pressurized air being forced through the nose, the pressured air exits out of the mouth producing an unpleasant sensation. This can occur when the patient puts on the mask connected to the pressured air supply before falling asleep and some patients will therefore leave the mask off for as long as <confidence value="5">.</confidence>
61
+ possible and may in fact fall asleep without wearing the mask and therefore without the benefits of the <confidence value="5">C</confidence>
62
+ PAP therapy. </p>
63
+ <p id="p-12" num="12">[0010] In addition to the problems associated with administering <confidence value="5">C</confidence>
64
+ PAP therapy there exists the inconvenience and cost of diagnosis which may be undertaken by overnight observation at a sleep clinic or the like. Hence a simple means whereby a patient's apnea problem can be diagnosed at home without supervision is clearly desirable as <boundary-data type="header">
65
+ <confidence value="888">-3-</confidence>
66
+ </boundary-data>
67
+ <page-break num="4"/>
68
+ <boundary-data type="header">WO 2005/077447 PCT/A<confidence value="588588666">U2005/000</confidence>
69
+ 174 </boundary-data>
70
+ well as a <confidence value="5">C</confidence>
71
+ PAP device which will deliver a continuously minimum appropriate pressure for substantially the entire period of therapy. </p>
72
+ <p id="p-13" num="13">[0011] Although diagnosis in a sleep clinic as outlined above is beneficial, it has some deficiencies. A patient is likely not to sleep in a fully relaxed state in an unfamiliar environment and a single night is insufficient to obtain a pressure setting that will be optimal in the long run. Thus home therapy at the pressure setting arrived at in this way is likely to be less than 100% effective on some occasions and higher than necessary for a substantial portion of the time. The cost and inconvenience of a sleep study in a hospital setting are to be avoided if possible.</p>
73
+ <p id="p-14" num="14">[0012] A skilled physician can usually recognize the symptoms of sleep apnea from questioning and examining a patient. Where no other indications are present there is very little risk in attempting nasal <confidence value="5">C</confidence>
74
+ PAP therapy without further testing as the treatment is fail safe and non-invasive. However, a very useful intermediate step would be to analyze the pattern of respiratory waveforms (e.g., pressure, flow or sound) over one or more full nights of sleep. Interpretation of these patterns together with questioning and examination will, in many cases, provide sufficient confirmation of apnea to prescribe nasal CPAP therapy. If nasal <confidence value="5">C</confidence>
75
+ PAP eliminates the symptoms of day time sleepiness (as assessed by the patient) and of apneic snoring patterns (as assessed by analysis of recorded respiratory sounds while on nasal <confidence value="5">C</confidence>
76
+ PAP), the treatment can be continued. </p>
77
+ <p id="p-15" num="15">Further check-ups can be conducted at intervals recommended by the physician.</p>
78
+ <p id="p-16" num="16">[0013] In the most general form of a <confidence value="5">C</confidence>
79
+ PAP treatment device, the intermediate step before the device attempts <confidence value="5">C</confidence>
80
+ PAP pressure increases is to analyze the patterns of the respiratory parameters that can be obtained from sensors, such as a pressure sensor or flow sensor. As those skilled in the art will recognize, these parameters include, in addition to acoustic rate of breathing, inhaled/exhaled air volume and inhaled/exhaled air flow rate, and provide comprehensive information for the physician to assess the patient's condition. This additional information, for example, generated by a pressure transducer, is available at additional cost and complexity. Similar information related to <boundary-data type="header">
81
+ <confidence value="888">-4-</confidence>
82
+ </boundary-data>
83
+ <page-break num="5"/>
84
+ <boundary-data type="header">WO 2005/077447 PCT<confidence value="6814">/AIJ</confidence>
85
+ 2005/000174 </boundary-data>
86
+ airflow may be estimated from the speed of or current supplied to the blower of the apparatus that is supplying the pressure to the mask in a system where pressure changes are generated by changing the speed of the blower. Examples of such an implementation are disclosed in commonly owned U.S. Patent Nos. 5,740,795, 6,332,463 and 6,237,593, the disclosures of which are hereby incorporated by reference. </p>
87
+ <p id="p-17" num="17">[0014] The measurement of other parameters would provide further information to assist diagnoses, and the acoustic and/or other respiratory recordings described above can readily be used in conjunction with other monitors such as ECG and/or pulse oximetry. Suitable monitors are available to measure both these parameters in the home. The correlation between reduced oxygen saturation and apnea is sufficiently well established to infer oxygen desaturation from the confirmation of an apneic event.</p>
88
+ <p id="p-18" num="18">[0015] One index determined from these parameters is the Apnea Hypopnea Index.</p>
89
+ <p id="p-19" num="19">The Apnea Hypopnea Index ("AHI") is an indicator of severity of a patient's sleep disordered breathing. The AH<confidence value="4">I</confidence>
90
+ is determined by adding the total number of apneas and hypopneas the patient experienced over a particular time period, such as during a sleep clinic study. Various forms of AHI index are known by those skilled in the art. </p>
91
+ <p id="p-20" num="20">[0016] However, in automated devices, sophisticated sensors and associated algorithms for detecting S<confidence value="5">D</confidence>
92
+ B events and determining an appropriate response to the detected events add a level of complexity to the device that may increase the cost, potentially making them too expensive for some patients. Thus there is a need for a device that can accurately adjust the therapeutic pressures in response to SDB events to alleviate the events but utilizing minimum hardware and minimized methodology for controlling the hardware. </p>
93
+ <boundary-data type="header">
94
+ <confidence value="888">-5-</confidence>
95
+ </boundary-data>
96
+ <boundary-data type="header">WO 2005/077447 P<confidence value="666815">CT/A1U</confidence>
97
+ 2005/000<confidence value="588">174</confidence>
98
+ </boundary-data>
99
+ <p id="p-21" num="21">
100
+ <page-break num="6"/>
101
+ Ob<confidence value="8">j</confidence>
102
+ ects and Summary of the Invention [0017] It is an objective of the invention to provide a device that can detect SDB events and automatically and effectively determine an appropriate pressure response. </p>
103
+ <p id="p-22" num="22">[0018] It is an objective of the invention to provide such a device that minimizes the pressure treatment but assures the provision of a minimum level of support necessary to treat the patient.</p>
104
+ <p id="p-23" num="23">[0019] It is still a further objective to provide such a device with minimal components to ensure that it is inexpensive and cost-effective to develop and manufacture.</p>
105
+ <p id="p-24" num="24">[0020] The invention is a device for detecting <confidence value="5">S</confidence>
106
+ DB events and adjusting pressure to prevent such events on a session-by-session <confidence value="8">b</confidence>
107
+ asis, such as night by night, rather than on a breath-by-breath basis. In the device, in a first session while providing a level of treatment pressure, an indicator of severity of S<confidence value="5">D</confidence>
108
+ B events is detected. For example, in the first session the device detects and records a total number of apneas and hypopneas. Preferably, the detection of such events does not result in a change to the treatment pressure during that session. In a subsequent session, the treatment pressure is adjusted based on what the device learned during the previous session. </p>
109
+ <p id="p-25" num="25">Thus, the historic S<confidence value="5">D</confidence>
110
+ B index from the previous session is compared to a threshold in a current session and the treatment pressure is currently adjusted based on the historic index. In other words, pressure changes in subsequent sessions may increase or decrease depending on the nature of the historic S<confidence value="5">D</confidence>
111
+ B indicator. For example, if the prior night's AHI is greater than a threshold of <part-num-ref name="threshold of">8,</part-num-ref>
112
+ the pressure is automatically increased for use during the new session. If the pressure is less than <part-num-ref name="pressure is less than">8,</part-num-ref>
113
+ the pressure may decrease or stay the same. In one embodiment, patterns in changes over several prior sessions, such as consecutive nights, are analyzed to automatically determine a pressure setting in a current session. For example, if the AH<confidence value="5">I</confidence>
114
+ is <part-num-ref name="AHI is">0</part-num-ref>
115
+ for two consecutive nights, the pressure may be reduced for or in the next night's treatment. </p>
116
+ <boundary-data type="header">
117
+ <confidence value="888">-6-</confidence>
118
+ </boundary-data>
119
+ <boundary-data type="header">WO 200<confidence value="5">5</confidence>
120
+ /077447 PCT/A<confidence value="5">U</confidence>
121
+ 200<confidence value="88888688">5/000174</confidence>
122
+ </boundary-data>
123
+ <p id="p-26" num="26">
124
+ <page-break num="7"/>
125
+ [0021<confidence value="5">]</confidence>
126
+ In the preferred embodiment of the invention, an AHI index is determined from a flow signal which is preferably calculated from speed of the blower or current to the blower without use of a differential pressure transducer type flow sensor. Similarly, it is preferred that no pressure sensor be used in the setting of the pressure in the mask. </p>
127
+ <p id="p-27" num="27">Such a configuration assists in meeting the objectives as previously described. Further aspects of the invention are described in more detail herein.</p>
128
+ <p id="p-28" num="28">Brief Description of the Fi<confidence value="5">g</confidence>
129
+ ures [0022] To satisfy the recited objectives, a description of the invention is provided with reference to appended drawings that depict typical embodiments of the invention and are not intended to limit the scope of the invention, in which: </p>
130
+ <p id="p-29" num="29">[0023] FIG. 1 depicts the structure of an embodiment of a pressure treatment apparatus suitable for implementing the methods of the current invention<confidence value="5">;</confidence>
131
+ </p>
132
+ <p id="p-30" num="30">[0024<confidence value="5">]</confidence>
133
+ FIG. 2 is a flow chart of steps in a methodology for the control of a pressure treatment apparatus for making pressure adjustments during a treatment session based on apnea/hypopnea (AHI) indices taken from an earlier treatment session<confidence value="5">;</confidence>
134
+ </p>
135
+ <p id="p-31" num="31">[0025] FIG. 3 is a more detailed flow chart of steps in a methodology for the control of a pressure treatment apparatus to determine an AHI during a treatment session; and [0026] FIG. 4 is a more detailed flow chart of steps in a methodology for the control of the adjustment of pressure treatment in a subsequent session based upon an AHI taken during a prior treatment session.</p>
136
+ <boundary-data type="header">
137
+ <confidence value="888">-7-</confidence>
138
+ </boundary-data>
139
+ <boundary-data type="header">WO 2005/077447 PCT<confidence value="6815">/AIU</confidence>
140
+ 2005/0001<confidence value="86">74</confidence>
141
+ </boundary-data>
142
+ <p id="p-32" num="32">
143
+ <page-break num="8"/>
144
+ Description of the Invention [0027] In reference to FIG. 1, mask flow is measured using a flow sensor 4f and/or pressure sensor 4p with a pneumotachograph and differential pressure transducer or similar device. A flow signal F(t) is derived and mask pressure is measured at a pressure tap using a pressure transducer to derive a pressure signal Pmask(t). The pressure sensor 4p and flow sensor 4f have only been shown symbolically in FIG. 1 since those skilled in the art would understand how to measure flow and pressure. Flow F(t) and pressure Pmask(t) signals are sent to a controller or microprocessor <part-num-ref name="controller or microprocessor">6</part-num-ref>
145
+ which then determines how to adjust the blower. Alternatively, it is preferred that a flow signal f(t) and pressure signal Pmask(t) be estimated or calculated in relation to the blower motor by monitoring power supplied to the motor and/or the speed of the motor as disclosed in U.S. Patent Nos. 5,740,795, 6,332,463 or 6,237,593, without the provision of flow and pressure sensors as described above. </p>
146
+ <p id="p-33" num="33">[0028] The controller <part-num-ref name="controller">6</part-num-ref>
147
+ is configured and adapted to implement the methodology described in more detail herein and may include integrated chips, a memory and/or other instruction or data storage medium. For example, programmed instructions with the control methodology may be coded on integrated chips in the memory of the device (e.g., firmware) or loaded as software. </p>
148
+ <p id="p-34" num="34">[0029<confidence value="5">]</confidence>
149
+ The pressure delivery device includes a blower <part-num-ref name="blower">8,</part-num-ref>
150
+ which preferably is an impellor. The impellor <part-num-ref name="impellor">8</part-num-ref>
151
+ is controlled by a servo <part-num-ref name="servo">10,</part-num-ref>
152
+ receives ambient air through an inlet <part-num-ref name="inlet">12</part-num-ref>
153
+ and delivers pressurized air through an outlet <part-num-ref name="outlet">14</part-num-ref>
154
+ defined by an air delivery conduit <part-num-ref name="air delivery conduit">16</part-num-ref>
155
+ and a mask <part-num-ref name="mask">18</part-num-ref>
156
+ with an integrated exhaust vent <part-num-ref name="integrated exhaust vent">20.</part-num-ref>
157
+ The impellor, motor, and controller assembly define a blower assembly and are located within the blower housing <part-num-ref name="blower housing">22.</part-num-ref>
158
+ </p>
159
+ <p id="p-35" num="35">Various switches 24 and displays <part-num-ref name="and displays">26</part-num-ref>
160
+ are provided in the blower housing. A number of sensors are provided within the blower to monitor, among other things, snore <part-num-ref name="blower to monitor, among other things, snore">28,</part-num-ref>
161
+ motor speed <part-num-ref name="blower to monitor, among other things, snore 28, motor speed">30,</part-num-ref>
162
+ and motor current <part-num-ref name="blower to monitor, among other things, snore 28, motor speed 30, and motor current">32.</part-num-ref>
163
+ Various devices known in the art can serve as these types of sensors. A communication interface <part-num-ref name="communication interface">34</part-num-ref>
164
+ allows data to be transferred between the apparatus and an external device, such as a computer or controller. </p>
165
+ <boundary-data type="header">
166
+ <confidence value="888">-8-</confidence>
167
+ </boundary-data>
168
+ <boundary-data type="header">WO 2005/077447 PCT/A<confidence value="15">1U</confidence>
169
+ 2005/000174 </boundary-data>
170
+ <p id="p-36" num="36">
171
+ <page-break num="9"/>
172
+ [0030] Preferably, the device delivers a generally constant therapeutic level of continuous positive airway pressure (CPAP) during any given treatment session. </p>
173
+ <p id="p-37" num="37">However, consistent with the control principles of the invention as described herein, other types of pressure treatment may be implemented in the apparatus, such as bi-level <confidence value="5">C</confidence>
174
+ PAP treatment or other variants of natural patient-synchronized pressure changes. </p>
175
+ <p id="p-38" num="38">A. Control of Pressure Ad<confidence value="5">j</confidence>
176
+ ustments Based on Historic AHI Determinations [0031<confidence value="5">]</confidence>
177
+ As illustrated in FIG. 2, the pressure treatment apparatus implements control based on historic AHI determinations. As shown in step <part-num-ref name="pressure treatment apparatus implements control based on historic AHI determinations. As shown in step">20,</part-num-ref>
178
+ airway pressure treatment is provided to the patient during a first treatment session. In such a session, in the absence of historic AHI, the pressure treatment level will be set to a default low or minimum level, or a level prescribed by a physician or clinician. Preferably, no adjustments to the treatment pressure are made to change the level of therapy in response to a current detection of an SDB event during the current session. During the treatment session, in step <part-num-ref name="treatment session, in step">22,</part-num-ref>
179
+ sleep disordered breathing events are detected and an index of these events is determined. Preferably, apnea and hypopnea events are detected and an AH<confidence value="5">I</confidence>
180
+ , the AHI being initialized for the current session, is incremented by the number of such detected events. In step <part-num-ref name="number of such detected events. In step">24,</part-num-ref>
181
+ a new or subsequent treatment session is initiated with the apparatus. In this subsequent session, a therapeutic level of the treatment is set automatically as a function of the SDB event related index that was determined in the prior treatment session. </p>
182
+ <p id="p-39" num="39">[0032] In the preferred embodiment of the invention, each of the previously described treatment sessions is a different night's treatment with the device. Thus, an AHI may be recorded during use of the treatment apparatus during a single night and saved at the conclusion of the session. This saved AHI may then be utilized to set the treatment pressure in the next use of the device, such as during the next night. To distinguish such sessions, the device may be configured to store the AHI on power down. Then it will utilize a previously recorded AHI, if it exists, in setting the treatment pressure after the device is powered on but before or as treatment is commenced.</p>
183
+ <boundary-data type="header">
184
+ <confidence value="888">-9-</confidence>
185
+ </boundary-data>
186
+ <boundary-data type="header">WO 2005/077447 PCT/A<confidence value="8">U</confidence>
187
+ 2005/0<confidence value="88666">00174</confidence>
188
+ </boundary-data>
189
+ <p id="p-40" num="40">
190
+ <page-break num="10"/>
191
+ Alternatively, other schemes for ensuring the use of an AHI from a previously recorded session may be implemented. In one alternative scheme, date and/or time of every determined AHI from all sessions are recorded and stored. During a subsequent use, checking is performed for the most recent AHI. Similarly, this may be implemented by checking the date of an AHI against an internal clock to permit the use of a previous day's AHI in setting treatment pressure. </p>
192
+ <p id="p-41" num="41">[0033] While additional pressure treatment adjustments may be made in a current session based on a current AHI determination or on detection of an S<confidence value="5">D</confidence>
193
+ B related event, it is preferred that no such adjustments be made until a subsequent session. Similarly, the ramping of pressure from a low pressure up to the set therapeutic treatment pressure such that the patient can fall asleep before reaching the therapeutic level may also be implemented by the device. </p>
194
+ <p id="p-42" num="42">B. Determination of an Apnea Hypopnea Index (AHI) in a first Session <confidence value="5">[</confidence>
195
+ 0034] As previously noted, the pressure treatment device preferably detects sleep disordered breathing events including apneas and hypopneas, by determining an Apnea-Hypopnea Index. Optionally, other SDB related indices may be used, for example, an apnea index, a hypopnea index or some other <confidence value="5">S</confidence>
196
+ DB related index. The preferred determination methodology is illustrated in the flow chart of FIG. 3. At the beginning of a treatment session with the device, a current S<confidence value="5">D</confidence>
197
+ B index or AHI is reset or initialized in step <part-num-ref name="current SDB index or AHI is reset or initialized in step">30.</part-num-ref>
198
+ During the delivery of pressure treatment, flow is continuously measured or determined in step <part-num-ref name="delivery of pressure treatment, flow is continuously measured or determined in step">32.</part-num-ref>
199
+ With flow information or the flow signal (e.g., from a differential pressure transducer or derived from blower speed or power to the blower motor), measures of ventilation (e.g., an average flow determined over a period of time) are calculated in a step <part-num-ref name="step">34.</part-num-ref>
200
+ </p>
201
+ <p id="p-43" num="43">[0035] Preferably, these ventilation measures include a short term measure and a long term measure. In one embodiment, a suitable recent ventilation measure or a short term average may be a low pass filtered flow signal utilizing a low pass filter having a <boundary-data type="header">
202
+ <confidence value="8">-</confidence>
203
+ <confidence value="888">10-</confidence>
204
+ </boundary-data>
205
+ <page-break num="11"/>
206
+ <boundary-data type="header">
207
+ <confidence value="5">W</confidence>
208
+ O 2005/077447 PC<confidence value="588">T/A</confidence>
209
+ <confidence value="5">U</confidence>
210
+ 2005/0001<confidence value="88">74</confidence>
211
+ </boundary-data>
212
+ time constant which is short with respect to the duration of a breath, e.g., about <part-num-ref name="about">2</part-num-ref>
213
+ to <part-num-ref name="to">8</part-num-ref>
214
+ seconds. A suitable longer term ventilation or longer term average measure of flow may be a low pass filtered flow signal utilizing a low pass filter having a time constant which is long with respect to the duration of a breath, e.g., about <part-num-ref name="about">110</part-num-ref>
215
+ seconds. </p>
216
+ <p id="p-44" num="44">[0036] These ventilation measures, including a short term measure and a long term measure, are for purposes of comparing a more recent average measure with a longer term average. From the results of such a comparison, either apneas or hypopneas may be detected in steps 36A and/or 36B respectively. For example, in detecting a hypopnea, if the short term average measure falls below the longer term average such that it is less than 50% of the longer term average, a hypopnea may be tallied or detected. Similarly, if the short term average falls below the longer term average such that it is less than 20% of the longer term average, an apnea may be tallied or detected.</p>
217
+ <p id="p-45" num="45">[0037] In one embodiment of the invention an AHI scoring scheme may be implemented as follows:</p>
218
+ <p id="p-46" num="46">
219
+ <confidence value="66">i.</confidence>
220
+ An apnea is scored if a <part-num-ref name="">2</part-num-ref>
221
+ second moving average ventilation drops below 25% of a recent average ventilation (time constant =1<confidence value="66">00</confidence>
222
+ s) for at least <part-num-ref name="recent average ventilation (time constant =100s) for at least">10</part-num-ref>
223
+ consecutive seconds, ii. A hypopnea is scored if an <part-num-ref name="">8</part-num-ref>
224
+ second moving average drops below 50% but not more than 25% of the recent average ventilation for <part-num-ref name="recent average ventilation for">10</part-num-ref>
225
+ consecutive seconds. </p>
226
+ <p id="p-47" num="47">[0038] Those skilled in the art will recognize other methods or modifications for detecting hypopneas or apneas and determining an AHI or an <confidence value="5">S</confidence>
227
+ DB index which will otherwise indicate severity in the patient's SDB symptoms. </p>
228
+ <boundary-data type="header">
229
+ <confidence value="8888">-11-</confidence>
230
+ </boundary-data>
231
+ <boundary-data type="header">WO 2<confidence value="668668888">005/07744</confidence>
232
+ 7 PCT/A<confidence value="5">U</confidence>
233
+ 2005/<confidence value="555">000</confidence>
234
+ 174 </boundary-data>
235
+ <p id="p-48" num="48">
236
+ <page-break num="12"/>
237
+ [0039] After detecting either an apnea or a hypopnea event, an AHI may be incremented in step <part-num-ref name="AHI may be incremented in step">37.</part-num-ref>
238
+ After incrementing the AHI, the system determines whether the session has ended at step <part-num-ref name="session has ended at step">38.</part-num-ref>
239
+ At this point, the system terminates at step <part-num-ref name="system terminates at step">39.</part-num-ref>
240
+ If the session is ongoing, the system cycles back to step <part-num-ref name="system cycles back to step">32</part-num-ref>
241
+ to continue detecting apnea and hypopnea events and incrementing the AHI. </p>
242
+ <p id="p-49" num="49">[0040] The total of these detected apneas and hypopneas for any given session would make up the AHI used in the adjustment of treatment pressure in a subsequent session. Preferably, the AH<confidence value="5">I</confidence>
243
+ is determined by adding the total number of apneas and hypopneas the patient experienced over a treatment period covering a single night. </p>
244
+ <p id="p-50" num="50">Optionally, the AHI may be a function of time such as an average hourly AH<confidence value="5">I</confidence>
245
+ determined over the total time for any given treatment session with the device such as a period of sleep or a single night of sleep. </p>
246
+ <p id="p-51" num="51">C. Adjustment of Treatment Pressure in Response to AHI in a Subsequent Session [0041] As previously noted, preferably automated adjustments to the therapeutic level of the treatment pressure are only made or only take effect for treatment in a subsequent session or subsequent night of treatment based on an AHI determined in a prior session or previous night of treatment. That is, the automated dynamic pressure changes are on a night-by-night basis rather than a breath-by-breath basis. Thus, the device implements an algorithm for adjusting the treatment pressure in a subsequent session. For example, as illustrated in FIG. 4, after starting a new or entering a treatment session in step <part-num-ref name="treatment session in step">40,</part-num-ref>
247
+ the device may then evaluate a previously recorded AHI in an evaluation step <part-num-ref name="evaluation step">42.</part-num-ref>
248
+ Based on the detected AHI from a prior session a new treatment pressure will be set. Optionally, for a first use or first session, the AHI may have a default of <part-num-ref name="default of">0</part-num-ref>
249
+ such that no changes to the treatment pressure will be implemented in the first session. Similarly, a default pressure setting for the first use may be a low non- therapeutic value (e.g., about 1-3 cmH2<confidence value="5">O</confidence>
250
+ ) or some other physician or clinician set value in a therapeutic range of about 4-20 cmH2<confidence value="58">0.</confidence>
251
+ </p>
252
+ <boundary-data type="header">
253
+ <confidence value="8">-</confidence>
254
+ <confidence value="88">12</confidence>
255
+ <confidence value="8">-</confidence>
256
+ </boundary-data>
257
+ <boundary-data type="header">WO 2005/077447 PCT<confidence value="688">/AU</confidence>
258
+ 2005/0001<confidence value="86">74</confidence>
259
+ </boundary-data>
260
+ <p id="p-52" num="52">
261
+ <page-break num="13"/>
262
+ [0042] In evaluating the historic AHI in step <part-num-ref name="historic AHI in step">42,</part-num-ref>
263
+ if a prior session results in no detected apneas or hypopneas or only a few (e.g., AHI = <part-num-ref name="AHI =">0</part-num-ref>
264
+ or less than 8), no pressure changes will be implemented and the treatment pressure setting will remain from the prior session. Alternatively, for purposes of determining the minimum pressure necessary to prevent SDB, for an AHI of <part-num-ref name="AHI of">0</part-num-ref>
265
+ or an AHI of less than <part-num-ref name="AHI of less than">8</part-num-ref>
266
+ from the prior session, the device may lower the pressure in the new session. In lowering the pressure, the device may decrement the pressure by a fixed amount, (e.g., 0.25 cmH2<confidence value="28">O)</confidence>
267
+ which is preferably lower than the pressure increase although they may be the same. </p>
268
+ <p id="p-53" num="53">Thus, in setting the treatment pressure in step <part-num-ref name="treatment pressure in step">44,</part-num-ref>
269
+ the new pressure for the current setting will be the pressure from the prior session less the fixed decrement amount. </p>
270
+ <p id="p-54" num="54">
271
+ <confidence value="5">[</confidence>
272
+ 0043] However, if the AHI from the prior session is greater than <part-num-ref name="prior session is greater than">0</part-num-ref>
273
+ or greater than some low non-adjustment range (e.g., 1-8 events), the treatment pressure will automatically increment upwards since such an AHI score is an indication of the need for an increase in treatment. Thus, based on the high AHI from the previous night, the treatment pressure can be increased by some increment. The treatment pressure increase is performed with the intent to decrease the AHI towards a clinically desirable level in the subsequent night. The ideal treatment pressure will decrease the AHI to a clinically desirable level but not be so far in excess of the minimum required pressure that it induces unnecessary discomfort. Therefore, the quantum of the incremental pressure increase may vary depending upon the perceived clinical severity of the AHI. </p>
274
+ <p id="p-55" num="55">For example, the choice of incremental pressure increase may reflect the clinical observation that a relatively small increment will induce a clinically significant change where the patient has a relatively low AHI (e.g., a pressure increment of 0.5 cmH2<confidence value="4">0</confidence>
275
+ for an AHI in the range of <part-num-ref name="range of">5</part-num-ref>
276
+ - <part-num-ref name="-">19)</part-num-ref>
277
+ while a relatively larger increment will be appropriate to induce a clinically significant change where the patient has a relatively high AH<confidence value="5">I</confidence>
278
+ (e.g., a pressure increment of <part-num-ref name="pressure increment of">2</part-num-ref>
279
+ cmH2<confidence value="5">O</confidence>
280
+ for an AH<confidence value="5">I</confidence>
281
+ of <part-num-ref name="AHI of">40</part-num-ref>
282
+ or higher). </p>
283
+ <p id="p-56" num="56">[0044] Referring to Fig. 4, in the treatment pressure setting step <part-num-ref name="treatment pressure setting step">44,</part-num-ref>
284
+ the treatment pressure is automatically set for the new session to be the previous session's pressure setting plus the increment. The treatment pressure will then be delivered during the <boundary-data type="header">
285
+ <confidence value="8">-</confidence>
286
+ <confidence value="888">13-</confidence>
287
+ </boundary-data>
288
+ <page-break num="14"/>
289
+ <boundary-data type="header">WO 2<confidence value="66885">005/0</confidence>
290
+ 77447 PCT<confidence value="688">/AU</confidence>
291
+ 2005/<confidence value="555">000</confidence>
292
+ 174 </boundary-data>
293
+ current session in step <part-num-ref name="current session in step">46</part-num-ref>
294
+ and then, at step <part-num-ref name="and then, at step">48,</part-num-ref>
295
+ the system cycles back to step <part-num-ref name="system cycles back to step">30</part-num-ref>
296
+ (Figure <part-num-ref name="(Figure">3)</part-num-ref>
297
+ and again begins the process of determining a new AHI. The new AHI will affect the treatment pressure for the next session or treatment in the next night or future session. Such a scheme allows the device to adjust itself over an unlimited number of nights, while evolving with the needs of the patient. </p>
298
+ <p id="p-57" num="57">[0045] In one embodiment, other schemes of adjustment of the pressure may be based on patterns of the AHI over more than a single night, such as two or more nights.</p>
299
+ <p id="p-58" num="58">For example, the pressure may be lowered if the AHI has been <part-num-ref name="AHI has been">0</part-num-ref>
300
+ for two or more consecutive sessions. Similarly, pressure may be increased only if the AHI in more than one consecutive night, for example, <part-num-ref name="AHI in more than one consecutive night, for example,">2</part-num-ref>
301
+ or <part-num-ref name="or">3</part-num-ref>
302
+ nights, suggests a need for an increase. </p>
303
+ <p id="p-59" num="59">Preferably, any decay in pressure over time is slower than the increase in pressure over time.</p>
304
+ <p id="p-60" num="60">
305
+ <confidence value="5">[</confidence>
306
+ 0046] Optionally, the device may be configured with an adaptation range that limits the changes to the treatment pressure that the device may automatically implement based on a previous night's AHI determination. The adaptation range may be a preset variable that is determined by a physician and preferably is not changed during the many treatment sessions with the user or patient. A default range may be set into the device in the absence of such a setting by a physician. For example, the physician may preset the adaptation range to a value of <part-num-ref name="value of">10</part-num-ref>
307
+ cmH2<confidence value="4">0</confidence>
308
+ . When a pressure change is implemented by the device, the range is checked to make certain that any increments attempted by the device never exceed the original pressure setting of the physician by the amount of the range. Thus, if the pressure is set to <part-num-ref name="pressure is set to">5</part-num-ref>
309
+ cmH2<confidence value="4">0</confidence>
310
+ for the first session with a patient, and the adaptation range is set to <part-num-ref name="adaptation range is set to">10</part-num-ref>
311
+ cmH2<confidence value="4">0</confidence>
312
+ , any automated treatment pressure change that attempts to increment the treatment pressure beyond <part-num-ref name="treatment pressure beyond">15</part-num-ref>
313
+ cmH2<confidence value="4">0</confidence>
314
+ would be prevented. In addition, the device may be configured with an optional warning indicator to advise the patient or the physician of the attempted increase beyond the adaptation range. </p>
315
+ <p id="p-61" num="61">
316
+ <confidence value="5">[</confidence>
317
+ 0047] A device that implements the above-described treatment scheme would have many benefits for SDB patients. For example, utilizing the described algorithm would be <boundary-data type="header">
318
+ <confidence value="8">-</confidence>
319
+ <confidence value="88">14</confidence>
320
+ <confidence value="8">-</confidence>
321
+ </boundary-data>
322
+ <page-break num="15"/>
323
+ <boundary-data type="header">WO 200<confidence value="4">5</confidence>
324
+ /077447 PCT/A<confidence value="5">U</confidence>
325
+ 200<confidence value="48666888">5/000174</confidence>
326
+ </boundary-data>
327
+ more cost effective when compared to more complex detection and adjustment schemes. Also, since the device can adjust on a night-by-night basis, it can provide adaptation for seasonal changes that may affect the patient's condition. It can also adapt with the patient's disease progression. </p>
328
+ <p id="p-62" num="62">[0048] The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not as restrictive. The scope of the invention is, therefore, indicated by the appended claims and their combination in whole or in part rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.</p>
329
+ <boundary-data type="header">
330
+ <confidence value="8">-</confidence>
331
+ <confidence value="888">15-</confidence>
332
+ </boundary-data>
333
+ </description>
334
+ </us-patent-application>
335
+
prior_art/10711736.xml ADDED
The diff for this file is too large to render. See raw diff
 
prior_art/10880754.xml ADDED
@@ -0,0 +1,545 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>10880754</doc-number>
8
+ <date>2004-06-30</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <heading id="h-1">UNITED STATES PATENT APPLICATION FOR:</heading>
14
+ <heading id="h-2">METHOD AND APPARATUS FOR STABLE</heading>
15
+ <heading id="h-3">PLASMA PROCESSING</heading>
16
+ <heading id="h-4">INVENTORS:</heading>
17
+ <heading id="h-5">VALENTIN N. TODOROW</heading>
18
+ <heading id="h-6">JOHN P. HOLLAND</heading>
19
+ <heading id="h-7">MICHAEL D. WILLWERTH</heading>
20
+ <p id="p-1" num="1">CERTIFICATION OF MAILING UNDER 37 C.F.R. 1.10 I hereby certify that this New Application and the <confidence value="1">/</confidence>
21
+ documents referred to as enclosed therein are being S<confidence value="88666">ignat</confidence>
22
+ deposited with the United States Postal Service on June <part-num-ref name="United States Postal Service on June">
23
+ <confidence value="666">30,</confidence>
24
+ </part-num-ref>
25
+ <part-num-ref name="United States Postal Service on June 30,">
26
+ <confidence value="66666">2004,</confidence>
27
+ </part-num-ref>
28
+ in an envelope marked as "Express Mail <confidence value="221">y;V</confidence>
29
+ <confidence value="56">f)</confidence>
30
+ <confidence value="14">m8</confidence>
31
+ United States <confidence value="5">P</confidence>
32
+ ostal Service", Mailing Label No. Name EV026405657US, addressed to: Commissioner for Patents, P.O. Box <part-num-ref name="envelope marked as &quot;Express Mail y;V f) m8 United States Postal Service&quot;, Mailing Label No. Name EV026405657US, addressed to: Commissioner for Patents, P.O. Box">1450,</part-num-ref>
33
+ Alexandria, VA 22313-1450 <confidence value="111">(__</confidence>
34
+ <confidence value="111">___</confidence>
35
+ <confidence value="111">___</confidence>
36
+ Date of signature ATTORNEY DOCKET NUMBER: <part-num-ref name="envelope marked as &quot;Express Mail y;V f) m8 United States Postal Service&quot;, Mailing Label No. Name EV026405657US, addressed to: Commissioner for Patents, P.O. Box 1450, Alexandria, VA 22313-1450 (__ ___ ___ Date of signature ATTORNEY DOCKET NUMBER:">7716</part-num-ref>
37
+ ALRT/ETCH/CONE/JB<confidence value="5">1</confidence>
38
+ Moser, Patterson &amp; Sheridan, L.L.P. </p>
39
+ <p id="p-2" num="2">3040 Post Oak Boulevard Suite 1500 Houston, TX <part-num-ref name="Houston, TX">77056</part-num-ref>
40
+ <boundary-data type="header">281630 1</boundary-data>
41
+ <page-break num="2"/>
42
+ <boundary-data type="header">PATENT <confidence value="2">-</confidence>
43
+ </boundary-data>
44
+ <boundary-data type="header">7716 <confidence value="222222222222222222">ALRT/ETCH/CONEIJB1</confidence>
45
+ </boundary-data>
46
+ </p>
47
+ <heading id="h-8">METHOD AND APPARATUS FOR STABLE PLASMA PROCESSING</heading>
48
+ <heading id="h-9">CROSS-REFERENCE TO RELATED APPLICATIONS</heading>
49
+ <p id="p-3" num="3">[0001<confidence value="2">]</confidence>
50
+ The subject matter of this application is related to the subject matter disclosed in United States Patent Application Serial No. <confidence value="8">,</confidence>
51
+ entitled "METHOD AND APPARATUS FOR PHOTOMASK PLASMA ETCHING", filed on <confidence value="6">,</confidence>
52
+ by Kumar, et al. (ATTORNEY DOCKET NUMBER 9400), which is hereby incorporated herein by reference in its entirety. </p>
53
+ <heading id="h-10">BACKGROUND OF THE INVENTION</heading>
54
+ <p id="p-4" num="4">Field of the Invention [0002<confidence value="5">]</confidence>
55
+ Embodiments of the present invention generally relate to a method and apparatus for plasma processing of a substrate and, more specifically, to a method and apparatus for etching a substrate using a stable plasma. </p>
56
+ <p id="p-5" num="5">Description of the Related Art [0003<confidence value="5">]</confidence>
57
+ Integrated circuits have evolved into complex devices that can include millions of transistors, capacitors and resistors on a single chip. The evolution of chip designs continually requires faster circuitry and greater circuit density. </p>
58
+ <p id="p-6" num="6">Circuit density has a pronounce importance as the speed and number of functions a circuit can execute increases along with the density of the circuit structure. Some design attributes affecting the speed and circuit density of integrated circuits include the resistance and thickness of the materials used to form the layer comprising the circuit structure formed on a substrate.</p>
59
+ <p id="p-7" num="7">
60
+ <confidence value="85556">[0004</confidence>
61
+ ] Metallic materials are used to create wireline interconnects, vias, electrodes, and the like. The metal structures are key to the functionality of an integrated circuit. One metal that is frequently used to fabricate circuit structures is tungsten. Tungsten may be accurately deposited using conventional Chemical Vapor Deposition (CVD) methods and generally has a low resistivity. Circuit designers have found tungsten to be a favorable material for use proximate polysilicon as tungsten exhibits good resistance to permeation <boundary-data type="header">
62
+ <confidence value="8">2</confidence>
63
+ </boundary-data>
64
+ <boundary-data type="header">281630</boundary-data>
65
+ <page-break num="3"/>
66
+ <boundary-data type="header">PATENT <confidence value="6">'</confidence>
67
+ </boundary-data>
68
+ <boundary-data type="header">7716 <confidence value="222222222222222222">ALRT/ETCHICONEIJB1</confidence>
69
+ </boundary-data>
70
+ by polysilicon, which enables tungsten to retain its physical properties over the course of substrate processing and device use. </p>
71
+ <p id="p-8" num="8">[0005<confidence value="5">]</confidence>
72
+ In order to maximize circuit density, the layers comprising the circuit structure, including those comprising tungsten, must be minimized. However, when processing such thin layers, care must be taken to avoid damaging the layers during processing. Damaged layers result in defective circuit structures and increased substrate rejects. </p>
73
+ <p id="p-9" num="9">
74
+ <confidence value="866666">[0006]</confidence>
75
+ One process that can easily damage thin layers is etching. </p>
76
+ <p id="p-10" num="10">Fluorinated chemistry is typically employed to remove exposed tungsten and other metals. A plasma is utilized to enhance the etch process. However, it is difficult to maintain a stable plasma. One method for increasing plasma stability is to increase the power supplied to the chamber. Another method is to decrease the gap between the substrate being etched and the top of the chamber. Unfortunately, both increasing the power and decreasing the gap lead to an increase in ion bombardment of the substrate, which may seriously damage the circuits being formed on the substrate.</p>
77
+ <p id="p-11" num="11">[0007<confidence value="5">]</confidence>
78
+ Therefore, there is a need in the art for an improved method and apparatus for etching metals, especially tungsten. </p>
79
+ <heading id="h-11">SUMMARY OF THE INVENTION</heading>
80
+ <p id="p-12" num="12">
81
+ <confidence value="855566">[0008]</confidence>
82
+ The present invention generally provides a method and apparatus for etching a substrate using a spatially modified plasma. In one embodiment, the method includes providing a process chamber having a plasma stabilizer disposed above a substrate support pedestal. A substrate is placed upon the pedestal. A process gas is introduced into the process chamber and a quasi- remote plasma is formed from the process gas. The substrate is etched with a plasma having an ion density to radical density ratio defined by the plasma stabilizer. </p>
83
+ <boundary-data type="header">
84
+ <confidence value="8">3</confidence>
85
+ </boundary-data>
86
+ <boundary-data type="header">281630</boundary-data>
87
+ <boundary-data type="header">PATENT <confidence value="2">-</confidence>
88
+ </boundary-data>
89
+ <boundary-data type="header">7716 <confidence value="222222222222222222">ALRTIETCHICONEIJB1</confidence>
90
+ </boundary-data>
91
+ <p id="p-13" num="13">
92
+ <page-break num="4"/>
93
+ <confidence value="85556">[0009</confidence>
94
+ ] In another embodiment of the invention, an apparatus is provided for etching a <confidence value="5">.</confidence>
95
+ substrate with a spatially modified plasma. The apparatus includes a process chamber having a substrate support pedestal disposed therein. An RF power source is provided for forming a plasma within the chamber. A plasma stabilizer is disposed in the chamber above the pedestal. The plasma stabilizer controls the spatial distribution of charged and neutral species of the plasma. </p>
96
+ <p id="p-14" num="14">The plasma stabilizer includes a substantially flat member electrically isolated from the chamber. The member has a plurality of apertures formed therethrough.</p>
97
+ <heading id="h-12">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
98
+ <p id="p-15" num="15">[0010] So that the manner in which the above recited features of the present invention can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only typical embodiments of this invention and are therefore not to be considered limiting of its scope, for the invention may admit to other equally effective embodiments.</p>
99
+ <p id="p-16" num="16">[0011] Figure 1 is a schematic diagram of an etch reactor having a plasma stabilizer;</p>
100
+ <p id="p-17" num="17">[0012] Figure 2 is a partial perspective view of one embodiment of the plasma stabilizer of Figure 1; and [0013] Figure 3 is a flow chart of a method of etching tungsten.</p>
101
+ <heading id="h-13">DETAILED DESCRIPTION</heading>
102
+ <p id="p-18" num="18">
103
+ <confidence value="85566">[0014</confidence>
104
+ ] The present invention provides a method and apparatus for improved etching processes. The apparatus includes a plasma stabilizer disposed in a plasma processing chamber. The plasma stabilizer controls the spatial distribution of the charged and neutral species in the chamber during processing such that a dense, stable plasma may be formed in an upper processing region of the chamber (above the plasma stabilizer) and a plasma <boundary-data type="header">
105
+ <confidence value="8">4</confidence>
106
+ </boundary-data>
107
+ <boundary-data type="header">281630</boundary-data>
108
+ <page-break num="5"/>
109
+ <boundary-data type="header">PATENT</boundary-data>
110
+ <boundary-data type="header">7716 ALRT<confidence value="5">/</confidence>
111
+ ETCH<confidence value="1">/</confidence>
112
+ CONE<confidence value="4885">/JB1</confidence>
113
+ </boundary-data>
114
+ with controlled characteristics in a lower processing region (between the plasma stabilizer and a substrate disposed on a substrate support pedestal). </p>
115
+ <p id="p-19" num="19">[0015] Figure 1 depicts a schematic diagram of an etch reactor <part-num-ref name="etch reactor">100</part-num-ref>
116
+ having a plasma stabilizer <part-num-ref name="plasma stabilizer">170.</part-num-ref>
117
+ Suitable reactors that may be adapted for use with the teachings disclosed herein include, for example, the Decoupled Plasma Source (DPS<confidence value="25">*)</confidence>
118
+ I and DPS<confidence value="6">®</confidence>
119
+ <confidence value="66">II</confidence>
120
+ reactors, all of which are available from Applied Materials, Inc. of Santa Clara, California. The DPS<confidence value="5">®</confidence>
121
+ I and DPS<confidence value="6">®</confidence>
122
+ <confidence value="66">II</confidence>
123
+ reactors may also be used as processing modules of a Centura<confidence value="4">®</confidence>
124
+ integrated semiconductor wafer processing system, also available from Applied Materials, Inc. The particular embodiment of the reactor <part-num-ref name="reactor">100</part-num-ref>
125
+ shown herein is provided for illustrative purposes and should not be used to limit the scope of the invention. </p>
126
+ <p id="p-20" num="20">
127
+ <confidence value="86666">[0016</confidence>
128
+ ] The reactor <part-num-ref name="reactor">100</part-num-ref>
129
+ generally comprises a process chamber <part-num-ref name="process chamber">102</part-num-ref>
130
+ having a substrate pedestal <part-num-ref name="substrate pedestal">124</part-num-ref>
131
+ within a conductive body (wall) <part-num-ref name="conductive body (wall)">104,</part-num-ref>
132
+ and a controller <part-num-ref name="controller">146.</part-num-ref>
133
+ The chamber <part-num-ref name="chamber">102</part-num-ref>
134
+ has a substantially flat dielectric ceiling <part-num-ref name="substantially flat dielectric ceiling">108.</part-num-ref>
135
+ Other modifications of the chamber <part-num-ref name="chamber">102</part-num-ref>
136
+ may have other types of ceilings, e.g., a dome-shaped ceiling. An antenna <part-num-ref name="antenna">110</part-num-ref>
137
+ is disposed above the ceiling <part-num-ref name="ceiling">108.</part-num-ref>
138
+ The antenna <part-num-ref name="antenna">110</part-num-ref>
139
+ comprises one or more inductive coil elements that may be selectively controlled (two co-axial elements 11<confidence value="5">0</confidence>
140
+ a and 11<confidence value="5">0</confidence>
141
+ b are shown in Figure 1). The antenna <part-num-ref name="antenna">110</part-num-ref>
142
+ is coupled through a first matching network <part-num-ref name="first matching network">114</part-num-ref>
143
+ to a plasma power source <part-num-ref name="plasma power source">112.</part-num-ref>
144
+ The plasma power source <part-num-ref name="plasma power source">112</part-num-ref>
145
+ is typically capable of producing up to about <part-num-ref name="is typically capable of producing up to about">3000</part-num-ref>
146
+ W at a tunable frequency in a range from about <part-num-ref name="range from about">50</part-num-ref>
147
+ kHz to about 13.56 MHz. </p>
148
+ <p id="p-21" num="21">[0017<confidence value="5">]</confidence>
149
+ The substrate pedestal (cathode) <part-num-ref name="substrate pedestal (cathode)">124</part-num-ref>
150
+ is coupled through a second matching network <part-num-ref name="second matching network">142</part-num-ref>
151
+ to a biasing power source <part-num-ref name="biasing power source">140.</part-num-ref>
152
+ The biasing source <part-num-ref name="biasing source">140</part-num-ref>
153
+ generally is a source of up to about <part-num-ref name="source of up to about">500</part-num-ref>
154
+ W at a frequency of approximately 13.56 MHz that is capable of producing either continuous or pulsed power. </p>
155
+ <p id="p-22" num="22">Alternatively, the source <part-num-ref name="source">140</part-num-ref>
156
+ may be a DC or pulsed DC source. </p>
157
+ <p id="p-23" num="23">
158
+ <confidence value="866665">[0018]</confidence>
159
+ In one embodiment, the substrate support pedestal <part-num-ref name="substrate support pedestal">124</part-num-ref>
160
+ comprises an electrostatic chuck <part-num-ref name="electrostatic chuck">160.</part-num-ref>
161
+ The electrostatic chuck <part-num-ref name="electrostatic chuck">160</part-num-ref>
162
+ comprises at least one clamping electrode <part-num-ref name="comprises at least one clamping electrode">132</part-num-ref>
163
+ and is controlled by a chuck power supply <part-num-ref name="chuck power supply">166.</part-num-ref>
164
+ In alternative embodiments, the substrate pedestal <part-num-ref name="substrate pedestal">124</part-num-ref>
165
+ may comprise substrate <boundary-data type="header">
166
+ <confidence value="8">5</confidence>
167
+ </boundary-data>
168
+ <boundary-data type="header">281630</boundary-data>
169
+ <page-break num="6"/>
170
+ <boundary-data type="header">PATENT <confidence value="6">'</confidence>
171
+ </boundary-data>
172
+ <boundary-data type="header">7716 ALRT<confidence value="5">/</confidence>
173
+ ETCH<confidence value="4">/</confidence>
174
+ CONE<confidence value="4885">/JB1</confidence>
175
+ </boundary-data>
176
+ retention mechanisms such as a susceptor clamp ring, a mechanical chuck, and the like. </p>
177
+ <p id="p-24" num="24">[0019] A lift mechanism <part-num-ref name="lift mechanism">138</part-num-ref>
178
+ is used to lower or raise the substrate <part-num-ref name="substrate">122</part-num-ref>
179
+ onto or off of the substrate support pedestal <part-num-ref name="substrate support pedestal">124.</part-num-ref>
180
+ Generally, the lift mechanism <part-num-ref name="lift mechanism">162</part-num-ref>
181
+ comprises a plurality of lift pins <part-num-ref name="plurality of lift pins">130</part-num-ref>
182
+ (one lift pin is shown) that travel through respective guide holes <part-num-ref name="(one lift pin is shown) that travel through respective guide holes">136.</part-num-ref>
183
+ </p>
184
+ <p id="p-25" num="25">[0020] In operation, the temperature of the substrate <part-num-ref name="substrate">122</part-num-ref>
185
+ is controlled by stabilizing the temperature of the substrate pedestal <part-num-ref name="substrate pedestal">124.</part-num-ref>
186
+ In one embodiment, the substrate support pedestal <part-num-ref name="substrate support pedestal">124</part-num-ref>
187
+ comprises a resistive heater <part-num-ref name="resistive heater">144</part-num-ref>
188
+ and a heat sink <part-num-ref name="heat sink">128.</part-num-ref>
189
+ The resistive heater <part-num-ref name="resistive heater">144</part-num-ref>
190
+ generally comprises at least one heating element <part-num-ref name="generally comprises at least one heating element">134</part-num-ref>
191
+ and is regulated by a heater power supply <part-num-ref name="heater power supply">168.</part-num-ref>
192
+ A backside gas (e.g., helium (He)) from a gas source <part-num-ref name="gas source">156</part-num-ref>
193
+ is provided via a gas conduit <part-num-ref name="gas conduit">158</part-num-ref>
194
+ to channels that are formed in the pedestal surface under the substrate <part-num-ref name="substrate">122.</part-num-ref>
195
+ The backside gas is used to facilitate heat transfer between the pedestal <part-num-ref name="pedestal">124</part-num-ref>
196
+ and the substrate <part-num-ref name="substrate">122.</part-num-ref>
197
+ During processing, the pedestal <part-num-ref name="pedestal">124</part-num-ref>
198
+ may be heated by the embedded resistive heater <part-num-ref name="embedded resistive heater">144</part-num-ref>
199
+ to a steady-state temperature, which in combination with the helium backside gas, facilitates uniform heating of the substrate <part-num-ref name="substrate">122.</part-num-ref>
200
+ Using such thermal control, the substrate <part-num-ref name="substrate">122</part-num-ref>
201
+ may be maintained at a temperature between about <part-num-ref name="temperature between about">0</part-num-ref>
202
+ and <part-num-ref name="and">350</part-num-ref>
203
+ degrees Celsius. </p>
204
+ <p id="p-26" num="26">[0021] A plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
205
+ is disposed in the chamber <part-num-ref name="chamber">102</part-num-ref>
206
+ above the pedestal <part-num-ref name="pedestal">124.</part-num-ref>
207
+ The plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
208
+ controls the spatial distribution of the charged and neutral species in the chamber <part-num-ref name="chamber">102</part-num-ref>
209
+ during processing such that a dense, stable plasma may be formed in an upper processing region of the chamber (above the plasma stabilizer <part-num-ref name="plasma stabilizer">170)</part-num-ref>
210
+ and a plasma with controlled characteristics in a lower processing region (between the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
211
+ and a substrate <part-num-ref name="substrate">122</part-num-ref>
212
+ disposed on a substrate support pedestal 124). </p>
213
+ <p id="p-27" num="27">[0022] The plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
214
+ is electrically isolated from the chamber walls <part-num-ref name="chamber walls">104</part-num-ref>
215
+ and the pedestal <part-num-ref name="pedestal">124</part-num-ref>
216
+ and generally comprises a substantially flat plate <part-num-ref name="substantially flat plate">172</part-num-ref>
217
+ and a plurality of legs <part-num-ref name="plurality of legs">176.</part-num-ref>
218
+ The plate <part-num-ref name="plate">172</part-num-ref>
219
+ is supported in the chamber <part-num-ref name="chamber">102</part-num-ref>
220
+ above the pedestal <part-num-ref name="pedestal">124</part-num-ref>
221
+ by the legs <part-num-ref name="legs">176.</part-num-ref>
222
+ The plate <part-num-ref name="plate">172</part-num-ref>
223
+ defines one or more openings (apertures) that define a desired open area in the surface of the plate <part-num-ref name="plate">172.</part-num-ref>
224
+ The open area of the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
225
+ controls the quantity of <boundary-data type="header">
226
+ <confidence value="8">6</confidence>
227
+ </boundary-data>
228
+ <boundary-data type="header">281630</boundary-data>
229
+ <page-break num="7"/>
230
+ <boundary-data type="header">PATENT</boundary-data>
231
+ <boundary-data type="header">7716 <confidence value="222222222222222222">ALRTIETCH/CONEIJB1</confidence>
232
+ </boundary-data>
233
+ ions that pass from a plasma formed in an upper process volume <part-num-ref name="upper process volume">178</part-num-ref>
234
+ of the process chamber <part-num-ref name="process chamber">102</part-num-ref>
235
+ to a lower process volume <part-num-ref name="lower process volume">180</part-num-ref>
236
+ located between the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
237
+ and the substrate <part-num-ref name="substrate">122.</part-num-ref>
238
+ Thus, the open area of the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
239
+ controls the spatial distribution of charged and neutral species of the plasma in the process chamber <part-num-ref name="process chamber">102.</part-num-ref>
240
+ The greater the open area, the more ions can pass through the plasma stabilizer <part-num-ref name="plasma stabilizer">170.</part-num-ref>
241
+ As such, the size of the apertures <part-num-ref name="apertures">174</part-num-ref>
242
+ affects the ion density in volume <part-num-ref name="ion density in volume">180.</part-num-ref>
243
+ </p>
244
+ <p id="p-28" num="28">[0023<confidence value="5">]</confidence>
245
+ The apertures <part-num-ref name="apertures">174,</part-num-ref>
246
+ or open area, of the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
247
+ also affect the amount of etch by-products created on the surface of the substrate <part-num-ref name="substrate">122</part-num-ref>
248
+ from diffusing into the upper process volume <part-num-ref name="upper process volume">178</part-num-ref>
249
+ of the process chamber <part-num-ref name="process chamber">102</part-num-ref>
250
+ where the RF power is being deposited into the plasma. The size of the aperture <part-num-ref name="aperture">174</part-num-ref>
251
+ is chosen to allow sufficient ions and radicals created in the upper process volume <part-num-ref name="upper process volume">178</part-num-ref>
252
+ to reach the surface of the substrate <part-num-ref name="substrate">122</part-num-ref>
253
+ and to prevent etch by-products from significantly destabilizing the deposition of RF power into the plasma. </p>
254
+ <p id="p-29" num="29">
255
+ <confidence value="85586">[0024</confidence>
256
+ ] In addition, the greater the open area, the more uniform the spatial distribution of the charged and neutral species of the plasma becomes. A larger open area also reduces the stability of the plasma. Thus, by controlling the open area of the plasma stabilizer <part-num-ref name="plasma stabilizer">170,</part-num-ref>
257
+ the stability of the plasma is controlled. </p>
258
+ <p id="p-30" num="30">In addition, the spatial distribution of charged and neutral species in the upper and lower processing volumes <part-num-ref name="upper and lower processing volumes">178,</part-num-ref>
259
+ <part-num-ref name="upper and lower processing volumes 178,">180</part-num-ref>
260
+ is controlled, thereby controlling etch uniformity and selectivity. </p>
261
+ <p id="p-31" num="31">[0025<confidence value="5">]</confidence>
262
+ Figure 2 depicts one specific embodiment of the plasma stabilizer <part-num-ref name="plasma stabilizer">170.</part-num-ref>
263
+ In this embodiment, the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
264
+ includes a plate <part-num-ref name="plate">172</part-num-ref>
265
+ having one or more apertures <part-num-ref name="having one or more apertures">174</part-num-ref>
266
+ and a plurality of legs <part-num-ref name="plurality of legs">176.</part-num-ref>
267
+ The plate <part-num-ref name="plate">172</part-num-ref>
268
+ should be thick enough to be robust and thin enough to prevent the ions formed in the plasma from recombining. The plate <part-num-ref name="plate">172</part-num-ref>
269
+ may be fabricated of a ceramic (such as alumina), quartz, anodized aluminum, or other materials compatible with process chemistries and conditions. In another embodiment, the plate <part-num-ref name="plate">172</part-num-ref>
270
+ could comprise a screen or a mesh wherein the open area of the screen or mesh corresponds to the desired open area provided by the one or more <boundary-data type="header">
271
+ <confidence value="8">7</confidence>
272
+ </boundary-data>
273
+ <boundary-data type="header">281630</boundary-data>
274
+ <page-break num="8"/>
275
+ <boundary-data type="header">PATENT</boundary-data>
276
+ <boundary-data type="header">7716 <confidence value="222222222222222222">ALRT/ETCH/CONEIJB1</confidence>
277
+ </boundary-data>
278
+ apertures <part-num-ref name="one or more apertures">174.</part-num-ref>
279
+ Alternatively, a combination of a plate and screen or mesh may also be utilized. </p>
280
+ <p id="p-32" num="32">
281
+ <confidence value="655866">[0026]</confidence>
282
+ The one or more apertures <part-num-ref name="one or more apertures">174</part-num-ref>
283
+ may vary in size, spacing and geometric arrangement across the surface of the plate <part-num-ref name="plate">172</part-num-ref>
284
+ to obtain a desired open area. The apertures <part-num-ref name="apertures">174</part-num-ref>
285
+ should be large enough to allow the plasma to sufficiently penetrate through the plate <part-num-ref name="plate">172</part-num-ref>
286
+ and may be arranged to define an open area in the surface of the plate <part-num-ref name="plate">172</part-num-ref>
287
+ of from about <part-num-ref name="of from about">2</part-num-ref>
288
+ percent to about <part-num-ref name="percent to about">90</part-num-ref>
289
+ percent. In one embodiment, the apertures <part-num-ref name="apertures">174</part-num-ref>
290
+ are greater than 0.2 inches (0.51 cm) in diameter. In one embodiment, the one or more apertures <part-num-ref name="one or more apertures">174</part-num-ref>
291
+ includes a plurality of approximately half-inch (1.25 cm) diameter holes arranged in a square grid pattern. It is contemplated that the holes may be arranged in other geometric or random patterns utilizing other size holes or holes of various sizes. In another embodiment, the one or more apertures <part-num-ref name="one or more apertures">220</part-num-ref>
292
+ may comprise a single aperture <part-num-ref name="single aperture">220.</part-num-ref>
293
+ In one embodiment, the single aperture <part-num-ref name="single aperture">220</part-num-ref>
294
+ may be substantially the same size and shape of the substrate <part-num-ref name="substrate">614</part-num-ref>
295
+ disposed on the pedestal <part-num-ref name="pedestal">616.</part-num-ref>
296
+ </p>
297
+ <p id="p-33" num="33">
298
+ <confidence value="5">[</confidence>
299
+ 0027<confidence value="5">]</confidence>
300
+ The size, shape and patterning of the holes may vary depending upon the desired ion density in the lower process volume <part-num-ref name="lower process volume">180.</part-num-ref>
301
+ For example, more holes of small diameter may be used to increase the radical to ion density ratio in the volume <part-num-ref name="volume">180.</part-num-ref>
302
+ In other situations, the holes may be made larger, or a number of larger holes may be interspersed with small holes to increase the ion density to radical density ratio in the volume <part-num-ref name="volume">180.</part-num-ref>
303
+ Alternatively, the larger holes may be positioned in specific areas of the plate <part-num-ref name="plate">172</part-num-ref>
304
+ to contour the ion distribution in the volume <part-num-ref name="volume">180.</part-num-ref>
305
+ It is also contemplated that the holes are not perpendicular to the surface of the plate, i.e., they may be angled. </p>
306
+ <p id="p-34" num="34">
307
+ <confidence value="866866">[0028]</confidence>
308
+ The height at which the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
309
+ is supported may vary to further control the etch process. The closer the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
310
+ is located to the ceiling <part-num-ref name="ceiling">108,</part-num-ref>
311
+ the smaller the upper process volume <part-num-ref name="upper process volume">178.</part-num-ref>
312
+ A small upper process volume <part-num-ref name="small upper process volume">178</part-num-ref>
313
+ promotes a more stable plasma. In one embodiment, the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
314
+ is disposed approximately <part-num-ref name="is disposed approximately">1</part-num-ref>
315
+ inch (2.54 cm) from the ceiling <part-num-ref name="ceiling">108.</part-num-ref>
316
+ A faster etch rate may be obtained by locating the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
317
+ closer to the pedestal <part-num-ref name="pedestal">124</part-num-ref>
318
+ and, therefore, the substrate <boundary-data type="header">
319
+ <confidence value="8">8</confidence>
320
+ </boundary-data>
321
+ <boundary-data type="header">281630</boundary-data>
322
+ <page-break num="9"/>
323
+ <boundary-data type="header">PATENT</boundary-data>
324
+ <boundary-data type="header">7716 <confidence value="222222222222222222">ALRT/ETCHICONEIJB1</confidence>
325
+ </boundary-data>
326
+ <part-num-ref name="substrate">122.</part-num-ref>
327
+ Alternatively, a lower, but more controlled, etch rate may be obtained by locating the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
328
+ farther from the pedestal <part-num-ref name="pedestal">124.</part-num-ref>
329
+ In one embodiment, the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
330
+ is disposed approximately <part-num-ref name="is disposed approximately">2</part-num-ref>
331
+ inches from the pedestal <part-num-ref name="pedestal">124.</part-num-ref>
332
+ Alternatively, the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
333
+ may have a contoured shape to be closer to the ceiling <part-num-ref name="ceiling">108</part-num-ref>
334
+ in certain areas and farther in others, thereby shaping the upper volume <part-num-ref name="upper volume">178</part-num-ref>
335
+ of the process chamber <part-num-ref name="process chamber">102</part-num-ref>
336
+ in a desired manner to control the shape or contour of the plasma. </p>
337
+ <p id="p-35" num="35">[0029] To maintain the plate <part-num-ref name="plate">172</part-num-ref>
338
+ in a spaced-apart relationship with respect to the substrate <part-num-ref name="substrate">122,</part-num-ref>
339
+ the plate <part-num-ref name="plate">172</part-num-ref>
340
+ is supported by a plurality of legs <part-num-ref name="plurality of legs">176</part-num-ref>
341
+ disposed on the pedestal <part-num-ref name="pedestal">124.</part-num-ref>
342
+ The legs <part-num-ref name="legs">176</part-num-ref>
343
+ are generally located around an outer perimeter of the pedestal <part-num-ref name="pedestal">124</part-num-ref>
344
+ or the edge ring <part-num-ref name="edge ring">126</part-num-ref>
345
+ and may be fabricated of the same materials as the plate <part-num-ref name="plate">172.</part-num-ref>
346
+ In one embodiment, three legs <part-num-ref name="plate 172. In one embodiment, three legs">176</part-num-ref>
347
+ may be utilized to provide a stable support for the plasma stabilizer <part-num-ref name="plasma stabilizer">170.</part-num-ref>
348
+ The legs <part-num-ref name="legs">176</part-num-ref>
349
+ generally maintain the plate <part-num-ref name="plate">172</part-num-ref>
350
+ in a substantially parallel orientation with respect to the substrate <part-num-ref name="substrate">122</part-num-ref>
351
+ or pedestal <part-num-ref name="or pedestal">124.</part-num-ref>
352
+ However, it is contemplated that an angled orientation may be used by having legs <part-num-ref name="angled orientation may be used by having legs">176</part-num-ref>
353
+ of varied lengths. </p>
354
+ <p id="p-36" num="36">[0030] An upper end of the legs <part-num-ref name="legs">176</part-num-ref>
355
+ may be press fit into a corresponding hole formed in the plate <part-num-ref name="plate">172.</part-num-ref>
356
+ Alternatively, the upper end of the legs <part-num-ref name="legs">176</part-num-ref>
357
+ may be threaded into the plate <part-num-ref name="plate">172</part-num-ref>
358
+ or into a bracket secured to an underside of the plate <part-num-ref name="plate">172.</part-num-ref>
359
+ Other conventional fastening methods not inconsistent with processing conditions may also be used to secure the legs <part-num-ref name="legs">176</part-num-ref>
360
+ to the plate <part-num-ref name="plate">176.</part-num-ref>
361
+ </p>
362
+ <p id="p-37" num="37">[0031] The legs <part-num-ref name="legs">176</part-num-ref>
363
+ may rest on the pedestal <part-num-ref name="pedestal">124</part-num-ref>
364
+ or the edge ring <part-num-ref name="edge ring">126.</part-num-ref>
365
+ </p>
366
+ <p id="p-38" num="38">Alternatively, the legs <part-num-ref name="legs">176</part-num-ref>
367
+ may extend into a receiving hole (not shown) formed in the pedestal <part-num-ref name="pedestal">124</part-num-ref>
368
+ or edge ring <part-num-ref name="or edge ring">126.</part-num-ref>
369
+ Other fastening methods are also contemplated for securing the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
370
+ to the pedestal <part-num-ref name="pedestal">124</part-num-ref>
371
+ or edge ring <part-num-ref name="or edge ring">126,</part-num-ref>
372
+ such as by screwing, bolting, bonding, and the like. When secured to the edge ring <part-num-ref name="edge ring">126,</part-num-ref>
373
+ the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
374
+ may be part of an easily- replaceable process kit for ease of use, maintenance, replacement, and the like. </p>
375
+ <p id="p-39" num="39">It is contemplated that the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
376
+ may be configured to be easily retrofitted in existing process chambers. </p>
377
+ <boundary-data type="header">
378
+ <confidence value="8">9</confidence>
379
+ </boundary-data>
380
+ <boundary-data type="header">281630</boundary-data>
381
+ <boundary-data type="header">PATENT</boundary-data>
382
+ <boundary-data type="header">7716 ALRT<confidence value="5">/</confidence>
383
+ ETCH<confidence value="4">/</confidence>
384
+ CONE<confidence value="4885">/JB1</confidence>
385
+ </boundary-data>
386
+ <p id="p-40" num="40">
387
+ <page-break num="10"/>
388
+ [0032] Alternatively, the plate <part-num-ref name="plate">172</part-num-ref>
389
+ may be supported above the pedestal <part-num-ref name="pedestal">124</part-num-ref>
390
+ by other means such as by using a bracket (not shown) attached to the wall <part-num-ref name="wall">104</part-num-ref>
391
+ or other structure within the process chamber <part-num-ref name="process chamber">102</part-num-ref>
392
+ - as long as the plate <part-num-ref name="plate">172</part-num-ref>
393
+ is insulated from the ground path. </p>
394
+ <p id="p-41" num="41">[0033] Returning to Figure 1, one or more process gases are provided to the process chamber <part-num-ref name="process chamber">102</part-num-ref>
395
+ from a gas panel <part-num-ref name="gas panel">120.</part-num-ref>
396
+ The process gases are typically supplied through one or more inlets <part-num-ref name="process gases are typically supplied through one or more inlets">116</part-num-ref>
397
+ (e.g., openings, injectors, and the like) located above the substrate pedestal <part-num-ref name="substrate pedestal">124.</part-num-ref>
398
+ In the embodiment depicted in Figure 1, the process gases are provided to the inlets <part-num-ref name="inlets">116</part-num-ref>
399
+ using an annular gas channel <part-num-ref name="annular gas channel">118.</part-num-ref>
400
+ The gas channel <part-num-ref name="gas channel">118</part-num-ref>
401
+ may be formed in the wall <part-num-ref name="wall">104</part-num-ref>
402
+ or in gas rings (as shown) that are coupled to the wall <part-num-ref name="wall">104.</part-num-ref>
403
+ During an etch process, the process gases are ignited into a plasma by applying power from the plasma source <part-num-ref name="plasma source">112</part-num-ref>
404
+ to the antenna <part-num-ref name="antenna">110.</part-num-ref>
405
+ </p>
406
+ <p id="p-42" num="42">[0034] The pressure in the chamber <part-num-ref name="chamber">102</part-num-ref>
407
+ is controlled using a throttle valve <part-num-ref name="throttle valve">162</part-num-ref>
408
+ and a vacuum pump <part-num-ref name="vacuum pump">164.</part-num-ref>
409
+ The temperature of the wall <part-num-ref name="wall">104</part-num-ref>
410
+ may be controlled using liquid-containing conduits (not shown) that run through the wall <part-num-ref name="wall">104.</part-num-ref>
411
+ Typically, the chamber wall <part-num-ref name="chamber wall">104</part-num-ref>
412
+ is formed from a metal (e.g., aluminum, stainless steel, and the like) and is coupled to an electrical ground <part-num-ref name="electrical ground">106.</part-num-ref>
413
+ The process chamber <part-num-ref name="process chamber">102</part-num-ref>
414
+ also comprises conventional systems for process control, internal diagnostic, end point detection, and the like. Such systems are collectively shown as support systems <part-num-ref name="like. Such systems are collectively shown as support systems">154.</part-num-ref>
415
+ </p>
416
+ <p id="p-43" num="43">[0035] The controller <part-num-ref name="controller">146</part-num-ref>
417
+ comprises a central processing unit (CPU) <part-num-ref name="central processing unit (CPU)">644,</part-num-ref>
418
+ a memory <part-num-ref name="memory">148,</part-num-ref>
419
+ and support circuits <part-num-ref name="memory 148, and support circuits">152</part-num-ref>
420
+ for the CPU <part-num-ref name="CPU">150</part-num-ref>
421
+ and facilitates control of the components of the process chamber <part-num-ref name="process chamber">102</part-num-ref>
422
+ and, as such, of the etch process, as discussed below in further detail. The controller <part-num-ref name="controller">146</part-num-ref>
423
+ may be one of any form of general-purpose computer processor that can be used in an industrial setting for controlling various chambers and sub-processors. The memory, or computer-readable medium, <part-num-ref name="memory, or computer-readable medium,">642</part-num-ref>
424
+ of the CPU <part-num-ref name="CPU">150</part-num-ref>
425
+ may be one or more of readily available memory such as random access memory (RAM), read only memory (ROM), floppy disk, hard disk, or any other form of digital storage, local or remote. The support circuits <part-num-ref name="support circuits">152</part-num-ref>
426
+ are coupled to the CPU <part-num-ref name="CPU">150</part-num-ref>
427
+ for supporting the processor in a conventional manner. These circuits include cache, power <boundary-data type="header">
428
+ <confidence value="88">10</confidence>
429
+ </boundary-data>
430
+ <boundary-data type="header">281630</boundary-data>
431
+ <page-break num="11"/>
432
+ <boundary-data type="header">PATENT <confidence value="6">'</confidence>
433
+ </boundary-data>
434
+ <boundary-data type="header">7716 <confidence value="222222222222222222">ALRTIETCHICONE/JB1</confidence>
435
+ </boundary-data>
436
+ supplies, clock circuits, <confidence value="222222222222">input/output</confidence>
437
+ circuitry and subsystems, and the like. The inventive method is generally stored in the memory <part-num-ref name="memory">148</part-num-ref>
438
+ as a software routine. </p>
439
+ <p id="p-44" num="44">Alternatively, such software routine may also be stored and/or executed by a second CPU (not shown) that is remotely located from the hardware being controlled by the CPU <part-num-ref name="CPU">150.</part-num-ref>
440
+ </p>
441
+ <p id="p-45" num="45">
442
+ <confidence value="855866">[0036]</confidence>
443
+ One exemplary method 300 for using the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
444
+ to etch a layer of tungsten disposed on a substrate is depicted in the flow chart of Figure 3 and illustrated with respect to Figure 1. The method <part-num-ref name="method">300</part-num-ref>
445
+ begins at step <part-num-ref name="begins at step">302</part-num-ref>
446
+ where a substrate <part-num-ref name="substrate">122</part-num-ref>
447
+ is placed in a process chamber <part-num-ref name="process chamber">102</part-num-ref>
448
+ on a support pedestal <part-num-ref name="support pedestal">124</part-num-ref>
449
+ beneath a plasma stabilizer <part-num-ref name="plasma stabilizer">170.</part-num-ref>
450
+ The substrate <part-num-ref name="substrate">122</part-num-ref>
451
+ is generally a semiconductor substrate having an at least partially exposed layer of tungsten disposed thereon. A bias power of from about <part-num-ref name="bias power of from about">0</part-num-ref>
452
+ to about <part-num-ref name="to about">200</part-num-ref>
453
+ W may be applied by the bias power source <part-num-ref name="bias power source">140</part-num-ref>
454
+ to the electrostatic chuck <part-num-ref name="electrostatic chuck">160</part-num-ref>
455
+ to assist in retaining the substrate <part-num-ref name="substrate">124</part-num-ref>
456
+ in place on the pedestal <part-num-ref name="pedestal">124</part-num-ref>
457
+ during processing. In one embodiment, about <part-num-ref name="during processing. In one embodiment, about">50</part-num-ref>
458
+ W of bias power is applied. Although tungsten is described as one example of a material that can be beneficially etched using the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
459
+ of the present invention, other materials, especially metals, can also be beneficially etched using the stabilizer <part-num-ref name="stabilizer">170</part-num-ref>
460
+ and the quasi-remote plasma generated thereby. </p>
461
+ <p id="p-46" num="46">
462
+ <confidence value="855686">[0037]</confidence>
463
+ At step 304, a process gas is introduced into the process chamber <part-num-ref name="process chamber">102.</part-num-ref>
464
+ The process gas may be sulfur hexafluoride (SF<confidence value="5">6</confidence>
465
+ ) and may also include nitrogen (N<confidence value="5">2</confidence>
466
+ ). The SF<confidence value="5">6</confidence>
467
+ may be provided at a rate of from about <part-num-ref name="rate of from about">20</part-num-ref>
468
+ to about <part-num-ref name="to about">300</part-num-ref>
469
+ standard cubic centimeters per minute (sccm). In one embodiment, SF<confidence value="5">6</confidence>
470
+ is provided at a rate of about <part-num-ref name="rate of about">48</part-num-ref>
471
+ sccm. The N2 may be provided at a rate of from about <part-num-ref name="rate of from about">0</part-num-ref>
472
+ to about <part-num-ref name="to about">30</part-num-ref>
473
+ sccm. In one embodiment, the N<confidence value="5">2</confidence>
474
+ is provided at a rate of about <part-num-ref name="rate of about">12</part-num-ref>
475
+ sccm. Other suitable process gases for etching include chlorine (C<confidence value="5">l</confidence>
476
+ 2), nitrogen trifluoride (NF3), carbon tetrafluoride (CF4), hydrogen chloride (HC<confidence value="588">I),</confidence>
477
+ and the like. These process gases may be provided in similar ranges as the <confidence value="885">SF6</confidence>
478
+ and may also be part of a gaseous compound or introduced along with other process gases, such as N2. The pressure inside the process chamber <part-num-ref name="process chamber">102</part-num-ref>
479
+ is generally controlled to be within the range of from about <part-num-ref name="range of from about">3</part-num-ref>
480
+ to about <part-num-ref name="to about">50</part-num-ref>
481
+ <boundary-data type="header">
482
+ <confidence value="88">11</confidence>
483
+ </boundary-data>
484
+ <boundary-data type="header">281630</boundary-data>
485
+ <page-break num="12"/>
486
+ <boundary-data type="header">PATENT</boundary-data>
487
+ <boundary-data type="header">7716 <confidence value="222222222222222222">ALRTIETCHICONE/JB1</confidence>
488
+ </boundary-data>
489
+ mTorr. In one embodiment, the pressure inside the process chamber <part-num-ref name="process chamber">102</part-num-ref>
490
+ is controlled to be about <part-num-ref name="is controlled to be about">10</part-num-ref>
491
+ mTorr. </p>
492
+ <p id="p-47" num="47">[0038] At step 306, a plasma is formed in the chamber <part-num-ref name="chamber">102</part-num-ref>
493
+ by applying R<confidence value="5">F</confidence>
494
+ power from the plasma power source <part-num-ref name="plasma power source">112</part-num-ref>
495
+ to the antenna <part-num-ref name="antenna">110.</part-num-ref>
496
+ Power is typically provided in a range of from about <part-num-ref name="range of from about">100</part-num-ref>
497
+ to about <part-num-ref name="to about">1200</part-num-ref>
498
+ W. In one embodiment, RF power at a power level of about <part-num-ref name="power level of about">600</part-num-ref>
499
+ W is applied to the antenna <part-num-ref name="antenna">110</part-num-ref>
500
+ at a frequency of about 13.56 MHz. </p>
501
+ <p id="p-48" num="48">
502
+ <confidence value="5">[</confidence>
503
+ 0039] When the plasma is formed during step <part-num-ref name="plasma is formed during step">306,</part-num-ref>
504
+ the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
505
+ provides for a dense, stable plasma in the upper process volume <part-num-ref name="upper process volume">178.</part-num-ref>
506
+ Thus, enabling the substrate <part-num-ref name="substrate">122</part-num-ref>
507
+ to be etched at lower pressures and power requirements. Specifically, plasma stability measurements taken over a blanket tungsten substrate in etch chambers not containing the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
508
+ have revealed that, over a range of pressures of from about <part-num-ref name="range of pressures of from about">0</part-num-ref>
509
+ to about <part-num-ref name="to about">60</part-num-ref>
510
+ mTorr, RF power of about <part-num-ref name="mTorr, RF power of about">1500</part-num-ref>
511
+ W and higher was required to maintain a stable plasma. At pressures in the range of from about <part-num-ref name="range of from about">10</part-num-ref>
512
+ to about <part-num-ref name="to about">30</part-num-ref>
513
+ mTorr, significantly higher power was required to stabilize the plasma, and in some cases, the plasma was not able to be stabilized even at power levels in excess of <part-num-ref name="plasma was not able to be stabilized even at power levels in excess of">3000</part-num-ref>
514
+ W. A similar set of plasma stability measurements were taken in the same chamber, but with a plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
515
+ installed. Using the plasma stabilizer <part-num-ref name="plasma stabilizer">170,</part-num-ref>
516
+ the plasma was found to be stable over a range of pressures from about <part-num-ref name="range of pressures from about">0</part-num-ref>
517
+ to about <part-num-ref name="to about">60</part-num-ref>
518
+ mTorr at about <part-num-ref name="mTorr at about">500</part-num-ref>
519
+ W of RF power. Thus, use of the plasma stabilizer <part-num-ref name="plasma stabilizer">170</part-num-ref>
520
+ widens the process window, enabling etch processes at pressures and power levels previously unattainable. Furthermore, the more stable plasma, in combination with the control of the spatial distribution of the charged and neutral species in the upper and lower processing volumes <part-num-ref name="upper and lower processing volumes">178,</part-num-ref>
521
+ <part-num-ref name="upper and lower processing volumes 178,">180,</part-num-ref>
522
+ improves etch uniformity and selectivity. </p>
523
+ <p id="p-49" num="49">
524
+ <confidence value="86666">[0040</confidence>
525
+ ] For other plasma processing applications, by-products created by the processing of the substrate may detrimentally affect the process results. For example, when etching chrome using a chlorine and oxygen plasma, the chrome-oxy-ch<confidence value="5">l</confidence>
526
+ oride etch by-product generated by the substrate can become dissociated by the plasma, which then inhibits the etching process. In this application, use of the plasma stabilizer prevents the etch by-products from <boundary-data type="header">
527
+ <confidence value="88">12</confidence>
528
+ </boundary-data>
529
+ <boundary-data type="header">281630</boundary-data>
530
+ <page-break num="13"/>
531
+ <boundary-data type="header">PATENT</boundary-data>
532
+ <boundary-data type="header">7716 ALRT<confidence value="4">/</confidence>
533
+ ETCH<confidence value="5">/</confidence>
534
+ CONE<confidence value="4885">/JB1</confidence>
535
+ </boundary-data>
536
+ traveling to the region where the RF power is being deposited and thereby improves the uniformity and selectivity of the chrome etch process. </p>
537
+ <p id="p-50" num="50">[0041] Similar improvements in the stability and uniformity of other plasma processing applications such as CVD, PVD, gate nitridation, and plasma implant could be achieved by using a plasma stabilizer structure as described above.</p>
538
+ <p id="p-51" num="51">[0042] While the foregoing is directed to embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof, and the scope thereof is determined by the claims that follow.</p>
539
+ <boundary-data type="header">
540
+ <confidence value="88">13</confidence>
541
+ </boundary-data>
542
+ <boundary-data type="header">281630</boundary-data>
543
+ </description>
544
+ </us-patent-application>
545
+
prior_art/10897695.xml ADDED
@@ -0,0 +1,109 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>10897695</doc-number>
8
+ <date>2006-02-23</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <p id="p-1" num="1">02/23/2006 T<confidence value="66">HU</confidence>
14
+ 11:19 <confidence value="666">FAX</confidence>
15
+ 12489888363 Car<confidence value="5">l</confidence>
16
+ son, Gaskey &amp; O<confidence value="668">lds</confidence>
17
+ <confidence value="2">R</confidence>
18
+ 002/012<confidence value="5">.</confidence>
19
+ </p>
20
+ <p id="p-2" num="2">67186-001 81102812 </p>
21
+ <heading id="h-1">AMENDMENTS TO THE SPECIFICATION</heading>
22
+ <p id="p-3" num="3">Please replace paragraph [0013] on page 3, with the following rewritten paragraph:</p>
23
+ <p id="p-4" num="4">[0013] Figur<confidence value="5">e</confidence>
24
+ <confidence value="6">1</confidence>
25
+ is a block diagram illustrating components of a battery heater system <part-num-ref name="battery heater system">100</part-num-ref>
26
+ according to one embodiment of the invention. Generally, the invention is directed to a vehicle battery heater system <part-num-ref name="vehicle battery heater system">100</part-num-ref>
27
+ that is powered by an external power source <confidence value="22466">e-g.,</confidence>
28
+ <confidence value="45686">a1.20</confidence>
29
+ <confidence value="86">AG</confidence>
30
+ <confidence value="55855">power</confidence>
31
+ <confidence value="222222">zctutc</confidence>
32
+ <confidence value="2222222">cutzidz</confidence>
33
+ <confidence value="66211">thz-v</confidence>
34
+ <confidence value="2211888">Meffler</confidence>
35
+ <confidence value="6">a</confidence>
36
+ <confidence value="115514156646">izpplementAl</confidence>
37
+ <confidence value="22222222">lwoltage</confidence>
38
+ b<confidence value="888778">attery</confidence>
39
+ <confidence value="66">on</confidence>
40
+ <confidence value="62522">board</confidence>
41
+ <confidence value="2">t</confidence>
42
+ <confidence value="22222222222252">vehiele)(e.g.,</confidence>
43
+ a 12<confidence value="66">0V</confidence>
44
+ AC power source outside the vehicle or a supplemen<confidence value="8">t</confidence>
45
+ al low-volta<confidence value="58">ge</confidence>
46
+ <confidence value="66">or</confidence>
47
+ acce<confidence value="8">s</confidence>
48
+ so<confidence value="8">r</confidence>
49
+ y battery on-board the vehicle<confidence value="5">)</confidence>
50
+ outside a high-voltage battery system <part-num-ref name="high-voltage battery system">102</part-num-ref>
51
+ or other electrical storage device. The battery system <part-num-ref name="battery system">102</part-num-ref>
52
+ includes on<confidence value="5">e</confidence>
53
+ or more battery <confidence value="8888">cell</confidence>
54
+ s <part-num-ref name="includes one or more battery cells">103.</part-num-ref>
55
+ By using an external power source that is separate from the high-voltage battery system <part-num-ref name="high-voltage battery system">102</part-num-ref>
56
+ to operate the heater system <part-num-ref name="heater system">100,</part-num-ref>
57
+ the invention can keep the battery system <part-num-ref name="battery system">102</part-num-ref>
58
+ warm and regulate the temperature of the battery system <part-num-ref name="battery system">102</part-num-ref>
59
+ reliably when the vehicle is exposed to a cold environment<confidence value="5">.</confidence>
60
+ </p>
61
+ <p id="p-5" num="5">Please replace paragraph [0016] on page 4, with the <confidence value="8">f</confidence>
62
+ ollowing rewritten paragraph: </p>
63
+ <p id="p-6" num="6">[0016] Alternatively, the controller <part-num-ref name="controller">114</part-num-ref>
64
+ may be powered by, for example, a separate low- voltag<confidence value="5">e</confidence>
65
+ battery <part-num-ref name="separate low- voltage battery">120,</part-num-ref>
66
+ the battery cells <part-num-ref name="battery cells">103</part-num-ref>
67
+ <confidence value="66">of</confidence>
68
+ <confidence value="6">a</confidence>
69
+ traction <confidence value="22222222222222">battertemseves</confidence>
70
+ , or other alternative power source. The low-voltage battery <part-num-ref name="low-voltage battery">120</part-num-ref>
71
+ may be, for example, a conventional accessory battery having a nominal voltage output of approximately 1<confidence value="5">O</confidence>
72
+ V-15V. If the controll<confidence value="8">e</confidence>
73
+ r <part-num-ref name="controller">114</part-num-ref>
74
+ is powered by the low-voltag<confidence value="5">e</confidence>
75
+ battery <part-num-ref name="low-voltage battery">120,</part-num-ref>
76
+ the controller <part-num-ref name="controller">114</part-num-ref>
77
+ can monitor the temperature of the battery system <part-num-ref name="battery system">102</part-num-ref>
78
+ even when the battery heater system <part-num-ref name="battery heater system">100</part-num-ref>
79
+ is not connected to the AC power source <part-num-ref name="AC power source">110.</part-num-ref>
80
+ The controller <part-num-ref name="controller">114</part-num-ref>
81
+ preferably draws a very small current during operation (e.g., on the order of less than <part-num-ref name="order of less than">1</part-num-ref>
82
+ mA). Moreover, by intermittently placing the controller <part-num-ref name="controller">114</part-num-ref>
83
+ into a sleep mode where it draws minimal current, as will be described in greater below, the controller <part-num-ref name="controller">114</part-num-ref>
84
+ avoids draining the low-voltage battery <part-num-ref name="low-voltage battery">120.</part-num-ref>
85
+ Note that the controller <part-num-ref name="controller">114</part-num-ref>
86
+ may also be powered by different sources during different modes of operation, if desired. The components of the heater system <part-num-ref name="heater system">100</part-num-ref>
87
+ may be connected together via any connection structure, such as an electrical <confidence value="8">h</confidence>
88
+ arness (not shown). </p>
89
+ <p id="p-7" num="7">
90
+ <confidence value="8">2</confidence>
91
+ PAGE 2<confidence value="882">12*</confidence>
92
+ RCVD AT 2<confidence value="1884">f231</confidence>
93
+ 200<confidence value="5">6</confidence>
94
+ 11:15:09 <confidence value="88">AM</confidence>
95
+ <confidence value="5">(</confidence>
96
+ Easte<confidence value="66">rn</confidence>
97
+ Standard Time<confidence value="55">]'</confidence>
98
+ <confidence value="85">SV</confidence>
99
+ R:USPT<confidence value="56668828884">OEFXRF.522'</confidence>
100
+ DNIS:27383<confidence value="882">00*</confidence>
101
+ CS<confidence value="4">I</confidence>
102
+ D:124898<confidence value="558588">88363'</confidence>
103
+ DURA<confidence value="6668">TION</confidence>
104
+ (mm<confidence value="65">.s</confidence>
105
+ s):03<confidence value="288">-10</confidence>
106
+ </p>
107
+ </description>
108
+ </us-patent-application>
109
+
prior_art/10903798.xml ADDED
@@ -0,0 +1,19 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <pat:SpecificationDocument xmlns:ent="urn:us:gov:doc:uspto:enterprise" xmlns:pat="urn:us:gov:doc:uspto:patent" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XML_SCHEMAS/V1_3/SpecificationDocument_1_0.xsd" pat:instanceFileName="10903798.2009-11-10.G1YVJJ1VPPOPPY3.SPEC.xml" pat:id="ID-10903798.2009-11-10.G1YVJJ1VPPOPPY3.SPEC" >
3
+ <pat:DocumentCode>SPEC</pat:DocumentCode>
4
+ <pat:DocumentHeaderDetails pat:id="ID-00001">
5
+ <pat:ApplicationHeaderDetails>
6
+ <pat:ApplicationNumber>10903798</pat:ApplicationNumber>
7
+ </pat:ApplicationHeaderDetails>
8
+ <pat:PageTotalQuantity>1</pat:PageTotalQuantity>
9
+ <pat:ParagraphTotalQuantity>4</pat:ParagraphTotalQuantity>
10
+ </pat:DocumentHeaderDetails>
11
+ <pat:MailRoomDate>2009-11-10</pat:MailRoomDate>
12
+ <pat:Specification>
13
+ <?PageStart number='1' fileName='' filePathName=''?>
14
+ <pat:BoundaryData><pat:HeaderText>Serial No. 10/903,798</pat:HeaderText></pat:BoundaryData><pat:P pat:id="p-1" pat:pNumber="1">Amendments to the Specification:</pat:P>
15
+ <pat:P pat:id="p-2" pat:pNumber="2">Page 1, lines 6 to 8 replace with the following.</pat:P>
16
+ <pat:P pat:id="p-3" pat:pNumber="3">- This application is the U.S. National Stage of <pat:PartName pat:idref="PN-00001">PCT/U<pat:OCRConfidenceData pat:levelNumber="4">S</pat:OCRConfidenceData>03/04468, filed</pat:PartName> <pat:PartNumber pat:id="PN-00001">14</pat:PartNumber> <pat:PartName pat:idref="PN-00002">February</pat:PartName> <pat:PartNumber pat:id="PN-00002">2003,</pat:PartNumber> which claims the benefit of <pat:PartName pat:idref="PN-00003">claims priority under</pat:PartName> <pat:PartNumber pat:id="PN-00003">35</pat:PartNumber> U.S.C. 365(c) to U.S. Provisional Application No.</pat:P>
17
+ <pat:P pat:id="p-4" pat:pNumber="4">60/357,170, filed 14 <pat:PartName pat:idref="PN-00004">February</pat:PartName> <pat:PartNumber pat:id="PN-00004">2002.</pat:PartNumber> - <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="888">-2-</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData></pat:P>
18
+ </pat:Specification>
19
+ </pat:SpecificationDocument>
prior_art/10911159.xml ADDED
@@ -0,0 +1,112 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>10911159</doc-number>
8
+ <date>2007-04-12</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <p id="p-1" num="1">
14
+ <confidence value="8">1</confidence>
15
+ 2. Apr. 2007 14:34 PEARL COHEN ZEDEK LATZER No. <part-num-ref name="14:34 PEARL COHEN ZEDEK LATZER No.">3396</part-num-ref>
16
+ P. 4/2<confidence value="5">8</confidence>
17
+ APPLICAN<confidence value="788">TSS</confidence>
18
+ : SUTSKOVER, <confidence value="5">l</confidence>
19
+ an et a<confidence value="55">l.</confidence>
20
+ </p>
21
+ <p id="p-2" num="2">
22
+ <confidence value="86">SF</confidence>
23
+ RIAL NO.: 10/911,<confidence value="588">159</confidence>
24
+ <confidence value="68">FT</confidence>
25
+ LED: A<confidence value="86">ug</confidence>
26
+ ust 2, <confidence value="8668">2004</confidence>
27
+ Page <part-num-ref name="Page">
28
+ <confidence value="8">2</confidence>
29
+ </part-num-ref>
30
+ AMENDMENTS TO T<confidence value="4">I</confidence>
31
+ E SPEC<confidence value="255688468">fFICATION</confidence>
32
+ <confidence value="2">'</confidence>
33
+ In the Abstr<confidence value="4">a</confidence>
34
+ ct: </p>
35
+ <p id="p-3" num="3">Pl<confidence value="8">e</confidence>
36
+ as<confidence value="8">e</confidence>
37
+ replace the Abstract wit<confidence value="8">h</confidence>
38
+ the following Abstract: </p>
39
+ <p id="p-4" num="4">
40
+ <confidence value="888">--T</confidence>
41
+ he present invention <confidence value="8">p</confidence>
42
+ rovides [[M<confidence value="44">]l</confidence>
43
+ <confidence value="8">m</confidence>
44
+ ethod and apparatus to perform channel estimation for a wireless communication system <confidence value="656656524">are-deser</confidence>
45
+ <confidence value="5">,</confidence>
46
+ the method <confidence value="22222222">corising</confidence>
47
+ : receiving a first preamble on a periodic basis<confidence value="5">,</confidence>
48
+ the first preamble having a first set of pil<confidence value="8">o</confidence>
49
+ t tones <confidence value="8">c</confidence>
50
+ orrespondin<confidence value="8">g</confidence>
51
+ <confidence value="22">to</confidence>
52
+ <confidence value="8">a</confidence>
53
+ <confidence value="8">f</confidence>
54
+ irst set of fr<confidence value="88">eq</confidence>
55
+ uenc<confidence value="8">y</confidence>
56
+ bands from a first su<confidence value="8">b</confidence>
57
+ scrib<confidence value="8">e</confidence>
58
+ r st<confidence value="78777">ation</confidence>
59
+ <confidence value="6">o</confidence>
60
+ f a <confidence value="8">p</confidence>
61
+ lurality of subscriber <confidence value="8">s</confidence>
62
+ tations over an <confidence value="2222222222">orthogonal</confidence>
63
+ fre<confidence value="8">q</confidence>
64
+ u<confidence value="8">e</confidence>
65
+ nc<confidence value="8">y</confidence>
66
+ division multiple ac<confidence value="8">c</confidence>
67
+ ess <confidence value="686">air</confidence>
68
+ in<confidence value="78878876">terface:</confidence>
69
+ estimatin<confidence value="8">g</confidence>
70
+ a first chann<confidence value="8">e</confidence>
71
+ l estimate parameter for each o<confidence value="5">f</confidence>
72
+ the first <confidence value="52">se</confidence>
73
+ <confidence value="2">o</confidence>
74
+ f fre<confidence value="8">q</confidence>
75
+ uenc<confidence value="8">y</confidence>
76
+ bands usin<confidence value="8">g</confidence>
77
+ the <confidence value="8">c</confidence>
78
+ orr<confidence value="8">e</confidence>
79
+ spond<confidence value="8">i</confidence>
80
+ ng first set of <confidence value="8">p</confidence>
81
+ ilot tones<confidence value="5">;</confidence>
82
+ estimating a second <confidence value="8">c</confidence>
83
+ hannel estimate parameter for each of the first set of fre<confidence value="8">q</confidence>
84
+ uenc<confidence value="8">y</confidence>
85
+ bands using the first channel estimate parameters<confidence value="5">:</confidence>
86
+ and <confidence value="2222222">assmin"</confidence>
87
+ the first set of fre<confidence value="8">q</confidence>
88
+ uency bands to the plurality of subsc<confidence value="8">r</confidence>
89
+ iber stations in accordance with the second cha<confidence value="8">n</confidence>
90
+ nel estimate para<confidence value="5">m</confidence>
91
+ ete<confidence value="65885">rs.--</confidence>
92
+ PAGE <part-num-ref name="second channel estimate parameters.-- PAGE">4128<confidence value="2">2</confidence>
93
+ </part-num-ref>
94
+ <confidence value="885">RCV</confidence>
95
+ D AT <part-num-ref name="RCVD AT">4112<confidence value="5885">1200</confidence>
96
+ 7 </part-num-ref>
97
+ 8:38:48 AM <confidence value="5">[</confidence>
98
+ Easte<confidence value="66">rn</confidence>
99
+ Daylight <confidence value="66668">Time'</confidence>
100
+ SVR:U<confidence value="4">S</confidence>
101
+ PTO<confidence value="5885882844">.EFXRF-2l'</confidence>
102
+ DNIS<confidence value="5">:</confidence>
103
+ 273830<confidence value="52">0'</confidence>
104
+ CSID<confidence value="5">:</confidence>
105
+ 646417551<confidence value="66">1'</confidence>
106
+ DURAT<confidence value="66">IO</confidence>
107
+ N (mm<confidence value="5">.</confidence>
108
+ ss):0<confidence value="4688">7.44</confidence>
109
+ </p>
110
+ </description>
111
+ </us-patent-application>
112
+
prior_art/10922650.xml ADDED
The diff for this file is too large to render. See raw diff
 
prior_art/10926801.xml ADDED
@@ -0,0 +1,627 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>10926801</doc-number>
8
+ <date>2004-08-26</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <heading id="h-1">APPARATUS AND METHODS FOR APPLYING IMAGES TO A SURFACE</heading>
14
+ <heading id="h-2">INVENTORS</heading>
15
+ <p id="p-1" num="1">Richard W. Baird Glenn R. Dalby and William J. <confidence value="22222">Postl</confidence>
16
+ </p>
17
+ <heading id="h-3">FIELD OF THE INVENTION</heading>
18
+ <p id="p-2" num="2">[0001] This invention relates generally to the application of graphic images, and, more specifically, to systems and methods for applying graphic images to a surface.</p>
19
+ <heading id="h-4">BACKGROUND OF THE INVENTION</heading>
20
+ <p id="p-3" num="3">[0002<confidence value="5">]</confidence>
21
+ In various commercial products, it is desirable to impart colorful visual effects through the application of a pigmented formulation to a surface to form an aesthetically appealing image. The image may be applied to the surface by various methods, including applying a paint material to the surface by means of a brush or an aerosol spray. </p>
22
+ <p id="p-4" num="4">Alternately, other methods may be used that avoid painting processes altogether. For example, an appliqu<confidence value="8">e</confidence>
23
+ or a decal having the desired image formed thereon may be adhered to the surface. </p>
24
+ <boundary-data type="header">
25
+ <confidence value="6">-</confidence>
26
+ <confidence value="2">1</confidence>
27
+ <confidence value="6">-</confidence>
28
+ BLACK L<confidence value="45">oW</confidence>
29
+ E &amp; GRAHAM </boundary-data>
30
+ <p id="p-5" num="5">
31
+ <boundary-data type="line-number">46020</boundary-data>
32
+ <boundary-data type="header">CUSTOMER <confidence value="666866">NUMBER</confidence>
33
+ <confidence value="8156858558566">BlNG-1-1095AP</confidence>
34
+ 701 Fifth Avenue, Suite 4800 </boundary-data>
35
+ <boundary-data type="header">
36
+ <confidence value="222222">Seatde</confidence>
37
+ , Washington 98104 </boundary-data>
38
+ 206.381.3300 <confidence value="2">-</confidence>
39
+ F: 206.381.3301 <page-break num="2"/>
40
+ [0003] The foregoing conventional methods have been widely used to apply images to an exterior portion of an aircraft. For example, images may be applied to wing, fuselage and tail surfaces of the aircraft for decorative <confidence value="222222">and/or</confidence>
41
+ functional purposes. Since the images are typically large and often detailed, skilled personnel are required to paint or adhere an image to an exterior portion of the aircraft. Consequently, the production cost of an aircraft is increased due to the additional labor cost associated with painting or adhering an image to the exterior portion of the aircraft. </p>
42
+ <p id="p-6" num="6">[0004] Other shortcomings stem from the foregoing processes, which will now be described in detail.<confidence value="5">.</confidence>
43
+ FIGURE 1 is a partial cross-sectional view of an external portion <part-num-ref name="external portion">10</part-num-ref>
44
+ of an aircraft having a painted image applied thereon, according to the prior art. The external portion <part-num-ref name="external portion">10</part-num-ref>
45
+ includes a supporting surface <part-num-ref name="supporting surface">12,</part-num-ref>
46
+ which is typically a structural portion of the aircraft, such as a fuselage panel, a wing panel, or other external surfaces of the aircraft, and a plurality of paint layers <part-num-ref name="plurality of paint layers">14</part-num-ref>
47
+ that are applied to the supporting surface <part-num-ref name="supporting surface">12.</part-num-ref>
48
+ The paint layers <part-num-ref name="paint layers">14</part-num-ref>
49
+ may include a primer layer <part-num-ref name="primer layer">16,</part-num-ref>
50
+ a base color layer <part-num-ref name="base color layer">18,</part-num-ref>
51
+ and a plurality of decorative color layers <part-num-ref name="plurality of decorative color layers">20</part-num-ref>
52
+ that collectively form the painted image on the external portion <part-num-ref name="external portion">10.</part-num-ref>
53
+ </p>
54
+ <p id="p-7" num="7">[0005] One significant shortcoming present in this method is that the paint layers <part-num-ref name="paint layers">14</part-num-ref>
55
+ are generally successively applied to the supporting surface <part-num-ref name="supporting surface">12,</part-num-ref>
56
+ so that a time-consuming drying period is required between successive paint applications, thus increasing the production time for the aircraft. Further, the application of the decorative color layers <part-num-ref name="decorative color layers">20</part-num-ref>
57
+ additionally requires the application of paint masking devices such as stencils, or tape between successive applications of the layers <part-num-ref name="layers">20,</part-num-ref>
58
+ which requires still more time and labor. </p>
59
+ <p id="p-8" num="8">Since spray application devices may only apply a single color portion of the image, the spray application device must be cleaned numerous times before image is complete, thus requiring still more time and labor.</p>
60
+ <p id="p-9" num="9">[0006<confidence value="5">]</confidence>
61
+ Still other shortcomings are inherent in the image itself when the image is applied by the foregoing method. For example, the application of the decorative color layers <part-num-ref name="decorative color layers">20</part-num-ref>
62
+ generally results in an external surface <part-num-ref name="external surface">22</part-num-ref>
63
+ having surface irregularities <part-num-ref name="having surface irregularities">24.</part-num-ref>
64
+ Since the external surface <part-num-ref name="external surface">22</part-num-ref>
65
+ is exposed to a slipstream while the aircraft is in flight, the surface irregularities <part-num-ref name="surface irregularities">24</part-num-ref>
66
+ generate additional surface drag o<confidence value="5">n</confidence>
67
+ the aircraft that results in increased fuel <confidence value="88">-2</confidence>
68
+ - BLACK LOWE &amp; GRAHAM <part-num-ref name="aircraft that results in increased fuel -2- BLACK LOWE &amp; GRAHAM">46020</part-num-ref>
69
+ <boundary-data type="header">CUSTOMER <confidence value="666666">NUMBER</confidence>
70
+ <confidence value="82">BI</confidence>
71
+ NG-<confidence value="5855865">1-1095A</confidence>
72
+ P 701 Fifth Avenue, Suite 4800 </boundary-data>
73
+ <boundary-data type="header">
74
+ <confidence value="222222">Seatle</confidence>
75
+ , Washington 98104 </boundary-data>
76
+ 206.381.3300 <confidence value="2">-</confidence>
77
+ F: 206.381.3301 <page-break num="3"/>
78
+ consumption for the aircraft. Although appliques, such as decals and other similar preformed images have been widely used for applying images to aircraft, and generally present a smooth external surface to the slipstream, appliqu<confidence value="8">e</confidence>
79
+ s are susceptible to premature degradation through prolonged exposure to ultraviolet radiation that results in fading and/or discoloration of the image. In addition, appliques may partially detach from the aircraft surface, particularly along exposed edges of the appliqu<confidence value="8">e</confidence>
80
+ , so that maintenance costs for the aircraft are increased. </p>
81
+ <p id="p-10" num="10">
82
+ <confidence value="5">[</confidence>
83
+ 0007<confidence value="5">]</confidence>
84
+ Therefore, there is an unmet need in the art for systems and methods for forming an image on an aircraft exterior that results in lower production and maintenance costs, while providing an image that is generally superior to those currently produced. </p>
85
+ <heading id="h-5">SUMMARY OF THE INVENTION</heading>
86
+ <p id="p-11" num="11">
87
+ <confidence value="5">[</confidence>
88
+ 0008<confidence value="5">]</confidence>
89
+ The present invention discloses systems and methods for applying graphic images to a surface. In one aspect, a system includes an applicator to direct a droplet pattern of a pigmented ink towards the surface, an motivating device coupled to the applicator to move the applicator in at least one transverse direction relative to the surface and also in a direction perpendicular to the surface, and a controller coupled to the motivating device that is configured to receive data corresponding to the graphics image and to control at least the motion of the motivating device to apply the graphic image to the surface. In another aspect, a method includes receiving an image file from an image source and generating a surface model that describes geometrical contours of the surface. An applicator is then controlled according to the surface model, and the graphic image is applied that corresponds to the image file. </p>
90
+ <heading id="h-6">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
91
+ <p id="p-12" num="12">
92
+ <confidence value="5">[</confidence>
93
+ 0009<confidence value="5">]</confidence>
94
+ The preferred and alternative embodiments of the present invention are described in detail below with reference to the following drawings. </p>
95
+ <p id="p-13" num="13">
96
+ <confidence value="5">[</confidence>
97
+ 0010<confidence value="5">]</confidence>
98
+ FIGURE <confidence value="5">1</confidence>
99
+ is a partial cross-sectional view of an external portion of an aircraft having a painted image applied thereon, according to the prior art; </p>
100
+ <boundary-data type="header">
101
+ <confidence value="585">-3-</confidence>
102
+ BLACK LOWE &amp; GR<confidence value="8">A</confidence>
103
+ HAM<confidence value="1">"</confidence>
104
+ </boundary-data>
105
+ <heading id="h-7">
106
+ <confidence value="2">_</confidence>
107
+ </heading>
108
+ <boundary-data type="header">
109
+ <confidence value="888">CUS</confidence>
110
+ TOMER <confidence value="6666666556565566">NUMBERBIN-1-1095</confidence>
111
+ 701 Fifth Avenue, Suite 4800 </boundary-data>
112
+ <boundary-data type="header">Seatt<confidence value="8">l</confidence>
113
+ e, Washington 98104 </boundary-data>
114
+ <p id="p-14" num="14">
115
+ <boundary-data type="line-number">46020 </boundary-data>
116
+ 206.381.3300 <confidence value="2">-</confidence>
117
+ F: 206.381.3301 <page-break num="4"/>
118
+ [0011<confidence value="5">]</confidence>
119
+ FIGURE 2 is a block diagrammatic view of a system for applying a graphic image to a surface according to an embodiment of the invention; </p>
120
+ <p id="p-15" num="15">
121
+ <confidence value="5">[</confidence>
122
+ 0012<confidence value="5">]</confidence>
123
+ FIGURE 3 is an isometric view of an actuator according to another embodiment of the invention, which may be used with the system of FIGURE 2; </p>
124
+ <p id="p-16" num="16">[0013] FIGURE 4 is a schematic view of an applicator supply system according to still another embodiment of the invention that may be used with the system of FIGURE 2;</p>
125
+ <p id="p-17" num="17">[0014] FIGURE 5 is a plan view of an applicator head according to still another embodiment of the invention that may form a portion of the applicator of FIGURE 2;</p>
126
+ <p id="p-18" num="18">[0015] FIGURE 6 is a block diagrammatic view of a controller according to still another embodiment of the invention that may be used with the system of FIGURE 2;</p>
127
+ <p id="p-19" num="19">[0016] FIGURE 7 is a partial cross-sectional view of an external portion of an aircraft that will be used to describe a method of applying an image to an aircraft according to another embodiment of the invention; and [0017] FIGURE 8 is a side elevation view of an aircraft having at least one graphic image according to an embodiment of the invention.</p>
128
+ <heading id="h-8">DETAILED DESCRIPTION OF THE INVENTION</heading>
129
+ <p id="p-20" num="20">[0018] The present invention relates to the application of images to a surface and, more specifically, to systems and methods for applying decorative images to an aircraft surface. Many specific details of certain embodiments of the invention are set forth in the following description and in FIGURES <part-num-ref name="following description and in FIGURES">2</part-num-ref>
130
+ through <part-num-ref name="through">8</part-num-ref>
131
+ to provide a thorough understanding of such embodiments. One skilled in the art, however, will understand that the present invention may have additional embodiments, or that the present invention may be practiced without several of the details described in the following description. </p>
132
+ <p id="p-21" num="21">[0019] FIGURE 2 is a block diagrammatic view of a system <part-num-ref name="system">30</part-num-ref>
133
+ for applying a graphic image to a surface according to an embodiment of the invention. The system <part-num-ref name="system">30</part-num-ref>
134
+ includes an applicator <part-num-ref name="applicator">32</part-num-ref>
135
+ operable to apply pigmented formulations such as inks of various colors to a surface <part-num-ref name="surface">34.</part-num-ref>
136
+ The applicator <part-num-ref name="applicator">32</part-num-ref>
137
+ will be described in greater detail below. The applicator <part-num-ref name="applicator">32</part-num-ref>
138
+ is coupled to an actuator (or other suitable motivating device) <part-num-ref name="actuator (or other suitable motivating device)">36</part-num-ref>
139
+ that is <confidence value="2222556">6020-4-</confidence>
140
+ BLACK LOWE &amp; GRAHAM <boundary-data type="line-number">46020</boundary-data>
141
+ <boundary-data type="header">CUSTOMER <confidence value="666866">NUMBER</confidence>
142
+ <confidence value="82868285585">B[NG-1-1095</confidence>
143
+ AP 701 Fifth Avenue, Su<confidence value="66">it</confidence>
144
+ e 4800 </boundary-data>
145
+ <boundary-data type="header">Seattle, Washington 98104</boundary-data>
146
+ <confidence value="424">2nR</confidence>
147
+ <confidence value="145">1Ai</confidence>
148
+ <confidence value="2166">;;nn</confidence>
149
+ <confidence value="1">*</confidence>
150
+ <confidence value="8">.</confidence>
151
+ <part-num-ref name="that is 6020-4- BLACK LOWE &amp; GRAHAM 2nR 1Ai ;;nn * .">
152
+ <confidence value="24">62</confidence>
153
+ </part-num-ref>
154
+ <confidence value="42">li</confidence>
155
+ <confidence value="242">mAn</confidence>
156
+ <page-break num="5"/>
157
+ configured to move the applicator <part-num-ref name="applicator">32</part-num-ref>
158
+ in a transverse direction relative to the surface <part-num-ref name="surface">34</part-num-ref>
159
+ by moving the applicator <part-num-ref name="applicator">32</part-num-ref>
160
+ in an x-direction and a y-direction. The actuator <part-num-ref name="actuator">36</part-num-ref>
161
+ may also move the applicator <part-num-ref name="applicator">32</part-num-ref>
162
+ in a perpendicular direction relative to the surface <part-num-ref name="surface">34</part-num-ref>
163
+ by moving the applicator <part-num-ref name="applicator">32</part-num-ref>
164
+ in a z-direction. The actuator <part-num-ref name="actuator">36</part-num-ref>
165
+ may comprise any positioning device operable to receive positioning instructions and configured to position the applicator <part-num-ref name="applicator">32</part-num-ref>
166
+ in the instructed position. In one specific embodiment, the actuator is a programmable manipulator such as robotic device capable of at least three-axis motion. In another embodiment, the actuator <part-num-ref name="actuator">36</part-num-ref>
167
+ comprises a three-axis translational device that will also be described in further detail below. The actuator <part-num-ref name="actuator">36</part-num-ref>
168
+ is coupled to a controller <part-num-ref name="controller">38</part-num-ref>
169
+ operable to receive image information <part-num-ref name="operable to receive image information">40</part-num-ref>
170
+ and control the motion of the actuator <part-num-ref name="actuator">36.</part-num-ref>
171
+ The controller <part-num-ref name="controller">38</part-num-ref>
172
+ is also operable to control an applicator supply system <part-num-ref name="applicator supply system">42</part-num-ref>
173
+ that supplies a liquid pigmented material to the applicator <part-num-ref name="applicator">32.</part-num-ref>
174
+ The applicator supply system <part-num-ref name="applicator supply system">42</part-num-ref>
175
+ will be described in further detail below. </p>
176
+ <p id="p-22" num="22">The controller 38 is further coupled to the applicator <part-num-ref name="applicator">32</part-num-ref>
177
+ in order to control the operation of the applicator <part-num-ref name="applicator">32,</part-num-ref>
178
+ as will also be described in detail below. </p>
179
+ <p id="p-23" num="23">
180
+ <confidence value="5">[</confidence>
181
+ 0020<confidence value="4">]</confidence>
182
+ FIGURE 3 is an isometric view of an actuator <part-num-ref name="actuator">50</part-num-ref>
183
+ according to another embodiment of the invention, which may be used with the system <part-num-ref name="system">30</part-num-ref>
184
+ of FIGURE 2. The actuator <part-num-ref name="actuator">50</part-num-ref>
185
+ includes a first frame <part-num-ref name="first frame">52</part-num-ref>
186
+ and a second frame <part-num-ref name="second frame">54</part-num-ref>
187
+ that is coupled to the first frame <part-num-ref name="first frame">52</part-num-ref>
188
+ to form a rigid unitary structure. The first frame <part-num-ref name="first frame">52</part-num-ref>
189
+ is spaced apart from the second frame <part-num-ref name="second frame">54</part-num-ref>
190
+ to permit a fin portion <part-num-ref name="fin portion">56</part-num-ref>
191
+ of an aircraft enpennage to be interposed between the first frame <part-num-ref name="first frame">52</part-num-ref>
192
+ and the second frame <part-num-ref name="second frame">54.</part-num-ref>
193
+ The actuator <part-num-ref name="actuator">50</part-num-ref>
194
+ is further configured to rest on a support platform <part-num-ref name="support platform">58</part-num-ref>
195
+ adjacent to the fin portion <part-num-ref name="fin portion">56.</part-num-ref>
196
+ In this embodiment, the actuator <part-num-ref name="actuator">50</part-num-ref>
197
+ also includes vacuum retainers <part-num-ref name="also includes vacuum retainers">60</part-num-ref>
198
+ configured to retain the actuator <part-num-ref name="actuator">50</part-num-ref>
199
+ in a fixed position relative to the fin portion <part-num-ref name="fin portion">56.</part-num-ref>
200
+ In particular, the vacuum retainers <part-num-ref name="vacuum retainers">60</part-num-ref>
201
+ are configured to hold the actuator <part-num-ref name="actuator">50</part-num-ref>
202
+ in proper registration with an image <part-num-ref name="image">62</part-num-ref>
203
+ formed on the fin portion <part-num-ref name="fin portion">56</part-num-ref>
204
+ by the applicator <part-num-ref name="applicator">32.</part-num-ref>
205
+ The vacuum retainers <part-num-ref name="vacuum retainers">60</part-num-ref>
206
+ form an enclosed volume when the retainers <part-num-ref name="retainers">60</part-num-ref>
207
+ are moved into a sealable relationship with the fin portion <part-num-ref name="fin portion">56,</part-num-ref>
208
+ which is evacuated by a vacuum pump (not shown in FIGURE 3) <confidence value="66">in</confidence>
209
+ order to restrain relative movement between the actuator <part-num-ref name="actuator">50</part-num-ref>
210
+ and the fin portion <part-num-ref name="fin portion">56.</part-num-ref>
211
+ </p>
212
+ <boundary-data type="header">
213
+ <confidence value="5">-</confidence>
214
+ <confidence value="5">5</confidence>
215
+ <confidence value="6">-</confidence>
216
+ BLA<confidence value="8">C</confidence>
217
+ K L<confidence value="56">ow</confidence>
218
+ E &amp; GRAHAM <confidence value="5">-</confidence>
219
+ </boundary-data>
220
+ <p id="p-24" num="24">
221
+ <boundary-data type="line-number">46020</boundary-data>
222
+ <boundary-data type="header">
223
+ <confidence value="666">CUS</confidence>
224
+ TOMER <confidence value="5">N</confidence>
225
+ UMBER B<confidence value="5686515585">ING--I1095</confidence>
226
+ AP 701 Fifth Avenue, Su<confidence value="65">it</confidence>
227
+ e 4800 </boundary-data>
228
+ <boundary-data type="header">
229
+ <confidence value="222222">Seatle</confidence>
230
+ , Washington 98104 </boundary-data>
231
+ <confidence value="211">')n</confidence>
232
+ (, <confidence value="1111">ISR1</confidence>
233
+ <confidence value="14111">;anfl</confidence>
234
+ <confidence value="18">*.</confidence>
235
+ <confidence value="111">P-l</confidence>
236
+ <confidence value="212">')4</confidence>
237
+ R1 <confidence value="11111">3,fl1</confidence>
238
+ <page-break num="6"/>
239
+ <confidence value="5">[</confidence>
240
+ 0021<confidence value="5">]</confidence>
241
+ The first frame <part-num-ref name="first frame">52</part-num-ref>
242
+ and the second frame <part-num-ref name="second frame">54</part-num-ref>
243
+ have a first guide <part-num-ref name="first guide">64</part-num-ref>
244
+ that guides the applicator <part-num-ref name="applicator">32</part-num-ref>
245
+ in the x-direction as it is moved. The first frame <part-num-ref name="first frame">52</part-num-ref>
246
+ and the second frame <part-num-ref name="second frame">54</part-num-ref>
247
+ also include a second guide <part-num-ref name="second guide">66</part-num-ref>
248
+ to guide the applicator <part-num-ref name="applicator">32</part-num-ref>
249
+ in the y-direction as it is moved. </p>
250
+ <p id="p-25" num="25">Accordingly, the first guide <part-num-ref name="first guide">64</part-num-ref>
251
+ and the second guide <part-num-ref name="second guide">66</part-num-ref>
252
+ also include translation devices (not shown in FIGURE 3) operable to move the applicator <part-num-ref name="applicator">32</part-num-ref>
253
+ along the first guide <part-num-ref name="first guide">64</part-num-ref>
254
+ and the second guide <part-num-ref name="second guide">66.</part-num-ref>
255
+ For example, the translation devices <confidence value="5">-</confidence>
256
+ may include a ball-bearing screw translation device, as is well understood in the art, although other linear translation devices are available. The first frame <part-num-ref name="first frame">52</part-num-ref>
257
+ and the second frame <part-num-ref name="second frame">54</part-num-ref>
258
+ also include a linear translator <part-num-ref name="linear translator">66</part-num-ref>
259
+ operable to move the applicator <part-num-ref name="applicator">32</part-num-ref>
260
+ in the z-direction. The linear translator <part-num-ref name="linear translator">66</part-num-ref>
261
+ may also include a ball-bearing screw translation device, although other linear translation devices may be used. </p>
262
+ <p id="p-26" num="26">[0022] Although the actuator <part-num-ref name="actuator">50</part-num-ref>
263
+ shown in FIGURE 3 is configured to apply the image <part-num-ref name="image">62</part-num-ref>
264
+ on opposing sides of the aircraft fin <part-num-ref name="aircraft fin">56,</part-num-ref>
265
+ it is understood that, in other embodiments, the actuator <part-num-ref name="actuator">50</part-num-ref>
266
+ may include a single applicator <part-num-ref name="single applicator">32</part-num-ref>
267
+ positioned on one of the first frame <part-num-ref name="first frame">52</part-num-ref>
268
+ and the second frame <part-num-ref name="second frame">54.</part-num-ref>
269
+ Moreover, the actuator <part-num-ref name="actuator">50</part-num-ref>
270
+ of FIGURE 3 includes a substantially linear first guide <part-num-ref name="substantially linear first guide">64</part-num-ref>
271
+ and a substantially linear second guide <part-num-ref name="substantially linear second guide">66.</part-num-ref>
272
+ In other embodiments, the first guide <part-num-ref name="first guide">64</part-num-ref>
273
+ <confidence value="222222">and/or</confidence>
274
+ the second guide <part-num-ref name="second guide">66</part-num-ref>
275
+ may be curved to conform to other structural shapes. </p>
276
+ <p id="p-27" num="27">For example, the second linear guide <part-num-ref name="second linear guide">66</part-num-ref>
277
+ may have a substantially curved shape while the first guide <part-num-ref name="first guide">64</part-num-ref>
278
+ is linear, so that the actuator <part-num-ref name="actuator">50</part-num-ref>
279
+ may be used to apply an image to a curved structural portion, such as a portion of an aircraft fuselage. </p>
280
+ <p id="p-28" num="28">[0023] FIGURE 4 is a schematic view of an applicator supply system <part-num-ref name="applicator supply system">70</part-num-ref>
281
+ according to still another embodiment of the invention that may be used with the system <part-num-ref name="system">30</part-num-ref>
282
+ of FIGURE 2. The applicator supply system <part-num-ref name="applicator supply system">70</part-num-ref>
283
+ includes a bulk supply reservoir <part-num-ref name="bulk supply reservoir">72</part-num-ref>
284
+ that contains a volume of a pigmented formulation, such as ink, or other similar materials. The bulk supply reservoir <part-num-ref name="bulk supply reservoir">72</part-num-ref>
285
+ includes a level sensor <part-num-ref name="level sensor">74</part-num-ref>
286
+ that is operable to sense a liquid level within the bulk supply reservoir <part-num-ref name="bulk supply reservoir">72</part-num-ref>
287
+ and generate a signal when the liquid level falls below a predetermined level. The bulk supply reservoir <part-num-ref name="bulk supply reservoir">72</part-num-ref>
288
+ also includes a fill port <part-num-ref name="fill port">76</part-num-ref>
289
+ to permit the pigmented formulation to be replenished. The fill port <part-num-ref name="fill port">76</part-num-ref>
290
+ may also be configured with an atmospheric vent to equalize a pressure within the bulk supply reservoir <part-num-ref name="bulk supply reservoir">72</part-num-ref>
291
+ with an atmospheric pressure. </p>
292
+ <p id="p-29" num="29">
293
+ <confidence value="88">-6</confidence>
294
+ - BLA<confidence value="8">C</confidence>
295
+ K L<confidence value="8">O</confidence>
296
+ WE &amp; GRAHAM<confidence value="2">-</confidence>
297
+ <confidence value="666665">46020_</confidence>
298
+ <boundary-data type="header">
299
+ <confidence value="8">C</confidence>
300
+ USTOMER NUMBER <confidence value="4">B</confidence>
301
+ ING-<confidence value="5">1</confidence>
302
+ -1095<confidence value="55">AP</confidence>
303
+ 701 Fifth Avenue, Suite 4800 </boundary-data>
304
+ <boundary-data type="header">Seattle, Washington 98104</boundary-data>
305
+ 206.381.3300 <confidence value="2">-</confidence>
306
+ F: 206.381.3301 <page-break num="7"/>
307
+ The bulk supply reservoir <part-num-ref name="bulk supply reservoir">72</part-num-ref>
308
+ is coupled to a feeder reservoir <part-num-ref name="feeder reservoir">78</part-num-ref>
309
+ by a supply line <part-num-ref name="supply line">80.</part-num-ref>
310
+ Since the bulk supply reservoir <part-num-ref name="bulk supply reservoir">72</part-num-ref>
311
+ and the feeder reservoir <part-num-ref name="feeder reservoir">78</part-num-ref>
312
+ may be positioned at different relative elevations, a supply pump <part-num-ref name="supply pump">82</part-num-ref>
313
+ is positioned in the supply line <part-num-ref name="supply line">80</part-num-ref>
314
+ to move the pigmented material from the bulk supply reservoir <part-num-ref name="bulk supply reservoir">72</part-num-ref>
315
+ to the feeder reservoir <part-num-ref name="feeder reservoir">78.</part-num-ref>
316
+ The supply line <part-num-ref name="supply line">80</part-num-ref>
317
+ may also include a filter <part-num-ref name="filter">84</part-num-ref>
318
+ to remove foreign material or agglomerated pigments from the material in the bulk supply reservoir <part-num-ref name="bulk supply reservoir">72.</part-num-ref>
319
+ The feeder reservoir <part-num-ref name="feeder reservoir">78</part-num-ref>
320
+ also includes a level sensor <part-num-ref name="level sensor">86</part-num-ref>
321
+ that is operable to sense a liquid level within the feeder reservoir <part-num-ref name="feeder reservoir">78</part-num-ref>
322
+ and generate a signal when the liquid level falls below a predetermined level. An atmospheric vent <part-num-ref name="atmospheric vent">88</part-num-ref>
323
+ is positioned on the feeder reservoir <part-num-ref name="feeder reservoir">78</part-num-ref>
324
+ to equalize an internal pressure within the feeder reservoir <part-num-ref name="feeder reservoir">78</part-num-ref>
325
+ with an atmospheric pressure. </p>
326
+ <p id="p-30" num="30">[0024] The feeder reservoir <part-num-ref name="feeder reservoir">78</part-num-ref>
327
+ is coupled to the applicator <part-num-ref name="applicator">32</part-num-ref>
328
+ (as shown in FIGURE 2) having at least one applicator head <part-num-ref name="having at least one applicator head">90</part-num-ref>
329
+ by distribution lines <part-num-ref name="by distribution lines">92.</part-num-ref>
330
+ The applicator head <part-num-ref name="applicator head">90</part-num-ref>
331
+ will be discussed in greater detail below. An applicator pump <part-num-ref name="applicator pump">94</part-num-ref>
332
+ moves a liquid stored within the feeder reservoir <part-num-ref name="feeder reservoir">78</part-num-ref>
333
+ to the applicator <part-num-ref name="applicator">32,</part-num-ref>
334
+ and further provides a pressure that is sufficient to atomize the liquid that is supplied to the at least one applicator head <part-num-ref name="at least one applicator head">90.</part-num-ref>
335
+ A distribution manifold may be positioned in the distribution lines <part-num-ref name="distribution lines">92</part-num-ref>
336
+ to permit more than a single applicator head <part-num-ref name="single applicator head">90</part-num-ref>
337
+ to be supplied. The distribution manifold <part-num-ref name="distribution manifold">96</part-num-ref>
338
+ may also be coupled to a return line <part-num-ref name="return line">98</part-num-ref>
339
+ that permits liquid to return to the reservoir <part-num-ref name="reservoir">78,</part-num-ref>
340
+ thus avoiding excessive liquid pressures at the at least one applicator head <part-num-ref name="at least one applicator head">90,</part-num-ref>
341
+ and also advantageously allowing the pigmented formulation stored within the reservoir <part-num-ref name="reservoir">78</part-num-ref>
342
+ to remain well-mixed. A solenoid valve <part-num-ref name="solenoid valve">100</part-num-ref>
343
+ may also be positioned in the return line <part-num-ref name="return line">98</part-num-ref>
344
+ that may be closed during periods when the applicator supply system <part-num-ref name="applicator supply system">70</part-num-ref>
345
+ is not operating, in order to prevent liquid within the distribution lines <part-num-ref name="distribution lines">92</part-num-ref>
346
+ from moving back into the reservoir <part-num-ref name="reservoir">78</part-num-ref>
347
+ by gravitational action. Flow meters <part-num-ref name="by gravitational action. Flow meters">102</part-num-ref>
348
+ operable to generate a signal when a liquid is in motion within the distribution lines <part-num-ref name="distribution lines">92</part-num-ref>
349
+ may be positioned near the at least one applicator head <part-num-ref name="at least one applicator head">90</part-num-ref>
350
+ in order to detect the absence of a liquid flow in the distribution lines <part-num-ref name="distribution lines">92.</part-num-ref>
351
+ </p>
352
+ <p id="p-31" num="31">[0025] FIGURE 5 is a plan view of an applicator head <part-num-ref name="applicator head">110</part-num-ref>
353
+ according to still another embodiment of the invention that may form a portion of the applicator <part-num-ref name="applicator">32</part-num-ref>
354
+ of FIGURE 2. The applicator head <part-num-ref name="applicator head">110</part-num-ref>
355
+ includes a plurality of liquid jet heads <part-num-ref name="plurality of liquid jet heads">112</part-num-ref>
356
+ operable to <boundary-data type="header">
357
+ <confidence value="2">6</confidence>
358
+ <confidence value="2556">0-7-</confidence>
359
+ BLACK LOWE &amp; GRAHAM<confidence value="1">-</confidence>
360
+ </boundary-data>
361
+ <boundary-data type="line-number">46020</boundary-data>
362
+ <boundary-data type="header">
363
+ <confidence value="66666666">CUSTOMER</confidence>
364
+ <confidence value="666866">NUMBER</confidence>
365
+ <confidence value="8566845558566">BING-1-1095AP</confidence>
366
+ 701 Fifth Avenue, Suite 4800 </boundary-data>
367
+ <boundary-data type="header">
368
+ <confidence value="222222">Seatle</confidence>
369
+ , Washington 98104 </boundary-data>
370
+ 206.381.3300 <confidence value="2">-</confidence>
371
+ F: 206.381.3301 <page-break num="8"/>
372
+ emit droplets a pigmented ink or other like materials towards a surface <part-num-ref name="surface">113</part-num-ref>
373
+ upon which an image is to be transferred. In some embodiments, each of the plurality of liquid jet heads <part-num-ref name="plurality of liquid jet heads">112</part-num-ref>
374
+ may be coupled to a separate applicator supply system <part-num-ref name="separate applicator supply system">70</part-num-ref>
375
+ (FIGURE <part-num-ref name="(FIGURE">4)</part-num-ref>
376
+ to dispense a selected color. For example, the applicator head <part-num-ref name="applicator head">110</part-num-ref>
377
+ may be coupled to four separate applicator supply systems <part-num-ref name="may be coupled to four separate applicator supply systems">70</part-num-ref>
378
+ to provide black, yellow, magenta and cyan-colored inks to the applicator head <part-num-ref name="applicator head">110.</part-num-ref>
379
+ The plurality of liquid jet heads <part-num-ref name="plurality of liquid jet heads">112</part-num-ref>
380
+ are also cou<confidence value="77">pl</confidence>
381
+ ed to a plurality of activation lines <part-num-ref name="plurality of activation lines">114</part-num-ref>
382
+ to transfer an activation signal from the controller <part-num-ref name="controller">38</part-num-ref>
383
+ (as shown in FIGURE 2) to a selected one of the liquid jet heads <part-num-ref name="liquid jet heads">112.</part-num-ref>
384
+ The liquid jet heads <part-num-ref name="liquid jet heads">112</part-num-ref>
385
+ comprising the applicator head <part-num-ref name="applicator head">110</part-num-ref>
386
+ are generally configured to deliver approximately <part-num-ref name="are generally configured to deliver approximately">200</part-num-ref>
387
+ dots-per-inch resolution by generating droplets of the pigmented ink having a typical volume of approximately <part-num-ref name="typical volume of approximately">80</part-num-ref>
388
+ pico- liters per droplet. One suitable applicator head is the commercially available XJ126 applicator head manufactured by Xaar PLC of Cambridge, UK, although other suitable applicator heads may also be used. </p>
389
+ <p id="p-32" num="32">[0026] The applicator head <part-num-ref name="applicator head">110</part-num-ref>
390
+ may also include at least one ultraviolet (UV) light source <part-num-ref name="may also include at least one ultraviolet (UV) light source">116</part-num-ref>
391
+ positioned proximate to the liquid jet heads <part-num-ref name="liquid jet heads">112</part-num-ref>
392
+ and operable to project UV radiation towards the surface <part-num-ref name="surface">113</part-num-ref>
393
+ in order to accelerate polymerization of a UV-cured ink. </p>
394
+ <p id="p-33" num="33">The UV light source 116 may also include a shutter mechanism to interrupt the emission of UV light from the source <part-num-ref name="source">116</part-num-ref>
395
+ so that the polymerization process may be interrupted. A proximity sensor <part-num-ref name="proximity sensor">118</part-num-ref>
396
+ is coupled to the applicator head <part-num-ref name="applicator head">110</part-num-ref>
397
+ that is operable to sense a distance <confidence value="5">'</confidence>
398
+ d' between the applicator head <part-num-ref name="applicator head">110</part-num-ref>
399
+ and the surface <part-num-ref name="surface">113.</part-num-ref>
400
+ Accordingly, the proximity sensor <part-num-ref name="proximity sensor">118</part-num-ref>
401
+ may be comprised of an inductive proximity sensor, a capacitive proximity sensor, or an ultrasonic proximity sensor, all of which are available from the Allen-Bradley Co. of Milwaukee, WI. The applicator head <part-num-ref name="applicator head">110</part-num-ref>
402
+ may also include an optical detector <part-num-ref name="optical detector">120</part-num-ref>
403
+ that is operable to view a portion of the surface <part-num-ref name="surface">113</part-num-ref>
404
+ while an image is applied to the surface <part-num-ref name="surface">113.</part-num-ref>
405
+ </p>
406
+ <p id="p-34" num="34">The optical detector 120 may include an integral light source for illumination of the surface <part-num-ref name="surface">113,</part-num-ref>
407
+ such as a white light emitting diode (LED) or<confidence value="5">,</confidence>
408
+ other similar light source. The applicator head <part-num-ref name="applicator head">110</part-num-ref>
409
+ may also include a mechanical stop <part-num-ref name="mechanical stop">122</part-num-ref>
410
+ to prevent the liquid jet heads <part-num-ref name="liquid jet heads">112</part-num-ref>
411
+ from contacting the surface <part-num-ref name="surface">113.</part-num-ref>
412
+ Accordingly, the mechanical stop <part-num-ref name="mechanical stop">122</part-num-ref>
413
+ may include a spring that <confidence value="88">-8</confidence>
414
+ - BLACK LOWE &amp; GRAHAM <boundary-data type="line-number">46020</boundary-data>
415
+ <boundary-data type="header">
416
+ <confidence value="44466666">cusTOMER</confidence>
417
+ <confidence value="666866">NUMBER</confidence>
418
+ <confidence value="8566856">BING-1-</confidence>
419
+ 1095<confidence value="66">AP</confidence>
420
+ 701 Fifth Avenue, Suite 4800 </boundary-data>
421
+ <boundary-data type="header">Seatt<confidence value="8">l</confidence>
422
+ e, Washington 98104 </boundary-data>
423
+ 206.381.3300 <confidence value="5">*</confidence>
424
+ F: 206.381.3301 <page-break num="9"/>
425
+ biases a wheel against the surface <part-num-ref name="surface">113</part-num-ref>
426
+ and is further configured to prevent positioning the liquid jet heads <part-num-ref name="liquid jet heads">112</part-num-ref>
427
+ at a distance less than <confidence value="62222">'dmin</confidence>
428
+ ' from the surface <part-num-ref name="surface">113.</part-num-ref>
429
+ </p>
430
+ <p id="p-35" num="35">[0027] FIGURE 6 is a block diagrammatic view of a controller <part-num-ref name="controller">130</part-num-ref>
431
+ according to still another embodiment of the invention that may be used with the system <part-num-ref name="system">30</part-num-ref>
432
+ of FIGURE 2. </p>
433
+ <p id="p-36" num="36">The controller 130 includes a personal computing device <part-num-ref name="personal computing device">132</part-num-ref>
434
+ such as the Dimension XPS personal computer system available from Dell Inc. of Houston, TX, although other suitable alternatives exist. The personal computing device <part-num-ref name="personal computing device">132</part-num-ref>
435
+ is configured to receive image information <part-num-ref name="is configured to receive image information">40</part-num-ref>
436
+ through a communications line, such as a 1<confidence value="66">00</confidence>
437
+ bT Ethernet communications line. The image information <part-num-ref name="image information">40</part-num-ref>
438
+ may be formatted in the well-known tagged image file format (TIFF), or in other suitable formats, such as the standard bit-mapped graphics format (BMP) or PCX. The image information <part-num-ref name="image information">40</part-num-ref>
439
+ may also include structural models, such as CATIA files that describe geometric details of an image surface. The personal computing device <part-num-ref name="personal computing device">132</part-num-ref>
440
+ is coupled to a peripheral component interconnect (PC<confidence value="66">I)</confidence>
441
+ board <part-num-ref name="peripheral component interconnect (PCI) board">134</part-num-ref>
442
+ to permit high speed digital communication between the personal computing device <part-num-ref name="personal computing device">132</part-num-ref>
443
+ and a printer interface unit <part-num-ref name="printer interface unit">136.</part-num-ref>
444
+ The printer interface unit <part-num-ref name="printer interface unit">136</part-num-ref>
445
+ controls the applicator <part-num-ref name="applicator">32</part-num-ref>
446
+ (as shown in FIGURE 2). For example, and with reference also to FIGURE 4, the printer interface unit <part-num-ref name="printer interface unit">136</part-num-ref>
447
+ is configured to accept signals generated by the level sensor <part-num-ref name="level sensor">74,</part-num-ref>
448
+ the level sensor <part-num-ref name="level sensor">86</part-num-ref>
449
+ and the flow sensors <part-num-ref name="flow sensors">102</part-num-ref>
450
+ and to control the pump <part-num-ref name="pump">94.</part-num-ref>
451
+ The unit <part-num-ref name="unit">136</part-num-ref>
452
+ is further configured to control the actuator (or other suitable motivating device) <part-num-ref name="actuator (or other suitable motivating device)">36</part-num-ref>
453
+ (as shown in FIGURE 2) by generating motion control commands <part-num-ref name="by generating motion control commands">137</part-num-ref>
454
+ and vacuum system commands <part-num-ref name="and vacuum system commands">138.</part-num-ref>
455
+ The printer interface <part-num-ref name="printer interface">136</part-num-ref>
456
+ is further coupled to a head interface board <part-num-ref name="head interface board">138</part-num-ref>
457
+ that controls the functions of the applicator head <part-num-ref name="applicator head">110</part-num-ref>
458
+ (as shown in FIGURE 5). For example, a UV detect signal <part-num-ref name="UV detect signal">139</part-num-ref>
459
+ is received by the head interface board <part-num-ref name="head interface board">138</part-num-ref>
460
+ through the printer interface <part-num-ref name="printer interface">136</part-num-ref>
461
+ to control the UV light source <part-num-ref name="UV light source">116</part-num-ref>
462
+ (as shown in FIGURE 5) and to control the shutter associated with the UV light source <part-num-ref name="UV light source">116.</part-num-ref>
463
+ The head interface board <part-num-ref name="head interface board">138</part-num-ref>
464
+ may also be configured to receive a media detect signal <part-num-ref name="media detect signal">140</part-num-ref>
465
+ that indicates a surface is proximate to the applicator head <part-num-ref name="applicator head">110.</part-num-ref>
466
+ The head interface board <part-num-ref name="head interface board">138</part-num-ref>
467
+ may also receive an encoder signal <part-num-ref name="encoder signal">141</part-num-ref>
468
+ that may be used to calculate a position corresponding to a next pixel to be printed. The media detect signal <part-num-ref name="media detect signal">140</part-num-ref>
469
+ and the <boundary-data type="header">
470
+ <confidence value="2222556">6020-9-</confidence>
471
+ BLACK LOWE &amp; GRAHAM<confidence value="1">"</confidence>
472
+ </boundary-data>
473
+ <boundary-data type="line-number">46020</boundary-data>
474
+ <boundary-data type="header">
475
+ <confidence value="888">CUS</confidence>
476
+ TOMER <confidence value="66666665655664">NUMBER-1-1095A</confidence>
477
+ 701 Fifth Avenue, Su<confidence value="66">it</confidence>
478
+ e 4800 </boundary-data>
479
+ <boundary-data type="header">Seattle, Washington 98104</boundary-data>
480
+ <confidence value="11111">,)n(.</confidence>
481
+ <confidence value="117">iui</confidence>
482
+ <confidence value="1111">2AAA</confidence>
483
+ <confidence value="2">.</confidence>
484
+ <confidence value="18">G.</confidence>
485
+ <confidence value="2221">)n4f</confidence>
486
+ <confidence value="1111">2.R1</confidence>
487
+ <confidence value="111">xfl</confidence>
488
+ <page-break num="10"/>
489
+ encoder signal <part-num-ref name=",)n(. iui 2AAA . G. )n4f 2.R1 xfl encoder signal">141</part-num-ref>
490
+ are generated by the optical detector <part-num-ref name="optical detector">120,</part-num-ref>
491
+ which is coupled to the applicator head <part-num-ref name="applicator head">110</part-num-ref>
492
+ (as shown in FIGURE 5). </p>
493
+ <p id="p-37" num="37">
494
+ <confidence value="5">[</confidence>
495
+ 0028<confidence value="5">]</confidence>
496
+ With reference still to FIGURE 6, the operation of the controller <part-num-ref name="controller">130</part-num-ref>
497
+ will be discussed in greater detail. The image information <part-num-ref name="image information">40</part-num-ref>
498
+ includes an image file is created through the use of existing image software, such as Adobe Photoshop, available from Adobe Systems Inc. of San Jose, CA, or Core<confidence value="4">l</confidence>
499
+ DRAW, available from Corel Corp. of Dallas TX. </p>
500
+ <p id="p-38" num="38">The image file may be presented to the controller <part-num-ref name="controller">130</part-num-ref>
501
+ in discrete parts, or "tiles", or it may be presented to the controller <part-num-ref name="controller">130</part-num-ref>
502
+ as a single file that encompasses the entire image. The image information <part-num-ref name="image information">40</part-num-ref>
503
+ may also include a three-dimensional surface model that describes the surface upon which the image is to be applied. The three-dimensional surface model may be generated by moving the applicator <part-num-ref name="applicator">32</part-num-ref>
504
+ across the surface and scanning the surface with the optical detector <part-num-ref name="optical detector">120</part-num-ref>
505
+ and/or the proximity sensor <part-num-ref name="proximity sensor">118</part-num-ref>
506
+ to compile a surface map of the aircraft portion that is to receive the image. Once a surface map is generated, it may be stored in the personal computing device <part-num-ref name="personal computing device">132</part-num-ref>
507
+ or it may be uploaded to a different storage location. </p>
508
+ <p id="p-39" num="39">Alternately, a pre-existing CATIA model that describes the structural details of a selected portion of the aircraft may be transferred to the controller <part-num-ref name="controller">130</part-num-ref>
509
+ and used as a three- dimensional surface model. In another approach, a pre-existing surface model may be utilized as a general guide to the surface structure, with the optical detector <part-num-ref name="optical detector">120</part-num-ref>
510
+ and/or the proximity sensor <part-num-ref name="proximity sensor">118</part-num-ref>
511
+ scanning the surface to provide information regarding minor discrepancies in surface contour that may exist between the surface model and the aircraft in the as-built condition. The controller <part-num-ref name="controller">130</part-num-ref>
512
+ controls the motion of the applicator <part-num-ref name="applicator">32</part-num-ref>
513
+ (as shown in FIGURE 2) as it moves across the surface structure by transferring motion control commands <part-num-ref name="surface structure by transferring motion control commands">137</part-num-ref>
514
+ to the actuator <part-num-ref name="actuator">36</part-num-ref>
515
+ (also shown in FIGURE 2). The commands <part-num-ref name="commands">137</part-num-ref>
516
+ may impart three-dimensional motion to the actuator <part-num-ref name="actuator">36</part-num-ref>
517
+ so that the applicator <part-num-ref name="applicator">32</part-num-ref>
518
+ may move across curved surfaces that may include obstructions or other surface irregularities. The commands <part-num-ref name="commands">137</part-num-ref>
519
+ may also impart motion to the actuator <part-num-ref name="actuator">36</part-num-ref>
520
+ so that the applicator <part-num-ref name="applicator">32</part-num-ref>
521
+ makes a single sweep across portions of the surface structure, so that the droplets forming an image on the surface structure are deposited in a single pass. Alternately, the motion imparted to the actuator <part-num-ref name="actuator">36</part-num-ref>
522
+ <confidence value="5">-</confidence>
523
+ <confidence value="88">10</confidence>
524
+ - BLACK LO<confidence value="8">W</confidence>
525
+ E &amp; GR<confidence value="5">A</confidence>
526
+ HAM<confidence value="1">-</confidence>
527
+ <boundary-data type="line-number">46020</boundary-data>
528
+ <boundary-data type="header">
529
+ <confidence value="66566666">CUSTOMER</confidence>
530
+ <confidence value="2">N</confidence>
531
+ <confidence value="2">R</confidence>
532
+ <confidence value="8568658558566">BING-1-1095AP</confidence>
533
+ 701 Fifth Avenue<confidence value="5">,</confidence>
534
+ Suite 4800 </boundary-data>
535
+ <boundary-data type="header">Seattle, Washington 98104</boundary-data>
536
+ <confidence value="22">?n</confidence>
537
+ (, <confidence value="22">ui</confidence>
538
+ <confidence value="6111">3nfl</confidence>
539
+ <confidence value="1">*</confidence>
540
+ <confidence value="7">.</confidence>
541
+ <confidence value="221">P-;</confidence>
542
+ <confidence value="111111">,)R1t~</confidence>
543
+ <confidence value="42">am</confidence>
544
+ <page-break num="11"/>
545
+ may include a plurality of repetitive sweeps across portions of the surface, in order to optically reinforce portions of the image having greater density. </p>
546
+ <p id="p-40" num="40">
547
+ <confidence value="5">[</confidence>
548
+ 0029] FIGURE 7 is a partial cross-sectional view of an external portion <part-num-ref name="external portion">160</part-num-ref>
549
+ of an aircraft that will be used to describe a method of applying an image to an aircraft according to an<confidence value="7">o</confidence>
550
+ ther embodiment of the invention. A primer layer <part-num-ref name="primer layer">162</part-num-ref>
551
+ is applied to a supporting surface <part-num-ref name="supporting surface">164,</part-num-ref>
552
+ which is typically a structural portion of the aircraft, such as a fuselage panel, a wing panel, or other external surfaces of the aircraft. The primer layer <part-num-ref name="primer layer">162</part-num-ref>
553
+ may be comprised of zin<confidence value="8">c</confidence>
554
+ chromate pigments that are added to carriers of several different resin types, such as epoxy, polyurethane, alkyd and others. A white opaque base layer <part-num-ref name="white opaque base layer">166</part-num-ref>
555
+ comprised of a resin type that is compatible with the primer layer <part-num-ref name="primer layer">162</part-num-ref>
556
+ is then applied. A graphics layer <part-num-ref name="graphics layer">168</part-num-ref>
557
+ may then be applied to the white opaque base layer <part-num-ref name="white opaque base layer">166</part-num-ref>
558
+ to form image segments <part-num-ref name="to form image segments">170,</part-num-ref>
559
+ each comprised of a selected color <confidence value="222222">and/or</confidence>
560
+ shape, which may be simultaneously applied to the white opaque base layer <part-num-ref name="white opaque base layer">166</part-num-ref>
561
+ using the ink<confidence value="5">-</confidence>
562
+ jet imaging process described in detail above. A transparent layer <part-num-ref name="transparent layer">172</part-num-ref>
563
+ may then be applied to the graphics layer <part-num-ref name="graphics layer">168</part-num-ref>
564
+ to protect the graphics layer <part-num-ref name="graphics layer">168</part-num-ref>
565
+ from the erosive effects of rain and water droplets encountered during flight, and to protect the image segments <part-num-ref name="image segments">170</part-num-ref>
566
+ of the graphics layer <part-num-ref name="graphics layer">168</part-num-ref>
567
+ from the prolonged effects of ultraviolet radiation. </p>
568
+ <p id="p-41" num="41">[0030] Those skilled in the art will also readily recognize that the foregoing embodiment may be applied to a wide variety of different locations on an aircraft. Referring now in particular to FIGURE 8, a side elevation view of an aircraft <part-num-ref name="aircraft">300</part-num-ref>
569
+ having at least one graphic image <part-num-ref name="having at least one graphic image">314</part-num-ref>
570
+ according to the foregoing embodiment is shown. With the exception of the graphic image <part-num-ref name="graphic image">314,</part-num-ref>
571
+ the aircraft <part-num-ref name="aircraft">300</part-num-ref>
572
+ includes components and subsystems generally known in the pertinent art, and in the interest of brevity, will not be described further. The aircraft <part-num-ref name="aircraft">300</part-num-ref>
573
+ generally includes one or more propulsion units <part-num-ref name="generally includes one or more propulsion units">302</part-num-ref>
574
+ that are coupled to wing assemblies <part-num-ref name="that are coupled to wing assemblies">304,</part-num-ref>
575
+ or alternately, to a fuselage <part-num-ref name="fuselage">306</part-num-ref>
576
+ or even other portions of the aircraft <part-num-ref name="aircraft">300.</part-num-ref>
577
+ </p>
578
+ <p id="p-42" num="42">Additionally, the aircraft <part-num-ref name="aircraft">300</part-num-ref>
579
+ also includes a tail assembly <part-num-ref name="tail assembly">308</part-num-ref>
580
+ and a landing assembly <part-num-ref name="landing assembly">310</part-num-ref>
581
+ coupled to the fuselage <part-num-ref name="fuselage">306.</part-num-ref>
582
+ The aircraft <part-num-ref name="aircraft">300</part-num-ref>
583
+ further includes other systems and subsystems generally required for the proper operation of the aircraft <part-num-ref name="aircraft">300.</part-num-ref>
584
+ For example, the aircraft <part-num-ref name="aircraft">300</part-num-ref>
585
+ includes a flight control system <part-num-ref name="flight control system">312</part-num-ref>
586
+ (not shown in FIGURE 8), as well as a plurality of other <boundary-data type="header">- 11 - BLACK <confidence value="6446">LOWE</confidence>
587
+ <confidence value="6">&amp;</confidence>
588
+ GR<confidence value="8888">AHAM</confidence>
589
+ </boundary-data>
590
+ <boundary-data type="line-number">46020</boundary-data>
591
+ <boundary-data type="header">CUSTOMER <confidence value="2222">NUMR</confidence>
592
+ <confidence value="2666545855">BNG--1095A</confidence>
593
+ P 701 Fifth Avenue, Sui<confidence value="5">t</confidence>
594
+ e 4800 </boundary-data>
595
+ <boundary-data type="header">Seattle, Washington 98104</boundary-data>
596
+ 206.381.3300 <confidence value="5">*</confidence>
597
+ F: 206.381.3301 <page-break num="12"/>
598
+ electrical, mechanical and electromechanical systems that cooperatively perform a variety of tasks necessary for the operation of the aircraft <part-num-ref name="aircraft">300.</part-num-ref>
599
+ Accordingly, the aircraft <part-num-ref name="aircraft">300</part-num-ref>
600
+ is generally representative of a commercial passenger aircraft, which may include, for example, the <part-num-ref name="">737,</part-num-ref>
601
+ <part-num-ref name="737,">747,</part-num-ref>
602
+ <part-num-ref name="737, 747,">757,</part-num-ref>
603
+ <part-num-ref name="737, 747, 757,">767</part-num-ref>
604
+ and <part-num-ref name="and">777</part-num-ref>
605
+ commercial passenger aircraft available from The Boeing Company of Chicago, IL. Although the aircraft <part-num-ref name="aircraft">300</part-num-ref>
606
+ shown in FIGURE 8 generally shows a commercial passenger aircraft, it is understood that the graphic image <part-num-ref name="graphic image">314</part-num-ref>
607
+ according to the foregoing embodiment may also be applied to flight vehicles of other types. Examples of such flight vehicles may include manned or even unmanned military aircraft, rotary wing aircraft, or even ballistic flight vehicles, as illustrated more fully in various descriptive volumes, such as Jane's All The World's Aircraft, available from Jane's Information Group, Ltd. of Coulsdon, Surrey, UK. </p>
608
+ <p id="p-43" num="43">
609
+ <confidence value="5">[</confidence>
610
+ 0031] While preferred and alternate embodiments of the invention have been illustrated and described, as noted above, many changes can be made without departing from the spirit and scope of the invention. Accordingly, the scope of the invention is not limited by the disclosure of these preferred and alternate embodiments. Instead, the invention should be determined entirely by reference to the claims that follow. </p>
611
+ <p id="p-44" num="44">
612
+ <confidence value="888">-12</confidence>
613
+ - BLACK LOWE &amp; GRAHAM<confidence value="1">"</confidence>
614
+ <boundary-data type="line-number">46020</boundary-data>
615
+ </p>
616
+ <heading id="h-9">CUSTOMER NUMBER</heading>
617
+ <boundary-data type="header">
618
+ <confidence value="858685855865">BING-1-1095A</confidence>
619
+ P 701 Fifth Avenue, Suite 4800 </boundary-data>
620
+ <boundary-data type="header">
621
+ <confidence value="222222">Searle</confidence>
622
+ , Washington 98104 </boundary-data>
623
+ <p id="p-45" num="45">206.381.3300 <confidence value="2">+</confidence>
624
+ F: 206.381.3301 </p>
625
+ </description>
626
+ </us-patent-application>
627
+
prior_art/10953863.xml ADDED
@@ -0,0 +1,65 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>10953863</doc-number>
8
+ <date>2007-12-28</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <boundary-data type="header">Application No. 10/953,863 PATENT</boundary-data>
14
+ <boundary-data type="header">Amendment dated December 28, 2007</boundary-data>
15
+ <boundary-data type="header">Reply to Office Action of September 28, 2007</boundary-data>
16
+ <p id="p-1" num="1">Amendments to the Specification:</p>
17
+ <p id="p-2" num="2">Please replace paragraph [0025<confidence value="5">]</confidence>
18
+ with the following amended paragraph. </p>
19
+ <p id="p-3" num="3">[0025<confidence value="5">]</confidence>
20
+ The system <part-num-ref name="system">100</part-num-ref>
21
+ also includes a second network <part-num-ref name="second network">108,</part-num-ref>
22
+ which may be any of the aforementioned networks. The first network <part-num-ref name="first network">104</part-num-ref>
23
+ and the second network <part-num-ref name="second network">108</part-num-ref>
24
+ may be the same network, different networks, or portions of a larger network. The second network <part-num-ref name="second network">108</part-num-ref>
25
+ provides a connection between the host computer system <part-num-ref name="host computer system">102</part-num-ref>
26
+ and computing devices <part-num-ref name="and computing devices">
27
+ <confidence value="668">110</confidence>
28
+ </part-num-ref>
29
+ <confidence value="8554">4-09</confidence>
30
+ at merchant locations <part-num-ref name="4-09 at merchant locations">107.</part-num-ref>
31
+ In a specific embodiment, the second network is a packet-based data network, such as the Internet. Wireless hubs <part-num-ref name="Internet. Wireless hubs">111</part-num-ref>
32
+ at merchant locations <part-num-ref name="at merchant locations">107,</part-num-ref>
33
+ allow customer computing devices <part-num-ref name="at merchant locations 107, allow customer computing devices">112</part-num-ref>
34
+ to access the second network <part-num-ref name="second network">108.</part-num-ref>
35
+ As those skilled in the art will appreciate the wireless hubs <part-num-ref name="wireless hubs">111</part-num-ref>
36
+ may use and of a variety of wireless protocols, including 802.1 <confidence value="2">1</confidence>
37
+ b, 802.1<confidence value="5">1</confidence>
38
+ <confidence value="88">a,</confidence>
39
+ 802.11g, 802.16, third generation 3G, or other appropriate communications protocol, which may be known by other common names such as Wireless Fidelity (WiFi), WiMAX, 3G, and the like. </p>
40
+ <p id="p-4" num="4">Please replace paragraph [0045<confidence value="5">]</confidence>
41
+ with the following amended paragraph. </p>
42
+ <p id="p-5" num="5">[0045<confidence value="5">]</confidence>
43
+ Thereafter, the service provider and host computer system may cooperate to keep track of the customer's balance. This may be accomplished in a number of ways. For example, the customer may have purchased a finite number of megabytes of access, a finite number of minutes, and/or a finite access period. In either case, the service provider may send information to the host computer system that allows the host computer system to appropriately adjust the customer's balance. The host computer system then may use this information in the future to determine whether the customer should be given access to the network. Keeping track of the customer's declining balance is reflected as block <part-num-ref name="customer's declining balance is reflected as block">416</part-num-ref>
44
+ in Fig. 4 <part-num-ref name="">
45
+ <confidence value="58">2.</confidence>
46
+ </part-num-ref>
47
+ </p>
48
+ <boundary-data type="header">Page 2 of 12</boundary-data>
49
+ <boundary-data type="header">Application No. 10/953,863 PATENT</boundary-data>
50
+ <boundary-data type="header">Amendment dated December 28, 2007</boundary-data>
51
+ <boundary-data type="header">Reply to Office Action of September 28, 2007</boundary-data>
52
+ <p id="p-6" num="6">
53
+ <page-break num="2"/>
54
+ Please replace paragraph [0046<confidence value="5">]</confidence>
55
+ with the following amended paragraph. </p>
56
+ <p id="p-7" num="7">[0046<confidence value="5">]</confidence>
57
+ Maintaining the customer's balance at block <part-num-ref name="customer's balance at block">41<confidence value="6">6</confidence>
58
+ </part-num-ref>
59
+ <confidence value="866">2-6</confidence>
60
+ may include keeping track of the customer's purchases using the presentation instrument. For example, if the customer makes purchases at the merchant location using the presentation instrument, the host computer system may credit the customer with loyalty points. Thereafter, the customer may redeem the points for other items, include additional network access. </p>
61
+ <boundary-data type="header">Page 3 of <confidence value="68">12</confidence>
62
+ </boundary-data>
63
+ </description>
64
+ </us-patent-application>
65
+
prior_art/10979005.xml ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>10979005</doc-number>
8
+ <date>2009-01-06</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <p id="p-1" num="1">Amendments to the Specification Please replace paragraph [0017] with the following amended paragraph:</p>
14
+ <p id="p-2" num="2">[0017<confidence value="5">]</confidence>
15
+ The guest atoms <part-num-ref name="guest atoms">12</part-num-ref>
16
+ in the filled skutterudite <part-num-ref name="filled skutterudite">10</part-num-ref>
17
+ maybe rare earth atoms, Na, K, Ca, Sr, Ba, and combinations of these atoms. According to the present invention, a source or starting material of the guest atoms <part-num-ref name="guest atoms">12</part-num-ref>
18
+ is mischmetal (Mm) alloy, which is an alloy of mostly C<confidence value="5">e</confidence>
19
+ (about <part-num-ref name="alloy of mostly Ce (about">50</part-num-ref>
20
+ wt. <confidence value="5">%</confidence>
21
+ ) and La (about <part-num-ref name="wt. %) and La (about">50</part-num-ref>
22
+ wt. <confidence value="686">%).</confidence>
23
+ Mischmetal is a naturally occurring material. It is commercially available and typically comprises varying amounts of at least four rare earth elements such as lanthanum, cerium, praseodymium and neodymium, and also non-rare earth impurities such as iron, magnesium, silicon, sulfur, and phosphorus. The mischmetal may be used alone or in combination with a rare earth metal or metals as the source or starting material for the guest atoms <part-num-ref name="guest atoms">12.</part-num-ref>
24
+ These rare-earth metals include those from the lanthanide series, such as Ce, Pr, Nd, Sm, <confidence value="5">E</confidence>
25
+ u and Gd, as well as those from the actinides series, such as Th and U. In a typical embodiment, the composition of the filled skutterudite <part-num-ref name="filled skutterudite">10</part-num-ref>
26
+ is Mm<confidence value="586">yCo</confidence>
27
+ 4Sb<confidence value="1">n</confidence>
28
+ (0&lt;y<confidence value="5">&lt;</confidence>
29
+ 1). </p>
30
+ <p id="p-3" num="3">
31
+ <confidence value="8">2</confidence>
32
+ </p>
33
+ </description>
34
+ </us-patent-application>
35
+
prior_art/10993882.xml ADDED
@@ -0,0 +1,33 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>10993882</doc-number>
8
+ <date>2008-08-28</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <boundary-data type="header">App. No. 10/993,882</boundary-data>
14
+ <boundary-data type="header">Office Action dated April 10, 2008</boundary-data>
15
+ <boundary-data type="header">Amendment dated August 28, 2008</boundary-data>
16
+ <heading id="h-1">AMEN<confidence value="8">D</confidence>
17
+ MENTS TO THE SPECIFICATION </heading>
18
+ <p id="p-1" num="1">[paragraph 0002] Local Area Networks (LANs) connect computing systems together at the Layer <part-num-ref name="Layer">2</part-num-ref>
19
+ level. </p>
20
+ <p id="p-2" num="2">The term "Layer 2" refers to the second layer in the protocol stack defined by the well-known Open Systems Interface (OSI) model, also known as the logical link, data link, or Media Access Control (MAC) layer. Each computing system connects to a LAN through a (MAC) device.</p>
21
+ <p id="p-3" num="3">Multiple LANs can be connected together using <confidence value="5">M</confidence>
22
+ AC bridges, as set forth in the "IEEE Standard for Information Technology, Telecommunications and Information Exchange between Systems, Local and Metropolitan Area Networks, Common Specifications, Part 3: Media Access Control (MAC) Bridges," published as ANS<confidence value="5266">I/IE</confidence>
23
+ EE Standard 802.1D (1998), which is incorporated herein by reference. (The 802.<confidence value="55">1D</confidence>
24
+ standard, as well as other IEEE standards cited herein, is available a<confidence value="6">t</confidence>
25
+ <confidence value="266664155555514222">standas.ieee.erg/e</confidence>
26
+ in the standards section of the IEEE Web site.) MAC bridges that implement the 802.<confidence value="5">1</confidence>
27
+ D standard allow MAC devices attached to physically separated LANs to appear to each other as if they were attached to a single LAN. The bridge includes two or more MAC devices that interconnect the bridge ports to respective LANs. </p>
28
+ <boundary-data type="header">
29
+ <confidence value="8">2</confidence>
30
+ </boundary-data>
31
+ </description>
32
+ </us-patent-application>
33
+
prior_art/11012499.xml ADDED
The diff for this file is too large to render. See raw diff
 
prior_art/11016221.xml ADDED
@@ -0,0 +1,502 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11016221</doc-number>
8
+ <date>2004-12-17</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <boundary-data type="header">
14
+ <confidence value="2222">Atty</confidence>
15
+ . Dkt No.: R<confidence value="5">O</confidence>
16
+ C920040202US1 </boundary-data>
17
+ <heading id="h-1">METHOD FOR ASSOCIATING ANNOTATIONS WITH DOCUMENT FAMILIES</heading>
18
+ <heading id="h-2">CROSS-REFERENCE TO RELATED APPLICATIONS</heading>
19
+ <p id="p-1" num="1">[0001] The present invention is related to the commonly owned, co-pending U.S.</p>
20
+ <p id="p-2" num="2">patent application, U.S. Serial No. 10/600,014, filed June 20, 2003, entitled, "Universal Annotation Management System" which is incorporated herein by reference in its entirety.</p>
21
+ <heading id="h-3">BACKGROUND OF THE INVENTION</heading>
22
+ <p id="p-3" num="3">Field of the <confidence value="5">I</confidence>
23
+ nvention [0002] The present invention generally relates to data management. More particularly, the present invention relates to managing annotations stored for a one version of a data source and making the annotations available to other versions of the data source. </p>
24
+ <p id="p-4" num="4">Description of the Related Art [0003] There are wel<confidence value="5">l</confidence>
25
+ -known methods for capturing and storing explicit knowledge as data using a computer system. Common methods for storing data include databases, word-processor documents, text files, spread-sheets, and many other formats for storing and retrieving data. Oftentimes, such data is analyzed by various individuals (e.g., experts, technicians, managers, researchers, etc.), resulting in rich interpretive information referred to as tacit knowledge. </p>
26
+ <p id="p-5" num="5">[0004] Generally, tacit knowledge is knowledge that is not made explicit. It may be highly personal, is oftentimes very transient, and usually requires joint, shared activities to be transmitted. Examples of tacit knowledge include subjective insights, intuitions, facts learned from conversational exchanges, and hunches. Despite its highly valuable quality, tacit knowledge is often only temporarily captured, for example, as cryptic notes in a lab notebook, discussions, conversations, instant messaging exchanges, <confidence value="5">e</confidence>
27
+ -mails messages, and other transient communications. </p>
28
+ <boundary-data type="header">
29
+ <confidence value="5">1</confidence>
30
+ </boundary-data>
31
+ <boundary-data type="header">
32
+ <confidence value="2222">Atty</confidence>
33
+ . Dkt No.: R<confidence value="5">O</confidence>
34
+ C920040202US1 </boundary-data>
35
+ <p id="p-6" num="6">
36
+ <page-break num="2"/>
37
+ Thus, because it is typically not captured systematically, tacit knowledge is often lost. </p>
38
+ <p id="p-7" num="7">
39
+ <confidence value="5">[</confidence>
40
+ 0005<confidence value="5">]</confidence>
41
+ One approach to capture tacit knowledge is to create annotations about explicit data. Virtually any identifiable type of data appearing in a data source may be annotated, including, a matrix of data such as a spreadsheet or database table, a text document, an image, or multi-media data. Further, sub-portions of objects (sub- objects) may be annotated, for example, an individual cell, row or column in a database table or a page, section, paragraph or word in a text document. </p>
42
+ <p id="p-8" num="8">[0006] An annotation system stores descriptive information about objects, or parts of objects, without modifying the objects directly. An annotation store, typically a database, stores descriptive information for an annotation, and an indexing scheme maps each annotation to the object, or position within the object. An advanced annotation system, such as the one described in a commonly owned, co- pending application entitled "Universal Annotation Management System" U.S. Serial No. 10/600,382 stores annotations separately from the corresponding data object and associates the annotations with an identifier that is location-independent. That is, the identifier does not depend on the location of a data source in a file system hierarchy or existence in a given database. Typically this identifier is derived from the document contents rather than from location artifacts such as filename, path, URL, etc.</p>
43
+ <p id="p-9" num="9">[0007<confidence value="5">]</confidence>
44
+ Problems arise, however, when the contents of an annotated data source are changed. Oftentimes, the annotation created for the unmodified document is still useful for the modified document. For example, where a group of individuals collaborates on the contents of a data source, or where the modifications introduce additional content, and do not disturb the content that was originally annotated, the annotations should be carried forward to subsequent versions of the data source. </p>
45
+ <p id="p-10" num="10">The annotations, however, may refer only to the original data source, and not the modified version. Hence, annotations may become orphaned when an original document is modified.</p>
46
+ <boundary-data type="header">
47
+ <confidence value="8">2</confidence>
48
+ </boundary-data>
49
+ <boundary-data type="header">Atty. Dkt No.: R<confidence value="5">O</confidence>
50
+ C920040202US1 </boundary-data>
51
+ <p id="p-11" num="11">
52
+ <page-break num="3"/>
53
+ [0008] One current method to prevent annotations from being orphaned involves storing the annotations directly within the document containing the annotated data. </p>
54
+ <p id="p-12" num="12">This solution, however, is not always possible, and more importantly, limits collaboration since a user who desires to view annotations must ensure that they are looking at the latest version of a document.</p>
55
+ <p id="p-13" num="13">[0009] Another solution involves using a document management system to record and maintain associations between versions of a data source. The annotation system is configured to lookup annotations in other versions of a data source based on the version hierarchy stored by the document management system. The main drawback to this approach is that it imposes the strict use of a document management system which requires users to formally check-in and check-out documents, and also imposes other heavy processes that consume system resources.</p>
56
+ <p id="p-14" num="14">[0010] Accordingly, there remains a need for techniques to provide an annotation system that manages annotations created for different versions of a data source that do not depend on storing the annotations with the data source. Such techniques should also lack the complexity and requirements imposed by a complex document management system.</p>
57
+ <heading id="h-4">SUMMARY OF THE INVENTION</heading>
58
+ <p id="p-15" num="15">[0011] The present invention generally provides methods, systems, and articles of manufacture providing an annotation system that manages annotations created for different versions of a data source family. Annotations created for one version of a data source may be viewed in context from both subsequent and prior versions of the same data source.</p>
59
+ <p id="p-16" num="16">[0012] Generally, embodiments of the invention associate annotations with both a data source "family identifier<confidence value="5">"</confidence>
60
+ (family ID) as well as a "version identifier<confidence value="5">"</confidence>
61
+ (version ID) where the family ID is an identifier that is embedded in the data source. Other than adding the family ID to the data source, the data source may remain unchanged by the annotation system. The family ID is maintained across different <boundary-data type="header">
62
+ <confidence value="8">3</confidence>
63
+ </boundary-data>
64
+ <page-break num="4"/>
65
+ <boundary-data type="header">
66
+ <confidence value="2222">Atty</confidence>
67
+ . Dkt No.: R<confidence value="5">O</confidence>
68
+ C920040202US1 </boundary-data>
69
+ versions of the data source, whereas version IDs are determined for a specific version of the data source. Version IDs can be constructed from each data source directly, and do not need to be stored. </p>
70
+ <p id="p-17" num="17">[0013] One embodiment of the invention provides a method for associating annotations with a data source family. The method generally includes, receiving a request to create a first annotation for data content in an initial version of a data source; generating a family identifier, wherein the family identifier is associated with the initial version of the data source and with subsequent versions of the data source, and obtaining annotation content for a first annotation associated with a portion of data content in the initial version of the data source. The method generally further includes, associating the first annotation with the family identifier and with the initial version of the data source; and storing the family identifier in the initial version of the data source.</p>
71
+ <p id="p-18" num="18">[0014] Another embodiment of the invention provides a method of displaying annotations created for different versions of a data source. The method generally includes determining a family identifier associated with the data source and determining a version identifier associated with the data source. The method generally further includes retrieving, from an annotation store, a set of one or more annotation records wherein each annotation record indicates the family identifier and the version identifier of the data source associated with the annotation record, and displaying, for each annotation record with a version identifier matching the version identifier associated with the data source, an indication that annotation content is available for data content in the data source.</p>
72
+ <p id="p-19" num="19">[0015] Another embodiment of the invention provides a computer-readable medium containing a plurality of instructions that when executed on a computer system perform operations. The operations generally include receiving a request to create a first annotation for data content in an initial version of a data source, generating a family identifier, wherein the family identifier is associated with the initial version of the data source and with all subsequent versions of the data source, and obtaining annotation content for a first annotation associated with the data <boundary-data type="header">
73
+ <confidence value="8">4</confidence>
74
+ </boundary-data>
75
+ <page-break num="5"/>
76
+ <boundary-data type="header">Atty. Dkt No.: R<confidence value="5">O</confidence>
77
+ C920040202US1 </boundary-data>
78
+ content in the initial version of the data source. The method generally further include, associating the first annotation with the family identifier and the initial version of the data source, and storing the family identifier in the initial version of the data source. </p>
79
+ <p id="p-20" num="20">[0016] Another embodiment of the invention provides a computer-readable medium containing a plurality of instructions which, when executed on a computer system is configured to perform operations for displaying annotations created for different versions of a data source. The operations generally include determining a family identifier associated with the data source, and determining a version identifier associated with the data source. The operations generally further include retrieving, from an annotation store, a set of one or more annotation records wherein each annotation record indicates the family identifier and the version identifier of the data source associated with the annotation record, and displaying, for each annotation record with a version identifier matching the version identifier associated with the data source of the data source, an indication that annotation content is available for data content in the data source.</p>
80
+ <p id="p-21" num="21">
81
+ <confidence value="5">[</confidence>
82
+ 0017] Another embodiment of the invention provides a system for managing annotations for multiple versions of a data source. The system generally includes an annotation management application configured to associate different versions of a data source with a common family identifier, a database used to store annotations created for the multiple versions of a data source; and an interface configured to display an indication of annotations created for a current version of a data source and an indication of annotations created for other versions of the data source. </p>
83
+ <p id="p-22" num="22">[0018<confidence value="5">]</confidence>
84
+ Another embodiment of the invention provides a system for managing annotations created for multiple versions of a data source. The system generally includes an annotation management application configured to associate different versions of the data source with a common family identifier and to associate annotations created for the data source with both a family identifier and a version identifier, a database used to store annotations created for the multiple versions of a data source, and an interface configured to display an indication of annotations <boundary-data type="header">
85
+ <confidence value="8">5</confidence>
86
+ </boundary-data>
87
+ <page-break num="6"/>
88
+ <boundary-data type="header">
89
+ <confidence value="2222">Atty</confidence>
90
+ . Dkt No.: R<confidence value="5">O</confidence>
91
+ C920040202US1 </boundary-data>
92
+ created for a current version of a data source, and configured to display an indication of annotations created for other versions of the data source. </p>
93
+ <heading id="h-5">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
94
+ <p id="p-23" num="23">[0019<confidence value="5">]</confidence>
95
+ So that the manner in which the above recited features, advantages and objects of the present invention are attained and can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to the embodiments as illustrated by the appended drawings. </p>
96
+ <p id="p-24" num="24">[0020] The appended drawings, however, illustrate only typical embodiments of the invention and should not, therefore, be considered limiting of its scope, for the invention may admit to other equally effective embodiments.</p>
97
+ <p id="p-25" num="25">[0021<confidence value="5">]</confidence>
98
+ Figure 1 illustrates an exemplary computing environment, according to one embodiment of the invention. </p>
99
+ <p id="p-26" num="26">[0022] Figure 2 illustrates a client server view of an annotation system, according to one embodiment of the invention.</p>
100
+ <p id="p-27" num="27">[0023] Figure 3 illustrates a relational view of an annotation system in communication with an application program and annotation database, according to one embodiment of the invention.</p>
101
+ <p id="p-28" num="28">[0024<confidence value="5">]</confidence>
102
+ Figure 4A illustrates a graphical user interface that displays an original version of a document that includes annotations created for the document, according to one embodiment of the invention. </p>
103
+ <p id="p-29" num="29">[0025<confidence value="5">]</confidence>
104
+ Figure 4B illustrates the document from Figure 4A after modification and additional annotations have been created, according to one embodiment of the invention. </p>
105
+ <p id="p-30" num="30">[0026<confidence value="5">]</confidence>
106
+ Figure 5 illustrates a time-lapse view of a document that includes the state of annotations created for the document and an annotation database used to store annotations created for the document family associated with the document, according to one embodiment of the invention. </p>
107
+ <boundary-data type="header">
108
+ <confidence value="8">6</confidence>
109
+ </boundary-data>
110
+ <boundary-data type="header">
111
+ <confidence value="1">'</confidence>
112
+ <confidence value="866">Att</confidence>
113
+ y. Dkt No.: R<confidence value="5">O</confidence>
114
+ C920040202US1 </boundary-data>
115
+ <p id="p-31" num="31">
116
+ <page-break num="7"/>
117
+ [0027] Figure 6A illustrates a method for creating an annotation for a data source, according to one embodiment of the present invention. </p>
118
+ <p id="p-32" num="32">[002<confidence value="5">8</confidence>
119
+ ] Figure 6B illustrates another method for creating an annotation for a modified version of a data source, according to one embodiment of the present invention. </p>
120
+ <p id="p-33" num="33">[0029] Figure 6<confidence value="5">C</confidence>
121
+ illustrates a method for viewing annotations created for different versions of a document family, according to one embodiment of the invention. </p>
122
+ <heading id="h-6">DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS</heading>
123
+ <p id="p-34" num="34">[0030<confidence value="5">]</confidence>
124
+ Embodiments of the invention provide methods, systems, and articles of manufacture for managing an annotation system that includes annotations created for multiple versions of a data source (i.e., a data source that begins with an initial version and is subsequently modified to create a family of versions). Annotations created for one version of the data source may be viewed in context from both subsequent and prior versions of the same data source. </p>
125
+ <p id="p-35" num="35">[0031<confidence value="5">]</confidence>
126
+ Embodiments of the invention associate annotations with both a data source "family identifier<confidence value="5">"</confidence>
127
+ (family ID) as well as a "version identifier<confidence value="5">"</confidence>
128
+ (version ID) where the family ID is an identifier that is embedded in the data source. Other than adding a family ID to the data source, the data source remains unchanged by the annotation system. The family ID is maintained across different versions of the data source, whereas version IDs are determined for a specific version of the data source. Version IDs can be constructed from each document directly, and do not need to be stored. </p>
129
+ <p id="p-36" num="36">[0032] When annotations are created, the family ID is retrieved from the data source (or one is created if none exists). Annotations are associates with both the specific version of the document (through the version ID) and to the family ID. When annotations are retrieved for a data source, a query for the family ID will return all annotations created for any version of the data source. In one embodiment, annotations may include metadata that indicates both the family ID and the version ID for the annotation. Further, one annotation may reference multiple version IDs.</p>
130
+ <boundary-data type="header">
131
+ <confidence value="8">7</confidence>
132
+ </boundary-data>
133
+ <boundary-data type="header">Atty. Dkt No.: R<confidence value="5">O</confidence>
134
+ C920040202US1 </boundary-data>
135
+ <p id="p-37" num="37">
136
+ <page-break num="8"/>
137
+ This allows users to distinguish between annotations created for the current version and annotations from other versions. In one embodiment, annotations created for the current version are displayed relative to the annotated content of the current version using an icon display. Annotations created for other versions may be viewed in context by displaying the other version of the data source associated with the annotation alongside the current version of the data source. </p>
138
+ <p id="p-38" num="38">[0033] As used herein, the term annotation generally refers to any type of descriptive information associated with data elements in a data source. Annotations may be captured in a variety of forms, including textual annotations (descriptions, revisions, clarifications, comments, instructions, etc.), graphical annotations (pictures, symbols, etc.) or sound recordings. While an annotation may exist in any of these forms, embodiments of the invention may be described below with reference to textual annotations as a particular, but not limiting, example of an annotation. Accordingly, as persons of ordinary skill in the art will understand, the following techniques described with reference to textual annotations made for a document (e.g., a document created using word-processing software) may also be applied to other types of annotations.</p>
139
+ <p id="p-39" num="39">[0034] As used herein, the term "data source" refers to any type of content containing data object, including without limitation, text documents, database records, database tables, spreadsheets, schematics, images, multi-media, and any other data source used by an application program to create manage, edit, store, view and/or analyze data. To help provide an understanding of the invention, embodiments of the invention are described using a document as a particular type of data source. While the following description may refer to a graphical user interface (GUI), those of ordinary skill in the art will understand that the same functionality may be provided through a non-graphical user interface, such as a command line, and further, that similar information may be exchanged between automated agents (e.g. a software daemon configured to generate annotations) via an automated interface.</p>
140
+ <boundary-data type="header">
141
+ <confidence value="8">8</confidence>
142
+ </boundary-data>
143
+ <boundary-data type="header">
144
+ <confidence value="2222">Atty</confidence>
145
+ . Dkt No.: R<confidence value="5">O</confidence>
146
+ C920040202US1 </boundary-data>
147
+ <p id="p-40" num="40">
148
+ <page-break num="9"/>
149
+ [0035] In the following description, reference is made to embodiments of the invention. The invention is not, however, limited to any specifically described embodiment. Rather, any combination of the following features and elements, whether related to a described embodiment or not, implements and practices the invention. Furthermore, in various embodiments the invention provides numerous advantages over the prior art. Although embodiments of the invention may achieve advantages over other possible solutions and the prior art, whether a particular advantage is achieved by a given embodiment does not limit the scope of the invention. Thus, the following aspects, features, embodiments and advantages are illustrative and are not considered elements or limitations of the appended claims except where explicitly recited in a claim. Likewise, references to "the invention" shall neither be construed as a generalization of any inventive subject matter disclosed herein nor considered an element or limitation of the appended claims except where explicitly recited in a claim. </p>
150
+ <p id="p-41" num="41">
151
+ <confidence value="5">[</confidence>
152
+ 0036] One embodiment of the invention is implemented as a program product for use with a computer system such as, for example, the computer system <part-num-ref name="computer system">100</part-num-ref>
153
+ shown in Figure 1 and described below. The program product defines functions of the embodiments (including the methods) described herein and can be contained on a variety of signal-bearing media<confidence value="5">.</confidence>
154
+ Illustrative signal-bearing media include, without limitation, (i) information permanently stored on non-writable storage media (e.g., read-only memory devices within a computer such as CD-ROM disks readable by a CD-ROM drive); (ii) alterable information stored on writable storage media (e.g., floppy disks within a diskette drive or hard-disk drive); and (iii) information conveyed across communications media, (e.g., a computer or telephone network) including wireless communications. The latter embodiment specifically includes information shared over the Internet or other large computer networks. Such signal-bearing media, when carrying computer-readable instructions that perform methods of the invention, represent embodiments of the present invention. </p>
155
+ <p id="p-42" num="42">[0037] In general, software routines implementing embodiments of the invention may be part of an operating system or part of a specific application, component, program, module, object, or sequence of instructions such as an executable script.</p>
156
+ <boundary-data type="header">
157
+ <confidence value="8">9</confidence>
158
+ </boundary-data>
159
+ <boundary-data type="header">Atty. Dkt No.: R<confidence value="5">O</confidence>
160
+ C920040202US1 </boundary-data>
161
+ <p id="p-43" num="43">
162
+ <page-break num="10"/>
163
+ Such software routines typically comprise a plurality of instructions capable of being performed using a computer system. Also, programs typically include variables and data structures that reside in memory or on storage devices as part of their operation. In addition, various programs described herein may be identified based upon the application for which they are implemented. Those skilled in the art recognize, however, that any particular nomenclature or specific application that follows facilitates a description of the invention and does not limit the invention for use solely with a specific application or nomenclature. Furthermore, the functionality of programs described herein using discrete modules or components interacting with one another. Those skilled in the art recognize, however, that different embodiments may combine or merge such components and modules in many different ways. </p>
164
+ <p id="p-44" num="44">Physical View of the Annotation Environment [0038<confidence value="5">]</confidence>
165
+ Figure 1 illustrates an exemplary system <part-num-ref name="exemplary system">100</part-num-ref>
166
+ including an annotation management application <part-num-ref name="annotation management application">140,</part-num-ref>
167
+ according to one embodiment of the invention. The universal annotation system <part-num-ref name="universal annotation system">100</part-num-ref>
168
+ may be provided to enterprise users, for example, from a service provider in the business of installing such systems. In an effort to ensure successful deployment of the annotation system <part-num-ref name="annotation system">100,</part-num-ref>
169
+ the service provider may address both the capture and harvest (retrieval) of tacit knowledge in the form of annotations <part-num-ref name="form of annotations">132.</part-num-ref>
170
+ The capture process generally involves users (e.g., people or, in some cases, application programs) entering annotation content about an item of "target" data. Once captured in the form of an annotation <part-num-ref name="annotation">132,</part-num-ref>
171
+ annotations may be stored in annotation store <part-num-ref name="annotation 132, annotations may be stored in annotation store">130.</part-num-ref>
172
+ </p>
173
+ <p id="p-45" num="45">[0039] Users typically create annotations by interacting with software that may be embedded within their particular applications (e.g., as a plug-in component illustrated for application <part-num-ref name="plug-in component illustrated for application">1202)</part-num-ref>
174
+ or, alternatively, with a separate annotation application that is external to their applications, for example, a stand-alone browser or custom application. </p>
175
+ <p id="p-46" num="46">
176
+ <confidence value="5">[</confidence>
177
+ 0040] The annotations <part-num-ref name="annotations">132</part-num-ref>
178
+ may be stored in a central annotation repository such as annotation store <part-num-ref name="central annotation repository such as annotation store">130,</part-num-ref>
179
+ which may be searched either independently or in <boundary-data type="header">
180
+ <confidence value="88">10</confidence>
181
+ </boundary-data>
182
+ <page-break num="11"/>
183
+ <boundary-data type="header">Atty. Dkt No.: R<confidence value="5">O</confidence>
184
+ C920040202US1 </boundary-data>
185
+ conjunction with the annotated data. Annotations <part-num-ref name="annotated data. Annotations">132</part-num-ref>
186
+ describe various data sources, such as documents <part-num-ref name="describe various data sources, such as documents">11<confidence value="86">71</confidence>
187
+ </part-num-ref>
188
+ generated by the manager with a first application <part-num-ref name="first application">
189
+ <confidence value="5882">1201</confidence>
190
+ </part-num-ref>
191
+ (e.g., a word processor), chemical data <part-num-ref name="word processor), chemical data">1172</part-num-ref>
192
+ manipulated by a chemist with a second application <part-num-ref name="second application">1202</part-num-ref>
193
+ (e.g., a database application), and biological data 117N (e.g., genomic data) generated by a biologist with an Nth appli<confidence value="8">c</confidence>
194
+ ation 120N (e<confidence value="66">.g</confidence>
195
+ ., a custom application). </p>
196
+ <p id="p-47" num="47">[0041] Figure 2 illustrates a networked computer system in a client-server configuration. Client computer systems 1<confidence value="5882">051-</confidence>
197
+ N include a network interface allowing communication with server system <part-num-ref name="network interface allowing communication with server system">110</part-num-ref>
198
+ over network <part-num-ref name="over network">104.</part-num-ref>
199
+ The network <part-num-ref name="network">104</part-num-ref>
200
+ may comprise a local area network wherein both the client systems <part-num-ref name="client systems">105</part-num-ref>
201
+ and server system <part-num-ref name="and server system">110</part-num-ref>
202
+ reside in the same general location, or may comprise network connections between geographically distributed systems, including network connections over the Internet. Network connections may be established over physical and wireless links using well known communication protocols. Client systems <part-num-ref name="Internet. Network connections may be established over physical and wireless links using well known communication protocols. Client systems">105</part-num-ref>
203
+ generally include a central processing unit (CPU) connected via a bus, to memory and storage (not shown). Client systems<confidence value="66">10</confidence>
204
+ 5 are running an operating system, (e.g., a Linux<confidence value="5">®</confidence>
205
+ distribution, Microsoft Windows<confidence value="2">®</confidence>
206
+ , International Business Machines' (IBM) AIX<confidence value="5">@</confidence>
207
+ , or Macintosh OSX<confidence value="4">®</confidence>
208
+ ) that manages the interaction between hardware components and higher-level software applications running on client system <part-num-ref name="interaction between hardware components and higher-level software applications running on client system">105.</part-num-ref>
209
+ </p>
210
+ <p id="p-48" num="48">[0042] In one embodiment, a user establishes a network connection between client system <part-num-ref name="network connection between client system">105</part-num-ref>
211
+ and annotation server system <part-num-ref name="and annotation server system">110.</part-num-ref>
212
+ Such a connection may include a login process wherein a user authenticates the user's identity to the server system <part-num-ref name="server system">110</part-num-ref>
213
+ using, for example, a username and password or other authentication schemes (e.g., digital certificates or biometric authentication). Systems that do not require authentication are also contemplated. </p>
214
+ <p id="p-49" num="49">[0043] The server system <part-num-ref name="server system">110</part-num-ref>
215
+ may include hardware components similar to those used by client system <part-num-ref name="may include hardware components similar to those used by client system">105.</part-num-ref>
216
+ Accordingly, the server system <part-num-ref name="server system">110</part-num-ref>
217
+ generally includes a CPU, a memory, and a storage device, coupled one another by a bus. </p>
218
+ <p id="p-50" num="50">The server system 110 is also running an operating system, (e.g., a Linux<confidence value="5">®</confidence>
219
+ <boundary-data type="header">
220
+ <confidence value="88">11</confidence>
221
+ </boundary-data>
222
+ <page-break num="12"/>
223
+ <boundary-data type="header">
224
+ <confidence value="2222">Atty</confidence>
225
+ . Dkt No.: R<confidence value="5">O</confidence>
226
+ C920040202US1 </boundary-data>
227
+ distribution, Microsoft Windows<confidence value="2">®</confidence>
228
+ , IBM's AIX<confidence value="5">@</confidence>
229
+ or <confidence value="686">OS/</confidence>
230
+ 400, FreeBSD, and the like) that manages the interaction between hardware components and higher-level software applications. </p>
231
+ <p id="p-51" num="51">[0044] The client/server configuration illustrated in Figure 2, however, is merely exemplary of one hardware/software configuration. Embodiments of the present invention may be implemented using other configurations, regardless of whether the computer systems are complex multi-user computing systems, such as a cluster of individual computers connected by a high-speed network that acts as a single system, single-user workstations, or network appliances lacking non-volatile storage of their own. Additionally, although described herein using a client/server configuration, embodiments employing distributed computing or peer-to-peer networking techniques are contemplated.</p>
232
+ <p id="p-52" num="52">[0045] In one embodiment, users interact with the server system <part-num-ref name="server system">110</part-num-ref>
233
+ using a graphical user interface (GUI). In a particular embodiment, GUI content may comprise HTML documents (i.e., web-pages) rendered on a client computer system <part-num-ref name="client computer system">
234
+ <confidence value="6666">1051</confidence>
235
+ . </part-num-ref>
236
+ In such case, application <part-num-ref name="client computer system 1051. In such case, application">120</part-num-ref>
237
+ may comprise a known web-browser. In such an embodiment, the server system <part-num-ref name="server system">110</part-num-ref>
238
+ includes a Hypertext Transfer Protocol (http) server <part-num-ref name="Hypertext Transfer Protocol (http) server">118</part-num-ref>
239
+ (e.g., a web server such as the open source Apache web-sever program or IBM's Web Sphere<confidence value="5">@</confidence>
240
+ program) configured to respond to HTTP requests from the client system <part-num-ref name="client system">105</part-num-ref>
241
+ and to transmit HTML documents to client system <part-num-ref name="and to transmit HTML documents to client system">105.</part-num-ref>
242
+ The web- pages themselves may be static documents stored on server system <part-num-ref name="web- pages themselves may be static documents stored on server system">110</part-num-ref>
243
+ or generated dynamically in response to HTTP requests from client system <part-num-ref name="or generated dynamically in response to HTTP requests from client system">105.</part-num-ref>
244
+ </p>
245
+ <p id="p-53" num="53">[0046] As illustrated in Figure 2, server system 110 may further include administrative tools <part-num-ref name="may further include administrative tools">122</part-num-ref>
246
+ and a database management system (DBMS) <part-num-ref name="database management system (DBMS)">124.</part-num-ref>
247
+ Each of these components may comprise a software program executing on the server system <part-num-ref name="server system">110.</part-num-ref>
248
+ The DBMS server <part-num-ref name="DBMS server">124</part-num-ref>
249
+ (or servers) generally comprises a software application configured to manage databases, including the annotation store <part-num-ref name="annotation store">130.</part-num-ref>
250
+ </p>
251
+ <p id="p-54" num="54">For some embodiments, the annotation management application <part-num-ref name="annotation management application">140,</part-num-ref>
252
+ and various related components, may be configured via a set of administrative tools <part-num-ref name="set of administrative tools">122.</part-num-ref>
253
+ For example, the administrative tools <part-num-ref name="administrative tools">122</part-num-ref>
254
+ may be used to generate a set of annotation <boundary-data type="header">
255
+ <confidence value="88">12</confidence>
256
+ </boundary-data>
257
+ <page-break num="13"/>
258
+ <boundary-data type="header">Atty. Dkt No.: R<confidence value="5">O</confidence>
259
+ C920040202US1 </boundary-data>
260
+ configuration files. In one embodiment, the annotation server <part-num-ref name="annotation server">140</part-num-ref>
261
+ comprises the software process configured to provide annotation functionally to users interacting with applications <part-num-ref name="software process configured to provide annotation functionally to users interacting with applications">120.</part-num-ref>
262
+ The annotation server <part-num-ref name="annotation server">140</part-num-ref>
263
+ includes routines to create, identify and store annotations. Additionally, the annotation server <part-num-ref name="annotation server">140</part-num-ref>
264
+ may be configured to communicate with HTTP server <part-num-ref name="may be configured to communicate with HTTP server">118</part-num-ref>
265
+ and DBMS server <part-num-ref name="and DBMS server">124</part-num-ref>
266
+ using well known inter-process communication techniques. </p>
267
+ <p id="p-55" num="55">[0047] Figure 3 illustrates an annotation database <part-num-ref name="annotation database">130.</part-num-ref>
268
+ In one embodiment, a user creates an annotation for an item of data in a document accessed by application <part-num-ref name="document accessed by application">120.</part-num-ref>
269
+ The annotation manager <part-num-ref name="annotation manager">140</part-num-ref>
270
+ receives annotation content and stores it in annotation store <part-num-ref name="receives annotation content and stores it in annotation store">130.</part-num-ref>
271
+ In one embodiment, annotation store <part-num-ref name="receives annotation content and stores it in annotation store 130. In one embodiment, annotation store">130</part-num-ref>
272
+ may include index table <part-num-ref name="may include index table">304</part-num-ref>
273
+ that stores an index value <part-num-ref name="index value">136,</part-num-ref>
274
+ the Family ID <part-num-ref name="Family ID">306,</part-num-ref>
275
+ version ID <part-num-ref name="Family ID 306, version ID">308</part-num-ref>
276
+ and any other metadata (illustrated by columns 2-N) for each annotation. For example, additional annotation metadata may indicate a point within the document (such as a page, paragraph, and line number for a text document) that identifies the data element within the document that is annotated by the annotation. An annotation record <part-num-ref name="annotation record">131</part-num-ref>
277
+ may comprise the index value <part-num-ref name="index value">136</part-num-ref>
278
+ for the annotation and the annotation content <part-num-ref name="annotation content">135.</part-num-ref>
279
+ The annotation record may also include a pointer to a copy of version of the document for which the annotation was created, that is, the annotation database may also store a copy of each version for each version of a document for which annotations are created. The relationship between an annotation index <part-num-ref name="annotation index">136</part-num-ref>
280
+ and a document need not be one-to-one, however, and one annotation may be indexed to multiple versions of a document within a document family. Alternatively, the same annotation may appear with multiple indexes, each one associated with a different version of a document. Annotation database <part-num-ref name="document. Annotation database">130</part-num-ref>
281
+ may be part of the annotation server process, or may comprise a separate database managed by DBMS <part-num-ref name="separate database managed by DBMS">124.</part-num-ref>
282
+ </p>
283
+ <p id="p-56" num="56">[0048] Each family ID may comprise a unique value generated for a document family. As used herein, a document family generally comprises successive versions of a document. Each time the document is modified (i.e., new content is added, current content removed, or some combination thereof) a new version ID is generated for the document, and the family ID is associated with the new version. In <boundary-data type="header">
284
+ <confidence value="88">13</confidence>
285
+ </boundary-data>
286
+ <page-break num="14"/>
287
+ <boundary-data type="header">
288
+ <confidence value="2222">Atty</confidence>
289
+ . Dkt No.: R<confidence value="5">O</confidence>
290
+ C920040202US1 </boundary-data>
291
+ <confidence value="2">-</confidence>
292
+ one embodiment, the version ID may be generated dynamically when needed form a particular version of the document. For example, a version ID may comprise a hash value such as an MD5 or SHA<confidence value="5">1</confidence>
293
+ hash of the current version of the document in the document family. The family ID may comprise a universally unique identifier such as an O<confidence value="5">I</confidence>
294
+ D or GU<confidence value="5">I</confidence>
295
+ D. Alternatively, a hash value corresponding to the first version of the document may be used as the family ID. Whether generated using hash functions or GUID values however, the family ID is associated with all versions of a document for a given family, and the version IDs are unique to each version of a document. To facilitate the description of the invention, simple character identifiers are used to represent family and version IDs. </p>
296
+ <p id="p-57" num="57">[0049] Figure 4A illustrates an exemplary GUI interface screen <part-num-ref name="exemplary GUI interface screen">402</part-num-ref>
297
+ displayed to a user interacting with application <part-num-ref name="user interacting with application">120.</part-num-ref>
298
+ In this example, the screen shows text content <part-num-ref name="screen shows text content">405.</part-num-ref>
299
+ In addition, the presence of an annotation for data in the document is indicated by annotation icon <part-num-ref name="document is indicated by annotation icon">404.</part-num-ref>
300
+ In an embodiment where annotations are managed using a web-based interface, the annotation icon may include a hyperlink. </p>
301
+ <p id="p-58" num="58">When clicked, the hyperlink causes a view annotation window <part-num-ref name="view annotation window">406</part-num-ref>
302
+ to open. In various embodiments, annotations associated with a document may be identified each time a user accesses a document, or in response to a user request to view annotations. Techniques for managing annotations are illustrated in detail in a commonly owned co-pending application entitled commonly owned, co-pending U.S. </p>
303
+ <p id="p-59" num="59">patent application, U.S. Serial No. 10/600,014, filed June 20, 2003, entitled, "Universal Annotation Management System" U.S. incorporated by reference in its entirety. In addition, version metadata 408 (not displayed to a user, as represented by the dashed lines) corresponding to the document viewed by application <part-num-ref name="document viewed by application">120</part-num-ref>
304
+ is stored with the document being viewed. In one embodiment, this metadata may include the associated family ID indicating the family associated with the document, as well as the version ID associated with the current document. The version metadata corresponds to annotation metadata <part-num-ref name="version metadata corresponds to annotation metadata">405</part-num-ref>
305
+ which indicates that the annotation <part-num-ref name="annotation">406</part-num-ref>
306
+ is associated with the document family <confidence value="5">"</confidence>
307
+ 1" and version "A." [0050] Figure 4B illustrates the same GUI screen <part-num-ref name="same GUI screen">402</part-num-ref>
308
+ displayed on application <part-num-ref name="displayed on application">120,</part-num-ref>
309
+ after being modified,<confidence value="1">-</confidence>
310
+ as illustrated by added content <part-num-ref name="displayed on application 120, after being modified,-as illustrated by added content">410</part-num-ref>
311
+ and new annotation <boundary-data type="header">
312
+ <confidence value="88">14</confidence>
313
+ </boundary-data>
314
+ <page-break num="15"/>
315
+ <boundary-data type="header">
316
+ <confidence value="2222">Atty</confidence>
317
+ . Dkt No.: R<confidence value="5">O</confidence>
318
+ C920040202US1 </boundary-data>
319
+ <part-num-ref name="and new annotation">412</part-num-ref>
320
+ indicated by annotation icon <part-num-ref name="indicated by annotation icon">413.</part-num-ref>
321
+ Because the document is modified, the version ID has been incremented. Accordingly, the version ID illustrated in Figure 4B is different than the version ID illustrated in Figure 4A. However, because both versions are part of the same document family, the Family ID remains the same. </p>
322
+ <p id="p-60" num="60">Annotation 412 is an annotation created for the second version of the document.</p>
323
+ <p id="p-61" num="61">Note, however, the annotation icon displayed in Figure 4A is not displayed as part of the document display <part-num-ref name="document display">405</part-num-ref>
324
+ in Figure 4B. This occurs because the version ID (namely, version "A" shown by annotation metadata <part-num-ref name="version ID (namely, version &quot;A&quot; shown by annotation metadata">414)</part-num-ref>
325
+ associated with the annotation <part-num-ref name="annotation">406</part-num-ref>
326
+ is different than the version ID for document <part-num-ref name="version ID for document">405</part-num-ref>
327
+ (namely, "B" after the modifications) identified version metadata <part-num-ref name="modifications) identified version metadata">408.</part-num-ref>
328
+ In one embodiment, family annotation display <part-num-ref name="modifications) identified version metadata 408. In one embodiment, family annotation display">407</part-num-ref>
329
+ may be used to indicate that annotations are available for prior (or subsequent) versions of the current document being accessed by application <part-num-ref name="current document being accessed by application">120.</part-num-ref>
330
+ As illustrated, family annotation display window <part-num-ref name="current document being accessed by application 120. As illustrated, family annotation display window">407</part-num-ref>
331
+ includes link <part-num-ref name="includes link">420.</part-num-ref>
332
+ Depending on the changes made between versions, the data that was annotated by the annotation may no longer exist in the current document. In one embodiment, the family annotation display window <part-num-ref name="family annotation display window">407</part-num-ref>
333
+ allows a user to view annotations created for other versions of the current document, in their original context, using the version of the document for which they were created by displaying the annotated content from the other version of the document. </p>
334
+ <p id="p-62" num="62">[0051] Figure 5 illustrates a time-lapse view of a document as it undergoes a series of modifications made to the document (document states 502- 510), the state of the annotation metadata for each version of the document (metadata 512-520), and information stored in the annotation database (states 522-530). The initial version of the document <part-num-ref name="document">502</part-num-ref>
335
+ is the original version. Associated with this version, and all subsequent versions, is<confidence value="5">-</confidence>
336
+ the family ID of "1" stored in document metadata (states 512-520). For convenience, as illustrated in Figure 5, annotations are indicated using "*" symbols. </p>
337
+ <p id="p-63" num="63">[0052] Initially, at state 502, the document metadata <part-num-ref name="document metadata">512</part-num-ref>
338
+ indicates family ID "1" and version ID "A." The document contains a single annotation <part-num-ref name="single annotation">532.</part-num-ref>
339
+ These IDs are reflected in the annotation store at <part-num-ref name="annotation store at">522.</part-num-ref>
340
+ At document state <part-num-ref name="annotation store at 522. At document state">504,</part-num-ref>
341
+ a second annotation <part-num-ref name="second annotation">534</part-num-ref>
342
+ is added to the document, and the annotation store <part-num-ref name="annotation store">534</part-num-ref>
343
+ is updated <boundary-data type="header">
344
+ <confidence value="88">15</confidence>
345
+ </boundary-data>
346
+ <page-break num="16"/>
347
+ <boundary-data type="header">Atty. Dkt No.: R<confidence value="5">O</confidence>
348
+ C920040202US1 </boundary-data>
349
+ with the second annotation. The version ID in metadata <part-num-ref name="version ID in metadata">514</part-num-ref>
350
+ remains unchanged at state <part-num-ref name="remains unchanged at state">504,</part-num-ref>
351
+ because no changes are made to document <part-num-ref name="remains unchanged at state 504, because no changes are made to document">504,</part-num-ref>
352
+ only to the annotations. </p>
353
+ <p id="p-64" num="64">In one embodiment, annotations are stored independently from the document, and adding annotations to an uncharged document do not require an update to the version ID.</p>
354
+ <p id="p-65" num="65">[0053] Subsequently, new content 507 is added to the document at state <part-num-ref name="document at state">506.</part-num-ref>
355
+ </p>
356
+ <p id="p-66" num="66">Once the document is modified and saved, the version ID "A" is longer valid.</p>
357
+ <p id="p-67" num="67">Accordingly, the annotation manager <part-num-ref name="annotation manager">140</part-num-ref>
358
+ may be configured to update the version ID stored with annotation metadata with a new version ID. In one embodiment, the annotation manager also saves a copy of the new document version. Doing so allows annotations created for a given version to be displayed in context of that version. As illustrated, the Version ID stored in metadata <part-num-ref name="Version ID stored in metadata">516</part-num-ref>
359
+ is updated to "B," at state <part-num-ref name="is updated to &quot;B,&quot; at state">506.</part-num-ref>
360
+ Also, the first and second annotations created for the prior version are no longer displayed with the document because the version ID corresponding to these annotations refers to a prior version ID (namely, version ID "A"). Further, the state <part-num-ref name="state">506</part-num-ref>
361
+ includes a third annotation <part-num-ref name="third annotation">538.</part-num-ref>
362
+ As illustrated, the third annotation <part-num-ref name="third annotation">538</part-num-ref>
363
+ is created for data from new content <part-num-ref name="is created for data from new content">507,</part-num-ref>
364
+ however, annotations may be created for any portion of the document <part-num-ref name="document">506.</part-num-ref>
365
+ </p>
366
+ <p id="p-68" num="68">[0054] Annotation store 526 includes the first and second annotations, indexed to the prior document version ID, along with the third annotation. If a user accesses the prior version and requests annotations, the annotation server <part-num-ref name="annotation server">140</part-num-ref>
367
+ will return the <confidence value="666">"*"</confidence>
368
+ and "<confidence value="66">**</confidence>
369
+ " annotations. All three annotations are indexed to the same document family ID, "1", and a query for all of the annotations in the document family will return annotations "<confidence value="558">*",</confidence>
370
+ <confidence value="2">"</confidence>
371
+ and <confidence value="666626">"***."</confidence>
372
+ At state <part-num-ref name="document family will return annotations &quot;*&quot;, &quot; and &quot;***.&quot; At state">508,</part-num-ref>
373
+ the document includes the view prior annotations display <part-num-ref name="view prior annotations display">509</part-num-ref>
374
+ from Figure 4B. This display allows a user to review annotations from other versions of the document. Depending on the version of a document being accessed, the display <part-num-ref name="display">509</part-num-ref>
375
+ may include annotations created for both prior versions and subsequent versions of the document. </p>
376
+ <p id="p-69" num="69">
377
+ <confidence value="86666">[0055</confidence>
378
+ ] In one embodiment, a user interacting with the annotation manager <part-num-ref name="annotation manager">140</part-num-ref>
379
+ may choose to associate annotations from other versions of the document with the <boundary-data type="header">
380
+ <confidence value="88">16</confidence>
381
+ </boundary-data>
382
+ <page-break num="17"/>
383
+ <boundary-data type="header">Atty. Dkt No.: R<confidence value="5">O</confidence>
384
+ C920040202US1 </boundary-data>
385
+ current one. Accordingly, document state <part-num-ref name="current one. Accordingly, document state">510</part-num-ref>
386
+ illustrates the document with annotation <part-num-ref name="document with annotation">542</part-num-ref>
387
+ and <part-num-ref name="and">544</part-num-ref>
388
+ which represent the annotations from document state <part-num-ref name="annotations from document state">504</part-num-ref>
389
+ re-associated with the current document. As illustrated, the database store <part-num-ref name="database store">530</part-num-ref>
390
+ includes index for annotation "<confidence value="5">*</confidence>
391
+ " and <confidence value="5885">"**"</confidence>
392
+ for both the "A" version of the document and the "B" version of the document. In one embodiment, when an annotation is associated with the current version of the document, it is no longer displayed in the display area <part-num-ref name="display area">509.</part-num-ref>
393
+ </p>
394
+ <p id="p-70" num="70">Operational Methods [0056] Figure 6A illustrates a method <part-num-ref name="method">600</part-num-ref>
395
+ to add annotations to a current version of a document, according to one embodiment of the invention. The method begins at step <part-num-ref name="method begins at step">610</part-num-ref>
396
+ where the annotation manager <part-num-ref name="annotation manager">140</part-num-ref>
397
+ receives a request to create an annotation for data content present in a current version of a document. For example, a user interacting with a word processing application may desire to annotate a passage of text appearing in the document. At step <part-num-ref name="document. At step">612,</part-num-ref>
398
+ the method queries whether the document being accessed has been modified. If so, the method moves to step <part-num-ref name="method moves to step">614,</part-num-ref>
399
+ further illustrated in Figure 6B. Otherwise, the method proceeds to step <part-num-ref name="method proceeds to step">616</part-num-ref>
400
+ where the annotation manager <part-num-ref name="annotation manager">140</part-num-ref>
401
+ retrieves the family and version ID for the current document. If this is the first time an annotation has been created for the document, then the annotation manger <part-num-ref name="annotation manger">140</part-num-ref>
402
+ may generate a family ID and associate it with the document. Next, the user is prompted to provide annotation content. For example, a user may indicate what data content is being annotated, as well as the content of the annotation. At step <part-num-ref name="annotation. At step">620,</part-num-ref>
403
+ the annotation content may be added to the annotation store, and stored with the appropriate family ID, and version ID in index table <part-num-ref name="appropriate family ID, and version ID in index table">304.</part-num-ref>
404
+ </p>
405
+ <p id="p-71" num="71">[0057] Figure 6B illustrates a method to create an annotation for a modified version of a current document. Like method <part-num-ref name="current document. Like method">600,</part-num-ref>
406
+ operations <part-num-ref name="current document. Like method 600, operations">622</part-num-ref>
407
+ begin at step <part-num-ref name="begin at step">624</part-num-ref>
408
+ where the annotation manager <part-num-ref name="annotation manager">140</part-num-ref>
409
+ receives a request to create an annotation for data content present in a current document. At step <part-num-ref name="current document. At step">626,</part-num-ref>
410
+ the method <part-num-ref name="method">622</part-num-ref>
411
+ queries whether the document being accessed has been modified. If not, then, at step <part-num-ref name="document being accessed has been modified. If not, then, at step">628,</part-num-ref>
412
+ an annotation may be created according to the method illustrated in Figure 6A. </p>
413
+ <boundary-data type="header">
414
+ <confidence value="88">17</confidence>
415
+ </boundary-data>
416
+ <boundary-data type="header">
417
+ <confidence value="2222">Atty</confidence>
418
+ . Dkt No.: R<confidence value="5">O</confidence>
419
+ C920040202US1 </boundary-data>
420
+ <p id="p-72" num="72">
421
+ <page-break num="18"/>
422
+ Next, if the document has been modified, the annotation manager <part-num-ref name="annotation manager">140</part-num-ref>
423
+ retrieves the family ID and for the document. Because the document has been modified, a new version ID is assigned to the current document at step <part-num-ref name="current document at step">632.</part-num-ref>
424
+ </p>
425
+ <p id="p-73" num="73">[0058] At step 634, the annotation manager <part-num-ref name="annotation manager">140</part-num-ref>
426
+ prompts a user for new annotation content. At step <part-num-ref name="user for new annotation content. At step">636,</part-num-ref>
427
+ the new annotation is stored in the annotation store with the family ID and new version ID. While the user interacts with the document, additional new annotations may be created. Thus, loop <part-num-ref name="document, additional new annotations may be created. Thus, loop">635</part-num-ref>
428
+ illustrates that step <part-num-ref name="illustrates that step">634</part-num-ref>
429
+ and step <part-num-ref name="and step">636</part-num-ref>
430
+ may be repeated. One a user has finished modifying a document, the modified document is saved. Optionally, at step <part-num-ref name="modified document is saved. Optionally, at step">640,</part-num-ref>
431
+ the annotation manager <part-num-ref name="annotation manager">140</part-num-ref>
432
+ may prompt the user to selectively choose which annotations from the previous version are still relevant to the modified version. At step <part-num-ref name="modified version. At step">642,</part-num-ref>
433
+ if the user has chosen to include any annotations from a prior version into the current version of the document, then any selected annotations are modified to include a reference to the version ID of the current document. Alternatively, a new annotation (copying the annotation from the other version) may be created that includes the version ID from the current document, e.g., the "<confidence value="2">*</confidence>
434
+ " and <confidence value="6666">"**"</confidence>
435
+ duplicated for both versions of the document in annotation store <part-num-ref name="document in annotation store">530.</part-num-ref>
436
+ </p>
437
+ <p id="p-74" num="74">[0059<confidence value="4">]</confidence>
438
+ Figure 6<confidence value="5">C</confidence>
439
+ illustrates a method <part-num-ref name="method">645</part-num-ref>
440
+ for viewing annotations created for different versions of a document family, including the current version, according to one embodiment of the invention. The method <part-num-ref name="method">645</part-num-ref>
441
+ begins at step <part-num-ref name="begins at step">650</part-num-ref>
442
+ when a user opens a document. At step <part-num-ref name="document. At step">652,</part-num-ref>
443
+ the annotation manager retrieves the family ID for the document. In one embodiment, this step may occur each time a user access a document for which annotations may be created. If the document opened at step <part-num-ref name="document opened at step">650</part-num-ref>
444
+ does not have an associated family ID, then no annotations have been created for the document. If the document has a family ID, then the version ID for the current document is also determined. At step <part-num-ref name="current document is also determined. At step">654,</part-num-ref>
445
+ the annotation manger <part-num-ref name="annotation manger">140</part-num-ref>
446
+ identifies annotations created for the current version of the document by matching the version ID with the version IDs of annotations in the annotation store. </p>
447
+ <p id="p-75" num="75">[0060] At step 655, annotations created for other versions of the document are identified. That is, at step <part-num-ref name="document are identified. That is, at step">655,</part-num-ref>
448
+ annotations created for prior, or subsequent, <boundary-data type="header">
449
+ <confidence value="88">18</confidence>
450
+ </boundary-data>
451
+ <page-break num="19"/>
452
+ <boundary-data type="header">
453
+ <confidence value="2222">Atty</confidence>
454
+ . Dkt No.: R<confidence value="5">O</confidence>
455
+ C920040202US1 </boundary-data>
456
+ versions of the current document are identified by identifying annotations with a matching family ID, but different version IDs. </p>
457
+ <p id="p-76" num="76">
458
+ <confidence value="5">[</confidence>
459
+ 0061] At step 656, an indication of annotations identified at steps <part-num-ref name="indication of annotations identified at steps">654</part-num-ref>
460
+ and <part-num-ref name="and">655</part-num-ref>
461
+ are displayed. In an environment employing a graphical user interface, this may include displaying an annotation icon at the point in the data source corresponding to the annotation. In one embodiment, an annotation icon may comprise an image displayed for an anchor tag in an HTML document like the following: </p>
462
+ <p id="p-77" num="77">&lt;A href=http://annotations.ibm.com/retreiveglobal.php?index=1729/&gt; <confidence value="82">&lt;I</confidence>
463
+ MG SRC=icon.gif<confidence value="5">"</confidence>
464
+ WIDTH<confidence value="588">="1</confidence>
465
+ 5" HE<confidence value="5">I</confidence>
466
+ GHT<confidence value="58886">="15"</confidence>
467
+ BORDER<confidence value="6845">="0"</confidence>
468
+ &gt; &lt;<confidence value="588">/A&gt;</confidence>
469
+ This way, the annotation ID, <part-num-ref name="annotation ID,">1729</part-num-ref>
470
+ in this example, is encoded into the display of the document. Doing so simplifies the annotation retrieval process and improves the efficiency of the annotation manger running <part-num-ref name="annotation manger running">140</part-num-ref>
471
+ on server system <part-num-ref name="on server system">110.</part-num-ref>
472
+ </p>
473
+ <p id="p-78" num="78">
474
+ <confidence value="5">[</confidence>
475
+ 0062] Also, at step 656 an indication of the availability of annotations from other versions is displayed. For example, the prior annotation window illustrated in Figure 4B may be displayed. Alternately, a user may request an indication of prior annotations using a menu selection or GUI interface button associated with the annotation manger <part-num-ref name="annotation manger">140</part-num-ref>
476
+ or application <part-num-ref name="or application">120.</part-num-ref>
477
+ At step <part-num-ref name="or application 120. At step">658,</part-num-ref>
478
+ annotation content, for both the current version (step 660), or other versions (steps <part-num-ref name="current version (step 660), or other versions (steps">662</part-num-ref>
479
+ - <part-num-ref name="-">666)</part-num-ref>
480
+ are displayed in response to a user request to view annotation content. </p>
481
+ <p id="p-79" num="79">[0063] If a user requests to view an annotation created for the current version of the document (e.g., clicks on an annotation icon displayed at step 656), then at step <part-num-ref name="annotation icon displayed at step 656), then at step">660,</part-num-ref>
482
+ the annotation corresponding to the index value encoded in the icon is used to retrieve the annotation from the annotation store <part-num-ref name="annotation store">630.</part-num-ref>
483
+ If a user requests to view an annotation created for a different version of the document in the document family, then at step <part-num-ref name="document family, then at step">662,</part-num-ref>
484
+ the annotation created for the another version is retrieved. In addition, at step <part-num-ref name="another version is retrieved. In addition, at step">664,</part-num-ref>
485
+ the annotation manger <part-num-ref name="annotation manger">140</part-num-ref>
486
+ may be configured to retrieve the version of the document in the document family used to create the annotation at step <part-num-ref name="annotation at step">662.</part-num-ref>
487
+ Doing so allows a user to view an annotation from another version of the current document in the same context that it was created. Next at step <part-num-ref name="same context that it was created. Next at step">666,</part-num-ref>
488
+ a user <boundary-data type="header">
489
+ <confidence value="88">19</confidence>
490
+ </boundary-data>
491
+ <page-break num="20"/>
492
+ <boundary-data type="header">Atty. Dkt No.: R<confidence value="5">O</confidence>
493
+ C920040202US1 </boundary-data>
494
+ may choose to associate an annotation originally created for a different version of the document in the family with the version ID of the current document. </p>
495
+ <p id="p-80" num="80">Conclusion [0064] By associating annotations with both a family ID and a version ID, embodiments of the invention provide a convenient annotation system that manages annotations created for a document family. Users may view annotations for the current version of a document, as well as annotations created for prior, or subsequent, versions of the same document. Because these annotations may still be useful for the current document, users may selective choose to associate annotations from other versions with the current version of a document.</p>
496
+ <p id="p-81" num="81">[0065] While the foregoing is directed to embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof, and the scope thereof is determined by the claims that follow.</p>
497
+ <boundary-data type="header">
498
+ <confidence value="88">20</confidence>
499
+ </boundary-data>
500
+ </description>
501
+ </us-patent-application>
502
+
prior_art/11035472.xml ADDED
@@ -0,0 +1,705 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11035472</doc-number>
8
+ <date>2005-01-14</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
14
+ <heading id="h-1">METHODS, SYSTEMS AND COMPUTER PROGRAM PRODUCTS FOR</heading>
15
+ <heading id="h-2">ANALOGY DETECTION AMONG ENTITIES USING RECIPROCAL</heading>
16
+ <heading id="h-3">SIMILARITY MEASURES</heading>
17
+ <p id="p-1" num="1">Federally S<confidence value="5">p</confidence>
18
+ onsored Research <confidence value="5">[</confidence>
19
+ 0001<confidence value="5">]</confidence>
20
+ This invention was made at least in part with government support under Defense Advance Research Projects Agency (DARPA), Contract No. </p>
21
+ <p id="p-2" num="2">MDA972-03-9-<confidence value="666">001</confidence>
22
+ . The government may have certain rights to this invention. </p>
23
+ <p id="p-3" num="3">Field of the Invention <confidence value="5">[</confidence>
24
+ 0002<confidence value="5">]</confidence>
25
+ This invention relates to knowledge management methods, systems and computer program products, and more particularly to methods, systems and computer program products that can detect analogies. </p>
26
+ <p id="p-4" num="4">Background of the Invention <confidence value="5">[</confidence>
27
+ 0003<confidence value="5">]</confidence>
28
+ Associative memories, also referred to as content addressable memories, are widely used in the field of pattern matching and identification, expert systems, artificial intelligence and analogy detection. As used herein, analogy detection is an associative memory function that finds similar things to a given thing. </p>
29
+ <p id="p-5" num="5">Analogy detection may be useful for data cleansing, alias detection, and other applications. Analogy-based reasoning also can use analogy detection across a set of related things, and may be used for many different applications, including hypothesis generation.</p>
30
+ <p id="p-6" num="6">
31
+ <confidence value="5">[</confidence>
32
+ 0004<confidence value="5">]</confidence>
33
+ For analogy detection, similarity is generally used as a defining criteria. However, similarity metrics by themselves may not provide decisions. For example, everything may be considered similar to everything else, even if the only element in common is in being a "thing". Thus, analogy detection should decide how much similarity is needed to consider two things as effectively the same, given the task at hand. Conventional analogy detection may determine similarity by setting a threshold which is based on the tradeoffs between hits, missed opportunities, false alarms and correct rejections. Other conventional analogy detection may include such <boundary-data type="header">
34
+ <confidence value="6">1</confidence>
35
+ </boundary-data>
36
+ <page-break num="2"/>
37
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
38
+ decision theories as hyperplane separation models which may try to fit the data on one or another side of a separation plane. </p>
39
+ <p id="p-7" num="7">[0005<confidence value="4">]</confidence>
40
+ It is also known to use various measurements of similarity by considering the similarity of two objects, each described as a vector of attributes. For example, the cosine of the angle between two vectors is known as a measure of document similarity. Jacquard similarity, the proportion of overlapping attributes, is also known in building biological taxonomies. Edit distance is yet another measure that may be used for alphabet detection, such as when comparing text strings of letters or protein sequences of amino acids. </p>
41
+ <p id="p-8" num="8">
42
+ <confidence value="5">[</confidence>
43
+ 0006] Similarity measures also may be an underlying basis for clustering, such as in methods for market segmentation of hierarchical classification. K-mean clustering can be used to place an item in one group or another, wherein the group is best defined by its average center. Bootstrapping techniques also may be used to look for similarities from a graph perspective, by traversing links in search for other nodes that share the same connections. Finally, mutual neighbor techniques, also called shared nearest neighbor techniques, look to confirm each node-node value in a similarity matrix by also asking how well the similar nodes share the same set of nearest neighbors. </p>
44
+ <p id="p-9" num="9">[0007] Notwithstanding these and/or other techniques, there continues to be a desire to provide analogy detection methods, systems and computer program products that can provide more accurate analogy detection among large numbers of entities, for alias detection, data cleansing and/or other applications.</p>
45
+ <p id="p-10" num="10">Summary of the Invention [0008] Analogies among a plurality of entities may be detected according to various embodiments of the present invention, by obtaining associative counts among the plurality of entities and computing respective similarity measures among respective given entities and other entities among the plurality of entities, using the associative counts. First and second entities are then identified from the plurality of entities as being analogies if the first entity has a strongest similarity measure with respect to the second entity and the second entity also has a strongest similarity measure with respect to the first entity. After identifying the first and second entities, other entities in the plurality of entities also may be identified as being analogies of <boundary-data type="header">
46
+ <confidence value="8">2</confidence>
47
+ </boundary-data>
48
+ <page-break num="3"/>
49
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
50
+ the first and/or second entities. Accordingly, reciprocal similarity measures are used to determine analogies, in some embodiments of the invention. </p>
51
+ <p id="p-11" num="11">
52
+ <confidence value="5">[</confidence>
53
+ 0009<confidence value="5">1</confidence>
54
+ Various techniques may be used in other embodiments of the present invention to compute the respective similarity measures among respective given entities and other entities among the plurality of entities using the associative counts. </p>
55
+ <p id="p-12" num="12">These techniques also may be used to compute similarity measures independent of analogy detecting according to various embodiments of the present invention. In some embodiments, a normalized entropy inverted among a respective given entity and other entities among a plurality of entities is computed, using the associative counts. In other embodiments, a similarity of the given entity to another entity from a perspective of a third entity, relative to an overall similarity of entities to one another from the perspective of the third entity, is computed. This computation may take place by computing a pair entropy of the given entity and the other entity from the perspective of the third entity, computing an overall entropy of entities to one another from the perspective of the third entity, computing a maximum overall entropy of entities to one another from the perspective of the third entity, and combining the pair entropy, the overall entropy, and the maximum overall entropy. Combining may take place by dividing the overall entropy minus the pair entropy by a log of the maximum overall entropy, to obtain a result. In other embodiments, the result is subtracted from one <confidence value="8688">(1).</confidence>
56
+ </p>
57
+ <p id="p-13" num="13">[0010<confidence value="5">]</confidence>
58
+ In some embodiments, the respective similarity measures among the respective given entities and the other entities among the plurality of entities may be computed by identifying candidate entities from among the plurality of entities, and computing respective similarity measures among the respective given entities and the candidate entities, using the associative counts. Moreover, in some embodiments, the candidate entities may be identified by obtaining an entity associative memory that identifies associations among the other entities from a perspective of the given entity, and using the associations that are identified in the entity associative memory to identify the candidate entities. In still other embodiments, the overall entropy of the plurality of entities to one another from the perspective of the third entity may be computed by incrementing at least one variable as new associative counts are obtained, so that the overall entropy need not be recomputed as new associative counts are obtained. </p>
59
+ <boundary-data type="header">
60
+ <confidence value="8">3</confidence>
61
+ </boundary-data>
62
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
63
+ <p id="p-14" num="14">
64
+ <page-break num="4"/>
65
+ <confidence value="5">[</confidence>
66
+ 0011<confidence value="5">1</confidence>
67
+ It will be understood that embodiments of the invention have been described above primarily with respect to method embodiments. However, analogous system embodiments and/or analogous computer program product <confidence value="8">e</confidence>
68
+ mbodiments also may be provided. </p>
69
+ <p id="p-15" num="15">Brief Description of the Drawin<confidence value="68">gs</confidence>
70
+ <confidence value="5">[</confidence>
71
+ 0012<confidence value="4">]</confidence>
72
+ Figure 1 is a block diagram of analogy detection methods, systems and/or computer program products according to various embodiments of the present invention. </p>
73
+ <p id="p-16" num="16">[0013<confidence value="5">]</confidence>
74
+ Figure 2 is a flowchart of operations that may be performed to detect analogies according to various embodiments of the present invention. </p>
75
+ <p id="p-17" num="17">[0014] Figure 3 is a flowchart of operations that may be performed to compute similarity measures according to various embodiments of the present invention.</p>
76
+ <p id="p-18" num="18">[0015] Figures 4 and <part-num-ref name="and">5</part-num-ref>
77
+ are block diagrams of memories that may be used according to various embodiments of the present invention. </p>
78
+ <p id="p-19" num="19">
79
+ <confidence value="5">[</confidence>
80
+ 0016<confidence value="5">]</confidence>
81
+ Figure 6 is a block diagram of an example of memories of Figure 5 that are populated with data for eight example entities, according to exemplary embodiments of the present invention. </p>
82
+ <p id="p-20" num="20">[0017] Figure 7 is a flowchart of operations that may be performed to compute similarity measures according to various embodiments of the present invention.</p>
83
+ <p id="p-21" num="21">[0018] Figure 8 is a flowchart of operations that may be performed to obtain an associative signature according to various embodiments of the present invention.</p>
84
+ <p id="p-22" num="22">[0019] Figure 9 illustrates an example of obtaining an associative signature according to embodiments of Figure 8.</p>
85
+ <p id="p-23" num="23">[0020] Figure 10 is a flowchart of operations that may be performed to obtain nearest neighbor candidates according to various embodiments of the present invention.</p>
86
+ <p id="p-24" num="24">[0021] Figure 11 is an example of obtaining nearest neighbor candidates according to embodiments of Figure 10.</p>
87
+ <p id="p-25" num="25">[0022] Figure 12 is a flowchart of operations that may be performed to compute analog information according to various embodiments of the present invention.</p>
88
+ <p id="p-26" num="26">[0023] Figure 13 illustrates an example of computing analog information according to embodiments of Figure 12.</p>
89
+ <boundary-data type="header">
90
+ <confidence value="8">4</confidence>
91
+ </boundary-data>
92
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
93
+ <p id="p-27" num="27">
94
+ <page-break num="5"/>
95
+ <confidence value="5">[</confidence>
96
+ 0024<confidence value="5">]</confidence>
97
+ Figure 14 illustrates identifying reciprocal entities according to various embodiments of the present invention. </p>
98
+ <p id="p-28" num="28">
99
+ <confidence value="5">[</confidence>
100
+ 0025<confidence value="4">]</confidence>
101
+ Figure 15 is a flowchart of operations that may be used to determine reciprocal coherence according to various embodiments of the present invention. </p>
102
+ <p id="p-29" num="29">
103
+ <confidence value="5">[</confidence>
104
+ 0026] Figure 16 illustrates an example of a reciprocal coherence set that may be obtained according to various embodiments of the present invention. </p>
105
+ <p id="p-30" num="30">
106
+ <confidence value="5">[</confidence>
107
+ 0027<confidence value="5">]</confidence>
108
+ Figure 17 illustrates construction of a subgraph of similarities according to various embodiments of the present invention. </p>
109
+ <p id="p-31" num="31">Detailed Description <confidence value="5">[</confidence>
110
+ 0028<confidence value="5">]</confidence>
111
+ The present invention now will be described more fully hereinafter with reference to the accompanying drawings, in which illustrative embodiments of the invention are shown. However, this invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. </p>
112
+ <p id="p-32" num="32">Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.</p>
113
+ <p id="p-33" num="33">
114
+ <confidence value="5">[</confidence>
115
+ 0029] It will be understood that when an element is referred to as being "coupled", "connected" or "responsive" to another element, it can be directly coupled, connected or responsive to the other element or intervening elements may also be present. In contrast, when an element is referred to as being "directly coupled", "directly connected" or "directly responsive" to another element, there are no intervening elements present. Like numbers refer to like elements throughout. As used herein the term "and/or" includes any and all combinations of one or more of the associated listed items and may be abbreviated by "<confidence value="588">/".</confidence>
116
+ </p>
117
+ <p id="p-34" num="34">
118
+ <confidence value="5">[</confidence>
119
+ 0030] It will also be understood that, although the terms first, second, etc. </p>
120
+ <p id="p-35" num="35">may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element.</p>
121
+ <p id="p-36" num="36">
122
+ <confidence value="5">[</confidence>
123
+ 0031<confidence value="5">]</confidence>
124
+ The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises," "comprising,<confidence value="6">"</confidence>
125
+ <confidence value="6">"</confidence>
126
+ includes" and/or "including" when used herein, specify the presence of stated features, steps, operations, elements, and/or <boundary-data type="header">
127
+ <confidence value="8">5</confidence>
128
+ </boundary-data>
129
+ <page-break num="6"/>
130
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
131
+ components, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, and/or groups thereof. </p>
132
+ <p id="p-37" num="37">[0032<confidence value="5">]</confidence>
133
+ Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein. </p>
134
+ <p id="p-38" num="38">[0033<confidence value="4">]</confidence>
135
+ The present invention is described in part below with reference to block diagrams and flowcharts of methods, systems and computer program products according to embodiments of the invention. It will be understood that a block of the block diagrams or flowcharts, and combinations of blocks in the block diagrams or flowcharts, may be implemented at least in part by computer program instructions. </p>
136
+ <p id="p-39" num="39">These computer program instructions may be provided to one or more enterprise, application, personal, pervasive and/or embedded computer systems, such that the instructions, which execute via the computer system(s) create means, modules, devices or methods for implementing the functions/acts specified in the block diagram block or blocks. Combinations of general purpose computer systems and/or special purpose hardware also may be used in other embodiments.</p>
137
+ <p id="p-40" num="40">
138
+ <confidence value="5">[</confidence>
139
+ 0034<confidence value="5">]</confidence>
140
+ These computer program instructions may also be stored in memory of the computer system(s) that can direct the computer system(s) to function in a particular manner, such that the instructions stored in the memory produce an article of manufacture including computer-readable program code which implements the functions/acts specified in block or blocks. The computer program instructions may also be loaded into the computer system(s) to cause a series of operational steps to be performed by the computer system(s) to produce a computer implemented process such that the instructions which execute on the processor provide steps for implementing the functions/acts specified in the block or blocks. Accordingly, a given block or blocks of the block diagrams and/or flowcharts provides support for methods, computer program products and/or systems (structural and/or means-plus- function). </p>
141
+ <p id="p-41" num="41">[0035] It should also be noted that in some alternate implementations, the functions/acts noted in the flowcharts may occur out of the order noted in the <boundary-data type="header">
142
+ <confidence value="8">6</confidence>
143
+ </boundary-data>
144
+ <page-break num="7"/>
145
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
146
+ flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Finally, the functionality of one or more blocks may be separated and/or combined with that of other blocks. </p>
147
+ <p id="p-42" num="42">
148
+ <confidence value="5">[</confidence>
149
+ 0036<confidence value="5">]</confidence>
150
+ Figure 1 is a block diagram of analogy detection methods, systems and/or computer program products according to various embodiments of the present invention. As shown in Figure 1, these analogy detection methods, systems and/or computer program products include a processing system, method and/or computer program product <part-num-ref name="processing system, method and/or computer program product">110</part-num-ref>
151
+ that interacts with one or more associative memories <part-num-ref name="that interacts with one or more associative memories">120</part-num-ref>
152
+ to detect analogies among a plurality of entities that are included in source data <part-num-ref name="plurality of entities that are included in source data">130.</part-num-ref>
153
+ </p>
154
+ <p id="p-43" num="43">Processing block 110 may be controlled by a user through a user interface <part-num-ref name="user interface">140,</part-num-ref>
155
+ and the outputs of analogy detection may be displayed, for example, in graphical form, via the user interface <part-num-ref name="user interface">140.</part-num-ref>
156
+ </p>
157
+ <p id="p-44" num="44">
158
+ <confidence value="5">[</confidence>
159
+ 0037] It will be understood that the term "entity" includes a person, place or thing for which an analogy is to be detected and may also include other data terms and/or concepts, such as verbs. Moreover, the source data <part-num-ref name="source data">130</part-num-ref>
160
+ can include source documents, database records or other data sources that are well known to those having skill in the art. Finally, the associative memories <part-num-ref name="associative memories">120</part-num-ref>
161
+ may be embodied using an associative memory network of U.S. Patent 6,581,049 to coinventor Aparicio, IV et al., entitled "A<confidence value="88686">rtifi</confidence>
162
+ cial Neurons Including Power Series of Weights and Counts That Represent Prior and Next Associations ", and assigned to the assignee of the present invention, the disclosure of which is hereby incorporated herein by reference in its entirety as if set forth fully herein. These associative memory networks may scale linearly or almost linearly and thereby allow large networks of associative memories to be provided. However, in other embodiments of the present invention, other associative memory architectures may be used. </p>
163
+ <p id="p-45" num="45">
164
+ <confidence value="5">[</confidence>
165
+ 0038<confidence value="5">]</confidence>
166
+ It will also be understood that the blocks of Figure 1 may be embodied as one or more enterprise, application, personal, pervasive and/or embedded computer systems and/or special purpose hardware that may be connected by a wired and/or wireless network. The blocks of Figure 1 may also include one or more general purpose data processors that execute one or more stored programs, one or more special purpose processors and/or special purpose hardware. For ease of nomenclature, a given system, method and/or computer program product that is illustrated in the drawings may also be referred to herein as a "block". Moreover, the <boundary-data type="header">
167
+ <confidence value="8">7</confidence>
168
+ </boundary-data>
169
+ <page-break num="8"/>
170
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
171
+ associative memories <part-num-ref name="associative memories">120</part-num-ref>
172
+ may be stored in one or more general purpose memory devices <confidence value="222222">and/or</confidence>
173
+ special purpose associative memory devices. These memory devices may represent an overall hierarchy of memory devices containing software <confidence value="222222">and/or</confidence>
174
+ data used to implement the associative memories <part-num-ref name="associative memories">120.</part-num-ref>
175
+ The memory devices can include, but are not limited to, the following types of devices: cache, ROM, PROM, EPROM, <confidence value="5">E</confidence>
176
+ EPROM, flash memory, SRAM <confidence value="222222">and/or</confidence>
177
+ DRAM. </p>
178
+ <p id="p-46" num="46">
179
+ <confidence value="5">[</confidence>
180
+ 0039<confidence value="5">]</confidence>
181
+ Figure 2 is a flowchart of operations that may be performed to detect analogies among a plurality of entities according to various embodiments of the present invention. Operations of Figure 2 may be performed, for example, by the processing block <part-num-ref name="processing block">110</part-num-ref>
182
+ of Figure 1 in conjunction with the associative memories <part-num-ref name="associative memories">120,</part-num-ref>
183
+ using the source data <part-num-ref name="source data">130</part-num-ref>
184
+ and the user interface <part-num-ref name="user interface">140.</part-num-ref>
185
+ </p>
186
+ <p id="p-47" num="47">[0040] Referring to Figure 2, associative counts are obtained among the plurality of entities based on the source data <part-num-ref name="source data">130</part-num-ref>
187
+ (Block 210). The obtaining of associative counts among entities from source data is well known to those having skill in the art and need not be described further herein. </p>
188
+ <p id="p-48" num="48">
189
+ <confidence value="5">[</confidence>
190
+ 0041<confidence value="5">]</confidence>
191
+ Then, at Block 220, operations are performed to compute respective similarity measures among respective given entities and other entities among the plurality of entities using the associative counts. Many techniques may be used to compute the similarity measures. Some techniques that may be used according to embodiments of the present invention will be described in detail below. At Block <part-num-ref name="present invention will be described in detail below. At Block">230,</part-num-ref>
192
+ operations are performed to identify first and second entities from the plurality of entities as being analogies if the first entity has a strongest similarity measure with respect to the second entity and the second entity also has a strongest similarity measure with respect to the first entity. This technique for identifying analogies among entities may be referred to herein as "reciprocal similarity" or "reciprocal coherence". Details will be provided below. Finally, at Block <part-num-ref name="first entity. This technique for identifying analogies among entities may be referred to herein as &quot;reciprocal similarity&quot; or &quot;reciprocal coherence&quot;. Details will be provided below. Finally, at Block">240,</part-num-ref>
193
+ having identified the first and second entities as analogies, other entities may be identified as being analogies of the first and second entities using techniques that will be described in detail below. </p>
194
+ <p id="p-49" num="49">[0042] Figure 3 is a flowchart of operations that may be performed to compute respective similarity measures among respective given entities and other entities among the plurality of entities according to various embodiments of the present invention. These operations may correspond to Block <part-num-ref name="present invention. These operations may correspond to Block">220</part-num-ref>
195
+ of Figure 2. In general, in some embodiments of the invention, similarity measures may be computed by <boundary-data type="header">
196
+ <confidence value="8">8</confidence>
197
+ </boundary-data>
198
+ <page-break num="9"/>
199
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
200
+ computing a respective normalized entropy inverted among a respective given entity and other entities among the plurality of entities, using the associative counts. In other embodiments, similarity measures may be computed by determining a similarity of the given entity to another entity from a perspective of a third entity, relative to an overall similarity of entities to one another from the perspective of the third entity. </p>
201
+ <p id="p-50" num="50">[0043] More specifically, referring to Figure 3, at Block 310, operations are performed to compute a "pair entropy" of the given entity and the other entity from <confidence value="1">-</confidence>
202
+ the perspective of the third entity. Operations are performed at Block <part-num-ref name="third entity. Operations are performed at Block">320</part-num-ref>
203
+ to compute an <confidence value="5">"</confidence>
204
+ overall entropy<confidence value="5">"</confidence>
205
+ of entities to one another from the perspective of the third entity. </p>
206
+ <p id="p-51" num="51">Operations are performed at Block 330 to compute a "maximum overall entropy" of entities to one another from the perspective of the third entity. Finally, at Block <part-num-ref name="third entity. Finally, at Block">340,</part-num-ref>
207
+ the pair entropy, the overall entropy and the maximum overall entropy are combined, to produce a measure of similarity. It will be understood by those having skill in the art that the operations of Blocks <part-num-ref name="operations of Blocks">310,</part-num-ref>
208
+ <part-num-ref name="operations of Blocks 310,">320</part-num-ref>
209
+ and <part-num-ref name="and">330</part-num-ref>
210
+ may be performed out of the order shown in Figure 3, and may be performed at least partially simultaneously, as will be described in detail below. </p>
211
+ <p id="p-52" num="52">[0044] As was described above, at Block 340, the pair entropy, overall entropy and maximum overall entropy may be combined. In some embodiments, the overall entropy minus the pair entropy are divided by a log of the maximum overall entropy to obtain a result. The result may then be subtracted from one to obtain a normalized entropy inverted. Additional details will,be provided below.</p>
212
+ <p id="p-53" num="53">
213
+ <confidence value="5">[</confidence>
214
+ 0045<confidence value="5">]</confidence>
215
+ Figure 4 illustrates an architecture of memories, such as associative memories <part-num-ref name="architecture of memories, such as associative memories">120</part-num-ref>
216
+ of Figure 1, according to various embodiments of the present invention. As shown in Figure 4, an int<confidence value="8">e</confidence>
217
+ grator <part-num-ref name="integrator">410,</part-num-ref>
218
+ a reciprocal filter <part-num-ref name="reciprocal filter">420</part-num-ref>
219
+ and a cognitive map <part-num-ref name="cognitive map">430</part-num-ref>
220
+ may be included. </p>
221
+ <p id="p-54" num="54">[0046] The integrator <part-num-ref name="integrator">410</part-num-ref>
222
+ may be a conventional associative matrix that totals (integrates) associations among various entities as source data <part-num-ref name="conventional associative matrix that totals (integrates) associations among various entities as source data">130</part-num-ref>
223
+ is provided. Thus, in some embodiments, the integrator <part-num-ref name="integrator">410</part-num-ref>
224
+ can be the primary associative matrix, which observes incoming entities and their associations to each other. The integrator <part-num-ref name="integrator">410,</part-num-ref>
225
+ by seeing the incoming entities, can compute the entropies of every value as a measure of information. It can also provide a global lookup function. Thus, given any set of inputs, it can determine the other inputs associated with them. </p>
226
+ <p id="p-55" num="55">[0047] Cognitive map 430, also referred to as a "distance map" or simply as a "map", may be used to store similarity measures among a given entity and other <boundary-data type="header">
227
+ <confidence value="8">9</confidence>
228
+ </boundary-data>
229
+ <page-break num="10"/>
230
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
231
+ entities among the plurality of entities. Unlike the integrator memory <part-num-ref name="integrator memory">410</part-num-ref>
232
+ that contains associative counts in its matrix, the cognitive map contains measures of similarity, according to some embodiments of the invention. These measures of similarity may be computed from the integrator memory <part-num-ref name="integrator memory">410,</part-num-ref>
233
+ as will be described below. Since this computation may be computationally expensive, the cognitive map <part-num-ref name="cognitive map">430</part-num-ref>
234
+ may be embodied as a persistent memory cache of this information. </p>
235
+ <p id="p-56" num="56">[0048] The reciprocal filter <part-num-ref name="reciprocal filter">420,</part-num-ref>
236
+ also simply referred to as a "filter", can include transient computations that may be performed to represent those entities that are reciprocally coherent. Coherence filtering can be performed rapidly, so that persistent caching may not be needed. This transience can allow for context dependency, so that the cognitive map <part-num-ref name="cognitive map">430</part-num-ref>
237
+ can represent the similarities as defined by the data, while the reciprocal filter <part-num-ref name="reciprocal filter">420</part-num-ref>
238
+ allows for real time biasing of a relevant sub- map according to some embodiments of the invention. </p>
239
+ <p id="p-57" num="57">
240
+ <confidence value="5">[</confidence>
241
+ 0049<confidence value="5">]</confidence>
242
+ Figure 5 is a block diagram of memories, such as associative memories <part-num-ref name="block diagram of memories, such as associative memories">120</part-num-ref>
243
+ of Figure 1, according to other embodiments of the present invention. These embodiments add a network <part-num-ref name="network">512</part-num-ref>
244
+ of entity associative memory networks <part-num-ref name="of entity associative memory networks">510.</part-num-ref>
245
+ A respective entity associative memory network <part-num-ref name="respective entity associative memory network">510</part-num-ref>
246
+ includes therein associations among a respective observer entity and a plurality of observed entities that are observed by the respective observer entity, based upon the source data. Stated differently, a respective entity associative memory network <part-num-ref name="respective entity associative memory network">510</part-num-ref>
247
+ includes associations between pairs of entities from a perspective of a third entity, wherein the pairs of entities may be referred to as observed entities, and the third entity may be referred to as an observer entity. </p>
248
+ <p id="p-58" num="58">
249
+ <confidence value="5">[</confidence>
250
+ 0050] Thus, for example, when source data 130 is observed into the associative memories <part-num-ref name="associative memories">120,</part-num-ref>
251
+ a separate entity associative memory network <part-num-ref name="separate entity associative memory network">510</part-num-ref>
252
+ may be created and populated by associations among a given observer entity and a plurality of observed entities that are observed by the observer entity. An observer denotes an entity from whose perspective observed entities are stored in a respective associative memory network <part-num-ref name="respective associative memory network">510.</part-num-ref>
253
+ By providing a network <part-num-ref name="network">512</part-num-ref>
254
+ of entity associative memory networks <part-num-ref name="of entity associative memory networks">510,</part-num-ref>
255
+ a respective one of which is arranged from the perspective of a respective observer entity, contextual associations may be provided among observer entities and observed entities. This contextual context can allow more efficient computation of candidate entities for analogy detection, as will be described in detail below. Moreover, the network <part-num-ref name="network">512</part-num-ref>
256
+ of entity associative memory networks <part-num-ref name="of entity associative memory networks">510</part-num-ref>
257
+ also <boundary-data type="header">
258
+ <confidence value="88">10</confidence>
259
+ </boundary-data>
260
+ <page-break num="11"/>
261
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
262
+ may be used for other knowledge management purposes, as described, for example, in Application Serial No. 10/980,520, filed November <part-num-ref name="also may be used for other knowledge management purposes, as described, for example, in Application Serial No. 10/980,520, filed November">3,</part-num-ref>
263
+ <part-num-ref name="also may be used for other knowledge management purposes, as described, for example, in Application Serial No. 10/980,520, filed November 3,">2004,</part-num-ref>
264
+ entitled Network of Networks of Associative Memory Networks for Knowledge Management, to Fleming et al., assigned to the assignee of the present invention, the disclosure of which is hereby incorporated herein by reference in its entirety as if set forth fully herein. For the sake of brevity, an entity associative memory network <part-num-ref name="entity associative memory network">510</part-num-ref>
265
+ may also be referred to herein as an "entity memory" <part-num-ref name="&quot;entity memory&quot;">510.</part-num-ref>
266
+ </p>
267
+ <p id="p-59" num="59">
268
+ <confidence value="5">[</confidence>
269
+ 0051] Thus, while the integrator memory <part-num-ref name="integrator memory">410</part-num-ref>
270
+ stores associations at large, each entity can have its own specialized memory <part-num-ref name="stores associations at large, each entity can have its own specialized memory">510</part-num-ref>
271
+ in embodiments of Figure 5. In these specialized memories <part-num-ref name="in embodiments of Figure 5. In these specialized memories">510,</part-num-ref>
272
+ the original data can be conditioned to each entity, storing the associations around each of its mentions in the data. This can provide a nonlinear model that is able to represent triples. For example, given Person:A, Person:D is associated with Person:Y. The general scope of the integrator <part-num-ref name="integrator">410</part-num-ref>
273
+ may not provide such triple associative information. As will be described in detail below, the specialization provided by the entity memories <part-num-ref name="entity memories">510</part-num-ref>
274
+ can provide a nonlinear signature of each entity in order to measure the nonlinear-similarity between two entity signatures. Thus, for example, many persons may have traveled to many cities, but the entity memory <part-num-ref name="entity memory">510</part-num-ref>
275
+ can specifically remember who traveled to where and with whom, which is a deeper basis for similarity. On the other hand, the entity memories <part-num-ref name="entity memories">510</part-num-ref>
276
+ may not be able to compute the entropy of each entity and association at large, which can remain the responsibility of the integrator <part-num-ref name="integrator">410.</part-num-ref>
277
+ The integrator <part-num-ref name="integrator">410</part-num-ref>
278
+ can also provide general associative lookup functions about which entities are connected to which others. Thus, both coarse-grained and fine-grained memories may be used. </p>
279
+ <p id="p-60" num="60">
280
+ <confidence value="5">[</confidence>
281
+ 0052<confidence value="5">]</confidence>
282
+ Figure 6 is a block diagram of an example of associative memories <part-num-ref name="example of associative memories">120</part-num-ref>
283
+ of Figure 5 that can be used for analogy detection among entities A, B, C, D, W, X, Y and Z. This simplified example of eight entities may be used for illustrative purposes, and will be used consistently as an example throughout the following description. It will be understood, however, that methods, systems and computer program products according to embodiments of the present invention will generally be used to detect analogies among much larger numbers of entities, on the order of thousands, hundreds of thousands, millions or more. Moreover, for the purposes of the example, it will be assumed that entities A, B, C and D are members of a first entity class, such as Persons, and entities W, X, Y and Z are members of a second entity class, such as <boundary-data type="header">
284
+ <confidence value="88">11</confidence>
285
+ </boundary-data>
286
+ <page-break num="12"/>
287
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
288
+ Places. However, in other embodiments, a single class or more than two classes may be provided. </p>
289
+ <p id="p-61" num="61">
290
+ <confidence value="5">[</confidence>
291
+ 0053<confidence value="5">]</confidence>
292
+ As shown in Figure 6, four entity memories 510a-510d are provided, a respective one of which includes associative counts among observed entities in the context of an observer entity A, B, C or D, respectively. A cognitive map <part-num-ref name="cognitive map">430,</part-num-ref>
293
+ a reciprocal filter <part-num-ref name="reciprocal filter">420</part-num-ref>
294
+ and an integrator <part-num-ref name="integrator">410</part-num-ref>
295
+ also are provided. An entropy cache <part-num-ref name="entropy cache">612</part-num-ref>
296
+ also may be provided to store and update the variables T and S, so as to reduce or avoid the need to recompute overall entropy, as will be described in more detail below. The entropy cache <part-num-ref name="entropy cache">612</part-num-ref>
297
+ may be part of the integrator <part-num-ref name="integrator">410</part-num-ref>
298
+ or separate therefrom. </p>
299
+ <p id="p-62" num="62">
300
+ <confidence value="5">[</confidence>
301
+ 0054<confidence value="5">]</confidence>
302
+ Figure 7 is a flowchart of operations that may be performed to compute similarity measures among a given entity and other entities according to various embodiments of the present invention, which may correspond to Block <part-num-ref name="present invention, which may correspond to Block">220</part-num-ref>
303
+ of Figure 2. More specifically, prior to performing the operations of Figure 7, the source data <part-num-ref name="source data">130</part-num-ref>
304
+ is read and the integrator <part-num-ref name="integrator">410</part-num-ref>
305
+ and entity memories <part-num-ref name="and entity memories">510</part-num-ref>
306
+ are populated. In particular, the integrator <part-num-ref name="integrator">410</part-num-ref>
307
+ learns the associative count for all entities to all other entities across all data records. The entity memories <part-num-ref name="entity memories">510</part-num-ref>
308
+ learn the coincidences of all other entities for a given entity that is mentioned in the data records. </p>
309
+ <p id="p-63" num="63">
310
+ <confidence value="5">[</confidence>
311
+ 0055<confidence value="5">]</confidence>
312
+ Referring now to Figure 7, the entity set is obtained at Block <part-num-ref name="entity set is obtained at Block">710.</part-num-ref>
313
+ </p>
314
+ <p id="p-64" num="64">Then, for each entity at Block 720, the relevant entity memory <part-num-ref name="relevant entity memory">510</part-num-ref>
315
+ is obtained at Block <part-num-ref name="is obtained at Block">730</part-num-ref>
316
+ and an associative signature is generated at Block <part-num-ref name="associative signature is generated at Block">740.</part-num-ref>
317
+ Computation of an associative signature will be described in detail below. In general, however, using a respective entity memory <part-num-ref name="respective entity memory">510</part-num-ref>
318
+ as the most specific, nonlinear source of information, the entity memory <part-num-ref name="entity memory">510</part-num-ref>
319
+ provides a signature that can provide the most informative subset of entities that can be used to describe a given entity. Using these associative signatures, the integrator memory <part-num-ref name="integrator memory">410</part-num-ref>
320
+ is used, at Block <part-num-ref name="is used, at Block">750,</part-num-ref>
321
+ to identify nearest neighbor candidates at Block <part-num-ref name="is used, at Block 750, to identify nearest neighbor candidates at Block">760.</part-num-ref>
322
+ Thus, using the integrator memory <part-num-ref name="integrator memory">410,</part-num-ref>
323
+ the signature of each entity is used as a set of keys for associative lookup of other entities that also have the same observed entities. This can provide a first pass determination of potential analogies, before looking into the detailed pairwise information. </p>
324
+ <p id="p-65" num="65">Therefore, Block 760 may not produce the final answer, but only an initial set of potentially analogous entities that are called "candidates".</p>
325
+ <p id="p-66" num="66">
326
+ <confidence value="5">[</confidence>
327
+ 0056] Continuing with the description of Figure 7, at Block <part-num-ref name="description of Figure 7, at Block">770,</part-num-ref>
328
+ for each candidate, analog information is computed at Block <part-num-ref name="description of Figure 7, at Block 770, for each candidate, analog information is computed at Block">780.</part-num-ref>
329
+ The analog information may <boundary-data type="header">
330
+ <confidence value="88">12</confidence>
331
+ </boundary-data>
332
+ <page-break num="13"/>
333
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
334
+ be accumulated to provide a similarity measure among a given entity and other entities, as will be described in detail below. In some embodiments, the analog information or similarity measure is based on normalized entropy inverted, which can be computed as was already described in connection with Figure 3. Thus, a nonlinear comparison of information, including a measure of differential information, is used to measure similarity between each entity and each candidate in some embodiments. </p>
335
+ <p id="p-67" num="67">These similarity measures are stored in the cognitive map <part-num-ref name="cognitive map">430</part-num-ref>
336
+ at Block <part-num-ref name="at Block">790.</part-num-ref>
337
+ </p>
338
+ <p id="p-68" num="68">
339
+ <confidence value="5">[</confidence>
340
+ 0057<confidence value="5">1</confidence>
341
+ Figure 8 is a flowchart of operations that may be performed to obtain an associative signature, which may correspond to Block <part-num-ref name="associative signature, which may correspond to Block">740</part-num-ref>
342
+ of Figure 7. At Block <part-num-ref name="of Figure 7. At Block">810,</part-num-ref>
343
+ observed entities that are listed in the entity memory <part-num-ref name="entity memory">510</part-num-ref>
344
+ that was obtained at Block <part-num-ref name="that was obtained at Block">730</part-num-ref>
345
+ are obtained. Since each entity memory <part-num-ref name="are obtained. Since each entity memory">510</part-num-ref>
346
+ lists only those observed entities to which it is associated, the list of such observed entities can become the primary basis for characterizing the observer entity. In some embodiments, all observed entities are obtained at Block <part-num-ref name="observer entity. In some embodiments, all observed entities are obtained at Block">810.</part-num-ref>
347
+ However, in other embodiments, metrics such as frequency or entropy may be used to obtain a set of "best" observed entities. </p>
348
+ <p id="p-69" num="69">Then, at Block 820, for each observed entity, associated observed entities are obtained at Block 830. More specifically, for each observed entity known to an observer entity, the entity memory <part-num-ref name="entity memory">510</part-num-ref>
349
+ can also report the strongest associations of other observed entities. While not an exhaustive representation of the complete entity memory <part-num-ref name="complete entity memory">510,</part-num-ref>
350
+ the list of best observed entities and its best associations can provide a distinct nonlinear description of the observer entity as a function of its surrounding coincidences. A list of entities and associations is merged into a single structure called the "associative signature" at Block <part-num-ref name="&quot;associative signature&quot; at Block">840.</part-num-ref>
351
+ </p>
352
+ <p id="p-70" num="70">[0058<confidence value="5">1</confidence>
353
+ Figure 9 demonstrates the construction of an associative signature where the entity memory <confidence value="666">510</confidence>
354
+ b for entity B is used. Thus, in entity memory <confidence value="66688">510b,</confidence>
355
+ observed entities are correlated with each other conditional on observer entity Person:B. While the integrator memory <part-num-ref name="integrator memory">410</part-num-ref>
356
+ would describe Person:B as strongly associated with City:W, it can also be seen that City:W is coincident with Person:A. </p>
357
+ <p id="p-71" num="71">In other words, the City:W AND Person:A association is a deeper, nonlinear description of Person:B. Not only does Person:B visit City:W, he did so with Person:A, at least once in this simple example.</p>
358
+ <p id="p-72" num="72">
359
+ <confidence value="5">[</confidence>
360
+ 0059<confidence value="5">]</confidence>
361
+ Depending on the application, such nonlinear predictive strength may or may not be used. For simple data cleansing in which there are highly informative entities and only a few are altered, such as by data error or as natural variants, the <boundary-data type="header">
362
+ <confidence value="88">13</confidence>
363
+ </boundary-data>
364
+ <page-break num="14"/>
365
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
366
+ power of linear signatures when combined with similarity measures described below might suffice. However, consider difficult cases in which the entity space is "saturated". For example, suppose in the extreme that everybody has traveled to City:W and that everybody has traveled with Person:A. From a linear perspective, City:W and Person:A are independently saturated and are totally uninformative. In this case, similarities and distinctions may only be made by referring to the interactions of entities. Everybody might have visited City:W and traveled with Person:A, but fewer should have visited City:W with Person:A. When analogies are hidden by such linear saturation or other forms of population "noise", then nonlinear signatures may be used for better detection. This is also true when the data is very sparse; given a greater absence of linear information, the extraction of the nonlinear information can help compensate. </p>
367
+ <p id="p-73" num="73">[0060<confidence value="5">1</confidence>
368
+ It will be understood by one skilled in the art that performance variations can be provided in generating a nonlinear signature, according to some embodiments of the invention. For instance, as will be described below, the integrator memory <part-num-ref name="integrator memory">410</part-num-ref>
369
+ contains information about each and every entity. Such information can be used to select those entities of the signature that will have the most information in subsequent process while ignoring those with little if any effect. Rather than describing each entity by its complete set of observed entities (and associated observed entities), such modifications can describe each entity as a signature of only the most informative observed entities, which can enhance or optimize subsequent processing. </p>
370
+ <p id="p-74" num="74">[0061<confidence value="5">]</confidence>
371
+ Although more complex models may generally represent the signature as a subset of the associations, Figure 9 shows how, in this simple example, <confidence value="5">{</confidence>
372
+ Ay, Aw<confidence value="5">}</confidence>
373
+ (indicating primary observed entities with secondary associations) describe what is known about Entity B. Figure 9 also shows how these signature attributes map back to the integrator memory <part-num-ref name="integrator memory">410</part-num-ref>
374
+ for subsequent activation and processing. </p>
375
+ <p id="p-75" num="75">
376
+ <confidence value="5">[</confidence>
377
+ 0062<confidence value="5">1</confidence>
378
+ Figure 10 is a flowchart of operations that can be used to obtain nearest neighbor candidates, which may correspond to Block <part-num-ref name="flowchart of operations that can be used to obtain nearest neighbor candidates, which may correspond to Block">760</part-num-ref>
379
+ of Figure 7. Operations begin with a given associative signature (Block <part-num-ref name="given associative signature (Block">850</part-num-ref>
380
+ of Figure 8). The operations recall other entities from the integrator memory <part-num-ref name="integrator memory">410</part-num-ref>
381
+ given the original entity's associative signature. Operations loop through the signature, pair by pair, activating both entities of the pair, and recalling and scoring other entities associated with the pair. Thus, for each entity pair at Block <part-num-ref name="pair. Thus, for each entity pair at Block">1020,</part-num-ref>
382
+ the associated entities are recalled at <boundary-data type="header">
383
+ <confidence value="88">14</confidence>
384
+ </boundary-data>
385
+ <page-break num="15"/>
386
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
387
+ Block <part-num-ref name="associated entities are recalled at Block">1030.</part-num-ref>
388
+ The exact technique for recall may be dependent upon the associative memory implementation. However, it is generally known how to "imagine" unknown entities given the conditions of other entities. Mathematically, given the entities in the pair, the memory can be set to imagine the most likely associated entities, excluding the original observer entity. The likelihood for each candidate for each pair can be accumulated for the candidate. For instance, if a candidate is highly likely given one pair, then this high score is added to the accumulation of prior scores for other entity pairs. A list of all likely candidates, given all pairs, is merged at Block <part-num-ref name="list of all likely candidates, given all pairs, is merged at Block">1040,</part-num-ref>
389
+ and sorted by the accumulated score. These likely entities are called "candidates", because further analysis of their similarity may still be performed below. </p>
390
+ <p id="p-76" num="76">
391
+ <confidence value="5">[</confidence>
392
+ 0063<confidence value="5">]</confidence>
393
+ Note that, in some embodiments, there is no penalty for a candidate that is missing a pair of attributes. The accumulation of likelihood scores is additive when a likelihood exists, but no assumption need be made about the absence of evidence. Unlike other techniques, there may be no penalty, because a penalty may incorrectly assume that absence of evidence is evidence of absence. </p>
394
+ <p id="p-77" num="77">
395
+ <confidence value="5">[</confidence>
396
+ 0064<confidence value="5">]</confidence>
397
+ Figure 11 demonstrates an example of one observed entity pair A<confidence value="5">Y</confidence>
398
+ from Entity B. Although it is possible to ask all the other entity memories <part-num-ref name="other entity memories">510</part-num-ref>
399
+ about Ay, this exhaustive search may be impractical. The integrator memory <part-num-ref name="integrator memory">410</part-num-ref>
400
+ provides a more efficient associative lookup, even if not as nonlinear and specific as each entity memory <part-num-ref name="more efficient associative lookup, even if not as nonlinear and specific as each entity memory">510.</part-num-ref>
401
+ Again referring to the specific example of the associative memory, given Person:A and City:Y as observed entities, the integrator memory <part-num-ref name="integrator memory">410</part-num-ref>
402
+ can recall associated persons (aside from the original Person:B). In this example, Person:D is the strongest candidate with association to both Person:A and City:Y. Person:C is the next best candidate, only associated with City:Y. Note that Person:A is logically excluded from being a candidate, because if Person:A is a known associate to Person:B, he/she cannot also be an alias of Person:B. </p>
403
+ <p id="p-78" num="78">
404
+ <confidence value="5">[</confidence>
405
+ 0065] Figure 12 is a flowchart of operations that may be performed to compute analog information, which may correspond to Block <part-num-ref name="flowchart of operations that may be performed to compute analog information, which may correspond to Block">780</part-num-ref>
406
+ of Figure 7. The accumulated analog information can provide a similarity measure, as was described above. Thus, as used herein, a similarity measure is obtained by accumulating analog information. Moreover, analog information may be computed according to some embodiments of the present invention by computing a normalized entropy inverted. </p>
407
+ <p id="p-79" num="79">The normalized entropy inverted may be computed by determining a similarity of a <boundary-data type="header">
408
+ <confidence value="88">15</confidence>
409
+ </boundary-data>
410
+ <page-break num="16"/>
411
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
412
+ given entity to another entity from a perspective of a third entity, relative to an overall similarity of entities to one another from the perspective of the third entity. This normalized entropy inverted may be computed as shown in Figure 12. More particularly, for a given candidate at Block <part-num-ref name="given candidate at Block">1210,</part-num-ref>
413
+ the relevant integrator memory <part-num-ref name="relevant integrator memory">510</part-num-ref>
414
+ is obtained at Block <part-num-ref name="is obtained at Block">1220,</part-num-ref>
415
+ and for each attribute pair at Block <part-num-ref name="is obtained at Block 1220, and for each attribute pair at Block">1230,</part-num-ref>
416
+ if a candidate has a primary attribute at Block <part-num-ref name="primary attribute at Block">1240,</part-num-ref>
417
+ then pair entropy is computed at Block <part-num-ref name="primary attribute at Block 1240, then pair entropy is computed at Block">1250,</part-num-ref>
418
+ and overall entropies are computed at Block <part-num-ref name="primary attribute at Block 1240, then pair entropy is computed at Block 1250, and overall entropies are computed at Block">1260.</part-num-ref>
419
+ These entropies are then combined at Block <part-num-ref name="primary attribute at Block 1240, then pair entropy is computed at Block 1250, and overall entropies are computed at Block 1260. These entropies are then combined at Block">1290</part-num-ref>
420
+ and accumulated at Block <part-num-ref name="and accumulated at Block">1270,</part-num-ref>
421
+ and a measure of similarity is returned at Block <part-num-ref name="measure of similarity is returned at Block">1280.</part-num-ref>
422
+ </p>
423
+ <p id="p-80" num="80">
424
+ <confidence value="5">[</confidence>
425
+ 0066] More specifically, the similarity measure can be determined by accumulating analog information, where analog information is given by the formula: </p>
426
+ <p id="p-81" num="81">Analog information =1 <confidence value="6">-</confidence>
427
+ overall entropy - pair entropy log maximum overall entropy where "pair entropy" means the entropy of the given entity and the other entity in the pair from the perspective of the third entity, "overall entropy" means the overall entropy of entities to one another from the perspective of the third entity, and "maximum overall entropy" means the maximum possible entropy of the entities to one another from the perspective of the third entity. </p>
428
+ <p id="p-82" num="82">An example of calculating analog information according to some embodiments of the invention will now be illustrated. Suppose the counts, corresponding to a column of the integrator memory <part-num-ref name="integrator memory">410</part-num-ref>
429
+ with respect to a given entity are <part-num-ref name="given entity are">1,</part-num-ref>
430
+ <part-num-ref name="given entity are 1,">1,</part-num-ref>
431
+ <part-num-ref name="given entity are 1, 1,">1,</part-num-ref>
432
+ <part-num-ref name="given entity are 1, 1, 1,">150,</part-num-ref>
433
+ <part-num-ref name="given entity are 1, 1, 1, 150,">2000</part-num-ref>
434
+ and <part-num-ref name="and">2001,</part-num-ref>
435
+ and the pair being used to compute the analog information is the counts of <part-num-ref name="counts of">2000</part-num-ref>
436
+ and <part-num-ref name="and">2001.</part-num-ref>
437
+ Then, the pair entropy is the entropy between <part-num-ref name="entropy between">2000</part-num-ref>
438
+ and <part-num-ref name="and">2001,</part-num-ref>
439
+ the overall entropy is the overall entropy between the counts of <part-num-ref name="counts of">1,</part-num-ref>
440
+ <part-num-ref name="counts of 1,">1,</part-num-ref>
441
+ <part-num-ref name="counts of 1, 1,">1,</part-num-ref>
442
+ <part-num-ref name="counts of 1, 1, 1,">150,</part-num-ref>
443
+ <part-num-ref name="counts of 1, 1, 1, 150,">2000</part-num-ref>
444
+ and <part-num-ref name="and">2001,</part-num-ref>
445
+ and the maximum overall entropy is the maximum overall entropy that is attainable for the six counts. Table <part-num-ref name="six counts. Table">1</part-num-ref>
446
+ illustrates the results of computing analog information for various combinations of pairs for the counts of <part-num-ref name="counts of">1,</part-num-ref>
447
+ <part-num-ref name="counts of 1,">1,</part-num-ref>
448
+ <part-num-ref name="counts of 1, 1,">1,</part-num-ref>
449
+ <part-num-ref name="counts of 1, 1, 1,">150,</part-num-ref>
450
+ <part-num-ref name="counts of 1, 1, 1, 150,">2000</part-num-ref>
451
+ and <part-num-ref name="and">2001</part-num-ref>
452
+ using the above formula. </p>
453
+ <p id="p-83" num="83">Table 1 Count <part-num-ref name="Count">1</part-num-ref>
454
+ Count <part-num-ref name="Count">2</part-num-ref>
455
+ Analog Information <part-num-ref name="Analog Information">2001</part-num-ref>
456
+ <part-num-ref name="">1</part-num-ref>
457
+ 0.53933 <part-num-ref name="0.53933">2000</part-num-ref>
458
+ <part-num-ref name="">1</part-num-ref>
459
+ 0.53933<confidence value="8">1</confidence>
460
+ <part-num-ref name="0.539331">150</part-num-ref>
461
+ <part-num-ref name="">1</part-num-ref>
462
+ 0.55916 <part-num-ref name="0.55916">2001</part-num-ref>
463
+ <part-num-ref name="">150</part-num-ref>
464
+ 0.678107 <part-num-ref name="0.678107">2000</part-num-ref>
465
+ <part-num-ref name="">150</part-num-ref>
466
+ 0.678154 <boundary-data type="header">
467
+ <confidence value="88">16</confidence>
468
+ </boundary-data>
469
+ <page-break num="17"/>
470
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
471
+ <part-num-ref name="0.678154">2001</part-num-ref>
472
+ <part-num-ref name="">2000</part-num-ref>
473
+ 0.923784 <part-num-ref name="0.923784">1</part-num-ref>
474
+ <part-num-ref name="">1</part-num-ref>
475
+ 0.923784 The analog information is presented in Table <part-num-ref name="analog information is presented in Table">1</part-num-ref>
476
+ in rank order going down the columns of the table. </p>
477
+ <p id="p-84" num="84">
478
+ <confidence value="5">[</confidence>
479
+ 0067<confidence value="5">]</confidence>
480
+ Additional discussion of the computation of a similarity measure according to various embodiments of the present invention now will be provided. In particular, entropy is a measure of information bits, but its actual values generally are unbounded. Furthermore, entropy generally is specific to a given distribution and may be difficult to compare across different distributions and different entities. Therefore, instead of raw entropy, some embodiments of the invention use an information score which inverts and normalizes the entropy value itself. Some embodiments of the invention can also use caching, updating, and differencing, as will now be described. </p>
481
+ <p id="p-85" num="85">
482
+ <confidence value="5">[</confidence>
483
+ 0068] In particular, normalization may be accomplished by comparing entropy to a maximum overall entropy. The maximum overall entropy is defined as the largest possible entropy given the size of a set of numbers. Maximum overall entropy is usually based only on what is called the "support size", i.e., the total number of numbers including zeros. However, because embodiments of the invention may defer the assumption that a zero is really a zero (because absence of evidence may not be evidence of absence), the maximum overall entropy may be computed from the size of the set of non-zero numbers. Given the information that is known, maximum overall entropy defines the greatest degree of disorder (lack of information). Thus, overall entropy/maximum overall entropy defines the normalized degree of disorder, ranging from 0-1. </p>
484
+ <p id="p-86" num="86">[0069] Moreover, to compute how much weight to assign to each attribute, it may be desirable to know how much information, not disorder, it contains. This can be obtained by inversion, and to again keep the range of information score from 0-1, it can be defined as <part-num-ref name="range of information score from 0-1, it can be defined as">1</part-num-ref>
485
+ - (overall entropy/maximum overall entropy). Inverted, as a score of information, this can then be used as a measure of information-based similarity. If two entities share the same attribute, the maximum contribution to similarity should equal <part-num-ref name="maximum contribution to similarity should equal">1.</part-num-ref>
486
+ However, to the degree that the attribute counts are common and uninformative, the information score should drop and so should the degree of informative similarity. </p>
487
+ <boundary-data type="header">
488
+ <confidence value="88">17</confidence>
489
+ </boundary-data>
490
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
491
+ <p id="p-87" num="87">
492
+ <page-break num="18"/>
493
+ [0070] The computation of such entropy may be computationally expensive. </p>
494
+ <p id="p-88" num="88">As presented in the above formula, the formula is simple, but when given extremely large integrator memories <part-num-ref name="formula is simple, but when given extremely large integrator memories">410,</part-num-ref>
495
+ thousands and even millions of counts and their probabilities might need to be computed each time, because entropy may account for all non-zero values for any row or column. Instead, according to some embodiments of the invention, manipulation of the entropy formula can provide an incremental update. As presented in Figures <part-num-ref name="incremental update. As presented in Figures">6</part-num-ref>
496
+ and <part-num-ref name="and">13,</part-num-ref>
497
+ the integrator memory <part-num-ref name="integrator memory">410</part-num-ref>
498
+ also includes an entropy cache <part-num-ref name="entropy cache">612</part-num-ref>
499
+ associated therewith, which is dynamically updated as new associations enter the integrator memory itself. More specifically, the variables T and S that are stored in the entropy cache <part-num-ref name="entropy cache">612</part-num-ref>
500
+ may be computed as follows: </p>
501
+ <p id="p-89" num="89">
502
+ <confidence value="5">[</confidence>
503
+ 0071] Let C denote an array of non-negative integers, indexed from <part-num-ref name="array of non-negative integers, indexed from">1</part-num-ref>
504
+ to n, and let C[k] denote the k-th element of C. To avoid the trivial case, assume that some of the C[k] are strictly positive. C induces a probability function P, as follows: </p>
505
+ <p id="p-90" num="90">[0072] Let T = C[k]<confidence value="8">&gt;</confidence>
506
+ <confidence value="8">0</confidence>
507
+ , and let P[k] = C[k]<confidence value="58">IT</confidence>
508
+ . Then the elements <confidence value="882">k=1</confidence>
509
+ <confidence value="868">P[k</confidence>
510
+ ] are non-negative and sum to <part-num-ref name="elements k=1 P[k] are non-negative and sum to">1,</part-num-ref>
511
+ as required. The entropy of P, denoted H(P), is defined by - H(P) <confidence value="8">=</confidence>
512
+ <confidence value="28888888">EP[k]log</confidence>
513
+ P[k]. </p>
514
+ <p id="p-91" num="91">k=1 <confidence value="5">[</confidence>
515
+ 0073<confidence value="5">]</confidence>
516
+ Some of the P[k] may equal <part-num-ref name="P[k] may equal">0,</part-num-ref>
517
+ and the logarithm function is undefined at <part-num-ref name="logarithm function is undefined at">0,</part-num-ref>
518
+ so a convention may be used that x log x denotes <part-num-ref name="convention may be used that x log x denotes">0</part-num-ref>
519
+ whenever x = <part-num-ref name="whenever x =">0.</part-num-ref>
520
+ In order to express H in terms of C and T: </p>
521
+ <p id="p-92" num="92">-H(P)= <confidence value="2">E</confidence>
522
+ P[k]log P[k] <confidence value="5">=</confidence>
523
+ <confidence value="885">k=1</confidence>
524
+ <confidence value="2">I</confidence>
525
+ (C[k] <confidence value="4">I</confidence>
526
+ <confidence value="8">T</confidence>
527
+ )log(C[k] <confidence value="686">/T)</confidence>
528
+ <confidence value="5">=</confidence>
529
+ <confidence value="82">(l</confidence>
530
+ <confidence value="5881">/T)j</confidence>
531
+ <confidence value="85">C[</confidence>
532
+ k](logC[k] <confidence value="8">-</confidence>
533
+ log<confidence value="885">T)=</confidence>
534
+ <confidence value="722">k=1</confidence>
535
+ <confidence value="855884">(1/T)j</confidence>
536
+ C[k]logC[k]<confidence value="888788">-(1/T)</confidence>
537
+ C[k]log<confidence value="8">T</confidence>
538
+ <confidence value="5">=</confidence>
539
+ <confidence value="821882">(l/T)$</confidence>
540
+ C[k]logC[k]<confidence value="8">-</confidence>
541
+ log<confidence value="6">T</confidence>
542
+ <confidence value="88">(1</confidence>
543
+ <confidence value="5">/</confidence>
544
+ <confidence value="872">T)$</confidence>
545
+ C[k] <confidence value="6">=</confidence>
546
+ <confidence value="662">k=1</confidence>
547
+ <confidence value="66">k=</confidence>
548
+ <boundary-data type="header">
549
+ <confidence value="88">18</confidence>
550
+ </boundary-data>
551
+ <page-break num="19"/>
552
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
553
+ <confidence value="8558186">(lT)EC[</confidence>
554
+ k]logC<confidence value="5888">[k]-</confidence>
555
+ logT = <confidence value="882">k=1</confidence>
556
+ <confidence value="868">S/T</confidence>
557
+ <confidence value="66">-l</confidence>
558
+ ogT, where S<confidence value="8">=</confidence>
559
+ C[k]<confidence value="4">I</confidence>
560
+ ogC[k]. </p>
561
+ <p id="p-93" num="93">If the value of C[k] changes from <confidence value="5">a</confidence>
562
+ to <confidence value="4">P</confidence>
563
+ , H can therefore be recomputed using: </p>
564
+ <p id="p-94" num="94">
565
+ <confidence value="8218885">TAeT-a+</confidence>
566
+ <confidence value="22222">p;and</confidence>
567
+ <confidence value="8">S</confidence>
568
+ <confidence value="1">A</confidence>
569
+ S-aloga+<confidence value="21">p8</confidence>
570
+ log<confidence value="4">p</confidence>
571
+ [0074<confidence value="5">]</confidence>
572
+ Accordingly, the above calculations show that when an associative count is updated in the integrator <part-num-ref name="integrator">410,</part-num-ref>
573
+ as new source data is input, entropy can be recomputed by recomputing the variable T and recomputing the variable S according to the above formulas. These two variables T and S then may be stored in the entropy cache <part-num-ref name="entropy cache">612</part-num-ref>
574
+ and incremented without the need to recalculate entropy with each change in each count. </p>
575
+ <p id="p-95" num="95">[0075<confidence value="4">]</confidence>
576
+ A similarity score according to embodiments of the invention can measure and accumulate the information that separates a pair of signatures from all other signatures. The informative weight of an entity is given by its information score, but this weight considers the entity's information in general, across all entities. To be more precise, it is desired to know entity-by-entity how much the third entity is similar across the two entities in distinguishing them from all others. As such, the information content between only the two entities may count. If the pair-information is subtracted from the total information, the difference represents how much information separates these two entities from all other entities of the same class. </p>
577
+ <p id="p-96" num="96">Rather than more abstract and general weightings of similarity, the specific similarity of the associative counts allows a definition of similarity as the distinctiveness of such fine-grained statistics.</p>
578
+ <p id="p-97" num="97">
579
+ <confidence value="5">[</confidence>
580
+ 0076<confidence value="5">]</confidence>
581
+ Consider some of the extreme cases: If the target and candidate entities are the two and only two associative counts for the entire attribute, then the pair-entropy is the total entropy, and all the entity's information is useful to distinguish these two entities from each other. All of the entity's information is between them. At another extreme, if the entity has many associative counts with high entropy but the two counts for the target and candidate are the same, then all of the information separates them-together from all the other entities in the class. </p>
582
+ <boundary-data type="header">
583
+ <confidence value="88">19</confidence>
584
+ </boundary-data>
585
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
586
+ <p id="p-98" num="98">
587
+ <page-break num="20"/>
588
+ <confidence value="5">[</confidence>
589
+ 0077<confidence value="5">]</confidence>
590
+ Thus, Figure 12 describes the overall flow for computing differential information as a measure of similarity. Given an entity and a candidate, and for each mutual attribute in the entity's signature and candidate's signature, the overall entropy is fetched from the entropy cache <part-num-ref name="entropy cache">612</part-num-ref>
591
+ and the pair entropy is computed from the specific pair of counts. Pair entropy is subtracted from the entity's total entropy, which is then normalized and inverted as a measure the distinctive information score. </p>
592
+ <p id="p-99" num="99">These information scores are accumulated across all mutual entities as a total measure of similarity.</p>
593
+ <p id="p-100" num="100">
594
+ <confidence value="5">[</confidence>
595
+ 0078] Figure 13 demonstrates the storage of the similarity metric within the cognitive map <part-num-ref name="cognitive map">430.</part-num-ref>
596
+ Given Person:B as the target (third) entity, the similarity scores to Person:D and Person:C are recorded. This map <part-num-ref name="similarity scores to Person:D and Person:C are recorded. This map">430</part-num-ref>
597
+ is not necessarily symmetric, because the similarity score of Person:C back to Person:A cannot be assumed to be the same. Beginning with the signature of Person:C, the recall of his/her nearest neighbors, and the existence of entity pairs generally produces a different set of analogies to Person:C. Generally speaking, it cannot be assumed that the reciprocal score will be the same value or that the reciprocal entity will even be included as a candidate. </p>
598
+ <p id="p-101" num="101">[0079] Fundamentally for some applications, the messiness of naturally distributed data does not guarantee that all entities even will see all the data. The very counts between one person and another might be inconsistent. However, such inconsistencies and differences in entity perspectives adds even less probability that two entities will agree in counts, analog similarity scores, and rank order of the candidates. This rarity may then be capitalized, according to some embodiments of the invention, by the filtering of reciprocal coherence - when the entities agree, as will now be described. It will also be understood that filtering by reciprocal coherence may be used, in other embodiments of the invention, where bidirectional counts are provided between entities.</p>
599
+ <p id="p-102" num="102">[0080] Identification of first and second entities as being analogies if the first entity has the strongest similarity measure with respect to the second entity and the second entity has the strongest similarity measure with respect to the first entity, according to embodiments of the invention, which may correspond to Block <part-num-ref name="invention, which may correspond to Block">230</part-num-ref>
600
+ of Figure 2, now will be described. In particular, the calculating of a similarity score and the rank ordering based on similarity, as was described above, can be rich and effective, but may only be a method of scoring and ranking. Beyond this, it may be <boundary-data type="header">
601
+ <confidence value="88">20</confidence>
602
+ </boundary-data>
603
+ <page-break num="21"/>
604
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
605
+ desirable to further refine or hone the candidate rankings to find the best similarities. </p>
606
+ <p id="p-103" num="103">As a signal detection task, analogy detection based only on similarity may still be subject to many false alarms when faced with high population noise. In the case of alias detection, for example, many people may be highly similar to each other, but not be aliases. More strongly stated, everybody is most similar to one other person, even if they are dissimilar. In other words, the analogy process will return scores and rank orders for each and every target, but this is not to say that all this information represents the best information.</p>
607
+ <p id="p-104" num="104">
608
+ <confidence value="5">[</confidence>
609
+ 0081<confidence value="5">]</confidence>
610
+ Rather than add the arbitrariness of some threshold value as is conventional, some embodiments of the present invention can provide more natural thresholds. In particular, rather than cut the analogy lists at one or another similarity score, some embodiments of the invention use the property of reciprocity to define a natural filter of these scores. Figure 14 continues with the example from Figure 13. </p>
611
+ <p id="p-105" num="105">Given the similarity measures of the map <part-num-ref name="map">430,</part-num-ref>
612
+ the rank order of similarities for each entity, from its perspective, can also be computed in the filter <part-num-ref name="filter">420.</part-num-ref>
613
+ In fact, rather than similarity, per se, the only measure that needs to be stored in the cognitive map can be the rank orderings. In general, two entities have a rank order of other entities that are similar to each of them. Whenever the first entity in one list agrees back as also first in its list, the first place ranking is reciprocal. In this case, as shown in Figure 14, Person:A thinks that Person:D is closest, and Person:D thinks Person:A is closest. </p>
614
+ <p id="p-106" num="106">They are reciprocal to this rank order of 1. This is also shown schematically in the entity diagram <part-num-ref name="entity diagram">1410</part-num-ref>
615
+ of Figure 14. </p>
616
+ <p id="p-107" num="107">
617
+ <confidence value="5">[</confidence>
618
+ 0082<confidence value="4">]</confidence>
619
+ Considering Figure 14 in terms of a graph, order <part-num-ref name="graph, order">1</part-num-ref>
620
+ reciprocity defines those places in a weighted graph where two nodes are closer to each other than to any other nodes. There is always at least one such pair in any graph, and never more than N/2 such pairs, where N is the number entities. While there are on the order of N2 number of analogy similarities possible in the cognitive map <part-num-ref name="cognitive map">430,</part-num-ref>
621
+ there are only on the order of <confidence value="66">1/</confidence>
622
+ N2 likely points of first order reciprocity. Thus, the analogy process can provide one level of filtering as a matter of analogy detection, while reciprocal coherence can add yet another level of filtering. </p>
623
+ <p id="p-108" num="108">[0083<confidence value="5">]</confidence>
624
+ Figure 15 is a flowchart of operations that may be used to determine reciprocal coherence, which may correspond to Block <part-num-ref name="flowchart of operations that may be used to determine reciprocal coherence, which may correspond to Block">230</part-num-ref>
625
+ of Figure 2. Given the similarity map (Block <part-num-ref name="similarity map (Block">1505)</part-num-ref>
626
+ and their rank order for each target entity (Block 1510), call each candidate a true analog, once the distinctive information is included in the <boundary-data type="header">
627
+ <confidence value="88">21</confidence>
628
+ </boundary-data>
629
+ <page-break num="22"/>
630
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
631
+ similarity score. The analogies are sorted at Block <part-num-ref name="analogies are sorted at Block">1515.</part-num-ref>
632
+ For each analogy (Block 1520), if the analogy is rank <part-num-ref name="analogy is rank">1,</part-num-ref>
633
+ its analogies (Block <part-num-ref name="analogy is rank 1, its analogies (Block">1535)</part-num-ref>
634
+ are also ranked, and if the target is the rank <confidence value="5">I</confidence>
635
+ analogy of the analogy (Block 1540), then this reciprocity is stored in the (transient) reciprocal filter at Block <part-num-ref name="(transient) reciprocal filter at Block">1550.</part-num-ref>
636
+ </p>
637
+ <p id="p-109" num="109">
638
+ <confidence value="5">[</confidence>
639
+ 0084<confidence value="5">]</confidence>
640
+ Figure 15 also describes how reciprocity is extended to other members of the analogy list. If a target is found to be reciprocal to its rank <part-num-ref name="target is found to be reciprocal to its rank">
641
+ <confidence value="4">1</confidence>
642
+ </part-num-ref>
643
+ analogy, then it is also possible to evaluate other analogies down the list. In other words, even if the analogy is not rank <part-num-ref name="analogy is not rank">1,</part-num-ref>
644
+ if all analogies about it are reciprocal (Blocks <part-num-ref name="analogy is not rank 1, if all analogies about it are reciprocal (Blocks">1530</part-num-ref>
645
+ and 1545), then it too is still a possibility to enter the coherence set. These operations can proceed as if the reciprocal rank <part-num-ref name="reciprocal rank">1</part-num-ref>
646
+ relationships were removed from the analogy sets and the process is repeated, moving the next most similar entities into the rank <part-num-ref name="rank">1</part-num-ref>
647
+ position. As shown in Figure 15, the reciprocal relationship when moving down the list should still be satisfied by both entities, the target and the analogy. Figure 16 graphically illustrates how this reciprocal relation can extend beyond rank <part-num-ref name="graphically illustrates how this reciprocal relation can extend beyond rank">1,</part-num-ref>
648
+ but can still locate the natural "breaks" in similarity, where a set of entities can be seen as disjoint from others. </p>
649
+ <p id="p-110" num="110">
650
+ <confidence value="5">[</confidence>
651
+ 0085<confidence value="5">]</confidence>
652
+ It will be understood that embodiments of the invention can be generalized to the mutual reciprocity of any rank order <part-num-ref name="mutual reciprocity of any rank order">(1,</part-num-ref>
653
+ <part-num-ref name="mutual reciprocity of any rank order (1,">2,</part-num-ref>
654
+ <part-num-ref name="mutual reciprocity of any rank order (1, 2,">3,</part-num-ref>
655
+ or more). However, the natural, extreme threshold of rank order <part-num-ref name="natural, extreme threshold of rank order">1</part-num-ref>
656
+ is most severe and may be most informative as the most discriminatory honing of coherence sets from all the information in the cognitive map. </p>
657
+ <p id="p-111" num="111">
658
+ <confidence value="5">[</confidence>
659
+ 0086<confidence value="5">]</confidence>
660
+ Figure 17 graphically illustrates construction of a subgraph of similarities <part-num-ref name="subgraph of similarities">1710</part-num-ref>
661
+ based on reciprocity. Figure 17 demonstrates how the extension of reciprocity grows to include Person:B, Person:D, and then Person:C as within a single connected graph. These three entities are members of a cluster, but more than just a cluster, the pair-wise reciprocal links form a sub-graph, not a f<confidence value="8">u</confidence>
662
+ lly connected clique. </p>
663
+ <p id="p-112" num="112">
664
+ <confidence value="5">[</confidence>
665
+ 0087<confidence value="5">]</confidence>
666
+ In summary, embodiments of the invention can be based on the evidence provided by real data. Associations can be defined by data correlations while entropy can be used to decorrelate spurious associations. Finally, coherence provides an additional filter of these associations, revealing only those that are most reasonable to report. Such filtering can be based on natural groupings rather than arbitrary thresholds and other parameters for typical segmentation. Reciprocity, the agreement between at least two perspectives, can define the natural basis for coherence. </p>
667
+ <boundary-data type="header">
668
+ <confidence value="88">22</confidence>
669
+ </boundary-data>
670
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
671
+ <p id="p-113" num="113">
672
+ <page-break num="23"/>
673
+ <confidence value="5">[</confidence>
674
+ 0088<confidence value="4">]</confidence>
675
+ Distance measures such as cosine and Jacquard generally assume complete knowledge in the vector description. In other words, the vector that describes a document or an entity is a list of the values that are apparently true. </p>
676
+ <p id="p-114" num="114">However, such differencing methods may also assume that missing values are in fact missing. As in the Jacquard method, missing values add some discount to similarity.</p>
677
+ <p id="p-115" num="115">In the real world of messy, incomplete, real time, and changing data, the absence of evidence is not evidence of absence. In alias detection for example, a new identity will arise for which there is little information as yet, compared to important targets for which a great deal of information is already well known. This differential lack in knowledge should not penalize the degree of similarity that is so far apparent.</p>
678
+ <p id="p-116" num="116">Embodiments of the invention can assume a more pure adherence to the facts, and only the facts, in measuring similarity. In document similarity as another example, here too, absence of a term is not necessarily absence, unless the vector provides that all concept, relational, and latent semantic similarities have also been tested for possible inclusion.</p>
679
+ <p id="p-117" num="117">[0089] Moreover, embodiments of the invention can build semantic networks from real data, which is complex and messy, but can also offer opportunities for deeper metrics. Rather than the mere existence of particular attributes or links, such data variability can be used to ascertain the information content of the link. Some conventional data cleansing techniques are beginning to include Inverted Document Frequency (IDF) as at least some measure of informativeness. In other words, some attributes are more important than others. For instance, in international travel, the city of London might be expected to appear more often than Timbuktu. Highly informative similarities should be weighted more; the attribute of traveling to Timbuktu is, therefore, more informative than traveling to London. However, IDF is only an approximation of the informativeness in a given term. Embodiments of the invention can use a more precise measure than IDF. In particular, embodiments of the invention can provide a specific formulation of entropy as a measure of differential information, as was described extensively above.</p>
680
+ <p id="p-118" num="118">[0090] As was also described above, entropy-based similarity according to some embodiments of the invention generally is highly directional. Thus, the information available to one node is unlikely to be identical for another node. This creates an asymmetrical similarity matrix, which is not typical nor even generally desirable for the assumptions of other clustering techniques. Beyond even the <boundary-data type="header">
681
+ <confidence value="88">23</confidence>
682
+ </boundary-data>
683
+ <page-break num="24"/>
684
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
685
+ assumption of triangularity equality between sets of distances, a single "distance" is not the same from both perspectives, in some embodiments of the invention. On the other hand, this makes any "confirmation" between the perspectives all the rarer and better able to "hone" on the most coherent, mutual similarities. Shared nearest neighbor methods may provide for some aspects of reciprocity. However, shared nearest neighbor methods account for common third-party neighbors, whereas, in some embodiments of the invention, for pure reciprocity with asymmetric weights, both perspectives in the pair itself require the primacy of each other (and then their neighbors in course). Coherence can be rarer and more selective, according to embodiments of the invention. In other embodiments of the invention, filtering by reciprocal coherence may be provided even when bidirectional (symmetric) weights are used. </p>
686
+ <p id="p-119" num="119">
687
+ <confidence value="5">[</confidence>
688
+ 0091] Also beyond shared nearest neighbors, some embodiments of the invention can take the asymmetric similarity matrix one step further by then analyzing the graph structure of the coherent subgroup. While shared neighbor methods generally are non-centroid and non-exhaustive, they still may be used as merely a way to segment a set of points into group membership. In contrast, embodiments of the invention can analyze the internal structure of each group and use such measures to rank the subgroups themselves. Rather than clustering, whether by globular or non- globular methods, the purpose of analogy detection can be more akin to a signal detection task. While segmentation typically tries to exhaustively place all points in one cluster or another, this need not be performed by embodiments of the invention. </p>
689
+ <p id="p-120" num="120">Embodiments of the invention may only want to know about those "clumps" of coherence that resonate as the <confidence value="22222">creme</confidence>
690
+ de la <confidence value="22222">creme</confidence>
691
+ analogies. Alias detection for example, may not be interested in clustering a population, but only wants to find those rare clumps of identities that are likely aliases of each other. Document clustering as another example, may not care to organize all the documents but only to present the most coherent subsets of documents that define major, integrating topics. For such signal detection applications based on analogy, embodiments of the invention can combine similarity scoring, ranking, subgrouping with additional scoring and ranking of the subgroups by looking at their graph structure. As a signal detection task, the true analogies should be found in the best subgraphs as additionally defined by the graph structure itself. The "noise" of other links can be irrelevant. </p>
692
+ <boundary-data type="header">
693
+ <confidence value="88">24</confidence>
694
+ </boundary-data>
695
+ <boundary-data type="header">Attorney Docket 9146-5</boundary-data>
696
+ <p id="p-121" num="121">
697
+ <page-break num="25"/>
698
+ <confidence value="2">1</confidence>
699
+ 0092] In the drawings and specification, there have been disclosed embodiments of the invention and, although specific terms are employed, they are used in a generic and descriptive sense only and not for purposes of limitation, the scope of the invention being set forth in the following claims. </p>
700
+ <boundary-data type="header">
701
+ <confidence value="88">25</confidence>
702
+ </boundary-data>
703
+ </description>
704
+ </us-patent-application>
705
+
prior_art/11038590.xml ADDED
The diff for this file is too large to render. See raw diff
 
prior_art/11047958.xml ADDED
@@ -0,0 +1,21 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11047958</doc-number>
8
+ <date>2010-07-01</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <p id="p-1" num="1">In the S<confidence value="5">p</confidence>
14
+ ecification On page <part-num-ref name="Specification On page">1,</part-num-ref>
15
+ please replace the title with the following: </p>
16
+ <p id="p-2" num="2">Training Mode For Image Capture Devices <confidence value="8">2</confidence>
17
+ <confidence value="2222222">oosoorm</confidence>
18
+ </p>
19
+ </description>
20
+ </us-patent-application>
21
+
prior_art/11065197.xml ADDED
@@ -0,0 +1,634 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11065197</doc-number>
8
+ <date>2005-02-24</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <boundary-data type="header">Attorney Docket No.:2003-0786.02</boundary-data>
14
+ <heading id="h-1">METHOD FOR PROVIDING REDUCED</heading>
15
+ <heading id="h-2">COST IMAGING TO CUSTOMERS</heading>
16
+ <heading id="h-3">BACKGROUND OF THE INVENTION</heading>
17
+ <p id="p-1" num="1">
18
+ <boundary-data type="line-number">5 </boundary-data>
19
+ 1. Field of the invention. </p>
20
+ <p id="p-2" num="2">The present invention relates to imaging, and, more particularly, to providing reduced cost imaging to customers, such as high usage customers.</p>
21
+ <p id="p-3" num="3">2. Description of the related art.</p>
22
+ <p id="p-4" num="4">Incentive initiatives, e.g., coupons and rebates, have long been used to attract <boundary-data type="line-number">10 </boundary-data>
23
+ consumers to purchase certain products. For example, supply items used in imaging with printers and copiers have been subject to such coupon and rebate programs. </p>
24
+ <p id="p-5" num="5">Supply items differ from many products, however, in that they are purchased on a recurring basis. For high usage customers, the recurrence may be a matter of weeks, or in some cases a few days. However, traditional coupon and rebate programs may not <boundary-data type="line-number">15 </boundary-data>
25
+ adequately reward high usage customers, such as for example, due to quantity limitations for the program. </p>
26
+ <heading id="h-4">SUMMARY OF THE INVENTION</heading>
27
+ <p id="p-6" num="6">The present invention relates to a method for providing reduced cost imaging to <boundary-data type="line-number">20 </boundary-data>
28
+ customers, such as for example, high usage customers. </p>
29
+ <p id="p-7" num="7">The present invention, in one exemplary embodiment, is directed to a method for reducing a cost of imaging to a customer, including determining a rate of consumption of imaging substance from a supply item; and, based on the rate of consumption, offering to the customer an imaging reward.</p>
30
+ <p id="p-8" num="8">
31
+ <boundary-data type="line-number">25 </boundary-data>
32
+ The present invention, in another embodiment, is directed to a supply item for use in an imaging apparatus, the supply item being associated with memory for storing information upon which a rate of consumption of imaging substance from the supply item can be determined, wherein at least one of a cost and an amount of imaging substance associated with an imaging reward is based on the rate of consumption. </p>
33
+ <p id="p-9" num="9">
34
+ <boundary-data type="line-number">30 </boundary-data>
35
+ The present invention, in another embodiment, is directed to a method for reducing a cost of imaging to a customer, including determining a rate of consumption of imaging substance from a supply item during a current license, wherein an amount of the imaging substance in the supply item is more than will be consumed during the current license; and, based on the rate of consumption during the current license, <boundary-data type="header">
36
+ <confidence value="7">1</confidence>
37
+ </boundary-data>
38
+ <page-break num="2"/>
39
+ <boundary-data type="header">Attorney Docket No.:2003-0786.02</boundary-data>
40
+ offering to the customer a new license for at least a portion of a remainder of the amount of imaging substance. </p>
41
+ <heading id="h-5">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
42
+ <p id="p-10" num="10">
43
+ <boundary-data type="line-number">5 </boundary-data>
44
+ The above-mentioned and other features and advantages of this invention, and the manner of attaining them, will become more apparent and the invention will be better understood by reference to the following description of embodiments of the invention taken in conjunction with the accompanying drawings, wherein: </p>
45
+ <p id="p-11" num="11">Fig. 1 is a diagrammatic depiction of an embodiment of a system that <boundary-data type="line-number">10 </boundary-data>
46
+ implements the present invention. </p>
47
+ <p id="p-12" num="12">Figs. 2A and 2B combine to form a general flowchart representing a method for reducing a cost of imaging for a customer, such as a high usage customer.</p>
48
+ <p id="p-13" num="13">Figs. 3A and 3B combine to form a general flowchart depicting an embodiment of a security method wherein the imaging apparatus contains the license.</p>
49
+ <p id="p-14" num="14">
50
+ <boundary-data type="line-number">15 </boundary-data>
51
+ Figs. 4A and 4B combine to form a flowchart depicting an embodiment of a security method wherein the supply item contains the license. </p>
52
+ <p id="p-15" num="15">Fig. 5 is a flowchart depicting another embodiment of a security method wherein the supply item contains the license.</p>
53
+ <p id="p-16" num="16">Corresponding reference characters indicate corresponding parts throughout the <boundary-data type="line-number">20 </boundary-data>
54
+ several views. The exemplifications set out herein illustrate exemplary embodiments of the invention and such exemplifications are not to be construed as limiting the scope of the invention in any manner. </p>
55
+ <heading id="h-6">DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS</heading>
56
+ <p id="p-17" num="17">
57
+ <boundary-data type="line-number">25 </boundary-data>
58
+ Referring now to the drawings and particularly to Fig. 1, there is shown a diagrammatic depiction of an imaging system <part-num-ref name="imaging system">10</part-num-ref>
59
+ embodying the present invention. </p>
60
+ <p id="p-18" num="18">Imaging system 10 may include an imaging apparatus <part-num-ref name="imaging apparatus">12,</part-num-ref>
61
+ a host <part-num-ref name="host">14</part-num-ref>
62
+ (optional), and a license vendor <part-num-ref name="license vendor">16.</part-num-ref>
63
+ Imaging apparatus <part-num-ref name="license vendor 16. Imaging apparatus">12</part-num-ref>
64
+ <confidence value="2222222222222">conmnunicates</confidence>
65
+ with host <part-num-ref name="conmnunicates with host">14</part-num-ref>
66
+ via a communications link <part-num-ref name="communications link">18.</part-num-ref>
67
+ License vendor <part-num-ref name="communications link 18. License vendor">16</part-num-ref>
68
+ may communicate with one, or both, of <boundary-data type="line-number">30 </boundary-data>
69
+ imaging apparatus <part-num-ref name="may communicate with one, or both, of imaging apparatus">12</part-num-ref>
70
+ and host <part-num-ref name="and host">14.</part-num-ref>
71
+ For example, license vendor <part-num-ref name="and host 14. For example, license vendor">16</part-num-ref>
72
+ may communicate with imaging apparatus <part-num-ref name="may communicate with imaging apparatus">12</part-num-ref>
73
+ via communications link <part-num-ref name="via communications link">20</part-num-ref>
74
+ and/or may communicate with host <part-num-ref name="and/or may communicate with host">14</part-num-ref>
75
+ via communications link <part-num-ref name="via communications link">22,</part-num-ref>
76
+ which is optional as indicated by the dashed line. </p>
77
+ <boundary-data type="header">
78
+ <confidence value="8">2</confidence>
79
+ </boundary-data>
80
+ <boundary-data type="header">Attorney Docket No.:2003-0786.02</boundary-data>
81
+ <p id="p-19" num="19">
82
+ <page-break num="3"/>
83
+ As used herein, the term "communications link" is used to generally refer to structure that facilitates electronic communication between two or more components, and may operate using wired or wireless technology. </p>
84
+ <p id="p-20" num="20">Communications link 18 may be established, for example, by a direct cable <boundary-data type="line-number">5 </boundary-data>
85
+ connection, wireless connection or by a network connection such as for example an Ethernet local area network (LAN). Imaging apparatus <part-num-ref name="Ethernet local area network (LAN). Imaging apparatus">12</part-num-ref>
86
+ may communicate with host <part-num-ref name="may communicate with host">14</part-num-ref>
87
+ via a standard communication protocol, such as for example, universal serial bus (USB) or Ethernet. Communication links <part-num-ref name="standard communication protocol, such as for example, universal serial bus (USB) or Ethernet. Communication links">20,</part-num-ref>
88
+ <part-num-ref name="standard communication protocol, such as for example, universal serial bus (USB) or Ethernet. Communication links 20,">22</part-num-ref>
89
+ may be established, for example, by a direct cable connection, wireless connection or by a network connection, such as a <boundary-data type="line-number">10 </boundary-data>
90
+ LAN, wide area network or Internet connection. </p>
91
+ <p id="p-21" num="21">In embodiments including host 14, host 14 may be, for example, a personal computer including a display monitor, an input device (e.g., keyboard), a processor, input/output (<confidence value="224">11O</confidence>
92
+ ) interfaces, memory, such as RAM, ROM, NVRAM, and a mass data storage device, such as a hard drive, CD-ROM and/or DVD units. During operation, <boundary-data type="line-number">15 </boundary-data>
93
+ host <part-num-ref name="hard drive, CD-ROM and/or DVD units. During operation, host">14</part-num-ref>
94
+ includes in its memory a software program including program instructions that function as an imaging driver <part-num-ref name="imaging driver">24</part-num-ref>
95
+ for imaging apparatus <part-num-ref name="for imaging apparatus">12.</part-num-ref>
96
+ Imaging driver <part-num-ref name="for imaging apparatus 12. Imaging driver">24</part-num-ref>
97
+ serves to facilitate communications between imaging apparatus <part-num-ref name="serves to facilitate communications between imaging apparatus">12,</part-num-ref>
98
+ and optionally, may serve to facilitate communications with license vendor <part-num-ref name="serves to facilitate communications between imaging apparatus 12, and optionally, may serve to facilitate communications with license vendor">16.</part-num-ref>
99
+ In addition, imaging driver <part-num-ref name="serves to facilitate communications between imaging apparatus 12, and optionally, may serve to facilitate communications with license vendor 16. In addition, imaging driver">24</part-num-ref>
100
+ serves in the traditional roll of providing formatted print data to imaging apparatus <part-num-ref name="traditional roll of providing formatted print data to imaging apparatus">12.</part-num-ref>
101
+ </p>
102
+ <p id="p-22" num="22">
103
+ <boundary-data type="line-number">20 </boundary-data>
104
+ Imaging apparatus 12 may include an ink jet print engine, or an electrophotographic print engine. Further, imaging apparatus <part-num-ref name="electrophotographic print engine. Further, imaging apparatus">12</part-num-ref>
105
+ may be used as a standalone unit that is not communicatively linked to a host, such as host <part-num-ref name="host, such as host">14.</part-num-ref>
106
+ For example, imaging apparatus <part-num-ref name="host, such as host 14. For example, imaging apparatus">12</part-num-ref>
107
+ may take the form of a multifunction machine, e.g., an all-in-one (AIO) device, which includes standalone copying and facsimile capabilities, <boundary-data type="line-number">25 </boundary-data>
108
+ in addition to optionally serving as a printer when attached to a host, such as host <part-num-ref name="host, such as host">14.</part-num-ref>
109
+ </p>
110
+ <p id="p-23" num="23">In one embodiment, the stand-alone features of imaging apparatus <part-num-ref name="stand-alone features of imaging apparatus">12</part-num-ref>
111
+ includes connectivity and processing capability sufficient to implement the various methods of the invention in the absence of host <part-num-ref name="absence of host">14.</part-num-ref>
112
+ In some implementations, for example, imaging apparatus <part-num-ref name="absence of host 14. In some implementations, for example, imaging apparatus">12</part-num-ref>
113
+ may communicate directly with license vendor <part-num-ref name="may communicate directly with license vendor">16</part-num-ref>
114
+ via communication link <boundary-data type="line-number">30 </boundary-data>
115
+ <part-num-ref name="via communication link">20,</part-num-ref>
116
+ such as for example, a telephone line connection. </p>
117
+ <p id="p-24" num="24">Imaging apparatus 12 may include, for example, a user interface <part-num-ref name="user interface">28,</part-num-ref>
118
+ an image recording unit <part-num-ref name="image recording unit">30,</part-num-ref>
119
+ a supply item <part-num-ref name="supply item">32</part-num-ref>
120
+ and a controller <part-num-ref name="controller">34,</part-num-ref>
121
+ which may be in the form of one or more Application Specific Integrated Circuits (ASIC). Controller <part-num-ref name="form of one or more Application Specific Integrated Circuits (ASIC). Controller">34</part-num-ref>
122
+ communicates <boundary-data type="header">
123
+ <confidence value="8">3</confidence>
124
+ </boundary-data>
125
+ <page-break num="4"/>
126
+ <boundary-data type="header">Attorney Docket No.:2003-0786.02</boundary-data>
127
+ with image recording unit <part-num-ref name="communicates with image recording unit">30</part-num-ref>
128
+ via a communications link <part-num-ref name="communications link">38.</part-num-ref>
129
+ Controller <part-num-ref name="communications link 38. Controller">34</part-num-ref>
130
+ communicates with supply item <part-num-ref name="communicates with supply item">32</part-num-ref>
131
+ via a communications link <part-num-ref name="communications link">40.</part-num-ref>
132
+ </p>
133
+ <p id="p-25" num="25">In the context of the examples for imaging apparatus <part-num-ref name="examples for imaging apparatus">12</part-num-ref>
134
+ given above, image recording unit <part-num-ref name="given above, image recording unit">30</part-num-ref>
135
+ may be, for example, an ink jet printhead unit or an <boundary-data type="line-number">5 </boundary-data>
136
+ electrophotographic printing unit, and includes an imaging head <part-num-ref name="imaging head">36</part-num-ref>
137
+ used for forming an image on a substrate <part-num-ref name="substrate">42,</part-num-ref>
138
+ such as a sheet of print media, e.g., paper, transparency, fabric, etc., or a photoconductive member. For convenience, each type of substrate <part-num-ref name="photoconductive member. For convenience, each type of substrate">42</part-num-ref>
139
+ will be referred to by the element number <part-num-ref name="element number">42,</part-num-ref>
140
+ for example, sheet(s) of print media <part-num-ref name="element number 42, for example, sheet(s) of print media">42.</part-num-ref>
141
+ </p>
142
+ <p id="p-26" num="26">Supply item 32 can be, for example, an ink supply tank, an ink jet cartridge, a <boundary-data type="line-number">10 </boundary-data>
143
+ toner tank, or an electrophotographic process (EP) cartridge, each of which containing a supply of an imaging substance, such as for example ink or toner, that is consumed during an imaging process. Imaging apparatus <part-num-ref name="imaging process. Imaging apparatus">12</part-num-ref>
144
+ uses the imaging substance contained in supply item <part-num-ref name="imaging substance contained in supply item">32</part-num-ref>
145
+ to form an image on the sheet of print media <part-num-ref name="sheet of print media">42.</part-num-ref>
146
+ Those skilled in the art will recognize that image recording unit <part-num-ref name="art will recognize that image recording unit">30</part-num-ref>
147
+ and supply item <part-num-ref name="and supply item">32</part-num-ref>
148
+ may be formed as <boundary-data type="line-number">15 </boundary-data>
149
+ individual discrete units, or may be combined in an integral unit, these options being depicted by dashed line <part-num-ref name="integral unit, these options being depicted by dashed line">44.</part-num-ref>
150
+ Thus, as used herein, the term "supply item" is intended to refer to either possibility. </p>
151
+ <p id="p-27" num="27">Supply item 32 can be subject to a license as to the amount of imaging substance contained therein that is available for use. The license may be referenced, for example, <boundary-data type="line-number">20 </boundary-data>
152
+ by license information, which may include a license identification and a licensed amount of usage. The initial supply amount (fill level) of imaging substance contained in supply item <part-num-ref name="initial supply amount (fill level) of imaging substance contained in supply item">32</part-num-ref>
153
+ can be greater than the initial licensed amount of usage of the imaging substance in supply item <part-num-ref name="imaging substance in supply item">32.</part-num-ref>
154
+ For example, in one implementation of the invention, the initial supply amount of the imaging substance contained in supply item <part-num-ref name="imaging substance contained in supply item">32</part-num-ref>
155
+ may be, for <boundary-data type="line-number">25 </boundary-data>
156
+ example, at least two times greater than the licensed amount. It is important to note, however, that while the initial amount of imaging substance supplied with imaging apparatus <part-num-ref name="initial amount of imaging substance supplied with imaging apparatus">12</part-num-ref>
157
+ and/or supply item <part-num-ref name="and/or supply item">32</part-num-ref>
158
+ is sufficient to accommodate both the initial license and one or more license renewals, the consumer has been required to pay only for the licensed amount at the time of the original supply item acquisition. </p>
159
+ <p id="p-28" num="28">
160
+ <boundary-data type="line-number">30 </boundary-data>
161
+ The licensed amount of usage of supply item 32 may be represented in a variety of forms, such as for example: the amount of imaging substance consumed from supply item 32; the number of imaging dots formed on print media, such as sheets of print media 42; the percent of image coverage on the printed sheets of media 42; the number <boundary-data type="header">
162
+ <confidence value="8">4</confidence>
163
+ </boundary-data>
164
+ <page-break num="5"/>
165
+ <boundary-data type="header">Attorney Docket No.:2003-0786.02</boundary-data>
166
+ of sheets of print media printed by supply item 32; the number of sheets printed by supply item <part-num-ref name="number of sheets printed by supply item">32</part-num-ref>
167
+ that exceeds a predetermined coverage amount; the number of imaging operations performed by imaging apparatus <part-num-ref name="number of imaging operations performed by imaging apparatus">12</part-num-ref>
168
+ with supply item <part-num-ref name="with supply item">32</part-num-ref>
169
+ installed; and/or an amount of time. </p>
170
+ <p id="p-29" num="29">
171
+ <boundary-data type="line-number">5 </boundary-data>
172
+ In one embodiment, supply item 32 has mounted thereto an electronics module <part-num-ref name="electronics module">46,</part-num-ref>
173
+ which includes memory for storing information relating to supply item <part-num-ref name="electronics module 46, which includes memory for storing information relating to supply item">32.</part-num-ref>
174
+ In some embodiments, electronics module <part-num-ref name="electronics module 46, which includes memory for storing information relating to supply item 32. In some embodiments, electronics module">46</part-num-ref>
175
+ may include a controller ASIC for performing program instructions relating to the licensing of supply item <part-num-ref name="licensing of supply item">32.</part-num-ref>
176
+ By attaching electronics module <part-num-ref name="licensing of supply item 32. By attaching electronics module">46</part-num-ref>
177
+ to supply item <part-num-ref name="to supply item">32,</part-num-ref>
178
+ in essence, the information relating to supply <boundary-data type="line-number">10 </boundary-data>
179
+ item <part-num-ref name="information relating to supply item">32,</part-num-ref>
180
+ e.g., usage license information associated with supply item <part-num-ref name="usage license information associated with supply item">32,</part-num-ref>
181
+ can travel with supply item <part-num-ref name="usage license information associated with supply item 32, can travel with supply item">32</part-num-ref>
182
+ from one imaging apparatus to another. The information relating to supply item <part-num-ref name="information relating to supply item">32</part-num-ref>
183
+ may include, for example: a supply item identification number; a fill level, i.e., the initial amount of the imaging substance contained in supply item 32; a type of supply item <part-num-ref name="type of supply item">32,</part-num-ref>
184
+ e.g., monochrome, color, photo, etc.; a usage gauge to maintain <boundary-data type="line-number">15 </boundary-data>
185
+ a record of usage of supply item 32; and/or usage license information, which may <confidence value="4">-</confidence>
186
+ include a license identification and an indication of the licensed amount of usage of supply item <part-num-ref name="licensed amount of usage of supply item">32.</part-num-ref>
187
+ </p>
188
+ <p id="p-30" num="30">License vendor 16 provides to a consumer access to a new usage license.</p>
189
+ <p id="p-31" num="31">License vendor 16 may be, for example, a license server, and may facilitate e-commerce <boundary-data type="line-number">20 </boundary-data>
190
+ transactions. In summary, in the licensing methods of the invention, a usage license is associated with at least one of imaging apparatus <part-num-ref name="usage license is associated with at least one of imaging apparatus">12</part-num-ref>
191
+ and supply item <part-num-ref name="and supply item">32,</part-num-ref>
192
+ and when the usage of imaging apparatus <part-num-ref name="usage of imaging apparatus">12</part-num-ref>
193
+ and/or supply item <part-num-ref name="and/or supply item">32</part-num-ref>
194
+ has reached a predefined usage threshold, the consumer is prompted to acquire a new license from license vendor <part-num-ref name="new license from license vendor">16.</part-num-ref>
195
+ </p>
196
+ <p id="p-32" num="32">This predefined usage threshold can, for example, represent a usage amount that is <boundary-data type="line-number">25 </boundary-data>
197
+ associated with the license being close to expiring, or a usage amount associated with license expiration. </p>
198
+ <p id="p-33" num="33">In one embodiment of the invention, for example, license vendor <part-num-ref name="invention, for example, license vendor">16</part-num-ref>
199
+ may be an <confidence value="5">e</confidence>
200
+ -commerce server that may be accessed by a customer via on-line communications over the Internet to acquire the new license. The e-commerce server may include a <boundary-data type="line-number">30 </boundary-data>
201
+ database established for enrolling and monitoring the customer's participation in an imaging rewards program, such as a license, electronic coupon, or rebate program, based on a rate of consumption of imaging substance, also referred to herein as a usage rate. The e-commerce server may be maintained in a database with confirmation <boundary-data type="header">
202
+ <confidence value="8">5</confidence>
203
+ </boundary-data>
204
+ <page-break num="6"/>
205
+ <boundary-data type="header">Attorney Docket No.:2003-0786.02</boundary-data>
206
+ electronically transmitted to imaging apparatus <part-num-ref name="database with confirmation electronically transmitted to imaging apparatus">12</part-num-ref>
207
+ or host <part-num-ref name="or host">14.</part-num-ref>
208
+ The acquisition of an additional supply item may be in the form of a renewal of supply item <part-num-ref name="renewal of supply item">32.</part-num-ref>
209
+ The renewal may be in the form of a replacement for supply item <part-num-ref name="replacement for supply item">32,</part-num-ref>
210
+ a number of physical replenishments of supply item <part-num-ref name="number of physical replenishments of supply item">32,</part-num-ref>
211
+ or, in a licensing implementation, by a virtual <boundary-data type="line-number">5 </boundary-data>
212
+ replenishment of supply item <part-num-ref name="virtual replenishment of supply item">32</part-num-ref>
213
+ through a new license, e.g., license renewal(s). </p>
214
+ <p id="p-34" num="34">Also shown in Fig. 1 is a license monitoring mechanism <part-num-ref name="license monitoring mechanism">48,</part-num-ref>
215
+ which is a functional unit that may reside in either of imaging apparatus <part-num-ref name="functional unit that may reside in either of imaging apparatus">12</part-num-ref>
216
+ or host <part-num-ref name="or host">14,</part-num-ref>
217
+ or may reside in a combination of imaging apparatus <part-num-ref name="combination of imaging apparatus">12</part-num-ref>
218
+ and a host <part-num-ref name="host">14,</part-num-ref>
219
+ these options being depicted by the dashed-line representing license monitoring mechanism <part-num-ref name="dashed-line representing license monitoring mechanism">48.</part-num-ref>
220
+ For <boundary-data type="line-number">10 </boundary-data>
221
+ example, license monitoring mechanism <part-num-ref name="dashed-line representing license monitoring mechanism 48. For example, license monitoring mechanism">48</part-num-ref>
222
+ may be formed, in whole or in part, in controller <part-num-ref name="may be formed, in whole or in part, in controller">34</part-num-ref>
223
+ of imaging apparatus <part-num-ref name="of imaging apparatus">12</part-num-ref>
224
+ or imaging driver <part-num-ref name="or imaging driver">24</part-num-ref>
225
+ of host <part-num-ref name="of host">14.</part-num-ref>
226
+ In one embodiment, for example, license monitoring mechanism <part-num-ref name="of host 14. In one embodiment, for example, license monitoring mechanism">48</part-num-ref>
227
+ is resident in the combination of controller <part-num-ref name="combination of controller">34</part-num-ref>
228
+ of imaging apparatus <part-num-ref name="of imaging apparatus">12</part-num-ref>
229
+ and imaging driver <part-num-ref name="and imaging driver">24</part-num-ref>
230
+ of host <part-num-ref name="of host">14.</part-num-ref>
231
+ </p>
232
+ <p id="p-35" num="35">In general, license monitoring mechanism 48 tracks an amount of usage of supply item <boundary-data type="line-number">15 </boundary-data>
233
+ <part-num-ref name="amount of usage of supply item">32</part-num-ref>
234
+ by imaging apparatus <part-num-ref name="by imaging apparatus">12,</part-num-ref>
235
+ determines whether the amount of usage of supply item <part-num-ref name="amount of usage of supply item">32</part-num-ref>
236
+ by imaging apparatus <part-num-ref name="by imaging apparatus">12</part-num-ref>
237
+ has reached a usage threshold, and upon reaching the usage threshold, then prompting the consumer to acquire a new license, which may include a renewal of the present license. Where a consumer desires an on-line e-commerce acquisition of the new license, for example, license monitoring mechanism <part-num-ref name="new license, for example, license monitoring mechanism">48</part-num-ref>
238
+ may <boundary-data type="line-number">20 </boundary-data>
239
+ initiate and establish communications with license vendor <part-num-ref name="may initiate and establish communications with license vendor">16</part-num-ref>
240
+ for acquiring the new license. </p>
241
+ <p id="p-36" num="36">The usage license may be structured to require a combination of a particular imaging device, such as imaging apparatus <part-num-ref name="particular imaging device, such as imaging apparatus">12,</part-num-ref>
242
+ and a particular supply item, such as supply item <part-num-ref name="particular supply item, such as supply item">32.</part-num-ref>
243
+ Such a combination may be verified by using identification numbers <boundary-data type="line-number">25 </boundary-data>
244
+ associated with the imaging apparatus and the supply item. Alternatively, the license may be structured such that the license only applies to a particular imaging apparatus or to a particular supply item. </p>
245
+ <p id="p-37" num="37">Figs. 2A and 2B combine to form a general flowchart representing one embodiment of a method for reducing a cost of imaging for a customer, such as a high <boundary-data type="line-number">30 </boundary-data>
246
+ usage customer. </p>
247
+ <p id="p-38" num="38">At step S 100, a customer acquires a supply item, e.g., supply item <part-num-ref name="supply item">32,</part-num-ref>
248
+ which is subject to a usage license. The usage license may be associated directly with supply item <part-num-ref name="usage license may be associated directly with supply item">32</part-num-ref>
249
+ (with license information stored in supply item electronics module 46), or <boundary-data type="header">
250
+ <confidence value="8">6</confidence>
251
+ </boundary-data>
252
+ <page-break num="7"/>
253
+ <boundary-data type="header">Attorney Docket No.:2003-0786.02</boundary-data>
254
+ associated indirectly by being associated with imaging apparatus <part-num-ref name="(with license information stored in supply item electronics module 46), or associated indirectly by being associated with imaging apparatus">12.</part-num-ref>
255
+ As set forth above, the imaging substance fill level of supply item <part-num-ref name="imaging substance fill level of supply item">32</part-num-ref>
256
+ when new is sufficient to service an initial license, and at least one new license. For example, the initial license may cover a predetermined initial percent of the total imaging substance contained in supply item <part-num-ref name="total imaging substance contained in supply item">32,</part-num-ref>
257
+ <boundary-data type="line-number">5 </boundary-data>
258
+ e.g., <part-num-ref name="">25</part-num-ref>
259
+ percent, and the new license may cover the remainder, or some predetermined portion of the remainder. </p>
260
+ <p id="p-39" num="39">At step S<confidence value="5">1</confidence>
261
+ 02, the customer installs supply item <part-num-ref name="customer installs supply item">32</part-num-ref>
262
+ in imaging apparatus <part-num-ref name="in imaging apparatus">12.</part-num-ref>
263
+ </p>
264
+ <p id="p-40" num="40">At step S 104, a rate of consumption of supply item <part-num-ref name="rate of consumption of supply item">32</part-num-ref>
265
+ is monitored. The monitoring may be performed, for example, by license monitoring mechanism <part-num-ref name="monitoring may be performed, for example, by license monitoring mechanism">48</part-num-ref>
266
+ of <boundary-data type="line-number">10 </boundary-data>
267
+ imaging apparatus <part-num-ref name="of imaging apparatus">12</part-num-ref>
268
+ and/or host <part-num-ref name="and/or host">14.</part-num-ref>
269
+ The monitoring may be performed continuously, or at a predetermined event, such as for example, when a low level of an imaging substance, such as ink or toner, is identified in supply item <part-num-ref name="imaging substance, such as ink or toner, is identified in supply item">32,</part-num-ref>
270
+ or when a predetermined time has expired. </p>
271
+ <p id="p-41" num="41">It is contemplated that the rate of consumption may be determined based on a <boundary-data type="line-number">15 </boundary-data>
272
+ variety of time and usage criteria. For example, the rate of consumption can be based on an amount of time required to use a specified amount of supply item 32; based on an amount of time between acquisitions of the supply items; based on an amount of use of the supply item, e.g., imaging substance volume depleted, during a specified amount of time; based on an amount of the supply item acquired, e.g., imaging substance volume <boundary-data type="line-number">20 </boundary-data>
273
+ acquired, during a specified amount of time; or, based on a quantity of the supply item, e.g., the number, acquired during a specified amount of time. </p>
274
+ <p id="p-42" num="42">At step S 106, it is determined whether the amount of imaging substance associated with the current usage license associated with supply item <part-num-ref name="current usage license associated with supply item">32</part-num-ref>
275
+ is depleted. </p>
276
+ <p id="p-43" num="43">This determination may be made, for example, by license monitoring mechanism 48 of <boundary-data type="line-number">25 </boundary-data>
277
+ imaging apparatus <part-num-ref name="of imaging apparatus">12</part-num-ref>
278
+ and/or host <part-num-ref name="and/or host">14.</part-num-ref>
279
+ If the determination at step S106 is NO, then the process returns to monitoring at step S <part-num-ref name="process returns to monitoring at step S">104.</part-num-ref>
280
+ </p>
281
+ <p id="p-44" num="44">If the determination at step S106 is YES, then a step S108 it is determined whether there is any remaining imaging substance in supply item <part-num-ref name="step S108 it is determined whether there is any remaining imaging substance in supply item">32</part-num-ref>
282
+ that may be used to service a new license. The determination may be, for example, a calculation performed <boundary-data type="line-number">30 </boundary-data>
283
+ by license monitoring mechanism <part-num-ref name="calculation performed by license monitoring mechanism">48</part-num-ref>
284
+ of imaging apparatus <part-num-ref name="of imaging apparatus">12</part-num-ref>
285
+ and/or host <part-num-ref name="and/or host">14.</part-num-ref>
286
+ If the determination is NO, for example, then at step <confidence value="55">S1</confidence>
287
+ 18 the customer simply may replace the current supply item with a new supply item. The process would then begin over at step S100. </p>
288
+ <boundary-data type="header">
289
+ <confidence value="8">7</confidence>
290
+ </boundary-data>
291
+ <boundary-data type="header">Attorney Docket No.:2003-0786.02</boundary-data>
292
+ <p id="p-45" num="45">
293
+ <page-break num="8"/>
294
+ If the determination at step S<confidence value="5">1</confidence>
295
+ 08 is YES, then at step <confidence value="55">S1</confidence>
296
+ 10 the usage rate during the current license and/or previous license is determined, based on information acquired at step S104. The determination may be, for example, a calculation performed by license monitoring mechanism <part-num-ref name="calculation performed by license monitoring mechanism">48</part-num-ref>
297
+ of imaging apparatus <part-num-ref name="of imaging apparatus">12</part-num-ref>
298
+ and/or host <part-num-ref name="and/or host">14.</part-num-ref>
299
+ </p>
300
+ <p id="p-46" num="46">
301
+ <boundary-data type="line-number">
302
+ <confidence value="8">5</confidence>
303
+ </boundary-data>
304
+ At step S 112, the amount of imaging substance and associated cost for a new license is determined. The determination may be, for example, a calculation performed by license monitoring mechanism <part-num-ref name="calculation performed by license monitoring mechanism">48</part-num-ref>
305
+ of imaging apparatus <part-num-ref name="of imaging apparatus">12</part-num-ref>
306
+ and/or host <part-num-ref name="and/or host">14.</part-num-ref>
307
+ For example, once the initial license has been depleted, the customer may be offered the remaining amount of imaging substance in supply item <part-num-ref name="remaining amount of imaging substance in supply item">32,</part-num-ref>
308
+ or some portion thereof, at a <boundary-data type="line-number">10 </boundary-data>
309
+ price based on the usage rate determined at step S <part-num-ref name="usage rate determined at step S">110.</part-num-ref>
310
+ Generally, the higher the usage rate becomes, the lower the price of the supply item will become. </p>
311
+ <p id="p-47" num="47">In one embodiment, depicted in Table 1, below, the higher the usage rate, the more ink will be offered for the next license and the effective cost per page will decrease.</p>
312
+ <p id="p-48" num="48">
313
+ <boundary-data type="line-number">
314
+ <confidence value="88">15</confidence>
315
+ </boundary-data>
316
+ Time Required Amount of New License Effective Expected to Use Initial Imaging Substance Cost to Per Page Time to Use Licensed Supply for New License Customer Cost to New License <confidence value="5">(</confidence>
317
+ in Weeks<confidence value="6">)</confidence>
318
+ <confidence value="6">(</confidence>
319
+ in Pages) Customer <confidence value="5">(</confidence>
320
+ in Weeks<confidence value="5">)</confidence>
321
+ 26 <part-num-ref name="">150</part-num-ref>
322
+ $10 $0.07 <part-num-ref name="$10 $0.07">26</part-num-ref>
323
+ <part-num-ref name="">13</part-num-ref>
324
+ <part-num-ref name="">300</part-num-ref>
325
+ $15 $0.05 <part-num-ref name="$15 $0.05">26</part-num-ref>
326
+ <part-num-ref name="">6</part-num-ref>
327
+ <part-num-ref name="">600</part-num-ref>
328
+ $20 $0.03 <part-num-ref name="$20 $0.03">24</part-num-ref>
329
+ <part-num-ref name="">3</part-num-ref>
330
+ <part-num-ref name="">900</part-num-ref>
331
+ $20 $0.02 <part-num-ref name="$20 $0.02">18</part-num-ref>
332
+ <part-num-ref name="">2</part-num-ref>
333
+ <part-num-ref name="">1200</part-num-ref>
334
+ $20 $0.02 <part-num-ref name="$20 $0.02">16</part-num-ref>
335
+ Table 1: Imaging Substance Amount and Cost of Next License Offering Thus, in this example, imaging apparatus <part-num-ref name="Table 1: Imaging Substance Amount and Cost of Next License Offering Thus, in this example, imaging apparatus">12</part-num-ref>
336
+ may offer the customer the <boundary-data type="line-number">20 </boundary-data>
337
+ opportunity to purchase a new (second) license, with the amount and the cost of that second license being based on the rate at which the first license was used, i.e., the usage rate of imaging substance during the previous license(s). The higher usage rate customers will have the option of the highest offering or any of the lower offerings. For instance, from Table <part-num-ref name="lower offerings. For instance, from Table">1,</part-num-ref>
338
+ a customer with a time to use initial supply of <part-num-ref name="time to use initial supply of">6</part-num-ref>
339
+ weeks may be <boundary-data type="line-number">25 </boundary-data>
340
+ presented with an offering of an imaging substance equivalent of <part-num-ref name="imaging substance equivalent of">600</part-num-ref>
341
+ pages, as well as options for <part-num-ref name="pages, as well as options for">300</part-num-ref>
342
+ or <part-num-ref name="or">150</part-num-ref>
343
+ pages. However, that same customer will not be given the option of the <part-num-ref name="">900</part-num-ref>
344
+ or <part-num-ref name="or">1200</part-num-ref>
345
+ page offerings. </p>
346
+ <boundary-data type="header">
347
+ <confidence value="8">8</confidence>
348
+ </boundary-data>
349
+ <boundary-data type="header">Attorney Docket No.:2003-0786.02</boundary-data>
350
+ <p id="p-49" num="49">
351
+ <page-break num="9"/>
352
+ Accordingly, the acquisition cost of the new license associated with supply item <part-num-ref name="new license associated with supply item">32</part-num-ref>
353
+ remains low, regardless of which usage rate is determined, but customers having higher usage rates will benefit from lower cost per page imaging, thereby further decreasing the total cost of imaging for the higher usage customers. </p>
354
+ <p id="p-50" num="50">
355
+ <boundary-data type="line-number">5 </boundary-data>
356
+ Another benefit is that the license replenishment rate will remain relatively constant regardless of the usage rate. For example, from the far right column of Table <part-num-ref name="far right column of Table">1,</part-num-ref>
357
+ it can be seen that the licenses for <part-num-ref name="licenses for">150,</part-num-ref>
358
+ <part-num-ref name="licenses for 150,">300</part-num-ref>
359
+ and <part-num-ref name="and">600</part-num-ref>
360
+ pages are expected to expire within <part-num-ref name="pages are expected to expire within">24</part-num-ref>
361
+ to <part-num-ref name="to">26</part-num-ref>
362
+ weeks. </p>
363
+ <p id="p-51" num="51">At step S 114, the customer is offered a new license, such as for example, by <boundary-data type="line-number">10 </boundary-data>
364
+ displaying a message at the user interface <part-num-ref name="user interface">28</part-num-ref>
365
+ of imaging apparatus <part-num-ref name="of imaging apparatus">12,</part-num-ref>
366
+ and/or at the display monitor of host <part-num-ref name="display monitor of host">14.</part-num-ref>
367
+ </p>
368
+ <p id="p-52" num="52">At step S <confidence value="66">11</confidence>
369
+ 6, it is determined whether the customer wants to purchase a new license. This determination may be made, for example, by controller <part-num-ref name="new license. This determination may be made, for example, by controller">34</part-num-ref>
370
+ or host <part-num-ref name="or host">14</part-num-ref>
371
+ based on input received from the customer, such as via user interface <part-num-ref name="customer, such as via user interface">28</part-num-ref>
372
+ of imaging <boundary-data type="line-number">15 </boundary-data>
373
+ apparatus <part-num-ref name="of imaging apparatus">12</part-num-ref>
374
+ or a keyboard of host <part-num-ref name="keyboard of host">14.</part-num-ref>
375
+ If the determination is NO, then the process proceeds to step S <part-num-ref name="process proceeds to step S">118,</part-num-ref>
376
+ and then the process is ended for the current supply item. </p>
377
+ <p id="p-53" num="53">If at step S116 the determination is YES, then at step S120 the customer purchases a new license via license vendor <part-num-ref name="new license via license vendor">16,</part-num-ref>
378
+ which may be, for example, an e- commerce transaction. In the present embodiment, the license replenishment process is <boundary-data type="line-number">20 </boundary-data>
379
+ accomplished through an electronic means whereby imaging apparatus <part-num-ref name="electronic means whereby imaging apparatus">12,</part-num-ref>
380
+ or alternatively host <part-num-ref name="electronic means whereby imaging apparatus 12, or alternatively host">14,</part-num-ref>
381
+ contacts license vendor <part-num-ref name="electronic means whereby imaging apparatus 12, or alternatively host 14, contacts license vendor">16</part-num-ref>
382
+ through an electronic network, such as for example, the Internet. Once contact is made with license vendor <part-num-ref name="Internet. Once contact is made with license vendor">16,</part-num-ref>
383
+ the customer will be required to perform an e-com<confidence value="5">m</confidence>
384
+ erce transaction. After license vendor <part-num-ref name="e-commerce transaction. After license vendor">16</part-num-ref>
385
+ verifies the e-commerce transaction is successful, license vendor <part-num-ref name="e-commerce transaction is successful, license vendor">16</part-num-ref>
386
+ will send the printer a <boundary-data type="line-number">25 </boundary-data>
387
+ license, e.g., license identification and associated license amount, by a secure electronic transmission, such as those known in the art, or by using one of the security measures more fully described below. </p>
388
+ <p id="p-54" num="54">At step S122, a security system verifies the new license as valid. The security system may be incorporated, for example, into license monitoring mechanism <part-num-ref name="security system may be incorporated, for example, into license monitoring mechanism">48.</part-num-ref>
389
+ Once <boundary-data type="line-number">30 </boundary-data>
390
+ verified, printing is resumed at step S124, and the process returns to usage rate monitoring at step S104. The security measures performed at step S<confidence value="5">1</confidence>
391
+ 22 will be described in more detail below with respect to the embodiments of Figs 3A, 3B; Figs. </p>
392
+ <p id="p-55" num="55">4A, 4B; and Fig. 5.</p>
393
+ <boundary-data type="header">
394
+ <confidence value="8">9</confidence>
395
+ </boundary-data>
396
+ <boundary-data type="header">Attorney Docket No.:2003-0786.02</boundary-data>
397
+ <p id="p-56" num="56">
398
+ <page-break num="10"/>
399
+ Once the second license is depleted, if there is enough imaging substance in supply item <part-num-ref name="second license is depleted, if there is enough imaging substance in supply item">32</part-num-ref>
400
+ to accommodate an additional license, the customer will again be offered a new license. The amount and cost of the third license (second new license) will again be a function of the usage rate of the first and second licenses. This licensing process <boundary-data type="line-number">5 </boundary-data>
401
+ may be repeated as long as there is imaging substance available in supply item <part-num-ref name="first and second licenses. This licensing process may be repeated as long as there is imaging substance available in supply item">32.</part-num-ref>
402
+ Once the imaging substance is depleted, as determined at step S<confidence value="5">1</confidence>
403
+ 08, the customer will be informed at step <confidence value="55">S1</confidence>
404
+ 18 to replace the current supply item with a new supply item. </p>
405
+ <p id="p-57" num="57">Optionally, if the manufacturer decides to license the entire contents of supply item <part-num-ref name="entire contents of supply item">32</part-num-ref>
406
+ in the first license, then the customer may be directed to purchase a new supply <boundary-data type="line-number">10 </boundary-data>
407
+ item based on the customer's supply item usage rate. For example, a high usage customer may be directed to purchase a high yield cartridge, or a low yield cartridge if they prefer a lower acquisition cost, whereas a low usage customer will be directed to purchase a low yield cartridge. </p>
408
+ <p id="p-58" num="58">The security measures of step S<confidence value="5">1</confidence>
409
+ 22 may be dependent upon the object to which <boundary-data type="line-number">15 </boundary-data>
410
+ the license is attached, i.e., imaging apparatus <part-num-ref name="imaging apparatus">12</part-num-ref>
411
+ or supply item <part-num-ref name="or supply item">32.</part-num-ref>
412
+ The first security method described below (see the embodiment of Figs. 3A-3B) is for a system in which the license will remain with imaging apparatus <part-num-ref name="license will remain with imaging apparatus">12.</part-num-ref>
413
+ The second security method described below (see the embodiments of Figs. 4A, 4B and <part-num-ref name="embodiments of Figs. 4A, 4B and">5)</part-num-ref>
414
+ is for a system in which the electronic license is sold with supply item <part-num-ref name="electronic license is sold with supply item">32.</part-num-ref>
415
+ </p>
416
+ <p id="p-59" num="59">
417
+ <boundary-data type="line-number">20 </boundary-data>
418
+ Referring to Figs. 1 and 3A, 3B, imaging apparatus <part-num-ref name="and 3A, 3B, imaging apparatus">12</part-num-ref>
419
+ may be sold with supply item <part-num-ref name="may be sold with supply item">32</part-num-ref>
420
+ filled with imaging substance. The security of the first method may utilize a Public/Private Key security. Controller <part-num-ref name="Public/Private Key security. Controller">34</part-num-ref>
421
+ of imaging apparatus <part-num-ref name="of imaging apparatus">12</part-num-ref>
422
+ will contain the Public Key of license vendor <part-num-ref name="Public Key of license vendor">16,</part-num-ref>
423
+ along with a unique serial number that identifies imaging apparatus <part-num-ref name="unique serial number that identifies imaging apparatus">12.</part-num-ref>
424
+ License vendor <part-num-ref name="unique serial number that identifies imaging apparatus 12. License vendor">16,</part-num-ref>
425
+ e.g., a server, will contain the corresponding <boundary-data type="line-number">25 </boundary-data>
426
+ Private Key. </p>
427
+ <p id="p-60" num="60">At step <confidence value="5">S</confidence>
428
+ 200, imaging apparatus 12 contacts license vendor <part-num-ref name="contacts license vendor">16.</part-num-ref>
429
+ At step <confidence value="4">S</confidence>
430
+ 202, imaging apparatus <part-num-ref name="contacts license vendor 16. At step S202, imaging apparatus">12</part-num-ref>
431
+ sends the details of the license offer to license vendor <part-num-ref name="license offer to license vendor">12.</part-num-ref>
432
+ At step <confidence value="5">S</confidence>
433
+ 204, imaging apparatus <part-num-ref name="license offer to license vendor 12. At step S204, imaging apparatus">12</part-num-ref>
434
+ sends a unique serial number of imaging apparatus <part-num-ref name="unique serial number of imaging apparatus">12</part-num-ref>
435
+ to license vendor <part-num-ref name="to license vendor">16</part-num-ref>
436
+ so that imaging apparatus <part-num-ref name="so that imaging apparatus">12</part-num-ref>
437
+ can be identified by license vendor <part-num-ref name="can be identified by license vendor">16.</part-num-ref>
438
+ </p>
439
+ <p id="p-61" num="61">
440
+ <boundary-data type="line-number">30 </boundary-data>
441
+ At step S206, the customer conducts an e-commerce transaction to pay for the new license, e.g., via a credit card. </p>
442
+ <p id="p-62" num="62">At step <confidence value="5">S</confidence>
443
+ 208, it is determined whether the e-commerce transaction was successful. If the determination at step <confidence value="4">S</confidence>
444
+ 208 is NO, then step <confidence value="4">S</confidence>
445
+ 206 is repeated. </p>
446
+ <boundary-data type="header">
447
+ <confidence value="88">10</confidence>
448
+ </boundary-data>
449
+ <boundary-data type="header">Attorney Docket No.:2003-0786.02</boundary-data>
450
+ <p id="p-63" num="63">
451
+ <page-break num="11"/>
452
+ If the determination at step <part-num-ref name="determination at step">
453
+ <confidence value="4">5</confidence>
454
+ 208 </part-num-ref>
455
+ is YES, then at step <part-num-ref name="is YES, then at step">
456
+ <confidence value="4">5</confidence>
457
+ 210 </part-num-ref>
458
+ license vendor <part-num-ref name="license vendor">16</part-num-ref>
459
+ signs the offer details and serial number with the Private Key of license vendor <part-num-ref name="Private Key of license vendor">16.</part-num-ref>
460
+ </p>
461
+ <p id="p-64" num="64">At step S212, license vendor 16 sends an electronic license specific to the unique serial number that is digitally signed by the Private Key of license vendor <part-num-ref name="Private Key of license vendor">16.</part-num-ref>
462
+ </p>
463
+ <p id="p-65" num="65">
464
+ <boundary-data type="line-number">5 </boundary-data>
465
+ At step <confidence value="5">S</confidence>
466
+ 214, controller 34 of imaging apparatus <part-num-ref name="of imaging apparatus">12</part-num-ref>
467
+ receives this license, and controller <part-num-ref name="receives this license, and controller">34</part-num-ref>
468
+ verifies the authenticity of the license by using the Public Key of license vendor <part-num-ref name="Public Key of license vendor">16</part-num-ref>
469
+ to verify the digital signature. </p>
470
+ <p id="p-66" num="66">At step <confidence value="4">5</confidence>
471
+ 216, controller 34 of imaging apparatus <part-num-ref name="of imaging apparatus">12</part-num-ref>
472
+ determines whether the signature verifies. If the determination is YES, i.e., that electronic license is verified, <boundary-data type="line-number">10 </boundary-data>
473
+ then imaging apparatus <part-num-ref name="that electronic license is verified, then imaging apparatus">12</part-num-ref>
474
+ will allow the customer to begin using the new license, and the process continues at step S <part-num-ref name="process continues at step S">
475
+ <confidence value="6">1</confidence>
476
+ 24 </part-num-ref>
477
+ of Fig. 2B. </p>
478
+ <p id="p-67" num="67">If the determination at step <confidence value="5">S</confidence>
479
+ 216 is NO, then at step <confidence value="588">S21</confidence>
480
+ 8 license vendor <part-num-ref name="determination at step S216 is NO, then at step S218 license vendor">16</part-num-ref>
481
+ is requested to resend the license, and the process continues at step <confidence value="5">S</confidence>
482
+ 210. </p>
483
+ <p id="p-68" num="68">Figs. 4A, 4B, and Fig. 5, are flowcharts depicting two embodiments, <boundary-data type="line-number">15 </boundary-data>
484
+ respectively, of the above-referenced second security method, wherein supply item <part-num-ref name="above-referenced second security method, wherein supply item">32</part-num-ref>
485
+ will contain the license. This will allow supply item <part-num-ref name="license. This will allow supply item">32</part-num-ref>
486
+ to be moved to a different imaging apparatus while utilizing the same license. In addition, multiple numbers of licenses can be contained in a single supply item. The license can be replenished by imaging apparatus <part-num-ref name="license can be replenished by imaging apparatus">12</part-num-ref>
487
+ or by another device that has the capability of communicating <boundary-data type="line-number">20 </boundary-data>
488
+ with supply item <part-num-ref name="capability of communicating with supply item">32,</part-num-ref>
489
+ e.g., a kiosk in a retail store. </p>
490
+ <p id="p-69" num="69">This method is implemented by storing a set of message authentication codes (MAC<confidence value="5">s</confidence>
491
+ ), in the electronic electronics module <part-num-ref name="electronic electronics module">46</part-num-ref>
492
+ of the supply item <part-num-ref name="supply item">32</part-num-ref>
493
+ during the manufacturing of supply item <part-num-ref name="manufacturing of supply item">32.</part-num-ref>
494
+ The MACs may be derived, for example, from the unique serial number of the supply item <part-num-ref name="supply item">32</part-num-ref>
495
+ by utilizing the FIPS standard HMAC <boundary-data type="line-number">25 </boundary-data>
496
+ (keyed-hashing for message authentication) algorithm. Each MAC stored in electronics module <part-num-ref name="FIPS standard HMAC (keyed-hashing for message authentication) algorithm. Each MAC stored in electronics module">46</part-num-ref>
497
+ will represent a license that may be used by supply item <part-num-ref name="license that may be used by supply item">32.</part-num-ref>
498
+ In order to utilize the license, the correct MAC code corresponding to the license level is written to electronics module <part-num-ref name="license level is written to electronics module">46</part-num-ref>
499
+ of supply item <part-num-ref name="of supply item">32.</part-num-ref>
500
+ When the MAC is written by imaging apparatus <part-num-ref name="MAC is written by imaging apparatus">12,</part-num-ref>
501
+ or by another device (such as a device at a kiosk), the ASIC in electronics <boundary-data type="line-number">30 </boundary-data>
502
+ module <part-num-ref name="ASIC in electronics module">46</part-num-ref>
503
+ of supply item <part-num-ref name="of supply item">32</part-num-ref>
504
+ will compare the MAC written to the MAC stored during manufacturing, and if they are equal then supply item <part-num-ref name="MAC stored during manufacturing, and if they are equal then supply item">32</part-num-ref>
505
+ will allow the next license to be used. </p>
506
+ <boundary-data type="header">
507
+ <confidence value="88">11</confidence>
508
+ </boundary-data>
509
+ <boundary-data type="header">Attorney Docket No.:2003-0786.02</boundary-data>
510
+ <p id="p-70" num="70">
511
+ <page-break num="12"/>
512
+ This method, wherein supply item is installed in imaging apparatus 12, will now be described with respect to the flowchart of Figs. 4A and 4B. </p>
513
+ <p id="p-71" num="71">At step <confidence value="4">5</confidence>
514
+ 300, imaging apparatus 12 contacts license vendor <part-num-ref name="contacts license vendor">16.</part-num-ref>
515
+ </p>
516
+ <p id="p-72" num="72">At step <confidence value="4">5</confidence>
517
+ 302, imaging apparatus 12 reads the serial number and license level <boundary-data type="line-number">5 </boundary-data>
518
+ (e.g., first license, second license, etc.) from electronics module <part-num-ref name="first license, second license, etc.) from electronics module">46</part-num-ref>
519
+ of supply item <part-num-ref name="of supply item">32.</part-num-ref>
520
+ </p>
521
+ <p id="p-73" num="73">At step <confidence value="4">S</confidence>
522
+ 304, imaging apparatus 12 sends the details of the license offer, the serial number of supply item <part-num-ref name="serial number of supply item">32</part-num-ref>
523
+ and the license level to license vendor <part-num-ref name="license level to license vendor">16.</part-num-ref>
524
+ </p>
525
+ <p id="p-74" num="74">At step <confidence value="4">S</confidence>
526
+ 306, the customer conducts an e-commerce transaction to pay for the new license, e.g., via a credit card. </p>
527
+ <p id="p-75" num="75">
528
+ <boundary-data type="line-number">10 </boundary-data>
529
+ At step <confidence value="5">S</confidence>
530
+ 308, it is determined whether the e-commerce transaction was successful. If the determination at step <confidence value="4">S</confidence>
531
+ 308 is NO, then step <part-num-ref name="determination at step S308 is NO, then step">
532
+ <confidence value="4">5</confidence>
533
+ 306 </part-num-ref>
534
+ is repeated. </p>
535
+ <p id="p-76" num="76">If the determination at step <confidence value="5">S</confidence>
536
+ 308 is YES, then at step <part-num-ref name="determination at step S308 is YES, then at step">
537
+ <confidence value="4">5</confidence>
538
+ 310 </part-num-ref>
539
+ license vendor <part-num-ref name="license vendor">16</part-num-ref>
540
+ calculates a MAC value based on the serial number of supply item <part-num-ref name="serial number of supply item">32</part-num-ref>
541
+ and the license level. </p>
542
+ <p id="p-77" num="77">
543
+ <boundary-data type="line-number">15 </boundary-data>
544
+ At step <confidence value="5">S</confidence>
545
+ 312, license vendor 16 sends an electronic license MAC to imaging apparatus <part-num-ref name="electronic license MAC to imaging apparatus">12.</part-num-ref>
546
+ </p>
547
+ <p id="p-78" num="78">At step <confidence value="5">S</confidence>
548
+ 314, controller 34 of imaging apparatus <part-num-ref name="of imaging apparatus">12</part-num-ref>
549
+ writes the license MAC to electronics module <part-num-ref name="license MAC to electronics module">46</part-num-ref>
550
+ of supply item <part-num-ref name="of supply item">32.</part-num-ref>
551
+ </p>
552
+ <p id="p-79" num="79">At step <confidence value="4">5</confidence>
553
+ 316, electronics module 46 of supply item <part-num-ref name="of supply item">32</part-num-ref>
554
+ verifies the license MAC. </p>
555
+ <p id="p-80" num="80">
556
+ <boundary-data type="line-number">20 </boundary-data>
557
+ At step <confidence value="68">S3</confidence>
558
+ 18, electronics module 46 of supply item <part-num-ref name="of supply item">32</part-num-ref>
559
+ determines whether the MAC verifies. If the determination is YES, i.e., that electronic license is verified, then imaging apparatus <part-num-ref name="that electronic license is verified, then imaging apparatus">12</part-num-ref>
560
+ will allow the customer to begin using the new license, and the process continues at step S<confidence value="5">1</confidence>
561
+ 24 of Fig. 2B. </p>
562
+ <p id="p-81" num="81">If the determination at step S318 is NO, then at step <confidence value="5">S</confidence>
563
+ 320 license vendor <part-num-ref name="determination at step S318 is NO, then at step S320 license vendor">16</part-num-ref>
564
+ is <boundary-data type="line-number">25 </boundary-data>
565
+ requested to resend the license MAC, and the process continues at step <part-num-ref name="process continues at step">
566
+ <confidence value="4">5</confidence>
567
+ 310. </part-num-ref>
568
+ </p>
569
+ <p id="p-82" num="82">A method wherein supply item 32 is installed in device at a kiosk will now be described with respect to the flowchart of Fig. 5. For replenishment by a kiosk system, the customer will take supply item <part-num-ref name="customer will take supply item">32</part-num-ref>
570
+ that can be licensed to a kiosk, such as those found in a retail store. If there is enough imaging substance remaining in supply item <part-num-ref name="retail store. If there is enough imaging substance remaining in supply item">32</part-num-ref>
571
+ <boundary-data type="line-number">30 </boundary-data>
572
+ for another license, then the kiosk will make the customer an offering, in the manner previous described, based on the usage rate of the previous license. If the customer decides on purchasing a new license, the kiosk operator will place supply item <part-num-ref name="kiosk operator will place supply item">32</part-num-ref>
573
+ in an <boundary-data type="header">
574
+ <confidence value="88">12</confidence>
575
+ </boundary-data>
576
+ <page-break num="13"/>
577
+ <boundary-data type="header">Attorney Docket No.:2003-0786.02</boundary-data>
578
+ electronic device that has the capability to communicate with electronics module <part-num-ref name="capability to communicate with electronics module">46</part-num-ref>
579
+ of supply item <part-num-ref name="of supply item">32.</part-num-ref>
580
+ </p>
581
+ <p id="p-83" num="83">At step <confidence value="5">S</confidence>
582
+ 400, the kiosk device contacts license vendor <part-num-ref name="kiosk device contacts license vendor">16.</part-num-ref>
583
+ </p>
584
+ <p id="p-84" num="84">At step <confidence value="5">S</confidence>
585
+ 402, the kiosk device reads the serial number and license level (e.g., <boundary-data type="line-number">5 </boundary-data>
586
+ first license, second license, etc.) from electronics module <part-num-ref name="first license, second license, etc.) from electronics module">46</part-num-ref>
587
+ of supply item <part-num-ref name="of supply item">32.</part-num-ref>
588
+ </p>
589
+ <p id="p-85" num="85">At step <confidence value="5">S</confidence>
590
+ 404, the kiosk device sends the details of the license offer, the serial number of supply item <part-num-ref name="serial number of supply item">32</part-num-ref>
591
+ and the license level to license vendor <part-num-ref name="license level to license vendor">16.</part-num-ref>
592
+ </p>
593
+ <p id="p-86" num="86">At step <confidence value="5">S</confidence>
594
+ 406 license vendor 16 calculates a MAC value based on the serial number of supply item <part-num-ref name="serial number of supply item">32</part-num-ref>
595
+ and the license level. </p>
596
+ <p id="p-87" num="87">
597
+ <boundary-data type="line-number">10 </boundary-data>
598
+ At step S408, license vendor 16 sends an electronic license MAC to the kiosk device. </p>
599
+ <p id="p-88" num="88">At step <confidence value="4">S</confidence>
600
+ 410, the kiosk device writes the license MAC to electronics module <part-num-ref name="license MAC to electronics module">46</part-num-ref>
601
+ of supply item <part-num-ref name="of supply item">32.</part-num-ref>
602
+ </p>
603
+ <p id="p-89" num="89">At step <confidence value="4">5</confidence>
604
+ 412, electronics module 46 of supply item <part-num-ref name="of supply item">32</part-num-ref>
605
+ verifies the license MAC. </p>
606
+ <p id="p-90" num="90">
607
+ <boundary-data type="line-number">15 </boundary-data>
608
+ At step <confidence value="4">5</confidence>
609
+ 414, electronics module 46 of supply item <part-num-ref name="of supply item">32</part-num-ref>
610
+ determines whether the MAC verifies. If the determination is YES, i.e., that electronic license is verified, then electronics module <part-num-ref name="that electronic license is verified, then electronics module">46</part-num-ref>
611
+ of supply item <part-num-ref name="of supply item">32</part-num-ref>
612
+ will allow the customer to begin using the new license, and the process continues at step <confidence value="5">S</confidence>
613
+ 124 of Fig. 2B. </p>
614
+ <p id="p-91" num="91">If the determination at step <part-num-ref name="determination at step">
615
+ <confidence value="4">5</confidence>
616
+ 414 </part-num-ref>
617
+ is NO, then at step <part-num-ref name="is NO, then at step">
618
+ <confidence value="4">5</confidence>
619
+ 416 </part-num-ref>
620
+ license vendor <part-num-ref name="license vendor">16</part-num-ref>
621
+ is <boundary-data type="line-number">20 </boundary-data>
622
+ requested to resend the license MAC, and the process continues at step S406. </p>
623
+ <p id="p-92" num="92">Thus, with the security methods described above, a new license can be established by imaging apparatus <part-num-ref name="new license can be established by imaging apparatus">12,</part-num-ref>
624
+ or by a kiosk device. From the customer's perspective, however, the license replenishment will appear the same as the method discussed previously with respect to Figs.3A, 3B utilizing Public/Private Key security. </p>
625
+ <p id="p-93" num="93">
626
+ <boundary-data type="line-number">25 </boundary-data>
627
+ While this invention has been described with respect to embodiments of the invention, the present invention may be further modified within the spirit and scope of this disclosure. This application is therefore intended to cover any variations, uses, or adaptations of the invention using its general principles. Further, this application is intended to cover such departures from the present disclosure as come within known or <boundary-data type="line-number">30 </boundary-data>
628
+ customary practice in the art to which this invention pertains and which fall within the limits of the appended claims. </p>
629
+ <boundary-data type="header">
630
+ <confidence value="88">13</confidence>
631
+ </boundary-data>
632
+ </description>
633
+ </us-patent-application>
634
+
prior_art/11066622.xml ADDED
@@ -0,0 +1,350 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11066622</doc-number>
8
+ <date>2005-02-25</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <heading id="h-1">
14
+ <confidence value="11">'I</confidence>
15
+ <confidence value="1">,</confidence>
16
+ </heading>
17
+ <p id="p-1" num="1">GTPP Docket No.: ENT<confidence value="558">002</confidence>
18
+ </p>
19
+ <heading id="h-2">DYNAMIC NETWORK DETECTION SYSTEM AND METHOD</heading>
20
+ <heading id="h-3">RELATED APPLICATIONS</heading>
21
+ <p id="p-2" num="2">[0001] This application claims the priority of the following application, which is herein incorporated by reference: U.S. Provisional Application Serial No.: 60/552,000 entitled, "Dynamically Created Distributed Monitors in Network Systems", filed <part-num-ref name="following application, which is herein incorporated by reference: U.S. Provisional Application Serial No.: 60/552,000 entitled, &quot;Dynamically Created Distributed Monitors in Network Systems&quot;, filed">10</part-num-ref>
22
+ March <part-num-ref name="March">2004.</part-num-ref>
23
+ </p>
24
+ <p id="p-3" num="3">[0002] This application herein incorporates by reference the following applications:</p>
25
+ <p id="p-4" num="4">"Distributed Intrusion Response System", US Patent Application No. 10/713,560 filed November 14, 2003 (attached hereto as Exhibit A) and US Publication No.</p>
26
+ <p id="p-5" num="5">
27
+ <confidence value="86">US</confidence>
28
+ 20050027837A1, filed July 29, 2003, entitled "System and Method for Dynamic Network Policy Management" (attached hereto as Exhibit B). Both applications are assigned to common assignee Enterasys Networks, Inc. </p>
29
+ <heading id="h-4">FIELD OF THE DISCLOSURE</heading>
30
+ <p id="p-6" num="6">[0003] This disclosure relates to network detection and monitoring systems and methods and, more particularly, to dynamic network detection systems and methods.</p>
31
+ <heading id="h-5">
32
+ <confidence value="88">BA</confidence>
33
+ CKGROUND </heading>
34
+ <p id="p-7" num="7">[0004] Networks, which may be hardwired or wireless, allow for the interconnection of various computing devices (e.g., desktop/laptop computer and servers, for example) and communication devices (e.g., telephones, radios and wireless access points (WAP), for example) and the sharing of data among these devices. Additionally, networks allow multiple devices, and therefore multiple users, to share centralized resources (e.g., network infrastructure, applications, databases, servers, printers, data storage devices, data backup devices, and internet gateways, for example).</p>
35
+ <boundary-data type="header">GTPP Docket No.: ENT<confidence value="558">002</confidence>
36
+ </boundary-data>
37
+ <p id="p-8" num="8">
38
+ <page-break num="2"/>
39
+ [0005] Unfortunately, as the access to a network increases, the likelihood of a network attack (i.e., by a hacker or a computer virus, for example) also increases. These attacks may be initiated via various means, such as a surreptitious email attachment, or infected data files copied onto a network drive. </p>
40
+ <p id="p-9" num="9">[0006] Once initiated, a network attack may result in network harm e.g., data corruption / loss / theft, network access denial, excess / complete network bandwidth consumption, network attack propagation <confidence value="5">/</confidence>
41
+ dissemination, and/or unwarranted or unauthorized use. Currently, there are several generally-available forms of network protection, including firewalls, Intrusion Detection Systems (IDS), Intrusion Prevention Systems (IPS), and dynamic response policy driven systems as referenced earlier. </p>
42
+ <p id="p-10" num="10">[0007] Firewalls, which are often positioned between a private network (e.g., a corporate computer network) and a public network (e.g., the internet), typically prevent the passage of suspect data packets based on the occurrence of a limited number of specific conditions. Unfortunately, the rigidity of firewalls often limits their usefulness.</p>
43
+ <p id="p-11" num="11">[0008] Unlike firewalls, which merely prevent the passage of suspect data packets, IDS are designed to initially allow data packet access to the network, such that the usage pattern of the data packets is observed. In the event of potentially harmful behavior by data packet(s), the network administrator is notified. At this point, the network administrator may analyze the situation and take the necessary enforcement action. Unfortunately, as network attacks spread rapidly throughout a network, any delay in taking an enforcement action may increase the severity of the attack. Furthermore, as the network administrator typically defines and implements the enforcement action to be taken, the level of response may not always be applicable with the level of attack. Unfortunately, while some IDS are capable of providing an automated response, these responses are typically minimal and static in nature, often resulting in false alarms, unneeded network shutdowns / slowdowns, and mismatches between levels of attack and levels of response.</p>
44
+ <boundary-data type="header">
45
+ <confidence value="8">2</confidence>
46
+ </boundary-data>
47
+ <boundary-data type="header">GTPP Docket No.: ENT<confidence value="558">002</confidence>
48
+ </boundary-data>
49
+ <p id="p-12" num="12">
50
+ <page-break num="3"/>
51
+ [0009] Most IPS devices (e.g., firewalls) have a very limited scope of network influence, as they can only block traffic fitting specific criteria that flows through them. </p>
52
+ <p id="p-13" num="13">Event driven dynamic policy systems attempt to detect interesting and potentially harmful network events using all the input gathering techniques from the above-described methods along with other data collection mechanisms (e.g., RMON, CMON, SMON, for example) to determine a threat severity and, if so configured, take an appropriate response.</p>
53
+ <p id="p-14" num="14">[0010] Typically, responses are driven by a dynamic distributed policy management approach capable of changing network policy based upon harmful (or potentially harmful) activity. All the approaches typically have some shortcomings demonstrated by the growing frequency of successful attacks. Routinely, the detection methods may indicate anomalous or harmful activity but lack the sophistication to isolate the attack such that the remedy is not as bad as (or worse than) the ongoing attack. Often, additional data is required to verify the extent or specifics of the attack, such as e.g., the origin port, the IP address, the MAC address, the attack location, the protocol, and whether the problem is ongoing or transient. Human intervention is often needed when: complex verification is required to distinguish between attacks and expected network behavior; and/or before implementing a network change that largely impacts network users and applications.</p>
54
+ <heading id="h-6">SUMMARY OF THE INVENTION</heading>
55
+ <p id="p-15" num="15">[0011] According to an aspect of this invention, a method of dynamically launching a monitor includes monitoring network operations, occurring within a device network, to determine the occurrence of one or more trigger events. One or more event-specific monitor processes are deployed in response to the occurrence of the one or more trigger events.</p>
56
+ <p id="p-16" num="16">[0012] One or more of the following features may also be included. Dynamically deploying one or more event-specific monitor processes may include comparing the one or more trigger events to a monitor rule set. The monitor rule set may define the one or more <boundary-data type="header">
57
+ <confidence value="8">3</confidence>
58
+ </boundary-data>
59
+ <page-break num="4"/>
60
+ <boundary-data type="header">GTPP Docket No.: ENT<confidence value="558">002</confidence>
61
+ </boundary-data>
62
+ event-specific monitor processes to be deployed in response to the occurrence of the one or more trigger events. The one or more trigger events may be chosen from the group consisting of<confidence value="5">:</confidence>
63
+ an excessive bandwidth usage, a network fault, a suspect address, a tripwire event, a port scan, a virus detection, an IDS event, a firewall event, an excessive flow rate setup, an unexpected protocol usage, an illegal operation, an authentication and login failure, a link change, and a status change. </p>
64
+ <p id="p-17" num="17">[0013] The network may include a plurality of network devices and dynamically deploying one or more event-specific monitor processes may include dynamically deploying one or more event specific monitors processes on at least two of the plurality of network devices. One or more of the plurality of network devices may be chosen from the group consisting of: a switch device, a routing device, a bridge, a gateway, an access point, an IDS, an IPS, a firewall, a repeater, a signal forwarding device, a packet forwarding device, a server, an attached function, and an end system.</p>
65
+ <p id="p-18" num="18">[0014] At least one of the event specific monitor processes may determine the occurrence of one or more suspect network conditions. One or more enforcement processes may be deployed in response to the occurrence of the one or more suspect network conditions. Dynamically deploying one or more enforcement processes may include comparing the one or more suspect network conditions to an enforcement rule set.</p>
66
+ <p id="p-19" num="19">The enforcement rule set may define the one or more enforcement processes to be deployed in response to the occurrence of the one or more suspect network conditions.</p>
67
+ <p id="p-20" num="20">One or more of the enforcement processes may be chosen from the group consisting of:</p>
68
+ <p id="p-21" num="21">temporarily disabling user access; permanently disabling user access; disconnecting a network user; suspending a network user, requiring that a network user reauthenticate;</p>
69
+ <p id="p-22" num="22">limiting the bandwidth of a network device; limiting the bandwidth of an application;</p>
70
+ <p id="p-23" num="23">quarantining a network user; filtering network traffic; redirecting network traffic; logging network traffic; mirroring port traffic; making network topology changes; sending network alerts; initiating network traps; and terminating network device sessions.</p>
71
+ <boundary-data type="header">
72
+ <confidence value="8">4</confidence>
73
+ </boundary-data>
74
+ <boundary-data type="header">GTPP Docket No.: ENT<confidence value="558">002</confidence>
75
+ </boundary-data>
76
+ <p id="p-24" num="24">
77
+ <page-break num="5"/>
78
+ <confidence value="5">[</confidence>
79
+ 0015] Dynamically deploying one or more event-specific monitor processes may include dynamically deploying at least two serial monitor processes. A first serial monitor process may generate a first set of suspect network conditions, and a second serial monitor process may generate a second set of suspect network conditions chosen from the first set of suspect network conditions. One or more enforcement processes may be deployed in response to the occurrence of the second set of suspect network conditions. </p>
80
+ <p id="p-25" num="25">[0016] Dynamically deploying one or more event-specific monitor processes may include dynamically deploying at least two parallel monitor processes. A first parallel monitor process may generate a first set of suspect network conditions, and a second parallel monitor process may generate a second set of suspect network conditions. A third set of suspect network conditions may be generated that is the intersection of the first and second sets of suspect network conditions. One or more enforcement processes may be deployed in response to the occurrence of the third set of suspect network conditions.</p>
81
+ <p id="p-26" num="26">[0017] Dynamically deploying one or more event-specific monitor processes may include dynamically deploying at least two parallel monitor processes. A first parallel monitor process may generate a first set of suspect network conditions. A second parallel monitor process may generate a second set of suspect network conditions. A third set of suspect network conditions may be generated that is the union of the first and second sets of suspect network conditions. One or more enforcement processes may be deployed in response to the occurrence of the third set of suspect network conditions.</p>
82
+ <p id="p-27" num="27">[0018] The device network may be a distributed computing network and/or a telephony network.</p>
83
+ <p id="p-28" num="28">[0019] According to an aspect of this invention, a method of dynamically launching a monitor includes monitoring network operations, occurring within a device network, to determine the occurrence of one or more trigger events. Network operations on a network device coupled to the device network are locally monitored in response to the occurrence of the one or more trigger events.</p>
84
+ <boundary-data type="header">
85
+ <confidence value="8">5</confidence>
86
+ </boundary-data>
87
+ <boundary-data type="header">GTPP Docket No.: ENT<confidence value="558">002</confidence>
88
+ </boundary-data>
89
+ <p id="p-29" num="29">
90
+ <page-break num="6"/>
91
+ [0020] One or more of the following features may also be included. Locally monitoring network operations may include comparing the one or more trigger events to a monitor rule set. The monitor rule set may define one or more event-specific monitor processes to be deployed in response to the occurrence of the one or more trigger events. </p>
92
+ <p id="p-30" num="30">Locally monitoring network operations may include dynamically deploying the one or more event-specific monitor processes on the network device in response to the occurrence of the one or more trigger events. At least one of the event specific monitor processes may determine the occurrence of one or more suspect network conditions. One or more enforcement processes may be deployed in response to the occurrence of the one or more suspect network conditions.</p>
93
+ <p id="p-31" num="31">[0021] The above-described methods may also be implemented as a sequence of instructions executed by a processor.</p>
94
+ <p id="p-32" num="32">[0022] The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features and advantages will become apparent from the description, the drawings, and the claims.</p>
95
+ <heading id="h-7">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
96
+ <p id="p-33" num="33">FIG<confidence value="5">.</confidence>
97
+ 1 is a block diagram of a system including a dynamic detection system; </p>
98
+ <p id="p-34" num="34">FIG 2 is a block diagram of the dynamic detection system of FIG. 1; and FIG<confidence value="5">.</confidence>
99
+ 3 is a diagrammatic view of the dynamic detection system of FIG<confidence value="5">.</confidence>
100
+ 1. </p>
101
+ <heading id="h-8">DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS</heading>
102
+ <p id="p-35" num="35">[0023] Referring to FIG. 1, there is shown a dynamic detection system <part-num-ref name="dynamic detection system">10</part-num-ref>
103
+ that monitors network traffic (e.g., data packets) on a network <part-num-ref name="network">12</part-num-ref>
104
+ to detect and analyze network events, and may execute one or more enforcement measures in response to the occurrence of a network event. </p>
105
+ <boundary-data type="header">
106
+ <confidence value="8">6</confidence>
107
+ </boundary-data>
108
+ <boundary-data type="header">GTPP Docket No.: ENT<confidence value="558">002</confidence>
109
+ </boundary-data>
110
+ <p id="p-36" num="36">
111
+ <page-break num="7"/>
112
+ [0024] Dynamic detection system 10 typically resides on and is executed by one or more computing devices (e.g., server <part-num-ref name="server">14)</part-num-ref>
113
+ connected to network <part-num-ref name="connected to network">12</part-num-ref>
114
+ (e.g., a local area network, an intranet, the internet, or some other form of network). The instruction sets and subroutines of dynamic detection system <part-num-ref name="instruction sets and subroutines of dynamic detection system">10</part-num-ref>
115
+ are typically stored on a storage device <part-num-ref name="storage device">16</part-num-ref>
116
+ connected to computing device <part-num-ref name="connected to computing device">14.</part-num-ref>
117
+ </p>
118
+ <p id="p-37" num="37">[0025] Storage device 16 may be, for example, a hard disk drive, a tape drive, an optical drive, a RAID array, a random access memory (RAM), or a read-only memory (ROM). A network administrator <part-num-ref name="network administrator">18</part-num-ref>
119
+ typically configures, accesses, and administers dynamic intruder detection system <part-num-ref name="typically configures, accesses, and administers dynamic intruder detection system">10</part-num-ref>
120
+ through a desktop application <part-num-ref name="desktop application">20</part-num-ref>
121
+ (e.g., Microsoft Internet Explorer TM, Netscape Navigator TM, or a specialized user interface) running on a computer <part-num-ref name="computer">22</part-num-ref>
122
+ that is also connected to the network <part-num-ref name="network">12.</part-num-ref>
123
+ </p>
124
+ <p id="p-38" num="38">[0026] Various network devices may be a part of network <part-num-ref name="part of network">12,</part-num-ref>
125
+ such as: switching devices <part-num-ref name="part of network 12, such as: switching devices">24,</part-num-ref>
126
+ <part-num-ref name="part of network 12, such as: switching devices 24,">26</part-num-ref>
127
+ (i.e., a device that examines each data packet to determine, from a physical address such as a MAC address, the intended recipient of the data packet); a routing device <part-num-ref name="routing device">28</part-num-ref>
128
+ (i.e., a device that determines the next network point to which a data packet should be forwarded toward its destination); a gateway <part-num-ref name="gateway">30</part-num-ref>
129
+ (i.e., a device that functions as an entrance to another network, e.g., the internet 32), which often includes a firewall <part-num-ref name="firewall">34</part-num-ref>
130
+ (i.e., a program or set of programs that protects a private network from users of other networks); and a wireless access point (WAP) <part-num-ref name="wireless access point (WAP)">36</part-num-ref>
131
+ (i.e., a device that allows for wireless communication of data between the access point <part-num-ref name="access point">36</part-num-ref>
132
+ and one or more computing devices <part-num-ref name="and one or more computing devices">38,</part-num-ref>
133
+ <part-num-ref name="and one or more computing devices 38,">40,</part-num-ref>
134
+ 42), for example. Additional devices include bridges (not shown), Intrusion Detection Systems (not shown), Intrusion Prevention Systems (not shown), repeaters (not shown), signal forwarding devices (not shown), a packet forwarding devices (not shown), attached functions (not shown), and end systems (not shown). Additionally, non-traditional computing devices, such as IP (i.e., internet protocol) telephones <part-num-ref name="internet protocol) telephones">44</part-num-ref>
135
+ and IP radios <part-num-ref name="and IP radios">46,</part-num-ref>
136
+ may also be connected to network <part-num-ref name="and IP radios 46, may also be connected to network">12.</part-num-ref>
137
+ </p>
138
+ <p id="p-39" num="39">[0027] Typically, each network system (e.g., network <part-num-ref name="network">12)</part-num-ref>
139
+ is considered to have a core <boundary-data type="header">
140
+ <confidence value="8">7</confidence>
141
+ </boundary-data>
142
+ <page-break num="8"/>
143
+ <boundary-data type="header">GTPP Docket No.: ENT<confidence value="558">002</confidence>
144
+ </boundary-data>
145
+ <part-num-ref name="core">48,</part-num-ref>
146
+ having a greater level of physical security and higher bandwidth interconnecting other network elements. </p>
147
+ <p id="p-40" num="40">[0028] Each network device 24, 26, 28, 30, 36 is typically capable of bidirectional communication with dynamic detection system <part-num-ref name="is typically capable of bidirectional communication with dynamic detection system">10.</part-num-ref>
148
+ Further, each network device is typically capable of executing one or more event specific monitor processes, which are controlled by and provide data to dynamic detection system <part-num-ref name="is typically capable of bidirectional communication with dynamic detection system 10. Further, each network device is typically capable of executing one or more event specific monitor processes, which are controlled by and provide data to dynamic detection system">10</part-num-ref>
149
+ (as will be discussed below in greater detail). </p>
150
+ <p id="p-41" num="41">[0029] Since there are numerous methods / algorithms that are used to analyze network traffic for the signs of inappropriate actions, malicious use or other harm of network resources, it is essentially impracticable to employ all of these methods and/or algorithms on a single network device, such as switching devices <part-num-ref name="single network device, such as switching devices">24,</part-num-ref>
151
+ <part-num-ref name="single network device, such as switching devices 24,">26,</part-num-ref>
152
+ router <part-num-ref name="single network device, such as switching devices 24, 26, router">28,</part-num-ref>
153
+ gateway <part-num-ref name="single network device, such as switching devices 24, 26, router 28, gateway">30,</part-num-ref>
154
+ or access point <part-num-ref name="single network device, such as switching devices 24, 26, router 28, gateway 30, or access point">36.</part-num-ref>
155
+ </p>
156
+ <p id="p-42" num="42">[0030] Referring also to FIG. 2, dynamic detection system 10 monitors <part-num-ref name="monitors">100</part-num-ref>
157
+ the network operations (e.g., traffic patterns, sender / recipient addresses, attachment names, and packet contents, for example) using basic packet, signal and flow detection methods to determine the occurrence of one or more trigger events (e.g., an excessive bandwidth usage, network faults, a suspect address, a tripwire event, port scanning, virus detection, IDS event, firewall event, excessive flow rate setups, unexpected protocol usage, illegal operations, authentication and login failures, link changes, status changes human initiated or manual operations and many other events including legitimate and expected operations which might be a precursor to an attack. A trigger event is an event that is indicative of a suspicious network event, e.g., a network intrusion (e.g., the presence of a network hacker), a virus propagation (e.g., the propagation of the MS Blaster WORM virus), the occurrence of a prohibited network activity (e.g., the downloading of MP3 files), or a high port-usage event, for example. </p>
158
+ <p id="p-43" num="43">[0031] Assume for illustrative purposes that dynamic detection system 10 is configured to monitor network <part-num-ref name="is configured to monitor network">12</part-num-ref>
159
+ to detect intrusion / virus events. As stated above, <boundary-data type="header">
160
+ <confidence value="8">8</confidence>
161
+ </boundary-data>
162
+ <page-break num="9"/>
163
+ <boundary-data type="header">GTPP Docket No.: ENT<confidence value="558">002</confidence>
164
+ </boundary-data>
165
+ dynamic detection system <part-num-ref name="to detect intrusion / virus events. As stated above, dynamic detection system">10</part-num-ref>
166
+ typically uses basic flow detection methods / algorithms to monitor network operations to detect the occurrence of one or more trigger events. </p>
167
+ <p id="p-44" num="44">Unfortunately, while the basic flow detection methods / algorithms are efficient at detecting high-level trigger events, quite often these trigger events are false alarms.</p>
168
+ <p id="p-45" num="45">[0032] Accordingly, in the event that dynamic detection system <part-num-ref name="event that dynamic detection system">10</part-num-ref>
169
+ detects <part-num-ref name="detects">102</part-num-ref>
170
+ a trigger event (which may or may not be indicative of an intrusion / virus event), dynamic detection system <part-num-ref name="intrusion / virus event), dynamic detection system">10</part-num-ref>
171
+ deploys <part-num-ref name="deploys">104</part-num-ref>
172
+ one or more event-specific monitor processes that determine whether the trigger event is indicative of a suspect network operation (which in this example is an intrusion / virus event) or merely a false alarm. </p>
173
+ <p id="p-46" num="46">[0033] The quantity and type of event-specific monitor processes deployed varies in accordance with the type of trigger event(s) detected by dynamic detection system <part-num-ref name="type of trigger event(s) detected by dynamic detection system">10.</part-num-ref>
174
+ </p>
175
+ <p id="p-47" num="47">Continuing with the above-stated example, assume that the trigger event detected is a sudden increase in the level of MS SQL traffic within network <part-num-ref name="level of MS SQL traffic within network">12.</part-num-ref>
176
+ Dynamic detection system <part-num-ref name="level of MS SQL traffic within network 12. Dynamic detection system">10</part-num-ref>
177
+ compares <part-num-ref name="compares">106</part-num-ref>
178
+ this detected trigger event to a monitor rule set to determine which (if any) intrusion / virus event(s) may be occurring. In this example, the monitor rule set would correlate detected trigger events to possible intrusion / virus events. Since a sudden increase in MS SQL traffic may be indicative of the propagation of the MS Blaster WORM virus on network <part-num-ref name="MS Blaster WORM virus on network">12,</part-num-ref>
179
+ trigger event comparison <part-num-ref name="MS Blaster WORM virus on network 12, trigger event comparison">106</part-num-ref>
180
+ would result in the deployment <part-num-ref name="deployment">104</part-num-ref>
181
+ of event-specific monitor processes designed to verify the existence of the MS Blaster WORM virus on network <part-num-ref name="MS Blaster WORM virus on network">12,</part-num-ref>
182
+ as opposed to the occurrence of a false alarm due to e.g., a network user performing a high-level of SQL database <confidence value="2222222222">read/write</confidence>
183
+ operations. </p>
184
+ <p id="p-48" num="48">[0034] An example of such an event-specific monitor process is a pattern matching process that analyzes individual data packets to see if the data within the data packet matches a defined and known pattern for the MS Blaster WORM virus. While a pattern matching process is computationally intensive, since the data packets are being examined for the existence of a single known pattern (as opposed to a known pattern for each of the thousands of known viruses), computational loading is manageable.</p>
185
+ <boundary-data type="header">
186
+ <confidence value="8">9</confidence>
187
+ </boundary-data>
188
+ <boundary-data type="header">GTPP Docket No.: ENT<confidence value="558">002</confidence>
189
+ </boundary-data>
190
+ <p id="p-49" num="49">
191
+ <page-break num="10"/>
192
+ [0035] When dynamically deploying event-specific monitor processes, dynamic detection system 10 may transmit the event specific monitor processes to other network devices (e.g., switching device <part-num-ref name="switching device">24)</part-num-ref>
193
+ for remote execution, and/or may execute the event-specific monitor process locally (i.e., on server 14). Continuing with the above-stated example, when dynamic detection system <part-num-ref name="above-stated example, when dynamic detection system">10</part-num-ref>
194
+ deploys the event-specific monitor process (i.e., the pattern matching process), the process is typically deployed to and executed on all network devices (i.e., in this example, switching devices <part-num-ref name="in this example, switching devices">24,</part-num-ref>
195
+ <part-num-ref name="in this example, switching devices 24,">26,</part-num-ref>
196
+ router <part-num-ref name="in this example, switching devices 24, 26, router">28,</part-num-ref>
197
+ gateway <part-num-ref name="in this example, switching devices 24, 26, router 28, gateway">30,</part-num-ref>
198
+ and access point 36). However, the number of network devices executing the event-specific monitor process may be reduced to target only highly-vulnerable devices. </p>
199
+ <p id="p-50" num="50">And, as stated above, the device (e.g., server <part-num-ref name="server">14)</part-num-ref>
200
+ executing dynamic detection system <part-num-ref name="executing dynamic detection system">10,</part-num-ref>
201
+ as well as any other attached computing device (e.g., computing devices <part-num-ref name="computing devices">22,</part-num-ref>
202
+ <part-num-ref name="computing devices 22,">38,</part-num-ref>
203
+ <part-num-ref name="computing devices 22, 38,">40,</part-num-ref>
204
+ <part-num-ref name="computing devices 22, 38, 40,">42,</part-num-ref>
205
+ 44), may also execute the event specific monitor processes. </p>
206
+ <p id="p-51" num="51">[0036] Once deployed and executed, the event-specific monitor processes perform their designated functions to determine <part-num-ref name="event-specific monitor processes perform their designated functions to determine">108</part-num-ref>
207
+ whether or not a suspect network condition is present and provide feedback to dynamic detection system <part-num-ref name="suspect network condition is present and provide feedback to dynamic detection system">10.</part-num-ref>
208
+ Continuing with the above-stated example, the event-specific monitor process performs a pattern matching function to determine <part-num-ref name="pattern matching function to determine">108</part-num-ref>
209
+ whether the suspect network condition (i.e., in this example, MS Blaster virus) is present within network <part-num-ref name="in this example, MS Blaster virus) is present within network">12.</part-num-ref>
210
+ In the event that one or more of the event specific monitor processes concludes that the MS Blaster WORM virus is present within the network, data is provided to dynamic detection system <part-num-ref name="network, data is provided to dynamic detection system">10</part-num-ref>
211
+ confirming the presence of the virus. </p>
212
+ <p id="p-52" num="52">[0037] In response to receiving such confirmation, dynamic detection system 10 may deploy <part-num-ref name="may deploy">110</part-num-ref>
213
+ additional event-specific monitoring processes to further confirm and reinforce the existence of, in this example, the MS Blaster WORM virus. The value in dynamically deploying additional event-specific monitor processes is that successive confirmations can create a higher likelihood of accuracy and extent. </p>
214
+ <p id="p-53" num="53">[0038] Once the existence of, in this example, the MS Blaster WORM virus is <boundary-data type="header">
215
+ <confidence value="88">10</confidence>
216
+ </boundary-data>
217
+ <page-break num="11"/>
218
+ <boundary-data type="header">GTPP Docket No.: ENT<confidence value="558">002</confidence>
219
+ </boundary-data>
220
+ confirmed, dynamic detection system <part-num-ref name="MS Blaster WORM virus is confirmed, dynamic detection system">10</part-num-ref>
221
+ may deploy <part-num-ref name="may deploy">112</part-num-ref>
222
+ one or more enforcement processes that resolve / mitigate the effect(s) of the suspect network condition(s), such that the quantity and type of enforcement processes deployed vary in accordance with the type of suspect network conditions(s) detected by the event-specific monitor processes dynamically deployed by dynamic detection system <part-num-ref name="event-specific monitor processes dynamically deployed by dynamic detection system">10.</part-num-ref>
223
+ Accordingly, dynamic detection system <part-num-ref name="event-specific monitor processes dynamically deployed by dynamic detection system 10. Accordingly, dynamic detection system">10</part-num-ref>
224
+ compares <part-num-ref name="compares">114</part-num-ref>
225
+ the suspect network condition to an enforcement rule set to determine which enforcement process(es) should be deployed. </p>
226
+ <p id="p-54" num="54">[0039] Additionally, it is possible for the existence of a suspect network condition not to require deployment of an enforcement process. For example, suppose a network administrator is simply interested in determining the point during the day at which the average port utilization of a switch exceed 70% (for purposes of determining network traffic patterns). When the monitor process determines that this condition has occurred, the monitor process may simply notify the system administrator and terminate operation (as indicated by phantom line <part-num-ref name="system administrator and terminate operation (as indicated by phantom line">116)</part-num-ref>
227
+ without deploying an enforcement process. </p>
228
+ <p id="p-55" num="55">[0040] Continuing with the above-stated example, the suspect network condition is the confirmation of the presence of the MS Blaster WORM virus on network <part-num-ref name="MS Blaster WORM virus on network">12.</part-num-ref>
229
+ Accordingly, the enforcement process(es) deployed may include: disabling access temporarily or completely, disconnecting a network user, forcing user re-authentication, limiting the bandwidth of a network device or application, quarantining, filtering traffic, redirecting network traffic, mirroring port traffic, filtering or limiting traffic based on protocols and or applications or fields and signals within the traffic, logging all traffic, making network topology changes, sending alerts or traps, terminating device sessions, and/or other changes to network access or uses. </p>
230
+ <p id="p-56" num="56">[0041] When deploying 104 event-specific monitor processes, they may be deployed in groups, such as in a serial fashion. For example, in certain situations, it may be desirable to examine the data files attached to email received by a mail server (attached to network <part-num-ref name="mail server (attached to network">12)</part-num-ref>
231
+ to determine which (if any) email has an attachment named "msblaster.exe". This <boundary-data type="header">
232
+ <confidence value="88">11</confidence>
233
+ </boundary-data>
234
+ <page-break num="12"/>
235
+ <boundary-data type="header">GTPP Docket No.: ENT<confidence value="558">002</confidence>
236
+ </boundary-data>
237
+ would result in the generation of a first set of suspect network conditions (i.e., the list of email containing attachments named "msblaster.exe"). A second serial event-specific monitor process may perform a pattern matching function to determine which of the suspect network conditions (i.e., the email containing attachments named "msblaster.exe") are conclusively infected with the MS Blaster WORM virus, thus creating a second set of suspect network conditions that is a subset of the first set of suspect network conditions. </p>
238
+ <p id="p-57" num="57">Additional event-specific monitor processes may be deployed to further enhance the accuracy of the results. Dynamic detection system <part-num-ref name="results. Dynamic detection system">10</part-num-ref>
239
+ may then deploy <part-num-ref name="may then deploy">112</part-num-ref>
240
+ one or more enforcement processes that resolve / mitigate the effect(s) of the second set of suspect network conditions. </p>
241
+ <p id="p-58" num="58">[0042] Alternatively, multiple event-specific monitor processes may be deployed 104 in a parallel fashion. For example, the first parallel event-specific monitor process may determine which (if any) email messages have an attachment named "msblaster.exe" (creating a first set of suspect network conditions). A second event-specific monitor process may perform a pattern matching function to determine which (if any) data packets are infected with the MS Blaster WORM virus (creating a second set of suspect network conditions which is independent of the first set of suspect network conditions). Dynamic detection system <part-num-ref name="first set of suspect network conditions). Dynamic detection system">10</part-num-ref>
242
+ may then generate a third set of suspect network conditions that is a mathematical function (e.g., an intersection or a union) of the first and second sets of suspect network conditions. Dynamic detection system <part-num-ref name="first and second sets of suspect network conditions. Dynamic detection system">10</part-num-ref>
243
+ may then deploy <part-num-ref name="may then deploy">112</part-num-ref>
244
+ one or more enforcement processes that resolve / mitigate the effect(s) of the third set of suspect network conditions. </p>
245
+ <p id="p-59" num="59">[0043] Referring also to FIG. 3, there is shown a diagrammatic view of dynamic detection system <part-num-ref name="diagrammatic view of dynamic detection system">10</part-num-ref>
246
+ operating on a network device (e.g., switching device <part-num-ref name="switching device">24,</part-num-ref>
247
+ <part-num-ref name="switching device 24,">26,</part-num-ref>
248
+ router device <part-num-ref name="switching device 24, 26, router device">28,</part-num-ref>
249
+ gateway <part-num-ref name="switching device 24, 26, router device 28, gateway">30,</part-num-ref>
250
+ or access point <part-num-ref name="switching device 24, 26, router device 28, gateway 30, or access point">36,</part-num-ref>
251
+ for example). As discussed above, dynamic detection system <part-num-ref name="switching device 24, 26, router device 28, gateway 30, or access point 36, for example). As discussed above, dynamic detection system">10</part-num-ref>
252
+ performs several functions, including one or more monitoring functions <part-num-ref name="performs several functions, including one or more monitoring functions">200,</part-num-ref>
253
+ <part-num-ref name="performs several functions, including one or more monitoring functions 200,">202,</part-num-ref>
254
+ <part-num-ref name="performs several functions, including one or more monitoring functions 200, 202,">204,</part-num-ref>
255
+ one or more analysis / response functions <part-num-ref name="performs several functions, including one or more monitoring functions 200, 202, 204, one or more analysis / response functions">206,</part-num-ref>
256
+ <part-num-ref name="performs several functions, including one or more monitoring functions 200, 202, 204, one or more analysis / response functions 206,">208,</part-num-ref>
257
+ <part-num-ref name="performs several functions, including one or more monitoring functions 200, 202, 204, one or more analysis / response functions 206, 208,">210,</part-num-ref>
258
+ and one <boundary-data type="header">
259
+ <confidence value="88">12</confidence>
260
+ </boundary-data>
261
+ <page-break num="13"/>
262
+ <boundary-data type="header">GTPP Docket No.: ENT<confidence value="558">002</confidence>
263
+ </boundary-data>
264
+ or more enforcement functions <part-num-ref name="performs several functions, including one or more monitoring functions 200, 202, 204, one or more analysis / response functions 206, 208, 210, and one or more enforcement functions">212,</part-num-ref>
265
+ <part-num-ref name="performs several functions, including one or more monitoring functions 200, 202, 204, one or more analysis / response functions 206, 208, 210, and one or more enforcement functions 212,">214,</part-num-ref>
266
+ <part-num-ref name="performs several functions, including one or more monitoring functions 200, 202, 204, one or more analysis / response functions 206, 208, 210, and one or more enforcement functions 212, 214,">216,</part-num-ref>
267
+ each of which will be discussed below in the following examples. </p>
268
+ <p id="p-60" num="60">[0044] Assume that a network switching device <part-num-ref name="network switching device">24</part-num-ref>
269
+ executes a first monitoring function <part-num-ref name="first monitoring function">200</part-num-ref>
270
+ that implements a basic flow detection algorithm that (while not highly accurate) consumes minimum resources (i.e., has little impact upon the operation of switching device 24). These monitoring functions may be deployed by default (i.e., always functioning) or (as discussed above) may be deployed due to the occurrence of a specific event. Example of these detection algorithms include R<confidence value="5">M</confidence>
271
+ ON (i.e., a remote monitoring function) and SMON (i.e., a switched network monitoring function). Additionally, switching device <part-num-ref name="switched network monitoring function). Additionally, switching device">24</part-num-ref>
272
+ may support highly-accurate detection algorithms (e.g., intrusion detection systems, stateful anomaly detection systems, and/or per data flow monitoring functions, for example) which are based on advanced algorithms and are highly <confidence value="8">a</confidence>
273
+ ccurate, but also consume significant switch resources. </p>
274
+ <p id="p-61" num="61">[0045] Once deployed, first monitoring function 200 may: send an event flag on detection of an event; wait to be polled; count the number of events detected continuously;</p>
275
+ <p id="p-62" num="62">count events / monitor events for a defined period of time; send a flag after the occurrence of a defined number of events (but keep counting); send a flag after the occurrence of a defined group of events; and/or run until automatically or manually terminated, for example.</p>
276
+ <p id="p-63" num="63">[0046] First analysis/response function 206 interprets the data provided by first monitoring function <part-num-ref name="data provided by first monitoring function">200.</part-num-ref>
277
+ In this example, first monitoring function <part-num-ref name="data provided by first monitoring function 200. In this example, first monitoring function">200</part-num-ref>
278
+ is in operation by default (i.e., always functioning). When first monitoring function <part-num-ref name="always functioning). When first monitoring function">200</part-num-ref>
279
+ observes a possible event (i.e., a trigger event), first monitoring function <part-num-ref name="trigger event), first monitoring function">200</part-num-ref>
280
+ notifies first analysis / response function <part-num-ref name="notifies first analysis / response function">206.</part-num-ref>
281
+ First analysis / response function <part-num-ref name="notifies first analysis / response function 206. First analysis / response function">206</part-num-ref>
282
+ then analyzes and interprets the data received from first monitoring function <part-num-ref name="data received from first monitoring function">200.</part-num-ref>
283
+ This analysis and interpretation may be performed in many different ways (e.g., comparing a trigger event detected to a monitor rule set, for example). </p>
284
+ <boundary-data type="header">
285
+ <confidence value="88">13</confidence>
286
+ </boundary-data>
287
+ <boundary-data type="header">GTPP Docket No.: ENT<confidence value="558">002</confidence>
288
+ </boundary-data>
289
+ <p id="p-64" num="64">
290
+ <page-break num="14"/>
291
+ [0047] If it is determined that additional inquiry is needed, first analysis / response function 206 may deploy one or more additional monitoring functions (e.g., monitoring functions <part-num-ref name="monitoring functions">202,</part-num-ref>
292
+ <part-num-ref name="monitoring functions 202,">204)</part-num-ref>
293
+ that utilize a more comprehensive monitoring algorithm. Examples of comprehensive monitoring algorithms that could be dynamically enabled include intrusion detection systems with specifically tuned signatures or the stateful inspection of a specific flow and/or the response flow. Dynamic detection system <part-num-ref name="response flow. Dynamic detection system">10</part-num-ref>
294
+ may deploy additional monitor functions if further investigation is warranted / needed. Once sufficiently certain, one or more enforcement functions (e.g., enforcement functions <part-num-ref name="enforcement functions">212,</part-num-ref>
295
+ <part-num-ref name="enforcement functions 212,">214,</part-num-ref>
296
+ <part-num-ref name="enforcement functions 212, 214,">216)</part-num-ref>
297
+ may be deployed. As discussed above, examples of these enforcement functions include: disabling access temporarily or completely, disconnecting a network user, forcing user re-authentication, limiting the bandwidth of a network device or application, quarantining, filtering traffic, redirecting network traffic, mirroring port traffic, filtering or limiting traffic based on protocols and or applications or fields and signals within the traffic, logging all traffic, making network topology changes, sending alerts or traps, terminating device sessions or other changes to network access or uses. </p>
298
+ <p id="p-65" num="65">[0048] The dynamic functionality of system <part-num-ref name="dynamic functionality of system">10</part-num-ref>
299
+ allows for monitor functions, analysis / response functions, and enforcement functions to be located on a single network device (e.g., switching device <part-num-ref name="switching device">24)</part-num-ref>
300
+ or distributed across multiple devices (e.g., monitor and analysis / response functions on server <part-num-ref name="monitor and analysis / response functions on server">14</part-num-ref>
301
+ and enforcement functions on switching device 24). </p>
302
+ <p id="p-66" num="66">[0049] The dynamic functionality of system <part-num-ref name="dynamic functionality of system">10</part-num-ref>
303
+ further allows for monitor functions, analysis / response functions, and enforcement functions to be located on a single network device (e.g., switching device <part-num-ref name="switching device">24)</part-num-ref>
304
+ or distributed across multiple devices (e.g., monitor and analysis / response functions on server <part-num-ref name="monitor and analysis / response functions on server">14</part-num-ref>
305
+ and enforcement functions on switching device 24). </p>
306
+ <p id="p-67" num="67">[0050] As a further example, assume that a monitor function (i.e., an uplink egress monitor function) executes (by default) on network switching device <part-num-ref name="uplink egress monitor function) executes (by default) on network switching device">24</part-num-ref>
307
+ and examines all <boundary-data type="header">
308
+ <confidence value="88">14</confidence>
309
+ </boundary-data>
310
+ <page-break num="15"/>
311
+ <boundary-data type="header">GTPP Docket No.: ENT<confidence value="558">002</confidence>
312
+ </boundary-data>
313
+ input ports to determine the occurrence of a certain input event. Upon detecting this event, system <part-num-ref name="certain input event. Upon detecting this event, system">10</part-num-ref>
314
+ may deploy additional monitor functions to determine the specific input port on which the event was detected. After determining the specific input port, additional monitors may be deployed to capture the source address of any device responding to the detected input port event. </p>
315
+ <p id="p-68" num="68">[0051] Accordingly, the deployment of one or more simple monitoring functions can aid in quickly isolating the origin of a very sophisticated event, or gaining the confirming evidence of the intent of an action or set of network actions. Therefore, local devices under the coordination of central analysis and management may be directed to determine if a device or action is local within the network device (i.e., one of perhaps hundreds in the network) and then, with additional dynamic monitor functions under local control, isolate the exact port and other pertinent information.</p>
316
+ <p id="p-69" num="69">[0052] While the dynamic detection system is described above as being executed on a server, other configurations are possible. For example, the dynamic detection system may be executed on any other network device, such as a switching device, routing device, gateway, or access point.</p>
317
+ <p id="p-70" num="70">[0053] While the dynamic detection system is described above as being executed on a network device connected to a distributed computing network, other configurations are possible. For example, the dynamic detection system may be executed on a device connected to a telephony network, such as telephones, switches, servers, and PBX (i.e., public branch exchange) devices, for example.</p>
318
+ <p id="p-71" num="71">[0054] While the dynamic detection system is described above as being used to detect intrusion / virus events, other configurations are possible, such as the control and regulation of network traffic.</p>
319
+ <p id="p-72" num="72">[0055] For example, most modern routing protocols (by default) typically route network traffic through a network port having the comparatively highest bandwidth rating.</p>
320
+ <p id="p-73" num="73">For example, if a network switching device has two ports, a low-speed <part-num-ref name="low-speed">100</part-num-ref>
321
+ Mbit<confidence value="5">/</confidence>
322
+ second <boundary-data type="header">
323
+ <confidence value="88">15</confidence>
324
+ </boundary-data>
325
+ <page-break num="16"/>
326
+ <boundary-data type="header">GTPP Docket No.: ENT<confidence value="558">002</confidence>
327
+ </boundary-data>
328
+ port and a high speed <part-num-ref name="high speed">1000</part-num-ref>
329
+ Mbit/second port, typically most (if not all) network traffic (e.g., data packets) are routed through the <part-num-ref name="">1000</part-num-ref>
330
+ Mbit/second port, with the <part-num-ref name="">100</part-num-ref>
331
+ Mbits/second port operating in a standby mode. </p>
332
+ <p id="p-74" num="74">[0056<confidence value="4">]</confidence>
333
+ However, it may be useful or desirable to route a portion of the network traffic through the low speed port. Accordingly, the administrator may configure the dynamic detection system to deploy an event specific monitor process to monitor the bandwidth consumption rate on the <part-num-ref name="">1000</part-num-ref>
334
+ Mbits/second port. This monitor process would then provide feedback to the dynamic detection system and, in the event that the consumption reaches a predefined threshold, an enforcement process is deployed. For example, assuming that the administrator defines the bandwidth threshold as 70% utilization of the <part-num-ref name="">1000</part-num-ref>
335
+ Mbit/second port (i.e., <part-num-ref name="">700</part-num-ref>
336
+ Mbit<confidence value="5">/</confidence>
337
+ second bandwidth consumption), upon receiving feedback from the event-specific monitor process indicating a consumption level that meets or exceeds this threshold, an enforcement process may be deployed that routes all world wide web traffic onto the low speed <part-num-ref name="low speed">100</part-num-ref>
338
+ Mbit<confidence value="5">/</confidence>
339
+ second port. The event-specific monitor process may be configured to continue to monitor the bandwidth consumption of the low speed <part-num-ref name="low speed">100</part-num-ref>
340
+ <confidence value="22222222222">Mbit/second</confidence>
341
+ port and the high speed <part-num-ref name="high speed">1000</part-num-ref>
342
+ Mbit/second port to determine if the sum of the bandwidth consumptions is less than 70% of the high speed <part-num-ref name="high speed">1000</part-num-ref>
343
+ Mbit/second port. If the event that the sum falls below the threshold level of 70%, the enforcement process that routes all world wide web traffic through the low speed port may be cancelled. </p>
344
+ <p id="p-75" num="75">[0057] A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made. Accordingly, other implementations are within the scope of the following claims.</p>
345
+ <boundary-data type="header">
346
+ <confidence value="88">16</confidence>
347
+ </boundary-data>
348
+ </description>
349
+ </us-patent-application>
350
+
prior_art/11068608.xml ADDED
@@ -0,0 +1,376 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11068608</doc-number>
8
+ <date>2005-02-28</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <heading id="h-1">TITLE OF THE INVENTION</heading>
14
+ <heading id="h-2">BRACKETS AND BRACKET SYSTEM FOR ASSEMBLING PLAYGROUND EQUI<confidence value="8">P</confidence>
15
+ MENT </heading>
16
+ <heading id="h-3">BACKGROUND OF THE INVENTION</heading>
17
+ <p id="p-1" num="1">[0001] The present invention is directed to a bracket system and brackets for assembling playground equipment, and a method for assembling playground equipment using the bracket system. More particularly, the present invention pertains to a bracket system and method of use thereof including several different types of brackets for assembling playground equipment comprising upright posts to which elements such as platforms, ladders, swing beams and the like are secured.</p>
18
+ <p id="p-2" num="2">[0002] Many different configurations of playground equipment are well known in the art. In many constructions, vertical frame beams or posts provide support for the equipment's individual play units, which may include mounted platforms, towers, ladders, slides, overhead bars, firepoles, ropes, climbing walls, or swing beams. Several of these distinct play units may be interconnected by a single deck, so that a child may reach all of the play units from the same platform. Other units also may be added, including other decks, to enlarge the equipment.</p>
19
+ <p id="p-3" num="3">[0003] Most known playground equipment is constructed of multiple components, which must be assembled by a user. In all such configurations, many of the components must be attached by hardware or mechanical fasteners such as bolts, screws, or the like. Many types of prior art playground equipment must be pre-assembled during construction, resulting in bulky pieces that are difficult to store and transport. Other types of prior art playground equipment have very complex constructions and connections, requiring the services of a professional with a variety of tools to put it together. Even if a user is supposed to be able to assemble a piece of playground equipment himself, in his own backyard, the means of connecting prior art components to one <boundary-data type="header">2071646<confidence value="5">_</confidence>
20
+ 2.DOC </boundary-data>
21
+ <page-break num="2"/>
22
+ another frequently is confusing and unclear, with every connector looking the same. Further, owner-assembled playground equipment frequently is not nearly as sturdy or secure as institutional playground equipment, because of sub-par assembly or connecting means. </p>
23
+ <p id="p-4" num="4">[0004] Accordingly, there exists a need for a rigid, strong, and stable bracket system for assembling modular playground equipment that is simple and straightforward to use. Such a bracket system and method of use thereof allows the playground equipment components together with their brackets to be efficiently and compactly stacked for easy transport and lower shipping costs. Desirably, such a bracket system includes brackets of several different styles, wherein each style is designed to safely and securely connect different types of playground equipment components. Most desirably, such a bracket system and method of use thereof allows users to quickly and easily understand how to assemble their playground equipment; unlike other, prior art means of constructing playground equipment, no professional assistance is required to use the bracket system of the present invention.</p>
24
+ <heading id="h-4">BRIEF SUMMARY OF THE INVENTION</heading>
25
+ <p id="p-5" num="5">[0005] A bracket system for assembling playground equipment includes a plurality of deck support brackets, at least two vertical frame brackets, at least two horizontal frame brackets, a swing bracket, and at least two ladder brackets. The deck support brackets secure a plurality of horizontal deck support beams to a plurality of vertical frame beams at first points along the vertical frame beams. The vertical frame brackets attach to at least two adjacent vertical frame beams at second points above the first points. The at least two horizontal frame brackets fix at least one horizontal frame beam to the at least two adjacent vertical frame beams at the second points; the horizontal frame brackets and the vertical frame brackets interconnect.</p>
26
+ <p id="p-6" num="6">[0006] The swing bracket fastens a swing support beam to the at least one horizontal frame beam at a third point along the at least one horizontal frame beam. The at least two ladder <boundary-data type="header">2071646_2.DOC 2</boundary-data>
27
+ <page-break num="3"/>
28
+ brackets connect a ladder to one of the horizontal deck support beams. Desirably, at least two additional ladder brackets are included, to connect a climbing wall to one of the plurality of horizontal deck support beams. </p>
29
+ <p id="p-7" num="7">[0007] In a preferred embodiment, the first points are located approximately at a midpoint between a bottom and a top of the vertical frame beams. The second points may be located approximately at a midpoint between the first points and a top of the vertical frame beams. The third point may be located approximately at a midpoint between the at least two horizontal frame brackets.</p>
30
+ <p id="p-8" num="8">[0008] Preferably, each of the brackets comprising the bracket system comprises a single piece of folded or bent material and creates each individual bracket style. This material may include durable metals and/or plastics. The deck support brackets include a base, a back perpendicularly oriented to the base, and left and right sloping sides. Outer portions of the left and right sides are substantially perpendicular to both the base and the back, but inner portions of the left and right sides fold perpendicularly to the outer portions, overlapping the forming a channel flaps which are separated by a slot above the back. The slot is useful to cooperate with other brackets as will be described below. The base, back, and left and right sides all include holes for receiving fasteners.</p>
31
+ <p id="p-9" num="9">[0009] The second frame brackets include a back, left and right side walls perpendicular to the back, and short upper and lower front walls perpendicular to the side walls. The upper front wall extends toward the lower front wall spaced by a channel gap, and the lower front wall extends away from the upper front wall. The back and upper and lower front walls as well as the side walls preferably include holes for receiving fasteners.</p>
32
+ <boundary-data type="header">2071646_2.DOC 3</boundary-data>
33
+ <p id="p-10" num="10">
34
+ <page-break num="4"/>
35
+ [00010] The second frame brackets include a back, left and lower sidewalls perpendicular to the back, and short lower front walls perpendicular to the side walls. The upper front wall extends toward the lower front wall and the lower front wall extends towards the upper front wall. The back and upper lower front walls as well as the side walls include walls for receiving fasteners. </p>
36
+ <p id="p-11" num="11">[00011] The swing bracket preferably includes a base, left and right upper back walls extending towards each other and perpendicular to the base, left and right side walls perpendicular to the left and right upper back walls, a lower back wall perpendicular to the base, and a lower front wall perpendicular to the base. The left and right upper back walls, the left and right sloping side walls, the lower back wall, and the lower front wall all include holes for receiving fasteners.</p>
37
+ <p id="p-12" num="12">[00012] Finally, the ladder brackets include a back, a sloping side wall perpendicular to the back, and a top wall at an obtuse angle to the back. The back, the side wall, and the top wall all include holes for receiving fasteners. A piece of playground equipment assembled with the bracket system and a method for assembling playground equipment also are disclosed. The method preferably includes the steps of securing horizontal deck beams to vertical frame beams with deck support brackets; attaching vertical frame brackets to adjacent vertical frame beams;</p>
38
+ <p id="p-13" num="13">fixing a horizontal frame beam to the adjacent vertical frame beams; interconnecting the horizontal frame brackets and the vertical frame brackets; fastening a swing support beam to the horizontal frame beam with a swing bracket; and connecting a ladder to one of the horizontal deck support beams with ladder brackets. Most desirably, the method further includes the step of connecting a climbing wall to one of the horizontal deck support beams with additional ladder brackets.</p>
39
+ <p id="p-14" num="14">[00013] The first and second frame brackets are not only usable separately but are also utilized together with overlapping wall portions such as side walls which overlap thereby allowing beams <boundary-data type="header">2071646_2.DOC 4</boundary-data>
40
+ <page-break num="5"/>
41
+ to be placed therethrough which secures the beams together and prevents rotation of one beam relative to the other. Holes for receiving fasteners through the brackets are useful to secure the beams to the brackets so that the brackets do not move relative to the beams. </p>
42
+ <p id="p-15" num="15">[00014] Similarly, deck support brackets are useful together with either the first and second frame brackets. By providing the slot over one of the wall portions of either the first and second brackets beams can constrained by the brackets. Using these brackets overlap bracket wall portions are located intermediate adjacent beams.</p>
43
+ <p id="p-16" num="16">[00015] The swing support bracket can function somewhat similarly by itself in that its base functions as the panel intermediate adjacent beams. When beams are installed with this bracket the beams are securely held in position relative to one another. Using these brackets at least some of the stresses on the brackets are carried by sheer load on the fasteners through the holes in the brackets, if at all.</p>
44
+ <p id="p-17" num="17">[00016] These and other features and advantages of the present invention will be apparent from the following detailed description, in conjunction with the appended claims.</p>
45
+ <heading id="h-5">BRIEF DESCRI<confidence value="8">P</confidence>
46
+ TION OF THE SEVERAL VIEWS OF THE DRAWINGS </heading>
47
+ <p id="p-18" num="18">[00017] The benefits and advantages of the present invention will become more readily apparent to those of ordinary skill in the relevant art after reviewing the following detailed description and accompanying drawings, wherein:</p>
48
+ <p id="p-19" num="19">Figure 1 is a perspective view of a piece of playground equipment assembled with a bracket system and brackets according to the preferred embodiment of the present invention;</p>
49
+ <p id="p-20" num="20">Figure 2 shows a perspective view of a deck support bracket used in the bracket system of the present invention;</p>
50
+ <p id="p-21" num="21">Figure 3 illustrates a perspective view of a vertical frame bracket used in the bracket system of the present invention;</p>
51
+ <boundary-data type="header">2071646_2.DOC 5</boundary-data>
52
+ <p id="p-22" num="22">
53
+ <page-break num="6"/>
54
+ Figure 4 depicts a perspective view of a horizontal frame bracket used in the bracket system of the present invention; </p>
55
+ <p id="p-23" num="23">Figure 5 is a perspective view of a swing bracket used in the bracket system of the present invention; and Figure 6 shows a perspective view of a ladder bracket used in the bracket system of the present invention;</p>
56
+ <p id="p-24" num="24">Figure 7 shows a perspective view of a deck support bracket connected to a second frame bracket;</p>
57
+ <p id="p-25" num="25">Figure 8 shows a detailed side view of a portions of the bracket shown in Figure 7 showing the installation of the deck bracket relative to the second frame bracket; and Figure 9 shows the first and second frame brackets connected together with the inserted beams removed.</p>
58
+ <heading id="h-6">DETAILED DESCRIPTION OF THE INVENTION</heading>
59
+ <p id="p-26" num="26">[00018] While the present invention is susceptible of embodiment in various forms, there is shown in the drawings and will hereinafter be described a presently preferred embodiment with the understanding that the present disclosure is to be considered an exemplification of the invention and is not intended to limit the invention to the specific embodiment illustrated.</p>
60
+ <p id="p-27" num="27">[00019] It should be further understood that the title of this section of this specification, namely, "Detailed Description Of The Invention", relates to a requirement of the United States Patent Office, and does not imply, nor should be inferred to limit the subject matter disclosed herein.</p>
61
+ <p id="p-28" num="28">[00020] Referring to the figures, and in particular Figure 1, there is shown a piece of playground equipment <part-num-ref name="piece of playground equipment">10,</part-num-ref>
62
+ assembled with the bracket system of the present invention. The bracket system includes deck support brackets <part-num-ref name="bracket system includes deck support brackets">12,</part-num-ref>
63
+ vertical frame brackets <part-num-ref name="bracket system includes deck support brackets 12, vertical frame brackets">14,</part-num-ref>
64
+ horizontal frame brackets <part-num-ref name="bracket system includes deck support brackets 12, vertical frame brackets 14, horizontal frame brackets">16,</part-num-ref>
65
+ <boundary-data type="header">2071646_2.DOC 6</boundary-data>
66
+ <page-break num="7"/>
67
+ swing brackets <part-num-ref name="bracket system includes deck support brackets 12, vertical frame brackets 14, horizontal frame brackets 16, swing brackets">18,</part-num-ref>
68
+ and ladder brackets <part-num-ref name="bracket system includes deck support brackets 12, vertical frame brackets 14, horizontal frame brackets 16, swing brackets 18, and ladder brackets">20.</part-num-ref>
69
+ The plurality of deck support brackets <part-num-ref name="plurality of deck support brackets">12</part-num-ref>
70
+ secure a plurality of horizontal deck support beams <part-num-ref name="plurality of horizontal deck support beams">22</part-num-ref>
71
+ to a plurality of vertical frame beams <part-num-ref name="plurality of vertical frame beams">24</part-num-ref>
72
+ at first points <part-num-ref name="at first points">26</part-num-ref>
73
+ along the vertical frame beams. Preferably, the first point <part-num-ref name="first point">26</part-num-ref>
74
+ is located approximately at a midpoint between a bottom <part-num-ref name="bottom">28</part-num-ref>
75
+ and a top <part-num-ref name="top">30</part-num-ref>
76
+ of the vertical frame beams <part-num-ref name="vertical frame beams">24.</part-num-ref>
77
+ The vertical frame beams <part-num-ref name="vertical frame beams">24</part-num-ref>
78
+ provide stability in addition to holding up the playground equipment <part-num-ref name="playground equipment">10.</part-num-ref>
79
+ At least one middle support beam <part-num-ref name="playground equipment 10. At least one middle support beam">23</part-num-ref>
80
+ connected to opposing deck support beams <part-num-ref name="connected to opposing deck support beams">22</part-num-ref>
81
+ with at least two deck support brackets further stabilizes the equipment <part-num-ref name="equipment">10.</part-num-ref>
82
+ A deck <part-num-ref name="deck">32</part-num-ref>
83
+ attaches to and is mounted on the horizontal deck support beams <part-num-ref name="horizontal deck support beams">22</part-num-ref>
84
+ and the middle support beam <part-num-ref name="middle support beam">23.</part-num-ref>
85
+ </p>
86
+ <p id="p-29" num="29">[00021] Most preferably, the bracket system uses a total of ten deck support brackets <part-num-ref name="total of ten deck support brackets">12.</part-num-ref>
87
+ Eight of the deck support brackets <part-num-ref name="deck support brackets">12</part-num-ref>
88
+ secure four deck support beams <part-num-ref name="secure four deck support beams">22</part-num-ref>
89
+ to four vertical frame beams <part-num-ref name="to four vertical frame beams">24,</part-num-ref>
90
+ so that two deck support brackets are fixed to each deck support beam <part-num-ref name="to four vertical frame beams 24, so that two deck support brackets are fixed to each deck support beam">22.</part-num-ref>
91
+ The remaining two deck support brackets secure a middle support beam <part-num-ref name="middle support beam">23</part-num-ref>
92
+ to two opposing deck support beams <part-num-ref name="to two opposing deck support beams">22</part-num-ref>
93
+ underneath the deck <part-num-ref name="deck">32</part-num-ref>
94
+ to further stabilize the equipment <part-num-ref name="equipment">10.</part-num-ref>
95
+ In this configuration, one deck support bracket <part-num-ref name="equipment 10. In this configuration, one deck support bracket">12</part-num-ref>
96
+ is attached to a left side <part-num-ref name="left side">34</part-num-ref>
97
+ of each deck support beam <part-num-ref name="of each deck support beam">22,</part-num-ref>
98
+ and one deck support bracket is attached to a right side <part-num-ref name="right side">36</part-num-ref>
99
+ of each deck support beam. Two deck support bracket <part-num-ref name="of each deck support beam. Two deck support bracket">12</part-num-ref>
100
+ then may be attached to adjacent sides of each of the four vertical frame beams <part-num-ref name="four vertical frame beams">24.</part-num-ref>
101
+ </p>
102
+ <p id="p-30" num="30">As shown in Figure 1, the deck support brackets <part-num-ref name="deck support brackets">12</part-num-ref>
103
+ may be connected to the first frame brackets <part-num-ref name="first frame brackets">14</part-num-ref>
104
+ or the second frame brackets <part-num-ref name="second frame brackets">16</part-num-ref>
105
+ in a similar manner. </p>
106
+ <p id="p-31" num="31">[00022] Figure 2 depicts a deck support bracket <part-num-ref name="deck support bracket">12</part-num-ref>
107
+ in accordance with the principles of the present invention. The deck support bracket <part-num-ref name="deck support bracket">12</part-num-ref>
108
+ preferably is composed of a single piece of material, folded or bent to include a base <part-num-ref name="base">38,</part-num-ref>
109
+ a back <part-num-ref name="back">40</part-num-ref>
110
+ perpendicularly oriented to the base, and left and right sloping sides <part-num-ref name="base, and left and right sloping sides">42,</part-num-ref>
111
+ <part-num-ref name="base, and left and right sloping sides 42,">44.</part-num-ref>
112
+ Most preferably, the deck support bracket <part-num-ref name="deck support bracket">12</part-num-ref>
113
+ is made of a durable metal <confidence value="222222">and/or</confidence>
114
+ plastic material. Outer portions <part-num-ref name="durable metal and/or plastic material. Outer portions">46</part-num-ref>
115
+ of the left and right sides <part-num-ref name="left and right sides">42,</part-num-ref>
116
+ <part-num-ref name="left and right sides 42,">44</part-num-ref>
117
+ are <boundary-data type="header">2071646_2.DOC 7</boundary-data>
118
+ <page-break num="8"/>
119
+ substantially perpendicular to both the base <part-num-ref name="base">38</part-num-ref>
120
+ and the back <part-num-ref name="back">40,</part-num-ref>
121
+ but inner portions of the left and right sides fold perpendicularly to the outer portions, overlapping the back forming flaps 48,49. </p>
122
+ <p id="p-32" num="32">The base 38, back 40, and left and right sides 42, 44 and flaps 48,49 include openings <part-num-ref name="and flaps 48,49 include openings">50</part-num-ref>
123
+ for receiving fasteners, such as screws, bolts, or the like. The flaps 48,49 are separated from the back <part-num-ref name="back">40</part-num-ref>
124
+ by slot <part-num-ref name="by slot">51.</part-num-ref>
125
+ The slot <part-num-ref name="slot">51</part-num-ref>
126
+ is useful in connecting with one of the first and second frame brackets 14,16 as will be described in detail below. </p>
127
+ <p id="p-33" num="33">[00023] Returning to Figure 1 and the bracket system, at least two vertical frame brackets <part-num-ref name="bracket system, at least two vertical frame brackets">14</part-num-ref>
128
+ are attached to at least two adjacent vertical frame beams <part-num-ref name="are attached to at least two adjacent vertical frame beams">24</part-num-ref>
129
+ at second points <part-num-ref name="at second points">54</part-num-ref>
130
+ along the vertical frame beams and above the first points <part-num-ref name="first points">26.</part-num-ref>
131
+ Preferably, the second points <part-num-ref name="second points">54</part-num-ref>
132
+ are located approximately at a midpoint between the first points <part-num-ref name="first points">26</part-num-ref>
133
+ and a top <part-num-ref name="top">30</part-num-ref>
134
+ of the vertical frame beams <part-num-ref name="vertical frame beams">24.</part-num-ref>
135
+ Most preferably, the bracket system uses a total of two vertical frame brackets <part-num-ref name="total of two vertical frame brackets">14,</part-num-ref>
136
+ each attached to one of two separate and adjacent vertical frame beams <part-num-ref name="total of two vertical frame brackets 14, each attached to one of two separate and adjacent vertical frame beams">24</part-num-ref>
137
+ at the second points <part-num-ref name="second points">54.</part-num-ref>
138
+ </p>
139
+ <p id="p-34" num="34">[00024] Figure 3 illustrates a first or vertical frame bracket <part-num-ref name="first or vertical frame bracket">14</part-num-ref>
140
+ in accordance with the principles of the present invention. The vertical frame bracket <part-num-ref name="vertical frame bracket">14</part-num-ref>
141
+ preferably is composed of a single piece of material, folded or bent to include a back <part-num-ref name="back">56,</part-num-ref>
142
+ left and right side walls <part-num-ref name="back 56, left and right side walls">58,</part-num-ref>
143
+ <part-num-ref name="back 56, left and right side walls 58,">60</part-num-ref>
144
+ perpendicular to the back, and short left and right front walls <part-num-ref name="back, and short left and right front walls">62,</part-num-ref>
145
+ <part-num-ref name="back, and short left and right front walls 62,">64</part-num-ref>
146
+ perpendicular to the side walls and extending towards each other. Most preferably, the vertical frame bracket <part-num-ref name="vertical frame bracket">14</part-num-ref>
147
+ is made of a durable metal and/or plastic material. The back <part-num-ref name="back">56,</part-num-ref>
148
+ side walls 58,60 and left and right front walls <part-num-ref name="back 56, side walls 58,60 and left and right front walls">62,</part-num-ref>
149
+ <part-num-ref name="back 56, side walls 58,60 and left and right front walls 62,">64</part-num-ref>
150
+ preferably include openings <part-num-ref name="preferably include openings">66</part-num-ref>
151
+ for receiving fasteners <part-num-ref name="for receiving fasteners">52,</part-num-ref>
152
+ such as screws, bolts, or the like. </p>
153
+ <p id="p-35" num="35">[00025] Again returning to Figure 1 and the bracket system, at least two horizontal frame brackets <part-num-ref name="bracket system, at least two horizontal frame brackets">16</part-num-ref>
154
+ fix at least one horizontal frame beam <part-num-ref name="fix at least one horizontal frame beam">68</part-num-ref>
155
+ to the at least two vertical frame beams <part-num-ref name="at least two vertical frame beams">24</part-num-ref>
156
+ at the second points <part-num-ref name="second points">54.</part-num-ref>
157
+ The at least two horizontal frame brackets <part-num-ref name="at least two horizontal frame brackets">16</part-num-ref>
158
+ and the at least two vertical frame brackets <part-num-ref name="at least two vertical frame brackets">14</part-num-ref>
159
+ interconnect as will be described below. Preferably, the bracket <boundary-data type="header">2071646_2.DOC 8</boundary-data>
160
+ <page-break num="9"/>
161
+ system uses a total of two horizontal frame brackets for fixing a single horizontal frame beam to both of two separate and adjacent vertical frame beams <part-num-ref name="single horizontal frame beam to both of two separate and adjacent vertical frame beams">24</part-num-ref>
162
+ at the second points <part-num-ref name="second points">54.</part-num-ref>
163
+ </p>
164
+ <p id="p-36" num="36">[00026] Figure 4 shows a second or horizontal frame bracket <part-num-ref name="second or horizontal frame bracket">16</part-num-ref>
165
+ in accordance with the principles of the present invention. The horizontal frame bracket <part-num-ref name="horizontal frame bracket">16</part-num-ref>
166
+ preferably is composed of a single piece of material, folded or bent to include a back <part-num-ref name="back">70,</part-num-ref>
167
+ upper and lower side walls <part-num-ref name="back 70, upper and lower side walls">72,</part-num-ref>
168
+ <part-num-ref name="back 70, upper and lower side walls 72,">74</part-num-ref>
169
+ perpendicular to the back, and short upper and lower front walls <part-num-ref name="back, and short upper and lower front walls">76,</part-num-ref>
170
+ <part-num-ref name="back, and short upper and lower front walls 76,">78</part-num-ref>
171
+ perpendicular to the side walls. Most preferably, the horizontal frame bracket <part-num-ref name="horizontal frame bracket">16</part-num-ref>
172
+ is made of a durable metal and/or plastic material. The upper front wall <part-num-ref name="upper front wall">76</part-num-ref>
173
+ extends toward the lower front wall <part-num-ref name="lower front wall">78</part-num-ref>
174
+ and depends from the upper side wall <part-num-ref name="upper side wall">72,</part-num-ref>
175
+ but the lower front wall extends away front the upper front wall and depends from the lower side wall <part-num-ref name="lower side wall">74.</part-num-ref>
176
+ The back <part-num-ref name="back">70,</part-num-ref>
177
+ side walls 72,74 and the upper and lower front walls <part-num-ref name="upper and lower front walls">76,</part-num-ref>
178
+ <part-num-ref name="upper and lower front walls 76,">78</part-num-ref>
179
+ include openings <part-num-ref name="include openings">80</part-num-ref>
180
+ for receiving fasteners <part-num-ref name="for receiving fasteners">52</part-num-ref>
181
+ such as screws, bolts, or the like. </p>
182
+ <p id="p-37" num="37">[00027] A swing bracket <part-num-ref name="swing bracket">18</part-num-ref>
183
+ fastens a swing support beam <part-num-ref name="swing support beam">82</part-num-ref>
184
+ to the at least one horizontal frame beam <part-num-ref name="at least one horizontal frame beam">68</part-num-ref>
185
+ at a third point <part-num-ref name="third point">84</part-num-ref>
186
+ along the at least one horizontal frame beam, as seen in Figure 1. </p>
187
+ <p id="p-38" num="38">Preferably, the third point <part-num-ref name="third point">84</part-num-ref>
188
+ is located approximately at a midpoint between the at least two horizontal frame brackets <part-num-ref name="at least two horizontal frame brackets">16.</part-num-ref>
189
+ Most preferably, a single swing bracket <part-num-ref name="single swing bracket">18</part-num-ref>
190
+ fastens the swing support beam <part-num-ref name="swing support beam">82</part-num-ref>
191
+ to a single horizontal frame beam <part-num-ref name="single horizontal frame beam">68</part-num-ref>
192
+ at the third point <part-num-ref name="third point">84.</part-num-ref>
193
+ </p>
194
+ <p id="p-39" num="39">[00028] Figure 5 depicts a swing bracket <part-num-ref name="swing bracket">18</part-num-ref>
195
+ in accordance with the principles of the present invention. The swing bracket <part-num-ref name="swing bracket">18</part-num-ref>
196
+ preferably is composed of a single piece of material, folded or bent to include a base <part-num-ref name="base">86,</part-num-ref>
197
+ left and right upper back walls <part-num-ref name="base 86, left and right upper back walls">88,</part-num-ref>
198
+ <part-num-ref name="base 86, left and right upper back walls 88,">90</part-num-ref>
199
+ extending toward each other and perpendicular to the base, defining channel <part-num-ref name="base, defining channel">39</part-num-ref>
200
+ therebetween left and right sloping side walls <part-num-ref name="therebetween left and right sloping side walls">92,</part-num-ref>
201
+ <part-num-ref name="therebetween left and right sloping side walls 92,">94</part-num-ref>
202
+ perpendicular to the left and right upper back walls, a lower back wall <part-num-ref name="lower back wall">96</part-num-ref>
203
+ perpendicular to the base and depending therefrom, and a lower front wall <part-num-ref name="lower front wall">98</part-num-ref>
204
+ perpendicular to the base and depending therefrom. Most preferably, the swing bracket <part-num-ref name="swing bracket">18</part-num-ref>
205
+ is made of a durable metal and/or <boundary-data type="header">2071646_2.DOC 9</boundary-data>
206
+ <page-break num="10"/>
207
+ plastic material. The left and right upper back walls <part-num-ref name="left and right upper back walls">88,</part-num-ref>
208
+ <part-num-ref name="left and right upper back walls 88,">90,</part-num-ref>
209
+ the left and right sloping side walls <part-num-ref name="left and right sloping side walls">92,</part-num-ref>
210
+ <part-num-ref name="left and right sloping side walls 92,">94,</part-num-ref>
211
+ the lower back wall <part-num-ref name="lower back wall">96,</part-num-ref>
212
+ and the lower front wall <part-num-ref name="lower front wall">98</part-num-ref>
213
+ include openings <part-num-ref name="include openings">100</part-num-ref>
214
+ for receiving fasteners <part-num-ref name="for receiving fasteners">52</part-num-ref>
215
+ such as screws, bolts, or the like. </p>
216
+ <p id="p-40" num="40">[00029] Turning again to Figure<confidence value="5">1</confidence>
217
+ and the bracket system, at least two ladder brackets <part-num-ref name="bracket system, at least two ladder brackets">20</part-num-ref>
218
+ connect a ladder <part-num-ref name="ladder">102</part-num-ref>
219
+ to one of the plurality of horizontal deck support beams <part-num-ref name="plurality of horizontal deck support beams">22.</part-num-ref>
220
+ Preferably, the bracket system uses a total of two ladder brackets <part-num-ref name="total of two ladder brackets">20,</part-num-ref>
221
+ each attached to one of two legs <part-num-ref name="total of two ladder brackets 20, each attached to one of two legs">104,</part-num-ref>
222
+ <part-num-ref name="total of two ladder brackets 20, each attached to one of two legs 104,">106</part-num-ref>
223
+ of the ladder <part-num-ref name="ladder">102,</part-num-ref>
224
+ and to one of the four horizontal deck support beams <part-num-ref name="four horizontal deck support beams">22.</part-num-ref>
225
+ In a preferred embodiment, additional ladder brackets <part-num-ref name="preferred embodiment, additional ladder brackets">20</part-num-ref>
226
+ also may be used to connect a climbing wall <part-num-ref name="climbing wall">108</part-num-ref>
227
+ to one of the plurality of horizontal deck support beams <part-num-ref name="plurality of horizontal deck support beams">22.</part-num-ref>
228
+ Most preferably, the bracket system uses two additional ladder brackets <part-num-ref name="bracket system uses two additional ladder brackets">20,</part-num-ref>
229
+ each attached to the climbing wall <part-num-ref name="climbing wall">108,</part-num-ref>
230
+ and to one of the four horizontal deck support beams <part-num-ref name="four horizontal deck support beams">22.</part-num-ref>
231
+ If both a ladder <part-num-ref name="ladder">102</part-num-ref>
232
+ and a climbing wall <part-num-ref name="climbing wall">108</part-num-ref>
233
+ are included with the piece of playground equipment <part-num-ref name="piece of playground equipment">10,</part-num-ref>
234
+ the ladder and the climbing wall should be connected to separate horizontal deck support beams <part-num-ref name="climbing wall should be connected to separate horizontal deck support beams">22.</part-num-ref>
235
+ Such beams <part-num-ref name="climbing wall should be connected to separate horizontal deck support beams 22. Such beams">22</part-num-ref>
236
+ may be adjacent, opposite, or unrelated to each other. </p>
237
+ <p id="p-41" num="41">[00030] Figure 6 illustrates a ladder bracket <part-num-ref name="ladder bracket">20</part-num-ref>
238
+ in accordance with the principles of the present invention. The ladder bracket <part-num-ref name="ladder bracket">20</part-num-ref>
239
+ preferably is composed of a single piece of material, folded or bent to include a back <part-num-ref name="back">110,</part-num-ref>
240
+ a sloping side wall <part-num-ref name="sloping side wall">112</part-num-ref>
241
+ perpendicular to the back, and a top wall <part-num-ref name="top wall">114</part-num-ref>
242
+ at an obtuse angle to the back. Most preferably, the ladder bracket <part-num-ref name="ladder bracket">20</part-num-ref>
243
+ is made of a durable metal and/or plastic material. The back <part-num-ref name="back">110,</part-num-ref>
244
+ the side wall <part-num-ref name="side wall">112,</part-num-ref>
245
+ and the top wall <part-num-ref name="top wall">114</part-num-ref>
246
+ all include openings <part-num-ref name="all include openings">116</part-num-ref>
247
+ for receiving fasteners <part-num-ref name="for receiving fasteners">52</part-num-ref>
248
+ such as screws, bolts, or the like. </p>
249
+ <p id="p-42" num="42">[00031] A method of assembling a piece of playground equipment <part-num-ref name="piece of playground equipment">10</part-num-ref>
250
+ using the bracket system of the present invention also is disclosed. The method includes the steps of securing a plurality of horizontal deck support beams <part-num-ref name="plurality of horizontal deck support beams">22</part-num-ref>
251
+ to a plurality of vertical frame beams <part-num-ref name="plurality of vertical frame beams">24</part-num-ref>
252
+ at first points <part-num-ref name="at first points">26</part-num-ref>
253
+ <boundary-data type="header">2071646_2.DOC 10</boundary-data>
254
+ <page-break num="11"/>
255
+ along the vertical frame beams with a plurality of deck support brackets <part-num-ref name="plurality of deck support brackets">12</part-num-ref>
256
+ and fasteners; </p>
257
+ <p id="p-43" num="43">attaching at least two vertical frame brackets 14 to at least two adjacent vertical frame beams at second points <part-num-ref name="to at least two adjacent vertical frame beams at second points">54</part-num-ref>
258
+ along the vertical frame beams above the first points with fasteners; fixing at least one horizontal frame beam <part-num-ref name="first points with fasteners; fixing at least one horizontal frame beam">68</part-num-ref>
259
+ to the at least two adjacent vertical frame beams at the second points with at least two horizontal frame brackets <part-num-ref name="second points with at least two horizontal frame brackets">16</part-num-ref>
260
+ and fasteners; interconnecting the at least two horizontal frame brackets and the at least two vertical frame brackets; fastening a swing support beam <part-num-ref name="swing support beam">82</part-num-ref>
261
+ to the at least one horizontal frame beam at a third point <part-num-ref name="third point">84</part-num-ref>
262
+ along the at least one horizontal frame beam with a swing bracket <part-num-ref name="swing bracket">18</part-num-ref>
263
+ and fasteners; and connecting a ladder <part-num-ref name="ladder">102</part-num-ref>
264
+ to one of the plurality of horizontal deck support beams with at least two ladder brackets <part-num-ref name="plurality of horizontal deck support beams with at least two ladder brackets">20</part-num-ref>
265
+ and fasteners. </p>
266
+ <p id="p-44" num="44">[00032] Preferably, the first points <part-num-ref name="first points">26</part-num-ref>
267
+ described in the above method are located approximately at a midpoint between a bottom <part-num-ref name="bottom">28</part-num-ref>
268
+ and a top <part-num-ref name="top">30</part-num-ref>
269
+ of the vertical frame beams <part-num-ref name="vertical frame beams">24.</part-num-ref>
270
+ The second points <part-num-ref name="second points">54</part-num-ref>
271
+ preferably are located approximately at a midpoint between the first points <part-num-ref name="first points">26</part-num-ref>
272
+ and a top <part-num-ref name="top">30</part-num-ref>
273
+ of the vertical frame beams <part-num-ref name="vertical frame beams">24.</part-num-ref>
274
+ The third point <part-num-ref name="third point">84</part-num-ref>
275
+ preferably is located approximately at a midpoint between the at least two horizontal frame brackets <part-num-ref name="at least two horizontal frame brackets">16.</part-num-ref>
276
+ Most preferably, the method of assembling a piece of playground equipment <part-num-ref name="piece of playground equipment">10</part-num-ref>
277
+ using the bracket system of the present invention further includes the step of connecting a climbing wall <part-num-ref name="climbing wall">108</part-num-ref>
278
+ to one of the plurality of horizontal deck support beams <part-num-ref name="plurality of horizontal deck support beams">22</part-num-ref>
279
+ with at least two additional ladder brackets <part-num-ref name="with at least two additional ladder brackets">20</part-num-ref>
280
+ and fasteners. </p>
281
+ <p id="p-45" num="45">[00033] Figure 7 shows the interlocking nature of the deck support bracket <part-num-ref name="deck support bracket">12</part-num-ref>
282
+ with the first frame support bracket <part-num-ref name="first frame support bracket">14.</part-num-ref>
283
+ The back <part-num-ref name="back">40</part-num-ref>
284
+ of the deck support bracket <part-num-ref name="deck support bracket">12</part-num-ref>
285
+ is located on one side of the left side wall <part-num-ref name="left side wall">58</part-num-ref>
286
+ while the flaps 48,49 are located on the other side of the left side wall <part-num-ref name="left side wall">58.</part-num-ref>
287
+ </p>
288
+ <p id="p-46" num="46">This allows the left side wall <part-num-ref name="left side wall">58</part-num-ref>
289
+ to be received within the slot <part-num-ref name="slot">51</part-num-ref>
290
+ as shown in Figure 8. The holes <part-num-ref name="holes">50</part-num-ref>
291
+ extend through both of the flaps 48,49, and the back <part-num-ref name="back">40.</part-num-ref>
292
+ The holes <part-num-ref name="holes">66</part-num-ref>
293
+ in the first frame <boundary-data type="header">2071646_2.DOC 11</boundary-data>
294
+ <page-break num="12"/>
295
+ member <part-num-ref name="first frame member">14</part-num-ref>
296
+ preferably coincide and/or overlap with the holes <part-num-ref name="holes">50.</part-num-ref>
297
+ Accordingly, fasteners can be provided through any of the holes 50,66 into an appropriate beam. </p>
298
+ <p id="p-47" num="47">[00034] Figure 9 shows first and second frame brackets 14,16 interconnected as could occur at a portion of a beam such as shown at position <part-num-ref name="beam such as shown at position">54</part-num-ref>
299
+ in Figure 1 or elsewhere. Of course, any of the sides 58,60, front walls 62,64, or back <part-num-ref name="sides 58,60, front walls 62,64, or back">56</part-num-ref>
300
+ could interface with the side wall 72,74 back <part-num-ref name="side wall 72,74 back">70</part-num-ref>
301
+ or even front wall <part-num-ref name="or even front wall">76</part-num-ref>
302
+ as illustrated in Figure 1. Since the holes <part-num-ref name="holes">80</part-num-ref>
303
+ as shown in Figure 4 overlap with the holes <part-num-ref name="holes">66</part-num-ref>
304
+ as shown in Figure 3 with adjacent panels placed next to one another in overlapping context, it should be easy to see that the fastener such as screws or bolts <part-num-ref name="fastener such as screws or bolts">52</part-num-ref>
305
+ as shown in Figure 9 can be placed through the holes into beams such as illustrated beam <part-num-ref name="holes into beams such as illustrated beam">24</part-num-ref>
306
+ shown in phantom in Figure 9. One skilled in the art will see as shown in Figure 9 that the side wall <part-num-ref name="side wall">58</part-num-ref>
307
+ is in contacting engagement with the side wall <part-num-ref name="side wall">72</part-num-ref>
308
+ of the second bracket <part-num-ref name="second bracket">16.</part-num-ref>
309
+ When another beam is inserted under the second bracket <part-num-ref name="second bracket">16,</part-num-ref>
310
+ the brackets 14,16 resist rotation relative to one another due to the interlocking nature of the brackets 14,16. In a similar manner, as the deck support brackets <part-num-ref name="deck support brackets">12</part-num-ref>
311
+ cooperate with either of the first or second brackets 14,16 as described above with reference to Figures <part-num-ref name="first or second brackets 14,16 as described above with reference to Figures">7</part-num-ref>
312
+ and <part-num-ref name="and">8.</part-num-ref>
313
+ </p>
314
+ <p id="p-48" num="48">[00035] Although the swing support bracket <part-num-ref name="swing support bracket">18</part-num-ref>
315
+ shown in Figure 5 does not have overlapping walls with one another, this bracket could be used with either of the frame brackets 14,15 shown in Figure 3 and Figure 4 or by itself as illustrated in Figure 1. By using the construction interlocking brackets or the swing support bracket <part-num-ref name="swing support bracket">18,</part-num-ref>
316
+ the weight load on the bracket tends to be applied to through sheer stresses on fasteners instead of on threads of a bolt through a single bore as is experienced through prior art drilled of beams connected with bolts and nuts. In testing, it has been discovered that the brackets of the present invention can support <part-num-ref name="present invention can support">4600</part-num-ref>
317
+ pounds of loan and are not the weak link. By utilizing these brackets, pre-drilling of holes in beams can be <boundary-data type="header">2071646_2.DOC 12</boundary-data>
318
+ <page-break num="13"/>
319
+ eliminated in many instances. This can result in a significant savings for the purchaser since appropriate length lumber can be relatively quickly assembled utilizing the brackets as shown and described herein. Assembly tools can be reduced to a drill or screwdriver and possibly a saw. </p>
320
+ <p id="p-49" num="49">[00036] Referring back to Figure 5, the positioning of the base <part-num-ref name="base">86</part-num-ref>
321
+ intermediate to beams as illustrated in Figure 1 with the side walls 92,94 connected to the swing support beam <part-num-ref name="swing support beam">82</part-num-ref>
322
+ and the low front and back walls 96,98 connected to the horizontal frame beam <part-num-ref name="horizontal frame beam">62</part-num-ref>
323
+ as shown in Figure 1. </p>
324
+ <p id="p-50" num="50">Resistance to rotation of the swing support beam <part-num-ref name="swing support beam">82</part-num-ref>
325
+ is established by the use of the swing support bracket <part-num-ref name="swing support bracket">18.</part-num-ref>
326
+ </p>
327
+ <p id="p-51" num="51">[00037] Accordingly, the use of either cooperating brackets or the swing support bracket is useful in providing rotation of joining beams. This is believed to be a significant advantage over the use of bolts through single bores at the ends of beams as is commonly utilized in the art.</p>
328
+ <p id="p-52" num="52">Most manufacturers that provide pre-drilled beams instruct owners to regularly tighten the nuts on bolts. Failure to regularly tighten these nuts could result in a nut becoming loose over time thereby allowing rotation of one beam relative to another. Since the load on the brackets shown in the structure are primarily distributed as sheer stress on the fasteners extending through the respective holes, there is no ability for the adjacent beams to rotate relative to one another even if the fasteners begin to back out over time which is extremely unlikely since the stress acts on the sheer of the fasteners.</p>
329
+ <p id="p-53" num="53">[00038<confidence value="5">]</confidence>
330
+ A preferable method of assembling playground equipment with a bracket system includes the steps of securing four horizontal deck support beams <part-num-ref name="steps of securing four horizontal deck support beams">22</part-num-ref>
331
+ to four vertical frame beams <part-num-ref name="to four vertical frame beams">24</part-num-ref>
332
+ at first points <part-num-ref name="at first points">26</part-num-ref>
333
+ along the vertical frame beams with eight deck support brackets <part-num-ref name="vertical frame beams with eight deck support brackets">12</part-num-ref>
334
+ and fasteners 52; connecting a middle support beam <part-num-ref name="middle support beam">23</part-num-ref>
335
+ to two opposing horizontal deck support <boundary-data type="header">2071646_2.DOC 13</boundary-data>
336
+ <page-break num="14"/>
337
+ beams <part-num-ref name="to two opposing horizontal deck support beams">22</part-num-ref>
338
+ underneath the deck <part-num-ref name="deck">32</part-num-ref>
339
+ with two deck support brackets <part-num-ref name="with two deck support brackets">12</part-num-ref>
340
+ and fasteners 52; attaching two vertical frame brackets <part-num-ref name="and fasteners 52; attaching two vertical frame brackets">14</part-num-ref>
341
+ to two adjacent vertical frame beams at second points <part-num-ref name="to two adjacent vertical frame beams at second points">54</part-num-ref>
342
+ along the vertical frame beams above the first points; fixing a horizontal frame beam <part-num-ref name="horizontal frame beam">68</part-num-ref>
343
+ to the two adjacent vertical frame beams at the second points with two horizontal frame brackets <part-num-ref name="second points with two horizontal frame brackets">16</part-num-ref>
344
+ and fasteners; interconnecting the two horizontal frame brackets and the two vertical frame brackets; </p>
345
+ <p id="p-54" num="54">fastening a swing support beam <part-num-ref name="swing support beam">82</part-num-ref>
346
+ to the horizontal frame beam at a third point <part-num-ref name="third point">84</part-num-ref>
347
+ along the horizontal frame beam with a swing bracket <part-num-ref name="swing bracket">18</part-num-ref>
348
+ and fasteners; connecting a ladder <part-num-ref name="ladder">102</part-num-ref>
349
+ to one of the horizontal deck support beams with two ladder brackets <part-num-ref name="horizontal deck support beams with two ladder brackets">20</part-num-ref>
350
+ and fasteners; and connecting a climbing wall <part-num-ref name="climbing wall">108</part-num-ref>
351
+ to another of the horizontal deck support beams with two additional ladder brackets and fasteners. </p>
352
+ <p id="p-55" num="55">[00039] A piece of playground equipment <part-num-ref name="piece of playground equipment">10</part-num-ref>
353
+ designed to be assembled with the bracket system of the present invention includes at least the following pieces: horizontal deck support beams <part-num-ref name="following pieces: horizontal deck support beams">22,</part-num-ref>
354
+ vertical frame beams <part-num-ref name="following pieces: horizontal deck support beams 22, vertical frame beams">24,</part-num-ref>
355
+ a deck <part-num-ref name="deck">32,</part-num-ref>
356
+ a horizontal frame beam <part-num-ref name="horizontal frame beam">68,</part-num-ref>
357
+ a swing support beam <part-num-ref name="swing support beam">82,</part-num-ref>
358
+ a ladder <part-num-ref name="ladder">102,</part-num-ref>
359
+ and the bracket system, which includes a plurality of deck support brackets, at least two vertical frame brackets, at least two horizontal frame brackets, a swing bracket, and at least two ladder brackets. Optionally, the piece of playground equipment <part-num-ref name="piece of playground equipment">10</part-num-ref>
360
+ also may include a climbing wall <part-num-ref name="climbing wall">108</part-num-ref>
361
+ and at least two additional ladder brackets. It is noted that the piece of playground equipment shown in Figure 1 is only one embodiment of playground equipment constructed with the present bracket system. Other styles of playground equipment <part-num-ref name="present bracket system. Other styles of playground equipment">10</part-num-ref>
362
+ assembled with the subject bracket system could include other or additional play units, designs, or modules while still falling within the scope of the present invention. As an example, Figure 2 depicts an alternate piece of playground equipment <part-num-ref name="alternate piece of playground equipment">10</part-num-ref>
363
+ assembled with the subject bracket system. </p>
364
+ <boundary-data type="header">2071646 2.DOC 14</boundary-data>
365
+ <p id="p-56" num="56">
366
+ <page-break num="15"/>
367
+ [00040] The bracket system of the present invention allows a piece of playground equipment <part-num-ref name="piece of playground equipment">10</part-num-ref>
368
+ to be assembled easily and quickly, without professional assistance. The modular nature of the various components and brackets of the present piece of playground equipment allows for easy transportation and storage. </p>
369
+ <p id="p-57" num="57">[00041] All patents referred to herein, are hereby incorporated herein by reference, whether or not specifically done so within the text of this disclosure.</p>
370
+ <p id="p-58" num="58">[00042] In the present disclosure, the words "a<confidence value="5">"</confidence>
371
+ or "an" are to be taken to include both the singular and the plural. Conversely, any reference to plural items shall, where appropriate, include the singular. </p>
372
+ <p id="p-59" num="59">[00043] From the foregoing it will be observed that numerous modifications and variations can be effectuated without departing from the true spirit and scope of the novel concepts of the present invention. It is to be understood that no limitation with respect to the specific embodiments illustrated is intended or should be inferred. The disclosure is intended to cover by the appended claims all such modifications as fall within the scope of the claims.</p>
373
+ <boundary-data type="header">2071646_2.DOC 15</boundary-data>
374
+ </description>
375
+ </us-patent-application>
376
+
prior_art/11097034.xml ADDED
@@ -0,0 +1,29 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11097034</doc-number>
8
+ <date>2008-08-18</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <heading id="h-1">AMENDMENTS TO THE SPECIFICATION</heading>
14
+ <p id="p-1" num="1">Please AMEND paragraph [0002] at page 1, as follows [0002] This application is related to: (i) U.S. Application No. 11/097<confidence value="5">,</confidence>
15
+ 591 <confidence value="55">..</confidence>
16
+ <confidence value="5554">APLi</confidence>
17
+ , filed concurrently, and entitled "MEDIA MANAGEMENT FOR GROUPS OF MEDIA ITEMS," which is hereby incorporated herein by reference; (ii) U.S. Application No. 10/973,925, filed October 25, 2004, and entitled "MULTIPLE MEDIA TYPE SYNCHRONIZATION BETWEEN HOST COMPUTER AND MEDIA DEVICE," which is hereby incorporated herein by reference; (iii) U.S. Patent Application No. 10/833,879, filed April 27, 2004, and entitled "METHOD AND SYSTEM FOR SHARING PLAYLISTS," which is hereby incorporated by reference herein; (iv) U.S. Patent Application No. </p>
18
+ <p id="p-2" num="2">10/833,399, filed April 27, 2004, and entitled "METHOD AND SYSTEM FOR CONFIGURABLE AUTOMATIC MEDIA SELECTION," which is hereby incorporated by reference herein; (v) U.S. Patent Application No. 10/277,418, filed October 21, 2002, and entitled "INTELLIGENT INTERACTION BETWEEN MEDIA PLAYER AND HOST COMPUTER," which is hereby incorporated herein by reference; (vi) U.S. Patent Application No. 10/198,639, filed July 16, 2002, and entitled "METHOD AND SYSTEM FOR UPDATING PLAYLISTS," which is hereby incorporated by reference herein; and (vii) U.S. Patent Application No. 10/118,069, filed April 5, 2002, and entitled "INTELLIGENT SYNCHRONIZATION OF MEDIA PLAYER WITH HOST COMPUTER," which is hereby incorporated herein by reference.</p>
19
+ <boundary-data type="header">11/097,034 2</boundary-data>
20
+ <p id="p-3" num="3">
21
+ <page-break num="2"/>
22
+ Please AMEND paragraph [0080] at page 21, as follows [0080] The invention is preferably implemented by software, but can also be implemented in hardware or a combination of hardware and software. The invention can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data which can thereafter be read by a computer system. Examples of the computer readable medium include read-only memory, random-access memory, <confidence value="5">C</confidence>
23
+ D-ROMs, DVDs, magnetic tape, and optical data storage devices<confidence value="6">,</confidence>
24
+ <confidence value="86625885">and-carr</confidence>
25
+ ier waves. The computer readable medium can also be distributed over network-coupled computer systems so that the computer readable code is stored and executed in a distributed fashion. </p>
26
+ <boundary-data type="header">11/097,034 3</boundary-data>
27
+ </description>
28
+ </us-patent-application>
29
+
prior_art/11102007.xml ADDED
@@ -0,0 +1,284 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11102007</doc-number>
8
+ <date>2005-04-08</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <boundary-data type="header">60,246-450; 11,047</boundary-data>
14
+ <heading id="h-1">REFRIGERANT SYSTEM WITH VARIABLE SPEED</heading>
15
+ <heading id="h-2">COMPRESSOR AND REHEAT FUNCTION</heading>
16
+ <heading id="h-3">BACKGROUND OF THE INVENTION</heading>
17
+ <p id="p-1" num="1">[0001] This invention relates to a variable speed motor for a compressor that is incorporated into a refrigerant system with a reheat function.</p>
18
+ <p id="p-2" num="2">[0002] Refrigerant systems are utilized in many applications such as to condition an environment. Air conditioners and heat pumps are used to cool and/or heat the air entering an environment. The cooling or heating load on the environment may change with ambient conditions, and as the temperature and/or humidity levels demanded by an occupant of the building vary. Obviously, the refrigerant system operation and control have to adequately reflect these changes to maintain stable temperature and humidity conditions within the environment.</p>
19
+ <p id="p-3" num="3">[0003] In some cases, while the system is operating in a cooling mode, the temperature level of the indoor air stream to provide a comfortable environment in a conditioned space may need to be higher than the temperature that would provide the ideal humidity level. On the other hand, lower the temperature of the air stream, more moisture can be removed from the air. These contradicting trends presented challenges to refrigerant system designers. One way to address such challenges is to utilize various schematics incorporating reheat coils. In many cases, a reheat coil placed on the indoor air path downstream of the evaporator is employed for the purposes of reheating the air supplied to the conditioned space, after it has been cooled in the evaporator, and where the moisture has been removed.</p>
20
+ <boundary-data type="header">
21
+ <confidence value="8">1</confidence>
22
+ </boundary-data>
23
+ <boundary-data type="header">60,246-450; 11,047</boundary-data>
24
+ <p id="p-4" num="4">
25
+ <page-break num="2"/>
26
+ [0004] In the prior art, controls can be programmed to optionally actuate the reheat function. However, the humidity control provided by the reheat circuit is increased or decreased in steps. It would be desirable to provide the ability to vary the humidity control between these discrete steps. </p>
27
+ <p id="p-5" num="5">[0005] In the past, attempts have been made to apply modulation or pulsation techniques to split and regulate refrigerant flow between a main circuit and a reheat branch.</p>
28
+ <p id="p-6" num="6">These approaches have not been found to be robust, and have strict limitations regarding their application range.</p>
29
+ <p id="p-7" num="7">[0006] Variable speed drives are known for driving compressors at a variable speed in a refrigerant system. By driving the compressor at a higher or lower speed, the amount of refrigerant that is compressed changes, and thus effecting operational characteristics and system capacity.</p>
30
+ <p id="p-8" num="8">[0007] Generally speaking, variable speed drives have not been utilized in refrigerant systems incorporating a reheat function for continuous dehumidification capability adjustment, and specifically in the refrigerant systems with variable sensible heat ratios.</p>
31
+ <p id="p-9" num="9">Thus, refrigerant systems that have incorporated a reheat function have been limited, in general, to providing the humidity control in discrete steps or over a narrow range of operating parameters.</p>
32
+ <heading id="h-4">SUMMARY OF T<confidence value="5">H</confidence>
33
+ E INVENTION </heading>
34
+ <p id="p-10" num="10">[0008] In a disclosed embodiment of this invention, a variable speed drive compressor is provided in a refrigerant system with a reheat circuit. By selectively utilizing the reheat circuit, the refrigerant system can provide better humidity control. Further, by <boundary-data type="header">
35
+ <confidence value="8">2</confidence>
36
+ </boundary-data>
37
+ <page-break num="3"/>
38
+ <boundary-data type="header">60,246-450; 11,047</boundary-data>
39
+ varying the speed of the compressor motor, humidity control below and above the step provided by the reheat circuit can be achieved. </p>
40
+ <p id="p-11" num="11">[0009] A control identifies a desired humidity level, and then achieves this desired level by first actuating the reheat circuit if enhanced dehumidification is desired, or not actuating the reheat circuit, and then determining a desired variable speed for achieving that exact humidity level. In one simplified method, the variable speed is adjusted incrementally, and the humidity control provided is monitored. When the desired level is reached, then the system operates at that new speed. If the humidity still needs to be adjusted, then the motor speed is adjusted in another incremental step.</p>
41
+ <p id="p-12" num="12">[0010] By providing the variable speed drive in combination with the reheat circuit, the present invention achieves the desired humidity level and control. Other design features, such as a condenser bypass and variable speed fans, to achieve variable sensible heat ratios, can be employed in combination with a variable speed compressor as well.</p>
42
+ <p id="p-13" num="13">[0011] Another embodiment incorporates an economizer function along with the reheat circuit and a variable speed drive compressor. This combination provides additional flexibility in system operation and humidity control.</p>
43
+ <p id="p-14" num="14">[0012] These and other features of the present invention can be best understood from the following specification and drawings, the following of which is a brief description.</p>
44
+ <heading id="h-5">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
45
+ <p id="p-15" num="15">[0013] Figure <confidence value="2">1</confidence>
46
+ A shows a first embodiment refrigerant system. </p>
47
+ <p id="p-16" num="16">[0014] Figure <confidence value="5">1</confidence>
48
+ B shows an option that would apply to any of the embodiments in this application. </p>
49
+ <boundary-data type="header">
50
+ <confidence value="8">3</confidence>
51
+ </boundary-data>
52
+ <boundary-data type="header">60,246-450; 11,047</boundary-data>
53
+ <p id="p-17" num="17">
54
+ <page-break num="4"/>
55
+ [0015] Figure 2 shows a second embodiment refrigerant system. </p>
56
+ <p id="p-18" num="18">[0016] Figure 3A shows a third embodiment refrigerant system.</p>
57
+ <p id="p-19" num="19">[0017] Figure 3B shows an alternative schematic.</p>
58
+ <p id="p-20" num="20">[0018] Figure 3C shows an alternative schematic.</p>
59
+ <p id="p-21" num="21">[0019] Figure 4 shows the humidity control provided by the prior art.</p>
60
+ <p id="p-22" num="22">[0020] Figure 5 shows the humidity control provided by the present invention.</p>
61
+ <p id="p-23" num="23">[0021] Figure 6 is a flowchart of a control algorithm according to the present invention.</p>
62
+ <heading id="h-6">DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT</heading>
63
+ <p id="p-24" num="24">[0022] A refrigerant system <part-num-ref name="refrigerant system">20</part-num-ref>
64
+ is illustrated in Figure <confidence value="5">1</confidence>
65
+ A having a compressor <part-num-ref name="compressor">22</part-num-ref>
66
+ provided with a control including a variable speed drive <part-num-ref name="variable speed drive">44.</part-num-ref>
67
+ It should be noted, that the terms "variable speed drive" and "variable frequency drive" have identical meaning within the scope of present invention and will be used interchangeably throughout the text. As is known, a motor for the compressor <part-num-ref name="compressor">22</part-num-ref>
68
+ can be driven at a variety of speeds such that the amount of refrigerant compressed by the compressor <part-num-ref name="compressor">22</part-num-ref>
69
+ per unit of time can be varied. </p>
70
+ <p id="p-25" num="25">[0023] As shown in Figure <confidence value="5">1</confidence>
71
+ B, while a single compressor may be utilized, multi- stage compressors <part-num-ref name="single compressor may be utilized, multi- stage compressors">222</part-num-ref>
72
+ and <part-num-ref name="and">322</part-num-ref>
73
+ may be employed as well. As is known, by utilizing staged compressors, a refrigerant system designer is provided with even more options and control. </p>
74
+ <p id="p-26" num="26">The variable speed drive 44 is shown communicating with one of the compressors <part-num-ref name="compressors">(222)</part-num-ref>
75
+ although it is also shown as optionally controlling both. </p>
76
+ <boundary-data type="header">
77
+ <confidence value="8">4</confidence>
78
+ </boundary-data>
79
+ <boundary-data type="header">60,246-450; 11,047</boundary-data>
80
+ <p id="p-27" num="27">
81
+ <page-break num="5"/>
82
+ [0024] As further shown in Figure <confidence value="2">1</confidence>
83
+ A, variable speed drives 144 may be associated with the fans <part-num-ref name="fans">40</part-num-ref>
84
+ and <part-num-ref name="and">47.</part-num-ref>
85
+ A worker in this art would recognize when variable control over these fan motors would be beneficial. </p>
86
+ <p id="p-28" num="28">[0025] Refrigerant compressed by the compressor <part-num-ref name="compressor">22</part-num-ref>
87
+ is passed to an outdoor heat exchanger <part-num-ref name="outdoor heat exchanger">24,</part-num-ref>
88
+ which would be the condenser in a cooling mode. Fan <part-num-ref name="cooling mode. Fan">47</part-num-ref>
89
+ moves air over the heat exchanger <part-num-ref name="heat exchanger">24</part-num-ref>
90
+ to provide heat exchange with the refrigerant to condense and then subcool the refrigerant. An expansion device <part-num-ref name="expansion device">36</part-num-ref>
91
+ is located downstream of the condenser <part-num-ref name="condenser">24,</part-num-ref>
92
+ and an evaporator <part-num-ref name="evaporator">38</part-num-ref>
93
+ is located downstream of the expansion device <part-num-ref name="expansion device">36.</part-num-ref>
94
+ As shown, a fan <part-num-ref name="fan">40</part-num-ref>
95
+ moves air over the evaporator <part-num-ref name="evaporator">38</part-num-ref>
96
+ to cool and dehumidify the air delivered to a conditioned space. </p>
97
+ <p id="p-29" num="29">[0026] A three-way valve <part-num-ref name="three-way valve">28</part-num-ref>
98
+ selectively routes refrigerant from a location intermediate the expansion device <part-num-ref name="expansion device">36</part-num-ref>
99
+ and condenser <part-num-ref name="and condenser">24,</part-num-ref>
100
+ and through a reheat heat exchanger <part-num-ref name="reheat heat exchanger">30.</part-num-ref>
101
+ This refrigerant is passed through a check valve <part-num-ref name="check valve">32</part-num-ref>
102
+ and returned to a main circuit at a point <part-num-ref name="point">34</part-num-ref>
103
+ upstream of the expansion device <part-num-ref name="expansion device">36</part-num-ref>
104
+ and downstream of the three-way valve <part-num-ref name="three-way valve">28.</part-num-ref>
105
+ </p>
106
+ <p id="p-30" num="30">[0027] As is known, when it is desired to have enhanced humidity control, the three-way valve <part-num-ref name="three-way valve">28</part-num-ref>
107
+ is moved to route refrigerant through the reheat coil <part-num-ref name="reheat coil">30,</part-num-ref>
108
+ and back to the return point <part-num-ref name="return point">34.</part-num-ref>
109
+ Now, the air blown by the fan <part-num-ref name="fan">40</part-num-ref>
110
+ and passing over the evaporator <part-num-ref name="evaporator">38</part-num-ref>
111
+ may be cooled to a temperature below that which is desired by an occupant of the space conditioned by the refrigerant system <part-num-ref name="refrigerant system">20.</part-num-ref>
112
+ The air at that point has extra moisture removed, since its temperature has been decreased due to heat transfer interaction with the refrigerant in the evaporator <part-num-ref name="evaporator">38.</part-num-ref>
113
+ That air is then passed over the reheat coil <part-num-ref name="reheat coil">30,</part-num-ref>
114
+ which heats the air back up to approach the desired temperature. Again, the reheat function is known in the prior art. It is the provision of such a reheat function in combination with a variable speed compressor that is inventive here. </p>
115
+ <boundary-data type="header">
116
+ <confidence value="8">5</confidence>
117
+ </boundary-data>
118
+ <boundary-data type="header">60,246-450; 11,047</boundary-data>
119
+ <p id="p-31" num="31">
120
+ <page-break num="6"/>
121
+ [0028] An additional feature of the reheat circuit shown in Figure <confidence value="5">1</confidence>
122
+ A is an ability to obtain variable sensible heat ratios provided by a bypass line <part-num-ref name="bypass line">21</part-num-ref>
123
+ having a valve <part-num-ref name="valve">122</part-num-ref>
124
+ to selectively bypass at least a portion of refrigerant around the condenser <part-num-ref name="condenser">24.</part-num-ref>
125
+ A valve <part-num-ref name="valve">26</part-num-ref>
126
+ is operated in conjunction with the valve <part-num-ref name="valve">122.</part-num-ref>
127
+ Should considerably less cooling, 'but still significant dehumidification be desired in the space conditioned by the refrigerant system <part-num-ref name="refrigerant system">20,</part-num-ref>
128
+ then the bypass line <part-num-ref name="bypass line">21</part-num-ref>
129
+ may be opened to bypass at least a portion of refrigerant through the valve <part-num-ref name="valve">122</part-num-ref>
130
+ and around the condenser <part-num-ref name="condenser">24.</part-num-ref>
131
+ The refrigerant reaching the evaporator <part-num-ref name="evaporator">36</part-num-ref>
132
+ will thus have lower cooling potential than would be the case if it all had passed through the condenser <part-num-ref name="condenser">24</part-num-ref>
133
+ and been cooled. At the same time, the refrigerant passing through the reheat heat exchanger <part-num-ref name="reheat heat exchanger">30</part-num-ref>
134
+ will have higher heating potential. Consequently, the reheat function will allow removal of extra moisture from air supplied to the conditioned space without overcooling the space. This provides the sensible heat ratio required by an occupant of the conditioned space. </p>
135
+ <p id="p-32" num="32">A worker of ordinary skill in the art would recognize how to use this design feature.</p>
136
+ <p id="p-33" num="33">[0029] Figure 2 shows an alternate embodiment refrigerant system <part-num-ref name="alternate embodiment refrigerant system">120,</part-num-ref>
137
+ wherein the compressor <part-num-ref name="compressor">22</part-num-ref>
138
+ is provided with a variable speed drive control <part-num-ref name="variable speed drive control">44.</part-num-ref>
139
+ As in Figure 1, a condenser <part-num-ref name="condenser">46</part-num-ref>
140
+ has a fan <part-num-ref name="fan">47</part-num-ref>
141
+ for blowing air over the condenser <part-num-ref name="condenser">46.</part-num-ref>
142
+ Also, as before, an expansion device <part-num-ref name="expansion device">48</part-num-ref>
143
+ and an evaporator <part-num-ref name="evaporator">50</part-num-ref>
144
+ having a fan <part-num-ref name="fan">52</part-num-ref>
145
+ are located further downstream in the refrigerant circuit. </p>
146
+ <p id="p-34" num="34">[0030] A reheat function is provided by a three-way valve <part-num-ref name="three-way valve">54</part-num-ref>
147
+ by selectively routing refrigerant from a location upstream of the condenser <part-num-ref name="condenser">46,</part-num-ref>
148
+ passing it through a reheat coil <part-num-ref name="reheat coil">56</part-num-ref>
149
+ and a check valve <part-num-ref name="check valve">59</part-num-ref>
150
+ and returning it to a main circuit at a point <part-num-ref name="point">58,</part-num-ref>
151
+ all located upstream of the condenser <part-num-ref name="condenser">56.</part-num-ref>
152
+ A refrigerant system designer would recognize when this system would operate similarly to the schematics illustrated in Figure <confidence value="288">1A.</confidence>
153
+ </p>
154
+ <boundary-data type="header">
155
+ <confidence value="8">6</confidence>
156
+ </boundary-data>
157
+ <boundary-data type="header">60,246-450; 11,047</boundary-data>
158
+ <p id="p-35" num="35">
159
+ <page-break num="7"/>
160
+ [0031] Figure 3A shows a distinct embodiment of a refrigerant system, and with additional features. In particular, system design known as an economizer cycle is incorporated into the schematic. The economizer cycle combined with the reheat function provides even more flexibility in operation and control. Although the reheat heat exchanger is shown in series with the condenser in Figures <confidence value="2">1</confidence>
161
+ A and <part-num-ref name="condenser in Figures 1A and">2,</part-num-ref>
162
+ and is shown in parallel to the condenser in Figure 3A, either arrangement is equally applicable and feasible. Further variations in the location of the tap for the reheat coil in relation to the condenser and economizer heat exchanger may also be utilized. As an example, the reheat coil may receive refrigerant from a tap located downstream of the condenser, rather than the upstream location as shown in Figure 3. Figures 1-3 are merely intended in combination to show that many reheat schemes can be utilized with the present invention. </p>
163
+ <p id="p-36" num="36">[0032] Figure 3A shows embodiment 89, wherein the three-way valve <part-num-ref name="three-way valve">90</part-num-ref>
164
+ is positioned upstream of the condenser <part-num-ref name="condenser">94.</part-num-ref>
165
+ When the reheat branch is in operation, refrigerant passes through the reheat coil <part-num-ref name="reheat coil">92,</part-num-ref>
166
+ and may bypass the condenser <part-num-ref name="condenser">94,</part-num-ref>
167
+ which may be maintained in an inactive mode. A check valve <part-num-ref name="check valve">110</part-num-ref>
168
+ and a return point <part-num-ref name="return point">96</part-num-ref>
169
+ to the main cycle are shown downstream of the reheat coil <part-num-ref name="reheat coil">92.</part-num-ref>
170
+ If an economizer expansion device <part-num-ref name="economizer expansion device">100</part-num-ref>
171
+ is open, a portion of refrigerant is rerouted through a tap line <part-num-ref name="tap line">98,</part-num-ref>
172
+ economizer expansion device <part-num-ref name="tap line 98, economizer expansion device">100,</part-num-ref>
173
+ economizer heat exchanger <part-num-ref name="tap line 98, economizer expansion device 100, economizer heat exchanger">102</part-num-ref>
174
+ and return line <part-num-ref name="and return line">106</part-num-ref>
175
+ to the economizer port of the compressor <part-num-ref name="compressor">22.</part-num-ref>
176
+ A main refrigerant flow in a liquid line <part-num-ref name="liquid line">104</part-num-ref>
177
+ also passes through the economizer heat exchanger <part-num-ref name="economizer heat exchanger">102</part-num-ref>
178
+ where heat transfer interaction between the two refrigerant flows (liquid high pressure refrigerant in the main loop and lower pressure refrigerant in the economizer branch) is taking place. In this embodiment, the condenser may be bypassed entirely by the <boundary-data type="header">
179
+ <confidence value="8">7</confidence>
180
+ </boundary-data>
181
+ <page-break num="8"/>
182
+ <boundary-data type="header">60,246-450; 11,047</boundary-data>
183
+ refrigerant flow through the reheat coil <part-num-ref name="reheat coil">92.</part-num-ref>
184
+ The tap line <part-num-ref name="tap line">98</part-num-ref>
185
+ may be positioned downstream of the economizer heat exchanger <part-num-ref name="economizer heat exchanger">102</part-num-ref>
186
+ as well. </p>
187
+ <p id="p-37" num="37">[0033] Although the two flows <part-num-ref name="two flows">98</part-num-ref>
188
+ and <part-num-ref name="and">104</part-num-ref>
189
+ are shown flowing through the economizer heat exchanger <part-num-ref name="economizer heat exchanger">102</part-num-ref>
190
+ in the same direction in Figure 3A, this is merely to simplify the illustration. In practice, it is generally preferred to have the two flows flowing through the economizer heat exchanger <part-num-ref name="economizer heat exchanger">102</part-num-ref>
191
+ in a counter-flow arrangement. The refrigerant in the tap line <part-num-ref name="tap line">98</part-num-ref>
192
+ subcools the refrigerant in the main line <part-num-ref name="main line">104,</part-num-ref>
193
+ such that after passing through the expansion device <part-num-ref name="expansion device">36,</part-num-ref>
194
+ it will have a higher cooling potential in the evaporator <part-num-ref name="evaporator">108.</part-num-ref>
195
+ Fan <part-num-ref name="evaporator 108. Fan">52</part-num-ref>
196
+ moves air to be conditioned over the evaporator <part-num-ref name="evaporator">108.</part-num-ref>
197
+ From the evaporator <part-num-ref name="evaporator">108,</part-num-ref>
198
+ the refrigerant returns to a suction line leading back to the compressor <part-num-ref name="compressor">22.</part-num-ref>
199
+ The refrigerant from the tap line <part-num-ref name="tap line">98</part-num-ref>
200
+ passes through a return line <part-num-ref name="return line">106</part-num-ref>
201
+ to an intermediate compression point in the compressor <part-num-ref name="compressor">22.</part-num-ref>
202
+ It should be understood that the economizer expansion device <part-num-ref name="economizer expansion device">100</part-num-ref>
203
+ also preferably includes a shut-off device, or a separate shut-off device is provided. </p>
204
+ <p id="p-38" num="38">[0034] The economizer cycle may or may not be engaged. To turn off the economizer cycle, the economizer expansion device <part-num-ref name="economizer expansion device">100</part-num-ref>
205
+ may be closed such that no refrigerant is supplied to the tap line <part-num-ref name="tap line">98.</part-num-ref>
206
+ Similarly, to turn off the reheat coil, the three-way valve <part-num-ref name="three-way valve">90</part-num-ref>
207
+ may be moved to such a position that no refrigerant is routed through the reheat coil <part-num-ref name="reheat coil">92.</part-num-ref>
208
+ Thus, either of these two functions may be utilized independent of the other, or neither could be used. The present invention is mainly directed to providing the ability to use both techniques in combination with each other, while providing a better control over the humidity and temperature and along with the variable speed compressor <part-num-ref name="variable speed compressor">22.</part-num-ref>
209
+ Also, it has to be understood that the three-way valve <part-num-ref name="three-way valve">90</part-num-ref>
210
+ can be substituted by a pair of conventional valves <boundary-data type="header">
211
+ <confidence value="8">8</confidence>
212
+ </boundary-data>
213
+ <page-break num="9"/>
214
+ <boundary-data type="header">60,246-450; 11,047</boundary-data>
215
+ and if the expansion device is of such a type that it cannot be closed down completely, an additional shutoff valve may be placed on the tap line <part-num-ref name="tap line">98.</part-num-ref>
216
+ </p>
217
+ <p id="p-39" num="39">[0035] When low humidity temperature level is desired in the air stream to be supplied to a conditioned space, along with the capability to provide a significant amount of latent capacity, both economizer expansion device <part-num-ref name="significant amount of latent capacity, both economizer expansion device">100</part-num-ref>
218
+ and the three-way valve <part-num-ref name="three-way valve">90</part-num-ref>
219
+ are moved to an open position to operate both the economizer heat exchanger <part-num-ref name="economizer heat exchanger">102</part-num-ref>
220
+ and the reheat coil <part-num-ref name="reheat coil">92.</part-num-ref>
221
+ </p>
222
+ <p id="p-40" num="40">Refrigerant passing through the main line <part-num-ref name="main line">104</part-num-ref>
223
+ will be subcooled by the refrigerant from the tap line <part-num-ref name="tap line">98.</part-num-ref>
224
+ Thus, that refrigerant will have a higher cooling potential (to achieve higher sensible and latent capacity) when reaching the evaporator <part-num-ref name="evaporator">108.</part-num-ref>
225
+ Consequently, an air stream provided by the fan <part-num-ref name="fan">52</part-num-ref>
226
+ can be supplied at a lower temperature and humidity (since at this lower temperature more moisture can be removed from the air), at the exit of the evaporator <part-num-ref name="evaporator">108</part-num-ref>
227
+ of the refrigerant system <part-num-ref name="refrigerant system">89.</part-num-ref>
228
+ This cooled and dehumidified air then passes over the reheat coil <part-num-ref name="reheat coil">92,</part-num-ref>
229
+ which will have hot high pressure refrigerant, as it is positioned upstream of the main expansion device <part-num-ref name="main expansion device">36.</part-num-ref>
230
+ This refrigerant will reheat the air to the desired temperature, while the moisture content in the air doesn't change. Thus, by utilizing the combination of the economizer cycle and reheat coil, a refrigerant system designer is able to achieve both desired temperature and humidity levels. Moreover, the higher efficiency levels are achieved due to implementation of the economizer cycle concept. </p>
231
+ <p id="p-41" num="41">[0036] Figure 3A shows an alternative schematic <part-num-ref name="alternative schematic">180</part-num-ref>
232
+ wherein a three-way valve <part-num-ref name="three-way valve">190</part-num-ref>
233
+ selectively directs refrigerant to an economizer heat exchanger <part-num-ref name="economizer heat exchanger">192</part-num-ref>
234
+ and then serially to a reheat heat exchanger <part-num-ref name="reheat heat exchanger">196.</part-num-ref>
235
+ As before, refrigerant returns to the main refrigerant circuit through a check valve <part-num-ref name="check valve">198.</part-num-ref>
236
+ This schematic illustrates that a reheat coil can be positioned in series with the economizer heat exchanger, and downstream of the economizer heat <boundary-data type="header">
237
+ <confidence value="8">9</confidence>
238
+ </boundary-data>
239
+ <page-break num="10"/>
240
+ <boundary-data type="header">60,246-450; 11,047</boundary-data>
241
+ exchanger. The earlier embodiment shows the reheat coil positioned although in series but upstream of the economizer heat exchanger. A worker in this art would recognize when each alternative might be most beneficial. </p>
242
+ <p id="p-42" num="42">[0037] Figure 3C shows yet another embodiment 210. In this embodiment, a three-way valve <part-num-ref name="three-way valve">200</part-num-ref>
243
+ selectively directs the refrigerant in a parallel flow pattern to the economizer heat exchanger <part-num-ref name="economizer heat exchanger">202</part-num-ref>
244
+ and to the reheat coil <part-num-ref name="reheat coil">204.</part-num-ref>
245
+ Again, a worker in this art would recognize when a parallel flow arrangement would be more beneficial than a serial configuration. </p>
246
+ <p id="p-43" num="43">[0038] Again, the Figures <confidence value="5">1</confidence>
247
+ A, <confidence value="4">1</confidence>
248
+ B, <part-num-ref name="Figures 1A, 1B,">2,</part-num-ref>
249
+ 3A, 3B and 3C are merely an attempt to show possible reheat options. There is a large number of reheat circuit arrangements and configurations that may be utilized with the present invention. A decision on the particular reheat design concept and relative position of the reheat coil and economizer heat exchanger should be properly evaluated against specific application requirements and may have various degree of flexibility. </p>
250
+ <p id="p-44" num="44">[0039] A control <part-num-ref name="control">44</part-num-ref>
251
+ for either refrigerant cycle <part-num-ref name="for either refrigerant cycle">20,</part-num-ref>
252
+ <part-num-ref name="for either refrigerant cycle 20,">120,</part-num-ref>
253
+ <part-num-ref name="for either refrigerant cycle 20, 120,">89,</part-num-ref>
254
+ <part-num-ref name="for either refrigerant cycle 20, 120, 89,">180</part-num-ref>
255
+ and <part-num-ref name="and">210</part-num-ref>
256
+ is able to identify sensible and latent capacity required to provide desired temperature and humidity levels, and operate the reheat function and/or the economizer function as necessary. Thus, as shown in Figure 4, the prior art provided varying stages A, B, and C of humidity control. </p>
257
+ <p id="p-45" num="45">However, as can be seen, there are several values between values A, B, and C that cannot be provided by this prior art system. This is, of course, an oversimplification of the system, yet this does provide a good basis for understanding the present invention.</p>
258
+ <p id="p-46" num="46">[0040] For instance, in the Figure 3A system, which includes a variable speed drive for its compressor motor, there are an infinite number of capacities provided between <boundary-data type="header">
259
+ <confidence value="88">10</confidence>
260
+ </boundary-data>
261
+ <page-break num="11"/>
262
+ <boundary-data type="header">60,246-450; 11,047</boundary-data>
263
+ the base values A, B, and C, as shown in Figure 5. Thus, as shown in Figure 5, by reducing the speed of the compressor after the reheat function is activated, a ramp R downwardly toward nor<confidence value="8">m</confidence>
264
+ al capacity can be provided. By increasing the speed of the motor when the reheat function is activated, another ramp R can be provided. At some point, operating both economizer and reheat functions makes more sense than increasing the compressor speed. </p>
265
+ <p id="p-47" num="47">The decision of switching between modes of operation is usually based on system efficiency and component reliability but also can employ another system characteristic or a combination of those as criteria. Similarly, another ramp R can be provided between the reheat function and the economizer and reheat combined function by either ramping up the speed in the reheat mode of operation, or reducing the speed in the reheat and economizer mode of operation. A final ramp R is provided by increasing motor speed while operating the system with both reheat and economizer functions activated when even greater dehumidification is desired. A worker of ordinary skill in the art would recognize when any one of these functions would be desirable. The Figures <confidence value="2">L</confidence>
266
+ A and <part-num-ref name="Figures LA and">2</part-num-ref>
267
+ systems provide similar additional control features between stages A and B. </p>
268
+ <p id="p-48" num="48">[0041] Figure 6 shows how the ramps would typically be achieved with a standard variable speed motor control as is known in the prior art. Ramps R as shown in Figure 5 are an oversimplification. In fact, the control typically moves in incremental steps (that may be uneven and depend on the control logic), and then monitors the operation of the refrigerant cycle after that incremental change. Thus, there would be a plurality of step changes along each ramp R, rather than the infinite number of changes as is illustrated in Figure 5.</p>
269
+ <p id="p-49" num="49">However, Figure 5 does provide a good illustration of the power of the present invention to provide adjustable dehumidification capability.</p>
270
+ <boundary-data type="header">
271
+ <confidence value="88">11</confidence>
272
+ </boundary-data>
273
+ <boundary-data type="header">60,246-450; 11,047</boundary-data>
274
+ <p id="p-50" num="50">
275
+ <page-break num="12"/>
276
+ [0042] It has to be noted that variable speed compressors may be used in combination with variable speed fans to enhance system operation and control even further. </p>
277
+ <p id="p-51" num="51">Also, a variable speed compressor can be utilized in the conventional mode of operation as well to control temperature and thus humidity within a relatively narrow range, as known in the prior art.</p>
278
+ <p id="p-52" num="52">[0043] Although preferred embodiments of this invention has been disclosed, a worker of ordinary skill in this art would recognize that certain modifications would come within the scope of this invention. For that reason, the following claims should be studied to determine the true scope and content of this invention.</p>
279
+ <boundary-data type="header">
280
+ <confidence value="88">12</confidence>
281
+ </boundary-data>
282
+ </description>
283
+ </us-patent-application>
284
+
prior_art/11103971.xml ADDED
@@ -0,0 +1,325 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11103971</doc-number>
8
+ <date>2005-04-12</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <heading id="h-1">EXPRESS MAIL MAILING LABEL NO:</heading>
14
+ <p id="p-1" num="1">162615 <confidence value="11">E1</confidence>
15
+ <confidence value="11">ff</confidence>
16
+ <confidence value="288">f//</confidence>
17
+ <confidence value="1111">_iQQ</confidence>
18
+ DATE<confidence value="5">:</confidence>
19
+ <confidence value="1">4</confidence>
20
+ <confidence value="12">e/</confidence>
21
+ <confidence value="51">/2</confidence>
22
+ <confidence value="14">2s</confidence>
23
+ </p>
24
+ <heading id="h-2">ELECTROCHEMICAL CELL STRUCTURE</heading>
25
+ <heading id="h-3">STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH &amp;</heading>
26
+ <heading id="h-4">DEVELOPMENT</heading>
27
+ <p id="p-2" num="2">[0001] This invention was conceived or first reduced to practice under a project funded by the Department of Energy under contract DE-FC36-04<confidence value="55">G0</confidence>
28
+ 14223. The United States Government has certain rights related to this invention. </p>
29
+ <heading id="h-5">BACKGROUND</heading>
30
+ <p id="p-3" num="3">[0002] The invention relates generally to electrochemical cell structures and more specifically to electrochemical cell structures having single-piece nonconductive frames that support the anode, the cathode and the electrolyte and define flowpaths for working fluids and for byproducts of ionic exchange.</p>
31
+ <p id="p-4" num="4">[0003] Electrochemical cells are energy conversion devices that are usually classified as either electrolysis cells or fuel cells. Electrolysis cells can function as hydrogen generators by electrolytically decomposing water to produce hydrogen and oxygen gases. Fuel cells electrochemically react a hydrogen gas with an oxidant across an exchange membrane or electrolyte to generate electricity and produce water.</p>
32
+ <p id="p-5" num="5">[0004] Alkaline electrolysis systems have been commercially available for several decades. Direct current voltage of about 1.7V to about 2.2V is applied to two electrodes that are positioned within a liquid electrolyte. At the positive electrode, oxygen is produced and at the negative electrode, hydrogen forms. An ion-permeable diaphragm keeps the gases separated.</p>
33
+ <p id="p-6" num="6">[0005] For electrochemical systems, especially alkaline electrolysis systems, to become economically feasible the manufacturing costs associated with these systems must markedly improve. Current systems require numerous process steps during assembly, with each step adding cost to the overall system. Additionally, conventional systems currently have many individual component parts including <boundary-data type="header">
34
+ <confidence value="8">1</confidence>
35
+ </boundary-data>
36
+ <page-break num="2"/>
37
+ <boundary-data type="header">162615</boundary-data>
38
+ multiple electrodes, diaphragms, gaskets, bolts and other miscellaneous parts that add to the complexity of the system assembly and drive the manufacturing costs up. </p>
39
+ <p id="p-7" num="7">[0006] Accordingly, there is a need for an improved electrochemical cell that promotes an overall reduction in the number of component parts and simplifies the associated manufacturing and fabrication process.</p>
40
+ <heading id="h-6">BRIEF DESCRIPTION</heading>
41
+ <p id="p-8" num="8">[0007] An electrochemical cell structure comprises an anode, a cathode spaced apart from the anode and an electrolyte in ionic communication with each of the cathode and the anode. A single-piece nonconductive frame supports each of the anode, the cathode and the electrolyte and defines flowpaths for working fluids and for byproducts of ionic exchange.</p>
42
+ <heading id="h-7">DRAWINGS</heading>
43
+ <p id="p-9" num="9">[0008] These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:</p>
44
+ <p id="p-10" num="10">[0009] FIG. 1 is a side cross-sectional view of one embodiment of the instant invention.</p>
45
+ <p id="p-11" num="11">[0010] FIG. 2 is a schematic representation of an alkaline electrolysis system.</p>
46
+ <p id="p-12" num="12">[0011<confidence value="5">]</confidence>
47
+ FIG. 3 is schematic representation of an exemplary alkaline electrolysis stack arrangement. </p>
48
+ <p id="p-13" num="13">[0012] FIG. 4 is an exploded view of one embodiment of the instant invention.</p>
49
+ <p id="p-14" num="14">[0013] FIG. 5 is a side view of an electrode insert in accordance with one embodiment of the instant invention.</p>
50
+ <boundary-data type="header">
51
+ <confidence value="8">2</confidence>
52
+ </boundary-data>
53
+ <boundary-data type="header">162615</boundary-data>
54
+ <p id="p-15" num="15">
55
+ <page-break num="3"/>
56
+ [0014] FIG. 6 is a perspective view of end caps in accordance with one embodiment of the instant invention. </p>
57
+ <p id="p-16" num="16">[0015] Fig. 7 is a top view of electrochemical cell structure in accordance with one embodiment of the instant invention.</p>
58
+ <p id="p-17" num="17">[0016] FIG. 8 is a side view of the electrochemical cell structure shown in FIG. 7.</p>
59
+ <p id="p-18" num="18">[0017] FIG. 9 is a flow chart representation of one method of fabrication of the instant invention.</p>
60
+ <p id="p-19" num="19">[0018] FIG. 10 is a flow chart representation of another method of fabrication of the instant invention.</p>
61
+ <p id="p-20" num="20">[0019] FIG. 11 is a schematic representation of an alkaline electrolysis system in accordance with the instant invention.</p>
62
+ <heading id="h-8">DETAILED DESCR<confidence value="8">I</confidence>
63
+ PTION </heading>
64
+ <p id="p-21" num="21">[0020] An electrochemical cell structure <part-num-ref name="electrochemical cell structure">10</part-num-ref>
65
+ comprising an anode <part-num-ref name="anode">12,</part-num-ref>
66
+ a cathode <part-num-ref name="cathode">14</part-num-ref>
67
+ spaced apart from the anode <part-num-ref name="anode">12,</part-num-ref>
68
+ an electrolyte <part-num-ref name="electrolyte">16</part-num-ref>
69
+ in ionic communication with each of the anode <part-num-ref name="anode">12</part-num-ref>
70
+ and the cathode <part-num-ref name="cathode">14,</part-num-ref>
71
+ and a single-piece nonconductive frame <part-num-ref name="single-piece nonconductive frame">18,</part-num-ref>
72
+ is shown in FIG. 1. The single-piece nonconductive frame <part-num-ref name="single-piece nonconductive frame">18</part-num-ref>
73
+ supports the anode <part-num-ref name="anode">12,</part-num-ref>
74
+ the cathode <part-num-ref name="cathode">14</part-num-ref>
75
+ and the electrolyte <part-num-ref name="electrolyte">16</part-num-ref>
76
+ and defines a plurality of flowpaths <part-num-ref name="plurality of flowpaths">20</part-num-ref>
77
+ for working fluids (not shown) or byproducts of ionic exchange (not shown). As shown in FIG. </p>
78
+ <p id="p-22" num="22">1, because the elements are encased in the single-piece nonconductive frame <part-num-ref name="single-piece nonconductive frame">18</part-num-ref>
79
+ and the flowpaths <part-num-ref name="flowpaths">20</part-num-ref>
80
+ are defined by the same, the construction is efficient and effective (no gaskets or seals are required) and the fabrication process is simplified. </p>
81
+ <p id="p-23" num="23">[0021] One type of electrochemical cell structure is utilized within an alkaline electrolysis system <part-num-ref name="alkaline electrolysis system">30,</part-num-ref>
82
+ as schematically shown in FIG. 2. Water (H2<confidence value="5">0</confidence>
83
+ ) is supplied into the system <part-num-ref name="system">30</part-num-ref>
84
+ via inlet <part-num-ref name="via inlet">32</part-num-ref>
85
+ and is circulated by pump <part-num-ref name="and is circulated by pump">34.</part-num-ref>
86
+ The water is combined with a base, typically Potassium Hydroxide (KOH) or Sodium Hydroxide (NaOH), to form a liquid alkaline electrolyte <part-num-ref name="liquid alkaline electrolyte">36,</part-num-ref>
87
+ which electrolyte <part-num-ref name="liquid alkaline electrolyte 36, which electrolyte">36</part-num-ref>
88
+ is circulated by pump <part-num-ref name="is circulated by pump">34</part-num-ref>
89
+ to electrolyzer <part-num-ref name="to electrolyzer">38.</part-num-ref>
90
+ Electrolyzer <part-num-ref name="to electrolyzer 38. Electrolyzer">38</part-num-ref>
91
+ includes an anode <part-num-ref name="anode">40</part-num-ref>
92
+ (+ electrode), a diaphragm <part-num-ref name="diaphragm">42</part-num-ref>
93
+ <boundary-data type="header">
94
+ <confidence value="8">3</confidence>
95
+ </boundary-data>
96
+ <page-break num="4"/>
97
+ <boundary-data type="header">162615</boundary-data>
98
+ and a cathode <part-num-ref name="cathode">44</part-num-ref>
99
+ (- electrode). Direct current voltage <part-num-ref name="(- electrode). Direct current voltage">46</part-num-ref>
100
+ is applied to the anode <part-num-ref name="anode">40</part-num-ref>
101
+ and the cathode <part-num-ref name="cathode">44</part-num-ref>
102
+ in the presence of the electrolyte <part-num-ref name="electrolyte">36.</part-num-ref>
103
+ The direct current voltage, typically a voltage in the range between about 1.7V to about 2.2V, splits the water into its constituents of hydrogen (H2) at the cathode <part-num-ref name="cathode">44</part-num-ref>
104
+ and oxygen <part-num-ref name="and oxygen">(<confidence value="66">02</confidence>
105
+ ) </part-num-ref>
106
+ at the anode <part-num-ref name="anode">40.</part-num-ref>
107
+ Diaphragm <part-num-ref name="anode 40. Diaphragm">42</part-num-ref>
108
+ keeps the H2 and <part-num-ref name="H2 and">02</part-num-ref>
109
+ gases separated. The <part-num-ref name="">02</part-num-ref>
110
+ gas in mixture with electrolyte <part-num-ref name="gas in mixture with electrolyte">36</part-num-ref>
111
+ is transported to an oxygen separator <part-num-ref name="oxygen separator">48.</part-num-ref>
112
+ After separation from the <confidence value="2">.</confidence>
113
+ electrolyte <part-num-ref name=". electrolyte">36,</part-num-ref>
114
+ the <part-num-ref name="">02</part-num-ref>
115
+ gas is stored, vented, or otherwise utilized and a portion of the electrolyte <part-num-ref name="electrolyte">50</part-num-ref>
116
+ is recirculated by pump <part-num-ref name="is recirculated by pump">34</part-num-ref>
117
+ into system <part-num-ref name="into system">30.</part-num-ref>
118
+ The H<confidence value="5">2</confidence>
119
+ gas in mixture with liquid electrolyte <part-num-ref name="H2 gas in mixture with liquid electrolyte">36</part-num-ref>
120
+ is transported to a hydrogen separator <part-num-ref name="hydrogen separator">52.</part-num-ref>
121
+ After separation from the electrolyte <part-num-ref name="electrolyte">36,</part-num-ref>
122
+ the H2 gas is captured and stored, burned, electrochemically reacted or otherwise utilized and a portion of the electrolyte <part-num-ref name="electrolyte">54</part-num-ref>
123
+ is recirculated by pump <part-num-ref name="is recirculated by pump">34</part-num-ref>
124
+ into system <part-num-ref name="into system">30.</part-num-ref>
125
+ </p>
126
+ <p id="p-24" num="24">
127
+ <confidence value="885">[00</confidence>
128
+ 22] As discussed above, in order for electrochemical systems, especially alkaline electrolysis systems, to become economically feasible the manufacturing costs associated with these systems must markedly improve. Current systems require numerous process steps during assembly, with each step adding cost to the overall system. Additionally, conventional systems currently have many individual component parts including multiple electrodes, diaphragms, gaskets, bolts and other miscellaneous parts that add to the complexity of the system assembly and drive the manufacturing costs up. </p>
129
+ <p id="p-25" num="25">[0023] One particularly difficult and expensive fabrication area is the stack assembly within these electrochemical systems. Taking an alkaline electrolysis stack as an exemplary stack arrangement, the general configuration and fabrication difficulties can be discussed in reference to FIG. 3. As shown in FIG. 3, a typical stack assembly <part-num-ref name="typical stack assembly">56</part-num-ref>
130
+ includes a plurality of repeat units <part-num-ref name="plurality of repeat units">58.</part-num-ref>
131
+ Each repeat unit <part-num-ref name="plurality of repeat units 58. Each repeat unit">58</part-num-ref>
132
+ includes an anode <part-num-ref name="anode">60,</part-num-ref>
133
+ a bipolar plate <part-num-ref name="bipolar plate">62,</part-num-ref>
134
+ a cathode <part-num-ref name="cathode">64</part-num-ref>
135
+ and a diaphragm <part-num-ref name="diaphragm">66.</part-num-ref>
136
+ Any large-scale implementation of an alkaline electrolysis stack may include as many as a hundred or more repeat units <part-num-ref name="hundred or more repeat units">58.</part-num-ref>
137
+ Each repeat unit <part-num-ref name="hundred or more repeat units 58. Each repeat unit">58</part-num-ref>
138
+ requires electrical coupling between the anode <part-num-ref name="anode">60,</part-num-ref>
139
+ the bipolar plate <part-num-ref name="bipolar plate">62</part-num-ref>
140
+ and the cathode <part-num-ref name="cathode">64,</part-num-ref>
141
+ referred to as the electrode assembly <part-num-ref name="electrode assembly">65.</part-num-ref>
142
+ Each electrode assembly <part-num-ref name="electrode assembly 65. Each electrode assembly">65</part-num-ref>
143
+ must be separated by a diaphragm <part-num-ref name="diaphragm">66,</part-num-ref>
144
+ <boundary-data type="header">
145
+ <confidence value="8">4</confidence>
146
+ </boundary-data>
147
+ <page-break num="5"/>
148
+ <boundary-data type="header">162615</boundary-data>
149
+ primarily to keep the hydrogen and oxygen gases from mixing between adjacent electrode assemblies <part-num-ref name="hydrogen and oxygen gases from mixing between adjacent electrode assemblies">65.</part-num-ref>
150
+ All of the repeat units <part-num-ref name="repeat units">58</part-num-ref>
151
+ within a stack must be positioned within some type of housing, and surrounded by nonconductive gasketing, sealing technologies, and piping or manifolds to distribute the electrolyte and to capture the hydrogen and oxygen gases. Hundreds or possibly thousands of connections and bolts or other fasteners are used to assemble this type of stack, further impacting the fabrication costs. </p>
152
+ <p id="p-26" num="26">[0024] In accordance with one embodiment of the instant invention, an electrochemical cell structure <part-num-ref name="electrochemical cell structure">100</part-num-ref>
153
+ is shown in FIGS. 4-8. Electrochemical cell structure <part-num-ref name="is shown in FIGS. 4-8. Electrochemical cell structure">100</part-num-ref>
154
+ is shown in an exploded view to better demonstrate the constituent parts in FIG 4. Electrochemical cell structure <part-num-ref name="constituent parts in FIG 4. Electrochemical cell structure">100</part-num-ref>
155
+ comprises an anode <part-num-ref name="anode">102</part-num-ref>
156
+ and a cathode <part-num-ref name="cathode">104</part-num-ref>
157
+ spaced apart from the anode <part-num-ref name="anode">102.</part-num-ref>
158
+ A bipolar plate <part-num-ref name="bipolar plate">106</part-num-ref>
159
+ is interposed between the anode <part-num-ref name="anode">102</part-num-ref>
160
+ and the cathode <part-num-ref name="cathode">104</part-num-ref>
161
+ to enable an electrical connection therebetween. In one embodiment of the invention, as best shown in FIG. 5, anode <part-num-ref name="invention, as best shown in FIG. 5, anode">102,</part-num-ref>
162
+ bipolar plate <part-num-ref name="invention, as best shown in FIG. 5, anode 102, bipolar plate">106</part-num-ref>
163
+ and cathode <part-num-ref name="and cathode">104</part-num-ref>
164
+ are joined together to create an electrode insert <part-num-ref name="electrode insert">108.</part-num-ref>
165
+ </p>
166
+ <p id="p-27" num="27">Electrochemical cell structure 100 (FIG. <part-num-ref name="(FIG.">4)</part-num-ref>
167
+ further comprises an electrode frame <part-num-ref name="electrode frame">110.</part-num-ref>
168
+ </p>
169
+ <p id="p-28" num="28">Electrode frame 110 comprises an electrolyte inlet <part-num-ref name="electrolyte inlet">112,</part-num-ref>
170
+ a first electrolyte flow path <part-num-ref name="first electrolyte flow path">114</part-num-ref>
171
+ on a top surface <part-num-ref name="top surface">116,</part-num-ref>
172
+ a second electrolyte flow path <part-num-ref name="second electrolyte flow path">117</part-num-ref>
173
+ on a bottom surface <part-num-ref name="bottom surface">118</part-num-ref>
174
+ (shown with dotted lines), a seat <part-num-ref name="seat">120,</part-num-ref>
175
+ an oxygen flow path <part-num-ref name="oxygen flow path">122</part-num-ref>
176
+ on top surface <part-num-ref name="on top surface">116</part-num-ref>
177
+ and a hydrogen flow path <part-num-ref name="hydrogen flow path">124</part-num-ref>
178
+ on bottom surface <part-num-ref name="on bottom surface">118</part-num-ref>
179
+ (shown with dotted lines). Electrode insert <part-num-ref name="(shown with dotted lines). Electrode insert">108</part-num-ref>
180
+ is positioned on seat <part-num-ref name="is positioned on seat">120.</part-num-ref>
181
+ Electrochemical cell structure <part-num-ref name="is positioned on seat 120. Electrochemical cell structure">100</part-num-ref>
182
+ further comprises a top diaphragm <part-num-ref name="top diaphragm">126,</part-num-ref>
183
+ a top diaphragm frame <part-num-ref name="top diaphragm frame">128,</part-num-ref>
184
+ a bottom diaphragm <part-num-ref name="bottom diaphragm">130</part-num-ref>
185
+ and a bottom diaphragm frame <part-num-ref name="bottom diaphragm frame">132.</part-num-ref>
186
+ For purposes of discussion, in this embodiment, the top diaphragm frame <part-num-ref name="top diaphragm frame">128,</part-num-ref>
187
+ the top diaphragm <part-num-ref name="top diaphragm">126,</part-num-ref>
188
+ the electrode insert <part-num-ref name="electrode insert">108,</part-num-ref>
189
+ the electrode frame <part-num-ref name="electrode frame">108,</part-num-ref>
190
+ the bottom diaphragm <part-num-ref name="bottom diaphragm">130</part-num-ref>
191
+ and the bottom diaphragm frame <part-num-ref name="bottom diaphragm frame">132</part-num-ref>
192
+ form a repeat plate <part-num-ref name="repeat plate">134.</part-num-ref>
193
+ An implementation of an alkaline electrolysis stack would include many, for example between about <part-num-ref name="alkaline electrolysis stack would include many, for example between about">10</part-num-ref>
194
+ to about <part-num-ref name="to about">100,</part-num-ref>
195
+ individual repeat plates <part-num-ref name="to about 100, individual repeat plates">134.</part-num-ref>
196
+ As shown in FIG. 6, each stack is typically capped with an end cap <part-num-ref name="end cap">140,</part-num-ref>
197
+ an anode <part-num-ref name="anode">102</part-num-ref>
198
+ and a current collector <part-num-ref name="current collector">142</part-num-ref>
199
+ at one end and an end cap <part-num-ref name="end cap">140,</part-num-ref>
200
+ a cathode <part-num-ref name="cathode">104</part-num-ref>
201
+ and a current collector <part-num-ref name="current collector">142</part-num-ref>
202
+ at an opposite end. </p>
203
+ <boundary-data type="header">
204
+ <confidence value="8">5</confidence>
205
+ </boundary-data>
206
+ <boundary-data type="header">162615</boundary-data>
207
+ <p id="p-29" num="29">
208
+ <page-break num="6"/>
209
+ [0025] In operation, an electrolyte is introduced via inlet <part-num-ref name="electrolyte is introduced via inlet">112</part-num-ref>
210
+ (FIG. <part-num-ref name="(FIG.">4)</part-num-ref>
211
+ and is distributed to the anode <part-num-ref name="anode">102</part-num-ref>
212
+ by first flow path <part-num-ref name="by first flow path">114</part-num-ref>
213
+ and to the cathode <part-num-ref name="cathode">104</part-num-ref>
214
+ by second flow path <part-num-ref name="by second flow path">117.</part-num-ref>
215
+ In addition, the electrolyte flows through the top membrane <part-num-ref name="top membrane">126</part-num-ref>
216
+ and the bottom membrane <part-num-ref name="bottom membrane">130</part-num-ref>
217
+ and creates an ionic bridge between adjacent repeat plates <part-num-ref name="ionic bridge between adjacent repeat plates">134.</part-num-ref>
218
+ A DC current is applied to the electrode inserts <part-num-ref name="electrode inserts">108</part-num-ref>
219
+ and a portion of the electrolyte dissociates into oxygen and hydrogen at each anode <part-num-ref name="electrolyte dissociates into oxygen and hydrogen at each anode">102</part-num-ref>
220
+ and cathode <part-num-ref name="and cathode">104,</part-num-ref>
221
+ respectively, within a representative stack. The oxygen and a portion of the electrolyte flow through oxygen flow path <part-num-ref name="electrolyte flow through oxygen flow path">122</part-num-ref>
222
+ to an oxygen outlet <part-num-ref name="oxygen outlet">123</part-num-ref>
223
+ and the hydrogen and a portion of the electrolyte flow through hydrogen flow path <part-num-ref name="electrolyte flow through hydrogen flow path">124</part-num-ref>
224
+ to a hydrogen outlet <part-num-ref name="hydrogen outlet">125.</part-num-ref>
225
+ Additional flow paths (not shown) are provided between adjacent repeat plates <part-num-ref name="hydrogen outlet 125. Additional flow paths (not shown) are provided between adjacent repeat plates">134</part-num-ref>
226
+ to allow the electrolyte to flow to one of the inlet <part-num-ref name="inlet">112,</part-num-ref>
227
+ the oxygen outlet <part-num-ref name="oxygen outlet">123</part-num-ref>
228
+ and the hydrogen outlet <part-num-ref name="hydrogen outlet">125.</part-num-ref>
229
+ </p>
230
+ <p id="p-30" num="30">[0026] As shown best in FIG 4, the top diaphragm support <part-num-ref name="top diaphragm support">128,</part-num-ref>
231
+ the electrode frame <part-num-ref name="electrode frame">110</part-num-ref>
232
+ and the bottom diaphragm support <part-num-ref name="bottom diaphragm support">132</part-num-ref>
233
+ components, of each repeat plate <part-num-ref name="components, of each repeat plate">134</part-num-ref>
234
+ are made of a nonconductive materials, and typically, although not necessarily, have the same general geometry. For purposes of clarity, these combined components are referred to as nonconductive frame <part-num-ref name="same general geometry. For purposes of clarity, these combined components are referred to as nonconductive frame">150.</part-num-ref>
235
+ In one embodiment, nonconductive frame <part-num-ref name="same general geometry. For purposes of clarity, these combined components are referred to as nonconductive frame 150. In one embodiment, nonconductive frame">150</part-num-ref>
236
+ comprises a material having a maximum working temperature in a range between about <part-num-ref name="range between about">60</part-num-ref>
237
+ degrees Celsius to about <part-num-ref name="degrees Celsius to about">120</part-num-ref>
238
+ degrees Celsius. This temperature range would support most alkaline electrolysis applications. In another embodiment, nonconductive frame <part-num-ref name="degrees Celsius. This temperature range would support most alkaline electrolysis applications. In another embodiment, nonconductive frame">150</part-num-ref>
239
+ comprises a material having a maximum working temperature in a range between about <part-num-ref name="range between about">60</part-num-ref>
240
+ degrees Celsius to about <part-num-ref name="degrees Celsius to about">300</part-num-ref>
241
+ degrees Celsius. This temperature range would support most alkaline electrolysis and fuel cell applications as well as most proton exchange membrane (PEM), polybenzimidazole (PBI), and acid electrolysis and fuel cell applications. </p>
242
+ <p id="p-31" num="31">[0027] In one embodiment of the instant invention, the nonconductive frame <part-num-ref name="nonconductive frame">150</part-num-ref>
243
+ comprises a polymer, typically a polymer chemically resistant to caustic to avoid degradation during prolonged exposure to bases like KOH or NaOH. In another embodiment, the nonconductive frame <part-num-ref name="nonconductive frame">150</part-num-ref>
244
+ comprises a hydrolytically stable polymer. </p>
245
+ <p id="p-32" num="32">In another embodiment, the nonconductive frame <part-num-ref name="nonconductive frame">150</part-num-ref>
246
+ is selected from the group <boundary-data type="header">
247
+ <confidence value="8">6</confidence>
248
+ </boundary-data>
249
+ <page-break num="7"/>
250
+ <boundary-data type="header">162615</boundary-data>
251
+ consisting of polyethylene, fluorinated polymers, polypropylene, and polysulfone polyphenyleneoxide<confidence value="5">,</confidence>
252
+ polyphenylenesulfide, polystyrene and blends thereof. </p>
253
+ <p id="p-33" num="33">[0028] In reference to FIGS. 7 and <part-num-ref name="and">8,</part-num-ref>
254
+ repeat plate <part-num-ref name="and 8, repeat plate">134</part-num-ref>
255
+ is depicted as a single unit. </p>
256
+ <p id="p-34" num="34">Each repeat plate 134 is constructed to provide an inlet <part-num-ref name="inlet">112</part-num-ref>
257
+ for the electrolyte. As best shown in FIG. 8, the electrolyte splits into two streams on either side of the bipolar plate <part-num-ref name="bipolar plate">106</part-num-ref>
258
+ and dissociates into H<confidence value="5">2</confidence>
259
+ and <part-num-ref name="and dissociates into H2 and">
260
+ <confidence value="5">0</confidence>
261
+ 2. </part-num-ref>
262
+ The diaphragms <part-num-ref name="diaphragms">126</part-num-ref>
263
+ and <part-num-ref name="and">130</part-num-ref>
264
+ bound each side of the electrode insert to ensure the H2 and <confidence value="55">O2</confidence>
265
+ do not mix between adjacent repeat plates <part-num-ref name="H2 and O2 do not mix between adjacent repeat plates">134.</part-num-ref>
266
+ The construction of this exemplary repeat plate <part-num-ref name="construction of this exemplary repeat plate">134</part-num-ref>
267
+ is simple and avoids the use of seals or gaskets. As depicted, the electrode i<confidence value="8">n</confidence>
268
+ sert <part-num-ref name="electrode insert">108</part-num-ref>
269
+ and the diaphragms <part-num-ref name="diaphragms">126</part-num-ref>
270
+ and <part-num-ref name="and">130</part-num-ref>
271
+ are supported and encased within the single-piece nonconductive frame of repeat plate <part-num-ref name="single-piece nonconductive frame of repeat plate">134.</part-num-ref>
272
+ The flow paths for the electrolyte are also defined by the single-piece nonconductive frame of repeat plate <part-num-ref name="single-piece nonconductive frame of repeat plate">134,</part-num-ref>
273
+ essentially removing any need for gasketing within the system. </p>
274
+ <p id="p-35" num="35">[0029] In one embodiment of the invention, the electrochemical cell structure is fabricated according to the process discussed in reference to FIG. 9. First an electrode assembly is positioned within a first nonconductive frame piece S <part-num-ref name="first nonconductive frame piece S">
275
+ <confidence value="6">1</confidence>
276
+ . </part-num-ref>
277
+ As discussed above, the electrode assembly typically comprises an anode, a cathode and a bipolar plate. Next, a second nonconductive frame piece is applied to the first nonconductive frame piece to sandwich the electrode assembly therebetween S2. Next, the first and second nonconductive frame pieces are joined together to form a single-piece nonconductive frame unit about the electrode assembly S3. Additional nonconductive frame pieces and additional component parts may be added as per requirements, for example, a diaphragm frame and a diaphragm. Multiple single-piece nonconductive frame units are joined together to form an electrochemical stack structure having a single-piece nonconductive frame. In one embodiment, the frame pieces or units are joined together by adhesive. In another embodiment, the frame pieces or units are joined together using ultrasonic or laser welding. In yet another embodiment, the frame pieces or units are joined together by applying heat or current to melt the pieces or units together. </p>
278
+ <boundary-data type="header">
279
+ <confidence value="8">7</confidence>
280
+ </boundary-data>
281
+ <boundary-data type="header">162615</boundary-data>
282
+ <p id="p-36" num="36">
283
+ <page-break num="8"/>
284
+ [0030] In another embodiment, the electrochemical cell structure is fabricated according to the process discussed in reference to FIG. 10. First at least one and typically a plurality of electrode assemblies are positioned within a molding apparatus S4. As discussed above, the electrode assembly typically comprises an anode, a cathode and a bipolar plate. Next, a heated molding material, typically a polymer, is dispensed into the molding apparatus and flows around the provided electrode assemblies S5. Finally, the molding material is cooled and the electrochemical cell structure is removed from the molding apparatus <confidence value="5">S</confidence>
285
+ 6. In this embodiment, the single- piece nonconductive frame is formed in place around the electrode assemblies, thereby further simplifying the fabrication process. The flow channels and pathways are predefined in the molding apparatus to ensure proper flow of working fluids and ionic byproducts during use. Additional component parts can be included if required, for example, diaphragms may be positioned within the molding apparatus prior to <confidence value="568">S5.</confidence>
286
+ </p>
287
+ <p id="p-37" num="37">[0031] One embodiment of the instant invention is depicted in FIG. 11. Water (H2<confidence value="5">0</confidence>
288
+ ) is supplied into the system and is circulated by pump <part-num-ref name="system and is circulated by pump">34.</part-num-ref>
289
+ The water is combined with an alkaline base, typically Potassium Hydroxide (KOH) or Sodium Hydroxide (Na<confidence value="5">O</confidence>
290
+ H), to form a liquid alkaline electrolyte that is circulated by pump <part-num-ref name="liquid alkaline electrolyte that is circulated by pump">34</part-num-ref>
291
+ to the inlet <part-num-ref name="inlet">112</part-num-ref>
292
+ formed in the single-piece nonconductive frame <part-num-ref name="single-piece nonconductive frame">150.</part-num-ref>
293
+ A plurality of electrode inserts <part-num-ref name="plurality of electrode inserts">108</part-num-ref>
294
+ is positioned within the single-piece nonconductive frame and is separated from adjacent electrode inserts <part-num-ref name="single-piece nonconductive frame and is separated from adjacent electrode inserts">108</part-num-ref>
295
+ by diaphragms, as discussed above. The electrolyte flows though the inlet <part-num-ref name="inlet">112</part-num-ref>
296
+ and to each of the respective electrode inserts <part-num-ref name="respective electrode inserts">108.</part-num-ref>
297
+ Direct current voltage is applied to the electrode inserts <part-num-ref name="electrode inserts">108</part-num-ref>
298
+ in the presence of the electrolyte. The direct current voltage splits the water into its constituents of hydrogen (H2) at the cathode and oxygen <part-num-ref name="cathode and oxygen">(<confidence value="5">0</confidence>
299
+ 2) </part-num-ref>
300
+ at the anode. The diaphragms keep the H2 and <part-num-ref name="H2 and">
301
+ <confidence value="66">02</confidence>
302
+ </part-num-ref>
303
+ gases separated. The <part-num-ref name="">02</part-num-ref>
304
+ gas in mixture with electrolyte is transported via oxygen outlet <part-num-ref name="gas in mixture with electrolyte is transported via oxygen outlet">123</part-num-ref>
305
+ (defined by single-piece nonconductive frame <part-num-ref name="(defined by single-piece nonconductive frame">150)</part-num-ref>
306
+ to an oxygen separator. After separation from the electrolyte, the <part-num-ref name="">02</part-num-ref>
307
+ gas is stored, vented, or otherwise utilized and a portion of the electrolyte is recirculated by pump <part-num-ref name="electrolyte is recirculated by pump">34</part-num-ref>
308
+ into the system. The H<confidence value="5">2</confidence>
309
+ gas in mixture with liquid electrolyte is transported via hydrogen outlet <part-num-ref name="H2 gas in mixture with liquid electrolyte is transported via hydrogen outlet">125</part-num-ref>
310
+ (defined by single-piece nonconductive frame <part-num-ref name="(defined by single-piece nonconductive frame">150)</part-num-ref>
311
+ to a hydrogen separator. After separation from the electrolyte, the H<confidence value="5">2</confidence>
312
+ gas is captured and stored, <boundary-data type="header">
313
+ <confidence value="8">8</confidence>
314
+ </boundary-data>
315
+ <page-break num="9"/>
316
+ <boundary-data type="header">162615</boundary-data>
317
+ burned, electrochemically reacted or otherwise utilized and a portion of the electrolyte is recirculated by pump <part-num-ref name="electrolyte is recirculated by pump">34</part-num-ref>
318
+ into the system. </p>
319
+ <p id="p-38" num="38">[0032] While only certain features of the invention have been illustrated and described herein, many modifications and changes will occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention.</p>
320
+ <boundary-data type="header">
321
+ <confidence value="8">9</confidence>
322
+ </boundary-data>
323
+ </description>
324
+ </us-patent-application>
325
+
prior_art/11111107.xml ADDED
@@ -0,0 +1,530 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11111107</doc-number>
8
+ <date>2005-04-20</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <heading id="h-1">UNITED STATES PATENT APPLICATION</heading>
14
+ <heading id="h-2">
15
+ <confidence value="88">OF</confidence>
16
+ </heading>
17
+ <p id="p-1" num="1">Joshua Todd <confidence value="5">Y</confidence>
18
+ uster Doug Wayne Dalton </p>
19
+ <heading id="h-3">FOR</heading>
20
+ <heading id="h-4">SYSTEM AND METHOD FOR MAPPING RELATIONSHIP</heading>
21
+ <heading id="h-5">MANAGEMENT INTELLIGENCE</heading>
22
+ <p id="p-2" num="2">(Atty. Dkt. 016346-0315811, Client Ref. Br<confidence value="588666">IT-001</confidence>
23
+ -U) </p>
24
+ <heading id="h-6">PREPARED BY:</heading>
25
+ <heading id="h-7">PILLSBURY WINTHROP LLP</heading>
26
+ <p id="p-3" num="3">2475 Hanover Street Palo Alto, CA 94304-1115 Phone: (650) 233-4500 Fax: <part-num-ref name="233-4500 Fax:">(650)</part-num-ref>
27
+ 233-4545 <boundary-data type="header">Attn.: Jubin Dana, Reg. No. 41,400</boundary-data>
28
+ <page-break num="2"/>
29
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
30
+ </p>
31
+ <heading id="h-8">CROSS REFERENCE TO RELATED APPLICATION</heading>
32
+ <p id="p-4" num="4">[0001] This,application claims the benefit of U.S. Provisional Application No. 60/564,245, filed April <part-num-ref name="benefit of U.S. Provisional Application No. 60/564,245, filed April">20,</part-num-ref>
33
+ <part-num-ref name="benefit of U.S. Provisional Application No. 60/564,245, filed April 20,">2004</part-num-ref>
34
+ (Atty. Dkt.: 016346-0309288) entitled </p>
35
+ <heading id="h-9">"SYSTEM AND METHOD FOR MAPPING RELATIONSHIP MANAGEMENT</heading>
36
+ <heading id="h-10">INTELLIGENCE'.</heading>
37
+ <heading id="h-11">FIELD OF THE INVENTION</heading>
38
+ <p id="p-5" num="5">[0002] The present invention relates generally to the field of data management and, more specifically to, business intelligence, enterprise search, social networking, and customer relationship management used to develop data for enterprise relationship management.</p>
39
+ <heading id="h-12">BACKGROUND OF THE INVENTION</heading>
40
+ <p id="p-6" num="6">[0003] Networking typically occurs on a verbal level. Known systems lack sufficient means for allowing members of an organization to share knowledge relating not just to what they know, but also to who the members know.</p>
41
+ <p id="p-7" num="7">Furthermore, known systems are inadequate for tracking whom everyone within the enterprise "knows" as well as finding ways to share that information without jeopardizing or diluting these relationships.</p>
42
+ <p id="p-8" num="8">[0004] It is known that a valuable asset of an organization or a company is the members or employees in light of the aggregate relationship of each of those individuals with individuals outside of the organization, on both a <boundary-data type="header">
43
+ <confidence value="8">1</confidence>
44
+ </boundary-data>
45
+ <page-break num="3"/>
46
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
47
+ professional and personal level. In essence, whom a given employee knows is valuable information that can be utilized by the organization. It is to the benefit of the organization, as well as the members or employees, to utilize the relationships that already exist to form and create new relationships with people outside of the organization. </p>
48
+ <p id="p-9" num="9">[0005] Various methods and systems currently exist that allow an organization to facilitate introductions that may result in the formation of new relationships between people inside the organization or company for the benefit of forming new relationships to individuals outside of the organization or company.</p>
49
+ <p id="p-10" num="10">[0006] For example, known systems allow a requestor to send a request to one or more individuals in the organization to inquire about a particular relationship that may exists between other members of the requestor's organization and an individual outside of the organization. However, these systems lack the ability to keep either or both the identity of the requestor and the individual with the connection anonymous relative to the other person.</p>
50
+ <p id="p-11" num="11">[0007] Other known systems attempt to find a relational path between the requestor within the organization and the targeted person outside the organization by identifying various links that connect the requestor to at least one other individual in the organization who knows a third-individual in the organization who knows a fourth-individual in the organization, and so on, until the final person is reached in the organization, which may be up to six degrees of separation or more, familiar with the targeted person outside the organization.</p>
51
+ <p id="p-12" num="12">However, the problem with this approach is that many individuals are involved instead of just the individual at the end of the chain within the organization, which results in an inefficient and often ineffective process, especially when there is little motivation for the members of the organization to respond to others <boundary-data type="header">
52
+ <confidence value="8">2</confidence>
53
+ </boundary-data>
54
+ <page-break num="4"/>
55
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
56
+ in the chain and eventually to the requestor. </p>
57
+ <p id="p-13" num="13">[0008] Alternative methods exist, such as use of electronic mail or e-mail, wherein the requestor generates a request in the form of an email to the members of the organization. The requestor queries a set group or potentially the entire organization hoping to get a response from other members of the organization familiar with the targeted person outside of the organization.</p>
58
+ <p id="p-14" num="14">However, such an approach not only lacks anonymity but also results in numerous emails being generated, which can increase exponentially.</p>
59
+ <p id="p-15" num="15">Furthermore, there is no effective means of evaluating the relationships. Also, this approach lacks the ability to quantitatively measure the effectiveness of this system in light of the burden on the system and the members of the organization.</p>
60
+ <p id="p-16" num="16">[0009] Thus, what is needed is a system and method that can identify individuals within an organization who are familiar with a targeted person outside of the organization. Furthermore, the system should be able to evaluate the strength of the relationship based on statistical data and present the information about the strength of the relationship between the individuals in the organization and the targeted person to a requestor. Such relationship data should be presented to the requestor while maintaining the anonymity of the other individuals within the organization with a relation to the targeted individual outside of the organization. Furthermore, what is needed is a system and method that will also allow the requestor to remain anonymous to the individual or individuals receiving the request, if so desired. The state of anonymity should continue until it is determined that the member of the organization or the requestor or both chooses to be identifiable by the other.</p>
61
+ <boundary-data type="header">
62
+ <confidence value="8">3</confidence>
63
+ </boundary-data>
64
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
65
+ <heading id="h-13">SUMMARY OF THE INVENTION</heading>
66
+ <p id="p-17" num="17">
67
+ <page-break num="5"/>
68
+ [0010] The present invention discloses a system and a method for identifying individuals within an organization that are familiar with a target person outside of the organization. Such data is presented to the requestor and the system is capable of maintaining the anonymity of either or both the individual of the organization receiving the request and the requestor, unless and until it is determined that the individual and/or the requestor are to be identified to each other. Additionally, the present invention includes a system and means for updating the data as identified below in situations where new contacts occur, when companies share relationship information, or when companies merge. For example, a data center can query and pull information from a selected company. </p>
69
+ <p id="p-18" num="18">[0011] One advantage of the present invention is that the identity of both parties involved in creating a connection, such as the requestor and the individual having the relationship with the target individual, can be kept anonymous until each respective party chooses to reveal his or her identity or such identity is revealed by the system administrator.</p>
70
+ <p id="p-19" num="19">[0012] Another advantage of the present invention is that it can weigh and rank relationships based on prior system usage. The present invention includes knowledge management, business intelligence, and search technologies and is directed to a method and system for collecting user relationship information, mapping relationship information, scoring relationship information, and providing a platform for connecting users together to share relationship information in a secure, non-invasive means.</p>
71
+ <p id="p-20" num="20">[0013] Yet another advantage of the present invention is the ability to include incentives for participation in the relationship management system to tie to an incentive either at a company level, at an individual level, or at a search <boundary-data type="header">
72
+ <confidence value="8">4</confidence>
73
+ </boundary-data>
74
+ <page-break num="6"/>
75
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
76
+ level whereby the incentive may either be pre-set or may be negotiated by the parties involved. </p>
77
+ <p id="p-21" num="21">[0014] Still another advantage of the present invention is aimed at not only "hunting" down and uncovering relationship management intelligence that already exists within the organization but also at facilitating control over relationships, enabling the organization to make them more plentiful, and higher quality, over time by enabling the "farming" of relationship networks. In this way, the person with the relationship retains some degree of control and, hence, a greater level of trust.</p>
78
+ <p id="p-22" num="22">[0015] The advantages of the present invention are achieved without the need to load or place software on each individual system or user system located at the organization. The software that extracts the relationship information can be remotely <confidence value="8">l</confidence>
79
+ ocated. This provides many advantages including the ability for a customer to get up and running quickly, without relying on their IT-department to install software in-house. Also, amongst other things, new features can automatically be pushed out to customers without patches needing to be installed at the customer. </p>
80
+ <p id="p-23" num="23">[0016] One application for such a system and method is in the area of sales-based enterprises, where the difference between a cold call and a warm lead when going into a sales call can be significant. Specifically, organizations looking to develop more channels for their products, those in high-growth markets where sales cycle speed is paramount in a "land grab" environment, would greatly benefit from using every resource available to find these warm leads. Secondly, sales-based organizations within already tightly competitive markets, where every bit of marginal information can help increase close rates and pump up revenues, would also stand to win out from gaining extra insight.</p>
81
+ <boundary-data type="header">
82
+ <confidence value="8">5</confidence>
83
+ </boundary-data>
84
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
85
+ <p id="p-24" num="24">
86
+ <page-break num="7"/>
87
+ [0017] Other areas of application include the field of human resource management. The process of finding and hiring the right candidate, for example, can be costly and such cost would be significantly reduced by using relationship management information in accordance with the teachings of the present invention to search out hires, in lieu of paying expensive recruiters and headhunters, and to check an applicant's reference. </p>
88
+ <p id="p-25" num="25">[0018] In addition, organizations recently acquiring other companies can benefit from a smoother merger-integration process. Rather than relying on scheduled meetings or informal conversations to establish who knows whom, the information becomes available immediately after the data from the acquired company's systems are cataloged.</p>
89
+ <p id="p-26" num="26">[0019] Another aspect of the invention disclosed is when two organizations merge or join. Regardless of timing, the merging of two organizations is an unavoidably complicated proposition requiring a huge amount of time, energy, and capital for sorting out which assets are additive, which are conflicting, and which are redundant. The present invention includes a means to benefit the new organization from its newly expanded relationship network from the start. Automated discovery and cataloging of relationship information, such as that found in email headers, makes integrating an acquired company's relationship information a streamlined process, rather than a burden and lost opportunity.</p>
90
+ <p id="p-27" num="27">[0020] The present invention includes the advantage of using any information that is related to relationship management within an organization, such as but not limited to information or data stored in customer relationship management databases, sales force automation systems and databases, contact information databases, phone records, and instant messaging contact or buddy lists (similar to those provided by various internet service providers) in <boundary-data type="header">
91
+ <confidence value="8">6</confidence>
92
+ </boundary-data>
93
+ <page-break num="8"/>
94
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
95
+ addition to information contained in e-mail headers. These sources of information can be "mined" to obtain the necessary information needed to create an effective relationship management system in accordance with the teaching of the present invention. </p>
96
+ <p id="p-28" num="28">[0021] These and other objects and advantages of the present invention will appear more clearly from the following description in which the preferred embodiments of the invention have been described in conjunction with the drawing figures.</p>
97
+ <heading id="h-14">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
98
+ <p id="p-29" num="29">[0022] <confidence value="5">T</confidence>
99
+ he present invention is illustrated by way of example, not limitation, in the figures of the accompanying drawings, in which like references indicate-similar elements and wherein: </p>
100
+ <p id="p-30" num="30">[0023] Figure 1 represents the architecture for capturing and mapping of data related to relationships, for example in the form of email interactions;</p>
101
+ <p id="p-31" num="31">[0024] Figure 2 is an example of how a user can search for a connection to a target individual based on knowing certain attributes of the target individual;</p>
102
+ <p id="p-32" num="32">[0025] Figure 3 depicts an example of how search results for relationships between individuals within the organization and target individuals can be displayed anonymously and how search results can be displayed in order of relevance ranked by a scoring system, or by taking <boundary-data type="header">
103
+ <confidence value="8">7</confidence>
104
+ </boundary-data>
105
+ <page-break num="9"/>
106
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
107
+ into account some user selected attributes; </p>
108
+ <p id="p-33" num="33">[0026] Figure 3a depicts an example of how search results for relationships between individuals within the organization and target companies can be displayed anonymously and how search results can be displayed in order of relevance ranked by a scoring system, or by taking into account some user selected attributes;</p>
109
+ <p id="p-34" num="34">[0027] Figure 4 depicts an example of how a requestor can request an introduction to a target individual by customizing a message, which may or may not be kept anonymous, to be sent to an individual with a relationship with the target individual;</p>
110
+ <p id="p-35" num="35">[0028] Figure 4a depicts an example of how a requestor can request an introduction to a target company by customizing a message, which may or may not be kept anonymous, to be sent to an individual with a relationship to the target company;</p>
111
+ <p id="p-36" num="36">[0029] Figure 5 depicts an example of an individual's homepage which may display a summary of current and completed requests made by the individual viewing the homepage as well as those requesting an introduction from the individual viewing the homepage;</p>
112
+ <p id="p-37" num="37">[0030] Figure 5a depicts an example of the system tracking the outstanding requests for introduction to various Target Persons;</p>
113
+ <p id="p-38" num="38">[0031] Figure 5b illustrates the requestor's electronic mail in-box after sending out a request and receiving a system generated confirmation that a request was routed;</p>
114
+ <p id="p-39" num="39">[0032] Figure 5c depicts and example of the system tracking the <boundary-data type="header">
115
+ <confidence value="8">8</confidence>
116
+ </boundary-data>
117
+ <page-break num="10"/>
118
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
119
+ outstanding requests for introduction to various Target Companies or Organizations; </p>
120
+ <p id="p-40" num="40">[0033] Figure 6 depicts an example of a request received by an individual that has a relationship with the target individual and includes an example of how an incentive is tracked and presented to the individual in accordance with the teachings of the present invention;</p>
121
+ <p id="p-41" num="41">[0034] Figure 6a depicts an example of a request received by an individual that has a relationship with the target company and includes an example of how an incentive is tracked and presented to the individual in accordance with the teachings of the present invention;</p>
122
+ <p id="p-42" num="42">[0035] Figure 6b illustrates the Link's electronic mail in-box after the requestor sends out a request and the Link receives a system generated message that a request is waiting for the Link to act on;</p>
123
+ <p id="p-43" num="43">[0036] Figure 7 depicts an example of a user receiving a reply to his or her introduction request to a target individual and includes capabilities such as accepting the request, continuing the dialog, or requesting more information - all of which may or may not be kept anonymous;</p>
124
+ <p id="p-44" num="44">[0037] Figure 7a depicts an example of a user receiving a reply to his or her introduction request to a target company and includes capabilities such as accepting the request, continuing the dialog, or requesting more information - all of which may or may not be kept anonymous;</p>
125
+ <p id="p-45" num="45">[0038] Figure 8 is a flowchart depicting how the data may be gathered from the header of emails to build the relational database;</p>
126
+ <boundary-data type="header">
127
+ <confidence value="8">9</confidence>
128
+ </boundary-data>
129
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
130
+ <p id="p-46" num="46">
131
+ <page-break num="11"/>
132
+ [0039] Figure 9 is a flow chart depicting how the request may be handled; </p>
133
+ <p id="p-47" num="47">[0040] Figure 10 is a relational table for the email-header information gathered;</p>
134
+ <p id="p-48" num="48">[0041] Figure 11 is a relational table for the profiles gathered;</p>
135
+ <p id="p-49" num="49">[0042] Figure 12 is a relational tab<confidence value="8">l</confidence>
136
+ e containing the fields used in building the relational data; </p>
137
+ <p id="p-50" num="50">
138
+ <confidence value="5">[</confidence>
139
+ 0043] Figure 13 shows a system for querying a company's server or servers in order to retrieve or pull data that includes relationship content information; and [0044] Figures 14a and 14b is a flow chart depicting the process of establishing a connection between a data center and a company server in order to download or pull the data that includes the relationship content information from the company server to the data center. </p>
140
+ <heading id="h-15">DETAILED DESCRIPTION</heading>
141
+ <p id="p-51" num="51">[0045] The present invention will now be described in detail with reference to the drawings, which are provided as illustrative examples of the invention so as to enable those skilled in the art to practice the invention.</p>
142
+ <p id="p-52" num="52">Notably, the figures and examples below are not meant to limit the scope of the present invention to a single embodiment, but other embodiments are possible by way of interchange of some or all of the described or illustrated elements.</p>
143
+ <p id="p-53" num="53">Moreover, where certain elements of the present invention can be partially or fully implemented using known components, only those portions of such known <boundary-data type="header">
144
+ <confidence value="88">10</confidence>
145
+ </boundary-data>
146
+ <page-break num="12"/>
147
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
148
+ components that are necessary for an understanding of the present invention will be described, and detailed descriptions of other portions of such known components will be omitted so as not to obscure the invention. </p>
149
+ <p id="p-54" num="54">
150
+ <confidence value="5">[</confidence>
151
+ 0046] <confidence value="5">I</confidence>
152
+ n the present specification, an embodiment showing a singular component should not necessarily be limited to other embodiments including a plurality of the same component, and vice-versa, unless explicitly stated otherwise herein. Moreover, applicants do not intend for any term in the specification or claims to be ascribed an uncommon or special meaning unless explicitly set forth as such. Further, the present invention encompasses present and future known equivalents to the known components referred to herein by way of illustration. </p>
153
+ <p id="p-55" num="55">[0047] Referring to Figure 1, a system <part-num-ref name="system">100</part-num-ref>
154
+ is operatively coupled to a company's or an organization's email server <part-num-ref name="organization's email server">102.</part-num-ref>
155
+ Alternatively, a client can be operatively coupled to each user's local email account. In either case, the system <part-num-ref name="system">100</part-num-ref>
156
+ is used to view and catalog data or information found in the emails including the requestor's name, email address, and date of interaction with the target individual, as well as other information that may be relevant to gathering the data needed to assess the strength of the relationship between a particular member of the organization and the target individual that the requestor desires to meet. For simplicity, the data that is gathered is referred to herein as relationship information or relationship data and the terms are used interchangeably. </p>
157
+ <p id="p-56" num="56">[0048] Although the foregoing embodiment relates to assessing the strength of relationships between individuals within an organization and target individuals outside the organization (or target individuals within the organization as detailed below), alternative embodiments are possible within the scope of the present invention. For example, one alternative embodiment of the present <boundary-data type="header">
158
+ <confidence value="88">11</confidence>
159
+ </boundary-data>
160
+ <page-break num="13"/>
161
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
162
+ invention relates to assessing the strength of relationships between individuals within the organization and target organizations, including various departments within the target organization and various job titles or positions within the target organization. </p>
163
+ <p id="p-57" num="57">[0049] In accordance with the present invention, in the event that the user of the system requires help in using the various features of the system, the user can activate a help menu. The help feature is launched and initially starts with an audio/video tutorial of the associated page the user is currently residing on so the user can quickly get up to speed on the functionality or features associated with that given page. Once the user has gained the necessary assistance, then the user can proceed to access the functions or feature of the system <part-num-ref name="system">100</part-num-ref>
164
+ presented to the user. </p>
165
+ <p id="p-58" num="58">[0050] In one exemplary arrangement, the system <part-num-ref name="system">100</part-num-ref>
166
+ accesses the organization's server <part-num-ref name="organization's server">102</part-num-ref>
167
+ and catalogs the information contained in the headers of all the emails sent and received through the organizations servers, as set forth in Figure 8. The data acquired from the email is stored in a table as shown in Figure 10. As indicated in Figure 8, if the system <part-num-ref name="system">100</part-num-ref>
168
+ detects that the profile is not part of the profile table, step <part-num-ref name="profile table, step">802,</part-num-ref>
169
+ then the profile is added to the bProfile table of Figure 11 at step <part-num-ref name="at step">804</part-num-ref>
170
+ of Figure 8. The process then proceeds to step <part-num-ref name="process then proceeds to step">806</part-num-ref>
171
+ of Figure 8, wherein the new relation is added to Relation table of Figure 12, as indicated below. The system <part-num-ref name="system">100</part-num-ref>
172
+ is designed to read the email-header information and ignore the email message content in order to make the process of extracting the relevant data more efficient. However, it is within the scope of the present invention to design the system <part-num-ref name="system">100</part-num-ref>
173
+ to be able to read and analyze the content of the email message along with its attachments, if any. </p>
174
+ <p id="p-59" num="59">Additionally, as discussed in detail below, the system <part-num-ref name="system">100</part-num-ref>
175
+ will be able to pull the information from the server <part-num-ref name="server">102</part-num-ref>
176
+ automatically so that the information is <boundary-data type="header">
177
+ <confidence value="88">12</confidence>
178
+ </boundary-data>
179
+ <page-break num="14"/>
180
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
181
+ maintained at a remote data unit or bank <part-num-ref name="remote data unit or bank">104.</part-num-ref>
182
+ </p>
183
+ <p id="p-60" num="60">
184
+ <confidence value="5">[</confidence>
185
+ 0051<confidence value="5">]</confidence>
186
+ The system <part-num-ref name="system">100</part-num-ref>
187
+ catalogs and tabulates information relating to who is sending emails to whom, when emails have been sent, and who is replying to them. Based on the format of the names and domain names in the "send to", "cc", and "bcc" sections of the header (e.g., Lastname, Firstname <confidence value="222222222222222222222">nameformat@entity.com</confidence>
188
+ ), the organization's server <part-num-ref name="organization's server">102</part-num-ref>
189
+ knows to whom the email was sent and for which company he or she works. Once the system <part-num-ref name="system">100</part-num-ref>
190
+ has analyzed the emails, calculations can be made and displayed relating to the link-strength between. the individual within the organization and an individual outside the organization. </p>
191
+ <p id="p-61" num="61">[0052] <confidence value="5">I</confidence>
192
+ n the preferred embodiment, the information gathered by the system <part-num-ref name="system">100</part-num-ref>
193
+ is encrypted, using standard encryption technology, and sent over the <confidence value="5">I</confidence>
194
+ nternet through a secure <confidence value="22222222222222">channel/tunnel</confidence>
195
+ to a hosting facility <part-num-ref name="hosting facility">106</part-num-ref>
196
+ where a remote unit <part-num-ref name="remote unit">104</part-num-ref>
197
+ is located. At the hosting facility the information is decrypted and relationships are determined and established based on the parameters that were analyzed. Such relationships are then stored in a private data table for future access, such as the tables shown in Figure 10, <part-num-ref name="tables shown in Figure 10,">11,</part-num-ref>
198
+ and <part-num-ref name="tables shown in Figure 10, 11, and">12.</part-num-ref>
199
+ The data is then decrypted and the remote unit <part-num-ref name="remote unit">104</part-num-ref>
200
+ analyzes parameters, such as how often a member of the organization emails <confidence value="5">I</confidence>
201
+ ndividual A at Company X, how often Individual A replies back, the amount of time lapsed since the most recent email interchange, whether there have been attachments or not, and so on. </p>
202
+ <p id="p-62" num="62">[0053] By analyzing the member's email address books, the system <part-num-ref name="system">100</part-num-ref>
203
+ in conjunction with the remote unit <part-num-ref name="remote unit">104</part-num-ref>
204
+ can provide both a quantitative and a qualitative measure of the strength of the relationship between the member and a target individual, such as <confidence value="5">I</confidence>
205
+ ndividual A. For example, having a work or office number represents a certain level of familiarity, while having a home and/or cell phone numbers in the address book implies a much stronger connection. </p>
206
+ <boundary-data type="header">
207
+ <confidence value="88">13</confidence>
208
+ </boundary-data>
209
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
210
+ <p id="p-63" num="63">
211
+ <page-break num="15"/>
212
+ <confidence value="5">[</confidence>
213
+ 0054] <confidence value="5">I</confidence>
214
+ n accordance with the present invention, a requestor queries the system to determine if there is anyone, referred to as an individual or a familiar contact, with a connection to the target individual. The system identifies these familiar contacts and provides evaluation tools to the requestor that are based on relationship-analytics, which are displayed to the requestor. For example, the system performs an analysis of the responses and/or the responsiveness of each familiar contact or person in order to provide calculated performance data and ratings for each familiar contact identified as having a connection to the target, without revealing the identity of the familiar contact. For example, the rating can be numerical, such as a ratio of 7-5-3, which indicates the responsiveness of the familiar contact. Thus, in the present example, if there are four identified familiar contacts and familiar-contact-<confidence value="5">1</confidence>
215
+ has a 7-5-3 ratio, it would infer that familiar-contact-<confidence value="5">1</confidence>
216
+ received <part-num-ref name="7-5-3 ratio, it would infer that familiar-contact-1 received">7</part-num-ref>
217
+ requests, responded to <part-num-ref name="requests, responded to">5</part-num-ref>
218
+ of them, and made <part-num-ref name="of them, and made">3</part-num-ref>
219
+ introductions. Yet another evaluation parameter for the requestor may be the response time of each familiar contact. Thus, if familiar-contact-2 has a median-response-time of <part-num-ref name="median-response-time of">3</part-num-ref>
220
+ days, the requestor would know approximately how long to expect to wait for a response when reaching out to this familiar contact. In this way the requestor can determine which of the identified familiar contacts is most likely to be responsive and based on that the requestor can select from the identified familiar contacts which familiar contact best suits the requestor's needs. </p>
221
+ <p id="p-64" num="64">
222
+ <confidence value="5">[</confidence>
223
+ 0055] Other examples of information that can be used to determine the strength of a relationship include an analysis of meetings scheduled within electronic calendars such as physical meetings between individuals involved in email exchanges, scheduled phone calls, and so forth. The system could also take into consideration such data sources as phone records, and the content of Personal Digital Assistants (PDA's), including the calendars. </p>
224
+ <boundary-data type="header">
225
+ <confidence value="88">14</confidence>
226
+ </boundary-data>
227
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
228
+ <p id="p-65" num="65">
229
+ <page-break num="16"/>
230
+ [0056] <confidence value="5">I</confidence>
231
+ n an alternative embodiment, the remote unit <part-num-ref name="remote unit">104</part-num-ref>
232
+ can be a local unit that is located at the customer premises proximal to the system <part-num-ref name="system">100</part-num-ref>
233
+ and the server <part-num-ref name="server">102,</part-num-ref>
234
+ so that the information that is gathered does not need to be transmitted through the <confidence value="5">I</confidence>
235
+ nternet in encrypted format to a central storage facility. </p>
236
+ <p id="p-66" num="66">[0057] Referring now to Figure 2, once the relationships have been determined and established, the requestor can open a request by entering the relevant information into any one or more of the fields <part-num-ref name="fields">202,</part-num-ref>
237
+ <part-num-ref name="fields 202,">204,</part-num-ref>
238
+ <part-num-ref name="fields 202, 204,">206,</part-num-ref>
239
+ and <part-num-ref name="fields 202, 204, 206, and">208</part-num-ref>
240
+ of the user interface window <part-num-ref name="user interface window">200.</part-num-ref>
241
+ Information entered into one or more of the fields is sent to the system where the data is stored. Sample fields include a search for a connection to a target individual based on knowing certain attributes of the target individual including but not limited to First Name, Last Name, Company Name, Job Title, and Department. The process is demonstrated through the example that follows. </p>
242
+ <p id="p-67" num="67">[0058] <confidence value="5">E</confidence>
243
+ mployee at Company <confidence value="4">O</confidence>
244
+ wants to get in touch with Target Individual at Target Company for a business proposal. Employee doesn't have a relationship with Target Individual, nor does he have any contact information. </p>
245
+ <p id="p-68" num="68">Further, Employee doesn't know anyone who knows Target <confidence value="5">I</confidence>
246
+ ndividual. Rather than trying to cold-call Target Individual, Employee logs-on through his or her employer's intranet; alternatively the employee can log-on externally through a Virtual Private Network or VPN or at any web-browser, to utilize the system <part-num-ref name="system">100</part-num-ref>
247
+ working with the remote unit <part-num-ref name="remote unit">104</part-num-ref>
248
+ to determine if anyone at Company <confidence value="4">O</confidence>
249
+ has an existing relationship with Target Individual. </p>
250
+ <p id="p-69" num="69">[0059] Employee logs on to the system <part-num-ref name="system">100,</part-num-ref>
251
+ either through his or her intranet connection or through the internet using the company's secure connection, and goes to the "Find Connections" section, such as shown in screen <part-num-ref name="&quot;Find Connections&quot; section, such as shown in screen">200</part-num-ref>
252
+ of Figure 2. Employee enters Target <confidence value="5">I</confidence>
253
+ ndividual's name and company into the fields <part-num-ref name="fields">202</part-num-ref>
254
+ and <part-num-ref name="and">204,</part-num-ref>
255
+ respectively, of screen <part-num-ref name="and 204, respectively, of screen">200.</part-num-ref>
256
+ If Employee <boundary-data type="header">
257
+ <confidence value="88">15</confidence>
258
+ </boundary-data>
259
+ <page-break num="17"/>
260
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
261
+ didn't know that he was looking for Target Individual in particular and just wanted someone from Target Company from a specific department, he could enter that information instead in the relevant fields. Once Employee submits the information it is sent to the remote unit <part-num-ref name="remote unit">104</part-num-ref>
262
+ of Figure 1 to search for relationship owners or Links at Company <confidence value="4">O</confidence>
263
+ that have a relationship with Target Individual as detailed below. </p>
264
+ <p id="p-70" num="70">[0060] Reference is made herein to various "Links" with the understanding that the phrase "Link" is an anonymous representation of an individual. In alternative embodiment, such as a system contemplated by this invention wherein anonymity is not preserved, the name of the individual could be used instead of the word "Link".</p>
265
+ <p id="p-71" num="71">[0061] <confidence value="5">I</confidence>
266
+ n an alternative embodiment, the Employee could access the system via any type of device that allows remote access to the system, such as a PDA. In this case the Employee would log-on to the system from a remote device and after authentication of the Employee as an authorized user, the user would have access to the system to make requests or respond to received requests. </p>
267
+ <p id="p-72" num="72">[0062] Furthermore, the system <part-num-ref name="system">100</part-num-ref>
268
+ of Figure 1 can monitor the users currently logged on to the system <part-num-ref name="system">100</part-num-ref>
269
+ and, thus, be able to provide the requestor with relevant information about each potential "Link" that may be immediately available to provide an immediate response. The system <part-num-ref name="system">100</part-num-ref>
270
+ could monitor certain parameters, such as idle time or other criteria to provide accurate information to the requestor relating to the immediate availability of the "Link" to provide an immediate response to the requestor. </p>
271
+ <p id="p-73" num="73">[0063] Referring now to Figure 9, at step 1000 the system receives the request. At steps <part-num-ref name="request. At steps">1002,</part-num-ref>
272
+ <part-num-ref name="request. At steps 1002,">1008,</part-num-ref>
273
+ <part-num-ref name="request. At steps 1002, 1008,">1014,</part-num-ref>
274
+ and <part-num-ref name="request. At steps 1002, 1008, 1014, and">1020,</part-num-ref>
275
+ the system looks at the request <boundary-data type="header">
276
+ <confidence value="88">16</confidence>
277
+ </boundary-data>
278
+ <page-break num="18"/>
279
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
280
+ to determine what information, if any has been entered. If <confidence value="5">n</confidence>
281
+ o information is entered in any of the fields, then the system detects that all fields are empty, step <part-num-ref name="system detects that all fields are empty, step">1028,</part-num-ref>
282
+ and returns an error message to the requestor, step <part-num-ref name="requestor, step">1030.</part-num-ref>
283
+ </p>
284
+ <p id="p-74" num="74">[0064] If information is entered in at least one field, then the system begins evaluating the content of each of the fields. For the fields that contain information, the system searches the relevant tables, such as the bRelation table, shown as bRelation table in Figure 12, to find a corresponding data element and returns that value. If there is no information entered in the field being analyzed, then the system returns the entire range of values that corresponds to the range of possible values for that field. Once all of the fields have been evaluated, the system, at step <part-num-ref name="system, at step">1026,</part-num-ref>
285
+ finds the overlap of the returned values based on the information entered in the fields. Although only four fields are shown and discussed, it is within the scope of the invention to use any number of fie<confidence value="8">l</confidence>
286
+ ds, depending on customer needs, such as more or less than four fields. </p>
287
+ <p id="p-75" num="75">[0065] Referring now to Figure 3, with the data in the fields <part-num-ref name="fields">202,</part-num-ref>
288
+ <part-num-ref name="fields 202,">204,</part-num-ref>
289
+ <part-num-ref name="fields 202, 204,">206,</part-num-ref>
290
+ and <part-num-ref name="fields 202, 204, 206, and">208</part-num-ref>
291
+ of the request evaluated, the system can then return a user interface screen <part-num-ref name="user interface screen">300.</part-num-ref>
292
+ The user interface screen <part-num-ref name="user interface screen">300</part-num-ref>
293
+ in the preferred embodiment is a browser type interface, having a select number of links <part-num-ref name="select number of links">302.</part-num-ref>
294
+ The results are presented as links so that the identity of the person is anonymous, shown in Figure 3 by the words "Link 1,<confidence value="2">"</confidence>
295
+ "Link 2," and so on in order of link strength. </p>
296
+ <p id="p-76" num="76">[0066] In the specific example, the number of "Links" is shown to be limited to five. However, the remote unit <part-num-ref name="remote unit">104</part-num-ref>
297
+ can return to the Employee any number of links, including all of the people within Company <confidence value="4">O</confidence>
298
+ that have any relation to the Target Individual. The number of links returned can be either set by the requestor or established by the system administrator. </p>
299
+ <boundary-data type="header">
300
+ <confidence value="88">17</confidence>
301
+ </boundary-data>
302
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
303
+ <p id="p-77" num="77">
304
+ <page-break num="19"/>
305
+ [0067] Figure 3 depicts an example of how search results can be displayed anonymously. It displays the name of the target individual, in this case Target Individual, but it may disguise or not display altogether other information including but not limited to contact information on the target individual as well as the name and contact information of the individual with a relationship with the target individual (shown in this example by listing "Link 1", "Link 2", ..., "Link 5" instead of revealing the individual with a relationship with the target individual). </p>
306
+ <p id="p-78" num="78">[0068] Figure 3 also depicts an example of how search results can be displayed in order of relevance, ranked by a scoring system that may take into account some of the following or other attributes including but not limited to the frequency of interaction, recentness of the interaction, and the completeness of contact information held by the individual with a relationship to the target individual. The requestor may also be given the option to re-sort the search results based on one or more attributes that he deems most important. The system may then re-weight the scoring system accordingly for the displaying of future search results by retaining information about how the requestor prefers to have the information displayed.</p>
307
+ <p id="p-79" num="79">[0069] In accordance with the present invention, link strength is estimated based on a weighting system that analyzes for example, frequency and recentness of the interaction, address book completeness, and so on. However, if Employee wanted to, he or she could modify the ordering of results to favor, say, recentness of the interaction as the most important aspect, in that he would like to see which link has communicated with Target Individual most recently.</p>
308
+ <p id="p-80" num="80">Or perhaps Employee would like to link through the contact that he or she deems has the closest "personal tie" to Target Individual. Then, Employee would favor those links with a high score for "address book completeness." <confidence value="68">In</confidence>
309
+ <boundary-data type="header">
310
+ <confidence value="88">18</confidence>
311
+ </boundary-data>
312
+ <page-break num="20"/>
313
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
314
+ this example, Employee chooses to connect with the link suggested by the system <part-num-ref name="system">100</part-num-ref>
315
+ as determined by the remote unit <part-num-ref name="remote unit">104,</part-num-ref>
316
+ selecting the first option, "Link 1," as his intermediary. </p>
317
+ <p id="p-81" num="81">[0070] Figure 3 also depicts an example of how <confidence value="5">-</confidence>
318
+ search results can include the ability to connect with an individual with the relationship to the target individual, such as placing a button labeled "Send request" next to each of the search results. </p>
319
+ <p id="p-82" num="82">[0071] Figure 4 depicts an example of how one can request an introduction to a target individual by customizing a message, which may or may not maintain anonymity, to be sent to an individual with a relationship with the target individual. Once Employee selects "Link 1" as his choice, he is brought to an introduction request page <part-num-ref name="introduction request page">400.</part-num-ref>
320
+ In it, Employee enters his request to the anonymous "Link 1," which might read, "Hi there, this is Employee over in management. I'm trying to get in contact with Target Individual at Target Company to talk about a company <confidence value="5">I</confidence>
321
+ 'm thinking about buying.<confidence value="5586">..."</confidence>
322
+ [0072] If Employee decides to remain anonymous, then Employee would clearly not include his name. Thus, Employee would send a message without revealing his identity since the system can keep Employee's identity anonymous. In that scenario, the request might read "Hi there, I'm trying to get into contact with Target Individual at Target Company to talk about a company <confidence value="5">I</confidence>
323
+ 'd like to buy. Could you facilitate contact between us?" The email message then gets sent through the system <part-num-ref name="system">100,</part-num-ref>
324
+ which knows the identity of both the Employee and the "Link" (or the intermediary) and is capable of properly routing the message without revealing the identity of either or both. At this point, Employee still has no information about the identity of "Link<confidence value="588">1".</confidence>
325
+ </p>
326
+ <p id="p-83" num="83">[0073] Referring now to Figures 5 and <part-num-ref name="and">6,</part-num-ref>
327
+ after the request has been <boundary-data type="header">
328
+ <confidence value="88">19</confidence>
329
+ </boundary-data>
330
+ <page-break num="21"/>
331
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
332
+ made, Employee is returned to a homepage, where it shows the number of requests that are outstanding at location <part-num-ref name="number of requests that are outstanding at location">502.</part-num-ref>
333
+ On the other side of the request or transaction, once Employee files his request with the system <part-num-ref name="system">100,</part-num-ref>
334
+ the system <part-num-ref name="system">100</part-num-ref>
335
+ sends the request to the anonymous "Link <confidence value="665">1.'</confidence>
336
+ The request lands in "Link <confidence value="5">1</confidence>
337
+ 's" email inbox, and "Link 1<confidence value="5">"</confidence>
338
+ can open and read the request. The email can be set up to contain a link to the request page in Link 1's account, and clicking on it takes him or her to that page as shown in Figure 6. </p>
339
+ <p id="p-84" num="84">[0074] Figure 6 depicts an example of a request received by an individual that has a relationship with the target individual. It can display or tie into an existing incentive, or enable the two individuals to negotiate a one-time incentive. It also may provide other capabilities including accepting the request, declining the request, beginning a dialog, or requesting more information - all of which may or may not be done anonymously.</p>
340
+ <p id="p-85" num="85">[0075] Then, Link 1 can either decide to make the introduction requested by the anonymous requestor, decline the request, or ask for more information and start a dialog with the requestor. If Link <part-num-ref name="requestor. If Link">1</part-num-ref>
341
+ declines the request, then Link <confidence value="588">1's</confidence>
342
+ identity will stay hidden from the requestor, if the system is configured accordingly. Keeping Link <confidence value="5">1</confidence>
343
+ 's identity hidden prevents internal office politics from becoming inflamed as a result of the decision not to make the introduction. </p>
344
+ <p id="p-86" num="86">[0076] However, if Link 1 should decide to make the introduction, Link <part-num-ref name="introduction, Link">1</part-num-ref>
345
+ can respond to the requestor, who may or may not be anonymous, informing him or her of the plan to do so. This is clearly a streamlined version of the actual process. </p>
346
+ <p id="p-87" num="87">[0077] It is clearly contemplated that certain situations will arise where an interchange is likely to involve more than a few rounds of replies before "Link 1<confidence value="5">"</confidence>
347
+ would agree to make an introduction. Thus, the system <part-num-ref name="system">100</part-num-ref>
348
+ along with the <boundary-data type="header">
349
+ <confidence value="88">20</confidence>
350
+ </boundary-data>
351
+ <page-break num="22"/>
352
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
353
+ remote unit <part-num-ref name="remote unit">104</part-num-ref>
354
+ are platforms that enable the requestor to anonymously connect with a Link that has a relationship with the target individual. </p>
355
+ <p id="p-88" num="88">[0078] Referring now to Figure 7, which is an example of Link <confidence value="588">1's</confidence>
356
+ response to the requestor, the system <part-num-ref name="system">100</part-num-ref>
357
+ alerts the requestor that someone has replied to a request, and to follow the link into his account. He clicks on the open request to find that Link <part-num-ref name="open request to find that Link">1</part-num-ref>
358
+ has replied. The choices include accepting the request, continuing the dialog, or requesting more information - all of which may or may not be kept anonymous. In addition, it may display a set of questions used for tracking usage metrics among other things, which may or may not be customizable by the administrator. </p>
359
+ <p id="p-89" num="89">[0079] At any point, either party can close the request, and the system moves the request from the "Open Requests" section to the "Closed Requests" section as shown in Figure 5. Once the request is closed, the system can ask the requestor to rate the performance of Link <part-num-ref name="performance of Link">1.</part-num-ref>
360
+ Future requestors can use such ratings to evaluate the reliability and effectiveness of Link <part-num-ref name="reliability and effectiveness of Link">1</part-num-ref>
361
+ in making introductions. In a similar manner, Link <part-num-ref name="similar manner, Link">1</part-num-ref>
362
+ can be asked to rate the performance of the requestor as it relates to how the target individual perceived the requestor or how the requestor handled responding to the questions and directions from Link <part-num-ref name="questions and directions from Link">1.</part-num-ref>
363
+ Any number of other relevant criteria can be established to rate and evaluate the requestor and Link <part-num-ref name="requestor and Link">1</part-num-ref>
364
+ at the end of a request, regardless of whether Link <part-num-ref name="request, regardless of whether Link">1</part-num-ref>
365
+ accepted or rejected making the introduction. </p>
366
+ <p id="p-90" num="90">[0080] Accordingly, the system <part-num-ref name="system">100</part-num-ref>
367
+ along with the remote unit <part-num-ref name="remote unit">104</part-num-ref>
368
+ includes the ability to monitor actions taken with respect to new relationships that have been established as well as existing relationships. Once a relationship has been established, the requestor can set-up certain parameters that assists the requestor in maintaining the relationship for future requirements. For example, the requestor can define certain conditions, such as the time lapsed <boundary-data type="header">
369
+ <confidence value="88">21</confidence>
370
+ </boundary-data>
371
+ <page-break num="23"/>
372
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
373
+ since the last email correspondence, which the system can monitor. If the conditions defined are not satisfied or certain limits are exceeded, then the system alerts the requestor that the requestor-defined parameters are exceeded or not satisfied. Thus, through a series of alerts, the system notifies the relationship-holder to take action, such as advising the requestor to reconnect with the target individual in order to maintain and strengthen the relationship. </p>
374
+ <p id="p-91" num="91">Although the foregoing system and method are described in terms of actions taken by the requestor, any individual with access to the services contemplated by the present invention can establish criteria that can be monitored in order to receive alerts, which are in response to the criteria defined. This is done to assist the individual to maintain or enhance any relationship. Conseque<confidence value="8">n</confidence>
375
+ tly, the present invention can assist users in strengthening their weaker relationships with well-timed system generated alerts in the form of emails containing data relating to the parameters established by the user as to why the alert was triggered. </p>
376
+ <p id="p-92" num="92">[0081] The present invention is described in terms of tracking a relationship between a person within an organization and a person outside the organization. However, it is within the scope of the present invention to track and provide information about relationships of individuals within the organization and the strength of those relationships. Thus, a person within an organization may wish to be introduced to another person within the organization and, thus, request such an introduction from other members of the organization familiar with that person. Alternatively, the strength of the relationship between two individuals of an organization can be tracked, such as the relationship between the requestor and the "Link", and presented to the requestor and/or the "Link" by the system. Using this relationship strength, the requestor has another parameter to consider in determining which Link to be selected from the group of anonymous Links has the best relationship with the requestor. Similarly, the <boundary-data type="header">
377
+ <confidence value="88">22</confidence>
378
+ </boundary-data>
379
+ <page-break num="24"/>
380
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
381
+ Link receiving the request can be provided relationship information, which relates to the relationship between the Link and the requestor, as another criterion to consider in deciding whether or not to make the introduction. </p>
382
+ <p id="p-93" num="93">[0082] The present invention also tracks information relating to the frequency or acceptance rate of any individual attempting to make an introduction relative to the number of requests that the individual has received.</p>
383
+ <p id="p-94" num="94">Accordingly, the requestor can be presented with data relating to the Link's ranking or rate for accepting requests to make introductions. The criteria presented to the requestor can even be specific enough to show the acceptance rate or ranking of any Link relating to requests to make introductions to a specific individual outside the organization. Thus, the requestor can see the acceptance ranking of any individual with respect to all requests as well as with respect to the specific request for a particular individual outside of the organization<confidence value="45">:"</confidence>
384
+ As indicated above, the similar ranking information can <confidence value="88">be</confidence>
385
+ presented regarding requests for making introductions to individuals within the organization. </p>
386
+ <p id="p-95" num="95">[0083] <confidence value="5">I</confidence>
387
+ n addition to presenting data relating to the strength of relationships between individuals, the present invention tracks Link information relating to company incentives and provides such information to those being asked to make an introduction. For example, if there is an incentive for making an introduction, then that particular incentive is presented to the individual or "Link" along with the request from the requestor. Thus, the individual receiving the request is immediately made aware of an incentive for participating in and making the introduction. This incentive information, along with the data relating to the individuals that participate in the incentive, is compiled by the system for later presentation to the appropriate department within the organization that requires the information to ensure that the individual receives the incentive <boundary-data type="header">
388
+ <confidence value="88">23</confidence>
389
+ </boundary-data>
390
+ <page-break num="25"/>
391
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
392
+ promised. </p>
393
+ <p id="p-96" num="96">[0084] Referring now to Figure 13, <confidence value="6">.</confidence>
394
+ a company system <part-num-ref name="company system">1300</part-num-ref>
395
+ is in communication with a data center <part-num-ref name="data center">1310,</part-num-ref>
396
+ such that during a communication session the data center <part-num-ref name="data center">1310</part-num-ref>
397
+ can retrieve relationship information from the server or servers located at the company system <part-num-ref name="company system">1300.</part-num-ref>
398
+ It will be apparent to those skilled in the art that the function of the server can be performed by a single computer or by a group of computers. The company system <part-num-ref name="company system">1300</part-num-ref>
399
+ includes a server or a group of servers and may or may not include internal users or user terminals. The users are grouped into user groups and the number of user groups depends on system design as well as how many users each server can support. Thus, there may be just one user group supported by a single server or there may be several user groups each supported by a server. </p>
400
+ <p id="p-97" num="97">
401
+ <confidence value="68">In</confidence>
402
+ alternative embodiments, a user may have more than one user profile and, hence, more than one email address. Accordingly, the user may have a profile on more than one server. Furthermore, in another embodiment, there may be multiple servers whose users get associated together remotely by the data center <part-num-ref name="data center">1310.</part-num-ref>
403
+ Thus, the scope of the present invention includes the situation where two user identities for the same user are supported by or located on two servers or one user identity is supported by two servers. </p>
404
+ <p id="p-98" num="98">[0085] <confidence value="5">I</confidence>
405
+ n accordance with one aspect of the present invention, the program or software necessary for extracting relationship information from the company system <part-num-ref name="company system">1300</part-num-ref>
406
+ is loaded at the data center <part-num-ref name="data center">1310</part-num-ref>
407
+ thereby eliminating the need to load software into the servers or the user terminals of the company system <part-num-ref name="company system">1300.</part-num-ref>
408
+ </p>
409
+ <p id="p-99" num="99">[0086] <confidence value="5">I</confidence>
410
+ n accordance with the teaching of the present invention, the data center <part-num-ref name="data center">1310</part-num-ref>
411
+ can communicate with and retrieve or pull relationship information or data from the company system <part-num-ref name="company system">1300</part-num-ref>
412
+ without having to update each individual <boundary-data type="header">
413
+ <confidence value="88">24</confidence>
414
+ </boundary-data>
415
+ <page-break num="26"/>
416
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
417
+ user's terminal. Even though the company system <part-num-ref name="company system">1300</part-num-ref>
418
+ is shown with only one server and one user, the company system <part-num-ref name="company system">1300</part-num-ref>
419
+ includes any number of servers, each supporting a group of users. For example, there may be three servers supporting three user groups. Alternatively, there may be just one server supporting one user group. The company system <part-num-ref name="company system">1300</part-num-ref>
420
+ and the data center <part-num-ref name="data center">1310</part-num-ref>
421
+ are in communication through the <confidence value="5">I</confidence>
422
+ nternet <part-num-ref name="Internet">1320.</part-num-ref>
423
+ Additionally, a remote office or remote user <part-num-ref name="remote office or remote user">1330</part-num-ref>
424
+ also communicates with the data center <part-num-ref name="data center">1310</part-num-ref>
425
+ through the <confidence value="5">I</confidence>
426
+ nternet <part-num-ref name="Internet">1320.</part-num-ref>
427
+ The scope of the present invention includes any number of user groups supported by any number of servers as well as any number of remote users. </p>
428
+ <p id="p-100" num="100">[0087] Referring now to Figures 13 and <part-num-ref name="and">14,</part-num-ref>
429
+ the process of downloading or pulling data or relationship information from a company side server at predetermined time intervals begins at step <part-num-ref name="company side server at predetermined time intervals begins at step">1400</part-num-ref>
430
+ wherein the server of the data center <part-num-ref name="data center">1310</part-num-ref>
431
+ initiates communication with the server of the company system <part-num-ref name="company system">1300.</part-num-ref>
432
+ At step <part-num-ref name="company system 1300. At step">1402</part-num-ref>
433
+ the data center <part-num-ref name="data center">1310</part-num-ref>
434
+ accesses its database or memory that contains information about the various company systems, such as the company system <part-num-ref name="company system">1300.</part-num-ref>
435
+ The data center <part-num-ref name="data center">1310</part-num-ref>
436
+ retrieves this data or information for each company system scheduled to be queried in order to update and pull the relevant data, which can include non-relationship data as well as relationship data. At step <part-num-ref name="relevant data, which can include non-relationship data as well as relationship data. At step">1404</part-num-ref>
437
+ the data center <part-num-ref name="data center">1310</part-num-ref>
438
+ determines the type of server that is at the company from which the data will be pulled. For example, the server can be any one of the following: IMAP, Exchange, Lotus Notes, Customer Relationship Management (<confidence value="5">C</confidence>
439
+ RM), ERP, Applicant Tracking System (ATS), or a PBX interface. However, the scope of the present invention is not limited by the type of server that is present at the company system <part-num-ref name="company system">1300.</part-num-ref>
440
+ At the step <part-num-ref name="step">1406,</part-num-ref>
441
+ the data center <part-num-ref name="data center">1310</part-num-ref>
442
+ retrieves the appropriate module that includes the appropriate protocol corresponding to the protocol for communication between the data center <part-num-ref name="data center">1310</part-num-ref>
443
+ and that type of server, which is part of the company system <part-num-ref name="company system">1300.</part-num-ref>
444
+ </p>
445
+ <boundary-data type="header">
446
+ <confidence value="88">25</confidence>
447
+ </boundary-data>
448
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
449
+ <p id="p-101" num="101">
450
+ <page-break num="27"/>
451
+ [0088] At 1408 the data center <part-num-ref name="data center">1310</part-num-ref>
452
+ determines if there is one server at the company system <part-num-ref name="company system">1300</part-num-ref>
453
+ that serves all users and/or communication sessions or if there are several user groups each supported by a different server. For example, the user machine requesting information may belong to one user group that is serviced by one server at the company system <part-num-ref name="company system">1300</part-num-ref>
454
+ while a second user may belong to a second user group that is serviced by a second server at the company system <part-num-ref name="company system">1300.</part-num-ref>
455
+ If there is only one server at the company system <part-num-ref name="company system">1300</part-num-ref>
456
+ or there is only one user group supported by one server that is being queried, which would be the same server supporting other users, then at step <part-num-ref name="same server supporting other users, then at step">1410</part-num-ref>
457
+ the data center loads the global agent profile. If the user is at a remote location or office or there are multiple user groups supported by different servers, then at step <part-num-ref name="remote location or office or there are multiple user groups supported by different servers, then at step">1412</part-num-ref>
458
+ the data center loads the user agent profile specific to that user. </p>
459
+ <p id="p-102" num="102">[0089] At step 1414, the data center <part-num-ref name="data center">1310</part-num-ref>
460
+ determines if the last communication session was successful. If so, then at step <part-num-ref name="last communication session was successful. If so, then at step">1416</part-num-ref>
461
+ the data center determines if there is new information since the last time information was pulled for that server at the company system. The new information is used to update the data for the company and the users. If the last communication was not successful, then at step <part-num-ref name="last communication was not successful, then at step">1418</part-num-ref>
462
+ the data center <part-num-ref name="data center">1310</part-num-ref>
463
+ begins at the last successful communication session as determined by the time stamps associated with the server located at the company system <part-num-ref name="company system">1300</part-num-ref>
464
+ and pulls the data since the last time stamp. In one embodiment, the time stamp data is stored at data center <part-num-ref name="time stamp data is stored at data center">1310.</part-num-ref>
465
+ In an alternative embodiment the time stamp information is stored at the server located at the company system <part-num-ref name="company system">1300.</part-num-ref>
466
+ In yet another embodiment, the time stamp information is stored at the both the server located at the company system <part-num-ref name="company system">1300</part-num-ref>
467
+ and at the data center <part-num-ref name="data center">1310.</part-num-ref>
468
+ </p>
469
+ <p id="p-103" num="103">[0090] In the event the communication session is interrupted, then the <boundary-data type="header">
470
+ <confidence value="88">26</confidence>
471
+ </boundary-data>
472
+ <page-break num="28"/>
473
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
474
+ data center <part-num-ref name="data center">1310</part-num-ref>
475
+ also tracks which users have had their related data pulled and/or updated at the data center <part-num-ref name="data center">1310.</part-num-ref>
476
+ For example, if there are one hundred users in a user group and the communication session fails after the data has been pulled for the X<confidence value="66">th</confidence>
477
+ user, such as the 35<confidence value="66">th</confidence>
478
+ user, then the data center <part-num-ref name="data center">1310</part-num-ref>
479
+ will be able to start the next communication session at the (X+<confidence value="6855">1)th</confidence>
480
+ user, such as the <confidence value="8866">36th</confidence>
481
+ user. Accordingly, a failed communication session can be resumed at the point that the communication session failed. </p>
482
+ <p id="p-104" num="104">[0091] Furthermore, in an alternative embodiment, large user groups can be split into smaller user groups. The task of handling updates for the smaller user groups is split among several servers at the data center <part-num-ref name="data center">1310</part-num-ref>
483
+ resulting in quicker update time. </p>
484
+ <p id="p-105" num="105">[0092] At step 1420 the data center <part-num-ref name="data center">1310</part-num-ref>
485
+ determines if an encrypted link can be established between the data center <part-num-ref name="data center">1310</part-num-ref>
486
+ and the server at the company system <part-num-ref name="company system">1300.</part-num-ref>
487
+ If an encrypted link can not be established, then at step <part-num-ref name="encrypted link can not be established, then at step">1422</part-num-ref>
488
+ a CLEARTEXT link is established and at step <part-num-ref name="CLEARTEXT link is established and at step">1426</part-num-ref>
489
+ the data is pulled and stored as a data module at the data center <part-num-ref name="data center">1310.</part-num-ref>
490
+ If an encrypted link can be established, then at step <part-num-ref name="encrypted link can be established, then at step">1424</part-num-ref>
491
+ the data center <part-num-ref name="data center">1310</part-num-ref>
492
+ communicates with the server using an encrypted link and thereby pulls the data from the server at the company system <part-num-ref name="company system">1300</part-num-ref>
493
+ using an encrypted link and at step <part-num-ref name="encrypted link and at step">1426</part-num-ref>
494
+ the data pulled from the server is store at the data center <part-num-ref name="data center">1310.</part-num-ref>
495
+ </p>
496
+ <p id="p-106" num="106">[0093] At step 1428 the data center <part-num-ref name="data center">1310</part-num-ref>
497
+ determines if the data was pulled successfully from the server. If so, then the data center <part-num-ref name="data center">1310</part-num-ref>
498
+ time stamps this last retrieval of data from the server. On the other hand, if the last communication session did not result in a successful retrieval or pull of the data, then at step <part-num-ref name="data, then at step">1432</part-num-ref>
499
+ the data center <part-num-ref name="data center">1310</part-num-ref>
500
+ provides a time stamp and indicates that the last communication session was not successful. </p>
501
+ <boundary-data type="header">
502
+ <confidence value="88">27</confidence>
503
+ </boundary-data>
504
+ <boundary-data type="header">Express Mail No. EV 382014713US</boundary-data>
505
+ <p id="p-107" num="107">
506
+ <page-break num="29"/>
507
+ [0094] At step 1434, the data center <part-num-ref name="data center">1310</part-num-ref>
508
+ checks to determine if the information pulled was the last information for this user. If not, then the process returns to step <part-num-ref name="process returns to step">1426</part-num-ref>
509
+ to pull and save the next data associated with the user. If there are no other records or data to be retrieved, then the process continues to step <part-num-ref name="process continues to step">1436</part-num-ref>
510
+ to determine if this is the last user supported by the company system <part-num-ref name="company system">1300.</part-num-ref>
511
+ If not, then the process returns to step <part-num-ref name="process returns to step">1408</part-num-ref>
512
+ and the next user is selected. If at step <part-num-ref name="next user is selected. If at step">1436</part-num-ref>
513
+ the data center <part-num-ref name="data center">1310</part-num-ref>
514
+ determines that this is the last user, then at step <part-num-ref name="last user, then at step">1438</part-num-ref>
515
+ the data center stores the time and date of the last successful communication. At step <part-num-ref name="last successful communication. At step">1440,</part-num-ref>
516
+ the data center <part-num-ref name="data center">1310</part-num-ref>
517
+ determines if there are any other servers at this company system that need to be accessed. If so, then the next server for this company system is selected and the process returns to step <part-num-ref name="process returns to step">1404.</part-num-ref>
518
+ If at step <part-num-ref name="process returns to step 1404. If at step">1440</part-num-ref>
519
+ it is determined that this server is the last server for this company system, then at step <part-num-ref name="last server for this company system, then at step">1442</part-num-ref>
520
+ the data center <part-num-ref name="data center">1310</part-num-ref>
521
+ determines if there are other company systems that need to be queried. If so, then the process returns to step <part-num-ref name="process returns to step">1402</part-num-ref>
522
+ wherein the next company account is loaded. If there are no other company accounts or systems to access, then the process ends at step <part-num-ref name="process ends at step">1446.</part-num-ref>
523
+ </p>
524
+ <p id="p-108" num="108">[0095] The foregoing detailed description of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. The described embodiments were chosen in order to best explain the principles of the invention and its practical application to thereby enable others skilled in the art to best utilize the invention in various embodiments and with various modifications as are suited to the particular use contemplated.</p>
525
+ <boundary-data type="header">
526
+ <confidence value="88">28</confidence>
527
+ </boundary-data>
528
+ </description>
529
+ </us-patent-application>
530
+
prior_art/11120656.xml ADDED
The diff for this file is too large to render. See raw diff
 
prior_art/11124751.xml ADDED
@@ -0,0 +1,25 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11124751</doc-number>
8
+ <date>2010-08-06</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <p id="p-1" num="1">App<confidence value="7">l</confidence>
14
+ e. No. 11/124,751 Reply dated August 6, 2010 Reply to Notice to File Corrected Application Papers dated June <part-num-ref name="Reply to Notice to File Corrected Application Papers dated June">21,</part-num-ref>
15
+ <part-num-ref name="Reply to Notice to File Corrected Application Papers dated June 21,">2010</part-num-ref>
16
+ Amendments to the Specification Please add the following paragraph after paragraph [0052] of Patent Application Publication No. 2006/0105315: </p>
17
+ <p id="p-2" num="2">[0052a] Fig. 1 shows the traditional steps that are followed by educational institutions when preparing a student, course and space schedule for an upcoming academic term.</p>
18
+ <p id="p-3" num="3">Please add the following paragraph after paragraph [0088] of Patent Application Publication No. 2006/0105315:</p>
19
+ <p id="p-4" num="4">[0088a] Fig. 2 shows the addition of student-specific demand analysis and resulting opportunities for changes to the traditional method of preparing a student, course and space schedule and including integration to an HVAC control system.</p>
20
+ <p id="p-5" num="5">
21
+ <confidence value="8">2</confidence>
22
+ 2725901.01 </p>
23
+ </description>
24
+ </us-patent-application>
25
+
prior_art/11125207.xml ADDED
The diff for this file is too large to render. See raw diff
 
prior_art/11127704.xml ADDED
@@ -0,0 +1,157 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11127704</doc-number>
8
+ <date>2008-06-11</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <boundary-data type="header">Application No. 11/127,704 Docket No.: CPEPIC-6141 UT<confidence value="4">1</confidence>
14
+ US </boundary-data>
15
+ <boundary-data type="header">Amendment dated June 11, 2008 (31203/30003G)</boundary-data>
16
+ <boundary-data type="header">Reply to Office Action of December 12, 2007</boundary-data>
17
+ <heading id="h-1">AMENDMENTS TO THE SPECIFICATION</heading>
18
+ <p id="p-1" num="1">Please amend paragraph [0078<confidence value="5">]</confidence>
19
+ as follows: </p>
20
+ <p id="p-2" num="2">
21
+ <confidence value="6">-</confidence>
22
+ In a preferred embodiment of the present invention, the active agent is a monoclonal antibody, which can be natural or synthetic. Examples of monoclonal antibodies include, but are not limited to: adalimutab (available from Abbot under the tradename <confidence value="55551">Humim</confidence>
23
+ HUMIRA<confidence value="2">@</confidence>
24
+ ), abciximab (available from Centocor under the <confidence value="22222222">tradname</confidence>
25
+ <confidence value="821885">ReoPre</confidence>
26
+ tradename REOPRO<confidence value="4">®</confidence>
27
+ ); <confidence value="2222222222">daclizumab</confidence>
28
+ , (available from Roche under the trad<confidence value="566866848842">name-Zenapaz</confidence>
29
+ tradename ZenapazTM), rituximab (available from IDEC/Genentech under the <confidence value="22222222">tradname</confidence>
30
+ <confidence value="2222222">Rituxin</confidence>
31
+ <confidence value="62">or</confidence>
32
+ <confidence value="6885586">Rituxan</confidence>
33
+ tradename RITUXIN<confidence value="4">®</confidence>
34
+ or RITUXAN<confidence value="2">@</confidence>
35
+ ), basiliximab (available from Novartis under the <confidence value="22222222">tradname</confidence>
36
+ <confidence value="5686885">Simulee</confidence>
37
+ t tradename SIMULECT<confidence value="2">@</confidence>
38
+ ), palivzumab (available from Medimmune under the t<confidence value="58558885">radname-</confidence>
39
+ Synagi<confidence value="4">s</confidence>
40
+ tradename SYNAGIS<confidence value="4">®</confidence>
41
+ ), infliximab (available from Centocor under the <confidence value="22222222">tradname</confidence>
42
+ <confidence value="68884">Remie</confidence>
43
+ ade tradename REMICADE<confidence value="2">@</confidence>
44
+ ), trastuxumab (available from Genentech under the tradname <confidence value="688">Her</confidence>
45
+ ept<confidence value="66">in</confidence>
46
+ tradename HERCEPTIN<confidence value="488">®),</confidence>
47
+ gemtuzumab (available from IDEC under the t<confidence value="2655">radn</confidence>
48
+ <confidence value="6666115652">meMyletarg</confidence>
49
+ tradename MYLOTARG<confidence value="2">@</confidence>
50
+ ), alemzutumab (available from Millennium<confidence value="5">/</confidence>
51
+ ILEX under the <confidence value="22222222">tradname</confidence>
52
+ <confidence value="8685885">C-ampat</confidence>
53
+ h tradename Campath<confidence value="2">®</confidence>
54
+ ), and ibritumomab (available from IDEC under the <confidence value="22222222">tradname</confidence>
55
+ <confidence value="2222222">Zevtlin</confidence>
56
+ tradename ZEVUL<confidence value="5">I</confidence>
57
+ NTM). Gammagard Liquid (available from Baxter Healthcare Corporation, Westlake Village, Calif.) is a ready-for-use sterile, liquid preparation of highly purified and concentrated immunoglobulin G (IgG) antibodies. -<confidence value="5">-</confidence>
58
+ Please amend paragraph [00155<confidence value="2">)</confidence>
59
+ as follows: </p>
60
+ <p id="p-3" num="3">
61
+ <confidence value="4">-</confidence>
62
+ - The Example describes preparation of anti-Factor VIII monoclonal antibody microspheres with Poloxamer as solvent and microsphere formation under cooling. Anti- Factor VIII monoclonal antibody in 40 mM phosphate buffer at pH=<confidence value="885">7.0</confidence>
63
+ and at a concentration of 5.3-5.5 (no sodium chloride) was provided by Baxter Healthcare Corporation (Bioscience Division, Hayward, Calif<confidence value="5">.</confidence>
64
+ ). Anti-Factor VIII monoclonal antibody is a <confidence value="222222">murine</confidence>
65
+ monoclonal antibody with a molecular weight of approximately <part-num-ref name="molecular weight of approximately">150</part-num-ref>
66
+ kD, and is used for purification purposes. 5 mL of this monoclonal antibody at concentration of 5.3 mg/mL were filtered through 0.22 <confidence value="2">p</confidence>
67
+ m and dialyzed against 40 mM ammonium acetate buffer pH=6.5 using dialysis cassette. Protein concentration was determined by measuring absorbance at optical density of <part-num-ref name="mM ammonium acetate buffer pH=6.5 using dialysis cassette. Protein concentration was determined by measuring absorbance at optical density of">280</part-num-ref>
68
+ nm. A 10<confidence value="5">%</confidence>
69
+ solution of Poloxamer <part-num-ref name="10% solution of Poloxamer">188</part-num-ref>
70
+ NF (Lutrol F68) available from <boundary-data type="header">
71
+ <confidence value="8">2</confidence>
72
+ </boundary-data>
73
+ <page-break num="2"/>
74
+ <boundary-data type="header">Application No. 11<confidence value="5">/</confidence>
75
+ 127,704 Docket No.: CPEPIC-6141 UT<confidence value="5">I</confidence>
76
+ US </boundary-data>
77
+ <boundary-data type="header">Amendment dated (31203<confidence value="5">/</confidence>
78
+ 30003G) </boundary-data>
79
+ <boundary-data type="header">Reply to Of<confidence value="5">f</confidence>
80
+ ice Action of December 12, 2007 </boundary-data>
81
+ BASF Corporation (Florham Park, N.J.) was prepared at pH=6.0 and filtered with 0.22 micron filter. Ammonium acetate was provided by Spectrum Chemicals (Gardena, Calif.). A dialysis cassette <confidence value="552">"Sl</confidence>
82
+ ide<confidence value="2255112">,-Lyze"</confidence>
83
+ SLIDE-A-LYZER<confidence value="2">@</confidence>
84
+ , molecular weight cutoff of 10,000 and sample volume 3-12 mL was provided by Pierce (Rockford, Ill.). Aliquots of 0.5 mL of the monoclonal antibody solution were inserted into twenty 1 mL microfuge tubes. 1 mL of 10% Poloxamer solution was added to each tube containing 0.5 mL of the anti-Factor VIII (at 5.3 <confidence value="885">mg/</confidence>
85
+ mL), and the solution was mixed gently at room temperature and incubated at 29<confidence value="1">°</confidence>
86
+ C for one-half hour. -- Please amend paragraph [00160] as follows: </p>
87
+ <p id="p-4" num="4">-- This Example shows gel electrophoresis of anti-factor VIII monoclonal antibody microspheres prepared according to Example 3. Tris-Acetate gel, 3-8%, 1.5 mm x 10 wells, Tris-Acetate SDS running buffer, NuPage LDS sample buffer, Mark <part-num-ref name="wells, Tris-Acetate SDS running buffer, NuPage LDS sample buffer, Mark">12</part-num-ref>
88
+ molecular weight Standard, and "Simp<confidence value="588668">lyBlue</confidence>
89
+ <confidence value="6686">Safe</confidence>
90
+ Sta<confidence value="4">i</confidence>
91
+ " SIMPLYBLUE SAFESTA<confidence value="684">IN®</confidence>
92
+ drying solution were provided by Invitrogen (Carlsbad, Calif.). Gel electrophoresis is a widely-used analytical technique for the separation and characterization of proteins and peptides, and for the estimation of the molecular weight of protein. -<confidence value="5">-</confidence>
93
+ Please amend paragraph [00167] as follows: </p>
94
+ <p id="p-5" num="5">-- In this Example, anti-CD34 monoclonal antibody microspheres were prepared with a Poloxamer solvent, and cooling was used in microsphere formation. Anti- CD34 monoclonal antibody is a murine IgG<confidence value="4">l</confidence>
95
+ Lambda monoclonal antibody with molecular weight of approximately <part-num-ref name="murine IgGl Lambda monoclonal antibody with molecular weight of approximately">146</part-num-ref>
96
+ kD. This monoclonal antibody is used for extra-cellular therapy, such as stem cell selection, in conjunction with the <confidence value="584884">Isole*</confidence>
97
+ ISOLEX<confidence value="2">@</confidence>
98
+ <part-num-ref name="Isole*ISOLEX@">300</part-num-ref>
99
+ and sele<confidence value="4">x</confidence>
100
+ ISOLEX<confidence value="4">®</confidence>
101
+ 300i Magnetic Cell Selection System (Baxter Healthcare Corporation). </p>
102
+ <p id="p-6" num="6">Stem cell selection system and treatment is indicated for processing autologous peripheral blood progenitor cell (PBPC) products to obtain a CD34+ cell enriched population intended for hematopoietic reconstitution after myeloablative therapy in patients with CD34-negative tumors. -<confidence value="5">-</confidence>
103
+ <boundary-data type="header">
104
+ <confidence value="8">3</confidence>
105
+ </boundary-data>
106
+ <page-break num="3"/>
107
+ <boundary-data type="header">Application No. 11/127,704 Docket No.: CPEP<confidence value="5">I</confidence>
108
+ C-6141 UT<confidence value="4">1</confidence>
109
+ US </boundary-data>
110
+ <boundary-data type="header">Amendment dated (31203/30003<confidence value="68">G)</confidence>
111
+ </boundary-data>
112
+ <boundary-data type="header">Reply to Office Action of December 12, 2007</boundary-data>
113
+ Please amend paragraph [00168] as follows: </p>
114
+ <p id="p-7" num="7">-- Anti-CD34 monoclonal antibody in 0.02M sodium phosphate buffer with 0.15M sodium chloride and 0.001% Tween 80, at pH=5.5 and at a concentration of 2.3-2.5 mg/mL, was provided by Baxter Healthcare Corporation (Bioscience Division, Hayward, Calif.). 5 mL of the monoclonal antibody at a concentration of 2.2 mg/mL were filtered through 0.22 <confidence value="2">p</confidence>
115
+ m and dialyzed against 40 mM ammonium acetate buffer, pH=6.0. A 15% solution of Poloxamer <part-num-ref name="15% solution of Poloxamer">188</part-num-ref>
116
+ NF (Lutrol F68), available from BAS<confidence value="5">F</confidence>
117
+ Corporation (Florham Park, N.J.), the solution being at pH=6.0, was prepared and filtered with 0.22 <confidence value="2">p</confidence>
118
+ m filter. </p>
119
+ <p id="p-8" num="8">Ammonium Acetate was provided by Spectrum Chemicals (Gardena, Calif<confidence value="5">.</confidence>
120
+ ). A dialysis cassette <confidence value="686688565656">"Slide-yzer"</confidence>
121
+ SLIDE-A-LYZER<confidence value="2">@</confidence>
122
+ , molecular weight cutoff of 10,000 and sample volume 3-12 mL was provided by Pierce (Rockford, Ill.). Aliquots of 0.5 mL of the monoclonal antibody solution were inserted to twenty 1 mL microfuge tubes. 0.5 mL of the 15% Poloxamer solution was added to each tube containing 0.5 mL of the anti-CD34, at 2.0 mg/mL and the solution was mixed gently at room temperature and incubated at 29<confidence value="1">°</confidence>
123
+ C for one-half hour. - Please amend paragraph [00178] as follows: </p>
124
+ <p id="p-9" num="9">-- 25% PEG/PVP solution (pH=5.6) in 100 mM sodium acetate buffer was prepared and filtered through 0.22 <confidence value="2">p</confidence>
125
+ m filter. 5 mL of the monoclonal antibody at the concentration of 2.2 mg/mL was filtered through 0.22 <confidence value="2">p</confidence>
126
+ m filter and dialyzed using a dialysis cassette <confidence value="686">"Sl</confidence>
127
+ ide<confidence value="255522">,--yr"</confidence>
128
+ SLIDE-A-LYZER<confidence value="4">®</confidence>
129
+ (molecular weight cutoff of 10,000 and sample volume 3-12 mL, provided by Pierce (Rockford, Ill.)). The monoclonal antibody was dialyzed against 40 mM ammonium acetate buffer, pH=6.0. Then, <part-num-ref name="mM ammonium acetate buffer, pH=6.0. Then,">200</part-num-ref>
130
+ <confidence value="2">l</confidence>
131
+ of 25% PEG/P<confidence value="88">VP</confidence>
132
+ solution (w/v) was added to <part-num-ref name="l of 25% PEG/PVP solution (w/v) was added to">500</part-num-ref>
133
+ <confidence value="22">pl</confidence>
134
+ of the anti-CD34 monoclonal antibody at concentration of 2.0 mg/mL and the solution was mixed gently at room temperature and incubated at 29<confidence value="1">°</confidence>
135
+ C for on-half hour. The process <confidence value="88241144">eentined</confidence>
136
+ -continued as described in Example <part-num-ref name="process eentined-continued as described in Example">6,</part-num-ref>
137
+ but for the removal of PEG/PVP, as opposed to poloxamer, by washes with a 95<confidence value="5">%</confidence>
138
+ methylene chloride/5% acetone solution. - <boundary-data type="header">
139
+ <confidence value="8">4</confidence>
140
+ </boundary-data>
141
+ <page-break num="4"/>
142
+ <boundary-data type="header">Application No. 11<confidence value="5">/</confidence>
143
+ 127,704 Docket No.: CPEPIC-6141 UT<confidence value="4">1</confidence>
144
+ US </boundary-data>
145
+ <boundary-data type="header">Amendment dated (31203/30003G)</boundary-data>
146
+ <boundary-data type="header">Reply to Office Action of December 12, 2007</boundary-data>
147
+ Please amend paragraph [00196] as follows: </p>
148
+ <p id="p-10" num="10">-- This Example shows particle size distribution of AAT particles at different process scales Aerosizer data. A sample of the final AAT dry powder small spherical particles was analyzed in a TSI <confidence value="68148814">Aeresize</confidence>
149
+ AEROSIZER<confidence value="2">@</confidence>
150
+ <part-num-ref name="TSI Aeresize AEROSIZER@">3225,</part-num-ref>
151
+ which measures particle size by time of flight measurements. From these measurements, different ratios of volume diameters were calculated to demonstrate the particle size distribution of the AAT small spherical particles and were used to compare to particles fabricated by methods other than that of the present invention. -- <boundary-data type="header">
152
+ <confidence value="8">5</confidence>
153
+ </boundary-data>
154
+ </p>
155
+ </description>
156
+ </us-patent-application>
157
+
prior_art/11128970.xml ADDED
@@ -0,0 +1,897 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11128970</doc-number>
8
+ <date>2005-05-13</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <p id="p-1" num="1">EV5498<confidence value="66666">95484</confidence>
14
+ </p>
15
+ <heading id="h-1">
16
+ <confidence value="5">I</confidence>
17
+ N THE UNITED STATES PATENT AND TRADEMARK OFFICE </heading>
18
+ <heading id="h-2">APPLICATION FOR LETTERS PATENT</heading>
19
+ <heading id="h-3">UNIFIED RECORDING AND PAUSE BUFFER FORMAT</heading>
20
+ <p id="p-2" num="2">Inventor(s):</p>
21
+ <p id="p-3" num="3">Peter J. Potrebic Elizabeth Rose McEnroe Peter T. Barrett ATTORNEY'S DOCKET NO. MS1-2483US (CLIENT DOCKET NO. 312274.01) <page-break num="2"/>
22
+ </p>
23
+ <heading id="h-4">TECHNICAL FIELD</heading>
24
+ <p id="p-4" num="4">
25
+ <confidence value="5">[</confidence>
26
+ 0001<confidence value="5">]</confidence>
27
+ This invention relates to television entertainment and information architectures and, in particular, to digital video recording. </p>
28
+ <heading id="h-5">BACKGROUND</heading>
29
+ <p id="p-5" num="5">
30
+ <confidence value="5">[</confidence>
31
+ 0002<confidence value="5">1</confidence>
32
+ Digital video recorders are implemented as client devices to receive video and/or audio content in the form of broadcast and/or interactive television entertainment and information. A digital video recorder includes a hard disk memory so that a viewer can record multiple television programs and other content of interest to the viewer. A user can schedule what programs to record, and then watch them back at her leisure. </p>
33
+ <p id="p-6" num="6">[0003<confidence value="5">1</confidence>
34
+ A digital video recorder also provides the viewer with convenient pause functionality, where she can pause the broadcast of a television program and return later to watch the program, while still in progress, from the point at which it was paused. To implement this functionality, a digital video recorder includes a pause buffer to record the broadcast as it is being watched. At any point, the viewer can rewind and playback the buffered broadcast to replay a scene or watch something that she may have missed the first time. A pause buffer is typically configured as a circular, or ring, buffer on the hard disk memory and the amount of time which a television program can be delayed is dependent upon how much storage space is allocated for the pause buffer. When a pause buffer reaches capacity (e.g., after <part-num-ref name="after">30</part-num-ref>
35
+ minutes), the content corresponding to the beginning of a pause event will be overwritten. In this manner, the pause buffer functions as a sliding thirty minute recorder of the most recently displayed content. </p>
36
+ <boundary-data type="header">
37
+ <confidence value="222222222">lee@hayes</confidence>
38
+ <confidence value="14">sr</confidence>
39
+ <confidence value="2144465">o5.se25</confidence>
40
+ <confidence value="6">I</confidence>
41
+ MS <confidence value="56">1-</confidence>
42
+ 2483US<confidence value="586">/31</confidence>
43
+ 2274.01 </boundary-data>
44
+ <p id="p-7" num="7">
45
+ <page-break num="3"/>
46
+ <confidence value="5">[</confidence>
47
+ 0004<confidence value="5">]</confidence>
48
+ Although the digital video recorder stores the content on the hard disk memory for later playback, the way the two types of recorded content-pause buffer and scheduled recordings-are created, managed, and structured on the disk is quite different. This has led to some issues that impact user experience. One problem concerns channel changes. </p>
49
+ <p id="p-8" num="8">Since the pause buffer records the content received on a current channel, a change to another channel results in the pause buffer ceasing recordation of the first channel and commencing recordation of the second channel. In some cases, when a viewer changes channels, any content stored in the pause buffer is deleted (commonly referred to as "flushing" the pause buffer). Thus, an accidental channel change can cause an undesired loss of content. As a result, a viewer can only access content maintained in the pause buffer for the duration of time that the viewer watches a particular channel without changing the channel.</p>
50
+ <p id="p-9" num="9">
51
+ <confidence value="5">[</confidence>
52
+ 0005<confidence value="5">]</confidence>
53
+ Another issue arises when a user pauses a program that is back-to-back with a scheduled recording. Once the recording begins, it can be difficult to playback the previous program from the pause buffer. Another situation that poses design difficulties is the ability to take the paused content in the pause buffer and "save" it as a persistent recording to be viewed later. </p>
54
+ <p id="p-10" num="10">[0006] Users also have a poor experience when trying to record back-to-back programs on the same channel. For example, suppose a first show A ends at 9:00 pm and a second show B is scheduled to begin at 9:00 pm. In current digital video recorders, a back-to- back recording for shows A and B will make a transition precisely at 9:00 pm. However, in some situations, the first show A may not precisely end at 9:00 pm, but instead might continue past 9:00 pm (such as much as <part-num-ref name="may not precisely end at 9:00 pm, but instead might continue past 9:00 pm (such as much as">30</part-num-ref>
55
+ seconds or a minute). In this situation, the <boundary-data type="header">
56
+ <confidence value="5881">leeE</confidence>
57
+ hayes <confidence value="12">ae</confidence>
58
+ <confidence value="1151122">om.ex-m</confidence>
59
+ <confidence value="6">2</confidence>
60
+ MS<confidence value="1">I</confidence>
61
+ -2483US<confidence value="68588">/3122</confidence>
62
+ 74.01 </boundary-data>
63
+ <page-break num="4"/>
64
+ recording for show A will end too early (at 9:00 pm), and the viewer will miss the last portion of the show (e.g., <part-num-ref name="">30</part-num-ref>
65
+ to <part-num-ref name="to">60</part-num-ref>
66
+ seconds). To view the missed portion, the viewer would need to watch the beginning portion of the second show B, which was to start at 9:00 pm, but effectively started after 9:00 pm (e.g., at 9:00:30 or 9:01:00). In other situations, show A may end too early, before 9:00 pm, resulting in an earlier start for show B. This results in the reverse problem, where <confidence value="5">.</confidence>
67
+ the first portion of show B is at the tail end of the recording for show A. These scenarios for back-to-back recording can result in a confusing, and perhaps frustrating user experience. </p>
68
+ <p id="p-11" num="11">[0007] Accordingly, for television-based entertainment, there is a need for techniques to improve the way pause buffers and recorded programs are managed.</p>
69
+ <heading id="h-6">SUMMARY</heading>
70
+ <p id="p-12" num="12">
71
+ <confidence value="5">[</confidence>
72
+ 0008<confidence value="2">]</confidence>
73
+ A unified recording format allows both recorded programs and pause buffered broadcasts to be stored in memory as a common virtual stream. As content is received on a channel, it is placed into the virtual stream with newer content at the start of the stream and progressively aging content migrating farther downstream. A front section of the stream effectively operates as a pause buffer, as the currently tuned broadcast program is recorded in this section and is responsive to pause/resume commands. Recorded programs are also stored as part of the same virtual stream. Pointers are used to identify the boundaries of the pause buffer, as well as the beginning and end of each recorded program in the virtual stream. </p>
74
+ <p id="p-13" num="13">
75
+ <confidence value="5">[</confidence>
76
+ 0009] In this manner, data in the pause buffer and data in a recorded program are managed in a unified manner, without any distinction between the two. The unified <boundary-data type="header">
77
+ <confidence value="588">lee</confidence>
78
+ hayes <confidence value="1">e</confidence>
79
+ <confidence value="2121212">so-amez</confidence>
80
+ <confidence value="6">3</confidence>
81
+ MS 1-2483US<confidence value="58">/3</confidence>
82
+ 12274.01 </boundary-data>
83
+ <page-break num="5"/>
84
+ format removes barriers between recorded content and paused buffered content that, in the past, have resulted in clumsy user experiences. The unified format allows users to save pause buffer content indefinitely, record back-to-back programs without conflicts, and facilitate channel change without permanent lose of previously buffered content. </p>
85
+ <heading id="h-7">BRIEF DESCRIPTION OF THE CONTENTS</heading>
86
+ <p id="p-14" num="14">
87
+ <confidence value="5">[</confidence>
88
+ 00010] The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items. </p>
89
+ <p id="p-15" num="15">
90
+ <confidence value="5">[</confidence>
91
+ 00011] Fig. 1 illustrates an exemplary television entertainment architecture in which the unified recording and pause buffer format can be implemented. </p>
92
+ <p id="p-16" num="16">[00012] Fig. 2 illustrates an example client device, a television, and various input devices that interact with the client device.</p>
93
+ <p id="p-17" num="17">[00013] Fig. 3 illustrates the client device implemented as part of a digital video recording system that stores recorded programs and paused broadcast programs within a unified virtual stream.</p>
94
+ <p id="p-18" num="18">[00014] Fig. 4 illustrates components of the digital video recording system of Fig.</p>
95
+ <p id="p-19" num="19">3 to demonstrate how recorded programs and paused broadcasts are stored in a unified format within a data structure.</p>
96
+ <p id="p-20" num="20">
97
+ <confidence value="5">[</confidence>
98
+ 00015] Figs. 5-9 show exemplary scenarios for storing recordings and paused broadcasts within a common virtual stream. </p>
99
+ <boundary-data type="header">
100
+ <confidence value="222222222">lee@hayes</confidence>
101
+ <confidence value="1">p</confidence>
102
+ <confidence value="41">se</confidence>
103
+ <confidence value="21">on</confidence>
104
+ <confidence value="5152">-92s</confidence>
105
+ 4 MS<confidence value="4">1</confidence>
106
+ -2483US<confidence value="68">/3</confidence>
107
+ 12274.01 </boundary-data>
108
+ <p id="p-21" num="21">
109
+ <page-break num="6"/>
110
+ <confidence value="5">[</confidence>
111
+ 00016<confidence value="5">]</confidence>
112
+ Fig. 10 is a flow diagram that illustrates a process for operating a digital video recording system such that recorded programs and paused broadcasts are stored in a unified format. </p>
113
+ <heading id="h-8">DETAILED DESCRIPTION</heading>
114
+ <p id="p-22" num="22">
115
+ <confidence value="5">[</confidence>
116
+ 00017] This disclosure is directed to a unified recording format that allows both scheduled recordings and paused broadcasts to be stored as a single virtual stream in memory. As content is received on a channel, it is continuously placed into the virtual stream. This forms a historically-arranged stream of content, with newer content at the start of the stream and aging content increasingly farther downstream. A beginning portion of the virtual stream effectively operates as a pause buffer. As the live program is received, it is recorded at the start of the virtual stream and available for playback in response to pause/resume commands. A pointer may be used to identify a current playback location in the stream. If a person is watching live TV, for example, the current playback location is at the start of the stream. If the current location is three minutes delayed, the pointer defines that location in the stream. When the person is viewing TV in normal "play" mode, the current playback location is moving forward in the stream in real time (i.e., one second of video for each second of real time). If the video is paused, the current playback location pointer is frozen, while the stream keeps growing at the front to buffer the live broadcast. The pointer can be moved backwards and forwards in the stream at faster rates in response to rewind and fast forward commands. </p>
117
+ <p id="p-23" num="23">
118
+ <confidence value="86">[0</confidence>
119
+ 0018] Recorded programs are also stored as part of the virtual stream. When the user records a program (e.g., as part of a scheduled recording or pressing a record button), <boundary-data type="header">
120
+ <confidence value="222222222">lee@hayes</confidence>
121
+ <confidence value="11">us</confidence>
122
+ <confidence value="212141">-m-use</confidence>
123
+ 5 <confidence value="554">MS1</confidence>
124
+ -24<confidence value="555514">83US/3</confidence>
125
+ 12274.<confidence value="65">01</confidence>
126
+ </boundary-data>
127
+ <page-break num="7"/>
128
+ the program is placed into the same virtual stream. Pairs of start and end pointers identify<confidence value="5">'</confidence>
129
+ the beginning and end of the recorded programs in the virtual stream. As programs age with the passage of time, the recorded programs migrate farther downstream in the virtual stream. Over time, there may develop gaps in the stream that contain content which is not part of the recorded program and not part of the pause buffer region of the virtual stream. Such gaps are identified and deleted so that the underlying storage can be reused by the system. </p>
130
+ <p id="p-24" num="24">
131
+ <confidence value="5">[</confidence>
132
+ 00019] The following discussion is directed to television-based entertainment and information systems, such as interactive TV networks, cable networks that utilize electronic program guides, and Web-enabled TV networks. Client devices in such systems include full-resource clients with substantial memory and processing resources, such as TV-enabled personal computers and digital video recorders equipped with hard disk memories. While the described techniques can be used in any of these systems and for any types of client devices, they are described in the context of the following exemplary environment. </p>
133
+ <p id="p-25" num="25">Exemplary System Architecture <confidence value="5">[</confidence>
134
+ 00020] Fig. 1 illustrates an exemplary television entertainment architecture <part-num-ref name="exemplary television entertainment architecture">100</part-num-ref>
135
+ in which the unified recording and pause buffer format can be implemented. Architecture <part-num-ref name="unified recording and pause buffer format can be implemented. Architecture">100</part-num-ref>
136
+ facilitates distribution of content and program data to multiple viewers, and includes one or more content providers <part-num-ref name="facilitates distribution of content and program data to multiple viewers, and includes one or more content providers">102,</part-num-ref>
137
+ one or more program data providers <part-num-ref name="facilitates distribution of content and program data to multiple viewers, and includes one or more content providers 102, one or more program data providers">104,</part-num-ref>
138
+ and a content distribution system <part-num-ref name="content distribution system">106.</part-num-ref>
139
+ Multiple client devices 108(1), 108(2), ..., 108(<confidence value="5">N</confidence>
140
+ ) are coupled to the content distribution system <part-num-ref name="content distribution system">106</part-num-ref>
141
+ via a broadcast network <part-num-ref name="broadcast network">110.</part-num-ref>
142
+ </p>
143
+ <boundary-data type="header">
144
+ <confidence value="588">lee</confidence>
145
+ <confidence value="2222222">hayesec</confidence>
146
+ <confidence value="251222">w.m295</confidence>
147
+ 6 MS 1-2483US<confidence value="586">/31</confidence>
148
+ 2274.0<confidence value="5">1</confidence>
149
+ </boundary-data>
150
+ <p id="p-26" num="26">
151
+ <page-break num="8"/>
152
+ [00021] Content provider 102 includes a content server <part-num-ref name="content server">112</part-num-ref>
153
+ and stored content <part-num-ref name="and stored content">114,</part-num-ref>
154
+ such as movies, television programs, commercials, music, and other audio and/or video content. Content server <part-num-ref name="and stored content 114, such as movies, television programs, commercials, music, and other audio and/or video content. Content server">112</part-num-ref>
155
+ controls distribution of the stored content <part-num-ref name="stored content">114</part-num-ref>
156
+ from content provider <part-num-ref name="from content provider">102</part-num-ref>
157
+ to the content distribution system <part-num-ref name="content distribution system">106.</part-num-ref>
158
+ Additionally, content server <part-num-ref name="content distribution system 106. Additionally, content server">112</part-num-ref>
159
+ controls distribution of live content (e.g., content that was not previously stored, such as live feeds) and/or content stored at other locations to the content distribution system <part-num-ref name="content distribution system">106.</part-num-ref>
160
+ </p>
161
+ <p id="p-27" num="27">
162
+ <confidence value="5">[</confidence>
163
+ 00022] Program data provider 104 includes an electronic program guide (EPG) database <part-num-ref name="electronic program guide (EPG) database">116</part-num-ref>
164
+ and an EPG server <part-num-ref name="EPG server">118.</part-num-ref>
165
+ The EPG database <part-num-ref name="EPG database">116</part-num-ref>
166
+ stores electronic files of program data that is used to generate an electronic program guide (or, "EPG", "program guide"). Program data (or, "EPG data") includes program titles, ratings, characters, descriptions, actor names, station identifiers, channel identifiers, schedule information, and so on. The EPG server <part-num-ref name="EPG server">118</part-num-ref>
167
+ processes the program data prior to distribution. The processing may involve any number of techniques to reduce, modify, or enhance the program data. Such processes might include selection of content, content compression, format modification, and the like. The EPG server <part-num-ref name="EPG server">118</part-num-ref>
168
+ generates a published version of the program data, which contains programming information for all channels for one or more days. The EPG server <part-num-ref name="EPG server">118</part-num-ref>
169
+ controls distribution of the published version of the program data from program data provider <part-num-ref name="program data from program data provider">104</part-num-ref>
170
+ to the content distribution system <part-num-ref name="content distribution system">106</part-num-ref>
171
+ using, for example, a file transfer protocol (FTP) over a TCP/IP network (e.g., Internet, UNIX, etc.). Further, the published version of the program data can be transmitted from program data provider <part-num-ref name="program data can be transmitted from program data provider">104</part-num-ref>
172
+ via a satellite directly to a client device, such as device 108(1). </p>
173
+ <p id="p-28" num="28">[00023] Content distribution system 106 includes a broadcast transmitter <part-num-ref name="broadcast transmitter">120,</part-num-ref>
174
+ one or more content processors <part-num-ref name="broadcast transmitter 120, one or more content processors">122,</part-num-ref>
175
+ and one or more program data processors <part-num-ref name="broadcast transmitter 120, one or more content processors 122, and one or more program data processors">124.</part-num-ref>
176
+ </p>
177
+ <boundary-data type="header">
178
+ <confidence value="222222222">lee(hayes</confidence>
179
+ <confidence value="2">*</confidence>
180
+ <confidence value="2515611">o-79258</confidence>
181
+ <confidence value="2">7</confidence>
182
+ MS<confidence value="4">1</confidence>
183
+ -2483US<confidence value="685">/31</confidence>
184
+ 2274.<confidence value="56">01</confidence>
185
+ </boundary-data>
186
+ <p id="p-29" num="29">
187
+ <page-break num="9"/>
188
+ Broadcast transmitter 120 broadcasts signals, such as cable television signals, across broadcast network <part-num-ref name="broadcasts signals, such as cable television signals, across broadcast network">110.</part-num-ref>
189
+ Broadcast network <part-num-ref name="broadcasts signals, such as cable television signals, across broadcast network 110. Broadcast network">110</part-num-ref>
190
+ can include a cable television network, RF, microwave, satellite, <confidence value="222222">and/or</confidence>
191
+ data network, such as the Internet, and may also include wired or wireless media using any broadcast format or broadcast protocol. Additionally, broadcast network <part-num-ref name="Internet, and may also include wired or wireless media using any broadcast format or broadcast protocol. Additionally, broadcast network">110</part-num-ref>
192
+ can be any type of network, using any type of network topology and any network communication protocol, and can be represented or otherwise implemented as a combination of two or more networks. </p>
193
+ <p id="p-30" num="30">
194
+ <confidence value="5">[</confidence>
195
+ 00024] A content processor <part-num-ref name="content processor">122</part-num-ref>
196
+ processes the content received from content provider <part-num-ref name="content received from content provider">102</part-num-ref>
197
+ prior to transmitting the content across broadcast network <part-num-ref name="content across broadcast network">110.</part-num-ref>
198
+ Similarly, a program data processor <part-num-ref name="program data processor">124</part-num-ref>
199
+ processes the program data received from program data provider <part-num-ref name="program data received from program data provider">104</part-num-ref>
200
+ prior to transmitting the program data across broadcast network <part-num-ref name="program data across broadcast network">110.</part-num-ref>
201
+ A particular content processor <part-num-ref name="particular content processor">122</part-num-ref>
202
+ may encode, or otherwise process, the received content into a format that is understood by the multiple client devices 108(1), 108(2), ..., 108(N) coupled to broadcast network <part-num-ref name="multiple client devices 108(1), 108(2), ..., 108(N) coupled to broadcast network">110.</part-num-ref>
203
+ Although Fig. 1 shows a single content provider <part-num-ref name="single content provider">102,</part-num-ref>
204
+ a single program data provider <part-num-ref name="single program data provider">104,</part-num-ref>
205
+ and a single content distribution system <part-num-ref name="single content distribution system">106,</part-num-ref>
206
+ the exemplary architecture <part-num-ref name="exemplary architecture">100</part-num-ref>
207
+ can include any number of content providers <confidence value="222222">and/or</confidence>
208
+ program data providers coupled to any number of content distribution systems. </p>
209
+ <p id="p-31" num="31">[00025] Content distribution system 106 is representative of a headend service, or network operator, which provides EPG data, as well as content, to multiple subscribers.</p>
210
+ <p id="p-32" num="32">Each content distribution system 106 may receive a slightly different version of the program data that takes into account different programming preferences and lineups. The EPG server <part-num-ref name="EPG server">118</part-num-ref>
211
+ creates different versions of EPG data (e.g., different versions of a program guide) that include those channels of relevance to respective headend services, <boundary-data type="header">
212
+ <confidence value="222222222">lee@hayes</confidence>
213
+ <confidence value="11">pk</confidence>
214
+ <confidence value="121652">so8-m8</confidence>
215
+ MS<confidence value="4">1</confidence>
216
+ -2483US<confidence value="58688">/3122</confidence>
217
+ 74.0<confidence value="5">1</confidence>
218
+ </boundary-data>
219
+ <page-break num="10"/>
220
+ and the content distribution system <part-num-ref name="content distribution system">106</part-num-ref>
221
+ transmits the EPG data to the multiple client devices 108(1), 108(2), ..., 108(N). In one implementation, for example, content distribution system <part-num-ref name="multiple client devices 108(1), 108(2), ..., 108(N). In one implementation, for example, content distribution system">106</part-num-ref>
222
+ utilizes a carousel file system to repeatedly broadcast the EPG data over an out-of-band (<confidence value="4">O</confidence>
223
+ OB) channel to the client devices <part-num-ref name="client devices">108.</part-num-ref>
224
+ </p>
225
+ <p id="p-33" num="33">
226
+ <confidence value="5">[</confidence>
227
+ 00026] Client devices 108 can be implemented in a number of ways. For example, a client device 108(1) receives broadcast content from a satellite-based transmitter via a satellite dish <part-num-ref name="satellite dish">126.</part-num-ref>
228
+ Client device 108(1) is also referred to as a set-top box or a satellite receiving device. Client device 108(<confidence value="5">1</confidence>
229
+ ) is coupled to a television 128(<confidence value="68">1)</confidence>
230
+ for presenting the content received by the client device (e.g., audio data and video data), as well as a graphical user interface. A particular client device <part-num-ref name="particular client device">108</part-num-ref>
231
+ can be coupled to any number of televisions <part-num-ref name="can be coupled to any number of televisions">128</part-num-ref>
232
+ <confidence value="222222">and/or</confidence>
233
+ similar devices that can be implemented to display or otherwise render content. Similarly, any number of client devices <part-num-ref name="and/or similar devices that can be implemented to display or otherwise render content. Similarly, any number of client devices">108</part-num-ref>
234
+ can be coupled to a single television <part-num-ref name="single television">128.</part-num-ref>
235
+ </p>
236
+ <p id="p-34" num="34">
237
+ <confidence value="5">[</confidence>
238
+ 00027] Client device 108(2) is also coupled to receive broadcast content from broadcast network 110 and provide the received content to associated television 128(2). </p>
239
+ <p id="p-35" num="35">Client device 108(2) is representative of a standalone cable set-top box. Client device 108(N) is an example of a combination television <part-num-ref name="combination television">130</part-num-ref>
240
+ and integrated set-top box <part-num-ref name="and integrated set-top box">132.</part-num-ref>
241
+ In this example, the various components and functionality of the set-top box are integrated into the television, rather than using two separate devices. The set-top box integrated into the television can receive broadcast signals via a satellite dish (similar to satellite dish <part-num-ref name="satellite dish (similar to satellite dish">126)</part-num-ref>
242
+ and/or via broadcast network <part-num-ref name="and/or via broadcast network">110.</part-num-ref>
243
+ In alternate implementations, client devices <part-num-ref name="and/or via broadcast network 110. In alternate implementations, client devices">108</part-num-ref>
244
+ may receive broadcast signals via the Internet or any other broadcast medium, such as back channel <part-num-ref name="Internet or any other broadcast medium, such as back channel">134</part-num-ref>
245
+ which can be implemented as an Internet prot<confidence value="8">o</confidence>
246
+ col (IP) connection using <boundary-data type="header">
247
+ <confidence value="222222222">lee@hayes</confidence>
248
+ <confidence value="5">e</confidence>
249
+ <confidence value="5">.</confidence>
250
+ MS1-<confidence value="5">2</confidence>
251
+ 483US<confidence value="585">/31</confidence>
252
+ 2274.0<confidence value="5">1</confidence>
253
+ </boundary-data>
254
+ <page-break num="11"/>
255
+ a modem connection and conventional telephone line, for example. Further, back channel <part-num-ref name="modem connection and conventional telephone line, for example. Further, back channel">134</part-num-ref>
256
+ provides an alternate communication link between each of the client devices <part-num-ref name="client devices">108,</part-num-ref>
257
+ and between the client devices <part-num-ref name="client devices">108</part-num-ref>
258
+ and the content distribution system <part-num-ref name="content distribution system">106.</part-num-ref>
259
+ </p>
260
+ <p id="p-36" num="36">
261
+ <confidence value="5">[</confidence>
262
+ 00028<confidence value="5">]</confidence>
263
+ Each client device 108 can run an electronic program guide (EPG) application that utilizes the program data. An EPG application enables a television viewer to navigate through an onscreen program guide and locate television shows and other broadcast content of interest to the viewer. With an EPG application, the television viewer can look at schedules of current and future programming, set reminders for upcoming programs, and/or enter instructions to record one or more television shows. </p>
264
+ <p id="p-37" num="37">
265
+ <confidence value="5">[</confidence>
266
+ 00029] One or more of the client devices <part-num-ref name="client devices">108</part-num-ref>
267
+ are also equipped with functionality to operate as a digital video recorder (DVR). These devices include a hard disk memory or other type of permanent storage and a DVR application that manages recordation of programs on the memory as well as pause buffer functionality. The D<confidence value="5">V</confidence>
268
+ R application employs a unified format that integrates recorded programs and paused broadcasts within a common virtual stream on the disk memory. This is described below in more detail. </p>
269
+ <p id="p-38" num="38">
270
+ <confidence value="5">[</confidence>
271
+ 00030] The exemplary architecture <part-num-ref name="exemplary architecture">100</part-num-ref>
272
+ also includes stored on-demand content <part-num-ref name="also includes stored on-demand content">136,</part-num-ref>
273
+ such as Video On-Demand (VOD) movie content. The stored on-demand content can be viewed with a television <part-num-ref name="television">128</part-num-ref>
274
+ via a client device <part-num-ref name="client device">108</part-num-ref>
275
+ through an onscreen movie guide, for example, and a viewer can enter instructions to stream a particular movie, or other stored content, down to a corresponding client device <part-num-ref name="corresponding client device">108.</part-num-ref>
276
+ </p>
277
+ <boundary-data type="header">
278
+ <confidence value="222222222">lee~hayes</confidence>
279
+ <confidence value="25">pe</confidence>
280
+ <confidence value="522">.39</confidence>
281
+ <confidence value="8">1</confidence>
282
+ 0 MS<confidence value="5">1</confidence>
283
+ -2483US <confidence value="8">/</confidence>
284
+ <confidence value="86">31</confidence>
285
+ 2274.<confidence value="86">01</confidence>
286
+ </boundary-data>
287
+ <p id="p-39" num="39">
288
+ <page-break num="12"/>
289
+ Exemplary Client Device with DVR Functionality <confidence value="5">[</confidence>
290
+ 00031<confidence value="5">]</confidence>
291
+ Fig. 2 illustrates an exemplary implementation <part-num-ref name="exemplary implementation">200</part-num-ref>
292
+ of a client device <part-num-ref name="client device">108</part-num-ref>
293
+ shown as a standalone unit that connects to a television <part-num-ref name="television">128.</part-num-ref>
294
+ Client device <part-num-ref name="television 128. Client device">108</part-num-ref>
295
+ can be implemented in any number of embodiments, including as a set-top box, a satellite receiver, a TV recorder with a hard disk, a digital video recorder (DVR) and playback system, a game console, an information appliance, and so forth. </p>
296
+ <p id="p-40" num="40">
297
+ <confidence value="5">[</confidence>
298
+ 00032] Client device 108 includes a wireless port <part-num-ref name="wireless port">202,</part-num-ref>
299
+ such as an infrared (IR) or Bluetooth wireless port, for receiving wireless communications from a remote control device <part-num-ref name="remote control device">204,</part-num-ref>
300
+ a handheld input device <part-num-ref name="handheld input device">206,</part-num-ref>
301
+ or any other wireless device, such as a wireless keyboard (not shown). Handheld input device <part-num-ref name="wireless keyboard (not shown). Handheld input device">206</part-num-ref>
302
+ can be a personal digital assistant (PDA), handheld computer, wireless phone, or the like. Additionally, a wired keyboard <part-num-ref name="wired keyboard">208</part-num-ref>
303
+ can be coupled to communicate with client device <part-num-ref name="can be coupled to communicate with client device">108.</part-num-ref>
304
+ In alternate embodiments, remote control device <part-num-ref name="can be coupled to communicate with client device 108. In alternate embodiments, remote control device">204,</part-num-ref>
305
+ handheld device <part-num-ref name="can be coupled to communicate with client device 108. In alternate embodiments, remote control device 204, handheld device">206,</part-num-ref>
306
+ and/or keyboard <part-num-ref name="can be coupled to communicate with client device 108. In alternate embodiments, remote control device 204, handheld device 206, and/or keyboard">208</part-num-ref>
307
+ may use an RF communication link or other mode of transmission to communicate with client device <part-num-ref name="RF communication link or other mode of transmission to communicate with client device">108.</part-num-ref>
308
+ </p>
309
+ <p id="p-41" num="41">
310
+ <confidence value="5">[</confidence>
311
+ 00033] Client device 108 receives one or more broadcast signals <part-num-ref name="receives one or more broadcast signals">210</part-num-ref>
312
+ from one or more broadcast sources, such as from a satellite or from a broadcast network, such as broadcast network <part-num-ref name="broadcast network, such as broadcast network">110</part-num-ref>
313
+ (Fig. 1). Client device <part-num-ref name="(Fig. 1). Client device">108</part-num-ref>
314
+ includes hardware <confidence value="222222">and/or</confidence>
315
+ software for receiving and decoding broadcast signal <part-num-ref name="includes hardware and/or software for receiving and decoding broadcast signal">210,</part-num-ref>
316
+ such as an NTSC, PAL, SECAM, or other TV system video signal. Client device <part-num-ref name="NTSC, PAL, SECAM, or other TV system video signal. Client device">108</part-num-ref>
317
+ also includes hardware and/or software for providing the user with a graphical user interface by which the user can, for example, access various network services, configure the client device <part-num-ref name="client device">108,</part-num-ref>
318
+ and perform other functions. </p>
319
+ <boundary-data type="header">
320
+ <confidence value="222222222">lee@hayes</confidence>
321
+ <confidence value="1">a</confidence>
322
+ <confidence value="655255282">59.-4.92%</confidence>
323
+ <confidence value="52">11</confidence>
324
+ MS<confidence value="86">1-</confidence>
325
+ 2483<confidence value="88">US</confidence>
326
+ <confidence value="68">/3</confidence>
327
+ 12274.01 </boundary-data>
328
+ <p id="p-42" num="42">
329
+ <page-break num="13"/>
330
+ <confidence value="5">[</confidence>
331
+ 00034<confidence value="5">]</confidence>
332
+ Client device 108 can communicate with other devices via one or more connections including a conventional telephone line <part-num-ref name="conventional telephone line">212,</part-num-ref>
333
+ an ISDN link <part-num-ref name="ISDN link">214,</part-num-ref>
334
+ a cable link <part-num-ref name="cable link">216,</part-num-ref>
335
+ an Ethernet link <part-num-ref name="Ethernet link">218,</part-num-ref>
336
+ a DSL link <part-num-ref name="DSL link">220,</part-num-ref>
337
+ and the like. Client device <part-num-ref name="like. Client device">108</part-num-ref>
338
+ may use any one or more of the various communication links 212-220 at a particular instant to communicate with any number of other devices. </p>
339
+ <p id="p-43" num="43">
340
+ <confidence value="5">[</confidence>
341
+ 00035] Client device 108 generates video signal(s) <part-num-ref name="generates video signal(s)">222</part-num-ref>
342
+ and audio signal(s) <part-num-ref name="and audio signal(s)">224,</part-num-ref>
343
+ both of which are communicated to television <part-num-ref name="and audio signal(s) 224, both of which are communicated to television">128.</part-num-ref>
344
+ The video signals and audio signals can be communicated from client device <part-num-ref name="video signals and audio signals can be communicated from client device">108</part-num-ref>
345
+ to television <part-num-ref name="to television">128</part-num-ref>
346
+ via an RF (radio frequency) link, S-video link, composite video link, component video link, or other communication link. Although not shown in Fig. 2, client device <part-num-ref name="RF (radio frequency) link, S-video link, composite video link, component video link, or other communication link. Although not shown in Fig. 2, client device">108</part-num-ref>
347
+ may include one or more lights or other indicators identifying the current status of the device. Additionally, the client device may include one or more control buttons, switches, or other selectable controls for controlling operation of the device. </p>
348
+ <p id="p-44" num="44">
349
+ <confidence value="5">[</confidence>
350
+ 00036] Client device 108 is also equipped with a hard disk memory and functionality to operate as a digital video recorder. The client device <part-num-ref name="client device">108</part-num-ref>
351
+ can record programs received as a broadcast signal <part-num-ref name="broadcast signal">210,</part-num-ref>
352
+ or received over other communication connections, such as cable <part-num-ref name="broadcast signal 210, or received over other communication connections, such as cable">216</part-num-ref>
353
+ and DSL <part-num-ref name="and DSL">220.</part-num-ref>
354
+ The client device <part-num-ref name="client device">108</part-num-ref>
355
+ is able to record these programs and additionally pause and resume the live broadcasts of these programs. </p>
356
+ <p id="p-45" num="45">The device 108 stores the scheduled recordings and paused broadcasts in a unified format as a single virtual stream. As content is received on a channel, it is added to the virtual stream to create an arbitrary-length stream of historically-aged content, where newer content is nearer to the front of the stream and older content is downstream. Currently <confidence value="5">-</confidence>
357
+ received content is stored at the front of the stream. In this manner, the front region of the <boundary-data type="header">lee <confidence value="5">@</confidence>
358
+ hayes <confidence value="155241421222">peesoms-s-sm</confidence>
359
+ <confidence value="8">1</confidence>
360
+ 2 MS<confidence value="4">1</confidence>
361
+ -2483US<confidence value="5">/</confidence>
362
+ 312274.<confidence value="68">01</confidence>
363
+ </boundary-data>
364
+ <page-break num="14"/>
365
+ stream forms a pause buffer. As the new content ages beyond a period suitable for temporarily paused content (e.g., <part-num-ref name="">30</part-num-ref>
366
+ minutes, <part-num-ref name="minutes,">60</part-num-ref>
367
+ minutes, <part-num-ref name="minutes,">90</part-num-ref>
368
+ minutes, etc.), the content can either be marked as a recording and saved indefinitely or reclaimed by the system. </p>
369
+ <p id="p-46" num="46">
370
+ <confidence value="5">[</confidence>
371
+ 00037<confidence value="5">1</confidence>
372
+ Fig. 3 illustrates components of the client device <part-num-ref name="client device">108</part-num-ref>
373
+ in more detail. The client device <part-num-ref name="client device">108</part-num-ref>
374
+ is shown within the context of an exemplary digital video recording system <part-num-ref name="exemplary digital video recording system">300</part-num-ref>
375
+ that includes selected components of television architecture <part-num-ref name="that includes selected components of television architecture">100,</part-num-ref>
376
+ such as the client device <part-num-ref name="client device">108,</part-num-ref>
377
+ a television <part-num-ref name="television">128,</part-num-ref>
378
+ and audio/video content <part-num-ref name="television 128, and audio/video content">114</part-num-ref>
379
+ received from the content providers via broadcast network <part-num-ref name="content providers via broadcast network">110.</part-num-ref>
380
+ Client device <part-num-ref name="content providers via broadcast network 110. Client device">108</part-num-ref>
381
+ includes components to implement a digital video recording system that stores both the scheduled recordings and paused programs in a unified format. </p>
382
+ <p id="p-47" num="47">
383
+ <confidence value="5">[</confidence>
384
+ 00038<confidence value="5">1</confidence>
385
+ Client device 108 includes one or more tuners <part-num-ref name="includes one or more tuners">302</part-num-ref>
386
+ which are representative of one or more in-band tuners that tune to various frequencies or channels to receive broadcast television signals, as well as an out-of-band tuner that tunes to the broadcast channel over which the EPG data is broadcast to client device <part-num-ref name="EPG data is broadcast to client device">108.</part-num-ref>
387
+ One or more processors <part-num-ref name="EPG data is broadcast to client device 108. One or more processors">304</part-num-ref>
388
+ process various instructions to control the operation of the client device <part-num-ref name="client device">108</part-num-ref>
389
+ and to communicate with other electronic and computing devices. </p>
390
+ <p id="p-48" num="48">
391
+ <confidence value="5">[</confidence>
392
+ 00039<confidence value="5">]</confidence>
393
+ Client device 108 can be implemented with one or more memory components, examples of which include a random access memory (RAM) <part-num-ref name="random access memory (RAM)">306,</part-num-ref>
394
+ a hard disk memory <part-num-ref name="hard disk memory">308,</part-num-ref>
395
+ and a non-volatile memory <part-num-ref name="non-volatile memory">310</part-num-ref>
396
+ (e.g., ROM, Flash, EPROM, EEPROM, etc.). The memory components (e.g., RAM <part-num-ref name="RAM">306,</part-num-ref>
397
+ disk memory <part-num-ref name="RAM 306, disk memory">308,</part-num-ref>
398
+ and non- volatile memory <part-num-ref name="RAM 306, disk memory 308, and non- volatile memory">310)</part-num-ref>
399
+ store various information <confidence value="222222">and/or</confidence>
400
+ data such as received content, EPG data, configuration information for client device <part-num-ref name="store various information and/or data such as received content, EPG data, configuration information for client device">108,</part-num-ref>
401
+ and/or graphical user interface information. </p>
402
+ <boundary-data type="header">
403
+ <confidence value="2222222222">lee@hayesp</confidence>
404
+ <confidence value="2254">w9-m</confidence>
405
+ 13 MS<confidence value="4">1</confidence>
406
+ -2483US<confidence value="684">/31</confidence>
407
+ 2274.0<confidence value="5">1</confidence>
408
+ </boundary-data>
409
+ <p id="p-49" num="49">
410
+ <page-break num="15"/>
411
+ [00040] Disk memory 308 stores recorded programs and paused content as one or more virtual streams, represented by unbounded streams 312(1), ..., 312(N). Each virtual stream <part-num-ref name="stores recorded programs and paused content as one or more virtual streams, represented by unbounded streams 312(1), ..., 312(N). Each virtual stream">312</part-num-ref>
412
+ is able to continuously record the programming being received on a channel to which a tuner <part-num-ref name="tuner">302</part-num-ref>
413
+ is tuned. Each stream has a beginning point at which a live broadcast is stored. The stream can be further characterized as having no defined length; rather, the stream length is arbitrarily long. Each stream can be considered virtual in that the programming content within the stream need not be stored in contiguous memory locations in disk memory <part-num-ref name="stream need not be stored in contiguous memory locations in disk memory">308,</part-num-ref>
414
+ but instead can be dispersed throughout the disk and yet still be logically part of the same stream. </p>
415
+ <p id="p-50" num="50">
416
+ <confidence value="5">[</confidence>
417
+ 00041] A front section of the stream forms a pause buffer. This pause buffer region can be defined to store, or otherwise maintain, any measure of content that can be based on a time value or a quantity value. As an example, the pause buffer may be defined as any content that has been recorded within the last N minutes (e.g., <part-num-ref name="">30,</part-num-ref>
418
+ <part-num-ref name="30,">60,</part-num-ref>
419
+ <part-num-ref name="30, 60,">90</part-num-ref>
420
+ minutes), or as the most recently recorded content that does not exceed some threshold amount of storage. The pause buffer region is identified in the stream by a pair of start and end pointers, similar to a recording. The start pointer is always pegged to the front end of the stream and the end pointer moves according to product defined constraints. </p>
421
+ <p id="p-51" num="51">
422
+ <confidence value="5">[</confidence>
423
+ 00042] Recorded programs are also stored as part of the virtual streams 312(1)- 312(N). A recording is identified by a pair of pointers or other references into the stream to set off the beginning and end of the recording. Content in the stream that does not fall within a recording and is not part of the pause buffer (e.g. content that is past <part-num-ref name="content that is past">90</part-num-ref>
424
+ minutes, but not in a recorded program) can be reclaimed by the system. Thus, in general, within the sparse stream, older data is referred to by one or more recordings and newer data is <boundary-data type="header">
425
+ <confidence value="2222222222">lee(@hayes</confidence>
426
+ <confidence value="41">pc</confidence>
427
+ <confidence value="22555171">s-32492s</confidence>
428
+ <confidence value="6">1</confidence>
429
+ 4 MS<confidence value="56">1-</confidence>
430
+ 2483US<confidence value="5">/</confidence>
431
+ 312274.01 </boundary-data>
432
+ <page-break num="16"/>
433
+ the active portion of the pause buffer. However, a recent or active recording can overlap with the boundaries of the current pause buffer. Thus, there is no separation or differentiation between recordings and pause buffer, as there is one unified representation or format for both on the disk memory. </p>
434
+ <p id="p-52" num="52">[00043] In one implementation, the device may be configured to create and manage one virtual stream. Alternatively, the device may create and manage multiple virtual streams, such as one virtual stream per one channel or per a collection of channels.</p>
435
+ <p id="p-53" num="53">
436
+ <confidence value="5">[</confidence>
437
+ 00044<confidence value="5">]</confidence>
438
+ An operating system <part-num-ref name="operating system">314</part-num-ref>
439
+ and one or more application programs <part-num-ref name="and one or more application programs">316</part-num-ref>
440
+ can be stored in non-volatile memory <part-num-ref name="can be stored in non-volatile memory">310</part-num-ref>
441
+ and executed on a processor <part-num-ref name="processor">304</part-num-ref>
442
+ to provide a runtime environment. A runtime environment facilitates extensibility of client device <part-num-ref name="runtime environment facilitates extensibility of client device">108</part-num-ref>
443
+ by allowing various interfaces to be defined that, in turn, allow application programs <part-num-ref name="by allowing various interfaces to be defined that, in turn, allow application programs">316</part-num-ref>
444
+ to interact with client device <part-num-ref name="to interact with client device">108.</part-num-ref>
445
+ Examples of possible application programs <part-num-ref name="to interact with client device 108. Examples of possible application programs">316</part-num-ref>
446
+ include a browser to browse the Web (e.g., "World Wide Web"), an email program to facilitate electronic mail, and so on. An EPG application <part-num-ref name="EPG application">318</part-num-ref>
447
+ is stored in memory <part-num-ref name="is stored in memory">310</part-num-ref>
448
+ to operate on the EPG data and generate a program guide. </p>
449
+ <p id="p-54" num="54">
450
+ <confidence value="5">[</confidence>
451
+ 00045] A DVR component <part-num-ref name="DVR component">320</part-num-ref>
452
+ is also shown implemented as software stored in memory <part-num-ref name="is also shown implemented as software stored in memory">310</part-num-ref>
453
+ and executed by processor <part-num-ref name="and executed by processor">304.</part-num-ref>
454
+ The DVR component <part-num-ref name="DVR component">320</part-num-ref>
455
+ facilitates digital video recording of the broadcast content <part-num-ref name="broadcast content">114</part-num-ref>
456
+ onto into one of the streams 312(1)-312(N) on disk memory <part-num-ref name="streams 312(1)-312(N) on disk memory">308.</part-num-ref>
457
+ The DVR component <part-num-ref name="DVR component">320</part-num-ref>
458
+ supports scheduled recording of programs based, for example, on the EPG data provided by EPG application <part-num-ref name="EPG data provided by EPG application">318</part-num-ref>
459
+ or by user entered time and channel scheduling. Additionally, the DVR component <part-num-ref name="DVR component">320</part-num-ref>
460
+ supports user-initiated recording in response to a user command. The DVR <part-num-ref name="DVR">320</part-num-ref>
461
+ also supports pause/resume functionality that allows the viewer to pause a live broadcast and <boundary-data type="header">
462
+ <confidence value="22222222222">Iee@hayesak</confidence>
463
+ <confidence value="421425541">9-m2-92ss</confidence>
464
+ 15 <confidence value="554">MS1</confidence>
465
+ -24<confidence value="555514">83US/3</confidence>
466
+ 12274.<confidence value="65">01</confidence>
467
+ </boundary-data>
468
+ <page-break num="17"/>
469
+ later resume viewing the broadcast from the paused point, while the broadcast is still in progress. The DVR component <part-num-ref name="DVR component">320</part-num-ref>
470
+ facilitates subsequent playback of the content from the streams 312(1)-312(<confidence value="5">N</confidence>
471
+ ), as well as shuttle commands such as fast forward, rewind, skip, and so forth. </p>
472
+ <p id="p-55" num="55">
473
+ <confidence value="5">[</confidence>
474
+ 00046<confidence value="5">]</confidence>
475
+ The DVR component <part-num-ref name="DVR component">320</part-num-ref>
476
+ includes a stream manager <part-num-ref name="stream manager">322</part-num-ref>
477
+ to create and manage the virtual streams 312(1)-312(N). The stream manager <part-num-ref name="stream manager">322</part-num-ref>
478
+ also maintains reference mappings to identify the various programs contained in virtual streams. The stream manager <part-num-ref name="stream manager">322</part-num-ref>
479
+ is described below in more detail with reference to Fig. 4. </p>
480
+ <p id="p-56" num="56">
481
+ <confidence value="5">[</confidence>
482
+ 00047<confidence value="5">]</confidence>
483
+ Client device 108 can also include other components pertaining to a television entertainment system which are not illustrated in this example. For instance, client device <part-num-ref name="television entertainment system which are not illustrated in this example. For instance, client device">108</part-num-ref>
484
+ can include a user interface application and user interface lights, buttons, controls, and the like to facilitate viewer interaction with the device. </p>
485
+ <p id="p-57" num="57">
486
+ <confidence value="5">[</confidence>
487
+ 00048<confidence value="5">]</confidence>
488
+ Client device 108 also includes a content processor and/or decoder <part-num-ref name="content processor and/or decoder">324</part-num-ref>
489
+ to process and decode a broadcast video signal, such as an NTSC, PAL, SECAM, or other TV system video signal. Content processor <part-num-ref name="NTSC, PAL, SECAM, or other TV system video signal. Content processor">324</part-num-ref>
490
+ can also include a video decoder and/or additional processors to receive, decode, and/or process video content received from the content distribution system (e.g., a network operator) over broadcast network <part-num-ref name="network operator) over broadcast network">110.</part-num-ref>
491
+ For example, content processor <part-num-ref name="network operator) over broadcast network 110. For example, content processor">324</part-num-ref>
492
+ may include an MP3 or MPEG-2 (Moving Pictures Experts Group) decoder that decodes MPEG-encoded video and advertisement content. </p>
493
+ <p id="p-58" num="58">MPEG-2 supports a variety of audio/video formats, including legacy TV, HDTV (high- definition television), DVD (digital versatile disc), and five-channel surround sound.</p>
494
+ <p id="p-59" num="59">
495
+ <confidence value="5">[</confidence>
496
+ 00049] Typically, video content includes video data and audio data that corresponds to the video<confidence value="2">-</confidence>
497
+ data. <confidence value="2">_</confidence>
498
+ Content processor <part-num-ref name="video- data. _ Content processor">324</part-num-ref>
499
+ generates <confidence value="8">v</confidence>
500
+ ideo and/or display <boundary-data type="header">
501
+ <confidence value="22222222222">lee~hayes*n</confidence>
502
+ <confidence value="222">039</confidence>
503
+ <confidence value="88">16</confidence>
504
+ <confidence value="88888888886858888588">MS1-2483US/312274.01</confidence>
505
+ </boundary-data>
506
+ <page-break num="18"/>
507
+ content that is formatted for display on display device <part-num-ref name="generates video and/or display content that is formatted for display on display device">128,</part-num-ref>
508
+ and generates decoded audio data that is formatted for broadcast by a broadcast device, such as one or more speakers (not shown). Content processor <part-num-ref name="broadcast device, such as one or more speakers (not shown). Content processor">324</part-num-ref>
509
+ can include a display controller (not shown) that processes the video and/or display content to display corresponding images on display device <part-num-ref name="video and/or display content to display corresponding images on display device">128.</part-num-ref>
510
+ A display controller can include a microcontroller, integrated circuit, and/or similar video processing component to process the images. It is to be appreciated that the techniques described herein can be implemented for any type of encoding format as well as for data and/or content streams that are not encoded. </p>
511
+ <p id="p-60" num="60">
512
+ <confidence value="5">[</confidence>
513
+ 00050<confidence value="5">]</confidence>
514
+ Client device 108 further includes a wireless interface <part-num-ref name="wireless interface">326,</part-num-ref>
515
+ a network interface <part-num-ref name="network interface">328,</part-num-ref>
516
+ a serial and/or parallel interface <part-num-ref name="serial and/or parallel interface">330,</part-num-ref>
517
+ and a modem <part-num-ref name="modem">332.</part-num-ref>
518
+ Wireless interface <part-num-ref name="modem 332. Wireless interface">326</part-num-ref>
519
+ allows client device <part-num-ref name="allows client device">108</part-num-ref>
520
+ to receive input commands and other information from a user-operated input device, such as from a remote control device or from another IR, Bluetooth, or similar RF input device. </p>
521
+ <p id="p-61" num="61">[00051] Network interface 328 and serial and/or parallel interface <part-num-ref name="and serial and/or parallel interface">330</part-num-ref>
522
+ allows client device <part-num-ref name="allows client device">108</part-num-ref>
523
+ to interact and communicate with other electronic and computing devices via various communication links. Although not shown, client device <part-num-ref name="to interact and communicate with other electronic and computing devices via various communication links. Although not shown, client device">108</part-num-ref>
524
+ may also include other types of data communication interfaces to communicate with other devices. </p>
525
+ <p id="p-62" num="62">Modem 332 facilitates communication with other electronic and computing devices via a conventional telephone line. Client device <part-num-ref name="conventional telephone line. Client device">108</part-num-ref>
526
+ also includes an audio and/or video output <part-num-ref name="audio and/or video output">334</part-num-ref>
527
+ that provides signals to television <part-num-ref name="that provides signals to television">128</part-num-ref>
528
+ or to other devices that process and/or display, or otherwise render, the audio and video data. </p>
529
+ <p id="p-63" num="63">[00052] Client device 108 receives viewer commands as control inputs <part-num-ref name="receives viewer commands as control inputs">336</part-num-ref>
530
+ from such viewer-operated devices as remote control device <part-num-ref name="from such viewer-operated devices as remote control device">204,</part-num-ref>
531
+ handheld device <part-num-ref name="from such viewer-operated devices as remote control device 204, handheld device">206,</part-num-ref>
532
+ and/or <boundary-data type="header">
533
+ <confidence value="222222222">lee@hayes</confidence>
534
+ <confidence value="2">p</confidence>
535
+ <confidence value="21511">o5-mm</confidence>
536
+ 17 MS<confidence value="56">1-</confidence>
537
+ 2483<confidence value="586858888588">US/312274.01</confidence>
538
+ </boundary-data>
539
+ <page-break num="19"/>
540
+ keyboard <part-num-ref name="from such viewer-operated devices as remote control device 204, handheld device 206, and/or keyboard">208</part-num-ref>
541
+ (See Fig. 2). The viewer inputs can include commands for DVR operation, such as record, pause/resume, fast-forward, rewind, play, and the like. The input commands may be input via an RF, IR, Bluetooth, or similar communication link or other mode of transmission. </p>
542
+ <p id="p-64" num="64">
543
+ <confidence value="5">[</confidence>
544
+ 00053<confidence value="5">]</confidence>
545
+ Although shown separately, some of the components of client device <part-num-ref name="components of client device">108</part-num-ref>
546
+ may be implemented in an application specific integrated circuit (ASIC). Additionally, a system bus (not shown) can be used to connect the various components within client device <part-num-ref name="various components within client device">108.</part-num-ref>
547
+ A system bus can be implemented as one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, or a local bus using any of a variety of bus architectures. By way of example, such architectures can include an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnects (PCI) bus also known as a Mezzanine bus. </p>
548
+ <p id="p-65" num="65">Unified Format <confidence value="5">[</confidence>
549
+ 00054<confidence value="5">]</confidence>
550
+ Fig. 4 illustrates how recorded programs and paused broadcasts are stored in a unified format. For ease of discussion, a single virtual stream <part-num-ref name="single virtual stream">312</part-num-ref>
551
+ is shown stored in disk memory <part-num-ref name="is shown stored in disk memory">308.</part-num-ref>
552
+ The stream <part-num-ref name="stream">312</part-num-ref>
553
+ has a beginning point referenced by a "live" pointer <part-num-ref name="&quot;live&quot; pointer">402.</part-num-ref>
554
+ Content received on a channel is stored in the stream <part-num-ref name="stream">312</part-num-ref>
555
+ at the live pointer <part-num-ref name="live pointer">402.</part-num-ref>
556
+ As time progresses and the stream grows, aging content is found increasingly farther downstream from the front region of the stream where live broadcasts are being recorded. </p>
557
+ <p id="p-66" num="66">Thus, the stream <part-num-ref name="stream">312</part-num-ref>
558
+ can be characterized as history of recorded content, with current <boundary-data type="header">
559
+ <confidence value="488">lee</confidence>
560
+ hayes <confidence value="4">P</confidence>
561
+ <confidence value="545121441">sO-m-ease</confidence>
562
+ <confidence value="85">18</confidence>
563
+ MS <confidence value="5">1</confidence>
564
+ -2483US <confidence value="8">/</confidence>
565
+ <confidence value="8688">3122</confidence>
566
+ 74.<confidence value="86">01</confidence>
567
+ </boundary-data>
568
+ <page-break num="20"/>
569
+ content at the right-hand side of the stream (in the Fig. 4 illustration) and increasingly older content extending to the left-hand side of the stream. The stream <part-num-ref name="stream">312</part-num-ref>
570
+ has no defined length (as represented by the dashed lines extending the stream to the left in Fig. </p>
571
+ <p id="p-67" num="67">4); rather the stream <part-num-ref name="stream">312</part-num-ref>
572
+ is arbitrarily long. </p>
573
+ <p id="p-68" num="68">
574
+ <confidence value="5">[</confidence>
575
+ 00055<confidence value="5">]</confidence>
576
+ A front section of the stream functions as a pause buffer <part-num-ref name="pause buffer">404.</part-num-ref>
577
+ This pause buffer region of the stream contains the most recently captured content from a current channel. Since the pause buffer is part of the larger stream, it can be of any arbitrary size. </p>
578
+ <p id="p-69" num="69">The buffer size can be set during manufacturing or configured by the user. The size may be based on time (e.g., <part-num-ref name="">30</part-num-ref>
579
+ or <part-num-ref name="or">60</part-num-ref>
580
+ minutes of content) or quantity of data or it can be dynamic, varying in size based on the amount of physical free space. A dashed line <part-num-ref name="dashed line">406</part-num-ref>
581
+ illustrates a conceptual boundary of the pause buffer <part-num-ref name="pause buffer">404,</part-num-ref>
582
+ but this boundary does not exist from a storage management viewpoint and is merely there for illustration purposes. With the unified format, there is no longer any barrier or separation between what constitutes content in a pause buffer and content in a recording. An accompanying pause buffer end pointer <part-num-ref name="accompanying pause buffer end pointer">407</part-num-ref>
583
+ is provided to mark the end of the pause buffer region <part-num-ref name="pause buffer region">404.</part-num-ref>
584
+ The live and end pointers <part-num-ref name="live and end pointers">402</part-num-ref>
585
+ and <part-num-ref name="and">407</part-num-ref>
586
+ are dynamic relative to the content in the stream, whereby they move to continually identif<confidence value="8">y</confidence>
587
+ the most recent pre-defined amount of content that is captured at the start of the stream. </p>
588
+ <p id="p-70" num="70">
589
+ <confidence value="5">[</confidence>
590
+ 00056<confidence value="5">]</confidence>
591
+ The stream also functions as persistent storage for recorded programs <part-num-ref name="stream also functions as persistent storage for recorded programs">408</part-num-ref>
592
+ that a user desires to maintain for a longer duration (or perhaps indefinitely) and playback at a later time. Initially, when a program is being recorded as part of a scheduled recording or in response to viewer activation of a record button, the program is recorded at the front of the stream in the pause buffer region <part-num-ref name="pause buffer region">404,</part-num-ref>
593
+ beginning at the live pointer <part-num-ref name="live pointer">402.</part-num-ref>
594
+ </p>
595
+ <boundary-data type="header">
596
+ <confidence value="2222222222">Iee@hayese</confidence>
597
+ <confidence value="125665566">s9.324956</confidence>
598
+ 19 MS<confidence value="56884">1-248</confidence>
599
+ 3US<confidence value="68">/3</confidence>
600
+ 12274.01 </boundary-data>
601
+ <p id="p-71" num="71">
602
+ <page-break num="21"/>
603
+ Thus, if the viewer is watching, she may use pause/resume functions on the same program that is being persistently recorded for later playback. With a recording, start and end pointers are used to identify the recording in the virtual stream <part-num-ref name="virtual stream">312.</part-num-ref>
604
+ After the program is recorded, and newer content is subsequently stored in the stream, the recorded program migrates downstream. In Fig. 4, two programs are shown recorded and maintained in the stream 312: a first recording (Re<confidence value="54">c1</confidence>
605
+ ) <part-num-ref name="first recording (Rec1)">410</part-num-ref>
606
+ and a second recording (Rec2) <part-num-ref name="second recording (Rec2)">412.</part-num-ref>
607
+ The first recording <part-num-ref name="first recording">410</part-num-ref>
608
+ is of longer duration and older than the second recording <part-num-ref name="second recording">412.</part-num-ref>
609
+ Since a recording may reside anywhere in the stream (including the pause buffer region 404), Fig. </p>
610
+ <p id="p-72" num="72">4 illustrates this concept by showing the recordings region <part-num-ref name="recordings region">408</part-num-ref>
611
+ overlapping with the pause buffer region <part-num-ref name="pause buffer region">404.</part-num-ref>
612
+ </p>
613
+ <p id="p-73" num="73">[00<confidence value="5885">057]</confidence>
614
+ Stream manager 322 creates the stream <part-num-ref name="stream">312</part-num-ref>
615
+ and manages the content stored in the stream. The stream manager <part-num-ref name="stream manager">322</part-num-ref>
616
+ includes a pointer list <part-num-ref name="pointer list">420</part-num-ref>
617
+ that contains pairs of start and end pointers which identify the beginning and end of recorded programs in the virtual stream <part-num-ref name="virtual stream">312.</part-num-ref>
618
+ In this illustration, there are two pairs of pointers for the two recorded programs <part-num-ref name="two recorded programs">410</part-num-ref>
619
+ and <part-num-ref name="and">412.</part-num-ref>
620
+ A start pointer <part-num-ref name="start pointer">422</part-num-ref>
621
+ and an end pointer <part-num-ref name="end pointer">424</part-num-ref>
622
+ identify the beginning and end of the first recording <part-num-ref name="first recording">410</part-num-ref>
623
+ and a start pointer <part-num-ref name="start pointer">426</part-num-ref>
624
+ and an end pointer <part-num-ref name="end pointer">428</part-num-ref>
625
+ identify the beginning and end of the second recording <part-num-ref name="second recording">412.</part-num-ref>
626
+ </p>
627
+ <p id="p-74" num="74">[00058] The stream manager <part-num-ref name="stream manager">322</part-num-ref>
628
+ may also be configured with a pause component <part-num-ref name="pause component">430</part-num-ref>
629
+ to manage the pause buffer <part-num-ref name="pause buffer">404.</part-num-ref>
630
+ The pause component <part-num-ref name="pause component">430</part-num-ref>
631
+ uses a current pointer <part-num-ref name="current pointer">432</part-num-ref>
632
+ to point to the location in the stream that is currently being displayed. Thus, as the viewer is watching live broadcast, the current pointer <part-num-ref name="current pointer">432</part-num-ref>
633
+ coincides with the live pointer <part-num-ref name="live pointer">402.</part-num-ref>
634
+ When a user pauses a broadcast, the pointer <part-num-ref name="pointer">432</part-num-ref>
635
+ stops moving at that point in the program, while the device continues to capture the broadcast. When the user wishes to <boundary-data type="header">
636
+ <confidence value="222222222">Iee@hayes</confidence>
637
+ <confidence value="2">p</confidence>
638
+ <confidence value="1">*</confidence>
639
+ <confidence value="4512">S-mu</confidence>
640
+ 20 MS1-2483<confidence value="88585">US/31</confidence>
641
+ 2274.0<confidence value="4">1</confidence>
642
+ </boundary-data>
643
+ <page-break num="22"/>
644
+ resume, playback begins at the current pointer <part-num-ref name="current pointer">432.</part-num-ref>
645
+ Shuttle controls such as fast forward and rewind move the current pointer forward and backward at appropriate speeds. </p>
646
+ <p id="p-75" num="75">[00059] The stream manager <part-num-ref name="stream manager">322</part-num-ref>
647
+ further includes a gaps collector <part-num-ref name="gaps collector">434</part-num-ref>
648
+ to remove content that is not part of a recording and is no longer in the pause buffer <part-num-ref name="pause buffer">404.</part-num-ref>
649
+ In Fig. 4, representative gaps <part-num-ref name="pause buffer 404. In Fig. 4, representative gaps">436</part-num-ref>
650
+ and <part-num-ref name="and">438</part-num-ref>
651
+ are shown in the stream <part-num-ref name="stream">312.</part-num-ref>
652
+ The gaps collector <part-num-ref name="gaps collector">434</part-num-ref>
653
+ can be implemented as a background process that analyzes the disk memory <part-num-ref name="disk memory">308</part-num-ref>
654
+ for any content that is not part of a recording and not in the pause buffer. Once a gap is identified, any underlying physical memory can be reclaimed as free and available for reuse by the system. </p>
655
+ <p id="p-76" num="76">[00060] Channel changes, power outages, and other disruptions may cause interruptions to the broadcast stored in the pause buffer region <part-num-ref name="pause buffer region">404.</part-num-ref>
656
+ In some cases, the viewer may not readily understand why there is a break in the broadcast when resuming play of the broadcast from the pause buffer after a pause event. Accordingly, the stream manager <part-num-ref name="stream manager">322</part-num-ref>
657
+ may further include an interruption interpreter <part-num-ref name="interruption interpreter">440</part-num-ref>
658
+ that determines the reason for the interruption. For example, the interpreter <part-num-ref name="interpreter">440</part-num-ref>
659
+ ascertains whether the break in the paused broadcast is the result of a channel change, a power outage, loss of distribution service, and or other situation. The interpreter <part-num-ref name="interpreter">440</part-num-ref>
660
+ may then present an explanation within a user interface <part-num-ref name="user interface">442</part-num-ref>
661
+ to inform the user of why the broadcast was interrupted. </p>
662
+ <p id="p-77" num="77">[00061<confidence value="4">]</confidence>
663
+ The arbitrary-length virtual stream <part-num-ref name="arbitrary-length virtual stream">312</part-num-ref>
664
+ is thus a data structure stored in hard disk memory that logically associates audio and/or video data of various programs. </p>
665
+ <p id="p-78" num="78">The data structure includes a pause buffer region at which new content is captured, but essentially treats recordings and the pause buffer in the same way, with both being <boundary-data type="header">
666
+ <confidence value="222222222">lee@hayes</confidence>
667
+ <confidence value="1">u</confidence>
668
+ <confidence value="16662152">g-324.2%</confidence>
669
+ <confidence value="8">2</confidence>
670
+ 1 MS<confidence value="66">1-</confidence>
671
+ 2483US<confidence value="5">/</confidence>
672
+ 312274.01 </boundary-data>
673
+ <page-break num="23"/>
674
+ identified by pointers. The pause buffer region is defined by dynamic start and end pointers that move relative to the content as content is captured, while the recordings are defined by start and end pointers that are fixed to the start and end of the program. Over time, the data structure defines an<confidence value="2">'</confidence>
675
+ arbitrarily long virtual stream that is sparsely filled with recordings and maintains a pause buffer region for recently captured content. The number of recordings that can be maintained in the virtual stream is bounded by the capacity of the disk storage. The lack of barrier between what is considered a recording and what is considered the pause buffer provides for an improved user experience, as will be discussed below with reference to the scenarios of Figs. 5-9. </p>
676
+ <p id="p-79" num="79">[00062] Several scenarios of how the stream manager <part-num-ref name="stream manager">322</part-num-ref>
677
+ manages the streams of content on the disk memory are described below with reference to Figs. 5-9. These are merely examples to demonstrate the flexibility and usefulness of the unified format, and are not intended to be exhaustive. </p>
678
+ <p id="p-80" num="80">[00063] Fig. 5 shows a scenario <part-num-ref name="scenario">500</part-num-ref>
679
+ where a pause buffer can refer back into a recording. Here, a virtual stream <part-num-ref name="virtual stream">502</part-num-ref>
680
+ has a first recording (Re<confidence value="52">cd</confidence>
681
+ ) <part-num-ref name="first recording (Recd)">504</part-num-ref>
682
+ and second recording (Rec2) <part-num-ref name="and second recording (Rec2)">506.</part-num-ref>
683
+ The second recording <part-num-ref name="second recording">506</part-num-ref>
684
+ overlaps with the pause buffer region <part-num-ref name="pause buffer region">404</part-num-ref>
685
+ of the stream <part-num-ref name="stream">502,</part-num-ref>
686
+ as represented by the end pointer for Rec2 <part-num-ref name="end pointer for Rec2">506</part-num-ref>
687
+ being within region <part-num-ref name="being within region">404.</part-num-ref>
688
+ This is the case, for example, when the DVR system recently ended recording a program less than the time duration of the pause buffer (e.g., the recording completed less than <part-num-ref name="recording completed less than">90</part-num-ref>
689
+ minutes ago). </p>
690
+ <p id="p-81" num="81">[00064] Since there is no distinction in the virtual stream as to paused content and recorded content, the viewer is able to move back and forth between a recently recorded program and the pause buffer content. For instance, suppose a viewer is recording one <boundary-data type="header">
691
+ <confidence value="222222222">lee@hayes</confidence>
692
+ <confidence value="4">p</confidence>
693
+ <confidence value="2211251">s0s"32e</confidence>
694
+ 22 MS1-2483US <confidence value="86">/3</confidence>
695
+ 12274.<confidence value="88">01</confidence>
696
+ </boundary-data>
697
+ <page-break num="24"/>
698
+ program on the channel (e.g., Rec2 <part-num-ref name="Rec2">506)</part-num-ref>
699
+ and that program recording ends. Further, suppose the viewer decides to rewind and view a portion of the recording, regardless of whether or not the viewer is aware that the recording has ended. With the unified format, the user can easily rewind into the recorded program and watch the desired portion of that recorded program. In contrast, previous DVR systems would have created a standalone pause buffer for recent content after the recording ended, and the viewer would not have been able to rewind into the recording. Instead, the viewer would probably need to locate the recording (e.g., via a user interface (UI)) and then use move through the recording to locate the desired portion. Thus, the unified format offers a natural and easy way to move back and forth across a boundary between a recording and a pause buffer that existed in previous DVR systems. </p>
700
+ <p id="p-82" num="82">
701
+ <confidence value="5">[</confidence>
702
+ 00065<confidence value="5">]</confidence>
703
+ Fig. 6 shows a scenario <part-num-ref name="scenario">600</part-num-ref>
704
+ where overlapping recordings on the same channel are also managed without causing conflicts. In scenario <part-num-ref name="same channel are also managed without causing conflicts. In scenario">600,</part-num-ref>
705
+ a virtual stream <part-num-ref name="virtual stream">602</part-num-ref>
706
+ has a first recording (Re<confidence value="55">cl</confidence>
707
+ ) <part-num-ref name="first recording (Recl)">604</part-num-ref>
708
+ that overlaps with a second recording (Rec2) <part-num-ref name="second recording (Rec2)">606.</part-num-ref>
709
+ This may occur, for example, where a user records a sporting event and the next scheduled program on the same channel, and the sporting event extends beyond the scheduled timeslot. With the unified format that treats recordings as data in a common virtual stream, these situations of overlapping recordings on the same channel are handled to provide an intuitive experience for the user. The start and end pointers reference the programs in the stream, and readily accommodate the overlapping recordings. </p>
710
+ <p id="p-83" num="83">
711
+ <confidence value="5">[</confidence>
712
+ 00066] Fig. 7 shows a scenario <part-num-ref name="scenario">700</part-num-ref>
713
+ where gaps between recordings are examined to determine if they still reference physical storage space that can be freed up for additional recordings. In this scenario, a virtual stream <part-num-ref name="virtual stream">702</part-num-ref>
714
+ has a first recording (Re<confidence value="668">cl)</confidence>
715
+ <boundary-data type="header">
716
+ <confidence value="488">lee</confidence>
717
+ <confidence value="1">@</confidence>
718
+ hayes <confidence value="11">pk</confidence>
719
+ <confidence value="2125252">so3.92s</confidence>
720
+ 23 MS<confidence value="4">1</confidence>
721
+ -2483US<confidence value="5">/</confidence>
722
+ 312274.0<confidence value="4">1</confidence>
723
+ </boundary-data>
724
+ <page-break num="25"/>
725
+ <part-num-ref name="first recording (Recl)">704</part-num-ref>
726
+ and a second recording (Rec2) <part-num-ref name="second recording (Rec2)">706.</part-num-ref>
727
+ The stream <part-num-ref name="stream">702</part-num-ref>
728
+ also has gaps <part-num-ref name="also has gaps">708</part-num-ref>
729
+ and <part-num-ref name="and">710</part-num-ref>
730
+ that reference physical memory that is currently storing content which is not part of a recording and not in the pause buffer <part-num-ref name="pause buffer">404.</part-num-ref>
731
+ The gaps collector <part-num-ref name="gaps collector">434</part-num-ref>
732
+ (Fig. <part-num-ref name="(Fig.">4)</part-num-ref>
733
+ is invoked to identify such gaps and reclaim the underlying physical storage space. As shown, the gaps collector <part-num-ref name="gaps collector">434</part-num-ref>
734
+ identifies the gaps <part-num-ref name="gaps">708</part-num-ref>
735
+ and <part-num-ref name="and">710</part-num-ref>
736
+ as referencing physical storage space and reclaims the physical storage space referenced by the gaps. This is reflected in post- collection stream 702' by addition of a hashing pattern in gaps <part-num-ref name="hashing pattern in gaps">708</part-num-ref>
737
+ and <part-num-ref name="and">710</part-num-ref>
738
+ to illustrate that it no longer references physical memory. Additionally, the system may use a similar technique to reclaim storage space associated with recordings in the stream that are subsequently deleted by the user. </p>
739
+ <p id="p-84" num="84">00067<confidence value="5">]</confidence>
740
+ As one exemplary technique, reference counts may be used to manage the data in the stream. Regions of the stream can be assigned different counts depending upon whether the region is part of a stream and still in use as part of a recording, or whether it is a gap or a deleted recording and thus free to be reclaimed. For instance, suppose a region that is part of a recording is assigned a count of "1" and a region that is referenced by two recordings is assigned a count of "2", and so forth. Additionally, the pause buffer region is assigned a count of <confidence value="85">"1</confidence>
741
+ ". Other regions that form gaps (i.e., not part of a recording or pause buffer) are assigned a count of "<confidence value="5">0</confidence>
742
+ ". When a recording is deleted or content leaves the pause buffer region without being part of a recording, the reference count is decremented. When the count reaches "<confidence value="5">0</confidence>
743
+ ", the gaps collector will identify the regions and determine whether the regions reference underlying physical storage. If so, the gaps collector marks the physical storage as "free" for reuse by the system. </p>
744
+ <boundary-data type="header">
745
+ <confidence value="222222222">Iee@hayes</confidence>
746
+ <confidence value="11">pe</confidence>
747
+ <confidence value="1411215614">sog*-ne2ws</confidence>
748
+ 24 MS<confidence value="66885">1-248</confidence>
749
+ 3US <confidence value="8">/</confidence>
750
+ <confidence value="86">31</confidence>
751
+ 2274.<confidence value="68">01</confidence>
752
+ </boundary-data>
753
+ <p id="p-85" num="85">
754
+ <page-break num="26"/>
755
+ <confidence value="5">[</confidence>
756
+ 00068<confidence value="5">]</confidence>
757
+ Fig. 8 shows a scenario <part-num-ref name="scenario">800</part-num-ref>
758
+ where a user changes channels (accidentally or intentionally) without losing or flushing all of the previous content in the pause buffer. In this scenario, a viewer is watching channel <part-num-ref name="viewer is watching channel">5,</part-num-ref>
759
+ briefly switches channels to channel <part-num-ref name="viewer is watching channel 5, briefly switches channels to channel">6,</part-num-ref>
760
+ and then returns to channel <part-num-ref name="viewer is watching channel 5, briefly switches channels to channel 6, and then returns to channel">5.</part-num-ref>
761
+ In Fig. 8, the pause buffer region <part-num-ref name="pause buffer region">404</part-num-ref>
762
+ is enlarged to illustrate this scenario. When the viewer is watching channel <part-num-ref name="viewer is watching channel">5,</part-num-ref>
763
+ content from that channel is recorded into a virtual stream <part-num-ref name="virtual stream">802,</part-num-ref>
764
+ as represented by a segment <part-num-ref name="segment">804</part-num-ref>
765
+ of the stream. When the viewer changes to channel <part-num-ref name="viewer changes to channel">6,</part-num-ref>
766
+ content from that channel is recorded into the virtual stream <part-num-ref name="virtual stream">802,</part-num-ref>
767
+ as represented by a segment <part-num-ref name="segment">806</part-num-ref>
768
+ of the stream. Finally, when the viewer returns to channel <part-num-ref name="viewer returns to channel">6,</part-num-ref>
769
+ the content from that channel is again recorded in the stream <part-num-ref name="stream">802,</part-num-ref>
770
+ as represented by a segment <part-num-ref name="segment">808.</part-num-ref>
771
+ </p>
772
+ <p id="p-86" num="86">[00069<confidence value="4">]</confidence>
773
+ With this unified format, the viewer is able to return to the content in segment <part-num-ref name="content in segment">804</part-num-ref>
774
+ prior to the channel change using pause buffer functionality. For instance, the viewer might return to location <part-num-ref name="viewer might return to location">810</part-num-ref>
775
+ in the stream <part-num-ref name="stream">802.</part-num-ref>
776
+ Since the content is persistent in the stream <part-num-ref name="stream">802</part-num-ref>
777
+ until recycled via a gaps collection process, the content is not flushed or deleted upon the channel change, as in prior conventional DVR systems. Therefore, the DVR system can return the user to point <part-num-ref name="user to point">810</part-num-ref>
778
+ and begin playing back the content in the pause buffer. </p>
779
+ <p id="p-87" num="87">
780
+ <confidence value="5">[</confidence>
781
+ 00070<confidence value="5">]</confidence>
782
+ However, when the viewer encounters segment <part-num-ref name="viewer encounters segment">806</part-num-ref>
783
+ on the playback, it will show the content from channel <part-num-ref name="content from channel">6.</part-num-ref>
784
+ This may be confusing to the viewer. To provide assistance in this situation, the system presents a UI to inform the viewer that the brief transition to channel <part-num-ref name="brief transition to channel">6</part-num-ref>
785
+ is the result of a channel change, and that the content on channel <part-num-ref name="content on channel">5</part-num-ref>
786
+ for that segment was therefore not captured. </p>
787
+ <boundary-data type="header">
788
+ <confidence value="588">lee</confidence>
789
+ hayes <confidence value="4">a</confidence>
790
+ <confidence value="5552555242">5os-324-2e</confidence>
791
+ <confidence value="88">25</confidence>
792
+ <confidence value="558885555185">MS-2483US/31</confidence>
793
+ 2274.0<confidence value="4">1</confidence>
794
+ </boundary-data>
795
+ <p id="p-88" num="88">
796
+ <page-break num="27"/>
797
+ [00071] Additionally, interruptions in the stream may occur for reasons other than channel change. For example, a similar interruption may occur during unexpected power loss while recording. When the power is restored and the system begins recording, there will be a segment of content missing from the virtual stream. In this case, the UI explains that the loss of data in the playback was caused by power loss. Other possible conditions might be loss of distribution network, technical difficulties at the content providers, and so forth. </p>
798
+ <p id="p-89" num="89">
799
+ <confidence value="5">[</confidence>
800
+ 00072] Fig. 9 shows another implementation scenario <part-num-ref name="shows another implementation scenario">900</part-num-ref>
801
+ where the stream manager <part-num-ref name="stream manager">322</part-num-ref>
802
+ creates multiple virtual streams. For instance, the stream manager may create one stream for each channel or group of channels. The scenario described above with respect to Fig. 8 would then be handled by placing content from channel <part-num-ref name="would then be handled by placing content from channel">5</part-num-ref>
803
+ in one stream and content from channel <part-num-ref name="in one stream and content from channel">6</part-num-ref>
804
+ in a second virtual stream. </p>
805
+ <p id="p-90" num="90">
806
+ <confidence value="5">[</confidence>
807
+ 00073] In another implementation, the system may be equipped with multiple tuners. One or more virtual streams may then be created and used to support the multiple tuners. In this example, one virtual stream 902(1), ..., 902(M) is created for each tuner 302(1), ..., 302(M), although other configurations are possible. With this arrangement, channel changes may not cause interruptions in the stream if one of the tuners is available. For example, suppose the viewer is watching channel <part-num-ref name="viewer is watching channel">5</part-num-ref>
808
+ on tuner 302(1). The content from channel <part-num-ref name="content from channel">5</part-num-ref>
809
+ is being recorded into virtual stream 902(1). When the viewer changes to channel <part-num-ref name="viewer changes to channel">6,</part-num-ref>
810
+ a second tuner 302(M) can tune to channel <part-num-ref name="second tuner 302(M) can tune to channel">6</part-num-ref>
811
+ and begin displaying the content on channel <part-num-ref name="content on channel">6.</part-num-ref>
812
+ Additionally, the content can be recorded into second virtual stream 902(M). At the same time, the first tuner 302(1) can continue to record content on channel <part-num-ref name="first tuner 302(1) can continue to record content on channel">5</part-num-ref>
813
+ into virtual stream 902(1). If the viewer subsequently returns to channel <part-num-ref name="viewer subsequently returns to channel">5</part-num-ref>
814
+ and <boundary-data type="header">
815
+ <confidence value="222222222">lee~hayes</confidence>
816
+ <confidence value="1">a</confidence>
817
+ <confidence value="441">Wan</confidence>
818
+ 26 MS<confidence value="486">7-2</confidence>
819
+ 483US<confidence value="58666">/3122</confidence>
820
+ 74.01 </boundary-data>
821
+ <page-break num="28"/>
822
+ wishes to playback what he missed while on channel <part-num-ref name="and wishes to playback what he missed while on channel">6,</part-num-ref>
823
+ the viewer can use pause/resume functions to playback from the missed content from channel <part-num-ref name="missed content from channel">5</part-num-ref>
824
+ in virtual stream 902(1). </p>
825
+ <p id="p-91" num="91">Method for Content Buffer Management [00074<confidence value="5">1</confidence>
826
+ Fig. 10 shows a process <part-num-ref name="process">1000</part-num-ref>
827
+ for operating a digital video recording system such that recorded programs and paused broadcasts are stored in a unified format. </p>
828
+ <p id="p-92" num="92">The process 1000 is illustrated as a collection of blocks in a logical flow graph, which represent a sequence of operations that can be implemented in hardware, software, or a combination thereof. In the context of software, the blocks represent computer- executable instructions that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures, and the like that perform particular functions or implement particular abstract data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described blocks can be combined in any order to implement the process.</p>
829
+ <p id="p-93" num="93">[00075<confidence value="5">1</confidence>
830
+ For discussion purposes, the process <part-num-ref name="process">1000</part-num-ref>
831
+ is described with reference the system <part-num-ref name="system">300</part-num-ref>
832
+ of Fig. 3 and the DVR aspects described with reference to Fig. 4. It is noted that the process <part-num-ref name="process">1000</part-num-ref>
833
+ may be implemented by other system architectures. </p>
834
+ <p id="p-94" num="94">[00076<confidence value="5">1</confidence>
835
+ At block 1002, an arbitrary-length virtual stream is created. As one example, the stream manager <part-num-ref name="stream manager">322</part-num-ref>
836
+ establishes a stream <part-num-ref name="stream">312</part-num-ref>
837
+ in hard disk memory <part-num-ref name="in hard disk memory">308</part-num-ref>
838
+ and provides an initial live pointer <part-num-ref name="initial live pointer">402</part-num-ref>
839
+ to identify the beginning of the stream (Fig. 4). At block <part-num-ref name="stream (Fig. 4). At block">1004,</part-num-ref>
840
+ content is received from a broadcast channel. The tuner <part-num-ref name="tuner">302</part-num-ref>
841
+ tunes to a particular channel on the broadcast network, and the content is received at the device <part-num-ref name="device">108.</part-num-ref>
842
+ </p>
843
+ <boundary-data type="header">
844
+ <confidence value="2222222222">lee@hayess</confidence>
845
+ <confidence value="141">5Ms</confidence>
846
+ 27 MS1-2483US<confidence value="68">/3</confidence>
847
+ 12274.0<confidence value="5">1</confidence>
848
+ </boundary-data>
849
+ <p id="p-95" num="95">
850
+ <page-break num="29"/>
851
+ [00077] At block 1006, the live broadcast content is stored in a first section of the virtual stream. In the described implementation of Fig. 4, the broadcast program being received on the current channel is stored in the pause buffer region <part-num-ref name="pause buffer region">404</part-num-ref>
852
+ of the stream <part-num-ref name="stream">312,</part-num-ref>
853
+ starting at the live pointer <part-num-ref name="live pointer">402.</part-num-ref>
854
+ At block <part-num-ref name="live pointer 402. At block">1008,</part-num-ref>
855
+ a user is enabled to pause and resume playback of the broadcast content stored in the pause buffer region <part-num-ref name="pause buffer region">404</part-num-ref>
856
+ of the virtual stream. When a user pauses a current broadcast, a current location pointer stops as more recent content continues to be captured in the stream. When the user resumes play, the device continues play beginning at the current location pointer, while the broadcast continues to be recorded into the pause buffer region <part-num-ref name="pause buffer region">404</part-num-ref>
857
+ at the live pointer <part-num-ref name="live pointer">402.</part-num-ref>
858
+ The user can also use shuttle commands to skip, rewind, etc. within the paused content. </p>
859
+ <p id="p-96" num="96">
860
+ <confidence value="5">[</confidence>
861
+ 00078] Programs stored as part of a recording operation (e.g., scheduled recording, one-touch recording, etc.) are likewise initially placed in the pause buffer region of the virtual stream in the same manner that broadcast content is recorded. The pause/resume functionality (and fast forward, rewind, etc.) can be applied to this recorded content in the pause buffer region <part-num-ref name="pause buffer region">404</part-num-ref>
862
+ in the same manner as the currently captured live programming that is not part of a recorded program. The recorded programs are identified via pointers and retained indefinitely in the virtual stream. Thus, as content ages, the recorded program moves through this pause buffer region and is maintained downstream in a second section of the virtual stream outside the pause buffer region (block 1010). As shown in Fig. 4, as recorded content ages beyond the constraints of the pause buffer (e.g., exceeds a size threshold or is longer than a temporal threshold), it continues to be held in the recording section <part-num-ref name="recording section">408</part-num-ref>
863
+ of the virtual stream <part-num-ref name="virtual stream">312</part-num-ref>
864
+ outside of the pause buffer region <part-num-ref name="pause buffer region">404.</part-num-ref>
865
+ The stream manager <part-num-ref name="stream manager">322</part-num-ref>
866
+ maintains a list of pointers that <boundary-data type="header">
867
+ <confidence value="222222222">lee@hayes</confidence>
868
+ <confidence value="141">oe&lt;</confidence>
869
+ <confidence value="2155651">on-a2se</confidence>
870
+ <confidence value="85">28</confidence>
871
+ MS<confidence value="4">1</confidence>
872
+ -2483<confidence value="6858688">US/3122</confidence>
873
+ 74.01 </boundary-data>
874
+ <page-break num="30"/>
875
+ identify the start and end points of the recorded programs in the virtual stream <part-num-ref name="virtual stream">312.</part-num-ref>
876
+ At block <part-num-ref name="virtual stream 312. At block">1012,</part-num-ref>
877
+ the user is enabled to playback selected ones of the recorded programs in the second section of the virtual stream. As one example, the device presents a UI that allows the user to browse the recorded programs stored in disk memory <part-num-ref name="recorded programs stored in disk memory">308,</part-num-ref>
878
+ and choose a program for playback. Once selected, the stream manager <part-num-ref name="stream manager">322</part-num-ref>
879
+ retrieves the corresponding start pointer and locates the start of the requested program. The program is then played back. </p>
880
+ <p id="p-97" num="97">
881
+ <confidence value="5">[</confidence>
882
+ 00079] As noted above, content that is not part of a recorded program or still in the pause buffer region of the virtual stream can be systematically examined and if referencing physical storage, that physical storage can be reclaimed by the system. At block <part-num-ref name="system. At block">1014,</part-num-ref>
883
+ a background process may be executed to identify and collect these gaps that reference storage space, and free up space on the hard disk memory that can be reused by the system. In one implementation, the gaps reclamation process is performed by the gaps collector <part-num-ref name="gaps collector">434</part-num-ref>
884
+ as a background process run by the stream manager <part-num-ref name="stream manager">322</part-num-ref>
885
+ (Fig. 4). </p>
886
+ <p id="p-98" num="98">Conclusion [00080] Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claims.</p>
887
+ <boundary-data type="header">
888
+ <confidence value="2222222222">lee(@hayes</confidence>
889
+ <confidence value="41">Pe</confidence>
890
+ <confidence value="5151211">so-3-em</confidence>
891
+ 29 MS<confidence value="5">1</confidence>
892
+ -2483US <confidence value="8">/</confidence>
893
+ 312274.<confidence value="86">01</confidence>
894
+ </boundary-data>
895
+ </description>
896
+ </us-patent-application>
897
+
prior_art/11132658.xml ADDED
@@ -0,0 +1,107 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11132658</doc-number>
8
+ <date>2007-03-22</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <boundary-data type="header">PATENTS</boundary-data>
14
+ <boundary-data type="header">
15
+ <confidence value="86">RO</confidence>
16
+ C920040358US1 </boundary-data>
17
+ <heading id="h-1">AMENDMENTS TO THE SPECIFICATION</heading>
18
+ <p id="p-1" num="1">On page 1 of the Application please amend the specification as follows:</p>
19
+ <p id="p-2" num="2">"The present application is related to U.S. Patent Application Serial No.<confidence value="66">[[</confidence>
20
+ <confidence value="66">]]</confidence>
21
+ 11/132,656, filed on even date herewith and titled "METHODS AND APPARATUS FOR SHARING PROCESSOR RESOURCES" (Attorney Docket No. R<confidence value="5">O</confidence>
22
+ C920040357), which is hereby incorporated by reference herein in its entirety." On page 6 of the Application please amend the specification as follows: </p>
23
+ <p id="p-3" num="3">"In some embodiments, the processing system may employ a unified register stack and/or allow registers in the unified register stack to store different types of data at different times as described in U.S. Patent Application Serial No.[[ <confidence value="66">]]</confidence>
24
+ 11/132,656, filed on even date herewith and titled </p>
25
+ <heading id="h-2">"METHODS AND APPARATUS FOR SHARING PROCESSOR RESOURCES"</heading>
26
+ <p id="p-4" num="4">(Attorney Docket No. R<confidence value="5">O</confidence>
27
+ C920040357), which is hereby incorporated by reference herein in its entirety. In this manner, the present methods and apparatus may efficiently use registers and execution units included in a processing system, thereby reducing an overall number of such registers and/or execution units required by the processing system. Consequently, the present methods and apparatus may reduce the amount of silicon area required by the processing system and power consumed thereby. For example, the present invention may include the first and/or second exemplary processors described with reference to FIGS. 1 and <part-num-ref name="and">4,</part-num-ref>
28
+ respectively, of U.S. Patent Application Serial No.<confidence value="66">[[</confidence>
29
+ <confidence value="66">]]</confidence>
30
+ 11/132,656, filed on even date herewith and titled "METHODS AND APPARATUS FOR SHARING <boundary-data type="header">-2-</boundary-data>
31
+ <page-break num="2"/>
32
+ <boundary-data type="header">PATENTS</boundary-data>
33
+ <boundary-data type="header">
34
+ <confidence value="86">RO</confidence>
35
+ C920040358U<confidence value="68">S1</confidence>
36
+ </boundary-data>
37
+ PROCESSOR RESOURCES" (Attorney Docket No. R<confidence value="5">O</confidence>
38
+ C920040357), which is hereby incorporated by reference herein in its entirety." On pages 34-35 please amend the specification as follows: </p>
39
+ <p id="p-5" num="5">"While operating in either the first or second mode, the exemplary processing system <part-num-ref name="exemplary processing system">100</part-num-ref>
40
+ may store a vector operands associated with a vector instruction therewith using one or more registers (e.g., VPRs) <part-num-ref name="VPRs)">104</part-num-ref>
41
+ in each of the first and second arrays <part-num-ref name="first and second arrays">103,</part-num-ref>
42
+ <part-num-ref name="first and second arrays 103,">105.</part-num-ref>
43
+ For example, in some embodiments, the exemplary processing system <part-num-ref name="exemplary processing system">100</part-num-ref>
44
+ may receive and store 128-bit vector operands associated with a vector instruction (although a larger or smaller vector operand may be employed). Further, the exemplary processing system <part-num-ref name="exemplary processing system">100</part-num-ref>
45
+ may operate on such 128-bit operands. Consequently, the processing system <part-num-ref name="processing system">100</part-num-ref>
46
+ may divide the 128-bit operand into four portions (although the vector operand may be divided into a larger or smaller number of portions). For example, the first and third portions may be stored in respective registers (e.g., VPRs) of the first array <part-num-ref name="first array">103,</part-num-ref>
47
+ and the second and fourth portions may be stored in respective registers (e.g., VPRs) of the second array <part-num-ref name="second array">105.</part-num-ref>
48
+ A VMX <part-num-ref name="VMX">180,</part-num-ref>
49
+ <part-num-ref name="VMX 180,">182</part-num-ref>
50
+ may operate on the 128-bit operand in two cycles. </p>
51
+ <p id="p-6" num="6">For example, during a first cycle the VMX <part-num-ref name="VMX">180,</part-num-ref>
52
+ <part-num-ref name="VMX 180,">182</part-num-ref>
53
+ may operate on the first portion stored in the first array <part-num-ref name="first array">103</part-num-ref>
54
+ and the second portion stored in the second array <part-num-ref name="second array">105</part-num-ref>
55
+ in tandem. During a subsequent cycle (e.g., the next cycle) the VMX <part-num-ref name="VMX">180,</part-num-ref>
56
+ <part-num-ref name="VMX 180,">182</part-num-ref>
57
+ may operate on the third portion stored in the first array <part-num-ref name="first array">103</part-num-ref>
58
+ and the fourth portion stored in the second array <part-num-ref name="second array">105</part-num-ref>
59
+ in tandem. </p>
60
+ <p id="p-7" num="7">Carry propagation may be employed between the execution units (e.g., FXUs <part-num-ref name="FXUs">154,</part-num-ref>
61
+ <part-num-ref name="FXUs 154,">168</part-num-ref>
62
+ or FPUs <part-num-ref name="or FPUs">160,</part-num-ref>
63
+ <part-num-ref name="or FPUs 160,">174)</part-num-ref>
64
+ that serve as VMXs <part-num-ref name="that serve as VMXs">180,</part-num-ref>
65
+ <part-num-ref name="that serve as VMXs 180,">182.</part-num-ref>
66
+ Further, carry propagation may be employed between the VMX <part-num-ref name="VMX">180,</part-num-ref>
67
+ <part-num-ref name="VMX 180,">182</part-num-ref>
68
+ during the first and subsequent cycles in which the <boundary-data type="header">-3-</boundary-data>
69
+ <page-break num="3"/>
70
+ <boundary-data type="header">PATENTS</boundary-data>
71
+ <boundary-data type="header">
72
+ <confidence value="86">RO</confidence>
73
+ C920040358U<confidence value="68">S1</confidence>
74
+ </boundary-data>
75
+ vector operation is performed. In a manner similar to that described in U.S. Patent Application Serial No.[[ <confidence value="66">]]</confidence>
76
+ 11/132,656, filed on even date herewith and titled "METHODS AND APPARATUS FOR SHARING PROCESSOR RESOURCES" (Attorney Docket No. </p>
77
+ <p id="p-8" num="8">
78
+ <confidence value="86">RO</confidence>
79
+ C920040357), which is hereby incorporated by reference herein in its entirety, the exemplary processing system <part-num-ref name="exemplary processing system">100</part-num-ref>
80
+ may operate on a single thread or simultaneously operate on a plurality of threads. Further, the first VMX <part-num-ref name="first VMX">180</part-num-ref>
81
+ may be employed for simple vector instructions and the second VMX <part-num-ref name="second VMX">182</part-num-ref>
82
+ may be employed for complex vector instructions. </p>
83
+ <p id="p-9" num="9">On page 37 please amend the specification as follows:</p>
84
+ <p id="p-10" num="10">"In summary, in some embodiments, the present methods and apparatus may provide a processing system with:</p>
85
+ <p id="p-11" num="11">GPRs - 32 registers x <part-num-ref name="registers x">8</part-num-ref>
86
+ bytes x <part-num-ref name="bytes x">2</part-num-ref>
87
+ threads = <part-num-ref name="threads =">512</part-num-ref>
88
+ bytes FPRs - <part-num-ref name="bytes FPRs -">32</part-num-ref>
89
+ registers x <part-num-ref name="registers x">8</part-num-ref>
90
+ bytes x <part-num-ref name="bytes x">2</part-num-ref>
91
+ threads = <part-num-ref name="threads =">512</part-num-ref>
92
+ bytes VPRs - <part-num-ref name="bytes VPRs -">32</part-num-ref>
93
+ registers x <part-num-ref name="registers x">16</part-num-ref>
94
+ bytes x <part-num-ref name="bytes x">2</part-num-ref>
95
+ threads = <part-num-ref name="threads =">1024</part-num-ref>
96
+ bytes. </p>
97
+ <p id="p-12" num="12">Therefore, a total of <part-num-ref name="total of">2048</part-num-ref>
98
+ bytes may be stored in a single array, which may be partitioned into <part-num-ref name="single array, which may be partitioned into">4</part-num-ref>
99
+ x 32-bit slices, and may include a total of twelve read ports and/or twelve write ports. </p>
100
+ <p id="p-13" num="13">In SMT mode, a thread may have affinity to one FXU and one FPU thereby avoiding requiring another <part-num-ref name="thread may have affinity to one FXU and one FPU thereby avoiding requiring another">1024</part-num-ref>
101
+ bytes. Further, in single-threaded mode, contents of GPRs and FPRs that are associated with a first thread may be duplicated in GPRs and FPRs associated with a second thread. Further, the present invention may be employed by processing systems that employ register renaming as described in U.S. Patent Application Serial No.[[ <confidence value="66">]]</confidence>
102
+ 11/132,656, filed on even date herewith and titled "METHODS AND APPARATUS FOR SHARING PROCESSOR RESOURCES" (Attorney Docket No. R<confidence value="5">O</confidence>
103
+ C920040357), which is hereby incorporated by reference herein in its entirety." <boundary-data type="header">-4-</boundary-data>
104
+ </p>
105
+ </description>
106
+ </us-patent-application>
107
+
prior_art/11140114.xml ADDED
@@ -0,0 +1,82 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11140114</doc-number>
8
+ <date>2007-12-06</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <boundary-data type="header">Attorney Docket No. ATEC.P<confidence value="4">0</confidence>
14
+ 10 Patent App. Serial No. 11/140,114 </boundary-data>
15
+ <boundary-data type="header">Client File No. 050015 S</boundary-data>
16
+ <heading id="h-1">IN THE SPECIFICATION</heading>
17
+ <p id="p-1" num="1">On page 7, line 3, please replace the paragraphs with the following paragraphs which show the changes made.</p>
18
+ <p id="p-2" num="2">Figure 2 is a block diagram of a system <part-num-ref name="system">200</part-num-ref>
19
+ according to an embodiment. The <boundary-data type="line-number">5 </boundary-data>
20
+ system <part-num-ref name="system">200</part-num-ref>
21
+ includes components or elements that may reside on various components of a video-capable computer system. In one embodiment an application <part-num-ref name="application">202,</part-num-ref>
22
+ a driver <part-num-ref name="driver">2062<confidence value="586">94,</confidence>
23
+ </part-num-ref>
24
+ and a shared memory <part-num-ref name="shared memory">205</part-num-ref>
25
+ reside on a host computer system, while remaining components reside on video-specific components, including one or more video cards, but the invention is not so limited. Any of the components shown could reside anywhere or, <boundary-data type="line-number">10 </boundary-data>
26
+ alternatively, various components could access other components remotely via a wired or wireless network. The application <part-num-ref name="application">202</part-num-ref>
27
+ is an end user application that requires video processing capability, such as a video game application. The application <part-num-ref name="application">202</part-num-ref>
28
+ communicates with application programming interface (API) <part-num-ref name="communicates with application programming interface (API)">204.</part-num-ref>
29
+ The API <part-num-ref name="API">204</part-num-ref>
30
+ can be any one of the available graphics, or video, or 3D APIs including DirectX (from <boundary-data type="line-number">15 </boundary-data>
31
+ Microsoft) and OpenGL (from Silicon Graphics). </p>
32
+ <p id="p-3" num="3">On page 18, line 19, please replace the paragraphs with the following paragraphs which show the changes made.</p>
33
+ <p id="p-4" num="4">The master VPU card 652 includes connectors <part-num-ref name="includes connectors">640</part-num-ref>
34
+ and <part-num-ref name="and">641.</part-num-ref>
35
+ The slave VPU card <boundary-data type="line-number">20 </boundary-data>
36
+ <part-num-ref name="slave VPU card">654</part-num-ref>
37
+ includes connectors <part-num-ref name="includes connectors">642</part-num-ref>
38
+ and <part-num-ref name="and">643.</part-num-ref>
39
+ Connectors <part-num-ref name="and 643. Connectors">640,</part-num-ref>
40
+ <part-num-ref name="and 643. Connectors 640,">641,</part-num-ref>
41
+ <part-num-ref name="and 643. Connectors 640, 641,">642</part-num-ref>
42
+ and <part-num-ref name="and">643</part-num-ref>
43
+ are connectors appropriate for the purpose of transmitting the required signals as known in the art. For example, the connector <part-num-ref name="connector">641</part-num-ref>
44
+ is a digital video in (DVI) connector in one embodiment. </p>
45
+ <p id="p-5" num="5">There could be more or less than the number of connectors shown in the Fi<confidence value="5">g</confidence>
46
+ ure 6Fi<confidence value="5427">gure</confidence>
47
+ <part-num-ref name="Figure 6Figure">
48
+ <confidence value="4118">609.</confidence>
49
+ </part-num-ref>
50
+ </p>
51
+ <p id="p-6" num="6">
52
+ <boundary-data type="line-number">
53
+ <confidence value="88">25</confidence>
54
+ </boundary-data>
55
+ On page 20, line 23, please replace the paragraphs with the following paragraphs which show the changes made. </p>
56
+ <p id="p-7" num="7">The system 900 includes all of the multiVPU functionality described herein. For example, the master VPU A <part-num-ref name="">908</part-num-ref>
57
+ processes frame data as instructed by the driver, and <part-num-ref name="driver, and">30</part-num-ref>
58
+ outputs processed frame data <part-num-ref name="outputs processed frame data">909</part-num-ref>
59
+ to the IM <part-num-ref name="IM">912.</part-num-ref>
60
+ The slave VPU B <part-num-ref name="slave VPU B">910</part-num-ref>
61
+ processes frame <boundary-data type="header">
62
+ <confidence value="8">2</confidence>
63
+ </boundary-data>
64
+ <page-break num="2"/>
65
+ <boundary-data type="header">Attorney Docket No. AT<confidence value="4">E</confidence>
66
+ C.P<confidence value="45">O1</confidence>
67
+ 0 Patent App. Serial No. 11/140,114 </boundary-data>
68
+ <boundary-data type="header">Client File No. 050015 S</boundary-data>
69
+ data as instructed by the driver, and outputs processed frame data <part-num-ref name="driver, and outputs processed frame data">911,</part-num-ref>
70
+ which is transferred to the IM <part-num-ref name="IM">912</part-num-ref>
71
+ for combining or compositing. The transfer is performed via the PCIE bus <part-num-ref name="PCIE bus">934</part-num-ref>
72
+ or via a dedicated inter-VPU connection (not shown), as previously described with reference to Fi<confidence value="5">g</confidence>
73
+ ure 6Figu<confidence value="288521">re-699</confidence>
74
+ . In either case, the composited frame is <part-num-ref name="composited frame is">5</part-num-ref>
75
+ output from the IM <part-num-ref name="IM">912</part-num-ref>
76
+ to a display (not shown). </p>
77
+ <boundary-data type="header">
78
+ <confidence value="8">3</confidence>
79
+ </boundary-data>
80
+ </description>
81
+ </us-patent-application>
82
+
prior_art/11141171.xml ADDED
@@ -0,0 +1,348 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11141171</doc-number>
8
+ <date>2005-05-31</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <heading id="h-1">IN THE UNITED STATES PATENT AND TRADEMARK OFFICE</heading>
14
+ <heading id="h-2">APPLICATION FOR UNITED STATES PATENT</heading>
15
+ <heading id="h-3">FOR</heading>
16
+ <heading id="h-4">METHOD AND SYSTEM FOR PRIORITIZING MEETING ATTENDEES</heading>
17
+ <p id="p-1" num="1">Inventor:</p>
18
+ <p id="p-2" num="2">O'Sullivan, Patrick Attorney Docket No.: 260-03<confidence value="8">8</confidence>
19
+ Client Reference No.: LOT9-2005-0047U<confidence value="58">S1</confidence>
20
+ Express Mail Mailing Label No. EV616801601U<confidence value="5">S</confidence>
21
+ Date of Deposit: 5/31/2005 <page-break num="2"/>
22
+ <boundary-data type="header">Patent Application</boundary-data>
23
+ <boundary-data type="header">260-038</boundary-data>
24
+ <boundary-data type="header">LOT9-2005-0047US <confidence value="8">1</confidence>
25
+ </boundary-data>
26
+ </p>
27
+ <heading id="h-5">FIELD OF THE INVENTION</heading>
28
+ <p id="p-3" num="3">The present invention relates generally to electronic calendaring and scheduling software, and more specifically to a method and system for prioritizing meeting attendees.</p>
29
+ <heading id="h-6">BACKGROUND OF THE INVENTION</heading>
30
+ <p id="p-4" num="4">As it is generally known, electronic calendaring and scheduling software applications enable a scheduling user to schedule a calendar event involving multiple attendees, such as a meeting, presentation, teleconference, videoconference, or the like.</p>
31
+ <p id="p-5" num="5">Examples of existing systems in this area include the Lotus Notes<confidence value="5">@</confidence>
32
+ and Lotus Organizer<confidence value="7">s</confidence>
33
+ systems provided by IBM<confidence value="2">@</confidence>
34
+ , and others. </p>
35
+ <p id="p-6" num="6">While existing systems have provided significant functionality to their users, it is still often difficult to find an event time that is suitable to all attendees. This is especially true for events involving large numbers of attendees. Moreover, in companies having geographically distributed employees, the scheduling challenge may be compounded by the need to schedule meeting times across multiple time zones. As a result, meetings and other events must sometimes be significantly delayed beyond what would be otherwise desirable, in order to fully accommodate the individual schedules of large numbers of attendees.</p>
36
+ <p id="p-7" num="7">Some existing systems have attempted to address these challenges by assigning weights to prospective attendees based on their availability. Attendees are then automatically eliminated from scheduling consideration based on lowest availability time, or on a "best fit" algorithm. However, existing systems have not yet sufficiently explored <boundary-data type="header">
37
+ <confidence value="8">2</confidence>
38
+ </boundary-data>
39
+ <page-break num="3"/>
40
+ <boundary-data type="header">Patent Application</boundary-data>
41
+ <boundary-data type="header">260-038</boundary-data>
42
+ <boundary-data type="header">LOT9-2005-0047US <confidence value="8">1</confidence>
43
+ </boundary-data>
44
+ the significant benefits that can be derived for a scheduling user when prospective attendees can be individually or collectively weighted against one another based on the scheduling user's perspective of attendee attendance priority. </p>
45
+ <p id="p-8" num="8">Another shortcoming of some existing systems is that they sometimes couple the TO:, CC:, and BCC: electronic mail ("email") fields to attendee priority levels. In such a case, an event scheduling user may be constrained to selecting from meeting times based on the assumption that, for example, all users listed in the TO: field of an email event notification are required attendees, all users listed in the CC: field of the notification are optional attendees, and all users listed in the BCC: field are being copied just for their information ("FYI"). This prevents the scheduling user from selecting possible event times that are determined based on considering some of the users in the TO: field of the notification as having a higher priority than others, considering some users in the CC: or BCC: fields as having higher priority than some users in the TO: field, and so on.</p>
46
+ <p id="p-9" num="9">Moreover, the impression made by email event notifications is that all users listed in the TO: field are of relatively higher priority to those listed in the other fields. This may motivate a scheduling user to list all attendees within the TO: field, thus potentially preventing generation of possible event times that consider different attendees as having different priorities with regard to the event being scheduled.</p>
47
+ <p id="p-10" num="10">For the reasons stated above and others, it would be desirable to have a new system for prioritizing meeting attendees that effectively facilitates convenient prioritization of prospective attendees based on a scheduling user's perspective of attendee priority with regard to a specific event being scheduled, and independent of how attendees are listed in email event notifications.</p>
48
+ <boundary-data type="header">
49
+ <confidence value="8">3</confidence>
50
+ </boundary-data>
51
+ <boundary-data type="header">Patent Application</boundary-data>
52
+ <boundary-data type="header">260-038</boundary-data>
53
+ <boundary-data type="header">LOT9-2005-0047US <confidence value="8">1</confidence>
54
+ </boundary-data>
55
+ <heading id="h-7">SUMMARY OF THE INVENTION</heading>
56
+ <p id="p-11" num="11">
57
+ <page-break num="4"/>
58
+ To address the above described shortcomings of the prior art and others, a method and system are disclosed for prioritizing attendees in an event scheduling system, based on a scheduling user's perspective of attendee priority. The disclosed system enables a scheduling user to conveniently prioritize attendees in order to improve the probability of success with regard to scheduling a calendar event. The scheduling user is provided with a user interface through which they can prioritize individual attendees, or groups of prospective attendees. An attendee of a lesser priority can be filtered out of the event scheduling process as indicated by the scheduling user, thereby reducing the challenge of finding an event time acceptable to relatively higher priority attendees. As a result, the disclosed system enables scheduling of more timely and effective meetings, and reduces the challenge of scheduling events across multiple attendees and time zones for a scheduling user. </p>
59
+ <p id="p-12" num="12">The disclosed system operates to provide a visual capability in a user interface for a scheduling user that enables fine grained prioritization of individual attendees, or groups of attendees, to allow determination of a relatively larger number of potential event times for a desired event. The disclosed system may be embodied to allow such attendee prioritization in situations where it is not be possible to establish a sufficient range of event times that are acceptable across all invitees. The disclosed system enables a scheduling user to indicate a number of attendee priority levels, where the number N of priority levels used for a given event may be user specific configuration parameter, or supplied on a per event basis. As a result of the user supplied prioritization of <boundary-data type="header">
60
+ <confidence value="8">4</confidence>
61
+ </boundary-data>
62
+ <page-break num="5"/>
63
+ <boundary-data type="header">Patent Application</boundary-data>
64
+ <boundary-data type="header">260-038</boundary-data>
65
+ <boundary-data type="header">LOT9-2005-0047US <confidence value="8">1</confidence>
66
+ </boundary-data>
67
+ prospective attendees, the disclosed system operates to supply possible event times relevant to each priority indicated by the scheduling user. Accordingly, where a scheduling user has assigned prospective attendees to attendee priorities <part-num-ref name="scheduling user has assigned prospective attendees to attendee priorities">1</part-num-ref>
68
+ through N, the disclosed system would respond by simultaneously presenting to the scheduling user N sets of prospective event times corresponding to the assigned priorities. Specifically, a first set of prospective event times would be presented that satisfy the availability constraints of all prospective attendees of priority <part-num-ref name="availability constraints of all prospective attendees of priority">1,</part-num-ref>
69
+ a second set of prospective event times would be presented that satisfy the availability constraints of all attendees of priorities <part-num-ref name="availability constraints of all attendees of priorities">1</part-num-ref>
70
+ and <part-num-ref name="and">2,</part-num-ref>
71
+ a third set of prospective event times would be presented that satisfy the availability constraints of all prospective attendees of priorities <part-num-ref name="availability constraints of all prospective attendees of priorities">1,</part-num-ref>
72
+ <part-num-ref name="availability constraints of all prospective attendees of priorities 1,">2</part-num-ref>
73
+ and <part-num-ref name="and">3,</part-num-ref>
74
+ and so on through a set of prospective event times that satisfy the availability constraints of all prospective attendees of priorities <part-num-ref name="availability constraints of all prospective attendees of priorities">1</part-num-ref>
75
+ through N. </p>
76
+ <p id="p-13" num="13">The disclosed system may further be embodied such that designations of which field a user is listed in for purposes of an email event notification is decoupled from that users priority. Accordingly, a user may be indicated for inclusion in any of the email fields TO:, CC:, BCC:, or the like, may be considered as having a relatively higher or lower priority with respect to any other user contained in any of those fields in the event notification.</p>
77
+ <p id="p-14" num="14">Thus there is disclosed a new system for prioritizing meeting attendees that effectively facilitates convenient prioritization of prospective attendees based on a scheduling user's perspective of attendee priority with regard to the event being scheduled, and that can decouple priorities of event attendees from their positions within email destination address fields of an event notification message.</p>
78
+ <boundary-data type="header">
79
+ <confidence value="8">5</confidence>
80
+ </boundary-data>
81
+ <boundary-data type="header">Patent Application</boundary-data>
82
+ <boundary-data type="header">260-038</boundary-data>
83
+ <boundary-data type="header">LOT9-2005-0047US <confidence value="8">1</confidence>
84
+ </boundary-data>
85
+ <heading id="h-8">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
86
+ <p id="p-15" num="15">
87
+ <page-break num="6"/>
88
+ In order to facilitate a fuller understanding of the present invention, reference is now made to the appended drawings. These drawings should not be construed as limiting the present invention, but are intended to be exemplary only. </p>
89
+ <p id="p-16" num="16">Fig. 1 is a block diagram illustrating hardware and software components in an illustrative embodiment;</p>
90
+ <p id="p-17" num="17">Fig. 2 is a flow chart illustrating steps performed in an illustrative embodiment;</p>
91
+ <p id="p-18" num="18">Fig. 3 is a simplified screen shot of a user interface for event scheduling provided by an illustrative embodiment;</p>
92
+ <p id="p-19" num="19">Fig. 4 is a simplified screen shot of a user interface for prioritizing invitees provided by an illustrative embodiment; and Fig 5 is a simplified screen shot of a user interface for presenting possible meeting times based on user specified attendee priorities.</p>
93
+ <boundary-data type="header">
94
+ <confidence value="8">6</confidence>
95
+ </boundary-data>
96
+ <boundary-data type="header">Patent Application</boundary-data>
97
+ <boundary-data type="header">260-038</boundary-data>
98
+ <boundary-data type="header">LOT9-2005-0047US <confidence value="8">1</confidence>
99
+ </boundary-data>
100
+ <heading id="h-9">DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS</heading>
101
+ <p id="p-20" num="20">
102
+ <page-break num="7"/>
103
+ As shown in Fig. 1, in an embodiment of the disclosed system, a number of software components execute on various computer systems, shown for purposes of illustration in Fig. 1 including a client computer system <part-num-ref name="client computer system">10</part-num-ref>
104
+ and other client computer systems <part-num-ref name="and other client computer systems">12,</part-num-ref>
105
+ shown including a number of client computer systems 12a, 12b, 12c, etc., as well as one or more server computer systems <part-num-ref name="number of client computer systems 12a, 12b, 12c, etc., as well as one or more server computer systems">14.</part-num-ref>
106
+ The client computer systems <part-num-ref name="client computer systems">10</part-num-ref>
107
+ and <part-num-ref name="and">12,</part-num-ref>
108
+ and server computer system(s) <part-num-ref name="and 12, and server computer system(s)">14</part-num-ref>
109
+ may, for example, each include at least one processor, program storage, such as memory, for storing program code executable on the processor, and one or more input/output devices and/or interfaces, such as data communication and/or peripheral devices and/or interfaces. The client computer systems <part-num-ref name="client computer systems">10</part-num-ref>
110
+ and <part-num-ref name="and">12</part-num-ref>
111
+ and server computer system(s) <part-num-ref name="and server computer system(s)">14</part-num-ref>
112
+ are communicably connected by a data communication network <part-num-ref name="data communication network">16,</part-num-ref>
113
+ such as a Local Area Network (LAN), the Internet, or the like, which may also be connected to a number of other client and/or server computer systems. The client computer systems <part-num-ref name="client computer systems">10</part-num-ref>
114
+ and <part-num-ref name="and">12</part-num-ref>
115
+ and server computer system(s) <part-num-ref name="and server computer system(s)">14</part-num-ref>
116
+ may further include appropriate operating system software. </p>
117
+ <p id="p-21" num="21">As further shown in Fig. 1, an event scheduling user <part-num-ref name="event scheduling user">18</part-num-ref>
118
+ is provided with an event scheduling user interface <part-num-ref name="event scheduling user interface">20</part-num-ref>
119
+ by event scheduling client software <part-num-ref name="by event scheduling client software">22</part-num-ref>
120
+ executing on the client computer system <part-num-ref name="client computer system">10.</part-num-ref>
121
+ The event scheduling user interface <part-num-ref name="event scheduling user interface">20</part-num-ref>
122
+ may be provided through a graphical user interface (GUI) provided by the client computer system <part-num-ref name="client computer system">10</part-num-ref>
123
+ to the scheduling user <part-num-ref name="scheduling user">18.</part-num-ref>
124
+ The event scheduling client software <part-num-ref name="event scheduling client software">22</part-num-ref>
125
+ may be embodied through or as part of a rich client application platform providing access to variety of application <boundary-data type="header">
126
+ <confidence value="8">7</confidence>
127
+ </boundary-data>
128
+ <page-break num="8"/>
129
+ <boundary-data type="header">Patent Application</boundary-data>
130
+ <boundary-data type="header">260-038</boundary-data>
131
+ <boundary-data type="header">LOT9-2005-0047US <confidence value="8">1</confidence>
132
+ </boundary-data>
133
+ functionalities, through or as part of a Web browser application program or the like, or in some other specific manner. In one embodiment, the event scheduling client software <part-num-ref name="event scheduling client software">22</part-num-ref>
134
+ operates in cooperation with the event scheduling server software <part-num-ref name="event scheduling server software">24</part-num-ref>
135
+ to provide the disclosed system, but those skilled in the art will recognize that the disclosed system is not limited to such a client-server implementation. Alternatively, the disclosed system may operate in a peer to peer environment, or in any other appropriate application configuration. </p>
136
+ <p id="p-22" num="22">During operation of the embodiment shown in Fig. 1, calendar information and event notifications <part-num-ref name="embodiment shown in Fig. 1, calendar information and event notifications">26</part-num-ref>
137
+ are communicated between the client computer systems <part-num-ref name="client computer systems">10</part-num-ref>
138
+ and <part-num-ref name="and">12</part-num-ref>
139
+ and server computer system <part-num-ref name="and server computer system">24.</part-num-ref>
140
+ For example, calendar information regarding users of the client computer systems <part-num-ref name="client computer systems">10</part-num-ref>
141
+ and <part-num-ref name="and">12</part-num-ref>
142
+ indicating available or free time of users associated with the client computer systems <part-num-ref name="client computer systems">10</part-num-ref>
143
+ and <part-num-ref name="and">12</part-num-ref>
144
+ may be collected by the event scheduling server software <part-num-ref name="event scheduling server software">24.</part-num-ref>
145
+ The event scheduling user <part-num-ref name="event scheduling user">18</part-num-ref>
146
+ uses the event scheduling interface <part-num-ref name="event scheduling interface">20</part-num-ref>
147
+ to define event attendees, and to determine possible event times based on availability of those event attendees. After determination and selection of a desired time for a given event, event notifications such as email messages are conveyed to ones of the client computer systems <part-num-ref name="client computer systems">10</part-num-ref>
148
+ and <part-num-ref name="and">12</part-num-ref>
149
+ in order to notify event attendees, for example by way of the Simple Mail Transfer Protocol (SMTP). As further described below, the event scheduling client software <part-num-ref name="event scheduling client software">22</part-num-ref>
150
+ and event scheduling server software <part-num-ref name="and event scheduling server software">24</part-num-ref>
151
+ enable the event scheduling user, through the event scheduling user interface <part-num-ref name="event scheduling user interface">20,</part-num-ref>
152
+ to conveniently and effectively determine a desirable event time based on attendee priorities of the event scheduling user <part-num-ref name="event scheduling user">18.</part-num-ref>
153
+ </p>
154
+ <boundary-data type="header">
155
+ <confidence value="8">8</confidence>
156
+ </boundary-data>
157
+ <boundary-data type="header">Patent Application</boundary-data>
158
+ <boundary-data type="header">260-038</boundary-data>
159
+ <boundary-data type="header">LOT9-2005-0047US <confidence value="8">1</confidence>
160
+ </boundary-data>
161
+ <p id="p-23" num="23">
162
+ <page-break num="9"/>
163
+ Fig. 2 is a flow chart illustrating steps performed by an embodiment of the disclosed system to enable an event scheduling user to find a desirable event time for a group of event attendees, based on the relative attendee priorities of the event scheduling user. At step <part-num-ref name="event scheduling user. At step">32,</part-num-ref>
164
+ the disclosed system operates to input a number of attendees for an event to be scheduled. The event attendees may be input at step <part-num-ref name="event attendees may be input at step">32</part-num-ref>
165
+ in any specific way, for example through a user interface screen defining which email destination address fields are to be used to contain email addresses corresponding to the event attendees, as further described below, or in some other specific manner. </p>
166
+ <p id="p-24" num="24">At step 34, the disclosed system provides the event scheduling user with the option of prioritizing specific attendees with respect to other attendees, independent from designation of the specific destination address fields in which their corresponding email addresses are to be contained in an event notification email message. The option provided at step <part-num-ref name="option provided at step">34</part-num-ref>
167
+ may be provided through a user interface display object, such as a button, pull down menu, or the like, that can be activated by the event scheduling user clicking on it using a mouse or other pointing device. </p>
168
+ <p id="p-25" num="25">At step 36, in response to user selection of the prioritization option provided at step <part-num-ref name="prioritization option provided at step">34,</part-num-ref>
169
+ the disclosed system enables the event scheduling user to input attendee prioritizations. The specific number of priorities used by the event scheduling user at step <part-num-ref name="event scheduling user at step">36</part-num-ref>
170
+ may be user specified, for example on an event specific basis, or defined as a user specific configuration parameter, or provided in some other appropriate way for a specific embodiment. The disclosed system enables the event scheduling user to indicate a specific priority for each attendee, and/or for groups of attendees as might be defined and associated with corresponding logical group names. The priorities defined at step <part-num-ref name="priorities defined at step">36</part-num-ref>
171
+ <boundary-data type="header">
172
+ <confidence value="8">9</confidence>
173
+ </boundary-data>
174
+ <page-break num="10"/>
175
+ <boundary-data type="header">Patent Application</boundary-data>
176
+ <boundary-data type="header">260-038</boundary-data>
177
+ <boundary-data type="header">LOT9-2005-0047US <confidence value="8">1</confidence>
178
+ </boundary-data>
179
+ are independent from any associations of attendees with email destination address fields in an event notification email message subsequently generated to invite the attendees to the event being scheduled. </p>
180
+ <p id="p-26" num="26">For example, an event scheduling user may consider the event attendees as falling into <part-num-ref name="event attendees as falling into">5</part-num-ref>
181
+ categories, with priority <part-num-ref name="categories, with priority">1</part-num-ref>
182
+ representing the most important attendees for the event, and priority <part-num-ref name="event, and priority">5</part-num-ref>
183
+ represent the least important. Accordingly, at step <part-num-ref name="least important. Accordingly, at step">36</part-num-ref>
184
+ the event scheduling user may assign specific attendees each with one of the priorities <part-num-ref name="priorities">1</part-num-ref>
185
+ through <part-num-ref name="through">5</part-num-ref>
186
+ at step <part-num-ref name="at step">36.</part-num-ref>
187
+ </p>
188
+ <p id="p-27" num="27">Since the priorities provided at step <part-num-ref name="priorities provided at step">36</part-num-ref>
189
+ are independent from the destination address fields for the event notification, the highest priority attendees (priority <part-num-ref name="highest priority attendees (priority">1)</part-num-ref>
190
+ could be included in any destination address field of the notification. This feature, for example, advantageously enables the event scheduling user to select an event time while ensuring that an attendee not included in the TO: field of the event notification is available for the event, and/or that some attendees addressed in the TO: field of the event notification are available for the event while other attendees addressed in that field may not be available, and/or that other specific attendee prioritizations indicated by the event scheduling user are considered. </p>
191
+ <p id="p-28" num="28">In another embodiment, the disclosed system may operate to determine at step <part-num-ref name="disclosed system may operate to determine at step">36</part-num-ref>
192
+ whether all attendees have been assigned priorities by the event scheduling user through the event scheduling user interface. If not, then those attendees for which a priority has not been so assigned are automatically assigned a priority lower than any priority that was explicitly assigned to an attendee by the scheduling user through the event scheduling interface. For example, if the scheduling user assigns a highest priority (priority <part-num-ref name="highest priority (priority">1)</part-num-ref>
193
+ to some subset of the attendees through the event scheduling user interface, <boundary-data type="header">
194
+ <confidence value="88">10</confidence>
195
+ </boundary-data>
196
+ <page-break num="11"/>
197
+ <boundary-data type="header">Patent Application</boundary-data>
198
+ <boundary-data type="header">260-038</boundary-data>
199
+ <boundary-data type="header">LOT9-2005-0047US <confidence value="8">1</confidence>
200
+ </boundary-data>
201
+ and then indicates that they have no more priorities to assign, and/or that possible event times are to be calculated, then the disclosed system may be embodied to automatically assign a lower priority (priority <part-num-ref name="lower priority (priority">2)</part-num-ref>
202
+ to the remaining attendees. Thus a next lower priority with respect to any lowest explicitly assigned priority may be automatically assigned to those attendees to which a priority was not explicitly assigned through the event scheduling interface, for purposes of calculating possible event times. </p>
203
+ <p id="p-29" num="29">In the case where the scheduling user indicates that they have finished assigning priorities, but the set of priorities assigned to attendees does not include one or more higher order priorities with respect to a lowest assigned priority, the disclosed system may be embodied to indicate an error has occurred, and/or provide some number of possible event times based on the priorities that were assigned. For example, if a scheduling user were to only assign priorities <part-num-ref name="scheduling user were to only assign priorities">1</part-num-ref>
204
+ and <part-num-ref name="and">3</part-num-ref>
205
+ to some number of attendees, without assigning priority <part-num-ref name="to some number of attendees, without assigning priority">2</part-num-ref>
206
+ to any assignees, the disclosed system may operate to convey a message or otherwise report a potential error, potentially in the same display that provides possible event times based on those priorities that were assigned, indicating that the scheduling user may have inadvertently forgotten to assign one or more users with the higher order priority, in this case priority <part-num-ref name="higher order priority, in this case priority">2.</part-num-ref>
207
+ </p>
208
+ <p id="p-30" num="30">Based on the attendees determined at step <part-num-ref name="attendees determined at step">32,</part-num-ref>
209
+ and the priorities determined at step <part-num-ref name="priorities determined at step">36,</part-num-ref>
210
+ and further responsive to user selection of the prioritization option provided at step <part-num-ref name="prioritization option provided at step">34,</part-num-ref>
211
+ at step <part-num-ref name="prioritization option provided at step 34, at step">38</part-num-ref>
212
+ the disclosed system operates to determine and present possible event times at which all attendees are available within each of the priorities obtained at step <part-num-ref name="priorities obtained at step">36.</part-num-ref>
213
+ </p>
214
+ <p id="p-31" num="31">The possible event times may then be presented to the event scheduling user in visually associated groups of times reflecting the complete availability of attendees within <boundary-data type="header">
215
+ <confidence value="88">11</confidence>
216
+ </boundary-data>
217
+ <page-break num="12"/>
218
+ <boundary-data type="header">Patent Application</boundary-data>
219
+ <boundary-data type="header">260-038</boundary-data>
220
+ <boundary-data type="header">LOT9-2005-0047US <confidence value="5">1</confidence>
221
+ </boundary-data>
222
+ specific priorities. For example, a first set of possible event times may be presented at which all attendees at priority <part-num-ref name="first set of possible event times may be presented at which all attendees at priority">1</part-num-ref>
223
+ are available. Another set of event times may be presented at which all attendees at priorities <part-num-ref name="are available. Another set of event times may be presented at which all attendees at priorities">1</part-num-ref>
224
+ and <part-num-ref name="and">2</part-num-ref>
225
+ are available, another set at which all attendees at priorities <part-num-ref name="are available, another set at which all attendees at priorities">1,</part-num-ref>
226
+ <part-num-ref name="are available, another set at which all attendees at priorities 1,">2</part-num-ref>
227
+ and <part-num-ref name="and">3</part-num-ref>
228
+ are available, and so on through the complete set of attendee priorities. </p>
229
+ <p id="p-32" num="32">Figs. 3-5 are simplified screen shots as provided through an embodiment of the event scheduling user interface <part-num-ref name="event scheduling user interface">20</part-num-ref>
230
+ of Fig. 1. Fig. 3 shows an example of an event scheduling application user interface <part-num-ref name="event scheduling application user interface">40.</part-num-ref>
231
+ An event subject indication field <part-num-ref name="event subject indication field">42</part-num-ref>
232
+ allows the event scheduling user to enter a subject of the event being scheduled. Meeting time parameters fields <part-num-ref name="event being scheduled. Meeting time parameters fields">44</part-num-ref>
233
+ enable the event scheduling user to enter parameters regarding the event being scheduled, such as start time, end time, and duration. The attendees fields <part-num-ref name="attendees fields">46</part-num-ref>
234
+ enable the event scheduling user to enter names or email addresses associated with attendees for the event. In the example embodiment of Fig. 3, the event scheduling user is allowed to enter attendees into three initial categories: <part-num-ref name="event scheduling user is allowed to enter attendees into three initial categories:">1)</part-num-ref>
235
+ Required (TO:), <part-num-ref name="Required (TO:),">2)</part-num-ref>
236
+ Optional (CC:), and FYI (BCC:). Email addresses of attendees entered into the Required (TO:) category are included in the TO: field of the event notification for the event being scheduled, email addresses of attendees entered into the Optional (CC:) category are included in the CC: field of the event notification for the event being scheduled, and email addresses of attendees entered into the FYI (BCC:) category are included in the BCC: field of the event notification for the event being scheduled. The suggested meeting times <part-num-ref name="suggested meeting times">48</part-num-ref>
237
+ are determined by finding possible event times that most accommodate the schedule information for attendees in the Required (TO:) category, then the attendees in the Optional (CC:) category, and finally potentially also the attendees in the FYI <boundary-data type="header">
238
+ <confidence value="88">12</confidence>
239
+ </boundary-data>
240
+ <page-break num="13"/>
241
+ <boundary-data type="header">Patent Application</boundary-data>
242
+ <boundary-data type="header">260-038</boundary-data>
243
+ <boundary-data type="header">LOT9-2005-0047US <confidence value="8">1</confidence>
244
+ </boundary-data>
245
+ (BCC:) category. Accordingly, the possible event times listed in order beginning with those that best match the schedule of the attendees in the Required (TO:) category, and so on. </p>
246
+ <p id="p-33" num="33">The event scheduling user is provided with a user interface display button <part-num-ref name="user interface display button">50</part-num-ref>
247
+ that can be clicked on with the mouse to request that a selected one of the possible meeting times within the suggested meeting times <part-num-ref name="suggested meeting times">48</part-num-ref>
248
+ is to be used to generate an event notification email message with destination email address fields populated with attendee email addresses as indicated by the Required (TO:), Optional (CC:) and FYI (BCC:) attendee categories. The event scheduling user is also provided with a user interface display button <part-num-ref name="user interface display button">52</part-num-ref>
249
+ that can be clicked on with the mouse to request that another interface screen or the like be provided in order to allow the event scheduling user to indicate attendee priorities to be associated with the event attendees or groups of attendees. An example of such a prioritization is shown by the attendee prioritization user interface <part-num-ref name="attendee prioritization user interface">60</part-num-ref>
250
+ <confidence value="88">of</confidence>
251
+ Fig. 4. </p>
252
+ <p id="p-34" num="34">As shown in Fig. 4, the attendee prioritization user interface <part-num-ref name="attendee prioritization user interface">60</part-num-ref>
253
+ includes an attendee prioritization list <part-num-ref name="attendee prioritization list">62</part-num-ref>
254
+ indicating a priority level associated with each attendee for the event being scheduled. The attendees can be assigned any priority in a user defined range of priorities, which may either be user-determined on an event specific basis, or may be user-configured for use across multiple events. For example, the disclosed system may be embodied to read in numeric priority levels entered into a priority level column <part-num-ref name="priority level column">61</part-num-ref>
255
+ of the attendee prioritization list <part-num-ref name="attendee prioritization list">62,</part-num-ref>
256
+ where each numeric priority level indicates a relative attendee priority, with the highest level priority being priority <part-num-ref name="highest level priority being priority">1,</part-num-ref>
257
+ and higher numbers indicating progressively lower relative priority levels. Each row of the <boundary-data type="header">
258
+ <confidence value="88">13</confidence>
259
+ </boundary-data>
260
+ <page-break num="14"/>
261
+ <boundary-data type="header">Patent Application</boundary-data>
262
+ <boundary-data type="header">260-038</boundary-data>
263
+ <boundary-data type="header">LOT9-2005-0047US <confidence value="5">1</confidence>
264
+ </boundary-data>
265
+ attendee <confidence value="22222222222222">prioritization</confidence>
266
+ list <part-num-ref name="attendee prioritization list">62</part-num-ref>
267
+ further includes indication of an attendee or group of attendees within an invitee column <part-num-ref name="invitee column">63.</part-num-ref>
268
+ The attendees listed in the invitee column <part-num-ref name="invitee column">63</part-num-ref>
269
+ may be represented by user names, email addresses, or other labels. Moreover, the information listed for each attendee in the invitee column <part-num-ref name="invitee column">63</part-num-ref>
270
+ may further include an indication of which email destination address field that is to be used to store the email address for that attendee. In the example of Fig. 4, this information is provided for purposes of illustration within parenthesis following the user name of each attendee. </p>
271
+ <p id="p-35" num="35">The user may thus be automatically provided with a list of attendees in the invitee column <part-num-ref name="invitee column">63,</part-num-ref>
272
+ and then be allowed to enter numeric values indicating attendee priorities in the priority level column. It should be further noted that the attendee name in the invitee column <part-num-ref name="invitee column">63</part-num-ref>
273
+ may indicate a predefined group of users, such as the "DevelopmentTeam" group name shown in Fig. 4. Such a group name would allow an event scheduling user to provide an attendee priority to be assigned to the entire attendee group. In one embodiment, the event scheduling user is further allowed to either assign attendee priority on a group basis to cover all group members, or alternatively provide different priorities to different group members. This permits a group name to be used to define the email destination address field to be used to store the email addresses of the group of the members of the group, and also allow the event scheduling user to independently indicate attendee priorities for individual group members. </p>
274
+ <p id="p-36" num="36">A user interface display button 64 or the like is provided to allow the event scheduling user to cause the attendee prioritization list <part-num-ref name="attendee prioritization list">62</part-num-ref>
275
+ to be re-ordered by priority level. A user interface display button <part-num-ref name="user interface display button">66</part-num-ref>
276
+ is provided to allow the event scheduling user to cause the disclosed system to provide a display of possible event times for the event <boundary-data type="header">
277
+ <confidence value="88">14</confidence>
278
+ </boundary-data>
279
+ <page-break num="15"/>
280
+ <boundary-data type="header">Patent Application</boundary-data>
281
+ <boundary-data type="header">260-038</boundary-data>
282
+ <boundary-data type="header">LOT9-2005-0047US <confidence value="8">1</confidence>
283
+ </boundary-data>
284
+ being scheduled that reflect the attendee priorities defined through the attendee prioritization user interface <part-num-ref name="attendee prioritization user interface">60.</part-num-ref>
285
+ </p>
286
+ <p id="p-37" num="37">Those skilled in the art will recognize that while the embodiment of the disclosed system shown in Fig. 4 includes a specific technique for entering and presenting attendee priorities, the present invention is not so limited. Accordingly, alternative embodiments may provide other specific interface designs or techniques allowing a scheduling user to provide attendee priorities for individual event attendees and/or groups of attendees.</p>
287
+ <p id="p-38" num="38">Similarly, those skilled in the art will recognize that attendee priorities need not be entered through a separate user interface screen than the user interface screen provided to allow the event scheduling user to define the email destination address fields to be used to store the email addresses of event attendees, and the same user interface screen may potentially be used for both purposes. Finally, the buttons <part-num-ref name="buttons">64</part-num-ref>
288
+ and <part-num-ref name="and">66</part-num-ref>
289
+ are only examples of user interface mechanisms that may be used to provide access to the associated functions, and various other specific techniques may be used for this purpose in the alternative. </p>
290
+ <p id="p-39" num="39">Fig. 5 shows an example of an event time selection interface <part-num-ref name="event time selection interface">70</part-num-ref>
291
+ provided in response to an event scheduling user clicking on the user interface display button <part-num-ref name="user interface display button">66</part-num-ref>
292
+ shown in Fig. 4. As shown in Fig. 5, a list <part-num-ref name="list">73</part-num-ref>
293
+ of possible event time sets for attendee priority sets includes a number of rows, each row having a column <part-num-ref name="column">74</part-num-ref>
294
+ for the attendee priority sets corresponding to the possible event times in the column <part-num-ref name="column">76.</part-num-ref>
295
+ In the embodiment of Fig. 5, the first row includes possible event times in column <part-num-ref name="first row includes possible event times in column">76</part-num-ref>
296
+ at which all attendees having priority <part-num-ref name="at which all attendees having priority">1</part-num-ref>
297
+ are available. The second row includes possible event times in column <part-num-ref name="second row includes possible event times in column">76</part-num-ref>
298
+ at which all attendees having priorities <part-num-ref name="at which all attendees having priorities">1</part-num-ref>
299
+ or <part-num-ref name="or">2</part-num-ref>
300
+ are available. The third <boundary-data type="header">
301
+ <confidence value="88">15</confidence>
302
+ </boundary-data>
303
+ <page-break num="16"/>
304
+ <boundary-data type="header">Patent Application</boundary-data>
305
+ <boundary-data type="header">260-038</boundary-data>
306
+ <boundary-data type="header">LOT9-2005-0047US <confidence value="8">1</confidence>
307
+ </boundary-data>
308
+ row includes possible event times at which all attendees having priorities <part-num-ref name="third row includes possible event times at which all attendees having priorities">1,</part-num-ref>
309
+ or <part-num-ref name="third row includes possible event times at which all attendees having priorities 1, or">2,</part-num-ref>
310
+ or <part-num-ref name="third row includes possible event times at which all attendees having priorities 1, or 2, or">3</part-num-ref>
311
+ are available, and so on. The list <part-num-ref name="list">73</part-num-ref>
312
+ may further indicate the total numbers of attendees that are available and unavailable for each possible event time. The event scheduling user may then select one of the presented possible event times by clicking on it, and then click on the button <part-num-ref name="button">80</part-num-ref>
313
+ to use that selected time for the event being scheduled. Event notifications will be sent out using email having destination address fields populated with attendee email addresses as indicated in the user interface of Fig. 3. The event scheduling user may also choose to click on the button <part-num-ref name="button">78</part-num-ref>
314
+ to return to the user interface of Fig. 3 to modify the associations between attendees and email notification destination address fields, or click on the button <part-num-ref name="button">82</part-num-ref>
315
+ to return to the user interface of Fig. 4 to re- prioritize the attendees. In this way the disclosed system enables great convenience and flexibility to the event scheduling user to modify the attendee prioritizations independent from the associations between attendees and email notification destination address fields, resulting in quick access to a wider range of possible event times meeting the event requirements, and therefore more timely and effective event scheduling. </p>
316
+ <p id="p-40" num="40">The disclosed system provides many significant advantages in various specific situations. For example, in a situation where the event scheduling user would like to set up a meeting with attendees A,B,C,D,E and F, and would further like Manager M and her administrative assistant N to attend. The event scheduling user may prefer to copy Manager M and her assistant on the event notification email message using the CC:</p>
317
+ <p id="p-41" num="41">destination address field, but also ensure that the meeting is scheduled for a time at which both M and N are available. The disclosed system enables this scheduling and notification to be conveniently performed.</p>
318
+ <boundary-data type="header">
319
+ <confidence value="88">16</confidence>
320
+ </boundary-data>
321
+ <boundary-data type="header">Patent Application</boundary-data>
322
+ <boundary-data type="header">260-038</boundary-data>
323
+ <boundary-data type="header">LOT9-2005-0047US <confidence value="8">1</confidence>
324
+ </boundary-data>
325
+ <p id="p-42" num="42">
326
+ <page-break num="17"/>
327
+ Additionally, situations often arise where the success of a meeting may come down to the ability to aggregate groups of key attendees. For example, a meeting may have little value if either attendees (A AND B) OR (C AND D) cannot attend. The disclosed system enables associating priorities with attendees in a dynamic way that allows the event scheduling user to easily determine possible event times that satisfy such logical requirements between attendees, and to select the actual event time accordingly. </p>
328
+ <p id="p-43" num="43">Figs. 1 and <part-num-ref name="and">2</part-num-ref>
329
+ are block diagram and flowchart illustrations of methods, apparatus(s) and computer program products according to an embodiment of the invention. It will be understood that each block of Figs. 1 and <part-num-ref name="and">2,</part-num-ref>
330
+ and combinations of these blocks, can be implemented by computer program instructions. These computer program instructions may be loaded onto a computer or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus create means for implementing the functions specified in the block or blocks. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the <boundary-data type="header">
331
+ <confidence value="88">17</confidence>
332
+ </boundary-data>
333
+ <page-break num="18"/>
334
+ <boundary-data type="header">Patent Application</boundary-data>
335
+ <boundary-data type="header">260-038</boundary-data>
336
+ <boundary-data type="header">LOT9-2005-0047US <confidence value="4">1</confidence>
337
+ </boundary-data>
338
+ computer or other programmable apparatus provide steps for implementing the functions specified in the block or blocks. </p>
339
+ <p id="p-44" num="44">Those skilled in the art should readily appreciate that programs defining the functions of the present invention can be delivered to a computer in many forms;</p>
340
+ <p id="p-45" num="45">including, but not limited to: (a) information permanently stored on non-writable storage media (e.g. read only memory devices within a computer such as ROM or CD-ROM disks readable by a computer <confidence value="555">1/0</confidence>
341
+ attachment); (b) information alterably stored on writable storage media (e.g. floppy disks and hard drives); or (c) information conveyed to a computer through communication media for example using wireless, baseband signaling or broadband signaling techniques, including carrier wave signaling techniques, such as over computer or telephone networks via a modem. </p>
342
+ <p id="p-46" num="46">While the invention is described through the above exemplary embodiments, it will be understood by those of ordinary skill in the art that modification to and variation of the illustrated embodiments may be made without departing from the inventive concepts herein disclosed. Moreover, while the preferred embodiments are described in connection with various illustrative program command structures, one skilled in the art will recognize that they may be embodied using a variety of specific command structures.</p>
343
+ <boundary-data type="header">
344
+ <confidence value="88">18</confidence>
345
+ </boundary-data>
346
+ </description>
347
+ </us-patent-application>
348
+
prior_art/11146897.xml ADDED
@@ -0,0 +1 @@
 
 
1
+ <?xml version="1.0" encoding="utf-8"?><pat:SpecificationDocument xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:pat="urn:us:gov:doc:uspto:patent" xmlns:ent="urn:us:gov:doc:uspto:enterprise" xmlns="urn:us:gov:doc:uspto:patent" xmlns:tbl="http://www.oasis-open.org/tables/exchange/1.0" xmlns:com="http://www.wipo.int/standards/XMLSchema/Common/1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XML_SCHEMAS/V1_3/SpecificationDocument_1_0.xsd" pat:instanceFileName="11146897.09-30-2014.I0PZ71LTPXXIFW3.SPEC.XML" pat:id="I0PZ71LTPXXIFW3"><pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001"><pat:ApplicationHeaderDetails><pat:ApplicationNumber>11146897</pat:ApplicationNumber></pat:ApplicationHeaderDetails><pat:PageTotalQuantity>8</pat:PageTotalQuantity><pat:ParagraphTotalQuantity>58</pat:ParagraphTotalQuantity></pat:DocumentHeaderDetails><pat:MailRoomDate>2014-09-30</pat:MailRoomDate><pat:DocumentCreateDateText>2014-09-30</pat:DocumentCreateDateText><pat:DocumentTitle>SPECIFICATION DOCUMENT</pat:DocumentTitle><pat:Specification><?PageStart number='1'?><pat:P pat:pNumber="1" pat:id="p-1"><pat:PatentImage pat:id='ID-00002' pat:imageContentCategory='Drawing' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11146897.09-30-2014.I0PZ71LTPXXIFW3.SPEC_30040671.1.300.307.852.414.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.357</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.84</com:WidthMeasure><com:ALTText>Drawing</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="2" pat:id="p-2">Amendments to the S<pat:OCRConfidenceData pat:levelNumber='5'>p</pat:OCRConfidenceData>ecification: </pat:P><pat:P pat:pNumber="3" pat:id="p-3">Please replace the <pat:PartName pat:idref='PN-00001'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00001'>3</pat:PartNumber>, <pat:PartName pat:idref='PN-00002'>line</pat:PartName> <pat:PartNumber pat:id='PN-00002'>17</pat:PartNumber>, of the application as filed with the following replacement paragraph: </pat:P><pat:P pat:pNumber="4" pat:id="p-4">The system provides a data sharing feature including a synchronization architecture by which a diabetic client may share data useful in management of the diabetic condition with selected health care professionals. This architecture may be implemented through an Internet-based synchronizing server. The system can handle incrementally added or modified data that is synchronized to the <pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>nternet-based server. </pat:P><pat:P pat:pNumber="5" pat:id="p-5">This f<pat:OCRConfidenceData pat:levelNumber='5621241'>eatures</pat:OCRConfidenceData>feature saves having to copy a full database each time a synchronization operation is requested. A security process assures that data is shared only as authorized by the original user and is accepted by the sharing health care professional. </pat:P><pat:P pat:pNumber="6" pat:id="p-6">Please replace the <pat:PartName pat:idref='PN-00003'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00003'>5</pat:PartNumber>, <pat:PartName pat:idref='PN-00004'>line</pat:PartName> <pat:PartNumber pat:id='PN-00004'>16</pat:PartNumber>, of the application as filed with the following replacement paragraph: </pat:P><pat:P pat:pNumber="7" pat:id="p-7"><pat:OCRConfidenceData pat:levelNumber='56256625884'>F-re-2-2Fiq</pat:OCRConfidenceData>ures 22A-B. Pre/Post Meal Mode with Hypo/Hyper Checked ([[left]]A); A<pat:OCRConfidenceData pat:levelNumber='66'>ll</pat:OCRConfidenceData> Time Periods Mode ([[right]]<pat:OCRConfidenceData pat:levelNumber='58'>B)</pat:OCRConfidenceData> Please replace the <pat:PartName pat:idref='PN-00005'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00005'>14</pat:PartNumber>, <pat:PartName pat:idref='PN-00006'>line</pat:PartName> <pat:PartNumber pat:id='PN-00006'>14</pat:PartNumber>, of the application as filed with the following replacement paragraph: </pat:P><pat:P pat:pNumber="8" pat:id="p-8">After installing the System on a PC or PC appliance, glucose data can be uploaded or copied from a compatible glucose meter, or data can be typed in from a keyboard, or imported from a file. One can maintain a record of his or her glucose, carbohydrates, insulin, exercise, state of health, doctor visits, medications, blood ketones, and/or laboratory results. One may enter as much or as little information as desired. </pat:P><pat:P pat:pNumber="9" pat:id="p-9"><pat:BoundaryData><pat:HeaderText>Page 2 <pat:OCRConfidenceData pat:levelNumber='88'>of</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='88'>28</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='2'?><pat:PatentImage pat:id='ID-00003' pat:imageContentCategory='Graph' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11146897.09-30-2014.I0PZ71LTPXXIFW3.SPEC_30040672.1.300.307.852.414.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.357</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.84</com:WidthMeasure><com:ALTText>Graph</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="10" pat:id="p-10">Please replace the <pat:PartName pat:idref='PN-00007'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00007'>14</pat:PartNumber>, <pat:PartName pat:idref='PN-00008'>line</pat:PartName> <pat:PartNumber pat:id='PN-00008'>20</pat:PartNumber>, of the application as filed with the following replacement paragraph: </pat:P><pat:P pat:pNumber="11" pat:id="p-11">The System analyzes the data and displays it in simple, clear reports (graphs and tables). The reports can be viewed on the computer screen or on the display of the computing appliance or they can be printed out (black-and-white or color). One can also automatically print one or more reports that are selected to be printed or displayed <pat:OCRConfidenceData pat:levelNumber='6888'>once</pat:OCRConfidenceData> each data is uploaded from a particular device. </pat:P><pat:P pat:pNumber="12" pat:id="p-12">Please replace the <pat:PartName pat:idref='PN-00009'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00009'>18</pat:PartNumber>, <pat:PartName pat:idref='PN-00010'>line</pat:PartName> <pat:PartNumber pat:id='PN-00010'>15</pat:PartNumber>, of the application as filed with the following replacement paragraph: </pat:P><pat:P pat:pNumber="13" pat:id="p-13">A Resource Links section provides options to take a user directly to resources available [[as]]<pat:OCRConfidenceData pat:levelNumber='1'>a</pat:OCRConfidenceData> the System website. These may include Ask the Diabetes Educator, Diabetes News, Check for Software Updates and Contact Tech Support. Contact tech support is preferably an email support option that, upon clicking, will result in a pop-up window either informing the user that a "local mail client" is not available or will supply the user with the <pat:OCRConfidenceData pat:levelNumber='5'>e</pat:OCRConfidenceData>-mail address for Customer Service/Tech Support. </pat:P><pat:P pat:pNumber="14" pat:id="p-14">Please replace the <pat:PartName pat:idref='PN-00011'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00011'>18</pat:PartNumber>, <pat:PartName pat:idref='PN-00012'>line</pat:PartName> <pat:PartNumber pat:id='PN-00012'>21</pat:PartNumber>, of the application as filed with the following replacement paragraph: </pat:P><pat:P pat:pNumber="15" pat:id="p-15">A Turning On Password Protection option is for users desiring to protect their data (and their privacy) by requiring the entry of a User ID and Password each time they start the System or each time they select a different user in the Select User field (Home version) or the Select HCP field (HCP version). To turn on password protection, on the Home page, a user may select System Settings from the File drop-down box (see FIG. </pat:P><pat:P pat:pNumber="16" pat:id="p-16">11). If System Settings is grayed out, then a user does not have the User Rights to turn on password protection. If a user does have User Rights, then the System Settings screen displays (see FIG. 12). When the box to Require User Logon is checked, then password protection is turned on and the first screen will be a Logon to System screen (see FIG. 13). This screen will also display when changing users in the Select User field <pat:BoundaryData><pat:HeaderText>Page 3 <pat:OCRConfidenceData pat:levelNumber='88'>of</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='88'>28</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='3'?><pat:PatentImage pat:id='ID-00004' pat:imageContentCategory='Graph' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11146897.09-30-2014.I0PZ71LTPXXIFW3.SPEC_30040673.1.300.307.852.414.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.357</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.84</com:WidthMeasure><com:ALTText>Graph</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="17" pat:id="p-17">(Home version) or in the Select H<pat:OCRConfidenceData pat:levelNumber='5'>C</pat:OCRConfidenceData>P field (H<pat:OCRConfidenceData pat:levelNumber='5'>C</pat:OCRConfidenceData>P version). The home page will appear upon typing in or otherwise <pat:OCRConfidenceData pat:levelNumber='14221224'>inerving</pat:OCRConfidenceData>insertin<pat:OCRConfidenceData pat:levelNumber='4'>q</pat:OCRConfidenceData> a User ID and Password. </pat:P><pat:P pat:pNumber="18" pat:id="p-18">Please replace the <pat:PartName pat:idref='PN-00013'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00013'>20</pat:PartNumber>, <pat:PartName pat:idref='PN-00014'>line</pat:PartName> <pat:PartNumber pat:id='PN-00014'>9</pat:PartNumber>, of the application as filed with the following replacement paragraph: </pat:P><pat:P pat:pNumber="19" pat:id="p-19">A graph can be viewed preferably in at least three modes. A desired mode may be selected from a <pat:PartName pat:idref='PN-00015'>Mode drop-down box</pat:PartName> <pat:PartNumber pat:id='PN-00015'>40</pat:PartNumber>, such as that illustrated at FIG. 21. </pat:P><pat:P pat:pNumber="20" pat:id="p-20">Standard, Pre/Post Meal and A<pat:OCRConfidenceData pat:levelNumber='66'>ll</pat:OCRConfidenceData> Time Periods modes may be selected. In Standard mode, glucose target ranges set apply to all glucose readings, regardless of when the glucose reading is taken. For example, target ranges will be the same for pre-meal readings as for post-meal readings or bedtime readings. In Pre/Post Meal mode, glucose target ranges set for pre-meal readings can be different from the target ranges for post-meal readings. In A<pat:OCRConfidenceData pat:levelNumber='66'>ll</pat:OCRConfidenceData> Time Periods mode, glucose target ranges set can be different for each time period listed, for example, Pre-Bkfst, Post-Bkfst, Pre-Lunch, Post- Lunch, Pre-Dinner, Post-Dinner, Bed, and Sleep. FIG. [[22]]2<pat:OCRConfidenceData pat:levelNumber='8'>2</pat:OCRConfidenceData>A illustrates <pat:OCRConfidenceData pat:levelNumber='5555685'>r-e/Pst</pat:OCRConfidenceData>Pre/Post Meal Mode with Hypo/Hyper checked <pat:OCRConfidenceData pat:levelNumber='528555'>(4eft)</pat:OCRConfidenceData> and FIG. 22B illustrates <pat:OCRConfidenceData pat:levelNumber='866'>All</pat:OCRConfidenceData> Time Periods Mode<pat:OCRConfidenceData pat:levelNumber='6658814566'>-(righ-t).</pat:OCRConfidenceData> </pat:P><pat:P pat:pNumber="21" pat:id="p-21">Please replace the <pat:PartName pat:idref='PN-00016'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00016'>21</pat:PartNumber>, <pat:PartName pat:idref='PN-00017'>line</pat:PartName> <pat:PartNumber pat:id='PN-00017'>4</pat:PartNumber>, of the application as filed with the following replacement paragraph: </pat:P><pat:P pat:pNumber="22" pat:id="p-22">To customize Time Periods to a normal daily schedule, a user can click on up/down arrows next to a time period (for example, Pre-Bkfst, Post-Bkfst, Sleep, etc.) to change the time. To automatically restore all Time Periods to the times shown here as defaults, a user can click Restore Default Time Periods in the box illustrated at FIG. 24. </pat:P><pat:P pat:pNumber="23" pat:id="p-23">The System will generally not allow a user to enter a <pat:PartName pat:idref='PN-00018'>normal daily schedule that exceeds</pat:PartName> <pat:PartNumber pat:id='PN-00018'>24</pat:PartNumber> hours. If a user tries, he or she will receive an error message illustrated at FIG. 25, and the time periods will be readjusted to <pat:PartName pat:idref='PN-00019'>equal</pat:PartName> <pat:PartNumber pat:id='PN-00019'>24</pat:PartNumber> hours. [[As]]A user can select a Glucose Unit of Measure from the drop-down box illustrated at FIG. 26. The default is mg/dL; and another choice is mmol/L. </pat:P><pat:P pat:pNumber="24" pat:id="p-24"><pat:BoundaryData><pat:HeaderText>Page 4 <pat:OCRConfidenceData pat:levelNumber='88'>of</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='88'>28</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='4'?><pat:PatentImage pat:id='ID-00005' pat:imageContentCategory='Graph' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11146897.09-30-2014.I0PZ71LTPXXIFW3.SPEC_30040674.1.300.307.852.414.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.357</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.84</com:WidthMeasure><com:ALTText>Graph</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="25" pat:id="p-25">Please replace the <pat:PartName pat:idref='PN-00020'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00020'>24</pat:PartNumber>, <pat:PartName pat:idref='PN-00021'>line</pat:PartName> <pat:PartNumber pat:id='PN-00021'>5</pat:PartNumber>, of the application as filed and amended on September 9, 2010 with the following replacement paragraph: </pat:P><pat:P pat:pNumber="26" pat:id="p-26">There are three ways to enter events (data) into the System in accordance with a preferred embodiment: upload from a device, manually enter data (e.g., from a keyboard, and import an existing file or database<pat:OCRConfidenceData pat:levelNumber='2'>}</pat:OCRConfidenceData>. The System can upload data from supported glucose monitoring devices (meters), such as Free<pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData>tyle Meter, Precision Xtra Meter, Free<pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData>tyle Flash Meter, Free<pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData>tyle Tracker System, and glucose meters of companies other than Abbott Diabetes Care <pat:OCRConfidenceData pat:levelNumber='66'>In</pat:OCRConfidenceData>c, as well as insulin pumps. At least the following data (event types) may be automatically uploaded to the System when uploading from a device: glucose readings, state of health, insulin doses, lab results, carbohydrates, medical exams, exercise, ketones (blood), medications and notes. Data previously uploaded from a device will not be overwritten when uploading again from that same device. Only the new data will be uploaded to the user's file. Meter functions, displays, and printed output assume a single glucose calibration type, either plasma or whole blood. When uploading glucose data from a device, the System does not differentiate between devices that are whole-blood or plasma calibrated. The System merely uploads the data with no calculations made. Because there are slight differences between the two calibrations, a user should not mix data from devices that use different calibration references. Uploading data into a user's account occurs if the device contains only that person's data. The System is preferably designed not to upload a specific portion of data from a device if data is intermixed with data from another person. </pat:P><pat:P pat:pNumber="27" pat:id="p-27">Please replace the <pat:PartName pat:idref='PN-00022'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00022'>24</pat:PartNumber>, <pat:PartName pat:idref='PN-00023'>line</pat:PartName> <pat:PartNumber pat:id='PN-00023'>26</pat:PartNumber>, of the application as filed with the following replacement paragraph: </pat:P><pat:P pat:pNumber="28" pat:id="p-28">Before uploading, the device is connected to an available <pat:OCRConfidenceData pat:levelNumber='66'>CO</pat:OCRConfidenceData>M port on a PC or other computing appliance using an approved data cable for that device. [[A]]A<pat:OCRConfidenceData pat:levelNumber='8'>n</pat:OCRConfidenceData> exemplary cable connection is illustrated at FIG. 60. To set up the device to the computing device, on the Home page, the user whose data is being uploaded from the <pat:BoundaryData><pat:HeaderText>Page 5 <pat:OCRConfidenceData pat:levelNumber='88'>of</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='88'>28</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='5'?><pat:PatentImage pat:id='ID-00006' pat:imageContentCategory='Graph' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11146897.09-30-2014.I0PZ71LTPXXIFW3.SPEC_30040675.1.300.307.852.414.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.357</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.84</com:WidthMeasure><com:ALTText>Graph</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="29" pat:id="p-29">device is selected, from the select user menu illustrated at the Home page of FIG. 61. </pat:P><pat:P pat:pNumber="30" pat:id="p-30">Next, <pat:PartName pat:idref='PN-00024'>Data Entry</pat:PartName> <pat:PartNumber pat:id='PN-00024'>72</pat:PartNumber> is selected on the <pat:PartName pat:idref='PN-00025'>main menu bar</pat:PartName> <pat:PartNumber pat:id='PN-00025'>2</pat:PartNumber>, as illustrated at FIG. 62; and <pat:PartName pat:idref='PN-00026'>then Device Setup</pat:PartName> <pat:PartNumber pat:id='PN-00026'>74</pat:PartNumber> is chosen from the drop-down list. </pat:P><pat:P pat:pNumber="31" pat:id="p-31">Please replace the <pat:PartName pat:idref='PN-00027'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00027'>25</pat:PartNumber>, <pat:PartName pat:idref='PN-00028'>line</pat:PartName> <pat:PartNumber pat:id='PN-00028'>24</pat:PartNumber>, of the application as filed with the following replacement paragraph: </pat:P><pat:P pat:pNumber="32" pat:id="p-32">A device upload may be undone. That is, the data from the most recent device upload may be undone as long as no data has been manually entered since the device upload and another user has not been selected. DataEntry is selected on the main menu bar of the Home page; <pat:PartName pat:idref='PN-00029'>then Undo Last Upload</pat:PartName> <pat:PartNumber pat:id='PN-00029'>88</pat:PartNumber> is chosen from the drop-down menu illustrated at FIG. 68. The System will then automatically undo the last upload. </pat:P><pat:P pat:pNumber="33" pat:id="p-33">Please replace the <pat:PartName pat:idref='PN-00030'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00030'>26</pat:PartNumber>, <pat:PartName pat:idref='PN-00031'>line</pat:PartName> <pat:PartNumber pat:id='PN-00031'>8</pat:PartNumber>, of the application as filed with the following replacement paragraph: </pat:P><pat:P pat:pNumber="34" pat:id="p-34">When HotSync completes, options may be selected for upload from the Free<pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData>tyle Tracker of other PDA-based device such as Event Data, Glucose Targets, Time Periods and Preferences, as illustrated at FIG. 70. Event Data will be generally <pat:OCRConfidenceData pat:levelNumber='556255555555'>autemcatic-y</pat:OCRConfidenceData>automaticall<pat:OCRConfidenceData pat:levelNumber='5'>y</pat:OCRConfidenceData> uploaded from the Free<pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData>tyle Tracker System. Glucose Targets may be selected to upload and overwrite the Glucose Targets data with data from the Free<pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData>tyle Tracker System. Time Periods may be selected to reset Time Periods data according to data from the Free<pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData>tyle Tracker System. Preferences may be selected to overwrite Preference Settings with settings from the Free<pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData>tyle Tracker System. Set as Default may be selected if a user wants to save these options as the defaults. If prompted to assign the device to a current user or to a new user, as illustrated at FIG. 72, then OK should be clicked after making a choice, keeping in mind that more than one device may be associated with a same user. </pat:P><pat:P pat:pNumber="35" pat:id="p-35"><pat:BoundaryData><pat:HeaderText>Page 6 <pat:OCRConfidenceData pat:levelNumber='88'>of</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='88'>28</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='6'?><pat:PatentImage pat:id='ID-00007' pat:imageContentCategory='Graph' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11146897.09-30-2014.I0PZ71LTPXXIFW3.SPEC_30040676.1.300.307.852.414.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.357</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.84</com:WidthMeasure><com:ALTText>Graph</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="36" pat:id="p-36">Please replace the <pat:PartName pat:idref='PN-00032'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00032'>28</pat:PartNumber>, <pat:PartName pat:idref='PN-00033'>line</pat:PartName> <pat:PartNumber pat:id='PN-00033'>27</pat:PartNumber>, of the application as filed with the following replacement paragraph: </pat:P><pat:P pat:pNumber="37" pat:id="p-37">Some databases can be imported directly into the System. Databases from certain programs may be automatically detected by the System as long as the software for the programs that created them is installed on the user's PC. These programs are referred to as supported databases. To import a database, <pat:PartName pat:idref='PN-00034'>DataEntry</pat:PartName> <pat:PartNumber pat:id='PN-00034'>118</pat:PartNumber> is selected on the <pat:PartName pat:idref='PN-00035'>main menu bar</pat:PartName> <pat:PartNumber pat:id='PN-00035'>2</pat:PartNumber> of the Home page; and <pat:PartName pat:idref='PN-00036'>then Import</pat:PartName> <pat:PartNumber pat:id='PN-00036'>120</pat:PartNumber> is selected from the drop- down box. From the <pat:PartName pat:idref='PN-00037'>Import drop-down box</pat:PartName> <pat:PartNumber pat:id='PN-00037'>122</pat:PartNumber>, the name of the device to upload the database from is selected as illustrated at FIG. 96. If the database is detected, the System will simply ask the user to confirm the import operation. If the database is not detected, the file browser opens as illustrated at FIG. 97. The user then browses to the directory where the file is located, selects the file type in the <pat:PartName pat:idref='PN-00038'>Files of Type window</pat:PartName> <pat:PartNumber pat:id='PN-00038'>124</pat:PartNumber>, and [[ff<pat:OCRConfidenceData pat:levelNumber='2855'>]]jf</pat:OCRConfidenceData> the file is located in that directory, it will be displayed and can be opened. FIG. </pat:P><pat:P pat:pNumber="38" pat:id="p-38">98 illustrates an Import Drop-Down Box for Activating Free<pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData>tyle Co<pat:OCRConfidenceData pat:levelNumber='5'>P</pat:OCRConfidenceData>ilot I Data, and FIG. </pat:P><pat:P pat:pNumber="39" pat:id="p-39">99 illustrates an Import Drop-Down List for Importing Events From a File. FIG. 100 illustrates a File Browser Window for selecting a file type for automatic import according to file type. </pat:P><pat:P pat:pNumber="40" pat:id="p-40">Please replace the <pat:PartName pat:idref='PN-00039'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00039'>48</pat:PartNumber>, <pat:PartName pat:idref='PN-00040'>line</pat:PartName> <pat:PartNumber pat:id='PN-00040'>7</pat:PartNumber>, of the application as filed with the following replacement paragraph: </pat:P><pat:P pat:pNumber="41" pat:id="p-41">The Weekly Pump View Report shows the components of insulin doses for each day in a seven-day period in bar graph (FIG. 134) and pie chart (FIG. 135) formats. To select the w<pat:PartName pat:idref='PN-00041'>eek </pat:PartName>(<pat:PartNumber pat:id='PN-00041'>7</pat:PartNumber> days) for the data a user wants to view, using the date field on the right (see FIG. 133), the user can select the last date in the week the user wants to see (Aug. 3, 2004, for example). The user can set the date field on the left to the first day of that week (Jul. 28, 2004, for example). FIG. 133 illustrates a Date Field for Selecting a Date. FIGS. 134-135 <pat:OCRConfidenceData pat:levelNumber='1121225552'>ilstr-ates</pat:OCRConfidenceData>illustrate Weekly Pump View Reports: Bar Graph and Pie Charts and Glucose Statistics Table, respectively. A Glucose Statistics table (see FIG. </pat:P><pat:P pat:pNumber="42" pat:id="p-42">135) summarizes the glucose readings for the week displayed. </pat:P><pat:P pat:pNumber="43" pat:id="p-43"><pat:BoundaryData><pat:HeaderText>Page 7 <pat:OCRConfidenceData pat:levelNumber='88'>of</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='88'>28</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='7'?><pat:PatentImage pat:id='ID-00008' pat:imageContentCategory='Graph' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11146897.09-30-2014.I0PZ71LTPXXIFW3.SPEC_30040677.1.300.307.852.414.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.357</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.84</com:WidthMeasure><com:ALTText>Graph</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="44" pat:id="p-44">Please replace the <pat:PartName pat:idref='PN-00042'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00042'>50</pat:PartNumber>, <pat:PartName pat:idref='PN-00043'>line</pat:PartName> <pat:PartNumber pat:id='PN-00043'>10</pat:PartNumber>, of the application as filed with the following replacement paragraph: </pat:P><pat:P pat:pNumber="45" pat:id="p-45">The H<pat:OCRConfidenceData pat:levelNumber='5'>C</pat:OCRConfidenceData>P first sets up the values in this table (see FIG. 141). Insulin adjustment may not be necessary for every Home user. The Glucose Start Value (mg<pat:OCRConfidenceData pat:levelNumber='5'>/</pat:OCRConfidenceData>dL) in the table is the blood glucose level at which the insulin dose should be increased. </pat:P><pat:P pat:pNumber="46" pat:id="p-46">Beginning with this value, consecutive blood glucose ranges are provided for each increase in insulin. These ranges are determined by the value entered as the patient's Insulin Sensitivity. The Insulin Dosage Amount is the amount of insulin above the patient's normal dose that should be taken when the patient's blood glucose level falls within the range specified. The Insulin Adjustment Table is provided as a convenient reference, and entries made in this table are generally not used by other application features. </pat:P><pat:P pat:pNumber="47" pat:id="p-47">Please replace the <pat:PartName pat:idref='PN-00044'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00044'>53</pat:PartNumber>, <pat:PartName pat:idref='PN-00045'>line</pat:PartName> <pat:PartNumber pat:id='PN-00045'>16</pat:PartNumber>, of the application as filed with the following replacement paragraph: </pat:P><pat:P pat:pNumber="48" pat:id="p-48">FIG. 146 illustrates a Synchronization Summary Screen. A confirmation message is sent to the user from the Host and to the user's <pat:OCRConfidenceData pat:levelNumber='5'>e</pat:OCRConfidenceData>-mail address. FIG. 147 illustrates a Confirmation Message From the Host<pat:OCRConfidenceData pat:levelNumber='2'>.</pat:OCRConfidenceData> </pat:P><pat:P pat:pNumber="49" pat:id="p-49">Please replace the <pat:PartName pat:idref='PN-00046'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00046'>56</pat:PartNumber>, <pat:PartName pat:idref='PN-00047'>line</pat:PartName> <pat:PartNumber pat:id='PN-00047'>1</pat:PartNumber>, of the application as filed with the following replacement paragraph: </pat:P><pat:P pat:pNumber="50" pat:id="p-50">FIG. 155 illustrates an Assign Access Level Screen. The Host then displays the Process Complete screen and sends an invitation to share data to the HCP. FIG. 156 illustrates a Process Complete Screen. </pat:P><pat:P pat:pNumber="51" pat:id="p-51">Please replace the <pat:PartName pat:idref='PN-00048'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00048'>61</pat:PartNumber>, <pat:PartName pat:idref='PN-00049'>line</pat:PartName> <pat:PartNumber pat:id='PN-00049'>2</pat:PartNumber>, of the application as filed with the following replacement paragraph: </pat:P><pat:P pat:pNumber="52" pat:id="p-52">The user can view the Restore Log at any time, as follows. The user can close or minimize the System application. The user can open the file browser and find the Health <pat:BoundaryData><pat:HeaderText>Page 8 <pat:OCRConfidenceData pat:levelNumber='88'>of</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='88'>28</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='8'?><pat:PatentImage pat:id='ID-00009' pat:imageContentCategory='Graph' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11146897.09-30-2014.I0PZ71LTPXXIFW3.SPEC_30040678.1.300.307.852.414.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.357</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.84</com:WidthMeasure><com:ALTText>Graph</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="53" pat:id="p-53">Management System folder. This is the folder where the application was installed. FIG. </pat:P><pat:P pat:pNumber="54" pat:id="p-54">181 illustrates a File Browser: Restore Log. The user can highlight the file named Restore<pat:OCRConfidenceData pat:levelNumber='56'>l[</pat:OCRConfidenceData> ]]<pat:OCRConfidenceData pat:levelNumber='5'>l</pat:OCRConfidenceData>og and click Open to view the log. </pat:P><pat:P pat:pNumber="55" pat:id="p-55">Please replace the <pat:PartName pat:idref='PN-00050'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00050'>63</pat:PartNumber>, <pat:PartName pat:idref='PN-00051'>line</pat:PartName> <pat:PartNumber pat:id='PN-00051'>28</pat:PartNumber>, of the application as filed with the following replacement paragraph: </pat:P><pat:P pat:pNumber="56" pat:id="p-56">United States published <pat:OCRConfidenceData pat:levelNumber='555222551226512866'>app.c-atien-no-App</pat:OCRConfidenceData>lication Nos. 2001/0011224, 2003/0163351, now U.S. Patent No. 8<pat:OCRConfidenceData pat:levelNumber='5'>,</pat:OCRConfidenceData>626<pat:OCRConfidenceData pat:levelNumber='5'>,</pat:OCRConfidenceData>521<pat:OCRConfidenceData pat:levelNumber='6'>,</pat:OCRConfidenceData> and 2003/0069753<pat:OCRConfidenceData pat:levelNumber='5'>,</pat:OCRConfidenceData> now U.S. Patent No. 7<pat:OCRConfidenceData pat:levelNumber='5'>,</pat:OCRConfidenceData>970<pat:OCRConfidenceData pat:levelNumber='5'>,</pat:OCRConfidenceData>620; </pat:P><pat:P pat:pNumber="57" pat:id="p-57">Please replace the <pat:PartName pat:idref='PN-00052'>paragraph beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00052'>64</pat:PartNumber>, <pat:PartName pat:idref='PN-00053'>line</pat:PartName> <pat:PartNumber pat:id='PN-00053'>1</pat:PartNumber>, of the application as filed with the following replacement paragraph: </pat:P><pat:P pat:pNumber="58" pat:id="p-58">United States <pat:OCRConfidenceData pat:levelNumber='666686'>patent</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='6555665585'>appcations</pat:OCRConfidenceData>Patent A<pat:OCRConfidenceData pat:levelNumber='66'>pp</pat:OCRConfidenceData>lication Nos. <pat:PartName pat:idref='PN-00054'>60/577</pat:PartName>,<pat:PartNumber pat:id='PN-00054'>064</pat:PartNumber> and <pat:PartName pat:idref='PN-00055'>10/112</pat:PartName>,<pat:PartNumber pat:id='PN-00055'>671</pat:PartNumber><pat:OCRConfidenceData pat:levelNumber='5'>,</pat:OCRConfidenceData> now U.S. Patent No. 7<pat:OCRConfidenceData pat:levelNumber='5'>,</pat:OCRConfidenceData>041<pat:OCRConfidenceData pat:levelNumber='5'>,</pat:OCRConfidenceData>468; and <pat:BoundaryData><pat:HeaderText>Page 9 <pat:OCRConfidenceData pat:levelNumber='88'>of</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='88'>28</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData></pat:P></pat:Specification></pat:SpecificationDocument>
prior_art/11153123.xml ADDED
@@ -0,0 +1,37 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11153123</doc-number>
8
+ <date>2009-12-31</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <p id="p-1" num="1">Attorney's Docket No.: 16113-0012001 </p>
14
+ <heading id="h-1">IN THE UNITED STATES PATENT AND TRADEMARK OFFICE</heading>
15
+ <p id="p-2" num="2">Applicant <confidence value="6">:</confidence>
16
+ Schirripa et al. Art Unit <confidence value="6">:</confidence>
17
+ 2161 Serial No. <confidence value="6">:</confidence>
18
+ 11/153,123 Examiner <confidence value="6">:</confidence>
19
+ Monica M. Pyo Filed <confidence value="6">:</confidence>
20
+ June <part-num-ref name="Serial No. : 11/153,123 Examiner : Monica M. Pyo Filed : June">15,</part-num-ref>
21
+ <part-num-ref name="Serial No. : 11/153,123 Examiner : Monica M. Pyo Filed : June 15,">2005</part-num-ref>
22
+ Con<confidence value="66">f.</confidence>
23
+ No. <confidence value="6">:</confidence>
24
+ <part-num-ref name="Conf. No. :">8457</part-num-ref>
25
+ Title <confidence value="6">:</confidence>
26
+ ELECTRONIC CONTENT CLASSIFICATION Mail Stop Amendment Commissioner for Patents P.O. Box <part-num-ref name="Title : ELECTRONIC CONTENT CLASSIFICATION Mail Stop Amendment Commissioner for Patents P.O. Box">1450</part-num-ref>
27
+ Alexandria, VA 22313-1450 AMENDMENT IN REPLY TO ACTION OF AUGUST <part-num-ref name="Alexandria, VA 22313-1450 AMENDMENT IN REPLY TO ACTION OF AUGUST">4,</part-num-ref>
28
+ <part-num-ref name="Alexandria, VA 22313-1450 AMENDMENT IN REPLY TO ACTION OF AUGUST 4,">2009</part-num-ref>
29
+ Please amend the above-identified application as follows: </p>
30
+ <heading id="h-2">CERTIFICATE OF MAILING BY EFS-WEB FILING</heading>
31
+ <p id="p-3" num="3">I hereby certif<confidence value="8">y</confidence>
32
+ that this paper was filed with the Patent and Trademark Office using the EFS-WEB system on this date: December <part-num-ref name="EFS-WEB system on this date: December">31,</part-num-ref>
33
+ <part-num-ref name="EFS-WEB system on this date: December 31,">2009</part-num-ref>
34
+ </p>
35
+ </description>
36
+ </us-patent-application>
37
+
prior_art/11163737.xml ADDED
@@ -0,0 +1,16 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <pat:SpecificationDocument xmlns:pat="urn:us:gov:doc:uspto:patent" xmlns="urn:us:gov:doc:uspto:patent" xmlns:ent="urn:us:gov:doc:uspto:enterprise" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:tbl="http://www.oasis-open.org/tables/exchange/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:com="http://www.wipo.int/standards/XMLSchema/Common/1" pat:instanceFileName="11163737.06-12-2014.HWCJ1D27PXXIFW3.SPEC.xml" pat:id="HWCJ1D27PXXIFW3" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XMLSchema/V1_3/SpecificationDocument_1_0.xsd">
3
+ <pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001">
4
+ <pat:ApplicationHeaderDetails><pat:ApplicationNumber>11163737</pat:ApplicationNumber></pat:ApplicationHeaderDetails>
5
+ <pat:PageTotalQuantity>1</pat:PageTotalQuantity>
6
+ <pat:ParagraphTotalQuantity>4</pat:ParagraphTotalQuantity>
7
+ </pat:DocumentHeaderDetails>
8
+ <pat:MailRoomDate>2014-06-12</pat:MailRoomDate>
9
+ <pat:Specification pat:id="Specification">
10
+ <?PageStart number="1"?>
11
+ <pat:P pat:id="p-1" pat:pNumber="1">App<pat:OCRConfidenceData pat:levelNumber="5">l</pat:OCRConfidenceData> No.:12/363,367 <pat:OCRConfidenceData pat:levelNumber="86">Am</pat:OCRConfidenceData>dt Dated: June 12, 2014 Reply to Notice to File Corrected Application Papers dated May 15, 2014 <pat:PartName pat:idref="PN-00001">Page </pat:PartName><pat:PartNumber pat:id="PN-00001"><pat:OCRConfidenceData pat:levelNumber="8">2</pat:OCRConfidenceData></pat:PartNumber> <pat:PartName pat:idref="PN-00002"><pat:OCRConfidenceData pat:levelNumber="68">of</pat:OCRConfidenceData> </pat:PartName><pat:PartNumber pat:id="PN-00002"><pat:OCRConfidenceData pat:levelNumber="8">3</pat:OCRConfidenceData></pat:PartNumber></pat:P>
12
+ <pat:Heading pat:id="h-1">AMENDMENTS TO THE SPECIFICATION</pat:Heading>
13
+ <pat:P pat:id="p-2" pat:pNumber="2">Please add the following paragraph [16] with the following amended paragraph:</pat:P>
14
+ <pat:P pat:id="p-3" pat:pNumber="3">[Para 16] Figures 4413-15 are flowcharts illustrating embodiments of processes used to assess the risk and impact of changes as part of a change management process used in a system according to example embodiments of the invention.</pat:P>
15
+ <pat:P pat:id="p-4" pat:pNumber="4">CHAR2\<pat:OCRConfidenceData pat:levelNumber="4">1</pat:OCRConfidenceData>601556v<pat:OCRConfidenceData pat:levelNumber="4">1</pat:OCRConfidenceData></pat:P>
16
+ </pat:Specification></pat:SpecificationDocument>
prior_art/11184301.xml ADDED
@@ -0,0 +1,42 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11184301</doc-number>
8
+ <date>2008-04-24</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <p id="p-1" num="1">Application No. 11/184,301 Attorney Docket No. 50277-2749 Filed July 18, 2005 </p>
14
+ <heading id="h-1">AMENDMENTS TO THE SPECIFICATION</heading>
15
+ <p id="p-2" num="2">Please amend the following paragraphs of the specification as indicated:</p>
16
+ <p id="p-3" num="3">[0044] Path table 202 includes columns R<confidence value="5">I</confidence>
17
+ D, PATHID<confidence value="5">,</confidence>
18
+ HK VALUE, LOCATOR, and VALUE. Each row in path table <part-num-ref name="includes columns RID, PATHID, HK VALUE, LOCATOR, and VALUE. Each row in path table">202</part-num-ref>
19
+ corresponds to a node within node tree <part-num-ref name="node within node tree">250.</part-num-ref>
20
+ Rows ra, rb, rc and rd correspond to nodes a, b, c and d, respectively. </p>
21
+ <p id="p-4" num="4">[0045] Column O<confidence value="5756685">RDER-KE</confidence>
22
+ YHK VALUE holds hierarchy-order key values, which are values that identify a node<confidence value="8">'</confidence>
23
+ s hierarchical level within a node tree representing an XML document and that identify the order of the node among the nodes at the same hierarchical level. </p>
24
+ <p id="p-5" num="5">[0062] Accordingly, the first entry of ReversePath contains as a reverse pathid and OrderKey-index reference the values <confidence value="5222">'a,'</confidence>
25
+ <confidence value="2222222">-'-1-'-</confidence>
26
+ (representing the first entry in OrderKey), respectively; the second entry contains <confidence value="55">'@</confidence>
27
+ <confidence value="6888662">c/a/','</confidence>
28
+ and <confidence value="686">'2'</confidence>
29
+ , respectively; the third entry contains <confidence value="5">'</confidence>
30
+ b/a<confidence value="662">/''</confidence>
31
+ <confidence value="42244">@c-ia</confidence>
32
+ and <confidence value="686">'3'</confidence>
33
+ , respectively; and the fourth entry contains <confidence value="5">'</confidence>
34
+ d/a<confidence value="66">/'</confidence>
35
+ and <confidence value="686">'4'</confidence>
36
+ , respectively. </p>
37
+ <p id="p-6" num="6">
38
+ <confidence value="86">OI</confidence>
39
+ D-2005-039-01 2 </p>
40
+ </description>
41
+ </us-patent-application>
42
+
prior_art/11198620.xml ADDED
The diff for this file is too large to render. See raw diff
 
prior_art/11200898.xml ADDED
@@ -0,0 +1,579 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11200898</doc-number>
8
+ <date>2005-08-10</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <heading id="h-1">TITLE OF THE INVENTION</heading>
14
+ <p id="p-1" num="1">Methods for Providing Neuroprotection for The Animal Central Nervous System Against The Effects Of <confidence value="7">i</confidence>
15
+ schemia, Neurodegeneration, Trauma, and Metal Poisoning. </p>
16
+ <heading id="h-2">CROSS-REFERENCE TO RELATED APPLICATIONS</heading>
17
+ <p id="p-2" num="2">This is a non-provisional application claiming the benefit of and priority to United States provisional patent application number 60/601547 filed August <part-num-ref name="benefit of and priority to United States provisional patent application number 60/601547 filed August">13,</part-num-ref>
18
+ <part-num-ref name="benefit of and priority to United States provisional patent application number 60/601547 filed August 13,">2004,</part-num-ref>
19
+ which is incorporated by reference. </p>
20
+ <heading id="h-3">INVENTORS</heading>
21
+ <p id="p-3" num="3">William H. Frey <confidence value="55">II</confidence>
22
+ , a citizen of the United States, residing at <part-num-ref name="United States, residing at">4800</part-num-ref>
23
+ Centerville Road, Apt. </p>
24
+ <p id="p-4" num="4">216, White Bear Lake, Minnesota 55127 Samual Scott Panter, a citizen of the United States, residing at <part-num-ref name="United States, residing at">2362</part-num-ref>
25
+ Greenwich St., San Francisco, California <part-num-ref name="Greenwich St., San Francisco, California">94123</part-num-ref>
26
+ Leah Ranae Bresin Hanson, a citizen of the United States, residing at <part-num-ref name="United States, residing at">300</part-num-ref>
27
+ Lady Slipper Lane, Vadnais Heights, Minnesota <part-num-ref name="Lady Slipper Lane, Vadnais Heights, Minnesota">55127</part-num-ref>
28
+ </p>
29
+ <heading id="h-4">BACKGROUND OF THE INVENTION</heading>
30
+ <p id="p-5" num="5">[001] Field of the Invention [002] The present invention is directed to methods for preconditioning and/or providing neuroprotection to the animal central nervous system against ischemia, neurodegeneration, trauma and metal poisoning, including associated cognitive, behavioral and physical impairments.</p>
31
+ <p id="p-6" num="6">[003] Description of the Related Art [004] Certain medical procedures, for example coronary artery bypass graft (CABG) surgery, are associated with neurological complications. In the case of CABG, the surgery is performed on more than 800,000 patients worldwide each year. Many of the CABG procedures performed are associated with neurological complications.</p>
32
+ <p id="p-7" num="7">These complications range from stroke in up to 16% of the patients to general cognitive decline with 50% of patients having impairment post-surgery and with progressive <boundary-data type="header">
33
+ <confidence value="888">-1-</confidence>
34
+ </boundary-data>
35
+ <boundary-data type="header">Attorney Docket No. 1871.2-<confidence value="66866">US-U1</confidence>
36
+ </boundary-data>
37
+ <page-break num="2"/>
38
+ decline occurring in some patients over the next five years. In addition, physical and behavioral impairment manifest in some CABG patients. Newman MF et al., N. Eng. J. </p>
39
+ <p id="p-8" num="8">Med. 344:395-402 (2001); Brillman J., Neurol. Clin. 11:475-495 (1993); and Selnes, O.A., Ann. Thorac. Surg. 67:1669-1676 (1999) are instructive.</p>
40
+ <p id="p-9" num="9">[005] Originally, it was hypothesized that the neurological complications associated with CABG surgery were either procedure or patient-related. The procedure generally implicated as potentially harmful was cardiopulmonary bypass using a pump and oxygenator. However, a recent study reports no difference in cognitive outcome between groups of patients undergoing CABG surgery performed with, or without, the pump and oxygenator. Such results suggest that the neurological impairments following CABG surgery may, in fact, be patient-related and, as a result, amenable to therapeutic manipulation.</p>
41
+ <p id="p-10" num="10">[006] In addition, patients at risk for, or diagnosed with disorders involving neurological impairments, e.g., Alzheimer's disease, Parkinson's disease, stroke, traumatic brain injury, spinal cord injury may benefit from similar therapeutic manipulation. See Crapper McLachlan, D.R., Dalton, A.J., Kruck, T.P.A., Bell, M.Y., Smith, W.L., Kalow, W., and Andrews, D.F. Intramuscular desferrioxamine in patients with Alzheimer's disease. The Lancet 337:1304-1308, <part-num-ref name="Lancet 337:1304-1308,">1991.</part-num-ref>
42
+ </p>
43
+ <p id="p-11" num="11">[007] A number of neurodegenerative disorders are known to have metal-associated pathology, i.e., resulting at least in part from metal poisoning, and may benefit from the therapeutic manipulation contemplated by embodiments of the present invention.</p>
44
+ <p id="p-12" num="12">These include AD, PD, Creutzfeldt-Jakob disease, familial amyotrophic lateral sclerosis, lewy-body dementia, carotid atherosclerosis, tardive dyskinesia, multiple sclerosis, Wilson's disease, progressive supranuclear palsy, Hallervorden-Spatz syndrome, multisystem atrophy, Huntington's disease, familial basal ganglia degeneration, Down's syndrome, cataracts, haemochromatosis, cerebral haemorrhage and head injury. See P.M. Doraiswamy and A.E. Finefrock, Metals in our minds: therapeutic implications for neurodegenerative disorders, The Lancet Neurology, Vol. <part-num-ref name="Lancet Neurology, Vol.">3,</part-num-ref>
45
+ July <part-num-ref name="Lancet Neurology, Vol. 3, July">2004.</part-num-ref>
46
+ </p>
47
+ <p id="p-13" num="13">[008] In general, ischemic conditions activate a number of genes that are important in the cellular and tissue adaptation to low oxygen conditions. These genes include <boundary-data type="header">
48
+ <confidence value="888">-2-</confidence>
49
+ </boundary-data>
50
+ <boundary-data type="header">Atto<confidence value="66">rn</confidence>
51
+ ey Docket No. 1871.2-US-U<confidence value="5">1</confidence>
52
+ </boundary-data>
53
+ <page-break num="3"/>
54
+ erythropoietin, glucose transporters, glycolytic enzymes, and the vascular endothelial growth factor (VEGF). VEGF is a major angiogenic factor that has been shown to activate new blood vessel formation. Transcriptional up-regulation has been shown to be implicated in the induction of the VEGF gene, an action mediated by the specific binding of the hypoxia-inducible factor-<confidence value="5">1</confidence>
55
+ (HIF-1) to the hypoxic response element </p>
56
+ <heading id="h-5">
57
+ <confidence value="88">(H</confidence>
58
+ RE). </heading>
59
+ <p id="p-14" num="14">[009] The HIF-1 transcription factor is a heterodimer composed of HIF-1<confidence value="5">a</confidence>
60
+ and HIF-1<confidence value="4">3</confidence>
61
+ and regulates the adaptive response to hypoxia in animal cells. HIF-<confidence value="66">1a</confidence>
62
+ accumulates under hypoxic conditions, but is virtually undetectable in normal oxygen conditions. HIF- <part-num-ref name="adaptive response to hypoxia in animal cells. HIF-1a accumulates under hypoxic conditions, but is virtually undetectable in normal oxygen conditions. HIF-">
63
+ <confidence value="8">1</confidence>
64
+ </part-num-ref>
65
+ <confidence value="2">p</confidence>
66
+ , on the other hand, is readily found in all cells. The HIF-1 heterodimer is believed to be neuroprotective against ischemia through the activation of EPO and VEGF. </p>
67
+ <p id="p-15" num="15">[010] HIF-<confidence value="5">1</confidence>
68
+ a has been shown in vitro to be activated by metal chelators, including both iron and copper chelating agents. A particular example of such an agent is deferoxamine (DFO),a hexadentate iron chelator, with kinetics similar to those associated with hypoxia, resulting in increased expression of HIF-<confidence value="5">1</confidence>
69
+ target genes, including EPO and VEGF. DFO is also known to stabilize HIF-<confidence value="5">1</confidence>
70
+ subunits, possibly by chelating and inactivating the iron that plays a role in targeting the subunit for proeolytic degradation under normoxic conditions. </p>
71
+ <p id="p-16" num="16">[011] <confidence value="5">I</confidence>
72
+ n vivo studies have demonstrated that DFO induces HIF-<confidence value="66">1a</confidence>
73
+ in neonatal and adult rats, injecting the chelator either subcutaneously (s.c.) or intraperitoneally (i.p.), typically in very high dosage. In addition, studies indicate that the following substances stimulate and/or stabilize HIF-<confidence value="66">1a</confidence>
74
+ : insulin, IGF-<confidence value="4">l</confidence>
75
+ , heregulin insulin, heregulin, TGFbeta, <confidence value="885">IL-</confidence>
76
+ beta, TNFalpha, cobalt, pyruvate, oxalacetate and lactate. </p>
77
+ <p id="p-17" num="17">[012] Problems exist, however, with the administration of DFO intravenously. DFO is not generally injected intravenously for at least two reasons. First, it is a small molecule and, as a result, is eliminated rapidly through the kidney. The typical plasma half-life in humans is less than <part-num-ref name="typical plasma half-life in humans is less than">10</part-num-ref>
78
+ minutes. Second, the injection of an intravenous bolus of DFO causes acute hypotension that is rapid, may lead to shock and may be lethal. These characteristics have limited the utility of <confidence value="5">D</confidence>
79
+ FO in particular as a neuroprotective agent. </p>
80
+ <boundary-data type="header">
81
+ <confidence value="888">-3-</confidence>
82
+ </boundary-data>
83
+ <boundary-data type="header">Atto<confidence value="66">rn</confidence>
84
+ ey Docket No. 1871.2-US-U<confidence value="5">1</confidence>
85
+ </boundary-data>
86
+ <p id="p-18" num="18">
87
+ <page-break num="4"/>
88
+ [013] One published study administered <confidence value="5">D</confidence>
89
+ FO intranasally to iron overloaded patients. </p>
90
+ <p id="p-19" num="19">G.S. Gordon et al., Intranasal Administration of Deferoxamine to Iron Overloaded Patients, (1989) Am. J. Med. Sci. 297(5):280-284. In this particular study, DFO was administered to the patients as a nasal spray in a volume of <part-num-ref name="volume of">75</part-num-ref>
91
+ microliters per spray. </p>
92
+ <p id="p-20" num="20">Significantly, such sprays are known to deposit the drug or other substance in the lower third of the nasal cavity. This is verified by patient observations stating that a bad taste in the mouth was resulting from the drug passing through the nasopharynx and into the mouth. As a result, this study did not involve delivering the drug to the upper third of the nasal cavity. Thus, the drug would not have reached the olfactory epithelium or the olfactory nerves. As a result, delivery of the drug to the CNS would be less than optimal.</p>
93
+ <p id="p-21" num="21">[014] It is recognized that intranasal delivery to the CNS may occur along both the olfactory and trigeminal nerve pathways. See Thorne, RG (2004), Delivery of Insulin- Like Growth Factor-I to the Rat Brain and Spinal Cord Along Olfactory and Trigeminal Pathways Following Intranasal Administration, Neuroscience, Vol. <part-num-ref name="Rat Brain and Spinal Cord Along Olfactory and Trigeminal Pathways Following Intranasal Administration, Neuroscience, Vol.">127,</part-num-ref>
94
+ pp. 481-496. </p>
95
+ <p id="p-22" num="22">Optimal delivery taking advantage of both pathways is accomplished by administering the substance in the upper third of the nasal cavity.</p>
96
+ <p id="p-23" num="23">[015] Regarding Alzheimer's disease, some studies indicate that cerebral vascular problems occur first, followed by neurodegeneration in later stages of the disease. For example, see The Lancet Neurology, vol. <part-num-ref name="Lancet Neurology, vol.">3,</part-num-ref>
97
+ page 184-190, Jack C. de <confidence value="5">l</confidence>
98
+ a Torre (March, 2004). Thus, it may be possible to prevent, mitigate or treat the effects of Alzheimer's disease at the appropriate disease stage through therapeutic manipulation targeted toward mitigation or prevention of cerebral ischemia or neurodegeneration. </p>
99
+ <p id="p-24" num="24">[016] In a published patent application, U.S. Pat. App. No. <part-num-ref name="published patent application, U.S. Pat. App. No.">20020028786</part-num-ref>
100
+ by William H. </p>
101
+ <p id="p-25" num="25">Frey <confidence value="55">II</confidence>
102
+ (also a co-inventor of the present application) entitled METHODS AND </p>
103
+ <heading id="h-6">COMPOSITIONS FOR ENHANCING CELLULAR FUNCTION THROUGH</heading>
104
+ <p id="p-26" num="26">PROTECTION OF TISSUE COMPONENTS, various substances are discussed that may be administered intranasally to treat various diseases and conditions. The entire contents of this reference are hereby incorporated by reference.</p>
105
+ <boundary-data type="header">
106
+ <confidence value="888">-4-</confidence>
107
+ </boundary-data>
108
+ <boundary-data type="header">Atto<confidence value="66">rn</confidence>
109
+ ey Docket No. 1871.2-US-U<confidence value="5">1</confidence>
110
+ </boundary-data>
111
+ <heading id="h-7">BRIEF SUMMARY OF THE INVENTION</heading>
112
+ <p id="p-27" num="27">
113
+ <page-break num="5"/>
114
+ [017] Given the situation described above there is a need for a method for efficiently and safely conditioning, or preconditioning, the animal CNS to prevent or minimize cognitive, behavioral and physical impairment due to ischemia, neurodegeneration, CNS trauma and free radical damage from copper, zinc and iron. In addition, there is a need for a method for efficiently and safely conditioning and treating the animal CNS to treat existing cognitive, behavioral and physical impairment due to ischemia, neurodegeneration, CNS trauma and free radical damage from copper and iron. </p>
115
+ <p id="p-28" num="28">Further, there is a need to optimize the administration or delivery of a therapeutic agent.</p>
116
+ <p id="p-29" num="29">[018] Methods and pharmaceutical compositions for preconditioning the <confidence value="5">C</confidence>
117
+ NS to neuroprotect against, minimize and/or prevent the effects of ischemia and the cognitive, behavioral and physical impairments that often accompany ischemic episodes by stimulating and stabilizing hypoxia-inducible factor-<confidence value="5">1</confidence>
118
+ a (HIF-<confidence value="54">1a</confidence>
119
+ ) are provided herein. </p>
120
+ <p id="p-30" num="30">
121
+ <confidence value="8">H</confidence>
122
+ IF-<confidence value="5">1</confidence>
123
+ a is known to provide a neuroprotective benefit under ischemic conditions. </p>
124
+ <p id="p-31" num="31">Patients at risk for certain diseases or disorders that carry a concomitant risk for <confidence value="8">i</confidence>
125
+ schemia may benefit, e.g., those at risk for Alzheimer's disease, Parkinson's disease or stroke. Patients undergoing certain medical procedures that may result in ischemia may also benefit. </p>
126
+ <p id="p-32" num="32">[019] In addition, methods and compounds for treating patients that have undergone an ischemic episode to minimize the effects of the ischemia.</p>
127
+ <p id="p-33" num="33">[020] Initially, under a representative embodiment of the invention, the possibility of an ischemic episode or neurodegeneration is recognized. Intranasal therapeutic agent is administered to the upper third of the nasal cavity to bypass the blood-brain barrier and access the central nervous system directly to avoid unwanted and potentially damaging side effects. Therapeutic agents include those substances that may interact with iron and/or copper such as iron chelators, copper chelators, and/or antioxidants and free radical scavengers. A particular example of such therapeutic agents is the iron chelator deferoxamine (DFO). DFO may also chelate copper as well as other metals. Intranasal administration of DFO is known to stimulate and/or stabilize HIF-<confidence value="5">1</confidence>
128
+ a and provides an efficient and safe method for pre-conditioning the <confidence value="5">C</confidence>
129
+ NS to protect against cerebral <boundary-data type="header">
130
+ <confidence value="888">-5-</confidence>
131
+ </boundary-data>
132
+ <boundary-data type="header">Atto<confidence value="66">rn</confidence>
133
+ ey Docket No. 1871.2-<confidence value="58866">US-U1</confidence>
134
+ </boundary-data>
135
+ <page-break num="6"/>
136
+ ischemia. The effects of pretreating a patient, who ultimately experiences ischemia, include significant reduction of infarct volume as well as a significant decrease in weight loss following stroke. </p>
137
+ <p id="p-34" num="34">[021] Another embodiment of the invention provides a method and pharmaceutical compositions for treating a patient that has undergone an ischemic episode by administering at least one does of a therapeutic agent via intranasal delivery to the upper one-third of the nasal cavity. As discussed above in connection with pretreatment, metal chelators, e.g., DFO, may be used to treat a patient post-stroke.</p>
138
+ <p id="p-35" num="35">The effects of post-stroke intranasal administration of such a therapeutic agent include significant reduction of infarct volume as well as a significant decrease in weight loss following stroke.</p>
139
+ <p id="p-36" num="36">[022] Thus, one embodiment of the invention relates to a method and pharmaceutical compositions for preventing, minimizing and/or treating neurologic complications due to cerebral ischemia as a result of certain medical procedures. The method comprises administering at least one dose of a therapeutic agent via intranasal delivery to the upper one-third of the nasal cavity prior to undergoing a medical procedure that may result in neurologic complications.</p>
140
+ <p id="p-37" num="37">[023] Another embodiment of the invention relates to a method and pharmaceutical compositions for preventing, minimizing and/or treating neurologic complications due to cerebral ischemia or neural degeneration as a result of certain medical procedures.</p>
141
+ <p id="p-38" num="38">The method comprises administering at least one dose of at least one therapeutic agent via intranasal delivery to the upper one-third of the nasal cavity during, prior to and/or after undergoing a medical procedure that may result in neurologic complications. The particular therapeutic agent(s) selected may preferentially chelate iron or copper or a combination of the iron and copper, or otherwise interact with select metals or prevent oxidation/reduction cycling of iron or copper.</p>
142
+ <p id="p-39" num="39">[024] Yet another embodiment of the invention relates to a method and pharmaceutical compositions for decreasing weight loss encountered by patients having cerebral ischemic episode.</p>
143
+ <boundary-data type="header">
144
+ <confidence value="888">-6-</confidence>
145
+ </boundary-data>
146
+ <boundary-data type="header">Atto<confidence value="66">rn</confidence>
147
+ ey Docket No. 1871.2-<confidence value="58868">US-U1</confidence>
148
+ </boundary-data>
149
+ <p id="p-40" num="40">
150
+ <page-break num="7"/>
151
+ [025] Another embodiment of the invention relates to a method and pharmaceutical compositions for preventing, minimizing and/or treating neurologic complications due to cerebral ischemia and/or neurodegeneration for patients at risk for, or diagnosed with<confidence value="5">,</confidence>
152
+ certain medical conditions such as Alzheimer's disease, Parkinson's disease, Creutzfeldt-Jakob disease, familial amyotrophic lateral sclerosis, lewy-body dementia, carotid atherosclerosis, tardive dyskinesia, multiple sclerosis, Wilson's disease, progressive supranuclear palsy, Hallervorden-Spatz syndrome, multisystem atrophy, Huntington's disease, familial basal ganglia degeneration, Down's syndrome, cataracts, haemochromatosis, cerebral hemorrhage, subarachnoic hemorrhage, head injury, and spinal cord injury. </p>
153
+ <p id="p-41" num="41">[026] The figures and the detailed description which follow more particularly exemplify these and other embodiments of the invention.</p>
154
+ <p id="p-42" num="42">[027] BRIEF DESCRIPTION OF THE DRAWINGS [028] The invention may be more completely understood in consideration of the following detailed description of various embodiments of the invention in connection with the accompanying drawings, which are as follows.</p>
155
+ <p id="p-43" num="43">[029] Figure 1 is a bar graph illustrating pre-stroke treatment with intranasal administration of three doses of 10% DFO and its effect on infarct volume.</p>
156
+ <p id="p-44" num="44">[030] Figure 2 is a bar graph illustrating pre-stroke treatment with intranasal administration of one dose of 10% DFO and its effect on infarct volume.</p>
157
+ <p id="p-45" num="45">[031] Figure 3 is a bar graph illustrating pre-stroke treatment with intranasal administration of three doses of 3% DFO and its effect on infarct volume.</p>
158
+ <p id="p-46" num="46">[032] Figure 4 is a bar graph illustrating post-stroke treatment with intranasal administration of six doses of 10% DFO and its effect on infarct volume.</p>
159
+ <p id="p-47" num="47">[033] Figure 5 is a bar graph illustrating pre-stroke treatment with intranasal administration of one dose of 10% DFO and its effect on weight loss post-stroke.</p>
160
+ <p id="p-48" num="48">[034] Figure 6 is a bar graph illustrating pre-stroke treatment with intranasal administration of three doses of 3% DFO and its effect on weight loss post-stroke.</p>
161
+ <boundary-data type="header">
162
+ <confidence value="888">-7-</confidence>
163
+ </boundary-data>
164
+ <boundary-data type="header">Atto<confidence value="66">rn</confidence>
165
+ ey Docket No. 1871.2-US-U<confidence value="5">1</confidence>
166
+ </boundary-data>
167
+ <p id="p-49" num="49">
168
+ <page-break num="8"/>
169
+ [035] Figure 7 is a bar graph illustrating pre-stroke treatment with intranasal administration of three doses of 10% DFO and its effect on weight loss post-stroke. </p>
170
+ <p id="p-50" num="50">[036] Figure 8 is a bar graph illustrating post-stroke treatment with intranasal administration of six doses of 10% DFO and its effect on weight loss post-stroke.</p>
171
+ <heading id="h-8">DETAILED DESCRIPTION OF THE INVENTION, INCLUDING THE BEST MODE</heading>
172
+ <p id="p-51" num="51">[037] While the invention is amenable to various modifications and alternative forms, specifics thereof are shown by way of example in the drawings and described in detail herein. It should be understood, however, that the intention is not to limit the invention to the particular embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.</p>
173
+ <p id="p-52" num="52">[038] Definitions [039] As used herein, "central nervous system" (CNS) refers to the brain and spinal cord and associated tissues.</p>
174
+ <p id="p-53" num="53">[040] An "effective amount" of agent is an amount sufficient to prevent, treat, reduce and/or ameliorate the symptoms, neuronal damage and/or underlying causes of any of the referenced disorders or diseases. In some instances, an "effective amount" is sufficient to eliminate the symptoms of those diseases and overcome the disease itself.</p>
175
+ <p id="p-54" num="54">[041] In the context of the present invention, the terms "treat" and "therapy" and "therapeutic" and the like refer to alleviate, slow the progression, prophylaxis, attenuation or cure of ischemia, trauma, metal poisoning or neurodegeneration.</p>
176
+ <p id="p-55" num="55">[042] "Prevent", as used herein, refers to putting off, delaying, slowing, inhibiting, or otherwise stopping, reducing or ameliorating the onset of ischemia, trauma, metal poisoning or neurodegeneration. It is preferred that a large enough quantity of the agent be applied in non-toxic levels in order to provide an effective level of neuroprotection.</p>
177
+ <p id="p-56" num="56">The method of the present invention may be used with any animal, such as a mammal or a bird (avian), more preferably a mammal. Poultry are a preferred bird. Exemplary mammals include, but are not limited to rats, mice, cats, dogs, horses, cows, sheep, pigs, and more preferably humans.</p>
178
+ <boundary-data type="header">
179
+ <confidence value="888">-8-</confidence>
180
+ </boundary-data>
181
+ <boundary-data type="header">Attorney Docket No. 1871.2-<confidence value="58868">US-U1</confidence>
182
+ </boundary-data>
183
+ <p id="p-57" num="57">
184
+ <page-break num="9"/>
185
+ [043] Thus, methods and pharmaceutical compositions are described herein that, inter <confidence value="2222">alia</confidence>
186
+ , prevent, and/or treat neurologic complications such as cognitive, behavioral and/or physical impairment due to ischemia, neurodegeneration, trauma and metal poisoning. </p>
187
+ <p id="p-58" num="58">[044] An alternative to potentially lethal and generally ineffective intravenous injection of metal chelators, e.g., DFO, may be accomplished using an alternative non-invasive method to directly target the substance to the brain and thus the central nervous system (CNS). Intranasal delivery allows substances to be rapidly delivered to the central nervous system, even those that do not readily cross the blood-brain barrier by bypassing the blood-brain barrier and directly exposes the <confidence value="5">C</confidence>
188
+ NS to the delivered substance. In this manner, unwanted systemic side effects are reduced if not eliminated. </p>
189
+ <p id="p-59" num="59">[045] Since DFO, similar to other metal chelators, has a strong Fe-I<confidence value="66">ll</confidence>
190
+ binding constant (10<confidence value="66">31</confidence>
191
+ ), it is rapidly eliminated from the blood and does not readily cross the blood-brain barrier. Thus, when metal chelator-based therapeutic agents are administered intravenously, orally or even intranasally--but not directly to the upper one-third of the nasal cavity--to target affected tissues within the brain, the therapeutic effect has been heretofore minimal. Delivery of intranasal DFO to the upper one-third of the nasal cavity has been assessed by administering <part-num-ref name="nasal cavity has been assessed by administering">6</part-num-ref>
192
+ mg DFO bound to <part-num-ref name="mg DFO bound to">6</part-num-ref>
193
+ <confidence value="5">p</confidence>
194
+ Ci of 59Fe (as 59FeC<confidence value="4">1</confidence>
195
+ 3) to rats under anesthesia. The IN dose in <part-num-ref name="IN dose in">60</part-num-ref>
196
+ <confidence value="2">p</confidence>
197
+ L was administered as <part-num-ref name="pL was administered as">6</part-num-ref>
198
+ <confidence value="25">pL</confidence>
199
+ drops over twenty minutes. Following delivery, tissues were removed for analysis. Using scintillation counting, labeled ferrioxamine was detected throughout the brain, with high concentrations detected in the olfactory bulbs, anterior olfactory nucleus, hypothalamus, frontal cortex and cervical spinal cord. Even higher ferrioxamine concentrations were observed in the trigeminal nerves and ventral dura. Peripheral tissues with the highest ferrioxamine concentrations included the olfactory epithelium, thyroid and cervical lymph nodes. By contrast, the blood concentrations of ferrioxamine, taken at <part-num-ref name="blood concentrations of ferrioxamine, taken at">5</part-num-ref>
200
+ minute intervals from dosing up to <part-num-ref name="minute intervals from dosing up to">25</part-num-ref>
201
+ minutes post-dose, are quite low, indicating a minimization of exposure of the therapeutic agent to non-target tissue. The data provided in Table <part-num-ref name="data provided in Table">1</part-num-ref>
202
+ below, thus illustrates that intranasal DFO, the concentrations having been calculated based on an extrapolation of the ferrioxamine concentration, <boundary-data type="header">
203
+ <confidence value="888">-9-</confidence>
204
+ </boundary-data>
205
+ <boundary-data type="header">Atto<confidence value="66">rn</confidence>
206
+ ey Docket No. 1871.2-<confidence value="58868">US-U1</confidence>
207
+ </boundary-data>
208
+ <page-break num="10"/>
209
+ administered to the upper one-third of the nasal cavity, is effectively delivered to the brain and upper spinal cord, with minimal systemic exposure. </p>
210
+ <p id="p-60" num="60">[046] Intranasal Delivery of DF<confidence value="5">O</confidence>
211
+ (uM concentrations in tissues @ 25 minutes after the onset of delivery) <confidence value="5">u</confidence>
212
+ L delivered <part-num-ref name="onset of delivery) uL delivered">62</part-num-ref>
213
+ <part-num-ref name="">65</part-num-ref>
214
+ <part-num-ref name="">60</part-num-ref>
215
+ <part-num-ref name="">60</part-num-ref>
216
+ <part-num-ref name="">64</part-num-ref>
217
+ <part-num-ref name="">62</part-num-ref>
218
+ <part-num-ref name="">62</part-num-ref>
219
+ <part-num-ref name="">62</part-num-ref>
220
+ <part-num-ref name="">66</part-num-ref>
221
+ <part-num-ref name="">61</part-num-ref>
222
+ <confidence value="588">uCi</confidence>
223
+ delivered 36.55 38.40 35.45 35.35 36.77 35.28 35.30 34.72 35.80 34.31 <confidence value="52">mg</confidence>
224
+ delivered 6.15 <confidence value="6666">6.44</confidence>
225
+ 5.95 5.95 6.29 6.05 6.05 6.07 6.45 6.00 <confidence value="2222">nmol</confidence>
226
+ delivered <confidence value="6">9</confidence>
227
+ ,361.73 9,801.65 <confidence value="5">9</confidence>
228
+ ,063.49 <confidence value="66666666">9,053.64</confidence>
229
+ 9,583.9<confidence value="5">7</confidence>
230
+ 9,218.26 <confidence value="5">9</confidence>
231
+ ,207.99 <confidence value="66666666">9,237.98</confidence>
232
+ <confidence value="6">9</confidence>
233
+ ,824.75 9,128.91 <confidence value="8">D</confidence>
234
+ rug Deliver<confidence value="4">y</confidence>
235
+ Time <part-num-ref name="uCi delivered 36.55 38.40 35.45 35.35 36.77 35.28 35.30 34.72 35.80 34.31 mg delivered 6.15 6.44 5.95 5.95 6.29 6.05 6.05 6.07 6.45 6.00 nmol delivered 9,361.73 9,801.65 9,063.49 9,053.64 9,583.97 9,218.26 9,207.99 9,237.98 9,824.75 9,128.91 Drug Delivery Time">21</part-num-ref>
236
+ <part-num-ref name="">21</part-num-ref>
237
+ <part-num-ref name="">20</part-num-ref>
238
+ <part-num-ref name="">18</part-num-ref>
239
+ <part-num-ref name="">20</part-num-ref>
240
+ <part-num-ref name="">22</part-num-ref>
241
+ <part-num-ref name="">20</part-num-ref>
242
+ <part-num-ref name="">20</part-num-ref>
243
+ <part-num-ref name="">20</part-num-ref>
244
+ <part-num-ref name="">18</part-num-ref>
245
+ <confidence value="8">T</confidence>
246
+ ime of Perfusion <part-num-ref name="Time of Perfusion">25</part-num-ref>
247
+ <part-num-ref name="">25</part-num-ref>
248
+ <part-num-ref name="">26</part-num-ref>
249
+ <part-num-ref name="">27</part-num-ref>
250
+ <part-num-ref name="">25</part-num-ref>
251
+ <part-num-ref name="">26</part-num-ref>
252
+ <part-num-ref name="">27</part-num-ref>
253
+ <part-num-ref name="">26</part-num-ref>
254
+ <part-num-ref name="">26</part-num-ref>
255
+ <part-num-ref name="">26</part-num-ref>
256
+ Rat weight <part-num-ref name="Rat weight">303</part-num-ref>
257
+ <part-num-ref name="">302</part-num-ref>
258
+ <part-num-ref name="">264</part-num-ref>
259
+ <part-num-ref name="">281</part-num-ref>
260
+ <part-num-ref name="">298</part-num-ref>
261
+ <part-num-ref name="">309</part-num-ref>
262
+ <part-num-ref name="">336</part-num-ref>
263
+ <part-num-ref name="">283</part-num-ref>
264
+ <part-num-ref name="">318</part-num-ref>
265
+ <part-num-ref name="">315</part-num-ref>
266
+ RAT# DF<confidence value="5">0</confidence>
267
+ 9 DF<confidence value="65">10</confidence>
268
+ <confidence value="6866">DF11</confidence>
269
+ DF<confidence value="5">1</confidence>
270
+ 2 DF<confidence value="5">1</confidence>
271
+ 3 DF<confidence value="5">1</confidence>
272
+ 4 DF<confidence value="5">1</confidence>
273
+ 5 DF<confidence value="5">1</confidence>
274
+ 8 DF<confidence value="5">1</confidence>
275
+ 9 DF2<confidence value="5">0</confidence>
276
+ Blood Sample <part-num-ref name="RAT# DF09 DF10 DF11 DF12 DF13 DF14 DF15 DF18 DF19 DF20 Blood Sample">1</part-num-ref>
277
+ <confidence value="5">(</confidence>
278
+ 5:00<confidence value="5">)</confidence>
279
+ 1.2 1.6 0.6 1.2 0.7 1.5 1.1 0.8 0.3 1.8 Blood Sample <part-num-ref name="(5:00) 1.2 1.6 0.6 1.2 0.7 1.5 1.1 0.8 0.3 1.8 Blood Sample">2</part-num-ref>
280
+ <confidence value="5">(</confidence>
281
+ 10:00<confidence value="5">)</confidence>
282
+ 1.1 2.1 1.1 <confidence value="666">1.2</confidence>
283
+ 1.2 <confidence value="666">1.8</confidence>
284
+ 1.7 1.0 0.4 1.9 Blood Sample <part-num-ref name="(10:00) 1.1 2.1 1.1 1.2 1.2 1.8 1.7 1.0 0.4 1.9 Blood Sample">3</part-num-ref>
285
+ <confidence value="5">(</confidence>
286
+ 15:00<confidence value="5">)</confidence>
287
+ 1.1 2.0 0.5 1.8 0.9 <confidence value="666">1.4</confidence>
288
+ 1.7 1.3 0.5 2.6 Blood Sample <part-num-ref name="(15:00) 1.1 2.0 0.5 1.8 0.9 1.4 1.7 1.3 0.5 2.6 Blood Sample">4</part-num-ref>
289
+ <confidence value="5">(</confidence>
290
+ 20:00<confidence value="5">)</confidence>
291
+ 1.1 1.8 0.3 1.9 1.1 <confidence value="666">1.6</confidence>
292
+ 1.5 1.1 0.4 <confidence value="666">2.9</confidence>
293
+ Blood Sample <part-num-ref name="(20:00) 1.1 1.8 0.3 1.9 1.1 1.6 1.5 1.1 0.4 2.9 Blood Sample">5</part-num-ref>
294
+ <confidence value="5">(</confidence>
295
+ 25:00<confidence value="5">)</confidence>
296
+ 1.8 1.6 1.8 1.3 1.5 2.2 1.7 1.3 0.5 2.1 Superficial Nodes <part-num-ref name="(25:00) 1.8 1.6 1.8 1.3 1.5 2.2 1.7 1.3 0.5 2.1 Superficial Nodes">
297
+ <confidence value="686">(4)</confidence>
298
+ </part-num-ref>
299
+ 3.4 0.9 0.6 0.9 2.2 0.6 1.8 0.6 1.1 0.8 <confidence value="8">C</confidence>
300
+ ervical Nodes <part-num-ref name="3.4 0.9 0.6 0.9 2.2 0.6 1.8 0.6 1.1 0.8 Cervical Nodes">
301
+ <confidence value="686">(2)</confidence>
302
+ </part-num-ref>
303
+ 12.9 10.9 34.2 <confidence value="6666">40.8</confidence>
304
+ 58.2 51.4 65.1 13.2 11.4 8.1 <confidence value="8">D</confidence>
305
+ orsal Dura 26.5 11.4 7.4 14.1 16.6 32.0 8.0 5.9 35.8 5.1 Ventral Dura 25.3 38.7 70.9 17.7 58.3 44.0 51.5 - 62.8 <confidence value="6666">11.6</confidence>
306
+ Tri<confidence value="7">g</confidence>
307
+ eminal Nerve 33.3 14.7 22.4 8.4 72.8 25.1 26.6 17.4 27.0 9.5 <confidence value="8">O</confidence>
308
+ lfactory Bulbs 12.7 10.6 30.0 14.7 20.5 13.1 <confidence value="6666">28.0</confidence>
309
+ 27.5 21.6 6.6 Anterior Olfactory Nucleus 4.4 4.2 - - 5.4 2.5 5.5 4.4 7.7 - Frontal <confidence value="5">C</confidence>
310
+ ortex 4.3 3.3 <confidence value="6666">13.6</confidence>
311
+ - 2.5 1.1 <confidence value="666">6.5</confidence>
312
+ 1.4 5<confidence value="5">.</confidence>
313
+ 0 - Caudate/Putamen 2.0 1.5 2.1 - 2.4 0.9 <confidence value="666">1.6</confidence>
314
+ 1.1 <confidence value="666">2.0</confidence>
315
+ <confidence value="8">-</confidence>
316
+ <confidence value="885">Sep</confidence>
317
+ tal Nucleus 2.6 1.6 1.6 - 3.2 1.9 2.0 1.8 <confidence value="666">2.9</confidence>
318
+ <confidence value="8">-</confidence>
319
+ <confidence value="8866">Hipp</confidence>
320
+ ocam<confidence value="4">p</confidence>
321
+ us 0.9 0.9 <confidence value="666">0.9</confidence>
322
+ - 2.3 1.2 1.2 0.5 1.3 - Parietal cortex 1.3 1.6 2.3 - 0.7 1.9 <confidence value="666">2.8</confidence>
323
+ 0.8 1.0 - Thalamus 1.1 1.2 1.2 - 1.5 1.0 1.0 0.8 <confidence value="666">1.2</confidence>
324
+ <confidence value="8">-</confidence>
325
+ <confidence value="666666666666">Hypothalamus</confidence>
326
+ 5.4 7.3 6.5 - 3.1 3.0 6.1 2.7 3.8 - <confidence value="66666666">Midbrain</confidence>
327
+ <confidence value="6">1</confidence>
328
+ .3 1<confidence value="66">.3</confidence>
329
+ 1.1 - 1.8 1.3 1.2 0.6 1.3 - <confidence value="5">P</confidence>
330
+ ons 2.0 1.5 1.4 - 1.5 2.0 2.6 0.7 2.4 - <confidence value="5">M</confidence>
331
+ edulla 1.1 2.3 1.2 - 1.7 2.2 3.0 1.0 2.0 - <confidence value="5">U</confidence>
332
+ pper Cervical Spinal <confidence value="5">C</confidence>
333
+ ord 2.1 1.4 3.7 1.5 3.9 <confidence value="666">6.8</confidence>
334
+ 7.3 1.4 4.6 4.6 <confidence value="8">C</confidence>
335
+ erebellum 0.8 <confidence value="666">0.9</confidence>
336
+ 0.6 - 0.9 1.4 1.1 0.5 1.1 - <confidence value="5">T</confidence>
337
+ hyroid 1125.4 2932.7 448.2 814.1 <confidence value="66666">466.7</confidence>
338
+ 1285.4 753.3 751.4 3463.9 605.9 <confidence value="8">O</confidence>
339
+ lfactory Epithelium 12016.8 11374.8 11191.7 13841.7 9519.2 10724.4 11764.8 9572.8 9321.0 12205.2 <confidence value="6">A</confidence>
340
+ xilla<confidence value="77">ry</confidence>
341
+ Nodes <part-num-ref name="12.9 10.9 34.2 40.8 58.2 51.4 65.1 13.2 11.4 8.1 Dorsal Dura 26.5 11.4 7.4 14.1 16.6 32.0 8.0 5.9 35.8 5.1 Ventral Dura 25.3 38.7 70.9 17.7 58.3 44.0 51.5 - 62.8 11.6 Trigeminal Nerve 33.3 14.7 22.4 8.4 72.8 25.1 26.6 17.4 27.0 9.5 Olfactory Bulbs 12.7 10.6 30.0 14.7 20.5 13.1 28.0 27.5 21.6 6.6 Anterior Olfactory Nucleus 4.4 4.2 - - 5.4 2.5 5.5 4.4 7.7 - Frontal Cortex 4.3 3.3 13.6 - 2.5 1.1 6.5 1.4 5.0 - Caudate/Putamen 2.0 1.5 2.1 - 2.4 0.9 1.6 1.1 2.0 - Septal Nucleus 2.6 1.6 1.6 - 3.2 1.9 2.0 1.8 2.9 - Hippocampus 0.9 0.9 0.9 - 2.3 1.2 1.2 0.5 1.3 - Parietal cortex 1.3 1.6 2.3 - 0.7 1.9 2.8 0.8 1.0 - Thalamus 1.1 1.2 1.2 - 1.5 1.0 1.0 0.8 1.2 - Hypothalamus 5.4 7.3 6.5 - 3.1 3.0 6.1 2.7 3.8 - Midbrain 1.3 1.3 1.1 - 1.8 1.3 1.2 0.6 1.3 - Pons 2.0 1.5 1.4 - 1.5 2.0 2.6 0.7 2.4 - Medulla 1.1 2.3 1.2 - 1.7 2.2 3.0 1.0 2.0 - Upper Cervical Spinal Cord 2.1 1.4 3.7 1.5 3.9 6.8 7.3 1.4 4.6 4.6 Cerebellum 0.8 0.9 0.6 - 0.9 1.4 1.1 0.5 1.1 - Thyroid 1125.4 2932.7 448.2 814.1 466.7 1285.4 753.3 751.4 3463.9 605.9 Olfactory Epithelium 12016.8 11374.8 11191.7 13841.7 9519.2 10724.4 11764.8 9572.8 9321.0 12205.2 Axillary Nodes">
342
+ <confidence value="686">(2)</confidence>
343
+ </part-num-ref>
344
+ 0.5 0.4 0.3 0.3 0.4 0.5 0.3 <confidence value="666">0.4</confidence>
345
+ 1.0 3.1 <confidence value="8">L</confidence>
346
+ iver 0.4 0.8 0.4 0.3 0.3 0.3 0.3 <confidence value="666">0.4</confidence>
347
+ 0.4 0.4 <confidence value="7">K</confidence>
348
+ idney 1.0 0.4 0.5 0.6 0.4 0.2 0.6 1.0 1.2 0.5 <confidence value="8">M</confidence>
349
+ uscle 0.4 0.3 0.3 0.4 0.4 0.2 0.6 0.6 0.7 0.4 <confidence value="8">H</confidence>
350
+ eart 0.4 0.4 0.5 1.6 0.6 0.3 2.2 <confidence value="666">0.2</confidence>
351
+ 0.2 0.5 <confidence value="8">L</confidence>
352
+ ung 0.6 1.4 0.7 - 1.0 0.5 2.2 1.5 1.1 0.5 <confidence value="8">L</confidence>
353
+ ower Cervical Spinal Cord 0.5 5.3 1.0 2.7 0.3 0.1 3.8 0.4 1.8 0.3 <confidence value="8">T</confidence>
354
+ horacic Spinal Cord 0.1 0.2 0.2 0.4 0.1 0.1 1.2 0.3 0.6 0.1 <confidence value="8">L</confidence>
355
+ umbar Spinal Cord 0.1 0.1 0.1 0.1 0.1 0.7 0.1 <confidence value="666">0.1</confidence>
356
+ 0.1 0.1 <confidence value="88">Sp</confidence>
357
+ inal Dura 1.9 3.3 1.3 <confidence value="666">4.2</confidence>
358
+ 1.1 2.3 - 0.4 1.5 0.8 TABLE <part-num-ref name="0.5 0.4 0.3 0.3 0.4 0.5 0.3 0.4 1.0 3.1 Liver 0.4 0.8 0.4 0.3 0.3 0.3 0.3 0.4 0.4 0.4 Kidney 1.0 0.4 0.5 0.6 0.4 0.2 0.6 1.0 1.2 0.5 Muscle 0.4 0.3 0.3 0.4 0.4 0.2 0.6 0.6 0.7 0.4 Heart 0.4 0.4 0.5 1.6 0.6 0.3 2.2 0.2 0.2 0.5 Lung 0.6 1.4 0.7 - 1.0 0.5 2.2 1.5 1.1 0.5 Lower Cervical Spinal Cord 0.5 5.3 1.0 2.7 0.3 0.1 3.8 0.4 1.8 0.3 Thoracic Spinal Cord 0.1 0.2 0.2 0.4 0.1 0.1 1.2 0.3 0.6 0.1 Lumbar Spinal Cord 0.1 0.1 0.1 0.1 0.1 0.7 0.1 0.1 0.1 0.1 Spinal Dura 1.9 3.3 1.3 4.2 1.1 2.3 - 0.4 1.5 0.8 TABLE">
359
+ <confidence value="5">1</confidence>
360
+ </part-num-ref>
361
+ <boundary-data type="header">
362
+ <confidence value="8888">-10-</confidence>
363
+ </boundary-data>
364
+ <boundary-data type="header">Attorney Docket No. 1871.2-<confidence value="5">U</confidence>
365
+ S-U1 </boundary-data>
366
+ <page-break num="11"/>
367
+ [047] The method of the invention delivers the therapeutic agent to the nasal cavity of a mammal. It is preferred that the agent be delivered to the olfactory area in the upper one-third of the nasal cavity and, particularly, to the olfactory neuroepithelium in order to promote rapid and efficient delivery of the agent to the <confidence value="5">C</confidence>
368
+ NS along the olfactory neural pathway rather than the capillaries within the respiratory epithelium. The preferred transport of the therapeutic agent, e.g., DFO, to the brain by means of the olfactory and trigeminal neural pathways rather than the circulatory system so that the harmful side effects and potentially short half-life of the agent is not an issue. Further, certain agents may simply be unable due to size to cross the blood-brain barrier from the bloodstream into the CNS. The preferred method allows direct delivery of such molecules to the <confidence value="5">C</confidence>
369
+ NS. The data provided in Table <part-num-ref name="data provided in Table">1</part-num-ref>
370
+ above strongly supports the increased efficacy of one embodiment of the inventive method. </p>
371
+ <p id="p-61" num="61">[048] To deliver the therapeutic agent to the CNS, the agent alone or in combination with other substances as a pharmaceutical composition may be administered to the olfactory area located in the upper one-third of the nasal cavity. The composition may be administered intranasally as a powered or liquid spray, nose drops, a gel or ointment, through a tube or catheter, by syringe, packtail, pledget or by submucosal infusion. Optimization of the administration of the therapeutic agent is provided by the various embodiments by applying the agent to the upper third of the nasal cavity.</p>
372
+ <p id="p-62" num="62">[049] The optimal concentration of the active therapeutic agent will necessarily depend upon the specific neurologic agent used, the characteristics of the patient and the nature of the disease or condition for which the agent is being used. In addition, the concentration will depend upon whether the agent is being employed in a preventive or treatment capacity. Further, the stage of a particular disease or disorder, e.g., early vs.</p>
373
+ <p id="p-63" num="63">late Alzheimer's disease, may dictate the optimal concentration of the agent.</p>
374
+ <p id="p-64" num="64">[050] Exemplary work performed according to one embodiment of the inventive method was performed, the results of which are illustrated in Figure 1. The experimental plan included administration of a 10% solution of DFO in distilled water in <boundary-data type="header">
375
+ <confidence value="888">-11</confidence>
376
+ <confidence value="8">-</confidence>
377
+ </boundary-data>
378
+ <boundary-data type="header">Atto<confidence value="66">rn</confidence>
379
+ ey Docket No. 1871.2-US-U<confidence value="5">1</confidence>
380
+ </boundary-data>
381
+ <page-break num="12"/>
382
+ three doses of <part-num-ref name="10% solution of DFO in distilled water in three doses of">6</part-num-ref>
383
+ mg each (in <part-num-ref name="mg each (in">60</part-num-ref>
384
+ <confidence value="24">pl</confidence>
385
+ ), one dose every three hours, directly to the CNS of laboratory rats via an intranasal (IN) (upper third of naval cavity) route followed by a 2- hour middle cerebral artery occlusion (MCAO) <part-num-ref name="2- hour middle cerebral artery occlusion (MCAO)">48</part-num-ref>
386
+ hours post-DFO administration. The animals were sacrificed <part-num-ref name="animals were sacrificed">5</part-num-ref>
387
+ days after MCAO and the brains removed, sectioned on a brain matrix at 2 mm intervals and then stained with 2,3,5-triphenyltetrazolium chloride (TT<confidence value="5">C</confidence>
388
+ ). Infarct volumes were measured using NIH Image. </p>
389
+ <p id="p-65" num="65">[051] Intranasal DFO reduced infarct volumes by 60% when expressed as either total infarct, cortical infarct, or striatal infarct volume. Brain proteins from olfactory bulb and from striatum were subjected to Western blot analysis for hypoxia-inducible factor-1<confidence value="5">a</confidence>
390
+ <confidence value="885885">(HIF-1</confidence>
391
+ a). See Figure 1 for a bar graph illustrating the results <part-num-ref name="results">(10)</part-num-ref>
392
+ for control animals (C) and pretreated animals (P) . The results are shown broken into the cortex (12), striatum <part-num-ref name="cortex (12), striatum">(14)</part-num-ref>
393
+ and overall total <part-num-ref name="and overall total">(16)</part-num-ref>
394
+ infarct volumes for control/pretreated animals. Figure 1 illustrates the effectiveness of pretreating an animal with IN <confidence value="5">D</confidence>
395
+ FO administration of three doses of 10% DFO to the upper one-third of the nasal cavity (10), using the experimental procedure described above in connection with Figure 1. Here, the control animals' (C) total infarct volume is 175.93 mm<confidence value="5">3</confidence>
396
+ (18), while the pretreated animals' (P) total infarct volume is 70.57 mm<confidence value="5">3</confidence>
397
+ (20). Thus, a reduction of 60% in infarct volume is realized by way of this pretreatment regimen. </p>
398
+ <p id="p-66" num="66">[052] Quantitation of the Western blot revealed that the amount of HIF-1<confidence value="5">a</confidence>
399
+ protein present in olfactory bulb and striatum was elevated approximately 30- and 20-fold, respectively. Additional brain samples from animals treated with intranasal <confidence value="5">D</confidence>
400
+ FO were generated, total RNA was isolated from olfactory bulb and striatum, and cDNA was generated using primers specific for HIF-<confidence value="5">1</confidence>
401
+ a. The c<confidence value="5">D</confidence>
402
+ NA was subjected to RT-PCR, and the results suggest that mRNA for HIF-<confidence value="5">1</confidence>
403
+ a was abundant; however, there were no differences in the concentration of HIF-<confidence value="5">1</confidence>
404
+ a mRNA in samples from animals treated with intranasal DFO and their controls treated with intranasal distilled water. </p>
405
+ <boundary-data type="header">
406
+ <confidence value="8888">-12-</confidence>
407
+ </boundary-data>
408
+ <boundary-data type="header">Atto<confidence value="66">rn</confidence>
409
+ ey Docket No. 1871.2-<confidence value="58868">US-U1</confidence>
410
+ </boundary-data>
411
+ <p id="p-67" num="67">
412
+ <page-break num="13"/>
413
+ [053] The data thus indicate that intranasal DFO pretreatment protects the brain during stroke via a mechanism involving the transcription factor H<confidence value="5">I</confidence>
414
+ F-1<confidence value="5">a</confidence>
415
+ and that infarct volume is significantly reduced as a result. </p>
416
+ <p id="p-68" num="68">[054] With reference to Figure 2, data indicating the effectiveness of pretreating an animal with IN DFO administration of one dose of 10% DFO to the upper one-third of the nasal cavity (22), using the experimental procedure described above is illustrated.</p>
417
+ <p id="p-69" num="69">As illustrated, the total infarct volume is reduced, as compared with controls treated with distilled water. The control animals' (C) total infarct volume is measured at 117.28 mm<confidence value="5">3</confidence>
418
+ (24), while the pretreated animals' (P) infarct volume is 86.72 mm<confidence value="5">3</confidence>
419
+ (26), an overall infarct volume reduction of 26%. </p>
420
+ <p id="p-70" num="70">[055] Referring now to Figure 3, data indicating the effectiveness of pretreating an animal with IN <confidence value="5">D</confidence>
421
+ FO administration of three doses of 3% <confidence value="5">D</confidence>
422
+ FO to the upper one-third of the nasal cavity, using the experimental procedure described above is illustrated (30). </p>
423
+ <p id="p-71" num="71">Here, the control animals' (C) total infarct volume is 157.01 mm<confidence value="5">3</confidence>
424
+ (34), while the pretreated animals' (P) total infarct volume is measured to be 101.83 mm3 (38), a reduction of 35%. </p>
425
+ <p id="p-72" num="72">[056] As the data presented in Figures 1-3 indicate, preconditioning animals by administering IN DFO, or other metal chelator, to the upper one-third of the nasal cavity significantly reduces total infarct volume. The Figures further indicate significant reduction of infarct volumes located in the Cortex and Striatum.</p>
426
+ <p id="p-73" num="73">[057] Thus, in one embodiment of the invention, an effective amount or dose of a metal chelator may be administered intranasally to precondition the CNS to protect a mammal against the potential of cerebral ischemia resulting from, e.g., coronary artery bypass graft (CABG) surgery. The administration of an effective amount of a metal chelator in the upper one-third of the nasal cavity eliminates the unwanted and potentially lethal side effects of DFO, for example, possible shock and rapid elimination, while providing the agent with virtually instant access to the CNS. Other metal chelating agents may have similar unwanted systemic effects. The metal chelator acts to increase the H<confidence value="5">I</confidence>
427
+ F-1<confidence value="5">a</confidence>
428
+ <boundary-data type="header">
429
+ <confidence value="8888">-13-</confidence>
430
+ </boundary-data>
431
+ <boundary-data type="header">Atto<confidence value="66">rn</confidence>
432
+ ey Docket No. 1871.2-US-U<confidence value="5">1</confidence>
433
+ </boundary-data>
434
+ <page-break num="14"/>
435
+ subunit concentration and stability of the HIF-<confidence value="5">1</confidence>
436
+ a subunits in the CNS. In this manner, the metal chelator performs to condition, or precondition, the CNS in anticipation of possible cerebral ischemia resulting from the CABG surgery; establishing a neuroprotective state against a future episode of cerebral ischemia. </p>
437
+ <p id="p-74" num="74">[058] Several neurologic disorders may be prevented, or the effects minimized, using different embodiments of the inventive method. For example, patients at risk for Alzheimer's disease may be aided by the technique, as this disease involves neurodegeneration, preceded by cerebral vascular difficulties. See, e.g., The Lancet Neurology, vol. <part-num-ref name="Lancet Neurology, vol.">3,</part-num-ref>
438
+ pp. 184-190, Jack C. de <confidence value="5">l</confidence>
439
+ a Torre (March, 2004). Thus, patients at risk for Alzheimer's disease may be pretreated using one or more of the inventive embodiments disclosed herein. </p>
440
+ <p id="p-75" num="75">[059] Further, in another embodiment, those patients scheduled for coronary artery bypass graft (CABG) surgery may also benefit due to the relatively high percentage of post-surgical cerebral ischemia.</p>
441
+ <p id="p-76" num="76">[060] In another embodiment, patients at risk for Parkinson's disease may benefit from the inventive method.</p>
442
+ <p id="p-77" num="77">[061] In yet another embodiment patients at risk for stroke may be aided by the inventive method. Such patients would include those having risk factors comprising hypertension, diabetes, obesity, smoking, antiphospholipid syndrome or with a history of stroke (thus prone to subsequent stroke).</p>
443
+ <p id="p-78" num="78">[062] The above embodiments essentially focus on prevention of the cognitive, behavioral and physical impairment due to cerebral ischemia as a result of certain episodes, disorders or medical procedures by pretreatment using IN administration of a metal chelator, e.g., DFO to the upper one-third of the nasal cavities. A series of alternate embodiments focus on treating and/or minimizing the effects of such disorders after they have been diagnosed.</p>
444
+ <boundary-data type="header">
445
+ <confidence value="8">-</confidence>
446
+ <confidence value="88">14</confidence>
447
+ <confidence value="8">-</confidence>
448
+ </boundary-data>
449
+ <boundary-data type="header">Atto<confidence value="66">rn</confidence>
450
+ ey Docket No. 1871.2-US-U<confidence value="5">1</confidence>
451
+ </boundary-data>
452
+ <p id="p-79" num="79">
453
+ <page-break num="15"/>
454
+ [063] In this regard, let us now turn to Figure 4. Here, the experimental method is as follows: The method is the same as described above in connection with Figure 1, except that the subjects are not pretreated. Instead, IN <confidence value="5">D</confidence>
455
+ FO is administered to the upper one-third of the nasal cavity at the start of reperfusion to treat the subjects. Six doses of 10% DFO <part-num-ref name="subjects. Six doses of 10% DFO">(6</part-num-ref>
456
+ mg <confidence value="5">D</confidence>
457
+ FO/dose) were administered in this manner; three doses of 10% DFO at 2-hour intervals on the day of surgery and the remaining three doses of 10% <confidence value="5">D</confidence>
458
+ FO at three-hour intervals on the day following surgery (40). Examination of the patient brains reveals that the total infarct volume was <part-num-ref name="total infarct volume was">257</part-num-ref>
459
+ mm3 <part-num-ref name="mm3">(42)</part-num-ref>
460
+ in the control animals (C) (treated with distilled water) and <part-num-ref name="control animals (C) (treated with distilled water) and">116</part-num-ref>
461
+ mm<confidence value="5">3</confidence>
462
+ <part-num-ref name="mm3">(44)</part-num-ref>
463
+ in animals pretreated with IN DFO (P); a reduction of 55%. </p>
464
+ <p id="p-80" num="80">[064] For example, one embodiment of the inventive method may be used to treat a patient having, or recently having undergone, a stroke.</p>
465
+ <p id="p-81" num="81">[065] In another embodiment, the inventive method may be used in a treatment plan for patients at risk for, or diagnosed with, Alzheimer's disease.</p>
466
+ <p id="p-82" num="82">[066] In another embodiment, the inventive method may be used to treat patients at risk for, or diagnosed with, Parkinson's disease.</p>
467
+ <p id="p-83" num="83">[067] In another embodiment, the inventive method may be used to treat patients at risk for, or diagnosed with, Wilson's disease.</p>
468
+ <p id="p-84" num="84">[068] In another embodiment, the inventive method may be used to treat patients at risk for, or diagnosed with, traumatic brain injury, spinal cord injury or cerebral hemorrhage.</p>
469
+ <p id="p-85" num="85">[069] In yet another embodiment, patients at risk for, or diagnosed with, stroke and/or transient ischemic attack, and thus at risk for a subsequent stroke, may benefit from the inventive method.</p>
470
+ <boundary-data type="header">
471
+ <confidence value="8">-</confidence>
472
+ <confidence value="888">15-</confidence>
473
+ </boundary-data>
474
+ <boundary-data type="header">Atto<confidence value="66">rn</confidence>
475
+ ey Docket No. 1871.2-<confidence value="5">U</confidence>
476
+ S-U1 </boundary-data>
477
+ <p id="p-86" num="86">
478
+ <page-break num="16"/>
479
+ [070] Figures 5-8 illustrate another embodiment of the inventive method. Patient weight loss following an ischemic episode is a nagging problem that may ultimately inhibit and slow the patient's recovery time. Figure 5 illustrates the effect of pretreating a patient with administration of one dose of 10% IN DFO <part-num-ref name="patient with administration of one dose of 10% IN DFO">(6</part-num-ref>
480
+ mg DFO/dose) to the upper one-third of the nasal cavity has on patient weight loss post-stroke <part-num-ref name="nasal cavity has on patient weight loss post-stroke">(50)</part-num-ref>
481
+ using the experimental method described above in connection with Figure 1. Here, the control subjects (C) (treated with distilled water) lost a total of 32.31 grams <part-num-ref name="total of 32.31 grams">(52)</part-num-ref>
482
+ compared with the subjects pretreated with IN <confidence value="5">D</confidence>
483
+ FO (P) with a weight loss of 4.60 grams (54); an 86% decrease in weight loss. </p>
484
+ <p id="p-87" num="87">[071] Figure 6 illustrates the effect of pretreating a patient with administration of three doses of 3% IN DFO <part-num-ref name="patient with administration of three doses of 3% IN DFO">(6</part-num-ref>
485
+ mg DFO/dose) to the upper one-third of the nasal cavity has on patient weight loss post-stroke <part-num-ref name="nasal cavity has on patient weight loss post-stroke">(60)</part-num-ref>
486
+ using the experimental method described above in connection with Figure 1. Here, the control subjects (C) (treated with distilled water) lost a total of 54.8 grams post-stroke <part-num-ref name="total of 54.8 grams post-stroke">(62)</part-num-ref>
487
+ compared with the subjects pretreated with IN <confidence value="5">D</confidence>
488
+ FO (P) with a post-stroke weight loss of 20.5 grams (64); an 62.6% decrease in weight loss. </p>
489
+ <p id="p-88" num="88">[072] Figure 7 illustrates the effect of pretreating a patient with administration of three doses of 10% IN DFO <part-num-ref name="patient with administration of three doses of 10% IN DFO">(6</part-num-ref>
490
+ mg DFO<confidence value="5">/</confidence>
491
+ dose) to the upper one-third of the nasal cavity has on patient weight loss post-stroke <part-num-ref name="nasal cavity has on patient weight loss post-stroke">(70)</part-num-ref>
492
+ using the experimental method described above in connection with Figure 1. Here, the control subjects (C) (treated with distilled water) lost a total of 55.38 grams post-stroke <part-num-ref name="total of 55.38 grams post-stroke">(72)</part-num-ref>
493
+ compared with the subjects pretreated with IN <confidence value="5">D</confidence>
494
+ FO (P) with a post-stroke weight loss of 8.44 grams (74); an 84.8% decrease in weight loss. </p>
495
+ <p id="p-89" num="89">
496
+ <confidence value="885">[07</confidence>
497
+ 3] Figure 8 illustrates the effect of administering IN DFO post-stroke, as opposed to the pretreatment regimes provided in Figures 6-<confidence value="52">8:</confidence>
498
+ Here, six doses of 10% IN DFO <part-num-ref name="pretreatment regimes provided in Figures 6-8: Here, six doses of 10% IN DFO">(6</part-num-ref>
499
+ mg DFO/dose) are administered to the upper one-third of the patient's nasal cavity (80). </p>
500
+ <p id="p-90" num="90">Following stroke, the control subjects (C) (treated with distilled water) lost a total of 56.83 grams <part-num-ref name="total of 56.83 grams">(82)</part-num-ref>
501
+ compared with the subjects pretreated with IN DFO (P) with a weight loss of 44.67 grams (84); an 21.4% decrease in weight loss. </p>
502
+ <boundary-data type="header">
503
+ <confidence value="8">-</confidence>
504
+ <confidence value="888">16-</confidence>
505
+ </boundary-data>
506
+ <boundary-data type="header">Attorney Docket No. 1871.2-<confidence value="5">U</confidence>
507
+ S-U<confidence value="5">1</confidence>
508
+ </boundary-data>
509
+ <p id="p-91" num="91">
510
+ <page-break num="17"/>
511
+ [074] DFO is a particular example of an iron chelator that may be used in one embodiment to stimulate and/or stabilize HIF-1<confidence value="5">a</confidence>
512
+ to achieve the desired neuroprotective result. Other iron chelators that may be administered according to an embodiment of the method comprise compounds from the hydroxamate family, and salicylaldehyde isonicotinoyl hydrazone. Other equivalent iron chelating compounds will present themselves readily to those skilled in the art and are within the scope of the disclosure. </p>
513
+ <p id="p-92" num="92">[075] Alternatively, copper chelating compounds may be administered according to an embodiment of the method and comprise trientine, n-acetyl cysteine amide, tetrathiomolybdate and bi-pyridyl compounds. Other equivalent copper chelating compounds will present themselves readily to those skilled in the art and are within the scope of the disclosure.</p>
514
+ <p id="p-93" num="93">[076] In another embodiment, a pharmaceutical composition may be comprised of a combination of at least one iron-chelating compound. Another pharmaceutical composition may comprise a combination of at least one copper-chelating compound.</p>
515
+ <p id="p-94" num="94">Yet another embodiment of a pharmaceutical composition according to the method may comprise a combination of at least one iron-chelating compound coupled with at least one copper-chelating compound.</p>
516
+ <p id="p-95" num="95">[077] In still another embodiment, a pharmaceutical composition may be comprised of a combination of at least one metal-chelating compound with at least one antioxidant.</p>
517
+ <p id="p-96" num="96">[078] In another embodiment, a pharmaceutical composition comprised of DFO and IGF-1 may be administered.</p>
518
+ <p id="p-97" num="97">[079] In general, any of the therapeutic agents or pharmaceutical compositions described or referenced herein may be administered to patients or subjects under embodiments of the inventive method prior to a surgical procedure such as CABG, during such a procedure or after such a procedure.</p>
519
+ <boundary-data type="header">
520
+ <confidence value="8888">-17-</confidence>
521
+ </boundary-data>
522
+ <boundary-data type="header">Atto<confidence value="66">rn</confidence>
523
+ ey Docket No. 1871.2-US-U<confidence value="5">1</confidence>
524
+ </boundary-data>
525
+ <p id="p-98" num="98">
526
+ <page-break num="18"/>
527
+ [080] Preferentially, the inventive method, and embodiments thereof, focuses on chelating iron and/or copper. This chelation strategy thus prevents cycling of iron and/or copper between an oxidized and a reduced state. Such cycling is highly undesirable as free radicals are formed. Free radicals and other reactive oxygen species, e.g., H2<confidence value="5">0</confidence>
528
+ 2, HOCI and radicals such as <confidence value="42">O2</confidence>
529
+ , sulfur cation, nitric oxide radical, ferryl, peroxyl, peroxynitrite, thiyl, thiylperoxyl and alkoxyl, are highly reactive and may be highly damaging to cellular components as the free radicals react. Free radical reactions may crosslink proteins, mutate DNA and peroxidize lipids. Such reactions have deleterious effects on cellular homeostasis. Thus, controlling the iron and copper ions through chelating agents reduces or eliminates such free radical damage from the oxidation/reduction cycling. </p>
530
+ <p id="p-99" num="99">[081] As a result, virtually any compound that prevents the cycling of iron and copper between the oxidized and reduced state may be used in different embodiments of the inventive method.</p>
531
+ <p id="p-100" num="100">[082] In still another embodiment, the therapeutic agent according to the inventive methods may comprise one or more of the following substances which stimulate and/or stabilize H<confidence value="5">I</confidence>
532
+ F-1<confidence value="5">a</confidence>
533
+ : insulin, IGF-<confidence value="2">I</confidence>
534
+ , heregulin insulin, heregulin, TGFbeta, IL-<confidence value="5">1</confidence>
535
+ beta, TNFalpha, cobalt, pyruvate, oxalacetate and lactate. It is within the scope of invention to create a pharmaceutical composition combining one or more of the foregoing substances. In addition, in other embodiments, the invention may administer a pharmaceutical composition comprising at least one of the foregoing substances with at least one metal chelator. Further, a pharmaceutical composition may be comprised in another embodiment of at least one of the foregoing substances combined with at least one antioxidant. </p>
536
+ <p id="p-101" num="101">[083] An effective amount, as herein defined, of the therapeutic agent to be administered pursuant to embodiments of the invention is the most preferred method of expression of dosage. Such effective amount is dependent upon many factors, including but no<confidence value="4">t</confidence>
537
+ limited to, the type of disease or condition giving rise to an anticipated <boundary-data type="header">
538
+ <confidence value="8">-</confidence>
539
+ <confidence value="888">18-</confidence>
540
+ </boundary-data>
541
+ <boundary-data type="header">Atto<confidence value="66">rn</confidence>
542
+ ey Docket No. 1871.2-<confidence value="58866">US-U1</confidence>
543
+ </boundary-data>
544
+ <page-break num="19"/>
545
+ cerebral ischemic episode, the patient's general health, size, age, and the nature of treatment, i.e., short-term of chronic treatment. For illustrative purposes only, exemplary treatment regimens relating generally to the therapeutic agents disclosed herein, including dosage ranges, volumes and frequency are provided below: </p>
546
+ <p id="p-102" num="102">[084] Efficacious dosage range: 0.0001 - 1.0 mg/kg.</p>
547
+ <p id="p-103" num="103">[085] A more preferred dosage range may be 0.005 - 1.0 mg/kg.</p>
548
+ <p id="p-104" num="104">[086] The most preferred dosage range may be 0.05 - 1.0 mg/kg.</p>
549
+ <p id="p-105" num="105">[087] The dosage volume (applicable to nasal sprays or drops) range may be 0.015 ml <confidence value="8">-</confidence>
550
+ 1.0 ml. </p>
551
+ <p id="p-106" num="106">[088] The preferred dosage volume (applicable to nasal sprays or drops) range may be 0.03 ml - 0.6 ml.</p>
552
+ <p id="p-107" num="107">[089] Generally, the treatment may be given in a single dose or multiple administrations, i.e., once, twice, three or more times daily over a period of time. For chronic disorders such as those diagnosed with, or at risk for, Alzheimer's disease, stroke or Parkinson's disease, the treatment may consist of at least one dose per day over an extended period of time. Alternatively, for those patients anticipating CABG surgery, the treatment may be a one-time dose to precondition the CNS in anticipation of potential cerebral ischemia. Such preconditioning may require more than one dose and may be administered from <part-num-ref name="CNS in anticipation of potential cerebral ischemia. Such preconditioning may require more than one dose and may be administered from">12</part-num-ref>
553
+ hours to <part-num-ref name="hours to">1</part-num-ref>
554
+ week prior to the CABG surgery. Post- stroke treatment may require more than one dose which may be administered several times over the course of a day, wherein this treatment regimen may encompass a week or more. </p>
555
+ <p id="p-108" num="108">[090] The brain concentrations that are likely to be achieved with the dosage ranges provided above are, for a single dose: 0.1 nM - <part-num-ref name="single dose: 0.1 nM -">50</part-num-ref>
556
+ <confidence value="2">p</confidence>
557
+ M. Over the course of a multi-dose treatment plan, the maximum brain concentration may be as high as <part-num-ref name="maximum brain concentration may be as high as">500</part-num-ref>
558
+ <confidence value="288">pM.</confidence>
559
+ </p>
560
+ <boundary-data type="header">
561
+ <confidence value="8">-</confidence>
562
+ <confidence value="888">19-</confidence>
563
+ </boundary-data>
564
+ <boundary-data type="header">Atto<confidence value="66">rn</confidence>
565
+ ey Docket No. 1871.2-<confidence value="66866">US-U1</confidence>
566
+ </boundary-data>
567
+ <p id="p-109" num="109">
568
+ <page-break num="20"/>
569
+ [091] The present invention should not be considered limited to the particular examples described above, but rather should be understood to cover all aspects of the invention. Various modifications, equivalent processes, as well as numerous structures to which the present invention may be applicable will be readily apparent to those of skill in the art to which the present invention is directed upon review of the present specification. </p>
570
+ <boundary-data type="header">
571
+ <confidence value="8">-</confidence>
572
+ <confidence value="88">20</confidence>
573
+ <confidence value="8">-</confidence>
574
+ </boundary-data>
575
+ <boundary-data type="header">Attorney Docket No. 1871.2-US-U<confidence value="5">1</confidence>
576
+ </boundary-data>
577
+ </description>
578
+ </us-patent-application>
579
+
prior_art/11207865.xml ADDED
@@ -0,0 +1,68 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11207865</doc-number>
8
+ <date>2006-03-09</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <p id="p-1" num="1">03/09/06 THU 16:11 FAX 4134487625 IP-LEGAL <confidence value="266">-4-</confidence>
14
+ USPTO CENT. FAX. <part-num-ref name="IP-LEGAL -4- USPTO CENT. FAX.">
15
+ <confidence value="14">41</confidence>
16
+ 004 </part-num-ref>
17
+ 153025-3 </p>
18
+ <heading id="h-1">
19
+ <confidence value="5">I</confidence>
20
+ N THE SPEC<confidence value="8">I</confidence>
21
+ FICATION </heading>
22
+ <p id="p-2" num="2">Please replace the existing section "CROSS-REFERENCE TO RELATED APPLICATIONS" on page <part-num-ref name="existing section &quot;CROSS-REFERENCE TO RELATED APPLICATIONS&quot; on page">1</part-num-ref>
23
+ of the specification, and replace with the following two sections, which are to be placed before the section F<confidence value="4">I</confidence>
24
+ ELD OF THE INVENT<confidence value="5">I</confidence>
25
+ ON. </p>
26
+ <heading id="h-2">STATEMENT REGARDING FEDERALLY FUNDED RESEARCH AND DEVELOPMENT</heading>
27
+ <p id="p-3" num="3">The U.S. Government may have certain rights in this invention pursuant to contract number <confidence value="86">70</confidence>
28
+ NANB2<confidence value="5">H</confidence>
29
+ 3034 awarded by the U.S. National Institute of Standards and Technology. </p>
30
+ <heading id="h-3">CROSS-REFERENCE TO RELATED APPLICATIONS</heading>
31
+ <p id="p-4" num="4">This application is a continuation-in-pa<confidence value="66">rt</confidence>
32
+ of US Patent Application Serial No. 10<confidence value="5">/</confidence>
33
+ 652,283 filed March <part-num-ref name="continuation-in-part of US Patent Application Serial No. 10/652,283 filed March">29,</part-num-ref>
34
+ <part-num-ref name="continuation-in-part of US Patent Application Serial No. 10/652,283 filed March 29,">2003,</part-num-ref>
35
+ which application is a continuation-in-part of US Patent Application Serial No. <part-num-ref name="continuation-in-part of US Patent Application Serial No.">09<confidence value="5">1</confidence>
36
+ 754154, </part-num-ref>
37
+ filed Jan. <part-num-ref name="continuation-in-part of US Patent Application Serial No. 091754154, filed Jan.">3,</part-num-ref>
38
+ <part-num-ref name="continuation-in-part of US Patent Application Serial No. 091754154, filed Jan. 3,">2001,</part-num-ref>
39
+ now US Patent No. 6,713<confidence value="5">,</confidence>
40
+ 088, issued April <part-num-ref name="continuation-in-part of US Patent Application Serial No. 091754154, filed Jan. 3, 2001, now US Patent No. 6,713,088, issued April">22,</part-num-ref>
41
+ <part-num-ref name="continuation-in-part of US Patent Application Serial No. 091754154, filed Jan. 3, 2001, now US Patent No. 6,713,088, issued April 22,">2004,</part-num-ref>
42
+ which is a continuation-in-part of US Patent Application No. 09/386<confidence value="5">,</confidence>
43
+ 883 filed Aug. <part-num-ref name="continuation-in-part of US Patent Application No. 09/386,883 filed Aug.">31,</part-num-ref>
44
+ <part-num-ref name="continuation-in-part of US Patent Application No. 09/386,883 filed Aug. 31,">1999.</part-num-ref>
45
+ This application also claims the benefits of U.S. Provisional Paten<confidence value="5">t</confidence>
46
+ Application Serial Number 60/603777 filed August <part-num-ref name="benefits of U.S. Provisional Patent Application Serial Number 60/603777 filed August">23,</part-num-ref>
47
+ <part-num-ref name="benefits of U.S. Provisional Patent Application Serial Number 60/603777 filed August 23,">2004</part-num-ref>
48
+ and U.S. Provisional Patent Application Serial Number 60/661395 filed March <part-num-ref name="and U.S. Provisional Patent Application Serial Number 60/661395 filed March">14,</part-num-ref>
49
+ <part-num-ref name="and U.S. Provisional Patent Application Serial Number 60/661395 filed March 14,">2005,</part-num-ref>
50
+ which patent applications are f<confidence value="8">u</confidence>
51
+ lly incorporated herein by reference. </p>
52
+ <p id="p-5" num="5">PAGE 4<confidence value="588">119</confidence>
53
+ <confidence value="66">'R</confidence>
54
+ CVD AT 319<confidence value="4">/</confidence>
55
+ 2006 3:49:22 PM <confidence value="5">[</confidence>
56
+ Easte<confidence value="66">rn</confidence>
57
+ Standard Time] SVR:USPT<confidence value="55">OE</confidence>
58
+ FXRF<confidence value="281882">.3122*</confidence>
59
+ DNIS:273<confidence value="4">8</confidence>
60
+ 300<confidence value="1">t</confidence>
61
+ CSI<confidence value="5">D</confidence>
62
+ :413448762<confidence value="42">5*</confidence>
63
+ DURATION (mm<confidence value="2">-</confidence>
64
+ ss):04<confidence value="88">44</confidence>
65
+ </p>
66
+ </description>
67
+ </us-patent-application>
68
+
prior_art/11211134.xml ADDED
@@ -0,0 +1,37 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11211134</doc-number>
8
+ <date>2009-09-17</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <heading id="h-1">PATENT</heading>
14
+ <p id="p-1" num="1">P57576 </p>
15
+ <heading id="h-2">
16
+ <confidence value="86">IN</confidence>
17
+ <confidence value="85">TH</confidence>
18
+ E SPE<confidence value="8">C</confidence>
19
+ IFICATION </heading>
20
+ <p id="p-2" num="2">Please amend the title of the invention in its entirety to read as follows:</p>
21
+ <heading id="h-3">SECONDARY <confidence value="2">B</confidence>
22
+ <confidence value="222222">ATTERY</confidence>
23
+ INCLUDING PROTEC<confidence value="8">T</confidence>
24
+ IVE </heading>
25
+ <heading id="h-4">
26
+ <confidence value="8">C</confidence>
27
+ IRC<confidence value="8">U</confidence>
28
+ IT MODULE <confidence value="86">TO</confidence>
29
+ PROTECT BATTERY WHEN </heading>
30
+ <heading id="h-5">SWELLI<confidence value="8">N</confidence>
31
+ G OCCURS </heading>
32
+ <p id="p-3" num="3">
33
+ <confidence value="222">-2-</confidence>
34
+ </p>
35
+ </description>
36
+ </us-patent-application>
37
+
prior_art/11221522.xml ADDED
@@ -0,0 +1,490 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?xml version="1.0" encoding="utf-8"?>
2
+ <!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
3
+ <us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
4
+ <us-bibliographic-data-application lang="EN" country="US">
5
+ <application-reference appl-type="utility">
6
+ <document-id>
7
+ <doc-number>11221522</doc-number>
8
+ <date>2005-09-08</date>
9
+ </document-id>
10
+ </application-reference>
11
+ </us-bibliographic-data-application>
12
+ <description id="description">
13
+ <boundary-data type="header">Attorney Docket No. 25647A</boundary-data>
14
+ <heading id="h-1">TITLE OF THE INVENTION</heading>
15
+ <heading id="h-2">POLYSTYRENE FOAM CONTAINING A MODIFIER-FREE</heading>
16
+ <heading id="h-3">NANOCLAY AND HAVING IMPROVED FIRE PROTECTION PERFORMANCE</heading>
17
+ <heading id="h-4">REFERENCE TO GOVERNMENT RIGHTS</heading>
18
+ <p id="p-1" num="1">[0001<confidence value="5">]</confidence>
19
+ This invention was made with Government support under Advanced Technology Program (ATP) Grant No. 70NANB2H3023 awarded by the National Institute of Standards and Technology (<confidence value="2222">NIST</confidence>
20
+ ). The Government may have certain rights to this invention. </p>
21
+ <heading id="h-5">TECHNICAL FIELD AND INDUSTRIAL</heading>
22
+ <heading id="h-6">APPLICABILITY OF THE INVENTION</heading>
23
+ <p id="p-2" num="2">[0002] The present invention relates generally to polymer foams containing a nanoclay, and more particularly, to polymer foams containing a modifier-free nanoclay that provides improved fire resistance. Methods of forming such modifier-free nanoclay polymer foams are also provided.</p>
24
+ <heading id="h-7">BACKGROUND OF THE INVENTION</heading>
25
+ <p id="p-3" num="3">[0003<confidence value="5">]</confidence>
26
+ Foamed resinous structures are useful in a wide variety of applications such as thermal insulation, in cushions, as packaging, and as adsorbents. Extruded foams are generally made by melting a polymer together with any desired additives to create a polymer melt. A blowing agent is mixed with the polymer melt at an appropriate temperature and pressure to produce a foamable gel mixture. The foamable gel mixture is then cooled and extruded into a zone of reduced pressure, which results in a foaming of the gel and the formation of the desired extruded foam product. </p>
27
+ <p id="p-4" num="4">[0004] Nanoclays have been used to modify cellular foams in both batch and continuous extrusion foaming processes. It has been discovered that the addition of <boundary-data type="header">
28
+ <confidence value="666">-1-</confidence>
29
+ </boundary-data>
30
+ <page-break num="2"/>
31
+ </p>
32
+ <heading id="h-8">
33
+ <confidence value="111">I''</confidence>
34
+ </heading>
35
+ <p id="p-5" num="5">Attorney Docket No. 25647A nanoclays into the polymer matrix of cellular foams results in an improvement in physical properties, such as improvements in mechanical strength (tensile modulus and strength and flexural modulus and strength), thermal stability, flame retardance, and barrier resistance.</p>
36
+ <p id="p-6" num="6">Three polymer/clay structures are possible: agglomerated nano-particles, intercalated nano- layers, and exfoliated nano-layers. In general, the greatest physical property enhancements, such as reducing the gas permeability, increasing the modulus, and/or increasing the thermal stability, are observed from nano-layers that are fully exfoliated throughout the polymer matrix.</p>
37
+ <p id="p-7" num="7">
38
+ <confidence value="5">[</confidence>
39
+ 0005<confidence value="5">]</confidence>
40
+ Although nanoclays have a high aspect ratio, they require special treatment to separate the nano-layers and achieve exfoliation. One such manner of achieving exfoliated nanolayers is to incorporate an organic modifier in the clay. Layered nano-materials, such as organo-montmorillonite, typically contain approximately <part-num-ref name="clay. Layered nano-materials, such as organo-montmorillonite, typically contain approximately">30</part-num-ref>
41
+ - <part-num-ref name="-">40</part-num-ref>
42
+ wt % of low molecular weight organic modifiers. These modifiers are used to convert the clay surface from hydrophilic to hydrophobic, and to make the clay particles compatible with the polymer matrix for dispersion. Previous attempts to form an intercalated or exfoliated microstructure of a nanoclay-polymer matrix/composite have utilized modifiers such as methacryloyloxyethylhexadecyl-dimethyl ammoniums and methyl tallow bis-2-hydroxyethyl quaternary ammonia salts (e.g., Closite 20A, commercially available from Southern Clay Products Inc.). Although polymer nanoclay composite foams containing such modifiers have demonstrated promising fire retardant properties in terms of reduced heat release, smoke release rate, and char forming during firing, these surface modifiers are considered fire hazards based on industry fire tests, such as oxygen index and flame surface spread rates. </p>
43
+ <p id="p-8" num="8">[0006<confidence value="5">]</confidence>
44
+ Therefore, there exists a need in the art to achieve an extruded or expanded polymer foam that contains a uniform clay dispersion in the polymer matrix that maintains the positive physical properties of nanoclay foam composites and meets the stringent requirements for industrial fire resistance applications. </p>
45
+ <boundary-data type="header">-2-</boundary-data>
46
+ <boundary-data type="header">Attorney Docket No. 25647A</boundary-data>
47
+ <heading id="h-9">SUMMARY OF THE INVENTION</heading>
48
+ <p id="p-9" num="9">
49
+ <page-break num="3"/>
50
+ [0007<confidence value="5">]</confidence>
51
+ It is an object of the present invention to provide expandable polymer beads that may be used to form insulation products such as foamed building and underground insulation products. The polymer beads are generally spherical and contain multiple water/nanoclay particles suspended in an emulsified water phase. The water/nanoclay particles are substantially uniformly distributed within the polymer matrix. The particular polymer utilized to form the polymer beads is preferably selected to provide sufficient mechanical strength to avoid rupture as a result of mechanical stress during formation of the bead, inclusion into the polymeric foam, and the processes utilized to form final polymer products. The polymer material is also preferably chemically stable within the expected temperature range during formation and subsequent use in a polymeric foam. Suitable examples include polystyrene, melamine formaldehyde, polyurethane, polymethyleneurea, polyester, polyethylene, polypropylene, polyethylene terephthalate, polycarbonate, polyamide, polyvinyl chloride, and polyvinyl alcohol. The nanoclay forming the water/nanoclay particles is preferably a modifier-free nanoclay, such as Na<confidence value="1">+</confidence>
52
+ MMT or Ca<confidence value="11">z+</confidence>
53
+ MMT. The polymer beads containing the water/nanoclay particles may be formed into a foam by an expanding process in which the polymer beads are expanded in a mold having a desired shape. The polymer beads may be expanded such by hot air, hot oil, supersaturated water steam, or microwave heating. The addition of nanoclay improves thermal and mechanical properties as well fire performance properties of the foam products. In addition, the modifier-free nanoclays reduce the burning characteristics of polymer foams such as melting and dripping and assists in the increase formation of char, which helps to meet stringent fire requirements. </p>
54
+ <p id="p-10" num="10">[0008] It is also an object of the present invention to provide a method of forming expandable polymer beads that may be used to form insulation products such as foamed building and underground insulation products. In one exemplary embodiment of the invention, the polymer beads described above are formed using inverse emulsion/suspension polymerizations. Water or water-containing compounds such as water/surfactant(s), water/alcohol(s), and water/polymer(s) may be used as a carrier to form the nanoclay composites. Preferably, the carrier is water. Initially, the modifier-free nanoclay is dispersed <boundary-data type="header">-3-</boundary-data>
55
+ <page-break num="4"/>
56
+ <boundary-data type="header">Attorney Docket No. 25647A</boundary-data>
57
+ in water such as by mechanical stirring to form a water/clay mixture. The nanoclay may be further moistened and pre-expanded by microwave heating, steaming, or frozen/vacuum treating before dispersing the modifier-free nanoclay into the water carrier. The water/clay mixture may then be emulsified in a pre-polymerized styrene/polystyrene system with the aid <confidence value="88">of</confidence>
58
+ non-flammable surfactants to form a water-in-oil (w/o) inverse emulsion. The non- flammable surfactants may be present in an amount from 0.1 to 3% by weight of styrene/polystyrene to stabilize the water/clay mixture. The inverse emulsion may be suspended in water (suspension water) in the presence of suspension stabilizers that can be removed after the completion of the polymerization. The suspension is then cooled to room (ambient) temperature and the spherical polystyrene beads containing the water/modifier-free nanoclay particles may be recovered by conventional rinsing and filtration techniques. </p>
59
+ <p id="p-11" num="11">[0009] It is a further object of the present invention to provide a method of forming insulation products such as foamed building and underground insulation products utilizing a modifier-free nanoclay encapsulated in a superabsorbent material. A modifier-free nanoclay such as Na<confidence value="188">+MM</confidence>
60
+ T or Ca<confidence value="55">2+</confidence>
61
+ MMT is dispersed in a carrier and agitated to form a carrier/nanoclay mixture. The carrier is preferably water, or a water-containing compound such as water/surfactant(s), water/alcohol(s), and water/polymer(s). Most preferably, the carrier is water. The carrier/nanoclay mixture is encapsulated in a superabsorbent material to form a modifier-free, nanoclay-containing compound that may be used in an extrusion or expansion foaming process. Examples of superabsorbent materials include crosslinked sodium polyacrylates and fine inorganic chemicals such as fumed or precipitated silica, zeolite, carbon black, zeolite, and diatomaceous earth. An extruded foam product may be prepared by any method known to those of skill in the art such as with an extruder (twin or single), a mixer, or a blender. </p>
62
+ <p id="p-12" num="12">
63
+ <confidence value="5">[</confidence>
64
+ 0010] It is an advantage of the present invention that the absence of surface modifiers on the nanoclay increases the resistance of foam products formed from such modifier-free nanoclays to fire, such as by reducing the flame spread and dripping and increasing oxygen index and char formation. </p>
65
+ <boundary-data type="header">
66
+ <confidence value="686">-4-</confidence>
67
+ </boundary-data>
68
+ <boundary-data type="header">Attorney Docket No. 25647A</boundary-data>
69
+ <p id="p-13" num="13">
70
+ <page-break num="5"/>
71
+ <confidence value="5">[</confidence>
72
+ 0011<confidence value="5">]</confidence>
73
+ It is another advantage of the present invention that the increased blowing power of water over conventional blowing agents produces a foam with <confidence value="5">b</confidence>
74
+ i-modal cell morphology, which may enhance the R-value of the insulation. </p>
75
+ <p id="p-14" num="14">
76
+ <confidence value="5">[</confidence>
77
+ 0012<confidence value="5">]</confidence>
78
+ It is also an advantage of the present invention that the modifier-free nanoclay polymer compounds have intercalated or exfoliated nano-layers that lead to an improvement of physical properties such as barrier resistance, mechanical strength, and flexural and tensile modulus. </p>
79
+ <p id="p-15" num="15">[0013] It is yet another advantage of the present invention that water is used as a carrier and as a co-blowing agent. Water provides a <confidence value="885">low</confidence>
80
+ -cost, environmentally friendly alternative to conventional hydrocarbon blowing agents. </p>
81
+ <p id="p-16" num="16">[0014] It is a further advantage of the present invention that the weaker interaction between the clay and the polymer matrix without clay surface modification may facilitate the orientation of the clay and improve physical properties such as barrier resistance, thermal stability, mechanical strength, and wear resistance.</p>
82
+ <p id="p-17" num="17">[0015] It is also an advantage of the present invention that the dispersion of the nanoclay in water increases safety and reduces human health concerns because the nanoclay is compounded directly into monomer or polymer.</p>
83
+ <p id="p-18" num="18">[0016] The foregoing and other objects, features, and advantages of the invention will appear more fully hereinafter from a consideration of the detailed description that follows. It is to be expressly understood, however, that the drawings are for illustrative purposes and are not to be construed as defining the limits of the invention.</p>
84
+ <heading id="h-10">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
85
+ <p id="p-19" num="19">[0017<confidence value="5">]</confidence>
86
+ The advantages of this invention will be apparent upon consideration of the following detailed disclosure of the invention, especially when taken in conjunction with the accompanying drawings wherein: </p>
87
+ <p id="p-20" num="20">[0018] FIG. 1 is a schematic illustration of a polymerization reactor used in accordance with at least one embodiment of the present invention;</p>
88
+ <boundary-data type="header">-5-</boundary-data>
89
+ <boundary-data type="header">Attorney Docket No. 25647A</boundary-data>
90
+ <p id="p-21" num="21">
91
+ <page-break num="6"/>
92
+ [0019] F<confidence value="5">I</confidence>
93
+ G. 2a is a schematic depiction of an emulsification of water in a styrene/polystyrene mixture; </p>
94
+ <p id="p-22" num="22">[0020] FIG. 2b is a schematic depiction of a suspension polymerization of styrene/polystyrene droplets;</p>
95
+ <p id="p-23" num="23">
96
+ <confidence value="5">[</confidence>
97
+ 0021] FIG. 3a is a scanning electron microscope (SEM) image of compacted microscopic water-containing polystyrene beads (10% H20); </p>
98
+ <p id="p-24" num="24">
99
+ <confidence value="5">[</confidence>
100
+ 0022] FIG 3b is a scanning electron microscope (SEM) image of compacted microscopic beads containing nanoclay and water (0.5 wt. % nanoclay, 10% H2<confidence value="588">O);</confidence>
101
+ </p>
102
+ <p id="p-25" num="25">
103
+ <confidence value="5">[</confidence>
104
+ 0023] FIG. 4a is a scanning electron microscope image (SEM) of the foam morphology of microscopic water-containing beads (10% H2<confidence value="5">O</confidence>
105
+ ) expanded with an air gun <part-num-ref name="air gun">(135</part-num-ref>
106
+ <confidence value="2">°</confidence>
107
+ C, <part-num-ref name="°C,">1</part-num-ref>
108
+ m<confidence value="66">in</confidence>
109
+ .); </p>
110
+ <p id="p-26" num="26">
111
+ <confidence value="5">[</confidence>
112
+ 0024] FIG. 4b is a scanning electron microscope (SEM) image of the foam morphology of microscopic water-containing beads (10% H2<confidence value="5">O</confidence>
113
+ ) expanded with an oil bath <part-num-ref name="oil bath">(135</part-num-ref>
114
+ <confidence value="2">°</confidence>
115
+ C, <part-num-ref name="°C,">1</part-num-ref>
116
+ m<confidence value="66">in</confidence>
117
+ .); </p>
118
+ <p id="p-27" num="27">[0025<confidence value="5">]</confidence>
119
+ FIG. 4c is a scanning electron microscope (SEM) image of the foam morphology of microscopic beads containing nanoclay (0.5 wt. % nanoclay, 10% H2<confidence value="68">O)</confidence>
120
+ expanded with an air gun <part-num-ref name="air gun">(135</part-num-ref>
121
+ <confidence value="2">°</confidence>
122
+ C, <part-num-ref name="°C,">1</part-num-ref>
123
+ m<confidence value="66">in</confidence>
124
+ .); </p>
125
+ <p id="p-28" num="28">[0026<confidence value="5">]</confidence>
126
+ FIG. 4d is a scanning electron microscope (SEM) image of the foam morphology of microscopic beads containing nanoclay (0.5 wt. % nanoclay, 10% H2<confidence value="68">O)</confidence>
127
+ expanded with an oil bath <part-num-ref name="oil bath">(135</part-num-ref>
128
+ <confidence value="2">°</confidence>
129
+ C, <part-num-ref name="°C,">1</part-num-ref>
130
+ m<confidence value="66">in</confidence>
131
+ .); </p>
132
+ <p id="p-29" num="29">
133
+ <confidence value="5">[</confidence>
134
+ 0027<confidence value="5">]</confidence>
135
+ FIGS. <confidence value="4">S</confidence>
136
+ a and <confidence value="4">S</confidence>
137
+ b are transmission electron microsope images (TEM) of water contained polystyrene nanoclay composites; and [0028<confidence value="5">]</confidence>
138
+ FIG. 6 is an x-ray diffraction (XRD) pattern of polystyrene/Na<confidence value="1">+</confidence>
139
+ MMT composites. </p>
140
+ <heading id="h-11">DETAILED DESCRIPTION AND</heading>
141
+ <heading id="h-12">PREFERRED EMBODIMENTS OF THE INVENTION</heading>
142
+ <p id="p-30" num="30">[0029<confidence value="5">]</confidence>
143
+ Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the <boundary-data type="header">-6-</boundary-data>
144
+ <page-break num="7"/>
145
+ <boundary-data type="header">Attorney Docket No. 25647A</boundary-data>
146
+ invention belongs. Although any methods and materials similar or equivalent to those described herein can be used in the practice or testing of the present invention, the preferred methods and materials are described herein. All references cited herein, including published or corresponding U.S. or foreign patent applications, issued U.S. or foreign patents, or any other references, are each incorporated by reference in their entireties, including all data, tables, figures, and text presented in the cited references. In the drawings, the thickness of the lines, layers, and regions may be exaggerated for clarity. It is to be noted that like numbers found throughout the figures denote like elements. </p>
147
+ <p id="p-31" num="31">
148
+ <confidence value="5">[</confidence>
149
+ 0030] The present invention relates to polymer extruded or expanded foams that contain modifier-free nanoclays and methods of making such polymer foams. The foams may be formed into an insulation product such as building insulation or underground insulation (e.g., highway, airport runway, railway, and underground utility insulation). In the present invention, water or a water-containing compound is used as a medium and a carrier for the modifier-free nanoclays. The addition of nano-materials to the foams improves thermal and mechanical properties as well fire performance properties. In addition, the modifier-free nanoclays assist in improving fire performance properties such as char formation, increasing the oxygen index, and decreasing the flame spread, which helps to meet stringent fire requirements. </p>
150
+ <p id="p-32" num="32">[0031<confidence value="5">]</confidence>
151
+ In one exemplary embodiment of the invention, polymer beads containing myriads of water/nanoclay particles (droplets) are formed using inverse emulsion/suspension polymerizations. Water or water-containing compounds such as water/surfactant(s), water/alcohol(s), and water/polymer(s) may be used as a carrier to form the nanoclay composites of the present invention. Water is preferably used as a carrier to reduce or eliminate the fire hazards of conventional modified nanoclays. It is desirable that the water is distilled water, and even more desirable that the water is deionized water. Water may also be used as a blowing or co-blowing agent in forming an expanded or extruded polystyrene foam. </p>
152
+ <p id="p-33" num="33">There are several advantages to utilizing water as a co-blowing agent to produce low density foams. For example, water is an effective and environmentally friendly low-cost co-blowing agent. It is non-flammable and does not produce volatile organic carbon (VOC) <boundary-data type="header">
153
+ <confidence value="686">-7-</confidence>
154
+ </boundary-data>
155
+ <page-break num="8"/>
156
+ <boundary-data type="header">Attorney Docket No. 25647A</boundary-data>
157
+ hydrocarbons. In addition, the high enthalpy of vaporization allows water to function as a coolant during the foaming process. Further, the increased blowing power of water over conventional blowing agents produces a foam with bi-modal cell morphology, which, in turn, may enhance the insulation R-value. </p>
158
+ <p id="p-34" num="34">
159
+ <confidence value="5">[</confidence>
160
+ 0032<confidence value="5">]</confidence>
161
+ Modifier-free nanoclays used in the present invention are not particularly limited and include modifier-free nanoclays such as sodium montmorillonite (Na<confidence value="1">+</confidence>
162
+ MMT), and calcium montmorillonite (Ca2<confidence value="5">+</confidence>
163
+ MMT), which can be synthetic or natural. Although calcium montmorillonite typically exists as aggregates formed of layered structures, the aggregates can be exfoliated in a water-based solution. It is to be appreciated that layered tal<confidence value="8">c</confidence>
164
+ minerals may be included in addition to, or in place of, the modifier-free nanoclays, and such embodiments are considered to be within the purview of this invention. In preferred embodiments, the nanoclay is Na<confidence value="1">+</confidence>
165
+ MMT, which is commercially available from Southe<confidence value="66">rn</confidence>
166
+ Clay Products, Inc. </p>
167
+ <p id="p-35" num="35">[0033] The polymer material utilized in forming the polymer beads according to the present invention include one or more polymeric materials such as polystyrene (PS), melamine formaldehyde (MF), polyurethane (PU), polymethyleneurea, polyester, polyethylene (PE), polypropylene (PP), polyethylene terephthalate (PET), polycarbonate (PC), polyamide (PA), polyvinyl chloride (PVC), and polyvinyl alcohol (PVA). The particular polymer material may be selected to provide sufficient mechanical strength to avoid rupture as a result of mechanical stress during formation, inclusion into the polymeric foam, and the processes utilized to form final polymer products. The polymer material is also preferably chemically stable, i.e., generally non-reactive, within the expected temperature range during formation and subsequent use in a polymeric foam. In a preferred embodiment, the polymer material is polystyrene.</p>
168
+ <p id="p-36" num="36">
169
+ <confidence value="5">[</confidence>
170
+ 0034<confidence value="5">]</confidence>
171
+ It is to be noted that although any of the carriers (e.g., water) or polymers (e.g., polystyrene) identified above may be used to form the carrier/nanoclay containing polymer beads, the embodiments will be described herein with respect to the preferred carrier, water, and the preferred polymer, polystyrene. The modifier-free nanoclay is dispersed in water such as by mechanical stirring. Optionally, the modifier-free nanoclay may be further moistened and pre-expanded by microwave heating, steaming, or frozen/vacuum treating <boundary-data type="header">-8-</boundary-data>
172
+ <page-break num="9"/>
173
+ <boundary-data type="header">Attorney Docket No. 25647A</boundary-data>
174
+ before dispersing the modifier-free nanoclay into the water carrier. A substantially uniform dispersion of water and clay may be achieved due to the hydrophilic clay surface. As used herein, the term "substantially uniform dispersion of water and clay" is meant to indicate that the clay is uniformly dispersed in the carrier (e.g., water) or that the clay is nearly uniformly dispersed in the carrier (e.g., water). </p>
175
+ <p id="p-37" num="37">[0035] The water/clay mixture may then be emulsified in a prepolymerized styrene/polystyrene system with the aid of non-flammable surfactants to form a water-in-oil (w/o) inverse emulsion. It is to be appreciated that the water/clay mixture may be emulsified in other types of polymers such as epoxy, phenolic, and polymethyl methacrylate (PMMA) as long as the monomer does not react with the water (i.e., carrier) during synthesis of the polystyrene beads. The non-flammable surfactants may be present in an amount from 0.1 to 3% by weight of styrene/polystyrene to stabilize the water/clay mixture. Suitable surfactants include amphiphillic surfactants such as bis(2-ethylhexyl) sulfosuccinate (AOT, commercially available from Sigma-Aldrich Corp.), sorbitan monooleate (SPAN <part-num-ref name="water/clay mixture. Suitable surfactants include amphiphillic surfactants such as bis(2-ethylhexyl) sulfosuccinate (AOT, commercially available from Sigma-Aldrich Corp.), sorbitan monooleate (SPAN">80,</part-num-ref>
176
+ commercially available from Sigma-Aldrich Corp.), sorbitan monostearate (SPAN <part-num-ref name="water/clay mixture. Suitable surfactants include amphiphillic surfactants such as bis(2-ethylhexyl) sulfosuccinate (AOT, commercially available from Sigma-Aldrich Corp.), sorbitan monooleate (SPAN 80, commercially available from Sigma-Aldrich Corp.), sorbitan monostearate (SPAN">60,</part-num-ref>
177
+ commercially available from Sigma-Aldrich Corp.), non-ionic surfactants, anionic surfactants, and any non- flammable water-in-oil (w/o) emulsifier. It is preferred that the surfactants be certified as non-flammable according to the Hazardous Materials Identification System (HMI<confidence value="5">S</confidence>
178
+ ) and/or the National Fire Protection Association (NFPA). </p>
179
+ <p id="p-38" num="38">[0036] The inverse emulsion may be suspended in water (suspension water) in the presence of suspension stabilizers that can be removed after the completion of the polymerization. Preferably, the suspension water is distilled water, and even more preferably deionized water. Other suitable suspension stabilizers include, but are not limited to hydroxyethylcellulose (HEC), polyvinyl alcohol (PVA), polyvinyl-pyrrolidone, salts of acrylic acid polymers, cellulose ethers, agarose, and natural gums that may be combined with an anionic emulsifier, and combinations thereof. The suspension stabilizers may be present in the inverse emulsion in an amount of approximately 0.1 - 5% by weight based on the suspension water, preferably in an amount of about <part-num-ref name="amount of about">1</part-num-ref>
180
+ - 1.5% by weight based on the suspension water. The suspension is cooled to room (ambient) temperature and the spherical <boundary-data type="header">-9-</boundary-data>
181
+ <page-break num="10"/>
182
+ <boundary-data type="header">Attorney Docket No. 25647A</boundary-data>
183
+ polystyrene beads containing the water/modifier-free nanoclay particles may be recovered by conventional rinsing and filtration techniques. The polystyrene beads may have a clay content up to 15% by weight based on the styrene/polystyrene, preferably a clay content of about <part-num-ref name="clay content of about">1</part-num-ref>
184
+ - 15% by weight based on the styrene/polystyrene, and more preferably a clay content of about 0.1 - 5% by weight based on the styrene/polystyrene. </p>
185
+ <p id="p-39" num="39">[0037<confidence value="5">]</confidence>
186
+ The polymer beads contain a uniform or substantially uniform distribution of water/modifier-free nanoclay particles within a polymer matrix (e.g., styrene/polystyrene system). The polymer beads are generally spherical in shape and have diameters of about 0.01 - <part-num-ref name="polymer beads are generally spherical in shape and have diameters of about 0.01 -">5</part-num-ref>
187
+ mm. The polymer beads containing the nanoclay may be formed into a foam by an expanding process in which the polymer beads containing the water/nanoclay particles are expanded such as by hot air, hot oil, supersaturated water steam, or microwave heating in a mold having a desired shape. The incorporation of the nanoclay in the polymer beads may result in an increased expansion ratio and final foam structures with bi-modal cell morphology. The final foam structures are preferably utilized in building applications such as building insulations for masonry cavity-walls, tilt-up walls, roofing, exterior walls, and under floor slabs and in underground applications such as highway insulation, airport runway insulation, railway insulation, and underground utility insulation. Further, the nanoclay polymer compounds provide intercalated or exfoliated nano-layers. The intercalated or exfoliated layers may lead to an improvement or enhancement of physical properties such as barrier resistance, mechanical strength, and flexural and tensile modulus. </p>
188
+ <p id="p-40" num="40">
189
+ <confidence value="5">[</confidence>
190
+ 0038<confidence value="5">]</confidence>
191
+ The polymer beads containing the water/nanoclay droplets may also be used in an extrusion process described below to form polymeric insulative foam products such as those described herein. For example, if the nanoclay/water containing polymer beads are added to a polymer matrix, the polymer beads may be co-foamed by using blowing agents such as pentane, N2, <confidence value="5">C</confidence>
192
+ O2, HCFC, HFC, or H<confidence value="5">C</confidence>
193
+ into final extruded foam products. The nanoclay/water containing polymer beads may expand after the extrusion process. </p>
194
+ <p id="p-41" num="41">[0039] In a second embodiment of the invention, a modifier-free nanoclay is encapsulated in a super-absorbent material which can then be used in an expanding or extruding process to form a foam product. Any one (or more) of the modifier-free nanoclays <boundary-data type="header">-10-</boundary-data>
195
+ <page-break num="11"/>
196
+ <boundary-data type="header">Attorney Docket No. 25647A</boundary-data>
197
+ described above is dispersed in a carrier, preferably water, with agitation, such as by mechanical stirring, to form a uniform or substantially uniform mixture of the carrier and the modifier-free nanoclay. The carrier/nanoclay mixture may be encapsulated in a super- absorbant material to form a modifier-free, nanoclay-containing compound suitable for extrusion or expansion foaming process. Non-limiting examples of super-absorbant materials include crosslinked sodium polyacrylates such as LiquiBlock 2G-1<confidence value="5">0</confidence>
198
+ (available from ETI), Alcosperse 747-D, 729-D, and 724-D (available from Alco Chemical), Stockha<confidence value="5">n</confidence>
199
+ sen SAB <part-num-ref name="modifier-free, nanoclay-containing compound suitable for extrusion or expansion foaming process. Non-limiting examples of super-absorbant materials include crosslinked sodium polyacrylates such as LiquiBlock 2G-10 (available from ETI), Alcosperse 747-D, 729-D, and 724-D (available from Alco Chemical), Stockhansen SAB">800</part-num-ref>
200
+ fine (available from Allied Colloid), and fine inorganic chemicals such as fumed or precipitated silica (Cab-<confidence value="5">O</confidence>
201
+ -Si<confidence value="4">l</confidence>
202
+ M-<confidence value="5">5</confidence>
203
+ P and Aerosil-200 available from Cabot), zeolite, carbon black (Black Pearls <part-num-ref name="fine (available from Allied Colloid), and fine inorganic chemicals such as fumed or precipitated silica (Cab-O-Sil M-5P and Aerosil-200 available from Cabot), zeolite, carbon black (Black Pearls">2000</part-num-ref>
204
+ available from Cabot), zeolite, and diatomaceous earth. </p>
205
+ <p id="p-42" num="42">
206
+ <confidence value="5">[</confidence>
207
+ 0040<confidence value="5">]</confidence>
208
+ As one example, the modifier-free, nanoclay-containing compound may be used for extrusion into foam products. The extruded foam product may be prepared by any method known to those of skill in the art such as with an extruder (twin or single), a mixer, or a blender. The encapsulated modifier-free, nanoclay, along with any optional polymers and/or additives, are heated to a first temperature sufficient to melt the polymer(s) (i.e., the melt mixing temperature) and mixed to form a melted nanoclay/polymer mixture. A blowing agent may be added to the nanoclay/polymer mixture under a first pressure and under conditions that permit a thorough mixing of the blowing agent and nanoclay/polymer mixture while preventing foaming of the mixture. A variety of blowing agents such as HCFC, HFC, <confidence value="865">CO2</confidence>
209
+ , H<confidence value="66">20</confidence>
210
+ , inert gases, and hydrocarbons may be used, either singly or in combination. Once the blowing agent is incorporated and thoroughly mixed with the nanoclay/polymer mixture, the resulting composition is typically referred to as a foamable gel. The foamable gel is then cooled to a second temperature (i.e., the die melt temperature), and is extruded into a zone of reduced pressure (a second pressure) resulting in foaming of the gel and formation of the desired extruded foam product. The nanoclay may behave as a surfactant to stabilize the growth of the bubbles at the interface of gas and polymer during the foaming process. </p>
211
+ <p id="p-43" num="43">[0041<confidence value="5">]</confidence>
212
+ Alternatively, the encapsulated modifier-free nanoclay may be formed into a foam by an expanding process in which the encapsulated emulsified water/modifier-free <boundary-data type="header">-11-</boundary-data>
213
+ <page-break num="12"/>
214
+ <boundary-data type="header">Attorney Docket No. 25647A</boundary-data>
215
+ nanoclay is expanded such as by hot air, hot oil, supersaturated water steam, or microwave heating in a mold having a desired shape. </p>
216
+ <p id="p-44" num="44">[0042<confidence value="5">]</confidence>
217
+ Non-limiting optional additives that may be incorporated into the extruded foam product include plasticizers, flame retardant chemicals, pigments, elastomers, extrusion aids, antioxidants, fillers, antistatic agents, cell size enlargement agents, and/or UV absorbers. </p>
218
+ <p id="p-45" num="45">[0043] In a third embodiment of the invention, the modifier-free nanoclay is directly injected into the polymer during an extrusion foaming process such as is described above. In this embodiment, an injection line for the carrier (e.g., water) separate from the injection line for the blowing agent and polymer matrix may be added on the extrusion line. A separate pump (e.g., a syringe pump) may be utilized to control the amount of the nanoclay/carrier injected into the extruder during foaming. As with the embodiments described above, the nanoclay and carrier may be any one or more of the nanoclays and carriers described herein.</p>
219
+ <p id="p-46" num="46">[0044<confidence value="5">]</confidence>
220
+ This process by directly injecting the nanoclay/carrier suspensions into the extrusion foaming line shortens the residence time of clay in the extruder and thus reduces the chances for re-aggregation of the clay. Well-dispersed clay without re-aggregation demonstrates high nucleation ability and product properties such as barrier resistance, mechanical strength, and flexural and tensile modulus. This direct injection method also reduces or eliminates any potential water loss by evaporation. As a result, an accurate metering can be obtained, which improves foam quality. </p>
221
+ <p id="p-47" num="47">[0045] There are numerous advantages of utilizing modifier-free nanoclays to form foam products. For instance, without a surface modification on the nanoclay, the synthesis of the polymer/clay nanocomposite (e.g., polymer beads or encapsulated nanoclay) is simplified, which reduces the manufacturing costs and increases the speed of the production lines. For example, conventional modified clays contain a specific modifier that limits the surfactants and emulsifiers that may be utilized. On the other hand, in the present invention, a more extensive list of surfactants and emulsifiers may be used to form the polymer/clay nanocomposite and thus the foamed product. In addition, by not surface-modif<confidence value="5">y</confidence>
222
+ ing the clay as in the present invention, more nanoclay can be added to the polymer beads and the clay and the polymer are directly interphased. </p>
223
+ <boundary-data type="header">-12-</boundary-data>
224
+ <boundary-data type="header">Attorney Docket No. 25647A</boundary-data>
225
+ <p id="p-48" num="48">
226
+ <page-break num="13"/>
227
+ [0046<confidence value="5">]</confidence>
228
+ Additionally, the dispersion of the nanoclay in water increases safety and reduces human health concerns because the fluffy nanoclay is either compounded directly into monomer or polymer. In addition, modifier-free nanoclays may act as a nucleation agent for non-polar foaming agents, such as water or ethanol. The weaker interaction between the clay and polymer matrix without clay surface modification may facilitate the orientation of clay, and thus improve the corresponding properties such as barrier resistance, thermal stability, mechanical strength, and wear resistance. Further, the absence of surface modifiers on the nanoclay increases the resistance of foam products formed from the modifier-free nanoclays to fire, such as by reducing the flame spread and dripping. </p>
229
+ <p id="p-49" num="49">[0047<confidence value="5">]</confidence>
230
+ Having generally described this invention, a further understanding can be obtained by reference to certain specific examples illustrated below which are provided for purposes of illustration only and are not intended to be all inclusive or limiting unless otherwise specified. </p>
231
+ <p id="p-50" num="50">[0048] Examples [0049<confidence value="5">]</confidence>
232
+ Example 1: Synthesis of Water-Containin<confidence value="5">g</confidence>
233
+ Polystyrene Nanoclay Composites Via Inverse Emulsion/Suspension Polymerization [0050<confidence value="5">]</confidence>
234
+ The polymerization experiments were performed in a 1000 ml three-neck round flask <part-num-ref name="ml three-neck round flask">10</part-num-ref>
235
+ fitted with an impeller stirrer <part-num-ref name="impeller stirrer">20</part-num-ref>
236
+ propelled by a motor <part-num-ref name="motor">30,</part-num-ref>
237
+ reflux condenser <part-num-ref name="motor 30, reflux condenser">40,</part-num-ref>
238
+ and nitrogen inlet <part-num-ref name="motor 30, reflux condenser 40, and nitrogen inlet">50</part-num-ref>
239
+ as shown in FIG. <confidence value="5">1</confidence>
240
+ . The flask <part-num-ref name="flask">10</part-num-ref>
241
+ was positioned in a warm water bath <part-num-ref name="warm water bath">60.</part-num-ref>
242
+ Styrene with dissolved 2,2'-azobis (isobutyronitrile) (AIBN), be<confidence value="7">n</confidence>
243
+ zoyl peroxide (BPO), and bis(2-ethylhexyl) sulfosuccinate (AOT) in an amount of <part-num-ref name="amount of">10</part-num-ref>
244
+ % by weight based on the emulsified water was stirred at <part-num-ref name="emulsified water was stirred at">350</part-num-ref>
245
+ rpm at <part-num-ref name="rpm at">90</part-num-ref>
246
+ <confidence value="2">°</confidence>
247
+ C under a nitrogen blanket to form a pre- polymerized styrene/polystyrene system. </p>
248
+ <p id="p-51" num="51">[0051] The synthesis reaction was performed in bulk with a conversion of approximately 60% (determined by offline DSC). A water/NaC<confidence value="4">l</confidence>
249
+ mixture for preparing polystyrene beads containing emulsified water/NaC<confidence value="4">I</confidence>
250
+ (control) or a water/clay (Na<confidence value="2">'</confidence>
251
+ MMT)/NaC<confidence value="4">l</confidence>
252
+ mixture for preparing the polymer beads containing myriads of water/nanoclay particles (droplets) having a final clay content of 0.5 - 1.5% by weight of styrene/polystyrene was added to the pre-polymerized styrene/polystyrene system and <boundary-data type="header">-13-</boundary-data>
253
+ <page-break num="14"/>
254
+ <boundary-data type="header">Attorney Docket No. 25647A</boundary-data>
255
+ emulsified by stirring the resulting mixture at <part-num-ref name="resulting mixture at">700</part-num-ref>
256
+ rpm for five minutes. A schematic illustration of the emulsification of the water in the styrene/polystyrene system with the water/clay (Na<confidence value="1">*</confidence>
257
+ MMT)/NaC<confidence value="4">l</confidence>
258
+ mixture is illustrated in FIG. 2a. As depicted in FIG. 2a, the inverse emulsion <part-num-ref name="inverse emulsion">100</part-num-ref>
259
+ contained nanoclay/water particles <part-num-ref name="contained nanoclay/water particles">130</part-num-ref>
260
+ suspended in the styrene/polystyrene system <part-num-ref name="styrene/polystyrene system">70.</part-num-ref>
261
+ The nanoclay/water particles were formed of nanoclay (Na<confidence value="2">+</confidence>
262
+ MMT) <part-num-ref name="nanoclay/water particles were formed of nanoclay (Na+MMT)">80</part-num-ref>
263
+ suspended in an emulsified water phase <part-num-ref name="emulsified water phase">90.</part-num-ref>
264
+ </p>
265
+ <p id="p-52" num="52">
266
+ <confidence value="5">[</confidence>
267
+ 0052<confidence value="5">]</confidence>
268
+ Subsequently, 100 g of the viscous inverse emulsion <part-num-ref name="viscous inverse emulsion">100</part-num-ref>
269
+ was then suspended in water (suspension water, 300g), with the aid of suspension stabilizers hydroxyethylcellulose (HEC) and polyvinyl alcohol (PVA) in an amount of 0.6% (HEC) and 0.005% (PVA). Polymerization was continued for five hours under a nitrogen atmosphere. </p>
270
+ <p id="p-53" num="53">The stirring rate and the temperature were maintained at <part-num-ref name="temperature were maintained at">350</part-num-ref>
271
+ rpm and <part-num-ref name="rpm and">90</part-num-ref>
272
+ <confidence value="2">*</confidence>
273
+ C, respectively. </p>
274
+ <p id="p-54" num="54">Finally, the suspension was cooled to room temperature and spherical products were recovered by rinsing and filtration. A schematic illustration of the suspension polymerization of the styrene/polystyrene droplets containing emulsified water is depicted in FIG. 2b. As shown in FIG. 2b, the suspension water <part-num-ref name="suspension water">110</part-num-ref>
275
+ contained polystyrene beads <part-num-ref name="contained polystyrene beads">120</part-num-ref>
276
+ having therein the water/nanoclay particles <part-num-ref name="water/nanoclay particles">130</part-num-ref>
277
+ (Na<confidence value="2">+</confidence>
278
+ MMT <part-num-ref name="(Na+MMT">80</part-num-ref>
279
+ suspended in the emulsified water phase 90). </p>
280
+ <p id="p-55" num="55">The water/nanoclay particles 130 were suspended in a styrene/polystyrene mixture <part-num-ref name="styrene/polystyrene mixture">140.</part-num-ref>
281
+ </p>
282
+ <p id="p-56" num="56">[0053<confidence value="5">]</confidence>
283
+ The recovered beads with and without Na<confidence value="2">+</confidence>
284
+ MMT were expanded utilizing two different heating mediums: hot air and hot oil bath. The heating temperature was <part-num-ref name="heating temperature was">135</part-num-ref>
285
+ <confidence value="2">°</confidence>
286
+ C in both cases. After exposure to the hot medium for one minute, the expanded beads were quenched by compressed cold air (in the hot air method) or by an ice-water mixture (in the hot oil bath method). The morphology of both the compact (i.e., before expansion) and the expanded beads was examined by a scanning electron microscope (SEM, HITATCHI <confidence value="68">S-</confidence>
287
+ 4300), operated at <part-num-ref name="scanning electron microscope (SEM, HITATCHI S- 4300), operated at">15</part-num-ref>
288
+ K<confidence value="5">V</confidence>
289
+ . Samples were freeze-fractured in liquid nitrogen and the fracture surface was sputter-coated with gold. </p>
290
+ <p id="p-57" num="57">
291
+ <confidence value="5">[</confidence>
292
+ 0054] The distribution of water in the compact beads is shown in FIGS. 3a and 3b. </p>
293
+ <p id="p-58" num="58">FIG. 3a illustrates the polystyrene beads without Na<confidence value="2">+</confidence>
294
+ MMT and FIG. 3b illustrates the polystyrene beads with Na<confidence value="2">+</confidence>
295
+ MMT. Due to the constant AOT/emulsified water ratio for both the water contained polystyrene beads without and without Na<confidence value="1">*</confidence>
296
+ MMT, similar domain size <boundary-data type="header">-14-</boundary-data>
297
+ <page-break num="15"/>
298
+ <boundary-data type="header">Attorney Docket No. 25647A</boundary-data>
299
+ and size distribution were obtained. Most water droplets exhibited a size of <part-num-ref name="size of">5</part-num-ref>
300
+ <confidence value="2">p</confidence>
301
+ m, with several larger droplets of approximately <confidence value="662">10p</confidence>
302
+ m. It was determined that with the incorporation of nanoclay (Na<confidence value="15">*M</confidence>
303
+ MT), the shape of the emulsified water in the beads was more regular compared to those beads that did not contain nanoclay. The uniform dispersion of water droplets leads to a uniform or substantially uniform foam morphology in the final foam products. </p>
304
+ <p id="p-59" num="59">[0055<confidence value="5">]</confidence>
305
+ The foam structures of the expanded polystyrene beads both with and without <confidence value="882">Na+</confidence>
306
+ MMT are shown in Figure 4. FIGS. 4a and 4c illustrate foams prepared by heating the polystyrene beads over an air gun and FIGS. 4b and 4c illustrate foams prepared by heating the polystyrene beads with a hot oil bath. The results are set forth in Table <part-num-ref name="results are set forth in Table">1.</part-num-ref>
307
+ It was determined that a higher expansion ratio of the foam was achieved by heating the polystyrene beads in a hot oil bath. The effect of the modifier-free nanoclay (Na<confidence value="2">+</confidence>
308
+ MMT) on the expansion and thus the final foam structures can also be seen in Figure 4. </p>
309
+ <p id="p-60" num="60">Table 1 Expansion Ratios of Polystyrene Beads With and Without Na<confidence value="2">+</confidence>
310
+ MMT Expansion ratio Polystryrene Beads Polystyrene Beads <confidence value="86">(a</confidence>
311
+ ) Without Na<confidence value="2">+</confidence>
312
+ MMT 0.5% Na<confidence value="2">+</confidence>
313
+ MMT 10% <confidence value="885">H20</confidence>
314
+ <confidence value="588">10%</confidence>
315
+ <confidence value="885">H20</confidence>
316
+ Hot Air gun <part-num-ref name="Expansion Ratios of Polystyrene Beads With and Without Na+MMT Expansion ratio Polystryrene Beads Polystyrene Beads (a) Without Na+MMT 0.5% Na+MMT 10% H20 10% H20 Hot Air gun">(135</part-num-ref>
317
+ <confidence value="2">°</confidence>
318
+ C, <confidence value="2222">lmin</confidence>
319
+ ) 2.2 3.2 Hot Oil Bath <part-num-ref name="°C, lmin) 2.2 3.2 Hot Oil Bath">(135</part-num-ref>
320
+ <confidence value="2">°</confidence>
321
+ C, <confidence value="22225">1min)</confidence>
322
+ 2.95 6.1 [0056<confidence value="5">]</confidence>
323
+ For polystyrene beads containing emulsified water (i.e., beads without <confidence value="882">Na+</confidence>
324
+ MMT), the average expansion ratio was 2.2 when a hot air gun was used to prepare the foam whereas the expansion ratio was 2.95 when the foam was prepared using a hot oil bath. </p>
325
+ <p id="p-61" num="61">For the polystyrene beads containing the water/nanoclay droplets, the increase in the expansion ratio due to the placement in a hot oil bath is more apparent. As shown in Table <part-num-ref name="hot oil bath is more apparent. As shown in Table">1,</part-num-ref>
326
+ compacted beads containing Na<confidence value="266">+MM</confidence>
327
+ T expanded nearly 90% more by the oil bath (6.1) then by hot air (3.2). It is believed that the reason for this difference in expansion may be the different diffusion rate of water in air and in oil. Once exposed to a hot medium (air/oil), a <boundary-data type="header">-15-</boundary-data>
328
+ <page-break num="16"/>
329
+ <boundary-data type="header">Attorney Docket No. 25647A</boundary-data>
330
+ large concentration difference of water inside and outside the beads may lead to the diffusion of water out of the beads, rather than expansion. However, the diffusion rate of water is much slower in the oil. Therefore, more water can be trapped inside the beads and thus result in expansion during the oil heating. </p>
331
+ <p id="p-62" num="62">[0057] As shown in Table 1, beads containing Na<confidence value="2">+</confidence>
332
+ MMT exhibited higher expansion ratios upon heating than beads that did not contain nanoclay. For example, when heated with hot air, the incorporation of 0.5 wt. % nanoclay (based on styrene/polystyrene) lead to an increase of the expansion ratio from 2.2 to 3.2. When beads containing Na<confidence value="2">+</confidence>
333
+ MMT were heated by the hot oil bath, the increase of expansion ratio associated with the nanoclay was more than 100% (i.e., 2.95 vs. 6.1). Before expansion, most of the clay exists in the emulsified water phase (reference numeral <part-num-ref name="emulsified water phase (reference numeral">90</part-num-ref>
334
+ in FIGS. 2a and 2b). During expansion, the nanoclay particles can be pushed against the cell wall of the foam, forming a barrier layer around the cell, which may diminish the loss of water via diffusion. As a result of the trapped water vapor, a higher expansion ratio may be achieved. It is to be noted that with the addition of clay, bimodal foam morphology is achieved (see, Figure 4d), both with cells of <confidence value="662">10p</confidence>
335
+ m and cells of <confidence value="666288">100pm.</confidence>
336
+ </p>
337
+ <p id="p-63" num="63">[0058<confidence value="5">]</confidence>
338
+ In addition, transmission electron microscopy (TEM) was used to characterize the nanoclay morphology in water/polymer phase. FIG. <confidence value="4">S</confidence>
339
+ a depicts layers of MMT along the cell wall of the foam. FIG. <confidence value="4">S</confidence>
340
+ b, a higher magnification (X <part-num-ref name="higher magnification (X">180</part-num-ref>
341
+ K) of the TEM image of FIG. </p>
342
+ <p id="p-64" num="64">
343
+ <confidence value="4">S</confidence>
344
+ a shows good exfoliation of the clay layers for the polystyrene beads. The exfoliated layers of the clay result in an enhancement of the physical properties of nano-polymer composites, such as gas barrier, mechanical strength, and tensile and flexural modulus. </p>
345
+ <p id="p-65" num="65">[0059] Example 2: Extrusion of Polystyrene Foams By Pre-Compounded Water<confidence value="5882">/Na+</confidence>
346
+ MMT With or Without a Su<confidence value="5">p</confidence>
347
+ eraborbent [0060] Table <part-num-ref name="Superaborbent [0060] Table">2</part-num-ref>
348
+ summarizes the experimental trials of four samples, A, B, C, and D. </p>
349
+ <p id="p-66" num="66">Sample A was a control sample, and contained no Na<confidence value="2">+</confidence>
350
+ MMT, polystyrene, or process aids. </p>
351
+ <p id="p-67" num="67">Process aids, such as Emkarate, a low molecular weight diester available from Alco Chemical, were used in Samples B - D to improve the appearance and to control the cell structure of the extruded foam. Compounds B and C were prepared by using a Leistritz twin- <boundary-data type="header">-16-</boundary-data>
352
+ <page-break num="17"/>
353
+ <boundary-data type="header">Attorney Docket No. 25647A</boundary-data>
354
+ screw extruder and then pelletized. Sample D was extruded in the same twin-screw extruder as Samples B and C but with 4% carbon dioxide as a foaming blowing agent. The extruder die temperature was approximately <part-num-ref name="extruder die temperature was approximately">120</part-num-ref>
355
+ <confidence value="2">°</confidence>
356
+ C and the die pressure <confidence value="5">w</confidence>
357
+ as approximately <part-num-ref name="die pressure was approximately">1350</part-num-ref>
358
+ psi. </p>
359
+ <p id="p-68" num="68">Table 2 Extrusion Foaming Components <confidence value="222">(a&gt;</confidence>
360
+ Process Sample Poly<confidence value="566">sty</confidence>
361
+ rene Na<confidence value="2">+</confidence>
362
+ MMT(%) <confidence value="66652">Aidb)</confidence>
363
+ </p>
364
+ <heading id="h-13">
365
+ <confidence value="1222">((%)</confidence>
366
+ </heading>
367
+ <p id="p-69" num="69">A 100 Control sam<confidence value="8">p</confidence>
368
+ le <part-num-ref name="Control sample">
369
+ <confidence value="5">0</confidence>
370
+ </part-num-ref>
371
+ B <part-num-ref name="B">85</part-num-ref>
372
+ <part-num-ref name="">5</part-num-ref>
373
+ <part-num-ref name="">10</part-num-ref>
374
+ C <part-num-ref name="C">85</part-num-ref>
375
+ <part-num-ref name="">10</part-num-ref>
376
+ <part-num-ref name="">5</part-num-ref>
377
+ D <part-num-ref name="D">97</part-num-ref>
378
+ <part-num-ref name="">2</part-num-ref>
379
+ (with half amount of water) <part-num-ref name="(with half amount of water)">1</part-num-ref>
380
+ (a) NOVA NC0038 (a high melt index polystyrene) (b) EMKARATE <part-num-ref name="high melt index polystyrene) (b) EMKARATE">1090</part-num-ref>
381
+ (a low molecular weight diester available from ALCO Chemical) <confidence value="5">[</confidence>
382
+ 0061<confidence value="5">]</confidence>
383
+ To reduce the surfactant usage on the nanoclay surface and to simultaneously obtain a good intercalation or exfoliation structure, untreated Na<confidence value="2">+</confidence>
384
+ MMT nanoclay was dispersed into water in a weight concentration range from 0.25 - 75%, preferably in a weight concentration from <part-num-ref name="weight concentration from">1</part-num-ref>
385
+ - 30%, and most preferably in a weight concentration range of from <part-num-ref name="weight concentration range of from">3</part-num-ref>
386
+ - 8%. The resulting clay/water paste was then compounded into polystyrene by melt compounding. </p>
387
+ <p id="p-70" num="70">[0062] FIG. 6 depicts the X-Ray diffraction (XRD) patterns for Samples A - D set forth in Table <part-num-ref name="- D set forth in Table">2.</part-num-ref>
388
+ It was determined that because peaks were observed with Samples B and C, which have 5% and 10% Na<confidence value="2">+</confidence>
389
+ MMT clay respectively, without water dispersing, clay layer intercalation was not obtained. Sample D, which was pre-dispersed Na<confidence value="2">+</confidence>
390
+ MMT with water, exhibited no peak on the XRD curve, which indicated possible exfoliation. </p>
391
+ <p id="p-71" num="71">[0063] Example 3: Fire Performance Testing [0064] Fire performance tests (e.g., fire resistance) on foamed insulation with modified nanoclays and with modifier-free nanoclays as shown in Table <part-num-ref name="fire resistance) on foamed insulation with modified nanoclays and with modifier-free nanoclays as shown in Table">3</part-num-ref>
392
+ were conducted <boundary-data type="header">-17-</boundary-data>
393
+ <page-break num="18"/>
394
+ <boundary-data type="header">Attorney Docket No. 25647A</boundary-data>
395
+ according to ASTM (oxygen index) and UL (Underwriters Laboratories in Northbrook, IL) small scale horizontal fire test methodology. The apparatus utilized to conduct the experimentation included a 3/8" ferrule laboratory Bunsen burner, two ring stands with adjustable clamps, and a <part-num-ref name="">4</part-num-ref>
396
+ inch X <part-num-ref name="inch X">8</part-num-ref>
397
+ <confidence value="51">/z</confidence>
398
+ inch hardware cloth (three mesh with 8/64" stainless steel wire) with <confidence value="5">%</confidence>
399
+ " to 1" length bent upwards at <part-num-ref name="/z inch hardware cloth (three mesh with 8/64&quot; stainless steel wire) with %&quot; to 1&quot; length bent upwards at">90</part-num-ref>
400
+ degree angle. The sample size utilized for testing was 2" X 6" and <confidence value="266">%'/</confidence>
401
+ " in thickness. To pass the UL small fire test for polystyrene foams, the duration of burning of the specimen should be less than <part-num-ref name="specimen should be less than">20</part-num-ref>
402
+ seconds, and the flame spread should extend less than <part-num-ref name="flame spread should extend less than">60</part-num-ref>
403
+ mm. In addition, the oxygen index for insulation required from ASTM C578 has a minimum of 24% in volume. </p>
404
+ <p id="p-72" num="72">[0065] Na<confidence value="2">+</confidence>
405
+ MMT without modifier and Na<confidence value="2">+</confidence>
406
+ MMT with Closite, a methyl tallow bis-2- hydroxyethyl quaternary ammonia salt modifier commercially available from Southern Clay Products, Inc. were dispersed in water with mechanical stirring. Both the modifier-free <confidence value="882">Na+</confidence>
407
+ MMT and the modified Na<confidence value="2">+</confidence>
408
+ MMT were extruded into foam boards with <part-num-ref name="modified Na+MMT were extruded into foam boards with">1</part-num-ref>
409
+ wt % of microencapsulated hexabromocyclododecane (HBCD) fire retardant using carbon dioxide as a blowing agent, such as described in copending U.S. Patent Publication No. 2004/0051191 to Loh, et al., which is expressly incorporated by reference it its entirety. As described in U.S. </p>
410
+ <p id="p-73" num="73">Patent Publication No. 204/0051191, flame retardants such as HBCD, ethylene bis(pentabromodiphenyl), chloronaphthalene, perchloropentadecane, and/or functional additives (e.g., smoke suppressants, infrared attenuation agents, and the like) can be incorporated as a core material into a microcapsule. The primary shell material is typically includes one or more polymeric materials such as melamine formaldehyde, polyurethane, polyester, polyethylene, polypropylene, polystyrene, and the like.</p>
411
+ <p id="p-74" num="74">[0066] Two group of the insulation samples were tested: one sample group containing <confidence value="882">Na+</confidence>
412
+ MMT polymer composite foam boards without a modifier (Samples <part-num-ref name="modifier (Samples">1</part-num-ref>
413
+ - <part-num-ref name="-">3)</part-num-ref>
414
+ and one sample group containing Na<confidence value="2">+</confidence>
415
+ MMT polymer composite foam boards with a modifier (Samples <part-num-ref name="modifier (Samples">4</part-num-ref>
416
+ - 6). A summary of the test results are shown in Table <part-num-ref name="test results are shown in Table">3.</part-num-ref>
417
+ </p>
418
+ <boundary-data type="header">-18-</boundary-data>
419
+ <boundary-data type="header">Attorney Docket No. 25647A</boundary-data>
420
+ <p id="p-75" num="75">
421
+ <page-break num="19"/>
422
+ Table 3 Summary of Oxygen and Small Scale Fire Testing Small Scale Fire Test Oxygen Time Flame Spread <confidence value="6666">Drip</confidence>
423
+ Index (sec <confidence value="882">mm)</confidence>
424
+ <confidence value="888">(%)</confidence>
425
+ Without modifier Sample <part-num-ref name="Summary of Oxygen and Small Scale Fire Testing Small Scale Fire Test Oxygen Time Flame Spread Drip Index (sec mm) (%) Without modifier Sample">1</part-num-ref>
426
+ with <confidence value="66">1%</confidence>
427
+ <confidence value="58">Na</confidence>
428
+ MMT <part-num-ref name="with 1% NaMMT">19</part-num-ref>
429
+ <part-num-ref name="">38</part-num-ref>
430
+ Flame drip <part-num-ref name="Flame drip">24</part-num-ref>
431
+ <confidence value="6">(</confidence>
432
+ with <part-num-ref name="(with">
433
+ <confidence value="6">3</confidence>
434
+ </part-num-ref>
435
+ <part-num-ref name="">
436
+ <confidence value="2">2</confidence>
437
+ </part-num-ref>
438
+ <confidence value="5">a</confidence>
439
+ <confidence value="6666">MMT)</confidence>
440
+ <part-num-ref name="MMT)">14</part-num-ref>
441
+ <part-num-ref name="">33</part-num-ref>
442
+ Partial dri<confidence value="8">p</confidence>
443
+ <part-num-ref name="Partial drip">25</part-num-ref>
444
+ <confidence value="6">(</confidence>
445
+ with <confidence value="62">5%</confidence>
446
+ <confidence value="25">/a</confidence>
447
+ <confidence value="6666">MMT)</confidence>
448
+ <part-num-ref name="(with 5% /a MMT)">15</part-num-ref>
449
+ <part-num-ref name="">34</part-num-ref>
450
+ No drip <part-num-ref name="No drip">24</part-num-ref>
451
+ With modifier Sample <part-num-ref name="With modifier Sample">4</part-num-ref>
452
+ (Na<confidence value="2">+</confidence>
453
+ MMT with 1% <part-num-ref name="(Na+MMT with 1%">30</part-num-ref>
454
+ <part-num-ref name="">47</part-num-ref>
455
+ Flame drip <part-num-ref name="Flame drip">22</part-num-ref>
456
+ <confidence value="2222222221">Closite"a)</confidence>
457
+ 20A) Sample <part-num-ref name="Closite&quot;a) 20A) Sample">5</part-num-ref>
458
+ (Na<confidence value="28">+M</confidence>
459
+ MT with 3% &gt;60 <part-num-ref name="(Na+MMT with 3% &gt;60">85</part-num-ref>
460
+ Partial drip <part-num-ref name="Partial drip">17</part-num-ref>
461
+ Closite 20A<confidence value="5">)</confidence>
462
+ Sample <part-num-ref name="Closite 20A) Sample">6</part-num-ref>
463
+ (Na<confidence value="2">+</confidence>
464
+ MMT with 5% &gt;60 &gt;100 No drip <part-num-ref name="(Na+MMT with 5% &gt;60 &gt;100 No drip">18</part-num-ref>
465
+ Closite 20A<confidence value="5">)</confidence>
466
+ (a) Closite 20A is a methyl tallow bis-2-hydroxyethyl quaternary ammonia salt modifier commercially available from Southern Clay Products, Inc. </p>
467
+ <p id="p-76" num="76">
468
+ <confidence value="5">[</confidence>
469
+ 0067<confidence value="5">]</confidence>
470
+ The polystyrene/nanoclay compounds containing modifiers all burned vigorously even with the presence of the 1% hexabromocyclododecane (HBCD) fire retardant, and failed to pass the <confidence value="5">U</confidence>
471
+ L small scale fire test and oxygen index as required by ASTM C578. In contrast, the modifier-free polystyrene/nanoclay composites containing 1% HBCD fire retardant demonstrated fire extinction consistent with the standard product without nanoclay, and passed both the small scale fire test and the oxygen index (%) ASTM C578 standard. Both of the Na<confidence value="2">+</confidence>
472
+ MMT polymer composite foam boards (with and without modifier) demonstrated char forming during burning. This char formation clearly demonstrates that nanoclay changes the burning characteristics of extruded polystyrene foams from the conventional thermoplastic melt dripping to the solid char formation of the nanoclay <boundary-data type="header">-19-</boundary-data>
473
+ <page-break num="20"/>
474
+ <boundary-data type="header">Attorney Docket No. 25647A</boundary-data>
475
+ extruded foams. Foam boards having a weight percentage of greater than <part-num-ref name="weight percentage of greater than">3</part-num-ref>
476
+ weight percent of the Na<confidence value="1">+</confidence>
477
+ MMT (Samples <part-num-ref name="Na+MMT (Samples">3</part-num-ref>
478
+ and <part-num-ref name="and">6)</part-num-ref>
479
+ were drip-free. It was also demonstrated that the elimination of the organic modifier typically used to improve processability (e.g., Closite 20A)<confidence value="5">,</confidence>
480
+ improved greatly reduced flame extension, which assists in maintaining the flames in a limited area. </p>
481
+ <p id="p-77" num="77">[0068<confidence value="5">]</confidence>
482
+ The invention of this application has been described above both generically and with regard to specific embodiments. Although the invention has been set forth in what is believed to be the preferred embodiments, a wide variety of alternatives known to those of skill in the art can be selected within the generic disclosure. The invention is not otherwise limited, except for the recitation of the claims set forth below. </p>
483
+ <heading id="h-14">
484
+ <confidence value="2">-</confidence>
485
+ </heading>
486
+ <boundary-data type="header">-20-<confidence value="2">-</confidence>
487
+ </boundary-data>
488
+ </description>
489
+ </us-patent-application>
490
+