Add files using upload-large-folder tool

prior_art/10484400.xml

@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<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="10484400.04-28-2014.HULDVTS1PXXIFW1.SPEC.xml" pat:id="HULDVTS1PXXIFW1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XMLSchema/V1_3/SpecificationDocument_1_0.xsd">
+<pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001">
+<pat:ApplicationHeaderDetails><pat:ApplicationNumber>10484400</pat:ApplicationNumber></pat:ApplicationHeaderDetails>
+<pat:PageTotalQuantity>1</pat:PageTotalQuantity>
+<pat:ParagraphTotalQuantity>2</pat:ParagraphTotalQuantity>
+</pat:DocumentHeaderDetails>
+<pat:MailRoomDate>2014-04-28</pat:MailRoomDate>
+<pat:Specification pat:id="Specification">
+<?PageStart number="1"?>
+<pat:BoundaryData><pat:HeaderText>Application/Control Number: 10/484,400                       Docket No.: 501059-A-US-NP(RB)</pat:HeaderText></pat:BoundaryData>
+<pat:BoundaryData><pat:HeaderText>Art Unit: 2478</pat:HeaderText></pat:BoundaryData>
+<pat:P pat:id="p-1" pat:pNumber="1">Amendment to the Specification Kindly amend the <pat:PartName pat:idref="PN-00001">paragraph sta<pat:OCRConfidenceData pat:levelNumber="66">rt</pat:OCRConfidenceData>ing on page </pat:PartName><pat:PartNumber pat:id="PN-00001">66</pat:PartNumber>, <pat:PartName pat:idref="PN-00002">line </pat:PartName><pat:PartNumber pat:id="PN-00002">7</pat:PartNumber> in the Specification as follows:</pat:P>
+<pat:P pat:id="p-2" pat:pNumber="2">Moreover, as mentioned previously, the invention can be implemented at least in part in the form of one or more software programs storable in a memory or other machine-readable storage medium, and executable by a processor of a CAS. A computer-readable storage medium or device disclosed herein expressly excludes transitory signals per se and transitory mediums such as carrier waves, wires, cables, fiber optics, infrared media, communication media, and the like.</pat:P>
+<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8">2</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>
+</pat:Specification></pat:SpecificationDocument>

prior_art/10576522.xml

@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<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="10576522.04-20-2015.I8SO0D9WPXXIFW2.SPEC.xml" pat:id="I8SO0D9WPXXIFW2" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XMLSchema/V1_3/SpecificationDocument_1_0.xsd">
+<pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001">
+<pat:ApplicationHeaderDetails><pat:ApplicationNumber>10576522</pat:ApplicationNumber></pat:ApplicationHeaderDetails>
+<pat:PageTotalQuantity>1</pat:PageTotalQuantity>
+<pat:ParagraphTotalQuantity>3</pat:ParagraphTotalQuantity>
+</pat:DocumentHeaderDetails>
+<pat:MailRoomDate>2015-04-20</pat:MailRoomDate>
+<pat:Specification pat:id="Specification">
+<?PageStart number="1"?>
+<pat:P pat:id="p-1" pat:pNumber="1">Application No.: 10/576,522 Docket No.: 7278U<pat:OCRConfidenceData pat:levelNumber="554">SO1</pat:OCRConfidenceData> (35226/06294)</pat:P>
+<pat:Heading pat:id="h-1"><pat:U>IN THE SPECIFICATION</pat:U></pat:Heading>
+<pat:P pat:id="p-2" pat:pNumber="2">Please insert the following new section after the title and before section labeled the <pat:PartName pat:idref="PN-00001">"FIELD OF <pat:OCRConfidenceData pat:levelNumber="5">I</pat:OCRConfidenceData>NVENTION" on page </pat:PartName><pat:PartNumber pat:id="PN-00001">1</pat:PartNumber> of the specification.</pat:P>
+<pat:Heading pat:id="h-2"><pat:U>CROSS-REFERENCE TO RELATED APPLICATIONS</pat:U></pat:Heading>
+<pat:P pat:id="p-3" pat:pNumber="3">This application is the U.S. national stage entry of PCT/U<pat:OCRConfidenceData pat:levelNumber="4">S</pat:OCRConfidenceData>2004/042770, with an international filing date of December 17, 2004, which claims the benefit of and priority to U.S. Provisional Patent Application Serial No. 60/531,495, entitled METHOD OF <pat:OCRConfidenceData pat:levelNumber="5">I</pat:OCRConfidenceData>NCREASING LEAN BODY MASS AND REDUCING BODY FAT MASS IN INFANTS and filed December 19, 2003, the entire disclosures of which are incorporated herein by reference in their entirety, to the extent that it is not conflicting with the present application.</pat:P>
+<pat:Heading pat:id="h-3">{02942594.D<pat:OCRConfidenceData pat:levelNumber="4">O</pat:OCRConfidenceData>C;2 <pat:OCRConfidenceData pat:levelNumber="5">}</pat:OCRConfidenceData>                   <pat:OCRConfidenceData pat:levelNumber="8">2</pat:OCRConfidenceData></pat:Heading>
+</pat:Specification></pat:SpecificationDocument>

prior_art/10580548.xml

@@ -0,0 +1,174 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>10580548</doc-number>
+        <date>2006-05-26</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">A universally a<confidence value="8">p</confidence>
+plicable virus inactivated blood <confidence value="77">pl</confidence>
+asma <confidence value="8">p</confidence>
+roduced from <confidence value="8">p</confidence>
+ortions of non-Caucasian <confidence value="8">p</confidence>
+lasma <boundary-data type="line-number">5   </boundary-data>
+The present invention relates to a blood plasma pooled from donors which are substantially of non-Caucasians, a pharmaceutical preparation comprising the blood plasma of the invention and the use of the blood plasma of the invention for the manufacturing of a medicament.    </p>
+    <p id="p-2" num="2">
+      <boundary-data type="line-number">10   </boundary-data>
+Back<confidence value="5">g</confidence>
+round of the invention Blood groups and the inherent inter-individual differences in human blood were discovered by Karl Landsteiner. The ABO blood group system comprises <part-num-ref name="ABO blood group system comprises">4</part-num-ref>
+ main phenotypes; <part-num-ref name="main phenotypes;">0,</part-num-ref>
+ A, B, and AB, the phenotype being governed by codominant alleles at the AB<confidence value="5">O</confidence>
+ locus on chromosome <part-num-ref name="ABO locus on chromosome">9.</part-num-ref>
+    </p>
+    <p id="p-3" num="3">
+      <boundary-data type="line-number">15  </boundary-data>
+Transfusion of AB<confidence value="5">O</confidence>
+-identical or compatible plasma, such as FFP of specific blood groups is an effective and generally well tolerated treatment of various types of complex or isolated coagulation factor deficiencies, in thrombotic thrombocytopenic purpura, and in repeated large volume plasma exchange.    </p>
+    <p id="p-4" num="4">However plasma transfusion in principle carries some risk of adverse events <boundary-data type="line-number">20   </boundary-data>
+among recipients, which include both transmission of infectious and non- infectious diseases.    </p>
+    <p id="p-5" num="5">Non-infectious  adverse  events  typically  occur  when  immunologic incompatibility between e.g. transfused donor red blood cells and recipient antibodies produce accelerated destruction of transfused cells. According to <boundary-data type="line-number">25  </boundary-data>
+Landsteiner's law, any human individual has antibodies in plasma if the corresponding antigen is absent from the red blood cells. For example, by infusing plasma from a group A donor to a group B patient, anti-B antibodies from donors plasma will react with and lead to destruction of the patient's red blood cells. Similarly, plasma from a group B donor, which contains anti-A <page-break num="2"/>
+      <boundary-data type="header">
+        <confidence value="8">-</confidence>
+ <confidence value="8">2</confidence>
+ <confidence value="8">-</confidence>
+      </boundary-data>
+antibodies, is incompatible with a blood group A patient; and plasma from a group <part-num-ref name="group">0</part-num-ref>
+ donor, which contains both anti-A and anti-B antibodies, is incompatible with a patient having blood group A, B, or AB. Therefore, the blood types must be matched to avoid a reaction based on ABO <boundary-data type="line-number">5   </boundary-data>
+incompatibi<confidence value="8">l</confidence>
+ity.    </p>
+    <p id="p-6" num="6">In addition to non-infectious adverse events, many infectious agents, including viruses, bacteria, and parasites, can be transmitted through blood transfusion.</p>
+    <p id="p-7" num="7">Well recognized viruses include hepatitis A virus (HA<confidence value="5">V</confidence>
+), hepatitis B Virus (HBV), hepatitis C Virus (HCV), human immunodeficiency virus types <part-num-ref name="virus (HAV), hepatitis B Virus (HBV), hepatitis C Virus (HCV), human immunodeficiency virus types">1</part-num-ref>
+ and <part-num-ref name="and">2</part-num-ref>
+ <boundary-data type="line-number">10  </boundary-data>
+(HIV-1/2), and human parvovirus (PV). The risk of transmission of viral infections is minimized by the introduction of donor screening and new test procedures, and in particular, by the introduction of virus inactivation and/or virus removal procedures. Such procedures include virus inactivation by solvent detergent treatment (EP-A-<confidence value="5">0</confidence>
+ <part-num-ref name="introduction of virus inactivation and/or virus removal procedures. Such procedures include virus inactivation by solvent detergent treatment (EP-A-0">131</part-num-ref>
+ 740), irradiation, and pasteurization, <boundary-data type="line-number">15   </boundary-data>
+or virus removal by <confidence value="22222222222222">nanoflltration</confidence>
+.    </p>
+    <p id="p-8" num="8">Solvent detergent treated human plasma with specific blood groups, such as <confidence value="222222222">Octaplas®</confidence>
+ of blood groups A, B, <part-num-ref name="B,">0,</part-num-ref>
+ or AB (Octapharma AG Switzerland), was already developed as an alternative to FFP in order to prevent virus transmission.    </p>
+    <p id="p-9" num="9">
+      <boundary-data type="line-number">20   </boundary-data>
+Universally applicable plasma in principle can be obtained by using only AB plasma, which contains neither anti-A nor anti-B antibodies (<confidence value="5">I</confidence>
+gM and IgG)<confidence value="5">,</confidence>
+ thus is compatible with any patient regardless of his blood group. However, the frequency of AB donors (4<confidence value="5">%</confidence>
+) is limited. A plasma suitable for universal transfusion is obtained, if anti-A and/or anti-B antibodies from blood group B <boundary-data type="line-number">25   </boundary-data>
+and A donors, respectively are removed and/or neutralised by optimal mixing of plasma with the different blood groups. Such neutralization of antibodies was already described (WO-A-99/07390) by mixing <part-num-ref name="different blood groups. Such neutralization of antibodies was already described (WO-A-99/07390) by mixing">6</part-num-ref>
+ to <part-num-ref name="to">10</part-num-ref>
+ parts of blood or blood plasma of blood group A, <part-num-ref name="">1</part-num-ref>
+ to <part-num-ref name="to">3</part-num-ref>
+ parts of blood or blood plasma of blood group B, and optionally <part-num-ref name="parts of blood or blood plasma of blood group B, and optionally">0</part-num-ref>
+ to 1.5 parts of blood or blood plasma of blood group <part-num-ref name="to 1.5 parts of blood or blood plasma of blood group">30</part-num-ref>
+   AB without admixing substantial amounts of blood or blood plasma derived from blood group <part-num-ref name="AB without admixing substantial amounts of blood or blood plasma derived from blood group">0.</part-num-ref>
+    </p>
+    <p id="p-10" num="10">
+      <page-break num="3"/>
+      <confidence value="58">-3</confidence>
+ <confidence value="8">-</confidence>
+ All human races in principle share the same blood system, although the frequency of the four main ABO blood groups varies in populations throughout the world. Measuring the titres of anti-A and anti-B antibodies, it was surprisingly found that not only the frequency of ABO blood groups but also <boundary-data type="line-number">5 </boundary-data>
+the titers of blood group specific antibodies differ between different ethnic groups. In the Caucasians, in general, the titers of anti-A in group B and group <part-num-ref name="titers of anti-A in group B and group">0</part-num-ref>
+ subjects tend to be higher than the titers of anti-B in group A and group <part-num-ref name="and group">0</part-num-ref>
+ subjects. On the contrary, in people with non-Caucasian background, such as African<confidence value="5">-</confidence>
+American, Hispanic or Native-American donors, anti-B is almost as <boundary-data type="line-number">10   </boundary-data>
+high as anti-A titers. Consequently, mixing Caucasian plasma with a considerable portion of non-Caucasian origin at the above mentioned ratios, no optimal neutralization of blood group specific antibodies was found. For example, by mixing of <part-num-ref name="above mentioned ratios, no optimal neutralization of blood group specific antibodies was found. For example, by mixing of">7</part-num-ref>
+ parts of blood group A plasma with <part-num-ref name="plasma with">3</part-num-ref>
+ parts of blood group B plasma, a considerable portion of which was collected from non- <boundary-data type="line-number">15   </boundary-data>
+Caucasian donors, high anti-B titres, both of <confidence value="5">I</confidence>
+gM and <confidence value="5">I</confidence>
+gG-type, were found in the plasma pool mixture.    </p>
+    <p id="p-11" num="11">Descri<confidence value="8">p</confidence>
+tion of the invention One object of the invention was to develop a further applicable virus <boundary-data type="line-number">20  </boundary-data>
+inactivated blood plasma, which is produced by optimal mixing of blood plasma of different blood groups, obtained from blood or plasma of Caucasian origin and portions of non-Caucasian donors, such as donors of African- American, Hispanic and native American origin, facilitating an optimal neutralization of blood group specific antibodies in the mixture.    </p>
+    <p id="p-12" num="12">
+      <boundary-data type="line-number">25   </boundary-data>
+This object is solved by a blood plasma for human use pooled from donors which belong to <part-num-ref name="blood plasma for human use pooled from donors which belong to">10</part-num-ref>
+ <confidence value="5">%</confidence>
+ or more to a non-Caucasian population, the plasma obtainable by mixing blood or blood plasma<confidence value="2">.</confidence>
+ of blood groups A and B, optionally AB without admixing substantial amounts of blood or blood plasma of blood group <part-num-ref name="and B, optionally AB without admixing substantial amounts of blood or blood plasma of blood group">0</part-num-ref>
+ which comprises <page-break num="4"/>
+      <boundary-data type="header">
+        <confidence value="277">-4-</confidence>
+      </boundary-data>
+- four to eight parts of blood or blood plasma from donors having the blood group A, - more than three to seven parts of blood or blood plasma from donors having the blood group B, <boundary-data type="line-number">5     </boundary-data>
+- zero to two parts of blood or blood plasma from donors having the blood group AB.    </p>
+    <p id="p-13" num="13">Fractions of blood group 0 can be present in the plasma of the invention so long as these fractions do not introduce antibodies exceeding substantially the overall A or B blood group antigen concentration.</p>
+    <p id="p-14" num="14">
+      <boundary-data type="line-number">10  </boundary-data>
+In the blood plasma product of the invention, ABO blood group specific antibodies are essentially neutralized by free blood group substances by an optimal mix of different blood groups, and therefore, this plasma can be transfused regardless of the patient's ABO blood group. Therefore, the blood plasma of the invention further reduces both, the risk of transfusion related <boundary-data type="line-number">15  </boundary-data>
+infections as well as ABO incompatibility related fatalities.    </p>
+    <p id="p-15" num="15">In another embodiment of the invention the blood plasma mixture is composed of - five to six parts of blood or blood plasma derived from donors with blood group A, <boundary-data type="line-number">20     </boundary-data>
+- four to five parts of blood or blood plasma derived from donors with blood group B, - zero to one part of blood or blood plasma derived from donors with blood group AB, and - substantially no blood or blood plasma derived from donors with blood <boundary-data type="line-number">25        </boundary-data>
+group <part-num-ref name="- four to five parts of blood or blood plasma derived from donors with blood group B, - zero to one part of blood or blood plasma derived from donors with blood group AB, and - substantially no blood or blood plasma derived from donors with blood group">0.</part-num-ref>
+    </p>
+    <p id="p-16" num="16">The ABO blood group specific antibody titre of the blood plasma of the invention is in particular lower than <part-num-ref name="invention is in particular lower than">16</part-num-ref>
+ for anti-A and anti-B <confidence value="5">I</confidence>
+gM antibodies, and lower than <part-num-ref name="for anti-A and anti-B IgM antibodies, and lower than">64</part-num-ref>
+ for anti-A and anti-B IgG antibodies. In another mixture of <page-break num="5"/>
+      <confidence value="8">-</confidence>
+ <part-num-ref name="for anti-A and anti-B IgG antibodies. In another mixture of -">
+        <confidence value="8">5</confidence>
+      </part-num-ref>
+ <confidence value="8">-</confidence>
+ the blood plasma of the invention, the titre of the anti-A and anti-B <confidence value="588">IgM</confidence>
+ antibodies is lower than <part-num-ref name="anti-A and anti-B IgM antibodies is lower than">8,</part-num-ref>
+ and the titre of anti-A and anti-B <confidence value="5">I</confidence>
+gG antibodies is lower than <part-num-ref name="titre of anti-A and anti-B IgG antibodies is lower than">32,</part-num-ref>
+ employing assays known to a skilled person and described in the European Pharmacopeia (indirect Coombs Test).    </p>
+    <p id="p-17" num="17">
+      <boundary-data type="line-number">5   </boundary-data>
+Preferably, the blood plasma of the invention is inactivated by the method of EP-A-131740,  known   as   solvent/detergent  treatment,  irradiation, pasteurisation and/or <confidence value="22222222222222">nanofiltration</confidence>
+. A typical solvent/detergent-treatment is for instance use of detergents such as oxyethylated polyphenols, like Triton-X- <part-num-ref name="typical solvent/detergent-treatment is for instance use of detergents such as oxyethylated polyphenols, like Triton-X-">100,</part-num-ref>
+ and/or polyoxyethylene derivatives of fatty acids such as Tween <part-num-ref name="typical solvent/detergent-treatment is for instance use of detergents such as oxyethylated polyphenols, like Triton-X- 100, and/or polyoxyethylene derivatives of fatty acids such as Tween">80</part-num-ref>
+ and <boundary-data type="line-number">10  </boundary-data>
+tri-N-butylphosphate (TNBP), or combinations thereof. Also medium to long- chain fatty acids or salts thereof, both saturated and unsaturated, preferably caprylic acid or its salts, can be used for virus inactivation. Other methods are irradiation, pasteurization or nanoflitration. All these methods are known to the person skilled in the art.    </p>
+    <p id="p-18" num="18">
+      <boundary-data type="line-number">15   </boundary-data>
+Preferably, the blood plasma of the invention is frozen or lyophilized.    </p>
+    <p id="p-19" num="19">The blood plasma of the invention shows coagulation activities comparable to fresh frozen plasma.</p>
+    <p id="p-20" num="20">The present invention is further illustrated by the following example.</p>
+    <p id="p-21" num="21">
+      <boundary-data type="line-number">20   </boundary-data>
+Exam<confidence value="5">p</confidence>
+le 1 <part-num-ref name="">190</part-num-ref>
+ kg of fresh frozen plasma of blood group A, <part-num-ref name="">156</part-num-ref>
+ kg of plasma of blood group B, and <part-num-ref name="kg of plasma of blood group B, and">34</part-num-ref>
+ kg plasma of blood group AB, all obtained in a considerable portion from non-Caucasian donors, are mixed after thawing at +37 <confidence value="2">*</confidence>
+C. The obtained plasma mixture is virus inactivated by using the solvent detergent <boundary-data type="line-number">25   </boundary-data>
+method. After removal of the virus inactivating reagents and freeze-drying, the amount of free anti-A and anti-B antibodies of both <confidence value="5">I</confidence>
+gM and <confidence value="4">I</confidence>
+gG-type is measured. The titre of anti-A and anti-B antibodies of <confidence value="5">I</confidence>
+gM-type is lower than <part-num-ref name="titre of anti-A and anti-B antibodies of IgM-type is lower than">8</part-num-ref>
+ and the titer of anti-A and anti-B antibodies of <confidence value="5">I</confidence>
+gG-type is lower than <part-num-ref name="titer of anti-A and anti-B antibodies of IgG-type is lower than">32<confidence value="5">.</confidence>
+      </part-num-ref>
+    </p>
+    <boundary-data type="header">
+      <confidence value="8">-</confidence>
+ <confidence value="8">6</confidence>
+ <confidence value="8">-</confidence>
+    </boundary-data>
+    <p id="p-22" num="22">
+      <page-break num="6"/>
+Exam<confidence value="5">p</confidence>
+le 2 <boundary-data type="line-number">205 </boundary-data>
+kg of fresh frozen plasma of blood group A, and <part-num-ref name="and">137</part-num-ref>
+ kg of plasma of blood <boundary-data type="line-number">group </boundary-data>
+B, all obtained in a considerable portion from non-Caucasian donors, are <boundary-data type="line-number">5   </boundary-data>
+mixed after thawing at +37 <confidence value="2">*</confidence>
+C . The same procedure as in example <part-num-ref name="same procedure as in example">1</part-num-ref>
+ was used. The titre of anti-A and anti-B antibodies of <confidence value="5">I</confidence>
+gM-type are lower than <part-num-ref name="titre of anti-A and anti-B antibodies of IgM-type are lower than">8</part-num-ref>
+ and of <confidence value="5">I</confidence>
+gG-type lower than <part-num-ref name="and of IgG-type lower than">32.</part-num-ref>
+    </p>
+  </description>
+</us-patent-application>
+

prior_art/10580609.xml

@@ -0,0 +1,285 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>10580609</doc-number>
+        <date>2006-05-25</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">
+      <confidence value="2">1</confidence>
+                  <confidence value="618721">1O/58a</confidence>
+ <confidence value="717">6o9</confidence>
+ <confidence value="7">1</confidence>
+     </p>
+    <heading id="h-1">DESCRIPTION</heading>
+    <heading id="h-2">BUSH BEARING</heading>
+    <heading id="h-3">TECHNICAL FIELD</heading>
+    <p id="p-2" num="2">The present invention relates to a bush bearing for rotatably supporting a shaft, and more particularly to a bush bearing which is secured at its outer peripheral surface to a housing, for rotatably supporting at its inner peripheral surface a shaft.</p>
+    <heading id="h-4">BACKGROUND ART</heading>
+    <p id="p-3" num="3">A bush bearing as a sliding bearing has advantages in that, as compared with a rolling bearing, the bush bearing is low-priced, and the amount of noise generated is low, so that it excels in the low noise characteristic. Because of such advantages, the bush bearings are used in numerous fields including compressors of automobiles and the like.</p>
+    <p id="p-4" num="4">The bush bearing is normally press fitted in a hole of a housing, is secured at its outer peripheral surface to the housing, and is adapted to rotatably support at its inner peripheral surface a shaft. To facilitate the press fitting into the housing hole, a tapered surface is formed at an outer peripheral surface on the end face side of the bush bearing.</p>
+    <p id="p-5" num="5">Incidentally, if a cutting tool (single point tool) is merely abutted against the outer peripheral surface on the end face side of the bush bearing to shave it off so as to form such a tapered surface, there is a possibility that very small burrs are produced on that outer peripheral surface. At the time of the press fitting of the bush bearing into the housing hole, these burrs can fall off and remain in the housing hole as dust (e.g., <page-break num="2"/>
+      <boundary-data type="header">
+        <confidence value="8">2</confidence>
+      </boundary-data>
+metal powder dust). This dust can enter between the inner peripheral surface of the bush bearing and the shaft, making it impossible to ensure smooth rotation of the shaft.    </p>
+    <p id="p-6" num="6">In addition, particularly in an aluminum-made housing, there is a possibility that the inner peripheral surface of the housing defining the hole is shaved by the burrs at the time of the press fitting of the bush bearing into the housing hole, and aluminum chips are produced. These aluminum chips can enter between the inner peripheral surface of the bush bearing and the shaft, making it impossible to ensure smooth rotation of the shaft.</p>
+    <p id="p-7" num="7">Furthermore, if the wall thickness on the end face side of the bush bearing becomes extremely small owing to the tapered surface formed, the end face side of the bush bearing becomes easily deformed in the press fitting into the housing hole, making it impossible to assure the roundness of the inner peripheral surface of the bush bearing.</p>
+    <p id="p-8" num="8">Meanwhile, if the tapered surface is formed so as to en<confidence value="8">l</confidence>
+arge the wall thickness on the end face side of the bush bearing in order to avoid this, the positioning and fixation of the bush bearing with respect to the housing hole prior to the press fitting into the housing hole become difficult; moreover, the guiding action based on the tapered surface in the press fitting into the housing hole is practically lost, possibly crushing the end face side of the bush bearing or unnecessarily enlarging the diameter of the open end of the housing hole.    </p>
+    <heading id="h-5">DISCLOSURE OF THE INVENTION</heading>
+    <p id="p-9" num="9">The present invention has been devised in view of the above-described problems, and its object is to provide a bush bearing which makes it possible to eliminate the occurrence of dust (e.g., metal powder dust, particularly aluminum chips) at the time of the press fitting into the housing hole, which makes it possible to easily <page-break num="3"/>
+      <boundary-data type="header">
+        <confidence value="8">3</confidence>
+      </boundary-data>
+perform the press fitting without crushing the open end and the like of the hole to be press fitted into, and which makes it possible to ensure the roundness of the inner peripheral surface even after the press fitting.    </p>
+    <p id="p-10" num="10">The bush bearing in accordance with a first aspect of the invention is a cylindrical bush bearing whose inner peripheral surface is a sliding surface, wherein an outer peripheral surface of the bush bearing has a cylindrical surface and a tapered surface interposed between the cylindrical surface and at least one annular axial end face of the bush bearing and formed by press forming, and if the wall thickness at the cylindrical surface of the bush bearing is assumed to be t, a difference <confidence value="4">S</confidence>
+ <confidence value="85">(=</confidence>
+ <confidence value="82">r1</confidence>
+ - r2) between a radius r<confidence value="2">1</confidence>
+ at the cylindrical surface of the bush bearing and a radius r2 at an outer peripheral edge of the one annular end face is in a range of not less than 0.<confidence value="2">i</confidence>
+t and not more than 0.3t.    </p>
+    <p id="p-11" num="11">According to the bush bearing in accordance with the first aspect, since the tapered surface is formed by press forming, no burrs are produced at the outer peripheral surface. Therefore, at the time of the press fitting into the housing hole, dust (e.g., metal powder dust, particularly aluminum chips) is not produced. Moreover, since the difference <confidence value="4">S</confidence>
+ is not less than 0.<confidence value="5">1</confidence>
+t, it is possible to secure an outer peripheral edge of the annular end face having a small diameter with respect to a hole diameter of the housing. As a result, it is possible to reliably perform the alignment with the housing hole prior to the press fitting into the housing hole, and to ensure the guiding action based on the tapered surface in the press fitting into the housing hole. In addition, since the difference <confidence value="4">S</confidence>
+ is not more than 0.3t, it is possible to secure the wall thickness of the annular end face to such an extent that the deformation of the end face side does not occur in the press fitting into the housing hole. As a result, it becomes possible to assure the roundness of the inner peripheral surface even after the press <page-break num="4"/>
+      <boundary-data type="header">
+        <confidence value="7">4</confidence>
+      </boundary-data>
+fitting.    </p>
+    <p id="p-12" num="12">In the bush bearing in accordance with the invention, the wall thickness t is not particularly limited, but it is possible to cite as a preferred example the wall thickness t of 0.5 mm to 5.0 mm, and as a more preferred example, the wall thickness t of 1.0 mm to 3.0 mm.</p>
+    <p id="p-13" num="13">As for the bush bearing in accordance with a second aspect of the invention, in the bush bearing according to the first aspect, the tapered surface extends in an axial direction continuously from the one annular end face, and the cylindrical surface extends continuously in the axial direction from the tapered surface toward another axial end face of the bush bearing.</p>
+    <p id="p-14" num="14">The bush bearing in accordance with the invention may be an endless cylindrical one (a bush bearing which does not have abutting faces), but as in a third aspect thereof the bush bearing is preferably constituted by a wrapped bush bearing in which a plate having the sliding surface on one surface is convoluted into a cylindrical shape such that the sliding surface is positioned on an inner peripheral side.</p>
+    <p id="p-15" num="15">As for the bush bearing in accordance with a fourth aspect of the invention, in the bush bearing according to the third aspect, the plate is constituted by a multilayered plate which includes a back plate coated with copper, a porous sintered metal layer adhered integrally to a copper coating layer on one surface of the back plate, and a sliding layer including a synthetic resin with which the porous sintered metal layer is impregnated, and which has self-lubricity and wear resistance, a portion of the sliding layer which includes the synthetic resin being formed on one surface of the porous sintered metal layer, and the wrapped bush bearing is formed by convoluting the multilayered plate into the cylindrical shape such that the sliding layer is positioned on the inner peripheral side.</p>
+    <boundary-data type="header">
+      <confidence value="8">5</confidence>
+    </boundary-data>
+    <p id="p-16" num="16">
+      <page-break num="5"/>
+The thickness of the copper coating layer which covers the back plate is preferably <part-num-ref name="back plate is preferably">1</part-num-ref>
+ <confidence value="2">p</confidence>
+m to <part-num-ref name="pm to">10</part-num-ref>
+  m, more preferably 3<confidence value="2">p</confidence>
+m to <part-num-ref name="m, more preferably 3pm to">5</part-num-ref>
+ <confidence value="2">p</confidence>
+m, and such a coating layer may be formed by plating treatment of the back plate.    </p>
+    <p id="p-17" num="17">As a steel plate used as the back plate, it is possible to use such as a cold rolled steel (SPCC: JIS G <part-num-ref name="cold rolled steel (SPCC: JIS G">4141)</part-num-ref>
+ or a structural rolled steel (SS: JIS G <part-num-ref name="structural rolled steel (SS: JIS G">3101)</part-num-ref>
+ having a plate thickness of 0.3 mm to 3.0 mm, preferably a plate thickness of 0.6 mm to 1.8 mm.    </p>
+    <p id="p-18" num="18">As the metal powder for forming the porous sintered metal layer, a powder of a copper alloy is used which generally passes <part-num-ref name="copper alloy is used which generally passes">100</part-num-ref>
+ mesh sieve, such as bronze, lead bronze, or phosphor bronze which excels in frictional wear characteristics as the metal itself. Depending on purposes, however, it is also possible to use a powder of an aluminum alloy or iron, other than the copper alloy. As the form of particle of this metal powder, it is possible to use one which is in lump form, spherical form, or irregular form. Preferably, the thickness of this porous sintered metal layer is generally 0.15 to 0.4 mm, particularly 0.2 to 0.3 mm. Preferably, the porosity is generally not less than 10% by volume, particularly <part-num-ref name="porosity is generally not less than 10% by volume, particularly">15</part-num-ref>
+ to 40% by volume.    </p>
+    <p id="p-19" num="19">As the synthetic resin which has self-lubricity and wear resistance and serves as the sliding layer forming material, it is possible to cite as preferred examples polytetrafluoroethylene resin, polytetrafluoroethylene resin containing a filler material such as lead or polyimide resin, polyacetal resin or oil-containing polyacetal resin containing a lubricating oil.</p>
+    <p id="p-20" num="20">As for the bush bearing in accordance with a fifth aspect of the invention, in the bush bearing according <confidence value="682">to-</confidence>
+ the fourth aspect, the tapered surface is constituted by an exposed surface of the copper coating layer.    </p>
+    <p id="p-21" num="21">As for the bush bearing in accordance with a sixth aspect of the invention, in the bush bearing according to any one of the first to fifth aspects, the tapered surface <page-break num="6"/>
+      <boundary-data type="header">
+        <confidence value="8">6</confidence>
+      </boundary-data>
+extends in the axial direction between the cylindrical surface and the one annular end face so as to be flat or convex toward an outside.    </p>
+    <p id="p-22" num="22">As for the bush bearing in accordance with a seventh aspect of the invention, in the bush bearing according to any one of the first to sixth aspects, a smooth circular arc surface is interposed between the tapered surface and the cylindrical surface. As in the bush bearing in accordance with an eighth aspect of the invention, such a smooth circular arc surface preferably has a radius of curvature which is not less than 0.1 mm and not more than 1.0 mm.</p>
+    <p id="p-23" num="23">As for the bush bearing in accordance with a ninth aspect of the invention, in the bush bearing according to any one of the first to eighth aspects, a smooth circular arc surface is interposed between the tapered surface and the one annular end face. As in the bush bearing in accordance with a 10th aspect of the invention, such a smooth circular arc surface preferably has a radius of curvature which is not less than 0.1 mm and not more than 0.5 mm.</p>
+    <p id="p-24" num="24">As for the bush bearing in accordance with a <confidence value="66">11</confidence>
+th aspect of the invention, in the bush bearing according to any one of the first to 10th aspects, an angle of intersection, <part-num-ref name="angle of intersection,">0,</part-num-ref>
+ between the tapered surface and an axial line is not less than 15<confidence value="2">*</confidence>
+ and not more than 25<confidence value="25">'.</confidence>
+    </p>
+    <p id="p-25" num="25">The tapered surface in the invention is formed by press forming, as described above, but in the press forming, the tapered surface is preferably formed by roll forming, as in the bush bearing in accordance with a 12th aspect of the invention.</p>
+    <p id="p-26" num="26">In the invention, the outer peripheral surface of the bush bearing is sufficient if it has a tapered surface interposed between the cylindrical surface and at least one annular axial end face of the bush bearing. Preferably, however, as in the bush bearing in accordance with a 13th aspect of the invention, the outer peripheral surface of the <page-break num="7"/>
+      <boundary-data type="header">
+        <confidence value="7">7</confidence>
+      </boundary-data>
+bush bearing further has, in addition to such a tapered surface, another tapered surface interposed between the cylindrical surface and the other annular axial end face of the bush bearing.    </p>
+    <p id="p-27" num="27">The other tapered surface may be formed in the same way as the aforementioned tapered surface as in the bush bearing in accordance with 14th to 22nd aspects of the invention.</p>
+    <p id="p-28" num="28">According to the invention, it is possible to provide a bush bearing which makes it possible to eliminate the occurrence of dust (e.g., metal powder dust, particularly aluminum chips) at the time of the press fitting into the housing hole, which makes it possible to easily perform the press fitting without crushing the open end and the like of the hole to be press fitted into, and which makes it possible to ensure the roundness of the inner peripheral surface even after the press fitting.</p>
+    <p id="p-29" num="29">Hereafter, a description will be given of the present invention and the mode for carrying out the invention with reference to the preferred embodiment shown in the drawings. It should be noted that the present invention is not limited to the embodiment.</p>
+    <heading id="h-6">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
+    <p id="p-30" num="30">Fig. 1 is a perspective view of a preferred embodiment of the invention;</p>
+    <p id="p-31" num="31">Fig. 2 is a cross-sectional view of the embodiment shown in Fig. 1;</p>
+    <p id="p-32" num="32">Fig. 3 is an explanatory partially enlarged cross-sectional view of the embodiment shown in Fig. 1;</p>
+    <p id="p-33" num="33">Fig. 4 is a diagram explaining a manufacturing method in accordance with the embodiment shown in Fig. 1;</p>
+    <p id="p-34" num="34">Fig. 5 is a diagram explaining the manufacturing method in accordance with <page-break num="8"/>
+      <boundary-data type="header">
+        <confidence value="8">8</confidence>
+      </boundary-data>
+the embodiment shown in Fig. 1; and Fig. 6 is a diagram explaining an example of use in accordance with the embodiment shown in Fig. 1.    </p>
+    <heading id="h-7">BEST MODE FOR CARRYING OUT THE INVENTION</heading>
+    <p id="p-35" num="35">In Figs. <confidence value="5">1</confidence>
+ to <part-num-ref name="to">3,</part-num-ref>
+ a cylindrical bush bearing <part-num-ref name="cylindrical bush bearing">1</part-num-ref>
+ in accordance with this embodiment is a wrapped bush bearing which has a cylindrical inner peripheral surface <part-num-ref name="cylindrical inner peripheral surface">2</part-num-ref>
+ serving as a sliding surface as well as an outer peripheral surface <part-num-ref name="outer peripheral surface">3,</part-num-ref>
+ and whose abutting faces <part-num-ref name="outer peripheral surface 3, and whose abutting faces">4</part-num-ref>
+ are abutted against each other.    </p>
+    <p id="p-36" num="36">The outer peripheral surface 3 includes a cylindrical surface 11; a tapered surface <part-num-ref name="tapered surface">13</part-num-ref>
+ interposed between the cylindrical surface <part-num-ref name="cylindrical surface">11</part-num-ref>
+ and one annular end face <part-num-ref name="and one annular end face">12</part-num-ref>
+ in an axial direction X and formed by press forming, or roll forming in the press forming in this embodiment; a smooth circular arc surface <part-num-ref name="smooth circular arc surface">14</part-num-ref>
+ interposed between the tapered surface <part-num-ref name="tapered surface">13</part-num-ref>
+ and the cylindrical surface 11; a smooth circular ar<confidence value="5">c</confidence>
+ surface <part-num-ref name="smooth circular arc surface">15</part-num-ref>
+ interposed between the tapered surface <part-num-ref name="tapered surface">13</part-num-ref>
+ and the end face 12; a tapered surface <part-num-ref name="tapered surface">17</part-num-ref>
+ interposed between the cylindrical surface <part-num-ref name="cylindrical surface">11</part-num-ref>
+ and the other annular end face <part-num-ref name="other annular end face">16</part-num-ref>
+ in the axial direction X and formed by press forming, or roll forming in the press forming in this embodiment; a smooth circular arc surface <part-num-ref name="smooth circular arc surface">18</part-num-ref>
+ interposed between the tapered surface <part-num-ref name="tapered surface">17</part-num-ref>
+ and the cylindrical surface 11; and a smooth circular arc surface <part-num-ref name="smooth circular arc surface">19</part-num-ref>
+ interposed between the tapered surface <part-num-ref name="tapered surface">17</part-num-ref>
+ and the end face <part-num-ref name="end face">16.</part-num-ref>
+    </p>
+    <p id="p-37" num="37">Since each of the tapered surface <part-num-ref name="tapered surface">17,</part-num-ref>
+ the circular ar<confidence value="5">c</confidence>
+ surface <part-num-ref name="circular arc surface">18,</part-num-ref>
+ and the circular arc surface <part-num-ref name="circular arc surface">19</part-num-ref>
+ is constructed in the same way as each of the tapered surface <part-num-ref name="tapered surface">13,</part-num-ref>
+ the circular ar<confidence value="5">c</confidence>
+ surface <part-num-ref name="circular arc surface">14,</part-num-ref>
+ and the circular arc surface <part-num-ref name="circular arc surface">15,</part-num-ref>
+ a detailed description will be given hereafter of the side of the tapered surface <part-num-ref name="tapered surface">13,</part-num-ref>
+ the circular arc surface <part-num-ref name="circular arc surface">14,</part-num-ref>
+ and the circular ar<confidence value="5">c</confidence>
+ surface <part-num-ref name="circular arc surface">15,</part-num-ref>
+ and a description of the side of the tapered surface <part-num-ref name="tapered surface">17,</part-num-ref>
+ the <page-break num="9"/>
+      <boundary-data type="header">
+        <confidence value="8">9</confidence>
+      </boundary-data>
+circular ar<confidence value="5">c</confidence>
+ surface <part-num-ref name="circular arc surface">18,</part-num-ref>
+ and the circular arc surface <part-num-ref name="circular arc surface">19</part-num-ref>
+ will be omitted.    </p>
+    <p id="p-38" num="38">The tapered surface 13, which extends between the cylindrical surface <part-num-ref name="cylindrical surface">11</part-num-ref>
+ and the end face <part-num-ref name="end face">12</part-num-ref>
+ in such a manner as to be inclined in the axial direction X and is constituted by an exposed surface of a copper coating layer <part-num-ref name="copper coating layer">31,</part-num-ref>
+ extends in the axial direction X continuously from the end face <part-num-ref name="end face">12</part-num-ref>
+ through the circular arc surface <part-num-ref name="circular arc surface">15</part-num-ref>
+ so as to be flat or convex toward the outside with a radius of curvature R<confidence value="2">1</confidence>
+. The cylindrical surface <part-num-ref name="cylindrical surface">11</part-num-ref>
+ extends continuously in the axial direction X from the tapered surface <part-num-ref name="tapered surface">13</part-num-ref>
+ through the circular arc surface <part-num-ref name="circular arc surface">14</part-num-ref>
+ toward the end face <part-num-ref name="end face">16</part-num-ref>
+ in the axial direction X and parallel to the axial direction X.    </p>
+    <p id="p-39" num="39">The smooth circular arc surface 14 interposed between the tapered surface <part-num-ref name="tapered surface">13</part-num-ref>
+ and the cylindrical surface <part-num-ref name="cylindrical surface">11</part-num-ref>
+ has a radius of curvature R2 which is not less than 0.1 mm and not more than 1.0 mm. The smooth circular ar<confidence value="5">c</confidence>
+ surface <part-num-ref name="smooth circular arc surface">15</part-num-ref>
+ interposed between the tapered surface <part-num-ref name="tapered surface">13</part-num-ref>
+ and the end face <part-num-ref name="end face">12</part-num-ref>
+ has a radius of curvature R3 which is not less than 0.1 mm and not more than 0.5 mm. An angle of intersection, <part-num-ref name="angle of intersection,">0,</part-num-ref>
+ between the tapered surface <part-num-ref name="tapered surface">13</part-num-ref>
+ and an axial line <part-num-ref name="axial line">20</part-num-ref>
+ is not less than <part-num-ref name="is not less than">15<confidence value="2">0</confidence>
+      </part-num-ref>
+ and not more than 25<confidence value="25">*.</confidence>
+    </p>
+    <p id="p-40" num="40">If the wall thickness at the cylindrical surface <part-num-ref name="cylindrical surface">11</part-num-ref>
+ of the bush bearing <part-num-ref name="bush bearing">1</part-num-ref>
+ is assumed to be t, a difference <part-num-ref name="difference">
+        <confidence value="2">8</confidence>
+      </part-num-ref>
+ <confidence value="85">(=</confidence>
+ <confidence value="82">r1</confidence>
+ - r2) between a radius r<confidence value="2">1</confidence>
+ at the cylindrical surface <part-num-ref name="cylindrical surface">11</part-num-ref>
+ of the bush bearing <part-num-ref name="bush bearing">1</part-num-ref>
+ and a radius r2 at an outer peripheral edge <part-num-ref name="outer peripheral edge">32</part-num-ref>
+ of the end face <part-num-ref name="end face">12</part-num-ref>
+ is in a range of not less than 0.<confidence value="5">l</confidence>
+t and not more than 0.3t.    </p>
+    <p id="p-41" num="41">The bush bearing 1 may be manufactured as follows. Namely, a press roller <part-num-ref name="press roller">52</part-num-ref>
+ having a cylindrical surface <part-num-ref name="cylindrical surface">51</part-num-ref>
+ as well as a press roller <part-num-ref name="press roller">54</part-num-ref>
+ having an annular recessed surface <part-num-ref name="annular recessed surface">53</part-num-ref>
+ of a shape complementary to the outer peripheral surface <part-num-ref name="outer peripheral surface">3,</part-num-ref>
+ such as those shown in Figs. 4 and <part-num-ref name="and">5,</part-num-ref>
+ are prepared. A belt-shaped plate <part-num-ref name="belt-shaped plate">65</part-num-ref>
+ consisting of a multilayered plate is inserted into a space <part-num-ref name="space">55</part-num-ref>
+ formed by the cylindrical surface <part-num-ref name="cylindrical surface">51</part-num-ref>
+ of the <page-break num="10"/>
+      <boundary-data type="header">
+        <confidence value="88">10</confidence>
+      </boundary-data>
+press roller <part-num-ref name="press roller">52</part-num-ref>
+ and the annular recessed surface <part-num-ref name="annular recessed surface">53</part-num-ref>
+ of the press roller <part-num-ref name="press roller">54,</part-num-ref>
+ wherein the multilayered plate includes a back plate <part-num-ref name="back plate">61</part-num-ref>
+ coated with copper serving as the coating layer <part-num-ref name="coating layer">31,</part-num-ref>
+ a porous sintered metal layer <part-num-ref name="porous sintered metal layer">63</part-num-ref>
+ adhered integrally to the copper coating layer <part-num-ref name="copper coating layer">31</part-num-ref>
+ on one surface <part-num-ref name="on one surface">62</part-num-ref>
+ of the back plate <part-num-ref name="back plate">61,</part-num-ref>
+ and a sliding layer <part-num-ref name="sliding layer">64</part-num-ref>
+ including a synthetic resin with which the porous sintered metal layer <part-num-ref name="porous sintered metal layer">63</part-num-ref>
+ is impregnated, and which has self-lubricity and wear resistance, a portion of the layer <part-num-ref name="layer">64</part-num-ref>
+ being formed on one surface of the porous sintered metal layer <part-num-ref name="porous sintered metal layer">63.</part-num-ref>
+ This plate <part-num-ref name="porous sintered metal layer 63. This plate">65</part-num-ref>
+ is subjected to roll forming by the press rollers <part-num-ref name="press rollers">52</part-num-ref>
+ and <part-num-ref name="and">54</part-num-ref>
+ which rotate, thereby forming on one surface <part-num-ref name="which rotate, thereby forming on one surface">66</part-num-ref>
+ of the plate <part-num-ref name="plate">65</part-num-ref>
+ a surface corresponding to the tapered surfaces <part-num-ref name="tapered surfaces">13</part-num-ref>
+ and <part-num-ref name="and">17</part-num-ref>
+ and the circular ar<confidence value="5">c</confidence>
+ surfaces <part-num-ref name="circular arc surfaces">14,</part-num-ref>
+ <part-num-ref name="circular arc surfaces 14,">15,</part-num-ref>
+ <part-num-ref name="circular arc surfaces 14, 15,">18,</part-num-ref>
+ and <part-num-ref name="circular arc surfaces 14, 15, 18, and">19.</part-num-ref>
+ Subsequently, the plate <part-num-ref name="plate">65,</part-num-ref>
+ which consists of such a multilayered plate and has on one surface a sliding surface <part-num-ref name="sliding surface">67</part-num-ref>
+ constituted by the exposed surface of the sliding layer <part-num-ref name="sliding layer">64</part-num-ref>
+ and on the other surface the surface <part-num-ref name="surface">66</part-num-ref>
+ constituted by the exposed surface of the coating layer <part-num-ref name="coating layer">31,</part-num-ref>
+ is cut into an appropriate length to thereby form the plate <part-num-ref name="plate">65</part-num-ref>
+ in the form of a strip. The strip-shaped plate <part-num-ref name="strip-shaped plate">65</part-num-ref>
+ thus obtained is convoluted into a cylindrical shape such that the sliding surface <part-num-ref name="sliding surface">67</part-num-ref>
+ is positioned on the inner peripheral side. After this convolution, the thus convoluted plate <part-num-ref name="thus convoluted plate">65</part-num-ref>
+ is subjected to upsetting, as required, to arrange the cylindrical shape, thereby obtaining the wrapped bush bearing <part-num-ref name="wrapped bush bearing">1</part-num-ref>
+ shown in Figs. 1 to <part-num-ref name="to">3.</part-num-ref>
+    </p>
+    <p id="p-42" num="42">According to the bush bearing <part-num-ref name="bush bearing">1,</part-num-ref>
+ since the tapered surface <part-num-ref name="tapered surface">13</part-num-ref>
+ is formed by roll forming, no burrs are produced at the outer peripheral surface <part-num-ref name="outer peripheral surface">3.</part-num-ref>
+ As a result, for example, at the time of press fitting into a hole <part-num-ref name="hole">72</part-num-ref>
+ of an aluminum-made housing <part-num-ref name="aluminum-made housing">71</part-num-ref>
+ of a compressor of an automobile, such as the one shown in Fig. 6, copper powder dust of the coating layer <part-num-ref name="coating layer">31</part-num-ref>
+ due to burrs is not produced. Further, since an inner peripheral surface <part-num-ref name="inner peripheral surface">73</part-num-ref>
+ of the housing <part-num-ref name="housing">71</part-num-ref>
+ defining the hole <part-num-ref name="hole">72</part-num-ref>
+ is not shaved by the burrs, aluminum chips are not produced. Moreover, since the difference <part-num-ref name="difference">
+        <confidence value="1">6</confidence>
+      </part-num-ref>
+ is not less than <confidence value="2222">0.lt</confidence>
+, it is <page-break num="11"/>
+      <boundary-data type="header">
+        <confidence value="88">11</confidence>
+      </boundary-data>
+possible to secure the outer peripheral edge <part-num-ref name="outer peripheral edge">32</part-num-ref>
+ of the annular end face <part-num-ref name="annular end face">12</part-num-ref>
+ having a small diameter (= 2<confidence value="2">-</confidence>
+r2) with respect to a hole diameter r3 of the housing <part-num-ref name="housing">71.</part-num-ref>
+ As a result, it is possible to reliably perform the alignment with the hole <part-num-ref name="hole">72</part-num-ref>
+ of the housing <part-num-ref name="housing">71</part-num-ref>
+ prior to the press fitting into the hole <part-num-ref name="hole">72</part-num-ref>
+ of the housing <part-num-ref name="housing">71,</part-num-ref>
+ and to ensure the guiding action based on the tapered surface <part-num-ref name="tapered surface">13</part-num-ref>
+ in the press fitting into the hole <part-num-ref name="hole">72</part-num-ref>
+ of the housing <part-num-ref name="housing">71.</part-num-ref>
+    </p>
+    <p id="p-43" num="43">In addition, since the difference <confidence value="4">S</confidence>
+ is not more than <confidence value="5">0</confidence>
+.3t, it is possible to secure the wall thickness (radial width) of the end face <part-num-ref name="end face">12</part-num-ref>
+ to such an extent that the deformation of the end face <part-num-ref name="end face">12</part-num-ref>
+ side does not occur in the press fitting into the hole <part-num-ref name="hole">72</part-num-ref>
+ of the housing <part-num-ref name="housing">71.</part-num-ref>
+    </p>
+    <p id="p-44" num="44">As a result, it becomes possible to assure the roundness of the inner peripheral surface <part-num-ref name="inner peripheral surface">2</part-num-ref>
+ even after the press fitting with an interference.    </p>
+  </description>
+</us-patent-application>
+

prior_art/10583536.xml

@@ -0,0 +1,777 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>10583536</doc-number>
+        <date>2006-06-15</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">
+      <confidence value="4">I</confidence>
+AP12 Rec<confidence value="5">'</confidence>
+d PCT/PT<confidence value="6">O</confidence>
+ <confidence value="4">1</confidence>
+5 JUN <part-num-ref name="JUN">2006</part-num-ref>
+ <confidence value="88">WO</confidence>
+ 2005/058580                               PCT<confidence value="5">/</confidence>
+KR2004/0033<confidence value="68">41</confidence>
+     </p>
+    <heading id="h-1">ARRANGEMENT AND METHOD FOR MANUFACTURING <confidence value="2">P</confidence>
+ET BOTTLE WITH    </heading>
+    <heading id="h-2">HANDLE FORMED AT BODY PART BY INJECTION BLOW MOLDING, AND</heading>
+    <heading id="h-3">PET BOTTLE MANUFACTURED BY THEM</heading>
+    <p id="p-2" num="2">[Technical Field<confidence value="5">]</confidence>
+ <boundary-data type="line-number">5        </boundary-data>
+The  present  in<confidence value="8">v</confidence>
+ention  relates  to  a method   for manufacturing a polyethylene terephthalate (which will be referred to as "PET") bottle having a handle formed on a body and a PET bottle manufactured thereby, and, more particularly, to arrangement and method for manufacturing <confidence value="8">a</confidence>
+ <boundary-data type="line-number">10  </boundary-data>
+PET bottle having a handle formed on a body through a continuous process by an injection blow molding method, and a PET bottle manufactured thereby.    </p>
+    <p id="p-3" num="3">[Background Art] <confidence value="5">I</confidence>
+n general, thermal plasticity is a measure of the <boundary-data type="line-number">15  </boundary-data>
+ability of a material, such as plastics, to be softened or melted by heating so that, when the softened or melted material is pushed into the mold or compressed against a inner wall of the mold, the material can be variously changed in shape according to the shape of a mold, and then <boundary-data type="line-number">20  </boundary-data>
+to be solidified when the material is cooled.    </p>
+    <p id="p-4" num="4">Methods of manufacturing a bottle by taking advantage of the thermal plasticity of plastics include a blow molding method, which is mainly used for manufacturing hollow products, such as a bottle.    Basically, the blow <boundary-data type="line-number">25  </boundary-data>
+molding method comprises pre-molding a (test tube-shaped) resin pipe at an appropriate temperature, what is referred to as a parison or preform, through extrusion or injection, inserting the parison into a mold having a cavity formed therein, and blowing air into the preform to expand the <part-num-ref name="">30</part-num-ref>
+  parison into a shape corresponding to the shape of the cavity. Such blow molding methods are generally applied to <page-break num="2"/>
+      <boundary-data type="header">WO 2005/058580                               PCT<confidence value="5">/</confidence>
+KR200<confidence value="5">4</confidence>
+/0033<confidence value="68">41</confidence>
+      </boundary-data>
+thermoplastic resins, and include an extrusion or direct blow molding method,<confidence value="5">.</confidence>
+ an injection blow molding method, a stretch  blow   molding  method,   and   the  like.     In manufacturing of the PET bottles, the injection stretch <boundary-data type="line-number">5  </boundary-data>
+blow molding method has been widely used The extrusion blow molding method is a molding method in which a blowing operation is<confidence value="2">-</confidence>
+ performed after extruding melted resin using an extruder, and, more specifically, comprises   forming   a   pipe-shaped  parison   using   a <boundary-data type="line-number">10  </boundary-data>
+thermoplastic resin supplied from a hopper and then melted within an extrusion screw, blowing the parison to be expanded to a predetermined shape within a mold, cooling the parison having the predetermined shape to provide a desired product of a predetermined shape, and ejecting the product <boundary-data type="line-number">15  </boundary-data>
+from the mold.    </p>
+    <p id="p-5" num="5">The extrusion blow molding method has advantages in that it is possible to form a container having a large volume, and a container having a handle, and in that it can be applied to molding of most plastic materials, such as <boundary-data type="line-number">20  </boundary-data>
+polyethylene (PE), polypropylene (PP), polyvinyl chloride (PVC), and the like.   However, the extrusion blow molding method has a disadvantage in that it cannot be applied to PET materials having a property of low melt strength.    </p>
+    <p id="p-6" num="6">In order to allow the extrusion blow molding method to <boundary-data type="line-number">25  </boundary-data>
+be applied to such PET materials, a modified PET resin is often used, but it is more expensive than typical PET resins while having fewer applications than stretched PET resin.    </p>
+    <p id="p-7" num="7">Meanwhile, the injection blow molding is a molding method combining an injection molding and the blow molding <boundary-data type="line-number">30  </boundary-data>
+method, and, unlike the extruding step for the parison in the extrusion blow molding method, it comprises injecting a parison or a preform stick into an injection mold, and blowing the parison in a blow mold.    </p>
+    <p id="p-8" num="8">As described above, in the case of the PET r<confidence value="7">e</confidence>
+sin with <part-num-ref name="PET resin with">35</part-num-ref>
+  the low melt strength, since it is difficult to apply the     </p>
+    <heading id="h-4">
+      <confidence value="21">L.</confidence>
+    </heading>
+    <boundary-data type="header">
+      <confidence value="88">WO</confidence>
+ 2005/058580                                PCT<confidence value="5">/</confidence>
+KR2004<confidence value="5">/</confidence>
+0033<confidence value="68">41</confidence>
+    </boundary-data>
+    <p id="p-9" num="9">
+      <page-break num="3"/>
+extrusion blow molding method thereto due to a draw down phenomenon on the parison, the injection blow molding method which does not cause the draw down phenomenon on the parison is usually used in the art. In particular, in the case of <boundary-data type="line-number">5  </boundary-data>
+the PET resin, the injection stretch blow molding method is mainly  applied,  which   bi-axially  stretches  a  parison longitudinally by means of a stretch rod while blowing the parison within the blow mold.    </p>
+    <p id="p-10" num="10">When producing the containers having the handle formed <boundary-data type="line-number">10  </boundary-data>
+on the body by means of the extrusion blow molding method, since a   portion  corresponding  to  the  handle  must  be compressed together. with rest portions of the parison during a process of compressing the parison between mold halves, the parison must be extruded to a pipe shape having a large <boundary-data type="line-number">15  </boundary-data>
+diameter. Moreover, since the parison must be expanded to a predetermined shape corresponding to that of a cavity in the mold as soon as the parison is extruded to the pipe shape, operations such as temperature treatment and the like cannot be smoothly performed, thereby making     it difficult   to <boundary-data type="line-number">20  </boundary-data>
+manufacture  a   container  having   a  uniform   thickness.    </p>
+    <p id="p-11" num="11">Moreover, since   the  mold  asymmetrically  surrounds  the parison, it is difficult to manufacture a container having a uniform thickness, and there is an increase of unnecessary portions, which must be removed after ejection of products <boundary-data type="line-number">25  </boundary-data>
+from the mold.    </p>
+    <p id="p-12" num="12">In comparison to the extrusion blow molding method, the injection blow molding method has advantages in that it can provide a molded product with even distribution of the mate<confidence value="8">r</confidence>
+ial in the product while having uniformity in weight, <boundary-data type="line-number">30  </boundary-data>
+volume and thickness of the product, and in that a design molding of a neck requiring accuracy is possible. However, there are disadvantages in that it is necessary to provide a highly advanced technology, especially, in manufacturing a mold and in a molding method, and to install two. types of <part-num-ref name="molding method, and to install two. types of">35</part-num-ref>
+  mold. Moreover, unlike the extrusion blow molding method, <boundary-data type="header">
+        <confidence value="8">3</confidence>
+      </boundary-data>
+      <page-break num="4"/>
+      <boundary-data type="header">WO 2005/058580                               PCT<confidence value="68">/K</confidence>
+R2004/0033<confidence value="68">41</confidence>
+      </boundary-data>
+there is a problem in that the injection blow molding method cannot form the container having the handle formed on the body.    </p>
+    <p id="p-13" num="13">[Disclosure] <boundary-data type="line-number">5   </boundary-data>
+[Technical Problem] Therefore, the present invention has been made in view of the above problems, and it is an object of the <boundary-data type="line-number">
+        <confidence value="2">-</confidence>
+         </boundary-data>
+present invention to provide arrangement and method for manufacturing a PET bottle having a handle formed on a body <boundary-data type="line-number">10  </boundary-data>
+through an injection blow molding method, designed to allow the PET bottle having the handle formed on the body, which cannot be manufactured by the conventional <confidence value="5">-</confidence>
+injection blow molding method, to be manufactured in such a manner that the handle is formed on the body during a process of <boundary-data type="line-number">15  </boundary-data>
+blowing, as with an extrusion blow molding method, and a PET bottle manufactured thereby.    </p>
+    <p id="p-14" num="14">[Technical Solution<confidence value="5">]</confidence>
+ In accordance with an aspect of the present invention, the above and other objects can be accomplished by the <boundary-data type="line-number">20  </boundary-data>
+provision of an arrangement for manufacturing a PET bottle having a handle formed on a body, comprising: a preform blow mold for blowing air into a preform to expand the preform in a predetermined ratio to a complete shape so as to allow a handle section to be compressed; a blow mold <boundary-data type="line-number">25  </boundary-data>
+havi<confidence value="8">n</confidence>
+g a handle forming portion for compressing both sides of the bottle to form     the handle section; a cutting apparatus including a mold punch for cutting off the compressed portion of the handle section compressed by the handle forming portion; a bonding apparatus for bonding the <boundary-data type="line-number">30  </boundary-data>
+compressed portion of the handle section compressed by the handle forming portion or a cut-off portion remaining in <boundary-data type="header">
+        <confidence value="8">4</confidence>
+      </boundary-data>
+      <page-break num="5"/>
+      <boundary-data type="header">WO 2005/058580                               PCT/KR200<confidence value="5">4</confidence>
+/0033<confidence value="68">41</confidence>
+      </boundary-data>
+the handle section after cutting off the compressed portion of the handle section by the cutting apparatus; and a conveyer for conveying the preform or the molded PET bottle while clamping a neck of the preform or a neck of the <boundary-data type="line-number">5  </boundary-data>
+molded PET bottle.    </p>
+    <p id="p-15" num="15">In accordance with another aspect of the present invention, a method of manufacturing a PET bottle having a handle formed on a body is provided, comprising the steps of: a) performing a     first blowing operation to blow <boundary-data type="line-number">10  </boundary-data>
+compressed air into a test tube-shaped preform in order to form a first hollow PET container after heating the test tube-shaped preform manufactured by injection molding and conveying the preform to a preform blow mold; b) performing a second blowing operation to blow compressed air into the <boundary-data type="line-number">
+        <confidence value="884">15.</confidence>
+       </boundary-data>
+first PET containerin order to form a second PET container having a handle section formed thereon after conveying the first PET container to a blow mold having a. handle forming portion; c) cutting off a compressed portion of the second PET container using a mold punch in a cutting mold for <boundary-data type="line-number">
+        <confidence value="884">20'</confidence>
+       </boundary-data>
+cutting off the compressed portion of the handle section in order to form a third PET container after conveying the second PET container to the cutting mold; and d) injection molding a cut-off portion in the handle section of the third PET container remaining after the step c) into a <boundary-data type="line-number">25  </boundary-data>
+predetermined shape in order to form a fourth PET container after conveying the third PET container to an insert injection mold for injection molding the cut-off portion of the handle section remaining after the step c)<confidence value="5">.</confidence>
+    </p>
+    <p id="p-16" num="16">
+      <confidence value="6">-</confidence>
+ In accordance with yet another aspect of the present <boundary-data type="line-number">30  </boundary-data>
+invention, a PET bottle manufactured by the arrangement or the method as described above is provided.    </p>
+    <p id="p-17" num="17">
+      <confidence value="5">[</confidence>
+Description of Drawings] The above and other objects, features and other <boundary-data type="header">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+      <page-break num="6"/>
+      <boundary-data type="header">WO 2005/058580                               PCT<confidence value="5">/</confidence>
+KR200<confidence value="5">4</confidence>
+/0033<confidence value="68">41</confidence>
+      </boundary-data>
+advantages of the present invention will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings, in which:    </p>
+    <p id="p-18" num="18">Figs. 1 to <part-num-ref name="to">3</part-num-ref>
+ are cross-sectional views illustrating a <boundary-data type="line-number">5  </boundary-data>
+conventional process of manufacturing a preform by means of an injection molding method;    </p>
+    <p id="p-19" num="19">Fig. 4 is a perspective view i<confidence value="8">l</confidence>
+lustr<confidence value="8">a</confidence>
+ting an overall construction of an arrangement for manufacturing a PET bottle having   a handle formed on     a body through   an <boundary-data type="line-number">10  </boundary-data>
+injection blow molding method     in accordance with   the present invention;    </p>
+    <p id="p-20" num="20">Fig. 5 is a top view illustrating the arrangement shown in Fig. 4;</p>
+    <p id="p-21" num="21">Figs. 6 to <part-num-ref name="to">10</part-num-ref>
+ are perspective views illustrating <boundary-data type="line-number">15  </boundary-data>
+products obtained at respective steps during an injection blow molding process for forming a PET bottle having a handle formed on a body in accordance with Embodiment <part-num-ref name="body in accordance with Embodiment">1</part-num-ref>
+ of the present invention;    </p>
+    <p id="p-22" num="22">Figs. 11 to    <part-num-ref name="to">15</part-num-ref>
+ are   schematic perspective views <boundary-data type="line-number">20  </boundary-data>
+illustrating apparatuses used for the respective steps during the injection blow molding process for forming the PET bottle having the handle      formed on the body    in accordance with Embodiment <part-num-ref name="body    in accordance with Embodiment">1</part-num-ref>
+ of the present invention;    </p>
+    <p id="p-23" num="23">Figs. 16 and <part-num-ref name="and">17</part-num-ref>
+ are perspective views illustrating <boundary-data type="line-number">25  </boundary-data>
+products obtained by the third step and the fourth step of a method in accordance with Embodiment <part-num-ref name="method in accordance with Embodiment">2</part-num-ref>
+ of the present invention; and Fig. 18 is a perspective view illustrating products obtained by the fifth step of a method in accordance with <boundary-data type="line-number">30  </boundary-data>
+Embodiment <part-num-ref name="method in accordance with Embodiment">3</part-num-ref>
+ of the present invention.    </p>
+    <p id="p-24" num="24">
+      <confidence value="5">[</confidence>
+Best Mode<confidence value="5">]</confidence>
+ Reference  will  now   be  made  in  detail. to   the embodiments of the present invention with reference to the <boundary-data type="header">
+        <confidence value="8">6</confidence>
+      </boundary-data>
+      <page-break num="7"/>
+      <boundary-data type="header">WO 2005/058580                               PCT<confidence value="5">/</confidence>
+KR2004/0033<confidence value="68">41</confidence>
+      </boundary-data>
+accompanying drawings, wherein like components will be denoted by like reference numerals throughout the drawings.    </p>
+    <p id="p-25" num="25">Embodiment 1 Figs. 1 to <part-num-ref name="to">3</part-num-ref>
+ are cross-sectional views illustrating a <boundary-data type="line-number">5  </boundary-data>
+conventional process of manufacturing a preform by means of injection molding.    </p>
+    <p id="p-26" num="26">As descried above, for forming a PET bottle having a handle formed on a body through an injection blow molding method (more preferably, an injection stretch blow molding <boundary-data type="line-number">10  </boundary-data>
+method), first, a test tube-shaped preform <part-num-ref name="test tube-shaped preform">10</part-num-ref>
+ is formed. As shown in the drawings, the preform <part-num-ref name="preform">10</part-num-ref>
+ is formed to a test tube shape by injecting resin around a core mold <part-num-ref name="core mold">5</part-num-ref>
+ by a cavity mold <part-num-ref name="cavity mold">3,</part-num-ref>
+ which is an injection mold. At this time, the injection mold has a gap formed between the core mold <part-num-ref name="core mold">5</part-num-ref>
+ <boundary-data type="line-number">15  </boundary-data>
+and the cavity mold <part-num-ref name="cavity mold">3</part-num-ref>
+ for forming the test-tube shaped preform <part-num-ref name="test-tube shaped preform">10,</part-num-ref>
+ so that the resin is poured into the gap through a gate 3a of the cavity mold <part-num-ref name="cavity mold">3,</part-num-ref>
+ and fills the gap, thereby forming the preform <part-num-ref name="preform">10.</part-num-ref>
+   The core mold <part-num-ref name="core mold">5</part-num-ref>
+ is formed at an upper portion with a neck mold <part-num-ref name="neck mold">4,</part-num-ref>
+ which is divided into two <boundary-data type="line-number">20  </boundary-data>
+parts 4a and 4b, and forms an entrance of the bottle. The molded preform <part-num-ref name="molded preform">10</part-num-ref>
+ is separated<confidence value="4">.</confidence>
+ from the cavity mold <part-num-ref name="cavity mold">3</part-num-ref>
+ and the core mold <part-num-ref name="core mold">5.</part-num-ref>
+   The preform <part-num-ref name="preform">10</part-num-ref>
+ separated from the core mold <part-num-ref name="core mold">4</part-num-ref>
+ is shown in Fig. 3.    </p>
+    <p id="p-27" num="27">Fig. 4 is a perspective view illustrating an overall <boundary-data type="line-number">25  </boundary-data>
+construction of an arrangement for manufacturing a PET bottle having   a handle   formed  on  a body through    an injection blow molding method     in  accordance with   the present invention, and Fig. 5 is a top view illustrating the <confidence value="8">a</confidence>
+rrangement shown in Fig. 4<confidence value="5">.</confidence>
+    </p>
+    <p id="p-28" num="28">
+      <boundary-data type="line-number">3.0       </boundary-data>
+Referring to Figs. 4 and <part-num-ref name="and">5,</part-num-ref>
+ the arrangement <part-num-ref name="arrangement">100</part-num-ref>
+ for manufacturing the PET bottle through the injection blow molding method in accordance with the invention comprises a preform heating box <part-num-ref name="preform heating box">21</part-num-ref>
+ to receive and heat a plurality of preforms <part-num-ref name="plurality of preforms">10,</part-num-ref>
+ a robot arm <part-num-ref name="robot arm">23</part-num-ref>
+ to deliver the heated. preforms <part-num-ref name="heated. preforms">35</part-num-ref>
+  <part-num-ref name="">10</part-num-ref>
+ from the preform heating box <part-num-ref name="preform heating box">21,</part-num-ref>
+ a rotational circular <boundary-data type="header">
+        <confidence value="8">7</confidence>
+      </boundary-data>
+      <page-break num="8"/>
+      <boundary-data type="header">WO 2005/058580                              PCT<confidence value="5">/</confidence>
+KR200<confidence value="5">4</confidence>
+/0033<confidence value="68">41</confidence>
+      </boundary-data>
+plate <part-num-ref name="rotational circular plate">20</part-num-ref>
+ to receive the heated preforms <part-num-ref name="heated preforms">10</part-num-ref>
+ from the robot arm <part-num-ref name="robot arm">23</part-num-ref>
+ and to convey the preforms to respective stages of a process for manufacturing the PET bottle, a preform blow mold <part-num-ref name="preform blow mold">40,</part-num-ref>
+ a blow mold <part-num-ref name="blow mold">50</part-num-ref>
+ having a handle forming portion, a <boundary-data type="line-number">5  </boundary-data>
+cutting mold <part-num-ref name="cutting mold">60</part-num-ref>
+ having a mold punch as a cutting apparatus, and an insert injection mold <part-num-ref name="insert injection mold">70</part-num-ref>
+ as a bonding apparatus, in which the preform blow mold <part-num-ref name="preform blow mold">40,</part-num-ref>
+ the blow mold <part-num-ref name="blow mold">50,</part-num-ref>
+ the cutting mold <part-num-ref name="cutting mold">60,</part-num-ref>
+ and the insert injection mold <part-num-ref name="insert injection mold">70</part-num-ref>
+ are located below the rotational circular plate <part-num-ref name="rotational circular plate">20,</part-num-ref>
+ and spaced <boundary-data type="line-number">10  </boundary-data>
+a predetermined distance from each other on a supporting die <part-num-ref name="supporting die">25</part-num-ref>
+ such that a continuous process can be performed by rotation of the rotational circular plate <part-num-ref name="rotational circular plate">20.</part-num-ref>
+ Additionally, the arrangement is provided at the sides of the supporting die <part-num-ref name="supporting die">25</part-num-ref>
+ with a series of auxiliary apparatuses, such as an <boundary-data type="line-number">15  </boundary-data>
+injector <part-num-ref name="injector">72,</part-num-ref>
+ a conveyor <part-num-ref name="conveyor">80</part-num-ref>
+ to convey a completed PET container <part-num-ref name="completed PET container">19,</part-num-ref>
+ and the like.    In particular, the cutting mold <part-num-ref name="cutting mold">60</part-num-ref>
+ is formed at the side surface thereof with a hole <part-num-ref name="hole">62</part-num-ref>
+ into which the mold punch <part-num-ref name="mold punch">61</part-num-ref>
+ (see Figs. 14a to 14c) is inserted. The injector <part-num-ref name="injector">72</part-num-ref>
+ is located at the side of the <boundary-data type="line-number">20  </boundary-data>
+insert injection mold <part-num-ref name="insert injection mold">70.</part-num-ref>
+ Although the construction of the arrangement shown in Figs. 4 and <part-num-ref name="and">5</part-num-ref>
+ is based on a blow molding method adopting a two-stage type injection blow molding, it is needless to say that the present invention is applicable to one-stage type injection blow molding.    </p>
+    <p id="p-29" num="29">
+      <boundary-data type="line-number">25        </boundary-data>
+The process of manufacturing the PET bottle having the handle formed on the body by means of the injection blow molding apparatus in accordance with the invention shown in Figs. 4 and <part-num-ref name="and">
+        <confidence value="5">5</confidence>
+      </part-num-ref>
+ will be described for respective steps thereof as follows.    </p>
+    <p id="p-30" num="30">
+      <boundary-data type="line-number">30        </boundary-data>
+Figs. 6 to <part-num-ref name="to">10</part-num-ref>
+ are perspective views sequentially illustrating products obtained <confidence value="5">'</confidence>
+at the respective steps during the injection blow molding process for forming the PET bottle having   the handle formed on the body in accordance with Embodiment <part-num-ref name="body in accordance with Embodiment">1</part-num-ref>
+ of the present invention, in <part-num-ref name="present invention, in">35</part-num-ref>
+  each of which (a) is a perspective view of the products <boundary-data type="header">
+        <confidence value="4">8</confidence>
+      </boundary-data>
+      <page-break num="9"/>
+      <boundary-data type="header">
+        <confidence value="88">WO</confidence>
+ 2005/058580                               PCT<confidence value="5">/</confidence>
+KR2004/0033<confidence value="68">41</confidence>
+      </boundary-data>
+formed at the respective steps, and (b) is a perspective view of a lower portion of the products cut off from a middle portion thereof.    </p>
+    <p id="p-31" num="31">Figs. <confidence value="66">11</confidence>
+   to  <part-num-ref name="to">15</part-num-ref>
+ are  schematic perspective   views <boundary-data type="line-number">5  </boundary-data>
+illustrating apparatuses used    in  the  respective  steps during the injection blow molding process for forming the PET bottle having the handle     formed on the body     in accordance with Embodiment <part-num-ref name="body     in accordance with Embodiment">1</part-num-ref>
+ of the invention.    </p>
+    <p id="p-32" num="32">(1) The first step <boundary-data type="line-number">10        </boundary-data>
+Referring to Figs. 4 and <part-num-ref name="and">5,</part-num-ref>
+ after being received and heated within the preform heating box <part-num-ref name="preform heating box">21,</part-num-ref>
+ a plurality of preforms <part-num-ref name="plurality of preforms">10</part-num-ref>
+ are sequentially clamped, and delivered one by one by means of the robot arm <part-num-ref name="robot arm">23</part-num-ref>
+ to the rotational circular plate <part-num-ref name="rotational circular plate">20</part-num-ref>
+ such that the heated preforms are mounted to a <boundary-data type="line-number">15  </boundary-data>
+predetermined position under the bottom of the rotational circular plate <part-num-ref name="rotational circular plate">20.</part-num-ref>
+ Then, the rotational circular plate <part-num-ref name="rotational circular plate">20</part-num-ref>
+ rotates to a predetermined angle, and places an associated preform <part-num-ref name="associated preform">10</part-num-ref>
+ mounted under the rotational circular plate <part-num-ref name="rotational circular plate">20</part-num-ref>
+ to the preform blow mold <part-num-ref name="preform blow mold">40</part-num-ref>
+ in order to perform a first <boundary-data type="line-number">20  </boundary-data>
+blowing operation of the present invention. In the preform blow mold <part-num-ref name="preform blow mold">40</part-num-ref>
+ (see Fig. 11), compressed air is blown into the  preform  <part-num-ref name="preform">10,</part-num-ref>
+ while   a  stretching  rod  (not  shown) stretches the preform <part-num-ref name="preform">10</part-num-ref>
+ from a preform holder <part-num-ref name="preform holder">24</part-num-ref>
+ holding the preform <part-num-ref name="preform">10.</part-num-ref>
+ In the present embodiment, although the <boundary-data type="line-number">25  </boundary-data>
+injection stretch blow molding method is illustrated as being used for manufacturing the PET bottle, the present invention is not limited to this method, and it is apparent that the injection blow molding method may also be employed.    </p>
+    <p id="p-33" num="33">By such a first blowing operation, a first PET <boundary-data type="line-number">30  </boundary-data>
+container <part-num-ref name="first PET container">13</part-num-ref>
+ as shown in Fig. 7 is formed, in which the first PET container <part-num-ref name="first PET container">13</part-num-ref>
+ has an elliptical hollow portion 13a formed at the center thereof (see Fig. 7). This is for the purpose of providing an appropriate shape for forming a handle section on the PET bottle through a series <confidence value="68">of</confidence>
+ <part-num-ref name="series of">35</part-num-ref>
+  molding processes described hereinafter.      However, it <boundary-data type="header">
+        <confidence value="1">9</confidence>
+      </boundary-data>
+      <page-break num="10"/>
+      <boundary-data type="header">WO 2005/058580                              PCT<confidence value="5">/</confidence>
+KR200<confidence value="5">4</confidence>
+/0033<confidence value="68">41</confidence>
+      </boundary-data>
+should be understood that the present invention is not limited to the elliptical shape as mentioned above. Fig.    </p>
+    <p id="p-34" num="34">12 shows the first PET container <part-num-ref name="first PET container">13</part-num-ref>
+ produced after the first blowing operation.    </p>
+    <p id="p-35" num="35">
+      <boundary-data type="line-number">5        </boundary-data>
+In accordance with the present embodiment, since the PET bottle has therein the elliptical hollow portion, which has directionality in a circumferential direction, and the handle is also disposed at one portion of the PET bottle, it is desirable that, when mounting the preform <part-num-ref name="preform">10</part-num-ref>
+ on the <boundary-data type="line-number">10  </boundary-data>
+blow molds <part-num-ref name="blow molds">40,</part-num-ref>
+ <part-num-ref name="blow molds 40,">50,</part-num-ref>
+ <part-num-ref name="blow molds 40, 50,">60</part-num-ref>
+ and <part-num-ref name="and">70</part-num-ref>
+ of the present invention, the preform <part-num-ref name="preform">10</part-num-ref>
+ on the blow molds <part-num-ref name="blow molds">40,</part-num-ref>
+ <part-num-ref name="blow molds 40,">50,</part-num-ref>
+ <part-num-ref name="blow molds 40, 50,">60</part-num-ref>
+ and <part-num-ref name="and">70</part-num-ref>
+ are mounted in the same direction. This can be achieved by fixing the direction of the PET bottle mounted under the rotational circular plate <part-num-ref name="rotational circular plate">20.</part-num-ref>
+ As one example, a groove (not shown) <boundary-data type="line-number">15  </boundary-data>
+may be formed on a predetermined position of a neck of the preform <part-num-ref name="preform">10</part-num-ref>
+ so as to allow the groove formed on the neck of the preform <part-num-ref name="preform">10</part-num-ref>
+ to be caught by a predetermined portion under the bottom of the rotational circular plate <part-num-ref name="rotational circular plate">20</part-num-ref>
+ when the rotational circular plate <part-num-ref name="rotational circular plate">20</part-num-ref>
+ clamps the preform <part-num-ref name="preform">10,</part-num-ref>
+ <confidence value="66">so</confidence>
+ <boundary-data type="line-number">20  </boundary-data>
+that the PET bottle is prevented from rotating under the bottom  of  the  rotational  circular plate   <part-num-ref name="rotational  circular plate">20,</part-num-ref>
+ thereby allowing the preform <part-num-ref name="preform">10</part-num-ref>
+ of the PET bottle to be accurately located into the respective blow molds.    </p>
+    <p id="p-36" num="36">Meanwhile, when forming the preform <part-num-ref name="preform">10</part-num-ref>
+ having a <boundary-data type="line-number">25  </boundary-data>
+circular hollow portion as shown in Fig. 6 into the first PET container <part-num-ref name="first PET container">13</part-num-ref>
+ having the elliptical hollow portion as described above (see Fig. 7), the preform must be formed to have a uniform thickness. As one method of achieving this purpose, there is a method of creating a temperature <boundary-data type="line-number">30  </boundary-data>
+variation in the circumferential (rotational) direction of the preform by heating an outer peripheral portion of the preform corresponding to a minor axis of an ellipsoid of the first PET container <part-num-ref name="first PET container">13</part-num-ref>
+ after blow molding the preform higher than an outer peripheral portion of the preform <part-num-ref name="preform">35</part-num-ref>
+  corresponding to a major axis of the ellipsoid of the first <boundary-data type="header">
+        <confidence value="88">10</confidence>
+      </boundary-data>
+      <page-break num="11"/>
+      <boundary-data type="header">WO 2005/058580                               PCT<confidence value="5866885">/KR2004</confidence>
+/0033<confidence value="68">41</confidence>
+      </boundary-data>
+PET container <part-num-ref name="first PET container">13</part-num-ref>
+ after blow molding the preform, such that the outer peripheral portion of the preform corresponding to the minor axis of the ellipsoid is extended more than the outer peripheral portion of the preform corresponding <boundary-data type="line-number">5  </boundary-data>
+to the major axis of the ellipsoid, thereby allowing the hollow portion of the first PET container to have the elliptical shape having the uniform thickness.    </p>
+    <p id="p-37" num="37">
+      <confidence value="5">I</confidence>
+t is desirable that, when forming the first PET container <part-num-ref name="first PET container">13</part-num-ref>
+ in the first blowing operation, the first PET <boundary-data type="line-number">10  </boundary-data>
+container <part-num-ref name="first PET container">13</part-num-ref>
+ is formed to <part-num-ref name="is formed to">60</part-num-ref>
+ <confidence value="2">~</confidence>
+ <part-num-ref name="~">80</part-num-ref>
+ % of the volume of a completed PET bottle design. Additionally, for preventing the product from being    cooled upon   a second blowing operation, which follows the first blowing operation, the temperature of the first blow mold <part-num-ref name="first blow mold">40</part-num-ref>
+ must be appropriately <boundary-data type="line-number">15  </boundary-data>
+controlled.    </p>
+    <p id="p-38" num="38">(2) The second step Next, a second blowing operation is performed to form a second PET container <part-num-ref name="second PET container">15</part-num-ref>
+ as shown in Fig. 8 after mounting the first elliptical PET container <part-num-ref name="first elliptical PET container">13</part-num-ref>
+ formed by the first <boundary-data type="line-number">20  </boundary-data>
+blowing operation to the blow mold <part-num-ref name="blow mold">50</part-num-ref>
+ having the handle forming portion. During the second blowing operation, both  <confidence value="2">.</confidence>
+    </p>
+    <p id="p-39" num="39">sides of a predetermined portion of a body of the first elliptical PET container <part-num-ref name="first elliptical PET container">13</part-num-ref>
+ formed by the first blow molding are compressed by molding protrusions <part-num-ref name="first blow molding are compressed by molding protrusions">51,</part-num-ref>
+ formed on <boundary-data type="line-number">25  </boundary-data>
+inner surfaces of mold halves to act as the handle forming portion for forming the handle section on the first PET container <part-num-ref name="first PET container">13,</part-num-ref>
+ while the remainder of the body of the first PET container <part-num-ref name="first PET container">13</part-num-ref>
+ is secondarily stretched by blowing. Fig.    </p>
+    <p id="p-40" num="40">13 shows the second PET container <part-num-ref name="second PET container">15</part-num-ref>
+ ejected after the <boundary-data type="line-number">30  </boundary-data>
+second  blowing  operation.    With  this  second  blowing operation, the body of the second PET container <part-num-ref name="second PET container">15</part-num-ref>
+ is formed into the completed PET bottle design.    </p>
+    <p id="p-41" num="41">Meanwhile, the first elliptical PET container <part-num-ref name="first elliptical PET container">13</part-num-ref>
+ primarily stretched in the first blowing operation is thin, <part-num-ref name="first blowing operation is thin,">35</part-num-ref>
+  and vulnerable to variation in outer temperature.       In <boundary-data type="header">
+        <confidence value="88">11</confidence>
+      </boundary-data>
+      <page-break num="12"/>
+      <boundary-data type="header">WO 2005/058580                              PCT<confidence value="5">/</confidence>
+KR200<confidence value="5">4</confidence>
+/0033<confidence value="68">41</confidence>
+      </boundary-data>
+particular,  considering  that   the  handle  section   is compressed by the mold piece <part-num-ref name="mold piece">51,</part-num-ref>
+ and thus suffers from a cooling phenomenon causing the temperature to be rapidly decreased, the blow mold <part-num-ref name="blow mold">50</part-num-ref>
+ having the handle forming <boundary-data type="line-number">5  </boundary-data>
+portion must be appropriately controlled in temperature.    </p>
+    <p id="p-42" num="42">Additionally,  since  the  second  blowing   operation  is continuously performed after primarily stretching the first PET container, and the stretchability of the first PET container is different from that of the preform <part-num-ref name="preform">10,</part-num-ref>
+ the <boundary-data type="line-number">10  </boundary-data>
+temperature and the blowing pressure for the primarily stretched container must be changed.    </p>
+    <p id="p-43" num="43">Additionally, for ensuring that, after a compressed portion 15b of the handle section of the second PET container <part-num-ref name="second PET container">15</part-num-ref>
+ is cut off in a process described hereinafter, <boundary-data type="line-number">15  </boundary-data>
+ends 17c (see Fig. 9)' of a cut-off portion remaining in the handle section are bonded to an insert injection portion 19c  (see Fig. 10) formed through an insert injection process, which is a bonding process, each of <confidence value="2">-</confidence>
+the molding protrusions <part-num-ref name="bonding process, each of -the molding protrusions">51</part-num-ref>
+ (see Fig. 13) is preferably formed on the <boundary-data type="line-number">20  </boundary-data>
+surface thereof with irregularities, which cause the ends 17c (see Fig. 15) of the cut-off portion remaining in the handle section to be slightly widened from each other.    </p>
+    <p id="p-44" num="44">(3) The third step Next, when the second PET container <part-num-ref name="second PET container">15</part-num-ref>
+ is provided by <boundary-data type="line-number">25  </boundary-data>
+the second blowing operation, the second PET container <part-num-ref name="second PET container">15</part-num-ref>
+ is f<confidence value="8">o</confidence>
+rmed at one portion thereof with the handle section of a depressed and raised feature, which will be formed to the handle upon completion of manufacturing the PET bottle.    </p>
+    <p id="p-45" num="45">Tha<confidence value="82">t~</confidence>
+ is, since the compressed portion 15b (see Fig. 8) of <boundary-data type="line-number">30  </boundary-data>
+the handle section is not completely separated, it must be removed by cutting. For this purpose, after the second PET container <part-num-ref name="second PET container">15</part-num-ref>
+ is conveyed to the cutting mold <part-num-ref name="cutting mold">
+        <confidence value="66">60</confidence>
+      </part-num-ref>
+ as shown in Fig. 14, the third step of the present invention will be performed. For reference, in (a) to (c) of Fig. <confidence value="5">1</confidence>
+4, (a) is <part-num-ref name="present invention will be performed. For reference, in (a) to (c) of Fig. 14, (a) is">35</part-num-ref>
+  a perspective view illustrating an overall construction of <boundary-data type="header">
+        <confidence value="88">12</confidence>
+      </boundary-data>
+      <page-break num="13"/>
+      <boundary-data type="header">WO 2005/058580                              PCT<confidence value="5">/</confidence>
+KR200<confidence value="55">4/</confidence>
+0033<confidence value="68">41</confidence>
+      </boundary-data>
+the cutting mold <part-num-ref name="cutting mold">60,</part-num-ref>
+ (b) is a horizontal sectional view of the cutting mold <confidence value="4">'</confidence>
+60 shown in (a) of Fig. 14, and (c) is a longitudinal sectional view thereof.    </p>
+    <p id="p-46" num="46">With the second PET container <part-num-ref name="second PET container">15</part-num-ref>
+ as shown in Fig. 8 <boundary-data type="line-number">5  </boundary-data>
+equipped to the cutting mold <part-num-ref name="cutting mold">60,</part-num-ref>
+ as a hydraulic pressure cylinder <part-num-ref name="hydraulic pressure cylinder">63</part-num-ref>
+ equipped at the side surface of the cutting mold <part-num-ref name="cutting mold">60</part-num-ref>
+ applies force to the mold punch <part-num-ref name="mold punch">61</part-num-ref>
+ inserted into a through-hole formed at the side surface of the cutting mold <part-num-ref name="cutting mold">60,</part-num-ref>
+ the mold punch <part-num-ref name="mold punch">61</part-num-ref>
+ is pushed into the compressed portion <boundary-data type="line-number">10  </boundary-data>
+15b of the handle section, and cuts off the compressed portion 15b, thereby forming a third PET container <part-num-ref name="third PET container">1<confidence value="68">7.</confidence>
+      </part-num-ref>
+    </p>
+    <p id="p-47" num="47">Then, the compressed portion <confidence value="66">15</confidence>
+b of the handle section is ejected through the mold piece 60a at one side of the cutting mold <part-num-ref name="cutting mold">60</part-num-ref>
+ by the mold punch <part-num-ref name="mold punch">61,</part-num-ref>
+ and is then recycled.    </p>
+    <p id="p-48" num="48">
+      <boundary-data type="line-number">15  </boundary-data>
+In Fig. 9, reference numerals 17a and 17b denote containing spaces defined in the third PET container <part-num-ref name="third PET container">17,</part-num-ref>
+ respectively.    </p>
+    <p id="p-49" num="49">Meanwhile, in the case where the second PET container <part-num-ref name="second PET container">15</part-num-ref>
+ has a thick wall, it is effective to install a heater <confidence value="66">61</confidence>
+a separately to an <confidence value="5">.</confidence>
+end of the mold punch <part-num-ref name="mold punch">61.</part-num-ref>
+ At this <boundary-data type="line-number">20  </boundary-data>
+time, the temperature of the heater <confidence value="2668">.61a</confidence>
+ is preferably in the range of <part-num-ref name="range of">260</part-num-ref>
+ <confidence value="2">~</confidence>
+ <part-num-ref name="~">300</part-num-ref>
+ <confidence value="2">"</confidence>
+C, and must be appropriately controlled to prevent the formation of yarns or threads..    </p>
+    <p id="p-50" num="50">Moreover, in order to prevent crystallization around the cut portion, it is desirable that the cutting process is <boundary-data type="line-number">25  </boundary-data>
+performed as quickly as possible.      After the cutting process, the ends 17c of the cut-off portion remaining in the handle section after cutting off the compressed portion may be partially widened.    </p>
+    <p id="p-51" num="51">When the compressed portion of the handle section is <boundary-data type="line-number">30  </boundary-data>
+cut off by means of the mold punch <part-num-ref name="mold punch">61</part-num-ref>
+ while being heated by the heater 61a equipped to the end of the mold punch <part-num-ref name="mold punch">61,</part-num-ref>
+ the cut-off portion can be slightly melted by the heat of the heater 61a, and becomes blunt, thereby forming a non- crystallized portion  (see 17c of Fig. 15)<confidence value="8">.</confidence>
+      The non- <part-num-ref name="non-">35</part-num-ref>
+  crystallized portion serves to enhance bonding efficiency <boundary-data type="header">
+        <confidence value="88">13</confidence>
+      </boundary-data>
+      <page-break num="14"/>
+      <boundary-data type="header">WO 2005/0<confidence value="5">5</confidence>
+8580                              PCT<confidence value="5">/</confidence>
+KR2004/003341      </boundary-data>
+with another PET part, which will be introduced during an insert injection process described below.    </p>
+    <p id="p-52" num="52">(4) The fourth step Meanwhile, it would seem possible that the ends of <boundary-data type="line-number">5  </boundary-data>
+the cut-off portion remaining in the handle section can be bonded to each other by heating and compressing the cut-off portion remaining in the handle section after the cutting process using the mold punch <part-num-ref name="mold punch">61.</part-num-ref>
+ However, since the PET material stretched by the blowing process has a fixed <boundary-data type="line-number">10  </boundary-data>
+molecular orientation, it is difficult to bond the PET material by heating and compressing. Additionally, even if bonding is performed in such a way, the bonding strength is insufficient to permit the completed bottle to be filled with certain items, such as liquid. Accordingly, in order <boundary-data type="line-number">15  </boundary-data>
+to ensure satisfactory bonding effects, instead of bonding the ends of the cut-off portion remaining in the handle section by compressing both sides of the cut-off portion simultaneously with the cutting process in the third step, it is desirable to perform a bonding process for the cut- <boundary-data type="line-number">20  </boundary-data>
+off portion remaining in the handle section in the fourth step after the cutting process in the third step.    </p>
+    <p id="p-53" num="53">As for the bonding process for the <confidence value="5">.</confidence>
+cut-off portion remaining in the handle section after the cutting process, the fourth step is performed after the third PET container <boundary-data type="line-number">25  </boundary-data>
+      <part-num-ref name="third PET container">17</part-num-ref>
+ with the compressed portion 15b removed from the handle section, as shown in Fig. 9, is conveyed<confidence value="5">.</confidence>
+ to the insert injection mold <part-num-ref name="insert injection mold">70,</part-num-ref>
+ acting as the bonding apparatus, as shown in Fig. 15.    </p>
+    <p id="p-54" num="54">For reference, in Fig. 15,     (a) is a horizontal <boundary-data type="line-number">30  </boundary-data>
+sectional view illustrating the insert injection mold <part-num-ref name="insert injection mold">70,</part-num-ref>
+ (b) is a longitudinal sectional view thereof, and (c) is an enlarged view of part A, where insert injection molding is performed in a state that insert injection mold halves <part-num-ref name="state that insert injection mold halves">70</part-num-ref>
+ are engaged with each other.    </p>
+    <p id="p-55" num="55">35        As shown <confidence value="2">-</confidence>
+in the drawings, in the fourth step of the <boundary-data type="header">
+        <confidence value="86">14</confidence>
+      </boundary-data>
+      <page-break num="15"/>
+      <boundary-data type="header">WO 2005/058580                               PCT<confidence value="5">/</confidence>
+KR2004/0033<confidence value="68">41</confidence>
+      </boundary-data>
+present invention, with the injector <part-num-ref name="injector">72</part-num-ref>
+ located at the side of the insert injection mold <part-num-ref name="insert injection mold">70,</part-num-ref>
+ injection molding is performed by means of the injector <part-num-ref name="injector">72</part-num-ref>
+ along a cutting line on the ends 17c    <confidence value="5">(</confidence>
+see Fig. 9) of the cut-off portion <boundary-data type="line-number">
+        <confidence value="5">5</confidence>
+        </boundary-data>
+remaining in the handle section of the third PET container <part-num-ref name="third PET container">17.</part-num-ref>
+    </p>
+    <p id="p-56" num="56">When the third PET container <part-num-ref name="third PET container">17</part-num-ref>
+ is mounted in the insert injection mold <part-num-ref name="insert injection mold">70,</part-num-ref>
+ both sides of an intermediate portion <confidence value="5">1</confidence>
+7d of the cut-off portion remaining in the handle <boundary-data type="line-number">10  </boundary-data>
+section are compressed by a predetermined portion <part-num-ref name="predetermined portion">71</part-num-ref>
+ (see Fig. 15), acting as a compressing member, of the insert injection mold <part-num-ref name="insert injection mold">70,</part-num-ref>
+ thereby preventing a sealing material from being leaked through a gap between the intermediate portions 17d into the space 17b. upon insert injection <boundary-data type="line-number">15  </boundary-data>
+molding.  At the same time, the ends 17c of the handle section of the third PET container <part-num-ref name="third PET container">17</part-num-ref>
+ are sealed through insert injection molding. That is, spaces a and b shown <confidence value="88">in</confidence>
+ Fig. 15 are filled with the sealing material, thereby providing an inner circumference of a handle section 19d <boundary-data type="line-number">20  </boundary-data>
+with a smooth and volumetric shape, so that when a user grips the handle of the PET bottle, the inner circumference of the handle section 19d provides a convenient grip for the PET bottle. At this time, the dimensions of an insert injection molded part 19c are determined to maintain a <boundary-data type="line-number">25  </boundary-data>
+constant strength according to thickness and shape of the bottle  so   as  to  provide  an   assistant  function  in strengthening of the handle section.    </p>
+    <p id="p-57" num="57">The fourth PET container 19 molded by the insert inje<confidence value="8">c</confidence>
+tion mold <part-num-ref name="insert injection mold">70</part-num-ref>
+ has the insert injection molded part 19c <boundary-data type="line-number">30  </boundary-data>
+formed around the ends 17c of the cut-off portion remaining in the handle section of the third PET container <part-num-ref name="third PET container">17</part-num-ref>
+ after the cutting process, and is a completed PET bottle.    </p>
+    <p id="p-58" num="58">Meanwhile, as for another bonding process for the cut-off portion remaining in the handle section after the <part-num-ref name="">35</part-num-ref>
+  cutting process, the fourth step may be performed by means <boundary-data type="header">
+        <confidence value="88">15</confidence>
+      </boundary-data>
+      <page-break num="16"/>
+      <boundary-data type="header">WO 2005/058580                              PCT<confidence value="5">/</confidence>
+KR200<confidence value="5">4</confidence>
+/0033<confidence value="68">41</confidence>
+      </boundary-data>
+of ultrasonic bonding instead of insert injection molding.    </p>
+    <p id="p-59" num="59">Ultrasonic bonding is a method of welding overlapping portions of the plastic to each other after generating heat on  the  overlapping  portions  by  means  of   ultrasonic <boundary-data type="line-number">5  </boundary-data>
+vibration, and is applicable not only to bonding of a thin material but also to bonding a thick plastic material. In particular, in the case of the PET materials, it is impossible or difficult to apply heat plat bonding, impulse bonding or high frequency bonding to bonding of the PET <boundary-data type="line-number">10  </boundary-data>
+materials, whereas the ultrasonic bonding can be applied thereto by use of the high frequency oscillator, vibrator, tool horn, and the like.    </p>
+    <p id="p-60" num="60">As  with  the  bonding  process   using  the  insert injection mold as described above, with both sides of the <boundary-data type="line-number">15  </boundary-data>
+intermediate portion 17d (see Fig. 9) of the handle section of the third PET container <part-num-ref name="third PET container">17</part-num-ref>
+ compressed, high frequency vibration is generated on the overlapping portions, so that the overlapping portions are heated and welded to each other.    </p>
+    <p id="p-61" num="61">
+      <boundary-data type="line-number">
+        <confidence value="88">20</confidence>
+      </boundary-data>
+ Embodiment 2 According to Embodiment <part-num-ref name="According to Embodiment">1,</part-num-ref>
+ the. method of manufacturing the PET bottle comprises the steps <confidence value="2">,</confidence>
+of performing the first blowing operation to blow compressed air into the preform <boundary-data type="line-number">25 </boundary-data>
+      <part-num-ref name="preform">10</part-num-ref>
+ in the preform blow mold <part-num-ref name="preform blow mold">40</part-num-ref>
+ <confidence value="2">.</confidence>
+in order to form the first hollow PET container <part-num-ref name="first hollow PET container">13</part-num-ref>
+ (the <confidence value="5">.</confidence>
+first step); performing the second blowing operation to blow compressed air into the first PET container <part-num-ref name="first PET container">13</part-num-ref>
+ in order to form the second PET container <part-num-ref name="second PET container">15</part-num-ref>
+ in the blow mold <part-num-ref name="blow mold">50</part-num-ref>
+ having the molding <boundary-data type="line-number">30  </boundary-data>
+protrusions  <part-num-ref name="molding protrusions">51</part-num-ref>
+  (the   second  step);  cutting  off   the compressed portion 15b of the second PET container <part-num-ref name="second PET container">15</part-num-ref>
+ in order to form the third PET container <part-num-ref name="third PET container">17</part-num-ref>
+ (the third step)<confidence value="8">;</confidence>
+    </p>
+    <p id="p-62" num="62">and bonding the ends 17c remaining in the handle section of the third PET container <part-num-ref name="third PET container">17</part-num-ref>
+ in order to form the fourth PET <part-num-ref name="fourth PET">35</part-num-ref>
+  container  (when   bonding  is  performed   during  insert <boundary-data type="header">
+        <confidence value="66">16</confidence>
+      </boundary-data>
+      <page-break num="17"/>
+      <boundary-data type="header">WO 2005/0<confidence value="686">585</confidence>
+80                              PCT<confidence value="5">/</confidence>
+KR200<confidence value="5">4</confidence>
+/0033<confidence value="68">41</confidence>
+      </boundary-data>
+injection molding, the fourth PET container has the shape shown in Fig. 10, and when bonding is performed during ultrasonic bonding, the fourth PET container has a similar shape shown in Fig. 17<confidence value="5">)</confidence>
+ (the fourth step)<confidence value="5">.</confidence>
+    </p>
+    <p id="p-63" num="63">
+      <boundary-data type="line-number">5        </boundary-data>
+Figs. 16 and <part-num-ref name="and">17</part-num-ref>
+ are perspective views illustrating products obtained by the third step and the fourth step of a method in accordance with Embodiment <part-num-ref name="method in accordance with Embodiment">2</part-num-ref>
+ of the present invention, respectively.    </p>
+    <p id="p-64" num="64">Referring to Figs. 16 and <part-num-ref name="and">17,</part-num-ref>
+ the method according to <boundary-data type="line-number">10  </boundary-data>
+Embodiment <part-num-ref name="method according to Embodiment">2</part-num-ref>
+ comprises the same steps as those of the method according to Embodiment <part-num-ref name="method according to Embodiment">1,</part-num-ref>
+ except for the sequence of the third step and the fourth step (more specifically, the ultrasonic bonding process) of Embodiment <part-num-ref name="ultrasonic bonding process) of Embodiment">1.</part-num-ref>
+ That is, in the third step of the method according to Embodiment <part-num-ref name="method according to Embodiment">2,</part-num-ref>
+ <boundary-data type="line-number">15  </boundary-data>
+both sides of the compressed portion 15b in the handle section of the second PET container <part-num-ref name="second PET container">15</part-num-ref>
+ shown in Fig. 8 are bonded by the ultrasonic bonding process, thereby forming a third PET container <part-num-ref name="third PET container">16</part-num-ref>
+ shown in Fig. 16, and in the fourth step of Embodiment <part-num-ref name="fourth step of Embodiment">2,</part-num-ref>
+ the compressed and bonded portion 1<confidence value="68">6b</confidence>
+ <boundary-data type="line-number">20  </boundary-data>
+of the handle section of the third PET container <part-num-ref name="third PET container">16</part-num-ref>
+ is cut off, thereby forming a fourth PET container <part-num-ref name="fourth PET container">18</part-num-ref>
+ shown in Fig.    </p>
+    <p id="p-65" num="65">
+      <confidence value="888">17.</confidence>
+    </p>
+    <p id="p-66" num="66">According to Embodiment 2, the second and third steps of the method may be performed separately. Alternatively, <boundary-data type="line-number">25  </boundary-data>
+the second and third steps of the method may be performed concurrently, by means of the blow mold <part-num-ref name="blow mold">50</part-num-ref>
+ (see Fig. 13) having an ultrasonic vibrator (not shown) equipped at the distal end of one of the molding protrusions <part-num-ref name="molding protrusions">51</part-num-ref>
+ of the blow mold <part-num-ref name="blow mold">50</part-num-ref>
+ for forming the second PET container <part-num-ref name="second PET container">15.</part-num-ref>
+   In the <boundary-data type="line-number">30  </boundary-data>
+latter case, there are effects of reducing the time for manufacturing the products as well as manufacturing costs.    </p>
+    <p id="p-67" num="67">Embodiment 3 Fig. 18 is a perspective view illustrating. products <part-num-ref name="perspective view illustrating. products">35</part-num-ref>
+  obtained by the fifth step of a method in accordance with <boundary-data type="header">
+        <confidence value="88">17</confidence>
+      </boundary-data>
+      <page-break num="18"/>
+      <boundary-data type="header">WO 2005/058580                               PCT/KR2004/0033<confidence value="68">41</confidence>
+      </boundary-data>
+Embodiment <part-num-ref name="method in accordance with Embodiment">3</part-num-ref>
+ of the present invention.       Embodiment <part-num-ref name="present invention.       Embodiment">3</part-num-ref>
+ consists of five steps.    </p>
+    <p id="p-68" num="68">The first step of the method according to Embodiment <part-num-ref name="method according to Embodiment">3</part-num-ref>
+ is the same as that of the first step of the method <boundary-data type="line-number">5  </boundary-data>
+according to Embodiments <part-num-ref name="method according to Embodiments">1</part-num-ref>
+ and <part-num-ref name="and">2.</part-num-ref>
+      That is, the first blowing operation is performed after the preform is mounted to the preform blow mold <part-num-ref name="preform blow mold">40.</part-num-ref>
+    </p>
+    <p id="p-69" num="69">Unlike the second step of the method according to Embodiments <part-num-ref name="method according to Embodiments">1</part-num-ref>
+ and <part-num-ref name="and">2,</part-num-ref>
+ in the second step of the method <boundary-data type="line-number">10  </boundary-data>
+according to Embodiment <part-num-ref name="method according to Embodiment">3,</part-num-ref>
+ the first PET container <part-num-ref name="first PET container">13</part-num-ref>
+ is not completely expanded to the completed PET bottle design by the blowing operation. Instead, according t<confidence value="5">o</confidence>
+ Embodiment <part-num-ref name="blowing operation. Instead, according to Embodiment">3,</part-num-ref>
+ the method comprises an additional fifth step       for performing a blowing operation to stretch the PET container <boundary-data type="line-number">15  </boundary-data>
+to the completed PET bottle design.    </p>
+    <p id="p-70" num="70">That is, the second step of the method according to Embodiment <part-num-ref name="method according to Embodiment">3</part-num-ref>
+ is provided by modifying the second step of the method according to Embodiments <part-num-ref name="method according to Embodiments">1</part-num-ref>
+ and <part-num-ref name="and">2,</part-num-ref>
+ in which the second blowing operation is performed to form a second PET <boundary-data type="line-number">20 </boundary-data>
+container having a shape of <part-num-ref name="shape of">70</part-num-ref>
+ <confidence value="2">~</confidence>
+ <part-num-ref name="~">90</part-num-ref>
+ <confidence value="6">%</confidence>
+ of the volume of the completed PET bottle design by blowing compressed air into a first PET container <part-num-ref name="first PET container">13</part-num-ref>
+ to such an extent that a handle section of the first PET container <part-num-ref name="first PET container">13</part-num-ref>
+ is not deformed when compressing the handle section with the blow mold <part-num-ref name="blow mold">50</part-num-ref>
+ having <boundary-data type="line-number">25  </boundary-data>
+the molding protrusions <part-num-ref name="molding protrusions">51.</part-num-ref>
+    </p>
+    <p id="p-71" num="71">In the second    step  of the method according    to Embodiment <part-num-ref name="method according    to Embodiment">3,</part-num-ref>
+ although the second PET container (similar to the PET container shown in Fig. 8) is also formed with a compressed portion 15b of the handle section by compressing <boundary-data type="line-number">30 </boundary-data>
+the first PET container <part-num-ref name="first PET container">13</part-num-ref>
+ expanded to the shape of <part-num-ref name="shape of">60</part-num-ref>
+ <confidence value="2">~</confidence>
+ <part-num-ref name="~">80</part-num-ref>
+ <confidence value="5">%</confidence>
+ of the volume of the completed PET bottle design in the first step, the second PET container is maintained in a state of being blown to the shape of <part-num-ref name="shape of">70</part-num-ref>
+ <confidence value="2">~</confidence>
+ <part-num-ref name="~">90</part-num-ref>
+ % of the volume of the completed PET bottle design.    </p>
+    <p id="p-72" num="72">35        Although the third and fourth steps of the method <boundary-data type="header">
+        <confidence value="85">18</confidence>
+      </boundary-data>
+      <page-break num="19"/>
+      <boundary-data type="header">WO 2005/058580                                             PCT<confidence value="5">/</confidence>
+KR200<confidence value="5">4</confidence>
+/0033<confidence value="68">41</confidence>
+      </boundary-data>
+according    to   Embodiment     <part-num-ref name="method according    to   Embodiment">3</part-num-ref>
+  are   the   same   as  those   of   the method    according    to   Embodiments     <part-num-ref name="method    according    to   Embodiments">1</part-num-ref>
+ or   <part-num-ref name="or">2,</part-num-ref>
+   it  is  desirable that    the   operating     temperature      of   the    first    step   is maintained in the third and fourth steps due to the blowing <boundary-data type="line-number">5   </boundary-data>
+operation for forming the PET container into the completed PET   bottle    in  the   fifth   step   as   described    below.      More specifically, as with Embodiment <part-num-ref name="fifth   step   as   described    below.      More specifically, as with Embodiment">1,</part-num-ref>
+ the compressed portion 15b of the second PET container is cut off in the third step, and ends 17c of a cut-off portion remaining in the <boundary-data type="line-number">10   </boundary-data>
+handle    section    of  the   third   PET   container     are  bonded    by means of insert injection or the ultrasonic bonding in the fourth    step.    Alternatively,       as  with   Embodiment     <part-num-ref name="fourth    step.    Alternatively,       as  with   Embodiment">2,</part-num-ref>
+   both sides of the compressed portion 15b are bonded through the ultrasonic     bonding   in   the  third    step, and    the   compressed <boundary-data type="line-number">15   </boundary-data>
+portion 1<confidence value="5">6</confidence>
+b is cut off in the fourth step.    </p>
+    <p id="p-73" num="73">In the fifth step of the method according to Embodiment <part-num-ref name="method according to Embodiment">3,</part-num-ref>
+ an additional blowing operation is performed to form a fifth PET container <part-num-ref name="fifth PET container">14</part-num-ref>
+ as shown in Fig. 18 after mounting a fourth PET container (similar to the container as shown in Fig<confidence value="5">.</confidence>
+ 10 or in Fig. 17, but in a state of being blown to <boundary-data type="line-number">
+        <confidence value="8">2</confidence>
+0         </boundary-data>
+the shape of <part-num-ref name="shape of">70</part-num-ref>
+ <confidence value="2">~</confidence>
+ <part-num-ref name="~">90</part-num-ref>
+ <confidence value="5">%</confidence>
+ of the volume of the completed PET bottle design) to a blow mold (not shown) having a completed PET bottle shape and having a handle forming portion which will penetrate the body of the<confidence value="5">'</confidence>
+ PET container in the fifth step. In comparison with the blow mold <part-num-ref name="blow mold">50</part-num-ref>
+ having the molding protrusions <part-num-ref name="molding protrusions">51</part-num-ref>
+ shown in Fig. 13, the blow mold for the third blowing operation of <boundary-data type="line-number">
+        <confidence value="8">2</confidence>
+5         </boundary-data>
+Embodiment <part-num-ref name="third blowing operation of Embodiment">3</part-num-ref>
+ is different from the blow mold <part-num-ref name="blow mold">50</part-num-ref>
+ in that molding protrusions acting as the handle forming portion formed on blow mold halves contact each other through an opening 19d or 18d of the handle section as shown in Fig. 10 or in Fig. 17. If the blowing process is performed in the fifth step after finis<confidence value="8">h</confidence>
+ing the bonding process in the third and fourth steps, an effect of <boundary-data type="line-number">
+        <confidence value="86">30</confidence>
+         </boundary-data>
+providing bonded portion 19c or 18c in Fi<confidence value="5">g</confidence>
+. 10 or in Fig. 17 embedded into the container is provided. Fig. 18 show the fifth PET container provided by the fifth step after finishing the bonding process, for example, by means of insert injection molding, in which the fifth PET container <part-num-ref name="fifth PET container">
+        <confidence value="52">14</confidence>
+      </part-num-ref>
+ has the insert injection molded part 19c of Fig. 10 embedded in the container, and the handle <part-num-ref name="handle">
+        <confidence value="8">3</confidence>
+5      </part-num-ref>
+   section has the penetrated shape 1<confidence value="588">4d.</confidence>
+    </p>
+    <boundary-data type="header">
+      <confidence value="66">19</confidence>
+    </boundary-data>
+    <boundary-data type="header">WO 2005/058580                               PCT<confidence value="5">/</confidence>
+KR2004/003341    </boundary-data>
+    <p id="p-74" num="74">
+      <page-break num="20"/>
+Embodiment 4 Embodiment <part-num-ref name="Embodiment">4</part-num-ref>
+ is provided by combining the second step of Embodiment <part-num-ref name="second step of Embodiment">2</part-num-ref>
+ in which the second blowing operation is <confidence value="2">-</confidence>
+ <boundary-data type="line-number">5  </boundary-data>
+performed by use of the blow mold <part-num-ref name="blow mold">50</part-num-ref>
+ having the handle forming portion, and the third step of Embodiment <part-num-ref name="third step of Embodiment">2</part-num-ref>
+ in which the compressed portion 15b is bonded by ultrasonic bonding.  Specifically, Embodiment <part-num-ref name="compressed portion 15b is bonded by ultrasonic bonding.  Specifically, Embodiment">4</part-num-ref>
+ is characterized in that formation and bonding of a compressed portion 15b in a <boundary-data type="line-number">10  </boundary-data>
+handle section are performed at the same time by use of a handle forming device including a handle forming portion and an ultrasonic bonding apparatus installed on the distal end of the handle forming portion.    </p>
+    <p id="p-75" num="75">In a method of manufacturing a PET bottle having a <boundary-data type="line-number">15  </boundary-data>
+handle formed on a body according to Embodiment <part-num-ref name="body according to Embodiment">4,</part-num-ref>
+ the first step is the same as that of Embodiments <part-num-ref name="same as that of Embodiments">1</part-num-ref>
+ to <part-num-ref name="to">3.</part-num-ref>
+ That is, in the first step of the method, the first blowing operation is performed after mounting the preform <part-num-ref name="preform">10</part-num-ref>
+ on the preform blow mold <part-num-ref name="preform blow mold">40<confidence value="5">.</confidence>
+      </part-num-ref>
+    </p>
+    <p id="p-76" num="76">
+      <boundary-data type="line-number">20        </boundary-data>
+In the second step, the formation and<confidence value="5">.</confidence>
+ bonding of the compressed portion 15b of the handle section are performed concurrently in such a manner that with both sides of a first  PET container compressed, ultrasonic bonding     is performed on the compressed portion 15b at the same time by <boundary-data type="line-number">25  </boundary-data>
+use of the handle forming device including the handle forming  portion  and  the  ultrasonic  bonding  apparatus installed on the distal end of the handle forming portion.    </p>
+    <p id="p-77" num="77">A second PET container formed by the second step is similar to the container shown in Fig. 16.</p>
+    <p id="p-78" num="78">
+      <boundary-data type="line-number">30        </boundary-data>
+In the third step, a compressed and bonded portion 16b of the handle section is cut off.    </p>
+    <p id="p-79" num="79">In the fourth step, a second blowing operation is performed after mounting a third PET container (similar to the container shown in Fig. 17, but in a state of being <part-num-ref name="state of being">35</part-num-ref>
+  blow molded to the shape of <part-num-ref name="shape of">60</part-num-ref>
+ <confidence value="2">~</confidence>
+ <part-num-ref name="~">80</part-num-ref>
+ <confidence value="5">%</confidence>
+ of the volume of the <boundary-data type="header">
+        <confidence value="88">20</confidence>
+      </boundary-data>
+      <page-break num="21"/>
+      <boundary-data type="header">WO 2005/058580                               PCT<confidence value="2">/</confidence>
+KR200<confidence value="5">4</confidence>
+/0033<confidence value="68">41</confidence>
+      </boundary-data>
+completed PET bottle design) to a blow mold (not shown) having a completed PET bottle shape and having a handle forming portion which will penetrate the body of the PET container.   In the fourth step, a fourth PET container <boundary-data type="line-number">5  </boundary-data>
+having the shape of the completed PET bottle is formed (as with the PET container as shown in Fig. 18, the fourth PET container also has the embedded portion 14c, but        is different from the PET container shown in Fig. 18 in that the embedded portion 14c is bonded by ultrasonic bonding)<confidence value="5">.</confidence>
+    </p>
+    <p id="p-80" num="80">
+      <boundary-data type="line-number">
+        <confidence value="5">1</confidence>
+0              </boundary-data>
+Although the above embodiments <confidence value="5">.</confidence>
+are described with respect to the PET resin, it is apparent that the present invention is also applicable to manufacturing of various bottles using plastic materials other than PET resin.    </p>
+    <p id="p-81" num="81">(Industrial Applicability<confidence value="1">]</confidence>
+ <boundary-data type="line-number">15        </boundary-data>
+As is apparent from the above description, according to the present invention, the PET bottle having the handle formed on the body, which      cannot be manufactured by conventional extrusion blow molding methods, is formed by the continuous injection blow molding method, thereby <boundary-data type="line-number">20  </boundary-data>
+providing convenience in use, enhancing efficiency upon manufacturing the PET bottle having the handle formed on the body, eliminating labor and costs related to recycling of the handle made of a different plastic material from that of the body in the conventional PET container, and <boundary-data type="line-number">25  </boundary-data>
+preventing environmental pollution and economic loss due to waste of the handles of the conventional PET container.    </p>
+    <p id="p-82" num="82">Although the injection blow molding method is an appropriate method for forming the PET bottle having the handle formed on the body, due to its advantage in that a <boundary-data type="line-number">30  </boundary-data>
+container having a uniform     thickness can be produced thereby, it is applicable to the containers made of plastic materials other than the PET resin, and it is obv<confidence value="7">i</confidence>
+ous that the shape of the container is not limited to ellipsoid.    </p>
+    <boundary-data type="header">
+      <confidence value="88">21</confidence>
+    </boundary-data>
+    <boundary-data type="header">WO 2005/058580                              PCT<confidence value="5">/</confidence>
+KR200<confidence value="5">4</confidence>
+/0033<confidence value="68">41</confidence>
+    </boundary-data>
+    <p id="p-83" num="83">
+      <page-break num="22"/>
+Although the preferred embodiments of the present invention have been disclosed for illustrative purposes, those skilled in the art will appreciate that various modifications, additions and substitutions are possible, <boundary-data type="line-number">5  </boundary-data>
+without  departing  from  the  scope  and  spirit  of the invention as disclosed in the accompanying claims.    </p>
+    <boundary-data type="header">
+      <confidence value="88">22</confidence>
+    </boundary-data>
+  </description>
+</us-patent-application>
+

prior_art/10584865.xml

@@ -0,0 +1,178 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>10584865</doc-number>
+        <date>2009-06-18</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <boundary-data type="header">App<confidence value="7">l</confidence>
+e. No. 10/584,865    </boundary-data>
+    <boundary-data type="header">June 18, 2009</boundary-data>
+    <heading id="h-1">AMENDMENTS TO THE SPECIFICATION:</heading>
+    <p id="p-1" num="1">On page 1, line 11, please amend the heading as follows:</p>
+    <p id="p-2" num="2">Background <confidence value="525662">f-the-</confidence>
+ <confidence value="56662666">vent-ion</confidence>
+ On page 3, line 30, please amend the heading as follows:    </p>
+    <p id="p-3" num="3">Summary <confidence value="58">of</confidence>
+ <confidence value="888">the</confidence>
+ <confidence value="877778877">invention</confidence>
+ On page <part-num-ref name="invention On page">3,</part-num-ref>
+ amend the paragraph beginning on line <part-num-ref name="paragraph beginning on line">31</part-num-ref>
+ as follows:    </p>
+    <p id="p-4" num="4">
+      <confidence value="85866">TheAn</confidence>
+ object <confidence value="252">efh</confidence>
+                 is to provide a system and a method that overcomes the problems mentioned above, where the system and the method makes it possible to provide the users of a mobile telecommunication system with a different quality of service in different coverage areas of the system. A further object <confidence value="58">of</confidence>
+ <confidence value="888">the</confidence>
+ invent<confidence value="888">ion</confidence>
+ is to provide a system and a method that makes it possible to dynamically change the quality of service for a user, which enables an adaptation to occurrences in the area covered by the mobile telecommunication system.    </p>
+    <p id="p-5" num="5">On page 4, amend the paragraph beginning at line <part-num-ref name="paragraph beginning at line">1</part-num-ref>
+ as follows:    </p>
+    <p id="p-6" num="6">
+      <confidence value="666">The</confidence>
+ <confidence value="2222222">iention</confidence>
+    <confidence value="22222222">ordingly</confidence>
+ provides <confidence value="62">fo</confidence>
+    Users of a mobile telecommunication system <confidence value="66">to</confidence>
+ beare grouped into one or more priority-groups. The possible priority-group or groups to which a specific user belongs are defined in a user-register. In turn, the user-register is linked to the user and to a user-device. Such a user-register may have additional information about the user and the user-device in question.    </p>
+    <boundary-data type="header">
+      <confidence value="888">-3-</confidence>
+    </boundary-data>
+    <boundary-data type="header">App<confidence value="7">l</confidence>
+e. No. 10/584,865    </boundary-data>
+    <boundary-data type="header">June 18, 2009</boundary-data>
+    <p id="p-7" num="7">
+      <page-break num="2"/>
+On page 4, amend the paragraph beginning at line <part-num-ref name="paragraph beginning at line">7</part-num-ref>
+ as follows:    </p>
+    <p id="p-8" num="8">
+      <confidence value="666">The</confidence>
+ i<confidence value="87888888">nvention</confidence>
+ also provides <confidence value="625">for</confidence>
+ <confidence value="624">onO</confidence>
+ne or more priority-tables are provided, each associated with one or several areas covered by the mobile telecommunication system. A priority-table comprises one or several priority-levels, where each priority-level can be assigned one or several priority-groups. It is preferred that a priority-table can be changed to meet the present need to prioritise particular users within a particular area covered by a telecommunication system.    </p>
+    <p id="p-9" num="9">On page 4, amend the paragraph beginning at line <part-num-ref name="paragraph beginning at line">14</part-num-ref>
+ as follows:    </p>
+    <p id="p-10" num="10">Moreover, t<confidence value="66">he</confidence>
+ <confidence value="2222222">iventon</confidence>
+ provides    a priority-table <confidence value="586884">te-bei</confidence>
+s compared with a user-register<confidence value="66">[[</confidence>
+,]] when a user-device linked to said user-register enters an area associated with said priority-table.    </p>
+    <p id="p-11" num="11">The user-device can then be provided with a certain level of service within said area, depending on a possible correspondence between the priority-table and the user-register, preferably a correspondence between the priority-groups defined in the user-register and the priority-groups assigned to the priority-levels in the priority-table.</p>
+    <p id="p-12" num="12">On page 5, amend the paragraph beginning at line <part-num-ref name="paragraph beginning at line">7</part-num-ref>
+ as follows:    </p>
+    <p id="p-13" num="13">One advantage of the present <confidence value="22222222">inventio</confidence>
+ is the ability to provide a group of users in a mobile telecommunication system with a quality of service that may differ between different coverage areas of the system, as well as differ within a certain coverage area of the system. Another advantage is the ability to easily accomplish a more or less dynamic change of the quality of service for a certain group of users within a coverage area by simply changing the priority-table associated with the coverage area in question. The primarily centralised user-registers also <boundary-data type="header">
+        <confidence value="888">-4-</confidence>
+      </boundary-data>
+      <page-break num="3"/>
+      <boundary-data type="header">App<confidence value="7">l</confidence>
+e. No. 10/584,865      </boundary-data>
+      <boundary-data type="header">June 18, 2009</boundary-data>
+facilitate the addition of new of priority-groups or the deletion of old priority-groups for each user. Further advantages will appear from the following detailed description <confidence value="68">of</confidence>
+ <confidence value="688">the</confidence>
+ <confidence value="7887877776">invention.</confidence>
+    </p>
+    <p id="p-14" num="14">On page 5, delete the paragraph beginning at line <part-num-ref name="paragraph beginning at line">19.</part-num-ref>
+    </p>
+    <p id="p-15" num="15">On page 5, amend the paragraphs beginning at line <part-num-ref name="paragraphs beginning at line">25</part-num-ref>
+ as follows:    </p>
+    <p id="p-16" num="16">Fig. 2 is a flowchart schematically illustrating the creation of a user-register according to an example embodiment <confidence value="2526626666666266666628">ofthe-present-inventi.</confidence>
+    </p>
+    <p id="p-17" num="17">Fig. 3 is a flowchart schematically illustrating the modification of an existing user-register according to an example embodiment <confidence value="2526626666666266666628">ofthe-present-inventi.</confidence>
+    </p>
+    <p id="p-18" num="18">Fig. 4 is a flowchart schematically illustrating the creation of a priority-table according to an example embodiment <confidence value="68">of</confidence>
+ <confidence value="688">the</confidence>
+ present <confidence value="8778775">invent.</confidence>
+    </p>
+    <p id="p-19" num="19">Fig. 5 is a flowchart schematically illustrating the modification of an existing priority-table according to an example embodiment <confidence value="68">of</confidence>
+ <confidence value="688">the</confidence>
+ present <confidence value="88">in</confidence>
+vent<confidence value="88">io</confidence>
+n<confidence value="6">.</confidence>
+    </p>
+    <p id="p-20" num="20">On page 6, amend the paragraphs beginning at line <part-num-ref name="paragraphs beginning at line">1</part-num-ref>
+ as follows:    </p>
+    <p id="p-21" num="21">Fig. 6 is a schematic diagram illustrating a macro cell and a micro cell, and a user equipment of an UM<confidence value="5">T</confidence>
+S-system, where according to an example embodiment <confidence value="252662666666626666662">ofthe-present-inventi</confidence>
+  a user- register has been linked to the user equipment and a priority table has been associated to the macro cell.    </p>
+    <boundary-data type="header">
+      <confidence value="888">-5-</confidence>
+    </boundary-data>
+    <boundary-data type="header">App<confidence value="7">l</confidence>
+e. No. 10/584,865    </boundary-data>
+    <boundary-data type="header">June 18, 2009</boundary-data>
+    <p id="p-22" num="22">
+      <page-break num="4"/>
+Fig. 7 is a schematic diagram of a Universal Mobile Telecommunication System (UM<confidence value="588">TS)</confidence>
+ according to an example embodiment <confidence value="25">of</confidence>
+ On page <part-num-ref name="example embodiment of On page">6,</part-num-ref>
+ line <part-num-ref name="example embodiment of On page 6, line">9</part-num-ref>
+ amend the heading as follows:    </p>
+    <p id="p-23" num="23">Detailed                                               Description On page 6, amend the paragraph beginning at line <part-num-ref name="paragraph beginning at line">11</part-num-ref>
+ as follows:    </p>
+    <p id="p-24" num="24">As there is a need for an improved system and method for providing the users of a mobile telecommunication system with different quality of service in different coverage areas of the telecommunication system, embodiments of such a system and such a method will be described in more detail below. In particular, at least one example embodiment <confidence value="66">of</confidence>
+ <confidence value="668">the</confidence>
+ p<confidence value="88888">resen</confidence>
+t <confidence value="2222222">inveton</confidence>
+ may dynamically change the quality of service for one or several groups of users to adapt the behaviour of the system to occurrences in the specific coverage area of the cellular telecommunication system.    </p>
+    <p id="p-25" num="25">On page 6, amend the paragraph beginning at line <part-num-ref name="paragraph beginning at line">19</part-num-ref>
+ as follows:    </p>
+    <p id="p-26" num="26">The example embodiments <confidence value="25552255222562656266525">efthe-present-inventien</confidence>
+ technology described herein are described in the light of an UM<confidence value="5">T</confidence>
+S-system, though the <confidence value="22222222">imvetion</confidence>
+ technology described herein can be implemented in almost any mobile telecommunication system, e.g. in a GSM-system. In particular, the <confidence value="41">in</confidence>
+ <confidence value="2222222">eveniei</confidence>
+ technology described herein-is not limited to systems with a hierarchic structure. On the contrary, the <confidence value="222222222">ievention</confidence>
+ technology can be implemented in a vast variety of different mobile or wireless telecommunication systems having different structures, e.g.    </p>
+    <boundary-data type="header">
+      <confidence value="888">-6-</confidence>
+    </boundary-data>
+    <boundary-data type="header">App<confidence value="7">l</confidence>
+e. No. 10/584,865    </boundary-data>
+    <boundary-data type="header">June 18, 2009</boundary-data>
+    <p id="p-27" num="27">
+      <page-break num="5"/>
+depending on the underlying technique, the performance needed, the acceptable economic costs etc. Other mobile or wireless telecommunication systems wherein the invention can be implemented may e.g. be structured as a ring network, or a bus network or as a star network etc.    </p>
+    <p id="p-28" num="28">In addition to the U<confidence value="5">M</confidence>
+TS- and GSM-system already mentioned the Wireless Local Area Networks (WLAN) is another example of a mobile telecommunication system wherein the <confidence value="6612255224266626">present-nventien</confidence>
+ technology described herein can be implemented.    </p>
+    <p id="p-29" num="29">On page 6, amend the paragraph beginning at line <part-num-ref name="paragraph beginning at line">33</part-num-ref>
+ as follows:    </p>
+    <p id="p-30" num="30">According to a preferred example embodiment of the present invention each user of an UM<confidence value="588">TS-</confidence>
+ system can be provided with a user-register, the creation of which is schematically illustrated by the flowchart in Fig. 2.    </p>
+    <p id="p-31" num="31">On page 7, amend the paragraph beginning at line <part-num-ref name="paragraph beginning at line">1</part-num-ref>
+ as follows:    </p>
+    <p id="p-32" num="32">
+      <confidence value="488545">SidTlh</confidence>
+e user subscriptions [[is]] are preferably reflected in the Home Location Register (HLR) of the UM<confidence value="5">T</confidence>
+S-system, and the user-register is therefore preferably a part of the information in the user subscription stored in the HLR, though other organisations and/or locations of the user- registers are conceivable. A user-register may even be stored in one or more RNC(s) or even in a     </p>
+    <heading id="h-2">
+      <confidence value="868">UE.</confidence>
+    </heading>
+    <p id="p-33" num="33">On page 13, amend the paragraph beginning at line <part-num-ref name="paragraph beginning at line">31</part-num-ref>
+ as follows:    </p>
+    <p id="p-34" num="34">Non-limiting example <confidence value="42488547221">Embedinents</confidence>
+embodiments of the invention have now been described essentially in connection with an UMTS-system. However, embodiments <confidence value="22222">efthe</confidence>
+ <confidence value="22541142">mvei~Pen</confidence>
+ are certainly applicable in a GSM-system. In general it should be emphasised that the <boundary-data type="header">
+        <confidence value="888">-7-</confidence>
+      </boundary-data>
+      <page-break num="6"/>
+      <boundary-data type="header">App<confidence value="7">l</confidence>
+e. No. 10/584,865      </boundary-data>
+      <boundary-data type="header">June 18, 2009</boundary-data>
+      <confidence value="2222222">mvei~en</confidence>
+ technology described herein can be implemented in essentially all known mobile telecommunication systems, regardless if such systems are organised in a ring structure, in a bus structure or in a star structure or in some other suitable structure. In particular, compared to an <confidence value="885">UMT</confidence>
+S-system or a GSM-system, there may e.g. be another number of levels between an access point and a central switching centre or similar.    </p>
+    <boundary-data type="header">
+      <confidence value="888">-8-</confidence>
+    </boundary-data>
+  </description>
+</us-patent-application>
+

prior_art/10830509.xml

@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>10830509</doc-number>
+        <date>2010-02-16</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">7012P001                                                                  Patent </p>
+    <heading id="h-1">IN THE SPECIFICATION</heading>
+    <p id="p-2" num="2">Please amend paragraph [0028] as marked up below:</p>
+    <p id="p-3" num="3">-- A machine-readable medium includes any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer). For example, a machine-readable medium includes read only memory ("ROM"); random access memory ("RAM"); magnetic disk storage media; optical storage media; flash memory devices; <confidence value="2">e</confidence>
+ <confidence value="776676">career</confidence>
+ waves<confidence value="6">,</confidence>
+ <confidence value="2222222">infraed</confidence>
+ signals<confidence value="6">,</confidence>
+ digi<confidence value="8">t</confidence>
+al signals<confidence value="6">,</confidence>
+  <confidence value="6">;</confidence>
+ etc.-- <confidence value="8">1</confidence>
+0/830,509                         Page <part-num-ref name="machine-readable medium includes read only memory (&quot;ROM&quot;); random access memory (&quot;RAM&quot;); magnetic disk storage media; optical storage media; flash memory devices; e career waves, infraed signals, digital signals,  ; etc.-- 10/830,509                         Page">
+        <confidence value="8">2</confidence>
+      </part-num-ref>
+ <confidence value="88">of</confidence>
+ <part-num-ref name="of">
+        <confidence value="88">36</confidence>
+      </part-num-ref>
+     </p>
+  </description>
+</us-patent-application>
+

prior_art/10881900.xml

@@ -0,0 +1,422 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>10881900</doc-number>
+        <date>2004-06-30</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">EXPRESS MAIL NO. EV336670629US </p>
+    <heading id="h-1">EXPLAINING TASK SCHEDULING FOR A PROJECT</heading>
+    <heading id="h-2">TECHNICAL FIELD</heading>
+    <p id="p-2" num="2">
+      <confidence value="8666">[000</confidence>
+1]     The technology disclosed herein relates generally to scheduling projects and, more particularly, to explaining task scheduling for a project.    </p>
+    <heading id="h-3">BACKGROUND</heading>
+    <p id="p-3" num="3">
+      <confidence value="4666">[000</confidence>
+2]     Projects are endeavors involving multiple tasks that are together completed for a purpose, such as creating products or services. Projects include, e.g., erecting bridges or buildings, creating software, and shooting movies. Tasks involved in a project for erecting a building may include, e.g., acquiring materials, hiring a general contractor, and laying a foundation. Each project or some of its tasks may have various constraints such as time, cost, and scope. Time constraints include, e.g., a specified start or finish date. Cost constraints include availability of resources such as people and equipment that may perform the tasks. As an example, an electrician may only be available during a period of time. Scope constraints include, e.g., quality, features, and functions. As an example, an architect may specify a number of windows. A subset of the project's tasks may also have dependencies on other tasks. As an example, materials may need to be acquired before the foundation can be laid. These considerations, comprising at least constraints and dependencies, may be analyzed when determining a project schedule.    </p>
+    <p id="p-4" num="4">[0003]     A project manager determines and manages a project's schedule by analyzing and balancing the considerations. Analyzing considerations may involve, e.g., determining in what order tasks are to be performed, which resources will perform the tasks, and the duration of the tasks. Balancing considerations may involve, e.g., adjusting or reducing one or more of the <boundary-data type="header">[41826-8050-<confidence value="688488">/SL041</confidence>
+540.120<confidence value="5">]</confidence>
+                                 6/24/04      </boundary-data>
+      <page-break num="2"/>
+considerations to affect a third considerations. As an example, the project manager may add resources or remove features to reduce the total time for a task or project that is behind schedule. Alternatively, if project scope must be increased because of new requirements, resources may need to be increased so that a task or the project does not become delayed.    </p>
+    <p id="p-5" num="5">
+      <confidence value="5">[</confidence>
+0004<confidence value="5">]</confidence>
+     Project managers may use project management software such as MICROSOFT PROJECT to assist in managing their projects. A project manager may use project management software to track all information relating to a project such as tasks, duration of tasks, resources, and other considerations. When this project information is specified, the project management software may automatically provide project feedback, such as by adjusting completion time of a task based on adjustments to considerations, graphically displaying relationships between the project's tasks, and estimating completion dates and costs based on indicated progress. As an example, if a project comprises three tasks and the project ends at the completion of a task, the project may end sooner if the project manager assigns an additional resource to the task. Thus, the project manager is able to use the project management software to create, predict, analyze, and manage project schedules.    </p>
+    <p id="p-6" num="6">[0005<confidence value="5">]</confidence>
+     A project manager may provide as input to project management software a variety of information relevant to a project. This information may include work periods, tasks, resources, and progress. Work period information may include, e.g., work days and work hours. Task information may include, e.g., names, durations, relationships to other tasks, and resources assigned to the tasks.    </p>
+    <p id="p-7" num="7">Resource information may include, e.g., types, names, costs, and work hours.</p>
+    <p id="p-8" num="8">Progress information may include an initial project plan (sometimes referred to as a "baseline"), task completion, and actual values. Actual values describe previously completed portions of the project plan. Examples of actual values include, e.g., start date, finish date, duration, and cost. The project management software may use this information to determine an initial project schedule.</p>
+    <boundary-data type="header">[41826-8050-U<confidence value="85555888588">S0000/SLO41</confidence>
+540.120]  -2-                      6/24/04    </boundary-data>
+    <p id="p-9" num="9">
+      <page-break num="3"/>
+[0006]    When the project manager provides additional input or adjusts one of the previously provided inputs, a scheduler component of the project management software may reschedule one or more tasks automatically. As an example, when a project has many tasks with multiple dependencies or constraints, a change to the expected duration of a task may cause the scheduler component to reschedule, e.g., the start or finish dates of other tasks, and potentially the overall project schedule. In a complicated project, the project manager may not understand why the adjustment caused the scheduler component to reschedule other tasks, how the rescheduling was determined, or how to resolve issues resulting from the adjustment. When a project manager does not understand why the project management software reschedules tasks, the project manager may be less comfortable with schedules determined by the project management software, and may be less likely to continue to use the project management software. It would thus be highly desirable for a project scheduler component to be able to explain task scheduling for a project.    </p>
+    <heading id="h-4">SUMMARY</heading>
+    <p id="p-10" num="10">[0007]    Techniques for causing project management software to explain task scheduling for a project are provided. A technique for explaining task scheduling for a project analyzes a subset of tasks of the project, stores an indication of an explanation relating to a primary consideration for determining a schedule for tasks, and then determines a schedule for the tasks. A primary consideration for determining a schedule for a task is a consideration that is actually used to determine the schedule for the task from a subset of considerations that could be used. The stored indication of an explanation may be used to generate an explanation that is provided to a user using one or more of a variety of user interfaces.  By storing the indications during analysis and providing the indications using a user interface, the project management software may enable its user to better understand various aspects of a project's schedule.</p>
+    <boundary-data type="header">[41826-8050-US<confidence value="5555">0000</confidence>
+/SL<confidence value="488">O41</confidence>
+540.120]  -3-                    6/24/04    </boundary-data>
+    <heading id="h-5">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
+    <p id="p-11" num="11">
+      <page-break num="4"/>
+      <confidence value="8666">[000</confidence>
+8]     Figure 1 illustrates a user interface of project management software in an embodiment.    </p>
+    <p id="p-12" num="12">
+      <confidence value="8666">[000</confidence>
+9]     Figure 2 illustrates a user interface of project management software in an embodiment.    </p>
+    <p id="p-13" num="13">[0010]     Figure 3 illustrates a user interface of project management software in an embodiment in which explanation of schedule information is provided in a tool tip.</p>
+    <p id="p-14" num="14">[0011]     Figure 4 illustrates a user interface of project management software in an embodiment in which explanation of schedule information is provided in a smart tag.</p>
+    <p id="p-15" num="15">[0012]     Figure 5 illustrates a user interface of project management software in an embodiment in which explanation of schedule information is provided in a text box of a dialog relating to task information.</p>
+    <p id="p-16" num="16">[0013]     Figure 6 illustrates a user interface of project management software in an embodiment in which explanation of schedule information is provided in a tool tip.</p>
+    <p id="p-17" num="17">[0014]     Figure 7 illustrates a user interface of project management software in an embodiment in which explanation of schedule information is provided in a textual area of the user interface.</p>
+    <p id="p-18" num="18">[0015]     Figure 8 is a block diagram illustrating an embodiment of components of project management software.</p>
+    <p id="p-19" num="19">
+      <confidence value="866">[00</confidence>
+16]     Figure 9 is a flow diagram illustrating an embodiment of a scheduletasks routine performed by the scheduler component.    </p>
+    <p id="p-20" num="20">[0017]     Figure 10 is a block diagram illustrating an embodiment of a data structure relating to a project and its tasks.</p>
+    <p id="p-21" num="21">[0018]     Figure 11 is a block diagram illustrating an embodiment of a data structure relating to a task.</p>
+    <p id="p-22" num="22">[0019]     Figure 12 illustrates an example of a suitable computing system environment in which the facility may be implemented.</p>
+    <boundary-data type="header">[41826-8050-US<confidence value="5555">0000</confidence>
+/SL<confidence value="488">O41</confidence>
+540.120]  -4-                       6/24/04    </boundary-data>
+    <heading id="h-6">DETAILED DESCRIPTION</heading>
+    <p id="p-23" num="23">
+      <page-break num="5"/>
+Overview <confidence value="566865">[0020]</confidence>
+     Techniques for causing project management software to explain task scheduling for a project are provided. In an embodiment, a system for explaining task scheduling for a project analyzes a subset of tasks of the project, stores an indication of an explanation relating to a primary consideration for determining a schedule for tasks, and then determines a schedule for the tasks. A primary consideration for determining a schedule for a task is a consideration that is actually used to determine the schedule for the task from a subset of considerations that could be used. As an example, when a successor task can begin only after three other predecessor tasks end, the primary consideration may be a predecessor task with the last completion date because the successor task can only begin after the last predecessor task ends. The stored indication of an explanation may be used to generate an explanation that is provided to a user using one or more of a variety of user interfaces. As examples, the indication may be displayed using a tool tip, a smart tag, a change in color, text in a dialog box, or a variety of other means of providing feedback to users. By storing the indications during analysis and providing the indications using a user interface, the project management software may enable its user to better understand portions of a project's schedule.    </p>
+    <p id="p-24" num="24">Figures [0021]     Turning now to the figures, Figures 1-7 illustrate various aspects of a user interface of project management software incorporating the techniques described herein.</p>
+    <p id="p-25" num="25">[0022]     Figure 1 illustrates a user interface of project management software in an embodiment.  The project management software may use a windowing environment such as MICROSOFT WINDOWS. The main window of the project management software <part-num-ref name="project management software">100</part-num-ref>
+ comprises a textual area for textually displaying and receiving information, and a graphical area for graphically displaying and <boundary-data type="header">
+        <confidence value="588">[41</confidence>
+826-8050-US<confidence value="5555">0000</confidence>
+/SL<confidence value="488">O41</confidence>
+540.120]  -5-                       6/24/04      </boundary-data>
+      <page-break num="6"/>
+receiving information. As an example, the textual area may display information relating to tasks such as a number <part-num-ref name="number">101,</part-num-ref>
+ a name <part-num-ref name="name">102,</part-num-ref>
+ and a duration <part-num-ref name="duration">104.</part-num-ref>
+ As a further example, the graphical area may display information relating to tasks and their schedule as a Gantt chart <part-num-ref name="Gantt chart">105.</part-num-ref>
+ The textual area and the graphical area may together be referred to as a project plan window.    </p>
+    <p id="p-26" num="26">[0023]    A user may be able to input information directly into the textual area by selecting a row, e.g., row <part-num-ref name="row">103</part-num-ref>
+ corresponding to task number <part-num-ref name="corresponding to task number">3,</part-num-ref>
+ and typing information or performing other user interface operations in a manner generally similar to that which would be performed when using spreadsheet software. As examples, the user may be able to type a name or description for a task, a duration for the task, and indicate that the task is a subtask of a summary task <part-num-ref name="summary task">106.</part-num-ref>
+    </p>
+    <p id="p-27" num="27">
+      <confidence value="5">[</confidence>
+0024<confidence value="5">]</confidence>
+    Each task may have one or more resources assigned to the task. These resources may be displayed in the Gantt chart adjacent to the bar for the task, such as resource <part-num-ref name="task, such as resource">107.</part-num-ref>
+ In the illustrated example, a "G.C. general management" resource is assigned to task number <part-num-ref name="&quot;G.C. general management&quot; resource is assigned to task number">3.</part-num-ref>
+    </p>
+    <p id="p-28" num="28">[0025]    Tasks may be linked with one another to indicate time-related dependencies. As an example, a successor task may only be capable of beginning after a predecessor task is completed. This relationship between predecessor and successor tasks may be referred to as a dependency. A dependency that causes a successor task to begin after a predecessor task ends may be referred to as a finish-to-start dependency. When tasks have a time- related dependency (e.g., a finish-to-start or other dependency), the project management software may indicate the dependency on the Gantt chart using an arrow, such as arrow <part-num-ref name="arrow, such as arrow">109.</part-num-ref>
+ Other time-related dependencies include, e.g., start-to- start, finish-to-finish, and start-to-finish (not shown). A start-to-start dependency may be used when two tasks should start at the same time; a finish-to-finish dependency may be used when two tasks should finish at the same time; and a start-to-finish dependency may be used when the start date of a predecessor task determines the finish date of a successor task.    </p>
+    <boundary-data type="header">[41826-8050-U<confidence value="5">S</confidence>
+0000/SL<confidence value="585">O41</confidence>
+540.120]  -6-                    6/24/04    </boundary-data>
+    <p id="p-29" num="29">
+      <page-break num="7"/>
+      <confidence value="5">[</confidence>
+0026<confidence value="5">]</confidence>
+     The user may be able to set or modify schedule information relating to a task (e.g., a constraint or dependency) using bars of the Gantt chart. As an example, the user may drag a left or right boundary of the bar <part-num-ref name="bar">108</part-num-ref>
+ to change the associated task's start date or end date. As a further example, the user may be able to drag and drop the bar to indicate that the task is a sub-task of a summary task (e.g., by moving the bar's position vertically) or change the task's schedule (e.g., by moving the bar's position horizontally).    </p>
+    <p id="p-30" num="30">[0027]     Figure 2 illustrates a user interface of project management software in an embodiment. Once schedule-related information is entered into the project management software (or retrieved from storage), various aspects of the user interface of the project management software <part-num-ref name="project management software">200</part-num-ref>
+ may be used to modify the previously entered information. As an example, the duration of a task may be modified by either typing in a new duration, or by selecting the duration and manipulating user interface controls that appear in relation to the selected task.    </p>
+    <p id="p-31" num="31">In the illustrated example, a duration <part-num-ref name="duration">202</part-num-ref>
+ of task <part-num-ref name="of task">3</part-num-ref>
+ is modified to indicate that the task's duration is <part-num-ref name="task's duration is">10</part-num-ref>
+ days, and not <part-num-ref name="days, and not">3</part-num-ref>
+ days as previously entered and shown in Figure 1.    </p>
+    <p id="p-32" num="32">[0028]     Figure 3 illustrates a user interface of project management software in an embodiment in which explanation of schedule information is provided in a tool tip.</p>
+    <p id="p-33" num="33">When a user momentarily positions a mouse pointer over a bar, the project management software may display a "tool tip." A tool tip is typically an informational message that appears near a user interface element or object over which a user momentarily positions a mouse pointer. The tool tip of a Gantt chart bar may indicate a name or description of the task, the task's start and finish dates, the task's duration, and a message indicating why the task was scheduled (or rescheduled).</p>
+    <p id="p-34" num="34">
+      <confidence value="5">[</confidence>
+0029]    In the illustrated user interface <part-num-ref name="illustrated user interface">300,</part-num-ref>
+ a user has momentarily positioned a mouse pointer <part-num-ref name="mouse pointer">302</part-num-ref>
+ over a bar of a Gantt chart relating to task number four of the illustrated project. As a result, a tool tip <part-num-ref name="tool tip">304</part-num-ref>
+ appears describing task number <part-num-ref name="appears describing task number">4.</part-num-ref>
+    </p>
+    <p id="p-35" num="35">The tool tip indicates that the task's name is "Submit bond and insurance"; the <boundary-data type="header">
+        <confidence value="588">[41</confidence>
+826-8050-US<confidence value="5555">0000</confidence>
+/SL<confidence value="585">O41</confidence>
+540.120]  -7-                       6/24/04      </boundary-data>
+      <page-break num="8"/>
+task begins on Thursday, January <part-num-ref name="task begins on Thursday, January">15,</part-num-ref>
+ <part-num-ref name="task begins on Thursday, January 15,">2004,</part-num-ref>
+ lasts two days and ends on Friday, January 16; and the task was scheduled forward from the finish date of task number <part-num-ref name="finish date of task number">3,</part-num-ref>
+ which finishes on Wednesday, January <part-num-ref name="finish date of task number 3, which finishes on Wednesday, January">14.</part-num-ref>
+ Task number <part-num-ref name="finish date of task number 3, which finishes on Wednesday, January 14. Task number">4</part-num-ref>
+ may have been scheduled forward from the finish date of task number <part-num-ref name="finish date of task number">3</part-num-ref>
+ because task number <part-num-ref name="because task number">4</part-num-ref>
+ is a successor task of task number <part-num-ref name="successor task of task number">3</part-num-ref>
+ and has a finish-to-start constraint on task number <part-num-ref name="finish-to-start constraint on task number">3.</part-num-ref>
+    </p>
+    <p id="p-36" num="36">[0030]    The project management software may provide a variety of informational messages. As examples, informational messages may indicate schedule adjustments based on time or resource constraints, or indeed any schedule consideration. Thus, the project management software may provide information to the user indicating an explanation of the schedule adjustment in a tool tip.</p>
+    <p id="p-37" num="37">[0031]    Figure 4 illustrates a user interface of project management software in an embodiment in which explanation of schedule information is provided in a smart tag. In the illustrated user interface <part-num-ref name="illustrated user interface">400,</part-num-ref>
+ a user has selected a smart tag indicator <part-num-ref name="smart tag indicator">402</part-num-ref>
+ relating to task number <part-num-ref name="relating to task number">4</part-num-ref>
+ of the illustrated project. When a user selects a smart tag indicator, the project management software may display a smart tag as an informational window associated with the indicator. A smart tag may include text and associated intelligence or logic. As an example, text included with smart tag <part-num-ref name="example, text included with smart tag">404</part-num-ref>
+ indicates that the task was scheduled forward from the finish date of task number <part-num-ref name="finish date of task number">3.</part-num-ref>
+ Associated logic (not shown) may include, e.g., fixing the start date of task number <part-num-ref name="start date of task number">4</part-num-ref>
+ and rescheduling its predecessor tasks (e.g., task number <part-num-ref name="task number">3)</part-num-ref>
+ such that they end at the fixed start date of task number <part-num-ref name="fixed start date of task number">4.</part-num-ref>
+ Other actions may also be possible. As an example, the smart tag may indicate that another resource is available to help complete task number <part-num-ref name="smart tag may indicate that another resource is available to help complete task number">3</part-num-ref>
+ (or number <part-num-ref name="(or number">4)</part-num-ref>
+ such that the finish dates of task numbers <part-num-ref name="finish dates of task numbers">3</part-num-ref>
+ or <part-num-ref name="or">4</part-num-ref>
+ can be readjusted. Thus, the project management software may provide information to the user indicating an explanation of the schedule adjustment for the task in a smart tag, and enable the user to perform other actions associated with the schedule adjustment.    </p>
+    <p id="p-38" num="38">[0032]    Figure 5 illustrates a user interface of project management software in an embodiment in which explanation of schedule information is provided in a text box <boundary-data type="header">[41826-8050-US<confidence value="5555">0000</confidence>
+/SL<confidence value="488">O41</confidence>
+540.120]  -8-                    6/24/04      </boundary-data>
+      <page-break num="9"/>
+of a dialog relating to task information. In the illustrated user interface, a dialog box <part-num-ref name="dialog box">500</part-num-ref>
+ provides information relating to a task to a user and receives information relating to the task from the user. A user may request the dialog box by using any of a variety of gestures using the user interfaces of Figures 1-4. As examples, the user may "double-click" on a task using a mouse or select a menu option after selecting a task. In the dialog box that appears, a text box <part-num-ref name="text box">502</part-num-ref>
+ may provide an explanation of schedule information that the project management software has determined for an indicated task (i.e., a task for which the dialog box was requested). As an example, the text box may provide an explanation that the indicated task was rescheduled because of an adjustment of a task on which the indicated task has a dependency. The information provided in the text box may be similar or equivalent to information provided in tool tip <part-num-ref name="text box may be similar or equivalent to information provided in tool tip">304</part-num-ref>
+ or smart tag <part-num-ref name="or smart tag">404.</part-num-ref>
+    </p>
+    <p id="p-39" num="39">Alternatively, the information provided in the text box may be more or less detailed than the information provided in the tool tip or the smart tag. Thus, the project management software may provide information to the user indicating an explanation of the schedule adjustment for the task in a text box of a dialog box.</p>
+    <p id="p-40" num="40">
+      <confidence value="5">[</confidence>
+0033<confidence value="5">]</confidence>
+     Figure 6 illustrates a user interface for project management software in an embodiment in which explanation of schedule information is provided in a tool tip.    </p>
+    <p id="p-41" num="41">In a manner similar to that described in relation to Figure 3, a user may momentarily position a mouse pointer over, e.g., an icon relating to a task. As an example, in the illustrated user interface <part-num-ref name="illustrated user interface">600,</part-num-ref>
+ a user has momentarily positioned a mouse pointer (not shown) over a notes icon <part-num-ref name="notes icon">602</part-num-ref>
+ relating to task number <part-num-ref name="relating to task number">9</part-num-ref>
+ of the illustrated project. When the user does so, a tool tip <part-num-ref name="tool tip">604</part-num-ref>
+ may appear containing an explanation of schedule information for the task. Other informational icons may also be used instead of or in addition to the notes icon. As an example, an informational icon may appear indicating that an explanation is available.    </p>
+    <p id="p-42" num="42">
+      <confidence value="666">[00</confidence>
+34]     Figure 7 illustrates a user interface of project management software in an embodiment in which explanation of schedule information is provided in a textual area of the user interface. The illustrated user interface <part-num-ref name="illustrated user interface">700</part-num-ref>
+ may comprise a <boundary-data type="header">[41826-8050-US<confidence value="5555">0000</confidence>
+/SL<confidence value="488">O41</confidence>
+540.120<confidence value="5">]</confidence>
+  -9<confidence value="5">-</confidence>
+                      6/24/04      </boundary-data>
+      <page-break num="10"/>
+column <part-num-ref name="column">702</part-num-ref>
+ that may contain an indication of an explanation of schedule information for each task.    </p>
+    <p id="p-43" num="43">[0035]    In an embodiment, a change in color, shape, or other format may indicate a primary consideration relating to a task's schedule. As examples, an arrow indicating a dependency between two tasks may appear in a different color or in a different format (e.g., bold) to indicate a primary consideration. Similarly, a bar of a Gantt chart may appear in a different color or shape to indicate that it is a primary consideration.</p>
+    <p id="p-44" num="44">[0036]    Figure 8 is a block diagram illustrating an embodiment of components of project management software. The illustrated project management software <part-num-ref name="illustrated project management software">800</part-num-ref>
+ comprises an input component <part-num-ref name="input component">802,</part-num-ref>
+ an output component <part-num-ref name="output component">804,</part-num-ref>
+ and a scheduler component <part-num-ref name="scheduler component">806.</part-num-ref>
+    </p>
+    <p id="p-45" num="45">[0037]    The input component may receive data from a user or other software. The user may provide data using any of a number of user interface elements of the project management software. As an example, the user may type information using a keyboard. Alternatively, the user may retrieve information from storage, such as by retrieving a previously stored schedule. Other software may provide data using an application program interface ("AP<confidence value="5">I</confidence>
+") of the project management software. The input component may store the received data in a schedule file, such as in primary storage (e.g., random access memory) or in secondary storage (e.g., hard disk).    </p>
+    <p id="p-46" num="46">[0038]    The output component may provide output of schedule information in a variety of means. As examples, the output component may provide schedule information in a Gantt chart, report, or table, or by using an API of other software to communicate the schedule information to the other software.</p>
+    <p id="p-47" num="47">[0039]    The scheduler component may determine a schedule for each task based on data received by the input component. The scheduler component may also determine a schedule for tasks based on schedule considerations, such as constraints or dependencies relating to other tasks.  Other scheduling considerations may include, e.g., task constraints, actual values that have been <boundary-data type="header">[41826-8050-US<confidence value="5555">0000</confidence>
+/SL<confidence value="488">O41</confidence>
+540.120<confidence value="5">]</confidence>
+  -10-                   6/24/04      </boundary-data>
+      <page-break num="11"/>
+reported on a task, start or finish dates of the project or its tasks, status dates for the project or its tasks, dependencies on other projects, or dependencies on milestones or phases within the project or other projects.    </p>
+    <p id="p-48" num="48">
+      <confidence value="66686">[0040</confidence>
+]     The scheduler component may also determine a schedule for tasks based on operations performed by a user, such as when leveling resources. The user may level resources to, e.g., ensure that a resource is not assigned to more tasks than the resource is capable of completing.    </p>
+    <p id="p-49" num="49">[0041<confidence value="5">]</confidence>
+     While the scheduler component determines a schedule for each task, it may store an indication of an explanation for the task's schedule. As an example, the scheduler component may store an indication of an explanation relating to a primary consideration for determining a schedule for the task. A primary consideration for determining a schedule for a task is a consideration that is actually used to determine the schedule for the task from a subset of considerations that could be used. As an example, when a successor task can begin only after three other predecessor tasks end, the primary consideration may be the predecessor task with the last completion date.    </p>
+    <p id="p-50" num="50">
+      <confidence value="866885">[0042]</confidence>
+     Primary considerations may include tasks that are on a critical path. A critical path is a subset of tasks that, if delayed, could delay the project with which the tasks are associated.    </p>
+    <p id="p-51" num="51">
+      <confidence value="866">[00</confidence>
+43]     The stored indication of an explanation may be used by the output component to generate an explanation that is later provided to a user. As an example, the indications may be stored in a form that a human may not easily comprehend, and the output component may convert the indications into human- readable text for display to the user.    </p>
+    <p id="p-52" num="52">
+      <confidence value="866">[00</confidence>
+44]     Thus, the project management software may store annotations or other indications explaining task scheduling as each task is scheduled.    </p>
+    <p id="p-53" num="53">
+      <confidence value="866">[00</confidence>
+45]     Figure 9 is a flow diagram illustrating an embodiment of a scheduletasks routine performed by the scheduler component. The routine begins at block <part-num-ref name="routine begins at block">902.</part-num-ref>
+    </p>
+    <p id="p-54" num="54">At block 904, the routine may order tasks for scheduling. Ordering the tasks for scheduling may involve placing predecessor tasks earlier in the orderthan <boundary-data type="header">[41826-8050-U<confidence value="85555">S0000</confidence>
+/SL<confidence value="488">O41</confidence>
+540.120]  -11-                      6/24/04      </boundary-data>
+      <page-break num="12"/>
+successor tasks, which may cause scheduling to be performed for predecessor tasks before successor tasks.    </p>
+    <p id="p-55" num="55">
+      <confidence value="866">[00</confidence>
+46]     At block 906, the routine selects the first of the ordered tasks.    </p>
+    <p id="p-56" num="56">
+      <confidence value="866">[00</confidence>
+47]    In block<confidence value="8">s</confidence>
+ 908-914, the routine may determine a primary consideration for a subset of tasks, provide an explanation relating to the scheduling for the tasks, and determine a schedule for the tasks. The scheduling for the tasks may include an indication of a primary consideration.    </p>
+    <p id="p-57" num="57">[004<confidence value="5">8</confidence>
+]     At block 908, the routine may analyze the selected task. Analyzing the selected task may include, e.g., determining which of a set (or subset) of considerations for the selected task is a primary consideration. As an example, a predecessor task that ends last may be a primary consideration for a successor task that has a finish-to-start dependency on the primary consideration.    </p>
+    <p id="p-58" num="58">[0049]     At block 910, the routine may store an indication of an explanation for the task's schedule. The routine may store this indication as an annotation relating to the selected task. As an example, the routine may store the indication in a data structure comprising data relating to the task (described in further detail below in relation to Figure 10). By storing the indication at the time of determining a schedule for the task, an accurate explanation for the task's schedule can be preserved.</p>
+    <p id="p-59" num="59">
+      <confidence value="66666">[0050</confidence>
+]     At block 912, the routine may determine a schedule for the selected task.    </p>
+    <p id="p-60" num="60">The routine may call a subroutine of the scheduler component or an altogether different component to determine the schedule for the task (not shown). Thus, the applicants' technique is compatible with a variety of project management software, including MICROSOFT PROJECT.</p>
+    <p id="p-61" num="61">[0051]     At block 914, the routine may update schedule information for the selected task. At block <part-num-ref name="selected task. At block">912,</part-num-ref>
+ the routine may store the schedule determined in a data structure associated with the task.    </p>
+    <p id="p-62" num="62">[0052]     At block 916, the routine may determine whether there are additional tasks to analyze. If there are additional tasks, the routine continues at block <part-num-ref name="routine continues at block">918.</part-num-ref>
+    </p>
+    <boundary-data type="header">[41826-8050-US<confidence value="5555">0000</confidence>
+/SL<confidence value="488">O41</confidence>
+540.120]  -12-                      6/24/04    </boundary-data>
+    <p id="p-63" num="63">
+      <page-break num="13"/>
+Otherwise, the routine continues at block <part-num-ref name="routine continues at block">920.</part-num-ref>
+ At block <part-num-ref name="routine continues at block 920. At block">918,</part-num-ref>
+ the routine selects the next task and then continues at block <part-num-ref name="next task and then continues at block">908.</part-num-ref>
+    </p>
+    <p id="p-64" num="64">[0053]    At block 920, the routine returns to its caller.</p>
+    <p id="p-65" num="65">[0054]     By performing these steps, the scheduler component may have determined a schedule for each task of a project and may also have indicated an explanation for determining the schedule.</p>
+    <p id="p-66" num="66">
+      <confidence value="86666">[0055</confidence>
+]     Figures 10-11 illustrate data structures associated with projects and tasks.    </p>
+    <p id="p-67" num="67">The data structures may store data provided by a user using a user interface of the project management software, or other software using an API exposed by the project management software, and may also store data or other information produced or determined by the project management software. The data structures may be stored in primary or secondary storage.</p>
+    <p id="p-68" num="68">
+      <confidence value="86666">[0056</confidence>
+]     Figure 10 is a block diagram illustrating an embodiment of a data structure relating to a project and its tasks. Each project may have project-related data stored in a data structure associated with the project <part-num-ref name="project">1002.</part-num-ref>
+ As examples, project- related data may include a project name, a project start date, and project holidays.    </p>
+    <p id="p-69" num="69">Project-related data may also include an indication of a number of tasks and their associated task-related data structures <part-num-ref name="number of tasks and their associated task-related data structures">1004.</part-num-ref>
+ Each task-related data structure comprises input data or other information relating to a task (further described below in relation to Figure 11).    </p>
+    <p id="p-70" num="70">[0057]     Figure 11 is a block diagram illustrating an embodiment of a data structure relating to a task. The task data structure <part-num-ref name="task data structure">1102</part-num-ref>
+ may comprise input data and other information associated with a task. As examples, task-related data may include, e.g., a task number, description, start date, duration, resources assigned to the task, dependencies or constraints, and an annotation or explanation relating to the task's schedule. The task-related data may also comprise additional information (not shown). There may be a one-to-one correspondence between the number of task data structures to and the number of tasks associated with the project. In the illustrated embodiment, the task data structure <part-num-ref name="task data structure">1102</part-num-ref>
+ is shown containing data corresponding to task number <part-num-ref name="is shown containing data corresponding to task number">4</part-num-ref>
+ as indicated in Figure 4.    </p>
+    <boundary-data type="header">[41826-8050-US<confidence value="5555">0000</confidence>
+/SL<confidence value="488">O41</confidence>
+540.120]  -13-                     6/24/04    </boundary-data>
+    <p id="p-71" num="71">
+      <page-break num="14"/>
+There may be additional task data structures for each of the other tasks in the project indicated in Figure 4 (not shown).    </p>
+    <p id="p-72" num="72">[0058]     Figure 12 illustrates an example of a suitable computing system environment <part-num-ref name="suitable computing system environment">110</part-num-ref>
+ or operating environment in which the facility may be implemented. The computing system environment <part-num-ref name="computing system environment">110</part-num-ref>
+ 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 facility. Neither should the computing system environment <part-num-ref name="computing system environment">110</part-num-ref>
+ be interpreted as having any dependency or requirement relating to any one or a combination of components illustrated in the exemplary operating environment <part-num-ref name="exemplary operating environment">110.</part-num-ref>
+    </p>
+    <p id="p-73" num="73">[0059]     The facility 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 facility include, but are not limited to, personal computers, server computers, hand-held or laptop devices, tablet devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.</p>
+    <p id="p-74" num="74">[0060]     The facility 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, and so forth that perform particular tasks or implement particular abstract data types. The facility 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 local and/or remote computer storage media including memory storage devices.</p>
+    <p id="p-75" num="75">[0061]     With reference to Figure 12, an exemplary system for implementing the facility includes a general purpose computing device in the form of a computer <boundary-data type="header">[41826-8050-US<confidence value="5555">0000</confidence>
+/SL<confidence value="488">O41</confidence>
+540.120<confidence value="5">]</confidence>
+  -14-                     6/24/04      </boundary-data>
+      <page-break num="15"/>
+      <part-num-ref name="computer">111.</part-num-ref>
+ Components of the computer <part-num-ref name="computer">111</part-num-ref>
+ may include, but are not limited to, a processing unit <part-num-ref name="processing unit">120,</part-num-ref>
+ a system memory <part-num-ref name="system memory">130,</part-num-ref>
+ and a system bus <part-num-ref name="system bus">121</part-num-ref>
+ that couples various system components including the system memory <part-num-ref name="system memory">130</part-num-ref>
+ to the processing unit <part-num-ref name="processing unit">120.</part-num-ref>
+ The system bus <part-num-ref name="system bus">121</part-num-ref>
+ 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>
+    <p id="p-76" num="76">[0062]    The computer <part-num-ref name="computer">111</part-num-ref>
+ typically includes a variety of computer-readable media.    </p>
+    <p id="p-77" num="77">Computer-readable media can be any available media that can be accessed by the computer <part-num-ref name="computer">111</part-num-ref>
+ and includes both volatile and nonvolatile media and removable and nonremovable media. By way of example, and not limitation, computer- readable media may comprise computer storage media and communication media. Computer storage media include volatile and nonvolatile, removable and nonremovable 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 include, but are not limited to, RAM, ROM, EEPROM, 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 be accessed by the computer <part-num-ref name="computer">111.</part-num-ref>
+ Communication media typically embody 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 include 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 include wired media such as a wired network or <boundary-data type="header">[41826-8050-US<confidence value="5555">0000</confidence>
+/SL<confidence value="488">O41</confidence>
+540.120]  -15-                   6/24/04      </boundary-data>
+      <page-break num="16"/>
+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>
+    <p id="p-78" num="78">[0063]    The system memory <part-num-ref name="system memory">130</part-num-ref>
+ 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>
+ and random access memory (RAM) <part-num-ref name="and random access memory (RAM)">132.</part-num-ref>
+ A basic input/output system (BIOS) <part-num-ref name="basic input/output system (BIOS)">133,</part-num-ref>
+ containing the basic routines that help to transfer information between elements within the computer <part-num-ref name="computer">111,</part-num-ref>
+ such as during start-up, is typically stored in ROM <part-num-ref name="computer 111, such as during start-up, is typically stored in ROM">131.</part-num-ref>
+    </p>
+    <p id="p-79" num="79">RAM 132 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by the processing unit <part-num-ref name="processing unit">120.</part-num-ref>
+ By way of example, and not limitation, Figure 12 illustrates operating system <part-num-ref name="illustrates operating system">134,</part-num-ref>
+ application programs <part-num-ref name="illustrates operating system 134, application programs">135,</part-num-ref>
+ other program modules <part-num-ref name="illustrates operating system 134, application programs 135, other program modules">136</part-num-ref>
+ and program data <part-num-ref name="and program data">137.</part-num-ref>
+    </p>
+    <p id="p-80" num="80">[0064]    The computer <part-num-ref name="computer">111</part-num-ref>
+ may also include other removable/nonremovable, volatile/nonvolatile computer storage media. By way of example only, Figure 12 illustrates a hard disk drive <part-num-ref name="hard disk drive">141</part-num-ref>
+ that reads from or writes to nonremovable, nonvolatile magnetic media, a magnetic disk drive <part-num-ref name="magnetic disk drive">151</part-num-ref>
+ that reads from or writes to a removable, nonvolatile magnetic disk <part-num-ref name="removable, nonvolatile magnetic disk">152,</part-num-ref>
+ and an optical disk drive <part-num-ref name="optical disk drive">155</part-num-ref>
+ that reads from or writes to a removable, nonvolatile optical disk <part-num-ref name="removable, nonvolatile optical disk">156</part-num-ref>
+ such as a CD- ROM or other optical media. Other removable/nonremovable, 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. The hard disk drive <part-num-ref name="hard disk drive">141</part-num-ref>
+ is typically connected to the system bus <part-num-ref name="system bus">121</part-num-ref>
+ through a nonremovable memory interface such as interface <part-num-ref name="nonremovable memory interface such as interface">140,</part-num-ref>
+ and magnetic disk drive <part-num-ref name="nonremovable memory interface such as interface 140, and magnetic disk drive">151</part-num-ref>
+ and optical disk drive <part-num-ref name="and optical disk drive">155</part-num-ref>
+ are typically connected to the system bus <part-num-ref name="system bus">121</part-num-ref>
+ by a removable memory interface, such as interface <part-num-ref name="removable memory interface, such as interface">150.</part-num-ref>
+    </p>
+    <p id="p-81" num="81">[0065]    The drives and their associated computer storage media, discussed above and illustrated in Figure 12, provide storage of computer-readable instructions, data structures, program modules, and other data for the computer <part-num-ref name="computer">111.</part-num-ref>
+ In Figure 12, for example, hard disk drive <part-num-ref name="computer 111. In Figure 12, for example, hard disk drive">141</part-num-ref>
+ is illustrated as storing operating system <part-num-ref name="is illustrated as storing operating system">144,</part-num-ref>
+ <boundary-data type="header">[41826-8050-US<confidence value="5555">0000</confidence>
+/SL<confidence value="488">041</confidence>
+540.120]  -16-                   6/24/04      </boundary-data>
+      <page-break num="17"/>
+application programs <part-num-ref name="is illustrated as storing operating system 144, application programs">145,</part-num-ref>
+ other program modules <part-num-ref name="is illustrated as storing operating system 144, application programs 145, other program modules">146</part-num-ref>
+ and program data <part-num-ref name="and program data">147.</part-num-ref>
+    </p>
+    <p id="p-82" num="82">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>
+ application programs <part-num-ref name="same as or different from operating system 134, application programs">135,</part-num-ref>
+ 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>
+ 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>
+ 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>
+ 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>
+ 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>
+ 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>
+ are given different numbers herein 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">111</part-num-ref>
+ through input devices such as a tablet or electronic digitizer <part-num-ref name="tablet or electronic digitizer">164,</part-num-ref>
+ a microphone <part-num-ref name="microphone">163,</part-num-ref>
+ a keyboard <part-num-ref name="keyboard">162</part-num-ref>
+ and pointing device <part-num-ref name="and pointing device">161,</part-num-ref>
+ commonly referred to as a mouse, trackball or touch pad. Other input devices not shown in Figure 12 may include a 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>
+ through a user input interface <part-num-ref name="user input interface">160</part-num-ref>
+ that is coupled to the system bus <part-num-ref name="system bus">121,</part-num-ref>
+ 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>
+ or other type of display device is also connected to the system bus <part-num-ref name="system bus">121</part-num-ref>
+ via an interface, such as a video interface <part-num-ref name="video interface">190.</part-num-ref>
+ The monitor <part-num-ref name="monitor">191</part-num-ref>
+ may also be integrated with a touch-screen panel or the like. Note that the monitor <part-num-ref name="monitor">191</part-num-ref>
+ and/or touch screen panel can be physically coupled to a housing in which the computer <part-num-ref name="computer">111</part-num-ref>
+ is incorporated, such as in a tablet-type personal computer. In addition, computing devices such as the computer <part-num-ref name="computer">111</part-num-ref>
+ may also include other peripheral output devices such as speakers <part-num-ref name="may also include other peripheral output devices such as speakers">195</part-num-ref>
+ and printer <part-num-ref name="and printer">196,</part-num-ref>
+ which may be connected through an output peripheral interface <part-num-ref name="output peripheral interface">194</part-num-ref>
+ or the like.    </p>
+    <p id="p-83" num="83">[0066]    The computer <part-num-ref name="computer">111</part-num-ref>
+ 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>
+    </p>
+    <p id="p-84" num="84">The remote computer 180 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">111,</part-num-ref>
+ although only a memory storage device <part-num-ref name="memory storage device">181</part-num-ref>
+ has been illustrated in Figure 12.    </p>
+    <p id="p-85" num="85">The logical connections depicted in Figure 12 include a local area network (LAN) <part-num-ref name="local area network (LAN)">171</part-num-ref>
+ and a wide area network (WAN) <part-num-ref name="wide area network (WAN)">173,</part-num-ref>
+ but may also include other networks.    </p>
+    <boundary-data type="header">
+      <confidence value="588">[41</confidence>
+826-8050-US<confidence value="5555">0000</confidence>
+/SL<confidence value="488">O41</confidence>
+540.120]  -17-                   6/24/04    </boundary-data>
+    <p id="p-86" num="86">
+      <page-break num="18"/>
+Such networking environments are commonplace in offices, enterprisewide computer networks, intranets and the <confidence value="5">I</confidence>
+nternet. For example, in the present facility, the computer <part-num-ref name="computer">111</part-num-ref>
+ may comprise the source machine from which data is being migrated, and the remote computer <part-num-ref name="remote computer">180</part-num-ref>
+ may comprise the destination machine. Note, however, that source and destination machines need not be connected by a network or any other means, but instead, data may be migrated via any media capable of being written by the source platform and read by the destination platform or platforms.    </p>
+    <p id="p-87" num="87">[0067]    When used in a LAN networking environment, the computer <part-num-ref name="computer">111</part-num-ref>
+ is connected to the LAN <part-num-ref name="LAN">171</part-num-ref>
+ through a network interface or adapter <part-num-ref name="network interface or adapter">170.</part-num-ref>
+ When used in a WAN networking environment, the computer <part-num-ref name="computer">111</part-num-ref>
+ typically includes a modem <part-num-ref name="modem">172</part-num-ref>
+ or other means for establishing communications over the WAN <part-num-ref name="WAN">173,</part-num-ref>
+ such as the <confidence value="5">I</confidence>
+nternet. The modem <part-num-ref name="modem">172,</part-num-ref>
+ which may be internal or external, may be connected to the system bus <part-num-ref name="system bus">121</part-num-ref>
+ via the user input interface <part-num-ref name="user input interface">160</part-num-ref>
+ or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer <part-num-ref name="computer">111,</part-num-ref>
+ or portions thereof, may be stored in the remote memory storage device <part-num-ref name="remote memory storage device">181.</part-num-ref>
+ By way of example, and not limitation, Figure 12 illustrates remote application programs <part-num-ref name="illustrates remote application programs">185</part-num-ref>
+ as residing on memory storage device <part-num-ref name="as residing on memory storage device">181.</part-num-ref>
+ 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.    </p>
+    <p id="p-88" num="88">
+      <confidence value="5">[</confidence>
+0068<confidence value="5">]</confidence>
+    While various functionalities and data are shown in Figure 12 as residing on particular computer systems that are arranged in a particular way, those skilled in the art will appreciate that such functionalities and data may be distributed in various other ways across computer systems in different arrangements. While computer systems configured as described above are typically used to support the operation of the facility, one of ordinary skill in the art will appreciate that the facility may be implemented using devices of various types and configurations, and having various components.    </p>
+    <boundary-data type="header">[41826-8050-US<confidence value="5555">0000</confidence>
+/SL<confidence value="488">O41</confidence>
+540.120<confidence value="5">]</confidence>
+  -18-                    6/24/04    </boundary-data>
+    <p id="p-89" num="89">
+      <page-break num="19"/>
+      <confidence value="5">[</confidence>
+0069<confidence value="5">]</confidence>
+     The techniques for causing project management software to explain task scheduling for a project may be described in the general context of computer- executable instructions, such as program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Typically, the functionality of the program modules may be combined or distributed as desired in various embodiments.    </p>
+    <p id="p-90" num="90">
+      <confidence value="5">[</confidence>
+0070<confidence value="5">]</confidence>
+     From the foregoing, it will be appreciated that specific embodiments of the invention have been described herein for purposes of illustration, but that various modifications may be made without deviating from the spirit and scope of the invention. Accordingly, the invention is not limited except as by the appended claims.    </p>
+    <boundary-data type="header">[41826-8050-US0000/SL<confidence value="488">O41</confidence>
+540.120]  -19-                      6/24/04    </boundary-data>
+  </description>
+</us-patent-application>
+

prior_art/10922417.xml

@@ -0,0 +1,401 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>10922417</doc-number>
+        <date>2004-08-20</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <heading id="h-1">U.S. PATENT APPLICATION</heading>
+    <p id="p-1" num="1">for </p>
+    <heading id="h-2">CONTEXT DATA IN UPNP SERVICE INFORMATION</heading>
+    <p id="p-2" num="2">Inventors: Jose Costa Requena Markku Tamski As Assignors to:</p>
+    <p id="p-3" num="3">Nokia Corporation P.O. Box 226 FIN-00045 <confidence value="22222">NOKIA</confidence>
+ GROUP Finland <page-break num="2"/>
+      <boundary-data type="header">Atty. <confidence value="5">D</confidence>
+kt. No.: 037145-4901 (NC 44467)      </boundary-data>
+    </p>
+    <heading id="h-3">CONTEXT DATA IN UPNP SERVICE INFORMATION</heading>
+    <heading id="h-4">FIELD OF THE INVENTION</heading>
+    <p id="p-4" num="4">[0001] The present invention is related to networks. More particularly, the present invention relates to resource discovery in a UPNP environment using context information.</p>
+    <heading id="h-5">BACKGROUND OF THE INVENTION</heading>
+    <p id="p-5" num="5">[0002] Universal Plug and Play (UPnPTM) defines an architecture for the network connectivity of intelligent consumer electronics, wireless devices, printers, and PCs of all form factors. The goal of UPnP technology is to provide easy-to-use, flexible, standards-based connectivity for ad-hoc or unmanaged networks whether in a home, in a small business, or in public spaces. In support of this goal, UPnP supports zero-configuration, "invisible" networking, and the automatic discovery of devices from a wide range of manufacturers. As a result, a device can dynamically join a network, obtain an IP address, convey its capabilities to the network, and determine the presence and capabilities of other devices. UPnP also provides a consistent, interoperable framework for remote Internet Gateway Device (IGD) configuration and management. UPnP is built using Hypertext Transfer Protocol (HTTP) over the User Datagram Protocol/Internet Protocol (UDP/IP) or the Transmission Control Protocol/Internet Protocol (TCP/IP) in addition to the eXtensible Markup Language (XML). HTTPU and HTTPMU are variants of HTTP defined to deliver messages over UDP/IP instead of TCP/IP.</p>
+    <p id="p-6" num="6">[0003] Devices on a UPnP network can be connected using any communication media including Radio Frequency wireless (including Radio Frequency IDentification (RFID)), phone line, power line, IrDA, Ethernet, and Institute of Electrical and Electronics Engineers (IEEE) <part-num-ref name="UPnP network can be connected using any communication media including Radio Frequency wireless (including Radio Frequency IDentification (RFID)), phone line, power line, IrDA, Ethernet, and Institute of Electrical and Electronics Engineers (IEEE)">1394.</part-num-ref>
+    </p>
+    <boundary-data type="header">-1-</boundary-data>
+    <boundary-data type="header">011.1211983.1</boundary-data>
+    <boundary-data type="header">Atty. Dkt. No.: 037145-4901 (NC 44467)</boundary-data>
+    <p id="p-7" num="7">
+      <page-break num="3"/>
+Thus, any communication medium that can be used to network devices can enable UPnP.    </p>
+    <p id="p-8" num="8">[0004] UPnP is an open networking architecture that consists of services, devices, and control points. Services are groups of states and actions. For example, a light switch has an "on" state and an "off<confidence value="5">"</confidence>
+ state. An action allows the network to determine the state of the switch or to change the state of the switch and is a command that can be used to trigger services to perform a function. Services typically reside in devices and provide device functionality that can be controlled using control points. A device may be a physical device such as a camcorder or a logical device such as a computer that is performing the functions of a camcorder. Devices may be physical or logical entities and are specified using simple XML descriptions and containing Application Programming Interfaces (APIs) for providing services.    </p>
+    <p id="p-9" num="9">Physical devices may host multiple logical devices, and each device may host multiple services. Control points are software applications that retrieve UPnP service and device descriptions, that send actions to services, and that receive events from services. A control point is capable of discovering and controlling other devices. An event is a message from a device to a control point that is used to keep subscribed control points informed of device status.</p>
+    <p id="p-10" num="10">A UPnP device may be a container for services and nested devices. For example, a combination TV/DVD player provides services and includes a nested device that may be the DVD player, for example.</p>
+    <p id="p-11" num="11">[0005] Messages are transported over UPnP networks using HTTP over the UDP/IP or TCP/IP. The supported message formats are Simple Service Discovery Protocol (SSDP), General Event Notification Architecture (GENA), and Simple Object Access Protocol (SOAP). UPnP relies on these three protocols to enable networking without a classical network administrator. SSDP provides for the discovery of devices on the network. GENA provides for subscribing to event reports and for the publication of those events. SOAP provides for control of the network devices <boundary-data type="header">-2-</boundary-data>
+      <boundary-data type="header">011.1211983.1</boundary-data>
+      <page-break num="4"/>
+      <boundary-data type="header">Atty. Dkt. No.: 037145-4901 (NC 44467)</boundary-data>
+through remote procedure calls between control points and devices.    </p>
+    <p id="p-12" num="12">Required UPnP information is inserted into all messages before they are formatted using SSDP, GENA, and SOAP and delivered via HTTP, HTTPU, or HTTPMU.</p>
+    <p id="p-13" num="13">[0006] Given an <confidence value="5">I</confidence>
+P address, the first step in UPnP networking is discovery. The discovery process for a UPnP device includes advertisement of the device presence on the network to other devices and control points using SSDP. Thus, when a device is added to a network, the device advertises its services to the control points on the network. Similarly, a new control point discovers UPnP devices on a network using SSDP. If an SSDP service hears a discovery request that matches a service that it offers then the service responds to the control point. Thus, UPnP allows a control point to search for devices of interest on the network.    </p>
+    <p id="p-14" num="14">[0007] The information exchanged between the device and the control point in both cases is a discovery message that provide basic information about the devices or one of its services, and a description Uniform Resource Locator <confidence value="5">(</confidence>
+URL) that can be used to gather additional detailed information about the device.<confidence value="2">.</confidence>
+ XML is used to describe the device features and capabilities. The notification announcement message URL points to an XML file in the network that contains a description of the UPnP device's capability. Thus, by retrieving the XML file, other devices can evaluate the features of the device and determine if the features satisfy their requirements.    </p>
+    <p id="p-15" num="15">Thus, after a control point discovers a device, the control point retrieves the device's service description from the URL provided by the device in the discovery message. The UPnP description for a device includes a list of any embedded devices or service, as well as URLs for control, for eventing, and for presentation.</p>
+    <p id="p-16" num="16">[0008] The UPnP description for a service includes a list of actions the service responds to and a list of variables that model the state of the service. The service publishes updates when these variables change by <boundary-data type="header">-3-</boundary-data>
+      <boundary-data type="header">011.1211983.1</boundary-data>
+      <page-break num="5"/>
+      <boundary-data type="header">Atty. Dkt. No.: 037145-4901 (NC 44467)</boundary-data>
+sending event messages. A control point may subscribe to this information so that it automatically receives the updates. Event messages contain the names of one of more state variables and the current value of those variables.    </p>
+    <p id="p-17" num="17">These messages are also expressed in XML and formatted using GENA.</p>
+    <p id="p-18" num="18">Thus, after retrieving the description of the device, the control point can send actions to a device's service by sending a suitable control message to the control URL for the service.</p>
+    <p id="p-19" num="19">[0009] Control messages are also expressed in XML using SOAP. In response to the control message, the service returns any action- specific values. Additionally, if a device has a URL for presentation, the control point can retrieve a page from this URL, load the page into a browser, and depending on the capabilities of the page, allow a user to control the device and/or view device status. Each UPnP control request is a SOAP message that contains the action to invoke along with a set of parameters.</p>
+    <p id="p-20" num="20">The response is a soap message as well and contains the status, return value, and any return parameters. The control point can refine the search to find only devices of a particular type, that perform particular services, or a specific device. The control point can not, however, refine the search based on context information. Context information includes additional information about the device and the services that the device is capable of providing. For example, the context information may include the current geographic location of the device. Context information may include the device availability for example if the device is a printer or a facsimile machine.</p>
+    <p id="p-21" num="21">[0010] What is needed, therefore, is a method of including context information to refine a search for a device or a search for an item at a device in a UPnP environment. What is further needed is a method of including the existence of context information to refine a search for a device in a UPnP environment.</p>
+    <boundary-data type="header">-4-</boundary-data>
+    <boundary-data type="header">011.1211983.1</boundary-data>
+    <boundary-data type="header">Atty. Dkt. No.: 037145-4901 (NC 44467)</boundary-data>
+    <heading id="h-6">SUMMARY OF THE INVENTION</heading>
+    <p id="p-22" num="22">
+      <page-break num="6"/>
+[0011] An exemplary embodiment of the invention relates to a device for performing a service for a second device. The device includes, but is not limited to, a memory, a communication interface, and a processor. The memory stores a device service description, wherein the device service description includes context information of the device. The communication interface is configured to receive a request sent from a first device using a network, the request to retrieve the device service description, and to send a response to the first device using the network, the response including the device service description. The processor couples to the communication interface and to the memory and is configured to select the device service description from the memory and to create the response including the device service description.    </p>
+    <p id="p-23" num="23">[0012] A format of the response may be, but is not limited to, a Simple Service Discovery Protocol and a Simple Object Access Protocol. A format of the request may be, but is not limited to, a Simple Service Discovery Protocol and a Simple Object Access Protocol. The context information may include, but is not limited to, a geographic location of the device.</p>
+    <p id="p-24" num="24">[0013] Another exemplary embodiment of the invention relates to a device for selecting another device to perform a service. The device includes, but is not limited to, a communication interface and a processor.</p>
+    <p id="p-25" num="25">The communication interface is configured to send a first request to a first device using a network, the first request to retrieve a first device service description from the first device, the first device service description including context information of the first device, and to receive a first response from the first device using the network, the first response including the first device service description. The processor couples to the communication interface and is configured to select the first device to perform a first service for the device based on the context information of the first device included in the first device service description.</p>
+    <boundary-data type="header">-5-</boundary-data>
+    <boundary-data type="header">011.1211983.1</boundary-data>
+    <boundary-data type="header">Atty. Dkt. No.: 037145-4901 (NC 44467)</boundary-data>
+    <p id="p-26" num="26">
+      <page-break num="7"/>
+[0014] A format of the response may be, but is not limited to, a Simple Service Discovery Protocol and a Simple Object Access Protocol. A format of the request may be, but is not limited to, a Simple Service Discovery Protocol and a Simple Object Access Protocol. The context information may include, but is not limited to, a geographic location of the device.    </p>
+    <p id="p-27" num="27">[0015] The processor may be further configured to determine a geographic location of the device, to determine a pointing direction to the first device from the device, and to identify the first device based on the pointing direction to the first device from the device, the geographic location of the first device, and the geographic location of the device. The communication interface may be further configured to send a second request to a second device using the network, the second request to retrieve a second device service description from the second device, the second device service description including context information of the second device, and to receive a second response from the second device using the network, the second response including the second device service description. The processor may be further configured to select the second device to perform a second service related to the first service for the device based on the context information of the second device included in the second device service description. The context information of the second device may include, but is not limited to, a geographic location of the second device. The processor may be further configured to determine a pointing direction to the second device from the device and to identify the second device based on the pointing direction to the second device from the device, the geographic location of the second device, and the geographic location of the device.</p>
+    <p id="p-28" num="28">[0016] Another exemplary embodiment of the invention relates to a system for selecting a device to perform a service. The system includes, but is not limited to, a first device and a second device. The first device includes, but is not limited to, a memory, a first communication interface, and a first processor. The memory stores a first device service description <boundary-data type="header">-6-</boundary-data>
+      <boundary-data type="header">011.1211983.<confidence value="8">1</confidence>
+      </boundary-data>
+      <page-break num="8"/>
+      <boundary-data type="header">Atty. Dkt. No.: 037145-4901 (NC 44467)</boundary-data>
+wherein the first device service description includes context information of the first device. The first communication interface is configured to receive a first request from a second device using a network, the first request to retrieve the first device service description from the first device, and to send a first response to the second device using the network, the first response including the first device service description. The first processor couples to the first communication interface and to the memory and is configured to select the first device service description from the first memory and to create the first response including the first device service description.    </p>
+    <p id="p-29" num="29">[0017] The second device includes, but is not limited to, a second communication interface and a second processor. The second communication interface is configured to send the first request to retrieve the first device service description from the first device and to receive the first response from the first device. The second processor couples to the second communication interface and is configured to select the first device to perform a first service for the second device based on the context information of the first device included in the first device service description.</p>
+    <p id="p-30" num="30">[0018]<confidence value="5">.</confidence>
+ Another exemplary embodiment of the invention relates to a method of selecting a device to perform a service. The method includes, but is not limited to, retrieving a first device service description from a first device using a network, the first device service description including context information of the first device, and selecting the first device to perform a first service for a second device based on the context information of the first device included in the first device service description.    </p>
+    <p id="p-31" num="31">[0019] The context information of the first device may include, but is not limited to, a geographic location of the first device. Selecting the first device to perform the first service for the second device may include, but is not limited to, pointing the second device at the first device, determining a geographic location of the second device, determining a pointing direction to the first device from the second device, and selecting the first device based <boundary-data type="header">-7-</boundary-data>
+      <boundary-data type="header">011.1211983.1</boundary-data>
+      <page-break num="9"/>
+      <boundary-data type="header">Atty. Dkt. No.: 037145-4901 (NC 44467)</boundary-data>
+on the pointing direction to the first device from the second device, the geographic location of the first device, and the geographic location of the second device.    </p>
+    <p id="p-32" num="32">[0020] The method may further include retrieving a second device service description from a third device using the network, the second device service description including context information of the third device, and selecting the third device to perform a second service related to the first service for the second device based on the context information of the third device included in the second device service description.</p>
+    <p id="p-33" num="33">[0021] The context information of the third device may include, but is not limited to, a geographic location of the third device. Selecting the third device to perform the second service for the second device may include, but is not limited to, pointing the second device at the third device, determining a pointing direction to the third device from the second device, and identifying the third device based on the pointing direction to the third device from the second device, the geographic location of the third device, and the geographic location of the second device.</p>
+    <p id="p-34" num="34">[0022] The method may further include selecting an item in a display at the second device while pointing the second device at the first device and releasing the item in the display at the second device while pointing the second device at the third device, thereby copying the item from the first device to the third device.</p>
+    <p id="p-35" num="35">[0023] Another exemplary embodiment of the invention relates to a computer program product for selecting a device to perform a service, the computer program product includes, but is not limited to, computer code configured to retrieve a first device service description from a first device using a network, the first device service description including context information of the first device, and to select the first device to perform a first <boundary-data type="header">-8-</boundary-data>
+      <boundary-data type="header">011.1211983.1</boundary-data>
+      <page-break num="10"/>
+      <boundary-data type="header">Atty. Dkt. No.: 037145-4901 (NC 44467)</boundary-data>
+service for a second device based on the context information of the first device included in the first device service description.    </p>
+    <p id="p-36" num="36">[0024] Another exemplary embodiment of the invention relates to a device for performing a service for a second device. The device includes, but is not limited to, a communication interface and a processor. The communication interface is configured to receive a request sent from a first device using a network, the request to perform a service at the device, and the request including context information associated with the service, and to send a response to the first device using the network. The processor couples to the communication interface and is configured to perform the service based on the context information.</p>
+    <p id="p-37" num="37">[0025] Another exemplary embodiment of the invention relates to a device for requesting a service from another device. The device includes, but is not limited to, a communication interface and a processor. The communication interface is configured to send a request using a network to a first device, the request to perform a service at the first device, and the request including context information associated with the service, and to receive a response from the first device. The processor couples to the communication interface and is configured to create the request including the context information.</p>
+    <p id="p-38" num="38">[0026] Another exemplary embodiment of the invention relates to a system for requesting a service from another device. The system includes, but is not limited to, a first device and a second device. The first device includes, but is not limited to, a first communication interface and a first processor. The first communication interface is configured to receive a request sent from a second device using a network, the request to perform a service at the first device, and the request including context information associated with the service, and to send a response to the second device using the network. The first processor couples to the first communication interface and is configured to perform the service based on the context <boundary-data type="header">-9-</boundary-data>
+      <boundary-data type="header">011.1211983.1</boundary-data>
+      <page-break num="11"/>
+      <boundary-data type="header">Atty. Dkt. No.: 037145-4901 (NC 44467)</boundary-data>
+information. The second device includes, but is not limited to, a second communication interface and a second processor. The second communication interface is configured to send the request using the network to the first device, and to receive the response to the request from the first device. The second processor couples to the second communication interface and is configured to create the request including the context information.    </p>
+    <p id="p-39" num="39">[0027] Another exemplary embodiment of the invention relates to a method for requesting a service from another device. The method includes, but is not limited to, creating a request, the request to perform a service at a first device, and the request including context information associated with the service, sending the request using a network to the first device, and receiving a response to the request from the first device.</p>
+    <p id="p-40" num="40">[0028] Another exemplary embodiment of the invention relates to a computer program product for requesting a service from another device.</p>
+    <p id="p-41" num="41">The computer program product includes, but is not limited to, computer code configured to create a request, the request to perform a service at a first device, and the request including context information associated with the service, to send the request using a network to the first device, and to receive a response to the request from the first device.</p>
+    <p id="p-42" num="42">[0029] Another exemplary embodiment of the invention relates to a device for performing a service for a second device. The device includes, but is not limited to, a communication interface and a processor. The communication interface is configured to receive a request sent from a first device using a network, the request to perform a service at the device, and to send a response to the first device using the network, the response including context information associated with the service. The processor couples to the communication interface and is configured to create the response including the context information and to perform the service.</p>
+    <boundary-data type="header">-10-</boundary-data>
+    <boundary-data type="header">011.1211983.1</boundary-data>
+    <boundary-data type="header">Atty. Dkt. No.: 037145-4901 (NC 44467)</boundary-data>
+    <p id="p-43" num="43">
+      <page-break num="12"/>
+[0030] Another exemplary embodiment of the invention relates to a device for requesting a service from another device. The device includes, but is not limited to, a communication interface and a processor. The communication interface is configured to send a request using a network to a first device, the request to perform a service at the first device, and to receive a response from the first device, the response including context information associated with the service. The processor couples to the communication interface and is configured to create the request.    </p>
+    <p id="p-44" num="44">[0031] Another exemplary embodiment of the invention relates to a system for requesting a service from another device. The system includes, but is not limited to, a first device and a second device. The first device includes, but is not limited to, a first communication interface and a first processor. The first communication interface is configured to receive a request sent from a second device using a network, the request to perform a service at the first device, and to send a response to the second device using the network, the response including context information associated with the service. The first processor couples to the first communication interface and is configured to create the response including the context information and to perform the service. The second device includes, but is not limited to, a second communication interface and a second processor. The second communication interface is configured to send the request using the network to the first device, the request to perform the service at the first device, and to receive a response from the first device. The second processor couples to the second communication interface and is configured to create the request.</p>
+    <p id="p-45" num="45">[0032] Another exemplary embodiment of the invention relates to a method for requesting a service from another device. The method includes, but is not limited to, creating a request, the request to perform a service at a first device, sending the request using a network to the first device, and receiving a response to the request from the first device, the response including context information associated with the service.</p>
+    <boundary-data type="header">-11-</boundary-data>
+    <boundary-data type="header">011.1211983.1</boundary-data>
+    <boundary-data type="header">Atty. Dkt. No.: 037145-4901 (NC 44467)</boundary-data>
+    <p id="p-46" num="46">
+      <page-break num="13"/>
+[0033] Another exemplary embodiment of the invention relates to a computer program product for requesting a service from another device.    </p>
+    <p id="p-47" num="47">The computer program product includes, but is not limited to, computer code configured to create a request, the request to perform a service at a first device, to send the request using a network to the first device, and to receive a response to the request from the first device, the response including context information associated with the service.</p>
+    <p id="p-48" num="48">[0034] Other principal features and advantages of the invention will become apparent to those skilled in the art upon review of the following drawings, the detailed description, and the appended claims.</p>
+    <heading id="h-7">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
+    <p id="p-49" num="49">[0035] The preferred embodiments will hereafter be described with reference to the accompanying drawings, wherein like numerals will denote like elements.</p>
+    <p id="p-50" num="50">[0036] FIG. <confidence value="5">1</confidence>
+ is an overview diagram of a system in accordance with an exemplary embodiment.    </p>
+    <p id="p-51" num="51">[0037] FIG. 2 is a block diagram of a first device in accordance with an exemplary embodiment.</p>
+    <p id="p-52" num="52">[0038] FIG. 3 is a block diagram of a second device in accordance with an exemplary embodiment.</p>
+    <p id="p-53" num="53">[0039] FIG. 4 is an overview diagram of a message sequence in accordance with an exemplary embodiment.</p>
+    <p id="p-54" num="54">[0040] FIG. 5 is an overview diagram of a sample use case in accordance with an exemplary embodiment.</p>
+    <boundary-data type="header">-12-</boundary-data>
+    <boundary-data type="header">011.1211983.1</boundary-data>
+    <boundary-data type="header">Atty. Dkt. No.: 037145<confidence value="5">-</confidence>
+4901 (NC 44467)    </boundary-data>
+    <heading id="h-8">DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS</heading>
+    <p id="p-55" num="55">
+      <page-break num="14"/>
+[0041] The term "device" as used herein includes a variety of network nodes. Such network nodes include printers, workstations, servers (for example, printer servers or file servers), scanners, PCs of all form factors, intelligent appliances (for example, cameras, video cameras, TVs, DVD players, radios), etc. The devices communicate over a network using communication protocols such as, for example, TCP/IP and UDP/IP. A device advertises its ability to perform a service and may be controlled by another device denoted a control point as related previously. The control point listens or searches for devices that it is capable of controlling to identify and to select devices to perform services for the control point. The device advertises its services possibly through an address to a page written in XML format. The XML formatted file includes information about the device and the services that the device may provide and is denoted a device service description. The XML formatted file may also include the address to additional information relating to the services advertised by and provided by the device. The additional information may also be captured in an XML formatted file. The control point may issue simple HTTP Get Requests to retrieve the device service description. The device may respond with an HTTP Get Response that includes the device service description. Using this description, the control point may select the device to perform a particular service for the control point.    </p>
+    <p id="p-56" num="56">[0042] With reference to FIG. 1, the system <part-num-ref name="system">2</part-num-ref>
+ comprises a network <part-num-ref name="network">4.</part-num-ref>
+ The network <part-num-ref name="network">4</part-num-ref>
+ includes a plurality of devices <part-num-ref name="plurality of devices">24.</part-num-ref>
+ The plurality of devices <part-num-ref name="plurality of devices">24</part-num-ref>
+ may comprise a cellular telephone <part-num-ref name="cellular telephone">6,</part-num-ref>
+ an Integrated Communication Device (<confidence value="5">I</confidence>
+CD) <part-num-ref name="Integrated Communication Device (ICD)">8,</part-num-ref>
+ a Personal Data Assistant (PDA) <part-num-ref name="Personal Data Assistant (PDA)">10,</part-num-ref>
+ a PC <part-num-ref name="PC">12</part-num-ref>
+ of any form factor including a laptop <part-num-ref name="laptop">14,</part-num-ref>
+ a printer <part-num-ref name="printer">16,</part-num-ref>
+ a scanner <part-num-ref name="scanner">18,</part-num-ref>
+ a TV <part-num-ref name="TV">20,</part-num-ref>
+ a video camera <part-num-ref name="video camera">22,</part-num-ref>
+ etc. The devices <part-num-ref name="devices">24</part-num-ref>
+ may communicate using various transmission technologies including, but not limited to, Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), Universal <boundary-data type="header">-13-</boundary-data>
+      <boundary-data type="header">011.1211983.1</boundary-data>
+      <page-break num="15"/>
+      <boundary-data type="header">Atty. Dkt. No.: 037145-4901 (NC 44467)</boundary-data>
+Mobile Telecommunications System (UMTS), Time Division Multiple Access (TDMA), TCP/IP, UDP/IP, Short Messaging Service, Multimedia Messaging Service, e-mail, Instant Messaging, Bluetooth, IEEE 802.11, etc. The devices <part-num-ref name="devices">24</part-num-ref>
+ may communicate using various media including, but not limited to, radio, infrared, laser, cable connection, etc. The network <part-num-ref name="network">4</part-num-ref>
+ may include additional devices <part-num-ref name="may include additional devices">24.</part-num-ref>
+ Some or all of the devices <part-num-ref name="devices">24</part-num-ref>
+ of system <part-num-ref name="of system">2</part-num-ref>
+ may comprise a control point device <part-num-ref name="control point device">26.</part-num-ref>
+ The system <part-num-ref name="system">2</part-num-ref>
+ may comprise any combination of wired or wireless networks including, but not limited to, a cellular telephone network, a wireless Local Area Network (LAN), a Bluetooth personal area network, an Ethernet LAN, token ring LAN, a wide area network, the Internet, etc. The system <part-num-ref name="system">2</part-num-ref>
+ may include both wired and wireless devices.    </p>
+    <p id="p-57" num="57">[0043] Communication between devices 24, 26 may be through one or more of the following connection methods without limitation: a link established according to the Bluetooth Standards and Protocols, an infrared communications link, a wireless communications link, a cellular network link, a physical serial connection, a physical parallel connection, a link established according to TCP/IP, etc.</p>
+    <p id="p-58" num="58">
+      <confidence value="86666">[0044</confidence>
+] With reference to FIG. 2, the device <part-num-ref name="device">24</part-num-ref>
+ comprises a display <part-num-ref name="display">30,</part-num-ref>
+ a communication interface <part-num-ref name="communication interface">32,</part-num-ref>
+ a processor <part-num-ref name="processor">34,</part-num-ref>
+ a memory <part-num-ref name="memory">36,</part-num-ref>
+ and a device service description <part-num-ref name="device service description">38.</part-num-ref>
+ Different and additional components may be incorporated into the device <part-num-ref name="device">24.</part-num-ref>
+ The display <part-num-ref name="display">30</part-num-ref>
+ of the device <part-num-ref name="device">24</part-num-ref>
+ is optional.    </p>
+    <p id="p-59" num="59">The display 30 presents information to a user. The display <part-num-ref name="display">30</part-num-ref>
+ may be a thin film transistor (TFT) display, a light emitting diode (LED) display, a Liquid Crystal Display (LCD), or any of a variety of different displays known to those skilled in the art.    </p>
+    <p id="p-60" num="60">[0045] The communication interface <part-num-ref name="communication interface">32</part-num-ref>
+ provides an interface for receiving and transmitting calls, messages, and any other information communicable between devices. Communications between the device <part-num-ref name="device">24</part-num-ref>
+ and other devices <part-num-ref name="and other devices">24,</part-num-ref>
+ and/or to the control point device <part-num-ref name="control point device">26</part-num-ref>
+ may be through one or more of the following connection methods, without limitation: an <boundary-data type="header">-14-</boundary-data>
+      <boundary-data type="header">011.1211983.1</boundary-data>
+      <page-break num="16"/>
+      <boundary-data type="header">Atty. Dkt. No.: 037145-4901 (NC 44467)</boundary-data>
+infrared communications link, a radio frequency communication link, a wireless communications link, a cellular network link, a link established according to TCP/IP, etc. Transferring content to and from the device may be through one or more of these connection methods. The device <part-num-ref name="device">24</part-num-ref>
+ may communicate using various transmission technologies including, but not limited to, CDMA, GSM, UMTS, TDMA, TCP/IP, Bluetooth, IrDA, R<confidence value="5">F</confidence>
+ID, etc.    </p>
+    <p id="p-61" num="61">The device 24 may communicate using various media including, but not limited to, radio, infrared, laser, optical, range reduced Bluetooth, cable connection, etc.</p>
+    <p id="p-62" num="62">[0046] The processor <part-num-ref name="processor">34</part-num-ref>
+ executes instructions that cause the device <part-num-ref name="device">24</part-num-ref>
+ to behave in a predetermined manner. The instructions may be written using one or more programming languages, scripting languages, assembly languages, etc. Additionally, the instructions may be carried out by a special purpose computer, logic circuits, or hardware circuits. Thus, the processor <part-num-ref name="processor">34</part-num-ref>
+ may be implemented in hardware, firmware, software, or any combination of these methods. The term "execution" is the process of running a program or the carrying out of the operation called for by an instruction. The processor <part-num-ref name="processor">34</part-num-ref>
+ executes an instruction, meaning that it performs the operations called for by that instruction. The processor <part-num-ref name="processor">34</part-num-ref>
+ couples to the communication interface <part-num-ref name="communication interface">32.</part-num-ref>
+    </p>
+    <p id="p-63" num="63">[0047] The processor <part-num-ref name="processor">34</part-num-ref>
+ may retrieve a set of instructions from a permanent memory device and copy the instructions in an executable form to a temporary memory device. The temporary memory device is generally some form of random access memory (RAM). The data in RAM is volatile meaning that it remains only as long as the device is turned on. When the device is turned off, RAM loses its data. Read only memory (ROM) refers to special memory used to store programs that boot the device and perform diagnostics. The values stored in ROM are always there, whether the power is on or not. For this reason, it is called non-volatile memory. Flash memory <boundary-data type="header">-15-</boundary-data>
+      <boundary-data type="header">011.1211983.1</boundary-data>
+      <page-break num="17"/>
+      <boundary-data type="header">Atty. Dkt. No.: 037145-4901 (NC 44467)</boundary-data>
+is a type of constantly-powered nonvolatile memory that can be erased and reprogrammed in units of memory called blocks.    </p>
+    <p id="p-64" num="64">[0048] The memory <part-num-ref name="memory">36</part-num-ref>
+ stores the device service description <part-num-ref name="device service description">38.</part-num-ref>
+ The device may have a plurality of memories <part-num-ref name="plurality of memories">36</part-num-ref>
+ using different memory technologies including, but not limited to, RAM, ROM, flash memory, etc. The memory may include a cache. The cache may include, but is not limited to, a dedicated bank of high-speed memory or a reserved section of regular memory used to improve performance. The cache provides a temporary storage area for instructions and data.    </p>
+    <p id="p-65" num="65">[0049] The device service description <part-num-ref name="device service description">38</part-num-ref>
+ may be a file or web browser page written in XML format. The XML formatted file or page includes information about the device <part-num-ref name="device">24</part-num-ref>
+ and the services that the device <part-num-ref name="device">24</part-num-ref>
+ provides.    </p>
+    <p id="p-66" num="66">In an exemplary embodiment, the device service description <part-num-ref name="device service description">38</part-num-ref>
+ includes context information for the device <part-num-ref name="device">24.</part-num-ref>
+ The context information may include, but is not limited to, a geographic location of the device <part-num-ref name="device">24.</part-num-ref>
+ The context information provides additional information relative to the services provided by the device <part-num-ref name="device">24.</part-num-ref>
+ For example, if the device <part-num-ref name="device">24</part-num-ref>
+ is a camera, the camera may store context information for each photograph taken by the camera that includes, but is not limited to, a date the photograph is taken, a time the photograph is taken, a location at which the photograph is taken, a subject matter of the photograph, a temperature at the photograph location, a photographer, etc. The camera may store context information describing the context information stored for each picture and/or may store context information related to the camera itself. Context information related to the camera itself may be the geographic location of the camera, a status of the camera battery, a total memory size of a camera memory, a remaining memory size of the camera memory, etc. Context information is also saved relative to each photograph which is an item stored at the camera.    </p>
+    <p id="p-67" num="67">[0050] The control point device <part-num-ref name="control point device">26</part-num-ref>
+ may send a request to the camera requesting the device service description <part-num-ref name="device service description">38</part-num-ref>
+ that includes the context <boundary-data type="header">-16-</boundary-data>
+      <boundary-data type="header">011.1211983.1</boundary-data>
+      <page-break num="18"/>
+      <boundary-data type="header">Atty. Dkt. No.: 037145-4901 (NC 44467)</boundary-data>
+information related to the camera itself. In this example, the response includes the context information in the device service description <part-num-ref name="device service description">38.</part-num-ref>
+ Based on this information, the control point device <part-num-ref name="control point device">26</part-num-ref>
+ may send a request to the camera to send the control point device <part-num-ref name="control point device">26</part-num-ref>
+ all of the pictures taken on August <part-num-ref name="pictures taken on August">6,</part-num-ref>
+ <part-num-ref name="pictures taken on August 6,">2004.</part-num-ref>
+ The control point device <part-num-ref name="control point device">26</part-num-ref>
+ "discovered<confidence value="5">"</confidence>
+ that the camera saved the date information associated with each photograph, and thus, could request the service of getting the photographs based on the date context information.    </p>
+    <p id="p-68" num="68">In this example, the request from the control point device <part-num-ref name="control point device">26</part-num-ref>
+ includes the context information and the device <part-num-ref name="device">24</part-num-ref>
+ performs the service based on the context information included with the request. In an alternative embodiment, the device <part-num-ref name="device">24</part-num-ref>
+ that is a camera may receive a request from the control point device <part-num-ref name="control point device">26</part-num-ref>
+ that does not include context information. For example, the control point device <part-num-ref name="control point device">26</part-num-ref>
+ sends a request for a list of photographs at the devi<confidence value="8">c</confidence>
+e <part-num-ref name="device">24.</part-num-ref>
+    </p>
+    <p id="p-69" num="69">The device 24 responds with the list of photographs at the device <part-num-ref name="device">24</part-num-ref>
+ with the list of pictures including the context information associated with each photograph. In this example, the response includes the context information with the response.    </p>
+    <p id="p-70" num="70">[0051] With reference to FIG. 3, the control point device <part-num-ref name="control point device">26</part-num-ref>
+ comprises a display <part-num-ref name="display">40,</part-num-ref>
+ a communication interface <part-num-ref name="communication interface">42,</part-num-ref>
+ and a processor <part-num-ref name="processor">44.</part-num-ref>
+    </p>
+    <p id="p-71" num="71">Different and additional components may be incorporated into the device <part-num-ref name="device">26.</part-num-ref>
+    </p>
+    <p id="p-72" num="72">The display 40 of the device <part-num-ref name="device">26</part-num-ref>
+ is optional. The display <part-num-ref name="display">40</part-num-ref>
+ presents information to a user. The display <part-num-ref name="display">40</part-num-ref>
+ may be a TFT display, an LED display, an LCD, or any of a variety of different displays known to those skilled in the art.    </p>
+    <p id="p-73" num="73">[0052] The communication interface <part-num-ref name="communication interface">42</part-num-ref>
+ provides an interface for receiving and transmitting calls, messages, and any other information communicable between devices. Communications between the control point device <part-num-ref name="control point device">26</part-num-ref>
+ and other control point devices <part-num-ref name="and other control point devices">26,</part-num-ref>
+ and/or to devices <part-num-ref name="and other control point devices 26, and/or to devices">24</part-num-ref>
+ may be through one or more of the following connection methods, without limitation:    </p>
+    <p id="p-74" num="74">an infrared communications link, a wireless communications link, a cellular <boundary-data type="header">-17-</boundary-data>
+      <boundary-data type="header">011.1211983.1</boundary-data>
+      <page-break num="19"/>
+      <boundary-data type="header">Atty. Dkt. No.: 037145-4901 (NC 44467)</boundary-data>
+network link, a link established according to TCP/IP, etc. Transferring content to and from the control point device <part-num-ref name="control point device">26</part-num-ref>
+ may be through one or more of these connection methods. The control point device <part-num-ref name="control point device">26</part-num-ref>
+ may communicate using various transmission technologies including, but not limited to, CDMA, GSM, UMTS, TDMA, TCP/IP, Bluetooth, IrDA, RFID, etc. The control point device <part-num-ref name="control point device">26</part-num-ref>
+ may communicate using various media including, but not limited to, radio, infrared, laser, optical, range reduced Bluetooth, cable connection, etc.    </p>
+    <p id="p-75" num="75">[0053] The processor <part-num-ref name="processor">44</part-num-ref>
+ executes instructions that cause the device <part-num-ref name="device">26</part-num-ref>
+ to behave in a predetermined manner. The instructions may be written using one or more programming languages, scripting languages, assembly languages, etc. Additionally, the instructions may be carried out by a special purpose computer, logic circuits, or hardware circuits. Thus, the processor <part-num-ref name="processor">44</part-num-ref>
+ may be implemented in hardware, firmware, software, or any combination of these methods. The processor <part-num-ref name="processor">44</part-num-ref>
+ executes an instruction, meaning that it performs the operations called for by that instruction. The processor <part-num-ref name="processor">44</part-num-ref>
+ couples to the communication interface <part-num-ref name="communication interface">42.</part-num-ref>
+    </p>
+    <p id="p-76" num="76">[0054] With reference to FIG. 4, an exemplary message sequence between the control point<confidence value="5">-</confidence>
+device <part-num-ref name="control point-device">26</part-num-ref>
+ and the device <part-num-ref name="device">24</part-num-ref>
+ is shown.    </p>
+    <p id="p-77" num="77">The communication interface 42 of the control point device <part-num-ref name="control point device">26</part-num-ref>
+ sends an HTTP Get Request <part-num-ref name="HTTP Get Request">50</part-num-ref>
+ to the device <part-num-ref name="device">24</part-num-ref>
+ to retrieve the device service description <part-num-ref name="device service description">38</part-num-ref>
+ from the device <part-num-ref name="device">24.</part-num-ref>
+ The communication interface <part-num-ref name="communication interface">32</part-num-ref>
+ of the device <part-num-ref name="device">24</part-num-ref>
+ receives the HTTP Get Request <part-num-ref name="HTTP Get Request">50</part-num-ref>
+ from the control point device <part-num-ref name="control point device">26.</part-num-ref>
+ The processor <part-num-ref name="processor">34</part-num-ref>
+ of the device <part-num-ref name="device">24</part-num-ref>
+ processes the received HTTP Get Request <part-num-ref name="received HTTP Get Request">50</part-num-ref>
+ and selects the device service description <part-num-ref name="device service description">38</part-num-ref>
+ from the memory <part-num-ref name="memory">36.</part-num-ref>
+ The processor <part-num-ref name="processor">34</part-num-ref>
+ of the device <part-num-ref name="device">24</part-num-ref>
+ creates an HTTP Get Response <part-num-ref name="HTTP Get Response">52</part-num-ref>
+ that includes the device service description. The communication interface <part-num-ref name="communication interface">32</part-num-ref>
+ of the device <part-num-ref name="device">24</part-num-ref>
+ sends the HTTP Get Response <part-num-ref name="HTTP Get Response">52</part-num-ref>
+ to the control point device <part-num-ref name="control point device">26.</part-num-ref>
+ The communication interface <part-num-ref name="communication interface">42</part-num-ref>
+ of the control point <part-num-ref name="control point">26</part-num-ref>
+ receives the HTTP Get Response <part-num-ref name="HTTP Get Response">52</part-num-ref>
+ including the device service description <part-num-ref name="device service description">38.</part-num-ref>
+ The processor <part-num-ref name="processor">44</part-num-ref>
+ of the control point device <part-num-ref name="control point device">26</part-num-ref>
+ processes the received HTTP Get <boundary-data type="header">-18-</boundary-data>
+      <boundary-data type="header">011.1211983.1</boundary-data>
+      <page-break num="20"/>
+      <boundary-data type="header">Atty. Dkt. No.: 037145-4901 (NC 44467)</boundary-data>
+Response <part-num-ref name="received HTTP Get Response">52</part-num-ref>
+ and selects the device <part-num-ref name="device">24</part-num-ref>
+ to perform a service for the control point device <part-num-ref name="control point device">26</part-num-ref>
+ based, for example, on the geographic location of the device <part-num-ref name="device">24</part-num-ref>
+ included in the device service description <part-num-ref name="device service description">38</part-num-ref>
+ and/or any other the context information of the device <part-num-ref name="device">24</part-num-ref>
+ included in the device service description <part-num-ref name="device service description">38.</part-num-ref>
+    </p>
+    <p id="p-78" num="78">The message format may be, but is not limited to, SSDP or SOAP.</p>
+    <p id="p-79" num="79">[0055] FIG. 5 shows an example use case of the system <part-num-ref name="system">2.</part-num-ref>
+    </p>
+    <p id="p-80" num="80">The network 4 includes the cellular telephone <part-num-ref name="cellular telephone">6,</part-num-ref>
+ the PC <part-num-ref name="PC">12,</part-num-ref>
+ and the video camera <part-num-ref name="video camera">22.</part-num-ref>
+ The cellular telephone <part-num-ref name="cellular telephone">6</part-num-ref>
+ may be the example control point device <part-num-ref name="example control point device">26.</part-num-ref>
+ The PC <part-num-ref name="PC">12</part-num-ref>
+ and the video camera <part-num-ref name="video camera">22</part-num-ref>
+ may be example devices <part-num-ref name="may be example devices">24.</part-num-ref>
+ The cellular telephone <part-num-ref name="cellular telephone">6</part-num-ref>
+ sends an HTTP Get Request <part-num-ref name="HTTP Get Request">60</part-num-ref>
+ to the PC <part-num-ref name="PC">12</part-num-ref>
+ to retrieve a device service description from the PC <part-num-ref name="PC">12.</part-num-ref>
+ Similarly, the cellular telephone <part-num-ref name="cellular telephone">6</part-num-ref>
+ sends an HTTP Get Request <part-num-ref name="HTTP Get Request">62</part-num-ref>
+ to the video camera <part-num-ref name="video camera">22</part-num-ref>
+ to retrieve a device service description from the video camera <part-num-ref name="video camera">22.</part-num-ref>
+ The PC <part-num-ref name="PC">12</part-num-ref>
+ creates an HTTP Get Response <part-num-ref name="HTTP Get Response">64</part-num-ref>
+ that includes the device service description of the PC <part-num-ref name="PC">12</part-num-ref>
+ and sends the HTTP Get Response <part-num-ref name="HTTP Get Response">64</part-num-ref>
+ to the cellular telephone <part-num-ref name="cellular telephone">6.</part-num-ref>
+ Similarly, the video camera <part-num-ref name="video camera">22</part-num-ref>
+ creates an HTTP Get Response <part-num-ref name="HTTP Get Response">66</part-num-ref>
+ that includes the device service description of the video camera <part-num-ref name="video camera">22</part-num-ref>
+ and sends the HTTP Get Response <part-num-ref name="HTTP Get Response">66</part-num-ref>
+ to the cellular telephone <part-num-ref name="cellular telephone">6.</part-num-ref>
+    </p>
+    <p id="p-81" num="81">[0056] The cellular telephone <part-num-ref name="cellular telephone">6</part-num-ref>
+ selects the video camera <part-num-ref name="video camera">22</part-num-ref>
+ to perform service request <part-num-ref name="to perform service request">68</part-num-ref>
+ by pointing the cellular telephone <part-num-ref name="cellular telephone">6</part-num-ref>
+ at the video camera <part-num-ref name="video camera">22</part-num-ref>
+ and selecting the video camera <part-num-ref name="video camera">22</part-num-ref>
+ based on the geographic location information contained in the context information include in the device service description of the video camera <part-num-ref name="video camera">22.</part-num-ref>
+ The cellular telephone <part-num-ref name="cellular telephone">6</part-num-ref>
+ may use a local compass or other similar sensor to determine the pointing direction of the cellular telephone <part-num-ref name="cellular telephone">6</part-num-ref>
+ to the video camera <part-num-ref name="video camera">22.</part-num-ref>
+ The cellular telephone <part-num-ref name="cellular telephone">6</part-num-ref>
+ and/or the video camera <part-num-ref name="video camera">22</part-num-ref>
+ may use, for example, a global positioning system to determine the geographic location of the cellular telephone <part-num-ref name="cellular telephone">6</part-num-ref>
+ and the video camera <part-num-ref name="video camera">22</part-num-ref>
+ respectively as known to those skilled in the art.    </p>
+    <p id="p-82" num="82">[0057] Service request 68 may be a request that the video camera <part-num-ref name="video camera">22</part-num-ref>
+ send a video clip taken at a specified time on a specified date to <boundary-data type="header">-19-</boundary-data>
+      <boundary-data type="header">011.1211983.1</boundary-data>
+      <page-break num="21"/>
+      <boundary-data type="header">Atty. Dkt. No.: 037145-4901 (NC 44467)</boundary-data>
+the cellular telephone <part-num-ref name="cellular telephone">6</part-num-ref>
+ using the context information included with the service request <part-num-ref name="service request">68.</part-num-ref>
+ Similarly, the cellular telephone <part-num-ref name="cellular telephone">6</part-num-ref>
+ selects the PC <part-num-ref name="PC">12</part-num-ref>
+ to perform service request <part-num-ref name="to perform service request">70</part-num-ref>
+ by pointing the cellular telephone <part-num-ref name="cellular telephone">6</part-num-ref>
+ at the PC <part-num-ref name="PC">12</part-num-ref>
+ and selecting the PC <part-num-ref name="PC">12</part-num-ref>
+ based on the geographic location information contained in the device service description of the PC <part-num-ref name="PC">12.</part-num-ref>
+ The cellular telephone <part-num-ref name="cellular telephone">6</part-num-ref>
+ may use a local compass or other similar sensor to identify the PC <part-num-ref name="PC">12</part-num-ref>
+ using the pointing direction of the cellular telephone <part-num-ref name="cellular telephone">6.</part-num-ref>
+ Service request <part-num-ref name="cellular telephone 6. Service request">70</part-num-ref>
+ may be a request that the PC <part-num-ref name="PC">12</part-num-ref>
+ copy the specified video clip sent through the cellular telephone <part-num-ref name="cellular telephone">6.</part-num-ref>
+    </p>
+    <p id="p-83" num="83">[0058] Additionally, a control point device <part-num-ref name="control point device">26</part-num-ref>
+ may search for services based on the ability of the device <part-num-ref name="device">24</part-num-ref>
+ to support the use of context information instead of based on the context information itself. For example, a camera may attempt to locate a content directory service that supports the use of context information. The content directory service may store the content of items and/or containers and provide browsing and searching for the items and/or the containers. The camera provides context information with each photograph, and thus, requests a content directory service that also supports use of the context information.    </p>
+    <p id="p-84" num="84">[0059] Context information may include usage history that lists each user using the device and/or service, when the device and/or service is used, what control point is used to request the service, etc. Context triggered messages may be initiated from the device such as reminders or notifications based on the context information that the device stores. Thus, messages also may be initiated from the device <part-num-ref name="device">24</part-num-ref>
+ to the control point device <part-num-ref name="control point device">26.</part-num-ref>
+    </p>
+    <p id="p-85" num="85">[0060] It is understood that the invention is not confined to the particular embodiments set forth herein as illustrative, but embraces all such modifications, combinations, and permutations as come within the scope of the following claims. Thus, the description of the preferred embodiments is for purposes of illustration and not limitation.</p>
+    <boundary-data type="header">-20-</boundary-data>
+    <boundary-data type="header">011.1211983.1</boundary-data>
+  </description>
+</us-patent-application>
+

prior_art/10929878.xml

@@ -0,0 +1,416 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>10929878</doc-number>
+        <date>2004-08-30</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <heading id="h-1">TECHNIQUES FOR HEALTH MONITORING AND CONTROL OF</heading>
+    <heading id="h-2">APPLICATION SERVERS</heading>
+    <p id="p-1" num="1">Field of the Invention <boundary-data type="line-number">5          </boundary-data>
+The present invention relates to improved application server performance and availability and, more particularly, to techniques for monitoring the health of application servers.    </p>
+    <p id="p-2" num="2">Back<confidence value="8">g</confidence>
+round of the Invention <boundary-data type="line-number">10         </boundary-data>
+Application server environments are prone to a variety of problems, e.g., malfunctions, caused by the inefficient design of hosted applications. Typical problems include memory leaks, deadlocks, inconsistent state and user errors. These deficiencies have an adverse effect on the near-term performance <confidence value="222222">and/or</confidence>
+ availability of the application. In most cases, these conditions can be detected through appropriate <boundary-data type="line-number">15   </boundary-data>
+instrumentation by a human administrator, who in turn decides on the best course of action to correct the problem.    </p>
+    <p id="p-3" num="3">Each condition requires a particular corrective action that ranges from non- intrusive software reconfiguration to more drastic techniques, such as restarting the application server and its hosted applications. The latter is also known as "software <boundary-data type="line-number">20   </boundary-data>
+rejuvenation," and is commonly used to remedy many software problems, including, memory leaks and deadlocks. See, for example, Y. Huang, et al., Software Rejuvenation:    </p>
+    <p id="p-4" num="4">Analysis, Module and Applications, IEEE Twenty-Fifth International Symposium on Fault-Tolerant Computing, 381-390 (1995), the disclosure of which is incorporated herein by reference.   A  system  can selectively rejuvenate software based on <boundary-data type="line-number">25   </boundary-data>
+measurements that indicate an impending outage. See, for example, U.S. Patent Number 6,629,266 issued to R.E. Harper et al., entitled "Method and System for Transparent Symptom-Based Selective Software Rejuvenation," the disclosure of which is incorporated herein by reference. If the system is part of a cluster, the system may determine whether another cluster member can accept the workload serviced by the <boundary-data type="line-number">30   </boundary-data>
+application requiring rejuvenation. If so, the system can interact with a cluster manager to start an instance of the application on another node.    </p>
+    <boundary-data type="header">
+      <confidence value="86">YO</confidence>
+R920040396U<confidence value="5">S</confidence>
+1                       1    </boundary-data>
+    <p id="p-5" num="5">
+      <page-break num="2"/>
+In cluster systems, such as the Windows NT<confidence value="2">@</confidence>
+ cluster system, failure detection is provided for applications running unmodified on a cluster. See, for example, R.    </p>
+    <p id="p-6" num="6">Gamache et al., Windows NT Clustering Service, IEEE COMPUTER, 55-62 (October 1998), the disclosure of which is incorporated herein by reference. An application- <boundary-data type="line-number">5   </boundary-data>
+specific cluster interface layer, through which an application can be started, stopped and monitored for failures, may also be provided. For example, a monitor may include application requests that serve as probes to determine if the application is operating correctly.    </p>
+    <p id="p-7" num="7">An extensible infrastructure for detecting and recovering from failures in a cluster <boundary-data type="line-number">10   </boundary-data>
+system is described, for example, in U.S. Patent Number 5,805,785 issued to D. Dias et al., entitled  "Method  for Monitoring  and  Recovery   of Subsystems    in  a Distributed/Clustered System," the disclosure of which is incorporated herein by reference. Basic failure detection using heartbeating (e.g., noting nodes that have gone down or come up on a particular network) is augmented by user-defined monitors to <boundary-data type="line-number">15   </boundary-data>
+detect failures in specific subsystems, and user-defined recovery programs to recover from the failures detected.  A "rolling upgrade" in which upgrades in a cluster are performed in a wave so that only one node is unavailable at a time is described, for example, in E.A. Brewer et al., Lessons from Giant-Scale Services, IEEE INTERNET COMPUTING, 46-55 (July/August 2001), the disclosure of which is incorporated herein by <boundary-data type="line-number">20   </boundary-data>
+reference.    </p>
+    <p id="p-8" num="8">Despite the recent progress in application server failure detection and rejuvenation, there exists a need for improved techniques for efficiently and effectively monitoring application server environments and addressing errors occurring therein.</p>
+    <p id="p-9" num="9">
+      <boundary-data type="line-number">25   </boundary-data>
+Summary of the Invention The present invention provides techniques for improving application server performance and availability. In one aspect of the invention, a method of monitoring the health of one or more application servers comprises the following steps. One or more health classes are specified, each of the one or more health classes defining one or more <part-num-ref name="one or more health classes defining one or more">30</part-num-ref>
+   health policies for the one or more application servers. At least one of the one or more <boundary-data type="header">
+        <confidence value="86">YO</confidence>
+R920040396US1                       2      </boundary-data>
+      <page-break num="3"/>
+health policies is monitored. Violations, if any, of the one or more health policies are detected.    </p>
+    <p id="p-10" num="10">A more complete understanding of the present invention, as well as further features and advantages of the present invention, will be obtained by reference to the <boundary-data type="line-number">5   </boundary-data>
+following detailed description and drawings.    </p>
+    <p id="p-11" num="11">Brief Descri<confidence value="5">p</confidence>
+tion of the Drawin<confidence value="68">gs</confidence>
+ FIG. 1 is a diagram illustrating an exemplary system for monitoring the health of an application server according to an embodiment of the present invention;    </p>
+    <p id="p-12" num="12">
+      <boundary-data type="line-number">10         </boundary-data>
+FIG. 2 is a diagram illustrating an exemplary application server environment according to an embodiment of the present invention;    </p>
+    <p id="p-13" num="13">FIG. 3 is a diagram illustrating an exemplary computer system comprising application servers and clusters according to an embodiment of the present invention;</p>
+    <p id="p-14" num="14">FIG. 4 is a diagram illustrating an exemplary system for defining a health policy <boundary-data type="line-number">15   </boundary-data>
+according to an embodiment of the present invention;    </p>
+    <p id="p-15" num="15">FIG. 5 is a diagram illustrating an exemplary health class according to an embodiment of the present invention;</p>
+    <p id="p-16" num="16">FIG. 6 is a diagram illustrating an exemplary detection only reaction according to an embodiment of the present invention;</p>
+    <p id="p-17" num="17">
+      <boundary-data type="line-number">20         </boundary-data>
+FIG. 7 is a diagram illustrating an exemplary supervised reaction according to an embodiment of the present invention;    </p>
+    <p id="p-18" num="18">FIG. 8 is a diagram illustrating an exemplary automatic reaction according to an embodiment of the present invention;</p>
+    <p id="p-19" num="19">FIG. 9 is a diagram illustrating an exemplary health subsystem configuration <boundary-data type="line-number">25   </boundary-data>
+according to an embodiment of the present invention;    </p>
+    <p id="p-20" num="20">FIG. 10 is a diagram illustrating an exemplary health subsystem runtime operation according to an embodiment of the present invention;</p>
+    <p id="p-21" num="21">FIG. 11 is a diagram illustrating an exemplary health sensor operation according to an embodiment of the present invention; and <boundary-data type="line-number">30         </boundary-data>
+FIG. 12 is a diagram illustrating an exemplary system for monitoring the health of one or more application servers according to an embodiment of the present invention.    </p>
+    <boundary-data type="header">
+      <confidence value="86">YO</confidence>
+R920040396US1                      3    </boundary-data>
+    <p id="p-22" num="22">
+      <page-break num="4"/>
+Detailed Descri<confidence value="5">p</confidence>
+tion of Preferred Embodiments FIG. 1 is a diagram illustrating an exemplary system <part-num-ref name="exemplary system">100</part-num-ref>
+ for monitoring the <boundary-data type="line-number">5   </boundary-data>
+health of an application server. The term "health," as used herein denotes the overall well-being and performance of the system and is defined by one or more health classes that are applied to servers of the system. System <part-num-ref name="system. System">100</part-num-ref>
+ comprises manager <part-num-ref name="comprises manager">102,</part-num-ref>
+ policy database <part-num-ref name="comprises manager 102, policy database">104,</part-num-ref>
+ health controller <part-num-ref name="comprises manager 102, policy database 104, health controller">106,</part-num-ref>
+ reaction manager <part-num-ref name="comprises manager 102, policy database 104, health controller 106, reaction manager">108,</part-num-ref>
+ health sensors <part-num-ref name="comprises manager 102, policy database 104, health controller 106, reaction manager 108, health sensors">110,</part-num-ref>
+ user applications <part-num-ref name="comprises manager 102, policy database 104, health controller 106, reaction manager 108, health sensors 110, user applications">112,</part-num-ref>
+ <part-num-ref name="comprises manager 102, policy database 104, health controller 106, reaction manager 108, health sensors 110, user applications 112,">114</part-num-ref>
+ and <part-num-ref name="and">116</part-num-ref>
+ and system management agent <part-num-ref name="and system management agent">118.</part-num-ref>
+ Health sensors <part-num-ref name="and system management agent 118. Health sensors">110,</part-num-ref>
+ <boundary-data type="line-number">10   </boundary-data>
+user applications <part-num-ref name="and system management agent 118. Health sensors 110, user applications">112,</part-num-ref>
+ <part-num-ref name="and system management agent 118. Health sensors 110, user applications 112,">114</part-num-ref>
+ and <part-num-ref name="and">116</part-num-ref>
+ and system management agent <part-num-ref name="and system management agent">118</part-num-ref>
+ comprise an application server of system <part-num-ref name="application server of system">100.</part-num-ref>
+ In an exemplary embodiment, system <part-num-ref name="exemplary embodiment, system">100</part-num-ref>
+ comprises one or more application servers, each of which host J2EE applications.    </p>
+    <p id="p-23" num="23">According to an exemplary embodiment of the present invention, system <part-num-ref name="present invention, system">100</part-num-ref>
+ is configured to implement a methodology for monitoring the health of an application <boundary-data type="line-number">15   </boundary-data>
+server, which may include detecting and/or reacting to specific health problems. Namely, in step <part-num-ref name="application server, which may include detecting and/or reacting to specific health problems. Namely, in step">1,</part-num-ref>
+ manager <part-num-ref name="application server, which may include detecting and/or reacting to specific health problems. Namely, in step 1, manager">102</part-num-ref>
+ initially specifies a health class. As will be described in detail below, a given health class can define one or more health monitoring policies for the application server, using a rule-based description. In step <part-num-ref name="rule-based description. In step">2,</part-num-ref>
+ the configuration of the specified health class is stored, e.g., in policy database <part-num-ref name="in policy database">104.</part-num-ref>
+    </p>
+    <p id="p-24" num="24">
+      <boundary-data type="line-number">20          </boundary-data>
+In step 3, optional health sensors are configured to monitor the health of an application server. Namely, the health policies specify what attributes of the operating environment will be monitored, the particular boundary health conditions that will trigger a policy violation, e.g., health exception, and/or the operations that are to be performed to correct the condition that triggered the violation. Therefore, in step <part-num-ref name="violation. Therefore, in step">4,</part-num-ref>
+ the health policies <boundary-data type="line-number">25   </boundary-data>
+are monitored. Monitoring the health policies involves first reading the health policies, e.g., from policy database <part-num-ref name="from policy database">104,</part-num-ref>
+ as in step 5a, and then, if a violation of a health policy is detected, initiate a corrective action, as in step <confidence value="5">5</confidence>
+b. An exemplary corrective action may include, but is not limited to, executing a restart of the application server, as in step <part-num-ref name="application server, as in step">6.</part-num-ref>
+    </p>
+    <p id="p-25" num="25">A condition that will trigger a health exception (a triggering condition), e.g., a <boundary-data type="line-number">30   </boundary-data>
+health policy violation, for example, may be a generalized attribute-value assertion on data observed from health sensors <part-num-ref name="generalized attribute-value assertion on data observed from health sensors">110,</part-num-ref>
+ e.g., sensor data. Namely, the triggering <boundary-data type="header">
+        <confidence value="86">YO</confidence>
+R920040396US1                        4      </boundary-data>
+      <page-break num="5"/>
+condition can be a simple equality clause, or, alter<confidence value="8">n</confidence>
+atively, a complex processing operation on multiple pieces of sensor data (for example, in an exemplary embodiment an error condition is detected when about ten percent threshold crossings are observed over about a <part-num-ref name="">60</part-num-ref>
+ minute period). Processing sensor data, e.g., against policy database <part-num-ref name="against policy database">104,</part-num-ref>
+ may <boundary-data type="line-number">5   </boundary-data>
+include, but is not limited to, applying statistical functions, applying assertions on the ordering (partial or total) of system events and scoping (including or excluding parts of the system under observation).    </p>
+    <p id="p-26" num="26">The health policy for a particular system is expressed in a policy specification language, and is then passed to a health controller, e.g., health controller <part-num-ref name="health controller">106.</part-num-ref>
+ Health <boundary-data type="line-number">10   </boundary-data>
+controller <part-num-ref name="health controller 106. Health controller">106</part-num-ref>
+ is responsible for implementing that health policy during normal operation of the system. Health controller <part-num-ref name="system. Health controller">106</part-num-ref>
+ stores the health policy in policy database <part-num-ref name="health policy in policy database">104</part-num-ref>
+ (a local repository) and configures the appropriate health sensors <part-num-ref name="appropriate health sensors">110</part-num-ref>
+ within the managed system to obtain the relevant system data. The identification of what health sensors <part-num-ref name="identification of what health sensors">110</part-num-ref>
+ to configure, and with what parameters, can be expressed in the health policy itself, or <boundary-data type="line-number">15   </boundary-data>
+alternatively, can be derived automatically from the health policy specification after a compilation process.    </p>
+    <p id="p-27" num="27">During system operation, health controller 106 periodically collects data from health sensors <part-num-ref name="periodically collects data from health sensors">110,</part-num-ref>
+ performs the required aggregations and statistical processing of the data and verifies the data against the stored health policies, e.g., in policy database <part-num-ref name="in policy database">104.</part-num-ref>
+    </p>
+    <p id="p-28" num="28">
+      <boundary-data type="line-number">20   </boundary-data>
+If a health violation is detected, a reaction to the violation may be issued. The reaction will reconfigure and tune the system <part-num-ref name="system">100</part-num-ref>
+ in such a way, e.g., that service is maintained.    </p>
+    <p id="p-29" num="29">FIG. 2 is a diagram illustrating an exemplary application server environment <part-num-ref name="exemplary application server environment">200.</part-num-ref>
+    </p>
+    <p id="p-30" num="30">Application server environment 200 comprises nodes <part-num-ref name="comprises nodes">202,</part-num-ref>
+ <part-num-ref name="comprises nodes 202,">204</part-num-ref>
+ and <part-num-ref name="and">206</part-num-ref>
+ connected via network interconnect <part-num-ref name="connected via network interconnect">208.</part-num-ref>
+ According to an exemplary embodiment of the present <boundary-data type="line-number">25   </boundary-data>
+invention, each of nodes <part-num-ref name="present invention, each of nodes">202,</part-num-ref>
+ <part-num-ref name="present invention, each of nodes 202,">204</part-num-ref>
+ and <part-num-ref name="and">206</part-num-ref>
+ contains a copy of the application server software according to the type of function that the node performs.    </p>
+    <p id="p-31" num="31">Application server environment 200 comprises the following exemplary types of nodes. Node <part-num-ref name="following exemplary types of nodes. Node">202</part-num-ref>
+ comprises an administrative node responsible for performing management functionality for the rest of the application server environment. Nodes <part-num-ref name="application server environment. Nodes">204</part-num-ref>
+ <boundary-data type="line-number">30   </boundary-data>
+and <part-num-ref name="and">206</part-num-ref>
+ comprise application server nodes. According to the teachings presented herein, application server environment <part-num-ref name="teachings presented herein, application server environment">200</part-num-ref>
+ comprises a plurality of application server nodes.    </p>
+    <boundary-data type="header">
+      <confidence value="86">YO</confidence>
+R920040396US<confidence value="4">1</confidence>
+                        <confidence value="8">5</confidence>
+    </boundary-data>
+    <p id="p-32" num="32">
+      <page-break num="6"/>
+Each application server node can host one or more application server instances. In turn, each application server instance can host zero or more enterprise application modules (also referred to herein as "applications").    </p>
+    <p id="p-33" num="33">FIG. 3 is a diagram illustrating exemplary computer system <part-num-ref name="diagram illustrating exemplary computer system">300</part-num-ref>
+ comprising <boundary-data type="line-number">5   </boundary-data>
+application servers and clusters. Namely, computer system <part-num-ref name="comprising application servers and clusters. Namely, computer system">300</part-num-ref>
+ comprises application server nodes <part-num-ref name="comprises application server nodes">302</part-num-ref>
+ and <part-num-ref name="and">304.</part-num-ref>
+ Application server node <part-num-ref name="and 304. Application server node">302</part-num-ref>
+ hosts application server instances <part-num-ref name="hosts application server instances">306</part-num-ref>
+ and <part-num-ref name="and">308.</part-num-ref>
+ Application server instance <part-num-ref name="and 308. Application server instance">306</part-num-ref>
+ hosts applications <part-num-ref name="hosts applications">312</part-num-ref>
+ and <part-num-ref name="and">314.</part-num-ref>
+    </p>
+    <p id="p-34" num="34">Application server instance 308 hosts applications <part-num-ref name="hosts applications">316</part-num-ref>
+ and <part-num-ref name="and">318.</part-num-ref>
+ Application server node <part-num-ref name="and 318. Application server node">304</part-num-ref>
+ hosts application server instance <part-num-ref name="hosts application server instance">310.</part-num-ref>
+ Application server instance <part-num-ref name="hosts application server instance 310. Application server instance">310</part-num-ref>
+ hosts <boundary-data type="line-number">10   </boundary-data>
+applications <part-num-ref name="hosts applications">320</part-num-ref>
+ and <part-num-ref name="and">322.</part-num-ref>
+ Application server instances <part-num-ref name="and 322. Application server instances">308</part-num-ref>
+ and <part-num-ref name="and">310</part-num-ref>
+ form cluster <part-num-ref name="form cluster">324.</part-num-ref>
+    </p>
+    <p id="p-35" num="35">The environment of computer system 300 allows the following groupings of application server instances. "Singleton" application server instances, e.g., application server instance <part-num-ref name="application server instance">306,</part-num-ref>
+ run independently of other application server instances and contain a single copy of an application. "Clustered" application server instances ("clusters"), e.g., <boundary-data type="line-number">15   </boundary-data>
+application server instances <part-num-ref name="application server instances">308</part-num-ref>
+ and <part-num-ref name="and">310,</part-num-ref>
+ run multiple copies of an application server instance on one or more nodes. Clusters can be further distinguished into static clusters and dynamic clusters. Specifically, the number of running application server instances in a dynamic cluster is determined at runtime and is based on an observed demand for an application, whereas with static clusters the number of servers is set at configuration.    </p>
+    <p id="p-36" num="36">
+      <boundary-data type="line-number">20          </boundary-data>
+The health controller, e.g., health controller <part-num-ref name="health controller">106,</part-num-ref>
+ as described in conjunction with the description of FIG. 1 above, is responsible for monitoring the health status of application server instances. There are two aspects of a health controller operation, namely, a configuration phase and a runtime phase. In the configuration phase, a health policy is defined. FIG. 4 is a diagram illustrating an exemplary system <part-num-ref name="exemplary system">400</part-num-ref>
+ for defining a <boundary-data type="line-number">25   </boundary-data>
+health policy.    </p>
+    <p id="p-37" num="37">Namely, as shown in FIG. 4, administrator 402, using administrator console 404, defines a number of health classes <part-num-ref name="number of health classes">406.</part-num-ref>
+ Each health class <part-num-ref name="number of health classes 406. Each health class">406</part-num-ref>
+ contains a set of targets (e.g., members of one or more health classes) and a health policy to be applied to the targets. The targets and the health policies can be modified dynamically. The health <part-num-ref name="health">30</part-num-ref>
+   policy includes one or more health conditions to be monitored, the corrective action to be <boundary-data type="header">
+        <confidence value="86">YO</confidence>
+R920040396US1                        6      </boundary-data>
+      <page-break num="7"/>
+taken and the reaction mode. This information becomes part of policy database <part-num-ref name="reaction mode. This information becomes part of policy database">104</part-num-ref>
+ and is stored into health controller <part-num-ref name="and is stored into health controller">106,</part-num-ref>
+ which in turn monitors the respective health classes.    </p>
+    <p id="p-38" num="38">FIG. 5 is a diagram illustrating an exemplary health class. Namely, health class <part-num-ref name="exemplary health class. Namely, health class">406</part-num-ref>
+ is shown to contain targets <part-num-ref name="is shown to contain targets">502,</part-num-ref>
+ <part-num-ref name="is shown to contain targets 502,">504</part-num-ref>
+ and <part-num-ref name="and">506</part-num-ref>
+ and health policies <part-num-ref name="and health policies">508,</part-num-ref>
+ <part-num-ref name="and health policies 508,">510</part-num-ref>
+ and <part-num-ref name="and">512,</part-num-ref>
+ <boundary-data type="line-number">5   </boundary-data>
+e.g., representing a health condition, a reaction mode and a reaction, respectively. The target of a health class, e.g., targets <part-num-ref name="targets">502,</part-num-ref>
+ <part-num-ref name="targets 502,">504</part-num-ref>
+ and <part-num-ref name="and">506,</part-num-ref>
+ can include one or more individual application servers (S), clusters or dynamic clusters (DC). When a cluster or dynamic cluster is specified as a target, the health class automatically applies to all application servers that are members of that cluster or dynamic cluster, including application servers <boundary-data type="line-number">10   </boundary-data>
+added to that cluster or dynamic cluster after the health class is created. The target of a health class can include all the nodes in the administrative domain. In the instance wherein the target of a health class includes all the nodes in the administrative domain, the health class would only have a single target and the health class would automatically apply to any application servers added after creation of the health class.    </p>
+    <p id="p-39" num="39">
+      <boundary-data type="line-number">15          </boundary-data>
+A health condition is an erroneous state in hardware and/or software that indicates a present or anticipated malfunction. Examples of health conditions include, but are not limited to, very high memory usage or high percentages of requests encountering internal server errors. In conventional systems, during the course of operation of application server environments, the operator would monitor the system for such conditions, and <boundary-data type="line-number">20   </boundary-data>
+when detected take corrective action. The present techniques provide a fully automated way of reacting to such problems.    </p>
+    <p id="p-40" num="40">According to an exemplary embodiment of the present invention, one or more of the following health conditions are monitored, which include, but are not limited to, the age of an application server (e.g., the time since startup), the work performed (e.g., the <boundary-data type="line-number">25   </boundary-data>
+number of served requests), a memory usage pattern indicating an impending resource problem and unusually long response times of requests indicating internal server errors (such as deadlocks).    </p>
+    <p id="p-41" num="41">A health class monitors exactly one health condition, e.g., health condition <part-num-ref name="health condition">508,</part-num-ref>
+ the health condition itself being tied to one or more low-level health parameters, <boundary-data type="line-number">30   </boundary-data>
+including, but not limited to, memory heap size and request response time. For detection purposes, the health class specifies the desired boundaries for these low-level health <boundary-data type="header">
+        <confidence value="86">YO</confidence>
+R920040396US1                        7      </boundary-data>
+      <page-break num="8"/>
+parameters. The low-level health parameters are evaluated periodically and, if a violation is detected, the health condition is triggered. The health controller then takes the corrective action specified by the health class.    </p>
+    <p id="p-42" num="42">The reaction mode, e.g., reaction mode <part-num-ref name="reaction mode">510,</part-num-ref>
+ defines how the system reacts in the <boundary-data type="line-number">5   </boundary-data>
+presence of a detected health condition, e.g., health condition <part-num-ref name="health condition">508.</part-num-ref>
+ In this exemplary embodiment, the reaction mode is used to execute the corrective action in one of three possible ways: <part-num-ref name="corrective action in one of three possible ways:">(1)</part-num-ref>
+ detection only, wherein a diagnostic message is produced upon detection of the condition, <part-num-ref name="condition,">(2)</part-num-ref>
+ supervised reaction, wherein a message is sent to the administrator with a suggestion of a corrective action or <part-num-ref name="corrective action or">(3)</part-num-ref>
+ automatic reaction, wherein a <boundary-data type="line-number">10   </boundary-data>
+reaction to the condition is scheduled for execution immediately.    </p>
+    <p id="p-43" num="43">FIG. 6 is a diagram illustrating an exemplary detection only reaction. In the detection only reaction <part-num-ref name="detection only reaction">600</part-num-ref>
+ shown in Fig. 6, one or more health conditions <part-num-ref name="shown in Fig. 6, one or more health conditions">602</part-num-ref>
+ are detected, collected by health controller <part-num-ref name="are detected, collected by health controller">106</part-num-ref>
+ and then a log entry <part-num-ref name="log entry">604</part-num-ref>
+ is made.    </p>
+    <p id="p-44" num="44">FIG. 7 is a diagram  illustrating an exemplary supervised reaction.  In the <boundary-data type="line-number">15   </boundary-data>
+supervised reaction <part-num-ref name="supervised reaction">700</part-num-ref>
+ shown in FIG. 7, one or more health conditions <part-num-ref name="shown in FIG. 7, one or more health conditions">602</part-num-ref>
+ are detected and then collected by health controller <part-num-ref name="are detected and then collected by health controller">106</part-num-ref>
+ which submits a request to an activity engine, e.g., activity engine <part-num-ref name="activity engine">702.</part-num-ref>
+ Activity engine <part-num-ref name="activity engine 702. Activity engine">702</part-num-ref>
+ is a component which receives actionable messages from within the application server environment that require the attention of a human administrator and provides the option of acknowledging the reception and/or <boundary-data type="line-number">20   </boundary-data>
+approving corrective action(s). Activity engine <part-num-ref name="reception and/or approving corrective action(s). Activity engine">702</part-num-ref>
+ then makes a request <part-num-ref name="request">704</part-num-ref>
+ for confirmation of a reaction, e.g., request user to approve corrective action. If the reaction is confirmed, then execution of the reaction <part-num-ref name="reaction">706</part-num-ref>
+ is conducted. Alternatively, if the reaction is not confirmed, then a log entry <part-num-ref name="log entry">604,</part-num-ref>
+ as in the detection only reaction, above, is made.    </p>
+    <p id="p-45" num="45">
+      <boundary-data type="line-number">25          </boundary-data>
+According to the exemplary embodiment shown in FIG. 7, reactions are limited to restarting the application server on which the erroneous condition was observed. This process is also known as software rejuvenation. The system architecture however, is not limited solely to rejuvenation actions, but can be used to signal any kind of automatic or supervised corrective action.    </p>
+    <p id="p-46" num="46">
+      <boundary-data type="line-number">30          </boundary-data>
+FIG. 8 is a diagram illustrating an exemplary automatic reaction. In the automatic reaction <part-num-ref name="automatic reaction">800</part-num-ref>
+ shown in FIG. 8, one or more health conditions <part-num-ref name="shown in FIG. 8, one or more health conditions">602</part-num-ref>
+ are detected and then <boundary-data type="header">
+        <confidence value="86">YO</confidence>
+R920040396US1                        8      </boundary-data>
+      <page-break num="9"/>
+collected by health controller <part-num-ref name="are detected and then collected by health controller">106,</part-num-ref>
+ as in the detection only and the supervised reactions, described above. An automatic reaction <part-num-ref name="automatic reaction">802</part-num-ref>
+ is then initiated.    </p>
+    <p id="p-47" num="47">Regarding the runtime phase of a health controller operation, the health controller, e.g., health controller <part-num-ref name="health controller">106</part-num-ref>
+ of FIG. 4, described above, reads each defined health class, <boundary-data type="line-number">5   </boundary-data>
+e.g., health class <part-num-ref name="health class">406</part-num-ref>
+ of FIG. 5, described above, and configures a health subsystem for every target, e.g., targets <part-num-ref name="targets">502,</part-num-ref>
+ <part-num-ref name="targets 502,">504</part-num-ref>
+ and <part-num-ref name="and">506</part-num-ref>
+ of FIG. 5, above, of the health class. The health subsystem is a high-level construct responsible for monitoring the health condition specified in the health class.    </p>
+    <p id="p-48" num="48">The health subsystem hides the low-level details of health data collection by <boundary-data type="line-number">10   </boundary-data>
+presenting a simple application program interface (API) to the health controller to determine if the health condition has been violated for the health class. In turn, the health subsystem configures one or more low-level sensors to obtain the necessary health data.    </p>
+    <p id="p-49" num="49">FIG. 9 is a diagram illustrating an exemplary health subsystem configuration. In FIG. 9, health subsystem <part-num-ref name="exemplary health subsystem configuration. In FIG. 9, health subsystem">900</part-num-ref>
+ is configured to implement health class A <part-num-ref name="">902</part-num-ref>
+ and health <boundary-data type="line-number">15   </boundary-data>
+class B <part-num-ref name="and health class B">904.</part-num-ref>
+    </p>
+    <p id="p-50" num="50">For the targets of health class A <part-num-ref name="">902,</part-num-ref>
+ health controller <part-num-ref name="902, health controller">106</part-num-ref>
+ instantiates age subsystem <part-num-ref name="instantiates age subsystem">906,</part-num-ref>
+ which in turn configures age sensor <part-num-ref name="instantiates age subsystem 906, which in turn configures age sensor">910</part-num-ref>
+ with the desired boundary (e.g., the maximum allowed age). Similarly, every target of health class B <part-num-ref name="maximum allowed age). Similarly, every target of health class B">904</part-num-ref>
+ requires the configuration of memory subsystem <part-num-ref name="configuration of memory subsystem">908</part-num-ref>
+ to detect erroneous memory usage patterns.    </p>
+    <p id="p-51" num="51">
+      <boundary-data type="line-number">20   </boundary-data>
+Memory subsystem 908 in turn initializes memory heap size sensor <part-num-ref name="in turn initializes memory heap size sensor">912,</part-num-ref>
+ heap growth rate sensor <part-num-ref name="in turn initializes memory heap size sensor 912, heap growth rate sensor">914</part-num-ref>
+ and memory leak sensor <part-num-ref name="and memory leak sensor">916.</part-num-ref>
+ The sensors continuously compute these quantities, e.g., memory heap size, heap growth rate and memory leak, using instrumentation available through the operating system or the application server environment. If the configured boundary conditions for any one of sensors <part-num-ref name="configured boundary conditions for any one of sensors">912,</part-num-ref>
+ <part-num-ref name="configured boundary conditions for any one of sensors 912,">914</part-num-ref>
+ or <boundary-data type="line-number">25   </boundary-data>
+      <part-num-ref name="or">916</part-num-ref>
+ are violated, memory subsystem <part-num-ref name="are violated, memory subsystem">908</part-num-ref>
+ will raise a flag, which will subsequently trigger the reaction specified in the health class (e.g., an application server restart).    </p>
+    <p id="p-52" num="52">FIG. 10 is a diagram illustrating exemplary health subsystem runtime operation <part-num-ref name="diagram illustrating exemplary health subsystem runtime operation">1000.</part-num-ref>
+ Specifically, health subsystem <part-num-ref name="diagram illustrating exemplary health subsystem runtime operation 1000. Specifically, health subsystem">1002</part-num-ref>
+ periodically checks the health sensors, e.g., sensors <part-num-ref name="sensors">1004</part-num-ref>
+ and <part-num-ref name="and">1006,</part-num-ref>
+ for violations of boundary health conditions. For conditions <boundary-data type="line-number">30   </boundary-data>
+involving single sensors, the subsystem can check for a violation by performing an assertion on the triggered condition (isTriggered) on its health sensors. For conditions <boundary-data type="header">
+        <confidence value="86">YO</confidence>
+R920040396US1                      9      </boundary-data>
+      <page-break num="10"/>
+involving multiple sensors, the subsystem may require a multitude of health sensors to be in the triggered state for a violation to occur, or it may poll sensors for data to determine if the condition is violated.    </p>
+    <p id="p-53" num="53">Once configured, each health sensor operates independently, and periodically <boundary-data type="line-number">5   </boundary-data>
+collects health-related data from the target using communication mechanisms specific to application server environment <part-num-ref name="target using communication mechanisms specific to application server environment">1008.</part-num-ref>
+ The health-related data obtained is checked with respect to the boundary parameters specified in the health class.    </p>
+    <p id="p-54" num="54">Exemplary health sensor boundary health conditions include, but are not limited to, maximum allowed server age (e.g., up to about <part-num-ref name="up to about">48</part-num-ref>
+ hours), maximum work performed <boundary-data type="line-number">10   </boundary-data>
+(e.g., up to about 100,000 requests), maximum heap size (e.g., up to about <part-num-ref name="up to about">200</part-num-ref>
+ megabytes) and maximum response time allowed (e.g., up to about five seconds for about <part-num-ref name="up to about five seconds for about">95</part-num-ref>
+ percent of incoming requests).    </p>
+    <p id="p-55" num="55">FIG. 11 is a diagram illustrating an exemplary health sensor operation. In FIG.</p>
+    <p id="p-56" num="56">11, boundary health conditions 1104 are checked by health sensors <part-num-ref name="are checked by health sensors">1102.</part-num-ref>
+ If a violation <boundary-data type="line-number">15   </boundary-data>
+of a boundary health condition is detected, a flag (trigger) <part-num-ref name="flag (trigger)">1106</part-num-ref>
+ is raised within the sensor and low-level health data <part-num-ref name="sensor and low-level health data">1108</part-num-ref>
+ is collected. Alternatively, if no violation of a boundary health condition is detected, then only low-level health data <part-num-ref name="boundary health condition is detected, then only low-level health data">1108</part-num-ref>
+ is collected.    </p>
+    <p id="p-57" num="57">The health controller periodically polls its subsystems, which in turn check the sensors. If the subsystem for a server is determined to be unhealthy, the health monitor <boundary-data type="line-number">20   </boundary-data>
+initiates a reaction. This process is performed for all configured subsystems and sensors.    </p>
+    <p id="p-58" num="58">Of particular importance are the runtime characteristics of the health controller.</p>
+    <p id="p-59" num="59">In a live application server environment, configurations may constantly change. For example, nodes may be added and/or removed, application server instances may be installed and/or removed from nodes and cluster membership may change.</p>
+    <p id="p-60" num="60">
+      <boundary-data type="line-number">25         </boundary-data>
+A component within the health controller, e.g., a topology manager, can be employed to observe the application server environment by <confidence value="5">'</confidence>
+listening' to configuration events from selected components and reacting appropriately. For example, when a new health class is created, the health controller creates a number of subsystems and sensors to obtain data from the class targets. When a health class is deleted, the corresponding <boundary-data type="line-number">30   </boundary-data>
+health subsystems are destroyed by the health controller and observation of the health parameters from the corresponding targets stops. When a new target is added to a health <boundary-data type="header">
+        <confidence value="86">YO</confidence>
+R920040396US1                      10      </boundary-data>
+      <page-break num="11"/>
+class, the appropriate health subsystem is configured for that server and added to the list of health subsystems under observation. When a target is removed from a health class, the corresponding health subsystem is destroyed. When the membership of a target changes (e.g., as is applicable to cluster systems), the appropriate health subsystems are <boundary-data type="line-number">5   </boundary-data>
+added and/or removed.    </p>
+    <p id="p-61" num="61">Because a target of a health class can be a server or a group of servers, it is possible to create multiple health classes on a server at different levels that monitor the same health conditions. For example, one can create a health class A that monitors the age of a cluster, with an instruction to restart if the age exceeds some value Y. Another <boundary-data type="line-number">10   </boundary-data>
+class B may be created that monitors the age of a server that is a member of the cluster in health class A, with an instruction to restart if the age exceeds some other value X. In this case, the health classes conflict. The health controller detects such conflicts and uses a precedence rule to determine which health class to apply. According to the teachings herein, a conflict occurs when multiple health classes with the same condition type (e.g., <boundary-data type="line-number">15   </boundary-data>
+age or work), corrective action and reaction mode are defined for a given server.    </p>
+    <p id="p-62" num="62">When a conflict occurs, the health controller applies the health class with the narrowest scope. In an exemplary embodiment, a single server is the narrowest scope, followed by a cluster and then an administrative domain. Additionally, users are prevented from defining classes that conflict at the same scope. For example, a non- <boundary-data type="line-number">20    </boundary-data>
+conflicting set of conditions according to this definition would be an administrative domain health class that sends a notification on violation of a memory condition, and a cluster health class that automatically restarts servers on violation of a memory condition.    </p>
+    <p id="p-63" num="63">If both of these health classes had automatic restarts as the reaction, they would conflict, and the cluster health class would apply to servers in the cluster.</p>
+    <p id="p-64" num="64">
+      <boundary-data type="line-number">25          </boundary-data>
+The health controller operates according to a set of configuration parameters that govern its runtime behavior. These configuration parameters include, but are not limited to, length of the control cycle (e.g., the time period between successive polling of the health subsystems), restart timeout (e.g., the maximum time allowed for a restart to occur; if the timeout is exceeded the restart is deemed as failed and the health controller <boundary-data type="line-number">30   </boundary-data>
+retries the operation), maximum number of server restarts (e.g., the maximum number of unsuccessful tries to restart a server, after which, an error is logged), minimum restart <boundary-data type="header">
+        <confidence value="86">YO</confidence>
+R920040396US1                        11      </boundary-data>
+      <page-break num="12"/>
+interval (e.g., the minimum time between consecutive attempts to restart a server, which prevents unnecessary frequent restarts) and constraining restart times (e.g., a list of time periods during which a restart is prohibited, such as, during peak business hours).    </p>
+    <p id="p-65" num="65">The restart timeout, maximum number of server restarts, minimum restart interval <boundary-data type="line-number">5   </boundary-data>
+and prohibited restart times parameters control the behavior of the server restart reaction.    </p>
+    <p id="p-66" num="66">However, in cluster server applications, at least one running instance is preferably always preserved, and in dynamic cluster applications, a user-specified minimum number of instances is preferably always preserved.</p>
+    <p id="p-67" num="67">FIG. 12 is a diagram illustrating an exemplary system for monitoring the health of <boundary-data type="line-number">10   </boundary-data>
+one or more application servers. Apparatus <part-num-ref name="health of one or more application servers. Apparatus">1220</part-num-ref>
+ comprises a computer system <part-num-ref name="computer system">1221</part-num-ref>
+ that interacts with media <part-num-ref name="that interacts with media">1227.</part-num-ref>
+ Computer system <part-num-ref name="that interacts with media 1227. Computer system">1221</part-num-ref>
+ comprises a processor <part-num-ref name="processor">1222,</part-num-ref>
+ a network interface <part-num-ref name="network interface">1225,</part-num-ref>
+ a memory <part-num-ref name="memory">1223,</part-num-ref>
+ a media interface <part-num-ref name="media interface">1226</part-num-ref>
+ and an optional display <part-num-ref name="optional display">1224.</part-num-ref>
+ Network interface <part-num-ref name="optional display 1224. Network interface">1225</part-num-ref>
+ allows computer system <part-num-ref name="allows computer system">1221</part-num-ref>
+ to connect to a network, while media interface <part-num-ref name="network, while media interface">1226</part-num-ref>
+ allows computer system <part-num-ref name="allows computer system">1221</part-num-ref>
+ to interact with media <part-num-ref name="to interact with media">1227,</part-num-ref>
+ <boundary-data type="line-number">15   </boundary-data>
+such as a Digital Versatile Disk (DVD) or a hard drive.    </p>
+    <p id="p-68" num="68">As is known in the art, the methods and apparatus discussed herein may be distributed as an article of manufacture that itself comprises a computer-readable medium having computer-readable code means embodied thereon. The computer-readable program code means is operable, in conjunction with a computer system such as <boundary-data type="line-number">20   </boundary-data>
+computer system <part-num-ref name="computer system such as computer system">1221,</part-num-ref>
+ to carry out all or some of the steps to perform one or more of the methods or create the apparatus discussed herein. For example, the computer-readable code is configured to implement a method of monitoring the health of one or more application servers by the steps of<confidence value="5">:</confidence>
+ monitoring at least one of one or more health policies for the one or more application servers, the one or more health policies being defined by <boundary-data type="line-number">25   </boundary-data>
+one or more specified health classes; and detecting violations, if any, of the one or more health policies. The computer-readable medium may be a recordable medium (e.g., floppy disks, hard drive, optical disks such as a DVD, or memory cards) or may be a transmission medium (e.g., a network comprising fiber-optics, the world-wide web, cables, or a wireless channel using time-division multiple access, code-division multiple <boundary-data type="line-number">30   </boundary-data>
+access, or other radio-frequency channel). Any medium known or developed that can store information suitable for use with a computer system may be used. The computer- <boundary-data type="header">
+        <confidence value="86">YO</confidence>
+R920040396US1                       12      </boundary-data>
+      <page-break num="13"/>
+readable code means is any mechanism for allowing a computer to read instructions and data, such as magnetic variations on a magnetic medium or height variations on the surface of a compact disk.    </p>
+    <p id="p-69" num="69">Memory 1223 configures the processor <part-num-ref name="processor">1222</part-num-ref>
+ to implement the methods, steps, <boundary-data type="line-number">5   </boundary-data>
+and functions disclosed herein. The memory <part-num-ref name="memory">1223</part-num-ref>
+ could be distributed or local and the processor <part-num-ref name="processor">1222</part-num-ref>
+ could be distributed or singular.  The memory <part-num-ref name="memory">1223</part-num-ref>
+ could be implemented as an electrical, magnetic or optical memory, or any combination of these or other types of storage devices. Moreover, the term "memory" should be construed broadly enough to encompass any information able to be read from or written to an <boundary-data type="line-number">10   </boundary-data>
+address in the addressable space accessed by processor <part-num-ref name="addressable space accessed by processor">1222.</part-num-ref>
+ With this definition, information on a network, accessible through network interface <part-num-ref name="network, accessible through network interface">1225,</part-num-ref>
+ is still within memory <part-num-ref name="network, accessible through network interface 1225, is still within memory">1223</part-num-ref>
+ because the processor <part-num-ref name="processor">1222</part-num-ref>
+ can retrieve the information from the network.    </p>
+    <p id="p-70" num="70">It should be noted that each distributed processor that makes up processor 1222 generally contains its own addressable memory space. It should also be noted that some or all of <boundary-data type="line-number">15   </boundary-data>
+computer system <part-num-ref name="generally contains its own addressable memory space. It should also be noted that some or all of computer system">1221</part-num-ref>
+ can be incorporated into an application-specific or general-use integrated circuit.    </p>
+    <p id="p-71" num="71">Optional video display 1224 is any type of video display suitable for interacting with a human user of apparatus <part-num-ref name="human user of apparatus">1220.</part-num-ref>
+ Generally, video display <part-num-ref name="human user of apparatus 1220. Generally, video display">1224</part-num-ref>
+ is a computer monitor or other similar video display.    </p>
+    <p id="p-72" num="72">
+      <boundary-data type="line-number">20         </boundary-data>
+Although illustrative embodiments of the present invention have been described herein, it is to be understood that the invention is not limited to those precise embodiments, and that various other changes and modifications may be made by one skilled in the art without departing from the scope or spirit of the invention.    </p>
+    <boundary-data type="header">
+      <confidence value="86">YO</confidence>
+R920040396US1                      13    </boundary-data>
+  </description>
+</us-patent-application>
+

prior_art/10942747.xml

@@ -0,0 +1,514 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>10942747</doc-number>
+        <date>2004-09-16</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">PATENT                                                            10320.9<confidence value="58858">0US01</confidence>
+     </p>
+    <heading id="h-1">DIGITAL CONTENT LICENSING TOOLBAR</heading>
+    <p id="p-2" num="2">
+      <boundary-data type="line-number">5                                    </boundary-data>
+Technical Field The present invention relates generally to graphical user interfaces for computer systems, and more particularly to a digital content licensing toolbar.    </p>
+    <p id="p-3" num="3">Back<confidence value="8">g</confidence>
+round <boundary-data type="line-number">10         </boundary-data>
+The rapid growth of the Internet and multimedia technology provides a vast distribution of digital content. Such digital content includes text, software programs, graphics, video, and audio in a variety of digital formats. It is technically possible for this digital content to move freely and reside in many locations from the time it is distributed until the time it is finally rendered and viewed by consumers.    </p>
+    <p id="p-4" num="4">
+      <boundary-data type="line-number">15         </boundary-data>
+One of the most significant issues for digital content providers is illegal use, distribution and re-distribution of the digital content. Typically, a content owner or rights owner, such as an author, a publisher, a broadcaster, etc. (hereinafter "content owner"), wishes to distribute such digital content to a user or recipient in exchange for a license fee or some other consideration. Such content owner would like to restrict what the user can <boundary-data type="line-number">20 </boundary-data>
+do with such distributed digital content. For example, the content owner would like to restrict the user from making an unlimited number of copies and re-distributing these copies to other users, at least in a manner that denies the content owner a license fee from such other users.    </p>
+    <boundary-data type="header">
+      <confidence value="8">1</confidence>
+    </boundary-data>
+    <p id="p-5" num="5">
+      <page-break num="2"/>
+Also, the content owner would like to provide the user with the flexibility to purchase different types of use licenses at different license fees, and at the same time hold the user to the terms of whatever type of license is in fact purchased. For example, the content owner may wish to allow distributed digital content to be copied only a limited <boundary-data type="line-number">5 </boundary-data>
+number of times.    </p>
+    <p id="p-6" num="6">However, after distribution has occurred, such content owners have very little, if any, control over the digital content. This is especially problematic in view of the fact that practically every new or recent personal computer includes software and hardware necessary to make an exact digital copy of such digital content. Also, the computer can <boundary-data type="line-number">10 </boundary-data>
+download the exact digital copy to a writeable magnetic or optical disk, or can send such exact digital copy over a network, such as the Internet, to any destination.    </p>
+    <p id="p-7" num="7">Today, content owners are provided with services to protect the distribution of their content. Users who want to copy or reuse content, such as a web page article, can simply click on an icon located on the viewed web page. This icon replaces, for example, the <boundary-data type="line-number">15 </boundary-data>
+traditional copyright symbol <confidence value="4">©</confidence>
+ and is hyperlinked to an instant clearance service. The article can then be licensed, purchased, and the received article can be used for personal, commercial, nonprofit, or academic reuse, according to the terms and prices set by the content owner. Also, for every license, the service creates a unique alphanumeric identifier stored in a database, which allows the content owner and a reprints provider to track the <boundary-data type="line-number">20 </boundary-data>
+status of the license. This license also serves as proof of compliance with the content owner's terms of use for both content owner and user.    </p>
+    <p id="p-8" num="8">The service also allows users to request quotes for customized reprints or customized e-prints. The service automatically forwards this request to the content owner's <boundary-data type="header">
+        <confidence value="8">2</confidence>
+      </boundary-data>
+      <page-break num="3"/>
+internal or external reprint provider. After receiving the reprints, the users can then distribute the content for their personal needs. Hence, simple and quick reuse of original content is legally obtained by providing instant access to rights and permissions at a point of acquisition of the content.    </p>
+    <p id="p-9" num="9">
+      <boundary-data type="line-number">5         </boundary-data>
+Further, the service is beneficial to content owners because it presents the content owners<confidence value="5">'</confidence>
+ various licensing options, processes the payments, issues the licenses, and fulfills the content in the form specified by the user. The service also ensures that the brand and intellectual property rights of the content owners are protected and monetized. Further, it allows an extension of their brand name and opens new revenue streams.    </p>
+    <p id="p-10" num="10">
+      <boundary-data type="line-number">10         </boundary-data>
+However, the service includes much inefficiency. For example, drawbacks to the service include wasting time filling out lengthy permission request forms when logging into multiple password protected sites and determining the licensability of numerous articles.    </p>
+    <p id="p-11" num="11">
+      <boundary-data type="line-number">
+        <confidence value="88">15</confidence>
+      </boundary-data>
+ <confidence value="88">20</confidence>
+ <boundary-data type="header">
+        <confidence value="8">3</confidence>
+      </boundary-data>
+      <page-break num="4"/>
+Summary In general terms, the present invention is a digital content licensing toolbar for providing search capabilities and notice of licensable subject matter.    </p>
+    <p id="p-12" num="12">One aspect of the present invention is a method for displaying search results and <boundary-data type="line-number">5   </boundary-data>
+identifying licensing status, including performing a query on a selected criteria, listing results of the query in a specified format, and indicating a licensing status for each result in the listing.    </p>
+    <p id="p-13" num="13">Another aspect of the present invention is directed to a computer system for displaying search results and identifying licensing status for each item in the search results, <boundary-data type="line-number">10  </boundary-data>
+the computer system including a user interface, a processor coupled to the user interface for displaying a toolbar on the user interface, the toolbar having a search field for performing a search on a selected criteria, an output device coupled to the processor for listing results of the search in a specified format, and an indicator linked to each search result in the listing for displaying a licensing status for each of the results in the listing.    </p>
+    <p id="p-14" num="14">
+      <boundary-data type="line-number">15         </boundary-data>
+Another aspect of the present invention is directed to a user menu interface for identifying licensing status for each item in a search result, including a search field for performing a search on selected criteria, and an indicator displaying the licensing status for a selected result in the listing.    </p>
+    <p id="p-15" num="15">Another aspect of the present invention is a program storage device readable by a <boundary-data type="line-number">20   </boundary-data>
+computer tangibly embodying one or more programs of instructions executable by the computer to perform a method for displaying search results and identifying licensing status, the method including performing a query on a selected criteria, listing results of the query in a specified format, and indicating a licensing status for each result in the listing.    </p>
+    <boundary-data type="header">
+      <confidence value="8">4</confidence>
+    </boundary-data>
+    <p id="p-16" num="16">
+      <page-break num="5"/>
+Yet another aspect of the present invention is directed to a system for associating tagged content with a licensee, the system including one or more content owners providing tagged content, and a user menu interface associated with a specific licensee for displaying license status of tagged content, wherein the license status displayed is based on the tagged <boundary-data type="line-number">5 </boundary-data>
+content of the one or more content owners for which the specified licensee has purchased a license.    </p>
+    <boundary-data type="header">
+      <confidence value="8">5</confidence>
+    </boundary-data>
+    <p id="p-17" num="17">
+      <page-break num="6"/>
+Descri<confidence value="8">p</confidence>
+tion of the Drawin<confidence value="68">gs</confidence>
+ Figure 1 is a block diagram illustrating one possible embodiment of a system implementing a digital content licensing toolbar according to the present invention;    </p>
+    <p id="p-18" num="18">Figure 2 illustrates one possible embodiment of a computer system that includes <boundary-data type="line-number">5 </boundary-data>
+the functional blocks of Figure 1;    </p>
+    <p id="p-19" num="19">Figure 3 is a block diagram illustrating an installation procedure for the digital content licensing toolbar according to the present invention;</p>
+    <p id="p-20" num="20">Figure 4 is a functional diagram illustrating the general functionality of the digital content licensing toolbar according to the present invention;</p>
+    <p id="p-21" num="21">
+      <boundary-data type="line-number">10         </boundary-data>
+Figure 5 illustrates one possible embodiment of a graphics user interface (GUI) application including a digital content license toolbar according to the present invention;    </p>
+    <p id="p-22" num="22">Figure 6 illustrates a general setup functionality for the digital content license toolbar according to the present invention;</p>
+    <p id="p-23" num="23">Figure 7 illustrates the search functionality of the digital content license toolbar <boundary-data type="line-number">15 </boundary-data>
+according to the present invention;    </p>
+    <p id="p-24" num="24">Figure 8 illustrates a search results summary report generated by the digital content licensing toolbar;</p>
+    <p id="p-25" num="25">Figure 9A illustrates a content provider functionality of digital content licensing toolbar according to the present invention; and <boundary-data type="line-number">20         </boundary-data>
+Figure 9B illustrates additional content provider functionality of digital content licensing toolbar according to the present invention.    </p>
+    <boundary-data type="header">
+      <confidence value="8">6</confidence>
+    </boundary-data>
+    <p id="p-26" num="26">
+      <page-break num="7"/>
+Detailed Description Various embodiments of the present invention will be described in detail with reference to the drawings, wherein like reference numerals represent like parts and assemblies throughout the several views. Reference to various embodiments does not limit <boundary-data type="line-number">5 </boundary-data>
+the scope of the invention, which is limited only by the scope of the claims attached hereto.    </p>
+    <p id="p-27" num="27">Additionally, any examples set forth in this specification are not intended to be limiting and merely set forth some of the many possible embodiments for the claimed invention.</p>
+    <p id="p-28" num="28">Figure 1 is a block diagram illustrating one possible embodiment of a system implementing a digital content licensing toolbar. A user menu interface, such as a toolbar, <boundary-data type="line-number">10 </boundary-data>
+can be any device or mechanism that is displayed on a user interface, such as a graphical user interface, which permits a user to trigger functions or commands used in an applications in an expedited manner. It will be readily appreciated by those skilled in the art that user interfaces and elements of user interfaces may be used in combination with any system having typical system components such as, for example, a processor and a <boundary-data type="line-number">15 </boundary-data>
+display. It should further be noted that the present invention may be embodied as an article of manufacture such as a software disk, optical disk, software download from a network, or the like including instructions for causing a processor to carry out steps in accordance therewith.    </p>
+    <p id="p-29" num="29">In general, such computer systems, as illustrated in block diagram form in Figure 1, <boundary-data type="line-number">20 </boundary-data>
+may include, for example, bus 100 for communicating information, processor <part-num-ref name="for communicating information, processor">101</part-num-ref>
+ coupled with bus <part-num-ref name="coupled with bus">100</part-num-ref>
+ for processing information and instructions. The system also includes random access memory <part-num-ref name="system also includes random access memory">102</part-num-ref>
+ coupled with bus <part-num-ref name="coupled with bus">100</part-num-ref>
+ for storing information and instructions for processor <part-num-ref name="for storing information and instructions for processor">101,</part-num-ref>
+ read only memory <part-num-ref name="for storing information and instructions for processor 101, read only memory">103</part-num-ref>
+ coupled with bus <part-num-ref name="coupled with bus">100</part-num-ref>
+ for storing static <boundary-data type="header">
+        <confidence value="8">7</confidence>
+      </boundary-data>
+      <page-break num="8"/>
+information and instructions for processor <part-num-ref name="for storing static information and instructions for processor">101,</part-num-ref>
+ data storage device <part-num-ref name="for storing static information and instructions for processor 101, data storage device">104</part-num-ref>
+ which may be, for example, a magnetic disk and disk drive or CD-ROM<confidence value="5">/</confidence>
+DVD-ROM drive, coupled with bus <part-num-ref name="magnetic disk and disk drive or CD-ROM/DVD-ROM drive, coupled with bus">100,</part-num-ref>
+ also for storing information and instructions.    </p>
+    <p id="p-30" num="30">The data storage device 104 stores an operating system for controlling the <boundary-data type="line-number">5 </boundary-data>
+operation of the programmable computing system. It will be appreciated that this component may comprise a general-purpose server operating system such as UNIX, <confidence value="66">LI</confidence>
+NUXTM, or Microsoft WINDOWS. A basic input/output system (<confidence value="5">"</confidence>
+BIOS") is also provided for controlling low-level operation of the computing system.    </p>
+    <p id="p-31" num="31">Display device 105 can be coupled to bus <part-num-ref name="can be coupled to bus">100</part-num-ref>
+ for displaying information and <boundary-data type="line-number">10 </boundary-data>
+providing visual feedback to a computer user. It will be understood that display device <part-num-ref name="computer user. It will be understood that display device">105</part-num-ref>
+ can include appropriate interfaces such as a graphics adapter or the like. Alphanumeric input device <part-num-ref name="like. Alphanumeric input device">106</part-num-ref>
+ may further be coupled to bus <part-num-ref name="may further be coupled to bus">100,</part-num-ref>
+ and may include, for example, a keyboard including alphanumeric and function keys for communicating information and command selections to processor <part-num-ref name="keyboard including alphanumeric and function keys for communicating information and command selections to processor">101.</part-num-ref>
+ Cursor control device <part-num-ref name="keyboard including alphanumeric and function keys for communicating information and command selections to processor 101. Cursor control device">107</part-num-ref>
+ may be coupled to bus <boundary-data type="line-number">15 </boundary-data>
+      <part-num-ref name="may be coupled to bus">100,</part-num-ref>
+ and, through visual feedback on display device <part-num-ref name="may be coupled to bus 100, and, through visual feedback on display device">105</part-num-ref>
+ from, for example, a pointer icon associated with a mouse, may communicate information and command selections to processor <part-num-ref name="mouse, may communicate information and command selections to processor">101.</part-num-ref>
+ Signal generating device <part-num-ref name="mouse, may communicate information and command selections to processor 101. Signal generating device">108</part-num-ref>
+ can further be coupled to the bus <part-num-ref name="bus">100</part-num-ref>
+ for providing signal related input/output functions to processor <part-num-ref name="for providing signal related input/output functions to processor">101.</part-num-ref>
+    </p>
+    <p id="p-32" num="32">Display device 105 can preferably be, for example, a liquid crystal device, cathode <boundary-data type="line-number">20 </boundary-data>
+ray tube, or other display device suitable for creating images and alphanumeric characters including ideographic character sets recognizable to the user. Cursor control device <part-num-ref name="user. Cursor control device">107</part-num-ref>
+ may allow the computer user to control the two-dimensional movement of a visible symbol such as a cursor and/or a pointer on a display screen of display device <part-num-ref name="display screen of display device">105.</part-num-ref>
+    </p>
+    <boundary-data type="header">
+      <confidence value="8">8</confidence>
+    </boundary-data>
+    <p id="p-33" num="33">
+      <page-break num="9"/>
+Many implementations of cursor control device 107 are known in the art including a trackball, mouse, joystick or special keys on the alphanumeric input device <part-num-ref name="alphanumeric input device">106,</part-num-ref>
+ any of which may be capable of signaling movement of a given direction or manner of displacement of a corresponding visual indication such as a pointer icon, or visual <boundary-data type="line-number">5 </boundary-data>
+representation of a cursor. It is to be appreciated that the cursor may be directed and/or activated via input from alphanumeric input device <part-num-ref name="cursor may be directed and/or activated via input from alphanumeric input device">106,</part-num-ref>
+ such as a keyboard, using special keys and key sequence commands.    </p>
+    <p id="p-34" num="34">Alternatively, a cursor may be directed and/or activated via input from a number of specially adapted cursor directing devices; including those uniquely developed for the <boundary-data type="line-number">10 </boundary-data>
+disabled. For example, a cursor may be directed and corresponding adjustments in the position of a cursor and/or corresponding selections, activations, and the like as might be seen, for example, by operating a mouse button may be made through devices specifically adapted to recognize speech input. In the discussions regarding cursor movement and/or activation within the possible embodiments, it is to be assumed that the input cursor- <boundary-data type="line-number">15  </boundary-data>
+directing device or push button may consist of any of those described above and specifically is not limited to a mouse cursor device.    </p>
+    <p id="p-35" num="35">Figure 2 illustrates one possible embodiment of computer system <part-num-ref name="illustrates one possible embodiment of computer system">200</part-num-ref>
+ that includes the functional blocks of Figure 1. It will be appreciated that such a computer system is one of many computer systems that may be used in accordance with the present invention.    </p>
+    <p id="p-36" num="36">
+      <boundary-data type="line-number">20 </boundary-data>
+Accordingly, keyboard 201 having, for example, keys <part-num-ref name="having, for example, keys">202</part-num-ref>
+ and numeric keypad <part-num-ref name="and numeric keypad">204</part-num-ref>
+ may be attached to computer <part-num-ref name="may be attached to computer">206</part-num-ref>
+ along with a cursor control device such as, for example, mouse device <part-num-ref name="cursor control device such as, for example, mouse device">208</part-num-ref>
+ having one or more mouse push buttons <part-num-ref name="having one or more mouse push buttons">210</part-num-ref>
+ for providing and controlling certain relocation and activation features associated with the cursor and, for <boundary-data type="header">
+        <confidence value="8">9</confidence>
+      </boundary-data>
+      <page-break num="10"/>
+example, an iconographic object which it may be "pointing" to. Mouse device <part-num-ref name="iconographic object which it may be &quot;pointing&quot; to. Mouse device">208</part-num-ref>
+ and push buttons <part-num-ref name="and push buttons">210,</part-num-ref>
+ for example, may make up one example of a device in accordance with cursor control device <part-num-ref name="device in accordance with cursor control device">107</part-num-ref>
+ (Figure 1). It will be appreciated that many other devices may be used as cursor control device <part-num-ref name="(Figure 1). It will be appreciated that many other devices may be used as cursor control device">107,</part-num-ref>
+ for instance, keyboard <part-num-ref name="(Figure 1). It will be appreciated that many other devices may be used as cursor control device 107, for instance, keyboard">201</part-num-ref>
+ may be substituted for <boundary-data type="line-number">5 </boundary-data>
+mouse device <part-num-ref name="may be substituted for mouse device">208</part-num-ref>
+ and buttons <part-num-ref name="and buttons">210</part-num-ref>
+ as described. Computer <part-num-ref name="as described. Computer">206</part-num-ref>
+ also typically contains one or more media drives <part-num-ref name="also typically contains one or more media drives">211,</part-num-ref>
+ which may include, for example, a floppy disk, hard disk or CD ROM. Computer <part-num-ref name="floppy disk, hard disk or CD ROM. Computer">206</part-num-ref>
+ may include a display screen <part-num-ref name="display screen">212,</part-num-ref>
+ which as described may include, for example, a CRT, LCD display, and the like.    </p>
+    <p id="p-37" num="37">In some applications, computing system 200 acts as a World Wide Web (web) <boundary-data type="line-number">10 </boundary-data>
+server to transmit web pages to a web browser application program executing on requesting devices to carry out this process. For instance, a web server may transmit pages used for retrieving information from a user. In one embodiment, the form elicits such information as user preferences, address, telephone number, billing information, credit card numbers, and the like. Moreover, the web server can transmit web pages to a requesting <boundary-data type="line-number">15 </boundary-data>
+device and allow a user to interact with web pages. The interaction can take place over the Internet, WAN/LAN, or any other suitable communications network.    </p>
+    <p id="p-38" num="38">The computing system 200 is connected to a WAN/LAN, or other communications network, via network interface unit <part-num-ref name="WAN/LAN, or other communications network, via network interface unit">215.</part-num-ref>
+ Hence, it will be appreciated that the network interface unit <part-num-ref name="network interface unit">215</part-num-ref>
+ includes the necessary circuitry for connecting computing system <part-num-ref name="necessary circuitry for connecting computing system">200</part-num-ref>
+ to <boundary-data type="line-number">20 </boundary-data>
+the WAN/LAN, and is constructed for use with various communication protocols including the TCP/IP protocol. Typically, the network interface unit <part-num-ref name="network interface unit">215</part-num-ref>
+ is a card contained within the computing system <part-num-ref name="computing system">200.</part-num-ref>
+    </p>
+    <boundary-data type="header">
+      <confidence value="88">10</confidence>
+    </boundary-data>
+    <p id="p-39" num="39">
+      <page-break num="11"/>
+Figure 3 is a block diagram illustrating an installation procedure for the digital content licensing toolbar <part-num-ref name="digital content licensing toolbar">300.</part-num-ref>
+ The digital content licensing toolbar <part-num-ref name="digital content licensing toolbar">300</part-num-ref>
+ provides various menu items (or icons) such as adding, moving, invoking, and removing the toolbar <part-num-ref name="toolbar">300</part-num-ref>
+ to or from an operating system or the like. The menu items provide familiar toolbar-like <boundary-data type="line-number">5 </boundary-data>
+features across applications and window instances within an operating system user interface environment such as, for example, Microsoft WINDOWS operating system and other operating systems that provide a user interface.    </p>
+    <p id="p-40" num="40">The digital content licensing toolbar 300 can be associated with a variety of applications, such as an Internet browser, e.g., <confidence value="5">I</confidence>
+NTERNET EXPLORER. However, the <boundary-data type="line-number">10 </boundary-data>
+installation is not limited to this application and the digital content licensing toolbar <part-num-ref name="digital content licensing toolbar">300</part-num-ref>
+ can be installed in any suitable software environment. The digital content licensing toolbar <part-num-ref name="digital content licensing toolbar">300</part-num-ref>
+ is downloaded, for example, via a signed cabinet (CAB) files <part-num-ref name="signed cabinet (CAB) files">302</part-num-ref>
+ located on a distribution diskette or from the Internet. When prompted, for example, a username and password <part-num-ref name="username and password">305</part-num-ref>
+ is entered to allow the user to download the toolbar <part-num-ref name="toolbar">300.</part-num-ref>
+    </p>
+    <p id="p-41" num="41">
+      <boundary-data type="line-number">15         </boundary-data>
+Standard data, such as extensible markup language (XML) data, is stored in the CAB files <part-num-ref name="CAB files">302</part-num-ref>
+ as well as on the Internet. Extensible markup language is a markup language for documents containing structured information. The structured information contains both content for the toolbar <part-num-ref name="toolbar">300</part-num-ref>
+ (words, pictures, etc.) and some indication of what role that content plays. For example, the extensible markup language data <boundary-data type="line-number">20 </boundary-data>
+downloaded from the Internet will provide dynamic configuration data that can change the look of the toolbar <part-num-ref name="toolbar">300</part-num-ref>
+ without forcing a user to acquire a new version.    </p>
+    <p id="p-42" num="42">When installing the toolbar <part-num-ref name="toolbar">300</part-num-ref>
+ via the Internet, a complete install package can be downloaded from the provider's (or the toolbar <part-num-ref name="toolbar">300)</part-num-ref>
+ site. The install package will prompt <boundary-data type="header">
+        <confidence value="88">11</confidence>
+      </boundary-data>
+      <page-break num="12"/>
+the user for valid information such as the user's company name and department. The install process will also validate various key codes to ensure that user has valid site licenses for the sites the user plans to visit; a site license being a license authorizing one or more persons employed by a single enterprise to utilize materials protected by copyright <boundary-data type="line-number">5 </boundary-data>
+and/or trademarks belonging to others. For example, key code can provide access to a variety of company sites, such as ADWEEK, REUTERS and WIRELESS REVIEW.    </p>
+    <p id="p-43" num="43">Figure 4 is a functional diagram <part-num-ref name="functional diagram">400</part-num-ref>
+ illustrating the general functionality of the digital content licensing toolbar <part-num-ref name="digital content licensing toolbar">402.</part-num-ref>
+ The following is a brief explanation of the functionality of several of the possible toolbar menu items. The digital content toolbar <part-num-ref name="digital content toolbar">402</part-num-ref>
+ <boundary-data type="line-number">10 </boundary-data>
+provides, but is not limited to, this functionality. However, a more detailed description of selected and additional functionality will be discussed later. The toolbar need not contain each of these functional elements but may be customized based upon the user company or individual user specifications.    </p>
+    <p id="p-44" num="44">Upon installation of the toolbar <part-num-ref name="toolbar">402,</part-num-ref>
+ as discussed in Figure 3, a unique toolbar <boundary-data type="line-number">15 </boundary-data>
+identifier <part-num-ref name="unique toolbar identifier">404</part-num-ref>
+ is provided. The identifier allows software to uniquely identify a user when an associated browser is activated. This identifier can be used to track user acquired licenses by the content owner or reprint provider. An auto check update <part-num-ref name="auto check update">406</part-num-ref>
+ is provided and prompts the user when updates to the toolbar are available. The user has the option to accept or cancel the update operation.    </p>
+    <p id="p-45" num="45">
+      <boundary-data type="line-number">20         </boundary-data>
+When text is entered into a search field on the toolbar <part-num-ref name="toolbar">402</part-num-ref>
+ and a query is executed and a list of publications <part-num-ref name="list of publications">408</part-num-ref>
+ is generated. The list contains an abstract for each of the publications. Also, each publication abstract in the list is provided with a link, such as a hyperlink, to the actual article (i.e., content) or category of articles <part-num-ref name="content) or category of articles">410.</part-num-ref>
+ A dynamic button <boundary-data type="header">
+        <confidence value="88">12</confidence>
+      </boundary-data>
+      <page-break num="13"/>
+icon for each search word <part-num-ref name="dynamic button icon for each search word">412</part-num-ref>
+ provides the user with a link to the next occurrence of the queried word on the current page (or other pages) of the currently viewed article. The highlight search word functiona<confidence value="8">l</confidence>
+ity <part-num-ref name="highlight search word functionality">414</part-num-ref>
+ allows the user to see each occurrence of the queried word highlighted in a publication. The queried word can be highlighted in, but is <boundary-data type="line-number">5 </boundary-data>
+not limited to, any font, color or texture provided by the application. Furthermore, when an article is selected, the user can use the search for similar content icon <part-num-ref name="search for similar content icon">416</part-num-ref>
+ to generate a list of similar subject matter. Zoom in/out functionality <part-num-ref name="list of similar subject matter. Zoom in/out functionality">417</part-num-ref>
+ allows the user to view, for example, a web page in greater or lesser detail.    </p>
+    <p id="p-46" num="46">Other functionality provided by the digital content licensing toolbar <part-num-ref name="digital content licensing toolbar">402</part-num-ref>
+ includes <boundary-data type="line-number">10 </boundary-data>
+allowing a user to go to the home site <part-num-ref name="home site">418.</part-num-ref>
+ The home site functionality <part-num-ref name="home site functionality">418</part-num-ref>
+ includes menu items such as editing user options <part-num-ref name="includes menu items such as editing user options">420</part-num-ref>
+ (e.g., <confidence value="22222222">username</confidence>
+ and password), executing updates <part-num-ref name="username and password), executing updates">422,</part-num-ref>
+ and an uninstall <part-num-ref name="uninstall">424</part-num-ref>
+ function to allow removal of the toolbar <part-num-ref name="toolbar">402.</part-num-ref>
+ More specifically, the edit user options menu item <part-num-ref name="edit user options menu item">420</part-num-ref>
+ stores user account information. When the user selects the edit user options menu item <part-num-ref name="edit user options menu item">420,</part-num-ref>
+ the user profile within the provider's website is <boundary-data type="line-number">15 </boundary-data>
+displayed. The user can now edit a variety of options, such as the user's account profile, email notifications, billing information, etc.    </p>
+    <p id="p-47" num="47">Two levels are provided for the user's account profile. The first level is an individual user profile that contains information such as the username, password and personal information such as company name, address, age, gender etc. The second level is <boundary-data type="line-number">20 </boundary-data>
+an administrative account profile. The administrative account profile stores account profile information such as billing information for the company.    </p>
+    <p id="p-48" num="48">The edit box with history functionality 426 maintains the history of the queried text string. This history can be used to recount prior searches. A "searched licensed data" <boundary-data type="header">
+        <confidence value="88">13</confidence>
+      </boundary-data>
+      <page-break num="14"/>
+functionality <part-num-ref name="&quot;searched licensed data&quot; functionality">428</part-num-ref>
+ allows the user to gather content from different time periods, such as yesterday <part-num-ref name="user to gather content from different time periods, such as yesterday">430,</part-num-ref>
+ the past week <part-num-ref name="past week">432,</part-num-ref>
+ and the past month <part-num-ref name="past month">434.</part-num-ref>
+ The user can then choose the license functionality <part-num-ref name="license functionality">436</part-num-ref>
+ to purchase or license the content.    </p>
+    <p id="p-49" num="49">Auto login functionality 438 allows the user to bypass the sign-in process by <boundary-data type="line-number">5 </boundary-data>
+transparently signing-in the user by using information from the user's account. Hence, the user can view a selected page from an otherwise password-protected site without the burden of filling out lengthy request forms or logging-in.    </p>
+    <p id="p-50" num="50">Finally, a call for help functionality <part-num-ref name="call for help functionality">439</part-num-ref>
+ allows the user to request additional information about content that the user is viewing. The user's information, along with a <boundary-data type="line-number">10 </boundary-data>
+link to the content the user is viewing, can be sent to a customer service representative of the content provider who can investigate the inquiry and respond accordingly.    </p>
+    <p id="p-51" num="51">Figure 5 illustrates one possible embodiment of a graphics user interface (GUI) application <part-num-ref name="graphics user interface (GUI) application">500</part-num-ref>
+ including a digital content license toolbar <part-num-ref name="digital content license toolbar">501.</part-num-ref>
+ Once the digital content license toolbar <part-num-ref name="digital content license toolbar">501</part-num-ref>
+ is installed on a graphics user interface <part-num-ref name="graphics user interface">500</part-num-ref>
+ as discussed above, toolbar <boundary-data type="line-number">15  </boundary-data>
+menu icons 504-512 are available through inheritance to subsequently launched instances of an application (e.g., INTERNET EXPLORER) and new applications. Similarly, when a configuration of the toolbar <part-num-ref name="toolbar">501</part-num-ref>
+ changes, the new configuration may take effect in all open application windows and in subsequently launched application windows.    </p>
+    <p id="p-52" num="52">The embodiment of Figure 5 shows a graphical user interface <part-num-ref name="graphical user interface">500</part-num-ref>
+ in a relatively <boundary-data type="line-number">20 </boundary-data>
+fundamental form, where the application employs, for example, document window <part-num-ref name="application employs, for example, document window">516</part-num-ref>
+ within an operating environment having pull down menu categories or icons. The menu categories include, for example, File <part-num-ref name="menu categories include, for example, File">518,</part-num-ref>
+ Edit <part-num-ref name="menu categories include, for example, File 518, Edit">520,</part-num-ref>
+ View <part-num-ref name="menu categories include, for example, File 518, Edit 520, View">522,</part-num-ref>
+ Favorites <part-num-ref name="menu categories include, for example, File 518, Edit 520, View 522, Favorites">524,</part-num-ref>
+ Tools <part-num-ref name="menu categories include, for example, File 518, Edit 520, View 522, Favorites 524, Tools">526</part-num-ref>
+ and Help <part-num-ref name="and Help">528</part-num-ref>
+ accessible using a pointer, the position of which may be controlled, for <boundary-data type="header">
+        <confidence value="88">14</confidence>
+      </boundary-data>
+      <page-break num="15"/>
+example, by a cursor control device as previously described such as a mouse, trackball, or the like. The graphical user interface <part-num-ref name="graphical user interface">500</part-num-ref>
+ environment can be driven by an operating system and can include, for example, hardware interfaces to resources such as printers, input devices, output devices, and the like as would be appreciated by one skilled in the art <boundary-data type="line-number">5 </boundary-data>
+of operating system design.    </p>
+    <p id="p-53" num="53">The document window 516 is configured to display content such as an article <part-num-ref name="article">530.</part-num-ref>
+    </p>
+    <p id="p-54" num="54">The article incorporates links (or tagged fields) 534, such as hyperlinks, to a clearance service for purchasing or licensing the article for reuse. A tagged field is, for example, custom extensible markup language (XML) code that identifies different characteristics of <boundary-data type="line-number">10 </boundary-data>
+content. For example, a tag can identify the title of an article. In general, the licensing of content provides a user with a limited license to print, reprint, e-mail (<confidence value="22222222222222">distribute).or</confidence>
+ display the content on the user's intranet. The user can incur additional charges if the licensed material is distributed outside the user's company/intranet, i.e., distributed over the Internet to unlicensed users.    </p>
+    <p id="p-55" num="55">
+      <boundary-data type="line-number">15         </boundary-data>
+Figure 6 illustrates a general setup functionality for the digital content license toolbar <part-num-ref name="digital content license toolbar">610.</part-num-ref>
+ The toolbar <part-num-ref name="toolbar">610</part-num-ref>
+ includes several menu items (or icons) as discussed above.    </p>
+    <p id="p-56" num="56">The logo menu icon 615, when selected, will take a user (i.e., customer, publisher, author) to the toolbar provider's homepage. The toolbar provider, as used herein, is the provider providing the service to access content owner data. Here, the user can obtain detailed <boundary-data type="line-number">20 </boundary-data>
+information on, for example, licensing and reprint services.    </p>
+    <p id="p-57" num="57">The user can also select the dropdown menu arrow <part-num-ref name="dropdown menu arrow">620</part-num-ref>
+ on the logo icon <part-num-ref name="logo icon">615</part-num-ref>
+ to display addition menu items. These menu items include a user options function <part-num-ref name="user options function">625,</part-num-ref>
+ update function <part-num-ref name="user options function 625, update function">630,</part-num-ref>
+ and an uninstall function <part-num-ref name="uninstall function">635.</part-num-ref>
+ When the user options menu item <part-num-ref name="user options menu item">625</part-num-ref>
+ <boundary-data type="header">
+        <confidence value="88">15</confidence>
+      </boundary-data>
+      <page-break num="16"/>
+is selected, a pop-up window <part-num-ref name="pop-up window">640</part-num-ref>
+ is displayed in the document window <part-num-ref name="document window">601</part-num-ref>
+ of the graphical user interface <part-num-ref name="graphical user interface">600.</part-num-ref>
+ The user is prompted to enter a username <part-num-ref name="username">642</part-num-ref>
+ and password <part-num-ref name="and password">644</part-num-ref>
+ which will be stored in memory and used to enter the toolbar provider's sites. To complete the operation the user selects the apply button <part-num-ref name="apply button">646,</part-num-ref>
+ or cancels the operation by <boundary-data type="line-number">5 </boundary-data>
+selecting the cancel <part-num-ref name="cancel">648</part-num-ref>
+ button.    </p>
+    <p id="p-58" num="58">The update function 630 allows the toolbar software to be manually updated to the newest version. Accordingly, by selecting the update function <part-num-ref name="update function">630,</part-num-ref>
+ the user is prompted to either continue with an update to the most current version of the toolbar software or cancel the selected operation. Alternatively, the user can set a parameter in the user options <part-num-ref name="user options">625</part-num-ref>
+ <boundary-data type="line-number">10 </boundary-data>
+to perform the update automatically. Hence, if a new version of the toolbar is subsequently released, the toolbar software is automatically activated to check the installed version and, if different from the released version, update to the most current version. In either the manual or automatic update operation, the user is subsequently notified as to the current version of the software installed.    </p>
+    <p id="p-59" num="59">
+      <boundary-data type="line-number">15          </boundary-data>
+The uninstall function 635 uninstalls the toolbar and associated software.    </p>
+    <p id="p-60" num="60">Accordingly, by selecting the uninstall function <part-num-ref name="uninstall function">635,</part-num-ref>
+ the user is prompted to either continue with the uninstall operation or cancel the selected operation. The user is then notified as to the current version of the toolbar.    </p>
+    <p id="p-61" num="61">Figure 7 illustrates the search functionality of the digital content license toolbar <boundary-data type="line-number">20 </boundary-data>
+      <part-num-ref name="digital content license toolbar">710.</part-num-ref>
+ A search text field <part-num-ref name="search text field">720</part-num-ref>
+ is provided on the toolbar <part-num-ref name="toolbar">710.</part-num-ref>
+ The search text field <part-num-ref name="search text field">720</part-num-ref>
+ allows the user to enter search criteria. For example, criteria such as a company name is entered into the search text field <part-num-ref name="search text field">720.</part-num-ref>
+ Alternatively, the menu arrow <part-num-ref name="menu arrow">725</part-num-ref>
+ can be selected to reveal a search history. The user then highlights the desired query from the search history <boundary-data type="header">
+        <confidence value="88">16</confidence>
+      </boundary-data>
+      <page-break num="17"/>
+by using a pointing device such as the arrow keys on the keypad or the mouse. The highlighted criteria are then loaded into the search field <part-num-ref name="search field">720.</part-num-ref>
+    </p>
+    <p id="p-62" num="62">The user then selects a timeframe for which the search is to be conducted. This is accomplished by selecting the search days icon <part-num-ref name="search days icon">730</part-num-ref>
+ to reveal a dropdown menu of toolbar <boundary-data type="line-number">5 </boundary-data>
+      <part-num-ref name="dropdown menu of toolbar">710</part-num-ref>
+ into the document window <part-num-ref name="document window">750</part-num-ref>
+ of the graphical user interface <part-num-ref name="graphical user interface">755.</part-num-ref>
+ The dropdown menu provides multiple ranges in which the search is to be conducted. For example, a user can search the previous day <part-num-ref name="previous day">735,</part-num-ref>
+ the past week <part-num-ref name="past week">740,</part-num-ref>
+ or the past month <part-num-ref name="past month">745.</part-num-ref>
+ When the range <part-num-ref name="range">735,</part-num-ref>
+ <part-num-ref name="range 735,">740,</part-num-ref>
+ <part-num-ref name="range 735, 740,">745</part-num-ref>
+ is selected, a search is automatically executed. A summary of search results is discussed in below.    </p>
+    <p id="p-63" num="63">
+      <boundary-data type="line-number">10         </boundary-data>
+Figure 8 illustrates a search results summary report generated by the digital content licensing toolbar <part-num-ref name="digital content licensing toolbar">800.</part-num-ref>
+ Search results are displayed, for example, in a paginated format (over multiple pages) in the document window <part-num-ref name="document window">810</part-num-ref>
+ of the graphical user interface <part-num-ref name="graphical user interface">815.</part-num-ref>
+    </p>
+    <p id="p-64" num="64">This paginated format will provide the user the ability to easily navigate through the results as well as improve the speed of the results that are returned from the search. However, the <boundary-data type="line-number">15 </boundary-data>
+search results are not limited to a paginated format and any suitable formats can be used.    </p>
+    <p id="p-65" num="65">In addition, when bandwidth or memory of the targeted processor is not sufficient, the summary of the search results can be transmitted to and displayed or stored on another server(s).</p>
+    <p id="p-66" num="66">In operation, when the range <part-num-ref name="range">735,</part-num-ref>
+ <part-num-ref name="range 735,">740,</part-num-ref>
+ <part-num-ref name="range 735, 740,">745</part-num-ref>
+ is selected (as discussed in Figure 7), <boundary-data type="line-number">20 </boundary-data>
+the user will be automatically be logged into one or more search databases/web pages using login information stored within the user's registry. The user is not limited to any specific database and can search, for example, the World Wide Web or any other desired location coupled to the user's computer system.    </p>
+    <boundary-data type="header">
+      <confidence value="88">17</confidence>
+    </boundary-data>
+    <p id="p-67" num="67">
+      <page-break num="18"/>
+To gain access to the desired databases/locations, user login information is retrieved from the registry (e.g., https://www.rsicopyright.com<confidence value="5">/</confidence>
+ics/user<confidence value="1">-</confidence>
+reg/user<confidence value="15">-l</confidence>
+ogin .html) and transmitted to login pages of licensed <confidence value="222222">and/or</confidence>
+ unlicensed sites. The user's registry can be located in any sufficient memory location and populated using information <boundary-data type="line-number">5 </boundary-data>
+stored by the options menu <part-num-ref name="options menu">625</part-num-ref>
+ (Figure 6). The login pages will accept the login information from the toolbar registry and will authenticate the user. If the login information is valid, the user will automatically be logged into the system and associated search databases/web pages.    </p>
+    <p id="p-68" num="68">A search results summary report 817 lists the content, such as article abstracts, that <boundary-data type="line-number">10 </boundary-data>
+match the search criteria entered in a search field <part-num-ref name="search field">818.</part-num-ref>
+ For example, if the search criteria "marketing" were entered in the search field <part-num-ref name="search field">818,</part-num-ref>
+ any content matching this criterion is displayed as, but not limited to, abstracts in the document window <part-num-ref name="document window">810</part-num-ref>
+ of the graphical user interface <part-num-ref name="graphical user interface">815.</part-num-ref>
+ The search criterion is replicated <part-num-ref name="search criterion is replicated">819</part-num-ref>
+ and displayed on the toolbar <part-num-ref name="toolbar">800</part-num-ref>
+ and in the summary report along with a timestamp and number of hits returned <part-num-ref name="timestamp and number of hits returned">820.</part-num-ref>
+ As <boundary-data type="line-number">15 </boundary-data>
+mentioned above, this embodiment is not limited to displaying abstracts of the result content and any suitable format is used, for example, the full text of each article can be displayed.    </p>
+    <p id="p-69" num="69">The results summary report 817 includes dynamic license icons <part-num-ref name="includes dynamic license icons">821</part-num-ref>
+ that precede each article <part-num-ref name="that precede each article">830</part-num-ref>
+ returned. The dynamic license icons <part-num-ref name="dynamic license icons">821</part-num-ref>
+ indicate whether the retrieved <boundary-data type="line-number">20 </boundary-data>
+article <part-num-ref name="retrieved article">830</part-num-ref>
+ is, for example, instantly licensable or not. The license icon <part-num-ref name="license icon">821</part-num-ref>
+ dynamically changes to display availability, licensability or no charge for the retrieved content.    </p>
+    <p id="p-70" num="70">However, one skilled in the art will realize that other indications, such as visual (e.g., color and text) or audio, can be used. For example, a green license icon indicates that accessed <boundary-data type="header">
+        <confidence value="88">18</confidence>
+      </boundary-data>
+      <page-break num="19"/>
+content is licensed by a user's site license, a yellow license icon indicates that the accessed content can be licensed by a user, and a red license icon indicates that the user is restricted from accessing content.    </p>
+    <p id="p-71" num="71">In general, the license icon <part-num-ref name="license icon">821</part-num-ref>
+ found in the results summary report <part-num-ref name="results summary report">817</part-num-ref>
+ will <boundary-data type="line-number">5 </boundary-data>
+include the following two major functions: notify the user that the content they are viewing is either <part-num-ref name="content they are viewing is either">(1)</part-num-ref>
+ already covered by the user's license so they can print, e-mail or display the content on their intranet or <part-num-ref name="content on their intranet or">(2)</part-num-ref>
+ instantly licensable as indicated by either a changing of the color of the dynamic license icon <part-num-ref name="dynamic license icon">821</part-num-ref>
+ or by presenting a message to the user.    </p>
+    <p id="p-72" num="72">
+      <boundary-data type="line-number">10         </boundary-data>
+More particularly, the user typically has several licensing options. These include:    </p>
+    <p id="p-73" num="73">(1) the user does not own a site license but the site provides licensable content, in which case the user can login to the site by filling out a request form and then obtain the desired content; <part-num-ref name="desired content;">(2)</part-num-ref>
+ the user has an internal site license (e.g., internal to the user's company) to access the content, and thus, the user can only use content for internal (company) needs;    </p>
+    <p id="p-74" num="74">
+      <boundary-data type="line-number">15 </boundary-data>
+and (3) the user has an internal site license to the access content, but would like to use the content for purposes not authorized pursuant to the license agreement. However, these licensing options are not exhaustive and other licensing option can be created as required.    </p>
+    <p id="p-75" num="75">In operation, software associated with the license icon <part-num-ref name="license icon">821</part-num-ref>
+ will parse through each page of each retrieved HTML source code document to verify if a tag is embedded within <boundary-data type="line-number">20 </boundary-data>
+the code. The tag is code, such as metadata or the like, that a content owner, or a subsequent aggregator or distributor or a distribution agent such as the operator of the system described herein, includes in published content, such as a published article transmitted on the World Wide Web (WWW). If the tag does appear within the page, the <boundary-data type="header">
+        <confidence value="88">19</confidence>
+      </boundary-data>
+      <page-break num="20"/>
+toolbar will assume that the article can be instantly licensable and will notify the user by, for example, changing the text or color of the license icon <part-num-ref name="license icon">821.</part-num-ref>
+    </p>
+    <p id="p-76" num="76">When viewing content that has been identified as being instantly licensable, the user will have the ability to select the license icon <part-num-ref name="license icon">821</part-num-ref>
+ and license the content. Upon <boundary-data type="line-number">5 </boundary-data>
+selecting the license icon <part-num-ref name="license icon">821,</part-num-ref>
+ the user will be directed (e.g., hyperlinked) to the content provider's site just as if they had selected the link included in the tagging of the article (Figure <part-num-ref name="article (Figure">5,</part-num-ref>
+ <part-num-ref name="article (Figure 5,">534)</part-num-ref>
+ or the toolbar license icon <part-num-ref name="toolbar license icon">835,</part-num-ref>
+ which will be discussed in greater detail later. For example, by selecting the license icon <part-num-ref name="license icon">821,</part-num-ref>
+ the appropriate web page will be displayed (i.e., the content provider's site), in which the user can proceed to license the <boundary-data type="line-number">10 </boundary-data>
+article. Again, if the user has a valid <confidence value="22222222">username</confidence>
+ and password stored in the registry, the user will automatically be logged-in at the content provider's site to continue the license process.    </p>
+    <p id="p-77" num="77">Figure 9A illustrates a content provider functionality of digital content licensing toolbar <part-num-ref name="content provider functionality of digital content licensing toolbar">900.</part-num-ref>
+ A content provider icon <part-num-ref name="content provider icon">910</part-num-ref>
+ is provided on the toolbar <part-num-ref name="toolbar">900.</part-num-ref>
+ By selecting the <boundary-data type="line-number">15 </boundary-data>
+content provider icon <part-num-ref name="content provider icon">910,</part-num-ref>
+ a user can choose from a list of content providers <part-num-ref name="list of content providers">920.</part-num-ref>
+ Content providers can be selected from either an alphabetical list <part-num-ref name="alphabetical list">930</part-num-ref>
+ or by industry <part-num-ref name="or by industry">940.</part-num-ref>
+ For example, if a content provider, such as REUTERS <part-num-ref name="content provider, such as REUTERS">950,</part-num-ref>
+ is selected from the alphabetical list <part-num-ref name="alphabetical list">930,</part-num-ref>
+ the REUTERS' homepage is displayed in the document window <part-num-ref name="document window">960</part-num-ref>
+ of the graphical user interface <part-num-ref name="graphical user interface">970.</part-num-ref>
+    </p>
+    <p id="p-78" num="78">
+      <boundary-data type="line-number">20         </boundary-data>
+At this point, the user can select an article from the REUTERS homepage. After the article is selected, the toolbar license icon <part-num-ref name="toolbar license icon">980</part-num-ref>
+ indicates whether the selected article <part-num-ref name="selected article">830</part-num-ref>
+ is, for example, instantly licensable or not. If the content is instantly licensable, the license icon <part-num-ref name="license icon">980</part-num-ref>
+ will indicate such availability with appropriate text or color message such <boundary-data type="header">
+        <confidence value="88">20</confidence>
+      </boundary-data>
+      <page-break num="21"/>
+as "Use This Article." If the content is not instantly licensable, the license icon <part-num-ref name="license icon">980</part-num-ref>
+ will indicate this status with appropriate text or color message such as "Attempt to License." Hence, the license icon <part-num-ref name="license icon">980</part-num-ref>
+ dynamically changes to display availability, licensability or no charge for the retrieved article. However, one skilled in the art will realize that other <boundary-data type="line-number">5 </boundary-data>
+indications, such as visual (e.g., color), audio or other forms of text, can be used.    </p>
+    <p id="p-79" num="79">In operation, software associated with the toolbar license icon <part-num-ref name="toolbar license icon">980</part-num-ref>
+ will parse through the selected page of the retrieved HTML source code document (i.e., the selected article) to verify if a tag is embedded within the code. The tag is code, such as metadata or the like, is included by the content owner in the published content, such as a published <boundary-data type="line-number">10 </boundary-data>
+article transmitted on the World Wide Web (WWW). If a tag appears within the page, the toolbar will assume that the article can be instantly licensable and will notify the user by, for example, changing the color of the license icon <part-num-ref name="license icon">980.</part-num-ref>
+ However, one skilled in the art will realize that other indications, such as audio or text, can be used. For example, the license icon <part-num-ref name="license icon">980</part-num-ref>
+ can dynamically change, displaying a message indicating the licensing <boundary-data type="line-number">15 </boundary-data>
+status of the selected article.    </p>
+    <p id="p-80" num="80">Figure 9B illustrates additional content provider functionality of digital content licensing toolbar 900. As discussed above, a content provider can be selected from either an alphabetical list <part-num-ref name="alphabetical list">930</part-num-ref>
+ or by industry <part-num-ref name="or by industry">940.</part-num-ref>
+ The industry type can be separated into multiple menu items. In this embodiment industry type is separated into Industry Type <part-num-ref name="industry type can be separated into multiple menu items. In this embodiment industry type is separated into Industry Type">1</part-num-ref>
+ <boundary-data type="line-number">20 </boundary-data>
+      <part-num-ref name="">(941)</part-num-ref>
+ and Industry Type <part-num-ref name="and Industry Type">2</part-num-ref>
+ (942). If a content provider, such as WIRELESS REVIEW <part-num-ref name="content provider, such as WIRELESS REVIEW">985</part-num-ref>
+ is selected, the WIRELESS REVIEW homepage is displayed in the document window <part-num-ref name="document window">960</part-num-ref>
+ of the graphical user interface <part-num-ref name="graphical user interface">970.</part-num-ref>
+    </p>
+    <boundary-data type="header">
+      <confidence value="88">21</confidence>
+    </boundary-data>
+    <p id="p-81" num="81">
+      <page-break num="22"/>
+At this point, the user can select an article from the homepage of WIRELESS REVIEW. After the article is selected, the toolbar license icon <part-num-ref name="toolbar license icon">980</part-num-ref>
+ indicates whether the selected article <part-num-ref name="selected article">985</part-num-ref>
+ is, for example, instantly licensable or not. The license icon <part-num-ref name="license icon">980</part-num-ref>
+ dynamically changes to display availability, licensability or no charge for the retrieved <boundary-data type="line-number">5 </boundary-data>
+article. However, one skilled in the art will realize that other indications, such as visual (e.g., color), audio or text, can be used.    </p>
+    <p id="p-82" num="82">The various embodiments described above are provided by way of illustration only and should not be construed to limit the invention. Those skilled in the art will readily recognize various modifications and changes that may be made to the present invention <boundary-data type="line-number">10 </boundary-data>
+without following the example embodiments and applications illustrated and described herein, and without departing from the true spirit and scope of the present invention, which is set forth in the following claims.    </p>
+    <boundary-data type="header">
+      <confidence value="88">22</confidence>
+    </boundary-data>
+  </description>
+</us-patent-application>
+

prior_art/10953746.xml

@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>10953746</doc-number>
+        <date>2008-09-29</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <heading id="h-1">AMENDMENT TO THE SPECIFICATION</heading>
+    <p id="p-1" num="1">Please delete Paragraph [0038].</p>
+    <p id="p-2" num="2">Please amend Paragraph [0096] with the following amended paragraph:</p>
+    <p id="p-3" num="3">
+      <confidence value="455566266266">InFIG-1-8-he</confidence>
+ The user can search and browse a variety of lists sorted in various ways.    </p>
+    <p id="p-4" num="4">Once delivered, users see their programmed delivery selections, which will automatically continue to deliver content, in a listing in the text box, indicating, in parentheses, the number of content selections included <part-num-ref name="number of content selections included">1501</part-num-ref>
+ (see FIG. 15). Users can vary the periodicity and length of the programmed content ordered by toggling easy-to-use buttons<confidence value="684">-16</confidence>
+06.    </p>
+    <p id="p-5" num="5">Please amend Paragraph [0097] with the following amended paragraph:</p>
+    <p id="p-6" num="6">FIG<confidence value="288">-18</confidence>
+ also des<confidence value="77">cr</confidence>
+ibes In the process of programmed media delivery<confidence value="665">-in</confidence>
+-detai<confidence value="4">l</confidence>
+ <confidence value="688">the</confidence>
+ <confidence value="6888">-The</confidence>
+ network updates a list of available programmed content channels on the device. The user selects from available programmed content channels displayed on the portable device, (e.g., "workout mix," "comedy") specifying frequency of update and number of content files to be delivered per update. Upon the next connection to the network, the device provides this information to the network, which is stored in the subscriber data database.    </p>
+    <p id="p-7" num="7">
+      <confidence value="8">2</confidence>
+     </p>
+  </description>
+</us-patent-application>
+

prior_art/10985630.xml

@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>10985630</doc-number>
+        <date>2005-11-18</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <heading id="h-1">AMENDMENTS TO THE SPECIFICATION</heading>
+    <p id="p-1" num="1">In the title:</p>
+    <p id="p-2" num="2">Please change title to "HIGHLIGHTING ITEMS FOR SEARCH RESULTS" Case 9317 (P3477)              -<confidence value="88">2-</confidence>
+     </p>
+  </description>
+</us-patent-application>
+

prior_art/11048210.xml

@@ -0,0 +1,592 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" file="US20060173961A1-20060803.XML" status="PRODUCTION" id="us-patent-application" country="US" date-produced="20060720" date-publ="20060803">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11048210</doc-number>
+        <date>20050201</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <drawings id="DRAWINGS">
+    <figure id="figure-D00000" num="00000">
+      <img id="EMI-D00000" he="70.87mm" wi="150.69mm" file="US20060173961A1-20060803-D00000.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00001" num="00001">
+      <img id="EMI-D00001" he="198.29mm" wi="151.55mm" file="US20060173961A1-20060803-D00001.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00002" num="00002">
+      <img id="EMI-D00002" he="234.44mm" wi="176.02mm" file="US20060173961A1-20060803-D00002.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00003" num="00003">
+      <img id="EMI-D00003" he="174.24mm" wi="158.83mm" file="US20060173961A1-20060803-D00003.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00004" num="00004">
+      <img id="EMI-D00004" he="186.94mm" wi="166.88mm" file="US20060173961A1-20060803-D00004.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00005" num="00005">
+      <img id="EMI-D00005" he="205.66mm" wi="164.76mm" file="US20060173961A1-20060803-D00005.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00006" num="00006">
+      <img id="EMI-D00006" he="242.49mm" wi="188.47mm" file="US20060173961A1-20060803-D00006.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00007" num="00007">
+      <img id="EMI-D00007" he="215.48mm" wi="168.40mm" file="US20060173961A1-20060803-D00007.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00008" num="00008">
+      <img id="EMI-D00008" he="235.97mm" wi="203.12mm" file="US20060173961A1-20060803-D00008.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00009" num="00009">
+      <img id="EMI-D00009" he="229.87mm" wi="202.44mm" file="US20060173961A1-20060803-D00009.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00010" num="00010">
+      <img id="EMI-D00010" he="243.59mm" wi="185.50mm" file="US20060173961A1-20060803-D00010.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00011" num="00011">
+      <img id="EMI-D00011" he="218.44mm" wi="185.25mm" file="US20060173961A1-20060803-D00011.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00012" num="00012">
+      <img id="EMI-D00012" he="241.89mm" wi="189.23mm" file="US20060173961A1-20060803-D00012.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00013" num="00013">
+      <img id="EMI-D00013" he="230.46mm" wi="191.35mm" file="US20060173961A1-20060803-D00013.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00014" num="00014">
+      <img id="EMI-D00014" he="226.06mm" wi="185.17mm" file="US20060173961A1-20060803-D00014.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00015" num="00015">
+      <img id="EMI-D00015" he="234.44mm" wi="198.29mm" file="US20060173961A1-20060803-D00015.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00016" num="00016">
+      <img id="EMI-D00016" he="236.64mm" wi="188.81mm" file="US20060173961A1-20060803-D00016.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00017" num="00017">
+      <img id="EMI-D00017" he="234.10mm" wi="185.17mm" file="US20060173961A1-20060803-D00017.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00018" num="00018">
+      <img id="EMI-D00018" he="246.30mm" wi="195.50mm" file="US20060173961A1-20060803-D00018.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00019" num="00019">
+      <img id="EMI-D00019" he="231.65mm" wi="191.77mm" file="US20060173961A1-20060803-D00019.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00020" num="00020">
+      <img id="EMI-D00020" he="241.81mm" wi="198.37mm" file="US20060173961A1-20060803-D00020.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00021" num="00021">
+      <img id="EMI-D00021" he="231.99mm" wi="191.09mm" file="US20060173961A1-20060803-D00021.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00022" num="00022">
+      <img id="EMI-D00022" he="225.72mm" wi="195.75mm" file="US20060173961A1-20060803-D00022.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00023" num="00023">
+      <img id="EMI-D00023" he="228.01mm" wi="194.39mm" file="US20060173961A1-20060803-D00023.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00024" num="00024">
+      <img id="EMI-D00024" he="225.47mm" wi="191.43mm" file="US20060173961A1-20060803-D00024.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00025" num="00025">
+      <img id="EMI-D00025" he="227.33mm" wi="198.04mm" file="US20060173961A1-20060803-D00025.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00026" num="00026">
+      <img id="EMI-D00026" he="218.10mm" wi="196.85mm" file="US20060173961A1-20060803-D00026.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00027" num="00027">
+      <img id="EMI-D00027" he="231.65mm" wi="184.83mm" file="US20060173961A1-20060803-D00027.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00028" num="00028">
+      <img id="EMI-D00028" he="231.31mm" wi="179.32mm" file="US20060173961A1-20060803-D00028.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00029" num="00029">
+      <img id="EMI-D00029" he="229.45mm" wi="153.42mm" file="US20060173961A1-20060803-D00029.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+    <figure id="figure-D00030" num="00030">
+      <img id="EMI-D00030" he="239.95mm" wi="203.03mm" file="US20060173961A1-20060803-D00030.TIF" alt="embedded image" img-content="drawing" img-format="tif"/>
+    </figure>
+  </drawings>
+  <description id="description">
+    <information level="warning">Multiple SPEC documents exist in this application.  The text data below may not be the most current text of the specification.</information>
+    <?summary-of-invention description="Summary of Invention" end="lead"?>
+    <heading level="2" id="h-0001">TECHNICAL FIELD </heading>
+    <p id="p-0002" num="0001"> The subject invention relates generally to email organization and in particular, to classifying and organizing a message store by people involved in the communication to facilitate navigating through and viewing communications related by sender and recipient(s) and subject matter. </p>
+    <heading level="2" id="h-0002">BACKGROUND OF THE INVENTION </heading>
+    <p id="p-0003" num="0002"> As the volume of information exchanged electronically grows, so does the need to organize it in a way that facilitates storage and future retrieval. Communication clients, particularly email clients, have become a repository of valuable data. Productivity of knowledge workers depends on the ability to find a requested piece of information that very often has arrived as an email or attachment. </p>
+    <p id="p-0004" num="0003"> The traditional way to organize email data uses a folder hierarchy, similar to the folder hierarchy of conventional file systems. In theory, the folder hierarchy is the ultimate classification&#x2014;being completely user defined, it has the potential to be the best representation of user intentions. Unfortunately, it does not always work so well in practice. </p>
+    <p id="p-0005" num="0004"> The main problem with the folder classification system is that it does require an explicit user action, whether it is filing the message in the appropriate folder, or creating a rule to do so automatically. With the current volume of email communication, the job quickly becomes a chore that few users can maintain. Some user surveys have shown that many users simply give up on folder classification, keeping all or most of their incoming messages in the inbox and finding requested items by sorting and searching. </p>
+    <p id="p-0006" num="0005"> Even for those users who do file all the mail items on a regular basis, the folder system does not often work as well as expected. The problem is the discrepancy between the dynamic nature of interpersonal contacts and the static folder structure. Even the best designed folder hierarchy (and few real users are experts in the taxonomy necessary to create the &#x201c;best&#x201d; hierarchy,) becomes partially obsolete after a period and should be redesigned. However, the labor cost of re-classifying all the items, especially those in the archives, is very high and usually not justified by the added benefit of the new organization. Some users complained that in the end, the obsolete folder structure often becomes an obstacle rather then an advantage, as the user does not always remember where the item was placed. </p>
+    <p id="p-0007" num="0006"> There have been many attempts to organize email communications automatically. Many email clients allow creating automatic rules to move new messages into appropriate folders, but automatic removal of new messages from inbox also removes them from user focus. </p>
+    <p id="p-0008" num="0007"> Another approach is to use standing queries. For example, a query may look for all mail items involving a given person as a sender or recipient. Standing queries allow grouping messages without taking them out of the inbox. Some authors proposed a predefined set of standing queries that can be used to organize the inbox. However, the drawback of a predefined set is in the limited number of categories: it does not scale well when the number of contacts grow. </p>
+    <heading level="2" id="h-0003">SUMMARY OF THE INVENTION </heading>
+    <p id="p-0009" num="0008"> The following presents a simplified summary of the invention in order to provide a basic understanding of some aspects of the invention. This summary is not an extensive overview of the invention. It is not intended to identify key/critical elements of the invention or to delineate the scope of the invention. Its sole purpose is to present some concepts of the invention in a simplified form, as a prelude to the more detailed description that is presented later. </p>
+    <p id="p-0010" num="0009"> The subject invention relates to a system and/or methodology that facilitate organizing, viewing and navigating through a message store in a people-based manner. In particular, the invention organizes the message data according to the sender or other contact associated with the data. In lieu of a traditional folder hierarchy list, a dynamic contact list can be employed. The contact list can comprise multiple tiers, whereby at the top tier or level of the list, the most frequently used contacts are shown. All other contacts are still accessible, but viewing them requires progressively more clicks depending on their respective tier location. </p>
+    <p id="p-0011" num="0010"> Determining which tier or level a contact is placed can be accomplished by at least two different approaches. In the first approach, the system and/or method can ascertain which contacts communicate most often with the user. When the frequency of communications satisfies a particular level's threshold, the contact name can be placed or kept at that level. The second approach involves user selection. More specifically, the user can expand the list to view other levels and then select a contact in a lower level. When the list is collapsed, the selected contact can be seen in the top level. </p>
+    <p id="p-0012" num="0011"> As previously mentioned, the contact list is dynamic; thus it can be continually updated. For some users, this can create disorientation and even a loss of control. To maintain some order with respect to the list, all contacts can be ordered alphabetically (e.g., by first name). Hence, a contact's name can be readily accessible to the user and easily found despite the dynamic nature of the contact list. </p>
+    <p id="p-0013" num="0012"> According to one aspect of the invention, messages can be automatically clustered based on the group or person who sent the message. For example, when a user wants to view messages from a particular person or group, the user can click on their name from the contact list. In an adjoining window on the display, messages between the user and the selected contact can be displayed. The messages can be organized in a conversation mode or in any other list mode (with or without a preview pane) as desired by the user. </p>
+    <p id="p-0014" num="0013"> In another aspect of the invention, messages can also be organized and viewed according to any other group or individuals included as recipients of the message (e.g., on the &#x201c;To:&#x201d;, &#x201c;cc:&#x201d;, or &#x201c;bcc:&#x201d; lines). When this option is selected, any message involving the user and the selected contact in addition to any other person or group can be shown. As can be imagined, this view often increases the number of messages available for viewing. </p>
+    <p id="p-0015" num="0014"> Yet another aspect of the invention facilitates more efficient organization of information shared between people. The information can be either in the form of attachments or as indirect links such as hyperlinks and calendar entries. In particular, the system and method can expose any shared items into a direct view. A virtual shared space that is populated with all the items shared with the user by email from a person or group can be created. When any one item is highlighted by the user, the corresponding message can be displayed in an adjoining window. </p>
+    <p id="p-0016" num="0015"> The shared space can also include a browser or view filter that allows the user to see the shared items by various groups such as type, sender, date, and/or folder, for example. Users can also further specify which items to view by employing a combination of such groups. For example, instead of looking at all web pages, the user may desire to see only the web pages shared with (or by) Jim Jones in the last 10 days. Furthermore, a preview of each shared item can be available to provide additional context with respect to the particular item and the associated message. </p>
+    <p id="p-0017" num="0016"> To the accomplishment of the foregoing and related ends, certain illustrative aspects of the invention are described herein in connection with the following description and the annexed drawings. These aspects are indicative, however, of but a few of the various ways in which the principles of the invention may be employed and the subject invention is intended to include all such aspects and their equivalents. Other advantages and novel features of the invention may become apparent from the following detailed description of the invention when considered in conjunction with the drawings.</p>
+    <?summary-of-invention description="Summary of Invention" end="tail"?>
+    <?brief-description-of-drawings description="Brief Description of Drawings" end="lead"?>
+    <heading level="2" id="h-0004">BRIEF DESCRIPTION OF THE DRAWINGS </heading>
+    <p id="p-0018" num="0017">
+      <figref idref="DRAWINGS">FIG. 1</figref>
+ is a high-level block diagram of a message organizational and display system in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0019" num="0018">
+      <figref idref="DRAWINGS">FIG. 2</figref>
+ is a block diagram of a message organizational and display system in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0020" num="0019">
+      <figref idref="DRAWINGS">FIG. 3</figref>
+ is a block diagram of display controls employed in a message organizational and display system in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0021" num="0020">
+      <figref idref="DRAWINGS">FIG. 4</figref>
+ is a block diagram of contact list controls employed in a message organizational and display system in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0022" num="0021">
+      <figref idref="DRAWINGS">FIG. 5</figref>
+ is a schematic diagram of an exemplary user interface employed in a message organizational and display system in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0023" num="0022">
+      <figref idref="DRAWINGS">FIG. 6</figref>
+ illustrates an exemplary user interface for a message organizational and display system in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0024" num="0023">
+      <figref idref="DRAWINGS">FIG. 7</figref>
+ is a schematic diagram of an exemplary user interface employed in a message organizational and display system after a contact has been selected in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0025" num="0024">
+      <figref idref="DRAWINGS">FIG. 8</figref>
+ illustrates an exemplary user interface for a message organizational and display system after a contact has been selected in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0026" num="0025">
+      <figref idref="DRAWINGS">FIG. 9</figref>
+ illustrates an exemplary user interface for a message organizational and display system after a view option has been selected in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0027" num="0026">
+      <figref idref="DRAWINGS">FIG. 10</figref>
+ illustrates an exemplary user interface for a message organizational and display system after multiple contacts have been selected in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0028" num="0027">
+      <figref idref="DRAWINGS">FIG. 11</figref>
+ is a schematic click-by-click diagram of navigating through a collapsible, expandable, and dynamic multi-level contact list employed in a message organizational and display system in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0029" num="0028">
+      <figref idref="DRAWINGS">FIG. 12</figref>
+ illustrates an exemplary user interface for navigating to a contact located on a lower level of a contact list that is employed in a message organizational and display system in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0030" num="0029">
+      <figref idref="DRAWINGS">FIG. 13</figref>
+ illustrates an exemplary user interface of the contact list of <figref idref="DRAWINGS">FIG. 12</figref>
+ that has been further expanded in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0031" num="0030">
+      <figref idref="DRAWINGS">FIG. 14</figref>
+ illustrates an exemplary user interface of an alternative view of a shared space employed in a message organizational and display system in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0032" num="0031">
+      <figref idref="DRAWINGS">FIG. 15</figref>
+ illustrates an exemplary user interface of an alternative view of a shared space in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0033" num="0032">
+      <figref idref="DRAWINGS">FIG. 16</figref>
+ illustrates an exemplary user interface of a collapsed contact list showing only the top level whereby a contact from a lower level has been manually added in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0034" num="0033">
+      <figref idref="DRAWINGS">FIG. 17</figref>
+ illustrates an exemplary user interface for a message organizational and display system whereby a shared item is linked to its corresponding message when highlighted in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0035" num="0034">
+      <figref idref="DRAWINGS">FIGS. 18 and 19</figref>
+ illustrate exemplary user interfaces that demonstrate the link between a highlighted item in the shared space and the corresponding message in an adjacent window in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0036" num="0035">
+      <figref idref="DRAWINGS">FIG. 20</figref>
+ illustrates an exemplary user interface for a message organizational and display system that allows a user to browse through a shared space by a folder grouping in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0037" num="0036">
+      <figref idref="DRAWINGS">FIG. 21</figref>
+ illustrates an exemplary user interface for a message organizational and display system that allows a user to browse through a shared space by a sender grouping in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0038" num="0037">
+      <figref idref="DRAWINGS">FIG. 22</figref>
+ illustrates an exemplary user interface for a message organizational and display system that allows a user to browse through a shared space by a date grouping in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0039" num="0038">
+      <figref idref="DRAWINGS">FIGS. 23-26</figref>
+ illustrate exemplary user interfaces for a message organizational and display system that allows a user to browse through a shared space by mail item type and then by one or more specific sub-groups in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0040" num="0039">
+      <figref idref="DRAWINGS">FIG. 27</figref>
+ is a flow chart illustrating an exemplary methodology that facilitates organizing a contact list that can be employed to more readily access messages from a message store based on associations with people in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0041" num="0040">
+      <figref idref="DRAWINGS">FIG. 28</figref>
+ is a flow chart illustrating an exemplary methodology that facilitates updating such contact list (<figref idref="DRAWINGS">FIG. 27</figref>
+) in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0042" num="0041">
+      <figref idref="DRAWINGS">FIG. 29</figref>
+ is a flow chart illustrating an exemplary methodology that facilitates organizing a message store based on contact associations in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0043" num="0042">
+      <figref idref="DRAWINGS">FIG. 30</figref>
+ is a flow chart illustrating an exemplary methodology that facilitates viewing and/or navigating a desired portion of a message store based on contact associations in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0044" num="0043">
+      <figref idref="DRAWINGS">FIG. 31</figref>
+ is a flow chart illustrating an exemplary methodology that facilitates viewing and/or navigating a desired portion of a message store based on contact associations in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0045" num="0044">
+      <figref idref="DRAWINGS">FIG. 32</figref>
+ illustrating an exemplary methodology that facilitates browsing shared items in accordance with an aspect of the subject invention.     </p>
+    <p id="p-0046" num="0045">
+      <figref idref="DRAWINGS">FIG. 33</figref>
+ illustrates an exemplary environment for implementing various aspects of the invention.    </p>
+    <?brief-description-of-drawings description="Brief Description of Drawings" end="tail"?>
+    <?detailed-description description="Detailed Description" end="lead"?>
+    <heading level="2" id="h-0005">DETAILED DESCRIPTION OF THE INVENTION </heading>
+    <p id="p-0047" num="0046"> The subject invention is now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the subject invention. It may be evident, however, that the subject invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate describing the subject invention. </p>
+    <p id="p-0048" num="0047"> As used in this application, the terms &#x201c;component&#x201d; and &#x201c;system&#x201d; are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and a computer. By way of illustration, both an application running on a server and the server can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. </p>
+    <p id="p-0049" num="0048"> The subject invention can incorporate various inference schemes and/or techniques in connection with determining communication frequency between a user and sender to ascertain at which level of a contact list the sender should be placed. As used herein, the term &#x201c;inference&#x201d; refers generally to the process of reasoning about or inferring states of the system, environment, and/or user from a set of observations as captured via events and/or data. Inference can be employed to identify a specific context or action, or can generate a probability distribution over states, for example. The inference can be probabilistic&#x2014;that is, the computation of a probability distribution over states of interest based on a consideration of data and events. Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data. Such inference results in the construction of new events or actions from a set of observed events and/or stored event data, whether or not the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources. </p>
+    <p id="p-0050" num="0049"> Referring now to <figref idref="DRAWINGS">FIG. 1</figref>
+, there is a high-level block diagram of a contact-based message organization and display system <part-num-ref name="display system">100</part-num-ref>
+ in accordance with an aspect of the subject invention. The system <part-num-ref name="system">100</part-num-ref>
+ includes a receiving component <part-num-ref name="receiving component">110</part-num-ref>
+ that can receive input such as in the form of messages (e.g., email). Presumably, the messages are sent from a plurality of senders (e.g., person or group) to a user. As the messages flow in to the system <part-num-ref name="system">100</part-num-ref>
+ and through the receiving component <part-num-ref name="receiving component">110</part-num-ref>
+, they can be organized by a people-based classification component <part-num-ref name="people-based classification component">120</part-num-ref>
+. Unlike a traditional folder arrangement, the people-based classification component <part-num-ref name="people-based classification component">120</part-num-ref>
+ can automatically sort and organize messages according to at least the sender. When a particular sender is selected from a list of senders, the corresponding messages between the sender and the user (e.g., any communication exchanged between the user and sender) can be shown on a multi-view display component <part-num-ref name="multi-view display component">130</part-num-ref>
+. The display component <part-num-ref name="display component">130</part-num-ref>
+ provides many different viewing options depending on the user's viewing preferences.     </p>
+    <p id="p-0051" num="0050"> Though not depicted in the figure, the user can also have the option to view his/her messages such as in a general inbox. The traditional inbox containing often hundreds or thousands of messages can be overwhelming. For most users of email systems, the primary purpose of the inbox view is to indicate what's new, so that important messages can be reacted to in a timely manner. Including older messages in the same view actually gets into way, (e.g., by obscuring the unread messages count). If the message remains unread after a few days, then it was probably unimportant or the user became aware of its content from another source. Therefore, such messages should be removed from the view so that other incoming ones may get proper attention. </p>
+    <p id="p-0052" num="0051"> To support this functionality, the subject invention provides for a modified inbox view (and the view of other message flow folders, such as Sent Items and Drafts) that employs an auto-archiving component. Most if not all messages older then a few days (e.g., 3 days for Inbox&#x2014;the number can be adjusted by the user) can be automatically removed from the view. All archived messages can still be found through the search or by browsing the list of senders (contacts). The user also has an option to keep any message in the Inbox view indefinitely by marking it with a &#x201c;follow up&#x201d; flag or some other symbol or notation. </p>
+    <p id="p-0053" num="0052"> Referring now to <figref idref="DRAWINGS">FIG. 2</figref>
+, there is illustrated a block diagram of a message organization and display system <part-num-ref name="display system">200</part-num-ref>
+ that facilitates a people-centric association of messages. The system <part-num-ref name="system">200</part-num-ref>
+ includes a contact analysis component <part-num-ref name="contact analysis component">210</part-num-ref>
+. Upon receipt of incoming messages (<part-num-ref name="Upon receipt of incoming messages (">220</part-num-ref>
+) from various group or individual contacts, the contact analysis component <part-num-ref name="contact analysis component">210</part-num-ref>
+ can examine the message to identify the sender as well as any other group or person included as a recipient of the message.     </p>
+    <p id="p-0054" num="0053"> The identified sender can be communicated to a dynamic contact list <part-num-ref name="dynamic contact list">230</part-num-ref>
+, and in particular, to a contact order component <part-num-ref name="contact order component">240</part-num-ref>
+. The contact order component <part-num-ref name="contact order component">240</part-num-ref>
+ can perform at least two operations: add a new sender to the list in alphabetical order with respect to other names already present; and determine the frequency at which communications are exchanged between the user and the sender. The resulting frequency can affect on which level of importance the sender's name is placed. The level of importance or communication frequency can be measured by looking at the communication activity over the last 30 days, for example. To compensate for spam messages, the activity can be weighted toward the messages sent to the contact (from the user).     </p>
+    <p id="p-0055" num="0054"> In general, the dynamic contact list uses the ranking information (e.g., importance determination) to select which names are shown first or on the top level, but orders the names alphabetically to make searching for a specific name easier and to avoid any suggestions about an individual's relative importance. The list can be selectively expanded bringing more names into view but can always hold to the strict alphabetic ordering. </p>
+    <p id="p-0056" num="0055"> The dynamic contact list <part-num-ref name="dynamic contact list">230</part-num-ref>
+ can be controlled or navigated through in part by a contact list zoom control <part-num-ref name="contact list zoom control">250</part-num-ref>
+ (e.g., see <figref idref="DRAWINGS">FIG. 11</figref>
+, infra, for further discussion). The zoom control <part-num-ref name="zoom control">250</part-num-ref>
+ can be employed to expand and collapse various portions of the contact list <part-num-ref name="contact list">230</part-num-ref>
+ in order to locate particular names on the list and/or to visualize other names that either appear before or after any desired name. Recall that the dynamic contact list can rank contacts according to multiple levels of importance, whereby the top level can remain in view by default and the other lower levels can be folded in or collapsed. The zoom control <part-num-ref name="zoom control">250</part-num-ref>
+ facilitates viewing the lower levels in a progressive manner. For example, getting to a contact on a bottom level (e.g., level 3 out of 3) may require additional clicks whereas a contact on the second level may require less.     </p>
+    <p id="p-0057" num="0056"> To view messages from at least one contact from the list, the user can make a contact selection <part-num-ref name="contact selection">260</part-num-ref>
+ such as by checking a box next to the contact. Almost immediately thereafter, a selection based message viewer <part-num-ref name="selection based message viewer">270</part-num-ref>
+ can display any communications exchanged between the user and the selected contact (in a separate window). The communications can be sorted or viewed in alternative modes (e.g., list view, conversation view, etc.) via a message browse control <part-num-ref name="message browse control">280</part-num-ref>
+.     </p>
+    <p id="p-0058" num="0057"> Furthermore, any attachments or hyperlinks included in any of the communications can be displayed in a separate window by way of a shared space viewer <part-num-ref name="shared space viewer">290</part-num-ref>
+. Thus, the user can easily see all the information that was &#x201c;shared&#x201d; via the message system <part-num-ref name="message system">200</part-num-ref>
+.     </p>
+    <p id="p-0059" num="0058"> Turning now to <figref idref="DRAWINGS">FIG. 3</figref>
+, there is illustrated various display controls that can be employed in a message organizational and display system (e.g., FIGS. <part-num-ref name="display system (e.g., FIGS.">1</part-num-ref>
+ and/or <part-num-ref name="and/or">2</part-num-ref>
+, supra) in accordance with an aspect of the invention. For instance, a message viewer <part-num-ref name="message viewer">300</part-num-ref>
+ can display messages associated with selected groups or individuals as a conversation view (by conversation viewer <part-num-ref name="conversation view (by conversation viewer">310</part-num-ref>
+). In the conversation view, portions of each message can be seen in a chronological order to facilitate viewing related groups of communications within the context of the subject matter discussed therein. Thus, a message from the sender can be followed by a response by the user, which can then be followed with a response by the sender, and so on. To view any message in greater detail, the user can simply open it into another window (e.g., by clicking on the message).     </p>
+    <p id="p-0060" num="0059"> Alternatively, a more compressed list view of each message can be displayed (by a list viewer <part-num-ref name="list viewer">320</part-num-ref>
+). The list view may allow for more messages to be displayed particularly when given a limited amount of screen space. As with the whole message store, the messages displayed at any time by the message viewer <part-num-ref name="message viewer">300</part-num-ref>
+ can be searched via a search component <part-num-ref name="search component">330</part-num-ref>
+. The results of such a search can be searched again if desired (e.g., nested search).     </p>
+    <p id="p-0061" num="0060"> Linked to the message viewer <part-num-ref name="message viewer">300</part-num-ref>
+ is a shared space viewer <part-num-ref name="shared space viewer">340</part-num-ref>
+. The shared space viewer can display any and all shared items that were sent with or included in the messages currently being shown by the message viewer. The shared space viewer <part-num-ref name="shared space viewer">340</part-num-ref>
+ can also include a browse control <part-num-ref name="browse control">350</part-num-ref>
+ to allow a user to sort or browse the shared items according to the shared items' metadata. For example, the shared items can be grouped by type, sender, date, and folder. A previewer <part-num-ref name="previewer">360</part-num-ref>
+ can also be included in the shared space viewer <part-num-ref name="shared space viewer">340</part-num-ref>
+. The previewer <part-num-ref name="previewer">360</part-num-ref>
+ can provide a thumbnail or other snapshot of the content of the shared item. Thus, if the item is a hyperlink, the previewer <part-num-ref name="previewer">360</part-num-ref>
+ can provide a snapshot of the corresponding document or web page.     </p>
+    <p id="p-0062" num="0061"> Because the message viewer <part-num-ref name="message viewer">300</part-num-ref>
+ and the shared space viewer <part-num-ref name="shared space viewer">340</part-num-ref>
+ are linked, items in the shared space can change as the contacts selected for message viewing by the message viewer <part-num-ref name="message viewer">300</part-num-ref>
+ change. For instance, imagine that the user has selected to see communications associated with Mary Smith. Any communications between the user and Mary Smith can be viewed in another window by the message viewer <part-num-ref name="message viewer">300</part-num-ref>
+. Likewise, there are 5 spreadsheets associated with those communications which can be viewed by the shared space viewer <part-num-ref name="shared space viewer">340</part-num-ref>
+. However, when the user de-selects Mary Smith and selects Joe Wright, a new set of messages will appear, as well as different shared items, if any.     </p>
+    <p id="p-0063" num="0062"> Furthermore, when the user highlights or hovers over a particular shared item, the corresponding message can be shown in the relevant window by the message viewer <part-num-ref name="message viewer">300</part-num-ref>
+. For example, suppose the corresponding message was off the screen, requiring the user to scroll down to it in order to see it. When the shared item belonging to that message is highlighted or hovered over, the message viewer can automatically bring that message up (or scroll to the message) into the viewable screen space. It should be appreciated that the message still remains in order according to specified sorting (e.g., chronological by date).     </p>
+    <p id="p-0064" num="0063"> Referring now to <figref idref="DRAWINGS">FIG. 4</figref>
+, there is illustrated a block diagram of a contact list control that can be employed in a message organizational and display system in accordance with an aspect of the invention. In particular, the control works cooperatively with a multi-level contact list <part-num-ref name="multi-level contact list">400</part-num-ref>
+ and can be characterized as a search component <part-num-ref name="search component">410</part-num-ref>
+. The search component <part-num-ref name="search component">410</part-num-ref>
+ can includes a suggestion component <part-num-ref name="suggestion component">420</part-num-ref>
+ that can match the first few letters of a name (input) communicated to the search component <part-num-ref name="search component">410</part-num-ref>
+ and expand the contact list <part-num-ref name="contact list">400</part-num-ref>
+ to highlight a potential match. The expanded contact list can be shown on a contact list display <part-num-ref name="contact list display">430</part-num-ref>
+.     </p>
+    <p id="p-0065" num="0064"> Turning now to <figref idref="DRAWINGS">FIG. 5</figref>
+, there is illustrated a schematic diagram of a user interface <part-num-ref name="user interface">500</part-num-ref>
+ for a message organization and display system in accordance with an aspect of the subject invention. The user interface <part-num-ref name="user interface">500</part-num-ref>
+ can include identification of the user <part-num-ref name="user">510</part-num-ref>
+ or mailbox owner and a list of contacts <part-num-ref name="list of contacts">520</part-num-ref>
+ associated with the user <part-num-ref name="user">510</part-num-ref>
+. The list of contacts includes any group or person that has sent or received a communication to or from the user, respectively. Communications can include emails, notifications, meeting invitations, transferred files, and the like.     </p>
+    <p id="p-0066" num="0065"> The user interface can also display the user's messages in a general inbox view <part-num-ref name="general inbox view">530</part-num-ref>
+. New messages as well as messages received in the last few days (e.g., configurable by the user) can be displayed in the general inbox view <part-num-ref name="general inbox view">530</part-num-ref>
+ (<part-num-ref name="(">540</part-num-ref>
+). Important messages that are not &#x201c;new&#x201d; but that may require additional action can be flagged by the user and moved to a different portion of the inbox (<part-num-ref name="inbox (">550</part-num-ref>
+). These messages can be &#x201c;stored&#x201d; there and may not be subject to an auto-archiving operation. Any other message that has been sitting in the inbox for P days (e.g., 3-5 days) can be auto-archived. Thus, they are removed from the general inbox but are stored and readily accessible via the contact list. As an alternative, the entire message store can also be searched.     </p>
+    <p id="p-0067" num="0066">
+      <figref idref="DRAWINGS">FIG. 6</figref>
+ demonstrates an exemplary user interface <part-num-ref name="demonstrates an exemplary user interface">600</part-num-ref>
+ illustrating various aspects of the subject invention including those described in <figref idref="DRAWINGS">FIG. 5</figref>
+, supra. The user interface <part-num-ref name="user interface">600</part-num-ref>
+ displays the user's inbox <part-num-ref name="user's inbox">610</part-num-ref>
+ having recent items from the last 3 days sorted according to the flag status of the messages. The precise number of days can vary depending on user preferences. Flagged messages <part-num-ref name="precise number of days can vary depending on user preferences. Flagged messages">620</part-num-ref>
+ are located on top to keep the user aware that additional attention is required for such messages. Unflagged messages <part-num-ref name="user aware that additional attention is required for such messages. Unflagged messages">630</part-num-ref>
+ can be listed below in chronological or some other order (e.g., sender, subject, received date, size, etc.).     </p>
+    <p id="p-0068" num="0067"> In the People/Groups section of the user interface <part-num-ref name="user interface">600</part-num-ref>
+, the user <part-num-ref name="user">640</part-num-ref>
+ is identified. Below the user <part-num-ref name="user">640</part-num-ref>
+ is a top-level view of a dynamic contact list <part-num-ref name="dynamic contact list">650</part-num-ref>
+. The contact list design represented in the figure is to show, initially, a list of the most significant contacts ordered alphabetically (e.g., top level). This offers one-step access to the most frequently used names. At the same time, all other names can be accessed by expanding the sections of the list between the top-level entries. The less significant names may require two or more subsequent expansions, but ultimately every name can be readily accessed through the same list control.     </p>
+    <p id="p-0069" num="0068"> At any given time, all the contacts are presented to the user as a single, flat, alphabetically-ordered list, but with some sections folded in (e.g., as indicated by the down-arrows by each contact). The position of each name is fully predictable, as even the hidden entries obey the same alphabetic ordering. Over time, if there are changes to the relative ordering (as determined by an importance algorithm), some other contacts may come up to the top level, but the overall order of all names on the list remains uniform. </p>
+    <p id="p-0070" num="0069"> The notion of using existing entries, such as individual contacts, as catalog indices (visible at the top level) is not new. In fact, this is the standard way to organize printed dictionaries. However, in the standard dictionary approach, indices are put at the beginning and end of every page to indicate the content of that page. This can be described as a &#x201c;constant distance&#x201d; between consecutive indices. The words chosen for indices are not particular in any way, they just happen to be at the beginning or end of the page. </p>
+    <p id="p-0071" num="0070"> In this invention's approach, the names chosen for indices are those that are on the top of our non-arbitrary &#x201c;importance&#x201d; list. Using the dictionary analogy, these would be the words that are most frequently looked up. Moreover, these names are entries by themselves&#x2014;clicking on any name selects it. This contrasts favorably against the standard alphabetic index, where getting to any entry is at least a two-step process. </p>
+    <p id="p-0072" num="0071"> Grouping all the contacts into several tiers or levels resembles a hierarchy. Displaying a true hierarchy for a set of people (e.g., in a form of a tree view with extra indentation for each level) could be perceived negatively if it does not align with traditional business organizational structures. To avoid any such connotation, the expanded names coming into view can be shown as peers to the top level ones. However, a navigational side bar can also be employed where the tiers are color-coded. The tiers are not hidden but instead, a visual representation that can best emphasize their utilitarian character can be sought (e.g., see <figref idref="DRAWINGS">FIGS. 12 and 13</figref>
+ for illustration of color-coded tiers).     </p>
+    <p id="p-0073" num="0072"> When looking for less frequently accessed names, the expansion is required only to some selected areas of the list. The total number of names visible on the list can be very limited, typically just in the tens. This allows for the effective use of screen real estate. </p>
+    <p id="p-0074" num="0073"> The user interface <part-num-ref name="user interface">600</part-num-ref>
+ can also include search operations that can search all messages or communications (<part-num-ref name="communications (">660</part-num-ref>
+). Search results can be further searched as well (<part-num-ref name="). Search results can be further searched as well (">670</part-num-ref>
+).     </p>
+    <p id="p-0075" num="0074"> Referring now to <figref idref="DRAWINGS">FIG. 7</figref>
+, there is illustrated a schematic diagram of a user interface <part-num-ref name="user interface">700</part-num-ref>
+ following the selection of a contact (Contact AB) from the contact list <part-num-ref name="contact list">710</part-num-ref>
+. By selecting Contact AB, the general inbox view <part-num-ref name="general inbox view">530</part-num-ref>
+ (<figref idref="DRAWINGS">FIG. 5</figref>
+) is replaced by a message window <part-num-ref name="message window">720</part-num-ref>
+ that includes all communications between only the user <part-num-ref name="user">730</part-num-ref>
+ and the selected contact (Contact AB). To clearly identify the content of the message window <part-num-ref name="message window">720</part-num-ref>
+, the parties associated with the communications shown in the message window can be listed at the top of the window (<part-num-ref name="window (">740</part-num-ref>
+). Information <part-num-ref name="). Information">750</part-num-ref>
+ about the selected contact can also be included in the window <part-num-ref name="window">720</part-num-ref>
+ or elsewhere on the display. The information <part-num-ref name="information">750</part-num-ref>
+ can include the person or group's email alias, email address, phone number, address, etc.     </p>
+    <p id="p-0076" num="0075"> Messages and/or any communications between the user and selected contact can be viewed in a conversation mode. In addition, any information shared in the communications such as attachments, hyperlinks, and the like can be displayed in a space designated for shared items <part-num-ref name="space designated for shared items">760</part-num-ref>
+.     </p>
+    <p id="p-0077" num="0076"> In <figref idref="DRAWINGS">FIG. 8</figref>
+, an exemplary user interface <part-num-ref name="an exemplary user interface">800</part-num-ref>
+ that reflects the diagram of <figref idref="DRAWINGS">FIG. 7</figref>
+ is depicted. As can be seen in the contact list <part-num-ref name="contact list">810</part-num-ref>
+, &#x201c;Shelly Farnham&#x201d; has been selected by the user &#x201c;Andrzej Turski&#x201d;. Thus, the general inbox view has been replaced with a person/group view of all communications between Shelly and Andrzej only.     </p>
+    <p id="p-0078" num="0077"> By selecting at least one contact from the list <part-num-ref name="list">810</part-num-ref>
+, the user can focus on a specific person. A group of people can be chosen either by selecting a people list entry that represents a group (i.e., email distribution list) or by marking multiple checkboxes on the list. Clicking directly on the entry name selects that entry only (clearing all other checkboxes). However, clicking in the checkbox area allows turning checkboxes on and off and creating an ad hoc group. The precise operation of selecting the checkboxes and entry names can vary depending user option selections.     </p>
+    <p id="p-0079" num="0078"> For the selected person (or the last person added to the group), profile information <part-num-ref name="group), profile information">820</part-num-ref>
+ including the alias name, phone number, and office location can be displayed. Other information can be shown as well depending on its availability and whether the user desires to view it. The full profile containing all the details of the person or group can be accessed in the address book (e.g., by clicking on the person or group name).     </p>
+    <p id="p-0080" num="0079"> In general, people-based message organization facilitates presenting the items known to all members of the selected group (e.g., the common knowledge within the group). Even if only a single person is selected, the mailbox owner is implicitly involved in all the communications stored in his/her message store&#x2014;hence, a two-person group results. </p>
+    <p id="p-0081" num="0080"> The communications are displayed in a conversational view (<part-num-ref name="conversational view (">820</part-num-ref>
+). In addition to offering any of the standard inbox views, the conversational view can be selected to visualize a set of messages associated with a group of people. The messages involving the same group tend to be related to each other. Even if they do not belong to the same message thread, they may discuss similar topics and contain mutual references. Essentially, they form a continuous &#x201c;conversation,&#x201d; to a much greater extent than messages flowing in the inbox from random people.     </p>
+    <p id="p-0082" num="0081"> The conversational view can be more applicable to current email users for other reasons as well. For instance, another common tendency, as observed in many users' inboxes, is a shift from long email messages (letter style) to a sequence of short messages and responses (instant messaging style). Short and quick messages gain popularity as email becomes faster and more ubiquitous. The whole sequence of short messages and replies is often needed to fully understand the conversation. </p>
+    <p id="p-0083" num="0082"> In the conversational view, the messages involving the selected people can be displayed as one long conversation (time-ordered)&#x2014;similar to the way conversations are displayed in instant messaging clients. For each message, the time, sender, subject, and the full message body expanded in place can be shown. Only the largest messages (e.g., &#x3e;1500 characters) have the message body truncated (e.g., indicated by more . . . button). </p>
+    <p id="p-0084" num="0083"> In addition, the original text formatting may be dropped to display all the message content in a uniform way as plain text. Finally, for messages that are replies or forwards, we only include the new text added by the last sender. Of course, any message can be opened and viewed in its complete original version by double clicking the message header. Moreover, the conversational view is a convenient way to look at email discussions within the group. Showing all the messages sent around the same time together facilitates understanding the context for each individual message. </p>
+    <p id="p-0085" num="0084"> As an aside, when showing messages associated with a selected person or a group, the subject invention can search across all folders and message stores. For example, if the email profile includes connections to multiple email transports (e.g., Exchange, POP, IMAP, HTTP), then one or more components of the invention can unify messages coming to the selected person or group from all possible sources. Moreover, contact list entries may define multiple email addresses associated with a single person. Communication involving any of these addresses is associated with the person. Therefore, the subject invention can perform a true unification of email communications with the selected group through various connections or email accounts. </p>
+    <p id="p-0086" num="0085"> The user interface <part-num-ref name="user interface">800</part-num-ref>
+ in <figref idref="DRAWINGS">FIG. 8</figref>
+ also includes a Mailed Items area <part-num-ref name="Mailed Items area">830</part-num-ref>
+. This area <part-num-ref name="This area">830</part-num-ref>
+ provides a separate view of all the mailed items shared between Shelly and Andrzej. In particular, all the file attachments and all identified Web and file links extracted from the body of the message can be presented. In addition, the Mailed Items area <part-num-ref name="Mailed Items area">830</part-num-ref>
+ includes the appointments involving all the selected people. Alternatively, the appointments can be shown in a calendar view as shared calendar events.     </p>
+    <p id="p-0087" num="0086"> Each item in the Mailed Items area (except for appointments) is associated with the message it came from. This association is important, since in many cases the message provides the context needed to understand the item origin or meaning. Even if the mailed items are shown separately from messages, a two-way link is maintained between them. Selecting any of the mailed items automatically scrolls the message list and highlights the parent message (e.g., <figref idref="DRAWINGS">FIGS. 17-19</figref>
+, infra, for demonstration). Conversely, selecting the message highlights the items within.     </p>
+    <p id="p-0088" num="0087"> As the number of mailed items grows large, it becomes useful to organize them in some way. The four most common item properties: item type, sender, send date, and parent message folder, can be employed as the grouping properties. When grouping by any of these properties is activated, the items can be divided into clusters that share the same property value. For example, by grouping by item type, one may easily find all items of type Word Document (e.g., <figref idref="DRAWINGS">FIGS. 17-22</figref>
+, infra, for illustration). This method of item grouping can replace and/or enhances the traditional folder structure of the file system.     </p>
+    <p id="p-0089" num="0088"> In a broader sense, the common knowledge within a group (e.g., user and selected person) may include communications with third parties. This can however include a lot of spam. A narrower interpretation limits the view only to messages exchanged within the group&#x2014;as depicted in <figref idref="DRAWINGS">FIG. 8</figref>
+. According to the user interface <part-num-ref name="user interface">900</part-num-ref>
+ in <figref idref="DRAWINGS">FIG. 9</figref>
+, the subject invention can support both models: a checkbox <part-num-ref name="checkbox">910</part-num-ref>
+ below the currently selected person or people labeled &#x201c;Show all items to/from selected people&#x201d; allows the user to decide whether the third party communications should be included or not. In contrast with <figref idref="DRAWINGS">FIG. 8</figref>
+, the user has selected the checkbox in <figref idref="DRAWINGS">FIG. 9</figref>
+. As a result, many more messages <part-num-ref name="result, many more messages">920</part-num-ref>
+ as well as shared (Mailed) items <part-num-ref name="as well as shared (Mailed) items">930</part-num-ref>
+ are displayed.     </p>
+    <p id="p-0090" num="0089"> Moving on to <figref idref="DRAWINGS">FIG. 10</figref>
+, the user interface <part-num-ref name="user interface">1000</part-num-ref>
+ presented therein demonstrates the selection of more than one person from the contact list <part-num-ref name="contact list">1010</part-num-ref>
+. In particular, both &#x201c;Shelly Farnham&#x201d; and &#x201c;Susan Yee&#x201d; are selected (as evidenced by their checked boxes). Consequently, Susan Yee has been added to the list of selected contacts (<part-num-ref name="list of selected contacts (">1020</part-num-ref>
+) in the message view window. Because she may have been the last person selected, her profile information <part-num-ref name="last person selected, her profile information">1030</part-num-ref>
+ can appear as well. To view Shelly's information again, the user can simply click on Shelly's name (<part-num-ref name="user can simply click on Shelly's name (">1020</part-num-ref>
+) in the message view window. Messages displayed in the message window can presumably include Andrzej, Shelly, Susan as well as any other third party&#x2014;since the checkbox is checked to show all items to/from the selected people.     </p>
+    <p id="p-0091" num="0090"> Turning now to <figref idref="DRAWINGS">FIG. 11</figref>
+, there is a schematic diagram that illustrates a click-by-click sequence of a zoomable contact list that can be utilized in a message organization and display system as described hereinabove. Level 1 (<part-num-ref name="display system as described hereinabove. Level 1 (">1100</part-num-ref>
+) shows the people most connected in terms of communication activity with the user (not shown). When the user clicks on a down-arrow next to a contact in Level 1, an additional level <part-num-ref name="contact in Level 1, an additional level">1110</part-num-ref>
+ (Level 2) is revealed. By clicking on the down-arrow next to &#x201c;Cezary Marcjan&#x201d;, contacts in the next tier (2<sup>nd </sup>
+tier) occurring between &#x201c;Benson Tan&#x201d; and &#x201c;Cezary Marcj an&#x201d; are now visible. To zoom in again, the user can click on the down-arrow next to &#x201c;Bill Mauer&#x201d; to reveal the 3<sup>rd </sup>
+tier <part-num-ref name="tier">1120</part-num-ref>
+ (Level 3) of contacts present between &#x201c;Bert Kleewein&#x201d; and &#x201c;Bill Mauer&#x201d;. Additional zooming can be performed where there appears a down-arrow. As each lower tier is expanded, a navigation bar can be found along one side of the opened tier. To zoom out of each tier, the navigation bar can be clicked on.     </p>
+    <p id="p-0092" num="0091"> To complement the browsing and navigation actions (e.g., zooming, expanding, etc.), an incremental search function can be employed. In a standard approach to such a feature, keying &#x2018;M&#x2019; would jump to the first entry starting with the letter &#x2018;M&#x2019;. Pressing &#x2018;M&#x2019; again would summon the second entry, and so on. Such an approach, however, might poorly complement the zoomable contact list, since the entries starting with &#x2018;M&#x2019; might be hidden. </p>
+    <p id="p-0093" num="0092"> In the subject invention, pressing &#x2018;M&#x2019; goes to the first entry with the letter &#x2018;M&#x2019;, on the highest level where there exists such an entry. It expands the hidden entries as necessary. Effectively, it selects the &#x201c;most important&#x201d; person starting with the letter M; or if there are a few people with a similar importance level, it selects the first one, but the other ones also come into view. </p>
+    <p id="p-0094" num="0093"> If one consecutively presses a few letters, the incremental control performs an incremental search for entries starting with these letters. For example, typing &#x201c;TIM&#x201d; finds entries starting with &#x201c;Tim&#x201d;. An aspect of the user interface <part-num-ref name="user interface">1200</part-num-ref>
+ in <figref idref="DRAWINGS">FIG. 12</figref>
+ demonstrates this control and search function. In the figure, the user has typed in &#x201c;HIM&#x201d; <part-num-ref name="user has typed in &#x201c;HIM&#x201d;">1210</part-num-ref>
+. The &#x201c;most important&#x201d; person starting with &#x201c;HIM&#x201d; appears in a second level <part-num-ref name="second level">1220</part-num-ref>
+, thus causing the contact list to expand where the entry occurs. In the standard approach, it jumps between entries starting with &#x2018;T&#x2019;, &#x2018;I&#x2019;, and &#x2018;M&#x2019;. The search mode is reset if one does anything other than typing a letter (e.g., clicking on an arrow key or a mouse button). Once the search mode is cancelled, one may start a new search for another name.     </p>
+    <p id="p-0095" num="0094"> The desired entry is in fact &#x201c;Himanshu Amin&#x201d;. When the user selects this contact, the message view can change to show all communications between Andrzej and Himanshu (and other third parties&#x2014;due to the checked box to show all item . . . ). In addition to the incremental search that tries to match the starting letters only, a regular text search can be employed. The regular search can match a substring in the entry name or its property (e.g., any of the contact's email aliases). The entries found through the text search are displayed using the same zoomable list algorithm (i.e., the most important names are shown first). </p>
+    <p id="p-0096" num="0095">
+      <figref idref="DRAWINGS">FIG. 13</figref>
+ illustrates a further zoom into the contact list to see the lower level contacts that come before <part-num-ref name="lower level contacts that come before">1310</part-num-ref>
+ and after <part-num-ref name="after">1320</part-num-ref>
+ &#x201c;Himanshu Amin&#x201d; alphabetically. As can be seen, there are lower level contacts that begin with &#x201c;HIM&#x201d; as well (e.g., &#x201c;Himabindu Thota&#x201d;), but were not shown earlier since the user's desired contact was found at an upper level.     </p>
+    <p id="p-0097" num="0096"> In <figref idref="DRAWINGS">FIG. 14</figref>
+, an exemplary user interface <part-num-ref name="an exemplary user interface">1400</part-num-ref>
+ depicts a change in the view of the mailed items area <part-num-ref name="mailed items area">1410</part-num-ref>
+ from <figref idref="DRAWINGS">FIG. 13</figref>
+. In <figref idref="DRAWINGS">FIG. 13</figref>
+, all Mailed items were shown. Now in <figref idref="DRAWINGS">FIG. 14</figref>
+, they are grouped by type (<part-num-ref name="they are grouped by type (">1420</part-num-ref>
+). Thus, to view a desired type, the user can select any one of the listed types. For example, the user selected &#x201c;Microsoft Word Document (39)&#x201d; and consequently, the 39 documents are displayed in the area <part-num-ref name="area">1410</part-num-ref>
+. All other types of mailed items are &#x201c;hidden&#x201d; from view temporarily.     </p>
+    <p id="p-0098" num="0097"> It should be appreciated that only those mail item types that actually exist for the selected people are available to view by the user. That is, if there were no &#x201c;Scheduled Meetings&#x201d;, then this type would not be shown in the Group by Type area <part-num-ref name="Group by Type area">1420</part-num-ref>
+. Alternatively, all types can be viewed but if no objects or files actually exist, a &#x201c;(0)&#x201d; notation is indicated.     </p>
+    <p id="p-0099" num="0098"> From <figref idref="DRAWINGS">FIG. 14</figref>
+ to <figref idref="DRAWINGS">FIG. 15</figref>
+, the user has selected a different group by type: &#x201c;Scheduled Meetings (1)&#x201d;. The one mailed item <part-num-ref name="one mailed item">1500</part-num-ref>
+ corresponding to a scheduled meeting is visible.     </p>
+    <p id="p-0100" num="0099"> From <figref idref="DRAWINGS">FIG. 15</figref>
+ to <figref idref="DRAWINGS">FIG. 16</figref>
+, the user has collapsed the expanded contact list <part-num-ref name="expanded contact list">1510</part-num-ref>
+ (<figref idref="DRAWINGS">FIG. 15</figref>
+), while keeping &#x201c;Himanshu Amin&#x201d; selected (checked box). In <figref idref="DRAWINGS">FIG. 16</figref>
+, &#x201c;Himanshu Amin&#x201d; now appears in the top level of the contact list <part-num-ref name="contact list">1600</part-num-ref>
+. One of the interesting features of the zoomable list is its ability to rearrange itself dynamically to show a different set of entries on the top level. For example, as in the case of &#x201c;Himanshu Amin&#x201d;, the user can expand the list and select one of the lower ranked entries. The (fully or partially) expanded list includes many other lower ranked entries that are not interesting at this time. Therefore, the user clicks on the collapse button to reduce the screen clutter.     </p>
+    <p id="p-0101" num="0100"> When collapsing the list, the user does not want lose any of the selected (e.g., marked with a check mark) entries from his/her view. Thus, the selected entries can be added to the top level tier, thereby either increasing the number of items in the top tier or causing the least important among the other entries to be removed. Following, the zoomable list can be repopulated or rebuilt using the new set of top level entries. This technique allows the user to manipulate the list to keep it relevant in all possible situations and at the same time, to keep it very compact. </p>
+    <p id="p-0102" num="0101"> Moving on to <figref idref="DRAWINGS">FIGS. 17-19</figref>
+, the two-way link between the mailed items and the corresponding messages is illustrated. In each of the figures, the user is viewing the mailed items in a grouping by type. A particular type is selected (e.g., Web pages in <figref idref="DRAWINGS">FIG. 17</figref>
+). Thereafter, one of the 107 web pages is highlighted which then brings up the relevant message (e.g., from Ron Goldin). As shown in each of the figures, the relevant message is highlighted for quick recognition by the user.     </p>
+    <p id="p-0103" num="0102">
+      <figref idref="DRAWINGS">FIG. 20</figref>
+ demonstrates the user's ability to browse through the mailed items via a grouping by folder. Such folders can be created in the messaging (email) system as well as is typically done with current email clients. <figref idref="DRAWINGS">FIGS. 21 and 22</figref>
+ show the user browsing through the mailed items via a grouping by sender and by date, respectively.     </p>
+    <p id="p-0104" num="0103">
+      <figref idref="DRAWINGS">FIGS. 23-25</figref>
+ depict yet another technique for browsing and/or filtering the mailed items displayed in the space. In these figures, the user has specified to only see a type of Mail item (e.g., Microsoft Word Document). Furthermore, the user can still browse by groupings. Thus, in <figref idref="DRAWINGS">FIG. 23</figref>
+, the user desires to see only mail items of type: Word Documents that are grouped by folder; in <figref idref="DRAWINGS">FIG. 24</figref>
+, only mail items of type: Word Documents that are grouped by sender; and in <figref idref="DRAWINGS">FIG. 25</figref>
+, only mail items of type: Word Documents that are grouped by date.     </p>
+    <p id="p-0105" num="0104"> Turning now to <figref idref="DRAWINGS">FIG. 26</figref>
+, an exemplary user interface <part-num-ref name="an exemplary user interface">2600</part-num-ref>
+ is shown when no other contacts are selected&#x2014;except for the user or mailbox owner. Recall that the entry for the mailbox owner is shown separately on the top of the contact list and always selected. If only the owner entry is selected, and the third party checkbox <part-num-ref name="third party checkbox">2610</part-num-ref>
+ is not checked, the view shows the owner's private items (e.g., items that do not involve anybody else). This turns out to be a very useful concept, particularly for users who use email as their data storage (e.g., they email the items to themselves). Apparently, this technique is used as a simple way of protecting the data (by backing it up on the email central server) and getting it replicated (e.g., between work and home.)     </p>
+    <p id="p-0106" num="0105"> When only the owner entry is selected and the third party checkbox <part-num-ref name="third party checkbox">2610</part-num-ref>
+ is checked, the view effectively includes all the items in the message store. This may be useful to view all the mailed items regardless of their people association and group them according to some other criteria. In the figure, the checkbox <part-num-ref name="checkbox">2610</part-num-ref>
+ is checked, thus all direct items sent to or from the user (Andrzej Turski) are displayed.     </p>
+    <p id="p-0107" num="0106"> Various methodologies in accordance with the subject invention will now be described via a series of acts, it is to be understood and appreciated that the subject invention is not limited by the order of acts, as some acts may, in accordance with the subject invention, occur in different orders and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all illustrated acts may be required to implement a methodology in accordance with the subject invention. </p>
+    <p id="p-0108" num="0107"> Referring now to <figref idref="DRAWINGS">FIG. 27</figref>
+, there is a flow diagram of an exemplary process <part-num-ref name="flow diagram of an exemplary process">2700</part-num-ref>
+ that facilitates contact-based message organization in accordance with an aspect of the subject invention. The process <part-num-ref name="process">2700</part-num-ref>
+ includes populating a contact list at <part-num-ref name="contact list at">2710</part-num-ref>
+ with contacts that are included on communications sent to a user (e.g., mailbox owner). The contacts can be at least the sender of the communication as well as any third party recipient of the message (e.g., on the To:, cc:, and/or bcc: lines). At <part-num-ref name="To:, cc:, and/or bcc: lines). At">2720</part-num-ref>
+, the relative communication activity between each contact in the list and the user can be determined. The contacts can be ordered alphabetically and then ranked according to their respective communication activity with the user at <part-num-ref name="user at">2730</part-num-ref>
+. At <part-num-ref name="At">2740</part-num-ref>
+, the top level of the contact list indicating those that are most connected to the user can be made visible on the list and displayed on a user interface. The other contacts in the lower levels can be somewhat hidden, collapsed, or folded-in to the list, but readily accessed due to the alphabetical organization of the list. Though not depicted in the figure, messages or other communications can then organized by contact, whereby the contact is the sender or a third party recipient. In either scenario, the user can view their messages by the people intimately associated with such messages.     </p>
+    <p id="p-0109" num="0108"> Referring now to <figref idref="DRAWINGS">FIG. 28</figref>
+, there is a flow diagram of an exemplary method <part-num-ref name="flow diagram of an exemplary method">2800</part-num-ref>
+ that facilitates populating a contact list in accordance with an aspect of the subject invention. The method <part-num-ref name="method">2800</part-num-ref>
+ involves identifying the contacts associated with a user's communications at <part-num-ref name="user's communications at">2810</part-num-ref>
+. At <part-num-ref name="At">2820</part-num-ref>
+, the communication activity with respect to any contact (e.g., person or group) can be monitored for T days to compute an amount of activity in that time period. For example, activity can be monitored in 30 day intervals. To depreciate spam and spammers, more weight can be given to messages received by contacts. If the amount satisfies a threshold set for a particular level of activity, then the contact can be placed at that level. The contact list can be updated at <part-num-ref name="contact list can be updated at">2830</part-num-ref>
+ once such analysis has been performed for each contact.     </p>
+    <p id="p-0110" num="0109"> Referring now to <figref idref="DRAWINGS">FIG. 29</figref>
+, there is a flow diagram of an exemplary method <part-num-ref name="flow diagram of an exemplary method">2900</part-num-ref>
+ that facilitates contact-based message organization in accordance with an aspect of the invention. The method <part-num-ref name="method">2900</part-num-ref>
+ includes receiving at least one communication at <part-num-ref name="includes receiving at least one communication at">2910</part-num-ref>
+. At <part-num-ref name="At">2920</part-num-ref>
+, the communication can be organized by sender and secondarily by other third party recipients of the communication. At <part-num-ref name="communication. At">2930</part-num-ref>
+, the &#x201c;organized by contact&#x201d; communication can be stored in a message data store.     </p>
+    <p id="p-0111" num="0110"> Access to and/or retrieval of stored messages can be accomplished as indicated in the exemplary process <part-num-ref name="exemplary process">3000</part-num-ref>
+ of <figref idref="DRAWINGS">FIG. 30</figref>
+. In the process <part-num-ref name="process">3000</part-num-ref>
+, at least one contact can be selected (via a check mark in the checkbox) on the contact list at <part-num-ref name="contact list at">3010</part-num-ref>
+. At <part-num-ref name="At">3020</part-num-ref>
+, all or substantially communications exchanged between the user and the selected contact can be viewed and displayed in a message window, for example. At <part-num-ref name="message window, for example. At">3030</part-num-ref>
+, all shared items corresponding to the displayed messages can be shown in a separate space. The process <part-num-ref name="process">3000</part-num-ref>
+ can proceed to <figref idref="DRAWINGS">FIGS. 31 and 32</figref>
+.     </p>
+    <p id="p-0112" num="0111"> In <figref idref="DRAWINGS">FIG. 31</figref>
+, the user can optionally select to see communications between the user, the selected contact (<figref idref="DRAWINGS">FIG. 30</figref>
+) and other third parties at <part-num-ref name="other third parties at">3110</part-num-ref>
+. Similarly, when this occurs, the additional shared items included in the third party communications can be added to the display area at <part-num-ref name="display area at">3120</part-num-ref>
+.     </p>
+    <p id="p-0113" num="0112"> Alternatively or in addition, <figref idref="DRAWINGS">FIG. 32</figref>
+ demonstrates that a subsequent process <part-num-ref name="subsequent process">3200</part-num-ref>
+ can involve browsing shared items by a grouping property (e.g., group by type, sender, date, folder, etc) at <part-num-ref name="grouping property (e.g., group by type, sender, date, folder, etc) at">3210</part-num-ref>
+. Optionally, the shared items can be browsed by type and then by a grouping property at <part-num-ref name="grouping property at">3220</part-num-ref>
+&#x2014;to further narrow the items on display.     </p>
+    <p id="p-0114" num="0113"> In order to provide additional context for various aspects of the subject invention, <figref idref="DRAWINGS">FIG. 33</figref>
+ and the following discussion are intended to provide a brief, general description of a suitable operating environment <part-num-ref name="suitable operating environment">3310</part-num-ref>
+ in which various aspects of the subject invention may be implemented. While the invention is described in the general context of computer-executable instructions, such as program modules, executed by one or more computers or other devices, those skilled in the art will recognize that the invention can also be implemented in combination with other program modules and/or as a combination of hardware and software.     </p>
+    <p id="p-0115" num="0114"> Generally, however, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular data types. The operating environment <part-num-ref name="operating environment">3310</part-num-ref>
+ is only one example of a suitable operating environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Other well known computer systems, environments, and/or configurations that may be suitable for use with the invention include but are not limited to, personal computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include the above systems or devices, and the like.     </p>
+    <p id="p-0116" num="0115"> With reference to <figref idref="DRAWINGS">FIG. 33</figref>
+, an exemplary environment <part-num-ref name="an exemplary environment">3310</part-num-ref>
+ for implementing various aspects of the invention includes a computer <part-num-ref name="computer">3312</part-num-ref>
+. The computer <part-num-ref name="computer">3312</part-num-ref>
+ includes a processing unit <part-num-ref name="processing unit">3314</part-num-ref>
+, a system memory <part-num-ref name="system memory">3316</part-num-ref>
+, and a system bus <part-num-ref name="system bus">3318</part-num-ref>
+. The system bus <part-num-ref name="system bus">3318</part-num-ref>
+ couples system components including, but not limited to, the system memory <part-num-ref name="system memory">3316</part-num-ref>
+ to the processing unit <part-num-ref name="processing unit">3314</part-num-ref>
+. The processing unit <part-num-ref name="processing unit">3314</part-num-ref>
+ can be any of various available processors. Dual microprocessors and other multiprocessor architectures also can be employed as the processing unit <part-num-ref name="processing unit">3314</part-num-ref>
+.     </p>
+    <p id="p-0117" num="0116"> The system bus <part-num-ref name="system bus">3318</part-num-ref>
+ can be any of several types of bus structure(s) including the memory bus or memory controller, a peripheral bus or external bus, and/or a local bus using any variety of available bus architectures including, but not limited to, 11-bit bus, Industrial Standard Architecture (ISA), Micro-Channel Architecture (MCA), Extended ISA (EISA), Intelligent Drive Electronics (IDE), VESA Local Bus (VLB), Peripheral Component Interconnect (PCI), Universal Serial Bus (USB), Advanced Graphics Port (AGP), Personal Computer Memory Card International Association bus (PCMCIA), and Small Computer Systems Interface (SCSI).     </p>
+    <p id="p-0118" num="0117"> The system memory <part-num-ref name="system memory">3316</part-num-ref>
+ includes volatile memory <part-num-ref name="includes volatile memory">3320</part-num-ref>
+ and nonvolatile memory <part-num-ref name="nonvolatile memory">3322</part-num-ref>
+. The basic input/output system (BIOS), containing the basic routines to transfer information between elements within the computer <part-num-ref name="computer">3312</part-num-ref>
+, such as during start-up, is stored in nonvolatile memory <part-num-ref name="such as during start-up, is stored in nonvolatile memory">3322</part-num-ref>
+. By way of illustration, and not limitation, nonvolatile memory <part-num-ref name="not limitation, nonvolatile memory">3322</part-num-ref>
+ can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory <part-num-ref name="flash memory. Volatile memory">3320</part-num-ref>
+ includes random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM).     </p>
+    <p id="p-0119" num="0118"> Computer <part-num-ref name="Computer">3312</part-num-ref>
+ also includes removable/nonremovable, volatile/nonvolatile computer storage media. <figref idref="DRAWINGS">FIG. 33</figref>
+ illustrates, for example a disk storage <part-num-ref name="disk storage">3324</part-num-ref>
+. Disk storage <part-num-ref name="Disk storage">3324</part-num-ref>
+ includes, but is not limited to, devices like a magnetic disk drive, floppy disk drive, tape drive, Jaz drive, Zip drive, LS-100 drive, flash memory card, or memory stick. In addition, disk storage <part-num-ref name="memory stick. In addition, disk storage">3324</part-num-ref>
+ can include storage media separately or in combination with other storage media including, but not limited to, an optical disk drive such as a compact disk ROM device (CD-ROM), CD recordable drive (CD-R Drive), CD rewritable drive (CD-RW Drive) or a digital versatile disk ROM drive (DVD-ROM). To facilitate connection of the disk storage devices <part-num-ref name="disk storage devices">3324</part-num-ref>
+ to the system bus <part-num-ref name="system bus">3318</part-num-ref>
+, a removable or non-removable interface is typically used such as interface <part-num-ref name="non-removable interface is typically used such as interface">3326</part-num-ref>
+.     </p>
+    <p id="p-0120" num="0119"> It is to be appreciated that <figref idref="DRAWINGS">FIG. 33</figref>
+ describes software that acts as an intermediary between users and the basic computer resources described in suitable operating environment <part-num-ref name="basic computer resources described in suitable operating environment">3310</part-num-ref>
+. Such software includes an operating system <part-num-ref name="Such software includes an operating system">3328</part-num-ref>
+. Operating system <part-num-ref name="Operating system">3328</part-num-ref>
+, which can be stored on disk storage <part-num-ref name="which can be stored on disk storage">3324</part-num-ref>
+, acts to control and allocate resources of the computer system <part-num-ref name="computer system">3312</part-num-ref>
+. System applications <part-num-ref name="System applications">3330</part-num-ref>
+ take advantage of the management of resources by operating system <part-num-ref name="management of resources by operating system">3328</part-num-ref>
+ through program modules <part-num-ref name="through program modules">3332</part-num-ref>
+ and program data <part-num-ref name="program data">3334</part-num-ref>
+ stored either in system memory <part-num-ref name="stored either in system memory">3316</part-num-ref>
+ or on disk storage <part-num-ref name="on disk storage">3324</part-num-ref>
+. It is to be appreciated that the subject invention can be implemented with various operating systems or combinations of operating systems.     </p>
+    <p id="p-0121" num="0120"> A user enters commands or information into the computer <part-num-ref name="computer">3312</part-num-ref>
+ through input device(s) <part-num-ref name="through input device(s)">3336</part-num-ref>
+. Input devices <part-num-ref name="Input devices">3336</part-num-ref>
+ include, but are not limited to, a pointing device such as a mouse, trackball, stylus, touch pad, keyboard, microphone, joystick, game pad, satellite dish, scanner, TV tuner card, digital camera, digital video camera, web camera, and the like. These and other input devices connect to the processing unit <part-num-ref name="processing unit">3314</part-num-ref>
+ through the system bus <part-num-ref name="system bus">3318</part-num-ref>
+ via interface port(s) <part-num-ref name="via interface port(s)">3338</part-num-ref>
+. Interface port(s) <part-num-ref name="Interface port(s)">3338</part-num-ref>
+ include, for example, a serial port, a parallel port, a game port, and a universal serial bus (USB). Output device(s) <part-num-ref name="universal serial bus (USB). Output device(s)">3340</part-num-ref>
+ use some of the same type of ports as input device(s) <part-num-ref name="same type of ports as input device(s)">3336</part-num-ref>
+. Thus, for example, a USB port may be used to provide input to computer <part-num-ref name="USB port may be used to provide input to computer">3312</part-num-ref>
+, and to output information from computer <part-num-ref name="to output information from computer">3312</part-num-ref>
+ to an output device <part-num-ref name="to an output device">3340</part-num-ref>
+. Output adapter <part-num-ref name="Output adapter">3342</part-num-ref>
+ is provided to illustrate that there are some output devices <part-num-ref name="is provided to illustrate that there are some output devices">3340</part-num-ref>
+ like monitors, speakers, and printers among other output devices <part-num-ref name="printers among other output devices">3340</part-num-ref>
+ that require special adapters. The output adapters <part-num-ref name="output adapters">3342</part-num-ref>
+ include, by way of illustration and not limitation, video and sound cards that provide a means of connection between the output device <part-num-ref name="output device">3340</part-num-ref>
+ and the system bus <part-num-ref name="system bus">3318</part-num-ref>
+. It should be noted that other devices and/or systems of devices provide both input and output capabilities such as remote computer(s) <part-num-ref name="output capabilities such as remote computer(s)">3344</part-num-ref>
+.     </p>
+    <p id="p-0122" num="0121"> Computer <part-num-ref name="Computer">3312</part-num-ref>
+ can operate in a networked environment using logical connections to one or more remote computers, such as remote computer(s) <part-num-ref name="more remote computers, such as remote computer(s)">3344</part-num-ref>
+. The remote computer(s) <part-num-ref name="remote computer(s)">3344</part-num-ref>
+ can be a personal computer, a server, a router, a network PC, a workstation, a microprocessor based appliance, a peer device or other common network node and the like, and typically includes many or all of the elements described relative to computer <part-num-ref name="elements described relative to computer">3312</part-num-ref>
+. For purposes of brevity, only a memory storage device <part-num-ref name="memory storage device">3346</part-num-ref>
+ is illustrated with remote computer(s) <part-num-ref name="is illustrated with remote computer(s)">3344</part-num-ref>
+. Remote computer(s) <part-num-ref name="Remote computer(s)">3344</part-num-ref>
+ is logically connected to computer <part-num-ref name="is logically connected to computer">3312</part-num-ref>
+ through a network interface <part-num-ref name="network interface">3348</part-num-ref>
+ and then physically connected via communication connection <part-num-ref name="then physically connected via communication connection">3350</part-num-ref>
+. Network interface <part-num-ref name="Network interface">3348</part-num-ref>
+ encompasses communication networks such as local-area networks (LAN) and wide-area networks (WAN). LAN technologies include Fiber Distributed Data Interface (FDDI), Copper Distributed Data Interface (CDDI), Ethernet/IEEE 1102.3, Token Ring/IEEE 1102.5 and the like. WAN technologies include, but are not limited to, point-to-point links, circuit switching networks like Integrated Services Digital Networks (ISDN) and variations thereon, packet switching networks, and Digital Subscriber Lines (DSL).     </p>
+    <p id="p-0123" num="0122"> Communication connection(s) <part-num-ref name="Communication connection(s)">3350</part-num-ref>
+ refers to the hardware/software employed to connect the network interface <part-num-ref name="network interface">3348</part-num-ref>
+ to the bus <part-num-ref name="bus">3318</part-num-ref>
+. While communication connection <part-num-ref name="While communication connection">3350</part-num-ref>
+ is shown for illustrative clarity inside computer <part-num-ref name="is shown for illustrative clarity inside computer">3312</part-num-ref>
+, it can also be external to computer <part-num-ref name="it can also be external to computer">3312</part-num-ref>
+. The hardware/software necessary for connection to the network interface <part-num-ref name="network interface">3348</part-num-ref>
+ includes, for exemplary purposes only, internal and external technologies such as, modems including regular telephone grade modems, cable modems and DSL modems, ISDN adapters, and Ethernet cards.     </p>
+    <p id="p-0124" num="0123"> What has been described above includes examples of the subject invention. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the subject invention, but one of ordinary skill in the art may recognize that many further combinations and permutations of the subject invention are possible. Accordingly, the subject invention is intended to embrace all such alterations, modifications, and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term &#x201c;includes&#x201d; is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term &#x201c;comprising&#x201d; as &#x201c;comprising&#x201d; is interpreted when employed as a transitional word in a claim. </p>
+    <?detailed-description description="Detailed Description" end="tail"?>
+  </description>
+</us-patent-application>

prior_art/11050993.xml

@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11050993</doc-number>
+        <date>2011-03-28</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">Application No. <confidence value="586">11/</confidence>
+050,993 Amendment dated March 28, 2011 Rep<confidence value="8">l</confidence>
+y to final Office Action of October <part-num-ref name="Reply to final Office Action of October">27,</part-num-ref>
+ <part-num-ref name="Reply to final Office Action of October 27,">2010</part-num-ref>
+     </p>
+    <heading id="h-1">AMENDMENT TO T<confidence value="5">H</confidence>
+E SPECIFICATION    </heading>
+    <p id="p-2" num="2">Amend the title of the application, shown on page <part-num-ref name="application, shown on page">
+        <confidence value="5">1</confidence>
+      </part-num-ref>
+ of the specification, to: METHODS     </p>
+    <heading id="h-2">FOR LOCALIZING PA<confidence value="8">I</confidence>
+N RESPONSES AND IDENTIFYING DAMAGED TISSUES.    </heading>
+    <p id="p-3" num="3">12500.2006con                               2<confidence value="588">/14</confidence>
+     </p>
+  </description>
+</us-patent-application>
+

prior_art/11081947.xml

@@ -0,0 +1,612 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11081947</doc-number>
+        <date>2005-03-17</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <heading id="h-1">SOUND REDUCING WEDGE SHAPED POLYMER INTERLAYERS</heading>
+    <heading id="h-2">FIELD OF THE INVENTION</heading>
+    <p id="p-1" num="1">The present invention is in the field of polymer interlayers and multiple layer <boundary-data type="line-number">5   </boundary-data>
+glass panels comprising polymer interlayers, and, more specifically, the present invention is in the field of wedge shaped polymer interlayers.    </p>
+    <heading id="h-3">BACKGROUND</heading>
+    <p id="p-2" num="2">
+      <confidence value="2222222222">Poly(vinyl</confidence>
+ butyral) (PVB) is commonly used in the manufacture of polymer <boundary-data type="line-number">10   </boundary-data>
+sheets that can be used as interlayers in light-transmitting laminates such as safety glass or polymeric laminates. Safety glass often refers to a transparent laminate comprising a poly(vinyl butyral) sheet, or interlayer, disposed between two sheets of glass. Safety glass often is used to provide a transparent barrier in architectural and automotive openings. Its main function is to absorb energy, such as that caused by a blow from an <boundary-data type="line-number">15   </boundary-data>
+object, without allowing penetration through the opening or the dispersion of shards of glass, thus minimizing damage or injury to the objects or persons within an enclosed area.    </p>
+    <p id="p-3" num="3">Safety glass also can be used to provide other beneficial effects, such as to reduce ultraviolet (UV) and/or infrared (IR) light transmission, and/or enhance the appearance and aesthetic appeal of window openings.</p>
+    <p id="p-4" num="4">
+      <boundary-data type="line-number">20          </boundary-data>
+Safety glass interlayers have also been used as an important component in automobile head-up display (HUD) systems, which can provide, for example, an instrument cluster image at the eye level of a driver of the automobile. Such a display allows a driver to stay focused on the upcoming road while visually accessing dash board information. One type of interlayer used in such head-up display systems is wedge <boundary-data type="line-number">25   </boundary-data>
+shaped in ver<confidence value="8">t</confidence>
+ical cross section. The wedge shape of the interlayer is used to provide the correct light dynamics through the windshield required for a head up display.    </p>
+    <p id="p-5" num="5">Unfortunately, as with standard windshields, head up display windshields can also lead to an undesirablely high noise transmission level through the windshield.</p>
+    <p id="p-6" num="6">Accordingly, further improved compositions and methods are needed to enhance 30   the sound dampening characteristics of multiple layer glass panels, and specifically <boundary-data type="header">
+        <confidence value="1">1</confidence>
+      </boundary-data>
+      <page-break num="2"/>
+multiple layer glass panels in which a wedge shaped interlayer is used to provide for head-up display capability.    </p>
+    <heading id="h-4">SUMMARY OF THE INVENTION</heading>
+    <p id="p-7" num="7">
+      <boundary-data type="line-number">5          </boundary-data>
+The present invention provides interlayers that can be used in multiple layer glass panel type applications to reduce the amount of sound transmitted through the panel, and, in particular, at coincident frequencies for such glass laminates, for example in the range of about 2,000 to 6,000 Hertz. This effect is achieved by incorporating an acoustic polymeric interlayer into wedge shaped laminated glass applications, and, more <boundary-data type="line-number">10   </boundary-data>
+specifically, into wedge shaped windshield applications.    </p>
+    <heading id="h-5">BRIEF DESCRIPTION OF THE FIGURES</heading>
+    <p id="p-8" num="8">Figure 1 is a schematic representation of one embodiment of a wedge shaped interlayer of the present invention.</p>
+    <p id="p-9" num="9">
+      <boundary-data type="line-number">
+        <confidence value="88">15</confidence>
+      </boundary-data>
+     </p>
+    <heading id="h-6">DETAILED DESCRIPTION</heading>
+    <p id="p-10" num="10">Now, according to the present invention, it has been discovered that wedge shaped windshield interlayers incorporating an acoustic polymer sheet can advantageously be used to limit sound transmission through a windshield and into a <boundary-data type="line-number">20   </boundary-data>
+vehicle. Wedge shaped interlayers of the present invention are particularly useful in automobiles in which a "heads up" display is provided and for which non-parallel glass layers are typically used in the windshield laminate.    </p>
+    <p id="p-11" num="11">As will be described in detail herein, windshield interlayers of the present invention are wedge shaped. As used herein, an interlayer or polymer sheet is said to be <boundary-data type="line-number">25   </boundary-data>
+"wedge shaped" if the average thickness of the interlayer or polymer sheet as measured at one edge is <confidence value="5">a</confidence>
+t least 0.13 millimeters greater than the average thickness of the interlayer or polymer sheet as measured at the opposite edge. Wedge shaped interlayers of the present invention, in cross section, can resemble, for example, an isosceles trapezoid or a right trapezoid, among others, when they are first formed. The thickness transitions of the <boundary-data type="line-number">30   </boundary-data>
+cross-section of the polymer sheet can occur gradually, or can be immediate. The rate of the thickness change from one edge of the polymer sheet to the opposite edge can be <boundary-data type="header">
+        <confidence value="8">2</confidence>
+      </boundary-data>
+      <page-break num="3"/>
+continuous, or can vary to the extent that the profile may be flat with no rate of thickness change in certain areas of the cross section of the polymer sheet. Likewise, the rate of thickness change may decrease or increase throughout the cross section of the polymer sheet as long as one edge of the polymer sheet is greater in thickness than the other edge.    </p>
+    <p id="p-12" num="12">
+      <boundary-data type="line-number">5   </boundary-data>
+Of course, after lamination with non-planar rigid substrates such as curved glass windshields, the wedge shaped interlayer will conform to the contours of the laminate.    </p>
+    <p id="p-13" num="13">The wedge shaped interlayers of the present invention can be formed from a single polymer sheet, or from two or more polymer sheets. As will be described in detail below, polymer sheets can be any suitable thermoplastic polymer, for example poly(vinyl <boundary-data type="line-number">10   </boundary-data>
+butyral).    </p>
+    <p id="p-14" num="14">In various embodiments, wedge shaped interlayers of the present invention are formed from a single polymer sheet. In various embodiments, the polymer sheet can be a wedge shaped polymer sheet that has been formed from a single acoustic polymer melt (as defined herein) in a single melt extrusion process. In other embodiments, a single <boundary-data type="line-number">15   </boundary-data>
+polymer sheet can be formed through a coextrusion process in which an acoustic polymer melt and a non acoustic polymer melt (as defined herein) are coextruded to form a single wedge shaped polymer sheet having an acoustic region and a non acoustic region. In various coextrusion embodiments, the regions are formed so as to approximate two separate layers within the single sheet, which emulates the effect that would be achieved <boundary-data type="line-number">20   </boundary-data>
+if two separate polymer sheets - an acoustic and a non acoustic - had been laminated together. In yet other embodiments, a first acoustic polymer melt and a second, different acoustic polymer melt can be coextruded to form a wedge shaped interlayer having two different acoustic regions. Again, each region approximates a layer within the sheet.    </p>
+    <p id="p-15" num="15">For any of the coextrusion embodiments described in the previous paragraph, a <boundary-data type="line-number">25   </boundary-data>
+further coextrusion region can be formed from acoustic or non acoustic material, as desired. For example, a wedge shaped polymer sheet can be formed by coextruding an acoustic polymer melt between two non acoustic polymer melts to form a three region wedge shaped polymer sheet that can be used as a noise suppressing interlayer. This embodiment has the advantage of relatively low blocking. Further coextrusion regions <boundary-data type="line-number">30   </boundary-data>
+can be formed with tinted melts, for example, to form color gradient regions within the polymer sheet.    </p>
+    <boundary-data type="header">
+      <confidence value="8">3</confidence>
+    </boundary-data>
+    <p id="p-16" num="16">
+      <page-break num="4"/>
+In any of the embodiments in which a single wedge shaped polymer sheet is used to form a wedge shaped windshield interlayer, one edge of the polymer sheet can have an edge with a thickness that is at least 0.13 millimeters, at least 0.2 millimeters, at least 0.3 millimeters, at least 0.4 millimeters, at least 0.5 millimeters, at least 0.7 millimeters, or at <boundary-data type="line-number">5   </boundary-data>
+least 1.0 millimeters greater than the thickness of the opposite edge, which difference forms a wedge shape.    </p>
+    <p id="p-17" num="17">In any of the embodiments in which a single wedge shaped polymer sheet is used to form a wedge shaped windshield interlayer, the thinner edge can have a thickness of, for example, at least 0.38 millimeters, at least 0.45 millimeters, at least 0.75 millimeters, <boundary-data type="line-number">10   </boundary-data>
+at least 1.0 millimeters, and/or from 0.38 to 2.5 millimeters, 0.4 to 2.0 millimeters, 0.5 to 1.75 millimeters, or 0.6 to 1.5 millimeters.    </p>
+    <p id="p-18" num="18">In various other embodiments, windshield interlayers of the present invention comprise more than one polymer sheet, and, optionally, other polymeric layers and/or other layers. In these embodiments, at least one of the polymer sheets is an acoustic <boundary-data type="line-number">15   </boundary-data>
+polymer sheet or a polymer sheet having an acoustic region<confidence value="5">,</confidence>
+ as defined herein.    </p>
+    <p id="p-19" num="19">As shown in Figure 1 generally at <part-num-ref name="generally at">10,</part-num-ref>
+ a two layer embodiment comprises a wedge shaped polymer sheet <part-num-ref name="wedge shaped polymer sheet">14</part-num-ref>
+ and a flat polymer sheet <part-num-ref name="flat polymer sheet">12.</part-num-ref>
+ The wedge shaped polymer sheet <part-num-ref name="wedge shaped polymer sheet">14</part-num-ref>
+ and the flat polymer sheet <part-num-ref name="flat polymer sheet">12</part-num-ref>
+ together form a wedge shaped interlayer having a first thickness, T<confidence value="5">1</confidence>
+, and a second thickness, T2. As described above for single layer <boundary-data type="line-number">20    </boundary-data>
+embodiments, one edge of the wedge shaped interlayer can have an edge with a thickness (T2) that is at least 0.13 millimeters, at least 0.2 millimeters, at least 0.3 millimeters, at least 0.4 millimeters, at least 0.5 millimeters, at least 0.7 millimeters, or at least 1.0 millimeters greater than the thickness of the opposite edge (T1), which difference forms a wedge shape. Further, T<confidence value="5">1</confidence>
+, as shown in Figure 1, can have a thickness of, for example, at <boundary-data type="line-number">25    </boundary-data>
+least 0.38 millimeters, at least 0.45 millimeters, at least 0.75 millimeters, at least 1.0 mm, and/or from 0.38 to 2.5 millimeters, 0.4 to 2.0 millimeters, 0.5 to 1.75 millimeters, or 0.6 to 1.5 millimeters.    </p>
+    <p id="p-20" num="20">The schematic representation of one embodiment of a wedge shaped interlayer of the present invention illustrated in Figure 1 shows a thickness transition of the cross- <boundary-data type="line-number">30   </boundary-data>
+section of the polymer sheet that occurs immediately and at a continuous and constant rate of the thickness change.    </p>
+    <boundary-data type="header">
+      <confidence value="8">4</confidence>
+    </boundary-data>
+    <p id="p-21" num="21">
+      <page-break num="5"/>
+For wedge shaped interlayer embodiments where the rate of thickness change from one edge of the polymer sheet to the opposite polymer sheet is continuous and constant, the wedge angle, formed between the wedge shaped surface and the opposite su<confidence value="8">r</confidence>
+face, can be calculated from the algorithm:    </p>
+    <p id="p-22" num="22">T2-T<confidence value="2">1</confidence>
+ <boundary-data type="line-number">5                                   </boundary-data>
+tan a =     </p>
+    <heading id="h-7">
+      <confidence value="5">W</confidence>
+    </heading>
+    <p id="p-23" num="23">Where a is the wedge angle, in milliradians; T<confidence value="4">1</confidence>
+ and T2 are defined in Figure 1, and W is the width of the wedge shaped interlayer sheet.    </p>
+    <p id="p-24" num="24">For wedge shaped interlayer embodiments of the present invention in which two or more layers are used, at least one of the layers is an acoustic polymer sheet or a <boundary-data type="line-number">10   </boundary-data>
+coextruded polymer sheet having an acoustic region, as described above. For example, the wedge shaped polymer sheet <part-num-ref name="wedge shaped polymer sheet">14</part-num-ref>
+ can be an acoustic polymer sheet and the flat polymer sheet <part-num-ref name="flat polymer sheet">12</part-num-ref>
+ can be a non acoustic polymer sheet. The reverse is also acceptable, where the wedge shaped polymer sheet <part-num-ref name="wedge shaped polymer sheet">14</part-num-ref>
+ is a non acoustic polymer sheet and the flat polymer sheet <part-num-ref name="flat polymer sheet">12</part-num-ref>
+ is an acoustic polymer sheet.    </p>
+    <p id="p-25" num="25">
+      <boundary-data type="line-number">15         </boundary-data>
+In yet further embodiments, one or more further layer of polymer sheet are incorporated into the construct shown in Figure 1. For example, a third polymer sheet, acoustic or non acoustic and wedge shaped or non wedge shaped can be incorporated.    </p>
+    <p id="p-26" num="26">Any suitable configuration of polymer sheets and sheet types can be used to form a wedge shaped interlayer, and in various embodiments, the overall dimensions of these <boundary-data type="line-number">20   </boundary-data>
+multiple layered interlayers will be within the ranges given above for thicknesses for single polymer sheet embodiments.    </p>
+    <p id="p-27" num="27">In various embodiments, a polymer film layer such as poly(ethylene terephthalate), as described elsewhere herein, can be included in a multiple layer construct of the present invention. For example, a polymer film can be included between <boundary-data type="line-number">25   </boundary-data>
+the wedge shaped polymer sheet <part-num-ref name="wedge shaped polymer sheet">14</part-num-ref>
+ and the flat polymer sheet <part-num-ref name="flat polymer sheet">12</part-num-ref>
+ in Figure 1 to produce a three layer embodiment in which a polymer film is incorporated between two polymer layers. In yet further embodiments, two or more polymer films can be incorporated into multiple layer interlayer embodiments of the present invention.    </p>
+    <p id="p-28" num="28">In various embodiments of the present invention, interlayers of the present <part-num-ref name="present">30</part-num-ref>
+   invention, when laminated between two sheets of glass panes, reduce the transmission of <boundary-data type="header">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+      <page-break num="6"/>
+sound through the laminated glass panel by at least <part-num-ref name="laminated glass panel by at least">2</part-num-ref>
+ decibels (dB) at the coincident frequency relative to a comparable laminated glass panel having a single conventional interlayer consisting of a non acoustic polymer sheet having the same shape as an interlayer of the present invention.    </p>
+    <p id="p-29" num="29">
+      <boundary-data type="line-number">5         </boundary-data>
+In various embodiments of the present invention, interlayers of the present invention, when laminated between two sheets of glass panes, improve the sound transmission loss by at least <part-num-ref name="sound transmission loss by at least">2</part-num-ref>
+ dB, more preferably <part-num-ref name="dB, more preferably">4</part-num-ref>
+ dB, and even more preferably <part-num-ref name="dB, and even more preferably">6</part-num-ref>
+ dB or higher, say <part-num-ref name="dB or higher, say">8</part-num-ref>
+ dB at the coincident frequency relative to a comparable laminated glass panel having a single conventional interlayer consisting of a non acoustic polymer sheet <boundary-data type="line-number">10   </boundary-data>
+having the same shape as an interlayer of the present invention.    </p>
+    <p id="p-30" num="30">For each embodiment described herein comprising a glass layer, another embodiment<confidence value="5">,</confidence>
+ exists, where suitable, wherein a glazing type material is used in place of the glass. Examples of such glazing layers include rigid plastics having a high glass transition temperature (Tg), for example above 60<confidence value="2">*</confidence>
+C or 70<confidence value="2">*</confidence>
+C, for example <boundary-data type="line-number">15   </boundary-data>
+polycarbonates, polyesters, polyalkyl methacrylates, and specifically those having from <part-num-ref name="high glass transition temperature (Tg), for example above 60*C or 70*C, for example polycarbonates, polyesters, polyalkyl methacrylates, and specifically those having from">1</part-num-ref>
+ to <part-num-ref name="to">3</part-num-ref>
+ carbon atoms in the alkyl moiety.    </p>
+    <p id="p-31" num="31">In addition to the interlayers provided herein, the present invention also provides methods of reducing the level of sound through an opening, comprising the step of disposing in the opening a multiple layer glass panel comprising any of the wedge shaped <boundary-data type="line-number">20   </boundary-data>
+interlayers of the present invention.    </p>
+    <p id="p-32" num="32">The present invention also includes methods of manufacturing a multiple layer glazing, comprising laminating any of the interlayers of the present invention between two rigid, transparent panels, as are known in the art, such as glass or acrylic layers.</p>
+    <p id="p-33" num="33">The present invention also includes multiple layer glass panels, such as <boundary-data type="line-number">25   </boundary-data>
+windshields and architectural windows, comprising a multiple layer interlayer of the present invention. Also included are multiple layer glazing panels having plastics, such as acrylics, or other suitable materials in place of the glass panels.    </p>
+    <heading id="h-8">POLYMER FILM</heading>
+    <p id="p-34" num="34">
+      <boundary-data type="line-number">30          </boundary-data>
+As used herein, a "polymer film" means a relatively thin and rigid polymer layer that functions as a performance enhancing layer. Polymer films differ from polymer <boundary-data type="header">
+        <confidence value="8">6</confidence>
+      </boundary-data>
+      <page-break num="7"/>
+sheets, as used herein, in that polymer films do not themselves provide the necessary penetration resistance and glass retention properties to a multiple layer glazing structure, but rather provide performance improvements, such as infrared absorption or reflection character. Poly(ethylene terephthalate) is most commonly used as a polymer film.    </p>
+    <p id="p-35" num="35">
+      <boundary-data type="line-number">5          </boundary-data>
+The polymer film is preferably optically transparent (i.e. objects adjacent one side of the layer can be comfortably seen by the eye of a particular observer looking through the layer from the other side), and usually has a greater, in some embodiments significantly greater, tensile modulus regardless of composition than that of an adjacent polymer sheet. In various embodiments, the polymer film comprises a thermoplastic <boundary-data type="line-number">10   </boundary-data>
+material. Among thermoplastic materials having suitable properties are nylons, polyurethanes, acrylics, polycarbonates, <confidence value="22222222222">polyolefins</confidence>
+ such as polypropylene, cellulose acetates and triacetates, vinyl chloride polymers and copolymers and the like.    </p>
+    <p id="p-36" num="36">In various embodiments, the polymer film comprises materials such as re- stretched thermoplastic films having the noted properties, which include polyesters. In <boundary-data type="line-number">15   </boundary-data>
+various embodiments, the polymer film comprises or consists of poly(ethylene terephthalate), and, in various embodiments, the polyethylene terephthalate has been biaxially stretched to improve strength, and/or has been heat stabilized to provide low shrinkage characteristics when subjected to elevated temperatures (e.g. less than 2% shrinkage in both directions after <part-num-ref name="less than 2% shrinkage in both directions after">30</part-num-ref>
+ minutes at 1<confidence value="881">50°</confidence>
+C).    </p>
+    <p id="p-37" num="37">
+      <boundary-data type="line-number">20          </boundary-data>
+An additional type of polymer film that can be used with the present invention, which is described in U.S. Patent 6,797,396, comprises a multitude of nonmetallic layers that function to reflect infrared radiation without creating interference that can be caused by metallic layers.    </p>
+    <p id="p-38" num="38">In various embodiments, the polymer film can have a thickness of 0.013 <boundary-data type="line-number">25   </boundary-data>
+millimeters to 0.20 millimeters, 0.025 millimeters to 0.10 millimeters, or 0.04 to 0.06 millimeters. The polymer film can optionally be surface treated or coated with a functional performance layer to improve one or more properties, such as adhesion or infrared radiation reflection. These functional performance layers include, for example, a multi-layer stack for reflecting infra-red solar radiation and transmitting visible light <boundary-data type="line-number">30   </boundary-data>
+when exposed to sunlight. This multi-layer stack is known in the art (see, for example, WO 88/01230 and U.S. Patent 4,799,745) and can comprise, for example, one or more <boundary-data type="header">
+        <confidence value="8">7</confidence>
+      </boundary-data>
+      <page-break num="8"/>
+Angstroms-thick metal layers and one or more (for example two) sequentially deposited, optically cooperating dielectric layers. As is also known (see, for example, U.S. Patents 4,017,661 and 4,786,783), the metal layer(s) may optionally be electrically resistance heated for defrosting or defogging of any associated glass layers. Various coating and <boundary-data type="line-number">5   </boundary-data>
+surface treatment techniques for poly(ethylene terephthalate) film and other polymer films that can be used with the present invention are disclosed in published European Application No. <part-num-ref name="present invention are disclosed in published European Application No.">0157030.</part-num-ref>
+ Polymer films of the present invention can also include a hardcoat <confidence value="222222">and/or</confidence>
+ and antifog layer, as are known in the art.    </p>
+    <heading id="h-9">POLYMER SHEET</heading>
+    <p id="p-39" num="39">
+      <boundary-data type="line-number">10   </boundary-data>
+As used herein, a "polymer sheet" means any thermoplastic polymer composition formed by any suitable method into a thin layer that is suitable alone, or in stacks of more than one layer, for use as an interlayer that provides adequate penetration resistance and glass retention properties to laminated glazing panels. Plasticized poly(vinyl butyral) is <boundary-data type="line-number">15   </boundary-data>
+most commonly used to form polymer sheets.    </p>
+    <p id="p-40" num="40">Polymer sheets of the present invention are acoustic polymer sheets or non acoustic polymer sheets. As used herein, an "acoustic polymer sheet" is a polymer sheet that has a glass transition temperature of less than 25<confidence value="2">*</confidence>
+C and that causes an improved sound transmission loss, as defined elsewhere herein and which can be measured as <boundary-data type="line-number">20   </boundary-data>
+described elsewhere herein, of at least <part-num-ref name="improved sound transmission loss, as defined elsewhere herein and which can be measured as described elsewhere herein, of at least">2</part-num-ref>
+ decibels. In various embodiments, acoustic polymer sheets of the present invention have glass transition temperatures of less than <confidence value="882">25*</confidence>
+C, less than 20<confidence value="2">*</confidence>
+C, less than 15<confidence value="2">*</confidence>
+C, or less than 10<confidence value="2">*</confidence>
+C, while being greater than -15<confidence value="288">*C.</confidence>
+    </p>
+    <p id="p-41" num="41">Non acoustic polymer sheets are polymer sheets that both do not have a glass transition temperatures of less than 25<confidence value="2">*</confidence>
+C and that cause an improvement in sound transmission loss <boundary-data type="line-number">25   </boundary-data>
+of less than <part-num-ref name="improvement in sound transmission loss of less than">2</part-num-ref>
+ decibels when compared with an otherwise equivalent polymer sheet having a glass transition temperature of between 30-33<confidence value="2">*</confidence>
+C. Further, as used herein, an "acoustic polymer melt" is any polymer melt that, when formed into a polymer sheet, has the qualities just described for an acoustic polymer sheet, and a "non acoustic polymer melt" is any polymer melt that, when formed into a polymer sheet, has the qualities just <part-num-ref name="qualities just">30</part-num-ref>
+   described for a non acoustic polymer sheet.    </p>
+    <boundary-data type="header">
+      <confidence value="8">8</confidence>
+    </boundary-data>
+    <p id="p-42" num="42">
+      <page-break num="9"/>
+A single polymer melt that is used to form a wedge shaped polymer sheet can be formed through the blend of two or more different polymeric materials. In some embodiments, a single polymer sheet can exhibit multiple glass transition temperatures.    </p>
+    <p id="p-43" num="43">A polymer sheet formed through such a melt that has at least one glass transition <boundary-data type="line-number">5   </boundary-data>
+temperature less than 25<confidence value="2">*</confidence>
+C, as used herein, is said to have a glass transition temperature of less than 25<confidence value="288">*C.</confidence>
+    </p>
+    <p id="p-44" num="44">A single polymer sheet that is formed through a coextrusion process in which an acoustic polymer melt and a non acoustic polymer melt are coextruded to form a single wedge shaped polymer sheet having an acoustic region and a non acoustic region can <boundary-data type="line-number">10   </boundary-data>
+have two or more glass transition temperatures in which at least one of the glass transition temperatures is less than 25<confidence value="2">*</confidence>
+C and at least one of the glass transition temperatures is greater than 25<confidence value="188">°C.</confidence>
+    </p>
+    <p id="p-45" num="45">Similarly, a wedge shaped interlayer that comprises an acoustic polymer sheet and a non acoustic polymer sheet, wherein at least one of the polymer sheets is wedge shaped, <boundary-data type="line-number">15   </boundary-data>
+can have multiple glass transition temperatures wherein at least one of the glass transition temperatures is less than 25<confidence value="2">*</confidence>
+C and at least one of the glass transition temperature is greater than 25<confidence value="288">*C.</confidence>
+    </p>
+    <p id="p-46" num="46">The polymer sheet can comprise any suitable polymer, and, in a preferred embodiment, the polymer sheet comprises poly(vinyl butyral). In any of the <boundary-data type="line-number">20   </boundary-data>
+embodiments of the present invention given herein that comprise poly(vinyl butyral) as the polymeric component of the polymer sheet, another embodiment is included in which the polymer component consists of or consists essentially of poly(vinyl butyral). In these embodiments, any of the variations in additives disclosed herein can be used with the polymer sheet having a polymer consisting of or consisting essentially of poly(vinyl <boundary-data type="line-number">25   </boundary-data>
+butyral).    </p>
+    <p id="p-47" num="47">In one embodiment, the polymer sheet comprises a polymer based on partially acetalized poly(vinyl alcohol)s. In another embodiment, the polymer sheet comprises a polymer selected from the group consisting of poly(vinyl butyral), polyurethane, polyvinyl chloride, poly(ethylene vinyl acetate), combinations thereof, and the like. In <boundary-data type="line-number">30   </boundary-data>
+other embodiments, the polymer sheet comprises plasticized poly(vinyl butyral). In further embodiments the polymer sheet comprises poly(vinyl butyral) and one or more <boundary-data type="header">
+        <confidence value="8">9</confidence>
+      </boundary-data>
+      <page-break num="10"/>
+other polymers. Other polymers having a suitable glass transition temperature can also be used.    </p>
+    <p id="p-48" num="48">In any of the sections herein in which preferred ranges, values, and/or methods are given specifically for poly(vinyl butyral) (for example, and without limitation, for <boundary-data type="line-number">5   </boundary-data>
+plasticizers, component percentages, thicknesses, and characteristic-enhancing additives), those ranges also apply, where applicable, to the other polymers and polymer blends disclosed herein as useful as components in polymer sheets.    </p>
+    <p id="p-49" num="49">For embodiments comprising poly(vinyl butyral), the poly(vinyl butyral) can be produced by known acetalization processes that involve reacting poly(vinyl alcohol) with <boundary-data type="line-number">10   </boundary-data>
+butyraldehyde in the presence of an acid catalyst, followed by neutralization of the catalyst, separation, stabilization, and drying of the resin, with the understanding that in various embodiments, residual hydroxyl content will be controlled, as described elsewhere herein.    </p>
+    <p id="p-50" num="50">In various embodiments, the polymer resin can comprise less than <part-num-ref name="polymer resin can comprise less than">25</part-num-ref>
+ wt. % <boundary-data type="line-number">15   </boundary-data>
+residual ester gro<confidence value="8888">ups,</confidence>
+ <part-num-ref name="wt. % residual ester groups,">
+        <confidence value="86">20</confidence>
+      </part-num-ref>
+ <confidence value="888">wt.</confidence>
+ <confidence value="88">%,</confidence>
+ <part-num-ref name="wt. %,">
+        <confidence value="66">15</confidence>
+      </part-num-ref>
+ <confidence value="888">wt.</confidence>
+ <confidence value="8">%</confidence>
+ <confidence value="8">,</confidence>
+ <part-num-ref name="wt. % ,">
+        <confidence value="66">10</confidence>
+      </part-num-ref>
+ <confidence value="888">wt.</confidence>
+ <confidence value="8">%</confidence>
+ <confidence value="8">,</confidence>
+ <part-num-ref name="wt. % ,">
+        <confidence value="8">7</confidence>
+      </part-num-ref>
+ wt. <confidence value="8">%</confidence>
+ <confidence value="8">,</confidence>
+ <part-num-ref name="wt. % ,">
+        <confidence value="6">5</confidence>
+      </part-num-ref>
+ wt. <confidence value="8">%</confidence>
+, or less than <part-num-ref name="wt. %, or less than">
+        <confidence value="8">3</confidence>
+      </part-num-ref>
+ wt. % residual ester groups calculated as polyvinyl acetate, with the balance, other than residual hydroxyl, being an acetal, preferably butyraldehyde acetal, but optionally including other acetal groups in a minor amount, e.g., a 2-ethyl hexanal group (see, for example, U.S. Patent 5,137,954).    </p>
+    <p id="p-51" num="51">
+      <boundary-data type="line-number">20         </boundary-data>
+In various embodiments it is advantageous to use poly(vinyl butyral) having a residual poly(vinyl alcohol) content, by weight, of 9% to 50%, 10% to 50%, 11% to 40%, 15% to 30%, or 20% to 30%, although other ranges can be used as well. It is also advantageous in some applications to use poly(vinyl butyral) having a residual poly(vinyl alcohol) content, by weight, of greater than 25%, greater than 27%, or greater than 30%.    </p>
+    <p id="p-52" num="52">
+      <boundary-data type="line-number">25         </boundary-data>
+In various embodiments, the polymer sheet comprises poly(vinyl butyral) having a molecular weight greater than 30,000, 40,000, 50,000, 55,000, 60,000, 65,000, 70,000, 120,000, 250,000, or 350,000 grams per mole (g/mole or Daltons). Small quantities of a dialdehyde or trialdehyde can also be added during the acetalization step to increase molecular weight to greater than <part-num-ref name="acetalization step to increase molecular weight to greater than">350</part-num-ref>
+ Dalton<confidence value="5">s</confidence>
+ (see, for example, U.S. Patents 4,874,814;    </p>
+    <p id="p-53" num="53">
+      <boundary-data type="line-number">30   </boundary-data>
+4,814,529; and 4,654,179). As used herein, the term "molecular weight" means the weight average molecular weight.    </p>
+    <boundary-data type="header">
+      <confidence value="88">10</confidence>
+    </boundary-data>
+    <p id="p-54" num="54">
+      <page-break num="11"/>
+In various embodiments of polymer sheets of the present invention, non acoustic polymer sheets can comprise <part-num-ref name="present invention, non acoustic polymer sheets can comprise">10</part-num-ref>
+ to <part-num-ref name="to">90,</part-num-ref>
+ <part-num-ref name="to 90,">15</part-num-ref>
+ to <part-num-ref name="to">85,</part-num-ref>
+ <part-num-ref name="to 85,">20</part-num-ref>
+ to <part-num-ref name="to">60,</part-num-ref>
+ <part-num-ref name="to 60,">25</part-num-ref>
+ to <part-num-ref name="to">60,</part-num-ref>
+ <part-num-ref name="to 60,">20</part-num-ref>
+ to <part-num-ref name="to">80,</part-num-ref>
+ <part-num-ref name="to 80,">25</part-num-ref>
+ to <part-num-ref name="to">70,</part-num-ref>
+ and <part-num-ref name="to 70, and">25</part-num-ref>
+ to <part-num-ref name="to">60</part-num-ref>
+ parts plasticizer per hundred resin ("phr") parts. Of course other quantities can be used as is appropriate for the particular application. The poly(vinyl butyral) sheet <boundary-data type="line-number">5   </boundary-data>
+preferably comprises <part-num-ref name="poly(vinyl butyral) sheet preferably comprises">20</part-num-ref>
+ to <part-num-ref name="to">80,</part-num-ref>
+ and more preferably <part-num-ref name="to 80, and more preferably">25</part-num-ref>
+ to <part-num-ref name="to">60,</part-num-ref>
+ parts plasticizer per one hundred parts of resin. In some embodiments, the plasticizer has<confidence value="5">-</confidence>
+a hydrocarbon segment of less than <part-num-ref name="plasticizer has-a hydrocarbon segment of less than">20,</part-num-ref>
+ less than <part-num-ref name="plasticizer has-a hydrocarbon segment of less than 20, less than">15,</part-num-ref>
+ less than <part-num-ref name="plasticizer has-a hydrocarbon segment of less than 20, less than 15, less than">12,</part-num-ref>
+ or less than <part-num-ref name="plasticizer has-a hydrocarbon segment of less than 20, less than 15, less than 12, or less than">10</part-num-ref>
+ carbon atoms. The amount of plasticizer can be adjusted to affect the glass transition temperature of the poly(vinyl butyral) sheet.    </p>
+    <p id="p-55" num="55">
+      <boundary-data type="line-number">10          </boundary-data>
+Conventional, non acoustic poly(vinyl butyral) interlayer typically has a glass transition temperature in the range of 30-33<confidence value="2">*</confidence>
+C. Acoustic poly(vinyl butyral) can differ from non acoustic interlayer in various ways, including modification to the mole ratio of the average amount of ethylene groups bonded to acetyl groups, the degree of acetalization, the length of aldehyde groups, and/or the amount of plasticizer. For <boundary-data type="line-number">15   </boundary-data>
+instance, the acoustic interlayer can be obtained by increasing the concentration of plasticizer and/or with a reduction in the hydroxyl content of the polyvinyl butyral resin, sufficient to reduce the glass transition temperature from about 30<confidence value="2">*</confidence>
+C to about 1<confidence value="82">8*</confidence>
+C or lower. In general, higher amounts of plasticizer are added to decrease the glass transition temperature. In various embodiments of the present invention, an acoustic polymer sheet <boundary-data type="line-number">20   </boundary-data>
+comprises, for example, 30-100 phr of plasticizer, 40-90 phr of plasticizer, 50-85 phr of plasticizer, or 60-80 phr of plasticizer.    </p>
+    <p id="p-56" num="56">Acoustic polymer sheets can also be obtained by using an unmodified poly(vinyl butyral) that is typically used in conventional interlayer, a compatiblizer agent, and a plasticizer. The role of the compatiblizer agent is to make the poly(vinyl butyral) resin <boundary-data type="line-number">25   </boundary-data>
+and the plasticizer more compatible to reduce the glass transition temperature of the interlayer. The compatiblizer can be added at <part-num-ref name="compatiblizer can be added at">2</part-num-ref>
+ to <part-num-ref name="to">50</part-num-ref>
+ phr. Examples of compatiblizer agents include, but are not limited to, t<confidence value="65">ri</confidence>
+-ethylene glycol, tetra-ethylene glycol or oligomers of ethylene glycols; propylene glycol and its oligomers; <confidence value="5">t</confidence>
+ri-ethylene glycol mono-(2-ethylhexanoate), and other alkyl, aryl hydrocarbons containing ethylene glycol <part-num-ref name="phr. Examples of compatiblizer agents include, but are not limited to, tri-ethylene glycol, tetra-ethylene glycol or oligomers of ethylene glycols; propylene glycol and its oligomers; tri-ethylene glycol mono-(2-ethylhexanoate), and other alkyl, aryl hydrocarbons containing ethylene glycol">30</part-num-ref>
+   or propylene glycol moieties, and their chemical derivatives.    </p>
+    <boundary-data type="header">
+      <confidence value="88">11</confidence>
+    </boundary-data>
+    <p id="p-57" num="57">
+      <page-break num="12"/>
+Any suitable plasticizers can be added to the polymer resins of the present invention in order to form the polymer sheets. Plasticizers used in the polymer sheets of the present invention can include esters of a polybasic acid or a polyhydric alcohol, among others. Suitable plasticizers include, for example, triethylene glycol di-(2- <boundary-data type="line-number">5   </boundary-data>
+ethylbutyrate), triethylene glycol di-(2-ethylhexanoate), triethylene glycol diheptanoate, tetraethylene glycol diheptanoate, dihexyl adipate, dioctyl adipate, hexyl cyclohexyladipate, mixtures of heptyl and nonyl adipates, diisononyl adipate, heptylnonyl adipate, dibutyl sebacate, polymeric plasticizers such as the oil-modified sebacic alkyds, and mixtures of phosphates and adipates such as disclosed in U.S. Pat. No. 3,841,890 and <boundary-data type="line-number">10   </boundary-data>
+adipates such as disclosed in U.S. Pat. No. 4,144,217, and mixtures and combinations of the foregoing. Other plasticizers that can be used are mixed adipates made from C4 to C9 alkyl alcohols and cyclo C4 to C<confidence value="44">IO</confidence>
+ alcohols, as disclosed in U.S. Pat. No. 5,013,779, and <confidence value="86">C6</confidence>
+ to C<confidence value="1">8</confidence>
+ adipate esters, such as hexyl adipate. In preferred embodiments, the plasticizer is triethylene glycol di-(2-ethylhexanoate).    </p>
+    <p id="p-58" num="58">
+      <boundary-data type="line-number">15          </boundary-data>
+Adhesion control agents (ACA<confidence value="5">s</confidence>
+) can also be included in the polymer sheets of the present invention to impart the desired adhesiveness. These agents can be incorporated into the outer sheets in a three polymer sheet embodiment, for example. Any of the ACAs disclosed in U.S. Patent 5,728,472 can be used. Additionally, residual sodium acetate and/or potassium acetate can be adjusted by varying the amount of the associated <boundary-data type="line-number">20   </boundary-data>
+hydroxide used in acid neutralization. In various embodiments, polymer sheets of the present invention comprise, in addition to sodium acetate, magnesium bis(2-ethyl butyrate)(chemical abstracts number 79992-76-0). The magnesium salt can be included in an amount effective to control adhesion of the polymer sheet to glass.    </p>
+    <p id="p-59" num="59">Additives may be incorporated into the polymer sheet to enhance its performance <boundary-data type="line-number">25   </boundary-data>
+in a final product. Such additives include, but are not limited to, plasticizers, dyes, pigments, stabilizers (e.g., ultraviolet stabilizers), antioxidants, flame retardants, other IR absorbers, anti-block agents, combinations of the foregoing additives, and the like, as are known in the art.    </p>
+    <p id="p-60" num="60">Agents that selectively absorb light in the visible or near infrared spectrum can be <part-num-ref name="visible or near infrared spectrum can be">30</part-num-ref>
+   added to any of the appropriate polymer sheets. Agents that can be used include dyes and <boundary-data type="header">
+        <confidence value="88">12</confidence>
+      </boundary-data>
+      <page-break num="13"/>
+pigments such as lanthanum hexaboride (LaB<confidence value="566">6),</confidence>
+ indium tin oxide, and antimony tin oxide.    </p>
+    <p id="p-61" num="61">As used herein, "resin" refers to the polymeric (for example poly(vinyl butyral)) component that is removed from the mixture that results from the acid catalysis and <boundary-data type="line-number">5   </boundary-data>
+subsequent neutralization of the polymeric precursors. Resin will generally have other components in addition to the polymer, for example poly(vinyl butyral), such as acetates, salts, and alcohols. As used herein, "melt" refers to a mixture of resin with a plasticizer and, optionally, other additives.    </p>
+    <p id="p-62" num="62">Any suitable method can be used to produce the polymer sheets and the multiple <boundary-data type="line-number">10   </boundary-data>
+layer interlayers of the present invention. Details of suitable processes for making poly(vinyl butyral) are known to those skilled in the art (see, for example, U.S. Patents 2,282,057 and 2,282,026). In one embodiment, the solvent method described in Vinyl Acetal Polymers, in Encyclopedia of Polymer Science &amp; Technology, <confidence value="655">3rd</confidence>
+ edition, Volume <part-num-ref name="solvent method described in Vinyl Acetal Polymers, in Encyclopedia of Polymer Science &amp; Technology, 3rd edition, Volume">8,</part-num-ref>
+ pages 381-399, by B.E. Wade <part-num-ref name="solvent method described in Vinyl Acetal Polymers, in Encyclopedia of Polymer Science &amp; Technology, 3rd edition, Volume 8, pages 381-399, by B.E. Wade">(2003)</part-num-ref>
+ can be used. In another embodiment, <boundary-data type="line-number">15   </boundary-data>
+the aqueous method described therein can be used. Poly(vinyl butyral) is commercially available in various forms from, for example, Solutia Inc., St. Louis, Missouri as ButvarT<confidence value="4">M</confidence>
+ resin.    </p>
+    <p id="p-63" num="63">One exemplary method of forming a poly(vinyl butyral) layer comprises extruding molten poly(vinyl butyral) comprising resin, plasticizer, and additives and then <boundary-data type="line-number">20   </boundary-data>
+forcing the melt through a sheet die (for example, a die having an opening that is substantially greater in one dimension than in a perpendicular dimension). A sheet die can be used to produce the wedge shaped polymer sheet in such a way that the die opening is controlled and/or altered across the width of the die to produce the desired wedge thickness profile while melt is being forced through the die. Wedge shaped layers <boundary-data type="line-number">25   </boundary-data>
+can be formed by using an appropriately wedge shaped sheet die.    </p>
+    <p id="p-64" num="64">Another exemplary method of forming a poly(vinyl butyral) layer comprises casting a melt from a die onto a roller, solidifying the resin, and subsequently removing the solidified resin as a sheet. In either embodiment, the surface texture at either or both sides of the layer may be controlled by adjusting the surfaces of the die opening or by <boundary-data type="line-number">30   </boundary-data>
+providing texture at the roller surface. Other techniques for controlling the layer texture include varying parameters of the materials (for example, the water content of the resin <boundary-data type="header">
+        <confidence value="88">13</confidence>
+      </boundary-data>
+      <page-break num="14"/>
+and/or the plasticizer, the melt temperature, molecular weight distribution of the poly(vinyl butyral), or combinations of the foregoing parameters). Furthermore, the layer can be configured to include spaced projections that define a temporary surface irregularity to facilitate the de-airing of the layer during lamination processes after which <boundary-data type="line-number">5   </boundary-data>
+the elevated temperatures and pressures of the laminating process cause the projections to melt into the layer, thereby resulting in a smooth finish.    </p>
+    <p id="p-65" num="65">Polymer sheets of the present invention that comprise acoustic and non acoustic regions can be produced by any method known in the art. In a typical method, two or more melts comprising polymer resin, plasticizer, and any desired additives can be <boundary-data type="line-number">10   </boundary-data>
+independently formed and coextruded to form a single polymer sheet having regions corresponding to each melt used. For example a first melt that, if used alone, would result in a sheet with a glass transition temperature of 20<confidence value="2">*</confidence>
+C, and a second melt that, if used alone, would result in a sheet with a glass transition temperature of 30<confidence value="2">*</confidence>
+C, can be coextruded to form a polymer sheet having a first region and a second region, each <boundary-data type="line-number">15   </boundary-data>
+approximating the shape of an individual sheet, wherein the first region has a glass transition temperature of 20<confidence value="2">*</confidence>
+C and the second region has a glass transition temperature of <confidence value="88288">30*C.</confidence>
+    </p>
+    <p id="p-66" num="66">Interlayers of the present invention that comprise more than one polymer sheet can be produced through a calendaring or pre-la<confidence value="68">mi</confidence>
+nation process. In a typical method, an <boundary-data type="line-number">20   </boundary-data>
+acoustic polymer sheet and a non acoustic polymer sheet, wherein at least one of the sheets is wedge shaped, are combined under pressure and heat to form an interlayer. The acoustic polymer sheet, if wedge shaped, is formed through a single polymer melt or through a coextrusion process as described in various embodiments in the previous paragraphs.    </p>
+    <p id="p-67" num="67">
+      <boundary-data type="line-number">25          </boundary-data>
+The following paragraphs describe various techniques that can be used to improve and/or measure the characteristics of the polymer sheet.    </p>
+    <p id="p-68" num="68">The clarity of a polymer sheet, and particularly a poly(vinyl butyral) layer, can be determined by measuring the haze value, which is a quantification of the amount of light scattered away from the direction of the incident beam in passing through the layer. The <boundary-data type="line-number">30   </boundary-data>
+percent haze can be measured according to the following technique. An apparatus for measuring the amount of haze, a Hazemeter, Model D25, which is available from Hunter <boundary-data type="header">
+        <confidence value="88">14</confidence>
+      </boundary-data>
+      <page-break num="15"/>
+Associates (Reston, VA), can be used in accordance with ASTM D1003-61 (Re-approved <confidence value="8">1</confidence>
+977)-Procedure A, using Illuminant C, at an observer angle of <part-num-ref name="observer angle of">2</part-num-ref>
+ degrees. In various embodiments of the present invention, percent haze is less than 5%, less than 3%, and less than 1%.    </p>
+    <p id="p-69" num="69">
+      <boundary-data type="line-number">5         </boundary-data>
+The visible transmittance can be quantified using a UV-Vis-NIR spectrophotometer such as the Lambda <part-num-ref name="Lambda">900</part-num-ref>
+ made by Perkin Elmer Corporation by methods described in international standard ISO 9050:1990. In various embodiments, the transmittance through a polymer sheet of the present invention is at least 60%, at least 70%, or at least 80%.    </p>
+    <p id="p-70" num="70">
+      <boundary-data type="line-number">10         </boundary-data>
+Pummel adhesion can be measured according to the following technique, and where "pummel" is referred to herein to quantify adhesion of a polymer sheet to glass, the following technique is used to determine pummel. Two-ply glass laminate samples are prepared with standard autoclave lamination conditions. The laminates are cooled to about -1<confidence value="82">8*</confidence>
+C (0<confidence value="2">*</confidence>
+F) and manually pummeled with a hammer to break the glass. All <boundary-data type="line-number">15   </boundary-data>
+broken glass that is not adhered to the poly(vinyl butyral) layer is then removed, and the amount of glass left adhered to the poly(vinyl butyral) layer is visually compared with a set of standards. The standards correspond to a scale in which varying degrees of glass remain adhered to the poly(vinyl butyral) layer. In particular, at a pummel standard of zero, no glass is left adhered to the poly(vinyl butyral) layer. At a pummel standard of <boundary-data type="line-number">20   </boundary-data>
+      <part-num-ref name="pummel standard of">10,</part-num-ref>
+ 100% of the glass remains adhered to the poly(vinyl butyral) layer. Poly(vinyl butyral) layers of the present invention can have, for example, a pummel value of between <part-num-ref name="pummel value of between">3</part-num-ref>
+ and <part-num-ref name="and">10.</part-num-ref>
+    </p>
+    <p id="p-71" num="71">The "yellowness index" of a polymer sheet can be measured according to the following: Transparent molded disks of polymer sheet <part-num-ref name="following: Transparent molded disks of polymer sheet">1</part-num-ref>
+ cm thick, having smooth <boundary-data type="line-number">25   </boundary-data>
+polymeric surfaces which are essentially plane and parallel, are formed. The index is measured according to ASTM method D <part-num-ref name="index is measured according to ASTM method D">1925,</part-num-ref>
+ "Standard Test Method for Yellowness Index of Plastics" from spectrophotometric light transmittance in the visible spectrum.    </p>
+    <p id="p-72" num="72">Values are corrected to 1 cm thickness using measured specimen thickness. In various embodiments of the present invention, a polymer sheet can have a yellowness index of <part-num-ref name="yellowness index of">12</part-num-ref>
+ <part-num-ref name="">30</part-num-ref>
+   or less, <part-num-ref name="or less,">10</part-num-ref>
+ or less, or <part-num-ref name="or less, or">8</part-num-ref>
+ or less.    </p>
+    <boundary-data type="header">
+      <confidence value="88">15</confidence>
+    </boundary-data>
+    <p id="p-73" num="73">
+      <page-break num="16"/>
+As used herein glass transition temperature of polymer sheets is determined by rheometric dynamic shear mode analysis using the following procedure. A thermoplastic polymer sheet is molded into a sample disc of <part-num-ref name="sample disc of">25</part-num-ref>
+ millimeters (mm) in diameter. The polymeric sample disc is placed between two 25 mm diameter parallel plate test fixtures <boundary-data type="line-number">5   </boundary-data>
+of a Rheometrics Dynamic Spectrometer II (available from Rheometrics, Incorporated, Piscataway, New Jersey). The polymer sheet sample disc is tested in shear mode at an oscillation frequency of <part-num-ref name="oscillation frequency of">1</part-num-ref>
+ Hertz as the temperature of the sample is increased from -20<confidence value="28">*C</confidence>
+ to 70<confidence value="2">*</confidence>
+C at a rate of 2<confidence value="2">*</confidence>
+C/minute. The position of the maximum value of tan delta (damping) plotted as dependent on temperature is used to determine glass transition <boundary-data type="line-number">10   </boundary-data>
+temperature.    </p>
+    <p id="p-74" num="74">As used herein, conventional laminated glass is formed through laminating a conventional interlayer consisting of a non-acoustic polymer sheet having the same shape as an interlayer of the present invention between two sheets of rigid glass panes. For the purpose of the present invention, the conventional laminated glass is referred to as <boundary-data type="line-number">15   </boundary-data>
+"reference laminate panel".    </p>
+    <p id="p-75" num="75">Improvement in acoustic insulation as used to characterize glass laminates consisting of the interlayers of the present invention is determined with reference to a reference laminate panel as described in previous paragraph. In typical laminates with two outer layers of glass, the "combined glass thickness" is the sum of the thickness of <boundary-data type="line-number">20   </boundary-data>
+the two layers of glass; in more complex laminates with three or more layers of glass, the combined glass thickness would be the sum of the three or more layers of glass.    </p>
+    <p id="p-76" num="76">For purposes of the present invention a "coincident frequency" means the frequency at which a panel exhibit a dip in sound transmission loss due to "coincident effect" (see Lu, J; Windshields with New PVB Interlayer for Vehicle Interior Noise <boundary-data type="line-number">25   </boundary-data>
+Reduction and Sound Quality Improvement - SAE Paper # 2003-01-1587). The coincident frequency of the reference panel is typically in the range of 2,000 to 6,000 Hertz, and can be empirically determined from a monolithic sheet of glass having a thickness equal to the combined glass thickness of glass in the reference panel from the algorithm <boundary-data type="line-number">
+        <confidence value="66">30</confidence>
+                                           </boundary-data>
+      <confidence value="21">-c</confidence>
+ <confidence value="885">15,</confidence>
+000 <confidence value="5">d</confidence>
+ <boundary-data type="header">
+        <confidence value="88">16</confidence>
+      </boundary-data>
+      <page-break num="17"/>
+where "d" is the total glass thickness in millimeters and <confidence value="66">"f</confidence>
+ <confidence value="5">c</confidence>
+" is in Hertz.    </p>
+    <p id="p-77" num="77">For purposes of this invention, improvement in acoustic performance can be measured by an increase in sound transmission loss at the coincident frequency (reference frequency) of the reference panel.</p>
+    <p id="p-78" num="78">
+      <boundary-data type="line-number">5         </boundary-data>
+"Sound transmission loss" is determined for a laminate of the present invention or conventional reference panel of fixed dimensions with ASTM E90 <part-num-ref name="present invention or conventional reference panel of fixed dimensions with ASTM E90">(95)</part-num-ref>
+ at a fixed temperature of <part-num-ref name="fixed temperature of">20</part-num-ref>
+ <confidence value="28">*C</confidence>
+ Glass laminates using interlayers of the present invention can be prepared by known procedures, for example as disclosed in U.S. Patents 5,024,895; 5,091,258;    </p>
+    <p id="p-79" num="79">
+      <boundary-data type="line-number">10   </boundary-data>
+5,145,744; 5,189,551;5,264,058 and 5,529,654. Preferred glass is heat strengthened, float glass and may be tinted or coated with metal and/or metal oxide layers to reflect specific portions of the electromagnetic spectrum, for example, infrared. Preferred glass laminates are made with glass that is not more than 3.2 mm thick, preferably thinner, for example not more than 2.5 mm thick, and more preferably not more than 2.3 mm thick. A glass <boundary-data type="line-number">15   </boundary-data>
+laminate can comprise glass of different thicknesses, for example 1.6 mm and 2.3 mm.    </p>
+    <p id="p-80" num="80">In a typical safety glass lamination process, a three layer assembly of glass, polymer interlayer, and glass is assembled and heated to a glass temperature of about 25<confidence value="1">°</confidence>
+C to <confidence value="882">50*</confidence>
+C and then passed through a pair of nip rolls to expel trapped air. The compressed assembly is then heated, for example by infrared radiation or in a convection oven, to a <boundary-data type="line-number">20   </boundary-data>
+temperature of about 60<confidence value="2">*</confidence>
+C to 1<confidence value="882">10*</confidence>
+C for a short period, for example about <part-num-ref name="short period, for example about">1</part-num-ref>
+ to <part-num-ref name="to">5</part-num-ref>
+ minutes.    </p>
+    <p id="p-81" num="81">The heated assembly is then passed through a second pair of nip rolls followed by autoclaving the assembly at about 1<confidence value="882">30*</confidence>
+C to 1<confidence value="882">50*</confidence>
+C and about 1,000 to 2,000 kilo Pascals for about <part-num-ref name="assembly at about 130*C to 150*C and about 1,000 to 2,000 kilo Pascals for about">30</part-num-ref>
+ minutes. Non-autoclave methods as disclosed in US Patent 5,536,347 are also useful.    </p>
+    <p id="p-82" num="82">
+      <boundary-data type="line-number">
+        <confidence value="88">25</confidence>
+      </boundary-data>
+     </p>
+    <heading id="h-10">EXAMPLES</heading>
+    <p id="p-83" num="83">The following examples are intended to illustrate and not limit or restrict the scope of the invention. Laminates used to illustrate the invention are prepared using the following materials:</p>
+    <p id="p-84" num="84">
+      <boundary-data type="line-number">30          </boundary-data>
+3GEH: triethylene glycol di(2-ethylhexanoate) plasticizer.    </p>
+    <p id="p-85" num="85">Glass: annealed float glass in thickness of 2.1 or 2.3 millimeters.</p>
+    <boundary-data type="header">
+      <confidence value="88">17</confidence>
+    </boundary-data>
+    <p id="p-86" num="86">
+      <page-break num="18"/>
+PVB: Non wedge shaped poly(vinyl butyral) having 18.7% hydroxyl content, containing 38 phr 3GEH and having a glass transition temperature of <part-num-ref name="glass transition temperature of">30</part-num-ref>
+ <confidence value="2">*</confidence>
+C, at a thickness of 0.38 mm <part-num-ref name="thickness of 0.38 mm">(15</part-num-ref>
+ m<confidence value="6688">il).</confidence>
+    </p>
+    <p id="p-87" num="87">C-PVB: Conventional wedge shaped poly(vinyl butyral) having 18.7% hydroxyl <boundary-data type="line-number">5   </boundary-data>
+content, containing 38 phr 3GE<confidence value="5">H</confidence>
+ and having a glass transition temperature of <part-num-ref name="glass transition temperature of">30</part-num-ref>
+ <confidence value="2">*</confidence>
+C, at a thickness in one edge of the sheet of 0.76 mm <part-num-ref name="sheet of 0.76 mm">(30</part-num-ref>
+ m<confidence value="66">il</confidence>
+) and on the opposite edge of 1.14 mm <part-num-ref name="opposite edge of 1.14 mm">(45</part-num-ref>
+ m<confidence value="66">il</confidence>
+), and a sheet width of 1,000 mm.    </p>
+    <p id="p-88" num="88">A-PVB1: Non-wedge shaped acoustic poly(vinyl butyral) having low (16%) hydroxyl content, containing <confidence value="68">50</confidence>
+ phr 3GEH plasticizer, having a glass transition <boundary-data type="line-number">10  </boundary-data>
+temperature of <part-num-ref name="glass transition temperature of">18</part-num-ref>
+ <confidence value="2">*</confidence>
+C, and being 0.5 mm <part-num-ref name="*C, and being 0.5 mm">(20</part-num-ref>
+ m<confidence value="66">il</confidence>
+) thick.    </p>
+    <p id="p-89" num="89">A-PVB2: Wedge shaped acoustic poly(vinyl butyral) having low (16%) hydroxyl content, containing 50 phr 3GEH plasticizer, having a glass transition temperature of <part-num-ref name="glass transition temperature of">18</part-num-ref>
+ <confidence value="2">*</confidence>
+ C, at a thickness in one edge of the sheet of 1.0 mm and on the opposite edge of 1.42.    </p>
+    <p id="p-90" num="90">A-PVB3: Non-wedge shaped co-extruded three-layer acoustic poly(vinyl butyral) <boundary-data type="line-number">15   </boundary-data>
+being 0.80 mm thick, wherein two outer layers containing 38 phr 3GEH and having a glass transition temperature of about 30<confidence value="2">*</confidence>
+C and the inner layer having low (12%) hydroxyl content, containing <part-num-ref name="inner layer having low (12%) hydroxyl content, containing">75</part-num-ref>
+ phr 3GEH plasticizer, having a glass transition temperature of about <part-num-ref name="glass transition temperature of about">2</part-num-ref>
+ <confidence value="2">*</confidence>
+C, and being 0.13 mm <part-num-ref name="*C, and being 0.13 mm">(5</part-num-ref>
+ m<confidence value="66">il</confidence>
+) thick.    </p>
+    <p id="p-91" num="91">Panels for acoustic testing comprising glass with various polymeric interlayers are <boundary-data type="line-number">20   </boundary-data>
+constructed into 48 x <part-num-ref name="x">75</part-num-ref>
+ cm panels of components assembled as indicated in Tables <part-num-ref name="cm panels of components assembled as indicated in Tables">1</part-num-ref>
+ through <part-num-ref name="through">4.</part-num-ref>
+ PVB interlayer film is conditioned in a humidity cabinet to a targeted moisture level of 0.43%, and hand laid up on a glass sheet preheated to <part-num-ref name="glass sheet preheated to">40</part-num-ref>
+ <confidence value="2">*</confidence>
+C. In case of panels containing multilayer interlayer the individual layers are stacked on the preheated glass in the order indicated. A second glass sheet preheated to 40<confidence value="2">*</confidence>
+C is placed on top of <boundary-data type="line-number">25   </boundary-data>
+the stacked interlayer sheets. The panel is then compressed by passing through nip rollers adjusted to <part-num-ref name="panel is then compressed by passing through nip rollers adjusted to">40</part-num-ref>
+ psig to de-air the structure and to tack the interlayer to the glass surface. The "de-aired" panel is placed in a preheated oven at 105<confidence value="2">*</confidence>
+C for about <part-num-ref name="preheated oven at 105*C for about">20</part-num-ref>
+ minutes and passed through the nip rollers a second time for further de-airing and to edge seal the panel. The panel is then air autoclaved (heated at elevated temperature and pressure).    </p>
+    <p id="p-92" num="92">
+      <boundary-data type="line-number">
+        <confidence value="88">30</confidence>
+      </boundary-data>
+ Table 1 (Prior Art) <boundary-data type="header">
+        <confidence value="88">18</confidence>
+      </boundary-data>
+      <page-break num="19"/>
+No.      Interlayer Components       Wedge Angle<confidence value="5">,</confidence>
+ mrad        T<confidence value="2">g</confidence>
+ <confidence value="8288">("C)</confidence>
+ <part-num-ref name="(Prior Art) No.      Interlayer Components       Wedge Angle, mrad        Tg (&quot;C)">1</part-num-ref>
+       PVB                          <part-num-ref name="PVB">0</part-num-ref>
+                       <part-num-ref name="">30</part-num-ref>
+ <part-num-ref name="">2</part-num-ref>
+        C-PVB                       0.38                     <part-num-ref name="C-PVB                       0.38">30</part-num-ref>
+ <boundary-data type="line-number">5                        </boundary-data>
+Table <part-num-ref name="Table">2</part-num-ref>
+ (Prior Art, Reference Panels) No.   Interlayer   Glass*   Coincident Fre<confidence value="5">q</confidence>
+. (Hz)  STL at coincident <confidence value="2222">freq</confidence>
+ (dB) <part-num-ref name="(Prior Art, Reference Panels) No.   Interlayer   Glass*   Coincident Freq. (Hz)  STL at coincident freq (dB)">3.</part-num-ref>
+    C-PVB       2.1-mm    <part-num-ref name="(Prior Art, Reference Panels) No.   Interlayer   Glass*   Coincident Freq. (Hz)  STL at coincident freq (dB) 3.    C-PVB       2.1-mm">4000</part-num-ref>
+                 <part-num-ref name="">31</part-num-ref>
+ <part-num-ref name="">4.</part-num-ref>
+    C-PVB        2.3-mm   <part-num-ref name="4.    C-PVB        2.3-mm">3150</part-num-ref>
+                 <part-num-ref name="">31</part-num-ref>
+ * Glass laminate consists of glass sheet/interlayer/glass sheet. The thickness of each <boundary-data type="line-number">10   </boundary-data>
+glass sheet is indicated in the Table above.    </p>
+    <p id="p-93" num="93">Table <confidence value="8">3</confidence>
+ No.      <confidence value="2222222222">Interlayer</confidence>
+ Components  Wedge Angle, mrad             T<confidence value="2">g</confidence>
+ <confidence value="8288">("C)</confidence>
+ <part-num-ref name="No.      Interlayer Components  Wedge Angle, mrad             Tg (&quot;C)">5</part-num-ref>
+       A-PVB2                       0.42                     <part-num-ref name="A-PVB2                       0.42">18</part-num-ref>
+ <boundary-data type="line-number">15   </boundary-data>
+      <part-num-ref name="">6</part-num-ref>
+       A-PVB2<confidence value="5">/</confidence>
+PVB                   0.42                     <part-num-ref name="A-PVB2/PVB                   0.42">18</part-num-ref>
+ and <part-num-ref name="and">30</part-num-ref>
+ <part-num-ref name="">7</part-num-ref>
+        A-PVB<confidence value="4">1</confidence>
+/C-PVB                0.38                     <part-num-ref name="A-PVB1/C-PVB                0.38">18</part-num-ref>
+ and <part-num-ref name="and">30</part-num-ref>
+ <part-num-ref name="">8</part-num-ref>
+        A-PVB3/C-PVB                0.38                    <part-num-ref name="A-PVB3/C-PVB                0.38">2</part-num-ref>
+ and <part-num-ref name="and">30</part-num-ref>
+ <part-num-ref name="">9</part-num-ref>
+        A-PVB<confidence value="4">l</confidence>
+/A-PVB2               0.42                     <part-num-ref name="A-PVBl/A-PVB2               0.42">18</part-num-ref>
+ <boundary-data type="line-number">20                                     </boundary-data>
+Table <part-num-ref name="Table">4</part-num-ref>
+ No. Interlayer components* STL at the reference <confidence value="2222">freq</confidence>
+ (dB) Improvement in STL (d<confidence value="66">B)</confidence>
+ <part-num-ref name="reference freq (dB) Improvement in STL (dB)">10</part-num-ref>
+    A-PVB2                     <part-num-ref name="A-PVB2">38</part-num-ref>
+                        <part-num-ref name="">7</part-num-ref>
+ <part-num-ref name="">11</part-num-ref>
+    A-PVB2/PVB                 <part-num-ref name="A-PVB2/PVB">38</part-num-ref>
+                        <part-num-ref name="">7</part-num-ref>
+ <part-num-ref name="">12</part-num-ref>
+    A-PVB<confidence value="4">1</confidence>
+/C-PVB               <part-num-ref name="A-PVB1/C-PVB">37</part-num-ref>
+                        <part-num-ref name="">6</part-num-ref>
+ <boundary-data type="line-number">25   </boundary-data>
+      <part-num-ref name="">13</part-num-ref>
+    A-PVB3/C-PVB               <part-num-ref name="A-PVB3/C-PVB">38</part-num-ref>
+                        <part-num-ref name="">7</part-num-ref>
+ * Glass laminates for STL measurements consist of glass sheet/interlayer components/glass sheet. The thickness of each glass sheet is 2.1-mm.    </p>
+    <p id="p-94" num="94">By virtue of the present invention, it is now possible to provide acoustic wedge <part-num-ref name="present invention, it is now possible to provide acoustic wedge">30</part-num-ref>
+   shaped interlayers that reduce sound transmission through a windshield.    </p>
+    <boundary-data type="header">
+      <confidence value="88">19</confidence>
+    </boundary-data>
+    <p id="p-95" num="95">
+      <page-break num="20"/>
+While the invention has been described with reference to exemplary embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a <boundary-data type="line-number">5   </boundary-data>
+particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiments disclosed as the best mode contemplated for carrying out this invention, but that the invention will include all embodiments falling within the scope of the appended claims.    </p>
+    <p id="p-96" num="96">
+      <boundary-data type="line-number">10         </boundary-data>
+It will further be understood that any of the ranges, values, or characteristics given for any single component of the present invention can be used interchangeably with any ranges, values, or characteristics given for any of the other components of the invention, where compatible, to form an embodiment having defined values for each of the components, as given herein throughout. For example, a polymer sheet can be formed <boundary-data type="line-number">15   </boundary-data>
+comprising wedge shapes in any of the ranges given in addition to any of the ranges given for plasticizer, where appropriate, to form many permutations that are within the scope of the present invention but that would be cumbersome to list.    </p>
+    <p id="p-97" num="97">Any figure reference numbers given within the abstract or any claims are for illustrative purposes only and should not be construed to limit the claimed invention to <boundary-data type="line-number">20   </boundary-data>
+any one particular embodiment shown in any figure.    </p>
+    <p id="p-98" num="98">Figures are not drawn to scale unless otherwise indicated.</p>
+    <p id="p-99" num="99">Each reference, including journal articles, patents, applications, and books, referred to herein is hereby incorporated by reference in its entirety.</p>
+    <boundary-data type="header">
+      <confidence value="88">20</confidence>
+    </boundary-data>
+  </description>
+</us-patent-application>
+

prior_art/11082128.xml

@@ -0,0 +1,51 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11082128</doc-number>
+        <date>2008-07-18</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">Atty. Docket No. 600189.400 </p>
+    <heading id="h-1">AMENDMENTS TO THE SPECIFICATION</heading>
+    <p id="p-2" num="2">Please replace the paragraph [0068], located on page <part-num-ref name="paragraph [0068], located on page">18</part-num-ref>
+ with the following:    </p>
+    <p id="p-3" num="3">
+      <confidence value="5">[</confidence>
+0068<confidence value="5">]</confidence>
+      Computer programs incorporating various features of the present invention may be encoded on various computer readable media for storage and/<confidence value="686">or-</confidence>
+ <confidence value="8788777">transmi</confidence>
+ssi<confidence value="778">on;</confidence>
+    </p>
+    <p id="p-4" num="4">suitable media include magnetic disk or tape, optical storage media such as CD or DVD, <confidence value="88">an</confidence>
+d flash memory, for <confidence value="2222222222">exampleand</confidence>
+ <confidence value="222222">carier</confidence>
+ <confidence value="8">s</confidence>
+ignal<confidence value="8">s</confidence>
+ a<confidence value="8">d</confidence>
+apte<confidence value="8">d</confidence>
+ <confidence value="666">for</confidence>
+ <confidence value="888888888878">transmission</confidence>
+ <confidence value="556">via</confidence>
+  <confidence value="5">,</confidence>
+ <confidence value="2222222">eptica1</confidence>
+, and/or wireless networks <confidence value="88">co</confidence>
+nf<confidence value="88">or</confidence>
+mi<confidence value="8">n</confidence>
+g to a variety <confidence value="2">o</confidence>
+f <confidence value="2222222222">proetocols</confidence>
+, in<confidence value="6">c</confidence>
+ludin<confidence value="6">g</confidence>
+ <confidence value="2222222">Intemet</confidence>
+. Computer readable media encoded with the program code may be packaged with a compatible device or provided separately from other devices<confidence value="588828884888855">-(eg,via4ntemet</confidence>
+ <confidence value="22222222">dewnlead</confidence>
+).    </p>
+    <p id="p-5" num="5">{00371354.DOC;}                      <confidence value="6">2</confidence>
+     </p>
+  </description>
+</us-patent-application>
+

prior_art/11097991.xml

@@ -0,0 +1,565 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11097991</doc-number>
+        <date>2008-05-16</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <boundary-data type="header">
+      <confidence value="2222">Appl</confidence>
+. No. 11<confidence value="5">/</confidence>
+097<confidence value="5">,</confidence>
+991 - Re<confidence value="686">ply</confidence>
+ to N<confidence value="48866">otice</confidence>
+ <confidence value="66">to</confidence>
+ File Corr<confidence value="6686">ecte</confidence>
+d A<confidence value="665856">pplica</confidence>
+tio<confidence value="5">n</confidence>
+ <confidence value="55656">dated</confidence>
+ <confidence value="222222">ebry0u</confidence>
+ <confidence value="2">!</confidence>
+    </boundary-data>
+    <p id="p-1" num="1">Amendments to the Specification:</p>
+    <p id="p-2" num="2">Please amend the specification as follows:</p>
+    <p id="p-3" num="3">Please replace paragraph [0006] at page 2, with the following amended paragraph.</p>
+    <p id="p-4" num="4">[00<confidence value="686">06]</confidence>
+       To achieve <confidence value="222222222222">cryoablation</confidence>
+, the ent<confidence value="8">i</confidence>
+re tumor must be frozen to <confidence value="5">"</confidence>
+kill<confidence value="5">"</confidence>
+ temperatures in the range of [[-40 <confidence value="25">[C</confidence>
+]] -40<confidence value="25">*C</confidence>
+, the Freeze/Thaw, F/T, cycle must be repeated, and the kill temperature<confidence value="5">,</confidence>
+ out to the tumor margins, must be maintained for a few minutes, designated the, "hold time," during <confidence value="8">c</confidence>
+ryosurgery. Despite a strict adherence to these standards, which are time consuming, certain tumors like prostate or metastatic liver cancer show a <part-num-ref name="">20</part-num-ref>
+ to <part-num-ref name="to">40</part-num-ref>
+ % post procedure recurrence. Whether the cause of this f<confidence value="8">a</confidence>
+ilure is disease-based or technique-<confidence value="66">re</confidence>
+lated, it's recognized that cryosurgery needs the support of adjunctive therapy in the form of <confidence value="588488">chemo-</confidence>
+ or radiotherapy to inc<confidence value="8">r</confidence>
+ease the rate of cell death at margins of the cryogenic lesion where the cell fate is known to be in balance for several days post treatment<confidence value="5">.</confidence>
+    </p>
+    <p id="p-5" num="5">Please replace paragraph [0007<confidence value="5">]</confidence>
+ at page 2, with the following amended paragraph.    </p>
+    <p id="p-6" num="6">[0007<confidence value="5">]</confidence>
+       The pretreatment of a tumor with a pro-inflammatory protein like T<confidence value="5">N</confidence>
+F-, based on the hypothesis that vascular- mediated injur<confidence value="8">y</confidence>
+ is responsible for defining the edge of the cryo lesion in microvascular-perfused tissue, augments the <confidence value="2222222222">cryoinjury</confidence>
+ that occurs at much higher temperatures, close to [[0<confidence value="2">E</confidence>
+ <confidence value="5246">CC]]</confidence>
+ <confidence value="22">Q_</confidence>
+ <confidence value="4">.</confidence>
+ <confidence value="6">d</confidence>
+ue to a inflammatory pre-sensitization of the <confidence value="2222222222222222">microvasculature</confidence>
+, Bo H. <confidence value="2222">Chao</confidence>
+, <confidence value="5">X</confidence>
+iaoming He and <confidence value="68">J.</confidence>
+C. <confidence value="2222222">Bischof</confidence>
+, C<confidence value="5">r</confidence>
+yobiology <part-num-ref name="microvasculature, Bo H. Chao, Xiaoming He and J.C. Bischof, Cryobiology">2004,</part-num-ref>
+ <part-num-ref name="microvasculature, Bo H. Chao, Xiaoming He and J.C. Bischof, Cryobiology 2004,">49,</part-num-ref>
+ 10-27.    </p>
+    <p id="p-7" num="7">Although this pretreatment seems better in terms of ablation completeness, it doesn't act directly on tumor cells and particularly on cells that may have escaped the margin of the <confidence value="2222222222">cryolesion</confidence>
+.    </p>
+    <boundary-data type="header">
+      <confidence value="8">2</confidence>
+    </boundary-data>
+    <boundary-data type="header">
+      <confidence value="825">Api</confidence>
+ <confidence value="447">NLo</confidence>
+ <confidence value="855">11/</confidence>
+097<confidence value="5">,</confidence>
+991 - Re<confidence value="656">ply</confidence>
+ to Notice t<confidence value="5">o</confidence>
+ Fi<confidence value="68">le</confidence>
+ <confidence value="2451458882888855">pQrgi.Applcation</confidence>
+ <confidence value="888815288558885684456555">date-d.Eebruary.20._2008</confidence>
+    </boundary-data>
+    <p id="p-8" num="8">
+      <page-break num="2"/>
+Please replace paragraph [0010<confidence value="5">]</confidence>
+ at page 3, with the following amended paragraph<confidence value="8">.</confidence>
+    </p>
+    <p id="p-9" num="9">
+      <confidence value="5">1</confidence>
+0010<confidence value="5">1</confidence>
+      <confidence value="6">I</confidence>
+ntra-tumor chemotherapy using different drugs and vectors or carriers of those drugs has been proposed to improve loca<confidence value="8">l</confidence>
+ delive<confidence value="8">r</confidence>
+y of chemotherapeutic agents and decrease their side effects. These new formulations, microspheres, liposomes, matrixes, etc<confidence value="25">.,</confidence>
+ have the capability of slowly releasing the active component at therapeutic dose b<confidence value="5">y</confidence>
+ dif<confidence value="8">f</confidence>
+usion through membrane and/or progressive degradatio<confidence value="684">n/J</confidence>
+ysis at bod<confidence value="8">y</confidence>
+ temperature. Such sustained release exposes ce<confidence value="8">l</confidence>
+ls to higher concentration of the c<confidence value="8">y</confidence>
+toto<confidence value="8">x</confidence>
+ic drug for longer periods of time, prevent side effects and result in better outcome. The agents'carriers are deposited locally or into the vascular bed of the tumor as the sole treatment and/or as a pre-adjuvant or adjuvant therapy to surgical excision, radiation therapy, 5-FU encapsulation and glioblastomas<confidence value="4">.</confidence>
+ as taught in U. S.    </p>
+    <p id="p-10" num="10">Patent No. 6,803,052, or <confidence value="8">m</confidence>
+icrowave <confidence value="8">h</confidence>
+yperthermia, as taught in U. S. Patent No. 6,788<confidence value="6688">,977</confidence>
+ and U. S. Patent No. 6,623,430. For the latter, moderate <confidence value="222222222222">byperthermia</confidence>
+ of the target organ, is triggering the release of the drug out <confidence value="5">o</confidence>
+f the the<confidence value="6688">rmo-</confidence>
+sensitive, solid-matrix <confidence value="22222222222">microsphere</confidence>
+ containing <confidence value="222222222222">doxorubicine</confidence>
+, Thermod<confidence value="6825">ox@,</confidence>
+ The company has initiated clinical studies for a combined treatment of liver malignant tumors that inject Thermodox<confidence value="2">®</confidence>
+ at periphery of a <confidence value="22222222222222">radiofrequency</confidence>
+ lesion, where tissue temperature is about [[<confidence value="5">+</confidence>
+41 <confidence value="25">[C</confidence>
+]] <confidence value="288">+41</confidence>
+ <confidence value="5">C</confidence>
+. These treatments rely for their safety and efficacy on the precise, homogeneous deposition and known degradation rates of the carriers. Since these carriers cannot be imaged, there is no method to determine, in real time, the optimum delivery, in ter<confidence value="8">m</confidence>
+s of spatial distribution and dose. Such assessments are based only on direct visualization, at open surgery, and on indirect measurement of tissue temperature.    </p>
+    <boundary-data type="header">
+      <confidence value="7">3</confidence>
+    </boundary-data>
+    <boundary-data type="header">
+      <confidence value="87777">Apple</confidence>
+ No. 11<confidence value="5">/</confidence>
+097<confidence value="5">,</confidence>
+991 - Re<confidence value="686">ply</confidence>
+ to Notice to File Corrected A<confidence value="666">ppl</confidence>
+icatio<confidence value="5">n</confidence>
+ dated Febr<confidence value="66">ua</confidence>
+ry 20<confidence value="5">,</confidence>
+ <confidence value="6222">2008</confidence>
+    </boundary-data>
+    <p id="p-11" num="11">
+      <page-break num="3"/>
+Please replace the Brief Description of the D<confidence value="66">ra</confidence>
+wing at page <part-num-ref name="Drawing at page">
+        <confidence value="5">8</confidence>
+,      </part-num-ref>
+ with the follow<confidence value="8">i</confidence>
+ng rewritten paragraphs.:    </p>
+    <p id="p-12" num="12">
+      <confidence value="655666">[00231</confidence>
+       Figu<confidence value="58">re</confidence>
+ <confidence value="5">1</confidence>
+ illustrates enhanced inhibition of viable tumor cell growt<confidence value="8">h</confidence>
+ in human prostate tumors receiving combined treatments <confidence value="66">(C</confidence>
+ryo+<confidence value="5">5</confidence>
+FU mcaps<confidence value="6">)</confidence>
+ <confidence value="8">c</confidence>
+om<confidence value="8">p</confidence>
+ared to increased tumor cell growth of the tumors treated with only <confidence value="22222222222">crvosurgery</confidence>
+. This figu<confidence value="8">r</confidence>
+e shows is<confidence value="685">-a4</confidence>
+able<confidence value="58858556">-shewing</confidence>
+ the synergistic effect of the combination of cryosurgical ablation and microencapsulated chemotherapy deposited at frozen region margins[[;]<confidence value="52">]_</confidence>
+ <part-num-ref name="combination of cryosurgical ablation and microencapsulated chemotherapy deposited at frozen region margins[[;]]_">
+        <confidence value="2">1</confidence>
+00241      </part-num-ref>
+       Figure 2 illustrates the sustained release of microencapsulated drug[[<confidence value="2222">;}].</confidence>
+    </p>
+    <p id="p-13" num="13">Comparison of viable tumor cell growth <confidence value="5">(</confidence>
+bioluminescence recorded from <confidence value="5">L</confidence>
+uc+ human prostate tumor cells) showing the reduction in viable cells resulting from <confidence value="222222222222">cryoablation</confidence>
+ alone <confidence value="86885">(CA),</confidence>
+ and the prolonged effect three weeks of the combined <confidence value="5">c</confidence>
+ryo-chemothera<confidence value="66">py</confidence>
+ treatment <confidence value="66">(C</confidence>
+A+M<confidence value="665">CC.</confidence>
+ This fi<confidence value="8">g</confidence>
+ure illustrates the long lasting action of the sustained release of the <confidence value="22222222222222222">microencapsulated</confidence>
+ drug.    </p>
+    <p id="p-14" num="14">
+      <confidence value="5">1</confidence>
+00251       Fig<confidence value="66">ur</confidence>
+e 3 a cross sectional view of a <confidence value="222222222">cryoprobe</confidence>
+ having a prezo crystal<confidence value="6">.</confidence>
+    </p>
+    <p id="p-15" num="15">
+      <confidence value="5">1</confidence>
+00261       Fig<confidence value="5">u</confidence>
+re 4A i<confidence value="5">s</confidence>
+ a table il<confidence value="8">l</confidence>
+ustrating the effect of cryoablation and/or <confidence value="22222222222222222">microencapsulated</confidence>
+ 5-fluorouraci<confidence value="5">l</confidence>
+ on prostate tumor necrosis. The kill ratio of the ice ball is the ratio of tumor necrosis measured three days postoperatively to ice ball surface. It reflects the overall destructive effect of the frozen part of the thermal lesion. Combined therapy gives a larger mean necrosis radius than <confidence value="222222222222">crvoablation</confidence>
+ alone. This difference is s<confidence value="888">ign</confidence>
+ificant: <confidence value="666">P&lt;0</confidence>
+.004.    </p>
+    <p id="p-16" num="16">
+      <confidence value="588">100</confidence>
+271       Fi<confidence value="66">gu</confidence>
+re 4<confidence value="5">B</confidence>
+ is a tabl<confidence value="8">e</confidence>
+ illustrating the cure rate observed with a <confidence value="2222222222222222">cytochemotherapy</confidence>
+ proto<confidence value="8">c</confidence>
+ol that in<confidence value="8">j</confidence>
+ected interstitially volume-adjusted doses of <confidence value="55">pc</confidence>
+aps5-FU at the time of <boundary-data type="header">
+        <confidence value="7">4</confidence>
+      </boundary-data>
+      <page-break num="4"/>
+      <boundary-data type="header">
+        <confidence value="8662">App[</confidence>
+ No. <confidence value="6665885">11/097,</confidence>
+991 - Re<confidence value="656">ply</confidence>
+ to No<confidence value="6666">tice</confidence>
+ to File Corrected A<confidence value="2286">ppli</confidence>
+cation dated Febr<confidence value="5885">uary</confidence>
+ 20 <confidence value="6662">200§</confidence>
+      </boundary-data>
+      <confidence value="222222222222">crvoablation</confidence>
+ perioperatively<confidence value="5">,</confidence>
+ and during the post-operative period at d<confidence value="26">ay</confidence>
+ <part-num-ref name="post-operative period at day">
+        <confidence value="6">7</confidence>
+      </part-num-ref>
+ <confidence value="8">a</confidence>
+nd day <part-num-ref name="and day">14.</part-num-ref>
+    </p>
+    <p id="p-17" num="17">
+      <confidence value="222222222222">Cryoablation</confidence>
+ was purpose<confidence value="88">ly</confidence>
+ s<confidence value="8">p</confidence>
+arin<confidence value="8">g</confidence>
+ the peripheral <confidence value="8">p</confidence>
+art of biolumines<confidence value="7">c</confidence>
+ent lung tumor <confidence value="5">(</confidence>
+A549 <confidence value="5686">luc)</confidence>
+ wh<confidence value="8">e</confidence>
+re the <confidence value="7">c</confidence>
+aps de<confidence value="8">p</confidence>
+ots were injected.    </p>
+    <p id="p-18" num="18">
+      <confidence value="58885">[0028</confidence>
+1      Figure <confidence value="6">5</confidence>
+ <confidence value="86">is</confidence>
+ an ultra sound image detecting microcapsules captured at real time<confidence value="5">,</confidence>
+ allowing deposition of the microcapsules at a precise and tar<confidence value="8">g</confidence>
+eted locat<confidence value="8">i</confidence>
+on.    </p>
+    <p id="p-19" num="19">Please replace paragraph [003<confidence value="885">6],</confidence>
+ now renumbered paragraph [0042]<confidence value="5">,</confidence>
+ at page 14, with the following <confidence value="8">a</confidence>
+mended paragraph.    </p>
+    <p id="p-20" num="20">[0042<confidence value="5">]</confidence>
+       We have calculated that the radius of the hypother<confidence value="7">m</confidence>
+ic zone, i.e. from <confidence value="518655">OIC-te</confidence>
+ <confidence value="255221">+250C@</confidence>
+ <confidence value="225">0*C</confidence>
+ to <confidence value="588255">+254C,</confidence>
+ from the cryoprobe center is about twice that of the frozen zone during experiments on <confidence value="222222222">xenogenic</confidence>
+ prostate and lung tumor models. Since we have observed an increased cell kill when <confidence value="2222222222222">microcapsules</confidence>
+ 5-<confidence value="5">F</confidence>
+U were deposited in tumor regions submitted to temperatures ranging from <confidence value="58818">--5EC</confidence>
+ <confidence value="5566525512526">te-12]C-i+5"C</confidence>
+ to <confidence value="2862">+12"</confidence>
+C, and given that microcapsules are deposited at tumor margins, we can easily decide the location of the ice front border, always at [[0 <confidence value="5">C</confidence>
+]] <confidence value="22">0"</confidence>
+C, by <confidence value="8">r</confidence>
+eference to the tumor margins. <confidence value="8">U</confidence>
+ltrasound imaging show real-time images of the advancing ice front edge, an <confidence value="22222222222222">hyperechogenic</confidence>
+ rim, when it comes close to the t<confidence value="8">u</confidence>
+mor margi<confidence value="8">n</confidence>
+s<confidence value="8">.</confidence>
+    </p>
+    <p id="p-21" num="21">However, since the entire ice-<confidence value="686">bal</confidence>
+l cannot be imaged by ultraso<confidence value="8">n</confidence>
+ography (shadowing behind the ice f<confidence value="8">r</confidence>
+ont), we use in conjunction the help of our impedance-based monitoring method to predict the location of the destructive ice front. The present invention described above uses a <confidence value="88">US</confidence>
+-guided minimally invasive tumor tissue ablation with a <confidence value="222222222222">cryosurgical</confidence>
+ probe(s), an ima<confidence value="7">g</confidence>
+eable vibrating delivery device and i<confidence value="7">m</confidence>
+ageable drug (s) carriers. <confidence value="5">T</confidence>
+he cryosurgical probe induces and the monitoring system depicts the formation of a lethal frozen zone in the target <boundary-data type="header">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+      <page-break num="5"/>
+      <boundary-data type="header">
+        <confidence value="11412">A~pp[</confidence>
+ <confidence value="656">No.</confidence>
+ <confidence value="6626662666">111097,991</confidence>
+ <confidence value="6">-</confidence>
+ <confidence value="66666">Reply</confidence>
+ <confidence value="66">to</confidence>
+ <confidence value="666666">Notice</confidence>
+ <confidence value="66">to</confidence>
+ <confidence value="6666">File</confidence>
+ <confidence value="25515188588565">GorrectedAppic</confidence>
+ <confidence value="22222">ation</confidence>
+ <confidence value="65">at</confidence>
+  <confidence value="222222">ebruar</confidence>
+ <confidence value="856">20,</confidence>
+ <confidence value="555">208</confidence>
+      </boundary-data>
+tumor surrounded by a sub-lethal zone. U<confidence value="5">S</confidence>
+ imaging of the ice front edge allows for assessing <confidence value="86">it</confidence>
+s extension to the tumor margins. Deposits of small volu<confidence value="8">m</confidence>
+es of <confidence value="222222222222222">thermosensitive</confidence>
+ microcapsules containing the cytotoxic drug(s) along with the ima<confidence value="7">g</confidence>
+eable contrast agent are injected percutaneously and distributed into tumor periphery with adapted imageable de<confidence value="8">l</confidence>
+ivery device. In a preferred embodiment, the major steps in this process are<confidence value="5">:</confidence>
+ <part-num-ref name="major steps in this process are:">1)</part-num-ref>
+ Fabrication of the special imageable cytotoxic <confidence value="2222222222222">microcapsules</confidence>
+ <confidence value="4288885">(-eaps)</confidence>
+ <confidence value="5268285">(ucaps)</confidence>
+; <part-num-ref name="special imageable cytotoxic microcapsules (-eaps) (ucaps);">2)</part-num-ref>
+ Ultrasound imaging to characterize the location, size, and shape of the target tumor, <part-num-ref name="target tumor,">3)</part-num-ref>
+ Ultrasound guidance and precise positioning of the vibrating cryoprobe(s) tip at selected location into tumor according to the operative planning <part-num-ref name="operative planning">4<confidence value="5">)</confidence>
+      </part-num-ref>
+ computer<confidence value="2">-</confidence>
+aided and image-guided <confidence value="222222222222">cryoablation</confidence>
+, with a single freeze session per probe (if multiple probes have been inserted) and no hold ti<confidence value="8">m</confidence>
+e at minimal temperature, to monitor ice ball growth within the edges of the tumor, and simultaneous <confidence value="8">c</confidence>
+reation of a <confidence value="22222222222">hypothennic</confidence>
+ region in the perimeter of the tumor [an<confidence value="5">d</confidence>
+ the adjacent tissues]; <part-num-ref name="adjacent tissues];">5)</part-num-ref>
+ Percutaneous injection of the microcaps in the hypothermi<confidence value="7">a</confidence>
+ regions of the tumor and surrounding tissue, using ultrasound visualization to insure precise delivery and distribution of the cytotoxic microcapsules, peripheral to the let<confidence value="8">h</confidence>
+al zone of the ice ball; and <part-num-ref name="ice ball; and">6)</part-num-ref>
+ sequential ultrasound imaging of the microcapsules deposits so that their degradation rate can be monitored and the time for re-dosing be determined with accuracy.    </p>
+    <boundary-data type="header">
+      <confidence value="7">6</confidence>
+    </boundary-data>
+    <boundary-data type="header">
+      <confidence value="822285">App[No</confidence>
+ <confidence value="855">11/</confidence>
+97,991 - Re<confidence value="442">pNy</confidence>
+ to N<confidence value="2">e</confidence>
+tice to Fil<confidence value="4">e</confidence>
+ Correc<confidence value="588">ted</confidence>
+ <confidence value="62212666562">Applicatior</confidence>
+ <confidence value="6156">daed</confidence>
+ <confidence value="455886">Erlary</confidence>
+ 20, 200<confidence value="2">8</confidence>
+    </boundary-data>
+    <p id="p-22" num="22">
+      <page-break num="6"/>
+Please replace paragraph <confidence value="5">[</confidence>
+0041<confidence value="4">]</confidence>
+, now renumbered paragraph [0046], at page 16, with the following amended paragraph.    </p>
+    <p id="p-23" num="23">
+      <confidence value="5">1</confidence>
+0046<confidence value="5">1</confidence>
+      The average <confidence value="222222222222">microcapsule</confidence>
+ diameter is <part-num-ref name="average microcapsule diameter is">
+        <confidence value="5">8</confidence>
+      </part-num-ref>
+ <confidence value="8">-</confidence>
+ <part-num-ref name="-">
+        <confidence value="86">16</confidence>
+      </part-num-ref>
+ microns<confidence value="5">,</confidence>
+ with a size distribution wherein <confidence value="5">8</confidence>
+0% of said <confidence value="2222222222222">microcapsules</confidence>
+ fall into a range between <part-num-ref name="range between">
+        <confidence value="4">1</confidence>
+      </part-num-ref>
+ - 30um . The drug loading of 5- FU is typically 0<confidence value="66">.3</confidence>
+6ng/<confidence value="22">pl</confidence>
+ of <confidence value="222222222222">microcapsule</confidence>
+ suspension <confidence value="282514864">{6-5i20-u</confidence>
+eap<confidence value="56222">s/-l-</confidence>
+ [65<confidence value="2868">,200</confidence>
+ <confidence value="2222222228">jcavs/tll.</confidence>
+    </p>
+    <p id="p-24" num="24">Please replace paragraph [0043], now renumbered paragraph [004<confidence value="54">8]</confidence>
+, at page 17, with the following amended paragraph.    </p>
+    <p id="p-25" num="25">[0048<confidence value="5">1</confidence>
+      <confidence value="6">C</confidence>
+ryoablation and hypothermia treatment<confidence value="6">:</confidence>
+ <confidence value="6">(</confidence>
+see Fig<confidence value="656">.l,</confidence>
+ <confidence value="5">p</confidence>
+per<confidence value="5">-</confidence>
+ <confidence value="588662">right-</confidence>
+ <confidence value="2222228">4rawig)</confidence>
+ Under general anesthesia a 3 mm diameter cryoprobe (Critical Ca<confidence value="66">re</confidence>
+ Innovations, Inc., <confidence value="668">VA,</confidence>
+ USA) is inserted vertically into tumor through a skin puncture. A 0.<confidence value="5">5</confidence>
+ mm bead wire insulated (PFA Teflon R) type T thermocouple (Omega<confidence value="5">,</confidence>
+ CT<confidence value="5">,</confidence>
+ USA) is placed <confidence value="22222222222222">percutaneously</confidence>
+ into tumor a few mm off the probe wall. The probe <confidence value="5">t</confidence>
+ip end contains a <confidence value="222222222222">thermocouple</confidence>
+ located at 5<confidence value="58">mm</confidence>
+ from tip end. Both thermocouples are connecte<confidence value="8">d</confidence>
+ to a data-logging module (Super Logics, <confidence value="5">C</confidence>
+P <part-num-ref name="data-logging module (Super Logics, CP">8<confidence value="5">2</confidence>
+18)      </part-num-ref>
+ and to a laptop (HP Pavilion ze <part-num-ref name="laptop (HP Pavilion ze">4145)</part-num-ref>
+ running a proprietary thermal monitoring and simulation software. During the c<confidence value="7">r</confidence>
+yosurgical procedure this software measures probe temperatures and uses them to predict: <part-num-ref name="cryosurgical procedure this software measures probe temperatures and uses them to predict:">1)</part-num-ref>
+ the tumor temperature  (+<confidence value="58">/-</confidence>
+ <part-num-ref name="tumor temperature  (+/-">
+        <confidence value="6">2</confidence>
+      </part-num-ref>
+ C), (assuming cylindrical symmetry, by solving the equation of thermal diffusivity), and <part-num-ref name="equation of thermal diffusivity), and">
+        <confidence value="5">2</confidence>
+)      </part-num-ref>
+ ice ball formation and temperatures of tumor and adjacent tissues at various distances beyond the ice ball.    </p>
+    <p id="p-26" num="26">
+      <confidence value="222222222222">Cryoablation</confidence>
+ of experimental prostate <confidence value="588">(DU</confidence>
+ <confidence value="6">1</confidence>
+45) and lung (A549) tumors consisted in freezing a portion of the tumor from skin surface to the deep margin and leaving a volume of peripheral tumor unfrozen but being submitted to hypothermia. The probe tip was purposely <boundary-data type="header">
+        <confidence value="8">7</confidence>
+      </boundary-data>
+      <page-break num="7"/>
+      <boundary-data type="header">
+        <confidence value="84">An</confidence>
+l. No 11<confidence value="5">/</confidence>
+097<confidence value="5">.</confidence>
+991 <confidence value="8825528">Replyto</confidence>
+ <confidence value="8566">Noti</confidence>
+ce to File Corrected A<confidence value="66686">pplic</confidence>
+ation dated February <confidence value="685">20.</confidence>
+ 2008      </boundary-data>
+not centered in t<confidence value="8">u</confidence>
+mor <confidence value="5">s</confidence>
+o that the ice ball never overlapped the entire tumor area. Hence, the frozen zone of the tumor was clearly distinguishable f<confidence value="8">r</confidence>
+om the hypothermic zone. A s<confidence value="8">i</confidence>
+ngle <confidence value="22222222222">freeze/thaw</confidence>
+ (F/T) cycle was used without hold time. Within <part-num-ref name="single freeze/thaw (F/T) cycle was used without hold time. Within">5</part-num-ref>
+ minutes the ice ball thawed spontaneously at room temperature. The duration of hypothermia zone <confidence value="5">i</confidence>
+n ice ball region was estimated to be from <part-num-ref name="duration of hypothermia zone in ice ball region was estimated to be from">1<confidence value="5">5</confidence>
+      </part-num-ref>
+ to <part-num-ref name="to">30</part-num-ref>
+ m<confidence value="556">in.</confidence>
+ <confidence value="6">A</confidence>
+ time that is clearly within the accepted duration of exposure to freezing temperatures for tumors during conventional cryoablation. The puncture was sealed with cyanoacrylate adhesive.    </p>
+    <p id="p-27" num="27">Please replace paragraph [0044]<confidence value="5">,</confidence>
+ now renumbered paragraph [0049], at page 18, with the following amended paragraph.    </p>
+    <p id="p-28" num="28">[0049]      Int<confidence value="66885">ratum</confidence>
+or percutaneous deposition of imageable cytotoxic <confidence value="2222222222222">nicrocapsules</confidence>
+: At the end of the freezing cycle, a <part-num-ref name="">25</part-num-ref>
+ gauge short-beveled needle is inserted, us<confidence value="8">i</confidence>
+ng the U.S.    </p>
+    <p id="p-29" num="29">visualization to locate the needle tip and echogenic deposits of <confidence value="5886">5-FU</confidence>
+ <confidence value="6255">[[Lc</confidence>
+aps]] <confidence value="82252">pcaps</confidence>
+ that are just peripheral to the ice ball margin. This is a unique technique that can confirm in real-time the proper distribution within the tumor and estimate if there are any volume of tumor that require complementary injections immediately or later. Each injection contained, based on the total tumor volume, from <part-num-ref name="total tumor volume, from">20</part-num-ref>
+ up to 200 ml of PBS suspension deposited in multiple peripheral sites of the tumor using a pa<confidence value="5">r</confidence>
+allel-<confidence value="5">r</confidence>
+ow technique or field block technique.    </p>
+    <boundary-data type="header">
+      <confidence value="4">8</confidence>
+    </boundary-data>
+    <boundary-data type="header">
+      <confidence value="2222">Appl</confidence>
+ No 11<confidence value="5">/</confidence>
+097 991 - Re<confidence value="5">p</confidence>
+ly to <confidence value="65">No</confidence>
+tic<confidence value="5585">eto.</confidence>
+ <confidence value="6525">Fjle</confidence>
+ Corrected A<confidence value="6666856688">pplication</confidence>
+ dated February <confidence value="662">20.</confidence>
+ <confidence value="6882">2008</confidence>
+    </boundary-data>
+    <p id="p-30" num="30">
+      <page-break num="8"/>
+Please replace paragraph <confidence value="4">[</confidence>
+0045<confidence value="4">]</confidence>
+, now renumbered paragraph [0051], at page 18, with the following amended paragrap<confidence value="75">h.</confidence>
+    </p>
+    <p id="p-31" num="31">
+      <confidence value="288882">[0051]</confidence>
+       The results of this combined modality show that this new modality of cryo- chemotherapy is far more effective in inhibiting <confidence value="8">t</confidence>
+umor growth than either individual treatment <confidence value="826622655525">(Pig;-ra4-5)</confidence>
+ (Figures <part-num-ref name="results of this combined modality show that this new modality of cryo- chemotherapy is far more effective in inhibiting tumor growth than either individual treatment (Pig;-ra4-5) (Figures">
+        <confidence value="4">1</confidence>
+      </part-num-ref>
+ and <confidence value="66">2)</confidence>
+. The inhibito<confidence value="8">r</confidence>
+y effect appears at sub-toxic doses of <confidence value="685">5-F</confidence>
+U, a<confidence value="5">s</confidence>
+ des<confidence value="8">c</confidence>
+ribed above. Moreover, this effectiveness doesn't require that the cell be submitted either to low negative temperature, <confidence value="5">i</confidence>
+.e. under [[-20 <confidence value="4">E</confidence>
+ <confidence value="6">C</confidence>
+]] -20<confidence value="2">4</confidence>
+C, to intracellular freezing, to complete or partial extra cellular freezing or to repeated F<confidence value="5">I</confidence>
+T cycles. <confidence value="5">W</confidence>
+e have calculated that the temperature of tumor at the sites of <confidence value="2222222222222">microcapsules</confidence>
+ deposition was about <confidence value="568655665">1-2--+-4-</confidence>
+ <confidence value="8858">12C+</confidence>
+ <confidence value="88268">-4°C.</confidence>
+    </p>
+    <p id="p-32" num="32">Please replace paragraph [0047], now <confidence value="2222222222">renumbered</confidence>
+ paragraph [0053], at page 19, with the following amended paragraph.    </p>
+    <p id="p-33" num="33">
+      <confidence value="5">1</confidence>
+0053<confidence value="5">1</confidence>
+      Another advantage of the invention is that the addition of microcaps 5-<confidence value="55">FU</confidence>
+ increases significantly the <confidence value="222222222222">cryonecrotic</confidence>
+ area <confidence value="558558665">(Table-I)</confidence>
+ (see Figure 4A<confidence value="66">),</confidence>
+ which in our experiments comes closer to the ice ball margin (b<confidence value="2">/</confidence>
+t 0<confidence value="66">.5</confidence>
+ to 1.5m<confidence value="66">m)</confidence>
+. Therefore, with this combined technique, U<confidence value="5">S</confidence>
+ imaging becomes a valuable tool to predict in real time the f<confidence value="8">u</confidence>
+ture location of the kill margins.    </p>
+    <boundary-data type="header">
+      <confidence value="8">9</confidence>
+    </boundary-data>
+    <boundary-data type="header">
+      <confidence value="4114">Arxl</confidence>
+ <confidence value="666">No.</confidence>
+ <confidence value="6622551">11/097.</confidence>
+ <confidence value="6522">91.-</confidence>
+ <confidence value="6588">Rely</confidence>
+ <confidence value="86">to</confidence>
+ <confidence value="648662">NQtice</confidence>
+ <confidence value="85">to</confidence>
+ <confidence value="5685">File</confidence>
+ <confidence value="58266865">Conected</confidence>
+ <confidence value="54">AA</confidence>
+lica<confidence value="48848686">tiondate</confidence>
+d February <confidence value="665">20,</confidence>
+ <confidence value="6688">2008</confidence>
+    </boundary-data>
+    <p id="p-34" num="34">
+      <page-break num="9"/>
+Please replace paragraph [0049]<confidence value="5">,</confidence>
+ now renumbered paragraph [0055<confidence value="2">]</confidence>
+, at page 19, with the following amended paragraph.    </p>
+    <p id="p-35" num="35">[0055]       Another advantage of our invention is that the microcapsules can be detected with real time U<confidence value="5">S</confidence>
+ imaging (Fig.[[<confidence value="6662">#]])</confidence>
+ so that their deposition at a precise and targeted location due to the vibrating delivery device visualized by the Ultrasound machine is made possible a<confidence value="5">s</confidence>
+ well as an estimate of their lifetime in tumor (<confidence value="88668525">Table-I)</confidence>
+ (see Fi<confidence value="6666">gure</confidence>
+ <confidence value="624">4B)</confidence>
+. Since U<confidence value="5">S</confidence>
+ allows for real-time imaging of the tumor and ice ball contours it is possible at anytime to deposit the microcapsules at pre-selected sites, at <confidence value="2222222">iceball</confidence>
+ margins and in tumor, with ext<confidence value="8">r</confidence>
+eme accuracy.    </p>
+    <p id="p-36" num="36">Please replace paragraph <confidence value="85">[0</confidence>
+054], now renumbered paragraph [0060<confidence value="66">],</confidence>
+ at page <confidence value="5">2</confidence>
+1, with the fol<confidence value="8">l</confidence>
+owing amended paragraph.    </p>
+    <p id="p-37" num="37">[0060<confidence value="5">]</confidence>
+       3. A combinat<confidence value="8">i</confidence>
+on of microencapsulated drugs can have a better effect on tumor growth inhibition. Numerous app<confidence value="8">r</confidence>
+oved c<confidence value="8">y</confidence>
+totoxic drugs and other agents that regulate tumor cell metabolism can be used for the treatment of solid mal<confidence value="8">i</confidence>
+gnant tumors. Other drugs that act as photosensitizer (like Photofrin<confidence value="2">@</confidence>
+) are also of much interest<confidence value="5">.</confidence>
+ It is of particular interest to be able encapsulate or co-encapsulate different drugs that will allow for the combination of multiple t<confidence value="8">r</confidence>
+eatment modalities on the same tumor<confidence value="5">.</confidence>
+ For <confidence value="8">i</confidence>
+nstances a treatment scenario would combine the cryo-application with the injection of [[ucaps]<confidence value="6">]</confidence>
+ <confidence value="18642">ucaps</confidence>
+ 5-FU a <confidence value="222222222">eytotoxic</confidence>
+ agent that is also a radio sensitizer. Tumor irradiation (brachytherapy, external beam therapy) would be a complementary treatment for any remnant lesion and to sterilize the peripheral marg<confidence value="8">i</confidence>
+n of the lesion, after completion of the <confidence value="2222222222">cryoachemo</confidence>
+ treatment.    </p>
+    <boundary-data type="header">
+      <confidence value="88">10</confidence>
+    </boundary-data>
+  </description>
+</us-patent-application>
+

prior_art/11120455.xml

@@ -0,0 +1,99 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11120455</doc-number>
+        <date>2010-01-21</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <boundary-data type="header">Serial No. 11/120,455</boundary-data>
+    <boundary-data type="header">Examiner: Paul P. <confidence value="8">T</confidence>
+ran    </boundary-data>
+    <heading id="h-1">IN THE SPECIFICATION</heading>
+    <p id="p-1" num="1">Please replace paragraph [0001] with the following:</p>
+    <p id="p-2" num="2">[0001]   This application claims the benefit of priority to U.S. Provisional Patent Application No. 60/646,465 entitled  "Integrated  and Detachable Wireless Headset Element for Cellular/Mobile/Portable Phones And Audio Playback Devices," (Attorney Docket No. BP4238) by Josephus A. Van Engelen, et al. filed on January <part-num-ref name="Van Engelen, et al. filed on January">24,</part-num-ref>
+ <part-num-ref name="Van Engelen, et al. filed on January 24,">2005,</part-num-ref>
+ and is incorporated herein by reference in its entirety for all purposes.    </p>
+    <p id="p-3" num="3">[0002]   This Application is related to the following applications:</p>
+    <p id="p-4" num="4">1.    Application No. 10/981,418 entitled "Universal Wireless Multimedia Device," (Attorney Docket No. BP2754C<confidence value="5">I</confidence>
+P), by Nambirajan Seshadri, et al., filed on November 4, 2004, which claims priority pursuant to 35 U.S.C. <confidence value="5">§</confidence>
+ <part-num-ref name="U.S.C. §">120,</part-num-ref>
+ as a continuation-in-part (CIP) to the following applications:    </p>
+    <p id="p-5" num="5">a.    U.S. Application No. 10/856,430 entitled "Providing a Universal Wireless Headset," (Attorney Docket No. BP2754), by Nambirajan Seshadri, et al., filed May <part-num-ref name="Universal Wireless Headset,&quot; (Attorney Docket No. BP2754), by Nambirajan Seshadri, et al., filed May">28,</part-num-ref>
+ <part-num-ref name="Universal Wireless Headset,&quot; (Attorney Docket No. BP2754), by Nambirajan Seshadri, et al., filed May 28,">2004,</part-num-ref>
+ which claims priority pursuant to <part-num-ref name="Universal Wireless Headset,&quot; (Attorney Docket No. BP2754), by Nambirajan Seshadri, et al., filed May 28, 2004, which claims priority pursuant to">35</part-num-ref>
+ USC <confidence value="5">§</confidence>
+ 119(e) to the U.S. Provisional Application No. 60/473,967 filed on May <part-num-ref name="U.S. Provisional Application No. 60/473,967 filed on May">28,</part-num-ref>
+ 2003;    </p>
+    <p id="p-6" num="6">and b.    U.S. Application No. 10/856,124 entitled "Modular Wireless Headset and/or Headphones" (Attorney Docket No. BP2755), filed May 28, 2004, which claims priority pursuant to 35 USC <confidence value="5">§</confidence>
+ 119(e) to U.S. Provisional Application No. 60/473,675 filed May <part-num-ref name="USC § 119(e) to U.S. Provisional Application No. 60/473,675 filed May">28,</part-num-ref>
+ <part-num-ref name="USC § 119(e) to U.S. Provisional Application No. 60/473,675 filed May 28,">2003.</part-num-ref>
+    </p>
+    <p id="p-7" num="7">2.    Application No. 10/976,300 entitled "Modular Wireless Multimedia Device," (Attorney Docket No. BP2755C<confidence value="5">I</confidence>
+P), by Nambirajan Seshadri, et al., filed on October 27, 2004, which claims priority pursuant to 35 U.S.C. <confidence value="5">§</confidence>
+ <part-num-ref name="U.S.C. §">120,</part-num-ref>
+ as a continuation-in-part (CIP) to the following applications:    </p>
+    <p id="p-8" num="8">a.    U.S. Application No. 10/856,124 entitled "Modular Wireless Headset and/or Headphones," (Attorney Docket No. BP2755), filed May 28, 2004, which claims priority pursuant to 35 USC <confidence value="5">§</confidence>
+ 119(e) to U.S. Provisional Application No. 60/473,675, filed on May <part-num-ref name="USC § 119(e) to U.S. Provisional Application No. 60/473,675, filed on May">28,</part-num-ref>
+ 2003; and <boundary-data type="header">BP4238 - Page 2</boundary-data>
+      <page-break num="2"/>
+      <boundary-data type="header">Serial No. 11/120,455</boundary-data>
+      <boundary-data type="header">Examiner: Paul P. <confidence value="8">T</confidence>
+ran      </boundary-data>
+b.    U.S. Application No. 10/856,430 filed May <part-num-ref name="USC § 119(e) to U.S. Provisional Application No. 60/473,675, filed on May 28, 2003; and b.    U.S. Application No. 10/856,430 filed May">28,</part-num-ref>
+ <part-num-ref name="USC § 119(e) to U.S. Provisional Application No. 60/473,675, filed on May 28, 2003; and b.    U.S. Application No. 10/856,430 filed May 28,">2004</part-num-ref>
+ entitled "Providing a Universal Wireless Headset, (Attorney Docket No. BP2754), which claims priority pursuant to <part-num-ref name="Universal Wireless Headset, (Attorney Docket No. BP2754), which claims priority pursuant to">35</part-num-ref>
+ USC <confidence value="5">§</confidence>
+ <confidence value="66">11</confidence>
+9(e) to U.S. Provisional Application No.    </p>
+    <p id="p-9" num="9">60/473,967 filed May 28, 2003.</p>
+    <p id="p-10" num="10">3.    Application No. 11/120,765 entitled "Modular Earpiece/Microphone that Anchors Voice Communications," (Attorney Docket No. BP4044), by Nambirajan Seshadri, et al., filed on May 3, 2005, which claims priority pursuant to 35 USC <confidence value="5">§</confidence>
+ <confidence value="66">11</confidence>
+9(e) to U.S. Provisional Application No. 60/656,828 filed on February <part-num-ref name="USC § 119(e) to U.S. Provisional Application No. 60/656,828 filed on February">25,</part-num-ref>
+ <part-num-ref name="USC § 119(e) to U.S. Provisional Application No. 60/656,828 filed on February 25,">2005.</part-num-ref>
+    </p>
+    <p id="p-11" num="11">4.    Application No. 11/122,146 entitled "Handover of Call Serviced by Modular Earpiece/Microphone Between Servicing Base Portions," (Attorney Docket No.</p>
+    <p id="p-12" num="12">BP4045), by Nambirajan Seshadri, et al., filed on May 4, 2005, now U.S. Patent No. 7,555,318, which claims priority under 35 USC <confidence value="5">§</confidence>
+ <confidence value="66">11</confidence>
+9(e) to U.S. Provisional Application No. 60/653,234 filed on February <part-num-ref name="USC § 119(e) to U.S. Provisional Application No. 60/653,234 filed on February">15,</part-num-ref>
+ <part-num-ref name="USC § 119(e) to U.S. Provisional Application No. 60/653,234 filed on February 15,">2005.</part-num-ref>
+    </p>
+    <p id="p-13" num="13">5.    Application No. 11/120,900 entitled "Modular Earpiece/Microphone (Headset) Operable to Service Voice Activated Commands," (Attorney Docket No.</p>
+    <p id="p-14" num="14">BP4046), by Nambirajan Seshadri, et al., filed on May 3, 2005, 6.    Application No. 11/120,903 entitled "Battery Management in a Modular Earpiece Microphone Combination," (Attorney Docket No. BP4047), by Nambirajan Seshadri, et al., filed on May <part-num-ref name="Modular Earpiece Microphone Combination,&quot; (Attorney Docket No. BP4047), by Nambirajan Seshadri, et al., filed on May">3,</part-num-ref>
+ <part-num-ref name="Modular Earpiece Microphone Combination,&quot; (Attorney Docket No. BP4047), by Nambirajan Seshadri, et al., filed on May 3,">2005</part-num-ref>
+ which claims priority under <part-num-ref name="which claims priority under">35</part-num-ref>
+ USC <confidence value="5">§</confidence>
+ <confidence value="66">11</confidence>
+9(e) to Provisional Application No. 60/646,270 filed on January <part-num-ref name="USC § 119(e) to Provisional Application No. 60/646,270 filed on January">24,</part-num-ref>
+ <part-num-ref name="USC § 119(e) to Provisional Application No. 60/646,270 filed on January 24,">2005.</part-num-ref>
+    </p>
+    <p id="p-15" num="15">7.    Application  No.   11/120,904  entitled  "Pairing  Modular  Wireless Earpiece/Microphone (Headset) to a Serviced Base Portion and Subsequent Access Thereto," (Attorney Docket No. BP4048), by Nambirajan Seshadri, et al., filed on May <part-num-ref name="Serviced Base Portion and Subsequent Access Thereto,&quot; (Attorney Docket No. BP4048), by Nambirajan Seshadri, et al., filed on May">3,</part-num-ref>
+ <part-num-ref name="Serviced Base Portion and Subsequent Access Thereto,&quot; (Attorney Docket No. BP4048), by Nambirajan Seshadri, et al., filed on May 3,">2005,</part-num-ref>
+ which claims priority under <part-num-ref name="Serviced Base Portion and Subsequent Access Thereto,&quot; (Attorney Docket No. BP4048), by Nambirajan Seshadri, et al., filed on May 3, 2005, which claims priority under">35</part-num-ref>
+ USC <confidence value="5">§</confidence>
+ <confidence value="66">11</confidence>
+9(e) to Provisional Application No. 60/646,437 filed on January <part-num-ref name="USC § 119(e) to Provisional Application No. 60/646,437 filed on January">24,</part-num-ref>
+ <part-num-ref name="USC § 119(e) to Provisional Application No. 60/646,437 filed on January 24,">2005.</part-num-ref>
+    </p>
+    <p id="p-16" num="16">8.    Application No. 11/120,902 entitled "Managing Access of Modular Wireless Earpiece/Microphone (Headset) to Public/Private Servicing Base Station," <boundary-data type="header">BP4238 - Page 3</boundary-data>
+      <page-break num="3"/>
+      <boundary-data type="header">Serial No. 11/120,455</boundary-data>
+      <boundary-data type="header">Examiner: Paul P. <confidence value="8">T</confidence>
+ran      </boundary-data>
+(Attorney Docket No. BP4049), by Nambirajan Seshadri, et al., filed on May 3, 2005, which claims priority under 35 <confidence value="666">USC</confidence>
+ <confidence value="5">§</confidence>
+ 119(e) to Provisional Application No. 60/646,235 filed on January <part-num-ref name="USC § 119(e) to Provisional Application No. 60/646,235 filed on January">24,</part-num-ref>
+ <part-num-ref name="USC § 119(e) to Provisional Application No. 60/646,235 filed on January 24,">2005.</part-num-ref>
+    </p>
+    <p id="p-17" num="17">9.    Application No. 11/120,676 entitled "Earpiece/Microphone (Headset) Servicing Multiple Incoming Audio Streams," (Attorney Docket No. BP4050), by Nambirajan Seshadri, et al., filed on May 3, 2005, now U.S. Patent No. 7,558,529, which claims priority under 35 USC <confidence value="5">§</confidence>
+ 119(e) to Provisional Application No.    </p>
+    <p id="p-18" num="18">60/646,272 filed on January 24, 2005.</p>
+    <p id="p-19" num="19">all of which are incorporated herein by reference in their entirety for all purposes.</p>
+    <boundary-data type="header">BP4238 - Page 4</boundary-data>
+  </description>
+</us-patent-application>
+

prior_art/11136266.xml

@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11136266</doc-number>
+        <date>2008-07-22</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">NCPT-003 Patent </p>
+    <heading id="h-1">IN THE SPECIFICATION:</heading>
+    <p id="p-2" num="2">Please amend the paragraph at page <part-num-ref name="paragraph at page">8,</part-num-ref>
+ lines 12-20 as follows:    </p>
+    <p id="p-3" num="3">As best seen in FIG. 2, the catheter <part-num-ref name="catheter">12</part-num-ref>
+ includes at least three lumens <part-num-ref name="includes at least three lumens">18</part-num-ref>
+ extending between the proximal ends <part-num-ref name="proximal ends">14,</part-num-ref>
+ <part-num-ref name="proximal ends 14,">16.</part-num-ref>
+ For example, the catheter <part-num-ref name="catheter">12</part-num-ref>
+ may include an instrument lumen 18a that extends from a port 32a in the handle <part-num-ref name="handle">30</part-num-ref>
+ to an opening 34a [[34]] in the distal tip <part-num-ref name="distal tip">17.</part-num-ref>
+    </p>
+    <p id="p-4" num="4">The instrument lumen 18a may have sufficient size to allow a guidewire or other rail or instrument (not shown) to be inserted therethrough, e.g., to facilitate advancing the catheter <part-num-ref name="catheter">12</part-num-ref>
+ over the rail, as explained further below. Optionally, the handle <part-num-ref name="handle">30</part-num-ref>
+ may include one or more seals (not shown) adjacent the port 32a, e.g., e.g., a hemostatic seal that prevents fluid, e.g., blood, from flowing proximally out of the port 32a, yet allows one or more instruments to be inserted therethrough and into the instrument lumen 18a.    </p>
+    <p id="p-5" num="5">
+      <confidence value="8">3</confidence>
+     </p>
+  </description>
+</us-patent-application>
+

prior_art/11141382.xml

@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11141382</doc-number>
+        <date>2005-10-26</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">
+      <confidence value="2">-</confidence>
+      App<confidence value="5">l</confidence>
+. No. 11/141,382 Preliminary Amendment dated October 26, 2005 Response Notice of Incomplete Reply dated September <part-num-ref name="Response Notice of Incomplete Reply dated September">14,</part-num-ref>
+ <part-num-ref name="Response Notice of Incomplete Reply dated September 14,">2005</part-num-ref>
+ In the Specification:    </p>
+    <p id="p-2" num="2">Insert the following paragraph after paragraph [0018<confidence value="68">]:</confidence>
+    </p>
+    <p id="p-3" num="3">The patent or application file contains at lease one drawing executed in color. Copies of this patent or patent application publication with color drawing(s) will be provided by the Office upon request and payment of the necessary fee.</p>
+    <p id="p-4" num="4">2 of 5 WRFMAIN 12392023.1 </p>
+  </description>
+</us-patent-application>
+

prior_art/11169765.xml

@@ -0,0 +1,599 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11169765</doc-number>
+        <date>2005-06-30</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <heading id="h-1">IN THE UNITED STATES PATENT AND TRADEMARK OFFICE</heading>
+    <heading id="h-2">U.S. PATENT APPLICATION</heading>
+    <heading id="h-3">FOR:</heading>
+    <heading id="h-4">RECOVERY TECHNIQUES FOR WIRELESS COMMUNICATIONS NETWORKS</heading>
+    <heading id="h-5">INVENTORS:</heading>
+    <p id="p-1" num="1">Jukka Reunam<confidence value="488">aki</confidence>
+ <confidence value="2222">Juha</confidence>
+ Salokannel Harald Kaaja Ulrico Celentano Tommy Ginman Morgan &amp; Finnegan L.L.P.    </p>
+    <p id="p-2" num="2">3 World Financial Center New York, NY 10281-2101 (212) 415-8700 (Telephone) <part-num-ref name="415-8700 (Telephone)">(212)</part-num-ref>
+ 415-8701 (Facsimile) <part-num-ref name="415-8701 (Facsimile)">1775</part-num-ref>
+ Eye Street, N.W., Suite <part-num-ref name="Eye Street, N.W., Suite">400</part-num-ref>
+ Washington D.C., <part-num-ref name="Washington D.C.,">20006</part-num-ref>
+ <part-num-ref name="">(202)</part-num-ref>
+ 857-7887 (Telephone) <part-num-ref name="857-7887 (Telephone)">(202)</part-num-ref>
+ 857-7929 (Facsimile) Attorneys For Applicant <boundary-data type="header">60735 v<confidence value="4">l</confidence>
+      </boundary-data>
+      <page-break num="2"/>
+    </p>
+    <heading id="h-6">RECOVERY TECHNIQUES FOR WIRELESS COMMUNICATIONS NETWORKS</heading>
+    <heading id="h-7">FIELD OF THE INVENTION</heading>
+    <p id="p-3" num="3">
+      <confidence value="5">[</confidence>
+0001<confidence value="5">]</confidence>
+      The present invention relates to wireless communications. More particularly, the present invention relates to recovery techniques in wireless communications networks.    </p>
+    <heading id="h-8">BACKGROUND OF THE INVENTION</heading>
+    <p id="p-4" num="4">
+      <confidence value="5">[</confidence>
+0002<confidence value="5">]</confidence>
+      Short-range wireless communications networks typically involve devices that have a communications range of one hundred meters or less. To provide communications over long distances, these networks often interface with other networks. For example, short-range networks may interface with cellular networks, wireline telecommunications networks, and the Internet.    </p>
+    <p id="p-5" num="5">
+      <confidence value="588885">[0003]</confidence>
+      Terminals in short-range wireless networks often behave in an ad hoc manner.    </p>
+    <p id="p-6" num="6">That is, they dynamically create and terminate connections with each other. For instance, a terminal may create a connection when it desires to communicate with another terminal in its communications range or coverage area.</p>
+    <p id="p-7" num="7">[0004]      Ad hoc networks typically employ wireless transmission techniques that are well suited for short-range communications. Examples of such techniques include Bluetooth, IEEE 802.15.3, and ultra wideband (UWB) technologies.</p>
+    <p id="p-8" num="8">
+      <confidence value="5">[</confidence>
+0005<confidence value="5">]</confidence>
+      Various short-range networks, such as Bluetooth and IEEE 802.15.3 networks, are referred to as wireless personal area networks (WPANs) or piconets. These networks include a single coordinator device (e.g, a master or piconet coordinator) and multiple non-coordinating devices (e.g., DEVs or slave devices) <confidence value="5">[</confidence>
+0006<confidence value="5">]</confidence>
+      IEEE 802.15.3 specifies a WPAN having multiple devices (DEVs). One of these devices functions as a piconet coordinator (PNC) while the other devices behave in a non- coordinator role. The timing of IEEE 802.15.3 piconets are based on a repeating pattern of "superframes" in which the network devices may be allocated communications resources.    </p>
+    <boundary-data type="header">Case NC 45264 (4208-4248)</boundary-data>
+    <boundary-data type="header">60735 v<confidence value="4">i</confidence>
+    </boundary-data>
+    <p id="p-9" num="9">
+      <page-break num="3"/>
+      <confidence value="588885">[0007]</confidence>
+      Connections between the devices within an IEEE 802.15.3 piconet may be either "normal" connections or peer-to-peer connections. In "normal" connections, all traffic is routed through the PNC, while in peer-to-peer connections, all traffic is sent directly between the peer devices (DEVs). However, peer-to-peer connections still require PNC involvement as the PNC allocates a portion of the piconet's common transmission medium for the DEVs to communicate over the peer-to-peer connection. This is because, in IEEE 802.15.3 networks, the PNC handles connection establishment for all types of connections (i.e., normal and peer-to-peer) and allocates the network's resources.    </p>
+    <p id="p-10" num="10">
+      <confidence value="88888">[0008</confidence>
+]      Moreover, the PNC's role is critical during the entire pendency of a connection.    </p>
+    <p id="p-11" num="11">For instance, if a piconet's PNC loses its connection with the other DEVs in the piconet, or if the PNC needs to terminate such connections temporarily, all connections involving these DEVs are totally lost. Therefore, the PNC is a single point of failure in an IEEE 802.15.3 piconet.</p>
+    <p id="p-12" num="12">
+      <confidence value="5">[</confidence>
+000<confidence value="86">9]</confidence>
+      Recovery of the piconet from such a failure involves recreating its connections at all levels (e.g., physical, logical, link, network, etc.). Unfortunately, this is an involved process requiring tasks, such as piconet querying and the determination of nearby DEVs. Moreover, authentication and key exchange procedures may also need to be performed for the piconet to be recovered.    </p>
+    <p id="p-13" num="13">
+      <confidence value="5">[</confidence>
+0010<confidence value="5">]</confidence>
+       Such procedures are undesirable because they require a substantial amount of valuable time. Moreover, disappearance of the PNC may cause data to be lost if the piconet cannot be reformed. Accordingly, techniques are needed for devices to maintain their communications connections when contact with a coordinator device is lost.    </p>
+    <heading id="h-9">SUMMARY OF THE INVENTION</heading>
+    <p id="p-14" num="14">
+      <confidence value="2">1</confidence>
+0011]      The present invention provides recovery techniques for wireless communications devices. For instance, according to embodiments of the present invention, a device and method may participate in a wireless communications network having a coordinator device that is responsible for allocating resources in the wireless communications network. Further, the device and method may establish a peer-to-peer connection with a remote device in the wireless <boundary-data type="header">
+        <confidence value="8">2</confidence>
+      </boundary-data>
+      <boundary-data type="header">Case NC 45264 (4208-4248)</boundary-data>
+      <boundary-data type="header">60735 v<confidence value="4">l</confidence>
+      </boundary-data>
+      <page-break num="4"/>
+communications network. This peer-to-peer connection is based on a reservation of resources from the coordinator device, wherein the reservation has one or more timing parameters. Upon detecting a disappearance of the coordinator device from the wireless communications network, communications with the remote device continues according to the one or more timing parameters of the peer-to-peer connection.    </p>
+    <p id="p-15" num="15">
+      <confidence value="5">[</confidence>
+0012]      This disappearance may be detected in various ways. For instance, this detection may involve failing to receive a beacon transmission from the coordinator device, or failing to receive a predetermined number of consecutive beacon transmission from the coordinator device.    </p>
+    <p id="p-16" num="16">
+      <confidence value="58">[0</confidence>
+013<confidence value="5">]</confidence>
+      In aspects of the present invention, a query may be sent to the remote device across the peer-to-peer connection. This query asks the remote device whether it has detected the disappearance of the coordinator device from the wireless communications network. A response to this query may indicate that the remote device continues to detect the presence of the coordinator device. Alternatively, the response may indicate that the remote device has detected the disappearance of the coordinator device.    </p>
+    <p id="p-17" num="17">
+      <confidence value="5">[</confidence>
+001<confidence value="86">4]</confidence>
+      In this case, the device and method waits for a reappearance of the coordinator device during a predetermined time interval. When the coordinator device fails to reappear during the predetermined time interval, the device and method determines with the remote device whether to become a new coordinator device for the wireless communications network.    </p>
+    <p id="p-18" num="18">
+      <confidence value="58">[0</confidence>
+015<confidence value="5">]</confidence>
+      The present invention also provides an apparatus having a transceiver and controller that are configured to perform various features of the present invention. In addition, the present invention also provides computer program product and system aspects.    </p>
+    <p id="p-19" num="19">
+      <confidence value="58">[0</confidence>
+016]      Also, the present invention provides recovery techniques for networks that employ a distributed approach for the allocation of communications resources.    </p>
+    <p id="p-20" num="20">
+      <confidence value="5">[</confidence>
+0017<confidence value="5">]</confidence>
+      Embodiments of the present invention advantageously save time and prevent the loss of information. Further features and advantages of the present invention will become apparent from the following description and accompanying drawings.    </p>
+    <boundary-data type="header">
+      <confidence value="8">3</confidence>
+    </boundary-data>
+    <boundary-data type="header">Case NC 45264 (4208-4248)</boundary-data>
+    <boundary-data type="header">
+      <confidence value="5">6</confidence>
+0735 v<confidence value="4">l</confidence>
+    </boundary-data>
+    <heading id="h-10">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
+    <p id="p-21" num="21">
+      <page-break num="5"/>
+      <confidence value="88">[0</confidence>
+018]      In the drawings, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements. The drawing in which an element first appears is indicated by the leftmost digit(s) in the reference number. The present invention will be described with reference to the accompanying drawings, wherein:    </p>
+    <p id="p-22" num="22">
+      <confidence value="5">[</confidence>
+0019<confidence value="5">]</confidence>
+      FIG. 1 is a diagram of an exemplary operational environment;    </p>
+    <p id="p-23" num="23">
+      <confidence value="588885">[0020]</confidence>
+      FIG. 2 is a diagram of an exemplary superframe;    </p>
+    <p id="p-24" num="24">
+      <confidence value="588885">[0021]</confidence>
+      FIG. 3 is a diagram of an environment in which a coordinator device has disappeared;    </p>
+    <p id="p-25" num="25">
+      <confidence value="58888">[0022</confidence>
+]      FIG<confidence value="5">s</confidence>
+. 4A-4D are diagrams of various coordinator device disappearance scenarios;    </p>
+    <p id="p-26" num="26">
+      <confidence value="58888">[0023</confidence>
+]      FIG. 5 is a flowchart of an exemplary device operation, according to an embodiment of the present invention;    </p>
+    <p id="p-27" num="27">
+      <confidence value="88888">[0024</confidence>
+]      FIG<confidence value="5">s</confidence>
+. 6A-6C are diagrams of various recovery scenarios, according to embodiments of the present invention;    </p>
+    <p id="p-28" num="28">
+      <confidence value="5">[</confidence>
+002<confidence value="85">5]</confidence>
+      FIG<confidence value="5">s</confidence>
+. 7 and <part-num-ref name="and">8</part-num-ref>
+ are diagrams of an environment in which devices have recovered from a coordinator device disappearance, according to an embodiment of the present invention;    </p>
+    <p id="p-29" num="29">and <confidence value="88888">[0026</confidence>
+]      FIG. 9 is a diagram of a wireless communications device, according to an embodiment of the present invention;    </p>
+    <heading id="h-11">DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS</heading>
+    <p id="p-30" num="30">I.    Operational Environment <confidence value="588">[00</confidence>
+27]      FIG. 1 is a diagram of an environment in which the present invention may <confidence value="88">be</confidence>
+ employed. In particular, FIG. <confidence value="6">1</confidence>
+ shows a short-range wireless communications network <part-num-ref name="short-range wireless communications network">100</part-num-ref>
+ having multiple wireless communications devices. These devices include a coordinator device <boundary-data type="header">
+        <confidence value="8">4</confidence>
+      </boundary-data>
+      <boundary-data type="header">Case NC 45264 (4208-4248)</boundary-data>
+      <boundary-data type="header">60735 <confidence value="55">v1</confidence>
+      </boundary-data>
+      <page-break num="6"/>
+      <part-num-ref name="coordinator device">104</part-num-ref>
+ and multiple slave devices (DEVs) <part-num-ref name="and multiple slave devices (DEVs)">102.</part-num-ref>
+ Accordingly, network <part-num-ref name="and multiple slave devices (DEVs) 102. Accordingly, network">100</part-num-ref>
+ may be an ad hoc network such as, for example, an IEEE 802.15.3 piconet or a Bluetooth network.    </p>
+    <p id="p-31" num="31">
+      <confidence value="5">[</confidence>
+0028<confidence value="5">]</confidence>
+      In network 100, each of DEVs 102 may communicate with coordinator device <part-num-ref name="may communicate with coordinator device">104</part-num-ref>
+ across a corresponding link <part-num-ref name="corresponding link">120.</part-num-ref>
+ For instance, FIG 1 shows DEV 102a communicating with coordinator device <part-num-ref name="shows DEV 102a communicating with coordinator device">104</part-num-ref>
+ across a link 120a, DEV 102b communicating with coordinator device <part-num-ref name="link 120a, DEV 102b communicating with coordinator device">104</part-num-ref>
+ across a link 120b, DEV 102c communicating with coordinator device <part-num-ref name="link 120b, DEV 102c communicating with coordinator device">104</part-num-ref>
+ across a link 120c, and DEV 102d communicating with coordinator device <part-num-ref name="link 120c, and DEV 102d communicating with coordinator device">104</part-num-ref>
+ across a link 120d.    </p>
+    <p id="p-32" num="32">
+      <confidence value="888">[00</confidence>
+ <confidence value="88">29</confidence>
+]     Each of these links 120 are referred to herein as indirect links when considering communications between DEVs <part-num-ref name="are referred to herein as indirect links when considering communications between DEVs">102,</part-num-ref>
+ because they provide multihop routes for communications between DEVs <part-num-ref name="are referred to herein as indirect links when considering communications between DEVs 102, because they provide multihop routes for communications between DEVs">102</part-num-ref>
+ through coordinator device <part-num-ref name="through coordinator device">104.</part-num-ref>
+ As an alternative to such indirect links, DEVs <part-num-ref name="alternative to such indirect links, DEVs">102</part-num-ref>
+ may communicate with each other directly. For instance, FIG. 1 shows DEVs 102a and 102b communicating across a direct link 122a (a peer-to-peer connection).    </p>
+    <p id="p-33" num="33">
+      <confidence value="5">[</confidence>
+0030<confidence value="5">]</confidence>
+      Links 120 provide for coordinator device <part-num-ref name="provide for coordinator device">104</part-num-ref>
+ to transmit network configuration information (e.g., beacons) to DEVs <part-num-ref name="beacons) to DEVs">102.</part-num-ref>
+ The network configuration information (which, in embodiments is included in beacons) may include resource allocation information, such as particular resource allocations, for various network connections according. For instance, in embodiments of the present invention, coordinator device <part-num-ref name="present invention, coordinator device">104</part-num-ref>
+ is responsible for allocating resources that establish connections across both indirect links <part-num-ref name="is responsible for allocating resources that establish connections across both indirect links">120</part-num-ref>
+ and direct links <part-num-ref name="and direct links">122.</part-num-ref>
+ In addition, coordinator device <part-num-ref name="and direct links 122. In addition, coordinator device">104</part-num-ref>
+ may repeatedly communicate information regarding these connections through beacon transmissions.    </p>
+    <p id="p-34" num="34">II.   Superframe <confidence value="5">[</confidence>
+0031<confidence value="5">]</confidence>
+      Wireless network transmissions in the environment of FIG. 1 may be based on a repeating time pattern, such as a superframe. An exemplary superframe format is shown in FIG.    </p>
+    <p id="p-35" num="35">2. In particular, FIG. 2 shows a frame format having superframes 202a, 202b, and 202c.</p>
+    <p id="p-36" num="36">
+      <confidence value="588885">[0032]</confidence>
+      Each superframe 202 includes a beacon period <part-num-ref name="beacon period">204</part-num-ref>
+ and a data transfer period <part-num-ref name="data transfer period">206.</part-num-ref>
+    </p>
+    <p id="p-37" num="37">Beacon periods 204 convey network configuration information transmissions from at least the piconet coordinator device (PNC) of the beaconing group. For instance, such information may <boundary-data type="header">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+      <boundary-data type="header">Case NC 45264 (4208-4248)</boundary-data>
+      <boundary-data type="header">60735 v<confidence value="4">l</confidence>
+      </boundary-data>
+      <page-break num="7"/>
+be used to set resource allocations and to communicate management information for the beaconing group. Moreover, in embodiments of the present invention, data transfer periods <part-num-ref name="present invention, data transfer periods">206</part-num-ref>
+ may be used to transmit information regarding services and features (e.g., information services, applications, games, topologies, rates, security features, etc.) of devices within the beaconing group.    </p>
+    <p id="p-38" num="38">
+      <confidence value="588885">[0033]</confidence>
+       Data transfer period 206 is used for devices to communicate data according to various transmission schemes. These schemes may include, for example, various modulation techniques. Also, these schemes may include frequency hopping techniques. Exemplary frequency hopping techniques include orthogonal frequency division multiplexing (OFDM) and/or time frequency codes (TFCs).    </p>
+    <p id="p-39" num="39">
+      <confidence value="5">[</confidence>
+0034<confidence value="5">]</confidence>
+       Data transfer periods 206 may support data communications across links <part-num-ref name="may support data communications across links">120</part-num-ref>
+ and <part-num-ref name="and">122.</part-num-ref>
+ For example, FIG. 2 shows an exemplary reservation of peer-to-peer links <part-num-ref name="exemplary reservation of peer-to-peer links">122</part-num-ref>
+ within data transfer period <part-num-ref name="within data transfer period">206.</part-num-ref>
+ In embodiments, these allocations involve allocations provided by coordinator device <part-num-ref name="within data transfer period 206. In embodiments, these allocations involve allocations provided by coordinator device">104.</part-num-ref>
+ FIG. 2 shows that these reservations have one or more timing parameters. For example, FIG. 2 shows the reservation for link 122a having a start time <part-num-ref name="start time">210,</part-num-ref>
+ and end time <part-num-ref name="start time 210, and end time">212,</part-num-ref>
+ and a duration <part-num-ref name="duration">214</part-num-ref>
+ within a data transfer period length <part-num-ref name="data transfer period length">216.</part-num-ref>
+ <confidence value="5">I</confidence>
+n addition, devices (e.g., DEVs 102a-d) may use data transfer periods <part-num-ref name="DEVs 102a-d) may use data transfer periods">206</part-num-ref>
+ to transmit control information, such as request messages to other devices. To facilitate the transmission of traffic, each device may <confidence value="88">be</confidence>
+ assigned a particular time slot within each data transfer period <part-num-ref name="particular time slot within each data transfer period">206.</part-num-ref>
+    </p>
+    <p id="p-40" num="40">III.  Disappearance Scenarios <confidence value="5">[</confidence>
+0035]      As discussed above, a coordinator device may "disappear" from an environment, such as communications network <part-num-ref name="environment, such as communications network">100.</part-num-ref>
+ FIG. 3 provides an example of such a disappearance. In particular, FIG. 3 illustrates coordinator device <part-num-ref name="illustrates coordinator device">104</part-num-ref>
+ losing its communications links with DEVs <part-num-ref name="losing its communications links with DEVs">102.</part-num-ref>
+ This is indicated in FIG. 3 by links <part-num-ref name="by links">120</part-num-ref>
+ being crossed-out. The disappearance may occur for various reasons, such as coordinator device <part-num-ref name="disappearance may occur for various reasons, such as coordinator device">104</part-num-ref>
+ moving beyond the communications range of DEVs <part-num-ref name="communications range of DEVs">102,</part-num-ref>
+ the occurrence of interference from other systems, or the loss of power (e.g., a low battery condition) in coordinator device <part-num-ref name="low battery condition) in coordinator device">104.</part-num-ref>
+    </p>
+    <boundary-data type="header">
+      <confidence value="8">6</confidence>
+    </boundary-data>
+    <boundary-data type="header">Case NC 45264 (4208-4248)</boundary-data>
+    <boundary-data type="header">60735 v<confidence value="4">i</confidence>
+    </boundary-data>
+    <p id="p-41" num="41">
+      <page-break num="8"/>
+      <confidence value="5">[</confidence>
+0036<confidence value="5">]</confidence>
+      As a result, DEVs <part-num-ref name="result, DEVs">102</part-num-ref>
+ are unable to communicate with coordinator device <part-num-ref name="are unable to communicate with coordinator device">104,</part-num-ref>
+ thus precluding communications between DEVs <part-num-ref name="are unable to communicate with coordinator device 104, thus precluding communications between DEVs">102</part-num-ref>
+ across indirect links. Moreover, DEVs <part-num-ref name="across indirect links. Moreover, DEVs">102</part-num-ref>
+ are unable to establish direct links with each other because there is no coordinator device to perform allocation operations for such links. However, according to embodiments of the present invention, these links may be maintained through recovery techniques in which a device for each of these links becomes a new coordinator device. This techniques are described in greater detail below.    </p>
+    <p id="p-42" num="42">
+      <confidence value="58888">[0037</confidence>
+]      Although FIG. 3 shows a complete disappearance of coordinator device <part-num-ref name="complete disappearance of coordinator device">104,</part-num-ref>
+ various other scenarios may occur. Examples of such scenarios are shown in FIGs. 4A-4D.    </p>
+    <p id="p-43" num="43">Each of these drawings shows a coordinator device <part-num-ref name="coordinator device">404</part-num-ref>
+ and DEVs 402a and 402b. In each of these scenarios, a direct link <part-num-ref name="direct link">422</part-num-ref>
+ exists between DEVs 402a and 402b.    </p>
+    <p id="p-44" num="44">
+      <confidence value="5">[</confidence>
+0038<confidence value="5">]</confidence>
+      In the scenario of FIG. 4A, coordinator device <part-num-ref name="scenario of FIG. 4A, coordinator device">404</part-num-ref>
+ is completely visible to devices 402a and 402b. Accordingly, a link 420a exists between devices <part-num-ref name="link 420a exists between devices">404</part-num-ref>
+ and 402a, and a link 420b exists between devices <part-num-ref name="link 420b exists between devices">404</part-num-ref>
+ and 402b.    </p>
+    <p id="p-45" num="45">
+      <confidence value="588885">[0039]</confidence>
+      In the scenario of FIG. 4B, coordinator device <part-num-ref name="scenario of FIG. 4B, coordinator device">404</part-num-ref>
+ has completely disappeared.    </p>
+    <p id="p-46" num="46">Accordingly, links 420a and 420b no longer exist. However, link 422 between devices 402a and 402b may still exist and remain intact.</p>
+    <p id="p-47" num="47">[0040<confidence value="5">]</confidence>
+      FIG. 4C and 4D show scenarios in which coordinator device 404 has partially disappeared. More particularly, in FIG. 4C, coordinator device <part-num-ref name="has partially disappeared. More particularly, in FIG. 4C, coordinator device">404</part-num-ref>
+ remains visible to device 402b but is no longer visible to device 402a. However, link <part-num-ref name="remains visible to device 402b but is no longer visible to device 402a. However, link">422</part-num-ref>
+ between devices 402a and 402b may remain intact.    </p>
+    <p id="p-48" num="48">
+      <confidence value="5">[</confidence>
+0041]      In contrast, FIG. 4D shows a scenario in which coordinator device <part-num-ref name="scenario in which coordinator device">404</part-num-ref>
+ remains visible to device 402a, but is no longer visible to device 402b. However, link <part-num-ref name="remains visible to device 402a, but is no longer visible to device 402b. However, link">422</part-num-ref>
+ between devices 402a and 402b may remain intact.    </p>
+    <boundary-data type="header">
+      <confidence value="8">7</confidence>
+    </boundary-data>
+    <boundary-data type="header">Case NC 45264 (4208-4248)</boundary-data>
+    <boundary-data type="header">60735 v<confidence value="4">l</confidence>
+    </boundary-data>
+    <p id="p-49" num="49">
+      <page-break num="9"/>
+IV.   Operation <confidence value="5">[</confidence>
+0042<confidence value="5">]</confidence>
+       Aspects of the present invention provide techniques in which devices recover from coordinator disappearance scenarios, such as the scenarios of FIG<confidence value="5">s</confidence>
+. 4A-4D. Accordingly, FIG. 5 is a flowchart of an exemplary device operation, according to an embodiment of the present invention. This operation provides for continued communications when a coordinator device disappears.    </p>
+    <p id="p-50" num="50">
+      <confidence value="5">[</confidence>
+0043<confidence value="5">]</confidence>
+       As shown in FIG. 5, this operation includes a step <part-num-ref name="step">502.</part-num-ref>
+ In this step, a device (e.g., a slave device or DEV) participates in a short-range wireless communications network, such as an IEEE 802.15.3 piconet or a Bluetooth network. This network includes a coordinator (e.g., a PNC). Accordingly, the device may participate in the network as a slave device or DEV.    </p>
+    <p id="p-51" num="51">
+      <confidence value="5">[</confidence>
+0044<confidence value="5">]</confidence>
+       In a step <part-num-ref name="step">504,</part-num-ref>
+ the device establishes a direct or peer-to-peer type of connection with a remote device. As discussed above, this connection exists across a direct link (e.g., one of links 122). Accordingly, step <part-num-ref name="one of links 122). Accordingly, step">504</part-num-ref>
+ may involve obtaining a reservation from the coordinator device. In embodiments, this reservation may be static such that it may exist so long as the participating devices desire.    </p>
+    <p id="p-52" num="52">
+      <confidence value="5">[</confidence>
+0045<confidence value="5">]</confidence>
+       This reservation has one or more timing parameters. Examples of such timing parameters may include starting time(s), ending time(s), and/or duration<confidence value="7">s</confidence>
+) within a timing format, such as a superframe. For instance, FIG. 2 shows a exemplary timing parameters within data transfer period 206a. In particular, FIG. 2 shows reservations for links <part-num-ref name="shows reservations for links">120</part-num-ref>
+ and <part-num-ref name="and">122</part-num-ref>
+ having particular timing (e.g., start times, end times, and/or durations) within the length (or duration) of data transfer period 206a.    </p>
+    <p id="p-53" num="53">
+      <confidence value="5">[</confidence>
+0046<confidence value="5">]</confidence>
+       During operation of the network, the coordinator device periodically transmits signals (or beacons) containing network status information. Thus, in a step <part-num-ref name="step">506,</part-num-ref>
+ the device determines whether it has received a beacon from the coordinator device. If so, then the device continues using the allocated reservation, as indicated by a step <part-num-ref name="step">508.</part-num-ref>
+ However, if the device has not received a beacon from the coordinator device, then a step <part-num-ref name="step">510</part-num-ref>
+ is performed. In embodiments, step <part-num-ref name="is performed. In embodiments, step">510</part-num-ref>
+ is performed when a single coordinator device beacon is not received.    </p>
+    <p id="p-54" num="54">However, in alternate embodiments, operation proceeds from step 508 to step <part-num-ref name="to step">510</part-num-ref>
+ when a predetermined number of consecutive coordinator device beacons are not received.    </p>
+    <boundary-data type="header">
+      <confidence value="8">8</confidence>
+    </boundary-data>
+    <boundary-data type="header">Case NC 45264 (4208-4248)</boundary-data>
+    <boundary-data type="header">60735 v<confidence value="1">l</confidence>
+    </boundary-data>
+    <p id="p-55" num="55">
+      <page-break num="10"/>
+      <confidence value="588885">[0047]</confidence>
+      In step 510, the device transmits a query to the remote device across the peer-to- peer connection established in step <part-num-ref name="peer-to- peer connection established in step">504.</part-num-ref>
+ This query asks the remote device whether it has received a beacon from the coordinator device. The device may utilize a predetermined portion of the link to transmit this query. For instance, this query may be transmitted during the initial portion of the resource (e.g., MAS(s)) reserved for this peer-to-peer connection. It should be further noted that according to embodiments of the present invention, a device may, instead of transmitting a query, receive a query asking whether it has received a beacon from the coordinator device.    </p>
+    <p id="p-56" num="56">
+      <confidence value="5">[</confidence>
+0048<confidence value="5">]</confidence>
+      As indicated by a step <part-num-ref name="step">512,</part-num-ref>
+ the device may or may not receive a response to this query. If no response is received, then operation proceeds to a step <part-num-ref name="step">514.</part-num-ref>
+ In this step, the device commences a scanning operation to locate other devices (such as the remote device). This scanning may commence after a predetermined amount of time elapses. For instance, in the context of IEEE 802.15.3 networks, step <part-num-ref name="context of IEEE 802.15.3 networks, step">514</part-num-ref>
+ may be performed after a certain number of superframe durations have passed.    </p>
+    <p id="p-57" num="57">
+      <confidence value="5">[</confidence>
+0049<confidence value="5">]</confidence>
+      However, if a query response is received from the remote device, then in a step <part-num-ref name="step">516,</part-num-ref>
+ the device determines from the response whether the remote device has received a beacon from the coordinator device. If so, then operation proceeds to step <part-num-ref name="coordinator device. If so, then operation proceeds to step">508.</part-num-ref>
+ As indicated above, in step <part-num-ref name="coordinator device. If so, then operation proceeds to step 508. As indicated above, in step">508,</part-num-ref>
+ the device continues using the allocated reservation for direct communication with the remote device.    </p>
+    <p id="p-58" num="58">
+      <confidence value="5">[</confidence>
+0050]      The device may receive a response to the query indicating that the remote device has received a beacon. Such a response may also include the contents of the received beacon.    </p>
+    <p id="p-59" num="59">As shown in FIG. 5, if such a response is received, then operation proceeds to step <part-num-ref name="response is received, then operation proceeds to step">508.</part-num-ref>
+ As indicated above, in step <part-num-ref name="response is received, then operation proceeds to step 508. As indicated above, in step">508,</part-num-ref>
+ the device continues using the allocated reservation.    </p>
+    <p id="p-60" num="60">
+      <confidence value="5">[</confidence>
+0051]      Alternatively, the device may receive a response to the query indicating that the remote device has not received a beacon. If such a response is received, then a step <part-num-ref name="step">518</part-num-ref>
+ is performed. In step <part-num-ref name="is performed. In step">518,</part-num-ref>
+ the device waits to receive a beacon for a predetermined amount of time, such as a predetermined number of superframes.    </p>
+    <p id="p-61" num="61">
+      <confidence value="5">[</confidence>
+0052<confidence value="5">]</confidence>
+      As indicated by a step <part-num-ref name="step">520,</part-num-ref>
+ if the device receives a beacon within this predetermined amount of time, then operation proceeds to step <part-num-ref name="beacon within this predetermined amount of time, then operation proceeds to step">508</part-num-ref>
+ in which the device continues <boundary-data type="header">
+        <confidence value="8">9</confidence>
+      </boundary-data>
+      <boundary-data type="header">Case NC 45264 (4208-4248)</boundary-data>
+      <boundary-data type="header">60735 v<confidence value="1">l</confidence>
+      </boundary-data>
+      <page-break num="11"/>
+using the reservation. However, if a beacon is not received during this predetermined amount of time, then a step <part-num-ref name="step">522</part-num-ref>
+ is performed. In step <part-num-ref name="is performed. In step">522,</part-num-ref>
+ the device and the remote device continue direct communications using the same timing (i.e., the same time slots of the superframe) that was allocated to the devices by the coordinator device in the superframe reservation of the extinct network (e.g., piconet).    </p>
+    <p id="p-62" num="62">[0053<confidence value="5">]</confidence>
+       In a step <part-num-ref name="step">523,</part-num-ref>
+ the device and the remote device determine which of them will become the coordinator device of a new network (e.g., piconet). Accordingly, this step may comprise the two devices negotiating to select which device will become this coordinator.    </p>
+    <p id="p-63" num="63">[0054<confidence value="5">]</confidence>
+       Such determination or negotiation may be based on various rules or factors, such as device parameters. Examples of such parameters may include, for example, one or more of remaining battery power, , device orientation including the number of devices a device can hear, device ID, and the like.    </p>
+    <p id="p-64" num="64">
+      <confidence value="5">[</confidence>
+0055]       If the negotiation indicates that the device should become a new coordinator device, the device becomes the new coordinator device (e.g., PNC) in a step <part-num-ref name="step">524.</part-num-ref>
+ Thereafter, the device (as a new coordinator device) renews the direct connection reservation with the remote device. In addition, while renewing this connection, the device may perform a scanning operation to ensure that any other coordinator devices within its coverage area are detected.    </p>
+    <p id="p-65" num="65">V.    Query and Response Mechanisms <confidence value="5">[</confidence>
+0056<confidence value="5">]</confidence>
+       Aspects of the present invention involve the transmission of queries and responses. Examples of these queries are described above with reference to steps <part-num-ref name="transmission of queries and responses. Examples of these queries are described above with reference to steps">510</part-num-ref>
+ and <part-num-ref name="and">512.</part-num-ref>
+    </p>
+    <p id="p-66" num="66">Such queries and responses may be embedded in existing frame formats, or in new fields. Also, new messages may be defined to handle these queries and responses.</p>
+    <p id="p-67" num="67">
+      <confidence value="5">[</confidence>
+0057<confidence value="5">]</confidence>
+       In embodiments of the present invention, the direct or peer-to-peer type of connection may be configured for data transfer that is predominately unidirectional. Such transfers may include, for example, downloads, file transfers, and/or server responses to client requests. For such transfers, the majority of data packets may be transmitted by one peer device, while the other device transmits smaller acknowledgment packets to signal the successful (or <boundary-data type="header">
+        <confidence value="88">10</confidence>
+      </boundary-data>
+      <boundary-data type="header">Case NC 45264 (4208-4248)</boundary-data>
+      <boundary-data type="header">
+        <confidence value="5">6</confidence>
+0735 <confidence value="4">v</confidence>
+      </boundary-data>
+      <page-break num="12"/>
+unsuccessful) reception of previously transmitted data packets. In embodiments of the present invention, queries and responses may be transmitted in data packets and acknowledgment packets.    </p>
+    <p id="p-68" num="68">VI.   Recovery Scenarios <confidence value="5">[</confidence>
+0058]      FIG<confidence value="5">s</confidence>
+. 6A-6C are diagrams of exemplary recovery scenarios, according to embodiments of the present invention. In particular, FIG<confidence value="5">s</confidence>
+. 6A-6C show sequences of events along a time axis <part-num-ref name="time axis">600.</part-num-ref>
+ These scenarios involve a network that includes two devices (device A and device B) and a coordinator device. Accordingly, these scenarios may occur in the environment of FIG. 1 as well as in other environments.    </p>
+    <p id="p-69" num="69">[0059]      Each of the depicted recovery scenarios involves a different type of coordinator device disappearance. For instance, FIG. 6A involves a total disappearance. As shown in FIG.</p>
+    <p id="p-70" num="70">6A, a step <part-num-ref name="step">602</part-num-ref>
+ occurs in which devices A and B establish a peer-to-peer connection. This establishment may involve various resource allocation processes handled by the coordinator device. Subsequent to this, a step <part-num-ref name="step">604</part-num-ref>
+ occurs in which neither device A nor device B receives a beacon transmission from the coordinator device. As a result of this, device A queries device B whether it received a beacon from the coordinator device, as shown by step <part-num-ref name="coordinator device, as shown by step">606.</part-num-ref>
+ It should be further noted that, according to embodiments of the present invention, device B may alternatively be the party sending the query. Following this, in a step <part-num-ref name="step">608,</part-num-ref>
+ device A receives a response from device B (or vice versa). This response indicates device B's failure to receive a beacon from the coordinator device.    </p>
+    <p id="p-71" num="71">
+      <confidence value="5">[</confidence>
+0060]      At this point, devices A and B understand that the coordinator device has disappeared from their mutual perspective. Despite this, in a step <part-num-ref name="step">610,</part-num-ref>
+ devices A and B continue to use the previous channel allocation for direct peer-to-peer communication. However, to provide a complete network, the devices need to negotiate which of the devices should become a new network (e.g., piconet) coordinator. According to an exemplary embodiment, device A becomes the coordinator device in a step <part-num-ref name="step">612</part-num-ref>
+ after a negotiation indicated that device A should become the new coordinator. This step may be performed after the occurrence of a <boundary-data type="header">
+        <confidence value="88">11</confidence>
+      </boundary-data>
+      <boundary-data type="header">Case NC 45264 (4208-4248)</boundary-data>
+      <boundary-data type="header">60735 <confidence value="4">v</confidence>
+      </boundary-data>
+      <page-break num="13"/>
+predetermined time interval in which a beacon is not received from the missing coordinator device.    </p>
+    <p id="p-72" num="72">
+      <confidence value="5">[</confidence>
+0061<confidence value="5">]</confidence>
+      FIG<confidence value="5">s</confidence>
+. 6B and 6C involve embodiments of the present invention in which only one device of a peer-to-peer connection loses contact with the coordinator device. For instance, in FIG. 6B, devices A and B establish a peer-to-peer connection in a step <part-num-ref name="step">620.</part-num-ref>
+ In a step <part-num-ref name="step">622,</part-num-ref>
+ the coordinator device beacon is received by device B, but not by device A. Following step <part-num-ref name="Following step">622,</part-num-ref>
+ device A queries device B whether it received a beacon from the coordinator device in a step <part-num-ref name="step">624.</part-num-ref>
+ Device A receives a response to the query in a step <part-num-ref name="step">626.</part-num-ref>
+ This response indicates that device B received the beacon from the coordinator device. In addition, the response may include information (such as parameters relating to the allocation of the peer-to-peer connection) that were contained in the beacon.    </p>
+    <p id="p-73" num="73">
+      <confidence value="5">[</confidence>
+0062<confidence value="5">]</confidence>
+      Upon receipt of this response, device A has indirectly received information regarding the coordinator device's beacon from device B. Thus, in a step <part-num-ref name="step">628,</part-num-ref>
+ devices A and B may continue to use the allocated reservation for the peer-to-peer connection without one of these devices becoming a new coordinator device of a newly established piconet.    </p>
+    <p id="p-74" num="74">[0063]      In FIG. 6C, devices A and B establish a peer-to-peer connection in a step <part-num-ref name="step">630.</part-num-ref>
+    </p>
+    <p id="p-75" num="75">However, in a step <part-num-ref name="step">632,</part-num-ref>
+ the coordinator device beacon is received by device B, but not by device A. Thus, in a step <part-num-ref name="step">634,</part-num-ref>
+ device B receives a query from device A that asks whether device A receives the coordinator device's beacon. In a step <part-num-ref name="step">636,</part-num-ref>
+ device B sends device A a response to this query indicating that it received this beacon. This response may include information (such as parameters of the peer-to-peer connection) that were contained in the beacon. Thus, in a step <part-num-ref name="step">628,</part-num-ref>
+ devices A and B may continue to use the allocated reservation for the peer-to-peer connection without one of these devices becoming a coordinator device of a newly established piconet.    </p>
+    <p id="p-76" num="76">
+      <confidence value="588885">[0064]</confidence>
+      Referring again to FIG. 1, network 100 includes a coordinator device <part-num-ref name="coordinator device">104.</part-num-ref>
+ Also, this network includes two direct or peer-to-peer type connections across links 122a and 122b. As described above, the term "peer-to-peer" indicates a direct, single-hop connection between two devices in a wireless ad-hoc network including a coordinator device, wherein neither of the devices participating in the connection is the coordinator device. FIG. 3 shows a situation in <boundary-data type="header">
+        <confidence value="88">12</confidence>
+      </boundary-data>
+      <boundary-data type="header">Case NC 45264 (4208-4248)</boundary-data>
+      <boundary-data type="header">60735 v<confidence value="4">i</confidence>
+      </boundary-data>
+      <page-break num="14"/>
+which coordinator device <part-num-ref name="situation in which coordinator device">104</part-num-ref>
+ totally disappears from the perspective of the these peer-to-peer connections. According to aspects of the present invention, these links are maintained through recovery techniques in which a device for each of these links becomes a new coordinator device.    </p>
+    <p id="p-77" num="77">
+      <confidence value="588885">[0065]</confidence>
+      As described above, a device in a peer-to-peer connection may become a new coordinator device when, for instance, the existing coordinator device disappears from the perspective of each of the peer devices. For instance, FIG. 7 shows such a recovery, according to an embodiment of the present invention. In this recovery, device 102a becomes a coordinator device for a new network 700a, which includes devices 102a and 102b. Also, FIG. 7 shows device 102c becoming a coordinator device for a new network 700b, which includes devices 102c and 102d.    </p>
+    <p id="p-78" num="78">
+      <confidence value="588885">[0066]</confidence>
+      Once devices 102a and 102c have become coordinator devices, two networks exist. However, these networks may merge into a single wireless network. FIG. 8 provides an example of such a merger. In this example, networks 700a and 700b have merged into a single network <part-num-ref name="single network">800.</part-num-ref>
+ This merger occurred by devices 102a and 102c (i.e., the coordinator devices for networks 700a and 700b, respectively) engaging in a coordinator negotiation <part-num-ref name="coordinator negotiation">802.</part-num-ref>
+    </p>
+    <p id="p-79" num="79">[0067<confidence value="5">]</confidence>
+      This negotiation involves the exchange of information between these devices and results in one of the devices taking on the coordinator device role. For instance, these devices may determine which one should be the coordinator device based on their operating characteristics, such as their remaining battery power or power source. As shown in FIG. 8, device 102a has assumed this role. From this merger, network <part-num-ref name="coordinator device based on their operating characteristics, such as their remaining battery power or power source. As shown in FIG. 8, device 102a has assumed this role. From this merger, network">800</part-num-ref>
+ is formed, which is similar in scope to network <part-num-ref name="is formed, which is similar in scope to network">100</part-num-ref>
+ of FIG. 1.    </p>
+    <p id="p-80" num="80">VII.  Wireless Communications Device <confidence value="5">[</confidence>
+0068]      As described above, wireless communications devices, such as DEVs 102, may employ the techniques of the present invention. Accordingly, such devices may be implemented in hardware, software, firmware, or any combination thereof. One such implementation is shown in FIG. 9. This implementation includes a processor (controller) <part-num-ref name="processor (controller)">910,</part-num-ref>
+ a memory <part-num-ref name="memory">912,</part-num-ref>
+ and <boundary-data type="header">
+        <confidence value="88">13</confidence>
+      </boundary-data>
+      <boundary-data type="header">Case NC 45264 (4208-4248)</boundary-data>
+      <boundary-data type="header">60735 v<confidence value="1">l</confidence>
+      </boundary-data>
+      <page-break num="15"/>
+a user interface <part-num-ref name="user interface">914.</part-num-ref>
+ In addition, the implementation of FIG. 9 includes a transceiver <part-num-ref name="transceiver">920</part-num-ref>
+ and an antenna <part-num-ref name="antenna">922.</part-num-ref>
+    </p>
+    <p id="p-81" num="81">
+      <confidence value="5">[</confidence>
+0069<confidence value="5">]</confidence>
+       As shown in FIG. 9, transceiver 920 is coupled to antenna <part-num-ref name="is coupled to antenna">922.</part-num-ref>
+ Transceiver <part-num-ref name="is coupled to antenna 922. Transceiver">920</part-num-ref>
+ includes electronics, which allow the device (in conjunction with antenna <part-num-ref name="device (in conjunction with antenna">922)</part-num-ref>
+ to exchange wireless signals remote devices, such as other DEVs <part-num-ref name="to exchange wireless signals remote devices, such as other DEVs">102.</part-num-ref>
+ Accordingly, transceiver <part-num-ref name="to exchange wireless signals remote devices, such as other DEVs 102. Accordingly, transceiver">920</part-num-ref>
+ may include a transmitter and a receiver. In embodiments, transceiver may handle the exchange of ultra wideband (UWB) signals. For the transmission of <confidence value="5">U</confidence>
+WB signals, such electronics may include modulation components (e.g., OFDM modulators) <confidence value="222222">and/or</confidence>
+ a pulse generator for certain types of impulse UWB transmissions. For the reception of UWB signals, such electronics may include demodulation components (e.g., OFDM demodulators), timing circuitry, and filters.    </p>
+    <p id="p-82" num="82">
+      <confidence value="5">[</confidence>
+0070<confidence value="5">]</confidence>
+       As shown in FIG. 9, processor 910 is coupled to transceiver <part-num-ref name="is coupled to transceiver">920.</part-num-ref>
+ Processor <part-num-ref name="is coupled to transceiver 920. Processor">910</part-num-ref>
+ controls device operation. Processor <part-num-ref name="controls device operation. Processor">910</part-num-ref>
+ may be implemented with one or more microprocessors that are each capable of executing software instructions (program code) stored in memory <part-num-ref name="may be implemented with one or more microprocessors that are each capable of executing software instructions (program code) stored in memory">912.</part-num-ref>
+    </p>
+    <p id="p-83" num="83">
+      <confidence value="5">[</confidence>
+0071<confidence value="5">]</confidence>
+       Memory 912 is a computer readable medium that may include random access memory (RAM), read only memory (ROM), and/or flash memory, and stores information in the form of data and software components (also referred to herein as modules). These software components include instructions (e.g., logic) that can be executed by processor <part-num-ref name="logic) that can be executed by processor">910.</part-num-ref>
+ Various types of software components may be stored in memory <part-num-ref name="logic) that can be executed by processor 910. Various types of software components may be stored in memory">912.</part-num-ref>
+ For instance, memory <part-num-ref name="logic) that can be executed by processor 910. Various types of software components may be stored in memory 912. For instance, memory">912</part-num-ref>
+ may store software components that control the operations of transceiver <part-num-ref name="operations of transceiver">920.</part-num-ref>
+ Also, memory <part-num-ref name="operations of transceiver 920. Also, memory">912</part-num-ref>
+ may store software components that provide for the functionality of a media access controller (MAC). This controller may perform various features, such as the steps described with reference to FIG. 3. It is important to note that the MAC may be implemented in hardware, software, firmware, or any combination thereof.    </p>
+    <p id="p-84" num="84">
+      <confidence value="588">[00</confidence>
+ <confidence value="885">72]</confidence>
+      In addition, memory 912 may store software components that control the exchange of information through user interface <part-num-ref name="exchange of information through user interface">914.</part-num-ref>
+ As shown in FIG. 9, user interface <part-num-ref name="exchange of information through user interface 914. As shown in FIG. 9, user interface">914</part-num-ref>
+ is also coupled to processor <part-num-ref name="is also coupled to processor">910.</part-num-ref>
+ User interface <part-num-ref name="is also coupled to processor 910. User interface">914</part-num-ref>
+ facilitates the exchange of information with a user. FIG. 9 shows that user interface <part-num-ref name="shows that user interface">914</part-num-ref>
+ includes a user input portion <part-num-ref name="user input portion">916</part-num-ref>
+ and a user output portion <part-num-ref name="user output portion">918.</part-num-ref>
+ User input portion <part-num-ref name="user output portion 918. User input portion">916</part-num-ref>
+ may include one or more devices that allow a user to input <boundary-data type="header">
+        <confidence value="88">14</confidence>
+      </boundary-data>
+      <boundary-data type="header">Case NC 45264 (4208-4248)</boundary-data>
+      <boundary-data type="header">
+        <confidence value="5">6</confidence>
+0735 v<confidence value="4">i</confidence>
+      </boundary-data>
+      <page-break num="16"/>
+information. Examples of such devices include keypads, touch screens, and microphones. User output portion <part-num-ref name="user to input information. Examples of such devices include keypads, touch screens, and microphones. User output portion">918</part-num-ref>
+ allows a user to receive information from the wireless communications device. Thus, user output portion <part-num-ref name="wireless communications device. Thus, user output portion">918</part-num-ref>
+ may include various devices, such as a display, and one or more audio speakers. Exemplary displays include liquid crystal displays (LCDs), and video displays.    </p>
+    <p id="p-85" num="85">
+      <confidence value="588885">[0073]</confidence>
+      The elements shown in FIG. 9 may be coupled according to various techniques.    </p>
+    <p id="p-86" num="86">One such technique involves coupling transceiver 920, processor 910, memory 912, and user interface 914 through one or more bus interfaces. In addition, each of these components is coupled to a power source, such as a rechargeable <confidence value="222222">and/or</confidence>
+ removable battery pack (not shown).    </p>
+    <p id="p-87" num="87">VIII. Distributed Control Networks <confidence value="5">[</confidence>
+0074<confidence value="5">]</confidence>
+      The above description has been made with reference to networks having a central coordinator device. However, techniques of the present invention may also be applied in networks that do not employ a central coordinator. An example of such a network is defined by the Multiband OFDM Alliance (MBOA).    </p>
+    <p id="p-88" num="88">
+      <confidence value="5">[</confidence>
+0075<confidence value="5">]</confidence>
+      MBOA involves the development of a high rate physical layer (PHY) standard for the IEEE 802.15.3a WPAN. In particular, this PHY involves a frequency hopping application of orthogonal frequency division multiplexing (OFDM). In addition, the MBOA is focused on developing a Medium Access Control (MAC) layer that would be used with the OFDM physical.    </p>
+    <p id="p-89" num="89">A current version of the MBOA MAC involves a group of wireless communications devices (referred to as a beaconing group) capable of communicating with each other. The timing employed by beaconing groups is based on a repeating pattern of superframes in which the devices may be allocated communications resources.</p>
+    <p id="p-90" num="90">
+      <confidence value="5">[</confidence>
+0076<confidence value="5">]</confidence>
+      The MBOA MAC layer provides for the allocation of resources through beacon transmissions. Each device in a beaconing group is assigned a portion of bandwidth to transmit beacons. However, instead of having a central coordinator, the MBOA MAC provides a distributed control approach. According to this approach, multiple devices share MAC layer <boundary-data type="header">
+        <confidence value="88">15</confidence>
+      </boundary-data>
+      <boundary-data type="header">Case NC 45264 (4208-4248)</boundary-data>
+      <boundary-data type="header">60735 v<confidence value="4">i</confidence>
+      </boundary-data>
+      <page-break num="17"/>
+responsibilities, such as various channel access mechanisms that allow devices to allocate portions of the transmission medium for communications traffic. These mechanisms include a protocol called the distributed reservation protocol (DRP), and a protocol called prioritized contention access (PCA). Thus in these networks, the existence of a beacon period (BP), but not a coordinator, is needed, [0077]      In certain situations, the MBOA beacon period can become corrupted due to interference in the corresponding time period. When this occurs, beacons from other devices may not be received. Moreover, techniques of the present invention, such as the operation of FIG. 5, may be employed.    </p>
+    <p id="p-91" num="91">
+      <confidence value="58888">[0078</confidence>
+]      For instance, in an exemplary embodiment, a device and a remote device have a peer-to-peer connection in a network that does not have a central controller (e.g., an MBOA network). Accordingly, if the device does not receive any beacons from other devices in the network (e.g., in its beaconing group), then (as in step <part-num-ref name="in its beaconing group), then (as in step">510)</part-num-ref>
+ the device may send an inquiry to the remote device.    </p>
+    <p id="p-92" num="92">
+      <confidence value="5">[</confidence>
+0079<confidence value="5">]</confidence>
+      If the remote device replies affirmatively that it received beacons from the other devices in the beaconing group, then (as indicated by steps <part-num-ref name="beaconing group, then (as indicated by steps">516</part-num-ref>
+ and <part-num-ref name="and">508)</part-num-ref>
+ the device may safely use its preexisting allocation. In this case, the device has been assured that no collision will occur with members of its beaconing group or with devices in neighboring beaconing groups.    </p>
+    <p id="p-93" num="93">
+      <confidence value="5">[</confidence>
+0080<confidence value="5">]</confidence>
+      Conversely, if the remote device indicates that it does not hear any beacons either, the devices may continue to use the preexisting allocation (as in step 522). However, since in this case, collisions may still occur, the devices keep searching for beacons from devices within their own beaconing group (as in step 520). In embodiments, this may involve enlarging the beacon period size and/or performing scanning operations on a more frequent basis (increasing scanning). After some time, they may assume all other devices have disappeared, and turn in normal operation mode, i.e., with minimal BP size and normal scanning (as in step 524).    </p>
+    <p id="p-94" num="94">
+      <confidence value="5">[</confidence>
+0081<confidence value="5">]</confidence>
+      Thus, according to aspects of the present invention a device may participate in a wireless communications network that allocates communications resources according to a distributed approach involving beacons from the network's devices. In such networks, the device establishes a peer-to-peer connection with a remote device. This peer-to-peer connection <boundary-data type="header">
+        <confidence value="88">16</confidence>
+      </boundary-data>
+      <boundary-data type="header">Case NC 45264 (4208-4248)</boundary-data>
+      <boundary-data type="header">60735 v<confidence value="4">i</confidence>
+      </boundary-data>
+      <page-break num="18"/>
+      <confidence value="5">i</confidence>
+s based on a reservation having one or more timing parameters. Upon detection of a disappearance of the network devices, the device continues to communicate with the remote device according to the one or more timing parameters of the peer-to-peer connection.    </p>
+    <p id="p-95" num="95">[0082]      This detection of the disappearance may include a failure to receive beacon transmissions from devices in the network. For example, this may involve a failure to receive beacons from all of the devices, or from some (e.g., at least a predetermined number) of the devices in the wireless communications network. The device may send a query to the remote device regarding this disappearance. In response, the remote device may indicate that it has received the beacons (and include information from these beacons). Alternatively, the remote device may indicate that it also detected the disappearance. If so, then (as described above) the devices may search for the other devices by performing, for example, scanning operations.</p>
+    <p id="p-96" num="96">
+      <confidence value="588885">[0083]</confidence>
+      Devices performing in such aspects may be implemented in the manner described above with reference to FIG. 9.    </p>
+    <p id="p-97" num="97">IX.   Conclusion <confidence value="5">[</confidence>
+0084<confidence value="5">]</confidence>
+      While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example only, and not in limitation. Accordingly, it will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the spirit and scope of the invention. Thus, the breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents. For instance, the wireless networks described herein are provided as examples. Thus, other network types are within the scope of the present invention.    </p>
+    <boundary-data type="header">
+      <confidence value="88">17</confidence>
+    </boundary-data>
+    <boundary-data type="header">Case NC 45264 (4208-4248)</boundary-data>
+    <boundary-data type="header">60735 v<confidence value="4">l</confidence>
+    </boundary-data>
+  </description>
+</us-patent-application>
+

prior_art/11183127.xml

@@ -0,0 +1,52 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11183127</doc-number>
+        <date>2011-01-11</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <heading id="h-1">AMENDMENTS TO THE SPECIFICATION</heading>
+    <p id="p-1" num="1">Please amend the paragraph beginning on page <part-num-ref name="paragraph beginning on page">26,</part-num-ref>
+ line <part-num-ref name="paragraph beginning on page 26, line">29,</part-num-ref>
+ as follows:    </p>
+    <p id="p-2" num="2">In FIGURE 15, once a response is received from the enrollment server <part-num-ref name="enrollment server">89</part-num-ref>
+ a block <part-num-ref name="block">265</part-num-ref>
+ examines whether an account was created. If it was<confidence value="5">,</confidence>
+ then a request is sent to the buyer computer <part-num-ref name="buyer computer">50</part-num-ref>
+ to generate a public key encryption pair in block <part-num-ref name="public key encryption pair in block">267</part-num-ref>
+ and to submit the public key to the enrollment server <part-num-ref name="enrollment server">89</part-num-ref>
+ on the commerce gateway <part-num-ref name="commerce gateway">52.</part-num-ref>
+ The enrollment server then signs the public key to create a digital certificate and returns a successful enrollment Web page <part-num-ref name="successful enrollment Web page">620,</part-num-ref>
+ as shown in FIGURE 8E<confidence value="5">,</confidence>
+ which is received in a block <part-num-ref name="block">276</part-num-ref>
+ along with the<confidence value="5884">-and</confidence>
+ the digital certificate in a block <part-num-ref name="block">278.</part-num-ref>
+ If at block <part-num-ref name="block 278. If at block">265</part-num-ref>
+ it was determined that an account was not created<confidence value="5">,</confidence>
+ then an unsuccessful application Web page is displayed (not shown) at a block <part-num-ref name="block">266.</part-num-ref>
+ In the case of applying for a virtual payment account, the result page <part-num-ref name="result page">620</part-num-ref>
+ provides details of the new account for the buyer[[,]] or contains a message informing the buyer that there was an error creating the account. The logic of FIGURE 15 of applying for a virtual payment account then ends in a block <part-num-ref name="block">279</part-num-ref>
+ and processing returns to FIGURE 13.    </p>
+    <p id="p-3" num="3">Please amend the paragraph beginning on page <part-num-ref name="paragraph beginning on page">39,</part-num-ref>
+ line <part-num-ref name="paragraph beginning on page 39, line">7,</part-num-ref>
+ as follows:    </p>
+    <p id="p-4" num="4">In one actual embodiment of the present invention, the commerce gateway <part-num-ref name="commerce gateway">52</part-num-ref>
+ requests report information from the credit processing server <part-num-ref name="credit processing server">53,</part-num-ref>
+ in particular from the financial database <part-num-ref name="financial database">98</part-num-ref>
+ stored on the credit processing server. [[I]] <confidence value="66">It</confidence>
+ will be appreciated by those of ordinary skill in the art[[,]] that a financial database may be used to store information <confidence value="222222222">ferrepert</confidence>
+ for report generation, yet may also store information relevant for other purposes.    </p>
+    <heading id="h-2">LAW OFFICES OF</heading>
+    <heading id="h-3">CHRISTENSEN <confidence value="8">O</confidence>
+'CONNOR JOHNSON <confidence value="222222222222">KINDNESS"LLC</confidence>
+    </heading>
+    <p id="p-5" num="5">1420 Fifth Avenue Suite 2800 Seattle, Washington <part-num-ref name="Seattle, Washington">98101</part-num-ref>
+ -2-                   206.682.8100 ECHG\25426AM7 DOC     </p>
+  </description>
+</us-patent-application>
+

prior_art/11194951.xml

@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11194951</doc-number>
+        <date>2009-02-05</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">
+      <confidence value="8">A</confidence>
+TTORNEY DOCKET NO. ACRY2<confidence value="5">0</confidence>
+ Application No. 11/194,951     </p>
+    <heading id="h-1">IN THE SPECIFICATION</heading>
+    <p id="p-2" num="2">In Paragraph [0060], please make the following change:</p>
+    <p id="p-3" num="3">[0060] The silver nanoparticles of the present invention are formed from weakly water soluble silver compounds formed with a variety of anions both inorganic and organic. However, even highly water-soluble compounds may be used in the practice of the present invention. Silver compounds with imidic organic anions are useful, and though many examples are given with silver saccharinate, the invention comprises any silver compound that will form nanoparticles in the methods disclosed herein. Silver compounds having imidic organic anions are the subject of another co-pending patent, entitled Antimicrobial Devices and Compositions, filed Aug. <part-num-ref name="subject of another co-pending patent, entitled Antimicrobial Devices and Compositions, filed Aug.">1,</part-num-ref>
+ <part-num-ref name="subject of another co-pending patent, entitled Antimicrobial Devices and Compositions, filed Aug. 1,">2005,</part-num-ref>
+ <confidence value="8886656">PCT/US2</confidence>
+005,        PCT/U<confidence value="5">S</confidence>
+2005/027260, incorporated by reference herein in its entirety, and all the compounds taught therein are included in the present invention. Silver compounds with derivatives of saccharin can be suitably employed. Other silver compounds, made by the reaction of soluble silver salts with compounds with active methylene groups e.g. acetylacetonate and derivatives may also be used.    </p>
+    <p id="p-4" num="4">889228 Page 2 of <part-num-ref name="of">12</part-num-ref>
+     </p>
+  </description>
+</us-patent-application>
+

prior_art/11207590.xml

@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11207590</doc-number>
+        <date>2012-01-05</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">U.S. Application No. 11/207,590 Amendment to the Title Please amend the title to read:</p>
+    <p id="p-2" num="2">METHOD AND APPARATUS FOR RESPONDING T<confidence value="562418522">O-EN9-UE-</confidence>
+ REQUEST     </p>
+    <heading id="h-1">FOR INFORMATION-PERSONA<confidence value="66">LI</confidence>
+ZATION    </heading>
+    <p id="p-3" num="3">
+      <confidence value="8">2</confidence>
+     </p>
+  </description>
+</us-patent-application>
+

prior_art/11209469.xml

@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11209469</doc-number>
+        <date>2011-03-03</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">Fig. 4 is a schematic depicting the overall steps in an analytic method in accordance with the invention.</p>
+    <p id="p-2" num="2">Figs. 5A-<confidence value="5">1</confidence>
+ and 5A-2 are graphs showing experimental design converted to continuous tracking reporting of an overall campaign effect in accordance with the invention.    </p>
+    <p id="p-3" num="3">which shows how different combinations of the experimental design cells can be used to derive population based effects, in accordance with the invention.</p>
+    <p id="p-4" num="4">Fig. 5B is a chart depicting return-on-investment analysis of various media in a typical campaign in accordance with the invention.</p>
+    <p id="p-5" num="5">Fig. 6 is a chart depicting the disparity of online and offline verification of ad exposure.</p>
+    <p id="p-6" num="6">Fig. 7 is a graph showing modeling brand lifts from average quintile frequencies.</p>
+    <p id="p-7" num="7">Fig. 8 is a graph showing online decay rates as determined under the inventive method.</p>
+    <p id="p-8" num="8">Fig. 9 is a graph showing disparate media delivery weights to online and offline populations.</p>
+    <p id="p-9" num="9">Fig. 10 is a graph showing that online surveys typically collect the heaviest online users.</p>
+    <p id="p-10" num="10">
+      <confidence value="22">11</confidence>
+ <confidence value="2222222">Wange(s</confidence>
+) a<confidence value="8888">ppli</confidence>
+ed Fig. <confidence value="11">14</confidence>
+ is a flow chart depicting how the inventive method isolates the effects of a <confidence value="8">d</confidence>
+ocument<confidence value="5">,</confidence>
+ magazine buy.    </p>
+    <p id="p-11" num="11">
+      <confidence value="46868">3/201</confidence>
+ 1       Fig. 12 is a flow chart depicting how the inventive method isolates the effects of a newspaper or radio campaign.    </p>
+    <p id="p-12" num="12">Fig. 13 is a flow chart depicting how the inventive method isolates the effects of an out of home campaign.</p>
+    <p id="p-13" num="13">Figs. 14A-B are a flow chart depicting how the inventive method isolates the effects of an online campaign.</p>
+    <p id="p-14" num="14">
+      <confidence value="88">21</confidence>
+     </p>
+  </description>
+</us-patent-application>
+

prior_art/11222602.xml

@@ -0,0 +1,362 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11222602</doc-number>
+        <date>2005-09-09</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <boundary-data type="header">678-1722<confidence value="885">(P1</confidence>
+2468)    </boundary-data>
+    <heading id="h-1">DATA COMMU<confidence value="8">N</confidence>
+ICATION METHOD BASED ON MULTI-RECEIVER    </heading>
+    <heading id="h-2">AGGREGATION</heading>
+    <heading id="h-3">PRIORITY</heading>
+    <p id="p-1" num="1">
+      <boundary-data type="line-number">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+ This application claims priority under 35 U.S.C. <confidence value="66">§1</confidence>
+19 to an application entitled "Data Communication Method Based on Multi-Receiver Aggregation" filed in the United States Patent and Trademark Office on September <part-num-ref name="United States Patent and Trademark Office on September">10,</part-num-ref>
+ <part-num-ref name="United States Patent and Trademark Office on September 10,">2004</part-num-ref>
+ and assigned Serial No. 60/609,150, and to an application entitled "Data Communication Method <boundary-data type="line-number">10 </boundary-data>
+Based On Multi-Receiver Aggregation" filed in the Korean Intellectual Property Office on January <part-num-ref name="Korean Intellectual Property Office on January">4,</part-num-ref>
+ <part-num-ref name="Korean Intellectual Property Office on January 4,">2005</part-num-ref>
+ and assigned Serial No. 2005-576, the contents of both of which are incorporated herein by reference.    </p>
+    <heading id="h-4">BACKGROUND OF THE INVENTION</heading>
+    <p id="p-2" num="2">
+      <boundary-data type="line-number">
+        <confidence value="88">15</confidence>
+      </boundary-data>
+ 1. Field of the Invention The present invention relates to wireless communication systems, and more particularly relates to a data communication method based on packet aggregation that can improve transmission efficiency and minimize power loss in a wireless <boundary-data type="line-number">20 </boundary-data>
+communication system based on multiple carriers.    </p>
+    <p id="p-3" num="3">2. Description of the Related Art Conventional communication systems use a hierarchical frame structure to efficiently transmit high layer data. Specifically, packet aggregation in a media access <part-num-ref name="media access">25</part-num-ref>
+ control (MAC) layer and a physical layer (P<confidence value="5">H</confidence>
+Y) is being studied and developed to <boundary-data type="header">
+        <confidence value="545">-1-</confidence>
+      </boundary-data>
+      <page-break num="2"/>
+      <boundary-data type="header">678-1722 <confidence value="885">(P1</confidence>
+2468)      </boundary-data>
+maximize the efficiency of radio resources of communication systems which conform to wireless communication standards such as the Institute of Electrical &amp; Electronic Engineers (IEEE) 802.11 and 802.16 standards.    </p>
+    <p id="p-4" num="4">
+      <boundary-data type="line-number">5         </boundary-data>
+Aggregation schemes include single receiver aggregation (SRA) for aggregating packets destined for a single station (STA) to transmit the aggregated packets in one physical layer (PHY) protocol data unit (PPDU), and multi-receiver aggregation (MRA) for aggregating packets destined for multiple STA<confidence value="5">s</confidence>
+ to transmit the aggregated packets in one PPDU.    </p>
+    <p id="p-5" num="5">
+      <boundary-data type="line-number">
+        <confidence value="88">10</confidence>
+      </boundary-data>
+ MRA schemes are classified into an MRA scheme based on a single transmission rate for applying the same transmission rate to packets to be transmitted to different destinations using a single PPDU and an MRA scheme based on multiple transmission rates for applying a transmission rate suitable for packets according to <boundary-data type="line-number">15 </boundary-data>
+each destination within the PPDU.    </p>
+    <p id="p-6" num="6">A packet aggregation scheme includes an MRA scheme based on a single transmission rate proposed by the task group N synchronization (TGnSyn<confidence value="5">c</confidence>
+) and a high throughput (HT)-burst scheme proposed by the World Wide Spectrum Efficiency <boundary-data type="line-number">20 </boundary-data>
+(WWiSE) group as two representative schemes proposed by the IEEE 802.11 TGn standard.    </p>
+    <p id="p-7" num="7">FIG. 1 illustrates the format of an MRA proposed by the TGnSync group. The MRA includes an MRA descriptor MAC protocol data unit (MRAD MPDU) <part-num-ref name="MRA descriptor MAC protocol data unit (MRAD MPDU)">101</part-num-ref>
+ <boundary-data type="header">
+        <confidence value="22722">-_2_-</confidence>
+      </boundary-data>
+      <page-break num="3"/>
+      <boundary-data type="header">678-1722 (P12468)</boundary-data>
+including receiver addresses (RAs), and a plurality of STA-by-STA MPDU groups <part-num-ref name="plurality of STA-by-STA MPDU groups">103,</part-num-ref>
+ <part-num-ref name="plurality of STA-by-STA MPDU groups 103,">105,</part-num-ref>
+ and <part-num-ref name="plurality of STA-by-STA MPDU groups 103, 105, and">107</part-num-ref>
+ each including an initiator aggregate control (<confidence value="686">IAC</confidence>
+) MPDU <part-num-ref name="initiator aggregate control (IAC) MPDU">102</part-num-ref>
+ and data MPDUs <part-num-ref name="and data MPDUs">104</part-num-ref>
+ to be transmitted to the RAs. The MPDUs <part-num-ref name="MPDUs">104</part-num-ref>
+ are identified by MPDU delimiters (MDs) <part-num-ref name="are identified by MPDU delimiters (MDs)">109.</part-num-ref>
+    </p>
+    <p id="p-8" num="8">
+      <boundary-data type="line-number">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+ The MRAD MPDU <part-num-ref name="MRAD MPDU">101</part-num-ref>
+ includes the RAs of MPDUs included in the MRA.    </p>
+    <p id="p-9" num="9">Because a reception STA can determine, in advance (i.e., before reception), if a packet to be received is present in a PPDU, the a reduction in reception power can be achieved.</p>
+    <p id="p-10" num="10">However, this MRA scheme is based on the single transmission rate, and must use the <boundary-data type="line-number">10 </boundary-data>
+lowest transmission rate because all reception STAs must be able to receive the MRA, despite that an optimal transmission rate is available according to the distance between reception STA<confidence value="5">s</confidence>
+ or channel characteristics. Therefore, the efficiency of transmission resources is reduced.    </p>
+    <p id="p-11" num="11">
+      <boundary-data type="line-number">15         </boundary-data>
+FIG<confidence value="5">.</confidence>
+ 2 illustrates the format of conventional high throughput HT-burst proposed by the WWiSE group. In FIG 2, the HT<confidence value="5">-</confidence>
+burst includes PPDUs or aggregation PPDUs (A-PPDUs) configured by frames on an STA-by-STA basis. In other words, a first PPDU <part-num-ref name="first PPDU">201</part-num-ref>
+ includes Frame #0 <part-num-ref name="includes Frame #0">210</part-num-ref>
+ and Frame #1 <part-num-ref name="and Frame #1">211</part-num-ref>
+ whose destinations are STA #1), a second PPDU <part-num-ref name="second PPDU">202</part-num-ref>
+ includes Frame #2 <part-num-ref name="includes Frame #2">212,</part-num-ref>
+ a third PPDU <part-num-ref name="third PPDU">203</part-num-ref>
+ includes Frame #3 <boundary-data type="line-number">20 </boundary-data>
+      <part-num-ref name="includes Frame #3">213</part-num-ref>
+ and a fourth PPDU <part-num-ref name="fourth PPDU">204</part-num-ref>
+ includes Frame #4 <part-num-ref name="includes Frame #4">214</part-num-ref>
+ and Frame #5 <part-num-ref name="and Frame #5">215.</part-num-ref>
+    </p>
+    <p id="p-12" num="12">When successive frames are transmitted at the same power in the conventional HT-burst scheme, the next frame is transmitted on the basis of zero interframe space (<confidence value="2222">ZIFS</confidence>
+). When successive frames are transmitted at different power in the HT<confidence value="5">-</confidence>
+burst <boundary-data type="header">
+        <confidence value="22722">-_3_.</confidence>
+      </boundary-data>
+      <page-break num="4"/>
+      <boundary-data type="header">678-1722 (P12468)</boundary-data>
+scheme, the next frame is transmitted on the basis of reduced interframe space (<confidence value="2222">RIFS</confidence>
+).    </p>
+    <p id="p-13" num="13">Here, the transmission power variation indicates the transmission rate variation. The conventional HT<confidence value="5">-</confidence>
+burst scheme does not take into account reception power reduction and has only an STA-by-STA aggregation effect. As an A-PPDU transmission interval is <boundary-data type="line-number">5 </boundary-data>
+reduced, a small benefit may be expected. However, a multi-STA aggregation effect is, for the most part, insignificant, in the conventional HT<confidence value="5">-</confidence>
+burst scheme.    </p>
+    <heading id="h-5">SUMMARY OF THE INVENTION</heading>
+    <p id="p-14" num="14">
+      <boundary-data type="line-number">10         </boundary-data>
+Accordingly, the present invention has been designed to solve the above and other problems occurring in the prior art. Therefore, it is an aspect of the present invention to provide a data communication method based on packet aggregation that can efficiently manage resources by determining transmission rates for reception stations (STAs) on the basis of channel state information received therefrom, <boundary-data type="line-number">15 </boundary-data>
+aggregating packets with the same transmission rate to be transmitted to the reception STAs to form a packet group, and transmitting packet groups with different transmission rates using a single multi-rate aggregation (MRA) burst.    </p>
+    <p id="p-15" num="15">It is another aspect of the present invention to provide a data communication <boundary-data type="line-number">20 </boundary-data>
+method based on packet aggregation that can minimize power consumption required for reception as one or more reception stations (STAs) initiate a reception only mode in a packet group interval including the STA<confidence value="5">s</confidence>
+ packets to be received using control information included in a multi-rate aggregation (MRA) burst.    </p>
+    <boundary-data type="header">
+      <confidence value="22722">-_4_-</confidence>
+    </boundary-data>
+    <boundary-data type="header">678-1722 (P12468)</boundary-data>
+    <p id="p-16" num="16">
+      <page-break num="5"/>
+The above and other aspects of the present invention can be achieved by a communication method in a wireless communication system having transmitters for determining a transmission rate for an associated receiver according to channel state information fed back from associated receivers, and transmitting packets at the <boundary-data type="line-number">5 </boundary-data>
+determined transmission rate, including grouping packets to be transmitted to the receivers according to transmission rates and generating frames with an identical transmission rate in a transmitter aggregating frames with different transmission rates into a single transmission burst and transmitting the single transmission burst, the transmission burst including a control information frame.    </p>
+    <p id="p-17" num="17">
+      <boundary-data type="line-number">
+        <confidence value="88">10</confidence>
+      </boundary-data>
+ The above and other aspects of the present invention can also be achieved by a data transmission method in a wireless communication system having transmitters for determining a transmission rate for an associated receiver according to channel state information fed-back from associated receivers, and transmitting packets at the <boundary-data type="line-number">15 </boundary-data>
+determined transmission rate, including grouping media access control (MAC) protocol data units (MPDUs) to be transmitted to the receivers according to transmission rates and generating aggregation physical layer (PHY) protocol data units (A-PPDUs) configured by MPDUs with an identical transmission rate and aggregating A-PPDUs with different transmission rates into a single multi-rate aggregation (MRA) burst and <boundary-data type="line-number">20 </boundary-data>
+transmitting the MRA burst.    </p>
+    <p id="p-18" num="18">The above and other aspects of the present invention can also be achieved by a data reception method in a wireless communication system having transmitters for determining a transmission rate for an associated receiver according to channel state <boundary-data type="header">
+        <confidence value="22722">-_5_-</confidence>
+      </boundary-data>
+      <page-break num="6"/>
+      <boundary-data type="header">678-1722 (P12468)</boundary-data>
+information fed back from associated receivers, and transmitting packets at the determined transmission rate, including when a multi-rate aggregation (<confidence value="5">M</confidence>
+RA) burst descriptor (BD) physical layer (PHY) protocol data unit (PPDU) is received from a transmitter, determining if a receiver's own address is present in the MRA BD PPDU; if <boundary-data type="line-number">5 </boundary-data>
+the receiver's own address is present, referring to a receiver address (RA) field of the MRA BD PPDU and identifying an aggregation PPDU (A-PPDU) to be received from transmitted A-PPDUs subsequent to the MRA BD PPDU; when the A-PPDU begins to be received, determining if the A-PPDU is an A-PPDU transmitted for the receiver using a preamble and a header of the A-PPDU; if the A-PPDU is an A-PPDU <boundary-data type="line-number">10 </boundary-data>
+transmitted for the receiver, receiving a total of the A-PPDU; and extracting media access control (MAC) protocol data units (MPDUs) transmitted for the receiver from the received A-PPDU.    </p>
+    <p id="p-19" num="19">The data reception method further including reading a header of the A-PPDU <boundary-data type="line-number">15 </boundary-data>
+and entering sleep mode until a next A-PPDU begins to be received, if the A-PPDU is not an A-PPDU transmitted for the receiver..    </p>
+    <p id="p-20" num="20">The data reception method further including referring to an M<confidence value="5">R</confidence>
+A burst duration field of the M<confidence value="5">R</confidence>
+A BD PPDU, when the receiver's own address is not present in <boundary-data type="line-number">20 </boundary-data>
+the MRA BD PPDU, terminating reception mode in a duration of the M<confidence value="5">R</confidence>
+A burst, and entering an off mode.    </p>
+    <heading id="h-6">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
+    <boundary-data type="header">
+      <confidence value="22722">-_6_-</confidence>
+    </boundary-data>
+    <boundary-data type="header">678-1722 <confidence value="885">(P1</confidence>
+2468)    </boundary-data>
+    <p id="p-21" num="21">
+      <page-break num="7"/>
+The above and other aspects and advantages of the present invention will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings, in which:    </p>
+    <p id="p-22" num="22">FIG. 1 is a diagram illustrating a conventional packet aggregation method;</p>
+    <p id="p-23" num="23">
+      <boundary-data type="line-number">5         </boundary-data>
+FIG. 2 is a diagram illustrating another conventional packet aggregation method;    </p>
+    <p id="p-24" num="24">FIG. 3 is a diagram illustrating an example of a packet aggregation communication method according to an embodiment of the present invention;</p>
+    <p id="p-25" num="25">FIG. 4 is a diagram illustrating a structure of a multi-rate aggregation (MRA) <boundary-data type="line-number">10 </boundary-data>
+burst descriptor (BD) MAC protocol data unit (MPDU) of FIG. 3; and FIG. 5 is a diagram illustrating the effect of reducing reception power of a station (STA) in a packet aggregation communication method according to an embodiment of the present invention.    </p>
+    <heading id="h-7">DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS</heading>
+    <p id="p-26" num="26">
+      <boundary-data type="line-number">15      </boundary-data>
+A packet aggregation method according to an embodiment of the present invention will now be described in detail with reference to the accompanying drawings.    </p>
+    <p id="p-27" num="27">
+      <boundary-data type="line-number">20         </boundary-data>
+FIG. 3 is a diagram illustrating an example of a packet aggregation communication method in accordance with an embodiment of the present invention.    </p>
+    <p id="p-28" num="28">A multi-rate aggregation (MRA) burst in accordance with an embodiment of the present invention includes an MRA burst descriptor (BD) PHY protocol data unit <boundary-data type="header">
+        <confidence value="585">-7-</confidence>
+      </boundary-data>
+      <page-break num="8"/>
+      <boundary-data type="header">678-1722 <confidence value="885">(P1</confidence>
+2468<confidence value="5">)</confidence>
+      </boundary-data>
+(PPDU) <part-num-ref name="MRA burst descriptor (BD) PHY protocol data unit (PPDU)">310</part-num-ref>
+ and three subsequent aggregation PPDUs (A-PPDUs) <part-num-ref name="and three subsequent aggregation PPDUs (A-PPDUs)">320,</part-num-ref>
+ <part-num-ref name="and three subsequent aggregation PPDUs (A-PPDUs) 320,">330,</part-num-ref>
+ and <part-num-ref name="and three subsequent aggregation PPDUs (A-PPDUs) 320, 330, and">340.</part-num-ref>
+    </p>
+    <p id="p-29" num="29">The MRA BD PPDU 310 is configured by a preamble <part-num-ref name="preamble">311,</part-num-ref>
+ a PHY header <part-num-ref name="PHY header">313,</part-num-ref>
+ and an MRA BD MAC protocol data unit (MPDU) <part-num-ref name="MRA BD MAC protocol data unit (MPDU)">315,</part-num-ref>
+ and is broadcast at a basic transmission rate.    </p>
+    <p id="p-30" num="30">
+      <boundary-data type="line-number">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+ Before an MRA BD PPDU is transmitted, a transmission station (STA) groups reception STA<confidence value="5">s</confidence>
+ according to transmission rates according to a channel state of each reception STA. Then, the transmission STA aggregates packets to be sent to addresses of reception STA<confidence value="5">s</confidence>
+ belonging to each group into an MRA PPDU based on a single <boundary-data type="line-number">10 </boundary-data>
+transmission rate, and configures an A-PPDU.    </p>
+    <p id="p-31" num="31">FIG. 3 illustrates a case where transmission rates for STA<confidence value="5">s</confidence>
+ with receiver addresses RA<confidence value="4">l</confidence>
+, RA2 and RA3 are set to <part-num-ref name="case where transmission rates for STAs with receiver addresses RAl, RA2 and RA3 are set to">1,</part-num-ref>
+ transmission rates for STAs with receiver addresses RA4, RA<confidence value="5">5</confidence>
+, and RA6 are set to <part-num-ref name="case where transmission rates for STAs with receiver addresses RAl, RA2 and RA3 are set to 1, transmission rates for STAs with receiver addresses RA4, RA5, and RA6 are set to">2,</part-num-ref>
+ and transmission rates for STA<confidence value="5">s</confidence>
+ with <boundary-data type="line-number">15 </boundary-data>
+receiver addresses RA7 and RA8 are set to <part-num-ref name="case where transmission rates for STAs with receiver addresses RAl, RA2 and RA3 are set to 1, transmission rates for STAs with receiver addresses RA4, RA5, and RA6 are set to 2, and transmission rates for STAs with receiver addresses RA7 and RA8 are set to">3,</part-num-ref>
+ according to channel state information fed back from the reception STAs.    </p>
+    <p id="p-32" num="32">As illustrated in FIG. 3, an MPDU group <part-num-ref name="MPDU group">321</part-num-ref>
+ to be sent to RA<confidence value="4">1</confidence>
+, an MPDU group <part-num-ref name="MPDU group">322</part-num-ref>
+ to be sent to RA2, and an MPDU group <part-num-ref name="MPDU group">323</part-num-ref>
+ to be sent to RA3 associated <boundary-data type="line-number">20 </boundary-data>
+with the transmission rate of <part-num-ref name="transmission rate of">
+        <confidence value="5">1</confidence>
+      </part-num-ref>
+ are aggregated into a first A-PPDU <part-num-ref name="first A-PPDU">320.</part-num-ref>
+ Similarly, MPDU groups to be sent to RA4, RA<confidence value="5">5</confidence>
+, and RA6 associated with the transmission rate of <part-num-ref name="transmission rate of">2</part-num-ref>
+ are aggregated into a second A-PPDU <part-num-ref name="second A-PPDU">330.</part-num-ref>
+ Similarly, MPDU groups to be sent to RA7 and RA8 associated with the transmission rate of <part-num-ref name="transmission rate of">3</part-num-ref>
+ are aggregated into a third A- PPDU <part-num-ref name="third A- PPDU">340.</part-num-ref>
+ Each A-PPDU is generated by inserting a preamble <part-num-ref name="preamble">324</part-num-ref>
+ and a physical layer <boundary-data type="header">
+        <confidence value="22722">._8_.</confidence>
+      </boundary-data>
+      <page-break num="9"/>
+      <boundary-data type="header">678-1722 (P12468)</boundary-data>
+(PHY) header <part-num-ref name="physical layer (PHY) header">325</part-num-ref>
+ before an MPDU group.    </p>
+    <p id="p-33" num="33">Each MPDU group includes a control MPDU <part-num-ref name="control MPDU">326</part-num-ref>
+ and data MPDUs <part-num-ref name="and data MPDUs">328.</part-num-ref>
+ The MPDUs are delimited by MPDU delimiters <part-num-ref name="MPDUs are delimited by MPDU delimiters">329.</part-num-ref>
+ A time interval between A-PPDUs uses <boundary-data type="line-number">5 </boundary-data>
+short interframe space (SIFS) for high-priority media access.    </p>
+    <p id="p-34" num="34">Three A-PPDUs and three MPDU groups have been illustrated in this embodiment. However, the number of A-PPDUs or MPDU groups configuring the MRA burst is not limited to three, but can be changed according to a communication <boundary-data type="line-number">10 </boundary-data>
+environment.    </p>
+    <p id="p-35" num="35">FIG. 4 is a diagram illustrating a structure of the MRA BD MPDU of FIG. 3.</p>
+    <p id="p-36" num="36">The MRA BD MPDU 315 includes a 2-octet frame control field <part-num-ref name="2-octet frame control field">410</part-num-ref>
+ indicating a frame type, a 2-octet MRA burst duration field <part-num-ref name="2-octet MRA burst duration field">420,</part-num-ref>
+ a 6-octet receiver address (RA) field <part-num-ref name="6-octet receiver address (RA) field">430,</part-num-ref>
+ <boundary-data type="line-number">15 </boundary-data>
+a 6-octet transmitter address (TA) field <part-num-ref name="6-octet transmitter address (TA) field">440,</part-num-ref>
+ a 1-octet "number of association ID (AID) (n)" field <part-num-ref name="1-octet &quot;number of association ID (AID) (n)&quot; field">450,</part-num-ref>
+ a 2n-octet receiver information field <part-num-ref name="2n-octet receiver information field">460</part-num-ref>
+ in the MRA burst, and a 4-octet frame check sequence (FCS) field <part-num-ref name="4-octet frame check sequence (FCS) field">470.</part-num-ref>
+    </p>
+    <p id="p-37" num="37">A value of the MRA burst duration field <part-num-ref name="MRA burst duration field">420</part-num-ref>
+ can be used to prevent contention <boundary-data type="line-number">20 </boundary-data>
+for time-consuming media access of legacy STA<confidence value="5">s</confidence>
+. The receiver information field <part-num-ref name="receiver information field">460</part-num-ref>
+ in the MRA burst includes a plurality of 2-octet AID elements <part-num-ref name="plurality of 2-octet AID elements">461.</part-num-ref>
+ Each <confidence value="66">AI</confidence>
+D element <part-num-ref name="plurality of 2-octet AID elements 461. Each AID element">461</part-num-ref>
+ includes a 2-bit delimiter <part-num-ref name="2-bit delimiter">463</part-num-ref>
+ and an AID <part-num-ref name="AID">465.</part-num-ref>
+ The delimiter <part-num-ref name="delimiter">463</part-num-ref>
+ can have a value of <confidence value="8886">"11"</confidence>
+ or "00<confidence value="5">"</confidence>
+ (binary). If the delimiter <part-num-ref name="delimiter">463</part-num-ref>
+ has a value of <confidence value="8888">"11"</confidence>
+ delimiter <part-num-ref name="value of &quot;11&quot; delimiter">463</part-num-ref>
+ indicates that an AID is included in the next A-PPDU, and the value "00<confidence value="5">"</confidence>
+ of the delimiter <part-num-ref name="delimiter">463</part-num-ref>
+ <boundary-data type="header">
+        <confidence value="272">-9-</confidence>
+      </boundary-data>
+      <page-break num="10"/>
+      <boundary-data type="header">678-1722 <confidence value="885">(P1</confidence>
+2468<confidence value="5">)</confidence>
+      </boundary-data>
+indicates that an AID included in the A-PPDU is the same as an AID of an immediately proceeding PPDU.    </p>
+    <p id="p-38" num="38">A reception method of a reception STA using the above-described MRA burst <boundary-data type="line-number">5 </boundary-data>
+structure will be described with reference to the accompanying drawings.    </p>
+    <p id="p-39" num="39">First, when an STA receives an MRA BD PPDU <part-num-ref name="MRA BD PPDU">310,</part-num-ref>
+ it determines if an AID element including the STA's unique AID is present among AID elements enumerated in the receiver information field <part-num-ref name="receiver information field">460</part-num-ref>
+ within the MRA BD MPDU <part-num-ref name="MRA BD MPDU">315</part-num-ref>
+ of the MRA BD <boundary-data type="line-number">10 </boundary-data>
+PPDU <part-num-ref name="MRA BD PPDU">310.</part-num-ref>
+    </p>
+    <p id="p-40" num="40">If it is determined that the STA's unique AID is included the STA determines which of the A-PPDUs <part-num-ref name="A-PPDUs">320,</part-num-ref>
+ <part-num-ref name="A-PPDUs 320,">330</part-num-ref>
+ and <part-num-ref name="and">340,</part-num-ref>
+ which are transmitted subsequent to the MRA BD PPDU 310), includes the STA's MPDUs to be received, using values of delimiters <boundary-data type="line-number">15 </boundary-data>
+      <part-num-ref name="STA's MPDUs to be received, using values of delimiters">463</part-num-ref>
+ of AID elements <part-num-ref name="of AID elements">461.</part-num-ref>
+    </p>
+    <p id="p-41" num="41">Continuously, when A-PPDUs are received, the STA refers to an A-PPDU preamble <part-num-ref name="A-PPDU preamble">324</part-num-ref>
+ and a PHY header <part-num-ref name="PHY header">325,</part-num-ref>
+ and determines if a received A-PPDU includes an MPDU transmitted for the STA. If the received A-PPDU includes an MPDU transmitted <boundary-data type="line-number">20 </boundary-data>
+for the STA, the STA receives an associated A-PPDU and detects MPDUs.    </p>
+    <p id="p-42" num="42">However, if the A-PPDU does not include an MPDU transmitted for the STA, the STA reads a PHY header and enters sleep mode until the start of the next A-PPDU.</p>
+    <boundary-data type="header">
+      <confidence value="6">-</confidence>
+ <confidence value="852">10_</confidence>
+    </boundary-data>
+    <boundary-data type="header">678-1722(P12468)</boundary-data>
+    <p id="p-43" num="43">
+      <page-break num="11"/>
+On the other hand, the receiving STA turns off reception power during a time interval indicated by the MRA burst duration field <part-num-ref name="MRA burst duration field">420</part-num-ref>
+ if the STA's AID is not included in the MRA BD PPDU <part-num-ref name="MRA BD PPDU">310.</part-num-ref>
+    </p>
+    <p id="p-44" num="44">
+      <boundary-data type="line-number">5         </boundary-data>
+In case of a legacy STA that cannot detect an MRA burst, reception power can be turned off using a long network allocation vector (NAV) function (or a function for limiting transmission used in the IEEE 802.11 standard) according to a value of the MRA burst duration field <part-num-ref name="MRA burst duration field">420.</part-num-ref>
+    </p>
+    <p id="p-45" num="45">
+      <boundary-data type="line-number">10         </boundary-data>
+FIG. 5 illustrates the effect of reducing reception power of an STA in a packet aggregation communication method in accordance with an embodiment of the present invention.    </p>
+    <p id="p-46" num="46">Referring to FIGS. 3 to <part-num-ref name="to">5,</part-num-ref>
+ for example, an STA with a receiver address of RA2 <boundary-data type="line-number">15 </boundary-data>
+determines that its own MPDUs to be received are included in the first A-PPDU <part-num-ref name="first A-PPDU">320</part-num-ref>
+ using delimiter values of AID elements included in the MRA BD PPDU <part-num-ref name="MRA BD PPDU">310,</part-num-ref>
+ receives the first A-PPDU <part-num-ref name="first A-PPDU">320,</part-num-ref>
+ detects its own MPDUs, and thereafter enters a sleep mode.    </p>
+    <p id="p-47" num="47">On the other hand, an STA with a receiver address of RA8 determines that its <boundary-data type="line-number">20 </boundary-data>
+own MPDUs to be received are included in the third A-PPDU <part-num-ref name="third A-PPDU">340</part-num-ref>
+ using delimiter values of AID elements included in the MRA BD PPDU <part-num-ref name="MRA BD PPDU">310.</part-num-ref>
+ At the start of reception of the first A-PPDU <part-num-ref name="first A-PPDU">320,</part-num-ref>
+ the STA refers to a preamble and a PHY header of the first A- PPDU, determines that the first A-PPDU is not an A-PPDU transmitted for the STA, and enters the sleep mode until the next A-PPDU arrives. When the first A-PPDU <part-num-ref name="first A-PPDU">320</part-num-ref>
+ ends, <confidence value="6">-</confidence>
+ <confidence value="41">ll</confidence>
+ <page-break num="12"/>
+      <boundary-data type="header">678-1722 (P12468)</boundary-data>
+the STA enters reception mode and begins to receive a second A-PPDU <part-num-ref name="second A-PPDU">330.</part-num-ref>
+ At the start of reception of the second A-PPDU <part-num-ref name="second A-PPDU">330,</part-num-ref>
+ the STA refers to a preamble and a PHY header of the second A-PPDU <part-num-ref name="second A-PPDU">330,</part-num-ref>
+ determines that the second A-PPDU <part-num-ref name="second A-PPDU">330</part-num-ref>
+ is not an A-PPDU transmitted for the STA, and enters the sleep mode until the next A-PPDU arrives. At <boundary-data type="line-number">5 </boundary-data>
+the start of reception of the third A-PPDU <part-num-ref name="third A-PPDU">340,</part-num-ref>
+ the STA refers to a preamble and a PHY header of the third A-PPDU <part-num-ref name="third A-PPDU">340,</part-num-ref>
+ determines that the third A-PPDU <part-num-ref name="third A-PPDU">340</part-num-ref>
+ is an A-PPDU transmitted for the STA, and receives the third A-PPDU <part-num-ref name="third A-PPDU">340</part-num-ref>
+ in its entirety.    </p>
+    <p id="p-48" num="48">Upon receiving an MRA BD PPDU (in its entirety), a third-party high <boundary-data type="line-number">10 </boundary-data>
+throughput (HT) STA with a receiver address of RA<confidence value="56">10</confidence>
+ enters the sleep mode. As soon as an interval of an MRA BD PPDU ends, a legacy STA with a receiver address of <confidence value="88">RA</confidence>
+13 performs a long NAV function.    </p>
+    <p id="p-49" num="49">The STA with the receiver address of RA2 and the STA with the receiver <boundary-data type="line-number">15 </boundary-data>
+address of RA8 enter the reception mode during a time interval in which they receive respective A-PPDUs transmitted to them, and enters the sleep mode during other A- PPDU intervals, such that the consumption of reception power is minimized.    </p>
+    <p id="p-50" num="50">In accordance with the present invention as described above, a data <boundary-data type="line-number">20 </boundary-data>
+communication method based on packet aggregation can efficiently manage resources by determining transmission rates for reception stations (STAs) on the basis of feedback channel state information in a transmission STA, aggregating packets with the same transmission rate to be transmitted to the reception STAs to form a packet group, and transmitting packet groups with different transmission rates using a single multi-rate <boundary-data type="header">
+        <confidence value="6">-</confidence>
+ <confidence value="882">12-</confidence>
+      </boundary-data>
+      <page-break num="13"/>
+      <boundary-data type="header">678-1722 (P12468)</boundary-data>
+aggregation (MRA) burst.    </p>
+    <p id="p-51" num="51">In accordance with the present invention, the data communication method based on packet aggregation can minimize the consumption of reception power as <boundary-data type="line-number">5 </boundary-data>
+reception STA<confidence value="5">s</confidence>
+ enter a reception mode only during a packet group interval including their own packets to be received, using control information included in a multi-rate aggregation (MRA) burst.    </p>
+    <p id="p-52" num="52">Although preferred embodiments of the present invention have been disclosed <boundary-data type="line-number">10 </boundary-data>
+for illustrative purposes, those skilled in the art will appreciate that various modifications, additions, and substitutions are possible, without departing from the scope of the present invention. Therefore, the present invention is not limited to the above-described embodiments, but is defined by the following claims, along with their full scope of equivalents.    </p>
+    <p id="p-53" num="53">
+      <confidence value="88">15</confidence>
+ <boundary-data type="header">
+        <confidence value="2">.</confidence>
+ <confidence value="882">13.</confidence>
+      </boundary-data>
+    </p>
+  </description>
+</us-patent-application>
+

prior_art/11226635.xml

@@ -0,0 +1,534 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11226635</doc-number>
+        <date>2005-09-14</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <heading id="h-1">MULTI-COMPONENT, WATERBORNE COATING</heading>
+    <heading id="h-2">COMPOSITIONS, RELATED COATINGS AND METHODS</heading>
+    <heading id="h-3">FIELD OF THE INVENTION</heading>
+    <p id="p-1" num="1">[0001]      The present invention relates to multi-component waterborne coating compositions that comprise a first component and a second component which are mixed together prior to application of the composition to a substrate. The first component comprises an aqueous dispersion of (i) a polycarbonate-polyurethane polymer, and (ii) an acrylic polyol having a number average molecular weight of no more than 5,000. The second component comprises a material having functional groups reactive with the functional groups of the acrylic <confidence value="222222">polyol</confidence>
+ and/or the polycarbonate-polyurethane polymer.    </p>
+    <p id="p-2" num="2">The present invention is also directed to coatings formed from such compositions and substrates at least partially coated with such compositions.</p>
+    <heading id="h-4">BACKGROUND INFORMATION</heading>
+    <p id="p-3" num="3">[0002]      Reducing the environmental impact of coating compositions, such as that associated with emissions into the air of volatile organics during their application has been an area of ongoing investigation and development in recent years. Accordingly, interest has increased in coating compositions containing low levels of volatile organic compounds ("low VOC coating compositions").</p>
+    <p id="p-4" num="4">
+      <confidence value="5">[</confidence>
+0003]      In certain markets, such as the consumer electronics market, it is desirable to apply protective and decorative coatings to plastic substrates, such as substrates constructed of acrylonitrile butadiene styrene and/or polycarbonate, among other materials. One problem that has been associated with the application of such coatings to these types of substrates, however, is achieving adequate adhesion of the coating to the substrate. In some cases, adequate adhesion is achieved by using <confidence value="222222222222">solventborne</confidence>
+ coatings that utilize solvents that chemically "etch" the substrate, thereby causing physical entanglement of the polymer chains of the substrate with the polymer chains in the coating. Such coating compositions, however, are incompatible with the desire to achieve environmentally friendly, low VOC coating compositions.    </p>
+    <boundary-data type="header">
+      <confidence value="6">1</confidence>
+    </boundary-data>
+    <p id="p-5" num="5">
+      <page-break num="2"/>
+      <confidence value="5">[</confidence>
+0004<confidence value="5">]</confidence>
+       Other properties desirable in coating compositions suitable for application to plastic substrates are humidity resistance and hardness. Humidity resistance is a measure of the ability of a coating to remain intact and unblemished after exposure to water, while harder coatings are more resistant to scratching and marring. It would be desirable to provide waterborne coating compositions suitable for application to plastic substrates, which can exhibit good adhesion properties to such substrates, while having sufficient humidity resistance and hardness properties.    </p>
+    <heading id="h-5">SUMMARY OF THE INVENTION</heading>
+    <p id="p-6" num="6">[0005]      In certain respects, the present invention is directed to multi-component waterborne coating compositions. These coating compositions comprise (a) a first component comprising an aqueous dispersion comprising (i) a polycarbonate- polyurethane polymer, and (ii) an acrylic polyol having a number average molecular weight of no more than 5,000; and (b) a second component comprising a material having functional groups reactive with the functional groups of the acrylic polyol and/or the polycarbonate-polyurethane polymer.</p>
+    <p id="p-7" num="7">[0006]       The present invention is also directed to substrates at least partially coated with a coating deposited from such a composition, methods for at least partially coating a substrate with such a composition, and substrates at least partially coated with a multi- component composite coating comprising at least one coating layer deposited from such a composition.</p>
+    <p id="p-8" num="8">[0007<confidence value="5">]</confidence>
+      In other respects, the present invention is directed to multi-component waterborne coating compositions comprising an aqueous dispersion of a polycarbonate- polyurethane polymer, wherein when the composition is deposited onto at least a portion of a plastic substrate and cured, the composition produces a coating that adheres to the substrate at least as well as a conventional multi-component <confidence value="22222222222">solventbome</confidence>
+ polyurethane containing coating composition adheres to the same substrate when applied under the same conditions.    </p>
+    <boundary-data type="header">
+      <confidence value="8">2</confidence>
+    </boundary-data>
+    <heading id="h-6">DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION</heading>
+    <p id="p-9" num="9">
+      <page-break num="3"/>
+      <confidence value="5">[</confidence>
+0008<confidence value="5">]</confidence>
+       For purposes of the following detailed description, it is to be understood that the invention may assume various alternative variations and step sequences, except where expressly specified to the contrary. Moreover, other than in any operating examples, or where otherwise indicated, all numbers expressing, for example, quantities of ingredients used in the specification and claims are to be understood as being modified in all instances by the term "about". Accordingly, unless indicated to the contrary, the numerical parameters set forth in the specification, including the claims, are approximations that may vary depending upon the desired properties to be obtained by the present invention. At the very least, and not as an attempt to limit the application of the doctrine of equivalents to the scope of the claims, each numerical parameter should at least be construed in light of the number of reported significant digits and by applying ordinary rounding techniques.    </p>
+    <p id="p-10" num="10">
+      <confidence value="5">[</confidence>
+0009<confidence value="5">]</confidence>
+       Notwithstanding that the numerical ranges and parameters setting forth the broad scope of the invention are approximations, the numerical values set forth in the specific examples are reported as precisely as possible. Any numerical value, however, inherently contains certain errors necessarily resulting from the standard variation found in their respective testing measurements.    </p>
+    <p id="p-11" num="11">
+      <confidence value="5">[</confidence>
+0010<confidence value="5">]</confidence>
+       Also, it should be understood that any numerical range recited herein is intended to include all sub-ranges subsumed therein. For example, a range of "1 to 10" is intended to include all sub-ranges between (and including) the recited minimum value of <part-num-ref name="recited minimum value of">1</part-num-ref>
+ and the recited maximum value of <part-num-ref name="recited maximum value of">10,</part-num-ref>
+ that is, having a minimum value equal to or greater than <part-num-ref name="minimum value equal to or greater than">1</part-num-ref>
+ and a maximum value of equal to or less than <part-num-ref name="maximum value of equal to or less than">10.</part-num-ref>
+    </p>
+    <p id="p-12" num="12">
+      <confidence value="5">[</confidence>
+0011<confidence value="5">]</confidence>
+      In this application, the use of the singular includes the plural and plural encompasses singular, unless specifically stated otherwise. For example, and without limitation, this application refers to coating compositions that comprise "an acrylic polyol". Such references to "an acrylic polyol" is meant to encompass coating compositions comprising one acrylic polyol as well as coating compositions that comprise more than one acrylic polyol. In addition, in this application, the use of "or" <boundary-data type="header">
+        <confidence value="8">3</confidence>
+      </boundary-data>
+      <page-break num="4"/>
+means "and/or" unless specifically stated otherwise, even though "and/or" may be explicitly used in certain instances.    </p>
+    <p id="p-13" num="13">[0012]       As previously indicated, certain embodiments of the present invention are directed to "multi-component" coating compositions. As used herein, the term "multi- component" means that the coating composition includes two or more components stored or packaged separately and then mixed together prior to application to a substrate. In certain embodiments of the present invention, the multi-component coating composition consists of two components.</p>
+    <p id="p-14" num="14">[0013]       As previously indicated, certain embodiments of the present invention are directed to "waterborne" coating compositions. As used herein, the term "waterborne<confidence value="8">"</confidence>
+ means that the solvent or carrier fluid for the coating composition primarily or principally comprises water. For example, in certain embodiments, the carrier fluid is at least <part-num-ref name="carrier fluid is at least">80</part-num-ref>
+ weight percent water.    </p>
+    <p id="p-15" num="15">[0014]       Certain embodiments of the present invention are directed to coating compositions that are "low VOC" coating compositions. As used herein, the term "low VOC composition" means that the composition contains no more than three <part-num-ref name="composition contains no more than three">(3)</part-num-ref>
+ pounds of volatile organic compounds per gallon of the composition. In certain embodiments, the coating compositions of the present invention comprise no more than one <part-num-ref name="present invention comprise no more than one">(1)</part-num-ref>
+ pound of volatile organic compound per gallon of the coating composition. As used herein, the term "volatile organic compound" refers to compounds that have at least one carbon atom and which are released from the composition during drying and/or curing thereof.    </p>
+    <p id="p-16" num="16">Examples of "volatile organic compounds" include, but are not limited to, alcohols, benzenes, toluenes, chloroforms, and cyclohexanes.</p>
+    <p id="p-17" num="17">[0015]       As previously indicated, certain embodiments of the coating compositions of the present invention comprise an aqueous dispersion comprising a polycarbonate- polyurethane polymer, in some cases an aliphatic polycarbonate-polyurethane polymer.</p>
+    <p id="p-18" num="18">As used herein, the term "aqueous dispersion" refers to a system wherein an organic component is in the dispersed phase as particles distributed throughout the continuous phase, which includes water. As used herein, the term "organic component" is meant to encompass all of the organic species present in the aqueous dispersion, including any <boundary-data type="header">
+        <confidence value="8">4</confidence>
+      </boundary-data>
+      <page-break num="5"/>
+polymers, as well as any organic solvents. As used herein, the term "polycarbonate- polyurethane polymer" is meant to include polymers that include repeating urethane     </p>
+    <heading id="h-7">
+      <confidence value="4">O</confidence>
+    </heading>
+    <heading id="h-8">
+      <confidence value="88">HN</confidence>
+    <confidence value="2">O</confidence>
+    </heading>
+    <p id="p-19" num="19">groups,            , and repeating carbonate groups,  <confidence value="26662">0-C-0</confidence>
+  <confidence value="5">,</confidence>
+ in the polymeric backbone.    </p>
+    <p id="p-20" num="20">
+      <confidence value="5">[</confidence>
+0016]      As will be appreciated by those skilled in the art, such polymers may be prepared from the reaction of a hydroxy functional carbonate containing material with a polyisocyanate. Suitable hydroxy functional carbonate containing materials include the reaction product of carbonic acid, or a derivative thereof, with a diol. Examples of suitable diols include, but are not limited to, ethylene glycol, propane-1,2- and 1,3-diol, butane-1,4- and -1,3-diol, hexane-1,6-diol, octane-<confidence value="5">1</confidence>
+,8-diol, neopentyl glycol, 1,4-bis- hydroxymethyl cyclohexane, 2-methyl-propane-<confidence value="4">1</confidence>
+,3-diol, 2,2,4-trimethylpentane-1,3<confidence value="8">-</confidence>
+ diol, diethylene glycol, tri- and tetraethylene glycol, dipropylene glycol, polypropylene glycols, dibutylene glycol, polybutylene glycols, Bisphenol A and tetrabromo Bisphenol A. In certain embodiments, the diol component contains from <part-num-ref name="diol component contains from">40</part-num-ref>
+ to 100% by weight of a hexane diol, such as hexane-1,6-diol, <confidence value="222222">and/or</confidence>
+ hexane diol derivatives containing ether or ester groups in addition to terminal hydroxyl groups, e.g., the products obtained by the reaction of <part-num-ref name="reaction of">1</part-num-ref>
+ mole of hexane diol with <confidence value="2">&gt;</confidence>
+1 mole of caprolactone.    </p>
+    <p id="p-21" num="21">[0017]      In certain embodiments, the hydroxy functional carbonate containing material is substantially linear although, in some cases, if desired, it may be branched by the incorporation of polyfunctional components, such as low-molecular weight polyols such as glycerol, trimethylol propane, hexane-1,2,6-triol, butane-1,2,4-triol, trimethylol propane, pentaerythritol, <confidence value="22222222">quinitol</confidence>
+, mannitol and sorbitol, methyl glycoside and 1,4,3,6- dianhydrohexitols.    </p>
+    <p id="p-22" num="22">[0018]      Any of a variety of suitable polyisocyanates may be used to form the polycarbonate-polyurethane polymer utilized in the coating compositions of the present invention. Suitable polyisocyanates include, but are not limited to, 1,4-tetramethylene <confidence value="222222222222">diisocyanate</confidence>
+, 1,6-hexamethylene diisocyanate, isophorone diisocyanate, 4,4'-methylene- bis-(cyclohexyl isocyanate), p-phenylene diisocyanate, diphenylmethane-4,4<confidence value="88">'-</confidence>
+ <boundary-data type="header">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+      <page-break num="6"/>
+diisocyanate, 2,4-toluene diisocyanate, 2,6-toluene diisocyanate, triphenylmethane- 4,4',4"-triisocyanate, 1,2,4-be<confidence value="5">n</confidence>
+zene triisocyanate, polymethylene polyphenyl isocyanate, the isocyanurate of hexamethylene diisocyanate, the biuret of hexamethylene diisocyanate, the isocyanurate of isophorone diisocyanate, meta-a,<confidence value="21868">a~a',</confidence>
+a'- tetramethylxylylenediisocyanate, and para-<confidence value="8686">a,a,</confidence>
+a',a'-tetramethylxylylenediisocyanate.    </p>
+    <p id="p-23" num="23">[0019<confidence value="5">]</confidence>
+      Aqueous dispersions of such polycarbonate-polyurethane polymers, which are suitable for use in the coating compositions of the present invention, are commercially available. Examples of such products include those available from Bayer MaterialScience AG, Pittsburgh, Pennsylvania, under the Bayhydrol<confidence value="2">@</confidence>
+ tradename, including Bayhydrol <part-num-ref name="Bayhydrol@ tradename, including Bayhydrol">121</part-num-ref>
+ (anionic dispersion of an aliphatic polycarbonate-polyurethane in water and n-methyl-2-pyrrolidine with a tensile strength of <part-num-ref name="tensile strength of">6700</part-num-ref>
+ psi and an elongation at break of <part-num-ref name="elongation at break of">150</part-num-ref>
+ %), Bayhydrol <part-num-ref name="%), Bayhydrol">123</part-num-ref>
+ (anionic dispersion of an aliphatic polycarbonate- polyurethane polymer in water and n-methyl-2-pyrrolidine with a tensile strength of <part-num-ref name="tensile strength of">6000</part-num-ref>
+ psi and an elongation at break of <part-num-ref name="elongation at break of">320</part-num-ref>
+ %), and Bayhydrol LS <part-num-ref name="%), and Bayhydrol LS">2952</part-num-ref>
+ (anionic dispersion of an aliphatic polycarbonate-polyurethane polymer in water alone with a tensile strength of <part-num-ref name="tensile strength of">5500</part-num-ref>
+ psi and an elongation at break of <part-num-ref name="elongation at break of">400</part-num-ref>
+ %). In some cases, such aqueous dispersions are substantially free or, in some cases, completely free of organic solvent, such as is the case with Bayhydrol LS <part-num-ref name="case with Bayhydrol LS">2952.</part-num-ref>
+ As used herein, the term <confidence value="5">"</confidence>
+substantially free" means that the material being discussed is present, if at all, as an incidental impurity. In other words, the material does not affect the properties of the composition. As used herein, the term "completely free" means that the material is not present at all.    </p>
+    <p id="p-24" num="24">[0020<confidence value="5">1</confidence>
+      As previously indicated, certain embodiments of the coating compositions of the present invention comprise an aqueous dispersion comprising an acrylic polyol.    </p>
+    <p id="p-25" num="25">Acrylic polyols suitable for use in the present invention include those made by addition polymerization of different unsaturated polymerizable materials, at least one of which is a hydroxy-containing ethylenically unsaturated polymerizable material. Examples of such materials, which are suitable for use in preparing the acrylic polyol included in the coating compositions of the present invention, are vinyl monomers, such as hydroxyalkyl acrylates and methacrylates, including the acrylic acid and methacrylic acid esters of ethylene glycol and propylene glycol. These acrylates and methacrylates often have <part-num-ref name="acrylic acid and methacrylic acid esters of ethylene glycol and propylene glycol. These acrylates and methacrylates often have">2</part-num-ref>
+ to <boundary-data type="header">
+        <confidence value="8">6</confidence>
+      </boundary-data>
+      <page-break num="7"/>
+      <part-num-ref name="to">6</part-num-ref>
+ carbon atoms in the alkyl group. Also suitable are hydroxy-containing esters and/or amides of unsaturated acids such as maleic acid, fumaric acid, itaconic acid and the like.    </p>
+    <p id="p-26" num="26">
+      <confidence value="4">[</confidence>
+0021<confidence value="5">]</confidence>
+      In certain embodiments, the hydroxy-containing ethylenically unsaturated polymerizable material comprises a mixture of two or more of the foregoing materials.    </p>
+    <p id="p-27" num="27">In certain embodiments, such mixtures comprise a mixture of materials wherein at least one of the materials comprises a primary hydroxy group, such as hydroxyethyl (meth)acrylate and 1-butyl (meth)acrylate. As used herein, the term "(meth)acrylate" is meant to include both acrylates and methacrylates. In certain embodiments, such mixtures comprise at least <part-num-ref name="term &quot;(meth)acrylate&quot; is meant to include both acrylates and methacrylates. In certain embodiments, such mixtures comprise at least">2</part-num-ref>
+ percent by weight of materials comprising a primary hydroxy group, based on the total weight of hydroxy-containing ethylenically unsaturated polymerizable materials.    </p>
+    <p id="p-28" num="28">[0022]      In certain embodiments, the amount of hydroxy-containing ethylenically unsaturated polymerizable material used to prepare the acrylic polyol ranges from <part-num-ref name="acrylic polyol ranges from">2</part-num-ref>
+ to <part-num-ref name="to">50</part-num-ref>
+ percent by weight, such as <part-num-ref name="percent by weight, such as">20</part-num-ref>
+ to <part-num-ref name="to">30</part-num-ref>
+ percent by weight, based on the weight of the total monomer combination used to prepare the acrylic polyol.    </p>
+    <p id="p-29" num="29">
+      <confidence value="5">[</confidence>
+0023]      In certain embodiments, the acrylic polyol present in the coating compositions of the present invention is also made from an ethylenically unsaturated polymerizable material(s) substantially, or, in some cases, completely free of hydroxyl groups and carboxylic acid groups. Examples of such materials, which are suitable for use in preparing the acrylic polyol utilized in the coating compositions of the present invention are vinyl monomers, such as alkyl, cycloalkyl, or aryl acrylates and methacrylates having <part-num-ref name="present invention are vinyl monomers, such as alkyl, cycloalkyl, or aryl acrylates and methacrylates having">1</part-num-ref>
+ to <part-num-ref name="to">6</part-num-ref>
+ carbon atoms in the esterifying group. Specific examples include methyl methacrylate and n-butyl methacrylate. Other suitable materials include lauryl methacrylate, 2-ethylhexyl methacrylate, <confidence value="22222222">isobomyl</confidence>
+ methacrylate, and cyclohexyl methacrylate. An aromatic vinyl monomer that is often included is styrene. Other materials that may be used are ethylenically unsaturated materials such as monoolefinic and diolefinic hydrocarbons, unsaturated esters of organic and inorganic acids, amides and esters of unsaturated acids, nitriles, and unsaturated acids. Examples of such monomers include, without limitation, 1,3-butadiene, acrylamide, acrylonitrile, alpha- methyl styrene, alpha-methyl chlorostyrene, vinyl butyrate, vinyl acetate, allyl chloride, <boundary-data type="header">
+        <confidence value="8">7</confidence>
+      </boundary-data>
+      <page-break num="8"/>
+divinyl benzene, diallyl itaconate, triallyl cyanurate, as well as mixtures thereof. In certain embodiments, the amount of ethylenically unsaturated polymerizable material(s) free of hydroxyl groups and carboxylic acid groups used to prepare the acrylic <confidence value="222222">polyol</confidence>
+ ranges from <part-num-ref name="acrylic polyol ranges from">40</part-num-ref>
+ to <part-num-ref name="to">98</part-num-ref>
+ percent by weight, such as <part-num-ref name="percent by weight, such as">60</part-num-ref>
+ to <part-num-ref name="to">80</part-num-ref>
+ percent by weight, based on the weight of the total monomer combination used to prepare the acrylic polyol.    </p>
+    <p id="p-30" num="30">[0024<confidence value="5">]</confidence>
+      In certain embodiments, the acrylic <confidence value="222222">polyol</confidence>
+ present in the coating compositions of the present invention is also made from an ethylenically unsaturated polymerizable material that comprises carboxylic acid groups. Virtually any unsaturated acid functional monomer may be used, for example, acrylic acid, methacrylic acid, itaconic acid, and half esters of unsaturated dicarboxylic acids such as maleic acid. In certain embodiments, the amount of ethylenically unsaturated polymerizable material that comprises carboxylic acid groups, which is used to prepare the acrylic polyol, ranges from 0.5 to <part-num-ref name="acrylic polyol, ranges from 0.5 to">10</part-num-ref>
+ percent by weight, such as <part-num-ref name="percent by weight, such as">2</part-num-ref>
+ to <part-num-ref name="to">4</part-num-ref>
+ percent by weight, based on the weight of the total monomer combination used to prepare the acrylic polyol.    </p>
+    <p id="p-31" num="31">[0025<confidence value="5">]</confidence>
+      In certain embodiments, the acrylic polyol described above may be synthesized from a combination of unsaturated <confidence value="22222222222222222222222">polymerizable.materials</confidence>
+ comprising (a) <part-num-ref name="combination of unsaturated polymerizable.materials comprising (a)">2</part-num-ref>
+ to <part-num-ref name="to">50</part-num-ref>
+ percent by weight, such as <part-num-ref name="percent by weight, such as">20</part-num-ref>
+ to <part-num-ref name="to">30</part-num-ref>
+ percent by weight, of hydroxy-containing ethylenically unsaturated polymerizable material(s); (b) <part-num-ref name="percent by weight, of hydroxy-containing ethylenically unsaturated polymerizable material(s); (b)">40</part-num-ref>
+ to <part-num-ref name="to">98</part-num-ref>
+ percent by weight, such as <part-num-ref name="percent by weight, such as">60</part-num-ref>
+ to <part-num-ref name="to">80</part-num-ref>
+ percent by weight, of ethylenically unsaturated polymerizable material(s) free of hydroxyl groups and carboxylic acid groups; and (c) 0.5 to <part-num-ref name="percent by weight, of ethylenically unsaturated polymerizable material(s) free of hydroxyl groups and carboxylic acid groups; and (c) 0.5 to">10</part-num-ref>
+ percent by weight, such as <part-num-ref name="percent by weight, such as">2</part-num-ref>
+ to <part-num-ref name="to">4</part-num-ref>
+ percent by weight, of ethylenically unsaturated polymerizable material(s) that comprise carboxylic acid groups.    </p>
+    <p id="p-32" num="32">[0026<confidence value="5">]</confidence>
+      In certain embodiments, the acrylic polyol has a hydroxyl number ranging from <part-num-ref name="hydroxyl number ranging from">2</part-num-ref>
+ to <part-num-ref name="to">50,</part-num-ref>
+ such as from <part-num-ref name="to 50, such as from">20</part-num-ref>
+ to <part-num-ref name="to">30,</part-num-ref>
+ or, in some cases, from <part-num-ref name="to 30, or, in some cases, from">5</part-num-ref>
+ to <part-num-ref name="to">250</part-num-ref>
+ mg KO<confidence value="5">H</confidence>
+/gram of polymer as determined by well known potentiometric techniques. In certain embodiments, the acrylic polyol contains from 0.070 to 1.400 millequivalents acid per gram of polymer solids, such as 0.250 to 0.550 millequivalents acid per gram of polymer solids.    </p>
+    <p id="p-33" num="33">[0027<confidence value="5">]</confidence>
+      As previously indicated, in certain embodiments of the coating compositions of the present invention the acrylic polyol is of relatively low molecular <boundary-data type="header">
+        <confidence value="8">8</confidence>
+      </boundary-data>
+      <page-break num="9"/>
+weight, i.e., it has a number average molecular weight of no more than 5,000, such as from <part-num-ref name="number average molecular weight of no more than 5,000, such as from">500</part-num-ref>
+ to <part-num-ref name="to">4000</part-num-ref>
+ or, in some cases, from <part-num-ref name="or, in some cases, from">1000</part-num-ref>
+ to <part-num-ref name="to">3000,</part-num-ref>
+ the molecular weight determined by gel permeation chromatography (GP<confidence value="66">C)</confidence>
+ using polystyrene as standard. In certain embodiments, such acrylic polyols also have a polydispersity index of from <part-num-ref name="polydispersity index of from">1</part-num-ref>
+ to <part-num-ref name="to">7,</part-num-ref>
+ such as <part-num-ref name="to 7, such as">1</part-num-ref>
+ to <part-num-ref name="to">5</part-num-ref>
+ or, in some cases <part-num-ref name="or, in some cases">1</part-num-ref>
+ to <part-num-ref name="to">4.</part-num-ref>
+ As used herein, the term "polydispersity index" refers to the weight average molecular weight (Mw) divided by the number average molecular weight (Mn) of the polymer as determined by gel permeation chromatography using polystyrene standards.    </p>
+    <p id="p-34" num="34">[0028]       In certain embodiments, an aqueous dispersion is formed comprising the acrylic polyol. A suitable method for making such an aqueous dispersion is set forth in the Examples herein. In certain embodiments, the aqueous dispersion comprising the acrylic polyol is prepared by first preparing the acrylic polymer in an organic solvent and then, prior to dispersing into water, acid groups on the acrylic polyol are neutralized with an alkaline material, such as an amine. Suitable amines that may be used for this purpose include, but are not limited to, dialkanolamines, trialkanolamines, alkylalkanolamines, and arylalkanolamines containing from <part-num-ref name="amine. Suitable amines that may be used for this purpose include, but are not limited to, dialkanolamines, trialkanolamines, alkylalkanolamines, and arylalkanolamines containing from">2</part-num-ref>
+ to <part-num-ref name="to">18</part-num-ref>
+ carbon atoms in the alkanol, alkyl, and aryl chains. Specific examples include N-ethyle<confidence value="5">t</confidence>
+hanolamine, N- methylethanolamine, diethanolamine, triethanolamine, N-phenylethanolamine and diisopropanolamine. Also suitable are amines which do not contain hydroxyl groups, such as trialkylamines, diamines and mixed alkyl-aryl amines and substituted amines in which the substituents are other than hydroxyl can also be used. Specific examples of these amines are triethylamine, methylethylamine, 2-methylpropylamine, diethylamine, dipropylamine, dibutylamine, dicocoamine, diphenylamine, N-methylaniline, diisopropylamine, methylphenylamine and dicyclohexylamine. Also, amines with ring structures such as morpholine, piperidine, N-methylpiperazine and N- hydroxyethylpiperazine can be used. Ammonia can also be used and is considered for the purposes of this application to be an amine.    </p>
+    <p id="p-35" num="35">[0029<confidence value="5">]</confidence>
+       In certain embodiments, the continuous phase of the aqueous dispersion comprises exclusively water. In some embodiments, however, organic solvent may be present in the aqueous dispersion as well (as part of the dispersed phase) to, for example, assist in lowering the viscosity of the polymer(s) to be dispersed. For example, in certain <boundary-data type="header">
+        <confidence value="8">9</confidence>
+      </boundary-data>
+      <page-break num="10"/>
+embodiments, the aqueous dispersion comprises up to <part-num-ref name="aqueous dispersion comprises up to">20</part-num-ref>
+ weight percent, such as up to <part-num-ref name="weight percent, such as up to">5</part-num-ref>
+ weight percent, or, in some cases, up to <part-num-ref name="weight percent, or, in some cases, up to">2</part-num-ref>
+ weight percent organic solvent, with weight percent being based on the total weight of the aqueous dispersion. Examples of suitable solvents which can be incorporated in the organic component of the aqueous dispersion are xylene, a ketone, such as methyl amyl ketone, methyl isoamyl ketone, and/or methyl isobutyl ketone, and/or an acetate, such as n-butyl acetate, t-butyl acetate, and/or butyl carbitol acetate.    </p>
+    <p id="p-36" num="36">[0030]      As previously indicated, the coating compositions of the present invention comprise a first component comprising an aqueous dispersion comprising the previously described polycarbonate-polyurethane polymer and the previously-described acrylic polyol. The Examples herein describe a suitable method for making such a dispersion.</p>
+    <p id="p-37" num="37">In certain embodiments, the aqueous dispersion is prepared by mixing an aqueous dispersion comprising the acrylic polyol, which may be prepared as described above, with an aqueous dispersion comprising the polycarbonate-polyurethane polymer, which may comprise one or more of the commercially available products described earlier. In certain embodiments of the present invention, the amount of polycarbonate-polyurethane polymer present in the first component ranges from <part-num-ref name="first component ranges from">5</part-num-ref>
+ to <part-num-ref name="to">50</part-num-ref>
+ percent by weight, such as <part-num-ref name="percent by weight, such as">15</part-num-ref>
+ to <part-num-ref name="to">30</part-num-ref>
+ percent by weight, based on the resins solids of the first component. In certain embodiments of the present invention, the amount of acrylic polyol present in the first component ranges from <part-num-ref name="first component ranges from">30</part-num-ref>
+ to <part-num-ref name="to">95</part-num-ref>
+ percent by weight, such as <part-num-ref name="percent by weight, such as">60</part-num-ref>
+ to <part-num-ref name="to">80</part-num-ref>
+ percent by weight, based on the resins solids of the first component.    </p>
+    <p id="p-38" num="38">[0031]      As previously indicated, the multi-component coating compositions of the present invention also comprise a second component comprising a material having functional groups reactive with the functional groups of the acrylic polyol and/or the polycarbonate-polyurethane polymer. Such a material may be referred to herein as a "curing agent" or "crosslinking agent." [0032]      Non-limiting examples of suitable curing agents include, for example, polyisocyanates that are adapted to be water soluble or water dispersible. Such materials are commercially available and include, for example, Desmodur<confidence value="4">®</confidence>
+ <confidence value="8">X</confidence>
+P <part-num-ref name="&quot;curing agent&quot; or &quot;crosslinking agent.&quot; [0032]      Non-limiting examples of suitable curing agents include, for example, polyisocyanates that are adapted to be water soluble or water dispersible. Such materials are commercially available and include, for example, Desmodur® XP">2410,</part-num-ref>
+ an aliphatic polyisocyanate resin based on hexamethylene diisocyanate, and Bayhydrol<confidence value="4">®</confidence>
+ VP LS <boundary-data type="header">
+        <confidence value="88">10</confidence>
+      </boundary-data>
+      <page-break num="11"/>
+      <part-num-ref name="aliphatic polyisocyanate resin based on hexamethylene diisocyanate, and Bayhydrol® VP LS">2319,</part-num-ref>
+ a water dispersed aliphatic polyisocyanate resin, Bayhydur<confidence value="4">®</confidence>
+ <part-num-ref name="water dispersed aliphatic polyisocyanate resin, Bayhydur®">302,</part-num-ref>
+ a water dispersible polyisocyanate resin based on hexamethylene diisocyanate, Bayhydur<confidence value="4">®</confidence>
+ VP LS <part-num-ref name="water dispersible polyisocyanate resin based on hexamethylene diisocyanate, Bayhydur® VP LS">2150,</part-num-ref>
+ a water dispersible polyisocyanate based on isophorone diisocyanate, and <confidence value="222222222">Bayhydur®</confidence>
+ XP <part-num-ref name="water dispersible polyisocyanate based on isophorone diisocyanate, and Bayhydur® XP">7165,</part-num-ref>
+ a solvent-free, water dispersible polyisocyanate based on hexamethylene diisocyanate, all of which are commercially available from Bayer MaterialScience AG. Also suitable are Rhodocoat<confidence value="4">®</confidence>
+ WT <part-num-ref name="solvent-free, water dispersible polyisocyanate based on hexamethylene diisocyanate, all of which are commercially available from Bayer MaterialScience AG. Also suitable are Rhodocoat® WT">1000,</part-num-ref>
+ WT <part-num-ref name="solvent-free, water dispersible polyisocyanate based on hexamethylene diisocyanate, all of which are commercially available from Bayer MaterialScience AG. Also suitable are Rhodocoat® WT 1000, WT">2092,</part-num-ref>
+ WT <part-num-ref name="solvent-free, water dispersible polyisocyanate based on hexamethylene diisocyanate, all of which are commercially available from Bayer MaterialScience AG. Also suitable are Rhodocoat® WT 1000, WT 2092, WT">2102,</part-num-ref>
+ XWT <part-num-ref name="solvent-free, water dispersible polyisocyanate based on hexamethylene diisocyanate, all of which are commercially available from Bayer MaterialScience AG. Also suitable are Rhodocoat® WT 1000, WT 2092, WT 2102, XWT">2104,</part-num-ref>
+ all of which are water dispersible polyisocyanate resins based on aliphatic polyisocyanates commercially available from Rhodia Corporation.    </p>
+    <p id="p-39" num="39">
+      <confidence value="5">[</confidence>
+0033<confidence value="5">]</confidence>
+      In certain embodiments, the material having functional groups reactive with the functional groups of the acrylic polyol and/or the polycarbonate-polyurethane polymer is present in the coating composition in an amount of <part-num-ref name="amount of">15</part-num-ref>
+ to <part-num-ref name="to">40</part-num-ref>
+ percent by weight, such as <part-num-ref name="percent by weight, such as">20</part-num-ref>
+ to <part-num-ref name="to">30</part-num-ref>
+ percent by weight, based on the total weight of resin solids in the composition.    </p>
+    <p id="p-40" num="40">
+      <confidence value="5">[</confidence>
+0034<confidence value="5">]</confidence>
+       The coating compositions of the present invention can contain, in addition to the components described above, a variety of other adjuvant materials. If desired, other resinous materials can be utilized in conjunction with the aforementioned resins.    </p>
+    <p id="p-41" num="41">Certain embodiments of the coating compositions of the present invention include surface active agents, such as any of the well known anionic, cationic or nonionic surfactants or dispersing agents.</p>
+    <p id="p-42" num="42">[0035]       The coating compositions of the present invention can further include inorganic and/or inorganic-organic particles, for example, silica, alumina, including treated alumina (e.g. silica-treated alumina known as alpha aluminum oxide), silicon carbide, diamond dust, cubic boron nitride, and boron carbide.</p>
+    <p id="p-43" num="43">[0036]      In certain embodiments, the particles comprise inorganic particles that have an average particle size ranging from <part-num-ref name="average particle size ranging from">1</part-num-ref>
+ to <part-num-ref name="to">10</part-num-ref>
+ microns, or from <part-num-ref name="microns, or from">1</part-num-ref>
+ to <part-num-ref name="to">5</part-num-ref>
+ microns prior to incorporation into the coating composition. In other embodiments, the inorganic particles comprise aluminum oxide having an average particle size ranging from <part-num-ref name="average particle size ranging from">1</part-num-ref>
+ to <part-num-ref name="to">5</part-num-ref>
+ microns prior to incorporation into the film-forming composition.    </p>
+    <p id="p-44" num="44">[0037]      In certain embodiments, such inorganic particles can have an average particle size ranging from <part-num-ref name="average particle size ranging from">1</part-num-ref>
+ to less than <part-num-ref name="to less than">1000</part-num-ref>
+ nanometers, such as from <part-num-ref name="nanometers, such as from">1</part-num-ref>
+ to <part-num-ref name="to">100</part-num-ref>
+ <boundary-data type="header">
+        <confidence value="88">11</confidence>
+      </boundary-data>
+      <page-break num="12"/>
+nanometers, or, in some cases, from <part-num-ref name="nanometers, or, in some cases, from">5</part-num-ref>
+ to <part-num-ref name="to">50</part-num-ref>
+ nanometers, or, in yet other cases, <part-num-ref name="nanometers, or, in yet other cases,">5</part-num-ref>
+ to <part-num-ref name="to">25</part-num-ref>
+ nanometers, prior to incorporation into the composition. These materials may constitute, in certain embodiments of the present invention, up to <part-num-ref name="present invention, up to">30</part-num-ref>
+ percent by weight, such as 0.05 to <part-num-ref name="percent by weight, such as 0.05 to">5</part-num-ref>
+ percent by weight, or, in some cases, 0.1 to <part-num-ref name="percent by weight, or, in some cases, 0.1 to">1</part-num-ref>
+ percent by weight, or, in yet other cases, 0.1 to 0.5 percent by weight, based on the total weight of the coating composition.    </p>
+    <p id="p-45" num="45">
+      <confidence value="5">[</confidence>
+0038]      The coating compositions also may contain a catalyst to accelerate the cure reaction, for example, between the curing agent(s) and the acrylic polyol and/or the polycarbonate-polyurethane polymer. Examples of suitable catalysts include organotin compounds such as dibutyl tin dilaurate, dibutyl tin oxide and dibutyl tin diacetate.    </p>
+    <p id="p-46" num="46">When used, the catalyst often is present in an amount ranging from 0.1 to 5.0 percent by weight, or, in some cases, 0.5 to 1.5 percent by weight, based on the total weight of resin solids present in the coating composition.</p>
+    <p id="p-47" num="47">[0039]      Other additive ingredients, for example, plasticizers, surfactants, thixotropic agents, anti-gassing agents, flow controllers, anti-oxidants, UV light absorbers and similar additives conventional in the art can be included in the compositions of the present invention. When used, these ingredients are often present in an amount of up to about <part-num-ref name="amount of up to about">40</part-num-ref>
+ percent by weight based on the total weight of resin solids.    </p>
+    <p id="p-48" num="48">[0040]      The coating compositions of the present invention also may, in certain embodiments, be formulated to include one or more pigments or fillers to provide color and/or optical effects, or opacity. Such pigmented coating compositions may be suitable for use in multi-component composite coatings as discussed below, for example, as a primer coating or as a pigmented base coating composition in a color-plus-clear system, or as a monocoat topcoat.</p>
+    <p id="p-49" num="49">
+      <confidence value="5">[</confidence>
+0041]      The solids content of the coating compositions of the present invention often ranges from <part-num-ref name="present invention often ranges from">20</part-num-ref>
+ to <part-num-ref name="to">75</part-num-ref>
+ percent by weight, or <part-num-ref name="percent by weight, or">30</part-num-ref>
+ to <part-num-ref name="to">65</part-num-ref>
+ percent by weight, or <part-num-ref name="percent by weight, or">40</part-num-ref>
+ to <part-num-ref name="to">55</part-num-ref>
+ percent by weight, based on the total weight of the coating composition.    </p>
+    <p id="p-50" num="50">[0042]      Suitable methods for making the coating compositions of the present invention are set forth in the Examples. Prior to application of the coating composition to a substrate, the first component and second component are mixed together. In certain embodiments, the coating compositions of the present invention have a pot life of up to <part-num-ref name="pot life of up to">8</part-num-ref>
+ <boundary-data type="header">
+        <confidence value="88">12</confidence>
+      </boundary-data>
+      <page-break num="13"/>
+hours, such as up to <part-num-ref name="hours, such as up to">4</part-num-ref>
+ hours. As used herein the term "pot life" refers to the length of time that the coating composition remains sufficiently flowable to be coatable.    </p>
+    <p id="p-51" num="51">[0043]       The coating compositions of the present invention can be applied to various substrates including wood, metals, glass, paper, masonry surfaces, foam, and plastic, including elastomeric substrates, among others. In some cases, the coating compositions of the present invention are particularly suitable for application to plastic substrates. As used herein, the term "plastic substrate" is intended to include any thermoplastic or thermosetting synthetic material used in injection or reaction molding, sheet molding or other similar processes whereby parts are formed, such as, for example, acrylonitrile butadiene styrene ("ABS"), polycarbonate, thermoplastic elastomer, polyurethane, and thermoplastic polyurethane, among others. As a result, the present invention is also directed to substrates at least partially coated with a coating deposited from a coating composition of the present invention. The compositions can be applied by conventional means including brushing, dipping, flow coating, spraying and the like.</p>
+    <p id="p-52" num="52">The usual spray techniques and equipment for air spraying and either manual or automatic methods can be used.</p>
+    <p id="p-53" num="53">[0044]       After application of the coating composition of the present invention to the substrate, the composition is allowed to coalesce to form a substantially continuous film on the substrate. Typically, the film thickness will be 0.01 to <part-num-ref name="film thickness will be 0.01 to">20</part-num-ref>
+ mils (about 0.25 to <part-num-ref name="mils (about 0.25 to">508</part-num-ref>
+ microns), such as 0.01 to <part-num-ref name="microns), such as 0.01 to">5</part-num-ref>
+ mils (0.25 to <part-num-ref name="mils (0.25 to">127</part-num-ref>
+ microns), or, in some cases, 0.1 to <part-num-ref name="microns), or, in some cases, 0.1 to">2</part-num-ref>
+ mils (2.54 to 50.8 microns) in thickness. The film is formed on the surface of the substrate by driving material, such as water and/or volatile organic compounds (if any) out of the film by heating or by an air drying period. In some cases, the heating will only be for a short period of time, sufficient to ensure that any subsequently applied coatings can be applied to the film without dissolving the composition. Suitable drying conditions will depend on the particular composition and substrate, but, in general, a drying time of from about <part-num-ref name="drying time of from about">1</part-num-ref>
+ to <part-num-ref name="to">5</part-num-ref>
+ minutes at a temperature of about 68<confidence value="2">*</confidence>
+F to 250<confidence value="2">*</confidence>
+F (20<confidence value="28">*C</confidence>
+ to 121<confidence value="2">*</confidence>
+C) will be adequate. More than one coat of the coating composition may be applied to develop the optimum appearance. Between coats, the previously applied coat may be flashed, that is, exposed to ambient conditions for about <part-num-ref name="previously applied coat may be flashed, that is, exposed to ambient conditions for about">1</part-num-ref>
+ to <part-num-ref name="to">20</part-num-ref>
+ minutes.    </p>
+    <boundary-data type="header">
+      <confidence value="88">13</confidence>
+    </boundary-data>
+    <p id="p-54" num="54">
+      <page-break num="14"/>
+[0045]      The coating compositions of the present invention may be used as a single coating, a clear top coating, a base coating in a two-layered system, or one or more layers of a multi-layered system including a clear top coating composition, colorant layer and base coating composition, or as a primer layer.    </p>
+    <p id="p-55" num="55">[0046]      In certain embodiments, the coating compositions of the present invention may be used as part of a multi-component composite coating, such as a "color-plus- clear" coating system, which includes at least one pigmented or colored base coat and at least one clear topcoat. As a result, the present invention is also directed to multi- component composite coatings, wherein at least one coating layer is deposited from a composition comprising a coating composition of the present invention. In certain embodiments, all of the layers of such a multi-component composite coating are deposited from a composition comprising a coating composition of the present invention.</p>
+    <p id="p-56" num="56">
+      <confidence value="5">[</confidence>
+0047<confidence value="5">]</confidence>
+      For example, in certain embodiments, the coating composition from which a pigmented base coating is deposited may include a coating composition of the present invention. In such embodiments<confidence value="5">,</confidence>
+ the coating composition of the clear topcoat in the color-plus-clear system may comprise any composition useful in coatings applications, such as those typically used in automotive OEM applications, automotive refinish applications, industrial coating applications, architectural coating applications, electrocoating applications, powder coating applications, coil coating applications, and aerospace coating applications, among others. The coating composition of the clear topcoat typically comprises a resinous binder. Particularly useful resinous binders include, for example, acrylic polymers, polyesters, including alkyds, and polyurethanes, among others.    </p>
+    <p id="p-57" num="57">
+      <confidence value="5">[</confidence>
+0048]      As previously indicated, certain embodiments of the coating compositions of the present invention can provide coatings that exhibit favorable adhesion to a plastic substrate. Therefore, as should be apparent from the foregoing description, the present invention is also directed to multi-component waterborne coating compositions comprising an aqueous dispersion of a polycarbonate-polyurethane polymer, wherein when the composition is deposited onto at least a portion of a plastic substrate and cured, the composition produces a coating that adheres to the substrate at least as well as a <boundary-data type="header">
+        <confidence value="88">14</confidence>
+      </boundary-data>
+      <page-break num="15"/>
+conventional multi-component <confidence value="222222222222">solventborne</confidence>
+ polyurethane containing coating composition adheres to the same substrate when applied under the same conditions. As used herein, when it is stated that a coating "adheres to a substrate at least as well as" another coating, it means that the coating exhibits adhesion properties, measured as described in the Examples herein, equal to or superior to the adhesion properties exhibited by the coating to which it is being compared. As used herein, the term "conventional multi-component <confidence value="222222222222">solventborne</confidence>
+ polyurethane containing coating composition" refers to a medium solids (30-45 percent solids by weight) <confidence value="2222222222228">solventborne,</confidence>
+ two component urethane monocoat, such as that commercially available from PPG Industries, Inc., Pittsburgh, Pennsylvania, as the SPECTRACRON<confidence value="2">@</confidence>
+ SPU <part-num-ref name="SPECTRACRON@ SPU">5000</part-num-ref>
+ XPM Series coatings. As used herein, when it is stated that a coating is applied "under the same conditions" as another coating, it means that the coating composition is (i) deposited on the substrate at the same or similar film thickness as the composition to which it is being compared, and (ii) cured under the same or similar cure conditions, such as cure temperature, humidity, and time, as the composition to which it is being compared.    </p>
+    <p id="p-58" num="58">
+      <confidence value="5">[</confidence>
+0049<confidence value="5">]</confidence>
+      Illustrating the invention are the following examples, which, however, are not to be considered as limiting the invention to their details. Unless otherwise indicated, all parts and percentages in the following examples, as well as throughout the specification, are by weight.    </p>
+    <heading id="h-9">EXAMPLES</heading>
+    <p id="p-59" num="59">Example 1:  Preparation of Acrylic Pol<confidence value="5">y</confidence>
+ol Dispersion [0050]      In a <part-num-ref name="">12</part-num-ref>
+ L glass reaction vessel equipped with a reflux condenser, a stainless steel agitator and a N2 inlet, <part-num-ref name="N2 inlet,">360</part-num-ref>
+ g of Aromatic <part-num-ref name="g of Aromatic">100</part-num-ref>
+ and <part-num-ref name="and">180</part-num-ref>
+ g of Dowanol PM were introduced and heated to reflux. In a second container a primary monomer mixture of <part-num-ref name="primary monomer mixture of">1416</part-num-ref>
+ g of methyl methacrylate, <part-num-ref name="g of methyl methacrylate,">661</part-num-ref>
+ g of styrene, <part-num-ref name="g of styrene,">73</part-num-ref>
+ g of <confidence value="5">a</confidence>
+-methylstyrene dimer, <part-num-ref name="g of a-methylstyrene dimer,">165</part-num-ref>
+ g of butyl methacrylate, <part-num-ref name="g of butyl methacrylate,">518</part-num-ref>
+ g of butyl acrylate and <part-num-ref name="g of butyl acrylate and">840</part-num-ref>
+ g of hydroxyethyl methacrylate was prepared. In a third container an initiator solution of <part-num-ref name="initiator solution of">251</part-num-ref>
+ g Lupersol <part-num-ref name="g Lupersol">270</part-num-ref>
+ in <part-num-ref name="in">90</part-num-ref>
+ g Dowanol PnB was prepared. The initiator solution was pumped into the <boundary-data type="header">
+        <confidence value="88">15</confidence>
+      </boundary-data>
+      <page-break num="16"/>
+reaction vessel at a constant rate over <part-num-ref name="constant rate over">3</part-num-ref>
+ hours and <part-num-ref name="hours and">35</part-num-ref>
+ minutes. Five minutes after the addition of the initiator solution started, the primary monomer mixture was pumped into the reactor at a constant rate over <part-num-ref name="constant rate over">2</part-num-ref>
+ hours. In a fourth container a secondary monomer mixture of <part-num-ref name="secondary monomer mixture of">242</part-num-ref>
+ g of methyl methacrylate, <part-num-ref name="g of methyl methacrylate,">189</part-num-ref>
+ g of styrene, <part-num-ref name="g of styrene,">340</part-num-ref>
+ g of hydroxyethyl methacrylate and <part-num-ref name="g of hydroxyethyl methacrylate and">113</part-num-ref>
+ g of acrylic acid was prepared. When the addition of the primary monomer solution was complete the secondary monomer mixture was pumped into the reaction vessel over <part-num-ref name="reaction vessel over">1</part-num-ref>
+ hour at a constant rate. After complete addition of the secondary monomer feed and the initiator solution the reaction was held at reflux for <part-num-ref name="reaction was held at reflux for">30</part-num-ref>
+ minutes.    </p>
+    <p id="p-60" num="60">After this hold period the reaction was cooled to <part-num-ref name="reaction was cooled to">100</part-num-ref>
+ <confidence value="2">*</confidence>
+C. At <part-num-ref name="*C. At">100</part-num-ref>
+ <confidence value="1">0</confidence>
+C an amine solution of <part-num-ref name="amine solution of">136</part-num-ref>
+ g of dimethylethanolamine, <part-num-ref name="g of dimethylethanolamine,">68</part-num-ref>
+ g of triethanolamine and <part-num-ref name="g of triethanolamine and">614</part-num-ref>
+ grams of deionized water was added to the reaction vessel dropwise from an addition funnel over <part-num-ref name="addition funnel over">20</part-num-ref>
+ minutes. After complete addition of the amine solution and mixing for <part-num-ref name="amine solution and mixing for">15</part-num-ref>
+ minutes, <part-num-ref name="minutes,">4905</part-num-ref>
+ g of deionized water was added under high agitation. The reaction was cooled to <part-num-ref name="reaction was cooled to">40</part-num-ref>
+ <confidence value="28">*C</confidence>
+ and left to mix at this temperature overnight. The resin dispersion was filtered through a <part-num-ref name="">25</part-num-ref>
+ micron filter. The resulting acrylic dispersion had a pH of 8.5, a solids content of 42.4%, an average particle size of <part-num-ref name="average particle size of">1650</part-num-ref>
+ angstroms, and a viscosity of <part-num-ref name="viscosity of">100</part-num-ref>
+ centipoise.    </p>
+    <p id="p-61" num="61">Example 2: Preparation of Coating Compositions [0051]       Samples 1 and <part-num-ref name="and">2</part-num-ref>
+ were prepared using the ingredients and amounts (in grams) shown in Table <part-num-ref name="ingredients and amounts (in grams) shown in Table">1.</part-num-ref>
+ The samples were prepared as follows. The first component ingredients were weighed together and processed for <confidence value="2">~</confidence>
+ <part-num-ref name="first component ingredients were weighed together and processed for ~">5</part-num-ref>
+ minutes at <confidence value="2">~</confidence>
+ <part-num-ref name="minutes at ~">500</part-num-ref>
+ rpm's. The second component ingredients were weighed together and processed for <confidence value="2">~</confidence>
+ <part-num-ref name="second component ingredients were weighed together and processed for ~">5</part-num-ref>
+ minutes at <confidence value="2">~</confidence>
+ <part-num-ref name="minutes at ~">500</part-num-ref>
+ rpm's. The two premixes were blended together for <part-num-ref name="two premixes were blended together for">2</part-num-ref>
+ minutes under agitation immediately prior to application.    </p>
+    <boundary-data type="header">
+      <confidence value="88">16</confidence>
+    </boundary-data>
+    <p id="p-62" num="62">
+      <page-break num="17"/>
+Table 1 Material          Sample <part-num-ref name="Material          Sample">1</part-num-ref>
+    Sample <part-num-ref name="Sample">2</part-num-ref>
+ First Com<confidence value="5">p</confidence>
+onent Tint Paste                 112.37      150.20 Product from Example <part-num-ref name="First Component Tint Paste                 112.37      150.20 Product from Example">1</part-num-ref>
+      116.99      134.21 Bayhydrol <confidence value="88">VP</confidence>
+ <confidence value="88">LS</confidence>
+ <part-num-ref name="116.99      134.21 Bayhydrol VP LS">2952</part-num-ref>
+         37.50        0.00 Deionized Water              24.83       20.98 BYK-333<confidence value="4">2</confidence>
+                      0.07        0.08 Dowanol PNB<confidence value="4">3</confidence>
+                  0.00        3.71 Second Com<confidence value="5">p</confidence>
+onent Bayhyrol <confidence value="88">VP</confidence>
+ LS <part-num-ref name="37.50        0.00 Deionized Water              24.83       20.98 BYK-3332                      0.07        0.08 Dowanol PNB3                  0.00        3.71 Second Component Bayhyrol VP LS">2319</part-num-ref>
+          12.77       15.02 Desmodur XP <part-num-ref name="12.77       15.02 Desmodur XP">2410</part-num-ref>
+             12.77       15.02 Butylcarbitol acetate<confidence value="1">4</confidence>
+       10.90       12.82 Tint paste based on Sparkle Silver <part-num-ref name="12.77       15.02 Butylcarbitol acetate4       10.90       12.82 Tint paste based on Sparkle Silver">3500,</part-num-ref>
+ a commercially available aluminum flake from Silberline Manufacturing Company. The amount of paste used was such that the total pigment weight to binder weight ratio for the finished coating was 0.17 to 1.00.    </p>
+    <p id="p-63" num="63">
+      <confidence value="8">2</confidence>
+ <confidence value="6">A</confidence>
+ polyether modified polysiloxane defoamer supplied by BYK Chemie.    </p>
+    <p id="p-64" num="64">
+      <confidence value="8">3</confidence>
+ n-butoxypropanol supplied by Dow Chemical Company.    </p>
+    <p id="p-65" num="65">
+      <confidence value="6">4</confidence>
+ Diethylene glycol butyl ether acetate supplied by Dow Chemical Company.    </p>
+    <p id="p-66" num="66">Example 3: Test Substrates <confidence value="5">[</confidence>
+0052<confidence value="5">]</confidence>
+       Samples 1 and <part-num-ref name="and">2</part-num-ref>
+ from Example <part-num-ref name="from Example">2</part-num-ref>
+ and a <confidence value="222222222222">solventborne</confidence>
+ coating were applied to various plastic substrates. The <confidence value="22222222222">solventbome</confidence>
+ coating was SPECTRACRON<confidence value="4">®</confidence>
+ XPM <part-num-ref name="solventbome coating was SPECTRACRON® XPM">60360<confidence value="4">5</confidence>
+,      </part-num-ref>
+ commercially available from PPG Industries, Inc. The coatings were applied using a conventional Binks model <part-num-ref name="conventional Binks model">61</part-num-ref>
+ spray gun commercially available from ITW Industrial Finishing. The coatings were applied to a film thickness of<confidence value="5">-</confidence>
+20 microns and the painted panels were allowed to dehydrate at ambient temperature for <part-num-ref name="painted panels were allowed to dehydrate at ambient temperature for">10</part-num-ref>
+ minutes.    </p>
+    <p id="p-67" num="67">The panels were subsequently baked at 60<confidence value="2">*</confidence>
+ C for 30 minutes. The panels were then allowed to condition under ambient conditions for <part-num-ref name="panels were then allowed to condition under ambient conditions for">7</part-num-ref>
+ days. The panels were then tested, the results of which are shown in Table <part-num-ref name="results of which are shown in Table">2.</part-num-ref>
+    </p>
+    <boundary-data type="header">
+      <confidence value="88">17</confidence>
+    </boundary-data>
+    <p id="p-68" num="68">
+      <page-break num="18"/>
+Table 2 Material              Sample <part-num-ref name="Material              Sample">1</part-num-ref>
+     Sample <part-num-ref name="Sample">2</part-num-ref>
+     Solventbo<confidence value="658">rne</confidence>
+ Hardness<confidence value="1">'</confidence>
+                          <part-num-ref name="Solventborne Hardness'">148</part-num-ref>
+          <part-num-ref name="">105</part-num-ref>
+         <part-num-ref name="">143</part-num-ref>
+ MEK Resistance<confidence value="4">2</confidence>
+                      <part-num-ref name="MEK Resistance2">4</part-num-ref>
+            <part-num-ref name="">4</part-num-ref>
+            <part-num-ref name="">4</part-num-ref>
+ Adhesion to:    </p>
+    <p id="p-69" num="69">
+      <confidence value="45">pC</confidence>
+4         5B          OB           OB ABS<confidence value="5">5</confidence>
+         <confidence value="5">5</confidence>
+B           OB          4B <confidence value="222222">PC/ABS</confidence>
+6          5B           OB          <confidence value="68">5B</confidence>
+ PVC          <confidence value="6">5</confidence>
+B           OB           <confidence value="68">5B</confidence>
+ Post Humidity Adhesion to:    </p>
+    <p id="p-70" num="70">
+      <confidence value="458">pC4</confidence>
+         <confidence value="5">5</confidence>
+B          OB           OB <confidence value="8851">ABS5</confidence>
+         <confidence value="6">5</confidence>
+B           OB           3B <confidence value="2222222">PC/ABS6</confidence>
+          <confidence value="6">5</confidence>
+B           OB          <confidence value="68">5B</confidence>
+ PVC          <confidence value="6">5</confidence>
+B           OB           <confidence value="68">5B</confidence>
+ <confidence value="2">1</confidence>
+Har<confidence value="5">d</confidence>
+ness was measured using a Konig Pendulum Hardness tester according t<confidence value="5">o</confidence>
+ ASTM D4366.    </p>
+    <p id="p-71" num="71">2 MEK resistance was measured according to ASTM D4752.</p>
+    <p id="p-72" num="72">
+      <confidence value="5">3</confidence>
+ Adhesion was measured according to ASTM D3359.    </p>
+    <p id="p-73" num="73">
+      <confidence value="2">4</confidence>
+ LEXAN EXL 1414 polycarbonate resin commercially available from GE Advanced Materials.    </p>
+    <p id="p-74" num="74">
+      <confidence value="5">5</confidence>
+ Dow Magnum 344 acrylonitrile-butadiene-styrene resin commercially available from Dow Chemical Company.    </p>
+    <p id="p-75" num="75">6 CYCOLOY <confidence value="5">I</confidence>
+P 1000 polycarbonate / acrylonitrile-butadiene-styrene alloy commercially available from GE Advanced Materials.    </p>
+    <p id="p-76" num="76">
+      <confidence value="888">7MP</confidence>
+ 101 Platinum DK2234 polyvinyl chloride resin from PolyOne Corporation.    </p>
+    <p id="p-77" num="77">
+      <confidence value="5">8</confidence>
+ Post humidity adhesion was measured according to ASTM D3359 on panels which had been conditioned at 98% humidity and 60<confidence value="2">*</confidence>
+C for 4 days prior to adhesion testing.    </p>
+    <p id="p-78" num="78">
+      <confidence value="5">[</confidence>
+0053<confidence value="5">]</confidence>
+        As can be seen in Table 2, sample 1 which comprised a coating composition of the present invention performed at least similarly to the <confidence value="222222222222">solventborne</confidence>
+ coating, in terms of adhesion, hardness, and humidity resistance.    </p>
+    <p id="p-79" num="79">[0054]        It will be readily appreciated by those skilled in the art that modifications may be made to the invention without departing from the concepts disclosed in the foregoing description. Such modifications are to be considered as included within the following claims unless the claims, by their language, expressly state otherwise.</p>
+    <p id="p-80" num="80">Accordingly, the embodiments described in detail herein are illustrative only and are not limiting to the scope of the invention which is to be given the full breadth of the appended claims and any and all equivalents thereof.</p>
+    <boundary-data type="header">
+      <confidence value="88">18</confidence>
+    </boundary-data>
+  </description>
+</us-patent-application>
+

prior_art/11236969.xml

@@ -0,0 +1,83 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11236969</doc-number>
+        <date>2009-06-11</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <heading id="h-1">
+      <confidence value="5">I</confidence>
+N THE SPECIFICATION:    </heading>
+    <p id="p-1" num="1">Please delete paragraph [0025] of the specification as originally filed and substitute therefor the following:</p>
+    <p id="p-2" num="2">[0025]    Referring now to Figure 1, a contemporary earpiece comprise <confidence value="8">a</confidence>
+ generally arcuate rib <part-num-ref name="generally arcuate rib">11</part-num-ref>
+ and a generally vertical rib <part-num-ref name="generally vertical rib">12.</part-num-ref>
+ A top lobe <part-num-ref name="top lobe">15</part-num-ref>
+ is forme at the top, near where the arcuate rib <part-num-ref name="arcuate rib">11</part-num-ref>
+ and the generally vertical rib <part-num-ref name="generally vertical rib">12</part-num-ref>
+ inters<confidence value="7">e</confidence>
+ct.    </p>
+    <p id="p-3" num="3">Similarly, a bottom lobe <part-num-ref name="bottom lobe">16</part-num-ref>
+ is formed at the bottom, near where the arcuate ri<confidence value="4">b</confidence>
+ <part-num-ref name="arcuate rib">11</part-num-ref>
+ and the generally vertical rib <part-num-ref name="generally vertical rib">12</part-num-ref>
+ intersect. A protrusion or stem <part-num-ref name="protrusion or stem">20</part-num-ref>
+ extends a<confidence value="8">w</confidence>
+ay from the vertical rib <part-num-ref name="vertical rib">12</part-num-ref>
+ and is configured to enter the ear canal. A bore <part-num-ref name="bore">21</part-num-ref>
+ for<confidence value="8">m</confidence>
+ed in the stem <part-num-ref name="stem">20</part-num-ref>
+ transmits sound to a point proximate the eardrum. Acou<confidence value="8">s</confidence>
+tic tubing attaches to the earpiece such that a generally contiguous sound channel is formed by the acoustic tubing and bore <part-num-ref name="acoustic tubing and bore">21.</part-num-ref>
+ On<confidence value="5">e</confidence>
+ <confidence value="88">ex</confidence>
+a<confidence value="888">mpl</confidence>
+e <confidence value="66">of</confidence>
+ <confidence value="5525">such</confidence>
+ <confidence value="56">an</confidence>
+ <confidence value="2222155">earpiGe</confidence>
+ Costa Mesa, CA). Su<confidence value="8">c</confidence>
+h ea<confidence value="8">r</confidence>
+pie<confidence value="8">c</confidence>
+es are also sold by Motorola, In<confidence value="2">c</confidence>
+. of S<confidence value="1">c</confidence>
+haumb<confidence value="1">~</confidence>
+ <confidence value="11">wq</confidence>
+ Please delete paragraph [0043] of the specification as originally filed and substitute therefor the following:    </p>
+    <p id="p-4" num="4">[0043]    Referring now to Figure 3, the earpiece of the present invention can be attached to acoustic tubing <part-num-ref name="present invention can be attached to acoustic tubing">32,</part-num-ref>
+ such as via a barbed fitting <part-num-ref name="barbed fitting">31.</part-num-ref>
+ A strap [[34]] <part-num-ref name="strap [[34]]">3<confidence value="8">3</confidence>
+      </part-num-ref>
+ can be used to secure acoustic tubing <part-num-ref name="can be used to secure acoustic tubing">32</part-num-ref>
+ to a wearer's clothing, such as via a clip <part-num-ref name="clip">34.</part-num-ref>
+ A speaker <part-num-ref name="speaker">35</part-num-ref>
+ converts electrical signals received via electrical cable <part-num-ref name="converts electrical signals received via electrical cable">37</part-num-ref>
+ from a two-way radio <part-num-ref name="two-way radio">41</part-num-ref>
+ into sound that is transmitted to the eardrum via acoustic tubing <part-num-ref name="eardrum via acoustic tubing">32</part-num-ref>
+ and via bore <part-num-ref name="and via bore">21</part-num-ref>
+ (Figures 2A-2C) of the <confidence value="85">AN</confidence>
+ B<confidence value="8">O</confidence>
+NE <confidence value="666">LLP</confidence>
+ earpiece. A plug <part-num-ref name="plug">3<confidence value="5">8</confidence>
+      </part-num-ref>
+ can be used to connect electrical cable <part-num-ref name="can be used to connect electrical cable">37</part-num-ref>
+ to two-way <confidence value="422225">2UITE2</confidence>
+  radio <part-num-ref name="to two-way 2UITE2  radio">41.</part-num-ref>
+    </p>
+    <p id="p-5" num="5">IRVINE CA 92612 <part-num-ref name="">(949)</part-num-ref>
+ 752-7040 <confidence value="885">FAX</confidence>
+ <part-num-ref name="752-7040 FAX">(40<confidence value="66">8)</confidence>
+      </part-num-ref>
+ 392<confidence value="5">-</confidence>
+9262 Page <part-num-ref name="392-9262 Page">2</part-num-ref>
+ of <part-num-ref name="of">11</part-num-ref>
+        App<confidence value="5">l</confidence>
+. No.: 11/236,969     </p>
+  </description>
+</us-patent-application>
+

prior_art/11249093.xml

@@ -0,0 +1,303 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11249093</doc-number>
+        <date>2005-10-11</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">Title:</p>
+    <p id="p-2" num="2">Vial for Test Strips Background of the Invention:</p>
+    <p id="p-3" num="3">Test strips for medical diagnostic purposes are typically supplied and carried in vials from which they are removed as required by a user, for example, when a diagnostic test is to be carried out.</p>
+    <p id="p-4" num="4">Typical types of test strips include those used for measuring analyte concentrations, such as glucose, in a human fluid, such as blood. Test strip vials should be user-friendly and inexpensive to make.</p>
+    <p id="p-5" num="5">Summary of the Invention The present invention provides a vial that has a generally annular open mouthed container that is cut at an oblique angle. At the open mouth, the wall of the generally annular container has a high side and a low side, formed by the oblique cut, where the low side is shorter in length than a diagnostic test strip allowing a user to easily manipulate individual test strips contained in the container. In one embodiment, the present invention provides a diagnostic test strip vial having a container, a lid, and a plurality of diagnostic test strips: (i) wherein the container comprises a generally annular wall terminating at a base and at an open mouth at an end opposite the base, wherein the annular wall is cut at an oblique angle whereby the wall has a high side and a low side at the open mouth, wherein the low side is shorter in length than a diagnostic test strip, (ii) wherein the test strips are disposed in the container, and (iii) wherein when the lid is closed with the container, the test strips are enclosed in the vial. The vial may also optionally comprise a desiccant.</p>
+    <p id="p-6" num="6">Brief Description of the Drawing Fig. 1 is an isometric view of a vial in accordance with the present invention.</p>
+    <p id="p-7" num="7">Fig. 2A is a side elevation view of a vial in accordance with the present invention.</p>
+    <p id="p-8" num="8">Fig. 2B is a side elevation view of a vial in accordance with the present invention.</p>
+    <p id="p-9" num="9">Fig. 2C is<confidence value="5">.</confidence>
+a side elevation view of a vial in accordance with the present invention.    </p>
+    <boundary-data type="header">
+      <confidence value="6">1</confidence>
+    </boundary-data>
+    <p id="p-10" num="10">
+      <page-break num="2"/>
+Fig. 3 is a side elevation view of a vial in accordance with the present invention.    </p>
+    <p id="p-11" num="11">Fig. 4 is a side elevation view of a vial in accordance with the present invention.</p>
+    <p id="p-12" num="12">Fig. 5 is a side elevation view of a vial in accordance with the present invention.</p>
+    <p id="p-13" num="13">Fig. 6 is a side elevation view of a vial in accordance with the present invention.</p>
+    <p id="p-14" num="14">Fig. 7A is a front elevation view of a vial in accordance with the present invention.</p>
+    <p id="p-15" num="15">Fig. 7B is an isometric vial of a vial in accordance with the present invention.</p>
+    <p id="p-16" num="16">Fig. 7C is an isometric vial of a vial in accordance with the present invention.</p>
+    <p id="p-17" num="17">Fig. 8 is a side elevation view of a vial in accordance with the present invention.</p>
+    <p id="p-18" num="18">Detailed Description of the Invention It is often an advantage in the analyte detection industry to provide vials, test strips, and diagnostic meters that are as small as possible to allow a user to carry them with the utmost ease.</p>
+    <p id="p-19" num="19">However, the user of such items may be arthritic or have some other physical impairment which would hinder their ability to remove a single diagnostic test strip from a small vial. This physically impaired user may find it easier to dump the strips contained in the vial into their hand or onto another potentially contaminated surface in order to retrieve a single strip for performing a diagnostic test. Subsequently, the user may return potentially contaminated strips to the vial for storage and for future tests.</p>
+    <p id="p-20" num="20">The present invention provides a user-friendly medical diagnostic test strip vial that allows a user greater access to the test strips contained in it. The vial has a generally annular open mouthed container that is cut at an oblique angle. At the open mouth, the wall of the generally annular container has a high side and a low side, formed by the oblique cut, where the low side is shorter in length than a diagnostic test strip thereby allowing a user to easily manipulate individual test strips therein contained. In one embodiment the diagnostic test strip vial comprises a container, a lid, and a plurality of diagnostic test strips: (i) wherein the container comprises a generally annular wall terminating at a base and at an open mouth at an end opposite the base, wherein the annular wall is cut at an oblique angle whereby the wall has a high side and a low side at the open mouth, wherein the low side is shorter in length than a diagnostic test strip, (ii) wherein the <boundary-data type="header">
+        <confidence value="8">2</confidence>
+      </boundary-data>
+      <page-break num="3"/>
+test strips are disposed in the container, and (iii) wherein when the lid is closed with the container, the test strips are enclosed in the vial. The vial may also optionally comprise a desiccant (e.g. a silica gel or a molecular sieve material such as that made by CSP Technologies, Inc.).    </p>
+    <p id="p-21" num="21">Figure 1 shows an isometric view of an exemplary embodiment of a vial <part-num-ref name="vial">01</part-num-ref>
+ of the present invention with the lid <part-num-ref name="lid">05</part-num-ref>
+ partially removed. The test strips <part-num-ref name="test strips">07</part-num-ref>
+ are disposed in a container <part-num-ref name="container">03</part-num-ref>
+ that has an annular wall <part-num-ref name="annular wall">09</part-num-ref>
+ terminating at a base <part-num-ref name="base">11</part-num-ref>
+ and at an open mouth <part-num-ref name="open mouth">13</part-num-ref>
+ having a high side <part-num-ref name="high side">15</part-num-ref>
+ and a low side <part-num-ref name="low side">17</part-num-ref>
+ that is shorter in length than the test strips <part-num-ref name="test strips">07</part-num-ref>
+ therein contained. The lid <part-num-ref name="lid">05</part-num-ref>
+ is sized to receive the annular wall <part-num-ref name="annular wall">09</part-num-ref>
+ of the container <part-num-ref name="container">03</part-num-ref>
+ that has a sealing ridge <part-num-ref name="sealing ridge">19</part-num-ref>
+ disposed on its outer periphery for sealing the vial <part-num-ref name="vial">01.</part-num-ref>
+ Simplified Figures 2A through <part-num-ref name="vial 01. Simplified Figures 2A through">8</part-num-ref>
+ are provided to detail other embodiments of the vial of the present invention.    </p>
+    <p id="p-22" num="22">Figure 2A depicts an embodiment of the present invention where a diagnostic test strip vial <part-num-ref name="diagnostic test strip vial">101</part-num-ref>
+ has a container <part-num-ref name="container">103,</part-num-ref>
+ a lid <part-num-ref name="lid">105,</part-num-ref>
+ and a plurality of diagnostic test strips <part-num-ref name="plurality of diagnostic test strips">107.</part-num-ref>
+ The container <part-num-ref name="container">103</part-num-ref>
+ has a generally annular wall <part-num-ref name="generally annular wall">109</part-num-ref>
+ terminating at a base <part-num-ref name="base">111</part-num-ref>
+ and at an open mouth <part-num-ref name="open mouth">113</part-num-ref>
+ at an end opposite the base <part-num-ref name="base">111.</part-num-ref>
+ The annular wall <part-num-ref name="annular wall">109</part-num-ref>
+ is cut at an oblique angle <part-num-ref name="oblique angle">114,</part-num-ref>
+ with respect to the axis of the annular wall <part-num-ref name="annular wall">109,</part-num-ref>
+ whereby the wall <part-num-ref name="wall">109</part-num-ref>
+ has a high side <part-num-ref name="high side">115</part-num-ref>
+ and a low side <part-num-ref name="low side">117</part-num-ref>
+ at the open mouth <part-num-ref name="open mouth">113.</part-num-ref>
+ The low side <part-num-ref name="low side">117</part-num-ref>
+ is shorter in length than a diagnostic test strip <part-num-ref name="diagnostic test strip">107</part-num-ref>
+ thereby allowing easy manipulation of individual test strips <part-num-ref name="thereby allowing easy manipulation of individual test strips">107</part-num-ref>
+ contained in the container <part-num-ref name="container">103.</part-num-ref>
+ Figure 2A shows vial <part-num-ref name="container 103. Figure 2A shows vial">101</part-num-ref>
+ wherein the lid <part-num-ref name="lid">105</part-num-ref>
+ is sized to slidably receive the annular wall <part-num-ref name="annular wall">109</part-num-ref>
+ of the container <part-num-ref name="container">103.</part-num-ref>
+ Figure 2A also shows an optional embodiment of the present invention wherein the vial <part-num-ref name="vial">101</part-num-ref>
+ further comprises a seal <part-num-ref name="seal">119.</part-num-ref>
+ Here seal <part-num-ref name="seal 119. Here seal">119</part-num-ref>
+ is a raised circular ridge <part-num-ref name="raised circular ridge">119</part-num-ref>
+ disposed about the outer periphery of wall <part-num-ref name="outer periphery of wall">109.</part-num-ref>
+ Lid <part-num-ref name="outer periphery of wall 109. Lid">105</part-num-ref>
+ may optionally have a corresponding circular depression <part-num-ref name="corresponding circular depression">121,</part-num-ref>
+ on its inner surface, that receives raised ridge <part-num-ref name="corresponding circular depression 121, on its inner surface, that receives raised ridge">119</part-num-ref>
+ so that raised ridge <part-num-ref name="so that raised ridge">119</part-num-ref>
+ may engage the corresponding depression <part-num-ref name="corresponding depression">121</part-num-ref>
+ in a snap fit engagement.    </p>
+    <p id="p-23" num="23">The term <confidence value="5">"</confidence>
+oblique angle" as it is used in the present invention is understood to mean an angle that is not <part-num-ref name="angle that is not">90<confidence value="2">0</confidence>
+      </part-num-ref>
+ with respect to the axis of the annular wall of the container. In Figure 2A, the <boundary-data type="header">
+        <confidence value="8">3</confidence>
+      </boundary-data>
+      <page-break num="4"/>
+annular wall <part-num-ref name="annular wall">109</part-num-ref>
+ is cut at this oblique angle <part-num-ref name="is cut at this oblique angle">114</part-num-ref>
+ so that the annular wall <part-num-ref name="annular wall">109</part-num-ref>
+ has a high side <part-num-ref name="high side">115</part-num-ref>
+ and a low side <part-num-ref name="low side">117</part-num-ref>
+ at the open mouth <part-num-ref name="open mouth">113</part-num-ref>
+ of the container <part-num-ref name="container">103.</part-num-ref>
+ In a preferred embodiment the oblique angle <part-num-ref name="oblique angle">
+        <confidence value="8">1</confidence>
+14      </part-num-ref>
+ is in the range of between 10<confidence value="1">°</confidence>
+ and <part-num-ref name="range of between 10° and">80<confidence value="2">0</confidence>
+,      </part-num-ref>
+ more preferably between <part-num-ref name="range of between 10° and 800, more preferably between">30<confidence value="2">0</confidence>
+      </part-num-ref>
+ and <part-num-ref name="and">60<confidence value="8">,</confidence>
+      </part-num-ref>
+ and still more preferably between <part-num-ref name="and 60, and still more preferably between">40<confidence value="2">0</confidence>
+      </part-num-ref>
+ and <part-num-ref name="and">50<confidence value="2">0</confidence>
+      </part-num-ref>
+ with respect to the axis of the annular wall of the container.    </p>
+    <p id="p-24" num="24">The oblique cut of the annular wall preferably extends through the entire wall. However in another embodiment the annular wall is partially cut at the oblique angle. Figure 2B shows an embodiment of the present invention where a diagnostic test strip vial <part-num-ref name="diagnostic test strip vial">1101</part-num-ref>
+ has a container <part-num-ref name="container">1103,</part-num-ref>
+ a lid <part-num-ref name="lid">1105,</part-num-ref>
+ and a plurality of diagnostic test strips <part-num-ref name="plurality of diagnostic test strips">1107.</part-num-ref>
+ The container <part-num-ref name="container">1103</part-num-ref>
+ has a generally annular wall <part-num-ref name="generally annular wall">1109</part-num-ref>
+ terminating at a base <part-num-ref name="base">1111</part-num-ref>
+ and at an open mouth <part-num-ref name="open mouth">1113</part-num-ref>
+ at an end opposite the base <part-num-ref name="base">1111.</part-num-ref>
+ Here, annular wall <part-num-ref name="base 1111. Here, annular wall">1109</part-num-ref>
+ is partially cut at an oblique angle <part-num-ref name="oblique angle">1114,</part-num-ref>
+ with respect to the axis of the annular wall <part-num-ref name="annular wall">1109,</part-num-ref>
+ whereby the wall <part-num-ref name="wall">1109</part-num-ref>
+ has a high side <part-num-ref name="high side">1115</part-num-ref>
+ and a low side <part-num-ref name="low side">1117</part-num-ref>
+ at the open mouth <part-num-ref name="open mouth">1113.</part-num-ref>
+ The low side <part-num-ref name="low side">1117</part-num-ref>
+ is shorter in length than a diagnostic test strip <part-num-ref name="diagnostic test strip">1107</part-num-ref>
+ thereby allowing easy manipulation of individual test strips <part-num-ref name="thereby allowing easy manipulation of individual test strips">1107</part-num-ref>
+ contained in the vial <part-num-ref name="vial">1103.</part-num-ref>
+ In the present embodiment wherein the annular wall <part-num-ref name="annular wall">1109</part-num-ref>
+ is partially cut at an oblique angle <part-num-ref name="oblique angle">1114</part-num-ref>
+ it is preferred that the annular wall <part-num-ref name="annular wall">1109</part-num-ref>
+ is cut so that at least 25%, more preferably at least 50%, for example 75% of the circumference of the annular wall <part-num-ref name="annular wall">1109</part-num-ref>
+ at its high side <part-num-ref name="at its high side">1115</part-num-ref>
+ is removed by the oblique cut.    </p>
+    <p id="p-25" num="25">The low side of the annular wall of the container is shorter in length, from the base to the open mouth, than a diagnostic test strip contained in the vial. In a preferred embodiment the height of the low side of the annular wall, when measured from the base, is greater than the major diameter of the annular wall and more preferably greater than twice the major diameter of the annular wall.</p>
+    <p id="p-26" num="26">When the oblique angle is small, for example in a range of between <part-num-ref name="range of between">10<confidence value="2">0</confidence>
+      </part-num-ref>
+ and <part-num-ref name="and">30<confidence value="2">0</confidence>
+      </part-num-ref>
+ it is preferred that the height of the low side of the annular wall be at least twice, and more preferably more than triple, the major diameter of the annular wall so as to prevent test strips from unwantedly tipping out of an open container. In another embodiment it is preferred that the height of the low side of the annular wall be between 50% and 80%, and more preferably between 60% and 75% <boundary-data type="header">
+        <confidence value="8">4</confidence>
+      </boundary-data>
+      <page-break num="5"/>
+of the length of a diagnostic test strip contained in the vial.    </p>
+    <p id="p-27" num="27">The term "slidably receive" is used in reference relative to the sizing of the annular wall of the container and the lid. As used in the specification and claims of this application "slidably receive" means that the container fits within the lid or vice versa and is removable and replaceable by the user. In some embodiments, the lid fits onto the container so that the fit between the lid and the container is sufficiently tight to prevent a test strip from fitting between the lid and the container. In a preferred embodiment the lid slides onto or into the container with minimal force, for example the force applied by one hand of the user, and when the lid is closed to the container the lid remains closed to the container when the vial is inverted and the lid is subjected to the force of gravity. In some embodiments, for example in the absence of a seal as depicted in Figure 2B, the fit between the lid and the container may be sufficiently tight so as to ensure a stable humidity environment inside the vial.</p>
+    <p id="p-28" num="28">Figure 2C shows a further embodiment of the invention. In this figure, vial <part-num-ref name="invention. In this figure, vial">201</part-num-ref>
+ has a lid <part-num-ref name="lid">205</part-num-ref>
+ that is sized to slidably receive the annular wall <part-num-ref name="annular wall">209</part-num-ref>
+ of the container <part-num-ref name="container">203.</part-num-ref>
+ Figure 2C also shows an embodiment of the present invention wherein the vial further comprises a seal <part-num-ref name="seal">219.</part-num-ref>
+ Seal <part-num-ref name="seal 219. Seal">219</part-num-ref>
+ is a raised circular ridge <part-num-ref name="raised circular ridge">219</part-num-ref>
+ disposed on the inside of lid <part-num-ref name="inside of lid">205.</part-num-ref>
+ The outer surface of annular wall <part-num-ref name="outer surface of annular wall">209</part-num-ref>
+ of container <part-num-ref name="of container">203</part-num-ref>
+ may optionally have a corresponding circular depression <part-num-ref name="corresponding circular depression">221</part-num-ref>
+ that receives raised circular ridge <part-num-ref name="that receives raised circular ridge">219</part-num-ref>
+ so that raised ridge <part-num-ref name="so that raised ridge">219</part-num-ref>
+ may engage the corresponding depression <part-num-ref name="corresponding depression">221</part-num-ref>
+ in a snap fit engagement.    </p>
+    <p id="p-29" num="29">The term "snap fit engagement" is herein understood to mean the sealing interaction between the raised sealing ridge and the corresponding depression. For example, in the embodiments where a raised sealing ridge is disposed on the inside of the lid and a corresponding depression is disposed on the outer surface of the annular wall of the container and where the lid is being closed with the container, the raised sealing ridge of the lid slides along the annular wall of the container until it reaches the corresponding depression where it is received. In other embodiments where a raised sealing ridge is disposed at the open mouth of the container and <boundary-data type="header">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+      <page-break num="6"/>
+where the lid has a corresponding depression disposed on its inner side, the lid snaps directly onto the container and the contents of the vial are sealed from the surrounding atmosphere. In a preferred embodiment when the raised ridge is received by the corresponding depression a noise is made by the interaction, for example a "click", to notify the user that the vial is sealed.    </p>
+    <p id="p-30" num="30">In the embodiments shown in Figures 2A, 2<confidence value="5">B</confidence>
+, and 2C the annular wall <part-num-ref name="annular wall">109,</part-num-ref>
+ <part-num-ref name="annular wall 109,">1109,</part-num-ref>
+ <part-num-ref name="annular wall 109, 1109,">209</part-num-ref>
+ is smooth on the inside, but may have step region <part-num-ref name="inside, but may have step region">1009</part-num-ref>
+ on the outside so that the combination of container and lid is smooth. This step however is optional, and sealing may occur through the interaction of the ridge <part-num-ref name="ridge">119,</part-num-ref>
+ <part-num-ref name="ridge 119,">219</part-num-ref>
+ and depression <part-num-ref name="and depression">121,</part-num-ref>
+ <part-num-ref name="and depression 121,">221</part-num-ref>
+ as shown in Figures <confidence value="2">1</confidence>
+A and <part-num-ref name="as shown in Figures 1A and">2.</part-num-ref>
+    </p>
+    <p id="p-31" num="31">Figure 3 depicts another embodiment of the vial of the present invention. In this Figure, the annular wall <part-num-ref name="annular wall">309</part-num-ref>
+ of container <part-num-ref name="of container">303</part-num-ref>
+ of vial <part-num-ref name="of vial">301</part-num-ref>
+ is sized to slidably receive lid <part-num-ref name="is sized to slidably receive lid">305.</part-num-ref>
+ Figure 3 also shows an optional <confidence value="22222222222">embo&lt;liment</confidence>
+ of the present invention wherein the vial <part-num-ref name="vial">301</part-num-ref>
+ further comprises a seal <part-num-ref name="seal">319.</part-num-ref>
+ Here seal <part-num-ref name="seal 319. Here seal">319</part-num-ref>
+ is a raised circular ridge <part-num-ref name="raised circular ridge">319</part-num-ref>
+ disposed on the outside of lid <part-num-ref name="outside of lid">305.</part-num-ref>
+ The inner surface of annular wall <part-num-ref name="inner surface of annular wall">309</part-num-ref>
+ of container <part-num-ref name="of container">303</part-num-ref>
+ may optionally have a corresponding circular depression <part-num-ref name="corresponding circular depression">321</part-num-ref>
+ that receives raised circular ridge <part-num-ref name="that receives raised circular ridge">319</part-num-ref>
+ so that raised ridge <part-num-ref name="so that raised ridge">319</part-num-ref>
+ may engage the corresponding depression <part-num-ref name="corresponding depression">321</part-num-ref>
+ in a snap fit engagement.    </p>
+    <p id="p-32" num="32">Figure 4 depicts yet another embodiment of the vial of the present invention. In this Figure, the annular wall <part-num-ref name="annular wall">409</part-num-ref>
+ of container <part-num-ref name="of container">403</part-num-ref>
+ of vial <part-num-ref name="of vial">401</part-num-ref>
+ is sized to slidably receive lid <part-num-ref name="is sized to slidably receive lid">405.</part-num-ref>
+ Figure 4 also shows an optional embodiment of the present invention wherein the vial further comprises a seal <part-num-ref name="seal">419.</part-num-ref>
+ Here seal <part-num-ref name="seal 419. Here seal">419</part-num-ref>
+ is a raised circular ridge <part-num-ref name="raised circular ridge">419</part-num-ref>
+ disposed on the inner surface of wall <part-num-ref name="inner surface of wall">409.</part-num-ref>
+ The outer surface of lid <part-num-ref name="outer surface of lid">405</part-num-ref>
+ may optionally have a corresponding circular depression <part-num-ref name="corresponding circular depression">421</part-num-ref>
+ that receives raised circular ridge <part-num-ref name="that receives raised circular ridge">419</part-num-ref>
+ so that raised ridge <part-num-ref name="so that raised ridge">419</part-num-ref>
+ may engage the corresponding depression 42<confidence value="2">-</confidence>
+1 in a snap fit engagement.    </p>
+    <p id="p-33" num="33">Figure 5 depicts another embodiment for a vial <part-num-ref name="vial">501</part-num-ref>
+ of the present invention where lid <part-num-ref name="present invention where lid">505</part-num-ref>
+ is pivotally connected to the container <part-num-ref name="container">503.</part-num-ref>
+ The pivotal connection <part-num-ref name="pivotal connection">504</part-num-ref>
+ here is living hinge <part-num-ref name="here is living hinge">504.</part-num-ref>
+    </p>
+    <p id="p-34" num="34">This living hinge 504 may be made of a thermoplastic resin. The pivotal connection <part-num-ref name="pivotal connection">504</part-num-ref>
+ may <boundary-data type="header">
+        <confidence value="8">6</confidence>
+      </boundary-data>
+      <page-break num="7"/>
+also be a mechanical hinge or other type of pivotal connection that is sized so that the lid <part-num-ref name="lid">505</part-num-ref>
+ may be bent back away from container <part-num-ref name="may be bent back away from container">503.</part-num-ref>
+ Lid <part-num-ref name="may be bent back away from container 503. Lid">505</part-num-ref>
+ also has a thumb lip <part-num-ref name="thumb lip">506</part-num-ref>
+ to give a user the ability to easily remove the lid from the container <part-num-ref name="container">503</part-num-ref>
+ thereby opening the vial <part-num-ref name="vial">501.</part-num-ref>
+ In the present Figure although lid <part-num-ref name="present Figure although lid">505</part-num-ref>
+ has desiccant <part-num-ref name="has desiccant">508</part-num-ref>
+ disposed therein, the desiccant <part-num-ref name="desiccant">508</part-num-ref>
+ may also or alternatively be disposed in container <part-num-ref name="may also or alternatively be disposed in container">503.</part-num-ref>
+    </p>
+    <p id="p-35" num="35">It is often preferred that medical diagnostic test strips be stored in a stable environment where there is reduced moisture as compared to the normal atmosphere. To maintain this reduced moisture environment it is often desired that the space within the container is sealed from the outside atmosphere using an "air-tight" seal that seals the lid to the container. In addition to sealing the container from the surrounding environment a desiccant may be employed as depicted in Figure 5. The desiccant may be located in the container, in the lid, or in both the container and lid such that it is in contact with the environment within the vial. Non-limiting examples of suitable desiccants include silica gel and molecular sieve material produced by CSP Technologies, Inc.</p>
+    <p id="p-36" num="36">In accordance with the present invention, types of seals are not limited and may include gaskets, raised sealing ridges, and stoppers among other seals. In a preferred embodiment, the vial comprises a seal disposed on the lid, the container, or both. In a further embodiment, this seal is a raised sealing ridge disposed on the lid, the container, or both and optionally further comprises a corresponding depression located on the opposite surface for snap fit engagement with the sealing ridge where the raised ridge snaps into the corresponding depression when the lid is closed with the container. The raised sealing ridge and the optional corresponding depression may be circular or oval in nature depending on the shape of the annular wall.</p>
+    <p id="p-37" num="37">A circular sealing ridge is preferred in some embodiments because it provides a more rigid seal as compared to an oval sealing ridge and is able to better withstand deformation pressures thereby providing a better seal. As depicted in Figures <part-num-ref name="better seal. As depicted in Figures">6,</part-num-ref>
+ <part-num-ref name="better seal. As depicted in Figures 6,">7,</part-num-ref>
+ and <part-num-ref name="better seal. As depicted in Figures 6, 7, and">8</part-num-ref>
+ in preferred embodiments the raised sealing ridge is circular and may be employed even if the annular wall of the container is <boundary-data type="header">
+        <confidence value="8">7</confidence>
+      </boundary-data>
+      <page-break num="8"/>
+oval by disposing the ridge at an oblique angle with respect to the axis of the annular wall.    </p>
+    <p id="p-38" num="38">Figure 6 depicts a vial <part-num-ref name="vial">601</part-num-ref>
+ of the present invention wherein the annular wall <part-num-ref name="annular wall">609</part-num-ref>
+ of the container <part-num-ref name="container">603</part-num-ref>
+ is oval or elliptical shape. A raised sealing ridge <part-num-ref name="raised sealing ridge">619</part-num-ref>
+ is disposed at an oblique angle <part-num-ref name="oblique angle">614,</part-num-ref>
+ with respect to the axis of the annular wall <part-num-ref name="annular wall">609,</part-num-ref>
+ on the annular wall <part-num-ref name="annular wall">609.</part-num-ref>
+ The oblique angle <part-num-ref name="oblique angle">614</part-num-ref>
+ is selected so that raised sealing ridge <part-num-ref name="is selected so that raised sealing ridge">619</part-num-ref>
+ is circular. An optional corresponding circular depression <part-num-ref name="optional corresponding circular depression">621</part-num-ref>
+ disposed at oblique angle <part-num-ref name="disposed at oblique angle">614</part-num-ref>
+ may also be present on the inner surface of the lid wherein the raised circular sealing ridge <part-num-ref name="raised circular sealing ridge">619</part-num-ref>
+ may engage the corresponding circular depression <part-num-ref name="corresponding circular depression">621</part-num-ref>
+ for snap fit engagement. Container <part-num-ref name="for snap fit engagement. Container">603</part-num-ref>
+ also has step region <part-num-ref name="also has step region">1009</part-num-ref>
+ on the outside of its annular wall <part-num-ref name="outside of its annular wall">609</part-num-ref>
+ so that the combination of container <part-num-ref name="combination of container">603</part-num-ref>
+ and lid is smooth. This step <part-num-ref name="and lid is smooth. This step">1009</part-num-ref>
+ however is optional.    </p>
+    <p id="p-39" num="39">Figure 7A shows a front view of vial <part-num-ref name="front view of vial">701</part-num-ref>
+ having a lid <part-num-ref name="lid">705</part-num-ref>
+ and a container <part-num-ref name="container">703</part-num-ref>
+ with an oval annular wa<confidence value="8">l</confidence>
+l <part-num-ref name="oval annular wall">709.</part-num-ref>
+ Container <part-num-ref name="oval annular wall 709. Container">703</part-num-ref>
+ comprises a circular raised sealing ridge <part-num-ref name="circular raised sealing ridge">719</part-num-ref>
+ disposed at an oblique angle with respect to the axis of the annular wall <part-num-ref name="annular wall">709.</part-num-ref>
+ Figures 7B and 7C show isometric views of vial <part-num-ref name="annular wall 709. Figures 7B and 7C show isometric views of vial">701</part-num-ref>
+ shown in Figure 7A. Figure 8 shows a side elevation view of closed vial <part-num-ref name="side elevation view of closed vial">801</part-num-ref>
+ with oval annular wall <part-num-ref name="with oval annular wall">809.</part-num-ref>
+ Container <part-num-ref name="with oval annular wall 809. Container">803</part-num-ref>
+ has a circular sealing ridge that is in sealing engagement with lid <part-num-ref name="circular sealing ridge that is in sealing engagement with lid">805.</part-num-ref>
+    </p>
+    <p id="p-40" num="40">The generally annular wall of the container may be circular, elliptical or oval in shape. It is sometimes preferred that the overall vial shape and also the shape of the annular wall be oval in nature so that the vial may easily fit into a carrying case for medical supplies to be carried by a user. It is also often preferred that medical test strip vials be camouflaged or appear to be something other than what they are. For example, a user may desire to have the test strip vial be in the shape of lipstick, lip balm, eye liner, a pen, or some other indiscreet object in order to downplay what is therein contained. Thus variations of the shape of the vial and its lid and/or container of the present invention are contemplated herein and do not depart from the scope of <confidence value="6">.</confidence>
+    </p>
+    <p id="p-41" num="41">the present invention.</p>
+    <boundary-data type="header">
+      <confidence value="8">8</confidence>
+    </boundary-data>
+    <p id="p-42" num="42">
+      <page-break num="9"/>
+The material and methods used to make the vials of the present invention are not particularly limited. However, for ease of manufacture and the costs associated therewith, injection molded thermoplastic resin is often preferred.    </p>
+    <boundary-data type="header">
+      <confidence value="8">9</confidence>
+    </boundary-data>
+  </description>
+</us-patent-application>
+

prior_art/11250353.xml

@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11250353</doc-number>
+        <date>2008-12-31</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">Attorney Docket No. 030101 </p>
+    <heading id="h-1">
+      <confidence value="5">I</confidence>
+N THE SPECIFICATION    </heading>
+    <p id="p-2" num="2">Please amend the first paragraph of the specification as presented below.</p>
+    <p id="p-3" num="3">[0001<confidence value="5">]</confidence>
+ The present Application for Patent is a Continuation<confidence value="52">of</confidence>
+ and claims priority<confidence value="544">-4o</confidence>
+ from, U.<confidence value="88">S.</confidence>
+    </p>
+    <p id="p-4" num="4">Patent <confidence value="5555525666">Applicatio</confidence>
+  <confidence value="66">No</confidence>
+  <confidence value="661562666">10/674,03</confidence>
+  No. 7,002,900, issued February 21, 2006 and entitled     </p>
+    <heading id="h-2">"TRANSMIT DIVERSITY PROCESS<confidence value="8">I</confidence>
+NG FOR A MULTI-ANTENNA COMMUNICATION    </heading>
+    <p id="p-5" num="5">SYSTEM"                                           , which claims the benefit of priorit<confidence value="8">y</confidence>
+ from U.S. Provisional Patent Application Serial No. 60/421,309, filed October <part-num-ref name="benefit of priority from U.S. Provisional Patent Application Serial No. 60/421,309, filed October">25,</part-num-ref>
+ <part-num-ref name="benefit of priority from U.S. Provisional Patent Application Serial No. 60/421,309, filed October 25,">2002</part-num-ref>
+ and entitled "MIMO WLAN SYSTEM," both of which are assigned to the assignee hereof and hereby expressly incorporated by reference herein.    </p>
+    <p id="p-6" num="6">-2- </p>
+  </description>
+</us-patent-application>
+

prior_art/11252681.xml

@@ -0,0 +1,52 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11252681</doc-number>
+        <date>2010-04-02</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">Amendments to the Specification Please replace the corresponding (numbered) pending paragraphs with the following (numbered) replacement paragraphs:</p>
+    <p id="p-2" num="2">[0003] <confidence value="5">I</confidence>
+ntaglio printing is a well known printing method using a printing plate having recesses formed in printing image areas with respect to non-printing image areas. After the entire intaglio printing plate is filled with a highly viscous ink, the ink on the non- printing image areas is wiped off to leave the ink only in the printing image areas.    </p>
+    <p id="p-3" num="3">Thereafter, a web or substrate such as a paper sheet is forced directly to the printing plate under heavy pressure to transfer the ink remaining in the printing image areas onto the paper. Line-engraved intaglio printing is typically used for printing security documents, such as banknotes, and uses printing cylinders having engravings therein in which intaglio printing inks have been deposited. The highly viscous paste-like intaglio inks used in such printing are substantially different in nature from inks used in other forms of printing such as gravure, offset and ink-jet printing. To varying degrees of success, attempts have been made to improve the dispersibility and chemical resistance of the paste-like intaglio inks; for example U.S. Pat. No. 6,833,395 in the name of Rygas et al.</p>
+    <p id="p-4" num="4">assigned to the Canadian Bank Note Company, Limited (Ottawa, <confidence value="55222">Caif-</confidence>
+   Canada) attempts to provide a solution to this problem.    </p>
+    <p id="p-5" num="5">[0005] As of late there has been considerable interest in obtaining special <confidence value="5665224">affec-s</confidence>
+ effects by magnetically orienting magnetic flakes, that is, flakes that will align in a magnetic field, in a predetermined manner, to follow the field lines. Examples are found in U.S.    </p>
+    <p id="p-6" num="6">Pat. No. 6,902,807 in the names of Argoitia et al., entitled Alignable diffractive pigment flakes, and U.S. Pat. No. 6,808,806 in the names of Phillips et al., entitled Methods for producing imaged coated articles by using magnetic pigments; Phillips et al., disclose orienting magnetically orientable flakes in applied magnetic fields to achieve special <confidence value="777776">affect</confidence>
+s effects; both of these patents are incorporated herein by reference.    </p>
+    <boundary-data type="header">
+      <confidence value="8">2</confidence>
+    </boundary-data>
+    <p id="p-7" num="7">
+      <page-break num="2"/>
+[0012] It is therefore an object of this invention to provide a method and apparatus that will allow these highly viscous paste-like inks to be utilized in the printing of special effect pigments wherein the pigments can be aligned in preferred orientations using a magnetic field so as to yield desired illusionary aff<confidence value="888">ect</confidence>
+s effects.    </p>
+    <p id="p-8" num="8">[0040] Refe<confidence value="66">rr</confidence>
+ing now to FIG. 5, a sheet of paper <part-num-ref name="sheet of paper">4</part-num-ref>
+ is printed between the rollers <part-num-ref name="rollers">1</part-num-ref>
+ and <part-num-ref name="and">3</part-num-ref>
+ and moves to the magnetic stage <part-num-ref name="magnetic stage">7.</part-num-ref>
+ Heating elements <part-num-ref name="magnetic stage 7. Heating elements">14</part-num-ref>
+ are mounted above the magnetic stage <part-num-ref name="magnetic stage">7</part-num-ref>
+ at the distance from 0.0625" to <confidence value="666">1.5</confidence>
+". The elements <part-num-ref name="elements">14</part-num-ref>
+ heat the paper and the ink to reduce the ink viscosity to the level providing alignment of magnetic particles in the field of the stage <part-num-ref name="stage">7.</part-num-ref>
+ The elements <part-num-ref name="elements">14</part-num-ref>
+ are usually longer t<confidence value="265">hat</confidence>
+ than the stage <part-num-ref name="stage">7</part-num-ref>
+ because they need to start to heat the ink before it comes to the stage <part-num-ref name="stage">7.</part-num-ref>
+ The UV-light source <part-num-ref name="UV-light source">13</part-num-ref>
+ is installed shortly after magnetic stage <part-num-ref name="is installed shortly after magnetic stage">7</part-num-ref>
+ in order to fix position of already aligned particles in the volume of the ink and to cure the ink vehicle.    </p>
+    <boundary-data type="header">
+      <confidence value="8">3</confidence>
+    </boundary-data>
+  </description>
+</us-patent-application>
+

prior_art/11262454.xml

@@ -0,0 +1,378 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11262454</doc-number>
+        <date>2005-10-28</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <boundary-data type="header">67,097-531; <confidence value="56">ID</confidence>
+F ID-<confidence value="4">1</confidence>
+103-US    </boundary-data>
+    <heading id="h-1">MECHANICAL FACE SEAL STOP PIN</heading>
+    <heading id="h-2">BACKGROUND OF THE INVENTION</heading>
+    <p id="p-1" num="1">[0001]   This invention relates to mechanical face seals and, more particularly, to an arrangement and method for establishing a range of movement of a mechanical face seal.</p>
+    <p id="p-2" num="2">[0002]   Conventional mechanical face seals are used in rotating equipment, such as gas turbine engines, to provide a seal between regions of high and low fluid pressure and temperature. For example, mechanical face seals are used for sealing a rotating shaft on a pump, compressor, agitator, gas turbine, or other rotating equipment. In gas turbine engines, mechanical face seals are used to prevent hot, high pressure air from entering a bearing compartment that operates at a lower pressure and temperature.</p>
+    <p id="p-3" num="3">[0003]   A conventional metal-backed face seal arrangement for a gas turbine engine includes an annular graphitic carbon ring secured to a rotationally static, axially translatable, annular metal seal housing. A seal seat is affixed to a rotatable engine main shaft and positioned axially adjacent to the graphitic carbon ring. A nose of the annular graphitic carbon ring is urged into contact with the seal seat by a combination of spring forces acting on the seal housing and the net resultant of axially opposing fluid pressure forces. The contact between the nose and the seal seat resists fluid leakage across the seal arrangement in the radial direction.</p>
+    <p id="p-4" num="4">[0004]   Typically, a conventional graphitic carbon ring mechanical face seal arrangement includes between six and twelve spring guides affixed to a non-rotatable support or seal housing. The seal housing axially translates along the spring guides. A coil spring is arranged coaxially about each spring guide between the seal housing and the support to provide a bias force that urges the graphitic carbon ring into contact with the seal seat.</p>
+    <p id="p-5" num="5">Disadvantageously, the six to twelve spring guides and six to twelve corresponding coil springs are time consuming to install and add expense to the arrangement. Functionally, the seal seat limits movement of the seal arrangement in one axial direction, however, only the support limits movement in the opposite direction. This may undesirably damage the support and seal arrangement, or over-compress and over-stress one or more of the coil springs.</p>
+    <boundary-data type="header">
+      <confidence value="8">1</confidence>
+    </boundary-data>
+    <boundary-data type="header">67,097-531; <confidence value="56">ID</confidence>
+F ID-<confidence value="4">1</confidence>
+103-US    </boundary-data>
+    <p id="p-6" num="6">
+      <page-break num="2"/>
+[0005]   Accordingly, there is a need for a simplified and robust gas turbine engine shaft seal arrangement having a limited range of movement to protect the seal arrangement from interfering with a support or over-compressing a spring.    </p>
+    <heading id="h-3">SUMMARY OF THE INVENTION</heading>
+    <p id="p-7" num="7">[0006<confidence value="2">]</confidence>
+   A gas turbine engine mechanical face seal arrangement according to the present invention includes a seal member having an annular seal element for sealing against a rotatable seal surface. The seal member includes guide slots that cooperate with a guide member to establish a direction of seal member movement. The guide member includes stops to establish a range of movement of the seal member along the direction of seal member movement. The limited range of motion of the seal member protects a bias spring from being over-compressed or over-stressed.    </p>
+    <p id="p-8" num="8">[0007]   One exemplary gas turbine engine mechanical face seal arrangement includes a spacer between the seal member and at least one of the guide members. The spacers provide anti-rotation of the seal member, axial travel guidance of the seal member and reduces friction and wear between the seal member and the guide members.</p>
+    <p id="p-9" num="9">[0008]   Accordingly, the disclosed examples provide a gas turbine engine mechanical face seal arrangement that provides a limited range of movement to protect the seal arrangement from over-compression and interfering with a support, as well as, to provide proper orientation, guidance and anti-rotation.</p>
+    <heading id="h-4">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
+    <p id="p-10" num="10">[0009]   The various features and advantages of this invention will become apparent to those skilled in the art from the following detailed description of the currently preferred embodiment. The drawings that accompany the detailed description can be briefly described as follows.</p>
+    <p id="p-11" num="11">[0010]   Figure 1 shows an example gas turbine engine.</p>
+    <p id="p-12" num="12">[0011]   Figure 2 shows a more detailed view of the bearing arrangement shown in Figure 1, including a seal arrangement.</p>
+    <p id="p-13" num="13">[0012]   Figure 3 shows an isometric projected view of an example guide member of the seal arrangement shown in Figure 2.</p>
+    <boundary-data type="header">
+      <confidence value="8">2</confidence>
+    </boundary-data>
+    <boundary-data type="header">67,097-531; <confidence value="66">ID</confidence>
+F ID-<confidence value="4">1</confidence>
+103-US    </boundary-data>
+    <p id="p-14" num="14">
+      <page-break num="3"/>
+[0013]   Figure 4 shows an annular spring biasing a seal member of the seal arrangement of Figure 2 into engagement with a retaining collar stop.    </p>
+    <p id="p-15" num="15">[0014]   Figure 5 shows the seal member of Figure 4 in a retracted position, compressing the annular spring and engaged with a stop.</p>
+    <p id="p-16" num="16">[0015]   Figure 6 shows an axial view of example guide member circumferential locations of the seal arrangement shown in Figure 2.</p>
+    <heading id="h-5">DETAILED DESCRIPTION OF T<confidence value="5">H</confidence>
+E PREFERRED EMBODIMENT    </heading>
+    <p id="p-17" num="17">[0016]   Figure 1 illustrates selected portions of an example rotational assembly <part-num-ref name="example rotational assembly">10,</part-num-ref>
+ such as a gas turbine engine for an aircraft. In this example, the rotational assembly <part-num-ref name="rotational assembly">10</part-num-ref>
+ includes a compressor section <part-num-ref name="compressor section">12,</part-num-ref>
+ a combustor section <part-num-ref name="combustor section">14,</part-num-ref>
+ and a turbine section <part-num-ref name="turbine section">16.</part-num-ref>
+ The rotational assembly <part-num-ref name="rotational assembly">10</part-num-ref>
+ operates in a known manner, feeding compressed air from the compressor section <part-num-ref name="compressor section">12</part-num-ref>
+ to the combustor section <part-num-ref name="combustor section">14.</part-num-ref>
+ The compressed air is mixed with fuel and reacts to produce a flow of hot gases <part-num-ref name="flow of hot gases">18.</part-num-ref>
+ The turbine section <part-num-ref name="turbine section">16</part-num-ref>
+ transforms the flow of hot gases <part-num-ref name="flow of hot gases">18</part-num-ref>
+ into mechanical energy to rotationally drive a shaft <part-num-ref name="shaft">20,</part-num-ref>
+ such as a turbine engine main shaft. The shaft <part-num-ref name="shaft">20</part-num-ref>
+ is coupled with the turbine section <part-num-ref name="turbine section">16</part-num-ref>
+ and the compressor section <part-num-ref name="compressor section">12</part-num-ref>
+ such that the turbine section <part-num-ref name="turbine section">16</part-num-ref>
+ drives the compressor section <part-num-ref name="compressor section">12.</part-num-ref>
+ An exhaust nozzle <part-num-ref name="exhaust nozzle">22</part-num-ref>
+ directs the hot gases <part-num-ref name="hot gases">18</part-num-ref>
+ out of the rotational assembly <part-num-ref name="rotational assembly">10.</part-num-ref>
+ An annular, non-rotatable case <part-num-ref name="annular, non-rotatable case">24</part-num-ref>
+ provides support for the shaft <part-num-ref name="shaft">20</part-num-ref>
+ on a bearing arrangement <part-num-ref name="bearing arrangement">26,</part-num-ref>
+ such as a No.1 bearing.    </p>
+    <p id="p-18" num="18">[0017]   Figure 2 shows a more detailed view of the bearing arrangement <part-num-ref name="bearing arrangement">26</part-num-ref>
+ shown in Figure 1. The bearing arrangement <part-num-ref name="bearing arrangement">26</part-num-ref>
+ includes a bearing <part-num-ref name="bearing">36</part-num-ref>
+ mounted between the case <part-num-ref name="case">24</part-num-ref>
+ and the shaft <part-num-ref name="shaft">20</part-num-ref>
+ that provides support for the shaft <part-num-ref name="shaft">20,</part-num-ref>
+ which rotates about a central axis A.    </p>
+    <p id="p-19" num="19">A seal arrangement 38 provides a fluid restriction between a low pressure and temperature (L) bearing chamber <part-num-ref name="low pressure and temperature (L) bearing chamber">40</part-num-ref>
+ and hot, high pressure (H) region outside of the bearing chamber <part-num-ref name="bearing chamber">40.</part-num-ref>
+    </p>
+    <p id="p-20" num="20">[0018]   A support wall <part-num-ref name="support wall">42</part-num-ref>
+ includes circumferentially spaced openings <part-num-ref name="includes circumferentially spaced openings">44.</part-num-ref>
+ Each of the guide members <part-num-ref name="guide members">46,</part-num-ref>
+ such as a stop pin, includes a head <part-num-ref name="head">45</part-num-ref>
+ that engages a corresponding opening <part-num-ref name="corresponding opening">44</part-num-ref>
+ of the support wall <part-num-ref name="support wall">42</part-num-ref>
+ to secure the guide member <part-num-ref name="guide member">46</part-num-ref>
+ to the support wall <part-num-ref name="support wall">42.</part-num-ref>
+ In the illustrated example, an interference fit between the head <part-num-ref name="head">45</part-num-ref>
+ and the corresponding opening <part-num-ref name="corresponding opening">44</part-num-ref>
+ provides a secure connection.    </p>
+    <p id="p-21" num="21">[0019]   Each guide member 46 includes a base section <part-num-ref name="base section">48</part-num-ref>
+ and a neck section <part-num-ref name="neck section">50.</part-num-ref>
+    </p>
+    <p id="p-22" num="22">In this example, both the base section <part-num-ref name="base section">48</part-num-ref>
+ and the neck section <part-num-ref name="neck section">50</part-num-ref>
+ are cylindrical and have <boundary-data type="header">
+        <confidence value="8">3</confidence>
+      </boundary-data>
+      <page-break num="4"/>
+      <boundary-data type="header">67,097-531; IDF ID-<confidence value="4">1</confidence>
+103-US      </boundary-data>
+respective diameters D<confidence value="4">1</confidence>
+ and D2. The diameter D<confidence value="4">1</confidence>
+ of the base section <part-num-ref name="base section">48</part-num-ref>
+ is larger than the diameter D2 of the neck section <part-num-ref name="neck section">50.</part-num-ref>
+ A distal end <part-num-ref name="distal end">52</part-num-ref>
+ of the neck section <part-num-ref name="neck section">50</part-num-ref>
+ receives a retaining collar <part-num-ref name="retaining collar">54.</part-num-ref>
+ The distal end <part-num-ref name="distal end">52</part-num-ref>
+ and retaining collar <part-num-ref name="and retaining collar">54</part-num-ref>
+ have respective openings 55a and 55b and a fastener F (Figure <part-num-ref name="fastener F (Figure">3)</part-num-ref>
+ is disposed through the openings 55b and 55a to secure the retaining collar <part-num-ref name="retaining collar">54</part-num-ref>
+ on the distal end <part-num-ref name="distal end">52.</part-num-ref>
+ A spacer sleeve <part-num-ref name="spacer sleeve">57</part-num-ref>
+ mounts on the neck section <part-num-ref name="neck section">50</part-num-ref>
+ of each of the guide members <part-num-ref name="guide members">46.</part-num-ref>
+ Optionally, spacer sleeves <part-num-ref name="guide members 46. Optionally, spacer sleeves">57</part-num-ref>
+ are used on a portion of the guide members <part-num-ref name="guide members">46</part-num-ref>
+ to further reduce the number of parts in the assembly.    </p>
+    <p id="p-23" num="23">[0020]    The guide members <part-num-ref name="guide members">46</part-num-ref>
+ support a seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ and cooperate with the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ and spacer sleeves <part-num-ref name="and spacer sleeves">57</part-num-ref>
+ to control a direction of seal housing <part-num-ref name="direction of seal housing">58</part-num-ref>
+ movement along an axial translation direction T. A flange <part-num-ref name="flange">60</part-num-ref>
+ extends in a radial direction relative to an engine central axis A. The flange <part-num-ref name="flange">60</part-num-ref>
+ includes guide slots <part-num-ref name="includes guide slots">62</part-num-ref>
+ that fit onto a corresponding spacer sleeve <part-num-ref name="corresponding spacer sleeve">57</part-num-ref>
+ to axially guide the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ and to prevent seal housing <part-num-ref name="and to prevent seal housing">58</part-num-ref>
+ rotation.    </p>
+    <p id="p-24" num="24">The flange 60 extends from a seal-receiving section <part-num-ref name="seal-receiving section">64</part-num-ref>
+ of the seal housing <part-num-ref name="seal housing">58.</part-num-ref>
+ A seal housing bore section <part-num-ref name="seal housing bore section">66</part-num-ref>
+ (one example of a force transfer section) extends axially from the seal- receiving section <part-num-ref name="seal- receiving section">64.</part-num-ref>
+ A contact section <part-num-ref name="contact section">68</part-num-ref>
+ extends radially from and is cantilevered from the seal housing bore section <part-num-ref name="seal housing bore section">66.</part-num-ref>
+ In one example, the seal-receiving section <part-num-ref name="seal-receiving section">64,</part-num-ref>
+ seal housing bore section <part-num-ref name="seal-receiving section 64, seal housing bore section">66,</part-num-ref>
+ and contact section <part-num-ref name="seal-receiving section 64, seal housing bore section 66, and contact section">68</part-num-ref>
+ are integrally formed as a single component.    </p>
+    <p id="p-25" num="25">[0021]    An axial surface <part-num-ref name="axial surface">70</part-num-ref>
+ of the contact section <part-num-ref name="contact section">68</part-num-ref>
+ includes a wear layer <part-num-ref name="wear layer">72</part-num-ref>
+ for contact with an annular spring <part-num-ref name="annular spring">74.</part-num-ref>
+ Alternatively, a plurality of coil springs or other types of bias members are used. The support wall <part-num-ref name="support wall">42</part-num-ref>
+ also includes a wear layer <part-num-ref name="wear layer">76</part-num-ref>
+ adjacent to the annular spring <part-num-ref name="annular spring">74.</part-num-ref>
+ The wear layers <part-num-ref name="wear layers">72</part-num-ref>
+ and <part-num-ref name="and">76</part-num-ref>
+ provide the benefit of protecting the axial surface <part-num-ref name="axial surface">70,</part-num-ref>
+ support wall <part-num-ref name="axial surface 70, support wall">42,</part-num-ref>
+ and annular spring <part-num-ref name="axial surface 70, support wall 42, and annular spring">74</part-num-ref>
+ from wear. In one example, the wear layers <part-num-ref name="wear layers">72</part-num-ref>
+ and <part-num-ref name="and">76</part-num-ref>
+ include a coating that is harder than the metal substrate of the respective contact section <part-num-ref name="respective contact section">68</part-num-ref>
+ and support wall <part-num-ref name="and support wall">42.</part-num-ref>
+ The annular spring <part-num-ref name="annular spring">74,</part-num-ref>
+ contact section <part-num-ref name="annular spring 74, contact section">68,</part-num-ref>
+ and support wall <part-num-ref name="annular spring 74, contact section 68, and support wall">42</part-num-ref>
+ may also include a hard coating for wear resistance.    </p>
+    <p id="p-26" num="26">[0022]    The seal-receiving section <part-num-ref name="seal-receiving section">64</part-num-ref>
+ includes an annular graphitic carbon ring <part-num-ref name="annular graphitic carbon ring">86</part-num-ref>
+ that is interference fit into the seal-receiving section <part-num-ref name="seal-receiving section">64.</part-num-ref>
+ The graphitic carbon ring <part-num-ref name="graphitic carbon ring">86</part-num-ref>
+ includes a nose <part-num-ref name="nose">88</part-num-ref>
+ that contacts seal seat <part-num-ref name="that contacts seal seat">90</part-num-ref>
+ when the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ is in a sealing position. In this example, the graphitic carbon ring <part-num-ref name="graphitic carbon ring">86</part-num-ref>
+ is at least partially radially aligned (i.e., axially offset) with the annular spring <part-num-ref name="annular spring">74.</part-num-ref>
+ The seal seat <part-num-ref name="seal seat">90</part-num-ref>
+ rotates with the shaft <part-num-ref name="shaft">20,</part-num-ref>
+ while the seal arrangement <part-num-ref name="seal arrangement">38</part-num-ref>
+ remains static with the case <part-num-ref name="case">24.</part-num-ref>
+    </p>
+    <boundary-data type="header">
+      <confidence value="8">4</confidence>
+    </boundary-data>
+    <boundary-data type="header">67,097-531; <confidence value="56">ID</confidence>
+F ID-<confidence value="4">1</confidence>
+103-US    </boundary-data>
+    <p id="p-27" num="27">
+      <page-break num="5"/>
+[0023]   The support wall <part-num-ref name="support wall">42</part-num-ref>
+ includes a seal groove <part-num-ref name="seal groove">92</part-num-ref>
+ and corresponding seal <part-num-ref name="and corresponding seal">94</part-num-ref>
+ located radially inward of the seal housing bore section <part-num-ref name="seal housing bore section">66.</part-num-ref>
+ In one example, the graphitic carbon ring <part-num-ref name="graphitic carbon ring">86</part-num-ref>
+ is referred to as a primary seal of the bearing chamber <part-num-ref name="bearing chamber">40</part-num-ref>
+ and the seal <part-num-ref name="seal">94</part-num-ref>
+ is referred to as a secondary seal that radially seals the seal arrangement <part-num-ref name="seal arrangement">38.</part-num-ref>
+    </p>
+    <p id="p-28" num="28">[0024]   The seal <part-num-ref name="seal">94</part-num-ref>
+ contacts the seal housing bore section <part-num-ref name="seal housing bore section">66</part-num-ref>
+ of the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ to resist fluid leakage across in the axial direction, as the seal member translates axially.    </p>
+    <p id="p-29" num="29">The seal 94 is resilient such that the seal <part-num-ref name="seal">94</part-num-ref>
+ maintains a radial bias force against the seal housing bore section <part-num-ref name="seal housing bore section">66.</part-num-ref>
+ Optionally, the seal housing bore section <part-num-ref name="seal housing bore section">66</part-num-ref>
+ includes a hard coating that extends along at least a portion of the seal housing bore section <part-num-ref name="seal housing bore section">66</part-num-ref>
+ for enhanced wear resistance. In one example, the seal <part-num-ref name="seal">94</part-num-ref>
+ is made of a durable, low-friction material, such as polytetrafluoroethylene.    </p>
+    <p id="p-30" num="30">[0025]    During operation of the rotational assembly <part-num-ref name="rotational assembly">10,</part-num-ref>
+ the net resultant of axially opposing fluid pressure forces and the annular spring <part-num-ref name="annular spring">74</part-num-ref>
+ provide a bias force on the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ to urge the graphitic carbon ring <part-num-ref name="graphitic carbon ring">86</part-num-ref>
+ into sealing contact with the seal seat <part-num-ref name="seal seat">90,</part-num-ref>
+ which rotates during rotational assembly <part-num-ref name="seal seat 90, which rotates during rotational assembly">10</part-num-ref>
+ operation. The annular spring <part-num-ref name="annular spring">74</part-num-ref>
+ provides a bias force against the wear layer <part-num-ref name="wear layer">72</part-num-ref>
+ of the contact section <part-num-ref name="contact section">68,</part-num-ref>
+ which transfers the force to the seal housing bore section <part-num-ref name="seal housing bore section">66</part-num-ref>
+ and seal-receiving section <part-num-ref name="and seal-receiving section">64.</part-num-ref>
+ The bias force urges the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ toward the seal seat <part-num-ref name="seal seat">90</part-num-ref>
+ to provide a sealing force between the graphitic carbon ring <part-num-ref name="graphitic carbon ring">86</part-num-ref>
+ and the seal seat <part-num-ref name="seal seat">90.</part-num-ref>
+    </p>
+    <p id="p-31" num="31">[0026]   Referring to Figure 3, the guide member <part-num-ref name="guide member">46</part-num-ref>
+ axially guides movement of the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ along a translation direction T via engagement with the spacer sleeve <part-num-ref name="spacer sleeve">57</part-num-ref>
+ and flange <part-num-ref name="and flange">60</part-num-ref>
+ of the seal housing <part-num-ref name="seal housing">58.</part-num-ref>
+ The spacer sleeve <part-num-ref name="spacer sleeve">57</part-num-ref>
+ includes rounded sides <part-num-ref name="includes rounded sides">98</part-num-ref>
+ and flat sides <part-num-ref name="and flat sides">100.</part-num-ref>
+ The flat sides <part-num-ref name="flat sides">100</part-num-ref>
+ correspond to the flat sides of the guide slot <part-num-ref name="guide slot">62.</part-num-ref>
+ The spacer sleeves <part-num-ref name="spacer sleeves">57</part-num-ref>
+ provide smooth movement of the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ along the guide member <part-num-ref name="guide member">46</part-num-ref>
+ and reduce friction and wear between the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ and neck sections <part-num-ref name="and neck sections">50.</part-num-ref>
+    </p>
+    <p id="p-32" num="32">[0027]   In the illustrated example, there is a space <part-num-ref name="space">105</part-num-ref>
+ between the retaining collar <part-num-ref name="retaining collar">54</part-num-ref>
+ and the flange <part-num-ref name="flange">60.</part-num-ref>
+ The space <part-num-ref name="space">105</part-num-ref>
+ allows the nose <part-num-ref name="nose">88</part-num-ref>
+ of the graphitic carbon ring <part-num-ref name="graphitic carbon ring">86</part-num-ref>
+ to contact the seal seat <part-num-ref name="seal seat">90</part-num-ref>
+ when the graphitic carbon ring <part-num-ref name="graphitic carbon ring">86</part-num-ref>
+ is in a sealing position. As the nose <part-num-ref name="nose">88</part-num-ref>
+ wears, the space <part-num-ref name="space">105</part-num-ref>
+ decreases.    </p>
+    <p id="p-33" num="33">[0028]   The retaining collar <part-num-ref name="retaining collar">54</part-num-ref>
+ secured on the neck section <part-num-ref name="neck section">50</part-num-ref>
+ functions as a stop to prevent the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ from moving beyond the retaining collar <part-num-ref name="retaining collar">54</part-num-ref>
+ in the direction T<confidence value="2">i</confidence>
+ <boundary-data type="header">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+      <page-break num="6"/>
+      <boundary-data type="header">67,097-531<confidence value="6">;</confidence>
+ <confidence value="5">D</confidence>
+F ID-<confidence value="4">1</confidence>
+103-US      </boundary-data>
+(e.g., when the nose <part-num-ref name="nose">88</part-num-ref>
+ wears down). The difference in diameter between the base portion <part-num-ref name="base portion">48</part-num-ref>
+ and the neck portion <part-num-ref name="neck portion">50</part-num-ref>
+ provides a stop <part-num-ref name="stop">106</part-num-ref>
+ that stops the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ from moving in the direction T2. Thus, the retaining collar <part-num-ref name="retaining collar">54</part-num-ref>
+ and stop <part-num-ref name="and stop">106</part-num-ref>
+ define a range of movement of the seal housing <part-num-ref name="seal housing">58.</part-num-ref>
+ This provides the benefit of protecting the annular spring <part-num-ref name="annular spring">74</part-num-ref>
+ from being over-compressed if the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ moves too far in the direction T2, which is a concern with prior shaft seal arrangements.    </p>
+    <p id="p-34" num="34">[0029]   Referring to Figure 4, the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ is shown in a sealing position wherein the graphitic carbon ring <part-num-ref name="graphitic carbon ring">86</part-num-ref>
+ is axially offset from the seal seat <part-num-ref name="seal seat">90.</part-num-ref>
+    </p>
+    <p id="p-35" num="35">[0030]   In the illustrated example, the nose <part-num-ref name="nose">88</part-num-ref>
+ has worn an amount that is greater than the size of space <part-num-ref name="size of space">105</part-num-ref>
+ (Figure 5). The retaining collar <part-num-ref name="retaining collar">54</part-num-ref>
+ contacts the flange <part-num-ref name="flange">60</part-num-ref>
+ and prevents the graphitic carbon ring86 from further wear against the seal seat <part-num-ref name="seal seat">90,</part-num-ref>
+ which may otherwise result in damage to the seal arrangement <part-num-ref name="seal arrangement">38.</part-num-ref>
+ The size of the space <part-num-ref name="space">105</part-num-ref>
+ may be predetermined in a design stage of the seal arrangement <part-num-ref name="seal arrangement">38</part-num-ref>
+ and may vary with design.    </p>
+    <p id="p-36" num="36">[0031]   Referring to Figure 5, the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ is shown in a retracted position wherein the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ is moved to the left in the illustration. In a retracted position, the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ compresses the annular spring <part-num-ref name="annular spring">74</part-num-ref>
+ against the support wall <part-num-ref name="support wall">42.</part-num-ref>
+    </p>
+    <p id="p-37" num="37">[0032]   Retraction may occur under any of several different conditions. During pre-assembly of the seal arrangement <part-num-ref name="seal arrangement">38,</part-num-ref>
+ for example, an operator may retract the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ to verify smooth travel of the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ along the direction of translation T.    </p>
+    <p id="p-38" num="38">The seal housing 58 may also retract under a pressure-reversal condition in which the pressure outside of the bearing chamber <part-num-ref name="bearing chamber">40</part-num-ref>
+ becomes lower than the pressure within the bearing chamber <part-num-ref name="bearing chamber">40.</part-num-ref>
+ In one example, the pressure may reverse if the seal between the nose <part-num-ref name="nose">88</part-num-ref>
+ and the seal seat <part-num-ref name="seal seat">90</part-num-ref>
+ is lost.    </p>
+    <p id="p-39" num="39">[0033]   The stop <part-num-ref name="stop">106</part-num-ref>
+ of the guide member <part-num-ref name="guide member">46</part-num-ref>
+ limits movement of the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ in the direction T2 toward the annular spring <part-num-ref name="annular spring">74</part-num-ref>
+ and seal <part-num-ref name="and seal">94.</part-num-ref>
+ This provides the benefit of protecting the annular spring <part-num-ref name="annular spring">74</part-num-ref>
+ fro<confidence value="8">m</confidence>
+ being over-compressed between the contact section <part-num-ref name="contact section">68</part-num-ref>
+ of the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ and the support wall <part-num-ref name="support wall">42</part-num-ref>
+ and prevents the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ from traveling too far and interfering with the support wall <part-num-ref name="support wall">42.</part-num-ref>
+ That is, if the annular spring <part-num-ref name="annular spring">74</part-num-ref>
+ is compressed beyond a compression threshold, the annular spring <part-num-ref name="annular spring">74</part-num-ref>
+ may yield and no longer provide a desirable or design-intended amount of bias force to maintain a seal between the nose <part-num-ref name="nose">88</part-num-ref>
+ and the seal seat <part-num-ref name="seal seat">90.</part-num-ref>
+ Furthermore, the seal-receiving section <part-num-ref name="seal-receiving section">68</part-num-ref>
+ (Figure <part-num-ref name="(Figure">2)</part-num-ref>
+ is <boundary-data type="header">
+        <confidence value="8">6</confidence>
+      </boundary-data>
+      <page-break num="7"/>
+      <boundary-data type="header">67,097-531; IDF ID-<confidence value="1">I</confidence>
+ 103-US      </boundary-data>
+prevented from contacting the seal <part-num-ref name="seal">94</part-num-ref>
+ or seal groove <part-num-ref name="or seal groove">92,</part-num-ref>
+ which may cause damage, and the seal <part-num-ref name="seal">94</part-num-ref>
+ is maintained in contact with the hard coating on the seal housing bore section <part-num-ref name="seal housing bore section">66.</part-num-ref>
+    </p>
+    <p id="p-40" num="40">[0034<confidence value="5">]</confidence>
+   In one example, the guide member <part-num-ref name="guide member">46</part-num-ref>
+ and stop <part-num-ref name="and stop">106</part-num-ref>
+ are designed to provide a desired spacing <part-num-ref name="desired spacing">110</part-num-ref>
+ between the contact section <part-num-ref name="contact section">68</part-num-ref>
+ of the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ and the support wall <part-num-ref name="support wall">42</part-num-ref>
+ when the flange <part-num-ref name="flange">60</part-num-ref>
+ abuts the stop <part-num-ref name="stop">106.</part-num-ref>
+ The spacing <part-num-ref name="spacing">110</part-num-ref>
+ corresponds to the compression threshold of the annular spring <part-num-ref name="annular spring">74,</part-num-ref>
+ such that the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ is unable to compress the annular spring <part-num-ref name="annular spring">74</part-num-ref>
+ an amount that exceeds the compression threshold. Given this description, one of ordinary skill in the art will recognize that the guide member <part-num-ref name="guide member">46</part-num-ref>
+ and stop <part-num-ref name="and stop">106</part-num-ref>
+ can alternatively be designed to provide desired spacings between other portions of the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ and support wall <part-num-ref name="and support wall">42.</part-num-ref>
+    </p>
+    <p id="p-41" num="41">[0035]   Figure 6 is an axial view of portions of the seal arrangement <part-num-ref name="seal arrangement">38</part-num-ref>
+ according to the section shown in Figure 2 (but showing the entire circumference). The seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ mounts on the guide members <part-num-ref name="guide members">46</part-num-ref>
+ at four circumferential locations, for example. One location <part-num-ref name="at four circumferential locations, for example. One location">108</part-num-ref>
+ is slightly off-center to ensure that the seal arrangement <part-num-ref name="seal arrangement">38</part-num-ref>
+ is installed in a desired orientation.    </p>
+    <p id="p-42" num="42">[0036]   Incorporation of the contact section <part-num-ref name="contact section">68</part-num-ref>
+ feature into the seal housing <part-num-ref name="seal housing">58</part-num-ref>
+ enables use of an arrangement that utilizes the annular spring <part-num-ref name="annular spring">74</part-num-ref>
+ and guide members <part-num-ref name="and guide members">46.</part-num-ref>
+    </p>
+    <p id="p-43" num="43">Utilizing the annular spring <part-num-ref name="annular spring">74</part-num-ref>
+ eliminates at least the six to twelve individual coil springs and corresponding spring guides known in prior arrangements, and the guide members <part-num-ref name="guide members">46</part-num-ref>
+ allow axial guidance of the seal housing <part-num-ref name="seal housing">58,</part-num-ref>
+ proper orientation of the seal arrangement <part-num-ref name="seal arrangement">38,</part-num-ref>
+ and anti- rotation of the primary seal. The stops on the guide members <part-num-ref name="guide members">46</part-num-ref>
+ protect the annular spring <part-num-ref name="annular spring">74</part-num-ref>
+ from being over-compressed or over-stressed. Thus the simplified arrangement eliminates parts, reduces expense, and provides a robust design.    </p>
+    <p id="p-44" num="44">[0037]   Although a preferred embodiment of this invention has been disclosed, a worker of ordinary skill in this art would recognize that certain modifications would come within the scope of this invention. For that reason, the following claims should be studied to determine the true scope and content of this invention.</p>
+    <boundary-data type="header">
+      <confidence value="8">7</confidence>
+    </boundary-data>
+  </description>
+</us-patent-application>
+

prior_art/11263582.xml

@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11263582</doc-number>
+        <date>2009-05-26</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <boundary-data type="header">U.S.S.N.: 11/263,582</boundary-data>
+    <boundary-data type="header">Filed: October 31, 2005</boundary-data>
+    <boundary-data type="header">RESPONSE TO OFFICE ACTION</boundary-data>
+    <heading id="h-1">AMENDMENTS TO THE SPECIFICATION</heading>
+    <p id="p-1" num="1">Please amend the specification as follows.</p>
+    <p id="p-2" num="2">[0001] The present application is related to co-pending, and commonly assigned U.S.</p>
+    <p id="p-3" num="3">Patent Application No. 10/854,762, Attorney Docket No. 47583/P<confidence value="4">O</confidence>
+48US/10316466, entitled     </p>
+    <heading id="h-2">"SYSTEM AND METHOD FOR ARCHIVING COLLABORATIVE ELECTRONIC</heading>
+    <p id="p-4" num="4">MEETINGS"; and concurrently filed, co-pending, and commonly assigned U.S. Patent Application No. 11/263,652                                                     <confidence value="4">,</confidence>
+ entitled "NETWORK CONFIGURATION WITH SMART EDGE SERVERS"; and U.S. Patent Application No. 11/263,074                                                     <confidence value="5">,</confidence>
+ entitled "VIRTUAL GROUP CONNECTIONS", the disclosures of which are hereby incorporated herein by reference.    </p>
+    <p id="p-5" num="5">[0030] FIGURE 3B is a block diagram illustrating electronic collaboration system <part-num-ref name="block diagram illustrating electronic collaboration system">31</part-num-ref>
+ configured according to another embodiment of the present invention. Electronic collaboration system <part-num-ref name="present invention. Electronic collaboration system">30</part-num-ref>
+ (FIGURE 3A) is configured according to one architecture of electronic meeting systems. Electronic collaboration system <part-num-ref name="(FIGURE 3A) is configured according to one architecture of electronic meeting systems. Electronic collaboration system">31</part-num-ref>
+ has been configured according to another architecture as described in commonly-assigned, co-pending U.S. Patent Application Serial No.    </p>
+    <p id="p-6" num="6">11/263,652 <confidence value="222222222">XX/XXXXXX</confidence>
+, entitled, "NETWORK CONFIGURATION WITH SMART EDGE SERVERS," the disclosure of which is incorporated herein by reference. Meeting server <part-num-ref name="disclosure of which is incorporated herein by reference. Meeting server">301</part-num-ref>
+ hosts and manages an on-going electronic meeting, much as done by meeting server <part-num-ref name="on-going electronic meeting, much as done by meeting server">300</part-num-ref>
+ (FIGURE 3A).    </p>
+    <p id="p-7" num="7">[0031] Meeting participants 311 and <part-num-ref name="and">312</part-num-ref>
+ connect into the meeting directly to meeting server <part-num-ref name="meeting directly to meeting server">301</part-num-ref>
+ through Internet <part-num-ref name="through Internet">101.</part-num-ref>
+ Electronic collaboration system <part-num-ref name="through Internet 101. Electronic collaboration system">31</part-num-ref>
+ also includes collaboration edge server <part-num-ref name="also includes collaboration edge server">303,</part-num-ref>
+ which provides a single connection into meeting server <part-num-ref name="single connection into meeting server">301</part-num-ref>
+ despite connecting any available number of meeting participants into the electronic meeting managed by meeting server <part-num-ref name="electronic meeting managed by meeting server">301.</part-num-ref>
+ This connection is implemented according to technology described in commonly- assigned, co-pending, U.S. Patent Application Serial No. <confidence value="8866666686">11/263,074</confidence>
+      <confidence value="5">,</confidence>
+ entitled "VIRTUAL GROUP CONNECTIONS," the disclosure of which is incorporated herein by <boundary-data type="header">
+        <confidence value="8">2</confidence>
+      </boundary-data>
+      <boundary-data type="header">US2008 685624.1</boundary-data>
+      <page-break num="2"/>
+      <boundary-data type="header">U.S.S.N.: 11/263,582</boundary-data>
+      <boundary-data type="header">Filed: October 31, 2005</boundary-data>
+      <boundary-data type="header">RESPONSE TO OFFICE ACTION</boundary-data>
+reference. Meeting participants <part-num-ref name="disclosure of which is incorporated herein by reference. Meeting participants">309</part-num-ref>
+ and <part-num-ref name="and">310</part-num-ref>
+ connect into the electronic meeting through collaboration edge server <part-num-ref name="electronic meeting through collaboration edge server">303.</part-num-ref>
+    </p>
+    <boundary-data type="header">
+      <confidence value="8">3</confidence>
+    </boundary-data>
+    <boundary-data type="header">US2008 685624.1</boundary-data>
+  </description>
+</us-patent-application>
+

prior_art/11271081.xml

@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11271081</doc-number>
+        <date>2010-12-01</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <heading id="h-1">AMENDMENT TO THE SPECIFICATION</heading>
+    <p id="p-1" num="1">Please replace the second full paragraph heading on page <part-num-ref name="second full paragraph heading on page">24,</part-num-ref>
+ line <part-num-ref name="second full paragraph heading on page 24, line">9</part-num-ref>
+ with the following amended heading<confidence value="5">:</confidence>
+    </p>
+    <heading id="h-2">
+      <confidence value="86">E.</confidence>
+ <confidence value="1">I</confidence>
+NEQUA<confidence value="55868885">LIT-ITES</confidence>
+ E. INE<confidence value="8">Q</confidence>
+UALITIES    </heading>
+    <p id="p-2" num="2">-- 2 --            Attorney Docket No.: APLE.P<confidence value="4">0</confidence>
+102 USPTO Serial No.: 11/271,081 Client Docket No.: P3839US1     </p>
+  </description>
+</us-patent-application>
+

prior_art/11274999.xml

@@ -0,0 +1,729 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11274999</doc-number>
+        <date>2005-11-15</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <boundary-data type="header">UTILITY PATENT APPLICATION</boundary-data>
+    <boundary-data type="header">AT<confidence value="8">T</confidence>
+ORNEY DOCKET NO. 028.0013    </boundary-data>
+    <heading id="h-1">METHODS AND SYSTEMS FOR DETECTING A POSITION-BASED</heading>
+    <heading id="h-2">ATTRIBUTE OF AN OBJECT USING DIGITAL CODES</heading>
+    <heading id="h-3">TECHNICAL FIELD</heading>
+    <p id="p-1" num="1">[0001] The present invention generally relates to position or proximity sensors such as touchpads, and more particularly relates to devices, systems and methods capable of detecting a position-based attribute of a finger, stylus or other object using digital codes.</p>
+    <heading id="h-4">BACKGROUND</heading>
+    <p id="p-2" num="2">[0002<confidence value="5">]</confidence>
+ Position sensors are commonly used as input devices for computers, personal digital assistants (PDAs), media players, video game players, consumer electronics, wireless phones, payphones, point-of-sale terminals, automatic teller machines, kiosks and the like.    </p>
+    <p id="p-3" num="3">One common type of sensor used in such applications is the touchpad sensor, which can be readily found, for example, as an input device on many notebook-type computers. A user generally operates the sensor by moving a finger, stylus or other stimulus near a sensing region of the sensor. The stimulus creates a capacitive, inductive or other electrical effect upon a carrier signal applied to the sensing region that can be detected and correlated to the position or proximity of the stimulus with respect to the sensing region. This positional information can in turn be used to move a cursor or other indicator on a display screen, scroll through text elements on the screen, or for any other user interface purpose. One example of a touchpad-type position sensor that is based on capacitive sensing technologies is described in United States Patent No. 5,880,411, which issued to Gillespie et al. on March <part-num-ref name="touchpad-type position sensor that is based on capacitive sensing technologies is described in United States Patent No. 5,880,411, which issued to Gillespie et al. on March">9,</part-num-ref>
+ <part-num-ref name="touchpad-type position sensor that is based on capacitive sensing technologies is described in United States Patent No. 5,880,411, which issued to Gillespie et al. on March 9,">1999.</part-num-ref>
+    </p>
+    <p id="p-4" num="4">[0003] While touchpad-type sensors have been in use for several years, engineers continue to seek design alternatives that reduce costs <confidence value="222222">and/or</confidence>
+ improve sensor performance. In particular, significant attention has been paid in recent years to reducing the effects of noise generated by display screens, power sources, radio frequency inte<confidence value="8">r</confidence>
+ference <confidence value="222222">and/or</confidence>
+ other <boundary-data type="header">
+        <confidence value="7">1</confidence>
+      </boundary-data>
+      <page-break num="2"/>
+      <boundary-data type="header">UTILITY PATENT APPLICATION</boundary-data>
+      <boundary-data type="header">ATTORNEY DOCKET NO. 028.0013</boundary-data>
+sources outside of the sensor. Numerous sampling, filtering, signal processing, shielding, and other noise-reduction techniques have been implemented with varying levels of success.    </p>
+    <p id="p-5" num="5">[0004<confidence value="5">]</confidence>
+ Accordingly, it is desirable to provide systems and methods for quickly, effectively and efficiently detecting a position-based attribute of an object in the presence of noise.    </p>
+    <p id="p-6" num="6">Other desirable features and characteristics will become apparent from the subsequent detailed description and the appended claims, taken in conjunction with the accompanying drawings and the foregoing technical field and background.</p>
+    <heading id="h-5">BRIEF SUMMARY</heading>
+    <p id="p-7" num="7">[0005] Methods, systems and devices are described for detecting a position-based attribute of a finger, stylus or other object with a touchpad or other sensor. According to various embodiments, the sensor includes a touch-sensitive region made up of any number of electrodes arranged in an appropriate fashion to detect user input. Modulation signals for one or more electrodes are produced as a function of any number of distinct discrete digital codes, which may be substantially orthogonal to each other. The modulation signals are applied to an associated at least one of the plurality of electrodes to obtain a resultant signal that is electrically affected by the position of the object. The resultant signal is demodulated using the plurality of distinct digital codes to discriminate electrical effects produced by the object. The position-based attribute of the object is then determined with respect to the plurality of electrodes from the electrical effects.</p>
+    <heading id="h-6">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
+    <p id="p-8" num="8">[0006<confidence value="5">]</confidence>
+ Various aspects of the present invention will hereinafter be described in conjunction with the following drawing figures, wherein like numerals denote like elements, and <confidence value="5">[</confidence>
+0007] FIGS. <confidence value="4">1</confidence>
+A-B are block diagrams showing exemplary sensing devices;    </p>
+    <p id="p-9" num="9">[0008<confidence value="5">]</confidence>
+ FIG. 2 is a flowchart showing an exemplary process for detecting a position-based attribute of an object;    </p>
+    <boundary-data type="header">
+      <confidence value="8">2</confidence>
+    </boundary-data>
+    <boundary-data type="header">UTILITY PATENT APPLICATION</boundary-data>
+    <boundary-data type="header">ATTORNEY DOCKET NO. 028.00<confidence value="88">13</confidence>
+    </boundary-data>
+    <p id="p-10" num="10">
+      <page-break num="3"/>
+      <confidence value="5">[</confidence>
+0009] FIG. 3 includes two frequency domain plots for exemplary received and demodulated signals;    </p>
+    <p id="p-11" num="11">
+      <confidence value="5">[</confidence>
+0010<confidence value="5">]</confidence>
+ FIG. 4 is a depiction of an exemplary scenario for processing electrical images of sensed objects;    </p>
+    <p id="p-12" num="12">[0011] FIG. 5 is a block diagram of an exemplary sensing device capable of sensing multiple position-based attributes in two dimensions;</p>
+    <p id="p-13" num="13">
+      <confidence value="5">[</confidence>
+0012<confidence value="5">]</confidence>
+ FIG. 6 includes two block diagrams of exemplary sensing devices with a filtering capacitor: one with simultaneous sensing of multiple signal channels on a common receive electrode, and the other with unified modulation and receive electrodes;    </p>
+    <p id="p-14" num="14">
+      <confidence value="5">[</confidence>
+0013<confidence value="5">]</confidence>
+ FIG. 7 is a block diagram of an exemplary sensing device formed on a single substrate; and <confidence value="5">[</confidence>
+0014] FIG. 8 is a block diagram of an exemplary sensing device formed on a flexible substrate.    </p>
+    <heading id="h-7">DETAILED DESCRIPTION</heading>
+    <p id="p-15" num="15">
+      <confidence value="5">[</confidence>
+0015] The following detailed description is merely exemplary in nature and is not intended to limit the invention or the application and uses of the invention. Furthermore, there is no intention to be bound by any expressed or implied theory presented in the preceding technical field, background, brief summary or the following detailed description.    </p>
+    <p id="p-16" num="16">
+      <confidence value="5">[</confidence>
+0016<confidence value="5">]</confidence>
+ According to various exemplary embodiments, spread spectrum techniques can be applied within a position sensor such as a touchpad to improve noise immunity <confidence value="222222">and/or</confidence>
+ to provide performance enhancements. Code division multiplexing (CDM), for example, can be used to create two or more distinct modulation signals that are applied to sensing electrode(s) within the sensor, thereby increasing the effective power of the applied signals.    </p>
+    <p id="p-17" num="17">Coded spread spectrum modulation may refer to direct sequence, frequency hopping, time hopping or various hybrids of these or other techniques. Because the modulation frequencies applied to the sensitive region cover a wider spectrum than was previously received, narrow band noise occurring at a particular frequency or moderate wide band <boundary-data type="header">
+        <confidence value="8">3</confidence>
+      </boundary-data>
+      <page-break num="4"/>
+      <boundary-data type="header">UTILITY PATENT APPLICATION</boundary-data>
+      <boundary-data type="header">ATTORNEY DOCKET NO. 028.0013</boundary-data>
+noise, uncorrelated with the coded modulation, has a minimal effect upon the narrower overall demodulated signal channels. The effect of noise on multiple signal channels may also be more uniform so that a minimum signal-to-noise ratio (SNR) is maintained for each useful signal channel. This concept can be exploited even further by selecting digital codes to produce frequency-domain signals that avoid known sources of noise. Spread spectrum techniques can therefore apply increased power to the sensing region while reducing the effects of noise, thereby resulting in a significantly improved SNR for the sensor in comparison to conventional time-domain multiplexing techniques of a comparable sample period. Spread spectrum techniques applied within the sensor may enable other beneficial sensor designs and features as well. These concepts are explored more fully below.    </p>
+    <p id="p-18" num="18">[0017] As used herein, the term "position sensor" is intended to encompass not only conventional touchpad devices, but also a broad range of equivalent devices that are capable of detecting the position or proximity of one or more fingers, pointers, styli or other objects.</p>
+    <p id="p-19" num="19">Such devices may include, without limitation, touch screens, touch pads, touch tablets, biometric authentication devices (e.g. fingerprint sensors), handwriting or character recognition devices, and the like. Similarly, the terms "position", "object position" and "position-based attribute" as used herein are intended to broadly encompass various types of absolute or relative positional or proximity information, and also other types of spatial- domain information such as speed, velocity, acceleration, and the like, including measurement of motion in one or more directions. Various position-based attributes may also include time history components, as in the case of gesture recognition and the like.</p>
+    <p id="p-20" num="20">Accordingly, many different types of "position sensors" may be capable of detecting widely varying "position-based attributes" beyond the mere presence or absence of an object in a wide array of alternate but equivalent embodiments determined by their applications.</p>
+    <p id="p-21" num="21">
+      <confidence value="5">[</confidence>
+0018] Turning now to the drawing figures and with initial reference to FIG. <confidence value="2">1</confidence>
+A, an exemplary sensor <part-num-ref name="exemplary sensor">100</part-num-ref>
+ suitably includes a sensing region <part-num-ref name="sensing region">101,</part-num-ref>
+ a controller <part-num-ref name="controller">102,</part-num-ref>
+ a modulator <part-num-ref name="modulator">107,</part-num-ref>
+ with associated drive circuitry <part-num-ref name="modulator 107, with associated drive circuitry">109,</part-num-ref>
+ and a demodulator <part-num-ref name="demodulator">117</part-num-ref>
+ with associated receiver circuitry <part-num-ref name="with associated receiver circuitry">115</part-num-ref>
+ as appropriate. A position-based attribute of a finger, stylus or other object <part-num-ref name="finger, stylus or other object">121</part-num-ref>
+ is detected by applying various modulation signals 11<confidence value="4">0</confidence>
+A-D to electrodes <part-num-ref name="is detected by applying various modulation signals 110A-D to electrodes">
+        <confidence value="66">11</confidence>
+      </part-num-ref>
+ 2A-D that, along with sensing electrode <part-num-ref name="2A-D that, along with sensing electrode">114,</part-num-ref>
+ define sensing region <part-num-ref name="2A-D that, along with sensing electrode 114, define sensing region">101.</part-num-ref>
+ The modulation signals 11<confidence value="488">0A-</confidence>
+ D are capacitively or otherwise electrically coupled to one or more receiving electrodes <part-num-ref name="modulation signals 110A- D are capacitively or otherwise electrically coupled to one or more receiving electrodes">114,</part-num-ref>
+ thereby forming any number of data transmission channels 113A-D. Electrical effects produced by object <part-num-ref name="modulation signals 110A- D are capacitively or otherwise electrically coupled to one or more receiving electrodes 114, thereby forming any number of data transmission channels 113A-D. Electrical effects produced by object">121</part-num-ref>
+ upon channels 113A-D can be subsequently identified in signals <part-num-ref name="upon channels 113A-D can be subsequently identified in signals">116</part-num-ref>
+ <boundary-data type="header">
+        <confidence value="8">4</confidence>
+      </boundary-data>
+      <page-break num="5"/>
+      <boundary-data type="header">UTILITY PATENT APPLICATION</boundary-data>
+      <boundary-data type="header">ATTORNEY DOCKET NO. 028.0013</boundary-data>
+received by the receive electrode, and these received signals can be subsequently processed to isolate the location of object <part-num-ref name="location of object">121</part-num-ref>
+ with respect to electrodes 112A-D within sensing region <part-num-ref name="with respect to electrodes 112A-D within sensing region">101.</part-num-ref>
+ An example of a conventional technique for capacitively sensing and processing object position in a touchpad is set forth in United States Patent No. 5,880,411, referenced above, although any other sensing techniques could be used in a wide array of alternate embodiments.    </p>
+    <p id="p-22" num="22">
+      <confidence value="5">[</confidence>
+0019<confidence value="5">]</confidence>
+ Although various types of sensors 100 are capable of detecting different electrical effects produced by object <part-num-ref name="are capable of detecting different electrical effects produced by object">121,</part-num-ref>
+ the exemplary embodiments of FIGS. <confidence value="2">l</confidence>
+A-B show configurations for monitoring changes in capacitance across sensing region <part-num-ref name="exemplary embodiments of FIGS. lA-B show configurations for monitoring changes in capacitance across sensing region">101</part-num-ref>
+ caused by the presence or absence of object <part-num-ref name="presence or absence of object">121.</part-num-ref>
+ More particularly, as modulation signals 11<confidence value="4">0</confidence>
+A-D are applied to electrodes <part-num-ref name="presence or absence of object 121. More particularly, as modulation signals 110A-D are applied to electrodes">
+        <confidence value="4">1</confidence>
+      </part-num-ref>
+ <confidence value="4">1</confidence>
+2A-D, a "virtual capacitor" is formed between each electrode <part-num-ref name="&quot;virtual capacitor&quot; is formed between each electrode">
+        <confidence value="4">1</confidence>
+      </part-num-ref>
+ <confidence value="4">1</confidence>
+2A- D transmitting the modulated signal and a receiving electrode <part-num-ref name="receiving electrode">114.</part-num-ref>
+ If an object is present within the fields created by this capacitor, the capacitance between the transmitting electrode <part-num-ref name="transmitting electrode">112</part-num-ref>
+ and the receiving electrode <part-num-ref name="receiving electrode">114</part-num-ref>
+ is affected. Typically, the effective capacitance between electrodes <part-num-ref name="effective capacitance between electrodes">112</part-num-ref>
+ and <part-num-ref name="and">114</part-num-ref>
+ is reduced if a grounded (or virtually grounded) object such as a finger is present, and the effective capacitance is increased if an ungrounded conductor (e.g. a stylus) or higher dielectric object is present. In either case, the change in capacitance caused by the presence of object <part-num-ref name="presence of object">121</part-num-ref>
+ is reflected in the output signal <part-num-ref name="output signal">116</part-num-ref>
+ such as voltage, current, or charge measured from receive electrode <part-num-ref name="such as voltage, current, or charge measured from receive electrode">114.</part-num-ref>
+    </p>
+    <p id="p-23" num="23">[0020] By monitoring signals 116 produced by each modulation signal <part-num-ref name="produced by each modulation signal">1<confidence value="5">1</confidence>
+      </part-num-ref>
+ <confidence value="4">0</confidence>
+A-D, then, the presence of object <part-num-ref name="presence of object">121</part-num-ref>
+ with respect to each electrode 112A-D (respectively) can be determined. In the exemplary embodiment shown in FIG. <confidence value="2">I</confidence>
+A, four sensing channels 113A- D are shown arranged in a one-dimensional sensing array <part-num-ref name="one-dimensional sensing array">101.</part-num-ref>
+ In the exemplary embodiment of FIG. 1B, seven channels 113A-G are implied with several channels 113A-C arranged in a first direction between 112A-C and <part-num-ref name="first direction between 112A-C and">114,</part-num-ref>
+ and the remaining channels <part-num-ref name="remaining channels">
+        <confidence value="5">1</confidence>
+      </part-num-ref>
+ <confidence value="4">1</confidence>
+3D-G arranged in a substantially orthogonal direction between 112D-G and <part-num-ref name="substantially orthogonal direction between 112D-G and">114</part-num-ref>
+ to allow for detection of image "silhouettes" in two dimensions, as described more fully below with reference to FIG. 4. In practice, as few as one channel (e.g. a button) or as many as dozens, hundreds or even more sensing channels could be arranged in any single or multi- dimensional pattern in a wide array of alternate embodiments. Properly arranged, the position of an object <part-num-ref name="object">121</part-num-ref>
+ with respect to sensing region <part-num-ref name="with respect to sensing region">101</part-num-ref>
+ can be determined from the electrical effects produced by object <part-num-ref name="electrical effects produced by object">121</part-num-ref>
+ upon the transmission of modulation signals <part-num-ref name="transmission of modulation signals">1<confidence value="5">1</confidence>
+      </part-num-ref>
+ <confidence value="488">0A-</confidence>
+ D applied to the various electrodes. These effects, in turn, are reflected in the received <boundary-data type="header">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+      <page-break num="6"/>
+      <boundary-data type="header">UTILITY PATENT APPLICATION</boundary-data>
+      <boundary-data type="header">AT<confidence value="8">T</confidence>
+ORNEY DOCKET NO. 028.00<confidence value="88">13</confidence>
+      </boundary-data>
+signals <part-num-ref name="received signals">116</part-num-ref>
+ that are demodulated and subsequently processed as appropriate to arrive at output signal <part-num-ref name="that are demodulated and subsequently processed as appropriate to arrive at output signal">120.</part-num-ref>
+    </p>
+    <p id="p-24" num="24">
+      <confidence value="5">[</confidence>
+0021<confidence value="5">]</confidence>
+ Further, sensor 100 may be readily configured or re-configured to create any type or number of sensing zones within region <part-num-ref name="may be readily configured or re-configured to create any type or number of sensing zones within region">101</part-num-ref>
+ by simply assigning or re-assigning digital codes used to create modulation signals <part-num-ref name="by simply assigning or re-assigning digital codes used to create modulation signals">110.</part-num-ref>
+ As shown in FIGS. <confidence value="4">l</confidence>
+A-B, each receiving electrode <part-num-ref name="by simply assigning or re-assigning digital codes used to create modulation signals 110. As shown in FIGS. lA-B, each receiving electrode">114</part-num-ref>
+ may receive signals coupled by any number of signal channels <part-num-ref name="may receive signals coupled by any number of signal channels">113,</part-num-ref>
+ thereby resulting i<confidence value="5">n</confidence>
+ multiple result signals <part-num-ref name="may receive signals coupled by any number of signal channels 113, thereby resulting in multiple result signals">116</part-num-ref>
+ being provided on a single path. Because signals <part-num-ref name="single path. Because signals">116</part-num-ref>
+ are provided on a common path, sensing channels <part-num-ref name="common path, sensing channels">113</part-num-ref>
+ of any number of electrodes may be created on a permanent or temporary basis by simply applying a common modulation signal <part-num-ref name="common modulation signal">110</part-num-ref>
+ (e.g. a modulation signal <part-num-ref name="modulation signal">110</part-num-ref>
+ formed from a common digital code) to each of the transmit electrodes <part-num-ref name="transmit electrodes">112</part-num-ref>
+ making up the sensing zone. Sensing zones within region <part-num-ref name="sensing zone. Sensing zones within region">101</part-num-ref>
+ may overlap <confidence value="222222">and/or</confidence>
+ vary with time, and are readily re-configurable through simple application of different digital codes to one or more electrodes <part-num-ref name="may overlap and/or vary with time, and are readily re-configurable through simple application of different digital codes to one or more electrodes">112.</part-num-ref>
+ More than one electrode may be part of a channel, and more than one channel modulation may be applied to an electrode.    </p>
+    <p id="p-25" num="25">
+      <confidence value="5">[</confidence>
+0022<confidence value="5">]</confidence>
+ In a traditional sensor, modulation signals <part-num-ref name="traditional sensor, modulation signals">1</part-num-ref>
+ <confidence value="54">l0</confidence>
+A-D are typically simple sinusoidal or other periodic alternating current (AC) signals applied sequentially to the various channels using any form of time domain multiplexing (TDM). By applying spread spectrum concepts commonly associated with radio communications to sensor <part-num-ref name="various channels using any form of time domain multiplexing (TDM). By applying spread spectrum concepts commonly associated with radio communications to sensor">100,</part-num-ref>
+ however, numerous benefits can be realized. In particular, digital coding techniques similar to those used in code division multiple access (CDMA) radio communications can be employed to create distinct modulation signals 11<confidence value="4">0</confidence>
+A-D that can be simultaneously applied to the various sensing zones of region <part-num-ref name="various sensing zones of region">101,</part-num-ref>
+ thereby potentially reducing the switching complexity of sensor <part-num-ref name="switching complexity of sensor">100.</part-num-ref>
+    </p>
+    <p id="p-26" num="26">[0023] Spread spectrum techniques applied within sensor 100 may provide additional benefits, such as improved resistance to noise. Because each signal channel <part-num-ref name="may provide additional benefits, such as improved resistance to noise. Because each signal channel">113</part-num-ref>
+ results from the application of an appropriate digital code, for example, principles of code gain can be readily exploited to improve the performance of sensor <part-num-ref name="performance of sensor">100.</part-num-ref>
+ The gain of each modulation signal <part-num-ref name="gain of each modulation signal">110</part-num-ref>
+ applied to one or more transmit electrodes <part-num-ref name="applied to one or more transmit electrodes">112</part-num-ref>
+ increases with the length of the code. Through the use of conventional code generation techniques, combinatorial variations of the digital codes with well-known spectral and correlation properties are relatively easy to generate. Further, these combinatorial variations provide a relatively large pool of potential distinct digital codes from which to create modulati<confidence value="8">o</confidence>
+n signals <part-num-ref name="relatively large pool of potential distinct digital codes from which to create modulation signals">110</part-num-ref>
+ with desirable time or <boundary-data type="header">
+        <confidence value="8">6</confidence>
+      </boundary-data>
+      <page-break num="7"/>
+      <boundary-data type="header">UTILITY PATENT APPLICATION</boundary-data>
+      <boundary-data type="header">ATTORNEY DOCKET NO. 028.0013</boundary-data>
+frequency domain characteristics, as described below. Additional detail about particular code generation and signal processing techniques are described more fully below.    </p>
+    <p id="p-27" num="27">
+      <confidence value="5">[</confidence>
+0024<confidence value="5">]</confidence>
+ Again with reference to FIGS. <confidence value="2">l</confidence>
+A-B, sensing region 101 is any capacitive, resistive, inductive or other type of sensor that is capable of detecting the position, proximity <confidence value="222222">and/or</confidence>
+ other position-based attribute of a finger, stylus or other object <part-num-ref name="finger, stylus or other object">121.</part-num-ref>
+    </p>
+    <p id="p-28" num="28">Exemplary sensing regions 101 include the various sensors produced by Synaptics Inc. of Santa Clara, California, which appropriately detect a one dimensional, two dimensional or multi-dimensional position of an object <part-num-ref name="object">121</part-num-ref>
+ using capacitive or inductive coupling, although many other sensing regions <part-num-ref name="using capacitive or inductive coupling, although many other sensing regions">101</part-num-ref>
+ could be used in a wide array of alternate embodiments.    </p>
+    <p id="p-29" num="29">Other types of sensing regions 101 capable of detecting position or proximity include sensors based upon acoustic, optical, or electromagnetic properties (e.g. radio frequency, infrared, ultraviolet or the like), and/or any other effects.</p>
+    <p id="p-30" num="30">[0025] Controller 102 is any processor, microcontroller, neural network, analog computer, programmed circuitry, or other module capable of processing input data <part-num-ref name="is any processor, microcontroller, neural network, analog computer, programmed circuitry, or other module capable of processing input data">118</part-num-ref>
+ to extract output indicia <part-num-ref name="to extract output indicia">120</part-num-ref>
+ and/or the like. The particular control circuitry <part-num-ref name="particular control circuitry">102</part-num-ref>
+ used varies widely from embodiment to embodiment, but in exemplary embodiments controller <part-num-ref name="used varies widely from embodiment to embodiment, but in exemplary embodiments controller">102</part-num-ref>
+ is a model T1004, T1005, T1<confidence value="4">0</confidence>
+XX or other microcontroller produced by Synaptics Inc. of Santa Clara, California. In many embodiments, controller <part-num-ref name="model T1004, T1005, T10XX or other microcontroller produced by Synaptics Inc. of Santa Clara, California. In many embodiments, controller">102</part-num-ref>
+ includes and/or communicates with a digital memory <part-num-ref name="digital memory">103</part-num-ref>
+ that suitably stores digital instructions in any software or firmware form that are executable by controller <part-num-ref name="that suitably stores digital instructions in any software or firmware form that are executable by controller">102</part-num-ref>
+ to implement the various sensing, control and other functions described herein.  Alternatively, the functions of memory <part-num-ref name="functions of memory">103</part-num-ref>
+ may be incorporated into controller <part-num-ref name="may be incorporated into controller">102</part-num-ref>
+ such that a physically distinct memory device <part-num-ref name="physically distinct memory device">103</part-num-ref>
+ may not be present in all embodiments. The physical controller may also incorporate more elements including the drive circuitry <part-num-ref name="drive circuitry">109</part-num-ref>
+ and receive circuitry <part-num-ref name="and receive circuitry">115,</part-num-ref>
+ as well as, others described.    </p>
+    <p id="p-31" num="31">
+      <confidence value="5">[</confidence>
+0026] Code generation module 104 is any discrete or integrated circuit, device, module, programming logic and/or the like capable of producing digital codes <part-num-ref name="like capable of producing digital codes">106</part-num-ref>
+ that can be used in generating modulation signals 1<confidence value="55">10</confidence>
+A-D. The number, size and types of digital codes produced vary significantly, but in various embodiments the codes are substantially orthogonal to each other, and are of sufficient length to provide for enough distinct digital codes to be associated with each sensing zone of region <part-num-ref name="codes are substantially orthogonal to each other, and are of sufficient length to provide for enough distinct digital codes to be associated with each sensing zone of region">101.</part-num-ref>
+ The discrete codes may be binary, ternary, or generically multi-level, and may indicate both driven and un-driven states (tri-state).Various circuits, modules and techniques for generating digital codes suitable for <boundary-data type="header">
+        <confidence value="8">7</confidence>
+      </boundary-data>
+      <page-break num="8"/>
+      <boundary-data type="header">UTILITY PATENT APPLICATION</boundary-data>
+      <boundary-data type="header">
+        <confidence value="8">A</confidence>
+TTORNEY DOCKET NO. 028.00<confidence value="88">13</confidence>
+      </boundary-data>
+use with CDM include shift register sequences such as Wa<confidence value="5">l</confidence>
+sh-Hadamard codes, m- sequences, Gold codes, Kasami codes, Barker codes, delay line multiple tap sequences, and/or the like. Alternatively, digital codes may be pre-determined and stored in a lookup table or other data structure within controller <part-num-ref name="lookup table or other data structure within controller">102</part-num-ref>
+ and/or memory <part-num-ref name="and/or memory">103,</part-num-ref>
+ and/or may be generated by controller <part-num-ref name="and/or memory 103, and/or may be generated by controller">102</part-num-ref>
+ using any suitable algorithm. In such embodiments, code generation module <part-num-ref name="using any suitable algorithm. In such embodiments, code generation module">104</part-num-ref>
+ may not be present as a separate physical element from controller <part-num-ref name="separate physical element from controller">102,</part-num-ref>
+ but rather should be considered to be a logical module representing the code generation and/or retrieval function carried out by controller <part-num-ref name="code generation and/or retrieval function carried out by controller">102</part-num-ref>
+ or other digital processing devices as appropriate.    </p>
+    <p id="p-32" num="32">
+      <confidence value="5">[</confidence>
+0027] The term "substantially orthogonal" in the context of the distinct digital codes is intended to convey that the distinct codes need not be perfectly orthogonal from each other in the mathematical sense, so long as the distinct codes are able to produce meaningful independent results. Strict orthogonality may thus be traded off for various other properties such as correlation, spectra, or compressibility. Similarly, the term "sensing zone<confidence value="5">"</confidence>
+ is intended to convey that a single code could be applied to multiple electrodes <part-num-ref name="single code could be applied to multiple electrodes">112</part-num-ref>
+ to create a single zone of sensitivity that encompasses a larger portion of sensing region <part-num-ref name="larger portion of sensing region">101</part-num-ref>
+ than any of the individual electrodes <part-num-ref name="individual electrodes">112.</part-num-ref>
+ Also, more than one code could be applied to an electrode creating overlapping or spatially filtered "sensing zones". For example phase delayed or "shifted" versions of the same code sequence can be distinct and substantially orthogonal such that they are readily distinguishable. In various cases, interpolation between phase shifts may even be possible.    </p>
+    <p id="p-33" num="33">[0028] Modulator 107 is any circuit, logic or other module capable of producing modulation signals 11<confidence value="4">0</confidence>
+A-D using the distinct digital codes produced by module <part-num-ref name="distinct digital codes produced by module">104.</part-num-ref>
+    </p>
+    <p id="p-34" num="34">Typically, modulator 107 modulates a carrier signal <part-num-ref name="carrier signal">111</part-num-ref>
+ with the digital codes <part-num-ref name="digital codes">106</part-num-ref>
+ using any type of amplitude modulation (AM), frequency modulation (FM), phase modulation (PM) or another suitable technique to create modulation signals 1<confidence value="85">10</confidence>
+A-D. Accordingly, modulator <part-num-ref name="using any type of amplitude modulation (AM), frequency modulation (FM), phase modulation (PM) or another suitable technique to create modulation signals 110A-D. Accordingly, modulator">107</part-num-ref>
+ may be implemented using any conventional digital and/or analog circuitry, or may be partially or entirely implemented with software logic executing within controller <part-num-ref name="may be implemented using any conventional digital and/or analog circuitry, or may be partially or entirely implemented with software logic executing within controller">102</part-num-ref>
+ or the like. Carrier signal <part-num-ref name="like. Carrier signal">111</part-num-ref>
+ may be produced by any oscillator or other signal generator <part-num-ref name="may be produced by any oscillator or other signal generator">105</part-num-ref>
+ as appropriate. In one embodiment suitable for use in a capacitively-sensing touchpad, signal <part-num-ref name="capacitively-sensing touchpad, signal">111</part-num-ref>
+ can be produced at frequencies that range from about <part-num-ref name="can be produced at frequencies that range from about">10</part-num-ref>
+ k<confidence value="5">H</confidence>
+z - <part-num-ref name="kHz -">100</part-num-ref>
+ <confidence value="66">MH</confidence>
+z, although these signals may be produced at any frequency or range in a wide array of equivalent embodiments. Additional detail about an exemplary modulation function is <boundary-data type="header">
+        <confidence value="8">8</confidence>
+      </boundary-data>
+      <page-break num="9"/>
+      <boundary-data type="header">UTILITY PATENT APPLICATION</boundary-data>
+      <boundary-data type="header">ATTORNEY DOCKET NO. 028.0013</boundary-data>
+described below with respect to FIG. 3. In still other embodiments, carrier signal <part-num-ref name="exemplary modulation function is described below with respect to FIG. 3. In still other embodiments, carrier signal">111</part-num-ref>
+ is eliminated and spectral components of the applied modulation signals 11<confidence value="5">0</confidence>
+A-D are determined from the clock rate, repeat lengths and/or other aspects of the digital codes. The carrier signal <part-num-ref name="carrier signal">111</part-num-ref>
+ may therefore be eliminated and/or conceptualized as a direct current (DC) signal in various alternate embodiments.    </p>
+    <p id="p-35" num="35">[0029<confidence value="5">]</confidence>
+ Modulation signals 1<confidence value="85">10</confidence>
+A-D are applied to electrodes 112A-D of sensing region 101 in any manner. In various embodiments, modulator <part-num-ref name="in any manner. In various embodiments, modulator">107</part-num-ref>
+ suitably applies the signals to the appropriate electrodes 112A-D via any drive circuitry <part-num-ref name="appropriate electrodes 112A-D via any drive circuitry">109,</part-num-ref>
+ which includes any sort of scaling amplifier, multiplexer, switch to any current or voltage source, charge transfer device, controlled impedance, and/or the like. Although FIG. 1 shows a single driver circuit <part-num-ref name="single driver circuit">109</part-num-ref>
+ interconnecting modulator <part-num-ref name="interconnecting modulator">107</part-num-ref>
+ and sensing region <part-num-ref name="and sensing region">101</part-num-ref>
+ in a serial fashion, in practice drive circuitry <part-num-ref name="serial fashion, in practice drive circuitry">109</part-num-ref>
+ will typically include multiple amplifiers, multiple drivers and/or other signal paths providing parallel connections between modulator <part-num-ref name="will typically include multiple amplifiers, multiple drivers and/or other signal paths providing parallel connections between modulator">107</part-num-ref>
+ and the various electrodes <part-num-ref name="various electrodes">112</part-num-ref>
+ within sensing region <part-num-ref name="within sensing region">101</part-num-ref>
+ to permit multiple sensing channels <part-num-ref name="to permit multiple sensing channels">113</part-num-ref>
+ to be driven by modulated electrodes <part-num-ref name="to be driven by modulated electrodes">112</part-num-ref>
+ simultaneously with the same or different signals.    </p>
+    <p id="p-36" num="36">
+      <confidence value="5">[</confidence>
+0030<confidence value="5">]</confidence>
+ As noted above, modulation signals 11<confidence value="4">0</confidence>
+A-D are provided to electrodes 112A-D in sensing region 101, and resultant signals 116 from receiving electrode <part-num-ref name="from receiving electrode">114</part-num-ref>
+ are provided to a suitable demodulator <part-num-ref name="suitable demodulator">117.</part-num-ref>
+  A  scaling amplifier, multiplexer, filter, discriminator, comparator, and/or other receiving circuitry <part-num-ref name="scaling amplifier, multiplexer, filter, discriminator, comparator, and/or other receiving circuitry">115</part-num-ref>
+ may be provided as well to shape received signals <part-num-ref name="may be provided as well to shape received signals">116.</part-num-ref>
+ Demodulator <part-num-ref name="may be provided as well to shape received signals 116. Demodulator">117</part-num-ref>
+ is any circuit or other module capable of demodulating the output <part-num-ref name="output">116</part-num-ref>
+ of sensing region <part-num-ref name="of sensing region">101</part-num-ref>
+ to identify any electrical effects produced by object <part-num-ref name="to identify any electrical effects produced by object">121.</part-num-ref>
+    </p>
+    <p id="p-37" num="37">Demodulator 117 may also include and/or communicate with a demodulation filter, such as any suitable digital or analog low-pass or band-pass filter, as well as any conventional analog-to-digital converter (ADC). In various embodiments, demodulator <part-num-ref name="demodulation filter, such as any suitable digital or analog low-pass or band-pass filter, as well as any conventional analog-to-digital converter (ADC). In various embodiments, demodulator">117</part-num-ref>
+ receives carrier signal <part-num-ref name="receives carrier signal">111</part-num-ref>
+ and/or the phase shifted versions of the distinct digital codes <part-num-ref name="distinct digital codes">106</part-num-ref>
+ to allow demodulation of both signals.   Alternatively, demodulator <part-num-ref name="to allow demodulation of both signals.   Alternatively, demodulator">117</part-num-ref>
+ provides analog demodulation of carrier signal <part-num-ref name="provides analog demodulation of carrier signal">111</part-num-ref>
+ and provides the resultant signals to controller <part-num-ref name="resultant signals to controller">102</part-num-ref>
+ and/or receiving circuitry <part-num-ref name="and/or receiving circuitry">115</part-num-ref>
+ for subsequent processing. Similarly, the demodulation function represented by module <part-num-ref name="demodulation function represented by module">117</part-num-ref>
+ in FIG. 1 may be logically provided in hardware, software, firmware and/or the like within controller <part-num-ref name="like within controller">102</part-num-ref>
+ and/or another component, thereby removing the need for a separately-identifiable demodulation circuit <part-num-ref name="separately-identifiable demodulation circuit">117.</part-num-ref>
+    </p>
+    <boundary-data type="header">
+      <confidence value="8">9</confidence>
+    </boundary-data>
+    <boundary-data type="header">UTILITY PATENT APPLICATION</boundary-data>
+    <boundary-data type="header">ATTORNEY DOCKET NO. 028.0013</boundary-data>
+    <p id="p-38" num="38">
+      <page-break num="10"/>
+[0031<confidence value="5">]</confidence>
+ During the operation of sensor <part-num-ref name="operation of sensor">100,</part-num-ref>
+ any number of distinct digital codes are produced by code generation module <part-num-ref name="operation of sensor 100, any number of distinct digital codes are produced by code generation module">104</part-num-ref>
+ and modulated with a carrier frequency to create a set of modulation signals 112A-D applied to any number of electrodes <part-num-ref name="set of modulation signals 112A-D applied to any number of electrodes">
+        <confidence value="66">11</confidence>
+      </part-num-ref>
+ 2A-D within sensing region <part-num-ref name="2A-D within sensing region">101.</part-num-ref>
+ The position of object <part-num-ref name="position of object">121</part-num-ref>
+ with respect to sensing region <part-num-ref name="with respect to sensing region">101</part-num-ref>
+ electrically affects one or more output signals <part-num-ref name="electrically affects one or more output signals">116</part-num-ref>
+ provided from sensing region <part-num-ref name="provided from sensing region">101.</part-num-ref>
+ By demodulating the resultant signals <part-num-ref name="resultant signals">116,</part-num-ref>
+ the electrical effects can be identified and subsequently processed by controller <part-num-ref name="electrical effects can be identified and subsequently processed by controller">102</part-num-ref>
+ or the like to determine a position-based attribute relating to object <part-num-ref name="position-based attribute relating to object">121.</part-num-ref>
+ By modulating the electrodes with an appropriate digital code, the narrower sensing frequency for the sensor is effectively spread across multiple frequencies, thereby improving noise rejection. Moreover, the use of code division multiplexing allows each of the modulation signals 11<confidence value="4">0</confidence>
+A-D to be applied simultaneously, thereby reducing or eliminating the need for separate time domain switching and control in many embodiments.    </p>
+    <p id="p-39" num="39">The electrical effects identified from sensing region 101 using spread spectrum techniques may be further processed by controller <part-num-ref name="using spread spectrum techniques may be further processed by controller">102</part-num-ref>
+ <confidence value="222222">and/or</confidence>
+ another processing device as appropriate.    </p>
+    <p id="p-40" num="40">[0032] With reference now to FIG. 2, an exemplary process <part-num-ref name="exemplary process">200</part-num-ref>
+ for detecting a position- based attribute of an object with respect to a sensing region <part-num-ref name="sensing region">101</part-num-ref>
+ suitably includes the broad steps of producing a set of distinct digital codes for modulation signals 11<confidence value="4">0</confidence>
+A-D (step 201), demodulating each of the response signals <part-num-ref name="response signals">116</part-num-ref>
+ that result from the application of modulation signals 1<confidence value="85">10</confidence>
+A-D (steps <part-num-ref name="application of modulation signals 110A-D (steps">204,</part-num-ref>
+ 206), and determining one or more position-based attributes of object <part-num-ref name="application of modulation signals 110A-D (steps 204, 206), and determining one or more position-based attributes of object">121</part-num-ref>
+ from the electrical effects identified within the response signals <part-num-ref name="response signals">116</part-num-ref>
+ (step 208).    </p>
+    <p id="p-41" num="41">In various further embodiments, the particular digital codes generated in step <part-num-ref name="particular digital codes generated in step">202</part-num-ref>
+ may be modified (step <part-num-ref name="may be modified (step">210)</part-num-ref>
+ to reduce the effects of noise, reducing interference on other devices caused by this device, or for any other purpose. Additional processing may also be performed (step 212), such as single or multi-object processing, rejection of undesired image data, <confidence value="222222">and/or</confidence>
+ the like.    </p>
+    <p id="p-42" num="42">[0033] Although flowchart shown in FIG. 2 is intended to show the various logical steps included in an exemplary process <part-num-ref name="exemplary process">200</part-num-ref>
+ rather than a literal software implementation, some or all of the steps in process <part-num-ref name="steps in process">200</part-num-ref>
+ may be stored in memory <part-num-ref name="may be stored in memory">103</part-num-ref>
+ and executed by controller <part-num-ref name="and executed by controller">102</part-num-ref>
+ alone and/or in conjunction with other components of sensor <part-num-ref name="alone and/or in conjunction with other components of sensor">100</part-num-ref>
+ (e.g. code generation module <part-num-ref name="code generation module">104,</part-num-ref>
+ modulator <part-num-ref name="code generation module 104, modulator">107,</part-num-ref>
+ demodulator <part-num-ref name="code generation module 104, modulator 107, demodulator">117</part-num-ref>
+ and/or the like). The various steps may be alternately stored within any digital storage medium, including any digital memory, transportable media (e.g. compact disk, floppy disk, portable memory and/or the like), magnetic or optical media, and/or the like. The various steps of process <part-num-ref name="various steps of process">200</part-num-ref>
+ may be applied <boundary-data type="header">
+        <confidence value="88">10</confidence>
+      </boundary-data>
+      <page-break num="11"/>
+      <boundary-data type="header">UTILITY PATENT APPLICATION</boundary-data>
+      <boundary-data type="header">ATTORNEY DOCKET NO. 028.0013</boundary-data>
+in any temporal order, or may be otherwise altered in any manner across a wide array of alternate embodiments. Further, the various steps shown in FIG. 2 could be combined or otherwise differently organized in any manner.    </p>
+    <p id="p-43" num="43">[0034] As noted above, the distinct digital codes <part-num-ref name="distinct digital codes">106</part-num-ref>
+ used to create modulation signals <part-num-ref name="used to create modulation signals">
+        <confidence value="8">1</confidence>
+      </part-num-ref>
+ <confidence value="55">1O</confidence>
+A-D may be produced in any manner (step 201), such as by any type of hardware or software logic represented by code generation module <part-num-ref name="1OA-D may be produced in any manner (step 201), such as by any type of hardware or software logic represented by code generation module">104</part-num-ref>
+ in FIG. 1. Any number of feedback shift registers, for example, can be configured in a maximum length sequence (MLS) or the like to generate a pseudo-random digital code of any desired length that could be readily applied in a variety of phases and/or sums as distinct code sequences to the various modulation signals 11<confidence value="4">0</confidence>
+A-D. The resulting sequence of binary codes <part-num-ref name="resulting sequence of binary codes">106</part-num-ref>
+ emanating from parallel shift registers is generally spectrally flat, with the exception of a minimal DC term. In an alternate embodiment, a MLS or other routine for generating digital codes <part-num-ref name="MLS or other routine for generating digital codes">106</part-num-ref>
+ may be simulated in software executing within controller <part-num-ref name="may be simulated in software executing within controller">102,</part-num-ref>
+ or elsewhere as appropriate.    </p>
+    <p id="p-44" num="44">In still other embodiments, codes 106 are generated prior to use and stored in a lookup table or other data structure in memory <part-num-ref name="lookup table or other data structure in memory">103,</part-num-ref>
+ or the like. In various alternate but equivalent embodiments, controller <part-num-ref name="like. In various alternate but equivalent embodiments, controller">102</part-num-ref>
+ may directly generate or retrieve codes <part-num-ref name="may directly generate or retrieve codes">106</part-num-ref>
+ and/or may produce them by directing the operation of a separate code generation module <part-num-ref name="separate code generation module">104</part-num-ref>
+ or the like. As noted above, the particular codes may be generated in any manner. A digital bit sequence may be simply shifted in phase, for example, to create multiple distinct codes.    </p>
+    <p id="p-45" num="45">Alternatively, distinct codes can be computed from other codes using a variety of methods including summation, exclusive-or, and multiplication, and/or other techniques of generating high dimensionality random and pseudo-random sequences. Code generation techniques based upon exclusive-or or multiplication operations may provide an additional benefit of generating linear combinations that may be useful in some embodiments.</p>
+    <p id="p-46" num="46">[0035] The various codes <part-num-ref name="various codes">106</part-num-ref>
+ are then used to modulate or otherwise create the particular modulation signals 11<confidence value="4">0</confidence>
+A-D that are applied to the various sensing electrodes 112A-D in sensing region <part-num-ref name="various sensing electrodes 112A-D in sensing region">101</part-num-ref>
+ (step 202). As described above, the applied signals are electrically affected by the presence of object <part-num-ref name="presence of object">121,</part-num-ref>
+ with the resultant electrical effects being determinable from received signal <part-num-ref name="resultant electrical effects being determinable from received signal">116</part-num-ref>
+ (step 203).    </p>
+    <p id="p-47" num="47">
+      <confidence value="5">[</confidence>
+0036] Demodulating received signal channels 113 (in step <part-num-ref name="(in step">204)</part-num-ref>
+ suitably involves extracting information about the position of object <part-num-ref name="position of object">121</part-num-ref>
+ from the modulated signals. Such extraction typically involves reversing the modulation process described above.    </p>
+    <boundary-data type="header">
+      <confidence value="88">11</confidence>
+    </boundary-data>
+    <boundary-data type="header">UTILITY PATENT APPLICATION</boundary-data>
+    <boundary-data type="header">AT<confidence value="8">T</confidence>
+ORNEY DOCKET NO. 028.0013    </boundary-data>
+    <p id="p-48" num="48">
+      <page-break num="12"/>
+Accordingly, demodulator 117 typically receives carrier signal <part-num-ref name="typically receives carrier signal">
+        <confidence value="666">111</confidence>
+      </part-num-ref>
+ (or another signal that is synchronous with signal <part-num-ref name="(or another signal that is synchronous with signal">111)</part-num-ref>
+ for performing analog demodulation and/or signal discrimination (e.g. distinguishing between noise and desired signal) in addition to the particular digital code <part-num-ref name="particular digital code">106</part-num-ref>
+ that previously modulated the carrier signal used to create the particular resultant signal <part-num-ref name="particular resultant signal">116.</part-num-ref>
+ Because the sensor both transmits and receives, it is rarely necessary to recover the carrier or code sequence.    </p>
+    <p id="p-49" num="49">
+      <confidence value="5">[</confidence>
+0037<confidence value="5">]</confidence>
+ Demodulation may be carried out for any number of received signal channels 113, as appropriate (step 206). In the exemplary sensor <part-num-ref name="exemplary sensor">100</part-num-ref>
+ shown in FIG. <confidence value="2">1</confidence>
+A, signal <part-num-ref name="shown in FIG. 1A, signal">116</part-num-ref>
+ resulting from the transmission of each signal channel from the modulated electrodes 112A- D are received on a common path emanating from receiving electrode <part-num-ref name="common path emanating from receiving electrode">114.</part-num-ref>
+ Even if the various sensing channels 113A-D are all active at the same time (e.g. modulation signals <part-num-ref name="modulation signals">
+        <confidence value="66">11</confidence>
+      </part-num-ref>
+ <confidence value="4">0</confidence>
+A-D are simultaneously provided to each modulated electrode <part-num-ref name="0A-D are simultaneously provided to each modulated electrode">
+        <confidence value="66">11</confidence>
+      </part-num-ref>
+ 2A-D), however, the resulting signals <part-num-ref name="resulting signals">116</part-num-ref>
+ produced by each channel 113A-D can be demodulated using conventional CDM demodulation techniques. Particular components (or channels) of resultant signal <part-num-ref name="produced by each channel 113A-D can be demodulated using conventional CDM demodulation techniques. Particular components (or channels) of resultant signal">116</part-num-ref>
+ produced in response to any modulation signal <part-num-ref name="produced in response to any modulation signal">1<confidence value="5">1</confidence>
+      </part-num-ref>
+ <confidence value="4">O</confidence>
+A-D can therefore be readily extracted. This concept can be exploited in myriad ways, as described below, to create a number of additional features and performance enhancements within sensor <part-num-ref name="number of additional features and performance enhancements within sensor">100.</part-num-ref>
+ A common modulation signal <part-num-ref name="common modulation signal">1<confidence value="5">1</confidence>
+      </part-num-ref>
+ <confidence value="4">O</confidence>
+A-D, for example, could be applied to multiple electrodes <confidence value="2">l</confidence>
+ <confidence value="1">l</confidence>
+2A-D to increase the size of any particular sensing zone within region <part-num-ref name="size of any particular sensing zone within region">101.</part-num-ref>
+ These zones can be readily adjusted during operation to create various operating modes or the like. To make the entire sensing region <part-num-ref name="entire sensing region">101</part-num-ref>
+ act as a single button, for example, each electrode 112A- D could be provided with the same modulation signal <part-num-ref name="same modulation signal">110</part-num-ref>
+ without otherwise adjusting the performance of the sensor. Because all of the signals resulting from receive electrode <part-num-ref name="signals resulting from receive electrode">116</part-num-ref>
+ are provided on a common path in FIG. 1, simply demodulating the entire received signal using the common modulation code will identify the presence of object <part-num-ref name="presence of object">121</part-num-ref>
+ anywhere within sensing region <part-num-ref name="anywhere within sensing region">101</part-num-ref>
+ in this case. Similar concepts can be applied to create any number of independent or overlapping sensing zones across sensing region <part-num-ref name="in this case. Similar concepts can be applied to create any number of independent or overlapping sensing zones across sensing region">101</part-num-ref>
+ through simple manipulation of digital code sequences <part-num-ref name="through simple manipulation of digital code sequences">106.</part-num-ref>
+ Furthermore, spatial frequency filtering can be done simply through proper modulation and demodulation, for example to accomplish palm rejection or to reject other inappropriate<confidence value="5">.</confidence>
+ inputs.    </p>
+    <p id="p-50" num="50">[0038] The demodulated signals <part-num-ref name="demodulated signals">118</part-num-ref>
+ are appropriately received at controller <part-num-ref name="are appropriately received at controller">102</part-num-ref>
+ so that the position-based attribute of object <part-num-ref name="position-based attribute of object">121</part-num-ref>
+ can be determined (step 208). These signals may be filtered digitally or as analog, using linear and non-linear filters. Various techniques for <boundary-data type="header">
+        <confidence value="88">12</confidence>
+      </boundary-data>
+      <page-break num="13"/>
+      <boundary-data type="header">UTILITY PATENT APPLICATION</boundary-data>
+      <boundary-data type="header">AT<confidence value="8">T</confidence>
+ORNEY DOCKET NO. 028.0013      </boundary-data>
+identifying the position of object <part-num-ref name="position of object">121</part-num-ref>
+ with respect to the various electrodes <part-num-ref name="various electrodes">
+        <confidence value="66">11</confidence>
+      </part-num-ref>
+ 2A-D include detection of peak electrical effect, computation of a centroid based upon the electrical effects, comparison of differences in electrical effects observed between electrodes 112A-D, comparison of changes in electrical effects over time, interpolation between signal channels from the electrodes, and/or according to many other techniques. In the case of peak detection, the position of object <part-num-ref name="position of object">121</part-num-ref>
+ is associated with one or more electrodes 112A-D by identifying which modulation signal 11<confidence value="4">0</confidence>
+A-D produced the greatest relative change of capacitive effect in resultant signal <part-num-ref name="greatest relative change of capacitive effect in resultant signal">116.</part-num-ref>
+ Sensing channels <part-num-ref name="greatest relative change of capacitive effect in resultant signal 116. Sensing channels">
+        <confidence value="66">11</confidence>
+      </part-num-ref>
+ 3A-D experiencing such peak (maximum, minimum, or otherwise distinct) electrical effects could also be identified by comparing currently-observed, scaled electrical effects to baseline values (e.g. average values for the particular channel that are empirically determined, averaged over time, stored from a previous observation, and/or the like). Still other embodiments could identify the channel 113A-D that produced peak electrical effects by comparing current electrical effects for each channel <part-num-ref name="channel 113A-D that produced peak electrical effects by comparing current electrical effects for each channel">
+        <confidence value="5">1</confidence>
+      </part-num-ref>
+ <confidence value="4">1</confidence>
+3A-D with current values observed in neighboring sensing channels.    </p>
+    <p id="p-51" num="51">Alternatively, a weighted average of the electrical effects observed from some or all of the modulated electrodes 112A-D can be computed, with this weighted average, or centroid, correlating to the position of object <part-num-ref name="position of object">121.</part-num-ref>
+ Many techniques for correlating electrical effects observed across sensing region <part-num-ref name="position of object 121. Many techniques for correlating electrical effects observed across sensing region">101</part-num-ref>
+ to a position of object <part-num-ref name="position of object">121</part-num-ref>
+ are known or may be subsequently developed, and any of these techniques may be used in various embodiments, according to the application.    </p>
+    <p id="p-52" num="52">
+      <confidence value="5">[</confidence>
+0039<confidence value="5">]</confidence>
+ By varying the digital codes <part-num-ref name="digital codes">106</part-num-ref>
+ used to create modulation signals 11<confidence value="4">0</confidence>
+A-D over time, various additional features can be implemented.  To implement a simple dual- differential digital-to-analog conversion for received signal channels <part-num-ref name="simple dual- differential digital-to-analog conversion for received signal channels">113,</part-num-ref>
+ for example, the digital code <part-num-ref name="digital code">106</part-num-ref>
+ applied to one or more electrodes <part-num-ref name="applied to one or more electrodes">112</part-num-ref>
+ is logically inverted (e.g. <confidence value="488">1's</confidence>
+ complement) on a periodic, aperiodic, or other time basis to obtain complementary sensed signals <part-num-ref name="periodic, aperiodic, or other time basis to obtain complementary sensed signals">116.</part-num-ref>
+ The complementary codes <part-num-ref name="complementary codes">106</part-num-ref>
+ can be used to drive two separate ADC inputs (e.g. ADCs present in driver <part-num-ref name="ADCs present in driver">115</part-num-ref>
+ and/or demodulator <part-num-ref name="and/or demodulator">117)</part-num-ref>
+ in opposite directions, thereby canceling out many types of variability or residual distortion in signal <part-num-ref name="in opposite directions, thereby canceling out many types of variability or residual distortion in signal">116.</part-num-ref>
+ Steps <part-num-ref name="in opposite directions, thereby canceling out many types of variability or residual distortion in signal 116. Steps">210</part-num-ref>
+ and <part-num-ref name="and">212</part-num-ref>
+ describe optional noise reconfiguration and image processing features, respectively, that may be enabled in various embodiments as additional benefits available from the use of spread spectrum techniques. These features are described in increasing detail below (in conjunction with FIGS. 3 and <part-num-ref name="and">4,</part-num-ref>
+ respectively), and may not be present within all embodiments. Because the digital codes <part-num-ref name="digital codes">106</part-num-ref>
+ are inherently simple to modify, store and <boundary-data type="header">
+        <confidence value="88">13</confidence>
+      </boundary-data>
+      <page-break num="14"/>
+      <boundary-data type="header">UTILITY PATENT APPLICATION</boundary-data>
+      <boundary-data type="header">ATTORNEY DOCKET NO. 028.00<confidence value="88">13</confidence>
+      </boundary-data>
+subsequently process, any number of signal enhancement, noise reduction and/or other performance improvements to sensor <part-num-ref name="are inherently simple to modify, store and subsequently process, any number of signal enhancement, noise reduction and/or other performance improvements to sensor">100</part-num-ref>
+ are enabled. Further, a relatively large number of digital codes are available due to the combinatorial power of digital sequences. Coding gain and orthogonality conventionally rely upon linearity and superposition of the particular codes used. Although non-linearity and dispersion limit the theoretical effectiveness of digital codes, these limitations can be more than offset by the increases in relative signal power (and thus SNR) that can result from simultaneously modulating more than one electrode <part-num-ref name="increases in relative signal power (and thus SNR) that can result from simultaneously modulating more than one electrode">112.</part-num-ref>
+ Further, since it is possible that self-induced inter-channel noise dominates over other noise sources in many embodiments, a relatively stable dynamic range can be provided.    </p>
+    <p id="p-53" num="53">
+      <confidence value="5">[</confidence>
+0040] Referring now to FIGS. 3A-B, spread spectrum techniques allow for improved noise avoidance as compared to conventional single-frequency sampling techniques. As noted above, a sensing zone may correspond to a single electrode <part-num-ref name="single electrode">112,</part-num-ref>
+ or a common modulation signal <part-num-ref name="common modulation signal">110</part-num-ref>
+ may be provided to multiple electrodes <part-num-ref name="may be provided to multiple electrodes">112</part-num-ref>
+ to create a larger sensing zone that effectively behaves as a single "electrode" for purposes of subsequent demodulation and computation. The modulated waveform <part-num-ref name="modulated waveform">110,</part-num-ref>
+ being the function of a distinct digital code <part-num-ref name="distinct digital code">106,</part-num-ref>
+ uniquely identifies the sensing zone to which it is applied, thereby allowing ready application of CDM and other conventional spread-spectrum techniques.    </p>
+    <p id="p-54" num="54">FIG. 3 shows an exemplary spectral plot <part-num-ref name="exemplary spectral plot">300</part-num-ref>
+ that emphasizes the frequency domain differences between the spectrum <part-num-ref name="spectrum">302</part-num-ref>
+ of carrier signal <part-num-ref name="of carrier signal">111</part-num-ref>
+ and the spectrum <part-num-ref name="spectrum">304</part-num-ref>
+ of modulated signal <part-num-ref name="of modulated signal">110.</part-num-ref>
+ In contrast to a single-frequency carrier signal <part-num-ref name="single-frequency carrier signal">302,</part-num-ref>
+ the multi- frequency spectrum <part-num-ref name="multi- frequency spectrum">304</part-num-ref>
+ of modulated signal received on <part-num-ref name="of modulated signal received on">114</part-num-ref>
+ is much wider. Because the spectrum <part-num-ref name="spectrum">304</part-num-ref>
+ of the modulated signal distributes available power across a much wider sensitivity band, the effects of narrowband<confidence value="1">*</confidence>
+ noise signals <part-num-ref name="effects of narrowband* noise signals">306</part-num-ref>
+ at or near any particular frequency of interest are significantly reduced. That is, if a spurious noise signal <part-num-ref name="spurious noise signal">306</part-num-ref>
+ happened to occur near a single-frequency (or narrowband) carrier signal <part-num-ref name="single-frequency (or narrowband) carrier signal">302,</part-num-ref>
+ any electrical effects present within the sensing channel <part-num-ref name="sensing channel">113</part-num-ref>
+ could be overwhelmed by the noise.    </p>
+    <p id="p-55" num="55">Moreover, adverse effects of wider-band noise 308 or interference from other modulated electrode channels <part-num-ref name="or interference from other modulated electrode channels">310</part-num-ref>
+ can be mitigated through spread-spectrum techniques, as shown in spectral plot <part-num-ref name="can be mitigated through spread-spectrum techniques, as shown in spectral plot">350</part-num-ref>
+ of received signal <part-num-ref name="of received signal">116.</part-num-ref>
+ Plot <part-num-ref name="of received signal 116. Plot">350</part-num-ref>
+ shows that the demodulated signal <part-num-ref name="demodulated signal">352</part-num-ref>
+ (corresponding to coupling of a channel <part-num-ref name="channel">113</part-num-ref>
+ and/or the presence of object <part-num-ref name="presence of object">121</part-num-ref>
+ near the demodulated sensing region) is contained within a relatively narrow frequency band, whereas signals <part-num-ref name="relatively narrow frequency band, whereas signals">354</part-num-ref>
+ received from other channels are spread across a wider band. Both <boundary-data type="header">
+        <confidence value="88">14</confidence>
+      </boundary-data>
+      <page-break num="15"/>
+      <boundary-data type="header">UTILITY PAT<confidence value="8">E</confidence>
+NT APPLICATION      </boundary-data>
+      <boundary-data type="header">ATTORNEY DOCKET NO. 028.00<confidence value="88">13</confidence>
+      </boundary-data>
+wideband noise <part-num-ref name="wider band. Both wideband noise">308</part-num-ref>
+ and narrow band noise <part-num-ref name="and narrow band noise">306</part-num-ref>
+ are similarly spread across wider frequency bands <part-num-ref name="are similarly spread across wider frequency bands">356</part-num-ref>
+ and <part-num-ref name="and">358</part-num-ref>
+ in the demodulated signal. By increasing the bandwidth of the applied modulated signal <part-num-ref name="applied modulated signal">110,</part-num-ref>
+ then, the signal-to-noise ratio in the demodulated signal <part-num-ref name="demodulated signal">116</part-num-ref>
+ is improved dramatically. The demodulation in turn spreads the noise outside of the signal band, which then becomes quite narrow, thereby allowing the desired signal portion <part-num-ref name="desired signal portion">352</part-num-ref>
+ to be readily extracted by a narrow band filter or the like.    </p>
+    <p id="p-56" num="56">
+      <confidence value="5">[</confidence>
+0041] This concept can be further exploited by selecting digital codes 106 that avoid known sources of noise. That is, digital codes <part-num-ref name="that avoid known sources of noise. That is, digital codes">106</part-num-ref>
+ of any bit length may be applied to carrier signal <part-num-ref name="of any bit length may be applied to carrier signal">111</part-num-ref>
+ to create spectral "gaps" at frequencies known to be susceptible to spurious noise. By applying conventional Fourier analysis (e.g. using a simple fast Fourier transform (FFT) or the like), digital codes can be selected to create modulation signals <part-num-ref name="like), digital codes can be selected to create modulation signals">110</part-num-ref>
+ having many desired spectral characteristics. Codes applied to any modulated electrode <part-num-ref name="having many desired spectral characteristics. Codes applied to any modulated electrode">112</part-num-ref>
+ can be modified during operation (e.g. step <part-num-ref name="step">210</part-num-ref>
+ in FIG. 2) and/or may be pre-selected to avoid expected or observed noise in resultant signals <part-num-ref name="and/or may be pre-selected to avoid expected or observed noise in resultant signals">116.</part-num-ref>
+ Alternatively, the particular codes <part-num-ref name="particular codes">106</part-num-ref>
+ applied to one or more electrodes <part-num-ref name="applied to one or more electrodes">112</part-num-ref>
+ may be randomly, pseudo-randomly, deterministically or otherwise modified during sensor operation, thereby statistically filtering any noise present within resultant signals <part-num-ref name="may be randomly, pseudo-randomly, deterministically or otherwise modified during sensor operation, thereby statistically filtering any noise present within resultant signals">116</part-num-ref>
+ or demodulated signals <part-num-ref name="or demodulated signals">118</part-num-ref>
+ over time. Similarly, particular spatial frequencies or spatial positions can be emphasized (e.g.    </p>
+    <p id="p-57" num="57">with code gain) or filtered out by the codes applied to different modulation electrodes. Code shifting during operation may provide other benefits (e.g. discrimination of or resilience to moisture) in addition to reducing the effects of noise or spurious effects of non-input objects (palm etc). In various equivalent embodiments, the frequency, phase, amplitude and/or waveform of carrier signal <part-num-ref name="frequency, phase, amplitude and/or waveform of carrier signal">111</part-num-ref>
+ may be adjusted in place of or in addition to modifying digital codes <part-num-ref name="may be adjusted in place of or in addition to modifying digital codes">106.</part-num-ref>
+    </p>
+    <p id="p-58" num="58">[0042<confidence value="5">]</confidence>
+ With reference now to FIG. 4, spread spectrum techniques that simultaneously apply multiple coded modulation signals 11<confidence value="4">0</confidence>
+A-D to various electrodes <confidence value="66">11</confidence>
+ 2A-D are able to identify multiple presences <part-num-ref name="2A-D are able to identify multiple presences">408,</part-num-ref>
+ <part-num-ref name="2A-D are able to identify multiple presences 408,">410,</part-num-ref>
+ <part-num-ref name="2A-D are able to identify multiple presences 408, 410,">412</part-num-ref>
+ of objects <part-num-ref name="of objects">121</part-num-ref>
+ located within sensing region <part-num-ref name="located within sensing region">101.</part-num-ref>
+    </p>
+    <p id="p-59" num="59">Multiple objects may correspond to the presence of multiple fingers on a touchpad, for example, a palm resting on sensor <part-num-ref name="palm resting on sensor">100</part-num-ref>
+ during use, simultaneous presence of a finger and a stylus, and/or any other combination of inputs. Electrical effects resulting from the various presences <part-num-ref name="various presences">408,</part-num-ref>
+ <part-num-ref name="various presences 408,">410</part-num-ref>
+ can be conceptually projected along one or more axes <part-num-ref name="can be conceptually projected along one or more axes">404,</part-num-ref>
+ <part-num-ref name="can be conceptually projected along one or more axes 404,">406</part-num-ref>
+ to identify the relative positions of the objects along that axis, as shown in FIG. 4. That is, peak value(s) of electrical effects can be correlated to relative positions of objects <part-num-ref name="objects along that axis, as shown in FIG. 4. That is, peak value(s) of electrical effects can be correlated to relative positions of objects">121</part-num-ref>
+ with <boundary-data type="header">
+        <confidence value="88">15</confidence>
+      </boundary-data>
+      <page-break num="16"/>
+      <boundary-data type="header">UTILITY PATENT APPLICATION</boundary-data>
+      <boundary-data type="header">
+        <confidence value="222222222">ATI'ORNEY</confidence>
+ DOCKET NO. 028.0013      </boundary-data>
+respect to sensing region <part-num-ref name="with respect to sensing region">101.</part-num-ref>
+ In the example of FIG. 4, a finger <part-num-ref name="finger">408</part-num-ref>
+ may be identified by increases in electrical effects projected along an "X" axis <part-num-ref name="&quot;X&quot; axis">404</part-num-ref>
+ and a "Y" axis <part-num-ref name="&quot;Y&quot; axis">406.</part-num-ref>
+ By correlating the relative X and Y positions of peak electrical effects, the location of presence <part-num-ref name="location of presence">408</part-num-ref>
+ can be correlated in two dimensions (or any other number of dimensions). Similarly, the example of FIG. 4A shows a larger area indicating a second presence <part-num-ref name="second presence">410</part-num-ref>
+ that results projections of electrical effects in axes <part-num-ref name="that results projections of electrical effects in axes">404</part-num-ref>
+ and <part-num-ref name="and">406.</part-num-ref>
+ These multiple projections of electrical effect can be additionally correlated to identify images (e.g. "outlines") of objects <part-num-ref name="&quot;outlines&quot;) of objects">121</part-num-ref>
+ present within region <part-num-ref name="present within region">101.</part-num-ref>
+ Taking this concept further, one or more images <part-num-ref name="present within region 101. Taking this concept further, one or more images">408,</part-num-ref>
+ <part-num-ref name="present within region 101. Taking this concept further, one or more images 408,">410</part-num-ref>
+ may be subsequently processed as appropriate. Presence of multiple fingers within region <part-num-ref name="may be subsequently processed as appropriate. Presence of multiple fingers within region">101</part-num-ref>
+ may be used to perform scrolling, mode selection or other tasks, for example. Similarly, if an image can be identified as resulting from a user's palm<confidence value="6">.</confidence>
+ (or another undesired portion of the user's body), that image <part-num-ref name="user's body), that image">410</part-num-ref>
+ can be subsequently rejected in future processing, such as reporting of positional information or other output signals.    </p>
+    <p id="p-60" num="60">
+      <confidence value="5">[</confidence>
+0043<confidence value="5">]</confidence>
+ In the exemplary embodiment shown in FIG. 4, the two axes <part-num-ref name="two axes">404,</part-num-ref>
+ <part-num-ref name="two axes 404,">406</part-num-ref>
+ generally correspond to portions of modulated electrodes <part-num-ref name="generally correspond to portions of modulated electrodes">112</part-num-ref>
+ or their associated channels shown arranged in two approximately orthogonal directions as in FIG <confidence value="4">1</confidence>
+B. Alternate embodiments, however, may include any number of electrodes <part-num-ref name="or their associated channels shown arranged in two approximately orthogonal directions as in FIG 1B. Alternate embodiments, however, may include any number of electrodes">112</part-num-ref>
+ arranged in any overlapping, non- overlapping, matrix or other arrangement. An example of a sensor <part-num-ref name="sensor">500</part-num-ref>
+ with overlapping electrodes 112A-G arranged in two dimensions is shown in FIG. 5. In such embodiments, electrical effects on received channels can effectively be independently measured at each crossing of the electrodes in two directions (e.g. X and Y directions corresponding to axes of <part-num-ref name="X and Y directions corresponding to axes of">404,</part-num-ref>
+ <part-num-ref name="X and Y directions corresponding to axes of 404,">406</part-num-ref>
+ in contour plot 400), with the results correlated in controller <part-num-ref name="results correlated in controller">102</part-num-ref>
+ to provide a two- dimensional representation or image of object <part-num-ref name="two- dimensional representation or image of object">121</part-num-ref>
+ rather than two one-dimensional "silhouettes" like <part-num-ref name="rather than two one-dimensional &quot;silhouettes&quot; like">404</part-num-ref>
+ and <part-num-ref name="and">406.</part-num-ref>
+ In such cases, electrodes arranged in the first direction (e.g.    </p>
+    <p id="p-61" num="61">electrodes 112A-C) may be modulated at separate times from electrodes arranged in the second direction (e.g. electrodes 112D-G), with one or more independent received signals <part-num-ref name="electrodes 112D-G), with one or more independent received signals">116</part-num-ref>
+ at any one time from either set of electrodes (e.g. electrodes 112D&amp;F) being provided to demodulator <part-num-ref name="electrodes 112D&amp;F) being provided to demodulator">117</part-num-ref>
+ via a multiplexer <part-num-ref name="multiplexer">502.</part-num-ref>
+ FIG. 5 shows the various electrodes 112A-G coupled to both modulator <part-num-ref name="various electrodes 112A-G coupled to both modulator">107</part-num-ref>
+ and demodulator <part-num-ref name="and demodulator">117</part-num-ref>
+ via a multiplexer <part-num-ref name="multiplexer">502.</part-num-ref>
+ The multiplexer may also connect one or more of the electrodes to receiving circuitry <part-num-ref name="electrodes to receiving circuitry">115</part-num-ref>
+ before demodulation. In practice, each electrode may be connected in any manner to allow signals to be applied on one subset of electrodes <part-num-ref name="before demodulation. In practice, each electrode may be connected in any manner to allow signals to be applied on one subset of electrodes">112</part-num-ref>
+ and received on another subset.    </p>
+    <boundary-data type="header">
+      <confidence value="88">16</confidence>
+    </boundary-data>
+    <boundary-data type="header">UTILITY PATENT APPLICATION</boundary-data>
+    <boundary-data type="header">ATTORNEY DOCKET NO. 028.0013</boundary-data>
+    <p id="p-62" num="62">
+      <page-break num="17"/>
+[0044] In various embodiments, two or more electrodes which serve to receive channels (e.g. analogous to channel <part-num-ref name="analogous to channel">113</part-num-ref>
+ described above) may be provided with independent resultant signals <part-num-ref name="described above) may be provided with independent resultant signals">116.</part-num-ref>
+ Further, inactive or unused electrodes (e.g. 112E&amp;G may be coupled to an electrical reference (e.g. ground) or driven with a modulated signal to improve spatial resolution on the active receive channels. This reference is commonly referenced as a shield or guard signal, which may be applied via multiplexing logic <part-num-ref name="shield or guard signal, which may be applied via multiplexing logic">502</part-num-ref>
+ or the like.    </p>
+    <p id="p-63" num="63">[0045] Digital coding and other spread-spectrum techniques may be equivalently applied in sensors that operate in any number of different manners. FIG. 6A, for example, shows an exemplary sensor <part-num-ref name="exemplary sensor">600</part-num-ref>
+ that includes any number of modulated electrodes 112A-B arranged in any single or multi-dimensional fashion that are coupled to a capacitive filter (e.g. an integrating capacitor <part-num-ref name="integrating capacitor">610)</part-num-ref>
+ which linearly transforms the charge transferred by the modulated electrodes. A microcontroller 102/104 or the like suitably generates distinct digital codes <part-num-ref name="like suitably generates distinct digital codes">106</part-num-ref>
+ that modulate 112A-B coupled to <part-num-ref name="that modulate 112A-B coupled to">114</part-num-ref>
+ electrode as described above. In this case, however, the digital codes <part-num-ref name="digital codes">106</part-num-ref>
+ are not necessarily intended to encode the voltage provided to each electrode 112A-B, but rather to control the timing of charge that is transferred to <part-num-ref name="timing of charge that is transferred to">114.</part-num-ref>
+ By controlling the timing of each electrode's charging and discharging and then observing the amount of charge collected at integrating capacitor <part-num-ref name="amount of charge collected at integrating capacitor">610</part-num-ref>
+ from <part-num-ref name="from">114,</part-num-ref>
+ the amount of charge provided by each electrode 112A-B can be determined from the demodulated signal <part-num-ref name="demodulated signal">118.</part-num-ref>
+ The charging of each electrode 112A-B can be controlled by selecting digital codes <part-num-ref name="charging of each electrode 112A-B can be controlled by selecting digital codes">106</part-num-ref>
+ such that voltage is applied to each electrode only when charge should be transferred to the receiving electrode <part-num-ref name="receiving electrode">114,</part-num-ref>
+ and otherwise allowing it to float. By selectively providing charge from individual <confidence value="222222">and/or</confidence>
+ groups of electrodes <confidence value="55">11</confidence>
+2A-B to capacitor <part-num-ref name="receiving electrode 114, and otherwise allowing it to float. By selectively providing charge from individual and/or groups of electrodes 112A-B to capacitor">610,</part-num-ref>
+ the amount of coupling from each electrode 112A-B (which is affected by the proximity of an object <part-num-ref name="object">121)</part-num-ref>
+ can be determined.    </p>
+    <p id="p-64" num="64">
+      <confidence value="5">[</confidence>
+0046<confidence value="5">]</confidence>
+ FIG. 6B presents an alternate embodiment of an exemplary sensor that has unified sensing and driving on each electrode <part-num-ref name="exemplary sensor that has unified sensing and driving on each electrode">112</part-num-ref>
+ that is filtered or demodulated by one or more capacitors <part-num-ref name="that is filtered or demodulated by one or more capacitors">610.</part-num-ref>
+ The codes <part-num-ref name="codes">106</part-num-ref>
+ modulate drive circuitry <part-num-ref name="modulate drive circuitry">109,</part-num-ref>
+ which may be implemented as a current source connected to the electrodes <part-num-ref name="electrodes">112.</part-num-ref>
+ The response of the electrode to the drive circuitry is affected by the coupling of an object <part-num-ref name="object">121</part-num-ref>
+ near the electrode, and the resultant signals (e.g. the voltage resulting from the coupling) are filtered and/or demodulated by the circuit <part-num-ref name="circuit">604</part-num-ref>
+ and capacitor <part-num-ref name="and capacitor">610.</part-num-ref>
+ The filtered signals may be further demodulated to determine position attributes of the object. Further, more than one electrode could be simultaneously driven with substantially orthogonal codes and after demodulation a stable coupling of one <boundary-data type="header">
+        <confidence value="88">17</confidence>
+      </boundary-data>
+      <page-break num="18"/>
+      <boundary-data type="header">UTILITY PATENT APPLICATION</boundary-data>
+      <boundary-data type="header">ATTORNEY DOCKET NO. 028.0013</boundary-data>
+electrode <confidence value="66">11</confidence>
+2A to another electrode 112B would substantially cancel out. These and many other position sensing methods benefit from digital coding and spread spectrum techniques.    </p>
+    <p id="p-65" num="65">[0047<confidence value="5">]</confidence>
+ With reference now to FIG. 7, various sensors 700 formed in accordance with the coding techniques described herein may be formed on a single circuit board or other substrate <part-num-ref name="single circuit board or other substrate">702.</part-num-ref>
+ In such embodiments, electrodes <confidence value="54">11</confidence>
+2A-G forming sensing region <part-num-ref name="single circuit board or other substrate 702. In such embodiments, electrodes 112A-G forming sensing region">101</part-num-ref>
+ may be disposed on one side of the substrate, with the processing components (e.g. controller <part-num-ref name="controller">102</part-num-ref>
+ and the like) formed on the opposite side. Because various sensors (e.g. sensors <part-num-ref name="sensors">100</part-num-ref>
+ and <part-num-ref name="and">500</part-num-ref>
+ shown in FIGS. 1 and <part-num-ref name="and">5)</part-num-ref>
+ do not require physical movement of sensing and receiving electrodes <part-num-ref name="do not require physical movement of sensing and receiving electrodes">112,</part-num-ref>
+ <part-num-ref name="do not require physical movement of sensing and receiving electrodes 112,">114</part-num-ref>
+ with respect to each other, electrodes <part-num-ref name="with respect to each other, electrodes">112,</part-num-ref>
+ <part-num-ref name="with respect to each other, electrodes 112,">114</part-num-ref>
+ in such sensors may be rigidly fixed on substrate <part-num-ref name="in such sensors may be rigidly fixed on substrate">702</part-num-ref>
+ in any manne<confidence value="8">r</confidence>
+. Substrate <part-num-ref name="in any manner. Substrate">702</part-num-ref>
+ can be made of a flexible material to allow for folding or bending. Further, a protective surface <part-num-ref name="protective surface">704</part-num-ref>
+ may be deposited or otherwise placed over the electrodes to provide consistent dielectric isolation and to protect against moisture, dust and other environmental effects. Surface <part-num-ref name="electrodes to provide consistent dielectric isolation and to protect against moisture, dust and other environmental effects. Surface">704</part-num-ref>
+ may also provide tactile feedback to the user as appropriate. FIG. 8 shows an exemplary sensor <part-num-ref name="exemplary sensor">800</part-num-ref>
+ is formed on a flexible substrate <part-num-ref name="flexible substrate">802</part-num-ref>
+ as appropriate. FIG. 8 also shows that the various processing components may be found on the same side of substrate <part-num-ref name="same side of substrate">802</part-num-ref>
+ as the modulated and sensing electrodes , and that the substrate <part-num-ref name="substrate">802</part-num-ref>
+ may also provide tactile feedback for region <part-num-ref name="may also provide tactile feedback for region">101.</part-num-ref>
+ It should be appreciated that the various concepts, structures, components and techniques described herein may be inter-combined and/or modified as appropriate to create a wide variety of alternate embodiments.    </p>
+    <p id="p-66" num="66">
+      <confidence value="5">[</confidence>
+0048<confidence value="5">]</confidence>
+ Accordingly, there are provided numerous systems, devices and processes for detecting a position-based attribute of a finger, stylus or other object in a position sensing device such as a touchpad. While at least one exemplary embodiment has been presented in the foregoing detailed description, it should be appreciated that a vast number of variations exist. The various steps of the techniques described herein, for example, may be practiced in any temporal order, and are not limited to the order presented and/or claimed herein. It should also be appreciated that the exemplary embodiments described herein are only examples, and are not intended to limit the scope, applicability, or configuration of the invention in any way. Various changes can therefore be made in the function and arrangement of elements without departing from the scope of the invention as set forth in the appended claims and the legal equivalents thereof.    </p>
+    <boundary-data type="header">
+      <confidence value="88">18</confidence>
+    </boundary-data>
+  </description>
+</us-patent-application>
+

prior_art/11291352.xml

@@ -0,0 +1,84 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11291352</doc-number>
+        <date>2009-04-02</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <boundary-data type="header">U.S. Application No.: 11/291,352  Attorney Docket No.: <confidence value="65">OI</confidence>
+D05-01(01201)    </boundary-data>
+    <boundary-data type="header">-15-</boundary-data>
+    <heading id="h-1">IN THE SPECIFICATION</heading>
+    <p id="p-1" num="1">Please enter the following amendment to the Specification:</p>
+    <p id="p-2" num="2">Please replace the paragraph at page <part-num-ref name="paragraph at page">13</part-num-ref>
+ line <part-num-ref name="line">14</part-num-ref>
+ to page <part-num-ref name="to page">14</part-num-ref>
+ line <part-num-ref name="line">10</part-num-ref>
+ with the following:    </p>
+    <p id="p-3" num="3">Figure 6 is a block diagram showing further details of an e<confidence value="5118">ampe</confidence>
+ exem<confidence value="8">p</confidence>
+lar<confidence value="8">y</confidence>
+ software architecture of a collaboration manager <part-num-ref name="collaboration manager">151</part-num-ref>
+ operable to maintain metadata providing access to applications <part-num-ref name="operable to maintain metadata providing access to applications">130</part-num-ref>
+ on behalf of users <part-num-ref name="on behalf of users">120</part-num-ref>
+ logged into the workspace. In this example, the collaboration manager <part-num-ref name="collaboration manager">151</part-num-ref>
+ includes a web interface <part-num-ref name="web interface">114,</part-num-ref>
+ a workspace server <part-num-ref name="workspace server">136,</part-num-ref>
+ and a resource framework <part-num-ref name="resource framework">140</part-num-ref>
+ having adaptors 142-1<confidence value="88">..</confidence>
+142-N <part-num-ref name="having adaptors 142-1..142-N">(142</part-num-ref>
+ generally) for each application <part-num-ref name="generally) for each application">130</part-num-ref>
+ that the server <part-num-ref name="server">110</part-num-ref>
+ supports. The workspace server <part-num-ref name="workspace server">136</part-num-ref>
+ 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>
+ within the resource framework <part-num-ref name="resource framework">140.</part-num-ref>
+ The <confidence value="22222222">adaptors</confidence>
+ adapter<confidence value="86">s-</confidence>
+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>
+ to control an application <part-num-ref name="application">130</part-num-ref>
+ 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>
+ for storage of application data <part-num-ref name="for storage of application data">134</part-num-ref>
+ by the application <part-num-ref name="application">130,</part-num-ref>
+ and to control general operational features of the application such as transmission<confidence value="188">-of</confidence>
+ electronic mail, creation of calendar appointments, and so forth. Depending upon the application, the ada<confidence value="7">p</confidence>
+tors <confidence value="686666655">adapter-1</confidence>
+42 can allow the workspaces <part-num-ref name="workspaces">150</part-num-ref>
+ to present a graphical user interface of the applications <part-num-ref name="applications">130</part-num-ref>
+ (some or all) to a user <part-num-ref name="user">120</part-num-ref>
+ of the workspace <part-num-ref name="workspace">150</part-num-ref>
+ as if that user were independently operating the application in standalone mode<confidence value="5">.</confidence>
+ (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>
+tor adapte<confidence value="665">r-1</confidence>
+42 can simply relay data from the application <part-num-ref name="application">130</part-num-ref>
+ to the workspace <part-num-ref name="workspace">150</part-num-ref>
+ 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>
+    </p>
+    <p id="p-4" num="4">In such a case, the application <part-num-ref name="application">130</part-num-ref>
+ can be used for its back-end (i.e. non- <page-break num="2"/>
+      <boundary-data type="header">U.S. Application No.: 11/291,352  Attorney Docket No.: <confidence value="656">OID</confidence>
+05-01(01201)      </boundary-data>
+      <boundary-data type="header">-16-</boundary-data>
+graphical) processing capabilities and the presentation of the application data <part-num-ref name="application data">134</part-num-ref>
+ to the user <part-num-ref name="user">120</part-num-ref>
+ is left up to the workspace <part-num-ref name="workspace">150.</part-num-ref>
+ In either configuration, the applications <part-num-ref name="applications">130</part-num-ref>
+ can be replaced with different versions of software <confidence value="414568888888">form-fromthe</confidence>
+ same or from different vendors, and only the ada<confidence value="8">p</confidence>
+tor adapter-may (or may not) need to be changed to accommodate the new version of the application.    </p>
+    <p id="p-5" num="5">Please replace the paragraph at page <part-num-ref name="paragraph at page">23</part-num-ref>
+ lines 1-16 with the following:    </p>
+    <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>
+non-writeable storage media such as ROM devices, or b) information alterably stored on ta<confidence value="28614">ngike</confidence>
+-writeable storage media <confidence value="2222222">such'as</confidence>
+ floppy disks, magnetic tapes, <confidence value="5">C</confidence>
+Ds, RAM devices, and other magnetic and optical media. The operations and methods may be implemented in a software executable object.    </p>
+    <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>
+ may be stored in a database of any type.    </p>
+  </description>
+</us-patent-application>
+

prior_art/11335902.xml

@@ -0,0 +1,748 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11335902</doc-number>
+        <date>2006-01-18</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <heading id="h-1">FINDING PHISHING SITES</heading>
+    <heading id="h-2">BACKGROUND</heading>
+    <p id="p-1" num="1">
+      <confidence value="5">[</confidence>
+0001]   Phishing (correctly spelled starting with a "ph" in the English language) generally refers to the concept of tricking a computer user into submitting personal information, ordinarily financial-related data, to a bogus website.    </p>
+    <p id="p-2" num="2">Phishing and its variants (phish, phished, and so forth) also refer to the techniques used to trick users. Phishing is typically used to obtain the submitted information for fraudulent criminal use.</p>
+    <p id="p-3" num="3">[0002]   One common type of phishing tactic is to send a large number of users an email message containing a link in the message contents, with the identity of the message sender and the message content arranged to look like the source is a legitimate business. The message may indicate that the user needs to resubmit some personal data so that the business can continue to serve the user, such as to restore financial information that the business lost. The link, however, is to a bogus website that, if carefully constructed, may look virtually identical to the pages offered by the legitimate <boundary-data type="header">
+        <confidence value="8">-</confidence>
+ <confidence value="8">1</confidence>
+ <confidence value="8">-</confidence>
+      </boundary-data>
+      <page-break num="2"/>
+site. Because links are difficult to read, and can even use foreign characters that look like normal characters to the user, some users are fooled into clicking the link, and often thereafter submit valuable data.    </p>
+    <p id="p-4" num="4">[0003]   Presently, legitimate enterprises fight phishing in a number of ways. For one, possible phishing sites are voluntarily identified by users, and their complaints may be investigated. Well-known, legitimate internet access providers and/or computing services such as Microsoft Corporation<confidence value="8">'</confidence>
+s Hotmail service provide mechanisms that facilitate user reporting of junk mail and suspicious sites.    </p>
+    <p id="p-5" num="5">Other schemes (e.g., closely monitored, specially-created seeded dummy email addresses) look for unsolicited junk email and emails likely directed to obtaining information fraudulently. When some threshold is met with respect to identifying an email / site as possibly suspicious, e.g., a certain amount of users have submitted a complaint regarding the same message, an expert "hand" grader working for the legitimate service evaluates the message and linked-to site, and determines whether the message and/or access to the site should be blocked.</p>
+    <boundary-data type="header">
+      <confidence value="8">-</confidence>
+ <confidence value="8">2</confidence>
+ <confidence value="8">-</confidence>
+    </boundary-data>
+    <p id="p-6" num="6">
+      <page-break num="3"/>
+[0004]   While the above model works to prevent phishing to an extent, users on the order of hundreds of millions may experience and submit complaints that in turn result in tens of thousands of reports being generated every day. This overwhelms an enterprise's ability to hand grade the sites.    </p>
+    <p id="p-7" num="7">At the same time, phishing sites are known to operate for as little as a few hours or so, e.g., before reformulating the email message and/or moving to a different address, and thus any message / site blocking performed by a service needs to be quickly implemented.</p>
+    <heading id="h-3">SUMMARY</heading>
+    <p id="p-8" num="8">[0005]   This Summary is provided to introduce a selection of representative concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used in any way that would limit the scope of the claimed subject matter.</p>
+    <boundary-data type="header">
+      <confidence value="8">-</confidence>
+ <confidence value="8">3</confidence>
+ <confidence value="8">-</confidence>
+    </boundary-data>
+    <p id="p-9" num="9">
+      <page-break num="4"/>
+[0006]   Briefly, various aspects of the subject matter described herein are directed towards processing data from at least one data source related to phishing sites, and using a predictive model to determine whether a site is likely to be a phishing site. For example, processing the data may comprise generating a report for each of a plurality of data sources, aggregating the reports and applying the predictive model to the aggregated reports. The predictive model may be built using machine learning based on training data, e.g., including known phishing sites and/or known non-phishing sites.    </p>
+    <p id="p-10" num="10">[0007]   Various means for determining whether an object corresponding to a site is likely a phishing-related object are described, including determining the likelihood based on one or more features when evaluated against the aggregated data. The determination may be output in some way, e.g., made available to a reputation service, used to block access to a site or warn a user before allowing access, and/or used to assist a hand grader in being more efficient in evaluating sites.</p>
+    <p id="p-11" num="11">[0008]   The model is strengthened by aggregating phishing- related data from a plurality of sources, which, for example, <boundary-data type="header">
+        <confidence value="7">-</confidence>
+ <confidence value="77">4-</confidence>
+      </boundary-data>
+      <page-break num="5"/>
+may include at least one source corresponding to an email service and at least one source corresponding to an internet access service. The features and properties of each site may be logged, and used to develop more accurate training data.    </p>
+    <p id="p-12" num="12">The model is strengthened further by using known phishing sites as well as known non-phishing sites, e.g., sites that appear to have features that would indicate phishing, but in actuality have been graded as non-phishing sites.</p>
+    <p id="p-13" num="13">[0009]   Other advantages may become apparent from the following detailed description when taken in conjunction with the drawings.</p>
+    <heading id="h-4">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
+    <p id="p-14" num="14">[0010]   The present invention is illustrated by way of example and not limited in the accompanying figures in which like reference numerals indicate similar elements and in which:</p>
+    <p id="p-15" num="15">[0011]   FIGURE 1 shows an illustrative example of a general- purpose computing environment into which various aspects of the present invention may be incorporated.</p>
+    <boundary-data type="header">
+      <confidence value="8">-</confidence>
+ <confidence value="8">5</confidence>
+ <confidence value="8">-</confidence>
+    </boundary-data>
+    <p id="p-16" num="16">
+      <page-break num="6"/>
+[0012]   FIG. 2 is a block diagram generally representing the accumulation of phishing-related data obtained from clients.    </p>
+    <p id="p-17" num="17">[0013]   FIG. 3 is a block diagram representing an example architecture for processing phishing-related data.</p>
+    <p id="p-18" num="18">[0014]   FIG. 4 is an example flow diagram representing various criteria used to classify phishing-related data.</p>
+    <p id="p-19" num="19">[0015]   FIG. 5 is a block diagram representing an example architecture for training an evaluation mechanism to differentiate among likely phishing sites and likely non- phishing sites using known phishing-related data.</p>
+    <heading id="h-5">DETAILED DESCRIPTION</heading>
+    <heading id="h-6">EXEMPLARY OPERATING ENVIRONMENT</heading>
+    <p id="p-20" num="20">[0016]   FIGURE 1 illustrates an example of a suitable computing system environment <part-num-ref name="suitable computing system environment">100</part-num-ref>
+ on which the invention may be implemented. The computing system environment <part-num-ref name="computing system environment">100</part-num-ref>
+ 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 <boundary-data type="header">
+        <confidence value="8">-</confidence>
+ <confidence value="8">6</confidence>
+ <confidence value="8">-</confidence>
+      </boundary-data>
+      <page-break num="7"/>
+environment <part-num-ref name="computing environment">100</part-num-ref>
+ 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>
+    </p>
+    <p id="p-21" num="21">[0017]   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, tablet devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.</p>
+    <p id="p-22" num="22">[0018]   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, and so forth, which perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where <boundary-data type="header">
+        <confidence value="277">-7-</confidence>
+      </boundary-data>
+      <page-break num="8"/>
+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 local and/or remote computer storage media including memory storage devices.    </p>
+    <p id="p-23" num="23">[0019]   With reference to FIG. 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>
+ Components of the computer <part-num-ref name="computer">110</part-num-ref>
+ may include, but are not limited to, a processing unit <part-num-ref name="processing unit">120,</part-num-ref>
+ a system memory <part-num-ref name="system memory">130,</part-num-ref>
+ and a system bus <part-num-ref name="system bus">121</part-num-ref>
+ that couples various system components including the system memory to the processing unit <part-num-ref name="processing unit">120.</part-num-ref>
+ The system bus <part-num-ref name="system bus">121</part-num-ref>
+ 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>
+    <boundary-data type="header">
+      <confidence value="8">-</confidence>
+ <confidence value="8">8</confidence>
+ <confidence value="8">-</confidence>
+    </boundary-data>
+    <p id="p-24" num="24">
+      <page-break num="9"/>
+[0020]   The computer <part-num-ref name="computer">110</part-num-ref>
+ typically includes a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by the computer <part-num-ref name="computer">110</part-num-ref>
+ and includes both volatile and nonvolatile media, and removable and non-removable media. By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes 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, EEPROM, 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 the computer <part-num-ref name="computer">110.</part-num-ref>
+ 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 <boundary-data type="header">
+        <confidence value="8">-</confidence>
+ <confidence value="8">9</confidence>
+ <confidence value="8">-</confidence>
+      </boundary-data>
+      <page-break num="10"/>
+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, R<confidence value="5">F</confidence>
+, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer- readable media.    </p>
+    <p id="p-25" num="25">[0021]   The system memory <part-num-ref name="system memory">130</part-num-ref>
+ 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>
+ and random access memory (RAM) <part-num-ref name="and random access memory (RAM)">132.</part-num-ref>
+ A basic input/output system <part-num-ref name="basic input/output system">133</part-num-ref>
+ (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>
+ 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>
+ 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>
+ 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>
+ By way of example, and not limitation, FIG. 1 illustrates operating system <part-num-ref name="illustrates operating system">134,</part-num-ref>
+ application programs <part-num-ref name="illustrates operating system 134, application programs">135,</part-num-ref>
+ other program modules <part-num-ref name="illustrates operating system 134, application programs 135, other program modules">136</part-num-ref>
+ and program data <part-num-ref name="and program data">137.</part-num-ref>
+    </p>
+    <boundary-data type="header">- 10 -</boundary-data>
+    <p id="p-26" num="26">
+      <page-break num="11"/>
+[0022]   The computer <part-num-ref name="computer">110</part-num-ref>
+ may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only, FIG. 1 illustrates a hard disk drive <part-num-ref name="hard disk drive">141</part-num-ref>
+ that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive <part-num-ref name="magnetic disk drive">151</part-num-ref>
+ that reads from or writes to a removable, nonvolatile magnetic disk <part-num-ref name="removable, nonvolatile magnetic disk">152,</part-num-ref>
+ and an optical disk drive <part-num-ref name="optical disk drive">155</part-num-ref>
+ that reads from or writes to a removable, nonvolatile optical disk <part-num-ref name="removable, nonvolatile optical disk">156</part-num-ref>
+ 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. The hard disk drive <part-num-ref name="hard disk drive">141</part-num-ref>
+ is typically connected to the system bus <part-num-ref name="system bus">121</part-num-ref>
+ through a non- removable memory interface such as interface <part-num-ref name="non- removable memory interface such as interface">140,</part-num-ref>
+ and magnetic disk drive <part-num-ref name="non- removable memory interface such as interface 140, and magnetic disk drive">151</part-num-ref>
+ and optical disk drive <part-num-ref name="and optical disk drive">155</part-num-ref>
+ are typically connected to the system bus <part-num-ref name="system bus">121</part-num-ref>
+ by a removable memory interface, such as interface <part-num-ref name="removable memory interface, such as interface">150.</part-num-ref>
+    </p>
+    <p id="p-27" num="27">[0023]   The drives and their associated computer storage media, described above and illustrated in FIG. 1, provide <boundary-data type="header">- 11 -</boundary-data>
+      <page-break num="12"/>
+storage of computer-readable instructions, data structures, program modules and other data for the computer <part-num-ref name="computer">110.</part-num-ref>
+ <confidence value="5">I</confidence>
+n FIG.    </p>
+    <p id="p-28" num="28">1, for example, hard disk drive 141 is illustrated as storing operating system <part-num-ref name="is illustrated as storing operating system">144,</part-num-ref>
+ application programs <part-num-ref name="is illustrated as storing operating system 144, application programs">145,</part-num-ref>
+ other program modules <part-num-ref name="is illustrated as storing operating system 144, application programs 145, other program modules">146</part-num-ref>
+ and program data <part-num-ref name="and program data">147.</part-num-ref>
+ 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>
+ application programs <part-num-ref name="same as or different from operating system 134, application programs">135,</part-num-ref>
+ 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>
+ 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>
+ 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>
+ 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>
+ 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>
+ 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>
+ are given different numbers herein 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>
+ through input devices such as a tablet, or electronic digitizer, <part-num-ref name="tablet, or electronic digitizer,">164,</part-num-ref>
+ a microphone <part-num-ref name="microphone">163,</part-num-ref>
+ a keyboard <part-num-ref name="keyboard">162</part-num-ref>
+ and pointing device <part-num-ref name="and pointing device">161,</part-num-ref>
+ commonly referred to as mouse, trackball or touch pad. Other input devices not shown in FIG. 1 may include a 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>
+ through a user input interface <part-num-ref name="user input interface">160</part-num-ref>
+ 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 (<confidence value="5">U</confidence>
+SB). A monitor <part-num-ref name="monitor">191</part-num-ref>
+ or other type of display device is also connected <boundary-data type="header">- 12 -</boundary-data>
+      <page-break num="13"/>
+to the system bus <part-num-ref name="system bus">121</part-num-ref>
+ via an interface, such as a video interface <part-num-ref name="video interface">190.</part-num-ref>
+ The monitor <part-num-ref name="monitor">191</part-num-ref>
+ may also be integrated with a touch-screen panel or the like. Note that the monitor and/or touch screen panel can be physically coupled to a housing in which the computing device <part-num-ref name="computing device">110</part-num-ref>
+ is incorporated, such as in a tablet-type personal computer. In addition, computers such as the computing device <part-num-ref name="computing device">110</part-num-ref>
+ may also include other peripheral output devices such as speakers <part-num-ref name="may also include other peripheral output devices such as speakers">195</part-num-ref>
+ and printer <part-num-ref name="and printer">196,</part-num-ref>
+ which may be connected through an output peripheral interface <part-num-ref name="output peripheral interface">194</part-num-ref>
+ or the like.    </p>
+    <p id="p-29" num="29">[0024]   The computer <part-num-ref name="computer">110</part-num-ref>
+ 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>
+ The remote computer <part-num-ref name="remote computer">180</part-num-ref>
+ 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>
+ although only a memory storage device <part-num-ref name="memory storage device">181</part-num-ref>
+ has been illustrated in FIG. 1. The logical connections depicted in FIG. 1 include a local area network (LAN) <part-num-ref name="local area network (LAN)">171</part-num-ref>
+ and a wide area network (WAN) <part-num-ref name="wide area network (WAN)">173,</part-num-ref>
+ but may also include other networks. Such networking environments are commonplace in <boundary-data type="header">- 13 -</boundary-data>
+      <page-break num="14"/>
+offices, enterprise-wide computer networks, intranets and the Internet.    </p>
+    <p id="p-30" num="30">[0025]   When used in a LAN networking environment, the computer <part-num-ref name="computer">110</part-num-ref>
+ is connected to the LAN <part-num-ref name="LAN">171</part-num-ref>
+ through a network interface or adapter <part-num-ref name="network interface or adapter">170.</part-num-ref>
+ When used in a WAN networking environment, the computer <part-num-ref name="computer">110</part-num-ref>
+ typically includes a modem <part-num-ref name="modem">172</part-num-ref>
+ or other means for establishing communications over the WAN <part-num-ref name="WAN">173,</part-num-ref>
+ such as the Internet. The modem <part-num-ref name="modem">172,</part-num-ref>
+ which may be internal or external, may be connected to the system bus <part-num-ref name="system bus">121</part-num-ref>
+ via the user input interface <part-num-ref name="user input interface">160</part-num-ref>
+ or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer <part-num-ref name="computer">110,</part-num-ref>
+ or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation, FIG. 1 illustrates remote application programs <part-num-ref name="illustrates remote application programs">185</part-num-ref>
+ as residing on memory device <part-num-ref name="as residing on memory device">181.</part-num-ref>
+ It may be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.    </p>
+    <boundary-data type="header">- 14 -</boundary-data>
+    <heading id="h-7">FINDING PHISHING SITES</heading>
+    <p id="p-31" num="31">
+      <page-break num="15"/>
+[0026]   Various aspects of the technology described herein are directed towards finding phishing sites using automated mechanisms to analyze data and thereby establish which sites are most likely phishing sites. As will be understood, this technology is not limited to phishing sites, but can be applied to distinguish other types of sites, such as sites that have bad reputations and/or may be considered malicious in other ways.    </p>
+    <p id="p-32" num="32">[0027]   <confidence value="5">I</confidence>
+n general, many of the examples herein are directed towards a particular example architecture / implementation in which various data sources are analyzed to determine probability values for sites, based on trends in the data and the like. These probability values may be used in numerous ways, e.g., directly distributed to servers, converted to a list of sites to block, warn, or take advantage of client security settings, to help hand graders determine which sites to carefully evaluate, and so forth. As such, notwithstanding the examples below, it is understood that any mechanisms may be used to implement the model described herein.    </p>
+    <boundary-data type="header">
+      <confidence value="8">-</confidence>
+ <confidence value="66">15</confidence>
+ <confidence value="8">-</confidence>
+    </boundary-data>
+    <p id="p-33" num="33">
+      <page-break num="16"/>
+[0028]   Thus, as is understood, the present invention is not limited to the examples, structures or functionality described herein. Rather, any of the examples described herein are non- limiting, and the present invention may be used various ways that provide benefits and advantages in computing in general.    </p>
+    <p id="p-34" num="34">[0029]   Turning to FIG. 2 of the drawings, there is shown a simplified example block diagram by which a service comprising a set of servers <part-num-ref name="set of servers">202</part-num-ref>
+ provides internet access services to web clients <part-num-ref name="provides internet access services to web clients">204</part-num-ref>
+ and email services to email clients <part-num-ref name="and email services to email clients">206.</part-num-ref>
+ As generally represented in FIG. 2, the web clients <part-num-ref name="web clients">204</part-num-ref>
+ and email clients <part-num-ref name="and email clients">206</part-num-ref>
+ may provide feedback regarding emails having links to suspicious websites, and/or may provide feedback regarding suspicious websites directly, independent of how the link was obtained. The feedback may be user-initiated, or may be automated to an extent, e.g., a browser or email program may include filtering code that submits a complaint whenever a site or email message appears to be suspicious. The clients may be updated with information based on machine learning, described below. Although FIG. 2 shows the web clients <part-num-ref name="web clients">204</part-num-ref>
+ and email clients <part-num-ref name="and email clients">206</part-num-ref>
+ directly providing this information to <boundary-data type="header">- 16 -</boundary-data>
+      <page-break num="17"/>
+the services' servers <part-num-ref name="services' servers">202,</part-num-ref>
+ it is understood that "out-of-band" reporting is another alternative way for users to submit data.    </p>
+    <p id="p-35" num="35">[0030]   In FIG. 2, the servers <part-num-ref name="servers">202</part-num-ref>
+ collect the data in a data store <part-num-ref name="data store">210</part-num-ref>
+ or the like. As described below with reference to FIG. 3, numerous other data sources may be used, and there may be separate stores for web client data and email client data, however for purposes of simplicity, FIG. 2 shows only the data store <part-num-ref name="data store">210,</part-num-ref>
+ which may represent a single source or multiple sources.    </p>
+    <p id="p-36" num="36">[0031]   In any event, and as described below, the data is processed via data processing means <part-num-ref name="data is processed via data processing means">220</part-num-ref>
+ to extract data as to any site having properties that indicates a phishing site. To this end, the data processing means <part-num-ref name="data processing means">220</part-num-ref>
+ may rely on criteria such as suspicious word / phrase lists <part-num-ref name="may rely on criteria such as suspicious word / phrase lists">222</part-num-ref>
+ (e.g., "credit card" or "bank account"), domain lists <part-num-ref name="&quot;credit card&quot; or &quot;bank account&quot;), domain lists">224</part-num-ref>
+ (e.g., good reputation versus unknown versus bad), traffic lists <part-num-ref name="good reputation versus unknown versus bad), traffic lists">226</part-num-ref>
+ regarding amount and characteristics of traffic to a site, and other data <part-num-ref name="site, and other data">228.</part-num-ref>
+ For example, geographic data (via the IP address) may be used to determine if a site is being hosted in a country or other physical location having a reputation as a location for phishing scams and/or located remotely relative <boundary-data type="header">- 17 -</boundary-data>
+      <page-break num="18"/>
+to the enterprise that the site is purporting to represent.    </p>
+    <p id="p-37" num="37">Seasonality may be a factor, e.g., hourly, daily, day of week, weekly, monthly and so forth. In essence, virtually any criteria may be used to evaluate the properties of a site.</p>
+    <p id="p-38" num="38">[0032]   FIG. 2 also shows (via a dashed block) optional other filtering <part-num-ref name="dashed block) optional other filtering">230,</part-num-ref>
+ such as hand grading or other mechanisms.    </p>
+    <p id="p-39" num="39">Note that hand grading may be done on already-published data, e.g., block a highly-suspicious site immediately, and then hand grade it to determine whether to unblock it.</p>
+    <p id="p-40" num="40">[0033]   In general, the result is a set of phishing sites <part-num-ref name="set of phishing sites">232</part-num-ref>
+ that are published to the services' servers, e.g., via a reputation service <part-num-ref name="reputation service">234</part-num-ref>
+ to block (or at least warn) the services' users from accessing bad sites, as well as block any email that distributes links to such sites. Known non- phishing sites <part-num-ref name="services' users from accessing bad sites, as well as block any email that distributes links to such sites. Known non- phishing sites">236</part-num-ref>
+ may also be published, for example in case other mechanisms may be blocking valid sites that appear suspicious but in actuality are not.    </p>
+    <p id="p-41" num="41">[0034]   Note that FIG. 2 (as well as FIG. 3, described below) depict only example architecture(s), and that a list or other data structure containing known phishing sites may be <boundary-data type="header">- 18 -</boundary-data>
+      <page-break num="19"/>
+alternatively (or in addition to) provided to a client via other mechanisms, e.g., not necessarily by querying a service.    </p>
+    <p id="p-42" num="42">For example, a list of sites may be provided as part of a data file or code update, such as provided with a regularly scheduled anti-spa<confidence value="5">m</confidence>
+ update, antivirus update, anti-spyware update and/or in numerous other ways.    </p>
+    <p id="p-43" num="43">[0035]   Turning to a more detailed example, FIG. 3 contains a high-level view of one example architecture (also referred to as a phish-finder system or anti-phishing system) <part-num-ref name="phish-finder system or anti-phishing system)">300</part-num-ref>
+ in which a phishing detection implementation may operate. As generally represented in FIG. 3, a variety of Phish Data sources 301-307 are available to the example anti-phishing system <part-num-ref name="example anti-phishing system">300.</part-num-ref>
+    </p>
+    <p id="p-44" num="44">[0036]   <confidence value="5">I</confidence>
+n general, there are sources corresponding to browser (e.g., Internet Explorer 7.x) submissions <part-num-ref name="Internet Explorer 7.x) submissions">301,</part-num-ref>
+ toolbar submissions <part-num-ref name="Internet Explorer 7.x) submissions 301, toolbar submissions">302,</part-num-ref>
+ FBL (feedback loop, e.g., provided by volunteer users of a service) submissions <part-num-ref name="service) submissions">303,</part-num-ref>
+ honeypots (closely monitored seeded/dummy email addresses) <part-num-ref name="service) submissions 303, honeypots (closely monitored seeded/dummy email addresses)">304,</part-num-ref>
+ and email service-supplied (e.g., Hotmail) fraud and junk mail submissions, <part-num-ref name="Hotmail) fraud and junk mail submissions,">305</part-num-ref>
+ and <part-num-ref name="and">306,</part-num-ref>
+ respectively. Note that although a limited number of example sources are shown, there is no <boundary-data type="header">- 19 -</boundary-data>
+      <page-break num="20"/>
+limitation to the number and type of data; indeed the "etc." source labeled <part-num-ref name="&quot;etc.&quot; source labeled">307</part-num-ref>
+ in FIG. 3 represents additional sources and types of phishing-related data. For example, it is likely that legitimate enterprises will share some of their data with one another, providing many more sources. Other examples include data from IP / domain registrars, certificate-related information, including certificates and the reputation of the certificate issuer, traffic changes in time (e.g., spikes in visits suddenly appearing), fuzzy matching email messages that have similar text to previously-known phishing messages, zombie heuristics indicative of whether a site is on a personal computer over a broadband connection, and so forth.    </p>
+    <p id="p-45" num="45">[0037]   Although not readily apparent in FIG. 3, some of the sources are more current with respect to data than others, e.g., honeypot data <part-num-ref name="honeypot data">304</part-num-ref>
+ is very up-to-date (nearly instantaneous), whereas browser, toolbar and user-provided data <part-num-ref name="is very up-to-date (nearly instantaneous), whereas browser, toolbar and user-provided data">301,</part-num-ref>
+ <part-num-ref name="is very up-to-date (nearly instantaneous), whereas browser, toolbar and user-provided data 301,">302,</part-num-ref>
+ <part-num-ref name="is very up-to-date (nearly instantaneous), whereas browser, toolbar and user-provided data 301, 302,">305</part-num-ref>
+ and <part-num-ref name="and">306</part-num-ref>
+ is moderately up-to-date, while FBL-like data <part-num-ref name="is moderately up-to-date, while FBL-like data">303</part-num-ref>
+ are relatively dated (but nevertheless useful)<confidence value="5">.</confidence>
+    </p>
+    <p id="p-46" num="46">
+      <confidence value="5">[</confidence>
+0038]   Additional details about some of the data sources are set forth below. Note that one main attack vector for <boundary-data type="header">- 20 -</boundary-data>
+      <page-break num="21"/>
+phishing is e-mail, so known spa<confidence value="7">m</confidence>
+ sources may include many URLs to phishing sites. Reports from Internet Explorer 7.x / MSN Toolbar will be available to users, who may benefit from an anti-phishing plug-in to report URLs as phishing or as not phishing. Although the quality of such reports may not be ideal, the sheer number of reporters in conjunction with cross-checks with other data sources will make such data actionable.    </p>
+    <p id="p-47" num="47">[0039]   A service such as Hotmail allows users to report sites (corresponding to email messages) that are believed to be fraudulent. To this end, the service may add a fraud reporting facility to its user interface, e.g., similar to the <confidence value="5">'</confidence>
+Report as Junk' facility that is currently available. These complaint reports can be made by any service user about any message, and thus such data may be used in conjunction with careful cross-checking techniques, and/or along with requiring a threshold amount of similar reports, to avoid spurious reports.    </p>
+    <p id="p-48" num="48">[0040]   FBL (feedback loop) spa<confidence value="7">m</confidence>
+ is another data source, and makes message contents available. Although it has a latency of about one day, FBL data is still useful; note that spa<confidence value="7">m</confidence>
+ is <boundary-data type="header">- 21 -</boundary-data>
+      <page-break num="22"/>
+a primary attack vehicle for phishing, and spa<confidence value="7">m</confidence>
+ data ordinarily contain a large number of phishing messages mixed in with a flood of general spa<confidence value="7">m</confidence>
+ data. Phishing sites have been successfully found from this data by using tools to narrow down possible candidates (e.g., by looking for keywords and phishing tricks), and by hand examining messages that were flagged by the tool. Although the current lag in average FBL message arrival time is about one day, which tends to reduce the value of locating currently-operating phishing sites via this data source, such information may be relevant for a long- operating site, and at least be used in training the predictive model, as described below.    </p>
+    <p id="p-49" num="49">[0041] Honeypots and other dynamic trap accounts receive e messages that are sent to seeded / inactive accounts respectively. Messages sent to dynamic trap accounts may be heavily down-sampled to provide actionable information that is like the honeypot data, but potentially with a much larger sample.</p>
+    <p id="p-50" num="50">[0042]   Ad hoc phishing reports from reliable, high- reputation sources may also be used to detect phishing sites.</p>
+    <p id="p-51" num="51">Another potential source is "Password Sharing Data" that finds <boundary-data type="header">- 22 -</boundary-data>
+      <page-break num="23"/>
+sites where users type in their username/passwords from other sites, and reports this suspicious behavior to a central server. If enough users report a site X as asking for their site Y password, this provides strong evidence that X is phishing Y.    </p>
+    <p id="p-52" num="52">[0043]   To eliminate false positives, due to there being many non-phishing URLs in the above-identified data sources and others, other sources of information may be used. For example, FBL Good Mail includes URLs that occur more often in good mail than in spa<confidence value="7">m</confidence>
+ mail, and are less likely to be phishing attacks. Domain Traffic Information refers to domains that have been receiving large amounts of traffic consistently for a long period of time; such domains are less likely to be hosting phishing sites, (with the exception of domains public hosting sites or redirectors, which are excluded to the extent possible)<confidence value="5">.</confidence>
+    </p>
+    <p id="p-53" num="53">[0044]   A raw sample of all of a service's email is useful for fingerprints, (wherein a fingerprint of an object such as an email message comprises a (typically small) representation of the object, such that if two object have the same fingerprint then the two objects are, with high probability, <boundary-data type="header">- 23 -</boundary-data>
+      <page-break num="24"/>
+equivalent for some given purpose), and may be used to help smooth out noise and inconsistencies in our other data sources. For example, this data will help distinguish URLs in fraud-reporting data (that are part of a phishing attack) from URLs appearing in large valid promotions that are often erroneously reported as fraud. Note that, for example, the complaint rate on phishing URLS may be ten percent, while the complaint rate on the valid promotion may be less than one percent, but the valid promotion may be ten times bigger and thus receive the same raw number of complaints as the phishing attack. The raw sample will distinguish between such instances.    </p>
+    <p id="p-54" num="54">
+      <confidence value="5">[</confidence>
+0045]   Ranking services, such as MSNRank, are based on searches of a URL or other URLs in a domain, and also may provide valuable data for use in eliminating false positives.    </p>
+    <p id="p-55" num="55">For example, URLs that have been indexed by a searching service and have high rankings are unlikely to be phishing sites. Similarly, pre-built lists of known legitimate banking or commerce sites corresponding to URLs on known good hosts are probably not phishing attacks.</p>
+    <boundary-data type="header">- 24 -</boundary-data>
+    <p id="p-56" num="56">
+      <page-break num="25"/>
+[0046]   Returning to FIG. 3, in general, the raw data from each of these sources 301-307 is processed, e.g., by respective data processing means 311-317 into machine-readable (and optionally human-readable) reports 321-327. For example, each data source 301-307 may have an associated process that monitors data as it arrives on the source in real time, extracts the properties needed by the system (examples of which are described below) and inserts them into a report store for the data stream. As described above with reference to FIG. 2, any of these processors 311-317 may access additional information as needed, such as top traffic lists, target domain lists, suspicious word lists, and so forth.    </p>
+    <p id="p-57" num="57">[0047]   In this example, there is one report store per data stream which contains the information extracted from the data on the stream, e.g., accumulated for the past N days. The value of N may be determined empirically and may be different for different data sources, and in fact there may be multiple N values for a single data source; e.g., multiple types of information may be extracted from the same data source and each type of information may be aggregated over multiple different time spans. The value N may also be a fraction of a <boundary-data type="header">- 25 -</boundary-data>
+      <page-break num="26"/>
+day and may vary. In addition to containing information aggregated over various time spans, each report may be generated in any time frame that is appropriate for its corresponding source, e.g., hourly, daily, weekly and even immediate if needed, e.g., if a serious threat is detected during processing of the raw data.    </p>
+    <p id="p-58" num="58">[0048<confidence value="5">]</confidence>
+   A report aggregator <part-num-ref name="report aggregator">332</part-num-ref>
+ is provided to aggregate information from the report stores 321-327 into a description <part-num-ref name="description">334</part-num-ref>
+ of how each host (or URL) has been observed in the data streams over the selected time periods. The aggregator <part-num-ref name="aggregator">332</part-num-ref>
+ also applies a predictive model <part-num-ref name="predictive model">336</part-num-ref>
+ (the training of which is described with reference to FIG. 5) to the aggregated information to estimate the probability that the specified object is a phishing site/page.    </p>
+    <p id="p-59" num="59">[0049]   These aggregated statistics 334, which may comprise elaborate statistics or be as simple as probability data with some supporting information, are stored for querying by query interfaces 341-343. The aggregator <part-num-ref name="aggregator">332</part-num-ref>
+ may be run periodically (e.g., once an hour, or once every twenty minutes) and/or as needed to update the aggregated statistics <part-num-ref name="aggregated statistics">334.</part-num-ref>
+    </p>
+    <boundary-data type="header">
+      <confidence value="6">-</confidence>
+ 26 -    </boundary-data>
+    <p id="p-60" num="60">
+      <page-break num="27"/>
+[0050]   The query interfaces 341-343 are provided for other components to take advantage of the statistical and other information <part-num-ref name="statistical and other information">334</part-num-ref>
+ generated by the phish finder system <part-num-ref name="phish finder system">300</part-num-ref>
+ of FIG. 3. For example, Query Interface <part-num-ref name="of FIG. 3. For example, Query Interface">1</part-num-ref>
+ (also labeled <part-num-ref name="(also labeled">341)</part-num-ref>
+ allows other components such as an importer <part-num-ref name="importer">346</part-num-ref>
+ to determine the probability that a specific host/URL is involved in a phishing attack. Query Interface <part-num-ref name="phishing attack. Query Interface">2</part-num-ref>
+ (also labeled <part-num-ref name="(also labeled">342)</part-num-ref>
+ allows other components such as the importer <part-num-ref name="importer">346</part-num-ref>
+ to request lists of hosts/<confidence value="5">U</confidence>
+RLs ordered by the probability that they are involved in Phishing. For example, this interface may be used to ask for the top 1,000 most likely phishing sites seen in any data source, the top <part-num-ref name="top">300</part-num-ref>
+ mostly likely phishing sites from the end user reports, the 1,000 sites reported by site owners that are least likely to actually be phishing sites, and so forth.    </p>
+    <p id="p-61" num="61">[0051]   Query Interface 3 (also labeled <part-num-ref name="(also labeled">343)</part-num-ref>
+ allows a component such as the URS (URL reputation service) <part-num-ref name="URS (URL reputation service)">234</part-num-ref>
+ to find sites that have a very high probability of being phishing sites, e.g., for semi-automatic "red-alert" or "yellow alert" generation, (or some finer-grained alerting mechanism). This interface accepts false positive thresholds. For example, a sample query may be something like "list all the sites that <boundary-data type="header">- 27 -</boundary-data>
+      <page-break num="28"/>
+may get a yellow alert while maintaining a false positive rate of less than one percent." [0052]   As can be readily appreciated, a substantial concept of the above-described anti-phishing system <part-num-ref name="above-described anti-phishing system">300</part-num-ref>
+ and strategy is to rapidly get known phishing web sites into the URS <part-num-ref name="URS">348</part-num-ref>
+ <confidence value="66">so</confidence>
+ that users of a legitimate provider / email service are protected from browsing to phishing sites. In part, this is performed by relying on external data providers to provide lists of known phishing sites, however the architecture of FIG. 3 enables anti-phishing strategies that need not rely solely on third-party data providers. This system <part-num-ref name="enables anti-phishing strategies that need not rely solely on third-party data providers. This system">300</part-num-ref>
+ is thus a substantial improvement, as third party providers may not be as cooperative as desired or provide high-quality reports, and may not provide sufficient coverage to detect otherwise detectable phishing sites. As can be readily appreciated, the architecture of FIG. 3 leverages many types of data sources, including those of data providers that are directly offering the services that are being protected.    </p>
+    <p id="p-62" num="62">[0053]    In addition to rapidly finding as many phishing sites as possible given streams of data from the sources 301- <part-num-ref name="sources 301-">307</part-num-ref>
+ (which includes any other sources), the anti-phishing <boundary-data type="header">- 28 -</boundary-data>
+      <page-break num="29"/>
+system <part-num-ref name="anti-phishing system">300</part-num-ref>
+ should not erroneously flag non-phishing sites as being phishing sites. To this end, the anti-phishing system <part-num-ref name="anti-phishing system">300</part-num-ref>
+ may have a confidence-ranked list of suspicious URLs available for a parallel process to extract and evaluate  For example, the anti-phishing system <part-num-ref name="anti-phishing system">300</part-num-ref>
+ may produce a list of likely phishing sites, ordered most-likely-phishing first.    </p>
+    <p id="p-63" num="63">This list may be passed to graders who verify or reject that the site is phishing and send the verified phishing sites as<confidence value="1">*</confidence>
+ output to the reputation service. For the sites the system finds most-likely-phishing, there may be a second path where the site is output to the URS immediately and also sent to the graders for verification, whereby if disconfirmed by the graders, the site is removed from the URS.    </p>
+    <p id="p-64" num="64">
+      <confidence value="5">[</confidence>
+0054]   Based on the data sources 301-307, the system <part-num-ref name="system">300</part-num-ref>
+ is able to collect a significant amount of statistical information about URLs, including their features and properties. Note that each property can be tracked per URL, per domain, and per IP address (via a DNS lookup on the domain). Properties may also be tracked at several different time resolutions, e.g., in the last ten minutes, hour, day, <boundary-data type="header">- 29 -</boundary-data>
+      <page-break num="30"/>
+week, month, and all time (particularly for known good URL sources)<confidence value="5">.</confidence>
+    </p>
+    <p id="p-65" num="65">[0055]   For email-related data sources, e.g., including FBL spa<confidence value="7">m</confidence>
+, FBL good, "This is junk," "This is fraud," honeypots, dynamic trap accounts, and raw e-mail samples), a given URL may be associated with the following features / properties:    </p>
+    <p id="p-66" num="66">
+      <confidence value="2">"</confidence>
+ Number of times the object <confidence value="5">(</confidence>
+URL, web server domain, web server IP) appeared in the source.    </p>
+    <p id="p-67" num="67">
+      <confidence value="2">"</confidence>
+ Ratio of the number of appearances in the last period to the current one (e.g. N times more appearances today than yesterday); ratio compared to one week ago (for the one day period); ratio compared to long-term averages and standard deviations; other time series features.    </p>
+    <p id="p-68" num="68">
+      <confidence value="2">"</confidence>
+ Number of times the object appeared in the source along with a commonly-phished brand (e.g. names of well-known financial institutions, credit cards, payment services, e-commerce sites, auction sites and so forth) in the body or subject of the message.    </p>
+    <p id="p-69" num="69">
+      <confidence value="2">"</confidence>
+ Number of times the object appeared with a phishing related word (e.g. login, password, credit, and so forth) in the body or subject of the message.    </p>
+    <p id="p-70" num="70">
+      <confidence value="2">"</confidence>
+ Whether common brands or phishing-related words appear in the host name or the URL.    </p>
+    <p id="p-71" num="71">
+      <confidence value="4">*</confidence>
+ Number of times the object appeared in the source along with a link to a commonly-phished domain, such as a well known financial-type domain, or top traffic domain, when the domain from the URL in question was not also to the commonly-phished domain (typically when the source contains emails)<confidence value="5">.</confidence>
+    </p>
+    <boundary-data type="header">- 30 -</boundary-data>
+    <p id="p-72" num="72">
+      <page-break num="31"/>
+      <confidence value="2">"</confidence>
+ Number of times the object was an exception (also referred to as "odd-man-out," where the object appears in a message or page together with some number of commonly-phished domains, but does not itself belong to a commonly-phished domain) when it appeared with commonly-phished domains, well known financial domains, or top traffic domains.    </p>
+    <p id="p-73" num="73">
+      <confidence value="2">"</confidence>
+ Number of times the object appeared in an email and the PRD (purported responsible domain) of the message was a commonly-phished site, a well known financial domain, or a top traffic domain.    </p>
+    <p id="p-74" num="74">
+      <confidence value="2">"</confidence>
+ Number of times the object appeared in the source and got a sender ID fail (hard or soft) for a known financial domain.    </p>
+    <p id="p-75" num="75">
+      <confidence value="2">"</confidence>
+ Number of times the object appeared in the source and got a sender ID pass for a known financial domain or a known good e-mail sender.    </p>
+    <p id="p-76" num="76">
+      <confidence value="2">"</confidence>
+ Number of times the object appeared in a message that got a move/delete SCL Spam<confidence value="7">m</confidence>
+ confidence level)<confidence value="5">.</confidence>
+    </p>
+    <p id="p-77" num="77">
+      <confidence value="2">"</confidence>
+ Number of times the object appeared in the source with a phishing trick (numeric IP, obfuscated URL, HRE<confidence value="5">F</confidence>
+ mismatch, "look-alike URL", and so forth)<confidence value="5">.</confidence>
+    </p>
+    <p id="p-78" num="78">
+      <confidence value="2">"</confidence>
+ Number of times the object appeared in an email message that had a fingerprint match with a known phishing message.    </p>
+    <p id="p-79" num="79">
+      <confidence value="2">"</confidence>
+ Number of times the object appeared in an email message that had a fingerprint match with a message from a known phish target domain.    </p>
+    <p id="p-80" num="80">
+      <confidence value="2">"</confidence>
+ Number of hours since the object was first observed in the data source.    </p>
+    <p id="p-81" num="81">
+      <confidence value="2">"</confidence>
+ Number of hours since the object was last observed in the data source.    </p>
+    <p id="p-82" num="82">
+      <confidence value="2">"</confidence>
+ Whether the host is a numeric IP address, and if so, whether the corresponding domain name matches zombie heuristics.    </p>
+    <boundary-data type="header">- 31 -</boundary-data>
+    <p id="p-83" num="83">
+      <page-break num="32"/>
+[0056]   The system <part-num-ref name="system">300</part-num-ref>
+ may also track ratios of these values (as value from spa<confidence value="7">m</confidence>
+ source divided by value from non-spa<confidence value="5">m</confidence>
+ source) for the following combinations; (note that these are only some possible example combinations of sources, and other combinations may be used)<confidence value="5">:</confidence>
+    </p>
+    <p id="p-84" num="84">
+      <confidence value="1">*</confidence>
+ FBL Spa<confidence value="5">m</confidence>
+ / FBL good <confidence value="1">*</confidence>
+ FBL Spa<confidence value="5">m</confidence>
+ / (FBL Spa<confidence value="5">m</confidence>
+ + FBL Good) <confidence value="1">*</confidence>
+ This is Junk Data / Raw data sample <confidence value="2">e</confidence>
+ This is fraud data / Raw data sample <confidence value="1">e</confidence>
+ Honeypot / Raw data sample <confidence value="1">e</confidence>
+ DTA / Raw data sample [0057]   The system <part-num-ref name="system">300</part-num-ref>
+ also may track the number of times a URL appeared recently in a spa<confidence value="7">m</confidence>
+ source and never in a good source.    </p>
+    <p id="p-85" num="85">[0058]   For each object, the system may also track its:</p>
+    <p id="p-86" num="86">
+      <confidence value="1">e</confidence>
+ Traffic (e.g., according to the MSN CEIP data) <confidence value="1">e</confidence>
+ Rank from search, e.g., MSNSearch (and/or the average of URLs for that web server domain/web server IP in the data) <confidence value="1">e</confidence>
+ Geolocation <confidence value="1">e</confidence>
+ Registrar information on the domain (how long ago was it registered) <boundary-data type="header">- 32 -</boundary-data>
+      <page-break num="33"/>
+      <confidence value="1">e</confidence>
+ Last-hop router of a traceroute to the host [0059]   Turning to an explanation of some example ways to identify phishing sites and measuring the performance of the system <part-num-ref name="system">300,</part-num-ref>
+ consider that at some date data indicates that phishing sites are active for N days on average (where N may include a fraction, and may be less than one) before being shut down. As can be readily appreciated, given this average, the benefit of detecting a phishing site is proportional to the amount of time remaining after the site is detected;    </p>
+    <p id="p-87" num="87">metrics should take this detection latency into account. For example, the metric for "<confidence value="68">FP</confidence>
+" (false positive) costs of blocked non-phish <confidence value="5">U</confidence>
+RLs may be time-independent, since such errors are probably resolved by other reporting and checking functions.    </p>
+    <p id="p-88" num="88">Conversely, the metric for "<confidence value="5">F</confidence>
+N" (false negative) costs of undiscovered phish URLs are likely time-dependent, in order to reward the detection system for minimizing detection latency.    </p>
+    <p id="p-89" num="89">Detection latency may be specified as "time until blocked" or "time until URL appears in top M suspicious objects" for some parameter M. Thus, the following may apply:</p>
+    <p id="p-90" num="90">
+      <confidence value="1">e</confidence>
+ <confidence value="68">FP</confidence>
+' : metric may be usual FP rate: fraction of non-phish URLs that were detected as phishing (0 &lt;= <confidence value="68">FP</confidence>
+' &lt;= 1)<confidence value="5">.</confidence>
+    </p>
+    <boundary-data type="header">- 33 -</boundary-data>
+    <p id="p-91" num="91">
+      <page-break num="34"/>
+      <confidence value="1">e</confidence>
+ <confidence value="6">F</confidence>
+N': metric may be (<confidence value="222222222">1/(number</confidence>
+ of phishURLs) * sumphishURLs min(1, (hours till detected)/24*N). In the formula, for a phish URL u, the contribution to the sum is <part-num-ref name="sum is">0</part-num-ref>
+ if u is detected as phishing after <part-num-ref name="if u is detected as phishing after">0</part-num-ref>
+ hours; the contribution is <part-num-ref name="contribution is">1</part-num-ref>
+ if taking more than 24*N hours (or never detect it), and may be linear in between. This is the usual <confidence value="5">F</confidence>
+N rate, weighted by detection latency; <part-num-ref name="usual FN rate, weighted by detection latency;">(<confidence value="5">0</confidence>
+      </part-num-ref>
+ <confidence value="85">&lt;=</confidence>
+ <confidence value="5">F</confidence>
+N' &lt;= 1).    </p>
+    <p id="p-92" num="92">[0060]   <confidence value="5">F</confidence>
+P' versus <confidence value="5">F</confidence>
+N' may be plotted for a ROC-like curve, or a scoring function may be formed, e.g.:    </p>
+    <p id="p-93" num="93">Score = k * <confidence value="5">F</confidence>
+P' + (1 - k) * <confidence value="588">FN'</confidence>
+ where <part-num-ref name="- k) * FN' where">0</part-num-ref>
+ &lt;= k &lt;= <part-num-ref name="&lt;= k &lt;=">1</part-num-ref>
+ is a constant that defines the comparative cost of a <confidence value="5">F</confidence>
+N compared to an F<confidence value="68">P.</confidence>
+    </p>
+    <p id="p-94" num="94">[0061]   One advantage of the system <part-num-ref name="system">300</part-num-ref>
+ is the ability to rapidly get known phishing web sites into a URL reputation service, which then may be queried by Anti-Phishing filters and used to protect users from browsing to known phishing sites. By leveraging available data sources and using probabilistic machine learning algorithms, the system <part-num-ref name="system">300</part-num-ref>
+ automatically finds sites that are phishing, as well as detecting likely false positives. Phishing sites are given a bad reputation in the URL reputation service, where they will receive a caution or block from anti-phishing clients.    </p>
+    <boundary-data type="header">- 34 -</boundary-data>
+    <p id="p-95" num="95">
+      <page-break num="35"/>
+Graders also may use the probabilities produced by the models to prioritize which sites they grade.    </p>
+    <p id="p-96" num="96">
+      <confidence value="5">[</confidence>
+0062]   By way of example, consider a new web site that gets reported as being a phishing site by a user of an internet access service. The system <part-num-ref name="system">300</part-num-ref>
+ examines statistics about how that site appeared in numerous data sources, and uses this information, along with a probabilistic model, to determine the probability that the site actually is a phishing site. If this probability is above a target threshold, the site can be automatically propagated to the URL reputation service with a bad reputation and, in any case, the probability can be used to prioritize grading.    </p>
+    <p id="p-97" num="97">[0063]   To summarize, the anti-phishing system <part-num-ref name="anti-phishing system">300</part-num-ref>
+ uses various data sources to find phishing sites, including sources that are closely affiliated with the email and internet access services being offered, (e.g., non-third party sources). The combination of sources provides a stronger model,<confidence value="5">.</confidence>
+ especially when aggregated across both email-based and browser-based sources, and the model is further strengthened by using data sources that contain known non-phishing sites (e.g. FBL good mail). Features are extracted about the sites, including <boundary-data type="header">- 35 -</boundary-data>
+      <page-break num="36"/>
+aggregations done at a host/site level, and probabilistic models are used to make predictions regarding phishing sites.    </p>
+    <p id="p-98" num="98">The probabilities that are found may be used to automatically warn users or block users from visiting dangerous sites, as well as to help human graders be more efficient in grading.</p>
+    <p id="p-99" num="99">Trend analysis may be used as well, e.g., spikes or anomalies may be an indicator of something unusual.</p>
+    <p id="p-100" num="100">[0064]   <confidence value="5">I</confidence>
+n general, the system <part-num-ref name="system">300</part-num-ref>
+ works by monitoring how web hosts or site URLs appear in the data sources that are available, and by using machine learning to build models that predict the probability that any given host is a phishing site from the way a host appears in the data sources. For example, consider a host that gets reported as a <confidence value="5">F</confidence>
+N by an internet service user, where a phishing filter indicated safe, but the user thinks it is a phish. If that host appeared ten times in a feedback loop on messages that got a <confidence value="5">'</confidence>
+Sender<confidence value="5">I</confidence>
+D pass' from a known good sender, then the system may be fairly certain it is unlikely that the reported host is a phishing site. The system would be more suspicious when the host is a numeric IP, and it appears in ten spa<confidence value="7">m</confidence>
+ messages in an email service <boundary-data type="header">- 36 -</boundary-data>
+      <page-break num="37"/>
+feedback <confidence value="8">l</confidence>
+oop, and in every one of these message it is an exception with a known phishing target.    </p>
+    <p id="p-101" num="101">[0065]   Whenever a new message or report arrives on one of the data sources 301-307, the message or complaint report is scanned by the system <part-num-ref name="system">300,</part-num-ref>
+ any web hosts (or site URLs) it contains are extracted, and a report is recorded. For example, with respect to email messages, for every <confidence value="5">U</confidence>
+RL in a message that arrives via the feedback loop, properties are recorded in the report. Such properties may include:    </p>
+    <p id="p-102" num="102">
+      <confidence value="2">"</confidence>
+ <confidence value="85">GU</confidence>
+ID - the GUID of the message; (note that this is an identifier for the message, not technically a property used for determining phish / not-phish) <confidence value="2">"</confidence>
+ reportTime - the time the Feedback user reported the message as spa<confidence value="7">m</confidence>
+ or good <confidence value="1">e</confidence>
+ rcvdTime -the time the Feedback user received the message <confidence value="1">*</confidence>
+ host - the host of the URL (e.g., foo.com for three letter TLDs, bar.bax.us for two letter TLDs, and the complete IP address for numeric hosts) <confidence value="2">e</confidence>
+ url <confidence value="1">*</confidence>
+ hasTargetWordBody - True if the body of the message contains one of several dozen phishing related words (including commonly phished brands, login, password, and so forth) <confidence value="1">e</confidence>
+ hasTargetWordSubject <confidence value="1">*</confidence>
+ hasTargetPRD - true if the PRD (purported responsible domain) of the message is a commonly phished domain <boundary-data type="header">- 37 -</boundary-data>
+      <page-break num="38"/>
+      <confidence value="2">"</confidence>
+ hasPhishTrick - True if the message has any URL that triggers one of the phishing heuristics <confidence value="2">"</confidence>
+ hasSIDFail - True if the message has a fail result code from a sender ID check <confidence value="1">*</confidence>
+ hasS<confidence value="5">I</confidence>
+DPass <confidence value="1">e</confidence>
+ numDomains<confidence value="5">I</confidence>
+nMessage - The number of unique domains of web hosts in the message <confidence value="2">e</confidence>
+ isOMOWithTargetDomain - True if the host from this report is not a commonly phished domain, but every other web host in the message is a commonly phished domain <confidence value="2">e</confidence>
+ isWithTargetDomain - True if the host from this message is not a commonly phished domain, but there is a web host in the message from a commonly phished domain <confidence value="2">e</confidence>
+ isTargetDomain - True if the host from this report is from a commonly phished domain <confidence value="2">e</confidence>
+ isTopTrafficDomain - True if the host from this report is on a top traffic list <confidence value="1">e</confidence>
+ isNumericHost - True if the host from this report is a numeric IP address <confidence value="2">e</confidence>
+ isFBLSpam <confidence value="2">e</confidence>
+ isFBLGood [0066]   For every browser-initiated report that arrives, properties including some or all of the following examples may be recorded in the report:    </p>
+    <p id="p-103" num="103">
+      <confidence value="1">"</confidence>
+ GUID - the GUID of the report (again, similar to a message GUID, an identifier for the report, not technically a property used for determining phish / not- phish) <boundary-data type="header">- 38 -</boundary-data>
+      <page-break num="39"/>
+      <confidence value="1">*</confidence>
+ Host - the host of the reported URL (foo.com for <part-num-ref name="reported URL (foo.com for">3</part-num-ref>
+ letter TLDs, bar.bax.us for <part-num-ref name="letter TLDs, bar.bax.us for">2</part-num-ref>
+ letter TLDs, and the complete IP address for numeric hosts) <confidence value="1">*</confidence>
+ reportTime - the time the URL was reported <confidence value="2">e</confidence>
+ isTargetDomain - True if the host from this report is from a commonly phished domain <confidence value="1">e</confidence>
+ isTopTrafficDomain - True if the host from this report is on a top traffic list <confidence value="2">"</confidence>
+ isFp - True if the browser phishing filter marked the URL as phish but the user reports that it is not phishing <confidence value="2">"</confidence>
+ isTp - True if the browser phishing filter marked the URL as phish and the user reports that it is phishing <confidence value="2">"</confidence>
+ isFn - True if the browser phishing filter marked the URL as not phish but the user reports that it is phishng <confidence value="2">"</confidence>
+ isTn - True if the browser phishing filter marked the URL as not phish and the user reports that it is not phishing [0067]   The system <part-num-ref name="system">300</part-num-ref>
+ also has two sources of classifications that it may monitor, including grader marks on the browser-generated reports and hand-tagged FBL messages.    </p>
+    <p id="p-104" num="104">With respect to grader marks on the browser-generated reports, each complaint report may be eventually examined by a human grader who may give it one of the following marks:</p>
+    <p id="p-105" num="105">o phish = true phishing U<confidence value="68">RL</confidence>
+ o nocat = not a phishing site o dead = the site was unreachable <boundary-data type="header">- 39 -</boundary-data>
+      <page-break num="40"/>
+o placeholder = the site was a placeholder page o foreign = foreign site could not be graded o redirect = the site was a redirector o norepro = the grader couldn't reproduce what the customer said about the site [0068] Once marked as a phish, the URL is known to be phishing in any other data sources. The system can also roll upwards and consider the host that the URL was on to be phishing. The system may also use the nocat reports for counter examples.    </p>
+    <p id="p-106" num="106">[0069] With respect to hand-tagged FBL messages, the hand evaluations made on messages in the FBL are recorded, resulting in known phishing sites being tagged. These are also used as training data, as described below.</p>
+    <p id="p-107" num="107">[0070] Turning to a consideration of training, training examples are produced from the data reports and phishing classifications described above. Each example corresponds to a web host (or site <confidence value="5">U</confidence>
+RL) that appeared in one of the data sources, and the features of the example record information about the contexts in which the host appeared. Examples are produced by aggregating these properties over time-windows of the data sources, e.g., by using every browser-generated <boundary-data type="header">- 40 -</boundary-data>
+      <page-break num="41"/>
+complaint report over the past day, every FBL <confidence value="7887">spam</confidence>
+ report over the past week, and every FBL good report over the past month.    </p>
+    <p id="p-108" num="108">[0071]   Note that different training and corresponding usage models may be made available based on different time frames.</p>
+    <p id="p-109" num="109">For example, near-instantaneous honeypot data 504 (FIG. <part-num-ref name="(FIG.">5)</part-num-ref>
+ may be used to produce a quick-react model, e.g., for newly seen <confidence value="5">U</confidence>
+RLs, in contrast to a medium speed model that may be built and used based on browser, toolbar and/or user-provided data <part-num-ref name="medium speed model that may be built and used based on browser, toolbar and/or user-provided data">501,</part-num-ref>
+ <part-num-ref name="medium speed model that may be built and used based on browser, toolbar and/or user-provided data 501,">502,</part-num-ref>
+ <part-num-ref name="medium speed model that may be built and used based on browser, toolbar and/or user-provided data 501, 502,">505</part-num-ref>
+ and <part-num-ref name="and">506.</part-num-ref>
+ A longer-time-frame model (e.g., based on FBL data <part-num-ref name="based on FBL data">503)</part-num-ref>
+ model also may be built and used, and while possibly old in usage, may provide more accurate results). In sum, there may be multiple models, each trained on the data available at some particular interval after the first observation of a phishing attack, (where some example intervals are described below)<confidence value="5">.</confidence>
+    </p>
+    <p id="p-110" num="110">[0072]   Features may be recorded for each host, including some or all of the following example features:</p>
+    <p id="p-111" num="111">
+      <confidence value="2">"</confidence>
+ isPhish - True if one of the sets of classified mail have a verified phishing site on this host.    </p>
+    <p id="p-112" num="112">
+      <confidence value="2">"</confidence>
+ numMessages - Number of FBL messages that contained a link to this host.    </p>
+    <boundary-data type="header">
+      <confidence value="6">-</confidence>
+ 41 -    </boundary-data>
+    <p id="p-113" num="113">
+      <page-break num="42"/>
+      <confidence value="2">"</confidence>
+ numURLs - number of unique URLs from this host that were seen in the FBL <confidence value="6">.</confidence>
+    </p>
+    <p id="p-114" num="114">
+      <confidence value="2">"</confidence>
+ numIETP - number of times a user reported that the browser filter called the site a phish site and they agreed.    </p>
+    <p id="p-115" num="115">
+      <confidence value="2">"</confidence>
+ numIEFP - number of times a user reported that the browser filter called the site a phish and they disagreed <confidence value="2">"</confidence>
+ numIETN - number of times a user reported that the browser filter called the site not phish and they agreed.    </p>
+    <p id="p-116" num="116">
+      <confidence value="2">"</confidence>
+ numIEFN -number of times a user reported that the browser filter called the site not phish and they disagreed.    </p>
+    <p id="p-117" num="117">
+      <confidence value="2">"</confidence>
+ numIEURLs - number of unique URLs that IE user reported on this domain.    </p>
+    <p id="p-118" num="118">
+      <confidence value="2">"</confidence>
+ pFBLGood - the portion of the <confidence value="5">F</confidence>
+BL messages that were marked good by the FBL user <confidence value="2">e</confidence>
+ pFBLSpam <confidence value="1">*</confidence>
+ isTopTraffic <confidence value="1">*</confidence>
+ isTargetDomain <confidence value="1">*</confidence>
+ <confidence value="85">pW</confidence>
+ithTargetWordBody - the percentage of the FBL messages that the host appeared in that had a target word in their body <confidence value="1">e</confidence>
+ pWithTargetWordSubject <confidence value="1">*</confidence>
+ pWithPhishTrick <confidence value="1">*</confidence>
+ pWithTarget<confidence value="588">PRD</confidence>
+ <confidence value="1">e</confidence>
+ pWithS<confidence value="5">I</confidence>
+DPass <confidence value="1">e</confidence>
+ pWithS<confidence value="5">I</confidence>
+DPassForTargetPRD <confidence value="1">*</confidence>
+ pWithSID<confidence value="5">F</confidence>
+ail <confidence value="2">e</confidence>
+ pWithSIDFailForTargetPRD <confidence value="1">e</confidence>
+ pWithS<confidence value="5">I</confidence>
+DFailWithTargetDomain - the percentage of the FBL messages that had a SID fail and also had a link to a target domain <boundary-data type="header">- 42 -</boundary-data>
+      <page-break num="43"/>
+      <confidence value="2">"</confidence>
+ pWithS<confidence value="686">IDF</confidence>
+ailWithTarget<confidence value="5">W</confidence>
+ord - the percentage of the FBL messages that had a SID fail and a target word (in either body of subject) <confidence value="2">"</confidence>
+ pOMOWithTargetDomain - the percentage of the <confidence value="5">F</confidence>
+BL messages where the host was an odd-man-out with a target domain <confidence value="2">"</confidence>
+ pWithTargetDomain - the percentage of FBL messages where the host appeared and there was a target domain in the message and the host isn't a target host <confidence value="2">"</confidence>
+ pWithPhishWithTargetWord - the percentage of <confidence value="5">F</confidence>
+BL messages where the host appeared that had both a phishing trick and a target word <confidence value="1">*</confidence>
+ pWithPhishWithTargetPRD <confidence value="2">e</confidence>
+ isNumericHost [0073] <confidence value="5">I</confidence>
+n one implementation, hosts that appear in the report stream but not in the FBL have a -<confidence value="5">1</confidence>
+ for each of the probability-related features described above.    </p>
+    <p id="p-119" num="119">
+      <confidence value="5">[</confidence>
+0074] In one example implementation, to generate training data, various training examples (where the isPhish field is filled in) were used, along with a large number of testing examples. A decision tree was built on the classified training examples (with kappa = 0.8, other parameters at default). FIG. 4 shows one example resulting tree (the portion of the leaf that is shaded, if any, represents the probability that a given site that reaches that leaf is a phishing site). This model encodes the fact (among many <boundary-data type="header">- 43 -</boundary-data>
+      <page-break num="44"/>
+others) that if a host appears in emails that have a target word in the subject and is a numeric host, then the probability it is phishing is extremely high.    </p>
+    <p id="p-120" num="120">[0075]   The topmost node represented in FIG. 4 evaluates the number of target words in the subject line and/or message body (and/or site content) that if present, may indicate a phishing site. The branch direction depends on a numerical value corresponding to this evaluation. In this example decision tree, the "numIETP" decision node represents evaluating the number of browser users (or number per time period such as the last X hours) that reported the site as a true positive suspicious / phishing site; "numIEFN" is a similar number but related to false negatives.</p>
+    <p id="p-121" num="121">[0076]   The "pOMOWithTargetDo" decision node represents link structure analysis; the "Is Numeric Host" nodes evaluate the submitted site's host information, and the "pFBLGood" nodes test feedback loop data, which although useful in this example, may not be fast enough to use for many short-lived phishing sites. In any event, in this example a leaf is ultimately reached, providing the classification information <boundary-data type="header">
+        <confidence value="6">-</confidence>
+ 44 -      </boundary-data>
+      <page-break num="45"/>
+(a probability value in this example) for the site / message being evaluated.    </p>
+    <p id="p-122" num="122">[0077]   Applying this model to the testing data, along with hand examination of some of the messages from the FBL that linked to hosts that had a high probability of being phishing sites according to the model, proved that a large majority of the test sites that fell into the two most-probable phishing leaves were indeed phishing. As can be readily appreciated, investigating any new hosts that fall into these leaves is a reliable way to find new phishing sites. Depending on the classification, reaching a leaf for a site may correspond to taking action to block a site, unblock a site, suggest hand grading, warn users about the possibility of phishing, and any other action.</p>
+    <p id="p-123" num="123">[0078]   The following table shows some example statistics on the phish hit rate of the five "most phishy" leaves in the tree:</p>
+    <p id="p-124" num="124">
+      <confidence value="8">P</confidence>
+ <confidence value="86">(i</confidence>
+s   N<confidence value="48688">umber</confidence>
+  <confidence value="845558">Number</confidence>
+ Ph<confidence value="8">i</confidence>
+sh)     o<confidence value="5">f</confidence>
+    of Non<confidence value="4">-</confidence>
+   <confidence value="6866">Leaf</confidence>
+ <confidence value="688">Hit</confidence>
+ Fro<confidence value="8">m</confidence>
+     Phish   Ph<confidence value="4">i</confidence>
+sh      <confidence value="5286">Rate</confidence>
+ Model    <confidence value="22266">Found</confidence>
+  <confidence value="888888851">Examined.</confidence>
+    </p>
+    <p id="p-125" num="125">0.94      27        <part-num-ref name="">2</part-num-ref>
+      9<confidence value="6666">3.0%</confidence>
+ 0.72       <part-num-ref name="93.0% 0.72">3</part-num-ref>
+        <part-num-ref name="">0</part-num-ref>
+     100.0<confidence value="5">%</confidence>
+ <boundary-data type="header">- 45 -</boundary-data>
+      <page-break num="46"/>
+0.66       <part-num-ref name="100.0% 0.66">6</part-num-ref>
+       <part-num-ref name="">32</part-num-ref>
+      15.8% 0.65       <part-num-ref name="15.8% 0.65">2</part-num-ref>
+       <part-num-ref name="">26</part-num-ref>
+       7.1% 0.45       <part-num-ref name="7.1% 0.45">1</part-num-ref>
+        <part-num-ref name="">2</part-num-ref>
+      33.0% 0.21       <part-num-ref name="33.0% 0.21">4</part-num-ref>
+       <part-num-ref name="">23</part-num-ref>
+      14.8% [0079]   Note that the potential impact of a phishing attack also may be considered, e.g., in a separate or integrated predictive model. For example, if many users in terms of numbers are likely to be attacked, the action taken may be to block immediately, but only temporarily until the site can be hand graded for a permanent decision, regardless of the probability. The amount of potential damage may also be a factor, e.g., a particularly clever attempt to obtain credit card numbers may be treated as severe and blocked even if not that many users are being attacked. Post attack impact data may also be used for future training.    </p>
+    <p id="p-126" num="126">[0080]   FIG. 5 is a high-level representation of the training side of a PhishFinder system. Data sources 501-507, data processors 511-517 and report stores 521-527 may be similar components to counterpart components represented in the system of FIG. 3, e.g., the components may be shared between the training and performance sides of the same system.</p>
+    <p id="p-127" num="127">However, the report stores 521-527 for the training system may <boundary-data type="header">- 46 -</boundary-data>
+      <page-break num="47"/>
+contain data on longer time periods than does the performance system, e.g., roughly N <confidence value="8">d</confidence>
+ays of data before the first phishing site that will be trained on first appeared. Note that although the same variable N is used in FIG. 5, N need not be the same value in every report, there may be multiple N values per report (aggregating the same information over multiple time spans), and again, N may be a fraction and/or less than one.    </p>
+    <p id="p-128" num="128">[0081]   In general, a training report aggregator <part-num-ref name="training report aggregator">554</part-num-ref>
+ aggregates information from the report stores 501-507 into a description of how each phishing host (or URL) and confirmed non-phishing host (or URL) was observed in the data streams over the selected time windows. The training report aggregator <part-num-ref name="training report aggregator">554</part-num-ref>
+ may generate several aggregated reports per known phishing site, for example using one or more of the following methods:    </p>
+    <p id="p-129" num="129">
+      <confidence value="2">"</confidence>
+ Using information available immediately upon the first observation of the site in any of the data sources, or one for the first observation in each data source where the site was observed.    </p>
+    <p id="p-130" num="130">
+      <confidence value="2">"</confidence>
+ One for every J observations of the site in any data source (with a maximum of K). Or N reports divided so each captures an even number of the observations of the site in the data sources.    </p>
+    <boundary-data type="header">- 47 -</boundary-data>
+    <p id="p-131" num="131">
+      <page-break num="48"/>
+      <confidence value="2">"</confidence>
+ One per T hours of the lifetime of the site in any of the data sources (with a maximum of M). Or X reports divided evenly among the complete lifespan of the site in the data sources.    </p>
+    <p id="p-132" num="132">
+      <confidence value="2">"</confidence>
+ Generate one report per known phishing/non-phishing site per T hours of report data.    </p>
+    <p id="p-133" num="133">[0082]   Using some example values, an exemplary model generates a report using the information available at first observation, and then another one per every T hours (where <confidence value="885">T=l</confidence>
+) hours for the lifetime of that phishing attack, up to a maximum of M (where M=150).    </p>
+    <p id="p-134" num="134">
+      <confidence value="5">[</confidence>
+0083]   These examples of how phishing sites 550 and non- phishing sites <part-num-ref name="and non- phishing sites">552</part-num-ref>
+ (each of which are updated as graders grade new sites) appear in the data sources are fed as training data / aggregated host statistics <part-num-ref name="data sources are fed as training data / aggregated host statistics">556</part-num-ref>
+ to a machine learning algorithm <part-num-ref name="machine learning algorithm">558.</part-num-ref>
+ In turn the machine learning algorithm <part-num-ref name="machine learning algorithm">558</part-num-ref>
+ produces a predictive model <part-num-ref name="predictive model">560,</part-num-ref>
+ which, for example, may be used as the predictive model <part-num-ref name="predictive model">336</part-num-ref>
+ of FIG. 3. The training data / aggregated host statistics <part-num-ref name="training data / aggregated host statistics">556</part-num-ref>
+ contain data for known phishing sites at several time periods. Any algorithm that builds a classification model / probabilistic model is appropriate for generating the predictive model <part-num-ref name="predictive model">560</part-num-ref>
+ (or the predictive model <part-num-ref name="predictive model">336</part-num-ref>
+ of FIG. 3), e.g., one implementation used <boundary-data type="header">- 48 -</boundary-data>
+      <page-break num="49"/>
+a learning algorithm such as decision tree induction (FIG. 4), while others may employ logistic regression, support vector machines, some hybrid combination of these, and so forth. The predictive model may be changed as needed, e.g., hourly, daily, whenever a new site appears, and so forth, including combinations of these, as new information becomes available.    </p>
+    <p id="p-135" num="135">Note that client filtering code also may be updated based on what is learned as new information becomes available, e.g., client training may also be performed. Further, while a single model that integrates information from all of the data sources may be used, it is also feasible to use a separate model that predicts per data source whether a host/URL is phishing or not (e.g. P(host seen in FBL is phishing <confidence value="5">I</confidence>
+ how it appeared in FBL)), with a meta learner used to combine the probabilities of the individual models. Standard ensemble learning methods may be used to build a model (e.g. boosting)<confidence value="5">.</confidence>
+    </p>
+    <p id="p-136" num="136">[0084]   While the invention is susceptible to various modifications and alternative constructions, certain illustrated embodiments thereof are shown in the drawings and have been described above in detail. It should be understood, however, that there is no intention to limit the invention to <boundary-data type="header">- 49 -</boundary-data>
+      <page-break num="50"/>
+the specific forms disclosed, but on the contrary, the intention is to cover all modifications, alternative constructions, and equivalents falling within the spirit and scope of the invention.    </p>
+    <boundary-data type="header">- 50 -</boundary-data>
+  </description>
+</us-patent-application>
+

prior_art/11337276.xml

@@ -0,0 +1,142 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11337276</doc-number>
+        <date>2008-12-11</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <boundary-data type="header">U.S. Serial No. 11/337,276</boundary-data>
+    <boundary-data type="header">Response to the Office action of August 20, 2008</boundary-data>
+    <p id="p-1" num="1">In the Specification:</p>
+    <p id="p-2" num="2">Please amend paragraph <confidence value="5">[</confidence>
+0030<confidence value="5">]</confidence>
+ in the following manner:    </p>
+    <p id="p-3" num="3">
+      <confidence value="5">[</confidence>
+0030<confidence value="5">]</confidence>
+ To allow the example user device <part-num-ref name="example user device">115</part-num-ref>
+ of FIG. <confidence value="5">1</confidence>
+ to identify the example store (e.g., retailer, wholesaler, etc.) <part-num-ref name="retailer, wholesaler, etc.)">155,</part-num-ref>
+ the example store <part-num-ref name="example store">155</part-num-ref>
+ of FIG. 1 includes one or more of any variety of RF terminals [[160]] <part-num-ref name="includes one or more of any variety of RF terminals [[160]]">
+        <confidence value="666">158</confidence>
+.      </part-num-ref>
+ The example RF terminal [[160]] <part-num-ref name="example RF terminal [[160]]">158</part-num-ref>
+ of FIG. 1 implements, for instance, a WiFi access point that allows the user device <part-num-ref name="user device">115</part-num-ref>
+ to, among other things, identify, for example, the name, location, address, etc. of the store <part-num-ref name="store">155.</part-num-ref>
+ The example RF terminal [[160]] <part-num-ref name="example RF terminal [[160]]">
+        <confidence value="666">158</confidence>
+      </part-num-ref>
+ may also be used to communicatively couple the user device <part-num-ref name="user device">115</part-num-ref>
+ to web server <part-num-ref name="to web server">120</part-num-ref>
+ via the Internet <part-num-ref name="Internet">125.</part-num-ref>
+ The example R<confidence value="5">F</confidence>
+ terminal [[160]] <part-num-ref name="example RF terminal [[160]]">
+        <confidence value="666">158</confidence>
+      </part-num-ref>
+ of FIG. 1 may also be used to provide one or more files to the example user device <part-num-ref name="example user device">115</part-num-ref>
+ that the user device <part-num-ref name="user device">115</part-num-ref>
+ may then display for the user via any variety of user interfaces (e.g., a web browser). In the illustrated example, the files transferred to the user device <part-num-ref name="user device">115</part-num-ref>
+ include information on in- store coupons and/or in-store specials. For instance, the example store coupon management device <part-num-ref name="example store coupon management device">145</part-num-ref>
+ of FIG. 1 may access in-store coupon and/or in-store special information stored in, for example, a local coupon store <part-num-ref name="local coupon store">165.</part-num-ref>
+ The store coupon management device <part-num-ref name="store coupon management device">145</part-num-ref>
+ generates one or more image files (e.g., extensible markup language (XML) pages) containing the in-store coupon(s) and/or in-store special information, and the one or more image files are sent to the user device <part-num-ref name="user device">115</part-num-ref>
+ via the R<confidence value="5">F</confidence>
+ terminal [[160]] <part-num-ref name="RF terminal [[160]]">158.</part-num-ref>
+    </p>
+    <boundary-data type="header">Page 2 of 16</boundary-data>
+    <boundary-data type="header">U.S. Serial No. 11/337,276</boundary-data>
+    <boundary-data type="header">Response to the Office action of August 20, 2008</boundary-data>
+    <p id="p-4" num="4">
+      <page-break num="2"/>
+Please amend paragraph <confidence value="5">[</confidence>
+0031<confidence value="5">]</confidence>
+ in the following manner:    </p>
+    <p id="p-5" num="5">
+      <confidence value="5">[</confidence>
+0031<confidence value="5">]</confidence>
+ Additionally or alternatively, the example user device <part-num-ref name="example user device">115</part-num-ref>
+ of FIG. <confidence value="5">1</confidence>
+ may obtain coupons associated with the store <part-num-ref name="store">155</part-num-ref>
+ and/or the user by identifying the store <part-num-ref name="store">155</part-num-ref>
+ and/or the user directly to the web server <part-num-ref name="web server">120.</part-num-ref>
+ For instance, when entering a store <part-num-ref name="store">155,</part-num-ref>
+ the user device <part-num-ref name="user device">115</part-num-ref>
+ may detect the name and location of the store <part-num-ref name="store">155</part-num-ref>
+ via the RF terminal [[160]] <part-num-ref name="RF terminal [[160]]">
+        <confidence value="866">158</confidence>
+.      </part-num-ref>
+ The user device <part-num-ref name="user device">115</part-num-ref>
+ may then automatically request coupon information for the identified store <part-num-ref name="identified store">155</part-num-ref>
+ by, for example, sending a coupon request to the web server <part-num-ref name="web server">120.</part-num-ref>
+ In response, the example web server <part-num-ref name="example web server">120</part-num-ref>
+ of FIG. <confidence value="5">1</confidence>
+ provides one or more image files (e.g., web pages) to the user device <part-num-ref name="user device">115</part-num-ref>
+ containing a list of coupons that the user may be interested in and/or that may apply to items for sale in the store <part-num-ref name="store">155.</part-num-ref>
+ For instance, the example web server <part-num-ref name="example web server">120</part-num-ref>
+ of FIG. <confidence value="5">1</confidence>
+ forwards coupons, from the user's coupon account and/or from the master coupon database <part-num-ref name="master coupon database">106,</part-num-ref>
+ for items that are actually sold at the store <part-num-ref name="store">155.</part-num-ref>
+ The forwarded coupons may be limited to only items that are actually available in the store <part-num-ref name="store">155.</part-num-ref>
+ The forwarded coupons may include coupons from a competitor to the store <part-num-ref name="store">155</part-num-ref>
+ in which the user device <part-num-ref name="user device">115</part-num-ref>
+ is located to enable the user to consider alternative shopping locations and/or to request the current store <part-num-ref name="current store">155</part-num-ref>
+ to honor the competitor's coupon.    </p>
+    <p id="p-6" num="6">Please amend paragraph <confidence value="5">[</confidence>
+0032<confidence value="5">]</confidence>
+ in the following manner:    </p>
+    <p id="p-7" num="7">
+      <confidence value="5">[</confidence>
+0032<confidence value="5">]</confidence>
+ To allow a user (via the example user device <part-num-ref name="example user device">115</part-num-ref>
+ and/or the example web- enabled device <part-num-ref name="example web- enabled device">135)</part-num-ref>
+ to identify coupons associated with yellow page directory entries, the example coupon management system <part-num-ref name="example coupon management system">110</part-num-ref>
+ of FIG. <confidence value="5">1</confidence>
+ includes a yellow pages database <part-num-ref name="yellow pages database">160.</part-num-ref>
+ In the example of FIG. 1, a user may perform any variety of yellow page search(es) via the example user device <part-num-ref name="example user device">115</part-num-ref>
+ and/or the example user web-enabled device <part-num-ref name="example user web-enabled device">135.</part-num-ref>
+ In the illustrated example, the search results may return, in addition to phone numbers, addresses, websites, <boundary-data type="header">Page 3 of 16</boundary-data>
+      <page-break num="3"/>
+      <boundary-data type="header">U.S. Serial No. 11/337,276</boundary-data>
+      <boundary-data type="header">Response to the Office action of August 20, 2008</boundary-data>
+etc., information regarding one or more coupons and/or links to coupons offered by the identified businesses and/or persons. For example, a yellow page search may locate two florists and indicate that the first florist offers an electronic coupon. In the example system of FIG. 1, the yellow page search(es) may include the location of the example user device <part-num-ref name="example user device">115</part-num-ref>
+ and/or the iden<confidence value="8">t</confidence>
+i<confidence value="8">f</confidence>
+y identified coupons may depend upon the location. For instance, a coupon may be identified to a user if the user is near enough to a location such that the coupon might entice the user to immediately make a purchase based on the offered coupon. As described below in connection with FIGS. 4A-5, the user may add the coupon offered via the yellow pages search to their coupon account, and then apply the coupon to a subsequent purchase made at the first florist.    </p>
+    <p id="p-8" num="8">Please amend paragraph <confidence value="5">[</confidence>
+0055<confidence value="5">]</confidence>
+ in the following manner:    </p>
+    <p id="p-9" num="9">
+      <confidence value="5">[</confidence>
+0055<confidence value="5">]</confidence>
+ In the illustrated example of FIG. 5, the POS terminal <part-num-ref name="POS terminal">140</part-num-ref>
+ displays and/or otherwise provides the order identifier <part-num-ref name="order identifier">520</part-num-ref>
+ to the user <part-num-ref name="user">405</part-num-ref>
+ [[who]]. As described above, the user <part-num-ref name="user">405</part-num-ref>
+ then enters the order identifier <part-num-ref name="order identifier">520</part-num-ref>
+ into the user device <part-num-ref name="user device">115,</part-num-ref>
+ which in turn, provides the order identifier <part-num-ref name="order identifier">520</part-num-ref>
+ and the subscriber identifier <part-num-ref name="subscriber identifier">415</part-num-ref>
+ to the web server <part-num-ref name="web server">120</part-num-ref>
+ as indicated with reference numeral <part-num-ref name="as indicated with reference numeral">525.</part-num-ref>
+ For example, the user <part-num-ref name="user">405</part-num-ref>
+ may enter the order identifier <part-num-ref name="order identifier">520</part-num-ref>
+ and the subscriber identifier <part-num-ref name="subscriber identifier">415</part-num-ref>
+ into an interface (e.g., a web page) displayed on the user device <part-num-ref name="user device">115.</part-num-ref>
+ Alternatively, the P<confidence value="66">OS</confidence>
+ terminal <part-num-ref name="POS terminal">140</part-num-ref>
+ and the user device <part-num-ref name="user device">115</part-num-ref>
+ may be communicatively coupled and the user device <part-num-ref name="user device">115</part-num-ref>
+ may obtain the order identifier <part-num-ref name="order identifier">520</part-num-ref>
+ directly from the P<confidence value="66">OS</confidence>
+ terminal <part-num-ref name="POS terminal">140</part-num-ref>
+ without user inputs.    </p>
+    <boundary-data type="header">Page 4 of 16</boundary-data>
+  </description>
+</us-patent-application>
+

prior_art/11348168.xml

@@ -0,0 +1,241 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
+<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>11348168</doc-number>
+        <date>2006-02-06</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <boundary-data type="header">15522</boundary-data>
+    <heading id="h-1">WELDING WIRE FEED SPEED CONTROL SYSTEM METHOD</heading>
+    <heading id="h-2">BACKGROUND</heading>
+    <p id="p-1" num="1">
+      <confidence value="5">[</confidence>
+0001]   The present invention relates generally to wire-feed welding devices and, in certain embodiments, to methods and apparatus for controlling wire electrode advancement.    </p>
+    <p id="p-2" num="2">[0002<confidence value="5">]</confidence>
+   A common metal welding technique employs the heat generated by electrical arcing to transition a workpiece to a molten state, to facilitate a welding process. One technique that employs this arcing principle is wire-feed welding. At its essence, wire- feed welding involves routing welding current from a power source into an electrode that is brought into close proximity with the workpiece. When close enough, current arcs from the electrode to the workpiece, completing a circuit and generating sufficient heat to weld the workpiece. Often, the electrode is consumed and becomes part of the weld itself. Thus, new wire electrode is advanced, replacing the consumed electrode and maintaining the welding arc. If the welding device is properly adjusted, the wire-feed advancement and arcing cycle progresses smoothly, providing a good weld.    </p>
+    <p id="p-3" num="3">[0003]   Traditionally, during a welding operation, an operator selects the level and types of resources provided to the weld location, depending, of course, on the particulars of the weld and the materials being welded. For instance, an operator may select between various kinds and sizes of wire electrode, ranging from the diameter of wire the electrode to the material the wire electrode is made of. Different kinds of wire electrode, however, perform well at different operational settings of the welding device. That is, different kinds of wire electrodes perform well within different voltage ranges and wire-feed speeds, for instance. For example, a given 0.023 inch mild-steel wire electrode may well perform at <part-num-ref name="given 0.023 inch mild-steel wire electrode may well perform at">17</part-num-ref>
+ Volts and with a wire-feed speed of <part-num-ref name="wire-feed speed of">250</part-num-ref>
+ inches per minute, while a 0.035 inch mild steel wire electrode well performs at <part-num-ref name="0.035 inch mild steel wire electrode well performs at">19</part-num-ref>
+ Volts with a wire-feed speed of <part-num-ref name="wire-feed speed of">230</part-num-ref>
+ inches per minute.    </p>
+    <boundary-data type="header">
+      <confidence value="6">1</confidence>
+    </boundary-data>
+    <boundary-data type="header">15522</boundary-data>
+    <p id="p-4" num="4">
+      <page-break num="2"/>
+[0004]   Conventionally, welding devices rely on the knowledge and acumen of the operator to select the most appropriate voltage and wire feed settings for the wire electrode being used and weld conditions. Unfortunately, in many cases, the weld operator is a novice to field, especially in the case of portable welding devices. If the operator does not properly adjust the voltage and wire-feed speed settings, the arcing may not be sufficient to produce a good weld, or a weld at all. Furthermore, in traditional devices, the wire-feed speed control and the voltage control are wholly independent from one another, thus making it difficult for the operator to adjust the both parameters while a weld is progressing.    </p>
+    <p id="p-5" num="5">[0005]   Therefore, there exists a need for improved apparatus and methods for the control of wire-feed welding devices.</p>
+    <heading id="h-3">BRIEF DESCRIPTION</heading>
+    <p id="p-6" num="6">[0006]  In accordance with one embodiment, the present technique provides a welding system in which the rate of advancement of wire electrode is determined automatically.</p>
+    <p id="p-7" num="7">For example, the device can include a control circuit that determines the rate of advancement of the wire electrode in response to a signal from the voltage selection device of the welding system. Thus, depending upon the operator selected voltage- which is selected via a voltage selection device- the control circuit will determine the appropriate rate of wire electrode advancement and control the advancement mechanism (e.g., electric motor) accordingly. Advantageously, linking the voltage level and wire- feed speed controls facilities easy of use for more novice operators and, furthermore, facilitates single-handed adjustment of two operational parameters during a welding process, for instance.</p>
+    <heading id="h-4">DRAW<confidence value="8">I</confidence>
+NGS    </heading>
+    <p id="p-8" num="8">[0007]  These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference <boundary-data type="header">
+        <confidence value="8">2</confidence>
+      </boundary-data>
+      <page-break num="3"/>
+      <boundary-data type="header">15522</boundary-data>
+to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:    </p>
+    <p id="p-9" num="9">
+      <confidence value="5">[</confidence>
+0008<confidence value="5">]</confidence>
+   FIG. 1 is a diagrammatic representation of a wire-feed welding system, in accordance with an exemplary embodiment of the present technique;    </p>
+    <p id="p-10" num="10">
+      <confidence value="5">[</confidence>
+0009<confidence value="5">]</confidence>
+   FIG. 2 is a schematic representation of a wire-feed welding system control, in accordance with an exemplary embodiment of the present technique; and [0010<confidence value="5">]</confidence>
+   FIG. 3 is a diagrammatic representation of a wire-feed welding system control, in accordance with an exemplary embodiment of the present technique; and <confidence value="5">[</confidence>
+0011<confidence value="5">]</confidence>
+   FIG. 4 is a diagrammatic representation of a wire-feed welding system control panel, in accordance with an exemplary embodiment of the present technique.    </p>
+    <heading id="h-5">DETAILED DESCRIPTION</heading>
+    <p id="p-11" num="11">[0012]   As discussed in detail below, the present technique, in accordance with certain embodiments, provides method and apparatus for controlling the advancement of wire electrode in a welding device. For example, a metal-inert-gas (MIG) welding system incorporating the present technique can include an "AUTO" setting that links the wire- feed speed to the voltage-level or vice-versa. Thus, in such a system, if an operator were to adjust the voltage to the wire electrode, the wire-feed speed would be automatically adjusted to accommodate the new voltage setting. Alternatively, the selected wire-feed speed can automatically determine an ouput voltage level. Advantageously, the linked relationship between the voltage-level control and the wire-feed control can assist an operator in obtaining desirable performance and, furthermore, can facilitate multifunctional control of the welding device via a single input knob. FIG. 1 illustrates an exemplary welding system that includes an embodiment of this wire-feed control technique. Indeed, the system <part-num-ref name="system">10</part-num-ref>
+ may be for portable use, and such systems are often stationed by less-experienced operators. However, prior to continuing, it is worth noting that the following discussion merely relates to exemplary embodiments of the present <boundary-data type="header">
+        <confidence value="8">3</confidence>
+      </boundary-data>
+      <page-break num="4"/>
+      <boundary-data type="header">15522</boundary-data>
+technique. Thus, the appended claims should not be viewed as limited to those embodiments described herein.    </p>
+    <p id="p-12" num="12">[0013<confidence value="5">]</confidence>
+   Returning to the exemplary welding system <part-num-ref name="exemplary welding system">10,</part-num-ref>
+ it includes a welding torch <part-num-ref name="welding torch">12</part-num-ref>
+ that defines the location of the welding operation with respect to a workpiece <part-num-ref name="workpiece">14.</part-num-ref>
+    </p>
+    <p id="p-13" num="13">Placement of the welding torch <part-num-ref name="welding torch">12</part-num-ref>
+ at a location proximate to the workpiece <part-num-ref name="workpiece">14</part-num-ref>
+ allows electrical current provided by a power source 16-which converts incoming alternating current (ac) power to an appropriate direct current (dc) power-and routed to the welding torch <part-num-ref name="welding torch">12</part-num-ref>
+ via a welding torch cable <part-num-ref name="welding torch cable">18,</part-num-ref>
+ to arc from the welding torch <part-num-ref name="welding torch">12</part-num-ref>
+ to the workpiece <part-num-ref name="workpiece">14.</part-num-ref>
+ In summary, this arcing completes an electrical circuit from the power source <part-num-ref name="power source">16,</part-num-ref>
+ to the welding torch <part-num-ref name="welding torch">12</part-num-ref>
+ via the welding torch cable <part-num-ref name="welding torch cable">18,</part-num-ref>
+ to a wire electrode, to the workpiece <part-num-ref name="workpiece">14,</part-num-ref>
+ and, at its conclusion, back to the power source <part-num-ref name="power source">16,</part-num-ref>
+ generally to ground.    </p>
+    <p id="p-14" num="14">Advantageously, this arcing generates a relatively large amount of heat causing the workpiece <part-num-ref name="workpiece">14</part-num-ref>
+ <confidence value="222222">and/or</confidence>
+ filler metal to transition to a molten state, facilitating the weld.    </p>
+    <p id="p-15" num="15">[0014]   To produce electrical arcing, the exemplary system <part-num-ref name="exemplary system">10</part-num-ref>
+ includes a wire-feeder <part-num-ref name="wire-feeder">20</part-num-ref>
+ that provides a consumable wire electrode to the welding torch cable <part-num-ref name="welding torch cable">18</part-num-ref>
+ and, in turn, to the welding torch <part-num-ref name="welding torch">12.</part-num-ref>
+ The welding torch <part-num-ref name="welding torch">12</part-num-ref>
+ conducts electrical current to the wire electrode via a contact tip (not shown) located in the neck assembly, leading to arcing between the egressing wire electrode and the workpiece <part-num-ref name="workpiece">14.</part-num-ref>
+    </p>
+    <p id="p-16" num="16">
+      <confidence value="5">[</confidence>
+0015]   To shield the weld area from contaminants during welding, to enhance ar<confidence value="5">c</confidence>
+ performance, and to improve the resulting weld, the exemplary system <part-num-ref name="exemplary system">10</part-num-ref>
+ includes a gas source <part-num-ref name="gas source">22</part-num-ref>
+ that feeds an inert, shielding gas to the welding torch <part-num-ref name="welding torch">12</part-num-ref>
+ via the welding torch cable <part-num-ref name="welding torch cable">18.</part-num-ref>
+ It is worth noting, however, that a variety of shielding materials, including various fluids and particulate solids, may be employed to protect the weld location.    </p>
+    <p id="p-17" num="17">Additionally, certain wire electrodes are designed to operate without a shielding material.</p>
+    <p id="p-18" num="18">[0016]   Advancement of these welding resources (e.g., welding current, wire-electrode, and shielding gas) is effectuated by actuation of a trigger <part-num-ref name="trigger">24</part-num-ref>
+ secured to a handle <part-num-ref name="handle">26.</part-num-ref>
+ By depressing the trigger <part-num-ref name="trigger">24</part-num-ref>
+ (arrow 28), a switch disposed within the trigger <part-num-ref name="trigger">24</part-num-ref>
+ is closed, <boundary-data type="header">
+        <confidence value="8">4</confidence>
+      </boundary-data>
+      <page-break num="5"/>
+      <boundary-data type="header">15522</boundary-data>
+causing the transmission of an electrical signal that commands promotion of the welding resources into the welding torch cable <part-num-ref name="welding torch cable">18.</part-num-ref>
+ For example, depressing the trigger <part-num-ref name="trigger">24</part-num-ref>
+ sends a signal to the control circuitry <part-num-ref name="control circuitry">30,</part-num-ref>
+ which, in turn, activates a motor <part-num-ref name="motor">32</part-num-ref>
+ that advances wire electrode into the welding torch cable <part-num-ref name="welding torch cable">18,</part-num-ref>
+ opens a valve to allow the flow of shielding material, and commands the power source to output the desired level of power to the wire electrode. Advantageously, the control circuitry <part-num-ref name="control circuitry">30</part-num-ref>
+ includes memory components <part-num-ref name="includes memory components">34,</part-num-ref>
+ to store programming instructions, command programs, appropriate data, etc. The control circuitry <part-num-ref name="control circuitry">30</part-num-ref>
+ also includes a processing device, such as a processor <part-num-ref name="processor">36,</part-num-ref>
+ a programming logic circuit (PLC), among others types of devices, to effectuate control of the welding system <part-num-ref name="welding system">10.</part-num-ref>
+    </p>
+    <p id="p-19" num="19">
+      <confidence value="5">[</confidence>
+0017]  To adjust operating parameters of the welding system <part-num-ref name="welding system">10,</part-num-ref>
+ a pair of input devices are provided: a wire-feed speed controller <part-num-ref name="wire-feed speed controller">38</part-num-ref>
+ and a voltage controller <part-num-ref name="voltage controller">40.</part-num-ref>
+ As illustrated, these input devices are potentiometer devices (i.e., POTS); however, other kinds of input devices, such as keypads, are envisaged. Each POT controller comprises a knob <part-num-ref name="knob">42</part-num-ref>
+ that is positionable between indexed locations that correspond with certain operational parameters. For example, in the illustrated welding system <part-num-ref name="illustrated welding system">10,</part-num-ref>
+ the power source <part-num-ref name="power source">16</part-num-ref>
+ outputs power within the operational range of ten to forty volts. An operator can control the output voltage to the wire electrode by turning the knob <part-num-ref name="knob">42</part-num-ref>
+ on the voltage controller <part-num-ref name="voltage controller">40</part-num-ref>
+ between the indexed positions, which are labeled from "1" to "7". If a voltage closer to <part-num-ref name="voltage closer to">40</part-num-ref>
+ V is desired, the knob <part-num-ref name="knob">42</part-num-ref>
+ can be turned toward the "7" position.    </p>
+    <p id="p-20" num="20">Conversely, if less output voltage is desired, the knob <part-num-ref name="knob">42</part-num-ref>
+ on the voltage controller <part-num-ref name="voltage controller">40</part-num-ref>
+ can be turned toward the "1" position. Similarly, the wire-feed speed of the system <part-num-ref name="system">10</part-num-ref>
+ can be adjusted by rotating the knob <part-num-ref name="knob">42</part-num-ref>
+ of the wire-feed speed controller <part-num-ref name="wire-feed speed controller">38</part-num-ref>
+ between the "3" and "7" positions, with the "3" position being a lowest operating wire-feed speed (e.g., <part-num-ref name="">75</part-num-ref>
+ inches per minute) and "7" being the fastest (e.g., <part-num-ref name="">1400</part-num-ref>
+ inches per minute).    </p>
+    <p id="p-21" num="21">
+      <confidence value="5">[</confidence>
+0018]  When left in a manual mode, the operator relies on his or her welding acumen to select the appropriate voltage-level and wire-feed speed settings, based on the type of weld to be made, the kind and size of the wire electrode, among other relevant factors.    </p>
+    <boundary-data type="header">
+      <confidence value="8">5</confidence>
+    </boundary-data>
+    <boundary-data type="header">15522</boundary-data>
+    <p id="p-22" num="22">
+      <page-break num="6"/>
+Many operators, however, may not have the breadth of experience and knowledge generally beneficial to make such decisions. Resultantly, maladjustment of the welding system <part-num-ref name="welding system">10</part-num-ref>
+ is possible. For example, if the wire-feed speed setting is too slow in comparison to the voltage level setting, then an ar<confidence value="5">c</confidence>
+ may not form or may extinguish prematurely. Conversely, if the wire-feed speed setting is too fast for the given voltage level setting, then the quality of the weld may be reduced. Additionally, when the system is in a manual mode, an operator may benefit from adjustments in the voltage setting, which, in turn, benefits from adjustments in the wire-feed speed setting. Unfortunately, in a manual mode, the operator may find it difficult to maintain the arc by depressing the trigger <part-num-ref name="trigger">24</part-num-ref>
+ while concurrently manipulating both the wire-feed speed controller <part-num-ref name="wire-feed speed controller">38</part-num-ref>
+ and the voltage controller <part-num-ref name="voltage controller">40.</part-num-ref>
+    </p>
+    <p id="p-23" num="23">
+      <confidence value="5">[</confidence>
+0019<confidence value="5">]</confidence>
+   To alleviate such concerns, the exemplary welding system <part-num-ref name="exemplary welding system">10</part-num-ref>
+ includes an "AUTO" setting <part-num-ref name="&quot;AUTO&quot; setting">44</part-num-ref>
+ on the wire-feed speed controller <part-num-ref name="wire-feed speed controller">38.</part-num-ref>
+ As illustrated in FIG. 2, placement of the wire-feed speed controller <part-num-ref name="wire-feed speed controller">38</part-num-ref>
+ at the "AUTO" setting <part-num-ref name="&quot;AUTO&quot; setting">44</part-num-ref>
+ transitions the welding system <part-num-ref name="welding system">10</part-num-ref>
+ from a manual mode to a more automated mode. For example, by selecting the "AUTO" setting <part-num-ref name="&quot;AUTO&quot; setting">44,</part-num-ref>
+ the control circuitry <part-num-ref name="control circuitry">30</part-num-ref>
+ automatically links the voltage level setting and the wire-feed speed setting, automatically adjusting the wire-feed speed setting based on the selected voltage level setting. As illustrated, when the voltage controller <part-num-ref name="voltage controller">40</part-num-ref>
+ is placed at the "4" location, the control circuitry <part-num-ref name="control circuitry">30,</part-num-ref>
+ in cooperation with its processor <part-num-ref name="control circuitry 30, in cooperation with its processor">36</part-num-ref>
+ and data stored in the memory <part-num-ref name="memory">34,</part-num-ref>
+ determines the appropriate wire-feed speed setting, in this case the wire-feed setting corresponding to a voltage level setting of "4." This correlation can be made via the use of a look-up table <part-num-ref name="look-up table">46</part-num-ref>
+ stored in the memory <part-num-ref name="memory">34,</part-num-ref>
+ or can be made via the use of an appropriate algorithm, among various other techniques for correlation.    </p>
+    <p id="p-24" num="24">
+      <confidence value="5">[</confidence>
+0020<confidence value="5">1</confidence>
+   Also, the "AUTO" setting may be found on the voltage control, the system determining a wire-feed speed based on selected voltage level.    </p>
+    <p id="p-25" num="25">[0021<confidence value="5">]</confidence>
+   During operation, the operator may determine that a more appropriate voltage setting is desired, adjusting the voltage controller <part-num-ref name="voltage controller">40</part-num-ref>
+ setting to the "3" position, for <boundary-data type="header">
+        <confidence value="8">6</confidence>
+      </boundary-data>
+      <page-break num="7"/>
+      <boundary-data type="header">15522</boundary-data>
+instance. In turn, the control circuitry <part-num-ref name="control circuitry">30</part-num-ref>
+ will determine the appropriate wire-feed speed setting-based on the look-up table <part-num-ref name="look-up table">46</part-num-ref>
+ or a stored algorithm, for example-and instruct to wire-feed motor <part-num-ref name="stored algorithm, for example-and instruct to wire-feed motor">32</part-num-ref>
+ to operate at this designated speed. Advantageously, the operator can adjust both the wire-feed speed and voltage level parameters through the manipulation of a single knob <part-num-ref name="single knob">42</part-num-ref>
+ on the voltage controller <part-num-ref name="voltage controller">40.</part-num-ref>
+    </p>
+    <p id="p-26" num="26">[0022<confidence value="5">]</confidence>
+   Turning to FIG. 3, this figure represents a wire-feed speed control scheme for a voltage controller <part-num-ref name="voltage controller">40</part-num-ref>
+ essentially having an infinite number of voltage settings between the "1" and "7" positions. With this controller <part-num-ref name="&quot;1&quot; and &quot;7&quot; positions. With this controller">40,</part-num-ref>
+ an operator may select from an essentially infinite number of voltage settings in the operational range of the welding system <part-num-ref name="welding system">10</part-num-ref>
+ simply by slightly adjusting or "tweaking" the position of the knob <part-num-ref name="knob">42.</part-num-ref>
+    </p>
+    <p id="p-27" num="27">However, the wire-feed speed setting, when the controller <part-num-ref name="controller">38</part-num-ref>
+ is in the "AUTO" position, is automatically selected based on the range of values the voltage controller <part-num-ref name="voltage controller">40</part-num-ref>
+ is within.    </p>
+    <p id="p-28" num="28">For example, the illustrated voltage controller <part-num-ref name="illustrated voltage controller">40</part-num-ref>
+ is set at a position slightly beyond the midpoint between the "3" and "4" settings. At this voltage setting, the control circuitry <part-num-ref name="control circuitry">30</part-num-ref>
+ determines that the wire-feed speed setting corresponding to a voltage setting of <confidence value="5">"</confidence>
+4", which may be gleaned from the look-up table <part-num-ref name="look-up table">46,</part-num-ref>
+ is to be applied. In fact, as illustrated, the control circuitry <part-num-ref name="control circuitry">30</part-num-ref>
+ commands the wire-feed motor <part-num-ref name="wire-feed motor">32</part-num-ref>
+ to operate at the wire-feed speed corresponding to a voltage level setting of "4" if the voltage control is set at or beyond the mid-point between the "3" and "4" settings, and at or before the mid-point between the "4" and "5" settings. This wire-feed speed setting scheme can be, of course, extended to the other voltage settings. For instance, the wire-feed speed setting for the voltage level setting of "4" may be applied when the voltage controller <part-num-ref name="voltage controller">40</part-num-ref>
+ is set at a location at or beyond the "4" setting but at or before the "5" setting. Alternatively, and by way of example, the wire-feed speed setting may be based on an algorithm, thus providing an automatically determined wire-feed speed essentially for each possible voltage setting between the "1" and "7" positions.    </p>
+    <p id="p-29" num="29">
+      <confidence value="5">[</confidence>
+0023]   FIG. 4 represents yet another alternative, exemplary mechanism for coupled control of the wire-feed speed and voltage level. As illustrated, the "AUTO" setting on <boundary-data type="header">
+        <confidence value="8">7</confidence>
+      </boundary-data>
+      <page-break num="8"/>
+      <boundary-data type="header">15522</boundary-data>
+the wire-feed speed controller <part-num-ref name="wire-feed speed controller">42</part-num-ref>
+ is segregated into two sub-sections, each for a different kind or size of welding wire. By way of example, one sub-section corresponds to a mild steel wire electrode having a diameter of 0.030 inches and the other corresponds to a mild steel wire electrode having a diameter of 0.024 inches, for example. It is, however, worth noting that the "AUTO" section can be divided into any number of sub-section, each corresponding to a different type or size of wire electrode. Depending upon the sub- section selected, the advancement rate of the wire electrode for a given voltage setting is changed. For example, if the wire-feed speed controller <part-num-ref name="wire-feed speed controller">42</part-num-ref>
+ is placed at the ".030" setting, the control circuitry <part-num-ref name="control circuitry">30</part-num-ref>
+ will select from a first look-up table that corresponds with the 0.30 inch wire electrode to determine the wire-feed speed for the given voltage setting.    </p>
+    <p id="p-30" num="30">Moreover, as the voltage setting is changed, the control circuit will remain within the first look-up table, selecting the wire-feed speed corresponding to the newly selected voltage.</p>
+    <p id="p-31" num="31">However, if the wire-feed speed controller is placed at the ".024" setting, the control circuitry <part-num-ref name="control circuitry">30</part-num-ref>
+ will look to a second, different look-up table to select the wire-feed setting for the given voltage setting. Moreover, as the voltage setting is changed, the control circuitry <part-num-ref name="control circuitry">30</part-num-ref>
+ will remain within this second look-up table, selecting the wire-feed speed corresponding to the newly selected voltage. Thus, the operator can automate the wire- feed setting selection to best suit the type of wire electrode employed. Of course, the wire-feed speed, rather than being selected from a look-up table, can be determined based on an appropriate algorithm, each algorithm corresponding to the type and kind of wire electrode employed, among other techniques. Where desired, a further input device may be provided for selecting which wire size or electrode type is being used. In certain implementations, the same input device may provide multiple positions or selection settings, certain of them corresponding to specific sizes or types of electrodes.    </p>
+    <p id="p-32" num="32">
+      <confidence value="5">[</confidence>
+0024]   As a further alternative, an input device that functions along with or in place of knob <part-num-ref name="input device that functions along with or in place of knob">40</part-num-ref>
+ may be employed directly on the welding torch. For example, an adjustment knob or button (e.g., a rocker switch) might be provided on the handle of the welding torch itself<confidence value="5">.</confidence>
+ Where desired, a signal then is taken from a conductor extending to the switch that is interpreted by the controller. The effect of the signal may be to increase <boundary-data type="header">
+        <confidence value="8">8</confidence>
+      </boundary-data>
+      <page-break num="9"/>
+      <boundary-data type="header">15522</boundary-data>
+and decrease the applied voltage, with wire feed speed being controlled as a function of the voltage, or vice versa. Such an arrangement would permit adjustments to the voltage and wire feed speed to be made while a welder is working remotely from the base unit, such as at the position of a workpiece or work area, without interrupting the work to return to the base unit.    </p>
+    <p id="p-33" num="33">
+      <confidence value="5">[</confidence>
+0025]   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>
+    <boundary-data type="header">
+      <confidence value="8">9</confidence>
+    </boundary-data>
+  </description>
+</us-patent-application>
+