Add files using upload-large-folder tool
Browse filesThis view is limited to 50 files because it contains too many changes. See raw diff
- applicant/10511797.xml +29 -0
- applicant/10955634.xml +556 -0
- applicant/10976834.xml +86 -0
- applicant/11011244.xml +723 -0
- applicant/11055667.xml +43 -0
- applicant/11173098.xml +319 -0
- applicant/11244005.xml +326 -0
- applicant/11265967.xml +425 -0
- applicant/11291352.xml +84 -0
- applicant/11333495.xml +111 -0
- applicant/11350903.xml +439 -0
- applicant/11359645.xml +348 -0
- applicant/11399872.xml +29 -0
- applicant/11456230.xml +428 -0
- applicant/11483478.xml +601 -0
- applicant/11496208.xml +593 -0
- applicant/11526192.xml +41 -0
- applicant/11545906.xml +351 -0
- applicant/11546560.xml +25 -0
- applicant/11554842.xml +61 -0
- applicant/11607511.xml +487 -0
- applicant/11611822.xml +40 -0
- applicant/11627926.xml +153 -0
- applicant/11670633.xml +0 -0
- applicant/11676496.xml +234 -0
- applicant/11689651.xml +31 -0
- applicant/11714274.xml +1 -0
- applicant/11718006.xml +28 -0
- applicant/11729702.xml +992 -0
- applicant/11731977.xml +394 -0
- applicant/11740814.xml +555 -0
- applicant/11746263.xml +318 -0
- applicant/11761332.xml +0 -0
- applicant/11762155.xml +142 -0
- applicant/11822548.xml +877 -0
- applicant/11850534.xml +30 -0
- applicant/11851638.xml +0 -0
- applicant/11862279.xml +0 -0
- applicant/11865099.xml +1 -0
- applicant/11873683.xml +184 -0
- applicant/11918822.xml +2 -0
- applicant/11925196.xml +676 -0
- applicant/11925811.xml +0 -0
- applicant/11956403.xml +307 -0
- applicant/11972794.xml +288 -0
- applicant/12006702.xml +58 -0
- applicant/12012118.xml +428 -0
- applicant/12019445.xml +0 -0
- applicant/12022572.xml +26 -0
- applicant/12022949.xml +23 -0
applicant/10511797.xml
ADDED
|
@@ -0,0 +1,29 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>10511797</doc-number>
|
| 8 |
+
<date>2005-02-22</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">
|
| 14 |
+
<confidence value="8">A</confidence>
|
| 15 |
+
MENDMENTS TO THE SPECIFICATION: </heading>
|
| 16 |
+
<p id="p-1" num="1">Please add the following new heading and paragraph to page <part-num-ref name="following new heading and paragraph to page">1</part-num-ref>
|
| 17 |
+
as the first paragraph after the </p>
|
| 18 |
+
<heading id="h-2">TITLE:</heading>
|
| 19 |
+
<p id="p-2" num="2">Related Applications This is a continuation-in-part application of Application No. 10/126,623, filed on <part-num-ref name="continuation-in-part application of Application No. 10/126,623, filed on">22</part-num-ref>
|
| 20 |
+
April <part-num-ref name="April">2002,</part-num-ref>
|
| 21 |
+
and a continuation-in-part application of Application No. 10/319,475, filed on <part-num-ref name="continuation-in-part application of Application No. 10/319,475, filed on">16</part-num-ref>
|
| 22 |
+
December <part-num-ref name="December">2002.</part-num-ref>
|
| 23 |
+
</p>
|
| 24 |
+
<p id="p-3" num="3">
|
| 25 |
+
<confidence value="8">2</confidence>
|
| 26 |
+
KOLS.155US Preliminary Amendment </p>
|
| 27 |
+
</description>
|
| 28 |
+
</us-patent-application>
|
| 29 |
+
|
applicant/10955634.xml
ADDED
|
@@ -0,0 +1,556 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>10955634</doc-number>
|
| 8 |
+
<date>2004-09-30</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">REMOTE JACK PACK</heading>
|
| 14 |
+
<p id="p-1" num="1">Technical Field of the Invention The present invention relates to a remote jack <boundary-data type="line-number">5 </boundary-data>
|
| 15 |
+
pack that is useful in remotely connecting various local video and/or audio sources to a television. </p>
|
| 16 |
+
<p id="p-2" num="2">Background of the Invention Televisions, such as those used in facilities <boundary-data type="line-number">10 </boundary-data>
|
| 17 |
+
like hotels and motels that accommodate guests, are connected to cables that carry a variety of television program, radio program, and/or video-on-demand channels. </p>
|
| 18 |
+
<p id="p-3" num="3">It is also known to use such televisions to notify guests about the activities offered or hosted by the facility. It <boundary-data type="line-number">15 </boundary-data>
|
| 19 |
+
is further known to use such televisions to offer guests various guest services such as express check out. </p>
|
| 20 |
+
<p id="p-4" num="4">Occasionally, games and video players coupled to the televisions are even provided by the facility so that the guests can play videos or games on the televisions.</p>
|
| 21 |
+
<p id="p-5" num="5">
|
| 22 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 23 |
+
However, all such programs, information, guest services, games, and video players are provided by the facility. Currently, guests have limited ability to connect their own equipment to the televisions provided in their accommodations. For example, guests frequently <page-break num="2"/>
|
| 24 |
+
<boundary-data type="header">Attorney Docket</boundary-data>
|
| 25 |
+
<boundary-data type="header">7256</boundary-data>
|
| 26 |
+
travel with personal computers, camcorders, portable games, DVD players, and MP3 players. Guests are unable to conveniently avail themselves of the enhanced viewing and/or listening experience that these televisions offer <boundary-data type="line-number">5 </boundary-data>
|
| 27 |
+
with respect to their own personal equipment. </p>
|
| 28 |
+
<p id="p-6" num="6">The present invention relates to a remote jack pack that allows a user to remotely, easily, and conveniently connect user equipment to a television.</p>
|
| 29 |
+
<p id="p-7" num="7">
|
| 30 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 31 |
+
Summary of the Invention According to one aspect of the present invention, a remote jack pack comprises a video input jack, an audio input jack, a video output, an audio output, and a control output. The video input jack is configured to receive a <boundary-data type="line-number">15 </boundary-data>
|
| 32 |
+
video signal, and the audio input jack is configured to receive an audio signal. The video output is configured to transfer the video signal to a television, and the audio output is configured to transfer the audio signal to the television. The control output is configured to <boundary-data type="line-number">20 </boundary-data>
|
| 33 |
+
automatically supply control signals to the television upon detection of a video and/or audio signal at a respective one of the video and/or audio input jacks. The control <boundary-data type="header">-2-</boundary-data>
|
| 34 |
+
<page-break num="3"/>
|
| 35 |
+
<boundary-data type="header">Attorney Docket</boundary-data>
|
| 36 |
+
<boundary-data type="header">7256</boundary-data>
|
| 37 |
+
signals indicate the availability of the video and audio signals for processing by the television. </p>
|
| 38 |
+
<p id="p-8" num="8">According to another aspect of the present invention, a television comprises a tuner arranged to <boundary-data type="line-number">5 </boundary-data>
|
| 39 |
+
supply video and audio signals of a selected channel, a video connector arranged to receive video from a remote jack pack, an audio connector arranged to receive audio from the remote jack pack, a control connector arranged to receive control signals from the remote jack pack, and a <boundary-data type="line-number">10 </boundary-data>
|
| 40 |
+
processor responsive to the control signals to selectively control display of the video and audio signals from the tuner and the video and audio signals from the video and audio connectors. </p>
|
| 41 |
+
<p id="p-9" num="9">
|
| 42 |
+
<confidence value="2">'</confidence>
|
| 43 |
+
According to still another aspect of the present <boundary-data type="line-number">15 </boundary-data>
|
| 44 |
+
invention, a system comprises a remote jack pack and a television. The remote jack pack comprises a video input jack configured to receive a video signal, an audio input jack configured to receive an audio signal, a video output configured to transfer the video signal to the television, <boundary-data type="line-number">20 </boundary-data>
|
| 45 |
+
an audio output configured to transfer the audio signal to the television, and a control output configured to supply control signals to the television. The control signals indicate the availability of the video and audio signals <boundary-data type="header">-3-</boundary-data>
|
| 46 |
+
<page-break num="4"/>
|
| 47 |
+
<boundary-data type="header">Attorney Docket</boundary-data>
|
| 48 |
+
<boundary-data type="header">7256</boundary-data>
|
| 49 |
+
for processing by the television. The television comprises a tuner arranged to supply video and audio signals of a selected channel, a video connector connected to the video output of the remote jack pack to receive the video signal <boundary-data type="line-number">5 </boundary-data>
|
| 50 |
+
from a remote jack pack, an audio connector connected to the audio output of the remote jack pack to receive the audio signal from the remote jack pack, a control connector connected to the control output of the remote jack pack to receive the control signals from the remote jack pack, and <boundary-data type="line-number">10 </boundary-data>
|
| 51 |
+
a processor responsive to the control signals to selectively control display of the video and audio signals from the tuner and the video and audio signals from the video and audio connectors. </p>
|
| 52 |
+
<p id="p-10" num="10">According to yet another aspect of the present <boundary-data type="line-number">15 </boundary-data>
|
| 53 |
+
invention, a television comprises at least first, second, and third control terminals and<confidence value="5">-</confidence>
|
| 54 |
+
a processor. The at least first, second, and third control terminals are arranged to receive corresponding first, second, and third control signals from a source external of the television. The <boundary-data type="line-number">20 </boundary-data>
|
| 55 |
+
processor selectively controls display of audio signals from first and second audio sources in response to only the first control signal and selectively controls display of <boundary-data type="header">-4-</boundary-data>
|
| 56 |
+
<page-break num="5"/>
|
| 57 |
+
<boundary-data type="header">Attorney Docket</boundary-data>
|
| 58 |
+
<boundary-data type="header">7256</boundary-data>
|
| 59 |
+
video signals from first and second video sources in response to only the second and third control signals. </p>
|
| 60 |
+
<p id="p-11" num="11">Brief Description of the Drawings <boundary-data type="line-number">5 </boundary-data>
|
| 61 |
+
These and other features and advantages will become more apparent from a detailed consideration of the invention when taken in conjunction with the drawings in which: </p>
|
| 62 |
+
<p id="p-12" num="12">Figure 1 illustrates a remote jack pack connected <boundary-data type="line-number">10 </boundary-data>
|
| 63 |
+
to a television according to one embodiment of the present invention; </p>
|
| 64 |
+
<p id="p-13" num="13">Figure 2 illustrates the audio portion of the remote jack pack shown in Figure 1;</p>
|
| 65 |
+
<p id="p-14" num="14">Figure 3 illustrates the video portion of the <boundary-data type="line-number">15 </boundary-data>
|
| 66 |
+
remote jack pack shown in Figure 1; </p>
|
| 67 |
+
<p id="p-15" num="15">Figure 4 illustrates video and audio control signals that are coupled from the remote jack pack to the television of Figure 1; and, Figure 5 illustrates an example of a television <boundary-data type="line-number">20 </boundary-data>
|
| 68 |
+
that can be used for the television of Figure 1. </p>
|
| 69 |
+
<p id="p-16" num="16">Detailed Description <boundary-data type="header">-5-</boundary-data>
|
| 70 |
+
<page-break num="6"/>
|
| 71 |
+
<boundary-data type="header">Attorney Docket</boundary-data>
|
| 72 |
+
<boundary-data type="header">7256</boundary-data>
|
| 73 |
+
As shown in Figure 1, a remote jack pack <part-num-ref name="remote jack pack">10</part-num-ref>
|
| 74 |
+
is remotely coupled to a television <part-num-ref name="television">12</part-num-ref>
|
| 75 |
+
by electrical lines <part-num-ref name="by electrical lines">14.</part-num-ref>
|
| 76 |
+
</p>
|
| 77 |
+
<p id="p-17" num="17">The remote jack pack 10, for example, may be attached to a mounting structure such as a desk, table, or stand that is <boundary-data type="line-number">5 </boundary-data>
|
| 78 |
+
remotely located from the television <part-num-ref name="television">12.</part-num-ref>
|
| 79 |
+
This mounting structure can conveniently, although not necessarily, support any of the equipment to be connected to the remote jack pack <part-num-ref name="remote jack pack">10.</part-num-ref>
|
| 80 |
+
</p>
|
| 81 |
+
<p id="p-18" num="18">The television 12 may be an analog television <boundary-data type="line-number">10 </boundary-data>
|
| 82 |
+
such as one conforming to the NTSC standard, a digital television such as one conforming to the ATSC digital television standard, or other television that is suitably equipped to receive the electrical lines <part-num-ref name="electrical lines">14.</part-num-ref>
|
| 83 |
+
The electrical lines <part-num-ref name="electrical lines">14</part-num-ref>
|
| 84 |
+
may include any number and type of <boundary-data type="line-number">15 </boundary-data>
|
| 85 |
+
electrical lines dependent upon the types of equipment to be coupled through the remote jack pack <part-num-ref name="remote jack pack">10</part-num-ref>
|
| 86 |
+
to the television <part-num-ref name="television">12.</part-num-ref>
|
| 87 |
+
</p>
|
| 88 |
+
<p id="p-19" num="19">The remote jack pack 10 supports a 3.5 mm audio input jack <part-num-ref name="3.5 mm audio input jack">16,</part-num-ref>
|
| 89 |
+
left and right audio input jacks <part-num-ref name="3.5 mm audio input jack 16, left and right audio input jacks">18</part-num-ref>
|
| 90 |
+
and <part-num-ref name="and">20,</part-num-ref>
|
| 91 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 92 |
+
a super VHS video input jack <part-num-ref name="super VHS video input jack">22,</part-num-ref>
|
| 93 |
+
a composite video input jack <part-num-ref name="composite video input jack">24,</part-num-ref>
|
| 94 |
+
and an RGB input jack <part-num-ref name="RGB input jack">26.</part-num-ref>
|
| 95 |
+
A radio audio input jack <part-num-ref name="radio audio input jack">28</part-num-ref>
|
| 96 |
+
is capable of accepting audio signals from a radio or other device. Because the radio audio input jack <part-num-ref name="radio audio input jack">28</part-num-ref>
|
| 97 |
+
may <boundary-data type="header">-6-</boundary-data>
|
| 98 |
+
<page-break num="7"/>
|
| 99 |
+
<boundary-data type="header">Attorney Docket</boundary-data>
|
| 100 |
+
<boundary-data type="header">7256</boundary-data>
|
| 101 |
+
be supported on the back of the remote jack pack <part-num-ref name="remote jack pack">10,</part-num-ref>
|
| 102 |
+
it is shown in phantom. </p>
|
| 103 |
+
<p id="p-20" num="20">The 3.5 mm audio input jack 16 is capable of receiving a corresponding plug from an MP3 player, CD, or <boundary-data type="line-number">5 </boundary-data>
|
| 104 |
+
radio. Accordingly, a user can play audio from any of these sources through the speakers of the television <part-num-ref name="television">12.</part-num-ref>
|
| 105 |
+
</p>
|
| 106 |
+
<p id="p-21" num="21">The left and right audio input jacks 18 and <part-num-ref name="and">20</part-num-ref>
|
| 107 |
+
are capable of receiving corresponding audio left and right plugs from audio equipment, a VCR, a DVD player, etc. </p>
|
| 108 |
+
<p id="p-22" num="22">
|
| 109 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 110 |
+
Accordingly, a user can play the audio portion of a video cassette or DVD or the audio from audio equipment through the speakers of the television <part-num-ref name="television">12.</part-num-ref>
|
| 111 |
+
</p>
|
| 112 |
+
<p id="p-23" num="23">The super VHS video input jack 22 is capable of receiving video super VHS plugs from a super VHS player or <boundary-data type="line-number">15 </boundary-data>
|
| 113 |
+
DVD player. The audio from these devices can be plugged into one of the audio jacks described above. Accordingly, a user can play super VHS video and audio on the television <part-num-ref name="television">12.</part-num-ref>
|
| 114 |
+
</p>
|
| 115 |
+
<p id="p-24" num="24">The RGB input jack 26 is capable of receiving a <boundary-data type="line-number">20 </boundary-data>
|
| 116 |
+
plug from a computer or set top box so that a user can play the video of a game, a DVD, etc. from a user's computer on the television <part-num-ref name="television">12</part-num-ref>
|
| 117 |
+
or the video from a set top box on the <boundary-data type="header">-7-</boundary-data>
|
| 118 |
+
<page-break num="8"/>
|
| 119 |
+
<boundary-data type="header">Attorney Docket</boundary-data>
|
| 120 |
+
<boundary-data type="header">7256</boundary-data>
|
| 121 |
+
television <part-num-ref name="television">12.</part-num-ref>
|
| 122 |
+
The audio from the computer or set top box can be plugged into one of the audio jacks described above. </p>
|
| 123 |
+
<p id="p-25" num="25">The composite video input jack 24 is capable of receiving video from a VCR or DVD. Accordingly, a user can <boundary-data type="line-number">5 </boundary-data>
|
| 124 |
+
play the video of a video cassette or DVD on the television <part-num-ref name="television">12.</part-num-ref>
|
| 125 |
+
</p>
|
| 126 |
+
<p id="p-26" num="26">The remote jack pack 10 may have other jacks such as a telephone jack <part-num-ref name="telephone jack">30,</part-num-ref>
|
| 127 |
+
a high speed internet connection jack <part-num-ref name="high speed internet connection jack">32,</part-num-ref>
|
| 128 |
+
and AC outlets <part-num-ref name="high speed internet connection jack 32, and AC outlets">34</part-num-ref>
|
| 129 |
+
and <part-num-ref name="and">36.</part-num-ref>
|
| 130 |
+
Accordingly, the user <boundary-data type="line-number">10 </boundary-data>
|
| 131 |
+
can connect a computer or other equipment to the telephone jack <part-num-ref name="telephone jack">30</part-num-ref>
|
| 132 |
+
and to the high speed internet connection jack <part-num-ref name="high speed internet connection jack">32</part-num-ref>
|
| 133 |
+
and can power various equipment such as a computer by way of the AC outlets <part-num-ref name="AC outlets">34</part-num-ref>
|
| 134 |
+
and <part-num-ref name="and">36.</part-num-ref>
|
| 135 |
+
For these purposes, the remote jack pack <part-num-ref name="remote jack pack">10</part-num-ref>
|
| 136 |
+
interconnects the telephone jack <part-num-ref name="telephone jack">30</part-num-ref>
|
| 137 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 138 |
+
with a telephone line <part-num-ref name="telephone line">38,</part-num-ref>
|
| 139 |
+
interconnects the high speed internet connection jack <part-num-ref name="high speed internet connection jack">32</part-num-ref>
|
| 140 |
+
with a high speed internet access line <part-num-ref name="high speed internet access line">40,</part-num-ref>
|
| 141 |
+
and supplies AC power from AC lines <part-num-ref name="high speed internet access line 40, and supplies AC power from AC lines">42</part-num-ref>
|
| 142 |
+
to the AC outlets <part-num-ref name="AC outlets">34</part-num-ref>
|
| 143 |
+
and <part-num-ref name="and">36.</part-num-ref>
|
| 144 |
+
</p>
|
| 145 |
+
<p id="p-27" num="27">The electrical lines 14 include three RGB lines <boundary-data type="line-number">
|
| 146 |
+
<confidence value="88">20</confidence>
|
| 147 |
+
</boundary-data>
|
| 148 |
+
<part-num-ref name="include three RGB lines">44,</part-num-ref>
|
| 149 |
+
a composite video line <part-num-ref name="composite video line">46,</part-num-ref>
|
| 150 |
+
two (left and right) audio lines <part-num-ref name="composite video line 46, two (left and right) audio lines">48,</part-num-ref>
|
| 151 |
+
and four control lines <part-num-ref name="composite video line 46, two (left and right) audio lines 48, and four control lines">50.</part-num-ref>
|
| 152 |
+
The three RGB lines <part-num-ref name="three RGB lines">44</part-num-ref>
|
| 153 |
+
connect the red (R), green (G), and blue (B) signals from the RGB input jack <part-num-ref name="RGB input jack">26</part-num-ref>
|
| 154 |
+
to RGB inputs of the television <boundary-data type="header">-8-</boundary-data>
|
| 155 |
+
<page-break num="9"/>
|
| 156 |
+
<boundary-data type="header">Attorney Docket</boundary-data>
|
| 157 |
+
<boundary-data type="header">7256</boundary-data>
|
| 158 |
+
<part-num-ref name="television">12.</part-num-ref>
|
| 159 |
+
The composite video line <part-num-ref name="composite video line">46</part-num-ref>
|
| 160 |
+
connects the composite video signal from the composite video input jack <part-num-ref name="composite video input jack">24</part-num-ref>
|
| 161 |
+
to a video input of the television <part-num-ref name="television">12.</part-num-ref>
|
| 162 |
+
As explained below, the composite video line <part-num-ref name="composite video line">46</part-num-ref>
|
| 163 |
+
also connects the super VHS video <boundary-data type="line-number">5 </boundary-data>
|
| 164 |
+
input jack <part-num-ref name="super VHS video input jack">22</part-num-ref>
|
| 165 |
+
to a video input of the television <part-num-ref name="television">12.</part-num-ref>
|
| 166 |
+
The audio lines <part-num-ref name="audio lines">48</part-num-ref>
|
| 167 |
+
connect the audio signals from the 3.5 <confidence value="66">mm</confidence>
|
| 168 |
+
audio input jack <part-num-ref name="3.5 mm audio input jack">16,</part-num-ref>
|
| 169 |
+
from the left and right audio input jacks <part-num-ref name="left and right audio input jacks">18</part-num-ref>
|
| 170 |
+
and <part-num-ref name="and">20,</part-num-ref>
|
| 171 |
+
and from the radio audio input jack <part-num-ref name="radio audio input jack">28</part-num-ref>
|
| 172 |
+
to audio inputs of the television <part-num-ref name="television">12.</part-num-ref>
|
| 173 |
+
The control lines <part-num-ref name="control lines">50</part-num-ref>
|
| 174 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 175 |
+
connect various control signals from the remote jack pack <part-num-ref name="remote jack pack">10</part-num-ref>
|
| 176 |
+
to the television <part-num-ref name="television">12,</part-num-ref>
|
| 177 |
+
as explained below. </p>
|
| 178 |
+
<p id="p-28" num="28">The remote jack pack 10 includes an audio portion <part-num-ref name="audio portion">52</part-num-ref>
|
| 179 |
+
as shown in Figure 2. The audio portion <part-num-ref name="audio portion">52</part-num-ref>
|
| 180 |
+
of the remote jack pack <part-num-ref name="remote jack pack">10</part-num-ref>
|
| 181 |
+
has the 3.5 mm audio input jack <part-num-ref name="3.5 mm audio input jack">16,</part-num-ref>
|
| 182 |
+
the <boundary-data type="line-number">15 </boundary-data>
|
| 183 |
+
left and right audio input jacks <part-num-ref name="left and right audio input jacks">18</part-num-ref>
|
| 184 |
+
and <part-num-ref name="and">20,</part-num-ref>
|
| 185 |
+
and the radio audio input jack <part-num-ref name="radio audio input jack">28</part-num-ref>
|
| 186 |
+
as shown. The audio portion <part-num-ref name="audio portion">52</part-num-ref>
|
| 187 |
+
of the remote jack pack <part-num-ref name="remote jack pack">10</part-num-ref>
|
| 188 |
+
further includes switches <part-num-ref name="further includes switches">54</part-num-ref>
|
| 189 |
+
and <part-num-ref name="and">56</part-num-ref>
|
| 190 |
+
and an audio detector <part-num-ref name="audio detector">58.</part-num-ref>
|
| 191 |
+
The switch <part-num-ref name="switch">54</part-num-ref>
|
| 192 |
+
cooperates with the 3.5 mm audio input jack <part-num-ref name="3.5 mm audio input jack">16,</part-num-ref>
|
| 193 |
+
and the switch <part-num-ref name="switch">56</part-num-ref>
|
| 194 |
+
is controlled <boundary-data type="line-number">20 </boundary-data>
|
| 195 |
+
by the audio detector <part-num-ref name="audio detector">58.</part-num-ref>
|
| 196 |
+
</p>
|
| 197 |
+
<p id="p-29" num="29">The contacts of the switch <part-num-ref name="switch">54</part-num-ref>
|
| 198 |
+
respond to the insertion of an audio plug into the 3.5 mm audio input jack <part-num-ref name="3.5 mm audio input jack">16</part-num-ref>
|
| 199 |
+
by opening so that the inserted audio plug is connected <boundary-data type="header">-9-</boundary-data>
|
| 200 |
+
<page-break num="10"/>
|
| 201 |
+
<boundary-data type="header">Attorney Docket</boundary-data>
|
| 202 |
+
<boundary-data type="header">7256</boundary-data>
|
| 203 |
+
to the switch <part-num-ref name="switch">56</part-num-ref>
|
| 204 |
+
and so that the left and right audio input jacks <part-num-ref name="left and right audio input jacks">18</part-num-ref>
|
| 205 |
+
and <part-num-ref name="and">20</part-num-ref>
|
| 206 |
+
are not connected to the switch <part-num-ref name="switch">56.</part-num-ref>
|
| 207 |
+
At the same time, the audio detector <part-num-ref name="audio detector">58</part-num-ref>
|
| 208 |
+
detects that there is an audio signal on the 3.5 mm audio input jack <part-num-ref name="3.5 mm audio input jack">16</part-num-ref>
|
| 209 |
+
and, <boundary-data type="line-number">5 </boundary-data>
|
| 210 |
+
consequently, controls the switch <part-num-ref name="switch">56</part-num-ref>
|
| 211 |
+
to couple this audio signal from the 3.5 mm audio input jack <part-num-ref name="3.5 mm audio input jack">16</part-num-ref>
|
| 212 |
+
to left and right audio output jacks <part-num-ref name="to left and right audio output jacks">60</part-num-ref>
|
| 213 |
+
and <part-num-ref name="and">62</part-num-ref>
|
| 214 |
+
of the audio portion <part-num-ref name="audio portion">52</part-num-ref>
|
| 215 |
+
of the remote jack pack <part-num-ref name="remote jack pack">10.</part-num-ref>
|
| 216 |
+
The left and right audio output jacks <part-num-ref name="left and right audio output jacks">60</part-num-ref>
|
| 217 |
+
and <part-num-ref name="and">62</part-num-ref>
|
| 218 |
+
connect to the audio lines <part-num-ref name="audio lines">48.</part-num-ref>
|
| 219 |
+
</p>
|
| 220 |
+
<p id="p-30" num="30">
|
| 221 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 222 |
+
Alternatively, when an audio plug is not inserted into the 3.5 mm audio input jack <part-num-ref name="3.5 mm audio input jack">16,</part-num-ref>
|
| 223 |
+
the contacts of the switch <part-num-ref name="switch">54</part-num-ref>
|
| 224 |
+
remain in their original positions. Accordingly, audio plugs inserted into the left and right audio input jacks <part-num-ref name="left and right audio input jacks">18</part-num-ref>
|
| 225 |
+
and <part-num-ref name="and">20</part-num-ref>
|
| 226 |
+
are connected to the switch <part-num-ref name="switch">56</part-num-ref>
|
| 227 |
+
and the 3.5 <boundary-data type="line-number">15 </boundary-data>
|
| 228 |
+
mm audio input jack <part-num-ref name="3.5 mm audio input jack">16</part-num-ref>
|
| 229 |
+
is not connected to the switch <part-num-ref name="switch">56.</part-num-ref>
|
| 230 |
+
</p>
|
| 231 |
+
<p id="p-31" num="31">At the same time, the audio detector <part-num-ref name="audio detector">58</part-num-ref>
|
| 232 |
+
detects that there is an audio signal on the left and right audio input jacks <part-num-ref name="left and right audio input jacks">18</part-num-ref>
|
| 233 |
+
and <part-num-ref name="and">20</part-num-ref>
|
| 234 |
+
and, consequently, controls the switch <part-num-ref name="switch">56</part-num-ref>
|
| 235 |
+
to couple this audio signal from the left and right audio <boundary-data type="line-number">20 </boundary-data>
|
| 236 |
+
input jacks <part-num-ref name="left and right audio input jacks">18</part-num-ref>
|
| 237 |
+
and <part-num-ref name="and">20</part-num-ref>
|
| 238 |
+
to the left and right audio output jacks <part-num-ref name="left and right audio output jacks">60</part-num-ref>
|
| 239 |
+
and <part-num-ref name="and">62</part-num-ref>
|
| 240 |
+
and then on to the audio lines <part-num-ref name="audio lines">48.</part-num-ref>
|
| 241 |
+
</p>
|
| 242 |
+
<p id="p-32" num="32">When a signal is present on the radio audio input jack <part-num-ref name="radio audio input jack">28,</part-num-ref>
|
| 243 |
+
the audio detector <part-num-ref name="audio detector">58</part-num-ref>
|
| 244 |
+
detects that there is an <boundary-data type="header">-10-</boundary-data>
|
| 245 |
+
<page-break num="11"/>
|
| 246 |
+
<boundary-data type="header">Attorney Docket</boundary-data>
|
| 247 |
+
<boundary-data type="header">7256</boundary-data>
|
| 248 |
+
audio signal on the radio audio input jack <part-num-ref name="radio audio input jack">28</part-num-ref>
|
| 249 |
+
and, consequently, controls the switch <part-num-ref name="switch">56</part-num-ref>
|
| 250 |
+
to couple this audio signal from the radio audio input jack <part-num-ref name="radio audio input jack">28</part-num-ref>
|
| 251 |
+
to the left and right audio output jacks <part-num-ref name="left and right audio output jacks">60</part-num-ref>
|
| 252 |
+
and <part-num-ref name="and">62</part-num-ref>
|
| 253 |
+
and then on to the audio <boundary-data type="line-number">5 </boundary-data>
|
| 254 |
+
lines <part-num-ref name="audio lines">48.</part-num-ref>
|
| 255 |
+
</p>
|
| 256 |
+
<p id="p-33" num="33">The audio detector 58, such as a threshold comparator and a microprocessor, also supplies control signals, as explained more fully below, over appropriate ones of the control lines <part-num-ref name="control lines">50</part-num-ref>
|
| 257 |
+
to condition the television <part-num-ref name="television">12</part-num-ref>
|
| 258 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 259 |
+
to couple its appropriate audio sources to the audio processors of the television <part-num-ref name="television">12.</part-num-ref>
|
| 260 |
+
</p>
|
| 261 |
+
<p id="p-34" num="34">The audio detector 58 may be arranged to resolve the contention that is created when two or more plugs are inserted into the 3.5 mm audio input jack <part-num-ref name="3.5 mm audio input jack">16,</part-num-ref>
|
| 262 |
+
the left and <boundary-data type="line-number">15 </boundary-data>
|
| 263 |
+
right audio input jacks <part-num-ref name="left and right audio input jacks">18</part-num-ref>
|
| 264 |
+
and <part-num-ref name="and">20,</part-num-ref>
|
| 265 |
+
and/or the radio audio input jack <part-num-ref name="radio audio input jack">28</part-num-ref>
|
| 266 |
+
during overlapping periods of time. In this case, the audio detector <part-num-ref name="audio detector">58</part-num-ref>
|
| 267 |
+
may be arranged or programmed to select one of the contending audio inputs for supply to the left and right audio output jacks <part-num-ref name="left and right audio output jacks">60</part-num-ref>
|
| 268 |
+
and <part-num-ref name="and">62.</part-num-ref>
|
| 269 |
+
For this <boundary-data type="line-number">20 </boundary-data>
|
| 270 |
+
purpose, this audio input selection may be implemented according to any desired prioritization model. </p>
|
| 271 |
+
<p id="p-35" num="35">The remote jack pack 10 further includes a video portion <part-num-ref name="video portion">64</part-num-ref>
|
| 272 |
+
as shown in Figure 3. The video portion <part-num-ref name="video portion">64</part-num-ref>
|
| 273 |
+
of <boundary-data type="header">-11-</boundary-data>
|
| 274 |
+
<page-break num="12"/>
|
| 275 |
+
<boundary-data type="header">Attorney Docket</boundary-data>
|
| 276 |
+
<boundary-data type="header">7256</boundary-data>
|
| 277 |
+
the remote jack pack <part-num-ref name="remote jack pack">10</part-num-ref>
|
| 278 |
+
has the super VHS video input jack <part-num-ref name="super VHS video input jack">22,</part-num-ref>
|
| 279 |
+
the composite video input jack <part-num-ref name="composite video input jack">24,</part-num-ref>
|
| 280 |
+
and the RGB input jack <part-num-ref name="RGB input jack">26,</part-num-ref>
|
| 281 |
+
as shown. The video portion <part-num-ref name="video portion">64</part-num-ref>
|
| 282 |
+
of the remote jack pack <part-num-ref name="remote jack pack">10</part-num-ref>
|
| 283 |
+
further includes a switch <part-num-ref name="switch">66,</part-num-ref>
|
| 284 |
+
a video detector <part-num-ref name="video detector">68,</part-num-ref>
|
| 285 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 286 |
+
and a combiner <part-num-ref name="combiner">70.</part-num-ref>
|
| 287 |
+
The switch <part-num-ref name="switch">66</part-num-ref>
|
| 288 |
+
is controlled by the video detector <part-num-ref name="video detector">68.</part-num-ref>
|
| 289 |
+
</p>
|
| 290 |
+
<p id="p-36" num="36">When a super VHS video plug is inserted into the super VHS video input jack<confidence value="2">-</confidence>
|
| 291 |
+
22, the combiner <part-num-ref name="combiner">70,</part-num-ref>
|
| 292 |
+
such as a summing circuit, combines the luminance and chrominance <boundary-data type="line-number">10 </boundary-data>
|
| 293 |
+
signals of the super VHS signal into a composite video signal. The video detector <part-num-ref name="video detector">68</part-num-ref>
|
| 294 |
+
detects that there is a composite video signal at the output of the combiner <part-num-ref name="combiner">70</part-num-ref>
|
| 295 |
+
and, consequently, controls the switch <part-num-ref name="switch">66</part-num-ref>
|
| 296 |
+
to couple this composite video signal from the combiner <part-num-ref name="combiner">70</part-num-ref>
|
| 297 |
+
to a composite <boundary-data type="line-number">15 </boundary-data>
|
| 298 |
+
video output jack <part-num-ref name="composite video output jack">72</part-num-ref>
|
| 299 |
+
in the video portion <part-num-ref name="video portion">64</part-num-ref>
|
| 300 |
+
of the remote jack pack <part-num-ref name="remote jack pack">10.</part-num-ref>
|
| 301 |
+
The composite video output jack <part-num-ref name="composite video output jack">72</part-num-ref>
|
| 302 |
+
connects to the composite video line <part-num-ref name="composite video line">46.</part-num-ref>
|
| 303 |
+
</p>
|
| 304 |
+
<p id="p-37" num="37">When a composite video plug is inserted into the composite video input jack <part-num-ref name="composite video input jack">24,</part-num-ref>
|
| 305 |
+
the video detector <part-num-ref name="video detector">68</part-num-ref>
|
| 306 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 307 |
+
detects that there is a video signal on the composite video input jack <part-num-ref name="composite video input jack">24</part-num-ref>
|
| 308 |
+
and, consequently, controls the switch <part-num-ref name="switch">66</part-num-ref>
|
| 309 |
+
to couple this video signal from the composite video input <boundary-data type="header">-12-</boundary-data>
|
| 310 |
+
<page-break num="13"/>
|
| 311 |
+
<boundary-data type="header">Attorney Docket</boundary-data>
|
| 312 |
+
<boundary-data type="header">7256</boundary-data>
|
| 313 |
+
jack <part-num-ref name="composite video input jack">24</part-num-ref>
|
| 314 |
+
to the composite video output jack <part-num-ref name="composite video output jack">72</part-num-ref>
|
| 315 |
+
and then on to the composite video line <part-num-ref name="composite video line">46.</part-num-ref>
|
| 316 |
+
</p>
|
| 317 |
+
<p id="p-38" num="38">When an RGB plug is inserted into the RGB input jack <part-num-ref name="RGB input jack">26,</part-num-ref>
|
| 318 |
+
the resulting signal on the RGB input jack <part-num-ref name="RGB input jack">26</part-num-ref>
|
| 319 |
+
is <boundary-data type="line-number">5 </boundary-data>
|
| 320 |
+
coupled directly through the remote jack pack <part-num-ref name="remote jack pack">10</part-num-ref>
|
| 321 |
+
to an RGB output jack <part-num-ref name="RGB output jack">74</part-num-ref>
|
| 322 |
+
and then on to the RGB lines <part-num-ref name="RGB lines">44.</part-num-ref>
|
| 323 |
+
</p>
|
| 324 |
+
<p id="p-39" num="39">The video detector 68, such as sync detector and a microprocessor, also supplies control signals, explained more fully below, over appropriate ones of the control <boundary-data type="line-number">10 </boundary-data>
|
| 325 |
+
lines <part-num-ref name="control lines">50</part-num-ref>
|
| 326 |
+
to condition the television <part-num-ref name="television">12</part-num-ref>
|
| 327 |
+
to couple its appropriate video sources to the video processors of the television <part-num-ref name="television">12.</part-num-ref>
|
| 328 |
+
Assuming that the audio detector <part-num-ref name="audio detector">58</part-num-ref>
|
| 329 |
+
and the video detector <part-num-ref name="video detector">68</part-num-ref>
|
| 330 |
+
have microprocessors as described above, the audio detector <part-num-ref name="audio detector">58</part-num-ref>
|
| 331 |
+
and the video detector <part-num-ref name="video detector">68</part-num-ref>
|
| 332 |
+
may share <boundary-data type="line-number">15 </boundary-data>
|
| 333 |
+
the same microprocessor. These microprocessors or shared microprocessor may perform other functions, such as other switching functions, than those described herein. </p>
|
| 334 |
+
<p id="p-40" num="40">The video detector 68 may be arranged to resolve the contention that is created when plugs are inserted into <boundary-data type="line-number">20 </boundary-data>
|
| 335 |
+
both the super VHS video input jack <part-num-ref name="super VHS video input jack">22</part-num-ref>
|
| 336 |
+
and the composite video input jack <part-num-ref name="composite video input jack">24</part-num-ref>
|
| 337 |
+
during overlapping periods of time. In this case, the video detector <part-num-ref name="video detector">68</part-num-ref>
|
| 338 |
+
may be arranged or programmed to select one of the contending video inputs for <boundary-data type="header">-13-</boundary-data>
|
| 339 |
+
<page-break num="14"/>
|
| 340 |
+
<boundary-data type="header">Attorney Docket</boundary-data>
|
| 341 |
+
<boundary-data type="header">7256</boundary-data>
|
| 342 |
+
supply to the composite video output jack <part-num-ref name="composite video output jack">72.</part-num-ref>
|
| 343 |
+
For this purpose, this video input selection may be implement according to any desired prioritization model. </p>
|
| 344 |
+
<p id="p-41" num="41">Figure 4 illustrates the video and audio control <boundary-data type="line-number">5 </boundary-data>
|
| 345 |
+
signals that are coupled over corresponding ones of the control lines <part-num-ref name="control lines">50</part-num-ref>
|
| 346 |
+
to the television <part-num-ref name="television">12.</part-num-ref>
|
| 347 |
+
As can be seen in Figure 4, the television <part-num-ref name="television">12</part-num-ref>
|
| 348 |
+
has six terminals. These six terminals may be formed as one or more jacks, pins, etc. </p>
|
| 349 |
+
<p id="p-42" num="42">Each of these terminals is connected to a corresponding one <boundary-data type="line-number">10 </boundary-data>
|
| 350 |
+
of the control lines <part-num-ref name="control lines">50.</part-num-ref>
|
| 351 |
+
There four control lines <part-num-ref name="control lines 50. There four control lines">50</part-num-ref>
|
| 352 |
+
are designated 0-3 in Figure 4. </p>
|
| 353 |
+
<p id="p-43" num="43">Thus, when the video detector <part-num-ref name="video detector">68</part-num-ref>
|
| 354 |
+
detects no signal on the super VHS video input jack <part-num-ref name="super VHS video input jack">22,</part-num-ref>
|
| 355 |
+
the RGB input jack <part-num-ref name="RGB input jack">26,</part-num-ref>
|
| 356 |
+
and the composite video input jack <part-num-ref name="composite video input jack">24,</part-num-ref>
|
| 357 |
+
it drives <boundary-data type="line-number">15 </boundary-data>
|
| 358 |
+
the control lines <part-num-ref name="control lines">0</part-num-ref>
|
| 359 |
+
and <part-num-ref name="and">1</part-num-ref>
|
| 360 |
+
high. In response to these control signals, the television <part-num-ref name="television">12</part-num-ref>
|
| 361 |
+
supplies the video output from its own tuner to its video processor for display to the user. A signal on control <confidence value="8">l</confidence>
|
| 362 |
+
ine <part-num-ref name="signal on control line">3</part-num-ref>
|
| 363 |
+
is not controlling as indicated by the x, and a signal on control <boundary-data type="line-number">20 </boundary-data>
|
| 364 |
+
line <part-num-ref name="signal on control line">2</part-num-ref>
|
| 365 |
+
controls audio as discussed below. </p>
|
| 366 |
+
<p id="p-44" num="44">When the video detector <part-num-ref name="video detector">68</part-num-ref>
|
| 367 |
+
detects an R<confidence value="5">G</confidence>
|
| 368 |
+
B signal on the RGB input jack <part-num-ref name="RGB input jack">26,</part-num-ref>
|
| 369 |
+
it drives the control line <part-num-ref name="control line">0</part-num-ref>
|
| 370 |
+
low and the control line <part-num-ref name="control line">1</part-num-ref>
|
| 371 |
+
high. In response to these control <boundary-data type="header">-14-</boundary-data>
|
| 372 |
+
<page-break num="15"/>
|
| 373 |
+
<boundary-data type="header">Attorney Docket</boundary-data>
|
| 374 |
+
<boundary-data type="header">7256</boundary-data>
|
| 375 |
+
signals, the television <part-num-ref name="television">12</part-num-ref>
|
| 376 |
+
supplies the RGB video on the RGB lines <part-num-ref name="RGB lines">44</part-num-ref>
|
| 377 |
+
to its video processor for display to the user. Again, a signal on control line <part-num-ref name="signal on control line">3</part-num-ref>
|
| 378 |
+
is not controlling as indicated by the x, and a signal on control line <part-num-ref name="signal on control line">2</part-num-ref>
|
| 379 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 380 |
+
controls audio as discussed below. </p>
|
| 381 |
+
<p id="p-45" num="45">When the video detector <part-num-ref name="video detector">68</part-num-ref>
|
| 382 |
+
detects a composite video signal either on the composite video input jack <part-num-ref name="composite video input jack">24</part-num-ref>
|
| 383 |
+
or at the output of the combiner <part-num-ref name="combiner">70,</part-num-ref>
|
| 384 |
+
it drives the control line <part-num-ref name="control line">0</part-num-ref>
|
| 385 |
+
high and the control line <part-num-ref name="control line">1</part-num-ref>
|
| 386 |
+
low. In response to <boundary-data type="line-number">10 </boundary-data>
|
| 387 |
+
these control signals, the television <part-num-ref name="television">12</part-num-ref>
|
| 388 |
+
supplies the composite video on the composite video line <part-num-ref name="composite video line">46</part-num-ref>
|
| 389 |
+
to its video processor for display to the user. Still again, a signal on control line <part-num-ref name="signal on control line">3</part-num-ref>
|
| 390 |
+
is not controlling as indicated by the x, and a signal on control line <part-num-ref name="signal on control line">2</part-num-ref>
|
| 391 |
+
controls audio as discussed <boundary-data type="line-number">15 </boundary-data>
|
| 392 |
+
below. </p>
|
| 393 |
+
<p id="p-46" num="46">When the audio detector <part-num-ref name="audio detector">58</part-num-ref>
|
| 394 |
+
detects no signal on the 3.5 mm audio input jack <part-num-ref name="3.5 mm audio input jack">16,</part-num-ref>
|
| 395 |
+
the left and right audio input jacks <part-num-ref name="left and right audio input jacks">18</part-num-ref>
|
| 396 |
+
and <part-num-ref name="and">20,</part-num-ref>
|
| 397 |
+
and the radio audio input jack <part-num-ref name="radio audio input jack">28,</part-num-ref>
|
| 398 |
+
it drives the control line <part-num-ref name="control line">3</part-num-ref>
|
| 399 |
+
high. In response to this <boundary-data type="line-number">20 </boundary-data>
|
| 400 |
+
control signal, the television <part-num-ref name="television">12</part-num-ref>
|
| 401 |
+
supplies the audio output from its own tuner to its audio processor for supply to its speakers. Any signal on control line <part-num-ref name="audio output from its own tuner to its audio processor for supply to its speakers. Any signal on control line">3</part-num-ref>
|
| 402 |
+
is not controlling, <boundary-data type="header">-15-</boundary-data>
|
| 403 |
+
<page-break num="16"/>
|
| 404 |
+
<boundary-data type="header">Attorney Docket</boundary-data>
|
| 405 |
+
<boundary-data type="header">7256</boundary-data>
|
| 406 |
+
and signals on control lines <part-num-ref name="is not controlling, and signals on control lines">0</part-num-ref>
|
| 407 |
+
and <part-num-ref name="and">1</part-num-ref>
|
| 408 |
+
control video, as discussed above. </p>
|
| 409 |
+
<p id="p-47" num="47">When the audio detector <part-num-ref name="audio detector">58</part-num-ref>
|
| 410 |
+
detects an audio signal on the 3.5 mm audio input jack <part-num-ref name="3.5 mm audio input jack">16,</part-num-ref>
|
| 411 |
+
the left and <boundary-data type="line-number">5 </boundary-data>
|
| 412 |
+
right audio input jacks <part-num-ref name="left and right audio input jacks">18</part-num-ref>
|
| 413 |
+
and <part-num-ref name="and">20,</part-num-ref>
|
| 414 |
+
or the radio input jack <part-num-ref name="radio input jack">28,</part-num-ref>
|
| 415 |
+
it drives the control line <part-num-ref name="control line">0</part-num-ref>
|
| 416 |
+
low. In response to this control signal, the television <part-num-ref name="television">12</part-num-ref>
|
| 417 |
+
supplies the audio on the audio lines <part-num-ref name="audio lines">48</part-num-ref>
|
| 418 |
+
to its audio processor for supply to its speakers. Again, any signal on control line <part-num-ref name="to its audio processor for supply to its speakers. Again, any signal on control line">3</part-num-ref>
|
| 419 |
+
is not <boundary-data type="line-number">10 </boundary-data>
|
| 420 |
+
controlling, and signals on control lines <part-num-ref name="is not controlling, and signals on control lines">0</part-num-ref>
|
| 421 |
+
and <part-num-ref name="and">1</part-num-ref>
|
| 422 |
+
control video, as discussed above. </p>
|
| 423 |
+
<p id="p-48" num="48">An exemplary television 80 is shown in Figure 5 and can be used for the television <part-num-ref name="television">12.</part-num-ref>
|
| 424 |
+
The exemplary television <part-num-ref name="exemplary television">80</part-num-ref>
|
| 425 |
+
includes a cabinet <part-num-ref name="cabinet">82</part-num-ref>
|
| 426 |
+
on which are mounted a <boundary-data type="line-number">15 </boundary-data>
|
| 427 |
+
video connector <part-num-ref name="video connector">84,</part-num-ref>
|
| 428 |
+
an RGB connector <part-num-ref name="RGB connector">86,</part-num-ref>
|
| 429 |
+
an audio connector <part-num-ref name="audio connector">88,</part-num-ref>
|
| 430 |
+
and a control connector <part-num-ref name="control connector">90.</part-num-ref>
|
| 431 |
+
The control connector <part-num-ref name="control connector">90</part-num-ref>
|
| 432 |
+
may comprise one or more jacks, pins, an RS232 connector, etc. The video connector <part-num-ref name="video connector">84</part-num-ref>
|
| 433 |
+
is connected to the composite video line <part-num-ref name="composite video line">46,</part-num-ref>
|
| 434 |
+
the RGB connector <part-num-ref name="RGB connector">86</part-num-ref>
|
| 435 |
+
is connected to the RGB <boundary-data type="line-number">20 </boundary-data>
|
| 436 |
+
lines <part-num-ref name="RGB lines">44,</part-num-ref>
|
| 437 |
+
the audio connector <part-num-ref name="audio connector">88</part-num-ref>
|
| 438 |
+
is connected to the audio lines <part-num-ref name="audio lines">48,</part-num-ref>
|
| 439 |
+
and the control connector <part-num-ref name="control connector">90</part-num-ref>
|
| 440 |
+
is connected to the control lines <part-num-ref name="control lines">50.</part-num-ref>
|
| 441 |
+
The video connector <part-num-ref name="video connector">84,</part-num-ref>
|
| 442 |
+
the RGB <boundary-data type="header">-16-</boundary-data>
|
| 443 |
+
<page-break num="17"/>
|
| 444 |
+
<boundary-data type="header">Attorney Docket</boundary-data>
|
| 445 |
+
<boundary-data type="header">7256</boundary-data>
|
| 446 |
+
connector <part-num-ref name="RGB connector">86,</part-num-ref>
|
| 447 |
+
and the audio connector <part-num-ref name="audio connector">88</part-num-ref>
|
| 448 |
+
may be corresponding jacks, terminals, pins, etc. </p>
|
| 449 |
+
<p id="p-49" num="49">The exemplary television 80 also includes a television controller <part-num-ref name="television controller">92,</part-num-ref>
|
| 450 |
+
a tuner <part-num-ref name="tuner">94,</part-num-ref>
|
| 451 |
+
a video processor <part-num-ref name="video processor">96,</part-num-ref>
|
| 452 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 453 |
+
an audio processor <part-num-ref name="audio processor">98,</part-num-ref>
|
| 454 |
+
a video display <part-num-ref name="video display">100,</part-num-ref>
|
| 455 |
+
and audio speakers <part-num-ref name="video display 100, and audio speakers">102.</part-num-ref>
|
| 456 |
+
The television controller <part-num-ref name="television controller">92,</part-num-ref>
|
| 457 |
+
for example, may comprise a microprocessor and controls the tuner <part-num-ref name="tuner">94</part-num-ref>
|
| 458 |
+
in accordance with a channel selected by a user. </p>
|
| 459 |
+
<p id="p-50" num="50">When the television controller <part-num-ref name="television controller">92</part-num-ref>
|
| 460 |
+
detects x<confidence value="666">111</confidence>
|
| 461 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 462 |
+
control signals on the control connector <part-num-ref name="control connector">90,</part-num-ref>
|
| 463 |
+
the television controller <part-num-ref name="television controller">92</part-num-ref>
|
| 464 |
+
controls the video processor <part-num-ref name="video processor">96</part-num-ref>
|
| 465 |
+
and the audio processor <part-num-ref name="audio processor">98</part-num-ref>
|
| 466 |
+
to process the video and audio from the tuner <part-num-ref name="tuner">94.</part-num-ref>
|
| 467 |
+
When the television controller <part-num-ref name="television controller">92</part-num-ref>
|
| 468 |
+
detects x<confidence value="666">010</confidence>
|
| 469 |
+
control signals on the control connector <part-num-ref name="control connector">90,</part-num-ref>
|
| 470 |
+
the television <boundary-data type="line-number">15 </boundary-data>
|
| 471 |
+
controller <part-num-ref name="television controller">92</part-num-ref>
|
| 472 |
+
controls the video processor <part-num-ref name="video processor">96</part-num-ref>
|
| 473 |
+
to process the video from the RGB connector <part-num-ref name="RGB connector">86</part-num-ref>
|
| 474 |
+
and controls the audio processor <part-num-ref name="audio processor">98</part-num-ref>
|
| 475 |
+
to process the audio from the audio connector <part-num-ref name="audio connector">88.</part-num-ref>
|
| 476 |
+
When the television controller <part-num-ref name="television controller">92</part-num-ref>
|
| 477 |
+
detects x<confidence value="556">001</confidence>
|
| 478 |
+
control signals on the control connector <part-num-ref name="control connector">90,</part-num-ref>
|
| 479 |
+
the television <boundary-data type="line-number">20 </boundary-data>
|
| 480 |
+
controller <part-num-ref name="television controller">92</part-num-ref>
|
| 481 |
+
controls the video processor <part-num-ref name="video processor">96</part-num-ref>
|
| 482 |
+
to process the video from the video connector <part-num-ref name="video connector">84</part-num-ref>
|
| 483 |
+
and controls the audio processor <part-num-ref name="audio processor">98</part-num-ref>
|
| 484 |
+
to process the audio from the audio connector <part-num-ref name="audio connector">88.</part-num-ref>
|
| 485 |
+
</p>
|
| 486 |
+
<boundary-data type="header">-17-</boundary-data>
|
| 487 |
+
<boundary-data type="header">Attorney Docket</boundary-data>
|
| 488 |
+
<boundary-data type="header">7256</boundary-data>
|
| 489 |
+
<p id="p-51" num="51">
|
| 490 |
+
<page-break num="18"/>
|
| 491 |
+
As can be seen from Figure 4, other combinations are possible. For example, if the television controller <part-num-ref name="television controller">92</part-num-ref>
|
| 492 |
+
detects x011 control signals on the control connector <part-num-ref name="control connector">90,</part-num-ref>
|
| 493 |
+
the television controller <part-num-ref name="television controller">92</part-num-ref>
|
| 494 |
+
controls the video processor <boundary-data type="line-number">5 </boundary-data>
|
| 495 |
+
<part-num-ref name="video processor">96</part-num-ref>
|
| 496 |
+
to process the video from the tuner <part-num-ref name="tuner">94</part-num-ref>
|
| 497 |
+
and controls the audio processor <part-num-ref name="audio processor">98</part-num-ref>
|
| 498 |
+
to process the audio from the audio connector <part-num-ref name="audio connector">88.</part-num-ref>
|
| 499 |
+
</p>
|
| 500 |
+
<p id="p-52" num="52">As further shown in Figure 5, the video processed by the video processor <part-num-ref name="video processor">96</part-num-ref>
|
| 501 |
+
is supplied to the video display <boundary-data type="line-number">10 </boundary-data>
|
| 502 |
+
<part-num-ref name="video display">100,</part-num-ref>
|
| 503 |
+
and the audio processed by the audio processor <part-num-ref name="audio processor">98</part-num-ref>
|
| 504 |
+
is supplied to the audio speakers <part-num-ref name="audio speakers">102.</part-num-ref>
|
| 505 |
+
</p>
|
| 506 |
+
<p id="p-53" num="53">Certain modifications of the present invention have been discussed above. Other modifications of the present invention will occur to those practicing in the art <boundary-data type="line-number">15 </boundary-data>
|
| 507 |
+
of the present invention. For example, the remote jack pack <part-num-ref name="remote jack pack">10</part-num-ref>
|
| 508 |
+
is shown with various audio and video input jacks. </p>
|
| 509 |
+
<p id="p-54" num="54">However, the remote jack pack <part-num-ref name="remote jack pack">10</part-num-ref>
|
| 510 |
+
may be provided with audio and video input jacks that allow connection to sources in addition to and/or other than an MP3 player, a DVD, a VCR, <boundary-data type="line-number">20 </boundary-data>
|
| 511 |
+
and a super VHS as described above. </p>
|
| 512 |
+
<p id="p-55" num="55">Moreover, as described above, the remote jack pack <part-num-ref name="remote jack pack">10</part-num-ref>
|
| 513 |
+
includes the left and right audio output jacks <part-num-ref name="left and right audio output jacks">60</part-num-ref>
|
| 514 |
+
and <part-num-ref name="and">62,</part-num-ref>
|
| 515 |
+
a composite video output jack <part-num-ref name="composite video output jack">72,</part-num-ref>
|
| 516 |
+
and an RGB output <boundary-data type="header">-18-</boundary-data>
|
| 517 |
+
<page-break num="19"/>
|
| 518 |
+
<boundary-data type="header">Attorney Docket</boundary-data>
|
| 519 |
+
<boundary-data type="header">7256</boundary-data>
|
| 520 |
+
jack <part-num-ref name="RGB output jack">74</part-num-ref>
|
| 521 |
+
to connect audio and video signals over the RGB lines <part-num-ref name="RGB lines">44,</part-num-ref>
|
| 522 |
+
the composite video line <part-num-ref name="composite video line">46,</part-num-ref>
|
| 523 |
+
and the audio lines <part-num-ref name="audio lines">48</part-num-ref>
|
| 524 |
+
to the television <part-num-ref name="television">12.</part-num-ref>
|
| 525 |
+
Instead, the RGB lines <part-num-ref name="RGB lines">44,</part-num-ref>
|
| 526 |
+
the composite video line <part-num-ref name="composite video line">46,</part-num-ref>
|
| 527 |
+
and the audio lines <part-num-ref name="audio lines">48</part-num-ref>
|
| 528 |
+
may be <boundary-data type="line-number">5 </boundary-data>
|
| 529 |
+
directly wired into the circuits within the remote jack pack <part-num-ref name="remote jack pack">10.</part-num-ref>
|
| 530 |
+
</p>
|
| 531 |
+
<p id="p-56" num="56">As can be seen from Figure 4, not all of the control lines <part-num-ref name="control lines">50</part-num-ref>
|
| 532 |
+
are used to carry a control signal. </p>
|
| 533 |
+
<p id="p-57" num="57">Therefore, the control line not used as indicated by Figure <boundary-data type="line-number">10 </boundary-data>
|
| 534 |
+
4 may be used by the remote jack pack <part-num-ref name="remote jack pack">10</part-num-ref>
|
| 535 |
+
for other purposes, may be deleted, or may be retained for expansion purposes. </p>
|
| 536 |
+
<p id="p-58" num="58">The exemplary television 80 as described above is provided with a control connector <part-num-ref name="control connector">90</part-num-ref>
|
| 537 |
+
that is coupled to the <boundary-data type="line-number">15 </boundary-data>
|
| 538 |
+
television controller <part-num-ref name="television controller">92</part-num-ref>
|
| 539 |
+
of the exemplary television <part-num-ref name="exemplary television">80.</part-num-ref>
|
| 540 |
+
</p>
|
| 541 |
+
<p id="p-59" num="59">The television controller 92, accordingly, detects the state of the control lines <part-num-ref name="control lines">50,</part-num-ref>
|
| 542 |
+
as also described above. As also described above, the control connector <part-num-ref name="control connector">90</part-num-ref>
|
| 543 |
+
may be an RS <part-num-ref name="RS">232</part-num-ref>
|
| 544 |
+
connection such as for those televisions that are <boundary-data type="line-number">20 </boundary-data>
|
| 545 |
+
equipped with RS <part-num-ref name="connection such as for those televisions that are equipped with RS">232</part-num-ref>
|
| 546 |
+
ports by the manufacturer. </p>
|
| 547 |
+
<p id="p-60" num="60">Accordingly, the description of the present invention is to be construed as illustrative only and is for the purpose of teaching those skilled in the art the <boundary-data type="header">-19-</boundary-data>
|
| 548 |
+
<page-break num="20"/>
|
| 549 |
+
<boundary-data type="header">Attorney Docket</boundary-data>
|
| 550 |
+
<boundary-data type="header">7256</boundary-data>
|
| 551 |
+
best mode of carrying out the invention. The details may be varied substantially without departing from the spirit of the invention, and the exclusive use of all modifications which are within the scope of the appended <part-num-ref name="appended">5</part-num-ref>
|
| 552 |
+
claims is reserved. </p>
|
| 553 |
+
<boundary-data type="header">-20-</boundary-data>
|
| 554 |
+
</description>
|
| 555 |
+
</us-patent-application>
|
| 556 |
+
|
applicant/10976834.xml
ADDED
|
@@ -0,0 +1,86 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>10976834</doc-number>
|
| 8 |
+
<date>2007-03-23</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">Application Number: 10/976,834 Page 3 of 29</boundary-data>
|
| 14 |
+
<boundary-data type="header">Art Unit: 2109</boundary-data>
|
| 15 |
+
<p id="p-1" num="1">Amendments to the Specification:</p>
|
| 16 |
+
<p id="p-2" num="2">Please replace paragraphs [0002]-[0003] with the following amended paragraphs:</p>
|
| 17 |
+
<p id="p-3" num="3">[0002<confidence value="5">]</confidence>
|
| 18 |
+
U.S. Patent Application Serial No. [[ <confidence value="5">]</confidence>
|
| 19 |
+
] 10/977,373, "TRACKING </p>
|
| 20 |
+
<heading id="h-1">DOMAIN NAME RELATED REPUTATION".</heading>
|
| 21 |
+
<p id="p-4" num="4">[0003<confidence value="5">]</confidence>
|
| 22 |
+
U.S. Patent Application Serial No. [[ <confidence value="5">]</confidence>
|
| 23 |
+
] 10/976,547, "PRESENTING </p>
|
| 24 |
+
<heading id="h-2">SEARCH ENGINE RESULTS BASED ON DOMAIN NAME RELATED REPUTATION".</heading>
|
| 25 |
+
<p id="p-5" num="5">Applicants adopt Examiner's suggestion to capitalize trademarks in the specification.</p>
|
| 26 |
+
<p id="p-6" num="6">Please replace paragraph [0019] with the following amended paragraph:</p>
|
| 27 |
+
<p id="p-7" num="7">[0019<confidence value="5">]</confidence>
|
| 28 |
+
The Se<confidence value="155565">adease</confidence>
|
| 29 |
+
SENDERBASE system (http://www.senderbase.org) keeps track of the amount of email messages originating from various domain names and IP addresses. <confidence value="1285882">IrenPet</confidence>
|
| 30 |
+
<confidence value="5652525622">Systems4c-</confidence>
|
| 31 |
+
IRONPORT SYSTEMS INC., a company that maintains <confidence value="56166244252415">SenderBase-efg</confidence>
|
| 32 |
+
SENDERBASE.ORG, explains how it works in this example: "If a sender has high global volumes of mail - say <part-num-ref name="sender has high global volumes of mail - say">200</part-num-ref>
|
| 33 |
+
Million messages per day - from a network of <part-num-ref name="network of">5</part-num-ref>
|
| 34 |
+
different domains and 1,700 IP addresses that have only been sending mail for <part-num-ref name="different domains and 1,700 IP addresses that have only been sending mail for">15</part-num-ref>
|
| 35 |
+
days yet have a high end user complaint rate and they don't accept incoming mail, they will have a very low reputation score [...]. If a sender is a Fortune <part-num-ref name="Fortune">500</part-num-ref>
|
| 36 |
+
company, they will likely have much more modest global email volumes - say 500,000 messages per day - will have a smaller number of IPs and domains with a long sending history, they will accept incoming email and have low (or zero) end user complaint rates." (http://www.ironport.com/pdf/iro<confidence value="88888">nport</confidence>
|
| 37 |
+
c60<confidence value="2">_</confidence>
|
| 38 |
+
rep basedpaper.pdf) Please replace paragraph [0021] with the following amended paragraph: </p>
|
| 39 |
+
<p id="p-8" num="8">[0021<confidence value="5">]</confidence>
|
| 40 |
+
<confidence value="8685885">SpaiCep</confidence>
|
| 41 |
+
SPAMCOP (http://www.spamcop.net) maintains a black list of IP addresses and allows users to report spa<confidence value="7">m</confidence>
|
| 42 |
+
to a centralized database. </p>
|
| 43 |
+
<boundary-data type="header">Application Number: 10/976,834 Page 4 of 29</boundary-data>
|
| 44 |
+
<boundary-data type="header">Art Unit: 2109</boundary-data>
|
| 45 |
+
<p id="p-9" num="9">
|
| 46 |
+
<page-break num="2"/>
|
| 47 |
+
Please replace paragraphs [0023]-[0024] with the following amended paragraphs: </p>
|
| 48 |
+
<p id="p-10" num="10">[0023<confidence value="5">]</confidence>
|
| 49 |
+
<confidence value="62446625">Cletmark</confidence>
|
| 50 |
+
CLOUDMARK, Inc. (http://cloudmark.com) provides spa<confidence value="7">m</confidence>
|
| 51 |
+
filtering and allows users to block or unblock messages manually. The users' votes on messages (blocking and unblocking) are reported to a centralized database, allowing for better spa<confidence value="7">m</confidence>
|
| 52 |
+
filtering by reducing the number of false positives. Each <confidence value="545588525">Cleudmark</confidence>
|
| 53 |
+
CLOUDMARK user is assigned with a reputation (trust rating). If a malicious user unblocks a spa<confidence value="7">m</confidence>
|
| 54 |
+
message, while a large number of other users block it, the malicious user's reputation will go down. If a user votes along the lines with the rest of the users, her/his reputation raises. </p>
|
| 55 |
+
<p id="p-11" num="11">[0024<confidence value="5">]</confidence>
|
| 56 |
+
<confidence value="66565884">Verisign</confidence>
|
| 57 |
+
VERISIGN, Inc. maintains the list of domain names that were issued a <confidence value="68685">VeriS</confidence>
|
| 58 |
+
ign VERISIGN SSL digital certificate, so called "Verified Domains List." The company plans to make the list accessible to third parties (http://www.verisign.com/printablePages/page_00505<confidence value="5">1</confidence>
|
| 59 |
+
.html). </p>
|
| 60 |
+
<p id="p-12" num="12">Please replace paragraph [0026] with the following amended paragraph:</p>
|
| 61 |
+
<p id="p-13" num="13">[0026<confidence value="5">]</confidence>
|
| 62 |
+
For the reputation-based systems to work properly, the sender's email address or at least its domain name part should be correct. Often malicious users forge (spoof) the sender's email address when they send out spa<confidence value="7">m</confidence>
|
| 63 |
+
, viruses, or phishing email messages. Among the solutions to this problem are <confidence value="6686868684">Mieresefts</confidence>
|
| 64 |
+
MICROSOFT'<confidence value="5">s</confidence>
|
| 65 |
+
Sender ID (http://www.microsof<confidence value="68">t.</confidence>
|
| 66 |
+
com/mscorp/twc/privacy/spamsenderid.mspx) and <confidence value="666854">Yahees</confidence>
|
| 67 |
+
YAHOO'<confidence value="5">s</confidence>
|
| 68 |
+
Domain Keys (http://antispam.yahoo.com<confidence value="5">/</confidence>
|
| 69 |
+
domainkeys). The Sender ID proposal envisions publishing the sender's email IP address in the DNS records of the sender's server. This allows the receiver of the email message to compare the originating IP address in the email with the IP address published in the DNS. If they don't match, the email address was forged. The Domain Keys proposal utilizes public-private key infrastructure. The sender publishes its public key in the DNS records and digitally signs outgoing email messages with its private key. The receiver can validate the sender's signature using the sender's public key published in the DNS records. </p>
|
| 70 |
+
<boundary-data type="header">Application Number: 10/976,834 Page 5 of 29</boundary-data>
|
| 71 |
+
<boundary-data type="header">Art Unit: 2109</boundary-data>
|
| 72 |
+
<p id="p-14" num="14">
|
| 73 |
+
<page-break num="3"/>
|
| 74 |
+
Please replace paragraph [0057] with the following amended paragraph: </p>
|
| 75 |
+
<p id="p-15" num="15">[0057<confidence value="5">]</confidence>
|
| 76 |
+
The Reputation Database <part-num-ref name="Reputation Database">115</part-num-ref>
|
| 77 |
+
may obtain various reputation data from other reputation services, such as <confidence value="56166244252426">SenderBase-erg</confidence>
|
| 78 |
+
SENDERBASE.ORG, Bonded Sender Program, <confidence value="5684585">SpaiCep</confidence>
|
| 79 |
+
SPAMCOP, "societies" of trusted users (e.g. http://trust.mindswap.org), black and white domain<confidence value="66">/I</confidence>
|
| 80 |
+
P/email lists, <confidence value="55552425">Ceudmark</confidence>
|
| 81 |
+
CLOUDMARK, <confidence value="5655884">VeiSign</confidence>
|
| 82 |
+
VERISIGN Verified Domains List, TRUSTe, etc. The variety of reputation data may aid in making better decisions by the Requester <part-num-ref name="Requester">130.</part-num-ref>
|
| 83 |
+
</p>
|
| 84 |
+
</description>
|
| 85 |
+
</us-patent-application>
|
| 86 |
+
|
applicant/11011244.xml
ADDED
|
@@ -0,0 +1,723 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11011244</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">AUS92004<confidence value="5">0</confidence>
|
| 14 |
+
811US1 Patent Application </boundary-data>
|
| 15 |
+
<heading id="h-1">OPERATING SYSTEM MIGRATION W<confidence value="8">I</confidence>
|
| 16 |
+
TH </heading>
|
| 17 |
+
<heading id="h-2">MINIMAL STORAGE AREA NETWORK RECONFIGURATION</heading>
|
| 18 |
+
<p id="p-1" num="1">Inventors: James P. Allen Daniel G. Eisenhauer Giles Roger Frazier Robert George Kovacs Satya Prakesh Sharma <boundary-data type="line-number">
|
| 19 |
+
<confidence value="8">5</confidence>
|
| 20 |
+
</boundary-data>
|
| 21 |
+
</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 |
+
Field of the Invention The field of the invention is data processing, or, more specifically, methods, systems, and products for migrating an operating system from a source computer to a destination computer. </p>
|
| 26 |
+
<p id="p-3" num="3">
|
| 27 |
+
<boundary-data type="line-number">
|
| 28 |
+
<confidence value="88">15</confidence>
|
| 29 |
+
</boundary-data>
|
| 30 |
+
Description Of Related Art There are a number of situations where operating system migration from a source <boundary-data type="line-number">20 </boundary-data>
|
| 31 |
+
computer to a destination computer is appropriate and commonly performed. If a system administrator is planning hardware maintenance on the source computer hardware, for example, the system administrator may migrate the operating system including its currently installed applications to another computer. Another situation where operating system migration is appropriate and often performed is when an<confidence value="2">.</confidence>
|
| 32 |
+
</p>
|
| 33 |
+
<p id="p-4" num="4">
|
| 34 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 35 |
+
operating system running one source computer has outgrown the physical resource limitations of that source computer's hardware and a system administrator may want <boundary-data type="header">
|
| 36 |
+
<confidence value="8">1</confidence>
|
| 37 |
+
</boundary-data>
|
| 38 |
+
<page-break num="2"/>
|
| 39 |
+
<boundary-data type="header">AUS92004<confidence value="5">0</confidence>
|
| 40 |
+
811US1 Patent Application </boundary-data>
|
| 41 |
+
to migrate to another computer whose hardware that can accommodate the resource requirements. </p>
|
| 42 |
+
<p id="p-5" num="5">Performing operating system migration poses a number of challenges when the operating system is operating as a component in a complex network, such as for <boundary-data type="line-number">5 </boundary-data>
|
| 43 |
+
example, a Storage Area Network (<confidence value="5">'</confidence>
|
| 44 |
+
SAN'). A SAN is a dedicated network that serves to interconnect storage-related resources available to one or more networked servers. A SAN is typically separate from local area networks (<confidence value="5">'</confidence>
|
| 45 |
+
LANs') and wide area networks (<confidence value="5">'</confidence>
|
| 46 |
+
WANs'). SANs are often characterized by high interconnection data rates between member storage peripherals. SANs are also often characterized by <boundary-data type="line-number">10 </boundary-data>
|
| 47 |
+
highly scalable architectures. SANs include both hardware and software for hardware management, monitoring, and configuration. </p>
|
| 48 |
+
<p id="p-6" num="6">One reason operating system migration poses a challenge when the operating system to be migrated is connected to a SAN, is that SANs are typically <confidence value="5">'</confidence>
|
| 49 |
+
zoned.' Zoning is a <boundary-data type="line-number">15 </boundary-data>
|
| 50 |
+
logical grouping of hosts and resources. A zoned operating system is only allowed access to storage devices within the operating system's zone. Zoning a SAN has a number of benefits including load balancing, dedication of storage capacity, data integrity, and security, as well as others that will occur to those of skill in the art. </p>
|
| 51 |
+
<p id="p-7" num="7">
|
| 52 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 53 |
+
One type of zoning that is commonly implemented with a SAN is logical unit masking (<confidence value="5">'</confidence>
|
| 54 |
+
LUN masking'). In LUN masking, each storage device is subdivided into logical units (<confidence value="5">'</confidence>
|
| 55 |
+
LUNs') and each storage device restricts operating systems access to a particular LUN. That is, an operating system is only allowed access to storage within its LUN. </p>
|
| 56 |
+
<p id="p-8" num="8">
|
| 57 |
+
<boundary-data type="line-number">
|
| 58 |
+
<confidence value="88">25</confidence>
|
| 59 |
+
</boundary-data>
|
| 60 |
+
Conventional operating system migration techniques require extensive reconfiguration of the SAN to the operating system to access the same storage in the same LUNs after migration. There is therefore an ongoing need for methods, systems, and products for migrating an operating system from a source computer to a <part-num-ref name="">30</part-num-ref>
|
| 61 |
+
destination computer that requires little or no reconfiguration of a storage area <boundary-data type="header">
|
| 62 |
+
<confidence value="8">2</confidence>
|
| 63 |
+
</boundary-data>
|
| 64 |
+
<page-break num="3"/>
|
| 65 |
+
<boundary-data type="header">AUS92004<confidence value="5">0</confidence>
|
| 66 |
+
811US1 Patent Application </boundary-data>
|
| 67 |
+
network. </p>
|
| 68 |
+
<heading id="h-4">SUMMARY OF THE INVENTION</heading>
|
| 69 |
+
<p id="p-9" num="9">
|
| 70 |
+
<boundary-data type="line-number">
|
| 71 |
+
<confidence value="8">5</confidence>
|
| 72 |
+
</boundary-data>
|
| 73 |
+
Methods, systems, and computer program products are provided for migrating an operating system from a source computer to a destination computer. Some embodiments include identifying a destination adapter of the destination computer that is coupled for data communications to a SAN that is also coupled for data <boundary-data type="line-number">10 </boundary-data>
|
| 74 |
+
communications to a source adapter of the source computer, logging off a virtual port name of the source adapter from a login manager, deregistering the virtual port name from the source adapter, registering the virtual port name with the destination adapter, and logging on the destination adapter to the login manager with the virtual port name. Typical embodiments also include transferring the operating system from the <boundary-data type="line-number">15 </boundary-data>
|
| 75 |
+
source computer to the destination computer. </p>
|
| 76 |
+
<p id="p-10" num="10">In typical embodiments, identifying a destination adapter of the destination computer that is coupled for data communications to a SAN that is also coupled for data communications to a source adapter of the source computer includes querying a <boundary-data type="line-number">
|
| 77 |
+
<confidence value="882">20.</confidence>
|
| 78 |
+
</boundary-data>
|
| 79 |
+
server for a world-wide port name of destination adapter. In typical embodiments, identifying a destination adapter of the destination computer that is coupled for data communications to a SAN that is also coupled for data communications to a source adapter of the source computer includes querying a server for the destination computer of the destination adapter. </p>
|
| 80 |
+
<p id="p-11" num="11">
|
| 81 |
+
<boundary-data type="line-number">
|
| 82 |
+
<confidence value="88">25</confidence>
|
| 83 |
+
</boundary-data>
|
| 84 |
+
In many embodiments, logging off a virtual port name of the source adapter from the login manager is carried out by disassociating an N_Port ID from the virtual port name. In many embodiments, logging on the destination adapter to the login manager with the virtual port name is carried out by associating an N_Port ID with the virtual <part-num-ref name="virtual">30</part-num-ref>
|
| 85 |
+
port name. </p>
|
| 86 |
+
<boundary-data type="header">
|
| 87 |
+
<confidence value="8">3</confidence>
|
| 88 |
+
</boundary-data>
|
| 89 |
+
<boundary-data type="header">AUS92004<confidence value="5">0</confidence>
|
| 90 |
+
811US1 Patent Application </boundary-data>
|
| 91 |
+
<p id="p-12" num="12">
|
| 92 |
+
<page-break num="4"/>
|
| 93 |
+
Methods, systems, and computer program products are also provided<confidence value="5">-</confidence>
|
| 94 |
+
for migrating an operating system from a source computer to a destination computer that include identifying a destination adapter of the destination computer that is coupled for data communications to a SAN that is also coupled for data communications to a source <boundary-data type="line-number">5 </boundary-data>
|
| 95 |
+
adapter of the source computer, removing the source adapter from a zone, adding the destination adapter to the zone, logging off the source adapter from a login manager, and logging on the destination adapter to the login manager. Typical embodiments also include transferring the operating system from the source computer to the destination computer. </p>
|
| 96 |
+
<p id="p-13" num="13">
|
| 97 |
+
<boundary-data type="line-number">
|
| 98 |
+
<confidence value="88">10</confidence>
|
| 99 |
+
</boundary-data>
|
| 100 |
+
In typical embodiments, removing the source adapter from a zone includes identifying a zone associated with the source adapter, identifying targets associated with the source adapter, disassociating the source adapter from the targets, and deleting the source adapter from the zone. In typical embodiments, adding the <boundary-data type="line-number">15 </boundary-data>
|
| 101 |
+
destination adapter to the zone includes identifying a zone associated with the source adapter, including the destination adapter in the zone, identifying targets associated with the source adapter, and associating the destination adapter with the targets. </p>
|
| 102 |
+
<p id="p-14" num="14">The foregoing and other objects, features and advantages of the invention will be <boundary-data type="line-number">20 </boundary-data>
|
| 103 |
+
apparent from the following more particular descripti<confidence value="8">o</confidence>
|
| 104 |
+
ns of exemplary embodiments of the invention as illustrated in the accompanying drawings wherein like reference numbers generally represent like parts of exemplary embodiments of the invention. </p>
|
| 105 |
+
<heading id="h-5">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 106 |
+
<p id="p-15" num="15">
|
| 107 |
+
<boundary-data type="line-number">
|
| 108 |
+
<confidence value="88">25</confidence>
|
| 109 |
+
</boundary-data>
|
| 110 |
+
Figure 1 depicts an exemplary data processing system capable of migrating an operating system from a source computer to a destination computer that requires little or no reconfiguration of a storage area network ('SAN'). </p>
|
| 111 |
+
<p id="p-16" num="16">
|
| 112 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 113 |
+
Figure 2 sets forth a block diagram of automated computing machinery useful in migrating an operating system from a source computer to a destination computer <boundary-data type="header">
|
| 114 |
+
<confidence value="8">4</confidence>
|
| 115 |
+
</boundary-data>
|
| 116 |
+
<page-break num="5"/>
|
| 117 |
+
<boundary-data type="header">AUS92004<confidence value="5">0</confidence>
|
| 118 |
+
811US1 Patent Application </boundary-data>
|
| 119 |
+
according to embodiments of the present invention. </p>
|
| 120 |
+
<p id="p-17" num="17">Figure 3 sets forth a flow chart illustrating an exemplary method for migrating an operating system from a source computer to a destination computer that requires no <boundary-data type="line-number">5 </boundary-data>
|
| 121 |
+
reconfiguration of the SAN and may be carried out by a migration module within the operating system to be migrated. </p>
|
| 122 |
+
<p id="p-18" num="18">Figure 4 sets forth an exemplary method for identifying a destination adapter of the destination computer that is coupled for data communications to a SAN that is also <boundary-data type="line-number">10 </boundary-data>
|
| 123 |
+
coupled for data communications to a source adapter of the source computer manager. </p>
|
| 124 |
+
<p id="p-19" num="19">Figure 5 sets forth another method for migrating an operating system from a source computer to a destination computer that does not require the use of virtual port names <boundary-data type="line-number">15 </boundary-data>
|
| 125 |
+
and employs only minimal reconfiguration of the SAN. </p>
|
| 126 |
+
<p id="p-20" num="20">Figure 6 sets forth a flow chart illustrating an exemplary method for removing the source adapter from a zone.</p>
|
| 127 |
+
<p id="p-21" num="21">
|
| 128 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 129 |
+
Figure 7 sets forth a flow chart illustrating an exemplary method of adding the destination adapter to a zone. </p>
|
| 130 |
+
<heading id="h-6">DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS</heading>
|
| 131 |
+
<p id="p-22" num="22">
|
| 132 |
+
<boundary-data type="line-number">
|
| 133 |
+
<confidence value="88">25</confidence>
|
| 134 |
+
</boundary-data>
|
| 135 |
+
Introduction The present invention is described to a large extent in this specification in terms of methods for migrating an operating system from a source computer to a destination <boundary-data type="line-number">30 </boundary-data>
|
| 136 |
+
computer. Persons skilled in the art, however, will recognize that any computer system that includes suitable programming means for operating in accordance with <boundary-data type="header">
|
| 137 |
+
<confidence value="8">5</confidence>
|
| 138 |
+
</boundary-data>
|
| 139 |
+
<page-break num="6"/>
|
| 140 |
+
<boundary-data type="header">AUS92004<confidence value="5">0</confidence>
|
| 141 |
+
811US1 Patent Application </boundary-data>
|
| 142 |
+
the disclosed methods also falls well within the scope of the present invention. </p>
|
| 143 |
+
<p id="p-23" num="23">Suitable programming means include any means for directing a computer system to execute the steps of the method of the invention, including for example, systems comprised of processing units and arithmetic-logic circuits coupled to computer <boundary-data type="line-number">5 </boundary-data>
|
| 144 |
+
memory, which systems have the capability of storing in computer memory, which computer memory includes electronic circuits configured to store data and program instructions, programmed steps of the method of the invention for execution by a processing unit. </p>
|
| 145 |
+
<p id="p-24" num="24">
|
| 146 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 147 |
+
The invention also may be embodied in a computer program product, such as a diskette or other recording medium, for use with any suitable data processing system. </p>
|
| 148 |
+
<p id="p-25" num="25">Embodiments of a computer program product may be implemented by use of any recording medium for machine-readable information, including magnetic media, optical media, or other suitable media. Persons skilled in the art will immediately <boundary-data type="line-number">15 </boundary-data>
|
| 149 |
+
recognize that any computer system having suitable programming means will be capable of executing the steps of the method of the invention as embodied in a program product. Persons skilled in the art will recognize immediately that, although most of the exemplary embodiments described in this specification are oriented to software installed and executing on compu<confidence value="8">t</confidence>
|
| 150 |
+
er hardware, nevertheless, alternative <boundary-data type="line-number">20 </boundary-data>
|
| 151 |
+
embodiments implemented as firmware or as hardware are well within the scope of the present invention. </p>
|
| 152 |
+
<p id="p-26" num="26">Operating System Migration With <boundary-data type="line-number">25 </boundary-data>
|
| 153 |
+
Minimal Storage Area Network Reconfiguration Methods, systems, and products for migrating an operating system from a source computer to a destination computer are now described with reference to the accompanying drawings, beginning with Figure 1. Figure 1 depicts an exemplary <boundary-data type="line-number">30 </boundary-data>
|
| 154 |
+
data processing system capable of migrating an operating system from a source computer to a destination computer that requires little or no reconfiguration of a <boundary-data type="header">
|
| 155 |
+
<confidence value="8">6</confidence>
|
| 156 |
+
</boundary-data>
|
| 157 |
+
<page-break num="7"/>
|
| 158 |
+
<boundary-data type="header">
|
| 159 |
+
<confidence value="2">-</confidence>
|
| 160 |
+
AUS92004<confidence value="5">0</confidence>
|
| 161 |
+
811US1 Patent Application </boundary-data>
|
| 162 |
+
storage area network (<confidence value="5">'</confidence>
|
| 163 |
+
SAN'). The system of Figure 1 includes a number of computers connected for data communications in networks. Each of the computers of the system of Figure 1 has installed upon it an operating system which may be migrated to another computer. </p>
|
| 164 |
+
<p id="p-27" num="27">
|
| 165 |
+
<boundary-data type="line-number">
|
| 166 |
+
<confidence value="8">5</confidence>
|
| 167 |
+
</boundary-data>
|
| 168 |
+
The data processing system of Figure 1 includes wide area network ("WAN") <part-num-ref name="includes wide area network ("WAN")">(101)</part-num-ref>
|
| 169 |
+
and storage area network ("SAN") (103). The network connection aspect of the architecture of Figure 1 is only for explanation, not for limitation. In fact, systems for migrating an operating system from a source computer to a destination computer <boundary-data type="line-number">10 </boundary-data>
|
| 170 |
+
according to embodiments of the present invention may also be connected as LANs, WANs, intranets, <confidence value="222222222">internets</confidence>
|
| 171 |
+
, the<confidence value="5">-</confidence>
|
| 172 |
+
Internet, webs, the World Wide Web itself, or other connections as will occur to those of skill in the art. Such networks are media that may be used to provide data communication connections between various devices, computers, and computer storage connected together within an overall data <boundary-data type="line-number">15 </boundary-data>
|
| 173 |
+
processing system. </p>
|
| 174 |
+
<p id="p-28" num="28">In the example of Figure 1, several exemplary devices including a PDA (109), a computer workstation (104), a mobile phone (110), and personal computer <part-num-ref name="mobile phone (110), and personal computer">(108)</part-num-ref>
|
| 175 |
+
are connected to a WAN (101). The network-enabled mobile phone <part-num-ref name="network-enabled mobile phone">(109)</part-num-ref>
|
| 176 |
+
connects to the <boundary-data type="line-number">20 </boundary-data>
|
| 177 |
+
WAN <part-num-ref name="WAN">(101)</part-num-ref>
|
| 178 |
+
through a wireless link (<confidence value="85">14</confidence>
|
| 179 |
+
6), and the PDA <part-num-ref name="PDA">(112)</part-num-ref>
|
| 180 |
+
connects to the WAN <part-num-ref name="WAN">(101)</part-num-ref>
|
| 181 |
+
through a wireless link (114).<confidence value="5">.</confidence>
|
| 182 |
+
In the example of Figure 1, the personal computer <part-num-ref name="personal computer">(108)</part-num-ref>
|
| 183 |
+
connects through a wireline connection <part-num-ref name="wireline connection">(120)</part-num-ref>
|
| 184 |
+
to the WAN (101), and the computer workstation <part-num-ref name="computer workstation">(104)</part-num-ref>
|
| 185 |
+
connects through a wireline connection <part-num-ref name="wireline connection">(122)</part-num-ref>
|
| 186 |
+
to the WAN (101). </p>
|
| 187 |
+
<p id="p-29" num="29">
|
| 188 |
+
<boundary-data type="line-number">
|
| 189 |
+
<confidence value="88">25</confidence>
|
| 190 |
+
</boundary-data>
|
| 191 |
+
In the example of Figure 1, each of the computers connected to the WAN <part-num-ref name="WAN">(101)</part-num-ref>
|
| 192 |
+
may access a storage area network (<confidence value="5">'</confidence>
|
| 193 |
+
SAN') <part-num-ref name="storage area network ('SAN')">(103)</part-num-ref>
|
| 194 |
+
that provides a number of storage devices. In the example of Figure 1 two redundant arrays of independent disks <confidence value="8688">('RA</confidence>
|
| 195 |
+
IDs') <part-num-ref name="two redundant arrays of independent disks ('RAIDs')">(126</part-num-ref>
|
| 196 |
+
and <part-num-ref name="and">138)</part-num-ref>
|
| 197 |
+
are connected to the SAN <part-num-ref name="SAN">(103)</part-num-ref>
|
| 198 |
+
through fiber optic <boundary-data type="line-number">30 </boundary-data>
|
| 199 |
+
connections <part-num-ref name="through fiber optic connections">(118</part-num-ref>
|
| 200 |
+
and 136). Redundant arrays of independent disks are disk drives that employ two or more drives in combination for improved fault tolerance and <boundary-data type="header">
|
| 201 |
+
<confidence value="8">7</confidence>
|
| 202 |
+
</boundary-data>
|
| 203 |
+
<page-break num="8"/>
|
| 204 |
+
<boundary-data type="header">
|
| 205 |
+
<confidence value="2">-</confidence>
|
| 206 |
+
AUS92004<confidence value="5">0</confidence>
|
| 207 |
+
811US1 Patent Application </boundary-data>
|
| 208 |
+
improved performance. In the example of Figure 1, a tape backup <part-num-ref name="tape backup">(128)</part-num-ref>
|
| 209 |
+
is also connected to the SAN <part-num-ref name="SAN">(103)</part-num-ref>
|
| 210 |
+
through a fiber optic connection (124). </p>
|
| 211 |
+
<p id="p-30" num="30">In the example of Figure 1, the SAN <part-num-ref name="SAN">(103)</part-num-ref>
|
| 212 |
+
is a Fibre Channel network. Fibre <boundary-data type="line-number">5 </boundary-data>
|
| 213 |
+
Channel is a protocol suite for transfer of data within a SAN. Fibre Channel is an architecture developed by a consortium of computer and mass storage device manufacturers currently being standardized by the American National Standards Institute (<confidence value="5">'</confidence>
|
| 214 |
+
ANSI'). Fibre Channel was designed for mass storage devices and other peripheral devices that require very high bandwidth. Using optical fiber to connect <boundary-data type="line-number">10 </boundary-data>
|
| 215 |
+
devices, Fibre Channel supports high data transfer rates. Interested readers may find additional information about Fibre Channel in the currently available Fibre Channel specification, which is ANSI document number ANS<confidence value="525685">I/INCI</confidence>
|
| 216 |
+
TS <part-num-ref name="currently available Fibre Channel specification, which is ANSI document number ANSI/INCITS">373</part-num-ref>
|
| 217 |
+
entitled Information Technology -Fibre Channel Framing and Signaling Interface (FC-FS). </p>
|
| 218 |
+
<p id="p-31" num="31">
|
| 219 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 220 |
+
While in this specification, methods, systems, and products for migrating an operating system from a source computer to a destination computer are described with reference to Fibre Channel, this is for explanation and not for limitation. In fact, migrating an operating system from a source computer to a destination computer may employ many different SAN technologies such as for example, InfiniBand<confidence value="4">®</confidence>
|
| 221 |
+
, iSCSI SAN, and <boundary-data type="line-number">20 </boundary-data>
|
| 222 |
+
others as will occur to those of skill in the art. </p>
|
| 223 |
+
<p id="p-32" num="32">In the example of Figure 1, a login manager <part-num-ref name="login manager">(134)</part-num-ref>
|
| 224 |
+
connects to the SAN <part-num-ref name="SAN">(103)</part-num-ref>
|
| 225 |
+
through a fiber optic link (144). The login manager <part-num-ref name="login manager">(134)</part-num-ref>
|
| 226 |
+
administers logging in adapters and logging off adapters with the SAN. The exemplary SAN of Figure 1 also includes a <boundary-data type="line-number">25 </boundary-data>
|
| 227 |
+
zone manager <part-num-ref name="zone manager">(626)</part-num-ref>
|
| 228 |
+
that implements zoning on the SAN by providing each operating system connected to the SAN access to that operating system's assigned storage devices. </p>
|
| 229 |
+
<p id="p-33" num="33">In some methods of migrating an operating system from a source computer to a <boundary-data type="line-number">30 </boundary-data>
|
| 230 |
+
destination computer, the operating system to be migrated includes a migration module that facilitates migration according to embodiments of the present invention. </p>
|
| 231 |
+
<boundary-data type="header">
|
| 232 |
+
<confidence value="8">8</confidence>
|
| 233 |
+
</boundary-data>
|
| 234 |
+
<boundary-data type="header">AUS92004<confidence value="5">0</confidence>
|
| 235 |
+
811US1 Patent Application </boundary-data>
|
| 236 |
+
<p id="p-34" num="34">
|
| 237 |
+
<page-break num="9"/>
|
| 238 |
+
In some such embodiments, the migration module in the operating system is capable generally of identifying a destination adapter of the destination computer that is coupled for data communications to a SAN that is also coupled for data communications to a source adapter of the source computer, logging off a virtual port <boundary-data type="line-number">5 </boundary-data>
|
| 239 |
+
name of the source adapter from a login manager, and deregistering the virtual port name from the source adapter. After being transferred from the source computer to the destination computer, the migration module of the operating system is capable generally of registering the virtual port name with the destination adapter and logging on the destination adapter to the login manager with the virtual port name. Such <boundary-data type="line-number">10 </boundary-data>
|
| 240 |
+
embodiments do not require the SAN to be reconfigured as a part of migration. </p>
|
| 241 |
+
<p id="p-35" num="35">Instead, such embodiments include registering the operating system with the destination adapter and logging the destination adapter onto the login manager <part-num-ref name="login manager">(134)</part-num-ref>
|
| 242 |
+
with the same virtual port name that was previously in use by the source adapter of the source computer. </p>
|
| 243 |
+
<p id="p-36" num="36">
|
| 244 |
+
<boundary-data type="line-number">
|
| 245 |
+
<confidence value="88">15</confidence>
|
| 246 |
+
</boundary-data>
|
| 247 |
+
To establish Fibre Channel connectivity, a port name of a Fibre channel adapter must be associated with an N-Port ID. Each end point on the connection is called an N_Port (Node Port), which contains both an N_Port ID and a Port Name. The N_Port ID of the destination port is the destination address of Fibre Channel frames sent to <boundary-data type="line-number">20 </boundary-data>
|
| 248 |
+
that port, and the N_Port ID of the source port is the source address. The Port Name is a world wide unique identifier (analogous to MAC addresses in Ethernet) that can<confidence value="5">.</confidence>
|
| 249 |
+
</p>
|
| 250 |
+
<p id="p-37" num="37">be queried by others in the SAN to determine the identity of that N_Port.</p>
|
| 251 |
+
<p id="p-38" num="38">Conventional Fibre Channel adapters are assigned a burned-in world-wide port name <boundary-data type="line-number">25 </boundary-data>
|
| 252 |
+
(<confidence value="5">'</confidence>
|
| 253 |
+
WWPN') that uniquely identifies the adapter and is used to establish Fibre Channel connectivity. These burned-in world-wide port names are static and cannot be assigned to other adapters. N_Port <confidence value="5">I</confidence>
|
| 254 |
+
D Virtualization (<confidence value="52222">'NPIV</confidence>
|
| 255 |
+
') however provides a Fibre Channel facility for assigning a virtual port name to an adapter. NPIV allows a single fibre channel adapter to be assigned more than one virtual port name. NP<confidence value="68">IV</confidence>
|
| 256 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 257 |
+
also advantageously allows a single virtual port name to be moved from one source Fibre Channel adapter to another destination Fibre Channel adapter thereby <boundary-data type="header">
|
| 258 |
+
<confidence value="8">9</confidence>
|
| 259 |
+
</boundary-data>
|
| 260 |
+
<page-break num="10"/>
|
| 261 |
+
<boundary-data type="header">AUS92004<confidence value="5">0</confidence>
|
| 262 |
+
811US1 Patent Application </boundary-data>
|
| 263 |
+
facilitating migrating an operating system from a source computer to a destination computer without reconfiguration of the SAN according to embodiments of the present invention. </p>
|
| 264 |
+
<p id="p-39" num="39">
|
| 265 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 266 |
+
As discussed above, migrating an operating system from a source computer to a destination computer without reconfiguration may in some embodiments be performed by a migration module of the operating system to be migrated. In alternative embodiments, migrating an operating system from a source computer to a destination computer is carried out with minor reconfiguration of the SAN. In the <boundary-data type="line-number">10 </boundary-data>
|
| 267 |
+
example of Figure 1, a Host Management Console (<confidence value="685">'HM</confidence>
|
| 268 |
+
C') <part-num-ref name="Host Management Console ('HMC')">(140)</part-num-ref>
|
| 269 |
+
is connected to the SAN through<confidence value="5">-</confidence>
|
| 270 |
+
either in-band or out-of-ba<confidence value="5">n</confidence>
|
| 271 |
+
d connection (142). The HMC <part-num-ref name="HMC">(140)</part-num-ref>
|
| 272 |
+
is capable of facilitating migration of operating system from a source computer to a destination computer with only minimal SAN reconfiguration by identifying a destination adapter of the destination computer that is coupled for data <boundary-data type="line-number">15 </boundary-data>
|
| 273 |
+
communications to a SAN that is also coupled for data communications to a source adapter of the source computer, removing the source adapter from a zone, adding the destination adapter to the zone, and instructing the operating system to log off the source adapter from the login manager. After the operating system is transferred from the source computer to the destination computer, the HMC is capable of <boundary-data type="line-number">20 </boundary-data>
|
| 274 |
+
instructing the operating system to log on the destination adapter to the login manager. </p>
|
| 275 |
+
<p id="p-40" num="40">The arrangement of devices making up the exemplary system illustrated in Figure 1 are for explanation, not for limitation. Data processing systems useful according to <boundary-data type="line-number">25 </boundary-data>
|
| 276 |
+
various embodiments of the present invention may include additional servers, routers, other storage devices, and peer-to-peer architectures, not shown in Figure 1, as will occur to those of skill in the art. Networks in such data processing systems may support many data communications protocols, including for example TCP/IP, HTTP, WAP, HDTP, Fibre Channel, InfiniBand, and others as will occur to those of skill in <boundary-data type="line-number">30 </boundary-data>
|
| 277 |
+
the art. Various embodiments of the present invention may be implemented on a variety of hardware platforms in addition to those illustrated in Figure 1. </p>
|
| 278 |
+
<boundary-data type="header">
|
| 279 |
+
<confidence value="88">10</confidence>
|
| 280 |
+
</boundary-data>
|
| 281 |
+
<boundary-data type="header">AUS92004<confidence value="5">0</confidence>
|
| 282 |
+
811US1 Patent Application </boundary-data>
|
| 283 |
+
<p id="p-41" num="41">
|
| 284 |
+
<page-break num="11"/>
|
| 285 |
+
As mentioned above, migrating an operating system from a source computer to a destination computer in accordance with the present invention is generally implemented with computers, that is, with automated computing machinery. For <boundary-data type="line-number">5 </boundary-data>
|
| 286 |
+
further explanation, Figure 2 sets forth a block diagram of automated computing machinery comprising a computer <part-num-ref name="computer">(152)</part-num-ref>
|
| 287 |
+
useful in migrating an operating system from a source computer to a destination computer according to embodiments of the present invention. The computer <part-num-ref name="computer">(152)</part-num-ref>
|
| 288 |
+
of Figure 2 includes at least one computer processor <part-num-ref name="includes at least one computer processor">(156)</part-num-ref>
|
| 289 |
+
or <confidence value="6866">'CPU</confidence>
|
| 290 |
+
' as well as random access memory <part-num-ref name="or 'CPU' as well as random access memory">(168)</part-num-ref>
|
| 291 |
+
("RAM"). </p>
|
| 292 |
+
<p id="p-42" num="42">
|
| 293 |
+
<boundary-data type="line-number">
|
| 294 |
+
<confidence value="88">10</confidence>
|
| 295 |
+
</boundary-data>
|
| 296 |
+
Stored in RAM (168) is an operating system (154). Operating systems useful in computers according to embodiments of the present invention include Unix, Linux, Windows NT<confidence value="448">TM,</confidence>
|
| 297 |
+
<confidence value="5">i</confidence>
|
| 298 |
+
5/OS<confidence value="55">Tm</confidence>
|
| 299 |
+
, and many others as will occur to those of skill in the art. </p>
|
| 300 |
+
<p id="p-43" num="43">The operating system (154) in the example of Figure 2 is shown in RAM (168), but <boundary-data type="line-number">15 </boundary-data>
|
| 301 |
+
many components of an operating system typically are stored in non-volatile memory <part-num-ref name="operating system typically are stored in non-volatile memory">(166)</part-num-ref>
|
| 302 |
+
also. As discussed above, in some embodiments of the present invention, migration of the operating system is performed largely by the operating system to be migrated. The exemp<confidence value="8">l</confidence>
|
| 303 |
+
ary operating system of Figure 2 therefore includes a migration module <part-num-ref name="migration module">(232)</part-num-ref>
|
| 304 |
+
capable of identifying a destination adapter of the destination computer <boundary-data type="line-number">20 </boundary-data>
|
| 305 |
+
that is coupled for data <confidence value="7">c</confidence>
|
| 306 |
+
ommunications to a SAN that is also coupled for data communications to a source adapter of the source computer, logging off a virtual port name of the source adapter from a login manager, and deregistering the virtual port name from the source adapter. After transferring the operating system from the source computer to the destination computer, the migration module is capable <boundary-data type="line-number">25 </boundary-data>
|
| 307 |
+
generally of registering the virtual port name with the destination adapter and logging on the destination adapter to the login manager with the virtual port name. </p>
|
| 308 |
+
<p id="p-44" num="44">The computer (152) of Figure 2 includes non-volatile computer memory <part-num-ref name="includes non-volatile computer memory">(166)</part-num-ref>
|
| 309 |
+
coupled through a system bus <part-num-ref name="system bus">(160)</part-num-ref>
|
| 310 |
+
to processor <part-num-ref name="to processor">(156)</part-num-ref>
|
| 311 |
+
and to other components of the <boundary-data type="line-number">30 </boundary-data>
|
| 312 |
+
computer. Non-volatile computer memory <part-num-ref name="computer. Non-volatile computer memory">(166)</part-num-ref>
|
| 313 |
+
may be implemented as a hard disk drive (170), optical disk drive (172), electrically erasable programmable read-only <boundary-data type="header">
|
| 314 |
+
<confidence value="88">11</confidence>
|
| 315 |
+
</boundary-data>
|
| 316 |
+
<page-break num="12"/>
|
| 317 |
+
<boundary-data type="header">AUS92004<confidence value="5">0</confidence>
|
| 318 |
+
811US1 Patent Application </boundary-data>
|
| 319 |
+
memory space (so-called <confidence value="55">'E</confidence>
|
| 320 |
+
EPROM' or <confidence value="5">'</confidence>
|
| 321 |
+
Flash' memory) (174), RAM drives (not shown), or as any other kind of computer memory as will occur to those of skill in the art. </p>
|
| 322 |
+
<p id="p-45" num="45">
|
| 323 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 324 |
+
The exemplary computer (152) of Figure 2 includes a communications adapter <part-num-ref name="communications adapter">(167)</part-num-ref>
|
| 325 |
+
for implementing connections for data communications (184), including connections through networks, to other computers (182), including servers, clients, data storage in the SAN, and others as will occur to those of skill in the art. Communications adapters implement the hardware level of connections for data communications <boundary-data type="line-number">10 </boundary-data>
|
| 326 |
+
through which local devices and remote devices or servers send data communications directly to one another and through networks. Examples of communications adapters useful for migrating an operating system from a source computer to a destination computer according to embodiments of the present invention include Fibre Channel adapters, modems for wired dial-up connections, Ethernet (IEEE 802.3) adapters for <boundary-data type="line-number">15 </boundary-data>
|
| 327 |
+
wired LAN connections, and 802.1 <confidence value="6">l</confidence>
|
| 328 |
+
b adapters for wireless LAN connections. </p>
|
| 329 |
+
<p id="p-46" num="46">The example computer of Figure 2 includes one or more input/output interface adapters (178). <confidence value="15">.I</confidence>
|
| 330 |
+
nput/output interface adapters in computers implement user-oriented input/output through, for example, software drivers and computer hardware for <boundary-data type="line-number">20 </boundary-data>
|
| 331 |
+
controlling output to display devices <part-num-ref name="includes one or more input/output interface adapters (178). .Input/output interface adapters in computers implement user-oriented input/output through, for example, software drivers and computer hardware for controlling output to display devices">(180)</part-num-ref>
|
| 332 |
+
such as computer display screens, as well as user input <confidence value="222222222">from:user</confidence>
|
| 333 |
+
input devices <part-num-ref name="such as computer display screens, as well as user input from:user input devices">(181)</part-num-ref>
|
| 334 |
+
such as keyboards and mice. </p>
|
| 335 |
+
<p id="p-47" num="47">As discussed above, migrating an operating system from a source computer to a destination computer according to embodiments of the present invention may be <boundary-data type="line-number">25 </boundary-data>
|
| 336 |
+
facilitated by a migration module in the operating system to be migrated or by a third party entity such as for example a host management console coupled for data communications with the source and destination computers. Migrating an operating system from a source computer to a destination computer may also be carried out in some embodiments with no reconfiguration of the SAN and in other embodiments <boundary-data type="line-number">30 </boundary-data>
|
| 337 |
+
with only minimal reconfiguration of the SAN. For further explanation, Figure 3 sets forth a flow chart illustrating an exemplary method for migrating an operating system <boundary-data type="header">
|
| 338 |
+
<confidence value="88">12</confidence>
|
| 339 |
+
</boundary-data>
|
| 340 |
+
<page-break num="13"/>
|
| 341 |
+
<boundary-data type="header">AUS92004<confidence value="5">0</confidence>
|
| 342 |
+
811US1 Patent Application </boundary-data>
|
| 343 |
+
from a source computer <part-num-ref name="source computer">(316)</part-num-ref>
|
| 344 |
+
to a destination computer <part-num-ref name="destination computer">(320)</part-num-ref>
|
| 345 |
+
that requires no reconfiguration of the SAN and may be carried out by a migration module within the operating system to be migrated. </p>
|
| 346 |
+
<p id="p-48" num="48">
|
| 347 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 348 |
+
The method of Figure 3 includes identifying <part-num-ref name="includes identifying">(302)</part-num-ref>
|
| 349 |
+
a destination adapter <part-num-ref name="destination adapter">(318)</part-num-ref>
|
| 350 |
+
of the destination computer <part-num-ref name="destination computer">(320)</part-num-ref>
|
| 351 |
+
that is coupled for data communications to a SAN that is also coupled for data communications to a source adapter <part-num-ref name="source adapter">(314)</part-num-ref>
|
| 352 |
+
of the source computer (316). Identifying <part-num-ref name="source computer (316). Identifying">(302)</part-num-ref>
|
| 353 |
+
a destination adapter <part-num-ref name="destination adapter">(318)</part-num-ref>
|
| 354 |
+
of the destination computer <part-num-ref name="destination computer">(320)</part-num-ref>
|
| 355 |
+
that is coupled for data communications to a SAN that is also coupled <boundary-data type="line-number">10 </boundary-data>
|
| 356 |
+
for data communications to a source adapter <part-num-ref name="source adapter">(314)</part-num-ref>
|
| 357 |
+
of the source computer <part-num-ref name="source computer">(316)</part-num-ref>
|
| 358 |
+
is carried out by use of in-band communications within the SAN or through out-of-band communications outside the SAN. For further explanation of an exemplary technique of identifying a destination adapter, Figure 4 sets forth an exemplary method for identifying a destination adapter of the destination computer that is coupled for data <boundary-data type="line-number">15 </boundary-data>
|
| 359 |
+
communications to a SAN that is also coupled for data communications to a source adapter of the source computer. The method of Figure 4 includes querying <part-num-ref name="includes querying">(402)</part-num-ref>
|
| 360 |
+
a server <part-num-ref name="server">(404)</part-num-ref>
|
| 361 |
+
within the SAN for a world-wide port name <part-num-ref name="world-wide port name">(408)</part-num-ref>
|
| 362 |
+
of destination adapter and receiving a query response <part-num-ref name="query response">(406)</part-num-ref>
|
| 363 |
+
including the world-wide port name <part-num-ref name="world-wide port name">
|
| 364 |
+
<confidence value="5">(</confidence>
|
| 365 |
+
408) </part-num-ref>
|
| 366 |
+
of the destination adapter. As discussed above a world-wide port name is a unique Fibre <boundary-data type="line-number">20 </boundary-data>
|
| 367 |
+
Channel<confidence value="18866">-iden</confidence>
|
| 368 |
+
tifier that is burned into the adapter and therefore is a static and <confidence value="8">u</confidence>
|
| 369 |
+
nique identification of the adapter. In the example of Figure 4, the server <part-num-ref name="server">(404)</part-num-ref>
|
| 370 |
+
maintains an adapter identification database <part-num-ref name="adapter identification database">(416)</part-num-ref>
|
| 371 |
+
that includes identifications of adapters that are coupled for data communications with the SAN. The server <part-num-ref name="server">(404)</part-num-ref>
|
| 372 |
+
of Figure 4 may be installed upon the login manager or located at another location coupled for <boundary-data type="line-number">25 </boundary-data>
|
| 373 |
+
data communications with the source computer. </p>
|
| 374 |
+
<p id="p-49" num="49">Having identified an adapter of a destination computer that is coupled for data communications with a SAN that is also coupled for data communication with the source adapter, the method of Figure 4 continues by identifying the destination <boundary-data type="line-number">30 </boundary-data>
|
| 375 |
+
computer having that adapter installed upon it. That is, the operating system must be migrated to the computer associated with the adapter coupled for data <boundary-data type="header">
|
| 376 |
+
<confidence value="88">13</confidence>
|
| 377 |
+
</boundary-data>
|
| 378 |
+
<page-break num="14"/>
|
| 379 |
+
<boundary-data type="header">AUS92004<confidence value="5">0</confidence>
|
| 380 |
+
811US1 Patent Application </boundary-data>
|
| 381 |
+
communications with the SAN. The method of Figure 4 therefore also includes querying <part-num-ref name="therefore also includes querying">(410)</part-num-ref>
|
| 382 |
+
a server <part-num-ref name="server">(404)</part-num-ref>
|
| 383 |
+
for an identification of the destination computer <part-num-ref name="destination computer">(413)</part-num-ref>
|
| 384 |
+
of the destination adapter <part-num-ref name="destination adapter">(408)</part-num-ref>
|
| 385 |
+
and receiving a query response <part-num-ref name="query response">(412)</part-num-ref>
|
| 386 |
+
that includes a destination computer <confidence value="5">I</confidence>
|
| 387 |
+
D <part-num-ref name="destination computer ID">(414)</part-num-ref>
|
| 388 |
+
identifying the destination computer. In the example <boundary-data type="line-number">5 </boundary-data>
|
| 389 |
+
of Figure 4, the server <part-num-ref name="server">(404)</part-num-ref>
|
| 390 |
+
includes a computer identification database <part-num-ref name="computer identification database">(414)</part-num-ref>
|
| 391 |
+
that includes computer <confidence value="5">I</confidence>
|
| 392 |
+
Ds indexed by adapter <confidence value="5">I</confidence>
|
| 393 |
+
Ds for identification of destination computers having an adapter with connectivity to the SAN. Such computers are candidates for operating system migration according to embodiments of the present invention. </p>
|
| 394 |
+
<p id="p-50" num="50">
|
| 395 |
+
<boundary-data type="line-number">
|
| 396 |
+
<confidence value="88">10</confidence>
|
| 397 |
+
</boundary-data>
|
| 398 |
+
Again with reference to Figure 3: After identifying a destination adapter of a destination computer, the method of Figure 3 continues by logging off <part-num-ref name="continues by logging off">(304)</part-num-ref>
|
| 399 |
+
a virtual port name of the source adapter <part-num-ref name="source adapter">(314)</part-num-ref>
|
| 400 |
+
from a login manager (134). As described above, a Fibre Channel N-Node comprises a port name and an N-Port ID. Logging <boundary-data type="line-number">15 </boundary-data>
|
| 401 |
+
off <part-num-ref name="N-Port ID. Logging off">(304)</part-num-ref>
|
| 402 |
+
a virtual port name of the source adapter <part-num-ref name="source adapter">(314)</part-num-ref>
|
| 403 |
+
from the login manager <part-num-ref name="login manager">(134)</part-num-ref>
|
| 404 |
+
according to the method of Figure 3 is carried out by disassociating an N_Port ID from the virtual port name. The Fibre Channel specification provides a standard fabric logout function LOGO that disassociates the N_Port ID from the virtual port name. </p>
|
| 405 |
+
<p id="p-51" num="51">
|
| 406 |
+
<boundary-data type="line-number">
|
| 407 |
+
<confidence value="88">20</confidence>
|
| 408 |
+
</boundary-data>
|
| 409 |
+
After disassociating the NPort ID with the virtual port name, typical embodiments also include logging off all input/output (<confidence value="5665">'I/O</confidence>
|
| 410 |
+
') devices providing access to storage devices on the SAN. Logging off of all input/output devices advantageously ensures that the <confidence value="555">1/0</confidence>
|
| 411 |
+
devices terminate any remaining commands initiated prior to migration. </p>
|
| 412 |
+
<p id="p-52" num="52">
|
| 413 |
+
<boundary-data type="line-number">
|
| 414 |
+
<confidence value="88">25</confidence>
|
| 415 |
+
</boundary-data>
|
| 416 |
+
The method of Figure 3 also includes deregistering <part-num-ref name="also includes deregistering">(306)</part-num-ref>
|
| 417 |
+
the virtual port name from the source adapter (314). In the method of Figure 3, deregistering <part-num-ref name="method of Figure 3, deregistering">(306)</part-num-ref>
|
| 418 |
+
the virtual port name from the source adapter is typically carried out by the operating system to be migrated. </p>
|
| 419 |
+
<p id="p-53" num="53">
|
| 420 |
+
<boundary-data type="line-number">
|
| 421 |
+
<confidence value="88">30</confidence>
|
| 422 |
+
</boundary-data>
|
| 423 |
+
The method of Figure 3 also includes transferring <part-num-ref name="also includes transferring">(308)</part-num-ref>
|
| 424 |
+
the operating system from the <boundary-data type="header">
|
| 425 |
+
<confidence value="88">14</confidence>
|
| 426 |
+
</boundary-data>
|
| 427 |
+
<page-break num="15"/>
|
| 428 |
+
<boundary-data type="header">AUS92004<confidence value="5">0</confidence>
|
| 429 |
+
811US1 Patent Application </boundary-data>
|
| 430 |
+
source computer <part-num-ref name="source computer">(316)</part-num-ref>
|
| 431 |
+
to the destination computer (320). Transferring <part-num-ref name="destination computer (320). Transferring">(308)</part-num-ref>
|
| 432 |
+
the operating system from the source computer <part-num-ref name="source computer">(316)</part-num-ref>
|
| 433 |
+
to the destination computer <part-num-ref name="destination computer">(320)</part-num-ref>
|
| 434 |
+
is often carried out by a system administrator and often includes copying the operating system from the source computer to the destination computer. In some embodiments, <boundary-data type="line-number">5 </boundary-data>
|
| 435 |
+
transferring <part-num-ref name="destination computer. In some embodiments, transferring">(308)</part-num-ref>
|
| 436 |
+
the operating system from the source computer <part-num-ref name="source computer">(316)</part-num-ref>
|
| 437 |
+
to the destination computer <part-num-ref name="destination computer">(320)</part-num-ref>
|
| 438 |
+
includes copying the operating system from the source computer to an intermediate storage media such as a disk and then copying the operating system from the intermediate storage media to the destination computer. </p>
|
| 439 |
+
<p id="p-54" num="54">
|
| 440 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 441 |
+
After the operating system is transferred from the source computer to the destination computer, the method of Figure 3 includes registering <part-num-ref name="includes registering">(310)</part-num-ref>
|
| 442 |
+
the virtual port name with the destination adapter (318). In many embodiments of the method of Figure 3, registering <part-num-ref name="method of Figure 3, registering">(310)</part-num-ref>
|
| 443 |
+
the virtual port name with the destination adapter <part-num-ref name="destination adapter">(318)</part-num-ref>
|
| 444 |
+
is carried out by the operating system to be migrated. </p>
|
| 445 |
+
<p id="p-55" num="55">
|
| 446 |
+
<boundary-data type="line-number">
|
| 447 |
+
<confidence value="88">15</confidence>
|
| 448 |
+
</boundary-data>
|
| 449 |
+
The method of Figure 3 also includes logging on <part-num-ref name="also includes logging on">(312)</part-num-ref>
|
| 450 |
+
the destination adapter <part-num-ref name="destination adapter">(318)</part-num-ref>
|
| 451 |
+
to the login manager <part-num-ref name="login manager">(134)</part-num-ref>
|
| 452 |
+
with the virtual port name. As described above, a Fibre Channel N-Node comprises a port name and an N-Port ID. Logging<confidence value="5">.</confidence>
|
| 453 |
+
on <part-num-ref name="N-Port ID. Logging. on">(312)</part-num-ref>
|
| 454 |
+
the destination adapter <part-num-ref name="destination adapter">(318)</part-num-ref>
|
| 455 |
+
to the login manager <part-num-ref name="login manager">(134)</part-num-ref>
|
| 456 |
+
with the virtual port name <boundary-data type="line-number">20 </boundary-data>
|
| 457 |
+
according to the method of Figure 3 may be carried out by associating an NPort <confidence value="88">ID</confidence>
|
| 458 |
+
<confidence value="8">w</confidence>
|
| 459 |
+
ith the virtual port name. The Fibre Channel specification provides a standard function FDISC issued by the Fibre Channel adapter to a login manager instructing the login manager to assign an N-Port ID to the adapter to establish an N-Node. In the method of Figure 3, the FDSIC function is parameterized with the virtual port <boundary-data type="line-number">25 </boundary-data>
|
| 460 |
+
name previously in use with the source adapter. Because zoning and LUN masking in the SAN are based on virtual port names, migration according to the method of Figure 3 advantageously provides access to the same storage devices available to the source computer before the migration without reconfiguration of the SAN. </p>
|
| 461 |
+
<p id="p-56" num="56">
|
| 462 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 463 |
+
After acquiring an N_Port ID, logging on <part-num-ref name="N_Port ID, logging on">(312)</part-num-ref>
|
| 464 |
+
the destination adapter <part-num-ref name="destination adapter">(318)</part-num-ref>
|
| 465 |
+
to the login manager <part-num-ref name="login manager">(134)</part-num-ref>
|
| 466 |
+
with the virtual port name also includes logging into the <confidence value="555">1/0</confidence>
|
| 467 |
+
<boundary-data type="header">
|
| 468 |
+
<confidence value="88">15</confidence>
|
| 469 |
+
</boundary-data>
|
| 470 |
+
<page-break num="16"/>
|
| 471 |
+
<boundary-data type="header">AUS92004081<confidence value="5885">1US1</confidence>
|
| 472 |
+
Patent Application </boundary-data>
|
| 473 |
+
devices that were previously logged off of prior to migration with the new N_Port ID. </p>
|
| 474 |
+
<p id="p-57" num="57">The Fibre Channel specification provides a port login (PLOG<confidence value="5">I</confidence>
|
| 475 |
+
) process to log into <confidence value="224">11O</confidence>
|
| 476 |
+
devices. </p>
|
| 477 |
+
<p id="p-58" num="58">
|
| 478 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 479 |
+
The method of Figure 3 advantageously provides method for operating system migration that does not require reconfiguration of the SAN because the method of Figure 3 utilizes virtual port names. For further explanation, Figure 5 sets forth another method for migrating an operating system from a source computer to a destination computer that does not require the use of virtual port names and employs <boundary-data type="line-number">10 </boundary-data>
|
| 480 |
+
only minimal reconfiguration of the SAN. The method of Figure 5 may be facilitated by a third<confidence value="2">-</confidence>
|
| 481 |
+
party entity such as for example a host management console (<confidence value="55">'H</confidence>
|
| 482 |
+
MC') coupled for data communications with the SAN. </p>
|
| 483 |
+
<p id="p-59" num="59">The method of Figure 5 includes identifying <part-num-ref name="includes identifying">(502)</part-num-ref>
|
| 484 |
+
a destination adapter <part-num-ref name="destination adapter">(318)</part-num-ref>
|
| 485 |
+
of the <boundary-data type="line-number">15 </boundary-data>
|
| 486 |
+
destination computer <part-num-ref name="destination computer">(320)</part-num-ref>
|
| 487 |
+
that is coupled for data communications to a SAN that is also coupled for data communications to a source adapter <part-num-ref name="source adapter">(314)</part-num-ref>
|
| 488 |
+
of the source computer (316). As described above with reference to Figure 4, identifying a destination adapter of the destination computer that is coupled for data communications to a SAN that is also coupled for data communications to a source <boundary-data type="line-number">
|
| 489 |
+
<confidence value="8">2</confidence>
|
| 490 |
+
0 </boundary-data>
|
| 491 |
+
adapter of the source computer may be carried out by querying a server within the SAN for a world-wide port name of a destination adapter and then querying a server for the destination computer of the destination adapter to identify a candidate destination computer for migration. </p>
|
| 492 |
+
<p id="p-60" num="60">
|
| 493 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 494 |
+
The method of Figure 5 also includes removing <part-num-ref name="also includes removing">(504)</part-num-ref>
|
| 495 |
+
the source adapter <part-num-ref name="source adapter">(314)</part-num-ref>
|
| 496 |
+
from a zone (512). As discussed above, a zone is logical grouping of hosts and resources. </p>
|
| 497 |
+
<p id="p-61" num="61">The exemplary zone (512) of Figure 5 includes a plurality of adapters in the zone <part-num-ref name="zone">(514)</part-num-ref>
|
| 498 |
+
identified by their burned-in world-wide port name. The exemplary zone <part-num-ref name="exemplary zone">(512)</part-num-ref>
|
| 499 |
+
of Figure 5 also associates targets <part-num-ref name="also associates targets">(518)</part-num-ref>
|
| 500 |
+
with the adapters (514). Targets are actual <boundary-data type="line-number">30 </boundary-data>
|
| 501 |
+
storage devices within the zone to which the operating system has access for data storage through their associated adapter. </p>
|
| 502 |
+
<boundary-data type="header">
|
| 503 |
+
<confidence value="88">16</confidence>
|
| 504 |
+
</boundary-data>
|
| 505 |
+
<boundary-data type="header">AUS92004<confidence value="5885885">0811US1</confidence>
|
| 506 |
+
Patent Application </boundary-data>
|
| 507 |
+
<p id="p-62" num="62">
|
| 508 |
+
<page-break num="17"/>
|
| 509 |
+
For further explanation, Figure 6 sets forth a flow chart illustrating an exemplary method for removing the source adapter from a zone. The method of Figure 6 includes identifying <part-num-ref name="includes identifying">(602)</part-num-ref>
|
| 510 |
+
a zone <part-num-ref name="zone">(512)</part-num-ref>
|
| 511 |
+
associated with the source adapter (608). In <boundary-data type="line-number">5 </boundary-data>
|
| 512 |
+
the method of Figure 6, identifying <part-num-ref name="method of Figure 6, identifying">(602)</part-num-ref>
|
| 513 |
+
a zone <part-num-ref name="zone">(512)</part-num-ref>
|
| 514 |
+
associated with the source adapter <part-num-ref name="source adapter">(608)</part-num-ref>
|
| 515 |
+
is carried out by querying a zone manager <part-num-ref name="zone manager">(626)</part-num-ref>
|
| 516 |
+
and receiving a zone query response <part-num-ref name="zone query response">(606)</part-num-ref>
|
| 517 |
+
containing an identification of the zone (512). The zone manager <part-num-ref name="zone manager">(626)</part-num-ref>
|
| 518 |
+
of Figure 6 maintains a zoning database <part-num-ref name="zoning database">(630)</part-num-ref>
|
| 519 |
+
including identifications of adapters indexed by their associated zones. In the example of Figure 6, the zone <boundary-data type="line-number">10 </boundary-data>
|
| 520 |
+
manager <part-num-ref name="zone manager">(626)</part-num-ref>
|
| 521 |
+
looks up the zone associated with the adapter and issues a zone query response <part-num-ref name="zone query response">(606)</part-num-ref>
|
| 522 |
+
containing the source adapter ID <part-num-ref name="source adapter ID">(608)</part-num-ref>
|
| 523 |
+
and a zone ID <part-num-ref name="zone ID">(5<confidence value="5">1</confidence>
|
| 524 |
+
2) </part-num-ref>
|
| 525 |
+
uniquely identifying the zone to which the source adapter is assigned. </p>
|
| 526 |
+
<p id="p-63" num="63">Removing the source adapter from a zone according to the method of Figure 6 also <boundary-data type="line-number">15 </boundary-data>
|
| 527 |
+
includes identifying <part-num-ref name="also includes identifying">(612)</part-num-ref>
|
| 528 |
+
targets <part-num-ref name="targets">(620)</part-num-ref>
|
| 529 |
+
associated with the source adapter (608). As mentioned above, targets are actual storage devices within the zone to which the operating system has access for data storage. In the example. of Figure 6, identifying <part-num-ref name="example. of Figure 6, identifying">(612)</part-num-ref>
|
| 530 |
+
targets <part-num-ref name="targets">(620)</part-num-ref>
|
| 531 |
+
associated with the source adapter <part-num-ref name="source adapter">(608)</part-num-ref>
|
| 532 |
+
is carried out by querying the zone manager <part-num-ref name="zone manager">(626)</part-num-ref>
|
| 533 |
+
and receiving a zone target query response <part-num-ref name="zone target query response">(618)</part-num-ref>
|
| 534 |
+
containing <boundary-data type="line-number">20 </boundary-data>
|
| 535 |
+
an identification of the targets (620). In the <confidence value="2222222222">example'of</confidence>
|
| 536 |
+
Figure 6, the zone manager <part-num-ref name="zone manager">(626)</part-num-ref>
|
| 537 |
+
maintains a targets database <part-num-ref name="targets database">(628)</part-num-ref>
|
| 538 |
+
that i<confidence value="5">n</confidence>
|
| 539 |
+
cludes<confidence value="15">-t</confidence>
|
| 540 |
+
he targets indexed by associated adapters. The zone manager <part-num-ref name="zone manager">(626)</part-num-ref>
|
| 541 |
+
issues a zone target query response <part-num-ref name="zone target query response">(618)</part-num-ref>
|
| 542 |
+
containing a source adapter identification <part-num-ref name="source adapter identification">(608)</part-num-ref>
|
| 543 |
+
and the targets <part-num-ref name="targets">(620)</part-num-ref>
|
| 544 |
+
associated with the source adapter. </p>
|
| 545 |
+
<p id="p-64" num="64">
|
| 546 |
+
<boundary-data type="line-number">
|
| 547 |
+
<confidence value="88">25</confidence>
|
| 548 |
+
</boundary-data>
|
| 549 |
+
Removing the source adapter from a zone according to the method of Figure 6 includes disassociating <part-num-ref name="includes disassociating">(622)</part-num-ref>
|
| 550 |
+
the source adapter <part-num-ref name="source adapter">(608)</part-num-ref>
|
| 551 |
+
from the targets <part-num-ref name="targets">(620)</part-num-ref>
|
| 552 |
+
and deleting <part-num-ref name="and deleting">(624)</part-num-ref>
|
| 553 |
+
the source adapter from the zone (512). Disassociating the source adapter from the targets before migration of the operating system advantageously <boundary-data type="line-number">30 </boundary-data>
|
| 554 |
+
frees the targets for association with the destination source adapter after migration of the operating system to the destination computer. </p>
|
| 555 |
+
<boundary-data type="header">
|
| 556 |
+
<confidence value="88">17</confidence>
|
| 557 |
+
</boundary-data>
|
| 558 |
+
<boundary-data type="header">AUS92004081<confidence value="5884">1US1</confidence>
|
| 559 |
+
Patent Application </boundary-data>
|
| 560 |
+
<p id="p-65" num="65">
|
| 561 |
+
<page-break num="18"/>
|
| 562 |
+
Again with reference to Figure 5: After removing (504) the source adapter <part-num-ref name="source adapter">(314)</part-num-ref>
|
| 563 |
+
from a zone (512), the method of Figure 5 continues by adding <part-num-ref name="continues by adding">(506)</part-num-ref>
|
| 564 |
+
the destination adapter <part-num-ref name="destination adapter">(318)</part-num-ref>
|
| 565 |
+
to the zone (512). For further explanation, Figure 7 sets forth a flow <boundary-data type="line-number">5 </boundary-data>
|
| 566 |
+
chart illustrating an exemplary method of adding the destination adapter to a zone. </p>
|
| 567 |
+
<p id="p-66" num="66">Adding the destination adapter to the zone according to the method of Figure 7 is carried out by identifying <part-num-ref name="is carried out by identifying">(602)</part-num-ref>
|
| 568 |
+
a zone <part-num-ref name="zone">(512)</part-num-ref>
|
| 569 |
+
associated with the source adapter. As described above with reference to Figure 6, identifying <part-num-ref name="source adapter. As described above with reference to Figure 6, identifying">(602)</part-num-ref>
|
| 570 |
+
a zone <part-num-ref name="zone">(512)</part-num-ref>
|
| 571 |
+
associated with the source adapter <part-num-ref name="source adapter">(608)</part-num-ref>
|
| 572 |
+
is carried out by querying <part-num-ref name="is carried out by querying">(604)</part-num-ref>
|
| 573 |
+
a zone manager <part-num-ref name="zone manager">(626)</part-num-ref>
|
| 574 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 575 |
+
and receiving a zone query response <part-num-ref name="zone query response">(606)</part-num-ref>
|
| 576 |
+
containing an identification of the zone (512). The zone manager <part-num-ref name="zone manager">(626)</part-num-ref>
|
| 577 |
+
of Figure 7 maintains a zoning database <part-num-ref name="zoning database">(630)</part-num-ref>
|
| 578 |
+
including identifications of adapters indexed by their associated zones. In the example of Figure 6, the zone manager <part-num-ref name="zone manager">(626)</part-num-ref>
|
| 579 |
+
looks up the zone associated with the adapter and issues a zone query response <part-num-ref name="zone query response">(606)</part-num-ref>
|
| 580 |
+
containing the source adapter <confidence value="88">ID</confidence>
|
| 581 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 582 |
+
<part-num-ref name="source adapter ID">(608)</part-num-ref>
|
| 583 |
+
and a zone ID <part-num-ref name="zone ID">(512)</part-num-ref>
|
| 584 |
+
uniquely identifying the zone to which the source adapter is assigned. </p>
|
| 585 |
+
<p id="p-67" num="67">Adding the destination adapter to the zone according to the method of Figure 7 also includes <part-num-ref name="also includes">(702)</part-num-ref>
|
| 586 |
+
the destination adapter <part-num-ref name="destination adapter">(706)</part-num-ref>
|
| 587 |
+
in the zone (512). Including <part-num-ref name="zone (512). Including">(702)</part-num-ref>
|
| 588 |
+
the <boundary-data type="line-number">20 </boundary-data>
|
| 589 |
+
destination adapter <part-num-ref name="destination adapter">(706)</part-num-ref>
|
| 590 |
+
in the zone (512)<confidence value="4">'</confidence>
|
| 591 |
+
ad<confidence value="8">v</confidence>
|
| 592 |
+
antageously adds the destination adapter as one of the contents or member<confidence value="5">.</confidence>
|
| 593 |
+
elements of the zone. </p>
|
| 594 |
+
<p id="p-68" num="68">Adding the destination adapter to the zone according to the method of Figure 7 is also includes identifying <part-num-ref name="is also includes identifying">(612)</part-num-ref>
|
| 595 |
+
targets <part-num-ref name="targets">(620)</part-num-ref>
|
| 596 |
+
associated with the source adapter (608). As <boundary-data type="line-number">25 </boundary-data>
|
| 597 |
+
mentioned above, targets are actual storage devices within the zone to which the operating system has access for data storage. In the example of Figure 7, identifying <part-num-ref name="example of Figure 7, identifying">(612)</part-num-ref>
|
| 598 |
+
targets <part-num-ref name="targets">(620)</part-num-ref>
|
| 599 |
+
associated with the source adapter <part-num-ref name="source adapter">(608)</part-num-ref>
|
| 600 |
+
is carried out by querying the zone manager <part-num-ref name="zone manager">(626)</part-num-ref>
|
| 601 |
+
and receiving a zone target query response <part-num-ref name="zone target query response">(618)</part-num-ref>
|
| 602 |
+
containing an identification of the targets (620). In the example of Figure 7, the zone manager <boundary-data type="line-number">30 </boundary-data>
|
| 603 |
+
maintains a targets database <part-num-ref name="targets database">(628)</part-num-ref>
|
| 604 |
+
that includes the targets indexed by associated adapters. The zone manager <part-num-ref name="zone manager">(626)</part-num-ref>
|
| 605 |
+
issues a zone target query response <part-num-ref name="zone target query response">(618)</part-num-ref>
|
| 606 |
+
<boundary-data type="header">
|
| 607 |
+
<confidence value="88">18</confidence>
|
| 608 |
+
</boundary-data>
|
| 609 |
+
<page-break num="19"/>
|
| 610 |
+
<boundary-data type="header">AUS92004081<confidence value="588">1US</confidence>
|
| 611 |
+
1 Patent Application </boundary-data>
|
| 612 |
+
containing an identification of the source adapter <part-num-ref name="source adapter">(608)</part-num-ref>
|
| 613 |
+
and an identification of the targets <part-num-ref name="targets">(620)</part-num-ref>
|
| 614 |
+
associated with the source adapter. </p>
|
| 615 |
+
<p id="p-69" num="69">Adding the destination adapter to the zone according to the method of Figure 7 also <boundary-data type="line-number">5 </boundary-data>
|
| 616 |
+
includes associating <part-num-ref name="also includes associating">(704)</part-num-ref>
|
| 617 |
+
the destination adapter <part-num-ref name="destination adapter">(706)</part-num-ref>
|
| 618 |
+
with the targets (620). </p>
|
| 619 |
+
<p id="p-70" num="70">Associating (704) the destination adapter <part-num-ref name="destination adapter">(706)</part-num-ref>
|
| 620 |
+
with the targets <part-num-ref name="targets">(620)</part-num-ref>
|
| 621 |
+
advantageously links the targets with the destination adapter thereby facilitating the migrated operating system's access to the targets after migration to the destination computer. </p>
|
| 622 |
+
<p id="p-71" num="71">
|
| 623 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 624 |
+
Again with reference to Figure 5, after adding the destination adapter to the zone, the method of Figure 5 continues by logging off <part-num-ref name="continues by logging off">(508)</part-num-ref>
|
| 625 |
+
the source adapter <part-num-ref name="source adapter">(314)</part-num-ref>
|
| 626 |
+
from the login manager (134). As discussed above, in many embodiments, the method of Figure 5 is facilitated by an H<confidence value="5">M</confidence>
|
| 627 |
+
C. In such embodiments, after adding the destination adapter to the zone the HMC instructs the operating system to log off the source <boundary-data type="line-number">15 </boundary-data>
|
| 628 |
+
adapter from the login manager. As described above, a Fibre Channel N-Node comprises a port name and an N-Port ID. Logging off <part-num-ref name="N-Port ID. Logging off">(508)</part-num-ref>
|
| 629 |
+
the source adapter <part-num-ref name="source adapter">(314)</part-num-ref>
|
| 630 |
+
from the login manager <part-num-ref name="login manager">(134)</part-num-ref>
|
| 631 |
+
is carried out by disassociating an N<confidence value="66">_P</confidence>
|
| 632 |
+
ort ID from a port name. In contrast with the method of Figure 3, the method of Figure 5 does not require the use of virtual port names and therefore the port name of the adapter in the <boundary-data type="line-number">20 </boundary-data>
|
| 633 |
+
example of Figure 5 may be either a virtual <confidence value="22222222">portmame</confidence>
|
| 634 |
+
or a burned-in world-wide port name. The Fibre Channel specification provides a standard fabric logout function LOGO that disassociates the N_Port ID from the port name. </p>
|
| 635 |
+
<p id="p-72" num="72">After disassociating the <confidence value="66">N_</confidence>
|
| 636 |
+
Port ID with the port name, typical embodiments also <boundary-data type="line-number">25 </boundary-data>
|
| 637 |
+
include logging off of all input/output (<confidence value="5554">'1/0</confidence>
|
| 638 |
+
') devices providing access to storage devices on the SAN. Logging off of all input/output devices advantageously ensures that the <confidence value="665">I/O</confidence>
|
| 639 |
+
devices terminate any remaining commands initiated prior to migration. </p>
|
| 640 |
+
<boundary-data type="header">
|
| 641 |
+
<confidence value="88">19</confidence>
|
| 642 |
+
</boundary-data>
|
| 643 |
+
<boundary-data type="header">AUS92004<confidence value="5">0</confidence>
|
| 644 |
+
811US1 Patent Application </boundary-data>
|
| 645 |
+
<p id="p-73" num="73">
|
| 646 |
+
<page-break num="20"/>
|
| 647 |
+
The method of Figure 5 also includes transferring <part-num-ref name="also includes transferring">(510)</part-num-ref>
|
| 648 |
+
the operating system from the source computer <part-num-ref name="source computer">(316)</part-num-ref>
|
| 649 |
+
to the destination computer (320). Transferring <part-num-ref name="destination computer (320). Transferring">(510)</part-num-ref>
|
| 650 |
+
the operating system from the source computer <part-num-ref name="source computer">(316)</part-num-ref>
|
| 651 |
+
to the destination computer <part-num-ref name="destination computer">(320)</part-num-ref>
|
| 652 |
+
is typically carried out by third party such as a system administrator and typically <boundary-data type="line-number">5 </boundary-data>
|
| 653 |
+
includes copying the operating system from the source computer to the destination computer. In some embodiments, transferring <part-num-ref name="destination computer. In some embodiments, transferring">(510)</part-num-ref>
|
| 654 |
+
the operating system from the source computer <part-num-ref name="source computer">(316)</part-num-ref>
|
| 655 |
+
to the destination computer <part-num-ref name="destination computer">(320)</part-num-ref>
|
| 656 |
+
includes copying the operating system from the source computer to an intermediate storage media such as a disk and then copying the operating system from the intermediate storage media to <boundary-data type="line-number">10 </boundary-data>
|
| 657 |
+
the destination computer. </p>
|
| 658 |
+
<p id="p-74" num="74">After transferring the operating system from the source computer to the destination computer, the method of Figure 5 includes logging on <part-num-ref name="includes logging on">(513)</part-num-ref>
|
| 659 |
+
the destination adapter <part-num-ref name="destination adapter">(318)</part-num-ref>
|
| 660 |
+
to the login manager (134). As discussed above, in many embodiments, the <boundary-data type="line-number">15 </boundary-data>
|
| 661 |
+
method of Figure 5 is facilitated by an <confidence value="5">H</confidence>
|
| 662 |
+
MC. In such embodiments, after transferring the operating system from the source computer to the destination computer the H<confidence value="68">MC</confidence>
|
| 663 |
+
instructs the operating system to log on the source destination adapter to the login manager. As described above, a Fibre Channel N-Node comprises a port name and an N-Port ID. Logging on the destination adapter to the login manager may be <boundary-data type="line-number">20 </boundary-data>
|
| 664 |
+
carried out by associating an N_Port I<confidence value="5">D</confidence>
|
| 665 |
+
with a port name. In contrast with the method of Figure 3, the method of Figure 5 does not require the use of virtual port names and therefore the port name of the adapter in the example of Figure 5 may be either a virtual port name or a burned-in world-wide port name. The Fibre Channel specification provides a standard function for logging in burned-in world-wide port <boundary-data type="line-number">25 </boundary-data>
|
| 666 |
+
names, FLOGI, issued by the Fibre Channel adapter to a login manager instructing the login manager to assign an N-Port ID to the adapter to establish an N-Node. </p>
|
| 667 |
+
<p id="p-75" num="75">After acquiring an N_Port ID, logging on the destination adapter to the login manager according to the method of Figure 5 also includes logging into the <confidence value="555">1/0</confidence>
|
| 668 |
+
devices that <boundary-data type="line-number">30 </boundary-data>
|
| 669 |
+
were previously logged off of prior to migration with the new N_Port ID. The Fibre Channel specification provides a port login (PLOGI) process to log into <confidence value="66">I/</confidence>
|
| 670 |
+
O devices. </p>
|
| 671 |
+
<boundary-data type="header">
|
| 672 |
+
<confidence value="88">20</confidence>
|
| 673 |
+
</boundary-data>
|
| 674 |
+
<boundary-data type="header">AUS92004081<confidence value="5885">1US1</confidence>
|
| 675 |
+
Patent Application </boundary-data>
|
| 676 |
+
<p id="p-76" num="76">
|
| 677 |
+
<page-break num="21"/>
|
| 678 |
+
Migrating an operating system from a source computer to a destination computer according to embodiments of the present invention provide a number of advantages. </p>
|
| 679 |
+
<p id="p-77" num="77">Such advantageous include:</p>
|
| 680 |
+
<p id="p-78" num="78">
|
| 681 |
+
<boundary-data type="line-number">
|
| 682 |
+
<confidence value="8">5</confidence>
|
| 683 |
+
</boundary-data>
|
| 684 |
+
<confidence value="2">"</confidence>
|
| 685 |
+
The destination adapter of the destination computer to which the operating system is migrated can be automatically identified using either in-band or out- of-band queries. </p>
|
| 686 |
+
<p id="p-79" num="79">
|
| 687 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 688 |
+
<confidence value="1">e</confidence>
|
| 689 |
+
No SAN reconfiguration is required to support OS migration in some embodiments and only minimal reconfiguration is required in others. </p>
|
| 690 |
+
<p id="p-80" num="80">
|
| 691 |
+
<confidence value="2">"</confidence>
|
| 692 |
+
Operating system migration can occur without major disruption to ongoing OS operation because no shutdown operations need to be done prior to <boundary-data type="line-number">15 </boundary-data>
|
| 693 |
+
migration. Uncompleted commands that may have been in process prior to migration will be abnormally terminated, but they will be automatically re- executed after migration through normal error recovery. </p>
|
| 694 |
+
<p id="p-81" num="81">
|
| 695 |
+
<confidence value="2">"</confidence>
|
| 696 |
+
Because no shutdown operations are required during migration, software <boundary-data type="line-number">20 </boundary-data>
|
| 697 |
+
drivers do not need to be <confidence value="8">r</confidence>
|
| 698 |
+
econfigured to support migration and applications may continue without interruption. </p>
|
| 699 |
+
<p id="p-82" num="82">
|
| 700 |
+
<confidence value="2">"</confidence>
|
| 701 |
+
The general techniques described in this specification are applicable to SAN technologies other than Fibre Channel. </p>
|
| 702 |
+
<p id="p-83" num="83">
|
| 703 |
+
<boundary-data type="line-number">
|
| 704 |
+
<confidence value="88">25</confidence>
|
| 705 |
+
</boundary-data>
|
| 706 |
+
<confidence value="2">"</confidence>
|
| 707 |
+
Operating system migration according to some embodiments of the present invention does not require virtual port names and therefore does not require the use of N Port ID Virtualization. Providing a method that does not require virtual port names is advantageous for use in legacy configurations in which <part-num-ref name="method that does not require virtual port names is advantageous for use in legacy configurations in which">30</part-num-ref>
|
| 708 |
+
doe not support NPIV. </p>
|
| 709 |
+
<boundary-data type="header">
|
| 710 |
+
<confidence value="88">21</confidence>
|
| 711 |
+
</boundary-data>
|
| 712 |
+
<boundary-data type="header">AUS92004<confidence value="5">0</confidence>
|
| 713 |
+
811US1 Patent Application </boundary-data>
|
| 714 |
+
<p id="p-84" num="84">
|
| 715 |
+
<page-break num="22"/>
|
| 716 |
+
It will be understood from the foregoing description that modifications and changes may be made in various embodiments of the present invention without departing from its true spirit. The descriptions in this specification are for purposes of illustration <boundary-data type="line-number">5 </boundary-data>
|
| 717 |
+
only and are not to be construed in a limiting sense. The scope of the present invention is limited only by the language of the following claims. </p>
|
| 718 |
+
<boundary-data type="header">
|
| 719 |
+
<confidence value="88">22</confidence>
|
| 720 |
+
</boundary-data>
|
| 721 |
+
</description>
|
| 722 |
+
</us-patent-application>
|
| 723 |
+
|
applicant/11055667.xml
ADDED
|
@@ -0,0 +1,43 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11055667</doc-number>
|
| 8 |
+
<date>2008-06-09</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="5">§</confidence>
|
| 14 |
+
1.111 Attorney Docket No.: Q86141 Application No.: 11/055,667 </p>
|
| 15 |
+
<heading id="h-1">AMENDMENTS TO THE SPECIFICATION</heading>
|
| 16 |
+
<p id="p-2" num="2">Please replace the present Abstract of the Disclosure with the following amended Abstract of the Disclosure:</p>
|
| 17 |
+
<p id="p-3" num="3">
|
| 18 |
+
<confidence value="666">One</confidence>
|
| 19 |
+
<confidence value="888">asp</confidence>
|
| 20 |
+
e<confidence value="8">c</confidence>
|
| 21 |
+
t <confidence value="66">of</confidence>
|
| 22 |
+
<confidence value="666">the</confidence>
|
| 23 |
+
<confidence value="5222">reet</confidence>
|
| 24 |
+
<confidence value="22222222">inention</confidence>
|
| 25 |
+
<confidence value="56">is</confidence>
|
| 26 |
+
<confidence value="52">in</confidence>
|
| 27 |
+
<confidence value="2">a</confidence>
|
| 28 |
+
A method of transporting compressed speech in packet mode in the core network of public land mobile network infrastructures over a core network segment is provided. The core network segment includ<confidence value="68664241852">es-inc4udin</confidence>
|
| 29 |
+
g a pair of transcoders equipped to operate in a tandem-free operation mode enabling transportation of compressed speech over said-t<confidence value="88">he</confidence>
|
| 30 |
+
segment<confidence value="5265666">.-said-</confidence>
|
| 31 |
+
The transcoders being adapted <confidence value="66">to</confidence>
|
| 32 |
+
<confidence value="222222222222">formatformat</confidence>
|
| 33 |
+
the compressed speech in a first format including compressed speech data and uncompressed speech data, in which method, for optimum transport in packet mode over the whole or a portion <confidence value="88">of</confidence>
|
| 34 |
+
<confidence value="6">s</confidence>
|
| 35 |
+
aid-t<confidence value="88">he</confidence>
|
| 36 |
+
segment, said-t<confidence value="88">he</confidence>
|
| 37 |
+
first format is changed to a second format including only compressed speech data. </p>
|
| 38 |
+
<p id="p-4" num="4">
|
| 39 |
+
<confidence value="8">2</confidence>
|
| 40 |
+
</p>
|
| 41 |
+
</description>
|
| 42 |
+
</us-patent-application>
|
| 43 |
+
|
applicant/11173098.xml
ADDED
|
@@ -0,0 +1,319 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11173098</doc-number>
|
| 8 |
+
<date>2005-07-01</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">MS <confidence value="5">#</confidence>
|
| 14 |
+
312091.<confidence value="52">01</confidence>
|
| 15 |
+
Atto<confidence value="66">rn</confidence>
|
| 16 |
+
ey Docket No. 03797.01311 </boundary-data>
|
| 17 |
+
<heading id="h-1">CONTEXTUAL TITLE EXTRACTION</heading>
|
| 18 |
+
<heading id="h-2">BACKGROUND</heading>
|
| 19 |
+
<p id="p-1" num="1">[01] Web pages on the World Wide Web are becoming more complex to accommodate rapidly growing information needs. For example, many web browsers contain a variety of information such as headline news, sports scores, market information, shopping information, and entertainment news. In addition, users during the course of typical web browsing may open multiple web browser screens to view multiple different web pages.</p>
|
| 20 |
+
<p id="p-2" num="2">
|
| 21 |
+
<confidence value="5885">[02]</confidence>
|
| 22 |
+
The use of a tab web browser enables a user to more efficiently display multiple web pages. A tab web browser allows a user to switch between multiple web pages in a single window. Additionally, a tab web browser may also allow for faster web page viewing as users may not have to wait for web pages to open as the tab browser may already have the web pages available for viewing as one of the displayed tabs. </p>
|
| 23 |
+
<p id="p-3" num="3">[03] For example, Figure 2 illustrates a tab web browser <part-num-ref name="tab web browser">200</part-num-ref>
|
| 24 |
+
which assists users in viewing several web pages at the same time. The tab web browser of Figure 2 illustrates various web pages such as "Webmail Direct" <part-num-ref name="illustrates various web pages such as "Webmail Direct"">202,</part-num-ref>
|
| 25 |
+
"CNN.com" <part-num-ref name="illustrates various web pages such as "Webmail Direct" 202, "CNN.com"">204,</part-num-ref>
|
| 26 |
+
and "DallasNews.com" <part-num-ref name="illustrates various web pages such as "Webmail Direct" 202, "CNN.com" 204, and "DallasNews.com"">206.</part-num-ref>
|
| 27 |
+
</p>
|
| 28 |
+
<p id="p-4" num="4">As a user opens additional web pages, the tabs displaying information related to each web page become smaller to allow additional accessed web pages to be displayed in the display area <part-num-ref name="display area">208.</part-num-ref>
|
| 29 |
+
</p>
|
| 30 |
+
<p id="p-5" num="5">
|
| 31 |
+
<confidence value="5">[</confidence>
|
| 32 |
+
04] Tab web browsers, however, may only display a limited amount of information on the tab <part-num-ref name="tab">210</part-num-ref>
|
| 33 |
+
for each web page. As a user opens multiple web pages using a tab browser, the tabs <part-num-ref name="tabs">210</part-num-ref>
|
| 34 |
+
for each web page become smaller and only a limited amount of information may be displayed on tab <part-num-ref name="limited amount of information may be displayed on tab">210.</part-num-ref>
|
| 35 |
+
The title for each tab <part-num-ref name="title for each tab">210</part-num-ref>
|
| 36 |
+
is important as the title information describes the represented web page to the user and allows a user to decide if they are interested in viewing the content of the web page. </p>
|
| 37 |
+
<p id="p-6" num="6">[05] Thus, it would be advancement in the art to provide a method in which the tabs of a tab web browser contain useful information concerning the content of the underling web <page-break num="2"/>
|
| 38 |
+
<boundary-data type="header">MS #312091.01 Attorney Docket No. 003797.01311</boundary-data>
|
| 39 |
+
page. Furthermore, the method should be transparent to a user and be useable on numerous types of documents with a minimal amount of effort. </p>
|
| 40 |
+
<heading id="h-3">SUMMARY</heading>
|
| 41 |
+
<p id="p-7" num="7">[06<confidence value="5">1</confidence>
|
| 42 |
+
The invention includes creation of contextual titles for web pages or other types of documents. The contextual titles provide meaningful titles for users based upon semantic content of the source document. The created contextual titles contain a limited amount of words to summarize contents of web pages or documents. The contextual titles may be utilized on tabs of a tab browser to provide concise and useful information to users. </p>
|
| 43 |
+
<heading id="h-4">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 44 |
+
<p id="p-8" num="8">
|
| 45 |
+
<confidence value="5885">[071</confidence>
|
| 46 |
+
A more complete understanding of the present invention and the advantages thereof may be acquired by referring to the following description in consideration of the accompanying drawings, in which like reference numbers indicate like features, and wherein: </p>
|
| 47 |
+
<p id="p-9" num="9">[08<confidence value="5">1</confidence>
|
| 48 |
+
Figure 1 illustrates an example of a suitable computing system environment on which the invention may be implemented. </p>
|
| 49 |
+
<p id="p-10" num="10">[09<confidence value="5">]</confidence>
|
| 50 |
+
Figure 2 illustrates a tab web browser displaying various web pages. </p>
|
| 51 |
+
<p id="p-11" num="11">
|
| 52 |
+
<confidence value="5885">[101</confidence>
|
| 53 |
+
Figure 3 illustrates a tab web browser displaying various web pages and a custom user's home page in accordance with an aspect of the invention. </p>
|
| 54 |
+
<p id="p-12" num="12">[11<confidence value="5">]</confidence>
|
| 55 |
+
Figure 4 illustrates a method of creating a contextual title in accordance with an aspect of the invention. </p>
|
| 56 |
+
<p id="p-13" num="13">[12<confidence value="5">1</confidence>
|
| 57 |
+
Figures 5 and <part-num-ref name="and">6</part-num-ref>
|
| 58 |
+
illustrate an exemplary contextual title creation from a web page or document in accordance with a first aspect of the invention. </p>
|
| 59 |
+
<p id="p-14" num="14">[13<confidence value="5">]</confidence>
|
| 60 |
+
Figure 7 illustrates another form of contextual title creation from a web page or document in accordance with another aspect of the invention. </p>
|
| 61 |
+
<boundary-data type="header">-2-</boundary-data>
|
| 62 |
+
<boundary-data type="header">MS <confidence value="5">#</confidence>
|
| 63 |
+
312091.01 Attorney Docket No. 003797.01311 </boundary-data>
|
| 64 |
+
<p id="p-15" num="15">
|
| 65 |
+
<page-break num="3"/>
|
| 66 |
+
<confidence value="4885">[14]</confidence>
|
| 67 |
+
Figure 8 illustrates a further form of contextual title creation in accordance with an aspect of the invention. </p>
|
| 68 |
+
<p id="p-16" num="16">[15] Figure 9 illustrates an additional form of contextual title creation in accordance with a further aspect of the invention.</p>
|
| 69 |
+
<heading id="h-5">DETAILED DESCRIPTION</heading>
|
| 70 |
+
<p id="p-17" num="17">
|
| 71 |
+
<confidence value="5885">[16]</confidence>
|
| 72 |
+
Figure 1 illustrates an example of a suitable computing system environment <part-num-ref name="suitable computing system environment">100</part-num-ref>
|
| 73 |
+
on which the invention may be implemented. Computing system environment <part-num-ref name="invention may be implemented. Computing system environment">100</part-num-ref>
|
| 74 |
+
is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Neither should the computing environment <part-num-ref name="computing environment">100</part-num-ref>
|
| 75 |
+
be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary operating environment <part-num-ref name="exemplary operating environment">100.</part-num-ref>
|
| 76 |
+
</p>
|
| 77 |
+
<p id="p-18" num="18">[17] With reference to Figure 1, an exemplary system for implementing the invention includes a general purpose computing device in the form of a computer <part-num-ref name="computer">110.</part-num-ref>
|
| 78 |
+
Components of computer <part-num-ref name="computer 110. Components of computer">110</part-num-ref>
|
| 79 |
+
may include, but are not limited to, a processing unit <part-num-ref name="processing unit">120,</part-num-ref>
|
| 80 |
+
a system memory <part-num-ref name="system memory">130,</part-num-ref>
|
| 81 |
+
and a system bus <part-num-ref name="system bus">121</part-num-ref>
|
| 82 |
+
that couples various system components including the system memory to the processing unit <part-num-ref name="processing unit">120.</part-num-ref>
|
| 83 |
+
The system bus <part-num-ref name="system bus">121</part-num-ref>
|
| 84 |
+
may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus also known as Mezzanine bus. </p>
|
| 85 |
+
<p id="p-19" num="19">
|
| 86 |
+
<confidence value="5">[</confidence>
|
| 87 |
+
18] Computer 110 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer <part-num-ref name="variety of computer readable media. Computer readable media can be any available media that can be accessed by computer">110</part-num-ref>
|
| 88 |
+
and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer <boundary-data type="header">-3-</boundary-data>
|
| 89 |
+
<page-break num="4"/>
|
| 90 |
+
<boundary-data type="header">
|
| 91 |
+
<confidence value="88">MS</confidence>
|
| 92 |
+
#312091.01 Attorney Docket No. 003797.01311 </boundary-data>
|
| 93 |
+
storage media and communication media. Computer storage media include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by computer <part-num-ref name="desired information and which can accessed by computer">110.</part-num-ref>
|
| 94 |
+
Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media. </p>
|
| 95 |
+
<p id="p-20" num="20">[19] The system memory <part-num-ref name="system memory">130</part-num-ref>
|
| 96 |
+
includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) <part-num-ref name="form of volatile and/or nonvolatile memory such as read only memory (ROM)">131</part-num-ref>
|
| 97 |
+
and random access memory (RAM) <part-num-ref name="and random access memory (RAM)">132.</part-num-ref>
|
| 98 |
+
A basic input/output system <part-num-ref name="basic input/output system">133</part-num-ref>
|
| 99 |
+
(BIOS), containing the basic routines that help to transfer information between elements within computer <part-num-ref name="basic routines that help to transfer information between elements within computer">110,</part-num-ref>
|
| 100 |
+
such as during start- up, is typically stored in ROM <part-num-ref name="basic routines that help to transfer information between elements within computer 110, such as during start- up, is typically stored in ROM">131.</part-num-ref>
|
| 101 |
+
RAM <part-num-ref name="basic routines that help to transfer information between elements within computer 110, such as during start- up, is typically stored in ROM 131. RAM">132</part-num-ref>
|
| 102 |
+
typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit <part-num-ref name="typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit">120.</part-num-ref>
|
| 103 |
+
By way of example, and not limitation, Figure 1 illustrates operating system <part-num-ref name="illustrates operating system">134,</part-num-ref>
|
| 104 |
+
application programs <part-num-ref name="illustrates operating system 134, application programs">135,</part-num-ref>
|
| 105 |
+
other program modules <part-num-ref name="illustrates operating system 134, application programs 135, other program modules">136,</part-num-ref>
|
| 106 |
+
and program data <part-num-ref name="illustrates operating system 134, application programs 135, other program modules 136, and program data">137.</part-num-ref>
|
| 107 |
+
</p>
|
| 108 |
+
<p id="p-21" num="21">[20] The computer <part-num-ref name="computer">110</part-num-ref>
|
| 109 |
+
may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only, Figure 1 illustrates a hard disk drive <part-num-ref name="hard disk drive">140</part-num-ref>
|
| 110 |
+
that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic <boundary-data type="header">-4-</boundary-data>
|
| 111 |
+
<page-break num="5"/>
|
| 112 |
+
<boundary-data type="header">
|
| 113 |
+
<confidence value="88">MS</confidence>
|
| 114 |
+
#312091.01 Attorney Docket No. 003797.01311 </boundary-data>
|
| 115 |
+
disk drive <part-num-ref name="magnetic disk drive">151</part-num-ref>
|
| 116 |
+
that reads from or writes to a removable, nonvolatile magnetic disk <part-num-ref name="removable, nonvolatile magnetic disk">152,</part-num-ref>
|
| 117 |
+
and an optical disk drive <part-num-ref name="optical disk drive">155</part-num-ref>
|
| 118 |
+
that reads from or writes to a removable, nonvolatile optical disk <part-num-ref name="removable, nonvolatile optical disk">156</part-num-ref>
|
| 119 |
+
such as a CD ROM or other optical media. Other removable/non-removable, volatile/nonvolatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like. </p>
|
| 120 |
+
<p id="p-22" num="22">The hard disk drive 141 is typically connected to the system bus <part-num-ref name="system bus">121</part-num-ref>
|
| 121 |
+
through a non- removable memory interface such as interface <part-num-ref name="non- removable memory interface such as interface">140,</part-num-ref>
|
| 122 |
+
and magnetic disk drive <part-num-ref name="non- removable memory interface such as interface 140, and magnetic disk drive">151</part-num-ref>
|
| 123 |
+
and optical disk drive <part-num-ref name="and optical disk drive">155</part-num-ref>
|
| 124 |
+
are typically connected to the system bus <part-num-ref name="system bus">121</part-num-ref>
|
| 125 |
+
by a removable memory interface, such as interface <part-num-ref name="removable memory interface, such as interface">150.</part-num-ref>
|
| 126 |
+
</p>
|
| 127 |
+
<p id="p-23" num="23">
|
| 128 |
+
<confidence value="5885">[21]</confidence>
|
| 129 |
+
The drives and their associated computer storage media discussed above and illustrated in Figure 1, provide storage of computer readable instructions, data structures, program modules and other data for the computer <part-num-ref name="computer">110.</part-num-ref>
|
| 130 |
+
In Figure 1, for example, hard disk drive <part-num-ref name="computer 110. In Figure 1, for example, hard disk drive">141</part-num-ref>
|
| 131 |
+
is illustrated as storing operating system <part-num-ref name="is illustrated as storing operating system">144,</part-num-ref>
|
| 132 |
+
application programs <part-num-ref name="is illustrated as storing operating system 144, application programs">145,</part-num-ref>
|
| 133 |
+
other program modules <part-num-ref name="is illustrated as storing operating system 144, application programs 145, other program modules">146,</part-num-ref>
|
| 134 |
+
and program data <part-num-ref name="is illustrated as storing operating system 144, application programs 145, other program modules 146, and program data">147.</part-num-ref>
|
| 135 |
+
Note that these components can either be the same as or different from operating system <part-num-ref name="same as or different from operating system">134,</part-num-ref>
|
| 136 |
+
application programs <part-num-ref name="same as or different from operating system 134, application programs">135,</part-num-ref>
|
| 137 |
+
other program modules <part-num-ref name="same as or different from operating system 134, application programs 135, other program modules">136,</part-num-ref>
|
| 138 |
+
and program data <part-num-ref name="same as or different from operating system 134, application programs 135, other program modules 136, and program data">137.</part-num-ref>
|
| 139 |
+
Operating system <part-num-ref name="same as or different from operating system 134, application programs 135, other program modules 136, and program data 137. Operating system">144,</part-num-ref>
|
| 140 |
+
application programs <part-num-ref name="same as or different from operating system 134, application programs 135, other program modules 136, and program data 137. Operating system 144, application programs">145,</part-num-ref>
|
| 141 |
+
other program modules <part-num-ref name="same as or different from operating system 134, application programs 135, other program modules 136, and program data 137. Operating system 144, application programs 145, other program modules">146,</part-num-ref>
|
| 142 |
+
and program data <part-num-ref name="same as or different from operating system 134, application programs 135, other program modules 136, and program data 137. Operating system 144, application programs 145, other program modules 146, and program data">147</part-num-ref>
|
| 143 |
+
are given different numbers here to illustrate that, at a minimum, they are different copies. A user may enter commands and information into the computer <part-num-ref name="computer">110</part-num-ref>
|
| 144 |
+
through input devices such as a keyboard <part-num-ref name="keyboard">162</part-num-ref>
|
| 145 |
+
and wireless pointing device <part-num-ref name="and wireless pointing device">161,</part-num-ref>
|
| 146 |
+
commonly referred to as a mouse, trackball or touch pad. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit <part-num-ref name="processing unit">120</part-num-ref>
|
| 147 |
+
through a user input interface <part-num-ref name="user input interface">160</part-num-ref>
|
| 148 |
+
that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A monitor <part-num-ref name="monitor">191</part-num-ref>
|
| 149 |
+
or other type of display device is also connected to the system bus <part-num-ref name="system bus">121</part-num-ref>
|
| 150 |
+
via an interface, such as a video interface <part-num-ref name="video interface">190.</part-num-ref>
|
| 151 |
+
In addition to the monitor, computers may also include other peripheral output devices such as speakers <part-num-ref name="monitor, computers may also include other peripheral output devices such as speakers">197</part-num-ref>
|
| 152 |
+
and printer <part-num-ref name="and printer">196,</part-num-ref>
|
| 153 |
+
which may be connected through an output peripheral interface <part-num-ref name="output peripheral interface">190.</part-num-ref>
|
| 154 |
+
</p>
|
| 155 |
+
<boundary-data type="header">-5-</boundary-data>
|
| 156 |
+
<boundary-data type="header">
|
| 157 |
+
<confidence value="88">MS</confidence>
|
| 158 |
+
<confidence value="6">#</confidence>
|
| 159 |
+
312091.01 Attorney Docket No. 003797.01311 </boundary-data>
|
| 160 |
+
<p id="p-24" num="24">
|
| 161 |
+
<page-break num="6"/>
|
| 162 |
+
<confidence value="5885">[22]</confidence>
|
| 163 |
+
The computer <part-num-ref name="computer">110</part-num-ref>
|
| 164 |
+
may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer <part-num-ref name="remote computer">180.</part-num-ref>
|
| 165 |
+
The remote computer <part-num-ref name="remote computer">180</part-num-ref>
|
| 166 |
+
may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer <part-num-ref name="computer">110,</part-num-ref>
|
| 167 |
+
although only a memory storage device <part-num-ref name="memory storage device">181</part-num-ref>
|
| 168 |
+
has been illustrated in Figure 1. The logical connections depicted in Figure 1 include a local area network (LAN) <part-num-ref name="local area network (LAN)">171</part-num-ref>
|
| 169 |
+
and a wide area network (WAN) <part-num-ref name="wide area network (WAN)">173,</part-num-ref>
|
| 170 |
+
but may also include other networks. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet. </p>
|
| 171 |
+
<p id="p-25" num="25">[23<confidence value="5">]</confidence>
|
| 172 |
+
When used in a LAN networking environment, the computer <part-num-ref name="computer">110</part-num-ref>
|
| 173 |
+
is connected to the LAN <part-num-ref name="LAN">171</part-num-ref>
|
| 174 |
+
through a network interface or adapter <part-num-ref name="network interface or adapter">170.</part-num-ref>
|
| 175 |
+
When used in a WAN networking environment, the computer <part-num-ref name="computer">110</part-num-ref>
|
| 176 |
+
typically includes a modem <part-num-ref name="modem">172</part-num-ref>
|
| 177 |
+
or other means for establishing communications over the WAN <part-num-ref name="WAN">173,</part-num-ref>
|
| 178 |
+
such as the Internet. The modem <part-num-ref name="modem">172,</part-num-ref>
|
| 179 |
+
which may be internal or external, may be connected to the system bus <part-num-ref name="system bus">121</part-num-ref>
|
| 180 |
+
via the user input interface <part-num-ref name="user input interface">160,</part-num-ref>
|
| 181 |
+
or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer <part-num-ref name="computer">110,</part-num-ref>
|
| 182 |
+
or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation, Figure 1 illustrates remote application programs <part-num-ref name="illustrates remote application programs">185</part-num-ref>
|
| 183 |
+
as residing on memory device <part-num-ref name="as residing on memory device">181.</part-num-ref>
|
| 184 |
+
</p>
|
| 185 |
+
<p id="p-26" num="26">It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used. A peripheral interface <part-num-ref name="peripheral interface">195</part-num-ref>
|
| 186 |
+
may interface to a video input device such as a scanner (not shown) or a digital camera <part-num-ref name="digital camera">194,</part-num-ref>
|
| 187 |
+
where output peripheral interface may support a standardized interface, including a universal serial bus (USB) interface. </p>
|
| 188 |
+
<p id="p-27" num="27">[24] The invention is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use with the invention include, but are not limited to, personal computers, server computers, hand- held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe <boundary-data type="header">-6-</boundary-data>
|
| 189 |
+
<page-break num="7"/>
|
| 190 |
+
<boundary-data type="header">MS <confidence value="5">#</confidence>
|
| 191 |
+
312091.01 Attorney Docket No. 003797.01311 </boundary-data>
|
| 192 |
+
computers, distributed computing environments that include any of the above systems or devices, and the like. </p>
|
| 193 |
+
<p id="p-28" num="28">
|
| 194 |
+
<confidence value="5885">[251</confidence>
|
| 195 |
+
The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. </p>
|
| 196 |
+
<p id="p-29" num="29">that performs particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.</p>
|
| 197 |
+
<p id="p-30" num="30">
|
| 198 |
+
<confidence value="5885">[261</confidence>
|
| 199 |
+
Figure 3 illustrates a tab browser displaying various web pages and a user's custom web page in accordance with an aspect of the invention. In Figure 3, a tab web browser <part-num-ref name="tab web browser">300</part-num-ref>
|
| 200 |
+
is utilized to display the various web pages and content. The tab browser <part-num-ref name="tab browser">300</part-num-ref>
|
| 201 |
+
may display various web pages such as "Yahoo.com" <part-num-ref name="may display various web pages such as "Yahoo.com"">304,</part-num-ref>
|
| 202 |
+
"ESPNstar.com" <part-num-ref name="may display various web pages such as "Yahoo.com" 304, "ESPNstar.com"">306,</part-num-ref>
|
| 203 |
+
"phoenixtv.com" <part-num-ref name="may display various web pages such as "Yahoo.com" 304, "ESPNstar.com" 306, "phoenixtv.com"">308,</part-num-ref>
|
| 204 |
+
"cnn.com" <part-num-ref name="may display various web pages such as "Yahoo.com" 304, "ESPNstar.com" 306, "phoenixtv.com" 308, "cnn.com"">310,</part-num-ref>
|
| 205 |
+
"The New York Times.com" <part-num-ref name="may display various web pages such as "Yahoo.com" 304, "ESPNstar.com" 306, "phoenixtv.com" 308, "cnn.com" 310, "The New York Times.com"">312,</part-num-ref>
|
| 206 |
+
and "sina.com" <part-num-ref name="may display various web pages such as "Yahoo.com" 304, "ESPNstar.com" 306, "phoenixtv.com" 308, "cnn.com" 310, "The New York Times.com" 312, and "sina.com"">314.</part-num-ref>
|
| 207 |
+
Those skilled in the art will realize that numerous other web pages may be displayed on tab browser <part-num-ref name="art will realize that numerous other web pages may be displayed on tab browser">300</part-num-ref>
|
| 208 |
+
and those shown in Figure 3 are meant to be exemplary. The web pages may be composed using hypertext mark-up language and/or an extensible markup language such as XML. Those skilled in the art will realize that other additional computer languages may be utilized in the creation of web pages. </p>
|
| 209 |
+
<p id="p-31" num="31">
|
| 210 |
+
<confidence value="5885">[271</confidence>
|
| 211 |
+
As the number of opened web pages increases, the tabs representing each web page become smaller in order to view as many tabs as possible within the display area. Each instance of an additional web page being added to the tab browser may make it more difficult for a user to remember what content is being displayed on the various web pages. For example, tab <part-num-ref name="various web pages. For example, tab">316</part-num-ref>
|
| 212 |
+
may display a web page representing a user's home page such as web page <part-num-ref name="user's home page such as web page">318.</part-num-ref>
|
| 213 |
+
The tab representing the user's home page may be named "Microsoft IE" <part-num-ref name="user's home page may be named "Microsoft IE"">320.</part-num-ref>
|
| 214 |
+
The title of the "Microsoft IE" <part-num-ref name=""Microsoft IE"">320</part-num-ref>
|
| 215 |
+
web page contains two words; </p>
|
| 216 |
+
<p id="p-32" num="32">however, titles of numerous other web pages contain numerous words which are not suitable for display on a tab of a tab browser due to limited display space. In addition, <boundary-data type="header">-7-</boundary-data>
|
| 217 |
+
<page-break num="8"/>
|
| 218 |
+
<boundary-data type="header">
|
| 219 |
+
<confidence value="88">MS</confidence>
|
| 220 |
+
<confidence value="6">#</confidence>
|
| 221 |
+
312091.0<confidence value="2">1</confidence>
|
| 222 |
+
Attorney Docket No. 003797.01311 </boundary-data>
|
| 223 |
+
many titles used for tabs on a tab browser do not utilize titles having contextual content representing the web page. The use of a title having contextual content may assist a user in quickly determining the content of the web page without having to view or read the contents of the web page. </p>
|
| 224 |
+
<p id="p-33" num="33">
|
| 225 |
+
<confidence value="5885">[28]</confidence>
|
| 226 |
+
Figure 4 shows an illustrative method for creating a contextual title for a web page or document. Referring to Figure 4, a user identifies information such as a web page to be displayed by the user. The web page may be accessed by a tab web browser through the URL of the web page. For example, a user interested in headline news may be interested in viewing headline news as reported by CNN. The user may decide to access CNN's website through the user's tab web browser. In step <part-num-ref name="user's tab web browser. In step">402,</part-num-ref>
|
| 227 |
+
preprocessing of the selected web page may be completed prior to key phrase extraction. For example, preprocessing may include filtering of stop words or the conversion of capital letters to lowercase letters. The preprocessing may include removing the HTML tags in order to obtain pure text content. In addition, preprocessing may include tokenizing the pure text into separate words and removing stop words such as "a," "the," "to." Finally, prepossessing may also include stemming to normalize words with same meaning (e.g. trimming the -s, -ing, -ed). </p>
|
| 228 |
+
<p id="p-34" num="34">
|
| 229 |
+
<confidence value="5885">[29]</confidence>
|
| 230 |
+
Next, in step 404 key phrase extraction from the web page or document may be initiated. </p>
|
| 231 |
+
<p id="p-35" num="35">The key phrase extraction may be executed on page content, URL, <confidence value="222222">and/or</confidence>
|
| 232 |
+
title of the web page or document. Key phrase extraction may be based on frequency of a cited word or phrase being utilized in the web page or document. </p>
|
| 233 |
+
<p id="p-36" num="36">
|
| 234 |
+
<confidence value="5885">[30]</confidence>
|
| 235 |
+
Furthermore, in step 406 the extracted key phrases may be utilized to create a contextual title. The contextual title may be displayed on the tabs of the tab web browser for the represented web page or document. Figures 5-9 illustrate various embodiments of the invention to determine a contextual title for a web page or document. The order of the presented embodiments in Figures 5-9 represent an order to determine which embodiments to use in case different results are obtained by various aspects of the invention. In one aspect of the invention, operations may be executed follows: <part-num-ref name="invention, operations may be executed follows:">1)</part-num-ref>
|
| 236 |
+
Extract important key phrases from title and page content; <part-num-ref name="Extract important key phrases from title and page content;">2)</part-num-ref>
|
| 237 |
+
Extract important key phrases from <boundary-data type="header">-8-</boundary-data>
|
| 238 |
+
<page-break num="9"/>
|
| 239 |
+
<boundary-data type="header">MS <confidence value="5">#</confidence>
|
| 240 |
+
312091.01 Attorney Docket No. 003797.01311 </boundary-data>
|
| 241 |
+
title combine with URL; <part-num-ref name="Extract important key phrases from title combine with URL;">3)</part-num-ref>
|
| 242 |
+
Extract important key phrases from URL combine with page content; <part-num-ref name="Extract important key phrases from URL combine with page content;">4)</part-num-ref>
|
| 243 |
+
Extract important key phrase from page content; <part-num-ref name="Extract important key phrase from page content;">5)</part-num-ref>
|
| 244 |
+
Extract important key phrase from URL independently; and <part-num-ref name="Extract important key phrase from URL independently; and">6)</part-num-ref>
|
| 245 |
+
Extract important key phrases from title. Each of the above listed six steps is optional. The more anterior operation may have a higher priority. </p>
|
| 246 |
+
<p id="p-37" num="37">[31<confidence value="5">]</confidence>
|
| 247 |
+
Figures 5 and <part-num-ref name="and">6</part-num-ref>
|
| 248 |
+
illustrate exemplary contextual title creation from a web page or document in accordance with an aspect of the invention. In Figure 5, a user's web page <part-num-ref name="user's web page">500</part-num-ref>
|
| 249 |
+
is displayed on a tab web browser <part-num-ref name="tab web browser">505.</part-num-ref>
|
| 250 |
+
The title of the web page <part-num-ref name="web page">500</part-num-ref>
|
| 251 |
+
may contain the user's name. For instance, the title of web page <part-num-ref name="title of web page">500</part-num-ref>
|
| 252 |
+
may be "Zheng Chen's Home Page" <part-num-ref name="may be "Zheng Chen's Home Page"">510.</part-num-ref>
|
| 253 |
+
</p>
|
| 254 |
+
<p id="p-38" num="38">
|
| 255 |
+
<confidence value="5">[</confidence>
|
| 256 |
+
32] In an aspect of the invention, key phrases are extracted from web page content and a web page title. Based on frequency, it may be determined that the words "Zheng Chen" are the most frequent words appearing in the page content or body of the web page <part-num-ref name="web page">500.</part-num-ref>
|
| 257 |
+
In addition, the words "Zheng Chen" may also appear in the title of web page <part-num-ref name="title of web page">500.</part-num-ref>
|
| 258 |
+
Based on the words being frequently used in the content and title of web page <part-num-ref name="content and title of web page">500,</part-num-ref>
|
| 259 |
+
the words "Zheng Chen" may be selected as the contextual title for web page <part-num-ref name="contextual title for web page">500.</part-num-ref>
|
| 260 |
+
Figure 6 shows the contextual title of "Zheng Chen" <part-num-ref name="contextual title of "Zheng Chen"">605</part-num-ref>
|
| 261 |
+
being displayed on a tab of the tab web browser. </p>
|
| 262 |
+
<p id="p-39" num="39">[33] Figure 7 illustrates another aspect of contextual title creation from a web page or document. In Figure 7, a web page <part-num-ref name="web page">700</part-num-ref>
|
| 263 |
+
is displayed on a tab web browser <part-num-ref name="tab web browser">705.</part-num-ref>
|
| 264 |
+
The web page <part-num-ref name="web page">700</part-num-ref>
|
| 265 |
+
may comprise information on an education institution such as Massachusetts Institute of Technology (MIT). The title of the web page may be mit.edu <part-num-ref name="web page may be mit.edu">710</part-num-ref>
|
| 266 |
+
as shown on tab <part-num-ref name="as shown on tab">715</part-num-ref>
|
| 267 |
+
in Figure 7. In an aspect of the invention, key phrases are extracted from web page content and combined with the title of the web page. </p>
|
| 268 |
+
<p id="p-40" num="40">[34] For example, based on frequency, it may be determined that the words "MIT" may be the most frequent words appearing in the page content or body of web page <part-num-ref name="page content or body of web page">700.</part-num-ref>
|
| 269 |
+
In addition, the words "MIT" may also appear in the title of the web page <part-num-ref name="web page">700.</part-num-ref>
|
| 270 |
+
Based on the words being frequently used in the content and title of the web page <part-num-ref name="web page">700,</part-num-ref>
|
| 271 |
+
the words "MIT" may be selected as the contextual title for web page <part-num-ref name="contextual title for web page">700.</part-num-ref>
|
| 272 |
+
</p>
|
| 273 |
+
<boundary-data type="header">-9-</boundary-data>
|
| 274 |
+
<boundary-data type="header">MS #312091.01 Attorney Docket No. 003797.01311</boundary-data>
|
| 275 |
+
<p id="p-41" num="41">
|
| 276 |
+
<page-break num="10"/>
|
| 277 |
+
<confidence value="5885">[35]</confidence>
|
| 278 |
+
Figure 8 illustrates a further form of contextual title creation in accordance with an aspect of the invention. In Figure 8, a web page <part-num-ref name="web page">800</part-num-ref>
|
| 279 |
+
is displayed on a tab web browser <part-num-ref name="tab web browser">805.</part-num-ref>
|
| 280 |
+
</p>
|
| 281 |
+
<p id="p-42" num="42">The web page may comprise information from a user's personal home page. The web page <part-num-ref name="web page">800</part-num-ref>
|
| 282 |
+
may not have a syntax title and instead use a default title such as "Microsoft.com" <part-num-ref name="default title such as "Microsoft.com"">810.</part-num-ref>
|
| 283 |
+
In an aspect of the invention, key phrases are extracted from web page content and combined with the URL of the web page. </p>
|
| 284 |
+
<p id="p-43" num="43">[36] For example, based on frequency, it may be determined that the words "Jian Wang" may be the most frequent phrase appearing in the page content or body of web page <part-num-ref name="page content or body of web page">800.</part-num-ref>
|
| 285 |
+
In addition, the phrase "Jian Wang" may also appear in the URL of the web page <part-num-ref name="web page">800.</part-num-ref>
|
| 286 |
+
</p>
|
| 287 |
+
<p id="p-44" num="44">Based on the phrase being frequently used in the content of web page <part-num-ref name="content of web page">800</part-num-ref>
|
| 288 |
+
and in the URL of the web page <part-num-ref name="web page">800,</part-num-ref>
|
| 289 |
+
the phrase "Jian Wang" may be determined as the contextual title of web page <part-num-ref name="contextual title of web page">800.</part-num-ref>
|
| 290 |
+
The contextual title "Jian Wang" may be displayed on a tab <part-num-ref name="tab">815</part-num-ref>
|
| 291 |
+
of tab web browser <part-num-ref name="of tab web browser">805.</part-num-ref>
|
| 292 |
+
</p>
|
| 293 |
+
<p id="p-45" num="45">[37] Figure 9 illustrates an additional form of contextual title creation in accordance with a further aspect of the invention. In Figure 9, a web page <part-num-ref name="web page">900</part-num-ref>
|
| 294 |
+
is displayed on a tab web browser <part-num-ref name="tab web browser">905.</part-num-ref>
|
| 295 |
+
The web page <part-num-ref name="web page">900</part-num-ref>
|
| 296 |
+
may comprise information such as publications and abstracts of various articles or journals. The URL of web page <part-num-ref name="URL of web page">900</part-num-ref>
|
| 297 |
+
may not have a descriptive syntax title for use as a contractual title. In addition, web page <part-num-ref name="contractual title. In addition, web page">900</part-num-ref>
|
| 298 |
+
may have a URL which also does not contain and words or phrases which could represent the semantic content of web page <part-num-ref name="semantic content of web page">900.</part-num-ref>
|
| 299 |
+
However, based on the frequency of words or phrases used in the page content, a contextual title of "Data Clustering" <part-num-ref name="contextual title of "Data Clustering"">910</part-num-ref>
|
| 300 |
+
may be used to represent the semantic content of web page <part-num-ref name="semantic content of web page">900.</part-num-ref>
|
| 301 |
+
</p>
|
| 302 |
+
<p id="p-46" num="46">[38] In a further aspect of the invention, a single word or words comprising a URL may be best suited for describing content of a web page or document. Under this embodiment, the contextual title may be based on the word or phrase contained in the URL.</p>
|
| 303 |
+
<p id="p-47" num="47">
|
| 304 |
+
<confidence value="5885">[39]</confidence>
|
| 305 |
+
In another aspect of the invention, the most frequent words or words in a title may be used to describe the semantic content of a web page. This embodiment may be used as a <boundary-data type="header">-10-</boundary-data>
|
| 306 |
+
<page-break num="11"/>
|
| 307 |
+
<boundary-data type="header">
|
| 308 |
+
<confidence value="88">MS</confidence>
|
| 309 |
+
<confidence value="6">#</confidence>
|
| 310 |
+
312091.<confidence value="66">01</confidence>
|
| 311 |
+
Attorney Docket No. 003797.013<confidence value="88">11</confidence>
|
| 312 |
+
</boundary-data>
|
| 313 |
+
default to determine a contextual title of a web page or document when the other above described embodiments do not produce a contextual title. </p>
|
| 314 |
+
<p id="p-48" num="48">[40<confidence value="2">]</confidence>
|
| 315 |
+
While the invention has been described with respect to specific examples including presently preferred modes of carrying out the invention, those skilled in the art will appreciate that there are numerous variations and permutations of the above described systems and techniques that fall within the spirit and scope of the invention as set forth in the appended claims. </p>
|
| 316 |
+
<boundary-data type="header">-11-</boundary-data>
|
| 317 |
+
</description>
|
| 318 |
+
</us-patent-application>
|
| 319 |
+
|
applicant/11244005.xml
ADDED
|
@@ -0,0 +1,326 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11244005</doc-number>
|
| 8 |
+
<date>2005-10-06</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">Docket No. 1500.1111</boundary-data>
|
| 14 |
+
<heading id="h-1">TITLE OF THE INVENTION</heading>
|
| 15 |
+
<p id="p-1" num="1">
|
| 16 |
+
<confidence value="8">A</confidence>
|
| 17 |
+
WORK<confidence value="7">F</confidence>
|
| 18 |
+
LOW SYSTEM FOR 3D MODEL CREATION </p>
|
| 19 |
+
<heading id="h-2">BACKGROUND OF THE INVENTION</heading>
|
| 20 |
+
<p id="p-2" num="2">1. Field of the <confidence value="5">I</confidence>
|
| 21 |
+
nvention [0001] The present invention is directed to workflow system for 3D model creation. </p>
|
| 22 |
+
<p id="p-3" num="3">2. Description of the Related Art [0002] In today's modeling environment there is a need for rapid 3D shape generation and design for a 3D modeling system. Conventional 3D modeling tools require fairly high precision, detail and attention to generate shapes. Conversely, sketching using a paint brush or pencil allows for very fluid and approximate shape exploration. However, once a 2D sketch is accepted, it is difficult to translate it into a 3D model.</p>
|
| 23 |
+
<p id="p-4" num="4">[0003] Solutions to today involve a simplistic approach where a 2D image plane serves as a backdrop reference for constructing 3D models in front of the image plane. While some reference can be used, it does not allow for rapid shape exploration. Also, often one or two reference image planes are used. Alternatively, state-of-the-art 3D modeling applications allow one or more construction planes to assist the user in placing or aligning 3D geometry in the scene. The motivation behind these construction planes is to make 3D geometry construction more efficient and have no notion of combining inking (i.e., sketching) and 3D geometry in a single plane.</p>
|
| 24 |
+
<p id="p-5" num="5">[0004] What is needed is a system that combines the sketchy and rapid nature of 2D painting with the precision and placement of 3D modeling. Such a needed system would bridge the gap between rapid concept sketching and precise 3D modeling. Such a needed hybrid system would leverage the strengths of both approaches. This type of hybrid workflow combining the benefits of rapid sketching with the ability to translate the concepts more readily into precise 3D modeling allows users "stay in one tool" to progress through "ideation" to more robust 3D designs.</p>
|
| 25 |
+
<heading id="h-3">SUMMARY OF THE INVENTION</heading>
|
| 26 |
+
<p id="p-6" num="6">[0005] It is an aspect of the present invention to provide a system that allows 2D sketching and 3D geometry creation to be performed in concert to develop a 3D model.</p>
|
| 27 |
+
<boundary-data type="header">
|
| 28 |
+
<confidence value="8">1</confidence>
|
| 29 |
+
</boundary-data>
|
| 30 |
+
<boundary-data type="header">Docket No. 1500.1111</boundary-data>
|
| 31 |
+
<p id="p-7" num="7">
|
| 32 |
+
<page-break num="2"/>
|
| 33 |
+
[0006] It is another aspect of the present invention to encourage shape exploration by the use of ink and a drawing on paper analogy while at the same time providing a geometry construction capability that works with the drawing. </p>
|
| 34 |
+
<p id="p-8" num="8">[0007<confidence value="5">]</confidence>
|
| 35 |
+
The above aspects can be attained by a 3D modeling workflow system is disclosed that allows the user to create multiple 2D planes in the 3D scene each having a position and orientation. These 2D planes can contain a combination of paint and model construction geometry. The construction geometry can span multiple 2D planes. Collectively the 2D planes allow a 3D sketch of a 3D object where portions of the object are drawn in by paint and other portions are composed of geometry. The user can swap between painting on the 2D planes and creating model geometry as needed during development. </p>
|
| 36 |
+
<p id="p-9" num="9">[0008] These together with other aspects and advantages which will be subsequently apparent, reside in the details of construction and operation as more fully hereinafter described and claimed, reference being had to the accompanying drawings forming a part hereof, wherein like numerals refer to like parts throughout.</p>
|
| 37 |
+
<heading id="h-4">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 38 |
+
<p id="p-10" num="10">[0009] Figure 1 depicts the creation of a plane.</p>
|
| 39 |
+
<p id="p-11" num="11">[0010] Figure 2 shows a user drawing/painting on a plane or sketch canvas.</p>
|
| 40 |
+
<p id="p-12" num="12">
|
| 41 |
+
<confidence value="5">[</confidence>
|
| 42 |
+
0011] Figure 3 illustrates that a new plane can be created by duplication and then be moved. </p>
|
| 43 |
+
<p id="p-13" num="13">[0012] Figure 4 shows creation of a model geometry curve connecting planes.</p>
|
| 44 |
+
<p id="p-14" num="14">[0013] Figure 5 show creating geometry directly on a plane.</p>
|
| 45 |
+
<p id="p-15" num="15">[0014] Figure 6 depicts connecting curves to form a curve network.</p>
|
| 46 |
+
<p id="p-16" num="16">[0015] Figure 7 illustrates surface geometry being automatically created for a curve network.</p>
|
| 47 |
+
<p id="p-17" num="17">[0016] Figure 8 shows a new plane being created that intersects the previously created planes.</p>
|
| 48 |
+
<p id="p-18" num="18">[0017] Figure 9 shows a brush stroke on a plane creating curve geometry.</p>
|
| 49 |
+
<p id="p-19" num="19">[0018] Figures 10, 11 and <part-num-ref name="and">12</part-num-ref>
|
| 50 |
+
show the paint strokes and planes used to crate a sketch model of a car. </p>
|
| 51 |
+
<boundary-data type="header">
|
| 52 |
+
<confidence value="8">2</confidence>
|
| 53 |
+
</boundary-data>
|
| 54 |
+
<boundary-data type="header">Docket No. 1500.1111</boundary-data>
|
| 55 |
+
<p id="p-20" num="20">
|
| 56 |
+
<page-break num="3"/>
|
| 57 |
+
[0019] Figure 13 depicts a curve network created using the reference sketches of figures 10-12. </p>
|
| 58 |
+
<p id="p-21" num="21">[0020] Figure 14 shows surface geometry created for the curve network of figure 13.</p>
|
| 59 |
+
<p id="p-22" num="22">[0021] Figure 15 shows the operations of making a paint stroke.</p>
|
| 60 |
+
<p id="p-23" num="23">[0022] Figure 16 illustrates geometry curve creation.</p>
|
| 61 |
+
<p id="p-24" num="24">[0023] Figure 17 shows the operations for geometry curves between canvases.</p>
|
| 62 |
+
<p id="p-25" num="25">[0024] Figure 18 shows target plane setting.</p>
|
| 63 |
+
<p id="p-26" num="26">[0025] Figure 19 illustrates hardware components.</p>
|
| 64 |
+
<p id="p-27" num="27">[0026] Figure 20 illustrates the possible workflow flow.</p>
|
| 65 |
+
<p id="p-28" num="28">[0027] Figure 21 shows the workflow of the example discussed with respect to figures 1-9.</p>
|
| 66 |
+
<p id="p-29" num="29">[0028] Figure 22 shows a relationship between world and image space.</p>
|
| 67 |
+
<heading id="h-5">DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS</heading>
|
| 68 |
+
<p id="p-30" num="30">[0029] The present invention is a workflow system that allows a user to sketch the outlines of an object, such as the design of a car, using conventional input tools, such as a mouse, a touch screen stylus, a tablet, etc. in a model space and then use that sketch as a reference to create model geometry for the object in the model space. The user sketches during a paint operation and converts to a geometry operation to create the model geometry. The user can switch back and forth between the drawing operation and the geometry operation by selecting appropriate tools, such as a pencil tool for drawing and a CV or Edit Point Curve Tool for making a geometry curve stroke, allowing the user to sketch a few lines, create geometry for the lines, then sketch some more lines, etc. During the paint operation sketching or drawing, the user uses the typical drawing tools and functions available in a conventional drawing system such as in the StudioTools<confidence value="5">®</confidence>
|
| 69 |
+
available from Alias Systems Corp. The sketching is performed on planes or two-dimensional (2D) canvases that can be arbitrarily positioned or repositioned in the three- dimensional (3D) model space. During the creating of model geometry in the geometry operation positions geometric points or curves in the 3D model space, using the sketches as a reference and using the conventional tools and functions for geometry creation found in a system such as StudioTools<confidence value="68">®.</confidence>
|
| 70 |
+
</p>
|
| 71 |
+
<boundary-data type="header">
|
| 72 |
+
<confidence value="8">3</confidence>
|
| 73 |
+
</boundary-data>
|
| 74 |
+
<boundary-data type="header">Docket No. 1500.1111</boundary-data>
|
| 75 |
+
<p id="p-31" num="31">
|
| 76 |
+
<page-break num="4"/>
|
| 77 |
+
[0030] The user of the present invention can start with the painting or sketch operation (although a canvas can be created during other operations) and creates a sketch plane or canvas <part-num-ref name="sketch plane or canvas">102</part-num-ref>
|
| 78 |
+
on an infinite plane <part-num-ref name="infinite plane">104</part-num-ref>
|
| 79 |
+
in the 3D model space of the figure 1. This plane <part-num-ref name="figure 1. This plane">102</part-num-ref>
|
| 80 |
+
can have arbitrary dimensions as needed by the user. This plane can be arbitrarily positioned by the user designating the plane <part-num-ref name="plane">102</part-num-ref>
|
| 81 |
+
and dragging it into a desired position and orientation. The plane <part-num-ref name="plane">102</part-num-ref>
|
| 82 |
+
is shown perspectively and in coincidence with the origin of the model space but could be created at any position in the model space. </p>
|
| 83 |
+
<p id="p-32" num="32">[0031] The user then can draw on the plane <part-num-ref name="plane">102</part-num-ref>
|
| 84 |
+
by selecting a paint tool and making painting/drawing strokes where figure 2 shows the plane <part-num-ref name="plane">102</part-num-ref>
|
| 85 |
+
with four paint strokes 202-208 having been made on the plane <part-num-ref name="plane">102.</part-num-ref>
|
| 86 |
+
As can be seen, the plane or canvas <part-num-ref name="plane or canvas">102</part-num-ref>
|
| 87 |
+
is treated much like a piece of paper upon which the user can draw. This canvas <part-num-ref name="user can draw. This canvas">102</part-num-ref>
|
| 88 |
+
could even be positioned so that it is perpendicular to the users view point, so that it appears like a piece of paper positioned on the display screen, reinforcing the paper sketching analogy for the user. </p>
|
| 89 |
+
<p id="p-33" num="33">[0032] The user, while in the drawing mode, can create another plane upon which to sketch.</p>
|
| 90 |
+
<p id="p-34" num="34">This plane can be empty as in figure 1 or the user can create a copy <part-num-ref name="copy">302</part-num-ref>
|
| 91 |
+
as depicted in figure 3. </p>
|
| 92 |
+
<p id="p-35" num="35">A duplicate of a plane <part-num-ref name="plane">302</part-num-ref>
|
| 93 |
+
also includes duplicates 304-310 of the paint stokes 202-208 of the plane <part-num-ref name="plane">102</part-num-ref>
|
| 94 |
+
being copied. In figure 3, the user has positioned or moved the duplicate plane <part-num-ref name="duplicate plane">302</part-num-ref>
|
| 95 |
+
above and at an angle with respect to original plane <part-num-ref name="angle with respect to original plane">102.</part-num-ref>
|
| 96 |
+
</p>
|
| 97 |
+
<p id="p-36" num="36">[0033] When the user is ready to use the sketch(es) as a reference for model geometry creation, the user switches the system into a geometry operation by, for example, conventional activation of a tool for drawing geometry curves, such as cv curve, edit point curve, blend curve, or sketch curve. In this operation, the user can specify the parameters of a model curve. Figure 4 shows a geometry curve <part-num-ref name="geometry curve">402</part-num-ref>
|
| 98 |
+
the user has created by snapping the curve to intersection points <part-num-ref name="curve to intersection points">404</part-num-ref>
|
| 99 |
+
and <part-num-ref name="and">406</part-num-ref>
|
| 100 |
+
of the planes <part-num-ref name="planes">302</part-num-ref>
|
| 101 |
+
and <part-num-ref name="and">102.</part-num-ref>
|
| 102 |
+
This particular operation has created geometry connecting the two planes <part-num-ref name="two planes">102</part-num-ref>
|
| 103 |
+
and <part-num-ref name="and">302.</part-num-ref>
|
| 104 |
+
</p>
|
| 105 |
+
<p id="p-37" num="37">[0034] The user can also create geometry coincident with or directly on a plane paint stroke as depicted in figure 5 where the user has specified a model geometry curve <part-num-ref name="model geometry curve">502</part-num-ref>
|
| 106 |
+
along part of the paint stroke <part-num-ref name="paint stroke">308</part-num-ref>
|
| 107 |
+
in plane canvas <part-num-ref name="in plane canvas">302.</part-num-ref>
|
| 108 |
+
</p>
|
| 109 |
+
<p id="p-38" num="38">[0035] Figure 6 shows, while in the geometry mode, the creation of curves <part-num-ref name="creation of curves">602</part-num-ref>
|
| 110 |
+
and <part-num-ref name="and">604</part-num-ref>
|
| 111 |
+
by the user where curve <part-num-ref name="user where curve">602</part-num-ref>
|
| 112 |
+
connects between planes <part-num-ref name="connects between planes">102</part-num-ref>
|
| 113 |
+
and <part-num-ref name="and">302</part-num-ref>
|
| 114 |
+
and curve <part-num-ref name="and curve">604</part-num-ref>
|
| 115 |
+
in plane <part-num-ref name="in plane">102.</part-num-ref>
|
| 116 |
+
</p>
|
| 117 |
+
<p id="p-39" num="39">The set of curves 402, 502, 602 and <part-num-ref name="and">604</part-num-ref>
|
| 118 |
+
form a network of curves. </p>
|
| 119 |
+
<boundary-data type="header">
|
| 120 |
+
<confidence value="8">4</confidence>
|
| 121 |
+
</boundary-data>
|
| 122 |
+
<boundary-data type="header">Docket No. 1500.1111</boundary-data>
|
| 123 |
+
<p id="p-40" num="40">
|
| 124 |
+
<page-break num="5"/>
|
| 125 |
+
[0036] While in the geometry mode, the user can use a network of curves, such as curves <part-num-ref name="network of curves, such as curves">402,</part-num-ref>
|
| 126 |
+
<part-num-ref name="network of curves, such as curves 402,">502,</part-num-ref>
|
| 127 |
+
<part-num-ref name="network of curves, such as curves 402, 502,">602</part-num-ref>
|
| 128 |
+
and <part-num-ref name="and">604</part-num-ref>
|
| 129 |
+
to create surface geometry <part-num-ref name="to create surface geometry">702</part-num-ref>
|
| 130 |
+
as shown in figure 7. </p>
|
| 131 |
+
<p id="p-41" num="41">[0037] As previously discussed the user can switch between the painting and geometry operations at any time. Figure 8 shows a plane <part-num-ref name="plane">802</part-num-ref>
|
| 132 |
+
created by the user after switching into the paint operation where the user has made paint strokes <part-num-ref name="user has made paint strokes">804,</part-num-ref>
|
| 133 |
+
<part-num-ref name="user has made paint strokes 804,">806</part-num-ref>
|
| 134 |
+
and <part-num-ref name="and">808</part-num-ref>
|
| 135 |
+
on the canvas (plane). </p>
|
| 136 |
+
<p id="p-42" num="42">This plane 802 has been oriented by the user relative to planes <part-num-ref name="user relative to planes">102</part-num-ref>
|
| 137 |
+
and <part-num-ref name="and">302,</part-num-ref>
|
| 138 |
+
so that it intersects both of these previously created planes <part-num-ref name="and 302, so that it intersects both of these previously created planes">102</part-num-ref>
|
| 139 |
+
and <part-num-ref name="and">302.</part-num-ref>
|
| 140 |
+
In this example, the user has created a center line profile sketch or a cross sectional sketch much as the user might do on paper to show what a model should look like in cross sectional profile. </p>
|
| 141 |
+
<p id="p-43" num="43">[0038] As for other sketches the user can switch to the geometry operation and create geometry using the plane <part-num-ref name="plane">802</part-num-ref>
|
| 142 |
+
as a reference. Figure 9 depicts a stylus type tool <part-num-ref name="stylus type tool">902</part-num-ref>
|
| 143 |
+
creating a geometry curve <part-num-ref name="geometry curve">904</part-num-ref>
|
| 144 |
+
on the plane <part-num-ref name="plane">802</part-num-ref>
|
| 145 |
+
using a brush stroke that substantially traces the paint stroke <part-num-ref name="paint stroke">806</part-num-ref>
|
| 146 |
+
previously created. </p>
|
| 147 |
+
<p id="p-44" num="44">[0039] The user can continue this process of building up a model one or more planes at a time by creating paint stroke reference planes that can be used to create model geometry.</p>
|
| 148 |
+
<p id="p-45" num="45">Figure 10 shows the paint stokes created by a user in this way to sketch a model of a car where the display of the planes on which the strokes have been made is disabled. Figure 11 shows this same sketch model with the display of the planes enabled. As can bee seen, the planes are oriented as the user might orient them when conceptualizing the basics of the car being modeled. Figure 12 shows the same model oriented with the front of the model car facing the user again showing the relationship between the canvas planes. In such a changed view, it is possible for the planes and the drawings, geometry, etc, to be in an edge-on orientation where the drawn lines may become invisible.</p>
|
| 149 |
+
<p id="p-46" num="46">[0040] Figure 13 shows the geometry created by the user for one side of the car by connecting points and specifying curves. This curve network, as also previously discussed, can be used to automatically make model surfaces as depicted in figure 14.</p>
|
| 150 |
+
<p id="p-47" num="47">[0041] The above discussed workflow operations are effected by a set of processes as discussed below with respect to figures 15-18. As previously discussed a number of actions, such as the creation of a plane or canvas, are performed using the conventional tools of an available system such as StudioTools<confidence value="5">®</confidence>
|
| 151 |
+
. Such conventional operations will not be described. In addition other operations that are effected during the processes discussed below and performed <boundary-data type="header">
|
| 152 |
+
<confidence value="8">5</confidence>
|
| 153 |
+
</boundary-data>
|
| 154 |
+
<page-break num="6"/>
|
| 155 |
+
<boundary-data type="header">Docket No. 1500.1111</boundary-data>
|
| 156 |
+
automatically by a system such as StudioTools<confidence value="5">®</confidence>
|
| 157 |
+
, like creating a rendered paint stoke or snapping a brush stoke to a curve will also not be discussed in detail. To help in visualizing what is happening in the processes discussed below various perspective views of the relationships involved are also shown in the figures. </p>
|
| 158 |
+
<p id="p-48" num="48">[0042] Figure 15 shows the process operations that occur when a user makes a paint stoke in a 3D model space. When the system detects an input event, such as the touch of a stylus to a screen, the activation of a mouse button down event that signifies the input of a point of a paint stoke, the system inputs <part-num-ref name="system inputs">1502</part-num-ref>
|
| 159 |
+
that position <part-num-ref name="that position">1504</part-num-ref>
|
| 160 |
+
and can display is on the screen <part-num-ref name="screen">1506</part-num-ref>
|
| 161 |
+
in the form of some type of cursor, such as a visible point, an arrow, etc. The system then constructs <part-num-ref name="system then constructs">1508</part-num-ref>
|
| 162 |
+
a ray <part-num-ref name="ray">1510</part-num-ref>
|
| 163 |
+
from the point <part-num-ref name="point">1504</part-num-ref>
|
| 164 |
+
to a virtual camera <part-num-ref name="virtual camera">1512</part-num-ref>
|
| 165 |
+
that can represent the user viewpoint into the 3D scene through a near plane <part-num-ref name="near plane">1514</part-num-ref>
|
| 166 |
+
that essentially represents the display screen <part-num-ref name="display screen">1506.</part-num-ref>
|
| 167 |
+
</p>
|
| 168 |
+
<p id="p-49" num="49">[0043] At this point a target canvas is selected as follows. First, the ray is intersected with the finite rectangles in world space representing the existing canvases. Of the intersected canvases, the one closest to the eye is selected for drawing. If no intersection occurs, then the ray is intersected with the infinite plane containing the last used canvas. If this intersection occurs, then this canvas is selected for drawing. If not, then a new canvas is created which fills the screen and is perpendicular to the view direction. Other canvas selection techniques can be used, such as choosing the closest intersected plane to the eye point along a pick ray or having the user choose explicitly from a list of planes".</p>
|
| 169 |
+
<p id="p-50" num="50">[0044] The system then projects the ray <part-num-ref name="ray">1510</part-num-ref>
|
| 170 |
+
into the scene determine <part-num-ref name="scene determine">1516</part-num-ref>
|
| 171 |
+
an intersection <part-num-ref name="intersection">1518</part-num-ref>
|
| 172 |
+
of the ray with the canvas or drawing plane <part-num-ref name="canvas or drawing plane">1520</part-num-ref>
|
| 173 |
+
in the scene. This point is a point with 2D coordinates that correspond to the 2D position of the point on the intersected canvas plane. </p>
|
| 174 |
+
<p id="p-51" num="51">This point is then added 1522 to the list of points for a paint stroke. As long as the user is inputting a paint stroke <part-num-ref name="paint stroke">1524,</part-num-ref>
|
| 175 |
+
such as by moving the mouse and holding the paint activation button down, points are added to the list and would appear in the scene <part-num-ref name="scene">1526</part-num-ref>
|
| 176 |
+
if the system was enabled to show the points of the stroke as it is being made. At the end of the brush stoke, or during the stroke, the system creates a curve in the scene <part-num-ref name="scene">1528</part-num-ref>
|
| 177 |
+
corresponding to the points. </p>
|
| 178 |
+
<p id="p-52" num="52">[0045] Figure 16 depicts the operations associated with the user making a brush stroke that creates a geometry curve on a plane or canvas in the 3D model space. Like the painting operation discussed above, the system inputs <part-num-ref name="system inputs">1602</part-num-ref>
|
| 179 |
+
the point, constructs a ray <part-num-ref name="ray">1604,</part-num-ref>
|
| 180 |
+
determines a target canvas as previously discussed, and determines <part-num-ref name="target canvas as previously discussed, and determines">1606</part-num-ref>
|
| 181 |
+
an intersection point in the <boundary-data type="header">
|
| 182 |
+
<confidence value="8">6</confidence>
|
| 183 |
+
</boundary-data>
|
| 184 |
+
<page-break num="7"/>
|
| 185 |
+
<boundary-data type="header">Docket No. 1500.1111</boundary-data>
|
| 186 |
+
model space. However, this intersection point <part-num-ref name="model space. However, this intersection point">1608</part-num-ref>
|
| 187 |
+
is the 3D intersection of the point with the plane in the world space of the model. This point is added <part-num-ref name="model. This point is added">1610</part-num-ref>
|
| 188 |
+
to the list of points for this brush stroke curve. These points may appear in the scene <part-num-ref name="scene">1612</part-num-ref>
|
| 189 |
+
were this display function enabled. Once the user is finished with the stroke, the system fits <part-num-ref name="system fits">1614</part-num-ref>
|
| 190 |
+
a spline curve to the points <part-num-ref name="points">1616</part-num-ref>
|
| 191 |
+
and then inserts <part-num-ref name="and then inserts">1618</part-num-ref>
|
| 192 |
+
that 3D curve into the 3D data model being constructed. </p>
|
| 193 |
+
<p id="p-53" num="53">[0046] When the user is creating a curve on multiple canvases, as depicted in figure 17, when the user activates the curve operation by, for example, depressing an appropriate mouse button, the system initializes <part-num-ref name="system initializes">1702</part-num-ref>
|
| 194 |
+
a new system curve C. This new curve is initially empty and a control point, p, for that curve is added <part-num-ref name="control point, p, for that curve is added">1704.</part-num-ref>
|
| 195 |
+
This control point will be assigned a position in the 3D space depending on the plane "intended" by the user. Like previously the input <part-num-ref name="input">1706</part-num-ref>
|
| 196 |
+
point is used to construct <part-num-ref name="point is used to construct">1708</part-num-ref>
|
| 197 |
+
a ray on the near plane. The system then determines <part-num-ref name="system then determines">1710</part-num-ref>
|
| 198 |
+
if a target plane has been set, that is the user has selected or designated a plane upon which to place the point. If a plane has not been set operations of setting the plane are performed (see figure 18). If the plane has been set, the point is moved <part-num-ref name="point is moved">1714</part-num-ref>
|
| 199 |
+
from the near plane to the intersection of the ray with the target plane. The moving of the control point about on the target plane in the loop <part-num-ref name="loop">1706,</part-num-ref>
|
| 200 |
+
<part-num-ref name="loop 1706,">1708,</part-num-ref>
|
| 201 |
+
<part-num-ref name="loop 1706, 1708,">1710</part-num-ref>
|
| 202 |
+
and <part-num-ref name="and">1714</part-num-ref>
|
| 203 |
+
continues until the user gets it in the desired position and the mouse button is released. The target plane is then unset <part-num-ref name="target plane is then unset">1716</part-num-ref>
|
| 204 |
+
and, if the operation is not changed, another control point is added <part-num-ref name="operation is not changed, another control point is added">1704</part-num-ref>
|
| 205 |
+
to the geometry curve, a target plane is selected and this point is also moved to a desired position. When the laying down of control points for the desired planes is completed, a geometry curve is placed in the model for the points. </p>
|
| 206 |
+
<p id="p-54" num="54">[0047] In setting a target plane (see figure 18) the system determines <part-num-ref name="system determines">1802</part-num-ref>
|
| 207 |
+
whether the ray point of intersection <part-num-ref name="ray point of intersection">(1504,</part-num-ref>
|
| 208 |
+
<part-num-ref name="ray point of intersection (1504,">1608)</part-num-ref>
|
| 209 |
+
intersects a boundary of a canvas rectangle. When this occurs the target plane is set <part-num-ref name="target plane is set">1804</part-num-ref>
|
| 210 |
+
as the infinite plane on which the canvas resides. That is, the user can select the desired plane upon for which a control point is to be set by touching the edge of the desired canvas. Other methods than touching the edge can be used, such as choosing the closest intersected plane to the eye point along a pick ray or having the user choose explicitly from a list of planes. </p>
|
| 211 |
+
<p id="p-55" num="55">[0048] If the user does not touch the edge of a desired canvas, the system determines <part-num-ref name="system determines">1806</part-num-ref>
|
| 212 |
+
if the view of the system is a fixed orthogonal view. If the view is fixed the target plane is set <confidence value="6866">1801</confidence>
|
| 213 |
+
as the plane perpendicular to the view vector (or projected ray). This is could be <boundary-data type="header">
|
| 214 |
+
<confidence value="8">7</confidence>
|
| 215 |
+
</boundary-data>
|
| 216 |
+
<page-break num="8"/>
|
| 217 |
+
<boundary-data type="header">Docket No. 1500.1111</boundary-data>
|
| 218 |
+
considered as essentially treating the display surface as a piece of paper. If the view is not set as fixed, the target plane becomes <part-num-ref name="target plane becomes">1810</part-num-ref>
|
| 219 |
+
the x-y plane where the z coordinate has a zero value. </p>
|
| 220 |
+
<p id="p-56" num="56">[0049] Figure 19 shows hardware components that can be used for the processes and workflow of the present invention. The user can input into desktop type computer <part-num-ref name="user can input into desktop type computer">1902</part-num-ref>
|
| 221 |
+
operation switches and point placements, etc, using a keyboard <part-num-ref name="keyboard">1904</part-num-ref>
|
| 222 |
+
and/or a mouse <part-num-ref name="mouse">1906</part-num-ref>
|
| 223 |
+
as well as other input devices, as previously mentioned. The computer displays the 3D model space along with the appropriate system GU<confidence value="5">I</confidence>
|
| 224 |
+
s with which the user interacts on the display <part-num-ref name="display">1908.</part-num-ref>
|
| 225 |
+
</p>
|
| 226 |
+
<p id="p-57" num="57">The system includes the traditional. The system also includes permanent or removable storage, such as magnetic and optical discs, RAM, ROM, etc. on which the process and data structures of the present invention can be stored and distributed. The processes can also be distributed via, for example, downloading over a network such as the Internet and can be executed in a client server relationship.</p>
|
| 227 |
+
<p id="p-58" num="58">
|
| 228 |
+
<confidence value="5">[</confidence>
|
| 229 |
+
0050] The processes discussed above with respect to figures 15-18 allow a flexible workflow discussed previously with respect to figures 1-14 and as depicted in figure 20. This workflow includes the typical first operation of creating <part-num-ref name="typical first operation of creating">2002</part-num-ref>
|
| 230 |
+
a canvas or plane. In the orient (or move) operation <part-num-ref name="orient (or move) operation">2004</part-num-ref>
|
| 231 |
+
the user moves the plane to a desired position. In the duplicate operation <part-num-ref name="duplicate operation">2006</part-num-ref>
|
| 232 |
+
canvases can be duplicated. The user draws or paints on the canvases in the draw operation <part-num-ref name="draw operation">2008.</part-num-ref>
|
| 233 |
+
The geometry operations include creating <part-num-ref name="geometry operations include creating">1010</part-num-ref>
|
| 234 |
+
a geometry curve on the canvas, creating surface geometry <part-num-ref name="canvas, creating surface geometry">2012</part-num-ref>
|
| 235 |
+
and creating 2<confidence value="66">01</confidence>
|
| 236 |
+
4curve geometry between or across canvases. The workflow of the example of figures 1-14 is partially shown in figure 21 and involves flows from canvas creation <part-num-ref name="and involves flows from canvas creation">2002</part-num-ref>
|
| 237 |
+
figuree) through drawing <part-num-ref name="figuree) through drawing">2008</part-num-ref>
|
| 238 |
+
on the canvas (figure <part-num-ref name="canvas (figure">2)</part-num-ref>
|
| 239 |
+
then duplicating <part-num-ref name="then duplicating">2006</part-num-ref>
|
| 240 |
+
it (figure 3), followed by orienting <part-num-ref name="it (figure 3), followed by orienting">2004</part-num-ref>
|
| 241 |
+
the duplicate canvas (figure 3), creating geometry between canvases (figure 4), creating surface geometry (figure <part-num-ref name="duplicate canvas (figure 3), creating geometry between canvases (figure 4), creating surface geometry (figure">5)</part-num-ref>
|
| 242 |
+
and creating curve geometry on the canvases (figure 6). </p>
|
| 243 |
+
<p id="p-59" num="59">[0051<confidence value="5">]</confidence>
|
| 244 |
+
The relationship between world space and image space as used in the present invention is depicted in figure 22. A point which lies on the canvas plane <part-num-ref name="canvas plane">2208</part-num-ref>
|
| 245 |
+
can be described in world space <part-num-ref name="can be described in world space">2204</part-num-ref>
|
| 246 |
+
as a 3D point p (2202), or in image space <part-num-ref name="3D point p (2202), or in image space">2210</part-num-ref>
|
| 247 |
+
as a 2D point s <part-num-ref name="2D point s">2206.</part-num-ref>
|
| 248 |
+
To convert between image space and world space a set of matrices as set forth below are used. </p>
|
| 249 |
+
<boundary-data type="header">
|
| 250 |
+
<confidence value="8">8</confidence>
|
| 251 |
+
</boundary-data>
|
| 252 |
+
<boundary-data type="header">Docket No. 1500.1111</boundary-data>
|
| 253 |
+
<p id="p-60" num="60">
|
| 254 |
+
<page-break num="9"/>
|
| 255 |
+
M = Image to World = Im<confidence value="55">00</confidence>
|
| 256 |
+
<confidence value="865">m10</confidence>
|
| 257 |
+
m20 m30<confidence value="5">1</confidence>
|
| 258 |
+
<confidence value="5855">Imo1</confidence>
|
| 259 |
+
<confidence value="6">.</confidence>
|
| 260 |
+
<confidence value="2">|</confidence>
|
| 261 |
+
<confidence value="2858">|m02</confidence>
|
| 262 |
+
<confidence value="2">.</confidence>
|
| 263 |
+
</p>
|
| 264 |
+
<p id="p-61" num="61">
|
| 265 |
+
<confidence value="2">|</confidence>
|
| 266 |
+
m03<confidence value="8">.</confidence>
|
| 267 |
+
<confidence value="6">.</confidence>
|
| 268 |
+
m33<confidence value="2">|</confidence>
|
| 269 |
+
Note, that this is a 4x4 homogeneous transform matrix. </p>
|
| 270 |
+
<p id="p-62" num="62">Converting image space to world space <confidence value="8">q</confidence>
|
| 271 |
+
<confidence value="8">=</confidence>
|
| 272 |
+
<confidence value="8">M</confidence>
|
| 273 |
+
<confidence value="6">*</confidence>
|
| 274 |
+
<confidence value="5882">Isu|</confidence>
|
| 275 |
+
<confidence value="5662">Isv|</confidence>
|
| 276 |
+
<confidence value="26865">|0.01</confidence>
|
| 277 |
+
<confidence value="5">1</confidence>
|
| 278 |
+
0.1<confidence value="5">1</confidence>
|
| 279 |
+
where q is a homogeneous point, q = qx, qy, qz, qw, su and sv are image space coordinates, 0.0 lies on the plane, 1.0 indicates a point rather than a vector is translated and <confidence value="222222228">px=qx/qw,</confidence>
|
| 280 |
+
<confidence value="22222222">py=qy/qw</confidence>
|
| 281 |
+
and <confidence value="222222228">pz=qz/qw.</confidence>
|
| 282 |
+
</p>
|
| 283 |
+
<p id="p-63" num="63">Converting world space to image space <confidence value="8">q</confidence>
|
| 284 |
+
<confidence value="8">=</confidence>
|
| 285 |
+
<confidence value="82">M-</confidence>
|
| 286 |
+
<confidence value="8">*</confidence>
|
| 287 |
+
<confidence value="488">ipx</confidence>
|
| 288 |
+
<confidence value="2">|</confidence>
|
| 289 |
+
<confidence value="5552">IPY|</confidence>
|
| 290 |
+
<confidence value="2882">|pz|</confidence>
|
| 291 |
+
<confidence value="5">1</confidence>
|
| 292 |
+
1.0<confidence value="5">1</confidence>
|
| 293 |
+
where px, py, pz are world space coordinates, 1.0 indicates a point translation and <confidence value="22222222">su=qx/qw</confidence>
|
| 294 |
+
and sv =qy/qw. </p>
|
| 295 |
+
<p id="p-64" num="64">[0052] The present invention uses a data structure that includes:</p>
|
| 296 |
+
<p id="p-65" num="65">Integer Width;</p>
|
| 297 |
+
<p id="p-66" num="66">Integer Height;</p>
|
| 298 |
+
<p id="p-67" num="67">How many pixels high and wide in image space coordinates does the image data extend.</p>
|
| 299 |
+
<p id="p-68" num="68">PixelArray image data;</p>
|
| 300 |
+
<p id="p-69" num="69">The actual data forming the canvas image.</p>
|
| 301 |
+
<p id="p-70" num="70">Matrix imagetoworldspace;</p>
|
| 302 |
+
<p id="p-71" num="71">Transform from image to world space where the matrix M is invertible <confidence value="858558">(IMI0)</confidence>
|
| 303 |
+
[0053] As discussed above, the present invention is a 3D modeling workflow that allows the user to create multiple 2D planes in the 3D scene each having a position and orientation. </p>
|
| 304 |
+
<p id="p-72" num="72">These 2D planes can contain a combination of paint, images and construction geometry (i.e., NURBS, polylines, etc.). Construction geometry can span multiple 2D planes. Collectively the 2D planes allow a 3D sketch of a 3D object where portions of the object are drawn in by paint and other portions are composed of geometry. The workflow encourages loose shape <boundary-data type="header">
|
| 305 |
+
<confidence value="8">9</confidence>
|
| 306 |
+
</boundary-data>
|
| 307 |
+
<page-break num="10"/>
|
| 308 |
+
<boundary-data type="header">Docket No. 1500.1111</boundary-data>
|
| 309 |
+
exploration by the use of ink and 2D plane placement/orientation within the 3D scene using a drawing on paper analogy. Progressive refinement of the 3D shape from sketch to a more robust 3D NURBS model is allowed. The 2D planes are typically transparent with only the ink, paint, image or 3D geometry opaque. The planes are "2-sided" in that the content can be seen on both sides of the plane. The 2D planes can be non-planar. The construction planes can be used as guides to create geometry (e.g., snapping). The image planes can be used to define local coordinate systems for creating geometry. The basic workflow that this invention supports is the hybrid construction of a 3D shape based on a mixture of painting and 3D geometry specification utilizing whichever medium is easier to express. The 3D sketches can be done in- place, to scale, and the viewer gets a sense of 3D without having to construct geometry. </p>
|
| 310 |
+
<p id="p-73" num="73">[0054<confidence value="5">]</confidence>
|
| 311 |
+
The present invention has been described with respect to the drawing surface being a 2D plane, like a sheet of paper. However, the present invention can be used with other types of canvases, such as non-planer canvases (non-planar surfaces and volumes such as spheres, cubes, cones, etc.). </p>
|
| 312 |
+
<p id="p-74" num="74">[0055] The present invention has been described with respect to the drawing surface being like a piece of paper that the user can draw upon. It is also possible for the surface upon which the user is allowed to draw to be an image, such as a photograph. This image can be loaded into the system as a plane and loaded image plane used a reference for the creation of geometry. This loading can be performed conventionally as part of canvas create which will make a new canvas containing the loaded image, or the image can be loaded as a new layer in an existing canvas.</p>
|
| 313 |
+
<p id="p-75" num="75">[0056] The present invention has been described with a number of different target surface/plane selection techniques. Other techniques can be used. The selection of a target plane involves the concept of "setting" a construction plane, which causes the plane to become a new ground plane. And the application, drawing or geometry creation, always targets the ground plane, which may be "set" to be the plane of a construction plane containing a canvas.</p>
|
| 314 |
+
<p id="p-76" num="76">Any selected plane can also be "locked" so that any operation performed in the locked state operates on that locked plane. The plane setting techniques that are used should support the workflow described herein.</p>
|
| 315 |
+
<p id="p-77" num="77">[0057] The many features and advantages of the invention are apparent from the detailed specification and, thus, it is intended by the appended claims to cover all such features and advantages of the invention that fall within the true spirit and scope of the invention. Further, <boundary-data type="header">
|
| 316 |
+
<confidence value="88">10</confidence>
|
| 317 |
+
</boundary-data>
|
| 318 |
+
<page-break num="11"/>
|
| 319 |
+
<boundary-data type="header">Docket No. 1500.1111</boundary-data>
|
| 320 |
+
since numerous modifications and changes will readily occur to those skilled in the art, it is not desired to limit the invention to the exact construction and operation illustrated and described, and accordingly all suitable modifications and equivalents may be resorted to, falling within the scope of the invention. </p>
|
| 321 |
+
<boundary-data type="header">
|
| 322 |
+
<confidence value="88">11</confidence>
|
| 323 |
+
</boundary-data>
|
| 324 |
+
</description>
|
| 325 |
+
</us-patent-application>
|
| 326 |
+
|
applicant/11265967.xml
ADDED
|
@@ -0,0 +1,425 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11265967</doc-number>
|
| 8 |
+
<date>2005-11-02</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">[10901/113] </p>
|
| 14 |
+
<heading id="h-1">POSITION MEASURING SYSTEM</heading>
|
| 15 |
+
<heading id="h-2">CROSS-REFERENCE TO RELATED APPLICATIONS</heading>
|
| 16 |
+
<p id="p-2" num="2">The present application claims priority to Application No. 10 <part-num-ref name="">2004</part-num-ref>
|
| 17 |
+
<part-num-ref name="">053</part-num-ref>
|
| 18 |
+
082.3, filed in the Federal Republic of Germany on November <part-num-ref name="Federal Republic of Germany on November">3,</part-num-ref>
|
| 19 |
+
<part-num-ref name="Federal Republic of Germany on November 3,">2004,</part-num-ref>
|
| 20 |
+
which is expressly incorporated <boundary-data type="line-number">5 </boundary-data>
|
| 21 |
+
herein in its entirety by reference thereto. </p>
|
| 22 |
+
<heading id="h-3">FIELD OF THE INVENTION</heading>
|
| 23 |
+
<p id="p-3" num="3">The present invention relates to a position measuring system having a laser light source. Such position measuring <boundary-data type="line-number">10 </boundary-data>
|
| 24 |
+
systems may be used to measure the relative position of two objects moving with respect to each other. </p>
|
| 25 |
+
<heading id="h-4">BACKGROUND INFORMATI<confidence value="88">ON</confidence>
|
| 26 |
+
</heading>
|
| 27 |
+
<p id="p-4" num="4">Highly accurate optical position measuring systems have <boundary-data type="line-number">15 </boundary-data>
|
| 28 |
+
become indispensable in many areas of technology. When highest accuracy is concerned, position measuring systems based on optical scanning principles are ahead by a large margin of other, for example, magnetic, capacitive or inductive scanning principles. In applications such as <boundary-data type="line-number">20 </boundary-data>
|
| 29 |
+
photolithography, for example, position measurements in the nanometer range may be required. It has been possible to achieve such accuracies only with the aid of interferometers. </p>
|
| 30 |
+
<p id="p-5" num="5">Position measuring systems based on the scanning of an optical measuring scale may also advance into these regions. Such <boundary-data type="line-number">25 </boundary-data>
|
| 31 |
+
interferential measuring systems have been conventional as three-grating measuring systems. At a splitting grating, light from a light source is split into different orders of diffraction, which are reflected at a measuring scale grating and are cast onto a combination grating, where rays of <boundary-data type="line-number">30 </boundary-data>
|
| 32 |
+
different orders of diffraction are combined with each other and are made to interfere. For this purpose, the splitting <confidence value="6">.</confidence>
|
| 33 |
+
grating and the combination grating may take the form of <boundary-data type="header">
|
| 34 |
+
<confidence value="8856">NY01</confidence>
|
| 35 |
+
1056990 </boundary-data>
|
| 36 |
+
<page-break num="2"/>
|
| 37 |
+
separate gratings (e.g., if the measuring scale is translucent) or as a single grating (e.g., if the measuring scale is reflecting). Even if in the second case only two gratings are physically present, the first, splitting grating <boundary-data type="line-number">5 </boundary-data>
|
| 38 |
+
simultaneously acts as a combination grating. Such a system is therefore also rightfully referred to as a three-grating measuring system. The provision of two or three gratings for a three-grating measuring system has nothing to do with the actual measuring principle and may be decided by the designer <boundary-data type="line-number">10 </boundary-data>
|
| 39 |
+
according to arbitrary criteria such as, for example, restrictions in the ray guidance or in the space available <confidence value="588">.in</confidence>
|
| 40 |
+
the scanning head. </p>
|
| 41 |
+
<p id="p-6" num="6">The different interfering ray bundles are detected by photo detectors and thus position-dependent detector signals <boundary-data type="line-number">15 </boundary-data>
|
| 42 |
+
that are out of phase with respect to each other are output. </p>
|
| 43 |
+
<p id="p-7" num="7">Since the scanning signals of such an interferential measuring system are largely free of harmonic waves, they are very well suited for interpolation. Using a measuring scale graduation in the micrometer range, the frequency multiplication effected <boundary-data type="line-number">20 </boundary-data>
|
| 44 |
+
by the interference of different orders of diffraction and a, e.g., 4096-fold subdivision of the scanning signals, it may be possible to achieve accuracies in the nanometer range. </p>
|
| 45 |
+
<p id="p-8" num="8">Interferential measuring systems may be arranged such that the interfering ray bundles propagate from their <boundary-data type="line-number">25 </boundary-data>
|
| 46 |
+
splitting to their combination through path lengths that are as equal as possible. The interference of the ray bundles thus occurs at a phase difference, which in an ideal case does not depend on the wavelength of the light source. The position value is ascertained from the phase difference such <boundary-data type="line-number">30 </boundary-data>
|
| 47 |
+
that this also does not depend on the wavelength. In practice, however, there may be component, installation and adjustment tolerances, which result in small differences in path length. The output position value thus slightly depends on the wavelength of the light source. For highly accurate <part-num-ref name="light source. For highly accurate">35</part-num-ref>
|
| 48 |
+
measuring systems, which require a measurement of the phase <boundary-data type="header">
|
| 49 |
+
<confidence value="8856">NY01</confidence>
|
| 50 |
+
1056990 2 </boundary-data>
|
| 51 |
+
<page-break num="3"/>
|
| 52 |
+
difference at a very high resolution, a light source having a light wavelength that is as constant as possible may therefore need to be used. </p>
|
| 53 |
+
<p id="p-9" num="9">In addition, a high intensity of the light source may be <boundary-data type="line-number">
|
| 54 |
+
<confidence value="5">5</confidence>
|
| 55 |
+
</boundary-data>
|
| 56 |
+
important in order to be able to generate high signal strengths at minimal noise levels. This is true particularly for measuring devices which have light sources coupled via optical waveguides. </p>
|
| 57 |
+
<p id="p-10" num="10">In the case of measuring devices having longer ray paths, <boundary-data type="line-number">10 </boundary-data>
|
| 58 |
+
the installation-related differences in path length of the interfering ray bundles can reach a magnitude at which the coherence length of the light source becomes significant. </p>
|
| 59 |
+
<p id="p-11" num="11">Only with a sufficient coherence length is it possible in these instances to keep the installation tolerances within <boundary-data type="line-number">15 </boundary-data>
|
| 60 |
+
acceptable limits. </p>
|
| 61 |
+
<p id="p-12" num="12">In the case of interferential position measuring systems of the highest resolution, laser diodes may be provided as light sources. Single-mode laser diodes, which due to their high intensity and great coherence length may actually be well <boundary-data type="line-number">20 </boundary-data>
|
| 62 |
+
suited, may have certain shortcomings for position measuring systems. In certain operating states (depending especially on the operating current and on the temperature of the laser diode), mode jumps may occur which result in a sudden change in the wavelength. In a highly accurate position measuring <boundary-data type="line-number">25 </boundary-data>
|
| 63 |
+
system, however, such a change in the wavelength results in a jumping of the position measurement and frequently also in a miscounting of an incremental counter. </p>
|
| 64 |
+
<p id="p-13" num="13">In order to avoid such problems, U.S. Patent No.</p>
|
| 65 |
+
<p id="p-14" num="14">4,676,645 and U.S. Patent No. 5,000,542 provide for the use of <boundary-data type="line-number">30 </boundary-data>
|
| 66 |
+
multi-mode laser diodes, which have modes that are very close to one another. In this manner, several modes are occupied in every operating state, the occupation of the modes being continuously redistributed with a change of the operating state such that there are no great jumps in the centroid <part-num-ref name="centroid">35</part-num-ref>
|
| 67 |
+
wavelength of the laser diode. Multi-mode laser diodes, <boundary-data type="header">
|
| 68 |
+
<confidence value="8856">NY01</confidence>
|
| 69 |
+
1056990 3 </boundary-data>
|
| 70 |
+
<page-break num="4"/>
|
| 71 |
+
however, are available only for smaller light outputs (< <part-num-ref name="laser diode. Multi-mode laser diodes, however, are available only for smaller light outputs (<">3</part-num-ref>
|
| 72 |
+
to <part-num-ref name="to">5</part-num-ref>
|
| 73 |
+
mW). In principle, laser diodes exhibit a single-mode behavior at higher light outputs. Measuring systems that require a high light output thus may not be equipped with <boundary-data type="line-number">5 </boundary-data>
|
| 74 |
+
multi-mode laser diodes. </p>
|
| 75 |
+
<p id="p-15" num="15">Such multi-mode laser diodes may also be less well suited for applications requiring a great coherence length. Their use rather may require tightly toleranced mechanical and optical components in order to obtain an interference signal <boundary-data type="line-number">10 </boundary-data>
|
| 76 |
+
at all on account of the short coherence length of multi-mode laser diodes. Such position measuring systems may therefore be intricate in their manufacture and thus expensive. </p>
|
| 77 |
+
<p id="p-16" num="16">Japanese Published Patent Application No. 2002-39714 provides for an interferometer to use a single-mode laser <boundary-data type="line-number">15 </boundary-data>
|
| 78 |
+
diode, which is supplied by a variable operating current. A mode-jump control device consistently readjusts (periodically or upon request) the operating current such that the laser diode is operated at an operating point that is as far as possible removed from a mode-jump point. For this purpose, in <boundary-data type="line-number">20 </boundary-data>
|
| 79 |
+
a mechanically fixed measuring system, mode jumps as a function of the operating current are detected by an irreversibly jumping position output signal and the operating current is then selected such that it is centrally between two mode jumps, that is, with the highest possible distance from <boundary-data type="line-number">25 </boundary-data>
|
| 80 |
+
the adjacent mode jumps. The consistently required measurement of the position of the mode jumps and the interruption of the actual measuring operation required for the mode jump detection, however, may be very complex and may not allow for a continuous position measurement. </p>
|
| 81 |
+
<p id="p-17" num="17">
|
| 82 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 83 |
+
German Published Patent Application No. 102 <part-num-ref name="">35</part-num-ref>
|
| 84 |
+
<part-num-ref name="">669</part-num-ref>
|
| 85 |
+
describes a position measuring system having a light source in the form of a single-mode laser light source. In order to overcome the described disadvantages of this laser light source, the use of a feedback device is provided. The laser <part-num-ref name="laser">35</part-num-ref>
|
| 86 |
+
light source and the feedback device interact with each other <boundary-data type="header">
|
| 87 |
+
<confidence value="8856">NY01</confidence>
|
| 88 |
+
1056990 4 </boundary-data>
|
| 89 |
+
<page-break num="5"/>
|
| 90 |
+
such that several closely adjacent modes in the laser light source are activated, thus resulting in a quasi-multi-mode operation of the single-mode laser light source. However, if a laser diode is used as a laser light source, then the <boundary-data type="line-number">5 </boundary-data>
|
| 91 |
+
interaction of the feedback device with the laser diode may result in spontaneous, short-term intensity drops and wavelength fluctuations, which are also referred to as low frequency fluctuations (LLFs) or dropouts. They are equal to mode jumps in their effect and may make an accurate position <boundary-data type="line-number">10 </boundary-data>
|
| 92 |
+
measurement very difficult. </p>
|
| 93 |
+
<heading id="h-5">SUMMARY</heading>
|
| 94 |
+
<p id="p-18" num="18">Example embodiments of the present invention may avoid problems associated with mode jumps of a laser light source in <boundary-data type="line-number">15 </boundary-data>
|
| 95 |
+
a simple manner. </p>
|
| 96 |
+
<p id="p-19" num="19">According to an example embodiment of the present invention, a position measuring system for determining the relative position of two objects includes a power supply unit for generating a variable operating current for a laser light <boundary-data type="line-number">20 </boundary-data>
|
| 97 |
+
source. At least one photodetector generates position- dependent output signals from the light received from the laser light source. In measurement operation, the power supply unit provides a direct current having a superimposed alternating current component to the laser light source. </p>
|
| 98 |
+
<p id="p-20" num="20">
|
| 99 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 100 |
+
In order to avoid problems associated with suddenly occurring wavelength fluctuations on account of mode jumps of a laser diode, mode jumps of high frequency may be obtained by force. This results in the formation of a centroid wavelength of the laser light that is relevant for the position <boundary-data type="line-number">30 </boundary-data>
|
| 101 |
+
measurement, which may change markedly less with the operating current or with the ambient temperature than in the case of a mode jump of a conventionally operated laser diode. </p>
|
| 102 |
+
<p id="p-21" num="21">For the purpose of forcing a mode jump at a high frequency, the direct current for operating the laser diode, <part-num-ref name="laser diode,">35</part-num-ref>
|
| 103 |
+
which due to the great coherence length and the high intensity <boundary-data type="header">
|
| 104 |
+
<confidence value="8856">NY01</confidence>
|
| 105 |
+
1056990 5 </boundary-data>
|
| 106 |
+
<page-break num="6"/>
|
| 107 |
+
may have the form of a single-mode laser diode, may have a superimposed alternating current component of a high frequency. Since a mode jump occurs as a function of the operating current, such a mode jump will occur periodically <boundary-data type="line-number">5 </boundary-data>
|
| 108 |
+
when the direct component of the operating current is so close to a mode jump point that due to the alternating component of the operating current the mode jump point is periodically covered. The closer the direct component of the operating current gets to the mode jump point, the more uniformly will <boundary-data type="line-number">10 </boundary-data>
|
| 109 |
+
both modes be occupied at an average over time. If the frequency bandwidth of the measuring system is smaller than the modulation frequency of the laser diode, then the position signals are determined only by the average over time of the two modes. Thus a slow drift of the operating current or of <boundary-data type="line-number">15 </boundary-data>
|
| 110 |
+
the ambient temperature may no longer cause a sudden change of the wavelength of the laser diode. Instead, a centroid wavelength may form, which may change markedly less quickly with the operating current or the ambient temperature in accordance with the continuous redistribution of the modes <boundary-data type="line-number">20 </boundary-data>
|
| 111 |
+
involved. This may be true particularly if several mode jumps are periodically covered at high frequency by the modulated operating current. </p>
|
| 112 |
+
<p id="p-22" num="22">The coherence length of a single-mode laser diode, which is operated at an alternating current amplitude between <part-num-ref name="alternating current amplitude between">1</part-num-ref>
|
| 113 |
+
and <boundary-data type="line-number">25 </boundary-data>
|
| 114 |
+
<part-num-ref name="and">15</part-num-ref>
|
| 115 |
+
mA, is typically still approximately 100<confidence value="2">p</confidence>
|
| 116 |
+
m to 5mm such that the laser radiation remains capable of interference even in the millimeter range. The requirements of the mechanical adjustment and the tolerances of the mechanical and optical components thus remain within reasonable limits. </p>
|
| 117 |
+
<p id="p-23" num="23">
|
| 118 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 119 |
+
Nevertheless, the reduced coherence length in comparison to conventionally operated single-mode laser diodes may help to reduce undesirable effects such as the co-modulation of stray interference branches or interferences between glass surfaces (at optical waveguide couplings, lenses, prisms, etc.)<confidence value="5">.</confidence>
|
| 120 |
+
</p>
|
| 121 |
+
<boundary-data type="header">
|
| 122 |
+
<confidence value="8856">NY01</confidence>
|
| 123 |
+
1056990 6 </boundary-data>
|
| 124 |
+
<p id="p-24" num="24">
|
| 125 |
+
<page-break num="7"/>
|
| 126 |
+
The HF modulation of the laser diode current may additionally reduce the feedback sensitivity of a laser diode. </p>
|
| 127 |
+
<p id="p-25" num="25">This may be significant, particularly when the light of the laser diode must be brought to the position measuring system <boundary-data type="line-number">5 </boundary-data>
|
| 128 |
+
via an optical waveguide, for example, because no heat input is allowed at the location of the position measurement. In such an instance, the feedbacks of the optical waveguide connection may result in so-called low frequency fluctuations (LFFs), which as spontaneous, short-term losses of the light <boundary-data type="line-number">10 </boundary-data>
|
| 129 |
+
output of the laser diode may make an accurate position measurement impossible. Such LFFs are also partially suppressed by the high-frequency modulation of the laser diode current, but are also shifted into a frequency range outside of the bandwidth of the position measuring system and thus may <boundary-data type="line-number">15 </boundary-data>
|
| 130 |
+
no longer influence the measurement. </p>
|
| 131 |
+
<p id="p-26" num="26">The HF modulation of the laser diode current may be particularly significant also in combination with a position measuring system, such as that described in German Published Patent Application No. <part-num-ref name="position measuring system, such as that described in German Published Patent Application No.">102</part-num-ref>
|
| 132 |
+
<part-num-ref name="">35</part-num-ref>
|
| 133 |
+
<part-num-ref name="">669,</part-num-ref>
|
| 134 |
+
mentioned above. The LFFs <boundary-data type="line-number">20 </boundary-data>
|
| 135 |
+
generated there by the feedback device are suppressed or shifted and may no longer interfere with the position measurement. </p>
|
| 136 |
+
<p id="p-27" num="27">To prevent beats between the scanning frequency of the photodetectors and the high-frequency modulation of the laser <boundary-data type="line-number">25 </boundary-data>
|
| 137 |
+
diode current, the scanning and the modulation in some cases may need to be synchronized so that a scanning of the photodetectors always occurs in the same phase position of the modulator. This may be done, for example, via a common timing pulse generator for both systems (position measuring system <boundary-data type="line-number">30 </boundary-data>
|
| 138 |
+
and modulator)<confidence value="8">.</confidence>
|
| 139 |
+
</p>
|
| 140 |
+
<p id="p-28" num="28">In order to achieve an average over time of the wavelength modulation, the modulation frequency of the alternating current component may need to be higher than the bandwidth of the sequential electronics for evaluating the <part-num-ref name="">35</part-num-ref>
|
| 141 |
+
shift-dependent output signals and also higher than the <boundary-data type="header">
|
| 142 |
+
<confidence value="8856">NY01</confidence>
|
| 143 |
+
1056990 7 </boundary-data>
|
| 144 |
+
<page-break num="8"/>
|
| 145 |
+
frequency of the output control of the laser diode (e.g., a control via a monitor photodiode)<confidence value="5">.</confidence>
|
| 146 |
+
</p>
|
| 147 |
+
<p id="p-29" num="29">Additional filters in the sequential electronics may suppress the residual modulation of the signals of the <boundary-data type="line-number">5 </boundary-data>
|
| 148 |
+
photodetectors. For this purpose, low-pass filters may be suitable, for example, but also higher-order filters. If the modulation frequency is sufficiently high above the bandwidth or the frequency limit of the sequential electronics of the position measuring system, then additional filters may be <boundary-data type="line-number">
|
| 149 |
+
<confidence value="88">10</confidence>
|
| 150 |
+
</boundary-data>
|
| 151 |
+
omitted. </p>
|
| 152 |
+
<p id="p-30" num="30">The form of the alternating current component may be, e.g., square, sinusoidal, etc. Using a triangular characteristic, it may be possible to achieve a more continuous centroid wavelength shift since the individual <boundary-data type="line-number">15 </boundary-data>
|
| 153 |
+
modes are weighted in a more uniform manner. </p>
|
| 154 |
+
<p id="p-31" num="31">Single-mode laser diodes, for which the HF modulation may be particularly suitable, may be constructed as index- commutated laser diodes, while multi-mode laser diodes may be amplification-commutated laser diodes. Even amplification- <boundary-data type="line-number">20 </boundary-data>
|
| 155 |
+
commutated laser diodes, however, may exhibit single-mode behavior starting at an output power of approximately 3mW. </p>
|
| 156 |
+
<p id="p-32" num="32">The use of the HF modulation of the operating current may also be a very promising possibility when using VCSEL diodes since with this diode type wavelength jumps occur as well.</p>
|
| 157 |
+
<p id="p-33" num="33">
|
| 158 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 159 |
+
Although in VCSEL diodes due to the short resonator length only one single longitudinal mode may build up, wavelength jumps may occur nevertheless. In the case of VCSEL diodes, it is the transversal mode and/or the polarization direction that may change abruptly and that may also entail a corresponding <boundary-data type="line-number">30 </boundary-data>
|
| 160 |
+
wavelength change. In order to force a soft transition in this instance as well, the modulation of the diode current may be used. </p>
|
| 161 |
+
<p id="p-34" num="34">The modulation of the light source current may also be used for detecting the difference in path length of the <part-num-ref name="">35</part-num-ref>
|
| 162 |
+
interfering light ray bundles. Such a detection may provide <boundary-data type="header">
|
| 163 |
+
<confidence value="8856">NY01</confidence>
|
| 164 |
+
1056990 <confidence value="5">8</confidence>
|
| 165 |
+
</boundary-data>
|
| 166 |
+
<page-break num="9"/>
|
| 167 |
+
information regarding component, mounting and adjusting tolerances and may be used for correcting them. The difference in path length is detected with the aid of the photodetectors of the measuring system, the currents of which, <boundary-data type="line-number">5 </boundary-data>
|
| 168 |
+
however, are supplied to amplifiers that may amplify the high- frequency modulation by the light source, the bandwidth of which thus is above the modulation frequency of the diode current. The phase or position evaluation of the amplified photocell signals that may conventionally be in position <boundary-data type="line-number">10 </boundary-data>
|
| 169 |
+
measuring systems yields phase or position values that oscillate back and forth synchronous with the modulation frequency. The amplitude of this high-frequency modulation represents a direct measure for the path length difference of the interfering ray bundles. This amplitude and thus the path <boundary-data type="line-number">15 </boundary-data>
|
| 170 |
+
length difference may then be brought to zero by corrective measures on component, adjusting and/or installation tolerances. </p>
|
| 171 |
+
<p id="p-35" num="35">The amplifiers used for detecting the high-frequency modulation may be integrated into a separate test instrument <boundary-data type="line-number">20 </boundary-data>
|
| 172 |
+
for the position measuring system. Alternatively, amplifiers having an appropriately high bandwidth may also be used in the measuring device itself, a low-pass filter connected in the outgoing circuit of the amplifiers suppressing the modulation of the currents of the photocells in the normal measuring <boundary-data type="line-number">25 </boundary-data>
|
| 173 |
+
mode. In the detection mode, the low-pass filters are deactivated. </p>
|
| 174 |
+
<p id="p-36" num="36">A parallel processing of the modulated signals branched off in front of the low-pass and the non-modulated signals branched off behind the low-pass may also be used for <boundary-data type="line-number">30 </boundary-data>
|
| 175 |
+
controlling a single-mode laser diode. While the non- modulated signals are supplied to the usual phase or position evaluation, the modulated signals may be evaluated in a detection circuit. The latter determines the signal amplitudes oscillating at the modulation frequency of the <part-num-ref name="">35</part-num-ref>
|
| 176 |
+
light source. These rise when the laser diode is operated <boundary-data type="header">
|
| 177 |
+
<confidence value="8856">NY01</confidence>
|
| 178 |
+
1056990 9 </boundary-data>
|
| 179 |
+
<page-break num="10"/>
|
| 180 |
+
near a mode jump. Using conventional control engineering, this detection signal may be used for controlling the direct component of the laser diode current such that the laser diode may always be operated in the range that is free of mode <boundary-data type="line-number">5 </boundary-data>
|
| 181 |
+
jumps. </p>
|
| 182 |
+
<p id="p-37" num="37">According to an example embodiment of the present invention, a position measurement system for determining a relative position of two objects includes: a power supply unit adapted to generate a variable operating current for a laser <boundary-data type="line-number">10 </boundary-data>
|
| 183 |
+
light source, the power supply unit adapted to supply to the laser light source, in measurement operations, a direct current having a superimposed alternating current component; </p>
|
| 184 |
+
<p id="p-38" num="38">and at least one photodetector adapted to generate position- dependent output signals from light received from the laser <boundary-data type="line-number">15 </boundary-data>
|
| 185 |
+
light source. </p>
|
| 186 |
+
<p id="p-39" num="39">The laser light source may include a single-mode laser diode.</p>
|
| 187 |
+
<p id="p-40" num="40">The power supply unit may include a laser diode drive and an HF modulator.</p>
|
| 188 |
+
<p id="p-41" num="41">
|
| 189 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 190 |
+
A frequency of the alternating current component may be between <part-num-ref name="alternating current component may be between">1</part-num-ref>
|
| 191 |
+
MHz and 1,000 MHz. </p>
|
| 192 |
+
<p id="p-42" num="42">An amplitude of the alternating current component may be greater than 10% of the direct current having the superimposed alternating current component.</p>
|
| 193 |
+
<p id="p-43" num="43">
|
| 194 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 195 |
+
A frequency of the alternating current component may greater than a bandwidth of sequential electronics for generating a position signal from the position-dependent output signals. </p>
|
| 196 |
+
<p id="p-44" num="44">The position measurement system may include sequential <boundary-data type="line-number">30 </boundary-data>
|
| 197 |
+
electronics adapted to generate a position signal from the position-dependent output signals, and a frequency of the alternating current component may be greater than a bandwidth of the sequential electronics. </p>
|
| 198 |
+
<boundary-data type="header">
|
| 199 |
+
<confidence value="8856">NY01</confidence>
|
| 200 |
+
1056990 <confidence value="68">10</confidence>
|
| 201 |
+
</boundary-data>
|
| 202 |
+
<p id="p-45" num="45">
|
| 203 |
+
<page-break num="11"/>
|
| 204 |
+
The single-mode laser diode may be connected t<confidence value="5">o</confidence>
|
| 205 |
+
<confidence value="8">a</confidence>
|
| 206 |
+
feedback device adapted to force the single-mode laser diode into a multi-mode operation. </p>
|
| 207 |
+
<p id="p-46" num="46">The position measurement system may include a feedback <boundary-data type="line-number">5 </boundary-data>
|
| 208 |
+
device connected to the single-mode laser diode, and the feedback device may be adapted to force the single-mode laser diode into a multi-mode operation. </p>
|
| 209 |
+
<p id="p-47" num="47">The feedback device may include an optical waveguide, and a length of the optical waveguide may form an external <boundary-data type="line-number">10 </boundary-data>
|
| 210 |
+
resonator to activate a plurality of laser modes in the single-mode laser diode. </p>
|
| 211 |
+
<p id="p-48" num="48">The at least one photodetector may be adapted to generate position-dependent output signals from light that is fed by optical waveguides to the at least one photodetector.</p>
|
| 212 |
+
<p id="p-49" num="49">
|
| 213 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 214 |
+
An HF modulator of the power supply unit and the sequential electronics may be mutually synchronized. </p>
|
| 215 |
+
<p id="p-50" num="50">According to an example embodiment of the present invention, a position measurement system for determining a relative position of two objects include: a laser light <boundary-data type="line-number">20 </boundary-data>
|
| 216 |
+
source; a power supply unit adapted to generate a variable operating current for the laser light source, the power supply unit adapted to supply to the laser light source, in measurement operations, a direct current having a superimposed alternating current component; and at least one photodetector <boundary-data type="line-number">25 </boundary-data>
|
| 217 |
+
adapted to generate position-dependent output signals from light received from the laser light source. </p>
|
| 218 |
+
<p id="p-51" num="51">According to an example embodiment of the present invention, a position measurement system for determining a relative position of two objects includes: power supply means <boundary-data type="line-number">30 </boundary-data>
|
| 219 |
+
for generating a variable operating current for a laser light source, the power supply unit for supplying to the laser light source, in measurement operations, a direct current having a superimposed alternating current component; and at least one photodetecting means for generating position-dependent output <part-num-ref name="superimposed alternating current component; and at least one photodetecting means for generating position-dependent output">35</part-num-ref>
|
| 220 |
+
signals from light received from the laser light source. </p>
|
| 221 |
+
<boundary-data type="header">
|
| 222 |
+
<confidence value="8856">NY01</confidence>
|
| 223 |
+
1056990 11 </boundary-data>
|
| 224 |
+
<p id="p-52" num="52">
|
| 225 |
+
<page-break num="12"/>
|
| 226 |
+
According to an example embodiment of the present invention, a method for compensating for a difference in path length of interfering light ray bundles in a position measurement system that includes a power supply unit adapted <boundary-data type="line-number">5 </boundary-data>
|
| 227 |
+
to generate a variable operating current for a laser light source, the power supply unit adapted to supply to the laser light source, in measurement operations, a direct current having a superimposed alternating current component, and at least one photodetector adapted to generate position-dependent <boundary-data type="line-number">10 </boundary-data>
|
| 228 |
+
output signals from light received from the laser light source, includes: feeding the position-dependent output signals of the at least one photodetector to an amplifier having a bandwidth that is above a frequency of the alternating current component. </p>
|
| 229 |
+
<p id="p-53" num="53">
|
| 230 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 231 |
+
The method may include determining the difference in path length in accordance with an amplitude of a high-frequency phase modulation derived from the position-dependent output signals of the at least one photodetector. </p>
|
| 232 |
+
<p id="p-54" num="54">The method may include minimizing an amplitude of a high- <boundary-data type="line-number">20 </boundary-data>
|
| 233 |
+
frequency modulation derived from the position-dependent output signals of the at least one photodetector and the difference in path length of the interfering light ray bundles by mechanically adjusting the position measurement system. </p>
|
| 234 |
+
<p id="p-55" num="55">Further aspects and details of example embodiments of the <boundary-data type="line-number">25 </boundary-data>
|
| 235 |
+
present invention are described below with reference to the appended Figures. </p>
|
| 236 |
+
<heading id="h-6">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 237 |
+
<p id="p-56" num="56">Figure 1 illustrates a position measuring system <boundary-data type="line-number">30 </boundary-data>
|
| 238 |
+
according to an example embodiment of the present invention. </p>
|
| 239 |
+
<p id="p-57" num="57">Figure 2a to 2c illustrate mode jumps as a function of the operating current.</p>
|
| 240 |
+
<p id="p-58" num="58">Figure 3a to 3c illustrate mode jumps as a function of the operating temperature.</p>
|
| 241 |
+
<p id="p-59" num="59">
|
| 242 |
+
<confidence value="88">35</confidence>
|
| 243 |
+
<boundary-data type="header">
|
| 244 |
+
<confidence value="8856">NY01</confidence>
|
| 245 |
+
1056990 12 </boundary-data>
|
| 246 |
+
<page-break num="13"/>
|
| 247 |
+
</p>
|
| 248 |
+
<heading id="h-7">DETAILED DESCRIPTION</heading>
|
| 249 |
+
<p id="p-60" num="60">Figure 1 illustrates an example embodiment of the present invention. Using a laser diode driver <part-num-ref name="laser diode driver">1,</part-num-ref>
|
| 250 |
+
the direct component of the operating current is generated for a single-mode laser <boundary-data type="line-number">5 </boundary-data>
|
| 251 |
+
diode <part-num-ref name="single-mode laser diode">3,</part-num-ref>
|
| 252 |
+
which is additionally modulated in an HF modulator <part-num-ref name="HF modulator">2.</part-num-ref>
|
| 253 |
+
</p>
|
| 254 |
+
<p id="p-61" num="61">Laser diode driver 1 and modulator <part-num-ref name="and modulator">2</part-num-ref>
|
| 255 |
+
together form a power supply unit for laser diode <part-num-ref name="power supply unit for laser diode">3.</part-num-ref>
|
| 256 |
+
Modulation frequencies between <part-num-ref name="power supply unit for laser diode 3. Modulation frequencies between">1</part-num-ref>
|
| 257 |
+
and <part-num-ref name="and">1000</part-num-ref>
|
| 258 |
+
MHz, e.g., in the range of some <part-num-ref name="range of some">100</part-num-ref>
|
| 259 |
+
MHz, are used. </p>
|
| 260 |
+
<p id="p-62" num="62">A frequency range of 250 to <part-num-ref name="to">300</part-num-ref>
|
| 261 |
+
MHz may be particularly <boundary-data type="line-number">10 </boundary-data>
|
| 262 |
+
suitable. The amplitude of the modulation may be chosen such that the minimum operating current, which is also referred to as the threshold current and which is required to drive laser diode <part-num-ref name="threshold current and which is required to drive laser diode">3,</part-num-ref>
|
| 263 |
+
is not undershot. A short-term undershooting of the minimum operating current, however, may be provided since this <boundary-data type="line-number">15 </boundary-data>
|
| 264 |
+
may cause a particularly strong excitation of laser diode <part-num-ref name="particularly strong excitation of laser diode">3,</part-num-ref>
|
| 265 |
+
which may result in the oscillation build-up of additional modes. The modulation should not exceed the maximum operating current of laser diode <part-num-ref name="maximum operating current of laser diode">3</part-num-ref>
|
| 266 |
+
or should do so only briefly. </p>
|
| 267 |
+
<p id="p-63" num="63">For a laser diode <part-num-ref name="laser diode">3</part-num-ref>
|
| 268 |
+
having a minimum operating current of <boundary-data type="line-number">20 </boundary-data>
|
| 269 |
+
3<confidence value="5">0</confidence>
|
| 270 |
+
mA and a maximum operating current of 7<confidence value="5">0</confidence>
|
| 271 |
+
mA, for example, an amplitude of <confidence value="55">lO</confidence>
|
| 272 |
+
mA may be provided if laser diode <part-num-ref name="amplitude of lOmA may be provided if laser diode">3</part-num-ref>
|
| 273 |
+
is operated at a direct component of the operating current of 5<confidence value="5">0</confidence>
|
| 274 |
+
mA. The minimum and maximum operating current of laser diode <part-num-ref name="minimum and maximum operating current of laser diode">3</part-num-ref>
|
| 275 |
+
defines its operating range. The amplitude of the alternating current <boundary-data type="line-number">25 </boundary-data>
|
| 276 |
+
component may amount to more than 10<confidence value="5">%</confidence>
|
| 277 |
+
of the direct current having the superimposed alternating current. In the mentioned example, the modulation ranges between <part-num-ref name="modulation ranges between">40</part-num-ref>
|
| 278 |
+
and 6<confidence value="5">0</confidence>
|
| 279 |
+
mA such that about half of the operating range of laser diode <part-num-ref name="operating range of laser diode">3</part-num-ref>
|
| 280 |
+
is covered. </p>
|
| 281 |
+
<p id="p-64" num="64">Thus many modes are simultaneously activated, and the change <boundary-data type="line-number">30 </boundary-data>
|
| 282 |
+
of the centroid wavelength with the operating current or with the temperature may turn out to be particularly small. </p>
|
| 283 |
+
<p id="p-65" num="65">The light of laser diode 3 is coupled by a focusing lens 4.1 into an optical waveguide 5.1, which brings the light to the actual measuring point. The use of an optical waveguide <part-num-ref name="optical waveguide">35</part-num-ref>
|
| 284 |
+
5.1 may make it possible to avoid an input of heat at the <boundary-data type="header">
|
| 285 |
+
<confidence value="8856">NY01</confidence>
|
| 286 |
+
1056990 13 </boundary-data>
|
| 287 |
+
<page-break num="14"/>
|
| 288 |
+
measuring point in especially temperature-critical applications. The optical waveguide may be interrupted by one or several fiber couplers <part-num-ref name="optical waveguide may be interrupted by one or several fiber couplers">6.</part-num-ref>
|
| 289 |
+
Both the coupling of the laser light into optical waveguide 5.1 as well as into the fiber <boundary-data type="line-number">5 </boundary-data>
|
| 290 |
+
couplers <part-num-ref name="fiber couplers">6</part-num-ref>
|
| 291 |
+
may cause reflections, which may trigger the LFFs described further above. Nevertheless, these reflections may actually be desirable and used deliberately. As described in German Published Patent Application No. <part-num-ref name="LFFs described further above. Nevertheless, these reflections may actually be desirable and used deliberately. As described in German Published Patent Application No.">102</part-num-ref>
|
| 292 |
+
<part-num-ref name="">35</part-num-ref>
|
| 293 |
+
<part-num-ref name="">669,</part-num-ref>
|
| 294 |
+
optical waveguide 5.1 may be arranged such that as a feedback device <boundary-data type="line-number">10 </boundary-data>
|
| 295 |
+
it interacts with single-mode laser diode <part-num-ref name="feedback device it interacts with single-mode laser diode">3</part-num-ref>
|
| 296 |
+
such that single- mode laser diode <part-num-ref name="such that single- mode laser diode">3</part-num-ref>
|
| 297 |
+
is forced into multi-mode operation. For this purpose, the length of optical waveguide 5.1 is chosen such that it forms an external resonator for single-mode laser diode <part-num-ref name="external resonator for single-mode laser diode">3.</part-num-ref>
|
| 298 |
+
In the process, the end of optical waveguide 5.1 <boundary-data type="line-number">15 </boundary-data>
|
| 299 |
+
facing away from laser diode <part-num-ref name="end of optical waveguide 5.1 facing away from laser diode">3</part-num-ref>
|
| 300 |
+
reflects a portion of the laser radiation back into laser diode <part-num-ref name="laser radiation back into laser diode">3.</part-num-ref>
|
| 301 |
+
The combination of such feedback device 5.1 with the HF modulation of the operating current of single-mode laser diode <part-num-ref name="operating current of single-mode laser diode">3</part-num-ref>
|
| 302 |
+
by modulator <part-num-ref name="by modulator">2</part-num-ref>
|
| 303 |
+
may be particularly suitable. For the problems with mode jumps of <boundary-data type="line-number">20 </boundary-data>
|
| 304 |
+
single-mode laser diode <part-num-ref name="problems with mode jumps of single-mode laser diode">3</part-num-ref>
|
| 305 |
+
are thus already reduced by the forced multi-mode operation. The problems with LFFs produced by feedback device 5.1 may be overcome by the HF modulation of the operating current. </p>
|
| 306 |
+
<p id="p-66" num="66">The light exits optical waveguide 5.1 and strikes a <boundary-data type="line-number">25 </boundary-data>
|
| 307 |
+
reflecting measuring scale <part-num-ref name="reflecting measuring scale">
|
| 308 |
+
<confidence value="5">8</confidence>
|
| 309 |
+
</part-num-ref>
|
| 310 |
+
via a collimator lens <part-num-ref name="collimator lens">7.</part-num-ref>
|
| 311 |
+
There, the light is split into two light ray bundles +1, -1 (+<confidence value="5">1</confidence>
|
| 312 |
+
st and -1st order), which form two symmetrical measuring branches. </p>
|
| 313 |
+
<p id="p-67" num="67">Each light ray bundle +1, -1 strikes through a scanning grating <part-num-ref name="scanning grating">9,</part-num-ref>
|
| 314 |
+
is again guided onto scanning grating <part-num-ref name="scanning grating 9, is again guided onto scanning grating">9</part-num-ref>
|
| 315 |
+
by a <boundary-data type="line-number">30 </boundary-data>
|
| 316 |
+
reflecting prism via an <confidence value="1">A</confidence>
|
| 317 |
+
/4 phase shifter 10.1, 10.2 and from there is again diffracted to measuring scale <part-num-ref name="A/4 phase shifter 10.1, 10.2 and from there is again diffracted to measuring scale">8.</part-num-ref>
|
| 318 |
+
There, the two light ray bundles +<confidence value="5">1</confidence>
|
| 319 |
+
, -1 are united into one light ray so as then to be split by a splitting grating <part-num-ref name="splitting grating">11</part-num-ref>
|
| 320 |
+
into three separate light rays, which strike through three differently <part-num-ref name="into three separate light rays, which strike through three differently">35</part-num-ref>
|
| 321 |
+
oriented pole filters 12.1, 12.2, 12.3. Focusing lenses 4.2, <boundary-data type="header">
|
| 322 |
+
<confidence value="8856">NY01</confidence>
|
| 323 |
+
1056990 <confidence value="88">14</confidence>
|
| 324 |
+
</boundary-data>
|
| 325 |
+
<page-break num="15"/>
|
| 326 |
+
4.3, 4.4 couple the three light rays into optical wave guides 5.2, 5.3, 5.4, which guide the light rays to photo detectors 13.1, 13.2, 13.3. Photodetectors 13.1, 13.2, 13.3 generate three position-dependent signals <confidence value="58882">-120*</confidence>
|
| 327 |
+
, <part-num-ref name="light rays to photo detectors 13.1, 13.2, 13.3. Photodetectors 13.1, 13.2, 13.3 generate three position-dependent signals -120*,">0<confidence value="2">0</confidence>
|
| 328 |
+
, </part-num-ref>
|
| 329 |
+
+120<confidence value="2">4</confidence>
|
| 330 |
+
, each <boundary-data type="line-number">5 </boundary-data>
|
| 331 |
+
displaced in phase by <part-num-ref name="light rays to photo detectors 13.1, 13.2, 13.3. Photodetectors 13.1, 13.2, 13.3 generate three position-dependent signals -120*, 00, +1204, each displaced in phase by">120</part-num-ref>
|
| 332 |
+
degrees, which may be processed by sequential electronics <part-num-ref name="degrees, which may be processed by sequential electronics">14</part-num-ref>
|
| 333 |
+
into a position value P. The modulation of the operating current of laser diode <part-num-ref name="operating current of laser diode">3</part-num-ref>
|
| 334 |
+
may occur in measuring operations, that is, during the detection of phase-displaced signals <confidence value="5">-</confidence>
|
| 335 |
+
120<confidence value="2">°</confidence>
|
| 336 |
+
, 0<confidence value="2">*</confidence>
|
| 337 |
+
, +<confidence value="5882">120*</confidence>
|
| 338 |
+
of photodetectors <boundary-data type="line-number">10 </boundary-data>
|
| 339 |
+
13.1, 13.2, 13.3. Only this may ensure that the negative influence of mode jumps and/or LFFs is suppressed. </p>
|
| 340 |
+
<p id="p-68" num="68">Sequential electronics 14 includes an amplifier circuit <part-num-ref name="amplifier circuit">15</part-num-ref>
|
| 341 |
+
for amplifying phase-displaced signals <confidence value="66884">-1200</confidence>
|
| 342 |
+
, <part-num-ref name="for amplifying phase-displaced signals -1200,">0<confidence value="2">0</confidence>
|
| 343 |
+
, </part-num-ref>
|
| 344 |
+
+120<confidence value="2">*</confidence>
|
| 345 |
+
of photodetectors 13.1, 13.2, 13.3. An evaluation circuit <part-num-ref name="evaluation circuit">17</part-num-ref>
|
| 346 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 347 |
+
forms a position value P from phase-displaced signals -120<confidence value="28">°,</confidence>
|
| 348 |
+
<part-num-ref name="position value P from phase-displaced signals -120°,">
|
| 349 |
+
<confidence value="5">0</confidence>
|
| 350 |
+
</part-num-ref>
|
| 351 |
+
+120<confidence value="2">*</confidence>
|
| 352 |
+
, and outputs this value. An optional filter <part-num-ref name="optional filter">16</part-num-ref>
|
| 353 |
+
may ensure that possible high-frequency residual modulations of phase-displaced signals -120, <part-num-ref name="may ensure that possible high-frequency residual modulations of phase-displaced signals -120,">0<confidence value="2">0</confidence>
|
| 354 |
+
, </part-num-ref>
|
| 355 |
+
+120 do not influence the ascertainment of the position value. </p>
|
| 356 |
+
<p id="p-69" num="69">
|
| 357 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 358 |
+
Photodetectors 13.1, 13.2, 13.3 are scanned in sequential electronics 14 at a certain scanning frequency in order to provide phase-displaced signals -<confidence value="5882">120*</confidence>
|
| 359 |
+
, 0<confidence value="2">*</confidence>
|
| 360 |
+
, +120<confidence value="2">°</confidence>
|
| 361 |
+
for further processing. As already mentioned, to avoid beats, it may be necessary to synchronize modulator <part-num-ref name="certain scanning frequency in order to provide phase-displaced signals -120*, 0*, +120° for further processing. As already mentioned, to avoid beats, it may be necessary to synchronize modulator">2</part-num-ref>
|
| 362 |
+
with the scanning of <boundary-data type="line-number">25 </boundary-data>
|
| 363 |
+
photodetectors 13.1, 13.2, 13.3. This is indicated in Figure 1 by the dashed connection between modulator <part-num-ref name="dashed connection between modulator">2</part-num-ref>
|
| 364 |
+
and sequential electronics <part-num-ref name="and sequential electronics">14.</part-num-ref>
|
| 365 |
+
</p>
|
| 366 |
+
<p id="p-70" num="70">In the exemplary embodiment illustrated in Figure 1, sequential electronics <part-num-ref name="exemplary embodiment illustrated in Figure 1, sequential electronics">14</part-num-ref>
|
| 367 |
+
also outputs the amplitude<confidence value="4">-</confidence>
|
| 368 |
+
A of the <boundary-data type="line-number">30 </boundary-data>
|
| 369 |
+
high-frequency (frequency of modulator <part-num-ref name="high-frequency (frequency of modulator">2)</part-num-ref>
|
| 370 |
+
phase modulation of phase-displaced signals <confidence value="66882">-120*</confidence>
|
| 371 |
+
, <part-num-ref name="phase modulation of phase-displaced signals -120*,">0<confidence value="2">4</confidence>
|
| 372 |
+
, </part-num-ref>
|
| 373 |
+
+120<confidence value="2">4</confidence>
|
| 374 |
+
. Since this amplitude A is a measure for the path length difference of the interfering light ray bundles +1, -1, a compensation of the path length difference may be made with the aid of this <part-num-ref name="aid of this">35</part-num-ref>
|
| 375 |
+
amplitude A. The optical elements in the ray path may be <boundary-data type="header">
|
| 376 |
+
<confidence value="8856">NY01</confidence>
|
| 377 |
+
1056990 15 </boundary-data>
|
| 378 |
+
<page-break num="16"/>
|
| 379 |
+
mechanically adjusted such that amplitude A disappears or falls below a specified threshold value. </p>
|
| 380 |
+
<p id="p-71" num="71">So as to be able to determine amplitude A in the evaluation circuit, position-dependent signals <confidence value="66882">-120*</confidence>
|
| 381 |
+
, <part-num-ref name="evaluation circuit, position-dependent signals -120*,">0<confidence value="28">0,</confidence>
|
| 382 |
+
</part-num-ref>
|
| 383 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 384 |
+
+120<confidence value="2">*</confidence>
|
| 385 |
+
of photodetectors 13.1, 13.2, 13.3 may need to be fed to an amplifier <part-num-ref name="amplifier">15</part-num-ref>
|
| 386 |
+
having a bandwidth above the frequency of the alternating current component. </p>
|
| 387 |
+
<p id="p-72" num="72">To determine position signal P, the amplified signals may then need to be freed by filter <part-num-ref name="amplified signals may then need to be freed by filter">16</part-num-ref>
|
| 388 |
+
of the high-frequency <confidence value="6">-</confidence>
|
| 389 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 390 |
+
modulation at the frequency of modulator <part-num-ref name="frequency of modulator">2.</part-num-ref>
|
| 391 |
+
This filter <part-num-ref name="frequency of modulator 2. This filter">16,</part-num-ref>
|
| 392 |
+
however, does not affect the signals that are used to determine amplitude A. In evaluation electronics <part-num-ref name="In evaluation electronics">14,</part-num-ref>
|
| 393 |
+
the part that determines amplitude A may need to have a sufficient bandwidth above the modulation frequency of laser light source <boundary-data type="line-number">15 </boundary-data>
|
| 394 |
+
<part-num-ref name="modulation frequency of laser light source">3.</part-num-ref>
|
| 395 |
+
</p>
|
| 396 |
+
<p id="p-73" num="73">For further clarification, Figure 2a illustrates the behavior of a single-mode laser diode without HF modulated operating current. With an increasing operating current, the wavelength of the emitted light changes only slowly until a <boundary-data type="line-number">20 </boundary-data>
|
| 397 |
+
mode jump occurs at approximately 45mA. This results in a very distinct jump in the wavelength. If one superimposes onto the operating current an HF component of the frequency <part-num-ref name="frequency">2</part-num-ref>
|
| 398 |
+
MHz and the amplitude 3mA (Figure 2b) or 6mA (Figure 2c), then one sees that the mode jump is expressed in a markedly rounded <boundary-data type="line-number">25 </boundary-data>
|
| 399 |
+
rise of the wavelength. The measurements at the basis of Figures 2a to 2c are conducted at a constant temperature in order to demonstrate a mode jump induced by a varying operating current. </p>
|
| 400 |
+
<p id="p-74" num="74">Figure 3a illustrates mode jumps that occur at a constant <boundary-data type="line-number">30 </boundary-data>
|
| 401 |
+
operating current of the laser diode, but at a variable temperature. Here, there are even several mode jumps in the tested temperature range. Without any modulation of the operating current, the wavelength jumps are very abrupt. </p>
|
| 402 |
+
<p id="p-75" num="75">Figures 3b and 3c are based on a current modulation at 2MHz, <part-num-ref name="current modulation at 2MHz,">35</part-num-ref>
|
| 403 |
+
this time at amplitude <confidence value="66">6m</confidence>
|
| 404 |
+
A (Figure 2b) or <confidence value="5">1</confidence>
|
| 405 |
+
2mA (Figure 2c). </p>
|
| 406 |
+
<boundary-data type="header">
|
| 407 |
+
<confidence value="8856">NY01</confidence>
|
| 408 |
+
1056990 16 </boundary-data>
|
| 409 |
+
<p id="p-76" num="76">
|
| 410 |
+
<page-break num="17"/>
|
| 411 |
+
Again it can be seen that the wavelength jumps are clearly rounded. </p>
|
| 412 |
+
<p id="p-77" num="77">The position measuring system described may have a complex optical system. In combination with this type of <boundary-data type="line-number">
|
| 413 |
+
<confidence value="5">5</confidence>
|
| 414 |
+
</boundary-data>
|
| 415 |
+
complex position measuring systems, the modulation of the operating current indeed may make sense especially in order to be able to perform truly highly accurate measurements without the negative influence of mode jumps and LFFs. The principle of the HF modulation of the operating current, however, may <boundary-data type="line-number">10 </boundary-data>
|
| 416 |
+
also be applied for more simple position measuring systems. </p>
|
| 417 |
+
<p id="p-78" num="78">Thus, for example, a measuring system for measuring the shape of a tool, which is based on the light barrier principle, may also profit from a modulated operating current. For in this instance as well, LFFs may result in the detection of an <boundary-data type="line-number">15 </boundary-data>
|
| 418 |
+
interruption of the light ray even though the laser diode used merely had a power loss. In this manner, it may be possible to measure tools such as cutters, drills, etc., at a very high resolution. </p>
|
| 419 |
+
<boundary-data type="header">
|
| 420 |
+
<confidence value="8856">NY01</confidence>
|
| 421 |
+
1056990 1<confidence value="8">7</confidence>
|
| 422 |
+
</boundary-data>
|
| 423 |
+
</description>
|
| 424 |
+
</us-patent-application>
|
| 425 |
+
|
applicant/11291352.xml
ADDED
|
@@ -0,0 +1,84 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11291352</doc-number>
|
| 8 |
+
<date>2009-04-02</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">U.S. Application No.: 11/291,352 Attorney Docket No.: <confidence value="65">OI</confidence>
|
| 14 |
+
D05-01(01201) </boundary-data>
|
| 15 |
+
<boundary-data type="header">-15-</boundary-data>
|
| 16 |
+
<heading id="h-1">IN THE SPECIFICATION</heading>
|
| 17 |
+
<p id="p-1" num="1">Please enter the following amendment to the Specification:</p>
|
| 18 |
+
<p id="p-2" num="2">Please replace the paragraph at page <part-num-ref name="paragraph at page">13</part-num-ref>
|
| 19 |
+
line <part-num-ref name="line">14</part-num-ref>
|
| 20 |
+
to page <part-num-ref name="to page">14</part-num-ref>
|
| 21 |
+
line <part-num-ref name="line">10</part-num-ref>
|
| 22 |
+
with the following: </p>
|
| 23 |
+
<p id="p-3" num="3">Figure 6 is a block diagram showing further details of an e<confidence value="5118">ampe</confidence>
|
| 24 |
+
exem<confidence value="8">p</confidence>
|
| 25 |
+
lar<confidence value="8">y</confidence>
|
| 26 |
+
software architecture of a collaboration manager <part-num-ref name="collaboration manager">151</part-num-ref>
|
| 27 |
+
operable to maintain metadata providing access to applications <part-num-ref name="operable to maintain metadata providing access to applications">130</part-num-ref>
|
| 28 |
+
on behalf of users <part-num-ref name="on behalf of users">120</part-num-ref>
|
| 29 |
+
logged into the workspace. In this example, the collaboration manager <part-num-ref name="collaboration manager">151</part-num-ref>
|
| 30 |
+
includes a web interface <part-num-ref name="web interface">114,</part-num-ref>
|
| 31 |
+
a workspace server <part-num-ref name="workspace server">136,</part-num-ref>
|
| 32 |
+
and a resource framework <part-num-ref name="resource framework">140</part-num-ref>
|
| 33 |
+
having adaptors 142-1<confidence value="88">..</confidence>
|
| 34 |
+
142-N <part-num-ref name="having adaptors 142-1..142-N">(142</part-num-ref>
|
| 35 |
+
generally) for each application <part-num-ref name="generally) for each application">130</part-num-ref>
|
| 36 |
+
that the server <part-num-ref name="server">110</part-num-ref>
|
| 37 |
+
supports. The workspace server <part-num-ref name="workspace server">136</part-num-ref>
|
| 38 |
+
may include a plurality of workspaces 150-1..150-M, each of which may access any of the applications 130-1 through 130-N via the adaptors <part-num-ref name="adaptors">142</part-num-ref>
|
| 39 |
+
within the resource framework <part-num-ref name="resource framework">140.</part-num-ref>
|
| 40 |
+
The <confidence value="22222222">adaptors</confidence>
|
| 41 |
+
adapter<confidence value="86">s-</confidence>
|
| 42 |
+
142 provide the appropriate API calls and sub-routines or object libraries to allow a workspace <part-num-ref name="workspace">150</part-num-ref>
|
| 43 |
+
to control an application <part-num-ref name="application">130</part-num-ref>
|
| 44 |
+
to perform application related functions such as creation of a workspace user account to operate the application, creation of an application container <part-num-ref name="application container">132</part-num-ref>
|
| 45 |
+
for storage of application data <part-num-ref name="for storage of application data">134</part-num-ref>
|
| 46 |
+
by the application <part-num-ref name="application">130,</part-num-ref>
|
| 47 |
+
and to control general operational features of the application such as transmission<confidence value="188">-of</confidence>
|
| 48 |
+
electronic mail, creation of calendar appointments, and so forth. Depending upon the application, the ada<confidence value="7">p</confidence>
|
| 49 |
+
tors <confidence value="686666655">adapter-1</confidence>
|
| 50 |
+
42 can allow the workspaces <part-num-ref name="workspaces">150</part-num-ref>
|
| 51 |
+
to present a graphical user interface of the applications <part-num-ref name="applications">130</part-num-ref>
|
| 52 |
+
(some or all) to a user <part-num-ref name="user">120</part-num-ref>
|
| 53 |
+
of the workspace <part-num-ref name="workspace">150</part-num-ref>
|
| 54 |
+
as if that user were independently operating the application in standalone mode<confidence value="5">.</confidence>
|
| 55 |
+
(i.e., as if the user had accessed the application outside of the workspace), but under the auspices of the workspace user account created when the application was included in the workspace (i.e. at workspace creation time). Alternatively, the ada<confidence value="8">p</confidence>
|
| 56 |
+
tor adapte<confidence value="665">r-1</confidence>
|
| 57 |
+
42 can simply relay data from the application <part-num-ref name="application">130</part-num-ref>
|
| 58 |
+
to the workspace <part-num-ref name="workspace">150</part-num-ref>
|
| 59 |
+
and the workspace can provide its own graphical user interface or client for representation of that data to the users <part-num-ref name="users">120.</part-num-ref>
|
| 60 |
+
</p>
|
| 61 |
+
<p id="p-4" num="4">In such a case, the application <part-num-ref name="application">130</part-num-ref>
|
| 62 |
+
can be used for its back-end (i.e. non- <page-break num="2"/>
|
| 63 |
+
<boundary-data type="header">U.S. Application No.: 11/291,352 Attorney Docket No.: <confidence value="656">OID</confidence>
|
| 64 |
+
05-01(01201) </boundary-data>
|
| 65 |
+
<boundary-data type="header">-16-</boundary-data>
|
| 66 |
+
graphical) processing capabilities and the presentation of the application data <part-num-ref name="application data">134</part-num-ref>
|
| 67 |
+
to the user <part-num-ref name="user">120</part-num-ref>
|
| 68 |
+
is left up to the workspace <part-num-ref name="workspace">150.</part-num-ref>
|
| 69 |
+
In either configuration, the applications <part-num-ref name="applications">130</part-num-ref>
|
| 70 |
+
can be replaced with different versions of software <confidence value="414568888888">form-fromthe</confidence>
|
| 71 |
+
same or from different vendors, and only the ada<confidence value="8">p</confidence>
|
| 72 |
+
tor adapter-may (or may not) need to be changed to accommodate the new version of the application. </p>
|
| 73 |
+
<p id="p-5" num="5">Please replace the paragraph at page <part-num-ref name="paragraph at page">23</part-num-ref>
|
| 74 |
+
lines 1-16 with the following: </p>
|
| 75 |
+
<p id="p-6" num="6">Those skilled in the art should readily appreciate that the programs and methods that provide a workspace for use in a collaboration environment as defined herein are deliverable to a processing device or as a processing device in many forms, including but not limited to a) information permanently stored on <confidence value="88566286">tangibe-</confidence>
|
| 76 |
+
non-writeable storage media such as ROM devices, or b) information alterably stored on ta<confidence value="28614">ngike</confidence>
|
| 77 |
+
-writeable storage media <confidence value="2222222">such'as</confidence>
|
| 78 |
+
floppy disks, magnetic tapes, <confidence value="5">C</confidence>
|
| 79 |
+
Ds, RAM devices, and other magnetic and optical media. The operations and methods may be implemented in a software executable object. </p>
|
| 80 |
+
<p id="p-7" num="7">Alternatively, the operations and methods disclosed herein may be embodied in whole or in part using hardware components, such as Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), state machines, controllers or other hardware components or devices, or a combination of hardware, software, and firmware components. The data such as metadata <part-num-ref name="data such as metadata">125</part-num-ref>
|
| 81 |
+
may be stored in a database of any type. </p>
|
| 82 |
+
</description>
|
| 83 |
+
</us-patent-application>
|
| 84 |
+
|
applicant/11333495.xml
ADDED
|
@@ -0,0 +1,111 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11333495</doc-number>
|
| 8 |
+
<date>2008-10-08</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">Application No. 11/333,495</boundary-data>
|
| 14 |
+
<boundary-data type="header">Reply to Office Action of July 09, 2008</boundary-data>
|
| 15 |
+
<heading id="h-1">AMENDMENTS TO THE SPECIFICATION</heading>
|
| 16 |
+
<p id="p-1" num="1">At Paragraph [0002] Please amend paragraph [0002] of the specification as follows:</p>
|
| 17 |
+
<p id="p-2" num="2">[0002] This application also makes reference to:</p>
|
| 18 |
+
<p id="p-3" num="3">United States Application Serial No. [[ <confidence value="668">1]1</confidence>
|
| 19 |
+
1/335,800 <confidence value="666668566424524">(AttorneyDeoket</confidence>
|
| 20 |
+
<confidence value="682">No.</confidence>
|
| 21 |
+
</p>
|
| 22 |
+
<p id="p-4" num="4">
|
| 23 |
+
<confidence value="14851151172">46439OU892)</confidence>
|
| 24 |
+
filed on January 19, 2006; </p>
|
| 25 |
+
<p id="p-5" num="5">United States Patent Application Serial No. [<confidence value="6">[</confidence>
|
| 26 |
+
<confidence value="5">]</confidence>
|
| 27 |
+
11/351,918 <confidence value="565524566541588">(Attorey-Deeket</confidence>
|
| 28 |
+
<confidence value="5482585254582">No-46434US92)</confidence>
|
| 29 |
+
filed on February 10, 2006 <confidence value="8">;</confidence>
|
| 30 |
+
</p>
|
| 31 |
+
<p id="p-6" num="6">United States Patent Application Serial No. [[ <confidence value="5">1</confidence>
|
| 32 |
+
]11/335801 <confidence value="6655558566241665">(Attorney-Doeket</confidence>
|
| 33 |
+
<confidence value="41166565661242">Nea-46432U892)</confidence>
|
| 34 |
+
filed on January 19, 2006; </p>
|
| 35 |
+
<p id="p-7" num="7">United States Patent Application Serial No. [[ <confidence value="68">]1</confidence>
|
| 36 |
+
1/302<confidence value="5">,</confidence>
|
| 37 |
+
930 <confidence value="2466">emet</confidence>
|
| 38 |
+
<confidence value="5586">No-1</confidence>
|
| 39 |
+
-64<confidence value="415542">33US2)</confidence>
|
| 40 |
+
filed on December 14, 2005; </p>
|
| 41 |
+
<p id="p-8" num="8">United States Patent Application Serial No. [<confidence value="6">[</confidence>
|
| 42 |
+
<confidence value="6">1</confidence>
|
| 43 |
+
]11/318,980 <confidence value="665544566524655">(Attoney-Deoket</confidence>
|
| 44 |
+
<confidence value="4521565884144">N-4-6434US92}</confidence>
|
| 45 |
+
filed on December 27<confidence value="5">,</confidence>
|
| 46 |
+
2005; </p>
|
| 47 |
+
<p id="p-9" num="9">United States Patent Application Serial No. [<confidence value="6">[</confidence>
|
| 48 |
+
<confidence value="668">1]1</confidence>
|
| 49 |
+
1/300,388 <confidence value="6655286666541665">(Attorney-Doeket</confidence>
|
| 50 |
+
<confidence value="5582884">No-4643</confidence>
|
| 51 |
+
<confidence value="42472">5U82)</confidence>
|
| 52 |
+
filed on December 14, 2005; </p>
|
| 53 |
+
<p id="p-10" num="10">United States Patent Application Serial No. [<confidence value="6">[</confidence>
|
| 54 |
+
<confidence value="668">1]1</confidence>
|
| 55 |
+
1/332,892 <confidence value="5666566666542665">(Attorney-Doeket</confidence>
|
| 56 |
+
<confidence value="41486">Noe-4</confidence>
|
| 57 |
+
643<confidence value="555141">6US-2)</confidence>
|
| 58 |
+
filed on January 17, 2006 <confidence value="8">;</confidence>
|
| 59 |
+
</p>
|
| 60 |
+
<p id="p-11" num="11">United States Patent Application Serial No. [[ <confidence value="68">]1</confidence>
|
| 61 |
+
1/335<confidence value="5">,</confidence>
|
| 62 |
+
026 <confidence value="6666266666542665">(Att^rney-Doeket</confidence>
|
| 63 |
+
<confidence value="44825828581181">Ne-46487-U892)</confidence>
|
| 64 |
+
filed on January 19, 2006; and United States Patent Application Serial No. [[ <confidence value="468">]]1</confidence>
|
| 65 |
+
1/333,159 <confidence value="6655588666642666">(Attorney-Doeket</confidence>
|
| 66 |
+
<confidence value="41482528844581">Noe-47964US92)</confidence>
|
| 67 |
+
filed on January 17, 2006. </p>
|
| 68 |
+
<boundary-data type="header">Page 3 of 20</boundary-data>
|
| 69 |
+
<boundary-data type="header">Application No. 11/333,495</boundary-data>
|
| 70 |
+
<boundary-data type="header">Reply to Office Action of July 09, 2008</boundary-data>
|
| 71 |
+
<p id="p-12" num="12">
|
| 72 |
+
<page-break num="2"/>
|
| 73 |
+
At Paragraph [0064] Please amend paragraph [0064] of the specification as follows: </p>
|
| 74 |
+
<p id="p-13" num="13">[0064] The RAW CODEC block <part-num-ref name="RAW CODEC block">214</part-num-ref>
|
| 75 |
+
may comprise suitable code that may be compiled directly or statically into the image editor 200<confidence value="5658">RE-F</confidence>
|
| 76 |
+
#. The PNG CODEC block <part-num-ref name="PNG CODEC block">216</part-num-ref>
|
| 77 |
+
may comprise suitable logic, circuitry, and/or code that may handle PNG compression and decompression of various images. The PNG CODEC block <part-num-ref name="PNG CODEC block">216</part-num-ref>
|
| 78 |
+
may be dynamically loaded into the image editor 2<confidence value="88587">00REF</confidence>
|
| 79 |
+
#. The JPEG CODEC block <part-num-ref name="JPEG CODEC block">218</part-num-ref>
|
| 80 |
+
may comprise suitable logic, circuitry, and/or code that may handle JPEG compression and decompression of various images. One or more of the CODECs such as the JPEG CODEC block <part-num-ref name="JPEG CODEC block">216</part-num-ref>
|
| 81 |
+
may be dynamically loaded into the image editor 200<confidence value="868">REF</confidence>
|
| 82 |
+
#. The GIF CODEC block <part-num-ref name="GIF CODEC block">220</part-num-ref>
|
| 83 |
+
may comprise suitable logic, circuitry, and/or code that may handle GIF compression and decompression of various images. The image CODEC for video block <part-num-ref name="image CODEC for video block">222</part-num-ref>
|
| 84 |
+
may comprise suitable logic and/or code that may handle image compression and decompression of various images. </p>
|
| 85 |
+
<p id="p-14" num="14">At Paragraph [0066] Please amend paragraph [0066] of the specification as follows:</p>
|
| 86 |
+
<p id="p-15" num="15">[0066] The plugin manager block <part-num-ref name="plugin manager block">226</part-num-ref>
|
| 87 |
+
may comprise suitable logic, circuitry, and/or code that may manage plugin that may be defined by a user. In this regard, the plugin manager block <part-num-ref name="plugin manager block">226</part-num-ref>
|
| 88 |
+
may handle various functions for the plugin effects block <part-num-ref name="plugin effects block">224.</part-num-ref>
|
| 89 |
+
In accordance with an embodiment of the invention, some advanced plugin operations may require a whole frame of image data, in which case the stripe interface <part-num-ref name="stripe interface">210</part-num-ref>
|
| 90 |
+
may be bypassed. In this regard, image data may be read from and/or written directly to a resource supplied by the resource block <part-num-ref name="resource block">208.</part-num-ref>
|
| 91 |
+
There may be instances where the same resource may not be used simultaneously as input and an output. In this regard, simultaneous use of a resource as an input and an output may result in data corruption <boundary-data type="header">Page 4 of 20</boundary-data>
|
| 92 |
+
<page-break num="3"/>
|
| 93 |
+
<boundary-data type="header">Application No. 11/333,495</boundary-data>
|
| 94 |
+
<boundary-data type="header">Reply to Office Action of July 09, 2008</boundary-data>
|
| 95 |
+
since an image may be processed a stripe at a time and written back to a file. An exception to this may occur when both the input and the output are in memory and the data is in RAW format. An image editor with plugin capability for editing images in a mobile communication device is described in more detail in United States Patent Application Serial No. [<confidence value="6">[</confidence>
|
| 96 |
+
<confidence value="5">]</confidence>
|
| 97 |
+
11/333,159<confidence value="6">]</confidence>
|
| 98 |
+
<confidence value="2">(</confidence>
|
| 99 |
+
<confidence value="5242">ttrn</confidence>
|
| 100 |
+
<confidence value="2">o</confidence>
|
| 101 |
+
<confidence value="5">e</confidence>
|
| 102 |
+
<confidence value="2">o</confidence>
|
| 103 |
+
filed on January <part-num-ref name="mobile communication device is described in more detail in United States Patent Application Serial No. [[ ]11/333,159] ( ttrn o e o filed on January">17,</part-num-ref>
|
| 104 |
+
<part-num-ref name="mobile communication device is described in more detail in United States Patent Application Serial No. [[ ]11/333,159] ( ttrn o e o filed on January 17,">2006,</part-num-ref>
|
| 105 |
+
which is incorporated herein by reference in its entirety. </p>
|
| 106 |
+
<boundary-data type="header">Page 5 <confidence value="88">of</confidence>
|
| 107 |
+
<confidence value="88">20</confidence>
|
| 108 |
+
</boundary-data>
|
| 109 |
+
</description>
|
| 110 |
+
</us-patent-application>
|
| 111 |
+
|
applicant/11350903.xml
ADDED
|
@@ -0,0 +1,439 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11350903</doc-number>
|
| 8 |
+
<date>2006-02-10</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">
|
| 14 |
+
<confidence value="111">,I,</confidence>
|
| 15 |
+
</heading>
|
| 16 |
+
<p id="p-1" num="1">
|
| 17 |
+
<confidence value="8">1</confidence>
|
| 18 |
+
</p>
|
| 19 |
+
<heading id="h-2">TRANSCODING METHOD IN A MOBILE COMMUNICATIONS SYSTEM</heading>
|
| 20 |
+
<heading id="h-3">FIELD OF THE INVENTION</heading>
|
| 21 |
+
<p id="p-2" num="2">[0001] The present solution relates to a method of code conversion for pro- viding enhanced communications services to a user in a mobile communica- tions system.</p>
|
| 22 |
+
<heading id="h-4">BACKGROUND OF THE INVENTION</heading>
|
| 23 |
+
<p id="p-3" num="3">[0002] One special feature offered in mobile communications systems is group communication. Conventionally group communication has been avail- able in trunked mobile communications systems, such as Professional Radio or Private Mobile Radio (PMR) systems, such as TETRA (Terrestrial Trunked Radio), which are special radio systems primarily intended for professional and governmental users, such as the police, military forces, oil plants.</p>
|
| 24 |
+
<p id="p-4" num="4">[0003] Group communication with a push-to-talk feature is one of the avail- able solutions. Generally, in voice communication provided with a "push-to- talk, release-to-listen" feature, a group call is based on the use of a pressel (push-to-talk button) as a switch. By pressing the pressel the user indicates his/her desire to speak, and the user equipment sends a service request to the network. The network either rejects the request or allocates the requested re- sources on the basis of predetermined criteria, such as the availability of re- sources, priority of the requesting user, etc. At the same time, a connection may also be established to other users in a specific subscriber group. When the voice connection has been established, the requesting user can talk and <page-break num="2"/>
|
| 25 |
+
<boundary-data type="header">
|
| 26 |
+
<confidence value="8">2</confidence>
|
| 27 |
+
</boundary-data>
|
| 28 |
+
the other users can listen on the channel. When the user releases the pressel, the user equipment signals a release message to the network, and the re- sources are released. Thus, instead of being reserved for a "call", the re- sources are reserved only for the actual speech transaction or speech item. </p>
|
| 29 |
+
<p id="p-5" num="5">[0004] The group communication is now becoming available also in public mobile communications systems. New packet-based group voice and data ser- vices are being developed for cellular networks, especially in the evolution of the GSM/GPRS/UMTS network. According to some approaches, the group communication service, and also one-to-one communication, is provided as a packet-based user or application level service in which the underlying commu- nications system only provides the basic connections (i.e. IP (Internet protocol) connections) between the group communications applications in the user ter- minals and the group communication service. The group communication ser- vice can be provided by a group communication server system while the group client applications reside in the user equipment or terminals. When this ap- proach is employed for push-to-talk communication, the concept is also re- ferred to as Push-to-talk over Cellular (PoC) network. Push-to-talk over Cellu- lar is an overlay speech service in a mobile cellular network where a connec- tion between two or more parties is established (typically) for a longer period, but the actual radio channels in the air interface are activated only when somebody is talking.</p>
|
| 30 |
+
<p id="p-6" num="6">[0005] A disadvantage of the current PoC systems is that the users of a PoC service are expected to be able to "talk" and/or "listen", i.e. to engage in <page-break num="3"/>
|
| 31 |
+
<boundary-data type="header">
|
| 32 |
+
<confidence value="8">3</confidence>
|
| 33 |
+
</boundary-data>
|
| 34 |
+
voice communication, in order to be able to take part in the P<confidence value="56">oC</confidence>
|
| 35 |
+
communica- tion. </p>
|
| 36 |
+
<heading id="h-5">BRIEF DESCRIPTION OF THE INVENTION</heading>
|
| 37 |
+
<p id="p-7" num="7">[0006] It is thus an object of the present invention to provide a method, a system, a network node and a mobile station for implementing the method so as to alleviate the above disadvantage. The objects of the present invention are achieved by a method and an arrangement characterized by what is stated in the independent claims. The preferred embodiments are disclosed in the dependent claims.</p>
|
| 38 |
+
<p id="p-8" num="8">[0007] According to a first aspect of the invention, during a communication session, such as a P<confidence value="56">oC</confidence>
|
| 39 |
+
session, a first user terminal is arranged to transmit, after having received a text inserted by a user, corresponding text-coded data to a network node. On the basis of the text-coded data received at the network node, the network node is arranged to generate an output comprising speech- coded data. The output includes the semantics of the text-coded data. </p>
|
| 40 |
+
<p id="p-9" num="9">
|
| 41 |
+
<confidence value="5">[</confidence>
|
| 42 |
+
0008] According to a second aspect of the invention, during a communica- tion session, such as a PoC session, a first user terminal is arranged to trans- mit, after having received speech from a user, corresponding speech-coded data to a network node. On basis of the speech-coded data received at the network node, the network node is arranged to generate an output comprising text-coded data. The output includes the semantics of the speech-coded data. </p>
|
| 43 |
+
<p id="p-10" num="10">
|
| 44 |
+
<page-break num="4"/>
|
| 45 |
+
<confidence value="22">r></confidence>
|
| 46 |
+
<confidence value="8">4</confidence>
|
| 47 |
+
[0009] According to a third aspect of the invention, during a communication session, such as a P<confidence value="56">oC</confidence>
|
| 48 |
+
session, a first user terminal is arranged to transmit, after having received speech from a user, corresponding first speech-coded data to a network node. On the basis of the first speech-coded data received at the network node, the network node is arranged to generate converted data. </p>
|
| 49 |
+
<p id="p-11" num="11">On the basis of the generated converted data the network node is arranged to then generate an output comprising second speech-coded data. The converted data and the output include the semantics of the first speech-coded data.</p>
|
| 50 |
+
<p id="p-12" num="12">[0010] According to a fourth aspect of the invention, the user terminal is ar- ranged, after receiving text-coded or speech-coded input <confidence value="2">-</confidence>
|
| 51 |
+
data from the user, by means of a communication session, such as a P<confidence value="56">oC</confidence>
|
| 52 |
+
session, to transmit cor- responding input data to the network node. The network node is arranged to perform at least one code conversion on the received input data to generate converted data. On the basis of the generated converted data, the network node is arranged to then generate an output comprising speech-coded data or text-coded output data, and to transmit the output from the network node to the user terminal. The converted data includes the semantics of the input data in a transcoded form. The output data includes the semantics of the input data in a translated form. </p>
|
| 53 |
+
<p id="p-13" num="13">[0011] An advantageous feature of the first aspect of the present solution is that it allows a speaking-impaired person to participate in a group communica- tion session, such as a P<confidence value="56">oC</confidence>
|
| 54 |
+
session. It also allows the P<confidence value="56">oC</confidence>
|
| 55 |
+
user to communi- cate in a place where speaking is not allowed. The second aspect of the pre- <page-break num="5"/>
|
| 56 |
+
<boundary-data type="header">
|
| 57 |
+
<confidence value="8">5</confidence>
|
| 58 |
+
</boundary-data>
|
| 59 |
+
sent solution enables including subtitles into a video that is being played in a video-PoC session. It allows a hearing-impaired person to participate in a P<confidence value="66">oC</confidence>
|
| 60 |
+
session. An advantageous feature of the third aspect of the present solution is that the user may participate in the PoC session anonymously, without reveal- ing his/her real identity to the other participants, as s/he is able to use an anonymous identity and/or artificial voice. The fourth aspect of the present so- lution allows the user to use a PoC terminal for obtaining a translation of a word or a sentence into another language. According to the fourth aspect, the user is able to send text and receive the translation in the form of speech, send speech and receive the translation in the form of text, and/or send speech and receive the translation in the form of speech. By means of the present solution, the user is able to have speech or text translated or embedded into other me- dia, for example, text or translated text may be superimposed or embedded in a video stream, which has an effect similar to video stream subtitles. </p>
|
| 61 |
+
<heading id="h-6">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 62 |
+
<p id="p-14" num="14">
|
| 63 |
+
<confidence value="5">[</confidence>
|
| 64 |
+
0012] In the following the invention will be described in greater detail by means of embodiments with reference to the accompanying drawings, in which [0013] Figure 1 illustrates a telecommunication system according to the pre- sent solution; </p>
|
| 65 |
+
<p id="p-15" num="15">[0014<confidence value="5">]</confidence>
|
| 66 |
+
Figures 2 and <part-num-ref name="and">3</part-num-ref>
|
| 67 |
+
illustrate signalling according to the present solution; </p>
|
| 68 |
+
<p id="p-16" num="16">[0015] Figure 4 is a flow chart illustrating the function of a PoC server ac- cording to the present solution.</p>
|
| 69 |
+
<boundary-data type="header">
|
| 70 |
+
<confidence value="8">6</confidence>
|
| 71 |
+
</boundary-data>
|
| 72 |
+
<heading id="h-7">DETAILED DESCRIPTION OF THE INVENTION</heading>
|
| 73 |
+
<p id="p-17" num="17">
|
| 74 |
+
<page-break num="6"/>
|
| 75 |
+
[0016] The embodiments of the present solution will be described below implemented in a 3G WCDMA (3<confidence value="5">r</confidence>
|
| 76 |
+
d generation Wideband code division multiple access) mobile communication system, such as the UMTS (Universal mobile telecommunications system). However, the invention is not restricted to these embodiments, but it can be applied in any communication system capable of providing push-to-talk and/or so called "Rich Call" services. Examples of such mobile systems include IMT-2000, IS-41, CDMA2000, GSM (Global system for mobile communications) or other similar mobile communication systems, such as the PCS (Personal communication system) or the DCS <part-num-ref name="DCS">1800</part-num-ref>
|
| 77 |
+
(Digital cellular system for <part-num-ref name="(Digital cellular system for">1800</part-num-ref>
|
| 78 |
+
MHz). The invention may also be utilized in any IP-based communication system, such as in the Internet. Specifications of communica- tions systems in general and of the IMT-2000 and the UMTS in particular are being developed rapidly. Such a development may require additional changes to be made to the present solution. Therefore, all the words and expressions should be interpreted as broadly as possible and they are only intended to il- lustrate and not to restrict the invention. What is essential for the present solu- tion is the function itself and not the network element or the device in which the function is implemented. </p>
|
| 79 |
+
<p id="p-18" num="18">[0017] The concept of the Push-to-talk over Cellular system PoC is, from an end-user point of view, similar to the short-wave radio and professional radio technologies. The user pushes a button, and after s/he has received a "ready to talk" signal, meaning that the user has reserved the floor for talking, s/he <page-break num="7"/>
|
| 80 |
+
</p>
|
| 81 |
+
<heading id="h-8">
|
| 82 |
+
<confidence value="111">,(I</confidence>
|
| 83 |
+
</heading>
|
| 84 |
+
<p id="p-19" num="19">
|
| 85 |
+
<confidence value="8">7</confidence>
|
| 86 |
+
can talk while keeping the PTT button pressed. The other users, i.e. members of the group in case of a group call, or one recipient in case of a 1-to-<confidence value="5">1</confidence>
|
| 87 |
+
call, are listening. The term "sender" may be used to refer to a user that talks at certain point of time (or, according to the present solution, transmits text or multime- dia). The term "recipient" may be used to refer to a user that listens to an in- coming talk burst (or, according to the present solution, receives text or multi- media). In this context, the term "talk burst" is used to refer to a shortish, unin- terrupted stream of talk sent by a single user during a P<confidence value="56">oC</confidence>
|
| 88 |
+
session. </p>
|
| 89 |
+
<p id="p-20" num="20">[0018] The present solution may also be applied to an arrangement imple- menting Rich Call. The Rich Call concept generally refers to a call combining different media and services, such as voice, video and mobile multimedia messaging, into a single call session. It applies efficient Internet protocol (IP) technology in a mobile network, such as so-called A<confidence value="6684">ll-I</confidence>
|
| 90 |
+
P technology. In this context the Rich Call feature may be implemented into a PoC system or it may be implemented into a mobile system that is not a P<confidence value="56">oC</confidence>
|
| 91 |
+
system. </p>
|
| 92 |
+
<p id="p-21" num="21">[0019] Figure 1 illustrates a telecommunications system S to which the prin- ciples of the present solution may be applied. In Fig. 1, a Push-to-talk over Cel- lular talk group server PS, i.e. a PoC server, is provided e.g. on top of a packet switched mobile network (not shown) in order to provide a packet mode (e.g.</p>
|
| 93 |
+
<p id="p-22" num="22">IP) voice, data and/or multimedia communication services to at least one user equipment UE1, UE2. The user equipment UE1, UE2 may be a mobile termi- nal, such as a P<confidence value="56">oC</confidence>
|
| 94 |
+
terminal, utilizing the packet-mode communication services provided by the P<confidence value="56">oC</confidence>
|
| 95 |
+
server PS of the system S. The P<confidence value="56">oC</confidence>
|
| 96 |
+
system comprises <page-break num="8"/>
|
| 97 |
+
<boundary-data type="header">
|
| 98 |
+
<confidence value="8">8</confidence>
|
| 99 |
+
</boundary-data>
|
| 100 |
+
several functional entities on top of the cellular network, which are not de- scribed in further detail here. The user functionality runs over the cellular net- work, which provides the data transfer services for the P<confidence value="56">oC</confidence>
|
| 101 |
+
system. The PoC system can also be seen as a core network using the cellular network as a ra- dio access network. The underlying cellular network can be, for example, a general packet radio system (GPRS) or a third generation (3G) radio access network. It should also be appreciated that the present solution does not need to be restricted to mobile stations and mobile systems but the terminal can be any terminal having a voice communication or multimedia capability in a com- munications system. For example, the user terminal may be a terminal (such as a personal computer PC) having Internet access and a Vo<confidence value="4">I</confidence>
|
| 102 |
+
P capability for voice communication over the Internet. It should be noted that a participant of a P<confidence value="56">oC</confidence>
|
| 103 |
+
session does not necessarily have to be a user terminal, it may also be a PoC client or some other client, such as an application server or an auto- mated system. The term "automated system" refers to a machine emulating a user of the P<confidence value="56">oC</confidence>
|
| 104 |
+
system and behaving as an "intelligent" participant in the P<confidence value="56">oC</confidence>
|
| 105 |
+
session, i.e. it refers to a computer-generated user having artificial intelligence. </p>
|
| 106 |
+
<p id="p-23" num="23">It may also be a simple pre-recorded message activated, for example, by means of a keyword. There may be a plurality of communication servers, i.e.</p>
|
| 107 |
+
<p id="p-24" num="24">
|
| 108 |
+
<confidence value="856">PoC</confidence>
|
| 109 |
+
servers, in the P<confidence value="56">oC</confidence>
|
| 110 |
+
system, but for reasons of clarity only one PoC server is shown in Figure 1. The P<confidence value="56">oC</confidence>
|
| 111 |
+
server comprises control-plane functions and user-plane functions providing packet mode server applications that communi- cate with the communication client application(s) in the user equipment UE1, UE2 over the IP connections provided by the communication system. The P<confidence value="56">oC</confidence>
|
| 112 |
+
<page-break num="9"/>
|
| 113 |
+
<boundary-data type="header">
|
| 114 |
+
<confidence value="8">9</confidence>
|
| 115 |
+
</boundary-data>
|
| 116 |
+
server PS according to the present solution may include a transcoding engine, or the transcoding engine may be a separate entity connected to the P<confidence value="56">oC</confidence>
|
| 117 |
+
server PS. </p>
|
| 118 |
+
<p id="p-25" num="25">[0020] Figure 2 illustrates, by way of example, the signaling according to an embodiment of the present solution. In Figure 2, a PoC communication ses- sion, which may also be referred to as a "P<confidence value="56">oC</confidence>
|
| 119 |
+
call", is established 2-1 between at least one user equipment UE1, UE2 and the P<confidence value="56">oC</confidence>
|
| 120 |
+
server PS. In step 2-2, an input received from a user of a first user equipment is registered, i.e. detected, in the first user equipment UE1. The received user input may comprise voice (speech), text and/or multimedia from the user. The user input may further comprise an indication whether (and how) the input should be transcoded (e.g. </p>
|
| 121 |
+
<p id="p-26" num="26">text-to-speech) and/or translated (e.g. Finnish-to-English) by the PoC server PS. The term "transcoding" refers to performing a code conversion of digital signals in one code to corresponding signals in a different code. Code conver- sion enables the carrying of signals in different types of networks or systems.</p>
|
| 122 |
+
<p id="p-27" num="27">The user equipment may be arranged to detect information on a language se- lected by the user or on a default language. Then, a corresponding talk burst (or text or multimedia) is transmitted 2-3 from the first user equipment UE<confidence value="5">1</confidence>
|
| 123 |
+
to the P<confidence value="56">oC</confidence>
|
| 124 |
+
server PS. This means that the user has used the push-to-talk button in order to speak or send text or multimedia during the session. In connection with the talk burst, information may be transmitted on whether, and how, the talk burst is to be transcoded and/or translated by the P<confidence value="56">oC</confidence>
|
| 125 |
+
server PS. In step 2-4, the talk burst is received in the PoC server PS. After receiving the talk burst in step 2-4, the P<confidence value="56">oC</confidence>
|
| 126 |
+
server is arranged to check whether the talk burst <page-break num="10"/>
|
| 127 |
+
<boundary-data type="header">
|
| 128 |
+
<confidence value="88">10</confidence>
|
| 129 |
+
</boundary-data>
|
| 130 |
+
comprises data that should be transcoded and/or translated. After that, it car- ries out 2-4 the appropriate speech-to-text, text-to-text (e.g. language transla- tion) and/or text-to-speech transcoding as described below, in order to provide an output talk burst. Then, the output talk burst (comprising voice, text, or mul- timedia) is transmitted 2-5 to the at least one second user equipment UE2. In step 2-6, the output talk burst is received in at least one second user equip- ment UE2. Alternatively, in step 2-4, the PoC server may be arranged to store the output talk burst without sending it to UE2. This allows the sending of the transcoded message via some other means instead of or in addition to PoC. </p>
|
| 131 |
+
<p id="p-28" num="28">This also allows storing the (possibly transcoded) messages for some other purpose. Thus the output talk burst may, for example, be saved into a file and/or be transmitted (later) e.g. by <confidence value="5">e</confidence>
|
| 132 |
+
-mail or MMS (Multimedia Messaging Service). This option may be utilized for example in a situation where a sender for some reason wishes to send data at a postponed time schedule. This op- tion may also be utilized for example in a situation where the system is ar- ranged to send "welcome data" to users who later join to the group communi- cation. Another option is that the output talk burst is provided to a P<confidence value="66">oC</confidence>
|
| 133 |
+
client or a server that stores the output talk burst. </p>
|
| 134 |
+
<p id="p-29" num="29">[0021] Figure 3 illustrates, by way of example, the signaling according to another embodiment of the present solution. In Figure 3, a PoC communication session, which may also be referred to as a "PoC call", is established 3-1 be- tween a user equipment UE1 and a P<confidence value="66">oC</confidence>
|
| 135 |
+
server PS. In step 3-2, an input is received in the first user equipment UE1 from a user of the user equipment. </p>
|
| 136 |
+
<p id="p-30" num="30">The received user input may comprise voice, text and/or multimedia from the <page-break num="11"/>
|
| 137 |
+
<boundary-data type="header">
|
| 138 |
+
<confidence value="88">11</confidence>
|
| 139 |
+
</boundary-data>
|
| 140 |
+
user. The user input may also comprise an indication whether (and how) the input is to be transcoded and/or translated by the P<confidence value="56">oC</confidence>
|
| 141 |
+
server PS. The user equipment may be arranged to detect information on a language selected by the user, e.g. by using a presence server, or on a default language. The pres- ence server may be an entity located in the P<confidence value="56">oC</confidence>
|
| 142 |
+
server, or a different product. </p>
|
| 143 |
+
<p id="p-31" num="31">The presence server maintains user presence data (such as "available", "busy", "do not disturb", location, time zone) and user preference data (such as language preferences). Then, a corresponding talk burst (or text or multimedia) is transmitted 3-3 from the user equipment UE1 to the P<confidence value="56">oC</confidence>
|
| 144 |
+
server PS. This means that the user has used the push-to-talk button in order to speak or send text or multimedia during the session. In connection with the talk burst, infor- mation may be transmitted whether, and how, the talk burst is to be transcoded and/or translated. In step 3-4, the talk burst is received in the P<confidence value="56">oC</confidence>
|
| 145 |
+
server PS. </p>
|
| 146 |
+
<p id="p-32" num="32">After receiving the talk burst in step 3-4, the PoC server is arranged to check whether the talk burst comprises data that should be transcoded and/or trans- lated. After that it carries out the appropriate speech-to-text, text-to-text (e.g.</p>
|
| 147 |
+
<p id="p-33" num="33">language translation) and/or text-to-speech transcoding as described below, in order to provide an output talk burst. Then, the output talk burst (comprising voice, text or multimedia) is transmitted 3-5 back to the user equipment UE1.</p>
|
| 148 |
+
<p id="p-34" num="34">In step 3-6, the output talk burst is received in the user equipment UE<confidence value="68">1.</confidence>
|
| 149 |
+
</p>
|
| 150 |
+
<p id="p-35" num="35">[0022] Figure 4 is a flow chart illustrating the function of a P<confidence value="56">oC</confidence>
|
| 151 |
+
server PS according to the present solution. In step 4-1, a P<confidence value="56">oC</confidence>
|
| 152 |
+
communication session is established. In step 4-2, a talk burst (or text or multimedia) is received from a first user equipment UE1. The talk burst (or text or multimedia) may also com- <page-break num="12"/>
|
| 153 |
+
<boundary-data type="header">
|
| 154 |
+
<confidence value="88">12</confidence>
|
| 155 |
+
</boundary-data>
|
| 156 |
+
prise information on whether, and/or how, it is to be transcoded and/or trans- lated in the P<confidence value="56">oC</confidence>
|
| 157 |
+
server. The talk burst may further comprise information on a language selected by the user or on a default language. Thus, after receiving the talk burst, the P<confidence value="56">oC</confidence>
|
| 158 |
+
server PS is arranged to check, in step 4-3, whether the talk burst comprises data that should be transcoded and/or translated, and/or how the information may be found in the presence server (or some other loca- tion where the user<confidence value="8">'</confidence>
|
| 159 |
+
s preferences are defined). If no transcoding and/or trans- lating is required, the P<confidence value="56">oC</confidence>
|
| 160 |
+
server forwards 4-4 the talk burst to the other par- ticipants of the P<confidence value="56">oC</confidence>
|
| 161 |
+
session. If transcoding and/or translating is required, the <confidence value="856">PoC</confidence>
|
| 162 |
+
server PS carries out 4-5 the appropriate speech-to-text, text-to-text (e.g. </p>
|
| 163 |
+
<p id="p-36" num="36">language translation) and/or text-to-speech transcoding as described below.</p>
|
| 164 |
+
<p id="p-37" num="37">
|
| 165 |
+
<confidence value="5">-</confidence>
|
| 166 |
+
After that, the transcoded and/or translated talk burst is transmitted to the other participants (or as in the case of Figure 3, back to the sender) of the PoC ses- sion. It should be noted that a participant of a P<confidence value="56">oC</confidence>
|
| 167 |
+
session may also be a P<confidence value="56">oC</confidence>
|
| 168 |
+
client, and thus, according to the present solution, the transcoded and/or trans- lated talk burst may be provided to a P<confidence value="56">oC</confidence>
|
| 169 |
+
client or a server. Alternatively, in step 4-5, the P<confidence value="56">oC</confidence>
|
| 170 |
+
server may be arranged to store the transcoded and/or translated talk burst without sending it to UE2. In this case the output talk burst may, for example, be saved into a file and/or be transmitted (later). </p>
|
| 171 |
+
<p id="p-38" num="38">[0023] In the following, the text-to-speech, text-to-text and speech-to-text transcoding/translating operations according to the present solution are de- scribed further.</p>
|
| 172 |
+
<boundary-data type="header">
|
| 173 |
+
<confidence value="88">13</confidence>
|
| 174 |
+
</boundary-data>
|
| 175 |
+
<p id="p-39" num="39">
|
| 176 |
+
<page-break num="13"/>
|
| 177 |
+
Text-to-s<confidence value="5">p</confidence>
|
| 178 |
+
eech [0024] The text-to-speech PoC (or Rich Call) application according to the present solution allows the user to send text to the application, and have it transcoded into speech. The user may turn the text-to-speech feature on or off by means of a P<confidence value="56">oC</confidence>
|
| 179 |
+
client. By doing so, the user may change his/her PoC status, so that the text-to-speech transcoding is enabled. A PoC server re- ceives 2-4, 4-2 text from the user and transcodes 2-4, 4-5 the text into speech. </p>
|
| 180 |
+
<p id="p-40" num="40">It may be possible for the transcoding engine to decide the language of the talk burst, or the sender and/or the recipient may be able to set a default text-to- speech language by means of the PoC client.</p>
|
| 181 |
+
<p id="p-41" num="41">[0025] The text-to-speech application may allow the user to send alterna- tively text and talk bursts. The sender may wish to send sometimes text and sometimes talk bursts during the same PoC session. In this case, the text-to- speech transcoding is performed in addition to the normal PoC service (i.e.</p>
|
| 182 |
+
<p id="p-42" num="42">real-time voice). If the sender sends a talk burst, it is transmitted to the recipi- ent(s) via the P<confidence value="56">oC</confidence>
|
| 183 |
+
server PS. If the sender sends 2-3 an input comprising text- coded data, the text-coded data is transcoded 2-4, 4-5 into speech by the PoC server, and the speech-coded data is then transmitted 2-5 to the recipient as a corresponding talk burst. </p>
|
| 184 |
+
<p id="p-43" num="43">[0026] The text-to-speech application may allow the user to utilize a feature that speaks out the text typed by the user. The user may send 3-3 text to the PoC application, and receive 3-6 back the corresponding "spoken" text. This may be useful for the user if s/he wishes to get an idea of how the text sounds <page-break num="14"/>
|
| 185 |
+
<boundary-data type="header">
|
| 186 |
+
<confidence value="88">14</confidence>
|
| 187 |
+
</boundary-data>
|
| 188 |
+
when it is transcoded into speech by the text-to-speech transcoding engine in the P<confidence value="66">oC</confidence>
|
| 189 |
+
server PS. The sender is thus able to listen to the text transcoded into speech by means of a specific language-reader service, so that the sender gets to hear a proper pronunciation of a word or a sentence. This feature is also useful for speaking-impaired persons. </p>
|
| 190 |
+
<p id="p-44" num="44">[0027] The P<confidence value="66">oC</confidence>
|
| 191 |
+
service transcodes the text into the speech according to preferences set by the user, or according to default preferences. The Po<confidence value="5">C</confidence>
|
| 192 |
+
server PS may comprise an additional component called transcoding function (also referred to as a transcoding engine). The component may be located in- side or outside of the actual PoC server PS. The transcoding functionality of the transcoding function is used for the text-to-speech transcoding. The client may request such functionality from the P<confidence value="66">oC</confidence>
|
| 193 |
+
server by changing a respective <confidence value="866">PoC</confidence>
|
| 194 |
+
presence status. For example, a PoC presence status may be of the fol- lowing form: </p>
|
| 195 |
+
<p id="p-45" num="45"><PoC Text-To-Speech> <Transcoding>[Off, On]</Transcoding> <Default Language> [English,Serbian,<confidence value="1">1</confidence>
|
| 196 |
+
talian,Finnish,...] </Default Language> </PoC Text-To-Speech> <page-break num="15"/>
|
| 197 |
+
<confidence value="16">41</confidence>
|
| 198 |
+
<part-num-ref name="">
|
| 199 |
+
<confidence value="88">15</confidence>
|
| 200 |
+
</part-num-ref>
|
| 201 |
+
[0028] The transcoding function may be turned on or off. If the transcoding is on, the server transcodes the text sent by the sender into speech and then sends it to the recipient(s). The default language may be the language that the sender is using. If the default language field is empty, the P<confidence value="56">oC</confidence>
|
| 202 |
+
server may be arranged to use its own default settings (e.g. Finnish language for operators in Finland) or to recognize the used language. The term "presence status" or "presence server" used herein do not necessarily have to refer to P<confidence value="56">oC</confidence>
|
| 203 |
+
pres- ence, they may also be used to refer to generic presence or generic presence attributes for some other type of communication, such as full-duplex speech and/or instant messaging sessions. </p>
|
| 204 |
+
<p id="p-46" num="46">[0029] When the P<confidence value="56">oC</confidence>
|
| 205 |
+
server is to transcode text into speech, in order to be transmitted to certain recipients (or to a certain recipient), the server will invoke the transcoding function. The transcoding function may be an existing text-to- speech transcoder, and it carries out the actual transcoding of text into speech. </p>
|
| 206 |
+
<p id="p-47" num="47">The server receives 2-4, 3-4, 4-2 the text from the sender and transcodes 2-4, 3-4, 4-5 it (according to the sender's PoC presence preferences). For example, if the preferences are: Transcoding=<confidence value="5">O</confidence>
|
| 207 |
+
n, Default Language=English, the transcoding engine will use these preferences for transcoding the text into a talk burst. The talk burst is then transmitted 2-5, 3-5, 4-6 to the recipient(s) (or in case of Figure 3, back to the sender). </p>
|
| 208 |
+
<p id="p-48" num="48">[0030] The implementation in the P<confidence value="56">oC</confidence>
|
| 209 |
+
client allows the sender to send text in a P<confidence value="56">oC</confidence>
|
| 210 |
+
1-to-<confidence value="5">1</confidence>
|
| 211 |
+
or group conversation. The sender is able to send text which is then transcoded in the P<confidence value="56">oC</confidence>
|
| 212 |
+
server, and the transcoded text (i.e. talk burst) is <page-break num="16"/>
|
| 213 |
+
<boundary-data type="header">
|
| 214 |
+
<confidence value="88">16</confidence>
|
| 215 |
+
</boundary-data>
|
| 216 |
+
sent from the PoC server to the recipient(s). This functionality may be utilized together with the speech-to-text functionality. In other words, the user may choose to use only text-to-speech, only speech-to-text, or both simultaneously. </p>
|
| 217 |
+
<p id="p-49" num="49">The P<confidence value="56">oC</confidence>
|
| 218 |
+
client may allow the user to choose his/her transcoding preferences from a menu. This enables the user to choose the default language, etc. The implementation may allow the transcoding preferences to be chosen by means of keywords or key symbols included in the typed text. For example, if the sender types in the beginning of the text "LANG:ENGLISH" or <confidence value="5">"</confidence>
|
| 219 |
+
*En*<confidence value="5">"</confidence>
|
| 220 |
+
, the transcoding function may be arranged to use this information for transcoding, and as a result of this, a voice reads the text in English. </p>
|
| 221 |
+
<p id="p-50" num="50">[0031] The text-to-speech application according to the present solution en- ables the P<confidence value="56">oC</confidence>
|
| 222 |
+
service to be used by hearing/speaking-impaired users, or by users that are in an environment where ordinary usage of the P<confidence value="56">oC</confidence>
|
| 223 |
+
service is not possible. Some users (e.g. teenagers) may find it easier to send text in the group conversation than to speak with their own voice.<confidence value="5">.</confidence>
|
| 224 |
+
This approach enables the anonymity of the user to be kept, as the user does not necessarily have to use his/her own voice in the conversation. </p>
|
| 225 |
+
<p id="p-51" num="51">[0032] The transcoding (text-to-speech) should be carried out in a usable way. To be able to correctly decode most of the transmitted speech it should be of high quality. Therefore, an existing text-to-speech component available on the market may be used.</p>
|
| 226 |
+
<p id="p-52" num="52">[0033] The aspects described above are not mandatory. In other words, text-to-speech transcoding may be used in a default mode (e.g. translation <page-break num="17"/>
|
| 227 |
+
<boundary-data type="header">
|
| 228 |
+
<confidence value="88">17</confidence>
|
| 229 |
+
</boundary-data>
|
| 230 |
+
from English text to English voice), without the possibility that the subscriber chooses the language, etc. </p>
|
| 231 |
+
<p id="p-53" num="53">[0034] There are several situations, where the recipient may be interested in utilising text-to-speech transcoding in P<confidence value="56">oC</confidence>
|
| 232 |
+
. For example, if the sender is <confidence value="5">,</confidence>
|
| 233 |
+
speaking-impaired, the conventional Push-to-talk over Cellular service may be difficult or even impossible to use. In addition, the advanced PoC services, such as "video P<confidence value="56">oC</confidence>
|
| 234 |
+
" or "Rich Call", are not usable for the speaking-impaired persons since the sender is not able, partially or fully, to send talk bursts be- cause s/he is not able to speak properly, and is thus unable to take part in a PoC conversation. On the other hand, the sender may be in a place that re- quires silent usage of the service. This means that if the recipient is in an envi- ronment where talking and/or listening is not possible (e.g. in a theatre, school, or meeting) the usage of the P<confidence value="56">oC</confidence>
|
| 235 |
+
service is not possible with the conventional implementation, i.e. the user is not able to send speech to the P<confidence value="56">oC</confidence>
|
| 236 |
+
application (because of the restrictive environment). </p>
|
| 237 |
+
<p id="p-54" num="54">Speech-to-text (video clip subtitles) [0035] The "video P<confidence value="56">oC</confidence>
|
| 238 |
+
", "see what <confidence value="5">I</confidence>
|
| 239 |
+
See", or "Rich Call" concepts allow a mobile user to share a video stream in connection with P<confidence value="56">oC</confidence>
|
| 240 |
+
or other media sessions (group or 1-to-<confidence value="5">1</confidence>
|
| 241 |
+
sessions). As a sender sends video stream any par- ticipant in the group may use the push-to-talk button in order to speak (i.e. to send talk bursts). The term "sender" refers to a user that talks at certain point of time, or sends video stream from his/her terminal. A recipient refers to a user that is listening to incoming talk bursts and/or viewing video streams. </p>
|
| 242 |
+
<boundary-data type="header">
|
| 243 |
+
<confidence value="88">18</confidence>
|
| 244 |
+
</boundary-data>
|
| 245 |
+
<p id="p-55" num="55">
|
| 246 |
+
<page-break num="18"/>
|
| 247 |
+
[0036] There may be situations when a user wishes to participate in a video <confidence value="856">PoC</confidence>
|
| 248 |
+
session, but is not willing (or able) to receive the audio. If the recipient is hearing-impaired, the ordinary push-to-talk audio service is difficult or even impossible to use. The recipient may wish to use the push-to-talk audio and video (and possibly also some other media) but the recipient is not able hear the audio talk bursts. On the other hand, if the recipient is in a noisy environ- ment, or in an environment where listening is not possible (like in a theatre, school, or meeting), the usage of the advanced P<confidence value="56">oC</confidence>
|
| 249 |
+
services is not possible with the conventional implementation. Therefore, the present solution allows talk bursts to be encoded to subtitles. According to the present solution, the recipient is able to turn a video stream subtitles feature on or off in the P<confidence value="56">oC</confidence>
|
| 250 |
+
client. This is an advantageous feature for example when the recipient is hear- ing-impaired, or the recipient is not able to listen to talk bursts for some other reason. </p>
|
| 251 |
+
<p id="p-56" num="56">[0037] As noted above, the recipient may be in a place that requires "silent" usage of the P<confidence value="56">oC</confidence>
|
| 252 |
+
service. A video stream subtitles option included in the P<confidence value="56">oC</confidence>
|
| 253 |
+
client allows the recipient to receive simultaneously video stream (i.e. a video clip) and a talk burst. This involves the P<confidence value="56">oC</confidence>
|
| 254 |
+
server PS being arranged to re- ceive 2-4, 4-2 an incoming talk burst from the sender UE1, transcode 2-4, 4-5 it into text, embed the text (as subtitles) to the video stream, and transmit 2-5, 4-6 the video stream with the embedded text to the recipient UE2. </p>
|
| 255 |
+
<p id="p-57" num="57">[0038] The transcoding engine may be arranged to decide the language of the text. Alternatively, the recipient (or the sender) may be able to set a default <page-break num="19"/>
|
| 256 |
+
<boundary-data type="header">
|
| 257 |
+
<confidence value="88">19</confidence>
|
| 258 |
+
</boundary-data>
|
| 259 |
+
speech-to-text language by means of the PoC client. The addition of subtitles may also be implemented in such a way that the audio of the video clip is kept. </p>
|
| 260 |
+
<p id="p-58" num="58">If the recipient is in a "quiet speech-to-text" mode the audio is not sent to him/her. It is also possible that the incoming talk burst comes from a P<confidence value="56">oC</confidence>
|
| 261 |
+
group session different from the one where the video comes from; for example, the video may be shared in a group "Friends", and the talk burst may come from a group "Family". Also in this case the PoC server is arranged to embed the text into the video stream, but it may be shown in a different way. For ex- ample, the name of the group from which the talk burst comes may be put in front of the text, text from the same group may be merged in the video, text from another group may be shown by means of a vertically or horizontally scrolling banner, or different colours may be used. </p>
|
| 262 |
+
<p id="p-59" num="59">[0039] The speech-to-text transcoding is carried out by means of a transcoding function component (i.e. a transcoding engine). The transcoding function component may be located inside or outside of the P<confidence value="56">oC</confidence>
|
| 263 |
+
server PS. </p>
|
| 264 |
+
<p id="p-60" num="60">Thus the P<confidence value="56">oC</confidence>
|
| 265 |
+
service uses the transcoding functionality of the transcoding function component for the speech-to-text transcoding. In addition, the P<confidence value="56">oC</confidence>
|
| 266 |
+
server has a component for editing (and/or mixing) the video streams. The component may be referred to as an editing component (not shown in Figure 1), and it may be located inside or outside of the P<confidence value="56">oC</confidence>
|
| 267 |
+
server PS. The editing (or mixing) component is able to receive 2-4, 4-2 the video stream, and embed the text in the form of subtitles into the video stream in order to provide a modi- fied video stream. After that the modified stream is transmitted 2-5, 4-6 as data packets from the P<confidence value="56">oC</confidence>
|
| 268 |
+
server PS to the recipient(s) UE2. It may also send <page-break num="20"/>
|
| 269 |
+
<boundary-data type="header">
|
| 270 |
+
<confidence value="88">20</confidence>
|
| 271 |
+
</boundary-data>
|
| 272 |
+
separately audio and video stream with embedded synchronization informa- tion. Regardless of the technique used for embedding/mixing/superimposing of the video and text, the end result is the same from the recipient's point of view. </p>
|
| 273 |
+
<p id="p-61" num="61">Any particular method of adding the text to the video is not mandated by the present solution.</p>
|
| 274 |
+
<p id="p-62" num="62">[0040] The P<confidence value="56">oC</confidence>
|
| 275 |
+
client may request the video clip subtitles functionality from the server by changing its PoC presence status. The P<confidence value="56">oC</confidence>
|
| 276 |
+
presence status of the client may look as follows: </p>
|
| 277 |
+
<p id="p-63" num="63">
|
| 278 |
+
<confidence value="8856"><PoC</confidence>
|
| 279 |
+
Video Clip Speech-To-Text> <Transcoding>[On, Off]</Transcoding> <Language> [English, Serbian, Italian, Finnish,...] </Language> <Subtitles> <Background>[On, Of<confidence value="5">f</confidence>
|
| 280 |
+
]</Background> <Background colour> [Black, White,...] </Background colour> <Font> <confidence value="8866">[Ari</confidence>
|
| 281 |
+
al, Comic Sans MS,...] </Font> <Font size> <page-break num="21"/>
|
| 282 |
+
<boundary-data type="header">
|
| 283 |
+
<confidence value="88">21</confidence>
|
| 284 |
+
</boundary-data>
|
| 285 |
+
[Large, Medium, Small] </Font size> <Font colour> [Black, White,...] </Font colour> </Subtitles> </PoC Video Clip Speech-To-Text> [0041] The client may change his/her "PoC video clip speech-to-text pres- ence" at any time. When the transcoding P<confidence value="66">oC</confidence>
|
| 286 |
+
presence attribute is set to "on", the server is arranged to receive incoming audio (i.e. video stream with em- bedded audio, or separate audio talk bursts), carry out the speech-to-text transcoding (a default language setting may be used, or the P<confidence value="66">oC</confidence>
|
| 287 |
+
server may be arranged to decide the language), embed text into the video as subtitles, and transmit 2-5, 4-6 the modified video stream to the appropriate recipient(s). </p>
|
| 288 |
+
<p id="p-64" num="64">The term "presence" used herein does not necessarily have to refer to P<confidence value="66">oC</confidence>
|
| 289 |
+
presence, it may also be used to refer to generic presence or generic presence attributes for some other type of communication, such as full-duplex video, au- dio and/or text messaging. </p>
|
| 290 |
+
<p id="p-65" num="65">[0042] Thus the speech-to-text feature according to the present solution al- lows the video stream to be displayed on the screen of the user terminal to- gether with the subtitles embedded/superimposed in the video stream. The user is able to turn the P<confidence value="66">oC</confidence>
|
| 291 |
+
video clip speech-to-text P<confidence value="66">oC</confidence>
|
| 292 |
+
presence function on or off. This may be carried out by means of a menu. In a submenu the user <page-break num="22"/>
|
| 293 |
+
<boundary-data type="header">
|
| 294 |
+
<confidence value="88">22</confidence>
|
| 295 |
+
</boundary-data>
|
| 296 |
+
(i.e. the sender and/or the recipient) may be able to select a default transcod- ing language. If the default language is selected, the server is arranged to use the default language specified by the user. Otherwise, the server may be ar- ranged to use default settings set by the service provider, or to recognize the language that is used. </p>
|
| 297 |
+
<p id="p-66" num="66">[0043<confidence value="5">]</confidence>
|
| 298 |
+
This functionality may also be achieved, if the mixing server is ar- ranged to send text and video streams separately, with or without the synchro- nization information. The mixing/superimposing/embedding of the text and video may be carried out on the client side according to the local user prefer- ences. The user may locally choose to e.g. change the text position, size or colour in the video. </p>
|
| 299 |
+
<p id="p-67" num="67">[0044] Insertion settings of the text over the video may be selected by the user. For example, the user may choose the appearance of the subtitles. The editing component in the PoC server may use the options selected by the user, or the server may be arranged to use default settings, or to adjust settings to the characteristics of the video (for instance, if the background is light, a dark background for subtitles may be used, and vice versa). It should be noted that the insertion of the text over the video might also be done on the client side. In this case the PoC server is arranged to send appropriate media streams sepa- rately (e.g. video stream and text stream in a selected language), and the cli- ent is arranged to take care of the synchronization and the displaying.</p>
|
| 300 |
+
<boundary-data type="header">
|
| 301 |
+
<confidence value="88">23</confidence>
|
| 302 |
+
</boundary-data>
|
| 303 |
+
<p id="p-68" num="68">
|
| 304 |
+
<page-break num="23"/>
|
| 305 |
+
[0045] The speech-to-text transcoding should be done in a usable way. In order to be able to correctly decode speech it should be of a high quality. </p>
|
| 306 |
+
<p id="p-69" num="69">Therefore, an existing speech-to-text transcoding component may be used.</p>
|
| 307 |
+
<p id="p-70" num="70">Virtual identity [0046] According to an embodiment of the present solution, a virtual identity feature may be included in the P<confidence value="56">oC</confidence>
|
| 308 |
+
system. There may be situations where a <confidence value="856">PoC</confidence>
|
| 309 |
+
user would like to use a virtual identity. If a sender wishes to take part in a chat group anonymously with a virtual identity, the PoC application allows sending speech using artificial voice and pictures or video clip stored and merged to a talk burst. Here, the sender refers to a user that talks or sends text or multimedia at a certain time point during a PoC session. The recipient is a user that receives a talk burst, text or multimedia. Again, it should be noted that the embodiment herein does not necessarily have to refer to a P<confidence value="56">oC</confidence>
|
| 310 |
+
com- munication system, but it may refer to any type of communication system for enabling video, audio, IP multimedia and/or some other media communication. </p>
|
| 311 |
+
<p id="p-71" num="71">[0047] The user may wish to take part in a P<confidence value="56">oC</confidence>
|
| 312 |
+
session with a voice differ- ent from his/her own and/or to provide pictures or video clips together with the talk burst in order to create a virtual identity for him/herself. The sender may turn a virtual identity feature on or off in the PoC client. The virtual identity pro- file includes a set of "profile moods" selected by the user. These settings are also available to the P<confidence value="56">oC</confidence>
|
| 313 |
+
server. The P<confidence value="56">oC</confidence>
|
| 314 |
+
server PS is arranged to perform a series of multimedia modifications and/or additions on the sent text/audio/video <page-break num="24"/>
|
| 315 |
+
<boundary-data type="header">
|
| 316 |
+
<confidence value="88">24</confidence>
|
| 317 |
+
</boundary-data>
|
| 318 |
+
before delivering to the recipient(s). These modifications and/or additions cor- respond to the profile moods set selected by the user. </p>
|
| 319 |
+
<p id="p-72" num="72">[0048] In connection with the PoC server, an additional component called a transcoding function is provided. This component may be located inside or outside of the P<confidence value="56">oC</confidence>
|
| 320 |
+
server. The PoC service uses the transcoding functionality of the transcoding function component for performing an appropriate speech- to-text or text-to-speech transcoding operation(s) according to the present so- lution. Further, in connection with the P<confidence value="56">oC</confidence>
|
| 321 |
+
server, an additional component called a media function is provided. Also this component may be located inside or outside of the PoC server. The P<confidence value="56">oC</confidence>
|
| 322 |
+
service uses the functionality of the media function component for producing an artificial voice for a talk burst in cooperation with the transcoding function according to the sender profile moods, and for combining still pictures, video clips, animated 3D pictures etc. </p>
|
| 323 |
+
<p id="p-73" num="73">with talk bursts. The video stream and the talk burst are sent together to the recipient(s) in one or more simultaneous sessions.</p>
|
| 324 |
+
<p id="p-74" num="74">[0049] For example, the virtual identity feature may be implemented, by means of presence XML settings, in the following way:</p>
|
| 325 |
+
<p id="p-75" num="75">
|
| 326 |
+
<confidence value="8856"><PoC</confidence>
|
| 327 |
+
Virtual Identity> <Voice> <Status>[on, off]</Status> <Language> [English, Serbian, Italian, Finnish,...] <page-break num="25"/>
|
| 328 |
+
<boundary-data type="header">
|
| 329 |
+
<confidence value="88">25</confidence>
|
| 330 |
+
</boundary-data>
|
| 331 |
+
</Language> <Tune> [Default Man, Default Woman, Angry Man, Nice Woman, Electric,...] <confidence value="8688"></Tu</confidence>
|
| 332 |
+
ne> <confidence value="86"><N</confidence>
|
| 333 |
+
oice> <Video> <Status>[on, of<confidence value="66">f]</confidence>
|
| 334 |
+
</Status> <confidence value="885"><Ty</confidence>
|
| 335 |
+
pe> [Still 2D Picture, Animated 3D Face, Recorded Clip,...] <confidence value="8686"></Ty</confidence>
|
| 336 |
+
pe> <Source> [http://photos.com/name/face<confidence value="5">1</confidence>
|
| 337 |
+
.jpg, http://www.mail.com/demo.htm, 0709AB7287254<confidence value="66">15</confidence>
|
| 338 |
+
C2A,...<confidence value="8">]</confidence>
|
| 339 |
+
</Source> <confidence value="86"><N</confidence>
|
| 340 |
+
ideo> </PoC Virtual <confidence value="5">I</confidence>
|
| 341 |
+
dentity> [0050] The profile attribute "Language" (<PoC Virtual <confidence value="4">I</confidence>
|
| 342 |
+
den- tity><Voice><Language>) refers to a default language that the sender is using. </p>
|
| 343 |
+
<p id="p-76" num="76">If this field is empty, the server may be arranged to use its own default setting (e.g. Finnish language for operators in Finland) or to try to recognise the used <page-break num="26"/>
|
| 344 |
+
<boundary-data type="header">
|
| 345 |
+
<confidence value="88">26</confidence>
|
| 346 |
+
</boundary-data>
|
| 347 |
+
language. The profile attribute "Voice Tune" (<PoC Virtual Iden- tity><Voice><Tune>) refers to a situation where the sender sends speech, text or multimedia to a group, and the recipient(s) receive a talk burst with a certain voice tune selected by the sender in his/her profile moods. As the sender sends 2-3 speech, the PoC server PS is arranged to transcode 2-4 it into text, and an artificial voice tune is created. The voice tune may be selected from a list of predefined voice samples as described above, or in a more detailed way for a component of human speech according to the following example: </p>
|
| 348 |
+
<p id="p-77" num="77"><Default Language> [English, Serbian, Italian, Finnish,...] </Default Language> <Voice>[Male, Female, male child, female child,...]<<confidence value="5">N</confidence>
|
| 349 |
+
oice> <Mood> [Normal, Happy, Ecstatic, Annoyed, Screaming, Crying,...] </Mood> <Volume>[Normal, Whisper, Shout,...]<<confidence value="5">N</confidence>
|
| 350 |
+
olume] <Accent> [English with Finnish Accent, English with Italian Accent,...] </Accent> <Modulation>[Echo, High-Pitch, Radio-like,..<confidence value="82">.]</confidence>
|
| 351 |
+
</Modulation> [0051] The attribute Still 2D Picture (<PoC Virtual Iden- tity><Video><Type>Still Picture) refers to a feature where the recipient(s), re- <page-break num="27"/>
|
| 352 |
+
<boundary-data type="header">
|
| 353 |
+
<confidence value="88">27</confidence>
|
| 354 |
+
</boundary-data>
|
| 355 |
+
ceiving a talk burst, may simultaneously view a two-dimensional picture de- fined in the sender profile moods. The attribute Animated 3D Face (<P<confidence value="66">oC</confidence>
|
| 356 |
+
Vir- tual <confidence value="4">I</confidence>
|
| 357 |
+
dentity><Video><Type>Animated 3D Face) refers to a feature where the recipient(s), receiving a talk burst, may view a three-dimensional animated face defined in the sender profile moods. A 3D animated face is a 2D picture of a face that is submitted to a process that makes it look like a 3D face that moves, and that may open and/or close the eyes and mouth when the sender talks. The attribute Recorded Video Clip (<PoC Virtual Iden- tity><Video><Type>Recorded Clip) refers to a feature where the recipient(s) receiving a talk burst may view a video clip decided by the sender in his/her profile moods. If the video clip is longer than the speech, the video clip may be truncated, or the talk burst may continue silently. If the video clip is shorter than the speech, it may be repeated in a loop, or the last image may be kept on the screen of the recipient's terminal. </p>
|
| 358 |
+
<p id="p-78" num="78">[0052] The user may join a Rich Call P<confidence value="66">oC</confidence>
|
| 359 |
+
group "friends", and set his/her virtual identity in the following way: </p>
|
| 360 |
+
<p id="p-79" num="79"><PoC Virtual Identity> <Voice> <Status>on</Status> <Language>English</Language> <Tune>Robot<<confidence value="5">/</confidence>
|
| 361 |
+
Tune> <confidence value="866"></V</confidence>
|
| 362 |
+
oice> <page-break num="28"/>
|
| 363 |
+
<boundary-data type="header">
|
| 364 |
+
<confidence value="88">28</confidence>
|
| 365 |
+
</boundary-data>
|
| 366 |
+
<Video> <Status>on</Status> <Type>Animated 3D Face<<confidence value="5">/</confidence>
|
| 367 |
+
Type> <Source> http://www.mail.com/demo.htm </Source> <confidence value="866"></V</confidence>
|
| 368 |
+
ideo> </PoC Virtual Identity> [0053] The sender says to the group "I will terminate you all..." by using a normal P<confidence value="66">oC</confidence>
|
| 369 |
+
talk. The server transcodes the speech to the artificially created speech of the Robot, and adds the video stream of the automated 3D face of the Robot. The recipients in the group see the "Animated 3D Face" of the Ro- bot and hear the Robot's voice. The eyes and mouth of the Robot open and close as if it were talking. Thus the user is able to use a virtual identity in the group communication. </p>
|
| 370 |
+
<p id="p-80" num="80">[0054] The user may join a "voice only" P<confidence value="66">oC</confidence>
|
| 371 |
+
group "Robot fans". The user may set his/her virtual identity in the following way: </p>
|
| 372 |
+
<p id="p-81" num="81"><PoC Virtual Identity> <Voice> <Status>on</Status> <Language>English</Language> <page-break num="29"/>
|
| 373 |
+
<boundary-data type="header">
|
| 374 |
+
<confidence value="88">29</confidence>
|
| 375 |
+
</boundary-data>
|
| 376 |
+
<Tune>Robot<<confidence value="5">/</confidence>
|
| 377 |
+
Tune> <confidence value="86"><N</confidence>
|
| 378 |
+
oice> <Video> <Status>off</Status> <confidence value="86"><N</confidence>
|
| 379 |
+
ideo> </PoC Virtual Identity> [0055] If the user says to the group "I will terminate you all...", the recipients will hear the Robot's voice. This enables the anonymity of the user. Thus the <confidence value="866">PoC</confidence>
|
| 380 |
+
service may be used with a virtual identity enhancing P<confidence value="66">oC</confidence>
|
| 381 |
+
chat groups. </p>
|
| 382 |
+
<p id="p-82" num="82">The P<confidence value="66">oC</confidence>
|
| 383 |
+
users may try different combinations of voice and video streams that are combined together. </p>
|
| 384 |
+
<p id="p-83" num="83">[0056] The transcoding should be carried out in a usable way (speech-to- text). In order to be able to correctly decode most of the speech it should be of a high quality. If the speech is not decoded accurately enough, the end-user satisfaction may drop. Therefore, a state-of-the-art speech-to-text/text-to- speech component should be used.</p>
|
| 385 |
+
<p id="p-84" num="84">
|
| 386 |
+
<confidence value="22222222">Lanquaqe</confidence>
|
| 387 |
+
translation [0057] A user may wish to participate in a 1-to-<confidence value="5">1</confidence>
|
| 388 |
+
or group communication in a situation where the other participant(s) use a language that is unknown to the user. In a situation where the other participants of a P<confidence value="66">oC</confidence>
|
| 389 |
+
session use a lan- guage that the user is not able to speak or write, the conventional push-to-talk service is useless as the user is not able to take part in the conversation of the <page-break num="30"/>
|
| 390 |
+
<boundary-data type="header">
|
| 391 |
+
<confidence value="88">30</confidence>
|
| 392 |
+
</boundary-data>
|
| 393 |
+
group. On the other hand the user may be in a situation where s/he would like to get a translation of a phrase. If the user needs a fast translation in a practi- cal situation, like ordering chocolate in a foreign country, an instant translation service might be helpful. There are also a lot of other situations where a cor- rect translation (possibly together with a correct pronunciation) would be use- ful. Thus the PoC application could be provided with an "automatic translation service". In this context, the term sender refers to the user that talks or sends text at a certain point of time. The term recipient refers to the user that is listen- ing to incoming talk bursts or receiving text. </p>
|
| 394 |
+
<p id="p-85" num="85">[0058] In a situation where the sender does not know the language that is used in a group the sender may turn a language translation feature on or off in the PoC client, and the setting will be available in the server. This implies that the sender may speak to the group (send talk bursts or text) using a source language, and a P<confidence value="56">oC</confidence>
|
| 395 |
+
server is arranged to perform a language translation be- fore delivering the translated talk burst to the other recipient(s). If the sender would like to get a fast translation in order to communicate directly with some- one the user may send speech or text to an automatic translation service pro- vider that performs the translation and delivers the translated speech and/or text back to the user. For instance, a user could send speech to a service pro- vider providing Italian-to-English translations, and as a result receive real-time text and/or speech translation into English. </p>
|
| 396 |
+
<p id="p-86" num="86">[0059] For example, the user may, while in a bar, send the following speech to the Italian-to-English service provider: "Vorrei una cioccolata calda, per <page-break num="31"/>
|
| 397 |
+
<boundary-data type="header">
|
| 398 |
+
<confidence value="88">31</confidence>
|
| 399 |
+
</boundary-data>
|
| 400 |
+
piacere". The speech gets translated into English language by the Italian-to- English service provider, and the PoC server delivers the talk burst with the translation back to the user: "I would like to have a hot chocolate, please". The talk burst. is then played by means of a loudspeaker of the user terminal, and the waiter may listen to and understand what the user wants. </p>
|
| 401 |
+
<p id="p-87" num="87">[0060] The P<confidence value="56">oC</confidence>
|
| 402 |
+
server may have an additional component called a transcoding function. The component may be located inside or outside of the PoC server. The P<confidence value="56">oC</confidence>
|
| 403 |
+
service may utilize the transcoding functionality of the transcoding function component for transcoding speech-to-text or text-to- speech. </p>
|
| 404 |
+
<p id="p-88" num="88">[0061] The speech translation is not necessarily carried out directly; there- fore the speech-to-speech translation process may include: a speech-to-text <confidence value="22222222222">transcoding</confidence>
|
| 405 |
+
step, a text-to-text translation step, and a text-to-speech transcod- ing step. The speech-to-text transcoding engine and the text-to-text translator may be arrang<confidence value="8">e</confidence>
|
| 406 |
+
d to automatically detect the source language, or the sender may be able to select a default speech and/or text language by means of the PoC client. </p>
|
| 407 |
+
<p id="p-89" num="89">[0062] The language translation feature may be implemented as P<confidence value="56">oC</confidence>
|
| 408 |
+
pres- ence XML settings in the following way: </p>
|
| 409 |
+
<p id="p-90" num="90"><PoC Automatic Language Translation> <Audio Translation> <page-break num="32"/>
|
| 410 |
+
<boundary-data type="header">
|
| 411 |
+
<confidence value="88">32</confidence>
|
| 412 |
+
</boundary-data>
|
| 413 |
+
<Status>[on, of<confidence value="5">f</confidence>
|
| 414 |
+
]</Status> <Source Language> [English, Serbian, Italian, Finnish] </Source Language> <Destination Language> [English, Serbian, Italian, Finnish] </Destination Language> </Audio Translation> <Text Translation> <Status>[on, off]</Status> <Source Language> [English, Serbian, Italian, Finnish] </Source Language> <Destination Language> [English, Serbian, Italian, Finnish] </Destination Language> <confidence value="86"></</confidence>
|
| 415 |
+
Text Translation> <confidence value="86"></</confidence>
|
| 416 |
+
PoC Automatic Language Translation> [0063] The implementation in the client enables the client to request the functionality from the server by changing the P<confidence value="56">oC</confidence>
|
| 417 |
+
presence (or some generic presence) status in order to perform a translation. Thus a text-to-text transla- tion may be performed, and the implementation may allow the preferences for the translation to be chosen by means of a keyword or a key symbol included <page-break num="33"/>
|
| 418 |
+
<boundary-data type="header">
|
| 419 |
+
<confidence value="88">33</confidence>
|
| 420 |
+
</boundary-data>
|
| 421 |
+
in the typed text. For example, if the sender types in the beginning of the text "LANG:ITA-ENG", the translation function is arranged to use this information for translating. </p>
|
| 422 |
+
<p id="p-91" num="91">[0064] With this improvement the difficulty of the users having no language in common may be overcome, which increases the flexibility of the PoC service when used for international communication. The usage of a variety of features may be enhanced, such as transcoding speech into text, translating text, transcoding text into speech, and streaming text instead of voice. The lan- guage translation feature allows the recipients in a group to receive translated text or speech. Further, it allows the original sender of text or speech to get a translation of the text or speech.</p>
|
| 423 |
+
<p id="p-92" num="92">[0065] The transcoding and the translating operations should be carried out in a usable way. Existing speech-to-text, text-to-speech and/or text-to-text (translation) components may be used.</p>
|
| 424 |
+
<p id="p-93" num="93">[0066] The present invention enables the performance of the following transcoding or translation acts in a PoC or Rich Call system: text->speech, speech->text, speech->text->speech, text->text->speech, speech->text->text, speech->text->text->speech. However, it is obvious to a person skilled in the art that data handled only by the server and not visible to the user does not necessarily have to be in a text (or speech) format but it may be in some ap- propriate metafile format, such as file, email or any generic metadata format, as long as the semantics of the original input are kept in the final output re- ceived by the user.</p>
|
| 425 |
+
<boundary-data type="header">
|
| 426 |
+
<confidence value="88">34</confidence>
|
| 427 |
+
</boundary-data>
|
| 428 |
+
<p id="p-94" num="94">
|
| 429 |
+
<page-break num="34"/>
|
| 430 |
+
[0067] The present invention enables the user to select the transmitting mode and/or the transcoding mode (i.e. speech or text). </p>
|
| 431 |
+
<p id="p-95" num="95">[0068] The signalling messages and steps shown in Figures <part-num-ref name="signalling messages and steps shown in Figures">2,</part-num-ref>
|
| 432 |
+
<part-num-ref name="signalling messages and steps shown in Figures 2,">3</part-num-ref>
|
| 433 |
+
and <part-num-ref name="and">4</part-num-ref>
|
| 434 |
+
are simplified and aim only at describing the idea of the invention. Other signalling messages may be sent and/or other functions carried out between the mes- sages and/or the steps. The signalling messages serve only as examples and they may contain only some of the information mentioned above. The mes- sages may also include other information, and the titles of the messages may deviate from those given above. </p>
|
| 435 |
+
<p id="p-96" num="96">[0069] In addition to prior art devices, the system, network nodes or user terminals implementing the operation according to the invention comprise means for receiving, generating or transmitting text-coded or speech-coded data as described above. The existing network nodes and user terminals com- prise processors and memory, which may be used in the functions according to the invention. All the changes needed to implement the invention may be carried out by means of software routines that can be added or updated and/or routines contained in application specific integrated circuits (ASIC) and/or pro- grammable circuits, such as an electrically programmable logic device EPLD or a field programmable gate array FPGA.</p>
|
| 436 |
+
<p id="p-97" num="97">[0070] It will be obvious to a person skilled in the art that, as the technology advances, the inventive concept can be implemented in various ways. The in- vention and its embodiments are not limited to the examples described above but may vary within the scope of the claims.Claims </p>
|
| 437 |
+
</description>
|
| 438 |
+
</us-patent-application>
|
| 439 |
+
|
applicant/11359645.xml
ADDED
|
@@ -0,0 +1,348 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11359645</doc-number>
|
| 8 |
+
<date>2006-02-22</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">200500432</boundary-data>
|
| 14 |
+
<boundary-data type="header">
|
| 15 |
+
<confidence value="8">1</confidence>
|
| 16 |
+
</boundary-data>
|
| 17 |
+
<p id="p-1" num="1">Express Mail Label No. EV366579212US </p>
|
| 18 |
+
<heading id="h-1">AUTOMATED CABLE IDENTIFICATION AND</heading>
|
| 19 |
+
<heading id="h-2">VERIFICATION SYSTEM</heading>
|
| 20 |
+
<heading id="h-3">BACKGROUND</heading>
|
| 21 |
+
<p id="p-2" num="2">[0001] Computer systems can be networked through an interconnection of cables to provide increased communication, memory capacity and operating flexibility. Building, managing, and re-configuring the cable connections of a networked computer system is a complex task that may involve cable wiring diagrams, labeled cables, and connector reference designators. The task becomes increasingly complex with an increasing number of cables, connections and possible configurations, to the point where it is extremely difficult to effectively manage the cables, connections and configurations of the networked system in the traditional manner.</p>
|
| 22 |
+
<heading id="h-4">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 23 |
+
<p id="p-3" num="3">[0002] For a detailed description of exemplary embodiments of the invention, reference will now be made to the accompanying drawings in which:</p>
|
| 24 |
+
<p id="p-4" num="4">[0003] Figure 1 shows a schematic block illustration of a system for automated verifying and identifying of computer system component connection locations and sequences in accordance with an exemplary embodiment of the present invention;</p>
|
| 25 |
+
<p id="p-5" num="5">[0004] Figure 2 shows a flow chart of a method for assembling network components and then verifying correct network component assembly in accordance with an exemplary embodiment of the present invention;</p>
|
| 26 |
+
<p id="p-6" num="6">[0005] Figure 3 shows a flow chart of a method for guided disassembly and reconnection of network components while the network remains in operation in accordance with an exemplary embodiment of the present invention;</p>
|
| 27 |
+
<boundary-data type="header">145394.04<confidence value="5">/</confidence>
|
| 28 |
+
2162.44900 </boundary-data>
|
| 29 |
+
<boundary-data type="header">200500432</boundary-data>
|
| 30 |
+
<boundary-data type="header">
|
| 31 |
+
<confidence value="8">2</confidence>
|
| 32 |
+
</boundary-data>
|
| 33 |
+
<p id="p-7" num="7">
|
| 34 |
+
<page-break num="2"/>
|
| 35 |
+
[0006] Figure 4A-B shows a flow chart of a method for automated upgrade or replacement of a network system component in accordance with an exemplary embodiment of the present invention; and [0007] Figure 5A-B shows a flow chart of a method for automated reconfiguration of a network system component in accordance with an exemplary embodiment of the present invention. </p>
|
| 36 |
+
<heading id="h-5">NOTATION AND NOMENCLATURE</heading>
|
| 37 |
+
<p id="p-8" num="8">[0008] Certain terms are used throughout the following description and claims to refer to particular system components. As one skilled in the art will appreciate, computer companies may refer to a component by different names. This document does not intend to distinguish between components that differ in name but not function. In the following discussion and in the claims, the terms <confidence value="5">"</confidence>
|
| 38 |
+
including" and "comprising" are used in an open-ended fashion, and thus should be interpreted to mean "including, but not limited to... ." Also, the term "couple" or "couples" is intended to mean either an indirect or direct electrical connection. </p>
|
| 39 |
+
<p id="p-9" num="9">Thus, if a first device couples to a second device, that connection may be through a direct electrical connection, or through an indirect electrical connection via other devices and connections.</p>
|
| 40 |
+
<heading id="h-6">DETAILED DESCRIPTION</heading>
|
| 41 |
+
<p id="p-10" num="10">[0009] The following discussion is directed to various embodiments of the invention. Although one or more of these embodiments may be preferred, the embodiments disclosed should not be interpreted, or otherwise used, as limiting the scope of the disclosure, including the claims. In addition, one skilled in the art will understand that the following description has broad application, and the discussion of any embodiment is meant only to be exemplary of that embodiment, and not intended to intimate that the scope of the disclosure, including the claims, is limited to that embodiment.</p>
|
| 42 |
+
<p id="p-11" num="11">[0010] Figure 1 is a schematic illustration of one embodiment of various computer system component connections that may be used in embodiments of the present invention. A system management utility <part-num-ref name="system management utility">10</part-num-ref>
|
| 43 |
+
is provided, along with a plurality of network subsystems <part-num-ref name="plurality of network subsystems">20,</part-num-ref>
|
| 44 |
+
cables <part-num-ref name="plurality of network subsystems 20, cables">30,</part-num-ref>
|
| 45 |
+
cable connectors <part-num-ref name="plurality of network subsystems 20, cables 30, cable connectors">40,</part-num-ref>
|
| 46 |
+
and indicators <part-num-ref name="plurality of network subsystems 20, cables 30, cable connectors 40, and indicators">50.</part-num-ref>
|
| 47 |
+
System management utility <part-num-ref name="plurality of network subsystems 20, cables 30, cable connectors 40, and indicators 50. System management utility">10</part-num-ref>
|
| 48 |
+
is loaded with, or has access to, a <boundary-data type="header">145394.04/2162.44900</boundary-data>
|
| 49 |
+
<page-break num="3"/>
|
| 50 |
+
<boundary-data type="header">200500432</boundary-data>
|
| 51 |
+
<boundary-data type="header">
|
| 52 |
+
<confidence value="8">3</confidence>
|
| 53 |
+
</boundary-data>
|
| 54 |
+
firmware configuration map <part-num-ref name="firmware configuration map">60,</part-num-ref>
|
| 55 |
+
which comprises instructions that contain a desired connection configuration for computer system components such as cables <part-num-ref name="desired connection configuration for computer system components such as cables">30</part-num-ref>
|
| 56 |
+
with regard to network subsystems <part-num-ref name="with regard to network subsystems">20.</part-num-ref>
|
| 57 |
+
In general, the system management utility comprises executable software that performs some, or all, of the functionality described herein. In this embodiment, firmware configuration map <part-num-ref name="functionality described herein. In this embodiment, firmware configuration map">60</part-num-ref>
|
| 58 |
+
provides the instructions and roadmap for how network subsystems <part-num-ref name="instructions and roadmap for how network subsystems">20</part-num-ref>
|
| 59 |
+
are to be interconnected by cables <part-num-ref name="are to be interconnected by cables">30</part-num-ref>
|
| 60 |
+
inserted on each opposite end into cable connectors <part-num-ref name="inserted on each opposite end into cable connectors">40</part-num-ref>
|
| 61 |
+
that are integrated into each network subsystem <part-num-ref name="that are integrated into each network subsystem">20.</part-num-ref>
|
| 62 |
+
</p>
|
| 63 |
+
<p id="p-12" num="12">[0011] In alternative embodiments, firmware configuration map 60 may direct how other computer system components are connected with respect to network subsystems <part-num-ref name="may direct how other computer system components are connected with respect to network subsystems">20.</part-num-ref>
|
| 64 |
+
For example, in addition to, or instead of, cables <part-num-ref name="may direct how other computer system components are connected with respect to network subsystems 20. For example, in addition to, or instead of, cables">30</part-num-ref>
|
| 65 |
+
as the computer system components, firmware configuration map <part-num-ref name="computer system components, firmware configuration map">60</part-num-ref>
|
| 66 |
+
may provide connection information with respect to network subsystems <part-num-ref name="may provide connection information with respect to network subsystems">20</part-num-ref>
|
| 67 |
+
for computer system components including but not limited to network card/boards, processors, and <confidence value="586">1/O</confidence>
|
| 68 |
+
devices. </p>
|
| 69 |
+
<p id="p-13" num="13">[0012] Firmware configuration map 60 may further provide the sequence in which instructions for interconnecting network subsystems <part-num-ref name="sequence in which instructions for interconnecting network subsystems">20</part-num-ref>
|
| 70 |
+
should be executed. The sequence information present in firmware configuration map <part-num-ref name="sequence information present in firmware configuration map">60</part-num-ref>
|
| 71 |
+
serves as guided directions to help automate the connection in a desired order of several cables <part-num-ref name="desired order of several cables">30</part-num-ref>
|
| 72 |
+
between specific cable connectors <part-num-ref name="between specific cable connectors">40</part-num-ref>
|
| 73 |
+
associated with network subsystems <part-num-ref name="associated with network subsystems">20.</part-num-ref>
|
| 74 |
+
</p>
|
| 75 |
+
<p id="p-14" num="14">[0013] System management utility 10 may be connected with user interface <part-num-ref name="may be connected with user interface">70</part-num-ref>
|
| 76 |
+
via point-to-point connections and a private Local Area Network (LAN). User interface <part-num-ref name="private Local Area Network (LAN). User interface">70</part-num-ref>
|
| 77 |
+
may include user display <part-num-ref name="may include user display">72</part-num-ref>
|
| 78 |
+
and input interface <part-num-ref name="and input interface">74.</part-num-ref>
|
| 79 |
+
In some embodiments, user interface <part-num-ref name="and input interface 74. In some embodiments, user interface">70</part-num-ref>
|
| 80 |
+
may comprise a processor, user display <part-num-ref name="processor, user display">72</part-num-ref>
|
| 81 |
+
may be a PC monitor, and user interface <part-num-ref name="PC monitor, and user interface">74</part-num-ref>
|
| 82 |
+
may be a mouse and/or keyboard. The system management utility generally comprises code provided in storage (e.g., a hard disk drive) and executed by a processor. </p>
|
| 83 |
+
<p id="p-15" num="15">[0014] System management utility 10 may be used to direct the identification and sequence for connecting computer system components such as cables <part-num-ref name="identification and sequence for connecting computer system components such as cables">30</part-num-ref>
|
| 84 |
+
with respect to network subsystems <part-num-ref name="with respect to network subsystems">20.</part-num-ref>
|
| 85 |
+
Firmware configuration map <part-num-ref name="with respect to network subsystems 20. Firmware configuration map">60</part-num-ref>
|
| 86 |
+
has stored therein various programmed network subsystem <part-num-ref name="has stored therein various programmed network subsystem">20</part-num-ref>
|
| 87 |
+
connection <boundary-data type="header">145394.04<confidence value="5">/</confidence>
|
| 88 |
+
2162.44900 </boundary-data>
|
| 89 |
+
<page-break num="4"/>
|
| 90 |
+
<boundary-data type="header">200500432</boundary-data>
|
| 91 |
+
<boundary-data type="header">
|
| 92 |
+
<confidence value="8">4</confidence>
|
| 93 |
+
</boundary-data>
|
| 94 |
+
configurations desired for a given application. User interface <part-num-ref name="given application. User interface">70</part-num-ref>
|
| 95 |
+
allows a user to select the desired configuration from firmware configuration map <part-num-ref name="desired configuration from firmware configuration map">60,</part-num-ref>
|
| 96 |
+
which then directs indicators <part-num-ref name="desired configuration from firmware configuration map 60, which then directs indicators">50</part-num-ref>
|
| 97 |
+
to activate at a desired location and/or in a desired sequence to prompt user to make the appropriate the network subsystem <part-num-ref name="network subsystem">20</part-num-ref>
|
| 98 |
+
connection according to the selected firmware configuration map <part-num-ref name="selected firmware configuration map">60.</part-num-ref>
|
| 99 |
+
In certain embodiments, indicators <part-num-ref name="selected firmware configuration map 60. In certain embodiments, indicators">50</part-num-ref>
|
| 100 |
+
may comprise one or more light emitting diodes (LEDs). Alternatively, indicators <part-num-ref name="may comprise one or more light emitting diodes (LEDs). Alternatively, indicators">50</part-num-ref>
|
| 101 |
+
may comprise a digital console, or in a further alternative embodiment may comprise an audible indicator. </p>
|
| 102 |
+
<p id="p-16" num="16">[0015] In some embodiments, after the prompted connection is made, system management utility <part-num-ref name="prompted connection is made, system management utility">10</part-num-ref>
|
| 103 |
+
activates a connectivity test among the computer system components connected with respect to network subsystems <part-num-ref name="computer system components connected with respect to network subsystems">20</part-num-ref>
|
| 104 |
+
using diagnostic circuitry to verify that the connection locations and/or sequences previously made were completed according to firmware configuration map <part-num-ref name="connection locations and/or sequences previously made were completed according to firmware configuration map">60.</part-num-ref>
|
| 105 |
+
If the connection is erroneous, broken, or was made out-of-sequence, then system management utility <part-num-ref name="connection is erroneous, broken, or was made out-of-sequence, then system management utility">10</part-num-ref>
|
| 106 |
+
responds and either activates the indicator <part-num-ref name="indicator">50</part-num-ref>
|
| 107 |
+
at the connection location in a continuous or flashing manner, meaning that the connection task must either be corrected or repeated. If the connection is made properly according firmware configuration map <part-num-ref name="connection is made properly according firmware configuration map">60,</part-num-ref>
|
| 108 |
+
the indicator is deactivated, and system management utility <part-num-ref name="indicator is deactivated, and system management utility">10</part-num-ref>
|
| 109 |
+
advances to the next connection direction in the selected firmware configuration map <part-num-ref name="selected firmware configuration map">60.</part-num-ref>
|
| 110 |
+
</p>
|
| 111 |
+
<p id="p-17" num="17">[0016] One computer system component connection task, which is an embodiment according to the present invention, involves assembling cables in a configured-to-order arrangement provided by a firmware configuration map and verifying that the cables are ultimately connected in the desired configuration.</p>
|
| 112 |
+
<p id="p-18" num="18">Figure 2 is a flow chart of a method for assembling cables according to a firmware configuration map and then subsequently verifying the cable assembly.</p>
|
| 113 |
+
<p id="p-19" num="19">In a step <part-num-ref name="step">100,</part-num-ref>
|
| 114 |
+
a system management utility is provided with at least one firmware configuration map. In a step <part-num-ref name="step">102,</part-num-ref>
|
| 115 |
+
the desired firmware configuration map is accessed and selected through a system management utility interface. The firmware configuration map has two subroutines, which are available through the system management utility interface: one subroutine for indicating the desired cable connection location (i.e., the indicator subroutine), and a subroutine <boundary-data type="header">145394.04<confidence value="5">/</confidence>
|
| 116 |
+
2162.44900 </boundary-data>
|
| 117 |
+
<page-break num="5"/>
|
| 118 |
+
<boundary-data type="header">200500432</boundary-data>
|
| 119 |
+
<boundary-data type="header">
|
| 120 |
+
<confidence value="8">5</confidence>
|
| 121 |
+
</boundary-data>
|
| 122 |
+
designed for checking cable connectivity via electrical testing (i.e., the connectivity subroutine). </p>
|
| 123 |
+
<p id="p-20" num="20">[0017] In a step <part-num-ref name="step">104,</part-num-ref>
|
| 124 |
+
the indicator subroutine is accessed from the active firmware configuration map. When the indicator subroutine is prompted, it activates the indicators located near the connectors that are to be cable- connected pursuant to the firmware configuration map in a step <part-num-ref name="step">106.</part-num-ref>
|
| 125 |
+
The indicator in the present embodiment is an LED light source. One embodiment involves assigning color codes to the LED light source during the indicator subroutine (such as yellow) and additionally flashing the LED light source to further direct the desired cable connection configuration. In a step <part-num-ref name="step">108,</part-num-ref>
|
| 126 |
+
the ends of a network cable are inserted at the connector locations identified by the activated indicators. </p>
|
| 127 |
+
<p id="p-21" num="21">[0018] The connectivity subroutine is then accessed and activated in a step <part-num-ref name="step">110,</part-num-ref>
|
| 128 |
+
which initiates an electrical test to determine whether a valid connection has been made for the desired cable connection path according to the active firmware configuration map, and that the desired cable connection path has been maintained for a sufficient period of time. In a step <part-num-ref name="step">112,</part-num-ref>
|
| 129 |
+
if the proper connectivity is confirmed, a message is sent to the system management utility, and in a step <part-num-ref name="step">114,</part-num-ref>
|
| 130 |
+
the indicators at the connection points of interest are directed to change state. In one embodiment, the indicator is again an LED light source, and a successful connectivity test results in the LED light source illuminating a steady green colored light. </p>
|
| 131 |
+
<p id="p-22" num="22">[0019] In a step <part-num-ref name="step">116,</part-num-ref>
|
| 132 |
+
the indicator subroutine searches for more cable connections present in the active firmware configuration map. If more cable connections within the active firmware configuration map are identified, the method returns to step <part-num-ref name="method returns to step">104</part-num-ref>
|
| 133 |
+
where the indicator and connectivity subroutines are repeated for each cable connection in the firmware configuration map. Further, when there are no additional cable connections identified in the active firmware configuration map, the method returns to step <part-num-ref name="method returns to step">102</part-num-ref>
|
| 134 |
+
to access a different firmware configuration map loaded in the system management utility. </p>
|
| 135 |
+
<p id="p-23" num="23">[0020] If, during step 112, the connectivity test determines that a proper cable connection has not been made according to the active firmware configuration <boundary-data type="header">145394.04/2162.44900</boundary-data>
|
| 136 |
+
<page-break num="6"/>
|
| 137 |
+
<boundary-data type="header">200500432</boundary-data>
|
| 138 |
+
<boundary-data type="header">
|
| 139 |
+
<confidence value="8">6</confidence>
|
| 140 |
+
</boundary-data>
|
| 141 |
+
map, the indicator at the erroneous connection point is activated to show the incorrect connection in a step <part-num-ref name="step">118.</part-num-ref>
|
| 142 |
+
The activation of the indicator can mean either that the cable was not properly inserted such that a workable electrical connection was formed, or that the cable was inserted at the wrong location. </p>
|
| 143 |
+
<p id="p-24" num="24">Upon notification of an incorrect connection, the operator has the option of proceeding to a step <part-num-ref name="step">120,</part-num-ref>
|
| 144 |
+
in which the connection is fixed so that a proper electrical connection is made, and returning to step <part-num-ref name="proper electrical connection is made, and returning to step">110</part-num-ref>
|
| 145 |
+
to run the connectivity test again. Alternatively, the operator may choose to remove the affected cable in a step <part-num-ref name="step">122,</part-num-ref>
|
| 146 |
+
and return to step <part-num-ref name="step 122, and return to step">104</part-num-ref>
|
| 147 |
+
to restart the indicator subroutine. </p>
|
| 148 |
+
<p id="p-25" num="25">[0021] Another embodiment of the present invention provides a method for the automated reconnection of network components according to a desired firmware configuration map after the components have been disconnected in order to remove and replace a network subsystem while the network remains in operation (i.e., a hot swap). In a preferred embodiment, the component requiring reconnection is a network cable and the network subsystem being replaced is a network board. The end of the cable requiring reconnection has been disconnected from a connector mounted on the board identified for replacement, while the other end of the cable remains attached to an unaffected network board. The selected board is replaced in a procedure referred to as a "hot swap" because the network system remains in operation while the affected cable end is disconnected and the board is removed and replaced.</p>
|
| 149 |
+
<p id="p-26" num="26">[0022] Figure 3 is a flow chart of a method for the guided reconnection of a network cable while the network remains in operation. In a step <part-num-ref name="step">200,</part-num-ref>
|
| 150 |
+
a system management utility is provided with at least one firmware configuration map. A firmware configuration map is selected that provides the desired cable connection configuration through the system management utility interface in a step <part-num-ref name="step">202.</part-num-ref>
|
| 151 |
+
The selected firmware configuration map is narrowed to the cable-connection path related to the recently replaced board in a step <part-num-ref name="step">204.</part-num-ref>
|
| 152 |
+
</p>
|
| 153 |
+
<p id="p-27" num="27">[0023] The indicator subroutine of the active firmware configuration map is accessed in a step <part-num-ref name="step">206</part-num-ref>
|
| 154 |
+
then and prompted in a step <part-num-ref name="step">208</part-num-ref>
|
| 155 |
+
to activate an indicator located at the cable reconnection location associated with the replaced board. </p>
|
| 156 |
+
<p id="p-28" num="28">Additionally, an indicator is activated at the connection point for the opposite end <boundary-data type="header">145394.04<confidence value="5">/</confidence>
|
| 157 |
+
2162.44900 </boundary-data>
|
| 158 |
+
<page-break num="7"/>
|
| 159 |
+
<boundary-data type="header">200500432</boundary-data>
|
| 160 |
+
<boundary-data type="header">
|
| 161 |
+
<confidence value="8">7</confidence>
|
| 162 |
+
</boundary-data>
|
| 163 |
+
of the affected cable. The activation of indicators at the fixed end of an affected cable and the desired reconnection point further guides the operator during the reconnection process. The indicator in this embodiment is an LED light source. </p>
|
| 164 |
+
<p id="p-29" num="29">One further aspect of the present embodiment involves assigning color codes to the LED light source during the indicator subroutine (such as yellow) and additionally flashing the LED light source to further direct the desired cable connection configuration. The cable is reconnected at the location corresponding to the activated indicator in a step <part-num-ref name="step">216,</part-num-ref>
|
| 165 |
+
typically at the empty connector on the replaced board. </p>
|
| 166 |
+
<p id="p-30" num="30">[0024] In a step <part-num-ref name="step">212,</part-num-ref>
|
| 167 |
+
the connectivity subroutine of the active firmware configuration map is accessed, which initiates an electrical test to determine whether a valid connection has been made for the desired cable connection path, and that the desired connection path has been maintained for an established period of time. If the proper connectivity is confirmed in a step <part-num-ref name="step">214,</part-num-ref>
|
| 168 |
+
a message is sent to the system management utility and the indicator is directed to change its state in a step <part-num-ref name="step">216.</part-num-ref>
|
| 169 |
+
In one embodiment, the indicator is an LED light source, and a successful connectivity test results in the LED light source illuminating a steady green color light. </p>
|
| 170 |
+
<p id="p-31" num="31">[0025] If, during step 214, the connectivity test determines that according to the active firmware configuration map an improper cable connection has been made, the indicator at the erroneous connection point changes state to show the incorrect connection in a step <part-num-ref name="step">218.</part-num-ref>
|
| 171 |
+
The state change of the indicator can mean either that the cable was not properly inserted such that a workable electrical connection was formed, or that the cable was inserted at the wrong location. </p>
|
| 172 |
+
<p id="p-32" num="32">Upon notification of an incorrect connection, the operator has the option of proceeding to a step <part-num-ref name="step">220,</part-num-ref>
|
| 173 |
+
in which the connection is fixed so that a proper electrical connection is made, and returning to step <part-num-ref name="proper electrical connection is made, and returning to step">212</part-num-ref>
|
| 174 |
+
to run the connectivity test again. Alternatively, the operator may choose to remove the affected cable in a step <part-num-ref name="step">222,</part-num-ref>
|
| 175 |
+
and return to step <part-num-ref name="step 222, and return to step">206</part-num-ref>
|
| 176 |
+
to restart the indicator subroutine. </p>
|
| 177 |
+
<p id="p-33" num="33">[0026] In a step <part-num-ref name="step">224,</part-num-ref>
|
| 178 |
+
the indicator subroutine searches for additional cable reconnection points that are required in the active firmware configuration map. If more reconnection points within the active firmware configuration map are <boundary-data type="header">145394.04/2162.44900</boundary-data>
|
| 179 |
+
<page-break num="8"/>
|
| 180 |
+
<boundary-data type="header">200500432</boundary-data>
|
| 181 |
+
<boundary-data type="header">
|
| 182 |
+
<confidence value="8">8</confidence>
|
| 183 |
+
</boundary-data>
|
| 184 |
+
identified, the method returns to step <part-num-ref name="method returns to step">204</part-num-ref>
|
| 185 |
+
where the firmware configuration map is again narrowed to the affected cable connection path. The indicator and connectivity subroutines are repeated for each affected cable connection path in the firmware configuration map affected by a board replacement, and further for each varied firmware configuration map loaded in the system management utility. </p>
|
| 186 |
+
<p id="p-34" num="34">If no additional required cable reconnections are detected in step 224, the system management utility tests the functionality of all the affected boards and associated cable connection paths replaced as a result of the hot swap in a step <part-num-ref name="step">226.</part-num-ref>
|
| 187 |
+
</p>
|
| 188 |
+
<p id="p-35" num="35">[0027] Another embodiment of the present invention involves a method for the automated or guided removal and installation of network components, followed by a verification of affected network component connection configurations that are utilized in highly available (HA) systems or in scaleable multi-processor (SMP) systems. HA systems are designed to incorporate failover and re-route paths between interconnected redundant system components. In a HA system, if one of the redundant components fails, the interconnection between the components allows the system to failover to another operable component. Cable form the interconnects in a HA system, and therefore must be accurately identified during replacement and upgrade procedures to prevent crashing the entire system.</p>
|
| 189 |
+
<p id="p-36" num="36">[0028<confidence value="5">]</confidence>
|
| 190 |
+
Similarly, SMP systems are designed to incorporate failover and re-route paths, which allow for ease of upgrade and expansion. SMP consist of a system architecture where multiple processors are interconnected and operate as a single system. The interconnection between processors is accomplished through cables, again highlighting the importance of accurately selecting cable connections for modification. The configurability of an SMP system is complicated by the cabled systems as cables will need to be moved, disconnected, and reconnected during the addition of network subsystems or other manners of reconfiguration. </p>
|
| 191 |
+
<p id="p-37" num="37">[0029] In the framework of a HA system or SMP system, a scenario may arise where there is a need to disconnect a cable to enable the upgrade or replacement of the cable or other existing network system components with newer versions of the same components, and then reconnect the cable. In the <boundary-data type="header">145394.04/2162.44900</boundary-data>
|
| 192 |
+
<page-break num="9"/>
|
| 193 |
+
<boundary-data type="header">200500432</boundary-data>
|
| 194 |
+
<boundary-data type="header">
|
| 195 |
+
<confidence value="8">9</confidence>
|
| 196 |
+
</boundary-data>
|
| 197 |
+
framework of a SMP system, a scenario may arise where the fundamental cable connectivity configuration needs to be altered to facilitate a network system reconfiguration. In both scenarios, it is important to correctly deal with cable connections in order to avoid crashing the entire associated system. A method for dealing with the upgrade/replacement scenario is shown in the flow chart depicted in Figure 4A-B. A method for dealing with the reconfiguration scenario is shown in the flow chart depicted in Figure 5A-B. </p>
|
| 198 |
+
<p id="p-38" num="38">[0030] Referring now to Figure 4A-B, a flow chart of a method for the automated or guided upgrade or replacement of a cabled network system is shown. In an embodiment according to the present invention, the system management utility is provided with at least one firmware configuration map in a step <part-num-ref name="step">300.</part-num-ref>
|
| 199 |
+
The system management utility is placed in an upgrade function and an upgrade firmware configuration map is selected in a step <part-num-ref name="step">302.</part-num-ref>
|
| 200 |
+
The system management utility then accesses disconnection location and sequence information from the indicator subroutine of the active firmware configuration map in a step <part-num-ref name="step">304.</part-num-ref>
|
| 201 |
+
</p>
|
| 202 |
+
<p id="p-39" num="39">[0031] In a step <part-num-ref name="step">306,</part-num-ref>
|
| 203 |
+
the indicator subroutine causes the indicator at the disconnection location to become illuminated. In the present embodiment, the indicator subroutine directs the LED light source at the cable disconnection location to flash and display yellow. The operator disconnects the cable end identified for disconnection by the activated indicator in a step <part-num-ref name="step">308.</part-num-ref>
|
| 204 |
+
The connectivity test subroutine is the accessed in a step <part-num-ref name="step">310</part-num-ref>
|
| 205 |
+
and initiates an electrical connectivity test at the cable disconnection location. When the connectivity test establishes that the correct cable has been disconnected in a step <part-num-ref name="step">312</part-num-ref>
|
| 206 |
+
in accordance with the disconnection location and sequence instructions, and that the disconnection has been maintained for a sufficient period of time, the system management utility is alerted. The system management utility directs the indicator subroutine to change the indicator at the cable disconnection location in a step <part-num-ref name="step">314</part-num-ref>
|
| 207 |
+
to indicate a proper cable disconnection. </p>
|
| 208 |
+
<p id="p-40" num="40">[0032] If the connectivity test in run in step <part-num-ref name="connectivity test in run in step">310</part-num-ref>
|
| 209 |
+
determines in step <part-num-ref name="determines in step">312</part-num-ref>
|
| 210 |
+
that the cable disconnection was performed improperly, the connectivity subroutine messages the management utility, which directs the indicator subroutine to <boundary-data type="header">145394.04<confidence value="5">/</confidence>
|
| 211 |
+
2162.44900 </boundary-data>
|
| 212 |
+
<page-break num="10"/>
|
| 213 |
+
<boundary-data type="header">200500432</boundary-data>
|
| 214 |
+
<boundary-data type="header">
|
| 215 |
+
<confidence value="88">10</confidence>
|
| 216 |
+
</boundary-data>
|
| 217 |
+
activate the indicator at the cable connection location to indicate the error by an alternative indicator display in a step <part-num-ref name="step">318.</part-num-ref>
|
| 218 |
+
In the present embodiment, the error is indicated by the LED light source at the erroneous connection point is illuminated a steady red color. The operator then replaces the last cable disconnected in error at the connection point where the error indicator is illuminated in a step <part-num-ref name="step">320.</part-num-ref>
|
| 219 |
+
</p>
|
| 220 |
+
<p id="p-41" num="41">The process repeats upon reconnection of the improperly disconnected cable beginning again with step <part-num-ref name="improperly disconnected cable beginning again with step">304.</part-num-ref>
|
| 221 |
+
</p>
|
| 222 |
+
<p id="p-42" num="42">[0033] The system management utility then determines if there are more cable locations identified for disconnection by the active firmware configuration map in a step <part-num-ref name="step">316.</part-num-ref>
|
| 223 |
+
If more disconnection locations are identified, the method returns to step <part-num-ref name="method returns to step">304</part-num-ref>
|
| 224 |
+
and the subsequent steps detailed above are repeated until all cables identified for disconnection have been properly disconnected. The system components associated with the disconnected cables may then be safely removed and replaced as the upgrade firmware configuration map or reconfiguration map requires. </p>
|
| 225 |
+
<p id="p-43" num="43">[0034] When the connectivity subroutine identifies no additional cable disconnection locations in step <part-num-ref name="connectivity subroutine identifies no additional cable disconnection locations in step">316,</part-num-ref>
|
| 226 |
+
the system management utility accesses the cable connection location indicator subroutine from the upgrade firmware configuration map in a step <part-num-ref name="step">322.</part-num-ref>
|
| 227 |
+
The indicator subroutine activates the indicator cue located at the desired connection point in a step <part-num-ref name="step">324.</part-num-ref>
|
| 228 |
+
In the present embodiment, the indicator cue is an LED that flashes yellow to indicate both connectors associated with a given cable for the desired cable connection path. </p>
|
| 229 |
+
<p id="p-44" num="44">In a step <part-num-ref name="step">326,</part-num-ref>
|
| 230 |
+
the operator is then directed to insert the cable end at the indicated connection location(s). </p>
|
| 231 |
+
<p id="p-45" num="45">[0035] In a step <part-num-ref name="step">328,</part-num-ref>
|
| 232 |
+
the system management utility accesses the connectivity subroutine and performs and electrical test to check for a proper connection for a given cable connection path. If the connectivity subroutine determines that a valid connection has been made and maintained for a sufficient time in a step <part-num-ref name="step">330,</part-num-ref>
|
| 233 |
+
the connectivity subroutine alerts the system management utility, which then directs the indicator subroutine to activate the indicator cue at the confirmed connection point in a step <part-num-ref name="step">332.</part-num-ref>
|
| 234 |
+
In the present embodiment, the indicator cue is an LED which is illuminated a steady green color to indicate a proper connection. </p>
|
| 235 |
+
<boundary-data type="header">145394.04<confidence value="5">/</confidence>
|
| 236 |
+
2162.44900 </boundary-data>
|
| 237 |
+
<boundary-data type="header">200500432</boundary-data>
|
| 238 |
+
<boundary-data type="header">
|
| 239 |
+
<confidence value="88">11</confidence>
|
| 240 |
+
</boundary-data>
|
| 241 |
+
<p id="p-46" num="46">
|
| 242 |
+
<page-break num="11"/>
|
| 243 |
+
[0036] If, during step 330, the connectivity test determines that a proper cable connection has not been made according to the active firmware configuration map, the indicator cue at the erroneous connection point is activated to show the incorrect connection in a step <part-num-ref name="step">336.</part-num-ref>
|
| 244 |
+
In the present embodiment, an LED is used as the indicator cue, and is directed to flash red at the improper connection point. </p>
|
| 245 |
+
<p id="p-47" num="47">The indicator can mean either that the cable was not properly inserted such that a workable electrical connection was formed, or that the cable was inserted at the wrong location. Upon notification of an incorrect connection, the operator is directed to proceed to a step <part-num-ref name="step">338,</part-num-ref>
|
| 246 |
+
in which the connection is fixed so that a proper electrical connection is made, and then returning to step <part-num-ref name="proper electrical connection is made, and then returning to step">328.</part-num-ref>
|
| 247 |
+
</p>
|
| 248 |
+
<p id="p-48" num="48">[0037] Once the present connection is indicated as correctly made in step <part-num-ref name="present connection is indicated as correctly made in step">332,</part-num-ref>
|
| 249 |
+
the system management utility determines is more connections are required by the active firmware configuration map in a step <part-num-ref name="step">334.</part-num-ref>
|
| 250 |
+
If additional connections are identified, the system management utility returns to step <part-num-ref name="system management utility returns to step">322.</part-num-ref>
|
| 251 |
+
If no additional connections are identified by the system management utility in step <part-num-ref name="system management utility in step">334,</part-num-ref>
|
| 252 |
+
the system management utility tests the functionality of all the components installed as a result of the upgrade in a step <part-num-ref name="step">340.</part-num-ref>
|
| 253 |
+
</p>
|
| 254 |
+
<p id="p-49" num="49">[0038] Referring now to Figure 5A-B, a flow chart of a method for the automated or guided reconfiguration of a cabled network system is shown. The reconfiguration involves a fundamental cable connectivity alteration and an associated re-mapping of the configuration guidelines. It is desirable that the reconfiguration is conducted in a way that minimizes network system disruption with respect to cables configuration paths that are changed and cable configuration paths that remain unaffected.</p>
|
| 255 |
+
<p id="p-50" num="50">[0039] In an embodiment according to the present invention, the system management utility is provided with at least one firmware configuration map in a step <part-num-ref name="step">400.</part-num-ref>
|
| 256 |
+
The system management utility is placed in a reconfiguration function and a new firmware configuration map is selected in a step <part-num-ref name="step">402.</part-num-ref>
|
| 257 |
+
An "old" firmware configuration map is known by the management utility and was used to configure the network system in its current state. The management utility then compares the new and old firmware configuration maps in a step <part-num-ref name="step">404</part-num-ref>
|
| 258 |
+
to identify <boundary-data type="header">145394.04/21<confidence value="5">6</confidence>
|
| 259 |
+
2.44900 </boundary-data>
|
| 260 |
+
<page-break num="12"/>
|
| 261 |
+
<boundary-data type="header">200500432</boundary-data>
|
| 262 |
+
<boundary-data type="header">
|
| 263 |
+
<confidence value="88">12</confidence>
|
| 264 |
+
</boundary-data>
|
| 265 |
+
the differences between the two configurations and to discover which cables must be changed. </p>
|
| 266 |
+
<p id="p-51" num="51">[0040] In a step <part-num-ref name="step">404,</part-num-ref>
|
| 267 |
+
the cables to be changed are identified and called into a sequential list for disconnection. The sequential list for disconnection is then correlated with two subroutines embedded in the selected firmware configuration map: the indicator subroutine and the connectivity subroutine. The indicator subroutine is accessed in a step <part-num-ref name="step">408.</part-num-ref>
|
| 268 |
+
In a step <part-num-ref name="step">410,</part-num-ref>
|
| 269 |
+
the indicator subroutine causes the indicators associated with the connectors at both ends of the cable to become illuminated if both ends of the cable are to be disconnected. </p>
|
| 270 |
+
<p id="p-52" num="52">Alternatively, the indicator subroutine may only direct the indicator associated with one of the connectors to be illuminated if only one cable end is to be disconnected. In the present embodiment, the indicator subroutine directs the LED light source indicator at the cable connection location desired to be disconnected to flash and display yellow. The operator disconnects the cable end identified for disconnection by the activated indicator in a step <part-num-ref name="step">412.</part-num-ref>
|
| 271 |
+
</p>
|
| 272 |
+
<p id="p-53" num="53">[0041] The connectivity test subroutine is then accessed in a step <part-num-ref name="step">414</part-num-ref>
|
| 273 |
+
and directs electrical connectivity tests to be run on the cable connection locations identified for disconnection. When the connectivity test establishes that the correct cable has been disconnected in accordance with the new firmware configuration map in a step <part-num-ref name="step">416,</part-num-ref>
|
| 274 |
+
and that the disconnection has been maintained for a valid period of time, the connectivity subroutine messages the management utility, which directs the indicator subroutine to change the indicator at the cable connection location in a step <part-num-ref name="step">418.</part-num-ref>
|
| 275 |
+
In the present embodiment, the LED light source indicator is illuminated the color green to indicate that the proper component has been disconnected. </p>
|
| 276 |
+
<p id="p-54" num="54">[0042] If the connectivity test in run in step <part-num-ref name="connectivity test in run in step">414</part-num-ref>
|
| 277 |
+
determines in step <part-num-ref name="determines in step">416</part-num-ref>
|
| 278 |
+
that the cable disconnection was performed improperly, the connectivity subroutine messages the management utility, which directs the indicator subroutine to activate the indicator at the cable connection location to indicate the error by an alternative indicator display in a step <part-num-ref name="step">422.</part-num-ref>
|
| 279 |
+
In the present embodiment, the error is indicated by the LED light source at the erroneous connection point is illuminated a steady red color. The operator then replaces the last component disconnected <boundary-data type="header">145394.04/2162.44900</boundary-data>
|
| 280 |
+
<page-break num="13"/>
|
| 281 |
+
<boundary-data type="header">200500432</boundary-data>
|
| 282 |
+
<boundary-data type="header">
|
| 283 |
+
<confidence value="88">13</confidence>
|
| 284 |
+
</boundary-data>
|
| 285 |
+
in error at the connection point where the error indicator is illuminated in a step <part-num-ref name="step">424.</part-num-ref>
|
| 286 |
+
The process repeats upon reconnection of the improperly disconnected component beginning again with step <part-num-ref name="improperly disconnected component beginning again with step">408.</part-num-ref>
|
| 287 |
+
</p>
|
| 288 |
+
<p id="p-55" num="55">[0043] The system management utility then determines if there are more component locations identified for disconnection by the active firmware configuration map in a step <part-num-ref name="step">420.</part-num-ref>
|
| 289 |
+
If more disconnection locations are identified, the method returns to step <part-num-ref name="method returns to step">408</part-num-ref>
|
| 290 |
+
and the subsequent steps detailed above are repeated until all cables identified for disconnection have been properly disconnected. The system components associated with the disconnected cables may then be safely removed and replaced as the upgrade firmware configuration map or reconfiguration map requires. </p>
|
| 291 |
+
<p id="p-56" num="56">[00<confidence value="66">44</confidence>
|
| 292 |
+
] When the connectivity subroutine identifies no additional cable disconnection locations in step <part-num-ref name="connectivity subroutine identifies no additional cable disconnection locations in step">420,</part-num-ref>
|
| 293 |
+
the system management utility accesses the connectivity subroutine for the new firmware configuration map in a step <part-num-ref name="step">426.</part-num-ref>
|
| 294 |
+
</p>
|
| 295 |
+
<p id="p-57" num="57">The connectivity subroutine directs an electrical test of all component connections in a step <part-num-ref name="step">428</part-num-ref>
|
| 296 |
+
in order to identify any incorrect connections based on the new firmware configuration map. If an incorrect component connection is identified in a step <part-num-ref name="step">430,</part-num-ref>
|
| 297 |
+
the connectivity subroutine alerts the system management utility, which in turn directs the indicator subroutine to activate the indicator cue at the error point in a step <part-num-ref name="step">432.</part-num-ref>
|
| 298 |
+
In the present embodiment, when an incorrect component connection is detected, the indicator cue is made to flash the color red. The indicator cue continues to flash red until the operator disconnects the improperly connected component in a step <part-num-ref name="step">434.</part-num-ref>
|
| 299 |
+
The system management utility then directs the connectivity subroutine to test component connections again in a repeat of step <part-num-ref name="repeat of step">428.</part-num-ref>
|
| 300 |
+
</p>
|
| 301 |
+
<p id="p-58" num="58">[0045] When the connectivity test in step <part-num-ref name="connectivity test in step">430</part-num-ref>
|
| 302 |
+
identifies no incorrect component connections, the system management utility accesses the component connection location indicator subroutine from the new firmware configuration map in a step <part-num-ref name="step">436.</part-num-ref>
|
| 303 |
+
The indicator subroutine activates the indicator cue located at the desired connection point in a step <part-num-ref name="step">438.</part-num-ref>
|
| 304 |
+
In the present embodiment, the indicator cue is an LED that flashes yellow to indicate both connectors associated with a given <boundary-data type="header">145394.04<confidence value="5">/</confidence>
|
| 305 |
+
2162.44900 </boundary-data>
|
| 306 |
+
<page-break num="14"/>
|
| 307 |
+
<boundary-data type="header">200500432</boundary-data>
|
| 308 |
+
<boundary-data type="header">
|
| 309 |
+
<confidence value="88">14</confidence>
|
| 310 |
+
</boundary-data>
|
| 311 |
+
cable for the desired cable connection path. In a step <part-num-ref name="step">440,</part-num-ref>
|
| 312 |
+
the operator is then directed to insert the component at the indicated connection location(s). </p>
|
| 313 |
+
<p id="p-59" num="59">[0046] <confidence value="5">I</confidence>
|
| 314 |
+
n a step <part-num-ref name="step">442,</part-num-ref>
|
| 315 |
+
the system management utility accesses the connectivity subroutine and performs and electrical test to check for a proper connection for a given cable connection path. If the connectivity subroutine determines that a valid connection has been made and maintained for a sufficient time in a step <part-num-ref name="step">444,</part-num-ref>
|
| 316 |
+
the connectivity subroutine alerts the system management utility, which then directs the indicator subroutine to activate the indicator cue at the confirmed connection point in a step <part-num-ref name="step">450.</part-num-ref>
|
| 317 |
+
In the present embodiment, the indicator cue is an LED which is illuminated a steady green color to indicate a proper connection. </p>
|
| 318 |
+
<p id="p-60" num="60">[0047] If, during step 444, the connectivity test determines that a proper cable connection has not been made according to the active firmware configuration map, the indicator cue at the erroneous connection point is activated to show the incorrect connection in a step <part-num-ref name="step">446.</part-num-ref>
|
| 319 |
+
In the present embodiment, an LED is used as the indicator cue, and is directed to flash red at the improper connection point. </p>
|
| 320 |
+
<p id="p-61" num="61">The indicator can mean either that the component was not properly inserted such that a workable electrical connection was formed, or that the component was inserted at the wrong location. Upon notification of an incorrect connection, the operator is directed to proceed to a step <part-num-ref name="step">448,</part-num-ref>
|
| 321 |
+
in which the connection is fixed so that a proper electrical connection is made, and then returning to step <part-num-ref name="proper electrical connection is made, and then returning to step">442.</part-num-ref>
|
| 322 |
+
</p>
|
| 323 |
+
<p id="p-62" num="62">[0048] Once the present connection is indicated as correctly made in step <part-num-ref name="present connection is indicated as correctly made in step">450,</part-num-ref>
|
| 324 |
+
the system management utility determines is more connections are required by the active firmware configuration map in a step <part-num-ref name="step">452.</part-num-ref>
|
| 325 |
+
If additional connections are identified, the system management utility returns to step <part-num-ref name="system management utility returns to step">436.</part-num-ref>
|
| 326 |
+
If no additional connections are identified by the system management utility in step <part-num-ref name="system management utility in step">452,</part-num-ref>
|
| 327 |
+
the system management utility accesses the connectivity subroutine and commences a final electrical test of all new component connections against the new firmware configuration map in a step <part-num-ref name="step">454.</part-num-ref>
|
| 328 |
+
If a connection error is identified by the connectivity subroutine in a step <part-num-ref name="step">456,</part-num-ref>
|
| 329 |
+
the system management utility is alerted, and the indicator subroutine is directed to activate the indicator cue at the improper connection point in a step <part-num-ref name="step">460.</part-num-ref>
|
| 330 |
+
In the present embodiment, the indicator cue is directed to flash red until the improper connection is removed. </p>
|
| 331 |
+
<boundary-data type="header">145394.04<confidence value="5">/</confidence>
|
| 332 |
+
2162.44900 </boundary-data>
|
| 333 |
+
<boundary-data type="header">200500432</boundary-data>
|
| 334 |
+
<boundary-data type="header">
|
| 335 |
+
<confidence value="88">15</confidence>
|
| 336 |
+
</boundary-data>
|
| 337 |
+
<p id="p-63" num="63">
|
| 338 |
+
<page-break num="15"/>
|
| 339 |
+
[0049] If no connection errors are identified in step 456, all indicator cues associated with the affected component connections are activated in a step <part-num-ref name="step">458.</part-num-ref>
|
| 340 |
+
</p>
|
| 341 |
+
<p id="p-64" num="64">In the present embodiment, the indicators are steady green when all components have been tested and verified as correctly connected.</p>
|
| 342 |
+
<p id="p-65" num="65">[0050] The above discussion is meant to be illustrative of the principles and various embodiments of the present invention. Numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. For example, the methods described in this application largely deal with network cable connections and configurations.</p>
|
| 343 |
+
<p id="p-66" num="66">However, this invention contemplates that the automated identification and verification system is adaptable to other network system components, such as card components. It is intended that the following claims be interpreted to embrace all such variations and modifications.</p>
|
| 344 |
+
<boundary-data type="header">145394.04<confidence value="5">/</confidence>
|
| 345 |
+
2162.44900 </boundary-data>
|
| 346 |
+
</description>
|
| 347 |
+
</us-patent-application>
|
| 348 |
+
|
applicant/11399872.xml
ADDED
|
@@ -0,0 +1,29 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11399872</doc-number>
|
| 8 |
+
<date>2009-01-02</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="2">1</confidence>
|
| 15 |
+
N THE SPECIFICATION Please replace the paragraph beginning on page <part-num-ref name="paragraph beginning on page">1,</part-num-ref>
|
| 16 |
+
line <part-num-ref name="paragraph beginning on page 1, line">12,</part-num-ref>
|
| 17 |
+
with the following replacement paragraph: </p>
|
| 18 |
+
<p id="p-2" num="2">The present application is also related to U.S. Patent Application <confidence value="5585662522665">Atrney-Doeket</confidence>
|
| 19 |
+
<confidence value="655">No.</confidence>
|
| 20 |
+
</p>
|
| 21 |
+
<p id="p-3" num="3">
|
| 22 |
+
<confidence value="44226686562124">Srivastava41'6</confidence>
|
| 23 |
+
Serial No. 11/399,726, entitled "Method And Apparatus For Delivering Subscription Service Content To Roaming Users," which is filed concurrently herewith and incorporated by reference herein. </p>
|
| 24 |
+
<p id="p-4" num="4">
|
| 25 |
+
<confidence value="8">2</confidence>
|
| 26 |
+
</p>
|
| 27 |
+
</description>
|
| 28 |
+
</us-patent-application>
|
| 29 |
+
|
applicant/11456230.xml
ADDED
|
@@ -0,0 +1,428 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11456230</doc-number>
|
| 8 |
+
<date>2006-07-10</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">METHOD AND APPARATUS TO ORGANIZE FI<confidence value="8">L</confidence>
|
| 14 |
+
ES BASED ON DOWNLOAD </heading>
|
| 15 |
+
<heading id="h-2">LOCATIONS</heading>
|
| 16 |
+
<heading id="h-3">BACKGROUND OF THE INVENTION</heading>
|
| 17 |
+
<p id="p-1" num="1">1. Field of the Invention:</p>
|
| 18 |
+
<p id="p-2" num="2">[0001] The present invention relates generally to an improved data processing system and in particular a method and apparatus for organizing data. Still more particularly, the present invention relates to a computer implemented method, apparatus, and computer usable program code for organizing files based on the download location of the files.</p>
|
| 19 |
+
<p id="p-3" num="3">2. Description of the Related Art:</p>
|
| 20 |
+
<p id="p-4" num="4">[0002] With the Internet, any computer may communicate with any other computer over the Internet using a variety of languages. These languages also are referred to as protocols. The set of protocols used on the Internet is called transmission control protocol/Internet protocol (TCP/IP). The Internet has revolutionized communications in commerce. For many users, e-mail is a widely used format to communicate over the Internet. Additionally, data is often transferred over the Internet. Users may obtain programs as well as data files over the Internet.</p>
|
| 21 |
+
<p id="p-5" num="5">The transfer of this type of data is typically facilitated through the hypertext transfer protocol (HTTP)<confidence value="5">.</confidence>
|
| 22 |
+
</p>
|
| 23 |
+
<p id="p-6" num="6">[0003] In downloading applications and files, a user may download files from various sources. One common occurrence of downloading is when a user downloads a plug-in to access websites or when a user installs programs, such as games, <boundary-data type="header">
|
| 24 |
+
<confidence value="8">1</confidence>
|
| 25 |
+
</boundary-data>
|
| 26 |
+
<boundary-data type="header">Docket No. AUS920<confidence value="555555884">060414US1</confidence>
|
| 27 |
+
</boundary-data>
|
| 28 |
+
<page-break num="2"/>
|
| 29 |
+
freeware, and shareware from different sites on the Internet. </p>
|
| 30 |
+
<p id="p-7" num="7">[0004] Currently, these files are typically downloaded into a particular directory or folder for installation.</p>
|
| 31 |
+
<p id="p-8" num="8">When these files are downloaded, they are not organized based on the particular site from which the files were obtained. For example, operating system patches from an operating system vendor are downloaded into a folder designated for the particular operating system.</p>
|
| 32 |
+
<p id="p-9" num="9">Identifying the downloaded files based on the location from where they were downloaded is currently unavailable.</p>
|
| 33 |
+
<p id="p-10" num="10">[0005] Often times, however, a business will repackage these files specifically for use by its employees or customers. When the operating system files are downloaded from the business rather than the operating system vendor, these files are typically placed into the folder for the operating system. As a result, identification of the source from where the files were received is unavailable.</p>
|
| 34 |
+
<p id="p-11" num="11">As another example, plug-ins often may be downloaded from different sites other than the vendor or creator of the plug-in. These plug-ins are typically organized based on the vendor rather than the source of the plug-in. When the source from which the files were downloaded is unknown, the user is often unable to determine whether the files should be trusted. For example, files downloaded from an employer's site are considered to be trusted while files downloaded from a freeware site may be less trustworthy.</p>
|
| 35 |
+
<p id="p-12" num="12">Knowing the download location of a file is often desirable because a user may not want to run or use files that are from unknown or questionable sources when at work or connected to a network for the user's employer. The user <boundary-data type="header">
|
| 36 |
+
<confidence value="8">2</confidence>
|
| 37 |
+
</boundary-data>
|
| 38 |
+
<boundary-data type="header">Docket No. AUS920<confidence value="555555685">060414US1</confidence>
|
| 39 |
+
</boundary-data>
|
| 40 |
+
<page-break num="3"/>
|
| 41 |
+
may wish to run a monitoring program or firewall when a file from a questionable or unknown source is executed to ensure that malicious processes do not run or are stopped. </p>
|
| 42 |
+
<boundary-data type="header">
|
| 43 |
+
<confidence value="8">3</confidence>
|
| 44 |
+
</boundary-data>
|
| 45 |
+
<boundary-data type="header">Docket No. AUS<confidence value="888858555655">920060414US1</confidence>
|
| 46 |
+
</boundary-data>
|
| 47 |
+
<heading id="h-4">SUMMARY OF THE INVENTION</heading>
|
| 48 |
+
<p id="p-13" num="13">
|
| 49 |
+
<page-break num="4"/>
|
| 50 |
+
[0006] The illustrative embodiments provide a computer implemented method, apparatus, and computer usable program code for managing files. A set of origination locations for a plurality of files is identified to form a set of identified origination locations in response to a request to view the plurality of files. Each origination location in the set of identified origination locations identifies a location from which a file in the plurality of files has been received. A representation of the plurality of files is presented using a set of graphical indicators based on the set of identified origination locations. </p>
|
| 51 |
+
<boundary-data type="header">
|
| 52 |
+
<confidence value="5">4</confidence>
|
| 53 |
+
</boundary-data>
|
| 54 |
+
<boundary-data type="header">Docket No. A<confidence value="16177116">US920ii0</confidence>
|
| 55 |
+
<confidence value="1612111">.4J'.._</confidence>
|
| 56 |
+
</boundary-data>
|
| 57 |
+
<heading id="h-5">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 58 |
+
<p id="p-14" num="14">
|
| 59 |
+
<page-break num="5"/>
|
| 60 |
+
[0007] The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further objectives and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein: </p>
|
| 61 |
+
<p id="p-15" num="15">[0008] Figure 1 depicts a pictorial representation of a network of data processing systems in which illustrative embodiments may be implemented;</p>
|
| 62 |
+
<p id="p-16" num="16">[0009] Figure 2 is a block diagram of a data processing system in which illustrative embodiments may be implemented;</p>
|
| 63 |
+
<p id="p-17" num="17">[0010] Figure 3 is a diagram illustrating components used for identifying the location of files in accordance with an illustrative embodiment;</p>
|
| 64 |
+
<p id="p-18" num="18">[0011] Figure 4 is a diagram illustrating components used for viewing files based on download locations in accordance with an illustrative embodiment;</p>
|
| 65 |
+
<p id="p-19" num="19">[0012] Figures 5A and 5B are diagrams illustrating a display of files in accordance with an illustrative embodiment;</p>
|
| 66 |
+
<p id="p-20" num="20">[0013] Figure 6 is a diagram illustrating a designation of locations for files in accordance with an illustrative embodiment;</p>
|
| 67 |
+
<p id="p-21" num="21">[0014] Figure 7 is a diagram illustrating a listing of files sorted based on download location in accordance with an illustrative embodiment;</p>
|
| 68 |
+
<boundary-data type="header">
|
| 69 |
+
<confidence value="8">5</confidence>
|
| 70 |
+
</boundary-data>
|
| 71 |
+
<boundary-data type="header">Docket No. AUS<confidence value="686465565644">920C60414US1</confidence>
|
| 72 |
+
</boundary-data>
|
| 73 |
+
<p id="p-22" num="22">
|
| 74 |
+
<page-break num="6"/>
|
| 75 |
+
[0015] Figure 8 is a flowchart of a process to identify and associate location data with downloaded files in accordance with an illustrative embodiment; and [0016] Figure 9 is a flowchart of a process to display a set of files using the associated location data in accordance with an illustrative embodiment. </p>
|
| 76 |
+
<boundary-data type="header">
|
| 77 |
+
<confidence value="8">6</confidence>
|
| 78 |
+
</boundary-data>
|
| 79 |
+
<boundary-data type="header">Docket No. <confidence value="668668888555685">AUS920060414US1</confidence>
|
| 80 |
+
</boundary-data>
|
| 81 |
+
<heading id="h-6">DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT</heading>
|
| 82 |
+
<p id="p-23" num="23">
|
| 83 |
+
<page-break num="7"/>
|
| 84 |
+
[0008] With reference now to the figures and in particular with reference to Figures 1-2, exemplary diagrams of data processing environments are provided in which illustrative embodiments may be implemented. It should be appreciated that Figures 1-2 are only exemplary and are not intended to assert or imply any limitation with regard to the environments in which different embodiments may be implemented. Many modifications to the depicted environments may be made. </p>
|
| 85 |
+
<p id="p-24" num="24">[0009] With reference now to the figures, Figure 1 depicts a pictorial representation of a network of data processing systems in which illustrative embodiments may be implemented. Network data processing system <part-num-ref name="network of data processing systems in which illustrative embodiments may be implemented. Network data processing system">100</part-num-ref>
|
| 86 |
+
is a network of computers in which embodiments may be implemented. Network data processing system <part-num-ref name="network of computers in which embodiments may be implemented. Network data processing system">100</part-num-ref>
|
| 87 |
+
contains network <part-num-ref name="contains network">102,</part-num-ref>
|
| 88 |
+
which is the medium used to provide communications links between various devices and computers connected together within network data processing system <part-num-ref name="medium used to provide communications links between various devices and computers connected together within network data processing system">100.</part-num-ref>
|
| 89 |
+
Network <part-num-ref name="medium used to provide communications links between various devices and computers connected together within network data processing system 100. Network">102</part-num-ref>
|
| 90 |
+
may include connections, such as wire, wireless communication links, or fiber optic cables. </p>
|
| 91 |
+
<p id="p-25" num="25">[0010] In the depicted example, server <part-num-ref name="depicted example, server">104</part-num-ref>
|
| 92 |
+
and server <part-num-ref name="and server">106</part-num-ref>
|
| 93 |
+
connect to network <part-num-ref name="connect to network">102</part-num-ref>
|
| 94 |
+
along with storage unit <part-num-ref name="along with storage unit">108.</part-num-ref>
|
| 95 |
+
In addition, clients <part-num-ref name="along with storage unit 108. In addition, clients">110,</part-num-ref>
|
| 96 |
+
<part-num-ref name="along with storage unit 108. In addition, clients 110,">112,</part-num-ref>
|
| 97 |
+
and <part-num-ref name="along with storage unit 108. In addition, clients 110, 112, and">114</part-num-ref>
|
| 98 |
+
connect to network <part-num-ref name="connect to network">102.</part-num-ref>
|
| 99 |
+
</p>
|
| 100 |
+
<p id="p-26" num="26">These clients 110, 112, and 114 may be, for example, personal computers or network computers. In the depicted example, server <part-num-ref name="depicted example, server">104</part-num-ref>
|
| 101 |
+
provides data, such as boot files, operating system images, and applications to clients <part-num-ref name="provides data, such as boot files, operating system images, and applications to clients">110,</part-num-ref>
|
| 102 |
+
<part-num-ref name="provides data, such as boot files, operating system images, and applications to clients 110,">112,</part-num-ref>
|
| 103 |
+
and <part-num-ref name="provides data, such as boot files, operating system images, and applications to clients 110, 112, and">114.</part-num-ref>
|
| 104 |
+
Clients <part-num-ref name="provides data, such as boot files, operating system images, and applications to clients 110, 112, and 114. Clients">110,</part-num-ref>
|
| 105 |
+
<part-num-ref name="provides data, such as boot files, operating system images, and applications to clients 110, 112, and 114. Clients 110,">112,</part-num-ref>
|
| 106 |
+
and <part-num-ref name="provides data, such as boot files, operating system images, and applications to clients 110, 112, and 114. Clients 110, 112, and">114</part-num-ref>
|
| 107 |
+
are clients to <boundary-data type="header">
|
| 108 |
+
<confidence value="8">7</confidence>
|
| 109 |
+
</boundary-data>
|
| 110 |
+
<boundary-data type="header">Docket No. A<confidence value="6586624112242">US9200C0414S1</confidence>
|
| 111 |
+
</boundary-data>
|
| 112 |
+
<page-break num="8"/>
|
| 113 |
+
server <part-num-ref name="are clients to server">104</part-num-ref>
|
| 114 |
+
in this example. Network data processing system <part-num-ref name="in this example. Network data processing system">100</part-num-ref>
|
| 115 |
+
may include additional servers, clients, and other devices not shown. </p>
|
| 116 |
+
<p id="p-27" num="27">[0011] In the depicted example, network data processing system <part-num-ref name="depicted example, network data processing system">100</part-num-ref>
|
| 117 |
+
is the Internet with network <part-num-ref name="Internet with network">102</part-num-ref>
|
| 118 |
+
representing a worldwide collection of networks and gateways that use the Transmission Control Protocol/Internet Protocol (TCP/IP) suite of protocols to communicate with one another. At the heart of the Internet is a backbone of high-speed data communication lines between major nodes or host computers, consisting of thousands of commercial, governmental, educational and other computer systems that route data and messages. Of course, network data processing system <part-num-ref name="backbone of high-speed data communication lines between major nodes or host computers, consisting of thousands of commercial, governmental, educational and other computer systems that route data and messages. Of course, network data processing system">100</part-num-ref>
|
| 119 |
+
also may be implemented as a number of different types of networks, such as for example, an intranet, a local area network (LAN), or a wide area network (WAN). Figure 1 is intended as an example, and not as an architectural limitation for different embodiments. </p>
|
| 120 |
+
<p id="p-28" num="28">[0012] With reference now to Figure 2, a block diagram of a data processing system is shown in which illustrative embodiments may be implemented. Data processing system <part-num-ref name="data processing system is shown in which illustrative embodiments may be implemented. Data processing system">200</part-num-ref>
|
| 121 |
+
is an example of a computer, such as server <part-num-ref name="computer, such as server">104</part-num-ref>
|
| 122 |
+
or client <part-num-ref name="or client">110</part-num-ref>
|
| 123 |
+
in Figure 1, in which computer usable code or instructions implementing the processes may be located for the illustrative embodiments. </p>
|
| 124 |
+
<p id="p-29" num="29">[0013] In the depicted example, data processing system <part-num-ref name="depicted example, data processing system">200</part-num-ref>
|
| 125 |
+
employs a hub architecture including a north bridge and memory controller hub (MCH) <part-num-ref name="north bridge and memory controller hub (MCH)">202</part-num-ref>
|
| 126 |
+
and a south bridge and input/output (I/<confidence value="5">0</confidence>
|
| 127 |
+
) controller hub (ICH) <part-num-ref name="south bridge and input/output (I/0) controller hub (ICH)">204.</part-num-ref>
|
| 128 |
+
Processor <part-num-ref name="south bridge and input/output (I/0) controller hub (ICH) 204. Processor">206,</part-num-ref>
|
| 129 |
+
main memory <part-num-ref name="south bridge and input/output (I/0) controller hub (ICH) 204. Processor 206, main memory">208,</part-num-ref>
|
| 130 |
+
and graphics processor <part-num-ref name="south bridge and input/output (I/0) controller hub (ICH) 204. Processor 206, main memory 208, and graphics processor">210</part-num-ref>
|
| 131 |
+
are coupled to north bridge and memory controller hub <part-num-ref name="are coupled to north bridge and memory controller hub">202.</part-num-ref>
|
| 132 |
+
Graphics <boundary-data type="header">
|
| 133 |
+
<confidence value="8">8</confidence>
|
| 134 |
+
</boundary-data>
|
| 135 |
+
<boundary-data type="header">Docket No. AUS920<confidence value="555555685">060414US1</confidence>
|
| 136 |
+
</boundary-data>
|
| 137 |
+
<page-break num="9"/>
|
| 138 |
+
processor <part-num-ref name="are coupled to north bridge and memory controller hub 202. Graphics processor">210</part-num-ref>
|
| 139 |
+
may be coupled to the MCH through an accelerated graphics port (AGP), for example. </p>
|
| 140 |
+
<p id="p-30" num="30">[0014] In the depicted example, local area network (LAN) adapter <part-num-ref name="depicted example, local area network (LAN) adapter">212</part-num-ref>
|
| 141 |
+
is coupled to south bridge and I/O controller hub <part-num-ref name="is coupled to south bridge and I/O controller hub">204</part-num-ref>
|
| 142 |
+
and audio adapter <part-num-ref name="and audio adapter">216,</part-num-ref>
|
| 143 |
+
keyboard and mouse adapter <part-num-ref name="and audio adapter 216, keyboard and mouse adapter">220,</part-num-ref>
|
| 144 |
+
modem <part-num-ref name="and audio adapter 216, keyboard and mouse adapter 220, modem">222,</part-num-ref>
|
| 145 |
+
read only memory (ROM) <part-num-ref name="and audio adapter 216, keyboard and mouse adapter 220, modem 222, read only memory (ROM)">224,</part-num-ref>
|
| 146 |
+
universal serial bus (USB) ports and other communications ports <part-num-ref name="and audio adapter 216, keyboard and mouse adapter 220, modem 222, read only memory (ROM) 224, universal serial bus (USB) ports and other communications ports">232,</part-num-ref>
|
| 147 |
+
and PCI/P<confidence value="668">CIe</confidence>
|
| 148 |
+
devices <part-num-ref name="and audio adapter 216, keyboard and mouse adapter 220, modem 222, read only memory (ROM) 224, universal serial bus (USB) ports and other communications ports 232, and PCI/PCIe devices">234</part-num-ref>
|
| 149 |
+
are coupled to south bridge and I/O controller hub <part-num-ref name="are coupled to south bridge and I/O controller hub">204</part-num-ref>
|
| 150 |
+
through bus <part-num-ref name="through bus">238,</part-num-ref>
|
| 151 |
+
and hard disk drive (HDD) <part-num-ref name="through bus 238, and hard disk drive (HDD)">226</part-num-ref>
|
| 152 |
+
and CD-ROM drive <part-num-ref name="and CD-ROM drive">230</part-num-ref>
|
| 153 |
+
are coupled to south bridge and I/O controller hub <part-num-ref name="are coupled to south bridge and I/O controller hub">204</part-num-ref>
|
| 154 |
+
through bus <part-num-ref name="through bus">240.</part-num-ref>
|
| 155 |
+
PCI/P<confidence value="66">CI</confidence>
|
| 156 |
+
e devices may include, for example, Ethernet adapters, add-in cards, and PC cards for notebook computers. PCI uses a card bus controller, while P<confidence value="66">CI</confidence>
|
| 157 |
+
e does not. ROM <part-num-ref name="card bus controller, while PCIe does not. ROM">224</part-num-ref>
|
| 158 |
+
may be, for example, a flash binary input/output system (BIOS). Hard disk drive <part-num-ref name="flash binary input/output system (BIOS). Hard disk drive">226</part-num-ref>
|
| 159 |
+
and CD-ROM drive <part-num-ref name="and CD-ROM drive">230</part-num-ref>
|
| 160 |
+
may use, for example, an integrated drive electronics (IDE) or serial advanced technology attachment (SATA) interface. A super I/O (SIO) device <part-num-ref name="super I/O (SIO) device">236</part-num-ref>
|
| 161 |
+
may be coupled to south bridge and I/O controller hub <part-num-ref name="may be coupled to south bridge and I/O controller hub">204.</part-num-ref>
|
| 162 |
+
</p>
|
| 163 |
+
<p id="p-31" num="31">[0015] An operating system runs on processor <part-num-ref name="operating system runs on processor">206</part-num-ref>
|
| 164 |
+
and coordinates and provides control of various components within data processing system <part-num-ref name="and coordinates and provides control of various components within data processing system">200</part-num-ref>
|
| 165 |
+
in Figure 2. The operating system may be a commercially available operating system such as <confidence value="2222222222">Microsoft®</confidence>
|
| 166 |
+
Windows<confidence value="5">®</confidence>
|
| 167 |
+
XP (Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both). An object oriented programming system, such as the <confidence value="66664">JavaM</confidence>
|
| 168 |
+
programming system, may run in conjunction with the operating system and provides calls to the operating system from Java programs or applications executing on data processing system <part-num-ref name="operating system from Java programs or applications executing on data processing system">200</part-num-ref>
|
| 169 |
+
(Java and all Java-based trademarks are <boundary-data type="header">
|
| 170 |
+
<confidence value="8">9</confidence>
|
| 171 |
+
</boundary-data>
|
| 172 |
+
<boundary-data type="header">Docket No. AUS920<confidence value="555555855">060414US1</confidence>
|
| 173 |
+
</boundary-data>
|
| 174 |
+
<page-break num="10"/>
|
| 175 |
+
trademarks of Sun Microsystems, Inc. in the United States, other countries, or both)<confidence value="5">.</confidence>
|
| 176 |
+
</p>
|
| 177 |
+
<p id="p-32" num="32">[0016] Instructions for the operating system, the object- oriented programming system, and applications or programs are located on storage devices, such as hard disk drive <part-num-ref name="object- oriented programming system, and applications or programs are located on storage devices, such as hard disk drive">226,</part-num-ref>
|
| 178 |
+
and may be loaded into main memory <part-num-ref name="object- oriented programming system, and applications or programs are located on storage devices, such as hard disk drive 226, and may be loaded into main memory">208</part-num-ref>
|
| 179 |
+
for execution by processor <part-num-ref name="for execution by processor">206.</part-num-ref>
|
| 180 |
+
The processes of the illustrative embodiments may be performed by processor <part-num-ref name="illustrative embodiments may be performed by processor">206</part-num-ref>
|
| 181 |
+
using computer implemented instructions, which may be located in a memory such as, for example, main memory <part-num-ref name="memory such as, for example, main memory">208,</part-num-ref>
|
| 182 |
+
read only memory <part-num-ref name="memory such as, for example, main memory 208, read only memory">224,</part-num-ref>
|
| 183 |
+
or in one or more peripheral devices. </p>
|
| 184 |
+
<p id="p-33" num="33">[0017] The hardware in Figures 1-2 may vary depending on the implementation. Other internal hardware or peripheral devices, such as flash memory, equivalent non-volatile memory, or optical disk drives and the like, may be used in addition to or in place of the hardware depicted in Figures 1-2. Also, the processes of the illustrative embodiments may be applied to a multiprocessor data processing system.</p>
|
| 185 |
+
<p id="p-34" num="34">[0017] In some illustrative examples, data processing system 200 may be a personal digital assistant (PDA), which is generally configured with flash memory to provide non- volatile memory for storing operating system files and/or user-generated data. A bus system may be comprised of one or more buses, such as a system bus, an I/O bus and a PCI bus. Of course the bus system may be implemented using any type of communications fabric or architecture that provides for a transfer of data between different components or devices attached to the fabric or architecture. A communications unit may include one or more devices used to transmit and receive data, such as a modem or a network adapter. A memory may be, for example, main memory <part-num-ref name="memory may be, for example, main memory">208</part-num-ref>
|
| 186 |
+
or <boundary-data type="header">
|
| 187 |
+
<confidence value="88">10</confidence>
|
| 188 |
+
</boundary-data>
|
| 189 |
+
<boundary-data type="header">Docket No. AUS920<confidence value="555555884">060414US1</confidence>
|
| 190 |
+
</boundary-data>
|
| 191 |
+
<page-break num="11"/>
|
| 192 |
+
a cache such as found in north bridge and memory controller hub <part-num-ref name="cache such as found in north bridge and memory controller hub">202.</part-num-ref>
|
| 193 |
+
A processing unit may include one or more processors or CPUs. The depicted examples in Figures 1-2 and above-described examples are not meant to imply architectural limitations. For example, data processing system <part-num-ref name="depicted examples in Figures 1-2 and above-described examples are not meant to imply architectural limitations. For example, data processing system">200</part-num-ref>
|
| 194 |
+
also may be a tablet computer, laptop computer, or telephone device in addition to taking the form of a </p>
|
| 195 |
+
<heading id="h-7">PDA.</heading>
|
| 196 |
+
<p id="p-35" num="35">[0018] The illustrative embodiments provide a computer implemented method, apparatus, and computer usable program code for managing files. A set of origination locations for files are identified in response to a request to view the files. The set of origination locations is one or more locations. Each origination location in the set of origination locations identifies a location from which a file in the files has been received. In other words, the origination location is a download location. A representation of these files is presented using a set of one or more graphical indicators or based on the set of origination locations for the files.</p>
|
| 197 |
+
<p id="p-36" num="36">[0019] The origination locations for files are identified when files are downloaded in these examples.</p>
|
| 198 |
+
<p id="p-37" num="37">The presentation of the files using graphical indicators may take various forms. For example, the different locations may be identified using a set of colors, different icons, or a set of alpha-numeric characters.</p>
|
| 199 |
+
<p id="p-38" num="38">[0020] Turning now to Figure 3, a diagram illustrating components used for identifying the location of files is depicted in accordance with an illustrative embodiment. In this illustrative example, download process <part-num-ref name="illustrative embodiment. In this illustrative example, download process">300</part-num-ref>
|
| 200 |
+
downloads or receives files <part-num-ref name="downloads or receives files">302</part-num-ref>
|
| 201 |
+
from sources, such as source <part-num-ref name="from sources, such as source">304</part-num-ref>
|
| 202 |
+
and <boundary-data type="header">
|
| 203 |
+
<confidence value="88">11</confidence>
|
| 204 |
+
</boundary-data>
|
| 205 |
+
<boundary-data type="header">Docket No. AUS920<confidence value="555555884">060414US1</confidence>
|
| 206 |
+
</boundary-data>
|
| 207 |
+
<page-break num="12"/>
|
| 208 |
+
source <part-num-ref name="and source">306.</part-num-ref>
|
| 209 |
+
As these files are downloaded, the user may be given an option to have the files <part-num-ref name="files">302</part-num-ref>
|
| 210 |
+
associated with a graphical indicator, such as color codes, based on the origination of these files from source <part-num-ref name="origination of these files from source">304</part-num-ref>
|
| 211 |
+
and source <part-num-ref name="and source">306.</part-num-ref>
|
| 212 |
+
</p>
|
| 213 |
+
<p id="p-39" num="39">[0021] The information regarding the location of the files <part-num-ref name="files">302</part-num-ref>
|
| 214 |
+
is identified and stored in location data <part-num-ref name="is identified and stored in location data">308.</part-num-ref>
|
| 215 |
+
</p>
|
| 216 |
+
<p id="p-40" num="40">The location information is identified from the universal resource locator (URL) in these examples. The universal resource locator from which a file is obtained is compared to a list or database of universal resource locator that are correlated to known sources. For example the universal resource locator having a domain name, such as abc.com, is associated with a company called ABC, Inc. In addition or in place of identifying the source based on the universal resource locator, the different embodiments may associate the download location with a trust level for security purposes. If the user selects to use this option, the download location is captured as metadata and stored in location data <part-num-ref name="download location is captured as metadata and stored in location data">308.</part-num-ref>
|
| 217 |
+
</p>
|
| 218 |
+
<p id="p-41" num="41">[0022] For example, if the user obtains plug-ins from source <part-num-ref name="user obtains plug-ins from source">304,</part-num-ref>
|
| 219 |
+
the identification of the location of source <part-num-ref name="location of source">304</part-num-ref>
|
| 220 |
+
is stored in location data <part-num-ref name="is stored in location data">308</part-num-ref>
|
| 221 |
+
as the plug-ins are stored or received as files <part-num-ref name="plug-ins are stored or received as files">302.</part-num-ref>
|
| 222 |
+
The location is stored in association with an identification of the file in location data <part-num-ref name="file in location data">308.</part-num-ref>
|
| 223 |
+
If the user obtains a freeware or shareware application from source <part-num-ref name="freeware or shareware application from source">306,</part-num-ref>
|
| 224 |
+
the identification of that location is stored in location data <part-num-ref name="identification of that location is stored in location data">308</part-num-ref>
|
| 225 |
+
as the files for the freeware or shareware application are received in files <part-num-ref name="freeware or shareware application are received in files">302.</part-num-ref>
|
| 226 |
+
As a result, each file in files <part-num-ref name="result, each file in files">302</part-num-ref>
|
| 227 |
+
is associated with the location of source <part-num-ref name="location of source">304</part-num-ref>
|
| 228 |
+
or source <part-num-ref name="or source">306</part-num-ref>
|
| 229 |
+
in location data <part-num-ref name="in location data">308,</part-num-ref>
|
| 230 |
+
in these examples. </p>
|
| 231 |
+
<boundary-data type="header">
|
| 232 |
+
<confidence value="88">12</confidence>
|
| 233 |
+
</boundary-data>
|
| 234 |
+
<boundary-data type="header">Docket No. AUS920<confidence value="555555884">060414US1</confidence>
|
| 235 |
+
</boundary-data>
|
| 236 |
+
<p id="p-42" num="42">
|
| 237 |
+
<page-break num="13"/>
|
| 238 |
+
[0023] In this manner, a representation of files <part-num-ref name="representation of files">302</part-num-ref>
|
| 239 |
+
may be presented using graphical indicators. In addition to this type of organization mechanism, the different illustrative embodiments also may allow for files to be sorted based on the download location. A legend identifying the different graphical indicators also may be presented to allow the user to easily identify the location of different files. </p>
|
| 240 |
+
<p id="p-43" num="43">[0024] Download process 300 may be implemented as a separate application or part of another application. For example, download process <part-num-ref name="separate application or part of another application. For example, download process">300</part-num-ref>
|
| 241 |
+
may be implemented in a web browser. Further, download process <part-num-ref name="web browser. Further, download process">300</part-num-ref>
|
| 242 |
+
also may be placed into an operating system as an operating system feature depending on the particular implementation. </p>
|
| 243 |
+
<p id="p-44" num="44">[0025] Turning now to Figure 4, a diagram illustrating components used for viewing files based on download locations is depicted in accordance with an illustrative embodiment. Viewer process <part-num-ref name="illustrative embodiment. Viewer process">400</part-num-ref>
|
| 244 |
+
is initiated in these examples when a user input is received at graphical user interface (GUI) <part-num-ref name="user input is received at graphical user interface (GUI)">402</part-num-ref>
|
| 245 |
+
to display files <part-num-ref name="to display files">404.</part-num-ref>
|
| 246 |
+
In these examples, viewer process <part-num-ref name="to display files 404. In these examples, viewer process">400</part-num-ref>
|
| 247 |
+
uses metadata stored in location data <part-num-ref name="uses metadata stored in location data">406</part-num-ref>
|
| 248 |
+
to identify the download location of files <part-num-ref name="download location of files">404</part-num-ref>
|
| 249 |
+
in response to a user request to view files <part-num-ref name="user request to view files">404.</part-num-ref>
|
| 250 |
+
</p>
|
| 251 |
+
<p id="p-45" num="45">This request may be made in a number of different ways through GUI <part-num-ref name="number of different ways through GUI">402.</part-num-ref>
|
| 252 |
+
For example, the user may select entries from a start menu to display program or document files. </p>
|
| 253 |
+
<p id="p-46" num="46">Alternatively, the user may use an explorer program to display files and folders.</p>
|
| 254 |
+
<p id="p-47" num="47">[0026] Files 404 are presented in GUI <part-num-ref name="are presented in GUI">402</part-num-ref>
|
| 255 |
+
using a representation of the files. This representation is typically an icon with text. In these examples, the <boundary-data type="header">
|
| 256 |
+
<confidence value="88">13</confidence>
|
| 257 |
+
</boundary-data>
|
| 258 |
+
<boundary-data type="header">Docket No. AUS920<confidence value="555555884">060414US1</confidence>
|
| 259 |
+
</boundary-data>
|
| 260 |
+
<page-break num="14"/>
|
| 261 |
+
representation of the files is altered or modified to identify the location from which the location have been received or downloaded. The particular manner in which the graphical indicators are selected is based on policy <part-num-ref name="graphical indicators are selected is based on policy">408,</part-num-ref>
|
| 262 |
+
in these examples. Policy <part-num-ref name="graphical indicators are selected is based on policy 408, in these examples. Policy">408</part-num-ref>
|
| 263 |
+
may be, for example, a set of rules designating color coding for different download locations. Policy <part-num-ref name="set of rules designating color coding for different download locations. Policy">408</part-num-ref>
|
| 264 |
+
may be preset or selected based on user input, depending on the particular implementation. </p>
|
| 265 |
+
<p id="p-48" num="48">[0027] A user may select using color coding to present files <part-num-ref name="user may select using color coding to present files">404</part-num-ref>
|
| 266 |
+
through GUI <part-num-ref name="through GUI">402.</part-num-ref>
|
| 267 |
+
The user also may select the particular color coding for each particular location in location data <part-num-ref name="particular color coding for each particular location in location data">406.</part-num-ref>
|
| 268 |
+
These types of selections may form a set of rules in policy <part-num-ref name="set of rules in policy">408</part-num-ref>
|
| 269 |
+
for presenting files <part-num-ref name="for presenting files">404.</part-num-ref>
|
| 270 |
+
</p>
|
| 271 |
+
<p id="p-49" num="49">Depending on the particular implementation, the user may be presented with other types of graphical indicators other than colors when viewing files. For example, an additional icon may be embedded with the graphical representation of a file depending on the location from which the file was received. Another option the user may set through GUI <part-num-ref name="user may set through GUI">402</part-num-ref>
|
| 272 |
+
is to sort the files based on the download location. </p>
|
| 273 |
+
<p id="p-50" num="50">Further, the user also may select to display a legend for the different graphical indicators to be presented with the files in GUI <part-num-ref name="files in GUI">402.</part-num-ref>
|
| 274 |
+
</p>
|
| 275 |
+
<p id="p-51" num="51">[0028] Turning now to Figures 5A and 5B, diagrams illustrating a display of files are depicted in accordance with an illustrative embodiment. In this illustrative example in Figure 5A, display <part-num-ref name="illustrative embodiment. In this illustrative example in Figure 5A, display">500</part-num-ref>
|
| 276 |
+
shows a program listing through program <part-num-ref name="program listing through program">502</part-num-ref>
|
| 277 |
+
in start menu <part-num-ref name="in start menu">504.</part-num-ref>
|
| 278 |
+
In this example, program <part-num-ref name="in start menu 504. In this example, program">502</part-num-ref>
|
| 279 |
+
contains two groupings: IBM <part-num-ref name="contains two groupings: IBM">506</part-num-ref>
|
| 280 |
+
and ABC, Inc <part-num-ref name="and ABC, Inc">508.</part-num-ref>
|
| 281 |
+
Each of these groupings contains a listing of files, such as programs, documents, or other types of files. In <boundary-data type="header">
|
| 282 |
+
<confidence value="88">14</confidence>
|
| 283 |
+
</boundary-data>
|
| 284 |
+
<boundary-data type="header">Docket No. AUS<confidence value="588858558855">920060414US1</confidence>
|
| 285 |
+
</boundary-data>
|
| 286 |
+
<page-break num="15"/>
|
| 287 |
+
this example, the user has moved a pointer over IBM <part-num-ref name="pointer over IBM">506</part-num-ref>
|
| 288 |
+
to display files within this grouping. </p>
|
| 289 |
+
<p id="p-52" num="52">[0029] IBM 506 contains IBM Document <part-num-ref name="contains IBM Document">510</part-num-ref>
|
| 290 |
+
and IBM Program <part-num-ref name="and IBM Program">512.</part-num-ref>
|
| 291 |
+
In these examples, the display of these files is presented using a graphical indicator to identify the source from which the files were received. In other words, the graphical indicator identifies the download location of the files. In these examples, the graphical indicator is a color coding as illustrated by the cross hatching in the graphical representation of IBM Document <part-num-ref name="graphical representation of IBM Document">510</part-num-ref>
|
| 292 |
+
and IBM Program <part-num-ref name="and IBM Program">512.</part-num-ref>
|
| 293 |
+
Legend <part-num-ref name="and IBM Program 512. Legend">514</part-num-ref>
|
| 294 |
+
identifies the location or source of these files. In this example, vendor <part-num-ref name="location or source of these files. In this example, vendor">516</part-num-ref>
|
| 295 |
+
is the source of IBM Document <part-num-ref name="source of IBM Document">510</part-num-ref>
|
| 296 |
+
and IBM Program <part-num-ref name="and IBM Program">512.</part-num-ref>
|
| 297 |
+
</p>
|
| 298 |
+
<p id="p-53" num="53">[0030] Many times, the source or download location of the files is different from the company or organization that created the program or document. For example, an employee may download operating system patches from the employer's internal website or intranet rather than directly from the operating system vendor that created the files. Such a download is often made because the employer may make slight modifications or additions to the package tailored specifically for the internal architecture of the company. The identification of the download location makes determining whether files are trusted files easier for the user.</p>
|
| 299 |
+
<p id="p-54" num="54">[0031] In Figure <confidence value="5">5</confidence>
|
| 300 |
+
B, the user has moved the pointer over ABC, Inc <part-num-ref name="pointer over ABC, Inc">
|
| 301 |
+
<confidence value="5">5</confidence>
|
| 302 |
+
08. </part-num-ref>
|
| 303 |
+
This causes the display of files within this grouping. These files include ABC, Inc Document <part-num-ref name="display of files within this grouping. These files include ABC, Inc Document">
|
| 304 |
+
<confidence value="5">5</confidence>
|
| 305 |
+
18 </part-num-ref>
|
| 306 |
+
and ABC, Inc Program <part-num-ref name="and ABC, Inc Program">
|
| 307 |
+
<confidence value="5">5</confidence>
|
| 308 |
+
20. </part-num-ref>
|
| 309 |
+
In this example, ABC, Inc Document <part-num-ref name="and ABC, Inc Program 520. In this example, ABC, Inc Document">
|
| 310 |
+
<confidence value="5">5</confidence>
|
| 311 |
+
18 </part-num-ref>
|
| 312 |
+
is displayed using the same graphical indicator or color as with IBM Document <part-num-ref name="same graphical indicator or color as with IBM Document">
|
| 313 |
+
<confidence value="666">510</confidence>
|
| 314 |
+
</part-num-ref>
|
| 315 |
+
and IBM Program <part-num-ref name="and IBM Program">
|
| 316 |
+
<confidence value="5">5</confidence>
|
| 317 |
+
12. </part-num-ref>
|
| 318 |
+
This <boundary-data type="header">
|
| 319 |
+
<confidence value="88">15</confidence>
|
| 320 |
+
</boundary-data>
|
| 321 |
+
<boundary-data type="header">Docket No. AUS920<confidence value="555555685">060414US1</confidence>
|
| 322 |
+
</boundary-data>
|
| 323 |
+
<page-break num="16"/>
|
| 324 |
+
indicates that this file was received from vendor <part-num-ref name="and IBM Program 512. This indicates that this file was received from vendor">516.</part-num-ref>
|
| 325 |
+
</p>
|
| 326 |
+
<p id="p-55" num="55">ABC, Inc Program 520, however, is displayed using a different color coding as indicated by the cross hatching for ABC, Inc <part-num-ref name="cross hatching for ABC, Inc">520.</part-num-ref>
|
| 327 |
+
This color coding indicates that the file was received from reseller <part-num-ref name="file was received from reseller">522</part-num-ref>
|
| 328 |
+
rather than vendor <part-num-ref name="rather than vendor">516.</part-num-ref>
|
| 329 |
+
</p>
|
| 330 |
+
<p id="p-56" num="56">In this manner, color coding is used along with legend 514 to identify the download locations of the files in the different groupings.</p>
|
| 331 |
+
<p id="p-57" num="57">[0032] Additionally, in Figures 5A and <confidence value="5">5</confidence>
|
| 332 |
+
B, groupings of files also may be associated with an indication of the source from which the files were received. In this example, IBM <part-num-ref name="files were received. In this example, IBM">506</part-num-ref>
|
| 333 |
+
indicates that the files were received from vendor <part-num-ref name="files were received from vendor">516.</part-num-ref>
|
| 334 |
+
ABC, Inc <part-num-ref name="files were received from vendor 516. ABC, Inc">508</part-num-ref>
|
| 335 |
+
does not contain a graphical indication in this example. A graphical indication is not provided because ABC, Inc <part-num-ref name="graphical indication is not provided because ABC, Inc">508</part-num-ref>
|
| 336 |
+
contains files from more than one download location. </p>
|
| 337 |
+
<p id="p-58" num="58">[0033] With a color coding system for files being downloaded, the actual site may be identified using a name for the site or the entity that provides the files at that site. Additionally, the source from which files have been received may be identified using a designation that may encompass more than one site. For example, green may be used for a downloaded file from a trusted site, red for a file downloaded from a freeware site, yellow for a file downloaded from a shareware site, blue for a file downloaded from a browser plug-in site, orange for a file downloaded from an unknown site, and white for a file that is not downloaded. White would indicate, for example, a file that is part of the original operating system installation.</p>
|
| 338 |
+
<boundary-data type="header">
|
| 339 |
+
<confidence value="88">16</confidence>
|
| 340 |
+
</boundary-data>
|
| 341 |
+
<boundary-data type="header">Docket No. AUS920<confidence value="488555685">060414US1</confidence>
|
| 342 |
+
</boundary-data>
|
| 343 |
+
<p id="p-59" num="59">
|
| 344 |
+
<page-break num="17"/>
|
| 345 |
+
[0034] In addition to color coding the graphical representation of the file, the text could be in a user defined color according to some legend or association scheme. </p>
|
| 346 |
+
<p id="p-60" num="60">[0035] Turning now to Figure 6, a diagram illustrating a designation of locations for files in accordance with an illustrative embodiment. In this figure, display <part-num-ref name="illustrative embodiment. In this figure, display">600</part-num-ref>
|
| 347 |
+
is a desktop containing IBM Program <part-num-ref name="desktop containing IBM Program">602</part-num-ref>
|
| 348 |
+
and ABC, Inc Program <part-num-ref name="and ABC, Inc Program">604.</part-num-ref>
|
| 349 |
+
In this example, the graphical indicator takes the form of an icon that is displayed in association with the representation of the program on display <part-num-ref name="program on display">600.</part-num-ref>
|
| 350 |
+
IBM Program <part-num-ref name="program on display 600. IBM Program">602</part-num-ref>
|
| 351 |
+
is displayed in association with circle <part-num-ref name="is displayed in association with circle">606</part-num-ref>
|
| 352 |
+
while ABC, Inc Program <part-num-ref name="while ABC, Inc Program">604</part-num-ref>
|
| 353 |
+
is displayed in association with star <part-num-ref name="is displayed in association with star">608.</part-num-ref>
|
| 354 |
+
</p>
|
| 355 |
+
<p id="p-61" num="61">[0036] Turning now to Figure 7, a diagram illustrating a listing of files sorted based on download location is depicted in accordance with an illustrative embodiment. In this example, window <part-num-ref name="illustrative embodiment. In this example, window">700</part-num-ref>
|
| 356 |
+
is a listing of files. IBM Document <part-num-ref name="listing of files. IBM Document">702,</part-num-ref>
|
| 357 |
+
IBM Program <part-num-ref name="listing of files. IBM Document 702, IBM Program">704,</part-num-ref>
|
| 358 |
+
ABC, Inc Document <part-num-ref name="listing of files. IBM Document 702, IBM Program 704, ABC, Inc Document">708</part-num-ref>
|
| 359 |
+
and ABC, Inc Program <part-num-ref name="and ABC, Inc Program">706</part-num-ref>
|
| 360 |
+
are displayed with details in this example. Each entry contains, in addition to the name of the file, the date the file was modified, the size of the file, the file type, and a download location. The different illustrative embodiments add this additional detail to help a user identify the source or download location of files. In this particular example, instead of displaying the actual download location, the download location is associated with an identification of the type of site. For example, IBM Document <part-num-ref name="type of site. For example, IBM Document">702</part-num-ref>
|
| 361 |
+
is from a trusted site while ABC, Inc Document <part-num-ref name="trusted site while ABC, Inc Document">708</part-num-ref>
|
| 362 |
+
is from an unknown site. </p>
|
| 363 |
+
<p id="p-62" num="62">[0037] Turning now to Figure 8, a flowchart of a process to identify and associate location data with downloaded <boundary-data type="header">
|
| 364 |
+
<confidence value="88">17</confidence>
|
| 365 |
+
</boundary-data>
|
| 366 |
+
<boundary-data type="header">Docket No. A<confidence value="68666656555685">US920060414US1</confidence>
|
| 367 |
+
</boundary-data>
|
| 368 |
+
<page-break num="18"/>
|
| 369 |
+
files is depicted in accordance with an illustrative embodiment. The process illustrated in Figure 8 is an example of a process that may be implemented in download process <part-num-ref name="process that may be implemented in download process">300</part-num-ref>
|
| 370 |
+
in Figure 3. </p>
|
| 371 |
+
<p id="p-63" num="63">[0038] The process begins by identifying the location of the download (step 800). Next, the process receives the file (step 802). Then, the process associates the file with location data (step 804). Finally, the process determines whether more files are present to download (step 806). If the process determines more files are present to download in step <part-num-ref name="process determines more files are present to download in step">806,</part-num-ref>
|
| 372 |
+
the process returns to step <part-num-ref name="process returns to step">802</part-num-ref>
|
| 373 |
+
to receive the files. If the process determines no more files are present to download in step <part-num-ref name="process determines no more files are present to download in step">806,</part-num-ref>
|
| 374 |
+
the process terminates. </p>
|
| 375 |
+
<p id="p-64" num="64">[0039] Turning now to Figure 9, a flowchart of a process to display a set of files using the associated location data is depicted in accordance with an illustrative embodiment. The flowchart in Figure 9 illustrates a process that may be implemented in viewer process <part-num-ref name="process that may be implemented in viewer process">400</part-num-ref>
|
| 376 |
+
in Figure 4. </p>
|
| 377 |
+
<p id="p-65" num="65">[0040] The process begins by receiving a request to view a set of files (step 900). In step <part-num-ref name="set of files (step 900). In step">900,</part-num-ref>
|
| 378 |
+
the request may originate from a user input selecting entries in a start menu or a user initiating an explorer program to view files. Next the process, selects a file from the set of files for processing (step 902). The process determines if the file is associated with location data (step 904). This determination is made using location data, such as location data <part-num-ref name="file is associated with location data (step 904). This determination is made using location data, such as location data">406</part-num-ref>
|
| 379 |
+
in Figure 4. If the file is associated with location data in step <part-num-ref name="file is associated with location data in step">904,</part-num-ref>
|
| 380 |
+
the process identifies a display <boundary-data type="header">
|
| 381 |
+
<confidence value="88">18</confidence>
|
| 382 |
+
</boundary-data>
|
| 383 |
+
<boundary-data type="header">Docket No. AUS920<confidence value="555555685">060414US1</confidence>
|
| 384 |
+
</boundary-data>
|
| 385 |
+
<page-break num="19"/>
|
| 386 |
+
mode for the file using a po<confidence value="8">l</confidence>
|
| 387 |
+
icy, such as policy <part-num-ref name="policy, such as policy">408</part-num-ref>
|
| 388 |
+
in Figure 4 (step 906)<confidence value="5">.</confidence>
|
| 389 |
+
</p>
|
| 390 |
+
<p id="p-66" num="66">[0041] Then, the process determines more files are present to process (step 908). If more files are not present to process, the files are sorted by download location (step 910), and the set of files are displayed using the associated location data (step <part-num-ref name="associated location data (step">912)</part-num-ref>
|
| 391 |
+
with the process terminating thereafter. </p>
|
| 392 |
+
<p id="p-67" num="67">[0042] Turning back to the determination made in step <part-num-ref name="determination made in step">908,</part-num-ref>
|
| 393 |
+
if the process determines that more files are present to process, the process returns to step <part-num-ref name="process returns to step">902.</part-num-ref>
|
| 394 |
+
Turning further back to the determination made in step <part-num-ref name="determination made in step">904,</part-num-ref>
|
| 395 |
+
if the process determines that the file is not associated with location data, the process proceeds to step <part-num-ref name="process proceeds to step">908</part-num-ref>
|
| 396 |
+
and continues as described above. </p>
|
| 397 |
+
<p id="p-68" num="68">[0043] Thus, the present invention provides a computer implemented method, apparatus, and computer usable program code for managing files. In response to a request to view files, origination locations for the files are identified.</p>
|
| 398 |
+
<p id="p-69" num="69">Each origination location identifies a location from which a file has been received. Representations of the files are presenting using a set of graphical indicators based on the origination locations. As a result, a user is able to present files based on their download location. In the depicted examples, the files are presented using graphical indicators in the form of color coding. Of course, any type of graphical indication may be used to differentiate files based on download location.</p>
|
| 399 |
+
<p id="p-70" num="70">[0044] The invention can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment containing both hardware and software elements.</p>
|
| 400 |
+
<boundary-data type="header">
|
| 401 |
+
<confidence value="88">19</confidence>
|
| 402 |
+
</boundary-data>
|
| 403 |
+
<boundary-data type="header">Docket No. AUS920<confidence value="858555685">060414US1</confidence>
|
| 404 |
+
</boundary-data>
|
| 405 |
+
<p id="p-71" num="71">
|
| 406 |
+
<page-break num="20"/>
|
| 407 |
+
In a preferred embodiment, the invention is implemented in software, which includes but is not limited to firmware, resident software, microcode, etc. </p>
|
| 408 |
+
<p id="p-72" num="72">[0045] Furthermore, the invention can take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system. For the purposes of this description, a computer-usable or computer readable medium can be any tangible apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.</p>
|
| 409 |
+
<p id="p-73" num="73">[0046] The medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. Examples of a computer-readable medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. Current examples of optical disks include compact disk - read only memory (CD-ROM), compact disk - read/write (CD-R/W) and </p>
|
| 410 |
+
<heading id="h-8">DVD.</heading>
|
| 411 |
+
<p id="p-74" num="74">[0047] A data processing system suitable for storing and/or executing program code will include at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements can include local memory employed during actual execution of the program code, bulk storage, and cache memories which provide temporary storage of at least some program code in <boundary-data type="header">
|
| 412 |
+
<confidence value="88">20</confidence>
|
| 413 |
+
</boundary-data>
|
| 414 |
+
<boundary-data type="header">Docket No. AUS920<confidence value="555555685">060414US1</confidence>
|
| 415 |
+
</boundary-data>
|
| 416 |
+
<page-break num="21"/>
|
| 417 |
+
order to reduce the number of times code must be retrieved from bulk storage during execution. </p>
|
| 418 |
+
<p id="p-75" num="75">[0048] Input/output or I/O devices (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers.</p>
|
| 419 |
+
<p id="p-76" num="76">[0049] Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modem and Ethernet cards are just a few of the currently available types of network adapters.</p>
|
| 420 |
+
<p id="p-77" num="77">[0050] The description of the present invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiment was chosen and described in order to best explain the principles of the invention, the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.</p>
|
| 421 |
+
<boundary-data type="header">
|
| 422 |
+
<confidence value="88">21</confidence>
|
| 423 |
+
</boundary-data>
|
| 424 |
+
<boundary-data type="header">Docket No. AUS920<confidence value="555555685">060414US1</confidence>
|
| 425 |
+
</boundary-data>
|
| 426 |
+
</description>
|
| 427 |
+
</us-patent-application>
|
| 428 |
+
|
applicant/11483478.xml
ADDED
|
@@ -0,0 +1,601 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11483478</doc-number>
|
| 8 |
+
<date>2006-07-10</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">Attorney Docket No.: 000005-<confidence value="66">00</confidence>
|
| 14 |
+
190<confidence value="488">0US</confidence>
|
| 15 |
+
Client Reference No.: 2006P00204US </p>
|
| 16 |
+
<heading id="h-1">PATENT APPLICATION</heading>
|
| 17 |
+
<p id="p-2" num="2">Systems and Methods of Managing Product Tracking Data Inventors: Zolt<confidence value="4">a</confidence>
|
| 18 |
+
n Nochta, a citizen of Hungary, residing at WutachstraBe <part-num-ref name="citizen of Hungary, residing at WutachstraBe">20</part-num-ref>
|
| 19 |
+
<part-num-ref name="">76199</part-num-ref>
|
| 20 |
+
Kar<confidence value="5">l</confidence>
|
| 21 |
+
sruhe, Germany Assignee: SAP AG Dietmar-Hopp-Allee <part-num-ref name="Karlsruhe, Germany Assignee: SAP AG Dietmar-Hopp-Allee">16</part-num-ref>
|
| 22 |
+
<part-num-ref name="">69180</part-num-ref>
|
| 23 |
+
Walldorf Germany Entity: Large </p>
|
| 24 |
+
<heading id="h-2">FOUNTAINHEAD LAW GROUP</heading>
|
| 25 |
+
<p id="p-3" num="3">900 Lafayette St., Suite 509 Santa Clara, CA <part-num-ref name="Santa Clara, CA">95050</part-num-ref>
|
| 26 |
+
Tel: 408-244-6319 <page-break num="2"/>
|
| 27 |
+
</p>
|
| 28 |
+
<heading id="h-3">PATENT</heading>
|
| 29 |
+
<p id="p-4" num="4">Attorney Docket No.: 000005-00190<confidence value="585">0US</confidence>
|
| 30 |
+
Systems and Methods of Managing Product Tracking Data </p>
|
| 31 |
+
<heading id="h-4">CROSS REFERENCE TO RELATED APPLICATIONS</heading>
|
| 32 |
+
<p id="p-5" num="5">
|
| 33 |
+
<confidence value="5">[</confidence>
|
| 34 |
+
0001<confidence value="5">]</confidence>
|
| 35 |
+
Not applicable. </p>
|
| 36 |
+
<heading id="h-5">BACKGROUND</heading>
|
| 37 |
+
<p id="p-6" num="6">
|
| 38 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 39 |
+
<confidence value="5">[</confidence>
|
| 40 |
+
0002<confidence value="5">]</confidence>
|
| 41 |
+
The present invention relates to data management systems, and in particular, to data management systems for managing product tracking data. </p>
|
| 42 |
+
<p id="p-7" num="7">
|
| 43 |
+
<confidence value="5">[</confidence>
|
| 44 |
+
0003<confidence value="5">]</confidence>
|
| 45 |
+
Today, the design, production, distribution, sales, maintenance of products and many other related business activities are conducted by multiple collaborating companies that <boundary-data type="line-number">10 </boundary-data>
|
| 46 |
+
build a so-called "supply chain". The different entities in the supply chain use their company-specific knowledge, resources and competencies in order to fulfill consumers' requirements by producing, transporting, transforming, etc. high-quality goods and related services. </p>
|
| 47 |
+
<p id="p-8" num="8">
|
| 48 |
+
<confidence value="5">[</confidence>
|
| 49 |
+
0004<confidence value="5">]</confidence>
|
| 50 |
+
The goal of so-called "track and trace" systems (also called tracking systems) in this <boundary-data type="line-number">15 </boundary-data>
|
| 51 |
+
context is to gather information about goods during their lifecycle. In this manner, goods may be tracked at the very atomic level (that is, on an individual item level), or at any other logistics handling unit levels, such as deliveries, pallets, cases, etc. </p>
|
| 52 |
+
<p id="p-9" num="9">[0005] Various types of data may be collected by track and trace systems. Such types include geographic information, environmental information, timestamp information, etc. For <boundary-data type="line-number">20 </boundary-data>
|
| 53 |
+
example, the geographic information may be information regarding the various geographic locations visited by the goods, such as the addresses of related producers, carriers, wholesalers, distributors, consumers, etc. The environmental information may be information related to temperature, such as temperature values measured during storage and transportation of tracked goods. The timestamp information may include timestamps for <boundary-data type="line-number">25 </boundary-data>
|
| 54 |
+
delivery, shipments, repair works, etc. </p>
|
| 55 |
+
<p id="p-10" num="10">[0006] Depending on the collected information and the quality (that is, the accuracy and completeness) of the resulting data, tracking information can be used in different business relevant cases. Examples include sophisticated inventory management, product authentication, product recall actions due to a production failure, quality management of <part-num-ref name="production failure, quality management of">30</part-num-ref>
|
| 56 |
+
shipping processes, etc. </p>
|
| 57 |
+
<boundary-data type="header">
|
| 58 |
+
<confidence value="6">1</confidence>
|
| 59 |
+
</boundary-data>
|
| 60 |
+
<p id="p-11" num="11">
|
| 61 |
+
<page-break num="3"/>
|
| 62 |
+
[0007] A tracking system that, for instance, tracks products of any producer in a given industry (for example, the pharmaceuticals of each pharmaceutical company) may have components such as a database, a search base (or index base), data management systems, and data query systems. The involved parties of the supply chain can connect to the system and <boundary-data type="line-number">5 </boundary-data>
|
| 63 |
+
can feed their respective data into it via respective clients. </p>
|
| 64 |
+
<p id="p-12" num="12">
|
| 65 |
+
<confidence value="5">[</confidence>
|
| 66 |
+
0008] When searching for tracking information to a given product that may be identified by an identifier (which may be unique), the user can connect to the tracking system, make a request, and download a subset of the available information related to the object in question. </p>
|
| 67 |
+
<p id="p-13" num="13">The identifier may include an electronic product code (EPC), a barcode, a printed or engraved <boundary-data type="line-number">10 </boundary-data>
|
| 68 |
+
serial number, etc. </p>
|
| 69 |
+
<p id="p-14" num="14">[0009] In general, the tracking system is outside of the supply chain. That is, the various entities in the supply chain direct the products according to market need, and the tracking system manages the tracking information.</p>
|
| 70 |
+
<p id="p-15" num="15">
|
| 71 |
+
<confidence value="5">[</confidence>
|
| 72 |
+
0010<confidence value="5">]</confidence>
|
| 73 |
+
A number of issues arise when using many existing tracking systems. Foremost <boundary-data type="line-number">15 </boundary-data>
|
| 74 |
+
among these are the security issues. Each entity in the supply chain needs to be authorized to access and update the tracking information at the relevant time. Such authorization is complex when the supply chain adjusts according to market need. More specifically, the tracking system operator does not know which business entity will be the intended next party in the supply chain that will further manufacture, ship, store, sell, buy, etc. the given tracked <boundary-data type="line-number">20 </boundary-data>
|
| 75 |
+
object. This is rather determined by ad-hoc economic needs, incoming orders, changes on transportation routes, costs, seasonal market behavior, fashion trends, etc. As market needs shift, entities may be added to, removed from, or moved around in the supply chain. </p>
|
| 76 |
+
<p id="p-16" num="16">
|
| 77 |
+
<confidence value="5">[</confidence>
|
| 78 |
+
0011<confidence value="5">1</confidence>
|
| 79 |
+
Therefore, the operator of the tracking system has no a priori information <confidence value="8">w</confidence>
|
| 80 |
+
hich entities should be made capable to access (for example, read, write, alter or delete) the <boundary-data type="line-number">25 </boundary-data>
|
| 81 |
+
corresponding tracking data. In the worst case, the operator of the tracking system does not even know all the possible entities that might be the next entities at some future point of time. </p>
|
| 82 |
+
<p id="p-17" num="17">[0012<confidence value="5">]</confidence>
|
| 83 |
+
Furthermore, some compartmentalization of tracking information is desirable. For example, an entity in the supply chain could potentially use the tracking system to gather business intelligence on another entity in the chain unless the tracking information is <boundary-data type="line-number">30 </boundary-data>
|
| 84 |
+
compartmentalized. The operator has to take care of a secure authorization and access control to the business sensitive tracking data. </p>
|
| 85 |
+
<boundary-data type="header">
|
| 86 |
+
<confidence value="8">2</confidence>
|
| 87 |
+
</boundary-data>
|
| 88 |
+
<p id="p-18" num="18">
|
| 89 |
+
<page-break num="4"/>
|
| 90 |
+
<confidence value="5">[</confidence>
|
| 91 |
+
0013<confidence value="4">]</confidence>
|
| 92 |
+
The security issues are further complicated when the tracking system is itself outside of the supply chain. In such a case, the tracking system cannot (by itself) define the access levels to be given to the various entities in the supply chain. </p>
|
| 93 |
+
<p id="p-19" num="19">
|
| 94 |
+
<confidence value="5">[</confidence>
|
| 95 |
+
0014<confidence value="5">]</confidence>
|
| 96 |
+
Thus, there is a need for an improved tracking system. The present invention solves <boundary-data type="line-number">5 </boundary-data>
|
| 97 |
+
these and other problems by providing a tracking system that allows one entity in the supply chain to authorize another entity in the supply chain to access the tracking system. </p>
|
| 98 |
+
<heading id="h-6">SUMMARY</heading>
|
| 99 |
+
<p id="p-20" num="20">
|
| 100 |
+
<confidence value="5">[</confidence>
|
| 101 |
+
0015<confidence value="5">]</confidence>
|
| 102 |
+
Embodiments of the present invention improve the tracking of products in a supply <boundary-data type="line-number">10 </boundary-data>
|
| 103 |
+
chain. In one embodiment, the present invention includes a computer-implemented method of managing product tracking data for tracking products in a supply chain. The method includes authorizing access to a database by a first entity. The method further includes accessing, by the first entity, a data record in the database. The data record is associated with a product to be tracked in the supply chain. The method further includes associating, by the <boundary-data type="line-number">15 </boundary-data>
|
| 104 |
+
first entity, the data record with a second entity. The second entity corresponds to an entity in the supply chain that will assume control over the product subsequent to said first entity. The method further includes authorizing access to the database by the second entity. The method further includes accessing, by the second entity, the data record in the database. </p>
|
| 105 |
+
<p id="p-21" num="21">[0016<confidence value="5">]</confidence>
|
| 106 |
+
According to another embodiment of the present invention, a computerized system <boundary-data type="line-number">20 </boundary-data>
|
| 107 |
+
implements the above method. The method may be implemented with software that is supported by databases. </p>
|
| 108 |
+
<p id="p-22" num="22">[0017] In this manner, the tracking system need not be pre-configured with the details of the supply chain, but may instead dynamically adjust as the supply chain changes in accordance with market conditions.</p>
|
| 109 |
+
<p id="p-23" num="23">
|
| 110 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 111 |
+
<confidence value="5">[</confidence>
|
| 112 |
+
0018<confidence value="5">]</confidence>
|
| 113 |
+
The following detailed description and accompanying drawings provide a better understanding of the nature and advantages of the present invention. </p>
|
| 114 |
+
<heading id="h-7">BRIEF DESCRIPTION OF THE DRAW<confidence value="8">I</confidence>
|
| 115 |
+
NGS </heading>
|
| 116 |
+
<p id="p-24" num="24">
|
| 117 |
+
<confidence value="5">[</confidence>
|
| 118 |
+
0019] FIG. 1 is a block diagram of a tracking system according to an embodiment of the <part-num-ref name="">30</part-num-ref>
|
| 119 |
+
present invention. </p>
|
| 120 |
+
<boundary-data type="header">
|
| 121 |
+
<confidence value="8">3</confidence>
|
| 122 |
+
</boundary-data>
|
| 123 |
+
<p id="p-25" num="25">
|
| 124 |
+
<page-break num="5"/>
|
| 125 |
+
[0020] FIG. 2 is a block diagram of a process according to an embodiment of the present invention. </p>
|
| 126 |
+
<p id="p-26" num="26">
|
| 127 |
+
<confidence value="5">[</confidence>
|
| 128 |
+
0021<confidence value="5">]</confidence>
|
| 129 |
+
FIGS. 3A-3<confidence value="5">B</confidence>
|
| 130 |
+
are data definition tables relating to access records according to embodiments of the present invention. </p>
|
| 131 |
+
<p id="p-27" num="27">
|
| 132 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 133 |
+
[0022<confidence value="5">]</confidence>
|
| 134 |
+
FIGS. 3C-3E are data tables that correspond to example access records according to embodiments of the present invention. </p>
|
| 135 |
+
<p id="p-28" num="28">
|
| 136 |
+
<confidence value="5">[</confidence>
|
| 137 |
+
0023] FIG. 4A is a data definition table relating to a tracking record according to an embodiment of the present invention. </p>
|
| 138 |
+
<p id="p-29" num="29">[0024] FIG. 4B is a data table that corresponds to an example tracking record according to <boundary-data type="line-number">10 </boundary-data>
|
| 139 |
+
an embodiment of the present invention. </p>
|
| 140 |
+
<p id="p-30" num="30">[0025] FIG. 5 is a block diagram of a supply chain <part-num-ref name="supply chain">500</part-num-ref>
|
| 141 |
+
throug<confidence value="8">h</confidence>
|
| 142 |
+
which a product is tracked according to an embodiment of the present invention. </p>
|
| 143 |
+
<heading id="h-8">DETAILED DESCRIPTION</heading>
|
| 144 |
+
<p id="p-31" num="31">
|
| 145 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 146 |
+
[0026] Described herein are techniques for operating a tracking system that tracks products in a supply chain. In the following description, for purposes of explanation, numerous examples and specific details are set forth in order to provide a thorough understanding of the present invention. It will be evident, however, to one skilled in the art that the present invention as defined by the claims may include some or all of the features in these examples <boundary-data type="line-number">20 </boundary-data>
|
| 147 |
+
alone or in combination with other features described below, and may further include obvious modifications and equivalents of the features and concepts described herein. </p>
|
| 148 |
+
<p id="p-32" num="32">[0027] The following description describes various methods and processes. Although the particular method steps are discussed in a particular order, such discussion is mainly for clarity of presentation. It should be recognized that such order may be varied, and some steps <boundary-data type="line-number">25 </boundary-data>
|
| 149 |
+
may be performed in parallel. One step need only follow another step when the other step must be completed before the one step begins. </p>
|
| 150 |
+
<p id="p-33" num="33">
|
| 151 |
+
<confidence value="5">[</confidence>
|
| 152 |
+
0028] In the following description, the term "access" is used. "Access" should be interpreted broadly to mean accessing data in order to read, write, create, update, modify<confidence value="8">,</confidence>
|
| 153 |
+
copy, delete, exercise control over, or otherwise manipulate the data, with particular <boundary-data type="header">
|
| 154 |
+
<confidence value="8">4</confidence>
|
| 155 |
+
</boundary-data>
|
| 156 |
+
<page-break num="6"/>
|
| 157 |
+
applicability to data relating to tracking products in a supply chain. Access also broadly includes the ability to grant or to deny, wholly or partially, access to the data to others. </p>
|
| 158 |
+
<p id="p-34" num="34">
|
| 159 |
+
<confidence value="5">[</confidence>
|
| 160 |
+
0029<confidence value="4">]</confidence>
|
| 161 |
+
In the following description, the term "control" is used. "Control" should be interpreted broadly to mean the ability to exert physical influence on a product, including <boundary-data type="line-number">5 </boundary-data>
|
| 162 |
+
manufacturing, remanufacturing, refurbishing, shipping, delivering, receiving, storing, selling, buying, etc. the product, with particular applicability to the use and movement of the product in a supply chain, and the tracking of the product in the supply chain. Control also includes the ability to incorporate the tracked product into another product that may itself be tracked. </p>
|
| 163 |
+
<p id="p-35" num="35">
|
| 164 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 165 |
+
<confidence value="5">[</confidence>
|
| 166 |
+
0030<confidence value="5">]</confidence>
|
| 167 |
+
In the following description, the term "entity" is used. "Entity" should be interpreted broadly to mean an individual, a group, a company, an association, a business, or other entity that exercises control over a product in a supply chain. Two or more entities make up a supply chain. </p>
|
| 168 |
+
<p id="p-36" num="36">
|
| 169 |
+
<confidence value="5">[</confidence>
|
| 170 |
+
0031<confidence value="5">]</confidence>
|
| 171 |
+
In the following description, the term "owner" is used. "Owner" should be <boundary-data type="line-number">15 </boundary-data>
|
| 172 |
+
interpreted broadly to mean an entity that is capable of exercising control over a product. </p>
|
| 173 |
+
<p id="p-37" num="37">Often a product may have only one owner at a given time.</p>
|
| 174 |
+
<p id="p-38" num="38">[0032<confidence value="5">]</confidence>
|
| 175 |
+
FIG. 1 is a block diagram of a tracking system <part-num-ref name="tracking system">100</part-num-ref>
|
| 176 |
+
according to an embodiment of the present invention. The tracking system <part-num-ref name="tracking system">100</part-num-ref>
|
| 177 |
+
may be implemented in a computer system, for example, as computer programs, data, and databases. The tracking system <part-num-ref name="tracking system">100</part-num-ref>
|
| 178 |
+
includes <boundary-data type="line-number">20 </boundary-data>
|
| 179 |
+
one or more tracking applications <part-num-ref name="includes one or more tracking applications">102,</part-num-ref>
|
| 180 |
+
an access rights database <part-num-ref name="access rights database">104,</part-num-ref>
|
| 181 |
+
and a tracking database <part-num-ref name="tracking database">106.</part-num-ref>
|
| 182 |
+
The tracking system <part-num-ref name="tracking system">100</part-num-ref>
|
| 183 |
+
may include, be a part of, or otherwise interface with other hardware or software components, which (for conciseness) are not shown. </p>
|
| 184 |
+
<p id="p-39" num="39">
|
| 185 |
+
<confidence value="4">[</confidence>
|
| 186 |
+
0033<confidence value="5">]</confidence>
|
| 187 |
+
The tracking applications <part-num-ref name="tracking applications">102</part-num-ref>
|
| 188 |
+
generally function as an interface between the entities in the supply chain and the tracking data. The tracking applications <part-num-ref name="tracking applications">102</part-num-ref>
|
| 189 |
+
receive as inputs <boundary-data type="line-number">25 </boundary-data>
|
| 190 |
+
various accesses from entities in the supply chain. For example, an entity may connect to the tracking applications <part-num-ref name="tracking applications">102</part-num-ref>
|
| 191 |
+
via a network, and may enter data as prompted by the tracking applications <part-num-ref name="tracking applications">102.</part-num-ref>
|
| 192 |
+
The tracking applications <part-num-ref name="tracking applications">102</part-num-ref>
|
| 193 |
+
generate as outputs responses to the entities, which may include access to the tracking data. </p>
|
| 194 |
+
<p id="p-40" num="40">
|
| 195 |
+
<confidence value="5">[</confidence>
|
| 196 |
+
0034<confidence value="4">]</confidence>
|
| 197 |
+
The access rights database <part-num-ref name="access rights database">104</part-num-ref>
|
| 198 |
+
generally works with the tracking applications <part-num-ref name="tracking applications">102</part-num-ref>
|
| 199 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 200 |
+
to control access to the tracking data. The access rights database <part-num-ref name="access rights database">104</part-num-ref>
|
| 201 |
+
receives as inputs information from the tracking applications <part-num-ref name="tracking applications">102.</part-num-ref>
|
| 202 |
+
This information may be in the form of <boundary-data type="header">
|
| 203 |
+
<confidence value="8">5</confidence>
|
| 204 |
+
</boundary-data>
|
| 205 |
+
<page-break num="7"/>
|
| 206 |
+
queries regarding whether a particular entity is authorized to access particular tracking data. </p>
|
| 207 |
+
<p id="p-41" num="41">The access rights database 104 generates as outputs information back to the tracking applications <part-num-ref name="tracking applications">102.</part-num-ref>
|
| 208 |
+
This information may be in the form of authorization acknowledgements that indicate whether a particular entity is authorized to access the particular tracking data <boundary-data type="line-number">5 </boundary-data>
|
| 209 |
+
that was queried. The authorization acknowledgements may also indicate what specific types of access are authorized to the entity for that particular tracking data. </p>
|
| 210 |
+
<p id="p-42" num="42">
|
| 211 |
+
<confidence value="5">[</confidence>
|
| 212 |
+
0035<confidence value="5">]</confidence>
|
| 213 |
+
The tracking database <part-num-ref name="tracking database">106</part-num-ref>
|
| 214 |
+
generally stores the tracking data for the products to be tracked in the supply chain. The tracking database <part-num-ref name="tracking database">106</part-num-ref>
|
| 215 |
+
receives as inputs tracking information. The tracking information may be in the form of authorized accesses to <boundary-data type="line-number">10 </boundary-data>
|
| 216 |
+
particular tracking data by a particular entity. Such authorized access may include updates to tracking data. The tracking database <part-num-ref name="tracking database">106</part-num-ref>
|
| 217 |
+
generates as outputs the responses to the authorized accesses. Such responses may include the tracking data itself, or a portion thereof, depending upon the level of authorized access, for example, in response to a read request. </p>
|
| 218 |
+
<p id="p-43" num="43">[0036<confidence value="5">]</confidence>
|
| 219 |
+
FIG. 2 is a block diagram of a process <part-num-ref name="process">200</part-num-ref>
|
| 220 |
+
according to an embodiment of the <boundary-data type="line-number">15 </boundary-data>
|
| 221 |
+
present invention. The process <part-num-ref name="process">200</part-num-ref>
|
| 222 |
+
may be implemented on the computer system that implements the tracking system <part-num-ref name="tracking system">100.</part-num-ref>
|
| 223 |
+
In such case, the process <part-num-ref name="process">200</part-num-ref>
|
| 224 |
+
may be performed by the tracking applications <part-num-ref name="tracking applications">102</part-num-ref>
|
| 225 |
+
or by other applications. Steps 202-204 concern initialization of the tracking data in the process <part-num-ref name="process">200,</part-num-ref>
|
| 226 |
+
and steps 206-212 concern the general tracking operation in the process <part-num-ref name="process">200.</part-num-ref>
|
| 227 |
+
</p>
|
| 228 |
+
<p id="p-44" num="44">
|
| 229 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 230 |
+
<confidence value="5">[</confidence>
|
| 231 |
+
0037<confidence value="5">]</confidence>
|
| 232 |
+
In step 202, a data record is initialized for the product to be tracked. This involves creating an access record for the product in the access rights database <part-num-ref name="access rights database">104</part-num-ref>
|
| 233 |
+
and creating a tracking record for the product in the tracking database <part-num-ref name="tracking database">106.</part-num-ref>
|
| 234 |
+
The access record is generally a data structure that includes a unique identifier for the product to be tracked, as well as an indicator of what entities are authorized to access the tracking data for that product. (See <boundary-data type="line-number">25 </boundary-data>
|
| 235 |
+
FIGS. 3A<confidence value="5">-</confidence>
|
| 236 |
+
3E and related description below for further details regarding the access record.) The tracking record is generally a data structure that includes the unique identifier for the product to be tracked, as well as other data related to tracking the product in the supply chain. </p>
|
| 237 |
+
<p id="p-45" num="45">(See FIGS. 4A-4B and related description below for further details regarding the tracking record.) <boundary-data type="line-number">30 </boundary-data>
|
| 238 |
+
<confidence value="5">[</confidence>
|
| 239 |
+
0038<confidence value="5">]</confidence>
|
| 240 |
+
In step <part-num-ref name="tracking record.) [0038] In step">204,</part-num-ref>
|
| 241 |
+
the access rights for the data record are initialized. For a given product to be tracked, one or more entities are initially authorized to access the data record. </p>
|
| 242 |
+
<p id="p-46" num="46">According to one embodiment, the authorized entity (or entities) is indicated in the access <boundary-data type="header">
|
| 243 |
+
<confidence value="8">6</confidence>
|
| 244 |
+
</boundary-data>
|
| 245 |
+
<page-break num="8"/>
|
| 246 |
+
record. The level of the entity's authorized access may also be indicated in the access record. </p>
|
| 247 |
+
<p id="p-47" num="47">For example, one access level would be the ability to authorize additional entities to access the tracking record. Other levels of access include read access, write access, update access, modification access, delete access, copy access, etc.</p>
|
| 248 |
+
<p id="p-48" num="48">
|
| 249 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 250 |
+
[0039<confidence value="5">]</confidence>
|
| 251 |
+
According to one embodiment, a single entity is authorized upon initialization of the data record. This single entity is often the first entity in the supply chain, such as the manufacturer of the product to be tracked. This first entity is authorized to authorize additional entities to access the tracking record. </p>
|
| 252 |
+
<p id="p-49" num="49">[0040<confidence value="5">]</confidence>
|
| 253 |
+
Once the data record has been initialized, the process <part-num-ref name="process">200</part-num-ref>
|
| 254 |
+
proceeds to the general <boundary-data type="line-number">10 </boundary-data>
|
| 255 |
+
operational mode. The general operational mode is directed mainly toward updating tracking data for a particular product as it moves in the supply chain. </p>
|
| 256 |
+
<p id="p-50" num="50">[0041<confidence value="5">]</confidence>
|
| 257 |
+
In step 206, the tracking applications <part-num-ref name="tracking applications">102</part-num-ref>
|
| 258 |
+
receive an input from an entity in the supply chain. This input is often in the form of a query for access to tracking data or an update to tracking data. The input may be digitally signed or encrypted, in which case the <boundary-data type="line-number">15 </boundary-data>
|
| 259 |
+
tracking applications <part-num-ref name="tracking applications">102</part-num-ref>
|
| 260 |
+
may verify the digital signature or perform the decryption as necessary, or may interface with other applications to do so. </p>
|
| 261 |
+
<p id="p-51" num="51">
|
| 262 |
+
<confidence value="5">[</confidence>
|
| 263 |
+
0042<confidence value="5">]</confidence>
|
| 264 |
+
In step 208, the tracking applications <part-num-ref name="tracking applications">102</part-num-ref>
|
| 265 |
+
determine whether the entity enquiring in step <part-num-ref name="entity enquiring in step">206</part-num-ref>
|
| 266 |
+
is authorized to access the tracking data. This involves accessing the access rights database <part-num-ref name="access rights database">104.</part-num-ref>
|
| 267 |
+
The relevant access record will indicate whether the entity is authorized to <boundary-data type="line-number">20 </boundary-data>
|
| 268 |
+
access a given tracking record. If the access record indicates that the entity is to be given a specific type of access (for example, read access or update access), the tracking applications <part-num-ref name="tracking applications">102</part-num-ref>
|
| 269 |
+
determine that as well from the access rights database <part-num-ref name="access rights database">104.</part-num-ref>
|
| 270 |
+
</p>
|
| 271 |
+
<p id="p-52" num="52">
|
| 272 |
+
<confidence value="5">[</confidence>
|
| 273 |
+
0043<confidence value="5">]</confidence>
|
| 274 |
+
In step 210, once the access has been authorized, the tracking applications <part-num-ref name="tracking applications">102</part-num-ref>
|
| 275 |
+
manage the access by the enquiring entity to the tracking data. In general, this involves the <boundary-data type="line-number">25 </boundary-data>
|
| 276 |
+
entity updating the tracking record for the tracked product. For example, a shipping entity may update the tracking record to include a delivery time of the product when it delivers the product to a warehouse. This may also involve providing information back to the entity, such as a response to a read request, or a verification that an update has been processed. </p>
|
| 277 |
+
<p id="p-53" num="53">
|
| 278 |
+
<confidence value="5">[</confidence>
|
| 279 |
+
0044<confidence value="5">]</confidence>
|
| 280 |
+
The process <part-num-ref name="process">200</part-num-ref>
|
| 281 |
+
may continue in steps 206-210 as various authorized entities access <part-num-ref name="may continue in steps 206-210 as various authorized entities access">30</part-num-ref>
|
| 282 |
+
the tracking data as the product moves in the supply chain. </p>
|
| 283 |
+
<boundary-data type="header">
|
| 284 |
+
<confidence value="8">7</confidence>
|
| 285 |
+
</boundary-data>
|
| 286 |
+
<p id="p-54" num="54">
|
| 287 |
+
<page-break num="9"/>
|
| 288 |
+
[0045] In step 212, an additional entity is authorized to access the tracking data for a given product. According to an embodiment of the present invention, an authorized entity in the supply chain may have the ability to authorize another entity to access the tracking data for a given product. Often the "current owner" of the product authorizes the prospective or <boundary-data type="line-number">5 </boundary-data>
|
| 289 |
+
anticipated "next owner" in the supply chain. In such a manner, entities may enter or leave the supply chain according to market needs, the supply chain adjusts to the changes, and the tracking system can track products in the supply chain without having any a priori knowledge of the supply chain. </p>
|
| 290 |
+
<p id="p-55" num="55">[0046<confidence value="5">]</confidence>
|
| 291 |
+
For example, for a given product, the manufacturer may be initially authorized to <boundary-data type="line-number">10 </boundary-data>
|
| 292 |
+
access the tracking data. The manufacturer then accesses the tracking system <part-num-ref name="tracking system">100</part-num-ref>
|
| 293 |
+
as desired to update the tracking data for the product. The next entity in the supply chain is the shipper, so the manufacturer authorizes the shipper to access the tracking data for the product. The shipper then accesses the tracking system <part-num-ref name="tracking system">100</part-num-ref>
|
| 294 |
+
as desired to update the tracking data for the product. The next entity in the supply chain is the wholesaler, so the shipper authorizes the <boundary-data type="line-number">15 </boundary-data>
|
| 295 |
+
wholesaler to access the tracking data for the product. The wholesaler then accesses the tracking system <part-num-ref name="tracking system">100</part-num-ref>
|
| 296 |
+
as desired to update the tracking data for the product. And so on. </p>
|
| 297 |
+
<p id="p-56" num="56">
|
| 298 |
+
<confidence value="5">[</confidence>
|
| 299 |
+
0047<confidence value="5">]</confidence>
|
| 300 |
+
Often, a single "next owner" is authorized at each relevant point. However, more than one "next owner" may be authorized if so desired. The multiple next owners may correspond to multiple branches in the supply chain. For example, a manufacturer may <boundary-data type="line-number">20 </boundary-data>
|
| 301 |
+
authorize two shippers as the next owners of the product. Whichever one of the two shippers that becomes the current owner then accesses the tracking data for the product. The multiple next owners may also be multiple stages in the supply chain. For example, a manufacturer may authorize a shipper as the next owner of the product, and may also authorize a wholesaler as the second next owner of the product. </p>
|
| 302 |
+
<p id="p-57" num="57">
|
| 303 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 304 |
+
[0048<confidence value="5">]</confidence>
|
| 305 |
+
The process <part-num-ref name="process">200</part-num-ref>
|
| 306 |
+
may continue in steps 206-212 as various authorized entities access the tracking data as the product moves in the supply chain. </p>
|
| 307 |
+
<p id="p-58" num="58">[0049<confidence value="5">]</confidence>
|
| 308 |
+
Once the next entity has assumed control over the product and become the current owner, the access rights of the previous owner may be adjusted. For example, once the shipper has assumed control over the product from the manufacturer, the access rights of the <boundary-data type="line-number">30 </boundary-data>
|
| 309 |
+
manufacturer may be adjusted to allow read access, but not write access, to the tracking data. </p>
|
| 310 |
+
<p id="p-59" num="59">[0050<confidence value="5">]</confidence>
|
| 311 |
+
In the general case for the process <part-num-ref name="process">200</part-num-ref>
|
| 312 |
+
described above, the data record is created by the first entity in the supply chain. However, other entities in the supply chain may also <boundary-data type="header">
|
| 313 |
+
<confidence value="8">8</confidence>
|
| 314 |
+
</boundary-data>
|
| 315 |
+
<page-break num="10"/>
|
| 316 |
+
create data records that correspond to additional products to be tracked. For example, a first manufacturer may initiate tracking of a first product that is delivered to a second manufacturer. The second manufacturer may incorporate the first product into a second product and may create a data record for the second product. The tracking record for the first <boundary-data type="line-number">5 </boundary-data>
|
| 317 |
+
product may be updated to include a pointer to the tracking record for the second product. </p>
|
| 318 |
+
<p id="p-60" num="60">The tracking record for the second product may be updated to include a pointer to the tracking record for the first product.</p>
|
| 319 |
+
<p id="p-61" num="61">
|
| 320 |
+
<confidence value="5">[</confidence>
|
| 321 |
+
0051<confidence value="5">]</confidence>
|
| 322 |
+
Although the general operational mode of the process <part-num-ref name="process">200</part-num-ref>
|
| 323 |
+
is directed toward transactional access to the tracking data, the tracking applications <part-num-ref name="tracking applications">102</part-num-ref>
|
| 324 |
+
may also include <boundary-data type="line-number">10 </boundary-data>
|
| 325 |
+
features to allow aggregative access to the tracking data by authorized entities. For example, if a manufacturer is using two shipping companies, the manufacturer may be authorized to view the tracking data for completed deliveries, in order to compare the performance of the shipping companies. </p>
|
| 326 |
+
<p id="p-62" num="62">
|
| 327 |
+
<confidence value="5">[</confidence>
|
| 328 |
+
0052<confidence value="5">]</confidence>
|
| 329 |
+
FIGS. 3A-3E relate to access records used in embodiments of the present invention. </p>
|
| 330 |
+
<p id="p-63" num="63">
|
| 331 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 332 |
+
FIGS. 3A-3B are data definition tables relating to access records according to embodiments of the present invention. FIGS. 3C-3E are data tables that correspond to example access records according to embodiments of the present invention. </p>
|
| 333 |
+
<p id="p-64" num="64">
|
| 334 |
+
<confidence value="5">[</confidence>
|
| 335 |
+
0053<confidence value="5">]</confidence>
|
| 336 |
+
FIG. 3A shows a data defi<confidence value="8">n</confidence>
|
| 337 |
+
ition table <part-num-ref name="data definition table">300</part-num-ref>
|
| 338 |
+
that includes two fields, an ID field <part-num-ref name="ID field">302</part-num-ref>
|
| 339 |
+
and an entity field <part-num-ref name="entity field">304.</part-num-ref>
|
| 340 |
+
The ID field <part-num-ref name="ID field">302</part-num-ref>
|
| 341 |
+
stores an identifier that corresponds to the product <boundary-data type="line-number">20 </boundary-data>
|
| 342 |
+
to be tracked. The entity field <part-num-ref name="entity field">304</part-num-ref>
|
| 343 |
+
stores an identifier that corresponds to an authorized entity. </p>
|
| 344 |
+
<p id="p-65" num="65">
|
| 345 |
+
<confidence value="5">[</confidence>
|
| 346 |
+
0054<confidence value="5">]</confidence>
|
| 347 |
+
FIG. 3B shows a data definition table <part-num-ref name="data definition table">310</part-num-ref>
|
| 348 |
+
that includes three fields, an ID field <part-num-ref name="ID field">312,</part-num-ref>
|
| 349 |
+
an entity field <part-num-ref name="entity field">314,</part-num-ref>
|
| 350 |
+
and an access level field <part-num-ref name="access level field">316.</part-num-ref>
|
| 351 |
+
The ID field <part-num-ref name="ID field">312</part-num-ref>
|
| 352 |
+
and the entity field <part-num-ref name="entity field">314</part-num-ref>
|
| 353 |
+
correspond to the similar fields in FIG. 3A. The access level field <part-num-ref name="access level field">316</part-num-ref>
|
| 354 |
+
stores an identifier <boundary-data type="line-number">25 </boundary-data>
|
| 355 |
+
that corresponds to a level of access. </p>
|
| 356 |
+
<p id="p-66" num="66">
|
| 357 |
+
<confidence value="5">[</confidence>
|
| 358 |
+
0055<confidence value="5">]</confidence>
|
| 359 |
+
FIG. 3C shows a data table <part-num-ref name="data table">320</part-num-ref>
|
| 360 |
+
corresponding to the data definition table <part-num-ref name="data definition table">300</part-num-ref>
|
| 361 |
+
that includes example data. The example data shows that for the tracked product identified by identifier <part-num-ref name="tracked product identified by identifier">0001,</part-num-ref>
|
| 362 |
+
the manufacturer is authorized to access the tracking data. </p>
|
| 363 |
+
<p id="p-67" num="67">
|
| 364 |
+
<confidence value="5">[</confidence>
|
| 365 |
+
0056<confidence value="5">]</confidence>
|
| 366 |
+
FIG. 3D shows a data table <part-num-ref name="data table">330</part-num-ref>
|
| 367 |
+
corresponding to the data definition table <part-num-ref name="data definition table">300</part-num-ref>
|
| 368 |
+
that <boundary-data type="line-number">30 </boundary-data>
|
| 369 |
+
includes example data. The example data shows that for the tracked product identified by identifier <part-num-ref name="tracked product identified by identifier">0001,</part-num-ref>
|
| 370 |
+
the manufacturer and the shipper are authorized to access the tracking data. </p>
|
| 371 |
+
<boundary-data type="header">
|
| 372 |
+
<confidence value="8">9</confidence>
|
| 373 |
+
</boundary-data>
|
| 374 |
+
<p id="p-68" num="68">
|
| 375 |
+
<page-break num="11"/>
|
| 376 |
+
<confidence value="5">[</confidence>
|
| 377 |
+
0057<confidence value="5">]</confidence>
|
| 378 |
+
FIG. 3E shows a data table <part-num-ref name="data table">340</part-num-ref>
|
| 379 |
+
corresponding to the data definition table <part-num-ref name="data definition table">310</part-num-ref>
|
| 380 |
+
that includes example data. The example data shows that for the tracked product identified by identifier <part-num-ref name="tracked product identified by identifier">0001,</part-num-ref>
|
| 381 |
+
the manufacturer has read access to the tracking data, and the shipper has write access to the tracking data. Thus, the example data indicates that the manufacturer has <boundary-data type="line-number">5 </boundary-data>
|
| 382 |
+
ceded control over the tracked product to the shipper. </p>
|
| 383 |
+
<p id="p-69" num="69">
|
| 384 |
+
<confidence value="5">[</confidence>
|
| 385 |
+
0058<confidence value="5">]</confidence>
|
| 386 |
+
As discussed above, the particular fields that are implemented in the access record may be adjusted according to design criteria. The fields shown above are for example purposes to illustrate the broad concept behind embodiments of the present invention. </p>
|
| 387 |
+
<p id="p-70" num="70">
|
| 388 |
+
<confidence value="5">[</confidence>
|
| 389 |
+
0059<confidence value="5">]</confidence>
|
| 390 |
+
FIGS. 4A-4B relate to tracking records according to embodiments of the present <boundary-data type="line-number">10 </boundary-data>
|
| 391 |
+
invention. FIG. 4A is a data definition table relating to a tracking record according to an embodiment of the present invention. FIG. 4B is a data table that corresponds to an example tracking record according to an embodiment of the present invention. </p>
|
| 392 |
+
<p id="p-71" num="71">
|
| 393 |
+
<confidence value="5">[</confidence>
|
| 394 |
+
0060<confidence value="5">]</confidence>
|
| 395 |
+
FIG. 4A shows a data definition table <part-num-ref name="data definition table">400</part-num-ref>
|
| 396 |
+
that includes two fields, an ID field <part-num-ref name="ID field">402</part-num-ref>
|
| 397 |
+
and a tracking data field <part-num-ref name="tracking data field">404.</part-num-ref>
|
| 398 |
+
The ID field <part-num-ref name="ID field">402</part-num-ref>
|
| 399 |
+
stores an identifier that corresponds to the <boundary-data type="line-number">15 </boundary-data>
|
| 400 |
+
product to be tracked. The tracking data field <part-num-ref name="tracking data field">404</part-num-ref>
|
| 401 |
+
stores tracking data. </p>
|
| 402 |
+
<p id="p-72" num="72">[0061] FIG. 4B shows a data table <part-num-ref name="data table">410</part-num-ref>
|
| 403 |
+
corresponding to the data definition table <part-num-ref name="data definition table">400</part-num-ref>
|
| 404 |
+
that includes example data. The example data shows that for the tracked product identified by identifier <part-num-ref name="tracked product identified by identifier">0001,</part-num-ref>
|
| 405 |
+
on <part-num-ref name="tracked product identified by identifier 0001, on">1</part-num-ref>
|
| 406 |
+
January the tracking record was initialized, on <part-num-ref name="tracking record was initialized, on">2</part-num-ref>
|
| 407 |
+
January the tracked product was in Warehouse A, on <part-num-ref name="on">3</part-num-ref>
|
| 408 |
+
January the tracked product was in Truck B, and on <part-num-ref name="tracked product was in Truck B, and on">4</part-num-ref>
|
| 409 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 410 |
+
January the tracked product was in Warehouse C. </p>
|
| 411 |
+
<p id="p-73" num="73">
|
| 412 |
+
<confidence value="5">[</confidence>
|
| 413 |
+
0062<confidence value="4">]</confidence>
|
| 414 |
+
As discussed above, the particular fields that are implemented in the tracking record may be adjusted according to design criteria. The fields shown above are for example purposes to illustrate the broad concept behind embodiments of the present invention. </p>
|
| 415 |
+
<p id="p-74" num="74">Example fields include a date field, a time field, a location field, a temperature field, a pointer <boundary-data type="line-number">25 </boundary-data>
|
| 416 |
+
field, a general information field, etc. </p>
|
| 417 |
+
<p id="p-75" num="75">
|
| 418 |
+
<confidence value="5">[</confidence>
|
| 419 |
+
0063<confidence value="5">]</confidence>
|
| 420 |
+
FIG. 5 is a block diagram of a supply chain <part-num-ref name="supply chain">500</part-num-ref>
|
| 421 |
+
through which a product is tracked according to an embodiment of the present invention. The block diagram provides a visual reference for an example process to schematically demonstrate how the embodiments of the present invention work in real world scenarios. </p>
|
| 422 |
+
<boundary-data type="header">
|
| 423 |
+
<confidence value="88">10</confidence>
|
| 424 |
+
</boundary-data>
|
| 425 |
+
<p id="p-76" num="76">
|
| 426 |
+
<page-break num="12"/>
|
| 427 |
+
<confidence value="5">[</confidence>
|
| 428 |
+
0064<confidence value="4">]</confidence>
|
| 429 |
+
The supply chain <part-num-ref name="supply chain">500</part-num-ref>
|
| 430 |
+
includes Company B <part-num-ref name="includes Company B">502,</part-num-ref>
|
| 431 |
+
Carrier B <part-num-ref name="includes Company B 502, Carrier B">504,</part-num-ref>
|
| 432 |
+
Company C <part-num-ref name="includes Company B 502, Carrier B 504, Company C">506,</part-num-ref>
|
| 433 |
+
Carrier C <part-num-ref name="includes Company B 502, Carrier B 504, Company C 506, Carrier C">508,</part-num-ref>
|
| 434 |
+
Company D <part-num-ref name="includes Company B 502, Carrier B 504, Company C 506, Carrier C 508, Company D">510,</part-num-ref>
|
| 435 |
+
Carrier D <part-num-ref name="includes Company B 502, Carrier B 504, Company C 506, Carrier C 508, Company D 510, Carrier D">512,</part-num-ref>
|
| 436 |
+
Company F <part-num-ref name="includes Company B 502, Carrier B 504, Company C 506, Carrier C 508, Company D 510, Carrier D 512, Company F">514,</part-num-ref>
|
| 437 |
+
Carrier E <part-num-ref name="includes Company B 502, Carrier B 504, Company C 506, Carrier C 508, Company D 510, Carrier D 512, Company F 514, Carrier E">516,</part-num-ref>
|
| 438 |
+
and Company G <part-num-ref name="includes Company B 502, Carrier B 504, Company C 506, Carrier C 508, Company D 510, Carrier D 512, Company F 514, Carrier E 516, and Company G">518.</part-num-ref>
|
| 439 |
+
</p>
|
| 440 |
+
<p id="p-77" num="77">[0065] Company B 502 is a vendor of nuts and Company C <part-num-ref name="vendor of nuts and Company C">506</part-num-ref>
|
| 441 |
+
is a manufacturer of bolts. </p>
|
| 442 |
+
<p id="p-78" num="78">
|
| 443 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 444 |
+
Company D 510 integrates the nuts and the bolts into a common product referred to as a gizmo. The resulting gizmo is then distributed, sold, or used, etc. by Company F <part-num-ref name="resulting gizmo is then distributed, sold, or used, etc. by Company F">514</part-num-ref>
|
| 445 |
+
and Company G <part-num-ref name="and Company G">518.</part-num-ref>
|
| 446 |
+
</p>
|
| 447 |
+
<p id="p-79" num="79">[0066] Company B 502 is initially authorized to edit the respective parts of the tracking database <part-num-ref name="tracking database">106</part-num-ref>
|
| 448 |
+
(see FIG. 1) that are foreseen to hold data on "nuts produced by Company B <boundary-data type="line-number">10 </boundary-data>
|
| 449 |
+
502". </p>
|
| 450 |
+
<p id="p-80" num="80">
|
| 451 |
+
<confidence value="5">[</confidence>
|
| 452 |
+
0067<confidence value="5">]</confidence>
|
| 453 |
+
When producing nuts, Company B 502 initializes the data sets (see steps 202-204 in FIG. 2). Depending on the desired granularity of the tracking data, Company B <part-num-ref name="tracking data, Company B">502</part-num-ref>
|
| 454 |
+
can set up identifiers and the respective tracking data sets, e.g. for every single nut that it has been producing. </p>
|
| 455 |
+
<p id="p-81" num="81">
|
| 456 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 457 |
+
<confidence value="5">[</confidence>
|
| 458 |
+
0068<confidence value="5">]</confidence>
|
| 459 |
+
When getting an order from Company D <part-num-ref name="order from Company D">510,</part-num-ref>
|
| 460 |
+
Company B <part-num-ref name="order from Company D 510, Company B">502</part-num-ref>
|
| 461 |
+
engages Carrier B <part-num-ref name="engages Carrier B">504</part-num-ref>
|
| 462 |
+
to deliver the requested nuts. </p>
|
| 463 |
+
<p id="p-82" num="82">
|
| 464 |
+
<confidence value="5">[</confidence>
|
| 465 |
+
0069] Thereby, Company B 502 can edit (i.e. write) the tracking data of the given nuts to state that they (e.g. represented by the identifiers) will be delivered and should arrive at Company D <part-num-ref name="identifiers) will be delivered and should arrive at Company D">510</part-num-ref>
|
| 466 |
+
(e.g. given by the postal address) at a certain date and time, etc., and also to <boundary-data type="line-number">20 </boundary-data>
|
| 467 |
+
state that the delivery is done by Carrier B <part-num-ref name="delivery is done by Carrier B">504.</part-num-ref>
|
| 468 |
+
</p>
|
| 469 |
+
<p id="p-83" num="83">
|
| 470 |
+
<confidence value="5">[</confidence>
|
| 471 |
+
0070] Further, Company B 502 also updates the respective content of the access rights database <part-num-ref name="access rights database">104</part-num-ref>
|
| 472 |
+
(see FIG. 1) by sending a digitally signed message to the tracking system <part-num-ref name="tracking system">100</part-num-ref>
|
| 473 |
+
(see FIG. 1) expressing that the respective tracking data to the given delivered nuts now can only be edited, i.e. written by Carrier B <part-num-ref name="written by Carrier B">504</part-num-ref>
|
| 474 |
+
as it is the new (temporary) owner of the <boundary-data type="line-number">25 </boundary-data>
|
| 475 |
+
delivered goods. </p>
|
| 476 |
+
<p id="p-84" num="84">
|
| 477 |
+
<confidence value="5">[</confidence>
|
| 478 |
+
0071] When arriving at the targeted Company D <part-num-ref name="targeted Company D">510,</part-num-ref>
|
| 479 |
+
Carrier B <part-num-ref name="targeted Company D 510, Carrier B">504</part-num-ref>
|
| 480 |
+
alters the tracking data, e.g., it sets the date/time of delivery, transport vehicle identifier, etc. for the delivered nuts. </p>
|
| 481 |
+
<boundary-data type="header">
|
| 482 |
+
<confidence value="88">11</confidence>
|
| 483 |
+
</boundary-data>
|
| 484 |
+
<p id="p-85" num="85">
|
| 485 |
+
<page-break num="13"/>
|
| 486 |
+
<confidence value="5">[</confidence>
|
| 487 |
+
0072<confidence value="5">]</confidence>
|
| 488 |
+
In the same time, Carrier B <part-num-ref name="same time, Carrier B">504</part-num-ref>
|
| 489 |
+
also authorizes Company D <part-num-ref name="also authorizes Company D">510</part-num-ref>
|
| 490 |
+
to alter the respective data sets, since Company D <part-num-ref name="respective data sets, since Company D">510</part-num-ref>
|
| 491 |
+
is the new responsible owner of the shipped goods. </p>
|
| 492 |
+
<p id="p-86" num="86">
|
| 493 |
+
<confidence value="5">[</confidence>
|
| 494 |
+
0073<confidence value="5">]</confidence>
|
| 495 |
+
Company C 506 manages its bolt delivery on Company D <part-num-ref name="manages its bolt delivery on Company D">510</part-num-ref>
|
| 496 |
+
in a similar way, by <boundary-data type="line-number">5 </boundary-data>
|
| 497 |
+
authorizing Carrier C <part-num-ref name="similar way, by authorizing Carrier C">508</part-num-ref>
|
| 498 |
+
as the responsible transportation company. </p>
|
| 499 |
+
<p id="p-87" num="87">
|
| 500 |
+
<confidence value="5">[</confidence>
|
| 501 |
+
0074<confidence value="5">]</confidence>
|
| 502 |
+
When producing the added value products from nuts and bolts, Company D <part-num-ref name="added value products from nuts and bolts, Company D">510</part-num-ref>
|
| 503 |
+
can set up new tracking data sets and unique identifiers for the produced new items (gizmos). </p>
|
| 504 |
+
<p id="p-88" num="88">These data sets can contain (backward) pointers to the respective data sets of the different built-in parts (i.e., nuts and bolts) of the new products. Alternatively, Company D <part-num-ref name="new products. Alternatively, Company D">510</part-num-ref>
|
| 505 |
+
can <boundary-data type="line-number">10 </boundary-data>
|
| 506 |
+
decide to further edit the existing separated data sets of the nuts or the bolts without setting up new data sets. </p>
|
| 507 |
+
<p id="p-89" num="89">
|
| 508 |
+
<confidence value="5">[</confidence>
|
| 509 |
+
0075<confidence value="5">]</confidence>
|
| 510 |
+
Goods produced by Company D 510 can then be distributed and sold in a similar way on other members of the supply chain, including Carrier D <part-num-ref name="supply chain, including Carrier D">512,</part-num-ref>
|
| 511 |
+
Company F <part-num-ref name="supply chain, including Carrier D 512, Company F">514,</part-num-ref>
|
| 512 |
+
Carrier E <part-num-ref name="supply chain, including Carrier D 512, Company F 514, Carrier E">516,</part-num-ref>
|
| 513 |
+
and Company G <part-num-ref name="supply chain, including Carrier D 512, Company F 514, Carrier E 516, and Company G">518.</part-num-ref>
|
| 514 |
+
</p>
|
| 515 |
+
<p id="p-90" num="90">
|
| 516 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 517 |
+
<confidence value="5">[</confidence>
|
| 518 |
+
0076<confidence value="5">]</confidence>
|
| 519 |
+
The methods and systems according to embodiments of the present invention help operators and participating entities within the supply chain (typically companies) to manage access to the possibly highly sensitive information stored in product tracking systems. For this purpose of authorization, the operator of the tracking system provides a service to which the entities within the supply chain can connect. </p>
|
| 520 |
+
<p id="p-91" num="91">
|
| 521 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 522 |
+
<confidence value="5">[</confidence>
|
| 523 |
+
0077<confidence value="5">]</confidence>
|
| 524 |
+
As mentioned above, at each point of time within a given product's lifecycle, there is a given definite set of entities (and often a single entity) that currently have control over a particular product in the supply chain at the respective point of time. </p>
|
| 525 |
+
<p id="p-92" num="92">[0078] As described above, many existing tracking systems are unable to adequately manage access to the tracking data. The embodiments of the present invention solve this <boundary-data type="line-number">25 </boundary-data>
|
| 526 |
+
dilemma by allowing the relevant data provisioning entities to autonomously and securely manage the tracking data related to a given object or set of objects. </p>
|
| 527 |
+
<p id="p-93" num="93">[0079<confidence value="5">]</confidence>
|
| 528 |
+
Thereby, only the respective first relevant entity (for example, the manufacturer of the product) need be given the a priori right to initially create a tracking data set within the tracking system for the given object that is to be tracked. For this purpose, the manufacturer <part-num-ref name="manufacturer">30</part-num-ref>
|
| 529 |
+
may log in to the tracking system, authenticate itself, and send the requested data. </p>
|
| 530 |
+
<boundary-data type="header">
|
| 531 |
+
<confidence value="88">12</confidence>
|
| 532 |
+
</boundary-data>
|
| 533 |
+
<p id="p-94" num="94">
|
| 534 |
+
<page-break num="14"/>
|
| 535 |
+
<confidence value="5">[</confidence>
|
| 536 |
+
0080] Once a data set has been initialized for the object, the current owner of it can autonomously decide which entity (or entities) should be made responsible for further altering the data. Modifications will typically comprise the addition of new entries to the current (initial) data set. </p>
|
| 537 |
+
<p id="p-95" num="95">
|
| 538 |
+
<boundary-data type="line-number">
|
| 539 |
+
<confidence value="8">5</confidence>
|
| 540 |
+
</boundary-data>
|
| 541 |
+
<confidence value="5">[</confidence>
|
| 542 |
+
0081<confidence value="5">]</confidence>
|
| 543 |
+
For example, the manufacturer of a product may determine the next responsible entity, for example the wholesaler, after the wholesaler has ordered or paid for the given product. Depending on the granularity of the data to be collected, the intended next entity may also be the carrier company that transports the ordered product. After successful delive<confidence value="8">r</confidence>
|
| 544 |
+
y and altering the tracking data, the carrier may designate the wholesaler as the next <boundary-data type="line-number">10 </boundary-data>
|
| 545 |
+
responsible entity to further manage the respective data sets. </p>
|
| 546 |
+
<p id="p-96" num="96">
|
| 547 |
+
<confidence value="5">[</confidence>
|
| 548 |
+
0082<confidence value="5">]</confidence>
|
| 549 |
+
In general, the "current owner" (with "owner" being understood to follow the broad definition given above) of the object may have access to the tracking data of that object. The current owner may further authorize the respective "next owner" to manage or alter the tracking data sets, typically after the object has changed its owner or other context that may <boundary-data type="line-number">15 </boundary-data>
|
| 550 |
+
be relevant for tracking. </p>
|
| 551 |
+
<p id="p-97" num="97">
|
| 552 |
+
<confidence value="5">[</confidence>
|
| 553 |
+
0083<confidence value="5">]</confidence>
|
| 554 |
+
Thereby, the current owner can either completely or partly lose its rights to make further changes on the data. </p>
|
| 555 |
+
<p id="p-98" num="98">[0084] It is also possible to handle access to tracking data of complex objects (e.g. cars) which contain multiple objects (e.g. gears, tires, engine, etc.) that can be tracked either as a <boundary-data type="line-number">20 </boundary-data>
|
| 556 |
+
set of single objects or even as one cumulated entity. </p>
|
| 557 |
+
<p id="p-99" num="99">
|
| 558 |
+
<confidence value="5">[</confidence>
|
| 559 |
+
0085<confidence value="5">]</confidence>
|
| 560 |
+
The embodiments of the present invention also support the (special) case where the current owner of the object and the related tracking data can authorize multiple next owners (i.e. the successors of successors etc.) instead of authorizing exactly one next entity. </p>
|
| 561 |
+
<p id="p-100" num="100">
|
| 562 |
+
<confidence value="5">[</confidence>
|
| 563 |
+
0086<confidence value="5">]</confidence>
|
| 564 |
+
This case is especially relevant for serving more stable/static supply chains or static <boundary-data type="line-number">25 </boundary-data>
|
| 565 |
+
parts of dynamic/ad-hoc supply chains. </p>
|
| 566 |
+
<p id="p-101" num="101">
|
| 567 |
+
<confidence value="5">[</confidence>
|
| 568 |
+
0087<confidence value="5">]</confidence>
|
| 569 |
+
In such cases, the current owner (who might dominate the complete supply chain) determines the way which the object should go trough until a certain point of time or location. For example, the manufacturer of a product exactly plans the way of the product through the supply chain, via the entities A, B and C in that sequence. Accordingly, the <boundary-data type="line-number">30 </boundary-data>
|
| 570 |
+
manufacturer can authorize A, B and C to make changes on the respective tracking data related to the product. </p>
|
| 571 |
+
<boundary-data type="header">
|
| 572 |
+
<confidence value="88">13</confidence>
|
| 573 |
+
</boundary-data>
|
| 574 |
+
<p id="p-102" num="102">
|
| 575 |
+
<page-break num="15"/>
|
| 576 |
+
<confidence value="5">[</confidence>
|
| 577 |
+
0088<confidence value="5">]</confidence>
|
| 578 |
+
Security of messages that are sent to the tracking system's authorization service is another concern that is addressed by embodiments of the present invention. The messages are preferably authenticated, in order to ensure the identity of the access granting entity, i.e. </p>
|
| 579 |
+
<p id="p-103" num="103">the current object owner. The messages are preferably protected against malicious changes <boundary-data type="line-number">5 </boundary-data>
|
| 580 |
+
by unauthorized parties who could otherwise gain access to the sensitive data, for instance, by granting access themselves. The messages may also be protected against eavesdropping, in order to protect against unauthorized parties that otherwise could monitor the process within the supply chain and/or make copies of the sent authorization messages. </p>
|
| 581 |
+
<p id="p-104" num="104">[0089] In additional embodiments, the above security protections may also be applied to <boundary-data type="line-number">10 </boundary-data>
|
| 582 |
+
the respective tracking information submitted to the tracking system. </p>
|
| 583 |
+
<p id="p-105" num="105">
|
| 584 |
+
<confidence value="5">[</confidence>
|
| 585 |
+
0090] To fulfill the above security protections, embodiments of the present invention may implement one of a number of security methods. Such methods include password based authentication methods and digital signatures; message integrity codes, such as cryptographic hash functions or keyed message authentication codes; and message encryption algorithms. </p>
|
| 586 |
+
<p id="p-106" num="106">
|
| 587 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 588 |
+
[0091<confidence value="5">]</confidence>
|
| 589 |
+
Depending on the selected security technologies, the access control service might be coupled with the corresponding security systems, such as public key infrastructures (i.e. when digital signatures are used to authenticate messages), password management and validation services, etc. These systems can be either run by the operator of the tracking system, or by a trusted external security service provider. </p>
|
| 590 |
+
<p id="p-107" num="107">
|
| 591 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 592 |
+
<confidence value="5">[</confidence>
|
| 593 |
+
0092] The above description illustrates various embodiments of the present invention along with examples of how aspects of the present invention may be implemented. The above examples and embodiments should not be deemed to be the only embodiments, and are presented to illustrate the flexibility and advantages of the present invention as defined by the following claims. Based on the above disclosure and the following claims, other <boundary-data type="line-number">25 </boundary-data>
|
| 594 |
+
arrangements, embodiments, implementations and equivalents will be evident to those skilled in the art and may be employed without departing from the spirit and scope of the invention as defined by the claims. The terms and expressions that have been employed here are used to describe the various embodiments and examples. These terms and expressions are not to be construed as excluding equivalents of the features shown and described, or portions <boundary-data type="line-number">30 </boundary-data>
|
| 595 |
+
thereof, it being recognized that various modifications are possible within the scope of the appended claims. </p>
|
| 596 |
+
<boundary-data type="header">
|
| 597 |
+
<confidence value="88">14</confidence>
|
| 598 |
+
</boundary-data>
|
| 599 |
+
</description>
|
| 600 |
+
</us-patent-application>
|
| 601 |
+
|
applicant/11496208.xml
ADDED
|
@@ -0,0 +1,593 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11496208</doc-number>
|
| 8 |
+
<date>2006-07-31</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">APPLICATION FOR UNITED STATES LETTERS PATENT</heading>
|
| 14 |
+
<p id="p-1" num="1">(Attorney Docket No. MBHB 06-416) (Client No. P1079U<confidence value="68">S)</confidence>
|
| 15 |
+
<boundary-data type="line-number">
|
| 16 |
+
<confidence value="8">5</confidence>
|
| 17 |
+
</boundary-data>
|
| 18 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 19 |
+
Title: Method for Implementing a Live Dealer Game <boundary-data type="line-number">
|
| 20 |
+
<confidence value="88">15</confidence>
|
| 21 |
+
</boundary-data>
|
| 22 |
+
Inventors: Martin Paul Moshal, a citizen of South Africa and a resident of Queens Way Quay, Gibraltar Carl Goodwin, a citizen of the United Kingdom and a resident of the Isle of Man <boundary-data type="line-number">20 </boundary-data>
|
| 23 |
+
Grant Smith, a citizen of South Africa and resident of the Isle of Man <boundary-data type="line-number">25 </boundary-data>
|
| 24 |
+
Assignee: Waterleaf Limited Top Floor, <part-num-ref name="Isle of Man Assignee: Waterleaf Limited Top Floor,">14</part-num-ref>
|
| 25 |
+
Athol Street Douglas Isle of Man IM<confidence value="5">1</confidence>
|
| 26 |
+
<confidence value="588">1JA</confidence>
|
| 27 |
+
United Kingdom <boundary-data type="header">
|
| 28 |
+
<confidence value="7">1</confidence>
|
| 29 |
+
</boundary-data>
|
| 30 |
+
<page-break num="2"/>
|
| 31 |
+
</p>
|
| 32 |
+
<heading id="h-2">BACKGROUND</heading>
|
| 33 |
+
<p id="p-2" num="2">In the gaming art, the term "Live Dealer" refers to games in which a player participates in a live game from a location remote from the area of live play, such as a casino. The present disclosure relates to a method of implementing a Live Dealer game, <boundary-data type="line-number">5 </boundary-data>
|
| 34 |
+
and more particularly, to methods of synchronizing a Live Dealer game between a dealer or local player at a live play area and one or more remotely-participating players. </p>
|
| 35 |
+
<p id="p-3" num="3">A Live Dealer game may be available for a variety of live casino games, such as, for example, roulette, baccarat, and blackjack. During a Live Dealer game, a remote player participates in the same game that a local player does. The remote player may <boundary-data type="line-number">10 </boundary-data>
|
| 36 |
+
receive information from the casino, such as what cards have been dealt by a live dealer or played by a local player, and also transmits information to the casino, such as what wagers have been made or cards played by the remote player. Additionally, the information communicated to the remote player from the casino may include a live video feed of game-play at the gaming table, and also an indication of a rank and suit of each <boundary-data type="line-number">15 </boundary-data>
|
| 37 |
+
dealt card as the card is scanned or otherwise sensed by a detector, such as a card reader. </p>
|
| 38 |
+
<p id="p-4" num="4">However, information sent to the remote player may not always be synchronized with information revealed at the gaming table. For example, the indication of the rank and suit of the dealt card may be sent to the remote player as the card is scanned, but this indication may be sent before the card is actually turned face-up to become visible. In <boundary-data type="line-number">20 </boundary-data>
|
| 39 |
+
such a scenario, the remote player may receive an indication of the rank and suit of the card before the card is actually revealed to the local player. </p>
|
| 40 |
+
<p id="p-5" num="5">A lack of synchronization between the live action and the communication to the remote player may lead to a situation where the participating players perceive that they <boundary-data type="header">
|
| 41 |
+
<confidence value="8">2</confidence>
|
| 42 |
+
</boundary-data>
|
| 43 |
+
<page-break num="3"/>
|
| 44 |
+
are at a disadvantage relative to each other. As a consequence, the players may lose confidence in the Live Dealer game, and play less, resulting in less revenue for the game proprietor. </p>
|
| 45 |
+
<boundary-data type="header">
|
| 46 |
+
<confidence value="8">3</confidence>
|
| 47 |
+
</boundary-data>
|
| 48 |
+
<heading id="h-3">SUMMARY</heading>
|
| 49 |
+
<p id="p-6" num="6">
|
| 50 |
+
<page-break num="4"/>
|
| 51 |
+
A method is disclosed for synchronizing a Live Dealer game so that the remote player receives information relating to game-play (e.g., dealt cards and revealed cards) at substantially the same time the information is revealed at the gaming table. In particular, <part-num-ref name="gaming table. In particular,">5</part-num-ref>
|
| 52 |
+
data indicating the rank and suit of a particular dealt card is transmitted to the remote player at substantially the same time that the card is revealed at the actual gaming table. </p>
|
| 53 |
+
<p id="p-7" num="7">In one embodiment, a live feed of game-play at the gaming table is sent to the remote player. During play, a server receives an indication of the rank and suit of the particular dealt card. The server delays transmission of data indicating the rank and suit <part-num-ref name="rank and suit">10</part-num-ref>
|
| 54 |
+
of the particular dealt card to the remote player, however, until it receives a status signal indicating that the particular dealt card has been revealed, or is about to be revealed at the gaming table. </p>
|
| 55 |
+
<p id="p-8" num="8">Accordingly, transmission of the data indicating the rank and suit of the particular dealt card to the remote player is substantially synchronized with revealing the card at the <part-num-ref name="">15</part-num-ref>
|
| 56 |
+
gaming table. </p>
|
| 57 |
+
<p id="p-9" num="9">The status signal may be sent to the server in a variety of circumstances. In one embodiment, the dealer activates a manual switch, and the status signal is then sent from the switch to the server. In another embodiment, the server receives the status signal when the live feed is processed by a real-time image processor, and when the processor <part-num-ref name="processor">20</part-num-ref>
|
| 58 |
+
determines that a predetermined portion of the face of the particular dealt card is visible. </p>
|
| 59 |
+
<p id="p-10" num="10">In yet another embodiment, a Radio Frequency Identification (RFID) tag on the card is read by an RFID reader at approximately the same time the card is revealed, and the RFID reader sends the status signal to the server.</p>
|
| 60 |
+
<boundary-data type="header">
|
| 61 |
+
<confidence value="8">4</confidence>
|
| 62 |
+
</boundary-data>
|
| 63 |
+
<p id="p-11" num="11">
|
| 64 |
+
<page-break num="5"/>
|
| 65 |
+
These as well as other aspects and advantages will become apparent to those of ordinary skill in the art by reading the following detailed description, with reference where appropriate to the accompanying drawings. Further, it should be understood that the embodiments described in this summary and elsewhere are intended to be examples <part-num-ref name="embodiments described in this summary and elsewhere are intended to be examples">5</part-num-ref>
|
| 66 |
+
only and do not necessarily limit the scope of the invention. </p>
|
| 67 |
+
<boundary-data type="header">
|
| 68 |
+
<confidence value="8">5</confidence>
|
| 69 |
+
</boundary-data>
|
| 70 |
+
<heading id="h-4">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 71 |
+
<p id="p-12" num="12">
|
| 72 |
+
<page-break num="6"/>
|
| 73 |
+
Figure 1 is an illustration of an example system where a remote player operating through an electronic gaming device may participate in a Live Dealer game via a communication network. </p>
|
| 74 |
+
<p id="p-13" num="13">5 Figure 2 is a block diagram of an example server and ancillary servers which may be used in carrying out a Live Dealer game in the system Figure 1.</p>
|
| 75 |
+
<p id="p-14" num="14">Figure 3 is an illustration of an example gaming space that includes a multitude of gaming tables, each having its own dealer.</p>
|
| 76 |
+
<p id="p-15" num="15">Figure 4 is an illustration of an example gaming table where a Live Dealer game <part-num-ref name="Live Dealer game">10</part-num-ref>
|
| 77 |
+
may occur. </p>
|
| 78 |
+
<p id="p-16" num="16">Figure 5 is a flow chart depicting functional blocks of a method of executing a Live Dealer game in accordance with one embodiment.</p>
|
| 79 |
+
<p id="p-17" num="17">Figures 6A and 6B illustrate an example bar code reader on a gaming table, and an example bar code on a card, respectively.</p>
|
| 80 |
+
<p id="p-18" num="18">15 Figures 7A and 7B illustrate an example RFID reader placed underneath a gaming table, and an example RFID tag embedded in a card, respectively.</p>
|
| 81 |
+
<p id="p-19" num="19">Figure 8 is an example screen shot of a Live Dealer game display that may be presented to a remote player operating through an electronic gaming device.</p>
|
| 82 |
+
<boundary-data type="header">
|
| 83 |
+
<confidence value="8">6</confidence>
|
| 84 |
+
</boundary-data>
|
| 85 |
+
<heading id="h-5">DETAILED DESCRIPTION</heading>
|
| 86 |
+
<p id="p-20" num="20">
|
| 87 |
+
<page-break num="7"/>
|
| 88 |
+
Figure 1 shows a system <part-num-ref name="system">100</part-num-ref>
|
| 89 |
+
that allows a remotely located player to engage in Live Dealer games. As illustrated, the system <part-num-ref name="system">100</part-num-ref>
|
| 90 |
+
includes a live play area <part-num-ref name="live play area">102</part-num-ref>
|
| 91 |
+
(for example, a casino), a communication network <part-num-ref name="communication network">104,</part-num-ref>
|
| 92 |
+
and an electronic gaming device <part-num-ref name="electronic gaming device">106</part-num-ref>
|
| 93 |
+
<part-num-ref name="">5</part-num-ref>
|
| 94 |
+
(e.g., computer, personal digital assistant, cellular telephone, or other kind of electronic device) for use by a remote player. The live play area <part-num-ref name="live play area">102</part-num-ref>
|
| 95 |
+
comprises a gaming space <part-num-ref name="gaming space">108,</part-num-ref>
|
| 96 |
+
where local players and a dealer are located, a communication link <part-num-ref name="communication link">110,</part-num-ref>
|
| 97 |
+
a server <part-num-ref name="server">112,</part-num-ref>
|
| 98 |
+
and a communication link <part-num-ref name="communication link">114.</part-num-ref>
|
| 99 |
+
The gaming space <part-num-ref name="gaming space">108</part-num-ref>
|
| 100 |
+
may be, for example, a casino or card room. Further, as depicted in Figure 3, the gaming space <part-num-ref name="gaming space">108</part-num-ref>
|
| 101 |
+
may <part-num-ref name="may">10</part-num-ref>
|
| 102 |
+
comprise one or more gaming tables, such as gaming tables <part-num-ref name="comprise one or more gaming tables, such as gaming tables">302</part-num-ref>
|
| 103 |
+
<confidence value="8">-</confidence>
|
| 104 |
+
<part-num-ref name="-">312.</part-num-ref>
|
| 105 |
+
</p>
|
| 106 |
+
<p id="p-21" num="21">The electronic gaming device 106 allows a remote player (or user, more generally) to interact with the live play area <part-num-ref name="live play area">102</part-num-ref>
|
| 107 |
+
by, for example, presenting the remote player with a live feed (either direct feed or animation) of game-play at the live play area <part-num-ref name="live play area">102.</part-num-ref>
|
| 108 |
+
In addition, the electronic gaming device <part-num-ref name="electronic gaming device">106</part-num-ref>
|
| 109 |
+
may receive user input and transmit <part-num-ref name="may receive user input and transmit">15</part-num-ref>
|
| 110 |
+
the user input to the server <part-num-ref name="server">112</part-num-ref>
|
| 111 |
+
via a wireline or wireless interface, for example. </p>
|
| 112 |
+
<p id="p-22" num="22">The communication link 110 connects input devices such as a camera or Radio Frequency Identification ("RFID") reader located at the gaming space <part-num-ref name="gaming space">108</part-num-ref>
|
| 113 |
+
with the server <part-num-ref name="server">112</part-num-ref>
|
| 114 |
+
to provide a live feed to the electronic gaming device <part-num-ref name="electronic gaming device">106.</part-num-ref>
|
| 115 |
+
The link <part-num-ref name="link">110</part-num-ref>
|
| 116 |
+
may be arranged in a wide variety of configurations. For example, the communication link <part-num-ref name="communication link">110</part-num-ref>
|
| 117 |
+
<part-num-ref name="">20</part-num-ref>
|
| 118 |
+
may be arranged as a plurality of communication links such as a local area network coupled to a wireless network. </p>
|
| 119 |
+
<p id="p-23" num="23">The server 112 may be operated by an entity that runs the Live Dealer game or by an entity that is indirectly associated with the Live Dealer game. The server <part-num-ref name="server">112</part-num-ref>
|
| 120 |
+
should <boundary-data type="header">
|
| 121 |
+
<confidence value="8">7</confidence>
|
| 122 |
+
</boundary-data>
|
| 123 |
+
<page-break num="8"/>
|
| 124 |
+
be understood to include a broad category of electronic communication systems that may communicate with one or more devices in the gaming space <part-num-ref name="gaming space">108</part-num-ref>
|
| 125 |
+
and with one or more electronic gaming devices <part-num-ref name="and with one or more electronic gaming devices">106</part-num-ref>
|
| 126 |
+
operated by remote players. For example, the server <part-num-ref name="server">112</part-num-ref>
|
| 127 |
+
will receive gaming data from the electronic gaming device <part-num-ref name="electronic gaming device">106,</part-num-ref>
|
| 128 |
+
such as an indication of <part-num-ref name="indication of">5</part-num-ref>
|
| 129 |
+
cards played, bets wagered, etc. Further, the server <part-num-ref name="server">112</part-num-ref>
|
| 130 |
+
may be arranged to communicate with entities not depicted in Figure 1, such as other gaming devices, a web server, or administrative facilities. </p>
|
| 131 |
+
<p id="p-24" num="24">The server 112 may be arranged in a variety of configurations and may include a communication interface, a processor, and data storage all linked together via a system <part-num-ref name="system">10</part-num-ref>
|
| 132 |
+
bus, for example. As such, the server <part-num-ref name="server">112</part-num-ref>
|
| 133 |
+
may perform functions described below by executing computer-readable program instructions stored in data storage to enable a plurality of electronic gaming devices to each play a separate instance of one or more Live Dealer games, to determine the outcome of game-play decisions and game results at a Live Dealer game, to transmit the game results to one or more electronic gaming <part-num-ref name="game results to one or more electronic gaming">15</part-num-ref>
|
| 134 |
+
devices, to operate in conjunction with a larger online gaming system (e.g., a separate gaming server, an online casino website, or a web server), or to manage a remote player's credit account, for example. Within exemplary embodiments, in addition, the server <part-num-ref name="server">112</part-num-ref>
|
| 135 |
+
also delays a transmission of data indicating rank and suit of a dealt card at the gaming space <part-num-ref name="gaming space">108</part-num-ref>
|
| 136 |
+
to remote players until a status signal indicating the status of the dealt card has <part-num-ref name="dealt card has">20</part-num-ref>
|
| 137 |
+
been received. </p>
|
| 138 |
+
<p id="p-25" num="25">The server 112 may include discrete servers or may be an integrated server. If distributed among different discrete servers, each server may reside remotely from, or locally in, the live play area <part-num-ref name="live play area">102.</part-num-ref>
|
| 139 |
+
For example, figure 2 is a block diagram of an example <boundary-data type="header">
|
| 140 |
+
<confidence value="8">8</confidence>
|
| 141 |
+
</boundary-data>
|
| 142 |
+
<page-break num="9"/>
|
| 143 |
+
server and ancillary servers that may be used in carrying out a Live Dealer game in the system of Figure 1. As shown, the server <part-num-ref name="server">112</part-num-ref>
|
| 144 |
+
may have access to a database server <part-num-ref name="database server">202,</part-num-ref>
|
| 145 |
+
a gaming server <part-num-ref name="gaming server">204,</part-num-ref>
|
| 146 |
+
and an edge server <part-num-ref name="edge server">206</part-num-ref>
|
| 147 |
+
(or a dedicated server, more generally). </p>
|
| 148 |
+
<p id="p-26" num="26">Each server may perform separate functions. For instance, the database server <part-num-ref name="database server">202</part-num-ref>
|
| 149 |
+
may <part-num-ref name="may">5</part-num-ref>
|
| 150 |
+
store game-related information and data, such as, amounts wagered, cards played, etc. </p>
|
| 151 |
+
<p id="p-27" num="27">In addition, the gaming server <part-num-ref name="gaming server">204</part-num-ref>
|
| 152 |
+
may generate data for transmission to the remotely located players, handle remote player registration, and act as a credit facility. </p>
|
| 153 |
+
<p id="p-28" num="28">The gaming server 204 may take a variety of configurations, such as a central gaming server, or alternatively, the gaming server may be arranged to avoid use of a centralized <part-num-ref name="centralized">10</part-num-ref>
|
| 154 |
+
server through a peer-to-peer network, a distributed network, or the like. The gaming server <part-num-ref name="gaming server">204</part-num-ref>
|
| 155 |
+
may determine the outcome of game-play decisions and game results at the Live Dealer game and transmit the results to a remote player at the electronic gaming device <part-num-ref name="electronic gaming device">106</part-num-ref>
|
| 156 |
+
via the communication network <part-num-ref name="communication network">104</part-num-ref>
|
| 157 |
+
and to any other participating remote players at corresponding electronic gaming devices via the communication network <part-num-ref name="communication network">104.</part-num-ref>
|
| 158 |
+
</p>
|
| 159 |
+
<p id="p-29" num="29">15 The gaming server <part-num-ref name="gaming server">204</part-num-ref>
|
| 160 |
+
may be part of a larger online gaming system. For example, such a gaming system may comprise the gaming server <part-num-ref name="gaming server">204</part-num-ref>
|
| 161 |
+
and an online casino website hosted on a casino web server. In one possible arrangement, the online casino website may be accessible by a remote player through the electronic gaming device <part-num-ref name="electronic gaming device">106</part-num-ref>
|
| 162 |
+
via the communication network <part-num-ref name="communication network">104.</part-num-ref>
|
| 163 |
+
Of course, the online casino website <part-num-ref name="online casino website">20</part-num-ref>
|
| 164 |
+
may be connected to a plurality of electronic gaming devices. </p>
|
| 165 |
+
<p id="p-30" num="30">The gaming server 204 may also include a corresponding database with a credit account corresponding to each remote player that participates in the Live Dealer game offered by the online casino. Additionally, the online casino website may enable the <boundary-data type="header">
|
| 166 |
+
<confidence value="8">9</confidence>
|
| 167 |
+
</boundary-data>
|
| 168 |
+
<page-break num="10"/>
|
| 169 |
+
remote player to place wagers in the Live Dealer game and to be presented with a display of the Live Dealer game. </p>
|
| 170 |
+
<p id="p-31" num="31">The illustrative edge server 206 shown in Figure 2 may transfer data between the gaming space <part-num-ref name="gaming space">108</part-num-ref>
|
| 171 |
+
and the communication network <part-num-ref name="communication network">104.</part-num-ref>
|
| 172 |
+
For example, the edge server <part-num-ref name="edge server">5</part-num-ref>
|
| 173 |
+
<part-num-ref name="">206</part-num-ref>
|
| 174 |
+
may receive data from the gaming space <part-num-ref name="gaming space">108</part-num-ref>
|
| 175 |
+
and transmit corresponding data to a remote player participating through the electronic gaming device <part-num-ref name="electronic gaming device">106.</part-num-ref>
|
| 176 |
+
Data received and sent by the edge server <part-num-ref name="edge server">206</part-num-ref>
|
| 177 |
+
may take a variety of forms. For example, the data may comprise a live feed of game-play at the gaming table, and the edge server <part-num-ref name="edge server">206</part-num-ref>
|
| 178 |
+
may broadcast the live feed to the electronic gaming device <part-num-ref name="electronic gaming device">106.</part-num-ref>
|
| 179 |
+
</p>
|
| 180 |
+
<p id="p-32" num="32">10 The communication link <part-num-ref name="communication link">114</part-num-ref>
|
| 181 |
+
couples the server <part-num-ref name="server">112</part-num-ref>
|
| 182 |
+
to the communication network <part-num-ref name="communication network">104</part-num-ref>
|
| 183 |
+
and may be arranged in a variety of configurations. The communication link <part-num-ref name="communication link">114</part-num-ref>
|
| 184 |
+
may be arranged as one or more communication links, e.g. as a local area network, each of which may be arranged as a physical or wireless link. Further, each communication link may send specialized data over the link. For example, one link may <part-num-ref name="link. For example, one link may">15</part-num-ref>
|
| 185 |
+
communicate digital data, while another link may broadcast streaming video, such as a live feed, for example The communication network <part-num-ref name="communication network">104</part-num-ref>
|
| 186 |
+
couples the live play area <part-num-ref name="live play area">102</part-num-ref>
|
| 187 |
+
and the server <part-num-ref name="server">
|
| 188 |
+
<confidence value="5">1</confidence>
|
| 189 |
+
12 </part-num-ref>
|
| 190 |
+
to the electronic gaming device <part-num-ref name="electronic gaming device">106</part-num-ref>
|
| 191 |
+
via the communication link <part-num-ref name="communication link">114.</part-num-ref>
|
| 192 |
+
The communication network <part-num-ref name="communication network">104</part-num-ref>
|
| 193 |
+
allows for unidirectional or bidirectional data <part-num-ref name="allows for unidirectional or bidirectional data">20</part-num-ref>
|
| 194 |
+
communication between the server <part-num-ref name="server">112</part-num-ref>
|
| 195 |
+
and the electronic gaming device <part-num-ref name="electronic gaming device">106.</part-num-ref>
|
| 196 |
+
As an example, the communication network <part-num-ref name="communication network">104</part-num-ref>
|
| 197 |
+
may take the form of the Internet or a telephone network. </p>
|
| 198 |
+
<boundary-data type="header">
|
| 199 |
+
<confidence value="88">10</confidence>
|
| 200 |
+
</boundary-data>
|
| 201 |
+
<p id="p-33" num="33">
|
| 202 |
+
<page-break num="11"/>
|
| 203 |
+
It should be understood that this and other arrangements described herein are for purposes of example only. As such, those skilled in the art will appreciate that other arrangements and other elements (e.g. machines, interfaces, functions, orders, and groupings of functions, etc.) can be used instead, and some elements may be omitted <part-num-ref name="machines, interfaces, functions, orders, and groupings of functions, etc.) can be used instead, and some elements may be omitted">5</part-num-ref>
|
| 204 |
+
altogether according to the desired results. Further, many of the elements that are described are functional entities that may be implemented as discrete or distributed components or in conjunction with other components, in any suitable combination and location. </p>
|
| 205 |
+
<p id="p-34" num="34">Figure 3 is an illustration of an example physical gaming space <part-num-ref name="example physical gaming space">108</part-num-ref>
|
| 206 |
+
of the system <part-num-ref name="system">10</part-num-ref>
|
| 207 |
+
<part-num-ref name="">100</part-num-ref>
|
| 208 |
+
shown in Figure 1. In this example, the gaming space <part-num-ref name="gaming space">108</part-num-ref>
|
| 209 |
+
includes six tables <part-num-ref name="includes six tables">302</part-num-ref>
|
| 210 |
+
- <part-num-ref name="-">312,</part-num-ref>
|
| 211 |
+
and associated card dealers <part-num-ref name="- 312, and associated card dealers">314</part-num-ref>
|
| 212 |
+
- <part-num-ref name="-">324,</part-num-ref>
|
| 213 |
+
input devices <part-num-ref name="- 324, input devices">326</part-num-ref>
|
| 214 |
+
- <part-num-ref name="-">336</part-num-ref>
|
| 215 |
+
(in the form of video cameras), and table-based readers <part-num-ref name="form of video cameras), and table-based readers">338</part-num-ref>
|
| 216 |
+
- <part-num-ref name="-">348</part-num-ref>
|
| 217 |
+
(in the form of RFID readers). </p>
|
| 218 |
+
<p id="p-35" num="35">A live feed of gaming action occurring at the gaming tables <part-num-ref name="gaming tables">302</part-num-ref>
|
| 219 |
+
- <part-num-ref name="-">312</part-num-ref>
|
| 220 |
+
is captured by the cameras <part-num-ref name="cameras">326</part-num-ref>
|
| 221 |
+
- <part-num-ref name="-">336</part-num-ref>
|
| 222 |
+
associated with each table, and the live feed is transmitted to <part-num-ref name="live feed is transmitted to">15</part-num-ref>
|
| 223 |
+
electronic devices of remote players that are participating in gaming occurring at the tables. Game play is synchronized for the remote players by timing the delivery of data indicating the rank and suit of cards to the remote players with the revealing of such cards at the gaming table. A gaming table may also include a display device, such as display devices <part-num-ref name="display device, such as display devices">350</part-num-ref>
|
| 224 |
+
and <part-num-ref name="and">352</part-num-ref>
|
| 225 |
+
associated with the gaming tables <part-num-ref name="gaming tables">304</part-num-ref>
|
| 226 |
+
and <part-num-ref name="and">310,</part-num-ref>
|
| 227 |
+
respectively, for <part-num-ref name="and 310, respectively, for">20</part-num-ref>
|
| 228 |
+
communicating game play of remote players to a dealer. </p>
|
| 229 |
+
<p id="p-36" num="36">Figure 4 is an illustration of an example gaming table <part-num-ref name="example gaming table">400,</part-num-ref>
|
| 230 |
+
such as one shown in Figure 3, where a Live Dealer game may occur. The gaming table <part-num-ref name="gaming table">400</part-num-ref>
|
| 231 |
+
includes a table <part-num-ref name="table">402,</part-num-ref>
|
| 232 |
+
a dealer <part-num-ref name="dealer">404,</part-num-ref>
|
| 233 |
+
dealer and player positions <part-num-ref name="dealer 404, dealer and player positions">406</part-num-ref>
|
| 234 |
+
- <part-num-ref name="-">412,</part-num-ref>
|
| 235 |
+
a card shoe <part-num-ref name="card shoe">414</part-num-ref>
|
| 236 |
+
(if a card-based <boundary-data type="header">
|
| 237 |
+
<confidence value="88">11</confidence>
|
| 238 |
+
</boundary-data>
|
| 239 |
+
<page-break num="12"/>
|
| 240 |
+
game is played, such as baccarat or blackjack), a table-based reader <part-num-ref name="table-based reader">416,</part-num-ref>
|
| 241 |
+
a display device <part-num-ref name="display device">418,</part-num-ref>
|
| 242 |
+
and a video camera <part-num-ref name="video camera">420.</part-num-ref>
|
| 243 |
+
</p>
|
| 244 |
+
<p id="p-37" num="37">The table-based reader 416 can identify the rank and suit of a card, for example, and thus may be an optical detector. If a card-based Live Dealer game is played (such as <part-num-ref name="card-based Live Dealer game is played (such as">5</part-num-ref>
|
| 245 |
+
blackjack or baccarat), the optical detector can capture an image of the face of a card. </p>
|
| 246 |
+
<p id="p-38" num="38">Further, the optical detector may be configured to determine whether a card has been wholly, or partially, revealed at the gaming table <part-num-ref name="gaming table">400,</part-num-ref>
|
| 247 |
+
i.e., the card is turned face-up. As another example, the table-based reader <part-num-ref name="table-based reader">416</part-num-ref>
|
| 248 |
+
may be a bar code reader, and in this instance, a face of each card will contain a unique bar code indicating the card's rank and <part-num-ref name="card's rank and">10</part-num-ref>
|
| 249 |
+
suit (or some kind of unique mark, for example). The bar code reader can then read the bar code on the card as the face of the card is passed over the reader by the dealer <part-num-ref name="dealer">404.</part-num-ref>
|
| 250 |
+
</p>
|
| 251 |
+
<p id="p-39" num="39">As yet another example, the table-based reader <part-num-ref name="table-based reader">416</part-num-ref>
|
| 252 |
+
may be a manual switch, such as a pushbutton or foot pedal, that can be activated or depressed by the dealer <part-num-ref name="dealer">404</part-num-ref>
|
| 253 |
+
to change the betting status of a game or to communicate to the server <part-num-ref name="server">112</part-num-ref>
|
| 254 |
+
that a card has been <part-num-ref name="card has been">15</part-num-ref>
|
| 255 |
+
revealed, i.e., turned face-up. </p>
|
| 256 |
+
<p id="p-40" num="40">As one other example, the table-based reader <part-num-ref name="table-based reader">416</part-num-ref>
|
| 257 |
+
may be an RFID reader, and in this instance, each card may include an RFID tag identifying the rank and suit of the card. </p>
|
| 258 |
+
<p id="p-41" num="41">The magnitude and orientation of a given card's RFID tag may be configured in such a way as to allow the RFID reader to only read the card's RFID tag when the card is face- <part-num-ref name="card is face-">20</part-num-ref>
|
| 259 |
+
up or in the process of being turned face-up by the dealer <part-num-ref name="dealer">404<confidence value="5">.</confidence>
|
| 260 |
+
</part-num-ref>
|
| 261 |
+
Hence, the RFID tag on a given card is read by the RFID reader at approximately the same time that the card is turned face-up or revealed. </p>
|
| 262 |
+
<boundary-data type="header">
|
| 263 |
+
<confidence value="88">12</confidence>
|
| 264 |
+
</boundary-data>
|
| 265 |
+
<p id="p-42" num="42">
|
| 266 |
+
<page-break num="13"/>
|
| 267 |
+
On the gaming table <part-num-ref name="gaming table">402,</part-num-ref>
|
| 268 |
+
the display device <part-num-ref name="display device">418</part-num-ref>
|
| 269 |
+
may include a visual and audio display used to communicate to the dealer the game-play (e.g., hit or stand) and betting decisions made by remote players participating in the Live Dealer game. Such a display may be necessary in games like blackjack, where the outcome of the game is based <part-num-ref name="game is based">5</part-num-ref>
|
| 270 |
+
directly on the game-play decisions made by both local and remote players to the game. </p>
|
| 271 |
+
<p id="p-43" num="43">The camera 420 may be positioned in a variety of locations to capture all the gaming activity occurring at the gaming table <part-num-ref name="gaming table">400.</part-num-ref>
|
| 272 |
+
For example, the camera <part-num-ref name="camera">420</part-num-ref>
|
| 273 |
+
may be situated above the table <part-num-ref name="table">402,</part-num-ref>
|
| 274 |
+
pointed toward the dealer <part-num-ref name="dealer">404,</part-num-ref>
|
| 275 |
+
placed behind the player positions <part-num-ref name="player positions">408</part-num-ref>
|
| 276 |
+
- <part-num-ref name="-">412,</part-num-ref>
|
| 277 |
+
or placed inside or under a rim of the table <part-num-ref name="table">402</part-num-ref>
|
| 278 |
+
and directed toward <part-num-ref name="and directed toward">10</part-num-ref>
|
| 279 |
+
the center of the table <part-num-ref name="table">402</part-num-ref>
|
| 280 |
+
(to capture a dealt card that is viewed by the dealer <part-num-ref name="dealer">404</part-num-ref>
|
| 281 |
+
or local player). The camera <part-num-ref name="camera">420</part-num-ref>
|
| 282 |
+
records a live video feed of game-play at the gaming table <part-num-ref name="gaming table">400,</part-num-ref>
|
| 283 |
+
which is transmitted over the network <part-num-ref name="network">104</part-num-ref>
|
| 284 |
+
shown in Figure 1 to the remote player's gaming device <part-num-ref name="remote player's gaming device">106.</part-num-ref>
|
| 285 |
+
The live feed may include a digital or analog signal representing gaming action captured by the camera <part-num-ref name="camera">420.</part-num-ref>
|
| 286 |
+
</p>
|
| 287 |
+
<p id="p-44" num="44">15 Figure 5 is a flow chart depicting functional blocks of a method of executing a Live Dealer game, such as that at the gaming table <part-num-ref name="gaming table">400,</part-num-ref>
|
| 288 |
+
for example. Initially, a live feed of game-play at the gaming table <part-num-ref name="gaming table">400</part-num-ref>
|
| 289 |
+
is sent to the electronic gaming device <part-num-ref name="electronic gaming device">106</part-num-ref>
|
| 290 |
+
and displayed to the remote player, as shown at block <part-num-ref name="remote player, as shown at block">502.</part-num-ref>
|
| 291 |
+
To do so, the server <part-num-ref name="server">112</part-num-ref>
|
| 292 |
+
will receive the live feed captured by the camera <part-num-ref name="camera">420,</part-num-ref>
|
| 293 |
+
and once the server <part-num-ref name="server">112</part-num-ref>
|
| 294 |
+
detects that a <part-num-ref name="">20</part-num-ref>
|
| 295 |
+
remote player operating through the electronic gaming device <part-num-ref name="electronic gaming device">106</part-num-ref>
|
| 296 |
+
has joined the Live Dealer game, the server <part-num-ref name="server">112</part-num-ref>
|
| 297 |
+
sends the live feed to the remote player. </p>
|
| 298 |
+
<p id="p-45" num="45">Next, as shown at block 504, the server <part-num-ref name="server">112</part-num-ref>
|
| 299 |
+
will receive and store an indication of a rank and suit of a card dealt by the dealer <part-num-ref name="dealer">404</part-num-ref>
|
| 300 |
+
to one of the players in the Live Dealer <boundary-data type="header">
|
| 301 |
+
<confidence value="88">13</confidence>
|
| 302 |
+
</boundary-data>
|
| 303 |
+
<page-break num="14"/>
|
| 304 |
+
game. In one embodiment, a card dealt from the card shoe <part-num-ref name="card shoe">414</part-num-ref>
|
| 305 |
+
may be scanned by the dealer <part-num-ref name="dealer">404</part-num-ref>
|
| 306 |
+
through the table-based reader <part-num-ref name="table-based reader">416</part-num-ref>
|
| 307 |
+
while the card is face-down prior to dealing the card to a player. In another embodiment, the dealer <part-num-ref name="dealer">404</part-num-ref>
|
| 308 |
+
may only scan the card through the table-based reader <part-num-ref name="table-based reader">416</part-num-ref>
|
| 309 |
+
when that card is to be revealed. In either <part-num-ref name="when that card is to be revealed. In either">5</part-num-ref>
|
| 310 |
+
instance, when the dealt card is scanned through the table-based reader <part-num-ref name="table-based reader">416,</part-num-ref>
|
| 311 |
+
the server <part-num-ref name="server">112</part-num-ref>
|
| 312 |
+
receives and stores an indication of the card's rank and suit. At this point, the server <part-num-ref name="server">112</part-num-ref>
|
| 313 |
+
has knowledge of the card's rank and suit, however, remote players do not. Of course, if the dealt card is the remote player's card, and the game being played at the table is one in which the remote player can view the card, then, at this point in time, the <part-num-ref name="">10</part-num-ref>
|
| 314 |
+
remote player can have knowledge of the card's suit and rank. </p>
|
| 315 |
+
<p id="p-46" num="46">As noted above, to determine the card's rank and suit, the table-based reader <part-num-ref name="table-based reader">416</part-num-ref>
|
| 316 |
+
may be a bar code reader that reads bar codes as the card is scanned through the reader that are present on the face of the card and indicate the card's rank and suit. Figure 6A is an illustration of a card <part-num-ref name="card">602</part-num-ref>
|
| 317 |
+
being scanned through a bar code reader <part-num-ref name="bar code reader">604</part-num-ref>
|
| 318 |
+
by the dealer <part-num-ref name="dealer">15</part-num-ref>
|
| 319 |
+
<part-num-ref name="">404.</part-num-ref>
|
| 320 |
+
Figure 6B illustrates an example card including a unique bar code <part-num-ref name="unique bar code">606</part-num-ref>
|
| 321 |
+
on the face of the card <part-num-ref name="card">602.</part-num-ref>
|
| 322 |
+
</p>
|
| 323 |
+
<p id="p-47" num="47">As another example, the table-based reader may be a RFID reader that reads RFID tags embedded within the card as the card is scanned through or over the RFID reader. When the RFID reader reads the RFID tag on a card, the reader sends a signal to <part-num-ref name="signal to">20</part-num-ref>
|
| 324 |
+
the server <part-num-ref name="server">112</part-num-ref>
|
| 325 |
+
indicating the tag for the scanned card, thereby providing the server <part-num-ref name="server">112</part-num-ref>
|
| 326 |
+
with an indication of the rank and suit of the card. Figure 7A is an illustration of a card <part-num-ref name="card">702</part-num-ref>
|
| 327 |
+
being scanned through or over an RFID reader <part-num-ref name="RFID reader">704</part-num-ref>
|
| 328 |
+
by the dealer <part-num-ref name="dealer">404.</part-num-ref>
|
| 329 |
+
Figure 7B illustrates an example RFID tag <part-num-ref name="example RFID tag">706</part-num-ref>
|
| 330 |
+
embedded in the card <part-num-ref name="card">702.</part-num-ref>
|
| 331 |
+
</p>
|
| 332 |
+
<boundary-data type="header">
|
| 333 |
+
<confidence value="88">14</confidence>
|
| 334 |
+
</boundary-data>
|
| 335 |
+
<p id="p-48" num="48">
|
| 336 |
+
<page-break num="15"/>
|
| 337 |
+
Alternatively, the table-based reader may be a camera that captures an image of the card, which is sent to the server <part-num-ref name="server">112.</part-num-ref>
|
| 338 |
+
The server <part-num-ref name="server">112</part-num-ref>
|
| 339 |
+
may then analyze the image to determine the identity of the card. </p>
|
| 340 |
+
<p id="p-49" num="49">Referring back to Figure 5, after receiving an indication of the card's rank and <part-num-ref name="card's rank and">5</part-num-ref>
|
| 341 |
+
suit, a status of the dealt card is determined, as shown at block <part-num-ref name="dealt card is determined, as shown at block">506,</part-num-ref>
|
| 342 |
+
in order to determine whether to transmit the identity of the card's rank and suit to the remote players. The status of a dealt card may include one of the following: (i) not revealed to all players at the gaming area (e.g., the card is still face-down at the live gaming area on the table 402), (ii) in the process of being revealed (e.g., when the dealer is physically turning the card <part-num-ref name="card">10</part-num-ref>
|
| 343 |
+
face-up), or (iii) revealed (e.g., when the card is face-up at the live gaming area and lying flat on the table 402). </p>
|
| 344 |
+
<p id="p-50" num="50">If the card's status is "not revealed," then the server <part-num-ref name="server">112</part-num-ref>
|
| 345 |
+
will not receive a status signal, or will receive a signal indicating that the card has yet to be revealed at the live gaming area. In this instance, the server <part-num-ref name="server">112</part-num-ref>
|
| 346 |
+
delays transmission of data indicating the <part-num-ref name="">15</part-num-ref>
|
| 347 |
+
rank and suit of the dealt card to the remote player until it receives a signal indicating that the card should be revealed, as indicated at block <part-num-ref name="card should be revealed, as indicated at block">508.</part-num-ref>
|
| 348 |
+
The server <part-num-ref name="server">112</part-num-ref>
|
| 349 |
+
may delay transmission of the card's identity by not deriving the rank and suit of the dealt card until the card is to be revealed, for example. </p>
|
| 350 |
+
<p id="p-51" num="51">However, if the status of the card is either "in the process of being revealed," or <part-num-ref name="process of being revealed," or">20</part-num-ref>
|
| 351 |
+
"revealed," then the server <part-num-ref name="server">112</part-num-ref>
|
| 352 |
+
will receive a signal indicating that the card should be revealed. Alternatively, the server <part-num-ref name="server">112</part-num-ref>
|
| 353 |
+
may receive the reveal card status signal only when the status of the card is "revealed." When the server <part-num-ref name="server">112</part-num-ref>
|
| 354 |
+
receives the signal indicating that the card should be revealed then the server <part-num-ref name="server">112</part-num-ref>
|
| 355 |
+
transmits data indicating <boundary-data type="header">
|
| 356 |
+
<confidence value="88">15</confidence>
|
| 357 |
+
</boundary-data>
|
| 358 |
+
<page-break num="16"/>
|
| 359 |
+
the card's rank and suit to the electronic gaming device <part-num-ref name="electronic gaming device">106,</part-num-ref>
|
| 360 |
+
as shown at block <part-num-ref name="electronic gaming device 106, as shown at block">510.</part-num-ref>
|
| 361 |
+
The transmission indicating the rank and suit of the dealt card may take a variety of configurations. For example, the indication may take the form of a bar code or RFID tag ID corresponding to the card. Software on the device <part-num-ref name="device">106</part-num-ref>
|
| 362 |
+
may correlate the code or tag <part-num-ref name="code or tag">5</part-num-ref>
|
| 363 |
+
to a particular playing card. </p>
|
| 364 |
+
<p id="p-52" num="52">Therefore, because transmission of the card's rank and suit occurs at approximately the same time that the card is revealed at the live gaming table, the live feed showing the card being revealed is substantially synchronized with the electronic gaming device <part-num-ref name="electronic gaming device">106</part-num-ref>
|
| 365 |
+
displaying graphic displays of the card's rank and suit. Hence, the <part-num-ref name="">10</part-num-ref>
|
| 366 |
+
remote player is given an indication of the card's rank and suit via a live feed window and graphic displays at substantially the same time. </p>
|
| 367 |
+
<p id="p-53" num="53">Figure 8 is a screenshot of an example Live Dealer game display <part-num-ref name="example Live Dealer game display">800</part-num-ref>
|
| 368 |
+
that may be presented to a remote player through the electronic gaming device <part-num-ref name="electronic gaming device">106.</part-num-ref>
|
| 369 |
+
The remote player may download appropriate gaming software from the server <part-num-ref name="server">112</part-num-ref>
|
| 370 |
+
to log on and <part-num-ref name="to log on and">15</part-num-ref>
|
| 371 |
+
register with the server <part-num-ref name="server">112</part-num-ref>
|
| 372 |
+
to play in the Live Dealer game. In this example, the server <part-num-ref name="server">112</part-num-ref>
|
| 373 |
+
registers the user as a remote player to the gaming table <part-num-ref name="gaming table">400</part-num-ref>
|
| 374 |
+
in the live play area <part-num-ref name="live play area">102.</part-num-ref>
|
| 375 |
+
</p>
|
| 376 |
+
<p id="p-54" num="54">The remote player is then presented with a Live Dealer game display <part-num-ref name="Live Dealer game display">800.</part-num-ref>
|
| 377 |
+
The display <part-num-ref name="display">800</part-num-ref>
|
| 378 |
+
includes a live feed window <part-num-ref name="live feed window">802,</part-num-ref>
|
| 379 |
+
a chat-room box <part-num-ref name="chat-room box">804,</part-num-ref>
|
| 380 |
+
a graphic display <part-num-ref name="graphic display">806</part-num-ref>
|
| 381 |
+
of the gaming table, and a graphic display <part-num-ref name="graphic display">814</part-num-ref>
|
| 382 |
+
of a rank and suit of a dealt card. The live feed <part-num-ref name="live feed">20</part-num-ref>
|
| 383 |
+
window <part-num-ref name="window">802</part-num-ref>
|
| 384 |
+
may show the table <part-num-ref name="table">402,</part-num-ref>
|
| 385 |
+
the dealer <part-num-ref name="dealer">404,</part-num-ref>
|
| 386 |
+
and a card <part-num-ref name="card">816</part-num-ref>
|
| 387 |
+
as it is being revealed. The graphic display <part-num-ref name="graphic display">806</part-num-ref>
|
| 388 |
+
may include, for example, a graphic display of the dealer <part-num-ref name="dealer">818,</part-num-ref>
|
| 389 |
+
the table <part-num-ref name="table">820,</part-num-ref>
|
| 390 |
+
the rank and suit of the card <part-num-ref name="card">822</part-num-ref>
|
| 391 |
+
that is being revealed (which corresponds to the card <part-num-ref name="card">816</part-num-ref>
|
| 392 |
+
in the live feed window 802), player positions <part-num-ref name="live feed window 802), player positions">808</part-num-ref>
|
| 393 |
+
- <part-num-ref name="-">812,</part-num-ref>
|
| 394 |
+
and <boundary-data type="header">
|
| 395 |
+
<confidence value="88">16</confidence>
|
| 396 |
+
</boundary-data>
|
| 397 |
+
<page-break num="17"/>
|
| 398 |
+
a simulation of game-play occurring at the gaming table <part-num-ref name="gaming table">400</part-num-ref>
|
| 399 |
+
(not depicted). The card <part-num-ref name="card">816</part-num-ref>
|
| 400 |
+
is displayed via graphic display <part-num-ref name="is displayed via graphic display">814</part-num-ref>
|
| 401 |
+
when the card is in the process of being revealed. </p>
|
| 402 |
+
<p id="p-55" num="55">The server 112 will make a determination as to whether the dealt card is revealed, <part-num-ref name="dealt card is revealed,">5</part-num-ref>
|
| 403 |
+
or whether the card is about to be revealed to the local players (or revealed at the gaming table, more generally). If the card has not been revealed and is not in the process of being revealed, then the live feed window <part-num-ref name="live feed window">802</part-num-ref>
|
| 404 |
+
will reflect this fact (i.e., the live feed will show that the card is face-down). At this point, the server <part-num-ref name="server">112</part-num-ref>
|
| 405 |
+
delays transmission of data indicating the rank and suit of the dealt card to the remote player. Hence, the remote <part-num-ref name="remote">10</part-num-ref>
|
| 406 |
+
player will receive no indication of the rank and suit of the card, either through the live feed window <part-num-ref name="live feed window">802,</part-num-ref>
|
| 407 |
+
the graphic display <part-num-ref name="graphic display">806,</part-num-ref>
|
| 408 |
+
or through the graphic display <part-num-ref name="graphic display">814.</part-num-ref>
|
| 409 |
+
Thus, synchronization as to the revealing of a dealt card between the local and remote players exists. </p>
|
| 410 |
+
<p id="p-56" num="56">As the card is revealed at the gaming table (or within a short period of time before <part-num-ref name="short period of time before">15</part-num-ref>
|
| 411 |
+
or after the card is revealed), the server <part-num-ref name="server">112</part-num-ref>
|
| 412 |
+
receives a status signal, and responsively transmits data to the remote player indicating the rank and suit of the dealt card. Further, the data may update the graphic displays <part-num-ref name="graphic displays">806</part-num-ref>
|
| 413 |
+
and <part-num-ref name="and">814</part-num-ref>
|
| 414 |
+
with the rank and suit of the dealt card. </p>
|
| 415 |
+
<p id="p-57" num="57">Thus, the Live Dealer game is synchronized in such a way that the graphic <part-num-ref name="graphic">20</part-num-ref>
|
| 416 |
+
displays <part-num-ref name="displays">806</part-num-ref>
|
| 417 |
+
and <part-num-ref name="and">814</part-num-ref>
|
| 418 |
+
of the rank and suit of the card will appear to the remote player at approximately the same time the card is revealed at the gaming table, as shown in the live feed window <part-num-ref name="live feed window">802.</part-num-ref>
|
| 419 |
+
This inspires confidence in the players in the integrity of the Live Dealer game and promotes loyalty to the game proprietor. </p>
|
| 420 |
+
<boundary-data type="header">
|
| 421 |
+
<confidence value="88">17</confidence>
|
| 422 |
+
</boundary-data>
|
| 423 |
+
<p id="p-58" num="58">
|
| 424 |
+
<page-break num="18"/>
|
| 425 |
+
The server 112 makes the determination as to whether the dealt card should be revealed through receipt of the status signal. The server <part-num-ref name="server">112</part-num-ref>
|
| 426 |
+
may receive the card status signal from a variety of devices and in a variety of ways. In one embodiment, the server <part-num-ref name="server">112</part-num-ref>
|
| 427 |
+
receives the status signal from a manual switch. The manual switch may be a <part-num-ref name="">5</part-num-ref>
|
| 428 |
+
pushbutton or a foot pedal, for example. During play, when the dealer <part-num-ref name="dealer">404</part-num-ref>
|
| 429 |
+
has either revealed a card or is in the process of revealing a card, the dealer <part-num-ref name="dealer">404</part-num-ref>
|
| 430 |
+
activates the switch. When the switch is activated, the switch sends a "reveal card" status signal to the server <part-num-ref name="server">112</part-num-ref>
|
| 431 |
+
. The receipt of the status signal at the server <part-num-ref name="server">112</part-num-ref>
|
| 432 |
+
indicates that the card is revealed or is about to be revealed at the gaming table. To maintain synchronization, the <part-num-ref name="">10</part-num-ref>
|
| 433 |
+
server <part-num-ref name="server">112</part-num-ref>
|
| 434 |
+
then sends data to the electronic gaming device <part-num-ref name="electronic gaming device">106</part-num-ref>
|
| 435 |
+
indicating the rank and suit of the revealed card to the remote player. </p>
|
| 436 |
+
<p id="p-59" num="59">The server 112 may also receive the card status signal from the table-based reader <part-num-ref name="table-based reader">416.</part-num-ref>
|
| 437 |
+
For example, if the dealer <part-num-ref name="dealer">404</part-num-ref>
|
| 438 |
+
only passes the card over or through the table-based reader <part-num-ref name="table-based reader">416</part-num-ref>
|
| 439 |
+
just prior to or upon revealing the card, once the table-based reader reads the <part-num-ref name="">15</part-num-ref>
|
| 440 |
+
card the table-based reader <part-num-ref name="table-based reader">416</part-num-ref>
|
| 441 |
+
will also send a signal to the signal <part-num-ref name="signal">112</part-num-ref>
|
| 442 |
+
indicating that the card is being revealed at the gaming table. </p>
|
| 443 |
+
<p id="p-60" num="60">As another example, if the table-based reader <part-num-ref name="table-based reader">416</part-num-ref>
|
| 444 |
+
is an RFID reader, then the RFID reader may read the RFID tag in the card only when the status of the card is "revealed" or "in the process of being revealed," and may not read the RFID tag when the <part-num-ref name="">20</part-num-ref>
|
| 445 |
+
card is "not revealed." This may be accomplished in a variety of ways. For example, the RFID reader may be configured to detect the orientation of the radio signals emitted from the RFID tag. An antenna of the RFID tag may direct the RFID tag's signals downward when the card is face-up and upward when the card is face-down. In this instance, when <boundary-data type="header">
|
| 446 |
+
<confidence value="88">18</confidence>
|
| 447 |
+
</boundary-data>
|
| 448 |
+
<page-break num="19"/>
|
| 449 |
+
the RFID reader detects that the tag's signals are upward (i.e., the card is face-down), then the RFID reader will not read the RFID tag. On the other hand, when the RFID reader detects that the tag's signals are downward, or generally downwards (i.e., the card is face-up, or in the process of being turned face-up by the dealer 404), then the RFID <part-num-ref name="RFID">5</part-num-ref>
|
| 450 |
+
reader will read the RFID tag on the card, and then transmit a signal to the server <part-num-ref name="server">112</part-num-ref>
|
| 451 |
+
indicating that the card should be revealed to the remote player. </p>
|
| 452 |
+
<p id="p-61" num="61">As another example, the RFID reader may be configured to detect the magnitude of the radio signals emitted the RFID tag, and based on the magnitude of the signals from the RFID tag, the RFID reader will read or not read the RFID tag. Magnitudes of the <part-num-ref name="">10</part-num-ref>
|
| 453 |
+
radio signals from the RFID tag may be altered by shielding one side of the RFID tag so as to diminish the magnitude of the radio signals on the shielded side, for example. Upon reading the RFID tag, the RFID reader will then transmit a signal to the server <part-num-ref name="server">112</part-num-ref>
|
| 454 |
+
indicating that the card should be revealed to the remote player. </p>
|
| 455 |
+
<p id="p-62" num="62">In yet another example, real-time image processing of a card shown in the live <part-num-ref name="live">15</part-num-ref>
|
| 456 |
+
feed may trigger the server <part-num-ref name="server">112</part-num-ref>
|
| 457 |
+
to reveal the rank and suit of the card to the remote player. The live feed captured by the camera <part-num-ref name="camera">420</part-num-ref>
|
| 458 |
+
could be processed by a real-time image processor to determine the status of a card shown in the live feed. If, for example, the real-time image processor determines that a predetermined portion of the face of the particular dealt card is visible, the camera <part-num-ref name="camera">420</part-num-ref>
|
| 459 |
+
may determine that the status of the card is <part-num-ref name="card is">20</part-num-ref>
|
| 460 |
+
either "revealed" or "in the process of being revealed," and thus transmit the status signal to the server <part-num-ref name="server">112.</part-num-ref>
|
| 461 |
+
The predetermined portion of the face card that triggers a determination that the card is either "revealed" or "in the process of being revealed" may vary from, for example, 5% of the face card to 100% of the face card. In one <boundary-data type="header">
|
| 462 |
+
<confidence value="88">19</confidence>
|
| 463 |
+
</boundary-data>
|
| 464 |
+
<page-break num="20"/>
|
| 465 |
+
embodiment, a dealt card is deemed revealed at the gaming table when 75% of the face of the card is recognized through commercially available image analysis techniques. </p>
|
| 466 |
+
<p id="p-63" num="63">In these examples, when the table-based reader <part-num-ref name="table-based reader">416</part-num-ref>
|
| 467 |
+
signals the server <part-num-ref name="server">112</part-num-ref>
|
| 468 |
+
to reveal the card to the remote player, the table-based reader <part-num-ref name="table-based reader">416</part-num-ref>
|
| 469 |
+
may also include within <part-num-ref name="may also include within">5</part-num-ref>
|
| 470 |
+
the signal the identification of the card's rank and suit. Thus, the server <part-num-ref name="server">112</part-num-ref>
|
| 471 |
+
may receive an indication of the card's rank and suit at approximately the same time that the server <part-num-ref name="server">112</part-num-ref>
|
| 472 |
+
receives a status signal indicating that the card is either revealed or about to be revealed. </p>
|
| 473 |
+
<p id="p-64" num="64">Since many modifications, variations, and changes in detail can be made to the <part-num-ref name="">10</part-num-ref>
|
| 474 |
+
described embodiments, it is intended that all matters in the foregoing description and shown in the accompanying drawings be interpreted as illustrative and not in a limiting sense. Further, it is intended to be understood that the following clauses further describe aspects of the present application. </p>
|
| 475 |
+
<p id="p-65" num="65">(1) An apparatus for synchronizing a live dealer game, comprising:</p>
|
| 476 |
+
<p id="p-66" num="66">15 a server communicatively coupled to at least one client device through a communication network; a camera to capture a live feed of game-play at a gaming table;</p>
|
| 477 |
+
<p id="p-67" num="67">a reader to read an indication of a rank and suit of a dealt card at the gaming table; and a processor coupled to the server, camera, and reader, wherein the processor: (i) sends the live feed of game-play to the at least one client device, (ii) receives from the reader the <part-num-ref name="">20</part-num-ref>
|
| 478 |
+
indication of the rank and suit of the dealt card; (iii) delays transmission of data indicating the rank and suit of the dealt card to the at least one client device until the server receives a status signal indicating the status of the dealt card; and (iv) upon receipt of the status signal by the server, transmits the data indicating the rank and suit of the <boundary-data type="header">
|
| 479 |
+
<confidence value="88">20</confidence>
|
| 480 |
+
</boundary-data>
|
| 481 |
+
<page-break num="21"/>
|
| 482 |
+
dealt card to the at least one client device so that the transmission is substantially synchronized with an appearance of the dealt card in the live feed of game-play. </p>
|
| 483 |
+
<p id="p-68" num="68">(2) The apparatus of clause (1), wherein the processor delays transmission of data indicating the rank and suit of the dealt card by not deriving the rank and suit of the dealt <part-num-ref name="dealt">5</part-num-ref>
|
| 484 |
+
card until the server receives the status signal. </p>
|
| 485 |
+
<p id="p-69" num="69">(3) The apparatus of clause <part-num-ref name="apparatus of clause">(1)</part-num-ref>
|
| 486 |
+
or (2), wherein the server sends the live feed via the Internet, as a broadcast signal, or over a wireless network. </p>
|
| 487 |
+
<p id="p-70" num="70">(4) The apparatus of clause (1), <part-num-ref name="apparatus of clause (1),">(2)</part-num-ref>
|
| 488 |
+
or (3), wherein the reader captures an image of the dealt card, the image comprises an indication of the rank and suit of the dealt card, <part-num-ref name="dealt card,">10</part-num-ref>
|
| 489 |
+
the reader sends the image to the server, and the processor responsively determines the rank and suit of the dealt card from the image. </p>
|
| 490 |
+
<p id="p-71" num="71">(5) The apparatus of clause (4), wherein the processor determines the rank and suit of the dealt card only after the status signal is received.</p>
|
| 491 |
+
<p id="p-72" num="72">(6) The apparatus of clause (1), <part-num-ref name="apparatus of clause (1),">(2)</part-num-ref>
|
| 492 |
+
or (3), wherein the reader comprises a bar <part-num-ref name="bar">15</part-num-ref>
|
| 493 |
+
code reader, each card contains a bar code identifying the card's rank and suit, the bar code reader reads the bar code of the dealt card when the face of the dealt card is passed over the reader, the bar code reader sends bar code information to the processor, and the processor responsively determines the rank and suit of the dealt card. </p>
|
| 494 |
+
<p id="p-73" num="73">(7) The apparatus of clause (6), wherein the processor determines the rank and <part-num-ref name="rank and">20</part-num-ref>
|
| 495 |
+
suit of the dealt card from the bar code only after the status signal is received. </p>
|
| 496 |
+
<p id="p-74" num="74">(8) The apparatus of clause (1), <part-num-ref name="apparatus of clause (1),">(2)</part-num-ref>
|
| 497 |
+
or (3), wherein the reader comprises a Radio Frequency Identification (RFID) reader, an RFID tag identifying a card's rank and suit is embedded within each card, the RFID reader reads the RFID tag of the card when the <boundary-data type="header">
|
| 498 |
+
<confidence value="88">21</confidence>
|
| 499 |
+
</boundary-data>
|
| 500 |
+
<page-break num="22"/>
|
| 501 |
+
card is passed over the reader, the RFID reader sends an indication of the tag to the server, and the processor responsively determines the rank and suit of the card from the indication of the tag. </p>
|
| 502 |
+
<p id="p-75" num="75">(9) The apparatus of clause (8), wherein the processor determines the rank and <part-num-ref name="rank and">5</part-num-ref>
|
| 503 |
+
suit from the indication of the tag only after the status signal is received. </p>
|
| 504 |
+
<p id="p-76" num="76">(10) The apparatus of clause (1), (2), (3), (4), (5), (6), (7), <part-num-ref name="apparatus of clause (1), (2), (3), (4), (5), (6), (7),">(8)</part-num-ref>
|
| 505 |
+
or (9), further comprising a second reader that determines the status of the dealt card and transmits the status signal to the server. </p>
|
| 506 |
+
<p id="p-77" num="77">(11) The apparatus of clause (10), wherein the second reader transmits the status <part-num-ref name="status">10</part-num-ref>
|
| 507 |
+
signal to the server when the status of the dealt card is revealed or in the process of being revealed. </p>
|
| 508 |
+
<p id="p-78" num="78">(12) The apparatus of clause <part-num-ref name="apparatus of clause">(10)</part-num-ref>
|
| 509 |
+
or (11), wherein the second reader comprises an Radio Frequency Identification (RFID) reader, each card is embedded with an RFID tag, the RFID reader reads the RFID tag of the dealt card at approximately the same time <part-num-ref name="same time">15</part-num-ref>
|
| 510 |
+
the card is lifted off the table, and wherein the RFID reader responsively sends the status signal to the processor. </p>
|
| 511 |
+
<p id="p-79" num="79">(13) The apparatus of clause <part-num-ref name="apparatus of clause">(10)</part-num-ref>
|
| 512 |
+
or (11), wherein the reader and second reader each comprise an RFID reader, and wherein the server receives an indication of the card's rank and suit from the first reader at approximately the same time the server <part-num-ref name="server">20</part-num-ref>
|
| 513 |
+
receives the status signal from the second reader indicating that the card is revealed. </p>
|
| 514 |
+
<p id="p-80" num="80">(14) The apparatus of clause <part-num-ref name="apparatus of clause">(10)</part-num-ref>
|
| 515 |
+
or (11), wherein the second reader comprises a manual switch, the manual switch is activated when the status of card is revealed or in the <boundary-data type="header">
|
| 516 |
+
<confidence value="88">22</confidence>
|
| 517 |
+
</boundary-data>
|
| 518 |
+
<page-break num="23"/>
|
| 519 |
+
process of being revealed, and the switch sends the status signal to the server when the switch is activated. </p>
|
| 520 |
+
<p id="p-81" num="81">(15) The apparatus of clause <part-num-ref name="apparatus of clause">(14)</part-num-ref>
|
| 521 |
+
wherein the manual switch comprises a pushbutton. </p>
|
| 522 |
+
<p id="p-82" num="82">5 (16) The apparatus of clause <part-num-ref name="apparatus of clause">(14)</part-num-ref>
|
| 523 |
+
wherein the manual switch comprises a foot pedal. </p>
|
| 524 |
+
<p id="p-83" num="83">(17) The apparatus of any preceding clause wherein the camera comprises a plurality of cameras positioned in a plurality of locations at the gaming table.</p>
|
| 525 |
+
<p id="p-84" num="84">(18) The apparatus of clause (1), (2), (3), <part-num-ref name="apparatus of clause (1), (2), (3),">(4)</part-num-ref>
|
| 526 |
+
or (5), wherein the processor <part-num-ref name="processor">10</part-num-ref>
|
| 527 |
+
performs real-time image processing of a particular dealt card as shown in the live feed to determine the status of the dealt card. </p>
|
| 528 |
+
<p id="p-85" num="85">(19) The apparatus of clause (1), (2), (3), (4), (5), (6), (7), (8), (9), (10), (11), <part-num-ref name="apparatus of clause (1), (2), (3), (4), (5), (6), (7), (8), (9), (10), (11),">(17)</part-num-ref>
|
| 529 |
+
or (18), wherein the processor determines the status of the dealt card by determining that a predetermined portion of a face of a particular dealt card is visible. </p>
|
| 530 |
+
<p id="p-86" num="86">15 (20) The apparatus of clause <part-num-ref name="apparatus of clause">(19)</part-num-ref>
|
| 531 |
+
wherein a predetermined portion of the face of a particular dealt card comprises 75% of the face of the card. </p>
|
| 532 |
+
<p id="p-87" num="87">(21) A live dealer game display comprising: a live feed window comprising a view of a dealt card as the card is revealed, or in the process of being revealed; and a graphic display of a rank and suit of the dealt card that is revealed, or in the process of <part-num-ref name="process of">20</part-num-ref>
|
| 533 |
+
being revealed, wherein the graphic display of the rank and suit of the dealt card is synchronized with the appearance of the dealt card shown in the live feed. </p>
|
| 534 |
+
<p id="p-88" num="88">(22) The display of clause (21), further comprising a graphic display of simulated game-play at the table, wherein the graphic display of simulated game-play at the table <boundary-data type="header">
|
| 535 |
+
<confidence value="88">23</confidence>
|
| 536 |
+
</boundary-data>
|
| 537 |
+
<page-break num="24"/>
|
| 538 |
+
includes a display of a rank and suit of a dealt card that is revealed or in the process of being revealed, and the display of the rank and suit of the dealt card is synchronized with the appearance of the dealt card shown in the live feed. </p>
|
| 539 |
+
<p id="p-89" num="89">(23) The display of clause (22), wherein (i) the graphic display of the rank and <part-num-ref name="rank and">5</part-num-ref>
|
| 540 |
+
suit of the dealt card that is revealed, or in the process of being revealed, (ii) the appearance of the dealt card shown in the live feed, and (iii) the display of the rank and suit of the dealt card within the graphic display of the simulated game are all synchronized. </p>
|
| 541 |
+
<p id="p-90" num="90">(24) A computer readable medium having stored therein instructions for causing <part-num-ref name="computer readable medium having stored therein instructions for causing">10</part-num-ref>
|
| 542 |
+
a processor to execute the steps described in any of the preceding clauses. </p>
|
| 543 |
+
<p id="p-91" num="91">(25) A method of synchronizing a live dealer game, wherein the live dealer game has a dealer at a gaming table in a live play area that deals cards, wherein the cards have a rank and suit, and at least one remote player participating through an electronic gaming device in communication with a server, comprising: sending a live feed of game-play at <part-num-ref name="live feed of game-play at">15</part-num-ref>
|
| 544 |
+
the gaming table to the remote player via the Internet, as a broadcast signal, or over a wireless network; receiving at the server an indication of the rank and suit of a particular dealt card; delaying transmission of data indicating the rank and suit of the particular dealt card to the electronic gaming device until the server receives a status signal indicating the status of the dealt card; and, upon receipt of the status signal by the server, <part-num-ref name="server,">20</part-num-ref>
|
| 545 |
+
transmitting the data indicating the rank and suit of the particular dealt card to the remote player, wherein the transmission is substantially synchronized with revealing the particular dealt card at the gaming table. </p>
|
| 546 |
+
<boundary-data type="header">
|
| 547 |
+
<confidence value="88">24</confidence>
|
| 548 |
+
</boundary-data>
|
| 549 |
+
<p id="p-92" num="92">
|
| 550 |
+
<page-break num="25"/>
|
| 551 |
+
(26) The method of clause (25), wherein the status signal is received when the status of the particular dealt card is revealed. </p>
|
| 552 |
+
<p id="p-93" num="93">(27) The method of clause (25), wherein the status signal is received when the status of the particular dealt card is in the process of being revealed.</p>
|
| 553 |
+
<p id="p-94" num="94">5 (28) The method of clause (25), <part-num-ref name="method of clause (25),">(26)</part-num-ref>
|
| 554 |
+
or (27), wherein delaying transmission of data indicating the rank and suit of the particular dealt card comprises preventing the server from deriving the rank and suit of the particular dealt card until the server receives the status signal. </p>
|
| 555 |
+
<p id="p-95" num="95">(29) The method of clause (25), (26), <part-num-ref name="method of clause (25), (26),">(27)</part-num-ref>
|
| 556 |
+
or (28), further comprising performing <part-num-ref name="or (28), further comprising performing">10</part-num-ref>
|
| 557 |
+
real-time image processing of a particular dealt card as shown in the live feed to determine the status of the card. </p>
|
| 558 |
+
<p id="p-96" num="96">(30) The method of clause (29), wherein performing real-time image processing of a particular dealt card shown in the live-feed comprises determining that a predetermined portion of the face of a particular dealt card is visible.</p>
|
| 559 |
+
<p id="p-97" num="97">15 (31) The method of clause (30), wherein a predetermined portion of the face of a particular dealt card comprises 75% of the face of the card.</p>
|
| 560 |
+
<p id="p-98" num="98">(32) The method of clause (25), (26), (27), (28), (29), <part-num-ref name="method of clause (25), (26), (27), (28), (29),">(30)</part-num-ref>
|
| 561 |
+
or (31), wherein receiving an indication of a particular dealt card's rank and suit comprises receiving an image of the card at the server. </p>
|
| 562 |
+
<p id="p-99" num="99">20 (33) The method of clause (32), wherein an indication of the rank and suit of a particular dealt card at the server is derived by scanning the card through a reader.</p>
|
| 563 |
+
<boundary-data type="header">
|
| 564 |
+
<confidence value="88">25</confidence>
|
| 565 |
+
</boundary-data>
|
| 566 |
+
<p id="p-100" num="100">
|
| 567 |
+
<page-break num="26"/>
|
| 568 |
+
(34) The method of clause (25), (26), (27), (28), (29), (30), (31), <part-num-ref name="method of clause (25), (26), (27), (28), (29), (30), (31),">(32)</part-num-ref>
|
| 569 |
+
or (33), further comprising analyzing the image of the card to determine the rank and suit of the card. </p>
|
| 570 |
+
<p id="p-101" num="101">(35) The method of clause (25), (26), <part-num-ref name="method of clause (25), (26),">(27)</part-num-ref>
|
| 571 |
+
or (28), wherein the indication of the <part-num-ref name="">5</part-num-ref>
|
| 572 |
+
rank and suit of the particular card dealt is generated by an RFID reader reading the RFID tag on a particular dealt card. </p>
|
| 573 |
+
<p id="p-102" num="102">(36) The method of clause (35), wherein the RFID reader sends the status signal to the server at approximately the same time that the dealt card is revealed.</p>
|
| 574 |
+
<p id="p-103" num="103">(37) The method of clause (35), wherein the RFID reader sends the status <part-num-ref name="status">10</part-num-ref>
|
| 575 |
+
signal to the server at approximately the same time that the dealt card is in the process of being revealed. </p>
|
| 576 |
+
<p id="p-104" num="104">(38) The method of clause (35), <part-num-ref name="method of clause (35),">(36)</part-num-ref>
|
| 577 |
+
or (37), wherein the RFID tag embedded in a card emits a radio signal in a particular orientation with respect the card, and receiving the status signal comprises the RFID reader reading the RFID tag of a particular card <part-num-ref name="particular card">15</part-num-ref>
|
| 578 |
+
only when the radio signal has an orientation corresponding to the particular card being face-up, or to the particular card being in the process of being turned face-up. </p>
|
| 579 |
+
<p id="p-105" num="105">(39) The method of clause (35), <part-num-ref name="method of clause (35),">(36)</part-num-ref>
|
| 580 |
+
or (37), wherein the RFID tag embedded in a card emits a radio signal that has a lower magnitude on one side of the card than the other, and receiving the status signal comprises the RFID reader detecting the magnitude <part-num-ref name="magnitude">20</part-num-ref>
|
| 581 |
+
of the signal and reading the RFID tag only when the signal has a magnitude that corresponds to the card being face-up, or to the card being in the process of being turned face-up. </p>
|
| 582 |
+
<boundary-data type="header">
|
| 583 |
+
<confidence value="88">26</confidence>
|
| 584 |
+
</boundary-data>
|
| 585 |
+
<p id="p-106" num="106">
|
| 586 |
+
<page-break num="27"/>
|
| 587 |
+
Various embodiments have been described. Those skilled in the art will understand, however, that changes and modifications may be made to the embodiments described without departing from the true scope and spirit of the present invention, which is defined by the following claims. </p>
|
| 588 |
+
<boundary-data type="header">
|
| 589 |
+
<confidence value="88">27</confidence>
|
| 590 |
+
</boundary-data>
|
| 591 |
+
</description>
|
| 592 |
+
</us-patent-application>
|
| 593 |
+
|
applicant/11526192.xml
ADDED
|
@@ -0,0 +1,41 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11526192</doc-number>
|
| 8 |
+
<date>2006-11-03</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">In the Specification:</p>
|
| 14 |
+
<p id="p-2" num="2">On page 1, line 14, please amend the following paragraph:</p>
|
| 15 |
+
<p id="p-3" num="3">1. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of United States Patent Application No. <confidence value="284">[TO</confidence>
|
| 16 |
+
<confidence value="86">Be</confidence>
|
| 17 |
+
Assign<confidence value="8">e</confidence>
|
| 18 |
+
d <confidence value="68">by</confidence>
|
| 19 |
+
USPT<confidence value="42">O}</confidence>
|
| 20 |
+
<confidence value="666666666">11/526,19</confidence>
|
| 21 |
+
3, entitled STERILIZING CUTTING SYSTEM, naming Edward S. Boyden, Roderick A. Hyde, Muriel Y. Ishikawa, Eric C. </p>
|
| 22 |
+
<p id="p-4" num="4">Leuthardt, Nathan P. Myhrvold, Dennis J. Rivet, Michael A. Smith, Thomas A.</p>
|
| 23 |
+
<p id="p-5" num="5">Weaver, and Lowell L. Wood, Jr. as inventors, filed 22 September <part-num-ref name="September">2006,</part-num-ref>
|
| 24 |
+
which is currently co-pending, or is an application of which a currently co-pending application is entitled to the benefit of the filing date. </p>
|
| 25 |
+
<p id="p-6" num="6">On page 1, line 23, please amend the following paragraph:</p>
|
| 26 |
+
<p id="p-7" num="7">2. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of United States Patent Application No. <confidence value="54">TO</confidence>
|
| 27 |
+
<confidence value="86">Be</confidence>
|
| 28 |
+
As<confidence value="8">s</confidence>
|
| 29 |
+
igned <confidence value="88">by</confidence>
|
| 30 |
+
USPT<confidence value="42">O}</confidence>
|
| 31 |
+
<confidence value="6666686">11/526,</confidence>
|
| 32 |
+
090, entitled STERILIZING CUTTING METHOD, naming Edward S. Boyden, Roderick A. Hyde, Muriel Y. Ishikawa, Eric C. </p>
|
| 33 |
+
<p id="p-8" num="8">Leuthardt, Nathan P. Myhrvold, Dennis J. Rivet, Michael A. Smith, Thomas A.</p>
|
| 34 |
+
<p id="p-9" num="9">Weaver, and Lowell L. Wood, Jr. as inventors, filed 22 September <part-num-ref name="September">2006,</part-num-ref>
|
| 35 |
+
which is currently co-pending, or is an application of which a currently co-pending application is entitled to the benefit of the filing date. </p>
|
| 36 |
+
<p id="p-10" num="10">
|
| 37 |
+
<confidence value="888">-2-</confidence>
|
| 38 |
+
</p>
|
| 39 |
+
</description>
|
| 40 |
+
</us-patent-application>
|
| 41 |
+
|
applicant/11545906.xml
ADDED
|
@@ -0,0 +1,351 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11545906</doc-number>
|
| 8 |
+
<date>2006-10-11</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">
|
| 14 |
+
<confidence value="2222222">Attomey</confidence>
|
| 15 |
+
Docket No. 10031.001400 E <confidence value="8">V</confidence>
|
| 16 |
+
<confidence value="6">8</confidence>
|
| 17 |
+
<confidence value="886">410</confidence>
|
| 18 |
+
<confidence value="8">7</confidence>
|
| 19 |
+
<confidence value="88">53</confidence>
|
| 20 |
+
<confidence value="8">6</confidence>
|
| 21 |
+
<confidence value="88">2U</confidence>
|
| 22 |
+
<confidence value="8">S</confidence>
|
| 23 |
+
</boundary-data>
|
| 24 |
+
<heading id="h-1">IN-LINE FURNACE CONVEYORS WITH INTEGRATED WAFER</heading>
|
| 25 |
+
<heading id="h-2">RETAINERS</heading>
|
| 26 |
+
<p id="p-1" num="1">Inventors: William P. Mulligan and Thomas Pass <boundary-data type="line-number">
|
| 27 |
+
<confidence value="8">5</confidence>
|
| 28 |
+
</boundary-data>
|
| 29 |
+
</p>
|
| 30 |
+
<heading id="h-3">BACKGROUND OF THE INVENTION</heading>
|
| 31 |
+
<p id="p-2" num="2">1. Field of the Invention The present invention relates generally to semiconductor wafer processing equipment, and more particularly but not exclusively to in-line furnaces.</p>
|
| 32 |
+
<p id="p-3" num="3">
|
| 33 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 34 |
+
2. Description of the Background Art Wafer processing furnaces are employed in the fabrication of semiconductor devices, including integrated circuits and solar cells. Examples of fabrication processes where furnaces are employed include diffusion and annealing. In an in-line furnace, wafers to be processed are placed on wafer boats, which in turn are placed on a <boundary-data type="line-number">15 </boundary-data>
|
| 35 |
+
conveyor that carries the boats from one end of the furnace to another. After the boats have gone through the furnace, the boats are lifted off the conveyor and the processed wafers are removed from the boats. In some in-line furnaces that do not use boats, the wafers are placed flat on the conveyor during processing. </p>
|
| 36 |
+
<p id="p-4" num="4">Embodiments of the present invention provide improved techniques for efficiently <part-num-ref name="present invention provide improved techniques for efficiently">20</part-num-ref>
|
| 37 |
+
transporting wafers through an in-line furnace. </p>
|
| 38 |
+
<boundary-data type="header">
|
| 39 |
+
<confidence value="888">-1-</confidence>
|
| 40 |
+
</boundary-data>
|
| 41 |
+
<boundary-data type="header">
|
| 42 |
+
<confidence value="2222222">Attomey</confidence>
|
| 43 |
+
Docket No. 10031.001400 </boundary-data>
|
| 44 |
+
<heading id="h-4">SUMMARY</heading>
|
| 45 |
+
<p id="p-5" num="5">
|
| 46 |
+
<page-break num="2"/>
|
| 47 |
+
In one embodiment, an in-line furnace includes a continuous conveyor configured to hold wafers at an angle relative to ground. The conveyor may have fixedly integrated wafer retainers configured to hold the wafers in slots. The conveyor may be formed by <boundary-data type="line-number">5 </boundary-data>
|
| 48 |
+
several segments that are joined together. Each of the segments may include a base and a set of wafer retainers formed thereon. The conveyor may be driven to move the wafers through a chamber of the furnace, where the wafers are thermally processed. </p>
|
| 49 |
+
<p id="p-6" num="6">These and other features of the present invention will be readily apparent to persons of ordinary skill in the art upon reading the entirety of this disclosure, which <boundary-data type="line-number">10 </boundary-data>
|
| 50 |
+
includes the accompanying drawings and claims. </p>
|
| 51 |
+
<heading id="h-5">DESCRIPTION OF THE DRAWINGS</heading>
|
| 52 |
+
<p id="p-7" num="7">FIG. 1(a) schematically shows a side view of an in-line furnace in accordance with an embodiment of the present invention.</p>
|
| 53 |
+
<p id="p-8" num="8">
|
| 54 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 55 |
+
FIG. 1(b) schematically shows a perspective view of a conveyor of a transport mechanism in the furnace of FIG. 1(a). </p>
|
| 56 |
+
<p id="p-9" num="9">FIG. 2(a) is a side view schematically showing a conveyor in accordance with an embodiment of the present invention.</p>
|
| 57 |
+
<p id="p-10" num="10">FIGS. 2(b) and 2(c) are top views schematically showing how segments of a <boundary-data type="line-number">20 </boundary-data>
|
| 58 |
+
conveyor may be joined together in accordance with embodiments of the present invention. </p>
|
| 59 |
+
<boundary-data type="header">
|
| 60 |
+
<confidence value="888">-2-</confidence>
|
| 61 |
+
</boundary-data>
|
| 62 |
+
<boundary-data type="header">Attorney Docket No. 10031.001400</boundary-data>
|
| 63 |
+
<p id="p-11" num="11">
|
| 64 |
+
<page-break num="3"/>
|
| 65 |
+
FIGS. 3(a), 3(b), 3(c), 3(d) and 3(e) schematically show front views of conveyors in accordance with embodiments of the present invention. </p>
|
| 66 |
+
<p id="p-12" num="12">FIGS. 4(a), 4(b), 5(a), 5(b), 6(a), and 6(b) schematically show various views of conveyors in accordance with embodiments of the present invention.</p>
|
| 67 |
+
<p id="p-13" num="13">
|
| 68 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 69 |
+
FIG. 7 shows a flow diagram of a method of processing a wafer in an in-line furnace in accordance with an embodiment of the present invention. </p>
|
| 70 |
+
<p id="p-14" num="14">The use of the same reference label in different drawings indicates the same or like components. Drawings are not necessarily to scale unless otherwise noted.</p>
|
| 71 |
+
<heading id="h-6">DETAILED DESCRIPTION</heading>
|
| 72 |
+
<p id="p-15" num="15">
|
| 73 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 74 |
+
In the present disclosure, numerous specific details are provided, such as examples of apparatus, components, and methods, to provide a thorough understanding of embodiments of the invention. Persons of ordinary skill in the art will recognize, however, that the invention can be practiced without one or more of the <boundary-data type="line-number">15 </boundary-data>
|
| 75 |
+
specific details. In other instances, well-known details are not shown or described to avoid obscuring aspects of the invention. </p>
|
| 76 |
+
<p id="p-16" num="16">Many solar companies use in-line furnaces where wafers are placed flat on the conveyor. Relative to batch furnaces, in-line furnaces have the advantage of continuous processing suitable for high volume manufacturing. Additionally, each <boundary-data type="line-number">20 </boundary-data>
|
| 77 |
+
wafer sees the exact same thermal profile, unlike in a batch furnace where temperature uniformity across the tube can be an issue. Relative to in-line furnaces with wafers lying flat on the conveyor, in-line furnaces with wafers oriented vertically, such as in <boundary-data type="header">
|
| 78 |
+
<confidence value="888">-3-</confidence>
|
| 79 |
+
</boundary-data>
|
| 80 |
+
<page-break num="4"/>
|
| 81 |
+
<boundary-data type="header">
|
| 82 |
+
<confidence value="2222222">Attomey</confidence>
|
| 83 |
+
Docket No. 10031.001400 </boundary-data>
|
| 84 |
+
embodiments of the present invention or for boats on conveyors, have the advantage of higher wafer area output for the same belt speed, which allows much shorter furnaces. </p>
|
| 85 |
+
<p id="p-17" num="17">For example, 10cm x 10cm wafers (100 cm2 area) gapped by 1cm on a continuous conveyor running at <part-num-ref name="continuous conveyor running at">11</part-num-ref>
|
| 86 |
+
<confidence value="222222">cm/min</confidence>
|
| 87 |
+
will process <part-num-ref name="cm/min will process">1</part-num-ref>
|
| 88 |
+
<confidence value="222222222">wafer/min</confidence>
|
| 89 |
+
<part-num-ref name="wafer/min">(100</part-num-ref>
|
| 90 |
+
cm2/min) when placed flat <boundary-data type="line-number">5 </boundary-data>
|
| 91 |
+
on the conveyor. In contrast, if these same wafers were vertically oriented with a 1<confidence value="88">cm</confidence>
|
| 92 |
+
gap on a continuous conveyor, processing of <part-num-ref name="continuous conveyor, processing of">11</part-num-ref>
|
| 93 |
+
<confidence value="2222222222">wafers/min</confidence>
|
| 94 |
+
(or <part-num-ref name="wafers/min (or">1100</part-num-ref>
|
| 95 |
+
cm2/min) can be achieved. By eliminating the boats, embodiments of the present invention can take advantage of the benefits of vertical wafer processing without the need for complex mechanisms or manual returns associated with boats. This also simplifies the <boundary-data type="line-number">10 </boundary-data>
|
| 96 |
+
loading/unloading automation of the furnace. </p>
|
| 97 |
+
<p id="p-18" num="18">FIG. 1(a) schematically shows a side view of an in-line furnace <part-num-ref name="in-line furnace">100</part-num-ref>
|
| 98 |
+
in accordance with an embodiment of the present invention. In the example of F<confidence value="5">I</confidence>
|
| 99 |
+
G. 1(a), the furnace <part-num-ref name="furnace">100</part-num-ref>
|
| 100 |
+
includes a processing chamber <part-num-ref name="processing chamber">110</part-num-ref>
|
| 101 |
+
and a transport mechanism <part-num-ref name="transport mechanism">150.</part-num-ref>
|
| 102 |
+
</p>
|
| 103 |
+
<p id="p-19" num="19">The transport mechanism 150 may include a drive mechanism <part-num-ref name="drive mechanism">154</part-num-ref>
|
| 104 |
+
and a conveyor <part-num-ref name="conveyor">152.</part-num-ref>
|
| 105 |
+
</p>
|
| 106 |
+
<p id="p-20" num="20">
|
| 107 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 108 |
+
A plurality of conveyor supports 153 supports the conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 109 |
+
and prevents it from sagging. In one embodiment, the conveyor supports <part-num-ref name="conveyor supports">153</part-num-ref>
|
| 110 |
+
comprise rollers placed underneath the conveyor <part-num-ref name="conveyor">152.</part-num-ref>
|
| 111 |
+
A continuous rolling or non-rolling conveyor support may also be used without detracting from the merits of the present invention. </p>
|
| 112 |
+
<p id="p-21" num="21">The conveyor 152 provides a continuously rotating platform on which a plurality <boundary-data type="line-number">20 </boundary-data>
|
| 113 |
+
of wafers <part-num-ref name="plurality of wafers">101</part-num-ref>
|
| 114 |
+
may be placed. As will be more apparent below, the conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 115 |
+
may include integrated wafer retainers that may support wafers <part-num-ref name="may include integrated wafer retainers that may support wafers">101</part-num-ref>
|
| 116 |
+
vertically or at an angle (i.e., greater than zero degree) relative to the ground (and the conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 117 |
+
as in FIG. </p>
|
| 118 |
+
<p id="p-22" num="22">1(a)). In the example of FIG. 1(a), the conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 119 |
+
loops forward and backward within <boundary-data type="header">
|
| 120 |
+
<confidence value="888">-4-</confidence>
|
| 121 |
+
</boundary-data>
|
| 122 |
+
<page-break num="5"/>
|
| 123 |
+
<boundary-data type="header">
|
| 124 |
+
<confidence value="2222222">Attomey</confidence>
|
| 125 |
+
Docket No. 10031.001400 </boundary-data>
|
| 126 |
+
the chamber <part-num-ref name="chamber">110.</part-num-ref>
|
| 127 |
+
In other embodiments, the conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 128 |
+
may loop in one direction through the interior of the chamber <part-num-ref name="chamber">110</part-num-ref>
|
| 129 |
+
and return outside the chamber <part-num-ref name="chamber">110.</part-num-ref>
|
| 130 |
+
In embodiments where the conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 131 |
+
loops outside the chamber <part-num-ref name="chamber">110,</part-num-ref>
|
| 132 |
+
the portion of the conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 133 |
+
outside the chamber <part-num-ref name="chamber">110</part-num-ref>
|
| 134 |
+
may run through a chase to protect the <boundary-data type="line-number">
|
| 135 |
+
<confidence value="5">5</confidence>
|
| 136 |
+
</boundary-data>
|
| 137 |
+
conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 138 |
+
and the wafers it carries from contamination. The conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 139 |
+
may extend beyond the chamber <part-num-ref name="chamber">110</part-num-ref>
|
| 140 |
+
or enclosed within the chamber <part-num-ref name="chamber">110.</part-num-ref>
|
| 141 |
+
In either case, a human operator or automation equipment may load an unprocessed wafer <part-num-ref name="unprocessed wafer">101</part-num-ref>
|
| 142 |
+
on a loading end of the chamber <part-num-ref name="chamber">110</part-num-ref>
|
| 143 |
+
and pick up a processed wafer <part-num-ref name="processed wafer">101</part-num-ref>
|
| 144 |
+
on the pick-up end of the chamber <part-num-ref name="chamber">110.</part-num-ref>
|
| 145 |
+
The chamber <part-num-ref name="chamber">110</part-num-ref>
|
| 146 |
+
may perform thermal processing on the wafer <boundary-data type="line-number">10 </boundary-data>
|
| 147 |
+
<part-num-ref name="wafer">101,</part-num-ref>
|
| 148 |
+
such diffusion or annealing, for example. Only some of the wafers <part-num-ref name="wafers">101</part-num-ref>
|
| 149 |
+
and conveyor supports <part-num-ref name="and conveyor supports">153</part-num-ref>
|
| 150 |
+
are labeled in FIG. 1(a) for clarity of illustration. </p>
|
| 151 |
+
<p id="p-23" num="23">In operation, wafers 101 to be processed may be placed on the conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 152 |
+
on the loading end of the chamber <part-num-ref name="chamber">110.</part-num-ref>
|
| 153 |
+
The drive mechanism <part-num-ref name="drive mechanism">154</part-num-ref>
|
| 154 |
+
rotates the conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 155 |
+
in a direction toward the pick-up end of the chamber <part-num-ref name="chamber">110.</part-num-ref>
|
| 156 |
+
This moves the wafers <boundary-data type="line-number">15 </boundary-data>
|
| 157 |
+
<part-num-ref name="wafers">101</part-num-ref>
|
| 158 |
+
into the chamber <part-num-ref name="chamber">110</part-num-ref>
|
| 159 |
+
where the wafers <part-num-ref name="wafers">101</part-num-ref>
|
| 160 |
+
are heated for thermal processing. </p>
|
| 161 |
+
<p id="p-24" num="24">Processed wafers 101 emerge on the pick-up end of the chamber <part-num-ref name="chamber">110</part-num-ref>
|
| 162 |
+
for pick-up. </p>
|
| 163 |
+
<p id="p-25" num="25">FIG. 1(b) schematically shows a perspective view of the conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 164 |
+
in relation to the drive mechanism <part-num-ref name="drive mechanism">154</part-num-ref>
|
| 165 |
+
in one embodiment of the present invention. The drive mechanism <part-num-ref name="drive mechanism">154</part-num-ref>
|
| 166 |
+
may comprise a cylinder with gears rotated by a motor (not shown) on <boundary-data type="line-number">20 </boundary-data>
|
| 167 |
+
an axis <part-num-ref name="axis">155,</part-num-ref>
|
| 168 |
+
for example. The drive mechanism <part-num-ref name="drive mechanism">154</part-num-ref>
|
| 169 |
+
may also include other components, such as idlers. Other ways of driving the conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 170 |
+
may also be used without detracting from the merits of the present invention. </p>
|
| 171 |
+
<boundary-data type="header">
|
| 172 |
+
<confidence value="7">-</confidence>
|
| 173 |
+
<confidence value="77">5-</confidence>
|
| 174 |
+
</boundary-data>
|
| 175 |
+
<boundary-data type="header">Attorney Docket No. 10031.001400</boundary-data>
|
| 176 |
+
<p id="p-26" num="26">
|
| 177 |
+
<page-break num="6"/>
|
| 178 |
+
The conveyor 152 may be made of a low impurity level material that will not degrade the properties of the wafers being processed, such as quartz or silicon carbide (SiC). In one embodiment, the conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 179 |
+
comprises a plurality of rigid segments that are joined together to allow a continuous conveyor <part-num-ref name="continuous conveyor">152</part-num-ref>
|
| 180 |
+
to flex in at least one <boundary-data type="line-number">5 </boundary-data>
|
| 181 |
+
direction. The conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 182 |
+
may include integrated wafer retainers that hold wafers at an angle relative to the ground or the conveyor's plane of travel. The conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 183 |
+
may be implemented as a belt, chain, or other type of conveyors. </p>
|
| 184 |
+
<p id="p-27" num="27">FIG. 2(a) is a side view schematically showing further details of the conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 185 |
+
in accordance with an embodiment of the present invention. In the example of FIG. </p>
|
| 186 |
+
<p id="p-28" num="28">
|
| 187 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 188 |
+
2(a), the conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 189 |
+
comprises a plurality of segments <part-num-ref name="plurality of segments">202</part-num-ref>
|
| 190 |
+
that are joined together to form a continuous loop. Each segment <part-num-ref name="continuous loop. Each segment">202</part-num-ref>
|
| 191 |
+
may include a base <part-num-ref name="base">232</part-num-ref>
|
| 192 |
+
and a plurality of wafer retainers <part-num-ref name="plurality of wafer retainers">231.</part-num-ref>
|
| 193 |
+
The wafer retainers <part-num-ref name="wafer retainers">231</part-num-ref>
|
| 194 |
+
may form slots for holding wafers <part-num-ref name="may form slots for holding wafers">101,</part-num-ref>
|
| 195 |
+
which in the example of FIG. 2(a) are vertical relative to the base <part-num-ref name="base">232.</part-num-ref>
|
| 196 |
+
In general, the wafer retainers <part-num-ref name="wafer retainers">231</part-num-ref>
|
| 197 |
+
hold the wafers <part-num-ref name="wafers">101</part-num-ref>
|
| 198 |
+
vertically or at an angle relative to the ground. </p>
|
| 199 |
+
<p id="p-29" num="29">
|
| 200 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 201 |
+
This increases wafer density inside the chamber <part-num-ref name="chamber">110</part-num-ref>
|
| 202 |
+
and allows the transport mechanism <part-num-ref name="transport mechanism">150</part-num-ref>
|
| 203 |
+
to travel slower for the same wafer throughput compared to furnaces where wafers are laid horizontally flat on conveyors. Advantageously, the chamber <part-num-ref name="chamber">110</part-num-ref>
|
| 204 |
+
may be made shorter and thus at a lower cost compared to conventional furnaces. The orientation of the wafers <part-num-ref name="wafers">101</part-num-ref>
|
| 205 |
+
on the conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 206 |
+
also minimizes wafer contact with the <boundary-data type="line-number">20 </boundary-data>
|
| 207 |
+
transport mechanism <part-num-ref name="transport mechanism">150.</part-num-ref>
|
| 208 |
+
Elimination of wafer boats on the conveyor <part-num-ref name="conveyor">152</part-num-ref>
|
| 209 |
+
simplifies wafer processing operations using the furnace <part-num-ref name="furnace">100,</part-num-ref>
|
| 210 |
+
thus reducing the cost of processing the wafers <part-num-ref name="wafers">101.</part-num-ref>
|
| 211 |
+
</p>
|
| 212 |
+
<boundary-data type="header">
|
| 213 |
+
<confidence value="888">-6-</confidence>
|
| 214 |
+
</boundary-data>
|
| 215 |
+
<boundary-data type="header">
|
| 216 |
+
<confidence value="2222222">Attomey</confidence>
|
| 217 |
+
Docket No. 10031.001400 </boundary-data>
|
| 218 |
+
<p id="p-30" num="30">
|
| 219 |
+
<page-break num="7"/>
|
| 220 |
+
FIGS. 2(b) and 2(c) are top views schematically showing how segments of a conveyor may be joined in accordance with embodiments of the present invention. </p>
|
| 221 |
+
<p id="p-31" num="31">Wafer retainers are not shown in FIGS. 2(b) and 2(c) for clarity of illustration. In the example of FIG. 2(b), the conveyor comprises a plurality of segments 202A, which are <boundary-data type="line-number">5 </boundary-data>
|
| 222 |
+
joined together by pins <part-num-ref name="plurality of segments 202A, which are joined together by pins">203.</part-num-ref>
|
| 223 |
+
Each segment 202A has a centrally located tab on one end and a centrally located cutout on the other. A tab of one segment 202A fits into the cutout of another to form a continuous conveyor. In the example of FIG. 2(c), each segment 202<confidence value="5">B</confidence>
|
| 224 |
+
has an offset tab on each end. The tabs of the segments 202<confidence value="5">B</confidence>
|
| 225 |
+
may be joined together by pins <part-num-ref name="segments 202B may be joined together by pins">213</part-num-ref>
|
| 226 |
+
to form a continuous conveyor. Other segment shapes and <boundary-data type="line-number">10 </boundary-data>
|
| 227 |
+
ways of joining them to form a continuous, flexible conveyor may also be used without detracting from the merits of the present invention. </p>
|
| 228 |
+
<p id="p-32" num="32">FIGS. 3(a), 3(b), 3(c), 3(d), and 3(e) schematically show front views of conveyors in accordance with embodiments of the present invention. In one embodiment, a wafer <part-num-ref name="wafer">101</part-num-ref>
|
| 229 |
+
comprises a semiconductor wafer with substantially straight edges that may be <boundary-data type="line-number">15 </boundary-data>
|
| 230 |
+
supported along the length of a wafer retainer. Preferably, a wafer <part-num-ref name="wafer">101</part-num-ref>
|
| 231 |
+
comprises a square or semi-square wafer that has at least two straight edges at a fixed angle, such as those used for solar cells. </p>
|
| 232 |
+
<p id="p-33" num="33">In FIG. 3(a), the wafer <part-num-ref name="wafer">101</part-num-ref>
|
| 233 |
+
is mounted vertically on the conveyor <part-num-ref name="conveyor">152,</part-num-ref>
|
| 234 |
+
with one of its straight edges resting on the base <part-num-ref name="base">232</part-num-ref>
|
| 235 |
+
(see also F<confidence value="5">I</confidence>
|
| 236 |
+
G. 2(a)). Wafer retainers <part-num-ref name="(see also FIG. 2(a)). Wafer retainers">231</part-num-ref>
|
| 237 |
+
on <boundary-data type="line-number">20 </boundary-data>
|
| 238 |
+
the front and back surfaces of the wafer <part-num-ref name="wafer">101</part-num-ref>
|
| 239 |
+
secure the wafer <part-num-ref name="wafer">101</part-num-ref>
|
| 240 |
+
on the conveyor <part-num-ref name="conveyor">152.</part-num-ref>
|
| 241 |
+
</p>
|
| 242 |
+
<p id="p-34" num="34">A single conveyor 152 is shown in FIG. 3(a), but two coplanar conveyors <part-num-ref name="is shown in FIG. 3(a), but two coplanar conveyors">152</part-num-ref>
|
| 243 |
+
that travel in unison in the same direction may also be used. </p>
|
| 244 |
+
<boundary-data type="header">
|
| 245 |
+
<confidence value="888">-7-</confidence>
|
| 246 |
+
</boundary-data>
|
| 247 |
+
<boundary-data type="header">
|
| 248 |
+
<confidence value="2222222">Attomey</confidence>
|
| 249 |
+
Docket No. 10031.001400 </boundary-data>
|
| 250 |
+
<p id="p-35" num="35">
|
| 251 |
+
<page-break num="8"/>
|
| 252 |
+
In FIG. 3(b), the wafer <part-num-ref name="wafer">101</part-num-ref>
|
| 253 |
+
is still mounted vertically relative to the ground but is now supported by two conveyors <part-num-ref name="ground but is now supported by two conveyors">152</part-num-ref>
|
| 254 |
+
that are at a fixed angle (e.g., <part-num-ref name="">90</part-num-ref>
|
| 255 |
+
degrees) relative to one another. This configuration prevents lateral (side to side) movement of the wafer <part-num-ref name="wafer">101,</part-num-ref>
|
| 256 |
+
and thus stabilizes the wafer <part-num-ref name="wafer">101</part-num-ref>
|
| 257 |
+
more securely compared to a single conveyor or <boundary-data type="line-number">5 </boundary-data>
|
| 258 |
+
two coplanar conveyors. The two conveyors <part-num-ref name="two conveyors">152</part-num-ref>
|
| 259 |
+
travel in unison in the same direction to move the wafer <part-num-ref name="wafer">101</part-num-ref>
|
| 260 |
+
through the furnace. </p>
|
| 261 |
+
<p id="p-36" num="36">In FIG. 3(c), the conveyor 152A has wafer retainers <part-num-ref name="conveyor 152A has wafer retainers">331</part-num-ref>
|
| 262 |
+
formed at a fixed angle relative to one another. The straight edges of the wafer <part-num-ref name="wafer">101</part-num-ref>
|
| 263 |
+
rest on slots formed by wafer retainers <part-num-ref name="rest on slots formed by wafer retainers">331</part-num-ref>
|
| 264 |
+
on the front and back surfaces of the wafer <part-num-ref name="wafer">101.</part-num-ref>
|
| 265 |
+
The embodiment <boundary-data type="line-number">10 </boundary-data>
|
| 266 |
+
of FIG. 3(c) is the same as that of FIG. 3(b) except that the wafer retainers <part-num-ref name="wafer retainers">331</part-num-ref>
|
| 267 |
+
share the same base <part-num-ref name="same base">332.</part-num-ref>
|
| 268 |
+
This advantageously allows the use of a single conveyor 152A in the furnace, while still preventing lateral movement of the wafer <part-num-ref name="wafer">101.</part-num-ref>
|
| 269 |
+
</p>
|
| 270 |
+
<p id="p-37" num="37">In FIG. 3(d), the conveyor 152B has wafer retainers <part-num-ref name="conveyor 152B has wafer retainers">341</part-num-ref>
|
| 271 |
+
that have significant vertical relief to provide even more lateral support to the wafer <part-num-ref name="wafer">101</part-num-ref>
|
| 272 |
+
even when using a <boundary-data type="line-number">15 </boundary-data>
|
| 273 |
+
single conveyor. In the embodiment of FIG. 3(d), the wafer retainers <part-num-ref name="wafer retainers">341</part-num-ref>
|
| 274 |
+
are formed at the edges of the base <part-num-ref name="base">342</part-num-ref>
|
| 275 |
+
and are perpendicular thereto. The straight edges of the wafer <part-num-ref name="wafer">101</part-num-ref>
|
| 276 |
+
rest on slots formed by the wafer retainers <part-num-ref name="wafer retainers">341</part-num-ref>
|
| 277 |
+
on the front and back surfaces of the wafer <part-num-ref name="wafer">101.</part-num-ref>
|
| 278 |
+
</p>
|
| 279 |
+
<p id="p-38" num="38">For increased throughput, a conveyor may include several lanes of wafer <boundary-data type="line-number">20 </boundary-data>
|
| 280 |
+
retainers per row. In FIG. 3(e), the conveyor 152F has several (three in the example) wafer retainers <part-num-ref name="example) wafer retainers">351</part-num-ref>
|
| 281 |
+
on a base <part-num-ref name="base">352.</part-num-ref>
|
| 282 |
+
The straight edges of the wafers <part-num-ref name="wafers">101</part-num-ref>
|
| 283 |
+
rest on slots formed by the wafer retainers <part-num-ref name="wafer retainers">351</part-num-ref>
|
| 284 |
+
on the front and back surfaces of the wafers <part-num-ref name="wafers">101,</part-num-ref>
|
| 285 |
+
and <boundary-data type="header">
|
| 286 |
+
<confidence value="888">-8-</confidence>
|
| 287 |
+
</boundary-data>
|
| 288 |
+
<page-break num="9"/>
|
| 289 |
+
<boundary-data type="header">
|
| 290 |
+
<confidence value="2222222">Attomey</confidence>
|
| 291 |
+
Docket No. 10031<confidence value="5">.</confidence>
|
| 292 |
+
001400 </boundary-data>
|
| 293 |
+
substantially line up to form a row of wafers. The conveyor 152F is configured to support several wafers <part-num-ref name="conveyor 152F is configured to support several wafers">101</part-num-ref>
|
| 294 |
+
side by side in a row. </p>
|
| 295 |
+
<p id="p-39" num="39">Wafer retainers may be integrated with the conveyor by forming relatively thick segments and then cutting slots in the segments. In that embodiment, the wafer <boundary-data type="line-number">5 </boundary-data>
|
| 296 |
+
retainers and their base form a single-piece segment. In another embodiment, the wafer retainers are fabricated separately from their base. The wafer retainers may then be integrated with the conveyor by fixedly attaching (either permanently or removably) them to their base to form a multi-piece segment. If the wafer retainers are not permanently fixedly attached, the wafer retainers may be replaced without having to <boundary-data type="line-number">10 </boundary-data>
|
| 297 |
+
replace the base. In any event, the wafer retainers are integrated with the conveyor in that unlike wafer boats, the wafer retainers are not removable from the conveyor during normal operation. Wafer retainers are preferably configured to contact as little of the wafer as possible to minimize contamination and to expose more of the wafer for processing. </p>
|
| 298 |
+
<p id="p-40" num="40">
|
| 299 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 300 |
+
FIGS. 4(a) and 4(b) schematically show a side view and a front view, respectively, of a conveyor 152<confidence value="5">C</confidence>
|
| 301 |
+
in accordance with an embodiment of the present invention. In the example of FIG. 4(a), wafer retainers <part-num-ref name="example of FIG. 4(a), wafer retainers">401</part-num-ref>
|
| 302 |
+
form slots <part-num-ref name="form slots">403</part-num-ref>
|
| 303 |
+
into which wafers may be inserted. As shown in FIG. 4(b), the conveyor 152<confidence value="5">C</confidence>
|
| 304 |
+
may have two or more wafer retainers <part-num-ref name="conveyor 152C may have two or more wafer retainers">401</part-num-ref>
|
| 305 |
+
to support each surface of the wafer. </p>
|
| 306 |
+
<p id="p-41" num="41">
|
| 307 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 308 |
+
FIGS. 5(a) and 5(b) schematically show a side view and a front view, respectively, of a conveyor 152D in accordance with an embodiment of the present invention. In this embodiment, wafer retainers <part-num-ref name="present invention. In this embodiment, wafer retainers">501</part-num-ref>
|
| 309 |
+
form slots <part-num-ref name="form slots">503</part-num-ref>
|
| 310 |
+
into which wafers may be inserted. As shown in FIG. 5(b), the conveyor 152D is similar to the conveyor <boundary-data type="header">
|
| 311 |
+
<confidence value="888">-9-</confidence>
|
| 312 |
+
</boundary-data>
|
| 313 |
+
<page-break num="10"/>
|
| 314 |
+
<boundary-data type="header">Attorney Docket No. 10031.001400</boundary-data>
|
| 315 |
+
<confidence value="8">1</confidence>
|
| 316 |
+
52C except that the two or more wafer retainers <part-num-ref name="two or more wafer retainers">501</part-num-ref>
|
| 317 |
+
supporting each surface of the wafer are not on the edges of the conveyor. </p>
|
| 318 |
+
<p id="p-42" num="42">FIGS. 6(a) and 6(b) schematically show a side view and a front view, respectively, of a conveyor 152E in accordance with an embodiment of the present <boundary-data type="line-number">5 </boundary-data>
|
| 319 |
+
invention. In this embodiment, wafer retainers <part-num-ref name="present invention. In this embodiment, wafer retainers">601</part-num-ref>
|
| 320 |
+
form slots <part-num-ref name="form slots">603</part-num-ref>
|
| 321 |
+
into which wafers may be inserted. Unlike those in conveyors 152C and 152D, the wafer retainers <part-num-ref name="wafer retainers">601</part-num-ref>
|
| 322 |
+
in conveyor 152C span the width of the conveyor. </p>
|
| 323 |
+
<p id="p-43" num="43">Turning now to FIG. 7, there is shown a flow diagram of a method <part-num-ref name="method">700</part-num-ref>
|
| 324 |
+
of processing a wafer in an in-line furnace chamber, such as an in-line process tube, in <boundary-data type="line-number">10 </boundary-data>
|
| 325 |
+
accordance with an embodiment of the present invention. </p>
|
| 326 |
+
<p id="p-44" num="44">In step 701, a plurality of wafers is placed on a continuous conveyor on one end of the furnace.</p>
|
| 327 |
+
<p id="p-45" num="45">In step 702, the wafers are supported by wafer retainers at an angle (e.g., <part-num-ref name="">90</part-num-ref>
|
| 328 |
+
degrees) relative to ground. The wafer retainers may be fixedly (either removably or <boundary-data type="line-number">15 </boundary-data>
|
| 329 |
+
permanently) integrated with the conveyor. In one embodiment, the wafer retainers are formed on a base, with the wafer retainers and the base forming a segment that is joined with other segments to form the conveyor. The integrated wafer retainers advantageously allow thermal processing of the wafers without having to use wafer boats. </p>
|
| 330 |
+
<p id="p-46" num="46">
|
| 331 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 332 |
+
<confidence value="5">I</confidence>
|
| 333 |
+
n step 703, the conveyor is driven to move the wafers through a chamber of the furnace. </p>
|
| 334 |
+
<boundary-data type="header">
|
| 335 |
+
<confidence value="8888">-10-</confidence>
|
| 336 |
+
</boundary-data>
|
| 337 |
+
<boundary-data type="header">Attorney Docket No. 10031.001400</boundary-data>
|
| 338 |
+
<p id="p-47" num="47">
|
| 339 |
+
<page-break num="11"/>
|
| 340 |
+
In step 704, the wafers are processed in the chamber. The processing of the wafers may involve diffusion, annealing, cooling, doping, and other processing suitably performed in a process tube. </p>
|
| 341 |
+
<p id="p-48" num="48">In step 705, the wafers are removed from the conveyor on the other end of the <boundary-data type="line-number">5 </boundary-data>
|
| 342 |
+
furnace. </p>
|
| 343 |
+
<p id="p-49" num="49">While specific embodiments of the present invention have been provided, it is to be understood that these embodiments are for illustration purposes and not limiting.</p>
|
| 344 |
+
<p id="p-50" num="50">Many additional embodiments will be apparent to persons of ordinary skill in the art reading this disclosure.</p>
|
| 345 |
+
<boundary-data type="header">
|
| 346 |
+
<confidence value="888">-11</confidence>
|
| 347 |
+
<confidence value="8">-</confidence>
|
| 348 |
+
</boundary-data>
|
| 349 |
+
</description>
|
| 350 |
+
</us-patent-application>
|
| 351 |
+
|
applicant/11546560.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>11546560</doc-number>
|
| 8 |
+
<date>2009-06-19</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">MARDIROSSIAN</heading>
|
| 14 |
+
<p id="p-1" num="1">App<confidence value="7">l</confidence>
|
| 15 |
+
e. No. 11/546,560 June 19, 2009 </p>
|
| 16 |
+
<heading id="h-2">AMENDMENTS TO THE TITLE:</heading>
|
| 17 |
+
<p id="p-2" num="2">Please amend the title as follows: "COMPUTER-MED<confidence value="5">I</confidence>
|
| 18 |
+
ATED SYSTEMS AND </p>
|
| 19 |
+
<heading id="h-3">METHODS FOR LOCATING TERRORISTS".</heading>
|
| 20 |
+
<p id="p-3" num="3">
|
| 21 |
+
<confidence value="888">-2-</confidence>
|
| 22 |
+
11494621 </p>
|
| 23 |
+
</description>
|
| 24 |
+
</us-patent-application>
|
| 25 |
+
|
applicant/11554842.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>11554842</doc-number>
|
| 8 |
+
<date>2010-11-11</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/554,842 Attorney Docket No.: 1358/US Paper Filed: 1358/US Page 2 of <part-num-ref name="of">21</part-num-ref>
|
| 14 |
+
Reply to Office Action Mailed August <part-num-ref name="Reply to Office Action Mailed August">11,</part-num-ref>
|
| 15 |
+
<part-num-ref name="Reply to Office Action Mailed August 11,">2010</part-num-ref>
|
| 16 |
+
Amendments to the Specification: </p>
|
| 17 |
+
<p id="p-2" num="2">Please replace paragraph 0049 with the following:</p>
|
| 18 |
+
<p id="p-3" num="3">[0049] As used here, a "computer readable medium" can be any means that can contain<confidence value="5">,</confidence>
|
| 19 |
+
or store, <confidence value="22222">cothe</confidence>
|
| 20 |
+
program for use by or in connection with the instruction execution system, apparatus, or device. The computer readable medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or <confidence value="222222222">propagati</confidence>
|
| 21 |
+
other medium. </p>
|
| 22 |
+
<p id="p-4" num="4">Please replace paragraph 0050 with the following:</p>
|
| 23 |
+
<p id="p-5" num="5">[0050] More specific examples (a non-exhaustive list) of the computer readable medium can include the following: <confidence value="77777">aired</confidence>
|
| 24 |
+
<confidence value="88888">netwo</confidence>
|
| 25 |
+
rk <confidence value="8888">conn</confidence>
|
| 26 |
+
ecti<confidence value="88">on</confidence>
|
| 27 |
+
<confidence value="626">and</confidence>
|
| 28 |
+
<confidence value="24122662">asGociae</confidence>
|
| 29 |
+
<confidence value="8888">conn</confidence>
|
| 30 |
+
e<confidence value="8">c</confidence>
|
| 31 |
+
ti<confidence value="88">on</confidence>
|
| 32 |
+
<confidence value="82">an</confidence>
|
| 33 |
+
d as<confidence value="888">soc</confidence>
|
| 34 |
+
iated tra<confidence value="888888888">nsmission</confidence>
|
| 35 |
+
<confidence value="8">m</confidence>
|
| 36 |
+
edi<confidence value="887">um,</confidence>
|
| 37 |
+
<confidence value="242">suc</confidence>
|
| 38 |
+
h as a<confidence value="2">n</confidence>
|
| 39 |
+
IEEE 802.11 (a), (b), <confidence value="2">o</confidence>
|
| 40 |
+
r (<confidence value="21">gM</confidence>
|
| 41 |
+
<confidence value="28">or</confidence>
|
| 42 |
+
<confidence value="2">a</confidence>
|
| 43 |
+
<confidence value="12228811">BLUIETOO</confidence>
|
| 44 |
+
TH tra<confidence value="888888888">nsmission</confidence>
|
| 45 |
+
<confidence value="2122">sytm</confidence>
|
| 46 |
+
<confidence value="2">a</confidence>
|
| 47 |
+
wide<confidence value="1">-</confidence>
|
| 48 |
+
are<confidence value="21">a°</confidence>
|
| 49 |
+
<confidence value="222222">ntwork</confidence>
|
| 50 |
+
(WAN), a<confidence value="122881">Gloal-</confidence>
|
| 51 |
+
are<confidence value="2">a</confidence>
|
| 52 |
+
<confidence value="5622">netk</confidence>
|
| 53 |
+
<confidence value="666566">(LAN),</confidence>
|
| 54 |
+
<confidence value="666242662662">the-Interet,</confidence>
|
| 55 |
+
<confidence value="2222225">tranet,</confidence>
|
| 56 |
+
a portable computer diskette, a random access memory (RAM), a read only memory (R<confidence value="5">O</confidence>
|
| 57 |
+
M), an erasable programmable read only memory (EPROM or Flash memory), a<confidence value="5546625452488155">R-ptical-4ibe-r,</confidence>
|
| 58 |
+
a portable compact disc (CD), a portable digital video disc (DVD), and the like. </p>
|
| 59 |
+
</description>
|
| 60 |
+
</us-patent-application>
|
| 61 |
+
|
applicant/11607511.xml
ADDED
|
@@ -0,0 +1,487 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11607511</doc-number>
|
| 8 |
+
<date>2006-11-30</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">DIGITAL MAPPING SYSTEM BASED ON</heading>
|
| 14 |
+
<heading id="h-2">CONTINUOUS SCANNING LINE OF SIGHT</heading>
|
| 15 |
+
<heading id="h-3">FIELD OF THE INVENTION</heading>
|
| 16 |
+
<p id="p-1" num="1">[0001] The field of the subject invention is mapping systems. The subject invention relates to cartography, in particular to digital mapping systems.</p>
|
| 17 |
+
<heading id="h-4">BACKGROUND OF THE INVENTION</heading>
|
| 18 |
+
<p id="p-2" num="2">[0002<confidence value="5">]</confidence>
|
| 19 |
+
Airborne camera assemblies for capturing aerial photos are used for commercial and military cartography applications, including reconnaissance, mapping and terrain model generation. Conventional assemblies suffer from three drawbacks. (i) They are very expensive, because they use accurate wide-angle lens cameras with large format CCDs for replicating analog film cameras, inertial navigation units and motion stabilizers. (ii) They are very large and heavy, because they use large lenses. (iii) Due to short optica<confidence value="8">l</confidence>
|
| 20 |
+
focal lengths, they require flight paths with <confidence value="5">l</confidence>
|
| 21 |
+
ow cruising altitudes. As a result, they have limited capability to cover large areas in short amounts of time. </p>
|
| 22 |
+
<boundary-data type="header">
|
| 23 |
+
<confidence value="22228">Atty.</confidence>
|
| 24 |
+
Docket No. 57399 -1- </boundary-data>
|
| 25 |
+
<heading id="h-5">SUMMARY OF THE DESCRIPTION</heading>
|
| 26 |
+
<p id="p-3" num="3">
|
| 27 |
+
<page-break num="2"/>
|
| 28 |
+
[0003<confidence value="5">]</confidence>
|
| 29 |
+
The subject invention concerns automated orthophoto, digital terrain model, digital surface model and camera model derivation from aerial photographs of a ground area. The subject invention provides a camera assembly for airborne use which is inexpensive, small and lightweight. The camera assembly of the subject invention has many advantages over prior art assemblies. </p>
|
| 30 |
+
<p id="p-4" num="4">
|
| 31 |
+
<confidence value="5">[</confidence>
|
| 32 |
+
0004<confidence value="5">]</confidence>
|
| 33 |
+
Prior art systems use expensive large format CCDs. In distinction, the subject invention uses inexpensive commercially available small format interline CCDs. Since large format C<confidence value="5">C</confidence>
|
| 34 |
+
Ds have low frame rates, using smaller CCDs with higher frame rates serves to acquire more total pixels per second. The subject invention generates a wide-angle sweep image from multiple frames, using a coherent photogrammetric camera model. Whereas small images are a drawback for prior art systems, the subject invention overcomes this drawback by using computer vision algorithms that solve and combine dozens of images into one sweep image with a coherent camera model. </p>
|
| 35 |
+
<p id="p-5" num="5">[0005<confidence value="5">]</confidence>
|
| 36 |
+
The subject invention uses mirror-based folding lenses to reduce the size of an optical assembly and yet maintain required focal lengths. </p>
|
| 37 |
+
<p id="p-6" num="6">Mirror-based folding lenses are much smaller, lighter and less expensive than the large calibrated mapping lenses used with prior art systems.</p>
|
| 38 |
+
<p id="p-7" num="7">The optical assemblies with such lenses require only simple motors for rotation.</p>
|
| 39 |
+
<p id="p-8" num="8">[0006<confidence value="5">]</confidence>
|
| 40 |
+
Prior art systems use mechanical shutters, which are not reliable and reduce the frame rate. Prior art systems also use polarizer shutters, which absorb significant light energy. In distinction, the subject invention uses a light-scattering liquid crystal shutter, which absorbs only negligible <boundary-data type="header">Atty. Docket No. 57399 -2-</boundary-data>
|
| 41 |
+
<page-break num="3"/>
|
| 42 |
+
amounts of light and is able to operate for long periods of time in high frequencies. Moreover, use of scattering liquid crystal shutters in the present invention serves to overcome smear effects that are typically produced by interline CCD cameras. </p>
|
| 43 |
+
<p id="p-9" num="9">
|
| 44 |
+
<confidence value="5">[</confidence>
|
| 45 |
+
0007<confidence value="5">]</confidence>
|
| 46 |
+
Prior art motion compensation relies on stabilization of an entire sensing element, by mounting the sensing element on a stabilizer that maintains an absolute angle. In distinction, the subject invention uses gyroscopic sensors, GPS data and motor encoders for calculating motion compensation. Motion compensation is performed by tilting a mirror mounted on the folding optics, using a piezoelectric tilt platform. Since the total weight and size of the mirror are small, motion compensation is performed very accurately. The present invention compensates for forward motion, which is determined from GPS data, and also for angular sweeping motion, which is determined from gyroscopic sensors. </p>
|
| 47 |
+
<p id="p-10" num="10">
|
| 48 |
+
<confidence value="5">[</confidence>
|
| 49 |
+
0008<confidence value="5">]</confidence>
|
| 50 |
+
There is thus provided in accordance with an embodiment of the subject invention apparatus for capturing images while in motion, including at least one CCD camera housed within an aircraft traveling along a flight path, for capturing aerial images of ground terrain, a motor for rotating an axis on which the at least one CCD camera is mounted, and for generating a sweeping back-and-forth motion for a field of view of the at least one CCD camera, the sweeping motion being transverse to the aircraft flight path, and an optical assembly connected to said at least one C<confidence value="5">C</confidence>
|
| 51 |
+
D camera. </p>
|
| 52 |
+
<p id="p-11" num="11">
|
| 53 |
+
<confidence value="5">[</confidence>
|
| 54 |
+
0009] There is further provided in accordance with an embodiment of the subject invention a method for generating a camera model, including capturing a plurality of images of a scene as the line of sight of a camera sweeps across a scene, deriving a synthetic photogrammetric camera <boundary-data type="header">Atty. Docket No. 57399 -3-</boundary-data>
|
| 55 |
+
<page-break num="4"/>
|
| 56 |
+
model from the plurality of images, and combining the plurality of images to derive a single continuous image, wherein the single continuous image is suitable for photogrammetric applications. </p>
|
| 57 |
+
<p id="p-12" num="12">
|
| 58 |
+
<confidence value="5">[</confidence>
|
| 59 |
+
0010<confidence value="4">]</confidence>
|
| 60 |
+
There is yet further provided in accordance with an embodiment of the subject invention a method for image compression, including receiving an image captured by a camera with a Bayer color CCD sensor at an original resolution, separating the captured image into <part-num-ref name="captured image into">1</part-num-ref>
|
| 61 |
+
red, <part-num-ref name="red,">1</part-num-ref>
|
| 62 |
+
blue and <part-num-ref name="blue and">2</part-num-ref>
|
| 63 |
+
green color channels, where each of the color channels has a resolution that is 1/4 of the original reso<confidence value="8">l</confidence>
|
| 64 |
+
ution, and compressing each of the color channels using grayscale image compression. </p>
|
| 65 |
+
<boundary-data type="header">Atty. Docket No. 57399 -4-</boundary-data>
|
| 66 |
+
<heading id="h-6">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 67 |
+
<p id="p-13" num="13">
|
| 68 |
+
<page-break num="5"/>
|
| 69 |
+
[0011] The subject invention will be more fully understood and appreciated from the following detailed description, taken in conjunction with the drawings in which: </p>
|
| 70 |
+
<p id="p-14" num="14">[0012<confidence value="5">]</confidence>
|
| 71 |
+
FIG. 1 is a simp<confidence value="8">l</confidence>
|
| 72 |
+
ified diagram of a typical flight path of an aircraft having one or more CCD cameras mounted therewithin and capturing aerial photos of the ground, in accordance with an embodiment of the subject invention; </p>
|
| 73 |
+
<p id="p-15" num="15">[0013] FIG. 2 is a simplified illustration of camera lines of sight, for determining accuracy of the synthetic model used by the present invention to combine frame images into a single coherent sweep image;</p>
|
| 74 |
+
<p id="p-16" num="16">[0014] FIG. 3 is a simplified block diagram of an overall in-flight system on board the aircraft for capturing, processing and storing a multitude of aerial photos of the ground, in accordance with an embodiment of the subject invention;</p>
|
| 75 |
+
<p id="p-17" num="17">[0015] FIG. 4 is a simplified block diagram of the internal elements of the CCD cameras of FIG. 3, in accordance with an embodiment of the subject invention;</p>
|
| 76 |
+
<p id="p-18" num="18">[0016] FIG. 5 is a cross-sectional view of an optical assembly with lens and mirrors, for the folding lens in FIG. 4, in accordance with an embodiment of the subject invention;</p>
|
| 77 |
+
<p id="p-19" num="19">
|
| 78 |
+
<confidence value="5">[</confidence>
|
| 79 |
+
0017] FIG. 6 is a simplified flowchart of a control loop that is used to stabilize a camera's line of sight, while the camera is in motion, in accordance with an embodiment of the subject invention; </p>
|
| 80 |
+
<p id="p-20" num="20">
|
| 81 |
+
<confidence value="5">[</confidence>
|
| 82 |
+
0018] FIG. 7 is a simplified block diagram of the data compressors of FIG. 3, in accordance with an embodiment of the subject invention; and <boundary-data type="header">Atty. Docket No. 57399 -5-</boundary-data>
|
| 83 |
+
<page-break num="6"/>
|
| 84 |
+
<confidence value="5">[</confidence>
|
| 85 |
+
0019<confidence value="5">]</confidence>
|
| 86 |
+
FIG. 8 is a simplified diagram illustrating how the re-ordering unit of FIG. 7 re-orders pixel color values, in accordance with an embodiment of the subject invention. </p>
|
| 87 |
+
<boundary-data type="header">Atty. Docket No. 57399 -6-</boundary-data>
|
| 88 |
+
<heading id="h-7">DETAILED DESCRIPTION</heading>
|
| 89 |
+
<p id="p-21" num="21">
|
| 90 |
+
<page-break num="7"/>
|
| 91 |
+
[0020] The subject invention concerns mapping, in particular generation of accurate terrain maps from a large number of aerial color photos captured by one or more CCD cameras mounted within a moving aircraft. </p>
|
| 92 |
+
<p id="p-22" num="22">The cameras' fields of view sweep back and forth, generally transverse to the direction of flight, so as to cover a wide strip of terrain surrounding the path of flight.</p>
|
| 93 |
+
<p id="p-23" num="23">[0021<confidence value="5">]</confidence>
|
| 94 |
+
Conventional photogrammetry uses either a "frame" camera model or a "push-broom" camera model. Generally, a camera model solution is a function that maps each pixel (i, j) in an image captured by a camera into a ray defined by <part-num-ref name="ray defined by">6</part-num-ref>
|
| 95 |
+
degrees of freedom emanating from the camera. The classical <part-num-ref name="classical">6</part-num-ref>
|
| 96 |
+
degrees of freedom comprise <confidence value="5">(</confidence>
|
| 97 |
+
x, y, z, kappa, phi, theta), where x, y and z are scalars, and kappa, phi and theta are angles. </p>
|
| 98 |
+
<p id="p-24" num="24">The camera model solution is generally obtained by sensing the camera's position and angles, or by using aerial triangulation using ground control points (GCPs). Obtaining a camera model is essential for mapping applications, surveillance applications and photogrammetry, as in creation of stereoscopic pairs..</p>
|
| 99 |
+
<p id="p-25" num="25">[0022] A frame camera model acquires full frames at a single time. The camera model for a full frame is defined by <part-num-ref name="full frame is defined by">6</part-num-ref>
|
| 100 |
+
degrees of freedom for an entire frame. A <confidence value="5">p</confidence>
|
| 101 |
+
ush-broom camera model is based on a scanning column. For each scan column <part-num-ref name="scanning column. For each scan column">6</part-num-ref>
|
| 102 |
+
degrees of freedom are solved. </p>
|
| 103 |
+
<p id="p-26" num="26">[0023] Each model has its relative advantages and disadvantages. The frame model is more stable than the push-broom model, but push-broom mode<confidence value="8">l</confidence>
|
| 104 |
+
s are currently generating larger images per model. The larger images cover a wider area, and are thus more useful. </p>
|
| 105 |
+
<boundary-data type="header">Atty. Docket No. 57399 -7-</boundary-data>
|
| 106 |
+
<p id="p-27" num="27">
|
| 107 |
+
<page-break num="8"/>
|
| 108 |
+
<confidence value="5">[</confidence>
|
| 109 |
+
0024<confidence value="5">]</confidence>
|
| 110 |
+
The present invention overcomes these disadvantages, and generates a large image with a singe accurate camera model. The present invention combines the advantages of push-broom cameras, namely, large images, with the advantages of frame cameras, namely, accuracy, and simple stable image model. </p>
|
| 111 |
+
<p id="p-28" num="28">
|
| 112 |
+
<confidence value="5">[</confidence>
|
| 113 |
+
0025<confidence value="5">]</confidence>
|
| 114 |
+
Reference is now made to FIG. 1, which is a simplified diagram of a flight path of an aircraft having one or more CCD cameras mounted therewithin and capturing aerial photos of the ground, in accordance with an embodiment of the subject invention. As shown in FIG. 1, the flight path is designated by P and consists of multiple legs denoted <part-num-ref name="flight path is designated by P and consists of multiple legs denoted">1</part-num-ref>
|
| 115 |
+
- <part-num-ref name="-">5,</part-num-ref>
|
| 116 |
+
each leg being substantially along a straight line. The flight path is substantially at a constant cruise altitude. </p>
|
| 117 |
+
<p id="p-29" num="29">[0026<confidence value="4">]</confidence>
|
| 118 |
+
As the craft proceeds along its flight path P on leg <part-num-ref name="craft proceeds along its flight path P on leg">1,</part-num-ref>
|
| 119 |
+
the cameras mounted within the craft capture a series of ground photographs at overlapping fields of view <part-num-ref name="series of ground photographs at overlapping fields of view">110</part-num-ref>
|
| 120 |
+
that are swept transverse to the direction of flight over sweeps <part-num-ref name="direction of flight over sweeps">120.</part-num-ref>
|
| 121 |
+
Each set of frames captured by the said cameras is called a strip. Sweeps <part-num-ref name="strip. Sweeps">120</part-num-ref>
|
| 122 |
+
span the area indicated between lines A and B, and move forward along the flight path in time. </p>
|
| 123 |
+
<p id="p-30" num="30">Similarly, as the craft proceeds along its flight path P on leg <part-num-ref name="craft proceeds along its flight path P on leg">2,</part-num-ref>
|
| 124 |
+
the cameras capture a series of ground photographs at overlapping fields of view <part-num-ref name="series of ground photographs at overlapping fields of view">130</part-num-ref>
|
| 125 |
+
that are swept over sweeps <part-num-ref name="that are swept over sweeps">140.</part-num-ref>
|
| 126 |
+
Strips <part-num-ref name="that are swept over sweeps 140. Strips">140</part-num-ref>
|
| 127 |
+
span the area indicated between lines C and D. Strips <part-num-ref name="area indicated between lines C and D. Strips">140</part-num-ref>
|
| 128 |
+
overlap with strips <part-num-ref name="overlap with strips">120,</part-num-ref>
|
| 129 |
+
<confidence value="66">so</confidence>
|
| 130 |
+
as to ensure complete ground coverage and grabbing of stereoscopic image pairs. Typically, the overlap between legs may be over 50<confidence value="5">%</confidence>
|
| 131 |
+
in order to provide sufficient coverage for stereoscopic view purposes. On leg <part-num-ref name="overlap between legs may be over 50% in order to provide sufficient coverage for stereoscopic view purposes. On leg">3</part-num-ref>
|
| 132 |
+
the strips swept out by the cameras' fields of view span the area between lines E and F, on leg <part-num-ref name="area between lines E and F, on leg">4</part-num-ref>
|
| 133 |
+
they span the area between lines G and <boundary-data type="header">Atty. Docket No. 57399 -8-</boundary-data>
|
| 134 |
+
<page-break num="9"/>
|
| 135 |
+
H, and on leg <part-num-ref name="area between lines G and H, and on leg">5</part-num-ref>
|
| 136 |
+
they span the areas between lines I and J. The strip overlap areas are the areas between lines C and B, between lines E and D, between lines G and F, and between lines I and H. The process may continue for additional legs. </p>
|
| 137 |
+
<p id="p-31" num="31">
|
| 138 |
+
<confidence value="5">[</confidence>
|
| 139 |
+
0027<confidence value="5">]</confidence>
|
| 140 |
+
The extent of overlap between the individual fields of view <part-num-ref name="individual fields of view">110</part-num-ref>
|
| 141 |
+
or <part-num-ref name="or">130</part-num-ref>
|
| 142 |
+
depends on their angles of view, and on the number of frames per second that the cameras can capture. As the frame rate is high, the speed of the aircraft is negligible. The extent of overlap between sweep <part-num-ref name="extent of overlap between sweep">110</part-num-ref>
|
| 143 |
+
and the sequential sweep depends on the velocity of the aircraft. </p>
|
| 144 |
+
<p id="p-32" num="32">The extent of overlap between the sweeps <part-num-ref name="sweeps">120</part-num-ref>
|
| 145 |
+
and <part-num-ref name="and">140</part-num-ref>
|
| 146 |
+
captured in adjacent legs depends on the distance between the various legs <part-num-ref name="various legs">1</part-num-ref>
|
| 147 |
+
- <part-num-ref name="-">5</part-num-ref>
|
| 148 |
+
and on the width of the sweeps swept out by the cameras' fields of view. </p>
|
| 149 |
+
<p id="p-33" num="33">The resolution of ground coverage depends on the focal lengths of the cameras and the resolutions of their C<confidence value="5">C</confidence>
|
| 150 |
+
D arrays. </p>
|
| 151 |
+
<p id="p-34" num="34">
|
| 152 |
+
<confidence value="5">[</confidence>
|
| 153 |
+
0028<confidence value="5">]</confidence>
|
| 154 |
+
In distinction from the prior art, the present invention combines the captured strips <part-num-ref name="captured strips">110</part-num-ref>
|
| 155 |
+
to generate a large sweep image having a coherent camera model. That is, each sweep of the cameras is used to generate a single large sweep image with a coherent camera model. For each pixel <confidence value="5">(</confidence>
|
| 156 |
+
i ,<confidence value="5">j</confidence>
|
| 157 |
+
) in the large sweep image, the camera model stores an index of the original frame that contains the pixel. For each original frame, the camera position and angles are known and stored with the frame image. As such, the synthetic camera model for the entire sweep image is as accurate as the individual frame models; i.e., the synthetic image does not add additional errors to the digital mapping process. </p>
|
| 158 |
+
<p id="p-35" num="35">[0029<confidence value="5">]</confidence>
|
| 159 |
+
Reference is now made to FIG. 2, which is a simplified illustration of camera lines of sight, for determining accuracy of the synthetic model used by the present invention to combine frame images <boundary-data type="header">Atty. Docket No. 57399 <confidence value="666">-9-</confidence>
|
| 160 |
+
</boundary-data>
|
| 161 |
+
<page-break num="10"/>
|
| 162 |
+
into a single coherent sweep image. Shown in FIG. 2 is camera at a first position <part-num-ref name="first position">210</part-num-ref>
|
| 163 |
+
when capturing a frame #1 and at a second position <part-num-ref name="second position">220</part-num-ref>
|
| 164 |
+
when capturing a frame #2. The line of sight for camera <part-num-ref name="line of sight for camera">210</part-num-ref>
|
| 165 |
+
is positioned and oriented according to parameters (x<confidence value="2">1</confidence>
|
| 166 |
+
, y<confidence value="5">l</confidence>
|
| 167 |
+
, z<confidence value="5">1</confidence>
|
| 168 |
+
, angles<confidence value="28">1,</confidence>
|
| 169 |
+
and the line of sight for camera <part-num-ref name="line of sight for camera">220</part-num-ref>
|
| 170 |
+
is positioned and oriented according to parameters (x2, y2, z2, angles2). The parameters angle<confidence value="6">s</confidence>
|
| 171 |
+
and angles2 are used here to denote the three angular degrees of freedom, (<confidence value="222222">kappal</confidence>
|
| 172 |
+
, phi<confidence value="8">l</confidence>
|
| 173 |
+
, <confidence value="222222">thetal</confidence>
|
| 174 |
+
) and (kappa2, phi2, theta2), respectively. The positional and angular parameters for the lines of sights are known from the camera model. The synthetic sweep model should be continuous and maintain the accuracy of the frame model for each pixel. The synthetic model assumes that the geometry along the stitch between two consecutive frames is maintained as a result of the similar perspective of frames #1 and frame #2. A DTM is used in order to create the stitch. </p>
|
| 175 |
+
<p id="p-36" num="36">
|
| 176 |
+
<confidence value="5">[</confidence>
|
| 177 |
+
0030<confidence value="5">]</confidence>
|
| 178 |
+
The curve denoted <part-num-ref name="curve denoted">230</part-num-ref>
|
| 179 |
+
represents a digital terrain model (DTM). </p>
|
| 180 |
+
<p id="p-37" num="37">As shown in FIG. 2, ground coordinates are determined by intersection of rays with the DTM. In particular, errors in the DTM contribute to errors in ground coordinate determination. Specifically, let <confidence value="5">e</confidence>
|
| 181 |
+
denote the extent of a DTM error as shown in FIG. 2. If the DTM is accurate, the panoramic projection of frames #1 and #2 is continuous. If the DTM is erroneous, the stitch line may not be continuous. As a result of this error, the camera model generates point P instead of point Q. By similar triangles, it can be seen that the deviation, denoted f in FIG. 2, satisfies <confidence value="8">f</confidence>
|
| 182 |
+
= d*e <confidence value="5">/</confidence>
|
| 183 |
+
(h+e) , <part-num-ref name="deviation, denoted f in FIG. 2, satisfies f = d*e / (h+e) ,">(1)</part-num-ref>
|
| 184 |
+
where d is the displacement between positions <part-num-ref name="displacement between positions">210</part-num-ref>
|
| 185 |
+
and <part-num-ref name="and">220.</part-num-ref>
|
| 186 |
+
Since h is much larger than e, EQUATION <part-num-ref name="and 220. Since h is much larger than e, EQUATION">1</part-num-ref>
|
| 187 |
+
can be approximated by <confidence value="2222222">f=d*e/h</confidence>
|
| 188 |
+
. <part-num-ref name="can be approximated by f=d*e/h .">(2)</part-num-ref>
|
| 189 |
+
<boundary-data type="header">Atty. Docket No. 57399 -10-</boundary-data>
|
| 190 |
+
<page-break num="11"/>
|
| 191 |
+
[0031<confidence value="5">]</confidence>
|
| 192 |
+
To appreciate the imp<confidence value="8">l</confidence>
|
| 193 |
+
ication of EQUATION <part-num-ref name="implication of EQUATION">2,</part-num-ref>
|
| 194 |
+
it is noted that under reasonable conditions the camera is moving at a velocity of <part-num-ref name="velocity of">70</part-num-ref>
|
| 195 |
+
<confidence value="222225">m/sec,</confidence>
|
| 196 |
+
the aircraft is at a height of h = <part-num-ref name="height of h =">3000</part-num-ref>
|
| 197 |
+
m, the image resolution of the camera corresponds to <part-num-ref name="camera corresponds to">10</part-num-ref>
|
| 198 |
+
cm/pixel, and the camera captures <part-num-ref name="camera captures">7</part-num-ref>
|
| 199 |
+
frames/sec. As such, the displacement d = <part-num-ref name="displacement d =">10</part-num-ref>
|
| 200 |
+
m, and an error f < 0.1 m is within a single pixel. According to EQUATION <part-num-ref name="single pixel. According to EQUATION">2,</part-num-ref>
|
| 201 |
+
the DTM error, e, can be as large as e = f*h / d = <part-num-ref name="DTM error, e, can be as large as e = f*h / d =">30</part-num-ref>
|
| 202 |
+
m, without having an impact beyond <part-num-ref name="impact beyond">1</part-num-ref>
|
| 203 |
+
pixel. The present invention ensures that the displacement, d, between the camera positions at successive frame captures is small. According to EQUATION <part-num-ref name="camera positions at successive frame captures is small. According to EQUATION">2,</part-num-ref>
|
| 204 |
+
this ensures that the threshold, e, for allowable DTM error is large. As such, the synthetic camera model for combining frames is insensitive even to large DTM errors, and results in a continuous sweep image. </p>
|
| 205 |
+
<p id="p-38" num="38">
|
| 206 |
+
<confidence value="5">[</confidence>
|
| 207 |
+
0032<confidence value="5">]</confidence>
|
| 208 |
+
Reference is now made to FIG. 3, which is a simplified block diagram of an overall in-flight system on board the aircraft for capturing, processing and storing a multitude of aerial photos of the ground, in accordance with an embodiment of the subject invention. The in-flight system is responsible for: </p>
|
| 209 |
+
<p id="p-39" num="39">
|
| 210 |
+
<confidence value="2">.</confidence>
|
| 211 |
+
Image grabbing and compression; </p>
|
| 212 |
+
<p id="p-40" num="40">
|
| 213 |
+
<confidence value="2">"</confidence>
|
| 214 |
+
Camera motor and motion compensation control; </p>
|
| 215 |
+
<p id="p-41" num="41">
|
| 216 |
+
<confidence value="2">"</confidence>
|
| 217 |
+
Interface to removable storage; and <confidence value="2">"</confidence>
|
| 218 |
+
Power supply and voltage regulation. </p>
|
| 219 |
+
<p id="p-42" num="42">[0033<confidence value="4">]</confidence>
|
| 220 |
+
Shown in FIG. 3 is an in-flight electronic unit <part-num-ref name="in-flight electronic unit">300</part-num-ref>
|
| 221 |
+
connected to two CCD cameras <part-num-ref name="connected to two CCD cameras">305</part-num-ref>
|
| 222 |
+
which are housed in hermetically sealed units. </p>
|
| 223 |
+
<p id="p-43" num="43">CCD cameras 305 are temperature-controlled to prevent focal length variation at changing altitudes. Also connected to in-flight electronic unit <part-num-ref name="are temperature-controlled to prevent focal length variation at changing altitudes. Also connected to in-flight electronic unit">300</part-num-ref>
|
| 224 |
+
are a motor driver <part-num-ref name="motor driver">310,</part-num-ref>
|
| 225 |
+
an antenna <part-num-ref name="antenna">315,</part-num-ref>
|
| 226 |
+
a navigation console <part-num-ref name="navigation console">320,</part-num-ref>
|
| 227 |
+
<boundary-data type="header">Atty. Docket No. 57399 -11-</boundary-data>
|
| 228 |
+
<page-break num="12"/>
|
| 229 |
+
an operating console <part-num-ref name="operating console">325,</part-num-ref>
|
| 230 |
+
a removable disk <part-num-ref name="removable disk">330,</part-num-ref>
|
| 231 |
+
and a DC power source <part-num-ref name="DC power source">335.</part-num-ref>
|
| 232 |
+
Navigation console <part-num-ref name="DC power source 335. Navigation console">320</part-num-ref>
|
| 233 |
+
is used to guide the pilot in accurately navigating the legs of the flight path. </p>
|
| 234 |
+
<p id="p-44" num="44">
|
| 235 |
+
<confidence value="5">[</confidence>
|
| 236 |
+
0034<confidence value="4">]</confidence>
|
| 237 |
+
Orientation of CCD cameras 305 is performed by motor driver <part-num-ref name="is performed by motor driver">310,</part-num-ref>
|
| 238 |
+
which is controlled by a camera control board <part-num-ref name="camera control board">345</part-num-ref>
|
| 239 |
+
housed inside in- flight electronic unit <part-num-ref name="housed inside in- flight electronic unit">300.</part-num-ref>
|
| 240 |
+
Camera control board <part-num-ref name="housed inside in- flight electronic unit 300. Camera control board">345</part-num-ref>
|
| 241 |
+
receives feedback information from CCD cameras <part-num-ref name="receives feedback information from CCD cameras">305,</part-num-ref>
|
| 242 |
+
and communicates with motor driver <part-num-ref name="receives feedback information from CCD cameras 305, and communicates with motor driver">310</part-num-ref>
|
| 243 |
+
in a feedback loop. The links <part-num-ref name="links">1</part-num-ref>
|
| 244 |
+
between CCD cameras <part-num-ref name="between CCD cameras">305</part-num-ref>
|
| 245 |
+
and camera control board <part-num-ref name="and camera control board">345</part-num-ref>
|
| 246 |
+
are camera control links that transmit DC, data, sync and analog signals. The links <part-num-ref name="links">2</part-num-ref>
|
| 247 |
+
between camera control board <part-num-ref name="between camera control board">345</part-num-ref>
|
| 248 |
+
and motor driver <part-num-ref name="and motor driver">310</part-num-ref>
|
| 249 |
+
transmit motor driver signals, typically 28v </p>
|
| 250 |
+
<heading id="h-8">DC.</heading>
|
| 251 |
+
<p id="p-45" num="45">[0035] CCD cameras 305 are each connected to a data compressor <part-num-ref name="data compressor">340,</part-num-ref>
|
| 252 |
+
housed inside in-flight electronic unit <part-num-ref name="data compressor 340, housed inside in-flight electronic unit">300.</part-num-ref>
|
| 253 |
+
Data compressors <part-num-ref name="data compressor 340, housed inside in-flight electronic unit 300. Data compressors">340</part-num-ref>
|
| 254 |
+
processor image data captured by CCD cameras <part-num-ref name="processor image data captured by CCD cameras">305,</part-num-ref>
|
| 255 |
+
as described in detail below with reference to FIG. 7. The camera links <part-num-ref name="camera links">3</part-num-ref>
|
| 256 |
+
between cameras <part-num-ref name="between cameras">305</part-num-ref>
|
| 257 |
+
and data compressors <part-num-ref name="and data compressors">340</part-num-ref>
|
| 258 |
+
transmit camera signals, and typically include approximate <part-num-ref name="transmit camera signals, and typically include approximate">13</part-num-ref>
|
| 259 |
+
low-voltage differential signal (LVDS) pairs. Camera control board <part-num-ref name="low-voltage differential signal (LVDS) pairs. Camera control board">345</part-num-ref>
|
| 260 |
+
is connected to each data compressor <part-num-ref name="is connected to each data compressor">340</part-num-ref>
|
| 261 |
+
by links <part-num-ref name="by links">4,</part-num-ref>
|
| 262 |
+
each link <part-num-ref name="by links 4, each link">4</part-num-ref>
|
| 263 |
+
being an internal trigger connection, and typically including <part-num-ref name="internal trigger connection, and typically including">2</part-num-ref>
|
| 264 |
+
LVDS pairs. </p>
|
| 265 |
+
<p id="p-46" num="46">[0036<confidence value="5">]</confidence>
|
| 266 |
+
Instruction processing in in-flight electronic unit 300 is performed by a CPU <part-num-ref name="CPU">350,</part-num-ref>
|
| 267 |
+
which communicates with other system components through a backplane data bus <part-num-ref name="backplane data bus">355.</part-num-ref>
|
| 268 |
+
Data compressors <part-num-ref name="backplane data bus 355. Data compressors">340,</part-num-ref>
|
| 269 |
+
camera control board <part-num-ref name="backplane data bus 355. Data compressors 340, camera control board">345,</part-num-ref>
|
| 270 |
+
navigation console <part-num-ref name="backplane data bus 355. Data compressors 340, camera control board 345, navigation console">320,</part-num-ref>
|
| 271 |
+
operating console <part-num-ref name="backplane data bus 355. Data compressors 340, camera control board 345, navigation console 320, operating console">325</part-num-ref>
|
| 272 |
+
and removable disk <part-num-ref name="and removable disk">330</part-num-ref>
|
| 273 |
+
each communicate with CPU <part-num-ref name="each communicate with CPU">350</part-num-ref>
|
| 274 |
+
using backplane <part-num-ref name="using backplane">355.</part-num-ref>
|
| 275 |
+
Camera control board <part-num-ref name="using backplane 355. Camera control board">345</part-num-ref>
|
| 276 |
+
is connected to backplane <boundary-data type="header">Atty. Docket No. 57399 -12-</boundary-data>
|
| 277 |
+
<page-break num="13"/>
|
| 278 |
+
<part-num-ref name="is connected to backplane">355</part-num-ref>
|
| 279 |
+
by link <part-num-ref name="by link">5</part-num-ref>
|
| 280 |
+
using universal serial bus transmission. Navigation console <part-num-ref name="using universal serial bus transmission. Navigation console">320</part-num-ref>
|
| 281 |
+
is connected to backplane <part-num-ref name="is connected to backplane">355</part-num-ref>
|
| 282 |
+
by link <part-num-ref name="by link">6,</part-num-ref>
|
| 283 |
+
which is a gigabit Ethernet connection. Operating console is connected to backplane <part-num-ref name="gigabit Ethernet connection. Operating console is connected to backplane">355</part-num-ref>
|
| 284 |
+
by link <part-num-ref name="by link">7,</part-num-ref>
|
| 285 |
+
which transmits analog VGA and USB signals. Removable disk <part-num-ref name="by link 7, which transmits analog VGA and USB signals. Removable disk">330</part-num-ref>
|
| 286 |
+
is connected to backplane <part-num-ref name="is connected to backplane">355</part-num-ref>
|
| 287 |
+
by link <part-num-ref name="by link">8,</part-num-ref>
|
| 288 |
+
which includes a hard disk interface, such as a serial advanced technology attachment (SATA) storage connecter, and by link <part-num-ref name="serial advanced technology attachment (SATA) storage connecter, and by link">9,</part-num-ref>
|
| 289 |
+
which provides 12v <confidence value="5">/</confidence>
|
| 290 |
+
5v power to removable disk <part-num-ref name="serial advanced technology attachment (SATA) storage connecter, and by link 9, which provides 12v / 5v power to removable disk">330</part-num-ref>
|
| 291 |
+
from backplane <part-num-ref name="from backplane">355.</part-num-ref>
|
| 292 |
+
</p>
|
| 293 |
+
<p id="p-47" num="47">
|
| 294 |
+
<confidence value="5">[</confidence>
|
| 295 |
+
0037] The present invention has many advantages over prior art aerial data capture systems. These advantages include inter alia: </p>
|
| 296 |
+
<p id="p-48" num="48">
|
| 297 |
+
<confidence value="2">"</confidence>
|
| 298 |
+
weight and size significantly less than prior art systems; </p>
|
| 299 |
+
<p id="p-49" num="49">
|
| 300 |
+
<confidence value="2">"</confidence>
|
| 301 |
+
use of non-polarized liquid crystal shutters to eliminate smear effects in CCD imagery; </p>
|
| 302 |
+
<p id="p-50" num="50">
|
| 303 |
+
<confidence value="2">"</confidence>
|
| 304 |
+
continuous scanning of the line of sight, as opposed to step scanning; </p>
|
| 305 |
+
<p id="p-51" num="51">
|
| 306 |
+
<confidence value="2">.</confidence>
|
| 307 |
+
forward motion compensation is performed using a piezoelectric platform; </p>
|
| 308 |
+
<p id="p-52" num="52">
|
| 309 |
+
<confidence value="2">"</confidence>
|
| 310 |
+
no need for precise inertial measurement unit; and <confidence value="2">"</confidence>
|
| 311 |
+
no need for entire sensor stabilization. </p>
|
| 312 |
+
<p id="p-53" num="53">
|
| 313 |
+
<confidence value="5">[</confidence>
|
| 314 |
+
0038<confidence value="5">]</confidence>
|
| 315 |
+
In accordance with an embodiment of the subject invention, the camera assembly includes <confidence value="1">*</confidence>
|
| 316 |
+
optical elements, including inter alia a window, mirror, lens, shutter and filter; </p>
|
| 317 |
+
<p id="p-54" num="54">
|
| 318 |
+
<confidence value="2">.</confidence>
|
| 319 |
+
a CCD sensor; </p>
|
| 320 |
+
<p id="p-55" num="55">
|
| 321 |
+
<confidence value="2">"</confidence>
|
| 322 |
+
an image stabilization tilt platform; </p>
|
| 323 |
+
<p id="p-56" num="56">
|
| 324 |
+
<confidence value="2">"</confidence>
|
| 325 |
+
a gyroscopic orientation sensor; </p>
|
| 326 |
+
<p id="p-57" num="57">
|
| 327 |
+
<confidence value="2">"</confidence>
|
| 328 |
+
a sealed enclosure; </p>
|
| 329 |
+
<boundary-data type="header">Atty. Docket No. 57399 -13-</boundary-data>
|
| 330 |
+
<p id="p-58" num="58">
|
| 331 |
+
<page-break num="14"/>
|
| 332 |
+
<confidence value="1">.</confidence>
|
| 333 |
+
a desiccator; and <confidence value="1">*</confidence>
|
| 334 |
+
insulation and a heating unit for thermal management of a liquid crystal shutter. </p>
|
| 335 |
+
<p id="p-59" num="59">[0039<confidence value="5">]</confidence>
|
| 336 |
+
Further in accordance with an embodiment of the subject invention, the sweep motion system includes <confidence value="1">"</confidence>
|
| 337 |
+
a support structure; </p>
|
| 338 |
+
<p id="p-60" num="60">
|
| 339 |
+
<confidence value="1">*</confidence>
|
| 340 |
+
a motor and transmission assembly; </p>
|
| 341 |
+
<p id="p-61" num="61">
|
| 342 |
+
<confidence value="1">*</confidence>
|
| 343 |
+
encoder / limit switches; and <confidence value="1">"</confidence>
|
| 344 |
+
cable management. </p>
|
| 345 |
+
<p id="p-62" num="62">
|
| 346 |
+
<confidence value="5">[</confidence>
|
| 347 |
+
0040<confidence value="5">]</confidence>
|
| 348 |
+
Reference is now made to FIG. 4, which is a simplified block diagram of the internal elements of CCD cameras <part-num-ref name="internal elements of CCD cameras">305,</part-num-ref>
|
| 349 |
+
in accordance with an embodiment of the subject invention. As shown in FIG. 4, a camera assembly <part-num-ref name="camera assembly">400</part-num-ref>
|
| 350 |
+
includes a gyroscope and gyroscopic control unit <part-num-ref name="gyroscope and gyroscopic control unit">405,</part-num-ref>
|
| 351 |
+
which sends gyroscopic orientation data to a motion compensation unit <part-num-ref name="motion compensation unit">450.</part-num-ref>
|
| 352 |
+
</p>
|
| 353 |
+
<p id="p-63" num="63">[0041<confidence value="5">]</confidence>
|
| 354 |
+
Camera assembly 400 also includes a CCD electronic unit <part-num-ref name="CCD electronic unit">410</part-num-ref>
|
| 355 |
+
for processor CCD sensor array data, and a CCD camera <part-num-ref name="CCD camera">415.</part-num-ref>
|
| 356 |
+
The sensor array data is passed from CCD electronics unit <part-num-ref name="sensor array data is passed from CCD electronics unit">410</part-num-ref>
|
| 357 |
+
to a data storage unit <part-num-ref name="data storage unit">360,</part-num-ref>
|
| 358 |
+
for post-processing on the ground. </p>
|
| 359 |
+
<p id="p-64" num="64">[0042<confidence value="5">]</confidence>
|
| 360 |
+
Camera assembly 400 also includes a shutter with an electric heater <part-num-ref name="electric heater">420.</part-num-ref>
|
| 361 |
+
In accordance with an embodiment of the subject invention, shutter <part-num-ref name="subject invention, shutter">420</part-num-ref>
|
| 362 |
+
is a liquid crystal shutter; specifically, a polymer stabilized cholestoric textured (PSCT) liquid crystal optical light scattering shutter. </p>
|
| 363 |
+
<p id="p-65" num="65">In reducing the subject invention to practice, it has been found that light- scattering liquid crystal shutters absorb only negligible amounts of light.</p>
|
| 364 |
+
<p id="p-66" num="66">In distinction, conventional liquid crystal shutters based on polarizers absorb significant light energy.</p>
|
| 365 |
+
<boundary-data type="header">Atty. Docket No. 57399 -14-</boundary-data>
|
| 366 |
+
<p id="p-67" num="67">
|
| 367 |
+
<page-break num="15"/>
|
| 368 |
+
<confidence value="5">[</confidence>
|
| 369 |
+
0043<confidence value="5">]</confidence>
|
| 370 |
+
Camera assembly 400 also includes a mirror-based folding lens <part-num-ref name="mirror-based folding lens">425.</part-num-ref>
|
| 371 |
+
Use of a mirror-based folding lens serves to reduce the overall size of the optical assembly. Typically, lens <part-num-ref name="optical assembly. Typically, lens">425</part-num-ref>
|
| 372 |
+
has a focal length of approximately 300mm. In reducing the subject invention to practice, it has been found that this relatively large focal length yields good resolution when the aircraft is flying at high altitude, which makes the sensing of large areas more efficient. </p>
|
| 373 |
+
<p id="p-68" num="68">
|
| 374 |
+
<confidence value="5">[</confidence>
|
| 375 |
+
0044<confidence value="5">]</confidence>
|
| 376 |
+
Camera assembly 400 is fixed to a rotating axis <part-num-ref name="rotating axis">435,</part-num-ref>
|
| 377 |
+
which is controlled by a motor <confidence value="5">/</confidence>
|
| 378 |
+
encoder <part-num-ref name="motor / encoder">440.</part-num-ref>
|
| 379 |
+
As axis <part-num-ref name="motor / encoder 440. As axis">435</part-num-ref>
|
| 380 |
+
continuously rotates back and forth, the line of sight of the camera sweeps across strips transverse to the flight path, such as strip <part-num-ref name="flight path, such as strip">120</part-num-ref>
|
| 381 |
+
illustrated in FIG. 1. </p>
|
| 382 |
+
<p id="p-69" num="69">Motor 440 receives control signals from an in-flight electronics unit <part-num-ref name="in-flight electronics unit">470,</part-num-ref>
|
| 383 |
+
such as in-flight electronics unit <part-num-ref name="in-flight electronics unit 470, such as in-flight electronics unit">300,</part-num-ref>
|
| 384 |
+
for controlling its rotation. </p>
|
| 385 |
+
<p id="p-70" num="70">
|
| 386 |
+
<confidence value="5">[</confidence>
|
| 387 |
+
0045<confidence value="5">]</confidence>
|
| 388 |
+
The line of sight of camera <part-num-ref name="line of sight of camera">415</part-num-ref>
|
| 389 |
+
is determined by the motor and by one or more mirrors within the optical assembly, as shown in FIG. 5 hereinbelow, whose positions are controlled by a mirror control compensation unit <part-num-ref name="mirror control compensation unit">430.</part-num-ref>
|
| 390 |
+
Mirror compensation unit <part-num-ref name="mirror control compensation unit 430. Mirror compensation unit">430</part-num-ref>
|
| 391 |
+
receives control signals from in-flight electronics unit <part-num-ref name="receives control signals from in-flight electronics unit">470,</part-num-ref>
|
| 392 |
+
and adjusts the positions of the mirrors so as to stabilize the line of sight. </p>
|
| 393 |
+
<p id="p-71" num="71">[0046<confidence value="5">]</confidence>
|
| 394 |
+
Reference is now made to FIG. 5, which is cross-sectional view of an optical assembly <part-num-ref name="optical assembly">500</part-num-ref>
|
| 395 |
+
with lens and mirrors, for folding lens <part-num-ref name="with lens and mirrors, for folding lens">425,</part-num-ref>
|
| 396 |
+
in accordance with an embodiment of the subject invention. Light rays enter assembly <part-num-ref name="subject invention. Light rays enter assembly">500</part-num-ref>
|
| 397 |
+
through a window <part-num-ref name="window">510,</part-num-ref>
|
| 398 |
+
and are reflected through a series of two mirrors, mirror <part-num-ref name="series of two mirrors, mirror">520</part-num-ref>
|
| 399 |
+
and mirror <part-num-ref name="and mirror">530,</part-num-ref>
|
| 400 |
+
which directs them onto a lens <part-num-ref name="lens">540.</part-num-ref>
|
| 401 |
+
</p>
|
| 402 |
+
<p id="p-72" num="72">[0047<confidence value="5">]</confidence>
|
| 403 |
+
Mirror 530 is accurately positioned by motion compensation controller <part-num-ref name="is accurately positioned by motion compensation controller">430.</part-num-ref>
|
| 404 |
+
In accordance with the subject invention, the motion <boundary-data type="header">Atty. Docket No. 57399 -15-</boundary-data>
|
| 405 |
+
<page-break num="16"/>
|
| 406 |
+
compensation is determined by processing gyroscopic sensor information, global positioning system (GPS) data, and information from motor encoder <part-num-ref name="motion compensation is determined by processing gyroscopic sensor information, global positioning system (GPS) data, and information from motor encoder">440.</part-num-ref>
|
| 407 |
+
The line of sight is stabilized by the mirror in order to compensate for continuous camera movement generated by the motor, and also to compensate for forward movement generated from the flight path of the aircraft. As such, the line of sight is stabilized in two dimensions. Mirror <part-num-ref name="line of sight is stabilized in two dimensions. Mirror">530</part-num-ref>
|
| 408 |
+
is mounted on a piezoelectric tilt platform, and compensation is carried out by tilting the platform. Since the weight and size of mirror <part-num-ref name="weight and size of mirror">530</part-num-ref>
|
| 409 |
+
is small, motion compensation is efficient and accurate. </p>
|
| 410 |
+
<p id="p-73" num="73">
|
| 411 |
+
<confidence value="5">[</confidence>
|
| 412 |
+
0048<confidence value="5">]</confidence>
|
| 413 |
+
The stabilized line of sight of the camera is determined by the angle of mirror <part-num-ref name="angle of mirror">530.</part-num-ref>
|
| 414 |
+
The mirror angle is changed while the CCD is exposed through a control loop. Specifically, the camera angle is monitored by gyro control unit <part-num-ref name="camera angle is monitored by gyro control unit">405.</part-num-ref>
|
| 415 |
+
A control loop calculates the required mirror angle for maintaining the camera's line of sight. When a calculation indicates a required change in mirror angle, the control loop instructs the piezoelectric device to move the mirror, by applying appropriate voltage on each piezoelectric pole. The platform reacts to this voltage by moving the mirror, and the camera's line of sight is thereby maintained. </p>
|
| 416 |
+
<p id="p-74" num="74">
|
| 417 |
+
<confidence value="5">[</confidence>
|
| 418 |
+
0049<confidence value="5">]</confidence>
|
| 419 |
+
Reference is now made to FIG. 6, which is a simplified flowchart of a control loop that is used to stabilize a camera's line of sight, while the camera is in motion, in accordance with an embodiment of the subject invention. At step <part-num-ref name="subject invention. At step">610</part-num-ref>
|
| 420 |
+
a dynamically changing angle, A<confidence value="68">l,</confidence>
|
| 421 |
+
between the camera and the ground, is determined by gyroscopic control unit <part-num-ref name="ground, is determined by gyroscopic control unit">405.</part-num-ref>
|
| 422 |
+
At step <part-num-ref name="ground, is determined by gyroscopic control unit 405. At step">620</part-num-ref>
|
| 423 |
+
an angle of tilt of the mirror, A2, is calculated so that the direction of the line of sight of the camera, as determined by <boundary-data type="header">Atty. Docket No. 57399 -16-</boundary-data>
|
| 424 |
+
<page-break num="17"/>
|
| 425 |
+
angles A<confidence value="5">l</confidence>
|
| 426 |
+
and A2, is in a specified target direction, D. At step <part-num-ref name="specified target direction, D. At step">630</part-num-ref>
|
| 427 |
+
an appropriate voltage is applied to the piezoelectric platform, so that the mirror tilts in the calculated angle A2. Steps <part-num-ref name="calculated angle A2. Steps">610</part-num-ref>
|
| 428 |
+
- <part-num-ref name="-">630</part-num-ref>
|
| 429 |
+
form a control loop that compensates for the motion of the camera. </p>
|
| 430 |
+
<p id="p-75" num="75">[0050] The color images captured by the CCD cameras are separated into three components, R, G, B, where R is a red component, B is a blue component, and G is a green component. Each color component is represented as <part-num-ref name="green component. Each color component is represented as">8</part-num-ref>
|
| 431 |
+
bits per pixel. Conventional compression codecs separate the images into three components Y, Cr, Cb, where Y is a luminance component, and Cr and Cb are chrominance components. </p>
|
| 432 |
+
<p id="p-76" num="76">Since luminance is generally the dominant visual component, the three components are sampled at 4:2:2 relative depths. As such, raw data of <part-num-ref name="three components are sampled at 4:2:2 relative depths. As such, raw data of">24</part-num-ref>
|
| 433 |
+
bits per pixel is reduced to <part-num-ref name="bits per pixel is reduced to">16</part-num-ref>
|
| 434 |
+
bits per pixel. </p>
|
| 435 |
+
<p id="p-77" num="77">
|
| 436 |
+
<confidence value="5">[</confidence>
|
| 437 |
+
0051<confidence value="5">]</confidence>
|
| 438 |
+
Specifically for Bayer color CCDs, the density distribution of color elements often results in high frequency chroma data, which would lead to distortions if sub-sampling were not applied. Bayer CCDs are constructed from regular arrays of R, G and B filters, and captured images are separated into <part-num-ref name="density distribution of color elements often results in high frequency chroma data, which would lead to distortions if sub-sampling were not applied. Bayer CCDs are constructed from regular arrays of R, G and B filters, and captured images are separated into">4</part-num-ref>
|
| 439 |
+
mono-chromatic images; namely, <part-num-ref name="mono-chromatic images; namely,">1</part-num-ref>
|
| 440 |
+
red image, <part-num-ref name="red image,">1</part-num-ref>
|
| 441 |
+
blue image and <part-num-ref name="blue image and">2</part-num-ref>
|
| 442 |
+
green images. The mono-chromatic images are <part-num-ref name="mono-chromatic images are">8</part-num-ref>
|
| 443 |
+
bits per pixel, and they have <confidence value="65">/4</confidence>
|
| 444 |
+
the resolution of the input image. </p>
|
| 445 |
+
<p id="p-78" num="78">Compression of the mono-chromatic images often enhances Bayer images, since compression tends to reduce spurious high frequencies that arise from edges generated in Bayer images, which are especially noticeable in the luminance component of YCrCb images.</p>
|
| 446 |
+
<p id="p-79" num="79">
|
| 447 |
+
<confidence value="5">[</confidence>
|
| 448 |
+
0052<confidence value="2">1</confidence>
|
| 449 |
+
In an embodiment of the subject invention, <confidence value="5">J</confidence>
|
| 450 |
+
PEG <part-num-ref name="subject invention, JPEG">2000</part-num-ref>
|
| 451 |
+
compression is implemented using dedicated hardware with <confidence value="5">J</confidence>
|
| 452 |
+
PEG <part-num-ref name="compression is implemented using dedicated hardware with JPEG">2000</part-num-ref>
|
| 453 |
+
compression unit. </p>
|
| 454 |
+
<boundary-data type="header">Atty. Docket No. 57399 -17-</boundary-data>
|
| 455 |
+
<p id="p-80" num="80">
|
| 456 |
+
<page-break num="18"/>
|
| 457 |
+
[0053] Reference is now made to FIG. 7, which is a simplified block diagram of data compressor <part-num-ref name="simplified block diagram of data compressor">340,</part-num-ref>
|
| 458 |
+
in accordance with an embodiment of the subject invention. Data compression is essential in order to use standard I/O data storage interfaces, such as data link <part-num-ref name="subject invention. Data compression is essential in order to use standard I/O data storage interfaces, such as data link">8</part-num-ref>
|
| 459 |
+
in FIG. 3. </p>
|
| 460 |
+
<p id="p-81" num="81">Otherwise, without compression, storing raw CCD images would exceed the capacity of convention SATA data busses.</p>
|
| 461 |
+
<p id="p-82" num="82">[0054<confidence value="5">]</confidence>
|
| 462 |
+
Shown in FIG. 7 is a camera link <part-num-ref name="camera link">710,</part-num-ref>
|
| 463 |
+
such as link <part-num-ref name="camera link 710, such as link">3</part-num-ref>
|
| 464 |
+
in FIG. 3, which transmits data to a re-ordering unit <part-num-ref name="re-ordering unit">720.</part-num-ref>
|
| 465 |
+
Re-ordering unit <part-num-ref name="re-ordering unit 720. Re-ordering unit">720</part-num-ref>
|
| 466 |
+
transmits the re-ordered data to a tiling unit <part-num-ref name="tiling unit">730,</part-num-ref>
|
| 467 |
+
which in turn transmits the tiled data to an compression chip <part-num-ref name="compression chip">740</part-num-ref>
|
| 468 |
+
for <confidence value="5">J</confidence>
|
| 469 |
+
PEG <part-num-ref name="for JPEG">2000</part-num-ref>
|
| 470 |
+
compression. </p>
|
| 471 |
+
<p id="p-83" num="83">Tiling unit 730 partitions a large image into smaller image blocks, thereby accelerating processing time.</p>
|
| 472 |
+
<p id="p-84" num="84">
|
| 473 |
+
<confidence value="5">[</confidence>
|
| 474 |
+
0055<confidence value="5">]</confidence>
|
| 475 |
+
Reference is now made to FIG. 8, which is a simplified diagram illustrating how re-ordering unit <part-num-ref name="simplified diagram illustrating how re-ordering unit">720</part-num-ref>
|
| 476 |
+
re-orders pixel color values, in accordance with an embodiment of the subject invention. </p>
|
| 477 |
+
<p id="p-85" num="85">
|
| 478 |
+
<confidence value="5">[</confidence>
|
| 479 |
+
0056<confidence value="5">]</confidence>
|
| 480 |
+
It will be appreciated by those skil<confidence value="8">l</confidence>
|
| 481 |
+
ed in the art that the subject invention has widespread application to terrain modeling for cartography, reconnaissance and 3-D flight simulation. </p>
|
| 482 |
+
<p id="p-86" num="86">[0057<confidence value="5">]</confidence>
|
| 483 |
+
In the foregoing specification, the invention has been described with reference to specific exemplary embodiments thereof. It will, however, be evident that various modifications and changes may be made to the specific exemplary embodiments without departing from the broader spirit and scope of the invention as set forth in the appended claims. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. </p>
|
| 484 |
+
<boundary-data type="header">Atty. Docket No. 57399 -18-</boundary-data>
|
| 485 |
+
</description>
|
| 486 |
+
</us-patent-application>
|
| 487 |
+
|
applicant/11611822.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>11611822</doc-number>
|
| 8 |
+
<date>2009-12-10</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 Paragraph <confidence value="5">1</confidence>
|
| 15 |
+
0124<confidence value="4">1</confidence>
|
| 16 |
+
on page <part-num-ref name="on page">43</part-num-ref>
|
| 17 |
+
as follows: </p>
|
| 18 |
+
<p id="p-2" num="2">
|
| 19 |
+
<confidence value="8825">--(0</confidence>
|
| 20 |
+
124 While the machine-readable medium <part-num-ref name="machine-readable medium">352</part-num-ref>
|
| 21 |
+
is shown in an exemplary embodiment to be a<confidence value="5">,</confidence>
|
| 22 |
+
single medium, the term "machine-readable medium" should be taken to include a single medium or multiple media (e.g.<confidence value="5">,</confidence>
|
| 23 |
+
a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. <confidence value="686">The</confidence>
|
| 24 |
+
ter<confidence value="8">m</confidence>
|
| 25 |
+
"machine-readable medium" shall also be taken to include any medium that is capable of storing<confidence value="5">.</confidence>
|
| 26 |
+
encoding<confidence value="5">.</confidence>
|
| 27 |
+
or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present invention. The ter<confidence value="8">m</confidence>
|
| 28 |
+
"machine-readable medium" shall accordingly be taken to include<confidence value="5">,</confidence>
|
| 29 |
+
but not be limited to<confidence value="5">,</confidence>
|
| 30 |
+
solid-state <confidence value="2222222222222222">memories[[,]]and</confidence>
|
| 31 |
+
optical and magnetic media<confidence value="6">,</confidence>
|
| 32 |
+
<confidence value="555">and</confidence>
|
| 33 |
+
<confidence value="222222">carier</confidence>
|
| 34 |
+
<confidence value="5555">wave</confidence>
|
| 35 |
+
<confidence value="6">.</confidence>
|
| 36 |
+
<confidence value="88">--</confidence>
|
| 37 |
+
-2- </p>
|
| 38 |
+
</description>
|
| 39 |
+
</us-patent-application>
|
| 40 |
+
|
applicant/11627926.xml
ADDED
|
@@ -0,0 +1,153 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11627926</doc-number>
|
| 8 |
+
<date>2010-06-10</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">Attorney Docket No. 10070507-01-US</boundary-data>
|
| 14 |
+
<boundary-data type="header">Application No. 11<confidence value="5">/</confidence>
|
| 15 |
+
627,926 </boundary-data>
|
| 16 |
+
<boundary-data type="header">Customer No. 27,495</boundary-data>
|
| 17 |
+
<heading id="h-1">IN THE SPECIFICATION</heading>
|
| 18 |
+
<p id="p-1" num="1">Please amend the specification as follows:</p>
|
| 19 |
+
<p id="p-2" num="2">Please amend paragraph [015] as follows:</p>
|
| 20 |
+
<p id="p-3" num="3">[015] Noncoding transcripts have been identified in organisms belonging to all domains of life. These transcripts include microRNA, snoRNA, housekeeping (infrastructural) RNA (e.g.</p>
|
| 21 |
+
<p id="p-4" num="4">rRNA, tRNA, snRNA, SRP RNA), and tmRNA, Noncoding RNA include imprinted transcripts (e.g. H<confidence value="5">1</confidence>
|
| 22 |
+
9 and Air), dosage compensation transcripts (e.g. Xist mammalian X-inactive specific transcript), stress response transcripts, p<confidence value="5">o</confidence>
|
| 23 |
+
l III transcripts, and disease-associated transcripts. </p>
|
| 24 |
+
<p id="p-5" num="5">Many of the disease-associated transcripts are over expressed in cancers. A database of information on noncoding transcripts can be found at <confidence value="22">ht</confidence>
|
| 25 |
+
<confidence value="825">hap</confidence>
|
| 26 |
+
:(double slash)n<confidence value="5">c</confidence>
|
| 27 |
+
rna(dot)rn<confidence value="66">a(</confidence>
|
| 28 |
+
dot)n<confidence value="6658865882">et(dot)pl/</confidence>
|
| 29 |
+
Browser(do<confidence value="2188666">tlhtml.</confidence>
|
| 30 |
+
</p>
|
| 31 |
+
<p id="p-6" num="6">Please amend paragraph [129] as follows:</p>
|
| 32 |
+
<p id="p-7" num="7">
|
| 33 |
+
<confidence value="5">[</confidence>
|
| 34 |
+
129<confidence value="5">]</confidence>
|
| 35 |
+
More recently, methods have been developed to estimate the T<confidence value="5">m</confidence>
|
| 36 |
+
of DNA:RNA hybrids for use in anti-sense technology (Sugimoto, N., S. Nakano, M. Katoh, A. Matsumura, H. </p>
|
| 37 |
+
<p id="p-8" num="8">Nakamuta, T. <confidence value="2222222">Ohmichi</confidence>
|
| 38 |
+
, M. Yoneyama, and M. Sasaki. 1995. Thermodynamic parameters to predict stability of RNA/DNA hybrid duplexes. Biochemistry. 34(35):12,211-12,116; Gray, D.M., 1997. Derivation of nearest-neighbor properties from data on nucleic acid oligomers. <confidence value="668">II.</confidence>
|
| 39 |
+
</p>
|
| 40 |
+
<boundary-data type="header">
|
| 41 |
+
<confidence value="888">-2-</confidence>
|
| 42 |
+
</boundary-data>
|
| 43 |
+
<boundary-data type="header">Attorney Docket No. 10070507-01-US</boundary-data>
|
| 44 |
+
<boundary-data type="header">Application No. 11<confidence value="5">/</confidence>
|
| 45 |
+
627,926 </boundary-data>
|
| 46 |
+
<boundary-data type="header">Customer No. 27,495</boundary-data>
|
| 47 |
+
<p id="p-9" num="9">
|
| 48 |
+
<page-break num="2"/>
|
| 49 |
+
Thermodynamic parameters of DNA:RNA hybrids and DNA duplexes. Biopolymers. 42(7):795- 810) and Le Novere, N., <part-num-ref name="and Le Novere, N.,">2001.</part-num-ref>
|
| 50 |
+
MELTING, computing the melting temperature of nucleic acid duplex. Bioinformatics. 17(12):1226-1227). When the stability of RNA:RNA, RNA:DNA, and DNA:DNA were compared, the most stable duplex was RNA:RNA. Whether the RNA:DNA or DNA:DNA duplex was more stable was dependent upon the nucleotide sequence. This sequence dependence is considered when calculating the Tm of DNA:RNA based using the nearestneighbor method <confidence value="66">(h</confidence>
|
| 51 |
+
http:(double slash<confidence value="5">)</confidence>
|
| 52 |
+
bioweb<confidence value="5">(</confidence>
|
| 53 |
+
dot<confidence value="66">)p</confidence>
|
| 54 |
+
asteur<confidence value="5">(</confidence>
|
| 55 |
+
dot<confidence value="5885">)fr(</confidence>
|
| 56 |
+
slash<confidence value="488">)se</confidence>
|
| 57 |
+
anal<confidence value="5">(</confidence>
|
| 58 |
+
slash<confidence value="2">l</confidence>
|
| 59 |
+
interfaces<confidence value="5">(</confidence>
|
| 60 |
+
slash<confidence value="5">)</confidence>
|
| 61 |
+
meltin<confidence value="4">g</confidence>
|
| 62 |
+
(dothtml). The nearestneighbor equation for DNA and RNA-based oligos is: <part-num-ref name="nearestneighbor equation for DNA and RNA-based oligos is:">(1)</part-num-ref>
|
| 63 |
+
T<confidence value="5">m</confidence>
|
| 64 |
+
= (1000AH/A + AS + R<confidence value="68">ln</confidence>
|
| 65 |
+
(C/4)) - 273.15 + 16.6 log[Na<confidence value="66">+]</confidence>
|
| 66 |
+
(For DNA see: Breslauer, K, J., R. Frank, H. Blocker, L. A. </p>
|
| 67 |
+
<p id="p-10" num="10">Marky, 1986. Proc. <confidence value="2222">Natl</confidence>
|
| 68 |
+
. Acad. Sci. USA 83:3746-3750 and for RNA see: Fre<confidence value="5">i</confidence>
|
| 69 |
+
er, S. M., R. </p>
|
| 70 |
+
<p id="p-11" num="11">Kierzek, J. A. Jaeger, N. Sugimoto, M. H. Caruthers, T. Neilson, D. H. Turner, <part-num-ref name="Jaeger, N. Sugimoto, M. H. Caruthers, T. Neilson, D. H. Turner,">1986.</part-num-ref>
|
| 71 |
+
Proc. <confidence value="22228">Natl.</confidence>
|
| 72 |
+
</p>
|
| 73 |
+
<p id="p-12" num="12">Acad. Sci. 83:9373-9377) AH (K<confidence value="5">c</confidence>
|
| 74 |
+
al/mol) is the sum of the nearest-neighbor enthalpy changes for duplexes. A is a constant containing corrections for helix initiation. AS is the sum of the nearest-neighbor entropy changes. R is the Gas Constant (1.99 cal K-<confidence value="4">l</confidence>
|
| 75 |
+
mol-1), and C is the concentration of the oligonucleotides. Exemplary AH and AS values for nearest neighbor interactions of DNA and RNA are shown in Table <part-num-ref name="oligonucleotides. Exemplary AH and AS values for nearest neighbor interactions of DNA and RNA are shown in Table">1.</part-num-ref>
|
| 76 |
+
In many <confidence value="8">c</confidence>
|
| 77 |
+
ases this equation gives values that are no more than <part-num-ref name="oligonucleotides. Exemplary AH and AS values for nearest neighbor interactions of DNA and RNA are shown in Table 1. In many cases this equation gives values that are no more than">5</part-num-ref>
|
| 78 |
+
<confidence value="1">0</confidence>
|
| 79 |
+
C from the empirical value. It is good to note that this equation includes a factor to adjust for salt concentration. </p>
|
| 80 |
+
<p id="p-13" num="13">Please amend paragraph [200] as follows:</p>
|
| 81 |
+
<boundary-data type="header">
|
| 82 |
+
<confidence value="888">-3-</confidence>
|
| 83 |
+
</boundary-data>
|
| 84 |
+
<boundary-data type="header">Attorney Docket No. 10070507-01-US</boundary-data>
|
| 85 |
+
<boundary-data type="header">Application No. 11/627,926</boundary-data>
|
| 86 |
+
<boundary-data type="header">Customer No. 27,495</boundary-data>
|
| 87 |
+
<p id="p-14" num="14">
|
| 88 |
+
<page-break num="3"/>
|
| 89 |
+
[20<confidence value="66">0]</confidence>
|
| 90 |
+
Polyadenylation control RNA templates were used as positive and negative controls in PAP reactions. A single-stranded <confidence value="5">R</confidence>
|
| 91 |
+
NA representing a previously-identified miRNA (Griffiths-Jones, S., R. J. Grocock, S. van Dongen, A. Bateman, A. J. Enright. <part-num-ref name="J. Enright.">2006.</part-num-ref>
|
| 92 |
+
miR<confidence value="5">B</confidence>
|
| 93 |
+
ase: </p>
|
| 94 |
+
<p id="p-15" num="15">microRNA sequences, targets and gene nomenclature. Nucleic Acids Res., 34:<confidence value="5">D</confidence>
|
| 95 |
+
140-D144 and Griffiths-Jones, <confidence value="5">S</confidence>
|
| 96 |
+
. 2004. The microRNA Registry. Nucleic Acids Res. 32:<confidence value="5">D</confidence>
|
| 97 |
+
109-D<confidence value="4">1</confidence>
|
| 98 |
+
11) or a miRNA not having significant homology to any previously-described <confidence value="588">miR</confidence>
|
| 99 |
+
NA (Alien; Table 2; </p>
|
| 100 |
+
<p id="p-16" num="16">SEQ ID NO:52) were used to test various polyadenylation conditions, to determine assay sensitivities, and to quantitate relative detection percentages in specificity assays. Nucleotide sequences of the mature miRNA were obtained from the most recent release of database provided at http<confidence value="5244411556156525222112255142">./iia1aangct.ac.uk/sequnccs/</confidence>
|
| 101 |
+
<confidence value="22222222222">hap:(double</confidence>
|
| 102 |
+
slash<confidence value="5">)</confidence>
|
| 103 |
+
micro<confidence value="6686">rna(</confidence>
|
| 104 |
+
dot<confidence value="4">)</confidence>
|
| 105 |
+
san<confidence value="58858866">ger(dot)</confidence>
|
| 106 |
+
ac(dot)uk(slash)sequences(slash<confidence value="4">)</confidence>
|
| 107 |
+
. The naming convention in the database (Ambros, V., B. Bartel, D. P. Bartel, C. B. Burge, J. C. Carrington, X. Chen, <confidence value="68">G.</confidence>
|
| 108 |
+
</p>
|
| 109 |
+
<p id="p-17" num="17">Dreyfuss, S. R. Eddy, S. Griffiths-Jones, M. Marshall, M. Matzke, <confidence value="5">G</confidence>
|
| 110 |
+
. Ruvkun, T. <confidence value="222222">Tuschl</confidence>
|
| 111 |
+
. 2003. </p>
|
| 112 |
+
<p id="p-18" num="18">A uniform system for microRNA annotation. RNA, 2003, 9(3):277-279) is used herein.</p>
|
| 113 |
+
<p id="p-19" num="19">Please amend paragraph [283] as follows:</p>
|
| 114 |
+
<p id="p-20" num="20">
|
| 115 |
+
<confidence value="5">[</confidence>
|
| 116 |
+
283] In this experiment, all % relative detections were less than 1 %. In order to determine how these results compare to existing technologies, they were compared to the <confidence value="885">Taq</confidence>
|
| 117 |
+
Man <confidence value="5">®</confidence>
|
| 118 |
+
MicroRNA Assays from Applied Biosystems and the miRCURYTM LNA Arrays from Exiqon. The % relative detection in this experiment are significantly less than the % <boundary-data type="header">
|
| 119 |
+
<confidence value="888">-4-</confidence>
|
| 120 |
+
</boundary-data>
|
| 121 |
+
<page-break num="4"/>
|
| 122 |
+
<boundary-data type="header">Attorney Docket No. 10070507-01-US</boundary-data>
|
| 123 |
+
<boundary-data type="header">Application No. 11<confidence value="5">/</confidence>
|
| 124 |
+
627,926 </boundary-data>
|
| 125 |
+
<boundary-data type="header">Customer No. 27,495</boundary-data>
|
| 126 |
+
relative detection reported for the Ta<confidence value="5">q</confidence>
|
| 127 |
+
Man<confidence value="4">®</confidence>
|
| 128 |
+
MicroRNA Assays (Caif<confidence value="2">u</confidence>
|
| 129 |
+
, C., D. A. Ridzon, A. J. </p>
|
| 130 |
+
<p id="p-21" num="21">
|
| 131 |
+
<confidence value="2222222">Broomer</confidence>
|
| 132 |
+
, Z. Zhou, D. H. Lee, J. T. Nguyen, M. Barbisin, N. L. Xu, V. R. Mahuvakar, M. </p>
|
| 133 |
+
<p id="p-22" num="22">R.Andersen, K. Q. Lao, K. J. Livak, K. J. Guegler. 2005. Real-time quantification of microRNAs by stem-loop RT-PCR. Nucleic Acids Res. 33(20): e<confidence value="5">1</confidence>
|
| 134 |
+
79). In particular, 3.7 and 2.5 % relative detection was observed with l<confidence value="5">e</confidence>
|
| 135 |
+
t-7a miRNA assay and the let-7<confidence value="5">c</confidence>
|
| 136 |
+
synthetic template and let-7c miRNA assay and the let-7b synthetic template, respectively. The % relative detection for this experiment is also significantly less than that demonstrated with the miRCUR<confidence value="66">YT</confidence>
|
| 137 |
+
M LNA Arrays <confidence value="82">(h</confidence>
|
| 138 |
+
http:(double <confidence value="222222222222222222222222">slash)www(dotlexiqon(dot</confidence>
|
| 139 |
+
<confidence value="885">com</confidence>
|
| 140 |
+
(slash<confidence value="4">)</confidence>
|
| 141 |
+
SEE<confidence value="5">E</confidence>
|
| 142 |
+
MS(slash)26(dot)asp). In particular, up to <part-num-ref name="miRCURYTM LNA Arrays (h http:(double slash)www(dotlexiqon(dot com (slash)SEEEMS(slash)26(dot)asp). In particular, up to">20</part-num-ref>
|
| 143 |
+
and <part-num-ref name="and">35</part-num-ref>
|
| 144 |
+
% relative detection of let-7b and let-7e, respectively, with the let-7a capture probe was reported. Additionally, let-7a was detected at <part-num-ref name="let-7a capture probe was reported. Additionally, let-7a was detected at">7</part-num-ref>
|
| 145 |
+
- <part-num-ref name="-">18</part-num-ref>
|
| 146 |
+
% relative detection with let-7b, <confidence value="5">l</confidence>
|
| 147 |
+
et-7e, and let-7f capture probes. These comparisons clearly demonstrate that the method described herein has higher specificity than competing technologies. </p>
|
| 148 |
+
<boundary-data type="header">
|
| 149 |
+
<confidence value="888">-5-</confidence>
|
| 150 |
+
</boundary-data>
|
| 151 |
+
</description>
|
| 152 |
+
</us-patent-application>
|
| 153 |
+
|
applicant/11670633.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
applicant/11676496.xml
ADDED
|
@@ -0,0 +1,234 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11676496</doc-number>
|
| 8 |
+
<date>2007-02-19</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">SELF-CONTAINED ILLUMINATED BUS SIGNAL</heading>
|
| 14 |
+
<p id="p-1" num="1">Priority Data Priority of U.S. Provisional Application No. 60/774628, filed 02/21/2006 is hereby claimed.</p>
|
| 15 |
+
<heading id="h-2">BACKGROUND OF THE INVENTION</heading>
|
| 16 |
+
<p id="p-2" num="2">
|
| 17 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 18 |
+
Field of the Invention The invention is to a bus stop sign and attention getter having self-contained solar powered, selective useable illumination for information dissemination and bus driver notification. </p>
|
| 19 |
+
<p id="p-3" num="3">Description of Related Art <boundary-data type="line-number">10 </boundary-data>
|
| 20 |
+
The prior art is crowded with roadside signs that include solar-powered illumination. </p>
|
| 21 |
+
<p id="p-4" num="4">Examples include P. Gibson (U.S. Patent No. 4,108,405, issued August 22, 1978) and D. Doan (U.S. Patent 4,200,904, issued April <part-num-ref name="and D. Doan (U.S. Patent 4,200,904, issued April">29,</part-num-ref>
|
| 22 |
+
<part-num-ref name="and D. Doan (U.S. Patent 4,200,904, issued April 29,">1980)</part-num-ref>
|
| 23 |
+
and W. Daigle, Jr. (U.S. Patent No. 6,131,321, issued Oct. <part-num-ref name="and W. Daigle, Jr. (U.S. Patent No. 6,131,321, issued Oct.">17,</part-num-ref>
|
| 24 |
+
<part-num-ref name="and W. Daigle, Jr. (U.S. Patent No. 6,131,321, issued Oct. 17,">2000)</part-num-ref>
|
| 25 |
+
and R. Jones (U.S. Patent No. 6,522,263, issued February <part-num-ref name="and R. Jones (U.S. Patent No. 6,522,263, issued February">18,</part-num-ref>
|
| 26 |
+
<part-num-ref name="and R. Jones (U.S. Patent No. 6,522,263, issued February 18,">2003)</part-num-ref>
|
| 27 |
+
and K. Lee (U.S. Patent No. 6,968,640, issued November <part-num-ref name="and K. Lee (U.S. Patent No. 6,968,640, issued November">29,</part-num-ref>
|
| 28 |
+
<part-num-ref name="and K. Lee (U.S. Patent No. 6,968,640, issued November 29,">2005)</part-num-ref>
|
| 29 |
+
and <boundary-data type="line-number">15 </boundary-data>
|
| 30 |
+
C. Tseng (U.S. Publication No. 2004/0076013 A<confidence value="5">l</confidence>
|
| 31 |
+
, published April <part-num-ref name="and C. Tseng (U.S. Publication No. 2004/0076013 Al, published April">22,</part-num-ref>
|
| 32 |
+
2004), and C. Beverly (U.S. Publication No. 2006/0139156 A<confidence value="5">l</confidence>
|
| 33 |
+
, published June <part-num-ref name="and C. Tseng (U.S. Publication No. 2004/0076013 Al, published April 22, 2004), and C. Beverly (U.S. Publication No. 2006/0139156 Al, published June">29,</part-num-ref>
|
| 34 |
+
2006). </p>
|
| 35 |
+
<boundary-data type="header">
|
| 36 |
+
<confidence value="8">1</confidence>
|
| 37 |
+
</boundary-data>
|
| 38 |
+
<p id="p-5" num="5">
|
| 39 |
+
<page-break num="2"/>
|
| 40 |
+
The providing of a "u" shape sign support or post with a reflective cover is disclosed by A. Burlando (U.S. Patent No. 6,158,379, issued December <part-num-ref name="Burlando (U.S. Patent No. 6,158,379, issued December">12,</part-num-ref>
|
| 41 |
+
<part-num-ref name="Burlando (U.S. Patent No. 6,158,379, issued December 12,">2000)</part-num-ref>
|
| 42 |
+
and A. Burlando (U.S. Patent No. 6,233,898, issued May <part-num-ref name="Burlando (U.S. Patent No. 6,233,898, issued May">22,</part-num-ref>
|
| 43 |
+
2001). </p>
|
| 44 |
+
<p id="p-6" num="6">D. Jones et al (U.S. Patent No. 6,943,698, issued September 13, 2005) disclose a <boundary-data type="line-number">5 </boundary-data>
|
| 45 |
+
traffic control sign with LED attraction. R. Patty (U.S. Patent No. 4,042,919, issued August <part-num-ref name="traffic control sign with LED attraction. R. Patty (U.S. Patent No. 4,042,919, issued August">16,</part-num-ref>
|
| 46 |
+
<part-num-ref name="traffic control sign with LED attraction. R. Patty (U.S. Patent No. 4,042,919, issued August 16,">1977)</part-num-ref>
|
| 47 |
+
teaches an illuminated sign with on/off switch for an intermittently activating a strobe light and illumination light. C. Tseng (U.S. 2004/0076013, published April <part-num-ref name="strobe light and illumination light. C. Tseng (U.S. 2004/0076013, published April">22,</part-num-ref>
|
| 48 |
+
<part-num-ref name="strobe light and illumination light. C. Tseng (U.S. 2004/0076013, published April 22,">2004)</part-num-ref>
|
| 49 |
+
teaches an illuminated door plate using a solar panel, battery and control. </p>
|
| 50 |
+
<heading id="h-3">SUMMARY OF THE INVENTION</heading>
|
| 51 |
+
<p id="p-7" num="7">
|
| 52 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 53 |
+
The invention is to a bus stop sign. Two primary signs are supported by a vertical support or bus shelter. One sign lists bus schedules and the other select information. The second sign, preferably in more than one language and brail, gives instructions on use of the sign illumination. The sign can be illuminated by pressing on a button or switch to read sign information and/or to notify an oncoming bus driver to stop because passengers are waiting. </p>
|
| 54 |
+
<p id="p-8" num="8">
|
| 55 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 56 |
+
The illumination is by various light sources powered by a solar panel battery combination activated by a manually ADA pressed switch or button. A reflector is positioned on the support for calling attention to the bus stop at night or during inclement weather. <part-num-ref name="bus stop at night or during inclement weather.">28</part-num-ref>
|
| 57 |
+
<part-num-ref name="">29</part-num-ref>
|
| 58 |
+
<boundary-data type="header">
|
| 59 |
+
<confidence value="8">2</confidence>
|
| 60 |
+
</boundary-data>
|
| 61 |
+
<page-break num="3"/>
|
| 62 |
+
</p>
|
| 63 |
+
<heading id="h-4">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 64 |
+
<p id="p-9" num="9">Fig. 1 is a perspective view of the bus stop sign of the invention.</p>
|
| 65 |
+
<p id="p-10" num="10">Fig. 2 is a sectional view along the section line 2-2 of Fig. 1 Fig. 3 is a simplified block diagram of the electric circuit of the invention.</p>
|
| 66 |
+
<heading id="h-5">DESCRIPTION OF THE PREFERRED EMBODIMENTS</heading>
|
| 67 |
+
<p id="p-11" num="11">
|
| 68 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 69 |
+
A bus stop sign and attention getter 1 is used by passengers for information dissemination. </p>
|
| 70 |
+
<p id="p-12" num="12">The primary support for the sign panel can be a bus shelter but is preferably a <confidence value="666">"u"</confidence>
|
| 71 |
+
shape pole <part-num-ref name=""u" shape pole">2</part-num-ref>
|
| 72 |
+
having its lower end supported by or imbedded in the ground or a solid surface. </p>
|
| 73 |
+
<p id="p-13" num="13">
|
| 74 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 75 |
+
The upper end can support or house an adjustable or swivel hood <part-num-ref name="adjustable or swivel hood">6.</part-num-ref>
|
| 76 |
+
The hood can be on a pipe <part-num-ref name="pipe">19</part-num-ref>
|
| 77 |
+
or other generally vertical stanchion attached to the vertical support. The hood can be rotated or pivoted <part-num-ref name="hood can be rotated or pivoted">61</part-num-ref>
|
| 78 |
+
to aim it in the direction illumination is desired. The pipe can be raised or lowered <part-num-ref name="pipe can be raised or lowered">62</part-num-ref>
|
| 79 |
+
in the support <part-num-ref name="support">2</part-num-ref>
|
| 80 |
+
or moved. The open side of the support is covered in part or totally by one or more signs <part-num-ref name="support is covered in part or totally by one or more signs">3,</part-num-ref>
|
| 81 |
+
<part-num-ref name="support is covered in part or totally by one or more signs 3,">9,</part-num-ref>
|
| 82 |
+
a reflector panel <part-num-ref name="reflector panel">23,</part-num-ref>
|
| 83 |
+
an illumination device and <boundary-data type="line-number">15 </boundary-data>
|
| 84 |
+
shield <part-num-ref name="illumination device and shield">7</part-num-ref>
|
| 85 |
+
and an illuminator switch <part-num-ref name="illuminator switch">8.</part-num-ref>
|
| 86 |
+
Along the length of the primary support <part-num-ref name="primary support">2</part-num-ref>
|
| 87 |
+
the wiring <part-num-ref name="wiring">24</part-num-ref>
|
| 88 |
+
for illumination is enclosed and protected within the recessed area <part-num-ref name="recessed area">21</part-num-ref>
|
| 89 |
+
of the support <part-num-ref name="support">2</part-num-ref>
|
| 90 |
+
by the <boundary-data type="header">
|
| 91 |
+
<confidence value="8">3</confidence>
|
| 92 |
+
</boundary-data>
|
| 93 |
+
<page-break num="4"/>
|
| 94 |
+
signs and reflector. An electrical supply combination <part-num-ref name="electrical supply combination">20</part-num-ref>
|
| 95 |
+
is also supported by the upper end of the primary support. A reflective tape <part-num-ref name="reflective tape">25</part-num-ref>
|
| 96 |
+
can extend over the sign above the reflector shield and under indicia to enhance visibility of the bus stop sign <part-num-ref name="bus stop sign">1</part-num-ref>
|
| 97 |
+
and its sign panel <part-num-ref name="and its sign panel">3.</part-num-ref>
|
| 98 |
+
</p>
|
| 99 |
+
<p id="p-14" num="14">The electric energy for the sign and bus driver notification illumination <part-num-ref name="sign and bus driver notification illumination">6</part-num-ref>
|
| 100 |
+
is provided <boundary-data type="line-number">5 </boundary-data>
|
| 101 |
+
by a solar panel <part-num-ref name="solar panel">9</part-num-ref>
|
| 102 |
+
and battery pack <part-num-ref name="and battery pack">5,</part-num-ref>
|
| 103 |
+
<part-num-ref name="and battery pack 5,">11.</part-num-ref>
|
| 104 |
+
A battery box <part-num-ref name="battery box">11</part-num-ref>
|
| 105 |
+
has an inner side secured to the upper end of the primary "u" support <part-num-ref name="primary "u" support">2.</part-num-ref>
|
| 106 |
+
The battery box inner side can be secured so as to be rotatable around the support. A battery <part-num-ref name="battery">5</part-num-ref>
|
| 107 |
+
can be placed in and locked into the battery box <part-num-ref name="battery box">11.</part-num-ref>
|
| 108 |
+
</p>
|
| 109 |
+
<p id="p-15" num="15">A solar panel 4 can be pivotally secured to the upper battery box outer side. The solar panel can be pivoted in the vertical plane <part-num-ref name="vertical plane">41</part-num-ref>
|
| 110 |
+
and in the horizontal plane <part-num-ref name="horizontal plane">42</part-num-ref>
|
| 111 |
+
so that it can be faced <boundary-data type="line-number">10 </boundary-data>
|
| 112 |
+
toward the sun. The solar panel <part-num-ref name="solar panel">4</part-num-ref>
|
| 113 |
+
is used to charge the battery <part-num-ref name="battery">5</part-num-ref>
|
| 114 |
+
and the battery is used to supply electricity to the illuminators under control of a manually operated switch <part-num-ref name="manually operated switch">8.</part-num-ref>
|
| 115 |
+
</p>
|
| 116 |
+
<p id="p-16" num="16">To be effective during all conditions, an illumination swivel hood <part-num-ref name="illumination swivel hood">6</part-num-ref>
|
| 117 |
+
is provided. </p>
|
| 118 |
+
<p id="p-17" num="17">The hood can be supported by a pipe <part-num-ref name="pipe">19</part-num-ref>
|
| 119 |
+
that is rotated <part-num-ref name="that is rotated">61</part-num-ref>
|
| 120 |
+
and raised or lowered <part-num-ref name="and raised or lowered">62</part-num-ref>
|
| 121 |
+
within the "u" shape primary support upper end so as to selectively face oncoming traffic and <boundary-data type="line-number">15 </boundary-data>
|
| 122 |
+
illuminate any sign and other article secured to the support. The hood houses illuminators for the sign that can be varied to include a white <part-num-ref name="white">13</part-num-ref>
|
| 123 |
+
and red or blue or green LED <part-num-ref name="and red or blue or green LED">14</part-num-ref>
|
| 124 |
+
for attracting attention to the sign. A flashing strobe light <part-num-ref name="flashing strobe light">15</part-num-ref>
|
| 125 |
+
can be included as an attention getter from a distance to identify and alert the bus driver that passengers are waiting at the stop. The color light(s) reflects off the reflectors <part-num-ref name="reflectors">23,</part-num-ref>
|
| 126 |
+
<part-num-ref name="reflectors 23,">25</part-num-ref>
|
| 127 |
+
adding to the attention-getting effect. </p>
|
| 128 |
+
<boundary-data type="header">
|
| 129 |
+
<confidence value="8">4</confidence>
|
| 130 |
+
</boundary-data>
|
| 131 |
+
<p id="p-18" num="18">
|
| 132 |
+
<page-break num="5"/>
|
| 133 |
+
The inner upper hood 29 can be painted white or have some other reflective surface to assist lighting the signs(s). The hood <part-num-ref name="hood">6</part-num-ref>
|
| 134 |
+
pipe support <part-num-ref name="pipe support">19</part-num-ref>
|
| 135 |
+
lower extent is shown housed within the "u" shape pole <part-num-ref name=""u" shape pole">2</part-num-ref>
|
| 136 |
+
upper end by a strap <part-num-ref name="strap">26.</part-num-ref>
|
| 137 |
+
In the event it is desired to place the sign on a shelter or other support, the pipe <part-num-ref name="pipe">19</part-num-ref>
|
| 138 |
+
and hood <part-num-ref name="and hood">6</part-num-ref>
|
| 139 |
+
can be removed and positioned on an <boundary-data type="line-number">5 </boundary-data>
|
| 140 |
+
adjacent support. To accommodate alinement of the hood with oncoming traffic when removed from the pole <part-num-ref name="pole">2</part-num-ref>
|
| 141 |
+
a universal joint <part-num-ref name="universal joint">28</part-num-ref>
|
| 142 |
+
is provided in the pipe. </p>
|
| 143 |
+
<p id="p-19" num="19">A driver alert sign 9 can be placed near the mid to lower extent of the primary support. The alert sign <part-num-ref name="alert sign">9</part-num-ref>
|
| 144 |
+
provides information about sign operation in several languages such as English, Spanish and braille. The sign is provided with a light that can be used for reading <boundary-data type="line-number">10 </boundary-data>
|
| 145 |
+
the information on the sign <part-num-ref name="sign">9</part-num-ref>
|
| 146 |
+
during dark or inclement weather. The button or switch <part-num-ref name="button or switch">8</part-num-ref>
|
| 147 |
+
is provided for actuating the light for this purpose as well as for alerting the bus driver to stop. </p>
|
| 148 |
+
<p id="p-20" num="20">The lights in housing shield 7 are primarily for illuminating the sign <part-num-ref name="sign">9</part-num-ref>
|
| 149 |
+
and are white lights <part-num-ref name="and are white lights">17,</part-num-ref>
|
| 150 |
+
<part-num-ref name="and are white lights 17,">18.</part-num-ref>
|
| 151 |
+
The lights in housing hood <part-num-ref name="lights in housing hood">6</part-num-ref>
|
| 152 |
+
perform the dual purpose of illuminating the sign <part-num-ref name="sign">3</part-num-ref>
|
| 153 |
+
and notifying the bus driver that a passenger is waiting to be picked up. For this <boundary-data type="line-number">15 </boundary-data>
|
| 154 |
+
reason it is preferred that a "white" light <part-num-ref name=""white" light">13</part-num-ref>
|
| 155 |
+
be provided in the hood with a flashing strobe light <part-num-ref name="flashing strobe light">15</part-num-ref>
|
| 156 |
+
and/or one or more L.E.D. color lights <part-num-ref name="and/or one or more L.E.D. color lights">14.</part-num-ref>
|
| 157 |
+
The lights, and in particular the color light(s), illuminate the sign and reflector(s) to enhance visibility and aesthetics. </p>
|
| 158 |
+
<boundary-data type="header">
|
| 159 |
+
<confidence value="8">5</confidence>
|
| 160 |
+
</boundary-data>
|
| 161 |
+
<p id="p-21" num="21">
|
| 162 |
+
<page-break num="6"/>
|
| 163 |
+
The solar panel can be composed of a single 1.26 W solar module that is about <part-num-ref name="single 1.26 W solar module that is about">7</part-num-ref>
|
| 164 |
+
inches in length, <part-num-ref name="inches in length,">6</part-num-ref>
|
| 165 |
+
inches in width and 1/4 inch thick, having a weight of about <part-num-ref name="weight of about">5</part-num-ref>
|
| 166 |
+
ounces. </p>
|
| 167 |
+
<p id="p-22" num="22">The panel array, when connected to the charging circuitry, can provide enough solar power to operate the system for years.</p>
|
| 168 |
+
<p id="p-23" num="23">
|
| 169 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 170 |
+
The preferred box 11 and battery <part-num-ref name="and battery">5</part-num-ref>
|
| 171 |
+
used can vary. The battery used can be a 12-volt battery. It can be a sealed lead acid rechargeable battery having an excellent temperature performance and very long life. Its length can be <part-num-ref name="excellent temperature performance and very long life. Its length can be">6</part-num-ref>
|
| 172 |
+
and 1/8 inches, with a width of <part-num-ref name="width of">6</part-num-ref>
|
| 173 |
+
and 5/8 inches, and a weight of <part-num-ref name="weight of">9</part-num-ref>
|
| 174 |
+
pounds. It is stored in a custom made galvanized lock box. The box can have a length of <part-num-ref name="length of">6</part-num-ref>
|
| 175 |
+
and inches, with a width of <part-num-ref name="width of">6</part-num-ref>
|
| 176 |
+
and 7/8 inches and a <boundary-data type="line-number">10 </boundary-data>
|
| 177 |
+
weight of <part-num-ref name="weight of">8</part-num-ref>
|
| 178 |
+
ounces. </p>
|
| 179 |
+
<p id="p-24" num="24">As to the swivel hood <part-num-ref name="swivel hood">6,</part-num-ref>
|
| 180 |
+
the hood can be made of a galvanized sheet metal. The hood length can be <part-num-ref name="hood length can be">4</part-num-ref>
|
| 181 |
+
- <part-num-ref name="-">6</part-num-ref>
|
| 182 |
+
inches with a height of <part-num-ref name="height of">2</part-num-ref>
|
| 183 |
+
- <part-num-ref name="-">4</part-num-ref>
|
| 184 |
+
inches and a weight of about <part-num-ref name="weight of about">5</part-num-ref>
|
| 185 |
+
ounces. </p>
|
| 186 |
+
<p id="p-25" num="25">The support pipe 19 can be a Condor pipe. This inch galvanized metal pipe can enclose the wiring, protecting it from the weather and vandalism, and can be used as an extension for <boundary-data type="line-number">15 </boundary-data>
|
| 187 |
+
the Swivel Hood. </p>
|
| 188 |
+
<p id="p-26" num="26">As to the illuminators, it is preferred that the high-powered L.E.D. utility reading light can be used. Its length can be about <part-num-ref name="high-powered L.E.D. utility reading light can be used. Its length can be about">2</part-num-ref>
|
| 189 |
+
inches with a width of about <part-num-ref name="width of about">1</part-num-ref>
|
| 190 |
+
and 1/8 inches and a weight of about <part-num-ref name="weight of about">1</part-num-ref>
|
| 191 |
+
ounce. </p>
|
| 192 |
+
<boundary-data type="header">
|
| 193 |
+
<confidence value="8">6</confidence>
|
| 194 |
+
</boundary-data>
|
| 195 |
+
<p id="p-27" num="27">
|
| 196 |
+
<page-break num="7"/>
|
| 197 |
+
The tamper resistant reflection shield 23 can be made of galvanized sheet metal. It is about <part-num-ref name="can be made of galvanized sheet metal. It is about">3</part-num-ref>
|
| 198 |
+
inches in width, the length can be about <part-num-ref name="length can be about">5</part-num-ref>
|
| 199 |
+
inches and it can be 1/4 inch thick with a weight of about <part-num-ref name="weight of about">1</part-num-ref>
|
| 200 |
+
pound. </p>
|
| 201 |
+
<p id="p-28" num="28">As to the switch <part-num-ref name="switch">8,</part-num-ref>
|
| 202 |
+
an ADA heavy-duty tension switch with a <part-num-ref name="">2</part-num-ref>
|
| 203 |
+
inch mushroom <boundary-data type="line-number">5 </boundary-data>
|
| 204 |
+
plunger is preferred. It can have a <part-num-ref name="">4</part-num-ref>
|
| 205 |
+
and inch length with a <part-num-ref name="">2</part-num-ref>
|
| 206 |
+
and inch width and can weigh about <part-num-ref name="and inch width and can weigh about">1</part-num-ref>
|
| 207 |
+
pound. </p>
|
| 208 |
+
<p id="p-29" num="29">The electrical circuitry 30 is quite simple. The solar panel <part-num-ref name="solar panel">4</part-num-ref>
|
| 209 |
+
provides a charge for the battery <part-num-ref name="battery">5.</part-num-ref>
|
| 210 |
+
The battery is used to power the illumination devices for viewing the information panel <part-num-ref name="information panel">9</part-num-ref>
|
| 211 |
+
and sign <part-num-ref name="and sign">3</part-num-ref>
|
| 212 |
+
as well as for notifying the bus driver that a stop is to be made to pick up <boundary-data type="line-number">10 </boundary-data>
|
| 213 |
+
passengers. Because of the large amount of time the device <part-num-ref name="device">1</part-num-ref>
|
| 214 |
+
is not in use, the only time illumination is necessary is when a rider needs to review the bus schedule or board a bus. In view of this, the illumination devices are both activated simultaneously. The positioning of the switch <part-num-ref name="switch">8</part-num-ref>
|
| 215 |
+
is such that the switch can be pushed and the signs observed at the same time by most people. The illumination can be limited to the actual time the passenger pushes on the <boundary-data type="line-number">15 </boundary-data>
|
| 216 |
+
switch or button <part-num-ref name="switch or button">8.</part-num-ref>
|
| 217 |
+
As an optional alternative, a timing device <part-num-ref name="timing device">10</part-num-ref>
|
| 218 |
+
can be installed in the circuit so that pushing the switch activates the lights for a time certain, such as for <part-num-ref name="time certain, such as for">5</part-num-ref>
|
| 219 |
+
to <part-num-ref name="to">30</part-num-ref>
|
| 220 |
+
seconds. This is usually enough time for the signs to be read and/or the bus driver to observe that a passenger is waiting. In the event it is not, the switch can be pressed a second time. </p>
|
| 221 |
+
<boundary-data type="header">
|
| 222 |
+
<confidence value="8">7</confidence>
|
| 223 |
+
</boundary-data>
|
| 224 |
+
<p id="p-30" num="30">
|
| 225 |
+
<page-break num="8"/>
|
| 226 |
+
The switch precludes the need for passengers to expose themselves to traffic for flagging down a bus and precludes unnecessary stops by bus drivers. </p>
|
| 227 |
+
<p id="p-31" num="31">It is believed that the construction, operation and advantages of this invention will be apparent to those skilled in the art. It is to be understood that the present disclosure is <boundary-data type="line-number">5 </boundary-data>
|
| 228 |
+
illustrative only and that changes, variations, substitutions, modifications and equivalents will be readily apparent to one skilled in the art and that such may be made without departing from the spirit of the invention as defined by the following claims. </p>
|
| 229 |
+
<boundary-data type="header">
|
| 230 |
+
<confidence value="8">8</confidence>
|
| 231 |
+
</boundary-data>
|
| 232 |
+
</description>
|
| 233 |
+
</us-patent-application>
|
| 234 |
+
|
applicant/11689651.xml
ADDED
|
@@ -0,0 +1,31 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11689651</doc-number>
|
| 8 |
+
<date>2010-09-07</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">PA-4102U; 67097-775PUS<confidence value="8">1</confidence>
|
| 14 |
+
</p>
|
| 15 |
+
<heading id="h-1">AMENDMENTS TO THE SPECIFICATION</heading>
|
| 16 |
+
<p id="p-2" num="2">Please amend paragraph [0024] as follows:</p>
|
| 17 |
+
<p id="p-3" num="3">[0024] The protective coating <part-num-ref name="protective coating">74</part-num-ref>
|
| 18 |
+
resists formation of ice, erosion, or both. Protecting against, and in some cases entirely preventing, ice formation and erosion provides the benefit of maintaining aerodynamically smooth surfaces over the nozzle section <part-num-ref name="nozzle section">56,</part-num-ref>
|
| 19 |
+
56' and/or nacelle <part-num-ref name="nozzle section 56, 56' and/or nacelle">28,</part-num-ref>
|
| 20 |
+
and preventing the effective flow area from artificially and undesirably changing due to ice formation or erosion. The protective coating <part-num-ref name="protective coating">74</part-num-ref>
|
| 21 |
+
may also prevent ice from accreting to a size that is large enough to hinder the movement of the nozzle section <part-num-ref name="nozzle section">56,</part-num-ref>
|
| 22 |
+
56'. Additionally, the example nozzle <part-num-ref name="example nozzle">40</part-num-ref>
|
| 23 |
+
may further include an anti-icing device <part-num-ref name="anti-icing device">78</part-num-ref>
|
| 24 |
+
that is operational to melt or break any ice that forms on the protective coating <part-num-ref name="protective coating">74.</part-num-ref>
|
| 25 |
+
</p>
|
| 26 |
+
<p id="p-4" num="4">
|
| 27 |
+
<confidence value="8">2</confidence>
|
| 28 |
+
</p>
|
| 29 |
+
</description>
|
| 30 |
+
</us-patent-application>
|
| 31 |
+
|
applicant/11714274.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="11714274.02-10-2015.I60XLPYGPXXIFW2.SPEC.XML" pat:id="I60XLPYGPXXIFW2"><pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001"><pat:ApplicationHeaderDetails><pat:ApplicationNumber>11714274</pat:ApplicationNumber></pat:ApplicationHeaderDetails><pat:PageTotalQuantity>1</pat:PageTotalQuantity><pat:ParagraphTotalQuantity>3</pat:ParagraphTotalQuantity></pat:DocumentHeaderDetails><pat:MailRoomDate>2015-02-10</pat:MailRoomDate><pat:Specification><?PageStart number='1'?><pat:P pat:pNumber="1" pat:id="p-1"><pat:BoundaryData><pat:HeaderText>Atty. <pat:OCRConfidenceData pat:levelNumber='5'>D</pat:OCRConfidenceData>kt. No. 098350-0106</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Application No. 11/714,274</pat:HeaderText></pat:BoundaryData>Amendments to the Title of the Invention: </pat:P><pat:P pat:pNumber="2" pat:id="p-2">Please replace the Title of the Invention with the following: </pat:P><pat:Heading pat:id="h-1">-- NANO-STRUCTURED ACYCLOVIR COMPOSITIONS AND METHODS OF</pat:Heading><pat:Heading pat:id="h-2">MAKING AND USING THE SAME--</pat:Heading><pat:P pat:pNumber="3" pat:id="p-3"><pat:BoundaryData><pat:HeaderText>-2-</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>4833-0006-5057 1</pat:HeaderText></pat:BoundaryData></pat:P></pat:Specification></pat:SpecificationDocument>
|
applicant/11718006.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>11718006</doc-number>
|
| 8 |
+
<date>2010-11-30</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">Serial No. <confidence value="5">1</confidence>
|
| 14 |
+
1/718,006 Attorney Docket No. 7000-489-<confidence value="48">IA</confidence>
|
| 15 |
+
In the S<confidence value="686">pec</confidence>
|
| 16 |
+
ification: </p>
|
| 17 |
+
<p id="p-2" num="2">Please replace paragraph 0046 with the following amended paragraph:</p>
|
| 18 |
+
<p id="p-3" num="3">[0046] Routing decisions may also be based on the type of content being requested, as well as the number of mobile terminals <part-num-ref name="number of mobile terminals">12</part-num-ref>
|
| 19 |
+
that have requested the selected content. The number of mobile terminals <part-num-ref name="number of mobile terminals">12</part-num-ref>
|
| 20 |
+
may be related to overall numbers or concentrations in particular areas. </p>
|
| 21 |
+
<p id="p-4" num="4">Accordingly, geographic distribution and concentrations may factor into the routing decision and may be considered related to relative locations of each of the mobile terminals <part-num-ref name="mobile terminals">12.</part-num-ref>
|
| 22 |
+
</p>
|
| 23 |
+
<p id="p-5" num="5">
|
| 24 |
+
<confidence value="8">2</confidence>
|
| 25 |
+
</p>
|
| 26 |
+
</description>
|
| 27 |
+
</us-patent-application>
|
| 28 |
+
|
applicant/11729702.xml
ADDED
|
@@ -0,0 +1,992 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11729702</doc-number>
|
| 8 |
+
<date>2007-03-29</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">K-C 64129991 <confidence value="8856">US01</confidence>
|
| 14 |
+
</p>
|
| 15 |
+
<heading id="h-1">ABSORBENT ARTICLES WITH EXTERNAL ACCESS TO INTERNAL</heading>
|
| 16 |
+
<heading id="h-2">CONDUCTORS</heading>
|
| 17 |
+
<heading id="h-3">BACKGROUND OF THE INVENTION</heading>
|
| 18 |
+
<p id="p-2" num="2">[001] Absorbent articles such as diapers, training pants, incontinence products, feminine hygiene products, swim undergarments, and the like conventionally <boundary-data type="line-number">5 </boundary-data>
|
| 19 |
+
include a liquid permeable body-side liner, a liquid impermeable outercover, and an absorbent core located between the outercover and the liner for taking in and retaining liquids (e.g., urine) exuded by the wearer. </p>
|
| 20 |
+
<p id="p-3" num="3">[002] Some absorbent arti<confidence value="6">c</confidence>
|
| 21 |
+
les further include various sensing circuits and signaling devices that produce a visual and/or an audible alarm when certain <boundary-data type="line-number">
|
| 22 |
+
<confidence value="66">10</confidence>
|
| 23 |
+
</boundary-data>
|
| 24 |
+
conditions are detected. Generally, the sensing circuits have been located within the absorbent articles and the signaling devices have been externally located on the absorbent article. </p>
|
| 25 |
+
<p id="p-4" num="4">[003] For proper operation, the signa<confidence value="8">l</confidence>
|
| 26 |
+
ing devices need to be electrically connected with the sensing circuits but typically one or more non-conductive layers <boundary-data type="line-number">
|
| 27 |
+
<confidence value="66">15</confidence>
|
| 28 |
+
</boundary-data>
|
| 29 |
+
are interposed therebetween. As such, various solutions have been proposed for reliably creating an electrical connection between the internal sensing circuit and the external signaling device. For example, it has been suggested that the non- conductive layer be slit, cut, or apertured to create openings to provide access to the sensing circuit lying below the non-conductive layer. However, these systems <boundary-data type="line-number">20 </boundary-data>
|
| 30 |
+
may be less desirable because precise registration control may be required to ensure that the openings are aligned with the conductive elements. This may complicate converting processes and increase cost and delay. Furthermore, these systems may be less desirable because the openings in the outercover and/or <confidence value="6">.</confidence>
|
| 31 |
+
</p>
|
| 32 |
+
<p id="p-5" num="5">liner may increase the possibility of body fluid escaping from the absorbent article.</p>
|
| 33 |
+
<p id="p-6" num="6">
|
| 34 |
+
<boundary-data type="line-number">
|
| 35 |
+
<confidence value="86">25</confidence>
|
| 36 |
+
</boundary-data>
|
| 37 |
+
[004] Other methods of creating an electrical connection have included signaling devices with conductive contacts adapted to pierce the non-conductive layers to contact the conductive sensing circuit located inside the absorbent articles. </p>
|
| 38 |
+
<p id="p-7" num="7">However, these systems may not result in reliable connections because the intervening layers of nonconductive materials may inhibit continuity between the <part-num-ref name="">30</part-num-ref>
|
| 39 |
+
signaling device and the conductive sensing circuit. Additionally, these systems <boundary-data type="header">
|
| 40 |
+
<confidence value="5">1</confidence>
|
| 41 |
+
</boundary-data>
|
| 42 |
+
<page-break num="2"/>
|
| 43 |
+
<confidence value="12">n-</confidence>
|
| 44 |
+
<confidence value="171">1-1</confidence>
|
| 45 |
+
<confidence value="6112221">OOI4UU'</confidence>
|
| 46 |
+
UOU<confidence value="12">'1</confidence>
|
| 47 |
+
also may increase the possibility of body fluid escaping from the absorbent article particularly if several penetration attempts are made before a proper connection is formed. Finally, these systems may require the signaling device to be in contact with the body of the wearer which may be less comfortable than a signaling device <boundary-data type="line-number">
|
| 48 |
+
<confidence value="5">5</confidence>
|
| 49 |
+
</boundary-data>
|
| 50 |
+
located only on a garment side of the absorbent article. </p>
|
| 51 |
+
<p id="p-8" num="8">[005] Therefore, there remains a need for an absorbent article that is adapted to provide a reliable connection between an internally positioned sensing circuit and an externally mounted signaling device while minimizing the shortcomings of the prior art.</p>
|
| 52 |
+
<p id="p-9" num="9">
|
| 53 |
+
<boundary-data type="line-number">
|
| 54 |
+
<confidence value="88">10</confidence>
|
| 55 |
+
</boundary-data>
|
| 56 |
+
</p>
|
| 57 |
+
<heading id="h-4">SUMMARY OF THE INVENTION</heading>
|
| 58 |
+
<p id="p-10" num="10">[006] In one aspect, the present invention provides an absorbent article having a liner and an outercover in facing relation with at least one conductive element located between the liner and the outercover. At least a portion of the conductive <boundary-data type="line-number">
|
| 59 |
+
<confidence value="66">15</confidence>
|
| 60 |
+
</boundary-data>
|
| 61 |
+
element is exposed through at least one of the liner and the outercover to define at least one external contact point. The at least one external contact point defines a perimeter and at least one of the liner and the outercover is sealed about the perimeter. In some embodiments, the absorbent article may include at least one external contact point that extends at least partially through the outercover. In <boundary-data type="line-number">20 </boundary-data>
|
| 62 |
+
some embodiments, the conductive elements are intact proximate the external contact points. In some embodiments, the conductive element is a laminate that includes a conductive layer and a masking layer. The conductive element may be oriented towards the outercover and the masking layer may be oriented towards the liner. </p>
|
| 63 |
+
<p id="p-11" num="11">
|
| 64 |
+
<boundary-data type="line-number">
|
| 65 |
+
<confidence value="86">25</confidence>
|
| 66 |
+
</boundary-data>
|
| 67 |
+
[007] In some embodiments, the absorbent article may have a length and first and second conductive elements extending the length of the absorbent article. In some embodiments, the first conductive element and the second conductive element may have a plurality of portions extending at least partially through the outercover to define a plurality of external contact points. In some embodiments, <boundary-data type="line-number">30 </boundary-data>
|
| 68 |
+
the outercover and the liner may be joined together at bond points that do not include the conductive element. </p>
|
| 69 |
+
<boundary-data type="header">
|
| 70 |
+
<confidence value="8">2</confidence>
|
| 71 |
+
</boundary-data>
|
| 72 |
+
<p id="p-12" num="12">
|
| 73 |
+
<page-break num="3"/>
|
| 74 |
+
[008] In another aspect, the present invention provides a kit. The kit may include any of the absorbent articles described herein and a signaling device. In some embodiments, the absorbent article may include a plurality of external contact points formed in the shape of a first indicia and the signaling device may include a <boundary-data type="line-number">
|
| 75 |
+
<confidence value="5">5</confidence>
|
| 76 |
+
</boundary-data>
|
| 77 |
+
second indicia wherein the first and second indicia facilitate the alignment of the signaling device, relative to the absorbent article. </p>
|
| 78 |
+
<p id="p-13" num="13">[009] In some embodiments, an absorbent article may have a length and include a liner and an outercover in facing relation. The absorbent article may also include a first conductive element and a second conductive element located between the <boundary-data type="line-number">
|
| 79 |
+
<confidence value="66">io</confidence>
|
| 80 |
+
</boundary-data>
|
| 81 |
+
liner and the outercover and extending the length of the absorbent article. The absorbent article may also include a plurality of portions of the first conductive element and the second conductive element that are at least partially exposed through the outercover to define a plurality of external contact points. Each external contact point defines a perimeter and the outercover may be sealed about <boundary-data type="line-number">15 </boundary-data>
|
| 82 |
+
each perimeter. </p>
|
| 83 |
+
<p id="p-14" num="14">[010] In some embodiments, the liner and the outercover may be joined together at bond points in areas that do not include the first or the second conductive elements. In some embodiments, the absorbent articles may include a plurality of external contact points wherein the plurality of external contact points are adapted <boundary-data type="line-number">20 </boundary-data>
|
| 84 |
+
to provide a first indicia for aligning a signaling device with the absorbent article to ensure electrical connectivity. In some embodiments, the absorbent article may be provided in a kit with a signaling device having a second indicia that is adapted to align with the first indicia to ensure proper electrical connectivity. </p>
|
| 85 |
+
<p id="p-15" num="15">[011] In another aspect, the present invention provides a method of exposing <boundary-data type="line-number">25 </boundary-data>
|
| 86 |
+
portions of internally positioned conductive elements to an external surface of an absorbent article. The method includes providing an outercover and liner in facing relation with a conductive element located therebetween; at least partially exposing a portion of the conductive element through the outercover to define at least one external contact point on an outer article surface; and sealing the <boundary-data type="line-number">30 </boundary-data>
|
| 87 |
+
outercover about a perimeter of the at least one external contact point by at least partially melting portions of the outercover. </p>
|
| 88 |
+
<p id="p-16" num="16">[012] In some embodiments, the method includes providing the outercover, the liner, and the conductive element as a part of an interconnected web of absorbent <boundary-data type="header">
|
| 89 |
+
<confidence value="8">3</confidence>
|
| 90 |
+
</boundary-data>
|
| 91 |
+
<page-break num="4"/>
|
| 92 |
+
articles. In some embodiments, the method includes exposing a portion of the conductive element by using pressure bonding, ultrasonic bonding, or thermal bonding. In some embodiments, the method includes exposing a portion of the conductive element at least partially through the outercover. </p>
|
| 93 |
+
<p id="p-17" num="17">
|
| 94 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 95 |
+
[013<confidence value="5">]</confidence>
|
| 96 |
+
In some embodiments, the steps of exposing a portion of the conductive element and sealing the outercover may occur in the same operation. In some embodiments, the conductive element may be a laminate having a conductive layer and a masking layer and the method may include orienting the conductive layer towards the outercover and orienting the masking layer towards the liner. In <boundary-data type="line-number">
|
| 97 |
+
<confidence value="55">1o</confidence>
|
| 98 |
+
</boundary-data>
|
| 99 |
+
some embodiments, the method may include bonding the outercover and the liner at bond points that do not include the conductive element in the same operation as the exposing step. </p>
|
| 100 |
+
<heading id="h-5">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 101 |
+
<p id="p-18" num="18">
|
| 102 |
+
<boundary-data type="line-number">
|
| 103 |
+
<confidence value="66">15</confidence>
|
| 104 |
+
</boundary-data>
|
| 105 |
+
A full and enabling disclosure of the present invention, including the best mode thereof to one skilled in the art, is set forth more particularly in the remainder of the specification, including reference to the accompanying figures, in which: </p>
|
| 106 |
+
<p id="p-19" num="19">Figure 1 is a rear perspective view of one embodiment of an absorbent article made in accordance with the present invention;</p>
|
| 107 |
+
<p id="p-20" num="20">
|
| 108 |
+
<boundary-data type="line-number">
|
| 109 |
+
<confidence value="86">20</confidence>
|
| 110 |
+
</boundary-data>
|
| 111 |
+
Figure 2 is a front perspective view of another embodiment of an absorbent article made in accordance with the present invention; </p>
|
| 112 |
+
<p id="p-21" num="21">Figure 3 is a plan view of another embodiment of an absorbent article made in accordance with the present invention wherein the article is illustrated in an unfastened, unfolded and laid flat condition showing the surface of the article that <boundary-data type="line-number">
|
| 113 |
+
<confidence value="86">25</confidence>
|
| 114 |
+
</boundary-data>
|
| 115 |
+
faces away from the wearer; </p>
|
| 116 |
+
<p id="p-22" num="22">Figure 4 is a plan view of the absorbent article of Figure 1 showing the surface of the absorbent article that faces the wearer when worn and with portions cut away to show underlying features;</p>
|
| 117 |
+
<p id="p-23" num="23">Figure 5 is a magnified cross-sectional view of the absorbent article of Figure 3 <boundary-data type="line-number">30 </boundary-data>
|
| 118 |
+
taken along the line 5-5; </p>
|
| 119 |
+
<p id="p-24" num="24">Figure 6 is a perspective view of the embodiment shown in Figure 2 further including an exemplary signaling device;</p>
|
| 120 |
+
<p id="p-25" num="25">Figure 7 representatively illustrates an exemplary kit of the present invention;</p>
|
| 121 |
+
<boundary-data type="header">
|
| 122 |
+
<confidence value="8">4</confidence>
|
| 123 |
+
</boundary-data>
|
| 124 |
+
<p id="p-26" num="26">
|
| 125 |
+
<page-break num="5"/>
|
| 126 |
+
Figure 8 is an exemplary cross-sectional view of one embodiment of the present invention; </p>
|
| 127 |
+
<p id="p-27" num="27">Figure 9 is an optical image of a modified diaper illustrating exemplary external contact points.</p>
|
| 128 |
+
<p id="p-28" num="28">
|
| 129 |
+
<boundary-data type="line-number">
|
| 130 |
+
<confidence value="8">5</confidence>
|
| 131 |
+
</boundary-data>
|
| 132 |
+
</p>
|
| 133 |
+
<heading id="h-6">DETAILED DESCRIPTION OF THE INVENTION</heading>
|
| 134 |
+
<p id="p-29" num="29">[014<confidence value="5">]</confidence>
|
| 135 |
+
It is to be understood by one of ordinary skill in the art that the present discussion is a description of exemplary embodiments only, and is not intended as limiting the broader aspects of the present invention. </p>
|
| 136 |
+
<p id="p-30" num="30">
|
| 137 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 138 |
+
[015] In one aspect, the present invention provides absorbent articles adapted to be joined with a signaling device that may be configured to indicate the presence of a body fluid in the absorbent article or other changes in the condition of the product or wearer. The absorbent article may be, for instance, a diaper, a training pant, an incontinence product, a feminine hygiene product, a medical garment, a <boundary-data type="line-number">
|
| 139 |
+
<confidence value="66">15</confidence>
|
| 140 |
+
</boundary-data>
|
| 141 |
+
bandage, or the like. Absorbent articles made according to the present disclosure may include an open circuit that becomes closed when a conductive fluid, such as a body fluid, is sensed in between a pair of conductive elements. Generally, the absorbent articles containing the open circuit are disposable meaning that they are designed to be discarded after a limited use rather than being laundered or <boundary-data type="line-number">
|
| 142 |
+
<confidence value="86">20</confidence>
|
| 143 |
+
</boundary-data>
|
| 144 |
+
otherwise restored for reuse. </p>
|
| 145 |
+
<p id="p-31" num="31">[016] The open circuit contained within the absorbent articles of the present disclosure is configured to be joined with a signaling device. The signaling device can provide power to the open circuit while also including some type of audible and/or visible signal that indicates to the user the presence of a body fluid.</p>
|
| 146 |
+
<p id="p-32" num="32">
|
| 147 |
+
<boundary-data type="line-number">
|
| 148 |
+
<confidence value="86">25</confidence>
|
| 149 |
+
</boundary-data>
|
| 150 |
+
Although the absorbent article itself is disposable, the signaling device may be reusable from article to article. In this regard, the present disclosure is particularly directed to absorbent articles adapted to provide convenient and reliable connection between the open circuit positioned inside the absorbent article and the signaling device located outside the absorbent article. </p>
|
| 151 |
+
<p id="p-33" num="33">
|
| 152 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 153 |
+
[017] As described above, the open circuit in combination with the signaling device may be configured to indicate the presence of a body fluid contained within the absorbent article. The particular targeted body fluid may vary depending upon <boundary-data type="header">
|
| 154 |
+
<confidence value="8">5</confidence>
|
| 155 |
+
</boundary-data>
|
| 156 |
+
<page-break num="6"/>
|
| 157 |
+
the particular type of absorbent article and the desired application. For instance, in one embodiment, the absorbent article comprises a diaper, a training pant, or the like and the signaling device is configured to indicate the presence of urine and/or any component of urine. Additionally, the signaling device may be <boundary-data type="line-number">s </boundary-data>
|
| 158 |
+
configured to indicate the presence of a metabolite that may indicate the presence of a diaper rash. For adult incontinence products and feminine hygiene products, on the other hand, the signaling device may be configured to indicate the presence of a yeast or of a particular constituent in urine, such as a polysaccharide. </p>
|
| 159 |
+
<p id="p-34" num="34">
|
| 160 |
+
<boundary-data type="line-number">
|
| 161 |
+
<confidence value="65">10</confidence>
|
| 162 |
+
</boundary-data>
|
| 163 |
+
[018] Referring to Figs. 1-4, for exemplary purposes, an absorbent article <part-num-ref name="absorbent article">20</part-num-ref>
|
| 164 |
+
that may be made in accordance with the present invention is shown. The absorbent article <part-num-ref name="absorbent article">20</part-num-ref>
|
| 165 |
+
may or may not be disposable. It is understood that the present invention is suitable for use with various other absorbent articles intended for personal wear, including but not limited to diapers, training pants, swim pants, <boundary-data type="line-number">
|
| 166 |
+
<confidence value="66">15</confidence>
|
| 167 |
+
</boundary-data>
|
| 168 |
+
feminine hygiene products, incontinence products, medical garments, surgical pads and bandages, other personal care or health care garments, and the like without departing from the scope of the present invention. </p>
|
| 169 |
+
<p id="p-35" num="35">[019] A diaper <part-num-ref name="diaper">20</part-num-ref>
|
| 170 |
+
is representatively illustrated in Fig. <confidence value="5">1</confidence>
|
| 171 |
+
in a partially fastened condition. A diaper <part-num-ref name="diaper">20</part-num-ref>
|
| 172 |
+
is also represented in Figs. 3 and <part-num-ref name="and">4</part-num-ref>
|
| 173 |
+
in an opened and <boundary-data type="line-number">20 </boundary-data>
|
| 174 |
+
unfolded state. Fig. 3 is a plan view illustrating the exterior side of a diaper <part-num-ref name="diaper">20,</part-num-ref>
|
| 175 |
+
while Fig. 4 illustrates the interior side of a diaper <part-num-ref name="diaper">20.</part-num-ref>
|
| 176 |
+
As shown in Figs. 3 and <part-num-ref name="and">4,</part-num-ref>
|
| 177 |
+
the diaper <part-num-ref name="diaper">20</part-num-ref>
|
| 178 |
+
defines a longitudinal direction <part-num-ref name="longitudinal direction">48</part-num-ref>
|
| 179 |
+
that extends from the front of the article when worn to the back of the article. Opposite to the longitudinal direction <part-num-ref name="longitudinal direction">48</part-num-ref>
|
| 180 |
+
is a lateral direction <part-num-ref name="lateral direction">49.</part-num-ref>
|
| 181 |
+
</p>
|
| 182 |
+
<p id="p-36" num="36">
|
| 183 |
+
<boundary-data type="line-number">
|
| 184 |
+
<confidence value="86">25</confidence>
|
| 185 |
+
</boundary-data>
|
| 186 |
+
[020] The diaper <part-num-ref name="diaper">20</part-num-ref>
|
| 187 |
+
defines a pair of longitudinal end regions, otherwise referred to herein as a front region <part-num-ref name="front region">22</part-num-ref>
|
| 188 |
+
and a back region <part-num-ref name="back region">24,</part-num-ref>
|
| 189 |
+
and a center region, otherwise referred to herein as a crotch region <part-num-ref name="crotch region">26,</part-num-ref>
|
| 190 |
+
extending longitudinally between and interconnecting the front and back regions <part-num-ref name="front and back regions">22,</part-num-ref>
|
| 191 |
+
<part-num-ref name="front and back regions 22,">24.</part-num-ref>
|
| 192 |
+
The diaper <part-num-ref name="diaper">20</part-num-ref>
|
| 193 |
+
also defines an inner article surface <part-num-ref name="inner article surface">28</part-num-ref>
|
| 194 |
+
adapted in use, i.e., positioned relative to the other <boundary-data type="line-number">30 </boundary-data>
|
| 195 |
+
components of the article <part-num-ref name="article">20,</part-num-ref>
|
| 196 |
+
to be disposed toward the wearer, and an outer article surface <part-num-ref name="outer article surface">30</part-num-ref>
|
| 197 |
+
opposite the inner surface. The front and back regions <part-num-ref name="front and back regions">22</part-num-ref>
|
| 198 |
+
and <part-num-ref name="and">24</part-num-ref>
|
| 199 |
+
are those portions of the diaper <part-num-ref name="diaper">20,</part-num-ref>
|
| 200 |
+
which when worn, wholly or partially cover <boundary-data type="header">
|
| 201 |
+
<confidence value="8">6</confidence>
|
| 202 |
+
</boundary-data>
|
| 203 |
+
<page-break num="7"/>
|
| 204 |
+
or encircle the waist or mid-lower torso of the wearer. The crotch region <part-num-ref name="crotch region">26</part-num-ref>
|
| 205 |
+
generally is that portion of the diaper <part-num-ref name="diaper">20</part-num-ref>
|
| 206 |
+
which, when worn, is positioned between the legs of the wearer and covers the lower torso and crotch of the wearer. The absorbent article <part-num-ref name="absorbent article">20</part-num-ref>
|
| 207 |
+
has a pair of laterally opposite side edges <part-num-ref name="pair of laterally opposite side edges">36</part-num-ref>
|
| 208 |
+
and a pair of <boundary-data type="line-number">5 </boundary-data>
|
| 209 |
+
longitudinally opposite waist edges, respectively designated front waist edge <part-num-ref name="pair of longitudinally opposite waist edges, respectively designated front waist edge">38</part-num-ref>
|
| 210 |
+
and back waist edge <part-num-ref name="and back waist edge">39.</part-num-ref>
|
| 211 |
+
</p>
|
| 212 |
+
<p id="p-37" num="37">[021] The illustrated diaper <part-num-ref name="illustrated diaper">20</part-num-ref>
|
| 213 |
+
includes a chassis <part-num-ref name="chassis">32</part-num-ref>
|
| 214 |
+
that, in various embodiments, encompasses the front region <part-num-ref name="front region">22,</part-num-ref>
|
| 215 |
+
the back region <part-num-ref name="back region">24,</part-num-ref>
|
| 216 |
+
and the crotch region <part-num-ref name="crotch region">26.</part-num-ref>
|
| 217 |
+
Referring to Figs. 1- <part-num-ref name="crotch region 26. Referring to Figs. 1-">4,</part-num-ref>
|
| 218 |
+
the chassis <part-num-ref name="chassis">32</part-num-ref>
|
| 219 |
+
includes an outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 220 |
+
<boundary-data type="line-number">
|
| 221 |
+
<confidence value="85">10</confidence>
|
| 222 |
+
</boundary-data>
|
| 223 |
+
and a bodyside liner <part-num-ref name="bodyside liner">42</part-num-ref>
|
| 224 |
+
that may be joined to the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 225 |
+
in a superimposed relation therewith by adhesives, ultrasonic bonds, thermal bonds or other conventional techniques. Referring to Fig. 4, the liner <part-num-ref name="liner">42</part-num-ref>
|
| 226 |
+
may suitably be joined to the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 227 |
+
along the perimeter of the chassis <part-num-ref name="chassis">32</part-num-ref>
|
| 228 |
+
to form a front waist seam <part-num-ref name="front waist seam">62</part-num-ref>
|
| 229 |
+
and a back waist seam <part-num-ref name="back waist seam">64.</part-num-ref>
|
| 230 |
+
As shown in Fig. 4, the liner <part-num-ref name="liner">42</part-num-ref>
|
| 231 |
+
may suitably be <boundary-data type="line-number">
|
| 232 |
+
<confidence value="55">is</confidence>
|
| 233 |
+
</boundary-data>
|
| 234 |
+
joined to the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 235 |
+
to form a pair of side seams <part-num-ref name="pair of side seams">61</part-num-ref>
|
| 236 |
+
in the front region <part-num-ref name="front region">22</part-num-ref>
|
| 237 |
+
and the back region <part-num-ref name="back region">24.</part-num-ref>
|
| 238 |
+
The liner <part-num-ref name="liner">42</part-num-ref>
|
| 239 |
+
can be generally adapted, i.e., positioned relative to the other components of the article <part-num-ref name="article">20,</part-num-ref>
|
| 240 |
+
to be disposed toward the wearer's skin during wear of the absorbent article. The chassis <part-num-ref name="chassis">32</part-num-ref>
|
| 241 |
+
may further include an absorbent structure <part-num-ref name="absorbent structure">44</part-num-ref>
|
| 242 |
+
particularly shown in Fig. 4 disposed between <boundary-data type="line-number">
|
| 243 |
+
<confidence value="86">20</confidence>
|
| 244 |
+
</boundary-data>
|
| 245 |
+
the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 246 |
+
and the bodyside liner <part-num-ref name="bodyside liner">42</part-num-ref>
|
| 247 |
+
for absorbing liquid body exudates exuded by the wearer, and may further include a pair of containment flaps <part-num-ref name="pair of containment flaps">46</part-num-ref>
|
| 248 |
+
secured to the bodyside liner <part-num-ref name="bodyside liner">42</part-num-ref>
|
| 249 |
+
for inhibiting the lateral flow of body exudates. </p>
|
| 250 |
+
<p id="p-38" num="38">[022] The outercover layer <part-num-ref name="outercover layer">40</part-num-ref>
|
| 251 |
+
may be constructed of any operative material, and may or may not be configured to be operatively liquid-permeable. In a <boundary-data type="line-number">25 </boundary-data>
|
| 252 |
+
particular configuration, the outercover layer <part-num-ref name="outercover layer">40</part-num-ref>
|
| 253 |
+
may be configured to provide an operatively liquid-impermeable layer. The outercover layer may, for example, include a polymeric film, a woven fabric, a nonwoven fabric or the like, as well as combinations or composites thereof. For example, the outercover layer <part-num-ref name="outercover layer">40</part-num-ref>
|
| 254 |
+
may include a polymer film laminated to a woven or nonwoven fabric. In a particular <boundary-data type="line-number">30 </boundary-data>
|
| 255 |
+
feature, the polymer film can be composed of polyethylene, polypropylene, polyester or the like, as well as combinations thereof. Additionally, the polymer film may be micro-embossed. Desirably, the outercover layer <part-num-ref name="outercover layer">40</part-num-ref>
|
| 256 |
+
can operatively <boundary-data type="header">
|
| 257 |
+
<confidence value="8">7</confidence>
|
| 258 |
+
</boundary-data>
|
| 259 |
+
<page-break num="8"/>
|
| 260 |
+
<confidence value="27">IK</confidence>
|
| 261 |
+
041Z<confidence value="12122112">UUVlUUUl</confidence>
|
| 262 |
+
permit a sufficient passage of air and moisture vapor out of the article while blocking the passage of bodily liquids. </p>
|
| 263 |
+
<p id="p-39" num="39">[023] The liner <part-num-ref name="liner">42</part-num-ref>
|
| 264 |
+
may be constructed of any operative material, and may be a composite material. For example, the liner <part-num-ref name="liner">42</part-num-ref>
|
| 265 |
+
can include a woven fabric, a <boundary-data type="line-number">
|
| 266 |
+
<confidence value="4">s</confidence>
|
| 267 |
+
</boundary-data>
|
| 268 |
+
nonwoven fabric, a polymer film, or the like, as well as combinations thereof. </p>
|
| 269 |
+
<p id="p-40" num="40">Examples of a nonwoven fabric include, spunbond fabric, <confidence value="222222222">meltblown</confidence>
|
| 270 |
+
fabric, coform fabric, a carded web, a bonded-carded-web, or the like as well as combinations thereof. For example, the liner <part-num-ref name="liner">42</part-num-ref>
|
| 271 |
+
can include a woven fabric, a nonwoven fabric, a polymeric film that has been configured to be operatively liquid-permeable, or <boundary-data type="line-number">
|
| 272 |
+
<confidence value="86">10</confidence>
|
| 273 |
+
</boundary-data>
|
| 274 |
+
the like, as well as combinations thereof. Other examples of suitable materials for constructing the liner <part-num-ref name="liner">42</part-num-ref>
|
| 275 |
+
can include rayon, bonded-carded webs of polyester, polypropylene, polyethylene, nylon, or other heat-bondable fibers, polyolefins, such as copolymers of polypropylene and polyethylene, linear low-density polyethylene, aliphatic esters such as polylactic acid, finely perforated film webs, <boundary-data type="line-number">
|
| 276 |
+
<confidence value="66">15</confidence>
|
| 277 |
+
</boundary-data>
|
| 278 |
+
net materials, and the like, as well as combinations thereof. </p>
|
| 279 |
+
<p id="p-41" num="41">[024] The elasticized containment flaps <part-num-ref name="elasticized containment flaps">46</part-num-ref>
|
| 280 |
+
as shown in Fig. 4 define a partially unattached edge which assumes an upright configuration in at least the crotch region <part-num-ref name="crotch region">26</part-num-ref>
|
| 281 |
+
of the diaper <part-num-ref name="diaper">20</part-num-ref>
|
| 282 |
+
to form a seal against the wearer's body. The containment flaps <part-num-ref name="containment flaps">46</part-num-ref>
|
| 283 |
+
can extend longitudinally along the entire length of the <boundary-data type="line-number">20 </boundary-data>
|
| 284 |
+
chassis <part-num-ref name="chassis">32</part-num-ref>
|
| 285 |
+
or may extend only partially along the length of the chassis. </p>
|
| 286 |
+
<p id="p-42" num="42">[025] To further enhance containment and/or absorption of body exudates, the diaper <part-num-ref name="diaper">20</part-num-ref>
|
| 287 |
+
may also suitably include leg elastic members <part-num-ref name="may also suitably include leg elastic members">58</part-num-ref>
|
| 288 |
+
(Fig. 4), as are known to those skilled in the art. The leg elastic members <part-num-ref name="leg elastic members">58</part-num-ref>
|
| 289 |
+
can be operatively joined to the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 290 |
+
and/or the bodyside liner <part-num-ref name="bodyside liner">42</part-num-ref>
|
| 291 |
+
and positioned in the crotch region <boundary-data type="line-number">
|
| 292 |
+
<confidence value="86">25</confidence>
|
| 293 |
+
</boundary-data>
|
| 294 |
+
<part-num-ref name="crotch region">26</part-num-ref>
|
| 295 |
+
of the absorbent article <part-num-ref name="absorbent article">20.</part-num-ref>
|
| 296 |
+
</p>
|
| 297 |
+
<p id="p-43" num="43">[026] In some embodiments, the absorbent article <part-num-ref name="absorbent article">20</part-num-ref>
|
| 298 |
+
may further include a surge management layer (not shown) which may be optionally located adjacent the absorbent structure <part-num-ref name="absorbent structure">44</part-num-ref>
|
| 299 |
+
and attached to various components in the article <part-num-ref name="article">20</part-num-ref>
|
| 300 |
+
such as the absorbent structure <part-num-ref name="absorbent structure">44</part-num-ref>
|
| 301 |
+
or the bodyside liner <part-num-ref name="bodyside liner">42</part-num-ref>
|
| 302 |
+
by methods known in the <boundary-data type="line-number">
|
| 303 |
+
<confidence value="86">30</confidence>
|
| 304 |
+
</boundary-data>
|
| 305 |
+
art, such as by using an adhesive. </p>
|
| 306 |
+
<p id="p-44" num="44">[027] As shown in Figs. 1- 4, absorbent articles 20 may further include a pair of opposing elastic side panels <part-num-ref name="pair of opposing elastic side panels">34</part-num-ref>
|
| 307 |
+
that are attached to the back region of the chassis <boundary-data type="header">
|
| 308 |
+
<confidence value="8">8</confidence>
|
| 309 |
+
</boundary-data>
|
| 310 |
+
<page-break num="9"/>
|
| 311 |
+
K-C <part-num-ref name="chassis K-C">64129991</part-num-ref>
|
| 312 |
+
<confidence value="8856">US01</confidence>
|
| 313 |
+
<part-num-ref name="US01">32.</part-num-ref>
|
| 314 |
+
As shown particularly in Figs. <confidence value="5">1</confidence>
|
| 315 |
+
and <part-num-ref name="and">2,</part-num-ref>
|
| 316 |
+
the side panels <part-num-ref name="side panels">34</part-num-ref>
|
| 317 |
+
may be stretched around the waist and/or hips of a wearer in order to secure the garment in place. </p>
|
| 318 |
+
<p id="p-45" num="45">As shown in Figs. 3 and <part-num-ref name="and">4,</part-num-ref>
|
| 319 |
+
the elastic side panels are attached to the chassis <part-num-ref name="chassis">32</part-num-ref>
|
| 320 |
+
along a pair of opposing longitudinal edges <part-num-ref name="pair of opposing longitudinal edges">37.</part-num-ref>
|
| 321 |
+
The side panels <part-num-ref name="side panels">34</part-num-ref>
|
| 322 |
+
may be <boundary-data type="line-number">5 </boundary-data>
|
| 323 |
+
attached or bonded to the chassis <part-num-ref name="chassis">32</part-num-ref>
|
| 324 |
+
using any suitable bonding technique. For instance, the side panels <part-num-ref name="side panels">34</part-num-ref>
|
| 325 |
+
may be joined to the chassis <part-num-ref name="chassis">32</part-num-ref>
|
| 326 |
+
by adhesives, ultrasonic bonds, thermal bonds, or other conventional techniques. </p>
|
| 327 |
+
<p id="p-46" num="46">[028<confidence value="5">]</confidence>
|
| 328 |
+
In an alternative embodiment, the elastic side panels may also be integrally formed with the chassis <part-num-ref name="chassis">32.</part-num-ref>
|
| 329 |
+
For instance, the side panels <part-num-ref name="side panels">34</part-num-ref>
|
| 330 |
+
may comprise an <boundary-data type="line-number">10 </boundary-data>
|
| 331 |
+
extension of the bodyside liner <part-num-ref name="bodyside liner">42,</part-num-ref>
|
| 332 |
+
the outercover <part-num-ref name="outercover">40,</part-num-ref>
|
| 333 |
+
or both the bodyside liner <part-num-ref name="bodyside liner">42</part-num-ref>
|
| 334 |
+
and the outercover <part-num-ref name="outercover">40.</part-num-ref>
|
| 335 |
+
</p>
|
| 336 |
+
<p id="p-47" num="47">[029] In the embodiments shown in the figures, the side panels <part-num-ref name="side panels">34</part-num-ref>
|
| 337 |
+
are connected to the back region of the absorbent article <part-num-ref name="absorbent article">20</part-num-ref>
|
| 338 |
+
and extend over the front region of the article when securing the article in place on a user. It should be understood, <boundary-data type="line-number">15 </boundary-data>
|
| 339 |
+
however, that the side panels <part-num-ref name="side panels">34</part-num-ref>
|
| 340 |
+
may alternatively be connected to the front region of the article <part-num-ref name="article">20</part-num-ref>
|
| 341 |
+
and extend over the back region when the article is donned. </p>
|
| 342 |
+
<p id="p-48" num="48">[030<confidence value="5">]</confidence>
|
| 343 |
+
With the absorbent article <part-num-ref name="absorbent article">20</part-num-ref>
|
| 344 |
+
in the fastened position as partially illustrated in Fig. <confidence value="5">1</confidence>
|
| 345 |
+
, the elastic side panels <part-num-ref name="elastic side panels">34</part-num-ref>
|
| 346 |
+
may be connected by a fastening system <part-num-ref name="fastening system">80</part-num-ref>
|
| 347 |
+
to define a 3-dimensional diaper configuration having a waist opening <part-num-ref name="waist opening">50</part-num-ref>
|
| 348 |
+
and a pair <boundary-data type="line-number">20 </boundary-data>
|
| 349 |
+
of leg openings <part-num-ref name="pair of leg openings">52.</part-num-ref>
|
| 350 |
+
The waist opening <part-num-ref name="waist opening">50</part-num-ref>
|
| 351 |
+
of the article <part-num-ref name="article">20</part-num-ref>
|
| 352 |
+
is defined by the waist edges <part-num-ref name="waist edges">38</part-num-ref>
|
| 353 |
+
and <part-num-ref name="and">39</part-num-ref>
|
| 354 |
+
which encircle the waist of the wearer. </p>
|
| 355 |
+
<p id="p-49" num="49">[031] In the embodiments shown in the figures, the side panels are releasably attachable to the front region <part-num-ref name="front region">22</part-num-ref>
|
| 356 |
+
of the article <part-num-ref name="article">20</part-num-ref>
|
| 357 |
+
by the fastening system. It should be understood, however, that in other embodiments the side panels may <boundary-data type="line-number">25 </boundary-data>
|
| 358 |
+
be permanently joined to the chassis <part-num-ref name="chassis">32</part-num-ref>
|
| 359 |
+
at each end. The side panels may be permanently bonded together, for instance, when forming a training pant, absorbent swimwear, and the like. </p>
|
| 360 |
+
<p id="p-50" num="50">[032] The fastening system <part-num-ref name="fastening system">80</part-num-ref>
|
| 361 |
+
may include laterally opposite first fastening components <part-num-ref name="may include laterally opposite first fastening components">82</part-num-ref>
|
| 362 |
+
adapted for refastenable engagement to corresponding second <boundary-data type="line-number">30 </boundary-data>
|
| 363 |
+
fastening components <part-num-ref name="adapted for refastenable engagement to corresponding second fastening components">84.</part-num-ref>
|
| 364 |
+
In the embodiment shown in Fig. 2, the first fastening component <part-num-ref name="first fastening component">82</part-num-ref>
|
| 365 |
+
is located on the elastic side panels <part-num-ref name="elastic side panels">34,</part-num-ref>
|
| 366 |
+
while the second fastening <boundary-data type="header">
|
| 367 |
+
<confidence value="8">9</confidence>
|
| 368 |
+
</boundary-data>
|
| 369 |
+
<page-break num="10"/>
|
| 370 |
+
<confidence value="1111">ftWk</confidence>
|
| 371 |
+
04<confidence value="21221161662">'I4Uy1UJUI'</confidence>
|
| 372 |
+
component <part-num-ref name="second fastening ftWk 04'I4Uy1UJUI' component">84</part-num-ref>
|
| 373 |
+
is located on the front region <part-num-ref name="front region">22</part-num-ref>
|
| 374 |
+
of the chassis <part-num-ref name="chassis">32.</part-num-ref>
|
| 375 |
+
In one aspect, a front or outer surface of each of the fastening components <part-num-ref name="fastening components">82,</part-num-ref>
|
| 376 |
+
<part-num-ref name="fastening components 82,">84</part-num-ref>
|
| 377 |
+
includes a plurality of engaging elements. The engaging elements of the first fastening components <part-num-ref name="first fastening components">82</part-num-ref>
|
| 378 |
+
are adapted to repeatedly engage and disengage corresponding <boundary-data type="line-number">
|
| 379 |
+
<confidence value="5">5</confidence>
|
| 380 |
+
</boundary-data>
|
| 381 |
+
engaging elements of the second fastening components <part-num-ref name="second fastening components">84</part-num-ref>
|
| 382 |
+
to releasably secure the article <part-num-ref name="article">20</part-num-ref>
|
| 383 |
+
in its three-dimensional configuration. </p>
|
| 384 |
+
<p id="p-51" num="51">[033] The fastening components <part-num-ref name="fastening components">82,</part-num-ref>
|
| 385 |
+
<part-num-ref name="fastening components 82,">84</part-num-ref>
|
| 386 |
+
may be any refastenable fasteners suitable for absorbent articles, such as adhesive fasteners, cohesive fasteners, mechanical fasteners, or the like. In particular aspects the fastening components <boundary-data type="line-number">
|
| 387 |
+
<confidence value="86">10</confidence>
|
| 388 |
+
</boundary-data>
|
| 389 |
+
include mechanical fastening elements for improved performance. Suitable mechanical fastening elements can be provided by interlocking geometric shaped materials, such as hooks, loops, bulbs, mushrooms, arrowheads, balls on stems, male and female mating components, buckles, snaps, and the like, and combinations thereof. </p>
|
| 390 |
+
<p id="p-52" num="52">
|
| 391 |
+
<boundary-data type="line-number">
|
| 392 |
+
<confidence value="56">is</confidence>
|
| 393 |
+
</boundary-data>
|
| 394 |
+
[034] In the embodiments illustrated in Figs. 1, <part-num-ref name="embodiments illustrated in Figs. 1,">3,</part-num-ref>
|
| 395 |
+
and <part-num-ref name="embodiments illustrated in Figs. 1, 3, and">4,</part-num-ref>
|
| 396 |
+
the first fastening components <part-num-ref name="first fastening components">82</part-num-ref>
|
| 397 |
+
include hook fasteners and the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 398 |
+
serves as the second fastening component <part-num-ref name="second fastening component">84.</part-num-ref>
|
| 399 |
+
In the illustrated aspect of Fig. 2, the first fastening components <part-num-ref name="first fastening components">82</part-num-ref>
|
| 400 |
+
include hook fasteners and the second fastening components <part-num-ref name="second fastening components">84</part-num-ref>
|
| 401 |
+
include complementary loop fasteners. Alternatively, the first <boundary-data type="line-number">20 </boundary-data>
|
| 402 |
+
fastening components <part-num-ref name="first fastening components">82</part-num-ref>
|
| 403 |
+
may include loop fasteners and the second fastening components <part-num-ref name="second fastening components">84</part-num-ref>
|
| 404 |
+
may be complementary hook fasteners. In another aspect, the fastening components <part-num-ref name="fastening components">82,</part-num-ref>
|
| 405 |
+
<part-num-ref name="fastening components 82,">84</part-num-ref>
|
| 406 |
+
can be interlocking similar surface fasteners, or adhesive and cohesive fastening elements such as an adhesive fastener and an adhesive-receptive landing zone or material; or the like. </p>
|
| 407 |
+
<p id="p-53" num="53">
|
| 408 |
+
<boundary-data type="line-number">
|
| 409 |
+
<confidence value="86">25</confidence>
|
| 410 |
+
</boundary-data>
|
| 411 |
+
[035] In addition to possibly having elastic side panels, the absorbent article <part-num-ref name="absorbent article">20</part-num-ref>
|
| 412 |
+
may include various waist elastic members for providing elasticity around the waist opening. For example, as shown in Fig. 2, the absorbent article <part-num-ref name="absorbent article">20</part-num-ref>
|
| 413 |
+
can include a front waist elastic member <part-num-ref name="front waist elastic member">54</part-num-ref>
|
| 414 |
+
and/or a back waist elastic member <part-num-ref name="back waist elastic member">56.</part-num-ref>
|
| 415 |
+
</p>
|
| 416 |
+
<p id="p-54" num="54">[036] As described above, the present disclosure is particularly directed to <boundary-data type="line-number">30 </boundary-data>
|
| 417 |
+
incorporating a body fluid indicating system, such as a wetness indicating system into the absorbent article <part-num-ref name="absorbent article">20.</part-num-ref>
|
| 418 |
+
In this regard, as shown in Figs. 1- <part-num-ref name="absorbent article 20. In this regard, as shown in Figs. 1-">4,</part-num-ref>
|
| 419 |
+
the absorbent <boundary-data type="header">
|
| 420 |
+
<confidence value="88">10</confidence>
|
| 421 |
+
</boundary-data>
|
| 422 |
+
<page-break num="11"/>
|
| 423 |
+
article <part-num-ref name="absorbent article">20</part-num-ref>
|
| 424 |
+
may include a first conductive element <part-num-ref name="first conductive element">100</part-num-ref>
|
| 425 |
+
spaced from a second conductive element <part-num-ref name="second conductive element">102.</part-num-ref>
|
| 426 |
+
In these embodiments, the conductive elements extend from the front region <part-num-ref name="front region">22</part-num-ref>
|
| 427 |
+
of the absorbent article to the back region <part-num-ref name="back region">24</part-num-ref>
|
| 428 |
+
without intersecting. The conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 429 |
+
and <part-num-ref name="and">102</part-num-ref>
|
| 430 |
+
can comprise any suitable <part-num-ref name="can comprise any suitable">
|
| 431 |
+
<confidence value="4">5</confidence>
|
| 432 |
+
</part-num-ref>
|
| 433 |
+
conductive material, such as a conductive thread or a conductive foil. The first conductive element <part-num-ref name="first conductive element">100</part-num-ref>
|
| 434 |
+
does not intersect the second conductive element <part-num-ref name="second conductive element">102</part-num-ref>
|
| 435 |
+
in order to form an open circuit that may be closed, for instance, when a conductive fluid is positioned in between the conductive elements. In other embodiments, however, the first conductive element <part-num-ref name="first conductive element">100</part-num-ref>
|
| 436 |
+
and the second conductive element <part-num-ref name="second conductive element">102</part-num-ref>
|
| 437 |
+
<part-num-ref name="">
|
| 438 |
+
<confidence value="86">10</confidence>
|
| 439 |
+
</part-num-ref>
|
| 440 |
+
may be connected to a sensor within the chassis. The sensor may, for example, be used to sense changes in temperature and/or may be used to sense the presence of a particular substance in urine or other body exudates. </p>
|
| 441 |
+
<p id="p-55" num="55">[037] In the embodiment shown in Fig. 1, the conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 442 |
+
and <part-num-ref name="and">102</part-num-ref>
|
| 443 |
+
extend the entire length of the absorbent article <part-num-ref name="absorbent article">20.</part-num-ref>
|
| 444 |
+
It should be understood, is however, that in other embodiments the conductive elements may extend only to the crotch region <part-num-ref name="crotch region">26</part-num-ref>
|
| 445 |
+
or may extend to any particular place in the absorbent article where a body fluid is intended to be sensed. </p>
|
| 446 |
+
<p id="p-56" num="56">[038] The conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 447 |
+
and <part-num-ref name="and">102</part-num-ref>
|
| 448 |
+
may be incorporated into the chassis <part-num-ref name="chassis">32</part-num-ref>
|
| 449 |
+
at any suitable location as long as the conductive elements are positioned so <confidence value="85">2o</confidence>
|
| 450 |
+
as to contact a body fluid that is absorbed by the absorbent article <part-num-ref name="absorbent article">20.</part-num-ref>
|
| 451 |
+
In this regard, the conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 452 |
+
and <part-num-ref name="and">102</part-num-ref>
|
| 453 |
+
generally lie inside the outercover <part-num-ref name="outercover">40.</part-num-ref>
|
| 454 |
+
In one embodiment, the conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 455 |
+
and <part-num-ref name="and">102</part-num-ref>
|
| 456 |
+
may be attached or laminated to the inside surface of the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 457 |
+
that faces the absorbent structure <part-num-ref name="absorbent structure">44.</part-num-ref>
|
| 458 |
+
Alternatively, the conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 459 |
+
and <part-num-ref name="and">102</part-num-ref>
|
| 460 |
+
may be <part-num-ref name="may be">
|
| 461 |
+
<confidence value="85">25</confidence>
|
| 462 |
+
</part-num-ref>
|
| 463 |
+
positioned on the absorbent structure <part-num-ref name="absorbent structure">44</part-num-ref>
|
| 464 |
+
or positioned on the liner <part-num-ref name="liner">42.</part-num-ref>
|
| 465 |
+
</p>
|
| 466 |
+
<p id="p-57" num="57">[039] In order for the internally positioned conductive elements <part-num-ref name="internally positioned conductive elements">100</part-num-ref>
|
| 467 |
+
and <part-num-ref name="and">102</part-num-ref>
|
| 468 |
+
to be easily connected to an externally mounted signaling device, the present invention provides an absorbent article having portions of the conductors <part-num-ref name="conductors">100</part-num-ref>
|
| 469 |
+
and/or <part-num-ref name="and/or">102</part-num-ref>
|
| 470 |
+
at least partially exposed through one or more non-conductive layers to define one or <part-num-ref name="at least partially exposed through one or more non-conductive layers to define one or">30</part-num-ref>
|
| 471 |
+
more external contact areas <part-num-ref name="more external contact areas">120</part-num-ref>
|
| 472 |
+
having one or more external contact points <part-num-ref name="having one or more external contact points">122.</part-num-ref>
|
| 473 |
+
</p>
|
| 474 |
+
<boundary-data type="header">
|
| 475 |
+
<confidence value="88">11</confidence>
|
| 476 |
+
</boundary-data>
|
| 477 |
+
<p id="p-58" num="58">
|
| 478 |
+
<page-break num="12"/>
|
| 479 |
+
See for example, Fig. 5 which is a cross sectional view of the absorbent article of Fig. 3 taken along the line 5-5. </p>
|
| 480 |
+
<p id="p-59" num="59">[040] Referring now to Fig. 5, the absorbent article <part-num-ref name="absorbent article">20,</part-num-ref>
|
| 481 |
+
in the portions illustrated, includes a laminate comprising an outercover <part-num-ref name="outercover">40,</part-num-ref>
|
| 482 |
+
a first conductive element <part-num-ref name="first conductive element">100,</part-num-ref>
|
| 483 |
+
<boundary-data type="line-number">
|
| 484 |
+
<confidence value="5">5</confidence>
|
| 485 |
+
</boundary-data>
|
| 486 |
+
and a liner <part-num-ref name="liner">42.</part-num-ref>
|
| 487 |
+
In various embodiments, and as illustrated in Fig. 5, the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 488 |
+
may include a laminate of two or more materials as is known in the art. For <confidence value="8">.</confidence>
|
| 489 |
+
</p>
|
| 490 |
+
<p id="p-60" num="60">example, the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 491 |
+
may be a laminate including a liquid impervious film layer and a non-woven "cloth-like" layer as is known in the art. The outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 492 |
+
defines the outer article surface <part-num-ref name="outer article surface">30</part-num-ref>
|
| 493 |
+
whereas the liner <part-num-ref name="liner">42</part-num-ref>
|
| 494 |
+
defines the inner article <boundary-data type="line-number">
|
| 495 |
+
<confidence value="86">10</confidence>
|
| 496 |
+
</boundary-data>
|
| 497 |
+
surface <part-num-ref name="inner article surface">28.</part-num-ref>
|
| 498 |
+
Portions of the first conductive element <part-num-ref name="first conductive element">100</part-num-ref>
|
| 499 |
+
are at least partially exposed through the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 500 |
+
to the outer surface <part-num-ref name="outer surface">30</part-num-ref>
|
| 501 |
+
to define one or more external contact points <part-num-ref name="to define one or more external contact points">122.</part-num-ref>
|
| 502 |
+
The contact points <part-num-ref name="contact points">122</part-num-ref>
|
| 503 |
+
collectively define an external contact zone <part-num-ref name="external contact zone">120</part-num-ref>
|
| 504 |
+
adapted for electrical connection with a signaling device. </p>
|
| 505 |
+
<p id="p-61" num="61">[041] The contact points <part-num-ref name="contact points">122</part-num-ref>
|
| 506 |
+
may have any suitable size, shape, and surface <boundary-data type="line-number">
|
| 507 |
+
<confidence value="66">15</confidence>
|
| 508 |
+
</boundary-data>
|
| 509 |
+
area. For example, the contact points <part-num-ref name="contact points">122</part-num-ref>
|
| 510 |
+
may be generally circular and have a diameter of 0.1 to 5 mm, 0.5 to 2 mm, or about <part-num-ref name="mm, or about">1</part-num-ref>
|
| 511 |
+
mm. In some embodiments, the individual contact points <part-num-ref name="individual contact points">122</part-num-ref>
|
| 512 |
+
may have a surface area of at least 0.1 mm2, at least 1.0 mm<confidence value="5">2</confidence>
|
| 513 |
+
, or at least 2.0 mm<confidence value="5">2</confidence>
|
| 514 |
+
. In some embodiments, the individual contact points <part-num-ref name="individual contact points">122</part-num-ref>
|
| 515 |
+
may have a surface area of about <part-num-ref name="surface area of about">3</part-num-ref>
|
| 516 |
+
mm<confidence value="5">2</confidence>
|
| 517 |
+
. Any number of contact points <part-num-ref name="mm2. Any number of contact points">122</part-num-ref>
|
| 518 |
+
<boundary-data type="line-number">
|
| 519 |
+
<confidence value="86">20</confidence>
|
| 520 |
+
</boundary-data>
|
| 521 |
+
may be included and the individual contact points <part-num-ref name="individual contact points">122</part-num-ref>
|
| 522 |
+
may have different shapes and may be provided in any suitable combination of shape, size, and/or pattern to form an external contact zone <part-num-ref name="external contact zone">120.</part-num-ref>
|
| 523 |
+
Likewise, the external contact zone <part-num-ref name="external contact zone">120</part-num-ref>
|
| 524 |
+
may have any suitable size, shape, and surface area. In some embodiments, the external contact area <part-num-ref name="external contact area">120</part-num-ref>
|
| 525 |
+
may be expressed as the percentage of the exposed <boundary-data type="line-number">25 </boundary-data>
|
| 526 |
+
conductor surface area as compared to the total area. In some embodiments, the external contact area <part-num-ref name="external contact area">120</part-num-ref>
|
| 527 |
+
may include <part-num-ref name="may include">5</part-num-ref>
|
| 528 |
+
to <part-num-ref name="to">50</part-num-ref>
|
| 529 |
+
percent or <part-num-ref name="percent or">20</part-num-ref>
|
| 530 |
+
to <part-num-ref name="to">40</part-num-ref>
|
| 531 |
+
percent conductive surface area. </p>
|
| 532 |
+
<p id="p-62" num="62">[042] In some embodiments, the contact points <part-num-ref name="contact points">122</part-num-ref>
|
| 533 |
+
may include indentations <part-num-ref name="may include indentations">124</part-num-ref>
|
| 534 |
+
on the inner surface <part-num-ref name="inner surface">28</part-num-ref>
|
| 535 |
+
corresponding to the contact points <part-num-ref name="contact points">122.</part-num-ref>
|
| 536 |
+
For example, as <part-num-ref name="contact points 122. For example, as">30</part-num-ref>
|
| 537 |
+
illustrated in Figs. 1, <part-num-ref name="illustrated in Figs. 1,">2,</part-num-ref>
|
| 538 |
+
and <part-num-ref name="illustrated in Figs. 1, 2, and">5</part-num-ref>
|
| 539 |
+
indentations <part-num-ref name="indentations">124</part-num-ref>
|
| 540 |
+
are present on the inner surface <part-num-ref name="inner surface">28</part-num-ref>
|
| 541 |
+
<boundary-data type="header">
|
| 542 |
+
<confidence value="88">12</confidence>
|
| 543 |
+
</boundary-data>
|
| 544 |
+
<page-break num="13"/>
|
| 545 |
+
<confidence value="2221">n-l.</confidence>
|
| 546 |
+
<confidence value="2111">0D4-</confidence>
|
| 547 |
+
<confidence value="11">Iy</confidence>
|
| 548 |
+
<confidence value="221">4UU</confidence>
|
| 549 |
+
<confidence value="81711">UDU7I</confidence>
|
| 550 |
+
and correspond with external contact points <part-num-ref name="n-l. 0D4- Iy 4UU UDU7I and correspond with external contact points">122</part-num-ref>
|
| 551 |
+
exposed on the outer surface <part-num-ref name="outer surface">30</part-num-ref>
|
| 552 |
+
(visible in Figs. 3 and 5). </p>
|
| 553 |
+
<p id="p-63" num="63">[043] The external contact points <part-num-ref name="external contact points">122</part-num-ref>
|
| 554 |
+
define a contact point perimeter <part-num-ref name="contact point perimeter">126.</part-num-ref>
|
| 555 |
+
In some embodiments, the material, through which the external contact points <part-num-ref name="external contact points">122</part-num-ref>
|
| 556 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 557 |
+
are exposed, may be sealed about the contact point perimeter <part-num-ref name="contact point perimeter">126</part-num-ref>
|
| 558 |
+
thereby inhibiting the passage of fluid through the material at these locations. See for example Fig. 5 wherein the external contact points <part-num-ref name="external contact points">122</part-num-ref>
|
| 559 |
+
are exposed through the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 560 |
+
and wherein the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 561 |
+
is sealed about the contact point perimeter <part-num-ref name="contact point perimeter">126</part-num-ref>
|
| 562 |
+
to prevent fluid escape therethrough. </p>
|
| 563 |
+
<p id="p-64" num="64">
|
| 564 |
+
<boundary-data type="line-number">
|
| 565 |
+
<confidence value="85">10</confidence>
|
| 566 |
+
</boundary-data>
|
| 567 |
+
[044] In some embodiments, the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 568 |
+
may be sealed about the perimeter <part-num-ref name="perimeter">126</part-num-ref>
|
| 569 |
+
of external contact points <part-num-ref name="of external contact points">122</part-num-ref>
|
| 570 |
+
such that portions of the outercover with external contact points <part-num-ref name="outercover with external contact points">122</part-num-ref>
|
| 571 |
+
have at least as much resistance to fluid passage as those portions of the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 572 |
+
having no external contact points <part-num-ref name="having no external contact points">122</part-num-ref>
|
| 573 |
+
exposed therethrough. In other words, in some embodiments, there is no <boundary-data type="line-number">
|
| 574 |
+
<confidence value="66">15</confidence>
|
| 575 |
+
</boundary-data>
|
| 576 |
+
detriment to the liquid impermeability of the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 577 |
+
due to the external contact points <part-num-ref name="external contact points">122.</part-num-ref>
|
| 578 |
+
</p>
|
| 579 |
+
<p id="p-65" num="65">[045] In some embodiments, portions of the first conductive element <part-num-ref name="first conductive element">100</part-num-ref>
|
| 580 |
+
and/or the second conductive element <part-num-ref name="second conductive element">102</part-num-ref>
|
| 581 |
+
may be exposed and/or extend at least partially through the liner <part-num-ref name="liner">42</part-num-ref>
|
| 582 |
+
to the inner article surface <part-num-ref name="inner article surface">28</part-num-ref>
|
| 583 |
+
to define one or more <boundary-data type="line-number">
|
| 584 |
+
<confidence value="85">2o</confidence>
|
| 585 |
+
</boundary-data>
|
| 586 |
+
external contact points <part-num-ref name="to define one or more external contact points">122</part-num-ref>
|
| 587 |
+
(not shown). The contact points <part-num-ref name="contact points">122</part-num-ref>
|
| 588 |
+
collectively define an external contact area <part-num-ref name="external contact area">120</part-num-ref>
|
| 589 |
+
adapted for electrical connection with a signaling device. In some embodiments, the contact points <part-num-ref name="contact points">122</part-num-ref>
|
| 590 |
+
may include indentations <part-num-ref name="may include indentations">124</part-num-ref>
|
| 591 |
+
on the outer surface <part-num-ref name="outer surface">30</part-num-ref>
|
| 592 |
+
corresponding to the contact points <part-num-ref name="contact points">122.</part-num-ref>
|
| 593 |
+
In some embodiments, portions of the first conductive element <part-num-ref name="first conductive element">100</part-num-ref>
|
| 594 |
+
and/or portions of the <boundary-data type="line-number">25 </boundary-data>
|
| 595 |
+
second conductive element <part-num-ref name="second conductive element">102</part-num-ref>
|
| 596 |
+
may be at least partially exposed and/or extended through both the liner <part-num-ref name="liner">42</part-num-ref>
|
| 597 |
+
and the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 598 |
+
to define external contact points <part-num-ref name="to define external contact points">122</part-num-ref>
|
| 599 |
+
on the inner article surface <part-num-ref name="inner article surface">28</part-num-ref>
|
| 600 |
+
and/or the outer article surface <part-num-ref name="outer article surface">30.</part-num-ref>
|
| 601 |
+
In such embodiments, the signaling device may suitably be connected with either or both surfaces. </p>
|
| 602 |
+
<p id="p-66" num="66">
|
| 603 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 604 |
+
[046] In various embodiments, portions of the first conductive element <part-num-ref name="first conductive element">100</part-num-ref>
|
| 605 |
+
and/or the second conductive element <part-num-ref name="second conductive element">102</part-num-ref>
|
| 606 |
+
may extend at least partially through <boundary-data type="header">
|
| 607 |
+
<confidence value="88">13</confidence>
|
| 608 |
+
</boundary-data>
|
| 609 |
+
<page-break num="14"/>
|
| 610 |
+
<confidence value="455">IK-</confidence>
|
| 611 |
+
<confidence value="54651424">bU412UU1</confidence>
|
| 612 |
+
<confidence value="888">UU1</confidence>
|
| 613 |
+
the liner <part-num-ref name="liner">42</part-num-ref>
|
| 614 |
+
and/or the outercover <part-num-ref name="outercover">40.</part-num-ref>
|
| 615 |
+
In some embodiments, portions of the first conductive element <part-num-ref name="first conductive element">100</part-num-ref>
|
| 616 |
+
and/or the second conductive element <part-num-ref name="second conductive element">102</part-num-ref>
|
| 617 |
+
may extend at least partially through the liner <part-num-ref name="liner">42</part-num-ref>
|
| 618 |
+
and/or the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 619 |
+
without rupturing the conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 620 |
+
and/or <part-num-ref name="and/or">102.</part-num-ref>
|
| 621 |
+
For example, in Fig. 5, portions of <boundary-data type="line-number">5 </boundary-data>
|
| 622 |
+
conductive element <part-num-ref name="and/or 102. For example, in Fig. 5, portions of conductive element">100</part-num-ref>
|
| 623 |
+
extend completely through the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 624 |
+
and are intact, i.e., not ruptured, torn, or otherwise discontinuous. In some embodiments, all portions of the first element <part-num-ref name="first element">100</part-num-ref>
|
| 625 |
+
and all portions of the second conductive element <part-num-ref name="second conductive element">102</part-num-ref>
|
| 626 |
+
are intact. Maintaining the conductive elements intact is believed to be advantageous because more continuity results in better reliability of the body <boundary-data type="line-number">
|
| 627 |
+
<confidence value="86">10</confidence>
|
| 628 |
+
</boundary-data>
|
| 629 |
+
fluid indicating system. </p>
|
| 630 |
+
<p id="p-67" num="67">[047] In some embodiments, the absorbent article may include a plurality of bond points <part-num-ref name="plurality of bond points">134</part-num-ref>
|
| 631 |
+
and a plurality of external contact points <part-num-ref name="plurality of external contact points">122.</part-num-ref>
|
| 632 |
+
For example, as illustrated in Fig. 3, an absorbent article <part-num-ref name="absorbent article">20</part-num-ref>
|
| 633 |
+
may include conductive elements <part-num-ref name="may include conductive elements">100</part-num-ref>
|
| 634 |
+
and <part-num-ref name="and">102</part-num-ref>
|
| 635 |
+
located between a liner and an outercover. The absorbent article <part-num-ref name="absorbent article">20</part-num-ref>
|
| 636 |
+
may <boundary-data type="line-number">15 </boundary-data>
|
| 637 |
+
also include a plurality of bond points <part-num-ref name="plurality of bond points">134</part-num-ref>
|
| 638 |
+
between the outercover and liner in locations that do not include the conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 639 |
+
and <part-num-ref name="and">102.</part-num-ref>
|
| 640 |
+
Likewise, the absorbent article <part-num-ref name="absorbent article">20</part-num-ref>
|
| 641 |
+
may include external contact points <part-num-ref name="may include external contact points">122</part-num-ref>
|
| 642 |
+
in locations that include the conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 643 |
+
and <part-num-ref name="and">102</part-num-ref>
|
| 644 |
+
between the liner and the outercover. </p>
|
| 645 |
+
<p id="p-68" num="68">
|
| 646 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 647 |
+
[048] In order for the conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 648 |
+
and <part-num-ref name="and">102</part-num-ref>
|
| 649 |
+
to be easily connected to a signaling device, the first conductive element <part-num-ref name="first conductive element">100</part-num-ref>
|
| 650 |
+
may be attached to and/or include a first conductive pad member <part-num-ref name="first conductive pad member">104,</part-num-ref>
|
| 651 |
+
while the second conductive element <part-num-ref name="second conductive element">102</part-num-ref>
|
| 652 |
+
may be connected to and/or include a second conductive pad member <part-num-ref name="second conductive pad member">106.</part-num-ref>
|
| 653 |
+
</p>
|
| 654 |
+
<p id="p-69" num="69">Likewise, portions of the first conductive pad member <part-num-ref name="first conductive pad member">104</part-num-ref>
|
| 655 |
+
and/or portions of the <boundary-data type="line-number">25 </boundary-data>
|
| 656 |
+
second conductive pad member <part-num-ref name="second conductive pad member">106</part-num-ref>
|
| 657 |
+
may be exposed and/or extended through the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 658 |
+
and/or the liner <part-num-ref name="liner">42</part-num-ref>
|
| 659 |
+
to define external contact points <part-num-ref name="to define external contact points">122</part-num-ref>
|
| 660 |
+
as described herein. </p>
|
| 661 |
+
<p id="p-70" num="70">[049] The pad members <part-num-ref name="pad members">104</part-num-ref>
|
| 662 |
+
and <part-num-ref name="and">106</part-num-ref>
|
| 663 |
+
may be provided for making a reliable connection between the open circuit formed by the conductive elements to a <boundary-data type="line-number">30 </boundary-data>
|
| 664 |
+
signaling device that is intended to be installed on the chassis by the consumer. </p>
|
| 665 |
+
<p id="p-71" num="71">In particular, the external contact points <part-num-ref name="external contact points">122</part-num-ref>
|
| 666 |
+
associated with the pad me<confidence value="8">m</confidence>
|
| 667 |
+
bers <part-num-ref name="pad members">104</part-num-ref>
|
| 668 |
+
<boundary-data type="header">
|
| 669 |
+
<confidence value="88">14</confidence>
|
| 670 |
+
</boundary-data>
|
| 671 |
+
<page-break num="15"/>
|
| 672 |
+
<confidence value="886">K-G</confidence>
|
| 673 |
+
<confidence value="18845558">64119991</confidence>
|
| 674 |
+
USU1 and <part-num-ref name="K-G 64119991USU1 and">106</part-num-ref>
|
| 675 |
+
may create a larger target zone for attaching the signaling device to the conductive elements. </p>
|
| 676 |
+
<p id="p-72" num="72">[050<confidence value="5">]</confidence>
|
| 677 |
+
The position of the conductive pad members <part-num-ref name="conductive pad members">104</part-num-ref>
|
| 678 |
+
and <part-num-ref name="and">106</part-num-ref>
|
| 679 |
+
on the absorbent article <part-num-ref name="absorbent article">20</part-num-ref>
|
| 680 |
+
can vary depending upon where it is desired to mount the signaling <boundary-data type="line-number">5 </boundary-data>
|
| 681 |
+
device. For instance, in Fig. 2, the conductive pad members <part-num-ref name="conductive pad members">104</part-num-ref>
|
| 682 |
+
and <part-num-ref name="and">106</part-num-ref>
|
| 683 |
+
are positioned in the back region <part-num-ref name="back region">24</part-num-ref>
|
| 684 |
+
along the waist opening of the article. It should be appreciated, however, that in other embodiments, the absorbent article <part-num-ref name="absorbent article">20</part-num-ref>
|
| 685 |
+
may include conductive pad members being positioned at either or both ends of each conductive element <part-num-ref name="may include conductive pad members being positioned at either or both ends of each conductive element">100</part-num-ref>
|
| 686 |
+
and <part-num-ref name="and">102.</part-num-ref>
|
| 687 |
+
In this manner, a user can determine whether <boundary-data type="line-number">10 </boundary-data>
|
| 688 |
+
or not to install the signaling device on the front or the back of the article. In still other embodiments, it should be understood that the pad members may be located along the side of the article or towards the crotch region of the article. </p>
|
| 689 |
+
<p id="p-73" num="73">[051] Referring to Fig. 6, for exemplary purposes, a signaling device <part-num-ref name="signaling device">110</part-num-ref>
|
| 690 |
+
is shown attached to the external contact points <part-num-ref name="external contact points">122.</part-num-ref>
|
| 691 |
+
As shown, in this embodiment, <boundary-data type="line-number">
|
| 692 |
+
<confidence value="66">15</confidence>
|
| 693 |
+
</boundary-data>
|
| 694 |
+
a signaling device <part-num-ref name="signaling device">110</part-num-ref>
|
| 695 |
+
includes a transmitter <part-num-ref name="transmitter">112</part-num-ref>
|
| 696 |
+
and a receiver <part-num-ref name="receiver">114.</part-num-ref>
|
| 697 |
+
The transmitter <part-num-ref name="transmitter">112</part-num-ref>
|
| 698 |
+
may include two or more terminals that are electrically connected to the first and second conductive elements <part-num-ref name="first and second conductive elements">100</part-num-ref>
|
| 699 |
+
and <part-num-ref name="and">102</part-num-ref>
|
| 700 |
+
via the external contact points <part-num-ref name="external contact points">122.</part-num-ref>
|
| 701 |
+
When a body fluid is present in the absorbent article <part-num-ref name="absorbent article">20,</part-num-ref>
|
| 702 |
+
the open circuit formed by the conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 703 |
+
and <part-num-ref name="and">102</part-num-ref>
|
| 704 |
+
is closed which, in turn, <boundary-data type="line-number">20 </boundary-data>
|
| 705 |
+
activates the signaling device <part-num-ref name="signaling device">110.</part-num-ref>
|
| 706 |
+
In particular, in this embodiment, the transmitter <part-num-ref name="transmitter">112</part-num-ref>
|
| 707 |
+
sends a wireless signal to the receiver <part-num-ref name="receiver">114</part-num-ref>
|
| 708 |
+
which then indicates to a user that a body fluid is present in the absorbent article. </p>
|
| 709 |
+
<p id="p-74" num="74">[052] The signaling device <part-num-ref name="signaling device">110</part-num-ref>
|
| 710 |
+
can emit an audible signal or a visual signal in order to indicate to the user that the circuit has been closed. The audible signal, <boundary-data type="line-number">
|
| 711 |
+
<confidence value="86">25</confidence>
|
| 712 |
+
</boundary-data>
|
| 713 |
+
for instance, may be as simple as one or more beeps to perhaps emitting a musical tune. Similarly, if the signaling device <part-num-ref name="signaling device">110</part-num-ref>
|
| 714 |
+
issues a visible signal, the visible signal may comprise a few lights or an interactive display. In still another embodiment, the receiver <part-num-ref name="receiver">114</part-num-ref>
|
| 715 |
+
of the signaling device <part-num-ref name="signaling device">110</part-num-ref>
|
| 716 |
+
may be configured to vibrate when the circuit within the absorbent article is closed. </p>
|
| 717 |
+
<boundary-data type="header">
|
| 718 |
+
<confidence value="88">15</confidence>
|
| 719 |
+
</boundary-data>
|
| 720 |
+
<p id="p-75" num="75">
|
| 721 |
+
<page-break num="16"/>
|
| 722 |
+
[053] As described above, the signaling device <part-num-ref name="signaling device">110</part-num-ref>
|
| 723 |
+
can be configured to indicate the presence of any suitable conductive fluid within the absorbent article <part-num-ref name="absorbent article">20.</part-num-ref>
|
| 724 |
+
The fluid may comprise, for instance, urine, a metabolite, and the like. </p>
|
| 725 |
+
<p id="p-76" num="76">[054] In the embodiment shown in Fig. 6, the signaling device <part-num-ref name="signaling device">110</part-num-ref>
|
| 726 |
+
includes a <boundary-data type="line-number">
|
| 727 |
+
<confidence value="5">s</confidence>
|
| 728 |
+
</boundary-data>
|
| 729 |
+
transmitter <part-num-ref name="transmitter">112</part-num-ref>
|
| 730 |
+
in combination with a receiver <part-num-ref name="receiver">114.</part-num-ref>
|
| 731 |
+
It should also be understood, however, that the signaling device may comprise a single unit that remains attached to the absorbent article <part-num-ref name="absorbent article">20.</part-num-ref>
|
| 732 |
+
For example, the signaling device may be mounted on the absorbent article and issue a visible signal and/or an audible signal from the signaling device itself. </p>
|
| 733 |
+
<p id="p-77" num="77">
|
| 734 |
+
<boundary-data type="line-number">
|
| 735 |
+
<confidence value="66">10</confidence>
|
| 736 |
+
</boundary-data>
|
| 737 |
+
[055] As discuss above, typical body fluid indicating systems require penetration through one or more layers to create contact between the conductive elements and the signaling device. The present invention includes one or more external contact points <part-num-ref name="present invention includes one or more external contact points">122</part-num-ref>
|
| 738 |
+
exposed to the surface of the article (inner surface <part-num-ref name="article (inner surface">28</part-num-ref>
|
| 739 |
+
and/or outer surface <part-num-ref name="and/or outer surface">30)</part-num-ref>
|
| 740 |
+
to provide direct surface to surface contact with the terminals of <boundary-data type="line-number">
|
| 741 |
+
<confidence value="66">15</confidence>
|
| 742 |
+
</boundary-data>
|
| 743 |
+
the signaling device. Therefore, any suitable means of attaching the signaling device to the absorbent article may be used. For example, in various embodiments, the signaling device may be attached to the absorbent article with adhesives, cohesives, hook and loop systems, snaps, buttons, and the like, and combinations thereof. Additionally or alternatively, the signaling device may be <boundary-data type="line-number">
|
| 744 |
+
<confidence value="86">20</confidence>
|
| 745 |
+
</boundary-data>
|
| 746 |
+
placed in a pocket or otherwise physically retained in proximity to the external contact points <part-num-ref name="external contact points">122</part-num-ref>
|
| 747 |
+
to establish electrical conductivity therebetween. </p>
|
| 748 |
+
<p id="p-78" num="78">[056] In some embodiments, the external contact points <part-num-ref name="external contact points">122</part-num-ref>
|
| 749 |
+
may be arranged such that the external contact area <part-num-ref name="external contact area">120</part-num-ref>
|
| 750 |
+
has any suitable shape, size, design, or configuration. For example, referring to Fig. 3, the external contact points <part-num-ref name="external contact points">122</part-num-ref>
|
| 751 |
+
are <boundary-data type="line-number">25 </boundary-data>
|
| 752 |
+
generally arranged in two parallel lines extending in the longitudinal direction <part-num-ref name="longitudinal direction">48</part-num-ref>
|
| 753 |
+
and corresponding with the first and the second conductive elements <part-num-ref name="second conductive elements">100</part-num-ref>
|
| 754 |
+
and <part-num-ref name="and">102.</part-num-ref>
|
| 755 |
+
</p>
|
| 756 |
+
<p id="p-79" num="79">In some embodiments, the external contact points <part-num-ref name="external contact points">122</part-num-ref>
|
| 757 |
+
may be arranged to resemble a target, arrows, letters, dots, shapes, or other indicia that may assist in the proper alignment of a signaling device with the conductive elements. </p>
|
| 758 |
+
<p id="p-80" num="80">
|
| 759 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 760 |
+
[057] For example, Fig. 7 representatively illustrates an absorbent article <part-num-ref name="absorbent article">160</part-num-ref>
|
| 761 |
+
and a signaling device <part-num-ref name="signaling device">162.</part-num-ref>
|
| 762 |
+
In some embodiments, the absorbent article <part-num-ref name="absorbent article">160</part-num-ref>
|
| 763 |
+
and the <boundary-data type="header">
|
| 764 |
+
<confidence value="88">16</confidence>
|
| 765 |
+
</boundary-data>
|
| 766 |
+
<page-break num="17"/>
|
| 767 |
+
signaling device <part-num-ref name="signaling device">162</part-num-ref>
|
| 768 |
+
may be a kit <part-num-ref name="kit">158.</part-num-ref>
|
| 769 |
+
The absorbent article <part-num-ref name="absorbent article">160</part-num-ref>
|
| 770 |
+
includes a first conductive element <part-num-ref name="first conductive element">100</part-num-ref>
|
| 771 |
+
and a second conductive element <part-num-ref name="second conductive element">102.</part-num-ref>
|
| 772 |
+
Portions of the conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 773 |
+
and <part-num-ref name="and">102</part-num-ref>
|
| 774 |
+
are at least partially exposed through the outercover <part-num-ref name="outercover">168</part-num-ref>
|
| 775 |
+
to define a plurality of external contact points <part-num-ref name="plurality of external contact points">164.</part-num-ref>
|
| 776 |
+
In the <boundary-data type="line-number">5 </boundary-data>
|
| 777 |
+
illustrated embodiment, the external contact points <part-num-ref name="external contact points">164</part-num-ref>
|
| 778 |
+
are shaped like hexagons. </p>
|
| 779 |
+
<p id="p-81" num="81">
|
| 780 |
+
<confidence value="5">[</confidence>
|
| 781 |
+
058] In some embodiments, the signaling device <part-num-ref name="signaling device">162</part-num-ref>
|
| 782 |
+
may include one or more indicia <part-num-ref name="may include one or more indicia">166</part-num-ref>
|
| 783 |
+
and the external contact points may be arranged in the same shape, pattern, and/or size as the indicia <part-num-ref name="indicia">166.</part-num-ref>
|
| 784 |
+
For example, as illustrated in Fig. 7, the signaling device <part-num-ref name="signaling device">162</part-num-ref>
|
| 785 |
+
has an indicia <part-num-ref name="indicia">166</part-num-ref>
|
| 786 |
+
made up of a series of hexagon shapes <boundary-data type="line-number">
|
| 787 |
+
<confidence value="86">10</confidence>
|
| 788 |
+
</boundary-data>
|
| 789 |
+
and the external contact points <part-num-ref name="external contact points">164</part-num-ref>
|
| 790 |
+
are sized, shaped, and positioned such that aligning the indicia <part-num-ref name="indicia">166</part-num-ref>
|
| 791 |
+
of the signaling device <part-num-ref name="signaling device">162</part-num-ref>
|
| 792 |
+
with the external contact points <part-num-ref name="external contact points">164</part-num-ref>
|
| 793 |
+
assures that the electrical terminals of the signaling device <part-num-ref name="signaling device">162</part-num-ref>
|
| 794 |
+
are aligned with the external contact points <part-num-ref name="external contact points">164</part-num-ref>
|
| 795 |
+
of the conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 796 |
+
and <part-num-ref name="and">102.</part-num-ref>
|
| 797 |
+
</p>
|
| 798 |
+
<p id="p-82" num="82">[059] The conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 799 |
+
and/or <part-num-ref name="and/or">102</part-num-ref>
|
| 800 |
+
may include any suitable <boundary-data type="line-number">
|
| 801 |
+
<confidence value="66">15</confidence>
|
| 802 |
+
</boundary-data>
|
| 803 |
+
conductive material. In some embodiments, the conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 804 |
+
and/or <part-num-ref name="and/or">102</part-num-ref>
|
| 805 |
+
can include conductive thread, conductive foil, and the like, and combinations thereof. In some embodiments, the conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 806 |
+
and/or <part-num-ref name="and/or">102</part-num-ref>
|
| 807 |
+
may be a laminate made of two or more layers of material wherein at least one of the layers is conductive. In some embodiments, the conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 808 |
+
and/or <boundary-data type="line-number">20 </boundary-data>
|
| 809 |
+
<part-num-ref name="and/or">102</part-num-ref>
|
| 810 |
+
may include a conductive layer oriented towards the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 811 |
+
and a second layer oriented towards liner <part-num-ref name="second layer oriented towards liner">42.</part-num-ref>
|
| 812 |
+
In some embodiments, the second layer may be a masking layer. </p>
|
| 813 |
+
<p id="p-83" num="83">[060] As used herein, the term "masking layer" refers to a layer of material having a color and/or pattern similar to the color and/or pattern of an overlaying material <boundary-data type="line-number">
|
| 814 |
+
<confidence value="86">25</confidence>
|
| 815 |
+
</boundary-data>
|
| 816 |
+
such that the masking layer is less visually noticeable. For example, Fig. 8 representatively illustrates a cross-sectional view similar to Fig. 5. Fig. 8 illustrates a liner <part-num-ref name="liner">42</part-num-ref>
|
| 817 |
+
defining an inner article surface <part-num-ref name="inner article surface">28</part-num-ref>
|
| 818 |
+
and an outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 819 |
+
defining an outer article surface <part-num-ref name="outer article surface">30.</part-num-ref>
|
| 820 |
+
Positioned between the liner <part-num-ref name="liner">42</part-num-ref>
|
| 821 |
+
and the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 822 |
+
is a conductive element <part-num-ref name="conductive element">100.</part-num-ref>
|
| 823 |
+
The conductive element <part-num-ref name="conductive element">100</part-num-ref>
|
| 824 |
+
includes <boundary-data type="line-number">
|
| 825 |
+
<confidence value="86">30</confidence>
|
| 826 |
+
</boundary-data>
|
| 827 |
+
a conductive layer <part-num-ref name="conductive layer">128</part-num-ref>
|
| 828 |
+
and a masking layer <part-num-ref name="masking layer">130</part-num-ref>
|
| 829 |
+
laminated together. The conductive layer <part-num-ref name="conductive layer">128</part-num-ref>
|
| 830 |
+
is oriented towards the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 831 |
+
whereas the masking <boundary-data type="header">
|
| 832 |
+
<confidence value="88">17</confidence>
|
| 833 |
+
</boundary-data>
|
| 834 |
+
<page-break num="18"/>
|
| 835 |
+
layer <part-num-ref name="masking layer">130</part-num-ref>
|
| 836 |
+
is oriented towards the liner <part-num-ref name="liner">42.</part-num-ref>
|
| 837 |
+
Portions of the conductive element <part-num-ref name="conductive element">100</part-num-ref>
|
| 838 |
+
are exposed through the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 839 |
+
to define external contact points <part-num-ref name="to define external contact points">122.</part-num-ref>
|
| 840 |
+
</p>
|
| 841 |
+
<p id="p-84" num="84">Each external contact point 122 defines a contact point perimeter <part-num-ref name="contact point perimeter">126.</part-num-ref>
|
| 842 |
+
In various embodiments, the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 843 |
+
may be sealed about the contact point perimeter <boundary-data type="line-number">
|
| 844 |
+
<confidence value="5">5</confidence>
|
| 845 |
+
</boundary-data>
|
| 846 |
+
<part-num-ref name="contact point perimeter">126</part-num-ref>
|
| 847 |
+
to prevent fluid passage there through. </p>
|
| 848 |
+
<p id="p-85" num="85">[061] In some embodiments, the liner <part-num-ref name="liner">42</part-num-ref>
|
| 849 |
+
may be white and the conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 850 |
+
and/or <part-num-ref name="and/or">102</part-num-ref>
|
| 851 |
+
may include a masking layer <part-num-ref name="masking layer">130</part-num-ref>
|
| 852 |
+
that is also white. In these embodiments, the conductive layer <part-num-ref name="conductive layer">128</part-num-ref>
|
| 853 |
+
of elements <part-num-ref name="of elements">100</part-num-ref>
|
| 854 |
+
and/or <part-num-ref name="and/or">102</part-num-ref>
|
| 855 |
+
may be less visible through the liner <part-num-ref name="liner">42</part-num-ref>
|
| 856 |
+
because of the masking layer <part-num-ref name="masking layer">130.</part-num-ref>
|
| 857 |
+
</p>
|
| 858 |
+
<p id="p-86" num="86">
|
| 859 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 860 |
+
[062] The conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 861 |
+
and/or <part-num-ref name="and/or">102</part-num-ref>
|
| 862 |
+
may have any suitable thickness and/or width. For example, in some embodiments, the conductive elements <part-num-ref name="conductive elements">100</part-num-ref>
|
| 863 |
+
and/or <part-num-ref name="and/or">102</part-num-ref>
|
| 864 |
+
may have a thickness of <part-num-ref name="thickness of">25</part-num-ref>
|
| 865 |
+
- <part-num-ref name="-">4000</part-num-ref>
|
| 866 |
+
angstroms, <part-num-ref name="angstroms,">50</part-num-ref>
|
| 867 |
+
- <part-num-ref name="-">2000</part-num-ref>
|
| 868 |
+
angstroms, or <part-num-ref name="angstroms, or">100</part-num-ref>
|
| 869 |
+
- <part-num-ref name="-">500</part-num-ref>
|
| 870 |
+
angstroms. Suitable conductive materials include NEPTAPE <part-num-ref name="angstroms. Suitable conductive materials include NEPTAPE">1001</part-num-ref>
|
| 871 |
+
laminated foil available from NEPTCO having offices at <part-num-ref name="laminated foil available from NEPTCO having offices at">30</part-num-ref>
|
| 872 |
+
Hamlet St., Pawtucket, <boundary-data type="line-number">
|
| 873 |
+
<confidence value="66">15</confidence>
|
| 874 |
+
</boundary-data>
|
| 875 |
+
Rhode Island, USA. NEPTAPE <part-num-ref name="Hamlet St., Pawtucket, Rhode Island, USA. NEPTAPE">1001</part-num-ref>
|
| 876 |
+
is a laminate having a <part-num-ref name="">12</part-num-ref>
|
| 877 |
+
micron layer of polyester film and a <part-num-ref name="">12</part-num-ref>
|
| 878 |
+
micron layer of aluminum film. Other suitable conductive materials include vapor deposited films such as those available from Vacumet Corporation having offices at <part-num-ref name="micron layer of aluminum film. Other suitable conductive materials include vapor deposited films such as those available from Vacumet Corporation having offices at">22</part-num-ref>
|
| 879 |
+
Riverview Drive, Wayne, New Jersey, USA. </p>
|
| 880 |
+
<p id="p-87" num="87">[063] In another aspect, the present invention provides a method of exposing <boundary-data type="line-number">20 </boundary-data>
|
| 881 |
+
portions of one or more internally positioned conductive materials to an external surface of an absorbent article. The method includes providing at least one conductive material and at least one non-conductive material. The method further includes exposing and/or extending one or more portions of the conductive material at least partially through the non-conductive material to define one or <boundary-data type="line-number">25 </boundary-data>
|
| 882 |
+
more external contact points. The exposing step may include ultrasonic bonding, pressure bonding, thermal bonding, and the like. The method may further include forming a seal about the contact points such that the non-conduct material remains liquid impermeable. The seal may result from portions of the non- conductive layers melting and flowing around the external contact point perimeter. </p>
|
| 883 |
+
<p id="p-88" num="88">
|
| 884 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 885 |
+
The method may further include locating the conductive material between the first non-conductive material and a second non-conductive material to form an absorbent article wherein the external contact points are exposed to an inner <boundary-data type="header">
|
| 886 |
+
<confidence value="88">18</confidence>
|
| 887 |
+
</boundary-data>
|
| 888 |
+
<page-break num="19"/>
|
| 889 |
+
and/or outer article surface. As used herein, the term "directed" describes the act of moving a first object through or towards a second object or surface. </p>
|
| 890 |
+
<p id="p-89" num="89">[064] In some embodiments, the method of exposing an internally positioned conductive material to an external surface of an absorbent article includes <boundary-data type="line-number">5 </boundary-data>
|
| 891 |
+
providing an outercover and liner in facing relation. The method may further include providing at least one conductive material located between the outercover and liner material. The method may further include at least partially exposing one or more portions of the conductive material through the outercover and/or the liner to define one or more external contact points. The exposing step may include <boundary-data type="line-number">
|
| 892 |
+
<confidence value="86">10</confidence>
|
| 893 |
+
</boundary-data>
|
| 894 |
+
ultrasonic bonding, pressure bonding, thermal bonding, and the like. In some embodiments, the method may further include sealing the outercover and/or the liner about the external contact points. The sealing may result from portions of the liner, outercover, adhesives, or combinations thereof experiencing localized melting thereby permitting material to flow around the external contact points. In <boundary-data type="line-number">
|
| 895 |
+
<confidence value="66">15</confidence>
|
| 896 |
+
</boundary-data>
|
| 897 |
+
some embodiments, the liner and the outercover may be bonded in locations that include the conductive material therebetween and in locations that do not include the conductive material therebetween. In other words, the outercover, conductive material, and liner laminate may include a plurality of bond points, some resulting in external contact points and some absent external contact points. As such, <boundary-data type="line-number">20 </boundary-data>
|
| 898 |
+
precise registration is not necessary to create the external contact points because a wide path of bonding can be created. When the conductive material is present, portions corresponding to the bond pattern will be exposed, at least partially, through the material. When the conductive material is not present, the outercover and liner will merely be bonded together as illustrated in Fig. 3. </p>
|
| 899 |
+
<p id="p-90" num="90">
|
| 900 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 901 |
+
[065] In some embodiments, the method of exposing an internally positioned conductive material to an external surface of an absorbent article includes providing an outercover and at least one conductive material in facing relation therewith. The method may further include directing one or more portions of the conductive material at least partially through the outercover to define one or more <boundary-data type="line-number">
|
| 902 |
+
<confidence value="86">30</confidence>
|
| 903 |
+
</boundary-data>
|
| 904 |
+
external contact points. The directing step may include the use of ultrasonic bonding, thermal bonding, pressure bonding, and the like. The method may further include the step of sealing the outercover about the external contact points <boundary-data type="header">
|
| 905 |
+
<confidence value="88">19</confidence>
|
| 906 |
+
</boundary-data>
|
| 907 |
+
<page-break num="20"/>
|
| 908 |
+
K-C 64129991US01 to maintain the liquid impermeability of the outercover. The method may further include providing a liner in facing relation with the outercover such that the conductive material is located between the outercover and the liner and the external contact points are exposed to an outer article surface. </p>
|
| 909 |
+
<p id="p-91" num="91">
|
| 910 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 911 |
+
[066] In some embodiments, the method may include providing an interconnected web of absorbent articles having at least one conductive material located therein. The interconnected web of absorbent articles may be subjected to a bonding process wherein at least a portion of the conductive material is directed towards and/or exposed to the outer article surface or inner article surface <boundary-data type="line-number">
|
| 912 |
+
<confidence value="86">10</confidence>
|
| 913 |
+
</boundary-data>
|
| 914 |
+
to define external contact points. </p>
|
| 915 |
+
<p id="p-92" num="92">[067] In various embodiments, the bonding process may cause one or more materials to flow proximate the location of the bond. In some embodiments, this flowing of material may help to seal the perimeter about the external contact point.</p>
|
| 916 |
+
<p id="p-93" num="93">In some embodiments, the material sealing the perimeter of the external contact <boundary-data type="line-number">15 </boundary-data>
|
| 917 |
+
points may be liner material, adhesive, film, nonwoven, or combinations thereof. </p>
|
| 918 |
+
<p id="p-94" num="94">[068] In some embodiments, the method may further include directing at least a portion of the conductive material at least partially through a non-conductive material and sealing the non-conductive material about the external contact points.</p>
|
| 919 |
+
<p id="p-95" num="95">For example, an absorbent article may include a liquid impermeable backsheet <boundary-data type="line-number">20 </boundary-data>
|
| 920 |
+
and a liquid permeable liner positioned in facing relation. The absorbent article may further include a conductive material located between the backsheet and the liner wherein at least a portion of the conductive material extends at least partially through the backsheet to define external contact points. The backsheet may be sealed around the external contact points to retain liquid impermeability. </p>
|
| 921 |
+
<p id="p-96" num="96">
|
| 922 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 923 |
+
[069] In some embodiments, the method may further include directing at least a portion of the conductive material at least partially through a non-conductive material without rupturing the conductive material to define one or more external contact points. In other words, portions of the conductive material may extend, at least partially, through a non-conductive material and remain intact at the location <part-num-ref name="location">30</part-num-ref>
|
| 924 |
+
of the external contact points. </p>
|
| 925 |
+
<boundary-data type="header">
|
| 926 |
+
<confidence value="88">20</confidence>
|
| 927 |
+
</boundary-data>
|
| 928 |
+
<p id="p-97" num="97">
|
| 929 |
+
<page-break num="21"/>
|
| 930 |
+
[070] In some embodiments, the method may include directing at least a portion of the conductive material at least partially through a non-conductive material that is liquid impervious to define one or more external contact points without rupturing the conductive material. The method may further include sealing the non- <boundary-data type="line-number">
|
| 931 |
+
<confidence value="5">5</confidence>
|
| 932 |
+
</boundary-data>
|
| 933 |
+
conductive material around the external contact points thereby maintaining the liquid impermeability. </p>
|
| 934 |
+
<p id="p-98" num="98">[071] In some embodiments, the method may include providing a conductive material laminated with a masking material wherein the conductive material is oriented towards the outercover and the masking material is oriented towards the <boundary-data type="line-number">
|
| 935 |
+
<confidence value="86">10</confidence>
|
| 936 |
+
</boundary-data>
|
| 937 |
+
liner such that the conductive element is less visible from the liner side. </p>
|
| 938 |
+
<p id="p-99" num="99">[072] Any suitable bonding process may be used to extend and/or expose portions of the conductive material through non-conductive layers. In various embodiments, the bonding process may include ultrasonic bonding, thermal bonding, pressure bonding, and the like, and combinations thereof. In various <boundary-data type="line-number">
|
| 939 |
+
<confidence value="66">15</confidence>
|
| 940 |
+
</boundary-data>
|
| 941 |
+
embodiments, the bonding process may bond the liner to the backsheet in areas not including the conductive material. For example, the bonding process may include ultrasonic bonding using a plunge bonder available from Dukane Intelligent Assembly Solutions having offices at <part-num-ref name="plunge bonder available from Dukane Intelligent Assembly Solutions having offices at">2900</part-num-ref>
|
| 942 |
+
Dukane Drive, St. Charles, IL, <part-num-ref name="Dukane Drive, St. Charles, IL,">60174,</part-num-ref>
|
| 943 |
+
</p>
|
| 944 |
+
<heading id="h-7">USA.</heading>
|
| 945 |
+
<p id="p-100" num="100">
|
| 946 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 947 |
+
[073] In various embodiments, the pressure on the bonder may be varied from <part-num-ref name="bonder may be varied from">20</part-num-ref>
|
| 948 |
+
to <part-num-ref name="to">90</part-num-ref>
|
| 949 |
+
pounds per square inch (psi) and the power levels may be varied from <part-num-ref name="power levels may be varied from">0</part-num-ref>
|
| 950 |
+
Joules to <part-num-ref name="Joules to">100</part-num-ref>
|
| 951 |
+
Joules. In various embodiments, bond times may range from 0.1 to 1.0 seconds. Any suitable anvil pattern may be utilized. In some embodiments, the bonder may be a rotary bonder. </p>
|
| 952 |
+
<p id="p-101" num="101">
|
| 953 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 954 |
+
[074] In specific embodiments, suitable bonds were achieved at 50 psi, a power level of 50-60 Joules, and a bond time of 0.4 to 0.5 seconds. These bonds were created in diapers commercially available from Kimberly-Clark Corporation under the brand name HUGGIES<confidence value="2">@</confidence>
|
| 955 |
+
Disposable Diapers. The diapers were modified by inserting a conductor material between the backsheet and the absorbent structure. </p>
|
| 956 |
+
<p id="p-102" num="102">
|
| 957 |
+
<boundary-data type="line-number">
|
| 958 |
+
<confidence value="86">30</confidence>
|
| 959 |
+
</boundary-data>
|
| 960 |
+
The conductor material was a foil laminate having <part-num-ref name="foil laminate having">12</part-num-ref>
|
| 961 |
+
micron foil layer and a <part-num-ref name="">12</part-num-ref>
|
| 962 |
+
micron thick polyester backing. The conductor material is available under the brand name NEPTCO <part-num-ref name="brand name NEPTCO">1001</part-num-ref>
|
| 963 |
+
laminated foil. Fig. 9 is an optical surface image of <boundary-data type="header">
|
| 964 |
+
<confidence value="88">21</confidence>
|
| 965 |
+
</boundary-data>
|
| 966 |
+
<page-break num="22"/>
|
| 967 |
+
exemplary external contact points <part-num-ref name="optical surface image of exemplary external contact points">122</part-num-ref>
|
| 968 |
+
exposed through the outercover <part-num-ref name="outercover">40.</part-num-ref>
|
| 969 |
+
The optical surface image was obtained by using a WILD MAKROSCOP M420 stereo microscope equipped with sub-stage transmitted illumination and a ZEISS AXIOCAM color video camera. The stereo microscope's lens system was set to <boundary-data type="line-number">5 </boundary-data>
|
| 970 |
+
8X magnification and incident lighting was provided by goose-neck fiber optics with a CUDA <confidence value="5">1</confidence>
|
| 971 |
+
-150 light source. </p>
|
| 972 |
+
<p id="p-103" num="103">[075] Referring to Fig. 9, a series of external contact points <part-num-ref name="series of external contact points">122</part-num-ref>
|
| 973 |
+
are exposed through the outercover <part-num-ref name="outercover">40.</part-num-ref>
|
| 974 |
+
The external contact points <part-num-ref name="external contact points">122</part-num-ref>
|
| 975 |
+
are intact and are available for contact with a signaling device. The external contact points <part-num-ref name="external contact points">122</part-num-ref>
|
| 976 |
+
<boundary-data type="line-number">
|
| 977 |
+
<confidence value="66">10</confidence>
|
| 978 |
+
</boundary-data>
|
| 979 |
+
define contact point perimeters <part-num-ref name="define contact point perimeters">126</part-num-ref>
|
| 980 |
+
wherein the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 981 |
+
has been melted and sealed about the perimeter <part-num-ref name="perimeter">126</part-num-ref>
|
| 982 |
+
thereby maintaining the liquid impermeability of the outercover <part-num-ref name="outercover">40</part-num-ref>
|
| 983 |
+
as a whole. </p>
|
| 984 |
+
<p id="p-104" num="104">[076] While the invention has been described in detail with respect to specific embodiments thereof, it will be appreciated that those skilled in the art, upon <boundary-data type="line-number">15 </boundary-data>
|
| 985 |
+
attaining understanding of the foregoing will readily appreciate alterations to, variations of, and equivalents to these embodiments. Accordingly, the scope of the present invention should be assessed as that of the appended claims and any equivalents thereto. Additionally, all combinations and/or sub-combinations of the disclosed embodiments, ranges, examples, and alternatives are also <part-num-ref name="disclosed embodiments, ranges, examples, and alternatives are also">20</part-num-ref>
|
| 986 |
+
contemplated. </p>
|
| 987 |
+
<boundary-data type="header">
|
| 988 |
+
<confidence value="88">22</confidence>
|
| 989 |
+
</boundary-data>
|
| 990 |
+
</description>
|
| 991 |
+
</us-patent-application>
|
| 992 |
+
|
applicant/11731977.xml
ADDED
|
@@ -0,0 +1,394 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11731977</doc-number>
|
| 8 |
+
<date>2007-04-02</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">
|
| 14 |
+
<confidence value="88">PD</confidence>
|
| 15 |
+
-20701<confidence value="8">0</confidence>
|
| 16 |
+
</boundary-data>
|
| 17 |
+
<heading id="h-1">METHOD AND SYSTEM OF RETRIEVING PRIOR BROADCASTED</heading>
|
| 18 |
+
<heading id="h-2">PROGRAMMING AT A USER DEVICE FROM A SERVICE PROVIDER</heading>
|
| 19 |
+
<p id="p-1" num="1">Robert G. Arsenault Xavier D. Riley <page-break num="2"/>
|
| 20 |
+
<boundary-data type="header">PD-20701<confidence value="8">0</confidence>
|
| 21 |
+
</boundary-data>
|
| 22 |
+
</p>
|
| 23 |
+
<heading id="h-3">METHOD AND SYSTEM OF RETRIEVING PRIOR BROADCASTED</heading>
|
| 24 |
+
<heading id="h-4">PROGRAMMING AT A USER DEVICE FROM A SERVICE PROVIDER</heading>
|
| 25 |
+
<heading id="h-5">TECHNICAL FIELD</heading>
|
| 26 |
+
<p id="p-2" num="2">[0001] The present disclosure relates generally to communicating content to a user and, more specifically, to communicating prior broadcasted programs or content to a user device.</p>
|
| 27 |
+
<heading id="h-6">BACKGROUND</heading>
|
| 28 |
+
<p id="p-3" num="3">[0002] The statements in this section merely provide background information related to the present disclosure and may not constitute prior art.</p>
|
| 29 |
+
<p id="p-4" num="4">[0003] Consumers increasingly desire access to various types of content, including music, videos, games, and the like. To meet these needs, content providers are increasingly investigating ways to provide content in a timely manner to consumers.</p>
|
| 30 |
+
<p id="p-5" num="5">[0004] Satellite distribution systems are one way in which to provide content to various consumers. Pay-per-view and regular broadcasts are available in a satellite system. In a pay-per-view system, access is provided to users for a particular program that is watched by more than one user at the same time. Recording devices in the user devices may be used to store the content for later playback.</p>
|
| 31 |
+
<p id="p-6" num="6">[0005] In certain situations, a user may desire access to content not available during a regular broadcast or one that is stored within the user device. For example, the user may learn of a broadcasted program of interest without a means to view the past program. Further, providing the user with a program on an individual basis, consumes valuable satellite resources. Therefore, it may be desirable to provide other means for distributing content when needed to various customers.</p>
|
| 32 |
+
<boundary-data type="header">
|
| 33 |
+
<confidence value="8">1</confidence>
|
| 34 |
+
</boundary-data>
|
| 35 |
+
<boundary-data type="header">PD-207010</boundary-data>
|
| 36 |
+
<heading id="h-7">SUMMARY</heading>
|
| 37 |
+
<p id="p-7" num="7">
|
| 38 |
+
<page-break num="3"/>
|
| 39 |
+
<confidence value="5">[</confidence>
|
| 40 |
+
0006] The present disclosure sets forth a method for utilizing a terrestrial communication network for providing requested content to a user device. The requested content may be retrieved from a content repository that stores certain broadcasted material for a predetermined amount of time. The material may be requested by the user and sent to the user device. In the case of a satellite content distribution system, another network such as a broadband network may be used to provide the requested content to the user device or set top box. This method reduces the burden on the satellite system although the satellite may be used in certain situations. </p>
|
| 41 |
+
<p id="p-8" num="8">[0007] In one aspect of the disclosure, a method of operating a communication system includes coupling the user device to a network and generating a program guide for programming including currently broadcasting programs and past programming. The programming guide includes program guide elements. The method also includes selecting a first program guide element from the past programming to form a selection signal, communicating the selection signal to a service provider, retrieving a program corresponding to the selection from a content repository associated with the service provider and communicating the program to a user device through the network.</p>
|
| 42 |
+
<p id="p-9" num="9">[0008] In a further aspect of the disclosure, a method of operating a communication system includes coupling the user device to a terrestrial network and a satellite and generating program guide for programming including currently broadcasting programs and past programming. The programming guide includes program guide elements. The method also includes communicating the program guide through the satellite, selecting a program guide element from the past programming to form a selection signal, communicating the selection signal to a service provider through the terrestrial network, retrieving a program corresponding to the selection from a content <boundary-data type="header">
|
| 43 |
+
<confidence value="8">2</confidence>
|
| 44 |
+
</boundary-data>
|
| 45 |
+
<page-break num="4"/>
|
| 46 |
+
<boundary-data type="header">PD-207010</boundary-data>
|
| 47 |
+
repository associated with the service provider, and communicating the program to a user device. </p>
|
| 48 |
+
<p id="p-10" num="10">[0009] In a further aspect of the disclosure, a communication system includes a network, a user device in communication with the network and a service provider communicating with the user device through the network. The service provider generates a program guide for programming including currently broadcasting programs and past programming. The programming guide includes program guide elements. The user device selects a program guide element from the past programming to form a selection signal and communicating the selection signal to a service provider. The service provider retrieves a program corresponding to the selection from a content repository associated with the service provider and communicates the program to a user device through the network.</p>
|
| 49 |
+
<p id="p-11" num="11">[0010] Further areas of applicability will become apparent from the description provided herein. It should be understood that the description and specific examples are intended for purposes of illustration only and are not intended to limit the scope of the present disclosure.</p>
|
| 50 |
+
<heading id="h-8">DRAWINGS</heading>
|
| 51 |
+
<p id="p-12" num="12">[0011] The drawings described herein are for illustration purposes only and are not intended to limit the scope of the present disclosure in any way.</p>
|
| 52 |
+
<p id="p-13" num="13">[0012] FIG. 1 is a block diagrammatic system view of a communication system according to the present disclosure.</p>
|
| 53 |
+
<p id="p-14" num="14">[0013] FIG. 2 is a representation of a program guide user interface on a display associated with the user device.</p>
|
| 54 |
+
<boundary-data type="header">
|
| 55 |
+
<confidence value="8">3</confidence>
|
| 56 |
+
</boundary-data>
|
| 57 |
+
<boundary-data type="header">PD-2070<confidence value="88">10</confidence>
|
| 58 |
+
</boundary-data>
|
| 59 |
+
<p id="p-15" num="15">
|
| 60 |
+
<page-break num="5"/>
|
| 61 |
+
[0014] FIG. 3 is a screen display of a user interface for confirming a requested program. </p>
|
| 62 |
+
<p id="p-16" num="16">[0015] FIG. 4 is a block diagrammatic view for selecting a past program from the user device perspective.</p>
|
| 63 |
+
<p id="p-17" num="17">[0016] FIG. 5 is a flowchart of the method for selecting a past program from the service provider perspective.</p>
|
| 64 |
+
<heading id="h-9">DETAILED DESCRIPTION</heading>
|
| 65 |
+
<p id="p-18" num="18">[0017] The following description is merely exemplary in nature and is not intended to limit the present disclosure, application, or uses. For purposes of clarity, the same reference numbers will be used in the drawings to identify similar elements. As used herein, the term module refers to an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality. As used herein, the phrase at least one of A, B, and C should be construed to mean a logical (A or B or C), using a non-exclusive logical or. It should be understood that steps within a method may be executed in different order without altering the principles of the present disclosure.</p>
|
| 66 |
+
<p id="p-19" num="19">[0018] While the following disclosure is made with respect to example <confidence value="8">D</confidence>
|
| 67 |
+
IRECTV<confidence value="4">®</confidence>
|
| 68 |
+
broadcast services and systems, it should be understood that many other delivery systems are readily applicable to disclosed systems and methods. Such systems include wireless terrestrial distribution systems, wired or cable distribution systems, cable television distribution systems, Ultra High Frequency (U<confidence value="5885">HF)/</confidence>
|
| 69 |
+
Very High Frequency (VHF) radio frequency systems or other terrestrial broadcast systems (e.g., Multi-channel Multi-point Distribution System (MMDS), Local Multi-point Distribution System <boundary-data type="header">
|
| 70 |
+
<confidence value="8">4</confidence>
|
| 71 |
+
</boundary-data>
|
| 72 |
+
<page-break num="6"/>
|
| 73 |
+
<boundary-data type="header">PD-207010</boundary-data>
|
| 74 |
+
(LMDS), etc.), Internet-based distribution systems, cellular distribution systems, power- line broadcast systems, any point-to-point and/or multicast Internet Protocol (<confidence value="5">I</confidence>
|
| 75 |
+
P) delivery network, and fiber optic networks. Further, the different functions collectively allocated among a service provider and integrated receiver/decoders (IRDs) as described below can be reallocated as desired without departing from the intended scope of the present patent. </p>
|
| 76 |
+
<p id="p-20" num="20">[0019] Further, while the following disclosure is made with respect to the delivery of content (e.g., television (TV), movies, games, music videos, etc.), it should be understood that the systems and methods disclosed herein could also be used for delivery of any media content type, for example, audio, music, data files, web pages, games, etc.</p>
|
| 77 |
+
<p id="p-21" num="21">Additionally, throughout this disclosure reference is made to data, information, programs, movies, assets, video data, etc., however, it will be readily apparent to persons of ordinary skill in the art that these terms are substantially equivalent in reference to the example systems and/or methods disclosed herein. As used herein, the term title or program will be used to refer to, for example, a media content type such as a movie itself and not the name of the movie.</p>
|
| 78 |
+
<p id="p-22" num="22">[0020] Referring now to Fig. 1, a communication system <part-num-ref name="communication system">10</part-num-ref>
|
| 79 |
+
includes a service provider <part-num-ref name="service provider">12</part-num-ref>
|
| 80 |
+
that communicates content to user devices <part-num-ref name="that communicates content to user devices">14.</part-num-ref>
|
| 81 |
+
The service provider <part-num-ref name="service provider">12</part-num-ref>
|
| 82 |
+
may include a controller <part-num-ref name="controller">16</part-num-ref>
|
| 83 |
+
that is used to control the overall operation of the system. The controller <part-num-ref name="controller">16</part-num-ref>
|
| 84 |
+
and some of the associated modules and components may be referred to as a head end. A satellite uplink module <part-num-ref name="satellite uplink module">18</part-num-ref>
|
| 85 |
+
is used to generate and communicate uplink signals <part-num-ref name="is used to generate and communicate uplink signals">20</part-num-ref>
|
| 86 |
+
to satellite <part-num-ref name="to satellite">22.</part-num-ref>
|
| 87 |
+
Satellite <part-num-ref name="to satellite 22. Satellite">22</part-num-ref>
|
| 88 |
+
generates downlink signals <part-num-ref name="generates downlink signals">24</part-num-ref>
|
| 89 |
+
to one or more user devices <part-num-ref name="to one or more user devices">14.</part-num-ref>
|
| 90 |
+
An antenna <part-num-ref name="antenna">26</part-num-ref>
|
| 91 |
+
associated with the satellite uplink module <part-num-ref name="satellite uplink module">18</part-num-ref>
|
| 92 |
+
is used to generate the uplink signals <part-num-ref name="uplink signals">20.</part-num-ref>
|
| 93 |
+
A downlink antenna <part-num-ref name="downlink antenna">28</part-num-ref>
|
| 94 |
+
associated with the user device <part-num-ref name="user device">14</part-num-ref>
|
| 95 |
+
is used to receive downlink signals. Various types of content or program signals and security information signals, but not limited to security information, encryption- <boundary-data type="header">
|
| 96 |
+
<confidence value="8">5</confidence>
|
| 97 |
+
</boundary-data>
|
| 98 |
+
<page-break num="7"/>
|
| 99 |
+
<boundary-data type="header">PD-20701<confidence value="8">0</confidence>
|
| 100 |
+
</boundary-data>
|
| 101 |
+
decryption information, digital rights management information, conditional access packets (CAPs), channel or content access lists or rights may be communicated through the communication system <part-num-ref name="communication system">10.</part-num-ref>
|
| 102 |
+
It should also be noted that various content may be encrypted based upon a control word (CW) known to the service provider and/or the various user devices. Control word packets (CWPs) may include, among other things, a time stamp and the control word that is used to compute a cryptographic hash of the contents. The control word packets may, from time to time, be transmitted from the service provider through the satellite to the user devices. </p>
|
| 103 |
+
<p id="p-23" num="23">[0021] The service provider <part-num-ref name="service provider">12</part-num-ref>
|
| 104 |
+
may also include a subscriber transaction management system <part-num-ref name="subscriber transaction management system">40.</part-num-ref>
|
| 105 |
+
The subscriber transaction management system (STMS) <part-num-ref name="subscriber transaction management system (STMS)">40</part-num-ref>
|
| 106 |
+
has the function of a billing system. The STMS <part-num-ref name="STMS">40</part-num-ref>
|
| 107 |
+
keeps track of various transactions and the services to which the various user devices are subscribed to. Billing information and enabling access to a system may be provided through the subscriber transaction management system. Transactions such as requested content may be billed by the system. </p>
|
| 108 |
+
<p id="p-24" num="24">[0022] A conditional access system <part-num-ref name="conditional access system">42</part-num-ref>
|
| 109 |
+
may also be coupled to controller <part-num-ref name="may also be coupled to controller">16.</part-num-ref>
|
| 110 |
+
</p>
|
| 111 |
+
<p id="p-25" num="25">The conditional access system 42 generates conditional access packets that may be provided through the satellite or through other communication networks to the user devices <part-num-ref name="user devices">14.</part-num-ref>
|
| 112 |
+
The conditional access system <part-num-ref name="conditional access system">42</part-num-ref>
|
| 113 |
+
may, for example, generate the CAP<confidence value="5">s</confidence>
|
| 114 |
+
described above. </p>
|
| 115 |
+
<p id="p-26" num="26">[0023] A content distribution network <part-num-ref name="content distribution network">44</part-num-ref>
|
| 116 |
+
may also be coupled to controller <part-num-ref name="may also be coupled to controller">16.</part-num-ref>
|
| 117 |
+
The content distribution network <part-num-ref name="content distribution network">44</part-num-ref>
|
| 118 |
+
in conjunction with a content repository <part-num-ref name="content repository">46</part-num-ref>
|
| 119 |
+
may be used to provide content through the satellite and through the various other networks. </p>
|
| 120 |
+
<p id="p-27" num="27">The content distribution network 44, although illustrated entirely within the service provider, may also be outside or partially outside the service provider <part-num-ref name="service provider">12.</part-num-ref>
|
| 121 |
+
That is, user <boundary-data type="header">
|
| 122 |
+
<confidence value="8">6</confidence>
|
| 123 |
+
</boundary-data>
|
| 124 |
+
<page-break num="8"/>
|
| 125 |
+
<boundary-data type="header">PD-207010</boundary-data>
|
| 126 |
+
devices <part-num-ref name="service provider 12. That is, user devices">14</part-num-ref>
|
| 127 |
+
may be provided access to content from various sources directly once authorized by the service provider. A pay television service may provide content to a user device directly once all the security safeguards have been met. The content repository <part-num-ref name="content repository">46</part-num-ref>
|
| 128 |
+
may be used to generate the current broadcast programming and may also be used to store previously broadcast programming. The previously broadcast programming may be from all channels, selected channels, or popular broadcasts as will be determined below. </p>
|
| 129 |
+
<p id="p-28" num="28">[0024] A website or server <part-num-ref name="website or server">48</part-num-ref>
|
| 130 |
+
may also be coupled to the controller <part-num-ref name="controller">16.</part-num-ref>
|
| 131 |
+
The website <part-num-ref name="website">48</part-num-ref>
|
| 132 |
+
may provide the user devices <part-num-ref name="user devices">14</part-num-ref>
|
| 133 |
+
a way in which to select past programming content for downloading. The use of the various components within the service provider <part-num-ref name="service provider">12</part-num-ref>
|
| 134 |
+
will become evident in the description below. </p>
|
| 135 |
+
<p id="p-29" num="29">[0025] The conditional access system <part-num-ref name="conditional access system">42,</part-num-ref>
|
| 136 |
+
the content distribution network <part-num-ref name="content distribution network">44,</part-num-ref>
|
| 137 |
+
and the website <part-num-ref name="website">48</part-num-ref>
|
| 138 |
+
may all be coupled to the Internet <part-num-ref name="Internet">50.</part-num-ref>
|
| 139 |
+
The Internet <part-num-ref name="Internet">50</part-num-ref>
|
| 140 |
+
may be reached through various types of networks, including, but not limited to, a wireless network, a broadband network, a broadband wireless network, a WiFi network, a WiMax network and an optical fiber network. </p>
|
| 141 |
+
<p id="p-30" num="30">[0026] A telephone system <part-num-ref name="telephone system">52</part-num-ref>
|
| 142 |
+
may also be used to communicate between the user device <part-num-ref name="user device">14</part-num-ref>
|
| 143 |
+
and the service provider <part-num-ref name="service provider">12.</part-num-ref>
|
| 144 |
+
The telephone system <part-num-ref name="telephone system">52</part-num-ref>
|
| 145 |
+
may include a cellular system that is for the most part wireless or a public switched telephone network </p>
|
| 146 |
+
<heading id="h-10">(<confidence value="222288">PSTN).</confidence>
|
| 147 |
+
</heading>
|
| 148 |
+
<p id="p-31" num="31">[0027] One example of a user device <part-num-ref name="user device">14</part-num-ref>
|
| 149 |
+
includes a fixed user device such as a set top box <part-num-ref name="set top box">60.</part-num-ref>
|
| 150 |
+
The set top box <part-num-ref name="set top box">60</part-num-ref>
|
| 151 |
+
may have various components such as a controller <part-num-ref name="controller">62</part-num-ref>
|
| 152 |
+
that is used to control the operation of the system and generate and provide the content to the display device <part-num-ref name="display device">64</part-num-ref>
|
| 153 |
+
such as a television. The set top box <part-num-ref name="set top box">60</part-num-ref>
|
| 154 |
+
may also be referred to as integrated receiver decoder (IRD). The set top box <part-num-ref name="set top box">60</part-num-ref>
|
| 155 |
+
may decode, decompress, <boundary-data type="header">
|
| 156 |
+
<confidence value="8">7</confidence>
|
| 157 |
+
</boundary-data>
|
| 158 |
+
<page-break num="9"/>
|
| 159 |
+
<boundary-data type="header">PD-207010</boundary-data>
|
| 160 |
+
depacketize, and demultiplex the content received from the satellite <part-num-ref name="satellite">22.</part-num-ref>
|
| 161 |
+
Also, any content received from the Internet <part-num-ref name="Internet">50</part-num-ref>
|
| 162 |
+
may also be decoded, demultiplexed, decompressed and depacketized, if needed. Output drivers, contained within the controller <part-num-ref name="controller">62,</part-num-ref>
|
| 163 |
+
may be used to control the audio and visual function of the display <part-num-ref name="display">64.</part-num-ref>
|
| 164 |
+
</p>
|
| 165 |
+
<p id="p-32" num="32">[0028] The set top box <part-num-ref name="set top box">60</part-num-ref>
|
| 166 |
+
may also include a memory <part-num-ref name="memory">66.</part-num-ref>
|
| 167 |
+
The memory <part-num-ref name="memory">66</part-num-ref>
|
| 168 |
+
may, for example, be a digital video recorder (DVR) such as a hard disk drive. The memory <part-num-ref name="memory">66</part-num-ref>
|
| 169 |
+
may also be various other types of memory including flash memory. The memory <part-num-ref name="memory">66</part-num-ref>
|
| 170 |
+
may be used to store content or programs received from the service provider <part-num-ref name="service provider">12</part-num-ref>
|
| 171 |
+
through the satellite <part-num-ref name="satellite">22</part-num-ref>
|
| 172 |
+
or through the Internet <part-num-ref name="Internet">50.</part-num-ref>
|
| 173 |
+
</p>
|
| 174 |
+
<p id="p-33" num="33">[0029] The user device <part-num-ref name="user device">14</part-num-ref>
|
| 175 |
+
associated with the set top box <part-num-ref name="set top box">60</part-num-ref>
|
| 176 |
+
may also include or be associated with a personal computer <part-num-ref name="personal computer">70.</part-num-ref>
|
| 177 |
+
The personal computer <part-num-ref name="personal computer">70</part-num-ref>
|
| 178 |
+
may be used to provide Internet access for the set top box <part-num-ref name="set top box">60</part-num-ref>
|
| 179 |
+
so that various content may be downloaded from the Internet <part-num-ref name="Internet">50</part-num-ref>
|
| 180 |
+
and from the service provider <part-num-ref name="service provider">12.</part-num-ref>
|
| 181 |
+
More specifically, content from the content repository <part-num-ref name="content repository">46</part-num-ref>
|
| 182 |
+
may be provided through the content distribution network <part-num-ref name="content distribution network">44</part-num-ref>
|
| 183 |
+
through the Internet <part-num-ref name="Internet">50</part-num-ref>
|
| 184 |
+
and stored on the memory <part-num-ref name="memory">66</part-num-ref>
|
| 185 |
+
of the set top box <part-num-ref name="set top box">60.</part-num-ref>
|
| 186 |
+
The personal computer <part-num-ref name="personal computer">70</part-num-ref>
|
| 187 |
+
may be used to form the network between the set top box <part-num-ref name="set top box">60</part-num-ref>
|
| 188 |
+
and the Internet <part-num-ref name="Internet">50.</part-num-ref>
|
| 189 |
+
The connection between the personal computer <part-num-ref name="personal computer">70</part-num-ref>
|
| 190 |
+
and the set top box <part-num-ref name="set top box">60</part-num-ref>
|
| 191 |
+
may be a wired or wireless connection. Of course, if the connection is a wireless connection, a wireless LAN and thus a wireless router may be associated or included within the personal computer <part-num-ref name="personal computer">70.</part-num-ref>
|
| 192 |
+
An antenna <part-num-ref name="antenna">74</part-num-ref>
|
| 193 |
+
on the PC <part-num-ref name="PC">70</part-num-ref>
|
| 194 |
+
represents a potential wireless connection to antenna <part-num-ref name="potential wireless connection to antenna">76</part-num-ref>
|
| 195 |
+
on the set top box <part-num-ref name="set top box">60.</part-num-ref>
|
| 196 |
+
The antenna <part-num-ref name="antenna">76</part-num-ref>
|
| 197 |
+
on the set top box <part-num-ref name="set top box">60</part-num-ref>
|
| 198 |
+
may also communicate to an outside wireless router, such as in a WiMax or WiFi system. </p>
|
| 199 |
+
<p id="p-34" num="34">[0030] A gateway <part-num-ref name="gateway">78</part-num-ref>
|
| 200 |
+
may be used to form access to the Internet in a WiFi or WiMax system through antenna <part-num-ref name="WiFi or WiMax system through antenna">79.</part-num-ref>
|
| 201 |
+
A telephone <part-num-ref name="telephone">72</part-num-ref>
|
| 202 |
+
may also be used to communicate with the service provider <part-num-ref name="service provider">12.</part-num-ref>
|
| 203 |
+
The telephone <part-num-ref name="telephone">72</part-num-ref>
|
| 204 |
+
may be used to initiate the past <boundary-data type="header">
|
| 205 |
+
<confidence value="8">8</confidence>
|
| 206 |
+
</boundary-data>
|
| 207 |
+
<page-break num="10"/>
|
| 208 |
+
<boundary-data type="header">PD-20701<confidence value="8">0</confidence>
|
| 209 |
+
</boundary-data>
|
| 210 |
+
programming download service by the user who communicates directly with an operator or a menu system at the service provider <part-num-ref name="service provider">12.</part-num-ref>
|
| 211 |
+
Part of the information received from the satellite <part-num-ref name="satellite">22</part-num-ref>
|
| 212 |
+
may include a program guide that includes various selections of past programming therein. </p>
|
| 213 |
+
<p id="p-35" num="35">[0031] The user devices <part-num-ref name="user devices">14</part-num-ref>
|
| 214 |
+
may also include mobile user devices <part-num-ref name="may also include mobile user devices">80.</part-num-ref>
|
| 215 |
+
The mobile user devices <part-num-ref name="mobile user devices">80</part-num-ref>
|
| 216 |
+
may include the functionality described above with respect to the set top box <part-num-ref name="set top box">60</part-num-ref>
|
| 217 |
+
such as a controller, a memory, an antenna <part-num-ref name="antenna">81</part-num-ref>
|
| 218 |
+
for communicating with the satellite and communicating through the wireless network. Although one antenna is shown, more than one may be used to receive the wireless network signals and the satellite signals. The antenna <part-num-ref name="antenna">81</part-num-ref>
|
| 219 |
+
is shown generally. The antenna may be incorporated within each device. However, mobile devices may communicate wirelessly through the Internet <part-num-ref name="Internet">50,</part-num-ref>
|
| 220 |
+
through a telephone system <part-num-ref name="telephone system">52,</part-num-ref>
|
| 221 |
+
such as a cellular system, through the Internet, a WiFi, WiMax, other type of wireless systems or more than one wireless system. The wireless communications may communicate content or programs as well as provide callbacks from the mobile user devices <part-num-ref name="mobile user devices">80</part-num-ref>
|
| 222 |
+
to the service provider <part-num-ref name="service provider">12.</part-num-ref>
|
| 223 |
+
The call backs may include a request for content. Confirmation signals may also use the Internet <part-num-ref name="Internet">50</part-num-ref>
|
| 224 |
+
or the telephone system <part-num-ref name="telephone system">52</part-num-ref>
|
| 225 |
+
as will be further described below. It should also be noted that a different network may be used to communicate program content and other communications between the service provider <part-num-ref name="service provider">12</part-num-ref>
|
| 226 |
+
and the user devices <part-num-ref name="user devices">14</part-num-ref>
|
| 227 |
+
including the mobile user devices <part-num-ref name="mobile user devices">80.</part-num-ref>
|
| 228 |
+
</p>
|
| 229 |
+
<p id="p-36" num="36">[0032] The mobile user devices <part-num-ref name="mobile user devices">80</part-num-ref>
|
| 230 |
+
may include many different devices, including a laptop computer <part-num-ref name="laptop computer">82,</part-num-ref>
|
| 231 |
+
a portable media player <part-num-ref name="portable media player">84,</part-num-ref>
|
| 232 |
+
a vehicle such as an automotive vehicle that includes a mobile set top box <part-num-ref name="mobile set top box">88</part-num-ref>
|
| 233 |
+
and a cell phone <part-num-ref name="cell phone">90.</part-num-ref>
|
| 234 |
+
The cell phone <part-num-ref name="cell phone">90</part-num-ref>
|
| 235 |
+
may include such devices as a personal digital assistant. It is important that all <boundary-data type="header">
|
| 236 |
+
<confidence value="8">9</confidence>
|
| 237 |
+
</boundary-data>
|
| 238 |
+
<page-break num="11"/>
|
| 239 |
+
<boundary-data type="header">PD-207010</boundary-data>
|
| 240 |
+
of the mobile user devices <part-num-ref name="mobile user devices">80</part-num-ref>
|
| 241 |
+
include some form of wireless communication system to receive content from the service provider <part-num-ref name="service provider">12.</part-num-ref>
|
| 242 |
+
</p>
|
| 243 |
+
<p id="p-37" num="37">[0033] The service provider <part-num-ref name="service provider">12</part-num-ref>
|
| 244 |
+
may include a program guide module <part-num-ref name="program guide module">92.</part-num-ref>
|
| 245 |
+
The program guide module <part-num-ref name="program guide module">92</part-num-ref>
|
| 246 |
+
is used to determine the contents of a program guide. The program guide module <part-num-ref name="program guide module">92</part-num-ref>
|
| 247 |
+
provides the user devices <part-num-ref name="user devices">14</part-num-ref>
|
| 248 |
+
with information regarding current and future programming. This is the typical function of the program guide modules in the <confidence value="86">DI</confidence>
|
| 249 |
+
RECTV<confidence value="4">®</confidence>
|
| 250 |
+
system. Information in the program guide include channels, programming information, times, titles, previews, and the like. A content or material identification (ID) such as a number or an alpha-numeric identifier may be used to identify the particular program. The content ID may correspond to <confidence value="5">I</confidence>
|
| 251 |
+
Ds of content stored in the content repository. The program guide module <part-num-ref name="program guide module">92,</part-num-ref>
|
| 252 |
+
in the present disclosure, also provides information to the user devices relative to past programming that is available from the service provider. The past programming is stored within the content repository <part-num-ref name="content repository">46.</part-num-ref>
|
| 253 |
+
The past programming may include all the programming broadcast within the last certain amount of time. The certain amount of time may be two weeks, a month, a week, a few days, or the like. All of the broadcasted programs for all of the channels may be made available. However, only certain numbers of channels may have their information stored. </p>
|
| 254 |
+
<p id="p-38" num="38">Also, portions of the channels or popular portions of the channels may be stored without the entire day's worth of programming for a particular channel. The program guide module <part-num-ref name="program guide module">92,</part-num-ref>
|
| 255 |
+
through the guidance of the controller <part-num-ref name="controller">16,</part-num-ref>
|
| 256 |
+
formulates the program guide and transmits the program guide information through the satellite <part-num-ref name="satellite">22</part-num-ref>
|
| 257 |
+
through the satellite uplink module <part-num-ref name="satellite uplink module">18</part-num-ref>
|
| 258 |
+
to the user devices <part-num-ref name="user devices">14.</part-num-ref>
|
| 259 |
+
Updates to the program guide may also be broadcast. The program guide module <part-num-ref name="program guide module">92</part-num-ref>
|
| 260 |
+
may consist of packetized information that is spaced from time to time throughout the broadcasted programming. </p>
|
| 261 |
+
<boundary-data type="header">
|
| 262 |
+
<confidence value="88">10</confidence>
|
| 263 |
+
</boundary-data>
|
| 264 |
+
<boundary-data type="header">PD-207010</boundary-data>
|
| 265 |
+
<p id="p-39" num="39">
|
| 266 |
+
<page-break num="12"/>
|
| 267 |
+
[0034] An audience measurement module <part-num-ref name="audience measurement module">94</part-num-ref>
|
| 268 |
+
coupled to the controller <part-num-ref name="controller">16</part-num-ref>
|
| 269 |
+
may also be provided within the service provider <part-num-ref name="service provider">12.</part-num-ref>
|
| 270 |
+
The audience measurement module <part-num-ref name="audience measurement module">94</part-num-ref>
|
| 271 |
+
may be used to measure the popularity of a particular program. Popularity information from the audience measurement module <part-num-ref name="audience measurement module">94</part-num-ref>
|
| 272 |
+
may be used to perform various functions including determining through which network a particular requested program may be broadcast. For example, if the audience measurement module determines that the particular program is being requested often, the satellite <part-num-ref name="satellite">22</part-num-ref>
|
| 273 |
+
may be used to broadcast a program to various users. If the audience measurement module <part-num-ref name="audience measurement module">94</part-num-ref>
|
| 274 |
+
determines the program is not very popular, the Internet or a broadband network may be used to distribute the program. </p>
|
| 275 |
+
<p id="p-40" num="40">[0035] The audience measurement module <part-num-ref name="audience measurement module">94</part-num-ref>
|
| 276 |
+
may receive information from the subscriber transaction management system <part-num-ref name="subscriber transaction management system">40</part-num-ref>
|
| 277 |
+
to count the number of times a particular program has been requested. The similar information may also be retrieved from the content repository <part-num-ref name="content repository">46</part-num-ref>
|
| 278 |
+
and the content distribution network <part-num-ref name="content distribution network">44</part-num-ref>
|
| 279 |
+
by counting the number of times the content has been transmitted. The actions and consequences of the audience measurement module will be evident below. </p>
|
| 280 |
+
<p id="p-41" num="41">[0036] Referring now to Fig. 2, a display <part-num-ref name="display">64</part-num-ref>
|
| 281 |
+
having a graphical user interface such as a program guide <part-num-ref name="program guide">120</part-num-ref>
|
| 282 |
+
is illustrated. The program guide includes channel identifiers <part-num-ref name="program guide includes channel identifiers">122</part-num-ref>
|
| 283 |
+
and programming elements <part-num-ref name="and programming elements">124.</part-num-ref>
|
| 284 |
+
The programming elements <part-num-ref name="programming elements">124,</part-num-ref>
|
| 285 |
+
not all of which are shown, may include various types of information including a title, rating, a brief description, the actors, and the like. As is illustrated, current broadcasting <part-num-ref name="like. As is illustrated, current broadcasting">126</part-num-ref>
|
| 286 |
+
is illustrated together with past programming <part-num-ref name="is illustrated together with past programming">128.</part-num-ref>
|
| 287 |
+
Determining past and current programming is relative to a particular point in time, e.g., the current time. As mentioned above, not all of the information for all of the programs may be available in the past programming portion <part-num-ref name="past programming portion">128.</part-num-ref>
|
| 288 |
+
A selection may be made by moving a screen cursor that <boundary-data type="header">
|
| 289 |
+
<confidence value="88">11</confidence>
|
| 290 |
+
</boundary-data>
|
| 291 |
+
<page-break num="13"/>
|
| 292 |
+
<boundary-data type="header">PD-20701<confidence value="8">0</confidence>
|
| 293 |
+
</boundary-data>
|
| 294 |
+
highlights various shows desired to be downloaded. For example, show A illustrated as element <part-num-ref name="illustrated as element">130</part-num-ref>
|
| 295 |
+
has a highlighted box. For a selection to take place, the user interacts by way of a remote control or buttons on the set top box to move to and select the desired element. It should also be noted that all of the past programming may not be displayed to the user. </p>
|
| 296 |
+
<p id="p-42" num="42">[0037] The program guide <part-num-ref name="program guide">120</part-num-ref>
|
| 297 |
+
and the elements <part-num-ref name="elements">124</part-num-ref>
|
| 298 |
+
therein may be scrolled by the user. For example, the program guide may be scrolled in the reverse direction (to the left in Fig. 2). Scrolling may take place corresponding to the time period for which the programming has been saved. That is, if two weeks of available past broadcasted programming is available and stored within the content repository, scrolling to the left may take place for only two weeks. It should be noted that various types of scrolling, including horizontal and vertical scrolling, may take place. </p>
|
| 299 |
+
<p id="p-43" num="43">[0038] Searching using a graphical user interface generated at the set top box may also take place by the user. For example, searching based on title, actor, key words in the title or description may take place in conjunction with the remote control or other user interface. After searching, a selection may be made. Selections may also be made at a website using a program guide.</p>
|
| 300 |
+
<p id="p-44" num="44">[0039] Referring now to Fig. 3, once a selection on display <part-num-ref name="selection on display">64</part-num-ref>
|
| 301 |
+
has taken place in Fig. 2, a confirmation screen <part-num-ref name="confirmation screen">140</part-num-ref>
|
| 302 |
+
may be displayed. The confirmation screen <part-num-ref name="confirmation screen">140</part-num-ref>
|
| 303 |
+
may generate a message <part-num-ref name="message">142</part-num-ref>
|
| 304 |
+
that includes a YES box <part-num-ref name="YES box">144</part-num-ref>
|
| 305 |
+
and a NO box <part-num-ref name="NO box">146.</part-num-ref>
|
| 306 |
+
The message may include that "YOU HAVE SELECTED SHOW A. THE FEE IS $X.<confidence value="5">0</confidence>
|
| 307 |
+
0. IS THIS CORRECT?" The user may then confirm the selections by selecting the YES box <part-num-ref name="YES box">144</part-num-ref>
|
| 308 |
+
which is bolded in Fig. 3. The YES box <part-num-ref name="YES box">144</part-num-ref>
|
| 309 |
+
may be selected by a push button on the remote or on the set top box itself. A confirmation signal is sent to the service provider to initiate the transfer of the program from the service provider to the user devices. </p>
|
| 310 |
+
<boundary-data type="header">
|
| 311 |
+
<confidence value="88">12</confidence>
|
| 312 |
+
</boundary-data>
|
| 313 |
+
<boundary-data type="header">PD-20701<confidence value="8">0</confidence>
|
| 314 |
+
</boundary-data>
|
| 315 |
+
<p id="p-45" num="45">
|
| 316 |
+
<page-break num="14"/>
|
| 317 |
+
[0040] Referring now to Fig. 4, a method of selecting a program from the perspective of the user is illustrated. In step <part-num-ref name="user is illustrated. In step">200,</part-num-ref>
|
| 318 |
+
the program guide is reviewed by the user. It should also be noted that step <part-num-ref name="user. It should also be noted that step">200</part-num-ref>
|
| 319 |
+
may be performed on the set top box or on a service provider website. That is, a user may logon to a user website and select a desired program from a program guide displayed on the selection. In this manner, remote access and control may be provided to the user. For example, if the user is at a workplace or another location having Internet access, the service provider website may be reached and logged into by the particular user. A selection may, therefore, be selected and communicated to the user device. In this manner, the particular program may be communicated to the user device so that it is available when the user returns to the device. </p>
|
| 320 |
+
<p id="p-46" num="46">As mentioned above, searching may also be used to find possible selections.</p>
|
| 321 |
+
<p id="p-47" num="47">[0041] In step 202, the program guide may be scrolled into past programming which is prior to the currently broadcasting program. The programming guide for past programming may be limited to only those available for downloading. Thus, the program guide on the website or on the display associated with the user device may be reduced in size. In step <part-num-ref name="user device may be reduced in size. In step">204,</part-num-ref>
|
| 322 |
+
a program from the past programming guide is selected to form a selection. As described in Fig. 2, the selection may be performed by using the remote or other user interface. In step <part-num-ref name="remote or other user interface. In step">208,</part-num-ref>
|
| 323 |
+
the program is retrieved that corresponds to the selection from a content repository. The selection may generate a content identifier that is used to select a corresponding program or content from the content repository. </p>
|
| 324 |
+
<p id="p-48" num="48">[0042] In step 210, a popularity rating of the program corresponding to the selection may be determined. As mentioned above, the audience measurement module <part-num-ref name="audience measurement module">94</part-num-ref>
|
| 325 |
+
of Fig. 1 may be used to determine the popularity rating of the particular program. In step <part-num-ref name="particular program. In step">212,</part-num-ref>
|
| 326 |
+
a means for communicating the program may be determined based upon the popularity rating. This was mentioned above in the description of Fig. 1. For example, a <boundary-data type="header">
|
| 327 |
+
<confidence value="88">13</confidence>
|
| 328 |
+
</boundary-data>
|
| 329 |
+
<page-break num="15"/>
|
| 330 |
+
<boundary-data type="header">PD-207010</boundary-data>
|
| 331 |
+
popular program may be communicated through the satellite while a less popular title may be communicated th<confidence value="8">r</confidence>
|
| 332 |
+
ough a terrestrial network. Both steps <part-num-ref name="terrestrial network. Both steps">210</part-num-ref>
|
| 333 |
+
and <part-num-ref name="and">212</part-num-ref>
|
| 334 |
+
are optional steps. </p>
|
| 335 |
+
<p id="p-49" num="49">[0043] In step 214, the program corresponding to the selection is communicated to the user device. As mentioned above, the program may be communicated through a different network than the selection signal is communicated.</p>
|
| 336 |
+
<p id="p-50" num="50">Although, both may use the same. The program may be communicated through a wireless network, a broadband network, a WiFi network, a WiMax network, a cellular network, a wireless broadband network, or th<confidence value="8">r</confidence>
|
| 337 |
+
ough a wired broadband network. A satellite network may also be used to communicate the program. In step <part-num-ref name="program. In step">216,</part-num-ref>
|
| 338 |
+
the selection is billed to the account associated with the user device. This may be performed at the subscriber transaction management system <part-num-ref name="subscriber transaction management system">40</part-num-ref>
|
| 339 |
+
illustrated in Fig. 1. </p>
|
| 340 |
+
<p id="p-51" num="51">[0044] In step 218, the program may be stored in the memory of the user device. In the case of a set top box, the program may be stored in a digital video recorder.</p>
|
| 341 |
+
<p id="p-52" num="52">The program may also be played back in real time as received. However, it is more likely that the program is played back from a memory in a commercial embodiment.</p>
|
| 342 |
+
<p id="p-53" num="53">[0045] In step 220, the program is played back on the user device. That is, depending on the type of program, the user device may be used to generate audio, audio and video, gaming control, or the like. The audio signals may be communicated through a speaker while the video signals are displayed on the display <part-num-ref name="display">64</part-num-ref>
|
| 343 |
+
illustrated in Fig. 1. </p>
|
| 344 |
+
<p id="p-54" num="54">[0046] Referring now to Fig. 5, a method of operating from the perspective of the service provider <part-num-ref name="service provider">12</part-num-ref>
|
| 345 |
+
is set forth. In step <part-num-ref name="is set forth. In step">250,</part-num-ref>
|
| 346 |
+
a program guide including current and past programming is communicated to one of the user devices <part-num-ref name="user devices">15.</part-num-ref>
|
| 347 |
+
The program guide may be formulated from information stored in the content repository <part-num-ref name="content repository">46</part-num-ref>
|
| 348 |
+
in Fig. 1. The program guide may be communicated through various means including satellite, <boundary-data type="header">
|
| 349 |
+
<confidence value="88">14</confidence>
|
| 350 |
+
</boundary-data>
|
| 351 |
+
<page-break num="16"/>
|
| 352 |
+
<boundary-data type="header">PD-2070<confidence value="88">10</confidence>
|
| 353 |
+
</boundary-data>
|
| 354 |
+
telephone, and various types of broadband and Internet connections. This connection may be wired or wireless and include a WiFi network, WiMax network, or the like. </p>
|
| 355 |
+
<p id="p-55" num="55">[0047] In step 252, programming is received from various sources including from DVDs, tapes, the satellite or optical fibers and are stored in the content repository <part-num-ref name="content repository">46.</part-num-ref>
|
| 356 |
+
In step <part-num-ref name="content repository 46. In step">254,</part-num-ref>
|
| 357 |
+
the programming is broadcast through the satellite <part-num-ref name="satellite">22.</part-num-ref>
|
| 358 |
+
In step <part-num-ref name="satellite 22. In step">256,</part-num-ref>
|
| 359 |
+
the broadcast programming is stored in the content repository. As mentioned above, the programming that is broadcast may be selectively stored in the content repository. That is, only popular programs or those deemed potentially popular may be stored. Also, programming from certain channels may not be stored at all. </p>
|
| 360 |
+
<p id="p-56" num="56">[0048] In step 258, stored broadcast programming may be deleted from the content repository. This may be under the control of the controller <part-num-ref name="controller">16.</part-num-ref>
|
| 361 |
+
The broadcast programming that is stored in the content repository may be date-stamped so that only a pre-determined amount of previously broadcast programming is retained or stored in the content repository. The date stamp may, for example, be the time and date of the broadcast. For example, a two-week retention window may be used by the content repository <part-num-ref name="content repository">46</part-num-ref>
|
| 362 |
+
for removing any older stored previously broadcasted program. Thus, any stored broadcasted programming greater than two weeks old may be deleted from the system or removed from being available (removed from the program guide). It should be noted that various times may be set forth. Also, various retention times associated with various programs or channels may also be set forth. That is, different channels and different programs may have different retention times within the content repository <part-num-ref name="content repository">46.</part-num-ref>
|
| 363 |
+
</p>
|
| 364 |
+
<p id="p-57" num="57">Popular titles could be maintained longer than less popular titles.</p>
|
| 365 |
+
<p id="p-58" num="58">[0049] Further, availability or retention windows may also be established to allow user devices to see what is available and still allow them sufficient time to download the material. For example, if two weeks of material is maintained, the actual <boundary-data type="header">
|
| 366 |
+
<confidence value="88">15</confidence>
|
| 367 |
+
</boundary-data>
|
| 368 |
+
<page-break num="17"/>
|
| 369 |
+
<boundary-data type="header">PD-207010</boundary-data>
|
| 370 |
+
publish time may be two weeks plus some fixed time to allocate the program to be communicated to a user device. The extra time may be fixed or variable depending on the length of a particular content. To summarize, the content may actually be available for a predetermined amount of time after it is removed from an "available" content list or the program guide. Such a feature may allow the system time to service various requests and, therefore, increase customer satisfaction. </p>
|
| 371 |
+
<p id="p-59" num="59">[0050] In step 260, requests are received at the service provider for particular stored content through a network. In step <part-num-ref name="network. In step">262,</part-num-ref>
|
| 372 |
+
an optional step of receiving a confirmation from the user device may be performed. That is, both a request and a confirmation may be required for transferring a program to the user device. The confirmation and request may also take place only at the user device and, thus, they may be combined into one signal received at the user device. </p>
|
| 373 |
+
<p id="p-60" num="60">[0051<confidence value="5">]</confidence>
|
| 374 |
+
In step 264, the program corresponding to the selected content is retrieved from the content repository. </p>
|
| 375 |
+
<p id="p-61" num="61">[0052] In step 266, optional steps corresponding to steps 210 and <part-num-ref name="and">212</part-num-ref>
|
| 376 |
+
may be performed. In step <part-num-ref name="may be performed. In step">266,</part-num-ref>
|
| 377 |
+
a popularity rating may be determined for the particular program. </p>
|
| 378 |
+
<p id="p-62" num="62">In step 268, a means for communicating based upon the popularity of the program may be determined. This may entail choosing a network. In step <part-num-ref name="network. In step">268,</part-num-ref>
|
| 379 |
+
based upon the popularity rating, a network for communicating may be determined. As mentioned above in step <part-num-ref name="network for communicating may be determined. As mentioned above in step">212,</part-num-ref>
|
| 380 |
+
various types of networks may be used based upon the popularity including wired, wireless, terrestrial, and satellite. In step <part-num-ref name="popularity including wired, wireless, terrestrial, and satellite. In step">270,</part-num-ref>
|
| 381 |
+
the program is communicated to the user device using the selected communication means. </p>
|
| 382 |
+
<p id="p-63" num="63">[0053] The present disclosure allows a user to request content that was heretofore otherwise not available. In prior systems, a user would identify various programming desirable to be downloaded prior to broadcast and thereafter, during the <boundary-data type="header">
|
| 383 |
+
<confidence value="88">16</confidence>
|
| 384 |
+
</boundary-data>
|
| 385 |
+
<page-break num="18"/>
|
| 386 |
+
<boundary-data type="header">PD-207010</boundary-data>
|
| 387 |
+
broadcast, storing the content on a local memory device. The present disclosure allows prior broadcasted programming to be received at various times after the program is broadcast. This provides a significant benefit to the user so they may access more content. </p>
|
| 388 |
+
<p id="p-64" num="64">[0054] Those skilled in the art can now appreciate from the foregoing description that the broad teachings of the disclosure can be implemented in a variety of forms. Therefore, while this disclosure includes particular examples, the true scope of the disclosure should not be so limited since other modifications will become apparent to the skilled practitioner upon a study of the drawings, the specification and the following claims.</p>
|
| 389 |
+
<boundary-data type="header">
|
| 390 |
+
<confidence value="88">17</confidence>
|
| 391 |
+
</boundary-data>
|
| 392 |
+
</description>
|
| 393 |
+
</us-patent-application>
|
| 394 |
+
|
applicant/11740814.xml
ADDED
|
@@ -0,0 +1,555 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11740814</doc-number>
|
| 8 |
+
<date>2007-04-26</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">20483</boundary-data>
|
| 14 |
+
<heading id="h-1">ACCESSORY ATTACHMENTS FOR A WELDING GARMENT</heading>
|
| 15 |
+
<heading id="h-2">CROSS REFERENCE TO RELATED APPLICATIONS</heading>
|
| 16 |
+
<p id="p-1" num="1">[0001<confidence value="2">J</confidence>
|
| 17 |
+
This application claims priority to U.S. Provisional Patent Application No. </p>
|
| 18 |
+
<p id="p-2" num="2">60/854,905, entitled "ACCESSORY ATTACHMENTS FOR A WELDING JACKET", filed on October <part-num-ref name="WELDING JACKET", filed on October">27,</part-num-ref>
|
| 19 |
+
<part-num-ref name="WELDING JACKET", filed on October 27,">2006.</part-num-ref>
|
| 20 |
+
</p>
|
| 21 |
+
<heading id="h-3">BACKGROUND</heading>
|
| 22 |
+
<p id="p-3" num="3">[0002<confidence value="5">]</confidence>
|
| 23 |
+
The invention relates generally to a welding garment. More specifically, the invention relates to a flame-resistant welding garment, such as a welding jacket or another article of clothing, configured to receive a supplemental flame-resistant protective layer or other accessory attachments. </p>
|
| 24 |
+
<p id="p-4" num="4">
|
| 25 |
+
<confidence value="5">[</confidence>
|
| 26 |
+
0003<confidence value="5">]</confidence>
|
| 27 |
+
Welding garments are typically a one-piece garment, which can be bulky and likely to retain body heat. If the welding garment is not worn by an operator, then the heat, sparks, or molten metal associated with a welding procedure may injure the operator due to a lack of flame resistance of normal clothing. However, in many facilities and applications, the operator may perform welding procedures intermittently rather than continuously throughout the day. Thus, the welding garment is not continuously needed for protection. Welding procedures often occur in uncontrollable, unpredictable, or extreme weather conditions, for example, high temperature and high humidity. These weather conditions can make the existing welding garments uncomfortable or unbearable to wear. As a result, the operator may be inclined to perform the welding procedures without the proper welding garment. </p>
|
| 28 |
+
<p id="p-5" num="5">In addition, if the welding garment becomes overly worn, damaged, or ineffective to protect against the welding conditions, then the entire welding garment is typically replaced at a significant cost.</p>
|
| 29 |
+
<heading id="h-4">BRIEF DESCRIPTION</heading>
|
| 30 |
+
<p id="p-6" num="6">
|
| 31 |
+
<confidence value="5">[</confidence>
|
| 32 |
+
0004<confidence value="5">]</confidence>
|
| 33 |
+
A flame resistant garment, in certain embodiments, may include multiple garment portions to provide different degrees of protection for welding or another <boundary-data type="header">
|
| 34 |
+
<confidence value="1">1</confidence>
|
| 35 |
+
</boundary-data>
|
| 36 |
+
<page-break num="2"/>
|
| 37 |
+
<boundary-data type="header">20483</boundary-data>
|
| 38 |
+
application. In one embodiment, the flame-resistant garment may include a base garment and one or more supplemental protective layers or garments. For example, the base garment may include a jacket, a vest, a coverall, a jumpsuit, an overall, pants, trousers, a smock, a hat, a hood, or a combination thereof<confidence value="5">.</confidence>
|
| 39 |
+
The protective layer may include a bib or any other suitable attachment to add further flame resistance. Further, the multiple garment portions may be coupled together via a snap fastener system, a hook-and-loop system, a button system, a zipper system, a buckle system, or a clip system, or a combination thereof. </p>
|
| 40 |
+
<heading id="h-5">DRAWINGS</heading>
|
| 41 |
+
<p id="p-7" num="7">
|
| 42 |
+
<confidence value="5">[</confidence>
|
| 43 |
+
0005<confidence value="5">]</confidence>
|
| 44 |
+
These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein: </p>
|
| 45 |
+
<p id="p-8" num="8">[0006] FIG. 1 illustrates a front elevational view and a back elevational view of an embodiment of a flame-resistant article of clothing, wherein the clothing includes a jacket having upper and lower portions made from first and second materials, respectively;</p>
|
| 46 |
+
<p id="p-9" num="9">
|
| 47 |
+
<confidence value="5">[</confidence>
|
| 48 |
+
0007<confidence value="5">]</confidence>
|
| 49 |
+
FIG. 2 illustrates a front elevational view and a back elevational view of an alternate embodiment of the jacket shown in FIG. 1; </p>
|
| 50 |
+
<p id="p-10" num="10">
|
| 51 |
+
<confidence value="5">[</confidence>
|
| 52 |
+
0008<confidence value="5">]</confidence>
|
| 53 |
+
FIG. 3 is a front elevational view of an embodiment of the jacket shown in FIGS. <confidence value="4">1</confidence>
|
| 54 |
+
and <part-num-ref name="and">2,</part-num-ref>
|
| 55 |
+
further illustrating a fastening mechanism located at an upper attachment area and a lower attachment area; </p>
|
| 56 |
+
<p id="p-11" num="11">
|
| 57 |
+
<confidence value="4">[</confidence>
|
| 58 |
+
0009<confidence value="5">]</confidence>
|
| 59 |
+
FIG. 4 is a back elevational view of an embodiment of a flame-resistant protective layer of clothing, such as a bib, configured to couple with the jacket shown in FIGS. 1-3; </p>
|
| 60 |
+
<p id="p-12" num="12">
|
| 61 |
+
<confidence value="5">[</confidence>
|
| 62 |
+
0010] FIG. 5A illustrates the bib of FIG. 4 removably attached to the jacket of FIGS. 1-3 at the upper attachment area; </p>
|
| 63 |
+
<boundary-data type="header">
|
| 64 |
+
<confidence value="8">2</confidence>
|
| 65 |
+
</boundary-data>
|
| 66 |
+
<boundary-data type="header">20483</boundary-data>
|
| 67 |
+
<p id="p-13" num="13">
|
| 68 |
+
<page-break num="3"/>
|
| 69 |
+
<confidence value="5">[</confidence>
|
| 70 |
+
0011<confidence value="5">]</confidence>
|
| 71 |
+
FIG. <confidence value="5">5</confidence>
|
| 72 |
+
B illustrates the bib of FIG. 4 removably attached to the jacket of FIGS. 1-3 at the lower attachment area; </p>
|
| 73 |
+
<p id="p-14" num="14">
|
| 74 |
+
<confidence value="5">[</confidence>
|
| 75 |
+
0012<confidence value="5">]</confidence>
|
| 76 |
+
FIG. 6 is a back elevational view of an alternate embodiment of the jacket of FIG. 1, wherein the jacket includes a shoulder attachment region, a mid-back attachment region, and a lower waist-line attachment region; </p>
|
| 77 |
+
<p id="p-15" num="15">
|
| 78 |
+
<confidence value="5">[</confidence>
|
| 79 |
+
0013<confidence value="5">]</confidence>
|
| 80 |
+
FIG. 7 illustrates the bib of FIG. 4 removably attached to the jacket of FIG. </p>
|
| 81 |
+
<p id="p-16" num="16">6 at the shoulder attachment region;</p>
|
| 82 |
+
<p id="p-17" num="17">
|
| 83 |
+
<confidence value="5">[</confidence>
|
| 84 |
+
0014<confidence value="5">]</confidence>
|
| 85 |
+
FIG. 8 illustrates an alternate embodiment of a bib removably attached to the jacket of FIG. 6 at the mid-back attachment region, wherein the bib wraps around the entire lower portion of the jacket; </p>
|
| 86 |
+
<p id="p-18" num="18">
|
| 87 |
+
<confidence value="5">1</confidence>
|
| 88 |
+
0015<confidence value="5">1</confidence>
|
| 89 |
+
FIG. 9A is an alternate embodiment of a jacket system illustrating a smock and a vest configuration; </p>
|
| 90 |
+
<p id="p-19" num="19">
|
| 91 |
+
<confidence value="5">[</confidence>
|
| 92 |
+
0016<confidence value="4">]</confidence>
|
| 93 |
+
FIG. 9B shows the jacket system of FIG. 9A, illustrating the smock attached to the vest; </p>
|
| 94 |
+
<p id="p-20" num="20">
|
| 95 |
+
<confidence value="5">[</confidence>
|
| 96 |
+
0017<confidence value="5">]</confidence>
|
| 97 |
+
FIG. 10 illustrates a front elevational view of an alternate embodiment of a flame-resistant article of clothing, wherein the clothing includes pants having a waist attachment section, a mid-thigh section, and a shin section; </p>
|
| 98 |
+
<p id="p-21" num="21">
|
| 99 |
+
<confidence value="5">[</confidence>
|
| 100 |
+
0018<confidence value="5">]</confidence>
|
| 101 |
+
FIG. 11 illustrates the bib of FIG. 4 removably attached to the pants of FIG. </p>
|
| 102 |
+
<p id="p-22" num="22">10 at the waist attachment section; and <confidence value="5">[</confidence>
|
| 103 |
+
0019<confidence value="5">]</confidence>
|
| 104 |
+
FIG. 12 illustrates a front elevational view of an alternate embodiment of a flame-resistant article of clothing, wherein the clothing includes a jumpsuit or overalls. </p>
|
| 105 |
+
<heading id="h-6">DETAILED DESCRIPTION</heading>
|
| 106 |
+
<p id="p-23" num="23">
|
| 107 |
+
<confidence value="5">[</confidence>
|
| 108 |
+
0020<confidence value="5">]</confidence>
|
| 109 |
+
Various embodiments of a welding garment are disclosed that provide flame-resistant protection to a wearer. The garment may include a flame-resistant article of clothing that is configured to receive a protective layer of clothing via a <boundary-data type="header">
|
| 110 |
+
<confidence value="8">3</confidence>
|
| 111 |
+
</boundary-data>
|
| 112 |
+
<page-break num="4"/>
|
| 113 |
+
<boundary-data type="header">20483</boundary-data>
|
| 114 |
+
fastening mechanism. The article of clothing may include a jacket, a vest, a coverall, a jumpsuit, an overall, pants, trousers, smock, a hat, a hood, or a combination thereof. </p>
|
| 115 |
+
<p id="p-24" num="24">The protective layer of clothing may include a bib or other accessory attachments.</p>
|
| 116 |
+
<p id="p-25" num="25">The accessory attachments provide for modularity or layering of flame-resistant material, thereby enabling the wearer to increase or decrease flame-resistant layers as desired. This is beneficial because it enables the operator to customize flame-resistant protection from one application to the next.</p>
|
| 117 |
+
<p id="p-26" num="26">
|
| 118 |
+
<confidence value="5">[</confidence>
|
| 119 |
+
0021<confidence value="4">1</confidence>
|
| 120 |
+
For example, in one of the contemplated embodiments, the article of clothing is a welding jacket that includes a top section and a bottom section that may be made from the same or different flame-resistant materials. In a first operation, the wearer might be engaged in an over-head welding operation, thereby exposing his or her upper body to the heat intensive operation. Therefore, the wearer may desire more protection for the shoulder area during this operation as compared to a lower level welding operation, e.g., at a bench or in a bent over position. </p>
|
| 121 |
+
<p id="p-27" num="27">
|
| 122 |
+
<confidence value="4">[</confidence>
|
| 123 |
+
0022<confidence value="5">]</confidence>
|
| 124 |
+
Additionally, the multi-layered system enables the user to wear the article of clothing in a fitted manner which may be more comfortable than a standard protective garment that only provides "one size fits all" protection. Finally, embodiments of the present invention reduce the cost of flame-resistant protection by enabling the user to replace worn or abraded accessory attachments without having to replace the entire article of clothing. This may also reduce the initial cost of the article of clothing by enabling the substitution of a less expensive material given it may only need to serve as a redundant layer to the attached accessory. Therefore, the article of clothing may not only be less expensive but may also be made from a lighter weight material to provide additional comfort for the wearer when he/she is not engaged in a welding operation. </p>
|
| 125 |
+
<p id="p-28" num="28">[0023] Turning now to the drawings, FIG. 1 illustrates a front view 12A and a back view 14A of a flame-resistant article of clothing in the form of jacket <confidence value="6688">10A.</confidence>
|
| 126 |
+
</p>
|
| 127 |
+
<p id="p-29" num="29">Welding jacket <confidence value="54">10</confidence>
|
| 128 |
+
A may be made from any number of materials, including leather, in whole or in part. Additionally, welding jacket may be made from flame-resistant materials that may include a chemically treated natural fabric, a chemically treated <boundary-data type="header">
|
| 129 |
+
<confidence value="8">4</confidence>
|
| 130 |
+
</boundary-data>
|
| 131 |
+
<page-break num="5"/>
|
| 132 |
+
<boundary-data type="header">20483</boundary-data>
|
| 133 |
+
natural fabric and synthetic fiber blend, a flame-resistant synthetic fiber blend, a flame-resistant leather, or a combination thereof. </p>
|
| 134 |
+
<p id="p-30" num="30">
|
| 135 |
+
<confidence value="5">[</confidence>
|
| 136 |
+
0024<confidence value="5">]</confidence>
|
| 137 |
+
Welding jacket <confidence value="24">10</confidence>
|
| 138 |
+
A includes a top section or upper portion 16A and a bottom section or lower portion 18A. Top section 16A includes a collar 20A, shoulder area 22A, a left sleeve <part-num-ref name="left sleeve">24,</part-num-ref>
|
| 139 |
+
and a right sleeve <part-num-ref name="right sleeve">26.</part-num-ref>
|
| 140 |
+
The top section 16A terminates at a first bottom edge or upper attachment area 28A. Bottom section 1<confidence value="88">8A</confidence>
|
| 141 |
+
substantially covers the torso of the wearer and terminates in a second bottom edge or lower attachment area 30A. Lower attachment area 30A may be located at or below the waist of the person wearing the jacket, when the jacket is worn. In the illustrated embodiment shown in FIG. 1, top section 16A may be made of leather and bottom section 18A may be made of a flame-resistant cotton fabric or any other suitable material. Jacket <confidence value="4">I</confidence>
|
| 142 |
+
A may be worn by the wearer in a standard fashion, and has a vertical zipper or vertical array of buttons that crosses the top section 16A and bottom section 18A to enable opening or closing of jacket <confidence value="54">10</confidence>
|
| 143 |
+
A about the wearer. </p>
|
| 144 |
+
<p id="p-31" num="31">Additionally, collar 20A may include a number of different configurations, such as a barracuda style or square edged turned down style.</p>
|
| 145 |
+
<p id="p-32" num="32">
|
| 146 |
+
<confidence value="5">[</confidence>
|
| 147 |
+
0025<confidence value="5">]</confidence>
|
| 148 |
+
FIG. 2 illustrates a front view 12B and a back view 14B of an alternate embodiment of a welding jacket <confidence value="24">1O</confidence>
|
| 149 |
+
B. Welding jacket <confidence value="25">lO</confidence>
|
| 150 |
+
B includes a top section 16B, a bottom section 18B, a collar 20B, a shoulder area 22B, a left sleeve 24B, a right sleeve 26B, a first bottom edge 28B, and a second bottom edge 30B. Additionally, jacket <confidence value="55">lO</confidence>
|
| 151 |
+
B may include a hat or hood attached at or near collar 20B. In the embodiment of FIG. 2, top section 16B and bottom section 18B are made from a single flame-resistant material, such as a flame-resistant cotton fabric, that is suitable for jacket <confidence value="55">1O</confidence>
|
| 152 |
+
B. Alternatively, as discussed with the embodiment illustrated in FIG. 1, top section 16B and bottom section 18B may include more than one flame-resistant material. </p>
|
| 153 |
+
<p id="p-33" num="33">[0026<confidence value="5">]</confidence>
|
| 154 |
+
Specifically, the top section 16B, the bottom section 18B, or both, may be made of a flame-resistant material including a cotton fabric impregnated with a flame retardant chemical; a vinal and polynosic rayon blend; an aramid synthetic fiber; a meta-aramid and para-aramid fiber blend; a meta-aramid, para-aramid, and <boundary-data type="header">
|
| 155 |
+
<confidence value="8">5</confidence>
|
| 156 |
+
</boundary-data>
|
| 157 |
+
<page-break num="6"/>
|
| 158 |
+
<boundary-data type="header">20483</boundary-data>
|
| 159 |
+
modacrylic fiber blend; an oxidized polyacrylonitrile and aramid fiber blend; or a combination thereof. An exemplary embodiment of a cotton fabric impregnated with a flame retardant chemical is available from Westex Inc. in Chicago, IL, and may be identified under the trademark INDURA. An exemplary embodiment of a cotton and high tenacity nylon fabric blend impregnated with a flame retardant chemical is also available from Westex Inc. and may be identified under the trademark <confidence value="5">I</confidence>
|
| 160 |
+
NDURA Ultra Soft<confidence value="5">.</confidence>
|
| 161 |
+
Finally, Westex also provides an exemplary embodiment of a vinal and polynosic rayon blend that may be identified under the trademark Vinex. </p>
|
| 162 |
+
<p id="p-34" num="34">
|
| 163 |
+
<confidence value="5">[</confidence>
|
| 164 |
+
0027] Additionally, an exemplary embodiment of an aramid synthetic fiber is available from DuPont in Richmond, VA, and may be identified under the trademark NOMEX. An exemplary embodiment of a meta-aramid and para-aramid fiber blend is also available from DuPont and may be identified under the trademark NOMEX <confidence value="888">III</confidence>
|
| 165 |
+
A. DuPont also provides an exemplary embodiment of a meta-aramid, para- aramid, and modacrylic fiber blend that may be identified under the trademark Protera. Finally, an exemplary embodiment of an oxidized polyacrylonitrile and aramid fiber blend is available from Chapman Thermal Products in Salt Lake City, UT, and may be identified under the trademark CarbonX. It should be noted that even though specific example of different materials have been disclosed, embodiments of the present invention are by no means limited to these materials and may include any suitable flame-resistant material. For example, the flame-resistant material may include leather, such as pigskin or goatskin leather. </p>
|
| 166 |
+
<p id="p-35" num="35">
|
| 167 |
+
<confidence value="5">[</confidence>
|
| 168 |
+
0028<confidence value="5">]</confidence>
|
| 169 |
+
In the following figures, the alphabetic characters "A" and "B" of similar items illustrated and described with reference to FIGS. 1 and <part-num-ref name="and">2</part-num-ref>
|
| 170 |
+
are shown in the figures, yet the following discussion excludes these characters for simplicity. Thus, only the numeric portion of each item is referenced in the following discussion. FIG. </p>
|
| 171 |
+
<p id="p-36" num="36">3 illustrates another front view 12 of the jacket <part-num-ref name="jacket">10</part-num-ref>
|
| 172 |
+
shown in FIGS. 1 and <part-num-ref name="and">2,</part-num-ref>
|
| 173 |
+
further illustrating a fastening mechanism located at an upper attachment area and a lower attachment area. As with the previous figures, FIG.3 illustrates jacket <part-num-ref name="previous figures, FIG.3 illustrates jacket">10</part-num-ref>
|
| 174 |
+
having top section <part-num-ref name="having top section">16</part-num-ref>
|
| 175 |
+
and bottom section <part-num-ref name="and bottom section">18.</part-num-ref>
|
| 176 |
+
Flame-resistant layers or flaps <part-num-ref name="and bottom section 18. Flame-resistant layers or flaps">32</part-num-ref>
|
| 177 |
+
and <part-num-ref name="and">38</part-num-ref>
|
| 178 |
+
are located at first bottom edge <part-num-ref name="are located at first bottom edge">28</part-num-ref>
|
| 179 |
+
and second bottom edge <part-num-ref name="and second bottom edge">30,</part-num-ref>
|
| 180 |
+
respectively. Flaps <part-num-ref name="and second bottom edge 30, respectively. Flaps">32,</part-num-ref>
|
| 181 |
+
<part-num-ref name="and second bottom edge 30, respectively. Flaps 32,">38</part-num-ref>
|
| 182 |
+
may be lifted to expose a fastening mechanism located on jacket <part-num-ref name="fastening mechanism located on jacket">10.</part-num-ref>
|
| 183 |
+
Further, flaps <boundary-data type="header">
|
| 184 |
+
<confidence value="8">6</confidence>
|
| 185 |
+
</boundary-data>
|
| 186 |
+
<page-break num="7"/>
|
| 187 |
+
<boundary-data type="header">20483</boundary-data>
|
| 188 |
+
<part-num-ref name="fastening mechanism located on jacket 10. Further, flaps">32,</part-num-ref>
|
| 189 |
+
<part-num-ref name="fastening mechanism located on jacket 10. Further, flaps 32,">38</part-num-ref>
|
| 190 |
+
are made from a flame-resistant material and provide a protective layer to cover the fastening mechanism. For example, flaps <part-num-ref name="fastening mechanism. For example, flaps">32,</part-num-ref>
|
| 191 |
+
<part-num-ref name="fastening mechanism. For example, flaps 32,">38</part-num-ref>
|
| 192 |
+
protect the fastening mechanism from molten metal, sparks, or BB's originating from a weld location during a welding procedure. </p>
|
| 193 |
+
<p id="p-37" num="37">
|
| 194 |
+
<confidence value="5">[</confidence>
|
| 195 |
+
0029] Specifically, one of the contemplated embodiments of the flame-resistant garment includes male snaps 36A, 36B, 36C, 40A, 40B, and 40C as the fastening mechanism. Thus, flaps <part-num-ref name="fastening mechanism. Thus, flaps">32,</part-num-ref>
|
| 196 |
+
<part-num-ref name="fastening mechanism. Thus, flaps 32,">38</part-num-ref>
|
| 197 |
+
helps to prevent the male snaps from becoming damaged or made inoperable as a result of refracted material that may lodge within the snaps and/or melt the snaps. Additionally, the present embodiments are not limited to snaps, and flaps 32,38 may provide protection for various fastening mechanisms. For example, the fastening mechanisms may include a hook-and-loop system, a button system, a zipper system, a buckle system, a clip system, a snap fastener system, or a combination system thereof<confidence value="5">.</confidence>
|
| 198 |
+
</p>
|
| 199 |
+
<p id="p-38" num="38">
|
| 200 |
+
<confidence value="5">[</confidence>
|
| 201 |
+
0030<confidence value="5">]</confidence>
|
| 202 |
+
FIG. 4 is a back view of an embodiment of a flame-resistant protective layer of clothing or protective garment <part-num-ref name="flame-resistant protective layer of clothing or protective garment">42</part-num-ref>
|
| 203 |
+
in the form of a bib. Bib <part-num-ref name="bib. Bib">42</part-num-ref>
|
| 204 |
+
is an accessory attachment having an attachment mechanism located along a top periphery of the bib. </p>
|
| 205 |
+
<p id="p-39" num="39">In one of the contemplated embodiments, the attachment mechanism includes female snaps 44A, 44B, 44C, 44D, 44E, and 44F. Female snaps 44A, 44B, and 44C are separated or spaced apart so that they mate with male snaps 36A, 36B, 36C, located on the right side of top section <part-num-ref name="right side of top section">16</part-num-ref>
|
| 206 |
+
of jacket <part-num-ref name="of jacket">10.</part-num-ref>
|
| 207 |
+
Similarly, female snaps 44D, 44E, and 44F are separated or spaced apart so that they mate with male snaps 36A, 36B, 36C, located on the left side of top section <part-num-ref name="left side of top section">16</part-num-ref>
|
| 208 |
+
of jacket <part-num-ref name="of jacket">10.</part-num-ref>
|
| 209 |
+
Bib accessory <part-num-ref name="of jacket 10. Bib accessory">42</part-num-ref>
|
| 210 |
+
may be sized to substantially or entirely cover jacket <part-num-ref name="may be sized to substantially or entirely cover jacket">10</part-num-ref>
|
| 211 |
+
about the torso of the wearer when attached to the jacket at this location. Finally, male snaps 40A, 40B, 40C may be spaced similar to male snaps 36A, 36B, and 36C, such that bib <part-num-ref name="jacket at this location. Finally, male snaps 40A, 40B, 40C may be spaced similar to male snaps 36A, 36B, and 36C, such that bib">42</part-num-ref>
|
| 212 |
+
can be attached at this location of jacket <part-num-ref name="can be attached at this location of jacket">10.</part-num-ref>
|
| 213 |
+
</p>
|
| 214 |
+
<p id="p-40" num="40">
|
| 215 |
+
<confidence value="5">[</confidence>
|
| 216 |
+
0031<confidence value="5">]</confidence>
|
| 217 |
+
FIG. 5A illustrates bib 42 partially attached to the right side of jacket <part-num-ref name="right side of jacket">10</part-num-ref>
|
| 218 |
+
at upper attachment area <part-num-ref name="at upper attachment area">28.</part-num-ref>
|
| 219 |
+
The figure shows flaps <part-num-ref name="figure shows flaps">32</part-num-ref>
|
| 220 |
+
lifted to expose the fastening mechanism thereby enabling bib <part-num-ref name="fastening mechanism thereby enabling bib">42</part-num-ref>
|
| 221 |
+
to be removably attached to jacket <part-num-ref name="to be removably attached to jacket">10.</part-num-ref>
|
| 222 |
+
Similarly, FIG. 5B illustrates bib <part-num-ref name="to be removably attached to jacket 10. Similarly, FIG. 5B illustrates bib">42</part-num-ref>
|
| 223 |
+
partially attached to the right side of jacket <part-num-ref name="right side of jacket">10</part-num-ref>
|
| 224 |
+
at the lower <boundary-data type="header">
|
| 225 |
+
<confidence value="8">7</confidence>
|
| 226 |
+
</boundary-data>
|
| 227 |
+
<page-break num="8"/>
|
| 228 |
+
<boundary-data type="header">20483</boundary-data>
|
| 229 |
+
attachment area <part-num-ref name="lower attachment area">30.</part-num-ref>
|
| 230 |
+
As illustrated in FIG. <confidence value="5">5</confidence>
|
| 231 |
+
B, male snaps 40A, 40B and 40C are equally spaced to align with female snaps 44A, <confidence value="66">44</confidence>
|
| 232 |
+
B, and 44<confidence value="5">C</confidence>
|
| 233 |
+
. Further, accessory attachment <part-num-ref name="lower attachment area 30. As illustrated in FIG. 5B, male snaps 40A, 40B and 40C are equally spaced to align with female snaps 44A, 44B, and 44C. Further, accessory attachment">42</part-num-ref>
|
| 234 |
+
may be sized to substantially or entirely cover the waste area and a portion of the legs down to the shin of the wearer. Finally, jacket <part-num-ref name="wearer. Finally, jacket">10</part-num-ref>
|
| 235 |
+
enables the wearer to use more than one protective garment or bib by including both upper attachment area <part-num-ref name="wearer to use more than one protective garment or bib by including both upper attachment area">28</part-num-ref>
|
| 236 |
+
and lower attachment area <part-num-ref name="and lower attachment area">30</part-num-ref>
|
| 237 |
+
that enables simultaneous attachment of two separate welding accessories <part-num-ref name="that enables simultaneous attachment of two separate welding accessories">42.</part-num-ref>
|
| 238 |
+
Alternatively, the bib <part-num-ref name="bib">42</part-num-ref>
|
| 239 |
+
may attach to both the upper and lower attachment areas <part-num-ref name="upper and lower attachment areas">28,</part-num-ref>
|
| 240 |
+
<part-num-ref name="upper and lower attachment areas 28,">30.</part-num-ref>
|
| 241 |
+
Furthermore, the bib <part-num-ref name="bib">42</part-num-ref>
|
| 242 |
+
may extend entirely or partially along the pants of a wearer, around the body of the wearer, or over the shoulders to cover the front and back of a wearer, or a combination thereof<confidence value="5">.</confidence>
|
| 243 |
+
</p>
|
| 244 |
+
<p id="p-41" num="41">
|
| 245 |
+
<confidence value="5">[</confidence>
|
| 246 |
+
0032<confidence value="5">]</confidence>
|
| 247 |
+
FIG. 6 is a back view <part-num-ref name="back view">14</part-num-ref>
|
| 248 |
+
of an alternate embodiment of the jacket <part-num-ref name="jacket">10</part-num-ref>
|
| 249 |
+
having a shoulder attachment region <part-num-ref name="shoulder attachment region">45,</part-num-ref>
|
| 250 |
+
a mid-back attachment region <part-num-ref name="mid-back attachment region">46,</part-num-ref>
|
| 251 |
+
and a waist-line attachment region <part-num-ref name="waist-line attachment region">47.</part-num-ref>
|
| 252 |
+
In this embodiment, the jacket <part-num-ref name="jacket">10</part-num-ref>
|
| 253 |
+
includes top section <part-num-ref name="includes top section">16,</part-num-ref>
|
| 254 |
+
bottom section <part-num-ref name="includes top section 16, bottom section">18,</part-num-ref>
|
| 255 |
+
and collar <part-num-ref name="includes top section 16, bottom section 18, and collar">20.</part-num-ref>
|
| 256 |
+
Further, the jacket <part-num-ref name="jacket">10</part-num-ref>
|
| 257 |
+
includes flaps <part-num-ref name="includes flaps">48</part-num-ref>
|
| 258 |
+
located at shoulder attachment region <part-num-ref name="located at shoulder attachment region">45</part-num-ref>
|
| 259 |
+
that provide a flame-resistant protective layer to cover fastening mechanisms 49A, 49B, and 49<confidence value="5">C</confidence>
|
| 260 |
+
. The jacket <part-num-ref name="jacket">10</part-num-ref>
|
| 261 |
+
similarly includes a flap <part-num-ref name="flap">50</part-num-ref>
|
| 262 |
+
and fastening mechanisms 52A, 52B, 52C, 52D, 52E, 52F located at mid-back attachment region <part-num-ref name="and fastening mechanisms 52A, 52B, 52C, 52D, 52E, 52F located at mid-back attachment region">46.</part-num-ref>
|
| 263 |
+
Additionally, the jacket may include flap <part-num-ref name="jacket may include flap">54</part-num-ref>
|
| 264 |
+
as well as fastening mechanism 56A, 56B, 56C, 56D, 56E, and 56F located at waist-line attachment region <part-num-ref name="as well as fastening mechanism 56A, 56B, 56C, 56D, 56E, and 56F located at waist-line attachment region">47.</part-num-ref>
|
| 265 |
+
As with the previous embodiments, flaps <part-num-ref name="previous embodiments, flaps">48,</part-num-ref>
|
| 266 |
+
<part-num-ref name="previous embodiments, flaps 48,">50,</part-num-ref>
|
| 267 |
+
and <part-num-ref name="previous embodiments, flaps 48, 50, and">54</part-num-ref>
|
| 268 |
+
may include a flame-resistant layer to cover and protect the fastening mechanisms. FIG. 6 further illustrates male snaps as the fastening mechanism. However, embodiments of the present invention are by no means limited to a snap fastener system. As with the embodiments discussed above, fastening mechanisms <part-num-ref name="embodiments discussed above, fastening mechanisms">49,</part-num-ref>
|
| 269 |
+
<part-num-ref name="embodiments discussed above, fastening mechanisms 49,">52,</part-num-ref>
|
| 270 |
+
and <part-num-ref name="embodiments discussed above, fastening mechanisms 49, 52, and">56</part-num-ref>
|
| 271 |
+
may include a hook-and-loop system, a button system, a zipper system, a buckle system, a clip system, or a combination thereof<confidence value="5">.</confidence>
|
| 272 |
+
</p>
|
| 273 |
+
<p id="p-42" num="42">
|
| 274 |
+
<confidence value="5">[</confidence>
|
| 275 |
+
0033] FIG. 7 illustrates bib <part-num-ref name="illustrates bib">42</part-num-ref>
|
| 276 |
+
partially attached to the right side of jacket <part-num-ref name="right side of jacket">10</part-num-ref>
|
| 277 |
+
at shoulder attachment region <part-num-ref name="at shoulder attachment region">45.</part-num-ref>
|
| 278 |
+
The figure shows flap <part-num-ref name="figure shows flap">48</part-num-ref>
|
| 279 |
+
lifted to expose the fastening mechanism thereby enabling bib <part-num-ref name="fastening mechanism thereby enabling bib">42</part-num-ref>
|
| 280 |
+
to be removably attached to the jacket <part-num-ref name="jacket">10.</part-num-ref>
|
| 281 |
+
Female snaps 44A, 44<confidence value="5">B</confidence>
|
| 282 |
+
, and 44C are separated or spaced apart so that they mate <boundary-data type="header">
|
| 283 |
+
<confidence value="8">8</confidence>
|
| 284 |
+
</boundary-data>
|
| 285 |
+
<page-break num="9"/>
|
| 286 |
+
<boundary-data type="header">20483</boundary-data>
|
| 287 |
+
with male snaps 49A, 49B, and 49C located on the right side of the jacket. Similarly, female snaps 44D, 44E, and 44F are separated or spaced apart so that they mate with male snaps 49A, 49B, 49C, located on the left side of the jacket. Bib accessory <part-num-ref name="jacket. Bib accessory">42</part-num-ref>
|
| 288 |
+
may be sized to substantially or entirely cover the shoulder region and upper torso of the wearer. This may be especially beneficial in over head welding applications. </p>
|
| 289 |
+
<p id="p-43" num="43">Additionally, male snaps 52A-52F and 56A-56F may be spaced similar to female snaps 44A-44F, such that bib 42 may be attached at either of these locations of jacket <part-num-ref name="may be attached at either of these locations of jacket">10.</part-num-ref>
|
| 290 |
+
Again, multiple fastening mechanisms enable the attachment of multiple welding accessories providing the wearer with the flexibility of multi-layering the flame- resistant garment. In some embodiments, a first protective layer may be coupled to the jacket <part-num-ref name="jacket">10</part-num-ref>
|
| 291 |
+
at the region <part-num-ref name="region">45,</part-num-ref>
|
| 292 |
+
a second protective layer may be coupled to the jacket <part-num-ref name="jacket">10</part-num-ref>
|
| 293 |
+
at the region <part-num-ref name="region">46,</part-num-ref>
|
| 294 |
+
and a third protective layer may be coupled to the jacket <part-num-ref name="jacket">10</part-num-ref>
|
| 295 |
+
at the region <part-num-ref name="region">47.</part-num-ref>
|
| 296 |
+
These protective layers on the back of the jacket <part-num-ref name="jacket">10</part-num-ref>
|
| 297 |
+
also may be in addition to one or more protective layers coupled to the front of the jacket <part-num-ref name="jacket">10</part-num-ref>
|
| 298 |
+
at areas <part-num-ref name="at areas">28</part-num-ref>
|
| 299 |
+
and <part-num-ref name="and">30,</part-num-ref>
|
| 300 |
+
as discussed in detail above. </p>
|
| 301 |
+
<p id="p-44" num="44">
|
| 302 |
+
<confidence value="5">[</confidence>
|
| 303 |
+
0034<confidence value="5">]</confidence>
|
| 304 |
+
FIG. 8 illustrates an alternate bib <part-num-ref name="alternate bib">58</part-num-ref>
|
| 305 |
+
partially attached to the jacket <part-num-ref name="jacket">10</part-num-ref>
|
| 306 |
+
of FIG. 6 at the mid-back attachment region <part-num-ref name="mid-back attachment region">46.</part-num-ref>
|
| 307 |
+
The figure illustrates bib <part-num-ref name="figure illustrates bib">58</part-num-ref>
|
| 308 |
+
wrapping around the entire lower portion of the jacket <part-num-ref name="jacket">10.</part-num-ref>
|
| 309 |
+
In this embodiment, alternate bib <part-num-ref name="jacket 10. In this embodiment, alternate bib">58</part-num-ref>
|
| 310 |
+
includes attachment mechanisms 60A, 60B, 60<confidence value="66">C,</confidence>
|
| 311 |
+
60D, 60E, and 60F arranged in a similar configuration to that of bib <part-num-ref name="similar configuration to that of bib">42.</part-num-ref>
|
| 312 |
+
Bib <part-num-ref name="similar configuration to that of bib 42. Bib">58</part-num-ref>
|
| 313 |
+
is attached to the mid-back attachment region <part-num-ref name="mid-back attachment region">46</part-num-ref>
|
| 314 |
+
of the jacket <part-num-ref name="jacket">10</part-num-ref>
|
| 315 |
+
via male snaps 52A, 52B, 52C, 52D, 52E, and 52F. In the figure, bib <part-num-ref name="figure, bib">58</part-num-ref>
|
| 316 |
+
is partially attached to the right side of the jacket with female snaps 60A, 60B, and 60C coupled to male snaps 52A, 52B, and 52<confidence value="5">C</confidence>
|
| 317 |
+
. The figure further illustrates bib <part-num-ref name="figure further illustrates bib">58</part-num-ref>
|
| 318 |
+
extending from the back right side of the jacket around to the front side of the jacket, and further around to the back left side of the jacket were the bib may be attached thereto. In this embodiment, the bib provides <part-num-ref name="bib provides">360</part-num-ref>
|
| 319 |
+
degree protection to a user as illustrated by the figure. </p>
|
| 320 |
+
<p id="p-45" num="45">
|
| 321 |
+
<confidence value="5">1</confidence>
|
| 322 |
+
0035<confidence value="5">1</confidence>
|
| 323 |
+
FIG. 9A illustrate a front view of an alternate embodiment of a jacket system <part-num-ref name="jacket system">62</part-num-ref>
|
| 324 |
+
that includes a sleeveless vest <part-num-ref name="sleeveless vest">64</part-num-ref>
|
| 325 |
+
and a sleeved bib or smock <part-num-ref name="sleeved bib or smock">66.</part-num-ref>
|
| 326 |
+
</p>
|
| 327 |
+
<p id="p-46" num="46">Sleeveless vest 64 includes a top section <part-num-ref name="top section">68,</part-num-ref>
|
| 328 |
+
bottom section <part-num-ref name="top section 68, bottom section">70,</part-num-ref>
|
| 329 |
+
collar <part-num-ref name="top section 68, bottom section 70, collar">72,</part-num-ref>
|
| 330 |
+
and sleeveless shoulder area <part-num-ref name="top section 68, bottom section 70, collar 72, and sleeveless shoulder area">74.</part-num-ref>
|
| 331 |
+
Top section <part-num-ref name="top section 68, bottom section 70, collar 72, and sleeveless shoulder area 74. Top section">68</part-num-ref>
|
| 332 |
+
includes collar <part-num-ref name="includes collar">72</part-num-ref>
|
| 333 |
+
and shoulder area <part-num-ref name="and shoulder area">74,</part-num-ref>
|
| 334 |
+
<boundary-data type="header">
|
| 335 |
+
<confidence value="8">9</confidence>
|
| 336 |
+
</boundary-data>
|
| 337 |
+
<page-break num="10"/>
|
| 338 |
+
<boundary-data type="header">20483</boundary-data>
|
| 339 |
+
and terminates at a first bottom edge or upper attachment area <part-num-ref name="first bottom edge or upper attachment area">76.</part-num-ref>
|
| 340 |
+
Bottom section <part-num-ref name="first bottom edge or upper attachment area 76. Bottom section">70</part-num-ref>
|
| 341 |
+
extends from first bottom edge <part-num-ref name="extends from first bottom edge">76</part-num-ref>
|
| 342 |
+
and terminates at a second bottom edge or lower attachment area <part-num-ref name="second bottom edge or lower attachment area">78.</part-num-ref>
|
| 343 |
+
Bottom section <part-num-ref name="second bottom edge or lower attachment area 78. Bottom section">70</part-num-ref>
|
| 344 |
+
may be sized to substantially or entirely cover the lower torso of the wearer. </p>
|
| 345 |
+
<p id="p-47" num="47">
|
| 346 |
+
<confidence value="4">[</confidence>
|
| 347 |
+
0036<confidence value="5">]</confidence>
|
| 348 |
+
Similarly to the previous embodiments, a top flap <part-num-ref name="top flap">80</part-num-ref>
|
| 349 |
+
and a bottom flap <part-num-ref name="bottom flap">82</part-num-ref>
|
| 350 |
+
are located at first bottom edge <part-num-ref name="are located at first bottom edge">76</part-num-ref>
|
| 351 |
+
and second bottom edge <part-num-ref name="and second bottom edge">78,</part-num-ref>
|
| 352 |
+
respectively. Top flap <part-num-ref name="and second bottom edge 78, respectively. Top flap">80</part-num-ref>
|
| 353 |
+
and bottom flap <part-num-ref name="and bottom flap">82</part-num-ref>
|
| 354 |
+
are made from a flame-resistant layer that covers and protects a top fastening mechanism 84A, 84B, and 84C and a bottom fastening mechanism 86A, 86B, and 86C. These mechanisms are located on both the left and right side of the jacket <part-num-ref name="jacket">10.</part-num-ref>
|
| 355 |
+
Additionally, the figure illustrates male snaps for the fastening mechanism, but as discussed above, the fastening mechanism is not limited to a snap fastener system. </p>
|
| 356 |
+
<p id="p-48" num="48">
|
| 357 |
+
<confidence value="5">[</confidence>
|
| 358 |
+
0037<confidence value="5">]</confidence>
|
| 359 |
+
FIG. 9A also illustrates front view 88 of the sleeved bib or smock <part-num-ref name="sleeved bib or smock">66.</part-num-ref>
|
| 360 |
+
A smock may be defined as loose outer garment that protects a layer of clothes or other garment. Sleeved bib or smock <part-num-ref name="layer of clothes or other garment. Sleeved bib or smock">66</part-num-ref>
|
| 361 |
+
includes collar <part-num-ref name="includes collar">90,</part-num-ref>
|
| 362 |
+
shoulder area <part-num-ref name="includes collar 90, shoulder area">92,</part-num-ref>
|
| 363 |
+
right sleeve <part-num-ref name="includes collar 90, shoulder area 92, right sleeve">94,</part-num-ref>
|
| 364 |
+
and left sleeve <part-num-ref name="includes collar 90, shoulder area 92, right sleeve 94, and left sleeve">84.</part-num-ref>
|
| 365 |
+
Sleeved bib <part-num-ref name="includes collar 90, shoulder area 92, right sleeve 94, and left sleeve 84. Sleeved bib">66</part-num-ref>
|
| 366 |
+
extends from the collar <part-num-ref name="collar">90</part-num-ref>
|
| 367 |
+
to a bottom edge <part-num-ref name="bottom edge">98.</part-num-ref>
|
| 368 |
+
</p>
|
| 369 |
+
<p id="p-49" num="49">Attachment mechanisms <confidence value="555">100</confidence>
|
| 370 |
+
A, <confidence value="6665">100B</confidence>
|
| 371 |
+
, 100<confidence value="26">C,</confidence>
|
| 372 |
+
<confidence value="6625">100D</confidence>
|
| 373 |
+
, 100E, and <confidence value="6665">100F</confidence>
|
| 374 |
+
are located near the bottom portion <part-num-ref name="bottom portion">98</part-num-ref>
|
| 375 |
+
of sleeved bib <part-num-ref name="of sleeved bib">66.</part-num-ref>
|
| 376 |
+
Both sleeved bib <part-num-ref name="of sleeved bib 66. Both sleeved bib">66</part-num-ref>
|
| 377 |
+
and vest <part-num-ref name="and vest">64</part-num-ref>
|
| 378 |
+
may be made from any of the flame-resistant materials discussed above or any other suitable material. </p>
|
| 379 |
+
<p id="p-50" num="50">[0038] FIG. 9B illustrates the welding jacket system of 9A with the sleeved bib <part-num-ref name="sleeved bib">66</part-num-ref>
|
| 380 |
+
attached to the sleeveless vest <part-num-ref name="sleeveless vest">64.</part-num-ref>
|
| 381 |
+
The sleeved bib <part-num-ref name="sleeved bib">66</part-num-ref>
|
| 382 |
+
is attached via the attachment mechanisms <confidence value="55588555">100A-100</confidence>
|
| 383 |
+
F coupled to the fastening mechanisms 84A, 84B, and 84C located on both the left and right side of sleeveless vest <part-num-ref name="left and right side of sleeveless vest">64.</part-num-ref>
|
| 384 |
+
Additional fastening and attachment mechanisms may also be included to further removably attach bib <part-num-ref name="left and right side of sleeveless vest 64. Additional fastening and attachment mechanisms may also be included to further removably attach bib">66</part-num-ref>
|
| 385 |
+
to vest <part-num-ref name="to vest">64.</part-num-ref>
|
| 386 |
+
In this embodiment, sleeveless vest <part-num-ref name="to vest 64. In this embodiment, sleeveless vest">64</part-num-ref>
|
| 387 |
+
or sleeved bib <part-num-ref name="or sleeved bib">66</part-num-ref>
|
| 388 |
+
can be made from similar materials or they may be made from different materials. For example, the vest <part-num-ref name="vest">64</part-num-ref>
|
| 389 |
+
may be made of a first flame resistant material, and the vest <part-num-ref name="vest">66</part-num-ref>
|
| 390 |
+
may be made of a second flame resistant material. The first and second flame resistant materials may be the same or different from one another. In addition, one or more protective layers, <boundary-data type="header">
|
| 391 |
+
<confidence value="88">10</confidence>
|
| 392 |
+
</boundary-data>
|
| 393 |
+
<page-break num="11"/>
|
| 394 |
+
<boundary-data type="header">20483</boundary-data>
|
| 395 |
+
made of the same or different materials, may be coupled to the vest <part-num-ref name="vest">64</part-num-ref>
|
| 396 |
+
via the attachment mechanisms <part-num-ref name="attachment mechanisms">84</part-num-ref>
|
| 397 |
+
and/or <part-num-ref name="and/or">88</part-num-ref>
|
| 398 |
+
with or without the bib <part-num-ref name="bib">66.</part-num-ref>
|
| 399 |
+
</p>
|
| 400 |
+
<p id="p-51" num="51">[0039<confidence value="5">]</confidence>
|
| 401 |
+
In some embodiments, sleeveless vest 64 can be made from a lightweight flame-resistant material, whereas sleeved bib <part-num-ref name="lightweight flame-resistant material, whereas sleeved bib">66</part-num-ref>
|
| 402 |
+
can be made from a heavier more abrasion resistant material. This embodiment may be particularly useful for overhead welding procedures, which can result in molten metal, sparks, and BB<confidence value="5">'</confidence>
|
| 403 |
+
s dropping onto the shoulder area <part-num-ref name="shoulder area">92</part-num-ref>
|
| 404 |
+
of the wearer. Further, this embodiment may be particularly useful in warmer climates enabling the user to remove the sleeved bib <part-num-ref name="sleeved bib">66</part-num-ref>
|
| 405 |
+
and use the vest <part-num-ref name="vest">64</part-num-ref>
|
| 406 |
+
alone or in combination with other protective layers. Additionally, jacket system <part-num-ref name="alone or in combination with other protective layers. Additionally, jacket system">62</part-num-ref>
|
| 407 |
+
enables the owner to replace sleeved bib <part-num-ref name="owner to replace sleeved bib">66</part-num-ref>
|
| 408 |
+
or the vest <part-num-ref name="vest">64</part-num-ref>
|
| 409 |
+
without requiring the replacement of the entire jacket system <part-num-ref name="entire jacket system">62.</part-num-ref>
|
| 410 |
+
This may be beneficial in situations where sleeved bib <part-num-ref name="entire jacket system 62. This may be beneficial in situations where sleeved bib">66</part-num-ref>
|
| 411 |
+
takes the brunt of normal everyday wear and tear. Finally, sleeveless vest <part-num-ref name="brunt of normal everyday wear and tear. Finally, sleeveless vest">64</part-num-ref>
|
| 412 |
+
may be made from various flame resistant fabrics and may even be in the form of a light weight flame-resistant shirt<confidence value="8">.</confidence>
|
| 413 |
+
</p>
|
| 414 |
+
<p id="p-52" num="52">[0040<confidence value="5">]</confidence>
|
| 415 |
+
FIG. 10 illustrates a front view of an alternate embodiment of a flame- resistant article of clothing in the form of pants or trousers <part-num-ref name="form of pants or trousers">102.</part-num-ref>
|
| 416 |
+
Pants <part-num-ref name="form of pants or trousers 102. Pants">102</part-num-ref>
|
| 417 |
+
include a waist section <part-num-ref name="waist section">104,</part-num-ref>
|
| 418 |
+
mid-thigh section <part-num-ref name="waist section 104, mid-thigh section">106,</part-num-ref>
|
| 419 |
+
shin section <part-num-ref name="waist section 104, mid-thigh section 106, shin section">108,</part-num-ref>
|
| 420 |
+
right leg <part-num-ref name="waist section 104, mid-thigh section 106, shin section 108, right leg">110,</part-num-ref>
|
| 421 |
+
and left leg <part-num-ref name="waist section 104, mid-thigh section 106, shin section 108, right leg 110, and left leg">112.</part-num-ref>
|
| 422 |
+
Waist section <part-num-ref name="waist section 104, mid-thigh section 106, shin section 108, right leg 110, and left leg 112. Waist section">104</part-num-ref>
|
| 423 |
+
extends from a top edge <part-num-ref name="top edge">114</part-num-ref>
|
| 424 |
+
to a first edge <part-num-ref name="first edge">116.</part-num-ref>
|
| 425 |
+
Mid-thigh section <part-num-ref name="first edge 116. Mid-thigh section">106</part-num-ref>
|
| 426 |
+
extends from the first edge <part-num-ref name="first edge">116</part-num-ref>
|
| 427 |
+
to a second edge <part-num-ref name="second edge">117.</part-num-ref>
|
| 428 |
+
Likewise, shin section <part-num-ref name="second edge 117. Likewise, shin section">108</part-num-ref>
|
| 429 |
+
extends from second edge <part-num-ref name="extends from second edge">117</part-num-ref>
|
| 430 |
+
to the end of the pants <part-num-ref name="pants">102.</part-num-ref>
|
| 431 |
+
</p>
|
| 432 |
+
<p id="p-53" num="53">[0041] As with the other flame resistant articles of clothing, pants <part-num-ref name="other flame resistant articles of clothing, pants">102</part-num-ref>
|
| 433 |
+
may include a number of flame-resistant layers or flaps. Flap <part-num-ref name="number of flame-resistant layers or flaps. Flap">118</part-num-ref>
|
| 434 |
+
is located on top edge <part-num-ref name="is located on top edge">114</part-num-ref>
|
| 435 |
+
and provides a flame-resistant protective layer to cover male snaps 120A, 120<confidence value="5">B</confidence>
|
| 436 |
+
, and 120C. Similarly, flap <part-num-ref name="flame-resistant protective layer to cover male snaps 120A, 120B, and 120C. Similarly, flap">122</part-num-ref>
|
| 437 |
+
is located at first edge <part-num-ref name="is located at first edge">116</part-num-ref>
|
| 438 |
+
and provides a flame-resistant protective layer to cover male snaps 124A, 124B, and 124C. Further, flap <part-num-ref name="flame-resistant protective layer to cover male snaps 124A, 124B, and 124C. Further, flap">126</part-num-ref>
|
| 439 |
+
is located at second edge <part-num-ref name="is located at second edge">117</part-num-ref>
|
| 440 |
+
and provides a flame-resistant protective layer to cover male snaps 128A, 128B, and 128<confidence value="5">C</confidence>
|
| 441 |
+
. In one of the contemplated embodiments, waist section <part-num-ref name="contemplated embodiments, waist section">104,</part-num-ref>
|
| 442 |
+
mid-thigh section <part-num-ref name="contemplated embodiments, waist section 104, mid-thigh section">106,</part-num-ref>
|
| 443 |
+
and shin section <part-num-ref name="contemplated embodiments, waist section 104, mid-thigh section 106, and shin section">108</part-num-ref>
|
| 444 |
+
may be made from similar or different materials. These may include any of the flame-resistant discussed above or any other suitable material. </p>
|
| 445 |
+
<boundary-data type="header">
|
| 446 |
+
<confidence value="88">11</confidence>
|
| 447 |
+
</boundary-data>
|
| 448 |
+
<boundary-data type="header">20483</boundary-data>
|
| 449 |
+
<p id="p-54" num="54">
|
| 450 |
+
<page-break num="12"/>
|
| 451 |
+
<confidence value="4">1</confidence>
|
| 452 |
+
0042<confidence value="5">1</confidence>
|
| 453 |
+
FIG. <confidence value="5">1</confidence>
|
| 454 |
+
1 illustrates bib <part-num-ref name="illustrates bib">42</part-num-ref>
|
| 455 |
+
partially attached to the right side of pants <part-num-ref name="right side of pants">102</part-num-ref>
|
| 456 |
+
to cover waist region <part-num-ref name="to cover waist region">104</part-num-ref>
|
| 457 |
+
and a portion of mid-thigh region <part-num-ref name="portion of mid-thigh region">106.</part-num-ref>
|
| 458 |
+
As illustrated, flap <part-num-ref name="portion of mid-thigh region 106. As illustrated, flap">118</part-num-ref>
|
| 459 |
+
may be lifted to expose fastening mechanisms 120A, 120B, and 120<confidence value="5">C</confidence>
|
| 460 |
+
. Attachment mechanism 44A, 44B, and 44C may then be coupled to fastening mechanisms 120A, 120B, and 120<confidence value="5">C</confidence>
|
| 461 |
+
. In this particular configuration bib <part-num-ref name="may be lifted to expose fastening mechanisms 120A, 120B, and 120C. Attachment mechanism 44A, 44B, and 44C may then be coupled to fastening mechanisms 120A, 120B, and 120C. In this particular configuration bib">42</part-num-ref>
|
| 462 |
+
provides an additional flame- resistant layer for waist section <part-num-ref name="additional flame- resistant layer for waist section">104</part-num-ref>
|
| 463 |
+
and mid-thigh section <part-num-ref name="and mid-thigh section">106.</part-num-ref>
|
| 464 |
+
This configuration may be particularly useful for a welding application where the user is in a sitting position, such as at a bench, and the user would like to obtain additional protection to these sections. </p>
|
| 465 |
+
<p id="p-55" num="55">
|
| 466 |
+
<confidence value="5">1</confidence>
|
| 467 |
+
0043<confidence value="5">1</confidence>
|
| 468 |
+
Further, bib 42 may also be attached at first edge <part-num-ref name="may also be attached at first edge">116</part-num-ref>
|
| 469 |
+
or second edge <part-num-ref name="or second edge">117</part-num-ref>
|
| 470 |
+
to provide a flame-resistant layer to the entire mid-thigh section <part-num-ref name="entire mid-thigh section">106</part-num-ref>
|
| 471 |
+
and/or shin region <part-num-ref name="and/or shin region">108.</part-num-ref>
|
| 472 |
+
In these configurations, bib <part-num-ref name="and/or shin region 108. In these configurations, bib">42</part-num-ref>
|
| 473 |
+
attaches to the respective snaps 124A-124C and/or 128A-128<confidence value="5">C</confidence>
|
| 474 |
+
located on both the right and left side of pants <part-num-ref name="right and left side of pants">102.</part-num-ref>
|
| 475 |
+
Additionally, a second bib or two independent bibs may be used in conjunction with first bib <part-num-ref name="second bib or two independent bibs may be used in conjunction with first bib">42</part-num-ref>
|
| 476 |
+
to provide protection for each individual leg. For example, additional fastening mechanisms may be located on the back side of the pants <part-num-ref name="pants">102</part-num-ref>
|
| 477 |
+
to enable the wearer to wrap and secure bib <part-num-ref name="wearer to wrap and secure bib">42</part-num-ref>
|
| 478 |
+
around a single leg. This configuration may be particularly useful for a welding application where the user is welding in a bent over position, such as for welding installed piping, and the user would like to provide additional protection to these sections. </p>
|
| 479 |
+
<p id="p-56" num="56">
|
| 480 |
+
<confidence value="5">[</confidence>
|
| 481 |
+
0044<confidence value="5">1</confidence>
|
| 482 |
+
FIG. 12 illustrates a front view <part-num-ref name="front view">132</part-num-ref>
|
| 483 |
+
of an alternate embodiment of a flame- resistant article of clothing in the form of a jumpsuit, coverall, or overalls <part-num-ref name="jumpsuit, coverall, or overalls">130.</part-num-ref>
|
| 484 |
+
</p>
|
| 485 |
+
<p id="p-57" num="57">Coverall 130 includes a top section <part-num-ref name="top section">134,</part-num-ref>
|
| 486 |
+
bottom section <part-num-ref name="top section 134, bottom section">136,</part-num-ref>
|
| 487 |
+
a leg section <part-num-ref name="leg section">138,</part-num-ref>
|
| 488 |
+
a collar <part-num-ref name="collar">140,</part-num-ref>
|
| 489 |
+
shoulder area <part-num-ref name="collar 140, shoulder area">142,</part-num-ref>
|
| 490 |
+
left sleeve <part-num-ref name="collar 140, shoulder area 142, left sleeve">144,</part-num-ref>
|
| 491 |
+
and right sleeve <part-num-ref name="collar 140, shoulder area 142, left sleeve 144, and right sleeve">146.</part-num-ref>
|
| 492 |
+
Top section <part-num-ref name="collar 140, shoulder area 142, left sleeve 144, and right sleeve 146. Top section">134</part-num-ref>
|
| 493 |
+
includes collar <part-num-ref name="includes collar">140</part-num-ref>
|
| 494 |
+
and shoulder area <part-num-ref name="and shoulder area">142</part-num-ref>
|
| 495 |
+
and terminates at a first edge <part-num-ref name="first edge">148.</part-num-ref>
|
| 496 |
+
Bottom section <part-num-ref name="first edge 148. Bottom section">136</part-num-ref>
|
| 497 |
+
extends from first edge <part-num-ref name="extends from first edge">148</part-num-ref>
|
| 498 |
+
to second edge <part-num-ref name="to second edge">150.</part-num-ref>
|
| 499 |
+
Leg section <part-num-ref name="to second edge 150. Leg section">138</part-num-ref>
|
| 500 |
+
extends from second edge <part-num-ref name="extends from second edge">150</part-num-ref>
|
| 501 |
+
downward to include a right leg <part-num-ref name="right leg">152</part-num-ref>
|
| 502 |
+
and a left leg <part-num-ref name="left leg">154</part-num-ref>
|
| 503 |
+
that terminate at a third edge <part-num-ref name="third edge">156.</part-num-ref>
|
| 504 |
+
</p>
|
| 505 |
+
<p id="p-58" num="58">
|
| 506 |
+
<confidence value="5">[</confidence>
|
| 507 |
+
0045<confidence value="5">]</confidence>
|
| 508 |
+
As with the other flame resistant articles of clothing, overall <part-num-ref name="other flame resistant articles of clothing, overall">130</part-num-ref>
|
| 509 |
+
may include a number of flame-resistant layers or flaps. Flap <part-num-ref name="number of flame-resistant layers or flaps. Flap">158</part-num-ref>
|
| 510 |
+
is located at first edge <boundary-data type="header">
|
| 511 |
+
<confidence value="88">12</confidence>
|
| 512 |
+
</boundary-data>
|
| 513 |
+
<page-break num="13"/>
|
| 514 |
+
<boundary-data type="header">20483</boundary-data>
|
| 515 |
+
<part-num-ref name="is located at first edge">148</part-num-ref>
|
| 516 |
+
and provides a flame-resistant protective layer to cover male snaps 160A, 160<confidence value="68">B,</confidence>
|
| 517 |
+
and 160<confidence value="5">C</confidence>
|
| 518 |
+
. Similarly, flap <part-num-ref name="flame-resistant protective layer to cover male snaps 160A, 160B, and 160C. Similarly, flap">162</part-num-ref>
|
| 519 |
+
is located at second edge <part-num-ref name="is located at second edge">150</part-num-ref>
|
| 520 |
+
and provides a flame- resistant protective layer to cover male snaps 164A, 164<confidence value="2">B</confidence>
|
| 521 |
+
, and 164<confidence value="5">C</confidence>
|
| 522 |
+
. In one of the contemplated embodiments, top section <part-num-ref name="contemplated embodiments, top section">134,</part-num-ref>
|
| 523 |
+
bottom section <part-num-ref name="contemplated embodiments, top section 134, bottom section">136,</part-num-ref>
|
| 524 |
+
and leg section <part-num-ref name="contemplated embodiments, top section 134, bottom section 136, and leg section">138</part-num-ref>
|
| 525 |
+
may be made from similar or different materials. These materials may include any of the flame-resistant materials discussed above or any other suitable material. </p>
|
| 526 |
+
<p id="p-59" num="59">
|
| 527 |
+
<confidence value="5">1</confidence>
|
| 528 |
+
0046<confidence value="5">]</confidence>
|
| 529 |
+
FIG. 12 further illustrates bib <part-num-ref name="further illustrates bib">42</part-num-ref>
|
| 530 |
+
removably attached to coveralls <part-num-ref name="removably attached to coveralls">130</part-num-ref>
|
| 531 |
+
at second edge <part-num-ref name="at second edge">150.</part-num-ref>
|
| 532 |
+
As shown in the figure, flap <part-num-ref name="figure, flap">162</part-num-ref>
|
| 533 |
+
may be lifted to expose fastening mechanisms 164A, <part-num-ref name="may be lifted to expose fastening mechanisms 164A,">164<confidence value="2">8</confidence>
|
| 534 |
+
, </part-num-ref>
|
| 535 |
+
and 164C, thereby enabling attachment mechanisms 44A- 44F to be coupled thereto. In this particular configuration, bib <part-num-ref name="may be lifted to expose fastening mechanisms 164A, 1648, and 164C, thereby enabling attachment mechanisms 44A- 44F to be coupled thereto. In this particular configuration, bib">42</part-num-ref>
|
| 536 |
+
provides an additional flame-resistant layer to cover the waist region and leg section <part-num-ref name="waist region and leg section">138.</part-num-ref>
|
| 537 |
+
Further, bib <part-num-ref name="waist region and leg section 138. Further, bib">42</part-num-ref>
|
| 538 |
+
may also be attached to first edge <part-num-ref name="may also be attached to first edge">148</part-num-ref>
|
| 539 |
+
to provide a flame-resistant layer to cover bottom section <part-num-ref name="flame-resistant layer to cover bottom section">136</part-num-ref>
|
| 540 |
+
and leg section <part-num-ref name="and leg section">138.</part-num-ref>
|
| 541 |
+
Finally, coveralls <part-num-ref name="and leg section 138. Finally, coveralls">130</part-num-ref>
|
| 542 |
+
may include additional fastening mechanisms that enable a wearer to provide added flame-resistant protection to other areas of the garment. For example, coverall <part-num-ref name="garment. For example, coverall">130</part-num-ref>
|
| 543 |
+
could include additional fastening mechanisms similar to those illustrated in FIGS. 6 and <part-num-ref name="and">10,</part-num-ref>
|
| 544 |
+
for instance, on top of the shoulder area or at different locations along right leg <part-num-ref name="shoulder area or at different locations along right leg">152</part-num-ref>
|
| 545 |
+
or left leg <part-num-ref name="or left leg">154.</part-num-ref>
|
| 546 |
+
Additionally, although the figure illustrates male snaps, the fastening mechanism is not limited to a snap fastener system. </p>
|
| 547 |
+
<p id="p-60" num="60">
|
| 548 |
+
<confidence value="588885">100471</confidence>
|
| 549 |
+
While only certain features of the invention have been illustrated and described herein, many modifications and changes will occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention. </p>
|
| 550 |
+
<boundary-data type="header">
|
| 551 |
+
<confidence value="88">13</confidence>
|
| 552 |
+
</boundary-data>
|
| 553 |
+
</description>
|
| 554 |
+
</us-patent-application>
|
| 555 |
+
|
applicant/11746263.xml
ADDED
|
@@ -0,0 +1,318 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11746263</doc-number>
|
| 8 |
+
<date>2007-05-09</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">Attorney Docket No. 279.D4<confidence value="5885">8US1</confidence>
|
| 14 |
+
</boundary-data>
|
| 15 |
+
<heading id="h-1">NEURAL STIMULATION SYSTEM ANALYZER</heading>
|
| 16 |
+
<heading id="h-2">TECHNICAL FIELD</heading>
|
| 17 |
+
<p id="p-1" num="1">[0001] This application relates generally to medical devices and, more particularly, to systems, devices and methods for analyzing neural stimulation systems.</p>
|
| 18 |
+
<heading id="h-3">BACKGROUND</heading>
|
| 19 |
+
<p id="p-2" num="2">[0002] Neural stimulation has been proposed to treat a number conditions. For example, vagal stimulation has been proposed to treat cardiovascular conditions such as heart failure, post-MI remodeling, hypertension, tachyarrhythmias, and atherosclerosis. Vagal stimulation has also been proposed to treat non-cardiovascular conditions such as epilepsy, depression, pain, obesity and diabetes. Implantable devices can be used to deliver neural stimulation.</p>
|
| 20 |
+
<heading id="h-4">SUMMARY</heading>
|
| 21 |
+
<p id="p-3" num="3">
|
| 22 |
+
<confidence value="5">[</confidence>
|
| 23 |
+
0003] Various embodiments relate to a device to analyze an implantable neural stimulation system that includes an implantable neural stimulation lead for an implantable neural stimulator to be implanted into a patient. Various device embodiments comprise an external housing, a pacing circuit in the housing, and a sensing circuit in the housing. The pacing circuit is adapted to deliver a test neural stimulation signal. At least one test lead cable is adapted to electrically connect the pacing circuit and the implantable neural stimulation lead to enable the test neural stimulation signal to be delivered to a neural target through the test lead cable and the implantable neural stimulation lead. At least one physiological sensor is adapted to sense a physiological response to stimulation of the neural target. At least one sensor cable is adapted to electrically connect the sensing circuit and the at least one physiological sensor. </p>
|
| 24 |
+
<p id="p-4" num="4">
|
| 25 |
+
<confidence value="5">[</confidence>
|
| 26 |
+
0004<confidence value="5">]</confidence>
|
| 27 |
+
Various device embodiments comprise an external housing, a pacing circuit in the housing, where the pacing circuit is adapted to deliver a test neural stimulation signal. At least one test lead cable is adapted to electrically connect the <boundary-data type="header">
|
| 28 |
+
<confidence value="7">1</confidence>
|
| 29 |
+
</boundary-data>
|
| 30 |
+
<page-break num="2"/>
|
| 31 |
+
<boundary-data type="header">Attorney Docket No. 279.D48US <confidence value="8">1</confidence>
|
| 32 |
+
</boundary-data>
|
| 33 |
+
pacing circuit and the implantable neural stimulation lead to enable the test neural stimulation signal to be delivered to a vagus nerve through the test lead cable and the implantable neural stimulation lead. The at least one test lead cable includes at least one clip to connect to at least one terminal of the neural stimulation lead. The device includes a sensing circuit in the housing, a plurality of ECG electrodes adapted for use in detecting an electrocardiogram, and at least one sensor cable adapted to electrically connect the sensing circuit and the plurality of ECG electrodes. A controller is adapted to communicate with the pacing circuit and the sensing circuit to process the electrocardiogram for use in identifying a response to stimulation of the vagus nerve. </p>
|
| 34 |
+
<p id="p-5" num="5">
|
| 35 |
+
<confidence value="5">[</confidence>
|
| 36 |
+
0005<confidence value="5">]</confidence>
|
| 37 |
+
Various system embodiments for analyzing an implantable neural stimulation system comprise means for connecting a test lead cable for an external analyzer to at least one terminal of <confidence value="5">a</confidence>
|
| 38 |
+
n implantable neural stimulation lead, means for delivering test neural stimulation using an external neural stimulation through the test lead cable and the neural stimulation to a neural target, and means for monitoring a physiologic response to the test neural stimulation. </p>
|
| 39 |
+
<p id="p-6" num="6">[0006] An embodiment relates to a method for analyzing an implantable neural stimulation system. A neural stimulation lead is implanted. The lead is adapted to be used to deliver neural stimulation to a neural target. A test lead cable for an external analyzer is connected to at least one terminal of the neural stimulation lead. Test neural stimulation is delivered using an external neural stimulation through the test lead cable and the neural stimulation to the neural target. A physiologic response to the test neural stimulation is monitored.</p>
|
| 40 |
+
<p id="p-7" num="7">[0007] This Summary is an overview of some of the teachings of the present application and not intended to be an exclusive or exhaustive treatment of the present subject matter. Further details about the present subject matter are found in the detailed description and appended claims. Other aspects will be apparent to persons skilled in the art upon reading and understanding the following detailed description and viewing the drawings that form a part thereof, each of which are not to be taken in a limiting sense. The scope of the present invention is defined by the appended claims and their equivalents.</p>
|
| 41 |
+
<boundary-data type="header">
|
| 42 |
+
<confidence value="8">2</confidence>
|
| 43 |
+
</boundary-data>
|
| 44 |
+
<boundary-data type="header">Attorney Docket No. 279.D48US <confidence value="8">1</confidence>
|
| 45 |
+
</boundary-data>
|
| 46 |
+
<heading id="h-5">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 47 |
+
<p id="p-8" num="8">
|
| 48 |
+
<page-break num="3"/>
|
| 49 |
+
<confidence value="5">[</confidence>
|
| 50 |
+
0008<confidence value="5">]</confidence>
|
| 51 |
+
FIG. 1 illustrates an embodiment of a neural stimulation system analyzer. </p>
|
| 52 |
+
<p id="p-9" num="9">[0009] FIG. 2 illustrates an implantable neural stimulator and an embodiment of a neural stimulation system analyzer.</p>
|
| 53 |
+
<p id="p-10" num="10">[0010<confidence value="5">]</confidence>
|
| 54 |
+
FIG. 3 illustrates an embodiment of a neural stimulation system analyzer with a test lead cable connected to a bipolar neural stimulation lead and with a sensor cable connected to ECG electrodes to be placed on a patient's skin. </p>
|
| 55 |
+
<p id="p-11" num="11">[0011] FIG. 4 illustrates a block diagram for an embodiment of a neural stimulation system analyzer.</p>
|
| 56 |
+
<p id="p-12" num="12">[0012] FIG. 5 illustrates a more detailed block diagram for the neural stimulation system analyzer embodiment illustrated in FIG. 4.</p>
|
| 57 |
+
<heading id="h-6">DETAILED DESCRIPTION</heading>
|
| 58 |
+
<p id="p-13" num="13">[0013] The following detailed description of the present subject matter refers to the accompanying drawings which show, by way of illustration, specific aspects and embodiments in which the present subject matter may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the present subject matter. Other embodiments may be utilized and structural, logical, and electrical changes may be made without departing from the scope of the present subject matter. References to "an", "one", or "various" embodiments in this disclosure are not necessarily to the same embodiment, and such references contemplate more than one embodiment. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope is defined only by the appended claims, along with the full scope of legal equivalents to which such claims are entitled.</p>
|
| 59 |
+
<p id="p-14" num="14">[0014] The present subject matter relates to a neural stimulation system analyzer, which is an external device used acutely during a neural stimulator system implant to test system integrity and titrate therapy. An embodiment of the neural stimulation system analyzer uses two interface cables, where one interface cable is a <boundary-data type="header">
|
| 60 |
+
<confidence value="8">3</confidence>
|
| 61 |
+
</boundary-data>
|
| 62 |
+
<page-break num="4"/>
|
| 63 |
+
<boundary-data type="header">Attorney Docket No. 279.D48US<confidence value="5">1</confidence>
|
| 64 |
+
</boundary-data>
|
| 65 |
+
lead test cable, and the other is a sensor cable. The lead test cable is adapted to be operably attached to an implantable neural stimulation lead for use in testing the lead. </p>
|
| 66 |
+
<p id="p-15" num="15">In an example where the implantable neural stimulation lead is a bipolar lead, the lead test cable is a bipolar cable. An embodiment of the lead test cable terminates in alligator clips, which can be used to attach the bipolar test cable to the bipolar implantable neural stimulation lead. Other connectors or clamps adapted to quickly make and break an electrical and mechanical connection between the lead test cable and the implantable neural stimulation cable can be used. An embodiment of the sensor cable is a multipolar cable that terminates in two or more ECG button connectors to be placed on the patient's skin.</p>
|
| 67 |
+
<p id="p-16" num="16">[0015<confidence value="5">]</confidence>
|
| 68 |
+
In some embodiments, the neural stimulation system analyzer measures neural lead impedance to determine system integrity. Some embodiments deliver a burst of neural stimulation and acutely measure a physiologic response, such as heart rate or heart rate variability (HRV) using surface ECG electrodes. Neural stimulation parameters can be adjusted, as necessary, at implant to achieve a desired change in the physiologic parameter and determine the physiologic stimulation threshold. Some device embodiments automatically determine the stimulation threshold by adjusting stimulation parameters and measuring the resulting change in the physiologic parameter. </p>
|
| 69 |
+
<p id="p-17" num="17">
|
| 70 |
+
<confidence value="5">[</confidence>
|
| 71 |
+
0016<confidence value="5">1</confidence>
|
| 72 |
+
The neural stimulation system analyzer is adapted to test the integrity of an implantable neural stimulator, and the placement of the stimulator electrodes to capture an autonomic nervous system (ANS) target, such as a vagus nerve. </p>
|
| 73 |
+
<p id="p-18" num="18">Implantable neural stimulation can deliver vagal modulation to treat a variety of cardiovascular disorders, including heart failure, post-MI remodeling, and hypertension. ANS and some cardiovascular disorders are briefly described below.</p>
|
| 74 |
+
<p id="p-19" num="19">
|
| 75 |
+
<confidence value="5">[</confidence>
|
| 76 |
+
0017<confidence value="5">]</confidence>
|
| 77 |
+
Some embodiments of the neural stimulation analyzer deliver test neural stimulation, monitor a physiologic response to the neural stimulation, and titrate parameter(s) of the test neural stimulation as may be necessary to realize the target physiologic response. Amplitude, frequency, pulse duration, duty cycle or other parameters can be adjusted to adjust the neural stimulation intensity. Various device <boundary-data type="header">
|
| 78 |
+
<confidence value="8">4</confidence>
|
| 79 |
+
</boundary-data>
|
| 80 |
+
<page-break num="5"/>
|
| 81 |
+
<boundary-data type="header">Attorney Docket No. 279.D4<confidence value="5">8</confidence>
|
| 82 |
+
US1 </boundary-data>
|
| 83 |
+
embodiments include a pacing circuit, a sensing circuit, and a controller to communicate with the pacing circuit and the sensing circuit to receive a sensed physiologic response, and automatically adjust an intensity of the test neural stimulation signal until the sensed physiologic response corresponds to a target physiologic response. Thus, for example, a physician can connect the analyzer to the implantable lead, and initiate the start of the analysis, and the analyzer automatically adjusts the stimulation parameter(s) to achieve the desired response. The parameters of the test neural stimulation that realize the target response can be programmed into the implantable neural stimulator. </p>
|
| 84 |
+
<p id="p-20" num="20">[0018] The ANS regulates "involuntary" organs, while the contraction of voluntary (skeletal) muscles is controlled by somatic motor nerves. Examples of involuntary organs include respiratory and digestive organs, and also include blood vessels and the heart. Often, the ANS functions in an involuntary, reflexive manner to regulate glands, to regulate muscles in the skin, eye, stomach, intestines and bladder, and to regulate cardiac muscle and the muscle around blood vessels, for example.</p>
|
| 85 |
+
<p id="p-21" num="21">[0019] The ANS includes the sympathetic nervous system and the parasympathetic nervous system. The sympathetic nervous system is affiliated with stress and the "fight or flight response" to emergencies. Among other effects, the "fight or flight response" increases blood pressure and heart rate to increase skeletal muscle blood flow, and decreases digestion to provide the energy for "fighting or fleeing." The parasympathetic nervous system is affiliated with relaxation and the "rest and digest response" which, among other effects, decreases blood pressure and heart rate, and increases digestion to conserve energy. The ANS maintains normal internal function and works with the somatic nervous system.</p>
|
| 86 |
+
<p id="p-22" num="22">[0020<confidence value="5">]</confidence>
|
| 87 |
+
The heart rate and force is increased when the sympathetic nervous system is stimulated, and is decreased when the sympathetic nervous system is inhibited (the parasympathetic nervous system is stimulated). An afferent neural pathway conveys impulses toward a nerve center. An efferent neural pathway conveys impulses away from a nerve center. </p>
|
| 88 |
+
<boundary-data type="header">
|
| 89 |
+
<confidence value="8">5</confidence>
|
| 90 |
+
</boundary-data>
|
| 91 |
+
<boundary-data type="header">Attorney Docket No. 279.D4<confidence value="5885">8US1</confidence>
|
| 92 |
+
</boundary-data>
|
| 93 |
+
<p id="p-23" num="23">
|
| 94 |
+
<page-break num="6"/>
|
| 95 |
+
[0021] Stimulating the sympathetic and parasympathetic nervous systems can have effects other than heart rate and blood pressure. For example, stimulating the sympathetic nervous system dilates the pupil, reduces saliva and mucus production, relaxes the bronchial muscle, reduces the successive waves of involuntary contraction (peristalsis) of the stomach and the motility of the stomach, increases the conversion of glycogen to glucose by the liver, decreases urine secretion by the kidneys, and relaxes the wall and closes the sphincter of the bladder. Stimulating the parasympathetic nervous system (inhibiting the sympathetic nervous system) constricts the pupil, increases saliva and mucus production, contracts the bronchial muscle, increases secretions and motility in the stomach and large intestine, increases digestion in the small intention, increases urine secretion, and contracts the wall and relaxes the sphincter of the bladder. The f<confidence value="8">u</confidence>
|
| 96 |
+
nctions associated with the sympathetic and parasympathetic nervous systems are many and can be complexly integrated with each other. </p>
|
| 97 |
+
<p id="p-24" num="24">[0022] Heart failure refers to a clinical syndrome in which cardiac f<confidence value="8">u</confidence>
|
| 98 |
+
nction causes a below normal cardiac output that can fall below a level adequate to meet the metabolic demand of peripheral tissues. Heart failure may present itself as congestive heart failure (CHF) due to the accompanying venous and pulmonary congestion. </p>
|
| 99 |
+
<p id="p-25" num="25">Heart failure can be due to a variety of etiologies such as ischemic heart disease.</p>
|
| 100 |
+
<p id="p-26" num="26">
|
| 101 |
+
<confidence value="5">[</confidence>
|
| 102 |
+
0023] Hypertension is a cause of heart disease and other related cardiac co- morbidities. Hypertension occurs when blood vessels constrict. As a result, the heart works harder to maintain flow at a higher blood pressure, which can contribute to heart failure. Hypertension generally relates to high blood pressure, such as a transitory or sustained elevation of systemic arterial blood pressure to a level that is likely to induce cardiovascular damage or other adverse consequences. Hypertension has been arbitrarily defined as a systolic blood pressure above 140 mm Hg or a diastolic blood pressure above 90 mm Hg. Consequences of uncontrolled hypertension include, but are not limited to, retinal vascular disease and stroke, left ventricular hypertrophy and failure, myocardial infarction, dissecting aneurysm, and renovascular disease. </p>
|
| 103 |
+
<boundary-data type="header">
|
| 104 |
+
<confidence value="8">6</confidence>
|
| 105 |
+
</boundary-data>
|
| 106 |
+
<boundary-data type="header">Attorney Docket No. 279.D4<confidence value="5">8</confidence>
|
| 107 |
+
US1 </boundary-data>
|
| 108 |
+
<p id="p-27" num="27">
|
| 109 |
+
<page-break num="7"/>
|
| 110 |
+
[0024<confidence value="5">]</confidence>
|
| 111 |
+
Cardiac remodeling refers to a complex remodeling process of the ventricles that involves structural, biochemical, neurohormonal, and electrophysiologic factors, which can result following a myocardial infarction (MI) or other cause of decreased cardiac output. Ventricular remodeling is triggered by a physiological compensatory mechanism that acts to increase cardiac output due to so- called backward failure which increases the diastolic filling pressure of the ventricles and thereby increases the so-called preload (i.e., the degree to which the ventricles are stretched by the volume of blood in the ventricles at the end of diastole). An increase in preload causes an increase in stroke volume during systole, a phenomena known as the Frank-Starling principle. When the ventricles are stretched due to the increased preload over a period of time, however, the ventricles become dilated. The enlargement of the ventricular volume causes increased ventricular wall stress at a given systolic pressure. Along with the increased pressure-volume work done by the ventricle, this acts as a stimulus for hypertrophy of the ventricular myocardium. The disadvantage of dilatation is the extra workload imposed on normal, residual myocardium and the increase in wall tension (Laplace's Law) which represent the stimulus for hypertrophy. If hypertrophy is not adequate to match increased tension, a vicious cycle ensues which causes further and progressive dilatation. As the heart begins to dilate, afferent baroreceptor and cardiopulmonary receptor signals are sent to the vasomotor central nervous system control center, which responds with hormonal secretion and sympathetic discharge. It is the combination of hemodynamic, sympathetic nervous system and hormonal alterations (such as presence or absence of angiotensin converting enzyme (ACE) activity) that ultimately account for the deleterious alterations in cell structure involved in ventricular remodeling. The sustained stresses causing hypertrophy induce apoptosis (i.e., programmed cell death) of cardiac muscle cells and eventual wall thinning which causes further deterioration in cardiac function. Thus, although ventricular dilation and hypertrophy may at first be compensatory and increase cardiac output, the processes ultimately result in both systolic and diastolic dysfunction. It has been shown that the extent of ventricular <boundary-data type="header">
|
| 112 |
+
<confidence value="8">7</confidence>
|
| 113 |
+
</boundary-data>
|
| 114 |
+
<page-break num="8"/>
|
| 115 |
+
<boundary-data type="header">Attorney Docket No. 279.D48US <confidence value="8">1</confidence>
|
| 116 |
+
</boundary-data>
|
| 117 |
+
remodeling is positively correlated with increased mortality in post-MI and heart failure patients. </p>
|
| 118 |
+
<p id="p-28" num="28">
|
| 119 |
+
<confidence value="86">[0</confidence>
|
| 120 |
+
025] The present subject matter relates to a neural stimulation analyzer that delivers test neural stimulation to an implantable neural stimulation lead. The neural stimulation system analyzer is adapted to detect a physiologic response to a test neural stimulation to determine whether the test neural stimulation is effective. The monitored physiologic response should be a quick response that indicates that the neural target has been stimulated. For example, heart rate, heart rate variability (HRV) and/or heart rate turbulence (HRT) can be monitored when a test neural stimulation is delivered to the vagus nerve. </p>
|
| 121 |
+
<p id="p-29" num="29">[0026<confidence value="5">]</confidence>
|
| 122 |
+
HRV relates to the regulation of the sinoatrial node, the natural pacemaker of the heart by the sympathetic and parasympathetic branches of the autonomic nervous system. The time interval between intrinsic ventricular heart contractions changes in response to the body's metabolic need for a change in heart rate and the amount of blood pumped through the circulatory system. For example, during a period of exercise or other activity, a person's intrinsic heart rate will generally increase over a given period of time. However, even on a beat-to-beat basis, that is, from one heart beat to the next, and without exercise, the time interval between intrinsic heart contractions varies in a normal person. These beat-to-beat variations in intrinsic heart rate are the result of proper regulation by the autonomic nervous system on blood pressure and cardiac output; the absence of such variations indicates a possible deficiency in the regulation being provided by the autonomic nervous system. </p>
|
| 123 |
+
<p id="p-30" num="30">One method for analyzing HRV involves detecting intrinsic ventricular contractions, and recording the time intervals between these contractions, referred to as the R-R intervals, after filtering out any ectopic contractions (ventricular contractions that are not the result of a normal sinus rhythm). This signal of R-R intervals is typically transformed into the frequency-domain, such as by using fast Fourier transform (FFT) techniques, so that its spectral frequency components can be analyzed and divided into low and high frequency bands. For example, the low frequency (LF) band can correspond to a frequency (f) range 0.04 Hz <confidence value="5"><</confidence>
|
| 124 |
+
<confidence value="8">f</confidence>
|
| 125 |
+
< 0.15 Hz, and the high frequency <boundary-data type="header">
|
| 126 |
+
<confidence value="8">8</confidence>
|
| 127 |
+
</boundary-data>
|
| 128 |
+
<page-break num="9"/>
|
| 129 |
+
<boundary-data type="header">Attorney Docket No. 279.D48US1</boundary-data>
|
| 130 |
+
(HF) band can correspond to a frequency range 0.15 Hz <confidence value="5"><</confidence>
|
| 131 |
+
<confidence value="8">f</confidence>
|
| 132 |
+
<confidence value="5"><</confidence>
|
| 133 |
+
0.40 Hz. The HF band of the R-R interval signal is influenced only by the parasympathetic/vagal component of the autonomic nervous system. The L<confidence value="5">F</confidence>
|
| 134 |
+
band of the R-R interval signal is influenced by both the sympathetic and parasympathetic components of the autonomic nervous system. Consequently, the ratio LF/HF is regarded as a good indication of the autonomic balance between sympathetic and parasympathetic/vagal components of the autonomic nervous system. An increase in the LF<confidence value="66">/H</confidence>
|
| 135 |
+
F ratio indicates an increased predominance of the sympathetic component, and a decrease in the LF/HF ratio indicates an increased predominance of the parasympathetic component. Thus, in an embodiment in which vagal stimulation is delivered to enhance nerve activity in the vagus nerve, effective vagal stimulation is expected to elicit a parasympathetic response which can be detected by a decrease in the LF/HF ratio. Neural stimulation can also be delivered to inhibit nerve traffic. Neural stimulation to inhibit nerve activity in the vagus nerve is expected to elicit a sympathetic response which can be detected by an increase in the LF/HF ratio. A spectral analysis of the frequency components of the R-R interval signal can be performed using a F<confidence value="5">F</confidence>
|
| 136 |
+
T (or other parametric transformation, such as autoregression) technique from the time domain into the frequency domain. One example of a HRV parameter is SDANN (standard deviation of averaged NN intervals), which represents the standard deviation of the means of all the successive <part-num-ref name="successive">5</part-num-ref>
|
| 137 |
+
minutes segments contained in a whole recording. Other HRV parameters can be used. </p>
|
| 138 |
+
<p id="p-31" num="31">[0027] HRT is the physiological response of the sinus node to a premature ventricular contraction (PVC), consisting of a short initial heart rate acceleration followed by a heart rate deceleration. HRT has been shown to be an index of autonomic function, closely correlated to HRV, and is believed to be due to the autonomic baroreflex. The PVC causes a brief disturbance of the arterial blood pressure (low amplitude of the premature beat, high amplitude of the ensuing normal beat), which instantaneously responds in the form of HRT if the autonomic system is healthy, but is either weakened or missing if the autonomic system is impaired. By way of example and not limitation, it has been proposed to quantify HRT using <boundary-data type="header">
|
| 139 |
+
<confidence value="8">9</confidence>
|
| 140 |
+
</boundary-data>
|
| 141 |
+
<page-break num="10"/>
|
| 142 |
+
<boundary-data type="header">Attorney Docket No. 279.D48US<confidence value="8">1</confidence>
|
| 143 |
+
</boundary-data>
|
| 144 |
+
Turbulence Onset (TO) and Turbulence Slope (TS). TO refers to the difference between the heart rate immediately before and after a PVC, and can be expressed as a percentage. For example, if two beats are evaluated before and after the PVC, TO can be expressed as: </p>
|
| 145 |
+
<p id="p-32" num="32">TO%<confidence value="22">-=</confidence>
|
| 146 |
+
(RR<confidence value="17288112">u+,RR±2)</confidence>
|
| 147 |
+
-(R<confidence value="17121">KRJRi</confidence>
|
| 148 |
+
)*1<confidence value="22">00</confidence>
|
| 149 |
+
<confidence value="2722">(RR-</confidence>
|
| 150 |
+
2 + R<confidence value="2217">R_1)</confidence>
|
| 151 |
+
<confidence value="88">RR</confidence>
|
| 152 |
+
2 and RR<confidence value="1">1</confidence>
|
| 153 |
+
are the first two normal intervals preceding the PVC and R<confidence value="8">R</confidence>
|
| 154 |
+
and RR+2 are the first two normal intervals following the PVC. In various embodiments, TO is determined for each individual PVC, and then the average value of all individual measurements is determined. However, TO does not have to be averaged over many measurements, but can be based on one PVC event. Positive TO values indicate deceleration of the sinus rhythm, and negative values indicate acceleration of the sinus rhythm. The number of R-R intervals analyzed before and after the PVC can be adjusted according to a desired application. TS, for example, can be calculated as the steepest slope of linear regression for each sequence of five R-R intervals. In various embodiments, the TS calculations are based on the averaged tachogram and expressed in milliseconds per RR interval. However, TS can be determined without averaging. </p>
|
| 155 |
+
<p id="p-33" num="33">The number of R-R intervals in a sequence used to determine a linear regression in the TS calculation also can be adjusted according to a desired application. Rules or criteria can be provided for use to select PVCs and for use in selecting valid RR intervals before and after the PVCs. A PVC event can be defined by an R-R interval in some interval range that is shorter than a previous interval by some time or percentage, or it can be defined by an R-R interval without an intervening P-wave (atrial event) if the atrial events are measured. Various embodiments select PVCs only if the contraction occurs at a certain range from the preceding contraction and if the contraction occurs within a certain range from a subsequent contraction. For example, various embodiments limit the HRT calculations to PVCs with a minimum prematurity of 20% and a post-extrasystole interval which is at least 20% longer than the normal interval. Additionally, pre-PVC R-R and post-PVC R-R intervals are considered to be valid if they satisfy the condition that none of the beats are PVCs.</p>
|
| 156 |
+
<boundary-data type="header">
|
| 157 |
+
<confidence value="88">10</confidence>
|
| 158 |
+
</boundary-data>
|
| 159 |
+
<boundary-data type="header">Attorney Docket No. 279.D48US <confidence value="8">1</confidence>
|
| 160 |
+
</boundary-data>
|
| 161 |
+
<p id="p-34" num="34">
|
| 162 |
+
<page-break num="11"/>
|
| 163 |
+
One HRT process, for example, excludes <confidence value="5">R</confidence>
|
| 164 |
+
R intervals that are less than a first time duration, that are longer than a second time duration, that differ from a preceding interval by more than a third time duration, or that differ from a reference interval by a predetermined amount time duration or percentage. In an embodiment of such an HRT process with specific values, <confidence value="5">R</confidence>
|
| 165 |
+
R intervals are excluded if they are less than 300 <confidence value="5">m</confidence>
|
| 166 |
+
s, are more than 2000 <confidence value="5">m</confidence>
|
| 167 |
+
s, differ from a preceding interval by more than 200 <confidence value="5">m</confidence>
|
| 168 |
+
s, or differ by more than 20% from the mean of the last five sinus intervals. Various embodiments of the present subject matter provide programmable parameters, such as any of the parameters identified above, for use in selecting PVCs and for use in selecting valid <confidence value="5">R</confidence>
|
| 169 |
+
R intervals before and after the PVCs. Benefits of using HRT to monitor autonomic balance include the ability to measure autonomic balance at a single moment in time. Additionally, unlike the measurement of HRV, HRT assessment can be performed in patients with frequent atrial pacing. Further, HRT analysis provides for a simple, non-processor-intensive measurement of autonomic balance. Thus, data processing, data storage, and data flow are relatively small, resulting in a device with less cost and less power consumption. Also, HRT assessment is faster than HRV, requiring much less <confidence value="686">R-R</confidence>
|
| 170 |
+
data. HRT allows assessment over short recording periods similar in duration to typical neural stimulation burst durations, such as on the order of tens of seconds, for example. </p>
|
| 171 |
+
<p id="p-35" num="35">[0028] FIG. 1 illustrates an embodiment of a neural stimulation system analyzer.</p>
|
| 172 |
+
<p id="p-36" num="36">The illustrated neural stimulation system analyzer 100 is an external device. The illustrated external device is adapted to use a test lead cable <part-num-ref name="test lead cable">101</part-num-ref>
|
| 173 |
+
to temporarily and operationally connect to an implantable neural stimulation lead <part-num-ref name="implantable neural stimulation lead">102,</part-num-ref>
|
| 174 |
+
which will be connected to an implantable pulse generator housing for a neural stimulator (not shown). The illustrated neural stimulation lead is illustrated in the cervical region of the patient, where the right vagus nerve, for example, could be targeted for neural stimulation. Various embodiments intravascularly feed the neural stimulation lead to a position proximate a desired neural target to transvascularly stimulate the neural target. For example, a neural stimulation lead can be fed into an internal jugular vein to stimulate a vagus nerve. Various embodiments transcutaneously tunnel the neural <boundary-data type="header">
|
| 175 |
+
<confidence value="88">11</confidence>
|
| 176 |
+
</boundary-data>
|
| 177 |
+
<page-break num="12"/>
|
| 178 |
+
<boundary-data type="header">Attorney Docket No. 279.D48US <confidence value="8">1</confidence>
|
| 179 |
+
</boundary-data>
|
| 180 |
+
stimulation lead to the desired neural target. The illustrated analyzer is adapted to use at least one sensor cable <part-num-ref name="illustrated analyzer is adapted to use at least one sensor cable">103,</part-num-ref>
|
| 181 |
+
such as a multipolar sensor cable, connected to two or more E<confidence value="5">C</confidence>
|
| 182 |
+
G electrodes <part-num-ref name="multipolar sensor cable, connected to two or more ECG electrodes">104</part-num-ref>
|
| 183 |
+
for use in detecting electrical activity of the heart. For example, the ECG electrodes can be used to detect heart rate, HRV, and HRT. Some embodiments use other physiologic parameter sensors such as respiration or blood pressure sensors, either in place of or in addition to, the <confidence value="5">E</confidence>
|
| 184 |
+
CG electrodes. </p>
|
| 185 |
+
<p id="p-37" num="37">[0029<confidence value="5">]</confidence>
|
| 186 |
+
The neural system analyzer <part-num-ref name="neural system analyzer">100</part-num-ref>
|
| 187 |
+
is adapted to deliver neural stimulation to the neural target through the test lead cable <part-num-ref name="test lead cable">101</part-num-ref>
|
| 188 |
+
and the implantable neural stimulation lead <part-num-ref name="implantable neural stimulation lead">102.</part-num-ref>
|
| 189 |
+
The analyzer <part-num-ref name="analyzer">100</part-num-ref>
|
| 190 |
+
is also adapted to sense a physiological response indicative of whether the neural target is being stimulated. The E<confidence value="68">CG</confidence>
|
| 191 |
+
electrodes can detect electrocardiograms, which can be used to detect heart rate. The detected heart rate can be used to perform heart rate variability (HRV) and heart rate turbulence (HRT) tests. Heart rate, HRV and HRT are examples of physiologic measurements that can indicate whether neural stimulation captured a desired target of the autonomic nervous system. Thus, for example, the neural stimulation lead can be appropriately moved to capture the neural target. Some embodiments of the external device verify the integrity of the neural stimulation lead, such as may be performed by testing the impedance of the lead. A high impedance, for example, may indicate a broken conductor in the lead. </p>
|
| 192 |
+
<p id="p-38" num="38">
|
| 193 |
+
<confidence value="5">[</confidence>
|
| 194 |
+
0030<confidence value="5">]</confidence>
|
| 195 |
+
The illustrated analyzer <part-num-ref name="illustrated analyzer">100</part-num-ref>
|
| 196 |
+
includes a user interface with an input <part-num-ref name="input">105</part-num-ref>
|
| 197 |
+
such as buttons and an output such as a display <part-num-ref name="display">106.</part-num-ref>
|
| 198 |
+
The buttons can be used to control the delivery of the test neural stimulation, and the display can be used to show a correlation between the neural stimulation and the monitored physiological response that indicates a successive test stimulation. </p>
|
| 199 |
+
<p id="p-39" num="39">
|
| 200 |
+
<confidence value="5">[</confidence>
|
| 201 |
+
0031<confidence value="5">]</confidence>
|
| 202 |
+
FIG. 2 illustrates an implantable neural stimulator <part-num-ref name="implantable neural stimulator">207</part-num-ref>
|
| 203 |
+
and an embodiment of a neural stimulation system analyzer <part-num-ref name="neural stimulation system analyzer">200.</part-num-ref>
|
| 204 |
+
The illustrated implantable neural stimulator <part-num-ref name="illustrated implantable neural stimulator">207</part-num-ref>
|
| 205 |
+
is placed subcutaneously or submuscularly in a patient's chest with lead(s) <part-num-ref name="patient's chest with lead(s)">208</part-num-ref>
|
| 206 |
+
positioned to stimulate a neural target in the cervical region (e.g. a vagus nerve). The illustrated system provides a lead to the right vagus nerve. The lead could be routed to the left vagus nerve. Some embodiments use leads to stimulate <boundary-data type="header">
|
| 207 |
+
<confidence value="88">12</confidence>
|
| 208 |
+
</boundary-data>
|
| 209 |
+
<page-break num="13"/>
|
| 210 |
+
<boundary-data type="header">Attorney Docket No. 279.D4<confidence value="5888">8US1</confidence>
|
| 211 |
+
</boundary-data>
|
| 212 |
+
both the left and <confidence value="8">r</confidence>
|
| 213 |
+
ight vagus nerve. According to various embodiments, neural stimulation lead(s) <part-num-ref name="left and right vagus nerve. According to various embodiments, neural stimulation lead(s)">208</part-num-ref>
|
| 214 |
+
are subcutaneously tunneled to a neural target, and can have a nerve cuff electrode to stimulate the neural target. Some vagus nerve stimulation lead embodiments are intravascularly fed into a vessel proximate to the neural target, and use electrode(s) within the vessel to transvascularly stimulate the neural target. For example, some embodiments stimulate the vagus using electrode(s) positioned within the internal jugular vein. The neural targets can be stimulated using other energy waveforms, such as ultrasound and light energy waveforms. The illustrated neural stimulation includes leadless ECG electrodes <part-num-ref name="illustrated neural stimulation includes leadless ECG electrodes">209</part-num-ref>
|
| 215 |
+
on the housing of the device, which are capable of being used to detect heart rate, for example, to provide feedback for the neural stimulation therapy. At the time of the implantation of the neural stimulator, the test lead cable <part-num-ref name="test lead cable">201</part-num-ref>
|
| 216 |
+
is temporarily connected to the implanted neural stimulation lead to enable the analyzer to determine an appropriate placement of the lead, and verify the integrity of the stimulation path within the lead. The ECG electrodes, for example, are connected to the analyzer and are also temporarily placed on the patient, enabling the analyzer to verify the capture of the neural target. </p>
|
| 217 |
+
<p id="p-40" num="40">[0032] Sensor cable(s) 203 connect the analyzer to electrodes <part-num-ref name="analyzer to electrodes">204.</part-num-ref>
|
| 218 |
+
These electrodes are used by the analyzer to detect electrical activity of the heart in response to a test neural stimulation delivered through the implantable neural stimulation lead through the test lead <part-num-ref name="test lead">201.</part-num-ref>
|
| 219 |
+
For example, the electrodes <part-num-ref name="electrodes">204</part-num-ref>
|
| 220 |
+
can be used to detect heart rate, HRV, and/or HRT. </p>
|
| 221 |
+
<p id="p-41" num="41">[0033<confidence value="5">]</confidence>
|
| 222 |
+
In some embodiments, the implantable neural stimulator is integrated with an implantable cardiac rhythm management device with lead(s) positioned to provide a CRM therapy to a heart. The CRM leads can be used to deliver a cardiac stimulation signal. The CRM leads can be used to pace the heart as part of a bradycardia therapy, an anti-tachycardia or a cardiac resynchronization therapy, for example, to shock the heart as part of an antitachycardia therapy, and to sense cardiac activity. Various embodiments use the CRM lead can also be used to deliver a premature ventricular contraction to perform an <confidence value="5">H</confidence>
|
| 223 |
+
RT analysis. </p>
|
| 224 |
+
<boundary-data type="header">
|
| 225 |
+
<confidence value="88">13</confidence>
|
| 226 |
+
</boundary-data>
|
| 227 |
+
<boundary-data type="header">Attorney Docket No. 279.D48US1</boundary-data>
|
| 228 |
+
<p id="p-42" num="42">
|
| 229 |
+
<page-break num="14"/>
|
| 230 |
+
[0034] Some embodiments of the analyzer are adapted to analyze both a neural stimulation system and a cardiac stimulation system. The testing can be done sequentially, as the cardiac and neural leads are implanted. Various cardiac lead embodiments have both pace and sense capabilities, such that the cardiac lead can be used to determine if the test pacing parameters attain a desired response. According to some device embodiments, the pacing circuit is adapted to deliver a test cardiac stimulation signal, and the test lead cable is adapted to electrically connect the pacing circuit and an implantable cardiac stimulation lead. Physiologic feedback is provided using a sensor adapted to sense a physiologic response to cardiac stimulation. The neural stimulation lead and the cardiac stimulation lead can be integrated into one lead. </p>
|
| 231 |
+
<p id="p-43" num="43">[0035] FIG. 3 illustrates an embodiment of a neural stimulation system analyzer <part-num-ref name="neural stimulation system analyzer">300</part-num-ref>
|
| 232 |
+
with a test lead cable <part-num-ref name="test lead cable">301</part-num-ref>
|
| 233 |
+
connected to a bipolar neural stimulation lead <part-num-ref name="bipolar neural stimulation lead">302</part-num-ref>
|
| 234 |
+
and with a sensor cable <part-num-ref name="sensor cable">303</part-num-ref>
|
| 235 |
+
connected to ECG electrodes <part-num-ref name="connected to ECG electrodes">304</part-num-ref>
|
| 236 |
+
to be placed on a patient's skin. The neural stimulation lead <part-num-ref name="neural stimulation lead">302</part-num-ref>
|
| 237 |
+
has a proximal end <part-num-ref name="proximal end">309</part-num-ref>
|
| 238 |
+
for connection to the pulse generator of the implantable neural stimulator, and a distal end <part-num-ref name="distal end">310.</part-num-ref>
|
| 239 |
+
The illustrated bipolar neural stimulation lead includes an external covering <part-num-ref name="external covering">311</part-num-ref>
|
| 240 |
+
made from an insulator material, a first electrode <part-num-ref name="first electrode">312</part-num-ref>
|
| 241 |
+
illustrated as a tip electrode, and a second electrode <part-num-ref name="second electrode">313</part-num-ref>
|
| 242 |
+
illustrated as a ring electrode. The electrodes are not covered by the insulator material. A first wire <part-num-ref name="first wire">314</part-num-ref>
|
| 243 |
+
extends from the first electrode <part-num-ref name="first electrode">312</part-num-ref>
|
| 244 |
+
to a first terminal <part-num-ref name="first terminal">315</part-num-ref>
|
| 245 |
+
at the proximal end of the lead, and a second wire <part-num-ref name="second wire">316</part-num-ref>
|
| 246 |
+
extends from the second electrode <part-num-ref name="second electrode">313</part-num-ref>
|
| 247 |
+
to a second terminal <part-num-ref name="second terminal">317</part-num-ref>
|
| 248 |
+
at the proximal end of the lead. </p>
|
| 249 |
+
<p id="p-44" num="44">
|
| 250 |
+
<confidence value="5">[</confidence>
|
| 251 |
+
0036] The illustrated test lead cable <part-num-ref name="illustrated test lead cable">301</part-num-ref>
|
| 252 |
+
has two connectors, such as clamps or alligator clips, to connect with the first and second terminals of the neural stimulation lead. The illustrated neural stimulation system analyzer is adapted to generate neural stimulation signals, which are delivered through the test lead cable <part-num-ref name="test lead cable">301</part-num-ref>
|
| 253 |
+
and through the neural stimulation lead to the first and second electrodes. The illustrated neural stimulation system analyzer is also adapted to test the lead impedance of the neural stimulation lead. A sensor cable <part-num-ref name="sensor cable">303</part-num-ref>
|
| 254 |
+
includes a sensor for use in detecting a <boundary-data type="header">
|
| 255 |
+
<confidence value="88">14</confidence>
|
| 256 |
+
</boundary-data>
|
| 257 |
+
<page-break num="15"/>
|
| 258 |
+
<boundary-data type="header">Attorney Docket No. 279.D48US <confidence value="8">1</confidence>
|
| 259 |
+
</boundary-data>
|
| 260 |
+
physiologic response to the neural stimulation test to verify capture of the target nerve. </p>
|
| 261 |
+
<p id="p-45" num="45">The illustrated sensor cable 303 is connected to ECG electrodes <part-num-ref name="is connected to ECG electrodes">304.</part-num-ref>
|
| 262 |
+
</p>
|
| 263 |
+
<p id="p-46" num="46">
|
| 264 |
+
<confidence value="5">[</confidence>
|
| 265 |
+
0037<confidence value="4">]</confidence>
|
| 266 |
+
FIG. 4 illustrates a block diagram for an embodiment of a neural stimulation system analyzer <part-num-ref name="neural stimulation system analyzer">400.</part-num-ref>
|
| 267 |
+
The analyzer <part-num-ref name="analyzer">400</part-num-ref>
|
| 268 |
+
has an external housing that contains electronic circuitry including sensing and pacing channel(s) <part-num-ref name="external housing that contains electronic circuitry including sensing and pacing channel(s)">421</part-num-ref>
|
| 269 |
+
and a pacing control circuit <part-num-ref name="pacing control circuit">422.</part-num-ref>
|
| 270 |
+
The sensing and pacing channel <part-num-ref name="sensing and pacing channel">421</part-num-ref>
|
| 271 |
+
is adapted to generate a neural stimulation burst, and sense a physical parameter responsive to the neural stimulation. The pacing control circuit <part-num-ref name="pacing control circuit">422</part-num-ref>
|
| 272 |
+
controls the overall operation of the analyzer <part-num-ref name="analyzer">400,</part-num-ref>
|
| 273 |
+
including the delivery of the pacing pulses in each sensing and pacing channel. The analyzer <part-num-ref name="analyzer">400</part-num-ref>
|
| 274 |
+
also includes a user interface <part-num-ref name="user interface">423,</part-num-ref>
|
| 275 |
+
which is electrically connected to the control circuit <part-num-ref name="control circuit">422.</part-num-ref>
|
| 276 |
+
The user interface <part-num-ref name="user interface">423</part-num-ref>
|
| 277 |
+
allows a user such as a physician or other caregiver to operate the analyzer and observe information acquired by the analyzer. In some embodiments, the user interface is mounted on a housing of the analyzer. An embodiment uses a display screen as a user interface. Other ways to provide feedback to the physician can be used, in addition to or in place of the display screen, such as an audio signal or light. According to some embodiments, the user interface is electrically connected to the electronic circuitry using wires or a cable. </p>
|
| 278 |
+
<p id="p-47" num="47">The user interface of a computer or a computer-based medical device programmer can be used as user interface. The analyzer can be incorporated into the computer or computer-based medical device programmer. Some analyzer embodiments are configured for detachable attachment to the computer or computer-based medical device programmer.</p>
|
| 279 |
+
<p id="p-48" num="48">
|
| 280 |
+
<confidence value="5">[</confidence>
|
| 281 |
+
0038<confidence value="5">]</confidence>
|
| 282 |
+
FIG. 5 illustrates a more detailed block diagram for the neural stimulation system analyzer embodiment illustrated in FIG. 4. The analyzer <part-num-ref name="analyzer">500</part-num-ref>
|
| 283 |
+
includes a sensing and pacing channel 521A, pacing control circuit <part-num-ref name="sensing and pacing channel 521A, pacing control circuit">522,</part-num-ref>
|
| 284 |
+
and a user interface <part-num-ref name="user interface">523.</part-num-ref>
|
| 285 |
+
</p>
|
| 286 |
+
<p id="p-49" num="49">The sensing and pacing channel includes a sensing circuit <part-num-ref name="sensing circuit">524</part-num-ref>
|
| 287 |
+
to sense a physiologic response (e.g. heart rate, HRV, or HRT) and a pacing circuit <part-num-ref name="pacing circuit">525</part-num-ref>
|
| 288 |
+
to deliver neural stimulation. The sensing and pacing channel can include multiple channels (e.g. 521<confidence value="8">B</confidence>
|
| 289 |
+
and 521C) to accommodate additional neural stimulation leads or to accommodate more complex electrical arrangements capable of providing various stimulation <boundary-data type="header">
|
| 290 |
+
<confidence value="88">15</confidence>
|
| 291 |
+
</boundary-data>
|
| 292 |
+
<page-break num="16"/>
|
| 293 |
+
<boundary-data type="header">Attorney Docket No. 279.D4<confidence value="5885">8US1</confidence>
|
| 294 |
+
</boundary-data>
|
| 295 |
+
vectors among the electrodes. The pacing control circuit <part-num-ref name="pacing control circuit">522</part-num-ref>
|
| 296 |
+
controls the delivery of pacing pulses to the neural target using a plurality of pacing parameters including user-programmable pacing parameters. These programmable pacing parameters can be evaluated using the analyzer. </p>
|
| 297 |
+
<p id="p-50" num="50">[0039] The illustrated user interface <part-num-ref name="illustrated user interface">523</part-num-ref>
|
| 298 |
+
includes a pacing parameter input <part-num-ref name="pacing parameter input">526</part-num-ref>
|
| 299 |
+
and a presentation device <part-num-ref name="presentation device">527.</part-num-ref>
|
| 300 |
+
The parameter input allows the user to enter and/or adjust the user-programmable pacing parameters. The presentation device includes a display screen <part-num-ref name="display screen">528</part-num-ref>
|
| 301 |
+
for displaying neural stimulation signal and/or physiological sensing signals in real time. Other outputs, such as an audio signal, can be used in addition to or in place of the presentation device to provide an indication of whether the test neural stimulation successfully stimulated a target nerve. </p>
|
| 302 |
+
<p id="p-51" num="51">[0040] According to various embodiments, the device, as illustrated and described above, is adapted to deliver neural stimulation as electrical stimulation to desired neural targets, such as through one or more stimulation electrodes positioned at predetermined location(s). Other elements for delivering neural stimulation can be used. For example, some embodiments use transducers to deliver neural stimulation using other types of energy, such as ultrasound, light, magnetic or thermal energy.</p>
|
| 303 |
+
<p id="p-52" num="52">[0041] One of ordinary skill in the art will understand that, the modules and other circuitry shown and described herein can be implemented using software, hardware, and combinations of software and hardware. As such, the terms module and circuitry, for example, are intended to encompass software implementations, hardware implementations, and software and hardware implementations.</p>
|
| 304 |
+
<p id="p-53" num="53">[0042] The methods illustrated in this disclosure are not intended to be exclusive of other methods within the scope of the present subject matter. Those of ordinary skill in the art will understand, upon reading and comprehending this disclosure, other methods within the scope of the present subject matter. The above-identified embodiments, and portions of the illustrated embodiments, are not necessarily mutually exclusive. These embodiments, or portions thereof, can be combined. In various embodiments, the methods are implemented using a computer data signal embodied in a carrier wave or propagated signal, that represents a sequence of <boundary-data type="header">
|
| 305 |
+
<confidence value="88">16</confidence>
|
| 306 |
+
</boundary-data>
|
| 307 |
+
<page-break num="17"/>
|
| 308 |
+
<boundary-data type="header">Attorney Docket No. 279.D4<confidence value="588">8US</confidence>
|
| 309 |
+
<confidence value="8">1</confidence>
|
| 310 |
+
</boundary-data>
|
| 311 |
+
instructions which, when executed by a processor cause the processor to perform the respective method. In various embodiments, the methods are implemented as a set of instructions contained on a computer-accessible medium capable of directing a processor to perform the respective method. In various embodiments, the medium is a magnetic medium, an electronic medium, or an optical medium. </p>
|
| 312 |
+
<p id="p-54" num="54">[0043] The above detailed description is intended to be illustrative, and not restrictive. Other embodiments will be apparent to those of skill in the art upon reading and understanding the above description. The scope of the invention should, therefore, be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.</p>
|
| 313 |
+
<boundary-data type="header">
|
| 314 |
+
<confidence value="88">17</confidence>
|
| 315 |
+
</boundary-data>
|
| 316 |
+
</description>
|
| 317 |
+
</us-patent-application>
|
| 318 |
+
|
applicant/11761332.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
applicant/11762155.xml
ADDED
|
@@ -0,0 +1,142 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11762155</doc-number>
|
| 8 |
+
<date>2010-09-30</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">Application No. 11/762,155 2</boundary-data>
|
| 14 |
+
<boundary-data type="header">Docket No. 20061606-US-CIP</boundary-data>
|
| 15 |
+
<heading id="h-1">AMENDMENTS TO THE SPECIFICATION</heading>
|
| 16 |
+
<p id="p-1" num="1">Please amend the Specification by replacin<confidence value="8">g</confidence>
|
| 17 |
+
the followin<confidence value="8">g</confidence>
|
| 18 |
+
para<confidence value="8">g</confidence>
|
| 19 |
+
raph numbers. </p>
|
| 20 |
+
<p id="p-2" num="2">[0007] Thus, one method embodiment herein starts by receiving initial user input. This initial user input can comprise initial natural language commands that identify an initial color selection.</p>
|
| 21 |
+
<p id="p-3" num="3">The method displays a plurality of initial color samples or patches that correspond to the initial color selection in a two- or three-dimensional grid (e.g., using a pseudo 3D plot - using perspective to give the illusion of 3D) on a graphic user interface, such as a computer monitor.</p>
|
| 22 |
+
<p id="p-4" num="4">The axes of the two-dimensional grid can correspond to a predetermined standard axis system.</p>
|
| 23 |
+
<p id="p-5" num="5">Also, simultaneously displayed on the graphic user interface are assigned names of the initial color regions, and these names are positioned adjacent (above, below, beside, in, on, etc.) the initial color regions. This displays the names of the colors as they are defined in the collection being searched. If it is a <confidence value="2222222">pantene</confidence>
|
| 24 |
+
Pantone collection then Pantone's names are displayed. If it was a collection of e<confidence value="228666">r-ayen</confidence>
|
| 25 |
+
Cra<confidence value="666">yon</confidence>
|
| 26 |
+
colors then it would be e<confidence value="2266821">r-ayene</confidence>
|
| 27 |
+
Cra<confidence value="66666">yon's</confidence>
|
| 28 |
+
names that are displayed. However, many times the initial natural language commands are different than assigned names (e.g., Pantone names) of the initial color regions because color names assignments are often made based on criteria that are fundamentally different than names commonly given by casual users e.g. for marketing purposes. </p>
|
| 29 |
+
<p id="p-6" num="6">[0008] After displaying the initial color regions, the method may (or may not) receive at least one additional user input. Such additional user inputs can comprise additional natural language commands and/or a <confidence value="8">r</confidence>
|
| 30 |
+
efi<confidence value="8">n</confidence>
|
| 31 |
+
ed revised axis selection. These additional natural language commands can comprise a color change magnitude, a color change direction, and a color change property. </p>
|
| 32 |
+
<boundary-data type="header">Application No. 11/762,155 3</boundary-data>
|
| 33 |
+
<boundary-data type="header">Docket No. 20061606-US-CIP</boundary-data>
|
| 34 |
+
<p id="p-7" num="7">
|
| 35 |
+
<page-break num="2"/>
|
| 36 |
+
For example, a natural language command of "slightly more blue" spoken or typed into a graphic user interface provides the color change magnitude ("slightly"), color change direction ("more"), and color change property ("blue") used by embodiments herein to revise the colors displayed to the user. </p>
|
| 37 |
+
<p id="p-8" num="8">[0009] Thus, the method revises the initial color selection to a revised color selection based on the color change magnitude, the color change direction, and the color change property provided in natural language format by the user. Then, the method can display <confidence value="8">r</confidence>
|
| 38 |
+
e<confidence value="8">f</confidence>
|
| 39 |
+
i<confidence value="8">n</confidence>
|
| 40 |
+
ed revised color regions (patches) that correspond to the <confidence value="8">r</confidence>
|
| 41 |
+
e<confidence value="8">f</confidence>
|
| 42 |
+
i<confidence value="8">n</confidence>
|
| 43 |
+
ed revised color selection in the two- or three dimensional grid of the display. However, the axes of the two-or three dimensional grids can also be modified to correspond to the <confidence value="8">r</confidence>
|
| 44 |
+
e<confidence value="8">f</confidence>
|
| 45 |
+
i<confidence value="8">n</confidence>
|
| 46 |
+
ed revised axis selection provided by the user in the additional input. The selection of the axes will affect the spatial relationships of the colors to each other as they are displayed on the user interface. For example, if the axes are chosen to be lightness on the vertical axis and hue on the horizontal axis then color samples or patches will be arranged vertically in order of their lightness and horizontally in order of their hue. </p>
|
| 47 |
+
<p id="p-9" num="9">[0010] In a similar manner to the display of the initial color regions, the display can also simultaneously display the assigned names of the <confidence value="88">re</confidence>
|
| 48 |
+
fi<confidence value="8">n</confidence>
|
| 49 |
+
e<confidence value="8">d</confidence>
|
| 50 |
+
revised color samples adjacent (above, below, beside, in, on, etc.) the <confidence value="88">re</confidence>
|
| 51 |
+
fi<confidence value="8">n</confidence>
|
| 52 |
+
e<confidence value="8">d</confidence>
|
| 53 |
+
revised color samples. The system may be configured such that the names are not displayed unless a pointing device is placed over the color or clicked on the color in order to avoid the display becoming too cluttered. Again, the additional natural language commands may be different than assigned names of the refined revised color samples. </p>
|
| 54 |
+
<p id="p-10" num="10">Indeed, the additional language commands comprise color change magnitudes, color change <page-break num="3"/>
|
| 55 |
+
<boundary-data type="header">Application No. 11/762,155 4</boundary-data>
|
| 56 |
+
<boundary-data type="header">Docket No. 20061606-US-CIP</boundary-data>
|
| 57 |
+
directions, and color change properties and do not necessarily correspond to the names a specific computer program may assign to colors. </p>
|
| 58 |
+
<p id="p-11" num="11">[0013] When displaying the initial color samples and the <confidence value="888">ref</confidence>
|
| 59 |
+
i<confidence value="8">n</confidence>
|
| 60 |
+
e<confidence value="8">d</confidence>
|
| 61 |
+
revised color samples, the method displays a principal color patch (corresponding respectively to the best matching sample to either the initial color selection or the <confidence value="888">ref</confidence>
|
| 62 |
+
i<confidence value="8">n</confidence>
|
| 63 |
+
ed revised color selection) and displays secondary color samples having similarities to the principal color patch. Ones of the secondary color samples that are more similar to the principal color patch are positioned closer to the principal color patch, and ones of the secondary color samples that are less similar to the principal color patch are positioned further from the principal color patch. The concept of similarity depends on the axes and measurement system you are using. In Figure one, the invention has defined axes to be lightness and colorfulness. Thus, similarity is measured in these terms. If one changed the axes properties to be, say, hue and saturation, then the similarity relationships might well change. </p>
|
| 64 |
+
<p id="p-12" num="12">[0015] This method similarly displays the initial color regions corresponding to the initial color selection in a two-dimensional grid and receives additional user input comprising additional natural language commands and a <confidence value="888">ref</confidence>
|
| 65 |
+
i<confidence value="8">n</confidence>
|
| 66 |
+
ed revised axis selection. This embodiment also revises the initial color selection to a revised color selection based on the color change magnitude, the color change direction, and the color change property. Then this method matches the revised color selection to the computer program colors to produce <confidence value="8">r</confidence>
|
| 67 |
+
efi<confidence value="8">n</confidence>
|
| 68 |
+
ed revised matching colors. These <confidence value="8">r</confidence>
|
| 69 |
+
efi<confidence value="8">n</confidence>
|
| 70 |
+
ed revised matching colors are displayed as <confidence value="8">r</confidence>
|
| 71 |
+
efi<confidence value="8">n</confidence>
|
| 72 |
+
e<confidence value="8">d</confidence>
|
| 73 |
+
revised color regions in the two- dimensional grid. Again, the axes of the two-dimensional grid can correspond to the <confidence value="88">re</confidence>
|
| 74 |
+
fi<confidence value="8">n</confidence>
|
| 75 |
+
e<confidence value="8">d</confidence>
|
| 76 |
+
revised axis selection and the assigned names can also be displayed on the graphic user interface. </p>
|
| 77 |
+
<boundary-data type="header">Application No. 11/762,155 5</boundary-data>
|
| 78 |
+
<boundary-data type="header">Docket No. 20061606-US-CIP</boundary-data>
|
| 79 |
+
<p id="p-13" num="13">
|
| 80 |
+
<page-break num="4"/>
|
| 81 |
+
Further, this embodiment can receive a selection of one or more of the <confidence value="155224">lef-ie</confidence>
|
| 82 |
+
revised color samples as one or more selected colors from the user. The selected color(s) are then provided to the associated computer program. </p>
|
| 83 |
+
<p id="p-14" num="14">[0032] Thus, the embodiments herein address the problem of finding colors based on their color appearance by allowing users to provide a natural language (verbal or typed) description of the color. Colors matching the verbal description are returned in a form that allows the user to either select the color the user wants, <confidence value="15524">ief-e</confidence>
|
| 84 |
+
revise the selection further with a new verbal selection, or shift the characteristics of the selection by issuing natural language color change commands such as <confidence value="5">'</confidence>
|
| 85 |
+
slightly lighter<confidence value="58">',</confidence>
|
| 86 |
+
<confidence value="5">'</confidence>
|
| 87 |
+
more colorful<confidence value="5">'</confidence>
|
| 88 |
+
etc. </p>
|
| 89 |
+
<p id="p-15" num="15">[0046] After displaying the initial color regions, the method can receive at least one additional user input in item <part-num-ref name="method can receive at least one additional user input in item">206.</part-num-ref>
|
| 90 |
+
Such additional user inputs <part-num-ref name="method can receive at least one additional user input in item 206. Such additional user inputs">206</part-num-ref>
|
| 91 |
+
can comprise additional natural language commands and/or a <confidence value="155224">lef-ie</confidence>
|
| 92 |
+
revised axis selection. These additional natural language commands may comprise a color change magnitude, a color change direction, and a color change property. </p>
|
| 93 |
+
<p id="p-16" num="16">In some cases the command may contain implicit information. e.g., the command <confidence value="5">'</confidence>
|
| 94 |
+
darker<confidence value="5">'</confidence>
|
| 95 |
+
may <confidence value="88">be</confidence>
|
| 96 |
+
parsed to mean <confidence value="5">'</confidence>
|
| 97 |
+
moderately more dark<confidence value="5">'</confidence>
|
| 98 |
+
. For example, a natural language command of "slightly more blue" spoken or typed into a graphic user interface <part-num-ref name="graphic user interface">302</part-num-ref>
|
| 99 |
+
provides the color change magnitude ("slightly"), color change direction ("more"), and color change property ("blue") used by embodiments herein to revise the colors displayed to the user. </p>
|
| 100 |
+
<p id="p-17" num="17">[0047] Thus, the method revises the initial color selection to a revised color selection based on the color change magnitude, the color change direction, and the color change property provided <page-break num="5"/>
|
| 101 |
+
<boundary-data type="header">Application No. 11/762,155 6</boundary-data>
|
| 102 |
+
<boundary-data type="header">Docket No. 20061606-US-CIP</boundary-data>
|
| 103 |
+
in natural language format by the user in item <part-num-ref name="user in item">208.</part-num-ref>
|
| 104 |
+
Then, the method can display <confidence value="155265">lef-ed</confidence>
|
| 105 |
+
revised color samples (patches) that correspond to the <confidence value="155255">ief-ed</confidence>
|
| 106 |
+
revised color selection in the two- dimensional grid of the display in item <part-num-ref name="display in item">212.</part-num-ref>
|
| 107 |
+
However, the axes of the two-dimensional grid can also be modified to correspond to the <confidence value="155255">lef-ed</confidence>
|
| 108 |
+
revised axis selection provided by the user in the additional input. The process loops back to obtain additional user inputs in item <part-num-ref name="process loops back to obtain additional user inputs in item">206</part-num-ref>
|
| 109 |
+
in an iterative, repeating process that continues until the user finds the color that they were seeking. </p>
|
| 110 |
+
<p id="p-18" num="18">[0048] In a similar manner to the display of the initial color regions, the display can also simultaneously display the assigned names of the <confidence value="1562242">ief-ied</confidence>
|
| 111 |
+
revised color samples or patches adjacent (above, below, beside, in, on, etc.) the <confidence value="1552265">ief-ied</confidence>
|
| 112 |
+
revised color regions. The system may <confidence value="88">be</confidence>
|
| 113 |
+
configured such that the names are not displayed unless a pointing device is placed over the color or clicked on the color in order to avoid the display becoming too cluttered. Again, the additional natural language commands may be different than assigned names of the <confidence value="1562255">lef-ied</confidence>
|
| 114 |
+
revised color samples or patches. Indeed, the additional language commands comprise color change magnitudes, color change directions, and color change properties that do not necessarily correspond to the names a specific computer program <part-num-ref name="specific computer program">312</part-num-ref>
|
| 115 |
+
may assign to colors. </p>
|
| 116 |
+
<p id="p-19" num="19">[0051] As shown in Figure 1, when displaying the initial color samples or patches and the <confidence value="6615242">efi-ned</confidence>
|
| 117 |
+
revised color samples or patches, the method displays a principal color patch (corresponding respectively to either the initial color selection or the <confidence value="1562242">lef-ied</confidence>
|
| 118 |
+
revised color selection) and displays secondary color samples or patches having similarities to the principal color patch. Ones of the secondary color samples or patches that are more similar to the principal color patch are positioned closer to the principal color patch and ones of the secondary color <page-break num="6"/>
|
| 119 |
+
<boundary-data type="header">Application No. 11/762,155 7</boundary-data>
|
| 120 |
+
<boundary-data type="header">Docket No. 20061606-US-CIP</boundary-data>
|
| 121 |
+
samples or patches that are less similar to the principal color patch are positioned further from the principal color patch. The concept of similarity depends on the measurement system you are using. In Figure one, the invention has defined axes to be lightness and colorfulness. Thus, similarity is measured in these terms. If one changed the axes properties to be, say, hue and saturation then the similarity relationships might well change. </p>
|
| 122 |
+
<p id="p-20" num="20">[0053] This method similarly displays the initial color regions corresponding to the initial color selection in a two-dimensional grid <part-num-ref name="two-dimensional grid">204</part-num-ref>
|
| 123 |
+
and receives additional user input comprising additional natural language commands and a <confidence value="155265">lef-ed</confidence>
|
| 124 |
+
revised axis selection in item <part-num-ref name="lef-ed revised axis selection in item">206.</part-num-ref>
|
| 125 |
+
This embodiment also revises the initial color selection to a revised color selection based on the color change magnitude, the color change direction, and the color change property in item <part-num-ref name="color change property in item">208.</part-num-ref>
|
| 126 |
+
Then this method matches the revised color selection to the computer program colors to produce <confidence value="1552242">ief-ied</confidence>
|
| 127 |
+
revised matching colors in item <part-num-ref name="computer program colors to produce ief-ied revised matching colors in item">209.</part-num-ref>
|
| 128 |
+
These <confidence value="255224">ref-ie</confidence>
|
| 129 |
+
revised matching colors are displayed as <confidence value="5622255">ef-ined</confidence>
|
| 130 |
+
revised color samples or patches in the two-dimensional grid in item <part-num-ref name="two-dimensional grid in item">212.</part-num-ref>
|
| 131 |
+
Again, the axes of the two-dimensional grid can correspond to the <confidence value="155255">lef-ed</confidence>
|
| 132 |
+
revised axis selection and the assigned names can also be displayed on the graphic user interface <part-num-ref name="graphic user interface">302.</part-num-ref>
|
| 133 |
+
</p>
|
| 134 |
+
<p id="p-21" num="21">[0054] Further, this embodiment can receive a selection of one or more of the <confidence value="2562525">ref-ine</confidence>
|
| 135 |
+
revised color samples or patches as one or more selected colors from the user through the graphic user interface <part-num-ref name="graphic user interface">302</part-num-ref>
|
| 136 |
+
in item <part-num-ref name="in item">214.</part-num-ref>
|
| 137 |
+
The selected color(s) are then provided to the associated computer program <part-num-ref name="associated computer program">312</part-num-ref>
|
| 138 |
+
in item <part-num-ref name="in item">216.</part-num-ref>
|
| 139 |
+
</p>
|
| 140 |
+
</description>
|
| 141 |
+
</us-patent-application>
|
| 142 |
+
|
applicant/11822548.xml
ADDED
|
@@ -0,0 +1,877 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11822548</doc-number>
|
| 8 |
+
<date>2007-07-06</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">Atty. Dkt. No.: 9862-000234/U<confidence value="5">S</confidence>
|
| 14 |
+
</boundary-data>
|
| 15 |
+
<heading id="h-1">A SEMICONDUCTOR MEMORY DEVICE, METHOD OF FABRICATING</heading>
|
| 16 |
+
<heading id="h-2">THE SAME, AND DEVICES EMPLOYING THE SEMICONDUCTOR</heading>
|
| 17 |
+
<heading id="h-3">MEMORY DEVICE</heading>
|
| 18 |
+
<heading id="h-4">FOREIGN PRIORITY INFORMATION</heading>
|
| 19 |
+
<p id="p-1" num="1">
|
| 20 |
+
<confidence value="5">[</confidence>
|
| 21 |
+
0001] A claim of priority under <part-num-ref name="claim of priority under">35</part-num-ref>
|
| 22 |
+
U.S.C. <part-num-ref name="U.S.C.">119</part-num-ref>
|
| 23 |
+
is made to Korean Application No. 10-2007-29185, f<confidence value="88">il</confidence>
|
| 24 |
+
ed March <part-num-ref name="is made to Korean Application No. 10-2007-29185, filed March">26,</part-num-ref>
|
| 25 |
+
<part-num-ref name="is made to Korean Application No. 10-2007-29185, filed March 26,">2007,</part-num-ref>
|
| 26 |
+
the entire contents of which are hereby incorporated by reference. </p>
|
| 27 |
+
<heading id="h-5">BACKGROUND OF THE INVENTION</heading>
|
| 28 |
+
<p id="p-2" num="2">
|
| 29 |
+
<confidence value="5">[</confidence>
|
| 30 |
+
0002<confidence value="4">]</confidence>
|
| 31 |
+
The present invention relates to a semiconductor memory device, a method of fabricating<confidence value="5">.</confidence>
|
| 32 |
+
the same, and devices employing the semiconductor memory device. </p>
|
| 33 |
+
<p id="p-3" num="3">
|
| 34 |
+
<confidence value="5">[</confidence>
|
| 35 |
+
0003] Non-volatile memory devices retain stored information even when not powered. One example of a non-volatile memory device is a flash memory. Many non-volatile memories have a memory cell array structure where the memory cells are floating gate transistors. Generally, these memory cells include a floating gate disposed between a semiconductor substrate and a control gate. A tunnel insulation layer often separates the floating gate from the semiconductor substrate. A drain and source are generally disposed on either side of the floating gate <boundary-data type="header">
|
| 36 |
+
<confidence value="6">1</confidence>
|
| 37 |
+
</boundary-data>
|
| 38 |
+
<page-break num="2"/>
|
| 39 |
+
<boundary-data type="header">Atty. Dkt. No.: 9862-000234/U<confidence value="5">S</confidence>
|
| 40 |
+
</boundary-data>
|
| 41 |
+
in the semiconductor substrate. During operation, charges are injected into or pulled from the floating gate by application of voltages to the control gate, drain and/or source. </p>
|
| 42 |
+
<p id="p-4" num="4">
|
| 43 |
+
<confidence value="5">[</confidence>
|
| 44 |
+
0004<confidence value="5">]</confidence>
|
| 45 |
+
A potential Vfg of the floating gate when a write potential V<confidence value="5">c</confidence>
|
| 46 |
+
g is applied to the control gate is determined by capacitive coupling as represented by equations <part-num-ref name="control gate is determined by capacitive coupling as represented by equations">1</part-num-ref>
|
| 47 |
+
and <part-num-ref name="and">2</part-num-ref>
|
| 48 |
+
below: </p>
|
| 49 |
+
<p id="p-5" num="5">Vfg = Cr(V<confidence value="5">c</confidence>
|
| 50 |
+
g-Vt-Vt<confidence value="4">0</confidence>
|
| 51 |
+
) (1) Cr = Cip/(Cip +Ctun) <part-num-ref name="Cr = Cip/(Cip +Ctun)">(2)</part-num-ref>
|
| 52 |
+
where Vt is the present cell transistor threshold value, Vt<confidence value="4">O</confidence>
|
| 53 |
+
is the threshold value (neutral threshold value) when no electric charge is stored in the floating gate, and Cr is the capacitive coupling ratio of the memory cell. As shown by equation <part-num-ref name="memory cell. As shown by equation">2,</part-num-ref>
|
| 54 |
+
the capacitive coupling ratio Cr depends on i) the capacitance Cip between the control gate and the floating gate and ii) the capacitance Ctun between the floating gate and the semiconductor substrate. </p>
|
| 55 |
+
<p id="p-6" num="6">[0005<confidence value="4">]</confidence>
|
| 56 |
+
As Vfg rises, an electric field acting on the tunnel insulation layer increases, and this facilitates injection of electric charge into the floating gate. In addition, according to the above equations, when Vcg is constant, Vfg increases in proportion to a capacitance ratio Cr. That is, <boundary-data type="header">
|
| 57 |
+
<confidence value="8">2</confidence>
|
| 58 |
+
</boundary-data>
|
| 59 |
+
<page-break num="3"/>
|
| 60 |
+
<boundary-data type="header">Atty. Dkt. No.: 9862-000234/US</boundary-data>
|
| 61 |
+
when this capacitance ratio Cr is large, a Vfg large enough to move electric charge can be obtained even if the write potential V<confidence value="5">c</confidence>
|
| 62 |
+
g is decreased. As a consequence, the write potential can be reduced. </p>
|
| 63 |
+
<heading id="h-6">SUMMARY OF THE INVENTION</heading>
|
| 64 |
+
<p id="p-7" num="7">
|
| 65 |
+
<confidence value="5">[</confidence>
|
| 66 |
+
0006<confidence value="4">]</confidence>
|
| 67 |
+
The present invention relates to a semiconductor memory device. </p>
|
| 68 |
+
<p id="p-8" num="8">[0007] In one embodiment, the semiconductor memory device includes a semiconductor substrate having projecting portions, a tunnel insulation layer formed over at least one of the projecting semiconductor substrate portions, and a floating gate structure disposed over the tunnel insulation layer. An upper portion of the floating gate structure is wider than a lower portion of the floating gate structure, and the lower portion of the floating gate structure has a width less than a width of the tunnel insulating layer. First insulation layer portions are formed in the semiconductor substrate and project from the semiconductor substrate such that the floating gate structure is disposed between the projecting first insulation layer portions. A dielectric layer is formed over the first insulation layer portions and the floating gate structure, and a control gate is formed over the dielectric layer.</p>
|
| 69 |
+
<boundary-data type="header">
|
| 70 |
+
<confidence value="8">3</confidence>
|
| 71 |
+
</boundary-data>
|
| 72 |
+
<boundary-data type="header">Atty. Dkt. No.: 9862-000234/US</boundary-data>
|
| 73 |
+
<p id="p-9" num="9">
|
| 74 |
+
<page-break num="4"/>
|
| 75 |
+
[0008<confidence value="4">]</confidence>
|
| 76 |
+
Another embodiment of the semiconductor memory device includes a semiconductor substrate, and a floating gate structure disposed over the substrate. An upper portion of the floating gate structure is wider than a lower portion of the floating gate structure. </p>
|
| 77 |
+
<p id="p-10" num="10">First insulation layer portions are formed in the semiconductor substrate and project from the semiconductor substrate such that the floating gate structure is disposed between the projecting f<confidence value="8">i</confidence>
|
| 78 |
+
rst insulation layer portions, and an upper surface of the floating gate structure is below an upper surface of the projecting first insulation layer portions. A dielectric layer is formed over the first insulation layer portions and the floating gate structure. A control gate is formed over the dielectric layer. </p>
|
| 79 |
+
<p id="p-11" num="11">[0009] A further embodiment of the semiconductor memory device includes a semiconductor substrate, and a floating gate structure disposed over the substrate. An upper portion of the floating gate structure is wider than a lower portion of the floating gate structure.</p>
|
| 80 |
+
<p id="p-12" num="12">First insulation layer portions are formed in the semiconductor substrate and project from the semiconductor substrate such that the floating gate is disposed between the projecting first insulation layer portions. The projecting first insulation layer portions define a recess exposing an upper portion of the floating gate structure. A dielectric layer is formed over the first insulation layer portions and the floating gate structure <boundary-data type="header">
|
| 81 |
+
<confidence value="8">4</confidence>
|
| 82 |
+
</boundary-data>
|
| 83 |
+
<page-break num="5"/>
|
| 84 |
+
<boundary-data type="header">
|
| 85 |
+
<confidence value="2">,</confidence>
|
| 86 |
+
Atty. Dkt. No.: 9862-000234/US </boundary-data>
|
| 87 |
+
such that the dielectric layer is formed in at least a portion of the recess. </p>
|
| 88 |
+
<p id="p-13" num="13">A control gate is formed over the dielectric layer.</p>
|
| 89 |
+
<p id="p-14" num="14">
|
| 90 |
+
<confidence value="5">[</confidence>
|
| 91 |
+
0010<confidence value="5">]</confidence>
|
| 92 |
+
The present invention also relates to a method of forming a semiconductor memory device. </p>
|
| 93 |
+
<p id="p-15" num="15">[0011<confidence value="5">]</confidence>
|
| 94 |
+
In one embodiment, the method includes forming a floating gate structure on a semiconductor substrate using a mask pattern, and etching a lower portion of the floating gate structure such that the lower portion of the floating gate structure is less wide than an upper portion of the floating gate structure. In this embodiment, the method further includes forming a first insulation layer over the semiconductor substrate, etching the f<confidence value="8">i</confidence>
|
| 95 |
+
rst insulation layer to expose the mask pattern, etching the mask pattern to create a recess defined by the first insulation layer that exposes the floating gate structure, forming a dielectric layer over the first insulation layer such that the dielectric layer is formed in at least a portion of the recess, and forming a control gate over the dielectric layer. </p>
|
| 96 |
+
<p id="p-16" num="16">
|
| 97 |
+
<confidence value="5">[</confidence>
|
| 98 |
+
0012<confidence value="5">]</confidence>
|
| 99 |
+
In another embodiment, the method includes forming a first floating gate over a semiconductor substrate using a mask pattern, forming a first insulation layer over the semiconductor substrate, etching the first insulation layer to expose the mask pattern, etching the mask <boundary-data type="header">
|
| 100 |
+
<confidence value="8">5</confidence>
|
| 101 |
+
</boundary-data>
|
| 102 |
+
<page-break num="6"/>
|
| 103 |
+
<boundary-data type="header">Atty. Dkt. No.: 9862-000234/U<confidence value="5">S</confidence>
|
| 104 |
+
</boundary-data>
|
| 105 |
+
pattern to create a first recess defined by the f<confidence value="8">i</confidence>
|
| 106 |
+
rst insulation layer that exposes the first floating gate, and forming a second floating gate layer over the semiconductor substrate such that the second floating gate layer fills at least a portion of the f<confidence value="8">i</confidence>
|
| 107 |
+
rst recess. In this embodiment, the method further includes etching the second floating gate layer to form a second floating gate such that a second recess is defined by the first insulation layer that exposes the second floating gate. A dielectric layer is formed over the f<confidence value="8">i</confidence>
|
| 108 |
+
rst insulation layer such that the dielectric layer is formed in at least a portion of the second recess, and a control gate is formed over the dielectric layer. </p>
|
| 109 |
+
<p id="p-17" num="17">[0013] The present invention still further relates to a memory device that includes a memory array having an array of memory cells, and each memory cell is conf<confidence value="8">i</confidence>
|
| 110 |
+
gured according to one of the above described embodiments. Control circuitry is configured to read data from and write data to the memory array. </p>
|
| 111 |
+
<p id="p-18" num="18">[0014] The present invention also relates to a memory system including a memory device and a memory controller. The memory controller is conf<confidence value="8">i</confidence>
|
| 112 |
+
gured to control the memory device. </p>
|
| 113 |
+
<p id="p-19" num="19">[0015<confidence value="4">]</confidence>
|
| 114 |
+
The memory device includes an array of memory cells, and each memory cell is configured according to one of the above described embodiments. </p>
|
| 115 |
+
<boundary-data type="header">
|
| 116 |
+
<confidence value="8">6</confidence>
|
| 117 |
+
</boundary-data>
|
| 118 |
+
<boundary-data type="header">Atty<confidence value="5">,</confidence>
|
| 119 |
+
Dkt. No.: 9862-<confidence value="666">000</confidence>
|
| 120 |
+
234/US </boundary-data>
|
| 121 |
+
<p id="p-20" num="20">
|
| 122 |
+
<page-break num="7"/>
|
| 123 |
+
The present invention further relates to a processing system. </p>
|
| 124 |
+
<p id="p-21" num="21">[0016<confidence value="4">)</confidence>
|
| 125 |
+
In one embodiment, the processing system includes a central processing unit and a memory device operatively connected to the central processing system. The memory device includes a memory array having an array of memory cells, and each memory cell is configured according to one of the above described embodiments. </p>
|
| 126 |
+
<boundary-data type="header">
|
| 127 |
+
<confidence value="8">7</confidence>
|
| 128 |
+
</boundary-data>
|
| 129 |
+
<boundary-data type="header">Atty. Dkt. No.: 9862-000234/US</boundary-data>
|
| 130 |
+
<heading id="h-7">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 131 |
+
<p id="p-22" num="22">
|
| 132 |
+
<page-break num="8"/>
|
| 133 |
+
<confidence value="5">[</confidence>
|
| 134 |
+
0017<confidence value="5">]</confidence>
|
| 135 |
+
The present invention will become more fully understood from the detailed description given herein below and the accompanying drawings which are given by way of illustration only, wherein like reference numerals designate corresponding parts in the various drawings, and wherein: </p>
|
| 136 |
+
<p id="p-23" num="23">
|
| 137 |
+
<confidence value="5">[</confidence>
|
| 138 |
+
0018<confidence value="5">1</confidence>
|
| 139 |
+
Figs. 1-10 illustrate an example embodiment of a method for forming a semiconductor memory device. </p>
|
| 140 |
+
<p id="p-24" num="24">
|
| 141 |
+
<confidence value="5">[</confidence>
|
| 142 |
+
0019<confidence value="5">1</confidence>
|
| 143 |
+
Fig. 11 illustrates a perspective view of the structure formed by the embodiment of Figs. 1-10. </p>
|
| 144 |
+
<p id="p-25" num="25">
|
| 145 |
+
<confidence value="5">[</confidence>
|
| 146 |
+
0020<confidence value="5">1</confidence>
|
| 147 |
+
Figs. 12-20 illustrate another example embodiment of a method for forming a semiconductor memory device. </p>
|
| 148 |
+
<p id="p-26" num="26">[0021<confidence value="5">1</confidence>
|
| 149 |
+
Fig. 21 illustrates a NAND flash memory according to an example embodiment. </p>
|
| 150 |
+
<p id="p-27" num="27">[0022<confidence value="5">1</confidence>
|
| 151 |
+
Fig. 22 illustrates an example of a portion of the memory array in the NAND flash memory of Fig. 21. </p>
|
| 152 |
+
<p id="p-28" num="28">[0023<confidence value="5">1</confidence>
|
| 153 |
+
Fig. 23 illustrates a NOR flash memory according to an example embodiment. </p>
|
| 154 |
+
<p id="p-29" num="29">[0024<confidence value="5">1</confidence>
|
| 155 |
+
FIG. 24 illustrates a circuit pattern of the first bank BK1 as an example associated with the row and column selectors and the peripherals, shown in FIG. 23. </p>
|
| 156 |
+
<boundary-data type="header">
|
| 157 |
+
<confidence value="8">8</confidence>
|
| 158 |
+
</boundary-data>
|
| 159 |
+
<boundary-data type="header">Atty. Dkt. No.: 9862-000234/US</boundary-data>
|
| 160 |
+
<p id="p-30" num="30">
|
| 161 |
+
<page-break num="9"/>
|
| 162 |
+
[0025<confidence value="4">]</confidence>
|
| 163 |
+
Figs. 25-30 illustrate additional example embodiments employing a memory cell according to example embodiments. </p>
|
| 164 |
+
<heading id="h-8">DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS</heading>
|
| 165 |
+
<p id="p-31" num="31">[0026<confidence value="5">]</confidence>
|
| 166 |
+
Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments may be embodied in many different forms and should not be construed as being limited to the example embodiments set forth herein. Example embodiments are provided so that this disclosure will be thorough, and will fully convey the scope to those who are skilled in the art. In some example embodiments, well-known processes, well- known device structures, and well-known technologies are not described in detail to avoid the unclear interpretation of the example embodiments. </p>
|
| 167 |
+
<p id="p-32" num="32">Throughout the specification, like reference numerals in the drawings denote like elements.</p>
|
| 168 |
+
<p id="p-33" num="33">[0027<confidence value="5">]</confidence>
|
| 169 |
+
It will be understood that when an element or layer is referred to as being "on", "connected to" or "coupled to" another element or layer, it may be directly on, connected or coupled to the other element or layer, or intervening elements or layers may be present. In contrast, when an element is referred to as being "directly on," "directly connected to" or <boundary-data type="header">
|
| 170 |
+
<confidence value="8">9</confidence>
|
| 171 |
+
</boundary-data>
|
| 172 |
+
<page-break num="10"/>
|
| 173 |
+
<boundary-data type="header">Atty. Dkt. No.: 9862-000234/US</boundary-data>
|
| 174 |
+
"directly coupled to" another element or layer, there may be no intervening elements or layers present. As used herein, the term "and/or<confidence value="5">"</confidence>
|
| 175 |
+
includes any and all combinations of one or more of the associated listed items. </p>
|
| 176 |
+
<p id="p-34" num="34">[0028<confidence value="5">1</confidence>
|
| 177 |
+
It will be understood that, although the terms first, second, third, etc. may be used herein to describe various elements, components, regions, layers and/or sections, these elements, components, regions, layers and/or sections should not be limited by these terms. These terms may be only used to distinguish one element, component, region, layer or section from another region, layer or section. Thus, a first element, component, region, layer or section discussed below could be termed a second element, component, region, layer or section without departing from the teachings of the example embodiments. </p>
|
| 178 |
+
<p id="p-35" num="35">
|
| 179 |
+
<confidence value="5">[</confidence>
|
| 180 |
+
0029<confidence value="5">1</confidence>
|
| 181 |
+
Spatially relative terms, such as "beneath", "below", "lower", "above", "upper" and the like, may be used herein for ease of description to describe one element or feature's relationship to another element(s) or feature(s) as illustrated in the figures. It will be understood that the spatially relative terms may be intended to encompass different orientations of the device in use or operation in addition to the orientation depicted in the figures. For example, if the device in the figures is turned over, elements described as "below" or "beneath" other <boundary-data type="header">
|
| 182 |
+
<confidence value="88">10</confidence>
|
| 183 |
+
</boundary-data>
|
| 184 |
+
<page-break num="11"/>
|
| 185 |
+
<boundary-data type="header">
|
| 186 |
+
<confidence value="2">.</confidence>
|
| 187 |
+
Atty<confidence value="1">F</confidence>
|
| 188 |
+
Dkt. No.: 9862-000234/US </boundary-data>
|
| 189 |
+
elements or features would then be oriented "above" the other elements or features. Thus, the example term "below" can encompass both an orientation of above and below. The device may be otherwise oriented (rotated <part-num-ref name="device may be otherwise oriented (rotated">90</part-num-ref>
|
| 190 |
+
degrees or at other orientations) and the spatially relative descriptors used herein interpreted accordingly. </p>
|
| 191 |
+
<p id="p-36" num="36">
|
| 192 |
+
<confidence value="5">[</confidence>
|
| 193 |
+
0030] The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting. </p>
|
| 194 |
+
<p id="p-37" num="37">As used herein, the singular forms "a", "an" and "the" may be intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.</p>
|
| 195 |
+
<p id="p-38" num="38">
|
| 196 |
+
<confidence value="5">[</confidence>
|
| 197 |
+
0031] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will <boundary-data type="header">
|
| 198 |
+
<confidence value="88">11</confidence>
|
| 199 |
+
</boundary-data>
|
| 200 |
+
<page-break num="12"/>
|
| 201 |
+
<boundary-data type="header">Atty<confidence value="5">,</confidence>
|
| 202 |
+
Dkt. No.: 9862-000234/US </boundary-data>
|
| 203 |
+
not be interpreted in an idealized or overly formal sense unless expressly so def<confidence value="8">i</confidence>
|
| 204 |
+
ned herein. </p>
|
| 205 |
+
<p id="p-39" num="39">
|
| 206 |
+
<confidence value="5">[</confidence>
|
| 207 |
+
0032] Figs. 1-10 illustrate an example embodiment of a method for forming a semiconductor memory device. In particular, Figs. 1-10 illustrate the formation of a memory cell for a non-volatile memory. As shown in Fig. 1, a tunnel insulation layer <part-num-ref name="tunnel insulation layer">102,</part-num-ref>
|
| 208 |
+
a first floating gate layer <part-num-ref name="first floating gate layer">104,</part-num-ref>
|
| 209 |
+
a second floating gate layer <part-num-ref name="second floating gate layer">106</part-num-ref>
|
| 210 |
+
and/or a hard mask layer <part-num-ref name="hard mask layer">108</part-num-ref>
|
| 211 |
+
are sequentially formed over a semiconductor substrate <part-num-ref name="semiconductor substrate">100.</part-num-ref>
|
| 212 |
+
For example, the semiconductor substrate <part-num-ref name="semiconductor substrate">100</part-num-ref>
|
| 213 |
+
may be a silicon substrate. The tunnel insulation layer <part-num-ref name="tunnel insulation layer">102</part-num-ref>
|
| 214 |
+
may be an oxide layer. For example, the tunnel insulation layer <part-num-ref name="tunnel insulation layer">102</part-num-ref>
|
| 215 |
+
may be a silicon oxide layer formed by thermal oxidation of the semiconductor substrate <part-num-ref name="semiconductor substrate">100.</part-num-ref>
|
| 216 |
+
The tunnel insulation layer <part-num-ref name="tunnel insulation layer">102</part-num-ref>
|
| 217 |
+
may be formed to a thickness of <part-num-ref name="thickness of">80</part-num-ref>
|
| 218 |
+
Angstroms. The f<confidence value="8">i</confidence>
|
| 219 |
+
rst floating gate layer <part-num-ref name="first floating gate layer">104</part-num-ref>
|
| 220 |
+
may be formed of polysilicon. The second floating gate layer <part-num-ref name="second floating gate layer">106</part-num-ref>
|
| 221 |
+
may be formed of a metal such as tantalum nitride, titanium nitride, etc. The hard mask layer <part-num-ref name="hard mask layer">108</part-num-ref>
|
| 222 |
+
may be formed of silicon nitride. Both the first and second floating gate layers <part-num-ref name="first and second floating gate layers">104</part-num-ref>
|
| 223 |
+
and <part-num-ref name="and">106</part-num-ref>
|
| 224 |
+
may be formed by chemical vapor deposition (C<confidence value="5">V</confidence>
|
| 225 |
+
D). According to one embodiment, the combined thickness of the first and second floating gate layers <part-num-ref name="first and second floating gate layers">104</part-num-ref>
|
| 226 |
+
and <part-num-ref name="and">106</part-num-ref>
|
| 227 |
+
may be <part-num-ref name="may be">300</part-num-ref>
|
| 228 |
+
Angstroms or less. For example, both the <boundary-data type="header">
|
| 229 |
+
<confidence value="88">12</confidence>
|
| 230 |
+
</boundary-data>
|
| 231 |
+
<page-break num="13"/>
|
| 232 |
+
<boundary-data type="header">Atty. Dkt. No.: 9862-<confidence value="666">000</confidence>
|
| 233 |
+
234/US </boundary-data>
|
| 234 |
+
first and second floating gate layers <part-num-ref name="first and second floating gate layers">104</part-num-ref>
|
| 235 |
+
and <part-num-ref name="and">106</part-num-ref>
|
| 236 |
+
may each be formed to a thickness of <part-num-ref name="thickness of">50</part-num-ref>
|
| 237 |
+
Angstroms. </p>
|
| 238 |
+
<p id="p-40" num="40">
|
| 239 |
+
<confidence value="5">[</confidence>
|
| 240 |
+
0033<confidence value="5">]</confidence>
|
| 241 |
+
As shown in Fig. 2, the hard mask layer <part-num-ref name="hard mask layer">108</part-num-ref>
|
| 242 |
+
is patterned using a resist pattern (not shown) to form a hard mask pattern 1<confidence value="66">08</confidence>
|
| 243 |
+
a. Then, the second floating gate layer <part-num-ref name="second floating gate layer">106</part-num-ref>
|
| 244 |
+
and the f<confidence value="8">i</confidence>
|
| 245 |
+
rst floating gate layer <part-num-ref name="first floating gate layer">104</part-num-ref>
|
| 246 |
+
are etched using the hard mask pattern 108a as a mask. This results in a floating gate structure <part-num-ref name="floating gate structure">107</part-num-ref>
|
| 247 |
+
formed of a first floating gate 104a and a second floating gate 106a. The etching may be an isotropic dry etch. </p>
|
| 248 |
+
<p id="p-41" num="41">[0034<confidence value="4">]</confidence>
|
| 249 |
+
Next, as shown in Fig. 3, a further etch is carried out to undercut etch the first floating gate 104a. This etch may be a non- isotropic etch having etch selectivity with respect to the second floating gate 106a such that the f<confidence value="8">i</confidence>
|
| 250 |
+
rst floating gate 104a is etched, but the second floating gate 106a is not. The non-isotropic etch may be a wet etch, chemical dry etch (CDE), etc. The etching in Fig. 3 results in a first floating gate 104b having a width that is less than a width of the second floating gate 106a, and the resulting floating gate structure 107a achieves a T shape. In one embodiment, the width of the first floating gate 104b is no more than 10% less than the width of the second floating gate 106a. </p>
|
| 251 |
+
<p id="p-42" num="42">[0035<confidence value="5">]</confidence>
|
| 252 |
+
As shown in Fig. 4, a well-known shallow trench isolation (ST<confidence value="66">I)</confidence>
|
| 253 |
+
process is carried out using the hard mask pattern 108a as a mask to <boundary-data type="header">
|
| 254 |
+
<confidence value="88">13</confidence>
|
| 255 |
+
</boundary-data>
|
| 256 |
+
<page-break num="14"/>
|
| 257 |
+
<boundary-data type="header">Atty. D<confidence value="66">kt</confidence>
|
| 258 |
+
. No.: 9862-000234/US </boundary-data>
|
| 259 |
+
first form holes <part-num-ref name="mask to first form holes">110</part-num-ref>
|
| 260 |
+
in the semiconductor substrate <part-num-ref name="semiconductor substrate">100.</part-num-ref>
|
| 261 |
+
Stated another way, this process forms semiconductor substrate projections <part-num-ref name="semiconductor substrate 100. Stated another way, this process forms semiconductor substrate projections">101,</part-num-ref>
|
| 262 |
+
and results in a tunnel insulation layer 102a formed on each projection <part-num-ref name="tunnel insulation layer 102a formed on each projection">101</part-num-ref>
|
| 263 |
+
and the floating gate structure 107a formed on the tunnel insulation layer 102a. As shown, the process results in the tunnel insulation layer 102a having a width greater than the first floating gate 104b. </p>
|
| 264 |
+
<p id="p-43" num="43">[0036] Next, as shown in Fig. 5, according to an embodiment, a thin insulating layer <part-num-ref name="thin insulating layer">112</part-num-ref>
|
| 265 |
+
is formed by thermal oxidation. In particular, the thermal oxidation process forms the thin insulation layer <part-num-ref name="thin insulation layer">112</part-num-ref>
|
| 266 |
+
on surfaces of the semiconductor substrate <part-num-ref name="semiconductor substrate">100</part-num-ref>
|
| 267 |
+
defining the holes <part-num-ref name="holes">110,</part-num-ref>
|
| 268 |
+
on the sidewalls of the f<confidence value="8">i</confidence>
|
| 269 |
+
rst floating gate 104b, and on the hard mask pattern 108a. </p>
|
| 270 |
+
<p id="p-44" num="44">[0037<confidence value="4">]</confidence>
|
| 271 |
+
As shown in Fig. 6, an insulation layer <part-num-ref name="insulation layer">114</part-num-ref>
|
| 272 |
+
known as an STI isolation layer is formed over the semiconductor substrate <part-num-ref name="semiconductor substrate">100</part-num-ref>
|
| 273 |
+
to completely fill the STI holes <part-num-ref name="STI holes">110</part-num-ref>
|
| 274 |
+
and cover the floating gate structure 107a. The insulation layer <part-num-ref name="insulation layer">114</part-num-ref>
|
| 275 |
+
may be formed of silicon oxide having a good gap-filling characteristic such as high-density plasma (HDP) oxide, borophosphosilicate glass (BPSG), TOSZ, polysilazene, etc. As shown in Fig. 7, the insulation layer <part-num-ref name="insulation layer">114</part-num-ref>
|
| 276 |
+
is polished by, for example, chemical mechanical polishing (CMP) to form insulation layer 114a having an STI structure. In the CMP process, the hard mask pattern 108a is used as an <boundary-data type="header">
|
| 277 |
+
<confidence value="88">14</confidence>
|
| 278 |
+
</boundary-data>
|
| 279 |
+
<page-break num="15"/>
|
| 280 |
+
<boundary-data type="header">
|
| 281 |
+
<confidence value="5">,</confidence>
|
| 282 |
+
Atty.<confidence value="5">,</confidence>
|
| 283 |
+
Dkt. No.: 9862-000234/US </boundary-data>
|
| 284 |
+
etch stopper. Accordingly, the insulation layer 114a has projection <part-num-ref name="insulation layer 114a has projection">115</part-num-ref>
|
| 285 |
+
between which the control gate structures 107a are disposed. </p>
|
| 286 |
+
<p id="p-45" num="45">[0038<confidence value="4">]</confidence>
|
| 287 |
+
As shown in Fig. 8, the hard mask pattern 108a is removed. For example, the hard mask pattern may be removed by a well-known wet etch process. Removing the hard mask pattern 108a creates a recess <part-num-ref name="recess">116</part-num-ref>
|
| 288 |
+
defined by the insulation layer 114a. Namely, an upper surface of the floating gate structure 107a is below an upper surface of the insulation layer 114a. </p>
|
| 289 |
+
<p id="p-46" num="46">
|
| 290 |
+
<confidence value="5">[</confidence>
|
| 291 |
+
0039<confidence value="4">]</confidence>
|
| 292 |
+
As further shown in Fig. 8, the insulation layer <part-num-ref name="insulation layer">112</part-num-ref>
|
| 293 |
+
is disposed on the sidewalls of the recess <part-num-ref name="recess">116.</part-num-ref>
|
| 294 |
+
This portion of the insulation layer <part-num-ref name="insulation layer">112</part-num-ref>
|
| 295 |
+
is removed by a wet cleaning process as shown in Fig. 9. The wet cleaning process also etches the insulation layer 114a such that the edges <part-num-ref name="edges">117</part-num-ref>
|
| 296 |
+
of the upper surface of the insulation layer 114a become rounded. In one embodiment, the wet cleaning process may be performed using HF and/or distilled water. After the cleaning process, the upper surface of the floating gate structure 107a still remains below the upper surface of the insulation layer 114a. Namely, the insulation layer 11<confidence value="88">4a</confidence>
|
| 297 |
+
still defines a recess <part-num-ref name="recess">116</part-num-ref>
|
| 298 |
+
exposing the second floating gate 106a, and the floating gate structure 107a remains disposed between projections <part-num-ref name="floating gate structure 107a remains disposed between projections">115</part-num-ref>
|
| 299 |
+
of the insulation layer 114a. </p>
|
| 300 |
+
<boundary-data type="header">
|
| 301 |
+
<confidence value="88">15</confidence>
|
| 302 |
+
</boundary-data>
|
| 303 |
+
<boundary-data type="header">Atty. Dkt. No.: 9862-000234/US</boundary-data>
|
| 304 |
+
<p id="p-47" num="47">
|
| 305 |
+
<page-break num="16"/>
|
| 306 |
+
<confidence value="5">[</confidence>
|
| 307 |
+
0040<confidence value="4">]</confidence>
|
| 308 |
+
As will be appreciated from Fig. 10, a dielectric layer and conductive layer are formed over the semiconductor substrate <part-num-ref name="semiconductor substrate">100.</part-num-ref>
|
| 309 |
+
The dielectric layer covers the insulation layer 114a and f<confidence value="8">i</confidence>
|
| 310 |
+
lls the recesses <part-num-ref name="recesses">116,</part-num-ref>
|
| 311 |
+
the conductive layer covers the dielectric layer. The dielectric layer and conductive layer may be patterned (e.g., through photolithography) to form dielectric pattern <part-num-ref name="through photolithography) to form dielectric pattern">120</part-num-ref>
|
| 312 |
+
and control gate <part-num-ref name="and control gate">122.</part-num-ref>
|
| 313 |
+
For example, the dielectric pattern <part-num-ref name="dielectric pattern">120</part-num-ref>
|
| 314 |
+
may have a strip shape. However, as shown in Fig. </p>
|
| 315 |
+
<p id="p-48" num="48">10, a bottom surface of the dielectric pattern <part-num-ref name="dielectric pattern">120</part-num-ref>
|
| 316 |
+
includes projections <part-num-ref name="includes projections">121</part-num-ref>
|
| 317 |
+
projecting into and filling the recesses <part-num-ref name="recesses">116</part-num-ref>
|
| 318 |
+
such that each the projections <part-num-ref name="projections">121</part-num-ref>
|
| 319 |
+
contacts a respective second floating gate 106a. In one embodiment, the dielectric pattern <part-num-ref name="dielectric pattern">120</part-num-ref>
|
| 320 |
+
may be formed of a material having a higher dielectric constant than the f<confidence value="8">i</confidence>
|
| 321 |
+
rst and second floating gates 104b and 106a. For example, the dielectric pattern <part-num-ref name="dielectric pattern">120</part-num-ref>
|
| 322 |
+
may be formed of A<confidence value="686">120</confidence>
|
| 323 |
+
3, Hf2<confidence value="54">03</confidence>
|
| 324 |
+
, etc. In one embodiment, the dielectric constant of the dielectric pattern <part-num-ref name="dielectric pattern">120</part-num-ref>
|
| 325 |
+
may be <part-num-ref name="may be">7</part-num-ref>
|
| 326 |
+
or greater. The control gate <part-num-ref name="control gate">122</part-num-ref>
|
| 327 |
+
may be formed of polysilicon, or the control gate <part-num-ref name="control gate">122</part-num-ref>
|
| 328 |
+
may be formed of or include a metal such as W, Ti, etc. </p>
|
| 329 |
+
<p id="p-49" num="49">
|
| 330 |
+
<confidence value="5">[</confidence>
|
| 331 |
+
0041] Fig. 11 illustrates a perspective view of the structure formed in Fig. 10. As will be appreciated from Figs. 10 and <part-num-ref name="and">11,</part-num-ref>
|
| 332 |
+
because the contact area between the second floating gate 106a and dielectric pattern <part-num-ref name="second floating gate 106a and dielectric pattern">120</part-num-ref>
|
| 333 |
+
is greater than the contact area between the first floating gate 104b and the <boundary-data type="header">
|
| 334 |
+
<confidence value="88">16</confidence>
|
| 335 |
+
</boundary-data>
|
| 336 |
+
<page-break num="17"/>
|
| 337 |
+
<boundary-data type="header">Atty. Dkt. No.: 9862-<confidence value="666">000</confidence>
|
| 338 |
+
234/US </boundary-data>
|
| 339 |
+
tunnel insulation layer <part-num-ref name="tunnel insulation layer">102,</part-num-ref>
|
| 340 |
+
and the dielectric pattern <part-num-ref name="dielectric pattern">120</part-num-ref>
|
| 341 |
+
has a higher dielectric constant than the floating gate structure 107a, the coupling ratio is reduced. </p>
|
| 342 |
+
<p id="p-50" num="50">[0042<confidence value="5">]</confidence>
|
| 343 |
+
Figs. 12-20 illustrate another example embodiment of a method for forming a semiconductor memory device. In particular, Figs. 12-20 illustrate the formation of a memory cell for a non-volatile memory. As shown, in Fig. 12, a tunnel insulation layer <part-num-ref name="tunnel insulation layer">202,</part-num-ref>
|
| 344 |
+
a f<confidence value="8">i</confidence>
|
| 345 |
+
rst floating gate layer <part-num-ref name="first floating gate layer">204,</part-num-ref>
|
| 346 |
+
and a sacrificial layer or hard mask layer <part-num-ref name="sacrificial layer or hard mask layer">206</part-num-ref>
|
| 347 |
+
are sequentially formed over a semiconductor substrate <part-num-ref name="semiconductor substrate">200.</part-num-ref>
|
| 348 |
+
For example, the semiconductor substrate <part-num-ref name="semiconductor substrate">200</part-num-ref>
|
| 349 |
+
may be a silicon substrate. The tunnel insulation layer <part-num-ref name="tunnel insulation layer">202</part-num-ref>
|
| 350 |
+
may be an oxide layer. For example, the tunnel insulation layer <part-num-ref name="tunnel insulation layer">202</part-num-ref>
|
| 351 |
+
may be a silicon oxide layer formed by thermal oxidation of the semiconductor substrate <part-num-ref name="semiconductor substrate">200.</part-num-ref>
|
| 352 |
+
The tunnel insulation layer <part-num-ref name="tunnel insulation layer">202</part-num-ref>
|
| 353 |
+
may be formed to a thickness of <part-num-ref name="thickness of">80</part-num-ref>
|
| 354 |
+
Angstroms. The first floating gate layer <part-num-ref name="first floating gate layer">204</part-num-ref>
|
| 355 |
+
may be formed of polysilicon. The hard mask layer <part-num-ref name="hard mask layer">206</part-num-ref>
|
| 356 |
+
may be formed of silicon nitride. The f<confidence value="8">i</confidence>
|
| 357 |
+
rst floating gate layer <part-num-ref name="first floating gate layer">204</part-num-ref>
|
| 358 |
+
may be formed by chemical vapor deposition (CVD). According to one embodiment, the first floating gate layer <part-num-ref name="first floating gate layer">204</part-num-ref>
|
| 359 |
+
may be <part-num-ref name="may be">50</part-num-ref>
|
| 360 |
+
Angstroms or less. </p>
|
| 361 |
+
<p id="p-51" num="51">[0043<confidence value="4">]</confidence>
|
| 362 |
+
As shown in Fig. 13, the hard mask layer <part-num-ref name="hard mask layer">206</part-num-ref>
|
| 363 |
+
is patterned using a resist pattern (not shown) to form a hard mask pattern 206a. </p>
|
| 364 |
+
<boundary-data type="header">
|
| 365 |
+
<confidence value="88">17</confidence>
|
| 366 |
+
</boundary-data>
|
| 367 |
+
<boundary-data type="header">Atty<confidence value="4">,</confidence>
|
| 368 |
+
Dkt. No.: 9862-<confidence value="666">000</confidence>
|
| 369 |
+
234/US </boundary-data>
|
| 370 |
+
<p id="p-52" num="52">
|
| 371 |
+
<page-break num="18"/>
|
| 372 |
+
Then, the first floating gate layer <part-num-ref name="first floating gate layer">204</part-num-ref>
|
| 373 |
+
is etched using the hard mask pattern 206a as a mask. This results in a first floating gate 204a. The etching may be an isotropic dry etch. </p>
|
| 374 |
+
<p id="p-53" num="53">[0044<confidence value="4">]</confidence>
|
| 375 |
+
Next, as shown in Fig. 14, a further etch is carried out to undercut etch the first floating gate 204a and form f<confidence value="8">i</confidence>
|
| 376 |
+
rst floating gate 204b. This etch may be a non-isotropic etch having etch selectivity with respect to the hard mask pattern 206a such that the first floating gate <confidence value="8">1</confidence>
|
| 377 |
+
04a is etched, but the hard mask patter 206a is not. The non-isotropic etch may be a wet etch, chemical dry etch (CDE), etc. </p>
|
| 378 |
+
<p id="p-54" num="54">[0045<confidence value="5">]</confidence>
|
| 379 |
+
As shown in Fig. 14, a well-known shallow trench isolation (STI) process is carried out using the hard mask pattern 206a as a mask to first form holes <part-num-ref name="mask to first form holes">208</part-num-ref>
|
| 380 |
+
in the semiconductor substrate <part-num-ref name="semiconductor substrate">200.</part-num-ref>
|
| 381 |
+
Stated another way, this process forms semiconductor substrate projections <part-num-ref name="semiconductor substrate 200. Stated another way, this process forms semiconductor substrate projections">201,</part-num-ref>
|
| 382 |
+
and results in i) a tunnel insulation layer 202a formed on each projection <part-num-ref name="tunnel insulation layer 202a formed on each projection">201</part-num-ref>
|
| 383 |
+
and ii) the first floating gate 204b formed on the tunnel insulation layer 202a. As shown, the process results in the first floating gate 204b having a width less than the tunnel insulation layer 202a. </p>
|
| 384 |
+
<p id="p-55" num="55">[0046<confidence value="5">]</confidence>
|
| 385 |
+
Next, as shown in Fig. 15, according to an embodiment, a thin insulating layer <part-num-ref name="thin insulating layer">210</part-num-ref>
|
| 386 |
+
is formed by thermal oxidation. In particular, the thermal oxidation process forms the thin insulation layer <part-num-ref name="thin insulation layer">210</part-num-ref>
|
| 387 |
+
on surfaces of the semiconductor substrate <part-num-ref name="semiconductor substrate">200</part-num-ref>
|
| 388 |
+
defining the holes <part-num-ref name="holes">208,</part-num-ref>
|
| 389 |
+
on <boundary-data type="header">
|
| 390 |
+
<confidence value="88">18</confidence>
|
| 391 |
+
</boundary-data>
|
| 392 |
+
<page-break num="19"/>
|
| 393 |
+
<boundary-data type="header">Atty. Dkt. No.: 9862-<confidence value="666">000</confidence>
|
| 394 |
+
234/US </boundary-data>
|
| 395 |
+
the sidewalls of the first floating gate 204b, and on the hard mask pattern 206a. </p>
|
| 396 |
+
<p id="p-56" num="56">
|
| 397 |
+
<confidence value="5">[</confidence>
|
| 398 |
+
0047<confidence value="4">]</confidence>
|
| 399 |
+
As shown in Fig. 15, an insulation layer <part-num-ref name="insulation layer">212</part-num-ref>
|
| 400 |
+
known as an STI isolation layer is formed over the semiconductor substrate <part-num-ref name="semiconductor substrate">200</part-num-ref>
|
| 401 |
+
to completely fill the STI holes <part-num-ref name="STI holes">208</part-num-ref>
|
| 402 |
+
and cover the floating gate structure formed thus far. The insulation layer <part-num-ref name="insulation layer">212</part-num-ref>
|
| 403 |
+
may be formed of silicon oxide having a good gap-filling characteristic such as high-density plasma (HDP) oxide, borophosphosilicate glass (BPSG), TOSZ, polysilazene, etc. </p>
|
| 404 |
+
<p id="p-57" num="57">As shown in Fig. 15, the insulation layer <part-num-ref name="insulation layer">212</part-num-ref>
|
| 405 |
+
is polished by, for example, chemical mechanical polishing (CMP) to form insulation layer <part-num-ref name="is polished by, for example, chemical mechanical polishing (CMP) to form insulation layer">212</part-num-ref>
|
| 406 |
+
having an STI structure. In the CMP process, the hard mask pattern 206a is used as an etch stopper. Accordingly, the insulation layer <part-num-ref name="insulation layer">212</part-num-ref>
|
| 407 |
+
has projections <part-num-ref name="has projections">215</part-num-ref>
|
| 408 |
+
between which the first floating gates 204b are disposed. </p>
|
| 409 |
+
<p id="p-58" num="58">
|
| 410 |
+
<confidence value="5">[</confidence>
|
| 411 |
+
0048] As shown in Fig. 16, the hard mask pattern 206a is removed. </p>
|
| 412 |
+
<p id="p-59" num="59">For example, the hard mask pattern 206a may be removed by a well- known wet etch process. Removing the hard mask pattern 206a creates a recess <part-num-ref name="recess">216</part-num-ref>
|
| 413 |
+
defined by the insulation layer <part-num-ref name="insulation layer">212.</part-num-ref>
|
| 414 |
+
Namely, an upper surface of the first floating gate 204b is below an upper surface of the insulation layer <part-num-ref name="insulation layer">212.</part-num-ref>
|
| 415 |
+
As shown further shown in Fig. 16, the insulation layer <part-num-ref name="insulation layer">208</part-num-ref>
|
| 416 |
+
is disposed on the sidewalls of the recess <part-num-ref name="recess">216.</part-num-ref>
|
| 417 |
+
</p>
|
| 418 |
+
<boundary-data type="header">
|
| 419 |
+
<confidence value="88">19</confidence>
|
| 420 |
+
</boundary-data>
|
| 421 |
+
<boundary-data type="header">Atty<confidence value="2">,</confidence>
|
| 422 |
+
Dkt. No.: 9862-<confidence value="555">000</confidence>
|
| 423 |
+
234/US </boundary-data>
|
| 424 |
+
<p id="p-60" num="60">
|
| 425 |
+
<page-break num="20"/>
|
| 426 |
+
<confidence value="5">[</confidence>
|
| 427 |
+
0049] As shown in Fig. 17, a second floating gate layer <part-num-ref name="second floating gate layer">214</part-num-ref>
|
| 428 |
+
is formed over the substrate <part-num-ref name="substrate">200</part-num-ref>
|
| 429 |
+
such that the second floating gate layer <part-num-ref name="second floating gate layer">214</part-num-ref>
|
| 430 |
+
substantially fills the recess <part-num-ref name="recess">216</part-num-ref>
|
| 431 |
+
and covers the insulation layer <part-num-ref name="insulation layer">212.</part-num-ref>
|
| 432 |
+
The second floating gate layer <part-num-ref name="second floating gate layer">214</part-num-ref>
|
| 433 |
+
may be polysilicon, and may be deposited by CVD. A CMP process is then performed to expose the insulation layer <part-num-ref name="insulation layer">212.</part-num-ref>
|
| 434 |
+
As a result, only second floating gate layer <part-num-ref name="result, only second floating gate layer">214</part-num-ref>
|
| 435 |
+
disposed in the recess <part-num-ref name="recess">216</part-num-ref>
|
| 436 |
+
remains. </p>
|
| 437 |
+
<p id="p-61" num="61">[0050] As shown in Fig. 18, the second floating gate layer <part-num-ref name="second floating gate layer">214</part-num-ref>
|
| 438 |
+
is etched to remove a portion of the second floating<confidence value="5">,</confidence>
|
| 439 |
+
gate layer <part-num-ref name="second floating, gate layer">214</part-num-ref>
|
| 440 |
+
and the insulation layer <part-num-ref name="insulation layer">210</part-num-ref>
|
| 441 |
+
in the recess <part-num-ref name="recess">216,</part-num-ref>
|
| 442 |
+
but not to remove the entire second floating gate layer <part-num-ref name="entire second floating gate layer">214</part-num-ref>
|
| 443 |
+
and insulation layer <part-num-ref name="and insulation layer">210</part-num-ref>
|
| 444 |
+
in the recess <part-num-ref name="recess">216.</part-num-ref>
|
| 445 |
+
</p>
|
| 446 |
+
<p id="p-62" num="62">As a result, a second floating gate 214a remains after the etching process.</p>
|
| 447 |
+
<p id="p-63" num="63">The second floating gate 214a may have a thickness of <part-num-ref name="thickness of">50</part-num-ref>
|
| 448 |
+
Angstroms. It will be understood, however, that the thicknesses of the first and second floating gates 204b and 214a may be varied. However, it may be desirable to keep the total thickness of the f<confidence value="8">i</confidence>
|
| 449 |
+
rst and second floating gates 204b and 214a at <part-num-ref name="first and second floating gates 204b and 214a at">300</part-num-ref>
|
| 450 |
+
Angstroms or less. </p>
|
| 451 |
+
<p id="p-64" num="64">[0051<confidence value="4">]</confidence>
|
| 452 |
+
As further shown in Fig. 18, the etching process creates a second recess <part-num-ref name="second recess">218.</part-num-ref>
|
| 453 |
+
The etching may be by wet or dry etching, and may have an etch selectivity with respect to the insulation layer <part-num-ref name="insulation layer">212.</part-num-ref>
|
| 454 |
+
</p>
|
| 455 |
+
<p id="p-65" num="65">Furthermore, the process shown in Figs. 16-18 results in the second <boundary-data type="header">
|
| 456 |
+
<confidence value="88">20</confidence>
|
| 457 |
+
</boundary-data>
|
| 458 |
+
<page-break num="21"/>
|
| 459 |
+
<boundary-data type="header">
|
| 460 |
+
<confidence value="5">.</confidence>
|
| 461 |
+
Atty.<confidence value="5">,</confidence>
|
| 462 |
+
Dkt. No.: 9862-000234/US </boundary-data>
|
| 463 |
+
floating gate 214a having a width that is greater than a width of the f<confidence value="8">i</confidence>
|
| 464 |
+
rst floating gate 204b, and a resulting floating gate structure <part-num-ref name="resulting floating gate structure">207</part-num-ref>
|
| 465 |
+
achieves a T shape. In one embodiment, the width of the first floating gate 204b is no more than 10% less than the width of the second floating gate 214a. </p>
|
| 466 |
+
<p id="p-66" num="66">Still further, the resulting upper surface of the floating gate structure <part-num-ref name="floating gate structure">207</part-num-ref>
|
| 467 |
+
(i.e., the upper surface of the second floating gate 214a) is below the upper surface of the projections <part-num-ref name="projections">215</part-num-ref>
|
| 468 |
+
of the insulation layer <part-num-ref name="insulation layer">212.</part-num-ref>
|
| 469 |
+
</p>
|
| 470 |
+
<p id="p-67" num="67">[0052<confidence value="4">]</confidence>
|
| 471 |
+
Next, as shown in Fig. 19, a wet cleaning process is performed to etch the insulation layer <part-num-ref name="insulation layer">212</part-num-ref>
|
| 472 |
+
such that the edges <part-num-ref name="edges">217</part-num-ref>
|
| 473 |
+
of the upper surface of the insulation layer <part-num-ref name="insulation layer">212</part-num-ref>
|
| 474 |
+
become rounded. In one embodiment, the wet cleaning process may be performed using HF and/or distilled water. After the cleaning process, the upper surface of the floating gate structure <part-num-ref name="floating gate structure">207</part-num-ref>
|
| 475 |
+
still remains below the upper surface of the insulation layer <part-num-ref name="insulation layer">212.</part-num-ref>
|
| 476 |
+
Namely, the insulation layer <part-num-ref name="insulation layer">212</part-num-ref>
|
| 477 |
+
still defines a recess <part-num-ref name="recess">218</part-num-ref>
|
| 478 |
+
exposing the second floating gate 214a, and the floating gate structure <part-num-ref name="floating gate structure">207</part-num-ref>
|
| 479 |
+
remains disposed between projections <part-num-ref name="remains disposed between projections">215</part-num-ref>
|
| 480 |
+
of the insulation layer <part-num-ref name="insulation layer">212.</part-num-ref>
|
| 481 |
+
</p>
|
| 482 |
+
<p id="p-68" num="68">[0053<confidence value="5">]</confidence>
|
| 483 |
+
As will be appreciated from Fig. 20, a dielectric layer and conductive layer are formed over the semiconductor substrate <part-num-ref name="semiconductor substrate">200.</part-num-ref>
|
| 484 |
+
The dielectric layer covers the insulation layer <part-num-ref name="insulation layer">212</part-num-ref>
|
| 485 |
+
and fills the recesses <part-num-ref name="recesses">218,</part-num-ref>
|
| 486 |
+
the conductive layer covers the dielectric layer. The dielectric layer and <boundary-data type="header">
|
| 487 |
+
<confidence value="88">21</confidence>
|
| 488 |
+
</boundary-data>
|
| 489 |
+
<page-break num="22"/>
|
| 490 |
+
<boundary-data type="header">Atty. Dkt. No.: 9862-000234/US</boundary-data>
|
| 491 |
+
conductive layer may be patterned (e.g., through photolithography) to form dielectric pattern <part-num-ref name="through photolithography) to form dielectric pattern">220</part-num-ref>
|
| 492 |
+
and control gate <part-num-ref name="and control gate">222.</part-num-ref>
|
| 493 |
+
For example, the dielectric pattern <part-num-ref name="dielectric pattern">220</part-num-ref>
|
| 494 |
+
may have a strip shape. However, as shown in Fig. </p>
|
| 495 |
+
<p id="p-69" num="69">20, a bottom surface of the dielectric pattern <part-num-ref name="dielectric pattern">220</part-num-ref>
|
| 496 |
+
includes projections <part-num-ref name="includes projections">221</part-num-ref>
|
| 497 |
+
projecting into and filling the recesses <part-num-ref name="recesses">218</part-num-ref>
|
| 498 |
+
such that each the projections <part-num-ref name="projections">221</part-num-ref>
|
| 499 |
+
contacts a respective second floating gate 214a. In one embodiment, the dielectric pattern <part-num-ref name="dielectric pattern">220</part-num-ref>
|
| 500 |
+
may be formed of a material having a higher dielectric constant than the first and second floating gates 204b and 214a. For example, the dielectric pattern <part-num-ref name="dielectric pattern">220</part-num-ref>
|
| 501 |
+
may be formed of A<confidence value="685">120</confidence>
|
| 502 |
+
3, Hf2<confidence value="54">O3</confidence>
|
| 503 |
+
, etc. In one embodiment, the dielectric constant of the dielectric pattern <part-num-ref name="dielectric pattern">220</part-num-ref>
|
| 504 |
+
may be <part-num-ref name="may be">7</part-num-ref>
|
| 505 |
+
or greater. The control gate <part-num-ref name="control gate">222</part-num-ref>
|
| 506 |
+
may be formed of polysilicon, or the control gate <part-num-ref name="control gate">222</part-num-ref>
|
| 507 |
+
may be formed of or include a metal such as W, Ti, etc. </p>
|
| 508 |
+
<boundary-data type="header">
|
| 509 |
+
<confidence value="88">22</confidence>
|
| 510 |
+
</boundary-data>
|
| 511 |
+
<boundary-data type="header">
|
| 512 |
+
<confidence value="2222">Atty</confidence>
|
| 513 |
+
. Dkt. No.: 9862-000234/US </boundary-data>
|
| 514 |
+
<p id="p-70" num="70">
|
| 515 |
+
<page-break num="23"/>
|
| 516 |
+
[0054<confidence value="5">]</confidence>
|
| 517 |
+
Fig. 21 illustrates a NAND flash memory according to an embodiment of the present invention. As shown, the NAND flash memory includes a memory array <part-num-ref name="memory array">310</part-num-ref>
|
| 518 |
+
of memory cells to store data, a page buffer block <part-num-ref name="page buffer block">320,</part-num-ref>
|
| 519 |
+
a Y-gating circuit <part-num-ref name="Y-gating circuit">330</part-num-ref>
|
| 520 |
+
and/or control/decoder circuitry <part-num-ref name="and/or control/decoder circuitry">340</part-num-ref>
|
| 521 |
+
for controlling the operation of the memory array <part-num-ref name="memory array">310,</part-num-ref>
|
| 522 |
+
the page buffer block <part-num-ref name="page buffer block">320,</part-num-ref>
|
| 523 |
+
and the Y-gating circuit <part-num-ref name="Y-gating circuit">330.</part-num-ref>
|
| 524 |
+
The control/decoder circuitry <part-num-ref name="control/decoder circuitry">340</part-num-ref>
|
| 525 |
+
receives command signals and an address, and generates control signals for controlling the memory array <part-num-ref name="memory array">310,</part-num-ref>
|
| 526 |
+
the page buffer block <part-num-ref name="page buffer block">320,</part-num-ref>
|
| 527 |
+
and the Y-gating circuit <part-num-ref name="Y-gating circuit">330.</part-num-ref>
|
| 528 |
+
</p>
|
| 529 |
+
<p id="p-71" num="71">
|
| 530 |
+
<confidence value="5">[</confidence>
|
| 531 |
+
0055<confidence value="5">]</confidence>
|
| 532 |
+
Fig. 22 illustrates an example of a portion of the memory array <part-num-ref name="memory array">310.</part-num-ref>
|
| 533 |
+
As shown, the memory array <part-num-ref name="memory array">310</part-num-ref>
|
| 534 |
+
includes a plurality of bit lines B/Le, B/Lo, where "e" and "o" designate even and odd bit lines. The memory cell array <part-num-ref name="memory cell array">310</part-num-ref>
|
| 535 |
+
includes a plurality of cell strings each respectively connected to one of bit lines B/Le and B/Lo. Each cell string in the illustrated example is formed from a string selection transistor SST connected to its corresponding bit line, a ground selection transistor GST connected to a common source line CSL, and a plurality of memory cells <confidence value="85">M1</confidence>
|
| 536 |
+
-Mm connected in series between the string selection transistor SST and the ground selection transistor GST. Each memory cell M 1-Mm may be formed according to one of the above described embodiments. While not shown in Fig. 22, more than one string may be connected to a bit line. </p>
|
| 537 |
+
<boundary-data type="header">
|
| 538 |
+
<confidence value="88">23</confidence>
|
| 539 |
+
</boundary-data>
|
| 540 |
+
<boundary-data type="header">Atty. Dkt. No.: 9862-<confidence value="666">000</confidence>
|
| 541 |
+
234/US </boundary-data>
|
| 542 |
+
<p id="p-72" num="72">
|
| 543 |
+
<page-break num="24"/>
|
| 544 |
+
Each bit line may be connected to a respective page buffer in the page buffer block <part-num-ref name="page buffer block">320.</part-num-ref>
|
| 545 |
+
</p>
|
| 546 |
+
<p id="p-73" num="73">[0056<confidence value="5">1</confidence>
|
| 547 |
+
The page buffer block <part-num-ref name="page buffer block">320</part-num-ref>
|
| 548 |
+
includes a plurality of page buffers for reading and writing data into the memory array <part-num-ref name="memory array">310</part-num-ref>
|
| 549 |
+
based on the control signals from the control/decoder circuitry <part-num-ref name="control/decoder circuitry">340.</part-num-ref>
|
| 550 |
+
The Y-gating circuit <part-num-ref name="Y-gating circuit">330</part-num-ref>
|
| 551 |
+
selects page buffers in the page buffer block <part-num-ref name="page buffer block">320</part-num-ref>
|
| 552 |
+
for input of data or output of data based on the control signals from the control/decoder circuitry <part-num-ref name="control/decoder circuitry">340.</part-num-ref>
|
| 553 |
+
Because the structure and operation of the page buffer block <part-num-ref name="page buffer block">320,</part-num-ref>
|
| 554 |
+
the Y-gating circuit <part-num-ref name="Y-gating circuit">330</part-num-ref>
|
| 555 |
+
and the control/decoder circuitry <part-num-ref name="control/decoder circuitry">340</part-num-ref>
|
| 556 |
+
are so well-known, the structure and operation of these elements will not be described in detail for the sake of brevity. Instead, USP 7,042,770 illustrating an example NAND flash memory, which may employ the embodiments of the present invention, is hereby incorporated by reference in its entirety. </p>
|
| 557 |
+
<p id="p-74" num="74">[0057<confidence value="2">]</confidence>
|
| 558 |
+
Furthermore, it will be appreciated that the embodiments of the present invention are not limited in application to a NAND flash memory having the architecture described above with respect to Figs. 21-22. </p>
|
| 559 |
+
<p id="p-75" num="75">Instead, the embodiment of the present invention may be applied to the cell array of various NAND flash memory architectures.</p>
|
| 560 |
+
<p id="p-76" num="76">[0058<confidence value="5">1</confidence>
|
| 561 |
+
Fig. 23 illustrates a NOR flash memory according to an embodiment of the present invention. As shown, the NOR flash memory <boundary-data type="header">
|
| 562 |
+
<confidence value="88">24</confidence>
|
| 563 |
+
</boundary-data>
|
| 564 |
+
<page-break num="25"/>
|
| 565 |
+
<boundary-data type="header">
|
| 566 |
+
<confidence value="6">,</confidence>
|
| 567 |
+
Atty. <confidence value="5">D</confidence>
|
| 568 |
+
kt. No.: 9862-000234/US </boundary-data>
|
| 569 |
+
device <part-num-ref name="NOR flash memory device">400</part-num-ref>
|
| 570 |
+
includes a cell array <part-num-ref name="cell array">410,</part-num-ref>
|
| 571 |
+
a row selector <part-num-ref name="row selector">440,</part-num-ref>
|
| 572 |
+
and/or a column selector <part-num-ref name="column selector">450.</part-num-ref>
|
| 573 |
+
</p>
|
| 574 |
+
<p id="p-77" num="77">[0059] The cell array <part-num-ref name="cell array">410</part-num-ref>
|
| 575 |
+
is composed of a plurality of banks BK<confidence value="5">1</confidence>
|
| 576 |
+
-BKn. </p>
|
| 577 |
+
<p id="p-78" num="78">Each bank includes of a plurality of sectors SC <confidence value="6">1</confidence>
|
| 578 |
+
-SCm, each as a unit of erasing. Each sector is constructed of a plurality of memory cells (not shown) coupled to a plurality of wordlines and bitlines. Output lines and output circuitry are not shown in FIG. 23 so that the overall NOR flash memory device <part-num-ref name="overall NOR flash memory device">400</part-num-ref>
|
| 579 |
+
is simply and clearly illustrated. </p>
|
| 580 |
+
<p id="p-79" num="79">[0060<confidence value="5">]</confidence>
|
| 581 |
+
The row selector <part-num-ref name="row selector">440</part-num-ref>
|
| 582 |
+
selects one wordline in response to a row address XA. The column selector <part-num-ref name="column selector">450</part-num-ref>
|
| 583 |
+
selects <part-num-ref name="selects">16</part-num-ref>
|
| 584 |
+
bitlines for every bank in response to a column address YA. The structures and operations regarding the cell array <part-num-ref name="cell array">410,</part-num-ref>
|
| 585 |
+
the row selector <part-num-ref name="row selector">440,</part-num-ref>
|
| 586 |
+
and the column selector <part-num-ref name="column selector">450</part-num-ref>
|
| 587 |
+
will be described with reference to FIG. 24 in detail. </p>
|
| 588 |
+
<p id="p-80" num="80">
|
| 589 |
+
<confidence value="5">[</confidence>
|
| 590 |
+
0061<confidence value="5">]</confidence>
|
| 591 |
+
The NOR flash memory device <part-num-ref name="NOR flash memory device">400</part-num-ref>
|
| 592 |
+
also includes a data input buffer <part-num-ref name="data input buffer">420,</part-num-ref>
|
| 593 |
+
a program driver <part-num-ref name="program driver">430,</part-num-ref>
|
| 594 |
+
and/or a controller <part-num-ref name="controller">470.</part-num-ref>
|
| 595 |
+
The data input buffer <part-num-ref name="data input buffer">420</part-num-ref>
|
| 596 |
+
receives program data of <part-num-ref name="receives program data of">16</part-num-ref>
|
| 597 |
+
bits in parallel, equal to the number of banks. The program data is stored in unit buffers <confidence value="68">IB</confidence>
|
| 598 |
+
<confidence value="6">1</confidence>
|
| 599 |
+
-IBn of the input buffer <part-num-ref name="input buffer">420</part-num-ref>
|
| 600 |
+
in units of <part-num-ref name="in units of">16</part-num-ref>
|
| 601 |
+
bits. The unit buffers IB1-IBn are alternatively operable under the control of data latch signals DLj <confidence value="66">(j</confidence>
|
| 602 |
+
=1.about.n). For instance, if DL1 is a high level, the first unit buffer IB<confidence value="5">1</confidence>
|
| 603 |
+
receives <part-num-ref name="first unit buffer IB1 receives">16</part-num-ref>
|
| 604 |
+
data bits in parallel. The receiver data is held in the first unit <boundary-data type="header">
|
| 605 |
+
<confidence value="88">25</confidence>
|
| 606 |
+
</boundary-data>
|
| 607 |
+
<page-break num="26"/>
|
| 608 |
+
<boundary-data type="header">Atty. Dkt. No.: 9862-<confidence value="666">000</confidence>
|
| 609 |
+
234/US </boundary-data>
|
| 610 |
+
buffer IB<confidence value="5">1</confidence>
|
| 611 |
+
for a time. The data input buffer <part-num-ref name="data input buffer">420</part-num-ref>
|
| 612 |
+
dumps data held in the unit buffers IB<confidence value="4">1</confidence>
|
| 613 |
+
-IBn contemporaneously to the program driver <part-num-ref name="program driver">430</part-num-ref>
|
| 614 |
+
when the program selection signal PSEL is a high level. </p>
|
| 615 |
+
<p id="p-81" num="81">[0062<confidence value="4">]</confidence>
|
| 616 |
+
The controller <part-num-ref name="controller">470</part-num-ref>
|
| 617 |
+
applies the program selection signal PSEL and the data latch signal DLj to the data input buffer <part-num-ref name="data input buffer">420.</part-num-ref>
|
| 618 |
+
The data input buffer <part-num-ref name="data input buffer">420</part-num-ref>
|
| 619 |
+
may receive the program data in units of <part-num-ref name="program data in units of">16</part-num-ref>
|
| 620 |
+
bits by the number of the banks or less, alternatively or sequentially, under regulation of the controller <part-num-ref name="controller">470.</part-num-ref>
|
| 621 |
+
</p>
|
| 622 |
+
<p id="p-82" num="82">[0063<confidence value="5">]</confidence>
|
| 623 |
+
The program driver <part-num-ref name="program driver">30</part-num-ref>
|
| 624 |
+
applies a program voltage contemporaneously to selected bitlines among bitline packets BL<confidence value="5">l</confidence>
|
| 625 |
+
i-BLni (i=<confidence value="88">1.</confidence>
|
| 626 |
+
about. <part-num-ref name="program voltage contemporaneously to selected bitlines among bitline packets BLli-BLni (i=1. about.">
|
| 627 |
+
<confidence value="5">1</confidence>
|
| 628 |
+
6) </part-num-ref>
|
| 629 |
+
in response to program data packets DB <part-num-ref name="in response to program data packets DB">
|
| 630 |
+
<confidence value="6">1</confidence>
|
| 631 |
+
</part-num-ref>
|
| 632 |
+
i-DBni (i=1<confidence value="8">.</confidence>
|
| 633 |
+
about. <part-num-ref name="i-DBni (i=1.about.">16)</part-num-ref>
|
| 634 |
+
stored in the data input buffer <part-num-ref name="data input buffer">420.</part-num-ref>
|
| 635 |
+
The program driver includes unit drivers PD <confidence value="8">1</confidence>
|
| 636 |
+
-PDn corresponding to the unit buffers <confidence value="68">IB</confidence>
|
| 637 |
+
<confidence value="8">1</confidence>
|
| 638 |
+
-IBn. </p>
|
| 639 |
+
<p id="p-83" num="83">The program driver 430 is supplied with a high voltage VPP from an external power source that is greater than the (internal) power source voltage. The high voltage VPP from the external source is used for supplying a drain voltage and a cell current of a selected cell transistor in a program operation. Otherwise, it may be possible to supply the high voltage VPP internally by using a charge pump circuit (not shown) embedded in the NOR flash memory device.</p>
|
| 640 |
+
<boundary-data type="header">
|
| 641 |
+
<confidence value="88">26</confidence>
|
| 642 |
+
</boundary-data>
|
| 643 |
+
<boundary-data type="header">Atty., Dkt. No.: 9862-000234/US</boundary-data>
|
| 644 |
+
<p id="p-84" num="84">
|
| 645 |
+
<page-break num="27"/>
|
| 646 |
+
<confidence value="5">[</confidence>
|
| 647 |
+
0064<confidence value="4">]</confidence>
|
| 648 |
+
The NOR flash memory device <part-num-ref name="NOR flash memory device">400</part-num-ref>
|
| 649 |
+
also includes a fail detector <part-num-ref name="fail detector">460.</part-num-ref>
|
| 650 |
+
The fail detector senses data stored in the cell array <part-num-ref name="cell array">410</part-num-ref>
|
| 651 |
+
and then detects a failure of programming by comparing the sense data with the program data stored in the data input buffer <part-num-ref name="data input buffer">420.</part-num-ref>
|
| 652 |
+
The fail detector <part-num-ref name="fail detector">460</part-num-ref>
|
| 653 |
+
is shared by all the banks of the cell array <part-num-ref name="cell array">410.</part-num-ref>
|
| 654 |
+
</p>
|
| 655 |
+
<p id="p-85" num="85">[0065<confidence value="4">]</confidence>
|
| 656 |
+
As illustrated in FIG. 23, the NOR flash memory device <part-num-ref name="NOR flash memory device">400</part-num-ref>
|
| 657 |
+
receives command signals CMD, address signals ADD, data DQi, and the high voltage VPP. For example, these signals may be supplied from a host device or memory controller. </p>
|
| 658 |
+
<p id="p-86" num="86">
|
| 659 |
+
<confidence value="5">[</confidence>
|
| 660 |
+
0066<confidence value="5">]</confidence>
|
| 661 |
+
FIG. 24 illustrates a circuit pattern of the first bank BK<confidence value="4">1</confidence>
|
| 662 |
+
as an example associated with the row and column selectors and the peripherals, shown in FIG. 23. The row selector <part-num-ref name="row selector">440</part-num-ref>
|
| 663 |
+
includes a plurality of row decoders RD <confidence value="8">1</confidence>
|
| 664 |
+
-RDm while the column selector <part-num-ref name="column selector">450</part-num-ref>
|
| 665 |
+
includes a plurality of column decoders CD<confidence value="5">1</confidence>
|
| 666 |
+
-CDm. Pairs of the row and column decoders correspond each to the sectors SC <confidence value="6">1</confidence>
|
| 667 |
+
-SCm. The column selector <part-num-ref name="column selector">450</part-num-ref>
|
| 668 |
+
is further comprised of a global column decoder GCD <part-num-ref name="global column decoder GCD">1</part-num-ref>
|
| 669 |
+
arranged corresponding to the first bank BK<confidence value="58">l.</confidence>
|
| 670 |
+
</p>
|
| 671 |
+
<p id="p-87" num="87">
|
| 672 |
+
<confidence value="5">[</confidence>
|
| 673 |
+
0067<confidence value="5">]</confidence>
|
| 674 |
+
Referring to FIG. 24, in the first bank BK1 composed of the plurality of sectors SC 1-SCm, each of which forms the erase unit, the first sector SC <part-num-ref name="first sector SC">1</part-num-ref>
|
| 675 |
+
is coupled to the row decoder RD <part-num-ref name="row decoder RD">1</part-num-ref>
|
| 676 |
+
for driving a wordline assigned to a selected memory cell MC and the column decoder for <boundary-data type="header">
|
| 677 |
+
<confidence value="88">27</confidence>
|
| 678 |
+
</boundary-data>
|
| 679 |
+
<page-break num="28"/>
|
| 680 |
+
<boundary-data type="header">Atty., Dkt. No.: 9862-<confidence value="666">000</confidence>
|
| 681 |
+
234/US </boundary-data>
|
| 682 |
+
selecting the bitlines BL<confidence value="5">1</confidence>
|
| 683 |
+
-BLk that are assigned to a global bitline (e.g., GBL1). The memory cells MC may be formed according to an embodiment of the present invention. The global bitlines are exemplarily arranged in numbers of <part-num-ref name="global bitlines are exemplarily arranged in numbers of">16,</part-num-ref>
|
| 684 |
+
<confidence value="66">so</confidence>
|
| 685 |
+
that each of the global bitlines GBL<confidence value="68">1-</confidence>
|
| 686 |
+
GBL16 is linked with the bitlines BL<confidence value="4">1</confidence>
|
| 687 |
+
-BLk (preferably namable as local bitlines relative to the global bitlines) through their corresponding column gate transistors in every sector. The column gate transistors are controlled by the column decoder corresponding thereto. Other sectors are disposed with the same connected feature as the first sector SC <part-num-ref name="first sector SC">
|
| 688 |
+
<confidence value="88">1.</confidence>
|
| 689 |
+
</part-num-ref>
|
| 690 |
+
</p>
|
| 691 |
+
<p id="p-88" num="88">
|
| 692 |
+
<confidence value="5">[</confidence>
|
| 693 |
+
0068<confidence value="5">1</confidence>
|
| 694 |
+
The global bitlines GBL1.about.GBL16 are lead from one (e.g., <confidence value="885">BL1</confidence>
|
| 695 |
+
i) of the bitline packets BL<confidence value="588">li.</confidence>
|
| 696 |
+
about.BLni provided by the program driver <part-num-ref name="program driver">30,</part-num-ref>
|
| 697 |
+
each by way of selection transistors G <confidence value="88">1.</confidence>
|
| 698 |
+
about.<confidence value="8">G</confidence>
|
| 699 |
+
<part-num-ref name="program driver 30, each by way of selection transistors G 1.about.G">16</part-num-ref>
|
| 700 |
+
controlled by the global column decoder GCD <part-num-ref name="global column decoder GCD">1.</part-num-ref>
|
| 701 |
+
As a result, the memory cell array is constructed in a hierarchical architecture with the local bitlines each connected to the memory cells along columns and the global bitlines each connected to a group of the local bitlines. </p>
|
| 702 |
+
<p id="p-89" num="89">[0069<confidence value="2">]</confidence>
|
| 703 |
+
Because the operation and further detailed structure of the NOR flash memory illustrated in Figs. 23-24 is well-known, further description will not be provided for the sake of brevity. Instead, USP 7,072,214 illustrating an example NOR flash memory, which may employ <boundary-data type="header">
|
| 704 |
+
<confidence value="88">28</confidence>
|
| 705 |
+
</boundary-data>
|
| 706 |
+
<page-break num="29"/>
|
| 707 |
+
<boundary-data type="header">
|
| 708 |
+
<confidence value="2">'</confidence>
|
| 709 |
+
Atty.<confidence value="2">,</confidence>
|
| 710 |
+
Dkt. No.: 9862-000234/US </boundary-data>
|
| 711 |
+
the embodiments of the present invention, is hereby incorporated by reference in its entirety. </p>
|
| 712 |
+
<p id="p-90" num="90">[0070<confidence value="5">]</confidence>
|
| 713 |
+
Furthermore, it will be appreciated that the embodiments of the present invention are not limited in application to a NOR flash memory having the architecture described above with respect to Figs. 23-24. </p>
|
| 714 |
+
<p id="p-91" num="91">Instead, the embodiment of the present invention may be applied to the cell array of various NOR flash memory architectures.</p>
|
| 715 |
+
<p id="p-92" num="92">[0071] Fig. 25 illustrates another embodiment. As shown, this embodiment includes a memory <part-num-ref name="memory">510</part-num-ref>
|
| 716 |
+
connected to a memory controller <part-num-ref name="memory controller">520.</part-num-ref>
|
| 717 |
+
The memory <part-num-ref name="memory">510</part-num-ref>
|
| 718 |
+
may be the NAND flash memory or NOR flash memory discussed above. However, the memory <part-num-ref name="memory">510</part-num-ref>
|
| 719 |
+
is not limited to these memory architectures, and may be any memory architecture having memory cells formed according to an embodiment of the present invention. The memory controller <part-num-ref name="memory controller">520</part-num-ref>
|
| 720 |
+
supplies the input signals for controlling operation of the memory <part-num-ref name="memory">510.</part-num-ref>
|
| 721 |
+
For example, in the case of the NAND flash memory of Figs. 21-22, the memory controller <part-num-ref name="memory controller">520</part-num-ref>
|
| 722 |
+
supplies the command CMD and address signals. In the example of the NOR flash memory of Figs. 23-24, the memory controller <part-num-ref name="memory controller">520</part-num-ref>
|
| 723 |
+
supplies the CMD, ADD, DQ and VPP signals. It will be appreciated that the memory controller <part-num-ref name="memory controller">520</part-num-ref>
|
| 724 |
+
may control the memory <part-num-ref name="memory">510</part-num-ref>
|
| 725 |
+
based on received control signals (not shown). </p>
|
| 726 |
+
<boundary-data type="header">
|
| 727 |
+
<confidence value="88">29</confidence>
|
| 728 |
+
</boundary-data>
|
| 729 |
+
<boundary-data type="header">Atty. Dkt. No.: 9862-000234/US</boundary-data>
|
| 730 |
+
<p id="p-93" num="93">
|
| 731 |
+
<page-break num="30"/>
|
| 732 |
+
[0072<confidence value="4">]</confidence>
|
| 733 |
+
Fig. 26 illustrates yet another embodiment. This embodiment is the same as the embodiment of Fig. 25, except that the memory <part-num-ref name="memory">510</part-num-ref>
|
| 734 |
+
and memory controller <part-num-ref name="and memory controller">520</part-num-ref>
|
| 735 |
+
have been embodied as a card <part-num-ref name="card">530.</part-num-ref>
|
| 736 |
+
For example, the card <part-num-ref name="card">530</part-num-ref>
|
| 737 |
+
may be a memory card such as a flash memory card. </p>
|
| 738 |
+
<p id="p-94" num="94">Namely, the card <part-num-ref name="card">530</part-num-ref>
|
| 739 |
+
may be a card meeting any industry standard for use with a consumer electronics device such as a digital camera, personal computer, etc. It will be appreciated that the memory controller <part-num-ref name="memory controller">520</part-num-ref>
|
| 740 |
+
may control the memory <part-num-ref name="memory">510</part-num-ref>
|
| 741 |
+
based on controls signals received by the card <part-num-ref name="card">530</part-num-ref>
|
| 742 |
+
from another (e.g., external) device. </p>
|
| 743 |
+
<p id="p-95" num="95">
|
| 744 |
+
<confidence value="5">[</confidence>
|
| 745 |
+
0073<confidence value="5">]</confidence>
|
| 746 |
+
Fig. 27 illustrates a further embodiment. This embodiment represents a portable device <part-num-ref name="portable device">600.</part-num-ref>
|
| 747 |
+
The portable device <part-num-ref name="portable device">600</part-num-ref>
|
| 748 |
+
may be an MP3 player, video player, combination video and audio player, etc. As shown, the portable device <part-num-ref name="portable device">600</part-num-ref>
|
| 749 |
+
includes the memory <part-num-ref name="memory">510</part-num-ref>
|
| 750 |
+
and memory controller <part-num-ref name="and memory controller">520.</part-num-ref>
|
| 751 |
+
The portable device <part-num-ref name="portable device">600</part-num-ref>
|
| 752 |
+
may also includes an encoder and decoder <part-num-ref name="encoder and decoder">610,</part-num-ref>
|
| 753 |
+
presentation components <part-num-ref name="encoder and decoder 610, presentation components">620</part-num-ref>
|
| 754 |
+
and interface <part-num-ref name="and interface">630.</part-num-ref>
|
| 755 |
+
</p>
|
| 756 |
+
<p id="p-96" num="96">
|
| 757 |
+
<confidence value="5">[</confidence>
|
| 758 |
+
0074<confidence value="4">]</confidence>
|
| 759 |
+
Data (video, audio, etc.) is input to and output from the memory <part-num-ref name="memory">510</part-num-ref>
|
| 760 |
+
via the memory controller <part-num-ref name="memory controller">520</part-num-ref>
|
| 761 |
+
by an encoder and decoder (EDC) <part-num-ref name="encoder and decoder (EDC)">610.</part-num-ref>
|
| 762 |
+
</p>
|
| 763 |
+
<p id="p-97" num="97">As shown by the dashed lines in Fig. 27, the data may be directly input to the memory <part-num-ref name="memory">510</part-num-ref>
|
| 764 |
+
from the EDC <part-num-ref name="EDC">610</part-num-ref>
|
| 765 |
+
and/or directly output from the memory <part-num-ref name="memory">510</part-num-ref>
|
| 766 |
+
to the EDC <part-num-ref name="EDC">610.</part-num-ref>
|
| 767 |
+
</p>
|
| 768 |
+
<boundary-data type="header">
|
| 769 |
+
<confidence value="88">30</confidence>
|
| 770 |
+
</boundary-data>
|
| 771 |
+
<boundary-data type="header">Atty<confidence value="5">.</confidence>
|
| 772 |
+
Dkt. No.: 9862-000234/US </boundary-data>
|
| 773 |
+
<p id="p-98" num="98">
|
| 774 |
+
<page-break num="31"/>
|
| 775 |
+
[0075<confidence value="5">]</confidence>
|
| 776 |
+
The EDC <part-num-ref name="EDC">610</part-num-ref>
|
| 777 |
+
encodes data for storage in the memory <part-num-ref name="memory">510.</part-num-ref>
|
| 778 |
+
For example, the EDC <part-num-ref name="EDC">610</part-num-ref>
|
| 779 |
+
may perform MP3 encoding on audio data for storage in the memory <part-num-ref name="memory">510.</part-num-ref>
|
| 780 |
+
Alternatively, the EDC <part-num-ref name="EDC">610</part-num-ref>
|
| 781 |
+
may perform MPEG encoding (e.g., MPEG2, MPEG4, etc.) on video data for storage in the memory <part-num-ref name="memory">510.</part-num-ref>
|
| 782 |
+
Still further, the EDC <part-num-ref name="EDC">610</part-num-ref>
|
| 783 |
+
may include multiple encoders for encoding different types of data according to different data formats. For example, the EDC <part-num-ref name="EDC">610</part-num-ref>
|
| 784 |
+
may include an MP3 encoder for audio data and an MPEG encoder for video data. </p>
|
| 785 |
+
<p id="p-99" num="99">
|
| 786 |
+
<confidence value="5">[</confidence>
|
| 787 |
+
0076<confidence value="5">1</confidence>
|
| 788 |
+
The EDC <part-num-ref name="EDC">610</part-num-ref>
|
| 789 |
+
may decode output from the memory <part-num-ref name="memory">510.</part-num-ref>
|
| 790 |
+
For example, the EDC <part-num-ref name="EDC">610</part-num-ref>
|
| 791 |
+
may perform MP3 decoding on audio data output from the memory <part-num-ref name="memory">510.</part-num-ref>
|
| 792 |
+
Alternatively, the EDC <part-num-ref name="EDC">610</part-num-ref>
|
| 793 |
+
may perform MPEG decoding (e.g., MPEG2, MPEG4, etc.) on video data output from the memory <part-num-ref name="memory">510.</part-num-ref>
|
| 794 |
+
Still further, the EDC <part-num-ref name="EDC">610</part-num-ref>
|
| 795 |
+
may include multiple decoders for decoding different types of data according to different data formats. </p>
|
| 796 |
+
<p id="p-100" num="100">For example, the EDC <part-num-ref name="EDC">610</part-num-ref>
|
| 797 |
+
may include an MP3 decoder for audio data and an MPEG decoder for video data. </p>
|
| 798 |
+
<p id="p-101" num="101">[0077<confidence value="5">1</confidence>
|
| 799 |
+
It will also be appreciated that EDC 610 may include only decoders. For example, already encoded data may be received by the EDC <part-num-ref name="EDC">610</part-num-ref>
|
| 800 |
+
and passed to the memory controller <part-num-ref name="memory controller">520</part-num-ref>
|
| 801 |
+
and/or the memory <part-num-ref name="memory">510.</part-num-ref>
|
| 802 |
+
</p>
|
| 803 |
+
<boundary-data type="header">
|
| 804 |
+
<confidence value="88">31</confidence>
|
| 805 |
+
</boundary-data>
|
| 806 |
+
<boundary-data type="header">Atty.<confidence value="4">'</confidence>
|
| 807 |
+
Dkt. No.: 9862-000234/U<confidence value="5">S</confidence>
|
| 808 |
+
</boundary-data>
|
| 809 |
+
<p id="p-102" num="102">
|
| 810 |
+
<page-break num="32"/>
|
| 811 |
+
<confidence value="5">[</confidence>
|
| 812 |
+
0078<confidence value="5">1</confidence>
|
| 813 |
+
The EDC <part-num-ref name="EDC">610</part-num-ref>
|
| 814 |
+
may receive data for encoding, or receive already encoded data, via the interface <part-num-ref name="interface">630.</part-num-ref>
|
| 815 |
+
The interface <part-num-ref name="interface">630</part-num-ref>
|
| 816 |
+
may conform to a known standard (e.g., firewire, USB, etc.). The interface <part-num-ref name="interface">630</part-num-ref>
|
| 817 |
+
may also include more than one interface. For example, interface <part-num-ref name="may also include more than one interface. For example, interface">630</part-num-ref>
|
| 818 |
+
may include a firewire interface, a USB interface, etc. Data from the memory <part-num-ref name="memory">510</part-num-ref>
|
| 819 |
+
may also be output via the interface <part-num-ref name="interface">630.</part-num-ref>
|
| 820 |
+
</p>
|
| 821 |
+
<p id="p-103" num="103">
|
| 822 |
+
<confidence value="5">[</confidence>
|
| 823 |
+
0079<confidence value="5">]</confidence>
|
| 824 |
+
The presentation components <part-num-ref name="presentation components">620</part-num-ref>
|
| 825 |
+
may present data output from the memory, and/or decoded by the EDC <part-num-ref name="EDC">610,</part-num-ref>
|
| 826 |
+
to a user. For example, the presentation components <part-num-ref name="presentation components">620</part-num-ref>
|
| 827 |
+
may include a speaker jack for outputting audio data, a display screen for outputting video data, and/or etc. </p>
|
| 828 |
+
<p id="p-104" num="104">
|
| 829 |
+
<confidence value="5">1</confidence>
|
| 830 |
+
0080<confidence value="5">]</confidence>
|
| 831 |
+
Fig. 28 illustrates a still further embodiment of the present invention. As shown, the memory <part-num-ref name="memory">510</part-num-ref>
|
| 832 |
+
may be connected with a host system <part-num-ref name="host system">700.</part-num-ref>
|
| 833 |
+
The host system <part-num-ref name="host system">700</part-num-ref>
|
| 834 |
+
may be a processing system such as a personal computer, digital camera, etc. The host system <part-num-ref name="host system">700</part-num-ref>
|
| 835 |
+
may use the memory <part-num-ref name="memory">510</part-num-ref>
|
| 836 |
+
as a removable storage medium. As will be appreciated, the host system <part-num-ref name="host system">700</part-num-ref>
|
| 837 |
+
supplies the input signals for controlling operation of the memory <part-num-ref name="memory">510.</part-num-ref>
|
| 838 |
+
For example, in the case of the NAND flash memory of Figs. 21-22, the host system <part-num-ref name="host system">700</part-num-ref>
|
| 839 |
+
supplies the command CMD and address signals. In the example of the NOR flash memory of Figs. 23-24, the host system <part-num-ref name="host system">700</part-num-ref>
|
| 840 |
+
supplies the CMD, ADD, DQ and VPP signals. </p>
|
| 841 |
+
<boundary-data type="header">
|
| 842 |
+
<confidence value="88">32</confidence>
|
| 843 |
+
</boundary-data>
|
| 844 |
+
<boundary-data type="header">
|
| 845 |
+
<confidence value="6">'</confidence>
|
| 846 |
+
Atty.<confidence value="4">,</confidence>
|
| 847 |
+
Dkt. No.: 9862-000234/U<confidence value="5">S</confidence>
|
| 848 |
+
</boundary-data>
|
| 849 |
+
<p id="p-105" num="105">
|
| 850 |
+
<page-break num="33"/>
|
| 851 |
+
[0081<confidence value="5">]</confidence>
|
| 852 |
+
Fig. 29 illustrates an embodiment of the present invention in which the host system <part-num-ref name="host system">700</part-num-ref>
|
| 853 |
+
is connected to the card <part-num-ref name="card">530</part-num-ref>
|
| 854 |
+
of Fig. 26. In this embodiment, the host system <part-num-ref name="host system">700</part-num-ref>
|
| 855 |
+
applies control signals to the card <part-num-ref name="card">530</part-num-ref>
|
| 856 |
+
such that the memory controller <part-num-ref name="memory controller">520</part-num-ref>
|
| 857 |
+
controls operation of the memory <part-num-ref name="memory">510.</part-num-ref>
|
| 858 |
+
</p>
|
| 859 |
+
<p id="p-106" num="106">
|
| 860 |
+
<confidence value="5">[</confidence>
|
| 861 |
+
0082] Fig. 30 illustrates a further embodiment of the present invention. As shown, the memory <part-num-ref name="memory">510</part-num-ref>
|
| 862 |
+
may be connected to a central processing unit (CPU) <part-num-ref name="central processing unit (CPU)">810</part-num-ref>
|
| 863 |
+
within a computer system <part-num-ref name="computer system">800.</part-num-ref>
|
| 864 |
+
For example, the computer system <part-num-ref name="computer system">800</part-num-ref>
|
| 865 |
+
may be a personal computer, personal data assistant, etc. The memory <part-num-ref name="memory">510</part-num-ref>
|
| 866 |
+
may be directly connected with the CPU <part-num-ref name="CPU">810,</part-num-ref>
|
| 867 |
+
connected via bus, etc. It will be appreciated, that Fig. 30 does not illustrate the full complement of components that may be included within a computer system <part-num-ref name="computer system">800</part-num-ref>
|
| 868 |
+
for the sake of clarity. </p>
|
| 869 |
+
<p id="p-107" num="107">[0083<confidence value="4">]</confidence>
|
| 870 |
+
The invention being thus described, it will be obvious that the same may be varied in many ways. Such variations are not to be regarded as a departure from the invention, and all such mod<confidence value="8">i</confidence>
|
| 871 |
+
fications are intended to be included within the scope of the invention. </p>
|
| 872 |
+
<boundary-data type="header">
|
| 873 |
+
<confidence value="88">33</confidence>
|
| 874 |
+
</boundary-data>
|
| 875 |
+
</description>
|
| 876 |
+
</us-patent-application>
|
| 877 |
+
|
applicant/11850534.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>11850534</doc-number>
|
| 8 |
+
<date>2010-10-18</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 paragraph [0024] on page 7, lines 6-12 as follows:</p>
|
| 15 |
+
<p id="p-2" num="2">
|
| 16 |
+
<confidence value="5">[</confidence>
|
| 17 |
+
0024] One or more embodiments of the invention are implemented by a computer-implemented graphics program <part-num-ref name="computer-implemented graphics program">208,</part-num-ref>
|
| 18 |
+
wherein the graphics program <part-num-ref name="graphics program">208</part-num-ref>
|
| 19 |
+
is represented by a window displayed on the display device <part-num-ref name="display device">202.</part-num-ref>
|
| 20 |
+
Generally, the graphics program <part-num-ref name="graphics program">208</part-num-ref>
|
| 21 |
+
comprises logic and/or data embodied in or readable from a device, <confidence value="2">,</confidence>
|
| 22 |
+
.g., one or more fixed and/or removable data storage devices <part-num-ref name="device, ,.g., one or more fixed and/or removable data storage devices">204</part-num-ref>
|
| 23 |
+
connected directly or indirectly to the computer <part-num-ref name="computer">200,</part-num-ref>
|
| 24 |
+
one or more remote devices coupled to the computer <part-num-ref name="computer">200</part-num-ref>
|
| 25 |
+
via a data communications device, etc. </p>
|
| 26 |
+
<p id="p-3" num="3">-2- G&C 30566.418-US-<confidence value="55">O1</confidence>
|
| 27 |
+
</p>
|
| 28 |
+
</description>
|
| 29 |
+
</us-patent-application>
|
| 30 |
+
|
applicant/11851638.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
applicant/11862279.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
applicant/11865099.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="11865099.10-01-2007.F793RP9QPPOPPY4.SPEC.XML" pat:id="F793RP9QPPOPPY4"><pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001"><pat:ApplicationHeaderDetails><pat:ApplicationNumber>11865099</pat:ApplicationNumber></pat:ApplicationHeaderDetails><pat:PageTotalQuantity>20</pat:PageTotalQuantity><pat:ParagraphTotalQuantity>70</pat:ParagraphTotalQuantity></pat:DocumentHeaderDetails><pat:MailRoomDate>2007-10-01</pat:MailRoomDate><pat:DocumentCreateDateText>2014-09-13</pat:DocumentCreateDateText><pat:DocumentTitle>SPECIFICATION DOCUMENT</pat:DocumentTitle><pat:Specification><?PageStart number='1'?><pat:Heading pat:id="h-1"><pat:OCRConfidenceData pat:levelNumber='5'>I</pat:OCRConfidenceData>N THE UNITED STATES PATENT AND TRADEMARK OFFICE</pat:Heading><pat:Heading pat:id="h-2">APPLICATION FOR UNITED STATES PATENT</pat:Heading><pat:P pat:pNumber="1" pat:id="p-1"><pat:PatentImage pat:id='ID-00002' pat:imageContentCategory='Drawing' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025234.4.387.1279.2162.1379.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.333</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>5.917</com:WidthMeasure><com:ALTText>Drawing</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:Heading pat:id="h-3">FOR</pat:Heading><pat:P pat:pNumber="2" pat:id="p-2">Inventors: Sandra L. Kogan Mary E. Raven Anuphinh P. Wanderski <pat:PatentImage pat:id='ID-00003' pat:imageContentCategory='Chemistry' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025234.10.1238.2312.2141.2405.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.31</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>3.01</com:WidthMeasure><com:ALTText>Chemistry</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage>Date: October 1, 2007 <?PageStart number='2'?><pat:PatentImage pat:id='ID-00004' pat:imageContentCategory='Chemistry' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025235.1.1803.160.2174.252.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.307</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.237</com:WidthMeasure><com:ALTText>Chemistry</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="3" pat:id="p-3"><pat:BoundaryData><pat:HeaderText>CAM9-2007-0088US <pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData></pat:P><pat:Heading pat:id="h-4">FIELD OF THE INVENTION</pat:Heading><pat:P pat:pNumber="4" pat:id="p-4">The present invention relates generally to contact lists for computer based communication systems, and more specifically to a method and system for searching contact lists quickly - by group name, tags and/or metadata. </pat:P><pat:Heading pat:id="h-5">BACKGROUND OF THE INVENTION</pat:Heading><pat:P pat:pNumber="5" pat:id="p-5">With the increased popularity of instant messaging and other forms of synchronous and asynchronous on-line collaboration and communication, the contact lists (e.g. instant messaging buddy lists, electronic address books, etc.) provided by such systems to their users are becoming difficult to manage. Contact lists in existing systems can become very long. Contacts added to a contact list can be categorized in many different ways, often resulting in overlapping group memberships. All these factors ultimately make it difficult for users of existing system to quickly find the people they need to communicate with. </pat:P><pat:P pat:pNumber="6" pat:id="p-6">It would accordingly be desirable to have a new system for searching a contact list that enables a communication system user to quickly find relevant contacts for a communication. </pat:P><pat:Heading pat:id="h-6">SUMMARY OF THE INVENTION</pat:Heading><pat:P pat:pNumber="7" pat:id="p-7">To address the above described and other shortcomings of existing systems, a new method and system for searching contact lists quickly is disclosed. The disclosed system operates to provide searching of a contact list by user defined group names, tags (referred <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>2</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='3'?><pat:PatentImage pat:id='ID-00005' pat:imageContentCategory='Drawing' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025236.1.1803.160.2174.252.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.307</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.237</com:WidthMeasure><com:ALTText>Drawing</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="8" pat:id="p-8"><pat:BoundaryData><pat:HeaderText>CAM9-2007-0088US <pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>to herein as contact or group "attributes"), and/or system defined metadata regarding contacts, groups and/or attributes. </pat:P><pat:P pat:pNumber="9" pat:id="p-9">In the disclosed system, a user of a communication system is allowed to organize their contacts in their contact list within a number of contact groups. In addition, the user is allowed to associate attributes with contact groups and/or individual contacts. The visual display of contacts within the user's contact list user interface display may be configured to visually organize contacts into the groups they belong to, and/or to display the attributes associated with groups and/or contacts within the top level contact list display. Group and/or contact attributes may alternatively be accessed by selecting (e.g. clicking on) a group or contact. A quick search feature is provided that allows the contact list to be searched based on group name, attribute, and/or contact name, as well as based on group, contact and/or attribute metadata (e.g. date and time created or last modified, context information regarding creation or last modification, contact e-mail address, etc.). </pat:P><pat:P pat:pNumber="10" pat:id="p-10">Thus there is disclosed a new system for searching a contact list that enables a communication system user to quickly find relevant contacts for a communication. </pat:P><pat:Heading pat:id="h-7">BRIEF DESCRIPTION OF THE DRAWINGS</pat:Heading><pat:P pat:pNumber="11" pat:id="p-11">In order to facilitate a fuller understanding of the present invention, reference is now made to the appended drawings. These drawings should not be construed as limiting the present invention, but are intended to be exemplary only. </pat:P><pat:P pat:pNumber="12" pat:id="p-12">Fig. <pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData> is a block diagram showing an example of software and/or hardware components in an illustrative embodiment of the disclosed system; </pat:P><pat:P pat:pNumber="13" pat:id="p-13"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>3</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='4'?><pat:PatentImage pat:id='ID-00006' pat:imageContentCategory='Drawing' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025237.1.1803.160.2174.252.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.307</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.237</com:WidthMeasure><com:ALTText>Drawing</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="14" pat:id="p-14"><pat:BoundaryData><pat:HeaderText>CAM9-2007-0088US <pat:OCRConfidenceData pat:levelNumber='8'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>Fig. 2 is a simplified screen shot showing an example of a contact definition user interface display object generated in an illustrative embodiment; </pat:P><pat:P pat:pNumber="15" pat:id="p-15">Fig. 3 is a simplified screen shot showing an example of a group definition user interface display object generated in an illustrative embodiment; </pat:P><pat:P pat:pNumber="16" pat:id="p-16">Fig. 4 is a simplified screen shot showing an example of a contact list user interface display object generated in an illustrative embodiment; </pat:P><pat:P pat:pNumber="17" pat:id="p-17">Fig. 5 is a simplified screen shot showing the example of the contact list user interface display object of Fig. 4 with an example of a quick search user interface display object; </pat:P><pat:P pat:pNumber="18" pat:id="p-18">Fig. 6 is a simplified screen shot showing an example of a Web Browser user interface during operation of an illustrative embodiment; </pat:P><pat:P pat:pNumber="19" pat:id="p-19">Fig. 7 is a simplified screen shot showing the example of the Web Browser user interface of Fig. 6 following creation of a new contact group based on information in a loaded Web page; and Fig. 8 is a flow chart showing an example of steps performed in an illustrative embodiment. </pat:P><pat:Heading pat:id="h-8">DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS</pat:Heading><pat:P pat:pNumber="20" pat:id="p-20">Fig. 1 is a block diagram showing an example of software and/or hardware components in an illustrative embodiment of the disclosed system. As shown in Fig. 1, a <pat:PartName pat:idref='PN-00001'>Client System</pat:PartName> <pat:PartNumber pat:id='PN-00001'>12</pat:PartNumber> includes a <pat:PartName pat:idref='PN-00002'>Communication Application Client</pat:PartName> <pat:PartNumber pat:id='PN-00002'>14</pat:PartNumber> that provides a <pat:PartName pat:idref='PN-00003'>Communication Application User Interface</pat:PartName> <pat:PartNumber pat:id='PN-00003'>16</pat:PartNumber> to a local user User A 10. The <pat:PartName pat:idref='PN-00004'>Communication Application Client</pat:PartName> <pat:PartNumber pat:id='PN-00004'>14</pat:PartNumber> may, for example, be part of any specific type of <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>4</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='5'?><pat:PatentImage pat:id='ID-00007' pat:imageContentCategory='Drawing' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025238.1.1803.160.2174.252.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.307</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.237</com:WidthMeasure><com:ALTText>Drawing</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="21" pat:id="p-21"><pat:BoundaryData><pat:HeaderText>CAM9-2007-0088U<pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='8'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>synchronous communication system, such as an instant messaging system, and/or part of any specific type of asynchronous communication system, such as electronic mail ("e- mail"). Accordingly, the <pat:PartName pat:idref='PN-00005'>Communication Application Client</pat:PartName> <pat:PartNumber pat:id='PN-00005'>14</pat:PartNumber> may be a client portion of an instant messaging system, and/or a client portion of an e-mail system. </pat:P><pat:P pat:pNumber="22" pat:id="p-22">The <pat:PartName pat:idref='PN-00006'>Communication Application User Interface</pat:PartName> <pat:PartNumber pat:id='PN-00006'>16</pat:PartNumber> is generated by the <pat:PartName pat:idref='PN-00007'>Communication Application Client</pat:PartName> <pat:PartNumber pat:id='PN-00007'>14</pat:PartNumber> within the <pat:PartName pat:idref='PN-00008'>Graphical User Interface</pat:PartName> <pat:PartNumber pat:id='PN-00008'>17</pat:PartNumber> <pat:PartName pat:idref='PN-00009'>on Client System</pat:PartName> <pat:PartNumber pat:id='PN-00009'>12</pat:PartNumber>, and includes a <pat:PartName pat:idref='PN-00010'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00010'>18</pat:PartNumber>, a <pat:PartName pat:idref='PN-00011'>Contact Definition User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00011'>20</pat:PartNumber>, and a <pat:PartName pat:idref='PN-00012'>Group Definition User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00012'>22</pat:PartNumber>. The <pat:PartName pat:idref='PN-00013'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00013'>18</pat:PartNumber> is a list of other users with whom the User A 10 may wish to communicate, and each entry in the <pat:PartName pat:idref='PN-00014'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00014'>18</pat:PartNumber> represents one such other user. Each entry in the <pat:PartName pat:idref='PN-00015'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00015'>18</pat:PartNumber> enables the User A 10 to quickly initiate a communication with the user represented with that entry, for example by selecting the entry, for example by clicking on the entry. In an embodiment in which the <pat:PartName pat:idref='PN-00016'>Communication Application Client</pat:PartName> <pat:PartNumber pat:id='PN-00016'>14</pat:PartNumber> is part of an instant messaging system, then clicking on an entry in the <pat:PartName pat:idref='PN-00017'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00017'>18</pat:PartNumber> by User A 10 initiates an instant messaging session with the user represented by the entry (e.g. by bringing up an instant messaging session user interface object into which the User A 10 can enter an initial instant message to be immediately delivered to the other user). Similarly, in an embodiment in which the <pat:PartName pat:idref='PN-00018'>Communication Application Client</pat:PartName> <pat:PartNumber pat:id='PN-00018'>14</pat:PartNumber> is part of an e-mail system, clicking on an entry in the <pat:PartName pat:idref='PN-00019'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00019'>18</pat:PartNumber> initiates the sending of an e-mail message to the user represented by the entry (e.g. by bringing up a message composition user interface with the other user's e-mail address pre-loaded into the destination address field). </pat:P><pat:P pat:pNumber="23" pat:id="p-23"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>5</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='6'?><pat:PatentImage pat:id='ID-00008' pat:imageContentCategory='Chemistry' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025239.1.1803.160.2174.252.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.307</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.237</com:WidthMeasure><com:ALTText>Chemistry</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="24" pat:id="p-24"><pat:BoundaryData><pat:HeaderText>CAM9-2007-0088U<pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='8'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>The specific visual display layout of the <pat:PartName pat:idref='PN-00020'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00020'>18</pat:PartNumber>, as well as other operational parameters of the <pat:PartName pat:idref='PN-00021'>Communication Application Client</pat:PartName> <pat:PartNumber pat:id='PN-00021'>14</pat:PartNumber>, may be responsive to configuration values stored by User A 10 in the <pat:PartName pat:idref='PN-00022'>User Preferences</pat:PartName> <pat:PartNumber pat:id='PN-00022'>24</pat:PartNumber>. </pat:P><pat:P pat:pNumber="25" pat:id="p-25">The entries in the <pat:PartName pat:idref='PN-00023'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00023'>18</pat:PartNumber> may be expressly entered by User A 10, and/or automatically generated by the <pat:PartName pat:idref='PN-00024'>Communication Application Client</pat:PartName> <pat:PartNumber pat:id='PN-00024'>14</pat:PartNumber> based on previous communications made by User A 10. When User A 10 indicates that a new contact is to be added to the <pat:PartName pat:idref='PN-00025'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00025'>18</pat:PartNumber> (e.g. by clicking on a corresponding graphical button, dragging and dropping information such as a user name, screen name, and/or e-mail address over the <pat:PartName pat:idref='PN-00026'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00026'>18</pat:PartNumber>, etc.), the disclosed system operates to generate the <pat:PartName pat:idref='PN-00027'>Contact Definition User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00027'>20</pat:PartNumber>. The <pat:PartName pat:idref='PN-00028'>Contact Definition User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00028'>20</pat:PartNumber> enables User A 10 to enter information items into the disclosed system regarding the contact to be added (e.g. user name, screen name, e-mail address, associated groups, and/or user defined contact attributes), which are then stored locally by the <pat:PartName pat:idref='PN-00029'>Communication Application Client</pat:PartName> <pat:PartNumber pat:id='PN-00029'>14</pat:PartNumber> and/or communicated to the <pat:PartName pat:idref='PN-00030'>Communication Application Server Process</pat:PartName> <pat:PartNumber pat:id='PN-00030'>32</pat:PartNumber> located on the <pat:PartName pat:idref='PN-00031'>remote Server System</pat:PartName> <pat:PartNumber pat:id='PN-00031'>30</pat:PartNumber>. Such user defined information items regarding contacts in the <pat:PartName pat:idref='PN-00032'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00032'>18</pat:PartNumber> may accordingly be stored in a database or the like in the <pat:PartName pat:idref='PN-00033'>Client System</pat:PartName> <pat:PartNumber pat:id='PN-00033'>12</pat:PartNumber> <pat:PartName pat:idref='PN-00034'>and/or Server System</pat:PartName> <pat:PartNumber pat:id='PN-00034'>30</pat:PartNumber>, and are searchable to find relevant contacts in the <pat:PartName pat:idref='PN-00035'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00035'>18</pat:PartNumber> through a quick search interface available to User A within the <pat:PartName pat:idref='PN-00036'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00036'>18</pat:PartNumber>, and further described below. </pat:P><pat:P pat:pNumber="26" pat:id="p-26">When User A 10 indicates that a new group is to be defined in the <pat:PartName pat:idref='PN-00037'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00037'>18</pat:PartNumber> (e.g. by clicking on a corresponding graphical button, dragging and dropping information other than a user name, screen name, and/or e-mail address over the <pat:PartName pat:idref='PN-00038'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00038'>18</pat:PartNumber>, <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>6</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='7'?><pat:PatentImage pat:id='ID-00009' pat:imageContentCategory='Graph' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025240.1.1803.160.2174.252.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.307</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.237</com:WidthMeasure><com:ALTText>Graph</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="27" pat:id="p-27"><pat:BoundaryData><pat:HeaderText>CAM9-2007-0088U<pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='8'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>etc.), the disclosed system operates to generate the <pat:PartName pat:idref='PN-00039'>Group Definition User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00039'>22</pat:PartNumber>. The <pat:PartName pat:idref='PN-00040'>Group Definition User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00040'>22</pat:PartNumber> enables User A 10 to enter information items into the disclosed system regarding a group to be added (e.g. group name, user names, screen names, e-mail addresses, etc. of contacts to be included in the group, and/or user defined attributes of the group), which are stored locally by the <pat:PartName pat:idref='PN-00041'>Communication Application Client</pat:PartName> <pat:PartNumber pat:id='PN-00041'>14</pat:PartNumber> and/or communicated to the <pat:PartName pat:idref='PN-00042'>Communication Application Server Process</pat:PartName> <pat:PartNumber pat:id='PN-00042'>32</pat:PartNumber> located on the <pat:PartName pat:idref='PN-00043'>remote Server System</pat:PartName> <pat:PartNumber pat:id='PN-00043'>30</pat:PartNumber>. Such user defined information items regarding groups in the <pat:PartName pat:idref='PN-00044'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00044'>18</pat:PartNumber> may accordingly be stored in a database or the like in the <pat:PartName pat:idref='PN-00045'>Client System</pat:PartName> <pat:PartNumber pat:id='PN-00045'>12</pat:PartNumber> <pat:PartName pat:idref='PN-00046'>and/or Server System</pat:PartName> <pat:PartNumber pat:id='PN-00046'>30</pat:PartNumber>, and are searchable to find relevant groups of contacts in the <pat:PartName pat:idref='PN-00047'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00047'>18</pat:PartNumber> through a quick search interface available to User A within the <pat:PartName pat:idref='PN-00048'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00048'>18</pat:PartNumber>, and further described below. </pat:P><pat:P pat:pNumber="28" pat:id="p-28">The <pat:PartName pat:idref='PN-00049'>Client System</pat:PartName> <pat:PartNumber pat:id='PN-00049'>12</pat:PartNumber> of Fig. 1 may be any specific type of a computer system or intelligent electronic device, such as a desktop, laptop, or palmtop computer system, or a personal digital assistant, cell phone, or other electronic device. The <pat:PartName pat:idref='PN-00050'>Client System</pat:PartName> <pat:PartNumber pat:id='PN-00050'>12</pat:PartNumber> of Fig. 1 may include or control a display device capable of displaying a graphical user interface (e.g. the <pat:PartName pat:idref='PN-00051'>Graphical User Interface</pat:PartName> <pat:PartNumber pat:id='PN-00051'>16</pat:PartNumber>) to a local user (e.g. User A 10), such as a liquid crystal display (LCD), cathode ray tube (CRT), interferometric modulator display (IMOD), light emitting diode (LED), or the like. </pat:P><pat:P pat:pNumber="29" pat:id="p-29">Those skilled in the art will recognize that the <pat:PartName pat:idref='PN-00052'>Communication Application Client</pat:PartName> <pat:PartNumber pat:id='PN-00052'>14</pat:PartNumber> and <pat:PartName pat:idref='PN-00053'>Server Process</pat:PartName> <pat:PartNumber pat:id='PN-00053'>32</pat:PartNumber> of Fig. 1 may be embodied using software or firmware, such as computer application program code, operating system program code, middleware, and/or wholly or partly using digital hardware components, such as application specific <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>7</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='8'?><pat:PatentImage pat:id='ID-00010' pat:imageContentCategory='Graph' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025241.1.1803.160.2174.252.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.307</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.237</com:WidthMeasure><com:ALTText>Graph</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="30" pat:id="p-30"><pat:BoundaryData><pat:HeaderText>CAM9-2007-0088U<pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='8'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and the like, and/or combinations of hardware and/or software or firmware. Those skilled in the art will further recognize that the <pat:PartName pat:idref='PN-00054'>Client System</pat:PartName> <pat:PartNumber pat:id='PN-00054'>12</pat:PartNumber> and <pat:PartName pat:idref='PN-00055'>Server System</pat:PartName> <pat:PartNumber pat:id='PN-00055'>30</pat:PartNumber> of Fig. 1 may include one or more processors, and program storage, such as memory, for storing program code executable on such processors, as well as input/output devices and/or interfaces. In the example of Fig. 1, the <pat:PartName pat:idref='PN-00056'>Client System</pat:PartName> <pat:PartNumber pat:id='PN-00056'>12</pat:PartNumber> and <pat:PartName pat:idref='PN-00057'>Server System</pat:PartName> <pat:PartNumber pat:id='PN-00057'>30</pat:PartNumber> are interconnected through a computer or <pat:PartName pat:idref='PN-00058'>data Communication Network</pat:PartName> <pat:PartNumber pat:id='PN-00058'>28</pat:PartNumber> (e.g. the Internet, a Local Area Network, etc.) through one or more of such input/output devices or interfaces, and through which may further be provided communication to a number of other client systems and/or other server systems. </pat:P><pat:P pat:pNumber="31" pat:id="p-31">Fig. 2 is a simplified screen shot showing an example of a <pat:PartName pat:idref='PN-00059'>Contact Definition User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00059'>40</pat:PartNumber> generated in an illustrative embodiment. As shown in Fig. 2, the <pat:PartName pat:idref='PN-00060'>Contact Definition User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00060'>40</pat:PartNumber> enables a local user (e.g. User A 10) to define a new contact or modify the definition of an existing contact for a contact list. To this end, the <pat:PartName pat:idref='PN-00061'>Contact Definition User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00061'>40</pat:PartNumber> includes a number of user interface display objects that allow a user to enter or modify information (e.g. contact name, addresses/screen names, associated groups, attributes, etc.) relating to a newly defined or previously existing contact. For example, the <pat:PartName pat:idref='PN-00062'>Contact Definition User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00062'>40</pat:PartNumber> includes a <pat:PartName pat:idref='PN-00063'>Contact Name field</pat:PartName> <pat:PartNumber pat:id='PN-00063'>42</pat:PartNumber> for entry of a user name, nickname, etc., to be used to quickly refer to the contact, an <pat:PartName pat:idref='PN-00064'>Addresses/Screen Names field</pat:PartName> <pat:PartNumber pat:id='PN-00064'>43</pat:PartNumber> for entry of e-mail addresses and/or screen names to be associated with the contact, <pat:PartName pat:idref='PN-00065'>Contact Groups field</pat:PartName> <pat:PartNumber pat:id='PN-00065'>44</pat:PartNumber> for entry of names of groups that the contact is to be contained within, and a <pat:PartName pat:idref='PN-00066'>Contact Attributes field</pat:PartName> <pat:PartNumber pat:id='PN-00066'>46</pat:PartNumber> for entry of one or <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>8</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='9'?><pat:PatentImage pat:id='ID-00011' pat:imageContentCategory='Table' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025242.1.1803.160.2174.252.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.307</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.237</com:WidthMeasure><com:ALTText>Table</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="32" pat:id="p-32"><pat:BoundaryData><pat:HeaderText>CAM9-2007-0088US <pat:OCRConfidenceData pat:levelNumber='8'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>more text attributes (e.g. "tags") that are to be associated with the contact. The attributes associated with a contact may be any specific type of content or pointer, such as text, links (e.g. Uniform Resource Locators (URLs)), etc. As described further below, the contact can subsequently be retrieved based on a match between a quick search query and at least a portion of one or more attributes associated with it. </pat:P><pat:P pat:pNumber="33" pat:id="p-33">The new or modified contact definition is stored when the user clicks on the <pat:PartName pat:idref='PN-00067'>OK button</pat:PartName> <pat:PartNumber pat:id='PN-00067'>48</pat:PartNumber>, or cancelled when the user clicks on the <pat:PartName pat:idref='PN-00068'>CANCEL button</pat:PartName> <pat:PartNumber pat:id='PN-00068'>50</pat:PartNumber>. </pat:P><pat:P pat:pNumber="34" pat:id="p-34">Fig. 3 is a simplified screen shot showing an example of a <pat:PartName pat:idref='PN-00069'>Group Definition User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00069'>60</pat:PartNumber> generated in an illustrative embodiment. As shown in Fig. 3, the <pat:PartName pat:idref='PN-00070'>Group Definition User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00070'>60</pat:PartNumber> enables a local user (e.g. User A 10) to define a new group or modify an existing group for a contact list. To this end, the <pat:PartName pat:idref='PN-00071'>Group Definition User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00071'>60</pat:PartNumber> includes a number of user interface display objects that allow a user to enter or modify information (e.g. group name, contacts within the group, group attributes, etc.) relating to a newly defined or previously existing group. For example, the <pat:PartName pat:idref='PN-00072'>Group Definition User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00072'>60</pat:PartNumber> includes a <pat:PartName pat:idref='PN-00073'>Group Name field</pat:PartName> <pat:PartNumber pat:id='PN-00073'>62</pat:PartNumber> for entry of a group name to be used to quickly refer to the group, a <pat:PartName pat:idref='PN-00074'>Contacts in Group</pat:PartName> <pat:PartNumber pat:id='PN-00074'>64</pat:PartNumber> for entry of contacts (e.g. by way of contact name, e-mail addresses and/or screen names, etc.) to be included in the group, and a <pat:PartName pat:idref='PN-00075'>Group Attributes field</pat:PartName> <pat:PartNumber pat:id='PN-00075'>66</pat:PartNumber> for entry of one or more text attributes (e.g. "tags") that are to be associated with the group. The attributes associated with a group may be any specific type of content or pointer, such as text, links (e.g. Uniform Resource Locators (URLs)), etc. As described further below, the group can subsequently be retrieved based <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>9</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='10'?><pat:PatentImage pat:id='ID-00012' pat:imageContentCategory='Table' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025243.1.1803.160.2174.252.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.307</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.237</com:WidthMeasure><com:ALTText>Table</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="35" pat:id="p-35"><pat:BoundaryData><pat:HeaderText>CAM9-2007-0088U<pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='8'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>on a match between a quick search query and at least a portion of one or more attributes associated with it. </pat:P><pat:P pat:pNumber="36" pat:id="p-36">The new or modified group definition is stored when the user clicks on the <pat:PartName pat:idref='PN-00076'>OK button</pat:PartName> <pat:PartNumber pat:id='PN-00076'>68</pat:PartNumber>, or cancelled when the user clicks on the <pat:PartName pat:idref='PN-00077'>CANCEL button</pat:PartName> <pat:PartNumber pat:id='PN-00077'>70</pat:PartNumber>. </pat:P><pat:P pat:pNumber="37" pat:id="p-37">Groups and attributes may, for example, be used to refer to the different roles that contacts have in their jobs. This use of the disclosed contact attributes may help address the problem that people may work in many different capacities in different groups (sometimes making it difficult to find the right contact within the contact list), and also enables searching by contact role. For example, a given contact may serve as a project manager for one team, designer on another team, and later on become a director of a company. If such a person appears within different groups from the contact list (e.g. within groups consisting of Team A, Product X, and Company ABC), a user could make sure it's the same person across all the groups by defining and/or searching role attributes associated with that person to obtain search results indicating that the person was tagged with different roles within each group, i.e. showing the contact with a project manager attribute within the group Team A, with a designer attribute within the group Product X, and now with a Director of Company attribute within the group ABC. </pat:P><pat:P pat:pNumber="38" pat:id="p-38">Fig. 4 is a simplified screen shot showing an example of a <pat:PartName pat:idref='PN-00078'>Contact List User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00078'>80</pat:PartNumber> generated in an illustrative embodiment. In the example of Fig. 4, the <pat:PartName pat:idref='PN-00079'>Contact List User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00079'>80</pat:PartNumber> is shown including a <pat:PartName pat:idref='PN-00080'>Quick Search Button</pat:PartName> <pat:PartNumber pat:id='PN-00080'>82</pat:PartNumber>, an <pat:PartName pat:idref='PN-00081'>Add Contact Button</pat:PartName> <pat:PartNumber pat:id='PN-00081'>83</pat:PartNumber>, an <pat:PartName pat:idref='PN-00082'>Add Group Button</pat:PartName> <pat:PartNumber pat:id='PN-00082'>85</pat:PartNumber>, a <pat:PartName pat:idref='PN-00083'>Contact Column</pat:PartName> <pat:PartNumber pat:id='PN-00083'>84</pat:PartNumber>, an <pat:PartName pat:idref='PN-00084'>Address/Screen Name Column</pat:PartName> <pat:PartNumber pat:id='PN-00084'>86</pat:PartNumber>, and an <pat:PartName pat:idref='PN-00085'>Attributes Column</pat:PartName> <pat:PartNumber pat:id='PN-00085'>88</pat:PartNumber>. When clicked on, the <pat:PartName pat:idref='PN-00086'>Quick Search Button</pat:PartName> <pat:PartNumber pat:id='PN-00086'>82</pat:PartNumber> provides a pull down menu of contact searches, <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>10</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='11'?><pat:PatentImage pat:id='ID-00013' pat:imageContentCategory='Table' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025244.1.1803.160.2174.252.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.307</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.237</com:WidthMeasure><com:ALTText>Table</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="39" pat:id="p-39"><pat:BoundaryData><pat:HeaderText>CAM9-2007-0088U<pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='8'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>as further shown in Fig. 5. The <pat:PartName pat:idref='PN-00087'>Quick Search Button</pat:PartName> <pat:PartNumber pat:id='PN-00087'>82</pat:PartNumber> thus provides a user interface to quick searching across the contacts in the contact list by contact name, address/screen name, group name, contact attribute, and/or group attribute. </pat:P><pat:P pat:pNumber="40" pat:id="p-40">The <pat:PartName pat:idref='PN-00088'>Add Contact Button</pat:PartName> <pat:PartNumber pat:id='PN-00088'>83</pat:PartNumber>, when clicked on, causes the disclosed system to display a contact definition user interface display object (e.g. <pat:PartName pat:idref='PN-00089'>Contact Definition User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00089'>40</pat:PartNumber> of Fig. 2). The <pat:PartName pat:idref='PN-00090'>Add Group Button</pat:PartName> <pat:PartNumber pat:id='PN-00090'>85</pat:PartNumber>, when clicked on, causes the disclosed system to display a group definition user interface display object (e.g. Group Definition User Interface Display Object of Fig. 3). Those skilled in the art will recognize that the <pat:PartName pat:idref='PN-00091'>use of buttons such as</pat:PartName> <pat:PartNumber pat:id='PN-00091'>83</pat:PartNumber> and 85 shown in Fig. 4 is just one possible way of triggering the display of contact definition and/or group definition user interface objects, and that any other specific user interface mechanism may be used in the alternative or additionally for this purpose as appropriate for a given embodiment. </pat:P><pat:P pat:pNumber="41" pat:id="p-41">Further in the example of Fig. 4, a <pat:PartName pat:idref='PN-00092'>Contact Column</pat:PartName> <pat:PartNumber pat:id='PN-00092'>84</pat:PartNumber> displays the names (e.g. user names or nicknames) of all contacts in the contact list. The <pat:PartName pat:idref='PN-00093'>names in Contacts Column</pat:PartName> <pat:PartNumber pat:id='PN-00093'>84</pat:PartNumber> are shown organized by groups, <pat:PartName pat:idref='PN-00094'>such that Contact</pat:PartName> <pat:PartNumber pat:id='PN-00094'>1</pat:PartNumber>, <pat:PartName pat:idref='PN-00095'>Contact</pat:PartName> <pat:PartNumber pat:id='PN-00095'>2</pat:PartNumber>, and <pat:PartName pat:idref='PN-00096'>Contact</pat:PartName> <pat:PartNumber pat:id='PN-00096'>3</pat:PartNumber> are displayed under Group A, and <pat:PartName pat:idref='PN-00097'>Contact</pat:PartName> <pat:PartNumber pat:id='PN-00097'>4</pat:PartNumber>, <pat:PartName pat:idref='PN-00098'>Contact</pat:PartName> <pat:PartNumber pat:id='PN-00098'>5</pat:PartNumber>, and <pat:PartName pat:idref='PN-00099'>Contact</pat:PartName> <pat:PartNumber pat:id='PN-00099'>6</pat:PartNumber> are displayed under Group B. In one embodiment of the disclosed system, when the user clicks on a name in the <pat:PartName pat:idref='PN-00100'>Contact Column</pat:PartName> <pat:PartNumber pat:id='PN-00100'>84</pat:PartNumber>, a communication (e.g. instant messaging session or e- mail message) is initiated with that contact. </pat:P><pat:P pat:pNumber="42" pat:id="p-42">The <pat:PartName pat:idref='PN-00101'>Address/Screen Name Column</pat:PartName> <pat:PartNumber pat:id='PN-00101'>86</pat:PartNumber> displays e-mail addresses or <pat:PartName pat:idref='PN-00102'>screen names for each contact named in column</pat:PartName> <pat:PartNumber pat:id='PN-00102'>84</pat:PartNumber>. For example, in an embodiment based on an instant messaging system, <pat:PartName pat:idref='PN-00103'>column</pat:PartName> <pat:PartNumber pat:id='PN-00103'>86</pat:PartNumber> would display the screen name(s) associated with <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>11</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='12'?><pat:PatentImage pat:id='ID-00014' pat:imageContentCategory='Table' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025245.1.1803.160.2174.252.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.307</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.237</com:WidthMeasure><com:ALTText>Table</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="43" pat:id="p-43"><pat:BoundaryData><pat:HeaderText>CAM9-2007-0088US <pat:OCRConfidenceData pat:levelNumber='8'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>each contact. Alternatively, in an embodiment based on an e-mail system, <pat:PartName pat:idref='PN-00104'>column</pat:PartName> <pat:PartNumber pat:id='PN-00104'>86</pat:PartNumber> would display the e-mail address(es) associated with each contact. </pat:P><pat:P pat:pNumber="44" pat:id="p-44">The <pat:PartName pat:idref='PN-00105'>Attributes Column</pat:PartName> <pat:PartNumber pat:id='PN-00105'>88</pat:PartNumber> displays the user defined attributes (i.e. tags) associated with each contact in the contact list. Accordingly, any text, pointers, images, etc. that a user has associated with a given contact in the contact list will be displayed in the <pat:PartName pat:idref='PN-00106'>Attributes Column</pat:PartName> <pat:PartNumber pat:id='PN-00106'>88</pat:PartNumber>. </pat:P><pat:P pat:pNumber="45" pat:id="p-45">The specific format of a contact list displayed by an embodiment of the disclosed system may be user configurable, e.g. based on the user configuration settings stored in the User Preferences shown in Fig. 1. Accordingly, user configuration settings may determine the specific columns of information displayed for each contact in the contact list. Moreover, whether contacts are displayed within their associated groups may be determined based on such a configuration setting. Alternatively, a configuration setting may indicate that the order in which contacts are displayed in the <pat:PartName pat:idref='PN-00107'>Contact List User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00107'>80</pat:PartNumber> based on some other factor. For example, a user configuration setting may be provided that causes contacts to be listed alphabetically, or grouped together by associated attributes, or in some other manner that may be independent of the group associations of the contacts. A configuration setting may alternatively indicate that the contacts in the <pat:PartName pat:idref='PN-00108'>Contact List User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00108'>80</pat:PartNumber> are to be displayed within their associated groups, but that the groups are to be displayed contiguously adjacent to other groups associated with the same attributes. In another possible configuration, only the group names would be initially displayed in the <pat:PartName pat:idref='PN-00109'>Contact List User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00109'>80</pat:PartNumber>, and the user would have to click on a group to see the contacts contained within it. </pat:P><pat:P pat:pNumber="46" pat:id="p-46"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>12</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='13'?><pat:PatentImage pat:id='ID-00015' pat:imageContentCategory='Chemistry' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025246.1.1803.160.2174.252.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.307</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.237</com:WidthMeasure><com:ALTText>Chemistry</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="47" pat:id="p-47"><pat:BoundaryData><pat:HeaderText>CAM9-2007-0088U<pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='8'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>Fig. 5 is a simplified screen shot showing the example of the Contact List User Interface Display Object of Fig. 4 with an example of a quick search user interface display object displayed in response to the user clicking on the <pat:PartName pat:idref='PN-00110'>Quick Search Button</pat:PartName> <pat:PartNumber pat:id='PN-00110'>82</pat:PartNumber> of Fig. 4: <pat:PartName pat:idref='PN-00111'>Quick Search Pull-Down Menu</pat:PartName> <pat:PartNumber pat:id='PN-00111'>100</pat:PartNumber>. <pat:PartName pat:idref='PN-00112'>Quick Search Pull-Down Menu</pat:PartName> <pat:PartNumber pat:id='PN-00112'>100</pat:PartNumber> includes a number of selectable search options, shown in the example of Fig. 5 as including a <pat:PartName pat:idref='PN-00113'>Search by Contact Name option</pat:PartName> <pat:PartNumber pat:id='PN-00113'>102</pat:PartNumber>, a <pat:PartName pat:idref='PN-00114'>Search by Group Name option</pat:PartName> <pat:PartNumber pat:id='PN-00114'>104</pat:PartNumber>, a <pat:PartName pat:idref='PN-00115'>Search Contacts by Attribute option</pat:PartName> <pat:PartNumber pat:id='PN-00115'>106</pat:PartNumber>, a <pat:PartName pat:idref='PN-00116'>Search Groups by Attribute option</pat:PartName> <pat:PartNumber pat:id='PN-00116'>108</pat:PartNumber>, and a Search Contacts and <pat:PartName pat:idref='PN-00117'>Groups by Attributes option</pat:PartName> <pat:PartNumber pat:id='PN-00117'>110</pat:PartNumber>. In response to a user selecting (e.g. clicking on) the <pat:PartName pat:idref='PN-00118'>Search by Contact Name option</pat:PartName> <pat:PartNumber pat:id='PN-00118'>102</pat:PartNumber>, the disclosed system displays a user interface object (e.g. pop-up window or the like) that enables the user to enter a search query (e.g. text) to be matched against the names of contacts in the contacts list in order to generate a result set of contacts matching the search query. The contacts having names matching the search query are then displayed as a current contact list (e.g. within the <pat:PartName pat:idref='PN-00119'>Contact List User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00119'>80</pat:PartNumber>), or in a separate results window or the like. </pat:P><pat:P pat:pNumber="48" pat:id="p-48">Similarly, in response to a user selecting (e.g. clicking on) the <pat:PartName pat:idref='PN-00120'>Search by Group Name option</pat:PartName> <pat:PartNumber pat:id='PN-00120'>104</pat:PartNumber>, the disclosed system displays a user interface object (e.g. pop-up window or the like) that enables the user to enter a search query (e.g. text) to be matched against the names of groups in the contacts list in order to generate a result set of groups matching the search query. The groups having names matching the search query are then displayed as a current contact list (e.g. within the <pat:PartName pat:idref='PN-00121'>Contact List User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00121'>80</pat:PartNumber>), or in a separate results window or the like. </pat:P><pat:P pat:pNumber="49" pat:id="p-49"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>13</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='14'?><pat:PatentImage pat:id='ID-00016' pat:imageContentCategory='Table' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025247.1.1803.160.2174.252.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.307</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.237</com:WidthMeasure><com:ALTText>Table</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="50" pat:id="p-50"><pat:BoundaryData><pat:HeaderText>CAM9-2007-0088US <pat:OCRConfidenceData pat:levelNumber='8'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>In response to a user selecting (e.g. clicking on) the <pat:PartName pat:idref='PN-00122'>Search Contacts by Attribute option</pat:PartName> <pat:PartNumber pat:id='PN-00122'>106</pat:PartNumber>, the disclosed system displays a user interface object (e.g. pop-up window or the like) that enables the user to enter a search query (e.g. text) to be matched against the attributes associated with contacts in the contacts list in order to generate a result set of contacts having attributes matching the search query. The contacts having associated attributes matching the search query are then displayed as a current contact list (e.g. within the <pat:PartName pat:idref='PN-00123'>Contact List User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00123'>80</pat:PartNumber>), or in a separate results window or the like. </pat:P><pat:P pat:pNumber="51" pat:id="p-51">In response to a user selecting (e.g. clicking on) the <pat:PartName pat:idref='PN-00124'>Search Groups by Attribute option</pat:PartName> <pat:PartNumber pat:id='PN-00124'>108</pat:PartNumber>, the disclosed system displays a user interface object (e.g. pop-up window or the like) that enables the user to enter a search query (e.g. text) to be matched against the attributes associated with groups in the contacts list in order to generate a result set of groups having attributes matching the search query. The groups having associated attributes matching the search query are then displayed as a current contact list (e.g. within the <pat:PartName pat:idref='PN-00125'>Contact List User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00125'>80</pat:PartNumber>), or in a separate results window or the like. </pat:P><pat:P pat:pNumber="52" pat:id="p-52">In response to a user selecting (e.g. clicking on) the Search Contacts and <pat:PartName pat:idref='PN-00126'>Groups by Attribute option</pat:PartName> <pat:PartNumber pat:id='PN-00126'>108</pat:PartNumber>, the disclosed system displays a user interface object (e.g. pop-up window or the like) that enables the user to enter a search query (e.g. text) to be matched against the attributes associated with contacts and groups in the contacts list in order to generate a result set of contacts and groups having attributes matching the search query. The contacts and groups having associated attributes matching the search query are then <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>14</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='15'?><pat:PatentImage pat:id='ID-00017' pat:imageContentCategory='Table' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025248.1.1803.160.2174.252.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.307</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.237</com:WidthMeasure><com:ALTText>Table</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="53" pat:id="p-53"><pat:BoundaryData><pat:HeaderText>CAM9-2007-0088US <pat:OCRConfidenceData pat:levelNumber='8'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>displayed as a current contact list (e.g. within the <pat:PartName pat:idref='PN-00127'>Contact List User Interface Display Object</pat:PartName> <pat:PartNumber pat:id='PN-00127'>80</pat:PartNumber>), or in a separate results window or the like. </pat:P><pat:P pat:pNumber="54" pat:id="p-54">Fig. 6 is a simplified screen shot showing an example of a <pat:PartName pat:idref='PN-00128'>Web Browser User Interface</pat:PartName> <pat:PartNumber pat:id='PN-00128'>120</pat:PartNumber> during operation of an illustrative embodiment of the disclosed system. As shown in Fig. 6, a <pat:PartName pat:idref='PN-00129'>Currently Loaded Web Page Display Area</pat:PartName> <pat:PartNumber pat:id='PN-00129'>122</pat:PartNumber> displays a currently loaded Web page that is an article including an <pat:PartName pat:idref='PN-00130'>title shown as Article Title</pat:PartName> <pat:PartNumber pat:id='PN-00130'>126</pat:PartNumber>, names of the article authors that are links to their e-mail addresses, <pat:PartName pat:idref='PN-00131'>shown as Article Authors</pat:PartName> <pat:PartNumber pat:id='PN-00131'>128</pat:PartNumber>, and an <pat:PartName pat:idref='PN-00132'>Article Body</pat:PartName> <pat:PartNumber pat:id='PN-00132'>132</pat:PartNumber>. If while reading the article shown in the <pat:PartName pat:idref='PN-00133'>Currently Loaded Web Page Display Area</pat:PartName> <pat:PartNumber pat:id='PN-00133'>122</pat:PartNumber>, the user determines that they are interested in following up on the contents of the article with the article authors, but cannot at the moment, or if they have questions for the authors or questions about the article in general, they may wish to add the <pat:PartName pat:idref='PN-00134'>Article Authors</pat:PartName> <pat:PartNumber pat:id='PN-00134'>128</pat:PartNumber> to the <pat:PartName pat:idref='PN-00135'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00135'>134</pat:PartNumber> shown in the <pat:PartName pat:idref='PN-00136'>Contact List Portlet</pat:PartName> <pat:PartNumber pat:id='PN-00136'>124</pat:PartNumber>. However, the user may also know that if they simply add the <pat:PartName pat:idref='PN-00137'>names of Article Authors</pat:PartName> <pat:PartNumber pat:id='PN-00137'>128</pat:PartNumber> and e-mail addresses to the <pat:PartName pat:idref='PN-00138'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00138'>134</pat:PartNumber>, they will later likely not remember why they were put there. Accordingly, the user can add the article authors to the <pat:PartName pat:idref='PN-00139'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00139'>134</pat:PartNumber> in such a way that the group membership and/or associated attributes for the authors will remind the user of their relevance. For example, the user could add the article authors to the <pat:PartName pat:idref='PN-00140'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00140'>134</pat:PartNumber> and associate attributes with them including at least a portion of the <pat:PartName pat:idref='PN-00141'>Article Title</pat:PartName> <pat:PartNumber pat:id='PN-00141'>126</pat:PartNumber>, and/or a text note describing the questions that the user wants to ask the authors. In addition, the user can associate a link to the article (e.g. from a Web Browser location bar or the like) as a contact attribute for each of the article authors in their corresponding entries in the <pat:PartName pat:idref='PN-00142'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00142'>134</pat:PartNumber>. Alternatively, the user can define a group to contain the article authors in the <pat:PartName pat:idref='PN-00143'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00143'>134</pat:PartNumber>, and associate the <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>15</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='16'?><pat:PatentImage pat:id='ID-00018' pat:imageContentCategory='Table' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025249.1.1803.160.2174.252.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.307</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.237</com:WidthMeasure><com:ALTText>Table</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="55" pat:id="p-55"><pat:BoundaryData><pat:HeaderText>CAM9-2007-0088US <pat:OCRConfidenceData pat:levelNumber='8'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>same attributes listed above with the group, so that the group attributes will remind the user of the context in which the article authors were added to the <pat:PartName pat:idref='PN-00144'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00144'>134</pat:PartNumber>. Moreover, in the case where a new group is defined to contain the article authors, the name of the article itself could be used as the name of the group. </pat:P><pat:P pat:pNumber="56" pat:id="p-56">In one embodiment of the disclosed system, as illustrated in Fig. 6, dragging and dropping the names of the article authors, the e-mail addresses of the article authors, over the <pat:PartName pat:idref='PN-00145'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00145'>134</pat:PartNumber> causes contact definition user interface display objects to be displayed that are pre-loaded with the article author names and/or e-mail addresses of the authors. Alternatively, dragging and dropping the names of the article authors, the e-mail addresses of the article authors, over the <pat:PartName pat:idref='PN-00146'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00146'>134</pat:PartNumber> causes the authors to be automatically added to the <pat:PartName pat:idref='PN-00147'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00147'>134</pat:PartNumber>. In the event that there is a conflict between the information dragged into the <pat:PartName pat:idref='PN-00148'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00148'>134</pat:PartNumber> and an existing entry, the user may be presented with user interface options allowing the user to either cancel the addition to the contact list, or to override the existing entry with the new contact information. </pat:P><pat:P pat:pNumber="57" pat:id="p-57">Similarly, in one embodiment of the disclosed system, dragging and dropping the <pat:PartName pat:idref='PN-00149'>Article Title</pat:PartName> <pat:PartNumber pat:id='PN-00149'>126</pat:PartNumber> over the <pat:PartName pat:idref='PN-00150'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00150'>134</pat:PartNumber> causes a group definition user interface display object to be displayed that is pre-loaded with the article title as the group name. Alternatively, dragging and dropping the article title over the <pat:PartName pat:idref='PN-00151'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00151'>134</pat:PartNumber> causes the article name to be automatically added as a group to the <pat:PartName pat:idref='PN-00152'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00152'>134</pat:PartNumber>. </pat:P><pat:P pat:pNumber="58" pat:id="p-58">Fig. 7 is a simplified screen shot showing the example of the Web Browser user interface of Fig. 6 following creation of a new contact group based on information in the loaded Web page shown in Fig. 6. As shown in Fig. 7, a <pat:PartName pat:idref='PN-00153'>new group</pat:PartName> <pat:PartNumber pat:id='PN-00153'>138</pat:PartNumber> that has a name <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>16</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='17'?><pat:PatentImage pat:id='ID-00019' pat:imageContentCategory='Table' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025250.1.1803.160.2174.252.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.307</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.237</com:WidthMeasure><com:ALTText>Table</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="59" pat:id="p-59"><pat:BoundaryData><pat:HeaderText>CAM9-2007-0088US <pat:OCRConfidenceData pat:levelNumber='8'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>matching at least a portion of the article title has been created in the <pat:PartName pat:idref='PN-00154'>Contact List</pat:PartName> <pat:PartNumber pat:id='PN-00154'>134</pat:PartNumber>, and the new group contains the authors of the article as contacts. </pat:P><pat:P pat:pNumber="60" pat:id="p-60">Fig. 8 is a flow chart showing an example of steps performed in an illustrative embodiment. As shown in Fig. 8, <pat:PartName pat:idref='PN-00155'>at step</pat:PartName> <pat:PartNumber pat:id='PN-00155'>150</pat:PartNumber>, the disclosed system displays user interface display objects for defining contacts, groups, and attributes associated with those contact and/or groups within the contact list. <pat:PartName pat:idref='PN-00156'>At step</pat:PartName> <pat:PartNumber pat:id='PN-00156'>152</pat:PartNumber>, the disclosed system displays a contact list with quick search options enabling the user to search the contact list based on contact name, group name, and/or based on user defined attributes associated with contacts and/or groups. <pat:PartName pat:idref='PN-00157'>At step</pat:PartName> <pat:PartNumber pat:id='PN-00157'>154</pat:PartNumber>, the disclosed system receives a search query from the user for searching the contact list, e.g. via a field in a pop-up window or the like. The <pat:PartName pat:idref='PN-00158'>search query received at step</pat:PartName> <pat:PartNumber pat:id='PN-00158'>154</pat:PartNumber> may be user-input text for matching against contact names, group names, contact attributes, and/or group attributes. <pat:PartName pat:idref='PN-00159'>At step</pat:PartName> <pat:PartNumber pat:id='PN-00159'>156</pat:PartNumber>, the disclosed system displays contact list search results matching the <pat:PartName pat:idref='PN-00160'>search query received at step</pat:PartName> <pat:PartNumber pat:id='PN-00160'>154</pat:PartNumber>. Such results may be displayed to the user as a newly populated contact list in a contact list user interface display object, or alternatively in a separate user interface window or the like created for the purpose of displaying the search results. </pat:P><pat:P pat:pNumber="61" pat:id="p-61">The disclosed system may further be embodied to provide for storage and searching of metadata associated with contacts within the contact list. In such an embodiment, contact metadata is automatically stored by the underlying system (e.g. communication application or the like), and may include group, contact and/or attribute metadata (e.g. date and time created or last modified, context information regarding creation or last modification, contact e-mail address, etc.). While automatic storage of <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>17</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='18'?><pat:PatentImage pat:id='ID-00020' pat:imageContentCategory='Table' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025251.1.1803.160.2174.252.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.307</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.237</com:WidthMeasure><com:ALTText>Table</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="62" pat:id="p-62"><pat:BoundaryData><pat:HeaderText>CAM9-2007-0088U<pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='8'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>metadata by the underlying system may be provided in such an embodiment, contact attributes may still be expressly entered by the user, or automatically collected based on monitoring of the user's communication application activities, etc. The stored metadata may be searchable. For example, in one embodiment, the stored metadata is searched in response to a user query (e.g. in a contact search by attribute) that doesn't provide an immediate match in the contact list. Alternatively, one or more separate metadata search options may be provided to the user in a user interface object such as the <pat:PartName pat:idref='PN-00161'>Quick Search Pull-Down Menu</pat:PartName> <pat:PartNumber pat:id='PN-00161'>100</pat:PartNumber> of Fig. 5 (e.g. Search Contact Metadata, Search Group Metadata, Search Attribute Metadata, etc.). </pat:P><pat:P pat:pNumber="63" pat:id="p-63">In an exemplary embodiment, the stored metadata is not displayed to the user within the contact list display object, but is displayed in brackets (i.e., "&lt;&gt;") following matching entries in the search results. For example, if a user typed "ABC" as a contact list search query, the search performed by an embodiment of the disclosed system would result in a user interface display of a list of contact names from the contact list such as the following: </pat:P><pat:P pat:pNumber="64" pat:id="p-64">Tom Smith &lt;ABC Company&gt; Gail Adams &lt;ABC Industry&gt; Shirley McDougal &lt;ABC@email.com&gt; While the above description regarding illustrative embodiments of the disclosed system includes examples of specific user interface display objects, such as graphical buttons, menus, dialog boxes, and the like, the present invention is not limited to those specific examples. Accordingly, those skilled in the art will recognize that alternative <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>18</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='19'?><pat:PatentImage pat:id='ID-00021' pat:imageContentCategory='Graph' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025252.1.1803.160.2174.252.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.307</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.237</com:WidthMeasure><com:ALTText>Graph</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="65" pat:id="p-65"><pat:BoundaryData><pat:HeaderText>CAM9-2007-0088US <pat:OCRConfidenceData pat:levelNumber='8'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>embodiments may use any specific type or kind of user interface display object that may be appropriate. </pat:P><pat:P pat:pNumber="66" pat:id="p-66">The disclosed system can take the form of an entirely software embodiment, an entirely hardware embodiment, or an embodiment containing both software and hardware elements. The figures include block diagram and flowchart illustrations of methods, apparatus(s) and computer program products according to an embodiment of the invention. It will be understood that each block in such figures, and combinations of these blocks, can be implemented by computer program instructions. These computer program instructions may be loaded onto a computer or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus create means for implementing the functions specified in the block or blocks. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the block or blocks. </pat:P><pat:P pat:pNumber="67" pat:id="p-67"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>19</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='20'?><pat:PatentImage pat:id='ID-00022' pat:imageContentCategory='Graph' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>11865099.10-01-2007.F793RP9QPPOPPY4.SPEC_27025253.1.1803.160.2174.252.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.307</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.237</com:WidthMeasure><com:ALTText>Graph</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="68" pat:id="p-68"><pat:BoundaryData><pat:HeaderText>CAM9-2007-0088US <pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>Those skilled in the art should readily appreciate that programs defining the functions of the present invention can be delivered to a computer in many forms; including, but not limited to: (a) information permanently stored on non-writable storage media (e.g. read only memory devices within a computer such as ROM or CD-ROM disks readable by a computer I/O attachment); (b) information alterably stored on writable storage media (e.g. floppy disks and hard drives); or (c) information conveyed to a computer through communication media for example using wireless, baseband signaling or broadband signaling techniques, including carrier wave signaling techniques, such as over computer or telephone networks via a modem. </pat:P><pat:P pat:pNumber="69" pat:id="p-69">While the invention is described through the above exemplary embodiments, it will be understood by those of ordinary skill in the art that modification to and variation of the illustrated embodiments may be made without departing from the inventive concepts herein disclosed. </pat:P><pat:P pat:pNumber="70" pat:id="p-70"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>20</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData></pat:P></pat:Specification></pat:SpecificationDocument>
|
applicant/11873683.xml
ADDED
|
@@ -0,0 +1,184 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11873683</doc-number>
|
| 8 |
+
<date>2007-10-17</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">INCENT<confidence value="8">I</confidence>
|
| 14 |
+
VE IMAGING METHODS AND DEVICES </heading>
|
| 15 |
+
<p id="p-1" num="1">Technical Field The present invention relates to a method for providing incentives to consumers at transactions and cards that are provided with changeable image displays.</p>
|
| 16 |
+
<p id="p-2" num="2">Background Art Conventional point-of-sale computer systems, such as those used in retail stores to record transactions, are being used more and more in customer relationship management systems. The flexibility of the traditional retail applications along with the improving functionality of retail point-of-sale printers has been utilized more and more for purposes of marketing goods and developing customer incentives.</p>
|
| 17 |
+
<p id="p-3" num="3">Improves to point-of-sale marketing have typically involved the issuance of promotions, often in the form of coupons, to customers in the checkout lanes. In order to increase the effectiveness of such advertising, systems identify a particular customer through a shopper's club card or other individually distinguishable indicia that is presented to the teller at the time of check out. Once a customer is identified, the system can scan a database of previous purchases made by that customer to identify purchasing habits. Based on these habits, the customer can be issued a coupon, often with the intent of getting the customer to stray from favorite brand names.</p>
|
| 18 |
+
<p id="p-4" num="4">Systems such as that described may involve the use of a secondary system with a <page-break num="2"/>
|
| 19 |
+
secondary printer. This secondary system operates independently of the retail system but is capable of accessing data concerning customer transactions. These systems are the subject of much criticism from retailers, however, that are concerned with the secondary hardware and applications that must reside in their stores. Many retailers also object to granting access to data regarding past purchases of their customers. Along these lines, consumers have expressed concern regarding the privacy of their transactions as many consumers feel that prior purchases are personal business and should not be used by a marketing company to derive profit. </p>
|
| 20 |
+
<p id="p-5" num="5">An improved system is described in U.S. Patent No. 7,028,894 to Turner et al. which includes a system and method for targeting marketing messages at a point-of-sale consumer by collecting current transactional receipt data, such as the time of a retail transaction, the date of the transaction, the number of items purchased the transaction, and the total dollar value of a transaction. The data collected from the receipt is then applied to one or more algorithms to determine which marketing messages are most likely to be successful. A predetermined number of marketing messages found most likely to be successful are then printed on the customer receipt in order of priority of expected effectiveness. The system is designed to be used in connection with a point-of-sale terminal without the need for additional hardware, such as a second printer, or the need to access historical customer data.</p>
|
| 21 |
+
<p id="p-6" num="6">To date, marketing systems that are designed to provide incentives in the form of coupons, redeemable discounts, etc. all rely on printed materials (e.g., coupons, discount certificates, etc.) which are either printed at the point-of-sale, for example on the back of a cash register receipt, or printed and mailed to customers who participate in customer programs that require the customers to furnish their mailing addresses. Alternatively, some merchants <confidence value="5">e</confidence>
|
| 22 |
+
-mail <boundary-data type="header">-2-</boundary-data>
|
| 23 |
+
<page-break num="3"/>
|
| 24 |
+
incentive offerings to registered customers in the form of coupons, redeemable discount certificates that the registered customer prints out on his or her home computer/printer. </p>
|
| 25 |
+
<p id="p-7" num="7">The present invention is directed to a <confidence value="222222222222222222222">promotional/marketing</confidence>
|
| 26 |
+
method that images incentives, e.g. coupons, discount certificates, etc. on a credit card, gift card, merchant card, shopper club card, or the like. </p>
|
| 27 |
+
<p id="p-8" num="8">Disclosure of the Invention According to various features, characteristics and embodiments of the present invention which will become apparent as the description thereof proceeds, the present invention provides a method of providing point-of-sale incentives to customers which involves;</p>
|
| 28 |
+
<p id="p-9" num="9">providing a customer with a card having a changeable display area;</p>
|
| 29 |
+
<p id="p-10" num="10">receiving the card from the customer during the purchase of a product or service;</p>
|
| 30 |
+
<p id="p-11" num="11">causing an image to be displayed on the display area of the card which image comprises an incentive to the customer; and returning the card to the customer with the image displayed thereon.</p>
|
| 31 |
+
<p id="p-12" num="12">The present invention further provides a method of providing incentives to customers which involves;</p>
|
| 32 |
+
<p id="p-13" num="13">providing a customer with a card having a changeable display area;</p>
|
| 33 |
+
<p id="p-14" num="14">receiving the card from the customer during a transaction;</p>
|
| 34 |
+
<p id="p-15" num="15">causing an image to be displayed on the display area of the card which image comprises an incentive to the customer; and returning the card to the customer with the image displayed thereon.</p>
|
| 35 |
+
<boundary-data type="header">-3-</boundary-data>
|
| 36 |
+
<p id="p-16" num="16">
|
| 37 |
+
<page-break num="4"/>
|
| 38 |
+
The present invention also provides a transaction card that displays an updated display of an image on the card which includes: </p>
|
| 39 |
+
<p id="p-17" num="17">a transaction card;</p>
|
| 40 |
+
<p id="p-18" num="18">a display area visible on a surface of the transaction card;</p>
|
| 41 |
+
<p id="p-19" num="19">a data communications package provided in the transaction card; and a microprocessor for storing a image data and updating and displaying an updated image on the card received from the data communications package.</p>
|
| 42 |
+
<p id="p-20" num="20">Brief Description of Drawings The present invention will be described with reference to the attached drawings which are given as non-limiting examples only, in which:</p>
|
| 43 |
+
<p id="p-21" num="21">Figure 1 is an illustration of a credit card according to one embodiment of the present invention.</p>
|
| 44 |
+
<p id="p-22" num="22">Figure 2 is a cross-sectional view of the credit card of Fig. <confidence value="5">1</confidence>
|
| 45 |
+
taken along sectional lines <confidence value="66866">II-II</confidence>
|
| 46 |
+
which illustrates how the leads extend from the display area to contact leads at the edge or peripheral portion of the card according to one embodiment. </p>
|
| 47 |
+
<p id="p-23" num="23">Figure 3 is a schematic illustration of a transaction card and system for updating and displaying images on the card.</p>
|
| 48 |
+
<p id="p-24" num="24">Best Mode for Carrying out the Invention <boundary-data type="header">-4-</boundary-data>
|
| 49 |
+
<page-break num="5"/>
|
| 50 |
+
The present invention is directed to credit cards, gift cards, merchant cards, shopper club cards, or similar cards that for one reason or another are can be presented at a point-of-sale transaction. More particularly, the present invention is directed to credit cards, gift cards, merchant cards, shopper club cards and the like which are provided with a changeable, renewable or updateable display upon which a incentive such as a coupon, discount certificate, etc. can be displayed. </p>
|
| 51 |
+
<p id="p-25" num="25">Figure 1 is an illustration of a credit card according to one embodiment of the present invention. The credit card shown in Fig. 1 and generally identified by reference numeral <part-num-ref name="and generally identified by reference numeral">1</part-num-ref>
|
| 52 |
+
can be sized and shaped like a conventional credit card and can include a standard machine-readable magnetic strip and any conventional security protection, e.g. hologram, security code number, owner signature area, photo identification of owner, etc. </p>
|
| 53 |
+
<p id="p-26" num="26">According to the present invention, the credit card includes a display area <part-num-ref name="display area">2</part-num-ref>
|
| 54 |
+
which can extend over any portion of a face of the credit card <part-num-ref name="credit card">1,</part-num-ref>
|
| 55 |
+
and is not necessarily limited to the configuration depicted in Fig. 1. The display area <part-num-ref name="display area">2</part-num-ref>
|
| 56 |
+
comprises an Electronic Paper Display (EPD) that is available from E Ink Corporation and described on E Ink Corporation's website at www.eink.com. The display area <part-num-ref name="display area">2</part-num-ref>
|
| 57 |
+
can be incorporated into the credit card using any convenient film imaging technique and is provided with an integrated driver lead or bus that is configured to present contact leads at an edge or peripheral portion of the card, generally identified by reference numeral <part-num-ref name="card, generally identified by reference numeral">3</part-num-ref>
|
| 58 |
+
in Fig. 1, for coupling the card to a suitable display driver that can change, renew or update images displayed on the display area. Figure 2 is a cross-sectional view of the credit card of Fig. 1 taken along sectional lines I<confidence value="5885">I-II</confidence>
|
| 59 |
+
which illustrates how the leads extend from the display area to contact leads at the edge or peripheral portion of the card according to one <boundary-data type="header">-5-</boundary-data>
|
| 60 |
+
<page-break num="6"/>
|
| 61 |
+
embodiment. As shown, leads <part-num-ref name="card according to one embodiment. As shown, leads">4</part-num-ref>
|
| 62 |
+
are embedded in the card <part-num-ref name="card">1</part-num-ref>
|
| 63 |
+
and extend from the display area <part-num-ref name="display area">2</part-num-ref>
|
| 64 |
+
to the contact leads <part-num-ref name="contact leads">3.</part-num-ref>
|
| 65 |
+
</p>
|
| 66 |
+
<p id="p-27" num="27">The use of an EPD eliminates the need for an onboard power supply to view images on the display area <part-num-ref name="display area">2,</part-num-ref>
|
| 67 |
+
since an EPD only requires power to change the image. In such a situation, the necessary power to change the image could be supplied externally though the contact leads. </p>
|
| 68 |
+
<p id="p-28" num="28">Of course it is within the scope of the invention to provide an onboard power supply, if desired to stabilize the displayed image and to assist in changing, renewing or updating the image.</p>
|
| 69 |
+
<p id="p-29" num="29">In an alternative embodiment, the display area <part-num-ref name="display area">2</part-num-ref>
|
| 70 |
+
could comprise an electronic display that is powered by an onboard power supply. Such electronic displays are known in the art of so- called "smart cards" as offered, for example, by Aveso, Inc. (Fridley, MN). Although such electronic displays can be used in the cards of the present invention, their requirement for display power consumption limits useful life and otherwise requires recharging or replacement of their power supplies. </p>
|
| 71 |
+
<p id="p-30" num="30">The present invention is further directed to the method using cards, e.g. credit cards, gift cards, merchant cards, shopper club cards, or similar cards having display areas in such a manner that the type of incentives, such as coupons, discount certificates, other offerings, etc. that are conventionally printed on the back or cash register receipts or separately from cash register receipt at a point-of-sale are, according to the present invention, provided as an image that is displayed on the display area of the cards.</p>
|
| 72 |
+
<p id="p-31" num="31">Since the image on the display area is changeable, renewable or updateable, it is possible to display a new incentive, e.g. new coupon, new discount certificates, other new offerings, etc., every time the card is presented at a point-of sale transaction. The system used to determine the particular type of incentive, e.g. coupon(s), discount certificate(s), other offering(s), etc. can be <boundary-data type="header">-6-</boundary-data>
|
| 73 |
+
<page-break num="7"/>
|
| 74 |
+
essentially the same as those used in known systems which print similar incentives on cash register receipts or secondary point-of-sale printers. Exemplary systems are disclosed or cited in U.S. Patent No. 7,028,894 to Turner et al., U.S. Patent No. 6,885,996 to Nicholson, and U.S. </p>
|
| 75 |
+
<p id="p-32" num="32">Patent No. 6,321,210 to O'Brien, et al., the complete disclosures of which are hereby expressly incorporated by reference.</p>
|
| 76 |
+
<p id="p-33" num="33">According to the present invention, the resulting data that would normally be processed to print a particular incentive is instead used to create an image that is displayed in the display area. Such signal/data processing can be accomplished by known means.</p>
|
| 77 |
+
<p id="p-34" num="34">According to an exemplarily scenario a customer having a card according to the present invention goes to a merchant and buys a product or service. Upon presenting his or her credit card to complete the purchase, the customer's card is placed in or ran through a card reader which debits the customer's credit card and a docking port which connects the integrated driver lead or bus at an edge or peripheral portion of the card with a suitable display driver that causes an incentive image to be displayed on the card. According to one embodiment, the displayed image is an incentive that is supplied by a product manufacturer or distributor or other enterprise and is not necessary related to any data related to the customer's shopping habits. In this embodiment, the product manufacturers or distributors or other enterprises can be charged a fee, similar to an advertisement fee, for placing their incentive images on the customer's card. When the customer uses his or her card for a subsequent purchase, the same process is repeated;</p>
|
| 78 |
+
<p id="p-35" num="35">however, a different incentive image can be displayed on the customer's card. The card reader and docking port can be provided as separate devices or a single integrated device.</p>
|
| 79 |
+
<p id="p-36" num="36">According to another embodiment, the card can include any type of information about the customer, such as geographic location, shopping habits, etc., that can be used to determine an <boundary-data type="header">-7-</boundary-data>
|
| 80 |
+
<page-break num="8"/>
|
| 81 |
+
appropriate incentive that has a greater potential to induce the customer into purchasing a specific product or service. A specific, non-limiting, example is the type of information that is provided on shoppers' club or merchant's cards, which can be in the formatted as an optical bar code or magnetically encoded. Such data can be read at the time the customer's card is presented to complete a purchase and the algorithms in the above-cited patents or similar algorithms can be used to determine an appropriate incentive image that is displayed on the display area of the card at the point-of-sale. </p>
|
| 82 |
+
<p id="p-37" num="37">In a further embodiment of the present invention, in addition to displaying the incentive images discussed above, a random prize notification could be generated and displayed.<confidence value="5">.</confidence>
|
| 83 |
+
For example, a sponsor could offer a prize or prizes that would be redeemable if and when a prize notification image would be generated and displayed on the display area of the cards. Such a promotion or random give-a-way would create an additional interest to customers, who in addition to receiving the incentives discussed above, might also be lucky enough to win a prize. </p>
|
| 84 |
+
<p id="p-38" num="38">According to another embodiment, the cards having the display areas could be "casino cards" e.g., slot cards, comp cards, players' cards, etc. which, in addition to being used in a conventional manner to reward a customer for his or her loyalty, for example by tracking the amount of money a customer spends and rewarding comps, cash back, etc., can display such rewards, additional incentives, prizes (randomly or drawn), etc.</p>
|
| 85 |
+
<p id="p-39" num="39">According to a further embodiment of the present invention, the cards could be provided with a memory chip that would store or stack data related to the last few, for example the last <part-num-ref name="last">3</part-num-ref>
|
| 86 |
+
or <part-num-ref name="or">4</part-num-ref>
|
| 87 |
+
incentive images, so that a consumer could use an incentive that was previously presented as an image, but subsequently replaced by a later incentive image. Such an <boundary-data type="header">-8-</boundary-data>
|
| 88 |
+
<page-break num="9"/>
|
| 89 |
+
embodiment would allow a customer to retain a desired incentive while conducting a point-of- sale transaction that does not utilize the desired incentive, but nevertheless replaces it with a new incentive image. The data stored in the onboard memory chip could be reviewed and verified by a merchant when the card is presented and placed in or ran through an appropriate card reader. When an incentive is used, the onboard memory chip could be updated to delete that incentive. </p>
|
| 90 |
+
<p id="p-40" num="40">Although a credit card has been used in the examples presented above, the method of providing incentive images on a card is not limited to the use of credit cards. Other types of cards, including gift cards, debit cards, ATM cards, shoppers' cards, merchants' cards, phone cards, etc. can also be used. Accordingly, the term "card" or "cards" as used herein encompasses all such cards and is not limited to only credit cards. Further, the present invention is not limited for use with rectangular cards, but could also be used in conjunction with keychain-type cards that may or may not be strictly flat or rectangularly shaped, but could have any three-dimensional shape.</p>
|
| 91 |
+
<p id="p-41" num="41">Further, reference herein to merchant or merchants includes all types of entities that engage in commercial activity, both wholesale and retail, including manufacturers, distributors or sellers of goods, service industries/entities of all types. Examples include, but are not limited to, department stores, grocery stores, restaurants, banks (AMT'<confidence value="5">s</confidence>
|
| 92 |
+
), casinos, etc. </p>
|
| 93 |
+
<p id="p-42" num="42">Further, it is noted that while the display area is shown in Fig. 1 as having a rectangular shape, the display area can have any desired shape and can include multiple display areas on one or both sides of the card. Further, in addition to the display areas, any and all the card types discussed herein could include memory chips and function as "smart cards" by storing <boundary-data type="header">-9-</boundary-data>
|
| 94 |
+
<page-break num="10"/>
|
| 95 |
+
data thereon and displaying images based upon the stored data, including images that are determined externally from the stored data. </p>
|
| 96 |
+
<p id="p-43" num="43">Figure 3 illustrates another embodiment of the present invention that is directed to a transaction card and system for updating and displaying images on the card.</p>
|
| 97 |
+
<p id="p-44" num="44">As used herein, the term "transactional card" refers to credit cards, gift cards<confidence value="5">,</confidence>
|
| 98 |
+
merchant cards, shopper club cards, or similar cards. Such cards are not necessary limited to rectangular cards, but could also be used in conjunction with keychain-type cards that may or may not be strictly flat or rectangularly shaped, but could have any three-dimensional shape. </p>
|
| 99 |
+
<p id="p-45" num="45">As depicted in Fig. 3 the transactional card <part-num-ref name="transactional card">5</part-num-ref>
|
| 100 |
+
includes a display area <part-num-ref name="display area">6</part-num-ref>
|
| 101 |
+
which can be similar to the display areas discussed herein in reference to the embodiment of the invention depicted in Figs. 1 and <part-num-ref name="and">2.</part-num-ref>
|
| 102 |
+
That is, the display area <part-num-ref name="display area">6</part-num-ref>
|
| 103 |
+
can be an EPD or an electronic display that is powered by an onboard power supply. </p>
|
| 104 |
+
<p id="p-46" num="46">The transactional card and system depicted in Fig 3 are used to display images on the card before and after a transaction. The images include coupons, discount certificates, or other marketing or promotional offerings, prize notifications, loyalty rewards, etc. The transaction can be any of a commercial activity including a sales transaction, casino gaming activity, cash or value transfer or debit, etc. In this regard, in addition to the display area <part-num-ref name="display area">6,</part-num-ref>
|
| 105 |
+
the transactional card is also provided with a microprocessor <part-num-ref name="microprocessor">7</part-num-ref>
|
| 106 |
+
that includes a memory for storing image data that has been displayed and/or will be displayed on card <part-num-ref name="memory for storing image data that has been displayed and/or will be displayed on card">5</part-num-ref>
|
| 107 |
+
and drives the display area <part-num-ref name="display area">6</part-num-ref>
|
| 108 |
+
to display the current and subsequent images on the card <part-num-ref name="card">5.</part-num-ref>
|
| 109 |
+
In addition, the transactional card <part-num-ref name="transactional card">5</part-num-ref>
|
| 110 |
+
also includes a data communications package <part-num-ref name="data communications package">8</part-num-ref>
|
| 111 |
+
that provides communications between the microprocessor <part-num-ref name="microprocessor">7</part-num-ref>
|
| 112 |
+
onboard the card <part-num-ref name="card">5</part-num-ref>
|
| 113 |
+
and a card processor <part-num-ref name="card processor">9,</part-num-ref>
|
| 114 |
+
discussed below. </p>
|
| 115 |
+
<boundary-data type="header">-10-</boundary-data>
|
| 116 |
+
<p id="p-47" num="47">
|
| 117 |
+
<page-break num="11"/>
|
| 118 |
+
The card processor 9 includes a data communications package <part-num-ref name="data communications package">10</part-num-ref>
|
| 119 |
+
that communicates with the onboard data communications package <part-num-ref name="onboard data communications package">8.</part-num-ref>
|
| 120 |
+
According to one embodiment of the present invention, the data communications packages <part-num-ref name="data communications packages">8</part-num-ref>
|
| 121 |
+
and <part-num-ref name="and">10</part-num-ref>
|
| 122 |
+
communication with a host communication module <part-num-ref name="host communication module">12</part-num-ref>
|
| 123 |
+
via processor <part-num-ref name="via processor">11.</part-num-ref>
|
| 124 |
+
The host communication module <part-num-ref name="host communication module">12</part-num-ref>
|
| 125 |
+
communicates to a host network which, for example can be a merchant's sales transaction network that verifies that the current value or balance of the card <part-num-ref name="card">5</part-num-ref>
|
| 126 |
+
is sufficient to complete a desired transaction. The host network debits the transactional card <part-num-ref name="transactional card">5</part-num-ref>
|
| 127 |
+
and communicates new image data via the host communications module <part-num-ref name="host communications module">12,</part-num-ref>
|
| 128 |
+
to the processor <part-num-ref name="processor">12,</part-num-ref>
|
| 129 |
+
which in turn communicates the new image data to the onboard microprocessor <part-num-ref name="onboard microprocessor">7</part-num-ref>
|
| 130 |
+
via the data communication packages <part-num-ref name="data communication packages">10</part-num-ref>
|
| 131 |
+
and <part-num-ref name="and">8.</part-num-ref>
|
| 132 |
+
The display driver of the microprocessor <part-num-ref name="microprocessor">7</part-num-ref>
|
| 133 |
+
updates the display area <part-num-ref name="display area">6</part-num-ref>
|
| 134 |
+
to show the new image on the card <part-num-ref name="card">5.</part-num-ref>
|
| 135 |
+
</p>
|
| 136 |
+
<p id="p-48" num="48">The card processor can include an electronic display <part-num-ref name="electronic display">13</part-num-ref>
|
| 137 |
+
that functions as a touch keypad to operate the card processor. Alternatively, a separate keypad could be provided. </p>
|
| 138 |
+
<p id="p-49" num="49">The transactional card 5 can either include an onboard power source to operate the microprocessor <part-num-ref name="microprocessor">7</part-num-ref>
|
| 139 |
+
and data communications package <part-num-ref name="and data communications package">8.</part-num-ref>
|
| 140 |
+
Alternatively, the power necessary to operate the microprocessor <part-num-ref name="microprocessor">7</part-num-ref>
|
| 141 |
+
and data communications package <part-num-ref name="and data communications package">8</part-num-ref>
|
| 142 |
+
could come from an external source, for example a docking port that is integral or separate from the card processor. As noted above, if an EPD is used, no power will be required to maintain the display of the balance. </p>
|
| 143 |
+
<p id="p-50" num="50">The data communication packages can comprise plug-in, docketing type systems or wireless, R<confidence value="5">F</confidence>
|
| 144 |
+
communication chipsets that are packaged appropriately for use in the card format. </p>
|
| 145 |
+
<p id="p-51" num="51">The transactional cards can comprise traditional magnetic stripped cards in which instance a reader/transaction processor can be provided that utilizes similar COTS hardware to interface the host system and the transactional cards.</p>
|
| 146 |
+
<boundary-data type="header">-11-</boundary-data>
|
| 147 |
+
<p id="p-52" num="52">
|
| 148 |
+
<page-break num="12"/>
|
| 149 |
+
The card processor can also include a physical link and software driven coding/decoding (code) to enable the transfer of appropriate date without host system changes. Typical host network data sources can be TCP/IP over Ethernet or similar, serial or parallel printer data designed to provide customer sales receipts, existing card-swipe terminals, etc. </p>
|
| 150 |
+
<p id="p-53" num="53">The transactional card and system depicted in Fig. 3 can use conventional software and hardware that is packaged so as to compatible with the format of a transactional card.</p>
|
| 151 |
+
<p id="p-54" num="54">According to another embodiment of the present invention the transactional card and system shown in Fig. 3 can be used to display a current/updated balance on a balance card. As used in reference to this embodiment, a "balance card" includes cards that have a value that changes when the cards are used in a transaction or when the cards are re-charged or re-loaded to increase their value. Non-limiting examples of balance cards include gift cards, credit cards that have a spending limit, re-loadable merchant cards, casino cards, fare cards, etc. Such cards are not necessary limited to rectangular cards, but could also be used in conjunction with keychain- type cards that may or may not be strictly flat or rectangularly shaped, but could have any three-dimensional shape.</p>
|
| 152 |
+
<p id="p-55" num="55">In order to update and display the current/updated balance or value of a balance card, the data communication packages <part-num-ref name="data communication packages">8</part-num-ref>
|
| 153 |
+
and <part-num-ref name="and">10</part-num-ref>
|
| 154 |
+
are bi-directional data communications packages. </p>
|
| 155 |
+
<p id="p-56" num="56">In operation, the bi-directional data communications package <part-num-ref name="bi-directional data communications package">8</part-num-ref>
|
| 156 |
+
reports an account and/or identification code/number and the current value or balance of the card <part-num-ref name="card">5</part-num-ref>
|
| 157 |
+
(if not available to the host network) to the bi-directional data communications package <part-num-ref name="bi-directional data communications package">10.</part-num-ref>
|
| 158 |
+
The bi-directional data communications package <part-num-ref name="bi-directional data communications package">10</part-num-ref>
|
| 159 |
+
forwards the account and/or identification code/number and the current value or balance of the card <part-num-ref name="card">5</part-num-ref>
|
| 160 |
+
to processor <part-num-ref name="to processor">11</part-num-ref>
|
| 161 |
+
which is in communication with a host communication module <part-num-ref name="host communication module">12.</part-num-ref>
|
| 162 |
+
The host communication module <part-num-ref name="host communication module">12</part-num-ref>
|
| 163 |
+
receives the account and/or <boundary-data type="header">-12-</boundary-data>
|
| 164 |
+
<page-break num="13"/>
|
| 165 |
+
identification code/number and the current value or balance of the card <part-num-ref name="card">5</part-num-ref>
|
| 166 |
+
and communicates to a host network which, for example can be a merchant's sales transaction network that verifies that the current value or balance of the card <part-num-ref name="card">5</part-num-ref>
|
| 167 |
+
is sufficient to complete a desired transaction. The host network debits the balance card <part-num-ref name="balance card">
|
| 168 |
+
<confidence value="5">5</confidence>
|
| 169 |
+
</part-num-ref>
|
| 170 |
+
(or can re-charge or re-load the balance card <part-num-ref name="balance card">5)</part-num-ref>
|
| 171 |
+
and communicates the new balance or value via the host communications module <part-num-ref name="host communications module">12,</part-num-ref>
|
| 172 |
+
to the processor <part-num-ref name="processor">12,</part-num-ref>
|
| 173 |
+
which in turn communicates the new balance or value to the onboard microprocessor <part-num-ref name="onboard microprocessor">7</part-num-ref>
|
| 174 |
+
via the bi-directional data communication packages <part-num-ref name="bi-directional data communication packages">10</part-num-ref>
|
| 175 |
+
and <part-num-ref name="and">8.</part-num-ref>
|
| 176 |
+
The display driver of the microprocessor <part-num-ref name="microprocessor">7</part-num-ref>
|
| 177 |
+
updates the display area <part-num-ref name="display area">6</part-num-ref>
|
| 178 |
+
to show the new balance or value of the card <part-num-ref name="card">5.</part-num-ref>
|
| 179 |
+
</p>
|
| 180 |
+
<p id="p-57" num="57">Although the present invention has been described with reference to particular means, materials and embodiments, from the foregoing description, one skilled in the art can easily ascertain the essential characteristics of the present invention and various changes and modifications can be made to adapt the various uses and characteristics without departing from the spirit and scope of the present invention as described above and set forth in the attached claims.</p>
|
| 181 |
+
<boundary-data type="header">-13-</boundary-data>
|
| 182 |
+
</description>
|
| 183 |
+
</us-patent-application>
|
| 184 |
+
|
applicant/11918822.xml
ADDED
|
@@ -0,0 +1,2 @@
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?><uspat:SpecificationDocument xmlns:uscom="urn:us:gov:doc:uspto:common" xmlns:uspat="urn:us:gov:doc:uspto:patent" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:com="http://www.wipo.int/standards/XMLSchema/ST96/Common" xmlns:pat="http://www.wipo.int/standards/XMLSchema/ST96/Patent" uscom:vendorName="VASTEC" uscom:createDateTime="2017-10-31T17:02:28Z" com:st96Version="V2_1" com:ipoVersion="US_V7_1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent Patent/V7_1/Schema/USPatent/Document/SpecificationDocument_V7_1.xsd" com:documentFileName="11918822.10-31-2017.J9FU7FOQRXEAPX3.SPEC.XML" com:id="J9FU7FOQRXEAPX3">
|
| 2 |
+
<uspat:DocumentMetadata com:id="ID0000001"><uscom:DocumentCode>SPEC</uscom:DocumentCode><uscom:ApplicationNumberText uscom:electronicText="11918822">11918822</uscom:ApplicationNumberText><com:PageTotalQuantity>1</com:PageTotalQuantity><uscom:ParagraphTotalQuantity>6</uscom:ParagraphTotalQuantity><uscom:OfficialDate>2017-10-31</uscom:OfficialDate></uspat:DocumentMetadata><?PageStart number='1'?><uscom:P com:pNumber="1" com:id="p-1">LAIBLE et al.</uscom:P><uscom:P com:pNumber="2" com:id="p-2">App<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">l</uscom:OCRConfidenceData>. No. 11/918,822</uscom:P><uscom:Heading com:id="h-1"><com:U>AMENDMENTS TO THE SPECIFICATION:</com:U></uscom:Heading><uscom:P com:pNumber="3" com:id="p-3" uscom:indentationLevelNumber="L1">On page 1, after the title please insert the following:</uscom:P><uscom:P com:pNumber="4" com:id="p-4" uscom:indentationLevelNumber="L1"><com:U>This application is a U.S. National Phase of International Patent Application No.</com:U></uscom:P><uscom:P com:pNumber="5" com:id="p-5"><uscom:PartName com:idrefs="PN-00001">PCT/EP2006/06<uscom:OCRConfidenceData uscom:ocrConfidenceCode="86">1 </uscom:OCRConfidenceData></uscom:PartName><uscom:PartNumber com:id="PN-00001"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">1</uscom:OCRConfidenceData>04,</uscom:PartNumber><com:U> filed March 28, 2006, which designates the U.S. and claims priority to German Patent Application No. DE 10 2005 021 589.0, filed May 10, 2005, the entire contents of each of which are hereby incorporated by reference.</com:U></uscom:P><uscom:P com:pNumber="6" com:id="p-6" uscom:indentationLevelNumber="L2"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="888">-2-</uscom:OCRConfidenceData></uscom:P></uspat:SpecificationDocument>
|
applicant/11925196.xml
ADDED
|
@@ -0,0 +1,676 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11925196</doc-number>
|
| 8 |
+
<date>2007-10-26</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 14 |
+
<heading id="h-1">TITLE: SYSTEM AND METHOD FOR VIDEO CODING USING</heading>
|
| 15 |
+
<heading id="h-2">VARIABLE COMPRESSION AND OBJECT MOTION TRACKING</heading>
|
| 16 |
+
<heading id="h-3">RELATED APPLICATION DATA</heading>
|
| 17 |
+
<p id="p-1" num="1">
|
| 18 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 19 |
+
This application claims the benefit of U.S. Provisional Patent Application Serial No. 60/980,011 filed October <part-num-ref name="benefit of U.S. Provisional Patent Application Serial No. 60/980,011 filed October">15,</part-num-ref>
|
| 20 |
+
<part-num-ref name="benefit of U.S. Provisional Patent Application Serial No. 60/980,011 filed October 15,">2007,</part-num-ref>
|
| 21 |
+
the disclosure of which is herein incorporated by reference in its entirety. </p>
|
| 22 |
+
<heading id="h-4">TECHNICAL FIELD OF THE INVENTION</heading>
|
| 23 |
+
<p id="p-2" num="2">
|
| 24 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 25 |
+
The technology of the present disclosure relates generally to compression of video data and, more particularly, to a system and method for video coding using different amounts of compression for various portions of a video image and tracking a moving object that is compressed to have high image fidelity. </p>
|
| 26 |
+
<heading id="h-5">BACKGROUND</heading>
|
| 27 |
+
<p id="p-3" num="3">
|
| 28 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 29 |
+
Mobile and/or wireless electronic devices are becoming increasingly popular. For example, mobile telephones, portable media players and portable gaming devices are now in wide-spread use. In addition, the features associated with certain types of electronic devices have become increasingly diverse. For example, many mobile telephones now <boundary-data type="line-number">20 </boundary-data>
|
| 30 |
+
include cameras that are capable of capturing still images and video images. </p>
|
| 31 |
+
<p id="p-4" num="4">It is common to encode video data from a video camera. Encoding the video data may be used to compress the video data so that the video data may be transmitted using less bandwidth and stored using less memory space.</p>
|
| 32 |
+
<p id="p-5" num="5">One encoding technique developed by the Moving Picture Experts Group (MPEG) <boundary-data type="line-number">25 </boundary-data>
|
| 33 |
+
under the MPEG-4 Standard contemplates identifying media objects from a scene. These objects include a still object (e.g., a fixed background), a video object (e.g., a talking <boundary-data type="header">
|
| 34 |
+
<confidence value="8">1</confidence>
|
| 35 |
+
</boundary-data>
|
| 36 |
+
<page-break num="2"/>
|
| 37 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 38 |
+
person without the background) and an audio object (e.g., the voice of the speaking person or background music). The distinguishing of media objects in MP<confidence value="5">E</confidence>
|
| 39 |
+
G-4 to describe a scene allows authors to construct scenes by placing media objects anywhere in a given coordinate system, applying transforms to change the geometrical or acoustical <boundary-data type="line-number">5 </boundary-data>
|
| 40 |
+
appearance of a media object, grouping primitive media objects to form compound media objects, applying streamed data to media objects to modify their attributes and changing viewing points. </p>
|
| 41 |
+
<p id="p-6" num="6">Unfortunately, MP<confidence value="5">E</confidence>
|
| 42 |
+
G-4 and other object-based encoding techniques have shortfalls when handling moving objects. When an object moves appreciably within the <boundary-data type="line-number">10 </boundary-data>
|
| 43 |
+
scene or when the camera angle changes so that the object moves relative to the background, coding of the scene restarts (e.g., a new reference frame or "Iframe" is established upon which the encoding of future frames are based until another Iframe is established). </p>
|
| 44 |
+
<heading id="h-6">SUMMARY</heading>
|
| 45 |
+
<p id="p-7" num="7">
|
| 46 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 47 |
+
To improve video encoding, the present disclosure describes an improved video coding technique and system that employ object tracking and variable compression for different portions of the scene. The object is coded to have higher fidelity than a remainder of the scene. The higher fidelity facilitates tracking of the object that, in turn, <boundary-data type="line-number">20 </boundary-data>
|
| 48 |
+
assists in maintaining quality coding of the object. </p>
|
| 49 |
+
<p id="p-8" num="8">According to one aspect of the disclosure, a method of coding a video signal that contains video data corresponding to an imaged scene includes identifying an object that corresponds to a visual element from the scene, a portion of the scene other than the visual element being a remainder of the scene; compressing video data corresponding to the <boundary-data type="line-number">25 </boundary-data>
|
| 50 |
+
object and compressing a remainder of the video data using an amount of compression that is greater than an amount of compression used to compress the video data for the object so as to produce a high fidelity video component corresponding to the visual element and a low fidelity video component corresponding to the remainder of the scene; and tracking the object using the high fidelity video component and using tracking information <boundary-data type="header">
|
| 51 |
+
<confidence value="8">2</confidence>
|
| 52 |
+
</boundary-data>
|
| 53 |
+
<page-break num="3"/>
|
| 54 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 55 |
+
regarding a predicted position of the object in a future frame of the video signal to compress the video data when the future frame arrives. </p>
|
| 56 |
+
<p id="p-9" num="9">According to one embodiment of the method, the object is identified using pattern recognition.</p>
|
| 57 |
+
<p id="p-10" num="10">
|
| 58 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 59 |
+
According to one embodiment of the method, the pattern recognition is used to identify a face of a person. </p>
|
| 60 |
+
<p id="p-11" num="11">According to one embodiment of the method, the object is identified by proximity of the visual element to a predetermined location within the scene.</p>
|
| 61 |
+
<p id="p-12" num="12">According to one embodiment of the method, the object is identified by receiving <boundary-data type="line-number">10 </boundary-data>
|
| 62 |
+
input from a user that specifies the visual element. </p>
|
| 63 |
+
<p id="p-13" num="13">According to one embodiment of the method, the data is broken into blocks of pixels and blocks containing pixels corresponding to the object are compressed to generate the high fidelity video component and remaining blocks are compressed to generate the low fidelity video component.</p>
|
| 64 |
+
<p id="p-14" num="14">
|
| 65 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 66 |
+
According to one embodiment, the method further includes transmitting an output video signal that includes the high fidelity video component and low fidelity video component, and higher error coding is applied to the high fidelity video component than error coding that is applied to low fidelity video component. </p>
|
| 67 |
+
<p id="p-15" num="15">According to one embodiment of the method, a reference frame is maintained for <boundary-data type="line-number">20 </boundary-data>
|
| 68 |
+
the object and a separate reference frame is maintained for the remainder of the scene. </p>
|
| 69 |
+
<p id="p-16" num="16">According to one embodiment of the method, the video coding is carried out by an electronic device that includes a camera assembly that images the scene to generate the video signal.</p>
|
| 70 |
+
<p id="p-17" num="17">According to one embodiment of the method, the electronic device is a mobile <part-num-ref name="mobile">25</part-num-ref>
|
| 71 |
+
telephone. </p>
|
| 72 |
+
<boundary-data type="header">
|
| 73 |
+
<confidence value="8">3</confidence>
|
| 74 |
+
</boundary-data>
|
| 75 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 76 |
+
<p id="p-18" num="18">
|
| 77 |
+
<page-break num="4"/>
|
| 78 |
+
According to another aspect of the disclosure, a video signal encoder that encodes a video signal that contains video data corresponding to an imaged scene includes an object identification module that identifies an object that corresponds to a visual element from the scene, a portion of the scene other than the visual element being a remainder of <boundary-data type="line-number">5 </boundary-data>
|
| 79 |
+
the scene; an image compression module that compresses video data corresponding to the object and compresses a remainder of the video data using an amount of compression that is greater than an amount of compression used to compress the video data for the object so as to produce a high fidelity video component corresponding to the visual element and a low fidelity video component corresponding to the remainder of the scene; and a motion <boundary-data type="line-number">10 </boundary-data>
|
| 80 |
+
tracking module that tracks the object using the high fidelity video component and generates tracking information regarding a predicted position of the object in a future frame of the video signal, the tracking information used by the image compression module to compress the video data when the future frame arrives. </p>
|
| 81 |
+
<p id="p-19" num="19">According to one embodiment of the encoder, the object identification module uses <boundary-data type="line-number">15 </boundary-data>
|
| 82 |
+
pattern recognition to identify the object. </p>
|
| 83 |
+
<p id="p-20" num="20">According to one embodiment of the encoder, the pattern recognition is used to identify a face of a person.</p>
|
| 84 |
+
<p id="p-21" num="21">According to one embodiment of the encoder, the object identification module uses proximity of the visual element to a predetermined location within the scene to identify the <boundary-data type="line-number">20 </boundary-data>
|
| 85 |
+
object. </p>
|
| 86 |
+
<p id="p-22" num="22">According to one embodiment of the encoder, the object identification module uses user input to identify the object.</p>
|
| 87 |
+
<p id="p-23" num="23">According to one embodiment of the encoder, the video data is broken into blocks of pixels and blocks containing pixels corresponding to the object are compressed to <boundary-data type="line-number">25 </boundary-data>
|
| 88 |
+
generate the high fidelity video component and remaining blocks are compressed to generate the low fidelity video component. </p>
|
| 89 |
+
<p id="p-24" num="24">According to one embodiment, the encoder further includes a transmission module to transmit an output video signal that includes the high fidelity video component and low fidelity video component to a destination, and the transmission module applies higher <boundary-data type="header">
|
| 90 |
+
<confidence value="8">4</confidence>
|
| 91 |
+
</boundary-data>
|
| 92 |
+
<page-break num="5"/>
|
| 93 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 94 |
+
error coding to the high fidelity video component than error coding that the transmission module applies to the low fidelity video component. </p>
|
| 95 |
+
<p id="p-25" num="25">According to one embodiment of the encoder, a reference frame is maintained for the object and a separate reference frame is maintained for the remainder of the scene.</p>
|
| 96 |
+
<p id="p-26" num="26">
|
| 97 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 98 |
+
According to one embodiment of the encoder, the encoder is part of an electronic device that includes a camera assembly that images the scene to generate the video. </p>
|
| 99 |
+
<p id="p-27" num="27">According to one embodiment of the encoder, the electronic device is a mobile telephone and includes call circuitry to establish a call over a network.</p>
|
| 100 |
+
<p id="p-28" num="28">According to another aspect of the disclosure, a second method of coding a video <boundary-data type="line-number">10 </boundary-data>
|
| 101 |
+
signal that contains video data corresponding to an imaged scene includes compressing video data corresponding to an identified portion of the scene; compressing a remainder of the video data using an amount of compression that is greater than an amount of compression used to compress the video data for the identified portion of the scene; and outputting a high fidelity video component corresponding to the identified portion of the <boundary-data type="line-number">15 </boundary-data>
|
| 102 |
+
scene and a low fidelity video component corresponding to the remainder of the video data. </p>
|
| 103 |
+
<p id="p-29" num="29">According to one embodiment of the second method, the identified portion of the scene corresponds to a fixed region of a video image that is represented by the video signal.</p>
|
| 104 |
+
<p id="p-30" num="30">
|
| 105 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 106 |
+
These and further features will be apparent with reference to the following description and attached drawings. In the description and drawings, particular embodiments of the invention have been disclosed in detail as being indicative of some of the ways in which the principles of the invention may be employed, but it is understood that the invention is not limited correspondingly in scope. Rather, the invention includes <boundary-data type="line-number">25 </boundary-data>
|
| 107 |
+
all changes, modifications and equivalents coming within the scope of the claims appended hereto. </p>
|
| 108 |
+
<boundary-data type="header">
|
| 109 |
+
<confidence value="8">5</confidence>
|
| 110 |
+
</boundary-data>
|
| 111 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 112 |
+
<p id="p-31" num="31">
|
| 113 |
+
<page-break num="6"/>
|
| 114 |
+
Features that are described and/or illustrated with respect to one embodiment may be used in the same way or in a similar way in one or more other embodiments and/or in combination with or instead of the features of the other embodiments. </p>
|
| 115 |
+
<p id="p-32" num="32">The terms "comprises" and "comprising," when used in this specification, are taken <boundary-data type="line-number">5 </boundary-data>
|
| 116 |
+
to specify the presence of stated features, integers, steps or components but do not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof. </p>
|
| 117 |
+
<heading id="h-7">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 118 |
+
<p id="p-33" num="33">
|
| 119 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 120 |
+
FIG<confidence value="58">s.</confidence>
|
| 121 |
+
<confidence value="5">1</confidence>
|
| 122 |
+
and <part-num-ref name="and">2</part-num-ref>
|
| 123 |
+
are respectively a front view and a rear view of an exemplary electronic device that includes a representative camera assembly; </p>
|
| 124 |
+
<p id="p-34" num="34">FIG. 3 is a schematic view of another representative camera assembly in the act of filming a scene;</p>
|
| 125 |
+
<p id="p-35" num="35">FIG. 4 is a block diagram of a video encoder that may be used to encode video data <boundary-data type="line-number">15 </boundary-data>
|
| 126 |
+
in accordance with aspects of the disclosure; </p>
|
| 127 |
+
<p id="p-36" num="36">FIG. 5 illustrates a representative video frame and depicts exemplary embodiments of identifying an object for tracking within an associated scene during video encoding;</p>
|
| 128 |
+
<p id="p-37" num="37">FIG. 6 illustrates another representative video frame and depicts another exemplary embodiment of identifying an object for tracking within an associated scene <boundary-data type="line-number">20 </boundary-data>
|
| 129 |
+
during video encoding; </p>
|
| 130 |
+
<p id="p-38" num="38">FIG. 7 illustrates a portion of a video frame that contains an object to be tracked and shows a manner in which compression may be applied to component pixel blocks from the portion of the video frame;</p>
|
| 131 |
+
<p id="p-39" num="39">FIG. 8 is a schematic block diagram of the electronic device of FIG<confidence value="58">s.</confidence>
|
| 132 |
+
<confidence value="5">1</confidence>
|
| 133 |
+
and 2; and <boundary-data type="line-number">25 </boundary-data>
|
| 134 |
+
FIG. 9 is a schematic diagram of a communications system in which the electronic device of FIG<confidence value="58">s.</confidence>
|
| 135 |
+
<confidence value="5">1</confidence>
|
| 136 |
+
and <part-num-ref name="and">2</part-num-ref>
|
| 137 |
+
may operate. </p>
|
| 138 |
+
<boundary-data type="header">
|
| 139 |
+
<confidence value="8">6</confidence>
|
| 140 |
+
</boundary-data>
|
| 141 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 142 |
+
<heading id="h-8">DETAILED DESCRIPTION OF EMBODIMENTS</heading>
|
| 143 |
+
<p id="p-40" num="40">
|
| 144 |
+
<page-break num="7"/>
|
| 145 |
+
Embodiments will now be described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. It will be understood that <boundary-data type="line-number">5 </boundary-data>
|
| 146 |
+
the figures are not necessarily to scale. </p>
|
| 147 |
+
<p id="p-41" num="41">Described below in conjunction with the appended figures are various embodiments of an improved video coding system and method. In the illustrated embodiments, the video coding is carried out by a device that includes a video camera used to capture video data. It will be understood that the video data may be captured by <boundary-data type="line-number">10 </boundary-data>
|
| 148 |
+
one device and then transferred to another device that carries out the video coding. It also will be understood that the camera assembly may be capable of capturing still images in addition to video images. </p>
|
| 149 |
+
<p id="p-42" num="42">The video coding will be primarily described in the context of processing video data generated by a digital video camera that is made part of a mobile telephone. It will be <boundary-data type="line-number">15 </boundary-data>
|
| 150 |
+
appreciated that the video coding may be used in other operational contexts such as, but not limited to, a dedicated video camera, another type of electronic device that has a camera (e.g., a personal digital assistant (PDA), a media player, a gaming device, a "web" camera, a computer, etc.), and so forth. Also, the video coding may be carried out by a device that processes existing video data, such as by a computer that accesses stored video <boundary-data type="line-number">20 </boundary-data>
|
| 151 |
+
data from a data storage medium or that receives video data over a communication link. </p>
|
| 152 |
+
<p id="p-43" num="43">Referring initially to FIG<confidence value="5">s</confidence>
|
| 153 |
+
. 1 and <part-num-ref name="and">2,</part-num-ref>
|
| 154 |
+
an electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 155 |
+
is shown. The illustrated electronic device <part-num-ref name="illustrated electronic device">10</part-num-ref>
|
| 156 |
+
is a mobile telephone. The electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 157 |
+
includes a camera assembly <part-num-ref name="camera assembly">12</part-num-ref>
|
| 158 |
+
for taking digital still pictures and/or digital video clips. It is emphasized that the electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 159 |
+
need not be a mobile telephone, but could be a <boundary-data type="line-number">25 </boundary-data>
|
| 160 |
+
dedicated camera or some other device as indicated above. For instance, as illustrated in FIG. 3, the electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 161 |
+
is a dedicated camera assembly <part-num-ref name="dedicated camera assembly">12.</part-num-ref>
|
| 162 |
+
</p>
|
| 163 |
+
<p id="p-44" num="44">With reference to FIG<confidence value="5">s</confidence>
|
| 164 |
+
. 1 through <part-num-ref name="through">3,</part-num-ref>
|
| 165 |
+
the camera assembly <part-num-ref name="camera assembly">12</part-num-ref>
|
| 166 |
+
may be arranged as a typical camera assembly that includes a lens assembly <part-num-ref name="lens assembly">14</part-num-ref>
|
| 167 |
+
to focus light from a scene <part-num-ref name="scene">16</part-num-ref>
|
| 168 |
+
within the field of view <part-num-ref name="field of view">18</part-num-ref>
|
| 169 |
+
of the camera assembly <part-num-ref name="camera assembly">12</part-num-ref>
|
| 170 |
+
onto a sensor (not shown). The <boundary-data type="header">
|
| 171 |
+
<confidence value="8">7</confidence>
|
| 172 |
+
</boundary-data>
|
| 173 |
+
<page-break num="8"/>
|
| 174 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 175 |
+
sensor converts the incident light into video data and outputs a corresponding video signal that may be coded using the techniques described in this disclosure. </p>
|
| 176 |
+
<p id="p-45" num="45">The camera assembly 12 may include other components such as, but not limited to, optical elements that supplement the lens assembly (e.g., a protective window, a filter, a <boundary-data type="line-number">5 </boundary-data>
|
| 177 |
+
prism, a mirror), focusing mechanics, optical zooming mechanics, a flash or light source <part-num-ref name="flash or light source">20,</part-num-ref>
|
| 178 |
+
a light meter <part-num-ref name="light meter">22,</part-num-ref>
|
| 179 |
+
a display <part-num-ref name="display">24</part-num-ref>
|
| 180 |
+
for functioning as an electronic viewfinder and as part of an interactive user interface, a keypad <part-num-ref name="keypad">26</part-num-ref>
|
| 181 |
+
and/or buttons <part-num-ref name="and/or buttons">28</part-num-ref>
|
| 182 |
+
for accepting user inputs, an optical viewfinder (not shown), a microphone, and any other components commonly associated with cameras. Another component may be an electronic controller that controls <boundary-data type="line-number">10 </boundary-data>
|
| 183 |
+
operation of the camera assembly <part-num-ref name="camera assembly">12.</part-num-ref>
|
| 184 |
+
The electronic controller or a separate circuit (e.g., a dedicated video encoder) may carry out the video coding. The electrical assembly that carries out the video coding may be embodied, for example, as a processor that executes logical instructions that are stored by an associated memory, as firmware, as an arrangement of dedicated circuit components or as a combination of these embodiments. </p>
|
| 185 |
+
<p id="p-46" num="46">
|
| 186 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 187 |
+
Thus, the video coding technique may be physically embodied as executable code (e.g., software) that is stored on a machine readable medium or as part of an electrical circuit. </p>
|
| 188 |
+
<p id="p-47" num="47">With additional reference to FIG. 4, illustrated is a block diagram of a video encoder <part-num-ref name="video encoder">30.</part-num-ref>
|
| 189 |
+
As indicated, the video encoder <part-num-ref name="video encoder">30</part-num-ref>
|
| 190 |
+
may be implemented in hardware and/or in software. An image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 191 |
+
may receive an input video signal that <boundary-data type="line-number">20 </boundary-data>
|
| 192 |
+
contains video data to be encoded. For instance, the input video signal may be the video signal generated by the sensor of the camera assembly <part-num-ref name="camera assembly">12.</part-num-ref>
|
| 193 |
+
The input video signal may be a series of frames (or video sequence) where each frame includes data to represent the imaged scene <part-num-ref name="imaged scene">16.</part-num-ref>
|
| 194 |
+
Collectively, the series of frames are referred to as a video image. </p>
|
| 195 |
+
<p id="p-48" num="48">Exemplary frame rates for the input video signal may be <part-num-ref name="input video signal may be">15</part-num-ref>
|
| 196 |
+
frames per second, <part-num-ref name="frames per second,">20</part-num-ref>
|
| 197 |
+
frames <boundary-data type="line-number">25 </boundary-data>
|
| 198 |
+
per second, <part-num-ref name="frames per second,">24</part-num-ref>
|
| 199 |
+
frames per second, <part-num-ref name="frames per second,">30</part-num-ref>
|
| 200 |
+
frames per second, or <part-num-ref name="frames per second, or">60</part-num-ref>
|
| 201 |
+
frames per second. </p>
|
| 202 |
+
<p id="p-49" num="49">The image compression module 32 applies a variable amount of compression to the video data for each frame of the video signal. For instance, the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 203 |
+
may apply a low or moderate amount of compression to one region of the image and a higher amount of compression to the rest of the image. The portion of the <boundary-data type="line-number">30 </boundary-data>
|
| 204 |
+
image that is compressed by the lower amount will have higher image fidelity relative to the portion of the image that is compressed with a higher amount of compression. As <boundary-data type="header">
|
| 205 |
+
<confidence value="8">8</confidence>
|
| 206 |
+
</boundary-data>
|
| 207 |
+
<page-break num="9"/>
|
| 208 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 209 |
+
such, a portion of the output video data corresponding to the portion of the video that is compressed with the lower amount of compression will be referred to as a high fidelity component and a portion of the output video data corresponding to the portion of video data that is compressed with the higher amount of compression will be referred to as a low <boundary-data type="line-number">5 </boundary-data>
|
| 210 |
+
fidelity component. The low fidelity component and the high fidelity component may be output by the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 211 |
+
in a single, combined stream (e.g., one signal) or in separate data streams (e.g., two or more signals). </p>
|
| 212 |
+
<p id="p-50" num="50">The portion of the image that receives lower compression may be a contiguous section of the image or may be non-contiguous. Therefore, the high fidelity component <boundary-data type="line-number">10 </boundary-data>
|
| 213 |
+
may correspond to one portion of the image or more than one portion of the image. </p>
|
| 214 |
+
<p id="p-51" num="51">The portion(s) of the image to receive lower compression may be one or more visual elements from the image, and may be considered an object. For simplicity, the ensuing description will refer to an object in the singular, but the reader should understand that the description of an object in the singular explicitly includes one or more than one <boundary-data type="line-number">15 </boundary-data>
|
| 215 |
+
portions of the image. </p>
|
| 216 |
+
<p id="p-52" num="52">The object may be identified by an object identification module <part-num-ref name="object identification module">34.</part-num-ref>
|
| 217 |
+
There are a number of ways in which the object may be identified by the object identification module <part-num-ref name="object identification module">34.</part-num-ref>
|
| 218 |
+
Some exemplary embodiments of object identification will be described. The object identification module <part-num-ref name="object identification module">34</part-num-ref>
|
| 219 |
+
may be capable of identifying the object using just one technique <boundary-data type="line-number">20 </boundary-data>
|
| 220 |
+
or more than one technique. In embodiments where the object identification module <part-num-ref name="object identification module">34</part-num-ref>
|
| 221 |
+
has the capability to identify the object using more than one technique, the technique that is employed for a video clip may be selected by a user. In another embodiment, the object identification module <part-num-ref name="object identification module">34</part-num-ref>
|
| 222 |
+
may analyze the image and select one of the techniques based on results of the analysis. </p>
|
| 223 |
+
<p id="p-53" num="53">
|
| 224 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 225 |
+
With additional reference to FIG. 5, a frame <part-num-ref name="frame">36</part-num-ref>
|
| 226 |
+
from a series of frames that makes up a video image is shown. The frame <part-num-ref name="frame">36</part-num-ref>
|
| 227 |
+
is a representation of a scene (e.g., the scene <part-num-ref name="scene">16</part-num-ref>
|
| 228 |
+
of FIG. 3) at one moment in time. The scene may change over time as items in the scene (e.g., people, cars, animals, etc.) move and/or the camera assembly <part-num-ref name="camera assembly">12</part-num-ref>
|
| 229 |
+
moves with respect to the scene. </p>
|
| 230 |
+
<boundary-data type="header">
|
| 231 |
+
<confidence value="8">9</confidence>
|
| 232 |
+
</boundary-data>
|
| 233 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 234 |
+
<p id="p-54" num="54">
|
| 235 |
+
<page-break num="10"/>
|
| 236 |
+
FIG. 5 is used to represent at least two exemplary techniques for object identification. The first technique is to designate a portion of the frame to receive lower compression than the rest of the frame. For instance, a fixed region <part-num-ref name="fixed region">38</part-num-ref>
|
| 237 |
+
of the frame may be designated to receive lower compression. All visual elements inside the perimeter of <boundary-data type="line-number">5 </boundary-data>
|
| 238 |
+
fixed region <part-num-ref name="perimeter of fixed region">38</part-num-ref>
|
| 239 |
+
will then receive lower compression and a remainder of the image will then receive higher compression relative to the fixed region <part-num-ref name="fixed region">38.</part-num-ref>
|
| 240 |
+
In this embodiment, the object that is identified by the object identification module <part-num-ref name="object identification module">34</part-num-ref>
|
| 241 |
+
is the fixed region <part-num-ref name="fixed region">38</part-num-ref>
|
| 242 |
+
and the object will not change in relative location from frame to frame. In the illustrated embodiment, the fixed region <part-num-ref name="fixed region">38</part-num-ref>
|
| 243 |
+
is illustrated as being in the center of the image and as a <boundary-data type="line-number">10 </boundary-data>
|
| 244 |
+
rectangle. It will be appreciated that the fixed region need not be in the center of the image and that other shapes (e.g., a circle or an oval) are contemplated. Also, the region <part-num-ref name="region">38</part-num-ref>
|
| 245 |
+
may surround a subregion (not illustrated) so that the subregion receives less compression than the region <part-num-ref name="region">38</part-num-ref>
|
| 246 |
+
that, in turn, receives less compression than the remainder of the image. In one embodiment, the fixed region <part-num-ref name="fixed region">38</part-num-ref>
|
| 247 |
+
may be comprised of plural <boundary-data type="line-number">15 </boundary-data>
|
| 248 |
+
spatially distinct regions that are each designated to receive less compression than the remainder of the image. For instance, the fixed region <part-num-ref name="fixed region">38</part-num-ref>
|
| 249 |
+
may be comprised of four regions arranged following the rule of thirds. The rule of thirds will be described in more detail with respect to FIG. 6. In another embodiment, the fixed region <part-num-ref name="fixed region">38</part-num-ref>
|
| 250 |
+
may be specified by the user. </p>
|
| 251 |
+
<p id="p-55" num="55">
|
| 252 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 253 |
+
The use of a fixed region <part-num-ref name="fixed region">38</part-num-ref>
|
| 254 |
+
of the image to be the identified object may be appropriate in certain filming circumstances. As an example, the fixed region <part-num-ref name="fixed region">38</part-num-ref>
|
| 255 |
+
may be a convenient object if the user of the camera assembly <part-num-ref name="camera assembly">12</part-num-ref>
|
| 256 |
+
were to compose a video clip to concentrate on a stationary or moving item while keeping that item in a relatively constant location in the image. For instance, the user may set the camera assembly <part-num-ref name="camera assembly">12</part-num-ref>
|
| 257 |
+
to film a <boundary-data type="line-number">25 </boundary-data>
|
| 258 |
+
speaker who is expected to remain in a predicted location as shown in the exemplary scene <part-num-ref name="exemplary scene">16</part-num-ref>
|
| 259 |
+
of FIG. 3. As another, the user may film a race car as the race car travels around a track and, during the filming, the user may attempt to center the car in the image. </p>
|
| 260 |
+
<p id="p-56" num="56">As indicated, FIG. 5 may represent another technique for object identification. In this embodiment, the object is not a fixed region of the image, but is an item in the filmed <boundary-data type="line-number">30 </boundary-data>
|
| 261 |
+
scene that may move. The technique is implemented to identify an item that may be the user<confidence value="8">'</confidence>
|
| 262 |
+
s main interest. In the illustrated embodiment, the object identification module <part-num-ref name="object identification module">34</part-num-ref>
|
| 263 |
+
<boundary-data type="header">
|
| 264 |
+
<confidence value="88">10</confidence>
|
| 265 |
+
</boundary-data>
|
| 266 |
+
<page-break num="11"/>
|
| 267 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 268 |
+
scans the image for predominate items that are located within or overlap with a designated area, such as the fixed region <part-num-ref name="fixed region">38.</part-num-ref>
|
| 269 |
+
In the representation of FIG. 5, an item <part-num-ref name="item">40</part-num-ref>
|
| 270 |
+
is present in the image and that item <part-num-ref name="image and that item">40</part-num-ref>
|
| 271 |
+
may be singled out by the object identification module <part-num-ref name="object identification module">34</part-num-ref>
|
| 272 |
+
as the identified object. The object identification module <part-num-ref name="object identification module">34</part-num-ref>
|
| 273 |
+
may communicate the location <boundary-data type="line-number">5 </boundary-data>
|
| 274 |
+
of the identified object to the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 275 |
+
such that the object may be compressed with less compression than the rest of the image. The location of the object may be specified in terms of a coordinate system, a group of pixel identities, or in any other appropriate manner. </p>
|
| 276 |
+
<p id="p-57" num="57">When the object is identified as an item from the scene, the object may move in <boundary-data type="line-number">10 </boundary-data>
|
| 277 |
+
relative location and/or size from frame to frame. To track this movement, the encoder <part-num-ref name="encoder">30</part-num-ref>
|
| 278 |
+
may include a motion tracking module <part-num-ref name="motion tracking module">42.</part-num-ref>
|
| 279 |
+
The motion tracking module <part-num-ref name="motion tracking module">42</part-num-ref>
|
| 280 |
+
may receive the object location information from the object identification module <part-num-ref name="object identification module">34</part-num-ref>
|
| 281 |
+
so that the initial position and size of the object is known to the motion tracking module <part-num-ref name="motion tracking module">42.</part-num-ref>
|
| 282 |
+
Thereafter, the motion tracking module <part-num-ref name="motion tracking module">42</part-num-ref>
|
| 283 |
+
may track location changes, shape changes and/or size changes <boundary-data type="line-number">15 </boundary-data>
|
| 284 |
+
of the object, which will be referred to collectively as the movement of the object. Object tracking information may be passed from the motion tracking module <part-num-ref name="motion tracking module">42</part-num-ref>
|
| 285 |
+
to the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 286 |
+
so that compression may be applied to the object even if the object has undergone movement. In this manner, the object is compressed to have relatively high fidelity throughout the video clip. Image compression and object tracking <boundary-data type="line-number">20 </boundary-data>
|
| 287 |
+
will be described in greater detail below. </p>
|
| 288 |
+
<p id="p-58" num="58">FIG. 6 illustrates another technique of object identification. Similar to the second technique described with respect to FIG. 5, the technique is implemented to identify an item that may be the user's main interest. In the illustrated embodiment, the object identification module <part-num-ref name="object identification module">34</part-num-ref>
|
| 289 |
+
scans the image for a prominent item or items that are coincident <boundary-data type="line-number">25 </boundary-data>
|
| 290 |
+
with designated points or spots, such as the points associated with the rule of thirds. The rule of thirds states that an image can be divided into nine equal parts by two equally- spaced horizontal lines 43a and two equally-spaced vertical lines 43b. The four points formed by the intersections of these lines can be used to align features in the video on the premise that an observer's eyes are naturally drawn toward these points. In FIG. 6, shown <boundary-data type="line-number">30 </boundary-data>
|
| 291 |
+
is a frame <part-num-ref name="frame">36</part-num-ref>
|
| 292 |
+
from a series of frames that makes up a video image with points identified by the intersection of rule of thirds lines <part-num-ref name="intersection of rule of thirds lines">43.</part-num-ref>
|
| 293 |
+
In the illustrated embodiment, the object <boundary-data type="header">
|
| 294 |
+
<confidence value="88">11</confidence>
|
| 295 |
+
</boundary-data>
|
| 296 |
+
<page-break num="12"/>
|
| 297 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 298 |
+
identification module <part-num-ref name="object identification module">34</part-num-ref>
|
| 299 |
+
scans the image for predominate items that are located at the intersection of the lines <part-num-ref name="lines">43.</part-num-ref>
|
| 300 |
+
In the representation of FIG. 6, the item <part-num-ref name="item">40</part-num-ref>
|
| 301 |
+
is present at one of the intersections and item <part-num-ref name="intersections and item">40</part-num-ref>
|
| 302 |
+
may be singled out by the object identification module <part-num-ref name="object identification module">34</part-num-ref>
|
| 303 |
+
as the identified object. The object identification module <part-num-ref name="object identification module">34</part-num-ref>
|
| 304 |
+
may communicate the location <boundary-data type="line-number">5 </boundary-data>
|
| 305 |
+
of the identified object to the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 306 |
+
and the motion tracking module <part-num-ref name="motion tracking module">42.</part-num-ref>
|
| 307 |
+
</p>
|
| 308 |
+
<p id="p-59" num="59">Another technique for identifying the object is by user identification. In one embodiment, the display <part-num-ref name="display">24</part-num-ref>
|
| 309 |
+
that is used as an electronic viewfinder may be touch-sensitive to form a touchscreen. The user may touch a point on the touchscreen that corresponds to <boundary-data type="line-number">10 </boundary-data>
|
| 310 |
+
an item or items of highest interest to the user. In turn, the object identification module <part-num-ref name="object identification module">34</part-num-ref>
|
| 311 |
+
may parse the image data for a visual element that is associated with the touched point and deem the part of the video data corresponding to the visual element as the object. The object identification module <part-num-ref name="object identification module">34</part-num-ref>
|
| 312 |
+
may then communicate the location of the identified object to the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 313 |
+
and the motion tracking module <part-num-ref name="motion tracking module">42.</part-num-ref>
|
| 314 |
+
In another <boundary-data type="line-number">15 </boundary-data>
|
| 315 |
+
embodiment, cross-hairs may be displayed on the display <part-num-ref name="display">24</part-num-ref>
|
| 316 |
+
with the image. The user may move the cross-hairs over a desired item using an input device, such as a navigation input device or a pointer, and select the item to be the object by pressing a select button. </p>
|
| 317 |
+
<p id="p-60" num="60">In turn, the object identification module <part-num-ref name="object identification module">34</part-num-ref>
|
| 318 |
+
may parse the image data for a visual element that is associated with the selected point and deem the part of the video data corresponding <boundary-data type="line-number">20 </boundary-data>
|
| 319 |
+
to the visual element as the object. The object identification module <part-num-ref name="object identification module">34</part-num-ref>
|
| 320 |
+
may then communicate the location of the identified object to the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 321 |
+
and the motion tracking module <part-num-ref name="motion tracking module">42.</part-num-ref>
|
| 322 |
+
</p>
|
| 323 |
+
<p id="p-61" num="61">Another technique for identifying the object is by pattern recognition. In this embodiment, the object identification module <part-num-ref name="object identification module">34</part-num-ref>
|
| 324 |
+
may scan the image for items that are <boundary-data type="line-number">25 </boundary-data>
|
| 325 |
+
recognizable and likely to be the items of interest to the user. Recognizable items may include, for example, a person's face, a person's body (e.g., a humanoid form), a car, a truck, a cat, a dog and so forth. For instance, a common face recognition technique is to search an image for color patterns that are indicative of a pair of eyes together with a bridge of a nose. If plural items are recognized, each of those items may be identified as <boundary-data type="line-number">30 </boundary-data>
|
| 326 |
+
the object. If a scene contains a relatively large number of recognized items (e.g., three or more items), the items may be prioritized based on size and/or location within the scene <boundary-data type="header">
|
| 327 |
+
<confidence value="88">12</confidence>
|
| 328 |
+
</boundary-data>
|
| 329 |
+
<page-break num="13"/>
|
| 330 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 331 |
+
and a selected number of the highest priority items (e.g., three or fewer) may be identified as the object. </p>
|
| 332 |
+
<p id="p-62" num="62">With additional reference to FIG. 7, an exemplary technique for varying the amount of compression across the video image is illustrated. In FIG. 7, a portion of a <boundary-data type="line-number">5 </boundary-data>
|
| 333 |
+
video frame <part-num-ref name="video frame">44</part-num-ref>
|
| 334 |
+
is shown. The frame portion <part-num-ref name="frame portion">44</part-num-ref>
|
| 335 |
+
is broken into a matrix of pixel blocks <part-num-ref name="matrix of pixel blocks">46.</part-num-ref>
|
| 336 |
+
</p>
|
| 337 |
+
<p id="p-63" num="63">Each pixel block 46 may be a group of pixels, such as an N x N square of pixels where N is a number, such as eight or sixteen. An object <part-num-ref name="object">48</part-num-ref>
|
| 338 |
+
to receive lower compression relative to the rest of the image is shown. The image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 339 |
+
applies low compression to the blocks <part-num-ref name="blocks">46</part-num-ref>
|
| 340 |
+
that overlap with the object <part-num-ref name="object">48</part-num-ref>
|
| 341 |
+
to result in high fidelity for <boundary-data type="line-number">10 </boundary-data>
|
| 342 |
+
those blocks <part-num-ref name="to result in high fidelity for those blocks">46.</part-num-ref>
|
| 343 |
+
Hence, the high fidelity blocks are identified with an "H" in FIG. 7. </p>
|
| 344 |
+
<p id="p-64" num="64">Similarly, the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 345 |
+
applies high compression to the blocks <part-num-ref name="blocks">46</part-num-ref>
|
| 346 |
+
that do not overlap with the object <part-num-ref name="object">48</part-num-ref>
|
| 347 |
+
to result in low fidelity for those blocks <part-num-ref name="to result in low fidelity for those blocks">46.</part-num-ref>
|
| 348 |
+
Hence, the low fidelity blocks are identified with an "L" in FIG. 7. Compression techniques may include, for example, applying a discrete Fourier transform (DFT) to the video data for <boundary-data type="line-number">15 </boundary-data>
|
| 349 |
+
each block <part-num-ref name="video data for each block">46.</part-num-ref>
|
| 350 |
+
Also, the compression techniques may include coding of residual data (sometimes referred to as "residuals"). Residual data relates to the parts of the image that move between frames. </p>
|
| 351 |
+
<p id="p-65" num="65">The relative amounts of compression to produce the high fidelity component and the low fidelity component may correspond to user selection regarding operational <boundary-data type="line-number">20 </boundary-data>
|
| 352 |
+
performance or may be established by default. In another embodiment, the relative amounts of compression may be selected by the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 353 |
+
based on one or more criteria. These criteria may include the quality (e.g., resolution) or other attributes of the input video signal, desired quality of the output signal, the type of delivery channel <part-num-ref name="type of delivery channel">50</part-num-ref>
|
| 354 |
+
that may be used to transmit the coded video data to a destination <part-num-ref name="destination">52,</part-num-ref>
|
| 355 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 356 |
+
the bit rate capacity of the delivery channel <part-num-ref name="delivery channel">50,</part-num-ref>
|
| 357 |
+
a bit rate allocation scheme that allocates total available bit rate between the object and the remainder of the image, the quality or service (QoS) of the delivery channel <part-num-ref name="delivery channel">50,</part-num-ref>
|
| 358 |
+
an amount of movement of the object relative to amount of movement of the remainder of the image, and so forth. In one embodiment, the higher compression to produce the low fidelity component may be carried out to retain <boundary-data type="line-number">30 </boundary-data>
|
| 359 |
+
four bits per color or six bits per color and the lower compression to produce the high fidelity component may be carried out to retain eight bits per color or ten bits per color. It <boundary-data type="header">
|
| 360 |
+
<confidence value="88">13</confidence>
|
| 361 |
+
</boundary-data>
|
| 362 |
+
<page-break num="14"/>
|
| 363 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 364 |
+
will be appreciated that compression may be carried out to obtain other combinations of compression results. </p>
|
| 365 |
+
<p id="p-66" num="66">In one embodiment, the same compression algorithm may be used to generate both the high and low fidelity components, but different settings and states may be used to <boundary-data type="line-number">5 </boundary-data>
|
| 366 |
+
generate the different fidelity components. In another embodiment, a first compression algorithm may be used to generate the high fidelity component and a second compression algorithm may be used to generate the low fidelity component. </p>
|
| 367 |
+
<p id="p-67" num="67">In the illustration of FIG. 4, the low fidelity component and the high fidelity component are shown separately to visually portray aspects of the disclosure. While it is <boundary-data type="line-number">10 </boundary-data>
|
| 368 |
+
possible to output these components from the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 369 |
+
in separate signals, it is also possible that the components may be output by the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 370 |
+
together in a single, combined video data signal. </p>
|
| 371 |
+
<p id="p-68" num="68">One or more operations may be performed on the output of the image compression module <part-num-ref name="image compression module">32.</part-num-ref>
|
| 372 |
+
For instance, the video data may be stored in a memory component for later <boundary-data type="line-number">15 </boundary-data>
|
| 373 |
+
retrieval and viewing and/or for later retrieval and transmission over a network to another device. In one embodiment, the encoder <part-num-ref name="encoder">30</part-num-ref>
|
| 374 |
+
may include an additional module that carries out post-processing of the video data to introduce video effects or perform other functions on the video data. Also, in the illustrated embodiment, the output of the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 375 |
+
may be input to a transmission module <part-num-ref name="transmission module">54.</part-num-ref>
|
| 376 |
+
The transmission <boundary-data type="line-number">20 </boundary-data>
|
| 377 |
+
module <part-num-ref name="transmission module">54</part-num-ref>
|
| 378 |
+
may prepare the video data for transmission to the destination <part-num-ref name="destination">52</part-num-ref>
|
| 379 |
+
over the delivery channel <part-num-ref name="delivery channel">50.</part-num-ref>
|
| 380 |
+
The delivery channel <part-num-ref name="delivery channel">50</part-num-ref>
|
| 381 |
+
may be any suitable network, wireless interface or wired interface. The transmission module <part-num-ref name="transmission module">54</part-num-ref>
|
| 382 |
+
may be responsible for packetizing the video data for transmission in accordance with the protocol of the delivery channel <part-num-ref name="delivery channel">50.</part-num-ref>
|
| 383 |
+
</p>
|
| 384 |
+
<p id="p-69" num="69">
|
| 385 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 386 |
+
In one embodiment, the transmission module <part-num-ref name="transmission module">54</part-num-ref>
|
| 387 |
+
may apply a higher degree of error coding to the high fidelity component than to the low fidelity component. As will be appreciated, as the amount of error coding increases, the delivery performance of the associated packets increase. It is contemplated that the high fidelity component will have greater interest to the user (e.g., a viewer) at the destination <part-num-ref name="destination">50</part-num-ref>
|
| 388 |
+
than the low fidelity <part-num-ref name="low fidelity">30</part-num-ref>
|
| 389 |
+
component. Therefore, if the high fidelity component has higher error coding than the low <boundary-data type="header">
|
| 390 |
+
<confidence value="88">14</confidence>
|
| 391 |
+
</boundary-data>
|
| 392 |
+
<page-break num="15"/>
|
| 393 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 394 |
+
fidelity component, then the delivery performance of the portion of the video image with the greater importance may be prioritized over the rest of the video image. This approach may maintain the overall quality of service associated with the delivery of the video image by not overloading the delivery channel <part-num-ref name="delivery channel">50</part-num-ref>
|
| 395 |
+
with a high degree of error coding for all the <boundary-data type="line-number">5 </boundary-data>
|
| 396 |
+
video data that is transmitted. Rather, the portion of the video data that is likely to be the most important part of the video image will be delivered with greater accuracy than the rest of the video data. Lost packets and other transmission issues will be more likely to occur with the lower priority portions of the video image. But missing data packets for such lower priority regions of the image may go unnoticed by the viewer or may not <boundary-data type="line-number">10 </boundary-data>
|
| 397 |
+
negatively affect the viewing experience. </p>
|
| 398 |
+
<p id="p-70" num="70">As indicated above, the output of the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 399 |
+
may be input to the motion tracking module <part-num-ref name="motion tracking module">42.</part-num-ref>
|
| 400 |
+
The motion tracking module <part-num-ref name="motion tracking module">42</part-num-ref>
|
| 401 |
+
analyzes this video data to track changes in the size, the shape and the location of the object that was identified by the object identification module <part-num-ref name="object identification module">34.</part-num-ref>
|
| 402 |
+
The tracked changes may be used by the <boundary-data type="line-number">15 </boundary-data>
|
| 403 |
+
motion tracking module <part-num-ref name="motion tracking module">42</part-num-ref>
|
| 404 |
+
to generate a prediction of the position of the object in the next frame or some future frame. The prediction may be input to the image compression module <part-num-ref name="image compression module">32.</part-num-ref>
|
| 405 |
+
The prediction may be updated on a frame by frame basis so that the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 406 |
+
has a current prediction of the position of the tracked object. The current prediction may be used by the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 407 |
+
to apply appropriate <boundary-data type="line-number">20 </boundary-data>
|
| 408 |
+
compression to an incoming frame of the video input signal. In particular, the portions of the frame corresponding to the predicted position of the object may receive the low compression and the remainder of the frame may receive the high compression. In this manner, the video data representation of the object may be maintained in the high fidelity component even as the location, shape and/or size of the object changes relative to the <boundary-data type="line-number">25 </boundary-data>
|
| 409 |
+
location, shape and/or size originally identified by the object identification module <part-num-ref name="object identification module">34.</part-num-ref>
|
| 410 |
+
</p>
|
| 411 |
+
<p id="p-71" num="71">The motion tracking module 42 may employ a predictive analysis technique to track the movement of the object in terms of size, location and shape. For instance, the motion tracking module <part-num-ref name="motion tracking module">42</part-num-ref>
|
| 412 |
+
may observe the object in a first frame (e.g., frame N) and identify the changes that occur to the object between the first frame and a second frame <boundary-data type="line-number">30 </boundary-data>
|
| 413 |
+
(e.g., frame N<confidence value="55">+1</confidence>
|
| 414 |
+
). Subspace tracking of basis vectors may be used to predict where the object will be in the future, such as a third frame (e.g., frame N+2) or subsequent frame. </p>
|
| 415 |
+
<boundary-data type="header">
|
| 416 |
+
<confidence value="88">15</confidence>
|
| 417 |
+
</boundary-data>
|
| 418 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 419 |
+
<p id="p-72" num="72">
|
| 420 |
+
<page-break num="16"/>
|
| 421 |
+
Residual data coded by the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 422 |
+
also may be used to assist in the tracking function. The prediction as to position of the object in the future frame is the information that may be passed back to the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 423 |
+
and, when the frame corresponding to the prediction arrives, the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 424 |
+
may <boundary-data type="line-number">5 </boundary-data>
|
| 425 |
+
compress the portion of the frame corresponding to the prediction with less compression than the remainder of the frame. </p>
|
| 426 |
+
<p id="p-73" num="73">The above-described technique for coding video data using variable compression and using motion tracking can lead to savings in the amount of space that it may take to store a video file for the video data. Similarly, if the video data were to be transmitted <boundary-data type="line-number">10 </boundary-data>
|
| 427 |
+
over the delivery channel <part-num-ref name="delivery channel">50,</part-num-ref>
|
| 428 |
+
a savings in the amount of bit rate that it may take to transmit the data may be experienced. These savings are possible since a large portion of the video image (e.g., the portion of the image other than the object) may be compressed with relatively low fidelity. But the viewing clarity of the object may be maintained at a high level due to the application of a lower amount of compression to the object. As a <boundary-data type="line-number">15 </boundary-data>
|
| 429 |
+
result, the viewer may be satisfied with the overall image. The amount of compression applied to the majority of the image (e.g., everything but the object) may be less than the amount of compression used in prior art techniques where the entire image receives the same amount of compression. As a result, the net amount of video data output by the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 430 |
+
using the disclosed technique may be lower than the net <boundary-data type="line-number">20 </boundary-data>
|
| 431 |
+
amount of video data that may be output by an encoder operating under conventional techniques. This may be especially true in circumstances where the object moves relative to a background, such when the object is a person that is walking or when the object is a car that is traveling around a race track. In these situations, prior art coding techniques are forced to start a reference frame (e.g., an I<confidence value="66">fr</confidence>
|
| 432 |
+
ame) often as the background may be subject <boundary-data type="line-number">25 </boundary-data>
|
| 433 |
+
to a fairly rapid amount of change and the associated data output for the background component is very high compared to a stationary background. In one embodiment of the above-disclosed technique, as long as the object may be tracked, the compression may continue without starting a new reference frame. In another embodiment, separate reference frames may be maintained for the object and the remainder of the image as <part-num-ref name="image as">30</part-num-ref>
|
| 434 |
+
compression is separately applied to these respective portions of the image. </p>
|
| 435 |
+
<boundary-data type="header">
|
| 436 |
+
<confidence value="88">16</confidence>
|
| 437 |
+
</boundary-data>
|
| 438 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 439 |
+
<p id="p-74" num="74">
|
| 440 |
+
<page-break num="17"/>
|
| 441 |
+
The video data that is output by the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 442 |
+
may be decoded and used to drive a display so that the video content may be viewed. Since the object is coded to have higher fidelity than the rest of the image (e.g., the object may have greater resolution than the rest of the image), the object may appear clearer than the remainder of <boundary-data type="line-number">5 </boundary-data>
|
| 443 |
+
the image. Depending on the compression levels that are employed, the remainder portion of the image may appear to be slightly out of focus, at least relative to the object. In some situations, the appearance of the object versus the appearance of the remainder of the image may create a desired effect. For instance, the appearance differences may make the object appear to "stand out" from a background. It will be understood that the appearance <boundary-data type="line-number">10 </boundary-data>
|
| 444 |
+
differential between the object and the remainder portion of the image results from the separate compression that is applied to these segments of the image and not post- processing of the output of the image compression module <part-num-ref name="image compression module">32.</part-num-ref>
|
| 445 |
+
It is recognized, however, that any desired pre-processing of the video input signal and/or post-processing of the output of the image compression module <part-num-ref name="image compression module">32</part-num-ref>
|
| 446 |
+
may be carried out. </p>
|
| 447 |
+
<p id="p-75" num="75">
|
| 448 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 449 |
+
Coding the object with higher fidelity affords substantial benefit to the tracking mechanism of the motion tracking module <part-num-ref name="motion tracking module">42.</part-num-ref>
|
| 450 |
+
On an area by area basis (e.g., a pixel square <part-num-ref name="pixel square">46</part-num-ref>
|
| 451 |
+
by pixel square <part-num-ref name="by pixel square">46</part-num-ref>
|
| 452 |
+
basis), more bits of video data are allocated to the object than the remainder of the image. Since more information is present with respect to the object, the tracking mechanism may make a better prediction (e.g., estimate) about the future <boundary-data type="line-number">20 </boundary-data>
|
| 453 |
+
location, size and shape of the object than if the object had been coded with less fidelity. </p>
|
| 454 |
+
<p id="p-76" num="76">That is, the available spatial information about the object in the high fidelity component and tracking of how the constituent features move between frames will support a more accurate prediction of the where the object will be within the larger image in the next frame or some other future frame. In other words, the object is coded with a relatively <boundary-data type="line-number">25 </boundary-data>
|
| 455 |
+
large number of bits per color that, in effect, gives the object high resolution. This resolution provides a large amount of data that may be correlated in terms of pixels and motion vectors from frame to frame. Also, the tracking, which is a continuous process, may rely more on data that is coded with respect to the object than on data that is coded in residual frame data. In sum, the tracking mechanism should perform better using video <boundary-data type="line-number">30 </boundary-data>
|
| 456 |
+
data coded in the above-described manner than using video data that is coded in a conventional manner. These benefits perpetuate as the video image progresses through frames to maintain high quality coding of the object throughout the video clip, even <boundary-data type="header">
|
| 457 |
+
<confidence value="88">17</confidence>
|
| 458 |
+
</boundary-data>
|
| 459 |
+
<page-break num="18"/>
|
| 460 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 461 |
+
though the object may be moving. This is because the emphasis is on initially coding the object using a relatively large number of bits and maintaining the fidelity of the object as it moves, while reducing the reliance on residual data relating to the object. </p>
|
| 462 |
+
<p id="p-77" num="77">In one embodiment, the object identification module <part-num-ref name="object identification module">34</part-num-ref>
|
| 463 |
+
may be configured to have <boundary-data type="line-number">5 </boundary-data>
|
| 464 |
+
a memory of previously tracked objects. For instance, if the encoder <part-num-ref name="encoder">30</part-num-ref>
|
| 465 |
+
tracks an object during one continuous recording of a scene (or a "take"), the object identification module <part-num-ref name="object identification module">34</part-num-ref>
|
| 466 |
+
may search for that object in a later take. The closer the takes are to each other in time, the more probability there may be that the same object may be present in the subsequent take. Therefore, in one embodiment, the memory of previously tracked objects may have <boundary-data type="line-number">10 </boundary-data>
|
| 467 |
+
an associated time limit. </p>
|
| 468 |
+
<p id="p-78" num="78">As indicated, the illustrated electronic device <part-num-ref name="illustrated electronic device">10</part-num-ref>
|
| 469 |
+
shown in FIG<confidence value="5">s</confidence>
|
| 470 |
+
. 1 and <part-num-ref name="and">2</part-num-ref>
|
| 471 |
+
is a mobile telephone. Features of the electronic device <part-num-ref name="electronic device">10,</part-num-ref>
|
| 472 |
+
when implemented as a mobile telephone, will be described with additional reference to FIG. 8. The electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 473 |
+
is shown as having a "brick" or "block" form factor housing, but it will be appreciated that <boundary-data type="line-number">15 </boundary-data>
|
| 474 |
+
other housing types may be utilized, such as a "flip-open" form factor (e.g., a "clamshell" housing) or a slide-type form factor (e.g., a "slider" housing). </p>
|
| 475 |
+
<p id="p-79" num="79">As indicated, the electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 476 |
+
may include the display <part-num-ref name="display">24.</part-num-ref>
|
| 477 |
+
The display <part-num-ref name="display">24</part-num-ref>
|
| 478 |
+
displays information to a user such as operating state, time, telephone numbers, contact information, various menus, etc., that enable the user to utilize the various features of the <boundary-data type="line-number">20 </boundary-data>
|
| 479 |
+
electronic device <part-num-ref name="electronic device">10.</part-num-ref>
|
| 480 |
+
The display <part-num-ref name="display">24</part-num-ref>
|
| 481 |
+
also may be used to visually display content received by the electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 482 |
+
and/or retrieved from a memory <part-num-ref name="memory">56</part-num-ref>
|
| 483 |
+
of the electronic device <part-num-ref name="electronic device">10.</part-num-ref>
|
| 484 |
+
</p>
|
| 485 |
+
<p id="p-80" num="80">The display 24 may be used to present images, video and other graphics to the user, such as photographs, mobile television content and video associated with games.</p>
|
| 486 |
+
<p id="p-81" num="81">The keypad 26 and/or buttons <part-num-ref name="and/or buttons">28</part-num-ref>
|
| 487 |
+
may provide for a variety of user input <boundary-data type="line-number">25 </boundary-data>
|
| 488 |
+
operations. For example, the keypad <part-num-ref name="keypad">26</part-num-ref>
|
| 489 |
+
may include alphanumeric keys for allowing entry of alphanumeric information such as telephone numbers, phone lists, contact information, notes, text, etc. In addition, the keypad <part-num-ref name="keypad">26</part-num-ref>
|
| 490 |
+
and/or buttons <part-num-ref name="and/or buttons">28</part-num-ref>
|
| 491 |
+
may include special function keys such as a "call send" key for initiating or answering a call, and a "call end" key for ending or "hanging up" a call. Special function keys also may include <part-num-ref name="call. Special function keys also may include">30</part-num-ref>
|
| 492 |
+
menu navigation and select keys to facilitate navigating through a menu displayed on the <boundary-data type="header">
|
| 493 |
+
<confidence value="88">18</confidence>
|
| 494 |
+
</boundary-data>
|
| 495 |
+
<page-break num="19"/>
|
| 496 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 497 |
+
display <part-num-ref name="display">24.</part-num-ref>
|
| 498 |
+
For instance, a pointing device and/or navigation keys may be present to accept directional inputs from a user. Special function keys may include audiovisual content playback keys to start, stop and pause playback, skip or repeat tracks, and so forth. </p>
|
| 499 |
+
<p id="p-82" num="82">Other keys associated with the mobile telephone may include a volume key, an audio mute <boundary-data type="line-number">5 </boundary-data>
|
| 500 |
+
key, an <confidence value="222222">on/off</confidence>
|
| 501 |
+
power key, a web browser launch key, etc. Keys or key-like functionality also may be embodied as a touch screen associated with the display <part-num-ref name="display">24.</part-num-ref>
|
| 502 |
+
Also, the display <part-num-ref name="display">24</part-num-ref>
|
| 503 |
+
and keypad <part-num-ref name="and keypad">26</part-num-ref>
|
| 504 |
+
and/or buttons <part-num-ref name="and/or buttons">28</part-num-ref>
|
| 505 |
+
may be used in conjunction with one another to implement soft key functionality. As such, the display <part-num-ref name="display">24,</part-num-ref>
|
| 506 |
+
the keypad <part-num-ref name="keypad">26</part-num-ref>
|
| 507 |
+
and/or the buttons <part-num-ref name="buttons">28</part-num-ref>
|
| 508 |
+
may be used to control the camera assembly <part-num-ref name="camera assembly">12.</part-num-ref>
|
| 509 |
+
</p>
|
| 510 |
+
<p id="p-83" num="83">
|
| 511 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 512 |
+
The electronic device 10 may include call circuitry that enables the electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 513 |
+
to establish a call and/or exchange signals with a called/calling device, which typically may be another mobile telephone or landline telephone. However, the called/calling device need not be another telephone, but may be some other device such as an Internet web server, content providing server, etc. Calls may take any suitable form. </p>
|
| 514 |
+
<p id="p-84" num="84">
|
| 515 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 516 |
+
For example, the call could be a conventional call that is established over a cellular circuit- switched network or a voice over Internet Protocol (VoIP) call that is established over a packet-switched capability of a cellular network or over an alternative packet-switched network, such as WiFi (e.g., a network based on the IEEE 802.11 standard), WiMax (e.g., a network based on the IEEE 802.16 standard), etc. Another example includes a video <boundary-data type="line-number">20 </boundary-data>
|
| 517 |
+
enabled call that is established over a cellular or alternative network. </p>
|
| 518 |
+
<p id="p-85" num="85">The electronic device 10 may be configured to transmit, receive and/or process data, such as text messages, instant messages, electronic mail messages, multimedia messages, image files, video files, audio files, ring tones, streaming audio, streaming video, data feeds (including podcasts and really simple syndication (RSS) data feeds), and <boundary-data type="line-number">25 </boundary-data>
|
| 519 |
+
<confidence value="66">so</confidence>
|
| 520 |
+
forth. It is noted that a text message is commonly referred to by some as "an SMS," which stands for simple message service. SMS is a typical standard for exchanging text messages. Similarly, a multimedia message is commonly referred to by some as "an MMS," which stands for multimedia message service. MMS is a typical standard for exchanging multimedia messages. Processing data may include storing the data in the <part-num-ref name="">30</part-num-ref>
|
| 521 |
+
memory <part-num-ref name="memory">56,</part-num-ref>
|
| 522 |
+
executing applications to allow user interaction with the data, displaying <boundary-data type="header">
|
| 523 |
+
<confidence value="88">19</confidence>
|
| 524 |
+
</boundary-data>
|
| 525 |
+
<page-break num="20"/>
|
| 526 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 527 |
+
video and/or image content associated with the data, outputting audio sounds associated with the data, and so forth. </p>
|
| 528 |
+
<p id="p-86" num="86">The electronic device 10 may include a primary control circuit <part-num-ref name="primary control circuit">58</part-num-ref>
|
| 529 |
+
that is configured to carry out overall control of the functions and operations of the electronic <boundary-data type="line-number">5 </boundary-data>
|
| 530 |
+
device <part-num-ref name="electronic device">10.</part-num-ref>
|
| 531 |
+
The control circuit <part-num-ref name="control circuit">58</part-num-ref>
|
| 532 |
+
may be responsible for controlling the camera assembly <part-num-ref name="camera assembly">12,</part-num-ref>
|
| 533 |
+
including the tasks of the encoder <part-num-ref name="encoder">30.</part-num-ref>
|
| 534 |
+
Alternatively, the encoder <part-num-ref name="encoder">30</part-num-ref>
|
| 535 |
+
may be embodied by a separate controller (not shown) of the camera assembly <part-num-ref name="camera assembly">12.</part-num-ref>
|
| 536 |
+
</p>
|
| 537 |
+
<p id="p-87" num="87">The control circuit 58 may include a processing device <part-num-ref name="processing device">60,</part-num-ref>
|
| 538 |
+
such as a central processing unit (CPU), microcontroller or microprocessor. The processing device <part-num-ref name="processing device">60</part-num-ref>
|
| 539 |
+
may <boundary-data type="line-number">10 </boundary-data>
|
| 540 |
+
execute code that implements the various functions of the electronic device <part-num-ref name="electronic device">10.</part-num-ref>
|
| 541 |
+
The code may be stored in a memory (not shown) within the control circuit <part-num-ref name="control circuit">58</part-num-ref>
|
| 542 |
+
and/or in a separate memory, such as the memory <part-num-ref name="memory">56,</part-num-ref>
|
| 543 |
+
in order to carry out operation of the electronic device <part-num-ref name="electronic device">10.</part-num-ref>
|
| 544 |
+
It will be apparent to a person having ordinary skill in the art of computer programming, and specifically in application programming for mobile telephones or other <boundary-data type="line-number">15 </boundary-data>
|
| 545 |
+
electronic devices, how to program a electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 546 |
+
to operate and carry out various logical functions. </p>
|
| 547 |
+
<p id="p-88" num="88">Among other data storage responsibilities, the memory <part-num-ref name="memory">56</part-num-ref>
|
| 548 |
+
may be used to store photographs and/or video clips that are captured by the camera assembly <part-num-ref name="camera assembly">12.</part-num-ref>
|
| 549 |
+
</p>
|
| 550 |
+
<p id="p-89" num="89">Alternatively, the images may be stored in a separate memory. The memory <part-num-ref name="memory">56</part-num-ref>
|
| 551 |
+
may be, <boundary-data type="line-number">20 </boundary-data>
|
| 552 |
+
for example, one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, a random access memory (RAM), or other suitable device. In a typical arrangement, the memory <part-num-ref name="memory">56</part-num-ref>
|
| 553 |
+
may include a non-volatile memory (e.g., a NAND or NOR architecture flash memory) for long term data storage and a volatile memory that functions as system memory for the control circuit <part-num-ref name="control circuit">58.</part-num-ref>
|
| 554 |
+
The volatile <boundary-data type="line-number">25 </boundary-data>
|
| 555 |
+
memory may be a RAM implemented with synchronous dynamic random access memory (SDRAM), for example. The memory <part-num-ref name="memory">56</part-num-ref>
|
| 556 |
+
may exchange data with the control circuit <part-num-ref name="control circuit">58</part-num-ref>
|
| 557 |
+
over a data bus. Accompanying control lines and an address bus between the memory <part-num-ref name="memory">56</part-num-ref>
|
| 558 |
+
and the control circuit <part-num-ref name="control circuit">58</part-num-ref>
|
| 559 |
+
also may be present. </p>
|
| 560 |
+
<p id="p-90" num="90">Continuing to refer to FIG<confidence value="5">s</confidence>
|
| 561 |
+
. 1, 2, and 8, the electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 562 |
+
includes an <part-num-ref name="">30</part-num-ref>
|
| 563 |
+
antenna <part-num-ref name="antenna">62</part-num-ref>
|
| 564 |
+
coupled to a radio circuit <part-num-ref name="radio circuit">64.</part-num-ref>
|
| 565 |
+
The radio circuit <part-num-ref name="radio circuit">64</part-num-ref>
|
| 566 |
+
includes a radio frequency <boundary-data type="header">
|
| 567 |
+
<confidence value="88">20</confidence>
|
| 568 |
+
</boundary-data>
|
| 569 |
+
<page-break num="21"/>
|
| 570 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 571 |
+
transmitter and receiver for transmitting and receiving signals via the antenna <part-num-ref name="antenna">62.</part-num-ref>
|
| 572 |
+
The radio circuit <part-num-ref name="radio circuit">64</part-num-ref>
|
| 573 |
+
may be configured to operate in a mobile communications system and may be used to send and receive data and/or audiovisual content. Receiver types for interaction with a mobile radio network and/or broadcasting network include, but are not limited to, <boundary-data type="line-number">5 </boundary-data>
|
| 574 |
+
global system for mobile communications (GSM), code division multiple access (CDMA), wideband CDMA (WCDMA), general packet radio service (GPRS), WiFi, WiMax, digital video broadcasting-handheld (DVB-H), integrated services digital broadcasting (ISDB), etc., as well as advanced versions of these standards. It will be appreciated that the antenna <part-num-ref name="antenna">62</part-num-ref>
|
| 575 |
+
and the radio circuit <part-num-ref name="radio circuit">64</part-num-ref>
|
| 576 |
+
may represent one or more than one radio transceivers. </p>
|
| 577 |
+
<p id="p-91" num="91">
|
| 578 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 579 |
+
The electronic device 10 further includes a sound signal processing circuit <part-num-ref name="sound signal processing circuit">66</part-num-ref>
|
| 580 |
+
for processing audio signals transmitted by and received from the radio circuit <part-num-ref name="radio circuit">64.</part-num-ref>
|
| 581 |
+
Coupled to the sound processing circuit <part-num-ref name="sound processing circuit">66</part-num-ref>
|
| 582 |
+
are a speaker <part-num-ref name="speaker">68</part-num-ref>
|
| 583 |
+
and a microphone <part-num-ref name="microphone">70</part-num-ref>
|
| 584 |
+
that enable a user to listen and speak via the electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 585 |
+
as is conventional. The radio circuit <part-num-ref name="radio circuit">64</part-num-ref>
|
| 586 |
+
and sound processing circuit <part-num-ref name="and sound processing circuit">66</part-num-ref>
|
| 587 |
+
are each coupled to the control circuit <part-num-ref name="control circuit">58</part-num-ref>
|
| 588 |
+
so as to carry out <boundary-data type="line-number">15 </boundary-data>
|
| 589 |
+
overall operation. Audio data may be passed from the control circuit <part-num-ref name="control circuit">58</part-num-ref>
|
| 590 |
+
to the sound signal processing circuit <part-num-ref name="sound signal processing circuit">66</part-num-ref>
|
| 591 |
+
for playback to the user. The audio data may include, for example, audio data from an audio file stored by the memory <part-num-ref name="memory">56</part-num-ref>
|
| 592 |
+
and retrieved by the control circuit <part-num-ref name="control circuit">58,</part-num-ref>
|
| 593 |
+
or received audio data such as in the form of streaming audio data from a mobile radio service. The sound processing circuit <part-num-ref name="sound processing circuit">66</part-num-ref>
|
| 594 |
+
may include any appropriate <boundary-data type="line-number">20 </boundary-data>
|
| 595 |
+
buffers, decoders, amplifiers and so forth. </p>
|
| 596 |
+
<p id="p-92" num="92">The display 24 may be coupled to the control circuit <part-num-ref name="control circuit">58</part-num-ref>
|
| 597 |
+
by a video processing circuit <part-num-ref name="video processing circuit">72</part-num-ref>
|
| 598 |
+
that converts video data to a video signal used to drive the display <part-num-ref name="display">24.</part-num-ref>
|
| 599 |
+
The video processing circuit <part-num-ref name="video processing circuit">72</part-num-ref>
|
| 600 |
+
may include any appropriate buffers, decoders, video data processors and so forth. The video data may be generated by the control circuit <part-num-ref name="control circuit">58,</part-num-ref>
|
| 601 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 602 |
+
retrieved from a video file that is stored in the memory <part-num-ref name="memory">56,</part-num-ref>
|
| 603 |
+
derived from an incoming video data stream that is received by the radio circuit <part-num-ref name="radio circuit">64</part-num-ref>
|
| 604 |
+
or obtained by any other suitable method. Also, the video data may be generated by the camera assembly <part-num-ref name="camera assembly">12</part-num-ref>
|
| 605 |
+
and coded by the encoder <part-num-ref name="encoder">30.</part-num-ref>
|
| 606 |
+
</p>
|
| 607 |
+
<p id="p-93" num="93">The electronic device 10 may further include one or more I/O interface(s) <part-num-ref name="may further include one or more I/O interface(s)">74.</part-num-ref>
|
| 608 |
+
The <boundary-data type="line-number">30 </boundary-data>
|
| 609 |
+
I/O interface(s) <part-num-ref name="I/O interface(s)">74</part-num-ref>
|
| 610 |
+
may be in the form of typical mobile telephone I/O interfaces and may include one or more electrical connectors. As is typical, the I/O interface(s) <part-num-ref name="I/O interface(s)">74</part-num-ref>
|
| 611 |
+
may be <boundary-data type="header">
|
| 612 |
+
<confidence value="88">21</confidence>
|
| 613 |
+
</boundary-data>
|
| 614 |
+
<page-break num="22"/>
|
| 615 |
+
<boundary-data type="header">DOCKET NO: PU07 0439US2</boundary-data>
|
| 616 |
+
used to couple the electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 617 |
+
to a battery charger to charge a battery of a power supply unit (PSU) <part-num-ref name="power supply unit (PSU)">76</part-num-ref>
|
| 618 |
+
within the electronic device <part-num-ref name="electronic device">10.</part-num-ref>
|
| 619 |
+
In addition, or in the alternative, the I/O interface(s) <part-num-ref name="I/O interface(s)">74</part-num-ref>
|
| 620 |
+
may serve to connect the electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 621 |
+
to a headset assembly (e.g., a personal handsfree (PHF) device) that has a wired interface with the electronic <boundary-data type="line-number">5 </boundary-data>
|
| 622 |
+
device <part-num-ref name="electronic device">10.</part-num-ref>
|
| 623 |
+
Further, the I/O interface(s) <part-num-ref name="I/O interface(s)">74</part-num-ref>
|
| 624 |
+
may serve to connect the electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 625 |
+
to a personal computer or other device via a data cable for the exchange of data. The electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 626 |
+
may receive operating power via the I/O interface(s) <part-num-ref name="I/O interface(s)">74</part-num-ref>
|
| 627 |
+
when connected to a vehicle power adapter or an electricity outlet power adapter. The PSU <part-num-ref name="PSU">76</part-num-ref>
|
| 628 |
+
may supply power to operate the electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 629 |
+
in the absence of an external power <boundary-data type="line-number">10 </boundary-data>
|
| 630 |
+
source. </p>
|
| 631 |
+
<p id="p-94" num="94">The electronic device 10 also may include a system clock <part-num-ref name="system clock">78</part-num-ref>
|
| 632 |
+
for clocking the various components of the electronic device <part-num-ref name="electronic device">10,</part-num-ref>
|
| 633 |
+
such as the control circuit <part-num-ref name="control circuit">58</part-num-ref>
|
| 634 |
+
and the memory <part-num-ref name="memory">56.</part-num-ref>
|
| 635 |
+
</p>
|
| 636 |
+
<p id="p-95" num="95">The electronic device 10 also may include a position data receiver <part-num-ref name="position data receiver">80,</part-num-ref>
|
| 637 |
+
such as a <boundary-data type="line-number">15 </boundary-data>
|
| 638 |
+
global positioning system (GPS) receiver, Galileo satellite system receiver or the like. </p>
|
| 639 |
+
<p id="p-96" num="96">The position data receiver 80 may be involved in determining the location of the electronic device <part-num-ref name="electronic device">10.</part-num-ref>
|
| 640 |
+
</p>
|
| 641 |
+
<p id="p-97" num="97">The electronic device 10 also may include a local wireless interface <part-num-ref name="local wireless interface">82,</part-num-ref>
|
| 642 |
+
such as an infrared transceiver and/or an RF interface (e.g., a Bluetooth interface), for establishing <boundary-data type="line-number">20 </boundary-data>
|
| 643 |
+
communication with an accessory, another mobile radio terminal, a computer or another device. For example, the local wireless interface <part-num-ref name="local wireless interface">82</part-num-ref>
|
| 644 |
+
may operatively couple the electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 645 |
+
to a headset assembly (e.g., a PHF device) in an embodiment where the headset assembly has a corresponding wireless interface. </p>
|
| 646 |
+
<p id="p-98" num="98">With additional reference to FIG. 9, the electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 647 |
+
may be configured to <boundary-data type="line-number">25 </boundary-data>
|
| 648 |
+
operate as part of a communications system <part-num-ref name="communications system">84.</part-num-ref>
|
| 649 |
+
The system <part-num-ref name="system">84</part-num-ref>
|
| 650 |
+
may include a communications network <part-num-ref name="communications network">86</part-num-ref>
|
| 651 |
+
having a server <part-num-ref name="server">88</part-num-ref>
|
| 652 |
+
(or servers) for managing calls placed by and destined to the electronic device <part-num-ref name="electronic device">10,</part-num-ref>
|
| 653 |
+
transmitting data to the electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 654 |
+
and carrying out any other support functions. The server <part-num-ref name="server">88</part-num-ref>
|
| 655 |
+
communicates with the electronic device <part-num-ref name="electronic device">10</part-num-ref>
|
| 656 |
+
via a transmission medium. The transmission medium may be any appropriate <part-num-ref name="transmission medium may be any appropriate">30</part-num-ref>
|
| 657 |
+
device or assembly, including, for example, a communications tower (e.g., a cell tower), <boundary-data type="header">
|
| 658 |
+
<confidence value="88">22</confidence>
|
| 659 |
+
</boundary-data>
|
| 660 |
+
<page-break num="23"/>
|
| 661 |
+
<boundary-data type="header">DOCKET NO: PU<confidence value="4">0</confidence>
|
| 662 |
+
7 0439US2 </boundary-data>
|
| 663 |
+
another mobile telephone, a wireless access point, a satellite, etc. Portions of the network may include wireless transmission pathways. The network <part-num-ref name="network">86</part-num-ref>
|
| 664 |
+
may support the communications activity of multiple electronic devices <part-num-ref name="communications activity of multiple electronic devices">10</part-num-ref>
|
| 665 |
+
and other types of end user devices. As will be appreciated, the server <part-num-ref name="server">88</part-num-ref>
|
| 666 |
+
may be configured as a typical computer <boundary-data type="line-number">5 </boundary-data>
|
| 667 |
+
system used to carry out server functions and may include a processor configured to execute software containing logical instructions that embody the functions of the server <part-num-ref name="server">88</part-num-ref>
|
| 668 |
+
and a memory to store such software. </p>
|
| 669 |
+
<p id="p-99" num="99">Although certain embodiments have been shown and described, it is understood that equivalents and modifications falling within the scope of the appended claims will <boundary-data type="line-number">10 </boundary-data>
|
| 670 |
+
occur to others who are skilled in the art upon the reading and understanding of this specification. </p>
|
| 671 |
+
<boundary-data type="header">
|
| 672 |
+
<confidence value="88">23</confidence>
|
| 673 |
+
</boundary-data>
|
| 674 |
+
</description>
|
| 675 |
+
</us-patent-application>
|
| 676 |
+
|
applicant/11925811.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
applicant/11956403.xml
ADDED
|
@@ -0,0 +1,307 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11956403</doc-number>
|
| 8 |
+
<date>2007-12-14</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">PRIORITIZED INCREMENTAL ASYNCHRONOUS MACHINE</heading>
|
| 14 |
+
<heading id="h-2">TRANSLATION OF STRUCTURED DOCUMENTS</heading>
|
| 15 |
+
<p id="p-1" num="1">Field of the Invention <boundary-data type="line-number">5 </boundary-data>
|
| 16 |
+
The present invention relates generally to electrical, electronic and computer arts, and, more particularly, to techniques for presenting translated text in a structured document. </p>
|
| 17 |
+
<p id="p-2" num="2">Back<confidence value="8">g</confidence>
|
| 18 |
+
round of the Invention <boundary-data type="line-number">10 </boundary-data>
|
| 19 |
+
The internet continues to expand rapidly and internet users, worldwide, are able to browse the web faster than ever before. However, regardless of how quickly an internet user can access the web, language barriers continue to prevent the efficient dissemination of information. </p>
|
| 20 |
+
<p id="p-3" num="3">The internet has attempted to address language issues by offering machine <boundary-data type="line-number">15 </boundary-data>
|
| 21 |
+
translation systems which translate a variety of input languages. However, these systems can be slow and inefficient. First, in conventional translation systems, an untranslated HyperText Markup Language (HTML) page is sent to a machine translation system that renders a translated page only after the page has been completely translated into a target language chosen by the user. This method is inefficient because it forces users to wait <boundary-data type="line-number">20 </boundary-data>
|
| 22 |
+
until translation of the entire page or pages has been completed. Many Internet users prefer skimming web pages for relevance prior to committed reading; thus, there may be instances wherein translation of the entire page is unnecessary and undesirable. </p>
|
| 23 |
+
<p id="p-4" num="4">Next, conventional techniques fail to address the limiting inverse relationship between translation time and translation quality. Machine translation systems, regardless <boundary-data type="line-number">25 </boundary-data>
|
| 24 |
+
of the underlying technology used (e.g., rule-based or statistical model-based), usually trade off between translation time and quality. Generally speaking, a translation system can provide better quality translations given more time, more rules, or a more extensive statistical model. Conventional translation systems do not operate around this inherent <boundary-data type="header">
|
| 25 |
+
<confidence value="86">YO</confidence>
|
| 26 |
+
R920070592U<confidence value="58">S1</confidence>
|
| 27 |
+
<confidence value="5">1</confidence>
|
| 28 |
+
</boundary-data>
|
| 29 |
+
<page-break num="2"/>
|
| 30 |
+
limitation. Rather, current systems simply choose a static operating point and either sacrifice speed for quality or quality for speed. </p>
|
| 31 |
+
<p id="p-5" num="5">Finally, conventional translation techniques do not apply an organized translation strategy. Current techniques indiscriminately translate web pages from start to finish.</p>
|
| 32 |
+
<p id="p-6" num="6">
|
| 33 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 34 |
+
This is impractical for two reasons. First, a user may not want to wait for a complete translation of a web page. Rather, a user may want to see key words translated first. </p>
|
| 35 |
+
<p id="p-7" num="7">Secondly, sections of text within a structured document differ in terms of usefulness to the user. For example, navigation menus in a web page tend to relay key pieces of information in short spans of text. At the same time, large spans of text may include <boundary-data type="line-number">10 </boundary-data>
|
| 36 |
+
buried pieces of key information. Therefore, the indiscriminate, rapid translation of entire web pages lacks efficiency and only acts to decrease the overall quality of translations. </p>
|
| 37 |
+
<p id="p-8" num="8">Accordingly, there exists a need for techniques for more efficiently translating and presenting text in a structured document which does not suffer from one or more <boundary-data type="line-number">15 </boundary-data>
|
| 38 |
+
problems found in conventional translation techniques. </p>
|
| 39 |
+
<p id="p-9" num="9">Summary of the Invention An illustrative embodiment of the present invention meets the above-noted needs by providing techniques for efficiently translating text in a structured document. These <boundary-data type="line-number">20 </boundary-data>
|
| 40 |
+
techniques offer several advantages over conventional methodologies, including: (i) presenting partial translations of text immediately when available; (ii) overcoming the processing limitation of translation time versus translation quality by making multiple simultaneous translation requests to multiple translation servers of differing speeds and quality; and (iii) prioritizing the order in which text is translated to maximize translation <boundary-data type="line-number">25 </boundary-data>
|
| 41 |
+
speed and translation effectiveness. </p>
|
| 42 |
+
<p id="p-10" num="10">In a first aspect of the invention, a method for presenting translated text in a structured document is provided. A structured document including text to be translated is received. At least one portion of the text to be translated is translated into at least one <boundary-data type="header">
|
| 43 |
+
<confidence value="86">YO</confidence>
|
| 44 |
+
R920070592US<confidence value="4">1</confidence>
|
| 45 |
+
<confidence value="8">2</confidence>
|
| 46 |
+
</boundary-data>
|
| 47 |
+
<page-break num="3"/>
|
| 48 |
+
representation of translated text of a specific language. The translation is carried out in accordance with a prioritization schedule. Further, the representation of translated text is provided by at least first and second servers, the first server independently providing the representation of translated text of a first quality and the second server independently <boundary-data type="line-number">5 </boundary-data>
|
| 49 |
+
providing the representation of translated text of a second quality, the first quality being different than the second quality. As the text is translated, the representation of translated text is presented immediately when available. In one embodiment of the present invention, the progress of translation is outputted. </p>
|
| 50 |
+
<p id="p-11" num="11">The representation of translated text may also be provided by a third server. The <boundary-data type="line-number">10 </boundary-data>
|
| 51 |
+
third server independently provides the at least one representation of translated text of a third quality, the third quality being different than the first quality and the second quality. </p>
|
| 52 |
+
<p id="p-12" num="12">More translation servers can be added in similar fashion.</p>
|
| 53 |
+
<p id="p-13" num="13">In accordance with one embodiment of the present invention, the step of translating may comprise prioritizing the at least one portion of the text to be translated <boundary-data type="line-number">15 </boundary-data>
|
| 54 |
+
according to at least one characteristic of the text including at least one of length, composition, natural order, syntax, visual prominence, and structural tags of the text. The step of prioritizing may further comprise inserting JavaScript code into the at least one portion of the text to be translated. Additionally, the step of translating may also comprise sending a translation request to one or multiple translation servers in parallel. </p>
|
| 55 |
+
<p id="p-14" num="14">
|
| 56 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 57 |
+
In accordance with an additional embodiment of the present invention, the step of presenting may comprise replacing the at least one representation of translated text of the first quality with the at least one representation of translated text of the second quality, the second quality being higher than the first quality. The at least one representation of translated text of the first quality and the at least one representation of translated text of <boundary-data type="line-number">25 </boundary-data>
|
| 58 |
+
the second quality may be distinguished by at least one of color, font, or another visual cue. </p>
|
| 59 |
+
<p id="p-15" num="15">The step of presenting may also be performed by at least one of visually and audibly. Further, the step of presenting may comprise <confidence value="2222222222">outputting</confidence>
|
| 60 |
+
the at least one <boundary-data type="header">
|
| 61 |
+
<confidence value="86">YO</confidence>
|
| 62 |
+
R920070592US<confidence value="4">1</confidence>
|
| 63 |
+
<confidence value="8">3</confidence>
|
| 64 |
+
</boundary-data>
|
| 65 |
+
<page-break num="4"/>
|
| 66 |
+
representation of translated text by mousing over the at least one portion of the text to be translated. Also, the step of presenting may comprise outputting the structured document and the at least one representation of translated text side-by-side. </p>
|
| 67 |
+
<p id="p-16" num="16">In a second aspect of the invention, an apparatus for presenting translated text in a <boundary-data type="line-number">5 </boundary-data>
|
| 68 |
+
structured document comprises a memory, and at least one processor coupled to the memory. The at least one processor being operative: (i) to receive the structured document including text to be translated; (ii) to translate to a specific language at least one portion of the text to be translated into at least one representation of translated text in accordance with a prioritization schedule, wherein the at least one representation of <boundary-data type="line-number">10 </boundary-data>
|
| 69 |
+
translated text is provided by at least first and second servers, the first server independently providing the at least one representation of translated text of a first quality and the second server independently providing the at least one representation of translated text of a second quality, the first quality being different than the second quality; and (iii) to present the at least one representation of translated text immediately <boundary-data type="line-number">15 </boundary-data>
|
| 70 |
+
when available. </p>
|
| 71 |
+
<p id="p-17" num="17">In a third aspect of the invention, an article of manufacture for presenting translated text in a structured document comprises a computer readable storage medium containing one or more computer programs, which when executed implement the steps <confidence value="885">of:</confidence>
|
| 72 |
+
(i) receiving the structured document including text to be translated; (ii) translating to <boundary-data type="line-number">20 </boundary-data>
|
| 73 |
+
a specific language at least one portion of the text to be translated into at least one representation of translated text in accordance with a prioritization schedule, wherein the at least one representation of translated text is provided by at least first and second servers, the first server independently providing the at least one representation of translated text of a first quality and the second server independently providing the at least <boundary-data type="line-number">25 </boundary-data>
|
| 74 |
+
one representation of translated text of a second quality, the first quality being different than the second quality; and (iii) presenting the at least one representation of translated text immediately when available. </p>
|
| 75 |
+
<boundary-data type="header">
|
| 76 |
+
<confidence value="86">YO</confidence>
|
| 77 |
+
R920070592US1 4 </boundary-data>
|
| 78 |
+
<p id="p-18" num="18">
|
| 79 |
+
<page-break num="5"/>
|
| 80 |
+
In a fourth aspect of the invention, a system for presenting translated text in a structured document is provided. The system comprises a first server, at least a second server, and at least one processor operatively coupled to the first and at least second servers. The at least one processor being operative: (i) to receive the structured document <boundary-data type="line-number">5 </boundary-data>
|
| 81 |
+
including text to be translated; (ii) to translate to a specific language at least one portion of the text to be translated into at least one representation of translated text in accordance with a prioritization schedule, wherein the at least one representation of translated text is provided by at least first and second servers, the first server independently providing the at least one representation of translated text of a first quality and the second server <boundary-data type="line-number">10 </boundary-data>
|
| 82 |
+
independently providing the at least one representation of translated text of a second quality, the first quality being different than the second quality; and (iii) to present the at least one representation of translated text immediately when available. </p>
|
| 83 |
+
<p id="p-19" num="19">These and other objects, features, and advantages of the present invention will become apparent from the following detailed description of illustrative embodiments <boundary-data type="line-number">15 </boundary-data>
|
| 84 |
+
thereof, which is to be read in connection with the accompanying drawings. </p>
|
| 85 |
+
<p id="p-20" num="20">Brief Description of the Drawings FIG. 1 is a flow diagram illustrating an exemplary methodology for presenting translated text in a structured document, in accordance with an embodiment of the present <boundary-data type="line-number">20 </boundary-data>
|
| 86 |
+
invention. </p>
|
| 87 |
+
<p id="p-21" num="21">FIG. 2 is a block diagram illustrating a system for implementing the methodology of FIG. 1, in accordance with an embodiment of the present invention.</p>
|
| 88 |
+
<p id="p-22" num="22">FIG. 3 is a diagram illustrating an exemplary user interface for a translation system, in accordance with an embodiment of the present invention.</p>
|
| 89 |
+
<p id="p-23" num="23">
|
| 90 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 91 |
+
FIG. 4 is an illustrative user interface depicting a partially translated structured document, in accordance with an embodiment of the present invention. </p>
|
| 92 |
+
<boundary-data type="header">
|
| 93 |
+
<confidence value="86">YO</confidence>
|
| 94 |
+
R920070592US<confidence value="5">1</confidence>
|
| 95 |
+
<confidence value="8">5</confidence>
|
| 96 |
+
</boundary-data>
|
| 97 |
+
<p id="p-24" num="24">
|
| 98 |
+
<page-break num="6"/>
|
| 99 |
+
FIG. 5 is an illustrative user interface implemented as a web page which incorporates a feature, referred to herein as a "tooltip" option, in accordance with an embodiment of the present invention. </p>
|
| 100 |
+
<p id="p-25" num="25">FIG. 6 is an illustrative user interface depicting, side-by-side, untranslated and <boundary-data type="line-number">5 </boundary-data>
|
| 101 |
+
translated text of a structured document, in accordance with an embodiment of the present invention. </p>
|
| 102 |
+
<p id="p-26" num="26">FIG. 7 is a block diagram illustrating an exemplary hardware implementation of a computing system in which one or more components/methodologies of the invention may be implemented, in accordance with an embodiment of the present invention.</p>
|
| 103 |
+
<p id="p-27" num="27">
|
| 104 |
+
<boundary-data type="line-number">
|
| 105 |
+
<confidence value="88">10</confidence>
|
| 106 |
+
</boundary-data>
|
| 107 |
+
Detailed Description of the Invention The present invention will be described in the context of illustrative embodiments of an exemplary web page translation system comprising multiple translation servers of differing speed and quality. It should be understood, however, that the invention is not <boundary-data type="line-number">15 </boundary-data>
|
| 108 |
+
limited to use with any particular translation system or web page. Rather, the invention is generally applicable to any translation technique that presents prioritized, incremental, and asynchronous machine translations of structured documents. </p>
|
| 109 |
+
<p id="p-28" num="28">The term "browser client" as used herein is intended to be construed broadly so as to encompass, by way of example and without limitation, any client used to browse the <boundary-data type="line-number">20 </boundary-data>
|
| 110 |
+
internet. Examples of browser clients include, Internet Explorer<confidence value="2">®</confidence>
|
| 111 |
+
(a registered trademark of Microsoft Corporation) and Mozilla FireFox<confidence value="2">*</confidence>
|
| 112 |
+
(a registered trademark of Mozilla Foundation). </p>
|
| 113 |
+
<p id="p-29" num="29">The term "translation server" as used herein is intended to be constructed broadly so as to compass, by way of example and without limitation, any translation engine that <boundary-data type="line-number">25 </boundary-data>
|
| 114 |
+
can receive a text string in source language and return a text string in the target language. </p>
|
| 115 |
+
<p id="p-30" num="30">Examples of translation servers include, but are not limited to, translation software products from IBM, Systran, etc. It should be noted that the method described in this application can use any existing translation servers without modification.</p>
|
| 116 |
+
<boundary-data type="header">
|
| 117 |
+
<confidence value="86">YO</confidence>
|
| 118 |
+
R920<confidence value="5">0</confidence>
|
| 119 |
+
70592US<confidence value="4">1</confidence>
|
| 120 |
+
<confidence value="8">6</confidence>
|
| 121 |
+
</boundary-data>
|
| 122 |
+
<p id="p-31" num="31">
|
| 123 |
+
<page-break num="7"/>
|
| 124 |
+
The term "mousing over" as used herein is intended to be construed broadly so as to encompass, by way of example and without limitation, a user interface technique of placing a cursor over a portion of graphical output to trigger additional graphical output. </p>
|
| 125 |
+
<p id="p-32" num="32">The term "structured document" as used herein is intended to be construed <boundary-data type="line-number">5 </boundary-data>
|
| 126 |
+
broadly so as to encompass, by way of example and without limitation, any text that is structured. An HTML web page is one type of structured document. It should be understood that embodiments of this invention do not mandate how the document structure is generated, it simply assumes that a structured document is available as input and the structure is known. </p>
|
| 127 |
+
<p id="p-33" num="33">
|
| 128 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 129 |
+
Referring initially to FIG. 1, a flow diagram illustrates an exemplary methodology <part-num-ref name="exemplary methodology">100</part-num-ref>
|
| 130 |
+
for presenting translated text in a structured document, in accordance with an embodiment of the present invention. Methodology <part-num-ref name="present invention. Methodology">100</part-num-ref>
|
| 131 |
+
begins at step <part-num-ref name="begins at step">102</part-num-ref>
|
| 132 |
+
where a structured document containing text to be translated is received. In an illustrative embodiment, a user via a browser client (e.g., a modified translation web browser) <boundary-data type="line-number">15 </boundary-data>
|
| 133 |
+
requests that a particular web document (e.g., web page) be translated. The request is directed to an application server. Upon receiving the request, the application server, acting as a proxy, retrieves the web page, inserts necessary customized JavaScript<confidence value="2">*</confidence>
|
| 134 |
+
(a registered trademark of Sun Microsystems, Inc.) code, and feeds the modified page back to the browser client. </p>
|
| 135 |
+
<p id="p-34" num="34">
|
| 136 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 137 |
+
At step 104, the text of the web page is translated to a specific language designated by the user. Initially, the web page is rendered by the browser client, at which point all text is in the original source language. In an illustrative embodiment, the browser client utilizes the structural information of the document, or some alternative criteria, to partition the text of the document into translation units. The translation units <boundary-data type="line-number">25 </boundary-data>
|
| 138 |
+
are ordered according to level of importance, as may be specified by the user, and organized in the form of a prioritization schedule <part-num-ref name="prioritization schedule">106.</part-num-ref>
|
| 139 |
+
In an additional embodiment, the ordered translation units are placed in a prioritization queue. </p>
|
| 140 |
+
<boundary-data type="header">
|
| 141 |
+
<confidence value="86">YO</confidence>
|
| 142 |
+
R920070592US1 7 </boundary-data>
|
| 143 |
+
<p id="p-35" num="35">
|
| 144 |
+
<page-break num="8"/>
|
| 145 |
+
Prioritizing the translation of text maximizes efficiency in two ways. First, server usage is reduced. Since text is translated in the order of importance, users may terminate a translation prior to completion of the translation if a user decides that a complete translation is unnecessary. Second, internet users can save time and browse the web <boundary-data type="line-number">5 </boundary-data>
|
| 146 |
+
more efficiently. For instance, by viewing the most important text first, a user can quickly determine if a complete translation is worth waiting for. If the initial translations return text that is deemed irrelevant by the user, the user can terminate the translation and browse elsewhere. </p>
|
| 147 |
+
<p id="p-36" num="36">There are various ways which may be employed to determine translation priority.</p>
|
| 148 |
+
<p id="p-37" num="37">
|
| 149 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 150 |
+
In one illustrative technique, priority is determined using format-independent strategies. </p>
|
| 151 |
+
<p id="p-38" num="38">This may include, for example, prioritizing according to: (1) length and composition of the translation units (e.g., longer spans of text presumably convey more information and are higher-priority); and <part-num-ref name="longer spans of text presumably convey more information and are higher-priority); and">(2)</part-num-ref>
|
| 152 |
+
the natural order of the translation units (e.g., the order in which text of a web page is presented may represent the order of importance). One <boundary-data type="line-number">15 </boundary-data>
|
| 153 |
+
simple prioritization strategy is to use the natural order of the nodes provided by the document parser/renderer. For visual formats such as HTML, this is usually an adequate strategy since users tend to read the output in the same order. </p>
|
| 154 |
+
<p id="p-39" num="39">In a second illustrative technique, priority is determined using format-specific strategies. This may include, for example, prioritizing according to: <part-num-ref name="second illustrative technique, priority is determined using format-specific strategies. This may include, for example, prioritizing according to:">(1)</part-num-ref>
|
| 155 |
+
visual <boundary-data type="line-number">20 </boundary-data>
|
| 156 |
+
prominence (e.g., text in the center of the screen, large blocks of text, bold faced, etc), which may indicate higher-priority; <part-num-ref name="screen, large blocks of text, bold faced, etc), which may indicate higher-priority;">(2)</part-num-ref>
|
| 157 |
+
lack of visual prominence (e.g., text that is not immediately visible without scrolling, text that is hardly visible, or text that is grayed- out), which may indicate lower-priority; and <part-num-ref name="text that is not immediately visible without scrolling, text that is hardly visible, or text that is grayed- out), which may indicate lower-priority; and">(3)</part-num-ref>
|
| 158 |
+
lack of syntactic str<confidence value="8">u</confidence>
|
| 159 |
+
cture (e.g., a single word), which, depending on location, may or may not indicate higher-priority (e.g., single <boundary-data type="line-number">25 </boundary-data>
|
| 160 |
+
words in a main heading versus single words in a secondary heading). In an additional embodiment, text that lacks syntactic str<confidence value="8">u</confidence>
|
| 161 |
+
cture may be sent to a special-purpose translation engine for processing. </p>
|
| 162 |
+
<boundary-data type="header">
|
| 163 |
+
<confidence value="86">YO</confidence>
|
| 164 |
+
R920070592US<confidence value="6">1</confidence>
|
| 165 |
+
<confidence value="5">8</confidence>
|
| 166 |
+
</boundary-data>
|
| 167 |
+
<p id="p-40" num="40">
|
| 168 |
+
<page-break num="9"/>
|
| 169 |
+
Preferably, priority ultimately determines which translated text an internet user will see first. Many different priority strategies may be developed, some of which were described herein above, and these strategies may be applied to the present invention, either individually or in combination, to maximize translation efficiency. Further, a user <boundary-data type="line-number">5 </boundary-data>
|
| 170 |
+
interface may be implemented to give internet users the ability to select from multiple predefined strategies, or as a means of entering their own prioritization strategy. It should be understood that the invention is not limited to any specific prioritization strategy; rather, the invention assumes such a prioritization strategy (or multiple prioritization strategies), if employed, is available for use. </p>
|
| 171 |
+
<p id="p-41" num="41">
|
| 172 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 173 |
+
Once the text of the web page is partitioned and prioritized, page translation can be initiated. In an illustrative embodiment, a fixed number of translation pipelines, each including a corresponding translation server, are utilized (108-1<confidence value="6">,</confidence>
|
| 174 |
+
<confidence value="8">.</confidence>
|
| 175 |
+
<confidence value="8">.</confidence>
|
| 176 |
+
. 108-N). For each translation unit, multiple asynchronous translation requests may be issued by the browser client to available translation servers that operate at different performance levels (e.g., <boundary-data type="line-number">15 </boundary-data>
|
| 177 |
+
speed and quality levels). It is to be appreciated that the number of servers used for performing the requested translation is not limited by the invention. Increasing the number of servers used in performing the translation may increase the speed and/or quality of the translation. </p>
|
| 178 |
+
<p id="p-42" num="42">The translation servers may be configured such that the fastest translation server <boundary-data type="line-number">20 </boundary-data>
|
| 179 |
+
is the first to return a translation. The first translation may be poor in quality compared to subsequent translations; however, the first translation provides the user with a quick and coarse view of the web page so that the user can more quickly assess the relevance of the content presented by the page. The first translation is preferably replaced, in whole or in part, as subsequent, higher-quality translations from slower servers begin to arrive. </p>
|
| 180 |
+
<p id="p-43" num="43">
|
| 181 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 182 |
+
Ideally, higher-quality translations are not replaced by lower-quality translations. If a user waits long enough, the entire web page will contain translations from the best- quality translation server. If a user is under a time constraint, the user can, at a minimum, appreciate the general content of a web page by reading initial translations. It should be <boundary-data type="header">
|
| 183 |
+
<confidence value="86">YO</confidence>
|
| 184 |
+
R920070592US<confidence value="4">1</confidence>
|
| 185 |
+
<confidence value="8">9</confidence>
|
| 186 |
+
</boundary-data>
|
| 187 |
+
<page-break num="10"/>
|
| 188 |
+
noted that after a user makes the initial request to translate a web page, no user intervention is needed for the remainder of the translation process. </p>
|
| 189 |
+
<p id="p-44" num="44">As translations from the translation servers become available, the translations are presented to the user immediately (step 110). Translations may be presented to the user <boundary-data type="line-number">5 </boundary-data>
|
| 190 |
+
visually and/or audibly via the browser client. In an illustrative embodiment, the original text of the web page is "morphed" into translated text and the translated text is morphed into subsequent translations. This "in-place" rendering technique provides a means of preserving the original web page layout. Also, in-place rendering can be visually pleasing. In order to differentiate between the multiple translation outputs for the same <boundary-data type="line-number">10 </boundary-data>
|
| 191 |
+
text, different colors, font-faces, sounds, or other presentation techniques can be used. </p>
|
| 192 |
+
<p id="p-45" num="45">In an additional embodiment, a user interface that allows a user to view all previous translations for a piece of text may be implemented. This is particularly useful, for example, in the unlikely, but possible, event that a faster translation server produces a better quality translation output than a slower translation server. In this instance, it is <boundary-data type="line-number">15 </boundary-data>
|
| 193 |
+
vital to make all translation results accessible to the user. This helps the user determine if the displayed text is the most accurate translation. One method of implementing this feature is to use a mouse-over tooltip that displays not only the original text before translation (for bilingual speakers), but all previously received translations. Preferably, the translation from the presumed best quality translation server (engine) will be <boundary-data type="line-number">20 </boundary-data>
|
| 194 |
+
displayed as the default translation. However, if a user feels that the default translation is not the best quality, the user may, in accordance with another aspect of the invention, designate a previously received translation as the default translation via the tooltip feature. </p>
|
| 195 |
+
<p id="p-46" num="46">It should be appreciated that methodologies for finding the best translation (e.g., <boundary-data type="line-number">25 </boundary-data>
|
| 196 |
+
in terms of translation accuracy or some other criteria) among a set of candidates are known by those skilled in the art and therefore will not be described herein. However, a simple assumption may be made that translations from slower servers should have better quality. </p>
|
| 197 |
+
<boundary-data type="header">
|
| 198 |
+
<confidence value="86">YO</confidence>
|
| 199 |
+
R920070592US<confidence value="5">1</confidence>
|
| 200 |
+
10 </boundary-data>
|
| 201 |
+
<p id="p-47" num="47">
|
| 202 |
+
<page-break num="11"/>
|
| 203 |
+
In an exemplary embodiment, the browser client also includes customized forward and backward navigation buttons similar to those found in conventional web browsers. Further, all mouse clicks in the translated page are intercepted and the targeted page is translated within the same interface. The navigation buttons can be used to move <boundary-data type="line-number">5 </boundary-data>
|
| 204 |
+
back and forth between pages within the interface. </p>
|
| 205 |
+
<p id="p-48" num="48">Referring now to FIG. 2, a block diagram illustrates an exemplary system <part-num-ref name="exemplary system">200</part-num-ref>
|
| 206 |
+
for implementing the methodology of FIG. 1, in accordance with an embodiment of the present invention. System <part-num-ref name="present invention. System">200</part-num-ref>
|
| 207 |
+
receives a request from an internet user to translate a structured document <part-num-ref name="structured document">202.</part-num-ref>
|
| 208 |
+
In response to the request, a translation processor <part-num-ref name="translation processor">204</part-num-ref>
|
| 209 |
+
retrieves <boundary-data type="line-number">10 </boundary-data>
|
| 210 |
+
the structured document <part-num-ref name="structured document">202.</part-num-ref>
|
| 211 |
+
The processor <part-num-ref name="processor">204</part-num-ref>
|
| 212 |
+
partitions the document into a plurality of translation units. The translation units are prioritized and placed in a prioritized translation queue <part-num-ref name="prioritized translation queue">206.</part-num-ref>
|
| 213 |
+
In accordance with the queue <part-num-ref name="queue">206,</part-num-ref>
|
| 214 |
+
asynchronous translation requests <part-num-ref name="queue 206, asynchronous translation requests">208</part-num-ref>
|
| 215 |
+
to translate the units are sent, preferably in parallel, to multiple translation servers of varying translation grades (210-1, . <confidence value="8">.</confidence>
|
| 216 |
+
. 210-3). In this example, a grade <part-num-ref name="grade">1</part-num-ref>
|
| 217 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 218 |
+
translation server 210-1 provides fast, but low-quality, translations. A grade <part-num-ref name="grade">2</part-num-ref>
|
| 219 |
+
translation server 210-2 provides moderate-quality translations at a moderate speed. And, a grade <part-num-ref name="grade">3</part-num-ref>
|
| 220 |
+
translation server 210-3 provides high-quality translations at a slow speed. As the servers output translated text, the translation processor <part-num-ref name="translation processor">204</part-num-ref>
|
| 221 |
+
immediately presents the translated translation units <part-num-ref name="translated translation units">(212)</part-num-ref>
|
| 222 |
+
to the user via a browser client. When presenting the translations, <boundary-data type="line-number">20 </boundary-data>
|
| 223 |
+
the translation processor <part-num-ref name="translation processor">204</part-num-ref>
|
| 224 |
+
preferably replaces lower-quality translations with higher- quality translations, as discussed above. </p>
|
| 225 |
+
<p id="p-49" num="49">Referring now to FIG. 3, an exemplary user interface <part-num-ref name="exemplary user interface">300</part-num-ref>
|
| 226 |
+
for a translation system is shown, in accordance with an embodiment of the present invention. User interface <part-num-ref name="present invention. User interface">300</part-num-ref>
|
| 227 |
+
resembles a conventional web browser. However, the user interface includes additional <boundary-data type="line-number">25 </boundary-data>
|
| 228 |
+
controls for translation. In an exemplary embodiment, the user interface <part-num-ref name="user interface">300</part-num-ref>
|
| 229 |
+
includes a uniform resource locator (URL) input <part-num-ref name="uniform resource locator (URL) input">302,</part-num-ref>
|
| 230 |
+
a translation progress indicator <part-num-ref name="translation progress indicator">304,</part-num-ref>
|
| 231 |
+
a language selection window <part-num-ref name="language selection window">306,</part-num-ref>
|
| 232 |
+
navigation buttons <part-num-ref name="language selection window 306, navigation buttons">308,</part-num-ref>
|
| 233 |
+
a translation mode toggle button <part-num-ref name="translation mode toggle button">310,</part-num-ref>
|
| 234 |
+
and a status bar <part-num-ref name="status bar">312.</part-num-ref>
|
| 235 |
+
It is to be appreciated that the invention is not limited to the <boundary-data type="header">
|
| 236 |
+
<confidence value="86">YO</confidence>
|
| 237 |
+
R920070592US1 <confidence value="88">11</confidence>
|
| 238 |
+
</boundary-data>
|
| 239 |
+
<page-break num="12"/>
|
| 240 |
+
particular translation features and controls shown. The URL input <part-num-ref name="URL input">302</part-num-ref>
|
| 241 |
+
may be used to specify a web address on the internet. The translation progress indicator <part-num-ref name="translation progress indicator">304</part-num-ref>
|
| 242 |
+
shows the translation progress of the translation servers. Progress may be shown, for example, by displaying the translation status corresponding to each server or by displaying translation <boundary-data type="line-number">5 </boundary-data>
|
| 243 |
+
progress for the fastest server. Alternative translation progress indication methodologies are contemplated, as will become apparent to those skilled in the art given the teachings herein. The language selection window <part-num-ref name="language selection window">306</part-num-ref>
|
| 244 |
+
allows a user to select a translation language pair. The navigation buttons <part-num-ref name="navigation buttons">308</part-num-ref>
|
| 245 |
+
allow a user to navigate to and from previously viewed web pages. The translation mode toggle button <part-num-ref name="translation mode toggle button">310</part-num-ref>
|
| 246 |
+
allows a user to switch between <boundary-data type="line-number">10 </boundary-data>
|
| 247 |
+
different translation modes, such as, original text, translated text, or original text and translated text side-by-side. The status bar <part-num-ref name="status bar">312</part-num-ref>
|
| 248 |
+
indicates the status of the translation (e.g., "Translating," "Translation completed," or "Error"). </p>
|
| 249 |
+
<p id="p-50" num="50">FIG. 4 is an illustrative user interface <part-num-ref name="illustrative user interface">400</part-num-ref>
|
| 250 |
+
depicting a partially translated str<confidence value="8">u</confidence>
|
| 251 |
+
ctured document, in accordance with an embodiment of the present invention. A <boundary-data type="line-number">15 </boundary-data>
|
| 252 |
+
translation progress indicator <part-num-ref name="translation progress indicator">402</part-num-ref>
|
| 253 |
+
shows a meter indicating partial translation of a web page. A status bar <part-num-ref name="status bar">404</part-num-ref>
|
| 254 |
+
indicates that the web page is in the process of being translated (e.g., "Translating..."). Portions of the web page designated as containing text with high translation priority <part-num-ref name="web page designated as containing text with high translation priority">(406)</part-num-ref>
|
| 255 |
+
are preferably translated first and portions of the web page designated as containing text of lower priority <part-num-ref name="web page designated as containing text of lower priority">(408)</part-num-ref>
|
| 256 |
+
are translated last (shown in the <boundary-data type="line-number">20 </boundary-data>
|
| 257 |
+
figure as untranslated text). </p>
|
| 258 |
+
<p id="p-51" num="51">FIG. 5 depicts an illustrative user interface <part-num-ref name="illustrative user interface">500</part-num-ref>
|
| 259 |
+
implemented as a web page which incorporates a feature, referred to herein as a "tooltip" option, in accordance with an embodiment of the present invention. A translation progress indicator <part-num-ref name="translation progress indicator">502</part-num-ref>
|
| 260 |
+
shows a full meter which indicates that the web page has been fully translated. Further, a status bar <boundary-data type="line-number">25 </boundary-data>
|
| 261 |
+
<part-num-ref name="status bar">504</part-num-ref>
|
| 262 |
+
indicates, "Translation Completed." In this illustrative embodiment, a user can view the original, untranslated source text by mousing over the translated text, in accordance with the tooltip feature. More particularly, as the user places the mouse cursor over a section of translated text, a source text tooltip pop-up window <part-num-ref name="source text tooltip pop-up window">506</part-num-ref>
|
| 263 |
+
appears. In this <boundary-data type="header">
|
| 264 |
+
<confidence value="86">YO</confidence>
|
| 265 |
+
R920070592US<confidence value="5">1</confidence>
|
| 266 |
+
12 </boundary-data>
|
| 267 |
+
<page-break num="13"/>
|
| 268 |
+
example, the source text tooltip contains the original, untranslated text; however, this pop-up technique can be used to show previously presented translations for a section of translated text. Further, the tooltip window may be programmed to give users the option to select which translations they want displayed as the default translation. Other <boundary-data type="line-number">5 </boundary-data>
|
| 269 |
+
techniques for presenting the original source text to the user are similarly contemplated given the teachings herein. </p>
|
| 270 |
+
<p id="p-52" num="52">Referring now to FIG. 6, a user interface <part-num-ref name="user interface">600</part-num-ref>
|
| 271 |
+
depicts, side-by-side, untranslated and translated text of a structured document, in accordance with an embodiment of the present invention. In this embodiment, a user can view the original web page <part-num-ref name="original web page">602,</part-num-ref>
|
| 272 |
+
the <boundary-data type="line-number">10 </boundary-data>
|
| 273 |
+
translated page <part-num-ref name="translated page">606,</part-num-ref>
|
| 274 |
+
or both side-by-side, by using a translation mode toggle button <part-num-ref name="translation mode toggle button">604,</part-num-ref>
|
| 275 |
+
or alternative means. The untranslated and translated text may be presented in separate windows as shown, although other presentation methodologies may be used. </p>
|
| 276 |
+
<p id="p-53" num="53">FIG. 7 is a block diagram illustrates an exemplary hardware implementation of a computing system <part-num-ref name="computing system">700</part-num-ref>
|
| 277 |
+
in which one or more components/methodologies of the invention <boundary-data type="line-number">15 </boundary-data>
|
| 278 |
+
(e.g., components/methodologies described in the context of FIG<confidence value="5">s</confidence>
|
| 279 |
+
. 1-6) may be implemented, according to an embodiment of the present invention. </p>
|
| 280 |
+
<p id="p-54" num="54">As shown, the techniques for presenting translated text in a structured document may be implemented in accordance with a processor <part-num-ref name="processor">710,</part-num-ref>
|
| 281 |
+
a memory <part-num-ref name="memory">712,</part-num-ref>
|
| 282 |
+
I/O devices <part-num-ref name="memory 712, I/O devices">714,</part-num-ref>
|
| 283 |
+
and a network interface <part-num-ref name="network interface">716,</part-num-ref>
|
| 284 |
+
coupled via a computer bus <part-num-ref name="computer bus">718</part-num-ref>
|
| 285 |
+
or alternate connection <boundary-data type="line-number">20 </boundary-data>
|
| 286 |
+
arrangement. </p>
|
| 287 |
+
<p id="p-55" num="55">It is to be appreciated that the term "processor" as used herein is intended to include any processing device, such as, for example, one that includes a CPU (central processing unit) and/or other processing circuitry. It is also to be understood that the term "processor" may refer to more than one processing device and that various elements <boundary-data type="line-number">25 </boundary-data>
|
| 288 |
+
associated with a processing device may be shared by other processing devices. </p>
|
| 289 |
+
<p id="p-56" num="56">The term "memory" as used herein is intended to include memory associated with a processor or CPU, such as, for example, RAM, ROM, a fixed memory device (e.g., hard drive), a removable memory device (e.g., diskette), flash memory, etc.</p>
|
| 290 |
+
<boundary-data type="header">
|
| 291 |
+
<confidence value="86">YO</confidence>
|
| 292 |
+
R920070592US1 13 </boundary-data>
|
| 293 |
+
<p id="p-57" num="57">
|
| 294 |
+
<page-break num="14"/>
|
| 295 |
+
In addition, the phrase "input/output devices" or "I/O devices" as used herein is intended to include, for example, one or more input devices (e.g., keyboard, mouse, scanner, etc.) for entering data to the processing unit, and/or one or more output devices (e.g., speaker, display, printer, etc.) for presenting results associated with the processing <boundary-data type="line-number">5 </boundary-data>
|
| 296 |
+
unit. </p>
|
| 297 |
+
<p id="p-58" num="58">Still further, the phrase "network interface" as used herein is intended to include, for example, one or more transceivers to permit the computer system to communicate with another computer system via an appropriate communications protocol.</p>
|
| 298 |
+
<p id="p-59" num="59">Software components including instructions or code for performing the <boundary-data type="line-number">10 </boundary-data>
|
| 299 |
+
methodologies described herein may be stored in one or more of the associated memory devices (e.g., ROM, fixed or removable memory) and, when ready to be utilized, loaded in part or in whole (e.g., into RAM) and executed by a CPU. </p>
|
| 300 |
+
<p id="p-60" num="60">Although illustrative embodiments of the present invention have been described herein with reference to the accompanying drawings, it is to be understood that the <boundary-data type="line-number">15 </boundary-data>
|
| 301 |
+
invention is not limited to those precise embodiments, and that various other changes and modifications may be made therein by one skilled in the art without departing from the scope of the appended claims. </p>
|
| 302 |
+
<boundary-data type="header">
|
| 303 |
+
<confidence value="86">YO</confidence>
|
| 304 |
+
R920070592US1 14 </boundary-data>
|
| 305 |
+
</description>
|
| 306 |
+
</us-patent-application>
|
| 307 |
+
|
applicant/11972794.xml
ADDED
|
@@ -0,0 +1,288 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>11972794</doc-number>
|
| 8 |
+
<date>2008-03-20</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">VERIFICATION OF TRANSLATION</heading>
|
| 14 |
+
<p id="p-1" num="1">
|
| 15 |
+
<confidence value="4">I</confidence>
|
| 16 |
+
, Jinwon Kim, hereby declare as follows: </p>
|
| 17 |
+
<p id="p-2" num="2">That <confidence value="5">I</confidence>
|
| 18 |
+
am familiar with the Korean and English languages; </p>
|
| 19 |
+
<p id="p-3" num="3">That I am capable of translating from Korean to English;</p>
|
| 20 |
+
<p id="p-4" num="4">That the translation attached hereto is a true and accurate translation of Method for image prediction of multi-view video cod<confidence value="7">e</confidence>
|
| 21 |
+
and computer readable recording medium therefor That all statements made herein of my own knowledge are true and that all statements made on information and belief are believed to be true; </p>
|
| 22 |
+
<p id="p-5" num="5">And further that these statements were made with the knowledge that willfu<confidence value="8">l</confidence>
|
| 23 |
+
false statements and the like so made are punishable by fine or imprisonment, or both, under Section <part-num-ref name="like so made are punishable by fine or imprisonment, or both, under Section">1001</part-num-ref>
|
| 24 |
+
of Title <part-num-ref name="of Title">18</part-num-ref>
|
| 25 |
+
of the United States Code and that such willful false statements may jeopardize the validity of the application or any registration resulting therefrom. </p>
|
| 26 |
+
<p id="p-6" num="6">
|
| 27 |
+
<confidence value="66">By</confidence>
|
| 28 |
+
<confidence value="2222">this</confidence>
|
| 29 |
+
<confidence value="222">2st</confidence>
|
| 30 |
+
<confidence value="222">day</confidence>
|
| 31 |
+
<confidence value="4">/</confidence>
|
| 32 |
+
Executed this 21st day of January <page-break num="2"/>
|
| 33 |
+
<boundary-data type="header">U.S. Patent Application Serial No. 11/972,79<confidence value="5">4</confidence>
|
| 34 |
+
</boundary-data>
|
| 35 |
+
<boundary-data type="header">English Translation</boundary-data>
|
| 36 |
+
</p>
|
| 37 |
+
<heading id="h-2">METHOD FOR IMAGE PREDICTION OF MULTI-VIEW VIDEO CODEC AND</heading>
|
| 38 |
+
<heading id="h-3">COMPUTER READABLE RECORDING MEDIUM THEREFOR</heading>
|
| 39 |
+
<heading id="h-4">CROSS-REFERENCE TO RELATED APPLICATION<confidence value="8">S</confidence>
|
| 40 |
+
</heading>
|
| 41 |
+
<p id="p-7" num="7">[0001] This application claims priority under 35 U.S.C. <confidence value="55">§1</confidence>
|
| 42 |
+
19 to U.S. Provisional Application Nos. 60/884,495 and 60/886,759, filed on January <part-num-ref name="U.S.C. §119 to U.S. Provisional Application Nos. 60/884,495 and 60/886,759, filed on January">11,</part-num-ref>
|
| 43 |
+
<part-num-ref name="U.S.C. §119 to U.S. Provisional Application Nos. 60/884,495 and 60/886,759, filed on January 11,">2007</part-num-ref>
|
| 44 |
+
and January <part-num-ref name="and January">26,</part-num-ref>
|
| 45 |
+
<part-num-ref name="and January 26,">2007,</part-num-ref>
|
| 46 |
+
the disclosure of which is incorporated herein by reference in its entirety. </p>
|
| 47 |
+
<heading id="h-5">BACKGROUND OF THE INVENTION</heading>
|
| 48 |
+
<p id="p-8" num="8">1. Field of the Invention [0002] The present disclosure relates to multi-view video coding, and more particularly, to a method for image prediction of a multi-view video codec and a computer readable recording medium therefore.</p>
|
| 49 |
+
<p id="p-9" num="9">2. Description of the Related Art [0003] A multi-view video codec is a video codec that outputs a plurality of images captured from different views as one or multiple compressed bitstreams. The multi-view video codec performs compression using a correlation between different views, i.e., inter- view correlation, as well as compression using spatial/temporal correlations, which is one of characteristics of a related-art video codec. In the multi-view video codec, a technique for effectively compressing images of different views must be added. However, in most cases, the related-art technique that uses the spatial/temporal correlation is still being used.</p>
|
| 50 |
+
<p id="p-10" num="10">In actuality, there is almost no technique that uses the inter-view correlation.</p>
|
| 51 |
+
<boundary-data type="header">
|
| 52 |
+
<confidence value="8">1</confidence>
|
| 53 |
+
</boundary-data>
|
| 54 |
+
<boundary-data type="header">U.S. Patent Application S<confidence value="5">e</confidence>
|
| 55 |
+
rial No. 11/972,794 </boundary-data>
|
| 56 |
+
<boundary-data type="header">English Translation</boundary-data>
|
| 57 |
+
<p id="p-11" num="11">
|
| 58 |
+
<page-break num="3"/>
|
| 59 |
+
[0004] In the related art multi-view video codec employing the existing H.264 standard, temporal prediction is conducted to remove temporal redundancy between images, thereby improving coding efficiency. However, the related art multi-view video codec performs coding by using an image of a different view simply as a reference image, failing to perform inter-view motion compensation in due consideration of a disparity, which is a displacement value between views. Thus, improvement of coding efficiency is limited because no technique is used for removing inter-view redundancy between images. </p>
|
| 60 |
+
<heading id="h-6">SUMMARY</heading>
|
| 61 |
+
<p id="p-12" num="12">[0005] Therefore, an object of the present invention is to provide a method for i<confidence value="8">m</confidence>
|
| 62 |
+
age prediction of a multi-view video codec capable of improving coding efficiency, and a computer readable recording medium therefor. </p>
|
| 63 |
+
<p id="p-13" num="13">[0006] Another object of the present invention is to provide a method for image prediction of a multi-view video codec capable of effectively using images of multiple different views, and a computer readable recording medium therefor.</p>
|
| 64 |
+
<p id="p-14" num="14">[0007] Another object of the present invention is to provide a method for image prediction of a multi-view video codec capable of proposing a new prediction scheme suitable for multi-view video coding, and a computer readable recording medium therefor.</p>
|
| 65 |
+
<p id="p-15" num="15">[0008<confidence value="5">]</confidence>
|
| 66 |
+
To achieve these and other advantages and in accordance with the purpose(s) of the present invention as embodied and broadly described herein, a method for image prediction of a multi-view video codec in accordance with an aspect of the present invention includes: partitioning an image to a plurality of base blocks; acquiring information of reference images which are temporally different; acquiring information of <boundary-data type="header">
|
| 67 |
+
<confidence value="8">2</confidence>
|
| 68 |
+
</boundary-data>
|
| 69 |
+
<page-break num="4"/>
|
| 70 |
+
<boundary-data type="header">U.S. Patent Application Serial No. 11/972,794</boundary-data>
|
| 71 |
+
<boundary-data type="header">English Translation</boundary-data>
|
| 72 |
+
reference images which have different views; and predicting a target block based on the acquired information. </p>
|
| 73 |
+
<p id="p-16" num="16">[0009<confidence value="5">]</confidence>
|
| 74 |
+
To achieve these and other advantages and in accordance with the purpose(s) of the present invention, there is provided a computer-readable recording medium storing a program for executing image prediction of a multi-view video codec in accordance with another aspect of the present invention, wherein the image prediction includes partitioning a target image to a plurality of base blocks; acquiring information of reference images which are temporally different; acquiring information of reference images which have different views; and predicting a target block based on the acquired information. </p>
|
| 75 |
+
<p id="p-17" num="17">[0010] The foregoing and other objects, features, aspects and advantages of the present invention will become more apparent from the following detailed description of the present invention when taken in conjunction with the accompanying drawings.</p>
|
| 76 |
+
<heading id="h-7">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 77 |
+
<p id="p-18" num="18">[0011] The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention.</p>
|
| 78 |
+
<p id="p-19" num="19">[0012] FIG. <confidence value="5">1</confidence>
|
| 79 |
+
is a flowchart illustrating a method for image prediction of a multi- view video codec according to an embodiment of the present invention; </p>
|
| 80 |
+
<p id="p-20" num="20">[0013] FIG. 2 illustrates an image reference structure in the method for image prediction of a multi-view video codec according to the embodiment of the present invention;</p>
|
| 81 |
+
<boundary-data type="header">
|
| 82 |
+
<confidence value="8">3</confidence>
|
| 83 |
+
</boundary-data>
|
| 84 |
+
<boundary-data type="header">U.S. Patent Application Serial No. <confidence value="66">11</confidence>
|
| 85 |
+
/972,7<confidence value="68">94</confidence>
|
| 86 |
+
</boundary-data>
|
| 87 |
+
<boundary-data type="header">English Translation</boundary-data>
|
| 88 |
+
<p id="p-21" num="21">
|
| 89 |
+
<page-break num="5"/>
|
| 90 |
+
[0014] FIG. 3 illustrates encoding/decoding using residual information of a macroblock according to an embodiment of the present invention; and [0015] FIG. 4 illustrates a weighting value reference model according to an embodiment of the present invention. </p>
|
| 91 |
+
<heading id="h-8">DETAILED DESCRIPTION OF EMBODIMENTS</heading>
|
| 92 |
+
<p id="p-22" num="22">[0016] In a codec that supports multi-view, prediction can be performed based on images of multiple different views, besides using a technique employed in the related-art two-dimensional codec. The prediction based on images of multiple different views must be concerned with how to obtain the most similar image to an image of a view to be currently compressed, using multiple images of different views. Even if a multi-view codec (MVC) is also a codec that supports multi-view, a technique using images having multiple different views has not yet been employed therein. For this reason, a technique for effectively compressing an image of a view to be currently compressed, based on images of different views will be described according to embodiments of the present invention.</p>
|
| 93 |
+
<p id="p-23" num="23">[0017] A method for image prediction of a multi-view video codec according to exemplary embodiments of the present invention can be realized as programs and stored in a computer-readable recording medium that can execute the programs. A computer or an equivalent digital device operates the programs for execution of the method for image prediction of a multi-view video codec according to the exemplary embodiments of the present invention. Thus, description will be made on the assumption that the operations are performed by a control means (hereinafter, referred to as a <confidence value="5">'</confidence>
|
| 94 |
+
control unit') of an arithmetic device. </p>
|
| 95 |
+
<boundary-data type="header">
|
| 96 |
+
<confidence value="8">4</confidence>
|
| 97 |
+
</boundary-data>
|
| 98 |
+
<boundary-data type="header">U.S. Patent Application Serial No. 11/972,794</boundary-data>
|
| 99 |
+
<boundary-data type="header">English Translation</boundary-data>
|
| 100 |
+
<p id="p-24" num="24">
|
| 101 |
+
<page-break num="6"/>
|
| 102 |
+
[0018<confidence value="5">]</confidence>
|
| 103 |
+
Hereinafter, specific embodiments will be described in detail with reference to the accompanying drawings. Like reference numerals refer to like elements throughout. </p>
|
| 104 |
+
<p id="p-25" num="25">In some embodiments, well-known processes, well-known device structures, and well- known techniques will not be described in detail to avoid ambiguous interpretation of the present invention.</p>
|
| 105 |
+
<p id="p-26" num="26">[0019] FIG. 1 is a flowchart of a method for image prediction of a multi-view video codec according to an embodiment of the present invention, and FIG. 2 illustrates an image reference structure according to the embodiment of the present invention. In operation S<confidence value="5">1</confidence>
|
| 106 |
+
10, a control unit partitions a target image to a number of base blocks suitably for block-unit compression. </p>
|
| 107 |
+
<p id="p-27" num="27">[0020<confidence value="5">]</confidence>
|
| 108 |
+
As illustrated in FIG. 2, two prediction methods may be used for a block <part-num-ref name="block">210</part-num-ref>
|
| 109 |
+
to be currently encoded/decoded (hereinafter, referred to as a target block). One of the prediction methods computes a temporal difference value with a reference image to obtain motion information, reference-image information and a difference value between images. The other method uses an image of a different view as a reference image to obtain motion information, and reference image information. In the drawing, reference blocks <part-num-ref name="drawing, reference blocks">220</part-num-ref>
|
| 110 |
+
and <part-num-ref name="and">230</part-num-ref>
|
| 111 |
+
are images that the target block <part-num-ref name="target block">210</part-num-ref>
|
| 112 |
+
references, and residual blocks <part-num-ref name="references, and residual blocks">240</part-num-ref>
|
| 113 |
+
and <part-num-ref name="and">250</part-num-ref>
|
| 114 |
+
are residual images that the target block references <part-num-ref name="target block references">210.</part-num-ref>
|
| 115 |
+
The residual means a difference between an original image and an encoded image, which is resulted from quantization of an encoding process. </p>
|
| 116 |
+
<p id="p-28" num="28">[0021] In operation S 120, the control unit acquires information of reference images that are temporally different (hereinafter, referred to as temporally different reference images). That is, a temporal difference value with a reference image is computed to acquire motion information and reference-image information. When the target block <part-num-ref name="target block">210</part-num-ref>
|
| 117 |
+
<boundary-data type="header">
|
| 118 |
+
<confidence value="8">5</confidence>
|
| 119 |
+
</boundary-data>
|
| 120 |
+
<page-break num="7"/>
|
| 121 |
+
<boundary-data type="header">
|
| 122 |
+
<confidence value="66">U.</confidence>
|
| 123 |
+
S. Patent Application Serial No. <confidence value="66">11</confidence>
|
| 124 |
+
/972,79<confidence value="5">4</confidence>
|
| 125 |
+
</boundary-data>
|
| 126 |
+
<boundary-data type="header">English Translation</boundary-data>
|
| 127 |
+
uses a temporally different image as a reference image, the target image can acquire motion information and a residual associated with the referenced image. </p>
|
| 128 |
+
<p id="p-29" num="29">[0022] The residual information does not include a temporal correlation but include an inter-view correlation. Thus, information quantity can be reduced by just addition or subtraction with residual information of an image having a different view. In this case, for a decoding operation, information reporting the use of the residual information of the different-view image may be added at the time of encoding. The information reporting the use of the residual information may be contained in macroblock layer or a higher layer.</p>
|
| 129 |
+
<p id="p-30" num="30">[0023] Even if residual information pieces of multiple images having different views are present, residual information of an image that is most similar to the target block <part-num-ref name="target block">2<confidence value="58">10</confidence>
|
| 130 |
+
</part-num-ref>
|
| 131 |
+
in terms of view may be used. Also, optimum residual information may be selected among residual information pieces of multiple images having different views. In this case, information that reports view information of the image of the residual information being used may be added. For example, information reporting the use of residual information of V<confidence value="5">I</confidence>
|
| 132 |
+
EW3 may be added. The information reporting the use of the residual information of the image having a specific view may be contained in a macroblock or a higher layer. </p>
|
| 133 |
+
<p id="p-31" num="31">[0024] Also, new residual information may be used, which is obtained by combining optimum residual information pieces among the residual information pieces of images having different views. For example, a mean value of the residual information pieces between at least two selected images having two different views may be used as the residual information, or new residual information may be generated by applying a low- pass filter (LPF) such as a deblocking filter to the mean value obtained in the aforementioned manner.</p>
|
| 134 |
+
<boundary-data type="header">
|
| 135 |
+
<confidence value="8">6</confidence>
|
| 136 |
+
</boundary-data>
|
| 137 |
+
<boundary-data type="header">U.S. Pat<confidence value="8">e</confidence>
|
| 138 |
+
nt Application S<confidence value="4">e</confidence>
|
| 139 |
+
rial No. 11/972,794 </boundary-data>
|
| 140 |
+
<boundary-data type="header">English Translation</boundary-data>
|
| 141 |
+
<p id="p-32" num="32">
|
| 142 |
+
<page-break num="8"/>
|
| 143 |
+
[0025] In operation S<confidence value="2">i</confidence>
|
| 144 |
+
30, the control unit acquires information of reference images having different views. That is, a difference value with a reference image having a different view is computed to acquire motion information and reference-image information. When the target block <part-num-ref name="target block">210</part-num-ref>
|
| 145 |
+
uses an image having a different view as a reference image, the target image can obtain motion information and residual information with respect to the referenced image. </p>
|
| 146 |
+
<p id="p-33" num="33">[0026] According to the embodiment of the present invention, to minimize this residual information, a method of using residual information present in a temporally different image is provided so as to minimize residual information to be currently encoded/decoded. Here, the residual information does not include an inter-view (spatial) correlation but include a temporal correlation. The image quantity can be reduced by just addition or subtraction with the residual of the temporally different image. In this case, for decoding, information reporting the use of the residual information of the temporally different image can be added at the time of encoding. The information reporting the use of the residual may be contained in a macroblock layer or a higher layer.</p>
|
| 147 |
+
<p id="p-34" num="34">[0027] Even if residual information pieces of multiple temporally different images are present, residual information of an image that is most similar to the target block <part-num-ref name="target block">210</part-num-ref>
|
| 148 |
+
in terms of time may be used. Also, optimum residual information may be selected among the residual information pieces of the temporally different images. In this case, information reporting the time of the image of the residual information may be added. </p>
|
| 149 |
+
<p id="p-35" num="35">The information reporting the use of the residual information of the image of the specific time may be contained in a macroblock or a higher layer.</p>
|
| 150 |
+
<p id="p-36" num="36">[0028] Also, new residual information may be used, which is obtained by combining optimum residual information pieces among the residual information pieces of the <boundary-data type="header">
|
| 151 |
+
<confidence value="8">7</confidence>
|
| 152 |
+
</boundary-data>
|
| 153 |
+
<page-break num="9"/>
|
| 154 |
+
<boundary-data type="header">U.S. Patent Application S<confidence value="5">e</confidence>
|
| 155 |
+
rial No. 11/972,794 </boundary-data>
|
| 156 |
+
<boundary-data type="header">English Translation</boundary-data>
|
| 157 |
+
multiple temporally different images. For example, the mean value of the residual information pieces between two temporally different images may be used as the residual information, or new residual information may be generated by applying a filter to the mean value obtained in the aforementioned manner. </p>
|
| 158 |
+
<p id="p-37" num="37">[0029] A location obtained by computation using a global disparity may be used as a reference residual block of the target block <part-num-ref name="target block">210.</part-num-ref>
|
| 159 |
+
</p>
|
| 160 |
+
<p id="p-38" num="38">[0030] To report the application of the above techniques, information of the following exemplary format may be used:</p>
|
| 161 |
+
<p id="p-39" num="39">{" ResPred is equal to 1" specifies that the current slice uses view residual prediction method. <confidence value="5">"</confidence>
|
| 162 |
+
ResPred is equal to 0<confidence value="5">"</confidence>
|
| 163 |
+
specifies that the current slice does not use view residual prediction method. When ResPred is not present, ResPred is inferred as <part-num-ref name="current slice does not use view residual prediction method. When ResPred is not present, ResPred is inferred as">0.</part-num-ref>
|
| 164 |
+
</p>
|
| 165 |
+
<p id="p-40" num="40">It can be located in slice layer or higher layer (SPS (Sequence Parameter Set), SPSE (SPS Extension), PPS (Picture Parameter Set), PPSE (PPS Extension), slice header, slice header extension, SEI (Supplementary Enhancement Information)).</p>
|
| 166 |
+
<p id="p-41" num="41">
|
| 167 |
+
<confidence value="5">"</confidence>
|
| 168 |
+
ResPredFlag is equal to <confidence value="66">1"</confidence>
|
| 169 |
+
specifies that the residual signal is predicted by the reconstructed residual signal of neighbor view or temporally collocated macroblock, if possible, with the considering of the global disparity. <confidence value="5">"</confidence>
|
| 170 |
+
ResPredFlag is equal to 0<confidence value="5">"</confidence>
|
| 171 |
+
specifies any residual signal is not predicted. When ViewPredFlag is not present, ViewPredFlag is inferred as 0.<confidence value="5">}</confidence>
|
| 172 |
+
[0031] In operation S<confidence value="5">1</confidence>
|
| 173 |
+
40, the control unit predicts the target block based on the acquired information pieces. That is, those information pieces are contained as prediction information of a corresponding image at the time of encoding, and the prediction is performed based on the prediction information at the time of decoding. This will now be described with reference to FIG. 3 in more detail. </p>
|
| 174 |
+
<boundary-data type="header">
|
| 175 |
+
<confidence value="8">8</confidence>
|
| 176 |
+
</boundary-data>
|
| 177 |
+
<boundary-data type="header">U.S. Patent Application S<confidence value="5">e</confidence>
|
| 178 |
+
rial No. 11/972,794 </boundary-data>
|
| 179 |
+
<boundary-data type="header">English Translation</boundary-data>
|
| 180 |
+
<p id="p-42" num="42">
|
| 181 |
+
<page-break num="10"/>
|
| 182 |
+
[0032] FIG. 3 illustrates encoding/decoding using residual information of a macroblock according to the embodiment of the present invention. Referring to FIG. 3, if a disparity corresponding to a target macroblock <part-num-ref name="target macroblock">310</part-num-ref>
|
| 183 |
+
indicates a reference macroblock <part-num-ref name="reference macroblock">320,</part-num-ref>
|
| 184 |
+
residual information at time (t) is generated using motion information of the reference macroblock, and a difference value with residual information generated by using motion information of a target macroblock is encoded/decoded. In this case, information reporting the use of the residual information may be contained in a residual data layer. Also, a value transmitted to a slice header or a value computed by a time interval with a transmitted slice may be used as a disparity. </p>
|
| 185 |
+
<p id="p-43" num="43">[0033] According to another embodiment, a target block <part-num-ref name="target block">210</part-num-ref>
|
| 186 |
+
may be expressed as the following Equation (1): </p>
|
| 187 |
+
<p id="p-44" num="44">Recon <confidence value="8">=</confidence>
|
| 188 |
+
Pred <confidence value="8">+</confidence>
|
| 189 |
+
Res (1) where Pred denotes a reference image of a specific size, which is most similar to a target block <part-num-ref name="target block">210</part-num-ref>
|
| 190 |
+
of FIG. 2 in a temporal/spatial domain and can be represented by motion information, and Res denotes residual information indicating a difference between a reference image and a target block <part-num-ref name="target block">210.</part-num-ref>
|
| 191 |
+
</p>
|
| 192 |
+
<p id="p-45" num="45">[0034] According to the embodiment of the present invention, to <confidence value="8">m</confidence>
|
| 193 |
+
inimize this residual information, a method of using residual information present in an image having a different view is proposed, thereby reducing the residual information being currently <confidence value="222222222222222">encoded/decoded</confidence>
|
| 194 |
+
. A video codec can be implemented such that Pred is properly selected to minimize Res. As Pred in the multi-view codec, an image that is proper in terms of view or time may be used. Pred may be defined by the following Equation (2): </p>
|
| 195 |
+
<p id="p-46" num="46">Pred = F(Pred' + Res') (2) <boundary-data type="header">
|
| 196 |
+
<confidence value="8">9</confidence>
|
| 197 |
+
</boundary-data>
|
| 198 |
+
<page-break num="11"/>
|
| 199 |
+
<boundary-data type="header">U.S. Patent Application Serial No. 11/972,79<confidence value="5">4</confidence>
|
| 200 |
+
</boundary-data>
|
| 201 |
+
<boundary-data type="header">English Translation</boundary-data>
|
| 202 |
+
[0035] That is, Pred is obtained by applying a proper filter, e.g., an LPF such as a deblocking filter in H.264, to a value obtained by adding a residual to a certain reference image. </p>
|
| 203 |
+
<p id="p-47" num="47">[0036] When Equation (2) is applied to Equation (1), the following Equation <part-num-ref name="following Equation">(3)</part-num-ref>
|
| 204 |
+
can be obtained: </p>
|
| 205 |
+
<p id="p-48" num="48">Recon = F(Pred' + Res') + Res" (3) where Pred' and Res' are a reference image and a residual of an image that the target block <part-num-ref name="target block">210</part-num-ref>
|
| 206 |
+
references, respectively. A combination of Pred' and Res' that are properly induced is used as a reference image of a current image, i.e., a target image, and residual information therebetween is minimized. </p>
|
| 207 |
+
<p id="p-49" num="49">[0037] If Equation (3) is rearranged with respect to the terms Pred' and Res' by distributing F, F(Pred') is represented by Pred, and Res is represented by F(Res')+Res".</p>
|
| 208 |
+
<p id="p-50" num="50">Thus, a gain is obtained by transmitting Res" instead of Res as in the related art.</p>
|
| 209 |
+
<p id="p-51" num="51">[0038<confidence value="5">]</confidence>
|
| 210 |
+
If Pred acquires a reference image in a temporal domain, the term Res' is obtained from a view domain, whereas if Pred acquires a reference image in a view domain, the term Res' is obtained from a temporal domain. F<confidence value="2">(</confidence>
|
| 211 |
+
, which is a filter suitable for the obtained term Res' may be additionally used. For example, the simplest filter having a filter coefficient { 1/2, 1/2<confidence value="5">}</confidence>
|
| 212 |
+
may be used, or a filter such as 1/20<confidence value="5">{</confidence>
|
| 213 |
+
1, -4. <part-num-ref name="filter such as 1/20{1, -4.">20,</part-num-ref>
|
| 214 |
+
<part-num-ref name="filter such as 1/20{1, -4. 20,">20,</part-num-ref>
|
| 215 |
+
-4, <part-num-ref name="filter such as 1/20{1, -4. 20, 20, -4,">
|
| 216 |
+
<confidence value="8">1</confidence>
|
| 217 |
+
</part-num-ref>
|
| 218 |
+
may be used. </p>
|
| 219 |
+
<p id="p-52" num="52">[0039] To report the application of the above techniques, information of the following exemplary format may be used:</p>
|
| 220 |
+
<p id="p-53" num="53">
|
| 221 |
+
<confidence value="5">{</confidence>
|
| 222 |
+
"NewPred is equal to <confidence value="2">1</confidence>
|
| 223 |
+
<confidence value="6">"</confidence>
|
| 224 |
+
specifies that the current slice uses new view prediction method according to the present invention. "NewPred is equal to 0" specifies that the current slice does not use new view prediction method according to the present invention. </p>
|
| 225 |
+
<boundary-data type="header">
|
| 226 |
+
<confidence value="88">10</confidence>
|
| 227 |
+
</boundary-data>
|
| 228 |
+
<boundary-data type="header">U.S. Patent Application S<confidence value="5">e</confidence>
|
| 229 |
+
rial No. 11/972,79<confidence value="5">4</confidence>
|
| 230 |
+
</boundary-data>
|
| 231 |
+
<boundary-data type="header">English Translation</boundary-data>
|
| 232 |
+
<p id="p-54" num="54">
|
| 233 |
+
<page-break num="12"/>
|
| 234 |
+
When NewPred is not present, NewPred is inferred as 0. It can be located in slice layer or higher layer (SPS, PPS, Slice header, slice header extension, SE<confidence value="68">).</confidence>
|
| 235 |
+
</p>
|
| 236 |
+
<p id="p-55" num="55">
|
| 237 |
+
<confidence value="5">"</confidence>
|
| 238 |
+
ResPredFlag is equal to 1<confidence value="6">"</confidence>
|
| 239 |
+
specifies that the predictor of the current macroblock is derivate as following, If the current macroblock is coded by inter mode (temporal direction), residual signal of neighbor view(s) and reference block of the current macroblock(s) are used as the predictor (Deblocking filter can be applied on the predictor). </p>
|
| 240 |
+
<p id="p-56" num="56">Otherwise (the current macroblock is coded by inter-view mode (view direction)), residual signal of collocated block(s) and reference block of the current <confidence value="222222222222">macroblock(s</confidence>
|
| 241 |
+
) is used as the predictor (Deblocking filter can be applied on the predictor.) if possible, with the considering of the global disparity. "ResPredFlag is equal to 0" specifies any residual signal is not predicted. When ViewPredFlag is not present, ViewPredFlag is inferred as 0.<confidence value="5">}</confidence>
|
| 242 |
+
[0040] According to another embodiment of the present invention, a weighting value or a weighted prediction value may be established. For example, if an image has a certain temporal characteristic such as image fading in/out, a weighting value of an image of a different view may be used. The weighting value means information indicating an extent to which image brightness or chrominance signals change over time as illustrated in FIG. </p>
|
| 243 |
+
<p id="p-57" num="57">4. FIG. 4 illustrates a weighting-value reference model according to the embodiment of the present invention.</p>
|
| 244 |
+
<p id="p-58" num="58">[0041] In general, even if images have different views, they may have similar temporal characteristics. That is, in the case where images are gradually brightened, an encoder may send a proper weighting value to a decoder so that the decoder can collectively apply the weighting value to the images of the different views.</p>
|
| 245 |
+
<boundary-data type="header">
|
| 246 |
+
<confidence value="88">11</confidence>
|
| 247 |
+
</boundary-data>
|
| 248 |
+
<boundary-data type="header">U.S. Patent Application Serial No. 11/972,794</boundary-data>
|
| 249 |
+
<boundary-data type="header">English Translation</boundary-data>
|
| 250 |
+
<p id="p-59" num="59">
|
| 251 |
+
<page-break num="13"/>
|
| 252 |
+
[0042] If a different light source is used for each view, it may be difficult to collectively apply the weighting value. In this case, a new weighting value must be used. </p>
|
| 253 |
+
<p id="p-60" num="60">[0043] As the simplest implementation method, weighting information may be defined for each view. However, this method may be inefficient because multiple redundant information pieces may be transmitted.</p>
|
| 254 |
+
<p id="p-61" num="61">[0044] According to the embodiment of the present invention, in order to reduce redundant information and overcome a limitation caused by using different light sources, a weighting value of a specific view such as a BaseView or VIEW<confidence value="4">O</confidence>
|
| 255 |
+
of FIG. 4 is shared, and information reporting whether weighting values of different views are used as they are (hereinafter, referred to as weighting information) is used. </p>
|
| 256 |
+
<p id="p-62" num="62">[0045] For example, as illustrated in FIG. 4, images of VIEW <confidence value="2">1</confidence>
|
| 257 |
+
may contain weighting information reporting the use of a weighting value of BaseView (View<confidence value="4">O</confidence>
|
| 258 |
+
), and images of View2 may contain weighting information reporting the use of their own weighting values without using the weighting value of BaseView. </p>
|
| 259 |
+
<p id="p-63" num="63">[0046] The weighting information is inserted in a bit stream to prevent mutual mis- operation between an encoder and a decoder. The weighting information may be contained in a slice header, a slice header extension or a higher layer such as PPS, PPSE, SPS, SPSE or SEI.</p>
|
| 260 |
+
<p id="p-64" num="64">[0047] To report the application of the above techniques, information of the following exemplary format may be used:</p>
|
| 261 |
+
<p id="p-65" num="65">
|
| 262 |
+
<confidence value="5">{</confidence>
|
| 263 |
+
"baseviewpredweighttableflag is equal to 1<confidence value="5">"</confidence>
|
| 264 |
+
specifies that the variables for weighted prediction are inferred. When baseviewpredweighttableflag is not present, it shall be inferred as follows: </p>
|
| 265 |
+
<boundary-data type="header">
|
| 266 |
+
<confidence value="88">12</confidence>
|
| 267 |
+
</boundary-data>
|
| 268 |
+
<boundary-data type="header">U.S. Patent Application Serial <confidence value="66">No</confidence>
|
| 269 |
+
. 11/972,794 </boundary-data>
|
| 270 |
+
<boundary-data type="header">English Translation</boundary-data>
|
| 271 |
+
<p id="p-66" num="66">
|
| 272 |
+
<page-break num="14"/>
|
| 273 |
+
If baseViewFlag (which indicates whether baseview or not) is equal to <confidence value="68">I,</confidence>
|
| 274 |
+
<confidence value="2222222222222222222222222">basepred_weighttable_flag</confidence>
|
| 275 |
+
shall be inferred to be equal to 0. </p>
|
| 276 |
+
<p id="p-67" num="67">Otherwise, baseview_predweighttable_flag shall be inferred to be equal to 1.<confidence value="5">}</confidence>
|
| 277 |
+
[0048] The method for image prediction of a multi-view video codec and the computer readable recording medium therefor according to the embodiments of the present invention, an image that is most similar to an image of a view to be currently compressed is generated by using inter-view prediction, i.e., using images of multiple different views, thereby improving coding efficiency. </p>
|
| 278 |
+
<p id="p-68" num="68">[0049] The methods for image prediction of a multi-view video codec according to the exemplary embodiments can be realized as programs and stored in a co<confidence value="5">m</confidence>
|
| 279 |
+
pute<confidence value="68">r-</confidence>
|
| 280 |
+
readable recording medium that can execute the programs. Examples of the computer- readable recording medium include CD-ROM, RAM, ROM, floppy disks, hard disks, magneto-optical disks and the like. </p>
|
| 281 |
+
<p id="p-69" num="69">[0050<confidence value="5">]</confidence>
|
| 282 |
+
As the present invention may be embodied in several forms without departing from the spirit or essential characteristics thereof, it should also be understood that the above-described embodiments are not limited by any of the details of the foregoing description, unless otherwise specified, but rather should be construed broadly within its spirit and scope as defined in the appended claims, and therefore all changes and modifications that fall within the metes and bounds of the claims, or equivalents of such metes and bounds are therefore intended to be embraced by the appended claims. </p>
|
| 283 |
+
<boundary-data type="header">
|
| 284 |
+
<confidence value="88">13</confidence>
|
| 285 |
+
</boundary-data>
|
| 286 |
+
</description>
|
| 287 |
+
</us-patent-application>
|
| 288 |
+
|
applicant/12006702.xml
ADDED
|
@@ -0,0 +1,58 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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="12006702.09-20-2012.H7CA1YCOPXXIFW3.SPEC.xml" pat:id="H7CA1YCOPXXIFW3" 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>12006702</pat:ApplicationNumber></pat:ApplicationHeaderDetails>
|
| 5 |
+
<pat:PageTotalQuantity>3</pat:PageTotalQuantity>
|
| 6 |
+
<pat:ParagraphTotalQuantity>16</pat:ParagraphTotalQuantity>
|
| 7 |
+
</pat:DocumentHeaderDetails>
|
| 8 |
+
<pat:MailRoomDate>2012-09-20</pat:MailRoomDate>
|
| 9 |
+
<pat:Specification pat:id="Specification">
|
| 10 |
+
<?PageStart number="1"?>
|
| 11 |
+
<pat:Heading pat:id="h-1">AMENDMENTS TO THE SPECIFICATION</pat:Heading>
|
| 12 |
+
<pat:P pat:id="p-1" pat:pNumber="1">Please replace paragraphs [0014-0019] of the originally filed specification with the following substitute paragraphs:</pat:P>
|
| 13 |
+
<pat:Heading pat:id="h-2">SUMMARY OF THE INVENTION</pat:Heading>
|
| 14 |
+
<pat:P pat:id="p-2" pat:pNumber="2">[0014] In one embodiment, the present invention includes a method for selectively imaging one or more objects in a display that comprises i) defining a visualization surface within the display using a computer processor; ii) selecting an object of interest from a plurality of objects within</pat:P>
|
| 15 |
+
<pat:P pat:id="p-3" pat:pNumber="3"><pat:PatentImage com:orientationCategory="Portrait" pat:imageWrappingStyleCategory="In front of text">
|
| 16 |
+
<com:ImageFormatCategory>SVG</com:ImageFormatCategory>
|
| 17 |
+
<com:ImageFileName>12006702.09-20-2012.H7CA1YCOPXXIFW3.SPEC.1.svg</com:ImageFileName>
|
| 18 |
+
<com:HeightMeasure com:measureUnitCode="In">0.58</com:HeightMeasure>
|
| 19 |
+
<com:WidthMeasure com:measureUnitCode="In">6.64</com:WidthMeasure>
|
| 20 |
+
<com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P>
|
| 21 |
+
<pat:P pat:id="p-4" pat:pNumber="4"> surface and an image of all object(s) remaining in the display or an image of the visualization surface and an intersection between the object(s) remaining in the display and the visualization surface, upon selecting the object of interest.</pat:P>
|
| 22 |
+
<pat:P pat:id="p-5" pat:pNumber="5">[0015] In another embodiment, the present invention includes a non-transitory computer- readable medium tangibly carrying computer executable instructions for selectively imaging one or more objects in a display, the instructions are executable to implement i) defining a visualization surface within the display; ii) selecting an object of interest from a plurality of</pat:P>
|
| 23 |
+
<pat:P pat:id="p-6" pat:pNumber="6"><pat:PatentImage com:orientationCategory="Portrait" pat:imageWrappingStyleCategory="In front of text">
|
| 24 |
+
<com:ImageFormatCategory>SVG</com:ImageFormatCategory>
|
| 25 |
+
<com:ImageFileName>12006702.09-20-2012.H7CA1YCOPXXIFW3.SPEC.2.svg</com:ImageFileName>
|
| 26 |
+
<com:HeightMeasure com:measureUnitCode="In">0.58</com:HeightMeasure>
|
| 27 |
+
<com:WidthMeasure com:measureUnitCode="In">6.64</com:WidthMeasure>
|
| 28 |
+
<com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P>
|
| 29 |
+
<pat:P pat:id="p-7" pat:pNumber="7"> visualization surface and an image of all object(s) remaining in the display or an image of the visualization surface and an intersection between the object(s) remaining in the display and the visualization surface<pat:OCRConfidenceData pat:levelNumber="5">,</pat:OCRConfidenceData> upon selecting the object of interest<pat:OCRConfidenceData pat:levelNumber="5">.</pat:OCRConfidenceData></pat:P>
|
| 30 |
+
<pat:P pat:id="p-8" pat:pNumber="8">[0016<pat:OCRConfidenceData pat:levelNumber="5">]</pat:OCRConfidenceData> In another embodiment, the present invention includes a method for selectively imaging one or more objects in a display which comprises i) defining a visualization surface within the <pat:BoundaryData><pat:HeaderText>033849<pat:OCRConfidenceData pat:levelNumber="5">/</pat:OCRConfidenceData>000157</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>136 - 559962v1</pat:HeaderText></pat:BoundaryData>
|
| 31 |
+
<?PageStart number="2"?>display using a computer processor; ii) selecting an object of interest from a plurality of objects within the display, at least one of the plurality of objects comprising a reservoir grid; and iii) displaying an image of the visualization surface<pat:OCRConfidenceData pat:levelNumber="5">,</pat:OCRConfidenceData> an intersection between the reservoir grid and the visualization surface and an image of all object(s) remaining in the display or an image of t<pat:OCRConfidenceData pat:levelNumber="88">he</pat:OCRConfidenceData> visualization surface and an intersection between the object(s) remaining in the display and the visualization surface<pat:OCRConfidenceData pat:levelNumber="5">,</pat:OCRConfidenceData> upon selecting the object of interest.</pat:P>
|
| 32 |
+
<pat:P pat:id="p-9" pat:pNumber="9">[0017<pat:OCRConfidenceData pat:levelNumber="6">]</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="5">I</pat:OCRConfidenceData>n another embodiment, the present invention includes a non-transitory computer- readable medium tangibly carrying computer executable instructions for selectively imaging one or more objects in a display, the instructions are executable to implement: i) defining a visualization surface within the display; ii) selecting an object of interest from a plurality of objects within the display at least one of the plurality of objects comprising a reservoir grid; and</pat:P>
|
| 33 |
+
<pat:P pat:id="p-10" pat:pNumber="10"><pat:PatentImage com:orientationCategory="Portrait" pat:imageWrappingStyleCategory="In front of text">
|
| 34 |
+
<com:ImageFormatCategory>SVG</com:ImageFormatCategory>
|
| 35 |
+
<com:ImageFileName>12006702.09-20-2012.H7CA1YCOPXXIFW3.SPEC.3.svg</com:ImageFileName>
|
| 36 |
+
<com:HeightMeasure com:measureUnitCode="In">1.80</com:HeightMeasure>
|
| 37 |
+
<com:WidthMeasure com:measureUnitCode="In">7</com:WidthMeasure>
|
| 38 |
+
<com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P>
|
| 39 |
+
<pat:P pat:id="p-11" pat:pNumber="11"> one or more objects in a display that is embodied on one or more computer readable media and executable on a computer that comprises i) a user input module for accepting user inputs related to defining a visualization surface within the display and selecting an object of interest from a plurality of objects within the display; ii) a visualization surface module for processing a set of instructions to determine an intersection between at least one of a plurality of objects removed from the display and the visualization surface and an intersection between all object(s) remaining in the display and the visualization surface; and iii) a rendering module for displaying only an <pat:BoundaryData><pat:HeaderText>033849<pat:OCRConfidenceData pat:levelNumber="5">/</pat:OCRConfidenceData>000157</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>136 - 559962v<pat:OCRConfidenceData pat:levelNumber="4">1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>
|
| 40 |
+
<?PageStart number="3"?>remaining in the display or an image of the visualization surface and an intersection between the</pat:P>
|
| 41 |
+
<pat:P pat:id="p-12" pat:pNumber="12"><pat:PatentImage com:orientationCategory="Portrait" pat:imageWrappingStyleCategory="In front of text">
|
| 42 |
+
<com:ImageFormatCategory>SVG</com:ImageFormatCategory>
|
| 43 |
+
<com:ImageFileName>12006702.09-20-2012.H7CA1YCOPXXIFW3.SPEC.4.svg</com:ImageFileName>
|
| 44 |
+
<com:HeightMeasure com:measureUnitCode="In">0.58</com:HeightMeasure>
|
| 45 |
+
<com:WidthMeasure com:measureUnitCode="In">6.66</com:WidthMeasure>
|
| 46 |
+
<com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P>
|
| 47 |
+
<pat:P pat:id="p-13" pat:pNumber="13"> object(s) remaining in the display and the visualization surface<pat:OCRConfidenceData pat:levelNumber="5">,</pat:OCRConfidenceData> upon selecting the object of interest.</pat:P>
|
| 48 |
+
<pat:P pat:id="p-14" pat:pNumber="14">[0019] In another embodiment, the present invention includes a platform for selectively imaging one or more objects in a display that is embodied on one or more computer readable media and executable on a computer that comprises i) a user input module for accepting user inputs related to defining a visualization surface within the display and selecting an object of interest from a plurality of objects within the display, at least one of the plurality of objects comprising a reservoir grid; ii) a visualization surface module for processing a set of instructions to determine an intersection between the reservoir grid and the visualization surface and an intersection between all object(s) remaining in the display and the visualization surface; and iii) a rendering</pat:P>
|
| 49 |
+
<pat:P pat:id="p-15" pat:pNumber="15"><pat:PatentImage com:orientationCategory="Portrait" pat:imageWrappingStyleCategory="In front of text">
|
| 50 |
+
<com:ImageFormatCategory>SVG</com:ImageFormatCategory>
|
| 51 |
+
<com:ImageFileName>12006702.09-20-2012.H7CA1YCOPXXIFW3.SPEC.5.svg</com:ImageFileName>
|
| 52 |
+
<com:HeightMeasure com:measureUnitCode="In">0.57</com:HeightMeasure>
|
| 53 |
+
<com:WidthMeasure com:measureUnitCode="In">6.65</com:WidthMeasure>
|
| 54 |
+
<com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P>
|
| 55 |
+
<pat:P pat:id="p-16" pat:pNumber="16"> image of the visualization surface and an intersection between the object(s) remaining in the display and the visualization surfa<pat:OCRConfidenceData pat:levelNumber="686">ce,</pat:OCRConfidenceData> upon selecting the object of interest.</pat:P>
|
| 56 |
+
<pat:BoundaryData><pat:HeaderText>033849<pat:OCRConfidenceData pat:levelNumber="5">/</pat:OCRConfidenceData>000157</pat:HeaderText></pat:BoundaryData>
|
| 57 |
+
<pat:BoundaryData><pat:HeaderText>136 - 559962<pat:OCRConfidenceData pat:levelNumber="55">v1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>
|
| 58 |
+
</pat:Specification></pat:SpecificationDocument>
|
applicant/12012118.xml
ADDED
|
@@ -0,0 +1,428 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>12012118</doc-number>
|
| 8 |
+
<date>2008-01-31</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">Docket Number P<confidence value="4">0</confidence>
|
| 14 |
+
7-164A Title Torsional Decoupler <boundary-data type="line-number">5 </boundary-data>
|
| 15 |
+
Field of the Invention The invention relates to a torsional decoupler, and more particularly, to a torsional decoupler having a frictional member transmitting a torque between the hub and the pulley. </p>
|
| 16 |
+
<p id="p-2" num="2">
|
| 17 |
+
<boundary-data type="line-number">
|
| 18 |
+
<confidence value="88">10</confidence>
|
| 19 |
+
</boundary-data>
|
| 20 |
+
Background of the Invention Isolators in engine accessory belt drives provide a vibration isolation function by utilizing a resilient member between the pulley and hub that is attached to the <boundary-data type="line-number">15 </boundary-data>
|
| 21 |
+
rotor of the alternator. Since the pulley and hub are connected, the relative motion between these two members is restricted. The stiffness of the resilient member is chose such that the first mode of vibration of the belt drive system is less that the firing frequency of the engine <boundary-data type="line-number">20 </boundary-data>
|
| 22 |
+
during idling. Therefore, at idle the isolator attenuates the vibration of the pulley, reducing the influence of the pulley on the rotor. Because the rotor vibration is reduced, less torque is required to be transmitted by the pulley and therefore the peak belt tensions are reduced. </p>
|
| 23 |
+
<p id="p-3" num="3">
|
| 24 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 25 |
+
As a result, there is less chance the tensioner spans will become tight, move the tensioner arm, and slacken the belt span ahead of the alternator in the belt movement direction. This reduces the possibility of belt chirp noises. Isolators are very effective during normal engine <boundary-data type="line-number">30 </boundary-data>
|
| 26 |
+
operation, but have limited functionality during start-up and shut-down. This is because the system passes through a resonance during start-up and shut down. </p>
|
| 27 |
+
<boundary-data type="header">
|
| 28 |
+
<confidence value="5">1</confidence>
|
| 29 |
+
</boundary-data>
|
| 30 |
+
<p id="p-4" num="4">
|
| 31 |
+
<page-break num="2"/>
|
| 32 |
+
To address this problem, decouplers provide a one way clutching feature. During crankshaft pulley acceleration in the engine start-up and running phases, the pulley and hub are locked to each other and the device behaves as a solid <boundary-data type="line-number">5 </boundary-data>
|
| 33 |
+
pulley. However, during the deceleration phases, the hub can rotate past or "overrun" the pulley. This is useful because it prevents the rotor inertia from creating high tensions in the tensioner span causing the tensioner arm to rotate away from the belt, thereby, avoiding belt slip <boundary-data type="line-number">10 </boundary-data>
|
| 34 |
+
noise. The decoupler may require a small torque to develop before the device actually overruns. Since there is no connection between the pulley and hub in the overrun mode, the pulley can rotate unrestricted. Decouplers function well for engine start-up and shut down events but are only <boundary-data type="line-number">15 </boundary-data>
|
| 35 |
+
somewhat adequate during engine running especially if the alternator is producing large current. </p>
|
| 36 |
+
<p id="p-5" num="5">Representative of the art is US patent no. 5,139,463 which discloses a serpentine belt drive system for an automotive vehicle in which the sequence of driven <boundary-data type="line-number">20 </boundary-data>
|
| 37 |
+
assemblies includes an alternator assembly comprising a housing and an armature assembly mounted in the housing for rotation about an armature axis. A hub structure is carried by the armature assembly outwardly of the housing for rotation therewith about the armature axis. A coil spring <boundary-data type="line-number">25 </boundary-data>
|
| 38 |
+
is disposed in operative relation between the alternator pulley and the hub structure for transmitting the driven rotational movements of the alternator pulley by the serpentine belt to the hub structure such that the armature assembly is rotated in the same direction as the alternator <boundary-data type="line-number">30 </boundary-data>
|
| 39 |
+
pulley while being capable of instantaneous relative resilient rotational movements in opposite directions with <boundary-data type="header">
|
| 40 |
+
<confidence value="8">2</confidence>
|
| 41 |
+
</boundary-data>
|
| 42 |
+
<page-break num="3"/>
|
| 43 |
+
respect to the alternator pulley during the driven rotational movement thereof. </p>
|
| 44 |
+
<p id="p-6" num="6">
|
| 45 |
+
<confidence value="8">W</confidence>
|
| 46 |
+
hat is needed is a torsional decoupler having a frictional member transmitting a torque between the hub and <boundary-data type="line-number">5 </boundary-data>
|
| 47 |
+
the pulley. The present invention meets this need. </p>
|
| 48 |
+
<p id="p-7" num="7">Summary of the Invention The primary aspect of the invention is to provide a torsional decoupler having a frictional member transmitting <boundary-data type="line-number">10 </boundary-data>
|
| 49 |
+
a torque between the hub and the pulley. </p>
|
| 50 |
+
<p id="p-8" num="8">Other aspects of the invention will be pointed out or made obvious by the following description of the invention and the accompanying drawings.</p>
|
| 51 |
+
<p id="p-9" num="9">The invention comprises a torsional decoupler <boundary-data type="line-number">15 </boundary-data>
|
| 52 |
+
comprising a hub having a hub surface, the hub surface having a profile, a pulley having a pulley surface, the pulley surface having a profile, a frictional member disposed between the hub surface and the pulley surface, the frictional member frictionally engaging at least one of <boundary-data type="line-number">20 </boundary-data>
|
| 53 |
+
the pulley surface or the hub surface, and the frictional member transmitting a torque between the hub and the pulley such that a movement occurs between the hub and the pulley. </p>
|
| 54 |
+
<p id="p-10" num="10">Brief Description of the Drawings <boundary-data type="line-number">25 </boundary-data>
|
| 55 |
+
The accompanying drawings, which are incorporated in and form a part of the specification, illustrate preferred embodiments of the present invention, and together with a description, serve to explain the principles of the invention. </p>
|
| 56 |
+
<p id="p-11" num="11">
|
| 57 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 58 |
+
Fig. 1 is an exploded view of the torsional decoupler. </p>
|
| 59 |
+
<p id="p-12" num="12">Fig. 2 is a cross-sectional view of the torsional decoupler.</p>
|
| 60 |
+
<boundary-data type="header">
|
| 61 |
+
<confidence value="8">3</confidence>
|
| 62 |
+
</boundary-data>
|
| 63 |
+
<p id="p-13" num="13">
|
| 64 |
+
<page-break num="4"/>
|
| 65 |
+
Fig. 3 is a typical engine belt drive system. </p>
|
| 66 |
+
<p id="p-14" num="14">Fig. 3A is a graph of typical engine speed during start up.</p>
|
| 67 |
+
<p id="p-15" num="15">Fig. 4 is the typical engine belt drive system shown <boundary-data type="line-number">5 </boundary-data>
|
| 68 |
+
in Fig. 3. </p>
|
| 69 |
+
<p id="p-16" num="16">Fig. 4A is a graph of typical engine speed during start up.</p>
|
| 70 |
+
<p id="p-17" num="17">Fig. 5 is a graph showing the asymmetric torque limiting nature of the device.</p>
|
| 71 |
+
<p id="p-18" num="18">
|
| 72 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 73 |
+
Fig. <confidence value="5">6</confidence>
|
| 74 |
+
is a schematic of asymmetric torque limits using hubload. </p>
|
| 75 |
+
<p id="p-19" num="19">Fig. 7 is a schematic of asymmetric torque limits using hubload.</p>
|
| 76 |
+
<p id="p-20" num="20">Fig. 8 is a graph showing transmitted torque based <boundary-data type="line-number">15 </boundary-data>
|
| 77 |
+
upon belt tension. </p>
|
| 78 |
+
<p id="p-21" num="21">Fig. 9 is a perspective view of an alternate embodiment<confidence value="8">.</confidence>
|
| 79 |
+
</p>
|
| 80 |
+
<p id="p-22" num="22">Fig. 10 is a cross-sectional view of the alternate embodiment in Fig. 9<confidence value="8">.</confidence>
|
| 81 |
+
</p>
|
| 82 |
+
<p id="p-23" num="23">
|
| 83 |
+
<boundary-data type="line-number">
|
| 84 |
+
<confidence value="88">20</confidence>
|
| 85 |
+
</boundary-data>
|
| 86 |
+
Detailed Description of the Preferred Embodiment Fig. 1 is an exploded view of the torsional decoupler. </p>
|
| 87 |
+
<p id="p-24" num="24">The inventive torsional decoupler reduces or eliminates the harmful effects of torsional vibration and high alternator <boundary-data type="line-number">25 </boundary-data>
|
| 88 |
+
inertia on accessory belt drives. High torsional vibration at a crankshaft pulley results from the torque pulses created by the firing of internal combustion (IC) engine cylinders. The frequency of this vibration is related to the RPM of the engine and the number of cylinders<confidence value="8">.</confidence>
|
| 89 |
+
</p>
|
| 90 |
+
<p id="p-25" num="25">
|
| 91 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 92 |
+
Torsional vibration at the crankshaft is transmitted through the serpentine belt to all accessories within the belt drive system. Of special concern is the alternator <boundary-data type="header">
|
| 93 |
+
<confidence value="8">4</confidence>
|
| 94 |
+
</boundary-data>
|
| 95 |
+
<page-break num="5"/>
|
| 96 |
+
since it has a relatively high inertia and a relatively "small" diameter pulley. A relatively small diameter pulley amplifies the angular vibration and together with the high inertia requires high torques to propel the <boundary-data type="line-number">5 </boundary-data>
|
| 97 |
+
alternator rotor. A high torque results in high peak belt tension. This can result in excessive tensioner arm motion leading to premature failure and belt slip resulting in chirp noises during engine start-up or shut-down. High torques can also cause violent belt flapping. The inventive <boundary-data type="line-number">10 </boundary-data>
|
| 98 |
+
decoupler reduces or eliminates theses problems. </p>
|
| 99 |
+
<p id="p-26" num="26">The decoupler comprises a hub <part-num-ref name="hub">10,</part-num-ref>
|
| 100 |
+
to which is engaged a friction member <part-num-ref name="friction member">20</part-num-ref>
|
| 101 |
+
and a pulley <part-num-ref name="pulley">30.</part-num-ref>
|
| 102 |
+
Lock ring <part-num-ref name="pulley 30. Lock ring">40</part-num-ref>
|
| 103 |
+
is used to hold the components together. </p>
|
| 104 |
+
<p id="p-27" num="27">Hub 10 comprises a grooved surface profile <part-num-ref name="grooved surface profile">11.</part-num-ref>
|
| 105 |
+
The <boundary-data type="line-number">15 </boundary-data>
|
| 106 |
+
grooves <part-num-ref name="grooves">11</part-num-ref>
|
| 107 |
+
extend parallel to an axis of rotation A-A. At one end of hub <part-num-ref name="axis of rotation A-A. At one end of hub">10</part-num-ref>
|
| 108 |
+
is a flange <part-num-ref name="flange">12.</part-num-ref>
|
| 109 |
+
Hub <part-num-ref name="flange 12. Hub">10</part-num-ref>
|
| 110 |
+
can be attached to an alternator shaft using a nut (not shown)<confidence value="8">.</confidence>
|
| 111 |
+
</p>
|
| 112 |
+
<p id="p-28" num="28">Friction member 20 comprises a length of frictional material, which may comprise plastic, or natural or <boundary-data type="line-number">20 </boundary-data>
|
| 113 |
+
synthetic rubber or similar elastomeric material. The member may comprise any conventional and/or suitable cured or thermoplastic elastomeric composition. Suitable elastomers that may be utilized for this purpose include for example polyurethane elastomers (including as well <boundary-data type="line-number">25 </boundary-data>
|
| 114 |
+
polyurethane/urea elastomers) (PU), polychloroprene rubber (CR), acrylonitrile butadiene rubber (NBR), hydrogenated NBR (HNBR), styrene-butadiene rubber (SBR), alkylated chlorosulfonated polyethylene (<confidence value="2222">ACSM</confidence>
|
| 115 |
+
), epichlorohydrin, polybutadiene rubber (BR), natural rubber (NR), and <boundary-data type="line-number">30 </boundary-data>
|
| 116 |
+
ethylene alpha olefin elastomers such as ethylene propylene copolymers (EPM), ethylene propylene diene terpolymers (EPDM), ethylene octene copolymers (EOM), ethylene butene <boundary-data type="header">
|
| 117 |
+
<confidence value="8">5</confidence>
|
| 118 |
+
</boundary-data>
|
| 119 |
+
<page-break num="6"/>
|
| 120 |
+
copolymers (EBM), ethylene octene terpolymers (EODM); and ethylene butene terpolymers (EBDM); and PPA or silicone rubber, or a combination of any two or more of the foregoing. </p>
|
| 121 |
+
<p id="p-29" num="29">
|
| 122 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 123 |
+
The pulley material can be steel, plastic or aluminum or a combination of two or more of the foregoing. </p>
|
| 124 |
+
<p id="p-30" num="30">A first outer surface 21 comprises a ribbed profile.</p>
|
| 125 |
+
<p id="p-31" num="31">Each "rib" extends in a direction that is parallel to a circumference of the member <part-num-ref name="member">20.</part-num-ref>
|
| 126 |
+
A second inner surface <part-num-ref name="second inner surface">22</part-num-ref>
|
| 127 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 128 |
+
comprises a toothed profile. A "tooth" (or groove) extends in a direction that is at <part-num-ref name="direction that is at">90<confidence value="2">0</confidence>
|
| 129 |
+
, </part-num-ref>
|
| 130 |
+
or normal, to the rib direction. In addition, the tooth is disposed normal to a direction of rotation of the pulley. </p>
|
| 131 |
+
<p id="p-32" num="32">In an alternate embodiment, the outer surface <part-num-ref name="outer surface">21</part-num-ref>
|
| 132 |
+
may <boundary-data type="line-number">15 </boundary-data>
|
| 133 |
+
comprise a toothed profile and the inner surface <part-num-ref name="inner surface">22</part-num-ref>
|
| 134 |
+
may comprise a ribbed profile. In the alternate embodiment surfaces <part-num-ref name="alternate embodiment surfaces">21,</part-num-ref>
|
| 135 |
+
<part-num-ref name="alternate embodiment surfaces 21,">22</part-num-ref>
|
| 136 |
+
would engage cooperating surfaces <part-num-ref name="would engage cooperating surfaces">11,</part-num-ref>
|
| 137 |
+
<part-num-ref name="would engage cooperating surfaces 11,">31</part-num-ref>
|
| 138 |
+
having like profiles, namely, surface <part-num-ref name="having like profiles, namely, surface">11</part-num-ref>
|
| 139 |
+
would be ribbed and surface <part-num-ref name="would be ribbed and surface">31</part-num-ref>
|
| 140 |
+
would be toothed. </p>
|
| 141 |
+
<p id="p-33" num="33">
|
| 142 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 143 |
+
Surface 22 cooperatively engages the grooved surface <part-num-ref name="grooved surface">11.</part-num-ref>
|
| 144 |
+
Member <part-num-ref name="grooved surface 11. Member">20</part-num-ref>
|
| 145 |
+
is not necessarily a continuous loop, but instead may comprise a length of material that is simply wrapped around hub <part-num-ref name="length of material that is simply wrapped around hub">10.</part-num-ref>
|
| 146 |
+
In an alternate embodiment the member <part-num-ref name="member">20</part-num-ref>
|
| 147 |
+
may be manufactured as a continuous <confidence value="8">l</confidence>
|
| 148 |
+
oop. </p>
|
| 149 |
+
<p id="p-34" num="34">
|
| 150 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 151 |
+
Pulley 30 comprises a ribbed profile on inner surface <part-num-ref name="ribbed profile on inner surface">31.</part-num-ref>
|
| 152 |
+
Surface <part-num-ref name="ribbed profile on inner surface 31. Surface">31</part-num-ref>
|
| 153 |
+
cooperatively engages surface <part-num-ref name="cooperatively engages surface">21</part-num-ref>
|
| 154 |
+
of member <part-num-ref name="of member">20.</part-num-ref>
|
| 155 |
+
Outer surface <part-num-ref name="of member 20. Outer surface">32</part-num-ref>
|
| 156 |
+
also comprises a ribbed profile for engaging a serpentine belt, see Fig. 3. Lock ring <part-num-ref name="serpentine belt, see Fig. 3. Lock ring">40</part-num-ref>
|
| 157 |
+
engages a groove <part-num-ref name="groove">13</part-num-ref>
|
| 158 |
+
in hub <part-num-ref name="in hub">10</part-num-ref>
|
| 159 |
+
to hold the torsional <part-num-ref name="torsional">30</part-num-ref>
|
| 160 |
+
decoupler together. </p>
|
| 161 |
+
<boundary-data type="header">
|
| 162 |
+
<confidence value="8">6</confidence>
|
| 163 |
+
</boundary-data>
|
| 164 |
+
<p id="p-35" num="35">
|
| 165 |
+
<page-break num="7"/>
|
| 166 |
+
Fig. 2 is a cross-sectional view of the torsional decoupler. To assemble the decoupler, surface <part-num-ref name="decoupler, surface">21</part-num-ref>
|
| 167 |
+
of member <part-num-ref name="of member">20</part-num-ref>
|
| 168 |
+
is engaged within pulley <part-num-ref name="is engaged within pulley">30</part-num-ref>
|
| 169 |
+
in contact with surface <part-num-ref name="in contact with surface">31.</part-num-ref>
|
| 170 |
+
</p>
|
| 171 |
+
<p id="p-36" num="36">The combination of pulley 30 and the surface <part-num-ref name="surface">22</part-num-ref>
|
| 172 |
+
of member <boundary-data type="line-number">5 </boundary-data>
|
| 173 |
+
<part-num-ref name="of member">20</part-num-ref>
|
| 174 |
+
is then slid into engagement with grooves <part-num-ref name="is then slid into engagement with grooves">11</part-num-ref>
|
| 175 |
+
on hub <part-num-ref name="on hub">10.</part-num-ref>
|
| 176 |
+
</p>
|
| 177 |
+
<p id="p-37" num="37">Lock ring 40 is then engaged with groove <part-num-ref name="is then engaged with groove">13.</part-num-ref>
|
| 178 |
+
Member <part-num-ref name="is then engaged with groove 13. Member">20</part-num-ref>
|
| 179 |
+
should not be subjected to any compression or preloading between hub <part-num-ref name="should not be subjected to any compression or preloading between hub">10</part-num-ref>
|
| 180 |
+
and pulley <part-num-ref name="and pulley">30</part-num-ref>
|
| 181 |
+
as part of the completed assembly. </p>
|
| 182 |
+
<p id="p-38" num="38">
|
| 183 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 184 |
+
The length of member 20 only need be sufficient to fit within pulley <part-num-ref name="only need be sufficient to fit within pulley">30</part-num-ref>
|
| 185 |
+
while engaged with surface <part-num-ref name="while engaged with surface">31.</part-num-ref>
|
| 186 |
+
The ends of member <part-num-ref name="ends of member">20</part-num-ref>
|
| 187 |
+
need not be in contact, and, a small gap (<confidence value="2414">~<_l</confidence>
|
| 188 |
+
mm) will not be detrimental to operation of the decoupler. Of course the ends may be in contact without affecting <boundary-data type="line-number">15 </boundary-data>
|
| 189 |
+
operation. </p>
|
| 190 |
+
<p id="p-39" num="39">Fig. 3 is a typical engine belt drive system. The system typically comprises an alternator (ALT) having a high inertia, an air conditioner compressor (A/C), and a crankshaft pulley (CRK). A belt (B) is entrained between <boundary-data type="line-number">20 </boundary-data>
|
| 191 |
+
each of the components. A tensioner (Ten) is engaged with the belt to apply and maintain a belt load. </p>
|
| 192 |
+
<p id="p-40" num="40">Fig. 3A is a graph of typical engine speed during start up. During portions of the start up phase when the engine is accelerating as indicated by the shaded portion <boundary-data type="line-number">25 </boundary-data>
|
| 193 |
+
"a" the belt spans after the alternator (S<confidence value="5">1</confidence>
|
| 194 |
+
) experiences high tension since positive torque is needed to accelerate the alternator inertia. The high tension causes belt stretch and the increase in belt length is accumulated in the tensioner span (S2). This causes the tensioner arm to <boundary-data type="line-number">30 </boundary-data>
|
| 195 |
+
move towards its free-arm stop. The tensioner maintains a controlled belt tension in the span before (S2) the <boundary-data type="header">
|
| 196 |
+
<confidence value="8">7</confidence>
|
| 197 |
+
</boundary-data>
|
| 198 |
+
<page-break num="8"/>
|
| 199 |
+
alternator ALT. Nothing extraordinary happens in terms of belt noise. </p>
|
| 200 |
+
<p id="p-41" num="41">Fig. 4 is the typical engine belt drive system shown in Fig. 3. Fig. 4A is a graph of typical engine speed <boundary-data type="line-number">5 </boundary-data>
|
| 201 |
+
during start up. During the phase when the engine is decelerating (shaded portion "b" in Fig. 4A) the alternator inertia will tend to continue to rotate at its current speed in relation to its inertia, at which time the alternator ALT will become the prime mover in the belt <boundary-data type="line-number">10 </boundary-data>
|
| 202 |
+
drive system. This causes the normally slack span around the tensioner (S2) to become tight. If the tension is high enough to overcome the spring load and damping in the tensioner, the tensioner arm will move towards its load stop (away from the belt), see Fig. 4. This in effect <boundary-data type="line-number">15 </boundary-data>
|
| 203 |
+
decreases the drive length and causes the belt spans before the alternator to slacken and loose tension. <confidence value="8">W</confidence>
|
| 204 |
+
hen the tension drops below some critical value, the drive will suffer from belt chirp noises. </p>
|
| 205 |
+
<p id="p-42" num="42">Fig. 5 is a graph showing the asymmetric torque <boundary-data type="line-number">20 </boundary-data>
|
| 206 |
+
limiting nature of the device. The principle of the device is to use hubload generated friction to asymmetrically limit the torque transferable through the torsional decoupler. </p>
|
| 207 |
+
<p id="p-43" num="43">Assuming positive torque transfer occurs when the <boundary-data type="line-number">25 </boundary-data>
|
| 208 |
+
pulley <part-num-ref name="pulley">30</part-num-ref>
|
| 209 |
+
is driving the hub <part-num-ref name="hub">10,</part-num-ref>
|
| 210 |
+
and negative torque transfer occurs when the hub <part-num-ref name="hub">10</part-num-ref>
|
| 211 |
+
is driving the pulley <part-num-ref name="pulley">30,</part-num-ref>
|
| 212 |
+
then it is desirable to limit the positive torque to a value slightly above that which is required by an alternator ALT to generate maximum current. This is <boundary-data type="line-number">30 </boundary-data>
|
| 213 |
+
determined by the frictional interface between surface <part-num-ref name="frictional interface between surface">21</part-num-ref>
|
| 214 |
+
and <part-num-ref name="and">31.</part-num-ref>
|
| 215 |
+
</p>
|
| 216 |
+
<boundary-data type="header">
|
| 217 |
+
<confidence value="8">8</confidence>
|
| 218 |
+
</boundary-data>
|
| 219 |
+
<p id="p-44" num="44">
|
| 220 |
+
<page-break num="9"/>
|
| 221 |
+
It is also desirable to be able to accelerate the alternator inertia and limit the negative torque to a small value to prevent the tightening of the tensioner normally slack span (S2), causing the tensioner Ten to move <boundary-data type="line-number">5 </boundary-data>
|
| 222 |
+
resulting in belt noise. </p>
|
| 223 |
+
<p id="p-45" num="45">This is demonstrated in Fig. 5. It is assumed that the coefficient of friction of the frictional interface (surfaces <part-num-ref name="frictional interface (surfaces">21,</part-num-ref>
|
| 224 |
+
<part-num-ref name="frictional interface (surfaces 21,">31)</part-num-ref>
|
| 225 |
+
is approximately 0.5 and the pulley diameter is approximately 50mm. Between approximately -5Nm <boundary-data type="line-number">10 </boundary-data>
|
| 226 |
+
and approximately +<confidence value="5">1</confidence>
|
| 227 |
+
5Nm, the frictional interface <part-num-ref name="frictional interface">(21,</part-num-ref>
|
| 228 |
+
<part-num-ref name="frictional interface (21,">31)</part-num-ref>
|
| 229 |
+
can support the torque generated at the belt (B) - pulley <part-num-ref name="belt (B) - pulley">(30)</part-num-ref>
|
| 230 |
+
interface. It is assumed that the tensioner provides approximately 300N nominal belt tension. Damping in the tensioner is present and will have some affect on the <boundary-data type="line-number">15 </boundary-data>
|
| 231 |
+
numbers in the illustrative example. </p>
|
| 232 |
+
<p id="p-46" num="46">When the hub <part-num-ref name="hub">10</part-num-ref>
|
| 233 |
+
is driving the pulley <part-num-ref name="pulley">30</part-num-ref>
|
| 234 |
+
during an engine deceleration, the tensioner span (S2) remains at the design tension of approximately 300N. However, the span <confidence value="885">(S1</confidence>
|
| 235 |
+
) after the alternator begins to loose tension. <confidence value="8">W</confidence>
|
| 236 |
+
hen <boundary-data type="line-number">20 </boundary-data>
|
| 237 |
+
the hubload reaches approximately <part-num-ref name="hubload reaches approximately">400</part-num-ref>
|
| 238 |
+
N, the frictional interface reaches its limit of approximately -5Nm and then slip occurs preventing the build-up of tension in the tensioner span. </p>
|
| 239 |
+
<p id="p-47" num="47">When the pulley <part-num-ref name="pulley">30</part-num-ref>
|
| 240 |
+
is driving the hub <part-num-ref name="hub">10,</part-num-ref>
|
| 241 |
+
the span <boundary-data type="line-number">25 </boundary-data>
|
| 242 |
+
before the pulley (S2) remains at the design tension of approximately 300N. However, the tension in span S<confidence value="5">1</confidence>
|
| 243 |
+
increases. When this tension reaches approximately 900N, the frictional interface can only support approximately <confidence value="86">+1</confidence>
|
| 244 |
+
5Nm of torque. Slip occurs beyond this point. "Hubload" <boundary-data type="line-number">30 </boundary-data>
|
| 245 |
+
refers to the sum of the tension load in each belt span across the decoupler <part-num-ref name="decoupler">100,</part-num-ref>
|
| 246 |
+
(<confidence value="5885">S1+S</confidence>
|
| 247 |
+
2). </p>
|
| 248 |
+
<boundary-data type="header">
|
| 249 |
+
<confidence value="8">9</confidence>
|
| 250 |
+
</boundary-data>
|
| 251 |
+
<p id="p-48" num="48">
|
| 252 |
+
<page-break num="10"/>
|
| 253 |
+
Fig. 6 is a schematic of asymmetric torque limits using hubload. In Fig. 6 the engine deceleration situation is illustrated. This means that the alternator shaft and hub <part-num-ref name="alternator shaft and hub">10</part-num-ref>
|
| 254 |
+
is driving the pulley <part-num-ref name="pulley">30,</part-num-ref>
|
| 255 |
+
for example, due to the <boundary-data type="line-number">5 </boundary-data>
|
| 256 |
+
inertia of the alternator shaft and rotor (not shown). The belt tension on span S<confidence value="5">1</confidence>
|
| 257 |
+
is approximately <confidence value="666">100</confidence>
|
| 258 |
+
N and the belt tension in span S2 is approximately <part-num-ref name="belt tension in span S2 is approximately">300</part-num-ref>
|
| 259 |
+
N. </p>
|
| 260 |
+
<p id="p-49" num="49">The torque being transmitted through the torsional decoupler for this condition <confidence value="668">is:</confidence>
|
| 261 |
+
</p>
|
| 262 |
+
<p id="p-50" num="50">
|
| 263 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 264 |
+
Torque = 0.<confidence value="5">5</confidence>
|
| 265 |
+
*(300+<confidence value="5">1</confidence>
|
| 266 |
+
00)*0.0<confidence value="4">5</confidence>
|
| 267 |
+
/2 = 5Nm Fig. 7 is a schematic of asymmetric torque limits using hubload. Fig. 7 is the engine accelerating condition. </p>
|
| 268 |
+
<p id="p-51" num="51">This means the pulley is driving the hub. The belt tension on span S<confidence value="4">l</confidence>
|
| 269 |
+
is approximately 900N and the belt tension in <boundary-data type="line-number">15 </boundary-data>
|
| 270 |
+
span S2 is approximately 300N. The torque transmitted through the decoupler for this condition is: </p>
|
| 271 |
+
<p id="p-52" num="52">Torque = 0.5*(300+900)*0.05/2 = <confidence value="5">1</confidence>
|
| 272 |
+
5Nm As noted elsewhere in this specification, the principal of operation of the torsional decoupler involves <boundary-data type="line-number">20 </boundary-data>
|
| 273 |
+
the frictional relationship between surface <part-num-ref name="frictional relationship between surface">21</part-num-ref>
|
| 274 |
+
and surface <part-num-ref name="and surface">31.</part-num-ref>
|
| 275 |
+
During operation, due to the frictional coefficient between surface <part-num-ref name="frictional coefficient between surface">31</part-num-ref>
|
| 276 |
+
and surface <part-num-ref name="and surface">21,</part-num-ref>
|
| 277 |
+
pulley <part-num-ref name="and surface 21, pulley">30</part-num-ref>
|
| 278 |
+
angularly progresses in a rotational + or - direction with respect to the frictional member <part-num-ref name="frictional member">20,</part-num-ref>
|
| 279 |
+
depending on the torque flow <boundary-data type="line-number">25 </boundary-data>
|
| 280 |
+
direction. That is, given two adjacent points on the pulley <part-num-ref name="pulley">30</part-num-ref>
|
| 281 |
+
and the member <part-num-ref name="member">20,</part-num-ref>
|
| 282 |
+
the points will move with respect to each other in a progressive manner during operation of the torsional decoupler. In effect, one component will be seen to "roll" with respect to the other. </p>
|
| 283 |
+
<p id="p-53" num="53">
|
| 284 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 285 |
+
The resulting angular progression is on the order of fractions of a degree per revolution of the decoupler. The hub and the pulley are frictionally engaged such that a <boundary-data type="header">
|
| 286 |
+
<confidence value="88">10</confidence>
|
| 287 |
+
</boundary-data>
|
| 288 |
+
<page-break num="11"/>
|
| 289 |
+
predetermined amount of micro-slip of the frictional engagement occurs resulting in a relative rotation, or angular progression, between the hub and pulley for each rotation of the decoupler. Further, the transmitted torque <boundary-data type="line-number">5 </boundary-data>
|
| 290 |
+
magnitude in a first direction is not equal to the transmitted torque magnitude in an opposite direction. </p>
|
| 291 |
+
<p id="p-54" num="54">This is somewhat analogous to the manner in which a tire rolls on pavement. Namely, in operation, some microslipping occurs between surface <part-num-ref name="tire rolls on pavement. Namely, in operation, some microslipping occurs between surface">21</part-num-ref>
|
| 292 |
+
and <part-num-ref name="and">31</part-num-ref>
|
| 293 |
+
as torque is <boundary-data type="line-number">10 </boundary-data>
|
| 294 |
+
being transmitted from the pulley to the frictional member, or, from the frictional member to the pulley. This characteristic is not the same as "slip" that one normally encounters, for example, when one slips on ice. The slip described for this device relates to the behavior of the <boundary-data type="line-number">15 </boundary-data>
|
| 295 |
+
materials in contact on the microscopic level. "Microslip" relates to the continuously occurring process where bonds are made and broken across the entirety of the contacting surfaces which gives the result of the surfaces moving with respect to each other, although it is not a gross "slip" <boundary-data type="line-number">20 </boundary-data>
|
| 296 |
+
that presents as part of daily experience on a macroscopic level, such as when a car slides on ice. </p>
|
| 297 |
+
<p id="p-55" num="55">As noted, surface 31 of pulley <part-num-ref name="of pulley">30</part-num-ref>
|
| 298 |
+
"rolls" upon surface <part-num-ref name=""rolls" upon surface">21</part-num-ref>
|
| 299 |
+
since the contact between surface <part-num-ref name="contact between surface">21</part-num-ref>
|
| 300 |
+
and surface <part-num-ref name="and surface">31</part-num-ref>
|
| 301 |
+
is not equal around the entire circumference. Consequently, <boundary-data type="line-number">25 </boundary-data>
|
| 302 |
+
the mechanism by which the decoupler operates is not based upon the frictional member having a resilient characteristic similar to a resilient rubber ball. </p>
|
| 303 |
+
<p id="p-56" num="56">Although resilience this is not excluded as a feature of the frictional member, the necessary feature is the <boundary-data type="line-number">30 </boundary-data>
|
| 304 |
+
suitable coefficient of friction (COF) between surfaces <part-num-ref name="suitable coefficient of friction (COF) between surfaces">21</part-num-ref>
|
| 305 |
+
and <part-num-ref name="and">31.</part-num-ref>
|
| 306 |
+
</p>
|
| 307 |
+
<boundary-data type="header">
|
| 308 |
+
<confidence value="88">11</confidence>
|
| 309 |
+
</boundary-data>
|
| 310 |
+
<p id="p-57" num="57">
|
| 311 |
+
<page-break num="12"/>
|
| 312 |
+
In the example in Fig. 6 and Fig. 7 the coefficient of friction between frictional element and pulley inner profile (surfaces <part-num-ref name="coefficient of friction between frictional element and pulley inner profile (surfaces">21,</part-num-ref>
|
| 313 |
+
<part-num-ref name="coefficient of friction between frictional element and pulley inner profile (surfaces 21,">31)</part-num-ref>
|
| 314 |
+
was approximately 0.5. This COF includes the "wedging effect" of the ribbed profile between <boundary-data type="line-number">5 </boundary-data>
|
| 315 |
+
the pulley and the frictional member surfaces. </p>
|
| 316 |
+
<p id="p-58" num="58">The inventive isolator may transmit torque in either rotational direction (+ or -) using the principles described in this specification. Further, the torque transmission magnitude can be asymmetric according to the rotational <boundary-data type="line-number">10 </boundary-data>
|
| 317 |
+
direction, meaning the magnitude of torque transmitted in one direction is not equal to the magnitude of torque transmitted in the opposite rotational direction. For the example system, operating conditions which cause transmitted torques to exceed the range of approximately -5Nm to +<confidence value="5">1</confidence>
|
| 318 |
+
5Nm <boundary-data type="line-number">15 </boundary-data>
|
| 319 |
+
may result in gross, unlimited slip between the pulley and the frictional member, or between the frictional member and the hub depending upon the configuration of the isolator. </p>
|
| 320 |
+
<p id="p-59" num="59">Since the torque transmitted is a function of hubload, changes to the hubload will contribute to changes in <boundary-data type="line-number">20 </boundary-data>
|
| 321 |
+
transmitted torque. Therefore, the amount of torque transmitted in either rotational direction can be selected as needed. </p>
|
| 322 |
+
<p id="p-60" num="60">Fig. 8 is a graph showing transmitted torque based upon belt tension. The choice of coefficient of friction <boundary-data type="line-number">25 </boundary-data>
|
| 323 |
+
value determines the limiting torque values for given hubloads. Two curves are presented. The first (I) represents the behavior of the frictional interface between surfaces <part-num-ref name="frictional interface between surfaces">21</part-num-ref>
|
| 324 |
+
and <part-num-ref name="and">31.</part-num-ref>
|
| 325 |
+
The second curve (II) represents that behavior of the interface between the belt (B) and the <boundary-data type="line-number">30 </boundary-data>
|
| 326 |
+
pulley surface <part-num-ref name="pulley surface">32.</part-num-ref>
|
| 327 |
+
The shaded area represents the operating range where torque transmission occurs. The area less than a belt tension of approximately <confidence value="666">100</confidence>
|
| 328 |
+
N and greater than <boundary-data type="header">
|
| 329 |
+
<confidence value="88">12</confidence>
|
| 330 |
+
</boundary-data>
|
| 331 |
+
<page-break num="13"/>
|
| 332 |
+
approximately 900N represents the operating range or the torsional decoupler where slip occurs. </p>
|
| 333 |
+
<p id="p-61" num="61">Fig. 9 is a perspective view of an alternate embodiment. Except as otherwise described for this Fig. 9 <boundary-data type="line-number">5 </boundary-data>
|
| 334 |
+
and Fig. 10, the description of the invention is according to Figs. 1 through Fig. 8 inclusive. </p>
|
| 335 |
+
<p id="p-62" num="62">The alternate embodiment comprises hub 100, inner bushing 2, torsion spring 50, toothed member 110, retaining members 111, 112, frictional member 20, pulley 30, torsion <boundary-data type="line-number">10 </boundary-data>
|
| 336 |
+
spring retainer 51, dust cover 8 and locking ring <part-num-ref name="and locking ring">
|
| 337 |
+
<confidence value="5">1</confidence>
|
| 338 |
+
</part-num-ref>
|
| 339 |
+
to keep the assembly together. Spring <part-num-ref name="assembly together. Spring">50</part-num-ref>
|
| 340 |
+
is compressed between the torsion spring retainer <part-num-ref name="torsion spring retainer">51</part-num-ref>
|
| 341 |
+
and flange <part-num-ref name="and flange">101</part-num-ref>
|
| 342 |
+
of the hub. </p>
|
| 343 |
+
<p id="p-63" num="63">In this alternate embodiment, toothed member 110, torsion spring 50, bushings 2 and <part-num-ref name="and">6,</part-num-ref>
|
| 344 |
+
and torsion spring <boundary-data type="line-number">15 </boundary-data>
|
| 345 |
+
retainer <part-num-ref name="and 6, and torsion spring retainer">51</part-num-ref>
|
| 346 |
+
comprise the hub assembly. The frictional decoupler member <part-num-ref name="frictional decoupler member">(20)</part-num-ref>
|
| 347 |
+
is engaged with the hub <part-num-ref name="hub">100</part-num-ref>
|
| 348 |
+
through the hub assembly. </p>
|
| 349 |
+
<p id="p-64" num="64">In yet another alternate embodiment torsion spring 50 is connected directly to friction member <part-num-ref name="is connected directly to friction member">20.</part-num-ref>
|
| 350 |
+
In Figs. 1-8 <boundary-data type="line-number">20 </boundary-data>
|
| 351 |
+
the friction member <part-num-ref name="friction member">20</part-num-ref>
|
| 352 |
+
is engaged with the hub <part-num-ref name="hub">10</part-num-ref>
|
| 353 |
+
through surface <part-num-ref name="through surface">11.</part-num-ref>
|
| 354 |
+
</p>
|
| 355 |
+
<p id="p-65" num="65">Torsion spring 50 is fixedly connected to flange <part-num-ref name="is fixedly connected to flange">101.</part-num-ref>
|
| 356 |
+
</p>
|
| 357 |
+
<p id="p-66" num="66">Toothed member 110 is fixedly connected to torsion spring retainer <part-num-ref name="is fixedly connected to torsion spring retainer">51,</part-num-ref>
|
| 358 |
+
for example by press fit. Torsion spring <boundary-data type="line-number">25 </boundary-data>
|
| 359 |
+
retainer <part-num-ref name="is fixedly connected to torsion spring retainer 51, for example by press fit. Torsion spring retainer">51</part-num-ref>
|
| 360 |
+
is slidingly engaged with hub <part-num-ref name="is slidingly engaged with hub">100</part-num-ref>
|
| 361 |
+
through bushing <part-num-ref name="through bushing">6.</part-num-ref>
|
| 362 |
+
Frictional member <part-num-ref name="through bushing 6. Frictional member">20</part-num-ref>
|
| 363 |
+
is retained on surface <part-num-ref name="is retained on surface">115</part-num-ref>
|
| 364 |
+
of toothed member <part-num-ref name="of toothed member">110</part-num-ref>
|
| 365 |
+
between retaining members <part-num-ref name="between retaining members">111,</part-num-ref>
|
| 366 |
+
<part-num-ref name="between retaining members 111,">112.</part-num-ref>
|
| 367 |
+
</p>
|
| 368 |
+
<p id="p-67" num="67">Toothed member 110 comprises a toothed surface <part-num-ref name="toothed surface">115</part-num-ref>
|
| 369 |
+
for cooperatively engaging surface <part-num-ref name="for cooperatively engaging surface">22.</part-num-ref>
|
| 370 |
+
Surfaces <part-num-ref name="for cooperatively engaging surface 22. Surfaces">21</part-num-ref>
|
| 371 |
+
and <part-num-ref name="and">31</part-num-ref>
|
| 372 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 373 |
+
interact as described elsewhere in this specification. </p>
|
| 374 |
+
<p id="p-68" num="68">Toothed member 110 is slidingly engaged with flange <part-num-ref name="is slidingly engaged with flange">101</part-num-ref>
|
| 375 |
+
through bushing <part-num-ref name="through bushing">2.</part-num-ref>
|
| 376 |
+
Bushings <part-num-ref name="through bushing 2. Bushings">2</part-num-ref>
|
| 377 |
+
and <part-num-ref name="and">6</part-num-ref>
|
| 378 |
+
provide damping <boundary-data type="header">
|
| 379 |
+
<confidence value="88">13</confidence>
|
| 380 |
+
</boundary-data>
|
| 381 |
+
<page-break num="14"/>
|
| 382 |
+
between the pulley and hub. The amount of damping is related to the coefficient of friction of the mating surfaces and hubload imparted by the belt. </p>
|
| 383 |
+
<p id="p-69" num="69">As an example, as to bushings <part-num-ref name="example, as to bushings">2</part-num-ref>
|
| 384 |
+
and <part-num-ref name="and">6,</part-num-ref>
|
| 385 |
+
<confidence value="5">O</confidence>
|
| 386 |
+
iles Techmet B <boundary-data type="line-number">5 </boundary-data>
|
| 387 |
+
bushing on steel has a COF of 0.18. The spring rate for spring <part-num-ref name="spring rate for spring">50</part-num-ref>
|
| 388 |
+
is approximately 0.27Nm/deg. The pulley diameter is approximately 56<confidence value="8">.</confidence>
|
| 389 |
+
5 mm. The numerical values are only offered as examples and are not intended to limit the breadth or scope of the invention. </p>
|
| 390 |
+
<p id="p-70" num="70">
|
| 391 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 392 |
+
In this alternate embodiment, the spring load will be significantly lower since the frictional decoupler (and the friction between pulley inner profile <part-num-ref name="friction between pulley inner profile">31</part-num-ref>
|
| 393 |
+
and frictional member surface <part-num-ref name="and frictional member surface">21)</part-num-ref>
|
| 394 |
+
will limit the amount of torque transmitted to and from the pulley <part-num-ref name="pulley">30</part-num-ref>
|
| 395 |
+
to the hub <part-num-ref name="hub">100.</part-num-ref>
|
| 396 |
+
For <boundary-data type="line-number">15 </boundary-data>
|
| 397 |
+
example, transmitted torque can be reduced from <part-num-ref name="hub 100. For example, transmitted torque can be reduced from">30</part-num-ref>
|
| 398 |
+
N-<confidence value="5">m</confidence>
|
| 399 |
+
to <part-num-ref name="N-m to">20</part-num-ref>
|
| 400 |
+
N-<confidence value="68">m.</confidence>
|
| 401 |
+
</p>
|
| 402 |
+
<p id="p-71" num="71">Torque transmitted by the decoupler is asymmetric and will not equally load the torsion spring <part-num-ref name="torsion spring">50</part-num-ref>
|
| 403 |
+
in both operating directions. In case of a prior art torsional <boundary-data type="line-number">20 </boundary-data>
|
| 404 |
+
decoupler torque is transmitted through the spring in the range of approximately -30N-m to +30N-<confidence value="5">m</confidence>
|
| 405 |
+
. In case of this alternate embodiment torque will be transmitted in the range of approximately -5N-<confidence value="5">m</confidence>
|
| 406 |
+
to +20N-m. This is a function of the hubload and the coefficient of friction between the <boundary-data type="line-number">25 </boundary-data>
|
| 407 |
+
sliding surfaces. </p>
|
| 408 |
+
<p id="p-72" num="72">Fig. 10 is a cross-sectional view of the alternate embodiment in Fig. 9. Bore <part-num-ref name="alternate embodiment in Fig. 9. Bore">102</part-num-ref>
|
| 409 |
+
receives an alternator shaft (not shown). Belt bearing surface <part-num-ref name="alternator shaft (not shown). Belt bearing surface">32</part-num-ref>
|
| 410 |
+
has a profile for engaging a multi-ribbed belt (not shown). Locking ring <part-num-ref name="multi-ribbed belt (not shown). Locking ring">30</part-num-ref>
|
| 411 |
+
<part-num-ref name="">1</part-num-ref>
|
| 412 |
+
is press fit into pulley <part-num-ref name="is press fit into pulley">30</part-num-ref>
|
| 413 |
+
in flange <part-num-ref name="in flange">33.</part-num-ref>
|
| 414 |
+
</p>
|
| 415 |
+
<boundary-data type="header">
|
| 416 |
+
<confidence value="88">14</confidence>
|
| 417 |
+
</boundary-data>
|
| 418 |
+
<p id="p-73" num="73">
|
| 419 |
+
<page-break num="15"/>
|
| 420 |
+
All numbers used in this specification are only presented as examples and are not intended to limit the breadth, interpretation or operation of the device. </p>
|
| 421 |
+
<p id="p-74" num="74">Although a form of the invention has been described <boundary-data type="line-number">5 </boundary-data>
|
| 422 |
+
herein, it will be obvious to those skilled in the art that variations may be made in the construction and relation of parts without departing from the spirit and scope of the invention described herein. </p>
|
| 423 |
+
<boundary-data type="header">
|
| 424 |
+
<confidence value="88">15</confidence>
|
| 425 |
+
</boundary-data>
|
| 426 |
+
</description>
|
| 427 |
+
</us-patent-application>
|
| 428 |
+
|
applicant/12019445.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
applicant/12022572.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>12022572</doc-number>
|
| 8 |
+
<date>2008-11-12</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.: 12/022,572 2 Docket No.: <part-num-ref name="Docket No.:">106842008500</part-num-ref>
|
| 14 |
+
</p>
|
| 15 |
+
<heading id="h-1">AMENDMENTS TO THE SPECIFICATION</heading>
|
| 16 |
+
<p id="p-2" num="2">Please insert the following paragraph before "Field of the Invention" on page <part-num-ref name="Invention" on page">1,</part-num-ref>
|
| 17 |
+
beginning at line 1: </p>
|
| 18 |
+
<p id="p-3" num="3">Cross-Reference to Related Applications Embodiments of the present invention are related to U.S. Patent Application Serial No.</p>
|
| 19 |
+
<p id="p-4" num="4">11/650,040, entitled Multi-Touch Auto Scannin<confidence value="5">g</confidence>
|
| 20 |
+
, filed on January 3, 2007. </p>
|
| 21 |
+
<p id="p-5" num="5">
|
| 22 |
+
<confidence value="288">la-</confidence>
|
| 23 |
+
1003782 </p>
|
| 24 |
+
</description>
|
| 25 |
+
</us-patent-application>
|
| 26 |
+
|
applicant/12022949.xml
ADDED
|
@@ -0,0 +1,23 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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>12022949</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">In the Specification:</p>
|
| 14 |
+
<p id="p-2" num="2">Please amend the title as follows<confidence value="5">:</confidence>
|
| 15 |
+
</p>
|
| 16 |
+
<p id="p-3" num="3">Method of Forming a Non Volatile Memory Device Using Wet Etching <confidence value="66">IN</confidence>
|
| 17 |
+
F <part-num-ref name="Non Volatile Memory Device Using Wet Etching INF">2007</part-num-ref>
|
| 18 |
+
P 52921 US Page <part-num-ref name="US Page">2</part-num-ref>
|
| 19 |
+
of <part-num-ref name="of">12</part-num-ref>
|
| 20 |
+
</p>
|
| 21 |
+
</description>
|
| 22 |
+
</us-patent-application>
|
| 23 |
+
|