Add files using upload-large-folder tool
Browse filesThis view is limited to 50 files because it contains too many changes. See raw diff
- prior_art/10490787.xml +30 -0
- prior_art/10527400.xml +0 -0
- prior_art/10537135.xml +56 -0
- prior_art/10543240.xml +921 -0
- prior_art/10548403.xml +61 -0
- prior_art/10549668.xml +25 -0
- prior_art/10557944.xml +780 -0
- prior_art/10576240.xml +1 -0
- prior_art/10578122.xml +22 -0
- prior_art/10580070.xml +28 -0
- prior_art/10581014.xml +41 -0
- prior_art/10582824.xml +0 -0
- prior_art/10596060.xml +191 -0
- prior_art/10596434.xml +516 -0
- prior_art/10864207.xml +0 -0
- prior_art/10879592.xml +1 -0
- prior_art/10902593.xml +36 -0
- prior_art/10936465.xml +0 -0
- prior_art/10967748.xml +27 -0
- prior_art/10992435.xml +33 -0
- prior_art/11011356.xml +436 -0
- prior_art/11012471.xml +682 -0
- prior_art/11013197.xml +0 -0
- prior_art/11035978.xml +25 -0
- prior_art/11072226.xml +400 -0
- prior_art/11110436.xml +40 -0
- prior_art/11114645.xml +654 -0
- prior_art/11120095.xml +52 -0
- prior_art/11130541.xml +0 -0
- prior_art/11140288.xml +372 -0
- prior_art/11142943.xml +44 -0
- prior_art/11170622.xml +46 -0
- prior_art/11171065.xml +0 -0
- prior_art/11173839.xml +0 -0
- prior_art/11179528.xml +0 -0
- prior_art/11213129.xml +276 -0
- prior_art/11213396.xml +1457 -0
- prior_art/11217024.xml +0 -0
- prior_art/11226590.xml +0 -0
- prior_art/11233981.xml +33 -0
- prior_art/11236126.xml +260 -0
- prior_art/11238937.xml +163 -0
- prior_art/11242115.xml +69 -0
- prior_art/11242678.xml +35 -0
- prior_art/11247464.xml +0 -0
- prior_art/11262122.xml +26 -0
- prior_art/11264679.xml +25 -0
- prior_art/11270795.xml +68 -0
- prior_art/11275739.xml +891 -0
- prior_art/11276709.xml +25 -0
prior_art/10490787.xml
ADDED
|
@@ -0,0 +1,30 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>10490787</doc-number>
|
| 8 |
+
<date>2011-10-20</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">Atty Dkt No. 8325-0027 Client No. S27-US <confidence value="8">1</confidence>
|
| 14 |
+
</p>
|
| 15 |
+
<heading id="h-1">PATENT</heading>
|
| 16 |
+
<heading id="h-2">AMENDMENTS TO THE SPECIFICATION</heading>
|
| 17 |
+
<p id="p-2" num="2">Please amend the paragraph beginning on page <part-num-ref name="paragraph beginning on page">71,</part-num-ref>
|
| 18 |
+
line <part-num-ref name="paragraph beginning on page 71, line">30</part-num-ref>
|
| 19 |
+
as follows: </p>
|
| 20 |
+
<p id="p-3" num="3">Recent studies in which its expression was modulated in ES cells have shown that levels of OCT4 expression ranging between 50 and 150% of normal levels are sufficient for self-renewal of the stem cell population and maintenance of totipotency. Lower levels of OCT4 expression (50% or less of normal<confidence value="5">)</confidence>
|
| 21 |
+
result in differentiation into trophectoderm <confidence value="22222222">endedenn</confidence>
|
| 22 |
+
, while OCT4 levels above 150% of normal result in differentiation into endoderm and mesoderm. See<confidence value="5">,</confidence>
|
| 23 |
+
Niwa et al. <part-num-ref name="stem cell population and maintenance of totipotency. Lower levels of OCT4 expression (50% or less of normal) result in differentiation into trophectoderm endedenn, while OCT4 levels above 150% of normal result in differentiation into endoderm and mesoderm. See, Niwa et al.">(2000)</part-num-ref>
|
| 24 |
+
Nature Genetics 24:372-376. </p>
|
| 25 |
+
<p id="p-4" num="4">
|
| 26 |
+
<confidence value="8">2</confidence>
|
| 27 |
+
</p>
|
| 28 |
+
</description>
|
| 29 |
+
</us-patent-application>
|
| 30 |
+
|
prior_art/10527400.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
prior_art/10537135.xml
ADDED
|
@@ -0,0 +1,56 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>10537135</doc-number>
|
| 8 |
+
<date>2010-04-26</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">04/26/201<confidence value="8">0</confidence>
|
| 14 |
+
<confidence value="5">M</confidence>
|
| 15 |
+
ON 18:12 <confidence value="4">F</confidence>
|
| 16 |
+
AX 7243875021 Philips Healthcare RECE<confidence value="42">VM</confidence>
|
| 17 |
+
<confidence value="686266">02/016</confidence>
|
| 18 |
+
</p>
|
| 19 |
+
<heading id="h-1">CENTRAL FAX CENTER</heading>
|
| 20 |
+
<p id="p-2" num="2">APR <confidence value="58">26</confidence>
|
| 21 |
+
<part-num-ref name="">2010</part-num-ref>
|
| 22 |
+
</p>
|
| 23 |
+
<heading id="h-2">PATENT</heading>
|
| 24 |
+
<p id="p-3" num="3">App<confidence value="45">L.</confidence>
|
| 25 |
+
No. 10/537,135 Docket No.: US<confidence value="4">0</confidence>
|
| 26 |
+
20476US Response to Of<confidence value="66">fi</confidence>
|
| 27 |
+
ce Action of January 26, 2010 <confidence value="5">C</confidence>
|
| 28 |
+
ustomer No. <part-num-ref name="Customer No.">24737</part-num-ref>
|
| 29 |
+
Amendment to the S<confidence value="5">p</confidence>
|
| 30 |
+
ecification: </p>
|
| 31 |
+
<p id="p-4" num="4">Please delete the paragraph on page <part-num-ref name="paragraph on page">6,</part-num-ref>
|
| 32 |
+
lines 17-22 and replace the same with the following amended paragraph: </p>
|
| 33 |
+
<p id="p-5" num="5">The monitor 2 may also have a greater range of motion <part-num-ref name="greater range of motion">9</part-num-ref>
|
| 34 |
+
in 3-dimensional space. In another case, the monitor <part-num-ref name="monitor">2</part-num-ref>
|
| 35 |
+
may even be 'held toward' the user, but back off as the user nears, allowing complete hands free operation of the screen. The optimal viewing pose for the monitor may comprise distance and orientation (typically 'straight ahead', zero degrees, 0.5 meters). Range of motion <part-num-ref name="monitor may comprise distance and orientation (typically 'straight ahead', zero degrees, 0.5 meters). Range of motion">9</part-num-ref>
|
| 36 |
+
must be tested to ensure that the monitor has a limited range of motion, not affecting the workspace. </p>
|
| 37 |
+
<p id="p-6" num="6">Page 2 of <part-num-ref name="of">
|
| 38 |
+
<confidence value="88">12</confidence>
|
| 39 |
+
</part-num-ref>
|
| 40 |
+
PAGE <part-num-ref name="PAGE">2<confidence value="5">1</confidence>
|
| 41 |
+
16 </part-num-ref>
|
| 42 |
+
<confidence value="2">*</confidence>
|
| 43 |
+
RCVD AT 4<confidence value="286">r26</confidence>
|
| 44 |
+
12010 6:12:09 PM <confidence value="5">(</confidence>
|
| 45 |
+
Eastern Day<confidence value="66">li</confidence>
|
| 46 |
+
ght Time<confidence value="52">]*</confidence>
|
| 47 |
+
SVR:USPTO<confidence value="585884888">.EPXRP-51</confidence>
|
| 48 |
+
<confidence value="25">*D</confidence>
|
| 49 |
+
NIS:2738300 <confidence value="4">*</confidence>
|
| 50 |
+
CSID:7243875021 <confidence value="5">"</confidence>
|
| 51 |
+
DURATION (mm<confidence value="24">-s</confidence>
|
| 52 |
+
s):02<confidence value="588">-44</confidence>
|
| 53 |
+
</p>
|
| 54 |
+
</description>
|
| 55 |
+
</us-patent-application>
|
| 56 |
+
|
prior_art/10543240.xml
ADDED
|
@@ -0,0 +1,921 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>10543240</doc-number>
|
| 8 |
+
<date>2005-07-22</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="5156665566">Pl036P0010</confidence>
|
| 15 |
+
<confidence value="666">543</confidence>
|
| 16 |
+
<part-num-ref name="">
|
| 17 |
+
<confidence value="5">2</confidence>
|
| 18 |
+
</part-num-ref>
|
| 19 |
+
<part-num-ref name="">
|
| 20 |
+
<confidence value="2">4</confidence>
|
| 21 |
+
</part-num-ref>
|
| 22 |
+
<part-num-ref name="">
|
| 23 |
+
<confidence value="6">1</confidence>
|
| 24 |
+
</part-num-ref>
|
| 25 |
+
<part-num-ref name="">
|
| 26 |
+
<confidence value="1188">3017</confidence>
|
| 27 |
+
</part-num-ref>
|
| 28 |
+
Rec'd PCT/PTO <part-num-ref name="Rec'd PCT/PTO">2</part-num-ref>
|
| 29 |
+
<part-num-ref name="">2</part-num-ref>
|
| 30 |
+
J<confidence value="88">UL</confidence>
|
| 31 |
+
<part-num-ref name="JUL">
|
| 32 |
+
<confidence value="5">2</confidence>
|
| 33 |
+
005 </part-num-ref>
|
| 34 |
+
</p>
|
| 35 |
+
<heading id="h-1">STORAGE STABLE FROZEN LACTIC ACID BACTERIA CULTURE</heading>
|
| 36 |
+
<heading id="h-2">FIELD OF THE INVENTION:</heading>
|
| 37 |
+
<p id="p-2" num="2">The present invention relates to a storage stable frozen lactic acid bacteria (LAB) culture <boundary-data type="line-number">5 </boundary-data>
|
| 38 |
+
that comprises LAB that are that are able to utilize sucrose, has a weight of at least <part-num-ref name="weight of at least">50</part-num-ref>
|
| 39 |
+
g fro- zen material and a content of viable bacteria of at least <part-num-ref name="content of viable bacteria of at least">
|
| 40 |
+
<confidence value="666">109</confidence>
|
| 41 |
+
</part-num-ref>
|
| 42 |
+
colony forming units (CFU) per g frozen material. </p>
|
| 43 |
+
<heading id="h-3">BACKGROUND OF THE INVENTION:</heading>
|
| 44 |
+
<p id="p-3" num="3">
|
| 45 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 46 |
+
Microorganisms are involved in the manufacture of food and feed products including most dairy products. Thus, bacterial cultures, in particular cultures of bacteria that are generally classified as lactic acid bacteria are essential in the making of all fermented milk products, cheese and butter. Cultures of such bacteria may be referred to as starter cultures and they impart specific features to various dairy products by performing a number of functions. </p>
|
| 47 |
+
<p id="p-4" num="4">
|
| 48 |
+
<boundary-data type="line-number">
|
| 49 |
+
<confidence value="88">15</confidence>
|
| 50 |
+
</boundary-data>
|
| 51 |
+
Commercial dairy starter cultures are generally composed of lactic acid and citric acid fer- menting lactic acid bacteria. In the present context, the expression "lactic acid bacteria" des- ignates a group of Gram positive, catalase negative, non-motile, microaerophilic or anaero- bic bacteria which ferment sugar with the production of acids including lactic acid as the <boundary-data type="line-number">20 </boundary-data>
|
| 52 |
+
predominantly produced acid, acetic acid, formic acid and propionic acid. The industrially most useful lactic acid bacteria are found among Lactococcus species, Streptococcus spe- cies, Enterococcus species, Lactobacillus species, Leuconostoc species and Pediococcus species. </p>
|
| 53 |
+
<p id="p-5" num="5">
|
| 54 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 55 |
+
Commonly used dairy starter culture strains of lactic acid bacteria are generally divided into mesophilic organisms having optimum growth temperatures at about 30<confidence value="2">"</confidence>
|
| 56 |
+
C and thermophilic organisms having optimum growth temperatures in the range of about <part-num-ref name="range of about">40</part-num-ref>
|
| 57 |
+
to about 45<confidence value="288">*C.</confidence>
|
| 58 |
+
<confidence value="2">-</confidence>
|
| 59 |
+
Typical organisms belonging to the mesophilic group include Lactococcus lactis subsp. lac- tis, Lactococcus lactis subsp. <confidence value="22222222">cremoris</confidence>
|
| 60 |
+
, Leuconostoc mesenteroides subsp. cremoris, Pedi<confidence value="68">o-</confidence>
|
| 61 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 62 |
+
coccus pentosaceus, Lactococcus lactis subsp. lactis biovar. <confidence value="2222222222222">diacetylactis</confidence>
|
| 63 |
+
and Lactobacillus casei subsp. casei. Thermophilic lactic acid bacterial species include as examples Strepto- <boundary-data type="header">293-002-USP</boundary-data>
|
| 64 |
+
<page-break num="2"/>
|
| 65 |
+
<boundary-data type="header">
|
| 66 |
+
<confidence value="856">P10</confidence>
|
| 67 |
+
36P<confidence value="555">C00</confidence>
|
| 68 |
+
</boundary-data>
|
| 69 |
+
<boundary-data type="header">
|
| 70 |
+
<confidence value="8">2</confidence>
|
| 71 |
+
</boundary-data>
|
| 72 |
+
coccus thermophilus, Enterococcus faecium, Lactobacillus lactis, Lactobacillus helveticus, Lactobacillus delbrueckii subsp. bulgaricus and Lactobacillus acidophilus. </p>
|
| 73 |
+
<p id="p-6" num="6">The dairy starter cultures are also classified according to their specific species composition <boundary-data type="line-number">5 </boundary-data>
|
| 74 |
+
and preferred industrial use. A pure starter culture comprises only a single specie and a mixed culture comprises two or more different species. Commercial relevant mesophilic mixed cultures include: </p>
|
| 75 |
+
<p id="p-7" num="7">
|
| 76 |
+
<confidence value="86">"O</confidence>
|
| 77 |
+
-culture" comprising Lactococcus lactis subsp. lactis and Lactococcus lactis subsp. cremoris. </p>
|
| 78 |
+
<p id="p-8" num="8">
|
| 79 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 80 |
+
"D-culture" comprising Lactococcus lactis subsp. lactis, Lactococcus lactis subsp. </p>
|
| 81 |
+
<p id="p-9" num="9">cremoris and Lactococcus lactis subsp. lactis biovar. diacetylactis.</p>
|
| 82 |
+
<p id="p-10" num="10">"L-culture" comprising Lactococcus lactis subsp. lactis, Lactococcus lactis subsp.</p>
|
| 83 |
+
<p id="p-11" num="11">cremoris and Leuconostoc mesenteroides subsp. cremoris.</p>
|
| 84 |
+
<p id="p-12" num="12">"LD-culture" comprising Lactococcus lactis subsp. lactis, Lactococcus lactis subsp.</p>
|
| 85 |
+
<p id="p-13" num="13">
|
| 86 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 87 |
+
cremoris, Lactococcus lactis subsp. lactis biovar. diacetylactis and Leuconostoc mesenteroides subsp.<confidence value="4">.</confidence>
|
| 88 |
+
cremoris. </p>
|
| 89 |
+
<p id="p-14" num="14">An <confidence value="5">O</confidence>
|
| 90 |
+
-culture is used to make cheese without holes (Cheddar, Cheshire, Feta). A D-culture is used to make butter. A L-culture is used to cheese with only small holes (cottage cheese) <boundary-data type="line-number">20 </boundary-data>
|
| 91 |
+
and curdled milk products with low C<confidence value="5">O</confidence>
|
| 92 |
+
2-production. A LD-culture is used to make cheese with normal hole sizes, curdled milk products (junket) and sour butter. Commercially, a LD- culture is currently one of the most used mixed cultures. </p>
|
| 93 |
+
<p id="p-15" num="15">Commercial relevant thermophilic mixed cultures include:</p>
|
| 94 |
+
<p id="p-16" num="16">
|
| 95 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 96 |
+
"Yoghurt culture" comprising Streptococcus thermophilus and Lactobacillus del- brueckii subsp. bulgaricus. </p>
|
| 97 |
+
<p id="p-17" num="17">"Thermophil cheese culture" comprising Streptococcus thermophilus and Lactoba- cillus helveticus.</p>
|
| 98 |
+
<p id="p-18" num="18">
|
| 99 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 100 |
+
An Yoghurt culture is used to make yoghurt and special Italian cheeses. An Thermophil cheese culture is used to make emmentaler cheese and special Italian cheeses. </p>
|
| 101 |
+
<boundary-data type="header">293-002-USP</boundary-data>
|
| 102 |
+
<boundary-data type="header">
|
| 103 |
+
<confidence value="814">PI0</confidence>
|
| 104 |
+
36P<confidence value="555">C00</confidence>
|
| 105 |
+
</boundary-data>
|
| 106 |
+
<boundary-data type="header">
|
| 107 |
+
<confidence value="8">3</confidence>
|
| 108 |
+
</boundary-data>
|
| 109 |
+
<p id="p-19" num="19">
|
| 110 |
+
<page-break num="3"/>
|
| 111 |
+
Commercial starter cultures may commonly be distributed as frozen cultures. Highly con- centrated frozen cultures are commercially very interesting since such cultures can be inocu- lated directly into milk without intermediate transfer. In others words, such highly concen- trated frozen cultures comprises so many bacteria that dairies do not have to make in-house <boundary-data type="line-number">5 </boundary-data>
|
| 112 |
+
bulk starters. A "bulk starter" is defined herein as a starter culture propagated at the dairy plant for inoculation into milk. Highly concentrated cultures may be referred to as direct vat set (DVS)-cultures. </p>
|
| 113 |
+
<p id="p-20" num="20">In order to comprise sufficient bacteria a commercial relevant highly concentrated frozen <boundary-data type="line-number">10 </boundary-data>
|
| 114 |
+
culture generally has a weight of at least <part-num-ref name="weight of at least">50</part-num-ref>
|
| 115 |
+
g and a content of viable bacteria of at least <part-num-ref name="content of viable bacteria of at least">
|
| 116 |
+
<confidence value="666">109</confidence>
|
| 117 |
+
</part-num-ref>
|
| 118 |
+
colony forming units (CFU) per g. </p>
|
| 119 |
+
<p id="p-21" num="21">Another presentation of commercial highly concentrated DVS-starter cultures is as freeze- dried or lyophilized cultures in the form of a powder. In this form, the starter can be shipped <boundary-data type="line-number">15 </boundary-data>
|
| 120 |
+
without refrigeration. </p>
|
| 121 |
+
<p id="p-22" num="22">The article of F.J. Chavarri et al (Biotechnology letters, vol 10, 1, 11- 16 (1988), "Cryopro- tective agents for frozen concentrated starters from non-bitter Streptococcus Lactis strains") describes that the storage viability of a frozen pure Streptococcus lactis culture could be im- <boundary-data type="line-number">20 </boundary-data>
|
| 122 |
+
proved by addition of 5% lactose or 5% sucrose. The lactose or sucrose worked as cryopro- tective agents. Streptococcus lactis is a former name of Lactococcus lactis subsp. lactis. </p>
|
| 123 |
+
<p id="p-23" num="23">Similarly, the article of R. <confidence value="2222222">Circoba</confidence>
|
| 124 |
+
et al (Eur Food Res Technol <part-num-ref name="article of R. Circoba et al (Eur Food Res Technol">(2000)</part-num-ref>
|
| 125 |
+
<part-num-ref name="">211,</part-num-ref>
|
| 126 |
+
<part-num-ref name="211,">433</part-num-ref>
|
| 127 |
+
- <part-num-ref name="-">437,</part-num-ref>
|
| 128 |
+
"In- fluence of cryoprotectants on the viability and acidif<confidence value="8">y</confidence>
|
| 129 |
+
ing activity of frozen and freeze-dried <boundary-data type="line-number">25 </boundary-data>
|
| 130 |
+
cells of the novel starter strain Lactococcus lactis subsp. lactis CECT 5180") describes that the storage viability of a frozen pure Lactococcus lactis subsp. lactis culture could be i<confidence value="68">m-</confidence>
|
| 131 |
+
proved by addition of different cryoprotective agents such as sugars (lactose, sucrose and trehalose), glutamic acid and gelatin. </p>
|
| 132 |
+
<p id="p-24" num="24">
|
| 133 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 134 |
+
The present inventors are not aware of any commercial available highly concentrated frozen cultures that comprise significant amounts of cryoprotective agents. </p>
|
| 135 |
+
<boundary-data type="header">293-002-USP</boundary-data>
|
| 136 |
+
<boundary-data type="header">
|
| 137 |
+
<confidence value="85">P1</confidence>
|
| 138 |
+
036<confidence value="8666">PC00</confidence>
|
| 139 |
+
</boundary-data>
|
| 140 |
+
<boundary-data type="header">
|
| 141 |
+
<confidence value="8">4</confidence>
|
| 142 |
+
</boundary-data>
|
| 143 |
+
<p id="p-25" num="25">
|
| 144 |
+
<page-break num="4"/>
|
| 145 |
+
EP259739 describes different suitable cryoprotective agents for freeze-dried cultures. A freeze-dried culture in the form of a powder is physically significant different from a frozen culture among others due to that a freeze-dried powder comprises significant less water as compared to a frozen culture. Accordingly, it is submitted that the skilled person would <boundary-data type="line-number">5 </boundary-data>
|
| 146 |
+
prima facie not consider that a specific cryoprotective agent described as useful for a freeze- dried culture would also be similar useful in a frozen culture. </p>
|
| 147 |
+
<p id="p-26" num="26">
|
| 148 |
+
<confidence value="86">W0</confidence>
|
| 149 |
+
00/39281 (Chr. Hansen A<confidence value="5">/</confidence>
|
| 150 |
+
S) describes a liquid starter culture stabilized by different cryoprotective agents. Page <part-num-ref name="liquid starter culture stabilized by different cryoprotective agents. Page">5,</part-num-ref>
|
| 151 |
+
lines 5-7 reads "the expression "liquid starter culture" relates <boundary-data type="line-number">10 </boundary-data>
|
| 152 |
+
to non-frozen liquid starter cultures having a liquid phase, e. g. an aqueous phase, content that is typically in the range of 50-90% by weight". Consequently, the liquid culture de- scribed in W<confidence value="566">O00</confidence>
|
| 153 |
+
/39281 is a non-frozen culture. </p>
|
| 154 |
+
<heading id="h-4">SUMMARY OF THE INVENTION:</heading>
|
| 155 |
+
<p id="p-27" num="27">
|
| 156 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 157 |
+
Prior to the present invention, the present inventors believed that there were no significant storage stability problems in relation to commercially relevant highly concentrated frozen lactic acid bacteria cultures. As said above, the present inventors are not aware of any com- mercial available highly concentrated frozen cultures that comprise significant amounts of cryoprotective agents. </p>
|
| 158 |
+
<p id="p-28" num="28">
|
| 159 |
+
<boundary-data type="line-number">
|
| 160 |
+
<confidence value="88">20</confidence>
|
| 161 |
+
</boundary-data>
|
| 162 |
+
Prior to the present invention, stability studies had been made starting from commercial highly concentrated lactic acid bacteria cultures that already had been frozen for 2-3 month. </p>
|
| 163 |
+
<p id="p-29" num="29">For instance, studies were made on 2-3 month old frozen LD-cultures. These studies showed no significant degradation of activity of the LD-cultures over a period of one year at <boundary-data type="line-number">25 </boundary-data>
|
| 164 |
+
temperature below -45<confidence value="2">*</confidence>
|
| 165 |
+
C. Consequently, it was believed that commercial relevant LD- cultures did not have significant storage stability problems. </p>
|
| 166 |
+
<p id="p-30" num="30">In order to analyze the stability during the first weeks of frozen storage different <confidence value="5">O</confidence>
|
| 167 |
+
-cultures were analyzed right from the first day of frozen storage. They did not show any significant <boundary-data type="line-number">30 </boundary-data>
|
| 168 |
+
reduction of activity neither during the first weeks nor during the next <part-num-ref name="next">12</part-num-ref>
|
| 169 |
+
month. Accord- ingly, these data essentially confirmed that there should be no storage stability problems in relation to commercially relevant highly concentrated frozen cultures. </p>
|
| 170 |
+
<boundary-data type="header">293-002-USP</boundary-data>
|
| 171 |
+
<boundary-data type="header">
|
| 172 |
+
<confidence value="856">P10</confidence>
|
| 173 |
+
36P<confidence value="566">C00</confidence>
|
| 174 |
+
</boundary-data>
|
| 175 |
+
<boundary-data type="header">
|
| 176 |
+
<confidence value="8">5</confidence>
|
| 177 |
+
</boundary-data>
|
| 178 |
+
<p id="p-31" num="31">
|
| 179 |
+
<page-break num="5"/>
|
| 180 |
+
Despite this, the present inventors continued to investigate stability issues of different com- mercial relevant frozen cultures and after a number of studies they identified that for in- stance frozen LD-cultures had a significant loss of activity within the first 1-3 weeks of fro- zen storage. After these weeks the further loss of activity was relatively insignificant in line <boundary-data type="line-number">5 </boundary-data>
|
| 181 |
+
with the prior known results described above. </p>
|
| 182 |
+
<p id="p-32" num="32">In summary, the work of the present inventors has identified hitherto unrecognized storage stability problems in relation to some types of commercial relevant highly concentrated fro- zen lactic acid bacteria cultures, such as e.g. commercial available frozen LD-cultures.</p>
|
| 183 |
+
<p id="p-33" num="33">
|
| 184 |
+
<boundary-data type="line-number">
|
| 185 |
+
<confidence value="88">10</confidence>
|
| 186 |
+
</boundary-data>
|
| 187 |
+
Once having identified this problem, the present inventors could start to try to solve the problem. As described herein they solved this by addition of cryoprotective agents to the<confidence value="5">.</confidence>
|
| 188 |
+
</p>
|
| 189 |
+
<p id="p-34" num="34">relevant highly concentrated frozen cultures<confidence value="5">.</confidence>
|
| 190 |
+
</p>
|
| 191 |
+
<p id="p-35" num="35">
|
| 192 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 193 |
+
As said above an <confidence value="5">O</confidence>
|
| 194 |
+
-culture comprises Lactococcus lactis subsp. lactis and Lactococcus lac- tis subsp. <confidence value="22222222">cremoris</confidence>
|
| 195 |
+
and a LD-culture comprises Lactococcus lactis subsp. lactis, Lactococ- cus lactis subsp. cremoris, Lactococcus lactis subsp. lactis biovar. diacetylactis and Leu- conostoc mesenteroides subsp. <confidence value="22222222">cremoris</confidence>
|
| 196 |
+
. </p>
|
| 197 |
+
<p id="p-36" num="36">
|
| 198 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 199 |
+
The Leuconostoc mesenteroides subsp. cremoris present in the LD-culture is able to utilize sucrose. The <confidence value="5">O</confidence>
|
| 200 |
+
-culture does not comprise bacteria that are able to utilize sucrose. </p>
|
| 201 |
+
<p id="p-37" num="37">Consequently, without being limited to theory, it is believed that the herein identified stabil- ity problems relate to commercial relevant highly frozen cultures that comprise bacteria that <boundary-data type="line-number">25 </boundary-data>
|
| 202 |
+
are able to utilize sucrose. </p>
|
| 203 |
+
<p id="p-38" num="38">As said above, in order to comprise sufficient bacteria a commercial relevant highly concen- trated frozen culture generally has a weight of at least <part-num-ref name="weight of at least">50</part-num-ref>
|
| 204 |
+
g and a content of viable bacteria of at least <part-num-ref name="content of viable bacteria of at least">10<confidence value="5">9</confidence>
|
| 205 |
+
</part-num-ref>
|
| 206 |
+
colony forming units (CF<confidence value="5">U</confidence>
|
| 207 |
+
) per g. The pure Lactococcus lactis subsp. lactis <boundary-data type="line-number">30 </boundary-data>
|
| 208 |
+
cultures described in the articles of F.J. Chavarri et al and R. Carboba et al (see above) are in the present context not considered commercial relevant highly concentrated frozen cul- <boundary-data type="header">
|
| 209 |
+
<confidence value="2">-</confidence>
|
| 210 |
+
293-002-U<confidence value="68">SP</confidence>
|
| 211 |
+
</boundary-data>
|
| 212 |
+
<page-break num="6"/>
|
| 213 |
+
<boundary-data type="header">
|
| 214 |
+
<confidence value="88">P1</confidence>
|
| 215 |
+
036P<confidence value="588">C00</confidence>
|
| 216 |
+
</boundary-data>
|
| 217 |
+
<boundary-data type="header">
|
| 218 |
+
<confidence value="8">6</confidence>
|
| 219 |
+
</boundary-data>
|
| 220 |
+
<confidence value="22222">tures</confidence>
|
| 221 |
+
since they are made on must smaller scale and comprises significant less grams of fro- zen culture. </p>
|
| 222 |
+
<p id="p-39" num="39">Accordingly, a first aspect of the invention relates to a frozen lactic acid bacteria (LAB) cul- <boundary-data type="line-number">5 </boundary-data>
|
| 223 |
+
ture that comprises LAB that are that are able to utilize sucrose, has a weight of at least <part-num-ref name="weight of at least">50</part-num-ref>
|
| 224 |
+
g frozen material and a content of viable bacteria of at least <part-num-ref name="content of viable bacteria of at least">
|
| 225 |
+
<confidence value="5">1</confidence>
|
| 226 |
+
09 </part-num-ref>
|
| 227 |
+
colony forming units (CFU) per g frozen material, characterized in that the frozen culture comprises from 0.5% to 80% of a cryoprotective agent measured as w/w of the frozen material. </p>
|
| 228 |
+
<p id="p-40" num="40">
|
| 229 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 230 |
+
The cryoprotective agent should preferably be added to the viable bacteria before they are frozen. </p>
|
| 231 |
+
<p id="p-41" num="41">Accordingly, in a second aspect the invention relates to a method for making a frozen lactic acid bacteria (LAB) culture that comprises LAB that are that are able to utilize sucrose, has <boundary-data type="line-number">15 </boundary-data>
|
| 232 |
+
a weight of at least <part-num-ref name="weight of at least">50</part-num-ref>
|
| 233 |
+
g frozen material and a content of viable bacteria of at least <part-num-ref name="content of viable bacteria of at least">
|
| 234 |
+
<confidence value="666">109</confidence>
|
| 235 |
+
</part-num-ref>
|
| 236 |
+
col- ony forming units (CFU) per g frozen material comprising following steps: </p>
|
| 237 |
+
<p id="p-42" num="42">(i) adding a cryoprotective agent to viable bacteria to get at least <part-num-ref name="cryoprotective agent to viable bacteria to get at least">50</part-num-ref>
|
| 238 |
+
g.of material with a content of viable bacteria of at least <part-num-ref name="content of viable bacteria of at least">10<confidence value="5">9</confidence>
|
| 239 |
+
</part-num-ref>
|
| 240 |
+
colony forming units (CFU) per g <confidence value="6">-</confidence>
|
| 241 |
+
material and comprising the cryoprotective agent in an amount from 0.5% to <boundary-data type="line-number">20 </boundary-data>
|
| 242 |
+
80%. measured as w/w of the material, (ii) freezing the material to get frozen material, and (iii) packing the frozen material in a suitable way. </p>
|
| 243 |
+
<p id="p-43" num="43">A third aspect of the invention relates to a frozen lactic acid bacteria (LAB) culture obtain<confidence value="5">-</confidence>
|
| 244 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 245 |
+
able by the method for making a frozen lactic acid bacteria (LAB) culture of the second as- pects of the invention. </p>
|
| 246 |
+
<p id="p-44" num="44">A fourth aspect of the invention relates to use of the frozen lactic acid bacteria (LAB) cul- ture as described above in a process for making a food or feed product.</p>
|
| 247 |
+
<p id="p-45" num="45">
|
| 248 |
+
<confidence value="88">30</confidence>
|
| 249 |
+
<boundary-data type="header">293-002-USP</boundary-data>
|
| 250 |
+
<page-break num="7"/>
|
| 251 |
+
<boundary-data type="header">
|
| 252 |
+
<confidence value="814">PI0</confidence>
|
| 253 |
+
36PC<confidence value="66">00</confidence>
|
| 254 |
+
</boundary-data>
|
| 255 |
+
<boundary-data type="header">
|
| 256 |
+
<confidence value="8">7</confidence>
|
| 257 |
+
</boundary-data>
|
| 258 |
+
</p>
|
| 259 |
+
<heading id="h-5">DEFINITIONS:</heading>
|
| 260 |
+
<p id="p-46" num="46">Prior to a discussion of the detailed embodiments of the invention is provided a definition of specific terms related to the main aspects of the invention.</p>
|
| 261 |
+
<p id="p-47" num="47">
|
| 262 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 263 |
+
The term "LAB that are that are able to utilize sucrose" denotes LAB that are able to fer- ment the sugar sucrose with the production of acids. </p>
|
| 264 |
+
<p id="p-48" num="48">The term "material" of the culture denotes the relevant substances of the culture including both the viable bacteria and cryoprotective agent. Possible packing is not included. Conse- <boundary-data type="line-number">10 </boundary-data>
|
| 265 |
+
quently, the weight of the material of the culture is not including the weight of possible packing. </p>
|
| 266 |
+
<p id="p-49" num="49">The term "packing" should be understood broadly. It denotes that the frozen lactic acid bac- teria (LAB) culture should be packed in order could to be provided to the user. It may be <boundary-data type="line-number">15 </boundary-data>
|
| 267 |
+
packed in a bottle, a tetra-pack, etc. </p>
|
| 268 |
+
<p id="p-50" num="50">The term "a cryoprotective agent" denotes a substance that is able to improve the storage stability of the frozen culture. In the present context it may be a single specific cryoprotec- tive agents or it may be two or more different agents. Accordingly, the w/w percentage of <boundary-data type="line-number">20 </boundary-data>
|
| 269 |
+
the cryoprotective agent(s) within the culture material should be understood as the sum of the amount of cryoprotective agent(s). A preferred way to determine whether a substance is a cryoprotective agent that is able to improve the storage stability of the frozen culture is to spilt a culture, as described herein, in two samples, add a specified amount of the cryopro- tective agent to one of them, freezing both of them and measure the milk acidifying activity <boundary-data type="line-number">25 </boundary-data>
|
| 270 |
+
of the cultures on the same day as freezing and periodically up to one year under frozen storage. If the culture with cryoprotective agent has improved milk acidifying activity seen over the storage period the substance is a cryoprotective agent. A suitable milk acidifying activity assay is given in working examples herein. </p>
|
| 271 |
+
<p id="p-51" num="51">30 Embodiments of the present invention is described below, by way of examples only <boundary-data type="header">293-002-U<confidence value="68">SP</confidence>
|
| 272 |
+
</boundary-data>
|
| 273 |
+
<page-break num="8"/>
|
| 274 |
+
<boundary-data type="header">
|
| 275 |
+
<confidence value="88">P1</confidence>
|
| 276 |
+
036PC00 </boundary-data>
|
| 277 |
+
<boundary-data type="header">
|
| 278 |
+
<confidence value="8">8</confidence>
|
| 279 |
+
</boundary-data>
|
| 280 |
+
</p>
|
| 281 |
+
<heading id="h-6">DRAWINGS</heading>
|
| 282 |
+
<p id="p-52" num="52">Figure 1 to 4: Stability profiles for F-DVS of Fl DaN & CH N<confidence value="66">11</confidence>
|
| 283 |
+
. For further details see working Example <part-num-ref name="to 4: Stability profiles for F-DVS of Fl DaN & CH N11. For further details see working Example">1.</part-num-ref>
|
| 284 |
+
</p>
|
| 285 |
+
<p id="p-53" num="53">
|
| 286 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 287 |
+
Figure 5 to 10: Stability profiles for F-DVS of Fl DaN, CH N<confidence value="66">11</confidence>
|
| 288 |
+
& CH N19. For further de- tails see working Example <part-num-ref name="to 10: Stability profiles for F-DVS of Fl DaN, CH N11 & CH N19. For further de- tails see working Example">2.</part-num-ref>
|
| 289 |
+
</p>
|
| 290 |
+
<p id="p-54" num="54">Figure 11: Stability profiles for R603. For further details see working Example 3.</p>
|
| 291 |
+
<heading id="h-7">DETAILED DESCRIPTION OF THE INVENTION:</heading>
|
| 292 |
+
<p id="p-55" num="55">
|
| 293 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 294 |
+
A frozen lactic acid bacteria (LAB) culture The term "mixed lactic acid bacteria (LAB) culture" denotes a mixed culture that comprises two or more different LAB species. The term a "pure lactic acid bacteria (LAB) culture" denotes a pure culture that comprises only a single LAB species specie. </p>
|
| 295 |
+
<p id="p-56" num="56">
|
| 296 |
+
<boundary-data type="line-number">
|
| 297 |
+
<confidence value="88">15</confidence>
|
| 298 |
+
</boundary-data>
|
| 299 |
+
The culture as described herein may be a mesophilic culture consisting of mesophilic bacte- ria having optimum growth temperatures at about 30<confidence value="288">°C.</confidence>
|
| 300 |
+
</p>
|
| 301 |
+
<p id="p-57" num="57">The culture as described herein comprises LAB that are that are able to utilize sucrose. The <boundary-data type="line-number">20 </boundary-data>
|
| 302 |
+
Leuconostoc mesenteroides subsp. cremoris is able to utilize sucrose. Among others, it is present in a L-culture and a LD-culture. </p>
|
| 303 |
+
<p id="p-58" num="58">Consequently, in a preferred embodiment the frozen culture is a L-culture or more prefera- bly a LD-culture. A L-culture and a LD-culture are examples of mesophilic cultures. Fur- <boundary-data type="line-number">25 </boundary-data>
|
| 304 |
+
ther they are mixed cultures. Consequently, a culture as described herein is preferably a mixed culture, more preferably a mesophilic mixed culture. </p>
|
| 305 |
+
<p id="p-59" num="59">A L-culture comprises Lactococcus <confidence value="222222">lactis</confidence>
|
| 306 |
+
subsp. <confidence value="222222">lactis</confidence>
|
| 307 |
+
, Lactococcus <confidence value="222222">lactis</confidence>
|
| 308 |
+
subsp. cremoris and Leuconostoc mesenteroides subsp. cremoris. </p>
|
| 309 |
+
<p id="p-60" num="60">
|
| 310 |
+
<confidence value="88">30</confidence>
|
| 311 |
+
<boundary-data type="header">293-002-USP</boundary-data>
|
| 312 |
+
<page-break num="9"/>
|
| 313 |
+
<boundary-data type="header">
|
| 314 |
+
<confidence value="814">PI0</confidence>
|
| 315 |
+
36P<confidence value="566">C00</confidence>
|
| 316 |
+
</boundary-data>
|
| 317 |
+
<boundary-data type="header">
|
| 318 |
+
<confidence value="8">9</confidence>
|
| 319 |
+
</boundary-data>
|
| 320 |
+
A LD-culture comprises Lactococcus <confidence value="222222">lactis</confidence>
|
| 321 |
+
subsp. lactis, Lactococcus lactis subsp. cremo- ris, Lactococcus lactis subsp. lactis biovar. diacetylactis and Leuconostoc mesenteroides subsp. cremoris. </p>
|
| 322 |
+
<p id="p-61" num="61">
|
| 323 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 324 |
+
The specific amount of the individual bacterial species may vary in accordance with the specific required use. The skilled person is aware of this and capable of determining the pre- ferred mixed culture composition according to the required needs. </p>
|
| 325 |
+
<p id="p-62" num="62">For instance, if aroma is required a relatively high percentage of the aroma making bacteria <boundary-data type="line-number">10 </boundary-data>
|
| 326 |
+
Lactococcus lactis subsp. lactis biovar. diacetylactis and Leuconostoc mesenteroides subsp. </p>
|
| 327 |
+
<p id="p-63" num="63">cremoris could be preferred.</p>
|
| 328 |
+
<p id="p-64" num="64">A preferred LD-culture comprises:</p>
|
| 329 |
+
<p id="p-65" num="65">Lactococcus lactis subsp. lactis, 60 - <part-num-ref name="-">95</part-num-ref>
|
| 330 |
+
%, Lactococcus lactis subsp. cremoris preferably <part-num-ref name="%, Lactococcus lactis subsp. cremoris preferably">70</part-num-ref>
|
| 331 |
+
- 90% Lactococcus lactis subsp. lactis biovar. diacetylactis, <part-num-ref name="- 90% Lactococcus lactis subsp. lactis biovar. diacetylactis,">5</part-num-ref>
|
| 332 |
+
- <part-num-ref name="-">40</part-num-ref>
|
| 333 |
+
%, pre<confidence value="88">f-</confidence>
|
| 334 |
+
Leuconostoc mesenteroides subsp. cremoris erably <part-num-ref name="%, pref- Leuconostoc mesenteroides subsp. cremoris erably">10</part-num-ref>
|
| 335 |
+
to <part-num-ref name="to">30</part-num-ref>
|
| 336 |
+
<boundary-data type="line-number">
|
| 337 |
+
<confidence value="86">15</confidence>
|
| 338 |
+
</boundary-data>
|
| 339 |
+
Within the ranges above, it is preferred to have from 0.25 to 6% of Leuconostoc mesenter- oides subsp. cremoris and from <part-num-ref name="ranges above, it is preferred to have from 0.25 to 6% of Leuconostoc mesenter- oides subsp. cremoris and from">7</part-num-ref>
|
| 340 |
+
to 30% of Lactococcus lactis subsp. lactis biovar. diacety- lactis. </p>
|
| 341 |
+
<p id="p-66" num="66">
|
| 342 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 343 |
+
Of course the total percentage sum of the <part-num-ref name="">4</part-num-ref>
|
| 344 |
+
different LAB specifies cannot exceed 100%. </p>
|
| 345 |
+
<p id="p-67" num="67">However, it may be less than 100% if other bacteria than the <part-num-ref name="">4</part-num-ref>
|
| 346 |
+
mentioned ones are present in the LD-culture. Working examples <part-num-ref name="LD-culture. Working examples">1</part-num-ref>
|
| 347 |
+
and <part-num-ref name="and">2</part-num-ref>
|
| 348 |
+
herein provides examples of stabilized LD- cultures. </p>
|
| 349 |
+
<p id="p-68" num="68">
|
| 350 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 351 |
+
The culture as described herein may be a thermophilic culture consisting of thermophilic bacteria having optimum growth temperatures in the range of about <part-num-ref name="range of about">40</part-num-ref>
|
| 352 |
+
to about 45<confidence value="288">"C.</confidence>
|
| 353 |
+
</p>
|
| 354 |
+
<boundary-data type="header">293-002-USP</boundary-data>
|
| 355 |
+
<boundary-data type="header">
|
| 356 |
+
<confidence value="856">P10</confidence>
|
| 357 |
+
36P<confidence value="555">C00</confidence>
|
| 358 |
+
</boundary-data>
|
| 359 |
+
<boundary-data type="header">
|
| 360 |
+
<confidence value="88">10</confidence>
|
| 361 |
+
</boundary-data>
|
| 362 |
+
<p id="p-69" num="69">
|
| 363 |
+
<page-break num="10"/>
|
| 364 |
+
The culture as described herein comprises LAB that are that are able to utilize sucrose. The thermophilic Lactobacillus acidophilus is able to utilize sucrose. Accordingly, in a preferred embodiment the frozen culture is a culture comprising Lactobacillus acidophilus, preferably <boundary-data type="line-number">5 </boundary-data>
|
| 365 |
+
a pure Lactobacillus acidophilus culture. Working example <part-num-ref name="pure Lactobacillus acidophilus culture. Working example">4</part-num-ref>
|
| 366 |
+
herein gives an example of a stabilized pure Lactobacillus acidophilus culture. </p>
|
| 367 |
+
<p id="p-70" num="70">The thermophilic Streptococcus thermophilus is able to utilize sucrose. Accordingly, in a preferred embodiment the frozen culture is a mixed <boundary-data type="line-number">10 </boundary-data>
|
| 368 |
+
"Yoghurt culture" comprising Streptococcus thermophilus and Lactobacillus del- brueckii subsp. bulgaricus; or "Thermophil cheese culture" comprising Streptococcus thermophilus and Lactoba- cillus helveticus. </p>
|
| 369 |
+
<p id="p-71" num="71">
|
| 370 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 371 |
+
Highly concentrated frozen lactic acid bacteria cultures The frozen cultures as described herein are<confidence value="5">,</confidence>
|
| 372 |
+
what in the food industry may be termed, highly concentrated frozen lactic acid bacteria cultures. In order to comprise sufficient bacteria such cultures should be relatively big (have a sufficient weight) combined with a relatively high concentration of viable bacteria. It is obvious that if relatively more bacteria is required <boundary-data type="line-number">20 </boundary-data>
|
| 373 |
+
the weight and/or the concentration of viable bacteria should be increased. </p>
|
| 374 |
+
<p id="p-72" num="72">Preferably, a frozen lactic acid bacteria (LAB) culture as described herein has a weight of at least <part-num-ref name="weight of at least">100</part-num-ref>
|
| 375 |
+
g frozen material, more preferably a weight of at least <part-num-ref name="weight of at least">250</part-num-ref>
|
| 376 |
+
g frozen material, even more preferably a weight of at least <part-num-ref name="weight of at least">500</part-num-ref>
|
| 377 |
+
g frozen material and most preferably a weight of at <boundary-data type="line-number">25 </boundary-data>
|
| 378 |
+
least <part-num-ref name="weight of at least">900</part-num-ref>
|
| 379 |
+
g frozen material. Preferably, the weight of the frozen material is less than <part-num-ref name="frozen material is less than">500</part-num-ref>
|
| 380 |
+
kg. </p>
|
| 381 |
+
<p id="p-73" num="73">Preferably, a frozen lactic acid bacteria (LAB) culture as described herein has a content of viable bacteria of at least 5x109 colony forming units (CF<confidence value="66">U)</confidence>
|
| 382 |
+
per g frozen material, more preferably a content of viable bacteria of at least <part-num-ref name="content of viable bacteria of at least">1010</part-num-ref>
|
| 383 |
+
colony forming units (CF<confidence value="5">U</confidence>
|
| 384 |
+
) per g fro- <boundary-data type="line-number">30 </boundary-data>
|
| 385 |
+
zen material, and most preferably a content of viable bacteria of at least 2x<confidence value="881">10'</confidence>
|
| 386 |
+
0 colony form- ing units (CF<confidence value="5">U</confidence>
|
| 387 |
+
) per g frozen material. </p>
|
| 388 |
+
<boundary-data type="header">293-002-U<confidence value="68">SP</confidence>
|
| 389 |
+
</boundary-data>
|
| 390 |
+
<boundary-data type="header">
|
| 391 |
+
<confidence value="856">P10</confidence>
|
| 392 |
+
36PC<confidence value="66">00</confidence>
|
| 393 |
+
</boundary-data>
|
| 394 |
+
<boundary-data type="header">
|
| 395 |
+
<confidence value="88">11</confidence>
|
| 396 |
+
</boundary-data>
|
| 397 |
+
<p id="p-74" num="74">
|
| 398 |
+
<page-break num="11"/>
|
| 399 |
+
Fermentation and suitable fermentations media for LAB are known in <confidence value="66">th</confidence>
|
| 400 |
+
e art and the skilled person is capable of selecting a suitable media and fermentation conditions in relation to the specific LAB. Suitable media and fermentations are given in the working example section herein. </p>
|
| 401 |
+
<p id="p-75" num="75">
|
| 402 |
+
<boundary-data type="line-number">
|
| 403 |
+
<confidence value="8">5</confidence>
|
| 404 |
+
</boundary-data>
|
| 405 |
+
In order to get sufficient amount of bacteria, it is in the present context preferred to make a relatively large-scale fermentation in suitable big fermentation tanks. Fermentation tanks of at least <part-num-ref name="relatively large-scale fermentation in suitable big fermentation tanks. Fermentation tanks of at least">50</part-num-ref>
|
| 406 |
+
<part-num-ref name="">1,</part-num-ref>
|
| 407 |
+
preferably at least <part-num-ref name="1, preferably at least">90</part-num-ref>
|
| 408 |
+
<part-num-ref name="">
|
| 409 |
+
<confidence value="5">1</confidence>
|
| 410 |
+
</part-num-ref>
|
| 411 |
+
or bigger are preferred. </p>
|
| 412 |
+
<p id="p-76" num="76">
|
| 413 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 414 |
+
After a suitable fermentation, the viable bacteria are preferably isolated by removal of the liquid (<confidence value="22222222222">supernatant</confidence>
|
| 415 |
+
) of the fermentation media (e.g. by centrifugation). The isolated viable bacteria may be termed the isolated biomass. The isolated viable bacteria shall preferably have a content of viable bacteria of at least <part-num-ref name="content of viable bacteria of at least">
|
| 416 |
+
<confidence value="666">109</confidence>
|
| 417 |
+
</part-num-ref>
|
| 418 |
+
colony forming units (CF<confidence value="66">U)</confidence>
|
| 419 |
+
per g or ml. </p>
|
| 420 |
+
<p id="p-77" num="77">
|
| 421 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 422 |
+
The frozen culture may be packaged is a suitable way in order to be provided to the user. </p>
|
| 423 |
+
<p id="p-78" num="78">Preferably the frozen culture is stored at a temperature from -18<confidence value="2">*</confidence>
|
| 424 |
+
C to -60<confidence value="2">*</confidence>
|
| 425 |
+
C, more prefera- bly from -<confidence value="682">18"</confidence>
|
| 426 |
+
C to -50<confidence value="2">*</confidence>
|
| 427 |
+
C. The frozen culture may be stored at a temperature from -1<confidence value="82">8"</confidence>
|
| 428 |
+
C to -25<confidence value="2">"</confidence>
|
| 429 |
+
C. The freezing of the culture shall preferably be done rapidly e.g. by freezing in liquid <boundary-data type="line-number">20 </boundary-data>
|
| 430 |
+
nitrogen. </p>
|
| 431 |
+
<p id="p-79" num="79">
|
| 432 |
+
<confidence value="22222222222222">Cryoprotective</confidence>
|
| 433 |
+
a<confidence value="8">g</confidence>
|
| 434 |
+
ent The cryoprotective agent may preferably be selected from proteins, protein hydrolysates and amino acids. Preferred suitable examples of these include the ones selected from the group <boundary-data type="line-number">25 </boundary-data>
|
| 435 |
+
consisting of Glutamic acid, Lysine, Na-glutamate, Na-caseinate, Malt extract, Skimmed milk powder, Whey powder, Yeast extract, Gluten, Collagen, Gelatin, Elastin, Keratin, and Albumins. </p>
|
| 436 |
+
<p id="p-80" num="80">More preferably the cryoprotective agent is a carbonhydrate. Preferred suitable examples of <boundary-data type="line-number">30 </boundary-data>
|
| 437 |
+
these include the ones selected from the group consisting Pentoses (eg. Ribose, Xylose), Hexoses (eg. fructose, mannose, Sorbose), Disaccharides (eg. Sucrose, Trehalose, Meli- biose, Lactulose), Oligosaccharides (eg. Raffmose), Oligo<confidence value="66">fr</confidence>
|
| 438 |
+
utoses (eg. Actilight, Fribro- <boundary-data type="header">293-002-USP</boundary-data>
|
| 439 |
+
<page-break num="12"/>
|
| 440 |
+
<boundary-data type="header">
|
| 441 |
+
<confidence value="814">PI0</confidence>
|
| 442 |
+
36P<confidence value="566">C00</confidence>
|
| 443 |
+
</boundary-data>
|
| 444 |
+
<boundary-data type="header">
|
| 445 |
+
<confidence value="88">12</confidence>
|
| 446 |
+
</boundary-data>
|
| 447 |
+
loses), Polysaccharides (eg. Maltodextrins, Xanthan Gum, Pectin, Alginate, Microcrystal- line cellulose, Dextran, PEG), and Sugar alcohols (Sorbitol, Manitol). </p>
|
| 448 |
+
<p id="p-81" num="81">The preferred carbohydrate is a disaccharide preferably Trehalose and more preferably Su- <boundary-data type="line-number">
|
| 449 |
+
<confidence value="6">5</confidence>
|
| 450 |
+
</boundary-data>
|
| 451 |
+
<confidence value="7">r</confidence>
|
| 452 |
+
ose. </p>
|
| 453 |
+
<p id="p-82" num="82">A preferred mixture of cryoprotective agents is a disaccharide (preferably sucrose) plus a polysaccharide (preferably maltodextrin). Example <part-num-ref name="polysaccharide (preferably maltodextrin). Example">4</part-num-ref>
|
| 454 |
+
shows a thermophilic Lactobacillus acidophilus culture stabilized with a mixture of sucrose and maltodextrin. Accordingly, for <boundary-data type="line-number">10 </boundary-data>
|
| 455 |
+
a culture comprising Lactobacillus acidophilus it is preferred to use a mixture of a disaccha<confidence value="5">-</confidence>
|
| 456 |
+
ride (preferably sucrose) and a polysaccharide (preferably maltodextrin) as cryoprotective agents. </p>
|
| 457 |
+
<p id="p-83" num="83">Preferably the frozen culture comprises from 2% to 70% of a cryoprotective agent measured <boundary-data type="line-number">15 </boundary-data>
|
| 458 |
+
as w/w of the frozen material, more preferably from 3% to 50% of a cryoprotective agent measured as w/w of the frozen material, even more preferably from 4% to 40% of a cryo- protective agent measured as w/w of the frozen material and most preferably from 4% to 10% of a cryoprotective agent measured as w/w of the frozen material. </p>
|
| 459 |
+
<p id="p-84" num="84">
|
| 460 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 461 |
+
The addition of the cryoprotective agent to the, after fermentation, isolated viable bacteria (biomass) may be done by mixing solid cryoprotective agent with the biomass for e.g. <part-num-ref name="">30</part-num-ref>
|
| 462 |
+
minutes at a suitable temperature. If the cryoprotective agent is e.g. sucrose a suitable tem- perature may be room temperature. Alternatively a sterile solution of the cryoprotective agent may be mixed with the biomass. For sucrose suitable sterile solutions may be made <confidence value="2">-</confidence>
|
| 463 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 464 |
+
from a 50% (w/w) sucrose solution. For trehalose suitable sterile solutions may be made from a 40% (w/w) solution. </p>
|
| 465 |
+
<p id="p-85" num="85">Use of the frozen lactic acid bacteria (LAB) culture A frozen lactic acid bacteria (LAB) culture as described herein may be used in a process for <part-num-ref name="process for">30</part-num-ref>
|
| 466 |
+
making a food or feed product according to the art. </p>
|
| 467 |
+
<boundary-data type="header">293-002-USP</boundary-data>
|
| 468 |
+
<boundary-data type="header">
|
| 469 |
+
<confidence value="88">P1</confidence>
|
| 470 |
+
036PC00 </boundary-data>
|
| 471 |
+
<boundary-data type="header">
|
| 472 |
+
<confidence value="88">13</confidence>
|
| 473 |
+
</boundary-data>
|
| 474 |
+
<p id="p-86" num="86">
|
| 475 |
+
<page-break num="13"/>
|
| 476 |
+
A L-culture is preferably used to make cheese with only small holes (cottage cheese) and curdled milk products with low <confidence value="665">CO2</confidence>
|
| 477 |
+
-production. </p>
|
| 478 |
+
<p id="p-87" num="87">A LD-culture is preferably used to make cheese with normal hole sizes, curdled milk prod- <boundary-data type="line-number">
|
| 479 |
+
<confidence value="5">5</confidence>
|
| 480 |
+
</boundary-data>
|
| 481 |
+
ucts (junket) and sour butter. </p>
|
| 482 |
+
<heading id="h-8">EXAMPLES:</heading>
|
| 483 |
+
<p id="p-88" num="88">Materials and methods <boundary-data type="line-number">10 </boundary-data>
|
| 484 |
+
Cultures: </p>
|
| 485 |
+
<p id="p-89" num="89">Fl DaN, CH N 11 and CH N19 (all commercially available frozen LD-cultures, Chr. Hansen A/S<confidence value="5">,</confidence>
|
| 486 |
+
Denmark). </p>
|
| 487 |
+
<p id="p-90" num="90">R-603 (commercially available frozen <confidence value="5">O</confidence>
|
| 488 |
+
-culture, Chr. Hansen A/S, Denmark). </p>
|
| 489 |
+
<p id="p-91" num="91">La-<confidence value="5">5</confidence>
|
| 490 |
+
(commercially available frozen Lactobacillus acidophilus culture, Chr. Hansen A/S, <boundary-data type="line-number">15 </boundary-data>
|
| 491 |
+
Denmark). </p>
|
| 492 |
+
<p id="p-92" num="92">Fermentation media and fermentation conditions:</p>
|
| 493 |
+
<p id="p-93" num="93">Medium composition for LD and <confidence value="5">O</confidence>
|
| 494 |
+
-cultures: </p>
|
| 495 |
+
<p id="p-94" num="94">The fermentation medium had the following composition: Casein peptone, <part-num-ref name="following composition: Casein peptone,">30</part-num-ref>
|
| 496 |
+
g/l; Prima- <boundary-data type="line-number">20 </boundary-data>
|
| 497 |
+
tone, <part-num-ref name="g/l; Prima- tone,">30</part-num-ref>
|
| 498 |
+
g<confidence value="55">/l</confidence>
|
| 499 |
+
; soy peptone, <part-num-ref name="g/l; soy peptone,">30</part-num-ref>
|
| 500 |
+
g<confidence value="55">/l</confidence>
|
| 501 |
+
; yeast peptone, <part-num-ref name="g/l; yeast peptone,">15</part-num-ref>
|
| 502 |
+
g<confidence value="55">/l</confidence>
|
| 503 |
+
; MgSO4, 1,5 g<confidence value="55">/l</confidence>
|
| 504 |
+
; Na-ascorbate, <part-num-ref name="g/l; MgSO4, 1,5 g/l; Na-ascorbate,">3</part-num-ref>
|
| 505 |
+
g/<confidence value="68">l;</confidence>
|
| 506 |
+
</p>
|
| 507 |
+
<p id="p-95" num="95">and lactose 50 g/<confidence value="68">1.</confidence>
|
| 508 |
+
</p>
|
| 509 |
+
<p id="p-96" num="96">The medium was sterilised by <confidence value="5">U</confidence>
|
| 510 |
+
HT-treatment. The finished medium had a pH of 6,5. </p>
|
| 511 |
+
<p id="p-97" num="97">Fermentation condition for LD and <confidence value="6">O</confidence>
|
| 512 |
+
-cultures: </p>
|
| 513 |
+
<p id="p-98" num="98">
|
| 514 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 515 |
+
The fermentation was performed in a <part-num-ref name="">100</part-num-ref>
|
| 516 |
+
<part-num-ref name="">
|
| 517 |
+
<confidence value="5">1</confidence>
|
| 518 |
+
</part-num-ref>
|
| 519 |
+
fermentation tank at 30<confidence value="2">"</confidence>
|
| 520 |
+
C, stirred at <part-num-ref name="fermentation tank at 30"C, stirred at">50</part-num-ref>
|
| 521 |
+
rpm. <part-num-ref name="rpm.">1</part-num-ref>
|
| 522 |
+
<confidence value="6">%</confidence>
|
| 523 |
+
of the culture mentioned above was used as inoculum. The anaerobic fermentation was run with nitrogen in the headspace and a pressure of about <part-num-ref name="pressure of about">2</part-num-ref>
|
| 524 |
+
bar. The cultures were allowed to acidify to pH 6.2 . The pH was subsequently maintained at 6,2 by controlled addition of <confidence value="5">1</confidence>
|
| 525 |
+
3,4 <confidence value="8">N</confidence>
|
| 526 |
+
<confidence value="88626">NH40H</confidence>
|
| 527 |
+
<confidence value="8">.</confidence>
|
| 528 |
+
</p>
|
| 529 |
+
<p id="p-99" num="99">
|
| 530 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 531 |
+
When no further base consumption was detected, the respective culture was cooled down to about 10<confidence value="288">*C.</confidence>
|
| 532 |
+
</p>
|
| 533 |
+
<boundary-data type="header">293-002-USP</boundary-data>
|
| 534 |
+
<boundary-data type="header">
|
| 535 |
+
<confidence value="88">P1</confidence>
|
| 536 |
+
036PC00 </boundary-data>
|
| 537 |
+
<boundary-data type="header">
|
| 538 |
+
<confidence value="88">14</confidence>
|
| 539 |
+
</boundary-data>
|
| 540 |
+
<p id="p-100" num="100">
|
| 541 |
+
<page-break num="14"/>
|
| 542 |
+
Following cooling, each of the fermentation broths were concentrated by centrifugation and subsequently frozen as pellets in liquid nitrogen. The pellets were immediately after freez- ing measured for acidification activity and CFU/g and stored at - 50<confidence value="2">*</confidence>
|
| 543 |
+
C until further analy- sis. </p>
|
| 544 |
+
<p id="p-101" num="101">
|
| 545 |
+
<boundary-data type="line-number">
|
| 546 |
+
<confidence value="8">5</confidence>
|
| 547 |
+
</boundary-data>
|
| 548 |
+
Media and fermentation condition for Lactobacillus acidophilus (La-5): </p>
|
| 549 |
+
<p id="p-102" num="102">The culture was grown in MRS broth (Merck, Damstadt, Germ<confidence value="5">a</confidence>
|
| 550 |
+
ny) in a <part-num-ref name="">100</part-num-ref>
|
| 551 |
+
<part-num-ref name="">
|
| 552 |
+
<confidence value="5">1</confidence>
|
| 553 |
+
</part-num-ref>
|
| 554 |
+
fermentation tank at 37<confidence value="2">°</confidence>
|
| 555 |
+
C, stirred at <part-num-ref name="fermentation tank at 37°C, stirred at">20</part-num-ref>
|
| 556 |
+
rpm. <part-num-ref name="rpm.">1</part-num-ref>
|
| 557 |
+
% of the culture mentioned above was used as inoculum. </p>
|
| 558 |
+
<p id="p-103" num="103">The anaerobic fermentation was run with nitrogen in the headspace and a pressure of about <boundary-data type="line-number">10 </boundary-data>
|
| 559 |
+
<part-num-ref name="pressure of about">2</part-num-ref>
|
| 560 |
+
bar. The cultures were allowed to acidify to pH 5.5. The pH was subsequently maintained at 5,5 by controlled addition of 13,4 N NH4<confidence value="48">OH</confidence>
|
| 561 |
+
<confidence value="8">.</confidence>
|
| 562 |
+
</p>
|
| 563 |
+
<p id="p-104" num="104">When no further base consumption was detected, the respective culture was cooled down to about <confidence value="68288">10°C.</confidence>
|
| 564 |
+
</p>
|
| 565 |
+
<p id="p-105" num="105">
|
| 566 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 567 |
+
Following cooling, each of the fermentation broths were concentrated by centrifugation and subsequently frozen as pellets in liquid nitrogen. The pellets were immediately after freez- ing measured for CFU/g and stored at - 50<confidence value="2">°</confidence>
|
| 568 |
+
C until further analysis. </p>
|
| 569 |
+
<p id="p-106" num="106">
|
| 570 |
+
<confidence value="2222222222">Acidifying</confidence>
|
| 571 |
+
activity assay and CFU analysis: </p>
|
| 572 |
+
<p id="p-107" num="107">
|
| 573 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 574 |
+
Frozen culture was inoculated on a 0.01 % level in 200 ml sterilized reconstituted skimmed milk (RSM) containing 9,5% solid matter and RSM were incubated at 30<confidence value="2">"</confidence>
|
| 575 |
+
C for 6h to permit acidification of the substrate material. The acidification activity was measured as described by Analytical Procedure Q-AM-052, "acidification activity - <confidence value="5">U</confidence>
|
| 576 |
+
HT", Chr. Hansen A/S (Den- mark). </p>
|
| 577 |
+
<p id="p-108" num="108">
|
| 578 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 579 |
+
CFU analysis was measured and calculated as described<confidence value="5">.</confidence>
|
| 580 |
+
by. analytical Procedure Q-AM- 071, "Enumeration of microorganisms" and Q-AM-022 "Calculation of total count, <confidence value="5">C</confidence>
|
| 581 |
+
hr. </p>
|
| 582 |
+
<p id="p-109" num="109">Hansen A/S (Denmark) using substrate 1209 - LD agar DK-med-rec-123, Chr-Hansen A/S (Denmark) or MRS agar.</p>
|
| 583 |
+
<boundary-data type="header">293-002-USP</boundary-data>
|
| 584 |
+
<boundary-data type="header">
|
| 585 |
+
<confidence value="856">P10</confidence>
|
| 586 |
+
36P<confidence value="566">C00</confidence>
|
| 587 |
+
</boundary-data>
|
| 588 |
+
<boundary-data type="header">
|
| 589 |
+
<confidence value="88">15</confidence>
|
| 590 |
+
</boundary-data>
|
| 591 |
+
<p id="p-110" num="110">
|
| 592 |
+
<page-break num="15"/>
|
| 593 |
+
Example <confidence value="5">1</confidence>
|
| 594 |
+
: Stability study offrozen LD-culture of <confidence value="5">F</confidence>
|
| 595 |
+
l DaN and CH <confidence value="844">NI1</confidence>
|
| 596 |
+
using sucrose, cys- tein chloride and sodium citrate as cryoprotective agents. </p>
|
| 597 |
+
<p id="p-111" num="111">This example describes the stability study with frozen cultures (F-DVS) of Fl DaN and C<confidence value="5">H</confidence>
|
| 598 |
+
<confidence value="86">N1</confidence>
|
| 599 |
+
1 formulated with sucrose, cystein chloride and sodium citrate as cryoprotective agents. </p>
|
| 600 |
+
<p id="p-112" num="112">
|
| 601 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 602 |
+
In all experiments the concentration of cystein chloride and sodium citrate were kept con- stant per gram concentrated biomass. The concentration of sucrose per gram biomass was varied from <part-num-ref name="concentration of sucrose per gram biomass was varied from">6</part-num-ref>
|
| 603 |
+
% (w/w) up to <part-num-ref name="% (w/w) up to">36</part-num-ref>
|
| 604 |
+
% (w<confidence value="2">/</confidence>
|
| 605 |
+
w). All additives were added to the concentrate as solids. </p>
|
| 606 |
+
<p id="p-113" num="113">
|
| 607 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 608 |
+
After fermentation, biomass was harvested and concentrated via centrifugation from fer- mentation broths of CH N <confidence value="66">11</confidence>
|
| 609 |
+
and Fl DaN. The cell concentrate of each culture was divided into appropriate portions of <part-num-ref name="cell concentrate of each culture was divided into appropriate portions of">300</part-num-ref>
|
| 610 |
+
gram and formulated as specified in the table <part-num-ref name="table">1</part-num-ref>
|
| 611 |
+
below. The additives and concentrates were mixed for <part-num-ref name="additives and concentrates were mixed for">30</part-num-ref>
|
| 612 |
+
minutes and subsequently freezed in liquid nitrogen and stored at -50<confidence value="2">*</confidence>
|
| 613 |
+
C. The frozen culture had a content of viable bacteria of at least <boundary-data type="line-number">15 </boundary-data>
|
| 614 |
+
<part-num-ref name="content of viable bacteria of at least">1010</part-num-ref>
|
| 615 |
+
colony forming units (CFU) per g frozen material. Culture activity in milk was meas- ured the same day as formulated and followed periodically up to one year. </p>
|
| 616 |
+
<p id="p-114" num="114">Table 1. Formulation procedure for F-DVS of Fl DaN & CH N<confidence value="668">11.</confidence>
|
| 617 |
+
</p>
|
| 618 |
+
<p id="p-115" num="115">Formulation Cell con- Cystein Sodium Sucrose Sucrose FL DaN CH N<confidence value="6">I</confidence>
|
| 619 |
+
<confidence value="8">1</confidence>
|
| 620 |
+
ID centrate <confidence value="666">(g)</confidence>
|
| 621 |
+
chloride <confidence value="666">(g)</confidence>
|
| 622 |
+
Citrate <confidence value="666">(g)</confidence>
|
| 623 |
+
<confidence value="2">(</confidence>
|
| 624 |
+
<confidence value="686">(%)</confidence>
|
| 625 |
+
<confidence value="6888866">(CFU/g)</confidence>
|
| 626 |
+
<confidence value="6">(</confidence>
|
| 627 |
+
CFU/<confidence value="56">g)</confidence>
|
| 628 |
+
F-DVS <part-num-ref name="ID centrate (g) chloride (g) Citrate (g) ( (%) (CFU/g) (CFU/g) F-DVS">300</part-num-ref>
|
| 629 |
+
<confidence value="5">.</confidence>
|
| 630 |
+
0,00 0,00 <part-num-ref name=".0,00 0,00">0</part-num-ref>
|
| 631 |
+
<part-num-ref name="">0</part-num-ref>
|
| 632 |
+
4,<confidence value="58866">0E+10</confidence>
|
| 633 |
+
5,<confidence value="58868">0E+10</confidence>
|
| 634 |
+
-DVS<confidence value="88">6%</confidence>
|
| 635 |
+
sucrose <part-num-ref name="4,0E+10 5,0E+10 -DVS6% sucrose">300</part-num-ref>
|
| 636 |
+
0,06 0,75 <part-num-ref name="0,06 0,75">2<confidence value="6">1</confidence>
|
| 637 |
+
</part-num-ref>
|
| 638 |
+
<part-num-ref name="">6</part-num-ref>
|
| 639 |
+
3,7E+<confidence value="66">10</confidence>
|
| 640 |
+
4,7E+<confidence value="66">10</confidence>
|
| 641 |
+
<confidence value="5">F</confidence>
|
| 642 |
+
-DVS <confidence value="665">10%</confidence>
|
| 643 |
+
sucrose <part-num-ref name="3,7E+10 4,7E+10 F-DVS 10% sucrose">300</part-num-ref>
|
| 644 |
+
0,06 0,75 <part-num-ref name="0,06 0,75">36</part-num-ref>
|
| 645 |
+
<part-num-ref name="">
|
| 646 |
+
<confidence value="66">10</confidence>
|
| 647 |
+
</part-num-ref>
|
| 648 |
+
3,6E+<confidence value="5">1</confidence>
|
| 649 |
+
0 4,5E+<confidence value="68">10</confidence>
|
| 650 |
+
F-DVS <part-num-ref name="3,6E+10 4,5E+10 F-DVS">22</part-num-ref>
|
| 651 |
+
<confidence value="6">%</confidence>
|
| 652 |
+
sucrose <part-num-ref name="% sucrose">300</part-num-ref>
|
| 653 |
+
0,06 0,75 <part-num-ref name="0,06 0,75">86</part-num-ref>
|
| 654 |
+
<part-num-ref name="">22</part-num-ref>
|
| 655 |
+
3,<confidence value="58866">1E+10</confidence>
|
| 656 |
+
3,9E+<confidence value="66">10</confidence>
|
| 657 |
+
F-DVS <part-num-ref name="3,1E+10 3,9E+10 F-DVS">36</part-num-ref>
|
| 658 |
+
<confidence value="6">%</confidence>
|
| 659 |
+
sucrose <part-num-ref name="% sucrose">300</part-num-ref>
|
| 660 |
+
0,06 0,75 <part-num-ref name="0,06 0,75">17<confidence value="5">1</confidence>
|
| 661 |
+
</part-num-ref>
|
| 662 |
+
<part-num-ref name="">36</part-num-ref>
|
| 663 |
+
2,5E+<confidence value="5">1</confidence>
|
| 664 |
+
0 3,2E<confidence value="666">+10</confidence>
|
| 665 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 666 |
+
Stability profiles for F-DVS of Fl DaN & CH N<confidence value="5">1</confidence>
|
| 667 |
+
1 given as activity versus numbers of days and activity differences compare to day <part-num-ref name="2,5E+10 3,2E+10 Stability profiles for F-DVS of Fl DaN & CH N11 given as activity versus numbers of days and activity differences compare to day">0</part-num-ref>
|
| 668 |
+
are summarized in figure 1 to <part-num-ref name="to">4.</part-num-ref>
|
| 669 |
+
It is evident that F-DVS of Fl DaN and C<confidence value="5">H</confidence>
|
| 670 |
+
N <part-num-ref name="to 4. It is evident that F-DVS of Fl DaN and CH N">
|
| 671 |
+
<confidence value="58">11</confidence>
|
| 672 |
+
</part-num-ref>
|
| 673 |
+
<confidence value="78">fr</confidence>
|
| 674 |
+
ee of additives are loosing activity thus stability. The re- duction in stability is equal to 0.40 pH units for CH N <part-num-ref name="re- duction in stability is equal to 0.40 pH units for CH N">11</part-num-ref>
|
| 675 |
+
and 0.60 pH units for Fl DaN after <part-num-ref name="and 0.60 pH units for Fl DaN after">365</part-num-ref>
|
| 676 |
+
days. All the tested sucrose formulations <part-num-ref name="tested sucrose formulations">(6</part-num-ref>
|
| 677 |
+
%, <part-num-ref name="%,">10</part-num-ref>
|
| 678 |
+
%, <part-num-ref name="%,">22</part-num-ref>
|
| 679 |
+
% and <part-num-ref name="% and">36</part-num-ref>
|
| 680 |
+
%) seem to have <boundary-data type="header">293-002-USP</boundary-data>
|
| 681 |
+
<page-break num="16"/>
|
| 682 |
+
<boundary-data type="header">
|
| 683 |
+
<confidence value="856">P10</confidence>
|
| 684 |
+
36P<confidence value="555">C00</confidence>
|
| 685 |
+
</boundary-data>
|
| 686 |
+
<boundary-data type="header">
|
| 687 |
+
<confidence value="88">16</confidence>
|
| 688 |
+
</boundary-data>
|
| 689 |
+
positive effect on the stability. Activity is reduced approx. 0.1 pH unit after <part-num-ref name="stability. Activity is reduced approx. 0.1 pH unit after">365</part-num-ref>
|
| 690 |
+
days of storage at - 55<confidence value="288">*C.</confidence>
|
| 691 |
+
</p>
|
| 692 |
+
<p id="p-116" num="116">Example 2: Stability study offrozen LD-culture of Fl DaN, CH<confidence value="811">NJJ</confidence>
|
| 693 |
+
<confidence value="6">&</confidence>
|
| 694 |
+
CH<confidence value="85">N1</confidence>
|
| 695 |
+
9 using su- <boundary-data type="line-number">
|
| 696 |
+
<confidence value="8">5</confidence>
|
| 697 |
+
</boundary-data>
|
| 698 |
+
<confidence value="7">r</confidence>
|
| 699 |
+
ose and trehalose as cryoprotective agents. </p>
|
| 700 |
+
<p id="p-117" num="117">This example describes the stability study with frozen cultures of Fl DaN and CH N<confidence value="5">1</confidence>
|
| 701 |
+
1 and CH N <part-num-ref name="stability study with frozen cultures of Fl DaN and CH N11 and CH N">19</part-num-ref>
|
| 702 |
+
formulated with sucrose and trehalose as cryoprotective agents. The concentration of sucrose per gram biomass was varied from 6% (w/w) up to <part-num-ref name="concentration of sucrose per gram biomass was varied from 6% (w/w) up to">10</part-num-ref>
|
| 703 |
+
% (w/w). Trehalose was only tested on a <part-num-ref name="">5</part-num-ref>
|
| 704 |
+
(w/w) level. All sucrose concentrations were prepared from a <part-num-ref name="">50</part-num-ref>
|
| 705 |
+
% (w/w) <boundary-data type="line-number">10 </boundary-data>
|
| 706 |
+
sucrose solution added to the biomass. The trehalose concentration was prepared from a <part-num-ref name="">40</part-num-ref>
|
| 707 |
+
<confidence value="6">%</confidence>
|
| 708 |
+
(w/w) solution. </p>
|
| 709 |
+
<p id="p-118" num="118">After fermentation, bio<confidence value="8">m</confidence>
|
| 710 |
+
ass was harvested and concentrated via centrifugation from fer- mentation broths of F<confidence value="5">l</confidence>
|
| 711 |
+
DaN, CH N 11 and CH N19. The cell concentrate of each culture <boundary-data type="line-number">15 </boundary-data>
|
| 712 |
+
was divided into appropriate portions of <part-num-ref name="cell concentrate of each culture was divided into appropriate portions of">300</part-num-ref>
|
| 713 |
+
gram and formulated as specified in the table <part-num-ref name="table">2</part-num-ref>
|
| 714 |
+
below. The additives and concentrates were mixed for <part-num-ref name="additives and concentrates were mixed for">30</part-num-ref>
|
| 715 |
+
minutes and subsequently freezed in liquid nitrogen and stored at - <part-num-ref name="minutes and subsequently freezed in liquid nitrogen and stored at -">50</part-num-ref>
|
| 716 |
+
<confidence value="2">°</confidence>
|
| 717 |
+
C. The frozen culture had a content of viable bacteria of at least <part-num-ref name="content of viable bacteria of at least">10<confidence value="5">1</confidence>
|
| 718 |
+
0 </part-num-ref>
|
| 719 |
+
colony forming units (CFU) per g frozen material. Culture activity in milk was measured the same day as formulated and followed periodically up to <part-num-ref name="same day as formulated and followed periodically up to">70</part-num-ref>
|
| 720 |
+
days. </p>
|
| 721 |
+
<p id="p-119" num="119">
|
| 722 |
+
<boundary-data type="line-number">
|
| 723 |
+
<confidence value="88">20</confidence>
|
| 724 |
+
</boundary-data>
|
| 725 |
+
Table 2. Formulation procedure for F-DVS of Fl DaN, CH N 11 & CH N19 using sucrose and trehalose as <confidence value="22222222222222">cryoprotective</confidence>
|
| 726 |
+
a<confidence value="8">g</confidence>
|
| 727 |
+
ents Formulation Cell concen- Additive Final additive Fl DaN CH N19 ID trate <confidence value="656">(g)</confidence>
|
| 728 |
+
solution <confidence value="666">(g)</confidence>
|
| 729 |
+
conc. (% Sucrose) CFU/<confidence value="5">g</confidence>
|
| 730 |
+
CFU/<confidence value="4">g</confidence>
|
| 731 |
+
-DVS <part-num-ref name="& CH N19 using sucrose and trehalose as cryoprotective agents Formulation Cell concen- Additive Final additive Fl DaN CH N19 ID trate (g) solution (g) conc. (% Sucrose) CFU/g CFU/g -DVS">300</part-num-ref>
|
| 732 |
+
<part-num-ref name="">0</part-num-ref>
|
| 733 |
+
<part-num-ref name="">0</part-num-ref>
|
| 734 |
+
3,<confidence value="5">0</confidence>
|
| 735 |
+
E+10 4,<confidence value="5">0</confidence>
|
| 736 |
+
E+10 -DVS/07G <part-num-ref name="3,0E+10 4,0E+10 -DVS/07G">300</part-num-ref>
|
| 737 |
+
<part-num-ref name="">43</part-num-ref>
|
| 738 |
+
<part-num-ref name="">6<confidence value="5">.</confidence>
|
| 739 |
+
</part-num-ref>
|
| 740 |
+
2,6E+10 3,5E+10 -DVS 5% Trehalos <part-num-ref name="6. 2,6E+10 3,5E+10 -DVS 5% Trehalos">300</part-num-ref>
|
| 741 |
+
<part-num-ref name="">43</part-num-ref>
|
| 742 |
+
<part-num-ref name="">5</part-num-ref>
|
| 743 |
+
2,6E+10 3,5E+10 -DVS 3% Sucrose <part-num-ref name="2,6E+10 3,5E+10 -DVS 3% Sucrose">300</part-num-ref>
|
| 744 |
+
<part-num-ref name="">19</part-num-ref>
|
| 745 |
+
<part-num-ref name="">3</part-num-ref>
|
| 746 |
+
2,8E+10 3,8E+10 -DVS 5% Sucrose <part-num-ref name="2,8E+10 3,8E+10 -DVS 5% Sucrose">300</part-num-ref>
|
| 747 |
+
<part-num-ref name="">34</part-num-ref>
|
| 748 |
+
<part-num-ref name="">5</part-num-ref>
|
| 749 |
+
2,7E+<confidence value="5">1</confidence>
|
| 750 |
+
0 3,6E+10 -DVS 6% Sucrose <part-num-ref name="2,7E+10 3,6E+10 -DVS 6% Sucrose">300</part-num-ref>
|
| 751 |
+
<part-num-ref name="">42</part-num-ref>
|
| 752 |
+
<part-num-ref name="">6</part-num-ref>
|
| 753 |
+
2,6E+<confidence value="5">1</confidence>
|
| 754 |
+
0 3,5E+10 -DVS 8% Sucrose <part-num-ref name="2,6E+10 3,5E+10 -DVS 8% Sucrose">300</part-num-ref>
|
| 755 |
+
<part-num-ref name="">57</part-num-ref>
|
| 756 |
+
<part-num-ref name="">8</part-num-ref>
|
| 757 |
+
2,5E+10 3,4E+10 -DVS 9% Sucrose <part-num-ref name="2,5E+10 3,4E+10 -DVS 9% Sucrose">300</part-num-ref>
|
| 758 |
+
<part-num-ref name="">66</part-num-ref>
|
| 759 |
+
<part-num-ref name="">9</part-num-ref>
|
| 760 |
+
2,5E+10 3,3E+10 -DVS 10% Sucrose <part-num-ref name="2,5E+10 3,3E+10 -DVS 10% Sucrose">300</part-num-ref>
|
| 761 |
+
<part-num-ref name="">75</part-num-ref>
|
| 762 |
+
<part-num-ref name="">10</part-num-ref>
|
| 763 |
+
2,4E+<confidence value="5">1</confidence>
|
| 764 |
+
0 3,2E+10 -DVS 13% Sucrose <part-num-ref name="2,4E+10 3,2E+10 -DVS 13% Sucrose">300</part-num-ref>
|
| 765 |
+
<part-num-ref name="">105</part-num-ref>
|
| 766 |
+
<part-num-ref name="">13</part-num-ref>
|
| 767 |
+
2,2E+<confidence value="5">1</confidence>
|
| 768 |
+
0 3,<confidence value="58868">0E+10</confidence>
|
| 769 |
+
<boundary-data type="header">293-002-USP</boundary-data>
|
| 770 |
+
<page-break num="17"/>
|
| 771 |
+
<boundary-data type="header">
|
| 772 |
+
<confidence value="86">P1</confidence>
|
| 773 |
+
036P<confidence value="588">C00</confidence>
|
| 774 |
+
</boundary-data>
|
| 775 |
+
<boundary-data type="header">
|
| 776 |
+
<confidence value="88">17</confidence>
|
| 777 |
+
</boundary-data>
|
| 778 |
+
Stability profiles for F-DVS of Fl DaN, CH N<confidence value="66">11</confidence>
|
| 779 |
+
& CH N19 using sucrose and trehalose as cryoprotective agents are summarized in figure 5 to <part-num-ref name="to">10.</part-num-ref>
|
| 780 |
+
</p>
|
| 781 |
+
<p id="p-120" num="120">All reference cultures have lost activity (Fl DaN: 0,3 pH units after 65 days at -50 <confidence value="2">*</confidence>
|
| 782 |
+
C; CH N <boundary-data type="line-number">5 </boundary-data>
|
| 783 |
+
11: 0,17 pH units after <part-num-ref name="days at -50 *C; CH N 11: 0,17 pH units after">60</part-num-ref>
|
| 784 |
+
days at -50 <confidence value="2">°</confidence>
|
| 785 |
+
C; CH N 19: 0,25 pH units after <part-num-ref name="days at -50 °C; CH N 19: 0,25 pH units after">70</part-num-ref>
|
| 786 |
+
days at -50 <confidence value="2">*</confidence>
|
| 787 |
+
C). </p>
|
| 788 |
+
<p id="p-121" num="121">All the tested formulations reduce the activity loss compare to the reference cultures. Fur- thermore, it is difficult to conclude which sucrose concentration is optimum with regard to stability.</p>
|
| 789 |
+
<p id="p-122" num="122">
|
| 790 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 791 |
+
From the stability profiles of Fl DaN and CH N19 it can be observed that the reference and the tested sucrose formulations have an initial lost of activity within the first <part-num-ref name="first">1</part-num-ref>
|
| 792 |
+
-3 weeks of storage. Hereafter, all the sucrose formulated concentrates show a constant stability profile. </p>
|
| 793 |
+
<p id="p-123" num="123">Fl DaN shows a higher initial loss than CH N19. However, no initial loss of activity could be observed from the stability profiles of all the tested formulations of CH N<confidence value="668">11.</confidence>
|
| 794 |
+
</p>
|
| 795 |
+
<p id="p-124" num="124">
|
| 796 |
+
<boundary-data type="line-number">
|
| 797 |
+
<confidence value="88">15</confidence>
|
| 798 |
+
</boundary-data>
|
| 799 |
+
Exam<confidence value="8">p</confidence>
|
| 800 |
+
le 3: Stability study offrozen <confidence value="5">O</confidence>
|
| 801 |
+
-culture of R-603 Initial loss of activity within the first <part-num-ref name="first">1</part-num-ref>
|
| 802 |
+
- <part-num-ref name="-">3</part-num-ref>
|
| 803 |
+
weeks has so far not been seen for any of Chr. </p>
|
| 804 |
+
<p id="p-125" num="125">Hansen A/S commercial available <confidence value="5">O</confidence>
|
| 805 |
+
-cultures (Lactococcus lactis subsp. cremoris & Lacto<confidence value="5">-</confidence>
|
| 806 |
+
coccus lactis subsp. lactis). Stability profiles for R603 followed up to 35 days and analyzed <boundary-data type="line-number">20 </boundary-data>
|
| 807 |
+
for acidification in M<confidence value="5">1</confidence>
|
| 808 |
+
7 media is summarized in figure 11. </p>
|
| 809 |
+
<p id="p-126" num="126">
|
| 810 |
+
<confidence value="8">E</confidence>
|
| 811 |
+
xample 4: Stability study offrozen Lactobacilus acidophislus (La-<confidence value="68">5)</confidence>
|
| 812 |
+
This example describes the stability study with frozen cultures of Lactobacillus acidophilus formulated with sucrose or sucrose and maltodextrine as cryoprotective agents. The concen- <boundary-data type="line-number">25 </boundary-data>
|
| 813 |
+
tration of sucrose per gram biomass was 32% (w/w). Sucrose and maltodextrine were tested <confidence value="88">at</confidence>
|
| 814 |
+
16%<confidence value="5">/</confidence>
|
| 815 |
+
<confidence value="8">1</confidence>
|
| 816 |
+
6%(w/w) level. </p>
|
| 817 |
+
<p id="p-127" num="127">After fermentation, biomass was harvested and concentrated by centrifugation. The cell concentrate<confidence value="5">.</confidence>
|
| 818 |
+
was divided into appropriate portions of <part-num-ref name="cell concentrate. was divided into appropriate portions of">300</part-num-ref>
|
| 819 |
+
gram and formulated. The addi- <boundary-data type="line-number">30 </boundary-data>
|
| 820 |
+
tives and concentrates were mixed for <part-num-ref name="addi- tives and concentrates were mixed for">30</part-num-ref>
|
| 821 |
+
minutes and subsequently freezed in liquid nitro- gen and stored at - <part-num-ref name="minutes and subsequently freezed in liquid nitro- gen and stored at -">20,</part-num-ref>
|
| 822 |
+
-50 or -80 <confidence value="25">*C</confidence>
|
| 823 |
+
. The stability was measured as colony-forming units <confidence value="8686">(CFU</confidence>
|
| 824 |
+
) per g frozen material on MRS agar 37<confidence value="2">*</confidence>
|
| 825 |
+
C <part-num-ref name="stability was measured as colony-forming units (CFU) per g frozen material on MRS agar 37*C">(72</part-num-ref>
|
| 826 |
+
hours). </p>
|
| 827 |
+
<boundary-data type="header">293-002-USP</boundary-data>
|
| 828 |
+
<boundary-data type="header">
|
| 829 |
+
<confidence value="814">Pl0</confidence>
|
| 830 |
+
36P<confidence value="566">C00</confidence>
|
| 831 |
+
</boundary-data>
|
| 832 |
+
<boundary-data type="header">
|
| 833 |
+
<confidence value="88">18</confidence>
|
| 834 |
+
</boundary-data>
|
| 835 |
+
<p id="p-128" num="128">
|
| 836 |
+
<page-break num="18"/>
|
| 837 |
+
Table 3: Lactobacillus acidophilus stored at different temperatures. Storage stability is measured as CFU/g after 6, 13, and 68 days Temp = Temp = + 32% Sucrose at Days -20<confidence value="2">°</confidence>
|
| 838 |
+
C -50<confidence value="2">°</confidence>
|
| 839 |
+
C Temp = -80<confidence value="2">°</confidence>
|
| 840 |
+
C -20<confidence value="28">°C</confidence>
|
| 841 |
+
<part-num-ref name="days Temp = Temp = + 32% Sucrose at Days -20°C -50°C Temp = -80°C -20°C">0</part-num-ref>
|
| 842 |
+
4.35E<confidence value="686">+10</confidence>
|
| 843 |
+
4.35E+1<confidence value="5">0</confidence>
|
| 844 |
+
4.35E+1<confidence value="5">0</confidence>
|
| 845 |
+
3.82E+1<confidence value="5">0</confidence>
|
| 846 |
+
<part-num-ref name="4.35E+10 4.35E+10 4.35E+10 3.82E+10">6</part-num-ref>
|
| 847 |
+
3.14E+1<confidence value="5">0</confidence>
|
| 848 |
+
4.87E+1<confidence value="5">0</confidence>
|
| 849 |
+
4.77E+1<confidence value="5">0</confidence>
|
| 850 |
+
2.61E+1<confidence value="5">0</confidence>
|
| 851 |
+
<part-num-ref name="3.14E+10 4.87E+10 4.77E+10 2.61E+10">13</part-num-ref>
|
| 852 |
+
2.75E+<confidence value="5">1</confidence>
|
| 853 |
+
0 4.37E+1<confidence value="5">0</confidence>
|
| 854 |
+
4.61E+1<confidence value="5">0</confidence>
|
| 855 |
+
2.5<confidence value="68666">0E+10</confidence>
|
| 856 |
+
<part-num-ref name="2.75E+10 4.37E+10 4.61E+10 2.50E+10">68</part-num-ref>
|
| 857 |
+
6.52E+09 4.15E+1<confidence value="5">0</confidence>
|
| 858 |
+
4.14E+<confidence value="66">10</confidence>
|
| 859 |
+
2.51E+10 <boundary-data type="line-number">5 </boundary-data>
|
| 860 |
+
Table 4: Lactobacillus acidophilus stored at -20<confidence value="2">*</confidence>
|
| 861 |
+
C without additives and with 32% sucrose or with 16% sucrose + 16% maltodextrine. </p>
|
| 862 |
+
<p id="p-129" num="129">without a 16% sucrose + 16% Days tives 32% sucrose maltodextrine <part-num-ref name="16% sucrose + 16% Days tives 32% sucrose maltodextrine">0</part-num-ref>
|
| 863 |
+
2.81E+<confidence value="5">1</confidence>
|
| 864 |
+
0 3.02E+1<confidence value="6">0</confidence>
|
| 865 |
+
<confidence value="2">-</confidence>
|
| 866 |
+
3.82E+1<confidence value="5">0</confidence>
|
| 867 |
+
<part-num-ref name="2.81E+10 3.02E+10 - 3.82E+10">7</part-num-ref>
|
| 868 |
+
1.81E+1<confidence value="5">0</confidence>
|
| 869 |
+
1.99E+1<confidence value="5">0</confidence>
|
| 870 |
+
2.97E+10 <part-num-ref name="1.81E+10 1.99E+10 2.97E+10">14</part-num-ref>
|
| 871 |
+
1.11E+10 <confidence value="5">1</confidence>
|
| 872 |
+
.56E+<confidence value="5">1</confidence>
|
| 873 |
+
0 2.04E+10 <part-num-ref name="1.11E+10 1.56E+10 2.04E+10">21</part-num-ref>
|
| 874 |
+
out of range 1.98E+<confidence value="58">10</confidence>
|
| 875 |
+
2.93E+1<confidence value="5">0</confidence>
|
| 876 |
+
<part-num-ref name="out of range 1.98E+10 2.93E+10">54</part-num-ref>
|
| 877 |
+
8.60E+09 1.53E+1<confidence value="5">0</confidence>
|
| 878 |
+
2.54E+1<confidence value="5">0</confidence>
|
| 879 |
+
Lactobacillus acidophilus seems storage stable at -50 and -80<confidence value="2">°</confidence>
|
| 880 |
+
C, but the viability is dec<confidence value="6868">lin-</confidence>
|
| 881 |
+
ing if the culture is stored at -20<confidence value="2">*</confidence>
|
| 882 |
+
C. By use of additives; sucrose or sucrose and maltodex- <part-num-ref name="culture is stored at -20*C. By use of additives; sucrose or sucrose and maltodex-">10</part-num-ref>
|
| 883 |
+
trine - it is possible to improve the stability of the culture at -20<confidence value="288">*C.</confidence>
|
| 884 |
+
</p>
|
| 885 |
+
<boundary-data type="header">293-002-U<confidence value="68">SP</confidence>
|
| 886 |
+
</boundary-data>
|
| 887 |
+
<boundary-data type="header">
|
| 888 |
+
<confidence value="88">P1</confidence>
|
| 889 |
+
036P<confidence value="588">C00</confidence>
|
| 890 |
+
</boundary-data>
|
| 891 |
+
<boundary-data type="header">
|
| 892 |
+
<confidence value="88">19</confidence>
|
| 893 |
+
</boundary-data>
|
| 894 |
+
<heading id="h-9">REFERENCES:</heading>
|
| 895 |
+
<p id="p-130" num="130">
|
| 896 |
+
<page-break num="19"/>
|
| 897 |
+
EP 259739 A<confidence value="5">1</confidence>
|
| 898 |
+
, Miles Laboratories, <part-num-ref name="A1, Miles Laboratories,">16</part-num-ref>
|
| 899 |
+
March <part-num-ref name="March">1988</part-num-ref>
|
| 900 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 901 |
+
F.J. <confidence value="22222222">Chavarri</confidence>
|
| 902 |
+
et al, "Cryoprotective agents for frozen concentrated starters from non-bitter Streptococcus Lactis strains", Biotechnology letters, vo<confidence value="6">l</confidence>
|
| 903 |
+
<part-num-ref name="F.J. Chavarri et al, "Cryoprotective agents for frozen concentrated starters from non-bitter Streptococcus Lactis strains", Biotechnology letters, vol">10,</part-num-ref>
|
| 904 |
+
<part-num-ref name="F.J. Chavarri et al, "Cryoprotective agents for frozen concentrated starters from non-bitter Streptococcus Lactis strains", Biotechnology letters, vol 10,">1,</part-num-ref>
|
| 905 |
+
11- <part-num-ref name="F.J. Chavarri et al, "Cryoprotective agents for frozen concentrated starters from non-bitter Streptococcus Lactis strains", Biotechnology letters, vol 10, 1, 11-">16</part-num-ref>
|
| 906 |
+
<part-num-ref name="">(1988)</part-num-ref>
|
| 907 |
+
R. <confidence value="2222222">Circoba</confidence>
|
| 908 |
+
et al., "Influence of cryoprotectants on the viability and acidifying activity of frozen and freeze-dried cells of the novel starter strain Lactococcus lactis subsp. lactis <boundary-data type="line-number">10 </boundary-data>
|
| 909 |
+
CECT 5180", Eur Food Res Technol <part-num-ref name="novel starter strain Lactococcus lactis subsp. lactis CECT 5180", Eur Food Res Technol">(2000)</part-num-ref>
|
| 910 |
+
<part-num-ref name="">211,</part-num-ref>
|
| 911 |
+
<part-num-ref name="211,">433</part-num-ref>
|
| 912 |
+
<confidence value="8">-</confidence>
|
| 913 |
+
<part-num-ref name="-">437</part-num-ref>
|
| 914 |
+
WO 00/39281, Chr. Hansen A<confidence value="5">/</confidence>
|
| 915 |
+
S, <part-num-ref name="WO 00/39281, Chr. Hansen A/S,">6</part-num-ref>
|
| 916 |
+
July <part-num-ref name="July">2000</part-num-ref>
|
| 917 |
+
<boundary-data type="header">293-002-USP</boundary-data>
|
| 918 |
+
</p>
|
| 919 |
+
</description>
|
| 920 |
+
</us-patent-application>
|
| 921 |
+
|
prior_art/10548403.xml
ADDED
|
@@ -0,0 +1,61 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>10548403</doc-number>
|
| 8 |
+
<date>2010-01-21</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">Serial <confidence value="668">No.</confidence>
|
| 14 |
+
<confidence value="6666666668">10/548,403</confidence>
|
| 15 |
+
<confidence value="566">Att</confidence>
|
| 16 |
+
y. <confidence value="5882">Dkt.</confidence>
|
| 17 |
+
<confidence value="668">No.</confidence>
|
| 18 |
+
<confidence value="56656625556">036179-0108</confidence>
|
| 19 |
+
AMENDMENTS TO T<confidence value="21">Hl</confidence>
|
| 20 |
+
E SPECIFICATION Plea<confidence value="8">s</confidence>
|
| 21 |
+
e replace <confidence value="866">the</confidence>
|
| 22 |
+
abstract with <confidence value="666">the</confidence>
|
| 23 |
+
followi<confidence value="8">n</confidence>
|
| 24 |
+
g<confidence value="8">:</confidence>
|
| 25 |
+
</p>
|
| 26 |
+
<p id="p-2" num="2">
|
| 27 |
+
<confidence value="666">The</confidence>
|
| 28 |
+
pr<confidence value="8">e</confidence>
|
| 29 |
+
sent invention pr<confidence value="8">o</confidence>
|
| 30 |
+
vides industrial <confidence value="82656">scale</confidence>
|
| 31 |
+
expanded bed ads<confidence value="8">o</confidence>
|
| 32 |
+
rption <confidence value="686">pro</confidence>
|
| 33 |
+
<confidence value="666">ess</confidence>
|
| 34 |
+
<confidence value="668">for</confidence>
|
| 35 |
+
fractionation <confidence value="666">and</confidence>
|
| 36 |
+
isolation <confidence value="66">of</confidence>
|
| 37 |
+
<confidence value="8855665666566">bio-molecules</confidence>
|
| 38 |
+
from f<confidence value="8">l</confidence>
|
| 39 |
+
uids<confidence value="8">,</confidence>
|
| 40 |
+
<confidence value="8">p</confidence>
|
| 41 |
+
referably proteins from milk <confidence value="666">and</confidence>
|
| 42 |
+
whey, in a <confidence value="2">c</confidence>
|
| 43 |
+
ost<confidence value="2">-</confidence>
|
| 44 |
+
effective manner. This is accomplished by operating the <confidence value="8">e</confidence>
|
| 45 |
+
xpanded bed column at high temperatures o<confidence value="2">f</confidence>
|
| 46 |
+
at last 40<confidence value="272">4C,</confidence>
|
| 47 |
+
combined with applying flow rates <confidence value="6">h</confidence>
|
| 48 |
+
eater than <confidence value="11121">46O91</confidence>
|
| 49 |
+
<part-num-ref name="expanded bed column at high temperatures of at last 404C, combined with applying flow rates heater than 46O91">
|
| 50 |
+
<confidence value="6252">1500</confidence>
|
| 51 |
+
</part-num-ref>
|
| 52 |
+
<confidence value="2222222">cm/hour</confidence>
|
| 53 |
+
. </p>
|
| 54 |
+
<p id="p-3" num="3">
|
| 55 |
+
<confidence value="666">-2-</confidence>
|
| 56 |
+
<confidence value="2222">WASH</confidence>
|
| 57 |
+
<confidence value="2222222">623082.</confidence>
|
| 58 |
+
</p>
|
| 59 |
+
</description>
|
| 60 |
+
</us-patent-application>
|
| 61 |
+
|
prior_art/10549668.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>10549668</doc-number>
|
| 8 |
+
<date>2011-06-29</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">AMENDMENT UNDER 37 C.F.R. <confidence value="6">§</confidence>
|
| 14 |
+
1.111 Attorney Docket No.: Q90317 <confidence value="22222">Appln</confidence>
|
| 15 |
+
. No.: 10/549,668 </p>
|
| 16 |
+
<heading id="h-1">AMENDMENTS TO THE SPECIFICATION</heading>
|
| 17 |
+
<p id="p-2" num="2">Please replace the present abstract of the disclosure with the following amended abstract of the disclosure:</p>
|
| 18 |
+
<p id="p-3" num="3">The present invention relates to a pressure sensitive adhesive sheet for protecting a surface, which has a structure that a pressure sensitive adhesive layer, a cured urethane (meth)acrylate layer, a hard coat layer and optionally a<confidence value="66615885">-proteet</confidence>
|
| 19 |
+
protective film are laminated in order, and a method for producing said sheet, which comprises applying a urethane(meth)acrylate on the surface of a releasing agent layer of a plastic film having the releasing agent layer, followed by curing, to form a cured urethane(meth)acrylate layer, applying a hard coat agent on the surface of the cured urethane(meth)acrylate layer, followed by curing, to form a hard coat layer, laminating a process film on the surface of the hard coat layer, and then peeling the above plastic film having a releasing agent layer, and subsequently forming a pressure sensitive adhesive layer on the exposed surface of the cured urethane(meth)acrylate layer. </p>
|
| 20 |
+
<p id="p-4" num="4">
|
| 21 |
+
<confidence value="8">2</confidence>
|
| 22 |
+
</p>
|
| 23 |
+
</description>
|
| 24 |
+
</us-patent-application>
|
| 25 |
+
|
prior_art/10557944.xml
ADDED
|
@@ -0,0 +1,780 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>10557944</doc-number>
|
| 8 |
+
<date>2005-11-21</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">WO 2004/103320 PCT<confidence value="5">/</confidence>
|
| 14 |
+
EP2004/004942 </boundary-data>
|
| 15 |
+
<heading id="h-1">SKIN TREATMENTS</heading>
|
| 16 |
+
<p id="p-1" num="1">Field of the invention The invention relates to the field of topical or systemic compositions and more <boundary-data type="line-number">5 </boundary-data>
|
| 17 |
+
particularly to compositions comprising a combination of retinoic acid and a Liver- X-receptor (LXR) agonist and their use in providing a variety of skin care benefits by slowing or inhibiting photo-induced or age-related skin damage. </p>
|
| 18 |
+
<p id="p-2" num="2">Back<confidence value="6">g</confidence>
|
| 19 |
+
round to the invention <boundary-data type="line-number">
|
| 20 |
+
<confidence value="86">10</confidence>
|
| 21 |
+
</boundary-data>
|
| 22 |
+
Skin is subject to deterioration through dermatological disorders, environmental abuse (wind, air conditioning, central heating) or through the normal ageing process (chronoageing) which may be accelerated by exposure of skin to sun (photoageing). In recent years the demand for cosmetic methods for improving the appearance and condition and, in particular, for reversing, reducing or <boundary-data type="line-number">15 </boundary-data>
|
| 23 |
+
preventing the visible signs of wrinkled, aged and/or photodamaged skin has grown enormously. </p>
|
| 24 |
+
<p id="p-3" num="3">Consumers are increasingly seeking "anti-ageing" products that reverse, treat or delay the visible signs of chronoaging and photoaging skin such as wrinkles, <boundary-data type="line-number">20 </boundary-data>
|
| 25 |
+
lines, sagging, hyperpigmentation and age spots. </p>
|
| 26 |
+
<p id="p-4" num="4">It is known in the art that retinoic acid is a potent anti-ageing active and induces dermal repair of photodamaged skin. It has been shown that wrinkle effacement and dermal repair following topical treatment of skin with retinoic acid arises <boundary-data type="line-number">
|
| 27 |
+
<confidence value="88">25</confidence>
|
| 28 |
+
</boundary-data>
|
| 29 |
+
through new collagen deposition and synthesis in the skin (for example, Griffiths et a<confidence value="5">l</confidence>
|
| 30 |
+
. N. Eng. J. med. <part-num-ref name="skin (for example, Griffiths et al. N. Eng. J. med.">(1993)</part-num-ref>
|
| 31 |
+
<part-num-ref name="">329,</part-num-ref>
|
| 32 |
+
530-535). It is widely accepted that strengthening of the dermal matrix by boosting the level of collagen in skin using retinoic acid provides anti- ageing/dermal repair benefits. </p>
|
| 33 |
+
<p id="p-5" num="5">
|
| 34 |
+
<boundary-data type="line-number">
|
| 35 |
+
<confidence value="86">30</confidence>
|
| 36 |
+
</boundary-data>
|
| 37 |
+
The Liver-X-receptor (LXR) is a nuclear receptor known to be present in human keratinocytes where it plays an integral role in the regulation of cell proliferation and differentiation as well as lipid metabolism within the epidermis. </p>
|
| 38 |
+
<boundary-data type="header">WO 2004/103320 PCT<confidence value="5">/</confidence>
|
| 39 |
+
EP2004/004942 </boundary-data>
|
| 40 |
+
<boundary-data type="header">
|
| 41 |
+
<confidence value="8">2</confidence>
|
| 42 |
+
</boundary-data>
|
| 43 |
+
<p id="p-6" num="6">
|
| 44 |
+
<page-break num="2"/>
|
| 45 |
+
Summary of the invention The present invention is based on a finding that LXR activators enhance the effects of retinoic acid i.e. that LXR activators and retinoic acid act synergistically. </p>
|
| 46 |
+
<p id="p-7" num="7">In particular, it is shown that LXR activators and retinoic acid act synergistically to <boundary-data type="line-number">5 </boundary-data>
|
| 47 |
+
upregulate CRAB P <confidence value="55">II</confidence>
|
| 48 |
+
expression in dermal fibroblasts, a well recognised marker of retinoic acid (RA) responsiveness and a transcriptional regulator in RA signalling (Delva et al., <part-num-ref name="transcriptional regulator in RA signalling (Delva et al.,">1999,</part-num-ref>
|
| 49 |
+
Mol. & Cell Biol. <part-num-ref name="transcriptional regulator in RA signalling (Delva et al., 1999, Mol. & Cell Biol.">19,</part-num-ref>
|
| 50 |
+
<part-num-ref name="transcriptional regulator in RA signalling (Delva et al., 1999, Mol. & Cell Biol. 19,">7158</part-num-ref>
|
| 51 |
+
- <part-num-ref name="-">7167)</part-num-ref>
|
| 52 |
+
Since upregulation of CRAB P <confidence value="55">II</confidence>
|
| 53 |
+
expression is known to correlate with the ability <boundary-data type="line-number">10 </boundary-data>
|
| 54 |
+
to reverse the physiological changes induced by chronological ageing and/or photoageing, a combination of an LXR activator and retinoic acid, and/or a metabolic precursor thereto, will be effective in the treatment and prevention of normal, but cosmetically undesirable, skin conditions, due to chronoaging or photoaging, such as wrinkles, lines, and sagging may be obtained through the <boundary-data type="line-number">15 </boundary-data>
|
| 55 |
+
application of cosmetic (topical) or oral compositions to the skin which comprises an LXR activating ligand in combination with retinoic acid and/or a metabolic precursor thereto. </p>
|
| 56 |
+
<p id="p-8" num="8">Any reference herein to an activator of LXR includes a reference to an activator <boundary-data type="line-number">20 </boundary-data>
|
| 57 |
+
of LXRa and/or of LXR<confidence value="11">.3</confidence>
|
| 58 |
+
, unless specifically stated to the contrary. </p>
|
| 59 |
+
<p id="p-9" num="9">Accordingly, in a first aspect of the present invention a composition is provided comprising (i) an LXR activator other than 25-hydroxycholesterol and (ii) retinoic acid and/or a metabolic precursor thereto.</p>
|
| 60 |
+
<p id="p-10" num="10">
|
| 61 |
+
<boundary-data type="line-number">
|
| 62 |
+
<confidence value="88">25</confidence>
|
| 63 |
+
</boundary-data>
|
| 64 |
+
A second aspect of the present invention provides a cosmetic method for reducing chronoageing and/or photoageing of the skin, the method comprising applying to the skin a topical composition comprising (i) an LXR activator other than 25-hydroxycholesterol and (ii) retinoic acid and/or a metabolic precursor <boundary-data type="line-number">30 </boundary-data>
|
| 65 |
+
thereto. </p>
|
| 66 |
+
<p id="p-11" num="11">A third aspect of the present invention comprises a cosmetic method of reducing chronoageing and/or photoageing of the skin, the method comprising dosing <page-break num="3"/>
|
| 67 |
+
<boundary-data type="header">WO 2004/103320 PCT<confidence value="5">/</confidence>
|
| 68 |
+
EP2004<confidence value="5">/</confidence>
|
| 69 |
+
004942 </boundary-data>
|
| 70 |
+
<boundary-data type="header">
|
| 71 |
+
<confidence value="8">3</confidence>
|
| 72 |
+
</boundary-data>
|
| 73 |
+
topically and/or systemically, an LXR activator and retinoic acid and/or a metabolic precursor thereto. In a preferred embodiment the LXR activator and the retinoic acid and/or metabolic precursor thereto are in the form of a composition. </p>
|
| 74 |
+
<p id="p-12" num="12">
|
| 75 |
+
<boundary-data type="line-number">
|
| 76 |
+
<confidence value="8">5</confidence>
|
| 77 |
+
</boundary-data>
|
| 78 |
+
<confidence value="5">I</confidence>
|
| 79 |
+
n one embodiment, the LXR activator and the retinoic acid and/or metabolic precursor thereto are administered by topical application to the skin. In another embodiment, the LXR activator and the retinoic acid and/or metabolic precursor thereto are administered systemically. </p>
|
| 80 |
+
<p id="p-13" num="13">
|
| 81 |
+
<boundary-data type="line-number">
|
| 82 |
+
<confidence value="88">10</confidence>
|
| 83 |
+
</boundary-data>
|
| 84 |
+
The present invention also provides use of a combination of an LXR activator and retinoic acid and/or a metabolic precursor thereto in the manufacture of a composition for topical and/or systemic application for reducing chronoageing and/or photoageing of the skin. Such a composition includes both skin creams, <boundary-data type="line-number">
|
| 85 |
+
<confidence value="66">15</confidence>
|
| 86 |
+
</boundary-data>
|
| 87 |
+
lotions, oils etc (including sunscreen compositions) and personal wash products such as liquid or solid soaps, and bath or shower gels, creams etc. </p>
|
| 88 |
+
<p id="p-14" num="14">The present invention further provides a method of enhancing the effect of retinoic acid on skin cells which method comprises administering to the skin cells <boundary-data type="line-number">20 </boundary-data>
|
| 89 |
+
(i) an LXR activator and (ii) retinoic acid and/or a precursor thereto. Enhancing the effect of retinoic acid on skin cells, such as fibroblasts, includes enhancing expression of retinoic acid responsive genes such as CRAB P <confidence value="558">II.</confidence>
|
| 90 |
+
</p>
|
| 91 |
+
<p id="p-15" num="15">Detailed Desc<confidence value="656">rip</confidence>
|
| 92 |
+
tion of the <confidence value="5">I</confidence>
|
| 93 |
+
nvention <boundary-data type="line-number">25 </boundary-data>
|
| 94 |
+
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. </p>
|
| 95 |
+
<p id="p-16" num="16">LXR activatin<confidence value="8">g</confidence>
|
| 96 |
+
<confidence value="86">ag</confidence>
|
| 97 |
+
ents Any reference herein to an activator of LXR includes a reference to an activator <boundary-data type="line-number">30 </boundary-data>
|
| 98 |
+
of LXRa and/or of LXR<confidence value="1">/</confidence>
|
| 99 |
+
, unless specifically stated to the contrary. </p>
|
| 100 |
+
<p id="p-17" num="17">The LXR activating agents can be provided as pure or semi-pure compounds or as crude extracts of natural products, such as plant extracts.</p>
|
| 101 |
+
<boundary-data type="header">WO 2004/103320 PCT<confidence value="5">/</confidence>
|
| 102 |
+
EP2004/004942 </boundary-data>
|
| 103 |
+
<boundary-data type="header">
|
| 104 |
+
<confidence value="8">4</confidence>
|
| 105 |
+
</boundary-data>
|
| 106 |
+
<p id="p-18" num="18">
|
| 107 |
+
<page-break num="4"/>
|
| 108 |
+
A preferred class of LXR activators comprises the compounds according to the general formulae (A) or (B); </p>
|
| 109 |
+
<p id="p-19" num="19">R4 R R2 3 <boundary-data type="line-number">
|
| 110 |
+
<confidence value="8">5</confidence>
|
| 111 |
+
</boundary-data>
|
| 112 |
+
</p>
|
| 113 |
+
<heading id="h-2">(A)</heading>
|
| 114 |
+
<p id="p-20" num="20">
|
| 115 |
+
<confidence value="88">or</confidence>
|
| 116 |
+
</p>
|
| 117 |
+
<heading id="h-3">
|
| 118 |
+
<confidence value="7">R</confidence>
|
| 119 |
+
</heading>
|
| 120 |
+
<p id="p-21" num="21">
|
| 121 |
+
<confidence value="7">R</confidence>
|
| 122 |
+
<confidence value="7">4</confidence>
|
| 123 |
+
<confidence value="855">R10</confidence>
|
| 124 |
+
<confidence value="86">R2</confidence>
|
| 125 |
+
<confidence value="84">R5</confidence>
|
| 126 |
+
<boundary-data type="line-number">
|
| 127 |
+
<confidence value="88">10</confidence>
|
| 128 |
+
</boundary-data>
|
| 129 |
+
</p>
|
| 130 |
+
<heading id="h-4">(B)</heading>
|
| 131 |
+
<p id="p-22" num="22">wherein;</p>
|
| 132 |
+
<p id="p-23" num="23">
|
| 133 |
+
<confidence value="66">15</confidence>
|
| 134 |
+
R represents a hydrogen, a hydroxyl, a keto, an acetyl, a C<confidence value="4">,</confidence>
|
| 135 |
+
to C<confidence value="21">10</confidence>
|
| 136 |
+
, substituted or unsubstituted, branched or unbranched, saturated or unsaturated alkyl group; </p>
|
| 137 |
+
<boundary-data type="header">WO 2004/103320 PCT<confidence value="5">/</confidence>
|
| 138 |
+
EP2004/004942 </boundary-data>
|
| 139 |
+
<boundary-data type="header">
|
| 140 |
+
<confidence value="8">5</confidence>
|
| 141 |
+
</boundary-data>
|
| 142 |
+
<p id="p-24" num="24">
|
| 143 |
+
<page-break num="5"/>
|
| 144 |
+
<confidence value="86">R,</confidence>
|
| 145 |
+
represents a lower alkyl group, a hydrogen or COR<confidence value="58">e;</confidence>
|
| 146 |
+
</p>
|
| 147 |
+
<p id="p-25" num="25">R2 represents a hydrogen, a halogen or a hydroxyl group;</p>
|
| 148 |
+
<p id="p-26" num="26">R3 represents a hydrogen, a hydroxyl, a halogen, a keto or a lower alkyl group;</p>
|
| 149 |
+
<p id="p-27" num="27">
|
| 150 |
+
<confidence value="86">R4</confidence>
|
| 151 |
+
represents a hydrogen, a hydroxyl, or a keto group; </p>
|
| 152 |
+
<p id="p-28" num="28">
|
| 153 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 154 |
+
R<confidence value="5">s</confidence>
|
| 155 |
+
represents a hydrogen, a halogen, a hydroxyl or lower alkyl group; </p>
|
| 156 |
+
<p id="p-29" num="29">
|
| 157 |
+
<confidence value="82">R6</confidence>
|
| 158 |
+
represents a lower alkyl group. </p>
|
| 159 |
+
<p id="p-30" num="30">X represents a hydrogen, a methyl or a halogen;</p>
|
| 160 |
+
<p id="p-31" num="31">Y represents a hydrogen, a hydroxyl, a acetyl or a keto group.</p>
|
| 161 |
+
<p id="p-32" num="32">
|
| 162 |
+
<boundary-data type="line-number">
|
| 163 |
+
<confidence value="86">10</confidence>
|
| 164 |
+
</boundary-data>
|
| 165 |
+
One preferred class of LXR activating compound of formula (A) or (B) is that wherein the R represents -H, -OH, =0, -COCH3, -COHCH<confidence value="4">3</confidence>
|
| 166 |
+
, =CHCH2<confidence value="5">O</confidence>
|
| 167 |
+
H, or -OCOCH3. </p>
|
| 168 |
+
<p id="p-33" num="33">Another possible class of compounds of formulae (A) and (B) wherein R is C<confidence value="2">1</confidence>
|
| 169 |
+
to <boundary-data type="line-number">
|
| 170 |
+
<confidence value="66">15</confidence>
|
| 171 |
+
</boundary-data>
|
| 172 |
+
<confidence value="82">C8</confidence>
|
| 173 |
+
alkyl being substituted or unsubstituted, branched or unbranched and saturated or unsaturated with the proviso that when it is C<confidence value="1">8</confidence>
|
| 174 |
+
, it is unsaturated. </p>
|
| 175 |
+
<p id="p-34" num="34">In formulae A and B, the bond by which the R group is linked to the carbon at position <part-num-ref name="carbon at position">17</part-num-ref>
|
| 176 |
+
will depend on the nature of the R group (indicated by wavy bond). </p>
|
| 177 |
+
<p id="p-35" num="35">
|
| 178 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 179 |
+
Where R is a hydrogen or a hydroxyl group or acetyl group the bond will be saturated, whereas when R is a keto group the bond will be unsaturated. When R is an alkyl group this group may be linked to the carbon at position <part-num-ref name="carbon at position">17</part-num-ref>
|
| 180 |
+
via a saturated or unsaturated bond, preferably this is an unsaturated bond. </p>
|
| 181 |
+
<p id="p-36" num="36">
|
| 182 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 183 |
+
For the purpose of the present invention R may represent a hydroxyl, a keto or an acetyl group. </p>
|
| 184 |
+
<p id="p-37" num="37">R may also represent a C<confidence value="5">1</confidence>
|
| 185 |
+
to C<confidence value="2">r</confidence>
|
| 186 |
+
(i.e. including C<confidence value="5">1</confidence>
|
| 187 |
+
,C2<confidence value="5">,</confidence>
|
| 188 |
+
C3,C4<confidence value="684684">,C5,C6</confidence>
|
| 189 |
+
and C<confidence value="68">7)</confidence>
|
| 190 |
+
substituted or unsubstituted, saturated or unsaturated, branched or unbranched <boundary-data type="line-number">
|
| 191 |
+
<confidence value="86">30</confidence>
|
| 192 |
+
</boundary-data>
|
| 193 |
+
alkyl group. Preferably said C<confidence value="5">,</confidence>
|
| 194 |
+
to C<confidence value="5">7</confidence>
|
| 195 |
+
alkyl group comprises at least one substituted group selected from hydroxyl, keto and acetyl groups and R may in particular represent substituted alkyl groups having two and three of said substitutions. More preferably the alkyl groups have undergone substitution with <page-break num="6"/>
|
| 196 |
+
<boundary-data type="header">WO 2004/103320 PCT<confidence value="5">/</confidence>
|
| 197 |
+
EP2004/004942 </boundary-data>
|
| 198 |
+
<boundary-data type="header">
|
| 199 |
+
<confidence value="8">6</confidence>
|
| 200 |
+
</boundary-data>
|
| 201 |
+
one or more keto or hydroxyl groups. Further preferred an alkyl R group is substituted at one or more positions corresponding or equivalent to C20, C21, C<confidence value="66">22</confidence>
|
| 202 |
+
and C<confidence value="66">23</confidence>
|
| 203 |
+
shown in figure 7. Where the substitution is with a keto group this is most preferably bonded to C<confidence value="65">20</confidence>
|
| 204 |
+
, whereas when substitution is with a hydroxyl group this <boundary-data type="line-number">5 </boundary-data>
|
| 205 |
+
is most preferably bonded to a carbon at C21 and <confidence value="66">/o</confidence>
|
| 206 |
+
r C<confidence value="668">22.</confidence>
|
| 207 |
+
</p>
|
| 208 |
+
<p id="p-38" num="38">It is preferred that the alkyl R group remains unbranched as this helps to maintain a favoured linear configuration, however in the event that the alkyl group is branch said branches preferably comprise <part-num-ref name="alkyl group is branch said branches preferably comprise">2</part-num-ref>
|
| 209 |
+
carbons, more preferably <part-num-ref name="carbons, more preferably">1</part-num-ref>
|
| 210 |
+
carbon. </p>
|
| 211 |
+
<p id="p-39" num="39">
|
| 212 |
+
<boundary-data type="line-number">
|
| 213 |
+
<confidence value="66">10</confidence>
|
| 214 |
+
</boundary-data>
|
| 215 |
+
Where the R group is an alkyl group as described above this will preferably have some degree of unsaturation. Preferably unsaturation occurs in the form of one or more substituted keto groups. </p>
|
| 216 |
+
<p id="p-40" num="40">
|
| 217 |
+
<boundary-data type="line-number">
|
| 218 |
+
<confidence value="66">15</confidence>
|
| 219 |
+
</boundary-data>
|
| 220 |
+
Where R represents an unsaturated C1 to C<confidence value="5">8</confidence>
|
| 221 |
+
alkyl group it is most preferred that this group has the formula -C(CH3)(CH2)2C<confidence value="5">=</confidence>
|
| 222 |
+
C(CH3)2.. </p>
|
| 223 |
+
<p id="p-41" num="41">In a preferred embodiment the R group of the LXR activating compound represents a hydrogen, a hydroxyl, a keto or an unsubstituted or, more <boundary-data type="line-number">20 </boundary-data>
|
| 224 |
+
preferably, substituted C1 to C<confidence value="5">4</confidence>
|
| 225 |
+
alkyl group. The latter comprise methyl, ethyl, n-propyl, isopropyl, n-butyl, isobutyl or ter-butyl. Preferably substitution occurs at <confidence value="864">C2o</confidence>
|
| 226 |
+
or C21 within the alkyl group. Where the R group is an alkyl group it is preferred that this is forms an unsaturated bond with C17 of the ring structure. </p>
|
| 227 |
+
<p id="p-42" num="42">
|
| 228 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 229 |
+
<confidence value="5">I</confidence>
|
| 230 |
+
n a most preferred embodiment R is selected from the group consisting of -H, -OH, =0, -COCH3, -COHCH<confidence value="4">3</confidence>
|
| 231 |
+
, =<confidence value="222225">CHCH3,</confidence>
|
| 232 |
+
=<confidence value="2222222">CHCH2OH</confidence>
|
| 233 |
+
, -OCOCH3 and C(CH3)(CH2)2C=C(CH3)2. </p>
|
| 234 |
+
<p id="p-43" num="43">A "lower alkyl" as employed herein includes both straight and branched chain <confidence value="86">30</confidence>
|
| 235 |
+
radicals of up to four carbon atoms, examples of suitable groups are outlined above. In a preferred embodiment R1 is a hydrogen. </p>
|
| 236 |
+
<boundary-data type="header">WO 2004/103320 PCT<confidence value="5">/</confidence>
|
| 237 |
+
EP2004/004942 </boundary-data>
|
| 238 |
+
<boundary-data type="header">
|
| 239 |
+
<confidence value="8">7</confidence>
|
| 240 |
+
</boundary-data>
|
| 241 |
+
<p id="p-44" num="44">
|
| 242 |
+
<page-break num="7"/>
|
| 243 |
+
R2 represents a hydrogen, a halogen preferably chlorine or a hydroxyl group, preferably R2 represents a hydrogen. </p>
|
| 244 |
+
<p id="p-45" num="45">R3 represents a hydrogen, a halogen preferably a fluorine or chlorine, a keto or a <boundary-data type="line-number">5 </boundary-data>
|
| 245 |
+
lower alkyl group. Preferably R<confidence value="5">3</confidence>
|
| 246 |
+
is either a keto group or a hydrogen. In a most preferred embodiment R3 is a hydrogen. </p>
|
| 247 |
+
<p id="p-46" num="46">Preferably R4 and R<confidence value="5">5</confidence>
|
| 248 |
+
represent a hydroxyl group or hydrogen, most preferably these represent a hydrogen. </p>
|
| 249 |
+
<p id="p-47" num="47">
|
| 250 |
+
<boundary-data type="line-number">
|
| 251 |
+
<confidence value="88">10</confidence>
|
| 252 |
+
</boundary-data>
|
| 253 |
+
<confidence value="82">R6</confidence>
|
| 254 |
+
represents a lower alkyl, preferably a methyl group. </p>
|
| 255 |
+
<p id="p-48" num="48">X preferably represents a hydrogen, a fluorine or a chlorine, most preferably X is a hydrogen.</p>
|
| 256 |
+
<p id="p-49" num="49">
|
| 257 |
+
<boundary-data type="line-number">
|
| 258 |
+
<confidence value="88">15</confidence>
|
| 259 |
+
</boundary-data>
|
| 260 |
+
Preferably Y represents a hydrogen, a hydroxyl or a keto group. </p>
|
| 261 |
+
<p id="p-50" num="50">When Y is a hydrogen, in a compound according to general formula A, a double bond may form between C1<confidence value="5">6</confidence>
|
| 262 |
+
and C17. </p>
|
| 263 |
+
<p id="p-51" num="51">
|
| 264 |
+
<boundary-data type="line-number">
|
| 265 |
+
<confidence value="88">20</confidence>
|
| 266 |
+
</boundary-data>
|
| 267 |
+
In a compound according to formula B, when Y is hydrogen R<confidence value="5">1</confidence>
|
| 268 |
+
is a preferably hydrogen or -COR<confidence value="4">E</confidence>
|
| 269 |
+
. Preferably when Y is a keto group the activating molecule conforms to general formula A, whereas, when Y is a hydroxyl group the activating molecule preferably conforms to general formula B. </p>
|
| 270 |
+
<p id="p-52" num="52">
|
| 271 |
+
<boundary-data type="line-number">
|
| 272 |
+
<confidence value="88">25</confidence>
|
| 273 |
+
</boundary-data>
|
| 274 |
+
In a most preferred embodiment the activating compound conforms to formula A wherein Y is a keto group. </p>
|
| 275 |
+
<p id="p-53" num="53">Where R is a hydrogen or a hydroxyl group, Y is preferably a keto group in an <boundary-data type="line-number">
|
| 276 |
+
<confidence value="86">30</confidence>
|
| 277 |
+
</boundary-data>
|
| 278 |
+
activating compound according to formula A. </p>
|
| 279 |
+
<p id="p-54" num="54">Where R is -COCH<confidence value="4">3</confidence>
|
| 280 |
+
, Y is preferably a hydrogen or a keto group in a activating compound according to either A or B, preferably according to formula A. </p>
|
| 281 |
+
<boundary-data type="header">WO 2004/103320 PCT<confidence value="5">/</confidence>
|
| 282 |
+
EP2004/004942 </boundary-data>
|
| 283 |
+
<boundary-data type="header">
|
| 284 |
+
<confidence value="8">8</confidence>
|
| 285 |
+
</boundary-data>
|
| 286 |
+
<p id="p-55" num="55">
|
| 287 |
+
<page-break num="8"/>
|
| 288 |
+
Where R is =CHCH3 or -OCOCH<confidence value="45">3,</confidence>
|
| 289 |
+
Y is most preferably a keto group in an activating compound according to general formula A. </p>
|
| 290 |
+
<p id="p-56" num="56">
|
| 291 |
+
<boundary-data type="line-number">
|
| 292 |
+
<confidence value="5">5</confidence>
|
| 293 |
+
</boundary-data>
|
| 294 |
+
Where R is =CHCH2<confidence value="5">O</confidence>
|
| 295 |
+
H, Y is preferably either; a hydrogen in an activating compound according to general formula A, wherein R4 is preferably a hydroxyl group; or a hydroxyl group in an activating compound according to formula B wherein R<confidence value="5">1</confidence>
|
| 296 |
+
is a hydrogen. </p>
|
| 297 |
+
<p id="p-57" num="57">
|
| 298 |
+
<boundary-data type="line-number">
|
| 299 |
+
<confidence value="66">10</confidence>
|
| 300 |
+
</boundary-data>
|
| 301 |
+
Where R is C(CH3)(CH2)2C=C(CH3)2<confidence value="5">.</confidence>
|
| 302 |
+
Y is preferably a hydrogen in an activating compound according to formula B wherein R<confidence value="5">1</confidence>
|
| 303 |
+
is also a hydrogen. </p>
|
| 304 |
+
<p id="p-58" num="58">Some preferred LXR activators are selected from 4-androsten-3,<confidence value="5">1</confidence>
|
| 305 |
+
6-dione, 4- androsten-3,<confidence value="5">1</confidence>
|
| 306 |
+
6-dione, androst-4-ene-3,6,<confidence value="8">1</confidence>
|
| 307 |
+
6-t<confidence value="66">ri</confidence>
|
| 308 |
+
one, 4-androsten-17beta-o<confidence value="4">l</confidence>
|
| 309 |
+
-3,16- <boundary-data type="line-number">
|
| 310 |
+
<confidence value="55">15</confidence>
|
| 311 |
+
</boundary-data>
|
| 312 |
+
<confidence value="87">do</confidence>
|
| 313 |
+
ne acetate, <confidence value="5">1</confidence>
|
| 314 |
+
6-ketotestosterone, 3<confidence value="1">Q</confidence>
|
| 315 |
+
-acetoxypregna-5,<confidence value="8">1</confidence>
|
| 316 |
+
6-dien-20-one, 3<confidence value="18">/-</confidence>
|
| 317 |
+
acetoxypregna-5-en-20-one, 3<confidence value="11">/3</confidence>
|
| 318 |
+
-hydroxypregna-5,<confidence value="8">1</confidence>
|
| 319 |
+
6-dien-20-one, 3<confidence value="18">Q-</confidence>
|
| 320 |
+
hydroxypregna-5-en-20-one, 5,16-dien-pregnane-3,20-diol, 4,16-dienpregna- 3,20-dione, 4,17(20)-(cis)-pregnadien-3,<confidence value="8">1</confidence>
|
| 321 |
+
6-dione, 4,17(20)-(trans)-pregnadien- 3,16-dione, 4-pregnen-3,<confidence value="5">1</confidence>
|
| 322 |
+
6,20-t<confidence value="66">ri</confidence>
|
| 323 |
+
one, 4,17(20)-pregnadien-1<confidence value="8">1</confidence>
|
| 324 |
+
beta,2<confidence value="5">1</confidence>
|
| 325 |
+
-diol-3-one, <boundary-data type="line-number">20 </boundary-data>
|
| 326 |
+
5,17(20)-pregnadien-3,<confidence value="8">1</confidence>
|
| 327 |
+
6-diol-diacetate, 5,17(20)-pregnadien-3,<confidence value="8">1</confidence>
|
| 328 |
+
6-diol, 5- pregnen-3beta,<confidence value="5">1</confidence>
|
| 329 |
+
6alpha,2<confidence value="8">1</confidence>
|
| 330 |
+
-triol-20-one, 24-hydroxychol-4-en-3-one, cholesta- 5,24-<confidence value="5">d</confidence>
|
| 331 |
+
ien-3<confidence value="1">Q</confidence>
|
| 332 |
+
-ol, cis-guggal sterone and desmosterol, and mixtures thereof. </p>
|
| 333 |
+
<p id="p-59" num="59">In an especially preferred embodiment, the LXR activator is 4,17(20)-(cis)- <boundary-data type="line-number">25 </boundary-data>
|
| 334 |
+
pregnadien-3,16-dione. </p>
|
| 335 |
+
<p id="p-60" num="60">The preparation of compounds of formulae (A) and (B) has been described in the literature and/or are commercially available e.g. from Sigma Chemical Company.</p>
|
| 336 |
+
<p id="p-61" num="61">
|
| 337 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 338 |
+
It is also possible to provide the LXR activator(s) in the form of one or more extracts of natural plant sources, e.g extracts of one or more of Commiphora mokul, Boswelta serrata, Dragon's blood resin (Daemorgos draco), apple peel, <page-break num="9"/>
|
| 339 |
+
<boundary-data type="header">WO 2004/103320 PCT<confidence value="5">/</confidence>
|
| 340 |
+
EP2004/004942 </boundary-data>
|
| 341 |
+
<boundary-data type="header">
|
| 342 |
+
<confidence value="8">9</confidence>
|
| 343 |
+
</boundary-data>
|
| 344 |
+
allspice, clove, Damar gum (exudate of Damar tree, Nettle (Lamium albim<confidence value="66">),</confidence>
|
| 345 |
+
red seaweed, Breuzihno resin, mastic gum, mountain ash berry and plantain. </p>
|
| 346 |
+
<p id="p-62" num="62">A plant extract differs from the intact plant material in that the various <boundary-data type="line-number">5 </boundary-data>
|
| 347 |
+
components present in the intact plant material will be present in different amounts in the extract, or substantially absent. Prior to extraction, plant materials may be dried and or mechanically processed, e.g. crushed. </p>
|
| 348 |
+
<p id="p-63" num="63">Extracts of plant materials are typically made by solvent extraction. Suitable <boundary-data type="line-number">
|
| 349 |
+
<confidence value="66">10</confidence>
|
| 350 |
+
</boundary-data>
|
| 351 |
+
solvents are those in which LXR activators are soluble. Since LXR activators are typically sterols/steroids, suitable solvents include organic solvents such as hexane, chloroform, benzene, petroleum ether, <confidence value="222222222222222">dichloromethane</confidence>
|
| 352 |
+
, acetone, ether, diethyl ether, ethyl acetate and mixtures of the above. Solvents may also include alcohols such as methanol, ethanol and isopropyl alcohol and mixtures thereof, <boundary-data type="line-number">15 </boundary-data>
|
| 353 |
+
optionally mixtures with water. Preferred solvents are those which are acceptable for use in products destined for human or animal use. Plant materials can also be extracted with supercritical liquid C<confidence value="588">02.</confidence>
|
| 354 |
+
</p>
|
| 355 |
+
<p id="p-64" num="64">Extraction methods include batch extraction and soxhlet extraction at <boundary-data type="line-number">20 </boundary-data>
|
| 356 |
+
temperatures up to the solvent boiling point. Extraction procedures may therefore include a heating step. Solvent extracted components may be subject to further purification/separation steps such as chromatography or fractional distillation. As used herein, "fraction" means any fractioned part of a solvent containing one or more of the active ingredients described above, e.g. obtained by chromatography <boundary-data type="line-number">25 </boundary-data>
|
| 357 |
+
or by fractional distillation. </p>
|
| 358 |
+
<p id="p-65" num="65">Sterols/steroids represent the unsaponifiable fractions (unsaps) of seed oils and extracts. These are components that cannot be converted to soaps (e.g. non fatty acid/glyceride material). In some extracts e.g. from oils, the unsaps can be <boundary-data type="line-number">
|
| 359 |
+
<confidence value="86">30</confidence>
|
| 360 |
+
</boundary-data>
|
| 361 |
+
enriched by a process of saponification. A suitable method is as follows: </p>
|
| 362 |
+
<p id="p-66" num="66">The lipid extract (<confidence value="55">-1</confidence>
|
| 363 |
+
g) from e.g. hexane and methanol extractions is refluxed with 2M potassium hydroxide in ethanol for <part-num-ref name="hexane and methanol extractions is refluxed with 2M potassium hydroxide in ethanol for">1</part-num-ref>
|
| 364 |
+
hour. After cooling the mixture is shaken <page-break num="10"/>
|
| 365 |
+
<boundary-data type="header">WO 2004/103320 PCT<confidence value="5">/</confidence>
|
| 366 |
+
EP2004<confidence value="5">/</confidence>
|
| 367 |
+
004942 </boundary-data>
|
| 368 |
+
<boundary-data type="header">
|
| 369 |
+
<confidence value="88">10</confidence>
|
| 370 |
+
</boundary-data>
|
| 371 |
+
with diethyl ether. The upper solvent layer containing the <confidence value="22222222222222">unsaponifiable</confidence>
|
| 372 |
+
fraction is removed and washed twice with water, dried by passing through a column of sodium sulphate and the solvent removed by evaporation under nitrogen at -70<confidence value="4">0</confidence>
|
| 373 |
+
C. This represents the unsaponifiable material (e.g. sterols). </p>
|
| 374 |
+
<p id="p-67" num="67">
|
| 375 |
+
<boundary-data type="line-number">
|
| 376 |
+
<confidence value="8">5</confidence>
|
| 377 |
+
</boundary-data>
|
| 378 |
+
Preferably the composition according to the first aspect of the present invention comprises at least one LXR activator other than a sterol, in particular at least one LXR activator other than any sterol disclosed in US-A-5 <part-num-ref name="sterol, in particular at least one LXR activator other than any sterol disclosed in US-A-5">587</part-num-ref>
|
| 379 |
+
<part-num-ref name="">367.</part-num-ref>
|
| 380 |
+
</p>
|
| 381 |
+
<p id="p-68" num="68">
|
| 382 |
+
<boundary-data type="line-number">
|
| 383 |
+
<confidence value="66">10</confidence>
|
| 384 |
+
</boundary-data>
|
| 385 |
+
Preferably 25-hydroxycholesterol is specifically excluded. </p>
|
| 386 |
+
<p id="p-69" num="69">Preferably, dehydroepiandrosterone and its derivatives are specifically excluded.</p>
|
| 387 |
+
<p id="p-70" num="70">Retinoic Acid and Its Metabolic Precursors <boundary-data type="line-number">
|
| 388 |
+
<confidence value="66">15</confidence>
|
| 389 |
+
</boundary-data>
|
| 390 |
+
Compositions of the present invention contain retinoic acid and/or one of its metabolic precursors. Many retinoic acid metabolic precursors are commonly known as retinoids. A non-limiting list of such precursors includes those disclosed in US-A-5,587,367. Examples of the latter include all trans or 13-cis retinoic acid, vitamin A or retinol, as well as its esters such as the acetate, <boundary-data type="line-number">20 </boundary-data>
|
| 391 |
+
pr<confidence value="7">o</confidence>
|
| 392 |
+
pionate or palmitate of retinol and the aldehyde of vitamin A or retinal. </p>
|
| 393 |
+
<p id="p-71" num="71">Some preferred retinoids are selected from retinyl esters, retinol, retinal and retinoic acid, preferably retinol or retinyl ester and mixtures thereof. The term "retin<confidence value="8">o</confidence>
|
| 394 |
+
l" includes the following isomers of retinol: all-trans-retin<confidence value="5">o</confidence>
|
| 395 |
+
l, 13-cis-retinol, <boundary-data type="line-number">25 </boundary-data>
|
| 396 |
+
11-cis-retinol, 9-cis-retin<confidence value="5">o</confidence>
|
| 397 |
+
l, 3,4-didehydro-retinol, 3,4-didehydro-13-cis-retin<confidence value="588">ol;</confidence>
|
| 398 |
+
</p>
|
| 399 |
+
<p id="p-72" num="72">3,4-didehydro-1<confidence value="5">1</confidence>
|
| 400 |
+
-cis-retinol; 3,4-didehydro-9-cis-retinol and mixtures thereof. </p>
|
| 401 |
+
<p id="p-73" num="73">Preferred isomers are all-trans-retinol, <confidence value="5">1</confidence>
|
| 402 |
+
3-cis-retinol, 3,4-didehydro-retinol, 9-cis- retin<confidence value="5">o</confidence>
|
| 403 |
+
l. Most preferred is all-trans-retin<confidence value="5">o</confidence>
|
| 404 |
+
l, due to its wide commercial availability. </p>
|
| 405 |
+
<p id="p-74" num="74">
|
| 406 |
+
<boundary-data type="line-number">
|
| 407 |
+
<confidence value="85">30</confidence>
|
| 408 |
+
</boundary-data>
|
| 409 |
+
Retinyl ester is an ester of retin<confidence value="8">o</confidence>
|
| 410 |
+
l. The term "retin<confidence value="8">o</confidence>
|
| 411 |
+
l" has been defined above. </p>
|
| 412 |
+
<p id="p-75" num="75">Retinyl esters suitable for use in the present invention are C <confidence value="488">i-C</confidence>
|
| 413 |
+
<part-num-ref name="present invention are C i-C">
|
| 414 |
+
<confidence value="65">30</confidence>
|
| 415 |
+
</part-num-ref>
|
| 416 |
+
esters of retinol, preferably C 2-C <part-num-ref name="esters of retinol, preferably C 2-C">
|
| 417 |
+
<confidence value="85">20</confidence>
|
| 418 |
+
</part-num-ref>
|
| 419 |
+
esters, and most preferably C <part-num-ref name="esters, and most preferably C">2,</part-num-ref>
|
| 420 |
+
C <part-num-ref name="esters, and most preferably C 2, C">3,</part-num-ref>
|
| 421 |
+
and C <part-num-ref name="esters, and most preferably C 2, C 3, and C">
|
| 422 |
+
<confidence value="52">16</confidence>
|
| 423 |
+
</part-num-ref>
|
| 424 |
+
esters because they are m<confidence value="8">o</confidence>
|
| 425 |
+
re commonly available. Examples of retinyl esters include <page-break num="11"/>
|
| 426 |
+
<boundary-data type="header">WO 2004/103320 PCT<confidence value="5">/</confidence>
|
| 427 |
+
EP2004<confidence value="5">/</confidence>
|
| 428 |
+
004942 </boundary-data>
|
| 429 |
+
<boundary-data type="header">
|
| 430 |
+
<confidence value="88">11</confidence>
|
| 431 |
+
</boundary-data>
|
| 432 |
+
but are not limited to: <confidence value="2222222">retinyl</confidence>
|
| 433 |
+
palmitate, retinyl formate, retinyl acetate, retinyl propionate, retinyl butyrate, retinyl valerate, retinyl isovalerate, <confidence value="2222222">retinyl</confidence>
|
| 434 |
+
hexanoate, retinyl heptanoate, retinyl octanoate, retinyl nonanoate, retinyl decanoate, retinyl undecandate, retinyl laurate, retinyl <confidence value="222222222222">tridecanoate</confidence>
|
| 435 |
+
, retinyl myristate, retinyl <boundary-data type="line-number">5 </boundary-data>
|
| 436 |
+
pentadecanoate, retinyl heptadeconoate, retinyl stearate, retinyl isostearate, retinyl nonadecanoate, retinyl arachidonate, retinyl behenate, retinyl linoleate, retinyl oleate. </p>
|
| 437 |
+
<p id="p-76" num="76">Preferred esters for use in the present invention are selected from retinyl <boundary-data type="line-number">10 </boundary-data>
|
| 438 |
+
palmitate, retinyl acetate and retinyl propionate and mixtures thereof, because these are the most commercially available and therefore the cheapest. Retinyl linoleate and retinyl oleate are also preferred due to their efficacy. </p>
|
| 439 |
+
<p id="p-77" num="77">Formulations <boundary-data type="line-number">
|
| 440 |
+
<confidence value="66">15</confidence>
|
| 441 |
+
</boundary-data>
|
| 442 |
+
<confidence value="6">I</confidence>
|
| 443 |
+
n a composition according to the invention, the amount of LXR activator, or mixtures thereof, is preferably from 0.00001 wt% to <part-num-ref name="amount of LXR activator, or mixtures thereof, is preferably from 0.00001 wt% to">50</part-num-ref>
|
| 444 |
+
wt%, such as from 0.001 to <part-num-ref name="wt%, such as from 0.001 to">35</part-num-ref>
|
| 445 |
+
wt%, more preferably from 0.01% to 10%, most preferably from 0.01 wt% to <part-num-ref name="wt%, more preferably from 0.01% to 10%, most preferably from 0.01 wt% to">
|
| 446 |
+
<confidence value="5">1</confidence>
|
| 447 |
+
</part-num-ref>
|
| 448 |
+
wt%. The amount of retinoic acid and/or metabolic precursor is preferably from 0.00001 % to 50%, such as from 0.001 to <part-num-ref name="amount of retinoic acid and/or metabolic precursor is preferably from 0.00001 % to 50%, such as from 0.001 to">35</part-num-ref>
|
| 449 |
+
wt%, more preferably from 0.001<confidence value="8">%</confidence>
|
| 450 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 451 |
+
to 10%, still more preferably from 0.01% to 1%, most preferably from 0.01% to 0.5% by weight. </p>
|
| 452 |
+
<p id="p-78" num="78">Preferably, at least one LXR activator and the retinoic acid or metabolic precursor thereof are obtained from different sources.</p>
|
| 453 |
+
<p id="p-79" num="79">
|
| 454 |
+
<boundary-data type="line-number">
|
| 455 |
+
<confidence value="88">25</confidence>
|
| 456 |
+
</boundary-data>
|
| 457 |
+
The composition is typically formulated for topical application or systemic application. </p>
|
| 458 |
+
<p id="p-80" num="80">A topical composition for reducing chronoageing and/or photoageing of the skin <part-num-ref name="skin">30</part-num-ref>
|
| 459 |
+
preferably comprises the LXR activator, the retinoic acid and/or metabolic precursor and a dermatologically acceptable vehicle. </p>
|
| 460 |
+
<boundary-data type="header">WO 2004/103320 PCT<confidence value="5">/</confidence>
|
| 461 |
+
EP2004/004942 </boundary-data>
|
| 462 |
+
<boundary-data type="header">
|
| 463 |
+
<confidence value="88">12</confidence>
|
| 464 |
+
</boundary-data>
|
| 465 |
+
<p id="p-81" num="81">
|
| 466 |
+
<page-break num="12"/>
|
| 467 |
+
A systemic composition for reducing chronoageing and/or photoageing of the skin preferably comprises the LXR activator, the retinoic acid and/or metabolic precursor and a physiologically acceptable vehicle. </p>
|
| 468 |
+
<p id="p-82" num="82">
|
| 469 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 470 |
+
To<confidence value="5">p</confidence>
|
| 471 |
+
ical formulations A topical composition according to the invention will usually contain a dermatologically acceptable vehic<confidence value="8">l</confidence>
|
| 472 |
+
e. A dermatologically acceptable vehicle acts as a dilutant, dispersant or carr<confidence value="8">i</confidence>
|
| 473 |
+
er for the LXR activator(s) and retinoic acid and/or metabolic precursor(s) in the composition, so as to facilitate its distribution <boundary-data type="line-number">
|
| 474 |
+
<confidence value="86">10</confidence>
|
| 475 |
+
</boundary-data>
|
| 476 |
+
when the composition is topically applied. </p>
|
| 477 |
+
<p id="p-83" num="83">Dermatologically acceptable vehicles other than water can include liquid or solid emollients, solvents, humectants, thickeners and powders. Examples of each of these types of vehicle which can be used singly or as mixtures of one or more <boundary-data type="line-number">
|
| 478 |
+
<confidence value="66">15</confidence>
|
| 479 |
+
</boundary-data>
|
| 480 |
+
vehicles, are as follows: </p>
|
| 481 |
+
<p id="p-84" num="84">Emollients, such as stearyl alcohol, glycerol monoricinoleate, glycerol monostearate, mink oil, cetyl alcohol, isopropyl isostearate, stearic acid, isobutyl palmitate, <confidence value="22222222">isocetyl</confidence>
|
| 482 |
+
stearate, oleyl alcohol, isopropyl luarate, hexyl laurate, decyl <boundary-data type="line-number">20 </boundary-data>
|
| 483 |
+
oleate, octadecan-2-ol, isocetyl alcohol, eicosanylalcohol, behenyl alcohol, <confidence value="22222">cetyl</confidence>
|
| 484 |
+
palmitate, silicone oils such as dimethylpolysiloxane, di-n-buty<confidence value="5">l</confidence>
|
| 485 |
+
sebacate, isopropyl <confidence value="222222222">myristate</confidence>
|
| 486 |
+
, isopropyl palmitate, isopropyl stearate, butyl stearate, polyethylene glycol, triethylene glycol, lanolin, cocoa butter, corn oil, cotton seed oil, tallow, lard, olive oil, palm kernal oil, rapeseed oil, safflower seed oil, evening <boundary-data type="line-number">25 </boundary-data>
|
| 487 |
+
primrose oil, soybean oil, sunflower seed oil, avocado oil, olive oil, sesame seed oil, coconut oil, arachis oil, castor oil, acetylated lanolin alcohols, petroleum jelly, mineral oil, butyl myristate, isostearic acid, palmitic acid, isopropyl linoleate, lauryl lactate, myristyl lactate, decyl oleate, myristyl myristate; </p>
|
| 488 |
+
<p id="p-85" num="85">
|
| 489 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 490 |
+
Propellants such as trichlorofluoromethane, dichlorodifluoro- methane, <confidence value="2222222222222222222222222">dichlorotetrafluoroethane</confidence>
|
| 491 |
+
, <confidence value="2222222222222222222222222">monochlorodifluoromethane</confidence>
|
| 492 |
+
, trichlorotrifluoroethane, propane, butane isobutanem demethyl ether, carbon dioxide, nitrous oxide; </p>
|
| 493 |
+
<boundary-data type="header">
|
| 494 |
+
<confidence value="88">WO</confidence>
|
| 495 |
+
2004/103320 PCT<confidence value="5">/</confidence>
|
| 496 |
+
EP2004<confidence value="5">/</confidence>
|
| 497 |
+
004942 </boundary-data>
|
| 498 |
+
<boundary-data type="header">
|
| 499 |
+
<confidence value="88">13</confidence>
|
| 500 |
+
</boundary-data>
|
| 501 |
+
<p id="p-86" num="86">
|
| 502 |
+
<page-break num="13"/>
|
| 503 |
+
Solvents such as ethyl alcohol, methylene chloride, isopropanol, acetone, ethylene glycol monoethyl ether, diethlyene glycol monobutyl ether, diethylene glycol monoethyl ether, dimethyl <confidence value="2222222222">sulphoxide</confidence>
|
| 504 |
+
, dimethyl formamide, tetrahydrofuran<confidence value="5">;</confidence>
|
| 505 |
+
</p>
|
| 506 |
+
<p id="p-87" num="87">
|
| 507 |
+
<boundary-data type="line-number">
|
| 508 |
+
<confidence value="8">5</confidence>
|
| 509 |
+
</boundary-data>
|
| 510 |
+
Powders, such as chalk, talc, fullers earth, kaolin, starch, gums, colloidal silica sodium polacrylate, tetre alkyl and/or trialkyl aryl ammonium smectites, chemically modified magnesium aluminium silicate, organically modified montmorillonite clay, hydrated aluminium silicate, fumed silica, carboxyvinyl <boundary-data type="line-number">10 </boundary-data>
|
| 511 |
+
polmer, sodium carboxymethyl cellulose, ethylene glycol monostearate. </p>
|
| 512 |
+
<p id="p-88" num="88">The dermatologically acceptable vehicle will usually form from 10 to 99.99 wt <confidence value="66">%,</confidence>
|
| 513 |
+
preferably from <part-num-ref name="to 99.99 wt %, preferably from">50</part-num-ref>
|
| 514 |
+
to <part-num-ref name="to">99</part-num-ref>
|
| 515 |
+
wt% of the final composition ready for use by the consumer. </p>
|
| 516 |
+
<p id="p-89" num="89">
|
| 517 |
+
<boundary-data type="line-number">
|
| 518 |
+
<confidence value="88">15</confidence>
|
| 519 |
+
</boundary-data>
|
| 520 |
+
The composition may also comprise water, usually up to <part-num-ref name="composition may also comprise water, usually up to">98</part-num-ref>
|
| 521 |
+
% volume, preferably <part-num-ref name="% volume, preferably">5</part-num-ref>
|
| 522 |
+
to <part-num-ref name="to">80</part-num-ref>
|
| 523 |
+
% volume of said final composition. </p>
|
| 524 |
+
<p id="p-90" num="90">One class of embodiments comprises a cosmetic method of providing at least <boundary-data type="line-number">20 </boundary-data>
|
| 525 |
+
one skin care benefit selected from preventing or reducing wrinkles, fine lines, sagging, loss of elasticity, loss of firmness, dermal and/or epidermal thinning, age spots and loss of "shine/vitality/glow/radiance", the method comprising applying to the skin, a topical composition of the invention as described above. </p>
|
| 526 |
+
<p id="p-91" num="91">
|
| 527 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 528 |
+
A topical or skin composition of the invention can be formulated as a lotion having a viscosity of from 4,000 to 10,000 mPas, a fluid cream having a viscosity of from 10,000 to 20,000 mPas or a cream having a viscosity of from 20,000 to 100,000 mPas or above at a temperature of 20<confidence value="1">°</confidence>
|
| 529 |
+
C. The composition may be packaged in a container to suit its viscosity and intended use by the consumer. </p>
|
| 530 |
+
<p id="p-92" num="92">
|
| 531 |
+
<boundary-data type="line-number">
|
| 532 |
+
<confidence value="86">30</confidence>
|
| 533 |
+
</boundary-data>
|
| 534 |
+
For example a lotion or fluid cream can be packaged in a bottle or a roll-ball applicator or a propellant driven aerosol device or a container fitted with a pump suitable for finger operation. When the composition is a cream, it can simply be <page-break num="14"/>
|
| 535 |
+
<boundary-data type="header">WO 2004/103320 PCT<confidence value="5">/</confidence>
|
| 536 |
+
EP2004/004942 </boundary-data>
|
| 537 |
+
<boundary-data type="header">
|
| 538 |
+
<confidence value="88">14</confidence>
|
| 539 |
+
</boundary-data>
|
| 540 |
+
stored in a non-deformable bottle or a squeeze container, such as a tub or a lidded jar. </p>
|
| 541 |
+
<p id="p-93" num="93">As already mentioned, compositions of the invention for topical application <boundary-data type="line-number">
|
| 542 |
+
<confidence value="5">5</confidence>
|
| 543 |
+
</boundary-data>
|
| 544 |
+
include personal wash compositions such as liquid soaps, solid soaps, gels, and oils for washing in either the bath or in a shower or for use as a skin <confidence value="222222222222">moisturising</confidence>
|
| 545 |
+
or conditioning product in shower or bath. </p>
|
| 546 |
+
<p id="p-94" num="94">The present invention relates to cosmetic methods of methods of reducing <boundary-data type="line-number">
|
| 547 |
+
<confidence value="86">10</confidence>
|
| 548 |
+
</boundary-data>
|
| 549 |
+
chronoageing and/or photoageing of the skin. The present invention also relates to methods of enhancing the effect of retinoic acid on skin cells. In one embodiment, such methods comprise the administration of a safe and effective amount of a composition of the invention to the skin or regions thereof. The amount of active agent and frequency of application will vary depending on the <boundary-data type="line-number">15 </boundary-data>
|
| 550 |
+
initial condition of the skin and the desired end result. </p>
|
| 551 |
+
<p id="p-95" num="95">A safe and effective amount of active in a topical composition is applied, generally from about <part-num-ref name="topical composition is applied, generally from about">
|
| 552 |
+
<confidence value="5">1</confidence>
|
| 553 |
+
</part-num-ref>
|
| 554 |
+
<confidence value="6">p</confidence>
|
| 555 |
+
g to about <part-num-ref name="pg to about">
|
| 556 |
+
<confidence value="5">1</confidence>
|
| 557 |
+
</part-num-ref>
|
| 558 |
+
mg per cm2 skin per application, preferably from about <part-num-ref name="mg per cm2 skin per application, preferably from about">2</part-num-ref>
|
| 559 |
+
<confidence value="5">p</confidence>
|
| 560 |
+
g to about <part-num-ref name="pg to about">800</part-num-ref>
|
| 561 |
+
<confidence value="22222">pg/cm</confidence>
|
| 562 |
+
2 skin per application, more preferably from <boundary-data type="line-number">
|
| 563 |
+
<confidence value="86">20</confidence>
|
| 564 |
+
</boundary-data>
|
| 565 |
+
about <part-num-ref name="pg/cm2 skin per application, more preferably from about">30</part-num-ref>
|
| 566 |
+
<confidence value="5">p</confidence>
|
| 567 |
+
g to about <part-num-ref name="pg to about">700</part-num-ref>
|
| 568 |
+
<confidence value="22222">pg/cm</confidence>
|
| 569 |
+
2 skin, most preferably from about <part-num-ref name="pg/cm2 skin, most preferably from about">75</part-num-ref>
|
| 570 |
+
<confidence value="5">p</confidence>
|
| 571 |
+
g to about <part-num-ref name="pg to about">250</part-num-ref>
|
| 572 |
+
<confidence value="22222">pg/cm</confidence>
|
| 573 |
+
2 skin. Frequency of application typically ranges from about four times a day to about twice a week, more preferably from about three times a day to about once every other day, more preferably at least twice daily. It is generally preferred that at least one application occurs in the evening. </p>
|
| 574 |
+
<p id="p-96" num="96">
|
| 575 |
+
<boundary-data type="line-number">
|
| 576 |
+
<confidence value="88">25</confidence>
|
| 577 |
+
</boundary-data>
|
| 578 |
+
Systemic formulations A composition according to the present invention for systemic administration may for example be adapted for oral administration, e.g. in the form of a tablet, lozenge, capsule, liquid (e.g <confidence value="5">.</confidence>
|
| 579 |
+
syrup or linctus) or as an injection (e.g. </p>
|
| 580 |
+
<p id="p-97" num="97">
|
| 581 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 582 |
+
subcutaneous or intramuscular ) or infusion or as a suppository. Typical such formulation techniques and appropriate pharmacologically acceptable carriers are well known to those skilled in the art. Suitable compositions for oral <page-break num="15"/>
|
| 583 |
+
<boundary-data type="header">WO 2004/103320 PCT<confidence value="5">/</confidence>
|
| 584 |
+
EP2004<confidence value="5">/</confidence>
|
| 585 |
+
004942 </boundary-data>
|
| 586 |
+
<boundary-data type="header">
|
| 587 |
+
<confidence value="88">15</confidence>
|
| 588 |
+
</boundary-data>
|
| 589 |
+
administration include those adapted for delayed release and/or for release in the lower gastrointestinal tract. </p>
|
| 590 |
+
<p id="p-98" num="98">The amount of the active ingredients administered depends upon the <boundary-data type="line-number">5 </boundary-data>
|
| 591 |
+
bioavailability of the compound from the composition, in particular where oral administration is used. Typically, however, the LXR activating agents and the retinoic acid or precursor thereto are each dosed in an amount of from about 0.01 mg/kg of body weight to about <part-num-ref name="amount of from about 0.01 mg/kg of body weight to about">100</part-num-ref>
|
| 592 |
+
mg/kg, preferably from about 0.1 to about <part-num-ref name="mg/kg, preferably from about 0.1 to about">30</part-num-ref>
|
| 593 |
+
mg/kg of body weight. The amount of the composition depends upon the percent <boundary-data type="line-number">10 </boundary-data>
|
| 594 |
+
of compound within its formula, which is a function of the amount of the compound required per dose, its stability, release characteristics and other pharmaceutical parameters. The doses are typically administered from once or twice weekly to one or twice daily. </p>
|
| 595 |
+
<p id="p-99" num="99">
|
| 596 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 597 |
+
The routes of administration and dosages described are intended only as a guide since a skilled practitioner will be able to determine readily the optimum route of administration and dosage for any particular individual. </p>
|
| 598 |
+
<p id="p-100" num="100">Another means of systemic dosing comprises dosing any of the aforementioned <boundary-data type="line-number">20 </boundary-data>
|
| 599 |
+
compositions in a food product which therefore does not necessarily require use of a pharmacologically/pharmaceutically acceptable carrier. </p>
|
| 600 |
+
<p id="p-101" num="101">As used herein, the term "food products<confidence value="5">"</confidence>
|
| 601 |
+
includes both food products as such and beverages. Suitable food products as such include spreads, dairy products <boundary-data type="line-number">25 </boundary-data>
|
| 602 |
+
(including milk and yoghurts), desserts, convenience foods/snacks, breakfast cereals and cereal bars, ready-cook meals, bread and frozen confections such as ice creams, water ices and sorbets and yoghurt ice creams. Food products also include dietary/nutritional supplements. Suitable beverages include tea, tea- flavoured drinks, coffee, soft drinks (e.g. carbonated squashes etc) and fruit juice. </p>
|
| 603 |
+
<p id="p-102" num="102">
|
| 604 |
+
<boundary-data type="line-number">
|
| 605 |
+
<confidence value="88">30</confidence>
|
| 606 |
+
</boundary-data>
|
| 607 |
+
The food products are typically supplemented with the active ingredients of the invention so that they contain higher amounts of the active ingredient(s) than they would normally contain. </p>
|
| 608 |
+
<boundary-data type="header">WO 2004/103320 PCT<confidence value="5">/</confidence>
|
| 609 |
+
EP2004<confidence value="5">/</confidence>
|
| 610 |
+
004942 </boundary-data>
|
| 611 |
+
<boundary-data type="header">
|
| 612 |
+
<confidence value="88">16</confidence>
|
| 613 |
+
</boundary-data>
|
| 614 |
+
<p id="p-103" num="103">
|
| 615 |
+
<page-break num="16"/>
|
| 616 |
+
Another class of embodiments comprises a method of providing at least one skin care benefit selected from preventing or reducing wrinkles, fine lines, sagging, loss of elasticity, loss of firmness, dermal and/or epidermal thinning, age spots <boundary-data type="line-number">5 </boundary-data>
|
| 617 |
+
and loss of "shine/vitality/glow/radiance", the method comprising administering orally, a systemic composition of the invention as described above, or a food product of the invention as described above. The present invention also relates to methods of enhancing the effect of retinoic acid on skin cells by administering systemically, such as orally, a systemic composition of the invention as described <boundary-data type="line-number">
|
| 618 |
+
<confidence value="86">10</confidence>
|
| 619 |
+
</boundary-data>
|
| 620 |
+
above, or a food product of the invention as described above. </p>
|
| 621 |
+
<p id="p-104" num="104">The invention also provides a closed container containing a cosmetically acceptable composition as herein defined.</p>
|
| 622 |
+
<p id="p-105" num="105">
|
| 623 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 624 |
+
The present invention will now be described further with reference to the following examples which are illustrative only and non-limiting. </p>
|
| 625 |
+
<p id="p-106" num="106">Exam<confidence value="8">p</confidence>
|
| 626 |
+
le <confidence value="5">1</confidence>
|
| 627 |
+
<boundary-data type="line-number">
|
| 628 |
+
<confidence value="86">20</confidence>
|
| 629 |
+
</boundary-data>
|
| 630 |
+
This is an evaluation of the ability of LXR activators to enhance the effect of retinoic acid on retinoic acid mediated gene expression, (i) using a reporter gene assay and (ii) measuring levels of expression of CRABP<confidence value="66">II</confidence>
|
| 631 |
+
in fibroblast cells. This is a predictor of effects on reducing chronoageing and/or photoageing because the activity of the genes tested is associated with reversing the physiological <boundary-data type="line-number">25 </boundary-data>
|
| 632 |
+
changes induced by chronological ageing and/or photoageing. </p>
|
| 633 |
+
<p id="p-107" num="107">Re<confidence value="8">p</confidence>
|
| 634 |
+
orter Gene Assay The assay was performed by transient transfection of Cos-7 cells with a mixture of five DNA plasmids. These are <part-num-ref name="mixture of five DNA plasmids. These are">1)</part-num-ref>
|
| 635 |
+
RAR reporter gene construct (Gift from David <boundary-data type="line-number">30 </boundary-data>
|
| 636 |
+
Talmage, Columbia University, USA). Modified pCAT-promoter reporter vector (Chloramphenicol acetyltransferase reporter vector commercially available form Promega). Containing a tandem repeat of <part-num-ref name="tandem repeat of">5</part-num-ref>
|
| 637 |
+
RAR response elements (RAREs) corresponding to the RARE found in the mouse RARbeta gene promoter region. </p>
|
| 638 |
+
<boundary-data type="header">WO 2004/103320 PCT<confidence value="5">/</confidence>
|
| 639 |
+
EP2004/004942 </boundary-data>
|
| 640 |
+
<boundary-data type="header">
|
| 641 |
+
<confidence value="88">17</confidence>
|
| 642 |
+
</boundary-data>
|
| 643 |
+
<p id="p-108" num="108">
|
| 644 |
+
<page-break num="17"/>
|
| 645 |
+
2) Over-expressing RAR<confidence value="5">y</confidence>
|
| 646 |
+
construct (Gift from Thomas Perlmann, Karolinska <confidence value="8">I</confidence>
|
| 647 |
+
nstitute, Sweden). Modified pCMX vector containing the coding region of a human RARy cDNA inserted downstream of the CMV promoter. <part-num-ref name="CMV promoter.">3)</part-num-ref>
|
| 648 |
+
Over- expressing RXR<confidence value="5">a</confidence>
|
| 649 |
+
construct (Gift of V.K.K. Chatterjee, Addenbrooke's Hospital, <boundary-data type="line-number">5 </boundary-data>
|
| 650 |
+
Cambridge). Modified pRSVcat containing the coding region of a human RXR<confidence value="5">a</confidence>
|
| 651 |
+
cDNA downstream of the RSV promoter. <part-num-ref name="RSV promoter.">4)</part-num-ref>
|
| 652 |
+
Over-expressing LXRa construct commercially available from <confidence value="5">I</confidence>
|
| 653 |
+
nvitrogen (GeneStorm hOR<confidence value="5">F</confidence>
|
| 654 |
+
Expression Vector Accession no. U22662) Modified pcDNA3.1/GS containing the coding region of human LXRa. <part-num-ref name="coding region of human LXRa.">5)</part-num-ref>
|
| 655 |
+
Control luciferase construct (pRL-TK Renilla luciferase reporter <boundary-data type="line-number">10 </boundary-data>
|
| 656 |
+
vector commercially available from Promega. For the transfection, DNA was made up as a mix of RARE reporter gene: RAR<confidence value="5">y</confidence>
|
| 657 |
+
: RXR<confidence value="5">a</confidence>
|
| 658 |
+
: LXRa: pRLTK in the ratio 4.15:4.95:3.33:8.97:1. </p>
|
| 659 |
+
<p id="p-109" num="109">Cos-7 cells were grown in <confidence value="5">D</confidence>
|
| 660 |
+
MEM with 10% FCS (foetal calf serum) at 37<confidence value="4">0</confidence>
|
| 661 |
+
C, 5% <boundary-data type="line-number">
|
| 662 |
+
<confidence value="66">15</confidence>
|
| 663 |
+
</boundary-data>
|
| 664 |
+
<confidence value="85">CO</confidence>
|
| 665 |
+
2 to 80% confluency. Cells were then plated out in 24 well plates at 50,000 cells per well and incubated overnight in DMEM with 10% FCS at 37<confidence value="4">0</confidence>
|
| 666 |
+
C, 5% C<confidence value="588">O2.</confidence>
|
| 667 |
+
</p>
|
| 668 |
+
<p id="p-110" num="110">Cells were then transfected using the LipofectAM<confidence value="5">I</confidence>
|
| 669 |
+
NE reagent (GibcoBRL). For each well 0.<confidence value="55">5p</confidence>
|
| 670 |
+
g of DNA mix (in 25p<confidence value="4">l</confidence>
|
| 671 |
+
of DMEM) was incubated with 1.1 <confidence value="85">pl</confidence>
|
| 672 |
+
LipofectAM<confidence value="5">I</confidence>
|
| 673 |
+
NE (in 25p<confidence value="5">l</confidence>
|
| 674 |
+
of DMEM) for <part-num-ref name="LipofectAMINE reagent (GibcoBRL). For each well 0.5pg of DNA mix (in 25pl of DMEM) was incubated with 1.1 pl LipofectAMINE (in 25pl of DMEM) for">45</part-num-ref>
|
| 675 |
+
minutes. The mixture was then made up <boundary-data type="line-number">20 </boundary-data>
|
| 676 |
+
to 250p<confidence value="4">l</confidence>
|
| 677 |
+
per well and added to the cells, which had been washed with <confidence value="685">1ml</confidence>
|
| 678 |
+
of DMEM. Cells were then incubated for <part-num-ref name="cells, which had been washed with 1ml of DMEM. Cells were then incubated for">5</part-num-ref>
|
| 679 |
+
hours at 37<confidence value="4">0</confidence>
|
| 680 |
+
C, 5% C<confidence value="5">O</confidence>
|
| 681 |
+
2 and 250pl DMEM with 20% SBCS (charcoal stripped bovine calf serum) added. Cells were incubated for <part-num-ref name="hours at 370C, 5% CO2 and 250pl DMEM with 20% SBCS (charcoal stripped bovine calf serum) added. Cells were incubated for">18</part-num-ref>
|
| 682 |
+
hours at 37<confidence value="2">*</confidence>
|
| 683 |
+
C, 5% C<confidence value="5">O</confidence>
|
| 684 |
+
2 before being treated with the appropriate compound<confidence value="5">/</confidence>
|
| 685 |
+
extract. Test compounds were made up as <confidence value="6666">1000</confidence>
|
| 686 |
+
x stocks (in DM<confidence value="66">SO</confidence>
|
| 687 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 688 |
+
or ethanol as appropriate) and diluted into DMEM with 10% SBCS <part-num-ref name="appropriate compound/ extract. Test compounds were made up as 1000x stocks (in DMSO or ethanol as appropriate) and diluted into DMEM with 10% SBCS">(50001</part-num-ref>
|
| 689 |
+
per well) immediately before being added to cells. Each treatment was performed in triplicate. The transfection mix was removed from the cells and replaced with the treatment mix, and incubated for <part-num-ref name="treatment mix, and incubated for">24</part-num-ref>
|
| 690 |
+
hours at 37<confidence value="4">0</confidence>
|
| 691 |
+
C, 5% C<confidence value="5">O</confidence>
|
| 692 |
+
2. Cells were washed with <confidence value="586">1ml</confidence>
|
| 693 |
+
of PBS (without calcium or magnesium) and then lysed with <confidence value="6665">100p</confidence>
|
| 694 |
+
per <boundary-data type="line-number">30 </boundary-data>
|
| 695 |
+
well of <confidence value="5">1</confidence>
|
| 696 |
+
x Lysis Buffer (as supplied with Promega Renilla Luciferase assay kit). </p>
|
| 697 |
+
<p id="p-111" num="111">Lysis was allowed to continue for 15 minutes and then the lysate was assayed for Renilla luciferase activity using the Promega Renilla Luciferase assay kit. For the assay 20<confidence value="54">p1</confidence>
|
| 698 |
+
of lysate was taken and assayed as described in the kit instructions <page-break num="18"/>
|
| 699 |
+
<boundary-data type="header">WO 2004/103320 PCT<confidence value="5">/</confidence>
|
| 700 |
+
EP2004/004942 </boundary-data>
|
| 701 |
+
<boundary-data type="header">
|
| 702 |
+
<confidence value="88">18</confidence>
|
| 703 |
+
</boundary-data>
|
| 704 |
+
using a MLX microtiter plate luminometer (Dynex). 75p<confidence value="4">l</confidence>
|
| 705 |
+
of lysate was assayed for chlorampenicol acetyltransferase activity using the Roche CAT ELISA kit as per the manufacturer's instructions. </p>
|
| 706 |
+
<p id="p-112" num="112">
|
| 707 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 708 |
+
CAT activity (RAR driven) was normalised against the Renilla luciferase value for that well and the mean calculated for the three wells treated with the same agent. </p>
|
| 709 |
+
<p id="p-113" num="113">Activity was then expressed as fold activation over the vehicle (ethanol) control values for that particular plate.</p>
|
| 710 |
+
<p id="p-114" num="114">
|
| 711 |
+
<boundary-data type="line-number">
|
| 712 |
+
<confidence value="86">10</confidence>
|
| 713 |
+
</boundary-data>
|
| 714 |
+
Table <confidence value="5">1</confidence>
|
| 715 |
+
Treatment Fold activity +<confidence value="5">/</confidence>
|
| 716 |
+
- sd (n<confidence value="588">=3)</confidence>
|
| 717 |
+
Ethanol 1.000 +/- 0.164 <confidence value="8855">0.1p</confidence>
|
| 718 |
+
M all-trans retinoic acid 1.733 +<confidence value="5">/</confidence>
|
| 719 |
+
- 0.445 <confidence value="885">35p</confidence>
|
| 720 |
+
M 22R hydroxycholesterol 1.209 +<confidence value="5">/</confidence>
|
| 721 |
+
- 0.030 <confidence value="8855">0.1p</confidence>
|
| 722 |
+
M all-trans retinoic acid and 2.962 +<confidence value="5">/</confidence>
|
| 723 |
+
- 0.582 <confidence value="885">35p</confidence>
|
| 724 |
+
M 22R hydroxycholesterol Fibroblast expression of CRABP<confidence value="668">II.</confidence>
|
| 725 |
+
</p>
|
| 726 |
+
<p id="p-115" num="115">Primary dermal fibroblasts were cultured in DMEM with 10% <confidence value="5">F</confidence>
|
| 727 |
+
CS (foetal calf <boundary-data type="line-number">
|
| 728 |
+
<confidence value="66">15</confidence>
|
| 729 |
+
</boundary-data>
|
| 730 |
+
serum) at 37<confidence value="4">0</confidence>
|
| 731 |
+
C, 5% C<confidence value="5">0</confidence>
|
| 732 |
+
2, 20% 02 to 80% confluency. Cells were then plated out in <part-num-ref name="to 80% confluency. Cells were then plated out in">12</part-num-ref>
|
| 733 |
+
well plates at 38,000 cells per well, and incubated for <part-num-ref name="well plates at 38,000 cells per well, and incubated for">24</part-num-ref>
|
| 734 |
+
hours. Medium was replaced and cells incubated for a further <part-num-ref name="further">24</part-num-ref>
|
| 735 |
+
hours at 37<confidence value="4">0</confidence>
|
| 736 |
+
C, 5% C<confidence value="2">O</confidence>
|
| 737 |
+
2, 4% <part-num-ref name="hours at 370C, 5% CO2, 4%">02.</part-num-ref>
|
| 738 |
+
</p>
|
| 739 |
+
<p id="p-116" num="116">Cells were treated with vehicle (ethanol) or 22R hydroxycholesterol and/or retinoic acid in <confidence value="586">1ml</confidence>
|
| 740 |
+
fresh medium (<confidence value="5">D</confidence>
|
| 741 |
+
MEM plus 10% FCS). Treatments were <boundary-data type="line-number">20 </boundary-data>
|
| 742 |
+
prepared as fresh <confidence value="6666">1000</confidence>
|
| 743 |
+
x stocks and diluted into medium immediately before addition to the cells. Treatment was for <part-num-ref name="cells. Treatment was for">24</part-num-ref>
|
| 744 |
+
hours at 37<confidence value="4">0</confidence>
|
| 745 |
+
C, 5% C<confidence value="2">O</confidence>
|
| 746 |
+
2, 20% <part-num-ref name="hours at 370C, 5% CO2, 20%">02.</part-num-ref>
|
| 747 |
+
Cells were washed in <confidence value="5">1</confidence>
|
| 748 |
+
ml phosphate buffer saline and trypsinised from the plates. </p>
|
| 749 |
+
<p id="p-117" num="117">Cells were pelleted at <confidence value="5">1</confidence>
|
| 750 |
+
3000g for 5 m<confidence value="66">in</confidence>
|
| 751 |
+
and washed with <confidence value="5">1</confidence>
|
| 752 |
+
ml PBS. Cells were re- pelleted and re-suspended in protein lysis buffer (4M urea, 0.5% <confidence value="566">SDS</confidence>
|
| 753 |
+
, 10mM <boundary-data type="line-number">25 </boundary-data>
|
| 754 |
+
EDTA in PBS with protease inhibitor cocktail). Samples were equilibrated for total protein content and the proteins separated by S<confidence value="5">D</confidence>
|
| 755 |
+
S-PAGE and blotted to nitrocellulose. Membranes were probed with antisera against the CRABP<confidence value="55">II</confidence>
|
| 756 |
+
<page-break num="19"/>
|
| 757 |
+
<boundary-data type="header">WO 2004/103320 PCT<confidence value="5">/</confidence>
|
| 758 |
+
EP2004<confidence value="5">/</confidence>
|
| 759 |
+
004942 </boundary-data>
|
| 760 |
+
<boundary-data type="header">
|
| 761 |
+
<confidence value="88">19</confidence>
|
| 762 |
+
</boundary-data>
|
| 763 |
+
protein and detected by ECL-plus. Intensity of signal was captured using a STORM scanner and quantified using ImageQuant 5.2. </p>
|
| 764 |
+
<p id="p-118" num="118">Table 2 <boundary-data type="line-number">
|
| 765 |
+
<confidence value="8">5</confidence>
|
| 766 |
+
</boundary-data>
|
| 767 |
+
Treatment Band Intensity Relative band % change (arbitrary units) intensity from vehicle Vehicle 168984.95 1.000 <part-num-ref name="Treatment Band Intensity Relative band % change (arbitrary units) intensity from vehicle Vehicle 168984.95 1.000">0</part-num-ref>
|
| 768 |
+
<confidence value="4">i</confidence>
|
| 769 |
+
nM all-trans retinoic acid 228603.88 1.353 +35.3% <confidence value="86">5p</confidence>
|
| 770 |
+
M 22R-hydroxycholesterol 167664.2 0.992 -0.8% <confidence value="25">in</confidence>
|
| 771 |
+
M all-trans retinoic acid 272710.54 1.614 +61.4% and 5pM 22R- hydroxycholesterol The various features and embodiments of the present invention, referred to in individual sections above apply, as appropriate, to other sections, mutatis mutandis. Consequently features specified in one section may be combined with <boundary-data type="line-number">
|
| 772 |
+
<confidence value="86">10</confidence>
|
| 773 |
+
</boundary-data>
|
| 774 |
+
features specified in other sections, as appropriate. </p>
|
| 775 |
+
<p id="p-119" num="119">All publications mentioned in the above specification are herein incorporated by reference. Various modifications and variations of the described methods and products of the invention will be apparent to those skilled in the art without <boundary-data type="line-number">15 </boundary-data>
|
| 776 |
+
departing from the scope of the invention. Although the invention has been described in connection with specific preferred embodiments, it should be understood that the invention as claimed should not be unduly limited to such specific embodiments. Indeed, various modifications of the described modes for carrying out the invention which are apparent to those skilled in the relevant fields <part-num-ref name="relevant fields">20</part-num-ref>
|
| 777 |
+
are intended to be within the scope of the following claims. </p>
|
| 778 |
+
</description>
|
| 779 |
+
</us-patent-application>
|
| 780 |
+
|
prior_art/10576240.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="10576240.07-17-2013.HJ8X3TKEPXXIFW3.SPEC.XML" pat:id="HJ8X3TKEPXXIFW3"><pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001"><pat:ApplicationHeaderDetails><pat:ApplicationNumber>10576240</pat:ApplicationNumber></pat:ApplicationHeaderDetails><pat:PageTotalQuantity>1</pat:PageTotalQuantity><pat:ParagraphTotalQuantity>4</pat:ParagraphTotalQuantity></pat:DocumentHeaderDetails><pat:MailRoomDate>2013-07-17</pat:MailRoomDate><pat:DocumentCreateDateText>2013-07-17</pat:DocumentCreateDateText><pat:DocumentTitle>SPECIFICATION DOCUMENT</pat:DocumentTitle><pat:Specification><?PageStart number='1'?><pat:P pat:pNumber="1" pat:id="p-1"><pat:BoundaryData><pat:HeaderText>Applicants: <pat:OCRConfidenceData pat:levelNumber='66'>I.</pat:OCRConfidenceData> Meiri-Bendek et al.</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Application No.: 10/576,240</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Examiner: J. A. Watts</pat:HeaderText></pat:BoundaryData>Amendment to the Specification Please amend the ABSTRACT of the published application as follows: </pat:P><pat:P pat:pNumber="2" pat:id="p-2">The invention provides an enzymatically-prepared fat base composition <pat:OCRConfidenceData pat:levelNumber='1211421'>mc1udin</pat:OCRConfidenceData>g which comprises a mixture of vegetable-derived triglycerides. The fat base composition has a <pat:PartName pat:idref='PN-00001'>total palmitic acid residues content of at most</pat:PartName> <pat:PartNumber pat:id='PN-00001'>38</pat:PartNumber><pat:OCRConfidenceData pat:levelNumber='5'>%</pat:OCRConfidenceData> of the total fatty acid residues, and <pat:PartName pat:idref='PN-00002'>at least</pat:PartName> <pat:PartNumber pat:id='PN-00002'>60</pat:PartNumber><pat:OCRConfidenceData pat:levelNumber='68'>%,</pat:OCRConfidenceData> <pat:PartName pat:idref='PN-00003'>preferably</pat:PartName> <pat:PartNumber pat:id='PN-00003'>62</pat:PartNumber><pat:OCRConfidenceData pat:levelNumber='5'>%</pat:OCRConfidenceData> of the fatty acid moieties at the <pat:PartName pat:idref='PN-00004'>sn</pat:PartName>-<pat:PartNumber pat:id='PN-00004'>2</pat:PartNumber> position of the glycerol backbone are palmitic acid residues, <pat:PartName pat:idref='PN-00005'>at least</pat:PartName> <pat:PartNumber pat:id='PN-00005'>70</pat:PartNumber><pat:OCRConfidenceData pat:levelNumber='5'>%</pat:OCRConfidenceData> of the fatty acid moieties at the <pat:PartName pat:idref='PN-00006'>sn</pat:PartName>-<pat:PartNumber pat:id='PN-00006'><pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData></pat:PartNumber> and <pat:PartName pat:idref='PN-00007'>sn</pat:PartName>-<pat:PartNumber pat:id='PN-00007'>3</pat:PartNumber> positions of the glycerol backbone are unsaturated, <pat:PartName pat:idref='PN-00008'>at least</pat:PartName> <pat:PartNumber pat:id='PN-00008'>40</pat:PartNumber><pat:OCRConfidenceData pat:levelNumber='5'>%</pat:OCRConfidenceData>, <pat:PartName pat:idref='PN-00009'>preferably</pat:PartName> <pat:PartNumber pat:id='PN-00009'>40</pat:PartNumber><pat:OCRConfidenceData pat:levelNumber='5885'>-60%</pat:OCRConfidenceData>, of the unsaturated fatty acid moieties at the <pat:PartName pat:idref='PN-00010'><pat:OCRConfidenceData pat:levelNumber='58'>sn</pat:OCRConfidenceData></pat:PartName><pat:OCRConfidenceData pat:levelNumber='8'>-</pat:OCRConfidenceData><pat:PartNumber pat:id='PN-00010'><pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData></pat:PartNumber> and <pat:PartName pat:idref='PN-00011'>sn</pat:PartName>-<pat:PartNumber pat:id='PN-00011'>3</pat:PartNumber> positions are oleic acid moieties, and <pat:PartName pat:idref='PN-00012'>at least</pat:PartName> <pat:PartNumber pat:id='PN-00012'>6</pat:PartNumber><pat:OCRConfidenceData pat:levelNumber='5'>%</pat:OCRConfidenceData>, <pat:PartName pat:idref='PN-00013'>preferably</pat:PartName> <pat:PartNumber pat:id='PN-00013'>6</pat:PartNumber><pat:OCRConfidenceData pat:levelNumber='58868'>-17%,</pat:OCRConfidenceData> of the unsaturated fatty acid moieties at the <pat:PartName pat:idref='PN-00014'>sn</pat:PartName>-<pat:PartNumber pat:id='PN-00014'><pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData></pat:PartNumber> and <pat:PartName pat:idref='PN-00015'>sn</pat:PartName>-<pat:PartNumber pat:id='PN-00015'>3</pat:PartNumber> positions are linoleic acid moieties. </pat:P><pat:P pat:pNumber="3" pat:id="p-3">The invention also provides preparation and various uses of the fat base composition in the field of infant nutrition. </pat:P><pat:P pat:pNumber="4" pat:id="p-4"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>2</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData></pat:P></pat:Specification></pat:SpecificationDocument>
|
prior_art/10578122.xml
ADDED
|
@@ -0,0 +1,22 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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="10578122.05-10-2013.HGP1MTPZPXXIFW2.SPEC.xml" pat:id="HGP1MTPZPXXIFW2" 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>10578122</pat:ApplicationNumber></pat:ApplicationHeaderDetails>
|
| 5 |
+
<pat:PageTotalQuantity>1</pat:PageTotalQuantity>
|
| 6 |
+
<pat:ParagraphTotalQuantity>4</pat:ParagraphTotalQuantity>
|
| 7 |
+
</pat:DocumentHeaderDetails>
|
| 8 |
+
<pat:MailRoomDate>2013-05-10</pat:MailRoomDate>
|
| 9 |
+
<pat:Specification pat:id="Specification">
|
| 10 |
+
<?PageStart number="1"?>
|
| 11 |
+
<pat:Heading pat:id="h-1"><pat:OCRConfidenceData pat:levelNumber="88">AM</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="72727">ENNME</pat:OCRConfidenceData> NTS T<pat:OCRConfidenceData pat:levelNumber="4">O</pat:OCRConfidenceData> THE SPEC<pat:OCRConfidenceData pat:levelNumber="67">IC</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="88">AT</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="288">[ON</pat:OCRConfidenceData></pat:Heading>
|
| 12 |
+
<pat:P pat:id="p-1" pat:pNumber="1"><pat:OCRConfidenceData pat:levelNumber="2">*</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="6">O</pat:OCRConfidenceData>n page 2<pat:OCRConfidenceData pat:levelNumber="5">,</pat:OCRConfidenceData> please replace the <pat:PartName pat:idref="PN-00001">paragraph starting on line </pat:PartName><pat:PartNumber pat:id="PN-00001">16</pat:PartNumber> with the following replacement paragraph:</pat:P>
|
| 13 |
+
<pat:P pat:id="p-2" pat:pNumber="2"><pat:OCRConfidenceData pat:levelNumber="6">-</pat:OCRConfidenceData> (amended) Moreover, the composition <pat:OCRConfidenceData pat:levelNumber="5">a</pat:OCRConfidenceData>nd heating values of most imported LNG varies dramatically and will generally depend on the particular source<pat:OCRConfidenceData pat:levelNumber="5">.</pat:OCRConfidenceData> While L<pat:OCRConfidenceData pat:levelNumber="66">NG</pat:OCRConfidenceData> with heavier contents or higher heating value can be produced at l<pat:OCRConfidenceData pat:levelNumber="66">ow</pat:OCRConfidenceData>er costs at the source, they are often not suitable for the North A<pat:OCRConfidenceData pat:levelNumber="5">m</pat:OCRConfidenceData>erican m<pat:OCRConfidenceData pat:levelNumber="5">a</pat:OCRConfidenceData>rket<pat:OCRConfidenceData pat:levelNumber="5">.</pat:OCRConfidenceData> For example<pat:OCRConfidenceData pat:levelNumber="5">,</pat:OCRConfidenceData> na<pat:OCRConfidenceData pat:levelNumber="66866">tural</pat:OCRConfidenceData> gas for the Californian market must meet a <pat:PartName pat:idref="PN-00002">heating value specification of </pat:PartName><pat:PartNumber pat:id="PN-00002">950</pat:PartNumber> <pat:PartName pat:idref="PN-00003"><pat:OCRConfidenceData pat:levelNumber="588588588">Btu/SCF-1</pat:OCRConfidenceData> </pat:PartName><pat:PartNumber pat:id="PN-00003">150</pat:PartNumber> Btu/SC<pat:OCRConfidenceData pat:levelNumber="5">F</pat:OCRConfidenceData>, and must meet composition <pat:OCRConfidenceData pat:levelNumber="5885">limi</pat:OCRConfidenceData>tat<pat:OCRConfidenceData pat:levelNumber="5">i</pat:OCRConfidenceData>ons <pat:OCRConfidenceData pat:levelNumber="66">on</pat:OCRConfidenceData> its C2 and C<pat:OCRConfidenceData pat:levelNumber="12">3+</pat:OCRConfidenceData> co<pat:OCRConfidenceData pat:levelNumber="5">m</pat:OCRConfidenceData>ponents<pat:OCRConfidenceData pat:levelNumber="4">.</pat:OCRConfidenceData> Especially where LNG is used as transportation fuel, the C2<pat:OCRConfidenceData pat:levelNumber="2">+</pat:OCRConfidenceData> content must be further reduced to avoid high combustion temperature and reduce greenhouse emissions<pat:OCRConfidenceData pat:levelNumber="5">.</pat:OCRConfidenceData> Table <pat:OCRConfidenceData pat:levelNumber="5">1</pat:OCRConfidenceData> below depicts composi<pat:OCRConfidenceData pat:levelNumber="66">ti</pat:OCRConfidenceData>on requirements in comparison to a typical imported <pat:OCRConfidenceData pat:levelNumber="5">L</pat:OCRConfidenceData>NG supply. <pat:OCRConfidenceData pat:levelNumber="86885">Thus,</pat:OCRConfidenceData> it would also be desirable to configure an LNG receiving terminal with the cap<pat:OCRConfidenceData pat:levelNumber="5">a</pat:OCRConfidenceData>bility to accommodate to varying LNG <pat:OCRConfidenceData pat:levelNumber="5">c</pat:OCRConfidenceData>ompositions<pat:OCRConfidenceData pat:levelNumber="4">.</pat:OCRConfidenceData></pat:P>
|
| 14 |
+
<pat:P pat:id="p-3" pat:pNumber="3"><pat:PatentImage com:orientationCategory="Portrait" pat:imageWrappingStyleCategory="In front of text">
|
| 15 |
+
<com:ImageFormatCategory>SVG</com:ImageFormatCategory>
|
| 16 |
+
<com:ImageFileName>10578122.05-10-2013.HGP1MTPZPXXIFW2.SPEC.1.svg</com:ImageFileName>
|
| 17 |
+
<com:HeightMeasure com:measureUnitCode="In">2.64</com:HeightMeasure>
|
| 18 |
+
<com:WidthMeasure com:measureUnitCode="In">5.18</com:WidthMeasure>
|
| 19 |
+
<com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P>
|
| 20 |
+
<pat:P pat:id="p-4" pat:pNumber="4"> <pat:OCRConfidenceData pat:levelNumber="5">T</pat:OCRConfidenceData>able <pat:OCRConfidenceData pat:levelNumber="4">1</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="84">--</pat:OCRConfidenceData></pat:P>
|
| 21 |
+
<pat:Heading pat:id="h-2"><pat:OCRConfidenceData pat:levelNumber="8">2</pat:OCRConfidenceData></pat:Heading>
|
| 22 |
+
</pat:Specification></pat:SpecificationDocument>
|
prior_art/10580070.xml
ADDED
|
@@ -0,0 +1,28 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>10580070</doc-number>
|
| 8 |
+
<date>2010-01-29</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.: 10/580,070 Amendments to the Specification:</p>
|
| 14 |
+
<p id="p-2" num="2">Please amend the paragraph beginning at page <part-num-ref name="paragraph beginning at page">36,</part-num-ref>
|
| 15 |
+
line <part-num-ref name="paragraph beginning at page 36, line">4</part-num-ref>
|
| 16 |
+
of the Clean Copy of the Substitute Specification as follows: </p>
|
| 17 |
+
<p id="p-3" num="3">Anti-Patent Literature No.<confidence value="5">5</confidence>
|
| 18 |
+
: Manual of the Additives for Food (Chemically Synthetic Substances), Food and Science Co., Ltd., <confidence value="666551556">April-996</confidence>
|
| 19 |
+
December <part-num-ref name="Additives for Food (Chemically Synthetic Substances), Food and Science Co., Ltd., April-996 December">10<confidence value="5">,</confidence>
|
| 20 |
+
</part-num-ref>
|
| 21 |
+
<part-num-ref name="Additives for Food (Chemically Synthetic Substances), Food and Science Co., Ltd., April-996 December 10,">1995.</part-num-ref>
|
| 22 |
+
</p>
|
| 23 |
+
<p id="p-4" num="4">
|
| 24 |
+
<confidence value="8">2</confidence>
|
| 25 |
+
</p>
|
| 26 |
+
</description>
|
| 27 |
+
</us-patent-application>
|
| 28 |
+
|
prior_art/10581014.xml
ADDED
|
@@ -0,0 +1,41 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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="10581014.05-06-2014.HUWSI229PXXIFW1.SPEC.xml" pat:id="HUWSI229PXXIFW1" 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>10581014</pat:ApplicationNumber></pat:ApplicationHeaderDetails>
|
| 5 |
+
<pat:PageTotalQuantity>2</pat:PageTotalQuantity>
|
| 6 |
+
<pat:ParagraphTotalQuantity>10</pat:ParagraphTotalQuantity>
|
| 7 |
+
</pat:DocumentHeaderDetails>
|
| 8 |
+
<pat:MailRoomDate>2014-05-06</pat:MailRoomDate>
|
| 9 |
+
<pat:Specification pat:id="Specification">
|
| 10 |
+
<?PageStart number="1"?>
|
| 11 |
+
<pat:BoundaryData><pat:HeaderText>Application No. 10/581,014</pat:HeaderText></pat:BoundaryData>
|
| 12 |
+
<pat:BoundaryData><pat:HeaderText>Amendment dated May XX, 2014</pat:HeaderText></pat:BoundaryData>
|
| 13 |
+
<pat:BoundaryData><pat:HeaderText>Reply to Office Communication of April 4, 2014</pat:HeaderText></pat:BoundaryData>
|
| 14 |
+
<pat:Heading pat:id="h-1">AMENDMENTS TO THE SPECIFICATION:</pat:Heading>
|
| 15 |
+
<pat:P pat:id="p-1" pat:pNumber="1">On page 190 of the <pat:PartName pat:idref="PN-00001">specification, lines </pat:PartName><pat:PartNumber pat:id="PN-00001">1</pat:PartNumber> <pat:PartName pat:idref="PN-00002">through </pat:PartName><pat:PartNumber pat:id="PN-00002">10</pat:PartNumber>, please amend the following paragraph as follows:</pat:P>
|
| 16 |
+
<pat:P pat:id="p-2" pat:pNumber="2">In this Example, experiments conducted to assess the expression of the perhydrolase in Streptomyces are described. To test expression of the perhydrolase in Streptomyces, a replicating plasmid was constructed with the phd gene being expressed from either the glucose isomerase <pat:OCRConfidenceData pat:levelNumber="885">(GI</pat:OCRConfidenceData>T) or the A4 promoter (<pat:OCRConfidenceData pat:levelNumber="411">See</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="15555">e.g.,</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="555514">US/PCT</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="6">/</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="6">,</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="66655">filed</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="52556652">November</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="616">18,</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="66666">2004,</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="552552">herein</pat:OCRConfidenceData></pat:P>
|
| 17 |
+
<pat:P pat:id="p-3" pat:pNumber="3"><pat:PatentImage com:orientationCategory="Portrait" pat:imageWrappingStyleCategory="In front of text">
|
| 18 |
+
<com:ImageFormatCategory>SVG</com:ImageFormatCategory>
|
| 19 |
+
<com:ImageFileName>10581014.05-06-2014.HUWSI229PXXIFW1.SPEC.1.svg</com:ImageFileName>
|
| 20 |
+
<com:HeightMeasure com:measureUnitCode="In">0.15</com:HeightMeasure>
|
| 21 |
+
<com:WidthMeasure com:measureUnitCode="In">6.15</com:WidthMeasure>
|
| 22 |
+
<com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P>
|
| 23 |
+
<pat:P pat:id="p-4" pat:pNumber="4"> these specific promoters, as any suitable promoter will find use with the present invention. Also, although the strain used for perhydrolase expression in this Example was Streptomyces lividans TK-23, it is contemplated that any Streptomyces will find use in the present invention.</pat:P>
|
| 24 |
+
<pat:P pat:id="p-5" pat:pNumber="5">On page 190 of the <pat:PartName pat:idref="PN-00003">specification, lines </pat:PartName><pat:PartNumber pat:id="PN-00003">16</pat:PartNumber> <pat:PartName pat:idref="PN-00004">through </pat:PartName><pat:PartNumber pat:id="PN-00004">26</pat:PartNumber>, please amend the following paragraph as follows:</pat:P>
|
| 25 |
+
<pat:P pat:id="p-6" pat:pNumber="6">Construction of pSECGT-MSAT and pSECA4-MSA<pat:OCRConfidenceData pat:levelNumber="8">T</pat:OCRConfidenceData> Using standard methods known in the art, the <pat:PartName pat:idref="PN-00005">phd coding sequence (See, Example </pat:PartName><pat:PartNumber pat:id="PN-00005">4)</pat:PartNumber> was cloned into pSECGT to place the gene under control of the GI promoter. Similarly, the gene was cloned in the same plasmid with the A4 promoter using methods known in the art (Se<pat:OCRConfidenceData pat:levelNumber="4">e</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="68666">e.g.,</pat:OCRConfidenceData> . Transformants were first selected in E. co<pat:OCRConfidenceData pat:levelNumber="5">l</pat:OCRConfidenceData>i, verified by sequence analysis, and then transformed into S. lividans TK-23 using methods known in the art (See e.g., Kieser et al., [2000], supra). The correct clones expressed from the GI promoter and the A4 promoter were designated "pSECGT-MSAT" and "pSECA4-phd." The sequence of pSECGT-MSAT is provided below, while Figure 18 provides a map of the plasmid.</pat:P>
|
| 26 |
+
<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8">2</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>
|
| 27 |
+
<pat:BoundaryData><pat:HeaderText>Atty Docket No. GC821-2-US</pat:HeaderText></pat:BoundaryData>
|
| 28 |
+
<pat:P pat:id="p-7" pat:pNumber="7">
|
| 29 |
+
<?PageStart number="2"?></pat:P>
|
| 30 |
+
<pat:BoundaryData><pat:HeaderText>Application No. 10/581,014</pat:HeaderText></pat:BoundaryData>
|
| 31 |
+
<pat:BoundaryData><pat:HeaderText>Amendment dated May XX, 2014</pat:HeaderText></pat:BoundaryData>
|
| 32 |
+
<pat:BoundaryData><pat:HeaderText>Reply to Office Communication of April 4, 2014</pat:HeaderText></pat:BoundaryData>
|
| 33 |
+
<pat:P pat:id="p-8" pat:pNumber="8">On page 211 of the specification, please replace the table with the following table:</pat:P>
|
| 34 |
+
<pat:P pat:id="p-9" pat:pNumber="9"><pat:PatentImage com:orientationCategory="Portrait" pat:imageWrappingStyleCategory="In front of text">
|
| 35 |
+
<com:ImageFormatCategory>SVG</com:ImageFormatCategory>
|
| 36 |
+
<com:ImageFileName>10581014.05-06-2014.HUWSI229PXXIFW1.SPEC.2.svg</com:ImageFileName>
|
| 37 |
+
<com:HeightMeasure com:measureUnitCode="In">7.33</com:HeightMeasure>
|
| 38 |
+
<com:WidthMeasure com:measureUnitCode="In">5.5</com:WidthMeasure>
|
| 39 |
+
<com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P>
|
| 40 |
+
<pat:P pat:id="p-10" pat:pNumber="10"> <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8">3</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Atty Docket No. GC821-2-US</pat:HeaderText></pat:BoundaryData></pat:P>
|
| 41 |
+
</pat:Specification></pat:SpecificationDocument>
|
prior_art/10582824.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
prior_art/10596060.xml
ADDED
|
@@ -0,0 +1,191 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>10596060</doc-number>
|
| 8 |
+
<date>2006-05-26</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">007034.00008 Page 1 of 10</boundary-data>
|
| 14 |
+
<heading id="h-1">ALUMINIUM ALLOY STRIP FOR WELDING</heading>
|
| 15 |
+
<heading id="h-2">FIELD OF THE INVENTION</heading>
|
| 16 |
+
<p id="p-1" num="1">
|
| 17 |
+
<confidence value="5885">[01]</confidence>
|
| 18 |
+
The invention relates to aluminium alloy strips, possibly cladded on one or two faces with a brazing alloy and intended for the production of brazed parts, particularly heat exchangers for automobiles or buildings, and more particularly parts assembled by fluxless brazing under a controlled atmosphere. </p>
|
| 19 |
+
<heading id="h-3">STATE OF THE ART</heading>
|
| 20 |
+
<p id="p-2" num="2">[02] The most frequently used process for the assembly of automobile heat exchangers is brazing. This is based on the use of a cladded strip composed of a so-called "core" alloy coated on one or two faces with a so-called "brazing" alloy, at least for one of the components to be assembled. This so-called "brazing" alloy is characterised by a liquid temperature about 30<confidence value="1">°</confidence>
|
| 21 |
+
C less than the solidus temperature of the core alloy. By applying an appropriate heat treatment, it is possible to melt only the cladding, which then wets the surfaces in contact allowing good assembly after the assembly has cooled. </p>
|
| 22 |
+
<p id="p-3" num="3">
|
| 23 |
+
<confidence value="5885">[03]</confidence>
|
| 24 |
+
There are three different brazing techniques presently available: </p>
|
| 25 |
+
<p id="p-4" num="4">[04] The most widespread is brazing under a controlled nitrogen atmosphere, after coating parts to be assembled with a non-corrosive "flux", the most frequently used being the <confidence value="22222222">Nocolok®</confidence>
|
| 26 |
+
flux. This product, designed to dissolve the surface oxide layer on aluminium and consequently to increase the wettability of the surfaces, is of the potassium fluoro- aluminate type. A number of problems arise when it is used. Obviously, the product has an intrinsic cost; its deposition requires special installations that frequently prevent complete automation of exchanger production lines; finally an effluent treatment must be arranged. </p>
|
| 27 |
+
<p id="p-5" num="5">[05] Another older technique but one still used particularly in North America is vacuum brazing. This process makes it necessary to use cladding that contains magnesium; this element is segregated on the surface and vaporises in the vacuum, capturing residual traces of oxygen. It thus avoids the oxide layer, initially broken by differential expansion, <page-break num="2"/>
|
| 28 |
+
<boundary-data type="header">007034.00008 Page <confidence value="8">2</confidence>
|
| 29 |
+
<confidence value="88">of</confidence>
|
| 30 |
+
<confidence value="66">10</confidence>
|
| 31 |
+
</boundary-data>
|
| 32 |
+
from reforming. No flux is necessary, but vacuum-creating installations are very complicated and associated maintenance costs are very high. For these economic reasons, existing lines are progressively being abandoned and replaced by Nocolok<confidence value="2">@</confidence>
|
| 33 |
+
lines. </p>
|
| 34 |
+
<p id="p-6" num="6">[06<confidence value="5">]</confidence>
|
| 35 |
+
Finally, a third process used more marginally, consists of depositing a nickel layer instead of the flux. Brazing is then done under nitrogen. The energy released during the brazing cycle by the creation of Al-Ni phases on the cladding surface is sufficient to break the oxide layer. </p>
|
| 36 |
+
<p id="p-7" num="7">[07] The main problem consists of performing the brazing operation on existing Nocolok<confidence value="4">®</confidence>
|
| 37 |
+
lines, since these are the most widespread and the most economic, without the use of flux or any other complex surface preparation and without causing degradation of the final properties of exchangers that will be assembled using this technique. </p>
|
| 38 |
+
<p id="p-8" num="8">
|
| 39 |
+
<confidence value="5885">[08]</confidence>
|
| 40 |
+
The solution that has been developed most widely in this field is an adaptation of the nickel deposition brazing process. Although increasingly simplified deposition techniques have been found and used, for example as described in patent application WO 02/07928 (Corus), they never provide more than a partial solution to the problem. </p>
|
| 41 |
+
<p id="p-9" num="9">The manufacturer of exchangers, or of aluminium strips if the operation is carried out by this manufacturer, must always add on specific installations for surface preparation before brazing and must continue to manage effluents, this time generated by nickel plating baths. Furthermore, although progress has been made in terms of resistance to corrosion as mentioned in patent application WO 02/060639 (Cor<confidence value="2">u</confidence>
|
| 42 |
+
s), the indicated performances do not always reach the performances claimed for Nocolok<confidence value="4">®</confidence>
|
| 43 |
+
brazed products (for example see patent application WO 02/40729 by Pechiney Rhenalu). </p>
|
| 44 |
+
<p id="p-10" num="10">[09] Other solutions are related to adaptation of the cladding alloy <confidence value="222222">and/or</confidence>
|
| 45 |
+
atmospheric conditions in brazing furnaces, as for example in US patent <part-num-ref name="cladding alloy and/or atmospheric conditions in brazing furnaces, as for example in US patent">3</part-num-ref>
|
| 46 |
+
<part-num-ref name="">811</part-num-ref>
|
| 47 |
+
<part-num-ref name="">177</part-num-ref>
|
| 48 |
+
(VAW) that mentions the addition of the Bi, Sr, Ba or Sb elements into brazing alloys to modify its surface tension. The effect of bismuth on the surface tension is also mentioned in patent EP <part-num-ref name="surface tension is also mentioned in patent EP">0004096</part-num-ref>
|
| 49 |
+
(Ford). More recently, the advantage of adding sodium, possibly accompanied by potassium or bismuth, is mentioned in application WO 01/98019 by Kaiser Aluminium. Finally in EP <part-num-ref name="advantage of adding sodium, possibly accompanied by potassium or bismuth, is mentioned in application WO 01/98019 by Kaiser Aluminium. Finally in EP">1306207</part-num-ref>
|
| 50 |
+
(Sky Aluminium), the brazing that contains <page-break num="3"/>
|
| 51 |
+
<boundary-data type="header">007034.00008 Page 3 of 10</boundary-data>
|
| 52 |
+
Mg and Bi is covered with a thin layer formed of an aluminium alloy that will remain solid when it begins to melt; it will only break later during the brazing cycle, releasing liquid cladding that then wets its upper surface. Oxidation of the liquid brazing alloy is avoided by working under an atmosphere for a short period. The oxide present on the thin layer is broken when it is surrounded by liquid. </p>
|
| 53 |
+
<heading id="h-4">PURPOSE AND OBJECTIVE OF THE INVENTION</heading>
|
| 54 |
+
<p id="p-11" num="11">
|
| 55 |
+
<confidence value="5">[</confidence>
|
| 56 |
+
10] The purpose of the invention is to enable production by fluxless brazing of parts made of aluminium alloy under good economic conditions, and particularly using the same equipment as is used for brazing with flux under a controlled atmosphere. </p>
|
| 57 |
+
<p id="p-12" num="12">
|
| 58 |
+
<confidence value="5885">[11]</confidence>
|
| 59 |
+
The purpose of the invention is an aluminium alloy strip or sheet containing 0.01 to 0.5% of yttrium and/or 0.05 to 0.5% of bismuth, coated on at least one face with a brazing alloy. The coating may be a layer cladded by co-rolling, for example an aluminium alloy containing <part-num-ref name="aluminium alloy containing">4</part-num-ref>
|
| 60 |
+
to 15% of silicon. It may also be a layer comprising particles of a brazing alloy, particularly particles of Al-Si alloy, possibly coated in a resin. </p>
|
| 61 |
+
<p id="p-13" num="13">[12<confidence value="5">]</confidence>
|
| 62 |
+
Another purpose of the invention is a brazed part, particularly a heat exchanger made using an aluminium alloy strip or sheet containing 0.01 to 0.5% of yttrium and/or 0.05 to 0.5% of bismuth. </p>
|
| 63 |
+
<heading id="h-5">DESCRIPTION OF THE FIGURES</heading>
|
| 64 |
+
<p id="p-14" num="14">[13] Figures la and <confidence value="5">l</confidence>
|
| 65 |
+
b show a top and side view respectively of V test pieces used in the examples to evaluate the brazability. </p>
|
| 66 |
+
<p id="p-15" num="15">[14<confidence value="5">]</confidence>
|
| 67 |
+
Figure 2 shows the definition of the width of the brazed joint used in the brazability test described in the examples. </p>
|
| 68 |
+
<heading id="h-6">DESCRIPTION OF THE INVENTION</heading>
|
| 69 |
+
<p id="p-16" num="16">[15<confidence value="5">]</confidence>
|
| 70 |
+
Unlike the techniques mentioned above, the invention is designed to modify the composition of the core alloy, such that brazing can take place without any deposition, under standard controlled atmosphere conditions, and that can be achieved without modifying the brazing installations used at equipment manufacturers. </p>
|
| 71 |
+
<boundary-data type="header">007034.00008 Page <confidence value="8">4</confidence>
|
| 72 |
+
<confidence value="88">of</confidence>
|
| 73 |
+
<confidence value="66">10</confidence>
|
| 74 |
+
</boundary-data>
|
| 75 |
+
<p id="p-17" num="17">
|
| 76 |
+
<page-break num="4"/>
|
| 77 |
+
<confidence value="5885">[16]</confidence>
|
| 78 |
+
Surprisingly, the addition of some elements in the core, such as yttrium at a content of 0.05% or bismuth at a content of about 0.15%, can result in a very satisfactory quality of brazed joints for fluxless brazing under nitrogen. </p>
|
| 79 |
+
<p id="p-18" num="18">
|
| 80 |
+
<confidence value="5885">[17]</confidence>
|
| 81 |
+
The method is applicable to all types of aluminium alloys containing at least 80% by weight of aluminium, and particularly alloys for which the composition satisfies the following conditions (% by weight) before the addition of elements specifically intended to enable fluxless brazing: </p>
|
| 82 |
+
<p id="p-19" num="19">
|
| 83 |
+
<confidence value="88">Si</confidence>
|
| 84 |
+
<confidence value="8"><</confidence>
|
| 85 |
+
1.0; Fe < 1.0; Cu <confidence value="8"><</confidence>
|
| 86 |
+
1.0; Mn <confidence value="8"><</confidence>
|
| 87 |
+
2.0; Mg <confidence value="8"><</confidence>
|
| 88 |
+
3.0; Zn <confidence value="8"><</confidence>
|
| 89 |
+
6.0; Ti <confidence value="8"><</confidence>
|
| 90 |
+
0.3; Zr <confidence value="8"><</confidence>
|
| 91 |
+
0.3; </p>
|
| 92 |
+
<p id="p-20" num="20">Cr <confidence value="5"><</confidence>
|
| 93 |
+
0.3; Hf < 0.6; V < 0.3; Ni < 2.0; Co < 2.0; In < 0.3; other elements < 0.05 each and 0.15 total; remainder aluminium. </p>
|
| 94 |
+
<p id="p-21" num="21">
|
| 95 |
+
<confidence value="5885">[18]</confidence>
|
| 96 |
+
The sheet or strip may be cladded by co-rolling on one or two faces with a brazing aluminium alloy, usually an alloy containing <part-num-ref name="alloy containing">4</part-num-ref>
|
| 97 |
+
to 15% of silicon. The brazing alloy may contain other additives such as copper, magnesium or zinc. It may also contain elements designed to modify the surface tension of the alloy, such as Ag, Be, Bi, Ce, La, Pb, Pd, Sb, Y or mischmetal, in other words a mixture of unseparated rare earth metals. In the case in which the brazing alloy is cladded on a single face, the other face may be coated by a sacrificial alloy, usually of the Al-Zn type, in a manner commonly known and intended to improve the resistance of the core alloy to corrosion. </p>
|
| 98 |
+
<p id="p-22" num="22">
|
| 99 |
+
<confidence value="5884">[19]</confidence>
|
| 100 |
+
The brazing alloy may also be deposited in the form of particles, particularly Al-Si particles, for example as described in patent EP <part-num-ref name="form of particles, particularly Al-Si particles, for example as described in patent EP">0565568</part-num-ref>
|
| 101 |
+
(Alcan International). For brazing under a controlled atmosphere, the brazing alloy particles are usually associated with flux particles, particularly flux based on fluorides such as potassium fluoro- aluminate, and a binder such as a polymer resin. One particular advantage of the invention in this case is to avoid the presence of flux in the coating. </p>
|
| 102 |
+
<p id="p-23" num="23">[20<confidence value="4">]</confidence>
|
| 103 |
+
The alloy sheet with the addition of bismuth <confidence value="222222">and/or</confidence>
|
| 104 |
+
yttrium may also be used uncoated when it is associated with another sheet coated with a brazing alloy for the production of the brazed part. </p>
|
| 105 |
+
<boundary-data type="header">007034.00008 Page 5 of 10</boundary-data>
|
| 106 |
+
<heading id="h-7">EXAMPLES</heading>
|
| 107 |
+
<p id="p-24" num="24">
|
| 108 |
+
<page-break num="5"/>
|
| 109 |
+
Example 1 [21] Four plates of core alloys with the following compositions were cast: </p>
|
| 110 |
+
<heading id="h-8">ALLOY SI <confidence value="88">FE</confidence>
|
| 111 |
+
CU MN MG T<confidence value="6">I</confidence>
|
| 112 |
+
<confidence value="8">Y</confidence>
|
| 113 |
+
<confidence value="8">B</confidence>
|
| 114 |
+
I CA </heading>
|
| 115 |
+
<p id="p-25" num="25">M 0.40 0.22 0.63 0.57 0.47 0.08 - - - <confidence value="8">M</confidence>
|
| 116 |
+
<confidence value="6">+</confidence>
|
| 117 |
+
Y 0.39 0.24 0.61 0.57 0.47 0.09 0.06 - - <confidence value="8">M</confidence>
|
| 118 |
+
<confidence value="6">+</confidence>
|
| 119 |
+
BI 0.39 0.22 0.62 0.59 0.49 0.09 - 0.15 - <confidence value="8">M</confidence>
|
| 120 |
+
<confidence value="5">+</confidence>
|
| 121 |
+
CA 0.40 0.22 0.63 0.57 0.47 0.08 - - 0.05 together with a <part-num-ref name="">4047</part-num-ref>
|
| 122 |
+
cladding alloy plate (Al - 12% Si). Assemblies were made from these plates such that the thickness of the cladding alloy represents 10% of the total thickness. These assemblies were hot rolled and then cold rolled so as to produce 0.3 mm thick cladded strips. These strips were then subjected to a restoration treatment for <part-num-ref name="restoration treatment for">10</part-num-ref>
|
| 123 |
+
h at 260<confidence value="188">°C.</confidence>
|
| 124 |
+
</p>
|
| 125 |
+
<p id="p-26" num="26">[22] The test piece illustrated in Figure 1 was used to evaluate the brazability of these materials. The "V" is composed of a 0.3 mm thick bare strip made of a <part-num-ref name="">3003</part-num-ref>
|
| 126 |
+
alloy in the H24 temper. A 15-minute degreasing treatment at 250<confidence value="1">°</confidence>
|
| 127 |
+
C was applied to the metal to be brazed. No other surface preparation was used and in particular no flux was deposited. </p>
|
| 128 |
+
<p id="p-27" num="27">Brazing is done in a double-wall glass furnace in which it is possible to view movements of liquid brazing alloy and the formation of joints during the treatment. The thermal cycle is composed of a temperature rise phase up to 610<confidence value="1">°</confidence>
|
| 129 |
+
C at a rate of approximately <confidence value="881">20°</confidence>
|
| 130 |
+
C/min, holding for <part-num-ref name="rate of approximately 20°C/min, holding for">2</part-num-ref>
|
| 131 |
+
minutes at 610<confidence value="1">°</confidence>
|
| 132 |
+
C, and then lowering at a rate of about <confidence value="881">30°</confidence>
|
| 133 |
+
C/minute. The complete process is done under continuous nitrogen scavenging, at a rate of <part-num-ref name="rate of">8</part-num-ref>
|
| 134 |
+
<confidence value="222228">1/min.</confidence>
|
| 135 |
+
</p>
|
| 136 |
+
<p id="p-28" num="28">[23] The results are marked A to <confidence value="5">E</confidence>
|
| 137 |
+
at the following scale: </p>
|
| 138 |
+
<p id="p-29" num="29">Mark A B C D E Joint length formed as a 100% 90% 75% 50% 0% percent of the total length <page-break num="6"/>
|
| 139 |
+
<boundary-data type="header">007034.00008 Page <confidence value="8">6</confidence>
|
| 140 |
+
<confidence value="88">of</confidence>
|
| 141 |
+
<confidence value="68">10</confidence>
|
| 142 |
+
</boundary-data>
|
| 143 |
+
<confidence value="5884">[24]</confidence>
|
| 144 |
+
The results are given in table 1: </p>
|
| 145 |
+
<p id="p-30" num="30">Table 1 Core Cladding Brazability M <part-num-ref name="Core Cladding Brazability M">4047</part-num-ref>
|
| 146 |
+
<confidence value="5">E</confidence>
|
| 147 |
+
<confidence value="8">M</confidence>
|
| 148 |
+
<confidence value="8">+</confidence>
|
| 149 |
+
Y <part-num-ref name="E M + Y">4047</part-num-ref>
|
| 150 |
+
A <confidence value="8">M</confidence>
|
| 151 |
+
<confidence value="8">+</confidence>
|
| 152 |
+
Bi <part-num-ref name="M + Bi">4047</part-num-ref>
|
| 153 |
+
A <confidence value="8">M</confidence>
|
| 154 |
+
<confidence value="8">+</confidence>
|
| 155 |
+
Ca <part-num-ref name="M + Ca">4047</part-num-ref>
|
| 156 |
+
E [25] The improvement in the brazability obtained due to the addition of Y or Bi to the core alloy can be seen. </p>
|
| 157 |
+
<p id="p-31" num="31">Example 2 [26<confidence value="5">]</confidence>
|
| 158 |
+
Two plates with the following compositions were cast in the same way: </p>
|
| 159 |
+
<p id="p-32" num="32">Alloy Si Fe Cu Mn Mg Ti Y N 0.17 0.18 0.64 1.37 - 0.08 - <confidence value="8">N</confidence>
|
| 160 |
+
<confidence value="8">+</confidence>
|
| 161 |
+
Y 0.19 0.17 0.67 1.32 - 0.09 0.06 together with a <part-num-ref name="">4045</part-num-ref>
|
| 162 |
+
cladding alloy plate (Al - 10% Si). The transformation procedure and the tests carried out are exactly the same as for example <part-num-ref name="same as for example">1.</part-num-ref>
|
| 163 |
+
</p>
|
| 164 |
+
<p id="p-33" num="33">[27] The results are given in table 2:</p>
|
| 165 |
+
<p id="p-34" num="34">Table 2 Core Cladding Brazability N <part-num-ref name="Core Cladding Brazability N">4045</part-num-ref>
|
| 166 |
+
<confidence value="5">E</confidence>
|
| 167 |
+
<confidence value="85">N+</confidence>
|
| 168 |
+
Y <part-num-ref name="E N+Y">4045</part-num-ref>
|
| 169 |
+
A [28] It can be seen that the addition of yttrium to alloy N significantly improves the brazability. </p>
|
| 170 |
+
<boundary-data type="header">007034.00008 Page 7 of 10</boundary-data>
|
| 171 |
+
<p id="p-35" num="35">
|
| 172 |
+
<page-break num="7"/>
|
| 173 |
+
Example 3 [29] Two plates with the following compositions were cast in the same way: </p>
|
| 174 |
+
<p id="p-36" num="36">Alloy Si Fe Cu Mn M<confidence value="5">g</confidence>
|
| 175 |
+
Ti Y P 0.15 0.35 0.1 0.1 0.8 0.125 - <confidence value="8">P</confidence>
|
| 176 |
+
<confidence value="6">+</confidence>
|
| 177 |
+
Y 0.15 0.35 0.1 0.1 0.8 0.125 0.06 together with a <part-num-ref name="">4045</part-num-ref>
|
| 178 |
+
cladding alloy plate (Al - 10% Si). The transformation procedure and the tests carried out are exactly the same as for example <part-num-ref name="same as for example">1.</part-num-ref>
|
| 179 |
+
</p>
|
| 180 |
+
<p id="p-37" num="37">[30<confidence value="4">]</confidence>
|
| 181 |
+
The results are given in table 3: </p>
|
| 182 |
+
<p id="p-38" num="38">Table 3 Core Cladding Brazability P <part-num-ref name="Core Cladding Brazability P">045</part-num-ref>
|
| 183 |
+
<confidence value="5">E</confidence>
|
| 184 |
+
<confidence value="8">P</confidence>
|
| 185 |
+
<confidence value="8">+</confidence>
|
| 186 |
+
Y <part-num-ref name="E P + Y">4045</part-num-ref>
|
| 187 |
+
A <confidence value="5">[</confidence>
|
| 188 |
+
31] It can be seen that the addition of yttrium to alloy P significantly improves the brazability. </p>
|
| 189 |
+
</description>
|
| 190 |
+
</us-patent-application>
|
| 191 |
+
|
prior_art/10596434.xml
ADDED
|
@@ -0,0 +1,516 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>10596434</doc-number>
|
| 8 |
+
<date>2006-06-13</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">WO 2005/063125 PCT/<confidence value="4">I</confidence>
|
| 14 |
+
B2004/004225 </boundary-data>
|
| 15 |
+
<boundary-data type="header">
|
| 16 |
+
<confidence value="8">1</confidence>
|
| 17 |
+
</boundary-data>
|
| 18 |
+
<heading id="h-1">SYSTEM FOR GUIDING A MEDICAL INSTRUMENT IN A PATIENT BODY</heading>
|
| 19 |
+
<heading id="h-2">FIELD OF THE INVENTION</heading>
|
| 20 |
+
<p id="p-1" num="1">The present invention relates to a medical system comprising a medical instrument to <boundary-data type="line-number">5 </boundary-data>
|
| 21 |
+
be guided in a patient body and means for visualizing said medical instrument. The invention also relates to a method to be used in said system. The invention finds for example its application for guiding a catheter inside the heart of a patient during an electrophysiology interventional procedure. </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 |
+
Clinical applications in which a medical instrument has to be guided into the body of a patient are becoming widespread. Notably the growing interest in minimal-invasive methods for the treatment of cardiac diseases necessitates the development of methods and devices allowing the physician to guide a medical instrument to predetermined positions <boundary-data type="line-number">15 </boundary-data>
|
| 26 |
+
inside or outside the heart. In electrophysiology for example, it is necessary to guide a catheter to a plurality of predetermined positions on the ventricular or atrial walls in order to measure an electrical pulse or to bu<confidence value="88">rn</confidence>
|
| 27 |
+
wall tissues. </p>
|
| 28 |
+
<p id="p-3" num="3">US patent 6,587,709 discloses a system for guiding a medical instrument in the body of a patient. Such a system acquires a live 3D ultrasound image data set using an ultrasound <boundary-data type="line-number">20 </boundary-data>
|
| 29 |
+
probe. An advantage of acquiring a 3D image data set is to get depth information. An advantage of using a live 3D ultrasound image modality is that the surrounding anatomy is visible, which facilitates the guidance of the medical instrument by the physician. The system further comprises localization means for localizing the medical instrument within the 3D ultrasound data set, which locates three ultrasound receivers mounted on the medical <boundary-data type="line-number">25 </boundary-data>
|
| 30 |
+
instrument relatively to said ultrasound probe. Such a localization allows an automatic selection of a plane to be imaged, which comprises at least a section of the medical instrument. Therefore no readjustment of the ultrasound probe position by hand is necessary. </p>
|
| 31 |
+
<p id="p-4" num="4">A first drawback of such a 3D ultrasound data set is that it has a narrow viewing field, which does not cover the whole part of the patient body concerned by a catheter introduction <boundary-data type="line-number">30 </boundary-data>
|
| 32 |
+
and placement. Therefore, for guiding the catheter during the whole procedure, the ultrasound probe has to be moved several times. At each displacement, a pre-operative step of locating the ultrasound probe in a referential of the interventional room is needed, because the location of the catheter is measured relatively to the ultrasound probe location. Such a pre-operative step may delay and complicate the interventional procedure. </p>
|
| 33 |
+
<boundary-data type="header">WO 2005/063125 PCT<confidence value="68">/I</confidence>
|
| 34 |
+
B2004/004225 </boundary-data>
|
| 35 |
+
<boundary-data type="header">
|
| 36 |
+
<confidence value="8">2</confidence>
|
| 37 |
+
</boundary-data>
|
| 38 |
+
<p id="p-5" num="5">
|
| 39 |
+
<page-break num="2"/>
|
| 40 |
+
A second drawback of the ultrasound imaging modality is that it has a low resolution Therefore, the acquired 3D ultrasound data set does not give an image of the catheter and its surrounding of acceptable quality. </p>
|
| 41 |
+
<p id="p-6" num="6">A third drawback of the ultrasound imaging modality is that there are some zones of <boundary-data type="line-number">5 </boundary-data>
|
| 42 |
+
the patient body where the thoracic cage blocks the ultrasound scan and no exploitable image can be output. </p>
|
| 43 |
+
<heading id="h-4">SUMMARY OF THE INVENTION</heading>
|
| 44 |
+
<p id="p-7" num="7">The object of the invention is therefore to provide a medical system for guiding a <boundary-data type="line-number">10 </boundary-data>
|
| 45 |
+
medical instrument in a patient body, which gives an improved visibility of the medical instrument and its surrounding anatomy during the whole procedure. </p>
|
| 46 |
+
<p id="p-8" num="8">This is achieved by a medical system comprising:</p>
|
| 47 |
+
<p id="p-9" num="9">- a medical instrument to be guided in a patient body, - X-Ray acquisition means for acquiring a two-dimensional X-ray image of said medical <boundary-data type="line-number">15 </boundary-data>
|
| 48 |
+
instrument, - ultrasound acquisition means for acquiring a three-dimensional ultrasound data set of said medical instrument using an ultrasound probe, - means for providing a localization of said ultrasound probe within a referential of said X- ray acquisition means, <boundary-data type="line-number">20 </boundary-data>
|
| 49 |
+
- means for selecting a region of interest around said medical instrument in the 3D ultrasound data set, that define a first localization of said region of interest within a referential of said ultrasound acquisition means, - means for converting said first localization of said region of interest within said referential of the ultrasound acquisition means into a second localization of said region of <boundary-data type="line-number">25 </boundary-data>
|
| 50 |
+
interest within said referential of the X-ray acquisition means, using said localization of the ultrasound probe, - means for generating and displaying a bi-modal representation of said medical instrument in which said two-dimensional X-ray image and the three-dimensional ultrasound data included in said region of interest are combined using said second localization. </p>
|
| 51 |
+
<p id="p-10" num="10">
|
| 52 |
+
<boundary-data type="line-number">
|
| 53 |
+
<confidence value="88">30</confidence>
|
| 54 |
+
</boundary-data>
|
| 55 |
+
With the invention, a bimodal representation is provided, in which two-dimensional (2D) X-Ray data and three-dimensional (3D) ultrasound data are combined. 2D X-ray data provide a good visibility and a high resolution of the medical instrument and of bone structures. 2D X-Ray data also benefit from a large viewing field, which allows a <page-break num="3"/>
|
| 56 |
+
<boundary-data type="header">WO 2005/063125 PCT<confidence value="66">/I</confidence>
|
| 57 |
+
B2004<confidence value="5">/</confidence>
|
| 58 |
+
004225 </boundary-data>
|
| 59 |
+
<boundary-data type="header">
|
| 60 |
+
<confidence value="8">3</confidence>
|
| 61 |
+
</boundary-data>
|
| 62 |
+
visualization of the whole area of the patient body concerned by the electrophysiology procedure. </p>
|
| 63 |
+
<p id="p-11" num="11">3D ultrasound data provide a good visibility of soft tissues and sometimes vascularities in a surrounding of the medical instrument. In addition, 3D ultrasound data give <boundary-data type="line-number">5 </boundary-data>
|
| 64 |
+
an indication of depth, which is not provided by the 2D X-Ray image, because said X-Ray image only provides a projection of said medical instrument in accordance with a geometry of the X-Ray acquisition means. Such a geometry defines lines of projection, along which absorptions of X-rays by the exposed tissues of the patient are accumulated. Therefore, the visibility of the surrounding of the medical instrument is improved by the combination of the <boundary-data type="line-number">10 </boundary-data>
|
| 65 |
+
2D X-Ray and the 3D ultrasound data. </p>
|
| 66 |
+
<p id="p-12" num="12">In order to provide such a combination, the system firstly localizes the ultrasound probe and the 3D ultrasound data set in a referential of the X-Ray acquisition means. Such a referential of the X-ray acquisition means is supposed to be fixed. Therefore, assuming that the ultrasound probe does not move, a position of any point of the 3D ultrasound data set in <boundary-data type="line-number">15 </boundary-data>
|
| 67 |
+
said referential the X-ray acquisition means can be deduced. As the position of the 2D X-Ray image on the X-Ray detector within the referential of the X-Ray acquisition means is given by the geometry of t<confidence value="5">h</confidence>
|
| 68 |
+
e X-Ray acquisition means, the localization of the 3D ultrasound data set within the referential of the X-Ray acquisition means allows a mapping of the 3D ultrasound data set with the 2D X-Ray image, i. e. a mapping of a projection of any point of <boundary-data type="line-number">20 </boundary-data>
|
| 69 |
+
the 3D ultrasound data set in accordance with the geometry of the X-Ray acquisition means with a point of the 2D X-Ray image. </p>
|
| 70 |
+
<p id="p-13" num="13">The system in accordance with the invention further selects a region of interest surrounding the medical instrument in the 3D ultrasound data set and provides a first localization of said region of interest within a referential of the ultrasound acquisition means.</p>
|
| 71 |
+
<p id="p-14" num="14">
|
| 72 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 73 |
+
Such a selection, which is made either manually or automatically, aims at suppressing any ultrasound data which could occlude the visualization of the medical instrument. </p>
|
| 74 |
+
<p id="p-15" num="15">The first localization, which is expressed with coordinates of a referential of the 3D ultrasound acquisition means, is then converted into a second localization of the medical instrument within the referential of the X-Ray acquisition means, using the localization of the <boundary-data type="line-number">30 </boundary-data>
|
| 75 |
+
ultrasound probe. </p>
|
| 76 |
+
<p id="p-16" num="16">The system in accordance with the invention finally generates a bimodal representation, in which the 3D ultrasound data included in said region of interest are combined to the 2D X-Ray data using said second localization of the region of interest within the referential of the X-Ray acquisition means.</p>
|
| 77 |
+
<boundary-data type="header">WO 2005/063125 PCT<confidence value="66">/I</confidence>
|
| 78 |
+
B2004<confidence value="4">1</confidence>
|
| 79 |
+
004225 </boundary-data>
|
| 80 |
+
<boundary-data type="header">
|
| 81 |
+
<confidence value="8">4</confidence>
|
| 82 |
+
</boundary-data>
|
| 83 |
+
<p id="p-17" num="17">
|
| 84 |
+
<page-break num="4"/>
|
| 85 |
+
Preferably, the bimodal representation is generated on the basis of the 2D-X-ray image. In this 2D X-ray image all the X-ray intensity values of points having corresponding points in the selected region of interest of the 3D ultrasound data set are combined by the ultrasound intensity values. </p>
|
| 86 |
+
<p id="p-18" num="18">
|
| 87 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 88 |
+
Said means for selecting a region of interest are intended to define a reference plane in which a part of said medical instrument is included. In a first embodiment of the invention the region of interest is included into said reference plane which, for instance, comprises the extremity of the medical instrument which is in contact with the wall tissue and is perpendicular to the orientation of the X-Ray acquisition means. Therefore, the means for <boundary-data type="line-number">10 </boundary-data>
|
| 89 |
+
generating a bimodal representation are intended to combine the 2D X-Ray image with the 2D ultrasound image which is obtained by sampling the 3D ultrasound data set over the reference plane coordinates in the referential of the X-Ray acquisition means. A first advantage of the first embodiment of the invention is that it is very simple. A second advantage is that any ultrasound data which could occlude the medical instrument and its <boundary-data type="line-number">15 </boundary-data>
|
| 90 |
+
surrounding have been removed. </p>
|
| 91 |
+
<p id="p-19" num="19">In an alternative, the selection means comprises detection means for detecting the medical instrument in the region of interest of the 3D ultrasound data set. Such a detection is for instance achieved automatically by using image processing techniques, for instance a filter for enhancing and thresholding elongated shapes. In the bimodal representation the X- <boundary-data type="line-number">20 </boundary-data>
|
| 92 |
+
ray intensity values of the points of the 2D X-ray image belonging to the detected medical instrument are advantageously kept unchanged. A first advantage is that the bimodal representation benefits from the high resolution of the medical instrument provided by the X- ray acquisition means. </p>
|
| 93 |
+
<p id="p-20" num="20">A second advantage of this detection is that it is based on image processing <boundary-data type="line-number">25 </boundary-data>
|
| 94 |
+
techniques and does not require any specific medical instrument, like a medical instrument equipped with active localizers. Considering that the medical instrument has to be changed for each new patient, another advantage of the system in accordance with the invention is to allow a non negligible cost savings. </p>
|
| 95 |
+
<p id="p-21" num="21">A third advantage of this detection is that it gives a localization of the extremity of the <boundary-data type="line-number">30 </boundary-data>
|
| 96 |
+
medical instrument. This localization, combined with the bimodal representation, may help generating of an electrical activation map of the heart cavity wall. As a matter of fact, in such a procedure, the medical instrument is a catheter equipped at its extremity with a sensor for measuring electrical pulses on a heart cavity wall. The user activates the sensor when the catheter is in contact with the heart cavity wall. A measurement of the electrical pulse at the <page-break num="5"/>
|
| 97 |
+
<boundary-data type="header">WO 2005/063125 PCT<confidence value="65">/I</confidence>
|
| 98 |
+
B2004<confidence value="5">/</confidence>
|
| 99 |
+
004225 </boundary-data>
|
| 100 |
+
<boundary-data type="header">
|
| 101 |
+
<confidence value="8">5</confidence>
|
| 102 |
+
</boundary-data>
|
| 103 |
+
current position of the catheter is made.The localization of the catheter provided by the system in accordance with the invention provides a location of the point corresponding to said current position and said electrical measurement in the electrical activation map. By visualizing the bimodal representation the user has the possibility to evaluate a distance <boundary-data type="line-number">5 </boundary-data>
|
| 104 |
+
between the current measurement point and previous measurement points. Therefore, the system in accordance with the invention facilitates a quick, uniform and complete mapping of the cavity wall. </p>
|
| 105 |
+
<p id="p-22" num="22">In a second embodiment of the invention, the system in accordance with the invention further comprises means for segmenting a wall tissue region in the 3D ultrasound data set.</p>
|
| 106 |
+
<p id="p-23" num="23">
|
| 107 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 108 |
+
Therefore, in the 2D X-ray image, only the X-ray intensity values of the points belonging to said wall tissue region are combined with the corresponding ultrasound intensity values. </p>
|
| 109 |
+
<p id="p-24" num="24">Therefore, the bimodal representation overweights X-Ray intensity values inside the cavity wall and ultrasound intensity values in and outside the cavity wall. An advantage is that the bimodal representation locally benefits from the best information available.</p>
|
| 110 |
+
<p id="p-25" num="25">
|
| 111 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 112 |
+
In a third embodiment of the invention, the region of interest is a 3D subset of the 3D ultrasound data set, which either lies behind the reference plane along the X-Ray direction or forms a slab around the reference plane. A volume rendered view of the 3D ultrasound data included in said selected region of interest is provided. The bimodal representation is built up by combining the intensity values of points of the 2D X-ray projection with the intensity <boundary-data type="line-number">20 </boundary-data>
|
| 113 |
+
values of the corresponding points in the volume rendered view. An advantage is to provide a perspective view of the surrounding tissues. </p>
|
| 114 |
+
<p id="p-26" num="26">The system in accordance with the invention is capable of acquiring the 2D X-Ray image and the 3D ultrasound data set in real-time. Therefore, the medical instrument can be tracked in each new 2D X-Ray image and 3D ultrasound data set.</p>
|
| 115 |
+
<p id="p-27" num="27">
|
| 116 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 117 |
+
In a fourth embodiment of the invention, the system comprises controlling means for periodically triggering the probe localization means. As a matter of fact, the position of the ultrasound probe within the referential of the X-Ray acquisition means may be changed by external movements of the patient like respiratory movements during the clinical procedure. </p>
|
| 118 |
+
<p id="p-28" num="28">Therefore, the localization of the ultrasound probe has to be updated regularly.</p>
|
| 119 |
+
<p id="p-29" num="29">
|
| 120 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 121 |
+
In a fifth embodiment of the invention, the system comprises means for estimating and compensating a motion of a current 3D ultrasound data set acquired at a time t with respect to a previous 3D ultrasound data set acquired at a time t-<confidence value="5">1</confidence>
|
| 122 |
+
. An advantage is that small displacements of the ultrasound probe can be corrected without triggering the probe <page-break num="6"/>
|
| 123 |
+
<boundary-data type="header">WO 2005/063125 PCT<confidence value="66">/I</confidence>
|
| 124 |
+
B2004<confidence value="5">/</confidence>
|
| 125 |
+
004225 </boundary-data>
|
| 126 |
+
<boundary-data type="header">
|
| 127 |
+
<confidence value="8">6</confidence>
|
| 128 |
+
</boundary-data>
|
| 129 |
+
localization means and therefore without interrupting the live visualisation of the medical instrument. </p>
|
| 130 |
+
<p id="p-30" num="30">These and other aspects of the invention will be apparent from and will be elucidated with reference to the embodiments described hereinafter.</p>
|
| 131 |
+
<p id="p-31" num="31">
|
| 132 |
+
<boundary-data type="line-number">
|
| 133 |
+
<confidence value="8">5</confidence>
|
| 134 |
+
</boundary-data>
|
| 135 |
+
</p>
|
| 136 |
+
<heading id="h-5">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 137 |
+
<p id="p-32" num="32">The present invention will now be described in more detail, by way of example, with reference to the accompanying drawings, wherein:</p>
|
| 138 |
+
<p id="p-33" num="33">
|
| 139 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 140 |
+
- Fig. 1 is a schematical drawing of a system in accordance with the invention, - Fig. 2 is a schematical drawing of means for localizing the ultrasound probe within the X- ray referential, when the ultrasound probe is equipped with active localizers, - Figs. 3, 4a and 4b are schematical drawings of means for localizing the ultrasound probe within the X-ray referential, when the probe is equipped with a belt comprising radio- <boundary-data type="line-number">15 </boundary-data>
|
| 141 |
+
opaque markers, - Fig. 5 is a schematical drawing of means for localizing the medical instrument and determining a plane comprising said medical instrument within the 3D ultrasound data set in accordance with the invention, - Fig. 6 is a schematical drawing of the converting means for converting a first localization <boundary-data type="line-number">20 </boundary-data>
|
| 142 |
+
of the region of interest within the referential of the ultrasound acquisition means into a second localization of the region of interest within the referential of the X-Ray acquisition means, - Fig. 7 is a schematical drawing of means for generating a bimodal representation in accordance with a first embodiment of the invention, <boundary-data type="line-number">25 </boundary-data>
|
| 143 |
+
- Fig. 8 is a schematical drawing of means for generating a bimodal representation in accordance with a second embodiment of the invention, - Fig. 9 is a schematical drawing of means for generating a bimodal representation in accordance with a third embodiment of the invention, - Fig. 10 is a schematical drawing of means for compensating a motion between a current <boundary-data type="line-number">30 </boundary-data>
|
| 144 |
+
3D ultrasound data set acquired at a current time and a previous 3D ultrasound data set acquired at a previous time, - Fig. 11 is a functional diagram of the method in accordance with the invention. </p>
|
| 145 |
+
<heading id="h-6">DETAILED DESCRIPTION OF THE INVENTION</heading>
|
| 146 |
+
<boundary-data type="header">WO 2005/063125 PCT<confidence value="68">/I</confidence>
|
| 147 |
+
B2004/004225 </boundary-data>
|
| 148 |
+
<boundary-data type="header">
|
| 149 |
+
<confidence value="8">7</confidence>
|
| 150 |
+
</boundary-data>
|
| 151 |
+
<p id="p-34" num="34">
|
| 152 |
+
<page-break num="7"/>
|
| 153 |
+
The present invention relates to a system for guiding a medical instrument in a patient body. Such a system is particularly adapted for guiding a catheter within the heart cavities in order to diagnose and cure heart diseases, but it can more generally be used for guiding any other medical instrument in the patient body, like for instance a needle. </p>
|
| 154 |
+
<p id="p-35" num="35">
|
| 155 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 156 |
+
The schematical drawing of Fig. 1 shows a patient <part-num-ref name="patient">1,</part-num-ref>
|
| 157 |
+
who is arranged on a patient table <part-num-ref name="patient table">2</part-num-ref>
|
| 158 |
+
and whose symbolically indicated heart <part-num-ref name="and whose symbolically indicated heart">3</part-num-ref>
|
| 159 |
+
is subjected to a treatment by means of a catheter <part-num-ref name="catheter">4</part-num-ref>
|
| 160 |
+
introduced into the body. The system comprises means <part-num-ref name="system comprises means">5</part-num-ref>
|
| 161 |
+
for acquiring a 2D X-ray image of the patient body. Said X-ray acquisition means comprise a focal X-ray source <part-num-ref name="focal X-ray source">6</part-num-ref>
|
| 162 |
+
and a detector <part-num-ref name="detector">7.</part-num-ref>
|
| 163 |
+
Advantageously, these X-ray acquisition means <part-num-ref name="detector 7. Advantageously, these X-ray acquisition means">5</part-num-ref>
|
| 164 |
+
are a C-arm system, as it is <boundary-data type="line-number">10 </boundary-data>
|
| 165 |
+
usually the case in a <confidence value="2222222">cathlab</confidence>
|
| 166 |
+
room. An advantage of such a C-arm system is to be able to have a rotational motion around the patient body in order to produce a plurality of 2D Xray images of the patient at known orientation angles. </p>
|
| 167 |
+
<p id="p-36" num="36">The system in accordance with the invention further comprises means <part-num-ref name="invention further comprises means">8</part-num-ref>
|
| 168 |
+
for acquiring a 3D ultrasound data set from an ultrasound probe <part-num-ref name="ultrasound probe">9,</part-num-ref>
|
| 169 |
+
which has been placed on the patient <boundary-data type="line-number">15 </boundary-data>
|
| 170 |
+
body and fixed by fixation means, for instance a belt <part-num-ref name="belt">10</part-num-ref>
|
| 171 |
+
or a stereotactic arm. It should be noted that both 2D X-ray image and 3D ultrasound data set are acquired in real-time, which enables a live visualization of the medical instrument, when it is guided inside the patient body. </p>
|
| 172 |
+
<p id="p-37" num="37">The X-ray acquisition means 5 are associated with a referential of coordinates <part-num-ref name="referential of coordinates">(<confidence value="5">0</confidence>
|
| 173 |
+
, </part-num-ref>
|
| 174 |
+
x, <boundary-data type="line-number">20 </boundary-data>
|
| 175 |
+
y, z), called X-Ray referential hereinafter, in which the geometry of the focal X-ray source <part-num-ref name="focal X-ray source">6</part-num-ref>
|
| 176 |
+
and the detector <part-num-ref name="detector">7</part-num-ref>
|
| 177 |
+
is known. It should be noted that the X-Ray referential <part-num-ref name="X-Ray referential">(<confidence value="5">0</confidence>
|
| 178 |
+
, </part-num-ref>
|
| 179 |
+
x, y, z) is bound to the fixed part of the X-Ray acquisition means and not to the C-arm. Therefore, the orientation of the C-arm can be expressed in said X-Ray referential. However, the geometry of the X-Ray acquisition means is dependent on a particular position of the C-arm. </p>
|
| 180 |
+
<p id="p-38" num="38">
|
| 181 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 182 |
+
The system in accordance with the invention further comprises means <part-num-ref name="invention further comprises means">11</part-num-ref>
|
| 183 |
+
for localizing the ultrasound probe <part-num-ref name="ultrasound probe">9</part-num-ref>
|
| 184 |
+
within the X-Ray referential <part-num-ref name="X-Ray referential">(<confidence value="5">0</confidence>
|
| 185 |
+
, </part-num-ref>
|
| 186 |
+
x, y, z), means <part-num-ref name="X-Ray referential (0, x, y, z), means">12</part-num-ref>
|
| 187 |
+
for selecting a region of interest around the medical instrument in the 3D ultrasound data set and for providing a first localization Loc<confidence value="1">i</confidence>
|
| 188 |
+
of the region of interest within a referential (<confidence value="4">O</confidence>
|
| 189 |
+
', x', y<confidence value="66">',</confidence>
|
| 190 |
+
z') of the ultrasound acquisition means, means <part-num-ref name="ultrasound acquisition means, means">13</part-num-ref>
|
| 191 |
+
for converting the first localization Loc<confidence value="4">1</confidence>
|
| 192 |
+
of <boundary-data type="line-number">30 </boundary-data>
|
| 193 |
+
the region of interest within a referential (<confidence value="4">O</confidence>
|
| 194 |
+
', x', y', z') into a second localization Loc2 of the region of interest within the X-Ray referential <part-num-ref name="X-Ray referential">(<confidence value="5">0</confidence>
|
| 195 |
+
, </part-num-ref>
|
| 196 |
+
x, y, z) and means for generating a bimodal representation BI by combining data from the 2D X-ray image with the 3D ultrasound data included in the region of interest and localized by the second localization Loc2. The bimodal representation BI is displayed on a screen <part-num-ref name="screen">15.</part-num-ref>
|
| 197 |
+
</p>
|
| 198 |
+
<boundary-data type="header">WO 2005/063125 PCT<confidence value="66">/I</confidence>
|
| 199 |
+
B2004/004225 </boundary-data>
|
| 200 |
+
<boundary-data type="header">
|
| 201 |
+
<confidence value="8">8</confidence>
|
| 202 |
+
</boundary-data>
|
| 203 |
+
<p id="p-39" num="39">
|
| 204 |
+
<page-break num="8"/>
|
| 205 |
+
Referring to Fig. 2, the probe localization means <part-num-ref name="probe localization means">11</part-num-ref>
|
| 206 |
+
are, in a first approach, based on an active localizer <part-num-ref name="active localizer">16,</part-num-ref>
|
| 207 |
+
well-known to those skilled in the art, which is arranged on the ultrasound probe <part-num-ref name="ultrasound probe">9.</part-num-ref>
|
| 208 |
+
Said active localizer <part-num-ref name="ultrasound probe 9. Said active localizer">16,</part-num-ref>
|
| 209 |
+
for instance an RF coil, is intended to transmit an R<confidence value="5">F</confidence>
|
| 210 |
+
signal to an R<confidence value="5">F</confidence>
|
| 211 |
+
receiving unit <part-num-ref name="RF receiving unit">17</part-num-ref>
|
| 212 |
+
placed under the patient body and for instance <boundary-data type="line-number">5 </boundary-data>
|
| 213 |
+
integrated into the table. The R<confidence value="5">F</confidence>
|
| 214 |
+
receiving unit transmits the received signal to measuring means <part-num-ref name="received signal to measuring means">18</part-num-ref>
|
| 215 |
+
for measuring a position of the ultrasound probe <part-num-ref name="ultrasound probe">9</part-num-ref>
|
| 216 |
+
in a known referential, for instance the referential <part-num-ref name="referential">(<confidence value="5">0</confidence>
|
| 217 |
+
, </part-num-ref>
|
| 218 |
+
x, y, z) of the X-ray acquisition means <part-num-ref name="X-ray acquisition means">5.</part-num-ref>
|
| 219 |
+
It should be noted that the active localizer <part-num-ref name="active localizer">16</part-num-ref>
|
| 220 |
+
must be two-dimensional and placed on the ultrasound probe <part-num-ref name="ultrasound probe">9</part-num-ref>
|
| 221 |
+
in such a way that a precise measurement of the position and of the orientation of the ultrasound <boundary-data type="line-number">10 </boundary-data>
|
| 222 |
+
probe can be calculated. It should be noted that a led-based optical localizer could be used as well. A first advantage of this first approach is that it provides a precise localization of the ultrasound probe. A second advantage is that it is performed in real-time and therefore, can be triggered during the clinical procedure. </p>
|
| 223 |
+
<p id="p-40" num="40">In a second approach of the probe localization means <part-num-ref name="probe localization means">11</part-num-ref>
|
| 224 |
+
shown in Fig. 3, the <boundary-data type="line-number">15 </boundary-data>
|
| 225 |
+
ultrasound probe <part-num-ref name="ultrasound probe">9</part-num-ref>
|
| 226 |
+
is fixed around the body of the patient <part-num-ref name="patient">1</part-num-ref>
|
| 227 |
+
with a belt <part-num-ref name="belt">10</part-num-ref>
|
| 228 |
+
equipped with at least three non aligned interdependent radio-opaque markers M<confidence value="4">1</confidence>
|
| 229 |
+
, M2 and M3. For instance, the belt <part-num-ref name="belt">10</part-num-ref>
|
| 230 |
+
comprises a plexiglas plaque, in which the three non aligned interdependent radio- opaque markers are fixed. </p>
|
| 231 |
+
<p id="p-41" num="41">The three markers M<confidence value="28">i,</confidence>
|
| 232 |
+
<confidence value="5">M</confidence>
|
| 233 |
+
2 and <confidence value="5">M</confidence>
|
| 234 |
+
3 belong to a same plane, therefore at least one 2D <boundary-data type="line-number">20 </boundary-data>
|
| 235 |
+
X-ray projection 2DXR<confidence value="4">1</confidence>
|
| 236 |
+
acquired with an orientation angle <part-num-ref name="orientation angle">
|
| 237 |
+
<confidence value="66">01</confidence>
|
| 238 |
+
</part-num-ref>
|
| 239 |
+
of the C-arm system <part-num-ref name="C-arm system">5</part-num-ref>
|
| 240 |
+
is needed in order to determine the position of the ultrasound probe in the X-Ray referential <part-num-ref name="X-Ray referential">
|
| 241 |
+
<confidence value="86">(0</confidence>
|
| 242 |
+
, </part-num-ref>
|
| 243 |
+
x, y, z). However, since the three markers are interdependent, and non-aligned, which means that they form a rigid tetraedre, it is well-known to those skilled in the art that the position of the probe is completely specified by the X-ray projection 2DXR<confidence value="48">I.</confidence>
|
| 244 |
+
</p>
|
| 245 |
+
<p id="p-42" num="42">
|
| 246 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 247 |
+
Referring to Fig. 4a, we consider a detector referential (d<confidence value="5">O</confidence>
|
| 248 |
+
, dx, dy). Six parameters like for instance the coordinates (dx<confidence value="4">i</confidence>
|
| 249 |
+
, dy<confidence value="4">1</confidence>
|
| 250 |
+
), (dx2, <confidence value="66">dy</confidence>
|
| 251 |
+
2), (dx3, dy3) of the projections P<confidence value="4">I</confidence>
|
| 252 |
+
, P2, P3 of the three markers M<confidence value="48">1,</confidence>
|
| 253 |
+
<confidence value="5">M</confidence>
|
| 254 |
+
2 and M3 in the first 2D X-ray image 2DXR do completely specify the position of the ultrasound probe <part-num-ref name="ultrasound probe">9</part-num-ref>
|
| 255 |
+
in the X-Ray referential <part-num-ref name="X-Ray referential">(<confidence value="5">0</confidence>
|
| 256 |
+
, </part-num-ref>
|
| 257 |
+
x, y, z). A first advantage of using radio-opaque markers M<confidence value="4">I</confidence>
|
| 258 |
+
, M2 and M3 is that they appear in a 2D X-Ray <boundary-data type="line-number">30 </boundary-data>
|
| 259 |
+
projection with a very high contrast, which facilitates their localization. Such a localization may be achieved manually or automatically. In the manual case, a user may click on at least two radio-opaque markers in each 2D X-ray image. In the automatical case, image processing techniques well known to those skilled in the art, like for instance a morphological filter, may be used for detecting the radio-opaque markers, which appear as highly contrasted blobs in <page-break num="9"/>
|
| 260 |
+
<boundary-data type="header">WO 2005/063125 PCT<confidence value="5">/</confidence>
|
| 261 |
+
IB2004/004225 </boundary-data>
|
| 262 |
+
<boundary-data type="header">
|
| 263 |
+
<confidence value="8">9</confidence>
|
| 264 |
+
</boundary-data>
|
| 265 |
+
the 2D X-ray projections. A second advantage is that such a localization is performed in real- time and therefore does not imply any peri-interventional step. It should be noted however that there is a priori no need to displace the ultrasound probe during the clinical procedure, because ultrasound data are intended to be used once the medical instrument has been guided <boundary-data type="line-number">5 </boundary-data>
|
| 266 |
+
in a cavity of the patient body to be investigated. A third advantage is that it does not introduce metallic objects in the field of view of the X-Ray and ultrasound acquisition means. </p>
|
| 267 |
+
<p id="p-43" num="43">In an alternative to the second approach, a second 2D X-Ray image 2DXR2 is acquired with a second orientation angle <part-num-ref name="second orientation angle">
|
| 268 |
+
<confidence value="5">0</confidence>
|
| 269 |
+
2 </part-num-ref>
|
| 270 |
+
of the C-arm system <part-num-ref name="C-arm system">5,</part-num-ref>
|
| 271 |
+
as shown in Fig. 4B. This second X-Ray image allows to determine the coordinates (<confidence value="2222">dx'1</confidence>
|
| 272 |
+
, dy'<confidence value="4">1</confidence>
|
| 273 |
+
), (dx'2, dy'2), (dx'3<confidence value="5">,</confidence>
|
| 274 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 275 |
+
dy'3) of a new set of projections P'<confidence value="45">1,</confidence>
|
| 276 |
+
P'2, P'3 of the three markers M<confidence value="4">1</confidence>
|
| 277 |
+
, M2 and M3. It should be noted that the localized points P<confidence value="4">1</confidence>
|
| 278 |
+
, P2, P3 and P'<confidence value="4">1</confidence>
|
| 279 |
+
, P'2 and P'<confidence value="5">3</confidence>
|
| 280 |
+
follow epipolar constraints: this means for instance that a line L<confidence value="4">1</confidence>
|
| 281 |
+
linking the source focal point to the point P<confidence value="5">1</confidence>
|
| 282 |
+
appears as a projected line L'<confidence value="4">I</confidence>
|
| 283 |
+
in the second X-ray image 2DXR2, which comprises P'<confidence value="4">I</confidence>
|
| 284 |
+
. A first advantage is that P'<confidence value="2">i</confidence>
|
| 285 |
+
has not to be searched within the whole image, but only on the projected line L'<confidence value="58">1.</confidence>
|
| 286 |
+
</p>
|
| 287 |
+
<p id="p-44" num="44">
|
| 288 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 289 |
+
A second advantage is that it gives a way of associating the points P<confidence value="4">1</confidence>
|
| 290 |
+
, P2, P3 and <confidence value="665">P'1</confidence>
|
| 291 |
+
, P'2, P'<confidence value="5">3</confidence>
|
| 292 |
+
with the right markers M<confidence value="4">1</confidence>
|
| 293 |
+
, M2 and M3. </p>
|
| 294 |
+
<p id="p-45" num="45">Such a localization of the ultrasound probe <part-num-ref name="ultrasound probe">9,</part-num-ref>
|
| 295 |
+
which involves two 2D X-Ray images is not performed in real-time and has therefore to be handled in a peri-interventional step of the clinical procedure. An advantage of acquiring two 2D X-Ray images is that the precision <boundary-data type="line-number">20 </boundary-data>
|
| 296 |
+
of the localization is greatly increased. </p>
|
| 297 |
+
<p id="p-46" num="46">Once the ultrasound probe <part-num-ref name="ultrasound probe">9</part-num-ref>
|
| 298 |
+
has been located in the X-Ray referential <part-num-ref name="X-Ray referential">(<confidence value="5">0</confidence>
|
| 299 |
+
, </part-num-ref>
|
| 300 |
+
x, y, z), an orientation of the probe is known and therefore, the location of the 3D ultrasound data set <part-num-ref name="3D ultrasound data set">22,</part-num-ref>
|
| 301 |
+
also called 3D ultrasound cone, can be deduced. This is achieved by the converting means <part-num-ref name="converting means">13</part-num-ref>
|
| 302 |
+
which calculate a position of a point of said 3D ultrasound data set in the X-Ray referential <boundary-data type="line-number">25 </boundary-data>
|
| 303 |
+
from said ultrasound probe localization. A projection of said point on the detector in accordance with the geometry of the X-Ray acquisition means can also be deduced. </p>
|
| 304 |
+
<p id="p-47" num="47">Referring to Fig. 5, the system in accordance with the invention comprises means <part-num-ref name="invention comprises means">12</part-num-ref>
|
| 305 |
+
for selecting a region of interest <part-num-ref name="region of interest">35</part-num-ref>
|
| 306 |
+
around the medical instrument <part-num-ref name="medical instrument">4</part-num-ref>
|
| 307 |
+
within the 3D ultrasound <boundary-data type="line-number">30 </boundary-data>
|
| 308 |
+
data set <part-num-ref name="3D ultrasound data set">21.</part-num-ref>
|
| 309 |
+
A reference plane comprising a part of the medical instrument is defined. </p>
|
| 310 |
+
<p id="p-48" num="48">Advantageously, said reference plane is chosen perpendicular to the direction of orientation of the X-Ray acquisition means. The region of interest is obtained by cropping a 3D ultrasound data subset, which lies behind said reference plane or by cropping a slab which is formed around said reference plane. In this way, structures which could occlude the visibility <page-break num="10"/>
|
| 311 |
+
<boundary-data type="header">WO 2005/063125 PCT<confidence value="66">/I</confidence>
|
| 312 |
+
B2004<confidence value="5">/</confidence>
|
| 313 |
+
004225 </boundary-data>
|
| 314 |
+
<boundary-data type="header">
|
| 315 |
+
<confidence value="88">10</confidence>
|
| 316 |
+
</boundary-data>
|
| 317 |
+
of medical instrument in the 3D ultrasound data set are removed. In a first approach, the user interactively selects the region of interest <part-num-ref name="region of interest">35</part-num-ref>
|
| 318 |
+
in the 3D ultrasound data set. In a second approach, a location of said reference plane can be predefined, for instance at a predefined reference depth equal to a third of the depth of the 3D data set. This predefined reference <boundary-data type="line-number">5 </boundary-data>
|
| 319 |
+
plane may be further rotated for searching a viewing angle view within the 3D ultrasound data set from which the medical instrument is more visible. A rotated reference plane <part-num-ref name="rotated reference plane">33</part-num-ref>
|
| 320 |
+
is obtained. Advantageously said viewing angle is applied to the C-arm system in order to optimize the 2D X-ray image. </p>
|
| 321 |
+
<p id="p-49" num="49">Advantageously the selection means <part-num-ref name="selection means">12</part-num-ref>
|
| 322 |
+
comprise means for detecting the medical <boundary-data type="line-number">10 </boundary-data>
|
| 323 |
+
instrument <part-num-ref name="medical instrument">4</part-num-ref>
|
| 324 |
+
within the 3D ultrasound data set <part-num-ref name="3D ultrasound data set">21.</part-num-ref>
|
| 325 |
+
It should be noted that a medical instrument usually appears with a high contrast within the 3D ultrasound data set. It is for instance the case of an electrophysiology catheter, which comprises a metal tip at its extremity. Said tip is a small and thin segment, which is very echogen and leaves a specific signature in the 3D ultrasound data set. Therefore, either the tip end is considered as a <boundary-data type="line-number">15 </boundary-data>
|
| 326 |
+
punctual landmark or the whole tip is considered as an elongated landmark. </p>
|
| 327 |
+
<p id="p-50" num="50">Consequently, said detection means involve image processing techniques, which are well known to those skilled in the art, for enhancing either a highly contrasted blob or elongated shape in a relatively uniform background.</p>
|
| 328 |
+
<p id="p-51" num="51">The detection means allow to automatically define the reference plane <part-num-ref name="reference plane">30</part-num-ref>
|
| 329 |
+
by a point <boundary-data type="line-number">20 </boundary-data>
|
| 330 |
+
EP<confidence value="4">1</confidence>
|
| 331 |
+
and a normal orientation <part-num-ref name="normal orientation">
|
| 332 |
+
<confidence value="5">9</confidence>
|
| 333 |
+
, </part-num-ref>
|
| 334 |
+
where the point EP<confidence value="4">I</confidence>
|
| 335 |
+
for instance corresponds to the detected extremity of the medical instrument, for instance the end of the tip <part-num-ref name="tip">31,</part-num-ref>
|
| 336 |
+
and the normal orientation <confidence value="5">N</confidence>
|
| 337 |
+
to the known orientation <part-num-ref name="known orientation">32</part-num-ref>
|
| 338 |
+
of the X-ray source <part-num-ref name="X-ray source">6.</part-num-ref>
|
| 339 |
+
</p>
|
| 340 |
+
<p id="p-52" num="52">In an alternative the reference plane <part-num-ref name="reference plane">33</part-num-ref>
|
| 341 |
+
is defined by at least three non aligned points <confidence value="884">EP1</confidence>
|
| 342 |
+
, EP2 and EP3 given by the detection of the medical instrument <part-num-ref name="medical instrument">4.</part-num-ref>
|
| 343 |
+
A second normal <confidence value="5">'</confidence>
|
| 344 |
+
<confidence value="88">is</confidence>
|
| 345 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 346 |
+
defined, which can advantageously serve for reorienting the X-ray source <part-num-ref name="X-ray source">6</part-num-ref>
|
| 347 |
+
in order to optimize the X-ray acquisition with respect to the detected position of the medical instrument <part-num-ref name="medical instrument">
|
| 348 |
+
<confidence value="88">4.</confidence>
|
| 349 |
+
</part-num-ref>
|
| 350 |
+
</p>
|
| 351 |
+
<p id="p-53" num="53">Referring to Fig. 6, a mapping between points included into the reference plane <part-num-ref name="reference plane">30,</part-num-ref>
|
| 352 |
+
<part-num-ref name="reference plane 30,">33</part-num-ref>
|
| 353 |
+
and points included into the 2D X-ray image <part-num-ref name="2D X-ray image">40</part-num-ref>
|
| 354 |
+
can be calculated from the knowledge of the <boundary-data type="line-number">30 </boundary-data>
|
| 355 |
+
geometry of the X-Ray acquisition means and of the second localization of the ultrasound probe <part-num-ref name="ultrasound probe">9</part-num-ref>
|
| 356 |
+
within the X-Ray referential <part-num-ref name="X-Ray referential">(<confidence value="5">0</confidence>
|
| 357 |
+
, </part-num-ref>
|
| 358 |
+
x, y, z) provided by the converting means <part-num-ref name="converting means">13.</part-num-ref>
|
| 359 |
+
For instance, the point EP<confidence value="4">1</confidence>
|
| 360 |
+
is projected on a point P(EP<confidence value="4">1</confidence>
|
| 361 |
+
) in the 2D X-Ray image <part-num-ref name="2D X-Ray image">40</part-num-ref>
|
| 362 |
+
in accordance with a projection line <part-num-ref name="projection line">36.</part-num-ref>
|
| 363 |
+
</p>
|
| 364 |
+
<boundary-data type="header">WO 2005/063125 PCT<confidence value="66">/I</confidence>
|
| 365 |
+
B2004<confidence value="5">/</confidence>
|
| 366 |
+
004225 </boundary-data>
|
| 367 |
+
<boundary-data type="header">
|
| 368 |
+
<confidence value="88">11</confidence>
|
| 369 |
+
</boundary-data>
|
| 370 |
+
<p id="p-54" num="54">
|
| 371 |
+
<page-break num="11"/>
|
| 372 |
+
The generation and display means 14 in accordance with the invention are intended to generate a bimodal representation of the medical instrument, in which information coming from both the 2D X-ray image and the 3D ultrasound data set are combined. </p>
|
| 373 |
+
<p id="p-55" num="55">
|
| 374 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 375 |
+
Preferably, such a combination is X-ray driven, which means that it is made on the basis of a 2D X-ray image <part-num-ref name="2D X-ray image">40,</part-num-ref>
|
| 376 |
+
as shown in Fig. 7. </p>
|
| 377 |
+
<p id="p-56" num="56">In a first embodiment of the invention, the region of interest of the medical instrument is included into the reference plane <part-num-ref name="reference plane">30,</part-num-ref>
|
| 378 |
+
<part-num-ref name="reference plane 30,">33.</part-num-ref>
|
| 379 |
+
Therefore, the ultrasound information contained in the region of interest corresponds to a 2D ultrasound view <part-num-ref name="2D ultrasound view">41,</part-num-ref>
|
| 380 |
+
which is obtained by sampling <boundary-data type="line-number">10 </boundary-data>
|
| 381 |
+
the 3D ultrasound data set over the reference plane <part-num-ref name="reference plane">30,</part-num-ref>
|
| 382 |
+
<part-num-ref name="reference plane 30,">33.</part-num-ref>
|
| 383 |
+
</p>
|
| 384 |
+
<p id="p-57" num="57">The bimodal representation is an image formed such that the intensity values of all the points of the 2D X-ray projection <part-num-ref name="2D X-ray projection">40</part-num-ref>
|
| 385 |
+
which have a corresponding point in the 2D ultrasound view <part-num-ref name="2D ultrasound view">41</part-num-ref>
|
| 386 |
+
are combined. Such a combination is for instance defined by a scalar function f of a first intensity value I<confidence value="2">,</confidence>
|
| 387 |
+
of a point of the 2D X-Ray image <part-num-ref name="2D X-Ray image">40</part-num-ref>
|
| 388 |
+
and a second intensity value <confidence value="5">I</confidence>
|
| 389 |
+
2 of <boundary-data type="line-number">15 </boundary-data>
|
| 390 |
+
the corresponding point in the 2D ultrasound view <part-num-ref name="2D ultrasound view">41.</part-num-ref>
|
| 391 |
+
Such a scalar function f provides an intensity value I, for instance, by implementing an alpha-blending technique, which is well- known to those skilled in the art, in the following way: </p>
|
| 392 |
+
<p id="p-58" num="58">
|
| 393 |
+
<confidence value="88">I=</confidence>
|
| 394 |
+
<confidence value="88558866885">f(I,,I2)=al</confidence>
|
| 395 |
+
+(1-<confidence value="5868">a)I2</confidence>
|
| 396 |
+
<confidence value="5">I</confidence>
|
| 397 |
+
f a is equal to one, then the intensity value I of the bimodal representation is equal to <boundary-data type="line-number">20 </boundary-data>
|
| 398 |
+
the first X-Ray intensity I<confidence value="2">1</confidence>
|
| 399 |
+
. On the contrary, if a is equal to zero, the intensity value I of the bimodal representation is equal to the second ultrasound intensity <confidence value="5">I</confidence>
|
| 400 |
+
2, which means that the intensity value of the point of the 2D X-Ray image is replaced by the intensity value of the corresponding point of the 2D ultrasound image <part-num-ref name="2D ultrasound image">41.</part-num-ref>
|
| 401 |
+
</p>
|
| 402 |
+
<p id="p-59" num="59">The ultrasound acquisition means provide a 3D ultrasound data set which is focused <boundary-data type="line-number">25 </boundary-data>
|
| 403 |
+
on the medical instrument. With the invention, the combination of the X-Ray and ultrasound intensity values has the advantage to improve the visibility of the tissues surrounding the medical instrument. </p>
|
| 404 |
+
<p id="p-60" num="60">It is well known to those skilled in the art that the projection of the medical instrument given by the X-ray source <part-num-ref name="X-ray source">7</part-num-ref>
|
| 405 |
+
on the detector <part-num-ref name="detector">7</part-num-ref>
|
| 406 |
+
is of good quality and benefits from <boundary-data type="line-number">30 </boundary-data>
|
| 407 |
+
high resolution and contrast. When a detection of the medical instrument within the region of interest of the 3D ultrasound data set has been made available by the detection means, then a position of the projection of the medical instrument <part-num-ref name="medical instrument">4</part-num-ref>
|
| 408 |
+
within the 2D X-ray projection <part-num-ref name="2D X-ray projection">40,</part-num-ref>
|
| 409 |
+
that is in the detector referential (d<confidence value="5">O</confidence>
|
| 410 |
+
, dx, dy), can be derived from the position of the medical <page-break num="12"/>
|
| 411 |
+
<boundary-data type="header">WO 2005/063125 PCT<confidence value="66">/I</confidence>
|
| 412 |
+
B2004/004225 </boundary-data>
|
| 413 |
+
<boundary-data type="header">
|
| 414 |
+
<confidence value="88">12</confidence>
|
| 415 |
+
</boundary-data>
|
| 416 |
+
instrument in the X-Ray referential <part-num-ref name="X-Ray referential">(<confidence value="5">0</confidence>
|
| 417 |
+
, </part-num-ref>
|
| 418 |
+
x, y, z). This position is for instance a set <part-num-ref name="set">43</part-num-ref>
|
| 419 |
+
of points of the X-ray projection corresponding to a set of points <part-num-ref name="set of points">42</part-num-ref>
|
| 420 |
+
within the 2D ultrasound view <part-num-ref name="2D ultrasound view">41.</part-num-ref>
|
| 421 |
+
</p>
|
| 422 |
+
<p id="p-61" num="61">Advantageously, the intensity values of the points of the 2D X-ray projection <part-num-ref name="2D X-ray projection">40</part-num-ref>
|
| 423 |
+
belonging to the detected medical instrument are given to the corresponding points of the <boundary-data type="line-number">5 </boundary-data>
|
| 424 |
+
bimodal representation. An advantage is to keep the good visibility and resolution of the medical instrument provided by the X-ray acquisition means. </p>
|
| 425 |
+
<p id="p-62" num="62">In a second embodiment of the invention shown in Fig. 8, the system in accordance with the invention further comprises means for segmenting a wall tissue region, for instance the endocardiac wall <part-num-ref name="endocardiac wall">44</part-num-ref>
|
| 426 |
+
in the neigbourhood of the medical instrument <part-num-ref name="medical instrument">4.</part-num-ref>
|
| 427 |
+
This is achieved by <boundary-data type="line-number">10 </boundary-data>
|
| 428 |
+
image processing techniques such as intensity value thresholding, since wall tissues like myocardiu<confidence value="7">m</confidence>
|
| 429 |
+
appear brighter than blood in ultrasound images. </p>
|
| 430 |
+
<p id="p-63" num="63">Another possibility is to detect borders, for instance by using an active contour technique (also called "snake"). This technique, well known to those skilled in the art, firstly consists in defining an initial contour and secondly in making said initial contour evolve <boundary-data type="line-number">15 </boundary-data>
|
| 431 |
+
under the influence of internal and external forces. A final contour <part-num-ref name="final contour">46</part-num-ref>
|
| 432 |
+
is obtained. It is then possible to differentiate points located inside from points located outside the contour <part-num-ref name="contour">46</part-num-ref>
|
| 433 |
+
and to only give to the outside points the intensity values of the corresponding points of the 2D ultrasound view <part-num-ref name="2D ultrasound view">41.</part-num-ref>
|
| 434 |
+
An advantage of this second embodiment is to benefit from X-ray information in a larger surrounding of the medical instrument <part-num-ref name="medical instrument">4.</part-num-ref>
|
| 435 |
+
</p>
|
| 436 |
+
<p id="p-64" num="64">
|
| 437 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 438 |
+
In a third embodiment of the invention schematically presented in Fig. 9, the system in accordance with the invention further comprises means for generating a volume rendered image <part-num-ref name="volume rendered image">51</part-num-ref>
|
| 439 |
+
of the defined region of interest <part-num-ref name="defined region of interest">35.</part-num-ref>
|
| 440 |
+
In the present example, the region of interest <part-num-ref name="region of interest">35</part-num-ref>
|
| 441 |
+
is a slab <part-num-ref name="slab">50.</part-num-ref>
|
| 442 |
+
The volume rendered image <part-num-ref name="volume rendered image">51</part-num-ref>
|
| 443 |
+
is obtained by integrating the 3D ultrasound data in accordance with a direction, for instance the direction of orientation of the <boundary-data type="line-number">25 </boundary-data>
|
| 444 |
+
X-Ray acquisition means, as illustrated by the cylinder <part-num-ref name="cylinder">52.</part-num-ref>
|
| 445 |
+
Said volume rendered image <part-num-ref name="cylinder 52. Said volume rendered image">51</part-num-ref>
|
| 446 |
+
is used instead of the 2D ultrasound view <part-num-ref name="2D ultrasound view">41</part-num-ref>
|
| 447 |
+
and combined with the 2D X-ray image <part-num-ref name="2D X-ray image">40</part-num-ref>
|
| 448 |
+
for generating a bimodal representation <part-num-ref name="bimodal representation">53</part-num-ref>
|
| 449 |
+
in a similar way as previously described. An advantage of this third approach is to provide a perspective view of the neighbourhood of the medical instrument <part-num-ref name="medical instrument">4,</part-num-ref>
|
| 450 |
+
which are for instance the heart cavities. </p>
|
| 451 |
+
<p id="p-65" num="65">
|
| 452 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 453 |
+
It should be noted that the generation means <part-num-ref name="generation means">14</part-num-ref>
|
| 454 |
+
could inversely generate a bimodal representation on the basis of the 3D ultrasound data set and replace X-ray information by ultrasound information. However, it is of less interest, because in this case, the bimodal representation has an image field which is reduced to the one of the 3D ultrasound acquisition means. </p>
|
| 455 |
+
<boundary-data type="header">WO 2005/063125 PCT<confidence value="68">/I</confidence>
|
| 456 |
+
B2004<confidence value="5">/</confidence>
|
| 457 |
+
004225 </boundary-data>
|
| 458 |
+
<boundary-data type="header">
|
| 459 |
+
<confidence value="88">13</confidence>
|
| 460 |
+
</boundary-data>
|
| 461 |
+
<p id="p-66" num="66">
|
| 462 |
+
<page-break num="13"/>
|
| 463 |
+
The system is intended to provide both a live 2D X-Ray image and a live 3D ultrasound data set. Although a localization of the probe has already been performed in a peri-interventional step, it could be necessary to update such a localization when patient movements occur, in particular if the respiratory movements have to be compensated for. As <boundary-data type="line-number">5 </boundary-data>
|
| 464 |
+
a matter of fact, a patient movement may cause a change of position of the ultrasound probe within the X-Ray referential and therefore induce errors when mapping the 2D X-Ray data with the 3D ultrasound data. Therefore, in a fourth embodiment of the invention, the system comprises controlling means for periodically triggering the means for localizing the ultrasound probe within the X-Ray referential. Such a triggering can be performed manually, <boundary-data type="line-number">10 </boundary-data>
|
| 465 |
+
when the user judges it necessary or automatically at regular time intervals, to the extent of retriggering this probe localization for every new 2D X-Ray image or 3D ultrasound data set acquired. It should be noted that in this case, the probe localization has to be performed in real-time.. An advantage is that it avoids any accumulation of errors when mapping the 2D X-Ray data with the 3D ultrasound data. </p>
|
| 466 |
+
<p id="p-67" num="67">
|
| 467 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 468 |
+
In a fifth embodiment of the invention, the system comprises means for compensating any relative motion of the ultrasound probe with respect to the patient heart in the interval between two successive probe localizations. These motion compensation means are intended to compensate a motion between a current 3D ultrasound data set 3DUS(to+ t) acquired at a current time to+t and a previous 3D ultrasound data set 3DUS(to) acquired at a previous time <boundary-data type="line-number">20 </boundary-data>
|
| 469 |
+
to, both ultrasound data sets corresponding to a same phase of the heart cycle. Firstly, motion vectors linking points of the current 3D ultrasound data set 3DUS(to+ t) with points of the previous 3D ultrasound data set 3DUS(to) are estimated and the points of the current 3D ultrasound data set 3DUS(to+ t) are displaced in accordance with the calculated motion vectors. Therefore, a motion compensated current 3D ultrasound data set MC(3DUS(to+t)) is <boundary-data type="line-number">25 </boundary-data>
|
| 470 |
+
obtained, which is expected to be closer to the previous 3D ultrasound data set 3DUS(to). In a first approach, a block-matching technique, well known to those skilled in the domain of video compression, is advantageously used. Referring to Fig. 10, which illustrates the principles of a block matching in the 2D case for simplicity reasons, the current and previous 3D ultrasound data sets 3DUS(to+t) and 3DUS(t<confidence value="4">0</confidence>
|
| 471 |
+
)are divided into blocks, for instance of <boundary-data type="line-number">30 </boundary-data>
|
| 472 |
+
8x8x8 points and for each block B<confidence value="14">n1</confidence>
|
| 473 |
+
of the current 3D ultrasound data set a search of the block B<confidence value="1">o</confidence>
|
| 474 |
+
o of the previous 3D ultrasound data set is performed, which leads to a maximum of correlation. A motion vector <confidence value="2">W</confidence>
|
| 475 |
+
= Bn<confidence value="881">Bn0</confidence>
|
| 476 |
+
is obtained. </p>
|
| 477 |
+
<p id="p-68" num="68">Therefore the motion compensation means are intended to compensate in the current ultrasound image for small motions which may have occurred between time to and time to + t.</p>
|
| 478 |
+
<boundary-data type="header">WO 2005/063125 PCT<confidence value="68">/I</confidence>
|
| 479 |
+
B2004/004225 </boundary-data>
|
| 480 |
+
<boundary-data type="header">
|
| 481 |
+
<confidence value="88">14</confidence>
|
| 482 |
+
</boundary-data>
|
| 483 |
+
<p id="p-69" num="69">
|
| 484 |
+
<page-break num="14"/>
|
| 485 |
+
It should be noted that motion compensation is efficient when small differences exist between both 3D ultrasound data sets. An advantage of the fifth embodiment of the invention is to provide a solution for compensating errors of localization due to small movements of the probe with respect to the cavity to be explored, like the heart, which is compatible with live <boundary-data type="line-number">5 </boundary-data>
|
| 486 |
+
visualization. This solution is particularily advantageous when the probe localization cannot be performed in real-time, for instance when several angular views provided by the C-arm are involved. In this case, the motion compensation means may be advantageously used in the mean time of two successive probe localizations. </p>
|
| 487 |
+
<p id="p-70" num="70">It should be noted that the system in accordance with the invention has a particular <boundary-data type="line-number">10 </boundary-data>
|
| 488 |
+
interest for electrophysiology procedures, which consist either in generating an electrical activation map of a heart cavity wall for diagnosing heart diseases or in burning a zone of the wall tissue, which has been identified as abnormal. As a matter of fact, by providing a live visualisation of a large viewing field of the area of operation, in which the medical instrument, the bone structures and the surrounding wall tissues are simultaneously visible, <boundary-data type="line-number">15 </boundary-data>
|
| 489 |
+
the system in accordance with the invention facilites a generation of the electrical activation map. </p>
|
| 490 |
+
<p id="p-71" num="71">The invention also relates to a method of guiding a medical instrument <part-num-ref name="medical instrument">4</part-num-ref>
|
| 491 |
+
in a patient body. Referring to Fig. 11, such a method comprises the steps of<confidence value="5">:</confidence>
|
| 492 |
+
</p>
|
| 493 |
+
<p id="p-72" num="72">- acquiring 60 a two-dimensional X-ray image of said medical instrument using an X-ray <boundary-data type="line-number">20 </boundary-data>
|
| 494 |
+
acquisition system, - acquiring 61a three-dimensional ultrasound data set of said medical instrument using said ultrasound probe, - localizing <part-num-ref name="X-ray acquisition system, - acquiring 61a three-dimensional ultrasound data set of said medical instrument using said ultrasound probe, - localizing">62</part-num-ref>
|
| 495 |
+
said ultrasound probe in a referential of said X-ray acquisition system, - selecting <part-num-ref name="referential of said X-ray acquisition system, - selecting">63</part-num-ref>
|
| 496 |
+
a region of interest of said medical instrument within said 3D ultrasound data <boundary-data type="line-number">25 </boundary-data>
|
| 497 |
+
set and providing a first localization of said region of interest within a referential of the ultrasound acquisition means, - converting <part-num-ref name="ultrasound acquisition means, - converting">64</part-num-ref>
|
| 498 |
+
said first localization within said referential of the 3D ultrasound data set into a second X-Ray localization within said referential of the X-ray acquisition system, - generating <part-num-ref name="X-ray acquisition system, - generating">65</part-num-ref>
|
| 499 |
+
and displaying a bimodal representation of said medical instrument in <part-num-ref name="bimodal representation of said medical instrument in">30</part-num-ref>
|
| 500 |
+
which both 2D X-ray image and the 3D ultrasound data included in said region of interest are combined using said second localization. </p>
|
| 501 |
+
<boundary-data type="header">WO 2005/063125 PCT<confidence value="54">/l</confidence>
|
| 502 |
+
B2004/004225 </boundary-data>
|
| 503 |
+
<boundary-data type="header">
|
| 504 |
+
<confidence value="88">15</confidence>
|
| 505 |
+
</boundary-data>
|
| 506 |
+
<p id="p-73" num="73">
|
| 507 |
+
<page-break num="15"/>
|
| 508 |
+
The drawings and their description hereinbefore illustrate rather than limit the invention. It will be evident that there are numerous alternatives, which fall within the scope of the appended claims. In this respect the following closing remarks are made: there are numerous ways of implementing functions by means of items of hardware or software, or <boundary-data type="line-number">5 </boundary-data>
|
| 509 |
+
both. In this respect, the drawings are very diagrammatic, each representing only one possible embodiment of the invention. Thus, although a drawing shows different functions as different blocks, this by no means excludes that a single item of hardware or software carries out several functions, nor does it exclude that a single function is carried out by an assembly of items of hardware or software, or both. </p>
|
| 510 |
+
<p id="p-74" num="74">
|
| 511 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 512 |
+
Any reference sign in a claim should not be construed as limiting the claim. Use of the verb "to comprise" and its conjugations does not exclude the presence of elements or steps other than those stated in a claim. Use of the article "a" or "an<confidence value="5">"</confidence>
|
| 513 |
+
preceding an element or step does not exclude the presence of a plurality of such elements or steps. </p>
|
| 514 |
+
</description>
|
| 515 |
+
</us-patent-application>
|
| 516 |
+
|
prior_art/10864207.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
prior_art/10879592.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="10879592.07-18-2014.HXRQTZWYPXXIFW3.SPEC.XML" pat:id="HXRQTZWYPXXIFW3"><pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001"><pat:ApplicationHeaderDetails><pat:ApplicationNumber>10879592</pat:ApplicationNumber></pat:ApplicationHeaderDetails><pat:PageTotalQuantity>1</pat:PageTotalQuantity><pat:ParagraphTotalQuantity>4</pat:ParagraphTotalQuantity></pat:DocumentHeaderDetails><pat:MailRoomDate>2014-07-18</pat:MailRoomDate><pat:DocumentCreateDateText>2014-07-23</pat:DocumentCreateDateText><pat:DocumentTitle>SPECIFICATION DOCUMENT</pat:DocumentTitle><pat:Specification><?PageStart number='1'?><pat:P pat:pNumber="1" pat:id="p-1">First Named Inventor Misha Dynin Attorney's Docket No. 16113-0340001 Serial No. <pat:PartName pat:idref='PN-00001'>10/879</pat:PartName>,<pat:PartNumber pat:id='PN-00001'>592</pat:PartNumber> Filed <pat:OCRConfidenceData pat:levelNumber='2'>:</pat:OCRConfidenceData> June 30, 2004 Page <pat:OCRConfidenceData pat:levelNumber='2'>:</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='8'>2</pat:OCRConfidenceData> Amendments to the Specification: </pat:P><pat:P pat:pNumber="2" pat:id="p-2">Please <pat:PartName pat:idref='PN-00002'>replace paragraph [0001] on page</pat:PartName> <pat:PartNumber pat:id='PN-00002'>1</pat:PartNumber>, with the following amended paragraph: </pat:P><pat:P pat:pNumber="3" pat:id="p-3">[0001<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> This application is related to co-pending U.S. Utility Patent Application Serial No. <pat:PartName pat:idref='PN-00003'>10/879</pat:PartName>,<pat:PartNumber pat:id='PN-00003'>591</pat:PartNumber>, filed June 30, 2004, entitled, "METHODS AND SYSTEMS FOR E<pat:PartName pat:idref='PN-00004'>NDORS<pat:OCRConfidenceData pat:levelNumber='5'>I</pat:OCRConfidenceData>NG LOCAL SEARCH RESULTS" <pat:OCRConfidenceData pat:levelNumber='254'>(tr</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='2442'>Doet</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='2'>o</pat:OCRConfidenceData></pat:PartName><pat:OCRConfidenceData pat:levelNumber='2'>.</pat:OCRConfidenceData><pat:PartNumber pat:id='PN-00004'><pat:OCRConfidenceData pat:levelNumber='111'>535</pat:OCRConfidenceData></pat:PartNumber><pat:OCRConfidenceData pat:levelNumber='12221'>/2729</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='25'>S.</pat:OCRConfidenceData> </pat:P><pat:P pat:pNumber="4" pat:id="p-4"><pat:OCRConfidenceData pat:levelNumber='8'>2</pat:OCRConfidenceData> </pat:P></pat:Specification></pat:SpecificationDocument>
|
prior_art/10902593.xml
ADDED
|
@@ -0,0 +1,36 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>10902593</doc-number>
|
| 8 |
+
<date>2008-04-28</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 S<confidence value="5">p</confidence>
|
| 14 |
+
ecification: </p>
|
| 15 |
+
<p id="p-2" num="2">Please replace the Title of the application with the following amended Title:</p>
|
| 16 |
+
<heading id="h-1">IMPROVED INSTANT MESSAGE MANAGEMENT USING WINDOWED USER INTERFACE Z-</heading>
|
| 17 |
+
<heading id="h-2">ORDER AND W<confidence value="88">IT</confidence>
|
| 18 |
+
H COLLABORATION DATA <confidence value="666">FOR</confidence>
|
| 19 |
+
<confidence value="88">IM</confidence>
|
| 20 |
+
PRO<confidence value="8">V</confidence>
|
| 21 |
+
ED <confidence value="88">MA</confidence>
|
| 22 |
+
N<confidence value="8">A</confidence>
|
| 23 |
+
GE<confidence value="8">M</confidence>
|
| 24 |
+
ENT <confidence value="66">OF</confidence>
|
| 25 |
+
</heading>
|
| 26 |
+
<heading id="h-3">ACKNOWLEDGE OF <confidence value="8">I</confidence>
|
| 27 |
+
N<confidence value="8">C</confidence>
|
| 28 |
+
OMIN<confidence value="8">G</confidence>
|
| 29 |
+
<confidence value="22222">INSTA</confidence>
|
| 30 |
+
<confidence value="88">NT</confidence>
|
| 31 |
+
MESSAGES </heading>
|
| 32 |
+
<p id="p-3" num="3">Page 2 of <part-num-ref name="of">17</part-num-ref>
|
| 33 |
+
Kessen et al. - 10/902,593 </p>
|
| 34 |
+
</description>
|
| 35 |
+
</us-patent-application>
|
| 36 |
+
|
prior_art/10936465.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
prior_art/10967748.xml
ADDED
|
@@ -0,0 +1,27 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>10967748</doc-number>
|
| 8 |
+
<date>2005-07-13</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">RAH:slm 07/11/05 399064.doc UNR-04-003 Attorney Reference Number 7276-70215-0<confidence value="5">1</confidence>
|
| 14 |
+
PATENT Application Number 10/967,748 Amendments to the S<confidence value="5">p</confidence>
|
| 15 |
+
ecification On page <part-num-ref name="Specification On page">1</part-num-ref>
|
| 16 |
+
of the specification, please replace the paragraph underneath "CROSS- REFERENCE TO RELATED APPLICATIONS" with the following rewritten paragraph: </p>
|
| 17 |
+
<p id="p-2" num="2">This utility application claims the p<confidence value="488">rie</confidence>
|
| 18 |
+
4ty-benefit of, and hereby incorporates by reference in its entirety, the <confidence value="6666625662288486">applicant'prior-</confidence>
|
| 19 |
+
U.S. Provisional Application No. 60/512,504, filed October <part-num-ref name="applicant'prior-U.S. Provisional Application No. 60/512,504, filed October">17,</part-num-ref>
|
| 20 |
+
<part-num-ref name="applicant'prior-U.S. Provisional Application No. 60/512,504, filed October 17,">2003<confidence value="6668">2004</confidence>
|
| 21 |
+
</part-num-ref>
|
| 22 |
+
Page <part-num-ref name="Page">2</part-num-ref>
|
| 23 |
+
of <part-num-ref name="of">25</part-num-ref>
|
| 24 |
+
</p>
|
| 25 |
+
</description>
|
| 26 |
+
</us-patent-application>
|
| 27 |
+
|
prior_art/10992435.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>10992435</doc-number>
|
| 8 |
+
<date>2008-07-17</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">Please AMEND page 30, line 16 - page <part-num-ref name="- page">31,</part-num-ref>
|
| 15 |
+
line <part-num-ref name="- page 31, line">3</part-num-ref>
|
| 16 |
+
as follows: </p>
|
| 17 |
+
<p id="p-2" num="2">Because such information and program instructions may be employed to implement the systems/methods described herein, the present invention relates to machine-readable media that include program instructions, state information, etc. for performing various operations described herein. Examples of machine-readable media include, but are not limited to, magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROM disks; magneto-optical media such as floptical disks; and hardware devices that are specially configured to store and perform program instructions, such as read-only memory devices (ROM) and random access memory (RAM). <confidence value="666">The</confidence>
|
| 18 |
+
in<confidence value="8">v</confidence>
|
| 19 |
+
enti<confidence value="88">on</confidence>
|
| 20 |
+
<confidence value="266">may</confidence>
|
| 21 |
+
<confidence value="6656">also</confidence>
|
| 22 |
+
<confidence value="66">be</confidence>
|
| 23 |
+
lines<confidence value="6">,</confidence>
|
| 24 |
+
<confidence value="2222222">electic</confidence>
|
| 25 |
+
<confidence value="56616">line,</confidence>
|
| 26 |
+
<confidence value="112">eL.</confidence>
|
| 27 |
+
Examples of program instructions include both machine code, such as produced by a compiler, and files containing higher level code that may be executed by the computer using an interpreter. </p>
|
| 28 |
+
<p id="p-3" num="3">Atty Docket No.: C<confidence value="5">I</confidence>
|
| 29 |
+
SCP389/444327 - <confidence value="8">2</confidence>
|
| 30 |
+
- Application No. 10/992,435 </p>
|
| 31 |
+
</description>
|
| 32 |
+
</us-patent-application>
|
| 33 |
+
|
prior_art/11011356.xml
ADDED
|
@@ -0,0 +1,436 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11011356</doc-number>
|
| 8 |
+
<date>2004-12-14</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">Non-Provisional Patent Application</boundary-data>
|
| 14 |
+
<boundary-data type="header">Express Mail No. EV332925751US</boundary-data>
|
| 15 |
+
<heading id="h-1">SYSTEM AND METHOD FOR DRIVING DIRECTIONS</heading>
|
| 16 |
+
<heading id="h-2">BASED ON NON-MAP CRITERIA</heading>
|
| 17 |
+
<heading id="h-3">FIELD OF THE INVENTION</heading>
|
| 18 |
+
<p id="p-1" num="1">The present invention relates generally to map driving <boundary-data type="line-number">5 </boundary-data>
|
| 19 |
+
directions. More specifically, the invention relates to a service that facilitates the map driving directions and user rewards based in part on a variety of non-coordinate criteria. </p>
|
| 20 |
+
<heading id="h-4">BACKGROUND</heading>
|
| 21 |
+
<p id="p-2" num="2">Travel direction web services, such as those available at the <boundary-data type="line-number">10 </boundary-data>
|
| 22 |
+
mapquest.com website, provide trip directions for people traveling by car from one address to another. MAPQUEST.COM is a registered trademark of MapQuest.com, Inc. Such services locate addresses through a process known as "geocoding". Geocoding assigns a latitude-longitude coordinate to an address. Once a latitude-longitude coordinate is <boundary-data type="line-number">15 </boundary-data>
|
| 23 |
+
assigned, the address can be displayed on a map or used in a spatial search. Websites such as mapquest.com use a wide variety of information from many sources to provide geocoding, mapping and routing services. In addition to the major highways shown at various scales for countries around the world, these third party sources provide <boundary-data type="line-number">20 </boundary-data>
|
| 24 |
+
province, city and water boundaries as well as railroad lines for most countries. Third parties may also provide street maps, census data, postal geography, and topographic maps. </p>
|
| 25 |
+
<p id="p-3" num="3">Although map direction services such as the mapquest.com website exist, these services typically focus on guiding people from one <boundary-data type="line-number">25 </boundary-data>
|
| 26 |
+
address to another based on street maps and generally do not consider ambient and non-street-map factors. Such ambient and non-street-map factors can be prevailing and forecasted weather conditions, the nature of a driver's car and car equipment (such as snow tires, weight of vehicle), time of day, holiday dates, gas prices, prevailing economic <boundary-data type="line-number">30 </boundary-data>
|
| 27 |
+
conditions (stock markets, etc.), number of people requesting map directions between two locations at a particular time, terrorist alert levels, nature of food stops along the way, elevation, historical <boundary-data type="header">IBM Docket No. Y<confidence value="5">O</confidence>
|
| 28 |
+
R920040535US1 </boundary-data>
|
| 29 |
+
<boundary-data type="header">
|
| 30 |
+
<confidence value="8">-</confidence>
|
| 31 |
+
<confidence value="8">1</confidence>
|
| 32 |
+
<confidence value="8">-</confidence>
|
| 33 |
+
</boundary-data>
|
| 34 |
+
<page-break num="2"/>
|
| 35 |
+
<boundary-data type="header">Non-Provisional Patent Application</boundary-data>
|
| 36 |
+
<boundary-data type="header">Express Mail No. EV332925751US</boundary-data>
|
| 37 |
+
record of traffic problems, number of traffic lights, number of police tickets given, accidents (predicted and current), weather predictions for dates supplied by the user, crime statistics, and the speed limits on each road in the path. </p>
|
| 38 |
+
<heading id="h-5">SU<confidence value="8">M</confidence>
|
| 39 |
+
MARY OF THE INVENTION </heading>
|
| 40 |
+
<p id="p-4" num="4">
|
| 41 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 42 |
+
The present invention addresses the above-mentioned limitations of the prior art by introducing a system that provides a user with a travel route and considers such ambient or "non-coordinate" factors such as: prevailing and forecasted weather conditions, vehicle <boundary-data type="line-number">10 </boundary-data>
|
| 43 |
+
characteristics (such as snow tires, weight of vehicle), time of day, holiday dates, gas prices, prevailing economic conditions (stock markets, etc.), number of people requesting map directions between two locations at a particular time, terrorist alert levels, nature of food stops along the way, elevation, historical record of traffic problems, <boundary-data type="line-number">15 </boundary-data>
|
| 44 |
+
number of traffic lights, number of police tickets given, accidents (predicted and current), weather predictions for dates supplied by the user, crime statistics, and the speed limits on each road in the path. </p>
|
| 45 |
+
<p id="p-5" num="5">Based on these criteria, the system may advise the traveler of optimal date and time to travel the route. Furthermore, the invention may be <boundary-data type="line-number">20 </boundary-data>
|
| 46 |
+
configured to provide a user with useful routes and may reward users for selecting and using certain routes. </p>
|
| 47 |
+
<p id="p-6" num="6">The present invention can optimize a user's trip based on a user<confidence value="8">'</confidence>
|
| 48 |
+
s profile that includes information about the user in conjunction with ambient and non-street-map factors. Various possible directions <boundary-data type="line-number">25 </boundary-data>
|
| 49 |
+
may be color coded on a map so that various possible choices are visually correlated with a number of non-street-map criteria. </p>
|
| 50 |
+
<p id="p-7" num="7">Thus, one exemplary aspect of the present invention is a method for providing travel directions to a user. The method includes a receiving operation to obtain coordinate information from the user.</p>
|
| 51 |
+
<p id="p-8" num="8">
|
| 52 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 53 |
+
Another receiving operation obtains non-coordinate information from at least one data source. A generating operation automatically generates <boundary-data type="header">IBM Docket No. Y<confidence value="5">O</confidence>
|
| 54 |
+
R920040535US1 </boundary-data>
|
| 55 |
+
<boundary-data type="header">
|
| 56 |
+
<confidence value="58">-2</confidence>
|
| 57 |
+
<confidence value="8">-</confidence>
|
| 58 |
+
</boundary-data>
|
| 59 |
+
<page-break num="3"/>
|
| 60 |
+
<boundary-data type="header">Non-Provisional Patent Application</boundary-data>
|
| 61 |
+
<boundary-data type="header">Express Mail No. EV332925751US</boundary-data>
|
| 62 |
+
at least one trip route based, at least in part, on the coordinate information and non-coordinate information. </p>
|
| 63 |
+
<p id="p-9" num="9">Another exemplary aspect of the present invention is an automated route provider coupled to a client. The route provider includes a <boundary-data type="line-number">5 </boundary-data>
|
| 64 |
+
coordinate information receiving module configured to receive coordinate information from the client. A non-coordinate information receiving module is configured to receive non-coordinate information from at least one data source. A routing module is configured to generate a trip route based, at least in part, on the coordinate <boundary-data type="line-number">10 </boundary-data>
|
| 65 |
+
information and non-coordinate information. </p>
|
| 66 |
+
<p id="p-10" num="10">Yet a further exemplary aspect of the invention is a computer program product configured to receive coordinate information from the user, receive non-coordinate information from at least one 'data source, and generate at least one trip route based, at least in part, on the <boundary-data type="line-number">15 </boundary-data>
|
| 67 |
+
coordinate information and non-coordinate information. </p>
|
| 68 |
+
<p id="p-11" num="11">The foregoing and other features, utilities and advantages of the invention will be apparent from the following more particular description of various embodiments of the invention as illustrated in the accompanying drawings.</p>
|
| 69 |
+
<heading id="h-6">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 70 |
+
<p id="p-12" num="12">
|
| 71 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 72 |
+
Fig. 1 shows an exemplary environment embodying the present invention. </p>
|
| 73 |
+
<p id="p-13" num="13">Fig. 2 shows exemplary modules forming one embodiment of a route provider.</p>
|
| 74 |
+
<p id="p-14" num="14">
|
| 75 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 76 |
+
Fig. 3 shows a flowchart of system operations performed by one embodiment of the present invention. </p>
|
| 77 |
+
<p id="p-15" num="15">
|
| 78 |
+
<confidence value="6">.</confidence>
|
| 79 |
+
Fig. 4 shows a table representing an exemplary data file used by a route provider to generate trip routes. </p>
|
| 80 |
+
<heading id="h-7">DETAILED DESCRIPTION OF THE INVENTION</heading>
|
| 81 |
+
<p id="p-16" num="16">
|
| 82 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 83 |
+
The following description details how the present invention is <boundary-data type="header">IBM Docket No. Y<confidence value="5">O</confidence>
|
| 84 |
+
R920040535US1 </boundary-data>
|
| 85 |
+
<boundary-data type="header">
|
| 86 |
+
<confidence value="58">-3</confidence>
|
| 87 |
+
<confidence value="8">-</confidence>
|
| 88 |
+
</boundary-data>
|
| 89 |
+
<page-break num="4"/>
|
| 90 |
+
<boundary-data type="header">Non-Provisional Patent Application</boundary-data>
|
| 91 |
+
<boundary-data type="header">Express Mail No. EV332925751US</boundary-data>
|
| 92 |
+
employed to calculate and convey map directions based on ambient and non-street-map factors, as well as optionally rewarding users for selecting and using certain routes. Throughout the description of the invention reference is made to Figs. 1-4. When referring to the <boundary-data type="line-number">5 </boundary-data>
|
| 93 |
+
figures, like structures and elements shown throughout are indicated with like reference numerals. </p>
|
| 94 |
+
<p id="p-17" num="17">Fig. 1 shows an exemplary environment <part-num-ref name="exemplary environment">102</part-num-ref>
|
| 95 |
+
embodying the present invention. It is initially noted that the environment <part-num-ref name="environment">102</part-num-ref>
|
| 96 |
+
is presented for illustration purposes only, and is representative of countless <boundary-data type="line-number">10 </boundary-data>
|
| 97 |
+
configurations in which the invention may be implemented. Thus, the present invention should not be construed as limited to the environment configurations shown and discussed herein. </p>
|
| 98 |
+
<p id="p-18" num="18">The environment 102 includes a route provider <part-num-ref name="route provider">104</part-num-ref>
|
| 99 |
+
coupled to a network <part-num-ref name="network">106.</part-num-ref>
|
| 100 |
+
As discussed in more detailed below, the route provider <boundary-data type="line-number">15 </boundary-data>
|
| 101 |
+
<part-num-ref name="route provider">104</part-num-ref>
|
| 102 |
+
is configured to provide one or more trip routes <part-num-ref name="is configured to provide one or more trip routes">108</part-num-ref>
|
| 103 |
+
to users <part-num-ref name="to users">110</part-num-ref>
|
| 104 |
+
based on coordinate and non-coordinate information. The route provider <part-num-ref name="route provider">104</part-num-ref>
|
| 105 |
+
may additionally suggest an optimal departure time for a particular set of trip routes <part-num-ref name="particular set of trip routes">108.</part-num-ref>
|
| 106 |
+
A trip route <part-num-ref name="trip route">108</part-num-ref>
|
| 107 |
+
is a detailed description of a travel path and may be conveyed to a user <part-num-ref name="user">110</part-num-ref>
|
| 108 |
+
through various known <boundary-data type="line-number">20 </boundary-data>
|
| 109 |
+
output methods, such as paper printout, computer display, and synthesized speech. </p>
|
| 110 |
+
<p id="p-19" num="19">Coordinate information is information traditionally used by travel direction web services, such as starting and ending addresses, and geocoded locations. Non-coordinate information, on the other hand, <boundary-data type="line-number">25 </boundary-data>
|
| 111 |
+
includes information such as an expected time of travel, prevailing weather conditions, forecasted weather conditions during the expected time of travel, user vehicle characteristics, holiday dates, fuel prices, toll prices, prevailing economic conditions, number of users requesting travel directions for travel during the expected time of <boundary-data type="line-number">30 </boundary-data>
|
| 112 |
+
travel, terrorist alert levels, nature of food stops, road elevation, historical record of traffic conditions, number of traffic lights, number of speeding tickets issued, historic number of traffic <boundary-data type="header">IBM Docket No. Y<confidence value="5">O</confidence>
|
| 113 |
+
R920040535US1 </boundary-data>
|
| 114 |
+
<boundary-data type="header">
|
| 115 |
+
<confidence value="8">-</confidence>
|
| 116 |
+
<confidence value="8">4</confidence>
|
| 117 |
+
<confidence value="8">-</confidence>
|
| 118 |
+
</boundary-data>
|
| 119 |
+
<page-break num="5"/>
|
| 120 |
+
<boundary-data type="header">Non-Provisional Patent Application</boundary-data>
|
| 121 |
+
<boundary-data type="header">Express Mail No. EV332925751US</boundary-data>
|
| 122 |
+
accidents, predicted <confidence value="8">n</confidence>
|
| 123 |
+
umber of traffic accidents, crime statistics, and the speed limits along the trip route. </p>
|
| 124 |
+
<p id="p-20" num="20">The present invention introduces the notion of a route provider <part-num-ref name="route provider">104.</part-num-ref>
|
| 125 |
+
As used herein, a route provider <part-num-ref name="route provider">104</part-num-ref>
|
| 126 |
+
may be a government or <boundary-data type="line-number">5 </boundary-data>
|
| 127 |
+
private entity that automatically helps drivers obtain optimal driving routes. The route provider <part-num-ref name="route provider">104</part-num-ref>
|
| 128 |
+
may additionally offer economic incentives for driving along predetermined these routes. It is contemplated that the route provider <part-num-ref name="route provider">104</part-num-ref>
|
| 129 |
+
may be a service executing locally on a user's computing device or as a remote service coupled to <boundary-data type="line-number">10 </boundary-data>
|
| 130 |
+
the user's computing device through a computer network <part-num-ref name="computer network">106,</part-num-ref>
|
| 131 |
+
as a shown. </p>
|
| 132 |
+
<p id="p-21" num="21">In a particular embodiment of the invention, the route provider <part-num-ref name="route provider">104</part-num-ref>
|
| 133 |
+
receives non-coordinate information from data sources <part-num-ref name="receives non-coordinate information from data sources">112</part-num-ref>
|
| 134 |
+
coupled to the network <part-num-ref name="network">106.</part-num-ref>
|
| 135 |
+
For example, one data source may be a fueling station <part-num-ref name="fueling station">114</part-num-ref>
|
| 136 |
+
in communication with the route provider <part-num-ref name="route provider">104.</part-num-ref>
|
| 137 |
+
In this <boundary-data type="line-number">15 </boundary-data>
|
| 138 |
+
case, the route provider <part-num-ref name="route provider">104</part-num-ref>
|
| 139 |
+
may periodically receive prices for fuel offered at the fueling station <part-num-ref name="fueling station">114.</part-num-ref>
|
| 140 |
+
The fueling station <part-num-ref name="fueling station">114</part-num-ref>
|
| 141 |
+
may also be configured to provide various other non-coordinate data to the route provider <part-num-ref name="route provider">104,</part-num-ref>
|
| 142 |
+
such as the type of food service it offers (if any) and the road visibility and traffic conditions around the fueling station <boundary-data type="line-number">20 </boundary-data>
|
| 143 |
+
<part-num-ref name="fueling station">104.</part-num-ref>
|
| 144 |
+
</p>
|
| 145 |
+
<p id="p-22" num="22">The route provider 104 may also store a user profile <part-num-ref name="user profile">116</part-num-ref>
|
| 146 |
+
containing, among other information, a preferred routing scheme. The preferred routing scheme lists which non-coordinate information is more important to the user in selecting a trip route. For example, the user <boundary-data type="line-number">25 </boundary-data>
|
| 147 |
+
<part-num-ref name="user">110</part-num-ref>
|
| 148 |
+
may indicate in the profile <part-num-ref name="profile">116</part-num-ref>
|
| 149 |
+
that he or she prefers driving along routes with historically low traffic accidents over routes with high speed limits. Accordingly, the route provider <part-num-ref name="route provider">104</part-num-ref>
|
| 150 |
+
can factor in the user's personal travel preferences indicated by the user profile <part-num-ref name="user profile">116</part-num-ref>
|
| 151 |
+
when generating a trip route <part-num-ref name="trip route">108</part-num-ref>
|
| 152 |
+
for the user <part-num-ref name="user">110.</part-num-ref>
|
| 153 |
+
</p>
|
| 154 |
+
<p id="p-23" num="23">
|
| 155 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 156 |
+
In another embodiment of the invention, the route provider <part-num-ref name="route provider">104</part-num-ref>
|
| 157 |
+
may offer economic incentives for users <part-num-ref name="may offer economic incentives for users">108</part-num-ref>
|
| 158 |
+
to travel along the trip routes <part-num-ref name="trip routes">108</part-num-ref>
|
| 159 |
+
generated. For example, the route provider <part-num-ref name="route provider">104</part-num-ref>
|
| 160 |
+
may issue a <boundary-data type="header">IBM Docket No. Y<confidence value="5">O</confidence>
|
| 161 |
+
R920040535US1 </boundary-data>
|
| 162 |
+
<boundary-data type="header">
|
| 163 |
+
<confidence value="8">-</confidence>
|
| 164 |
+
<confidence value="8">5</confidence>
|
| 165 |
+
<confidence value="8">-</confidence>
|
| 166 |
+
</boundary-data>
|
| 167 |
+
<page-break num="6"/>
|
| 168 |
+
<boundary-data type="header">Non-Provisional Patent Application</boundary-data>
|
| 169 |
+
<boundary-data type="header">Express Mail No. EV332925751US</boundary-data>
|
| 170 |
+
coupon code <part-num-ref name="coupon code">118</part-num-ref>
|
| 171 |
+
entitling the user <part-num-ref name="user">108</part-num-ref>
|
| 172 |
+
to a price discount at a fueling station <part-num-ref name="fueling station">114</part-num-ref>
|
| 173 |
+
along the trip route <part-num-ref name="trip route">108.</part-num-ref>
|
| 174 |
+
The economic incentives may be valid for a particular time range, thereby further motivating the user <part-num-ref name="user">108</part-num-ref>
|
| 175 |
+
to travel along the trip route during a particular time window. </p>
|
| 176 |
+
<p id="p-24" num="24">
|
| 177 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 178 |
+
Other examples of economic incentives contemplated by the present invention include a reduction in toll fee by municipalities for drivers that travel along trip routes generated by the route provider <part-num-ref name="route provider">104,</part-num-ref>
|
| 179 |
+
and automobile insurance rate discounts by insurance companies for drivers that take historically safer trip routes generated by the route <boundary-data type="line-number">10 </boundary-data>
|
| 180 |
+
provider <part-num-ref name="route provider">104.</part-num-ref>
|
| 181 |
+
</p>
|
| 182 |
+
<p id="p-25" num="25">Governments may want to encourage less gasoline consumption, thus producing less pollution, and the states may provide credit for traveling certain routes. The information regarding accidents, police activity, etc., may be aggregated from different web sites to form an <boundary-data type="line-number">15 </boundary-data>
|
| 183 |
+
accurate "picture" of the surrounding area. Also, since government sites are aware of road construction projects and schedules, the system can guide drivers around troubled areas by getting data from the government sites and even could aggregate some weather information and perhaps guide users past certain attractions or landmarks. Users may <boundary-data type="line-number">20 </boundary-data>
|
| 184 |
+
make requests for the "scenic route" or "fastest possible route." This system may facilitate financial gains to users if the information could get users to meetings on time. </p>
|
| 185 |
+
<p id="p-26" num="26">It is contemplated that the network <part-num-ref name="network">106</part-num-ref>
|
| 186 |
+
may be any network known to those skilled in the art for effectuating communications between the <boundary-data type="line-number">25 </boundary-data>
|
| 187 |
+
various devices within the environment <part-num-ref name="environment">102.</part-num-ref>
|
| 188 |
+
For example, the network <part-num-ref name="network">106</part-num-ref>
|
| 189 |
+
may include wired and wireless communication capabilities. The network may be a pubic network, such as the Internet, or a private network, such as the OnStar(R) satellite network. ONSTAR is a registered trademark of General Motors Corporation, a Delaware company. </p>
|
| 190 |
+
<p id="p-27" num="27">
|
| 191 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 192 |
+
Furthermore, the network <part-num-ref name="network">106</part-num-ref>
|
| 193 |
+
may utilize numerous communication protocols known to those skilled in the art, such as TCP/IP. </p>
|
| 194 |
+
<p id="p-28" num="28">Turning to Fig. 2, exemplary modules forming one embodiment of <boundary-data type="header">IBM Docket No. Y<confidence value="5">O</confidence>
|
| 195 |
+
R920040535US1 </boundary-data>
|
| 196 |
+
<boundary-data type="header">
|
| 197 |
+
<confidence value="8">-</confidence>
|
| 198 |
+
<confidence value="8">6</confidence>
|
| 199 |
+
<confidence value="8">-</confidence>
|
| 200 |
+
</boundary-data>
|
| 201 |
+
<page-break num="7"/>
|
| 202 |
+
<boundary-data type="header">Non-Provisional Patent Application</boundary-data>
|
| 203 |
+
<boundary-data type="header">Express Mail No. EV332925751US</boundary-data>
|
| 204 |
+
the route provider <part-num-ref name="route provider">104</part-num-ref>
|
| 205 |
+
are shown. The modules shown may be implemented in hardware, software or as a combination of both. The implementation is a matter of choice dependent on the performance requirements of the system realizing the invention. </p>
|
| 206 |
+
<p id="p-29" num="29">
|
| 207 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 208 |
+
Central in the route provider arrangement is a routing module <part-num-ref name="routing module">202.</part-num-ref>
|
| 209 |
+
The routing module <part-num-ref name="routing module">202</part-num-ref>
|
| 210 |
+
is configured to generate a trip route based, at least in part, on coordinate information and non-coordinate information. The coordinate information is obtained from a coordinate module <part-num-ref name="coordinate module">204,</part-num-ref>
|
| 211 |
+
while non-coordinate information is received from a non- <boundary-data type="line-number">10 </boundary-data>
|
| 212 |
+
coordinate module <part-num-ref name="non- coordinate module">206.</part-num-ref>
|
| 213 |
+
The routing module <part-num-ref name="routing module">202</part-num-ref>
|
| 214 |
+
may further utilize user profile information to create the trip route. In such a configuration, profile information is received from a profile manager <part-num-ref name="profile manager">208.</part-num-ref>
|
| 215 |
+
</p>
|
| 216 |
+
<p id="p-30" num="30">The coordinate module 204 is configured to receive trip coordinates from the user. These coordinates may be in the form, for <boundary-data type="line-number">15 </boundary-data>
|
| 217 |
+
example, of street addresses, postal zip codes, geographic region, or latitude and longitude coordinates. The coordinate module <part-num-ref name="coordinate module">204</part-num-ref>
|
| 218 |
+
can use a database, conversion service, or other processing technique known to those skilled in the art to translate coordinates received by the user into geocoding. </p>
|
| 219 |
+
<p id="p-31" num="31">
|
| 220 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 221 |
+
The non-coordinate module 206 is configured to receive non- coordinate information from at least one data source. For example, the non-coordinate module <part-num-ref name="non-coordinate module">206</part-num-ref>
|
| 222 |
+
may contact a weather service to retreave weather information. Weather information includes current and predicted weather conditions about the temperature, wind speed, <boundary-data type="line-number">25 </boundary-data>
|
| 223 |
+
humidity, atmospheric pressure, sunset and sunrise times, rain, snow, fog, ice, flooding and the like along a particular strech of the trip route. In addition, the non-coordinate module <part-num-ref name="non-coordinate module">206</part-num-ref>
|
| 224 |
+
may receive statistical information from one or more data sources. Statistical information can include alert levels, toll prices, fuel prices, <boundary-data type="line-number">30 </boundary-data>
|
| 225 |
+
prevailing economic conditions, nature of food stops, road elevation, historical record of traffic conditions, road conditions (i.e., construction), number of traffic lights, number of speeding tickets <boundary-data type="header">IBM Docket No. Y<confidence value="5">O</confidence>
|
| 226 |
+
R920040535US1 </boundary-data>
|
| 227 |
+
<boundary-data type="header">
|
| 228 |
+
<confidence value="8">-</confidence>
|
| 229 |
+
<confidence value="8">7</confidence>
|
| 230 |
+
<confidence value="8">-</confidence>
|
| 231 |
+
</boundary-data>
|
| 232 |
+
<page-break num="8"/>
|
| 233 |
+
<boundary-data type="header">Non-Provisional Patent Application</boundary-data>
|
| 234 |
+
<boundary-data type="header">Express Mail No. EV332925751US</boundary-data>
|
| 235 |
+
issued, historic number of traffic accidents, predicted number of traffic accidents, crime statistics, and the speed limits along the trip route. It is contemplated that statistical information may be received from various governmental, non-profit, and private data <boundary-data type="line-number">5 </boundary-data>
|
| 236 |
+
services. </p>
|
| 237 |
+
<p id="p-32" num="32">Some non-coordinate information maybe user supplied, such as whether a user's vehicle is a commercial vehicle and the height and weight of the user vehicle. This information may be used to rule out trip routes that restrict travel based on the height, weight or <boundary-data type="line-number">10 </boundary-data>
|
| 238 |
+
commercial purpose of vehicles. Furthermore, some non-coordinate information may be generated by the route provider <part-num-ref name="route provider">104</part-num-ref>
|
| 239 |
+
itself. For example, the route provider may keep track of the number of users requesting travel directions for travel during the expected time of travel and holiday dates. </p>
|
| 240 |
+
<p id="p-33" num="33">
|
| 241 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 242 |
+
The profile manager 208 is coupled to a profile database <part-num-ref name="profile database">212</part-num-ref>
|
| 243 |
+
tha<confidence value="8">t</confidence>
|
| 244 |
+
stores user profiles employed by the route provider <part-num-ref name="route provider">104.</part-num-ref>
|
| 245 |
+
In addition<confidence value="4">.</confidence>
|
| 246 |
+
</p>
|
| 247 |
+
<p id="p-34" num="34">to containing information about the user's home location and vehicle type, a user profile includes a preferred routing scheme based on non- coordinate information. The user profile may indicate that an optimal <boundary-data type="line-number">20 </boundary-data>
|
| 248 |
+
trip route should have an estimated travel time no slower than X- percent of the fasted possible trip route, where X is a value selectable by the user. In addition, the user profile may contain a list indicating the order of preference for selecting various routes. </p>
|
| 249 |
+
<p id="p-35" num="35">For example, the user profile may contain the following entry:</p>
|
| 250 |
+
<p id="p-36" num="36">
|
| 251 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 252 |
+
Avoid routes (in order of preference) with: </p>
|
| 253 |
+
<p id="p-37" num="37">1. Historically high accidents 2. Low speed limits 3. Hazardous weather forecasted It should be noted that other embodiments of the present invention may <boundary-data type="line-number">30 </boundary-data>
|
| 254 |
+
store user profiles at the user's computing device rather than at the route provider <part-num-ref name="route provider">104.</part-num-ref>
|
| 255 |
+
</p>
|
| 256 |
+
<boundary-data type="header">IBM Docket No. Y<confidence value="5">O</confidence>
|
| 257 |
+
R920040535US1 </boundary-data>
|
| 258 |
+
<boundary-data type="header">
|
| 259 |
+
<confidence value="58">-8</confidence>
|
| 260 |
+
<confidence value="8">-</confidence>
|
| 261 |
+
</boundary-data>
|
| 262 |
+
<boundary-data type="header">Non-Provisional Patent Application</boundary-data>
|
| 263 |
+
<boundary-data type="header">Express Mail No. EV332925751US</boundary-data>
|
| 264 |
+
<p id="p-38" num="38">
|
| 265 |
+
<page-break num="9"/>
|
| 266 |
+
The routing manager 202 receives data from the coordinate module <part-num-ref name="coordinate module">204,</part-num-ref>
|
| 267 |
+
non-coordinate module <part-num-ref name="coordinate module 204, non-coordinate module">206</part-num-ref>
|
| 268 |
+
and profile module <part-num-ref name="and profile module">208,</part-num-ref>
|
| 269 |
+
and generates one or more trip routes for the user utilizing the combined information. The route coordinator may additionally suggest an optimal <boundary-data type="line-number">5 </boundary-data>
|
| 270 |
+
trip departure time based on transient non-coordinate information such as weather and traffic conditions. Furthermore, the different routes generated may be color-coded such that color codes are configured to indicate the prominence of different non-coordinate information used in generating the different trip routes. Various routing schemes are <boundary-data type="line-number">10 </boundary-data>
|
| 271 |
+
known to those <confidence value="2222222222">skilled'in</confidence>
|
| 272 |
+
the art that can be utilized by the routing manager <part-num-ref name="routing manager">202.</part-num-ref>
|
| 273 |
+
Such routing schemes are outside the scope of the present invention. The trip route may be communicated to the user in various forms, such as a text description, pictorial display, voice message, and multimedia presentation. </p>
|
| 274 |
+
<p id="p-39" num="39">
|
| 275 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 276 |
+
In one embodiment of the invention, the routing module <part-num-ref name="routing module">202</part-num-ref>
|
| 277 |
+
is coupled to an incentive manager <part-num-ref name="incentive manager">210.</part-num-ref>
|
| 278 |
+
The incentive manager <part-num-ref name="incentive manager">210</part-num-ref>
|
| 279 |
+
is configured to offer one or more economic incentives to the users to travel along a trip route. It is contemplated that economic incentives may be, for example, advertisements and/or price discounts for goods or <boundary-data type="line-number">20 </boundary-data>
|
| 280 |
+
service sold along a trip route. Furthermore, the incentive manager <part-num-ref name="incentive manager">210</part-num-ref>
|
| 281 |
+
may collect a commission from merchants featured in the economic incentive. </p>
|
| 282 |
+
<p id="p-40" num="40">In another embodiment of the invention, a third party may pay for all or part of the route provider system. For example, a storeowner <boundary-data type="line-number">25 </boundary-data>
|
| 283 |
+
may wish to pay to have trip directions along his store. A government may pay the route provider <part-num-ref name="route provider">104</part-num-ref>
|
| 284 |
+
to suggest roads that do not produce congestion at a particular time of day or that, for example, avoid parades. A third party, such as a government or storeowner may offer incentives for traversing a particular path. Incentives may include <boundary-data type="line-number">30 </boundary-data>
|
| 285 |
+
discounts, coupons, cash, or services. </p>
|
| 286 |
+
<p id="p-41" num="41">In Fig. 3, a flowchart of system operations performed by one embodiment of the present invention is shown. It should be remarked <boundary-data type="header">IBM Docket No. Y<confidence value="5">O</confidence>
|
| 287 |
+
R920040535US1 </boundary-data>
|
| 288 |
+
<boundary-data type="header">
|
| 289 |
+
<confidence value="58">-9</confidence>
|
| 290 |
+
<confidence value="8">-</confidence>
|
| 291 |
+
</boundary-data>
|
| 292 |
+
<page-break num="10"/>
|
| 293 |
+
<boundary-data type="header">Non-Provisional Patent Application</boundary-data>
|
| 294 |
+
<boundary-data type="header">Express Mail No. EV332925751US</boundary-data>
|
| 295 |
+
that the logical operations shown may be implemented <part-num-ref name="logical operations shown may be implemented">(1)</part-num-ref>
|
| 296 |
+
as a sequence of computer executed steps running on a computing system and/or <part-num-ref name="computing system and/or">(2)</part-num-ref>
|
| 297 |
+
as interconnected machine modules within the computing system. As mentioned above, the implementation is a matter of choice dependent on <boundary-data type="line-number">5 </boundary-data>
|
| 298 |
+
the performance requirements of the system implementing the invention. </p>
|
| 299 |
+
<p id="p-42" num="42">Accordingly, the logical operations making up the embodiments of the present invention described herein are referred to alternatively as operations, steps, or modules.</p>
|
| 300 |
+
<p id="p-43" num="43">Operational flow begins with receiving operation 302. During <boundary-data type="line-number">10 </boundary-data>
|
| 301 |
+
this operation, the route provider receives coordinate information from a user's computing device via a computer network. The coordinate <confidence value="222222222222222">information.may</confidence>
|
| 302 |
+
be, for example, the start and destination locations <confidence value="88">fo</confidence>
|
| 303 |
+
r an upcoming trip. The computing device may reside in a car, in a user's home, in a store, or other public location. The computing <boundary-data type="line-number">15 </boundary-data>
|
| 304 |
+
device may include input means such as a keyboard, touch pad, and/or speech recognition unit through which a user may supply the desired destination for a trip. In some cases, coordinate information may be entered by a third party, such as a secretary for the user or by a software agent that is planning a trip for one or more users. </p>
|
| 305 |
+
<p id="p-44" num="44">
|
| 306 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 307 |
+
Furthermore, the computing device may include output means to convey the trip route to the user, such as a video display, sound system, and/or printer. After receiving operation <part-num-ref name="video display, sound system, and/or printer. After receiving operation">302</part-num-ref>
|
| 308 |
+
is completed, process flow continues to accessing operation <part-num-ref name="is completed, process flow continues to accessing operation">304.</part-num-ref>
|
| 309 |
+
</p>
|
| 310 |
+
<p id="p-45" num="45">At accessing operation 304, the route provider checks the user <boundary-data type="line-number">25 </boundary-data>
|
| 311 |
+
information contained in the user profile. User profiles typically contain driver preferences and information about the driver's vehicle. </p>
|
| 312 |
+
<p id="p-46" num="46">The information in a user profile can also include user requests, such as "give me several scenic routes" or "give me the fastest possible route." The user may also enter such information interactively in <boundary-data type="line-number">30 </boundary-data>
|
| 313 |
+
real-time. After accessing operation <part-num-ref name="user may also enter such information interactively in real-time. After accessing operation">304</part-num-ref>
|
| 314 |
+
is completed, control passes to receiving operation <part-num-ref name="is completed, control passes to receiving operation">306.</part-num-ref>
|
| 315 |
+
</p>
|
| 316 |
+
<p id="p-47" num="47">At receiving operation 306, the route provider receives non- coordinate information from one or more data sources. For example, the <boundary-data type="header">IBM Docket No. Y<confidence value="5">O</confidence>
|
| 317 |
+
R920040535US<confidence value="5">1</confidence>
|
| 318 |
+
</boundary-data>
|
| 319 |
+
<boundary-data type="header">
|
| 320 |
+
<confidence value="6">-</confidence>
|
| 321 |
+
10 - </boundary-data>
|
| 322 |
+
<page-break num="11"/>
|
| 323 |
+
<boundary-data type="header">Non-Provisional Patent Application</boundary-data>
|
| 324 |
+
<boundary-data type="header">Express Mail No. EV332925751U<confidence value="5">S</confidence>
|
| 325 |
+
</boundary-data>
|
| 326 |
+
route provider may receive as input the prevailing and forecasted weather conditions for travel dates specified by a user. Such information is available over a network from various weather tracking agencies. This non-coordinate information can be helpful to a user <boundary-data type="line-number">5 </boundary-data>
|
| 327 |
+
wishing to avoid routes with predicted snow. </p>
|
| 328 |
+
<p id="p-48" num="48">For a user wishing to minimize the cost of travel, the route provider may check for gas prices along a particular route. The route provider may further check prevailing economic conditions (stock markets, taxes, tax deductions, etc.). For example, sales taxes in <boundary-data type="line-number">10 </boundary-data>
|
| 329 |
+
different states may differ and affect the driving routes preferred by users. The route provider may further check tolls and find a route that minimizes toll charges. </p>
|
| 330 |
+
<p id="p-49" num="49">For users wishing to avoid traffic, the route provider may check the number of people requesting map directions between two locations at <boundary-data type="line-number">15 </boundary-data>
|
| 331 |
+
a particular time. For example, if thousands of people are listing Disney World as a destination on a particular date through a certain set of roads, the route provider may suggest alternate routes to stay clear of traffic. The route provider may check the time of day for the route and suggest alternative routes so that a user can avoid traffic. </p>
|
| 332 |
+
<p id="p-50" num="50">
|
| 333 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 334 |
+
The route provider may check the holiday dates for the route and suggest an alternative route so that a user can avoid holiday traffic congestion and for other purposes. The route provider may check the historical record of traffic problems in order to suggest routes that minimize this traffic. </p>
|
| 335 |
+
<p id="p-51" num="51">
|
| 336 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 337 |
+
Some users may employ the route provider to find the fastest route to a particular destination. For this objective, the route provider may check the number of traffic lights and duration of traffic light red signals along certain routes in order to suggest routes that avoid delays. Other relevant non-coordinate information includes the <boundary-data type="line-number">30 </boundary-data>
|
| 338 |
+
speed limits along the various roads used along a preferred trip route. </p>
|
| 339 |
+
<p id="p-52" num="52">For those users concerned with safety, the route provider may request non-coordinate information such as the historical record of <boundary-data type="header">IBM Docket No. Y<confidence value="5">O</confidence>
|
| 340 |
+
R920040535U<confidence value="68">S1</confidence>
|
| 341 |
+
</boundary-data>
|
| 342 |
+
<boundary-data type="header">- 11 -</boundary-data>
|
| 343 |
+
<page-break num="12"/>
|
| 344 |
+
<boundary-data type="header">Non-Provisional Patent Application</boundary-data>
|
| 345 |
+
<boundary-data type="header">Express Mail No. EV332925751US</boundary-data>
|
| 346 |
+
accidents along certain routes in order to suggest routes that avoid accidents. The route provider may check a terrorist alert level for drivers that may want to avoid certain locations that could be terrorist targets. </p>
|
| 347 |
+
<p id="p-53" num="53">
|
| 348 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 349 |
+
The route provider may check the nature of food stops along the way, and this information may interact with time of day information in order to supply the driver with preferred driving directions. The route provider may check the elevation of roads, which may be useful for drivers or passengers who have medical conditions sensitive to <boundary-data type="line-number">10 </boundary-data>
|
| 350 |
+
elevation. The route provider may check the number of police tickets predicted to be given based on historical records along certain routes in order to suggest routes that avoid tickets. The route provider may check crime statistics associated with locations along suggested routes so that drivers may avoid high crime areas. The route provider may <boundary-data type="line-number">15 </boundary-data>
|
| 351 |
+
check aspects of the scenery along routes so that drivers may obtain a scenic route. </p>
|
| 352 |
+
<p id="p-54" num="54">After receiving operation 306 is completed, control passes to generating operation <part-num-ref name="is completed, control passes to generating operation">308,</part-num-ref>
|
| 353 |
+
where the route provider supplies one or more trip routes to the user based on information gained in operations <part-num-ref name="user based on information gained in operations">302,</part-num-ref>
|
| 354 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 355 |
+
<part-num-ref name="user based on information gained in operations 302,">304</part-num-ref>
|
| 356 |
+
and <part-num-ref name="and">306.</part-num-ref>
|
| 357 |
+
In addition, the generating operation <part-num-ref name="generating operation">308</part-num-ref>
|
| 358 |
+
may advise the traveler of an optimal date and time to travel one or more of the generated routes. For example, if the route provider determines that delays are likely on a certain date and time or with predicted weather conditions, the route provider will advise the user of an alternative <boundary-data type="line-number">25 </boundary-data>
|
| 359 |
+
date and time. It is contemplated that the driving directions and various characteristics of the driving routes and criteria may be visually indicated by color on a map. After generating operation <part-num-ref name="map. After generating operation">308</part-num-ref>
|
| 360 |
+
is completed, control optionally passes to issuing operation <part-num-ref name="is completed, control optionally passes to issuing operation">310.</part-num-ref>
|
| 361 |
+
</p>
|
| 362 |
+
<p id="p-55" num="55">At issuing operation 310, the route provider issues to the user <boundary-data type="line-number">30 </boundary-data>
|
| 363 |
+
at least one economic incentive to travel along the trip route. A third party, such as a government agency or store owner may offer rewards for traversing particular travel paths, such as paths with low <boundary-data type="header">IBM Docket No. Y<confidence value="5">O</confidence>
|
| 364 |
+
R920040535US1 </boundary-data>
|
| 365 |
+
<boundary-data type="header">
|
| 366 |
+
<confidence value="6">-</confidence>
|
| 367 |
+
12 - </boundary-data>
|
| 368 |
+
<page-break num="13"/>
|
| 369 |
+
<boundary-data type="header">Non-Provisional Patent Application</boundary-data>
|
| 370 |
+
<boundary-data type="header">Express Mail No. EV332925751US</boundary-data>
|
| 371 |
+
traffic, low accident rates, or paths that pass certain stores and malls. Rewards may include discounts, coupons, cash, or services. </p>
|
| 372 |
+
<p id="p-56" num="56">Insurance companies, governments, or parents of a young driver may prefer users to take different routes for a variety of reasons <boundary-data type="line-number">5 </boundary-data>
|
| 373 |
+
including safety reasons. Stores may want drivers to pass their shops in hopes of attracting more customers. Governments and local communities may wish to shape traffic patterns to avoid congestion or pollution. The route provider may assist such plans by providing directions and including incentives to use such directions. A driver's <boundary-data type="line-number">10 </boundary-data>
|
| 374 |
+
compliance with a particular traversal can be monitored using, for example, coupons redeemable at specific locations, global positioning services, through tolls, easy pass, and other indicators. After issuing operation <part-num-ref name="particular traversal can be monitored using, for example, coupons redeemable at specific locations, global positioning services, through tolls, easy pass, and other indicators. After issuing operation">310</part-num-ref>
|
| 375 |
+
is completed, the process ends. </p>
|
| 376 |
+
<p id="p-57" num="57">Fig. 4 shows a table <part-num-ref name="table">402</part-num-ref>
|
| 377 |
+
representing an exemplary data file used <boundary-data type="line-number">15 </boundary-data>
|
| 378 |
+
by the route provider to generate trip routes. The data file is preferably stored at the route provider, however it is contemplated that some information may be stored at the user's computing device. </p>
|
| 379 |
+
<p id="p-58" num="58">Each row 404 in the table <part-num-ref name="table">402</part-num-ref>
|
| 380 |
+
represents a user record. Furthermore, each user record includes user ID <part-num-ref name="user record. Furthermore, each user record includes user ID">406,</part-num-ref>
|
| 381 |
+
vehicle information <part-num-ref name="user record. Furthermore, each user record includes user ID 406, vehicle information">408,</part-num-ref>
|
| 382 |
+
and <boundary-data type="line-number">20 </boundary-data>
|
| 383 |
+
driver preferences <part-num-ref name="user record. Furthermore, each user record includes user ID 406, vehicle information 408, and driver preferences">410</part-num-ref>
|
| 384 |
+
fields. </p>
|
| 385 |
+
<p id="p-59" num="59">The user ID 406 may be a unique alphanumeric string identifying the user and can act as a key for the data file. Typically, the user transmits an identifier to the route provider, such as a login name, which the route provider tries to match with a user ID <part-num-ref name="user ID">406</part-num-ref>
|
| 386 |
+
in the data <boundary-data type="line-number">25 </boundary-data>
|
| 387 |
+
file. This saves the user from having to resubmit the same information over and over again to the route provider. </p>
|
| 388 |
+
<p id="p-60" num="60">The vehicle information 408 may include information related to the nature of user's car. For example, the vehicle information may indicate characteristics such as all-wheel drive, snow tire equipped, <boundary-data type="line-number">30 </boundary-data>
|
| 389 |
+
and weight and height. This information is useful because vehicle characteristics may affect the route preference of the driver. For example, a user without snow tires may wish to avoid snowy roads. </p>
|
| 390 |
+
<boundary-data type="header">IBM Docket No. Y<confidence value="5">O</confidence>
|
| 391 |
+
R920040535US1 </boundary-data>
|
| 392 |
+
<boundary-data type="header">- 13 -</boundary-data>
|
| 393 |
+
<boundary-data type="header">Non-Provisional Patent Application</boundary-data>
|
| 394 |
+
<boundary-data type="header">Express Mail No. EV332925751US</boundary-data>
|
| 395 |
+
<p id="p-61" num="61">
|
| 396 |
+
<page-break num="14"/>
|
| 397 |
+
Driver preferences 410 include various characteristics in trip routes that the user has predilections for. A user may indicate, for example, a preference for scenic routes, fastest possible routes, cheapest routes, routes with food and/or rest stops every thirty miles, <boundary-data type="line-number">5 </boundary-data>
|
| 398 |
+
and other preferences relevant to the routing module. </p>
|
| 399 |
+
<p id="p-62" num="62">It is contemplated that the system can determine and display one or more suggested driving routes based on a variety of criteria mentioned and in numerous ways. For example, a user may enter a starting point S and destination point D on a map. The system may <boundary-data type="line-number">10 </boundary-data>
|
| 400 |
+
determine that there are several different viable routes between points S and D using known methods for route determination. Next, the system assesses the relative favorableness of the possible routes based on various non-coordinate information, such as weather and traffic forecasts. In particular, the system may assign attributes A for each <boundary-data type="line-number">15 </boundary-data>
|
| 401 |
+
road segment along the route as a function of time. The system may also assign a weight W at a given time t, so that for each road segment along the route, the system evaluates a function such as, f(t) = A<confidence value="4">1</confidence>
|
| 402 |
+
(t)*W1(t) + A2(t)*W2(t) + . . . A<confidence value="6688681">n(t)*W.</confidence>
|
| 403 |
+
(t) In order to give the potential traveler a relative indication of <boundary-data type="line-number">20 </boundary-data>
|
| 404 |
+
route favorableness according to time of day, the system evaluates this function for a range of time values t, starting at a given time to and progressing through end time t<confidence value="18">o,</confidence>
|
| 405 |
+
incremented by some arbitrary amount of time, such as <part-num-ref name="given time to and progressing through end time to, incremented by some arbitrary amount of time, such as">15</part-num-ref>
|
| 406 |
+
minutes. Attribute data may be uploaded from various data sources such as real-time weather and traffic databases. </p>
|
| 407 |
+
<p id="p-63" num="63">
|
| 408 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 409 |
+
Naturally, not all attributes will be available for every road segment, and missing attributes need not contribute to f(t). </p>
|
| 410 |
+
<p id="p-64" num="64">A higher value for W indicates a greater importance of a particular attribute in determining the favorableness of a route. For example, if a driver has snow tires (e.g., as indicated in the vehicle <boundary-data type="line-number">30 </boundary-data>
|
| 411 |
+
information 408), W may decrease relative to a driver who does not have snow tires. Truckers and motorcycles may have different needs. People of different ages and driving skills may likewise have different needs. </p>
|
| 412 |
+
<boundary-data type="header">IBM Docket No. Y<confidence value="5">O</confidence>
|
| 413 |
+
R920040535US<confidence value="4">1</confidence>
|
| 414 |
+
</boundary-data>
|
| 415 |
+
<boundary-data type="header">- 14 -</boundary-data>
|
| 416 |
+
<boundary-data type="header">Non-Provisional Patent Application</boundary-data>
|
| 417 |
+
<boundary-data type="header">Express Mail No. EV332925751US</boundary-data>
|
| 418 |
+
<p id="p-65" num="65">
|
| 419 |
+
<page-break num="15"/>
|
| 420 |
+
Weights may be assigned and controlled by the user, route-provider, and/or third parties such as an insurance company. </p>
|
| 421 |
+
<p id="p-66" num="66">The generated values for f(t) for each route from start to destination may be examined and sorted using known methods for finding <boundary-data type="line-number">5 </boundary-data>
|
| 422 |
+
the maximum and minimum values, and these values can be compared, ranked, and visualized. Once f(t) is computed for several possible paths, the system may display maps that are labeled for different times of the day, using, for example, color to indicate the favorableness of the routes. For instance, the favorableness of routes may be indicated <boundary-data type="line-number">10 </boundary-data>
|
| 423 |
+
by a gradient color scale that ranges from green to red, with green being best, red worst. A route may be green at one time of the day but shift towards red at another time as a result of weather and traffic forecasts, since the user may see maps at different times <confidence value="222222">of'day</confidence>
|
| 424 |
+
. </p>
|
| 425 |
+
<p id="p-67" num="67">The foregoing description of the invention has been presented for <boundary-data type="line-number">15 </boundary-data>
|
| 426 |
+
purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed, and other modifications and variations may be possible in light of the above teachings. For example, the route provider may be embodied in various tangible media know in the art, including, but not limited to, <boundary-data type="line-number">20 </boundary-data>
|
| 427 |
+
read only memory, random access memory, data streams, optical and magnetic memory, and the like. The embodiments disclosed were chosen and described 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 various <boundary-data type="line-number">25 </boundary-data>
|
| 428 |
+
modifications as are suited to the particular use contemplated. It is intended that the appended claims be construed to include other alternative embodiments of the invention except insofar as limited by the prior art. </p>
|
| 429 |
+
<boundary-data type="header">IBM Docket No. Y<confidence value="5">O</confidence>
|
| 430 |
+
R920040535US1 </boundary-data>
|
| 431 |
+
<boundary-data type="header">
|
| 432 |
+
<confidence value="6">-</confidence>
|
| 433 |
+
15 - </boundary-data>
|
| 434 |
+
</description>
|
| 435 |
+
</us-patent-application>
|
| 436 |
+
|
prior_art/11012471.xml
ADDED
|
@@ -0,0 +1,682 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11012471</doc-number>
|
| 8 |
+
<date>2004-12-15</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">EV5<confidence value="66868688">54747024</confidence>
|
| 15 |
+
</p>
|
| 16 |
+
<heading id="h-2">IN THE UNITED STATES PATENT AND TRADEMARK OFFICE</heading>
|
| 17 |
+
<heading id="h-3">APPLICATION FOR LETTERS PATENT</heading>
|
| 18 |
+
<p id="p-2" num="2">Searching Elect<confidence value="885">ron</confidence>
|
| 19 |
+
ic Program Guide <confidence value="6688">Data</confidence>
|
| 20 |
+
Inventors: </p>
|
| 21 |
+
<p id="p-3" num="3">Dana S. Rao Daniel Danker David H. Sloo George K. Nyako ATTORNEY'S DOCKET NO. MS1-2257US <confidence value="661">ee~</confidence>
|
| 22 |
+
Oc#: ms<confidence value="4">1</confidence>
|
| 23 |
+
-2257us/Ms#: 306556.01 <page-break num="2"/>
|
| 24 |
+
</p>
|
| 25 |
+
<heading id="h-4">SEARCHING ELECTRONIC PROGRAM GUIDE DATA</heading>
|
| 26 |
+
<heading id="h-5">TECHNICAL FIELD</heading>
|
| 27 |
+
<p id="p-4" num="4">
|
| 28 |
+
<confidence value="566652">100011</confidence>
|
| 29 |
+
The present invention generally relates to the field of content navigation and more particularly relates to searching electronic program guide data. </p>
|
| 30 |
+
<heading id="h-6">BACKGROUND</heading>
|
| 31 |
+
<p id="p-5" num="5">10002<confidence value="5">1</confidence>
|
| 32 |
+
Users have access to an ever increasing variety of content that may be output in a wide variety of ways. For example, a user may view traditional television programming received over a network by using a client, such as a set- top box. The user may also view pay-per-view movies, order video-on-demand (VOD) content, interact with a video game, play music, and so on. The user may also access content locally on the client, such as from a digital video disc (DVD), broadcast content stored on a hard disk drive for viewing in the future (e.g., a digital video recorder), and so on. </p>
|
| 33 |
+
<p id="p-6" num="6">[0003<confidence value="5">1</confidence>
|
| 34 |
+
To navigate through this even increasing variety of content, the user may interact wit<confidence value="8">h</confidence>
|
| 35 |
+
user interface which displays representations of the content, such as an electronic program guide (EPG). For example, the EPG may enable the user to observe a listing of television programs that are currently being streamed, as well as a listing of television programs that will be streamed in the future. </p>
|
| 36 |
+
<p id="p-7" num="7">Additionally, the EPG may allow the user to navigate to a television program from <boundary-data type="header">
|
| 37 |
+
<confidence value="8">2</confidence>
|
| 38 |
+
<confidence value="666">Oc#</confidence>
|
| 39 |
+
: ms<confidence value="4">1</confidence>
|
| 40 |
+
-2257us/Ms#: 306556.01 </boundary-data>
|
| 41 |
+
<confidence value="17711">Iee0-</confidence>
|
| 42 |
+
hay<confidence value="77">es</confidence>
|
| 43 |
+
<page-break num="3"/>
|
| 44 |
+
the EPG itself. For instance, the user may select a representation of a television program to cause the client to tune to that television program. </p>
|
| 45 |
+
<p id="p-8" num="8">10004<confidence value="5">1</confidence>
|
| 46 |
+
Traditionally, an EPG is configured to locate particular content items of interest, such as a particular television program. However, content may also be known by the name of the provider instead of by the name of the content itself<confidence value="5">.</confidence>
|
| 47 |
+
</p>
|
| 48 |
+
<p id="p-9" num="9">For instance, a user may want to watch the "Weather Channel" and not know the name of any particular content item that is available via the Weather Channel. A traditional EPG, however, does not address the channels themselves and rather is focused on the content items that are available via the channels.</p>
|
| 49 |
+
<p id="p-10" num="10">
|
| 50 |
+
<confidence value="5">[</confidence>
|
| 51 |
+
0005<confidence value="4">]</confidence>
|
| 52 |
+
Therefore, there is a continuing need for searching of electronic program guide (EPG) data that addresses channels and channel characteristics. </p>
|
| 53 |
+
<heading id="h-7">SUMMARY</heading>
|
| 54 |
+
<p id="p-11" num="11">
|
| 55 |
+
<confidence value="5">[</confidence>
|
| 56 |
+
0006<confidence value="5">]</confidence>
|
| 57 |
+
Searching EPG data is described. In an implementation, EPG data includes content metadata that describes characteristics of a respective one of a plurality of content items, such as content title, actors, genre, and so on. EPG data also includes channel metadata that describes characteristics respective channels, such as call sign, channel name, and so on. A search may be performed on both the content and channel metadata to locate content items and channels, respectively, which correspond to a search request. Thus, in this example, a single search may be performed to locate both channels and content items. In another <boundary-data type="header">3 Oc<confidence value="5">#</confidence>
|
| 58 |
+
: ms<confidence value="4">1</confidence>
|
| 59 |
+
-2257us<confidence value="5">/</confidence>
|
| 60 |
+
Ms#: 306556.01 </boundary-data>
|
| 61 |
+
<confidence value="22222222">leeehays</confidence>
|
| 62 |
+
<page-break num="4"/>
|
| 63 |
+
example, the search may be performed to locate a particular channel without also searching for corresponding content items. </p>
|
| 64 |
+
<heading id="h-8">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 65 |
+
<p id="p-12" num="12">
|
| 66 |
+
<confidence value="5">[</confidence>
|
| 67 |
+
0007<confidence value="5">1</confidence>
|
| 68 |
+
FIG. 1 is an illustration of an environment in an exemplary implementation that includes a content provider that is communicatively coupled to a client over a network. </p>
|
| 69 |
+
<p id="p-13" num="13">
|
| 70 |
+
<confidence value="5">[</confidence>
|
| 71 |
+
0008<confidence value="5">]</confidence>
|
| 72 |
+
FIG. 2 is an illustration of an exemplary implementation of a system showing a distribution server and the client of FIG. 1 in greater detail. </p>
|
| 73 |
+
<p id="p-14" num="14">
|
| 74 |
+
<confidence value="5555">[000</confidence>
|
| 75 |
+
9] FIG. 3 is a flow diagram depicting a procedure in an exemplary implementation in which both content metadata and channel metadata, which collectively provide EPG data, are searched in response to a search request received from a user through interaction with an EPG. </p>
|
| 76 |
+
<p id="p-15" num="15">
|
| 77 |
+
<confidence value="255652">[00101</confidence>
|
| 78 |
+
FIG. 4 is an illustration of an exemplary implementation in which the client of FIG. 3 outputs the EPG, which includes a search window configured for interaction by a user to form the search request. </p>
|
| 79 |
+
<p id="p-16" num="16">
|
| 80 |
+
<confidence value="255662">[00111</confidence>
|
| 81 |
+
FIG. 5 is a flow diagram depicting a procedure in another exemplary implementation in which a search request and a search result are formed through interaction by a user with an EPG. </p>
|
| 82 |
+
<p id="p-17" num="17">
|
| 83 |
+
<confidence value="4">1</confidence>
|
| 84 |
+
0012<confidence value="4">]</confidence>
|
| 85 |
+
FIG. 6 is a flow diagram depicting a procedure in an exemplary implementation in which a result of a search of EPG data includes channels having a common owner. </p>
|
| 86 |
+
<boundary-data type="header">4 Oc<confidence value="5">#</confidence>
|
| 87 |
+
: ms<confidence value="4">1</confidence>
|
| 88 |
+
-2257us<confidence value="5">/</confidence>
|
| 89 |
+
Ms#: 306556.01 </boundary-data>
|
| 90 |
+
<p id="p-18" num="18">
|
| 91 |
+
<confidence value="1771177116">lee0-hayes</confidence>
|
| 92 |
+
<page-break num="5"/>
|
| 93 |
+
<confidence value="5">1</confidence>
|
| 94 |
+
0013<confidence value="4">1</confidence>
|
| 95 |
+
The same reference numbers are utilized in instances in the discussion to reference like structures and components. </p>
|
| 96 |
+
<heading id="h-9">DETAILED DESCRIPTION</heading>
|
| 97 |
+
<p id="p-19" num="19">
|
| 98 |
+
<confidence value="5">1</confidence>
|
| 99 |
+
00141 Overview Searching electronic program guide (EPG) data is described. In an implementation, functionality is provided to search for channels as well as content items that are available via the channels. For example, a user may enter a search request having the alphabetic characters "STA". EPG data may be configured to include content metadata that describes characteristics of content items (e.g., title, detailed description, and so on) and channel metadata that describes characteristics of channels (e.g., call sign, channel name, and so on). Both the content metadata and the channel metadata are searched in response to the request. For instance, the search "STA" may locate a "Star Gazing" channel and a television program titled "Stars of Hollywood". In this way, the user is provided with a single, integrated search of the EPG data that addresses both channels and content items. Further discussion of EPG data searching may be found beginning in relation to FIG. 1. </p>
|
| 100 |
+
<p id="p-20" num="20">
|
| 101 |
+
<confidence value="5">1</confidence>
|
| 102 |
+
00151 The search request may be entered in a variety of ways. For example, an EPG may be provided which includes representations of a plurality of content items (e.g., television programs) and a search window. The user may utilize an input device (e.g., a remote control) to enter text into the search window to search the EPG data. In another example, the user may highlight a channel identifier in <boundary-data type="header">5 Oc#: ms<confidence value="4">1</confidence>
|
| 103 |
+
-22<confidence value="5">5</confidence>
|
| 104 |
+
7us<confidence value="5">/</confidence>
|
| 105 |
+
Ms#: 306556.01 </boundary-data>
|
| 106 |
+
<confidence value="288">fee</confidence>
|
| 107 |
+
<confidence value="222222">ghayes</confidence>
|
| 108 |
+
<page-break num="6"/>
|
| 109 |
+
the EPG and then enter text via the input device. As the user enters the text, the EPG may be configured to automatically scroll to the channel that matches the entered text. Further discussion of entering a search request may be found in relation to FIGS. 4 and <part-num-ref name="and">5.</part-num-ref>
|
| 110 |
+
</p>
|
| 111 |
+
<p id="p-21" num="21">
|
| 112 |
+
<confidence value="5">[</confidence>
|
| 113 |
+
0016 Exem<confidence value="5">p</confidence>
|
| 114 |
+
lary Environment FIG. 1 is an illustration of an environment <part-num-ref name="environment">100</part-num-ref>
|
| 115 |
+
in an exemplary implementation that includes a content provider <part-num-ref name="content provider">102</part-num-ref>
|
| 116 |
+
that is communicatively coupled to a client <part-num-ref name="client">104</part-num-ref>
|
| 117 |
+
over a network <part-num-ref name="network">106.</part-num-ref>
|
| 118 |
+
The client <part-num-ref name="client">104</part-num-ref>
|
| 119 |
+
may be configured in a variety of ways. For example, the client <part-num-ref name="client">104</part-num-ref>
|
| 120 |
+
may be configured as a computing device that is capable of communicating over the network <part-num-ref name="network">106,</part-num-ref>
|
| 121 |
+
such as a desktop computer, a mobile station, an entertainment appliance, a set-top box <part-num-ref name="set-top box">108</part-num-ref>
|
| 122 |
+
communicatively coupled to a display device <part-num-ref name="display device">110</part-num-ref>
|
| 123 |
+
as illustrated, a wireless phone, and so forth. The client <part-num-ref name="client">104</part-num-ref>
|
| 124 |
+
may range from a full resource device with substantial memory and processor resources (e.g., television enabled personal computers, television recorders equipped with hard disk) to a low-resource device with limited memory and/or processing resources (e.g., traditional set-top boxes). </p>
|
| 125 |
+
<p id="p-22" num="22">The client 104 may also relate to a person and/or entity that operates the client. In other words, client <part-num-ref name="client. In other words, client">104</part-num-ref>
|
| 126 |
+
may describe a logical client that includes a user and/or a machine. Although one client <part-num-ref name="machine. Although one client">104</part-num-ref>
|
| 127 |
+
is illustrated, a plurality of clients may be communicatively coupled to the network <part-num-ref name="network">106.</part-num-ref>
|
| 128 |
+
Likewise, although one content provider <part-num-ref name="network 106. Likewise, although one content provider">102</part-num-ref>
|
| 129 |
+
is illustrated, a plurality of content providers may also be included in the environment <part-num-ref name="environment">100.</part-num-ref>
|
| 130 |
+
The network <part-num-ref name="network">106</part-num-ref>
|
| 131 |
+
is illustrated as the Internet, and may <boundary-data type="header">6 Oc#: ms<confidence value="4">1</confidence>
|
| 132 |
+
-2257us/Ms#: 306556.01 </boundary-data>
|
| 133 |
+
<confidence value="17711">lee0-</confidence>
|
| 134 |
+
hay<confidence value="116">e2s</confidence>
|
| 135 |
+
<page-break num="7"/>
|
| 136 |
+
include a variety of other networks, such as an intranet, a wired or wireless telephone network, a broadcast network which may include a backchannel to provide two-way communication, and so forth. </p>
|
| 137 |
+
<p id="p-23" num="23">
|
| 138 |
+
<confidence value="5">[</confidence>
|
| 139 |
+
0017<confidence value="5">1</confidence>
|
| 140 |
+
The content provider <part-num-ref name="content provider">102</part-num-ref>
|
| 141 |
+
includes a plurality of content 112<confidence value="66">(j</confidence>
|
| 142 |
+
), where "j" can be any integer from <part-num-ref name="plurality of content 112(j), where "j" can be any integer from">1</part-num-ref>
|
| 143 |
+
to "J". The content 112<confidence value="52">(j</confidence>
|
| 144 |
+
) may include a variety of data, such as streaming content (e.g., television programming and pay-per-view movies), one or more results of remote application processing, and so on. The content 112<confidence value="66">(j</confidence>
|
| 145 |
+
) is communicated over a network <part-num-ref name="network">114</part-num-ref>
|
| 146 |
+
to a head end <part-num-ref name="head end">116.</part-num-ref>
|
| 147 |
+
The network <part-num-ref name="network">114</part-num-ref>
|
| 148 |
+
may be the same as or different from network <part-num-ref name="same as or different from network">106.</part-num-ref>
|
| 149 |
+
For example, the network <part-num-ref name="network">114</part-num-ref>
|
| 150 |
+
may be configured as a private subnet while the network <part-num-ref name="network">106</part-num-ref>
|
| 151 |
+
is configured as the Internet. </p>
|
| 152 |
+
<p id="p-24" num="24">
|
| 153 |
+
<confidence value="5">[</confidence>
|
| 154 |
+
0018<confidence value="5">1</confidence>
|
| 155 |
+
Content 112<confidence value="66">(j</confidence>
|
| 156 |
+
) communicated from the content provider <part-num-ref name="content provider">102</part-num-ref>
|
| 157 |
+
over the network <part-num-ref name="network">114</part-num-ref>
|
| 158 |
+
is received by the head end <part-num-ref name="head end">116</part-num-ref>
|
| 159 |
+
and stored in a content database <part-num-ref name="content database">118</part-num-ref>
|
| 160 |
+
as content 120(k), where "k" can be any integer from "1" to "K". The content 120(k) may be the same as or different from the content 112<confidence value="52">(j</confidence>
|
| 161 |
+
) received from the content provider <part-num-ref name="content provider">102.</part-num-ref>
|
| 162 |
+
The content 120(k), for instance, may include additional data for streaming to the client <part-num-ref name="client">104,</part-num-ref>
|
| 163 |
+
may be compressed using one or more data compression techniques by the head end <part-num-ref name="head end">116,</part-num-ref>
|
| 164 |
+
may be encrypted, and so forth. </p>
|
| 165 |
+
<p id="p-25" num="25">
|
| 166 |
+
<confidence value="5">[</confidence>
|
| 167 |
+
0019<confidence value="5">]</confidence>
|
| 168 |
+
The client <part-num-ref name="client">104</part-num-ref>
|
| 169 |
+
may be configured in a variety of ways to receive the content 120(k) over the network <part-num-ref name="network">106.</part-num-ref>
|
| 170 |
+
As illustrated, the client <part-num-ref name="client">104</part-num-ref>
|
| 171 |
+
may be configured as a set-top box <part-num-ref name="set-top box">108</part-num-ref>
|
| 172 |
+
that is communicatively coupled to a display device <part-num-ref name="display device">110.</part-num-ref>
|
| 173 |
+
The client <part-num-ref name="client">104</part-num-ref>
|
| 174 |
+
includes hardware and software to transport and <boundary-data type="header">7 Oc#: ms<confidence value="4">1</confidence>
|
| 175 |
+
-2257us/Ms#: 306556.01 </boundary-data>
|
| 176 |
+
<confidence value="2222222">eehayes</confidence>
|
| 177 |
+
<page-break num="8"/>
|
| 178 |
+
decrypt content 120(k) received from the head end <part-num-ref name="head end">116</part-num-ref>
|
| 179 |
+
for rendering by the display device <part-num-ref name="display device">110.</part-num-ref>
|
| 180 |
+
Although a display device <part-num-ref name="display device">110</part-num-ref>
|
| 181 |
+
is shown, a variety of other output devices are also contemplated, such as speakers. </p>
|
| 182 |
+
<p id="p-26" num="26">[0020<confidence value="5">1</confidence>
|
| 183 |
+
The client <part-num-ref name="client">104</part-num-ref>
|
| 184 |
+
may also include digital video recorder (DVR) functionality. </p>
|
| 185 |
+
<p id="p-27" num="27">For instance, the client <part-num-ref name="client">104</part-num-ref>
|
| 186 |
+
may include a database <part-num-ref name="database">122</part-num-ref>
|
| 187 |
+
to record the content 120(k) received from the network <part-num-ref name="network">106.</part-num-ref>
|
| 188 |
+
The database <part-num-ref name="database">122</part-num-ref>
|
| 189 |
+
may be implemented in a variety of ways, such as a hard disk drive, a removable computer-readable medium (e.g., a writable digital video disc), and so on. Content 124(o), where "o" can be any number from one to "<confidence value="4">O</confidence>
|
| 190 |
+
", that is stored in the database <part-num-ref name="database">122</part-num-ref>
|
| 191 |
+
of the client <part-num-ref name="client">104</part-num-ref>
|
| 192 |
+
may be copies of the content 120(k) that was streamed from the head end <part-num-ref name="head end">116.</part-num-ref>
|
| 193 |
+
</p>
|
| 194 |
+
<p id="p-28" num="28">Additionally, content 124(<confidence value="5">o</confidence>
|
| 195 |
+
) may represent content obtained from a variety of other sources, such as from a computer-readable medium (e.g., a digital video disc) that is accessible by the client <part-num-ref name="client">104.</part-num-ref>
|
| 196 |
+
</p>
|
| 197 |
+
<p id="p-29" num="29">
|
| 198 |
+
<confidence value="5">[</confidence>
|
| 199 |
+
002<confidence value="52">11</confidence>
|
| 200 |
+
The client <part-num-ref name="client">104</part-num-ref>
|
| 201 |
+
includes a navigation module <part-num-ref name="navigation module">126</part-num-ref>
|
| 202 |
+
that is executable on the client <part-num-ref name="client">104</part-num-ref>
|
| 203 |
+
to control content playback on the client <part-num-ref name="client">104,</part-num-ref>
|
| 204 |
+
such as through the use of one or more "trick modes". The trick modes may provide non-linear playback of the content 124(o) (i.e., time shift the playback of the content 124(o)) such as pause, rewind, fast forward, slow motion playback, and the like. For example, during a pause, the client <part-num-ref name="client">104</part-num-ref>
|
| 205 |
+
may continue to record the content 120(k) in the database <part-num-ref name="database">122</part-num-ref>
|
| 206 |
+
as content 124(o). The client <part-num-ref name="client">104,</part-num-ref>
|
| 207 |
+
through execution of the navigation module <part-num-ref name="navigation module">126,</part-num-ref>
|
| 208 |
+
may then playback the content 124(o) from the database <part-num-ref name="database">122,</part-num-ref>
|
| 209 |
+
starting at the point in time the content 124(o) was paused, while continuing <boundary-data type="header">
|
| 210 |
+
<confidence value="8">8</confidence>
|
| 211 |
+
<confidence value="666">Oc#</confidence>
|
| 212 |
+
: ms<confidence value="4">1</confidence>
|
| 213 |
+
-2257us/Ms#: 306556.01 </boundary-data>
|
| 214 |
+
<confidence value="1771188127">Iee0-haves</confidence>
|
| 215 |
+
<page-break num="9"/>
|
| 216 |
+
to record the currently-broadcast content 120(k) in the database <part-num-ref name="database">122</part-num-ref>
|
| 217 |
+
from the head end <part-num-ref name="head end">116.</part-num-ref>
|
| 218 |
+
</p>
|
| 219 |
+
<p id="p-30" num="30">10022<confidence value="5">1</confidence>
|
| 220 |
+
When playback of the content 124(o) is requested, the navigation module <part-num-ref name="navigation module">126</part-num-ref>
|
| 221 |
+
may be executed on the client <part-num-ref name="client">104</part-num-ref>
|
| 222 |
+
to retrieve the content 124(o). The navigation module <part-num-ref name="navigation module">126</part-num-ref>
|
| 223 |
+
may also restore the content 124(o) to the original encoded format as received from the content provider <part-num-ref name="content provider">102.</part-num-ref>
|
| 224 |
+
For example, when the content 120(k) is recorded in the database <part-num-ref name="database">122</part-num-ref>
|
| 225 |
+
to form content 124(o), the content 120(k) may be compressed. Therefore, when the navigation module <part-num-ref name="navigation module">126</part-num-ref>
|
| 226 |
+
retrieves the content 124(<confidence value="5">o</confidence>
|
| 227 |
+
), the content 124(o) is decompressed for rendering by the display device <part-num-ref name="display device">110.</part-num-ref>
|
| 228 |
+
</p>
|
| 229 |
+
<p id="p-31" num="31">
|
| 230 |
+
<confidence value="5">[</confidence>
|
| 231 |
+
0023<confidence value="5">1</confidence>
|
| 232 |
+
The navigation module <part-num-ref name="navigation module">126</part-num-ref>
|
| 233 |
+
may also be executed on the client <part-num-ref name="client">104</part-num-ref>
|
| 234 |
+
to retrieve content 120(k) stored on the head end <part-num-ref name="head end">116.</part-num-ref>
|
| 235 |
+
For example, the navigation module <part-num-ref name="navigation module">126</part-num-ref>
|
| 236 |
+
may communicate with a content module <part-num-ref name="content module">128</part-num-ref>
|
| 237 |
+
that is executable on a distribution server <part-num-ref name="distribution server">130</part-num-ref>
|
| 238 |
+
to cause recordation of content 112<confidence value="66">(j</confidence>
|
| 239 |
+
) received from the content provider <part-num-ref name="content provider">102</part-num-ref>
|
| 240 |
+
as content 120(k). In this instance, the content module <part-num-ref name="content module">128</part-num-ref>
|
| 241 |
+
provides network digital video recorder (NDVR) functionality in a manner similar to a DVR. For instance, the content module <part-num-ref name="content module">128</part-num-ref>
|
| 242 |
+
may support one or more trick modes to fast forward, pause, perform slow-motion playback, and so on in a manner similar to playback of the content 124(<confidence value="5">o</confidence>
|
| 243 |
+
) that is stored locally on the client <part-num-ref name="client">104.</part-num-ref>
|
| 244 |
+
The navigation module <part-num-ref name="navigation module">126</part-num-ref>
|
| 245 |
+
may also communicate with the content module <part-num-ref name="content module">128</part-num-ref>
|
| 246 |
+
to order on-demand content (e.g., VOD), PPV content, and so on. Thus, the environment <part-num-ref name="environment">100</part-num-ref>
|
| 247 |
+
may support a wide variety of content, such as VOD, PPV, <boundary-data type="header">9 Oc#: ms<confidence value="4">1</confidence>
|
| 248 |
+
-2257us/Ms#: 306556.01 </boundary-data>
|
| 249 |
+
<confidence value="288">lee</confidence>
|
| 250 |
+
<confidence value="222222">ghayes</confidence>
|
| 251 |
+
<page-break num="10"/>
|
| 252 |
+
locally-stored content 124(o), remotely-stored content 120(k), television programs, video games, music, and so on. </p>
|
| 253 |
+
<p id="p-32" num="32">
|
| 254 |
+
<confidence value="5">1</confidence>
|
| 255 |
+
00241 To navigate through this wide variety of content to locate a particular content item of interest (e.g., locally on the client <part-num-ref name="client">104,</part-num-ref>
|
| 256 |
+
remotely from the head end <part-num-ref name="head end">116,</part-num-ref>
|
| 257 |
+
and so on), the environment <part-num-ref name="environment">100</part-num-ref>
|
| 258 |
+
may support electronic program guide (EPG) functionality. For instance, the head end <part-num-ref name="head end">116</part-num-ref>
|
| 259 |
+
may also include a plurality of EPG data 132(m), where "<confidence value="5">m</confidence>
|
| 260 |
+
" can be any integer from one to "M". The plurality of EPG data 132(m) is stored in an EPG database <part-num-ref name="EPG database">134</part-num-ref>
|
| 261 |
+
for communication to the client <part-num-ref name="client">104.</part-num-ref>
|
| 262 |
+
Although illustrated separately, the EPG database <part-num-ref name="EPG database">134</part-num-ref>
|
| 263 |
+
and the content database <part-num-ref name="content database">118</part-num-ref>
|
| 264 |
+
may be implemented utilizing the same system. In an implementation, the EPG data 132(m) is broadcast utilizing a carousel file system. </p>
|
| 265 |
+
<p id="p-33" num="33">The carousel file system repeatedly broadcasts the EPG data 132(m) over an out- of-band (OOB) channel to the client <part-num-ref name="client">104</part-num-ref>
|
| 266 |
+
over the network <part-num-ref name="network">106.</part-num-ref>
|
| 267 |
+
The client <part-num-ref name="client">104</part-num-ref>
|
| 268 |
+
may then store the broadcast EPG data 132(m) received over the network <part-num-ref name="network">106</part-num-ref>
|
| 269 |
+
as EPG data 136(n), where "n" can be any integer from one to "N", in a database <part-num-ref name="database">138.</part-num-ref>
|
| 270 |
+
To generate an EPG <part-num-ref name="EPG">140,</part-num-ref>
|
| 271 |
+
the client <part-num-ref name="client">104</part-num-ref>
|
| 272 |
+
executes an EPG module <part-num-ref name="EPG module">142</part-num-ref>
|
| 273 |
+
that examines and configures the EPG data 136(n) into a form that suitable for output to and rendering by the display device <part-num-ref name="display device">110.</part-num-ref>
|
| 274 |
+
Additionally, the EPG <part-num-ref name="EPG">140</part-num-ref>
|
| 275 |
+
may be configured to describe content that is provided from various locations, such as the content 120(k) available from the head end <part-num-ref name="head end">116,</part-num-ref>
|
| 276 |
+
content 124(o) stored locally on the client <part-num-ref name="client">104,</part-num-ref>
|
| 277 |
+
and so on. </p>
|
| 278 |
+
<boundary-data type="header">10 Oc#: ms<confidence value="4">1</confidence>
|
| 279 |
+
-2257us<confidence value="5">/</confidence>
|
| 280 |
+
Ms#: 306556.01 </boundary-data>
|
| 281 |
+
<p id="p-34" num="34">
|
| 282 |
+
<confidence value="17711">Iee0-</confidence>
|
| 283 |
+
hayes <page-break num="11"/>
|
| 284 |
+
[0025<confidence value="4">1</confidence>
|
| 285 |
+
In another implementation, the EPG <part-num-ref name="EPG">140</part-num-ref>
|
| 286 |
+
is formed from the EPG data 132(m) at the head end <part-num-ref name="head end">116</part-num-ref>
|
| 287 |
+
and then distributed to the client <part-num-ref name="client">104.</part-num-ref>
|
| 288 |
+
For example, the head end <part-num-ref name="head end">116</part-num-ref>
|
| 289 |
+
may also include an EPG module <part-num-ref name="EPG module">144</part-num-ref>
|
| 290 |
+
that is executable on the distribution server <part-num-ref name="distribution server">130</part-num-ref>
|
| 291 |
+
to generate the EPG <part-num-ref name="EPG">140</part-num-ref>
|
| 292 |
+
from the EPG data 132(m). The EPG <part-num-ref name="EPG">140</part-num-ref>
|
| 293 |
+
may be configured in a variety of ways through execution of the EPG module <part-num-ref name="EPG module">144</part-num-ref>
|
| 294 |
+
at the head end <part-num-ref name="head end">116,</part-num-ref>
|
| 295 |
+
such as a particular EPG for each particular client that is communicatively coupled to the head end <part-num-ref name="head end">116,</part-num-ref>
|
| 296 |
+
a generic EPG representing each item of content 120(k) (which will also be referred to in the following discussion as a "content item"), and so on. Distribution from the head end <part-num-ref name="head end">116</part-num-ref>
|
| 297 |
+
to the client <part-num-ref name="client">104</part-num-ref>
|
| 298 |
+
may be accommodated in a number of ways, including cable, RF, microwave, digital subscriber line (DSL), and satellite. </p>
|
| 299 |
+
<p id="p-35" num="35">
|
| 300 |
+
<confidence value="5">[</confidence>
|
| 301 |
+
0026<confidence value="5">]</confidence>
|
| 302 |
+
Either one or both of the EPG modules <part-num-ref name="EPG modules">142,</part-num-ref>
|
| 303 |
+
<part-num-ref name="EPG modules 142,">144</part-num-ref>
|
| 304 |
+
may be executed to search EPG data 136(n), 132(m) to locate a particular content item and/or channel of interest. For example, the EPG data 132(m) may include content metadata 146(m), channel metadata 148(m), and schedule data 150(m). Content metadata 146(m) is configured to describe one or more characteristics of a corresponding content item. Likewise, channel metadata 148(m) is configured to describe one or more characteristics of a corresponding channel. Channels may be configured in a variety of ways, and include what is also referred to as "sub-channels", which may be utilized to provide alternate-audio version of content, wide-screen versions of content items, and so on. </p>
|
| 305 |
+
<boundary-data type="header">11 Oc#: ms<confidence value="4">1</confidence>
|
| 306 |
+
-2257us<confidence value="5">/</confidence>
|
| 307 |
+
Ms#: 306556.01 </boundary-data>
|
| 308 |
+
<p id="p-36" num="36">
|
| 309 |
+
<confidence value="222222222">lee@hayes</confidence>
|
| 310 |
+
<page-break num="12"/>
|
| 311 |
+
<confidence value="5">1</confidence>
|
| 312 |
+
0027<confidence value="5">1</confidence>
|
| 313 |
+
Schedule data 150(m) is utilized to describe when the content items described in the content metadata 146(m) are available via the channels described via the channel metadata 148(m). The EPG module <part-num-ref name="EPG module">144,</part-num-ref>
|
| 314 |
+
when executed may search the content metadata 146(m) as well as the channel metadata 148(m) to locate content and channels, respectively, that correspond to a search request. </p>
|
| 315 |
+
<p id="p-37" num="37">Further discussion of EPG data may be found in relation to FIG. 2, while further discussion of execution of the EPG modules may be found in relation to FIG. 3.</p>
|
| 316 |
+
<p id="p-38" num="38">
|
| 317 |
+
<confidence value="5">1</confidence>
|
| 318 |
+
00281 Generally, any of the functions described herein can be implemented using software, firmware (e.g., fixed logic circuitry), manual processing, or a combination of these implementations. The terms "module," "functionality," and "logic" as used herein generally represent software, firmware, or a combination of software and firmware. In the case of a software implementation, the module, functionality, or logic represents program code that performs specified tasks when executed on a processor (e.g., CPU or CPUs). The program code can be stored in one or more computer readable memory devices, further description of which may be found in relation to FIG. 2. The features of the searching strategies described below are platform-independent, meaning that the searching strategies may be implemented on a variety of commercial computing platforms having a variety of processors. </p>
|
| 319 |
+
<p id="p-39" num="39">
|
| 320 |
+
<confidence value="5">1</confidence>
|
| 321 |
+
0029<confidence value="5">1</confidence>
|
| 322 |
+
FIG. 2 is an illustration of an exemplary implementation of a system <part-num-ref name="system">200</part-num-ref>
|
| 323 |
+
showing the distribution server <part-num-ref name="distribution server">130</part-num-ref>
|
| 324 |
+
and the client <part-num-ref name="client">104</part-num-ref>
|
| 325 |
+
of FIG. 1 in greater detail. </p>
|
| 326 |
+
<p id="p-40" num="40">The client 104 includes a processor <part-num-ref name="processor">202</part-num-ref>
|
| 327 |
+
and memory <part-num-ref name="and memory">204.</part-num-ref>
|
| 328 |
+
The navigation module <boundary-data type="header">12 Oc#: ms<confidence value="4">1</confidence>
|
| 329 |
+
-2257us/Ms#: 306556.01 </boundary-data>
|
| 330 |
+
<confidence value="1771161177">lee0-hayes</confidence>
|
| 331 |
+
<page-break num="13"/>
|
| 332 |
+
<part-num-ref name="navigation module lee0-hayes">126</part-num-ref>
|
| 333 |
+
is illustrated as being executed on the processor <part-num-ref name="processor">202</part-num-ref>
|
| 334 |
+
and is storable in memory <part-num-ref name="and is storable in memory">204.</part-num-ref>
|
| 335 |
+
The database <part-num-ref name="database">122,</part-num-ref>
|
| 336 |
+
which is utilized to store the plurality of content 124(o), is illustrated as included in the memory <part-num-ref name="memory">204.</part-num-ref>
|
| 337 |
+
Likewise, the database <part-num-ref name="database">138</part-num-ref>
|
| 338 |
+
which is used to store the plurality of EPG data 136(n) is also illustrated as included in the memory <part-num-ref name="memory">204.</part-num-ref>
|
| 339 |
+
Although illustrated together, the databases <part-num-ref name="databases">122,</part-num-ref>
|
| 340 |
+
<part-num-ref name="databases 122,">138</part-num-ref>
|
| 341 |
+
may be implemented as stand-alone devices. For example, the databases <part-num-ref name="databases">122,</part-num-ref>
|
| 342 |
+
<part-num-ref name="databases 122,">138</part-num-ref>
|
| 343 |
+
may be respectively implemented as a hard disk drive and RAM, both may be configured as RAM, one may be configured as a removable memory device, and so forth. </p>
|
| 344 |
+
<p id="p-41" num="41">
|
| 345 |
+
<confidence value="5">[</confidence>
|
| 346 |
+
003<confidence value="55">01</confidence>
|
| 347 |
+
As shown in the environment <part-num-ref name="environment">100</part-num-ref>
|
| 348 |
+
of FIG. 1, the client <part-num-ref name="client">104</part-num-ref>
|
| 349 |
+
may obtain content from a variety of sources. For example, the client <part-num-ref name="client">104</part-num-ref>
|
| 350 |
+
may execute the navigation module <part-num-ref name="navigation module">126</part-num-ref>
|
| 351 |
+
to retrieve content 124(o) from the database <part-num-ref name="database">122.</part-num-ref>
|
| 352 |
+
The retrieved content 124(o) may then be output using an output interface <part-num-ref name="output interface">206</part-num-ref>
|
| 353 |
+
for rendering on the display device <part-num-ref name="display device">110.</part-num-ref>
|
| 354 |
+
The client <part-num-ref name="client">104,</part-num-ref>
|
| 355 |
+
through execution of the navigation module <part-num-ref name="navigation module">126,</part-num-ref>
|
| 356 |
+
is also capable of requesting content 120(k) from the distribution server <part-num-ref name="distribution server">130</part-num-ref>
|
| 357 |
+
over the network <part-num-ref name="network">106.</part-num-ref>
|
| 358 |
+
The distribution server <part-num-ref name="distribution server">130</part-num-ref>
|
| 359 |
+
is represented pictorially as including the database <part-num-ref name="database">118</part-num-ref>
|
| 360 |
+
having the plurality of content 120(k) for streaming over a network <part-num-ref name="network">106.</part-num-ref>
|
| 361 |
+
The distribution server <part-num-ref name="distribution server">130</part-num-ref>
|
| 362 |
+
may provide EPG data 132(m) from the database <part-num-ref name="database">134</part-num-ref>
|
| 363 |
+
that describes content available from the content provider <part-num-ref name="content provider">102</part-num-ref>
|
| 364 |
+
of FIG. 1. </p>
|
| 365 |
+
<p id="p-42" num="42">
|
| 366 |
+
<confidence value="4">1</confidence>
|
| 367 |
+
0031<confidence value="5">1</confidence>
|
| 368 |
+
The navigation module <part-num-ref name="navigation module">126,</part-num-ref>
|
| 369 |
+
when executed on the processor <part-num-ref name="processor">202,</part-num-ref>
|
| 370 |
+
may send a request via the network <part-num-ref name="network">106</part-num-ref>
|
| 371 |
+
to the distribution server <part-num-ref name="distribution server">130</part-num-ref>
|
| 372 |
+
to request content 120(k) for streaming over the network <part-num-ref name="network">106,</part-num-ref>
|
| 373 |
+
such as a PPV movie, VOD, and so <part-num-ref name="PPV movie, VOD, and so">13</part-num-ref>
|
| 374 |
+
Oc#: ms<confidence value="4">1</confidence>
|
| 375 |
+
-2257us/Ms#: 306556.01 <page-break num="14"/>
|
| 376 |
+
forth. To communicate using the network <part-num-ref name="network">106,</part-num-ref>
|
| 377 |
+
the client <part-num-ref name="client">104</part-num-ref>
|
| 378 |
+
includes a network interface <part-num-ref name="network interface">208</part-num-ref>
|
| 379 |
+
to communicatively couple the client <part-num-ref name="client">104</part-num-ref>
|
| 380 |
+
with the distribution server <part-num-ref name="distribution server">130.</part-num-ref>
|
| 381 |
+
As previously described, the network <part-num-ref name="network">106</part-num-ref>
|
| 382 |
+
may support two-way communication between the distribution server <part-num-ref name="distribution server">130</part-num-ref>
|
| 383 |
+
and the client <part-num-ref name="client">104.</part-num-ref>
|
| 384 |
+
</p>
|
| 385 |
+
<p id="p-43" num="43">Additionally, the network <part-num-ref name="network">106</part-num-ref>
|
| 386 |
+
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 including, for example, microwave, satellite, and/or data networks, such as the Internet. Furthermore, the network <part-num-ref name="network">106</part-num-ref>
|
| 387 |
+
may be capable of transmitting and receiving wired or wireless media using any broadcast format or broadcast protocol. </p>
|
| 388 |
+
<p id="p-44" num="44">
|
| 389 |
+
<confidence value="5">1</confidence>
|
| 390 |
+
0032<confidence value="5">1</confidence>
|
| 391 |
+
The distribution server <part-num-ref name="distribution server">130</part-num-ref>
|
| 392 |
+
is illustrated as including a network transmitter <part-num-ref name="network transmitter">210</part-num-ref>
|
| 393 |
+
(hereinafter "transmitter"). The transmitter <part-num-ref name="transmitter">210</part-num-ref>
|
| 394 |
+
may distribute the content 120(k) from the database <part-num-ref name="database">118,</part-num-ref>
|
| 395 |
+
the EPG data 132(m) from the database <part-num-ref name="database">134,</part-num-ref>
|
| 396 |
+
and so on. In alternate implementations, the distribution server <part-num-ref name="distribution server">130,</part-num-ref>
|
| 397 |
+
database <part-num-ref name="distribution server 130, database">118,</part-num-ref>
|
| 398 |
+
database <part-num-ref name="distribution server 130, database 118, database">134,</part-num-ref>
|
| 399 |
+
and the transmitter <part-num-ref name="transmitter">210</part-num-ref>
|
| 400 |
+
may be implemented as one or more distinct components, locally as part of the head end <part-num-ref name="head end">116</part-num-ref>
|
| 401 |
+
and/or content provider <part-num-ref name="and/or content provider">102</part-num-ref>
|
| 402 |
+
of FIG. 1, or remotely as part of another distinct system. For instance, although the distribution server <part-num-ref name="distribution server">130</part-num-ref>
|
| 403 |
+
is shown as including the EPG module <part-num-ref name="EPG module">144</part-num-ref>
|
| 404 |
+
and content module <part-num-ref name="and content module">128</part-num-ref>
|
| 405 |
+
(which are executable for distribution of content 120(k), distribution of the EPG data 132(m), and/or generation of the EPG <part-num-ref name="EPG">140</part-num-ref>
|
| 406 |
+
as previously described), each component and its corresponding functionality may be <boundary-data type="header">14 Oc#: ms<confidence value="4">1</confidence>
|
| 407 |
+
-2257us/Ms#: 306556.01 </boundary-data>
|
| 408 |
+
<confidence value="11111416">le0-hyes</confidence>
|
| 409 |
+
<page-break num="15"/>
|
| 410 |
+
implemented via a distinct device, such as a server. Accordingly, the distribution server <part-num-ref name="distribution server">130</part-num-ref>
|
| 411 |
+
may represent a plurality of servers which provide the functionality. </p>
|
| 412 |
+
<p id="p-45" num="45">
|
| 413 |
+
<confidence value="4">1</confidence>
|
| 414 |
+
0033<confidence value="5">1</confidence>
|
| 415 |
+
The distribution server <part-num-ref name="distribution server">130</part-num-ref>
|
| 416 |
+
also includes a processor <part-num-ref name="processor">212</part-num-ref>
|
| 417 |
+
and memory <part-num-ref name="and memory">214.</part-num-ref>
|
| 418 |
+
</p>
|
| 419 |
+
<p id="p-46" num="46">The content module 128 is illustrated as including the EPG module <part-num-ref name="EPG module">144,</part-num-ref>
|
| 420 |
+
which are both illustrated as being executed on the processor <part-num-ref name="processor">212</part-num-ref>
|
| 421 |
+
and are storable in memory <part-num-ref name="and are storable in memory">214.</part-num-ref>
|
| 422 |
+
The EPG module <part-num-ref name="EPG module">144</part-num-ref>
|
| 423 |
+
is illustrated as within the content module <part-num-ref name="content module">128</part-num-ref>
|
| 424 |
+
to portray that both modules may be implemented together, although both modules may also be implemented separately as "stand-alone" modules as shown in FIG. 1. </p>
|
| 425 |
+
<p id="p-47" num="47">
|
| 426 |
+
<confidence value="5">[</confidence>
|
| 427 |
+
0034<confidence value="5">1</confidence>
|
| 428 |
+
The content module <part-num-ref name="content module">128</part-num-ref>
|
| 429 |
+
may also control distribution of the content 120(k) over the network <part-num-ref name="network">106</part-num-ref>
|
| 430 |
+
as previously described. For instance, the content module <part-num-ref name="content module">128</part-num-ref>
|
| 431 |
+
may receive a request from the client <part-num-ref name="client">104</part-num-ref>
|
| 432 |
+
to receive the content 120(k). The content module <part-num-ref name="content module">128</part-num-ref>
|
| 433 |
+
processes the request, such as to determine whether the client <part-num-ref name="client">104</part-num-ref>
|
| 434 |
+
is permitted to receive the content 120(k) (e.g., the client <part-num-ref name="client">104</part-num-ref>
|
| 435 |
+
has obtained conditional access rights to the content), obtain billing information from the client <part-num-ref name="client">104,</part-num-ref>
|
| 436 |
+
locate the requested content from the plurality of content 120(k), and so on. </p>
|
| 437 |
+
<p id="p-48" num="48">If the client <part-num-ref name="client">104</part-num-ref>
|
| 438 |
+
is permitted to receive the content 120(k), the content module <part-num-ref name="content module">128</part-num-ref>
|
| 439 |
+
may be executed to stream the content 120(k) to the client <part-num-ref name="client">104</part-num-ref>
|
| 440 |
+
over the network <part-num-ref name="network">106</part-num-ref>
|
| 441 |
+
by using the transmitter <part-num-ref name="transmitter">210.</part-num-ref>
|
| 442 |
+
In this instance, the content 120(k) is provided from the distribution server <part-num-ref name="distribution server">130</part-num-ref>
|
| 443 |
+
in response to the request, and therefore is provided "on-demand" to the client <part-num-ref name="client">104.</part-num-ref>
|
| 444 |
+
Examples of on-demand content items include VOD, video games, content that is locally stored via a DVR or remotely via a NDVR, and so on. </p>
|
| 445 |
+
<boundary-data type="header">15 Oc#: ms<confidence value="5">1</confidence>
|
| 446 |
+
-2257us/Ms#: 306556.01 </boundary-data>
|
| 447 |
+
<p id="p-49" num="49">
|
| 448 |
+
<confidence value="177177116">Iee-hayes</confidence>
|
| 449 |
+
<page-break num="16"/>
|
| 450 |
+
100351 The content module <part-num-ref name="content module">128,</part-num-ref>
|
| 451 |
+
when executed in this example, may also control distribution of the EPG data 132(m) from the database <part-num-ref name="database">134</part-num-ref>
|
| 452 |
+
over the network <part-num-ref name="network">106.</part-num-ref>
|
| 453 |
+
</p>
|
| 454 |
+
<p id="p-50" num="50">EPG data 132(m) may include any data that may be utilized to generate the EPG <part-num-ref name="EPG">140,</part-num-ref>
|
| 455 |
+
such as obtained from the content provider <part-num-ref name="content provider">102</part-num-ref>
|
| 456 |
+
which describes the provided content, metadata included with content 124(<confidence value="5">o</confidence>
|
| 457 |
+
) stored on the database <part-num-ref name="database">138</part-num-ref>
|
| 458 |
+
on the client <part-num-ref name="client">104</part-num-ref>
|
| 459 |
+
as previously described in the DVR example, and so on. </p>
|
| 460 |
+
<p id="p-51" num="51">
|
| 461 |
+
<confidence value="5">1</confidence>
|
| 462 |
+
0036<confidence value="5">1</confidence>
|
| 463 |
+
The EPG data 132(m), for instance, may be configured to include content metadata 146(m), channel metadata 148(m), and schedule data 150(m) as previously described. Content metadata 146(m) includes data that describes characteristics of a particular one of a plurality of content items 216(x), where "x" can be any integer from one to "X". For example, content metadata 146(m) for content item 216(x) may include a content title, detailed description of the content item, content genre, actors appearing in the content item, rating (e.g., PG, G, Mature, and so on), plot, whether the content item supports closed captioning, whether the content item is interactive, and other descriptive information that corresponds to the content item itself. Channel metadata 148(m) includes data that describes characteristics of a particular one of a plurality of channels 218(y), where "y" can be any integer from one to "Y". For example, channel metadata 148(m) may describe a call sign (e.g., KXYZ) of the respective channel 218(y), a title (e.g., "The Fried Food Channel") of the respective channel 218(y), a genre (e.g., sports, news, and so on), a detailed description of the respective channel <confidence value="8">2</confidence>
|
| 464 |
+
18(y), the owner of the respective channel 218(y), and so on. </p>
|
| 465 |
+
<boundary-data type="header">16 Oc#: ms<confidence value="4">1</confidence>
|
| 466 |
+
-2257us<confidence value="5">/</confidence>
|
| 467 |
+
Ms#: 306556.01 </boundary-data>
|
| 468 |
+
<p id="p-52" num="52">
|
| 469 |
+
<confidence value="17711">Iee0-</confidence>
|
| 470 |
+
hayes <page-break num="17"/>
|
| 471 |
+
<confidence value="86">10</confidence>
|
| 472 |
+
0371 Schedule data 150(m) includes a plurality of time/content/channel 220(<confidence value="68">z)</confidence>
|
| 473 |
+
entries, where "z" can be any integer from one to <confidence value="666">"Z"</confidence>
|
| 474 |
+
. Each of the time/content/channel 220(z) entries describes a particular time, at which, a corresponding one of the plurality of content items 216(x) is available via a corresponding one of the plurality of channels 218(y). Thus, the schedule data 150(m) may be utilized to "link" the content metadata 146(m) with the channel metadata 148(m) for generating the EPG <part-num-ref name="EPG">140.</part-num-ref>
|
| 475 |
+
</p>
|
| 476 |
+
<p id="p-53" num="53">
|
| 477 |
+
<confidence value="5">[</confidence>
|
| 478 |
+
00381 The EPG module <part-num-ref name="EPG module">144,</part-num-ref>
|
| 479 |
+
when executed, utilizes the EPG data 132(m), and more particularly the content metadata 146(m), channel metadata 148(m), and schedule data 150(m) to generate the EPG <part-num-ref name="EPG">140.</part-num-ref>
|
| 480 |
+
Once displayed, a user may interact with the EPG <part-num-ref name="EPG">140</part-num-ref>
|
| 481 |
+
to search the EPG data 132(m) for particular content items 216(x) and/or channels 218(y) of interest, further discussion of which may be found beginning in relation to FIG. 3. </p>
|
| 482 |
+
<p id="p-54" num="54">Exemplary Procedures <confidence value="5">[</confidence>
|
| 483 |
+
0039<confidence value="5">]</confidence>
|
| 484 |
+
The following discussion describes searching of EPG data that may be implemented utilizing the previously described systems and devices. Aspects of each of the procedures may be implemented in hardware, firmware, or software, or a combination thereof. The procedures are shown as a set of blocks that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. </p>
|
| 485 |
+
<p id="p-55" num="55">
|
| 486 |
+
<confidence value="5">1</confidence>
|
| 487 |
+
0040<confidence value="5">1</confidence>
|
| 488 |
+
FIG. 3 is a flow diagram depicting a procedure <part-num-ref name="procedure">300</part-num-ref>
|
| 489 |
+
in an exemplary implementation in which both content metadata 146(m) and channel metadata <boundary-data type="header">17 <confidence value="666">Oc#</confidence>
|
| 490 |
+
: ms<confidence value="4">1</confidence>
|
| 491 |
+
-2257us/Ms#: 306556.01 </boundary-data>
|
| 492 |
+
<confidence value="177177116">Iee-hayes</confidence>
|
| 493 |
+
<page-break num="18"/>
|
| 494 |
+
148(m) are searched in response to a search request received from a user through interaction with an EPG. In this implementation, searching will be described that is performed through execution of the EPG module <part-num-ref name="EPG module">144</part-num-ref>
|
| 495 |
+
on the distribution server <part-num-ref name="distribution server">130.</part-num-ref>
|
| 496 |
+
It should be noted that similar searching may also be performed locally on the client, such as through execution of the EPG module <part-num-ref name="EPG module">142</part-num-ref>
|
| 497 |
+
of FIG. 1. </p>
|
| 498 |
+
<p id="p-56" num="56">
|
| 499 |
+
<confidence value="5">1</confidence>
|
| 500 |
+
0041<confidence value="5">1</confidence>
|
| 501 |
+
First, a client <part-num-ref name="client">104</part-num-ref>
|
| 502 |
+
communicates a search request <part-num-ref name="search request">302</part-num-ref>
|
| 503 |
+
to a head end <part-num-ref name="head end">116</part-num-ref>
|
| 504 |
+
over a network <part-num-ref name="network">106</part-num-ref>
|
| 505 |
+
(block 304). The search request <part-num-ref name="search request">302</part-num-ref>
|
| 506 |
+
may be formed and communicated in a variety of ways. For example, the search request may be entered by the user through use of an input device, such as a keyboard, to formulate the search. In another implementation, the search request may be formed through interaction by the user with the EPG <part-num-ref name="EPG">140</part-num-ref>
|
| 507 |
+
when output by the client <part-num-ref name="client">104,</part-num-ref>
|
| 508 |
+
further discussion of which may be found in relation to FIG. 4. </p>
|
| 509 |
+
<p id="p-57" num="57">
|
| 510 |
+
<confidence value="5">[</confidence>
|
| 511 |
+
0042<confidence value="4">]</confidence>
|
| 512 |
+
The head end <part-num-ref name="head end">116,</part-num-ref>
|
| 513 |
+
upon receipt of the search request <part-num-ref name="search request">302,</part-num-ref>
|
| 514 |
+
executes the EPG module <part-num-ref name="EPG module">144</part-num-ref>
|
| 515 |
+
to search EPG data 132(m), and more particularly to search content metadata 146(m) and channel metadata 148(m) that is included in the EPG data 132(m). For example, the head end <part-num-ref name="head end">116</part-num-ref>
|
| 516 |
+
may include a database <part-num-ref name="database">134,</part-num-ref>
|
| 517 |
+
as previously described in relation to FIG. 1, which includes a plurality of EPG data 132(m). </p>
|
| 518 |
+
<p id="p-58" num="58">The EPG data 132(m) may include content metadata 146(m), channel metadata 148(m), and schedule data 150(m), each of which is compartmentalized to be separate, one from another. For instance, the content metadata 146(m) may be downloaded and stored on the head end <part-num-ref name="head end">116</part-num-ref>
|
| 519 |
+
separately from the channel metadata 148(m). </p>
|
| 520 |
+
<boundary-data type="header">18 Oc#: ms<confidence value="4">1</confidence>
|
| 521 |
+
-2257us<confidence value="5">/</confidence>
|
| 522 |
+
Ms#: 306556.01 </boundary-data>
|
| 523 |
+
<p id="p-59" num="59">
|
| 524 |
+
<confidence value="17718812">lee-have</confidence>
|
| 525 |
+
<page-break num="19"/>
|
| 526 |
+
10043<confidence value="5">1</confidence>
|
| 527 |
+
When searching the EPG data 132(m), the EPG module <part-num-ref name="EPG module">144</part-num-ref>
|
| 528 |
+
may compare the search request <part-num-ref name="search request">302</part-num-ref>
|
| 529 |
+
to a plurality of characteristics of the content metadata 146(m) and/or the channel metadata 148(m) to find a match. For instance, the content metadata 146(m) may describe a genre 308(1), plot 308(2), actors 308(3), content title 308(4), and other 308(A) characteristics of a particular content item. </p>
|
| 530 |
+
<p id="p-60" num="60">Likewise, the channel metadata 148(m) may describe a plurality of characteristics of a particular channel, such as a call sign 310(1), genre 310(2), channel title 310(3), and other 310(B) such characteristics. The EPG module <part-num-ref name="EPG module">144</part-num-ref>
|
| 531 |
+
may compare text, such as alphabetic characters, included in the search request <part-num-ref name="search request">302</part-num-ref>
|
| 532 |
+
with text describing the characteristics 308(1)-308(A), 310(1)-310(B) of the content and channels, respectively, to find corresponding content and channels. In an implementation, the EPG module <part-num-ref name="EPG module">144</part-num-ref>
|
| 533 |
+
may also determine when the described content items that correspond to the located content metadata 146(m) are available by examining the schedule data 150(m). </p>
|
| 534 |
+
<p id="p-61" num="61">
|
| 535 |
+
<confidence value="5">1</confidence>
|
| 536 |
+
0044<confidence value="5">1</confidence>
|
| 537 |
+
Based on the search, the head end <part-num-ref name="head end">116</part-num-ref>
|
| 538 |
+
executes the EPG module <part-num-ref name="EPG module">144</part-num-ref>
|
| 539 |
+
to form a search result <part-num-ref name="search result">312</part-num-ref>
|
| 540 |
+
for communication to the client <part-num-ref name="client">104</part-num-ref>
|
| 541 |
+
over the network <part-num-ref name="network">106</part-num-ref>
|
| 542 |
+
(block 314). For example, the EPG module <part-num-ref name="EPG module">144</part-num-ref>
|
| 543 |
+
may be included within a server module that is configured to form and communicate a stream of packets over the network <part-num-ref name="network">106</part-num-ref>
|
| 544 |
+
to the client <part-num-ref name="client">104.</part-num-ref>
|
| 545 |
+
In the illustrated implementation, the client <part-num-ref name="client">104</part-num-ref>
|
| 546 |
+
then outputs the search result <part-num-ref name="search result">312</part-num-ref>
|
| 547 |
+
in conjunction with an EPG <part-num-ref name="EPG">140</part-num-ref>
|
| 548 |
+
for rendering by the display device <part-num-ref name="display device">110</part-num-ref>
|
| 549 |
+
(block 316). For example, the search result <part-num-ref name="search result">312</part-num-ref>
|
| 550 |
+
may include a plurality of representations of channels and content items that were <part-num-ref name="plurality of representations of channels and content items that were">19</part-num-ref>
|
| 551 |
+
Oc#: ms<confidence value="4">l</confidence>
|
| 552 |
+
-2257us<confidence value="5">/</confidence>
|
| 553 |
+
Ms#: 306556.01 <page-break num="20"/>
|
| 554 |
+
located during the search. The plurality of representations may be configured to enable the user to navigate to the represented item, such as to tune to a represented channel, load a represented content item from the database <part-num-ref name="database">122</part-num-ref>
|
| 555 |
+
of FIG. 1, and so on. Thus, the search module <part-num-ref name="search module">144</part-num-ref>
|
| 556 |
+
may be executed to search both content and channel metadata 146(m), 148(m) to locate channels and/or content items of interest. As previously described, the search request <part-num-ref name="search request">302</part-num-ref>
|
| 557 |
+
may be formed in a variety of ways, an example of which may be found in relation to the following illustration. </p>
|
| 558 |
+
<p id="p-62" num="62">
|
| 559 |
+
<confidence value="4">1</confidence>
|
| 560 |
+
0045<confidence value="4">]</confidence>
|
| 561 |
+
FIG. 4 is an illustration of an exemplary implementation in which the client of FIG. 3 outputs the EPG <part-num-ref name="EPG">140,</part-num-ref>
|
| 562 |
+
which includes a search window <part-num-ref name="search window">402</part-num-ref>
|
| 563 |
+
configured for interaction by a user to form the search request <part-num-ref name="search request">302.</part-num-ref>
|
| 564 |
+
The EPG <part-num-ref name="EPG">400</part-num-ref>
|
| 565 |
+
of FIG. 4 is configured for output in a "10' experience". For example, a desktop computer is generally used by a user while sitting close to a display device. The user may utilize a mouse and keyboard connected to the desktop computer to interact with one or more applications that are being executed on the desktop computer. </p>
|
| 566 |
+
<p id="p-63" num="63">Because of the proximity between the user and the display device, this is referred to as a "2' experience" (e.g., a distance of about two <part-num-ref name="distance of about two">(2)</part-num-ref>
|
| 567 |
+
feet). Clients may also be configured for use in a more casual setting, such as a set-top box in a living room. </p>
|
| 568 |
+
<p id="p-64" num="64">To interact with the set-top box, the user may utilize a remote control. Because of the distance between the user and the display device, this scenario is referred to as a "10' experience". Traditional EPGs that are configured for the 10' experience, however, generally require a separate search page to search the EPG data.</p>
|
| 569 |
+
<boundary-data type="header">20 Oc#: ms<confidence value="4">l</confidence>
|
| 570 |
+
-2257us<confidence value="5">/</confidence>
|
| 571 |
+
Ms#: 306556.01 </boundary-data>
|
| 572 |
+
<p id="p-65" num="65">
|
| 573 |
+
<confidence value="188">fee</confidence>
|
| 574 |
+
hayes <page-break num="21"/>
|
| 575 |
+
Therefore, a user utilizing a traditional EPG is required to leave an EPG guide page, which includes representations of content items, to access a dedicated search page to perform the search. This navigation between pages results in inconvenience to the user and consequent underutilization of the search feature. </p>
|
| 576 |
+
<p id="p-66" num="66">Accordingly, the EPG <part-num-ref name="EPG">400</part-num-ref>
|
| 577 |
+
includes a search window <part-num-ref name="search window">402</part-num-ref>
|
| 578 |
+
such that the user does not need to leave an EPG guide page to perform a search. </p>
|
| 579 |
+
<p id="p-67" num="67">
|
| 580 |
+
<confidence value="5">[</confidence>
|
| 581 |
+
00461 To enter text via the EPG <part-num-ref name="EPG">400,</part-num-ref>
|
| 582 |
+
for instance, a display of a keyboard <part-num-ref name="keyboard">404</part-num-ref>
|
| 583 |
+
may be provided. For instance, a user may enter alphabetic text by selecting the representations of letters included in the keyboard <part-num-ref name="keyboard">404,</part-num-ref>
|
| 584 |
+
an example of which is illustrated in FIG. 4 as "BE". Alternatively, a mobile phone text entry system may be used to allow users to enter text quickly using the commonly used system employed by mobile devices. </p>
|
| 585 |
+
<p id="p-68" num="68">
|
| 586 |
+
<confidence value="5">[</confidence>
|
| 587 |
+
00471 Upon receipt of the alphabetic text "BE", the EPG module <part-num-ref name="EPG module">144</part-num-ref>
|
| 588 |
+
may search EPG data having content and channel metadata (e.g., EPG data 132(m) and/or EPG data 136(n) of FIG. 1) to find content items and channels which correspond to the alphabetic text. It should be noted, however, that the searching may also be dynamically performed as text is entered. For example, a search may begin once the letter "B" is entered and the results of the search displayed adjacent to a search window. These results may then be subsequently narrowed with the input of a next character, e.g., "<confidence value="5">E</confidence>
|
| 589 |
+
", and displayed along with the search window. Thus, the user may receive im<confidence value="8">m</confidence>
|
| 590 |
+
ediate feedback regarding the search as the search is being entered. </p>
|
| 591 |
+
<boundary-data type="header">21 Oc#: ms<confidence value="5">1</confidence>
|
| 592 |
+
-2257us/Ms#: 306556.01 </boundary-data>
|
| 593 |
+
<p id="p-69" num="69">
|
| 594 |
+
<confidence value="177188127">Iee-haves</confidence>
|
| 595 |
+
<page-break num="22"/>
|
| 596 |
+
<confidence value="5">1</confidence>
|
| 597 |
+
00481 In the illustrated example, the EPG module <part-num-ref name="EPG module">144</part-num-ref>
|
| 598 |
+
locates content items and channels which are described in the EPG <part-num-ref name="EPG">140</part-num-ref>
|
| 599 |
+
utilizing a plurality of representations. The illustrated EPG <part-num-ref name="illustrated EPG">140</part-num-ref>
|
| 600 |
+
includes representations of a movie "A Beautiful Mind" <part-num-ref name="movie "A Beautiful Mind"">406,</part-num-ref>
|
| 601 |
+
a channel "206 BET" <part-num-ref name="channel "206 BET"">408,</part-num-ref>
|
| 602 |
+
a television program "A Better Tomorrow" <part-num-ref name="television program "A Better Tomorrow"">410,</part-num-ref>
|
| 603 |
+
an infomercial "Be a Ballerina" <part-num-ref name="Ballerina"">412,</part-num-ref>
|
| 604 |
+
a public service announcement "Be Cool, Play it Safe" <part-num-ref name="public service announcement "Be Cool, Play it Safe"">414,</part-num-ref>
|
| 605 |
+
and a streaming audio channel "922 BRAZ Brazilian Rhythms" <part-num-ref name="streaming audio channel "922 BRAZ Brazilian Rhythms"">416.</part-num-ref>
|
| 606 |
+
Thus, in this example each of the representations includes at least one of the entered textual letters. Further, the EPG module <part-num-ref name="EPG module">142</part-num-ref>
|
| 607 |
+
may order the representations as shown based on how much of the represented channel and/or content item corresponds to the search request. This is shown in FIG. 4 through illustration of the streaming audio channel "922 BRAZ Brazilian Rhythms" <part-num-ref name="streaming audio channel "922 BRAZ Brazilian Rhythms"">416</part-num-ref>
|
| 608 |
+
as last in the list of representations since the representation does not include the letter "<confidence value="5">E</confidence>
|
| 609 |
+
" as entered in the search window <part-num-ref name="search window">402.</part-num-ref>
|
| 610 |
+
In another implementation, the EPG may automatically scroll to the representation which corresponds to the entered text in the text entry window <part-num-ref name="text entry window">402.</part-num-ref>
|
| 611 |
+
For example, a user might not be able to remember a channel number, but does remember a call sign of the channel. Therefore, the user can take advantage of the adjacent search window <part-num-ref name="adjacent search window">402</part-num-ref>
|
| 612 |
+
by entering all or part of the call sign of the channel. In response to the entry, the EPG may automatically scroll to a representation of the channel which corresponds to the entry. Thus, a user may interact with the EPG to quickly navigate even when using an input device that is configured for the 10' experience, such as a television remote control, or for other system having limited <boundary-data type="header">22 Oc#: ms<confidence value="4">1</confidence>
|
| 613 |
+
-2257us/Ms#: 306556.01 </boundary-data>
|
| 614 |
+
<confidence value="17711">lee0-</confidence>
|
| 615 |
+
hay<confidence value="16">es</confidence>
|
| 616 |
+
<page-break num="23"/>
|
| 617 |
+
display space, such as a wireless phone. Although use of a search window <part-num-ref name="search window">402</part-num-ref>
|
| 618 |
+
which is displayable concurrently with a plurality of representations of content items and/or channels has been described, a variety of other input techniques may be utilized to input the search request, another example of which may be found in relation to the following figure. </p>
|
| 619 |
+
<p id="p-70" num="70">
|
| 620 |
+
<confidence value="5">[</confidence>
|
| 621 |
+
0049<confidence value="5">]</confidence>
|
| 622 |
+
FIG. <confidence value="5">5</confidence>
|
| 623 |
+
is a flow diagram depicting a procedure <part-num-ref name="procedure">500</part-num-ref>
|
| 624 |
+
in another exemplary implementation in which a search request and a search result are formed through interaction by a user with an EPG. A client outputs an EPG <part-num-ref name="EPG">502</part-num-ref>
|
| 625 |
+
having a display of a plurality of channel representations 504-510 (block 512). In the illustrated EPG <part-num-ref name="illustrated EPG">502,</part-num-ref>
|
| 626 |
+
the plurality of channel representations 504-510 are displayed in a column having a corresponding heading "Channel". Each of the channel representations 504-510 displays a call sign or title of the represented channel and a number of the represented channel. For instance, representation <part-num-ref name="represented channel. For instance, representation">504</part-num-ref>
|
| 627 |
+
includes the text "KQED 990", representation <part-num-ref name="text "KQED 990", representation">506</part-num-ref>
|
| 628 |
+
includes the text "Holiday 991", representation <part-num-ref name="text "Holiday 991", representation">508</part-num-ref>
|
| 629 |
+
includes the text "HBO 992", and representation <part-num-ref name="text "HBO 992", and representation">510</part-num-ref>
|
| 630 |
+
includes the text "HBO Action 993". The EPG <part-num-ref name="EPG">502</part-num-ref>
|
| 631 |
+
is also illustrated as including a plurality of representations <part-num-ref name="plurality of representations">512</part-num-ref>
|
| 632 |
+
of corresponding content items that are available via the respective channels. </p>
|
| 633 |
+
<p id="p-71" num="71">
|
| 634 |
+
<confidence value="5">[</confidence>
|
| 635 |
+
0050<confidence value="4">]</confidence>
|
| 636 |
+
The EPG may then receive an input from a user through interaction with the EPG (block <part-num-ref name="EPG (block">514)</part-num-ref>
|
| 637 |
+
which is illustrated as EPG 502'. For example, the user may utilize a television remote control to select the representation <confidence value="5">5</confidence>
|
| 638 |
+
04'. Representation 504' is illustrated as a negative image of corresponding representation <part-num-ref name="negative image of corresponding representation">504</part-num-ref>
|
| 639 |
+
of EPG <boundary-data type="header">23 <confidence value="656">Oc#</confidence>
|
| 640 |
+
: ms<confidence value="4">1</confidence>
|
| 641 |
+
-2257us/Ms#: 306556.01 </boundary-data>
|
| 642 |
+
<confidence value="222222222">leeghayes</confidence>
|
| 643 |
+
<page-break num="24"/>
|
| 644 |
+
<part-num-ref name="of EPG leeghayes">502</part-num-ref>
|
| 645 |
+
to depict the selection. The user may then enter alphabetic text while the representation 504' is selected, such as through use of text entry keys on an input device. </p>
|
| 646 |
+
<p id="p-72" num="72">
|
| 647 |
+
<confidence value="5">1</confidence>
|
| 648 |
+
00511 As previously described, an EPG module may then be executed to search channel metadata based on the received input (block 516). Based on the search, the EPG 502' is configured to form EPG 502" for display of at least one channel having channel metadata that corresponds to the received input (block 518). For instance, the user may have entered the alphabetic characters "HB" while channel representation 504' was selected. Therefore, the EPG module may interpret from this action that the user wishes to search for a particular channel and thus search channel metadata for one or more channels which satisfy the search request. </p>
|
| 649 |
+
<p id="p-73" num="73">Representations 508", 510", 520, 522 of channels which satisfy the search request may then be output in the configured EGP 502" for viewing by the user (block 524). Although entry of alphabetic characters via a search window and through selection of a representation has been described, a wide variety of other input techniques and display techniques may be employed without departing from the spirit and scope thereof. For example, a user may enter a call sign of a channel number in the search window <part-num-ref name="search window">402</part-num-ref>
|
| 650 |
+
of FIG. 4 as previously described, which causes the channel lineup to automatically scroll to the channel having the entered call sign. </p>
|
| 651 |
+
<p id="p-74" num="74">
|
| 652 |
+
<confidence value="866686">[00521</confidence>
|
| 653 |
+
FIG. 6 is a flow diagram depicting a procedure <part-num-ref name="procedure">600</part-num-ref>
|
| 654 |
+
in an exemplary implementation in which a result of a search of EPG data includes channels having <boundary-data type="header">24 Oc#: ms<confidence value="4">l</confidence>
|
| 655 |
+
-2257us/Ms#: 306556.01 </boundary-data>
|
| 656 |
+
<confidence value="17711">Iee0-</confidence>
|
| 657 |
+
hay<confidence value="16">es</confidence>
|
| 658 |
+
<page-break num="25"/>
|
| 659 |
+
a common owner. In the previous implementations, channel metadata was searched to locate channels which correspond to a search request. The channel metadata may also be searched to promote "branding", such as channels which share a common owner. For instance, an input may be received from a user through interaction with an EPG (block <part-num-ref name="EPG (block">602)</part-num-ref>
|
| 660 |
+
as previously described. A search may be performed utilizing channel metadata and based on the received input for channels owned by a common owner such that at least one of the channels corresponds to the received input (block 604). </p>
|
| 661 |
+
<p id="p-75" num="75">
|
| 662 |
+
<confidence value="2">1</confidence>
|
| 663 |
+
0053<confidence value="5">1</confidence>
|
| 664 |
+
A search, for example, may be performed for "satellite news". As a result of the search, a news channel "Satellite News" may be located in channel metadata. The EPG module which performs the search may also locate other channels which are also owned by the owner of the "Satellite News" channel, such as "Satellite Headlines" Channel and a channel titled "In Their Own Words". </p>
|
| 665 |
+
<p id="p-76" num="76">Thus, the search result may include a channel which corresponds to the received input (e.g., "Satellite News" channel) as well as other channels which are commonly owned (e.g., "Satellite Headlines" channel and "In Their Own Words" channel). As before, the EPG may then be configured to display a representation of the at least one channel that corresponds to the search request and another representation of another channel that is commonly owned (block 606). The configured EPG may then be output for viewing by a user (block 608). In this way, the channel metadata may be utilized to promote brands (i.e., families) of <boundary-data type="header">25 <confidence value="656">Oc#</confidence>
|
| 666 |
+
: ms<confidence value="4">1</confidence>
|
| 667 |
+
-2257us<confidence value="5">/</confidence>
|
| 668 |
+
Ms#: 306556.01 </boundary-data>
|
| 669 |
+
<confidence value="177177116">lee-hayes</confidence>
|
| 670 |
+
<page-break num="26"/>
|
| 671 |
+
channels that may be of interest to the user and are presented to the user without the user having to search for each commonly owned channel individually. </p>
|
| 672 |
+
<p id="p-77" num="77">
|
| 673 |
+
<confidence value="6666">1005</confidence>
|
| 674 |
+
41 Conclusion Although the invention has been described in language specific to structural features and/or methodological acts, it is to be understood that the invention 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 claimed invention. </p>
|
| 675 |
+
<boundary-data type="header">26 Oc#: ms<confidence value="4">1</confidence>
|
| 676 |
+
-2257us/Ms#: 306556.01 </boundary-data>
|
| 677 |
+
<p id="p-78" num="78">
|
| 678 |
+
<confidence value="222222222">lee~hayes</confidence>
|
| 679 |
+
</p>
|
| 680 |
+
</description>
|
| 681 |
+
</us-patent-application>
|
| 682 |
+
|
prior_art/11013197.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
prior_art/11035978.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>11035978</doc-number>
|
| 8 |
+
<date>2009-01-14</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">P2621<confidence value="66885">1.A10</confidence>
|
| 14 |
+
</p>
|
| 15 |
+
<heading id="h-1">IN T<confidence value="5">H</confidence>
|
| 16 |
+
E SPECIFICATION </heading>
|
| 17 |
+
<p id="p-2" num="2">Please replace the Abstract with the Abstract of the Disclosure appended on the following page.</p>
|
| 18 |
+
<p id="p-3" num="3">
|
| 19 |
+
<confidence value="4">(</confidence>
|
| 20 |
+
P26211 00606455.DOC<confidence value="8">}</confidence>
|
| 21 |
+
<confidence value="8">2</confidence>
|
| 22 |
+
</p>
|
| 23 |
+
</description>
|
| 24 |
+
</us-patent-application>
|
| 25 |
+
|
prior_art/11072226.xml
ADDED
|
@@ -0,0 +1,400 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11072226</doc-number>
|
| 8 |
+
<date>2005-03-07</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">CYLINDRICAL SP<confidence value="8">U</confidence>
|
| 14 |
+
TTERI<confidence value="8">N</confidence>
|
| 15 |
+
G TARGET, CERA<confidence value="8">M</confidence>
|
| 16 |
+
IC SINTERED BODY, AND </heading>
|
| 17 |
+
<heading id="h-2">PROCESS FOR PRODUCING SINTERED BODY</heading>
|
| 18 |
+
<heading id="h-3">FIELD OF THE INVENTION</heading>
|
| 19 |
+
<p id="p-1" num="1">The present invention relates to a cylindrical sputtering target used in a magnetron rotating cathode sputtering apparatus, a hollow cylindrical ceramic sintered body used as a target material, and a process for producing the ceramic sintered body.</p>
|
| 20 |
+
<heading id="h-4">BACKGROUND ART</heading>
|
| 21 |
+
<p id="p-2" num="2">A magnetron rotating cathode sputtering apparatus a magnetic filed generation device inside a cylindrical target, and performs sputtering by rotating a target while cooling from the inside of the target. The entire face of the target material becomes an erosion state, and is uniformly cut. As a result, markedly high target use efficiency (60% or higher) is obtained, compared with use efficiency (20-30%) of the conventional flat plate type magnetron rotating cathode sputtering apparatus. Further, by rotating a target, large power per unit area can be introduced, compared with the conventional flat plate type magnetron rotating cathode sputtering apparatus. As a result, high film formation rate is obtained (see, for example, JP-T<confidence value="5">-</confidence>
|
| 22 |
+
58-500174) (The term "JP-T" as used herein means a published Japanese translation of a PCT patent application). Such a rotating cathode sputtering method is wide spread in a metal target which is easily processed into a cylindrical shape and has high mechanical strength. However, in a ceramic target having low strength and being brittle, cracks, deformation or the like are liable to occur during its production. For this reason, only a target produced using a specific material or produced by a specific process has been used. </p>
|
| 23 |
+
<p id="p-3" num="3">It is known that the conventional flat plate type the conventional flat plate type sputtering target improves its quality by increasing a density of its ceramic sintered body. For example, in ITO (Indium Tin Oxide) used as a transparent conductive film, there are a method of obtaining a high density target by sintering the ITO in a pressurized oxygen atmosphere (for example, JP-A-3-060351), and a method in which <boundary-data type="header">
|
| 24 |
+
<confidence value="8">1</confidence>
|
| 25 |
+
</boundary-data>
|
| 26 |
+
<page-break num="2"/>
|
| 27 |
+
density of a sintered body is increased and diameter of sintered particles is controlled, thereby a sputtering rate increases, and generation of nodule on a target surface, causing fine particles, is effectively prevented (for example, JP-A-5-311428). Thus, various ingenuities have been made in the flat plate type ITO target. In particular, in view of that a high density target produced by a sintering method has excellent quality, the sintering method is recently employed as a production method of the flat plate type target. </p>
|
| 28 |
+
<p id="p-4" num="4">However, when density of a cylindrical ceramic target is made to have high density using the sintering method, there was the problem that sintering shrinkage is large, so that cracks, deformation and the like occur in sintering. For this reason, the cylindrical target that can be produced by the sintering method has low sintering shrinkage and low density showing a relative density of about 80%, as described in, for example, working examples of JP-A-3-153868 or comparative examples of JP-A-6-156431.</p>
|
| 29 |
+
<p id="p-5" num="5">Proposed methods other than the sintering method include a method of forming a target layer on an outer surface of a cylindrical substrate by a plasma spray method (for example, JP-A-1<confidence value="5">0</confidence>
|
| 30 |
+
-068072), and a method of forming a target by charging a powder on an outer surface of a cylindrical substrate, and performing hot isotropic pressing (HIP<confidence value="5">)</confidence>
|
| 31 |
+
(for example, JP-A-<confidence value="56">05</confidence>
|
| 32 |
+
-156431). Those methods directly produce a target on the cylindrical substrate. Therefore, the cylindrical substrate and target material (sintered body) cannot be separated from the used target. This gives rise to the problems that reuse of a substrate or recycle of a target material, generally performed, is impossible or difficult, and such is not economical in a sputtering target using an expensive material. </p>
|
| 33 |
+
<p id="p-6" num="6">In a method of forming a target layer by an arc spray method, the layer formed tends to contain air bubbles, and have low density. In ITO target described in <confidence value="5">J</confidence>
|
| 34 |
+
P-A-1<confidence value="5">0</confidence>
|
| 35 |
+
-068072, the maximum density is 5.3 <confidence value="2222">g/cm</confidence>
|
| 36 |
+
3, and this density merely corresponds to a relative density 74% (calculated from true density of ITO: 7.156 <boundary-data type="header">
|
| 37 |
+
<confidence value="8">2</confidence>
|
| 38 |
+
</boundary-data>
|
| 39 |
+
<page-break num="3"/>
|
| 40 |
+
<confidence value="2222">g/cm</confidence>
|
| 41 |
+
3). This is very low density, compared with a high density target recently used. </p>
|
| 42 |
+
<p id="p-7" num="7">A method of forming a target by HIP requires large cost, which is not economical.</p>
|
| 43 |
+
<p id="p-8" num="8">Further, where a sputtering target is produced using ceramics sintered in a reducing atmosphere as in HIP, problems arise that oxides, particularly, ITO, have decreased oxygen content, and quality of a film obtained by sputtering deteriorates.</p>
|
| 44 |
+
<p id="p-9" num="9">Where a target is produced by a sintering method, a sintered body must be bonded to a cylindrical substrate. However, this involves the problem that cracks or breakage are liable to occur in such a bonding step. In the cylindrical target, a method of preventing generation of cracks or breakage in a bonding step has been proposed by that instead of using, as a substrate, Cu which has conventionally been used in a flat plate type target, for example, Ti having a coefficient of thermal expansion very similar to that of ITO sintered body being a target material is used as a cylindrical substrate (for example, <confidence value="5">J</confidence>
|
| 45 |
+
P-A-06-293963 and <confidence value="5">J</confidence>
|
| 46 |
+
P-A-08-060351). However, considering that Ti is an expensive material, and Ti can be applied to only the case that the target material and the substrate have the similar coefficient of thermal expansion, use of a cylindrical substrate made of Ti was not yet sufficient in a production process of the cylindrical ceramic target. In this method, heating temperature in bonding is low, and this is effective as a countermeasure for breakage in a bonding step. However, Ag paste is very hard after curing, and does not have ductility as possessed by indium solder. </p>
|
| 47 |
+
<p id="p-10" num="10">Consequently, the target does not act as a buffering material when the target is heated and expanded in sputtering, and there has been the possibility that the target cracks during sputtering.</p>
|
| 48 |
+
<heading id="h-5">SUMMARY OF THE INVENTION</heading>
|
| 49 |
+
<p id="p-11" num="11">Accordingly, one object of the present invention is to provide a hollow cylindrical ceramic sintered body having high density.</p>
|
| 50 |
+
<p id="p-12" num="12">Another object of the present invention is to provide a cylindrical ceramic sputtering target that can be bonded to a cylindrical substrate comprising any material, <boundary-data type="header">
|
| 51 |
+
<confidence value="8">3</confidence>
|
| 52 |
+
</boundary-data>
|
| 53 |
+
<page-break num="4"/>
|
| 54 |
+
and in particular, has high quality without cracks or breakage even in bonding to a cylindrical substrate comprising Cu. </p>
|
| 55 |
+
<p id="p-13" num="13">Still another object of the present invention is to provide a process for producing the ceramic sintered body.</p>
|
| 56 |
+
<p id="p-14" num="14">As a result of various investigations, it has been found that in sintering a hollow cylindrical ceramic sintered body having high density, when a cylindrical ceramic molding to be sintered is placed on a plate-like ceramic molding having a coefficient of sintering shrinkage similar to that of the cylindrical ceramic molding, and the resulting assembly is sintered, cracks or breakage generated during sintering disappear, and a hollow cylindrical ceramic sintered body having a relative density of 95% or higher can be obtained.</p>
|
| 57 |
+
<p id="p-15" num="15">It has further been found that in a cylindrical sputtering target comprising a target material comprising a hollow cylindrical ceramic sintered body, and a cylindrical substrate bonded to the target material, there is a correlation between a relative density of the hollow cylindrical ceramic sintered body which is a target material, and cracks or breakage generated in producing the cylindrical sputtering target, and cracks or breakage generated in the production can be prevented by that the relative density of the hollow cylindrical ceramic sintered body is 95% or higher.</p>
|
| 58 |
+
<p id="p-16" num="16">The present invention has been completed based on those findings.</p>
|
| 59 |
+
<p id="p-17" num="17">The hollow cylindrical ceramic <confidence value="7">s</confidence>
|
| 60 |
+
intered body according to the present invention is a hollow cylindrical ceramic sintered body for use as a target material in a cylindrical sputtering target, the sintered body having a relative density of 95% or higher. </p>
|
| 61 |
+
<p id="p-18" num="18">The process for producing the hollow cylindrical ceramic sintered body according to the present invention is that in sintering a hollow cylindrical ceramic sintered body having high density, a cylindrical ceramic molding is placed on a plate-like ceramic molding having a coefficient of sintering shrinkage similar to that of the cylindrical ceramic molding to be sintered, and the resulting assembly is sintered.</p>
|
| 62 |
+
<boundary-data type="header">
|
| 63 |
+
<confidence value="8">4</confidence>
|
| 64 |
+
</boundary-data>
|
| 65 |
+
<p id="p-19" num="19">
|
| 66 |
+
<page-break num="5"/>
|
| 67 |
+
The cylindrical sputtering target according to the present invention comprises a cylindrical substrate, and a target material comprising a hollow cylindrical ceramic sintered body, bonded to an outer surface of the cylindrical substrate, the ceramic target material having a relative density of 95% or higher. </p>
|
| 68 |
+
<p id="p-20" num="20">A low melting solder is preferably used to bond the target material comprising the hollow cylindrical ceramic sintered body to the cylindrical substrate. In particular, a low melting solder layer having a thickness of 0.5-1.5 mm is preferably formed between the outer surface of the cylindrical substrate and the hollow cylindrical ceramic sintered body.</p>
|
| 69 |
+
<p id="p-21" num="21">The cylindrical substrate that can be used in the cylindrical sputtering target of the present invention is a cylindrical substrate comprising Cu, Cu alloy or SUS.</p>
|
| 70 |
+
<p id="p-22" num="22">The material of the ceramic sintered body that can be used is an oxide comprising, as the main component, at least one element selected from the group consisting of In, Sn, Zn, Al, Ta, Nb and Ti.</p>
|
| 71 |
+
<p id="p-23" num="23">A low melting solder comprising indium as the main component means a low melting solder containing at least 80% by weight of indium, and the oxide comprising, as the main component, at least one element selected from the group consisting of In, Sn, Zn, Al, Ta, <confidence value="5">N</confidence>
|
| 72 |
+
b and Ti means an oxide containing 80% by weight or more of the sum of those elements in terms of their oxides. </p>
|
| 73 |
+
<heading id="h-6">BRIEF DESCRIPTION OF THE DRAWING</heading>
|
| 74 |
+
<p id="p-24" num="24">Fig. <confidence value="4">l</confidence>
|
| 75 |
+
A is a perspective view showing one example of configuration of a molding when dewaxing and sintering in the present invention. </p>
|
| 76 |
+
<p id="p-25" num="25">Fig. 2B is a plane view (seen from the upper) of the embodiment shown in Fig.</p>
|
| 77 |
+
<p id="p-26" num="26">
|
| 78 |
+
<confidence value="588">1A.</confidence>
|
| 79 |
+
</p>
|
| 80 |
+
<p id="p-27" num="27">In the drawings:</p>
|
| 81 |
+
<p id="p-28" num="28">1: <confidence value="8">h</confidence>
|
| 82 |
+
ollow cylindrical ceramic molding 2: plate-like ceramic molding <boundary-data type="header">
|
| 83 |
+
<confidence value="8">5</confidence>
|
| 84 |
+
</boundary-data>
|
| 85 |
+
<page-break num="6"/>
|
| 86 |
+
3: sintering center of molding </p>
|
| 87 |
+
<heading id="h-7">DETAILED DESCRI<confidence value="8">P</confidence>
|
| 88 |
+
TION OF THE INVENTION </heading>
|
| 89 |
+
<p id="p-29" num="29">The present invention is described in detail below.</p>
|
| 90 |
+
<p id="p-30" num="30">The ceramic sintered body of the present invention is not particularly limited.</p>
|
| 91 |
+
<p id="p-31" num="31">Examples of the sintered body that can be used include ITO (Indium Tin Oxide), AZO (Aluminum Zinc Oxide), IZO (Indium Zinc Oxide), Ta2<confidence value="54">05</confidence>
|
| 92 |
+
, Nb2<confidence value="5">0</confidence>
|
| 93 |
+
s and Ti<confidence value="488">O2.</confidence>
|
| 94 |
+
</p>
|
| 95 |
+
<p id="p-32" num="32">The process for producing the hollow cylindrical ceramic sintered body of the present invention is not particularly limited so long as a hollow cylindrical sintered body having a relative density of 95% or higher can be obtained. For example, the sintered body can be produced by the following process.</p>
|
| 96 |
+
<p id="p-33" num="33">When at least two kinds of compounds are used as a starting powder, those compounds are mixed to obtain a starting mixed powder. Mixing the starting powder can be conducted by, for example, ball mill, jet mill or cross mixer. Prior to mixing the starting powder, the starting powder is preferably subjected to pulverization and/or classification treatments. Applying the starting powder to such pulverization and/or classification treatments enables the starting powder to have a fine particle diameter, and therefore to mix uniformly. As a result, it is possible to prevent deformation, breakage or density unevenness of the sintered body caused by heterogeneity of composition in the sintered body, making it possible to easily obtain a high density sintered body. Where carbonates or the like other than oxides are used as the starting powder, the powder may be mixed, calcined and then subjected to decarbonation treatment or the like. Where a single kind of a compound is used as the starting powder, it is as a matter of course that the above mixing operation is not necessary. In the present invention, such a powder (single kind) is also called a starting mixed powder.</p>
|
| 97 |
+
<p id="p-34" num="34">The starting mixed powder thus obtained is molded by a molding method such as CIP (Cold Isotropic Pressing) method or centrifugal molding method to produce a <boundary-data type="header">
|
| 98 |
+
<confidence value="8">6</confidence>
|
| 99 |
+
</boundary-data>
|
| 100 |
+
<page-break num="7"/>
|
| 101 |
+
molding. Where a molding is produced with CIP method, a powder is charged in a cylindrical rubber mold having a core (core rod), and is molded using C<confidence value="5">I</confidence>
|
| 102 |
+
P apparatus under pressure of <part-num-ref name="core (core rod), and is molded using CIP apparatus under pressure of">500</part-num-ref>
|
| 103 |
+
kg/cm2 or higher. If required and necessary, the C<confidence value="5">I</confidence>
|
| 104 |
+
P can be conducted under further high pressure. Second time or subsequent C<confidence value="5">I</confidence>
|
| 105 |
+
P is conducted after placing the cylindrical molding in a thin rubber bag and then conducting vacuum deaeration. The pressure applied is a pressure higher than that in C<confidence value="4">I</confidence>
|
| 106 |
+
P treatment conducted immediately before, and is preferably 1,000 kg/cm2 or higher, more preferably 2,000 kg/cm<confidence value="5">2</confidence>
|
| 107 |
+
or higher. Where the powder has poor moldability, a binder comprising, as the main component, an organic compound such as paraffin or polyvinyl alcohol may be added to the powder, if required and necessary. A molding obtained by <confidence value="8">C</confidence>
|
| 108 |
+
IP method has poor shape accuracy. Therefore, such a molding may be subjected to grinding processing with lathe at the stage of a molding. </p>
|
| 109 |
+
<p id="p-35" num="35">Where a molding is produced by a centrifugal molding method, a binder, a dispersing agent and water are added to a sta<confidence value="8">r</confidence>
|
| 110 |
+
ting mixed powder, and the resulting mixture is mixed with ball mill or the like to prepare a molding slurry. To obtain further sufficient mixing effect, mixing time is preferably <part-num-ref name="molding slurry. To obtain further sufficient mixing effect, mixing time is preferably">3</part-num-ref>
|
| 111 |
+
hours or longer, more preferably <part-num-ref name="hours or longer, more preferably">5</part-num-ref>
|
| 112 |
+
hours or longer. </p>
|
| 113 |
+
<p id="p-36" num="36">Viscosity of the slurry is determined depending on the amounts of the above dispersing agent, binder and water added. To obtain a molding having high strength and to obtain good adhesion properties to a mold, the viscosity is preferably 100-5,000 centipoise, more preferably 500-2,500 centipoise.</p>
|
| 114 |
+
<p id="p-37" num="37">The slurry thus obtained is subjected to centrifugal molding. Degassing of the slurry is preferably conducted prior to molding. Degassing is conducted, for example, as follows. Polyalkylene glycol defoaming agent is added to the slurry, and the resulting mixture is subjected to degassing treatment under vacuum.</p>
|
| 115 |
+
<p id="p-38" num="38">A mold for use in the centrifugal molding is a cylindrical mold comprising a porous material. Porous resin or gypsum can be used as a material for the mold <boundary-data type="header">
|
| 116 |
+
<confidence value="8">7</confidence>
|
| 117 |
+
</boundary-data>
|
| 118 |
+
<page-break num="8"/>
|
| 119 |
+
without any limitation. The centrifugal molding is a molding method comprising placing a slurry in a cylindrical porous mold, and rotating the mold at high speed to absorb water in the slurry in the porous mold, thereby forming a molding. This method is suitable to obtain a cylindrical molding having high shape accuracy. Outer diameter of a cylindrical molding is determined by an inner diameter of the cylindrical porous mold. Thickness of the molding can easily be adjusted to an optional thickness by controlling the amount of slurry introduced. The number of revolution in such a case is preferably 500-3,000 rpm from the standpoint of productivity. </p>
|
| 120 |
+
<p id="p-39" num="39">The molding produced by a centrifugal molding method and dried can further be subjected to compaction treatment by CIP, if desired and necessary. To obtain sufficient compaction effect, pressure in such CIP is preferably 1,000 kg/cm2 or higher, more preferably 2,000 kg/cm<confidence value="5">2</confidence>
|
| 121 |
+
or higher. </p>
|
| 122 |
+
<p id="p-40" num="40">To remove water and organic materials such as binder remaining in a molding produced by CIP method or a molding produced by centrifugal molding method, the molding is subjected to dewaxing treatment at a temperature of 300-500<confidence value="288">°C.</confidence>
|
| 123 |
+
</p>
|
| 124 |
+
<p id="p-41" num="41">Temperature rising rate in such a dewaxing treatment is preferably 10<confidence value="2">*</confidence>
|
| 125 |
+
C/hr or lower, more preferably 5<confidence value="2">*</confidence>
|
| 126 |
+
C/hr or lower, to prevent cracks in the course that a dispersing agent and a binder gasify. Where the molding is produced by CIP method, if an organic material, particularly a binder, is not added, dewaxing treatment may be omitted. </p>
|
| 127 |
+
<p id="p-42" num="42">The molding thus obtained is sintered in a sintering furnace to produce a ceramic sintered body. The sintering is conducted in a manner such that the molding is placed on a plate-like ceramic molding having a coefficient of sintering shrinkage similar to that of a cylindrical ceramic molding. Specifically, a cylindrical ceramic molding is placed on a plate-like ceramic molding such that a circular cross-section of the cylindrical ceramic molding contacts with a plate face of the plate-like ceramic molding, as shown in Fig. <confidence value="4">l</confidence>
|
| 128 |
+
A. In particular, the molding is preferably placed such that the center (sintering center) of the cylindrical ceramic molding and the center (sintering <boundary-data type="header">
|
| 129 |
+
<confidence value="8">8</confidence>
|
| 130 |
+
</boundary-data>
|
| 131 |
+
<page-break num="9"/>
|
| 132 |
+
center) of the plate-like ceramic molding overlap, as shown in Fig. <confidence value="5">1</confidence>
|
| 133 |
+
B. Thus, sintering is conducted in a manner such that the cylindrical ceramic molding is placed on the plate-like ceramic molding having a coefficient of shrinkage similar to that of the cylindrical ceramic molding, and this makes it possible to easily prevent breakage or deformation of a sintered body due to sintering shrinkage. Difference between the coefficient of sintering shrinkage of the cylindrical ceramic molding (i.e., coefficient of shrinkage in a radius direction on the circular cross-section) and the coefficient of shrinkage in center direction on a plate face on the plate-like ceramic molding is preferably within <confidence value="5">±</confidence>
|
| 134 |
+
1%, more preferably <confidence value="5">±</confidence>
|
| 135 |
+
0.5%. Any material can be used as the material for a ceramic used as a plate-like ceramic molding so long as the coefficient of sintering shrinkage of a molding can be adjusted to the above range by granulation of powder, molding conditions or the like. If the diameter of a cylindrical shape is large, it is preferable that the coefficient of shrinkage is adjusted further strictly. Use of the same material as that used in the cylindrical ceramic molding enables the coefficient of shrinkage to easily adjust. The plate-like ceramic molding is preferably a square flat plate-like ceramic molding as shown in Fig. 1. However, a ceramic molding having a disc shape may be used, and a ceramic molding having polygon shape or a rectangular shape may also be used. Thus, a sintering method using ceramic moldings having similar coefficient of shrinkage does not require any specific sintering tool, and is particularly effective in a material requiring high sintering temperature or a material having high density. </p>
|
| 136 |
+
<p id="p-43" num="43">To decrease friction in sintering and shrinking a molding, a powder is spread between the plate-like ceramic molding and a furnace floor (setter), and between the plate-like ceramic molding and the cylindrical ceramic <confidence value="8">m</confidence>
|
| 137 |
+
olding. The powder used is not particularly limited so long as it is not reactive with a ceramic material. For example, alumina powder is preferably used in producing ITO sintered body. In order that a molding shrinks uniformly, the powder such as alumina powder has preferably a <boundary-data type="header">
|
| 138 |
+
<confidence value="8">9</confidence>
|
| 139 |
+
</boundary-data>
|
| 140 |
+
<page-break num="10"/>
|
| 141 |
+
shape close to a sphere. The powder further preferably has a particle diameter of 100-1,000 <confidence value="268">pm.</confidence>
|
| 142 |
+
</p>
|
| 143 |
+
<p id="p-44" num="44">Sintering conditions (sintering temperature, temperature rising rate, temperature lowering rate, etc.) in such a case vary depending on the kind of the ceramic material used. For example, in the case of ITO, the sintering temperature is preferably 1,450-1,650<confidence value="2">°</confidence>
|
| 144 |
+
C at the temperature of which solid solubilization of tin oxide into indium oxide is promoted. If the sintering temperature is lower than 1,450<confidence value="2">*</confidence>
|
| 145 |
+
C, sintering into ITO is not sufficient, and a sintered body obtained has poor strength. On the other hand, if the sintering temperature exceeds 1,650<confidence value="2">°</confidence>
|
| 146 |
+
C, indium oxide or tin oxide remarkably evaporates from ITO sintered particles, and this is a factor causing problems such as compositional deviation. To obtain a sufficient rising effect of density, the molding is desirably maintained at the sintering temperature for <part-num-ref name="sintering temperature for">5</part-num-ref>
|
| 147 |
+
hours or longer, preferably 5-30 hours. The temperature rising rate up to the sintering temperature is preferably 20-100<confidence value="2">*</confidence>
|
| 148 |
+
C/hr, considering uniform shrinkage of the molding due to sintering. </p>
|
| 149 |
+
<p id="p-45" num="45">The temperature lowering rate up to room temperature after maintaining at the sintering temperature is preferably 100<confidence value="2">*</confidence>
|
| 150 |
+
C/hr or lower from the standpoint of absorbing thermal shock to a sintered body and preventing warpage and cracks. </p>
|
| 151 |
+
<p id="p-46" num="46">The above production process makes it possible to obtain a hollow cylindrical ceramic sintered body having a relative density of 95% or higher, preferably 98% or higher, more preferably 99% or higher.</p>
|
| 152 |
+
<p id="p-47" num="47">In particular, according to the production process of the hollow cylindrical ceramic sintered body of the present invention, the hollow cylindrical ceramic sintered body having a relative density of 99.7% or higher can be obtained without causing breakage or cracks by optimizing starting mixed powder, molding conditions, sintering conditions and the like, even in the case of an oxide sintered body of indium and tin.</p>
|
| 153 |
+
<p id="p-48" num="48">Thus, the production process according to the present invention makes it possible to obtain a cylindrical sputtering target having a target material comprising ITO sintered <boundary-data type="header">
|
| 154 |
+
<confidence value="88">10</confidence>
|
| 155 |
+
</boundary-data>
|
| 156 |
+
<page-break num="11"/>
|
| 157 |
+
body having a relative density of 99.7% or higher, which has not been obtained in the conventional process. In the conventional flat plate-like ITO sputtering target, it has been required for the target material to have a relative density of 99.7% or higher in order to reduce nodule. Therefore, the cylindrical sputtering target having a target material comprising an oxide sintered body comprising indium and tin, having a relative density of 99.7% or higher can suitably be used as a low nodule ITO sputtering target. </p>
|
| 158 |
+
<p id="p-49" num="49">The content of indium and tin in the oxide sintered body of indium and tin is preferably 95:5 to 80:20 in terms of weight ratio of indium oxide to tin oxide (indium oxide <confidence value="5">:</confidence>
|
| 159 |
+
tin oxide) The sintered body obtained by the production process of the hollow cylindrical ceramic sintered body of the present invention involves slight deformation in the sintering step. The sintered body is preferably subjected to grinding processing to obtain a hollow cylindrical sputtering target material. Processing to a cylindrical shape is generally conducted using a lathe. However, a ceramic sintered body is brittle, and hence breakage or strain may occur in fixing the same to a machine tool. Thus, there is the possibility that processing accuracy deteriorates. Therefore, in processing the sintered body, it is preferable that jig is used or processing work is designed such that eccentricity (deviation between center of outer diameter and center of inner diameter) is preferably 0.2 mm or smaller, more preferably 0.1 mm or smaller. This removes ununiform expansion due to heating in bonding the sintered body to a cylindrical substrate, thereby suppressing occurrence of breakage. </p>
|
| 160 |
+
<p id="p-50" num="50">The target thus grinding processed is bonded to a cylindrical substrate. In the present invention, material for the cylindrical substrate is not particularly limited, and other than Ti, Mo, SUS or the like having a coefficient of thermal expansion similar to that of ceramics such as ITO can also be used. Further, non-oxygen copper or copper alloys such as phosphorus bronze, conventionally used in a flat plate-like target, can be used. In the present invention, the target material is bonded to a cylindrical substrate <boundary-data type="header">
|
| 161 |
+
<confidence value="88">11</confidence>
|
| 162 |
+
</boundary-data>
|
| 163 |
+
<page-break num="12"/>
|
| 164 |
+
using a low melting solder. The low melting solder used is preferably a low melting solder comprising indium as the main component <part-num-ref name="main component">(80</part-num-ref>
|
| 165 |
+
wt% or higher). The indium solder is widely used in a flat plate-like target, and indium is rich in ductility. </p>
|
| 166 |
+
<p id="p-51" num="51">Therefore, the indium solder has the effect to absorb strain such as thermal expansion between the target material heated during sputtering and the cooled substrate. Further, when the target material is bonded to the substrate with the low melting solder, the target material can easily be peeled from the used target. Thus, reuse of the cylindrical substrate and recycle of the target material are easy.</p>
|
| 167 |
+
<p id="p-52" num="52">A method of bonding the target material to the cylindrical substrate is not particularly limited so long as the low melting solder layer having a thickness of 0.5-1.5 mm, preferably 0.5-1.0 mm, can be formed between the outer surface of the cylindrical substrate and the target material comprising the hollow cylindrical ceramic sintered body. The bonding method is conducted, for example, as follows.</p>
|
| 168 |
+
<p id="p-53" num="53">The cylindrical target material is processed to have an inner diameter of 1-3 mm, preferably 1-2 mm, smaller than the outer diameter of the cylindrical substrate to which the cylindrical target material is bonded. Portion other than the bonded portion on the target material and the substrate is subjected to a masking treatment using, for example, a heat-resistant film. Indium-based low melting solder is applied by, for example, a thermal spray method to the inner surface of the target material at the same thickness as a clearance (0.5-1.5 mm, preferably 0.5-1.0 mm) to the substrate. The target material is placed in an oven in a state that a ribbon type resistance heater is wound around the target material, and heated therein at a temperature (for example, 1<confidence value="882">50*</confidence>
|
| 169 |
+
C in the case of indium) slightly lower than the melting point of the indium-based low melting solder (for example, 156.6<confidence value="2">°</confidence>
|
| 170 |
+
C in the case of indium). Similarly, the indium-based low melting solder is applied to the outer surface of the cylindrical substrate, and the substrate is placed in an oven and heated therein at a temperature of 80-120<confidence value="2">*</confidence>
|
| 171 |
+
C. Prior to applying the low melting solder, undercoat treatment such as UV irradiation, Ni plating or <boundary-data type="header">
|
| 172 |
+
<confidence value="88">12</confidence>
|
| 173 |
+
</boundary-data>
|
| 174 |
+
<page-break num="13"/>
|
| 175 |
+
deposition may be applied to improve wettablity of the solder. </p>
|
| 176 |
+
<p id="p-54" num="54">The ribbon type resistance heater wound around the cylindrical target material is connected to power source to heat the target material. The top portion of the cylindrical substrate is inserted into the hollow portion of the target material, and while elevating the heating temperature with the ribbon type resistance heater, the whole cylindrical substrate is pressurized and inserted into the hollow portion of the target material. Those operations are preferably conducted in an atmosphere heated to about 80-120<confidence value="2">*</confidence>
|
| 177 |
+
C, but can be<confidence value="2">~</confidence>
|
| 178 |
+
conducted at room temperature. When conducted at room temperature, the operation should be conducted smoothly for a short period of time as compared with the case of conducting at a heated atmosphere. Thus, attention should be paid to, for example, set somewhat higher temperature by heater. Pressure applied to insert the cylindrical substrate into the hollow portion of the target material is preferably 0.1 kg/cm2 or lower, more preferably 0.01 kg/cm2, to the unit bonded area when the cylindrical substrate and the target material are finally bonded at the prescribed position. If the pressure is too high, the cylindrical substrate is inserted by such pressure prior to softening the low melting solder. As a result, stress may remain in the bonded portion or bonding ratio between the target material and the substrate may decrease. The "pressure" used herein means pressure including the self weight of the cylindrical substrate. Means for pressurization is not particularly limited. There is, for example, a pressurizing method such as pressurization with a pressurizing machine such as oil pressure press, or a weight. Thus, lowering the heating temperature to the cylindrical substrate has the effect to suppress cracks of the target material due to thermal expansion of the substrate. The substrate comprises a metal. Therefore, there is less possibility that cracks or the like occur in heat shock in the heating operation of the low melting solder. To match the center of the hollow cylindrical target material and the center of the substrate, a plurality of spacers having a thickness smaller than a clearance between the target material and the substrate can be inserted. </p>
|
| 179 |
+
<boundary-data type="header">
|
| 180 |
+
<confidence value="88">13</confidence>
|
| 181 |
+
</boundary-data>
|
| 182 |
+
<p id="p-55" num="55">
|
| 183 |
+
<page-break num="14"/>
|
| 184 |
+
The spacer can be used without consideration of its direction. Therefore, a wire type spacer is preferably used. In order to achieve both the center-matching accuracy and the operating efficiency, the thickness of spacer is preferably about 80% of the clearance. </p>
|
| 185 |
+
<p id="p-56" num="56">By the above, the low melting solder layer having a thickness of 0.5-1.5 mm, preferably 0.5-1.0 mm, can be formed between the outer surface of the cylindrical substrate and the target material comprising a hollow cylindrical ceramic sintered body, and the formation of such a layer can effectively absorb strain due to thermal expansion or the like in the bonding step, thereby preventing occurrence of cracks or breakage.</p>
|
| 186 |
+
<p id="p-57" num="57">According to the present invention, a high density hollow cylindrical ceramic sintered body having a relative density of 95% or higher can easily be produced.</p>
|
| 187 |
+
<p id="p-58" num="58">Further, by using such a ceramic sintered body as a target material, occurrence of cracks or breakage in the step of bonding the target material to the cylindrical substrate can effectively be prevented. In addition, by forming a low melting solder layer having a thickness of 0.5-1.5 mm between the outer surface of the cylindrical substrate and the target material comprising a hollow cylindrical ceramic sintered body, and bonding the substrate and the ceramic sintered body, it is possible to effectively absorb strain due to thermal expansion or the like. In combination with use of a high density target material having a relative density of 95% or higher, it is possible to further effectively prevent occurrence of cracks or breakage in the b<confidence value="8">o</confidence>
|
| 188 |
+
nding step. In addition to this, even in the use under high electric power density, it is possible to provide an excellent cylindrical sputtering target without occurrence of cracks or breakage. In particular, according to the present invention, it is possible to use a cylindrical substrate comprising various materials such as Cu, Cu alloys or SUS, and it is also possible to provide a cylindrical sputtering target having excellent cooling efficiency at low cost. </p>
|
| 189 |
+
<p id="p-59" num="59">Further, in the cylindrical sputtering target of the present invention, the low melting solder layer having a uniform thickness of 0.5-1.5 mm is formed between the outer surface of the cylindrical substrate and the target material comprising a hollow <boundary-data type="header">
|
| 190 |
+
<confidence value="88">14</confidence>
|
| 191 |
+
</boundary-data>
|
| 192 |
+
<page-break num="15"/>
|
| 193 |
+
cylindrical ceramic sintered body. As a result, the target material can easily be peeled from the used target. This enables the cylindrical substrate to reutilize easily and also the target material to recycle easily. </p>
|
| 194 |
+
<p id="p-60" num="60">The present invention will be described in more detail by reference to the following Examples, but it should be understood that the invention is not construed as being limited thereto.</p>
|
| 195 |
+
<p id="p-61" num="61">EXAMPLE 1 Indium oxide having a 50% diameter (a particle diameter at 50% volume percent in the cumulative curve of the particle size distribution; hereinafter the same) of 0.54 <confidence value="5">p</confidence>
|
| 196 |
+
m and tin oxide having the diameter of 1.03 m were mixed with a dry ball mill for <part-num-ref name="dry ball mill for">16</part-num-ref>
|
| 197 |
+
hours such that the compositional propo<confidence value="8">r</confidence>
|
| 198 |
+
tion is indium oxide <confidence value="5">:</confidence>
|
| 199 |
+
tin oxide = 1:1 to prepare ITO mixed powder. The ITO mixed powder was taken out of a vessel, and 1.1% of a polycarboxylic acid type dispersing agent (solid content of the agent to the amount of the ITO mixed powder is 1.1%), 1.0% of a polyacrylic acid type binder (solid content of the binder to the amount of the ITO mixed powder is 1.0%), and 25.5% of ion-exchanged water (to the amount of the ITO mixed powder) were added to the powder. The resulting mixture was mixed with a ball mill for <part-num-ref name="ball mill for">16</part-num-ref>
|
| 200 |
+
hours to obtain a molding slurry. Viscosity of this slurry was measured, and it was found to be <part-num-ref name="molding slurry. Viscosity of this slurry was measured, and it was found to be">680</part-num-ref>
|
| 201 |
+
centipoise. </p>
|
| 202 |
+
<p id="p-62" num="62">A polyalkylene glycol type defoaming agent was added to the slurry, and degassing treatment was conducted in vacuo. The slurry was poured into a cylindrical porous mold for centrifugal molding, made of a resin and having an inner diameter of 125 mm and a length of 200 mm, and centrifugal molding was conducted with the number of revolution of 1,200 rpm. The resulting molding was dried, and then the dispersing agent and binder remained in the molding were removed. For the purpose of sintering, the molding was placed on a flat plate-like ITO molding having a size of <part-num-ref name="size of">130</part-num-ref>
|
| 203 |
+
x <part-num-ref name="x">130</part-num-ref>
|
| 204 |
+
x 10 mm so as to match each center. The resulting assembly was subjected <boundary-data type="header">
|
| 205 |
+
<confidence value="88">15</confidence>
|
| 206 |
+
</boundary-data>
|
| 207 |
+
<page-break num="16"/>
|
| 208 |
+
to dewaxing and sintering in a sintering furnace having oxygen flow atmosphere under the following conditions. </p>
|
| 209 |
+
<p id="p-63" num="63">Dewaxing conditions Dewaxing temperature: 450<confidence value="28">*C</confidence>
|
| 210 |
+
Temperature rising rate: 5<confidence value="2">*</confidence>
|
| 211 |
+
C/hr Holding time: None Sintering Conditions Charge weight/oxygen flow rate: 1.00 <confidence value="222222222222">kg.min/liter</confidence>
|
| 212 |
+
Temperature rising rate: 5<confidence value="828688">0*C/hr</confidence>
|
| 213 |
+
Sintering temperature: 1,450<confidence value="28">*C</confidence>
|
| 214 |
+
Sintering time: 5 hrs Temperature lowering rate: 1<confidence value="882">00*</confidence>
|
| 215 |
+
C/hr Density of <part-num-ref name="hrs Temperature lowering rate: 100*C/hr Density of">10</part-num-ref>
|
| 216 |
+
sintered bodies obtained was measured, and it was found to be 6.85-6.89 g/cm3 (relative density: 95.7-96.3%). The density was measured with Archimedean method according to JIS R1634 (1998). Weighted average value, 7.156 g/cm3, calculated from mixing ratio of indium oxide and tin oxide was used as true density of ITO sintered body. </p>
|
| 217 |
+
<p id="p-64" num="64">The sintered body obtained was grinding processed to a size having an outer diameter of 98 mm, an inner diameter of 78 mm and a length of 150 mm to prepare a target material. In this processing, the inside (inner diameter) of the sintered body was first processed using a lathe, a tapered fixing jig (having a hole for matching center position) was put in the processed inside of t<confidence value="5">h</confidence>
|
| 218 |
+
e sintered body, both edges of the fixing jig were fixed with a lathe, and the outside (outer diameter) of the sintered body was processed. In this case, eccentricity (deviation in centers between the inner diameter and the outer diameter) of the cylindrical target material was 0.2 mm or smaller in all <part-num-ref name="cylindrical target material was 0.2 mm or smaller in all">10</part-num-ref>
|
| 219 |
+
samples. </p>
|
| 220 |
+
<p id="p-65" num="65">The portion of the cylindrical target material other than the portion to be bonded <boundary-data type="header">
|
| 221 |
+
<confidence value="88">16</confidence>
|
| 222 |
+
</boundary-data>
|
| 223 |
+
<page-break num="17"/>
|
| 224 |
+
to a cylindrical substrate was masked with <confidence value="6">a</confidence>
|
| 225 |
+
heat-resistant tape. Six Cu wires each having a diameter of 0.8 mm were arranged to the inner surface of the target material in a length direction, and indium was then thermal sprayed to the inner surface of the target material at a thickness of about 1 mm so as to cover the wires. The target material was placed and heated in a 1<confidence value="882">50*</confidence>
|
| 226 |
+
C oven in a state that a ribbon type resistance heater was wound around the target material. </p>
|
| 227 |
+
<p id="p-66" num="66">A cylindrical substrate was used, which is made of Cu, and has an outer diameter of 76 mm, an inner diameter of 66 mm and a length of <part-num-ref name="length of">150</part-num-ref>
|
| 228 |
+
mm. The portion of the substrate other than the portion to be bonded to the sintered body was masked with a heat-resistant tape, and the substrate was coated with indium using an ultrasonic soldering bit, placed in a 100<confidence value="2">"</confidence>
|
| 229 |
+
C oven, and heated therein. </p>
|
| 230 |
+
<p id="p-67" num="67">The target material was taken out of the 150<confidence value="2">*</confidence>
|
| 231 |
+
C oven, and then placed in a 100<confidence value="28">*C</confidence>
|
| 232 |
+
oven. The ribbon type resistance heater was connected to a slide regulator (slidax) to heat the target material. The cylindrical substrate was inserted into the target material from the upper thereof, and was supported with a jig. Heating temperature was elevated with a ribbon type resistance heater. When one/fourth of the cylindrical substrate was inserted in the target material by the self weight of the substrate, 1.5 kg load was placed on the substrate to completely insert the cylindrical substrate into the target material. The assembly was gradually cooled, and the heat<confidence value="1">-</confidence>
|
| 233 |
+
resistant tape was peeled to confirm the target material. As a result, breakage was observed in three target materials often target materials. </p>
|
| 234 |
+
<p id="p-68" num="68">EXAMPLE 2 Indium oxide powder and tin oxide powder each were pulverized with a dry ball mill for <part-num-ref name="dry ball mill for">48</part-num-ref>
|
| 235 |
+
hours. The tin oxide powder was further subjected to dry jet mill pulverization. 50% diameters of indium oxide powder and tin oxide powder at this stage were 0.46 m and 0.28 <confidence value="5">p</confidence>
|
| 236 |
+
m, respectively. Those powders were dry mixed in the same manner as in Example <part-num-ref name="same manner as in Example">1,</part-num-ref>
|
| 237 |
+
and a slurry was prepared using the resulting mixture in <boundary-data type="header">
|
| 238 |
+
<confidence value="88">17</confidence>
|
| 239 |
+
</boundary-data>
|
| 240 |
+
<page-break num="18"/>
|
| 241 |
+
the same manner as in Example <part-num-ref name="same manner as in Example">1.</part-num-ref>
|
| 242 |
+
As a result of measurement of viscosity of this slurry, it was found to be <part-num-ref name="result of measurement of viscosity of this slurry, it was found to be">870</part-num-ref>
|
| 243 |
+
centipoise. </p>
|
| 244 |
+
<p id="p-69" num="69">Centrifugal molding was conducted and the resulting molding was dried, in the same manner as in Example <part-num-ref name="same manner as in Example">1.</part-num-ref>
|
| 245 |
+
C<confidence value="5">I</confidence>
|
| 246 |
+
P treatment was applied to the molding under pressure of <part-num-ref name="molding under pressure of">3</part-num-ref>
|
| 247 |
+
<confidence value="222222">ton/cm</confidence>
|
| 248 |
+
2. Dewaxing and sintering were conducted in the same manner as in Example <part-num-ref name="same manner as in Example">1</part-num-ref>
|
| 249 |
+
except for changing the sintering conditions as follows, thereby preparing ten sintered bodies. </p>
|
| 250 |
+
<p id="p-70" num="70">Sintering Conditions Charge weight/oxygen flow rate: 0.38 kg<confidence value="2">-</confidence>
|
| 251 |
+
min<confidence value="5">/</confidence>
|
| 252 |
+
liter Temperature rising rate: 50<confidence value="2">*</confidence>
|
| 253 |
+
C/hr Sintering temperature: 1,600<confidence value="28">°C</confidence>
|
| 254 |
+
Sintering time: 5 hrs Temperature lowering rate: 1<confidence value="882">00*</confidence>
|
| 255 |
+
C/hr As a result of measurement of density of thus obtained ten sintered bodies in the same manner as in Example <part-num-ref name="same manner as in Example">1,</part-num-ref>
|
| 256 |
+
it was found to be all 7.14 g/cm3 (relative density: </p>
|
| 257 |
+
<p id="p-71" num="71">99.8%).</p>
|
| 258 |
+
<p id="p-72" num="72">The sintered bodies were grinding processed in the same manner as in Example <part-num-ref name="same manner as in Example">1.</part-num-ref>
|
| 259 |
+
The eccentricity was all 0.1 mm or smaller. Each sintered body was bonded to a cylindrical substrate made of Cu in the same manner as in Example <part-num-ref name="same manner as in Example">1.</part-num-ref>
|
| 260 |
+
No breakage was observed in all ten sintered bodies. </p>
|
| 261 |
+
<p id="p-73" num="73">EXAMPLE 3 ITO mixed powder was prepared in the same manner as in Example <part-num-ref name="same manner as in Example">1.</part-num-ref>
|
| 262 |
+
Paraffin as a binder was added to the powder in an amount of 1.5% (based on the amount of ITO mixed powder). </p>
|
| 263 |
+
<p id="p-74" num="74">A cylindrical urethane rubber mold having an inner diameter of 140 mm (wall thickness: <part-num-ref name="mm (wall thickness:">7</part-num-ref>
|
| 264 |
+
mm) and a length of 220 mm, having closing lids at the upper and the lower thereof, and containing a columnar core (shaft) was filled with the powder obtained <boundary-data type="header">
|
| 265 |
+
<confidence value="88">18</confidence>
|
| 266 |
+
</boundary-data>
|
| 267 |
+
<page-break num="19"/>
|
| 268 |
+
above while tapping. The rubber mold was closed, and CIP treatment was conducted under a pressure of <part-num-ref name="pressure of">3</part-num-ref>
|
| 269 |
+
ton/cm<confidence value="5">2</confidence>
|
| 270 |
+
to obtain a molding. This molding was processed with a lathe to an outer diameter of 121 mm, an inner diameter of 93 mm and a length of <part-num-ref name="length of">200</part-num-ref>
|
| 271 |
+
mm. Dewaxing and sintering were conducted in the same manner as in Example <part-num-ref name="same manner as in Example">1</part-num-ref>
|
| 272 |
+
except for changing the sintering conditions as follows, thereby preparing ten sintered bodies. </p>
|
| 273 |
+
<p id="p-75" num="75">Sintering Conditions Charge weight/oxygen flow rate: 1.00 kg<confidence value="2">-</confidence>
|
| 274 |
+
min/liter Temperature rising rate: 50<confidence value="2">*</confidence>
|
| 275 |
+
C/hr Sintering temperature: <confidence value="5">1</confidence>
|
| 276 |
+
,500<confidence value="28">°C</confidence>
|
| 277 |
+
Sintering time: 5 hrs Temperature lowering rate: <part-num-ref name="hrs Temperature lowering rate:">1<confidence value="66">00</confidence>
|
| 278 |
+
</part-num-ref>
|
| 279 |
+
<confidence value="8688">C/hr</confidence>
|
| 280 |
+
As a result of measurement of density of the thus obtained ten sintered bodies in the same manner as in Example <part-num-ref name="same manner as in Example">1,</part-num-ref>
|
| 281 |
+
it was found to be 7.03-7.05 g/cm3 (relative density: </p>
|
| 282 |
+
<p id="p-76" num="76">98.2-98.5%).</p>
|
| 283 |
+
<p id="p-77" num="77">The sintered bodies obtained were grinding processed in the same manner as in Example <part-num-ref name="same manner as in Example">
|
| 284 |
+
<confidence value="6">1</confidence>
|
| 285 |
+
</part-num-ref>
|
| 286 |
+
to an outer diameter of 97 mm, an inner diameter of <confidence value="88">78</confidence>
|
| 287 |
+
mm and a length of <part-num-ref name="length of">150.</part-num-ref>
|
| 288 |
+
The eccentricity was all 0.1 mm or smaller. Each sintered body was bonded to a cylindrical substrate made of Cu in the same manner as in Example <part-num-ref name="same manner as in Example">1.</part-num-ref>
|
| 289 |
+
No breakage was observed in all ten sintered bodies. </p>
|
| 290 |
+
<p id="p-78" num="78">EXAMPLE 4 Ten sintered bodies were prepared in the same manner as in Example <part-num-ref name="same manner as in Example">3.</part-num-ref>
|
| 291 |
+
</p>
|
| 292 |
+
<p id="p-79" num="79">The sintered bodies obtained were grinding processed in the same manner as in Example <part-num-ref name="same manner as in Example">1</part-num-ref>
|
| 293 |
+
to an outer diameter of 97 mm, an inner diameter of <part-num-ref name="inner diameter of">78</part-num-ref>
|
| 294 |
+
and a length of 150 mm to obtain target materials. In this case, the outer diameter was first processed using a lathe. Thereafter, the outer diameter was fixed with the lathe, and the inner diameter was processed. The eccentricity was 0.8-0.3 mm. Each sintered body was <boundary-data type="header">
|
| 295 |
+
<confidence value="88">19</confidence>
|
| 296 |
+
</boundary-data>
|
| 297 |
+
<page-break num="20"/>
|
| 298 |
+
bonded to a cylindrical substrate made of Cu in the same manner as in Example <part-num-ref name="same manner as in Example">1.</part-num-ref>
|
| 299 |
+
</p>
|
| 300 |
+
<p id="p-80" num="80">Breakage was observed in two sintered bodies often sintered bodies.</p>
|
| 301 |
+
<p id="p-81" num="81">EXAMPLE 5 Zinc oxide having a 50% diameter of 0.78 m and aluminum oxide having a 50% diameter of 0.45 <confidence value="5">p</confidence>
|
| 302 |
+
m were mixed with a dry ball mill for <part-num-ref name="dry ball mill for">16</part-num-ref>
|
| 303 |
+
hours in a proportion of zinc oxide <confidence value="5">:</confidence>
|
| 304 |
+
aluminum oxide = <part-num-ref name="proportion of zinc oxide :aluminum oxide =">98</part-num-ref>
|
| 305 |
+
<confidence value="8">:</confidence>
|
| 306 |
+
<part-num-ref name=":">2</part-num-ref>
|
| 307 |
+
(wt%) to prepare AZO mixed powder. </p>
|
| 308 |
+
<p id="p-82" num="82">Paraffin as a binder was added to the mixed powder in an amount of 1.5% (to the amount of AZO mixed powder).</p>
|
| 309 |
+
<p id="p-83" num="83">A molding was prepared and processed in the same manner as in Example <part-num-ref name="same manner as in Example">3.</part-num-ref>
|
| 310 |
+
</p>
|
| 311 |
+
<p id="p-84" num="84">To remove a dispersing agent and a binder remained in the molding and sintering the molding, the molding was placed on a plate-like AZO molding having a size of <part-num-ref name="size of">130</part-num-ref>
|
| 312 |
+
x <part-num-ref name="x">130</part-num-ref>
|
| 313 |
+
x 10 mm so as to coincide the center of the molding and the center of AZO molding, and was subjected to dewaxing and sintering in an atmospheric sintering furnace under the following conditions. Thus, ten sintered bodies were prepared. </p>
|
| 314 |
+
<p id="p-85" num="85">Dewaxing conditions Dewaxing temperature: 450<confidence value="28">°C</confidence>
|
| 315 |
+
Temperature rising rate: 5<confidence value="28688">*C/hr</confidence>
|
| 316 |
+
Holding time: None Sintering Conditions Temperature rising rate: 50<confidence value="2">*</confidence>
|
| 317 |
+
C/hr Sintering temperature: 1,350<confidence value="28">*C</confidence>
|
| 318 |
+
Sintering time: 5 hrs Temperature lowering rate: 1<confidence value="882">00*</confidence>
|
| 319 |
+
C/hr As a result of measuring density of each of the thus obtained ten sintered bodies in the same manner as in Example <part-num-ref name="same manner as in Example">1,</part-num-ref>
|
| 320 |
+
it was found to be 5.46-5.48 g/cm3 (relative density: 98.2-98.6%). Weighted average value 5.560 g/cm3 calculated from mixing ratio of zinc oxide and aluminum oxide was used as a true density of the AZO sintered <boundary-data type="header">
|
| 321 |
+
<confidence value="88">20</confidence>
|
| 322 |
+
</boundary-data>
|
| 323 |
+
<page-break num="21"/>
|
| 324 |
+
body. </p>
|
| 325 |
+
<p id="p-86" num="86">The sintered body obtained was grinding processed into a size having an outer diameter of 98 mm, an inner diameter of 78 mm and a length of 150 mm in the same manner as in Example <part-num-ref name="same manner as in Example">1</part-num-ref>
|
| 326 |
+
to prepare a target material. The eccentricity between the inner diameter and the outer diameter of the cylindrical target material was all 0.1 mm or smaller. Each sintered body was bonded to a cylindrical substrate made of Cu in the same manner as in Example <part-num-ref name="same manner as in Example">1.</part-num-ref>
|
| 327 |
+
No breakage was observed in all ten sintered bodies. </p>
|
| 328 |
+
<p id="p-87" num="87">EXAMPLE 6 Indium oxide having a 50% diameter of 0.54 m and zin<confidence value="8">c</confidence>
|
| 329 |
+
oxide having a 50% diameter of 0.78 m were mixed with a dry ball mill for <part-num-ref name="dry ball mill for">16</part-num-ref>
|
| 330 |
+
hours in a proportion of indium oxide <confidence value="5">:</confidence>
|
| 331 |
+
zinc oxide = <part-num-ref name="proportion of indium oxide :zinc oxide =">90</part-num-ref>
|
| 332 |
+
<confidence value="8">:</confidence>
|
| 333 |
+
<part-num-ref name=":">10</part-num-ref>
|
| 334 |
+
(wt%) to prepare IZO mixed powder as a binder. </p>
|
| 335 |
+
<p id="p-88" num="88">Paraffin was added to the mixed powder in an amount of 1.5% (to the amount of IZO mixed powder).</p>
|
| 336 |
+
<p id="p-89" num="89">A molding was prepared and processed in the same manner as in Example <part-num-ref name="same manner as in Example">3.</part-num-ref>
|
| 337 |
+
</p>
|
| 338 |
+
<p id="p-90" num="90">To remove a dispersing agent and a binder remained in the molding and sintering the molding, the molding was placed on a plate-like IZO molding having a size of <part-num-ref name="size of">130</part-num-ref>
|
| 339 |
+
x <part-num-ref name="x">130</part-num-ref>
|
| 340 |
+
x 10 mm so as to coincide the center of the molding and the center of IZO molding, and was subjected to dewaxing and sintering in an atmospheric sintering furnace under the following conditions. Thus, ten sintered bodies were prepared. </p>
|
| 341 |
+
<p id="p-91" num="91">Dewaxing conditions Dewaxing temperature: 450<confidence value="28">°C</confidence>
|
| 342 |
+
Temperature rising rate: 5<confidence value="28688">"C/hr</confidence>
|
| 343 |
+
Holding time: None Sintering Conditions Temperature rising rate: 50<confidence value="2">*</confidence>
|
| 344 |
+
C/hr Sintering temperature: 1,300<confidence value="28">*C</confidence>
|
| 345 |
+
Sintering time: 5 hrs <boundary-data type="header">
|
| 346 |
+
<confidence value="88">21</confidence>
|
| 347 |
+
</boundary-data>
|
| 348 |
+
<page-break num="22"/>
|
| 349 |
+
Temperature lowering rate: 1<confidence value="8828688">00*C/hr</confidence>
|
| 350 |
+
As a result of measuring density of each of the thus obtained ten sintered bodies in the same manner as in Example <part-num-ref name="same manner as in Example">1,</part-num-ref>
|
| 351 |
+
it was found to be 6.91-6.93 g/cm3 (relative density: 99.0-99.2%). Weighted average value 6.983 g/cm3 calculated from mixing ratio of indium oxide and zinc oxide was used as a true density of the IZO sintered body. </p>
|
| 352 |
+
<p id="p-92" num="92">The sintered body obtained was grinding processed into a size having an outer diameter of 98 mm, an inner diameter of 78 mm and a length of 150 mm in the same manner as in Example <part-num-ref name="same manner as in Example">1</part-num-ref>
|
| 353 |
+
to prepare a target material. The eccentricity between the inner diameter and the outer diameter of the cylindrical target material was all 0.1 mm or smaller. Each sintered body was bonded to a cylindrical substrate made of Cu in the same manner as in Example <part-num-ref name="same manner as in Example">1.</part-num-ref>
|
| 354 |
+
No breakage was observed in all ten sintered bodies. </p>
|
| 355 |
+
<p id="p-93" num="93">COMPARATIVE EXAMPLE 1 Ten ITO sintered bodies were prepared in the same manner as in Example <part-num-ref name="same manner as in Example">1,</part-num-ref>
|
| 356 |
+
except that the cylindrical molding was directly placed on a sintering furnace, and a flat plate-like ITO molding was not used. In all ten sintered bodies, breakage occurred in the state of expanding to the lower side. </p>
|
| 357 |
+
<p id="p-94" num="94">COMPARATIVE EXAMPLE 2 Ten ITO sintered bodies were prepared in the same manner as in Example <part-num-ref name="same manner as in Example">1,</part-num-ref>
|
| 358 |
+
except that the sintering conditions were changed as follows. </p>
|
| 359 |
+
<p id="p-95" num="95">Sintering Conditions Charge weight/oxygen flow rate: 1.00 kg<confidence value="2">-</confidence>
|
| 360 |
+
min<confidence value="5">/</confidence>
|
| 361 |
+
liter Temperature rising rate: 50<confidence value="2">*</confidence>
|
| 362 |
+
C/hr Sintering temperature: 1,400<confidence value="28">*C</confidence>
|
| 363 |
+
Sintering time: 5 <confidence value="588">hrs</confidence>
|
| 364 |
+
Temperature lowering rate: <confidence value="5882">100*</confidence>
|
| 365 |
+
C/hr As a result of measuring density of each of the thus obtained ten sintered bodies <boundary-data type="header">
|
| 366 |
+
<confidence value="88">22</confidence>
|
| 367 |
+
</boundary-data>
|
| 368 |
+
<page-break num="23"/>
|
| 369 |
+
in the same manner as in Example <part-num-ref name="same manner as in Example">1,</part-num-ref>
|
| 370 |
+
it was found to be 6.54-6.62 g/cm3 (relative density: 91.4-92.5%). </p>
|
| 371 |
+
<p id="p-96" num="96">The sintered body obtained was grinding processed in the same manner as in Example <part-num-ref name="same manner as in Example">1.</part-num-ref>
|
| 372 |
+
The eccentricity between the inner diameter and the outer diameter of the cylindrical target material was all 0.2 mm or smaller. Each sintered body was bonded to a cylindrical substrate made of Cu in the same manner as in Example <part-num-ref name="same manner as in Example">1.</part-num-ref>
|
| 373 |
+
Breakage occurred in all ten sintered bodies. </p>
|
| 374 |
+
<p id="p-97" num="97">COMPARATIVE EXAMPLE 3 Ten A<confidence value="5">T</confidence>
|
| 375 |
+
O sintered bodies were prepared in the same manner as in Example <part-num-ref name="same manner as in Example">4,</part-num-ref>
|
| 376 |
+
except that the sintering conditions were changed as follows. </p>
|
| 377 |
+
<p id="p-98" num="98">Sintering Conditions Temperature rising rate: 50<confidence value="2">*</confidence>
|
| 378 |
+
C/hr Sintering temperature: 1,200<confidence value="28">*C</confidence>
|
| 379 |
+
Sintering time: 5 hrs Temperature lowering rate: 1<confidence value="882">00*</confidence>
|
| 380 |
+
C/hr As a result of measuring density of each of the thus obtained ten sintered bodies in the same manner as in Example <part-num-ref name="same manner as in Example">1,</part-num-ref>
|
| 381 |
+
it was found to be 5.19-5.23 g/cm3 (relative density: 93.3-94.1%). </p>
|
| 382 |
+
<p id="p-99" num="99">The sintered body obtained was grinding processed in the same manner as in Example <part-num-ref name="same manner as in Example">1.</part-num-ref>
|
| 383 |
+
The eccentricity between the inner diameter and the outer diameter of the cylindrical target material was all 0.1 mm or smaller. Each sintered body was bonded to a cylindrical substrate made of Cu in the same manner as in Example <part-num-ref name="same manner as in Example">1.</part-num-ref>
|
| 384 |
+
Breakage occurred in all ten sintered bodies. </p>
|
| 385 |
+
<p id="p-100" num="100">It should further be apparent to those skilled in the art that various changes in form and detail of the invention as shown and described above may be made. It is intended that such changes be included within the spirit and scope of the claims appended hereto.</p>
|
| 386 |
+
<boundary-data type="header">
|
| 387 |
+
<confidence value="88">23</confidence>
|
| 388 |
+
</boundary-data>
|
| 389 |
+
<p id="p-101" num="101">
|
| 390 |
+
<page-break num="24"/>
|
| 391 |
+
This application is based on Japanese Patent Application No. 2004-063 <confidence value="88">17</confidence>
|
| 392 |
+
1 filed March <part-num-ref name="filed March">5,</part-num-ref>
|
| 393 |
+
<part-num-ref name="filed March 5,">2004,</part-num-ref>
|
| 394 |
+
the disclosure of which is incorporated herein by reference in its entirety. </p>
|
| 395 |
+
<boundary-data type="header">
|
| 396 |
+
<confidence value="88">24</confidence>
|
| 397 |
+
</boundary-data>
|
| 398 |
+
</description>
|
| 399 |
+
</us-patent-application>
|
| 400 |
+
|
prior_art/11110436.xml
ADDED
|
@@ -0,0 +1,40 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11110436</doc-number>
|
| 8 |
+
<date>2010-08-02</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">Amend Paragraph 0053 of the published application as follows:</p>
|
| 15 |
+
<p id="p-2" num="2">Conventional radars employing automatic detection and tracking algorithms typically set the detection threshold high enough to achieve a probability of false alarm (PFA) to <part-num-ref name="probability of false alarm (PFA) to">1</part-num-ref>
|
| 16 |
+
in 10.sup.6 resolution cells or less. For a radar display extending <part-num-ref name="radar display extending">50</part-num-ref>
|
| 17 |
+
km in range with a <part-num-ref name="">100</part-num-ref>
|
| 18 |
+
m range resolution and <confidence value="55">1.</confidence>
|
| 19 |
+
degree. azimuth resolution, this translates to about <part-num-ref name="m range resolution and 1.degree. azimuth resolution, this translates to about">1</part-num-ref>
|
| 20 |
+
false alarm every <part-num-ref name="false alarm every">5</part-num-ref>
|
| 21 |
+
scans or <part-num-ref name="scans or">12</part-num-ref>
|
| 22 |
+
seconds (typical marine radar scan rates are <part-num-ref name="seconds (typical marine radar scan rates are">24</part-num-ref>
|
| 23 |
+
RPM). In contrast, low detection thresholds are a special feature of the detection processor <part-num-ref name="detection processor">22</part-num-ref>
|
| 24 |
+
and are used in order to increase the sensitivity of the radar, allowing smaller targets to be detected. An unwanted side effect is that the false alarm rate increases substantially, making it more difficult for tracking to perform. For example, the PFA could [[drop]] increase <part-num-ref name="PFA could [[drop]] increase">3</part-num-ref>
|
| 25 |
+
orders of magnitude from typical settings to say <confidence value="4">l</confidence>
|
| 26 |
+
0.sup.-3 resulting in <part-num-ref name="orders of magnitude from typical settings to say l0.sup.-3 resulting in">180</part-num-ref>
|
| 27 |
+
false alarms per scan or <part-num-ref name="false alarms per scan or">72</part-num-ref>
|
| 28 |
+
false alarms per second. This is a huge stress on tracking. To mitigate this effect, as well as to successfully track through maneuvers without degradations in track quality, the track processor <part-num-ref name="track processor">24</part-num-ref>
|
| 29 |
+
preferably includes multiple hypothesis testing (MHT) tracking with interacting multiple model (<confidence value="55">1M</confidence>
|
| 30 |
+
M) extended Kalman filtering as described earlier, and which are further described in [D. B. Reid, "An algorithm for tracking multiple targets", IEEE Transactions on Automatic Control, vol. AC-24, no. <part-num-ref name="preferably includes multiple hypothesis testing (MHT) tracking with interacting multiple model (1MM) extended Kalman filtering as described earlier, and which are further described in [D. B. Reid, "An algorithm for tracking multiple targets", IEEE Transactions on Automatic Control, vol. AC-24, no.">6,</part-num-ref>
|
| 31 |
+
December <part-num-ref name="preferably includes multiple hypothesis testing (MHT) tracking with interacting multiple model (1MM) extended Kalman filtering as described earlier, and which are further described in [D. B. Reid, "An algorithm for tracking multiple targets", IEEE Transactions on Automatic Control, vol. AC-24, no. 6, December">1979,</part-num-ref>
|
| 32 |
+
pp. 843-854], [G. A. Watson and W. D. Blair, "<confidence value="5">I</confidence>
|
| 33 |
+
MM algorithm for tracking targets that maneuver through coordinates turns", Proceedings of the SPIE (Society of Photo-Optical Instrumentation Engineers, vol. <part-num-ref name="SPIE (Society of Photo-Optical Instrumentation Engineers, vol.">1698,</part-num-ref>
|
| 34 |
+
Signal and Data Processing of Small Targets, Apr. 20-22, <part-num-ref name="SPIE (Society of Photo-Optical Instrumentation Engineers, vol. 1698, Signal and Data Processing of Small Targets, Apr. 20-22,">1992,</part-num-ref>
|
| 35 |
+
pp. 236-247]. These advanced processing algorithms often found in military radars yields the performance of much higher-priced systems and have been shown to work well under these high false alarm rate conditions. </p>
|
| 36 |
+
<p id="p-3" num="3">2 SN 11/110.436 S45-<confidence value="66">00</confidence>
|
| 37 |
+
7us </p>
|
| 38 |
+
</description>
|
| 39 |
+
</us-patent-application>
|
| 40 |
+
|
prior_art/11114645.xml
ADDED
|
@@ -0,0 +1,654 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11114645</doc-number>
|
| 8 |
+
<date>2005-04-25</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">UNITED STATES PATENT AND TRADEMARK OFFICE</heading>
|
| 14 |
+
<p id="p-1" num="1">Utility Patent Application for an Invention titled </p>
|
| 15 |
+
<heading id="h-2">METHODS AND SYSTEMS FOR MAINTAINING QUALITY OF</heading>
|
| 16 |
+
<heading id="h-3">SERVICE (QOS) LEVELS FOR DATA TRANSMISSIONS</heading>
|
| 17 |
+
<p id="p-2" num="2">Filed on April 25, 2005 <confidence value="1747">fBy:</confidence>
|
| 18 |
+
</p>
|
| 19 |
+
<heading id="h-4">
|
| 20 |
+
<confidence value="222222">BHUMIP</confidence>
|
| 21 |
+
KHASNABISH </heading>
|
| 22 |
+
<p id="p-3" num="3">18 Patterson Road Lexington, MA 02421 Citizenship: Canada/Bangladesh </p>
|
| 23 |
+
<heading id="h-5">NABEEL COCKER</heading>
|
| 24 |
+
<p id="p-4" num="4">110 Lowell Avenue New Hyde Park, NY 11040 Citizenship: Kenya Verizon Docket No.: 04-1507 <boundary-data type="header">Customer No. 32127</boundary-data>
|
| 25 |
+
<page-break num="2"/>
|
| 26 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="4">®</confidence>
|
| 27 |
+
EV 373627752 </boundary-data>
|
| 28 |
+
</p>
|
| 29 |
+
<heading id="h-6">METHODS AND SYSTEMS FOR MAINTAINING QUALITY OF</heading>
|
| 30 |
+
<heading id="h-7">SERVICE (QOS) LEVELS FOR DATA TRANSMISSIONS</heading>
|
| 31 |
+
<heading id="h-8">BACKGROUND</heading>
|
| 32 |
+
<p id="p-5" num="5">[0001] Many types of data transmissions have emerged that require certain transmission quality levels to maintain the integrity of the data when the data is transmitted over packet-switched networks (e.g., internet protocol networks). Video-on-demand and voice services are examples of such data transmissions. Voice services over internet protocol networks, commonly referred to as Vo<confidence value="5">I</confidence>
|
| 33 |
+
P, are an emerging alternative to standard voice services over circuit-switched telephone networks, largely because of the potential cost savings provided by Vo<confidence value="5">I</confidence>
|
| 34 |
+
P. By using packet-switched networks (e.g., the Internet) to transmit voice services, callers are able to avoid long distance fees associated with using a telephone carrier's traditional circuit-switched telephony networks. </p>
|
| 35 |
+
<p id="p-6" num="6">[0002] However, implementation of Vo<confidence value="5">I</confidence>
|
| 36 |
+
P has proved to be a challenging task with respect to providing the same voice quality typically offered by traditional circuit-switched telephone services. One aspect that makes high- quality Vo<confidence value="5">I</confidence>
|
| 37 |
+
P a challenging task is congestion of internet protocol (<confidence value="488">IP)</confidence>
|
| 38 |
+
networks. When IP networks become congested, data transmissions experience longer transmission delays that may not meet minimum quality standards. Moreover, when IP networks are used to transport different types of data (e.g., voice transmissions and more typical types of digital data), chances of congestion increase, especially when minimum quality standards are required for more than one particular data transmission over the network. </p>
|
| 39 |
+
<p id="p-7" num="7">[0003] Further, the common use of IP networks for transmitting various types of data, as well as associated control signaling, tends to complicate timing issues for data transmissions. Not only does control signaling require responses to messages within pre-specified time intervals, as mentioned above, time-criticalness is also required for many types of media data traffic transmissions (e.g., video-on-demand and voice services transmissions). The wide variety of timing requirements for the different types of transmissions tends to complicate network timing, which can undesirably affect the quality of transmissions that have minimum quality standards. In particular, excessive <boundary-data type="header">
|
| 40 |
+
<confidence value="8">1</confidence>
|
| 41 |
+
</boundary-data>
|
| 42 |
+
<page-break num="3"/>
|
| 43 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="4">®</confidence>
|
| 44 |
+
EV 373627752 </boundary-data>
|
| 45 |
+
packet loss, transmission delay, or variation in transmission delays (i.e., jitter) may degrade the quality of transmitted data signals, including voice services transmissions. Moreover, bandwidth limitations, lengths of network paths, and other network parameters may also undesirably affect the quality of data transmissions over IP networks. </p>
|
| 46 |
+
<p id="p-8" num="8">[0004] Parameters used to define and measure the quality of data transmissions over IP networks are commonly referred to as quality-of-service (QoS) parameters, which include parameters such as packet loss, delay, and jitter. To help control QoS parameters for data transmissions, many traditional Vo<confidence value="5">I</confidence>
|
| 47 |
+
P services have implemented admission controls for selecting which data transmissions (e.g., which telephone calls) to admit for transmission over the IP network based on a predefined order of priority. If, for example, the IP network cannot handle additional telephone calls of lower priority than the already admitted telephone calls, the call admission controls will not admit the additional telephone calls for transmission over the IP network. While call admission controls have helped to prevent instances of voice quality degradation by preventing congestion of IP networks, call admission controls have several drawbacks. For example, when call admission controls are relied upon solely or primarily to maintain voice quality parameters, customer satisfaction is often jeopardized whenever callers are unable to place calls due to a lack of network availability. The inability to place calls can easily cause would-be callers to feel dissatisfied with the Vo<confidence value="68">IP</confidence>
|
| 48 |
+
services offered by service carriers. In turn, the users' unsatisfactory experiences may cause service carriers to suffer a loss of business, reputation, or goodwill. </p>
|
| 49 |
+
<p id="p-9" num="9">[0005] In short, conventional IP networks do not transmit data in a manner that consistently satisfies minimum quality standards required by many types of data transmissions (e.g., voice services transmissions).</p>
|
| 50 |
+
<heading id="h-9">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 51 |
+
<p id="p-10" num="10">[0006] The accompanying drawings illustrate various embodiments and are a part of the specification. The illustrated embodiments are merely <boundary-data type="header">
|
| 52 |
+
<confidence value="8">2</confidence>
|
| 53 |
+
</boundary-data>
|
| 54 |
+
<page-break num="4"/>
|
| 55 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="4">®</confidence>
|
| 56 |
+
EV 373627752 </boundary-data>
|
| 57 |
+
examples and do not limit the scope of the disclosure. Throughout the drawings, identical reference numbers designate identical or similar elements. </p>
|
| 58 |
+
<p id="p-11" num="11">[0007] Figure 1 is a block diagram of a system for simulating and monitoring data transmissions over a network framework, according to one embodiment.</p>
|
| 59 |
+
<p id="p-12" num="12">[0008] Figure 2 is a block diagram illustrating another embodiment of the system of Figure 1.</p>
|
| 60 |
+
<p id="p-13" num="13">[0009] Figure 3 is a chart illustrating measured mean opinion scores (MOS) for different quantities of voice data streams transmitted over the system of Figure 2, according to one embodiment.</p>
|
| 61 |
+
<p id="p-14" num="14">[0010] Figure 4 is a chart illustrating measured packet loss and link utilization for different quantities of voice transmission packet streams being transmitted over the system of Figure 2, according to one embodiment.</p>
|
| 62 |
+
<p id="p-15" num="15">[0011] Figure 5 is a block diagram of an operational Vo<confidence value="5">I</confidence>
|
| 63 |
+
P network framework for monitoring link utilization and maintaining voice quality of service (QoS) levels based on the monitored link utilization, according to one embodiment. </p>
|
| 64 |
+
<p id="p-16" num="16">[0012] Figure 6 is a flowchart illustrating a method of identifying a link utilization threshold for a bottleneck link of the system of Figure 1.</p>
|
| 65 |
+
<p id="p-17" num="17">[0013] Figure 7 is a flowchart illustrating a method of maintaining QoS parameters for data transmissions based on link utilization levels.</p>
|
| 66 |
+
<heading id="h-10">DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS</heading>
|
| 67 |
+
<p id="p-18" num="18">[0014] The presently disclosed methods and systems provide for the maintenance of quality-of-service (QoS) levels for data transmissions. A network framework is provided. Data transmissions are transmitted over the network framework. QoS parameters and network link utilization rates associated with the data transmissions are monitored, thereby enabling network operators to determine network link utilization thresholds, which are defined as the link utilization rates at which the QoS parameters of the data transmissions begin to degrade below predetermined quality standards.</p>
|
| 68 |
+
<p id="p-19" num="19">[0015] The determined link utilization thresholds may be used to deliver and maintain data transmissions with desired QoS levels. The utilization thresholds may be implemented to provide desired QoS levels in links of the <boundary-data type="header">
|
| 69 |
+
<confidence value="8">3</confidence>
|
| 70 |
+
</boundary-data>
|
| 71 |
+
<page-break num="5"/>
|
| 72 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="2">@</confidence>
|
| 73 |
+
EV 373627752 </boundary-data>
|
| 74 |
+
provided network framework and/or in links of similar operational packet- switched networks. By using the determined link utilization thresholds to limit link utilization rates, the available bandwidth of packet-switched network links can be utilized to the extent allowable without degrading data quality below the predetermined quality standards. Consequently, network resources are allocated so that subscribers do not experience undesirable degradations in data quality or, even worse, not being able to have their data transmissions admitted for transmission over packet-switched networks. In some embodiments, the data transmissions comprise voice services transmissions. </p>
|
| 75 |
+
<p id="p-20" num="20">Certain embodiments of the present systems and methods will now be described in detail.</p>
|
| 76 |
+
<p id="p-21" num="21">
|
| 77 |
+
<confidence value="4">1</confidence>
|
| 78 |
+
. INTRODUCTION OF ELEMENTS [0016] Figure 1 is a block diagram of a system <part-num-ref name="system">100</part-num-ref>
|
| 79 |
+
for simulating and monitoring voice transmissions over a network framework, according to one embodiment. The system <part-num-ref name="system">100</part-num-ref>
|
| 80 |
+
is configured to monitor QoS parameters and link utilization rates associated with the simulated voice transmissions, as described below. </p>
|
| 81 |
+
<p id="p-22" num="22">A. Signal Generator [0017] As shown in Figure 1, signal generators 110-1 and 110-2 (collectively "signal generators 110") are in connection with respective customer edge routers 115-1 and 115-2 (collectively "customer edge routers 115") of a network framework <part-num-ref name="network framework">116.</part-num-ref>
|
| 82 |
+
In the embodiment of Figure 1, the signal generators <part-num-ref name="signal generators">110</part-num-ref>
|
| 83 |
+
are located outside of the network framework <part-num-ref name="network framework">116,</part-num-ref>
|
| 84 |
+
and the customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 85 |
+
are part of the network framework <part-num-ref name="network framework">116.</part-num-ref>
|
| 86 |
+
</p>
|
| 87 |
+
<p id="p-23" num="23">Connections 118-1 and 118-2 (collectively "connections 118") between the signal generators <part-num-ref name="signal generators">110</part-num-ref>
|
| 88 |
+
and the customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 89 |
+
may include any known media and/or protocols (e.g., Ethernet) capable of carrying data transmissions. The connections <part-num-ref name="connections">118</part-num-ref>
|
| 90 |
+
may be direct or indirect connections between the signal generators <part-num-ref name="signal generators">110</part-num-ref>
|
| 91 |
+
and the customer edge routers <part-num-ref name="customer edge routers">115.</part-num-ref>
|
| 92 |
+
</p>
|
| 93 |
+
<p id="p-24" num="24">[0018] The signal generators <part-num-ref name="signal generators">110</part-num-ref>
|
| 94 |
+
are configured to make, maintain, and terminate different mixes and loads of data traffic over the network framework <part-num-ref name="network framework">116.</part-num-ref>
|
| 95 |
+
In particular, the signal generators <part-num-ref name="signal generators">110</part-num-ref>
|
| 96 |
+
may generate different quantities of data streams (i.e., data transmissions) over the network framework <part-num-ref name="network framework">116.</part-num-ref>
|
| 97 |
+
</p>
|
| 98 |
+
<boundary-data type="header">
|
| 99 |
+
<confidence value="8">4</confidence>
|
| 100 |
+
</boundary-data>
|
| 101 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="2">@</confidence>
|
| 102 |
+
EV 373627752 </boundary-data>
|
| 103 |
+
<p id="p-25" num="25">
|
| 104 |
+
<page-break num="6"/>
|
| 105 |
+
Accordingly, the signal generators <part-num-ref name="signal generators">110</part-num-ref>
|
| 106 |
+
are able to increase and decrease the quantity of data streams that are active on the system <part-num-ref name="system">100.</part-num-ref>
|
| 107 |
+
By generating or transmitting data streams, or simulated data streams, the signal generators <part-num-ref name="signal generators">110</part-num-ref>
|
| 108 |
+
are able to generate different traffic loads on the network framework <part-num-ref name="network framework">116.</part-num-ref>
|
| 109 |
+
</p>
|
| 110 |
+
<p id="p-26" num="26">[0019] In some embodiments, the signal generators <part-num-ref name="signal generators">110</part-num-ref>
|
| 111 |
+
are able to generate voice services transmissions (e.g., voice telephone calls) in the form of packetized data streams suitable for use with Vo<confidence value="5">I</confidence>
|
| 112 |
+
P applications and packet- switched networks. For example, IP-based telephone call data streams may be generated in accordance with known protocols for carrying voice data, including G.711 and G.729b protocols, which are well known to those skilled in the art. The data streams may comprise real-time transfer protocol (RTP) streams. </p>
|
| 113 |
+
<p id="p-27" num="27">[0020] The signal generators <part-num-ref name="signal generators">110</part-num-ref>
|
| 114 |
+
may include any device(s) and/or instructions capable of generating and/or transmitting data streams, including voice transmission streams suitable for Vo<confidence value="5">I</confidence>
|
| 115 |
+
P applications. The devices may include but are not limited to known IP telephones, session initiation protocol (SIP) telephones, IP/PBXs, servers, gateways (e.g., internet protocol to public switched telephone network (IP/PSTN) gateways and media gateway control protocol (MGCP) gateways), integrated access devices (<confidence value="5">I</confidence>
|
| 116 |
+
ADs) capable of transmitting voice packet data streams; modems; network interface cards, video servers, and any other device capable of providing data streams for transmission over the network framework <part-num-ref name="network framework">116.</part-num-ref>
|
| 117 |
+
In one embodiment, the signal generators <part-num-ref name="signal generators">110</part-num-ref>
|
| 118 |
+
include SIP-based Vo<confidence value="5">I</confidence>
|
| 119 |
+
P call generators or verifiers. </p>
|
| 120 |
+
<p id="p-28" num="28">[0021] In some embodiments, the signal generators <part-num-ref name="signal generators">110</part-num-ref>
|
| 121 |
+
may not be limited solely to generating data transmissions. In particular, the signal generators <part-num-ref name="signal generators">110</part-num-ref>
|
| 122 |
+
may be configured to receive incoming data transmissions. For example, in one embodiment the signal generator 110-1 may transmit a telephone call over the network framework <part-num-ref name="network framework">116</part-num-ref>
|
| 123 |
+
shown in Figure 1 to the signal generator 110-2, which will receive the incoming telephone call. Further, the signal generators <part-num-ref name="signal generators">110</part-num-ref>
|
| 124 |
+
may include any of the QoS monitoring capabilities described below. As discussed below in greater detail, QoS monitoring includes, for example, monitoring parameters (e.g., delay, jitter, packet loss) for an RTP stream, and mapping the parameters to mean opinion score (MOS) for Vo<confidence value="68">IP</confidence>
|
| 125 |
+
applications. </p>
|
| 126 |
+
<boundary-data type="header">
|
| 127 |
+
<confidence value="8">5</confidence>
|
| 128 |
+
</boundary-data>
|
| 129 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="4">®</confidence>
|
| 130 |
+
EV 373627752 </boundary-data>
|
| 131 |
+
<p id="p-29" num="29">
|
| 132 |
+
<page-break num="7"/>
|
| 133 |
+
[0022] While Figure 1 shows only one signal generator 110-1 in connection with one customer edge router 115-1, those skilled in the art will appreciate that multiple signal generators <part-num-ref name="art will appreciate that multiple signal generators">110</part-num-ref>
|
| 134 |
+
may be in connection with and transmit data streams to one customer edge router 115-1. In other words, multiple signal generators <part-num-ref name="may be in connection with and transmit data streams to one customer edge router 115-1. In other words, multiple signal generators">110</part-num-ref>
|
| 135 |
+
may be connected to the customer edge router 115-<confidence value="6">1</confidence>
|
| 136 |
+
<confidence value="88">to</confidence>
|
| 137 |
+
form a sub-network of endpoints useful for establishing simulated data transmissions over the network framework <part-num-ref name="network framework">116.</part-num-ref>
|
| 138 |
+
</p>
|
| 139 |
+
<p id="p-30" num="30">B. Network Framework [0023] The network framework <part-num-ref name="network framework">116</part-num-ref>
|
| 140 |
+
is made of components and links configured to form paths over the network framework <part-num-ref name="network framework">116</part-num-ref>
|
| 141 |
+
and between different endpoints. The network framework <part-num-ref name="network framework">116</part-num-ref>
|
| 142 |
+
may comprise or be part of a packet-switched network capable of carrying data transmissions between endpoints such as the signal generators <part-num-ref name="signal generators">110.</part-num-ref>
|
| 143 |
+
Accordingly, network operators may use the network framework <part-num-ref name="network framework">116</part-num-ref>
|
| 144 |
+
to monitor and determine link utilization thresholds for links of operational packet-switched networks. This may be performed during operation, provisioning, maintenance, or other events associated with packet-switched networks. </p>
|
| 145 |
+
<p id="p-31" num="31">[0024] Alternatively, the network framework <part-num-ref name="network framework">116</part-num-ref>
|
| 146 |
+
may be configured to emulate at least part of a packet-switched network. For example, the network framework <part-num-ref name="network framework">116</part-num-ref>
|
| 147 |
+
may include components suitable for emulating characteristics of components of operational packet-switched networks. Accordingly, the network framework <part-num-ref name="network framework">116</part-num-ref>
|
| 148 |
+
can be used to model links of packet-switched networks. Data transmissions can be simulated over the links of the network framework <part-num-ref name="network framework">116</part-num-ref>
|
| 149 |
+
and used to determine link utilization thresholds, which may be implemented in links of operational packet-switched networks. The components and links of the network framework <part-num-ref name="network framework">116</part-num-ref>
|
| 150 |
+
shown in Figure 1 will now be described in detail. </p>
|
| 151 |
+
<p id="p-32" num="32">1. Customer Edge Router [0025] The customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 152 |
+
are configured to receive the data streams generated by the signal generators <part-num-ref name="signal generators">110</part-num-ref>
|
| 153 |
+
and to route the data streams to provider edge routers 130-1 and 130-2 (collectively "provider edge routers 130"). For data streams traveling through the customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 154 |
+
in the opposite direction (i.e., from provider edge routers <part-num-ref name="from provider edge routers">130</part-num-ref>
|
| 155 |
+
toward signal <boundary-data type="header">
|
| 156 |
+
<confidence value="8">6</confidence>
|
| 157 |
+
</boundary-data>
|
| 158 |
+
<page-break num="8"/>
|
| 159 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="4">®</confidence>
|
| 160 |
+
EV 373627752 </boundary-data>
|
| 161 |
+
generators 110), the customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 162 |
+
are configured to route the data streams to the appropriate signal generators <part-num-ref name="appropriate signal generators">110</part-num-ref>
|
| 163 |
+
or to other destinations. </p>
|
| 164 |
+
<p id="p-33" num="33">[0026] In one embodiment, the customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 165 |
+
comprise virtual routers configured to activate and deactivate connective links with the provider edge routers <part-num-ref name="provider edge routers">130.</part-num-ref>
|
| 166 |
+
The customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 167 |
+
may be implemented using known routing devices. The activation and deactivation of links between the customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 168 |
+
and the provider edge routers <part-num-ref name="provider edge routers">130</part-num-ref>
|
| 169 |
+
will be described in more detail below. </p>
|
| 170 |
+
<p id="p-34" num="34">2. Access Link [0027] Access links 140-1 and 140-2 (collectively "access links 140") connect the customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 171 |
+
with the provider edge routers <part-num-ref name="provider edge routers">130.</part-num-ref>
|
| 172 |
+
</p>
|
| 173 |
+
<p id="p-35" num="35">When data streams travel over the access links <part-num-ref name="access links">140</part-num-ref>
|
| 174 |
+
in the direction from the customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 175 |
+
to the provider edge routers <part-num-ref name="provider edge routers">130,</part-num-ref>
|
| 176 |
+
the access links <part-num-ref name="access links">140</part-num-ref>
|
| 177 |
+
are referred to as ingress links <part-num-ref name="are referred to as ingress links">140.</part-num-ref>
|
| 178 |
+
When the data streams travel over the access links <part-num-ref name="access links">140</part-num-ref>
|
| 179 |
+
in the opposite direction, the access links <part-num-ref name="access links">140</part-num-ref>
|
| 180 |
+
are referred to as egress links <part-num-ref name="are referred to as egress links">140.</part-num-ref>
|
| 181 |
+
</p>
|
| 182 |
+
<p id="p-36" num="36">[0028] The access links <part-num-ref name="access links">140</part-num-ref>
|
| 183 |
+
may include any media capable of carrying the data streams between the customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 184 |
+
and the provider edge routers <part-num-ref name="provider edge routers">130.</part-num-ref>
|
| 185 |
+
For example, the access links <part-num-ref name="access links">140</part-num-ref>
|
| 186 |
+
may include one or more permanent virtual circuits (PVCs) (see items <part-num-ref name="may include one or more permanent virtual circuits (PVCs) (see items">230</part-num-ref>
|
| 187 |
+
of Figure 2) or virtual local area networks (VLANs) configured to provide ingress and egress networks or links. In one embodiment, the access links <part-num-ref name="access links">140</part-num-ref>
|
| 188 |
+
are made up of a plurality of provisioned asynchronous transfer mode (ATM) constant bit rate (CBR) PVCs, which will be understood by those skilled in the art. The PVCs may have different bandwidth capacities. However, in one embodiment, each of the PVCs has a bandwidth capacity of approximately <part-num-ref name="bandwidth capacity of approximately">512</part-num-ref>
|
| 189 |
+
kilobits per second. </p>
|
| 190 |
+
<p id="p-37" num="37">[0029] Each of the PVCs or VLANs may be individually activated or deactivated by the customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 191 |
+
and/or provider edge routers <part-num-ref name="and/or provider edge routers">130,</part-num-ref>
|
| 192 |
+
thereby allowing the amount of available bandwidth of the access links <part-num-ref name="access links">140</part-num-ref>
|
| 193 |
+
to be adjusted. Consequently, individual PVCs may be activated or deactivated based on measured utilization rates of the access links <part-num-ref name="access links">140,</part-num-ref>
|
| 194 |
+
as discussed below. </p>
|
| 195 |
+
<boundary-data type="header">
|
| 196 |
+
<confidence value="8">7</confidence>
|
| 197 |
+
</boundary-data>
|
| 198 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="4">®</confidence>
|
| 199 |
+
EV 373627752 </boundary-data>
|
| 200 |
+
<p id="p-38" num="38">
|
| 201 |
+
<page-break num="9"/>
|
| 202 |
+
3. Link Utilization Monitor [0030] Link utilization monitors 150-1 and 150-2 (collectively "link utilization monitors 150") are in connection with the access links <part-num-ref name="access links">140</part-num-ref>
|
| 203 |
+
and are each disposed between a particular customer edge router <part-num-ref name="particular customer edge router">115</part-num-ref>
|
| 204 |
+
and a particular provider edge router <part-num-ref name="particular provider edge router">130,</part-num-ref>
|
| 205 |
+
as shown in Figure 1. The link utilization monitors <part-num-ref name="link utilization monitors">150</part-num-ref>
|
| 206 |
+
may be connected with the access links <part-num-ref name="access links">140</part-num-ref>
|
| 207 |
+
at any point or points along the access link <part-num-ref name="access link">140.</part-num-ref>
|
| 208 |
+
Although not shown in Figure 1, the link utilization monitors <part-num-ref name="link utilization monitors">150</part-num-ref>
|
| 209 |
+
may alternatively be connected with the customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 210 |
+
or the provider edge routers <part-num-ref name="provider edge routers">130.</part-num-ref>
|
| 211 |
+
</p>
|
| 212 |
+
<p id="p-39" num="39">[0031] The link utilization monitors <part-num-ref name="link utilization monitors">150</part-num-ref>
|
| 213 |
+
may include any device or devices, physical or logical, capable of monitoring and determining link utilization rates, including devices known in the art. The link utilization monitors <part-num-ref name="link utilization monitors">150</part-num-ref>
|
| 214 |
+
may be stand-alone devices or may be integrated with other devices. For example, the link utilization monitors <part-num-ref name="link utilization monitors">150</part-num-ref>
|
| 215 |
+
may be integrated with the customer edge routers <part-num-ref name="customer edge routers">115,</part-num-ref>
|
| 216 |
+
the provider edge routers <part-num-ref name="provider edge routers">130,</part-num-ref>
|
| 217 |
+
or devices in which the provider edge routers <part-num-ref name="provider edge routers">130</part-num-ref>
|
| 218 |
+
and/or the customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 219 |
+
are deployed. </p>
|
| 220 |
+
<p id="p-40" num="40">[0032] Link utilization rate is generally a measure of the fraction or percentage of the bandwidth capacity of a link that is being utilized by data transmissions over the link. For example, if a particular link has a bandwidth capacity of <part-num-ref name="bandwidth capacity of">512</part-num-ref>
|
| 221 |
+
kilobits per second, and <part-num-ref name="kilobits per second, and">256</part-num-ref>
|
| 222 |
+
kilobits per second are being transmitted over the link, the utilization of the link is fifty percent. </p>
|
| 223 |
+
<p id="p-41" num="41">[0033] As data streams are transported over the access links <part-num-ref name="access links">140,</part-num-ref>
|
| 224 |
+
the link utilization monitors <part-num-ref name="link utilization monitors">150</part-num-ref>
|
| 225 |
+
can dynamically monitor and determine the link utilization rates of the access links <part-num-ref name="access links">140.</part-num-ref>
|
| 226 |
+
Thus, the link utilization monitors <part-num-ref name="link utilization monitors">150</part-num-ref>
|
| 227 |
+
are able to track current link utilization rates. The monitored link utilization rates are useful for determining link utilization thresholds, which are, in turn, useful for delivering and maintaining QoS levels for data transmissions, as discussed below. </p>
|
| 228 |
+
<p id="p-42" num="42">4. Provider Edge Router [0034] The provider edge routers <part-num-ref name="provider edge routers">130</part-num-ref>
|
| 229 |
+
are configured to receive data streams from the customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 230 |
+
and to route the data streams to core routers 170-1 and 170-2 (collectively "core routers 170"). For data streams traveling through the provider edge routers <part-num-ref name="provider edge routers">130</part-num-ref>
|
| 231 |
+
in the opposite direction (i.e., from provider edge routers <part-num-ref name="from provider edge routers">130</part-num-ref>
|
| 232 |
+
toward customer edge routers <boundary-data type="header">
|
| 233 |
+
<confidence value="8">8</confidence>
|
| 234 |
+
</boundary-data>
|
| 235 |
+
<page-break num="10"/>
|
| 236 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="2">@</confidence>
|
| 237 |
+
EV 373627752 </boundary-data>
|
| 238 |
+
115), the provider edge routers <part-num-ref name="provider edge routers">130</part-num-ref>
|
| 239 |
+
are configured to route the data streams to the appropriate customer edge routers <part-num-ref name="appropriate customer edge routers">115.</part-num-ref>
|
| 240 |
+
</p>
|
| 241 |
+
<p id="p-43" num="43">[0035] In one embodiment, the provider edge routers <part-num-ref name="provider edge routers">130</part-num-ref>
|
| 242 |
+
comprise virtual routers configured to activate and deactivate the links or networks that make up the access links <part-num-ref name="access links">140</part-num-ref>
|
| 243 |
+
between the provider edge routers <part-num-ref name="provider edge routers">130</part-num-ref>
|
| 244 |
+
and the customer edge routers <part-num-ref name="customer edge routers">115.</part-num-ref>
|
| 245 |
+
The provider edge routers <part-num-ref name="provider edge routers">130</part-num-ref>
|
| 246 |
+
may be implemented using known routing devices. The activation and deactivation of the access links <part-num-ref name="access links">140</part-num-ref>
|
| 247 |
+
between the customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 248 |
+
and the provider edge routers <part-num-ref name="provider edge routers">130</part-num-ref>
|
| 249 |
+
will be described in more detail below. </p>
|
| 250 |
+
<p id="p-44" num="44">5. Transport Link [0036] Transport links 180-1 and 180-2 (collectively "transport links 180") connect the provider edge routers <part-num-ref name="provider edge routers">130</part-num-ref>
|
| 251 |
+
with their respective core routers <part-num-ref name="with their respective core routers">170.</part-num-ref>
|
| 252 |
+
</p>
|
| 253 |
+
<p id="p-45" num="45">The transport links 180 may include any transmission medium or media suitable for packet data stream transmission. In one embodiment, the transport links <part-num-ref name="transport links">180</part-num-ref>
|
| 254 |
+
are made up of asynchronous transfer mode (ATM) optical carrier three (<confidence value="66">OC</confidence>
|
| 255 |
+
<part-num-ref name="are made up of asynchronous transfer mode (ATM) optical carrier three (OC">3)</part-num-ref>
|
| 256 |
+
media, which are known to those skilled in the art. </p>
|
| 257 |
+
<p id="p-46" num="46">6. Core Router [0037] The core routers 170-1 and 170-2 are able to route data streams between each other over a core network link <part-num-ref name="core network link">190.</part-num-ref>
|
| 258 |
+
As known to those skilled in the art, core routers <part-num-ref name="art, core routers">170</part-num-ref>
|
| 259 |
+
are typically connection points to a backbone network and can include switching computers equipped to transfer data over core networks. </p>
|
| 260 |
+
<p id="p-47" num="47">7. Core Network Link [0038] The core network link <part-num-ref name="core network link">190</part-num-ref>
|
| 261 |
+
can include any packet-switched network medium or media capable of carrying data streams between the core routers <part-num-ref name="core routers">170.</part-num-ref>
|
| 262 |
+
For example, the core network link <part-num-ref name="core network link">190</part-num-ref>
|
| 263 |
+
may be an internet protocol (IP), multi-protocol label switching (MPLS), or IP/MPLS network medium or media. </p>
|
| 264 |
+
<p id="p-48" num="48">In one embodiment, the core network link <part-num-ref name="core network link">190</part-num-ref>
|
| 265 |
+
includes at least one packet- over-SONET (POS) optical carrier twelve (<confidence value="66">OC</confidence>
|
| 266 |
+
-12) medium connecting the core routers <part-num-ref name="core routers">170</part-num-ref>
|
| 267 |
+
to each other. </p>
|
| 268 |
+
<p id="p-49" num="49">C. QoS Monitor [0039] QoS monitors 195-1 and 195-2 (collectively "QoS monitors 195") are configured to monitor end-to-end QoS parameters of data transmissions.</p>
|
| 269 |
+
<p id="p-50" num="50">The QoS monitors 195 may be configured to monitor QoS parameters at <boundary-data type="header">
|
| 270 |
+
<confidence value="8">9</confidence>
|
| 271 |
+
</boundary-data>
|
| 272 |
+
<page-break num="11"/>
|
| 273 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="4">®</confidence>
|
| 274 |
+
EV 373627752 </boundary-data>
|
| 275 |
+
locations behind the customer edge routers <part-num-ref name="customer edge routers">115.</part-num-ref>
|
| 276 |
+
As shown in Figure 1, the QoS monitors may be connected to the links <part-num-ref name="links">118</part-num-ref>
|
| 277 |
+
between the call edge routers <part-num-ref name="call edge routers">115</part-num-ref>
|
| 278 |
+
and the signal generators <part-num-ref name="signal generators">110.</part-num-ref>
|
| 279 |
+
Alternatively, the QoS monitors <part-num-ref name="QoS monitors">195</part-num-ref>
|
| 280 |
+
may be integrated with the signal generators <part-num-ref name="signal generators">110,</part-num-ref>
|
| 281 |
+
the customer edge routers <part-num-ref name="customer edge routers">115,</part-num-ref>
|
| 282 |
+
and/or devices in which the signal generators <part-num-ref name="signal generators">110</part-num-ref>
|
| 283 |
+
or the customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 284 |
+
are deployed. </p>
|
| 285 |
+
<p id="p-51" num="51">[0040] The QoS monitors <part-num-ref name="QoS monitors">195</part-num-ref>
|
| 286 |
+
may include one or more devices and/or instructions for monitoring various parameters. For example, when data transmissions are voice-based, the parameters may relate to voice quality and QoS. For example, the QoS monitors <part-num-ref name="QoS monitors">195</part-num-ref>
|
| 287 |
+
may be configured to monitor mean opinion scores (MOS), perceptual evaluation of speech quality (PESQ), packet loss, delay, jitter, and other parameters associated with the quality of data transmissions. To measure these various QoS parameters, the QoS monitors <part-num-ref name="QoS monitors">195</part-num-ref>
|
| 288 |
+
may include digital speech level analyzers (DSLAs), Vo<confidence value="5">I</confidence>
|
| 289 |
+
P Call analyzers, network protocol analyzers, and any other known devices and/or <confidence value="5">.</confidence>
|
| 290 |
+
computer instructions (e.g., software) useful for measuring network transmission parameters. </p>
|
| 291 |
+
<p id="p-52" num="52">[0041] The QoS parameters monitored by the QoS monitors <part-num-ref name="QoS monitors">195</part-num-ref>
|
| 292 |
+
are useful for determining whether data transmissions are being delivered at a desired level of quality. For example, when the data transmissions comprise voice services transmissions, it is typically desirable for the voice services transmissions to exhibit a PSTN-grade (also known as toll-quality) voice quality, which is often defined as a mean opinion score (MOS) of at least approximately 4.0. For business-grade voice services, a MOS of approximately 3.5 to 4.0 is expected. </p>
|
| 293 |
+
<p id="p-53" num="53">[0042] By monitoring QoS parameters, data transmission quality can be quantitatively determined. The QoS parameter values can be used by network operators to determine whether data transmissions are at an acceptable quality level by comparing the determined values to predetermined quality thresholds (e.g., a MOS of 4.0 for PSTN-grade voice services). The determined QoS parameters may then be used to identify key link utilization rates at which the QoS parameters deteriorate below the predetermined quality thresholds, which will be discussed in more detail below with reference <boundary-data type="header">
|
| 294 |
+
<confidence value="88">10</confidence>
|
| 295 |
+
</boundary-data>
|
| 296 |
+
<page-break num="12"/>
|
| 297 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="4">®</confidence>
|
| 298 |
+
EV 373627752 </boundary-data>
|
| 299 |
+
to examples of data transmissions being simulated by another embodiment of the system <part-num-ref name="system">100,</part-num-ref>
|
| 300 |
+
which embodiment is shown in Figure 2. </p>
|
| 301 |
+
<heading id="h-11">II. VOICE TRAFFIC SIMULATIONS</heading>
|
| 302 |
+
<p id="p-54" num="54">[0043] Figure 2 is a block diagram illustrating another embodiment of the system <part-num-ref name="system">100</part-num-ref>
|
| 303 |
+
of Figure 1. As shown in Figure 2, system <part-num-ref name="of Figure 1. As shown in Figure 2, system">200</part-num-ref>
|
| 304 |
+
is similar to the system <part-num-ref name="system">100</part-num-ref>
|
| 305 |
+
shown in Figure 1. The system <part-num-ref name="system">200</part-num-ref>
|
| 306 |
+
includes Ethernet switches 210-1 and 210-2 (collectively "Ethernet switches 210") configured to form the connections <part-num-ref name="connections">118</part-num-ref>
|
| 307 |
+
between the signal generators <part-num-ref name="signal generators">110,</part-num-ref>
|
| 308 |
+
the QoS monitors <part-num-ref name="QoS monitors">195,</part-num-ref>
|
| 309 |
+
and the customer edge routers <part-num-ref name="customer edge routers">115.</part-num-ref>
|
| 310 |
+
The customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 311 |
+
are in connection with the provider edge routers <part-num-ref name="provider edge routers">130.</part-num-ref>
|
| 312 |
+
The customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 313 |
+
and provider edge routers <part-num-ref name="and provider edge routers">130</part-num-ref>
|
| 314 |
+
are implemented as virtual routers in an edge router <part-num-ref name="edge router">220.</part-num-ref>
|
| 315 |
+
</p>
|
| 316 |
+
<p id="p-55" num="55">[0044] The edge router <part-num-ref name="edge router">220</part-num-ref>
|
| 317 |
+
may comprise any known device in which virtual routers may be implemented to form permanent virtual circuits (PVCs) <part-num-ref name="may comprise any known device in which virtual routers may be implemented to form permanent virtual circuits (PVCs)">230</part-num-ref>
|
| 318 |
+
connecting the virtual route<confidence value="8">r</confidence>
|
| 319 |
+
s to each other. The PVCs <part-num-ref name="PVCs">230</part-num-ref>
|
| 320 |
+
may form the access links <part-num-ref name="access links">140</part-num-ref>
|
| 321 |
+
discussed above. In particular, PVCs 230-1, 230-2, 230-3, 230-4, and 230-5 form the access link 140-1 between customer edge router 115-1 and provider edge router 130-1, while PVCs 230-6, 230-7, 230-8, 230- <part-num-ref name="access link 140-1 between customer edge router 115-1 and provider edge router 130-1, while PVCs 230-6, 230-7, 230-8, 230-">9,</part-num-ref>
|
| 322 |
+
and 230-10 form the access link 140-2 between customer edge router 115- <part-num-ref name="access link 140-2 between customer edge router 115-">2</part-num-ref>
|
| 323 |
+
and provider edge router 130-2. </p>
|
| 324 |
+
<p id="p-56" num="56">[0045] While Figure 2 shows five PVCs <part-num-ref name="shows five PVCs">230</part-num-ref>
|
| 325 |
+
forming connections between each customer edge router <part-num-ref name="forming connections between each customer edge router">115</part-num-ref>
|
| 326 |
+
and provider edge router <part-num-ref name="and provider edge router">130,</part-num-ref>
|
| 327 |
+
different quantities of PVCs <part-num-ref name="and provider edge router 130, different quantities of PVCs">230</part-num-ref>
|
| 328 |
+
may be used to provide different amounts of bandwidth between the customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 329 |
+
and the provider edge routers <part-num-ref name="provider edge routers">130.</part-num-ref>
|
| 330 |
+
In one embodiment, each of the PVCs <part-num-ref name="PVCs">230</part-num-ref>
|
| 331 |
+
has a bandwidth capacity of approximately <part-num-ref name="bandwidth capacity of approximately">512</part-num-ref>
|
| 332 |
+
kilobits per second. </p>
|
| 333 |
+
<p id="p-57" num="57">[0046] The PVCs <part-num-ref name="PVCs">230</part-num-ref>
|
| 334 |
+
are arranged to provide links forming alternate paths over the access links <part-num-ref name="access links">140.</part-num-ref>
|
| 335 |
+
For example, PVC 230-1 forms a first link that makes up at least part of a first path over the access link 140-1. PVC 230-1 forms a second link that makes up at least part of a second path of the access link 140-1. PVC 230-2 may be configured as an alternate to PVC 230-1. </p>
|
| 336 |
+
<p id="p-58" num="58">Accordingly, when the PVC 230-1 reaches or exceeds a predetermined utilization threshold, the system <part-num-ref name="system">200</part-num-ref>
|
| 337 |
+
may be configured to reroute at least a <boundary-data type="header">
|
| 338 |
+
<confidence value="88">11</confidence>
|
| 339 |
+
</boundary-data>
|
| 340 |
+
<page-break num="13"/>
|
| 341 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="5">@</confidence>
|
| 342 |
+
EV 373627752 </boundary-data>
|
| 343 |
+
subset of data transmissions from PVC 230-1 to PVC 230-2. The rerouting of data transmissions based on link utilization rates will be discussed in more detail below. </p>
|
| 344 |
+
<p id="p-59" num="59">[0047] As with system 100 of Figure 1, in system <part-num-ref name="of Figure 1, in system">200,</part-num-ref>
|
| 345 |
+
the provider edge routers <part-num-ref name="provider edge routers">130</part-num-ref>
|
| 346 |
+
are in connection with the core routers <part-num-ref name="core routers">170</part-num-ref>
|
| 347 |
+
by the transport links <part-num-ref name="transport links">180,</part-num-ref>
|
| 348 |
+
and the core routers <part-num-ref name="core routers">170</part-num-ref>
|
| 349 |
+
are connected to each other by the core network link <part-num-ref name="core network link">190.</part-num-ref>
|
| 350 |
+
</p>
|
| 351 |
+
<p id="p-60" num="60">[0048] System 200 is configured so that data transmissions over the network framework <part-num-ref name="network framework">116</part-num-ref>
|
| 352 |
+
can be simulated and monitored. In order to simulate network parameters of operational networks, the system <part-num-ref name="system">200</part-num-ref>
|
| 353 |
+
may include software or other tools to inject network parameters such as packet loss, delay, jitter, and the like into data transmissions sent over paths of the network framework <part-num-ref name="network framework">116</part-num-ref>
|
| 354 |
+
of the system <part-num-ref name="system">200.</part-num-ref>
|
| 355 |
+
In particular, this allows the system <part-num-ref name="system">200</part-num-ref>
|
| 356 |
+
to emulate a long-haul core <confidence value="5">I</confidence>
|
| 357 |
+
P network. </p>
|
| 358 |
+
<p id="p-61" num="61">[0049] To illustrate the capabilities of the system <part-num-ref name="system">200</part-num-ref>
|
| 359 |
+
for simulating voice transmissions, an example of a voice transmission simulation scenario will now be described in detail. However, other types of data transmissions (e.g., video streams) may be simulated using the system <part-num-ref name="system">200.</part-num-ref>
|
| 360 |
+
While voice transmissions may flow over the network shown in Figure 2 in either direction (i.e., from the signal generator 110-<confidence value="6">1</confidence>
|
| 361 |
+
to the QoS monitor 195-2 and from the signal generator 110-2 to the QoS monitor 195-1), for purposes of explanation, simulations involving voice transmissions in the form of telephone calls generated by the signal generator 110-1 and received by the QoS monitor 195-2 will now be described. </p>
|
| 362 |
+
<p id="p-62" num="62">[0050] To enable voice traffic simulations, the signal generators <part-num-ref name="signal generators">110</part-num-ref>
|
| 363 |
+
are configured to simulate various traffic loads over one or more segments of any of the network paths formed by the system <part-num-ref name="system">200.</part-num-ref>
|
| 364 |
+
The path for the simulation example described herein is the path traveled by data streams transmitted from the signal generator 110-1 to the QoS monitor 195-2. The signal generator <part-num-ref name="signal generator">110</part-num-ref>
|
| 365 |
+
may include one or more load generators to produce different levels of traffic loads on the media path. Other devices in the system <part-num-ref name="system">200</part-num-ref>
|
| 366 |
+
may also include load generators for simulating traffic loads on particular segments of network paths of the system <part-num-ref name="system">200.</part-num-ref>
|
| 367 |
+
</p>
|
| 368 |
+
<boundary-data type="header">
|
| 369 |
+
<confidence value="88">12</confidence>
|
| 370 |
+
</boundary-data>
|
| 371 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="2">@</confidence>
|
| 372 |
+
EV 373627752 </boundary-data>
|
| 373 |
+
<p id="p-63" num="63">
|
| 374 |
+
<page-break num="14"/>
|
| 375 |
+
[0051] By generating various levels of traffic loads over a particular path, or particular segments of the path, the system <part-num-ref name="system">200</part-num-ref>
|
| 376 |
+
is able to measure voice quality in relation to traffic loads (i.e., link utilizations), as described below. </p>
|
| 377 |
+
<p id="p-64" num="64">Initial measurements may be taken with no load on the particular path in order to establish baseline network path properties. In one embodiment, the signal generator 110-1 is configured to generate and transmit different traffic loads for predefined time intervals so that measurements can be taken to help identify changes in QoS parameters as a function of varying traffic loads. For example, the signal generator 110-1 may produce traffic loads in twenty percent increments of bandwidth capacity.</p>
|
| 378 |
+
<p id="p-65" num="65">[0052] In one simulation scenario, three telephone calls are placed simultaneously by the signal generator 110-1. The telephone calls may comprise RTP streams generated by the signal generator 110-1 and sent over media particular network path to the signal generator 110-2 or the QoS monitor 195-2. The QoS monitor 195-2 is able to monitor end-to-end QoS parameters and other data associated with the telephone calls passing over the selected network path formed by the system <part-num-ref name="system">200.</part-num-ref>
|
| 379 |
+
Once measurements have been gathered for the three telephone calls, the number of telephone calls is increased to four telephone calls, and associated data gathered by the QoS monitor 195-2. Then the number of telephone calls is increased to five and associated data gathered by the QoS monitor 195-2. </p>
|
| 380 |
+
<p id="p-66" num="66">[0053] In one embodiment, the calls are placed in accordance with G.71<confidence value="88">1,</confidence>
|
| 381 |
+
which is known to those skilled in the art. A G.711-based telephone call typically utilizes approximately <part-num-ref name="G.711-based telephone call typically utilizes approximately">100</part-num-ref>
|
| 382 |
+
kilobits per second of bandwidth as it traverses a network path. In other voice data simulation scenarios, other telephone call protocols, such as G.729b, may be used. </p>
|
| 383 |
+
<p id="p-67" num="67">[0054] While the simulation example described herein includes the signal generator 110-1 providing IP-based voice signals, any known telephone call endpoint or transmission device may be connected with the system <part-num-ref name="system">200</part-num-ref>
|
| 384 |
+
and used to generate telephone calls over the call path formed by the system <part-num-ref name="system">200.</part-num-ref>
|
| 385 |
+
</p>
|
| 386 |
+
<p id="p-68" num="68">For example, the system <part-num-ref name="system">200</part-num-ref>
|
| 387 |
+
may be connected with time-division multiplexing (TDM) devices, class-<confidence value="5">5</confidence>
|
| 388 |
+
switches, SS7 devices, PSTN devices, servers, IP/PSTN gateways, and other known telephony devices. Further, simulated voice traffic may be generated and received by different call <boundary-data type="header">
|
| 389 |
+
<confidence value="88">13</confidence>
|
| 390 |
+
</boundary-data>
|
| 391 |
+
<page-break num="15"/>
|
| 392 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="4">®</confidence>
|
| 393 |
+
EV 373627752 </boundary-data>
|
| 394 |
+
endpoints and devices in connection with the network framework <part-num-ref name="network framework">116</part-num-ref>
|
| 395 |
+
of the system <part-num-ref name="system">200.</part-num-ref>
|
| 396 |
+
Other types of devices may also be used for simulations of different types of data transmissions. </p>
|
| 397 |
+
<p id="p-69" num="69">[0055] By simulating various loads of voice traffic over a network path (or segments of the network path), the system <part-num-ref name="system">200</part-num-ref>
|
| 398 |
+
is able to provide measurements of voice quality. The measurements of voice quality may be in terms of QoS parameters, including MOS, PESQ, delay, jitter, and packet loss, which are helpful for analyzing the network characteristics and performance of the media path. As known to those skilled in the art, these QoS parameters affect the voice quality of Vo<confidence value="5">I</confidence>
|
| 399 |
+
P transmissions. For example, packet loss over a one-hop network typically should not exceed one percent of the transmitted packets. Similarly, MOS should be 4.0 or greater for toll- quality voice services. </p>
|
| 400 |
+
<p id="p-70" num="70">[0056] Measurements of end-to-end QoS parameters may be obtained by the QoS monitors <part-num-ref name="QoS monitors">195</part-num-ref>
|
| 401 |
+
for simulated traffic loads. The QoS parameters provide a quantified measure of voice quality and can be used to analyze voice quality based on bandwidth utilization of links of network path formed by the system <part-num-ref name="system">200.</part-num-ref>
|
| 402 |
+
For this analysis, link utilization rates of the links of the particular network path are monitored. While the system <part-num-ref name="system">200</part-num-ref>
|
| 403 |
+
may be configured to monitor utilization rates on any of the links forming any of the paths over the network framework <part-num-ref name="network framework">116,</part-num-ref>
|
| 404 |
+
Figure 2 shows an example of the ingress link 140-1 being monitored by the link utilization monitor 150-1 because the ingress link 140-1 is the bottleneck (i.e., the lowest bandwidth capacity) link of the system <part-num-ref name="system">200.</part-num-ref>
|
| 405 |
+
Because the ingress link 140-1 has the lowest bandwidth capacity of the different links of the network framework <part-num-ref name="network framework">116,</part-num-ref>
|
| 406 |
+
the bandwidth utilization of the ingress link 140-1 prominently affects the QoS of data transmissions. As shown in Figure 2, the link utilization monitor 150-2 should similarly monitor the bandwidth utilization of the egress link 140-2. </p>
|
| 407 |
+
<p id="p-71" num="71">[0057] As simulated telephone calls are transmitted from the signal generator 110-1, over the ingress link 140-1, and to the signal generator 110- <part-num-ref name="signal generator 110-">2</part-num-ref>
|
| 408 |
+
or the QoS monitor 195-2, the utilization rate of the ingress link 140-1 is monitored and compared with the QoS parameters measured by the QoS monitor 195-2 to determine the link utilization rates at which the measured QoS parameters are identified as deteriorating below desired quality <boundary-data type="header">
|
| 409 |
+
<confidence value="88">14</confidence>
|
| 410 |
+
</boundary-data>
|
| 411 |
+
<page-break num="16"/>
|
| 412 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="4">®</confidence>
|
| 413 |
+
EV 373627752 </boundary-data>
|
| 414 |
+
thresholds (e.g., a toll-grade MOS or a specific packet-loss rate). Figures <part-num-ref name="specific packet-loss rate). Figures">3</part-num-ref>
|
| 415 |
+
and <part-num-ref name="and">4</part-num-ref>
|
| 416 |
+
illustrate measured relationships of QoS parameters and link utilization rates for the voice transmission simulation scenario described above. </p>
|
| 417 |
+
<p id="p-72" num="72">[0058] Figure 3 is a chart of the determined MOS value per telephone call for the above-described voice transmission simulation scenario. Figure 3 illustrates determined MOS values corresponding to when three, four, and five active telephone calls are simulated over the network framework <part-num-ref name="network framework">116.</part-num-ref>
|
| 418 |
+
The vertical axis of the chart represents the MOS value, and the x-axis of the chart represents the number of samples that were taken for each simulation. As shown in plot <part-num-ref name="number of samples that were taken for each simulation. As shown in plot">310</part-num-ref>
|
| 419 |
+
of Figure 3, for the case in which three telephone calls are transmitted over a single PVC 230-1 of the ingress link 140-1, the determined MOS for each call remains steady at a value of approximately 4.45. </p>
|
| 420 |
+
<p id="p-73" num="73">[0059] As the number of active telephone calls over the network framework <part-num-ref name="network framework">116</part-num-ref>
|
| 421 |
+
is increased to four, degradation in call quality is observed. As shown by plot <part-num-ref name="is increased to four, degradation in call quality is observed. As shown by plot">320</part-num-ref>
|
| 422 |
+
in Figure 3, several mean opinion scores have dropped below a value of approximately 3.0. As the number of telephone calls is increased to five, voice quality is even more severely degraded. As shown by plot <part-num-ref name="number of telephone calls is increased to five, voice quality is even more severely degraded. As shown by plot">330</part-num-ref>
|
| 423 |
+
in Figure 3, several telephone calls now have MOS values below 2.5. The relatively lower MOS values shown in Figure 3 for quantities of four and five telephone calls is attributable to the packet loss and delay experienced by the data packets of the voice transmission streams as the PVC 230-1 of the ingress link 140-1 over which the data packets are traveling becomes more congested (i.e., higher utilization rates). The relationship of MOS to packet loss and link utilization is further illustrated in Figure 4. </p>
|
| 424 |
+
<p id="p-74" num="74">[0060] As shown in Figure 4, average packet loss increases as the number of telephone calls over the network framework <part-num-ref name="network framework">116</part-num-ref>
|
| 425 |
+
increases (i.e., link utilization increases). In Figure 4, plot <part-num-ref name="link utilization increases). In Figure 4, plot">410</part-num-ref>
|
| 426 |
+
represents the link utilization of PVC 230-1 as a percentage of the bandwidth capacity of PVC 230-1, and plot <part-num-ref name="bandwidth capacity of PVC 230-1, and plot">420</part-num-ref>
|
| 427 |
+
represents average percentage of the data packets of the telephone call data streams that are lost during transmission. Measurements of link utilization and packet loss are shown for three, four, and five telephone calls being active over the network framework <part-num-ref name="network framework">116.</part-num-ref>
|
| 428 |
+
The x-axis of the chart of Figure 4 represents the number of active calls being simulated. </p>
|
| 429 |
+
<boundary-data type="header">
|
| 430 |
+
<confidence value="88">15</confidence>
|
| 431 |
+
</boundary-data>
|
| 432 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="4">®</confidence>
|
| 433 |
+
EV 373627752 </boundary-data>
|
| 434 |
+
<p id="p-75" num="75">
|
| 435 |
+
<page-break num="17"/>
|
| 436 |
+
[0061] As shown in Figure 4, when three telephone calls are transmitted over PVC 230-1, approximately 62% of the bandwidth capacity of the PVC 230-1 is used, and no measurable amount of packet loss is observed. When four telephone calls are transmitted, a link utilization rate of approximately 83% for PVC 230-1 and a packet loss of approximately 0.001% are observed. </p>
|
| 437 |
+
<p id="p-76" num="76">In the case of five telephone calls being transmitted, a packet loss of approximately 2.6% is observed, and the link utilization rate of PVC 230-1 is approximately 103%. Thus, at five telephone calls, the link utilization rate exceeds the link capacity by approximately three percent.</p>
|
| 438 |
+
<p id="p-77" num="77">[0062] From Figures 3 and <part-num-ref name="and">4,</part-num-ref>
|
| 439 |
+
as well as the simulation described above, it can be seen that as link utilization increases beyond a certain utilization threshold, several of the telephone calls currently admitted for transmission over the network framework <part-num-ref name="network framework">116</part-num-ref>
|
| 440 |
+
of system <part-num-ref name="of system">200</part-num-ref>
|
| 441 |
+
experience degradation in voice quality. Key utilization rates associated with voice quality deteriorations can be determined from the telephone call simulations of the system <part-num-ref name="system">200.</part-num-ref>
|
| 442 |
+
For example, when PSTN-grade call quality (MOS of approximately 4.0 or greater) is desired, Figures <part-num-ref name="system 200. For example, when PSTN-grade call quality (MOS of approximately 4.0 or greater) is desired, Figures">3</part-num-ref>
|
| 443 |
+
and <part-num-ref name="and">4</part-num-ref>
|
| 444 |
+
show that a link utilization rate not greater than approximately 60% along the ingress link 140-1 will consistently maintain a MOS that is satisfactory for PSTN-grade quality. This relationship is determined based on the measured data for three active telephone calls over PVC 230-1 of the network framework <part-num-ref name="network framework">116.</part-num-ref>
|
| 445 |
+
Observation of QoS parameters for three telephone calls identified consistently acceptable MOS values above PSTN-grade call quality and a corresponding link utilization rate of approximately 62% of link capacity. </p>
|
| 446 |
+
<p id="p-78" num="78">[0063] The simulation scenario described above is merely illustrative.</p>
|
| 447 |
+
<p id="p-79" num="79">System 200 is able to simulate various voice traffic loads (i.e., link utilization rates) along any different path segment of the network framework, including any of the PVC <part-num-ref name="PVC">230.</part-num-ref>
|
| 448 |
+
Further, data types other than voice transmissions may be simulated. Accordingly, operators are able to use the system <part-num-ref name="system">200</part-num-ref>
|
| 449 |
+
to identify link utilization rates of network links (e.g., a bottleneck link) that correspond with degradations in data transmission quality below desired levels. </p>
|
| 450 |
+
<p id="p-80" num="80">[0064] The identified utilization rates may be used as link utilization thresholds for maintaining desired quality levels by limiting link utilization to <boundary-data type="header">
|
| 451 |
+
<confidence value="88">16</confidence>
|
| 452 |
+
</boundary-data>
|
| 453 |
+
<page-break num="18"/>
|
| 454 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="4">®</confidence>
|
| 455 |
+
EV 373627752 </boundary-data>
|
| 456 |
+
rates that do not exceed the link utilization thresholds. To maintain desired quality levels, the system <part-num-ref name="system">200</part-num-ref>
|
| 457 |
+
may provide for adjusting the amount of active bandwidth by activating and/or de-activating network links in order to maintain link utilization rates below the predetermined link utilization thresholds. The adjusting of active bandwidth based on predetermined link utilization thresholds can be implemented in the systems <part-num-ref name="systems">100</part-num-ref>
|
| 458 |
+
and <part-num-ref name="and">200,</part-num-ref>
|
| 459 |
+
as well as in operational networks having frameworks similar to those of systems <part-num-ref name="and 200, as well as in operational networks having frameworks similar to those of systems">100</part-num-ref>
|
| 460 |
+
and <part-num-ref name="and">200,</part-num-ref>
|
| 461 |
+
as discussed below. </p>
|
| 462 |
+
<heading id="h-12">
|
| 463 |
+
<confidence value="888">III</confidence>
|
| 464 |
+
. MAINTAINING LINK UTILIZATION RATES </heading>
|
| 465 |
+
<p id="p-81" num="81">[0065] Returning to Figure 2, once data traffic simulations have been performed and the link utilization thresholds determined, the link utilization thresholds may be integrated into the system <part-num-ref name="system">200</part-num-ref>
|
| 466 |
+
to maintain desired levels of data transmission quality. This can be done by configuring the system <part-num-ref name="system">200</part-num-ref>
|
| 467 |
+
to maintain link utilization rates at or below the link utilization thresholds. As a result, QoS parameters of voice services will not deteriorate below desired quality thresholds. </p>
|
| 468 |
+
<p id="p-82" num="82">[0066] As data streams are transmitted over a particular path of the network framework <part-num-ref name="network framework">116,</part-num-ref>
|
| 469 |
+
link utilization rates are monitored for selected links. </p>
|
| 470 |
+
<p id="p-83" num="83">For example, the link utilization monitor 150-1 is configured to monitor link utilization rates of any of the PVCs <part-num-ref name="PVCs">230</part-num-ref>
|
| 471 |
+
of the ingress link 140-1. The system <part-num-ref name="system">200</part-num-ref>
|
| 472 |
+
compares the monitored link utilization rates with the link utilization thresholds. If the link utilization rates exceed the link utilization thresholds, the system <part-num-ref name="system">200</part-num-ref>
|
| 473 |
+
recognizes that additional bandwidth should be provided to reduce the link utilization rate of the link(s) being monitored. The system <part-num-ref name="system">200</part-num-ref>
|
| 474 |
+
is able to provide notice to network operators to indicate that additional bandwidth should be activated. Additional bandwidth may be activated by operators using interfaces with the edge router <part-num-ref name="edge router">220</part-num-ref>
|
| 475 |
+
of Figure 2. It is also anticipated that known techniques may be implemented in the system <part-num-ref name="system">200</part-num-ref>
|
| 476 |
+
for automatically activating additional bandwidth in response to link utilization rates exceeding predetermined thresholds. </p>
|
| 477 |
+
<p id="p-84" num="84">[0067] To illustrate the maintaining of data transmission quality by managing bandwidth in response to monitored link utilization rates, reference may be made to the link utilization rates of the ingress link 140-1 of the <boundary-data type="header">
|
| 478 |
+
<confidence value="88">17</confidence>
|
| 479 |
+
</boundary-data>
|
| 480 |
+
<page-break num="19"/>
|
| 481 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="4">®</confidence>
|
| 482 |
+
EV 373627752 </boundary-data>
|
| 483 |
+
system <part-num-ref name="system">200.</part-num-ref>
|
| 484 |
+
For the simulation scenario described above, a link utilization threshold is identified for the ingress link 140-1. Based on the measurements shown in Figures <part-num-ref name="measurements shown in Figures">3</part-num-ref>
|
| 485 |
+
and <part-num-ref name="and">4,</part-num-ref>
|
| 486 |
+
in one embodiment the link utilization threshold may be set to approximately 60% because at a link utilization rate of approximately 62%, the MOS values for each telephone call remains above PSTN-grade quality (MOS of 4.0). However, at a utilization rate of approximately 83%, several telephone calls exhibit MOS values below PSTN- grade quality. That is, the MOS values of all calls degrade since transmission capacity is shared by all the sessions (calls). </p>
|
| 487 |
+
<p id="p-85" num="85">[0068] The determined link utilization threshold (e.g., approximately 60%) may be implemented in the system <part-num-ref name="system">200</part-num-ref>
|
| 488 |
+
in order to maintain link utilization rates not in excess of the threshold. As data streams are transmitted over the ingress link 140-1, the link utilization monitor 150-1 monitors the utilization rate of the access link 140-1. More specifically, the link utilization monitor 150-1 monitors the link utilization rate of each active PVC <part-num-ref name="link utilization rate of each active PVC">230</part-num-ref>
|
| 489 |
+
of the ingress link 140-1. When the link utilization monitor 150-1 determines that a link utilization rate of an active PVC <part-num-ref name="active PVC">230</part-num-ref>
|
| 490 |
+
has exceeded the predetermined utilization threshold, the system <part-num-ref name="system">200</part-num-ref>
|
| 491 |
+
may activate one or more additional PVCs <part-num-ref name="may activate one or more additional PVCs">230</part-num-ref>
|
| 492 |
+
of the ingress link 140-1 in order to increase the amount of available bandwidth. Telephone calls may then be rerouted over the newly activated PVCs <part-num-ref name="newly activated PVCs">230</part-num-ref>
|
| 493 |
+
to decrease the utilization rate of the monitored PVC <part-num-ref name="monitored PVC">230.</part-num-ref>
|
| 494 |
+
</p>
|
| 495 |
+
<p id="p-86" num="86">[0069] Conversely, minimum link utilization thresholds may be implemented to prevent an excessive number of PVCs <part-num-ref name="excessive number of PVCs">230</part-num-ref>
|
| 496 |
+
from remaining active when utilization rates are low. For example, if three PVCs <part-num-ref name="from remaining active when utilization rates are low. For example, if three PVCs">230</part-num-ref>
|
| 497 |
+
are active and carrying telephone calls at low enough rates that two PVCs <part-num-ref name="are active and carrying telephone calls at low enough rates that two PVCs">230</part-num-ref>
|
| 498 |
+
could transmit the calls without exceeding the predetermined maximum utilization thresholds, then one of the active PVCs <part-num-ref name="active PVCs">230</part-num-ref>
|
| 499 |
+
may be deactivated to conserve network resources. </p>
|
| 500 |
+
<p id="p-87" num="87">[0070] PVCs 230 may be activated and deactivated using techniques known to those skilled in the art. In the system <part-num-ref name="system">200</part-num-ref>
|
| 501 |
+
of Figure 2, the customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 502 |
+
and/or provider edge routers <part-num-ref name="and/or provider edge routers">130</part-num-ref>
|
| 503 |
+
may be configured to activate and deactivate the PVCs <part-num-ref name="PVCs">230</part-num-ref>
|
| 504 |
+
between them. As known to those skilled in the art, interfaces (not shown) to the customer edge routers <part-num-ref name="customer edge routers">115</part-num-ref>
|
| 505 |
+
and/or the provider edge routers <part-num-ref name="provider edge routers">130</part-num-ref>
|
| 506 |
+
may be provided to allow network <boundary-data type="header">
|
| 507 |
+
<confidence value="88">18</confidence>
|
| 508 |
+
</boundary-data>
|
| 509 |
+
<page-break num="20"/>
|
| 510 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="2">@</confidence>
|
| 511 |
+
EV 373627752 </boundary-data>
|
| 512 |
+
operators to control the activation and/or deactivation of the PVCs <part-num-ref name="PVCs">230.</part-num-ref>
|
| 513 |
+
</p>
|
| 514 |
+
<p id="p-88" num="88">Accordingly, the system <part-num-ref name="system">200</part-num-ref>
|
| 515 |
+
may be configured to provide notification to network providers when it is determined that available bandwidth should be increased or decreased to appropriately accommodate the monitored link utilization rates. In this manner, resources are managed based on the monitored link utilization rates, and data transmission quality is maintained at desired levels. </p>
|
| 516 |
+
<p id="p-89" num="89">[0071] It is also anticipated that known or future techniques for automatically activating and deactivating available link bandwidth may be used in the system <part-num-ref name="system">200</part-num-ref>
|
| 517 |
+
to automatically manage available bandwidth based on monitored utilization rates. </p>
|
| 518 |
+
<p id="p-90" num="90">[0072] The above-described example of identifying and using link utilization thresholds to maintain QoS levels is merely illustrative. Different link utilization thresholds may be identified and implemented for different segments of different networks and for different types and mixes of data transmissions. Further, different QoS parameters, or different combinations of QoS parameters, may be monitored as used as thresholds to maintain data transmission quality above desired levels. For example, packet loss thresholds may be determined, monitored, and used to maintain desired levels of data transmission quality. In addition, other techniques for adjusting active or available bandwidth based on monitored QoS parameters may be used in some embodiments.</p>
|
| 519 |
+
<p id="p-91" num="91">[0073] The techniques described above for maintaining desired levels of quality for data transmissions are not limited to use with the systems <part-num-ref name="systems">100</part-num-ref>
|
| 520 |
+
and <part-num-ref name="and">200.</part-num-ref>
|
| 521 |
+
The QoS parameter thresholds (e.g., link utilization thresholds) determined using the systems <part-num-ref name="systems">100</part-num-ref>
|
| 522 |
+
and <part-num-ref name="and">200</part-num-ref>
|
| 523 |
+
can also be implemented in operational networks having designs similar (e.g., having a similar number of call legs) to the network frameworks <part-num-ref name="network frameworks">116</part-num-ref>
|
| 524 |
+
used for simulating data traffic to determine QoS parameter thresholds, as described above. For example, Figure 5 is a block diagram of a network <part-num-ref name="network">500</part-num-ref>
|
| 525 |
+
that can be used as a test bed network as described above in relation to systems <part-num-ref name="test bed network as described above in relation to systems">100</part-num-ref>
|
| 526 |
+
and <part-num-ref name="and">200</part-num-ref>
|
| 527 |
+
and/or as an operational network configured to maintain and deliver a desired level of quality by adjusting the available bandwidth of network links (e.g., a bottleneck link) based on predetermined link utilization thresholds. While <boundary-data type="header">
|
| 528 |
+
<confidence value="88">19</confidence>
|
| 529 |
+
</boundary-data>
|
| 530 |
+
<page-break num="21"/>
|
| 531 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="4">®</confidence>
|
| 532 |
+
EV 373627752 </boundary-data>
|
| 533 |
+
Figure 5 shows the network <part-num-ref name="network">500</part-num-ref>
|
| 534 |
+
being used to transmit voice services transmissions, those skilled in the art will understand that the network <part-num-ref name="network">500</part-num-ref>
|
| 535 |
+
may be used to maintain desired quality levels for other types of data, or various mixes of different types of data, being transmitted over the network <part-num-ref name="network">500.</part-num-ref>
|
| 536 |
+
</p>
|
| 537 |
+
<p id="p-92" num="92">A. Layer-2 Aggregation Switch [0074] The network <part-num-ref name="network">500</part-num-ref>
|
| 538 |
+
includes <confidence value="5">l</confidence>
|
| 539 |
+
ayer-2 aggregation switches 510-1 and 510-2 (collectively <confidence value="66">"L</confidence>
|
| 540 |
+
2 aggregation switches 510") arranged to communicate with data endpoints, including IP endpoints 515-1 and 515-2 (collectively "IP endpoints 515") and TDM endpoints 520-1 and 520-2 (collectively "T<confidence value="68">DM</confidence>
|
| 541 |
+
endpoints 520"). The L2 aggregation switches <part-num-ref name="L2 aggregation switches">510</part-num-ref>
|
| 542 |
+
are configured to receive voice transmissions generated by the data endpoints and direct the voice transmissions over the access links <part-num-ref name="access links">140</part-num-ref>
|
| 543 |
+
to appropriate provider edge routers <part-num-ref name="to appropriate provider edge routers">130.</part-num-ref>
|
| 544 |
+
The L2 aggregation switches <part-num-ref name="L2 aggregation switches">510</part-num-ref>
|
| 545 |
+
may include devices known in the art for receiving and directing data transmissions. </p>
|
| 546 |
+
<p id="p-93" num="93">B. IP Endpoints [0075] The IP endpoints <part-num-ref name="IP endpoints">515</part-num-ref>
|
| 547 |
+
can include any known device or devices for generating, transmitting, and/or receiving voice packet data transmissions, including but not limited to known IP telephones (e.g., session initiation protocol (SIP) telephones), servers, and integrated access devices (<confidence value="5">I</confidence>
|
| 548 |
+
ADs) capable of transmitting and receiving voice packet data streams. </p>
|
| 549 |
+
<p id="p-94" num="94">C. TDM Endpoints [0076] The T<confidence value="5">D</confidence>
|
| 550 |
+
M endpoints <part-num-ref name="TDM endpoints">520</part-num-ref>
|
| 551 |
+
can include any known device or devices for generating, transmitting, and/or receiving TDM and/or PSTN voice transmissions, including but not limited to standard telephones known to those skilled in the art. </p>
|
| 552 |
+
<p id="p-95" num="95">[0077] The TDM endpoints <part-num-ref name="TDM endpoints">520</part-num-ref>
|
| 553 |
+
are connected to the L2 aggregation switches <part-num-ref name="L2 aggregation switches">510</part-num-ref>
|
| 554 |
+
by internet protocol to public-switched telephone network (IP/PSTN) gateways 525-1 and 525-2, which are known to those skilled in the art. The T<confidence value="5">D</confidence>
|
| 555 |
+
M endpoint 520-2 shown in Figure 5 is connected to the IP/PSTN gateway 525-2 by a public-switched telephone network (PSTN) <part-num-ref name="public-switched telephone network (PSTN)">530</part-num-ref>
|
| 556 |
+
as will be understood to those skilled in the art. </p>
|
| 557 |
+
<p id="p-96" num="96">[0078] Although not shown in Figure 5, other known call endpoints and transmission points may be connected with the network <part-num-ref name="network">500</part-num-ref>
|
| 558 |
+
and configured to <boundary-data type="header">
|
| 559 |
+
<confidence value="88">20</confidence>
|
| 560 |
+
</boundary-data>
|
| 561 |
+
<page-break num="22"/>
|
| 562 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="4">®</confidence>
|
| 563 |
+
EV 373627752 </boundary-data>
|
| 564 |
+
send and/or receive voice data transmissions over the network <part-num-ref name="network">500.</part-num-ref>
|
| 565 |
+
For example, PSTN connections to the network <part-num-ref name="network">500</part-num-ref>
|
| 566 |
+
may include but are not limited to SS7 links to signal transfer points (STPs), or T<confidence value="665">1/I</confidence>
|
| 567 |
+
MT and FX links to class-<confidence value="5">5</confidence>
|
| 568 |
+
switches, which will be understood by those skilled in the <confidence value="6688">art.</confidence>
|
| 569 |
+
</p>
|
| 570 |
+
<p id="p-97" num="97">D. Softswitch [0079] A softswitch <part-num-ref name="softswitch">540</part-num-ref>
|
| 571 |
+
is in connection with the layer-2 aggregation switch 510-2 and is configured with instructions for controlling the routing of voice transmissions to appropriate provider edge routers <part-num-ref name="routing of voice transmissions to appropriate provider edge routers">130</part-num-ref>
|
| 572 |
+
for ingress signals and to appropriate call endpoints for egress signals. The softswitch <part-num-ref name="softswitch">540</part-num-ref>
|
| 573 |
+
is able to control routing performed at the layer-2 aggregation softswitches 510-1 and 510-2. The softswitch <part-num-ref name="softswitch">540</part-num-ref>
|
| 574 |
+
may be implemented using devices known to those skilled in the art. </p>
|
| 575 |
+
<p id="p-98" num="98">E. Provider Edge Router [0080] The provider edge routers <part-num-ref name="provider edge routers">130</part-num-ref>
|
| 576 |
+
implemented in the network <part-num-ref name="network">500</part-num-ref>
|
| 577 |
+
shown in Figure 5 are configured to receive data streams (e.g., telephone calls) from the L2 aggregation switches <part-num-ref name="L2 aggregation switches">510</part-num-ref>
|
| 578 |
+
and to route the data streams over the transport links <part-num-ref name="transport links">180</part-num-ref>
|
| 579 |
+
to the core routers <part-num-ref name="core routers">170</part-num-ref>
|
| 580 |
+
for transmission over a core network <part-num-ref name="core network">550.</part-num-ref>
|
| 581 |
+
For data streams traveling through the provider edge routers <part-num-ref name="provider edge routers">130</part-num-ref>
|
| 582 |
+
in the opposite direction (i.e., from provider edge routers <part-num-ref name="from provider edge routers">130</part-num-ref>
|
| 583 |
+
toward the call endpoints, the provider edge routers <part-num-ref name="provider edge routers">130</part-num-ref>
|
| 584 |
+
are configured to route the data streams to appropriate L2 aggregate switches <part-num-ref name="data streams to appropriate L2 aggregate switches">510.</part-num-ref>
|
| 585 |
+
</p>
|
| 586 |
+
<p id="p-99" num="99">[0081] As discussed above, the provider edge routers <part-num-ref name="provider edge routers">130</part-num-ref>
|
| 587 |
+
implemented in the operation network of Figure 5 may comprise virtual routers configured to activate and deactivate links making up the access links <part-num-ref name="access links">140</part-num-ref>
|
| 588 |
+
and connecting the provider edge routers <part-num-ref name="provider edge routers">130</part-num-ref>
|
| 589 |
+
with the L2 aggregation switches <part-num-ref name="L2 aggregation switches">510.</part-num-ref>
|
| 590 |
+
</p>
|
| 591 |
+
<p id="p-100" num="100">F. Core Network [0082] The core network <part-num-ref name="core network">550</part-num-ref>
|
| 592 |
+
may comprise any known packet-switched network capable of carrying packet data streams (e.g., voice-over-IP data streams). The core network <part-num-ref name="core network">550</part-num-ref>
|
| 593 |
+
may comprise an IP, multi-protocol label- switched (MPLS), and/or IP/MPLS network or networks. </p>
|
| 594 |
+
<p id="p-101" num="101">[0083] To maintain the quality of data transmitted over the network <part-num-ref name="network">500,</part-num-ref>
|
| 595 |
+
link utilization rates of the network links may be monitored as discussed above. For example, for data streams traveling from layer-2 aggregation switch 510-<confidence value="6">1</confidence>
|
| 596 |
+
to provider edge router 130-1, the link utilization monitor 150-1 <boundary-data type="header">
|
| 597 |
+
<confidence value="88">21</confidence>
|
| 598 |
+
</boundary-data>
|
| 599 |
+
<page-break num="23"/>
|
| 600 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="4">®</confidence>
|
| 601 |
+
EV 373627752 </boundary-data>
|
| 602 |
+
monitors the link utilization of the ingress link 140-1. When the link utilization monitor 150-1 detects a link utilization rate as having exceeded a predetermined utilization threshold, the steps discussed above may be executed to maintain utilization of the ingress link 140-1 below the predetermined utilization threshold. If link utilization rates exceed the predetermined utilization threshold, for example, additional bandwidth may be activated, as discussed above. In a similar manner, if link utilization rates are below predetermined minimum thresholds, bandwidth may be deactivated as long as the bandwidth remaining active is sufficient to maintain utilization rates at or below the predetermined maximum utilization thresholds. </p>
|
| 603 |
+
<heading id="h-13">IV. PROCESS FLOW VIEWS</heading>
|
| 604 |
+
<p id="p-102" num="102">[0084] Figures 6 and <part-num-ref name="and">7</part-num-ref>
|
| 605 |
+
illustrate examples of methods of determining appropriate link utilization thresholds useful for maintaining QoS levels of data transmissions by allocating bandwidth based on monitored link utilization rates. While the methods of Figures <part-num-ref name="methods of Figures">6</part-num-ref>
|
| 606 |
+
and <part-num-ref name="and">7</part-num-ref>
|
| 607 |
+
are directed to bottleneck links of a network, those skilled in the art will understand that the steps of the methods may be applied to other network links. </p>
|
| 608 |
+
<p id="p-103" num="103">[0085] Figure 6 is a flowchart illustrating a method of identifying a link utilization threshold for a bottleneck link of the system <part-num-ref name="system">100</part-num-ref>
|
| 609 |
+
of Figure 1. As shown in Figure 6, data traffic is simulated over the bottleneck link at step <part-num-ref name="bottleneck link at step">605.</part-num-ref>
|
| 610 |
+
Step <part-num-ref name="bottleneck link at step 605. Step">605</part-num-ref>
|
| 611 |
+
may be performed according to the description of simulating data transmissions over the network framework <part-num-ref name="network framework">116</part-num-ref>
|
| 612 |
+
described above. QoS parameters associated with the simulated data traffic are monitored at step <part-num-ref name="simulated data traffic are monitored at step">610.</part-num-ref>
|
| 613 |
+
The QoS parameters may be monitored at the bottleneck link (e.g., the ingress link 140-1) of a network designed for simulating data transmissions over packet-switched networks, as discussed above. While potentially any QoS parameter(s) may be monitored at step <part-num-ref name="network designed for simulating data transmissions over packet-switched networks, as discussed above. While potentially any QoS parameter(s) may be monitored at step">610,</part-num-ref>
|
| 614 |
+
in one embodiment bandwidth utilization rate of at least one link is monitored. </p>
|
| 615 |
+
<p id="p-104" num="104">[0086] At step 620, it is determined whether the monitored QoS parameters are above predetermined quality thresholds. The predetermined quality thresholds may be defined by a network operator based on particular applications of the network. A network operator may set a predetermined quality threshold to correspond with a desired level of service. For example, a <boundary-data type="header">
|
| 616 |
+
<confidence value="88">22</confidence>
|
| 617 |
+
</boundary-data>
|
| 618 |
+
<page-break num="24"/>
|
| 619 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="2">@</confidence>
|
| 620 |
+
EV 373627752 </boundary-data>
|
| 621 |
+
network operator may set a threshold value for QoS parameters such as packet loss, bandwidth utilization rate, transmission delay, jitter, or any other parameter useful for measuring quality of data transmissions. For a Vo<confidence value="68">IP</confidence>
|
| 622 |
+
application for example, a predetermined quality threshold may be set to a MOS value of 4.0 for PSTN-grade voice transmissions. If it is determined at step <part-num-ref name="MOS value of 4.0 for PSTN-grade voice transmissions. If it is determined at step">620</part-num-ref>
|
| 623 |
+
that QoS parameters are above the predetermined quality thresholds, as defined by a network operator, processing returns to step <part-num-ref name="network operator, processing returns to step">610</part-num-ref>
|
| 624 |
+
for continued monitoring of QoS parameters. </p>
|
| 625 |
+
<p id="p-105" num="105">[0087] On the other hand, if it is determined at step <part-num-ref name="other hand, if it is determined at step">620</part-num-ref>
|
| 626 |
+
that the monitored QoS parameters are not above the predetermined quality thresholds, processing moves to step <part-num-ref name="predetermined quality thresholds, processing moves to step">630.</part-num-ref>
|
| 627 |
+
At step <part-num-ref name="predetermined quality thresholds, processing moves to step 630. At step">630,</part-num-ref>
|
| 628 |
+
a link utilization rate of a bottleneck link is identified, as discussed above. The link utilization rate corresponds with the utilization rate at which the QoS parameters deteriorate below the predetermined quality thresholds. The link utilization rate may be implemented in networks as a link utilization threshold to maintain the quality of the QoS parameters, as shown in Figure 7. </p>
|
| 629 |
+
<p id="p-106" num="106">[0088] Figure 7 is a flowchart illustrating a method of maintaining QoS levels for data transmissions based on the link utilization rates determined in Figure 6. At step <part-num-ref name="link utilization rates determined in Figure 6. At step">710,</part-num-ref>
|
| 630 |
+
the bottleneck link of a network is identified. This determination may be based on bandwidth capacity. The bottleneck link is typically the ingress link 140-1 of a network. Processing then moves to step <part-num-ref name="network. Processing then moves to step">720,</part-num-ref>
|
| 631 |
+
at which step bandwidth utilization rates of the bottleneck link are monitored, as discussed above. </p>
|
| 632 |
+
<p id="p-107" num="107">[0089] At step 730, it is determined whether the determined link utilization rate has exceeded a predetermined utilization threshold. If it is found at step <part-num-ref name="predetermined utilization threshold. If it is found at step">730</part-num-ref>
|
| 633 |
+
that the utilization rate has not exceeded the predetermined utilization threshold, processing returns to step <part-num-ref name="predetermined utilization threshold, processing returns to step">720</part-num-ref>
|
| 634 |
+
for continued monitoring of the utilization rates. </p>
|
| 635 |
+
<p id="p-108" num="108">[0090] On the other hand, if it is determined at step <part-num-ref name="other hand, if it is determined at step">730</part-num-ref>
|
| 636 |
+
that the utilization rate has exceeded the predetermined utilization threshold, processing moves to step <part-num-ref name="predetermined utilization threshold, processing moves to step">740.</part-num-ref>
|
| 637 |
+
At step <part-num-ref name="predetermined utilization threshold, processing moves to step 740. At step">740,</part-num-ref>
|
| 638 |
+
additional bandwidth is activated and data transmissions rerouted to distribute the data streams being transmitted over the ingress link 140-1 among additional links, thereby maintaining utilization <boundary-data type="header">
|
| 639 |
+
<confidence value="88">23</confidence>
|
| 640 |
+
</boundary-data>
|
| 641 |
+
<page-break num="25"/>
|
| 642 |
+
<boundary-data type="header">Docket No. 04-1507 ExpressMail<confidence value="2">@</confidence>
|
| 643 |
+
EV 373627752 </boundary-data>
|
| 644 |
+
rates below the predetermined utilization thresholds. Processing then returns to step <part-num-ref name="predetermined utilization thresholds. Processing then returns to step">720</part-num-ref>
|
| 645 |
+
for continued monitoring of the utilization rates. </p>
|
| 646 |
+
<p id="p-109" num="109">[0091] By activating and deactivating bandwidth based on utilization rates and utilization thresholds, desired levels of data transmission quality are maintained and delivered while using an appropriate amount of bandwidth resources for the measured amounts of traffic on network links. Bandwidth can be activated as traffic load increases so that additional data streams are not rejected from network admission based on priority. In some embodiments, known admission controls can be made secondary to the bandwidth utilization techniques discussed herein so that data streams will not be rejected from admission to the network unless traffic loads are extreme enough that all available bandwidth is active and being utilized at or near the determined utilization thresholds.</p>
|
| 647 |
+
<heading id="h-14">V. ALTERNATIVE EMBODIMENTS</heading>
|
| 648 |
+
<p id="p-110" num="110">[0092] The preceding description has been presented only to illustrate and describe embodiments of the invention. It is not intended to be exhaustive or to limit the invention to any precise form disclosed. The invention may be practiced otherwise than is specifically explained and illustrated without departing from its spirit or scope. For example, while several examples relating to voice services transmissions of IP networks have been described herein, the invention may be practiced for different types of data transmissions. It is intended that the scope of the invention be defined by the following claims.</p>
|
| 649 |
+
<boundary-data type="header">
|
| 650 |
+
<confidence value="88">24</confidence>
|
| 651 |
+
</boundary-data>
|
| 652 |
+
</description>
|
| 653 |
+
</us-patent-application>
|
| 654 |
+
|
prior_art/11120095.xml
ADDED
|
@@ -0,0 +1,52 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11120095</doc-number>
|
| 8 |
+
<date>2005-07-18</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/120,095 Reply to Notice to File Corrected Application Papers of June 20, 2005 Specification Amendments:</p>
|
| 14 |
+
<p id="p-2" num="2">Please replace paragraph [0027] on page 4 with the following amended paragraph:</p>
|
| 15 |
+
<p id="p-3" num="3">
|
| 16 |
+
<confidence value="88">--</confidence>
|
| 17 |
+
FIG<confidence value="6">.</confidence>
|
| 18 |
+
<confidence value="54">18</confidence>
|
| 19 |
+
<confidence value="4111241422">ilhistraes</confidence>
|
| 20 |
+
FIG<confidence value="5">s</confidence>
|
| 21 |
+
. 18A and <confidence value="5">1</confidence>
|
| 22 |
+
8B illustrate several exemplary color images with different overlays, according to one embodiment; <confidence value="66">--</confidence>
|
| 23 |
+
Please add the following new paragraph after paragraph [0038] on page <part-num-ref name="following new paragraph after paragraph [0038] on page">5</part-num-ref>
|
| 24 |
+
of the application: </p>
|
| 25 |
+
<p id="p-4" num="4">--The patent or application file contains at least one drawing executed in color.</p>
|
| 26 |
+
<p id="p-5" num="5">Copies of this patent or patent application publication with color drawing(s) will be provided by the Office upon request and payment of the necessary fee.-<confidence value="5">-</confidence>
|
| 27 |
+
Please replace the paragraph [00118] on page <part-num-ref name="paragraph [00118] on page">30</part-num-ref>
|
| 28 |
+
with the following amended paragraph: </p>
|
| 29 |
+
<p id="p-6" num="6">
|
| 30 |
+
<confidence value="6656622242121265662165666">--FIG.-48-44hstratesFIGs.</confidence>
|
| 31 |
+
18A and 18B illustrate several exemplary color images with different overlays. <confidence value="528815884">T4e-uppei</confidence>
|
| 32 |
+
-In FIG. 18A the two images are taken from the same video stream. The first image has a channel logo overlay in the upper left corner and a promotion overlay in the upper right corner while the second image has no channel overlay and has a different promotion overlay. T<confidence value="5554">he-4</confidence>
|
| 33 |
+
ewe<confidence value="286">r-I</confidence>
|
| 34 |
+
n FIG. <confidence value="5">1</confidence>
|
| 35 |
+
8B the two images are taken from the same video stream. The first image has a station overlay in the upper right corner and an interactive bottom in the lower right corner while the second image has a different channel logo in the upper right and no interactive button. Comparing fingerprints for th<confidence value="6">e</confidence>
|
| 36 |
+
<confidence value="446">FSt</confidence>
|
| 37 |
+
<confidence value="216">Set</confidence>
|
| 38 |
+
<confidence value="46">Of</confidence>
|
| 39 |
+
<confidence value="6">i</confidence>
|
| 40 |
+
<confidence value="15512">Mageo</confidence>
|
| 41 |
+
<confidence value="666">the</confidence>
|
| 42 |
+
<confidence value="42121">SIfon</confidence>
|
| 43 |
+
<confidence value="626">set</confidence>
|
| 44 |
+
<confidence value="14">oI</confidence>
|
| 45 |
+
G. 18A images or FIG. 1<confidence value="88">8B</confidence>
|
| 46 |
+
images may result in a non-match due to the different overlays.-- <part-num-ref name="different overlays.--">
|
| 47 |
+
<confidence value="8">2</confidence>
|
| 48 |
+
</part-num-ref>
|
| 49 |
+
</p>
|
| 50 |
+
</description>
|
| 51 |
+
</us-patent-application>
|
| 52 |
+
|
prior_art/11130541.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
prior_art/11140288.xml
ADDED
|
@@ -0,0 +1,372 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11140288</doc-number>
|
| 8 |
+
<date>2005-05-27</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">Utility Patent Application <confidence value="88">of</confidence>
|
| 14 |
+
Eric J. HANSEN for a </p>
|
| 15 |
+
<heading id="h-1">SYSTEM AND METHOD FOR OPTIMIZING WEBSITE VISITOR ACTIONS</heading>
|
| 16 |
+
<p id="p-2" num="2">Copyright Notice [0001] A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. Copyright 2004-2005 SiteSpect, Inc.</p>
|
| 17 |
+
<p id="p-3" num="3">Cross Reference to Related Application<confidence value="5">s</confidence>
|
| 18 |
+
[0002] This utility patent application claims priority from U.S. provisional patent application serial number 60/609,654, filed 09/14/2004, titled "SYSTEM AND METHOD FOR OPTIMIZING WEBSITE VISITOR ACTIONS" in the name of Eric J. HANSEN. </p>
|
| 19 |
+
<boundary-data type="header">
|
| 20 |
+
<confidence value="5">1</confidence>
|
| 21 |
+
</boundary-data>
|
| 22 |
+
<p id="p-4" num="4">
|
| 23 |
+
<page-break num="2"/>
|
| 24 |
+
Background of the Invention Field of the Invention [0003] The invention relates generally to online marketing, advertising, and web functionality. The invention relates more specifically to conversion marketing, namely the science of measuring, testing, and improving the rate at which website visitors respond to website content with a predefined action or actions, including, but not limited to, clicking a link, filling out a web page form, putting an item in a shopping basket, subscribing to a newsletter, or purchasing a product. </p>
|
| 25 |
+
<p id="p-5" num="5">Description of Prior Art [0004] The greatest challenge for today's website operators is maximizing conversion rates -- the number of visitors who make a purchase, register for a new account, sign up for a newsletter, submit a sales lead, adopt a website feature, etc. A website's conversion rate is a measure of how successfully the website persuades visitors to move toward making a conversion.</p>
|
| 26 |
+
<p id="p-6" num="6">[0005] The conversion process is normally comprised of numerous pages and links. The content on each page (including the text headings of each link) must compel the visitor forward through the site. While a few visitors quickly move forward through a site, the majority of visitors never click to a second page on the average site. Of the few that do click to a second page, only a small percent follow through with any conversion action on the site.</p>
|
| 27 |
+
<p id="p-7" num="7">[0006] To optimize web conversions, the website operator must figure out how best to speak to the site's visitors, in a way that they understand, telling them what they need to know at each point in the conversion process. Specifically, the website operator needs to test variations of website content (including, but not limited to, product descriptions, headlines, calls to action, assurance messages, images, and <boundary-data type="header">
|
| 28 |
+
<confidence value="8">2</confidence>
|
| 29 |
+
</boundary-data>
|
| 30 |
+
<page-break num="3"/>
|
| 31 |
+
words that aid site navigation and usability) and determine which are most persuasive to the visitor. </p>
|
| 32 |
+
<p id="p-8" num="8">[0007] There have been several<confidence value="5">,</confidence>
|
| 33 |
+
attempts at optimizing web conversions using variation testing. One model for such testing is a remote content server model. In such a model, a request from a visitor's web browser is sent directly to a website. The website responds with customized content that includes JavaScript code. The JavaScript code subsequently contacts a remote server of the optimization tool vendor. The web browser executes the JavaScript and requests variable web page content from a remote server. Then the remote server processes the web browser's JavaScript request, sending the web browser content variations and tracking the visitor's session, typically using a cookie. The web browser inserts the content variations into the web page to complete rendering. </p>
|
| 34 |
+
<p id="p-9" num="9">[0008] While the remote content server model provides a relatively simple way to introduce variations into multiple regions on the same page, the model suffers from a number of disadvantages:</p>
|
| 35 |
+
<p id="p-10" num="10">1) The website operator must modify a target server's website pages to include the JavaScript code.</p>
|
| 36 |
+
<p id="p-11" num="11">2) The web browser must have JavaScript enabled.</p>
|
| 37 |
+
<p id="p-12" num="12">3) The web browser may have to make multiple HTTP connections to the remote server, which slows overall page load time.</p>
|
| 38 |
+
<p id="p-13" num="13">4) This model cannot track or modify non-HTML content, such as ".TXT," ".XML," ".EXE," or ".PDF" files since JavaScript is not executed for those document types.</p>
|
| 39 |
+
<p id="p-14" num="14">5) Since the page is not fully rendered until processed by the end-user's browser, the content that the user sees cannot be recorded for auditing or analysis purposes (which is done by products such as Tealeaf so that the operator's technical staff can investigate problems reported by end users).</p>
|
| 40 |
+
<p id="p-15" num="15">6) The model can typically only insert static content into a page (whether the encompassing page itself is statically or dynamically generated). This prevents <boundary-data type="header">
|
| 41 |
+
<confidence value="8">3</confidence>
|
| 42 |
+
</boundary-data>
|
| 43 |
+
<page-break num="4"/>
|
| 44 |
+
testing variations of the dynamic content itself, such as the formatting of a catalog page or search engine results. </p>
|
| 45 |
+
<p id="p-16" num="16">[0009] Another model for testing variations is a remote redirection server model. In this model, a visitor clicks on a static link (HREF) for a website, and the web browser makes a request to a redirect server or redirect page. The redirect server responds with an HTTP "Location" redirect to a link on the target website. The redirect server also tracks a visitor's session, typically using a cookie. The web browser accepts the redirect and automatically requests a new URL from the website. The website then responds with content variations.</p>
|
| 46 |
+
<p id="p-17" num="17">
|
| 47 |
+
<confidence value="5">[</confidence>
|
| 48 |
+
0010] The remote redirection server model improves on the remote content server model in that it does not require JavaScript in the web browser. Although the remote redirection server model is able to track clicks and provide variations of any type of content, the model suffers from a number of disadvantages: </p>
|
| 49 |
+
<p id="p-18" num="18">1) A website operator must physically create new variations of pages, and must re- code links wherever the resulting page may require a variation.</p>
|
| 50 |
+
<p id="p-19" num="19">2) The web browser has to make two requests for a test page (one to the redirect server, and a second for the redirect to the website), which slows overall page load time.</p>
|
| 51 |
+
<p id="p-20" num="20">3) Page content cannot be dynamically altered by the testing product.</p>
|
| 52 |
+
<p id="p-21" num="21">4) Links may display the URL of the redirect server instead of that of the website.</p>
|
| 53 |
+
<p id="p-22" num="22">5) The web browser may display a warning when redirecting from HTTPS to HTTP sites (or vice versa).</p>
|
| 54 |
+
<p id="p-23" num="23">[0011] Another model for testing variations is an integrated module model. In this model, a visitor's web browser requests content directly from a target website. The target website server is integrated with a marketing optimization module so that the visitor's request is handled within the same system. The integrated marketing module instructs the website how to render content, track actions, and so forth. The website server returns content variations directly to the web browser.</p>
|
| 55 |
+
<boundary-data type="header">
|
| 56 |
+
<confidence value="8">4</confidence>
|
| 57 |
+
</boundary-data>
|
| 58 |
+
<p id="p-24" num="24">
|
| 59 |
+
<page-break num="5"/>
|
| 60 |
+
[0012] The integrated model uses the website platform's own session management facility and thus can avoid using additional cookies and JavaScript. By integrating the marketing module with the website platform, there are relatively fewer time delays, more content variation options within the same page, and the model can track clicks and provide variations of any type of content. The integrated model, however, suffers from a number of drawbacks: </p>
|
| 61 |
+
<p id="p-25" num="25">1) Installing an integrated model is complex, expensive, and time consuming to the website operator.</p>
|
| 62 |
+
<p id="p-26" num="26">2) The website operator must reconfigure the website architecture to be compatible with the marketing vendor's integrated module.</p>
|
| 63 |
+
<p id="p-27" num="27">3) The integrated module cannot manage marketing tests that span heterogeneous servers. For example, if a website operator runs a vendor's integrated module on a first subdomain (e.g. <confidence value="2222222222222222">www1.example.com</confidence>
|
| 64 |
+
), but not on a second subdomain of the website (e.g. www2.example.com), then only the first subdomain can use the marketing test module, even though the two systems may host the website jointly. </p>
|
| 65 |
+
<p id="p-28" num="28">[0013] There are also a number of patents and patent applications that attempt to optimize web conversions.</p>
|
| 66 |
+
<p id="p-29" num="29">[0014] U.S. Patent 5,968,125 "Process For Optimizing The Effectiveness Of A Hypertext Element" (Garrick et al. 10-19-1999) discloses a process for determining the effectiveness of a web page to a visitor by creating alternative and test web pages, sending requests to the test web page, and monitoring the use of the web page and the rate that the web page objective was met and replacing pages with the page most visited.</p>
|
| 67 |
+
<p id="p-30" num="30">[0015] U.S. Patent Application 20020042738 "Method And Apparatus For Determining The Effectiveness Of Internet Advertising" (Srinivasan et al. 04-11-2002) discloses a method and system for measuring the effectiveness of the layout or appearance of a website advertisement to a visitor wherein different visitors are shown different <boundary-data type="header">
|
| 68 |
+
<confidence value="8">5</confidence>
|
| 69 |
+
</boundary-data>
|
| 70 |
+
<page-break num="6"/>
|
| 71 |
+
formats of the same page a<confidence value="5">n</confidence>
|
| 72 |
+
d response to the page is monitored and statistics are analyzed regarding the responses. </p>
|
| 73 |
+
<p id="p-31" num="31">[0016<confidence value="5">]</confidence>
|
| 74 |
+
U.S. Patent Application 20030014304 "Method Of Analyzing Internet Advertising Effects" (Calvert et al. 01-16-2003) discloses a method of evaluating Internet advertisement effectiveness that involves collecting Internet activity information associated with a multitude of cookies. </p>
|
| 75 |
+
<p id="p-32" num="32">[0017] U.S. Patent Application 20030018501 "Adaptive Testing For Conversion-Related Estimates Relevant To A Network Accessible Site" (Shan 01-23-2003) discloses a method and system for processing test data relevant to specific behavior of visitors of a website.</p>
|
| 76 |
+
<p id="p-33" num="33">[0018] U.S. Patent 6,662,215 "System And Method For Content Optimization" (Moskowitz et al. 12-09-2003) discloses a system and method for determining appropriate website content for consumers comprising a server arrangement, including a "real time content optimization" server, a user computer, and a network, wherein upon request a web page is generated for the user having static and dynamic elements which are tested for user reaction and response.</p>
|
| 77 |
+
<p id="p-34" num="34">[0019] U.S. Patent Application 20040030597 "Method And System Of Optimizing The Response And Profitability Of A Marketing Program" (Bibas 02-12-2004) discloses a method and system for tracking a consumer's behavior on a website, dynamically changing an advertisement or sales page, and testing a <confidence value="2222222222">sales.page</confidence>
|
| 78 |
+
to a subset of the marketing program to optimize the content of the page. </p>
|
| 79 |
+
<p id="p-35" num="35">[0020] U.S. Patent Application 20040123247 "Method and apparatus for dynamically altering electronic content" (Wachen, Mark et al. 06-24-2004) discloses "[a] method and apparatus for altering electronic content includes a template for assigning variables and values to a section of the content, a generator that creates the <confidence value="1">*</confidence>
|
| 80 |
+
<boundary-data type="header">
|
| 81 |
+
<confidence value="8">6</confidence>
|
| 82 |
+
</boundary-data>
|
| 83 |
+
<page-break num="7"/>
|
| 84 |
+
permutations of the content, a transmitter that pro<confidence value="8">v</confidence>
|
| 85 |
+
ides the content to a requestor and a evaluator and optimizer that aids in selecting the most optimal permutation of the content." [0021] While the prior art discloses attempts to improve online marketing, none of the web conversion optimization models provides a method of introducing page variations on existing website content without needing to make modifications to existing, back- end, content on the target server. What is needed, therefore is <part-num-ref name="target server. What is needed, therefore is">1)</part-num-ref>
|
| 86 |
+
a product that does not require modifications to a target server, <part-num-ref name="target server,">2)</part-num-ref>
|
| 87 |
+
a product that does not require web browsers to run JavaScript or accept cookies, and <part-num-ref name="product that does not require web browsers to run JavaScript or accept cookies, and">3)</part-num-ref>
|
| 88 |
+
a product that can track visitor actions on any type of request and introduce variations on both statically- and dynamically-generated HTML and non-HTML content. </p>
|
| 89 |
+
<p id="p-36" num="36">Brief Summary of the Invention <confidence value="5">[</confidence>
|
| 90 |
+
0022] The invention is a web software product that helps website operators create content variations, and then scientifically test and measure the impact that those content variations have on visitor conversion actions. The invention makes it possible to test any number of variations -<confidence value="5">-</confidence>
|
| 91 |
+
in any combination -- on a target server's website visitors. The invention produces conclusive answers about the impact of any type of content change on visitor conversion rates. Website operators learn, for example, which product descriptions yield the most sales, which promotional language pulls the most sales leads, and what site registration form generates the most sign-ups. </p>
|
| 92 |
+
<p id="p-37" num="37">[0023] The invention provides a method of using a reverse proxy server to introduce page variations on existing website content, without the need to make any modification to existing (back-end) content on the target server. The target server hosts the website to be tested and evaluated. The reverse proxy server delivers web content variations to visitors. A visitor's web browser-or any electronic device capable of <boundary-data type="header">
|
| 93 |
+
<confidence value="8">7</confidence>
|
| 94 |
+
</boundary-data>
|
| 95 |
+
<page-break num="8"/>
|
| 96 |
+
accessing web content-first sends a request directly to a reverse proxy server. The reverse proxy server then retrieves content from the target server. The target server sends unmodified content to the reverse proxy server. A modification module system on the reverse proxy server is then responsible for modifying and delivering content, and tracking a visitor's actions (including responses, non-responses, conversions, non-conversions, etc.). </p>
|
| 97 |
+
<p id="p-38" num="38">[0024] The reverse proxy server may track a visitor's session with its own cookie, the target server<confidence value="8">'</confidence>
|
| 98 |
+
s cookie, using the target server's UR<confidence value="52">L/</confidence>
|
| 99 |
+
path translation to piggy-back on the target server's session management facilities, using a hidden form field, or by any other method of session management. The system may also keep a visitor's session through the reverse proxy server's session management facilities, independent of the target server. The system on the reverse proxy server evaluates requests and responses and tracks a visitor's actions. The modification module modifies content to introduce variations as required, and responds to the web browser with final content. </p>
|
| 100 |
+
<p id="p-39" num="39">[0025] The target server website operator creates test campaigns to measure the impact of variations of copy, headlines, positioning, layout, imagery, price, etc. The modification module includes a user interface for allowing the website operator to create site variations using a WYSIWIG (what-you-see-is-what-you-get) visual editor. This eliminates the need to modify the target server content and saves time and cost otherwise spent on web designers and programmers. The operator can also target optimization efforts by segmenting visitors by specific criteria. The operator can stipulate that one or more visitor segments are assigned or not assigned to a test group based on operator-controlled parameters, assignment criteria, and test campaign parameters.</p>
|
| 101 |
+
<p id="p-40" num="40">[0026] The testing is then automated through the reverse proxy server system. Testing includes use of A/B testing, split path (i.e., split run) testing, and multivariate testing.</p>
|
| 102 |
+
<p id="p-41" num="41">During the test campaign, the modification module collects data for each response <boundary-data type="header">
|
| 103 |
+
<confidence value="8">8</confidence>
|
| 104 |
+
</boundary-data>
|
| 105 |
+
<page-break num="9"/>
|
| 106 |
+
point (action) that the website operator desires to measure. Some measurable actions include: adding an item to a shopping cart, registering for an account, and completing a sale. </p>
|
| 107 |
+
<p id="p-42" num="42">[0027] At any time during a test campaign, the website operator can run a report to see how variations are impacting visitor conversions. The report is customizable and can show how visitors responded during a visit as well as across repeated visits to show if a variation affected the likelihood of a conversion on a return visit. Reports can include charts and graphs with statistical summaries supporting the results. The modification module provides the ability to track, correlate, and measure visitor actions on a target server to one or more test groups.</p>
|
| 108 |
+
<p id="p-43" num="43">Features and Advantages [0028] One feature of the invention is that there is no need to modify the target server. The target server's website operator can create site variations using a WYSIWIG editor.</p>
|
| 109 |
+
<p id="p-44" num="44">The advantage of a visual editor is saving time and cost otherwise spent on web designers and programmers.</p>
|
| 110 |
+
<p id="p-45" num="45">
|
| 111 |
+
<confidence value="5">[</confidence>
|
| 112 |
+
0029] Another feature of the invention is that the website operator can segment visitors by specific criteria. The advantage of criteria-based segmentation is being able to target optimization efforts to the highest value market segment(s). The invention enables segmenting with several types of criteria, including historical visitor data stored within the invention as well as that provided by the web operator's external CRM/SFA system. </p>
|
| 113 |
+
<p id="p-46" num="46">[0030] Another feature of the invention is that variations can be created for both statically and dynamically created content. Variations are created using a search and replace technique involving "regular expressions." Use of regular expressions enables more complex variations to be introduced, particularly on dynamically-generated content.</p>
|
| 114 |
+
<boundary-data type="header">
|
| 115 |
+
<confidence value="8">9</confidence>
|
| 116 |
+
</boundary-data>
|
| 117 |
+
<p id="p-47" num="47">
|
| 118 |
+
<page-break num="10"/>
|
| 119 |
+
[0031] Another feature of the invention is multivariate/matrix testing. This method of testing achieves higher response rates in less time than A/B testing, by testing any number of variations for any number of factors anywhere on the target server, alone or in combination. </p>
|
| 120 |
+
<p id="p-48" num="48">[0032] Another feature of the invention is that it can provide built-in reports. The advantage of reports, with accompanying charts and graphs, is that it gives web operators conclusive answers, with statistical summaries to support the results.</p>
|
| 121 |
+
<p id="p-49" num="49">[0033] Another feature of the invention is sophisticated test campaign scheduling. The modification module lets a website operator run test campaigns individually or concurrently. Also, test campaigns can be scheduled in advance, and run on <confidence value="88">an</confidence>
|
| 122 |
+
automated basis where the tests stop once certain conditions have been met. </p>
|
| 123 |
+
<p id="p-50" num="50">[0034] Another feature of the invention is reusable test campaign elements. Website operators save time by creating new test campaigns using elements from previous test campaigns. The modification module's library stores previous variations, response points, and assignment test criteria for subsequent use.</p>
|
| 124 |
+
<p id="p-51" num="51">[0035] Another feature of the invention is the ability to track and analyze visitor actions.</p>
|
| 125 |
+
<p id="p-52" num="52">The system can track not only individual actions, but also sequences of actions such as specific click-paths through a shopping visit. The modification module can even track how variations affected actions across visits. The modification module can track requests for HTML content as well as non-HTML content.</p>
|
| 126 |
+
<p id="p-53" num="53">[0036] Another feature of the invention is the ability to signal to the target server that a current request came from a visitor in a specific test group. This enables the target server's website operator to test functional variations in the target server by creating code that can alter its function based on the visitor's test group status.</p>
|
| 127 |
+
<boundary-data type="header">
|
| 128 |
+
<confidence value="88">10</confidence>
|
| 129 |
+
</boundary-data>
|
| 130 |
+
<p id="p-54" num="54">
|
| 131 |
+
<page-break num="11"/>
|
| 132 |
+
[0037<confidence value="5">]</confidence>
|
| 133 |
+
A feature of the reverse proxy model is that the invention can optionally cache static content, e.g. images, in the reverse proxy server for web acceleration, and can increase speed of network traffic by optionally deflating or compressing content as it is sent back in the HTTP response. </p>
|
| 134 |
+
<p id="p-55" num="55">[0038] An advantage of the invention is that the website operator does not need to modify target server content, or require special programs on the visitor's web browser. The system can track visitor actions with or without cookies.</p>
|
| 135 |
+
<p id="p-56" num="56">[0039] Another advantage of the invention is that the general system cost is moderate.</p>
|
| 136 |
+
<p id="p-57" num="57">With no website modification needed, a target server's operator can avoid reconfiguring target web server architecture. No needed website modification also means a short campaign set-up time.</p>
|
| 137 |
+
<p id="p-58" num="58">[0040] Another advantage of the invention is compatibility with all web content. The system works on all sites, static or dynamic content, and even sites spread across multiple hosts.</p>
|
| 138 |
+
<p id="p-59" num="59">[0041] By combining the proven methods of direct response testing and experimental <confidence value="2">.</confidence>
|
| 139 |
+
design, the invention enables website operators to: <part-num-ref name="invention enables website operators to:">1)</part-num-ref>
|
| 140 |
+
determine which changes improve conversion rates by testing the changes on a subset of visitors, <part-num-ref name="subset of visitors,">2)</part-num-ref>
|
| 141 |
+
test unlimited variations using a web-based management system that requires no technical expertise or modifications to the target server, and <part-num-ref name="target server, and">3)</part-num-ref>
|
| 142 |
+
optimize the target server for specific customer groups using visitor segmentation. </p>
|
| 143 |
+
<boundary-data type="header">
|
| 144 |
+
<confidence value="88">11</confidence>
|
| 145 |
+
</boundary-data>
|
| 146 |
+
<p id="p-60" num="60">
|
| 147 |
+
<page-break num="12"/>
|
| 148 |
+
Brief Description of the Drawings [0042] In the drawings, closely related figures and items have the same number but different alphabetic suffixes. Processes, states, statuses, and databases are named for their respective functions. </p>
|
| 149 |
+
<p id="p-61" num="61">[0043] FIG. <confidence value="5">1</confidence>
|
| 150 |
+
is an overall system diagram showing the reverse proxy server model. </p>
|
| 151 |
+
<p id="p-62" num="62">[0044] FIG. 2 is a system diagram showing hardware of the reverse proxy server model.</p>
|
| 152 |
+
<p id="p-63" num="63">[0045] FIG. 3 is a flow chart of entry point response.</p>
|
| 153 |
+
<p id="p-64" num="64">[0046] FIG. 4 is a flow chart of user identification and user management.</p>
|
| 154 |
+
<p id="p-65" num="65">[0047] FIG. 5 is a flow chart for content management, including response point analysis and variation transformation.</p>
|
| 155 |
+
<boundary-data type="header">
|
| 156 |
+
<confidence value="88">12</confidence>
|
| 157 |
+
</boundary-data>
|
| 158 |
+
<p id="p-66" num="66">
|
| 159 |
+
<page-break num="13"/>
|
| 160 |
+
Detailed Description of the Invention, <confidence value="5">I</confidence>
|
| 161 |
+
ncluding the Preferred Embodiment Operation [0048] In the following detailed description of the invention, reference is made to the accompanying drawings which form a part hereof, and in which are shown, by way of illustration, specific embodiments in which the invention may be practiced. It is to be understood that other embodiments may be used, and structural changes may be made, without departing from the scope of the present invention. </p>
|
| 162 |
+
<p id="p-67" num="67">[0049] FIG. <confidence value="5">1</confidence>
|
| 163 |
+
is an overall system diagram showing the reverse proxy server model. The model begins after a web page request originates <part-num-ref name="web page request originates">(1)</part-num-ref>
|
| 164 |
+
from web browser <part-num-ref name="from web browser">100.</part-num-ref>
|
| 165 |
+
</p>
|
| 166 |
+
<p id="p-68" num="68">Instead of sending the request directly to target server <part-num-ref name="request directly to target server">130,</part-num-ref>
|
| 167 |
+
the request is sent to reverse proxy server <part-num-ref name="request is sent to reverse proxy server">120,</part-num-ref>
|
| 168 |
+
over Internet <part-num-ref name="request is sent to reverse proxy server 120, over Internet">110,</part-num-ref>
|
| 169 |
+
or over some other network. Reverse proxy server <part-num-ref name="request is sent to reverse proxy server 120, over Internet 110, or over some other network. Reverse proxy server">120</part-num-ref>
|
| 170 |
+
includes a proxy module <part-num-ref name="proxy module">122</part-num-ref>
|
| 171 |
+
for handling all proxy-related tasks and a modification module <part-num-ref name="modification module">124</part-num-ref>
|
| 172 |
+
for modifying content, tracking visitors actions, collecting data for selected visitor response points, and reporting on how content changes affect conversion rates. Data related to test campaigns, visitors, users, and content variations is stored in one or more databases (not shown), which can be implemented as part of reverse proxy server <part-num-ref name="for modifying content, tracking visitors actions, collecting data for selected visitor response points, and reporting on how content changes affect conversion rates. Data related to test campaigns, visitors, users, and content variations is stored in one or more databases (not shown), which can be implemented as part of reverse proxy server">120</part-num-ref>
|
| 173 |
+
or elsewhere. </p>
|
| 174 |
+
<p id="p-69" num="69">[0050] Continuing with FIG. 1. Reverse proxy server 120 requests <part-num-ref name="requests">(2)</part-num-ref>
|
| 175 |
+
content from target server <part-num-ref name="content from target server">130.</part-num-ref>
|
| 176 |
+
Target server <part-num-ref name="content from target server 130. Target server">130</part-num-ref>
|
| 177 |
+
responds to reverse proxy server <part-num-ref name="responds to reverse proxy server">120</part-num-ref>
|
| 178 |
+
by sending <part-num-ref name="by sending">(3)</part-num-ref>
|
| 179 |
+
unmodified content to reverse proxy server <part-num-ref name="unmodified content to reverse proxy server">120.</part-num-ref>
|
| 180 |
+
Reverse proxy server <part-num-ref name="unmodified content to reverse proxy server 120. Reverse proxy server">120</part-num-ref>
|
| 181 |
+
tracks a visitor's session using a cookie of reverse proxy server <part-num-ref name="cookie of reverse proxy server">120</part-num-ref>
|
| 182 |
+
or target server <part-num-ref name="or target server">130.</part-num-ref>
|
| 183 |
+
</p>
|
| 184 |
+
<p id="p-70" num="70">Reverse proxy server 120 may also track the visitor by URL/path translation via a piggy-back approach. Reverse proxy server <part-num-ref name="piggy-back approach. Reverse proxy server">120</part-num-ref>
|
| 185 |
+
evaluates the request and response and tracks the visitor's actions. Reverse proxy server <part-num-ref name="visitor's actions. Reverse proxy server">120</part-num-ref>
|
| 186 |
+
modifies web content, sent by target server <part-num-ref name="modifies web content, sent by target server">130,</part-num-ref>
|
| 187 |
+
to introduce variations as required. Finally <boundary-data type="header">
|
| 188 |
+
<confidence value="88">13</confidence>
|
| 189 |
+
</boundary-data>
|
| 190 |
+
<page-break num="14"/>
|
| 191 |
+
reverse proxy server <part-num-ref name="modifies web content, sent by target server 130, to introduce variations as required. Finally reverse proxy server">120</part-num-ref>
|
| 192 |
+
responds to web browser <part-num-ref name="responds to web browser">100</part-num-ref>
|
| 193 |
+
by sending <part-num-ref name="by sending">(4)</part-num-ref>
|
| 194 |
+
modified content. </p>
|
| 195 |
+
<p id="p-71" num="71">[0051] In the preferred embodiment, reverse pr<confidence value="8">o</confidence>
|
| 196 |
+
xy server <part-num-ref name="preferred embodiment, reverse proxy server">120</part-num-ref>
|
| 197 |
+
runs on an Intel-based computer running the Linux operating system, the MySQL database server, and the Apache httpd (web) server; and the proxy module is implemented with Apache's modproxy module. </p>
|
| 198 |
+
<p id="p-72" num="72">[0052] FIG. 2 is a system diagram showing hardware of the reverse proxy server model.</p>
|
| 199 |
+
<p id="p-73" num="73">FIG. 2 illustrates a plurality of client computers <part-num-ref name="plurality of client computers">300</part-num-ref>
|
| 200 |
+
running web browsers <part-num-ref name="running web browsers">100</part-num-ref>
|
| 201 |
+
(not shown). Reverse proxy computer <part-num-ref name="(not shown). Reverse proxy computer">320</part-num-ref>
|
| 202 |
+
runs reverse proxy server <part-num-ref name="runs reverse proxy server">120,</part-num-ref>
|
| 203 |
+
and target computer <part-num-ref name="runs reverse proxy server 120, and target computer">330</part-num-ref>
|
| 204 |
+
runs target server <part-num-ref name="runs target server">130.</part-num-ref>
|
| 205 |
+
Client computer <part-num-ref name="runs target server 130. Client computer">300,</part-num-ref>
|
| 206 |
+
reverse proxy computer <part-num-ref name="runs target server 130. Client computer 300, reverse proxy computer">320,</part-num-ref>
|
| 207 |
+
and target computer <part-num-ref name="runs target server 130. Client computer 300, reverse proxy computer 320, and target computer">330</part-num-ref>
|
| 208 |
+
are interconnected and communicate via network <part-num-ref name="are interconnected and communicate via network">310,</part-num-ref>
|
| 209 |
+
which is the Internet for the Application Service Provider (ASP) model (where the application is hosted on the service provider's computer) or a LAN for the enterprise model (where the application is hosted on the client's computer). It is to be understood that reverse proxy computer <part-num-ref name="client's computer). It is to be understood that reverse proxy computer">320</part-num-ref>
|
| 210 |
+
and target computer <part-num-ref name="and target computer">330</part-num-ref>
|
| 211 |
+
can be one or more physical computers. Reverse proxy computer <part-num-ref name="can be one or more physical computers. Reverse proxy computer">320</part-num-ref>
|
| 212 |
+
can be any computer operable to run a database server and a web server. </p>
|
| 213 |
+
<p id="p-74" num="74">[0053] The system is able to compensate for reverse proxy server <part-num-ref name="system is able to compensate for reverse proxy server">120</part-num-ref>
|
| 214 |
+
failure. If reverse proxy server <part-num-ref name="failure. If reverse proxy server">120</part-num-ref>
|
| 215 |
+
is down, target server <part-num-ref name="is down, target server">130</part-num-ref>
|
| 216 |
+
can still be available by deploying a hot backup server (not shown) with an intelligent load balancer. The load balancer transparently redirects traffic to the hot backup. Another option is to deploy edge- routing services to redirect traffic from one connectivity network to another network. </p>
|
| 217 |
+
<p id="p-75" num="75">For example, the system can be collocated at a data center that has peering with four tier-one Internet backbones (not shown). If a packet that would ordinarily travel through (for example) backbone <part-num-ref name="packet that would ordinarily travel through (for example) backbone">1</part-num-ref>
|
| 218 |
+
cannot be transmitted, then the edge-router (not shown) detects this and re-routes the packet, and subsequent packets, through (for example) backbone <part-num-ref name="packet, and subsequent packets, through (for example) backbone">2.</part-num-ref>
|
| 219 |
+
Another option is to deploy DNS failover, whereby if the DNS <boundary-data type="header">
|
| 220 |
+
<confidence value="88">14</confidence>
|
| 221 |
+
</boundary-data>
|
| 222 |
+
<page-break num="15"/>
|
| 223 |
+
server detects that the reverse proxy server is down, then subsequent DNS queries return the IP address of the target computer. When the DNS server detects that the reverse proxy server has returned to normal operation, subsequent DNS queries return the IP address of the reverse proxy server. </p>
|
| 224 |
+
<p id="p-76" num="76">[0054] The system is also able to compensate for any delay with HTTP requests and responses between reverse proxy server <part-num-ref name="system is also able to compensate for any delay with HTTP requests and responses between reverse proxy server">120</part-num-ref>
|
| 225 |
+
and target server <part-num-ref name="and target server">130</part-num-ref>
|
| 226 |
+
by closely positioning the servers, or placing the servers on the same network in a data center. </p>
|
| 227 |
+
<p id="p-77" num="77">Caching static content, and deflating and compressing content also compensates for any delays.</p>
|
| 228 |
+
<p id="p-78" num="78">[0055] When a website operator launches a test campaign, the website operator tells the system, via a user interface (not shown) to the modification module <part-num-ref name="modification module">124</part-num-ref>
|
| 229 |
+
of reverse proxy server <part-num-ref name="of reverse proxy server">120,</part-num-ref>
|
| 230 |
+
exactly which type(s) of visitors to test. For example, if a target server <part-num-ref name="target server">130</part-num-ref>
|
| 231 |
+
sells to a broad market, then perhaps the operator of target server <part-num-ref name="operator of target server">130</part-num-ref>
|
| 232 |
+
will simply want a representative sample of all visitors, such as 5% of all visitors over a two week period of time. If a business targets one or more specific market segments, then the system lets the business target efforts precisely. The system provides several types of segmentation criteria, including past visitor history, referrals from search engines or banner ads, entry through specific landing pages, and customer segments defined by the web operator's Customer Relationship Management/Sales Force Automation (CRM/SFA) system. The number and types of the segmentation criteria is adjustable according to the needs of a particular target server. </p>
|
| 233 |
+
<p id="p-79" num="79">[0056] Generally, the system will vary or modify HTML content, since the majority of web pages appear in this format, but the system is not limited to varying HTML content.</p>
|
| 234 |
+
<p id="p-80" num="80">The system can vary content for plain text documents,<confidence value="5">.</confidence>
|
| 235 |
+
WML documents, CSS documents, and other non-HTML content. </p>
|
| 236 |
+
<boundary-data type="header">
|
| 237 |
+
<confidence value="88">15</confidence>
|
| 238 |
+
</boundary-data>
|
| 239 |
+
<p id="p-81" num="81">
|
| 240 |
+
<page-break num="16"/>
|
| 241 |
+
[0057] Embodied as a web software product, the invention can be offered as an ASP version, offered as an enterprise (installed) version, and other formats. In one embodiment of the invention (ASP model), the software runs as a hosted service on a web server in a third-party data center or facility. For very high traffic sites (enterprise model), a standalone version can be installed in a website operator's own data center. The system is operable to run multiple concurrent test campaigns with the ability to signal a visitor's test status through the use of a cookie or other HTTP header transmitted between the reverse proxy server <part-num-ref name="reverse proxy server">120</part-num-ref>
|
| 242 |
+
and target server <part-num-ref name="and target server">130</part-num-ref>
|
| 243 |
+
for functionality testing. </p>
|
| 244 |
+
<p id="p-82" num="82">[0058] FIG. 3 is a flow chart of entry point response. In step <part-num-ref name="flow chart of entry point response. In step">320,</part-num-ref>
|
| 245 |
+
the reverse proxy server <part-num-ref name="reverse proxy server">120</part-num-ref>
|
| 246 |
+
(not shown) receives an HTTP request from a client computer <part-num-ref name="client computer">300</part-num-ref>
|
| 247 |
+
(not shown). </p>
|
| 248 |
+
<p id="p-83" num="83">The target website operator decides attributes of the HTTP request that indicate whether or not the request will result in modified or unmodified content being delivered to the client computer <part-num-ref name="client computer">300.</part-num-ref>
|
| 249 |
+
In step <part-num-ref name="client computer 300. In step">335,</part-num-ref>
|
| 250 |
+
if the visitor's HTTP request includes attributes (such as IP address, USER-AGENT, URI path, or content-type) that the target website operator has not defined for tracking, then the HTTP request will be passed through, resulting, in step <part-num-ref name="HTTP request will be passed through, resulting, in step">330,</part-num-ref>
|
| 251 |
+
in no variation of the target website's content and no tracking of the visitor's request, and then operation proceeds to step <part-num-ref name="visitor's request, and then operation proceeds to step">335,</part-num-ref>
|
| 252 |
+
where response content is transmitted to the visitor. Otherwise, operation proceeds to step <part-num-ref name="visitor. Otherwise, operation proceeds to step">340.</part-num-ref>
|
| 253 |
+
In step <part-num-ref name="visitor. Otherwise, operation proceeds to step 340. In step">340,</part-num-ref>
|
| 254 |
+
additional protocol checks are performed to determine whether tracking and variation should be performed. For example, if the request does not produce an "OK" response code (e.g. HTTP status code number <part-num-ref name="HTTP status code number">200)</part-num-ref>
|
| 255 |
+
from the target web server, then the request will not be tracked. If the protocol checks of step <part-num-ref name="protocol checks of step">340</part-num-ref>
|
| 256 |
+
indicate that no tracking should be done, then operation proceeds to step <part-num-ref name="indicate that no tracking should be done, then operation proceeds to step">330.</part-num-ref>
|
| 257 |
+
Otherwise, operation proceeds to step <part-num-ref name="indicate that no tracking should be done, then operation proceeds to step 330. Otherwise, operation proceeds to step">345.</part-num-ref>
|
| 258 |
+
In step <part-num-ref name="indicate that no tracking should be done, then operation proceeds to step 330. Otherwise, operation proceeds to step 345. In step">345,</part-num-ref>
|
| 259 |
+
the system checks to see if the-HTTP request is for text-based content, and, if so, then content is buffered in step <part-num-ref name="system checks to see if the-HTTP request is for text-based content, and, if so, then content is buffered in step">350.</part-num-ref>
|
| 260 |
+
If not, operation proceeds to step <part-num-ref name="system checks to see if the-HTTP request is for text-based content, and, if so, then content is buffered in step 350. If not, operation proceeds to step">355.</part-num-ref>
|
| 261 |
+
In step <part-num-ref name="system checks to see if the-HTTP request is for text-based content, and, if so, then content is buffered in step 350. If not, operation proceeds to step 355. In step">355,</part-num-ref>
|
| 262 |
+
anti-caching is performed (response headers are adjusted) to prevent caching by downstream proxies and browsers. Next, operation proceeds to step <part-num-ref name="system checks to see if the-HTTP request is for text-based content, and, if so, then content is buffered in step 350. If not, operation proceeds to step 355. In step 355, anti-caching is performed (response headers are adjusted) to prevent caching by downstream proxies and browsers. Next, operation proceeds to step">360,</part-num-ref>
|
| 263 |
+
user identification and management, which is described in FIG. 4. </p>
|
| 264 |
+
<boundary-data type="header">
|
| 265 |
+
<confidence value="88">16</confidence>
|
| 266 |
+
</boundary-data>
|
| 267 |
+
<p id="p-84" num="84">
|
| 268 |
+
<page-break num="17"/>
|
| 269 |
+
[0059] FIG. 4 is a flow chart of user identification and user management. In step <part-num-ref name="flow chart of user identification and user management. In step">400,</part-num-ref>
|
| 270 |
+
a visitor is identified via cookie data or UR<confidence value="5">I</confidence>
|
| 271 |
+
(Uniform Resource Identifier) data contained in the visitor's request. Operation proceeds to step <part-num-ref name="visitor's request. Operation proceeds to step">405,</part-num-ref>
|
| 272 |
+
where the system checks to see if the visitor has a Globally Unique IDentifier (GUID). If the result of step <part-num-ref name="result of step">405</part-num-ref>
|
| 273 |
+
is no, operation proceeds to step <part-num-ref name="is no, operation proceeds to step">430,</part-num-ref>
|
| 274 |
+
and if the result of step <part-num-ref name="result of step">405</part-num-ref>
|
| 275 |
+
is yes, operation proceeds to step <part-num-ref name="is yes, operation proceeds to step">410.</part-num-ref>
|
| 276 |
+
In step <part-num-ref name="is yes, operation proceeds to step 410. In step">410,</part-num-ref>
|
| 277 |
+
the system looks up the user and retrieves the most recent user visit data, and operation proceeds to step <part-num-ref name="most recent user visit data, and operation proceeds to step">415.</part-num-ref>
|
| 278 |
+
</p>
|
| 279 |
+
<p id="p-85" num="85">In step 415, the system checks to see if user data was found, and if no, then operation proceeds to step <part-num-ref name="system checks to see if user data was found, and if no, then operation proceeds to step">430.</part-num-ref>
|
| 280 |
+
If yes, then operation proceeds to step <part-num-ref name="system checks to see if user data was found, and if no, then operation proceeds to step 430. If yes, then operation proceeds to step">420.</part-num-ref>
|
| 281 |
+
In step <part-num-ref name="system checks to see if user data was found, and if no, then operation proceeds to step 430. If yes, then operation proceeds to step 420. In step">420,</part-num-ref>
|
| 282 |
+
the system checks to see if any user visit data was found for the user, and if no, then operation proceeds to step <part-num-ref name="user, and if no, then operation proceeds to step">430.</part-num-ref>
|
| 283 |
+
If yes, then operation proceeds to step <part-num-ref name="user, and if no, then operation proceeds to step 430. If yes, then operation proceeds to step">425.</part-num-ref>
|
| 284 |
+
In step <part-num-ref name="user, and if no, then operation proceeds to step 430. If yes, then operation proceeds to step 425. In step">425,</part-num-ref>
|
| 285 |
+
the system checks to see if the user's most recent user visit data has expired, and if yes, then operation proceeds to step <part-num-ref name="user's most recent user visit data has expired, and if yes, then operation proceeds to step">445.</part-num-ref>
|
| 286 |
+
If no, then operation proceeds to step <part-num-ref name="user's most recent user visit data has expired, and if yes, then operation proceeds to step 445. If no, then operation proceeds to step">499.</part-num-ref>
|
| 287 |
+
</p>
|
| 288 |
+
<p id="p-86" num="86">[0060] Continuing with FIG. 4. In step 430, the system checks to see whether the user is being tracked, and if no, then operation proceeds to step <part-num-ref name="user is being tracked, and if no, then operation proceeds to step">435.</part-num-ref>
|
| 289 |
+
In step <part-num-ref name="user is being tracked, and if no, then operation proceeds to step 435. In step">435,</part-num-ref>
|
| 290 |
+
the system performs a pass-through response, i.e. no variation of the target website's content and no tracking of the visitor's request, and operation proceeds to step <part-num-ref name="visitor's request, and operation proceeds to step">436,</part-num-ref>
|
| 291 |
+
where response content is transmitted to the visitor. If the result of step <part-num-ref name="result of step">430</part-num-ref>
|
| 292 |
+
is yes, then operation proceeds to step <part-num-ref name="is yes, then operation proceeds to step">440,</part-num-ref>
|
| 293 |
+
where the system creates a user record and, if a reverse proxy server is managing session data, then the system also sets a cookie. Then operation proceeds to step <part-num-ref name="cookie. Then operation proceeds to step">470.</part-num-ref>
|
| 294 |
+
</p>
|
| 295 |
+
<p id="p-87" num="87">[0061] Continuing with FIG. 4. In step 445, the system checks to see if the user was previously assigned to a test campaign, and if no, then operation proceeds to step <part-num-ref name="test campaign, and if no, then operation proceeds to step">470.</part-num-ref>
|
| 296 |
+
If yes, operation proceeds to step <part-num-ref name="test campaign, and if no, then operation proceeds to step 470. If yes, operation proceeds to step">450.</part-num-ref>
|
| 297 |
+
In step <part-num-ref name="test campaign, and if no, then operation proceeds to step 470. If yes, operation proceeds to step 450. In step">450,</part-num-ref>
|
| 298 |
+
the system looks up visit and time limits for the assigned test campaign, and operation proceeds to step <part-num-ref name="assigned test campaign, and operation proceeds to step">455.</part-num-ref>
|
| 299 |
+
</p>
|
| 300 |
+
<p id="p-88" num="88">In step 455, the system checks to see whether the user was previously assigned to a test campaign, and if no, then operation proceeds to step <part-num-ref name="test campaign, and if no, then operation proceeds to step">470.</part-num-ref>
|
| 301 |
+
If yes, then <boundary-data type="header">
|
| 302 |
+
<confidence value="88">17</confidence>
|
| 303 |
+
</boundary-data>
|
| 304 |
+
<page-break num="18"/>
|
| 305 |
+
operation proceeds to step <part-num-ref name="test campaign, and if no, then operation proceeds to step 470. If yes, then operation proceeds to step">455.</part-num-ref>
|
| 306 |
+
In step <part-num-ref name="test campaign, and if no, then operation proceeds to step 470. If yes, then operation proceeds to step 455. In step">455,</part-num-ref>
|
| 307 |
+
the system checks to see whether the user still qualifies for assignment to the test campaign, and if yes, then operation proceeds to step <part-num-ref name="test campaign, and if yes, then operation proceeds to step">497.</part-num-ref>
|
| 308 |
+
If no, operation proceeds to step <part-num-ref name="test campaign, and if yes, then operation proceeds to step 497. If no, operation proceeds to step">460.</part-num-ref>
|
| 309 |
+
In step <part-num-ref name="test campaign, and if yes, then operation proceeds to step 497. If no, operation proceeds to step 460. In step">460,</part-num-ref>
|
| 310 |
+
the system updates user data to remove the current assignment and inserts user assignment history data, and then operation proceeds to step <part-num-ref name="current assignment and inserts user assignment history data, and then operation proceeds to step">465.</part-num-ref>
|
| 311 |
+
In step <part-num-ref name="current assignment and inserts user assignment history data, and then operation proceeds to step 465. In step">465,</part-num-ref>
|
| 312 |
+
the system checks to see whether the visitor can be reassigned to another test campaign, and if yes, then operation proceeds to step <part-num-ref name="visitor can be reassigned to another test campaign, and if yes, then operation proceeds to step">470.</part-num-ref>
|
| 313 |
+
If no, then operation proceeds to step <part-num-ref name="visitor can be reassigned to another test campaign, and if yes, then operation proceeds to step 470. If no, then operation proceeds to step">495.</part-num-ref>
|
| 314 |
+
In step <part-num-ref name="visitor can be reassigned to another test campaign, and if yes, then operation proceeds to step 470. If no, then operation proceeds to step 495. In step">495,</part-num-ref>
|
| 315 |
+
the system checks to see whether this user visit should be logged, and if yes, then operation proceeds to step <part-num-ref name="system checks to see whether this user visit should be logged, and if yes, then operation proceeds to step">497.</part-num-ref>
|
| 316 |
+
If no, then operation proceeds to step <part-num-ref name="system checks to see whether this user visit should be logged, and if yes, then operation proceeds to step 497. If no, then operation proceeds to step">499.</part-num-ref>
|
| 317 |
+
</p>
|
| 318 |
+
<p id="p-89" num="89">
|
| 319 |
+
<confidence value="5">[</confidence>
|
| 320 |
+
0062] Continuing with FIG. 4. In step 470, the system evaluates the available test campaigns and user assignment criteria. A user can be included or excluded from a given test campaign based on a plurality of operater-defined variables, including, but not limited to, the visitor's and/or request's date/time, the USERAGENT value, IP address, entry URL, current URL, referring URL, visitor history, cookie value, and past visitor actions. Next, operation proceeds to step <part-num-ref name="USERAGENT value, IP address, entry URL, current URL, referring URL, visitor history, cookie value, and past visitor actions. Next, operation proceeds to step">480.</part-num-ref>
|
| 321 |
+
In step <part-num-ref name="USERAGENT value, IP address, entry URL, current URL, referring URL, visitor history, cookie value, and past visitor actions. Next, operation proceeds to step 480. In step">480,</part-num-ref>
|
| 322 |
+
the system checks to see whether the user qualifies for a new test campaign assignment, and if no, then operation proceeds to step <part-num-ref name="new test campaign assignment, and if no, then operation proceeds to step">495.</part-num-ref>
|
| 323 |
+
If yes, then operation proceeds to step <part-num-ref name="new test campaign assignment, and if no, then operation proceeds to step 495. If yes, then operation proceeds to step">485.</part-num-ref>
|
| 324 |
+
In step <part-num-ref name="new test campaign assignment, and if no, then operation proceeds to step 495. If yes, then operation proceeds to step 485. In step">485,</part-num-ref>
|
| 325 |
+
the system assigns the user to a test campaign and variation group, and operation proceeds to step <part-num-ref name="test campaign and variation group, and operation proceeds to step">495.</part-num-ref>
|
| 326 |
+
In step <part-num-ref name="test campaign and variation group, and operation proceeds to step 495. In step">490,</part-num-ref>
|
| 327 |
+
the system stores the assigned test campaign (T<confidence value="5">C</confidence>
|
| 328 |
+
) and variation group (VG) information in user data, and operation proceeds to step <part-num-ref name="assigned test campaign (TC) and variation group (VG) information in user data, and operation proceeds to step">497.</part-num-ref>
|
| 329 |
+
</p>
|
| 330 |
+
<p id="p-90" num="90">[0063] Continuing with FIG. 4. In step 497, a new user visit is created, and operation proceeds to step <part-num-ref name="new user visit is created, and operation proceeds to step">499,</part-num-ref>
|
| 331 |
+
continue to content management, which is described in FIG. </p>
|
| 332 |
+
<p id="p-91" num="91">
|
| 333 |
+
<confidence value="88">5.</confidence>
|
| 334 |
+
</p>
|
| 335 |
+
<p id="p-92" num="92">[0064] FIG. 5 is a flow chart for content management, including response point analysis and variation transformation. Operation begins at step <part-num-ref name="flow chart for content management, including response point analysis and variation transformation. Operation begins at step">500,</part-num-ref>
|
| 336 |
+
where the system <boundary-data type="header">
|
| 337 |
+
<confidence value="88">18</confidence>
|
| 338 |
+
</boundary-data>
|
| 339 |
+
<page-break num="19"/>
|
| 340 |
+
checks to see whether a user is assigned to a test campaign, and if no, then operation proceeds to step <part-num-ref name="test campaign, and if no, then operation proceeds to step">540.</part-num-ref>
|
| 341 |
+
If yes, operation proceeds to step <part-num-ref name="test campaign, and if no, then operation proceeds to step 540. If yes, operation proceeds to step">505,</part-num-ref>
|
| 342 |
+
where the system loops through response points for the current test campaign, and then operation proceeds to step <part-num-ref name="current test campaign, and then operation proceeds to step">510.</part-num-ref>
|
| 343 |
+
In step <part-num-ref name="current test campaign, and then operation proceeds to step 510. In step">510,</part-num-ref>
|
| 344 |
+
the system checks to see whether there were any response point hits, and if no, then operation proceeds to step <part-num-ref name="system checks to see whether there were any response point hits, and if no, then operation proceeds to step">520.</part-num-ref>
|
| 345 |
+
</p>
|
| 346 |
+
<p id="p-93" num="93">If yes, then operation proceeds to step 515, where the system records hit(s) for the user visit and, if required, updates the hit rating for the user visit, and then operation proceeds to step <part-num-ref name="user visit, and then operation proceeds to step">520.</part-num-ref>
|
| 347 |
+
In step <part-num-ref name="user visit, and then operation proceeds to step 520. In step">520,</part-num-ref>
|
| 348 |
+
the system checks to see whether the user is assigned to a non-control variation group, and if no, then operation proceeds to step <part-num-ref name="non-control variation group, and if no, then operation proceeds to step">540.</part-num-ref>
|
| 349 |
+
If yes, then operation proceeds to step <part-num-ref name="non-control variation group, and if no, then operation proceeds to step 540. If yes, then operation proceeds to step">525,</part-num-ref>
|
| 350 |
+
where the system performs variations for the current variation group. Next, operation proceeds to step <part-num-ref name="current variation group. Next, operation proceeds to step">520.</part-num-ref>
|
| 351 |
+
In step <part-num-ref name="current variation group. Next, operation proceeds to step 520. In step">530,</part-num-ref>
|
| 352 |
+
the system checks to see whether any variations were applied, and if no, then operation proceeds to step <part-num-ref name="system checks to see whether any variations were applied, and if no, then operation proceeds to step">540.</part-num-ref>
|
| 353 |
+
If yes, then operation proceeds to step <part-num-ref name="system checks to see whether any variations were applied, and if no, then operation proceeds to step 540. If yes, then operation proceeds to step">535,</part-num-ref>
|
| 354 |
+
where the system records hit(s) for the user visit and, if required, updates the hit rating for the user visit, and then operation proceeds to step <part-num-ref name="user visit, and then operation proceeds to step">540.</part-num-ref>
|
| 355 |
+
In step <part-num-ref name="user visit, and then operation proceeds to step 540. In step">540,</part-num-ref>
|
| 356 |
+
the system updates data, including user visit data, page view count data (only for non- image requests) and time-stamp data, and then operation proceeds to step <part-num-ref name="system updates data, including user visit data, page view count data (only for non- image requests) and time-stamp data, and then operation proceeds to step">545,</part-num-ref>
|
| 357 |
+
where response content is transmitted to the visitor. </p>
|
| 358 |
+
<p id="p-94" num="94">[0065<confidence value="5">]</confidence>
|
| 359 |
+
In the preferred embodiment, the proxy module and the modification module are implemented on a reverse proxy server. </p>
|
| 360 |
+
<p id="p-95" num="95">Other Embodiments [0066] In another embodiment, a separate third-party reverse proxy server is used. The functions of the proxy module are performed by the third-party reverse proxy server, and the modification module is a stand-alone software product that operates in conjunction with the third-party reverse proxy server. In this embodiment, the modification module accepts input from and transmits output to the reverse proxy <boundary-data type="header">
|
| 361 |
+
<confidence value="88">19</confidence>
|
| 362 |
+
</boundary-data>
|
| 363 |
+
<page-break num="20"/>
|
| 364 |
+
server, and no software changes to the reverse proxy server or the target server are required. </p>
|
| 365 |
+
<p id="p-96" num="96">[0067] In another embodiment, the modification module is a stand-alone software product.</p>
|
| 366 |
+
<p id="p-97" num="97">In this embodiment, the reverse proxy server is optional. The target server receives a request from a web browser for web content from the target website hosted at a target server; and the modification module retrieves unmodified web content from the target server, modifies the web content (including performing a search and replace operation using regular expressions), delivers the modified web content to the requesting web browser, tracks actions of the visitor, collects data for each response point selected to be measured, and reports on how content changes affect conversion rates. In this embodiment, both the Application Service Provider (ASP) model (where the modification module is hosted on the service provider's computer) or a LAN for the enterprise model (where the modification module is hosted on the client's computer) can be used. A variation of the ASP model involves implementing the modification module in a computer "appliance" that could be installed in the client's premises or in the service provider's premises.</p>
|
| 367 |
+
<boundary-data type="header">
|
| 368 |
+
<confidence value="88">20</confidence>
|
| 369 |
+
</boundary-data>
|
| 370 |
+
</description>
|
| 371 |
+
</us-patent-application>
|
| 372 |
+
|
prior_art/11142943.xml
ADDED
|
@@ -0,0 +1,44 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11142943</doc-number>
|
| 8 |
+
<date>2009-09-29</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">Applicant Judge, et al. Attorney's Docket No.: 20281-0008001 Serial No. <confidence value="6">:</confidence>
|
| 14 |
+
11/142,943 Filed <confidence value="6">:</confidence>
|
| 15 |
+
June <confidence value="88">2,</confidence>
|
| 16 |
+
2005 Page <confidence value="6">:</confidence>
|
| 17 |
+
<part-num-ref name="Page :">
|
| 18 |
+
<confidence value="8">2</confidence>
|
| 19 |
+
</part-num-ref>
|
| 20 |
+
<confidence value="88">of</confidence>
|
| 21 |
+
<part-num-ref name="of">
|
| 22 |
+
<confidence value="88">16</confidence>
|
| 23 |
+
</part-num-ref>
|
| 24 |
+
Amendments to the Specification Please replace the paragraph beginning at page <part-num-ref name="paragraph beginning at page">16,</part-num-ref>
|
| 25 |
+
line <part-num-ref name="paragraph beginning at page 16, line">24</part-num-ref>
|
| 26 |
+
with the following amended paragraph: </p>
|
| 27 |
+
<p id="p-2" num="2">The systems' and methods' data (e.g., associations, mappings, etc.) may be stored and implemented in one or more different types of computer-implemented ways, such as different types of storage devices and programming constructs (e.g., data stores, RAM, ROM, Flash memory, flat files, databases, programming data structures, programming variables, IF-THEN (or similar type) statement constructs, etc.). It is noted that data structures describe formats for use in organizing and storing data in memory (e.<confidence value="885">g.,</confidence>
|
| 28 |
+
storage devices or other computer-readable media<confidence value="66">),</confidence>
|
| 29 |
+
databases, or programs<confidence value="6">,</confidence>
|
| 30 |
+
<confidence value="222222222">memory,or</confidence>
|
| 31 |
+
<confidence value="55552">ether</confidence>
|
| 32 |
+
<confidence value="87">co</confidence>
|
| 33 |
+
mp<confidence value="8888">uter</confidence>
|
| 34 |
+
rea<confidence value="8">d</confidence>
|
| 35 |
+
able <confidence value="66566">media</confidence>
|
| 36 |
+
<confidence value="666">for</confidence>
|
| 37 |
+
<confidence value="655">use</confidence>
|
| 38 |
+
<confidence value="66">by</confidence>
|
| 39 |
+
<confidence value="22">c-</confidence>
|
| 40 |
+
emp<confidence value="12">ut</confidence>
|
| 41 |
+
er- program. </p>
|
| 42 |
+
</description>
|
| 43 |
+
</us-patent-application>
|
| 44 |
+
|
prior_art/11170622.xml
ADDED
|
@@ -0,0 +1,46 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11170622</doc-number>
|
| 8 |
+
<date>2010-03-17</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="1417">|il/</confidence>
|
| 15 |
+
<confidence value="5">(</confidence>
|
| 16 |
+
<confidence value="1">1</confidence>
|
| 17 |
+
</p>
|
| 18 |
+
<heading id="h-1">IN THE SPECIFICATION</heading>
|
| 19 |
+
<p id="p-2" num="2">
|
| 20 |
+
<confidence value="22222222222222">Please4nserthe</confidence>
|
| 21 |
+
following sentence as follows under the heading "Related <confidence value="22222222222222">Application"as</confidence>
|
| 22 |
+
follows: <confidence value="24">lo</confidence>
|
| 23 |
+
This application is a continuation of application serial no. 10/664<confidence value="5">,</confidence>
|
| 24 |
+
985<confidence value="5">,</confidence>
|
| 25 |
+
filed Se<confidence value="8">p</confidence>
|
| 26 |
+
tember <part-num-ref name="continuation of application serial no. 10/664,985, filed September">18<confidence value="5">,</confidence>
|
| 27 |
+
</part-num-ref>
|
| 28 |
+
<part-num-ref name="continuation of application serial no. 10/664,985, filed September 18,">2003<confidence value="5">,</confidence>
|
| 29 |
+
</part-num-ref>
|
| 30 |
+
which is a continuation of application serial no. 09/974,788, whi<confidence value="42">eh</confidence>
|
| 31 |
+
-was filed on October <part-num-ref name="continuation of application serial no. 09/974,788, whieh-was filed on October">12,</part-num-ref>
|
| 32 |
+
<part-num-ref name="continuation of application serial no. 09/974,788, whieh-was filed on October 12,">2001</part-num-ref>
|
| 33 |
+
and issued as U.S. Patent No. 6<confidence value="5">,</confidence>
|
| 34 |
+
654<confidence value="66">,4</confidence>
|
| 35 |
+
18, which is a continuation of application serial no. 08/899,096, <confidence value="22222222">whiehwas</confidence>
|
| 36 |
+
filed on July <part-num-ref name="continuation of application serial no. 08/899,096, whiehwas filed on July">24,</part-num-ref>
|
| 37 |
+
<part-num-ref name="continuation of application serial no. 08/899,096, whiehwas filed on July 24,">1997</part-num-ref>
|
| 38 |
+
which claims the benefit of priority afforded by provisional application no. 60/038,016, filed February <part-num-ref name="benefit of priority afforded by provisional application no. 60/038,016, filed February">16,</part-num-ref>
|
| 39 |
+
<part-num-ref name="benefit of priority afforded by provisional application no. 60/038,016, filed February 16,">1997,</part-num-ref>
|
| 40 |
+
the disclosure of each of these applications is incorporated herein by reference. </p>
|
| 41 |
+
<p id="p-3" num="3">
|
| 42 |
+
<confidence value="8">2</confidence>
|
| 43 |
+
</p>
|
| 44 |
+
</description>
|
| 45 |
+
</us-patent-application>
|
| 46 |
+
|
prior_art/11171065.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
prior_art/11173839.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
prior_art/11179528.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
prior_art/11213129.xml
ADDED
|
@@ -0,0 +1,276 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11213129</doc-number>
|
| 8 |
+
<date>2005-08-26</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">Patent Application Attorney Docket Number 20041785-US-NP Express Mail Number ED 027847015 US </p>
|
| 14 |
+
<heading id="h-1">VEHICLE NETWORK ADVERTISING SYSTEM</heading>
|
| 15 |
+
<heading id="h-2">CROSS REFERENCE TO RELATED APPLICATIONS</heading>
|
| 16 |
+
<p id="p-2" num="2">[0001] The following copending applications, Attorney Docket Number 20041782-US-NP, U.S. Application Serial No. XX/XXX,XXX, filed August <part-num-ref name="following copending applications, Attorney Docket Number 20041782-US-NP, U.S. Application Serial No. XX/XXX,XXX, filed August">26,</part-num-ref>
|
| 17 |
+
<part-num-ref name="following copending applications, Attorney Docket Number 20041782-US-NP, U.S. Application Serial No. XX/XXX,XXX, filed August 26,">2005,</part-num-ref>
|
| 18 |
+
titled "Reverse Bidding for Trip Services", Attorney Docket Number 20041783-US-NP, U.S. Application Serial No. </p>
|
| 19 |
+
<p id="p-3" num="3">XX/XXX,XXX, filed August 26, 2005, titled "System for Propagating Advertisements for Market Controlled Presentation", and Attorney Docket Number 20041784-US-NP, U.S.</p>
|
| 20 |
+
<p id="p-4" num="4">Application Serial No. XX/XXX,XXX, filed August 26, 2005, titled "System to Manage Advertising and Coupon Presentation in Vehicles", are assigned to the same assignee of the present application. The entire disclosures of these copending applications are totally incorporated herein by reference in their entirety.</p>
|
| 21 |
+
<heading id="h-3">INCORPORATION BY REFERENCE</heading>
|
| 22 |
+
<p id="p-5" num="5">
|
| 23 |
+
<confidence value="5">[</confidence>
|
| 24 |
+
0002<confidence value="5">]</confidence>
|
| 25 |
+
The following U.S. patent publications are fully incorporated herein by reference: </p>
|
| 26 |
+
<p id="p-6" num="6">U.S. Publication Number 2001/0042038 to Phatak ("Method and System for Conducting an Auction for Resources"); U.S. Publication Number 2002/0032035 to Teshima ("Apparatus and Method for Delivery of Advertisement Information to Mobile Units"); U.S. Publication Number 2002/0194061 to Himmel et al. ("Method and System for Request Based Advertising on a Mobile Phone"); U.S. Publication Number 2003/0003929 to Himmel et al. ("Method and System for Schedule Based Advertising on a Mobile Phone"); and U.S. Publication Number 2004/0215526 to Luo et al. ("Interactive Shopping and Selling Via a Wireless Network").</p>
|
| 27 |
+
<heading id="h-4">BACKGROUND</heading>
|
| 28 |
+
<p id="p-7" num="7">[0003] This disclosure relates generally to the advertisement of goods and services to mobile units and more specifically to a digital context-aware advertisement delivery and presentation architecture.</p>
|
| 29 |
+
<boundary-data type="header">-1-</boundary-data>
|
| 30 |
+
<p id="p-8" num="8">
|
| 31 |
+
<page-break num="2"/>
|
| 32 |
+
<confidence value="5">[</confidence>
|
| 33 |
+
0004<confidence value="5">]</confidence>
|
| 34 |
+
Traditionally, roadside billboards have acted as a means for advertising goods and services to travelers, including drivers, walkers, and bikers. This advertising outlet has been frequently used by restaurants, automobile dealers, convenience stores, hotels, hospitals, and other service industries and manufacturers to provide information on services or goods available, as well as the location of the advertiser. However, billboard space is limited due to local restrictions and environmental concerns. An alternative to billboard advertising is vehicular network advertising which has become feasible with the development of more sophisticated wireless communication systems and the use of numerous sensing and control capabilities within mobile units. While vehicle network advertising would be a useful tool for advertisers to increase sales, customer affinity, and profits, there are problems associated with effectively using the ubiquitous sensing, computation and wireless communication infrastructure soon to be in place for such networks for issuing, deliver and presenting advertisements, particularly coupons, to customers in a user-friendly manner. </p>
|
| 35 |
+
<heading id="h-5">BRIEF SUMMARY</heading>
|
| 36 |
+
<p id="p-9" num="9">
|
| 37 |
+
<confidence value="5">[</confidence>
|
| 38 |
+
0005<confidence value="5">]</confidence>
|
| 39 |
+
The disclosed embodiments provide examples of improved solutions to the problems noted in the above Background discussion and the art cited therein. There is shown in these examples an improved architecture for context-aware advertisement and delivery among mobile communication devices over a communication network, in which the architecture is stored and executed as an application for use by network devices. The architecture includes a navigation module, which provides map data vehicles on the network and a context recognition module, which interprets data provided by sensors within the vehicle. Advertising data is received by a data reception module, and a configuration module determines presentation slot availability. The value and content of the advertisement are verified by the advertisement management module; selected advertisements are presented to the vehicle user. </p>
|
| 40 |
+
<boundary-data type="header">-2-</boundary-data>
|
| 41 |
+
<p id="p-10" num="10">
|
| 42 |
+
<page-break num="3"/>
|
| 43 |
+
<confidence value="5">[</confidence>
|
| 44 |
+
0006<confidence value="5">]</confidence>
|
| 45 |
+
In another embodiment there is provided an architecture for context-aware advertisement and delivery among mobile communication devices over a communication network, in which the architecture is stored and executed as an application for use by network devices. The architecture includes capability for providing map data for vehicles on the network, as well as interpreting data provided by sensors within the vehicle. As advertising data is received, it is entered into memory. Presentation slot availability is determined, with a presentation slot corresponding to a particular circumstance for which advertisements may be presented to a vehicle user. The architecture also includes capability for verifying the value and content of the advertisement before presenting it to a vehicle user. </p>
|
| 46 |
+
<p id="p-11" num="11">
|
| 47 |
+
<confidence value="5">[</confidence>
|
| 48 |
+
0007<confidence value="5">]</confidence>
|
| 49 |
+
In yet another embodiment there is disclosed a method for context-aware advertisement and delivery among mobile communication devices over a communication network, with the method stored and executed as an application for use by network devices. </p>
|
| 50 |
+
<p id="p-12" num="12">The method includes providing map data for vehicles on the network and interpreting localization data, map data, or device state data provided by sensors within the vehicle, as needed. When advertising data is received, it is entered into memory. Presentation slot availability is determined, with presentation slots corresponding to particular circumstances for which advertisements may be presented to a vehicle user. The method verifies the value and content of the advertisement before presenting it to the vehicle user.</p>
|
| 51 |
+
<p id="p-13" num="13">[0008] In yet another embodiment, there is disclosed a computer-readable storage medium having computer readable program code embodied in the medium causing the computer to perform method steps for context-aware advertisement and delivery among mobile communication devices over a communication network. The method includes providing map data for vehicles on the network and interpreting localization data, map data, or device state data provided by sensors within the vehicle, as needed. As advertising data is received, it is entered into memory. Presentation slot availability is determined, with presentation slots corresponding to particular circumstances for which advertisements may be presented to a vehicle user. The method verifies the value and content of the advertisement before presenting it to the vehicle user.</p>
|
| 52 |
+
<boundary-data type="header">-3-</boundary-data>
|
| 53 |
+
<heading id="h-6">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 54 |
+
<p id="p-14" num="14">
|
| 55 |
+
<page-break num="4"/>
|
| 56 |
+
<confidence value="5">[</confidence>
|
| 57 |
+
0009<confidence value="5">]</confidence>
|
| 58 |
+
The foregoing and other features of the embodiments described herein will be apparent and easily understood from a further reading of the specification, claims and by reference to the accompanying drawings in which: </p>
|
| 59 |
+
<p id="p-15" num="15">
|
| 60 |
+
<confidence value="5">[</confidence>
|
| 61 |
+
0010<confidence value="5">]</confidence>
|
| 62 |
+
FIG. 1 illustrates an example embodiment of the vehicle advertising network; </p>
|
| 63 |
+
<p id="p-16" num="16">
|
| 64 |
+
<confidence value="5">[</confidence>
|
| 65 |
+
0011<confidence value="5">]</confidence>
|
| 66 |
+
FIG. 2 illustrates one possible communication mode between an advertiser and a vehicle on the vehicle advertising network; </p>
|
| 67 |
+
<p id="p-17" num="17">
|
| 68 |
+
<confidence value="5">[</confidence>
|
| 69 |
+
0012<confidence value="5">]</confidence>
|
| 70 |
+
FIG. 3 illustrates another possible communication mode between an advertiser and a vehicle on the vehicle advertising network; </p>
|
| 71 |
+
<p id="p-18" num="18">
|
| 72 |
+
<confidence value="5">[</confidence>
|
| 73 |
+
0013<confidence value="5">]</confidence>
|
| 74 |
+
FIG. 4 illustrates an embodiment of the capabilities of vehicles participating in the vehicle advertising network; </p>
|
| 75 |
+
<p id="p-19" num="19">
|
| 76 |
+
<confidence value="5">[</confidence>
|
| 77 |
+
0014<confidence value="5">]</confidence>
|
| 78 |
+
FIG. 5 illustrates an embodiment of the computing architecture for vehicles participating in the vehicle advertising network; </p>
|
| 79 |
+
<p id="p-20" num="20">
|
| 80 |
+
<confidence value="5">[</confidence>
|
| 81 |
+
0015<confidence value="5">]</confidence>
|
| 82 |
+
FIG. 6 illustrates the operation of the computing architecture presented in Figure 5; </p>
|
| 83 |
+
<p id="p-21" num="21">
|
| 84 |
+
<confidence value="5">[</confidence>
|
| 85 |
+
0016<confidence value="5">]</confidence>
|
| 86 |
+
FIG. 7 illustrates one embodiment of a communication mode among vehicles on the vehicle advertising network; and <confidence value="5">[</confidence>
|
| 87 |
+
0017<confidence value="5">]</confidence>
|
| 88 |
+
FIG. 8 illustrates an embodiment of the computing architecture for vehicles participating in the vehicle advertising network in an inter-vehicle communication mode. </p>
|
| 89 |
+
<heading id="h-7">DETAILED DESCRIPTION</heading>
|
| 90 |
+
<p id="p-22" num="22">
|
| 91 |
+
<confidence value="5">[</confidence>
|
| 92 |
+
0018<confidence value="5">]</confidence>
|
| 93 |
+
The vehicle advertising network described herein provides a digital context-aware advertisement delivery and presentation framework which provides an effective strategy for product advertisement and business intelligence as vehicular communication devices and sensors are becoming more pervasive. The network includes an ad hoc wireless network system to propagate advertising for market-controlled presentation in vehicles, a system to <boundary-data type="header">-4-</boundary-data>
|
| 94 |
+
<page-break num="5"/>
|
| 95 |
+
manage advertising and coupon presentation in vehicles, and a reverse bidding framework for trip services. While for convenience and brevity in the following discussion a vehicle is described as an automobile moving on a roadway, it is noted that vehicle as used herein includes any mobile entity with a computing device having wireless communication capability, such as a boat, an airplane, or a user carrying a cell phone, as well as an automobile. All are fully contemplated by the specification and scope of the claims herein. </p>
|
| 96 |
+
<p id="p-23" num="23">
|
| 97 |
+
<confidence value="5">[</confidence>
|
| 98 |
+
0019] In the following description numerous specific details are set forth in order to provide a thorough understanding of the system and method. It would be apparent, however, to one skilled in the art to practice the system and method without such specific details. In other instances, specific implementation details have not been shown in detail in order not to unnecessarily obscure the present invention. Referring to Figure <confidence value="68">1,</confidence>
|
| 99 |
+
the schematic diagram illustrates an example embodiment of the system for vehicle network advertising. Intelligent transportation network <part-num-ref name="system for vehicle network advertising. Intelligent transportation network">110</part-num-ref>
|
| 100 |
+
may provide various capabilities, such as route information and navigation services, weather information, traffic information, road condition information, neighboring vehicle location, velocity and acceleration information, traffic light signal information, traffic sign information, retail/service location information, and AMBER alert information, among others, as well as advertising management. The server supporting intelligent transportation network <part-num-ref name="server supporting intelligent transportation network">110</part-num-ref>
|
| 101 |
+
may be a general-purpose computer upon which reside the software modules capable of managing system operation. It may also be a system designed specifically for inter vehicle communication into which software modules for coupon/advertisement management have been incorporated. </p>
|
| 102 |
+
<p id="p-24" num="24">[0020<confidence value="4">]</confidence>
|
| 103 |
+
Within intelligent transportation network 110 resides coupon and advertisement management module <part-num-ref name="resides coupon and advertisement management module">120,</part-num-ref>
|
| 104 |
+
which includes coupon/advertisement billing module <part-num-ref name="resides coupon and advertisement management module 120, which includes coupon/advertisement billing module">150,</part-num-ref>
|
| 105 |
+
coupon/advertisement admission module <part-num-ref name="resides coupon and advertisement management module 120, which includes coupon/advertisement billing module 150, coupon/advertisement admission module">140,</part-num-ref>
|
| 106 |
+
and coupon/advertisement distribution module <part-num-ref name="resides coupon and advertisement management module 120, which includes coupon/advertisement billing module 150, coupon/advertisement admission module 140, and coupon/advertisement distribution module">130.</part-num-ref>
|
| 107 |
+
Coupon/advertisement admission module <part-num-ref name="resides coupon and advertisement management module 120, which includes coupon/advertisement billing module 150, coupon/advertisement admission module 140, and coupon/advertisement distribution module 130. Coupon/advertisement admission module">140</part-num-ref>
|
| 108 |
+
may perform several functions, including accepting coupons/ads from advertisers with a chosen pricing scheme, determining the initial scope over which each coupon/ad is disseminated, and, optionally, stamping and authenticating the coupons/ads for propagation in the network. Coupon/ad distribution <boundary-data type="header">-5-</boundary-data>
|
| 109 |
+
<page-break num="6"/>
|
| 110 |
+
module <part-num-ref name="network. Coupon/ad distribution module">130</part-num-ref>
|
| 111 |
+
propagates the coupons/ads in the network according to prescribed scope parameters, such as area and time. Billing module <part-num-ref name="network according to prescribed scope parameters, such as area and time. Billing module">150</part-num-ref>
|
| 112 |
+
monitors the response of vehicle users to specific coupons and may use that information to compute the cost to the respective advertisers, and may use the information for adjustment of the presentation strategy to improve effectiveness of advertisement presentation. The billing module may also contain a function to trigger removal of propagation of a coupon/ad in the network, for example, upon request by the advertiser. Network <part-num-ref name="advertiser. Network">110</part-num-ref>
|
| 113 |
+
transmits information to participating vehicles <part-num-ref name="transmits information to participating vehicles">180</part-num-ref>
|
| 114 |
+
either directly or through transmission units <part-num-ref name="either directly or through transmission units">170</part-num-ref>
|
| 115 |
+
and <part-num-ref name="and">190</part-num-ref>
|
| 116 |
+
located along a roadway. </p>
|
| 117 |
+
<p id="p-25" num="25">[0021<confidence value="5">]</confidence>
|
| 118 |
+
While the architecture described in Fig 1 is independent of the underlying wireless transmission protocols, existing wireless transmission protocols such as DSRC (Dedicated Short Range Communication protocol), IEEE 802.11 (WiFi) may be used. There are no specific transmission protocols required for a vehicle to participate in the network except for the necessity of having a wireless signal reception interface for the chosen signal band and protocol. For intermediary transmission units such as units <part-num-ref name="chosen signal band and protocol. For intermediary transmission units such as units">170</part-num-ref>
|
| 119 |
+
and <part-num-ref name="and">190,</part-num-ref>
|
| 120 |
+
both reception and re-transmission capabilities are needed. The intermediary transmission units may receive signals from satellites or cellular towers, using a protocol and wireless media that are different from the one it uses to transmit to vehicles, as well as the protocol it uses to transmit among vehicles. Generally, network transmissions are based on a geographical broadcast, usually targeting vehicles in a specific area. The user does not need to access the central system before information is transmitted. </p>
|
| 121 |
+
<p id="p-26" num="26">[0022] Various computing environments may incorporate capabilities for supporting an intelligent transportation network. The following discussion is intended to provide a brief, general description of suitable computing environments in which the method and system may be implemented. Although not required, the method and system will be described in the general context of computer-executable instructions, such as program modules, being executed by a single computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the <boundary-data type="header">-6-</boundary-data>
|
| 122 |
+
<page-break num="7"/>
|
| 123 |
+
method and system may be practiced with other computer system configurations, including hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, networked P<confidence value="5">C</confidence>
|
| 124 |
+
s, minicomputers, mainframe computers, and the like. </p>
|
| 125 |
+
<p id="p-27" num="27">
|
| 126 |
+
<confidence value="5">[</confidence>
|
| 127 |
+
0023<confidence value="5">]</confidence>
|
| 128 |
+
The method and system may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communication network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices. </p>
|
| 129 |
+
<p id="p-28" num="28">
|
| 130 |
+
<confidence value="5">[</confidence>
|
| 131 |
+
0024<confidence value="5">]</confidence>
|
| 132 |
+
Turning now to Figure 2, there is illustrated one potential communication mode through the network. Here a service provider or advertiser <part-num-ref name="service provider or advertiser">230</part-num-ref>
|
| 133 |
+
communicates with the network through server <part-num-ref name="network through server">210.</part-num-ref>
|
| 134 |
+
Network advertising management modules residing within the server process the provider/advertiser information, identify vehicle traffic that may be interested in the provider/advertiser information, and transmit the information to vehicle <part-num-ref name="information to vehicle">220</part-num-ref>
|
| 135 |
+
via any of the transmission modes described hereinabove. </p>
|
| 136 |
+
<p id="p-29" num="29">[0025] An alternative communication mode is illustrated in Figure 3, in which the service provided/advertiser may communicate with the server, as described above with respect to Figure 2, or directly with vehicles. The information is in general sent to vehicles in one or multiple chosen geographical areas. However, the recipients may be further differentiated by other factors such as direction of travel (for example, vehicles approaching a service provider as opposed to traveling away from a service provider). To avoid a potential spa<confidence value="7">m</confidence>
|
| 137 |
+
problem, only information from authenticated advertisers may be propagated in the network. Each advertiser allowed to directly inject ads into the network is provided with an individualized unique digital key for the purpose of authentication, as discussed more fully hereinbelow with respect to Figure 5. </p>
|
| 138 |
+
<p id="p-30" num="30">
|
| 139 |
+
<confidence value="5">[</confidence>
|
| 140 |
+
0026<confidence value="5">]</confidence>
|
| 141 |
+
Only messages containing legitimate signatures are forwarded in the system. The software on each vehicle contains an authentication component for admission control. The admission control module also maintains a record of the admitted information. This record, similar to an effect and transaction related record (for example, a vehicle user may notice a <boundary-data type="header">-7-</boundary-data>
|
| 142 |
+
<page-break num="8"/>
|
| 143 |
+
particular ad or coupon, drive to the specific store, and cash the coupon), is transmitted to the central server at the appropriate time for billing purposes. In other words, a subscription is required to obtain transmission rights for direct vehicle communication. </p>
|
| 144 |
+
<p id="p-31" num="31">
|
| 145 |
+
<confidence value="5">[</confidence>
|
| 146 |
+
0027<confidence value="5">]</confidence>
|
| 147 |
+
Turning now to Figure 4, in one embodiment a vehicle capable of participating in the advertising network may include such features as gas level sensors, in-vehicle activity sensors, car health sensors, and tire pressure sensors, among others. These sensors form important support for the ad/coupon presentation process. Information from these sensors is used to decide when and what coupon/ad should be presented. In other words, the information provides useful context to enable context-awareness in coupon/ad presentation. The vehicle also includes wireless communication capability, which may take the form of IEEE 802.11 or the DSRC protocol. These capabilities are controlled through an onboard management computer system. This system may take the form of a general computer with input/output for wireless cards and sensors. The computer contains at least a central processing unit, some memory, storage, and network advertising operating system and software. </p>
|
| 148 |
+
<p id="p-32" num="32">
|
| 149 |
+
<confidence value="5">[</confidence>
|
| 150 |
+
0028<confidence value="5">]</confidence>
|
| 151 |
+
Figure 5 illustrates the software residing in the onboard computer in an advertising network vehicle. Raw sensor data <part-num-ref name="advertising network vehicle. Raw sensor data">590</part-num-ref>
|
| 152 |
+
is assembled and provided, with navigation software and data from module <part-num-ref name="is assembled and provided, with navigation software and data from module">580,</part-num-ref>
|
| 153 |
+
to context recognition module <part-num-ref name="is assembled and provided, with navigation software and data from module 580, to context recognition module">540.</part-num-ref>
|
| 154 |
+
Navigation software and data module <part-num-ref name="is assembled and provided, with navigation software and data from module 580, to context recognition module 540. Navigation software and data module">580</part-num-ref>
|
| 155 |
+
in general uses GPS data for localization, and may use estimation for occasional localization when GPS signals are not available. The software may use map data on the hard drive or portable media such as a CD or a flash memory card. Navigation software may be provided by the auto manufacturer or any other third party. Context recognition module <part-num-ref name="auto manufacturer or any other third party. Context recognition module">540</part-num-ref>
|
| 156 |
+
interprets the location (and area information, passenger travel destination information, etc.) data from navigation software and data module <part-num-ref name="location (and area information, passenger travel destination information, etc.) data from navigation software and data module">580</part-num-ref>
|
| 157 |
+
and vehicle state information, such as gas level, tire pressure, number of occupant, speed, to provide a few examples, from raw sensor data <part-num-ref name="few examples, from raw sensor data">590,</part-num-ref>
|
| 158 |
+
and forms a working context for the ad management software residing in ad management module <part-num-ref name="ad management software residing in ad management module">520.</part-num-ref>
|
| 159 |
+
One example of a working context is "fuel is low (from a sensor in the fuel gage), and a service station is in the vicinity (from a navigation location map)". A working context is a key trigger component for coupon presentation. </p>
|
| 160 |
+
<boundary-data type="header">-8-</boundary-data>
|
| 161 |
+
<p id="p-33" num="33">
|
| 162 |
+
<page-break num="9"/>
|
| 163 |
+
[0029] Data reception module 570 receives advertising data and may do some preliminary error checking (e.g. for transmission error). Decryption and authentication module <part-num-ref name="for transmission error). Decryption and authentication module">560</part-num-ref>
|
| 164 |
+
de- crypts data passed from data reception module <part-num-ref name="de- crypts data passed from data reception module">570</part-num-ref>
|
| 165 |
+
and checks the signature of the data using authentication mechanisms. One example authentication mechanism would be determining whether the signature appears among a set of legitimate numeric sequence distributed by the server. The decrypted data including the signature are passed to ad memory module <part-num-ref name="signature are passed to ad memory module">550.</part-num-ref>
|
| 166 |
+
Ad memory module <part-num-ref name="signature are passed to ad memory module 550. Ad memory module">550</part-num-ref>
|
| 167 |
+
includes capability for entering the new ad/coupon intro memory and storing the record (for example in the form of a signature/content pair) to a database on the hard drive. The record may also contain the time the data is received and may utilize finer grain content information, such as parsing the content into ad types, coupon value, ad value to the advertising service (amount the advertiser will pay for an effective ad presentation), advertiser name, target area, and valid presentation period, as a few examples. The database table may be managed according to ad types, validity time, or any other known approach. Ad memory module <part-num-ref name="database table may be managed according to ad types, validity time, or any other known approach. Ad memory module">550</part-num-ref>
|
| 168 |
+
receives a "valid ad" request from ad management module <part-num-ref name=""valid ad" request from ad management module">520</part-num-ref>
|
| 169 |
+
and transmits the set of matching valid ads back to ad management module <part-num-ref name="set of matching valid ads back to ad management module">520</part-num-ref>
|
| 170 |
+
which checks ad value and content of set of ads and calculates the effective value of presenting each ad to the vehicle user at a particular moment. It then selects one or a few of the best-valued advertisements and presents them to the vehicle user through ad presentation module <part-num-ref name="vehicle user through ad presentation module">510.</part-num-ref>
|
| 171 |
+
</p>
|
| 172 |
+
<p id="p-34" num="34">
|
| 173 |
+
<confidence value="5">[</confidence>
|
| 174 |
+
0030<confidence value="5">]</confidence>
|
| 175 |
+
As an illustrative example, two coupons may be received from service stations A and B respectively. Station A offers to pay $.<confidence value="4">0</confidence>
|
| 176 |
+
1 for each "drive-to after seeing coupon" event and station B offers to pay $.02 for each "drive-to after seeing coupon". Ad management module <part-num-ref name="offers to pay $.01 for each "drive-to after seeing coupon" event and station B offers to pay $.02 for each "drive-to after seeing coupon". Ad management module">520</part-num-ref>
|
| 177 |
+
may choose to present B's coupon at a particular moment. Ad management module <part-num-ref name="particular moment. Ad management module">520</part-num-ref>
|
| 178 |
+
may choose to present A's coupon rather than B's coupon if the following is true: </p>
|
| 179 |
+
<p id="p-35" num="35">B's station is relatively far away, and the driver's preference of A is known from history, especially if the estimated likelihood of the driver ignoring B's coupon is greater than fifty percent. Configuration module <part-num-ref name="driver ignoring B's coupon is greater than fifty percent. Configuration module">530</part-num-ref>
|
| 180 |
+
determines what presentation slots are available to be used and passes this information to ad management module <part-num-ref name="determines what presentation slots are available to be used and passes this information to ad management module">520.</part-num-ref>
|
| 181 |
+
The configuration module <part-num-ref name="configuration module">530</part-num-ref>
|
| 182 |
+
may contain a user interface to enable users to input presentation slots and preferences. </p>
|
| 183 |
+
<boundary-data type="header">-9-</boundary-data>
|
| 184 |
+
<p id="p-36" num="36">
|
| 185 |
+
<page-break num="10"/>
|
| 186 |
+
Ad management module 520 transmits the approved ads to ad presentation module <part-num-ref name="approved ads to ad presentation module">510,</part-num-ref>
|
| 187 |
+
which directs the ad to audio or video capabilities present in the vehicle. </p>
|
| 188 |
+
<p id="p-37" num="37">
|
| 189 |
+
<confidence value="5">[</confidence>
|
| 190 |
+
0031] Turning now to Figure 6, the architecture of the software onboard the vehicle is illustrated. Here, user interface <part-num-ref name="vehicle is illustrated. Here, user interface">610</part-num-ref>
|
| 191 |
+
communicates directly with reverse bidding management module <part-num-ref name="communicates directly with reverse bidding management module">620,</part-num-ref>
|
| 192 |
+
transaction event detector <part-num-ref name="communicates directly with reverse bidding management module 620, transaction event detector">630,</part-num-ref>
|
| 193 |
+
and ad presentation management module <part-num-ref name="communicates directly with reverse bidding management module 620, transaction event detector 630, and ad presentation management module">640.</part-num-ref>
|
| 194 |
+
</p>
|
| 195 |
+
<p id="p-38" num="38">Reverse bidding management module 620 enables retailers and service providers the opportunity of doing more informed targeting of potential customers as well as enabling them to perform inventory management and sales-pricing in real or near-real time. For example, a restaurant manager could be provided with the number and arrival time of customers prior to arrival; travelers would have opportunities to plan their route according to available services and service providers' bids on plausible and competing route plans, to obtain more efficient services. Ad presentation management module <part-num-ref name="number and arrival time of customers prior to arrival; travelers would have opportunities to plan their route according to available services and service providers' bids on plausible and competing route plans, to obtain more efficient services. Ad presentation management module">640</part-num-ref>
|
| 196 |
+
permits better advertising targeting and more effective use of ad time for advertisers, while travelers receive more relevant ads and avoid advertising overload. </p>
|
| 197 |
+
<p id="p-39" num="39">
|
| 198 |
+
<confidence value="5">[</confidence>
|
| 199 |
+
0032] Transaction event detector 630 receives vehicle location information from location service module <part-num-ref name="receives vehicle location information from location service module">660,</part-num-ref>
|
| 200 |
+
which determines location based on GPS data. Location change information may form a basis for detecting a "drive-to" event. Furthermore, a "click" on the items presented on the user interface may form a "click-though" event detected by transaction event detector <part-num-ref name=""click-though" event detected by transaction event detector">630.</part-num-ref>
|
| 201 |
+
Detected transaction events, such as a "drive-to" and "click-through" are used later for billing purposes. Context detection module <part-num-ref name=""drive-to" and "click-through" are used later for billing purposes. Context detection module">650</part-num-ref>
|
| 202 |
+
identifies additional information which would be useful for the purposes of targeting advertising. For example, it would determine if a child is present in the vehicle, the number of people in the vehicle, whether the trip is for leisure or business, whether the fuel level is low, the temperature is high, the tire pressure is low, or whether a meal break timing is approaching, etc. This information is then provided to reverse bidding management module <part-num-ref name="meal break timing is approaching, etc. This information is then provided to reverse bidding management module">620,</part-num-ref>
|
| 203 |
+
which has also received vehicle location information from location service module <part-num-ref name="meal break timing is approaching, etc. This information is then provided to reverse bidding management module 620, which has also received vehicle location information from location service module">660.</part-num-ref>
|
| 204 |
+
</p>
|
| 205 |
+
<p id="p-40" num="40">
|
| 206 |
+
<confidence value="5">[</confidence>
|
| 207 |
+
0033<confidence value="5">]</confidence>
|
| 208 |
+
Navigation support module 670 assists the driver in navigating the vehicle to specific locations and provides trip information and general area information to ad <boundary-data type="header">-10-</boundary-data>
|
| 209 |
+
<page-break num="11"/>
|
| 210 |
+
presentation module <part-num-ref name="vehicle to specific locations and provides trip information and general area information to ad presentation module">640.</part-num-ref>
|
| 211 |
+
Navigation support module <part-num-ref name="vehicle to specific locations and provides trip information and general area information to ad presentation module 640. Navigation support module">670</part-num-ref>
|
| 212 |
+
includes navigation map and navigation plan (via input from driver.) capability. The navigation maps may include business/service information at each location. Location service module <part-num-ref name="navigation maps may include business/service information at each location. Location service module">660</part-num-ref>
|
| 213 |
+
provides vehicle location information to transaction event detector module <part-num-ref name="provides vehicle location information to transaction event detector module">630</part-num-ref>
|
| 214 |
+
and reverse bidding management module <part-num-ref name="and reverse bidding management module">620.</part-num-ref>
|
| 215 |
+
While for the purposes of discussion modules <part-num-ref name="purposes of discussion modules">660</part-num-ref>
|
| 216 |
+
and <part-num-ref name="and">670</part-num-ref>
|
| 217 |
+
are illustrated as being separate modules, their functionality could be combined into a single navigation and location module. </p>
|
| 218 |
+
<p id="p-41" num="41">
|
| 219 |
+
<confidence value="5">[</confidence>
|
| 220 |
+
0034<confidence value="5">]</confidence>
|
| 221 |
+
Authentication module 690 checks the signature of the advertisement/coupon data using authentication mechanisms. Any known mechanism for authentication may be employed, for example, checking whether the signature appears among a set of legitimate numeric sequence (provided by the central server). The authenticated ads are passed to ad presentation module <part-num-ref name="authenticated ads are passed to ad presentation module">640.</part-num-ref>
|
| 222 |
+
Communication module <part-num-ref name="authenticated ads are passed to ad presentation module 640. Communication module">680</part-num-ref>
|
| 223 |
+
receives ad data and passes it to authentication module <part-num-ref name="receives ad data and passes it to authentication module">690.</part-num-ref>
|
| 224 |
+
In scenarios where no authentication is required, it may pass the received data directly to <part-num-ref name="received data directly to">640.</part-num-ref>
|
| 225 |
+
Additionally authentication module <part-num-ref name="received data directly to 640. Additionally authentication module">690</part-num-ref>
|
| 226 |
+
provides authenticated data to reverse bidding management module <part-num-ref name="provides authenticated data to reverse bidding management module">620</part-num-ref>
|
| 227 |
+
for reverse bidding management. The reverse bidding management functions include sending bid solicitations to service providers, selecting and aggregating bids along alternate trip routes, seeking additional input from the vehicle user, finalizing a trip plan, sending the plan to the navigation system, communicating the route decision to service providers, monitoring the progress on the route and carrying out alert and reminder functions. </p>
|
| 228 |
+
<p id="p-42" num="42">
|
| 229 |
+
<confidence value="5">[</confidence>
|
| 230 |
+
0035<confidence value="5">]</confidence>
|
| 231 |
+
Reverse bidding module 620 may send bid solicitations to communication module <part-num-ref name="may send bid solicitations to communication module">680,</part-num-ref>
|
| 232 |
+
which then sends the solicitations out to service providers and provides the received bids, deals, or advertisements and the identification of the bidder to reverse bidding management module <part-num-ref name="bidder to reverse bidding management module">620</part-num-ref>
|
| 233 |
+
for selection, aggregation and presentation to the user through user interface <part-num-ref name="user through user interface">610.</part-num-ref>
|
| 234 |
+
Operation of reverse bidding management module <part-num-ref name="user through user interface 610. Operation of reverse bidding management module">620</part-num-ref>
|
| 235 |
+
is further described in Attorney Docket Number 20041782-US-NP, U.S. Application Serial No. XX<confidence value="5">/</confidence>
|
| 236 |
+
XXX,XXX, filed August <part-num-ref name="is further described in Attorney Docket Number 20041782-US-NP, U.S. Application Serial No. XX/XXX,XXX, filed August">26,</part-num-ref>
|
| 237 |
+
<part-num-ref name="is further described in Attorney Docket Number 20041782-US-NP, U.S. Application Serial No. XX/XXX,XXX, filed August 26,">2005,</part-num-ref>
|
| 238 |
+
titled "Reverse Bidding for Trip Services", incorporated by reference hereinabove <boundary-data type="header">-11-</boundary-data>
|
| 239 |
+
<page-break num="12"/>
|
| 240 |
+
[0036<confidence value="5">]</confidence>
|
| 241 |
+
Turning now to Figure 7, there is illustrated another potential communication mode through the network. Here communication is achieved among vehicles <part-num-ref name="network. Here communication is achieved among vehicles">710</part-num-ref>
|
| 242 |
+
rather than through a central network via communication capabilities <part-num-ref name="central network via communication capabilities">720</part-num-ref>
|
| 243 |
+
over an ad hoc network. In this mode, vehicles receive messages directly from advertisers or from an advertising service, as described more fully with reference to Figure 8 below. </p>
|
| 244 |
+
<p id="p-43" num="43">[0037<confidence value="5">]</confidence>
|
| 245 |
+
As illustrated in Figure 8, the schematic diagram illustrates an example embodiment of the system for propagating advertisements for market-controlled presentation in an ad hoc advertising network. Before an advertiser can launch an advertisement into the propagation network <part-num-ref name="propagation network">830,</part-num-ref>
|
| 246 |
+
the advertiser <part-num-ref name="advertiser">820</part-num-ref>
|
| 247 |
+
must contact an advertising service <part-num-ref name="advertising service">810</part-num-ref>
|
| 248 |
+
and obtain authorization to propagate the advertisement. This is described more fully in copending application Attorney Docket Number 20041783-US-NP, U.S. Application Serial No. XX/XXX,XXX, titled "System for Propagating Advertisements for Market Controlled Presentation". The advertisement presented to the advertising system by the advertiser <part-num-ref name="advertiser">820</part-num-ref>
|
| 249 |
+
may be in the form of text or image, audio or video, and could include special offers, such as coupons or discounts. The advertiser also may present a bid to the system. The details of the bid may depend on the economic mechanism that is used, but would usually specify a <confidence value="5">'</confidence>
|
| 250 |
+
presentation slot', and some indication of what the advertiser will pay for a successful advertisement presentation. For example, an advertiser might bid on the "low gas warning" presentation slot, bidding $.50, indicating that it will pay one dollar when a driver responds to the ad by driving to the gas station. The text of the advertisement may be "Unleaded regular gas $1.80, after a $.20/gallon discount to the recipient if this message, use exit 25." <confidence value="5">[</confidence>
|
| 251 |
+
0038] When advertising service <part-num-ref name="recipient if this message, use exit 25." [0038] When advertising service">810</part-num-ref>
|
| 252 |
+
authorizes the advertisement, it may also include ranking information that is computed from the bid. So, in the case of the gasoline example, the ranking information may be the bid itself, in this case $.50. This corresponds to a simple auction, where slots are awarded to the advertisers that are willing to pay the most per response. More complex auctions may rank bidders according to an estimate of the revenue, that is, the product of the probability of response with the amount bid. In such an auction, the advertiser would compute this estimate and include it in the certification record. </p>
|
| 253 |
+
<boundary-data type="header">-12-</boundary-data>
|
| 254 |
+
<p id="p-44" num="44">
|
| 255 |
+
<page-break num="13"/>
|
| 256 |
+
<confidence value="5">[</confidence>
|
| 257 |
+
0039<confidence value="5">]</confidence>
|
| 258 |
+
Propagation of the advertisement through network <part-num-ref name="advertisement through network">830</part-num-ref>
|
| 259 |
+
is governed by targeting information that is supplied by the advertiser, and by the geography and traffic loads that the advertisement encounters as it is propagated. For example, in the case of the gasoline advertisement, the advertiser may wish to target only the southbound lanes of a nearby highway, and northwards for five miles or until <part-num-ref name="nearby highway, and northwards for five miles or until">250</part-num-ref>
|
| 260 |
+
vehicles are reached. Vehicle condition and environmental information are used to govern the presentation of the advertisement and advertisers can be charged by verified successful presentation. If driver <part-num-ref name="advertisement and advertisers can be charged by verified successful presentation. If driver">840</part-num-ref>
|
| 261 |
+
responds to an advertisement by either selecting the advertisement to obtain more information or driving to the place of business described in the advertisement, then a response record is generated and propagated back to advertising service <part-num-ref name="response record is generated and propagated back to advertising service">810.</part-num-ref>
|
| 262 |
+
When advertising service <part-num-ref name="response record is generated and propagated back to advertising service 810. When advertising service">810</part-num-ref>
|
| 263 |
+
receives a response record, it allows the advertising service to charge for the advertisements. Together, the authorization and the response record allow the vehicle to implement market-based presentation slot advertising without an online connection. </p>
|
| 264 |
+
<p id="p-45" num="45">
|
| 265 |
+
<confidence value="5">[</confidence>
|
| 266 |
+
0040<confidence value="5">]</confidence>
|
| 267 |
+
While the present discussion has been illustrated and described with reference to specific embodiments, further modification and improvements will occur to those skilled in the art. For example, the system may provide the users counter-offer capabilities. Assuming a user was presented a gas coupon bearing a 5% discount, the user could query other service stations in the area to determine if the same discount or a better discount is available from a competitor<confidence value="8">'</confidence>
|
| 268 |
+
s service station. Additionally, "code" as used herein, or "program" as used herein, is any plurality of binary values or any executable, interpreted or compiled code which can be used by a computer or execution device to perform a task. This code or program can be written in any one of several known computer languages. A "computer," as used herein, can mean any device which stores, processes, routes, manipulates, or performs like operation on data. It is to be understood, therefore, that this disclosure is not limited to the particular forms illustrated and that it is intended in the appended claims to embrace all alternatives, modifications, and variations which do not depart from the spirit and scope of the embodiments described herein. </p>
|
| 269 |
+
<boundary-data type="header">-13-</boundary-data>
|
| 270 |
+
<p id="p-46" num="46">
|
| 271 |
+
<page-break num="14"/>
|
| 272 |
+
[0041] The claims, as originally presented and as they may be amended, encompass variations, alternatives, modifications, improvements, equivalents, and substantial equivalents of the embodiments and teachings disclosed herein, including those that are presently unforeseen or unappreciated, and that, for example, may arise from applicants/patentees and others. </p>
|
| 273 |
+
<boundary-data type="header">-14-</boundary-data>
|
| 274 |
+
</description>
|
| 275 |
+
</us-patent-application>
|
| 276 |
+
|
prior_art/11213396.xml
ADDED
|
@@ -0,0 +1,1457 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11213396</doc-number>
|
| 8 |
+
<date>2005-12-14</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">DEC-14-2005 11<confidence value="5">:</confidence>
|
| 14 |
+
47 FROM ROSENBAUM <confidence value="5">8</confidence>
|
| 15 |
+
ASSOCI<confidence value="8">A</confidence>
|
| 16 |
+
TES TO 15712738300 P.04 </boundary-data>
|
| 17 |
+
<boundary-data type="header">App<confidence value="7">l</confidence>
|
| 18 |
+
e. No. <confidence value="66">11</confidence>
|
| 19 |
+
/213.396 </boundary-data>
|
| 20 |
+
<boundary-data type="header">Amdt<confidence value="5">.</confidence>
|
| 21 |
+
Dated Dec. 13, 2005 </boundary-data>
|
| 22 |
+
<heading id="h-1">AMENDMENTS <confidence value="68">TO</confidence>
|
| 23 |
+
<confidence value="668">THE</confidence>
|
| 24 |
+
<confidence value="222222222222">SPECIICATION</confidence>
|
| 25 |
+
</heading>
|
| 26 |
+
<p id="p-1" num="1">Please replace the paragraph beginning at page <part-num-ref name="paragraph beginning at page">30,</part-num-ref>
|
| 27 |
+
line <part-num-ref name="paragraph beginning at page 30, line">20,</part-num-ref>
|
| 28 |
+
which starts with "Another embodiment", with the following amended paragraph: </p>
|
| 29 |
+
<p id="p-2" num="2">Another embodiment of the present invention is the compound of formula (I), wherein E, D<confidence value="4">'</confidence>
|
| 30 |
+
and L' are as defined; <confidence value="11">L2</confidence>
|
| 31 |
+
is <confidence value="5">0</confidence>
|
| 32 |
+
; A and A<confidence value="5">'</confidence>
|
| 33 |
+
are independently (CH2)<confidence value="4">d</confidence>
|
| 34 |
+
, 1,2- phenylene, 1,3-phenylene, or 1,4-phenylene; <confidence value="5">d</confidence>
|
| 35 |
+
is 1-4; B is S-S<confidence value="5">,</confidence>
|
| 36 |
+
S-S<confidence value="44">=0</confidence>
|
| 37 |
+
, S-S<confidence value="4">0</confidence>
|
| 38 |
+
2 or S- <confidence value="8">S</confidence>
|
| 39 |
+
NH; a is 0; <confidence value="66">D2</confidence>
|
| 40 |
+
is NO, N<confidence value="5">O</confidence>
|
| 41 |
+
2 or a nitric oxide releasing molecule such as NONOate<confidence value="5">.</confidence>
|
| 42 |
+
In a further embodiment, D2 is a NON<confidence value="5">O</confidence>
|
| 43 |
+
ate selected from the group consisting of<confidence value="5">:</confidence>
|
| 44 |
+
</p>
|
| 45 |
+
<p id="p-3" num="3">Ac0<confidence value="1161">,V01</confidence>
|
| 46 |
+
<confidence value="8111111">-.*.pN,</confidence>
|
| 47 |
+
<confidence value="26">AN</confidence>
|
| 48 |
+
<confidence value="28">+N</confidence>
|
| 49 |
+
<confidence value="562222">H2C,-O</confidence>
|
| 50 |
+
<confidence value="516">RIN</confidence>
|
| 51 |
+
<confidence value="226">%0-</confidence>
|
| 52 |
+
<confidence value="6">,</confidence>
|
| 53 |
+
<confidence value="56166">7R7RN</confidence>
|
| 54 |
+
<confidence value="6">-</confidence>
|
| 55 |
+
<confidence value="666">and</confidence>
|
| 56 |
+
<confidence value="85816">R7R1N</confidence>
|
| 57 |
+
<confidence value="22">"-</confidence>
|
| 58 |
+
- In <confidence value="666">yet</confidence>
|
| 59 |
+
anothe<confidence value="8">r</confidence>
|
| 60 |
+
<confidence value="2222222222">embediemnt</confidence>
|
| 61 |
+
embodimen<confidence value="86">t,</confidence>
|
| 62 |
+
when [[<confidence value="6868">D2]]</confidence>
|
| 63 |
+
<confidence value="66">D2</confidence>
|
| 64 |
+
is one of the above NONOates, B is S-S. </p>
|
| 65 |
+
<p id="p-4" num="4">Please replace the paragraph beginning at page <part-num-ref name="paragraph beginning at page">96,</part-num-ref>
|
| 66 |
+
line <part-num-ref name="paragraph beginning at page 96, line">2,</part-num-ref>
|
| 67 |
+
which begins with "Drugs listed", with the following amended paragraph: </p>
|
| 68 |
+
<p id="p-5" num="5">Drugs listed in the following list can be converted to <confidence value="5154">NQ-r</confidence>
|
| 69 |
+
eleasing prodrugs <confidence value="58">of</confidence>
|
| 70 |
+
formula <confidence value="45">I.</confidence>
|
| 71 |
+
This list is in no way limiting the scope of drugs covered in this invention, but given as representative examples. All the amino- (including amide-NH and sulf<confidence value="4885">onam</confidence>
|
| 72 |
+
ide<confidence value="5">-</confidence>
|
| 73 |
+
NH, carbamate-N<confidence value="56">H,</confidence>
|
| 74 |
+
sulf<confidence value="5">a</confidence>
|
| 75 |
+
mate-N<confidence value="5">H</confidence>
|
| 76 |
+
, hydrazone-N<confidence value="66">H,</confidence>
|
| 77 |
+
semicarbazone-N<confidence value="66">H,</confidence>
|
| 78 |
+
thiosemicarbazone-N<confidence value="66">H,</confidence>
|
| 79 |
+
urea-NH, phosphoramide-NH and the like. See above, for the description of "amino-containing drugs"), <confidence value="5">c</confidence>
|
| 80 |
+
arboxyl-, <confidence value="5">h</confidence>
|
| 81 |
+
ydroxyl-(including oxime-OH), and carbonyl (both aldehyde and keto groups)-containing drugs under various therapeutic categories as listed in Merck Index <part-num-ref name="description of "amino-containing drugs"), carboxyl-, hydroxyl-(including oxime-OH), and carbonyl (both aldehyde and keto groups)-containing drugs under various therapeutic categories as listed in Merck Index">(13</part-num-ref>
|
| 82 |
+
<part-num-ref name="">
|
| 83 |
+
<confidence value="2">4</confidence>
|
| 84 |
+
</part-num-ref>
|
| 85 |
+
editions) and other data bases such as prous science's ensemble, integrity, and the like and also all the qualified (i.e., amino-, and <confidence value="588">/or</confidence>
|
| 86 |
+
hydroxyl-, and/or carboxyl-, and/or carbonyl-containing) investigational drugs as listed in databases such Merck Index (<confidence value="685">13a</confidence>
|
| 87 |
+
editions), iddb, ensemble, integrity, and the like<confidence value="5">.</confidence>
|
| 88 |
+
are covered under this invention without any limitation<confidence value="5">.</confidence>
|
| 89 |
+
</p>
|
| 90 |
+
<boundary-data type="header">2 of 39</boundary-data>
|
| 91 |
+
<boundary-data type="header">PAGE <confidence value="868858854">4141'RCVD</confidence>
|
| 92 |
+
AT <confidence value="861884">12)141</confidence>
|
| 93 |
+
200<confidence value="5885885">512:40:</confidence>
|
| 94 |
+
00 PM <confidence value="5">[</confidence>
|
| 95 |
+
Easte<confidence value="66">rn</confidence>
|
| 96 |
+
Standard Time<confidence value="68">]'</confidence>
|
| 97 |
+
<confidence value="866668885586686886">SVR:USPTO-EFXRF32'</confidence>
|
| 98 |
+
DNIS<confidence value="5">:</confidence>
|
| 99 |
+
2738300'<confidence value="66866888">CSID:847</confidence>
|
| 100 |
+
<confidence value="888">770</confidence>
|
| 101 |
+
<confidence value="88884">6006'</confidence>
|
| 102 |
+
DURAT<confidence value="668">ION</confidence>
|
| 103 |
+
(mm<confidence value="5">s</confidence>
|
| 104 |
+
s):<confidence value="5566">0934</confidence>
|
| 105 |
+
</boundary-data>
|
| 106 |
+
<boundary-data type="header">DEC-14-2005 11<confidence value="5">:</confidence>
|
| 107 |
+
47 FROM ROSEN<confidence value="66">BA</confidence>
|
| 108 |
+
UM <confidence value="52">8.</confidence>
|
| 109 |
+
ASSOCI<confidence value="8">A</confidence>
|
| 110 |
+
TES TO 1571273<confidence value="4">8</confidence>
|
| 111 |
+
300 P.05 </boundary-data>
|
| 112 |
+
<boundary-data type="header">App<confidence value="7">l</confidence>
|
| 113 |
+
e. No.11/213<confidence value="5">.</confidence>
|
| 114 |
+
396 </boundary-data>
|
| 115 |
+
<boundary-data type="header">
|
| 116 |
+
<confidence value="2222">Amdt</confidence>
|
| 117 |
+
. Da<confidence value="8">t</confidence>
|
| 118 |
+
ed Dec. 13, 2005 </boundary-data>
|
| 119 |
+
<p id="p-6" num="6">
|
| 120 |
+
<page-break num="2"/>
|
| 121 |
+
Please replace the paragraph beginning at page <part-num-ref name="paragraph beginning at page">109,</part-num-ref>
|
| 122 |
+
on line <part-num-ref name="paragraph beginning at page 109, on line">9,</part-num-ref>
|
| 123 |
+
which starts with "It is appreciated", with the following amended paragraph: </p>
|
| 124 |
+
<p id="p-7" num="7">It is appreciated that <confidence value="5282">NQ-r</confidence>
|
| 125 |
+
eleasi<confidence value="2">n</confidence>
|
| 126 |
+
g prodrugs of any two or more drugs from the above lists of potential drugs can be used in combination depending on the medical application/need. While a combination formulation may occassionally consist of more than two drugs (depending on the medical need), the following pairs of drugs are covered in this invention as illustrative pairs of candidate drugs for combination therapy<confidence value="2">.</confidence>
|
| 127 |
+
</p>
|
| 128 |
+
<p id="p-8" num="8">Please replace the paragraph beginning at page <part-num-ref name="paragraph beginning at page">111,</part-num-ref>
|
| 129 |
+
line <part-num-ref name="paragraph beginning at page 111, line">6,</part-num-ref>
|
| 130 |
+
which starts with "It <confidence value="22222">shoud</confidence>
|
| 131 |
+
", with the following amended paragraph: </p>
|
| 132 |
+
<p id="p-9" num="9">It [[shoud<confidence value="66">]]</confidence>
|
| 133 |
+
should be understood that either or both of any selected pair of drugs (in any proportion) can be in the form of prodrug(s) of formula (<confidence value="5">I</confidence>
|
| 134 |
+
) or pharmaceutically acceptable salts thereof and the other drug can be in its native form. For clarity, let us assume that <confidence value="56">Ib</confidence>
|
| 135 |
+
uprofen and Paracetamol are present as active principles in a pharmaceutical <confidence value="22222222222">eempeisiien</confidence>
|
| 136 |
+
com<confidence value="8">p</confidence>
|
| 137 |
+
osition<confidence value="6">.</confidence>
|
| 138 |
+
Then, either or both of these drugs can be in their N<confidence value="521">O-r</confidence>
|
| 139 |
+
eleasi<confidence value="5">n</confidence>
|
| 140 |
+
g prodrug form (i.e., NO-Paracetamol and Ibuprofen<confidence value="5">/</confidence>
|
| 141 |
+
Paracetamol and NO-<confidence value="56">Ib</confidence>
|
| 142 |
+
uprofen/ NO-Paraceta<confidence value="5">m</confidence>
|
| 143 |
+
ol and NO<confidence value="4">-</confidence>
|
| 144 |
+
Ibuprofen, etc.) and they can be present in any proportion. </p>
|
| 145 |
+
<p id="p-10" num="10">Please replace the paragraph beginning at page <part-num-ref name="paragraph beginning at page">111,</part-num-ref>
|
| 146 |
+
line <part-num-ref name="paragraph beginning at page 111, line">18,</part-num-ref>
|
| 147 |
+
which starts with "It should also<confidence value="5">"</confidence>
|
| 148 |
+
, with the following amended paragraph: </p>
|
| 149 |
+
<p id="p-11" num="11">It should also be understood that a pharmaceutical composition containing a combination of one of the above listed/qualified drug(s) and its own prodrug is also covered (<confidence value="66">i.</confidence>
|
| 150 |
+
e., a pharmaceutical composition consisting of NO-Paracetamol and Paracetamol in any proportion). In such pharmaceutical combinations, the free drug will be useful for faster onset of action and the prodrug will be useful for extension of the duration of action as it releases the drug in a controlled fashion over a longer period of time. Such combination drug therapy may also minimize the toxicity and other side effects due to excessive plasma concentration of free drug. It should also be understood that a pharmaceutical combination may contain a prodrug of one of the above listed/qualified drugs and an another type of prodrug of the same drug (i.e., NO prodrug <boundary-data type="header">3 of 39</boundary-data>
|
| 151 |
+
<boundary-data type="header">PAGE 5141 <confidence value="2">*</confidence>
|
| 152 |
+
RCVD AT 12<confidence value="18818558">11412005</confidence>
|
| 153 |
+
12:40:0<confidence value="5">0</confidence>
|
| 154 |
+
PM [Easte<confidence value="66">rn</confidence>
|
| 155 |
+
Standard T<confidence value="56824">ime]'</confidence>
|
| 156 |
+
SVR:USPT<confidence value="45">O-</confidence>
|
| 157 |
+
EFXRF<confidence value="4882884">432*DNI</confidence>
|
| 158 |
+
S:2738300<confidence value="5">'</confidence>
|
| 159 |
+
CSI<confidence value="5">D</confidence>
|
| 160 |
+
:84<confidence value="8">7</confidence>
|
| 161 |
+
<confidence value="88">77</confidence>
|
| 162 |
+
0 6<confidence value="586">006</confidence>
|
| 163 |
+
DURAT<confidence value="668">ION</confidence>
|
| 164 |
+
<confidence value="8822">(mm-</confidence>
|
| 165 |
+
ss):09<confidence value="288">-34</confidence>
|
| 166 |
+
</boundary-data>
|
| 167 |
+
<page-break num="3"/>
|
| 168 |
+
<boundary-data type="header">DEC-14-200<confidence value="5">5</confidence>
|
| 169 |
+
11:<confidence value="86">47</confidence>
|
| 170 |
+
FROM ROSENB<confidence value="8">A</confidence>
|
| 171 |
+
UM <confidence value="6">&</confidence>
|
| 172 |
+
ASSOCI<confidence value="8">A</confidence>
|
| 173 |
+
TES TO 15712738300 P.<confidence value="88">06</confidence>
|
| 174 |
+
</boundary-data>
|
| 175 |
+
<boundary-data type="header">App<confidence value="7">l</confidence>
|
| 176 |
+
e. No.11/213.396 </boundary-data>
|
| 177 |
+
<boundary-data type="header">Amdt. Dated D<confidence value="5">e</confidence>
|
| 178 |
+
c. 13, 2005 </boundary-data>
|
| 179 |
+
of <confidence value="2222222222">prasetamel</confidence>
|
| 180 |
+
<confidence value="22222222222">paracetamol</confidence>
|
| 181 |
+
and mutual prodrug of paracetamol with another dr<confidence value="8">u</confidence>
|
| 182 |
+
g) and these can be present in any therapeutic proportion depending on the medical need<confidence value="5">.</confidence>
|
| 183 |
+
</p>
|
| 184 |
+
<boundary-data type="header">4 of 39</boundary-data>
|
| 185 |
+
<boundary-data type="header">PAGE <confidence value="86882">6141*</confidence>
|
| 186 |
+
<confidence value="8888">RCVD</confidence>
|
| 187 |
+
<confidence value="88">AT</confidence>
|
| 188 |
+
<confidence value="66665">12142</confidence>
|
| 189 |
+
00512:40:00 <confidence value="88">PM</confidence>
|
| 190 |
+
<confidence value="66">[E</confidence>
|
| 191 |
+
aste<confidence value="5">m</confidence>
|
| 192 |
+
Standard Time<confidence value="558666">]'SVR:</confidence>
|
| 193 |
+
USPT<confidence value="446666684882">O0EFXRF4132*</confidence>
|
| 194 |
+
DNIS:2<confidence value="5">7</confidence>
|
| 195 |
+
38300<confidence value="4">'</confidence>
|
| 196 |
+
CSID:84<confidence value="8">7</confidence>
|
| 197 |
+
<confidence value="258">710</confidence>
|
| 198 |
+
6006<confidence value="4">'</confidence>
|
| 199 |
+
DURAT<confidence value="668">ION</confidence>
|
| 200 |
+
<confidence value="8866">(mm.</confidence>
|
| 201 |
+
ss):09<confidence value="668">.34</confidence>
|
| 202 |
+
</boundary-data>
|
| 203 |
+
<boundary-data type="header">DEC-14-2005 11<confidence value="2">:</confidence>
|
| 204 |
+
48 FROM ROSENBAUM <confidence value="5">8</confidence>
|
| 205 |
+
ASSOCIATES TO 15712738300 P<confidence value="456">.07</confidence>
|
| 206 |
+
</boundary-data>
|
| 207 |
+
<boundary-data type="header">App<confidence value="7">l</confidence>
|
| 208 |
+
e. No.<confidence value="5">1</confidence>
|
| 209 |
+
1/213.396 </boundary-data>
|
| 210 |
+
<boundary-data type="header">
|
| 211 |
+
<confidence value="2222">Amdt</confidence>
|
| 212 |
+
. Dated D<confidence value="5">e</confidence>
|
| 213 |
+
c. 13, 2005 </boundary-data>
|
| 214 |
+
<p id="p-12" num="12">
|
| 215 |
+
<page-break num="4"/>
|
| 216 |
+
Please replace the entire <confidence value="8">p</confidence>
|
| 217 |
+
age <part-num-ref name="entire page">33</part-num-ref>
|
| 218 |
+
with the following amended page: </p>
|
| 219 |
+
<p id="p-13" num="13">(a) From carboxyl-containing drugs: (a) From carboxyl-containing drugs:</p>
|
| 220 |
+
<p id="p-14" num="14">
|
| 221 |
+
<confidence value="2">o</confidence>
|
| 222 |
+
0 <part-num-ref name="">0</part-num-ref>
|
| 223 |
+
<confidence value="858">H3C</confidence>
|
| 224 |
+
<confidence value="4">O</confidence>
|
| 225 |
+
O H3<confidence value="8">C</confidence>
|
| 226 |
+
<confidence value="4">O</confidence>
|
| 227 |
+
<confidence value="4">O</confidence>
|
| 228 |
+
<confidence value="865">H30</confidence>
|
| 229 |
+
<part-num-ref name="H3C O O H3C O O H30">
|
| 230 |
+
<confidence value="5">0</confidence>
|
| 231 |
+
</part-num-ref>
|
| 232 |
+
<confidence value="5">O</confidence>
|
| 233 |
+
<confidence value="1121">6-O1</confidence>
|
| 234 |
+
<confidence value="4">S</confidence>
|
| 235 |
+
<confidence value="126">O0H</confidence>
|
| 236 |
+
<confidence value="1">K</confidence>
|
| 237 |
+
<confidence value="11">r,</confidence>
|
| 238 |
+
<confidence value="141">8Sr</confidence>
|
| 239 |
+
<confidence value="55">OH</confidence>
|
| 240 |
+
I-C1-PD1 I<confidence value="682">-C1</confidence>
|
| 241 |
+
-PD<confidence value="5">2</confidence>
|
| 242 |
+
I-C<confidence value="58865">l-PD3</confidence>
|
| 243 |
+
<confidence value="4">o</confidence>
|
| 244 |
+
<confidence value="4">O</confidence>
|
| 245 |
+
<confidence value="6562">H3C0</confidence>
|
| 246 |
+
<part-num-ref name="O 6-O1 S O0H K r, 8Sr OH I-C1-PD1 I-C1-PD2 I-Cl-PD3 o O H3C0">
|
| 247 |
+
<confidence value="2">0</confidence>
|
| 248 |
+
</part-num-ref>
|
| 249 |
+
<part-num-ref name="">
|
| 250 |
+
<confidence value="2">0</confidence>
|
| 251 |
+
</part-num-ref>
|
| 252 |
+
<confidence value="85814">H3CAO</confidence>
|
| 253 |
+
<confidence value="6">O</confidence>
|
| 254 |
+
<confidence value="4">o</confidence>
|
| 255 |
+
<confidence value="415144">lKNAkO</confidence>
|
| 256 |
+
<confidence value="71">Sr</confidence>
|
| 257 |
+
<confidence value="6">O</confidence>
|
| 258 |
+
<confidence value="2661">ICHs</confidence>
|
| 259 |
+
<confidence value="5">S</confidence>
|
| 260 |
+
<confidence value="6">O</confidence>
|
| 261 |
+
<confidence value="662">CH3</confidence>
|
| 262 |
+
<confidence value="4">o</confidence>
|
| 263 |
+
<confidence value="5884">I-CI</confidence>
|
| 264 |
+
-PD<confidence value="65">4a</confidence>
|
| 265 |
+
<confidence value="6686">I-Cl</confidence>
|
| 266 |
+
-PD4b <confidence value="11">NC</confidence>
|
| 267 |
+
= a metal ion <confidence value="48">FC</confidence>
|
| 268 |
+
<confidence value="8">O</confidence>
|
| 269 |
+
<confidence value="844">H00</confidence>
|
| 270 |
+
<part-num-ref name="metal ion FC O H00">
|
| 271 |
+
<confidence value="5">0</confidence>
|
| 272 |
+
</part-num-ref>
|
| 273 |
+
<confidence value="5">O</confidence>
|
| 274 |
+
<confidence value="11">O^</confidence>
|
| 275 |
+
<confidence value="41">S,</confidence>
|
| 276 |
+
<confidence value="7127">NI-6</confidence>
|
| 277 |
+
<confidence value="1">I</confidence>
|
| 278 |
+
<confidence value="8">N</confidence>
|
| 279 |
+
<confidence value="22">OH</confidence>
|
| 280 |
+
<confidence value="5">O</confidence>
|
| 281 |
+
I-C<confidence value="5">1</confidence>
|
| 282 |
+
-PD<confidence value="5">S</confidence>
|
| 283 |
+
<confidence value="214884">HOI-Cl</confidence>
|
| 284 |
+
-PD6 <confidence value="6171">H3Cx</confidence>
|
| 285 |
+
O O O H<confidence value="17">3C</confidence>
|
| 286 |
+
O O <confidence value="1">&</confidence>
|
| 287 |
+
<confidence value="1211">IHN'</confidence>
|
| 288 |
+
<confidence value="1">^</confidence>
|
| 289 |
+
<confidence value="611">S"$</confidence>
|
| 290 |
+
OH <confidence value="1">O</confidence>
|
| 291 |
+
<confidence value="1">-</confidence>
|
| 292 |
+
<confidence value="271">,Ca</confidence>
|
| 293 |
+
I-C1-<confidence value="588">PD7</confidence>
|
| 294 |
+
<confidence value="717">H3C</confidence>
|
| 295 |
+
<confidence value="1">O</confidence>
|
| 296 |
+
O <confidence value="7">N</confidence>
|
| 297 |
+
<confidence value="1">H</confidence>
|
| 298 |
+
I-C1-PD9 <confidence value="222121">-G-PW0</confidence>
|
| 299 |
+
</p>
|
| 300 |
+
<heading id="h-2">
|
| 301 |
+
<confidence value="85">CI</confidence>
|
| 302 |
+
</heading>
|
| 303 |
+
<heading id="h-3">N N</heading>
|
| 304 |
+
<heading id="h-4">
|
| 305 |
+
<confidence value="22">\/</confidence>
|
| 306 |
+
<confidence value="6">O</confidence>
|
| 307 |
+
</heading>
|
| 308 |
+
<p id="p-15" num="15">
|
| 309 |
+
<confidence value="666566655">I-C1-PD10</confidence>
|
| 310 |
+
<confidence value="666566656">I-C1-PD10</confidence>
|
| 311 |
+
<confidence value="212">HoH</confidence>
|
| 312 |
+
<confidence value="22">H0</confidence>
|
| 313 |
+
<confidence value="1">~</confidence>
|
| 314 |
+
<confidence value="82">H3</confidence>
|
| 315 |
+
<confidence value="22">HH</confidence>
|
| 316 |
+
<confidence value="1">O</confidence>
|
| 317 |
+
<confidence value="1172">I-C1</confidence>
|
| 318 |
+
-PD<confidence value="11">11</confidence>
|
| 319 |
+
<confidence value="718">HsC</confidence>
|
| 320 |
+
<confidence value="2">N</confidence>
|
| 321 |
+
<confidence value="27">-S</confidence>
|
| 322 |
+
<confidence value="2">H</confidence>
|
| 323 |
+
<confidence value="6">I</confidence>
|
| 324 |
+
<confidence value="1">C</confidence>
|
| 325 |
+
-PD12 </p>
|
| 326 |
+
<heading id="h-5">O O</heading>
|
| 327 |
+
<p id="p-16" num="16">I-C<confidence value="488656">l-PD13</confidence>
|
| 328 |
+
<confidence value="22">sC</confidence>
|
| 329 |
+
<confidence value="6">0</confidence>
|
| 330 |
+
<part-num-ref name="">
|
| 331 |
+
<confidence value="5">0</confidence>
|
| 332 |
+
</part-num-ref>
|
| 333 |
+
<confidence value="858">HaC</confidence>
|
| 334 |
+
<confidence value="145">.HH</confidence>
|
| 335 |
+
<confidence value="2">N</confidence>
|
| 336 |
+
<confidence value="45">a0</confidence>
|
| 337 |
+
<confidence value="4">o</confidence>
|
| 338 |
+
<confidence value="6">H</confidence>
|
| 339 |
+
<part-num-ref name="HaC .HH N a0 o H">
|
| 340 |
+
<confidence value="2">0</confidence>
|
| 341 |
+
</part-num-ref>
|
| 342 |
+
<confidence value="8">H</confidence>
|
| 343 |
+
I-C<confidence value="58655">l-PD1</confidence>
|
| 344 |
+
4 I<confidence value="58584">-C1-M</confidence>
|
| 345 |
+
<confidence value="5">a</confidence>
|
| 346 |
+
<confidence value="4">O</confidence>
|
| 347 |
+
<confidence value="85">Na</confidence>
|
| 348 |
+
<confidence value="8685886688">I-C1-PD15b</confidence>
|
| 349 |
+
<boundary-data type="header">5 of <confidence value="88">39</confidence>
|
| 350 |
+
</boundary-data>
|
| 351 |
+
<boundary-data type="header">PAGE <confidence value="86882">7141'</confidence>
|
| 352 |
+
RCVD <confidence value="88">AT</confidence>
|
| 353 |
+
<confidence value="884885">121141</confidence>
|
| 354 |
+
200<confidence value="4">5</confidence>
|
| 355 |
+
12:40:00 <confidence value="88">PM</confidence>
|
| 356 |
+
<confidence value="5">[</confidence>
|
| 357 |
+
Easte<confidence value="66">rn</confidence>
|
| 358 |
+
Standard Time] SVR:USPT<confidence value="56858856884">O-EFXRF432'</confidence>
|
| 359 |
+
DNIS:2738300<confidence value="2">'</confidence>
|
| 360 |
+
CSID:847 770 6006 DURAT<confidence value="668">ION</confidence>
|
| 361 |
+
<confidence value="885">(mm</confidence>
|
| 362 |
+
ss):09<confidence value="568">.34</confidence>
|
| 363 |
+
</boundary-data>
|
| 364 |
+
<page-break num="5"/>
|
| 365 |
+
<boundary-data type="header">DEC-14-2005 11:48 FROM ROSENBAUM <confidence value="6">&</confidence>
|
| 366 |
+
ASSOCI<confidence value="8">A</confidence>
|
| 367 |
+
TES TO 15712738300 P.08 </boundary-data>
|
| 368 |
+
<boundary-data type="header">App<confidence value="7">l</confidence>
|
| 369 |
+
e. No.<confidence value="4">1</confidence>
|
| 370 |
+
1/213<confidence value="5">.</confidence>
|
| 371 |
+
396 </boundary-data>
|
| 372 |
+
<boundary-data type="header">
|
| 373 |
+
<confidence value="2222">Amdt</confidence>
|
| 374 |
+
. Da<confidence value="8">t</confidence>
|
| 375 |
+
ed Dec. 13, 2005 </boundary-data>
|
| 376 |
+
Please replace the entire page <part-num-ref name="entire page">37</part-num-ref>
|
| 377 |
+
with the following amended page: </p>
|
| 378 |
+
<p id="p-17" num="17">
|
| 379 |
+
<confidence value="855">NO2</confidence>
|
| 380 |
+
<confidence value="858">NO2</confidence>
|
| 381 |
+
<confidence value="5">O</confidence>
|
| 382 |
+
<confidence value="252">CH3</confidence>
|
| 383 |
+
<confidence value="1">O</confidence>
|
| 384 |
+
<confidence value="1">O</confidence>
|
| 385 |
+
<confidence value="1222">SRN:</confidence>
|
| 386 |
+
<confidence value="812">H31</confidence>
|
| 387 |
+
<confidence value="1">\</confidence>
|
| 388 |
+
<confidence value="78112781">I-H1-PDI</confidence>
|
| 389 |
+
<confidence value="82">NO</confidence>
|
| 390 |
+
CH<confidence value="1">3</confidence>
|
| 391 |
+
<confidence value="1">i</confidence>
|
| 392 |
+
<confidence value="778822">IH-PD2</confidence>
|
| 393 |
+
CH, </p>
|
| 394 |
+
<heading id="h-6">
|
| 395 |
+
<confidence value="2">O</confidence>
|
| 396 |
+
<confidence value="7">R</confidence>
|
| 397 |
+
<confidence value="2">H</confidence>
|
| 398 |
+
</heading>
|
| 399 |
+
<p id="p-18" num="18">
|
| 400 |
+
<confidence value="2">N</confidence>
|
| 401 |
+
<confidence value="11">H3</confidence>
|
| 402 |
+
<confidence value="21111112111">N-i-D]0-H3~</confidence>
|
| 403 |
+
<confidence value="67722">1-PCH</confidence>
|
| 404 |
+
<confidence value="222221">NROOH3</confidence>
|
| 405 |
+
<confidence value="2222">NO20</confidence>
|
| 406 |
+
<confidence value="8">o</confidence>
|
| 407 |
+
<confidence value="11">CM</confidence>
|
| 408 |
+
<confidence value="12">NA</confidence>
|
| 409 |
+
<confidence value="1111">Q><~</confidence>
|
| 410 |
+
<confidence value="1">A</confidence>
|
| 411 |
+
<confidence value="1">~</confidence>
|
| 412 |
+
<confidence value="88">CI</confidence>
|
| 413 |
+
<confidence value="52556556">NO2I-PD4</confidence>
|
| 414 |
+
<confidence value="8">R</confidence>
|
| 415 |
+
<confidence value="5">=</confidence>
|
| 416 |
+
<confidence value="86">H,</confidence>
|
| 417 |
+
lower alkyl, e<confidence value="52">tm</confidence>
|
| 418 |
+
<confidence value="2">l</confidence>
|
| 419 |
+
<confidence value="682">CH3</confidence>
|
| 420 |
+
<confidence value="66">HN</confidence>
|
| 421 |
+
<confidence value="22685">'_CH3</confidence>
|
| 422 |
+
<confidence value="22">lH</confidence>
|
| 423 |
+
<confidence value="5">S</confidence>
|
| 424 |
+
<confidence value="2">;</confidence>
|
| 425 |
+
</p>
|
| 426 |
+
<p id="p-19" num="19">NH2 <confidence value="51">Na</confidence>
|
| 427 |
+
<confidence value="48858884">1-H1-PDS</confidence>
|
| 428 |
+
<confidence value="854">NH2</confidence>
|
| 429 |
+
<confidence value="85">N3</confidence>
|
| 430 |
+
<confidence value="5824">I-H1</confidence>
|
| 431 |
+
-PD6 </p>
|
| 432 |
+
<heading id="h-7">
|
| 433 |
+
<confidence value="2">O</confidence>
|
| 434 |
+
</heading>
|
| 435 |
+
<p id="p-20" num="20">
|
| 436 |
+
<confidence value="2">O</confidence>
|
| 437 |
+
<confidence value="2">N</confidence>
|
| 438 |
+
O O<confidence value="22">H0</confidence>
|
| 439 |
+
N <confidence value="2">R</confidence>
|
| 440 |
+
<confidence value="2">O</confidence>
|
| 441 |
+
<confidence value="88665">I-HI-</confidence>
|
| 442 |
+
PD7 <confidence value="48858681">I-H1-PDS</confidence>
|
| 443 |
+
</p>
|
| 444 |
+
<heading id="h-8">
|
| 445 |
+
<confidence value="5">H</confidence>
|
| 446 |
+
<confidence value="6">-</confidence>
|
| 447 |
+
<confidence value="4">O</confidence>
|
| 448 |
+
<confidence value="844">ONN</confidence>
|
| 449 |
+
</heading>
|
| 450 |
+
<heading id="h-9">
|
| 451 |
+
<confidence value="5">H</confidence>
|
| 452 |
+
<confidence value="2">N</confidence>
|
| 453 |
+
</heading>
|
| 454 |
+
<p id="p-21" num="21">
|
| 455 |
+
<confidence value="2211221">CHflHCN</confidence>
|
| 456 |
+
<confidence value="661">CHS</confidence>
|
| 457 |
+
<confidence value="12">H3</confidence>
|
| 458 |
+
<confidence value="2">H</confidence>
|
| 459 |
+
<confidence value="412224">ON---O</confidence>
|
| 460 |
+
<confidence value="1">_</confidence>
|
| 461 |
+
<confidence value="1">Q</confidence>
|
| 462 |
+
<confidence value="1">Q</confidence>
|
| 463 |
+
I-H<confidence value="2">1</confidence>
|
| 464 |
+
-PD<confidence value="12">10</confidence>
|
| 465 |
+
<confidence value="1">0</confidence>
|
| 466 |
+
H-- <confidence value="51">Ry</confidence>
|
| 467 |
+
<part-num-ref name="H-- Ry">
|
| 468 |
+
<confidence value="2">0</confidence>
|
| 469 |
+
</part-num-ref>
|
| 470 |
+
<confidence value="882">--0</confidence>
|
| 471 |
+
<confidence value="5">Q</confidence>
|
| 472 |
+
<part-num-ref name="--0 Q">
|
| 473 |
+
<confidence value="2">0</confidence>
|
| 474 |
+
</part-num-ref>
|
| 475 |
+
H I-H<confidence value="58884">1-PD1</confidence>
|
| 476 |
+
<confidence value="2">%</confidence>
|
| 477 |
+
</p>
|
| 478 |
+
<heading id="h-10">
|
| 479 |
+
<confidence value="2">-</confidence>
|
| 480 |
+
N N </heading>
|
| 481 |
+
<p id="p-22" num="22">
|
| 482 |
+
<confidence value="2">O</confidence>
|
| 483 |
+
<confidence value="871">CHa</confidence>
|
| 484 |
+
<confidence value="11112">lNY-°</confidence>
|
| 485 |
+
<confidence value="1164">H-2n</confidence>
|
| 486 |
+
N <confidence value="21">0O</confidence>
|
| 487 |
+
<confidence value="11">_,</confidence>
|
| 488 |
+
<confidence value="17177711">IH1-PD12</confidence>
|
| 489 |
+
<confidence value="2">0</confidence>
|
| 490 |
+
<confidence value="21">Ry</confidence>
|
| 491 |
+
<confidence value="1">_</confidence>
|
| 492 |
+
<confidence value="1111">H2CH</confidence>
|
| 493 |
+
<confidence value="11111111">NHCMOCCH</confidence>
|
| 494 |
+
<confidence value="1111">(~y2</confidence>
|
| 495 |
+
= a<confidence value="61721">in-dh</confidence>
|
| 496 |
+
ain gr<confidence value="6886">oups</confidence>
|
| 497 |
+
<confidence value="42">oO</confidence>
|
| 498 |
+
<confidence value="41">an</confidence>
|
| 499 |
+
add<confidence value="86">s)</confidence>
|
| 500 |
+
or any <confidence value="1112">limu</confidence>
|
| 501 |
+
<confidence value="68">or</confidence>
|
| 502 |
+
<confidence value="222222">nmloul</confidence>
|
| 503 |
+
conta<confidence value="88877">ining</confidence>
|
| 504 |
+
<confidence value="688668">water-</confidence>
|
| 505 |
+
<confidence value="488586656">I-HI-PD13</confidence>
|
| 506 |
+
<confidence value="2224">Wu"g</confidence>
|
| 507 |
+
<confidence value="445">Wps</confidence>
|
| 508 |
+
<confidence value="8151">sidi</confidence>
|
| 509 |
+
<confidence value="6">a</confidence>
|
| 510 |
+
s <confidence value="222222">hydrfy</confidence>
|
| 511 |
+
<confidence value="66">am</confidence>
|
| 512 |
+
<confidence value="862">no,</confidence>
|
| 513 |
+
<confidence value="866">and</confidence>
|
| 514 |
+
<confidence value="222222">artoyi</confidence>
|
| 515 |
+
<confidence value="22222221">hphat*e.</confidence>
|
| 516 |
+
<confidence value="222227">sulte.</confidence>
|
| 517 |
+
<confidence value="1211">etc_</confidence>
|
| 518 |
+
<confidence value="885">NO2</confidence>
|
| 519 |
+
<confidence value="2">N</confidence>
|
| 520 |
+
<confidence value="1111111111">(td-HI-8m4</confidence>
|
| 521 |
+
<confidence value="611621">NK'CH,</confidence>
|
| 522 |
+
I-HI-<confidence value="1111">PD14</confidence>
|
| 523 |
+
<boundary-data type="header">6 of <confidence value="88">39</confidence>
|
| 524 |
+
</boundary-data>
|
| 525 |
+
<boundary-data type="header">PAGE 8141<confidence value="2">*</confidence>
|
| 526 |
+
RCVD <confidence value="88">AT</confidence>
|
| 527 |
+
<confidence value="881884">121141</confidence>
|
| 528 |
+
200<confidence value="4">5</confidence>
|
| 529 |
+
12:40:00<confidence value="88">PM</confidence>
|
| 530 |
+
<confidence value="5">[</confidence>
|
| 531 |
+
Easte<confidence value="5">m</confidence>
|
| 532 |
+
Standard <confidence value="85588666">TineSVR:</confidence>
|
| 533 |
+
USPT<confidence value="52666865885">O-EFXRF432'</confidence>
|
| 534 |
+
DNIS:2738300<confidence value="28545">'C8ID</confidence>
|
| 535 |
+
:847 <confidence value="588">770</confidence>
|
| 536 |
+
6006 DURAT<confidence value="668">ION</confidence>
|
| 537 |
+
<confidence value="88566">(mm.s</confidence>
|
| 538 |
+
s):<confidence value="55265">09-34</confidence>
|
| 539 |
+
</boundary-data>
|
| 540 |
+
<page-break num="6"/>
|
| 541 |
+
<boundary-data type="header">DEC-14-2005 11:48 FROM ROSENBAUM <confidence value="6">&</confidence>
|
| 542 |
+
ASSOCI<confidence value="8">A</confidence>
|
| 543 |
+
TES TO 1571273<confidence value="5">8</confidence>
|
| 544 |
+
300 P.09 </boundary-data>
|
| 545 |
+
<boundary-data type="header">App<confidence value="6">l</confidence>
|
| 546 |
+
e. No.11<confidence value="5">/</confidence>
|
| 547 |
+
213.3<confidence value="4">9</confidence>
|
| 548 |
+
</boundary-data>
|
| 549 |
+
<boundary-data type="header">
|
| 550 |
+
<confidence value="2222">Amdt</confidence>
|
| 551 |
+
. Dated D<confidence value="5">e</confidence>
|
| 552 |
+
c. 13, 2005 </boundary-data>
|
| 553 |
+
Please replace the entire page <part-num-ref name="entire page">41</part-num-ref>
|
| 554 |
+
with the following amended page: </p>
|
| 555 |
+
<p id="p-23" num="23">(b) From amino-containing drugs <confidence value="5">o</confidence>
|
| 556 |
+
<confidence value="5">O</confidence>
|
| 557 |
+
<confidence value="88448">EtO2C</confidence>
|
| 558 |
+
<confidence value="1">N</confidence>
|
| 559 |
+
<confidence value="11">0"</confidence>
|
| 560 |
+
<confidence value="51411">SX'%^</confidence>
|
| 561 |
+
<confidence value="1855">%N02</confidence>
|
| 562 |
+
<confidence value="8558">H02C</confidence>
|
| 563 |
+
<confidence value="412">NNA</confidence>
|
| 564 |
+
<confidence value="66">NO</confidence>
|
| 565 |
+
<confidence value="4884">I-A1</confidence>
|
| 566 |
+
-NOPD1 <confidence value="2">p</confidence>
|
| 567 |
+
<confidence value="268">[-A</confidence>
|
| 568 |
+
-NO<confidence value="562">PD2</confidence>
|
| 569 |
+
<confidence value="85">CI</confidence>
|
| 570 |
+
<confidence value="5">O</confidence>
|
| 571 |
+
<confidence value="64">Cr</confidence>
|
| 572 |
+
<confidence value="4">i</confidence>
|
| 573 |
+
<confidence value="11">rC</confidence>
|
| 574 |
+
H2N <confidence value="2">N</confidence>
|
| 575 |
+
<confidence value="88">NH</confidence>
|
| 576 |
+
<confidence value="588">H2N</confidence>
|
| 577 |
+
<confidence value="8">N</confidence>
|
| 578 |
+
<confidence value="2">N</confidence>
|
| 579 |
+
<confidence value="1">0</confidence>
|
| 580 |
+
<confidence value="625">NO2</confidence>
|
| 581 |
+
I-A<confidence value="2">I</confidence>
|
| 582 |
+
-NOP<confidence value="668">D3A</confidence>
|
| 583 |
+
I-A<confidence value="2">l</confidence>
|
| 584 |
+
-NO<confidence value="6625">PD3B</confidence>
|
| 585 |
+
<part-num-ref name="NO2 I-AI-NOPD3A I-Al-NOPD3B">
|
| 586 |
+
<confidence value="2">0</confidence>
|
| 587 |
+
</part-num-ref>
|
| 588 |
+
</p>
|
| 589 |
+
<heading id="h-11">
|
| 590 |
+
<confidence value="5">N</confidence>
|
| 591 |
+
<confidence value="5">O</confidence>
|
| 592 |
+
</heading>
|
| 593 |
+
<p id="p-24" num="24">
|
| 594 |
+
<confidence value="56">CH</confidence>
|
| 595 |
+
<confidence value="2">e</confidence>
|
| 596 |
+
<confidence value="222">CO2</confidence>
|
| 597 |
+
<confidence value="21">Me</confidence>
|
| 598 |
+
I-A<confidence value="4">1</confidence>
|
| 599 |
+
-NOPD4 <confidence value="6666668662">I-Al-NOPD5</confidence>
|
| 600 |
+
<confidence value="2">M</confidence>
|
| 601 |
+
<confidence value="214">9"-</confidence>
|
| 602 |
+
<confidence value="11122">--,&N</confidence>
|
| 603 |
+
Me OMe <confidence value="22">HN</confidence>
|
| 604 |
+
<confidence value="22">NN</confidence>
|
| 605 |
+
<confidence value="211">Oin</confidence>
|
| 606 |
+
<confidence value="1">S</confidence>
|
| 607 |
+
<confidence value="2">N</confidence>
|
| 608 |
+
<confidence value="22122">2MeNO</confidence>
|
| 609 |
+
<confidence value="6662665652">I-A--NOPD7</confidence>
|
| 610 |
+
</p>
|
| 611 |
+
<heading id="h-12">
|
| 612 |
+
<confidence value="2">(</confidence>
|
| 613 |
+
<confidence value="1">C</confidence>
|
| 614 |
+
<confidence value="2">O</confidence>
|
| 615 |
+
<confidence value="2">N</confidence>
|
| 616 |
+
</heading>
|
| 617 |
+
<p id="p-25" num="25">
|
| 618 |
+
<confidence value="155">3eo</confidence>
|
| 619 |
+
<confidence value="6">C</confidence>
|
| 620 |
+
<confidence value="2">0</confidence>
|
| 621 |
+
<confidence value="65">CI</confidence>
|
| 622 |
+
I-A<confidence value="4">1</confidence>
|
| 623 |
+
-NOPD<confidence value="5">S</confidence>
|
| 624 |
+
<confidence value="1111222222222212">HNNOI-Al-NOPD10a</confidence>
|
| 625 |
+
<confidence value="2">O</confidence>
|
| 626 |
+
<confidence value="22">Nt</confidence>
|
| 627 |
+
<confidence value="1111">N0NQ</confidence>
|
| 628 |
+
<confidence value="11">^/</confidence>
|
| 629 |
+
<confidence value="1">O</confidence>
|
| 630 |
+
<confidence value="212">0-'</confidence>
|
| 631 |
+
<confidence value="212">N0N</confidence>
|
| 632 |
+
<confidence value="111">pN0</confidence>
|
| 633 |
+
<confidence value="1">L</confidence>
|
| 634 |
+
<confidence value="7">I</confidence>
|
| 635 |
+
<confidence value="21">N.</confidence>
|
| 636 |
+
<confidence value="212">N~N</confidence>
|
| 637 |
+
<confidence value="2">F</confidence>
|
| 638 |
+
<confidence value="1">~</confidence>
|
| 639 |
+
<confidence value="2">j</confidence>
|
| 640 |
+
<confidence value="1">a</confidence>
|
| 641 |
+
<confidence value="1">F</confidence>
|
| 642 |
+
<confidence value="2">-</confidence>
|
| 643 |
+
<confidence value="1">R</confidence>
|
| 644 |
+
<confidence value="1">N</confidence>
|
| 645 |
+
<confidence value="111">PJ~</confidence>
|
| 646 |
+
<confidence value="21112">HO's0</confidence>
|
| 647 |
+
<confidence value="21212">7ON0N</confidence>
|
| 648 |
+
<confidence value="122">O2N</confidence>
|
| 649 |
+
<confidence value="1111">-NPD</confidence>
|
| 650 |
+
<confidence value="2">F</confidence>
|
| 651 |
+
<confidence value="1">S</confidence>
|
| 652 |
+
<confidence value="1">O</confidence>
|
| 653 |
+
</p>
|
| 654 |
+
<heading id="h-13">
|
| 655 |
+
<confidence value="881">CH,</confidence>
|
| 656 |
+
</heading>
|
| 657 |
+
<p id="p-26" num="26">I-A<confidence value="2">l</confidence>
|
| 658 |
+
-NO<confidence value="68558">PD10b</confidence>
|
| 659 |
+
<confidence value="1">o</confidence>
|
| 660 |
+
<confidence value="1">P</confidence>
|
| 661 |
+
<confidence value="11">c0</confidence>
|
| 662 |
+
<confidence value="1">3</confidence>
|
| 663 |
+
<confidence value="2">N</confidence>
|
| 664 |
+
<confidence value="7">N</confidence>
|
| 665 |
+
<confidence value="6">O</confidence>
|
| 666 |
+
<confidence value="611">S.S</confidence>
|
| 667 |
+
<confidence value="1">O</confidence>
|
| 668 |
+
<confidence value="7">N</confidence>
|
| 669 |
+
<confidence value="1">O</confidence>
|
| 670 |
+
<part-num-ref name="N N O S.S O N O">
|
| 671 |
+
<confidence value="1">2</confidence>
|
| 672 |
+
</part-num-ref>
|
| 673 |
+
<confidence value="2">S</confidence>
|
| 674 |
+
<confidence value="2">N</confidence>
|
| 675 |
+
<confidence value="2">O</confidence>
|
| 676 |
+
<confidence value="4">o</confidence>
|
| 677 |
+
<confidence value="5">O</confidence>
|
| 678 |
+
<confidence value="5">O</confidence>
|
| 679 |
+
<confidence value="5">O</confidence>
|
| 680 |
+
I-A<confidence value="4">2</confidence>
|
| 681 |
+
-NOPD<confidence value="1">t</confidence>
|
| 682 |
+
a I-A<confidence value="488">Z-N</confidence>
|
| 683 |
+
OPD<confidence value="58">1b</confidence>
|
| 684 |
+
<confidence value="5">N</confidence>
|
| 685 |
+
<part-num-ref name="S N O o O O O I-A2-NOPDta I-AZ-NOPD1b N">
|
| 686 |
+
<confidence value="2">0</confidence>
|
| 687 |
+
</part-num-ref>
|
| 688 |
+
<confidence value="6662665665">I-A2-NOPDa</confidence>
|
| 689 |
+
<confidence value="6666666866">-A2-NOPD2b</confidence>
|
| 690 |
+
<boundary-data type="header">
|
| 691 |
+
<confidence value="8">7</confidence>
|
| 692 |
+
<confidence value="68">of</confidence>
|
| 693 |
+
<confidence value="88">39</confidence>
|
| 694 |
+
</boundary-data>
|
| 695 |
+
<boundary-data type="header">PAGE <confidence value="52862">9141*</confidence>
|
| 696 |
+
RCVD <confidence value="88">AT</confidence>
|
| 697 |
+
<confidence value="884882">12/141</confidence>
|
| 698 |
+
200512:40:00 <confidence value="88">PM</confidence>
|
| 699 |
+
<confidence value="5">[</confidence>
|
| 700 |
+
Easte<confidence value="66">rn</confidence>
|
| 701 |
+
Standard Time<confidence value="42">)'</confidence>
|
| 702 |
+
<confidence value="866">SR:</confidence>
|
| 703 |
+
USPT<confidence value="5868855884">OEFXRF432'</confidence>
|
| 704 |
+
DNIS:2738300<confidence value="5">'</confidence>
|
| 705 |
+
CSI<confidence value="5">D</confidence>
|
| 706 |
+
:847 770 6006 <confidence value="1">t</confidence>
|
| 707 |
+
DURAT<confidence value="668">ION</confidence>
|
| 708 |
+
<confidence value="8886">(mm-</confidence>
|
| 709 |
+
ss):09<confidence value="17">34</confidence>
|
| 710 |
+
</boundary-data>
|
| 711 |
+
<page-break num="7"/>
|
| 712 |
+
<boundary-data type="header">DEC-14-2005 11:48 FROM ROSEN<confidence value="66">BA</confidence>
|
| 713 |
+
UM 8<confidence value="5">.</confidence>
|
| 714 |
+
ASSOCI<confidence value="8">A</confidence>
|
| 715 |
+
TES TO 15712738300 P.10 </boundary-data>
|
| 716 |
+
<boundary-data type="header">App<confidence value="7">l</confidence>
|
| 717 |
+
e. No.<confidence value="88885">11/21</confidence>
|
| 718 |
+
3.39<confidence value="5">6</confidence>
|
| 719 |
+
</boundary-data>
|
| 720 |
+
<boundary-data type="header">
|
| 721 |
+
<confidence value="22226">Amdt.</confidence>
|
| 722 |
+
Dated Dec. 13, 2005 </boundary-data>
|
| 723 |
+
Please replace page <part-num-ref name="I-A2-NOPDa -A2-NOPD2b Please replace page">52</part-num-ref>
|
| 724 |
+
with the following amended page: </p>
|
| 725 |
+
<p id="p-27" num="27">
|
| 726 |
+
<confidence value="88">Ph</confidence>
|
| 727 |
+
<confidence value="5">s</confidence>
|
| 728 |
+
<confidence value="622">CO2</confidence>
|
| 729 |
+
<confidence value="2">0</confidence>
|
| 730 |
+
<confidence value="1">H</confidence>
|
| 731 |
+
<part-num-ref name="H">
|
| 732 |
+
<confidence value="2">0</confidence>
|
| 733 |
+
</part-num-ref>
|
| 734 |
+
<part-num-ref name="">
|
| 735 |
+
<confidence value="2">0</confidence>
|
| 736 |
+
</part-num-ref>
|
| 737 |
+
<confidence value="221">KJ~</confidence>
|
| 738 |
+
<confidence value="2">H</confidence>
|
| 739 |
+
<confidence value="22">No</confidence>
|
| 740 |
+
<confidence value="2222222222222">Sultamacillin</confidence>
|
| 741 |
+
<confidence value="4">O</confidence>
|
| 742 |
+
<confidence value="6">N</confidence>
|
| 743 |
+
<confidence value="2">O</confidence>
|
| 744 |
+
<confidence value="54">CI</confidence>
|
| 745 |
+
Ph <confidence value="5688668865">I-CA-MPD10</confidence>
|
| 746 |
+
<part-num-ref name="KJ~ H No Sultamacillin O N O CI Ph I-CA-MPD10">
|
| 747 |
+
<confidence value="2">0</confidence>
|
| 748 |
+
</part-num-ref>
|
| 749 |
+
<confidence value="85">CO</confidence>
|
| 750 |
+
2H Me<confidence value="586">O2C</confidence>
|
| 751 |
+
<confidence value="82265">CO2Et</confidence>
|
| 752 |
+
<part-num-ref name="CO2H MeO2C CO2Et">
|
| 753 |
+
<confidence value="6">0</confidence>
|
| 754 |
+
</part-num-ref>
|
| 755 |
+
<confidence value="6">N</confidence>
|
| 756 |
+
<confidence value="858">H3C</confidence>
|
| 757 |
+
<confidence value="2">N</confidence>
|
| 758 |
+
<confidence value="8">N</confidence>
|
| 759 |
+
<confidence value="2">O</confidence>
|
| 760 |
+
<confidence value="422">SOH</confidence>
|
| 761 |
+
</p>
|
| 762 |
+
<heading id="h-14">
|
| 763 |
+
<confidence value="8">H</confidence>
|
| 764 |
+
<confidence value="4">O</confidence>
|
| 765 |
+
OH </heading>
|
| 766 |
+
<p id="p-28" num="28">
|
| 767 |
+
<confidence value="55">HN</confidence>
|
| 768 |
+
<confidence value="66">OH</confidence>
|
| 769 |
+
I-CA<confidence value="666852">-MPDIl</confidence>
|
| 770 |
+
<confidence value="58">HC</confidence>
|
| 771 |
+
<confidence value="55">NF</confidence>
|
| 772 |
+
<confidence value="28">ZN</confidence>
|
| 773 |
+
<confidence value="1">O</confidence>
|
| 774 |
+
<confidence value="2">/</confidence>
|
| 775 |
+
H3 <confidence value="1">1</confidence>
|
| 776 |
+
<confidence value="66">OH</confidence>
|
| 777 |
+
<confidence value="8858668668">I-CA-MPD12</confidence>
|
| 778 |
+
<confidence value="22">H3</confidence>
|
| 779 |
+
<confidence value="2">M</confidence>
|
| 780 |
+
<part-num-ref name="OH I-CA-MPD12 H3 M">
|
| 781 |
+
<confidence value="2">0</confidence>
|
| 782 |
+
</part-num-ref>
|
| 783 |
+
</p>
|
| 784 |
+
<heading id="h-15">
|
| 785 |
+
<confidence value="526">HMC</confidence>
|
| 786 |
+
<confidence value="6">H</confidence>
|
| 787 |
+
</heading>
|
| 788 |
+
<p id="p-29" num="29">
|
| 789 |
+
<confidence value="588">H3C</confidence>
|
| 790 |
+
<confidence value="5">N</confidence>
|
| 791 |
+
<confidence value="211">0Sc</confidence>
|
| 792 |
+
<confidence value="8">O</confidence>
|
| 793 |
+
<confidence value="8">O</confidence>
|
| 794 |
+
<confidence value="6">H</confidence>
|
| 795 |
+
<confidence value="8">O</confidence>
|
| 796 |
+
M = H <confidence value="88">or</confidence>
|
| 797 |
+
<confidence value="8">a</confidence>
|
| 798 |
+
metal <confidence value="588">ion</confidence>
|
| 799 |
+
<confidence value="5">I</confidence>
|
| 800 |
+
-CA-<confidence value="66845">MPDI3</confidence>
|
| 801 |
+
I-CA-MPD14 </p>
|
| 802 |
+
<heading id="h-16">
|
| 803 |
+
<confidence value="1">!</confidence>
|
| 804 |
+
<confidence value="8">H</confidence>
|
| 805 |
+
<confidence value="7">O</confidence>
|
| 806 |
+
</heading>
|
| 807 |
+
<p id="p-30" num="30">
|
| 808 |
+
<confidence value="666">H3C</confidence>
|
| 809 |
+
<confidence value="25">0H</confidence>
|
| 810 |
+
<confidence value="1">t</confidence>
|
| 811 |
+
<confidence value="28">NO</confidence>
|
| 812 |
+
<confidence value="2">I</confidence>
|
| 813 |
+
<confidence value="117">ACN</confidence>
|
| 814 |
+
<confidence value="2">N</confidence>
|
| 815 |
+
<confidence value="15666666662">sI-CA-MPD18</confidence>
|
| 816 |
+
<confidence value="5">O</confidence>
|
| 817 |
+
<confidence value="5">O</confidence>
|
| 818 |
+
I-CA-MPD<confidence value="48">17</confidence>
|
| 819 |
+
<confidence value="5">O</confidence>
|
| 820 |
+
<confidence value="52">H0</confidence>
|
| 821 |
+
<confidence value="25">NN</confidence>
|
| 822 |
+
<confidence value="44">NO</confidence>
|
| 823 |
+
<confidence value="21">NO</confidence>
|
| 824 |
+
<confidence value="14">SS</confidence>
|
| 825 |
+
<confidence value="1">0</confidence>
|
| 826 |
+
<confidence value="661">CHa</confidence>
|
| 827 |
+
<confidence value="5666666521">I-CA-MPD2-</confidence>
|
| 828 |
+
<confidence value="555">OH3</confidence>
|
| 829 |
+
</p>
|
| 830 |
+
<heading id="h-17">
|
| 831 |
+
<confidence value="11">CC</confidence>
|
| 832 |
+
</heading>
|
| 833 |
+
<p id="p-31" num="31">
|
| 834 |
+
<confidence value="2">0</confidence>
|
| 835 |
+
<confidence value="5256">E02C</confidence>
|
| 836 |
+
I-CA-<confidence value="56688">MPD22</confidence>
|
| 837 |
+
<boundary-data type="header">
|
| 838 |
+
<confidence value="5">8</confidence>
|
| 839 |
+
of <confidence value="88">39</confidence>
|
| 840 |
+
</boundary-data>
|
| 841 |
+
<boundary-data type="header">PAGE <confidence value="884888">10141'</confidence>
|
| 842 |
+
RCVD <confidence value="88">AT</confidence>
|
| 843 |
+
<confidence value="68685">12141</confidence>
|
| 844 |
+
200512:40:00 <confidence value="88">PM</confidence>
|
| 845 |
+
<confidence value="5">[</confidence>
|
| 846 |
+
Easte<confidence value="66">rn</confidence>
|
| 847 |
+
Standard Time<confidence value="248866">]'SVR:</confidence>
|
| 848 |
+
USPT<confidence value="514">O-E</confidence>
|
| 849 |
+
FXRF<confidence value="55885">4132'</confidence>
|
| 850 |
+
DNIS:2<confidence value="4">7</confidence>
|
| 851 |
+
38300<confidence value="4">'</confidence>
|
| 852 |
+
CSID:847 <confidence value="688">770</confidence>
|
| 853 |
+
600<confidence value="55">6'</confidence>
|
| 854 |
+
DURATI<confidence value="68">ON</confidence>
|
| 855 |
+
(mm<confidence value="5">s</confidence>
|
| 856 |
+
s):09<confidence value="288">-34</confidence>
|
| 857 |
+
</boundary-data>
|
| 858 |
+
<page-break num="8"/>
|
| 859 |
+
<boundary-data type="header">DEC-14-2005 11:48 FROM ROSENBAUM <confidence value="5">&</confidence>
|
| 860 |
+
ASSOCI<confidence value="8">A</confidence>
|
| 861 |
+
TES TO 1571273<confidence value="4">8</confidence>
|
| 862 |
+
300 P.11 </boundary-data>
|
| 863 |
+
<boundary-data type="header">App<confidence value="7">l</confidence>
|
| 864 |
+
e. No<confidence value="666">.11</confidence>
|
| 865 |
+
/213<confidence value="5">.</confidence>
|
| 866 |
+
396 </boundary-data>
|
| 867 |
+
<boundary-data type="header">Amdt. Dated D<confidence value="5">e</confidence>
|
| 868 |
+
c. 13, 2005 </boundary-data>
|
| 869 |
+
Clean replacement page 33: </p>
|
| 870 |
+
<p id="p-32" num="32">(a) From carboxyl-containing drugs:</p>
|
| 871 |
+
<p id="p-33" num="33">
|
| 872 |
+
<confidence value="2526">HC00</confidence>
|
| 873 |
+
<confidence value="4">o</confidence>
|
| 874 |
+
<confidence value="224">oHc</confidence>
|
| 875 |
+
<confidence value="4">o</confidence>
|
| 876 |
+
<confidence value="4">o</confidence>
|
| 877 |
+
<confidence value="8582">H3CO</confidence>
|
| 878 |
+
<confidence value="4">o</confidence>
|
| 879 |
+
<confidence value="2411">-'Kr</confidence>
|
| 880 |
+
<confidence value="4">S</confidence>
|
| 881 |
+
<confidence value="66">OH</confidence>
|
| 882 |
+
<confidence value="221">oWN</confidence>
|
| 883 |
+
<confidence value="41">S.</confidence>
|
| 884 |
+
<confidence value="88">OH</confidence>
|
| 885 |
+
<confidence value="11665">SANH2</confidence>
|
| 886 |
+
I-C<confidence value="2">1</confidence>
|
| 887 |
+
-PD<confidence value="4">1</confidence>
|
| 888 |
+
I-C<confidence value="2">l</confidence>
|
| 889 |
+
-PD<confidence value="6">2</confidence>
|
| 890 |
+
<confidence value="68658665">I-C1-PD3</confidence>
|
| 891 |
+
<confidence value="21226">Hec-o</confidence>
|
| 892 |
+
<confidence value="2">0</confidence>
|
| 893 |
+
<part-num-ref name="">
|
| 894 |
+
<confidence value="2">0</confidence>
|
| 895 |
+
</part-num-ref>
|
| 896 |
+
<confidence value="55">HC</confidence>
|
| 897 |
+
<part-num-ref name="HC">
|
| 898 |
+
<confidence value="2">0</confidence>
|
| 899 |
+
</part-num-ref>
|
| 900 |
+
<confidence value="4">o</confidence>
|
| 901 |
+
<confidence value="21">N,</confidence>
|
| 902 |
+
<confidence value="2">H</confidence>
|
| 903 |
+
<confidence value="22">k.</confidence>
|
| 904 |
+
<confidence value="4111">s'-i</confidence>
|
| 905 |
+
O CH<confidence value="1">3</confidence>
|
| 906 |
+
<confidence value="2">N</confidence>
|
| 907 |
+
<confidence value="1">I</confidence>
|
| 908 |
+
<confidence value="6">O</confidence>
|
| 909 |
+
<confidence value="11">-P</confidence>
|
| 910 |
+
<confidence value="6111">Sg^,</confidence>
|
| 911 |
+
O CH<confidence value="1">3</confidence>
|
| 912 |
+
<confidence value="6">o</confidence>
|
| 913 |
+
<confidence value="2">H</confidence>
|
| 914 |
+
<confidence value="882661">-C-D4a</confidence>
|
| 915 |
+
<confidence value="5652">I-Cl</confidence>
|
| 916 |
+
-PD4<confidence value="8">b</confidence>
|
| 917 |
+
<confidence value="22">M+</confidence>
|
| 918 |
+
a metal ion <confidence value="52">Co</confidence>
|
| 919 |
+
<confidence value="6">o</confidence>
|
| 920 |
+
<confidence value="8414">H3tA</confidence>
|
| 921 |
+
<confidence value="41">OO</confidence>
|
| 922 |
+
<confidence value="6">o</confidence>
|
| 923 |
+
<confidence value="6848865">-Cl-PD5</confidence>
|
| 924 |
+
<confidence value="2">o</confidence>
|
| 925 |
+
I-C<confidence value="4">1</confidence>
|
| 926 |
+
-PD6 <confidence value="1414">3CAO</confidence>
|
| 927 |
+
<confidence value="44">CI</confidence>
|
| 928 |
+
<confidence value="666651">I-C-PD</confidence>
|
| 929 |
+
<confidence value="52">O0</confidence>
|
| 930 |
+
I-C<confidence value="28688">I-PD7</confidence>
|
| 931 |
+
<confidence value="11111">NICH3</confidence>
|
| 932 |
+
<part-num-ref name="metal ion Co o H3tA OO o -Cl-PD5 oI-C1-PD6 3CAO CI I-C-PD O0 I-CI-PD7 NICH3">
|
| 933 |
+
<confidence value="2">0</confidence>
|
| 934 |
+
</part-num-ref>
|
| 935 |
+
<confidence value="211">0.N</confidence>
|
| 936 |
+
<part-num-ref name="0.N">
|
| 937 |
+
<confidence value="1">0</confidence>
|
| 938 |
+
</part-num-ref>
|
| 939 |
+
<confidence value="1211">0/\i</confidence>
|
| 940 |
+
<confidence value="1">'</confidence>
|
| 941 |
+
<part-num-ref name="0/\i '">
|
| 942 |
+
<confidence value="6">0</confidence>
|
| 943 |
+
</part-num-ref>
|
| 944 |
+
<part-num-ref name="">
|
| 945 |
+
<confidence value="2">0</confidence>
|
| 946 |
+
</part-num-ref>
|
| 947 |
+
<confidence value="8865886">I-C1-P9</confidence>
|
| 948 |
+
<confidence value="688185865">I-CJ-PD10</confidence>
|
| 949 |
+
<confidence value="714">HaC</confidence>
|
| 950 |
+
<confidence value="1">O</confidence>
|
| 951 |
+
<confidence value="421">S-S</confidence>
|
| 952 |
+
<confidence value="48">oH</confidence>
|
| 953 |
+
<confidence value="2">H</confidence>
|
| 954 |
+
<confidence value="8">C</confidence>
|
| 955 |
+
<confidence value="222">NHO</confidence>
|
| 956 |
+
<confidence value="5665666556666665">I-C1-PD11I-C-PD2</confidence>
|
| 957 |
+
<part-num-ref name="I-C1-P9 I-CJ-PD10 HaC O S-S oH H C NHO I-C1-PD11I-C-PD2">
|
| 958 |
+
<confidence value="2">0</confidence>
|
| 959 |
+
</part-num-ref>
|
| 960 |
+
<part-num-ref name="">
|
| 961 |
+
<confidence value="2">0</confidence>
|
| 962 |
+
</part-num-ref>
|
| 963 |
+
I-C<confidence value="5">l</confidence>
|
| 964 |
+
-PD13 <confidence value="11">iK</confidence>
|
| 965 |
+
<confidence value="1">Y</confidence>
|
| 966 |
+
<confidence value="41">o0</confidence>
|
| 967 |
+
<confidence value="1">/</confidence>
|
| 968 |
+
<confidence value="5">s</confidence>
|
| 969 |
+
<confidence value="1121">OxYo</confidence>
|
| 970 |
+
<confidence value="2">N</confidence>
|
| 971 |
+
<confidence value="881">CH3</confidence>
|
| 972 |
+
<confidence value="812">H3C</confidence>
|
| 973 |
+
<confidence value="14">0S</confidence>
|
| 974 |
+
<confidence value="661">CHa</confidence>
|
| 975 |
+
<part-num-ref name="I-Cl-PD13 iK Y o0 / s OxYo N CH3 H3C 0S CHa">
|
| 976 |
+
<confidence value="2">0</confidence>
|
| 977 |
+
</part-num-ref>
|
| 978 |
+
H <part-num-ref name="H">
|
| 979 |
+
<confidence value="2">0</confidence>
|
| 980 |
+
</part-num-ref>
|
| 981 |
+
<confidence value="8">H</confidence>
|
| 982 |
+
<confidence value="5884">I-C1</confidence>
|
| 983 |
+
-PD<confidence value="4">1</confidence>
|
| 984 |
+
4 I-C<confidence value="2">l</confidence>
|
| 985 |
+
-PD1<confidence value="68">5a</confidence>
|
| 986 |
+
<confidence value="718">H3C</confidence>
|
| 987 |
+
<confidence value="11611">N/S"S</confidence>
|
| 988 |
+
<confidence value="1">O</confidence>
|
| 989 |
+
<confidence value="1">N</confidence>
|
| 990 |
+
<confidence value="1">H</confidence>
|
| 991 |
+
<confidence value="2">o</confidence>
|
| 992 |
+
<confidence value="885">Na'</confidence>
|
| 993 |
+
I-C<confidence value="5">l</confidence>
|
| 994 |
+
-PD<confidence value="668">15b</confidence>
|
| 995 |
+
<boundary-data type="header">9 of 39</boundary-data>
|
| 996 |
+
<boundary-data type="header">PAGE <confidence value="885888886888">11141'RCVDAT</confidence>
|
| 997 |
+
<confidence value="885585">121141</confidence>
|
| 998 |
+
200512:40:<confidence value="6688">00PM</confidence>
|
| 999 |
+
[Easte<confidence value="66">rn</confidence>
|
| 1000 |
+
Standard <confidence value="86856">Tiel'</confidence>
|
| 1001 |
+
<confidence value="8668888248885142">SR:USPTO4FXRFI32</confidence>
|
| 1002 |
+
<confidence value="5688885">DNIS:27</confidence>
|
| 1003 |
+
383<confidence value="664">00'</confidence>
|
| 1004 |
+
CSID:<confidence value="68868">84770</confidence>
|
| 1005 |
+
6006<confidence value="5">'</confidence>
|
| 1006 |
+
DURAT<confidence value="668">ION</confidence>
|
| 1007 |
+
<confidence value="8824">(mms</confidence>
|
| 1008 |
+
s):<confidence value="58288">09-34</confidence>
|
| 1009 |
+
</boundary-data>
|
| 1010 |
+
<page-break num="9"/>
|
| 1011 |
+
<boundary-data type="header">DEC-14-2005 11<confidence value="5">:</confidence>
|
| 1012 |
+
48 FROM ROSENB<confidence value="8">A</confidence>
|
| 1013 |
+
UM & ASSOCIATES TO 15712738300 P.<confidence value="88">12</confidence>
|
| 1014 |
+
</boundary-data>
|
| 1015 |
+
<boundary-data type="header">App<confidence value="7">l</confidence>
|
| 1016 |
+
e. No.11/213.396 </boundary-data>
|
| 1017 |
+
<boundary-data type="header">Amdt. Dated Dec. 13, 2005</boundary-data>
|
| 1018 |
+
Clean replacement page 37: </p>
|
| 1019 |
+
<p id="p-34" num="34">
|
| 1020 |
+
<confidence value="86">NO</confidence>
|
| 1021 |
+
2 NO<confidence value="6">2</confidence>
|
| 1022 |
+
<confidence value="5">O</confidence>
|
| 1023 |
+
<confidence value="685">CH3</confidence>
|
| 1024 |
+
<confidence value="2">O</confidence>
|
| 1025 |
+
<confidence value="2">0</confidence>
|
| 1026 |
+
<confidence value="7">O</confidence>
|
| 1027 |
+
<confidence value="2">R</confidence>
|
| 1028 |
+
<confidence value="2">C</confidence>
|
| 1029 |
+
I-H<confidence value="25885">1-PD1</confidence>
|
| 1030 |
+
<confidence value="452">CH3</confidence>
|
| 1031 |
+
<confidence value="5">-</confidence>
|
| 1032 |
+
<confidence value="241">CH3</confidence>
|
| 1033 |
+
</p>
|
| 1034 |
+
<heading id="h-18">
|
| 1035 |
+
<confidence value="2212">NNPC</confidence>
|
| 1036 |
+
</heading>
|
| 1037 |
+
<p id="p-35" num="35">
|
| 1038 |
+
<confidence value="6">N</confidence>
|
| 1039 |
+
<confidence value="871">CHg</confidence>
|
| 1040 |
+
<confidence value="81">Nf</confidence>
|
| 1041 |
+
H3 I<confidence value="72">HI</confidence>
|
| 1042 |
+
-PD3 C<confidence value="111">~ta</confidence>
|
| 1043 |
+
</p>
|
| 1044 |
+
<heading id="h-19">
|
| 1045 |
+
<confidence value="2">N</confidence>
|
| 1046 |
+
O <confidence value="72">NA</confidence>
|
| 1047 |
+
<confidence value="7">S</confidence>
|
| 1048 |
+
<confidence value="21">NO</confidence>
|
| 1049 |
+
<confidence value="16">RC</confidence>
|
| 1050 |
+
</heading>
|
| 1051 |
+
<p id="p-36" num="36">
|
| 1052 |
+
<confidence value="14727821">1I-H1-P'</confidence>
|
| 1053 |
+
D4 R <confidence value="2">=</confidence>
|
| 1054 |
+
H, lower alkyl, etc<confidence value="2">.</confidence>
|
| 1055 |
+
</p>
|
| 1056 |
+
<p id="p-37" num="37">
|
| 1057 |
+
<confidence value="662">HNa</confidence>
|
| 1058 |
+
<confidence value="1">R</confidence>
|
| 1059 |
+
</p>
|
| 1060 |
+
<heading id="h-20">
|
| 1061 |
+
<confidence value="1">-</confidence>
|
| 1062 |
+
<confidence value="11">N.</confidence>
|
| 1063 |
+
</heading>
|
| 1064 |
+
<heading id="h-21">
|
| 1065 |
+
<confidence value="6">O</confidence>
|
| 1066 |
+
<confidence value="7">N</confidence>
|
| 1067 |
+
<confidence value="1">O</confidence>
|
| 1068 |
+
<confidence value="1">'</confidence>
|
| 1069 |
+
<confidence value="1">O</confidence>
|
| 1070 |
+
N O <confidence value="21">R-</confidence>
|
| 1071 |
+
</heading>
|
| 1072 |
+
<p id="p-38" num="38">
|
| 1073 |
+
<confidence value="14">OH</confidence>
|
| 1074 |
+
<confidence value="4">r</confidence>
|
| 1075 |
+
<confidence value="111141242">alkySleOH</confidence>
|
| 1076 |
+
<confidence value="5">N</confidence>
|
| 1077 |
+
<confidence value="82">Na</confidence>
|
| 1078 |
+
<confidence value="56845865">I-HI-PD5</confidence>
|
| 1079 |
+
NH2 <confidence value="52">N3</confidence>
|
| 1080 |
+
<confidence value="88448844">I-HI-PD6</confidence>
|
| 1081 |
+
<confidence value="7">O</confidence>
|
| 1082 |
+
<confidence value="2">N</confidence>
|
| 1083 |
+
<confidence value="2">N</confidence>
|
| 1084 |
+
O R <confidence value="1">,</confidence>
|
| 1085 |
+
<confidence value="1">y</confidence>
|
| 1086 |
+
<confidence value="1">^</confidence>
|
| 1087 |
+
<confidence value="1122">SSHa</confidence>
|
| 1088 |
+
<confidence value="58868486">I-HI-pD7</confidence>
|
| 1089 |
+
I-<confidence value="528852">H1-PD3</confidence>
|
| 1090 |
+
<confidence value="2">H</confidence>
|
| 1091 |
+
<confidence value="855">CH3</confidence>
|
| 1092 |
+
<confidence value="1">I</confidence>
|
| 1093 |
+
<confidence value="188">JNH</confidence>
|
| 1094 |
+
<confidence value="2">H</confidence>
|
| 1095 |
+
-- <confidence value="28">0-</confidence>
|
| 1096 |
+
<confidence value="2">_</confidence>
|
| 1097 |
+
<confidence value="11">r-</confidence>
|
| 1098 |
+
<confidence value="11">t.</confidence>
|
| 1099 |
+
<confidence value="7">O</confidence>
|
| 1100 |
+
<confidence value="122">ONN</confidence>
|
| 1101 |
+
</p>
|
| 1102 |
+
<heading id="h-22">
|
| 1103 |
+
<confidence value="2">O</confidence>
|
| 1104 |
+
<confidence value="66">HN</confidence>
|
| 1105 |
+
</heading>
|
| 1106 |
+
<p id="p-39" num="39">I-H<confidence value="4771162122">I-P0p9HjS$</confidence>
|
| 1107 |
+
<confidence value="6">H</confidence>
|
| 1108 |
+
<confidence value="2">a</confidence>
|
| 1109 |
+
<confidence value="11212">S-O-R</confidence>
|
| 1110 |
+
<confidence value="6">H</confidence>
|
| 1111 |
+
<confidence value="11">0s</confidence>
|
| 1112 |
+
I H1 -PD10<confidence value="2">0</confidence>
|
| 1113 |
+
<confidence value="2">O</confidence>
|
| 1114 |
+
I-H<confidence value="4">I</confidence>
|
| 1115 |
+
-PD<confidence value="55">11</confidence>
|
| 1116 |
+
<confidence value="7">O</confidence>
|
| 1117 |
+
<confidence value="22">CI</confidence>
|
| 1118 |
+
<confidence value="2">N</confidence>
|
| 1119 |
+
<confidence value="2">H</confidence>
|
| 1120 |
+
<confidence value="771">3C,</confidence>
|
| 1121 |
+
CH<confidence value="2">3</confidence>
|
| 1122 |
+
<confidence value="155">H2N</confidence>
|
| 1123 |
+
<confidence value="6">N</confidence>
|
| 1124 |
+
<confidence value="1">C</confidence>
|
| 1125 |
+
I-H<confidence value="4">1</confidence>
|
| 1126 |
+
-PD1<confidence value="5">2</confidence>
|
| 1127 |
+
<confidence value="122222212">I-H1-PD23</confidence>
|
| 1128 |
+
<confidence value="1">a</confidence>
|
| 1129 |
+
<confidence value="1251">CC2H</confidence>
|
| 1130 |
+
NHCH<confidence value="551411">(R400t</confidence>
|
| 1131 |
+
<confidence value="8615">(Ry2</confidence>
|
| 1132 |
+
<confidence value="566868666">side-chai</confidence>
|
| 1133 |
+
n groups <confidence value="77661611">I-I-FDIS</confidence>
|
| 1134 |
+
<confidence value="1661">Carb</confidence>
|
| 1135 |
+
o a<confidence value="66">dd</confidence>
|
| 1136 |
+
s) or any group or molecule <confidence value="2222222">coairng</confidence>
|
| 1137 |
+
water- <confidence value="526">NO2</confidence>
|
| 1138 |
+
<confidence value="6">H</confidence>
|
| 1139 |
+
<confidence value="222222222222">solubilizing</confidence>
|
| 1140 |
+
groups such as hydroxyl<confidence value="4">,</confidence>
|
| 1141 |
+
a<confidence value="8">m</confidence>
|
| 1142 |
+
ino, and <confidence value="222222228">carboxyl.</confidence>
|
| 1143 |
+
</p>
|
| 1144 |
+
<p id="p-40" num="40">
|
| 1145 |
+
<confidence value="51">N^</confidence>
|
| 1146 |
+
<confidence value="1">O</confidence>
|
| 1147 |
+
<confidence value="5">N</confidence>
|
| 1148 |
+
<confidence value="2">S</confidence>
|
| 1149 |
+
<confidence value="56">OH</confidence>
|
| 1150 |
+
phospha<confidence value="8">t</confidence>
|
| 1151 |
+
e<confidence value="6">,</confidence>
|
| 1152 |
+
sulfate, etc<confidence value="5">.</confidence>
|
| 1153 |
+
</p>
|
| 1154 |
+
<p id="p-41" num="41">
|
| 1155 |
+
<confidence value="5">(</confidence>
|
| 1156 |
+
a) I-<confidence value="4">H</confidence>
|
| 1157 |
+
1-PD14 <boundary-data type="header">
|
| 1158 |
+
<confidence value="88">10</confidence>
|
| 1159 |
+
<confidence value="6888">of39</confidence>
|
| 1160 |
+
</boundary-data>
|
| 1161 |
+
<boundary-data type="header">PAGE <confidence value="881885">12/41'</confidence>
|
| 1162 |
+
RCVD AT <confidence value="662885">121141</confidence>
|
| 1163 |
+
2005 <confidence value="5">1</confidence>
|
| 1164 |
+
2:40:00 PM [Easte<confidence value="66">rn</confidence>
|
| 1165 |
+
Standard T<confidence value="5885">ime]</confidence>
|
| 1166 |
+
<confidence value="8866">SVR:</confidence>
|
| 1167 |
+
USPT<confidence value="55">OE</confidence>
|
| 1168 |
+
FXRF<confidence value="2">.</confidence>
|
| 1169 |
+
6132<confidence value="2">*</confidence>
|
| 1170 |
+
<confidence value="1">D</confidence>
|
| 1171 |
+
NIS:2<confidence value="5">7</confidence>
|
| 1172 |
+
38300' CSID:<confidence value="68288">84?77</confidence>
|
| 1173 |
+
0 6006' DURA<confidence value="6668">TION</confidence>
|
| 1174 |
+
<confidence value="8852">(mm-</confidence>
|
| 1175 |
+
ss):09<confidence value="288">-34</confidence>
|
| 1176 |
+
</boundary-data>
|
| 1177 |
+
<page-break num="10"/>
|
| 1178 |
+
<boundary-data type="header">DEC-14-2005 11:49 FROM ROSENBAUM <confidence value="6">&</confidence>
|
| 1179 |
+
ASSOCI<confidence value="8">A</confidence>
|
| 1180 |
+
TES TO 1571273<confidence value="4">8</confidence>
|
| 1181 |
+
300 P<confidence value="888">.13</confidence>
|
| 1182 |
+
</boundary-data>
|
| 1183 |
+
<boundary-data type="header">App<confidence value="1">I</confidence>
|
| 1184 |
+
. No.11/213.396 </boundary-data>
|
| 1185 |
+
<boundary-data type="header">Amdt. Dated Dec. 13, 2005</boundary-data>
|
| 1186 |
+
Clean replacement page 41: </p>
|
| 1187 |
+
<p id="p-42" num="42">(b) From amino-containing drugs 0 <part-num-ref name="">0</part-num-ref>
|
| 1188 |
+
<confidence value="88488">EtO2C</confidence>
|
| 1189 |
+
<confidence value="4">S</confidence>
|
| 1190 |
+
<confidence value="5">N</confidence>
|
| 1191 |
+
<confidence value="6556">HO2C</confidence>
|
| 1192 |
+
<confidence value="1">)</confidence>
|
| 1193 |
+
<confidence value="2525">SNO2</confidence>
|
| 1194 |
+
<confidence value="4">c</confidence>
|
| 1195 |
+
<confidence value="1884885884">I-A1-NOPDI</confidence>
|
| 1196 |
+
<confidence value="66">CI</confidence>
|
| 1197 |
+
I-A<confidence value="4">1</confidence>
|
| 1198 |
+
-NOPD2 <confidence value="11111">CIc/c</confidence>
|
| 1199 |
+
<confidence value="2112">OANC</confidence>
|
| 1200 |
+
<part-num-ref name="EtO2C S N HO2C ) SNO2 c I-A1-NOPDI CI I-A1-NOPD2 CIc/c OANC">
|
| 1201 |
+
<confidence value="2">0</confidence>
|
| 1202 |
+
</part-num-ref>
|
| 1203 |
+
<confidence value="2">N</confidence>
|
| 1204 |
+
<confidence value="2222222">O$nd/or</confidence>
|
| 1205 |
+
N<confidence value="2">N</confidence>
|
| 1206 |
+
H2N N NH H2N <confidence value="6">N</confidence>
|
| 1207 |
+
<confidence value="4">S</confidence>
|
| 1208 |
+
<confidence value="651">NO2</confidence>
|
| 1209 |
+
<confidence value="1882">[-A1</confidence>
|
| 1210 |
+
-NOP<confidence value="658">D3A</confidence>
|
| 1211 |
+
<confidence value="6">H</confidence>
|
| 1212 |
+
I-A<confidence value="4">1</confidence>
|
| 1213 |
+
-NO<confidence value="4228">PD3B</confidence>
|
| 1214 |
+
</p>
|
| 1215 |
+
<heading id="h-23">
|
| 1216 |
+
<confidence value="22">HN</confidence>
|
| 1217 |
+
<confidence value="2">O</confidence>
|
| 1218 |
+
</heading>
|
| 1219 |
+
<p id="p-43" num="43">Me <confidence value="585">OMe</confidence>
|
| 1220 |
+
<confidence value="8685">I-Al</confidence>
|
| 1221 |
+
-NOPD4 H O C<confidence value="2">O</confidence>
|
| 1222 |
+
2H Me<confidence value="1">O</confidence>
|
| 1223 |
+
<confidence value="8">N</confidence>
|
| 1224 |
+
<confidence value="2">M</confidence>
|
| 1225 |
+
I-A<confidence value="2">l</confidence>
|
| 1226 |
+
-NOP<confidence value="58">OS</confidence>
|
| 1227 |
+
<confidence value="1222">O-NO</confidence>
|
| 1228 |
+
<confidence value="2526">HNO2</confidence>
|
| 1229 |
+
I-A<confidence value="5">1</confidence>
|
| 1230 |
+
-NOPD<confidence value="5">6</confidence>
|
| 1231 |
+
<confidence value="211">HaC</confidence>
|
| 1232 |
+
<confidence value="2">N</confidence>
|
| 1233 |
+
<confidence value="2">N</confidence>
|
| 1234 |
+
O S <confidence value="122">ON2</confidence>
|
| 1235 |
+
<confidence value="6">N</confidence>
|
| 1236 |
+
I-A<confidence value="4">l</confidence>
|
| 1237 |
+
-NOPD7 M<confidence value="2454">eO2C</confidence>
|
| 1238 |
+
<confidence value="85565">CO2Et</confidence>
|
| 1239 |
+
<confidence value="85">Cl</confidence>
|
| 1240 |
+
<confidence value="2">0</confidence>
|
| 1241 |
+
<confidence value="2188">I)-A</confidence>
|
| 1242 |
+
-NOPD<confidence value="2">O</confidence>
|
| 1243 |
+
<confidence value="58">HN</confidence>
|
| 1244 |
+
<confidence value="4882">SNO2</confidence>
|
| 1245 |
+
<confidence value="625">N0O</confidence>
|
| 1246 |
+
<confidence value="666">NO2</confidence>
|
| 1247 |
+
</p>
|
| 1248 |
+
<heading id="h-24">
|
| 1249 |
+
<confidence value="7">N</confidence>
|
| 1250 |
+
<confidence value="22">NH</confidence>
|
| 1251 |
+
</heading>
|
| 1252 |
+
<p id="p-44" num="44">
|
| 1253 |
+
<confidence value="52">HO</confidence>
|
| 1254 |
+
<confidence value="26">OH</confidence>
|
| 1255 |
+
<confidence value="5665666666">I-A1-NOPD9</confidence>
|
| 1256 |
+
<confidence value="625">FNN</confidence>
|
| 1257 |
+
<confidence value="2">N</confidence>
|
| 1258 |
+
<confidence value="51">H1</confidence>
|
| 1259 |
+
<confidence value="2">H</confidence>
|
| 1260 |
+
<confidence value="2">H</confidence>
|
| 1261 |
+
<confidence value="1">0</confidence>
|
| 1262 |
+
<confidence value="5">N</confidence>
|
| 1263 |
+
<confidence value="152">yNH</confidence>
|
| 1264 |
+
<confidence value="1">O</confidence>
|
| 1265 |
+
<confidence value="5662">I-Al</confidence>
|
| 1266 |
+
<confidence value="6652224">-NOD10a</confidence>
|
| 1267 |
+
<confidence value="22">F2</confidence>
|
| 1268 |
+
<confidence value="1">S</confidence>
|
| 1269 |
+
<confidence value="266266514225">H-A1-NOPD10b</confidence>
|
| 1270 |
+
<confidence value="251">CH8</confidence>
|
| 1271 |
+
<confidence value="5">H</confidence>
|
| 1272 |
+
</p>
|
| 1273 |
+
<heading id="h-25">
|
| 1274 |
+
<confidence value="2">O</confidence>
|
| 1275 |
+
O <confidence value="2">N</confidence>
|
| 1276 |
+
O O<confidence value="2">H</confidence>
|
| 1277 |
+
</heading>
|
| 1278 |
+
<p id="p-45" num="45">
|
| 1279 |
+
<confidence value="56666665615">I-A2-NOPD~a</confidence>
|
| 1280 |
+
<confidence value="8886888882">I-A2-NOPDI</confidence>
|
| 1281 |
+
<confidence value="5">b</confidence>
|
| 1282 |
+
<confidence value="722">020</confidence>
|
| 1283 |
+
</p>
|
| 1284 |
+
<heading id="h-26">O O O O</heading>
|
| 1285 |
+
<p id="p-46" num="46">
|
| 1286 |
+
<confidence value="2">N</confidence>
|
| 1287 |
+
<confidence value="7">O</confidence>
|
| 1288 |
+
<confidence value="1212">SN2N</confidence>
|
| 1289 |
+
<confidence value="26">NO</confidence>
|
| 1290 |
+
<confidence value="22">N2</confidence>
|
| 1291 |
+
I-A2-NOPD<confidence value="48">Za</confidence>
|
| 1292 |
+
I-A<confidence value="5">2</confidence>
|
| 1293 |
+
-NOPD2b <boundary-data type="header">11 of <confidence value="88">39</confidence>
|
| 1294 |
+
</boundary-data>
|
| 1295 |
+
<boundary-data type="header">PAGE <confidence value="88885">1341'</confidence>
|
| 1296 |
+
<confidence value="8858">RCVD</confidence>
|
| 1297 |
+
<confidence value="88">AT</confidence>
|
| 1298 |
+
<confidence value="66885">12141</confidence>
|
| 1299 |
+
200512:40:<confidence value="66">00</confidence>
|
| 1300 |
+
<confidence value="88">PM</confidence>
|
| 1301 |
+
[Easte<confidence value="5">m</confidence>
|
| 1302 |
+
Standard <confidence value="886821">Timejt</confidence>
|
| 1303 |
+
<confidence value="8866">SVR:</confidence>
|
| 1304 |
+
USPT<confidence value="55">O-</confidence>
|
| 1305 |
+
EFXRF<confidence value="5">-</confidence>
|
| 1306 |
+
613<confidence value="5">2</confidence>
|
| 1307 |
+
DNIS:2738300<confidence value="4">'</confidence>
|
| 1308 |
+
CSID:847 770<confidence value="88682">60062</confidence>
|
| 1309 |
+
DURATI<confidence value="68">ON</confidence>
|
| 1310 |
+
<confidence value="8852">(mm-</confidence>
|
| 1311 |
+
ss):09<confidence value="588">.34</confidence>
|
| 1312 |
+
</boundary-data>
|
| 1313 |
+
<page-break num="11"/>
|
| 1314 |
+
<boundary-data type="header">DEC-14-2005 11<confidence value="5">:</confidence>
|
| 1315 |
+
49 FROM ROSENBAUM & <confidence value="8">A</confidence>
|
| 1316 |
+
SSOCI<confidence value="8">A</confidence>
|
| 1317 |
+
TES TO 15712738300 P.<confidence value="88">14</confidence>
|
| 1318 |
+
</boundary-data>
|
| 1319 |
+
<boundary-data type="header">App<confidence value="675">le.</confidence>
|
| 1320 |
+
No<confidence value="25">.1</confidence>
|
| 1321 |
+
1/213<confidence value="5">.</confidence>
|
| 1322 |
+
396 </boundary-data>
|
| 1323 |
+
<boundary-data type="header">
|
| 1324 |
+
<confidence value="2222">Amdt</confidence>
|
| 1325 |
+
. Dated Dec. 13, 2005 </boundary-data>
|
| 1326 |
+
Clean replacement page 52: </p>
|
| 1327 |
+
<p id="p-47" num="47">
|
| 1328 |
+
<confidence value="66">NH</confidence>
|
| 1329 |
+
<confidence value="1">o</confidence>
|
| 1330 |
+
<confidence value="1">o</confidence>
|
| 1331 |
+
<confidence value="1">O</confidence>
|
| 1332 |
+
<confidence value="2">H</confidence>
|
| 1333 |
+
<confidence value="5">s</confidence>
|
| 1334 |
+
<confidence value="5488">C02H</confidence>
|
| 1335 |
+
<confidence value="771">Ph_</confidence>
|
| 1336 |
+
<confidence value="7218">N1H2</confidence>
|
| 1337 |
+
<confidence value="2121">NE'l</confidence>
|
| 1338 |
+
<confidence value="2">1</confidence>
|
| 1339 |
+
<part-num-ref name="">
|
| 1340 |
+
<confidence value="1">1</confidence>
|
| 1341 |
+
</part-num-ref>
|
| 1342 |
+
O O <confidence value="22">HN</confidence>
|
| 1343 |
+
<confidence value="1">N</confidence>
|
| 1344 |
+
<confidence value="82">Nq</confidence>
|
| 1345 |
+
<confidence value="2222222222222">Sultamacillin</confidence>
|
| 1346 |
+
<confidence value="22">N4</confidence>
|
| 1347 |
+
<confidence value="1">O</confidence>
|
| 1348 |
+
<confidence value="41">CN</confidence>
|
| 1349 |
+
Ph <confidence value="4">I</confidence>
|
| 1350 |
+
-CA-MPD1<confidence value="2">O</confidence>
|
| 1351 |
+
<part-num-ref name="O O HN N Nq Sultamacillin N4 O CN Ph I-CA-MPD1O">
|
| 1352 |
+
<confidence value="8">0</confidence>
|
| 1353 |
+
</part-num-ref>
|
| 1354 |
+
<confidence value="255">O2H</confidence>
|
| 1355 |
+
<confidence value="8185">McO2</confidence>
|
| 1356 |
+
C C<confidence value="5">O</confidence>
|
| 1357 |
+
2Et <part-num-ref name="O2H McO2C CO2Et">
|
| 1358 |
+
<confidence value="1">9</confidence>
|
| 1359 |
+
</part-num-ref>
|
| 1360 |
+
<confidence value="6">N</confidence>
|
| 1361 |
+
<confidence value="85">H3</confidence>
|
| 1362 |
+
C N <confidence value="8">N</confidence>
|
| 1363 |
+
<confidence value="4155">S^,O</confidence>
|
| 1364 |
+
<confidence value="55">OH</confidence>
|
| 1365 |
+
</p>
|
| 1366 |
+
<heading id="h-27">
|
| 1367 |
+
<confidence value="6">H</confidence>
|
| 1368 |
+
<confidence value="8">H</confidence>
|
| 1369 |
+
<confidence value="4">O</confidence>
|
| 1370 |
+
OH </heading>
|
| 1371 |
+
<heading id="h-28">OH <confidence value="8">F</confidence>
|
| 1372 |
+
</heading>
|
| 1373 |
+
<p id="p-48" num="48">HN H <confidence value="2">0</confidence>
|
| 1374 |
+
I-CA-MPD<confidence value="21">I1</confidence>
|
| 1375 |
+
H3C N OH <confidence value="5">I</confidence>
|
| 1376 |
+
-CA<confidence value="888855">-MPD12</confidence>
|
| 1377 |
+
<confidence value="841">H30</confidence>
|
| 1378 |
+
<confidence value="5">M</confidence>
|
| 1379 |
+
<confidence value="885">H3C</confidence>
|
| 1380 |
+
H <part-num-ref name="I-CA-MPDI1 H3C N OH I-CA-MPD12 H30 M H3C H">
|
| 1381 |
+
<confidence value="2">0</confidence>
|
| 1382 |
+
</part-num-ref>
|
| 1383 |
+
<confidence value="885">H30</confidence>
|
| 1384 |
+
<confidence value="4881">NYO.</confidence>
|
| 1385 |
+
<confidence value="7">S</confidence>
|
| 1386 |
+
<confidence value="18">'N</confidence>
|
| 1387 |
+
H3C <confidence value="6">N</confidence>
|
| 1388 |
+
<part-num-ref name="H30 NYO. S 'N H3C N">
|
| 1389 |
+
<confidence value="22">00</confidence>
|
| 1390 |
+
</part-num-ref>
|
| 1391 |
+
<confidence value="2">H</confidence>
|
| 1392 |
+
<confidence value="5">O</confidence>
|
| 1393 |
+
<confidence value="6">M</confidence>
|
| 1394 |
+
<confidence value="8">=</confidence>
|
| 1395 |
+
<confidence value="5">H</confidence>
|
| 1396 |
+
or a metal <confidence value="468">ion</confidence>
|
| 1397 |
+
I-CA-MPD13 I-CA-MPD14 <confidence value="8">H</confidence>
|
| 1398 |
+
<part-num-ref name="metal ion I-CA-MPD13 I-CA-MPD14 H">
|
| 1399 |
+
<confidence value="2">0</confidence>
|
| 1400 |
+
</part-num-ref>
|
| 1401 |
+
<confidence value="2">N</confidence>
|
| 1402 |
+
<confidence value="2">N</confidence>
|
| 1403 |
+
<confidence value="5">O</confidence>
|
| 1404 |
+
<confidence value="2">H</confidence>
|
| 1405 |
+
I-CA-<confidence value="866844">MPD168</confidence>
|
| 1406 |
+
<confidence value="2">N</confidence>
|
| 1407 |
+
<confidence value="8888888884">I-CA-MPD15</confidence>
|
| 1408 |
+
<confidence value="8">N</confidence>
|
| 1409 |
+
</p>
|
| 1410 |
+
<heading id="h-29">
|
| 1411 |
+
<confidence value="2">H</confidence>
|
| 1412 |
+
<confidence value="2">O</confidence>
|
| 1413 |
+
<confidence value="1112">OOMH</confidence>
|
| 1414 |
+
</heading>
|
| 1415 |
+
<p id="p-49" num="49">
|
| 1416 |
+
<confidence value="5">N</confidence>
|
| 1417 |
+
<confidence value="2222212">I-C-MD1</confidence>
|
| 1418 |
+
<confidence value="122">oCH</confidence>
|
| 1419 |
+
<confidence value="5566555555">I-CA-MPDIS</confidence>
|
| 1420 |
+
<confidence value="1">O</confidence>
|
| 1421 |
+
<confidence value="222112">I-C-?Q</confidence>
|
| 1422 |
+
<confidence value="2">></confidence>
|
| 1423 |
+
<confidence value="221">NxO</confidence>
|
| 1424 |
+
<confidence value="1">N</confidence>
|
| 1425 |
+
<confidence value="1">O</confidence>
|
| 1426 |
+
<confidence value="11">s~</confidence>
|
| 1427 |
+
<confidence value="6">O</confidence>
|
| 1428 |
+
<confidence value="222">0HH</confidence>
|
| 1429 |
+
<confidence value="222222222">I-CA-MPD2</confidence>
|
| 1430 |
+
<confidence value="2">H</confidence>
|
| 1431 |
+
<confidence value="2">O</confidence>
|
| 1432 |
+
<confidence value="2">H</confidence>
|
| 1433 |
+
<confidence value="2566666665">DI-CA-MPD1</confidence>
|
| 1434 |
+
<confidence value="222">Et2</confidence>
|
| 1435 |
+
<confidence value="2">N</confidence>
|
| 1436 |
+
<confidence value="2222">OC-,</confidence>
|
| 1437 |
+
<confidence value="5666666662">I-CA-MPD2H</confidence>
|
| 1438 |
+
<confidence value="112211111111">I-CA-MPDZZD2</confidence>
|
| 1439 |
+
<boundary-data type="header">12 of 39</boundary-data>
|
| 1440 |
+
<boundary-data type="header">PAGE <confidence value="88585">14/41</confidence>
|
| 1441 |
+
RCVD AT <confidence value="66685">12141</confidence>
|
| 1442 |
+
200512:40:00 <confidence value="88">PM</confidence>
|
| 1443 |
+
[Easte<confidence value="5">m</confidence>
|
| 1444 |
+
Standard Time<confidence value="24586685881">]'SVR:USPT1</confidence>
|
| 1445 |
+
FXRF<confidence value="4">4</confidence>
|
| 1446 |
+
132<confidence value="28866884">*DNIS:27</confidence>
|
| 1447 |
+
38300 CSID:84<confidence value="6">7</confidence>
|
| 1448 |
+
<confidence value="66">77</confidence>
|
| 1449 |
+
0 600<confidence value="54">6'</confidence>
|
| 1450 |
+
DURAT<confidence value="668">ION</confidence>
|
| 1451 |
+
<confidence value="8662">(mm-</confidence>
|
| 1452 |
+
ss):09<confidence value="288">-34</confidence>
|
| 1453 |
+
</boundary-data>
|
| 1454 |
+
</p>
|
| 1455 |
+
</description>
|
| 1456 |
+
</us-patent-application>
|
| 1457 |
+
|
prior_art/11217024.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
prior_art/11226590.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
prior_art/11233981.xml
ADDED
|
@@ -0,0 +1,33 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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="11233981.2007-01-12.EWV0LT05PPOPPY4.SPEC.xml" pat:id="ID-11233981.2007-01-12.EWV0LT05PPOPPY4.SPEC" >
|
| 3 |
+
<pat:DocumentCode>SPEC</pat:DocumentCode>
|
| 4 |
+
<pat:DocumentHeaderDetails pat:id="ID-00001">
|
| 5 |
+
<pat:ApplicationHeaderDetails>
|
| 6 |
+
<pat:ApplicationNumber>11233981</pat:ApplicationNumber>
|
| 7 |
+
</pat:ApplicationHeaderDetails>
|
| 8 |
+
<pat:PageTotalQuantity>3</pat:PageTotalQuantity>
|
| 9 |
+
<pat:ParagraphTotalQuantity>14</pat:ParagraphTotalQuantity>
|
| 10 |
+
</pat:DocumentHeaderDetails>
|
| 11 |
+
<pat:MailRoomDate>2007-01-12</pat:MailRoomDate>
|
| 12 |
+
<pat:Specification>
|
| 13 |
+
<?PageStart number='1' fileName='' filePathName=''?>
|
| 14 |
+
<pat:BoundaryData><pat:HeaderText>AMENDMENT AND RESPONSE UNDER 37 CFR <pat:OCRConfidenceData pat:levelNumber="5">§</pat:OCRConfidenceData> 1.111 Page 2</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Serial Number: 11/233,981 Dkt: 2139.<pat:OCRConfidenceData pat:levelNumber="55">00</pat:OCRConfidenceData>2US<pat:OCRConfidenceData pat:levelNumber="4">1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Filing Date: September 23, 2005</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Title: METHOD F<pat:OCRConfidenceData pat:levelNumber="5">O</pat:OCRConfidenceData>R ERECTING AN AT LEAST TW<pat:OCRConfidenceData pat:levelNumber="5">O</pat:OCRConfidenceData>-PIECE MAIN BOOM F<pat:OCRConfidenceData pat:levelNumber="5">O</pat:OCRConfidenceData>R A LATTICE-B<pat:OCRConfidenceData pat:levelNumber="5">O</pat:OCRConfidenceData>OM CRANE AND LATTICE-BOOM</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>CRANE BUILT ACCORDINGLY</pat:HeaderText></pat:BoundaryData><pat:Heading pat:id="h-1">
|
| 15 |
+
IN THE SPECIFICATION</pat:Heading>
|
| 16 |
+
<pat:P pat:id="p-1" pat:pNumber="1">Please amend the specification as follows:</pat:P>
|
| 17 |
+
<pat:P pat:id="p-2" pat:pNumber="2">The paragraph beginning at <pat:PartName pat:idref="PN-00001">page</pat:PartName> <pat:PartNumber pat:id="PN-00001">1,</pat:PartNumber> line <pat:PartName pat:idref="PN-00002">page 1, line</pat:PartName><pat:PartNumber pat:id="PN-00002">6</pat:PartNumber> is amended as follows:</pat:P>
|
| 18 |
+
<pat:P pat:id="p-3" pat:pNumber="3">The present invention relates to a method for erecting [[an]] a boom of a crane, and in particular a method for erecting a main boom of a lattice-boom crane subdivided into at least two jib portions<pat:OCRConfidenceData pat:levelNumber="6">,</pat:OCRConfidenceData> . The main boom is not erected necessarily with the aid of an auxiliary crane or other additional means, but <pat:OCRConfidenceData pat:levelNumber="52">ac</pat:OCRConfidenceData> rather results from using the geometric-kinematic properties of the main boom subdivided into at least two jib portions. Moreover, the present invention relates to a main boom for a lattice-boom crane being adapted for being erected using the method according to the invention such that auxiliary means for erection, as e.g. auxiliary cranes, are not compulsory.</pat:P>
|
| 19 |
+
<pat:P pat:id="p-4" pat:pNumber="4">Moreover, the invention relates to a crane, in particular a lattice-boom crane having a main boom, being constructed to be erected using the method according to the invention.</pat:P>
|
| 20 |
+
<pat:P pat:id="p-5" pat:pNumber="5">The paragraph beginning at <pat:PartName pat:idref="PN-00003">page</pat:PartName> <pat:PartNumber pat:id="PN-00003">20,</pat:PartNumber> line <pat:PartName pat:idref="PN-00004">page 20, line</pat:PartName><pat:PartNumber pat:id="PN-00004">15</pat:PartNumber> is amended as follows:</pat:P>
|
| 21 |
+
<pat:P pat:id="p-6" pat:pNumber="6"><pat:OCRConfidenceData pat:levelNumber="2">t</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="2252">tchc</pat:OCRConfidenceData> When the tilting moment M<pat:OCRConfidenceData pat:levelNumber="5">K</pat:OCRConfidenceData> and the standing moment M<pat:OCRConfidenceData pat:levelNumber="5">s</pat:OCRConfidenceData> are in equilibrium, in a f<pat:OCRConfidenceData pat:levelNumber="8">u</pat:OCRConfidenceData>rther step III it is started to lift the <pat:PartName pat:idref="PN-00005">angled boom portions</pat:PartName> <pat:PartNumber pat:id="PN-00005">1,</pat:PartNumber> <pat:PartName pat:idref="PN-00006">angled boom portions 1,</pat:PartName><pat:PartNumber pat:id="PN-00006">2</pat:PartNumber> by pivoting them around the hinge [[D]] <pat:OCRConfidenceData pat:levelNumber="5">C</pat:OCRConfidenceData> at the <pat:PartName pat:idref="PN-00007">upper carriage</pat:PartName> <pat:PartNumber pat:id="PN-00007">14</pat:PartNumber> of the <pat:PartName pat:idref="PN-00008">crane carriage</pat:PartName> <pat:PartNumber pat:id="PN-00008">19</pat:PartNumber> (Fig. 2d). Already during the lifting of the <pat:PartName pat:idref="PN-00009">angled boom portions</pat:PartName> <pat:PartNumber pat:id="PN-00009">1,</pat:PartNumber> <pat:PartName pat:idref="PN-00010">angled boom portions 1,</pat:PartName><pat:PartNumber pat:id="PN-00010">2,</pat:PartNumber> the <pat:PartName pat:idref="PN-00011">upper boom portion</pat:PartName> <pat:PartNumber pat:id="PN-00011">1</pat:PartNumber> in turn can be pivoted simultaneously upwards around the hinge A, at which it is coupled to the <pat:PartName pat:idref="PN-00012">lower boom portion</pat:PartName> <pat:PartNumber pat:id="PN-00012">2.</pat:PartNumber></pat:P>
|
| 22 |
+
<?PageStart number='2' fileName='' filePathName=''?>
|
| 23 |
+
<pat:BoundaryData><pat:HeaderText>AMENDMENT AND RESPONSE UNDER 37 CFR <pat:OCRConfidenceData pat:levelNumber="5">§</pat:OCRConfidenceData> 1.111 Page 3</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Serial Number: <pat:OCRConfidenceData pat:levelNumber="5">1</pat:OCRConfidenceData>1/233,981 Dkt: 2<pat:OCRConfidenceData pat:levelNumber="4">1</pat:OCRConfidenceData>39.002U<pat:OCRConfidenceData pat:levelNumber="55">S1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Filing Date: September 23, 2005</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Title: METHOD FOR ERECTING AN AT LEAST TWO-PIECE MAIN BOOM FOR A LATTICE-BOOM CRANE AND LATTICE-BO<pat:OCRConfidenceData pat:levelNumber="68">OM</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>CRANE BUILT ACCORDINGLY</pat:HeaderText></pat:BoundaryData><pat:P pat:id="p-7" pat:pNumber="7">The paragraph beginning at <pat:PartName pat:idref="PN-00013">page</pat:PartName> <pat:PartNumber pat:id="PN-00013">21,</pat:PartNumber> line <pat:PartName pat:idref="PN-00014">page 21, line</pat:PartName><pat:PartNumber pat:id="PN-00014">28</pat:PartNumber> is amended as follows:</pat:P>
|
| 24 |
+
<pat:P pat:id="p-8" pat:pNumber="8">Another possibility to erect a main boom using the method according to the invention is shown in Fig. 3a to 3f<pat:OCRConfidenceData pat:levelNumber="52885">[[:]]</pat:OCRConfidenceData>. In Fig. 3a again a starting position of the <pat:PartName pat:idref="PN-00015">main boom</pat:PartName> <pat:PartNumber pat:id="PN-00015">1,</pat:PartNumber> <pat:PartName pat:idref="PN-00016">main boom 1,</pat:PartName><pat:PartNumber pat:id="PN-00016">2</pat:PartNumber> is illustrated, in which the latter is supported besides the first support point in form of a hinge to hinge point C on the <pat:PartName pat:idref="PN-00017">upper carriage</pat:PartName> <pat:PartNumber pat:id="PN-00017">14</pat:PartNumber> at least on a second support point [[C]] <pat:OCRConfidenceData pat:levelNumber="56">D'</pat:OCRConfidenceData> on the ground.</pat:P>
|
| 25 |
+
<pat:P pat:id="p-9" pat:pNumber="9">The upper boom portion 1 and the <pat:PartName pat:idref="PN-00018">lower boom portion</pat:PartName> <pat:PartNumber pat:id="PN-00018">2</pat:PartNumber> are respectively stretched via the <pat:PartName pat:idref="PN-00019">upper retaining cable</pat:PartName> <pat:PartNumber pat:id="PN-00019">9</pat:PartNumber> and a <pat:PartName pat:idref="PN-00020">lower retaining cable</pat:PartName> <pat:PartNumber pat:id="PN-00020">8,</pat:PartNumber> respectively, via the <pat:PartName pat:idref="PN-00021">tension support</pat:PartName> <pat:PartNumber pat:id="PN-00021">15</pat:PartNumber> by means of a <pat:PartName pat:idref="PN-00022">hoist</pat:PartName> <pat:PartNumber pat:id="PN-00022">17</pat:PartNumber> towards a <pat:PartName pat:idref="PN-00023">counter weight</pat:PartName> <pat:PartNumber pat:id="PN-00023">16</pat:PartNumber> at the <pat:PartName pat:idref="PN-00024">upper carriage</pat:PartName> <pat:PartNumber pat:id="PN-00024">14.</pat:PartNumber> In the position shown in Fig.</pat:P>
|
| 26 |
+
<pat:P pat:id="p-10" pat:pNumber="10">3a, the <pat:PartName pat:idref="PN-00025">two retaining cables</pat:PartName> <pat:PartNumber pat:id="PN-00025">8,</pat:PartNumber> <pat:PartName pat:idref="PN-00026">two retaining cables 8,</pat:PartName><pat:PartNumber pat:id="PN-00026">9</pat:PartNumber> are released.</pat:P>
|
| 27 |
+
<pat:P pat:id="p-11" pat:pNumber="11">The paragraph beginning at <pat:PartName pat:idref="PN-00027">page</pat:PartName> <pat:PartNumber pat:id="PN-00027">22,</pat:PartNumber> line <pat:PartName pat:idref="PN-00028">page 22, line</pat:PartName><pat:PartNumber pat:id="PN-00028">8</pat:PartNumber> is amended as follows:</pat:P>
|
| 28 |
+
<pat:P pat:id="p-12" pat:pNumber="12">Starting from this starting position, according to Fig. 3b and 3c, the <pat:PartName pat:idref="PN-00029">lower boom portion</pat:PartName> <pat:PartNumber pat:id="PN-00029">1</pat:PartNumber> is lifted by operating the piston cylinder unit [[5]] 5', whereby the boom tip of the <pat:PartName pat:idref="PN-00030">upper boom portion</pat:PartName> <pat:PartNumber pat:id="PN-00030">1</pat:PartNumber> is caused to move on a <pat:OCRConfidenceData pat:levelNumber="222222">eiekal</pat:OCRConfidenceData> circular path with center point A into the position shown in Fig. 3c. In this position, the effective lever arm <pat:OCRConfidenceData pat:levelNumber="5">1</pat:OCRConfidenceData>' is reduced clearly whereby the tilting moment M<pat:OCRConfidenceData pat:levelNumber="5">K</pat:OCRConfidenceData> producible by the <pat:PartName pat:idref="PN-00031">main boom</pat:PartName> <pat:PartNumber pat:id="PN-00031">1,</pat:PartNumber> <pat:PartName pat:idref="PN-00032">main boom 1,</pat:PartName><pat:PartNumber pat:id="PN-00032">2</pat:PartNumber> has become substantially smaller. Assuming again that the position shown in Fig. 3c is the position in that the tilting moment M<pat:OCRConfidenceData pat:levelNumber="5">K</pat:OCRConfidenceData> is in equilibrium with the standing moment M<pat:OCRConfidenceData pat:levelNumber="5">s</pat:OCRConfidenceData>, then at the earliest in this position it can be started to activate the <pat:PartName pat:idref="PN-00033">hoist</pat:PartName> <pat:PartNumber pat:id="PN-00033">17</pat:PartNumber> whereby by means of traction on the <pat:PartName pat:idref="PN-00034">retaining cable</pat:PartName> <pat:PartNumber pat:id="PN-00034">8,</pat:PartNumber> the <pat:PartName pat:idref="PN-00035">lower boom portion</pat:PartName> <pat:PartNumber pat:id="PN-00035">2</pat:PartNumber> is erected. Thereby, the ground contact at the second support point D is lost.</pat:P>
|
| 29 |
+
<pat:P pat:id="p-13" pat:pNumber="13">The paragraph beginning at <pat:PartName pat:idref="PN-00036">page</pat:PartName> <pat:PartNumber pat:id="PN-00036">22,</pat:PartNumber> line <pat:PartName pat:idref="PN-00037">page 22, line</pat:PartName><pat:PartNumber pat:id="PN-00037">19</pat:PartNumber> is amended as follows:</pat:P>
|
| 30 |
+
<pat:P pat:id="p-14" pat:pNumber="14">According to Fig. 3d, the lower boom portion is in a further lifted position, which has been effected by further activating of the <pat:PartName pat:idref="PN-00038">hoist</pat:PartName> <pat:PartNumber pat:id="PN-00038">17.</pat:PartNumber> Comparing the angle position of the <pat:PartName pat:idref="PN-00039">upper boom portion</pat:PartName> <pat:PartNumber pat:id="PN-00039">1</pat:PartNumber> in Fig. 3c and 3d, it can be seen that the angle has not changed or only negligibly with respect to the horizontal plane. This is achieved due to the fact that during the erection of <?PageStart number='3' fileName='' filePathName=''?>
|
| 31 |
+
<pat:BoundaryData><pat:HeaderText>AMENDMENT AND RESPONSE UNDER 37 CFR <pat:OCRConfidenceData pat:levelNumber="5">§</pat:OCRConfidenceData> 1.111 Page 4</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Serial Number: 11/233,981 Dkt: 2139.002U<pat:OCRConfidenceData pat:levelNumber="44">S1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Filing Date: September 23, 2005</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Title: METHOD FOR ERECTING AN AT LEAST TWO-PIECE MAIN BOOM FOR A LATTICE-BOOM CRANE AND LATTICE-BOOM</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>CRANE BUILT ACCORDINGLY</pat:HeaderText></pat:BoundaryData>the <pat:PartName pat:idref="PN-00040">lower boom portion</pat:PartName> <pat:PartNumber pat:id="PN-00040">2,</pat:PartNumber> the piston cylinder unit [[5]] 5' is drawn in successively. Immediately before the two boom portions according to Fig. 3e have reached the stretched boom position, the <pat:PartName pat:idref="PN-00041">upper retaining cable</pat:PartName> <pat:PartNumber pat:id="PN-00041">9</pat:PartNumber> is stretched such that the <pat:PartName pat:idref="PN-00042">lower retaining cable</pat:PartName> <pat:PartNumber pat:id="PN-00042">8</pat:PartNumber> will become loose. Now, the main boom can be bolted at bolting point B and the crane is ready to be operated (Fig. 3f<pat:OCRConfidenceData pat:levelNumber="68">).</pat:OCRConfidenceData></pat:P>
|
| 32 |
+
</pat:Specification>
|
| 33 |
+
</pat:SpecificationDocument>
|
prior_art/11236126.xml
ADDED
|
@@ -0,0 +1,260 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11236126</doc-number>
|
| 8 |
+
<date>2005-11-18</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">11/18/05 FRI 11:53 FAX 5152881338 MC<confidence value="5">K</confidence>
|
| 14 |
+
EE VOORHEES & SEASE <confidence value="21">01</confidence>
|
| 15 |
+
003 </boundary-data>
|
| 16 |
+
<p id="p-1" num="1">Amendments to the S<confidence value="5">p</confidence>
|
| 17 |
+
ecification Please amend page <part-num-ref name="Specification Please amend page">1,</part-num-ref>
|
| 18 |
+
fourth paragraph, as follows: </p>
|
| 19 |
+
<p id="p-2" num="2">Traditionally, the freezer compartment has been provided above the fre<confidence value="8">s</confidence>
|
| 20 |
+
h food compartment in a so-called top mount refrigerator. The freezer compartment <confidence value="5">m</confidence>
|
| 21 |
+
ay also be located side-by-side with the fresh food compartment. A bottom mount ref<confidence value="7">r</confidence>
|
| 22 |
+
igerator is one in which <confidence value="5">t</confidence>
|
| 23 |
+
he freezer compartment is mounted below the fresh food compartment. These bottom mount refrigerators are popular because they pro<confidence value="8">v</confidence>
|
| 24 |
+
ide easier access to the <confidence value="268182688868">--ezen-fresh</confidence>
|
| 25 |
+
food compartment, and provide relatively mor<confidence value="8">e</confidence>
|
| 26 |
+
useful storage space than the freezer section of a similarly sized side-by-side model. </p>
|
| 27 |
+
<p id="p-3" num="3">Please amend page 10, first and second paragraphs, as follows:</p>
|
| 28 |
+
<p id="p-4" num="4">The embodiment of Figures 3-5 utilizes an icemaker <part-num-ref name="icemaker">32</part-num-ref>
|
| 29 |
+
that mounts to the side<confidence value="485">Wal</confidence>
|
| 30 |
+
l <part-num-ref name="sideWall">36</part-num-ref>
|
| 31 |
+
of the cabinet <part-num-ref name="cabinet">
|
| 32 |
+
<confidence value="42">11</confidence>
|
| 33 |
+
. </part-num-ref>
|
| 34 |
+
This is advantageous because it permits the long dimension of the <confidence value="22222222">icemakdr</confidence>
|
| 35 |
+
<part-num-ref name="icemakdr">32</part-num-ref>
|
| 36 |
+
to be oriented parallel to the sidewall <part-num-ref name="sidewall">36</part-num-ref>
|
| 37 |
+
so that it is completely contained by the depth of th<confidence value="6">e</confidence>
|
| 38 |
+
fresh food compartment <part-num-ref name="fresh food compartment">14.</part-num-ref>
|
| 39 |
+
<confidence value="4252525222222556556">Hewever,;-mcuntingM</confidence>
|
| 40 |
+
ountin<confidence value="5">g</confidence>
|
| 41 |
+
the <confidence value="22222222">icemaker</confidence>
|
| 42 |
+
<part-num-ref name="icemaker">32</part-num-ref>
|
| 43 |
+
to the sidewall <part-num-ref name="sidewall">36</part-num-ref>
|
| 44 |
+
<confidence value="141556">mekes-</confidence>
|
| 45 |
+
improves access to the icemaker <part-num-ref name="icemaker">32</part-num-ref>
|
| 46 |
+
for serviceability <confidence value="222222225">ifficult.</confidence>
|
| 47 |
+
<confidence value="551">Tho</confidence>
|
| 48 |
+
<confidence value="16">c,</confidence>
|
| 49 |
+
<confidence value="56">it</confidence>
|
| 50 |
+
<confidence value="24111">maytz</confidence>
|
| 51 |
+
<confidence value="111">mac</confidence>
|
| 52 |
+
<confidence value="4115">dzci</confidence>
|
| 53 |
+
<confidence value="66686862">However.</confidence>
|
| 54 |
+
</p>
|
| 55 |
+
<p id="p-5" num="5">another option is to mount the icemaker <part-num-ref name="icemaker">32</part-num-ref>
|
| 56 |
+
to the rear wall <part-num-ref name="rear wall">
|
| 57 |
+
<confidence value="66">44</confidence>
|
| 58 |
+
, </part-num-ref>
|
| 59 |
+
as is shown in Figures 28-32. </p>
|
| 60 |
+
<p id="p-6" num="6">The casing 48 that forms the ice compartment walls <part-num-ref name="ice compartment walls">26</part-num-ref>
|
| 61 |
+
may be made from an <confidence value="11">iw</confidence>
|
| 62 |
+
injection molded urethane foam surrounded by a plastic wrapping. Alternatively, the c<confidence value="8">a</confidence>
|
| 63 |
+
sing may be a hollow part that is filled with foam insulation. Typically the walls will be ab<confidence value="8">o</confidence>
|
| 64 |
+
ut <part-num-ref name="walls will be about">1</part-num-ref>
|
| 65 |
+
<confidence value="1">M</confidence>
|
| 66 |
+
</p>
|
| 67 |
+
<heading id="h-1">
|
| 68 |
+
<confidence value="17">C)</confidence>
|
| 69 |
+
</heading>
|
| 70 |
+
<p id="p-7" num="7">inch to 1.5 inches thick<confidence value="5">.</confidence>
|
| 71 |
+
They need to provide sufficient insulation to prevent <confidence value="5">I</confidence>
|
| 72 |
+
<confidence value="22222222">Mweating</confidence>
|
| 73 |
+
<confidence value="88">co</confidence>
|
| 74 |
+
ndensation from forming on the exterior of the walls within the fresh foo<confidence value="8">d</confidence>
|
| 75 |
+
compartment <part-num-ref name="fresh food compartment">14.</part-num-ref>
|
| 76 |
+
They should also have sufficient structural integrity that the top wall <confidence value="5">o</confidence>
|
| 77 |
+
f the casing <part-num-ref name="casing">46</part-num-ref>
|
| 78 |
+
can act as a shelf on which fresh food may be stored. </p>
|
| 79 |
+
<p id="p-8" num="8">Please amend page 12, last paragraph, ending on page 13 as follows:</p>
|
| 80 |
+
<p id="p-9" num="9">As an alternative to locating the ice compartment <part-num-ref name="ice compartment">24</part-num-ref>
|
| 81 |
+
at the lower corner <confidence value="5">o</confidence>
|
| 82 |
+
f the fresh food compartment <part-num-ref name="fresh food compartment">14,</part-num-ref>
|
| 83 |
+
Figures 19-22 show an embodiment where the ice compartment <part-num-ref name="ice compartment">24</part-num-ref>
|
| 84 |
+
is located mid way along one of the sidewa<confidence value="8">l</confidence>
|
| 85 |
+
ls <part-num-ref name="sidewalls">36</part-num-ref>
|
| 86 |
+
of the cabinet <part-num-ref name="cabinet">11.</part-num-ref>
|
| 87 |
+
A casing <part-num-ref name="casing">82</part-num-ref>
|
| 88 |
+
is <confidence value="8">p</confidence>
|
| 89 |
+
rovided to enclose the ice compartment within the fresh food compartment <part-num-ref name="fresh food compartment">14</part-num-ref>
|
| 90 |
+
along one of the sidewalls <part-num-ref name="sidewalls">
|
| 91 |
+
<confidence value="8">2</confidence>
|
| 92 |
+
</part-num-ref>
|
| 93 |
+
PAGE 316<confidence value="5">*</confidence>
|
| 94 |
+
RCVD AT 1<confidence value="5">1</confidence>
|
| 95 |
+
181200511:52:5<confidence value="5">7</confidence>
|
| 96 |
+
<confidence value="88">AM</confidence>
|
| 97 |
+
<confidence value="66">[E</confidence>
|
| 98 |
+
aste<confidence value="66">rn</confidence>
|
| 99 |
+
Standard Time<confidence value="52">]*</confidence>
|
| 100 |
+
SVR:USPT<confidence value="4">O</confidence>
|
| 101 |
+
EFXRF<confidence value="684884">-6128'</confidence>
|
| 102 |
+
DNIS:2738300<confidence value="2">*</confidence>
|
| 103 |
+
CS<confidence value="4">I</confidence>
|
| 104 |
+
D:5152881338<confidence value="2">*</confidence>
|
| 105 |
+
DURATION (mm<confidence value="5">-</confidence>
|
| 106 |
+
ss):02<confidence value="45">08</confidence>
|
| 107 |
+
<page-break num="2"/>
|
| 108 |
+
<boundary-data type="header">11/18/05 FRI 11:54 FAX 5152881338 MC<confidence value="5">K</confidence>
|
| 109 |
+
EE VOORHEES & SEASE <confidence value="5">1</confidence>
|
| 110 |
+
004 </boundary-data>
|
| 111 |
+
<part-num-ref name="PAGE 316* RCVD AT 11181200511:52:57 AM [Eastern Standard Time]* SVR:USPTOEFXRF-6128' DNIS:2738300* CSID:5152881338* DURATION (mm-ss):0208">36</part-num-ref>
|
| 112 |
+
of the cabinet <part-num-ref name="cabinet">
|
| 113 |
+
<confidence value="66">11</confidence>
|
| 114 |
+
</part-num-ref>
|
| 115 |
+
of a bottom mount refrigerator. The casing <part-num-ref name="casing">82</part-num-ref>
|
| 116 |
+
is sealed <confidence value="22222">alosg</confidence>
|
| 117 |
+
the rear wall <part-num-ref name="rear wall">44,</part-num-ref>
|
| 118 |
+
sidewall <part-num-ref name="rear wall 44, sidewall">36</part-num-ref>
|
| 119 |
+
and divider wall <part-num-ref name="and divider wall">16</part-num-ref>
|
| 120 |
+
to enclose the ice compartment <part-num-ref name="ice compartment">24.</part-num-ref>
|
| 121 |
+
A f<confidence value="8">r</confidence>
|
| 122 |
+
ont portion of the casing <part-num-ref name="casing">82</part-num-ref>
|
| 123 |
+
may be removable to provide access to the ice compartment <part-num-ref name="ice compartment">24.</part-num-ref>
|
| 124 |
+
P<confidence value="8">r</confidence>
|
| 125 |
+
eferably the casing <part-num-ref name="casing">82</part-num-ref>
|
| 126 |
+
is insulated to allow for a temperature difference between the ice compartment <part-num-ref name="ice compartment">24</part-num-ref>
|
| 127 |
+
and the fresh food compartment <part-num-ref name="fresh food compartment">14.</part-num-ref>
|
| 128 |
+
An air duct <part-num-ref name="air duct">74</part-num-ref>
|
| 129 |
+
is provided at the rear of the ice c<confidence value="88">om</confidence>
|
| 130 |
+
part<confidence value="8">m</confidence>
|
| 131 |
+
ent <part-num-ref name="ice compartment">24</part-num-ref>
|
| 132 |
+
to provide cold air from the evaporator to the ice compartment <part-num-ref name="ice compartment">24</part-num-ref>
|
| 133 |
+
through opening 84.<confidence value="1">,</confidence>
|
| 134 |
+
Bracket <part-num-ref name="through opening 84., Bracket">86</part-num-ref>
|
| 135 |
+
fastens to rear wall <part-num-ref name="fastens to rear wall">44</part-num-ref>
|
| 136 |
+
to provide a mounting bracket for icemaker <part-num-ref name="mounting bracket for icemaker">32.</part-num-ref>
|
| 137 |
+
<confidence value="11421415566651122656">Pnfembi-abraed8;4hat</confidence>
|
| 138 |
+
<confidence value="244224256266266625">theemaker-32-and-5</confidence>
|
| 139 |
+
<confidence value="4485884681">bfaeket-86</confidence>
|
| 140 |
+
A water line fill tube <part-num-ref name="water line fill tube">87</part-num-ref>
|
| 141 |
+
supplies water to the icemaker <part-num-ref name="icemaker">32<confidence value="2">.</confidence>
|
| 142 |
+
</part-num-ref>
|
| 143 |
+
Motor <part-num-ref name="icemaker 32. Motor">38</part-num-ref>
|
| 144 |
+
turns spindle <part-num-ref name="turns spindle">88</part-num-ref>
|
| 145 |
+
that has two prongs <part-num-ref name="that has two prongs">90</part-num-ref>
|
| 146 |
+
that engage hel<confidence value="518888">e-ribs</confidence>
|
| 147 |
+
<part-num-ref name="that engage hele-ribs">92</part-num-ref>
|
| 148 |
+
in disk <part-num-ref name="in disk">94</part-num-ref>
|
| 149 |
+
associated with auger <part-num-ref name="associated with auger">40.</part-num-ref>
|
| 150 |
+
The dispenser assembly <part-num-ref name="dispenser assembly">46</part-num-ref>
|
| 151 |
+
is provided at the end of the auger <part-num-ref name="auger">40</part-num-ref>
|
| 152 |
+
to slowly dispense ice to the dispen<confidence value="8">s</confidence>
|
| 153 |
+
ing area <part-num-ref name="dispensing area">22</part-num-ref>
|
| 154 |
+
through an aperture <part-num-ref name="aperture">96</part-num-ref>
|
| 155 |
+
formed on a lower surface of the casing <part-num-ref name="casing">82.</part-num-ref>
|
| 156 |
+
</p>
|
| 157 |
+
<p id="p-10" num="10">Please amend the last paragraph on page <part-num-ref name="last paragraph on page">15,</part-num-ref>
|
| 158 |
+
ending on page <part-num-ref name="last paragraph on page 15, ending on page">16</part-num-ref>
|
| 159 |
+
as follows: </p>
|
| 160 |
+
<p id="p-11" num="11">Figures 34-36 illustrate an embodiment of a trigger mechanism that can be use<confidence value="8">d</confidence>
|
| 161 |
+
to activate a dispensing occurrence with any of the above described embodiments. Selection butto<confidence value="8">n</confidence>
|
| 162 |
+
s <part-num-ref name="above described embodiments. Selection buttons">
|
| 163 |
+
<confidence value="666">116</confidence>
|
| 164 |
+
</part-num-ref>
|
| 165 |
+
<confidence value="224">aem</confidence>
|
| 166 |
+
provided on facing <part-num-ref name="aem provided on facing">118</part-num-ref>
|
| 167 |
+
that fits on the door <part-num-ref name="door">18</part-num-ref>
|
| 168 |
+
in alignment with the shell <part-num-ref name="shell">56.</part-num-ref>
|
| 169 |
+
The sel<confidence value="78">ec</confidence>
|
| 170 |
+
tion buttons <part-num-ref name="selection buttons">116</part-num-ref>
|
| 171 |
+
allow a user to choose a dispensing mode such as ice, water, or crushed ice. The shell <part-num-ref name="shell">60</part-num-ref>
|
| 172 |
+
forms a cavity that defines the dispensing area <part-num-ref name="dispensing area">22.</part-num-ref>
|
| 173 |
+
An activation lever <part-num-ref name="activation lever">120</part-num-ref>
|
| 174 |
+
extends downwardly at the rear of <confidence value="2">-</confidence>
|
| 175 |
+
the dispensing area <part-num-ref name="dispensing area">22.</part-num-ref>
|
| 176 |
+
Activation lever <part-num-ref name="dispensing area 22. Activation lever">120</part-num-ref>
|
| 177 |
+
is connected to an activation switch <part-num-ref name="activation switch">124</part-num-ref>
|
| 178 |
+
<confidence value="5">b</confidence>
|
| 179 |
+
y a linkage assembly <part-num-ref name="linkage assembly">122.</part-num-ref>
|
| 180 |
+
To activate a dispensing occurrence, the cup or glass <part-num-ref name="cup or glass">60</part-num-ref>
|
| 181 |
+
is moved into <confidence value="55">th</confidence>
|
| 182 |
+
e dispensing <confidence value="2">r</confidence>
|
| 183 |
+
area <part-num-ref name="dispensing r area">22</part-num-ref>
|
| 184 |
+
and pressed against activation lever <part-num-ref name="and pressed against activation lever">120.</part-num-ref>
|
| 185 |
+
When activation lever <part-num-ref name="and pressed against activation lever 120. When activation lever">120</part-num-ref>
|
| 186 |
+
is <confidence value="222222222222222">pressedrearward</confidence>
|
| 187 |
+
, the <confidence value="2">o</confidence>
|
| 188 |
+
linkage assembly <part-num-ref name="o linkage assembly">122</part-num-ref>
|
| 189 |
+
correspondingly moves the activation switch <part-num-ref name="activation switch">124</part-num-ref>
|
| 190 |
+
outward to a c<confidence value="8">l</confidence>
|
| 191 |
+
osed position <part-num-ref name="closed position">
|
| 192 |
+
<confidence value="2">0</confidence>
|
| 193 |
+
</part-num-ref>
|
| 194 |
+
that activates a dispensing occurrence by starting any associated motors and by openin<confidence value="8">g</confidence>
|
| 195 |
+
any necessary <confidence value="55">-<</confidence>
|
| 196 |
+
flaps or covers to allow passage of ice from the storage container <part-num-ref name="storage container">34</part-num-ref>
|
| 197 |
+
to the dispensing area <part-num-ref name="dispensing area">22.</part-num-ref>
|
| 198 |
+
Figure 35 shows the trigger mechanism in a normal rest position with the activation switch <part-num-ref name="activation switch">12<confidence value="6">4</confidence>
|
| 199 |
+
</part-num-ref>
|
| 200 |
+
withdrawn to a closed position. Figure 36 shows the trigger mechanism in a dispense position with <confidence value="4">t</confidence>
|
| 201 |
+
he cup <part-num-ref name="cup">60</part-num-ref>
|
| 202 |
+
pressing against the lever <part-num-ref name="lever">120</part-num-ref>
|
| 203 |
+
to move the activation switch to the extended closed position. It should be appreciated that rather than selection buttons <part-num-ref name="extended closed position. It should be appreciated that rather than selection buttons">116,</part-num-ref>
|
| 204 |
+
a sliding lever could be used to i<confidence value="88">nd</confidence>
|
| 205 |
+
icated <confidence value="888">the</confidence>
|
| 206 |
+
preferred dispensing mode. This mechanical trigger mechanism for activating the dis<confidence value="8">p</confidence>
|
| 207 |
+
ense system <part-num-ref name="dispense system">
|
| 208 |
+
<confidence value="8">3</confidence>
|
| 209 |
+
</part-num-ref>
|
| 210 |
+
PAGE 4<confidence value="682">16*</confidence>
|
| 211 |
+
RCVD AT 11<confidence value="5882">1181</confidence>
|
| 212 |
+
200511:<confidence value="5">5</confidence>
|
| 213 |
+
2:57 <confidence value="88">AM</confidence>
|
| 214 |
+
<confidence value="5">[</confidence>
|
| 215 |
+
Easte<confidence value="66">rn</confidence>
|
| 216 |
+
Standard <confidence value="666622">Time]*</confidence>
|
| 217 |
+
SVR:USPT<confidence value="25">C-</confidence>
|
| 218 |
+
EFXRF<confidence value="28588">-6128</confidence>
|
| 219 |
+
DNIS:27383<confidence value="411">00r</confidence>
|
| 220 |
+
CSID:5152881338<confidence value="2">*</confidence>
|
| 221 |
+
DURATION <confidence value="6882">(mm-</confidence>
|
| 222 |
+
ss):02<confidence value="288">-08</confidence>
|
| 223 |
+
<page-break num="3"/>
|
| 224 |
+
<boundary-data type="header">11/18/05 FRI 11:54 FAX 5152881338 MCKEE VOORHEES & SEASE <confidence value="5511886">lijl005</confidence>
|
| 225 |
+
</boundary-data>
|
| 226 |
+
eliminates electrical wires which typically <confidence value="66">ru</confidence>
|
| 227 |
+
n throu<confidence value="67">gh</confidence>
|
| 228 |
+
the door hinge pin and the <confidence value="2222222">doorlto</confidence>
|
| 229 |
+
the dispenser cavity area. Therefore, the door can more easily be re<confidence value="8">m</confidence>
|
| 230 |
+
oved and the swing of the do<confidence value="5">o</confidence>
|
| 231 |
+
reversed by moving the hinge to the opposite side of the cabinet<confidence value="5">.</confidence>
|
| 232 |
+
Such swing reversal normally is not an issue on side-by<confidence value="5">-</confidence>
|
| 233 |
+
side models. </p>
|
| 234 |
+
<p id="p-12" num="12">
|
| 235 |
+
<confidence value="12">44</confidence>
|
| 236 |
+
<confidence value="2222">P5S5</confidence>
|
| 237 |
+
</p>
|
| 238 |
+
<heading id="h-2">
|
| 239 |
+
<confidence value="11">I-</confidence>
|
| 240 |
+
</heading>
|
| 241 |
+
<p id="p-13" num="13">
|
| 242 |
+
<confidence value="11">iC</confidence>
|
| 243 |
+
</p>
|
| 244 |
+
<heading id="h-3">
|
| 245 |
+
<confidence value="11">II</confidence>
|
| 246 |
+
</heading>
|
| 247 |
+
<p id="p-14" num="14">
|
| 248 |
+
<confidence value="1">i</confidence>
|
| 249 |
+
<confidence value="2">4</confidence>
|
| 250 |
+
<confidence value="222">PAG</confidence>
|
| 251 |
+
<confidence value="2112212211222222">512RVDT118201:25</confidence>
|
| 252 |
+
<confidence value="22222">M[atr</confidence>
|
| 253 |
+
<confidence value="2222">tnad</confidence>
|
| 254 |
+
<confidence value="21222112221222211122222111">SRUPOEXF622DI:7802CI:12838</confidence>
|
| 255 |
+
<confidence value="2222">DRTO</confidence>
|
| 256 |
+
<confidence value="211211">m~s:20</confidence>
|
| 257 |
+
</p>
|
| 258 |
+
</description>
|
| 259 |
+
</us-patent-application>
|
| 260 |
+
|
prior_art/11238937.xml
ADDED
|
@@ -0,0 +1,163 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11238937</doc-number>
|
| 8 |
+
<date>2005-09-29</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">UNITED STATES</heading>
|
| 14 |
+
<heading id="h-2">PATENT APPLICATION</heading>
|
| 15 |
+
<p id="p-1" num="1">for Enhancing Tables and SQL Interaction with Queue Semantics submitted by Jason Chen <confidence value="22222222">Bhashyam</confidence>
|
| 16 |
+
Ramesh on behalf of NCR Corporation Dayton, Ohio Express Mail No.: <confidence value="11">t0</confidence>
|
| 17 |
+
<confidence value="1">(</confidence>
|
| 18 |
+
<confidence value="1">I</confidence>
|
| 19 |
+
<confidence value="1">%</confidence>
|
| 20 |
+
<confidence value="2">/</confidence>
|
| 21 |
+
Date:<confidence value="2222222">_______</confidence>
|
| 22 |
+
<confidence value="2">_</confidence>
|
| 23 |
+
Prepared by Harden E. Stevens, III Reg. 55,649 NCR Corporation 1700 South Patterson Avenue Dayton, OH <part-num-ref name="South Patterson Avenue Dayton, OH">45479</part-num-ref>
|
| 24 |
+
<part-num-ref name="">(803)</part-num-ref>
|
| 25 |
+
939-6505 [voice] <part-num-ref name="939-6505 [voice]">(803)</part-num-ref>
|
| 26 |
+
939-5099 [fax] <boundary-data type="header">NCR Docket 11557.00 1</boundary-data>
|
| 27 |
+
<page-break num="2"/>
|
| 28 |
+
Technical Field [1] The present invention relates to Enterprise Data Warehouses and Relational Database Management Systems used to support real-time decision management. </p>
|
| 29 |
+
<p id="p-2" num="2">Background [2] Enterprise data warehouse (EDW) systems have traditionally been used for decision support by enabling business entities to view some aspect of their businesses in real-time and plan tactical or strategic moves aimed at improving operations. Businesses increasingly are trying to push the decision support capabilities of EDW systems to real-time, allowing for decisions on business operations to be made quickly in response to certain events. In many cases, real- time events occur in some time-ordered manner or priority, the order of which the businesses would like to preserve and react to accordingly. Traditional EDW systems, however, do not easily lend themselves to these sort of time-ordered operations, and attempts at making them do so have proven difficult.</p>
|
| 30 |
+
<p id="p-3" num="3">Summary [3] In general, according to one embodiment, this invention involves a method for use in delivering data from a database table in response to a query. The method includes accessing an ordered list that indicates an order of retrieval for each of one or more rows in the database table and returning the row that is first in the order.</p>
|
| 31 |
+
<p id="p-4" num="4">[4] In general, according to one embodiment, this invention involves a method for use in delivering data from a database table in response to a query. The method includes assessing whether the database table has any rows of data. When there are no rows of data in the table, halting execution of the query until data is placed in the database table and then returning the data that was placed in the database table.</p>
|
| 32 |
+
<p id="p-5" num="5">[5] In general, according to one embodiment, this invention involves a system for use in delivering data from a database table in response to a query. The system provided by embodiments of the present invention comprises: a database that includes one table; one or more data-storage facilities that together store the <boundary-data type="header">NCR Docket 11557.00 2</boundary-data>
|
| 33 |
+
<page-break num="3"/>
|
| 34 |
+
database; and a database-management component coupled to the database and configured to access an ordered list that indicates an order of retrieval for each of one or more rows in the database table and returns the row that is first in the order. </p>
|
| 35 |
+
<p id="p-6" num="6">[6] In general, according to one embodiment, this invention involves a system for use in storing data in a database table. The system provided by embodiments of the present invention comprises: a database that includes one table; one or more data-storage facilities that together store the database; and a database-management component coupled to the database and configured to store data in one or more rows in the database table and create an ordered list that indicates an order of retrieval for the one or more rows.</p>
|
| 36 |
+
<p id="p-7" num="7">[7] In general, according to one embodiment, this invention involves a system for use in delivering data from a database table in response to a query. The system provided by embodiments of the present invention comprises: a database that includes one table; one or more data-storage facilities that together store the database; and a database-management component coupled to the database and configured to assess whether the database table has any rows of data. When there are no rows of data in the table, halting executing of the query until data is placed in the database table and then returning the data that was placed in the database table.</p>
|
| 37 |
+
<p id="p-8" num="8">Brief Description of the Drawings [8] Figures <confidence value="2">I</confidence>
|
| 38 |
+
A and <confidence value="5">1</confidence>
|
| 39 |
+
B are block diagrams of a massively parallel processor (MPP) system. </p>
|
| 40 |
+
<p id="p-9" num="9">[9] Figure 2 is a block diagram of a database comprising a queue table and a relational database table.</p>
|
| 41 |
+
<p id="p-10" num="10">[10] Figure 3 is a flow chart that illustrates execution of a query on a queue table.</p>
|
| 42 |
+
<p id="p-11" num="11">
|
| 43 |
+
<confidence value="8666">[11]</confidence>
|
| 44 |
+
Figure 4 is a flow chart that illustrates execution of a "select and consume<confidence value="5">"</confidence>
|
| 45 |
+
command on a queue table. </p>
|
| 46 |
+
<p id="p-12" num="12">[12] Figures 5A and 5B are flow charts that illustrate insertion of data into a queue table.</p>
|
| 47 |
+
<boundary-data type="header">NCR Docket 11557.00 3</boundary-data>
|
| 48 |
+
<p id="p-13" num="13">
|
| 49 |
+
<page-break num="4"/>
|
| 50 |
+
Detailed Description [13] Figures <confidence value="5">1</confidence>
|
| 51 |
+
A and 1B are block diagrams that illustrate an exemplary computer hardware environment that is often used to implement an Enterprise Data Warehouse (EDW) as a Relational Database Management System (RDBMS). The computer hardware environment shown here is a massively parallel processing (MPP) computer system <part-num-ref name="massively parallel processing (MPP) computer system">100</part-num-ref>
|
| 52 |
+
that includes one or more nodes <part-num-ref name="that includes one or more nodes">102</part-num-ref>
|
| 53 |
+
interconnected by a network <part-num-ref name="network">104.</part-num-ref>
|
| 54 |
+
Within each of the nodes <part-num-ref name="nodes">102</part-num-ref>
|
| 55 |
+
is a processing module <part-num-ref name="processing module">106,</part-num-ref>
|
| 56 |
+
which typically includes: one or more physical processors 112; random access memory (RAM) 116; read-only memory (ROM) 118; network communications hardware 110; and other components. Each of the physical processors <part-num-ref name="physical processors">112</part-num-ref>
|
| 57 |
+
may also include multiple core processors. In some systems, one or more data storage units (DSUs) <part-num-ref name="may also include multiple core processors. In some systems, one or more data storage units (DSUs)">108</part-num-ref>
|
| 58 |
+
are attached to the processing module <part-num-ref name="processing module">106</part-num-ref>
|
| 59 |
+
through a storage controller <part-num-ref name="storage controller">114.</part-num-ref>
|
| 60 |
+
</p>
|
| 61 |
+
<p id="p-14" num="14">Typically, at least one of the nodes <part-num-ref name="nodes">102</part-num-ref>
|
| 62 |
+
also includes user interface components such as a monitor, a keyboard, and a mouse <part-num-ref name="mouse">120.</part-num-ref>
|
| 63 |
+
A database administrator (DBA) is able to manage the RDBMS through the user interface components <part-num-ref name="user interface components">120</part-num-ref>
|
| 64 |
+
in one of the nodes or by communicating over the network <part-num-ref name="network">104</part-num-ref>
|
| 65 |
+
to one of the nodes <part-num-ref name="nodes">102</part-num-ref>
|
| 66 |
+
having a user interface <part-num-ref name="user interface">120.</part-num-ref>
|
| 67 |
+
</p>
|
| 68 |
+
<p id="p-15" num="15">[14] Each of the nodes <part-num-ref name="nodes">102</part-num-ref>
|
| 69 |
+
executes one or more computer programs, such as an operating system, Data Mining Applications performing data mining operations, Real-time Data Management (RTDM) Applications for performing operations on the data, Client Database Applications interacting with the database, <confidence value="222222">and/or</confidence>
|
| 70 |
+
a Relational Database Management System (RDBMS) for managing a relational database stored across one or more of the DSUs. In some embodiments, a computer system having only a single node manages all or some subset of the computer programs. </p>
|
| 71 |
+
<p id="p-16" num="16">[15] Those skilled in the art will recognize that the exemplary environment illustrated in Figures <confidence value="5">1</confidence>
|
| 72 |
+
A and 1B are not intended to limit the present invention. </p>
|
| 73 |
+
<p id="p-17" num="17">Indeed, those skilled in the art will recognize that other alternative hardware environments may be used without departing from the scope of the present invention. In addition, it should be understood that the present invention may also apply to other computer programs than those disclosed here.</p>
|
| 74 |
+
<boundary-data type="header">NCR Docket 11557.00 4</boundary-data>
|
| 75 |
+
<p id="p-18" num="18">
|
| 76 |
+
<page-break num="5"/>
|
| 77 |
+
[16] Figure 2 shows the structure of a relational database <part-num-ref name="relational database">200</part-num-ref>
|
| 78 |
+
which is organized into one or more relational tables <part-num-ref name="which is organized into one or more relational tables">205</part-num-ref>
|
| 79 |
+
that store data in an organized fashion, typically according to a logical data model (LDM) created especially for the type of data being stored. Client computer systems access the data stored in the database tables <part-num-ref name="database tables">205</part-num-ref>
|
| 80 |
+
by submitting queries to the RDBMS in some database query language such as the Structured Query Language (SQL) put forth by the American National Standards Institute (ANSI). One or more indexes <part-num-ref name="American National Standards Institute (ANSI). One or more indexes">240</part-num-ref>
|
| 81 |
+
are created within the database to summarize the data stored in the database and thus to reduce the time required to identif<confidence value="8">y</confidence>
|
| 82 |
+
and access the data that is responsive to any given query. The index <part-num-ref name="index">240</part-num-ref>
|
| 83 |
+
typically contains information about the data stored in each row of a table, information which allows the database to execute database queries without accessing and examining every row in the table. </p>
|
| 84 |
+
<p id="p-19" num="19">[17] In addition to traditional relational tables, the database <part-num-ref name="database">200</part-num-ref>
|
| 85 |
+
also includes one or more tables, known as queue tables <part-num-ref name="also includes one or more tables, known as queue tables">210,</part-num-ref>
|
| 86 |
+
that provide enhanced support for real- time decision making in an EDW system. Each of the queue tables <part-num-ref name="queue tables">210</part-num-ref>
|
| 87 |
+
is a relational table that has non-traditional "queue like" properties. In particular, each of the queue tables <part-num-ref name="queue tables">210</part-num-ref>
|
| 88 |
+
is created and managed in a manner that provides for the preservation of order amongst data placed in the table. This preservation of order typically appears as a preservation of some time related order (e.g., the time order in which the data is placed in the queue table or comes into existence at some external source) or as the preservation of some priority-based order (e.g., higher priority data is distinguished from lower priority data). In general, the queue tables typically use some characteristic of the data they store - be it an intrinsic characteristic of the data created with the data itself or an extrinsic characteristic added to the data at some point - to indicate an order of retrieval for returning the rows of data that make up the tables. </p>
|
| 89 |
+
<p id="p-20" num="20">[18] One way that the database, through the queue tables <part-num-ref name="queue tables">210,</part-num-ref>
|
| 90 |
+
preserves the order of data is through the use of one or more index type structures known as ordered lists <part-num-ref name="use of one or more index type structures known as ordered lists">220.</part-num-ref>
|
| 91 |
+
Each of the ordered lists <part-num-ref name="ordered lists">220</part-num-ref>
|
| 92 |
+
in the database maintains, for a corresponding queue table <part-num-ref name="corresponding queue table">210,</part-num-ref>
|
| 93 |
+
an order of retrieval for the rows stored in that queue table. Unlike a standard database index <part-num-ref name="standard database index">240,</part-num-ref>
|
| 94 |
+
which can not anticipate which <boundary-data type="header">NCR Docket 11557.00 5</boundary-data>
|
| 95 |
+
<page-break num="6"/>
|
| 96 |
+
data will be requested or the order in which it will be returned, the ordered lists <part-num-ref name="ordered lists">220</part-num-ref>
|
| 97 |
+
are created precisely to specify which rows of data are returned in response to individual queries. </p>
|
| 98 |
+
<p id="p-21" num="21">[19] The criteria used in any one of the ordered lists <part-num-ref name="ordered lists">220</part-num-ref>
|
| 99 |
+
to govern the retrieval order for rows of data stored in the corresponding queue table <part-num-ref name="corresponding queue table">210</part-num-ref>
|
| 100 |
+
are independent of the nature of the database system in which the queue tables are implemented and are often chosen by the DBA. For example, in some systems, the retrieval order in an ordered list relies on time based information, such as a timestamp indicating when each row was created in the corresponding queue table. The database may or may not store the time based information with the corresponding rows of data. This time based information, when it is stored with the corresponding data, is typically stored in a time indicator data column <part-num-ref name="time indicator data column">215</part-num-ref>
|
| 101 |
+
in the corresponding queue table <part-num-ref name="corresponding queue table">210.</part-num-ref>
|
| 102 |
+
In some embodiments however, the time based information, if stored at all, is stored outside of the queue table. For example, in some of these embodiments, the time based information is stored as part of the ordered list that corresponds to the queue table. Also, in some embodiments, the time based information is hidden and is not assessable through database queries, while in other embodiments the time based information is accessible through database queries. </p>
|
| 103 |
+
<p id="p-22" num="22">[20] In other embodiments, the retrieval order preserved by the ordered list is based on an occurrence of some event other than the time at which the data was stored in the corresponding queue table. In these embodiments, the time at which the event occurred is typically supplied with the data.</p>
|
| 104 |
+
<p id="p-23" num="23">[21] In still other embodiments, retrieval order is based on priority ratings assigned to the rows of data stored in the queue table. In some cases, the priority ratings are provided to the database along with the data and, in others, priority ratings are calculated within the database by applying an algorithm to the data stored in the queue table.</p>
|
| 105 |
+
<p id="p-24" num="24">[22] Queue tables like those described above carry several advantages beyond their ability to preserve order among data. These advantages include: 1) the ability to suspend execution of a database query when no data is available and then resume execution of the query and return the requested data when the data becomes <boundary-data type="header">NCR Docket 11557.00 6</boundary-data>
|
| 106 |
+
<page-break num="7"/>
|
| 107 |
+
available; <part-num-ref name="data becomes available;">2)</part-num-ref>
|
| 108 |
+
the ability to return only a single row of data in response to a query, even when multiple rows satisfy the query; and <part-num-ref name="query; and">3)</part-num-ref>
|
| 109 |
+
the ability to execute "select and consume" queries that lead to the return of a row of data followed by deletion of the data from the queue table. </p>
|
| 110 |
+
<p id="p-25" num="25">[23<confidence value="5">]</confidence>
|
| 111 |
+
In regard to the first of these advantages, when the database receives a traditional database query, the database either returns the requested data or upon failing to return data, indicates that no data is available and ends the query. In a real-time environment, failing to return data wastes valuable computer and database resources, because it forces the reissuance of the query, perhaps more than once, until data is available. Through the use of queue tables, on the other hand, the database is able to suspend execution of a query when no data is available and resume execution of the query once the data becomes available. Suspending and resuming queries in this manner reduces the consumption of computer and database resources used in processing queries and reduces the delays traditionally associated with retrieving real-time data from the database. </p>
|
| 112 |
+
<p id="p-26" num="26">[24] The second of the advantages listed above is the ability of the database to return only a sing<confidence value="8">l</confidence>
|
| 113 |
+
e row of data from a database table in response to a query, even when multiple rows of data might satisfy the query. In a traditional database system, a single row of data can be returned only if the query is sufficiently complex and has decided to target only that row. Quiet often, such a query is not even possible. In a database system implementing queue tables however, the DBA can set the system to return only one row from a queue table in response to any query. Returning only a single row of data greatly reduces the complexity of database queries and minimizes the impact on the resources required to execute the queries when only small amounts of data are needed at a time. </p>
|
| 114 |
+
<p id="p-27" num="27">[25] The use of queue tables also allows the database to execute "select and consume" commands. These commands provide a simple mechanism for retrieving a row of data from a queue table and then removing or deleting the returned row from the queue table. In general, the "select and consume command" is performed as an indivisible command that is not and in fact can not be interrupted during execution. In a traditional database system, data is locked at the SQL command <boundary-data type="header">NCR Docket 11557.00 7</boundary-data>
|
| 115 |
+
<page-break num="8"/>
|
| 116 |
+
level to prevent the execution of other queries attempting to retrieve the same data before that data can be deleted from the table. The structure of the queue table allows for easy execution of a "select and consume" command in the database system. </p>
|
| 117 |
+
<p id="p-28" num="28">[26] Figures 3 and <part-num-ref name="and">4</part-num-ref>
|
| 118 |
+
both show examples for flow of operations in the database when processing queries that target queue tables. In general, the database processes incoming queries differently when a queue table is targeted than it does when a tradition relational table is targeted. </p>
|
| 119 |
+
<p id="p-29" num="29">[27] Figure 3 illustrates a database operation where suspension and resumption of a query is called for. Upon receiving a query that targets a queue table (step 300), the database assesses whether data is available in the table (step 310). If data is available, the database returns at least some portion of the requested data (step <confidence value="8">3</confidence>
|
| 120 |
+
20). If no data is available in the queue table, the database halts execution of the query command (step <part-num-ref name="query command (step">330)</part-num-ref>
|
| 121 |
+
until it receives an indication that data responsive to the query has been placed into the table (step 340). Upon receiving the indication, the database resumes the query (step <part-num-ref name="query (step">350)</part-num-ref>
|
| 122 |
+
and returns at least some portion of the data requested (step 320). </p>
|
| 123 |
+
<p id="p-30" num="30">[28] In some systems, when the database system suspends a query, the application that issued the query also suspends execution. In some of these systems, the application starts a timer before issuing the query. If the timer expires before the application has received a response to the query, the application (or some part of the application) resumes execution and the application decides whether to:</p>
|
| 124 |
+
<p id="p-31" num="31">1) abort the query altogether; <part-num-ref name="query altogether;">2)</part-num-ref>
|
| 125 |
+
process other work while continuing to await for a response; or <part-num-ref name="response; or">3)</part-num-ref>
|
| 126 |
+
set another timer and continue to wait for a response to the query. </p>
|
| 127 |
+
<p id="p-32" num="32">[29] Fig. 4 shows an example of database operations when queue tables are present in the system. Upon receiving a database query, (step 400), the database assesses whether data is available in the table or tables (step 410). If data is available, the database assesses the type of table targeted by the query (step 415). If a queue table is not involved in the query, the database returns at least some portion of the requested data (step <part-num-ref name="requested data (step">425)</part-num-ref>
|
| 128 |
+
and the database terminates the processing of the query (step 470). If a queue table is involved in the query, the database identifies <boundary-data type="header">NCR Docket 11557.00 8</boundary-data>
|
| 129 |
+
<page-break num="9"/>
|
| 130 |
+
and locks the next row in the queue table (step <part-num-ref name="queue table (step">440)</part-num-ref>
|
| 131 |
+
and then returns at least some portion of the requested data (step 445). The database then assesses whether the requested data was returned successfully (step 450). If the data was returned successfully, the locked row is deleted from the queue table and the lock is removed (step 455), and then the database terminates the processing of the query (step 470). </p>
|
| 132 |
+
<p id="p-33" num="33">If the data was not returned successfully, the data remains in the queue table but the lock is removed (step <part-num-ref name="lock is removed (step">460)</part-num-ref>
|
| 133 |
+
and the database terminates the processing of the query (step 470). </p>
|
| 134 |
+
<p id="p-34" num="34">[30] Returning to step 410, if no data is available, the database assesses the type of table targeted by the query (step 420). If a queue table is not involved in the query, the database will return a token indicating that no data was available and then terminate the processing of the query (step 470). If a queue table is involved in the query, the database will suspend execution of the query until the requested data is received (step <part-num-ref name="requested data is received (step">435)</part-num-ref>
|
| 135 |
+
and then terminate the processing of the query (step 470). </p>
|
| 136 |
+
<p id="p-35" num="35">[31] Figures 5A and <confidence value="5">5</confidence>
|
| 137 |
+
B both show examples for inserting data into a queue table. </p>
|
| 138 |
+
<p id="p-36" num="36">In general, when data is inserted into a queue table, the database performs the traditional steps of inserting the data into the queue table and then performs an additional step of managing an ordered list that is associated with the queue table.</p>
|
| 139 |
+
<p id="p-37" num="37">An ordered list is a database structure associated with a queue table and maintained by the database. The ordered list indicates the order of retrieval for the rows of data stored in the queue table. In some systems, the ordered list is a simple linked list of pointers to the rows in the queue table. The list is linked together in the order in which the rows are to be retrieved. Any of several different algorithms can be selected to govern the order of retrieval when the queue table that the ordered list is associated with is created. Among the possible algorithms are: <part-num-ref name="possible algorithms are:">1)</part-num-ref>
|
| 140 |
+
returning the oldest data stored in the queue table, where calculating the age of the data is based on when the data was inserted into the queue table; <part-num-ref name="queue table;">2)</part-num-ref>
|
| 141 |
+
returning the oldest data stored in the queue table, where calculating the age of the data is based on a date provided with the data; and <part-num-ref name="data; and">3)</part-num-ref>
|
| 142 |
+
returning the data having the highest priority rating, where the priority rating is based on a information provided with the data (this may involve a calculation that was provided when the algorithm was selected). In some <boundary-data type="header">NCR Docket 11557.00 9</boundary-data>
|
| 143 |
+
<page-break num="10"/>
|
| 144 |
+
systems, the DBA selects default settings for all queue tables which include the order of retrieval. </p>
|
| 145 |
+
<p id="p-38" num="38">[32] Figure <confidence value="5">5</confidence>
|
| 146 |
+
A illustrates an operation for inserting data into a queue table and updating the ordered list associated with the queue table. In this example, the order of retrieval is based on when the data was inserted into the queue table e.g., the row of data that has been stored in the queue table for the longest period of time is first in the order of retrieval. </p>
|
| 147 |
+
<p id="p-39" num="39">[33] Upon receiving data for storage in a queue table (step 500), the database creates a row in the queue table (step <part-num-ref name="queue table (step">505)</part-num-ref>
|
| 148 |
+
and stores the data in that row (step 510). </p>
|
| 149 |
+
<p id="p-40" num="40">A record is then created in an ordered list associated with the queue table (step <part-num-ref name="queue table (step">515)</part-num-ref>
|
| 150 |
+
and a pointer to the row in the queue table is stored in the record (step 520). The record is added to the ordered list so that it is last in the ordered list (step 525). (It is possible that the record can be both last and first in the ordered list if the queue table has only one row of data.) The record is last in the ordered list because the data that it points to is the most recently stored data in the queue table. The record remains last in the ordered list until another record is added to the ordered list. As additional data is inserted into the queue table, the data associated with the record ages and becomes decreasingly recent. At some point, this data becomes the oldest data in the queue table and therefore will be first in the ordered list. Once the data is stored and the ordered list updated, an indication is sent to any query waiting for data to be inserted into this queue table (step 530). The indication causes the waiting or suspended query to resume execution. </p>
|
| 151 |
+
<p id="p-41" num="41">[34] Figure <confidence value="5">5</confidence>
|
| 152 |
+
B illustrates an operation for inserting data into a queue table and updating the ordered list associated with the queue table. In this case, the order of retrieval is based on a priority rating provided with the data. Upon receiving data for storage in a queue table (step 550), the database creates a row in the queue table (step <part-num-ref name="queue table (step">555)</part-num-ref>
|
| 153 |
+
and stores the data in that row (step 560). The priority rating is received (step <part-num-ref name="priority rating is received (step">565)</part-num-ref>
|
| 154 |
+
and stored with the data in the queue table (step 570). In some systems, the priority rating is stored separately from the data. In still other systems, the priority rating is stored in the ordered list. A record is then created in an ordered list associated with the queue table (step <part-num-ref name="queue table (step">575)</part-num-ref>
|
| 155 |
+
and a pointer to the row in the queue <boundary-data type="header">NCR Docket 11557.00 10</boundary-data>
|
| 156 |
+
<page-break num="11"/>
|
| 157 |
+
table is stored in the record (step 580). The record is inserted into the ordered list based on the priority ratings (step 585). Once the data and priority ratings are stored and the ordered list is updated, an indication is sent to any query waiting for data to be inserted into this queue table (step 590). The indication causes the waiting or suspended query to resume execution. </p>
|
| 158 |
+
<p id="p-42" num="42">[35] In some systems, a query command that targets a queue table will include an SQL "where" clause that places restrictions on the data to be returned. When a query of this type is received, the database examines the data in the queue table in the order specified by the ordered list associated with the queue table and returns at least a portion of the data from the first row found that satisfies the restrictions contained in the query. The row may not be the first row listed in the ordered list, but it will be the row closest to the first row in the ordered list that satisfies the query. If no data is found, the execution of the query is suspended until data satisfying the query is inserted into the queue table. In still other systems, when a query containing a "where" clause is received, the database uses one or more database indexes along with the ordered list to reduce the time needed to search for data in the queue table.</p>
|
| 159 |
+
<p id="p-43" num="43">[36] While the invention has been described with respect to a limited number of embodiments, those skilled in the art will appreciate that numerous modifications and variations of the invention exist. It is intended that the appended claims cover all such modifications and variations as fall within the true spirit and scope of the invention.</p>
|
| 160 |
+
<boundary-data type="header">NCR Docket 11557.00 11</boundary-data>
|
| 161 |
+
</description>
|
| 162 |
+
</us-patent-application>
|
| 163 |
+
|
prior_art/11242115.xml
ADDED
|
@@ -0,0 +1,69 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11242115</doc-number>
|
| 8 |
+
<date>2005-12-22</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">Dec-22-05 02:3<confidence value="5">1</confidence>
|
| 14 |
+
pm Fr<confidence value="5884">om-Q</confidence>
|
| 15 |
+
UALCO<confidence value="54">MI</confidence>
|
| 16 |
+
AF-210A 858-845-2550 T-115 P.003/004 F-9<confidence value="68">82</confidence>
|
| 17 |
+
</p>
|
| 18 |
+
<heading id="h-1">PATENT</heading>
|
| 19 |
+
<heading id="h-2">
|
| 20 |
+
<confidence value="255">(IN</confidence>
|
| 21 |
+
<confidence value="866">THE</confidence>
|
| 22 |
+
SPECIFICATION </heading>
|
| 23 |
+
<p id="p-2" num="2">Please amend the specification as shown below:</p>
|
| 24 |
+
<p id="p-3" num="3">[0001] The present Application for Patent claims priority to Provisional Ap<confidence value="5">p</confidence>
|
| 25 |
+
lication No. </p>
|
| 26 |
+
<p id="p-4" num="4">60/7<confidence value="882">10.</confidence>
|
| 27 |
+
366 entitled "PILOT AN<confidence value="5">D</confidence>
|
| 28 |
+
DATA TRANSMISSION IN A <confidence value="5">Q</confidence>
|
| 29 |
+
UASI-ORTHOGONAL SINGLE-CAR<confidence value="66">RI</confidence>
|
| 30 |
+
ER FRE<confidence value="8">Q</confidence>
|
| 31 |
+
UE<confidence value="8">N</confidence>
|
| 32 |
+
CY DIVISION MULTIPLE ACCESS SYSTEM" filed August <part-num-ref name="QUASI-ORTHOGONAL SINGLE-CARRIER FREQUENCY DIVISION MULTIPLE ACCESS SYSTEM" filed August">
|
| 33 |
+
<confidence value="886">22.</confidence>
|
| 34 |
+
</part-num-ref>
|
| 35 |
+
<confidence value="86686125">2005,1Pr</confidence>
|
| 36 |
+
ovisiona<confidence value="4">l</confidence>
|
| 37 |
+
Application No. <confidence value="5">6</confidence>
|
| 38 |
+
0/691,701 entitled "PILOT AND DATA </p>
|
| 39 |
+
<heading id="h-3">TRANSMISSION IN A QUASI-ORTHOGONAL SINGLE-CARRIER F<confidence value="8">R</confidence>
|
| 40 |
+
EQUENCY </heading>
|
| 41 |
+
<p id="p-5" num="5">D<confidence value="8">I</confidence>
|
| 42 |
+
VISION MULTIPLE ACCESS SYSTEM" filed June 16, 2005, and Provisional Application Serial No. 60/702,033 filed July 22, 2005 assigned to the assignee hereof and all hereby expressly incorporated by reference herein. </p>
|
| 43 |
+
<p id="p-6" num="6">Att<confidence value="8">o</confidence>
|
| 44 |
+
rney <confidence value="5">D</confidence>
|
| 45 |
+
ocket No.: 050717 Customer No.: <part-num-ref name="Customer No.:">23696</part-num-ref>
|
| 46 |
+
<part-num-ref name="">2</part-num-ref>
|
| 47 |
+
PAGE 314<confidence value="4885888">'RCYDAT</confidence>
|
| 48 |
+
<part-num-ref name="PAGE 314'RCYDAT">
|
| 49 |
+
<confidence value="8848848868">1212212005</confidence>
|
| 50 |
+
</part-num-ref>
|
| 51 |
+
<confidence value="5">5</confidence>
|
| 52 |
+
:40<confidence value="686">:47</confidence>
|
| 53 |
+
<confidence value="88">PM</confidence>
|
| 54 |
+
<confidence value="5">[</confidence>
|
| 55 |
+
Easte<confidence value="66">rn</confidence>
|
| 56 |
+
Standard Time]' <confidence value="86">SV</confidence>
|
| 57 |
+
R:USPT<confidence value="52">O-</confidence>
|
| 58 |
+
EFXRF<confidence value="25862">.I27*</confidence>
|
| 59 |
+
DNIS<confidence value="684">:21</confidence>
|
| 60 |
+
38300' <confidence value="5">C</confidence>
|
| 61 |
+
SID<confidence value="5">:</confidence>
|
| 62 |
+
858 <part-num-ref name="5:40:47 PM [Eastern Standard Time]' SVR:USPTO-EFXRF.I27* DNIS:2138300' CSID:858">845</part-num-ref>
|
| 63 |
+
<confidence value="88688">2550'</confidence>
|
| 64 |
+
DURAT<confidence value="668">ION</confidence>
|
| 65 |
+
(mm<confidence value="2886688488">-ss):00.56</confidence>
|
| 66 |
+
</p>
|
| 67 |
+
</description>
|
| 68 |
+
</us-patent-application>
|
| 69 |
+
|
prior_art/11242678.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>11242678</doc-number>
|
| 8 |
+
<date>2010-02-16</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="8887">Appl</confidence>
|
| 15 |
+
e. No.: <confidence value="665">11/</confidence>
|
| 16 |
+
242,678 <confidence value="2222">Amdt</confidence>
|
| 17 |
+
. Da<confidence value="8">t</confidence>
|
| 18 |
+
e: February 16, 2010 Filing Date: February <part-num-ref name="Filing Date: February">3,</part-num-ref>
|
| 19 |
+
<part-num-ref name="Filing Date: February 3,">2010</part-num-ref>
|
| 20 |
+
Amendments to the S<confidence value="5">p</confidence>
|
| 21 |
+
ecification In the specification, please amendment paragraph [0015] as indicated below: </p>
|
| 22 |
+
<p id="p-2" num="2">
|
| 23 |
+
<confidence value="4">[</confidence>
|
| 24 |
+
0015<confidence value="5">]</confidence>
|
| 25 |
+
The present invention provides the ability to take a snapshot of a system, securely store the image and re-image the system back to the original state. An auto discovery mechanism provides a list of machines that can be used as targets<confidence value="5">.</confidence>
|
| 26 |
+
A security server checks the security policy for each potential system and prevents those with no or limited availability or those with security issues from being used by the provisioning system. The remaining machines after the auto discovery and security check are put in i<confidence value="85141">s-mif</confidence>
|
| 27 |
+
a pool of target machines that can be imaged, used for load balance issues, and re-imaged when load balancin<confidence value="8">g</confidence>
|
| 28 |
+
tasks on those tar<confidence value="8">g</confidence>
|
| 29 |
+
et machines are complete. </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/11247464.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
prior_art/11262122.xml
ADDED
|
@@ -0,0 +1,26 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11262122</doc-number>
|
| 8 |
+
<date>2006-12-21</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:</p>
|
| 14 |
+
<p id="p-2" num="2">Please insert the following as the first paragraph beneath the title on page 1:</p>
|
| 15 |
+
<p id="p-3" num="3">
|
| 16 |
+
<confidence value="5">-</confidence>
|
| 17 |
+
-This application claims benefit of U.S. Provisional Application No. 60/623,346, filed on October 29, 2004, U.S. Provisional Application No. 60/651,372, filed on February 9, 2005, U.S. </p>
|
| 18 |
+
<p id="p-4" num="4">Provisional Application No. 60/651<confidence value="5">,</confidence>
|
| 19 |
+
535 filed on February 9, 2005, and U.S. Provisional Application No. 60/723,901 filed on October 5, 2005, which in their entirety are herein incorporated by reference.-<confidence value="5">-</confidence>
|
| 20 |
+
Please replace the abstract with the replacement abstract herein provided on the following separate sheet. </p>
|
| 21 |
+
<p id="p-5" num="5">
|
| 22 |
+
<confidence value="8">-</confidence>
|
| 23 |
+
2 - </p>
|
| 24 |
+
</description>
|
| 25 |
+
</us-patent-application>
|
| 26 |
+
|
prior_art/11264679.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>11264679</doc-number>
|
| 8 |
+
<date>2011-06-07</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/264,679 Docket No.: V0196.0010 Amendment dated June 7, 2011 Reply to Office Action of December <part-num-ref name="Reply to Office Action of December">8,</part-num-ref>
|
| 14 |
+
<part-num-ref name="Reply to Office Action of December 8,">2010</part-num-ref>
|
| 15 |
+
</p>
|
| 16 |
+
<heading id="h-1">AMENDMENTS TO THE TITLE</heading>
|
| 17 |
+
<p id="p-2" num="2">Please amend the title as follows to correct for an obvious typographic error:</p>
|
| 18 |
+
<p id="p-3" num="3">Method for <confidence value="222222222222222">au*thematieally</confidence>
|
| 19 |
+
automatically setting up and/or controlling a telecommunication conference <part-num-ref name="telecommunication conference">
|
| 20 |
+
<confidence value="8">2</confidence>
|
| 21 |
+
</part-num-ref>
|
| 22 |
+
</p>
|
| 23 |
+
</description>
|
| 24 |
+
</us-patent-application>
|
| 25 |
+
|
prior_art/11270795.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>11270795</doc-number>
|
| 8 |
+
<date>2008-07-29</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">ATTORNEY DOCKET NO. PATENT APPLICATION</boundary-data>
|
| 14 |
+
<boundary-data type="header">063170.8172 USSN 11/270,795</boundary-data>
|
| 15 |
+
<boundary-data type="header">
|
| 16 |
+
<confidence value="8">2</confidence>
|
| 17 |
+
</boundary-data>
|
| 18 |
+
<p id="p-1" num="1">In the Specification Please amend the Cross-Reference paragraph on page <part-num-ref name="Cross-Reference paragraph on page">1</part-num-ref>
|
| 19 |
+
to read as follows: </p>
|
| 20 |
+
<p id="p-2" num="2">This application is being filed concurrently with the following applications, which are incorporated herein by reference: "Method and System for Configuring a Supplemental Directory," having a serial number of <confidence value="66686666">11/270,7</confidence>
|
| 21 |
+
94, and an attorney docket number of 063170.8171; "Method and System for Improving Write Performance in a Supplemental Directory," having a serial number of <confidence value="66668666">11/270,8</confidence>
|
| 22 |
+
96, and an attorney docket number of 063170.8173; "Method and System for Providing a Directory Overlay," having a serial number of <confidence value="6666866">11/270,</confidence>
|
| 23 |
+
793, and an attorney docket number of 063170.8174; "Method and System for Automatic Registration of Attribute Types," having a serial number of <confidence value="66668666">11/270,3</confidence>
|
| 24 |
+
20, and an attorney docket number of 063170.8203; "System and Method for Routing Directory Service Operations in a Directory Service Network," having a serial number of <confidence value="6666686">11/269,</confidence>
|
| 25 |
+
551, and an attorney docket number of 019232-0316613; </p>
|
| 26 |
+
<p id="p-3" num="3">"System and Method for Efficient Directory Performance Using Non-Persistent Storage," having a serial number of <confidence value="6666686">11/269,</confidence>
|
| 27 |
+
637, and an attorney docket number of 019232- 0316610; "System and Method for Providing a Directory Service Network," having a serial number of <confidence value="1">_</confidence>
|
| 28 |
+
<confidence value="666668668">11/269,63</confidence>
|
| 29 |
+
8, and an attorney docket number of 019232-0316611; and "System and Method for Writing Data to a Directory," having a serial number of <confidence value="6668866688">11/270,188</confidence>
|
| 30 |
+
, and an attorney docket number of 063170.3119. </p>
|
| 31 |
+
<p id="p-4" num="4">Please amend the paragraph beginning at Page <part-num-ref name="paragraph beginning at Page">24,</part-num-ref>
|
| 32 |
+
Line <part-num-ref name="paragraph beginning at Page 24, Line">21</part-num-ref>
|
| 33 |
+
through Page <part-num-ref name="through Page">26,</part-num-ref>
|
| 34 |
+
Line <part-num-ref name="through Page 26, Line">8,</part-num-ref>
|
| 35 |
+
as follows: </p>
|
| 36 |
+
<p id="p-5" num="5">FIGURE 11 is a block diagram illustrating an alternative embodiment, showing a directory system <part-num-ref name="directory system">400.</part-num-ref>
|
| 37 |
+
Directory system <part-num-ref name="directory system 400. Directory system">400</part-num-ref>
|
| 38 |
+
includes a reference directory <part-num-ref name="reference directory">404</part-num-ref>
|
| 39 |
+
as well as a supplemental directory <part-num-ref name="supplemental directory">414,</part-num-ref>
|
| 40 |
+
similar to the supplemental directory and reference directory described above. Further, system <part-num-ref name="supplemental directory and reference directory described above. Further, system">400</part-num-ref>
|
| 41 |
+
includes a persistent information store <part-num-ref name="persistent information store">410</part-num-ref>
|
| 42 |
+
associated with reference directory <part-num-ref name="associated with reference directory">404.</part-num-ref>
|
| 43 |
+
However, in this embodiment, supplemental directory <part-num-ref name="associated with reference directory 404. However, in this embodiment, supplemental directory">414</part-num-ref>
|
| 44 |
+
includes a non-persistent information store <part-num-ref name="non-persistent information store">415.</part-num-ref>
|
| 45 |
+
Non-persistent information store <part-num-ref name="non-persistent information store 415. Non-persistent information store">415</part-num-ref>
|
| 46 |
+
may be an alternate evaluator as disclosed in corresponding applications which are incorporated herein by reference: "Method and Apparatus for Enhancing Directory Performance," having a <boundary-data type="header">DAL<confidence value="4">0</confidence>
|
| 47 |
+
1:1010717.1 </boundary-data>
|
| 48 |
+
<page-break num="2"/>
|
| 49 |
+
<boundary-data type="header">ATTORNEY DOCKET NO. PATENT APPLICATION</boundary-data>
|
| 50 |
+
<boundary-data type="header">063170.8172 USSN 11/270,795</boundary-data>
|
| 51 |
+
<boundary-data type="header">
|
| 52 |
+
<confidence value="8">3</confidence>
|
| 53 |
+
</boundary-data>
|
| 54 |
+
serial number of 11/134,047, filed 5/20/05, and having an attorney docket number of 063170.6309; "Method and Apparatus of Optimising Directory Performance," having a serial number of 11/134,143, filed 5/20/05, and having an attorney docket number of 063170.6340; </p>
|
| 55 |
+
<p id="p-6" num="6">"Method and Apparatus for Handling Directory Operations," having a serial number of 11/134,251, filed 5/20/05, and having an attorney docket number of 063170.6582; "Method and Apparatus for Loading Data into an Alternate Evaluator for Directory Operations," having a serial number of 11/134,043, filed 5/20/05, and having an attorney docket number of 063170.6311; "Structure of an Alternate Evaluator for Directory Operations," having a serial number of 11/134,237, filed 5/20/05, and having an attorney docket number of 063170.6583;</p>
|
| 56 |
+
<p id="p-7" num="7">"Method of Selecting a Processor for Query Evaluation," having a serial number of 11/134,070, filed 5/20/05, and having an attorney docket number of 063170.6306; "Dynamic Management of Indexes for an Alternate Evaluator," having a serial number of 60/722,729, filed 9/30/05, and having an attorney docket number of 063170.8215; "Dynamic Creation of Indexes for an Alternate Evaluator," having a serial number of 60/722,917, filed 9/30/05, and having an attorney docket number of 063170.8227; or a directory as disclosed in "System and Method for Routing Directory Service Operations in a Directory Service Network," having a serial number of 11/269,551, and an attorney docket number of 019232-0316613;</p>
|
| 57 |
+
<p id="p-8" num="8">"System and Method for Efficient Directory Performance Using Non-Persistent Storage," having a serial number of <confidence value="6668686">11/269,</confidence>
|
| 58 |
+
637, and an attorney docket number of 019232- 0316610; "System and Method for Providing a Directory Service Network," having a serial number of <confidence value="66666666666">11/269,638,</confidence>
|
| 59 |
+
and an attorney docket number of 019232-0316611; and "System and Method for Writing Data to a Directory," having a serial number of <confidence value="66668686668">11/270,188,</confidence>
|
| 60 |
+
and an attorney docket number of 063170.3119, which are incorporated herein by reference. </p>
|
| 61 |
+
<p id="p-9" num="9">In addition, a persistent information store <part-num-ref name="persistent information store">416</part-num-ref>
|
| 62 |
+
is associated with supplemental directory <part-num-ref name="is associated with supplemental directory">414.</part-num-ref>
|
| 63 |
+
</p>
|
| 64 |
+
<boundary-data type="header">DAL<confidence value="4">0</confidence>
|
| 65 |
+
1:1010717.1 </boundary-data>
|
| 66 |
+
</description>
|
| 67 |
+
</us-patent-application>
|
| 68 |
+
|
prior_art/11275739.xml
ADDED
|
@@ -0,0 +1,891 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11275739</doc-number>
|
| 8 |
+
<date>2006-01-26</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">STACK MAGAZINE SYSTEM</heading>
|
| 14 |
+
<heading id="h-2">BACKGROUND</heading>
|
| 15 |
+
<p id="p-1" num="1">
|
| 16 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 17 |
+
The present invention generally relates to bodily fluid sampling devices and more specifically, but not exclusively, concerns a dispenser system for dispensing test elements that test biological fluid. </p>
|
| 18 |
+
<p id="p-2" num="2">The acquisition and testing of bodily fluids is useful for many purposes and continues to grow in importance for use in medical diagnosis and treatment, such as <boundary-data type="line-number">10 </boundary-data>
|
| 19 |
+
for diabetes, and in other diverse applications. In the medical field, it is desirable for lay operators to perform tests routinely, quickly, and reproducibly outside of a laboratory setting, with rapid results and a readout of the resulting test information. </p>
|
| 20 |
+
<p id="p-3" num="3">Testing can be performed on various bodily fluids and, for certain applications, is particularly related to the testing of blood and/or interstitial fluid. Performing home- <boundary-data type="line-number">15 </boundary-data>
|
| 21 |
+
based testing can be difficult for many patients, especially for patients with limited hand dexterity, such as the elderly or diabetics. For example, diabetics can sometimes experience numbness or tingling in their extremities, such as their hands, which can make self<confidence value="5">-</confidence>
|
| 22 |
+
testing difficult because they are unable to accurately position a test strip to collect the blood sample. In addition, wounds for diabetics tend to heal more slowly, <boundary-data type="line-number">20 </boundary-data>
|
| 23 |
+
and as a result, there is a desire to make incisions less invasive. </p>
|
| 24 |
+
<p id="p-4" num="4">Recently, lancet integrated test strips or elements have been developed in which a test strip is integrated with a lancet or other piercing means so as to form a single disposable unit. While these integrated units have somewhat simplified the collection and testing of fluid samples, there are still a number of issues that need to <boundary-data type="line-number">25 </boundary-data>
|
| 25 |
+
be resolved before a commercial unit can be implemented. One issue concerns maintaining the sterility of the lancet prior to use so as to minimize the risk of infection. Another issue concerns the disposal of used units after use. Once used, the integrated units become a biohazard that need to be disposed of in a safe manner. A number of different types of systems have been proposed for dispensing test strips, <boundary-data type="line-number">30 </boundary-data>
|
| 26 |
+
lancets, or some combination thereof, but most of these systems have significant drawbacks. </p>
|
| 27 |
+
<p id="p-5" num="5">Multiple use test systems like drums, discs, and reel-to-reel tapes have been developed to house multiple test strips, but these systems fail to address a number of <boundary-data type="header">
|
| 28 |
+
<confidence value="5">W</confidence>
|
| 29 |
+
P 23465 US<confidence value="5">/</confidence>
|
| 30 |
+
7404-744 CPS:375701 1 </boundary-data>
|
| 31 |
+
<page-break num="2"/>
|
| 32 |
+
issues. For example, reel-to-reel cassette systems typically bend a tape of lancet integrated test elements during dispensing, which can result in damage to the lancet and/or the test strip. Other cassette or cartridges are bulky in nature, which makes them commercially impractical for household or other routine use. Still yet other <boundary-data type="line-number">5 </boundary-data>
|
| 33 |
+
systems require the use of a complicated indexing mechanism, which tends to make the systems have an unsuitable reliability due to jamming and/or other complications. </p>
|
| 34 |
+
<p id="p-6" num="6">Typically, such systems also require specially designed test elements that are not configured for current single use test strips. Drum transport systems have been proposed for transporting test strips from a magazine, but such drum transport <boundary-data type="line-number">10 </boundary-data>
|
| 35 |
+
systems have failed to satisfactorily address the disposal issue regarding the used test strips. </p>
|
| 36 |
+
<p id="p-7" num="7">With portable meters, such as portable blood glucose meters, small meter sizes and ease of handling are desirable features. Most users would prefer smaller meters that are able to discretely fit inside a pocket or a purse so that the user is able to <boundary-data type="line-number">15 </boundary-data>
|
| 37 |
+
perform testing in any situation, such as in a restaurant bathroom or when traveling. </p>
|
| 38 |
+
<p id="p-8" num="8">One factor affecting size of meters that handle multiple test strips is storage compartment sizes. In previous designs, the storage compartments tended to be rather large and bulky because test elements were stored in a disorderly fashion.</p>
|
| 39 |
+
<p id="p-9" num="9">Thus, needs remain for further contributions in this area of technology.</p>
|
| 40 |
+
<boundary-data type="header">
|
| 41 |
+
<confidence value="5">W</confidence>
|
| 42 |
+
P 23465 US<confidence value="5">/</confidence>
|
| 43 |
+
7404-744 CPS:375701 2 </boundary-data>
|
| 44 |
+
<heading id="h-3">SUMMARY</heading>
|
| 45 |
+
<p id="p-10" num="10">
|
| 46 |
+
<page-break num="3"/>
|
| 47 |
+
One aspect concerns a meter system that includes a supply magazine that stores a plurality of lancet integrated test elements in a stacked manner. The lancet integrated test elements each include a test strip for testing a body fluid sample and a <boundary-data type="line-number">5 </boundary-data>
|
| 48 |
+
lancet. The test strip is generally flat, and the test strip has a sample opening at one end and opposing side edges. The lancet is coupled to the test strip for forming an incision where the body fluid sample is drawn. The lancet is configured to extend proximal the sample opening. A meter has a connector portion configured to operatively couple to the lancet integrated. The meter is configured to fire the lancets <boundary-data type="line-number">10 </boundary-data>
|
| 49 |
+
on the lancet integrated test elements. A transport mechanism is configured to transfer the lancet integrated test elements to the connector portion of the meter. The transport mechanism is configured to engage at least one of the side edges to minimize risk of damaging the test strip and lancet proximal the sample opening of the lancet integrated test element. </p>
|
| 50 |
+
<p id="p-11" num="11">
|
| 51 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 52 |
+
Another aspect concerns a system that includes a supply magazine configured to store test elements in a stacked manner prior to use. The test elements are configured to analyze body fluid. A waste magazine is configured to store the test elements in a stacked manner after use. A transport drum is disposed between the supply magazine and the waste magazine to transport the test elements from the <boundary-data type="line-number">20 </boundary-data>
|
| 53 |
+
supply magazine to the waste magazine. </p>
|
| 54 |
+
<p id="p-12" num="12">Still yet another aspect concerns a system that includes a supply magazine configured to store a stack of test elements. A meter includes a connector configured to connect to the test elements. A transport system is configured to transport test elements from the supply magazine to the connector of the meter. The transport <boundary-data type="line-number">25 </boundary-data>
|
| 55 |
+
system includes a disc-shaped transport member configured to receive at least one of the test elements from the magazine. The disc-shaped transport member is rotatable relative to the meter to transport the at least one of the test elements to the connector. </p>
|
| 56 |
+
<p id="p-13" num="13">Further forms, objects, features, aspects, benefits, advantages, and embodiments of the present invention will become apparent from a detailed <part-num-ref name="detailed">30</part-num-ref>
|
| 57 |
+
description and drawings provided herewith. </p>
|
| 58 |
+
<boundary-data type="header">
|
| 59 |
+
<confidence value="5">W</confidence>
|
| 60 |
+
P 23465 US<confidence value="5">/</confidence>
|
| 61 |
+
7404-744 CPS:375701 3 </boundary-data>
|
| 62 |
+
<heading id="h-4">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 63 |
+
<p id="p-14" num="14">
|
| 64 |
+
<page-break num="4"/>
|
| 65 |
+
FIG. 1 is a front view of a meter system according to one embodiment. </p>
|
| 66 |
+
<p id="p-15" num="15">FIG. 2 is a first top view of the FIG. 1 meter system with a transport shuttle in a loading position.</p>
|
| 67 |
+
<p id="p-16" num="16">
|
| 68 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 69 |
+
FIG. 3 is a second top view of the FIG. 1 meter system with the transport shuttle in an unloading position. </p>
|
| 70 |
+
<p id="p-17" num="17">FIG. 4 is a top view of a lancet integrated test element loaded on a meter of the FIG. 1 system.</p>
|
| 71 |
+
<p id="p-18" num="18">FIG. 5 is a perspective view of a meter system according to another <boundary-data type="line-number">10 </boundary-data>
|
| 72 |
+
embodiment. </p>
|
| 73 |
+
<p id="p-19" num="19">FIG. 6 is a perspective view of a transport drum of the FIG. 5 system.</p>
|
| 74 |
+
<p id="p-20" num="20">FIG. 7 is a diagrammatic view of a test element being loaded on the FIG. 6 drum.</p>
|
| 75 |
+
<p id="p-21" num="21">FIG. 8 is a top view of the FIG. 7 test element loaded on the FIG. 6 drum.</p>
|
| 76 |
+
<p id="p-22" num="22">
|
| 77 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 78 |
+
FIG. 9 is a cross-sectional view of the FIG. 7 test element loaded on the FIG. 6 drum. </p>
|
| 79 |
+
<p id="p-23" num="23">FIG. 10 is a perspective view of a waste magazine for the FIG. 5 system.</p>
|
| 80 |
+
<p id="p-24" num="24">FIG. 11 is a partial cross-sectional view of the FIG. 7 test element being loaded into the FIG. 10 waste magazine.</p>
|
| 81 |
+
<p id="p-25" num="25">
|
| 82 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 83 |
+
FIG. 12 is a perspective view of a meter system according to a further embodiment. </p>
|
| 84 |
+
<p id="p-26" num="26">FIG. 13 is a perspective view of a magazine for the FIG. 12 meter system.</p>
|
| 85 |
+
<p id="p-27" num="27">FIG. 14 is a top view of the FIG. 12 meter system with its transport disc removed.</p>
|
| 86 |
+
<p id="p-28" num="28">
|
| 87 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 88 |
+
FIG. 15 is a top view of the transport disc for the FIG. 12 meter system. </p>
|
| 89 |
+
<p id="p-29" num="29">FIG. 16 is an exploded view of the FIG. 15 transport disc.</p>
|
| 90 |
+
<p id="p-30" num="30">FIG. 17 is an enlarged view of a test element being loaded onto the FIG. 15 transport disc.</p>
|
| 91 |
+
<boundary-data type="header">
|
| 92 |
+
<confidence value="5">W</confidence>
|
| 93 |
+
P 23465 US<confidence value="5">/</confidence>
|
| 94 |
+
7404-744 CPS:375701 4 </boundary-data>
|
| 95 |
+
<heading id="h-5">DESCRIPTION OF THE SELECTED EMBODIMENTS</heading>
|
| 96 |
+
<p id="p-31" num="31">
|
| 97 |
+
<page-break num="5"/>
|
| 98 |
+
For the purposes of promoting an understanding of the principles of the invention, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be <boundary-data type="line-number">5 </boundary-data>
|
| 99 |
+
understood that no limitation of the scope of the invention is thereby intended, such alterations and further modifications in the illustrated device, and such further applications of the principles of the invention as illustrated therein being contemplated as would normally occur to one skilled in the art to which the invention relates. A number of embodiments of the invention are shown in detail; although it <boundary-data type="line-number">10 </boundary-data>
|
| 100 |
+
will be apparent to those skilled in the relevant art that some features that are not relevant to the present invention may not be shown for the sake of clarity. It should be noted that directional terms, such as "up", "down<confidence value="5">"</confidence>
|
| 101 |
+
, "top<confidence value="5">"</confidence>
|
| 102 |
+
and "bottom", are used herein solely for the convenience of the reader in order to aid in the reader's understanding of the illustrated embodiments, and it is not the intent that the use of <boundary-data type="line-number">15 </boundary-data>
|
| 103 |
+
these directional terms in any manner limit the described, illustrated, and/or claimed features to a specific direction or orientation. </p>
|
| 104 |
+
<p id="p-32" num="32">As mentioned previously, there have been a number of drawbacks to prior cartridge or cassette designs, especially with respect to lancet integrated test elements (LITs). For example, some cassette systems bend a tape of LITs during dispensing, <boundary-data type="line-number">20 </boundary-data>
|
| 105 |
+
which can result in damage to the lancet and/or the test strip. Other cassette or cartridges are bulky in nature, which makes them commercially impractical for household or other routine use. Still yet other systems require the use of a complicated indexing mechanism, which tends to make the systems have unsuitable reliability due to jamming and/or other problems. Typically, such systems also <boundary-data type="line-number">25 </boundary-data>
|
| 106 |
+
require specially designed test elements that are not configured for current single use test strips. Moreover, disposal of hazardous, used LITs is always a concern. </p>
|
| 107 |
+
<p id="p-33" num="33">The meter system according to a number of aspects of the present invention addresses these as well as many other concerns. A meter system for analyzing body fluids includes a supply magazine for storing a stack of test elements, a meter for <boundary-data type="line-number">30 </boundary-data>
|
| 108 |
+
analyzing fluid samples, and a transport system for transporting test elements from the supply magazine to the meter. In a number of embodiments, the transport system is configured to minimize damage to the test elements as well as to promote fluid <boundary-data type="header">
|
| 109 |
+
<confidence value="5">W</confidence>
|
| 110 |
+
P 23465 US<confidence value="5">/</confidence>
|
| 111 |
+
7404-744 CPS:375701 5 </boundary-data>
|
| 112 |
+
<page-break num="6"/>
|
| 113 |
+
collection by grabbing the side edges of the test elements. Moreover, the transport systems limit the number of components used, which improves reliability as well as provides a compact design. The stack cartridge design allows for the use of preexisting single use test elements in a multi-use design. In one form, the transport <boundary-data type="line-number">5 </boundary-data>
|
| 114 |
+
system includes a shuttle that slides the top-most test element from the stack onto a connection portion of the meter. In another form, the transport system includes a drum that rotates to transport test elements from the supply magazine to a testing position and, once used, to a waste magazine for disposal. This allows used LITs to be disposed of safely. In a further form, the transport system includes a disc that <boundary-data type="line-number">10 </boundary-data>
|
| 115 |
+
rotates to transport the test elements. The disc-shaped transport system provides a compact and highly reliable design. </p>
|
| 116 |
+
<p id="p-34" num="34">A meter transport system 30 according to one embodiment, among many, is depicted in FIGS. 1, <part-num-ref name="according to one embodiment, among many, is depicted in FIGS. 1,">2,</part-num-ref>
|
| 117 |
+
<part-num-ref name="according to one embodiment, among many, is depicted in FIGS. 1, 2,">3</part-num-ref>
|
| 118 |
+
and <part-num-ref name="and">4.</part-num-ref>
|
| 119 |
+
As shown in FIG. 1, the system <part-num-ref name="system">30</part-num-ref>
|
| 120 |
+
includes a meter <part-num-ref name="meter">32,</part-num-ref>
|
| 121 |
+
a magazine <part-num-ref name="magazine">34</part-num-ref>
|
| 122 |
+
that contains a stack of test elements <part-num-ref name="stack of test elements">36,</part-num-ref>
|
| 123 |
+
and a transfer or transport <boundary-data type="line-number">15 </boundary-data>
|
| 124 |
+
mechanism <part-num-ref name="transfer or transport mechanism">38</part-num-ref>
|
| 125 |
+
that transports the test elements <part-num-ref name="test elements">36</part-num-ref>
|
| 126 |
+
from the magazine <part-num-ref name="magazine">34</part-num-ref>
|
| 127 |
+
to the meter <part-num-ref name="meter">32.</part-num-ref>
|
| 128 |
+
In the illustrated embodiment, the test elements <part-num-ref name="test elements">36</part-num-ref>
|
| 129 |
+
include LITs that each include a lancet and a test strip. LITs are configured to lance an incision in tissue and analyze a body fluid sample from the incision. For further information regarding the LITs, reference is made to U.S. Patent Application No. 11/070,502, filed March <part-num-ref name="LITs, reference is made to U.S. Patent Application No. 11/070,502, filed March">2,</part-num-ref>
|
| 130 |
+
<part-num-ref name="LITs, reference is made to U.S. Patent Application No. 11/070,502, filed March 2,">2005,</part-num-ref>
|
| 131 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 132 |
+
which is incorporated by reference in its entirety. Nevertheless, the test element <part-num-ref name="test element">36</part-num-ref>
|
| 133 |
+
in other embodiments can include other types of test elements, such as simple test strips that do not have any type of lancet or needle. The test elements <part-num-ref name="test elements">36</part-num-ref>
|
| 134 |
+
in the embodiment shown analyze fluid samples electrochemically, and the meter <part-num-ref name="meter">32</part-num-ref>
|
| 135 |
+
is configured to analyze the signals from the test elements <part-num-ref name="test elements">36</part-num-ref>
|
| 136 |
+
so as to provide test results via a display <boundary-data type="line-number">25 </boundary-data>
|
| 137 |
+
or some other type of output device. However, in other embodiments, the test elements <part-num-ref name="test elements">36</part-num-ref>
|
| 138 |
+
and meter <part-num-ref name="and meter">32</part-num-ref>
|
| 139 |
+
can analyze fluid samples in other manners, such as optically. </p>
|
| 140 |
+
<p id="p-35" num="35">Inside, the magazine <part-num-ref name="magazine">34</part-num-ref>
|
| 141 |
+
includes a molded desiccant <part-num-ref name="molded desiccant">40</part-num-ref>
|
| 142 |
+
for maintaining low humidity levels within the magazine <part-num-ref name="magazine">34</part-num-ref>
|
| 143 |
+
and a spring <part-num-ref name="spring">42</part-num-ref>
|
| 144 |
+
that is configured to bias the <boundary-data type="line-number">30 </boundary-data>
|
| 145 |
+
test elements <part-num-ref name="test elements">36</part-num-ref>
|
| 146 |
+
through an outlet opening of the magazine <part-num-ref name="magazine">34</part-num-ref>
|
| 147 |
+
into the transport mechanism <part-num-ref name="transport mechanism">38.</part-num-ref>
|
| 148 |
+
In one form, the spring <part-num-ref name="spring">42</part-num-ref>
|
| 149 |
+
includes a coil spring, but it should be understood that the spring <part-num-ref name="spring">42</part-num-ref>
|
| 150 |
+
can include other types of biasing devices. To further <boundary-data type="header">
|
| 151 |
+
<confidence value="5">W</confidence>
|
| 152 |
+
P 23465 US<confidence value="5">/</confidence>
|
| 153 |
+
7404-744 CPS:375701 6 </boundary-data>
|
| 154 |
+
<page-break num="7"/>
|
| 155 |
+
maintain acceptable humidity levels for the test elements <part-num-ref name="test elements">36</part-num-ref>
|
| 156 |
+
within the magazine <part-num-ref name="magazine">34,</part-num-ref>
|
| 157 |
+
the magazine has a moisture seal <part-num-ref name="moisture seal">46</part-num-ref>
|
| 158 |
+
that seals the outlet opening <part-num-ref name="outlet opening">44,</part-num-ref>
|
| 159 |
+
and the moisture seal <part-num-ref name="moisture seal">46</part-num-ref>
|
| 160 |
+
is removed prior to use. </p>
|
| 161 |
+
<p id="p-36" num="36">Referring to FIG. 2, the transport mechanism <part-num-ref name="transport mechanism">38</part-num-ref>
|
| 162 |
+
includes a transport member <boundary-data type="line-number">5 </boundary-data>
|
| 163 |
+
or shuttle <part-num-ref name="transport member or shuttle">48</part-num-ref>
|
| 164 |
+
with a test element opening <part-num-ref name="test element opening">50</part-num-ref>
|
| 165 |
+
in which the test elements <part-num-ref name="test elements">36</part-num-ref>
|
| 166 |
+
are received. The shuttle <part-num-ref name="shuttle">48</part-num-ref>
|
| 167 |
+
in one embodiment is slidably coupled to the meter <part-num-ref name="meter">32.</part-num-ref>
|
| 168 |
+
In another embodiment, the shuttle <part-num-ref name="shuttle">48</part-num-ref>
|
| 169 |
+
is slidably coupled to the magazine <part-num-ref name="magazine">34,</part-num-ref>
|
| 170 |
+
and in further embodiments, the shuttle <part-num-ref name="shuttle">48</part-num-ref>
|
| 171 |
+
is slidably coupled to both the meter <part-num-ref name="meter">32</part-num-ref>
|
| 172 |
+
and the magazine <part-num-ref name="magazine">34.</part-num-ref>
|
| 173 |
+
The transport mechanism <part-num-ref name="transport mechanism">38</part-num-ref>
|
| 174 |
+
further includes a stabilizer arm <part-num-ref name="stabilizer arm">52</part-num-ref>
|
| 175 |
+
with a <boundary-data type="line-number">10 </boundary-data>
|
| 176 |
+
contact member <part-num-ref name="contact member">54</part-num-ref>
|
| 177 |
+
(FIG. <part-num-ref name="(FIG.">1)</part-num-ref>
|
| 178 |
+
that contacts the test element <part-num-ref name="test element">36</part-num-ref>
|
| 179 |
+
when positioned within the test element opening <part-num-ref name="test element opening">50</part-num-ref>
|
| 180 |
+
of the shuttle <part-num-ref name="shuttle">48.</part-num-ref>
|
| 181 |
+
In the illustrated embodiment, the stabilizer arm <part-num-ref name="stabilizer arm">52</part-num-ref>
|
| 182 |
+
acts like a spring when pressing against the test element <part-num-ref name="test element">36.</part-num-ref>
|
| 183 |
+
In one form, the stabilizer arm <part-num-ref name="stabilizer arm">52</part-num-ref>
|
| 184 |
+
includes a leaf spring, but it should be recognized that the stabilizer arm <part-num-ref name="stabilizer arm">52</part-num-ref>
|
| 185 |
+
can include other types of biasing devices. The stabilizer arm <part-num-ref name="stabilizer arm">52</part-num-ref>
|
| 186 |
+
is <boundary-data type="line-number">15 </boundary-data>
|
| 187 |
+
configured to hold the test elements <part-num-ref name="test elements">36</part-num-ref>
|
| 188 |
+
within the test element opening <part-num-ref name="test element opening">50.</part-num-ref>
|
| 189 |
+
In particular, the stabilizer arm <part-num-ref name="stabilizer arm">52</part-num-ref>
|
| 190 |
+
applies a force to the test element <part-num-ref name="test element">36</part-num-ref>
|
| 191 |
+
that is less than the force the spring <part-num-ref name="spring">42</part-num-ref>
|
| 192 |
+
applies to the test elements <part-num-ref name="test elements">36</part-num-ref>
|
| 193 |
+
within the magazine <part-num-ref name="magazine">34</part-num-ref>
|
| 194 |
+
so that the magazine <part-num-ref name="magazine">34</part-num-ref>
|
| 195 |
+
is able to feed test elements <part-num-ref name="is able to feed test elements">36</part-num-ref>
|
| 196 |
+
into the test element opening <part-num-ref name="test element opening">50</part-num-ref>
|
| 197 |
+
of the shuttle <part-num-ref name="shuttle">48.</part-num-ref>
|
| 198 |
+
</p>
|
| 199 |
+
<p id="p-37" num="37">
|
| 200 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 201 |
+
Once the test element <part-num-ref name="test element">36</part-num-ref>
|
| 202 |
+
is loaded, the shuttle <part-num-ref name="shuttle">48</part-num-ref>
|
| 203 |
+
slides in a loading direction towards the meter <part-num-ref name="meter">32,</part-num-ref>
|
| 204 |
+
as is indicated by arrow <part-num-ref name="meter 32, as is indicated by arrow">56</part-num-ref>
|
| 205 |
+
in FIG. 2. The motive force from the shuttle <part-num-ref name="shuttle">48</part-num-ref>
|
| 206 |
+
is applied to the side edges of the test element <part-num-ref name="test element">36,</part-num-ref>
|
| 207 |
+
which tends to minimize the risk of damage. In one form, the user manually moves the shuttle <part-num-ref name="shuttle">48,</part-num-ref>
|
| 208 |
+
and in another form, the meter <part-num-ref name="meter">32</part-num-ref>
|
| 209 |
+
automatically moves the shuttle <part-num-ref name="shuttle">48</part-num-ref>
|
| 210 |
+
with a motor or <boundary-data type="line-number">25 </boundary-data>
|
| 211 |
+
other movement imparting device. The meter <part-num-ref name="meter">32</part-num-ref>
|
| 212 |
+
has a load cavity <part-num-ref name="load cavity">58</part-num-ref>
|
| 213 |
+
in which the test element <part-num-ref name="test element">36</part-num-ref>
|
| 214 |
+
is loaded. In the illustrated embodiment, the load cavity <part-num-ref name="load cavity">58</part-num-ref>
|
| 215 |
+
has one or more contacts <part-num-ref name="has one or more contacts">60</part-num-ref>
|
| 216 |
+
that electrically couple the test element <part-num-ref name="test element">36</part-num-ref>
|
| 217 |
+
to the meter <part-num-ref name="meter">32.</part-num-ref>
|
| 218 |
+
</p>
|
| 219 |
+
<p id="p-38" num="38">Nevertheless, the contacts <part-num-ref name="contacts">60</part-num-ref>
|
| 220 |
+
can be located elsewhere or can be optional in other embodiments, such as for test elements that optically analyze samples. The load <boundary-data type="line-number">30 </boundary-data>
|
| 221 |
+
cavity <part-num-ref name="load cavity">58</part-num-ref>
|
| 222 |
+
in the embodiment shown includes a lancet actuation mechanism <part-num-ref name="lancet actuation mechanism">61</part-num-ref>
|
| 223 |
+
for firing the lancet in the test element <part-num-ref name="test element">36.</part-num-ref>
|
| 224 |
+
The lancet actuation mechanism <part-num-ref name="lancet actuation mechanism">61</part-num-ref>
|
| 225 |
+
in one form is the same as the firing mechanism described in U.S. Patent Application No. </p>
|
| 226 |
+
<boundary-data type="header">
|
| 227 |
+
<confidence value="5">W</confidence>
|
| 228 |
+
P 23465 US<confidence value="5">/</confidence>
|
| 229 |
+
7404-744 CPS:375701 7 </boundary-data>
|
| 230 |
+
<p id="p-39" num="39">
|
| 231 |
+
<page-break num="8"/>
|
| 232 |
+
11/070,502, filed March 2, 2005, which is incorporated by reference in its entirety. </p>
|
| 233 |
+
<p id="p-40" num="40">The lancet actuation mechanism 61 in FIG. 2 includes a lancet engagement arm <part-num-ref name="lancet engagement arm">62</part-num-ref>
|
| 234 |
+
and a guide slot <part-num-ref name="guide slot">64</part-num-ref>
|
| 235 |
+
where the lancet arm <part-num-ref name="lancet arm">62</part-num-ref>
|
| 236 |
+
moves during actuation. As should be recognized, other types of actuation or firing mechanisms can be used. Moreover, the <boundary-data type="line-number">5 </boundary-data>
|
| 237 |
+
lancet actuation mechanism <part-num-ref name="lancet actuation mechanism">61</part-num-ref>
|
| 238 |
+
can be optional in other embodiments. </p>
|
| 239 |
+
<p id="p-41" num="41">Looking again at FIG. 1, the surface between the ends of the magazine <part-num-ref name="magazine">34</part-num-ref>
|
| 240 |
+
and meter <part-num-ref name="and meter">32</part-num-ref>
|
| 241 |
+
along which the test element <part-num-ref name="test element">36</part-num-ref>
|
| 242 |
+
rides when in the shuttle <part-num-ref name="shuttle">48</part-num-ref>
|
| 243 |
+
are generally level or flush with one another. With the system of FIG. 1, the test element <part-num-ref name="test element">36</part-num-ref>
|
| 244 |
+
can be accurately loaded into the meter <part-num-ref name="meter">32,</part-num-ref>
|
| 245 |
+
which can be important for test elements like <boundary-data type="line-number">10 </boundary-data>
|
| 246 |
+
LITs. If an LIT is improperly loaded, the lancet in the LIT can for example misfire and/or lance too deeply, which may lead to injury. When the test element <part-num-ref name="test element">36</part-num-ref>
|
| 247 |
+
in the shuttle <part-num-ref name="shuttle">48</part-num-ref>
|
| 248 |
+
slides over the load cavity <part-num-ref name="load cavity">58</part-num-ref>
|
| 249 |
+
in the meter <part-num-ref name="meter">32,</part-num-ref>
|
| 250 |
+
as is shown in FIG. 3, the stabilizer arm <part-num-ref name="stabilizer arm">52</part-num-ref>
|
| 251 |
+
pushes the test element <part-num-ref name="test element">36</part-num-ref>
|
| 252 |
+
into the load cavity <part-num-ref name="load cavity">58,</part-num-ref>
|
| 253 |
+
thereby loading the test element <part-num-ref name="test element">36</part-num-ref>
|
| 254 |
+
on the meter <part-num-ref name="meter">32.</part-num-ref>
|
| 255 |
+
With such a construction, the location of the test <boundary-data type="line-number">15 </boundary-data>
|
| 256 |
+
element <part-num-ref name="test element">36</part-num-ref>
|
| 257 |
+
can be tightly controlled. After the test element <part-num-ref name="test element">36</part-num-ref>
|
| 258 |
+
is loaded, the lancet actuation mechanism is able to fire the lancet in the test element <part-num-ref name="test element">36,</part-num-ref>
|
| 259 |
+
and the meter <part-num-ref name="meter">32</part-num-ref>
|
| 260 |
+
is able to read the test results from the test element <part-num-ref name="test element">36</part-num-ref>
|
| 261 |
+
via contacts <part-num-ref name="via contacts">60.</part-num-ref>
|
| 262 |
+
</p>
|
| 263 |
+
<p id="p-42" num="42">As can be seen in FIG. 4, which shows the top of the meter <part-num-ref name="meter">32</part-num-ref>
|
| 264 |
+
with the shuttle <part-num-ref name="shuttle">48</part-num-ref>
|
| 265 |
+
removed, an ejection mechanism <part-num-ref name="ejection mechanism">66</part-num-ref>
|
| 266 |
+
of the meter <part-num-ref name="meter">32</part-num-ref>
|
| 267 |
+
defines the load cavity <part-num-ref name="load cavity">58</part-num-ref>
|
| 268 |
+
in <boundary-data type="line-number">20 </boundary-data>
|
| 269 |
+
which the test element <part-num-ref name="test element">36</part-num-ref>
|
| 270 |
+
is received. The ejection mechanism <part-num-ref name="ejection mechanism">66</part-num-ref>
|
| 271 |
+
includes a series of rails <part-num-ref name="series of rails">68</part-num-ref>
|
| 272 |
+
that define the U-shaped load cavity <part-num-ref name="U-shaped load cavity">58</part-num-ref>
|
| 273 |
+
and an ejection button <part-num-ref name="ejection button">70.</part-num-ref>
|
| 274 |
+
The rails <part-num-ref name="rails">68</part-num-ref>
|
| 275 |
+
are slidably mounted on the meter <part-num-ref name="meter">32</part-num-ref>
|
| 276 |
+
such that when the user presses the ejection button <part-num-ref name="ejection button">70,</part-num-ref>
|
| 277 |
+
the test element <part-num-ref name="test element">36</part-num-ref>
|
| 278 |
+
travels in an ejection direction, as is indicated with arrow <part-num-ref name="ejection direction, as is indicated with arrow">72</part-num-ref>
|
| 279 |
+
in FIG. 4. In one form, the ejection mechanism <part-num-ref name="ejection mechanism">66</part-num-ref>
|
| 280 |
+
is spring biased so that <boundary-data type="line-number">25 </boundary-data>
|
| 281 |
+
the ejection mechanism <part-num-ref name="ejection mechanism">66</part-num-ref>
|
| 282 |
+
returns to its initial position once the ejection button <part-num-ref name="ejection button">70</part-num-ref>
|
| 283 |
+
is released. As should be recognized, the ejection mechanism <part-num-ref name="ejection mechanism">66</part-num-ref>
|
| 284 |
+
can be optional in other embodiments or can be automatically actuated. </p>
|
| 285 |
+
<p id="p-43" num="43">The operation of the system <part-num-ref name="system">30</part-num-ref>
|
| 286 |
+
will be generally described with reference to FIGS. 1, <part-num-ref name="will be generally described with reference to FIGS. 1,">2,</part-num-ref>
|
| 287 |
+
<part-num-ref name="will be generally described with reference to FIGS. 1, 2,">3,</part-num-ref>
|
| 288 |
+
and <part-num-ref name="will be generally described with reference to FIGS. 1, 2, 3, and">4.</part-num-ref>
|
| 289 |
+
Looking at FIGS. <confidence value="5">1</confidence>
|
| 290 |
+
and <part-num-ref name="and">2,</part-num-ref>
|
| 291 |
+
the force applied by the spring <part-num-ref name="spring">42</part-num-ref>
|
| 292 |
+
in <boundary-data type="line-number">30 </boundary-data>
|
| 293 |
+
the magazine <part-num-ref name="magazine">34</part-num-ref>
|
| 294 |
+
against the test elements <part-num-ref name="test elements">36</part-num-ref>
|
| 295 |
+
pushes a single test element <part-num-ref name="single test element">36</part-num-ref>
|
| 296 |
+
into the test element opening <part-num-ref name="test element opening">50</part-num-ref>
|
| 297 |
+
of the shuttle <part-num-ref name="shuttle">48.</part-num-ref>
|
| 298 |
+
As the test element <part-num-ref name="test element">36</part-num-ref>
|
| 299 |
+
is received into the shuttle <part-num-ref name="shuttle">48,</part-num-ref>
|
| 300 |
+
the stabilizer arm <part-num-ref name="stabilizer arm">52</part-num-ref>
|
| 301 |
+
deflects because the insertion force applied by the <boundary-data type="header">
|
| 302 |
+
<confidence value="5">W</confidence>
|
| 303 |
+
P 23465 US<confidence value="5">/</confidence>
|
| 304 |
+
7404-744 CPS:375701 8 </boundary-data>
|
| 305 |
+
<page-break num="9"/>
|
| 306 |
+
spring <part-num-ref name="spring">42</part-num-ref>
|
| 307 |
+
in the magazine <part-num-ref name="magazine">34</part-num-ref>
|
| 308 |
+
is greater than the force applied by the stabilizer arm <part-num-ref name="stabilizer arm">52.</part-num-ref>
|
| 309 |
+
</p>
|
| 310 |
+
<p id="p-44" num="44">The stabilizer arm 52 deflects to the extent so that a single test element <part-num-ref name="single test element">36</part-num-ref>
|
| 311 |
+
is received in the shuttle <part-num-ref name="shuttle">48.</part-num-ref>
|
| 312 |
+
It is envisioned that in other embodiments, the shuttle <part-num-ref name="shuttle">48</part-num-ref>
|
| 313 |
+
can be configured to receive more than one test element <part-num-ref name="can be configured to receive more than one test element">36.</part-num-ref>
|
| 314 |
+
Once the test element <part-num-ref name="test element">36</part-num-ref>
|
| 315 |
+
is <boundary-data type="line-number">5 </boundary-data>
|
| 316 |
+
loaded, the shuttle <part-num-ref name="shuttle">48</part-num-ref>
|
| 317 |
+
slides in the loading direction <part-num-ref name="loading direction">56</part-num-ref>
|
| 318 |
+
towards the meter <part-num-ref name="meter">32.</part-num-ref>
|
| 319 |
+
The shuttle <part-num-ref name="shuttle">48</part-num-ref>
|
| 320 |
+
can be manually moved by the user and/or automatically moved by the meter <part-num-ref name="meter">32.</part-num-ref>
|
| 321 |
+
</p>
|
| 322 |
+
<p id="p-45" num="45">When the shuttle <part-num-ref name="shuttle">48</part-num-ref>
|
| 323 |
+
moves over the load cavity <part-num-ref name="load cavity">58,</part-num-ref>
|
| 324 |
+
the stabilizer arm <part-num-ref name="stabilizer arm">52</part-num-ref>
|
| 325 |
+
pushes the test element <part-num-ref name="test element">36</part-num-ref>
|
| 326 |
+
into the load cavity <part-num-ref name="load cavity">58,</part-num-ref>
|
| 327 |
+
as is depicted in FIGS. 3 and <part-num-ref name="and">4.</part-num-ref>
|
| 328 |
+
</p>
|
| 329 |
+
<p id="p-46" num="46">
|
| 330 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 331 |
+
After the test element <part-num-ref name="test element">36</part-num-ref>
|
| 332 |
+
is loaded, the lancet actuation mechanism <part-num-ref name="lancet actuation mechanism">61</part-num-ref>
|
| 333 |
+
is used to fire the lancet in the test element <part-num-ref name="test element">36.</part-num-ref>
|
| 334 |
+
In one embodiment, the stabilizer arm <part-num-ref name="stabilizer arm">52</part-num-ref>
|
| 335 |
+
remains in contact with the test element <part-num-ref name="test element">36</part-num-ref>
|
| 336 |
+
so that during lancing and/or fluid collection/analysis, the test element <part-num-ref name="test element">36</part-num-ref>
|
| 337 |
+
remains stably positioned. In another embodiment, once the test element <part-num-ref name="test element">36</part-num-ref>
|
| 338 |
+
is loaded, the shuttle <part-num-ref name="shuttle">48</part-num-ref>
|
| 339 |
+
returns to the loading <boundary-data type="line-number">15 </boundary-data>
|
| 340 |
+
configuration that is illustrated in FIG. 2. After the incision is formed, the test element <part-num-ref name="test element">36</part-num-ref>
|
| 341 |
+
collects the fluid sample, and the result from the fluid analysis in the meter <part-num-ref name="meter">32</part-num-ref>
|
| 342 |
+
is communicated to the meter <part-num-ref name="meter">32</part-num-ref>
|
| 343 |
+
via the contacts <part-num-ref name="contacts">60.</part-num-ref>
|
| 344 |
+
Subsequently, the user ejects the now used test element <part-num-ref name="now used test element">36</part-num-ref>
|
| 345 |
+
for disposal by pressing the ejection button <part-num-ref name="ejection button">70</part-num-ref>
|
| 346 |
+
of the ejection mechanism <part-num-ref name="ejection mechanism">66.</part-num-ref>
|
| 347 |
+
</p>
|
| 348 |
+
<p id="p-47" num="47">
|
| 349 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 350 |
+
A meter transport system 80 according to another embodiment is illustrated in FIG 5. The meter transport system <part-num-ref name="meter transport system">80</part-num-ref>
|
| 351 |
+
is configured to be integrated with other components like a meter and a housing, for example. As can be seen, the meter system <part-num-ref name="meter system">80</part-num-ref>
|
| 352 |
+
in FIG. 5 includes a supply compartment or magazine <part-num-ref name="supply compartment or magazine">82</part-num-ref>
|
| 353 |
+
for storing unused test elements <part-num-ref name="for storing unused test elements">36,</part-num-ref>
|
| 354 |
+
a waste compartment or magazine <part-num-ref name="waste compartment or magazine">84</part-num-ref>
|
| 355 |
+
for storing used test elements <boundary-data type="line-number">25 </boundary-data>
|
| 356 |
+
<part-num-ref name="for storing used test elements">36,</part-num-ref>
|
| 357 |
+
and a transfer or transport mechanism <part-num-ref name="transfer or transport mechanism">86</part-num-ref>
|
| 358 |
+
that transports test elements <part-num-ref name="that transports test elements">36</part-num-ref>
|
| 359 |
+
from the supply magazine <part-num-ref name="supply magazine">82</part-num-ref>
|
| 360 |
+
to the waste magazine <part-num-ref name="waste magazine">84.</part-num-ref>
|
| 361 |
+
Both magazines <part-num-ref name="waste magazine 84. Both magazines">82,</part-num-ref>
|
| 362 |
+
<part-num-ref name="waste magazine 84. Both magazines 82,">84</part-num-ref>
|
| 363 |
+
include springs <part-num-ref name="include springs">42</part-num-ref>
|
| 364 |
+
for biasing the test elements <part-num-ref name="test elements">36</part-num-ref>
|
| 365 |
+
in the magazines <part-num-ref name="magazines">82,</part-num-ref>
|
| 366 |
+
<part-num-ref name="magazines 82,">84</part-num-ref>
|
| 367 |
+
so that the test elements <part-num-ref name="test elements">36</part-num-ref>
|
| 368 |
+
are tightly packed. The magazines <part-num-ref name="magazines">82,</part-num-ref>
|
| 369 |
+
<part-num-ref name="magazines 82,">84</part-num-ref>
|
| 370 |
+
in the embodiment shown extend in a longitudinal direction, but it should be appreciated that the magazines <part-num-ref name="magazines">82,</part-num-ref>
|
| 371 |
+
<part-num-ref name="magazines 82,">84</part-num-ref>
|
| 372 |
+
can be <boundary-data type="line-number">30 </boundary-data>
|
| 373 |
+
oriented in other manners. For instance, the magazines <part-num-ref name="magazines">82,</part-num-ref>
|
| 374 |
+
<part-num-ref name="magazines 82,">84</part-num-ref>
|
| 375 |
+
in other embodiments can be oriented in a V-shaped or L-shaped manner, to name a few examples. As <boundary-data type="header">
|
| 376 |
+
<confidence value="5">W</confidence>
|
| 377 |
+
P 23465 US<confidence value="5">/</confidence>
|
| 378 |
+
7404-744 CPS:375701 9 </boundary-data>
|
| 379 |
+
<page-break num="10"/>
|
| 380 |
+
should be recognized, the system <part-num-ref name="system">80</part-num-ref>
|
| 381 |
+
addresses the disposal issue by automatically storing used test elements <part-num-ref name="disposal issue by automatically storing used test elements">36</part-num-ref>
|
| 382 |
+
in the waste magazine <part-num-ref name="waste magazine">84.</part-num-ref>
|
| 383 |
+
</p>
|
| 384 |
+
<p id="p-48" num="48">In the illustrated embodiment, the transport mechanism <part-num-ref name="transport mechanism">86</part-num-ref>
|
| 385 |
+
includes a transport drum <part-num-ref name="transport drum">88.</part-num-ref>
|
| 386 |
+
To transport test elements <part-num-ref name="transport drum 88. To transport test elements">36,</part-num-ref>
|
| 387 |
+
the transport drum <part-num-ref name="transport drum">88</part-num-ref>
|
| 388 |
+
rotates in clockwise <part-num-ref name="rotates in clockwise">90</part-num-ref>
|
| 389 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 390 |
+
and counterclockwise <part-num-ref name="and counterclockwise">92</part-num-ref>
|
| 391 |
+
directions, as shown in FIG. 5. Between the magazines <part-num-ref name="magazines">82,</part-num-ref>
|
| 392 |
+
<part-num-ref name="magazines 82,">84,</part-num-ref>
|
| 393 |
+
the drum <part-num-ref name="drum">88</part-num-ref>
|
| 394 |
+
is able to rotate to a sampling position or orientation <part-num-ref name="sampling position or orientation">94</part-num-ref>
|
| 395 |
+
where a fluid sample can be collected and analyzed. </p>
|
| 396 |
+
<p id="p-49" num="49">As mentioned before, with portable meters, such as portable blood glucose meters, small meter sizes and ease of handling are desirable features. Most users <boundary-data type="line-number">10 </boundary-data>
|
| 397 |
+
would prefer smaller meters that are able to discretely fit inside a pocket or a purse so that the user is able to perform testing in any situation, such as in a restaurant bathroom or when traveling. One factor affecting size of meters that handle multiple test strips is storage compartment sizes. In previous designs, the storage compartments tended to be rather large and bulky because test elements were stored <boundary-data type="line-number">15 </boundary-data>
|
| 398 |
+
in a disorderly fashion. The meter transport system <part-num-ref name="meter transport system">80</part-num-ref>
|
| 399 |
+
in FIG. 5 stores test elements in both the supply <part-num-ref name="supply">82</part-num-ref>
|
| 400 |
+
and waste <part-num-ref name="and waste">84</part-num-ref>
|
| 401 |
+
magazines in a compact, stacked fashion. This allows the entire system package to have a compact design. In addition, the drum <part-num-ref name="drum">88</part-num-ref>
|
| 402 |
+
provides a compact as well as effective mechanism to transport test elements <part-num-ref name="compact as well as effective mechanism to transport test elements">36.</part-num-ref>
|
| 403 |
+
</p>
|
| 404 |
+
<p id="p-50" num="50">Turning to FIG. 6, the drum <part-num-ref name="drum">88</part-num-ref>
|
| 405 |
+
has a cylindrical shape with a hollow interior <boundary-data type="line-number">20 </boundary-data>
|
| 406 |
+
<part-num-ref name="hollow interior">96</part-num-ref>
|
| 407 |
+
that is configured to receive the lancet actuation mechanism <part-num-ref name="lancet actuation mechanism">61.</part-num-ref>
|
| 408 |
+
It is envisioned that the drum <part-num-ref name="drum">88</part-num-ref>
|
| 409 |
+
can have a different overall shape in other embodiments. For instance, the drum <part-num-ref name="drum">88</part-num-ref>
|
| 410 |
+
in other forms can have a hexagonal cross-sectional shape or other shapes. The drum <part-num-ref name="drum">88</part-num-ref>
|
| 411 |
+
has a test element relief notch <part-num-ref name="test element relief notch">98</part-num-ref>
|
| 412 |
+
in which the test element <part-num-ref name="test element">36</part-num-ref>
|
| 413 |
+
is received when loaded. In the embodiment shown, the notch <part-num-ref name="notch">98</part-num-ref>
|
| 414 |
+
is in the form of <boundary-data type="line-number">25 </boundary-data>
|
| 415 |
+
a flat section or indentation on the drum <part-num-ref name="drum">88,</part-num-ref>
|
| 416 |
+
but the notch <part-num-ref name="notch">98</part-num-ref>
|
| 417 |
+
can be shaped differently in other embodiments. As can be seen in FIG. 7, the notch <part-num-ref name="notch">98</part-num-ref>
|
| 418 |
+
has contacts <part-num-ref name="has contacts">60</part-num-ref>
|
| 419 |
+
for electrically coupling the test element <part-num-ref name="test element">36</part-num-ref>
|
| 420 |
+
to the meter. At the notch <part-num-ref name="notch">98,</part-num-ref>
|
| 421 |
+
the drum <part-num-ref name="drum">88</part-num-ref>
|
| 422 |
+
further incorporates the lancet actuation mechanism <part-num-ref name="lancet actuation mechanism">61</part-num-ref>
|
| 423 |
+
with the engagement arm <part-num-ref name="engagement arm">62</part-num-ref>
|
| 424 |
+
that engages the lancet in the test element <part-num-ref name="test element">36</part-num-ref>
|
| 425 |
+
and guide slot <part-num-ref name="and guide slot">64</part-num-ref>
|
| 426 |
+
where the engagement <boundary-data type="line-number">30 </boundary-data>
|
| 427 |
+
arm <part-num-ref name="engagement arm">62</part-num-ref>
|
| 428 |
+
travels. As mentioned before, the lancet in the test element <part-num-ref name="test element">36</part-num-ref>
|
| 429 |
+
can be actuated in other manners, and the test element <part-num-ref name="test element">36</part-num-ref>
|
| 430 |
+
in other forms may not incorporate a lancet. </p>
|
| 431 |
+
<boundary-data type="header">
|
| 432 |
+
<confidence value="5">W</confidence>
|
| 433 |
+
P 23465 US<confidence value="5">/</confidence>
|
| 434 |
+
7404-744 CPS:375701 10 </boundary-data>
|
| 435 |
+
<p id="p-51" num="51">
|
| 436 |
+
<page-break num="11"/>
|
| 437 |
+
Along one side of the notch <part-num-ref name="notch">98,</part-num-ref>
|
| 438 |
+
the drum <part-num-ref name="drum">88</part-num-ref>
|
| 439 |
+
has one or more catch rails <part-num-ref name="has one or more catch rails">100</part-num-ref>
|
| 440 |
+
that hold the test element <part-num-ref name="test element">36</part-num-ref>
|
| 441 |
+
in place during transport, as is depicted in FIGS. 6, <part-num-ref name="in place during transport, as is depicted in FIGS. 6,">7,</part-num-ref>
|
| 442 |
+
<part-num-ref name="in place during transport, as is depicted in FIGS. 6, 7,">8,</part-num-ref>
|
| 443 |
+
and <part-num-ref name="in place during transport, as is depicted in FIGS. 6, 7, 8, and">9.</part-num-ref>
|
| 444 |
+
Looking at FIG. 9, the rails <part-num-ref name="rails">100</part-num-ref>
|
| 445 |
+
have retention channels <part-num-ref name="have retention channels">101</part-num-ref>
|
| 446 |
+
that are configured to retain the test elements <part-num-ref name="test elements">36,</part-num-ref>
|
| 447 |
+
and the rails <part-num-ref name="rails">100</part-num-ref>
|
| 448 |
+
have an overall shape that <boundary-data type="line-number">5 </boundary-data>
|
| 449 |
+
is L-shaped so as to engage the edges of the test element <part-num-ref name="test element">36,</part-num-ref>
|
| 450 |
+
which tends to minimize damage. In the depicted embodiment, the rails <part-num-ref name="rails">100</part-num-ref>
|
| 451 |
+
engage generally at the corners of the test elements <part-num-ref name="test elements">36.</part-num-ref>
|
| 452 |
+
As should be recognized, the rails <part-num-ref name="rails">100</part-num-ref>
|
| 453 |
+
in other embodiments can be shaped differently and engage the test elements <part-num-ref name="test elements">36</part-num-ref>
|
| 454 |
+
in other manners. For example, in one form, the rails <part-num-ref name="rails">100</part-num-ref>
|
| 455 |
+
are integral with the drum <part-num-ref name="drum">88</part-num-ref>
|
| 456 |
+
so that the rails <part-num-ref name="rails">100</part-num-ref>
|
| 457 |
+
are <boundary-data type="line-number">10 </boundary-data>
|
| 458 |
+
generally flush with respect to the outer surface of the drum <part-num-ref name="drum">88.</part-num-ref>
|
| 459 |
+
It is envisioned that other types of holding devices such as clips can be used in other embodiments. In the illustrated embodiment, the rails <part-num-ref name="rails">100</part-num-ref>
|
| 460 |
+
only partially cover the ends of the test elements <part-num-ref name="test elements">36</part-num-ref>
|
| 461 |
+
so as to not interfere with lancing and fluid collection. As will be explained in greater detail below with reference to FIGS. 10 and <part-num-ref name="and">
|
| 462 |
+
<confidence value="66">11</confidence>
|
| 463 |
+
, </part-num-ref>
|
| 464 |
+
the rails <part-num-ref name="rails">100</part-num-ref>
|
| 465 |
+
in the illustrated <boundary-data type="line-number">15 </boundary-data>
|
| 466 |
+
embodiment are spaced apart along one side of the test element <part-num-ref name="test element">36</part-num-ref>
|
| 467 |
+
to form a relief gap <part-num-ref name="relief gap">102</part-num-ref>
|
| 468 |
+
that receives a catch <part-num-ref name="catch">104</part-num-ref>
|
| 469 |
+
on the waste magazine <part-num-ref name="waste magazine">84.</part-num-ref>
|
| 470 |
+
</p>
|
| 471 |
+
<p id="p-52" num="52">Turning to FIG. 10, the waste magazine <part-num-ref name="waste magazine">84</part-num-ref>
|
| 472 |
+
has a waste receptacle opening <part-num-ref name="waste receptacle opening">106</part-num-ref>
|
| 473 |
+
that faces the drum <part-num-ref name="drum">88</part-num-ref>
|
| 474 |
+
and is configured to receive used test elements <part-num-ref name="and is configured to receive used test elements">36.</part-num-ref>
|
| 475 |
+
Around the opening <part-num-ref name="opening">106,</part-num-ref>
|
| 476 |
+
the waste magazine <part-num-ref name="waste magazine">84</part-num-ref>
|
| 477 |
+
has the catch <part-num-ref name="catch">104</part-num-ref>
|
| 478 |
+
and a series of rails <part-num-ref name="series of rails">108</part-num-ref>
|
| 479 |
+
with <boundary-data type="line-number">20 </boundary-data>
|
| 480 |
+
channels <part-num-ref name="with channels">110</part-num-ref>
|
| 481 |
+
configured to catch used test elements <part-num-ref name="configured to catch used test elements">36</part-num-ref>
|
| 482 |
+
from the drum <part-num-ref name="drum">88.</part-num-ref>
|
| 483 |
+
The rails <part-num-ref name="rails">108</part-num-ref>
|
| 484 |
+
are oriented in a U-shaped configuration with the catch <part-num-ref name="catch">104</part-num-ref>
|
| 485 |
+
located at an open end <part-num-ref name="open end">112</part-num-ref>
|
| 486 |
+
of the U-shaped rails <part-num-ref name="U-shaped rails">108.</part-num-ref>
|
| 487 |
+
The catch <part-num-ref name="catch">104</part-num-ref>
|
| 488 |
+
is made of a resilient material that deflects to receive the test element <part-num-ref name="test element">36,</part-num-ref>
|
| 489 |
+
and once the trailing side of the test element <part-num-ref name="test element">36</part-num-ref>
|
| 490 |
+
passes the catch <part-num-ref name="catch">104,</part-num-ref>
|
| 491 |
+
the catch <part-num-ref name="catch">104</part-num-ref>
|
| 492 |
+
returns to its original undeflected state, thereby <boundary-data type="line-number">25 </boundary-data>
|
| 493 |
+
retaining the test element <part-num-ref name="test element">36</part-num-ref>
|
| 494 |
+
in the waste compartment <part-num-ref name="waste compartment">84.</part-num-ref>
|
| 495 |
+
The catch <part-num-ref name="catch">104</part-num-ref>
|
| 496 |
+
can include a spring and/or can be made from a resilient material, such as plastic, to allow deflection of the catch <part-num-ref name="catch">104.</part-num-ref>
|
| 497 |
+
</p>
|
| 498 |
+
<p id="p-53" num="53">FIG. 11 illustrates the interface between the rails <part-num-ref name="rails">100</part-num-ref>
|
| 499 |
+
of the drum <part-num-ref name="drum">88</part-num-ref>
|
| 500 |
+
and the rails <part-num-ref name="rails">108</part-num-ref>
|
| 501 |
+
of the waste magazine <part-num-ref name="waste magazine">84</part-num-ref>
|
| 502 |
+
when a used test element <part-num-ref name="used test element">36</part-num-ref>
|
| 503 |
+
is loaded into the <boundary-data type="line-number">30 </boundary-data>
|
| 504 |
+
waste magazine <part-num-ref name="waste magazine">84.</part-num-ref>
|
| 505 |
+
Although the drum <part-num-ref name="drum">88</part-num-ref>
|
| 506 |
+
will be described as being rotated in a specific direction during the various stages, it should be recognized that the drum <part-num-ref name="drum">88</part-num-ref>
|
| 507 |
+
can be rotated in other combinations of directions at the various stages. As can be <boundary-data type="header">
|
| 508 |
+
<confidence value="5">W</confidence>
|
| 509 |
+
P 23465 US<confidence value="5">/</confidence>
|
| 510 |
+
7404-744 CPS:375701 11 </boundary-data>
|
| 511 |
+
<page-break num="12"/>
|
| 512 |
+
seen, when the test element <part-num-ref name="test element">36</part-num-ref>
|
| 513 |
+
is in the loaded position, the catch <part-num-ref name="catch">104</part-num-ref>
|
| 514 |
+
is received in the relief gap <part-num-ref name="relief gap">102</part-num-ref>
|
| 515 |
+
between the rails <part-num-ref name="rails">100</part-num-ref>
|
| 516 |
+
on the drum <part-num-ref name="drum">88.</part-num-ref>
|
| 517 |
+
The catch <part-num-ref name="catch">104</part-num-ref>
|
| 518 |
+
holds the test element <part-num-ref name="test element">36</part-num-ref>
|
| 519 |
+
within the rails <part-num-ref name="rails">108</part-num-ref>
|
| 520 |
+
of the waste magazine <part-num-ref name="waste magazine">84</part-num-ref>
|
| 521 |
+
as the drum <part-num-ref name="drum">88</part-num-ref>
|
| 522 |
+
rotates back to load another test element <part-num-ref name="rotates back to load another test element">36</part-num-ref>
|
| 523 |
+
from the supply magazine <part-num-ref name="supply magazine">82.</part-num-ref>
|
| 524 |
+
</p>
|
| 525 |
+
<p id="p-54" num="54">
|
| 526 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 527 |
+
The operation of the transport system <part-num-ref name="transport system">80</part-num-ref>
|
| 528 |
+
will be initially described with reference to FIGS. 5 and <part-num-ref name="and">6.</part-num-ref>
|
| 529 |
+
The drum <part-num-ref name="drum">88</part-num-ref>
|
| 530 |
+
receives a fresh test element <part-num-ref name="fresh test element">36</part-num-ref>
|
| 531 |
+
from the supply magazine <part-num-ref name="supply magazine">82</part-num-ref>
|
| 532 |
+
by rotating in a clockwise direction <part-num-ref name="clockwise direction">90</part-num-ref>
|
| 533 |
+
such that the test element relief notch <part-num-ref name="test element relief notch">98</part-num-ref>
|
| 534 |
+
rotates slightly past the opening of the supply magazine <part-num-ref name="supply magazine">82.</part-num-ref>
|
| 535 |
+
As mentioned before, the drum <part-num-ref name="drum">88</part-num-ref>
|
| 536 |
+
can be manually rotated by the user and/or rotated via <boundary-data type="line-number">10 </boundary-data>
|
| 537 |
+
a drive mechanism, such as an electric motor. Upon the drum <part-num-ref name="drum">88</part-num-ref>
|
| 538 |
+
rotating in the counterclockwise direction <part-num-ref name="counterclockwise direction">92,</part-num-ref>
|
| 539 |
+
the rails <part-num-ref name="rails">100</part-num-ref>
|
| 540 |
+
on the drum <part-num-ref name="drum">88</part-num-ref>
|
| 541 |
+
catch the top-most test element <part-num-ref name="top-most test element">36</part-num-ref>
|
| 542 |
+
on the stack of test elements <part-num-ref name="stack of test elements">36</part-num-ref>
|
| 543 |
+
in the supply magazine <part-num-ref name="supply magazine">82,</part-num-ref>
|
| 544 |
+
as is depicted in FIGS. 7, <part-num-ref name="supply magazine 82, as is depicted in FIGS. 7,">8,</part-num-ref>
|
| 545 |
+
and <part-num-ref name="supply magazine 82, as is depicted in FIGS. 7, 8, and">9.</part-num-ref>
|
| 546 |
+
As the drum <part-num-ref name="drum">88</part-num-ref>
|
| 547 |
+
continues to rotate, the test element <part-num-ref name="test element">36</part-num-ref>
|
| 548 |
+
is removed from the supply magazine <part-num-ref name="supply magazine">82.</part-num-ref>
|
| 549 |
+
</p>
|
| 550 |
+
<p id="p-55" num="55">
|
| 551 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 552 |
+
The drum 88 then orients the test element <part-num-ref name="test element">36</part-num-ref>
|
| 553 |
+
at the sampling position <part-num-ref name="sampling position">94</part-num-ref>
|
| 554 |
+
(FIG. </p>
|
| 555 |
+
<p id="p-56" num="56">5). While at the sampling position <part-num-ref name="sampling position">94,</part-num-ref>
|
| 556 |
+
the test element <part-num-ref name="test element">36</part-num-ref>
|
| 557 |
+
collects and analyzes a fluid sample. In one form, the lancet engagement arm <part-num-ref name="lancet engagement arm">62</part-num-ref>
|
| 558 |
+
(FIG. <part-num-ref name="(FIG.">7)</part-num-ref>
|
| 559 |
+
fires the lancet of the test element <part-num-ref name="test element">36</part-num-ref>
|
| 560 |
+
so as to form an incision in tissue. Body fluid from the incision is then drawn into the test element <part-num-ref name="test element">36,</part-num-ref>
|
| 561 |
+
and the readings for the analysis are conveyed via <boundary-data type="line-number">20 </boundary-data>
|
| 562 |
+
the contacts <part-num-ref name="contacts">60</part-num-ref>
|
| 563 |
+
on the drum <part-num-ref name="drum">88.</part-num-ref>
|
| 564 |
+
It is contemplated that in other embodiments, the fluid sample can analyzed with the test element <part-num-ref name="test element">36</part-num-ref>
|
| 565 |
+
moved to a different position once the fluid sample is collected. </p>
|
| 566 |
+
<p id="p-57" num="57">After the fluid sample is analyzed, the now used test element <part-num-ref name="now used test element">36</part-num-ref>
|
| 567 |
+
on the drum <part-num-ref name="drum">88</part-num-ref>
|
| 568 |
+
is transported to the waste magazine <part-num-ref name="waste magazine">84.</part-num-ref>
|
| 569 |
+
In the illustrated embodiment, the drum <boundary-data type="line-number">25 </boundary-data>
|
| 570 |
+
<part-num-ref name="drum">88</part-num-ref>
|
| 571 |
+
is rotated in a counterclockwise direction <part-num-ref name="counterclockwise direction">92</part-num-ref>
|
| 572 |
+
(FIG. <part-num-ref name="(FIG.">5)</part-num-ref>
|
| 573 |
+
in order to load the used test element <part-num-ref name="used test element">36</part-num-ref>
|
| 574 |
+
into the waste magazine <part-num-ref name="waste magazine">84.</part-num-ref>
|
| 575 |
+
The leading side of the test element <part-num-ref name="test element">36,</part-num-ref>
|
| 576 |
+
which is opposite the rails <part-num-ref name="rails">100</part-num-ref>
|
| 577 |
+
on the drum <part-num-ref name="drum">88,</part-num-ref>
|
| 578 |
+
pushes against the top-most test element <part-num-ref name="top-most test element">36</part-num-ref>
|
| 579 |
+
in the waste magazine <part-num-ref name="waste magazine">84</part-num-ref>
|
| 580 |
+
at a slight angle. This results in the test element <part-num-ref name="test element">36</part-num-ref>
|
| 581 |
+
in the waste magazine being pushed slightly backwards to make room for the test <boundary-data type="line-number">30 </boundary-data>
|
| 582 |
+
element <part-num-ref name="test element">36</part-num-ref>
|
| 583 |
+
on the drum <part-num-ref name="drum">88.</part-num-ref>
|
| 584 |
+
In addition, the catch <part-num-ref name="catch">104</part-num-ref>
|
| 585 |
+
on the waste magazine <part-num-ref name="waste magazine">84</part-num-ref>
|
| 586 |
+
deflects slightly. When the drum <part-num-ref name="drum">88</part-num-ref>
|
| 587 |
+
rotates further, the test element <part-num-ref name="test element">36</part-num-ref>
|
| 588 |
+
on the drum <part-num-ref name="drum">88</part-num-ref>
|
| 589 |
+
slides into the rails <part-num-ref name="rails">108</part-num-ref>
|
| 590 |
+
of the waste magazine <part-num-ref name="waste magazine">84.</part-num-ref>
|
| 591 |
+
The test element <part-num-ref name="test element">36</part-num-ref>
|
| 592 |
+
continues <boundary-data type="header">
|
| 593 |
+
<confidence value="5">W</confidence>
|
| 594 |
+
P 23465 US<confidence value="5">/</confidence>
|
| 595 |
+
7404-744 CPS:375701 12 </boundary-data>
|
| 596 |
+
<page-break num="13"/>
|
| 597 |
+
to slide into the rails <part-num-ref name="rails">108</part-num-ref>
|
| 598 |
+
of the magazine <part-num-ref name="magazine">84</part-num-ref>
|
| 599 |
+
as the drum <part-num-ref name="drum">88</part-num-ref>
|
| 600 |
+
rotates until the catch <part-num-ref name="catch">104</part-num-ref>
|
| 601 |
+
of the waste magazine <part-num-ref name="waste magazine">84</part-num-ref>
|
| 602 |
+
is received into the relief gap <part-num-ref name="relief gap">102</part-num-ref>
|
| 603 |
+
between the rails <part-num-ref name="rails">100</part-num-ref>
|
| 604 |
+
on the drum <part-num-ref name="drum">88.</part-num-ref>
|
| 605 |
+
At that point, the catch <part-num-ref name="catch">104</part-num-ref>
|
| 606 |
+
returns to its original undeflected state so that the test element <part-num-ref name="test element">36</part-num-ref>
|
| 607 |
+
is held within the waste magazine <part-num-ref name="waste magazine">84.</part-num-ref>
|
| 608 |
+
Afterwards, the drum <boundary-data type="line-number">5 </boundary-data>
|
| 609 |
+
<part-num-ref name="drum">88</part-num-ref>
|
| 610 |
+
is rotated in a clockwise direction <part-num-ref name="clockwise direction">90</part-num-ref>
|
| 611 |
+
(FIG. <part-num-ref name="(FIG.">5)</part-num-ref>
|
| 612 |
+
such that the catch <part-num-ref name="catch">104</part-num-ref>
|
| 613 |
+
retains the test element <part-num-ref name="test element">36</part-num-ref>
|
| 614 |
+
in the waste magazine <part-num-ref name="waste magazine">84.</part-num-ref>
|
| 615 |
+
The same stages are repeated for testing additional fluid samples, and once all of the test elements <part-num-ref name="test elements">36</part-num-ref>
|
| 616 |
+
have been used, the user can dispose of the magazine <part-num-ref name="magazine">84</part-num-ref>
|
| 617 |
+
and/or other various components of the system <part-num-ref name="system">80</part-num-ref>
|
| 618 |
+
<confidence value="66">so</confidence>
|
| 619 |
+
as to minimize the risk of hazardous waste exposure. </p>
|
| 620 |
+
<p id="p-58" num="58">
|
| 621 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 622 |
+
A meter system 120 with a transport system <part-num-ref name="transport system">122</part-num-ref>
|
| 623 |
+
for transporting test elements <part-num-ref name="for transporting test elements">36</part-num-ref>
|
| 624 |
+
according to another embodiment is illustrated in FIG. 12. As shown, the meter system <part-num-ref name="meter system">120</part-num-ref>
|
| 625 |
+
includes a meter <part-num-ref name="meter">124,</part-num-ref>
|
| 626 |
+
a supply magazine <part-num-ref name="supply magazine">126</part-num-ref>
|
| 627 |
+
that contains a stack of unused test elements <part-num-ref name="stack of unused test elements">36,</part-num-ref>
|
| 628 |
+
and the transport system <part-num-ref name="transport system">122</part-num-ref>
|
| 629 |
+
that transports test elements <part-num-ref name="that transports test elements">36</part-num-ref>
|
| 630 |
+
from the magazine <part-num-ref name="magazine">126</part-num-ref>
|
| 631 |
+
to the meter <part-num-ref name="meter">124.</part-num-ref>
|
| 632 |
+
As will be described in greater detail below, <boundary-data type="line-number">15 </boundary-data>
|
| 633 |
+
the transport system <part-num-ref name="transport system">122</part-num-ref>
|
| 634 |
+
in the depicted embodiment is generally disc-shaped and the disc spins to transport the test elements <part-num-ref name="test elements">36.</part-num-ref>
|
| 635 |
+
As will be appreciated, the transport system <part-num-ref name="transport system">122</part-num-ref>
|
| 636 |
+
in the illustrated embodiment provides a compact and reliable device for transporting test elements <part-num-ref name="compact and reliable device for transporting test elements">36.</part-num-ref>
|
| 637 |
+
</p>
|
| 638 |
+
<p id="p-59" num="59">The meter 124 includes an output device <part-num-ref name="output device">128</part-num-ref>
|
| 639 |
+
in the form of a display for <boundary-data type="line-number">20 </boundary-data>
|
| 640 |
+
displaying readings and an input device <part-num-ref name="input device">130</part-num-ref>
|
| 641 |
+
in the form of one or buttons. Like the previous embodiments, the magazine <part-num-ref name="magazine">126</part-num-ref>
|
| 642 |
+
includes a spring <part-num-ref name="spring">42</part-num-ref>
|
| 643 |
+
that biases the test elements <part-num-ref name="test elements">36</part-num-ref>
|
| 644 |
+
towards a supply opening <part-num-ref name="supply opening">132.</part-num-ref>
|
| 645 |
+
The magazine <part-num-ref name="magazine">126</part-num-ref>
|
| 646 |
+
can further include a desiccant to maintain low humidity levels in the magazine <part-num-ref name="magazine">126.</part-num-ref>
|
| 647 |
+
Looking at FIG. 14, the meter <part-num-ref name="meter">124</part-num-ref>
|
| 648 |
+
and the magazine <part-num-ref name="magazine">126</part-num-ref>
|
| 649 |
+
are generally oriented in a side-by-side fashion. </p>
|
| 650 |
+
<p id="p-60" num="60">
|
| 651 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 652 |
+
The meter 124 has a female test element connector <part-num-ref name="female test element connector">134</part-num-ref>
|
| 653 |
+
in which the end of the test element <part-num-ref name="test element">36</part-num-ref>
|
| 654 |
+
that contains contacts is received. Inside, the connector <part-num-ref name="connector">134</part-num-ref>
|
| 655 |
+
in one embodiment can have the lancet engagement arm <part-num-ref name="lancet engagement arm">62</part-num-ref>
|
| 656 |
+
for actuating the lancet in the test element <part-num-ref name="test element">36.</part-num-ref>
|
| 657 |
+
Further, the meter <part-num-ref name="meter">124</part-num-ref>
|
| 658 |
+
has a shaft <part-num-ref name="shaft">136</part-num-ref>
|
| 659 |
+
that is used to rotate the transport system <part-num-ref name="transport system">122,</part-num-ref>
|
| 660 |
+
as will be explained in greater detail below. In one form, the shaft <part-num-ref name="shaft">136</part-num-ref>
|
| 661 |
+
is <boundary-data type="line-number">30 </boundary-data>
|
| 662 |
+
coupled to a motor inside the meter <part-num-ref name="meter">124</part-num-ref>
|
| 663 |
+
so that the meter <part-num-ref name="meter">124</part-num-ref>
|
| 664 |
+
is able to automatically rotate the transport system <part-num-ref name="transport system">122.</part-num-ref>
|
| 665 |
+
In another form, the shaft <part-num-ref name="shaft">136</part-num-ref>
|
| 666 |
+
merely provides a pivot point when the user manually rotates the transport system <part-num-ref name="transport system">122.</part-num-ref>
|
| 667 |
+
As depicted by <boundary-data type="header">
|
| 668 |
+
<confidence value="5">W</confidence>
|
| 669 |
+
P 23465 US<confidence value="5">/</confidence>
|
| 670 |
+
7404-744 CPS:375701 13 </boundary-data>
|
| 671 |
+
<page-break num="14"/>
|
| 672 |
+
arrow <part-num-ref name="transport system 122. As depicted by arrow">138</part-num-ref>
|
| 673 |
+
in FIG. 14, the transport system <part-num-ref name="transport system">122</part-num-ref>
|
| 674 |
+
rotates in a manner such that one of the test elements <part-num-ref name="test elements">36</part-num-ref>
|
| 675 |
+
from the magazine <part-num-ref name="magazine">126</part-num-ref>
|
| 676 |
+
is inserted into the female connector <part-num-ref name="female connector">134.</part-num-ref>
|
| 677 |
+
</p>
|
| 678 |
+
<p id="p-61" num="61">Near the female connector <part-num-ref name="female connector">134,</part-num-ref>
|
| 679 |
+
the meter <part-num-ref name="meter">124</part-num-ref>
|
| 680 |
+
has a relief notch <part-num-ref name="relief notch">140</part-num-ref>
|
| 681 |
+
in which the collection end of the test element <part-num-ref name="test element">36</part-num-ref>
|
| 682 |
+
extends to collect fluid from an incised body <boundary-data type="line-number">5 </boundary-data>
|
| 683 |
+
part, such as a finger. </p>
|
| 684 |
+
<p id="p-62" num="62">Turning to FIGS. 15 and <part-num-ref name="and">16,</part-num-ref>
|
| 685 |
+
the transport system <part-num-ref name="transport system">122</part-num-ref>
|
| 686 |
+
likewise has a relief notch <part-num-ref name="relief notch">142</part-num-ref>
|
| 687 |
+
that is configured to prevent interference with the test element <part-num-ref name="test element">36</part-num-ref>
|
| 688 |
+
when collecting a fluid sample. Again, the shaft <part-num-ref name="shaft">136</part-num-ref>
|
| 689 |
+
from the meter <part-num-ref name="meter">124</part-num-ref>
|
| 690 |
+
is coupled to the transport system <part-num-ref name="transport system">122</part-num-ref>
|
| 691 |
+
for rotating of the transport system <part-num-ref name="transport system">122.</part-num-ref>
|
| 692 |
+
The transport system <boundary-data type="line-number">10 </boundary-data>
|
| 693 |
+
<part-num-ref name="transport system">122</part-num-ref>
|
| 694 |
+
includes a test element cavity or recess<confidence value="5">1</confidence>
|
| 695 |
+
44 in which the test element <part-num-ref name="test element">36</part-num-ref>
|
| 696 |
+
is received and a gripping mechanism <part-num-ref name="gripping mechanism">146</part-num-ref>
|
| 697 |
+
for gripping the test element <part-num-ref name="test element">36</part-num-ref>
|
| 698 |
+
when in the test element cavity <part-num-ref name="test element cavity">144.</part-num-ref>
|
| 699 |
+
In the embodiment illustrated in FIG. 16, the transport system <part-num-ref name="transport system">122</part-num-ref>
|
| 700 |
+
is in the form of a composite disc with a first (or top) layer or disc <part-num-ref name="first (or top) layer or disc">148</part-num-ref>
|
| 701 |
+
and a second (or bottom) layer or disc <part-num-ref name="second (or bottom) layer or disc">150</part-num-ref>
|
| 702 |
+
that is sandwiched between the first disc <boundary-data type="line-number">15 </boundary-data>
|
| 703 |
+
<part-num-ref name="first disc">148</part-num-ref>
|
| 704 |
+
and the meter <part-num-ref name="meter">124.</part-num-ref>
|
| 705 |
+
The discs <part-num-ref name="discs">148,</part-num-ref>
|
| 706 |
+
<part-num-ref name="discs 148,">150</part-num-ref>
|
| 707 |
+
are able to both move independently with respect to one another and in unison together. It is contemplated that the transport system <part-num-ref name="transport system">122</part-num-ref>
|
| 708 |
+
can be configured differently in other embodiments and can engage the test element <part-num-ref name="test element">36</part-num-ref>
|
| 709 |
+
in other manners. For instance, instead of two discs, the transport system <part-num-ref name="transport system">122</part-num-ref>
|
| 710 |
+
in other embodiments can include one or mores discs that have test <boundary-data type="line-number">20 </boundary-data>
|
| 711 |
+
element engagement rails similar to the above-discussed embodiments that hold the test element <part-num-ref name="test element">36</part-num-ref>
|
| 712 |
+
during transport. </p>
|
| 713 |
+
<p id="p-63" num="63">Looking at FIG. 16, the underside of the top disc <part-num-ref name="top disc">148,</part-num-ref>
|
| 714 |
+
which faces the bottom disc <part-num-ref name="bottom disc">150,</part-num-ref>
|
| 715 |
+
has one or more lock pins <part-num-ref name="bottom disc 150, has one or more lock pins">152</part-num-ref>
|
| 716 |
+
that are configured to engage on or more corresponding grip members <part-num-ref name="that are configured to engage on or more corresponding grip members">154</part-num-ref>
|
| 717 |
+
on the bottom disc <part-num-ref name="bottom disc">150.</part-num-ref>
|
| 718 |
+
In the illustrated <boundary-data type="line-number">25 </boundary-data>
|
| 719 |
+
embodiment, the top disc <part-num-ref name="top disc">148</part-num-ref>
|
| 720 |
+
includes a pair of lock pins <part-num-ref name="pair of lock pins">152</part-num-ref>
|
| 721 |
+
that are configured to engage a pair of grip members <part-num-ref name="pair of grip members">154</part-num-ref>
|
| 722 |
+
that are located on opposite sides of the test element cavity <part-num-ref name="test element cavity">144.</part-num-ref>
|
| 723 |
+
However, in other embodiments, the transport system <part-num-ref name="transport system">122</part-num-ref>
|
| 724 |
+
can include more or less lock pins <part-num-ref name="can include more or less lock pins">152</part-num-ref>
|
| 725 |
+
and grip members <part-num-ref name="and grip members">154</part-num-ref>
|
| 726 |
+
than are shown. The lock pins <part-num-ref name="lock pins">152</part-num-ref>
|
| 727 |
+
are generally rigid, while the grip members <part-num-ref name="grip members">154</part-num-ref>
|
| 728 |
+
are flexible. With reference <boundary-data type="line-number">30 </boundary-data>
|
| 729 |
+
to FIG. 17, the grip members <part-num-ref name="grip members">154</part-num-ref>
|
| 730 |
+
each have hooked shaped ends that form catches <part-num-ref name="each have hooked shaped ends that form catches">156</part-num-ref>
|
| 731 |
+
that are configured to engage the lock pins <part-num-ref name="lock pins">152.</part-num-ref>
|
| 732 |
+
</p>
|
| 733 |
+
<boundary-data type="header">
|
| 734 |
+
<confidence value="5">W</confidence>
|
| 735 |
+
P 23465 US<confidence value="5">/</confidence>
|
| 736 |
+
7404-744 CPS:375701 14 </boundary-data>
|
| 737 |
+
<p id="p-64" num="64">
|
| 738 |
+
<page-break num="15"/>
|
| 739 |
+
As noted above, a motor in the meter <part-num-ref name="meter">124</part-num-ref>
|
| 740 |
+
can automatically rotate the top disc <part-num-ref name="top disc">148</part-num-ref>
|
| 741 |
+
and/or the user can manually rotate the top disc <part-num-ref name="top disc">148.</part-num-ref>
|
| 742 |
+
When the top disc <part-num-ref name="top disc">148</part-num-ref>
|
| 743 |
+
is rotated in a counterclockwise direction <part-num-ref name="counterclockwise direction">158,</part-num-ref>
|
| 744 |
+
the lock pins <part-num-ref name="lock pins">152</part-num-ref>
|
| 745 |
+
engage the catches <part-num-ref name="catches">156</part-num-ref>
|
| 746 |
+
on the grip members <part-num-ref name="grip members">154,</part-num-ref>
|
| 747 |
+
which in turn compresses the grip members <part-num-ref name="grip members">154</part-num-ref>
|
| 748 |
+
in an <boundary-data type="line-number">5 </boundary-data>
|
| 749 |
+
inward direction <part-num-ref name="inward direction">160.</part-num-ref>
|
| 750 |
+
Consequently, the grip members <part-num-ref name="grip members">154</part-num-ref>
|
| 751 |
+
grip the sides of the test element <part-num-ref name="test element">36,</part-num-ref>
|
| 752 |
+
thereby holding the test element in the transport system <part-num-ref name="transport system">122.</part-num-ref>
|
| 753 |
+
Holding the sides of the test elements in such a manner helps to reduce damage of the test element <part-num-ref name="test element">36</part-num-ref>
|
| 754 |
+
during transport. Once the lock pins <part-num-ref name="lock pins">152</part-num-ref>
|
| 755 |
+
on the top disc <part-num-ref name="top disc">148</part-num-ref>
|
| 756 |
+
engage the catches <part-num-ref name="catches">156,</part-num-ref>
|
| 757 |
+
the bottom disc <part-num-ref name="bottom disc">150</part-num-ref>
|
| 758 |
+
starts moving in the counterclockwise direction <part-num-ref name="counterclockwise direction">158</part-num-ref>
|
| 759 |
+
so as to <boundary-data type="line-number">10 </boundary-data>
|
| 760 |
+
transport the test element <part-num-ref name="test element">36</part-num-ref>
|
| 761 |
+
to the test element connector <part-num-ref name="test element connector">134.</part-num-ref>
|
| 762 |
+
When in the test element cavity <part-num-ref name="test element cavity">144,</part-num-ref>
|
| 763 |
+
the test element <part-num-ref name="test element">36</part-num-ref>
|
| 764 |
+
can be angled slightly so that the end of the test element <part-num-ref name="test element">36</part-num-ref>
|
| 765 |
+
extends from the underside of the bottom disc <part-num-ref name="bottom disc">150</part-num-ref>
|
| 766 |
+
so that the test element <part-num-ref name="test element">36</part-num-ref>
|
| 767 |
+
is able to engage the connector <part-num-ref name="connector">134.</part-num-ref>
|
| 768 |
+
Alternatively or additionally, the bottom disc <part-num-ref name="bottom disc">150</part-num-ref>
|
| 769 |
+
can incorporate a beveled cavity <part-num-ref name="beveled cavity">162</part-num-ref>
|
| 770 |
+
at one end of the test element <boundary-data type="line-number">15 </boundary-data>
|
| 771 |
+
cavity <part-num-ref name="test element cavity">144</part-num-ref>
|
| 772 |
+
that exposes the connection end of the test element <part-num-ref name="test element">36</part-num-ref>
|
| 773 |
+
to the connector <part-num-ref name="connector">134</part-num-ref>
|
| 774 |
+
so as to facilitate the connection between the test element <part-num-ref name="test element">36</part-num-ref>
|
| 775 |
+
and the connector <part-num-ref name="connector">134.</part-num-ref>
|
| 776 |
+
</p>
|
| 777 |
+
<p id="p-65" num="65">Once the test element <part-num-ref name="test element">36</part-num-ref>
|
| 778 |
+
reaches the connector <part-num-ref name="connector">134,</part-num-ref>
|
| 779 |
+
the end of the test element <part-num-ref name="test element">36</part-num-ref>
|
| 780 |
+
containing the contacts is inserted into the connector <part-num-ref name="connector">134</part-num-ref>
|
| 781 |
+
to engage the spring-biased contacts in the connector <part-num-ref name="connector">134,</part-num-ref>
|
| 782 |
+
thereby forming an electrical connection between the <boundary-data type="line-number">20 </boundary-data>
|
| 783 |
+
test element <part-num-ref name="test element">36</part-num-ref>
|
| 784 |
+
and the meter <part-num-ref name="meter">124.</part-num-ref>
|
| 785 |
+
Afterwards, the top disc <part-num-ref name="top disc">148</part-num-ref>
|
| 786 |
+
is rotated in a clockwise direction (either manually or automatically), which disengages the lock pins <part-num-ref name="lock pins">152</part-num-ref>
|
| 787 |
+
from the grip members <part-num-ref name="grip members">154.</part-num-ref>
|
| 788 |
+
With the lock pins <part-num-ref name="lock pins">152</part-num-ref>
|
| 789 |
+
removed, the grip members <part-num-ref name="grip members">154</part-num-ref>
|
| 790 |
+
release the test element <part-num-ref name="test element">36</part-num-ref>
|
| 791 |
+
such that the test element <part-num-ref name="test element">36</part-num-ref>
|
| 792 |
+
remains in the connector <part-num-ref name="connector">134.</part-num-ref>
|
| 793 |
+
</p>
|
| 794 |
+
<p id="p-66" num="66">
|
| 795 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 796 |
+
A technique for loading test elements 36 onto the meter <part-num-ref name="meter">124</part-num-ref>
|
| 797 |
+
in the meter system <part-num-ref name="meter system">120</part-num-ref>
|
| 798 |
+
will be initially described with reference to FIGS. 12, <part-num-ref name="will be initially described with reference to FIGS. 12,">14,</part-num-ref>
|
| 799 |
+
<part-num-ref name="will be initially described with reference to FIGS. 12, 14,">15,</part-num-ref>
|
| 800 |
+
and <part-num-ref name="will be initially described with reference to FIGS. 12, 14, 15, and">16.</part-num-ref>
|
| 801 |
+
</p>
|
| 802 |
+
<p id="p-67" num="67">During loading, the bottom disc <part-num-ref name="bottom disc">150</part-num-ref>
|
| 803 |
+
is rotated so that the test element cavity <part-num-ref name="test element cavity">144</part-num-ref>
|
| 804 |
+
is positioned over the supply opening <part-num-ref name="supply opening">132</part-num-ref>
|
| 805 |
+
of the magazine <part-num-ref name="magazine">126.</part-num-ref>
|
| 806 |
+
In one form, the bottom disc <part-num-ref name="bottom disc">150</part-num-ref>
|
| 807 |
+
has a spring that biases the bottom disc <part-num-ref name="bottom disc">150</part-num-ref>
|
| 808 |
+
to a position where the test <boundary-data type="line-number">30 </boundary-data>
|
| 809 |
+
element cavity <part-num-ref name="test element cavity">144</part-num-ref>
|
| 810 |
+
is positioned over the magazine. In other forms, the bottom disc <part-num-ref name="bottom disc">150</part-num-ref>
|
| 811 |
+
can be manually positioned by the user and/or automatically positioned via a motor. The spring <part-num-ref name="spring">42</part-num-ref>
|
| 812 |
+
in the magazine <part-num-ref name="magazine">126</part-num-ref>
|
| 813 |
+
pushes the top-most test element <part-num-ref name="top-most test element">36</part-num-ref>
|
| 814 |
+
into <boundary-data type="header">
|
| 815 |
+
<confidence value="5">W</confidence>
|
| 816 |
+
P 23465 US<confidence value="5">/</confidence>
|
| 817 |
+
7404-744 CPS:375701 15 </boundary-data>
|
| 818 |
+
<page-break num="16"/>
|
| 819 |
+
the test element cavity <part-num-ref name="test element cavity">144.</part-num-ref>
|
| 820 |
+
Looking at FIGS. 16 and <part-num-ref name="and">17,</part-num-ref>
|
| 821 |
+
the top disc <part-num-ref name="top disc">148</part-num-ref>
|
| 822 |
+
is rotated in the counterclockwise direction <part-num-ref name="counterclockwise direction">158</part-num-ref>
|
| 823 |
+
such the lock pins <part-num-ref name="lock pins">152</part-num-ref>
|
| 824 |
+
engage the grip members <part-num-ref name="grip members">154.</part-num-ref>
|
| 825 |
+
Once the lock pins <part-num-ref name="lock pins">152</part-num-ref>
|
| 826 |
+
engage the grip members <part-num-ref name="grip members">154,</part-num-ref>
|
| 827 |
+
the grip members <part-num-ref name="grip members">154</part-num-ref>
|
| 828 |
+
squeeze against the side edges of the test elements <part-num-ref name="test elements">36</part-num-ref>
|
| 829 |
+
to hold the test element <part-num-ref name="test element">36</part-num-ref>
|
| 830 |
+
in <boundary-data type="line-number">5 </boundary-data>
|
| 831 |
+
the test element cavity <part-num-ref name="test element cavity">144.</part-num-ref>
|
| 832 |
+
As the top disc <part-num-ref name="top disc">148</part-num-ref>
|
| 833 |
+
continues to rotate, the engagement of the lock pins <part-num-ref name="lock pins">152</part-num-ref>
|
| 834 |
+
with the grip members <part-num-ref name="grip members">154</part-num-ref>
|
| 835 |
+
causes the bottom disc <part-num-ref name="bottom disc">150</part-num-ref>
|
| 836 |
+
to rotate in unison with the top disc <part-num-ref name="top disc">148.</part-num-ref>
|
| 837 |
+
The bottom surface of the bottom disc <part-num-ref name="bottom disc">150</part-num-ref>
|
| 838 |
+
holds the remaining test elements <part-num-ref name="remaining test elements">36</part-num-ref>
|
| 839 |
+
in the magazine <part-num-ref name="magazine">126</part-num-ref>
|
| 840 |
+
as the transport system <part-num-ref name="transport system">122</part-num-ref>
|
| 841 |
+
rotates. </p>
|
| 842 |
+
<p id="p-68" num="68">The transport system 122 continues to rotate in the counterclockwise direction until <boundary-data type="line-number">10 </boundary-data>
|
| 843 |
+
the connection end of the test element <part-num-ref name="test element">36</part-num-ref>
|
| 844 |
+
is inserted into the connector <part-num-ref name="connector">134</part-num-ref>
|
| 845 |
+
of the meter <part-num-ref name="meter">124.</part-num-ref>
|
| 846 |
+
At that point, the contacts in the connector <part-num-ref name="connector">134</part-num-ref>
|
| 847 |
+
engage the contacts on the test element <part-num-ref name="test element">36.</part-num-ref>
|
| 848 |
+
</p>
|
| 849 |
+
<p id="p-69" num="69">Once the test element <part-num-ref name="test element">36</part-num-ref>
|
| 850 |
+
is connected to the connector <part-num-ref name="connector">134,</part-num-ref>
|
| 851 |
+
the top disc <part-num-ref name="top disc">148</part-num-ref>
|
| 852 |
+
rotates in a clockwise direction, thereby disengaging the lock pins <part-num-ref name="lock pins">152</part-num-ref>
|
| 853 |
+
from the grip <boundary-data type="line-number">15 </boundary-data>
|
| 854 |
+
members <part-num-ref name="grip members">154.</part-num-ref>
|
| 855 |
+
The now disengaged lock pins <part-num-ref name="now disengaged lock pins">152</part-num-ref>
|
| 856 |
+
release the test element <part-num-ref name="test element">36</part-num-ref>
|
| 857 |
+
in the connector <part-num-ref name="connector">134.</part-num-ref>
|
| 858 |
+
The bottom disc <part-num-ref name="bottom disc">150</part-num-ref>
|
| 859 |
+
is then rotated in a clockwise direction so that the test element cavity <part-num-ref name="test element cavity">144</part-num-ref>
|
| 860 |
+
is positioned over the magazine <part-num-ref name="magazine">126.</part-num-ref>
|
| 861 |
+
The bottom disc <part-num-ref name="bottom disc">150</part-num-ref>
|
| 862 |
+
can be rotated in the clockwise direction manually by the user and/or automatically, such as via a return spring or a motor. Both discs <part-num-ref name="motor. Both discs">148,</part-num-ref>
|
| 863 |
+
<part-num-ref name="motor. Both discs 148,">150</part-num-ref>
|
| 864 |
+
are oriented in a manner <boundary-data type="line-number">20 </boundary-data>
|
| 865 |
+
such that their relief notches <part-num-ref name="manner such that their relief notches">142</part-num-ref>
|
| 866 |
+
align with the relief notch <part-num-ref name="relief notch">140</part-num-ref>
|
| 867 |
+
in the meter <part-num-ref name="meter">124</part-num-ref>
|
| 868 |
+
so as to permit sampling by the test element <part-num-ref name="test element">36.</part-num-ref>
|
| 869 |
+
Afterwards, the lancet in the test element <part-num-ref name="test element">36</part-num-ref>
|
| 870 |
+
can be fired to form an incision, and the fluid from the incision can be analyzed with the test element <part-num-ref name="test element">36.</part-num-ref>
|
| 871 |
+
The results from the analysis can be outputted via the output device <part-num-ref name="output device">128</part-num-ref>
|
| 872 |
+
on the meter <part-num-ref name="meter">124.</part-num-ref>
|
| 873 |
+
Once the test element <part-num-ref name="test element">36</part-num-ref>
|
| 874 |
+
is used, the test element can be <boundary-data type="line-number">25 </boundary-data>
|
| 875 |
+
manually discarded by the user. It is contemplated that the test element <part-num-ref name="test element">36</part-num-ref>
|
| 876 |
+
can be automatically discarded in other embodiments. After the used test element <part-num-ref name="used test element">36</part-num-ref>
|
| 877 |
+
is discarded, an unused test element <part-num-ref name="unused test element">36</part-num-ref>
|
| 878 |
+
from the magazine <part-num-ref name="magazine">126</part-num-ref>
|
| 879 |
+
can be loaded in the same fashion as described above. </p>
|
| 880 |
+
<p id="p-70" num="70">While the invention has been illustrated and described in detail in the drawings <boundary-data type="line-number">30 </boundary-data>
|
| 881 |
+
and foregoing description, the same is to be considered as illustrative and not restrictive in character, it being understood that only the preferred embodiment has been shown and described and that all changes and modifications that come within the <boundary-data type="header">
|
| 882 |
+
<confidence value="5">W</confidence>
|
| 883 |
+
P 23465 US<confidence value="5">/</confidence>
|
| 884 |
+
7404-744 CPS:375701 16 </boundary-data>
|
| 885 |
+
<page-break num="17"/>
|
| 886 |
+
spirit of the invention are desired to be protected. All publications, patents, and patent applications cited in this specification are herein incorporated by reference as if each individual publication, patent, or patent application was specifically and individually indicated to be incorporated by reference as set forth in its entirety herein. </p>
|
| 887 |
+
<boundary-data type="header">WP 23465 US<confidence value="5">/</confidence>
|
| 888 |
+
7404-744 CPS:375701 17 </boundary-data>
|
| 889 |
+
</description>
|
| 890 |
+
</us-patent-application>
|
| 891 |
+
|
prior_art/11276709.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>11276709</doc-number>
|
| 8 |
+
<date>2010-06-11</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">Beckett et al. S/N: 11/276,709 In the Specification Please amend paragraph [0036] as follows:</p>
|
| 14 |
+
<p id="p-2" num="2">[0036<confidence value="5">]</confidence>
|
| 15 |
+
As <confidence value="456665666">refeenee-</confidence>
|
| 16 |
+
referenced above, images 36, 38, 40, and 42 are functional images that are displayed because the physician selected a functional parameter on data window <part-num-ref name="functional parameter on data window">14.</part-num-ref>
|
| 17 |
+
In this regard, if the physician had selected cell <part-num-ref name="physician had selected cell">44,</part-num-ref>
|
| 18 |
+
the images window would have been automatically updated to display anatomical images from the medical exam conducted at Time C for the same lesion. Thus, through inputs to the quantitative data window <part-num-ref name="quantitative data window">14,</part-num-ref>
|
| 19 |
+
the physician can interactively view and analyze the several images acquired from a patient acquired in several medical exams over an extended period of time. This advantageously allows a physician to not only detect abnormalities and pathologies but also assess the effectiveness of treatment of the abnormalities and pathologies. </p>
|
| 20 |
+
<p id="p-3" num="3">
|
| 21 |
+
<confidence value="8">2</confidence>
|
| 22 |
+
</p>
|
| 23 |
+
</description>
|
| 24 |
+
</us-patent-application>
|
| 25 |
+
|