Add files using upload-large-folder tool

applicant/10526848.xml

@@ -0,0 +1,501 @@
+<?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>10526848</doc-number>
+        <date>2005-03-03</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">
+      <confidence value="26">"/</confidence>
+     <confidence value="5">'</confidence>
+                                 <confidence value="1822282588">1U35A60848</confidence>
+ DT15 Rec<confidence value="5">'</confidence>
+d PCT/PTO     0 <part-num-ref name="">
+        <confidence value="6">3</confidence>
+      </part-num-ref>
+ WO 20<confidence value="5">0</confidence>
+4/023849                                              PCT<confidence value="5">/</confidence>
+IB2003/0039<confidence value="68">81</confidence>
+     </p>
+    <heading id="h-1">MASTERSLAVE ORIENTED TWO-WAY RF WIRELESS LI<confidence value="6">G</confidence>
+HTING    </heading>
+    <heading id="h-2">CONTROL SYSTEM</heading>
+    <heading id="h-3">BACKGROUND OF THE INVENTION</heading>
+    <p id="p-2" num="2">
+      <boundary-data type="line-number">5   </boundary-data>
+1. Field of the Invention The present invention relates to a lighting control system, and particularly to a master-slave oriented two-way radio frequency (RF) lighting control system.    </p>
+    <p id="p-3" num="3">
+      <boundary-data type="line-number">10   </boundary-data>
+2. Description of the Related Art Conventional building lighting systems, both residential and commercial, include numerous lighting units controlled by wall switches interconnected together by electrical wiring. Any changes and modifications to the lighting system are either constrained by the electrical wiring or require re-wiring of the lighting system. Conventional lighting <boundary-data type="line-number">15   </boundary-data>
+system configurations are therefore inflexible and costly to modify.    </p>
+    <p id="p-4" num="4">Lighting system control configurations range from simple to complex. In one of the simplest control schemes, lights are turned on/off by dedicated wall switches located, typically, in the same room as the lights controlled by the wall mounted switches.</p>
+    <p id="p-5" num="5">
+      <boundary-data type="line-number">20   </boundary-data>
+Additionally, wall dimmers may be used to control (i.e., vary) the intensity of the lights.    </p>
+    <p id="p-6" num="6">More complicated control functions such as grouping, preset lighting scenes, dimming and lighting based on ambient light, occupancy, and other factors can be implemented to provide intelligent control of the building lighting system. Such intelligent lighting system control may be implemented using an open, proprietary, or a standard lighting <boundary-data type="line-number">25   </boundary-data>
+control command set such as, for example, the industry-standard DALI (Digital Addressable Lighting Interface). However, retrofitting and/or modifying a lighting system for DALI requires extra control wires for connecting a control box to the lighting units' ballast. Also, the conventionally wired DA<confidence value="66">LI</confidence>
+ system has the disadvantage of added installation cost and retrofit inflexibility.    </p>
+    <p id="p-7" num="7">
+      <confidence value="88">30</confidence>
+ <boundary-data type="header">
+        <confidence value="4">1</confidence>
+      </boundary-data>
+      <page-break num="2"/>
+      <boundary-data type="header">WO 2004/023849                                              PCT/IB2003/003981</boundary-data>
+In some lighting systems a remote control unit is used, for example, to provide user convenience in controlling the lights. In most of such lighting systems, the remote control communication is based on <confidence value="5">I</confidence>
+R (infrared) technology. <confidence value="5">I</confidence>
+R communication requires a line-of-sight between the <confidence value="5">I</confidence>
+R linked devices and have a limited range based on certain <boundary-data type="line-number">
+        <confidence value="5">5</confidence>
+         </boundary-data>
+output power limits. Accordingly, lighting systems relying on <confidence value="5">I</confidence>
+R communication are suitable for simple control functions limited to small areas such as a single room within a building. To communicate using <confidence value="66">IR</confidence>
+ over a large area requires increased transmitting power and/or repeaters, both of which are a costly proposition. <confidence value="6">.</confidence>
+    </p>
+    <p id="p-8" num="8">
+      <boundary-data type="line-number">10         </boundary-data>
+RF technology has the advantages of flexibility and ease of installation. It can be used for both local control (one room) and wide area control (building wide). Currently there are some RF-based lighting control systems. U. S. Pat. No. 6,174,073 describes a lighting system including a plurality of lighting units each having an illumin<confidence value="8">a</confidence>
+tion element and an associated switch (i.e., control box) responsive to a RF (radio frequency) signal, <boundary-data type="line-number">15   </boundary-data>
+and remote control switch units for transmitting RF signals to the lighting units. The <confidence value="5">'</confidence>
+073 patent discloses a lighting system using one-way communication between the remote control units and the control box attached to conventional electronic analog ballasts. The signal transmitted from the remote control switch unit is received by the control circuitry of the light unit to control a switch between the mains power supply and the ballast. The <boundary-data type="line-number">20   </boundary-data>
+remote   control  switch  turns  on/off  and   dims   the  lighting  units  by connecting/disconnecting the lighting to the power supply. The disclosed system may be used for retrofits to convert manually operated wall switches into remote/handheld wireless controlled switches. However, since communication in the <confidence value="5">'</confidence>
+073 system is one- way, there is no data feed back from the ballast to the remote control unit.    </p>
+    <p id="p-9" num="9">
+      <confidence value="88">25</confidence>
+ <boundary-data type="header">
+        <confidence value="8">2</confidence>
+      </boundary-data>
+      <page-break num="3"/>
+      <boundary-data type="header">WO 2004/023849                                              PCT/<confidence value="5">I</confidence>
+B2003/003981      </boundary-data>
+Other lighting systems use a proprietary protocol for two-way RF communications between the remote control units and the luminaries. These systems also use additional circuit<confidence value="8">r</confidence>
+y outside of the luminary ballast, such as an actuator, as the communication interface for exchanging information with the remote control unit. The actuator, in <boundary-data type="line-number">5 </boundary-data>
+response to the signal received from the remote control unit, outputs a variable signal for turning on/off and dimming the ballasts. Each ballast stores the IDs of their assigned, designated remote control units so that only lighting control commands issued from the assigned remote control units will be acknowledged and responded to. This type of lighting control system provides two-way communication yet it has the disadvantage of <boundary-data type="line-number">10 </boundary-data>
+being vulnerable to the situation where a remote control is lost or inoperable. This type of lighting system requires an additional device and intervention for recovering control of the ballasts in the event the designated remote control unit(s) assigned to the ballasts is lost or inoperable.    </p>
+    <heading id="h-4">SUMMARY OF THE INVENTION</heading>
+    <p id="p-10" num="10">
+      <boundary-data type="line-number">
+        <confidence value="66">15</confidence>
+       </boundary-data>
+It is an object of the present teachings to provide a lighting control system providing a two-way master-slave oriented communication lighting control network.    </p>
+    <p id="p-11" num="11">It is another object of the present teachings to provide such a lighting control <boundary-data type="line-number">20 </boundary-data>
+network communicating via RF wireless links.    </p>
+    <p id="p-12" num="12">It is still another object of the present teachings to provide such a lighting control system that connect a plurality of local two-way communication lighting control networks to form a larger network.</p>
+    <p id="p-13" num="13">
+      <boundary-data type="line-number">
+        <confidence value="88">25</confidence>
+      </boundary-data>
+ In accordance with the present teachings, there is provided a method and apparatus for providing a lighting control network including a remote control unit having a RF signal transmitter and a RF receiver, and a plurality of lighting control units, each of the lighting control units having a RF signal transmitter, a RF receiver, and a lighting unit <part-num-ref name="lighting unit">
+        <confidence value="86">30</confidence>
+      </part-num-ref>
+ associated therewith, wherein the remote control unit and the plurality of lighting control <boundary-data type="header">
+        <confidence value="8">3</confidence>
+      </boundary-data>
+      <page-break num="4"/>
+      <boundary-data type="header">WO 2004/023849                                              PCT<confidence value="65">/I</confidence>
+B2003/003981      </boundary-data>
+units are configured in a master-slave oriented network, one of the plurality of lighting control units being configured as a master in the network and remaining lighting control units of the plurality of lighting units and the remote control units being configured as slaves in the network, and the plurality of lighting control units and the remote control <boundary-data type="line-number">5   </boundary-data>
+unit communicating bi-directionally with each other via RF wireless links. The network may also include sensors for detecting an environmental or system parameter. Multiple instances of the local lighting control network may be interfaced together to form a building-wide network.    </p>
+    <p id="p-14" num="14">
+      <boundary-data type="line-number">
+        <confidence value="66">10</confidence>
+               </boundary-data>
+The above and other objects, advantages, and benefits of the present invention will be understood by reference to following detailed description and appended sheets of drawings.    </p>
+    <heading id="h-5">
+      <confidence value="22222">BRIBF</confidence>
+ DESCRIPTION OF THE DRAWINGS    </heading>
+    <p id="p-15" num="15">
+      <boundary-data type="line-number">15         </boundary-data>
+The above set forth and other features of the present teachings are made more apparent in the ensuing Detailed Description of the Invention when read in conjunction with the attached Drawings, wherein:    </p>
+    <p id="p-16" num="16">FIG. <confidence value="2">1</confidence>
+A is an exemplary depiction of a lighting control network in accordance <boundary-data type="line-number">20   </boundary-data>
+with the present invention;    </p>
+    <p id="p-17" num="17">FIG. <confidence value="25">lB</confidence>
+ is an exemplary conceptual construct of the lighting control network of the present invention combining a general wireless communication protocol and a lighting-specific standard, in accordance with the present invention;    </p>
+    <p id="p-18" num="18">
+      <boundary-data type="line-number">
+        <confidence value="88">25</confidence>
+      </boundary-data>
+ FIG. 2 is an exemplary depiction of a ballast of the lighting control system of FIG.    </p>
+    <p id="p-19" num="19">
+      <confidence value="2">I</confidence>
+A, in accordance with the teachings of the present invention;    </p>
+    <p id="p-20" num="20">FIG. 3 is an exemplary depiction of a sensor of the lighting control system of FIG.</p>
+    <p id="p-21" num="21">30   <confidence value="5">1</confidence>
+A, in accordance with the teachings of the present invention; and <boundary-data type="header">
+        <confidence value="8">4</confidence>
+      </boundary-data>
+      <page-break num="5"/>
+      <boundary-data type="header">WO 2004/023849                                             PCT/<confidence value="15">IB</confidence>
+2003/003981      </boundary-data>
+FIG. 4 is an exemplary depiction of a remote control of the lighting system of FIG. <confidence value="2">I</confidence>
+A, in accordance with the teachings of the present invention; and <boundary-data type="line-number">5         </boundary-data>
+FIG. 5 is an exemplary depiction of the lighting control network of the present invention configured in a mesh topology.    </p>
+    <heading id="h-6">DETAILED DESCRIPTION OF THE <confidence value="8">I</confidence>
+NVENTION    </heading>
+    <p id="p-22" num="22">Referring to the figures, and in particular to FIG. <confidence value="2">1</confidence>
+A, there is depicted an <boundary-data type="line-number">10  </boundary-data>
+exemplary representation of a lighting control network <part-num-ref name="lighting control network">100</part-num-ref>
+ in accordance with the teachings of the present invention. Note that while lighting control network <part-num-ref name="present invention. Note that while lighting control network">100</part-num-ref>
+ illustrates an exemplary deployment of the lighting control network of the present invention, it should be appreciated by those skilled in the art that the lighting control system of the present invention may be implemented and adapted to a variety of <boundary-data type="line-number">15  </boundary-data>
+application environments.    </p>
+    <p id="p-23" num="23">
+      <confidence value="445">hIr</confidence>
+ an aspect of the present invention, the lighting control system includes a master-slave oriented two-way (i.e., bi-directional) RF wireless lighting control network.    </p>
+    <p id="p-24" num="24">Lighting control network 100 includes ballasts <part-num-ref name="includes ballasts">5,</part-num-ref>
+ <part-num-ref name="includes ballasts 5,">15,</part-num-ref>
+ <part-num-ref name="includes ballasts 5, 15,">25.</part-num-ref>
+ Each of the ballasts has a <boundary-data type="line-number">20  </boundary-data>
+lighting control unit and is associated with a lighting unit controlled thereby. As shown, ballast <part-num-ref name="lighting unit controlled thereby. As shown, ballast">5</part-num-ref>
+ is associated with lighting unit <part-num-ref name="is associated with lighting unit">10,</part-num-ref>
+ ballast <part-num-ref name="is associated with lighting unit 10, ballast">15</part-num-ref>
+ is associated with lighting unit <part-num-ref name="is associated with lighting unit">20,</part-num-ref>
+ and ballast <part-num-ref name="is associated with lighting unit 20, and ballast">25</part-num-ref>
+ is associated with lighting unit <part-num-ref name="is associated with lighting unit">30.</part-num-ref>
+ The lighting control network also includes at least one remote control unit for issuing commands for controlling the operation of the lighting units <part-num-ref name="lighting units">10,</part-num-ref>
+ <part-num-ref name="lighting units 10,">20,</part-num-ref>
+ <part-num-ref name="lighting units 10, 20,">30.</part-num-ref>
+ Exemplary lighting control network <part-num-ref name="lighting units 10, 20, 30. Exemplary lighting control network">100</part-num-ref>
+ <boundary-data type="line-number">25  </boundary-data>
+includes two remote control units <part-num-ref name="includes two remote control units">40</part-num-ref>
+ and <part-num-ref name="and">42.</part-num-ref>
+ More or less remote control units may be included. For example, lighting control network <part-num-ref name="and 42. More or less remote control units may be included. For example, lighting control network">100</part-num-ref>
+ may optionally have one or three (or more) remote control units associated therewith.    </p>
+    <p id="p-25" num="25">Lighting control network 100 has sensors <part-num-ref name="has sensors">35,</part-num-ref>
+ <part-num-ref name="has sensors 35,">37</part-num-ref>
+ for detecting, i.e., sensing and <part-num-ref name="sensing and">30</part-num-ref>
+   monitoring the status of an environmental and/or system parameter. The particular <boundary-data type="header">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+      <page-break num="6"/>
+      <boundary-data type="header">WO 2004/023849                                              PCT/<confidence value="5">I</confidence>
+B2003/003981      </boundary-data>
+parameter monitored may va<confidence value="8">r</confidence>
+y depending on the application of lighting control network <part-num-ref name="application of lighting control network">100.</part-num-ref>
+    </p>
+    <p id="p-26" num="26">The various ballasts, remote control units, and sensors of lighting control network <boundary-data type="line-number">5   </boundary-data>
+100 are associated with each other to form a communication and control network for controlling the operation of the lighting units <part-num-ref name="lighting units">10,</part-num-ref>
+ <part-num-ref name="lighting units 10,">20,</part-num-ref>
+ <part-num-ref name="lighting units 10, 20,">30</part-num-ref>
+ associated therewith. As mentioned above, the ballasts, remote control units, and sensors of lighting control network <part-num-ref name="ballasts, remote control units, and sensors of lighting control network">100</part-num-ref>
+ are configured in a master-slave oriented network wherein one of the ballasts of the lighting control network <part-num-ref name="lighting control network">100</part-num-ref>
+ are designated as a local control master.    </p>
+    <p id="p-27" num="27">
+      <boundary-data type="line-number">10   </boundary-data>
+Ballast 5 is the local control master for lighting control network <part-num-ref name="local control master for lighting control network">100.</part-num-ref>
+ The remaining ballasts, namely ballasts <part-num-ref name="remaining ballasts, namely ballasts">15,</part-num-ref>
+ 25; sensors <part-num-ref name="remaining ballasts, namely ballasts 15, 25; sensors">35,</part-num-ref>
+ 37; and remote control units <part-num-ref name="remaining ballasts, namely ballasts 15, 25; sensors 35, 37; and remote control units">40,</part-num-ref>
+ <part-num-ref name="remaining ballasts, namely ballasts 15, 25; sensors 35, 37; and remote control units 40,">42</part-num-ref>
+ are slave devices relative to the lighting control network <part-num-ref name="lighting control network">100</part-num-ref>
+ local control master, ballast <part-num-ref name="local control master, ballast">5.</part-num-ref>
+    </p>
+    <p id="p-28" num="28">In an aspect of the present invention, ballasts <part-num-ref name="present invention, ballasts">5,</part-num-ref>
+ <part-num-ref name="present invention, ballasts 5,">15,</part-num-ref>
+ 25; sensors <part-num-ref name="present invention, ballasts 5, 15, 25; sensors">35,</part-num-ref>
+ 37; and remote <boundary-data type="line-number">15   </boundary-data>
+control units <part-num-ref name="present invention, ballasts 5, 15, 25; sensors 35, 37; and remote control units">40,</part-num-ref>
+ <part-num-ref name="present invention, ballasts 5, 15, 25; sensors 35, 37; and remote control units 40,">42</part-num-ref>
+ communicate with each other via RF wireless links. The RF wireless links are represented in FIG. <confidence value="2">1</confidence>
+A as dashed lines. The double arrows on the dashed lines indicate that the communication between the devices of lighting control network <part-num-ref name="devices of lighting control network">100</part-num-ref>
+ communicate bi-directionally. That is, the ballasts, sensors, and remote control units may each transmit and receive RF signals.    </p>
+    <p id="p-29" num="29">
+      <boundary-data type="line-number">
+        <confidence value="88">20</confidence>
+      </boundary-data>
+ FIG. <confidence value="2">1</confidence>
+A also shows that local lighting control network 100 and other local lighting control networks may be wired or wirelessly connected to a central control master <part-num-ref name="central control master">200</part-num-ref>
+ to form a building-wide lighting control network (discussed in greater detail below). The building-wide network may thus comprise a two-tier hierarchy network of local control <boundary-data type="line-number">25   </boundary-data>
+masters and a central control master.    </p>
+    <p id="p-30" num="30">Referring to FIG. 2, an exemplary depiction of a ballast, including a lighting control unit, applicable for use in lighting control network <part-num-ref name="lighting control unit, applicable for use in lighting control network">100</part-num-ref>
+ is shown. Ballast <part-num-ref name="is shown. Ballast">5</part-num-ref>
+ of FIG. <confidence value="2">1</confidence>
+A is depicted as including a RF transceiver for transmitting and receiving RF <part-num-ref name="RF transceiver for transmitting and receiving RF">30</part-num-ref>
+   signals, a MCU (microcontroller), and a lamp driver for driving lighting unit <part-num-ref name="lamp driver for driving lighting unit">10.</part-num-ref>
+ The RF <boundary-data type="header">
+        <confidence value="8">6</confidence>
+      </boundary-data>
+      <page-break num="7"/>
+      <boundary-data type="header">WO 2004/023849                                              PCT/<confidence value="5">I</confidence>
+B2003<confidence value="5">/</confidence>
+003981      </boundary-data>
+transceiver receives and demodulates the R<confidence value="5">F</confidence>
+ signals and passes the demodulated signal to the MCU.     The MCU     has program  code encoded therein, including network communication  protocol code   and  application  code  for addressing network communication issues and lighting unit control issues, respectively.    </p>
+    <p id="p-31" num="31">
+      <boundary-data type="line-number">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+ In an aspect of the present invention, the lighting control unit aspects of the invention are housed in a common housing with other lighting unit ballast circuitry.    </p>
+    <p id="p-32" num="32">Thus, no additional wiring, either power or control, is required for implementing the ballasts disclosed herein.</p>
+    <p id="p-33" num="33">
+      <boundary-data type="line-number">
+        <confidence value="88">10</confidence>
+      </boundary-data>
+ FIG. <confidence value="4">1</confidence>
+B illustrates the conceptual network construction aspect of the present invention. In particular, FIG. <confidence value="4">1</confidence>
+B shows the combination of a general wireless communication protocol (e.g., Zigbee) and a lighting-specific standard (e.g., DAL). The master has direct communication links with the slave devices such as the slave remote- <boundary-data type="line-number">15   </boundary-data>
+control units, ballasts, and sensors. This direct (i.e., <confidence value="2222222222222">real/physical</confidence>
+) communication link is implemented via a RF wireless link and is represented by the solid line double-arrow between R<confidence value="5">F</confidence>
+ transceivers of the local control master, ballast <part-num-ref name="local control master, ballast">5,</part-num-ref>
+ and the slave device, ballast <part-num-ref name="slave device, ballast">15.</part-num-ref>
+    </p>
+    <p id="p-34" num="34">
+      <boundary-data type="line-number">20         </boundary-data>
+Regarding the network protocol for R<confidence value="5">F</confidence>
+ communication, it may be any R<confidence value="5">F</confidence>
+ wireless communication protocol, either proprietary or open-standard, for ensuring a master-slave oriented reliable two-way communication. Such a network protocol includes, but is not limited to Zigbee <confidence value="4">m</confidence>
+. Zigbee<confidence value="55">TM</confidence>
+ is a low cost, low power consumption, two-way, wireless communications standard proposed by the Zigbee Working group aimed initially at <boundary-data type="line-number">25   </boundary-data>
+automation, toys, and PC peripherals. The lighting-specific standard (e.g., DAL<confidence value="68">I)</confidence>
+ In order to apply a lighting control standard originally designed for wired <boundary-data type="header">
+        <confidence value="8">7</confidence>
+      </boundary-data>
+      <page-break num="8"/>
+      <boundary-data type="header">WO 2004/023849                                              PCT<confidence value="68">/I</confidence>
+B2003/003981      </boundary-data>
+connections, such as DALI<confidence value="5">,</confidence>
+ to wireless controls the Zigbee<confidence value="65">TM</confidence>
+ communication protocol is used to ensure a reliable RF link. It should be appreciated that the selection and use of DALI and Zigbee<confidence value="55">TM</confidence>
+ in the embodiments discussed herein are only examples, not limitations, of the lighting control and communication protocols, respectively, <boundary-data type="line-number">
+        <confidence value="5">5</confidence>
+       </boundary-data>
+encompassed by the present invention.    </p>
+    <p id="p-35" num="35">The RF transceiver receives and demodulates the RF signals and passes them to a microcontroller. The microcontroller is loaded with the embedded ballast software program, including the communications protocol module and the application module.</p>
+    <p id="p-36" num="36">
+      <boundary-data type="line-number">10 </boundary-data>
+The communications protocol module takes care of the network communication issues and the application module processes the A<confidence value="66">PI</confidence>
+ commands from communications protocol and controls the ballast with DALI commands.    </p>
+    <p id="p-37" num="37">FIG. 3 is an exemplary depiction of sensor <part-num-ref name="exemplary depiction of sensor">35</part-num-ref>
+ of lighting control network <part-num-ref name="of lighting control network">100.</part-num-ref>
+    </p>
+    <p id="p-38" num="38">
+      <boundary-data type="line-number">15 </boundary-data>
+Sensor 35 is shown as including a RF transceiver for transmitting and receiving R<confidence value="5">F</confidence>
+ signals, a MC<confidence value="5">U</confidence>
+ and a sensor module for detecting an environmental or system parameter.    </p>
+    <p id="p-39" num="39">The particular type of sensor(s) included with sensor 35 may depend on the application and goals of lighting control network <part-num-ref name="application and goals of lighting control network">100.</part-num-ref>
+ Thus, the sensor module of sensor <part-num-ref name="sensor module of sensor">35</part-num-ref>
+ may include, either alone or in combination, for example, an ambient light sensor, a motion <boundary-data type="line-number">20 </boundary-data>
+sensor, an occupancy sensor, and a temperature sensor. Other types of environmental and system sensors may be substituted for and/or included in combination with the foregoing sensor types.    </p>
+    <p id="p-40" num="40">FIG. 4 provides an exemplary depiction of remote control <part-num-ref name="exemplary depiction of remote control">40</part-num-ref>
+ of lighting control <part-num-ref name="of lighting control">25</part-num-ref>
+ network <part-num-ref name="network">100.</part-num-ref>
+ Remote control <part-num-ref name="network 100. Remote control">40</part-num-ref>
+ is shown as including a R<confidence value="5">F</confidence>
+ transceiver for transmitting <boundary-data type="header">
+        <confidence value="8">8</confidence>
+      </boundary-data>
+      <page-break num="9"/>
+      <boundary-data type="header">WO 2004/023849                                                 PCT<confidence value="65">/I</confidence>
+B2003/003981      </boundary-data>
+and receiving RF signals, a M<confidence value="5">C</confidence>
+U and an user interface. The user interface provides a means for a user to input commands for controlling the lighting units. The user interface preferably includes an interactive, graphical user interface that provides intuitive indications of the status of the controlled lighting units, system parameters, and input <boundary-data type="line-number">5   </boundary-data>
+commands (e.g., accepted/rejected). In another aspect, the user interface may include electro-mechanical buttons and keys. Also, the remote control unit may be implemented using a dedicated or general purpose computing device (e.g., a PC and a PDA).    </p>
+    <p id="p-41" num="41">In each room, see zone 1 and zone <part-num-ref name="and zone">2</part-num-ref>
+ of FIG. <confidence value="5">1</confidence>
+A, the ballast located therein is <boundary-data type="line-number">10   </boundary-data>
+controlled by one or more buttons (i.e., the user interface) located on the remote control unit associated with the ballast. Using the remote control unit, a user can remotely (i.e., not physically connected to) operate the lighting units, selectively group the lighting units in different configurations, set up various lighting scenes, etc.    </p>
+    <p id="p-42" num="42">
+      <boundary-data type="line-number">15         </boundary-data>
+Since the co<confidence value="88">mm</confidence>
+unication between the ballasts, sensors, and remote control units is bi-directional, the sensors can report data regarding the parameter(s) monitored, such as presence sensing, motion detection or ambient light detection, amount of power consumed, and other data to the local control master, ballast <part-num-ref name="local control master, ballast">5.</part-num-ref>
+ The local control master may then adjust the outputs of lighting units <part-num-ref name="outputs of lighting units">10,</part-num-ref>
+ <part-num-ref name="outputs of lighting units 10,">20,</part-num-ref>
+ <part-num-ref name="outputs of lighting units 10, 20,">30</part-num-ref>
+ outputs according to the reported <boundary-data type="line-number">20   </boundary-data>
+data and the lighting plan and other lighting objectives programmed into lighting control network <part-num-ref name="lighting plan and other lighting objectives programmed into lighting control network">100.</part-num-ref>
+ Local control master, ballast <part-num-ref name="lighting plan and other lighting objectives programmed into lighting control network 100. Local control master, ballast">5</part-num-ref>
+ acts as the network coordinator for lighting control network <part-num-ref name="network coordinator for lighting control network">100.</part-num-ref>
+    </p>
+    <boundary-data type="header">
+      <confidence value="8">9</confidence>
+    </boundary-data>
+    <boundary-data type="header">WO 2004/023849                                              PCT/<confidence value="5">I</confidence>
+B2003/003981    </boundary-data>
+    <p id="p-43" num="43">
+      <page-break num="10"/>
+Regarding operation of lighting control network 100, the local control master, ballast <part-num-ref name="local control master, ballast">
+        <confidence value="5">5</confidence>
+,      </part-num-ref>
+ establishes its network with a network ID. The other ballasts <part-num-ref name="other ballasts">15,</part-num-ref>
+ <part-num-ref name="other ballasts 15,">2<confidence value="5">5</confidence>
+,      </part-num-ref>
+ remote controls <part-num-ref name="other ballasts 15, 25, remote controls">40,</part-num-ref>
+ <part-num-ref name="other ballasts 15, 25, remote controls 40,">42,</part-num-ref>
+ and sensors <part-num-ref name="other ballasts 15, 25, remote controls 40, 42, and sensors">35,</part-num-ref>
+ <part-num-ref name="other ballasts 15, 25, remote controls 40, 42, and sensors 35,">37,</part-num-ref>
+ acting as network slaves, join lighting control network <part-num-ref name="other ballasts 15, 25, remote controls 40, 42, and sensors 35, 37, acting as network slaves, join lighting control network">100,</part-num-ref>
+ preferably using an enumeration algorithm. The enumeration algorithm <boundary-data type="line-number">5 </boundary-data>
+preferably utilizes an address pre-programmed into the ballasts <part-num-ref name="ballasts">15,</part-num-ref>
+ <part-num-ref name="ballasts 15,">25,</part-num-ref>
+ remote controls <part-num-ref name="ballasts 15, 25, remote controls">40,</part-num-ref>
+ <part-num-ref name="ballasts 15, 25, remote controls 40,">42,</part-num-ref>
+ and sensors <part-num-ref name="ballasts 15, 25, remote controls 40, 42, and sensors">35,</part-num-ref>
+ <part-num-ref name="ballasts 15, 25, remote controls 40, 42, and sensors 35,">37</part-num-ref>
+ that uniquely identifies them. During the enumeration procedure, the ballasts <part-num-ref name="ballasts">15,</part-num-ref>
+ <part-num-ref name="ballasts 15,">25,</part-num-ref>
+ remote controls <part-num-ref name="ballasts 15, 25, remote controls">40,</part-num-ref>
+ <part-num-ref name="ballasts 15, 25, remote controls 40,">42,</part-num-ref>
+ and sensors <part-num-ref name="ballasts 15, 25, remote controls 40, 42, and sensors">35,</part-num-ref>
+ <part-num-ref name="ballasts 15, 25, remote controls 40, 42, and sensors 35,">37</part-num-ref>
+ receive the network ID of the local control master, ballast <part-num-ref name="local control master, ballast">5.</part-num-ref>
+ The network ID of the local control master identifies the local network established by the local control master. Each of the <boundary-data type="line-number">10 </boundary-data>
+ballasts <part-num-ref name="ballasts">15,</part-num-ref>
+ <part-num-ref name="ballasts 15,">25,</part-num-ref>
+ remote controls <part-num-ref name="ballasts 15, 25, remote controls">40,</part-num-ref>
+ <part-num-ref name="ballasts 15, 25, remote controls 40,">42,</part-num-ref>
+ and sensors <part-num-ref name="ballasts 15, 25, remote controls 40, 42, and sensors">35,</part-num-ref>
+ <part-num-ref name="ballasts 15, 25, remote controls 40, 42, and sensors 35,">37</part-num-ref>
+ also preferably receives an allocated short address to identify themselves in subsequent communications with the local control master, ballast <part-num-ref name="local control master, ballast">
+        <confidence value="68">5.</confidence>
+      </part-num-ref>
+    </p>
+    <p id="p-44" num="44">A pairing algorithm is used to associate the keys/controls of the remote control <boundary-data type="line-number">15 </boundary-data>
+units with particular ballasts, according to the lighting configuration and layout needs.    </p>
+    <p id="p-45" num="45">For example, remote control unit 40 is "paired" with ballast <part-num-ref name="is &quot;paired&quot; with ballast">15</part-num-ref>
+ and remote control unit <part-num-ref name="and remote control unit">42</part-num-ref>
+ is <confidence value="5">"</confidence>
+paired" with ballast <part-num-ref name="is &quot;paired&quot; with ballast">25.</part-num-ref>
+ In this manner, the ballasts of the present invention are "virtually wired" (since communicating via RF wireless links) to the keys/controls of the remote control units. The pairing procedure is preferably accomplished by placing the <boundary-data type="line-number">20 </boundary-data>
+remote control units in a special programming mode, referred to herein as TEACH mode.    </p>
+    <p id="p-46" num="46">The local control master, ballast 5, records the pairing links between the keys/controls of the user interface of the remote control units and the ballasts paired together during the TEACH mode. The ballasts and remote control unit pairing <boundary-data type="line-number">25 </boundary-data>
+relationships may be stored in a table and a relational database in a memo<confidence value="8">r</confidence>
+y location of the MCU of the local control master.    </p>
+    <p id="p-47" num="47">The pairing procedure is shown in the following Table <part-num-ref name="following Table">1.</part-num-ref>
+    </p>
+    <p id="p-48" num="48">Buttons pressed on        Reaction of Master         Reaction of Ba<confidence value="55">ll</confidence>
+ast Remote-control unit <boundary-data type="header">
+        <confidence value="88">10</confidence>
+      </boundary-data>
+      <page-break num="11"/>
+      <boundary-data type="header">WO 2004/023849                                                 PCT<confidence value="68">/I</confidence>
+B2003/003981      </boundary-data>
+having two buttons Both for 2 sec or more      Enter-TEACH-mode           all ON Next/previous               Select active ballast      Active one OFF (address +1/-<confidence value="58">1)</confidence>
+ <confidence value="66">-L</confidence>
+eft/right button          Attach                     back ON Left/right for <part-num-ref name="sec or more      Enter-TEACH-mode           all ON Next/previous               Select active ballast      Active one OFF (address +1/-1) -Left/right button          Attach                     back ON Left/right for">2</part-num-ref>
+ sec or more  Detach                   back ON Both for <part-num-ref name="sec or more  Detach                   back ON Both for">2</part-num-ref>
+ sec or more      Return-to-NORMAL           all OFF and then ON again Table <part-num-ref name="sec or more      Return-to-NORMAL           all OFF and then ON again Table">1</part-num-ref>
+ As an example of an exempla<confidence value="8">r</confidence>
+y pairing algorithm in TEACH mode, the local control master first enters TEACH mode and sends a command to turn on all the <boundary-data type="line-number">
+        <confidence value="5">5</confidence>
+         </boundary-data>
+registered ballasts. The networked ballasts are cycled through using, for example, "Next" and "Previous" buttons on the remote control unit. Depending on the button/key pressed on the remote-control unit, either "Next" or "Previous", one of the networked ballasts is selected. The active, i.e., selected, ballast is turned of<confidence value="5">f</confidence>
+ to visually notify the user which ballast was selected. The selected ballast is then paired with a particular key of the <boundary-data type="line-number">10   </boundary-data>
+remote control unit. A message is sent to the master, for example, to attach or detach the ballast to the network. Pairing data is stored in the master in a table or database. The selected ballast is turned back on after the pairing is complete. The user may select additional ballasts to <confidence value="6">"</confidence>
+pair" to the remote control unit or return to the normal mode of lighting control operation.    </p>
+    <p id="p-49" num="49">
+      <boundary-data type="line-number">
+        <confidence value="88">15</confidence>
+      </boundary-data>
+ In one aspect of the operation of light control network <part-num-ref name="operation of light control network">100,</part-num-ref>
+ the slave devices communicate with the local control master using R<confidence value="5">F</confidence>
+ signals generated therein. The R<confidence value="5">F</confidence>
+ signals include the network ID and the slave's ID. When the user issues a command by, <part-num-ref name="command by,">20</part-num-ref>
+   for example, pressing a key on remote control unit <part-num-ref name="key on remote control unit">40</part-num-ref>
+ a specific data packet related to the <boundary-data type="header">
+        <confidence value="88">11</confidence>
+      </boundary-data>
+      <page-break num="12"/>
+      <boundary-data type="header">WO 2004/023849                                              PCT/<confidence value="5">I</confidence>
+B2003/003981      </boundary-data>
+pressed key (e.g., a command to turn on lighting unit <part-num-ref name="command to turn on lighting unit">20)</part-num-ref>
+ in the form of a RF signal is transmitted to the local control master, ballast <part-num-ref name="local control master, ballast">5.</part-num-ref>
+ Upon receipt of the RF signal from remote control unit <part-num-ref name="RF signal from remote control unit">40,</part-num-ref>
+ local control master, ballast <part-num-ref name="RF signal from remote control unit 40, local control master, ballast">5</part-num-ref>
+ retrieves the pairing data for remote control unit <part-num-ref name="pairing data for remote control unit">40</part-num-ref>
+ and ballast <part-num-ref name="and ballast">15</part-num-ref>
+ associated with the pressed key from its look-up table and <boundary-data type="line-number">5   </boundary-data>
+routes the data packet via RF signal to destination ballast <part-num-ref name="data packet via RF signal to destination ballast">15.</part-num-ref>
+    </p>
+    <p id="p-50" num="50">Destination ballast 15 receives the packet via RF signal, demodulates, and decodes the signal. Lighting unit <part-num-ref name="signal. Lighting unit">20</part-num-ref>
+ is operated in accordance to the issued command. In this example, lighting unit <part-num-ref name="issued command. In this example, lighting unit">20</part-num-ref>
+ is commanded to turn on.    </p>
+    <p id="p-51" num="51">
+      <boundary-data type="line-number">
+        <confidence value="88">10</confidence>
+      </boundary-data>
+ According to another aspect of the present invention, the local control master sends out beacons or polling messages at a predetermined interval to maintain the health of light control network <part-num-ref name="health of light control network">100.</part-num-ref>
+ In this manner the network slave devices are periodically informed of the local control master's status. The local control master status may include <boundary-data type="line-number">15   </boundary-data>
+whether the local control master is allowing new  devices to join the network.    </p>
+    <p id="p-52" num="52">Additionally, the local control master can monitor the status of the slave devices on the network.</p>
+    <p id="p-53" num="53">In yet another aspect of the present invention, lighting control network <part-num-ref name="present invention, lighting control network">100</part-num-ref>
+ can be <boundary-data type="line-number">20   </boundary-data>
+maintained in the instance of a power outage and/or local control master, ballast <part-num-ref name="power outage and/or local control master, ballast">5,</part-num-ref>
+ malfunctions or is otherwise rendered inoperable for coordinating the functions of network <part-num-ref name="functions of network">100.</part-num-ref>
+ Accordingly, at least one of the slave ballasts (for example, ballast <part-num-ref name="slave ballasts (for example, ballast">15)</part-num-ref>
+ may be designated as a back-up local control master in the event that the local control master, ballast <part-num-ref name="local control master, ballast">5,</part-num-ref>
+ fails. In the event of such failure, back-up local control master ballast <part-num-ref name="event of such failure, back-up local control master ballast">15</part-num-ref>
+ <boundary-data type="line-number">25   </boundary-data>
+becomes the primary local control master. In another aspect hereof, all of the devices not designated as the master may act as a back-up master and be randomly selected as the master upon an emergency or failure of the primary local control master.    </p>
+    <p id="p-54" num="54">
+      <confidence value="88">30</confidence>
+ <boundary-data type="header">
+        <confidence value="88">12</confidence>
+      </boundary-data>
+      <page-break num="13"/>
+      <boundary-data type="header">WO 2004/023849                                              PCT/<confidence value="5">I</confidence>
+B2003/003981      </boundary-data>
+The designation of a primary, and a secondary, etc., back-up local control masters can be implemented according to a variety of network reconfiguration schemes. The particular algorithm used for converting a ballast into the new master may vary depending <boundary-data type="line-number">5 </boundary-data>
+on the application and lighting control protocol used. It is noted however, that network <part-num-ref name="application and lighting control protocol used. It is noted however, that network">100</part-num-ref>
+ reconfigures as a master-slave oriented two-way communication network such that the pairing data is maintained by at least one device designated as a local control master.    </p>
+    <p id="p-55" num="55">Accordingly, lighting control network 100 of the present invention provides <boundary-data type="line-number">10 </boundary-data>
+increased lighting system layout flexibility; reliable two-way communication, including feedback data from the ballast, such as power consumption or diagnostic information, affording improved lighting and power management; is not susceptible to the missing remote control unit situation since pairing link data is consolidated in the local control master. As discussed above, in the instance the master fails, there is a back-up local <boundary-data type="line-number">15 </boundary-data>
+control master to take over the coordination and control functionality for the network.    </p>
+    <p id="p-56" num="56">In an aspect of the present invention, the existence of a local control master facilitates forming a building-wide lighting control network. The local control master can transmit data, communicate, local network data concerning the local network to a central <boundary-data type="line-number">20 </boundary-data>
+master for the entire building to achieve "building automation" or a "building management<confidence value="6">'</confidence>
+ network.    </p>
+    <p id="p-57" num="57">This building-wide network connects all different kinds of the building management systems, such as lighting, heating, security and elevator systems, and so on <boundary-data type="line-number">25 </boundary-data>
+together and forms communication pathways to the building management center, which can be a PC or other centralized control equipment such as central control master <part-num-ref name="PC or other centralized control equipment such as central control master">200</part-num-ref>
+ of FIG. <confidence value="5">1</confidence>
+A. The devices included in this network include ballasts, remote control units, occupancy sensors, motion detectors, light sensors, temperature sensors, humidity sensors, window blind controllers, circuit breaker panel boxes, and any other type of <part-num-ref name="devices included in this network include ballasts, remote control units, occupancy sensors, motion detectors, light sensors, temperature sensors, humidity sensors, window blind controllers, circuit breaker panel boxes, and any other type of">30</part-num-ref>
+ sensors or devices that are may be used for the building control systems mentioned above.    </p>
+    <boundary-data type="header">
+      <confidence value="88">13</confidence>
+    </boundary-data>
+    <boundary-data type="header">WO 2004/023849                                              PCT<confidence value="5">/</confidence>
+IB2003/003981    </boundary-data>
+    <p id="p-58" num="58">
+      <page-break num="14"/>
+In an aspect hereof, the devices in the network communicate in different ways depending on the communication protocol used. For instance, the communication <boundary-data type="line-number">
+        <confidence value="5">5</confidence>
+         </boundary-data>
+protocol used may be a hierarchical net or a flat mesh.    </p>
+    <p id="p-59" num="59">In a hierarchical network structure, the central control master <part-num-ref name="central control master">200</part-num-ref>
+ is the top master of the network. In each room, there is a local master that can reside in the ballast or any other appropriate devices in the local network. The ballast is suitable for the system <boundary-data type="line-number">10   </boundary-data>
+where the local master needs to be mains-powered. The local masters of the building network can talk to one each through communication links established therebetween.    </p>
+    <p id="p-60" num="60">Network data and status is reported to the central control master by the local masters (e.g., ballast <part-num-ref name="ballast">5)</part-num-ref>
+ and network commands and data can be sent to central control <part-num-ref name="and network commands and data can be sent to central control">200</part-num-ref>
+ via the same communication pathways. Local control masters control and coordinate the operations of <boundary-data type="line-number">15  </boundary-data>
+the various devices in the local networks. The devices can talk to another through physical/virtual links after initialization or configuration. The communication between any two slave-devices can go through the local master.    </p>
+    <p id="p-61" num="61">In a mesh network structure a shown in FIG. 5, central control master <part-num-ref name="shown in FIG. 5, central control master">200</part-num-ref>
+ is the <boundary-data type="line-number">20   </boundary-data>
+master of the network. All the other devices can be the slaves s<confidence value="2">1</confidence>
+, s2,..., s6. All of the slave devices, sl-s6, can communicate with one another. A command issued by the master will f<confidence value="8">i</confidence>
+nd the best route to get to the destination slave device by using other slave devices as routing or repeating devices. For example, a command destined for slave s6 may take route CM-s<confidence value="4">1</confidence>
+-s3-s6 or route CM-s2-s4-s6, depending on network traffic and <boundary-data type="line-number">25   </boundary-data>
+other considerations.    </p>
+    <p id="p-62" num="62">It should be appreciated by those skilled in the art that the system environment, i.e., ballasts, remote control units, sensors, a building, a room, a lighting zone, and other <boundary-data type="line-number">
+        <confidence value="6">-</confidence>
+       </boundary-data>
+aspects of the teachings herein are but examples of implementations suitable for the <part-num-ref name="">30</part-num-ref>
+  lighting control system network of the present teachings, and thus do not limit the scope <boundary-data type="header">
+        <confidence value="88">14</confidence>
+      </boundary-data>
+      <page-break num="15"/>
+      <boundary-data type="header">WO 2004/023849                                              PCT<confidence value="65">/I</confidence>
+B2003<confidence value="5">/</confidence>
+003981      </boundary-data>
+or variety of applications that the present invention may be suitably implemented. Thus, it should be understood that the foregoing description is only illustrative of a present implementation of the teachings herein. Various alternatives and modification may be devised by those skilled in the art without departing from the invention. Accordingly, the <boundary-data type="line-number">5   </boundary-data>
+present invention is intended to embrace all such alter<confidence value="8">n</confidence>
+atives, modifications, and variances which fall within the scope of the appended claims.    </p>
+    <boundary-data type="header">
+      <confidence value="88">15</confidence>
+    </boundary-data>
+  </description>
+</us-patent-application>
+

applicant/11293330.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>11293330</doc-number>
+        <date>2008-09-16</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">
+      <confidence value="888">-2-</confidence>
+ In The Specification:    </p>
+    <p id="p-2" num="2">Please amend the paragraph beginning on page <part-num-ref name="paragraph beginning on page">90,</part-num-ref>
+ line <part-num-ref name="paragraph beginning on page 90, line">3,</part-num-ref>
+ as follows:    </p>
+    <p id="p-3" num="3">--It can, however, be a problem for an enterprise to verify identity this way, especially if the enterprise has to do this many times for many applying persons. While it is true that the enterprise may limit the amounts to a few cents at the most, if the number of transfers is large, say on the order of a million a month, the overall cost may be considerable. The enterprise typically does not get the money back.-- Please amend the paragraph beginning on page <part-num-ref name="paragraph beginning on page">92,</part-num-ref>
+ line <part-num-ref name="paragraph beginning on page 92, line">19,</part-num-ref>
+ as follows:    </p>
+    <p id="p-4" num="4">--In the different embodiments described above, transfers and account opening [[a]] and closing has been described as occurring automatically in response to user configuration. However, in some cases, user alerts may be provided, recommendations made, and user decisions solicited in the process, rather than strictly automated transfer and implementation.-- </p>
+  </description>
+</us-patent-application>
+

applicant/11391653.xml

@@ -0,0 +1,590 @@
+<?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>11391653</doc-number>
+        <date>2006-03-28</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <heading id="h-1">MONITOR MANAGEMENT THAT ENABLES ENHANCED DATA COLLECTION</heading>
+    <heading id="h-2">FIELD OF THE INVENTION</heading>
+    <p id="p-1" num="1">
+      <confidence value="5">[</confidence>
+0001<confidence value="5">]</confidence>
+ The invention relates generally to managing monitors, and more particularly, to a solution for generating a monitor having enhanced data collection capabilities.    </p>
+    <heading id="h-3">BACKGROUND OF THE INVENTION</heading>
+    <p id="p-2" num="2">[0002] An event correlation engine processes events originated from one or more sources in a network to establish relationships across the events, and possibly point to a root cause of an event that a system administrator otherwise may not notice. The success of the event correlation engine is largely dictated by an availability of sufficient data to arrive at an accurate conclusion.</p>
+    <p id="p-3" num="3">To date, the event correlation engine receives event data from various sensors located at various computing systems (e.g., computing devices, routers, etc.) in the network. Each sensor detects a particular type of event, and collects and forwards a certain type of data on the event to the event correlation engine. The event correlation engine then processes the event data using a set of correlation rules. This arrangement is targeted at automating the resolution of known problems, but is <confidence value="22222222">lirnited</confidence>
+ in its ability to explore unknown existing relationships.    </p>
+    <p id="p-4" num="4">
+      <confidence value="5">[</confidence>
+0003<confidence value="5">]</confidence>
+ In view of the foregoing, a need exists to overcome one or more of the deficiencies in the related art.    </p>
+    <heading id="h-4">BRIEF SUMMARY OF THE INVENTION</heading>
+    <p id="p-5" num="5">
+      <confidence value="5">[</confidence>
+0004<confidence value="5">]</confidence>
+ The invention provides a solution for managing a monitor that includes enhanced data collection capabilities. A set of triggers, each of which is capable of monit<confidence value="8">o</confidence>
+ring a co<confidence value="8">m</confidence>
+put<confidence value="8">i</confidence>
+ng <boundary-data type="header">RSW920050212US1                        1</boundary-data>
+      <page-break num="2"/>
+environment for a condition, and a set of collectors each of which is capable of collecting environment information for the computing environment are obtained. A set of links that define a relationship between a trigger and a collector can be defined by a user and used to generate the monitor. In this manner, the monitor is configurable to collect any combination of data about the computing environment in response to the presence/occurrence of the condition. The collected data can then be used to provide an improved analysis of environment data to identify any unknown existing relationships, root causes of problems, and/or the like.    </p>
+    <p id="p-6" num="6">
+      <confidence value="5">[</confidence>
+0005<confidence value="5">]</confidence>
+ A first aspect of the invention provides a method of managing a monitor, the method comprising: obtaining a set of triggers, each trigger being capable of monitoring a computing environment for a condition; obtaining a set of collectors, each collector being capable of collecting environment information for the computing environment; obtaining a set of links, each link defining a relationship between a trigger in the set of triggers and a collector in the set of collectors; and generating a monitor based on the set of links.    </p>
+    <p id="p-7" num="7">
+      <confidence value="5">[</confidence>
+0006<confidence value="5">]</confidence>
+ A second aspect of the invention provides a system for managing a monitor, the system comprising: a system for obtaining a set of triggers, each trigger being capable of monitoring a computing environment for a condition; a system for obtaining a set of collectors, each collector being capable of collecting environment information for the computing environment; a system for obtaining a set of links, each link defining a relationship between a trigger in the set of triggers and a collector in the set of collectors; and a system for generating a monitor based on the set of links.    </p>
+    <p id="p-8" num="8">
+      <confidence value="5">[</confidence>
+0007<confidence value="5">]</confidence>
+ A third aspect of the invention provides a program product stored on a computer- readable medium, which when executed, enables a computer infrastructure to manage a monitor, the program product comprising <confidence value="8">c</confidence>
+omputer <confidence value="7877">prog</confidence>
+ram cod<confidence value="8">e</confidence>
+ <confidence value="85">fo</confidence>
+r enabling the c<confidence value="8">o</confidence>
+mputer infrast<confidence value="8">r</confidence>
+uctur<confidence value="8">e</confidence>
+ <boundary-data type="header">RSW920050212US1                        2</boundary-data>
+      <page-break num="3"/>
+to: obtain a set of triggers, each trigger being capable of monitoring a computing environment for a condition; obtain a set of collectors, each collector being capable of collecting environment information for the computing environment; obtain a set of links, each link defining a relationship between a trigger in the set of triggers and a collector in the set of collectors; and generate a monitor based on the set of links.    </p>
+    <p id="p-9" num="9">
+      <confidence value="5">[</confidence>
+0008<confidence value="4">]</confidence>
+ A fourth aspect of the invention provides a method of generating a system for managing a monitor, the method comprising: providing a computer infrastructure operable to: obtain a set of triggers, each trigger being capable of monitoring a computing environment for a condition;    </p>
+    <p id="p-10" num="10">obtain a set of collectors, each collector being capable of collecting environment information for the computing environment; obtain a set of links, each link defining a relationship between a trigger in the set of triggers and a collector in the set of collectors; and generate a monitor based on the set of links.</p>
+    <p id="p-11" num="11">[0009] A fifth aspect of the invention provides a business method for managing a set of monitors, the business method comprising managing a computer infrastructure that performs the process described herein; and receiving payment based on the managing.</p>
+    <p id="p-12" num="12">[0010] The illustrative aspects of the present invention are designed to solve one or more of the problems herein described <confidence value="222222">and/or</confidence>
+ one or more other problems not discussed.    </p>
+    <heading id="h-5">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
+    <p id="p-13" num="13">
+      <confidence value="5">[</confidence>
+0011] These and other features of the invention will be more readily understood from the following detailed description of the various aspects of the invention taken in conjunction with the accompanying drawings that depict various embodiments of the invention.    </p>
+    <boundary-data type="header">
+      <confidence value="88">RS</confidence>
+W920050212US1                         3    </boundary-data>
+    <p id="p-14" num="14">
+      <page-break num="4"/>
+[0012] FIG. 1 shows an illustrative environment for managing a set of monitors according to an embodiment of the invention.    </p>
+    <p id="p-15" num="15">[0013<confidence value="5">]</confidence>
+ FIG. 2 shows an illustrative data flow diagram for the environment of FIG. 1 according to an embodiment of the invention.    </p>
+    <p id="p-16" num="16">
+      <confidence value="5">[</confidence>
+0014<confidence value="5">]</confidence>
+ FIG. 3 shows an illustrative monitor definition interface according to an embodiment of the invention.    </p>
+    <p id="p-17" num="17">
+      <confidence value="5">[</confidence>
+0015<confidence value="5">]</confidence>
+ FIG. 4 shows a data flow diagram for an illustrative monitor after implementation on a computing environment according to an embodiment of the invention.    </p>
+    <p id="p-18" num="18">[0016<confidence value="5">]</confidence>
+ It is noted that the drawings are not to scale. The drawings are intended to depict only typical aspects of the invention, and therefore should not be considered as limiting the scope of the invention. In the drawings, like numbering represents like elements between the drawings.    </p>
+    <heading id="h-6">DETAILED DESCRIPTION OF THE <confidence value="8">I</confidence>
+NVENTION    </heading>
+    <p id="p-19" num="19">[0017] As indicated above, the invention provides a solution for managing a monitor that includes enhanced data collection capabilities. A set of triggers, each of which is capable of monitoring a computing environment for a condition, and a set of collectors each of which is capable of collecting environment information for the computing environment are obtained. A set of links that define a relationship between a trigger and a collector can be defined by a user and used to generate the monitor. In this manner, the monitor is configurable to collect any combination of data about the computing environment in response to the presence/occurrence of the condition. The collected data can then be used to provide an improved analysis of environment data to identify any unknown existing relationships, root causes of problems, and/or <boundary-data type="header">RSW920050212US<confidence value="4">1</confidence>
+                        <confidence value="8">4</confidence>
+      </boundary-data>
+      <page-break num="5"/>
+the like. As used herein, unless otherwise noted, the term "set" means one or more (i.e., at least one) and the phrase "any solution" means any now known or later developed solution.    </p>
+    <p id="p-20" num="20">
+      <confidence value="5">[</confidence>
+0018<confidence value="5">]</confidence>
+ Turning to the drawings, FIG. <confidence value="4">1</confidence>
+ shows an illustrative environment <part-num-ref name="illustrative environment">10</part-num-ref>
+ for managing a set of monitors <part-num-ref name="set of monitors">54</part-num-ref>
+ according to an embodiment of the invention. To this extent, environment <part-num-ref name="invention. To this extent, environment">10</part-num-ref>
+ includes a computer infrastructure <part-num-ref name="computer infrastructure">12</part-num-ref>
+ that can perform the process described herein in order to manage the set of monitors <part-num-ref name="set of monitors">54.</part-num-ref>
+ In particular, computer infrastructure <part-num-ref name="set of monitors 54. In particular, computer infrastructure">12</part-num-ref>
+ is shown including a computing device <part-num-ref name="computing device">14</part-num-ref>
+ that comprises a monitor system <part-num-ref name="monitor system">30,</part-num-ref>
+ which makes computing device <part-num-ref name="monitor system 30, which makes computing device">14</part-num-ref>
+ operable to manage monitor(s) <part-num-ref name="operable to manage monitor(s)">54</part-num-ref>
+ by performing the process described herein. To this extent, monitor system <part-num-ref name="process described herein. To this extent, monitor system">30</part-num-ref>
+ enables computing device <part-num-ref name="enables computing device">14</part-num-ref>
+ to generate monitor <part-num-ref name="to generate monitor">54</part-num-ref>
+ based on link data <part-num-ref name="based on link data">60</part-num-ref>
+ that defines a set of links between a set of triggers <part-num-ref name="set of triggers">50</part-num-ref>
+ and a set of collectors <part-num-ref name="set of collectors">52.</part-num-ref>
+    </p>
+    <p id="p-21" num="21">[0019<confidence value="5">]</confidence>
+ Computing device 14 is shown including a processor <part-num-ref name="processor">20,</part-num-ref>
+ a memory 22A, an input/output (<confidence value="665">I/O</confidence>
+) interface <part-num-ref name="input/output (I/O) interface">24,</part-num-ref>
+ and a bus <part-num-ref name="bus">26.</part-num-ref>
+ Further, computing device <part-num-ref name="bus 26. Further, computing device">14</part-num-ref>
+ is shown in communication with an external <confidence value="665">I/O</confidence>
+ device/resource <part-num-ref name="external I/O device/resource">28</part-num-ref>
+ and a storage system 22B. As is known in the art, in general, processor <part-num-ref name="art, in general, processor">20</part-num-ref>
+ executes computer program code, such as monitor system <part-num-ref name="executes computer program code, such as monitor system">30,</part-num-ref>
+ which is stored in memory 22A and/or storage system 22B. While executing computer program code, processor <part-num-ref name="executes computer program code, such as monitor system 30, which is stored in memory 22A and/or storage system 22B. While executing computer program code, processor">20</part-num-ref>
+ can read and/or write data, such as link data <part-num-ref name="can read and/or write data, such as link data">60,</part-num-ref>
+ to/from memory 22A, storage system 22B, and/or I/O interface <part-num-ref name="can read and/or write data, such as link data 60, to/from memory 22A, storage system 22B, and/or I/O interface">24.</part-num-ref>
+ Bus <part-num-ref name="can read and/or write data, such as link data 60, to/from memory 22A, storage system 22B, and/or I/O interface 24. Bus">26</part-num-ref>
+ provides a communications link between each of the components in computing device <part-num-ref name="components in computing device">14.</part-num-ref>
+ <confidence value="665">I/O</confidence>
+ device <part-num-ref name="components in computing device 14. I/O device">28</part-num-ref>
+ can comprise any device that transfers information between a user <part-num-ref name="user">16</part-num-ref>
+ and computing device <part-num-ref name="and computing device">14.</part-num-ref>
+ To this extent, <confidence value="685">I/O</confidence>
+ device <part-num-ref name="and computing device 14. To this extent, I/O device">28</part-num-ref>
+ can comprise a user <confidence value="254">I/O</confidence>
+ device to enable an individual user <part-num-ref name="individual user">16</part-num-ref>
+ to interact with computing device <part-num-ref name="to interact with computing device">14</part-num-ref>
+ and/or a communications device to enable a system user <part-num-ref name="system user">16</part-num-ref>
+ to communicate with computing device <part-num-ref name="to communicate with computing device">14</part-num-ref>
+ using any type of communications link.    </p>
+    <boundary-data type="header">RSW920050212US1                         5</boundary-data>
+    <p id="p-22" num="22">
+      <page-break num="6"/>
+      <confidence value="5">[</confidence>
+0020<confidence value="6">]</confidence>
+ <confidence value="6">I</confidence>
+n any event, computing device 14 can comprise any general purpose computing article of manufacture capable of executing computer program code installed thereon (e.g., a personal computer, server, handheld device, etc.). However, it is understood that computing device <part-num-ref name="personal computer, server, handheld device, etc.). However, it is understood that computing device">14</part-num-ref>
+ and monitor system <part-num-ref name="and monitor system">30</part-num-ref>
+ are only representative of various possible equivalent computing devices that may perform the process described herein. To this extent, in other embodiments, the functionality provided by computing device <part-num-ref name="functionality provided by computing device">14</part-num-ref>
+ and monitor system <part-num-ref name="and monitor system">30</part-num-ref>
+ can be implemented by a computing article of manufacture that includes any combination of general and/or specific purpose hardware and/or computer program code. In each embodiment, the program code and hardware can be created using standard programming and engineering techniques, respectively.    </p>
+    <p id="p-23" num="23">
+      <confidence value="5">[</confidence>
+0021<confidence value="5">]</confidence>
+ Similarly, computer infrastructure 12 is only illustrative of various types of computer infrastructures for implementing the invention. For example, in one embodiment, computer infrastructure <part-num-ref name="invention. For example, in one embodiment, computer infrastructure">12</part-num-ref>
+ comprises two or more computing devices (e.g., a server cluster) that communicate over any type of communications link, such as a network, a shared memory, or the like, to perform the process described herein. Further, while performing the process described herein, one or more computing devices in computer infrastructure <part-num-ref name="process described herein, one or more computing devices in computer infrastructure">12</part-num-ref>
+ can communicate with one or more other computing devices external to computer infrastructure <part-num-ref name="can communicate with one or more other computing devices external to computer infrastructure">12</part-num-ref>
+ using any type of communications link. In either case, the communications link can comprise any combination of various types of wired and/or wireless links; comprise any combination of one or more types of networks (e.g., the Internet, a wide area network, a local area network, a virtual private network, etc.); and/or utilize any combination of various types of transmission techniques and protocols.    </p>
+    <p id="p-24" num="24">
+      <confidence value="5">[</confidence>
+0022<confidence value="5">]</confidence>
+ As discussed herein, monitor system 30 enables computer infrastructure <part-num-ref name="enables computer infrastructure">12</part-num-ref>
+ to manage a set of monitors <part-num-ref name="set of monitors">54.</part-num-ref>
+ To this extent, monitor system <part-num-ref name="set of monitors 54. To this extent, monitor system">30</part-num-ref>
+ is shown including an interface component <part-num-ref name="interface component">
+        <confidence value="666">32,</confidence>
+      </part-num-ref>
+ <confidence value="6">a</confidence>
+ trigger component <part-num-ref name="trigger component">
+        <confidence value="686">34,</confidence>
+      </part-num-ref>
+ <confidence value="6">a</confidence>
+ <confidence value="88">co</confidence>
+lle<confidence value="8">c</confidence>
+ti<confidence value="8">o</confidence>
+n component <part-num-ref name="collection component">
+        <confidence value="666">36,</confidence>
+      </part-num-ref>
+ <confidence value="6">a</confidence>
+ <confidence value="777886">deploy</confidence>
+ <confidence value="2">e</confidence>
+ <confidence value="86">nt</confidence>
+ component <part-num-ref name="deploy e nt component">
+        <confidence value="666">38,</confidence>
+      </part-num-ref>
+ <confidence value="886">and</confidence>
+ <confidence value="8">a</confidence>
+ <boundary-data type="header">RSW920050212US1                         6</boundary-data>
+      <page-break num="7"/>
+correlation component <part-num-ref name="correlation component">40.</part-num-ref>
+ Operation of each of these components is discussed further herein.    </p>
+    <p id="p-25" num="25">However, it is understood that some of the various systems/components shown in FIG. 1 can be implemented independently, combined, and/or stored in memory for one or more separate computing devices that are included in computer infrastructure <part-num-ref name="can be implemented independently, combined, and/or stored in memory for one or more separate computing devices that are included in computer infrastructure">12.</part-num-ref>
+ Further, it is understood that some of the systems/components and/or functionality discussed herein may not be implemented, or additional systems/components and/or functionality may be included as part of computer infrastructure <part-num-ref name="systems/components and/or functionality discussed herein may not be implemented, or additional systems/components and/or functionality may be included as part of computer infrastructure">12.</part-num-ref>
+    </p>
+    <p id="p-26" num="26">[0023] Regardless, the invention provides a solution for managing monitor(s) <part-num-ref name="solution for managing monitor(s)">54.</part-num-ref>
+ In general, monitor system <part-num-ref name="solution for managing monitor(s) 54. In general, monitor system">30</part-num-ref>
+ can generate monitor(s) <part-num-ref name="can generate monitor(s)">54</part-num-ref>
+ using trigger(s) <part-num-ref name="using trigger(s)">50</part-num-ref>
+ and collector(s) <part-num-ref name="and collector(s)">52.</part-num-ref>
+ To this extent, monitor system <part-num-ref name="and collector(s) 52. To this extent, monitor system">30</part-num-ref>
+ enables user <part-num-ref name="enables user">16</part-num-ref>
+ to link/associate a trigger <part-num-ref name="trigger">50</part-num-ref>
+ with one or more collectors <part-num-ref name="with one or more collectors">52.</part-num-ref>
+ Each trigger <part-num-ref name="with one or more collectors 52. Each trigger">50</part-num-ref>
+ can comprise a program object or the like that is capable of monitoring a computing environment <part-num-ref name="computing environment">18</part-num-ref>
+ for the presence/occurrence of a condition. The condition can comprise any type of situation on computing environment <part-num-ref name="condition can comprise any type of situation on computing environment">18.</part-num-ref>
+ For example, the condition can comprise an availability/usage of a particular resource (e.g., processing memory, and/or the like) of computing environment <part-num-ref name="like) of computing environment">18</part-num-ref>
+ going below/above a predefined range/threshold, an occurrence of a particular type of interrupt, a status/transition of a process/application, and/or the like.    </p>
+    <p id="p-27" num="27">
+      <confidence value="5">[</confidence>
+0024<confidence value="5">]</confidence>
+ Likewise, each collector 52 can comprise a program object or the like that is capable of collecting a particular type of environment information for computing environment <part-num-ref name="particular type of environment information for computing environment">18.</part-num-ref>
+ The environment information can comprise any type of information on one or more resources of computing environment <part-num-ref name="environment information can comprise any type of information on one or more resources of computing environment">18.</part-num-ref>
+ For example, the environment information can comprise a list of applications/processes executing in computing environment <part-num-ref name="list of applications/processes executing in computing environment">18,</part-num-ref>
+ amount(s) of resource(s) being <confidence value="6222">used</confidence>
+ <confidence value="2">a</confidence>
+ current <confidence value="2222222">statuso</confidence>
+ <confidence value="2">a</confidence>
+  <confidence value="22222222222222222">prcs/apprlicaton,</confidence>
+ <confidence value="222222">and/or</confidence>
+ the <confidence value="2222">like</confidence>
+ <confidence value="22222222">Regrdlss</confidence>
+ <confidence value="2222">each</confidence>
+ <confidence value="2">.</confidence>
+ <confidence value="22222">trige</confidence>
+ <confidence value="224">50A</confidence>
+ <confidence value="2222">RSW9</confidence>
+ <part-num-ref name="like Regrdlss each . trige 50A RSW9">
+        <confidence value="22">20</confidence>
+      </part-num-ref>
+ <confidence value="222222252">050212LU1</confidence>
+         <confidence value="444">jJJ</confidence>
+       <part-num-ref name="050212LU1         jJJ">
+        <confidence value="55">1,</confidence>
+      </part-num-ref>
+ <confidence value="62">a7</confidence>
+ <confidence value="1">W</confidence>
+  <confidence value="4411">uiL.</confidence>
+ <confidence value="55115">11AL.</confidence>
+ <confidence value="1">I</confidence>
+ <confidence value="1141111115">&lt;6aiui1.J,</confidence>
+ <confidence value="141">LaL</confidence>
+ <confidence value="14">tI</confidence>
+  <confidence value="11">.J</confidence>
+ <confidence value="5554">aiiU</confidence>
+ <boundary-data type="header">RSW920050212US 1                        7</boundary-data>
+      <page-break num="8"/>
+collector <part-num-ref name="050212LU1         jJJ       1, a7 W  uiL. 11AL. I &lt;6aiui1.J, LaL tI  .J aiiU collector">52</part-num-ref>
+ can comprise any type of compiled, interpreted, and/or comparable type of program object. For example, the program object can comprise an executable program, an object file, source code for generating a compiled program object, an interpreted program, and/or the like.    </p>
+    <p id="p-28" num="28">[0025<confidence value="5">]</confidence>
+ In any event, FIG. 2 shows an illustrative data flow diagram for environment <part-num-ref name="illustrative data flow diagram for environment">10</part-num-ref>
+ (FIG.    </p>
+    <p id="p-29" num="29">1) according to an embodiment of the invention. Trigger component <part-num-ref name="invention. Trigger component">34</part-num-ref>
+ manages a set of triggers <part-num-ref name="set of triggers">50,</part-num-ref>
+ while collection component <part-num-ref name="set of triggers 50, while collection component">36</part-num-ref>
+ manages a set of collectors <part-num-ref name="set of collectors">52.</part-num-ref>
+ In general, each component <part-num-ref name="set of collectors 52. In general, each component">34,</part-num-ref>
+ <part-num-ref name="set of collectors 52. In general, each component 34,">36</part-num-ref>
+ can enable a user <part-num-ref name="user">16</part-num-ref>
+ (FIG. <part-num-ref name="(FIG.">1)</part-num-ref>
+ to request various operations (e.g., read, write, modify, delete, etc.) on the corresponding program object(s) <part-num-ref name="corresponding program object(s)">50,</part-num-ref>
+ <part-num-ref name="corresponding program object(s) 50,">52</part-num-ref>
+ and perform the requested operations.    </p>
+    <p id="p-30" num="30">User 16 can request an operation using any solution. For example, components <part-num-ref name="operation using any solution. For example, components">34,</part-num-ref>
+ <part-num-ref name="operation using any solution. For example, components 34,">36</part-num-ref>
+ can generate a user interface for display to user <part-num-ref name="user interface for display to user">16,</part-num-ref>
+ which renders some or all of the data for a program object <part-num-ref name="program object">50,</part-num-ref>
+ <part-num-ref name="program object 50,">52,</part-num-ref>
+ and enables user <part-num-ref name="program object 50, 52, and enables user">16</part-num-ref>
+ to request one or more actions. Further, components <part-num-ref name="to request one or more actions. Further, components">34,</part-num-ref>
+ <part-num-ref name="to request one or more actions. Further, components 34,">36</part-num-ref>
+ can define an application program interface (API) or the like that enables user <part-num-ref name="like that enables user">16,</part-num-ref>
+ another system in this case, to request one or more actions and receive data on program object(s) <part-num-ref name="like that enables user 16, another system in this case, to request one or more actions and receive data on program object(s)">50,</part-num-ref>
+ <part-num-ref name="like that enables user 16, another system in this case, to request one or more actions and receive data on program object(s) 50,">52.</part-num-ref>
+    </p>
+    <p id="p-31" num="31">[0026] Interface component 32 can enable user <part-num-ref name="can enable user">16</part-num-ref>
+ (FIG. <part-num-ref name="(FIG.">1)</part-num-ref>
+ to define a set of links (stored as link data <part-num-ref name="set of links (stored as link data">60)</part-num-ref>
+ between trigger(s) <part-num-ref name="between trigger(s)">50</part-num-ref>
+ and collector(s) <part-num-ref name="and collector(s)">52.</part-num-ref>
+ To this extent, interface component <part-num-ref name="and collector(s) 52. To this extent, interface component">32</part-num-ref>
+ can generate a monitor definition interface <part-num-ref name="monitor definition interface">56</part-num-ref>
+ for display to user <part-num-ref name="for display to user">16.</part-num-ref>
+ FIG. 3 shows an illustrative monitor definition interface <part-num-ref name="illustrative monitor definition interface">56</part-num-ref>
+ according to an embodiment of the invention. Interface <part-num-ref name="invention. Interface">56</part-num-ref>
+ is shown displaying a set of target computing environments (devices) <part-num-ref name="set of target computing environments (devices)">70</part-num-ref>
+ along with configuration information <part-num-ref name="along with configuration information">72</part-num-ref>
+ for each target computing environment <part-num-ref name="for each target computing environment">70.</part-num-ref>
+ In general, configuration information <part-num-ref name="for each target computing environment 70. In general, configuration information">72</part-num-ref>
+ can comprise any type of configuration information <part-num-ref name="can comprise any type of configuration information">72,</part-num-ref>
+ e.g., operating system type/version (as shown), hardware configuration, basic input output system (BIOS) type/version, and/or the like, for the corresponding target computing environment <part-num-ref name="corresponding target computing environment">70.</part-num-ref>
+    </p>
+    <boundary-data type="header">RSW920050212US1                         8</boundary-data>
+    <p id="p-32" num="32">
+      <page-break num="9"/>
+      <confidence value="5">[</confidence>
+0027<confidence value="5">]</confidence>
+ Referring to FIGS. 2 and <part-num-ref name="and">3,</part-num-ref>
+ interface component <part-num-ref name="and 3, interface component">32</part-num-ref>
+ can obtain target computing environment(s) <part-num-ref name="can obtain target computing environment(s)">70</part-num-ref>
+ using any solution. For example, interface component <part-num-ref name="using any solution. For example, interface component">32</part-num-ref>
+ can generate a user interface that lists all computing environments <part-num-ref name="user interface that lists all computing environments">18</part-num-ref>
+ available on a network and enables user <part-num-ref name="network and enables user">16</part-num-ref>
+ to select one or more computing environments <part-num-ref name="to select one or more computing environments">18</part-num-ref>
+ for inclusion in the set of target computing environments <part-num-ref name="set of target computing environments">70.</part-num-ref>
+ Further, interface component <part-num-ref name="set of target computing environments 70. Further, interface component">32</part-num-ref>
+ can obtain the available computing environments <part-num-ref name="available computing environments">18</part-num-ref>
+ and/or configuration information <part-num-ref name="and/or configuration information">72</part-num-ref>
+ for each target computing environment <part-num-ref name="for each target computing environment">70</part-num-ref>
+ using any solution. For example, interface component <part-num-ref name="using any solution. For example, interface component">32</part-num-ref>
+ can query each computing environment <part-num-ref name="can query each computing environment">18,</part-num-ref>
+ query a data store of data on computing environments <part-num-ref name="data store of data on computing environments">18,</part-num-ref>
+ and/or query another system that can obtain and provide available computing environments <part-num-ref name="data store of data on computing environments 18, and/or query another system that can obtain and provide available computing environments">18</part-num-ref>
+ and/or configuration information <part-num-ref name="and/or configuration information">72.</part-num-ref>
+    </p>
+    <p id="p-33" num="33">[0028<confidence value="5">]</confidence>
+ In any event, interface 56 further includes a set of available triggers <part-num-ref name="set of available triggers">74</part-num-ref>
+ and a set of available collectors <part-num-ref name="set of available collectors">76.</part-num-ref>
+ Interface component <part-num-ref name="set of available collectors 76. Interface component">32</part-num-ref>
+ can obtain the set of available triggers <part-num-ref name="set of available triggers">74</part-num-ref>
+ from trigger component <part-num-ref name="from trigger component">34</part-num-ref>
+ using any solution. For example, the set of available triggers <part-num-ref name="set of available triggers">74</part-num-ref>
+ can comprise all triggers <part-num-ref name="can comprise all triggers">50</part-num-ref>
+ managed by trigger component <part-num-ref name="managed by trigger component">34.</part-num-ref>
+ Alternatively, the set of available triggers <part-num-ref name="set of available triggers">74</part-num-ref>
+ can be selected from all triggers <part-num-ref name="can be selected from all triggers">50</part-num-ref>
+ based on the set of target computing environments <part-num-ref name="set of target computing environments">70.</part-num-ref>
+ To this extent, interface component <part-num-ref name="set of target computing environments 70. To this extent, interface component">32</part-num-ref>
+ can provide the set of target computing environments <part-num-ref name="set of target computing environments">70</part-num-ref>
+ and/or the corresponding configuration information <part-num-ref name="corresponding configuration information">72</part-num-ref>
+ to trigger component <part-num-ref name="to trigger component">34,</part-num-ref>
+ which can provide interface component <part-num-ref name="to trigger component 34, which can provide interface component">32</part-num-ref>
+ with each trigger <part-num-ref name="with each trigger">50</part-num-ref>
+ that is compatible with at least one of the target computing environments <part-num-ref name="target computing environments">18</part-num-ref>
+ and/or configuration information <part-num-ref name="and/or configuration information">72.</part-num-ref>
+ For example, a trigger <part-num-ref name="trigger">50</part-num-ref>
+ may require a particular type/version of operating system on computing environment <part-num-ref name="particular type/version of operating system on computing environment">18.</part-num-ref>
+ Likewise, interface component <part-num-ref name="particular type/version of operating system on computing environment 18. Likewise, interface component">32</part-num-ref>
+ can obtain the set of available collectors <part-num-ref name="set of available collectors">76</part-num-ref>
+ from collector component <part-num-ref name="from collector component">36</part-num-ref>
+ using any solution, such as one similar to those described with respect to the set of av<confidence value="8888888">ailable</confidence>
+ <confidence value="2222222">trggers</confidence>
+ <part-num-ref name="set of available trggers">
+        <confidence value="225">74.</confidence>
+      </part-num-ref>
+    </p>
+    <boundary-data type="header">RSW920050212US 1                        9</boundary-data>
+    <p id="p-34" num="34">
+      <page-break num="10"/>
+      <confidence value="5">[</confidence>
+0029] When the set of target computing environments <part-num-ref name="set of target computing environments">70</part-num-ref>
+ includes multiple computing environments <part-num-ref name="includes multiple computing environments">18,</part-num-ref>
+ one or more of the set of available triggers <part-num-ref name="set of available triggers">74</part-num-ref>
+ <confidence value="222222">and/or</confidence>
+ set of available collectors <part-num-ref name="and/or set of available collectors">76</part-num-ref>
+ may not be compatible with each target computing environment <part-num-ref name="may not be compatible with each target computing environment">18.</part-num-ref>
+ In this case, interface component <part-num-ref name="may not be compatible with each target computing environment 18. In this case, interface component">32</part-num-ref>
+ can provide an indication to user <part-num-ref name="indication to user">16</part-num-ref>
+ (FIG. 1). For example, interface <part-num-ref name="(FIG. 1). For example, interface">56</part-num-ref>
+ is shown displaying a warning indicator (e.g., an exclamation point) for "TRIGGER D". Further, user <part-num-ref name="exclamation point) for &quot;TRIGGER D&quot;. Further, user">16</part-num-ref>
+ can select the warning indicator (e.g., by hovering a mouse over it, right/left clicking on the indicator, etc.), and interface component <part-num-ref name="indicator, etc.), and interface component">32</part-num-ref>
+ can provide further details regarding the indication (e.g., displayed in a popup window as shown for the warning indicator for "COLLECTOR B").    </p>
+    <p id="p-35" num="35">It is understood that this is only an illustrative solution, and interface component <part-num-ref name="illustrative solution, and interface component">32</part-num-ref>
+ can implement any solution.    </p>
+    <p id="p-36" num="36">
+      <confidence value="5">[</confidence>
+0030<confidence value="5">]</confidence>
+ Regardless, interface 56 enables user <part-num-ref name="enables user">16</part-num-ref>
+ (FIG. <part-num-ref name="(FIG.">1)</part-num-ref>
+ to manage a set of links <part-num-ref name="set of links">78</part-num-ref>
+ between the set of available triggers <part-num-ref name="set of available triggers">74</part-num-ref>
+ and the set of available collectors <part-num-ref name="set of available collectors">76.</part-num-ref>
+ Each link defines a relationship between a trigger <part-num-ref name="trigger">50</part-num-ref>
+ and a collector <part-num-ref name="collector">52.</part-num-ref>
+ In particular, each link indicates that when trigger <part-num-ref name="collector 52. In particular, each link indicates that when trigger">50</part-num-ref>
+ detects the corresponding monitored condition, each related collector <part-num-ref name="corresponding monitored condition, each related collector">52</part-num-ref>
+ should collect the corresponding environment information. In one embodiment, interface component <part-num-ref name="corresponding environment information. In one embodiment, interface component">32</part-num-ref>
+ can obtain a set of default links from link data <part-num-ref name="set of default links from link data">60.</part-num-ref>
+ The set of default links can define, for a trigger <part-num-ref name="trigger">50,</part-num-ref>
+ one or more collectors <part-num-ref name="trigger 50, one or more collectors">52</part-num-ref>
+ that can collect the corresponding environment information. For example, "TRIGGER A" could have a default link with "COLLECTOR A", and as a result, the set of links <part-num-ref name="set of links">78</part-num-ref>
+ could include a link between "TRIGGER A" and "COLLECTOR A". In this manner, user <part-num-ref name="link between &quot;TRIGGER A&quot; and &quot;COLLECTOR A&quot;. In this manner, user">16</part-num-ref>
+ is not required to define commonly used links in the set of links <part-num-ref name="set of links">78.</part-num-ref>
+ However, it is understood that user <part-num-ref name="set of links 78. However, it is understood that user">16</part-num-ref>
+ could choose to remove one or more of the default links from the set of links <part-num-ref name="set of links">78.</part-num-ref>
+    </p>
+    <boundary-data type="header">RSW920050212US1                         10</boundary-data>
+    <p id="p-37" num="37">
+      <page-break num="11"/>
+      <confidence value="5">[</confidence>
+0031<confidence value="5">]</confidence>
+ User 16 (FIG. <part-num-ref name="(FIG.">1)</part-num-ref>
+ can use interface <part-num-ref name="can use interface">56</part-num-ref>
+ to define, modify, delete, and/or the like, links in the set of links <part-num-ref name="set of links">78</part-num-ref>
+ using any solution. For example, user <part-num-ref name="using any solution. For example, user">16</part-num-ref>
+ can use a mouse or the like to drag a connection from a trigger <part-num-ref name="trigger">
+        <confidence value="66">50</confidence>
+      </part-num-ref>
+ in the set of available triggers <part-num-ref name="set of available triggers">74</part-num-ref>
+ to a collector <part-num-ref name="collector">52</part-num-ref>
+ in the set of available collectors <part-num-ref name="set of available collectors">76.</part-num-ref>
+ Interface <part-num-ref name="set of available collectors 76. Interface">56</part-num-ref>
+ can display each link in the set of links <part-num-ref name="set of links">78</part-num-ref>
+ using any solution. To this extent, the link(s) for each trigger <part-num-ref name="link(s) for each trigger">50</part-num-ref>
+ can be displayed using a unique color, style, and/or the like.    </p>
+    <p id="p-38" num="38">[0032<confidence value="5">]</confidence>
+ In any event, once user 16 (FIG. <part-num-ref name="(FIG.">1)</part-num-ref>
+ has defined a desired set of links <part-num-ref name="desired set of links">78,</part-num-ref>
+ user <part-num-ref name="desired set of links 78, user">16</part-num-ref>
+ can select to generate one or more monitors <part-num-ref name="can select to generate one or more monitors">54</part-num-ref>
+ (e.g., by selecting a "CREATE MONITORS" button in interface 56). In this case, deployment component <part-num-ref name="&quot;CREATE MONITORS&quot; button in interface 56). In this case, deployment component">38</part-num-ref>
+ can obtain link data <part-num-ref name="can obtain link data">60</part-num-ref>
+ (e.g., which comprises the set of links <part-num-ref name="set of links">78)</part-num-ref>
+ and generate one or more monitors <part-num-ref name="and generate one or more monitors">54</part-num-ref>
+ based on link data <part-num-ref name="based on link data">60.</part-num-ref>
+ In one embodiment, deployment component <part-num-ref name="based on link data 60. In one embodiment, deployment component">38</part-num-ref>
+ obtains a monitor engine <part-num-ref name="monitor engine">58,</part-num-ref>
+ which can implement the various links defined by link data <part-num-ref name="various links defined by link data">60</part-num-ref>
+ between trigger(s) <part-num-ref name="between trigger(s)">50</part-num-ref>
+ and collector(s) <part-num-ref name="and collector(s)">52.</part-num-ref>
+ In particular, deployment component <part-num-ref name="and collector(s) 52. In particular, deployment component">38</part-num-ref>
+ can provide monitor engine <part-num-ref name="can provide monitor engine">58</part-num-ref>
+ with a reference to a trigger <part-num-ref name="trigger">50</part-num-ref>
+ and its corresponding collector(s) <part-num-ref name="and its corresponding collector(s)">52.</part-num-ref>
+ Monitor engine <part-num-ref name="and its corresponding collector(s) 52. Monitor engine">58</part-num-ref>
+ can include functionality that is able to initiate trigger <part-num-ref name="can include functionality that is able to initiate trigger">50,</part-num-ref>
+ receive a notification of a situation from trigger <part-num-ref name="situation from trigger">50,</part-num-ref>
+ invoke each collector <part-num-ref name="situation from trigger 50, invoke each collector">52</part-num-ref>
+ in response to the notification, and receive environment information from each collector <part-num-ref name="notification, and receive environment information from each collector">52.</part-num-ref>
+    </p>
+    <p id="p-39" num="39">[0033<confidence value="5">]</confidence>
+ Deployment component 38 can generate monitor(s) <part-num-ref name="can generate monitor(s)">54</part-num-ref>
+ using any solution. For example, deployment component <part-num-ref name="using any solution. For example, deployment component">38</part-num-ref>
+ can compile and/or link monitor engine <part-num-ref name="can compile and/or link monitor engine">58,</part-num-ref>
+ trigger(s) <part-num-ref name="can compile and/or link monitor engine 58, trigger(s)">50,</part-num-ref>
+ and collector(s) <part-num-ref name="can compile and/or link monitor engine 58, trigger(s) 50, and collector(s)">52</part-num-ref>
+ to generate a single executable file for monitor <part-num-ref name="single executable file for monitor">54.</part-num-ref>
+ In one embodiment, deployment component <part-num-ref name="single executable file for monitor 54. In one embodiment, deployment component">38</part-num-ref>
+ generates a single monitor <part-num-ref name="single monitor">54</part-num-ref>
+ for each trigger <part-num-ref name="for each trigger">50</part-num-ref>
+ having one or more links defined in link data <part-num-ref name="having one or more links defined in link data">60.</part-num-ref>
+ Alternatively, deployment component <part-num-ref name="having one or more links defined in link data 60. Alternatively, deployment component">38</part-num-ref>
+ can generate a single monitor <part-num-ref name="single monitor">54</part-num-ref>
+ that is capable of managing the implementation of multiple triggers <part-num-ref name="implementation of multiple triggers">50</part-num-ref>
+ and their corresponding collectors <part-num-ref name="and their corresponding collectors">52.</part-num-ref>
+ Further<confidence value="5">,</confidence>
+ when <confidence value="6">a</confidence>
+ trigger <part-num-ref name="trigger">
+        <confidence value="66">50</confidence>
+      </part-num-ref>
+ <confidence value="222222">and/or</confidence>
+ c<confidence value="888">oll</confidence>
+ect<confidence value="8">o</confidence>
+r <part-num-ref name="and/or collector">
+        <confidence value="66">52</confidence>
+      </part-num-ref>
+ <confidence value="66">is</confidence>
+ <confidence value="656">not</confidence>
+ supp<confidence value="8">o</confidence>
+rte<confidence value="8">d</confidence>
+ <confidence value="66">by</confidence>
+ <boundary-data type="header">RSW920050212US1                        11</boundary-data>
+      <page-break num="12"/>
+one or more target computing environments <part-num-ref name="is not supported by one or more target computing environments">18,</part-num-ref>
+ deployment component <part-num-ref name="is not supported by one or more target computing environments 18, deployment component">38</part-num-ref>
+ can generate a unique monitor <part-num-ref name="unique monitor">54</part-num-ref>
+ for each computing environment <part-num-ref name="for each computing environment">18,</part-num-ref>
+ which only includes the supported trigger(s) <part-num-ref name="supported trigger(s)">50</part-num-ref>
+ and collector(s) <part-num-ref name="and collector(s)">52.</part-num-ref>
+    </p>
+    <p id="p-40" num="40">
+      <confidence value="5">[</confidence>
+0034<confidence value="5">]</confidence>
+ Once monitor(s) 54 are a<confidence value="8">v</confidence>
+ailable, user <part-num-ref name="are available, user">16</part-num-ref>
+ (FIG. <part-num-ref name="(FIG.">1)</part-num-ref>
+ can select (e.g., by selecting the "DEPLOY MONITORS" button) to deploy the monitor(s) <part-num-ref name="monitor(s)">54</part-num-ref>
+ to the set of target computing environments <part-num-ref name="set of target computing environments">70.</part-num-ref>
+ In response, deployment component <part-num-ref name="set of target computing environments 70. In response, deployment component">38</part-num-ref>
+ can deploy the monitor(s) <part-num-ref name="monitor(s)">54</part-num-ref>
+ for implementation on each of the target computing environments <part-num-ref name="target computing environments">18.</part-num-ref>
+ To this extent, when multiple monitor(s) <part-num-ref name="target computing environments 18. To this extent, when multiple monitor(s)">54</part-num-ref>
+ are to be deployed, e.g., one monitor <part-num-ref name="one monitor">54</part-num-ref>
+ for each selected trigger <part-num-ref name="for each selected trigger">50</part-num-ref>
+ and/or different monitors <part-num-ref name="and/or different monitors">54</part-num-ref>
+ for different configurations, deployment component <part-num-ref name="for different configurations, deployment component">38</part-num-ref>
+ can select the appropriate monitor(s) <part-num-ref name="appropriate monitor(s)">54</part-num-ref>
+ for each target computing environment <part-num-ref name="for each target computing environment">18</part-num-ref>
+ and provide the selected monitor(s) <part-num-ref name="selected monitor(s)">54</part-num-ref>
+ for implementation.    </p>
+    <p id="p-41" num="41">
+      <confidence value="5">[</confidence>
+0035] FIG. 4 shows a data flow diagram for an illustrative monitor <part-num-ref name="illustrative monitor">54</part-num-ref>
+ after implementation on a computing environment <part-num-ref name="computing environment">18</part-num-ref>
+ according to an embodiment of the invention. Monitor <part-num-ref name="invention. Monitor">54</part-num-ref>
+ can be generated by deployment component <part-num-ref name="can be generated by deployment component">38</part-num-ref>
+ based on the set of links <part-num-ref name="set of links">78</part-num-ref>
+ defined for "TRIGGER A".    </p>
+    <p id="p-42" num="42">After initialization by monitor engine 58, trigger 50 obtains monitored information <part-num-ref name="obtains monitored information">80</part-num-ref>
+ about computing environment <part-num-ref name="about computing environment">18.</part-num-ref>
+ As noted above, monitored information <part-num-ref name="about computing environment 18. As noted above, monitored information">80</part-num-ref>
+ can comprise any type of information on one or more resources, processes, events, etc., that is required by trigger <part-num-ref name="can comprise any type of information on one or more resources, processes, events, etc., that is required by trigger">50</part-num-ref>
+ to determine the presence of a condition on computing environment <part-num-ref name="condition on computing environment">18.</part-num-ref>
+ When monitored information <part-num-ref name="condition on computing environment 18. When monitored information">80</part-num-ref>
+ indicates the presence of the condition, trigger <part-num-ref name="condition, trigger">50</part-num-ref>
+ can notify monitor engine <part-num-ref name="can notify monitor engine">58.</part-num-ref>
+    </p>
+    <p id="p-43" num="43">In response, monitor engine 58 can invoke each collector 52A, 52C, 52F, each of which collects a corresponding type of environment information 82A, 82C, 82F for computing environment <part-num-ref name="corresponding type of environment information 82A, 82C, 82F for computing environment">18.</part-num-ref>
+    </p>
+    <p id="p-44" num="44">Monitor engine 58 can package all of the environment information 82A, 82C, 82F into event <confidence value="2552">data</confidence>
+ <part-num-ref name="environment information 82A, 82C, 82F into event data">
+        <confidence value="662">62.</confidence>
+      </part-num-ref>
+    </p>
+    <boundary-data type="header">RSW920050212US 1                      12</boundary-data>
+    <p id="p-45" num="45">
+      <page-break num="13"/>
+      <confidence value="5">[</confidence>
+0036<confidence value="5">]</confidence>
+ Monitor 54 can provide event data <part-num-ref name="can provide event data">62</part-num-ref>
+ for processing by correlation component <part-num-ref name="for processing by correlation component">40.</part-num-ref>
+    </p>
+    <p id="p-46" num="46">After receiving event data 62, correlation component 40 can analyze event data <part-num-ref name="can analyze event data">62</part-num-ref>
+ together with event data received from other monitor(s) <part-num-ref name="together with event data received from other monitor(s)">54</part-num-ref>
+ and/or other events, to establish any relationships between events and/or to determine a root cause of one or more events. Correlation component <part-num-ref name="root cause of one or more events. Correlation component">40</part-num-ref>
+ can generate correlation data <part-num-ref name="can generate correlation data">64</part-num-ref>
+ for presentation to user <part-num-ref name="for presentation to user">16</part-num-ref>
+ (FIG. <part-num-ref name="(FIG.">1)</part-num-ref>
+ that comprises the results of the analysis of event data <part-num-ref name="analysis of event data">62,</part-num-ref>
+ e.g., a set of relationships, a set of root causes, and/or the like.    </p>
+    <p id="p-47" num="47">
+      <confidence value="5">[</confidence>
+0037] While shown and described herein as a method and system for managing a set of monitors, it is understood that the invention further provides various alternative embodiments.    </p>
+    <p id="p-48" num="48">For example, in one embodiment, the invention provides a program product stored on a computer-readable medium, which when executed, enables a computer infrastructure to manage the set of monitors. To this extent, the computer-readable medium includes program code, such as monitor system <part-num-ref name="computer-readable medium includes program code, such as monitor system">30</part-num-ref>
+ (FIG. 1), which implements the process described herein. It is understood that the term "computer-readable medium" comprises one or more of any type of tangible medium of expression (e.g., physical embodiment) of the program code. In particular, the computer-readable medium can comprise program code embodied on one or more portable storage articles of manufacture (e.g., a compact disc, a magnetic disk, a tape, etc.), on one or more data storage portions of a computing device, such as memory 22A (FIG. <part-num-ref name="computing device, such as memory 22A (FIG.">1)</part-num-ref>
+ and/or storage system 22B (FIG. <part-num-ref name="and/or storage system 22B (FIG.">1)</part-num-ref>
+ (e.g., a fixed disk, a read-only memory, a random access memory, a cache memory, etc.), as a data signal traveling over a network (e.g., during a wired/wireless electronic distribution of the program product), on paper (e.g., capable of being scanned in as electronic data), and/or the like.    </p>
+    <p id="p-49" num="49">
+      <confidence value="5">[</confidence>
+0038<confidence value="5">]</confidence>
+ In another embodiment, the invention provides a method of generating a system for managing a set of <confidence value="88">mo</confidence>
+nit<confidence value="8">o</confidence>
+r<confidence value="82">s.</confidence>
+ <confidence value="26">In</confidence>
+ thi<confidence value="8">s</confidence>
+ <confidence value="2466">rce,</confidence>
+ a computer <confidence value="22222222222222">irfrastructure</confidence>
+, such <confidence value="66">as</confidence>
+ computer <boundary-data type="header">
+        <confidence value="88">RS</confidence>
+W920050212US1                         13      </boundary-data>
+      <page-break num="14"/>
+infrastructure <part-num-ref name="computer irfrastructure, such as computer infrastructure">12</part-num-ref>
+ (FIG. 1), can be obtained (e.g., created, maintained, having made available to, etc.) and one or more systems for performing the process described herein can be obtained (e.g., created, purchased, used, modified, etc.) and deployed to the computer infrastructure. To this extent, the deployment of each system can comprise one or more of<confidence value="5">:</confidence>
+ <part-num-ref name="deployment of each system can comprise one or more of:">(1)</part-num-ref>
+ installing program code on a computing device, such as computing device <part-num-ref name="computing device, such as computing device">14</part-num-ref>
+ (FIG. 1), from a computer-readable medium; <part-num-ref name="computer-readable medium;">(2)</part-num-ref>
+ adding one or more computing devices to the computer infrastructure; and <part-num-ref name="computer infrastructure; and">(3)</part-num-ref>
+ incorporating and/or modifying one or more existing systems of the computer infrastructure, to enable the computer infrastructure to perform the process steps of the invention.    </p>
+    <p id="p-50" num="50">
+      <confidence value="5">[</confidence>
+0039<confidence value="5">]</confidence>
+ In still another embodiment, the invention provides a business method that performs the process described herein on a subscription, advertising, and/or fee basis. That is, a service provider, such as a Solutions Integrator, could offer to manage a set of monitors as described herein. In this case, the service provider can manage (e.g., create, maintain, support, etc.) a computer infrastructure, such as computer infrastructure <part-num-ref name="computer infrastructure, such as computer infrastructure">12</part-num-ref>
+ (FIG. 1), that performs the process described herein for one or more customers. In return, the service provider can receive payment from the customer(s) under a subscription and/or fee agreement, receive payment from the sale of advertising to one or more third parties, and/or the like.    </p>
+    <p id="p-51" num="51">
+      <confidence value="5">[</confidence>
+0040<confidence value="5">]</confidence>
+ As used herein, it is understood that the terms "program code" and "computer program code" are synonymous and mean any expression, in any language, code or notation, of a set of instructions that cause a computing device having an information processing capability to perform a particular function either directly or after any combination of the following: (a) conversion to another language, code or notation; (b) reproduction in a different material form;    </p>
+    <p id="p-52" num="52">and/or (c) decompression. To this extent, program code can be embodied as one or more types of program <confidence value="222222228">nrodcits,</confidence>
+ such <confidence value="66">as</confidence>
+ <confidence value="6">a</confidence>
+n <confidence value="22222222222222222222">application/software</confidence>
+ program<confidence value="6">,</confidence>
+ component <confidence value="2222222222">softvarc/a</confidence>
+ <confidence value="222222">librry</confidence>
+ <confidence value="2">o</confidence>
+ <boundary-data type="header">RSW920050212US1                         14</boundary-data>
+      <page-break num="15"/>
+functions, an operating system, a basic <confidence value="224">I/O</confidence>
+ system/driver for a particular computing and/or <confidence value="685">1/0</confidence>
+ device, and the like. Further, it is understood that the terms "component" and "system" are synonymous as used herein and represent any combination of hardware and/or software capable of performing some function(s).    </p>
+    <p id="p-53" num="53">[0041<confidence value="5">]</confidence>
+ The foregoing description of various aspects of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed, and obviously, many modifications and variations are possible. Such modifications and variations that may be apparent to an individual in the art are included within the scope of the invention as defined by the accompanying claims.    </p>
+    <boundary-data type="header">RSW920050212US<confidence value="4">1</confidence>
+                        15    </boundary-data>
+  </description>
+</us-patent-application>
+

applicant/11411853.xml

@@ -0,0 +1,24 @@
+<?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>11411853</doc-number>
+        <date>2009-06-24</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">Application No. 11/411,853 Docket No. 042144-000007 Page 2 of <part-num-ref name="of">12</part-num-ref>
+ Amendments to the Specification Replace paragraph [0041] of the original specification with the following paragraph with material deleted to overcome objections to the specification.    </p>
+    <p id="p-2" num="2">[0041]: As will be appreciated by those skilled in the art, the foregoing example, demonstrations, and method steps may be implemented by suitable code on a processor base system, such as general purpose or special purpose computer. It should also be noted that different implementations of the present technique may perform some or all the steps described herein in different orders or substantially concurrently, that may be, in parallel.</p>
+    <p id="p-3" num="3">Furthermore, the functions may be implemented in a variety of programming languages. Such code, as will be appreciated by those skilled in the art, may be stored [[ot]] to adapted for storage in one or more tangible machine readable media, such as on memory chips, local or remote hard disks, optical disks or other media, which may be accessed by a processor based system to execute the stored code. Note that <confidence value="666">the</confidence>
+ tangible media <confidence value="666">may</confidence>
+ <confidence value="2666">comp</confidence>
+   <confidence value="2">p</confidence>
+   <confidence value="42">or</confidence>
+ 12558542.2     </p>
+  </description>
+</us-patent-application>
+

applicant/11435448.xml

@@ -0,0 +1,37 @@
+<?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>11435448</doc-number>
+        <date>2007-05-15</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">In the Specification Please replace paragraph [0001] with the following amended paragraph:</p>
+    <p id="p-2" num="2">[0001]   This patent application is related to the co-pending U.S. Patent Application, entitled "CLUSTERING AND CLASSIFICATION OF CATEGORY DATA", attorney docket no. 80398.P649, application no. 11/436<confidence value="5">,</confidence>
+142. The related co-pending application is assigned to the same assignee as the present application.    </p>
+    <boundary-data type="header">
+      <confidence value="8">2</confidence>
+    </boundary-data>
+    <p id="p-3" num="3">
+      <page-break num="2"/>
+Consideration of the application as preliminary amended is respectfully requested.    </p>
+    <p id="p-4" num="4">If there are any additional charges, please charge them to our Deposit Account No. 02- 2666.</p>
+    <p id="p-5" num="5">Respectfully submitted, </p>
+    <heading id="h-1">BLAKELY, SOKOLOFF, TAYLOR</heading>
+    <heading id="h-2">&amp; ZAFMAN LLP</heading>
+    <p id="p-6" num="6">
+      <confidence value="88888">Dated</confidence>
+       <confidence value="21">/i</confidence>
+   , 2007 Sheryl Sue Holloway Attorney for Applicant Registration No. 37,850 <part-num-ref name="Sheryl Sue Holloway Attorney for Applicant Registration No. 37,850">12400</part-num-ref>
+ Wilshire Boulevard Seventh Floor Los Angeles, CA 90025-1026 <part-num-ref name="Wilshire Boulevard Seventh Floor Los Angeles, CA 90025-1026">(408)</part-num-ref>
+ 720-8300 x3476 <boundary-data type="header">
+        <confidence value="8">3</confidence>
+      </boundary-data>
+    </p>
+  </description>
+</us-patent-application>
+

applicant/11517973.xml

@@ -0,0 +1,380 @@
+<?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>11517973</doc-number>
+        <date>2006-09-08</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">Dkt. 5014<confidence value="5">/</confidence>
+75630 Application for United States Letters Patent To all whom it may concern<confidence value="8">:</confidence>
+    </p>
+    <p id="p-2" num="2">Be it known that <confidence value="58">I,</confidence>
+ Michael A. ZIVIN have invented certain new and useful improvements in     </p>
+    <heading id="h-1">METHOD AND SYSTEM FOR DETERMINING THE OPTIMAL TRAVEL ROUTE</heading>
+    <heading id="h-2">BY WHICH CUSTOMERS CAN PURCHASE LOCAL GOODS</heading>
+    <heading id="h-3">AT THE LOWEST TOTAL COST</heading>
+    <p id="p-3" num="3">of which the following is a full, clear and exact description:</p>
+    <boundary-data type="header">
+      <confidence value="8">1</confidence>
+    </boundary-data>
+    <heading id="h-4">METHOD AND SYSTEM FOR DETERMINING THE OPTIMAL TRAVEL ROUTE BY</heading>
+    <heading id="h-5">WHICH CUSTOMERS CAN PURCHASE LOCAL GOODS AT THE LOWEST TOTAL</heading>
+    <heading id="h-6">COST</heading>
+    <heading id="h-7">-- CROSS REFERENCE TO RELATED APPLICATION</heading>
+    <p id="p-4" num="4">
+      <page-break num="2"/>
+      <boundary-data type="line-number">5                  </boundary-data>
+This application claims the benefit of U.S. Provisional Application No. 60/754,776, filed December <part-num-ref name="benefit of U.S. Provisional Application No. 60/754,776, filed December">28,</part-num-ref>
+ <part-num-ref name="benefit of U.S. Provisional Application No. 60/754,776, filed December 28,">2005.</part-num-ref>
+ -- <boundary-data type="line-number">10   </boundary-data>
+    </p>
+    <heading id="h-8">FIELD OF THE INVENTION</heading>
+    <p id="p-5" num="5">This invention relates to a method and system for performing purchase transactions over a general access computer network and, in particular, to a system and method that incorporates geography and location into purchasing decisions.</p>
+    <heading id="h-9">BACKGROUND OF THE INVENTION</heading>
+    <p id="p-6" num="6">
+      <boundary-data type="line-number">15   </boundary-data>
+It is well known that customers have less free time than in the past to manage household responsibilities. According to a recent Economic Policy Institute study, in <part-num-ref name="recent Economic Policy Institute study, in">2001</part-num-ref>
+ the average American family worked 11% more hours <part-num-ref name="average American family worked 11% more hours">(111</part-num-ref>
+ hours) than it did in <part-num-ref name="hours) than it did in">1975.</part-num-ref>
+ Despite having <boundary-data type="line-number">20    </boundary-data>
+less leisure time, customers are spending more time shopping than ever before. In the past few decades, the amount of time customers spent shopping for local goods has increased by nearly 200%. According to the U.S. Government's Center for Transportation Analysis, the average American drove 2,567 miles on shopping trips in <part-num-ref name="average American drove 2,567 miles on shopping trips in">1983</part-num-ref>
+ and over 5,188 miles in <part-num-ref name="and over 5,188 miles in">2001.</part-num-ref>
+    </p>
+    <p id="p-7" num="7">In addition, the average number of miles per trip increased nearly 50%.</p>
+    <p id="p-8" num="8">
+      <boundary-data type="line-number">
+        <confidence value="88">25</confidence>
+      </boundary-data>
+ With less leisure time, most customers would like to reduce the amount of time they spend shopping for everyday products and services in their local neighborhoods. The positive trend <page-break num="3"/>
+      <boundary-data type="header">
+        <confidence value="8">2</confidence>
+      </boundary-data>
+towards online shopping shows that customers like the convenience and prices they find for online goods. However, in the offline, local world, customers are using other tactics to save time and money. Customers increasingly prefer to visit only a few large vendors for the majority of their purchases. The rapid growth of large discounters shows that customers are <boundary-data type="line-number">5   </boundary-data>
+consolidating their purchases at fewer vendors. In addition, customers are willing to change their purchase behavior to save on purchases. The growth of wholesale clubs shows that customers are willing to travel to out-of-the-way locations and buy larger quantities of goods to save money.    </p>
+    <p id="p-9" num="9">
+      <boundary-data type="line-number">10   </boundary-data>
+While consolidating purchases and buying in bulk might work for mass merchandised products, there is no equivalent for the purchase of local services and goods such as haircuts, eye examinations, or car washes. These are often provided by much smaller vendors such as mom-and-pop businesses. Customers must travel to many different vendors and rarely receive discounts for these services.    </p>
+    <p id="p-10" num="10">
+      <boundary-data type="line-number">
+        <confidence value="88">15</confidence>
+      </boundary-data>
+ As customers become more sophisticated in their purchasing strategies, so too have businesses. Manufacturers, retailers and service shops are using a variety of pricing models.    </p>
+    <p id="p-11" num="11">"Price segmentation" is a marketing term used to describe the process of segmenting customers by characteristics such as willingness to pay, need for convenience, and volume <boundary-data type="line-number">20    </boundary-data>
+purchases. For example, warehouse clubs use price segmentation to provide low prices for customers willing to purchase products in bulk from out-of-the-way locations. Most customers are unaware of price segmentation strategies, but realize that some customers pay more than other customers for the same goods.    </p>
+    <boundary-data type="header">
+      <confidence value="8">3</confidence>
+    </boundary-data>
+    <p id="p-12" num="12">
+      <page-break num="4"/>
+It is increasingly more difficult for customers to determine if they are getting the lowest price for a product or service. The wide variety of pricing schemes and price segmentation strategies means that some customers may never get the opportunity to buy a good at the same price as another set of customers. For example, female customers may be sent coupons <boundary-data type="line-number">5   </boundary-data>
+in the mail for 10% off at a particular vendor but male customers never receive the coupon.    </p>
+    <p id="p-13" num="13">Effectively, customers do not have transparency into prices, thus making it difficult for them to make educated decisions on what goods to buy, at what time and from what vendor.</p>
+    <p id="p-14" num="14">Price transparency is further exacerbated by the difficulty of comparing similar products sold <boundary-data type="line-number">10   </boundary-data>
+by different vendors. Products and services are often sold in different quantities, for examples, a <confidence value="5">1</confidence>
+2oz can of soda versus a 48oz bottle of the same soda or a <part-num-ref name="">60</part-num-ref>
+ minute massage versus a <part-num-ref name="">90</part-num-ref>
+ minute massage. The difference in quantity makes it difficult for customers to know if they are getting a good deal.    </p>
+    <p id="p-15" num="15">
+      <boundary-data type="line-number">15   </boundary-data>
+The purchase price of goods is only one component of the total cost of the goods. When buying goods online, the item has a price to which are added shipping costs and taxes. When shopping offline, customers often do not factor in the many other variables that contribute to the total cost of buying goods. These variables might include:    </p>
+    <p id="p-16" num="16">
+      <boundary-data type="line-number">20       </boundary-data>
+      <confidence value="1">"</confidence>
+  Travel costs-such as for fuel, time spent on the road, wear and tear on the automobile, or time waiting for public transportation <confidence value="2">"</confidence>
+ Sales tax-different rates for purchasing in one county versus another <confidence value="2">"</confidence>
+ Opportunity costs-the lower prices one may have paid for the same goods at a different location <page-break num="5"/>
+      <boundary-data type="header">
+        <confidence value="8">4</confidence>
+      </boundary-data>
+      <confidence value="2">"</confidence>
+ Search costs-the amount of time one spends searching for vendors that carry the goods at the prices they are willing to buy them <confidence value="2">"</confidence>
+ Discounts-price segmentation has meant that consumers receive many different types of discounts that should be factored into purchasing decisions <boundary-data type="line-number">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+ When evaluating which goods to buy and the vendors they should be bought from, customers must make tradeoffs which often do not result in the lowest total price for the customer. For example, when factoring in time costs and fuel costs, some customers may be surprised to learn that traveling <part-num-ref name="customer. For example, when factoring in time costs and fuel costs, some customers may be surprised to learn that traveling">40</part-num-ref>
+ miles to a warehouse club might not result in any cost savings over <boundary-data type="line-number">10   </boundary-data>
+buying the goods from local vendors.    </p>
+    <p id="p-17" num="17">Rarely are customers aware of the many variables that ideally should be factored into everyday purchasing decisions. Coupled with the lack of price transparency, customers are rarely able to make educated purchasing decisions and are therefore unlikely to pay the <boundary-data type="line-number">15   </boundary-data>
+lowest price for products and services.    </p>
+    <p id="p-18" num="18">The growing acceptance of wireless Internet access, portable computers and automobile navigation systems means that customers can make smarter shopping decisions. Services such as Google Maps and Mapquest and hardware such as Magellan navigation systems <boundary-data type="line-number">20    </boundary-data>
+allow customers to determine how to optimally get from point A to point B. In addition, customers are increasingly using wireless devices to access local information such as weather reports and basic vendor information such as location and phone numbers.    </p>
+    <p id="p-19" num="19">Limited pricing information for many large vendors such as electronics retailers and 25    department stores already may be available on wireless devices. However, what is needed is <page-break num="6"/>
+      <boundary-data type="header">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+      <confidence value="88">an</confidence>
+ offering that determines the optimal means by which customers should purchase such goods in a local area so as to minimize total purchase costs. It is not enough for customers to simply compare the price of a product at store A versus the same product at store B. The other aforementioned factors should be taken into account. The customer should be <boundary-data type="line-number">5   </boundary-data>
+presented with a list of vendors which should be considered and the order in which one should make the purchases. For example, driving <part-num-ref name="purchases. For example, driving">10</part-num-ref>
+ miles across town during rush hour to purchase a $5.00 item might not be financially worthwhile if the same item can be purchased nearby for $6.00. While the cost of the item on a per unit basis might be higher, the total purchase likely will be lower.    </p>
+    <p id="p-20" num="20">
+      <boundary-data type="line-number">
+        <confidence value="88">10</confidence>
+      </boundary-data>
+ These types of decisions often are made by customers in their heads and without full information. Given the plethora of data feeds available (such as traffic feeds), pricing and vendor data, and customers' willingness to provide detailed information about themselves (such as their default zip code), it is desirable to create a system that determines the optimal <boundary-data type="line-number">15   </boundary-data>
+means of purchasing goods and services in a local area at the lowest total cost.    </p>
+    <heading id="h-10">SUMMARY OF THE INVENTION</heading>
+    <p id="p-21" num="21">It is an object of the present invention to provide a method and system for purchasing goods and services in a local area.</p>
+    <p id="p-22" num="22">
+      <boundary-data type="line-number">20    </boundary-data>
+It is a further object of the present invention to provide a method and system for purchasing goods and services at the lowest total cost.    </p>
+    <p id="p-23" num="23">To these and other ends, the system and method of present invention uses numerous data sources coupled with customer preferences, computer algorithms and visual displays to <part-num-ref name="system and method of present invention uses numerous data sources coupled with customer preferences, computer algorithms and visual displays to">25</part-num-ref>
+    provide customers with an optimized shopping list. This shopping list is optimized such that <page-break num="7"/>
+      <boundary-data type="header">
+        <confidence value="8">6</confidence>
+      </boundary-data>
+customers can pay the lowest total price for goods particularly taking into account the customer's desire to spend the least amount of time shopping. In other words, the system finds the ideal balance between money saved and time costs.    </p>
+    <p id="p-24" num="24">
+      <boundary-data type="line-number">5   </boundary-data>
+In carrying out this invention, several purchasing problems are solved that no current system has solved. Chief among those is the ability to save customers time and money by giving customers greater price transparency so they can chose which vendors to patronize.    </p>
+    <p id="p-25" num="25">Customers generally are not aware of small price differences between the identical products and services at different locations. This system provides a means by which customers can <boundary-data type="line-number">10   </boundary-data>
+visually see the base price (the sticker price) and the total price of goods at different locations and easily eliminate vendors with prices the customer deems unacceptable.    </p>
+    <p id="p-26" num="26">In addition, customers have only a cursory understanding of why vendors price the same goods at different prices. For example, vendors in more remote locations may have lower <boundary-data type="line-number">15   </boundary-data>
+prices due to lower rent and employee costs while vendors in highly trafficked areas may have steeper prices because of higher rent and employee costs. Again, this system allows consumers to see how variables such as convenience, customer service, and product selection might affect price. In some embodiments of the invention, customers will be able to see the vendors color coded based on their average prices relative to one another.    </p>
+    <p id="p-27" num="27">
+      <boundary-data type="line-number">
+        <confidence value="88">20</confidence>
+      </boundary-data>
+ Consumers do not have a good sense for the total costs associated with purchasing a product or service in their local area. There are too many variables for an individual to consider and often it is not worth the effort to do this analysis manually in order to save a small amount of money. However, using databases and computing power, these calculations can be <part-num-ref name="small amount of money. However, using databases and computing power, these calculations can be">25</part-num-ref>
+    performed almost immediately with minimal time cost to the customer. While the savings a <page-break num="8"/>
+      <boundary-data type="header">
+        <confidence value="8">7</confidence>
+      </boundary-data>
+customer might get on a single shopping trip would be small, over time, these small savings would amount to large sums saved.    </p>
+    <p id="p-28" num="28">The system also provides the means by which customers can switch their purchasing <boundary-data type="line-number">5   </boundary-data>
+decisions after they have embarked on a shopping trip, thereby saving them time. For example, if a vendor has run out of a product, a hair stylist has a backlog of customers, or traffic congestion develops, then the customer can be alerted and provided with alternate solutions in real-time. This alert can come in many forms. In one embodiment, the alert is presented on the customer's navigation system and an updated shopping list is presented. In <boundary-data type="line-number">10   </boundary-data>
+another embodiment, the customer receives an email or text message to his or her mobile phone.    </p>
+    <p id="p-29" num="29">Customers often do not consider a vendor with which they are unfamiliar because that vendor may be in a less desirable location, the goods it sells are unknown, and/or the prices it offers <boundary-data type="line-number">15   </boundary-data>
+are also unknown. For example, many customers may not be aware that a certain hair salon also sells a brand of shampoo at a lower cost than the local drugstore. The method and system of the present invention allows customers greater insight into the savings they might achieve by trying other vendors they have never patronized before. This also helps vendors by exposing them to new customers.    </p>
+    <p id="p-30" num="30">
+      <boundary-data type="line-number">
+        <confidence value="88">20</confidence>
+      </boundary-data>
+ With the growing use of mapping and navigation systems, this invention allows for integration of shopping recommendations with location data. Customers would like to see the total price of various goods graphically integrated with mapping systems. Thus, in one embodiment of the invention, the total price for an eye examination, for example, can be <part-num-ref name="eye examination, for example, can be">25</part-num-ref>
+    shown along with a graphic depicting the vendor's physical store location. As the customer <page-break num="9"/>
+      <boundary-data type="header">
+        <confidence value="8">8</confidence>
+      </boundary-data>
+travels in his or her automobile, the prices for eye exams at far away locations can change, showing in real-time how distance affects the total price of an eye exam.    </p>
+    <p id="p-31" num="31">In addition, consumers often do not have a good sense for how a vendor's prices compare <boundary-data type="line-number">5   </boundary-data>
+with the prices of competing vendors. Consumers typically have a feeling that one vendor is more expensive than another, but they have little hard evidence. For example, if one compared <part-num-ref name="feeling that one vendor is more expensive than another, but they have little hard evidence. For example, if one compared">30</part-num-ref>
+ products from supermarket A with the same <part-num-ref name="same">30</part-num-ref>
+ products from supermarket B, it could be determined that one supermarket is more or less expensive than the other. In essence, a consumer price index has been created. This system allows customers to compare <boundary-data type="line-number">10   </boundary-data>
+the total price of a shopping list amongst locations. This information is then fed into an online mapping system or vehicle navigation system. The physical vendor locations are color coded according to how costly the goods are relative to other vendors. For example, expensive supermarkets are shaded red and inexpensive ones are shaded green.    </p>
+    <p id="p-32" num="32">
+      <boundary-data type="line-number">15   </boundary-data>
+This invention uses a large number of variables covering goods, vendors, locations, and consumer preferences to determine the optimal means by which consumers should buy goods in their local area.    </p>
+    <p id="p-33" num="33">Data on goods (products and services) is provided by vendors, third parties, or by customers.</p>
+    <p id="p-34" num="34">
+      <boundary-data type="line-number">20    </boundary-data>
+Product and service data might contain data points such as the price of the goods, manufacturer, package size, Universal Product Code (UPC), Manufacturer's Suggested Retail Price (MSRP), size, weight, duration (for services), identified product substitutes or complements, or any other relevant data.    </p>
+    <boundary-data type="header">
+      <confidence value="8">9</confidence>
+    </boundary-data>
+    <p id="p-35" num="35">
+      <page-break num="10"/>
+Data on vendors is provided by the vendors themselves, third parties or customers. Vendor data might contain data points such as the vendor location (address or GPS coordinates), goods offered, prices, inventory levels, and business hours. Customer ratings of vendors are also collected. Customers can rate vendors on a variety of criteria such as quality, selection, <boundary-data type="line-number">5   </boundary-data>
+convenience and service.    </p>
+    <p id="p-36" num="36">Customer data and preferences are also important. Customers provide information such as their location (by city, postal code, street address, or GPS coordinates), favorite vendors, vendors they dislike, working schedule, discount cards held, estimated time value of money, <boundary-data type="line-number">10   </boundary-data>
+coupons held, and type of automobile.    </p>
+    <p id="p-37" num="37">In addition, other data points are used such as average gasoline prices in the area, traffic conditions, product rebates, and state and local tax rates. These data points may come from third party data feeds fed into the system from an external source which collects said <boundary-data type="line-number">15   </boundary-data>
+disseminates such information.    </p>
+    <p id="p-38" num="38">One embodiment of the system is a search engine interface whereby customers can look up goods by name, description, category, vendor, location or other criteria. The system uses the customer's default or current location which either is provided by the customer or determined <boundary-data type="line-number">20    </boundary-data>
+by the device the customer is using and has been transmitted to the system. The system then references its database of goods and returns the relevant matches for products and services based on commonly used Boolean and natural language search algorithms. The goods are included in the search results only if the goods are offered in the customer's local area. This is determined by searching each vendor in a specific radius. Customers may specify how far <page-break num="11"/>
+      <boundary-data type="header">
+        <confidence value="88">10</confidence>
+      </boundary-data>
+they are willing to travel. The vendor's radius is determined using the vendor's GPS coordinates, postal code, or address.    </p>
+    <p id="p-39" num="39">Once identified as being within reasonable proximity to the customer, the vendors are <boundary-data type="line-number">5   </boundary-data>
+checked to see if they provide the requested goods, if the goods are in stock (in the case of a product), or if the vendor has availability (in case of a service). Vendors who have low ratings, as determined by the customer community, or who have been excluded by the customer are not included in the matches. Vendors who have been identified previously as "preferred vendors" are always included in the matches if they sell the requested goods and <boundary-data type="line-number">10   </boundary-data>
+the goods are in stock or available.    </p>
+    <p id="p-40" num="40">Customers can view the goods and vendors that were identified by the system. Displayed is the price of the goods, with rebates, coupons or other cost savers subtracted from the base price. In addition, an estimated total cost is shown for each of the goods which factors in <boundary-data type="line-number">15   </boundary-data>
+variables such as the cost of traveling to the vendor's location and time costs. These costs are often higher than simply the base price of the goods. Customers are also presented with substitute and complementary goods. For example, after searching for one brand, customers may be shown alternate brands or may be shown related products.    </p>
+    <p id="p-41" num="41">
+      <boundary-data type="line-number">20    </boundary-data>
+Customers can select the goods they would like to purchase and may add them to a shopping list along with the quantity of each of the goods they would like to purchase. Customers may also select the specific vendor locations at which they would like to purchase the goods or let the system determine this for them. For example, many customers have a preferred hair stylist and would not like to select a haircut at a different barber or salon. However, many <part-num-ref name="different barber or salon. However, many">25</part-num-ref>
+   customers would be willing to purchase goods from any vendor who can provide the goods at <page-break num="12"/>
+      <boundary-data type="header">
+        <confidence value="88">11</confidence>
+      </boundary-data>
+the lowest total cost. In this instance, the customer asks the system to optimize the shopping trip to determine how the goods could be purchased for the lowest total cost.    </p>
+    <p id="p-42" num="42">The system uses numerous variables to determine the optimal means of purchasing the goods <boundary-data type="line-number">5   </boundary-data>
+for the lowest total cost. The optimization method is comprised of several steps:    </p>
+    <p id="p-43" num="43">
+      <confidence value="2">"</confidence>
+ Selection of the vendors and location (amongst the ones not eliminated by the customer) with preference given to those with:    </p>
+    <p id="p-44" num="44">o Inventory remaining (for a product) <boundary-data type="line-number">10             </boundary-data>
+o  Availability (for a service) o Lowest prices (with discounts and taxes factored in) o Closest proximity to the customer's current location and to other vendors o If the vendor and its locations are on a preferred list o Vendors with high customer ratings <boundary-data type="line-number">15          </boundary-data>
+      <confidence value="2">-</confidence>
+ Public transportation availability (if the customer cannot provide transportation) <confidence value="2">"</confidence>
+ Calculation of the quantities of the goods that should be purchased from each vendor which is determined by:    </p>
+    <p id="p-45" num="45">o Price divided by units (weight, quantity, etc.) if possible, to determine the cost per unit (which makes comparisons easier) <boundary-data type="line-number">20             </boundary-data>
+o  Amount of the goods the customer would like to purchase o Availability of the goods in the size and volume at each vendor location <confidence value="2">"</confidence>
+ Determination of the order in which the vendors should be visited which is determined by:    </p>
+    <p id="p-46" num="46">o How close the vendor locations are to each other <part-num-ref name="vendor locations are to each other">25</part-num-ref>
+             o  Customer's preferred routes <page-break num="13"/>
+      <boundary-data type="header">
+        <confidence value="88">12</confidence>
+      </boundary-data>
+o Estimated time it takes to travel between locations <confidence value="1">e</confidence>
+ Computation of the recommended routes by which the vendors should be visited which is determined by:    </p>
+    <p id="p-47" num="47">o Commonly used linear programming and routing algorithms <boundary-data type="line-number">
+        <confidence value="8">5</confidence>
+             </boundary-data>
+      <confidence value="1">"</confidence>
+  Display of the vendor locations, total cost of purchases at each location, total trip time, and routes by which the customer should travel Collectively, the outputs from the system are considered a recommended "shopping trip." Each shopping trip has a base cost (the price of only the goods) and a total cost associated <boundary-data type="line-number">10   </boundary-data>
+with it.  The shopping trip with the lowest total cost is considered the primary recommendation to the customer. Customers can chose alternate shopping trips which may not save as much money but may be favorable for any number of personal reasons.    </p>
+    <p id="p-48" num="48">In one embodiment of the system, the total cost of the shopping trip can change in real-time if <boundary-data type="line-number">15   </boundary-data>
+any of the variables change such as traffic conditions. Variables are continually evaluated by the system and if the total cost of any recommended shopping trip changes, the customer can be alerted and alternate recommendations provided. For example, if a vendor has run out of a product, a hair stylist has a backlog of customers, or traffic congestion develops, then the customer can be alerted and provided with alternate solutions in real-time. This alert can <boundary-data type="line-number">20   </boundary-data>
+come in many forms. In one embodiment, the alert is presented on the customer's navigation system and an updated shopping list is presented. In another embodiment, the customer receives an email or text message to his or her mobile phone.    </p>
+    <p id="p-49" num="49">Once customers have completed their trip, they can input into the system which of the items <part-num-ref name="items">25</part-num-ref>
+    on their shopping list were actually purchased, how much was purchased, and their <page-break num="14"/>
+      <boundary-data type="header">
+        <confidence value="88">13</confidence>
+      </boundary-data>
+satisfaction with the vendors they patronized. This data can be used to further provide recommendations in the future.    </p>
+    <heading id="h-11">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
+    <p id="p-50" num="50">
+      <boundary-data type="line-number">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+ FIGURE 1 is an input system and screen display that allows customers to provide personal shopping preferences.    </p>
+    <p id="p-51" num="51">FIGURE 2 is a system and screen display that allows customers to search for particular types <boundary-data type="line-number">10   </boundary-data>
+of goods in the customer's local area.    </p>
+    <p id="p-52" num="52">FIGURE 3 is a graphical user interface display screen that shows a list of vendors selling specific goods in the customer's local area.</p>
+    <p id="p-53" num="53">
+      <boundary-data type="line-number">15   </boundary-data>
+FIGURE 4 is of a display screen that shows a customer's optimized shopping trip that has been based on customer preferences, data on goods and vendors, and location data.    </p>
+    <p id="p-54" num="54">FIGURE 5 is a system output integrated into a navigation or mapping system to provide customers with a visual means of making an optimized shopping trip.</p>
+    <p id="p-55" num="55">
+      <boundary-data type="line-number">
+        <confidence value="88">20</confidence>
+      </boundary-data>
+     </p>
+    <heading id="h-12">DETAILED DESCRIPTION OF THE DRAWINGS</heading>
+    <p id="p-56" num="56">FIGURE 1 is an illustration of an input system and screen display [100] that allows <part-num-ref name="input system and screen display [100] that allows">25</part-num-ref>
+    customers to enter personal shopping preferences. In implementing the system, the customer <page-break num="15"/>
+      <boundary-data type="header">
+        <confidence value="88">14</confidence>
+      </boundary-data>
+provides an estimated value of one hour [101] of his or her time. This information is used to determine how much time a customer should spend shopping for goods. For example, customers with high time values should spend less time traveling from one vendor to another if it means small savings.    </p>
+    <p id="p-57" num="57">
+      <boundary-data type="line-number">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+ Customers also specify how far they are willing to drive and walk [102] during a shopping trip. Older shoppers, for example, may decide that walking more than one half mile is too difficult.    </p>
+    <p id="p-58" num="58">
+      <boundary-data type="line-number">10   </boundary-data>
+The default starting location [103] may be a city and state combination or a zip code. If the system is part of a larger navigation system, then customers may not even need to provide this information. The default starting location might be a customer's home address with street information. This data point will be used to determine the origins of shopping trips.    </p>
+    <p id="p-59" num="59">
+      <boundary-data type="line-number">15   </boundary-data>
+Preferred vendors [104] are given preference when determining which locations should be recommended to customers. Disliked vendors [105] are not included in the recommended shopping trips or are given low priority.    </p>
+    <p id="p-60" num="60">Customers can optionally specify what discount cards, membership cards, rebates or coupons <boundary-data type="line-number">20    </boundary-data>
+[106] they hold. These are applied and reduce the total costs to the customer.    </p>
+    <p id="p-61" num="61">Customers are also asked to specify what kinds of automobiles they drive [107] if any. This will be used to determine how much fuel they consume per mile. If an automobile consumes a large quantity of fuel, then the system will give higher priority to vendors in close <part-num-ref name="system will give higher priority to vendors in close">25</part-num-ref>
+    proximity to the customer's origin. In addition, automobiles depreciate for each mile driven.    </p>
+    <boundary-data type="header">
+      <confidence value="88">15</confidence>
+    </boundary-data>
+    <p id="p-62" num="62">
+      <page-break num="16"/>
+Each automobile make, model and year depreciates a different amount and this will be used by the shopping trip optimization engine.    </p>
+    <p id="p-63" num="63">Finally, customers may specify that they are willing to provide public transportation [108].</p>
+    <p id="p-64" num="64">
+      <boundary-data type="line-number">5   </boundary-data>
+The system will take public transit costs, routes and schedules into consideration when optimizing the shopping trip. This variable is important in markets such as New York or Chicago where customers often do not own automobiles and may have to walk or use taxis, buses or subways.    </p>
+    <p id="p-65" num="65">
+      <boundary-data type="line-number">10   </boundary-data>
+FIGURE 2 is an illustration of a screen display of the system that allows customers to search for particular goods [200]. Customers can enter in a search term and their location [201].    </p>
+    <p id="p-66" num="66">Products and services that are sold in the local area specified (and within the radius specified by the customer preferences) are found and displayed to the customer [202]. The search may be conducted on the Internet using an available search engine.</p>
+    <p id="p-67" num="67">
+      <boundary-data type="line-number">
+        <confidence value="88">15</confidence>
+      </boundary-data>
+ For example, consider that the customer searches for "haircut." Several matches might be returned including, "women's haircut" and "haircut, shampoo and blow-dry." The high, low and average price of the service is shown [203]. Customers can then optionally request a specific list of vendors who perform that service [204]. The system also may recommend <boundary-data type="line-number">20    </boundary-data>
+which vendor is ideal.    </p>
+    <p id="p-68" num="68">Customers also are presented with complementary goods [205] which the customer may also want to consider. The system also presents alternative goods [206] which may provide more value to the customer.</p>
+    <p id="p-69" num="69">
+      <confidence value="88">25</confidence>
+ <page-break num="17"/>
+      <boundary-data type="header">
+        <confidence value="88">16</confidence>
+      </boundary-data>
+FIGURE 3 is a screen display used in the system showing a list of vendors who are selling the selected goods in the local area [300]. The goods the customer is trying to locate is shown at the top of the display [301]. The price range (low to high) also is shown [302]. The vendors carrying the goods are shown in the first column [303]. In addition, the system also <boundary-data type="line-number">5   </boundary-data>
+recommends various vendors based on customer feedback ratings or ratings obtained from a third party [304]. These ratings are based on how vendors are perceived in terms of product quality, convenience, selection, average prices and customer service.    </p>
+    <p id="p-70" num="70">In one embodiment of the system the current price of the specified goods is displayed [305].</p>
+    <p id="p-71" num="71">
+      <boundary-data type="line-number">10   </boundary-data>
+In another embodiment, the average price of the goods over time may be shown. The distance to the vendor's location [306] is also shown. A location may be the street address of a store, a location in a shopping mall, or some other location designation. The distance to the location [307] is provided to the customer so they understand how far they must travel from their default location (or origin) to the vendor. In addition, the availability of the goods is <boundary-data type="line-number">15   </boundary-data>
+displayed [308]. Availability might include the number of units of the product in stock or the time slots available if it is a service. The rating [309] is a customer feedback rating such as the number of stars a vendor has received. Customers can add a specific vendor to their shopping list [310] if they have a strong desire to purchase the goods from that vendor. They can also specify the quantity of the goods they wish to add to their list. Customers optionally <boundary-data type="line-number">20   </boundary-data>
+can allow the system to choose the vendor for them.    </p>
+    <p id="p-72" num="72">Some customers may have preferred vendors they have specified when inputting their customer preferences. In this embodiment of the system, non-preferred vendors can be left out of the vendor list [311<confidence value="88">].</confidence>
+    </p>
+    <p id="p-73" num="73">
+      <confidence value="88">25</confidence>
+ <page-break num="18"/>
+      <boundary-data type="header">
+        <confidence value="88">17</confidence>
+      </boundary-data>
+Thus, the customer may create a virtual shopping list by use of the system and method of the present invention.    </p>
+    <p id="p-74" num="74">Customers can also specify if they are willing to travel farther [312] than originally specified.</p>
+    <p id="p-75" num="75">
+      <boundary-data type="line-number">5   </boundary-data>
+Choosing this option may allow the system to find additional vendors carrying the goods.    </p>
+    <p id="p-76" num="76">FIGURE 4 shows a customer's optimized shopping trip [400] in a screen display produced by the system. Customers may decide to use the first trip given to them or can request an additional trip [401]. When requesting an additional trip, customers may decide to change <boundary-data type="line-number">10   </boundary-data>
+one or more of the variables. An example would include changing the distance the customer is willing to travel or the addition of a time constraint.    </p>
+    <p id="p-77" num="77">The customer is presented with a savings estimate [402], which is the difference between the total cost [412] and the average cost of the goods at all vendors in the local area. For <boundary-data type="line-number">15   </boundary-data>
+example, if the optimized cost of the goods is $100.00 and the average cost of the same goods in the local area is $125.00, then the estimated savings would be $25.00. This mechanism provides a benchmark that gives customers an idea of how much value the system is providing to them. Customers also can see the estimated time required to complete the shopping trip [403].    </p>
+    <p id="p-78" num="78">
+      <boundary-data type="line-number">
+        <confidence value="88">20</confidence>
+      </boundary-data>
+ In one embodiment of the system, the optimized shopping trip lists goods in the order they should be purchased <confidence value="5">[</confidence>
+404<confidence value="5">]</confidence>
+. The vendor [405] carrying the goods and [406] and location of the vendor are shown. The distance [407] may also be provided.    </p>
+    <boundary-data type="header">
+      <confidence value="88">18</confidence>
+    </boundary-data>
+    <p id="p-79" num="79">
+      <page-break num="19"/>
+The purchase cost of the goods [410] is calculated using the price [408] and quantity [409].    </p>
+    <p id="p-80" num="80">The total cost of the goods [411] is calculated using the method described above and will almost always be greater than the purchase price.</p>
+    <p id="p-81" num="81">
+      <boundary-data type="line-number">5   </boundary-data>
+Customers are shown totals [412] for columns such as distance, purchase cost and total cost.    </p>
+    <p id="p-82" num="82">Also, in an embodiment of the invention, customers can chose to map [413] the shopping trip on a graphical display. Customers are given the option to travel farther [414] in order to save even more money if such savings are applicable. Finally, because the shopping trip may be updated in real-time, a timestamp [415] is provided.</p>
+    <p id="p-83" num="83">
+      <boundary-data type="line-number">
+        <confidence value="88">10</confidence>
+      </boundary-data>
+ FIGURE 5 shows an embodiment of the system in which a shopping trip is integrated into a mapping or navigation system [500]. At the top of the display is the starting address and ending address [501] as well as the estimated distance and trip time. The customer's current location [502] is shown as well as the proposed travel route [503]. Along the route are the <boundary-data type="line-number">15   </boundary-data>
+vendor locations [504] that the system recommends the user patronize. In this embodiment of the invention, the proposed stops are numbered. Customers are able to get more information on a location [505] by clicking on the location, tapping on a screen, using spoken commands or by another known method. For example, a navigation system may use voice recognition to allow a customer to request more information such as the exact street address <boundary-data type="line-number">20   </boundary-data>
+or hours of operation. The system could then use an artificial voice to speak the information back to the customer.    </p>
+    <p id="p-84" num="84">The system may also present the shopping list [506] to the customer. The list includes the goods <confidence value="5">[</confidence>
+507] in the order they should be purchased. Each listing would specify the location of <part-num-ref name="location of">25</part-num-ref>
+   the goods, the estimated time it would take to purchase the goods, its purchase cost and total <page-break num="20"/>
+      <boundary-data type="header">
+        <confidence value="88">19</confidence>
+      </boundary-data>
+costs. The shopping list would also present totals [508] for the purchase costs and total costs.    </p>
+    <p id="p-85" num="85">In this embodiment of the system, the customer has the option to print [509<confidence value="5">]</confidence>
+ the map and shopping list recommendations.    </p>
+    <p id="p-86" num="86">
+      <boundary-data type="line-number">5   </boundary-data>
+Various changes and modifications may be effected by one skilled in the art without departing from the spirit and scope of the invention. For example, the invention could be used in connection with services, and the term "goods" should be understood to include both goods and services.    </p>
+    <p id="p-87" num="87">
+      <boundary-data type="line-number">
+        <confidence value="88">10</confidence>
+      </boundary-data>
+ <confidence value="88">15</confidence>
+ <part-num-ref name="">
+        <confidence value="88">20</confidence>
+      </part-num-ref>
+     </p>
+  </description>
+</us-patent-application>
+

applicant/11799217.xml

@@ -0,0 +1,397 @@
+<?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>11799217</doc-number>
+        <date>2007-04-30</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <heading id="h-1">COVER PAGE</heading>
+    <p id="p-1" num="1">Hewlett-Packard Com<confidence value="5885">pany</confidence>
+ Docket Number:    </p>
+    <p id="p-2" num="2">200603280-1 Title:</p>
+    <heading id="h-2">TAMPER INDICATION SYSTEM AND METHOD FOR A COMPUTING SYSTEM</heading>
+    <p id="p-3" num="3">Inventor:</p>
+    <p id="p-4" num="4">Mark R. SCHILLER <page-break num="2"/>
+      <boundary-data type="header">200603280-1</boundary-data>
+      <boundary-data type="header">
+        <confidence value="8">1</confidence>
+      </boundary-data>
+    </p>
+    <heading id="h-3">TAMPER INDICATION SYSTEM AND METHOD FOR A COMPUTING SYSTEM</heading>
+    <heading id="h-4">BACKGROUND</heading>
+    <p id="p-5" num="5">[0001]     When passing through security checkpoints, such as security checkpoints at airports, computing systems are often subjected to a "power-on" test that is intended to ascertain whether the computing system is a legitimately operating computing system.</p>
+    <p id="p-6" num="6">However, such tests are often incomplete from a security standpoint. For example, a digital media drive (DMD) may have been removed from a notebook computer and replaced with a case holding contraband, but a "power-on" test is unlikely to uncover such a replacement.</p>
+    <p id="p-7" num="7">Further, tamper-evident adhesive labels can be used to indicate removal of parts from a computing system or an opening of the case, but replacement labels can be applied in place of the damaged originals in order to erase the evidence of tampering.</p>
+    <heading id="h-5">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
+    <p id="p-8" num="8">[0002]     For a more complete understanding of the present application, the objects and advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:</p>
+    <p id="p-9" num="9">[0003]     FIGURE 1 is a diagram illustrating an embodiment of a tamper indication system for a computing system;</p>
+    <p id="p-10" num="10">[0004]     FIGURE 2 is a diagram illustrating an embodiment of a tamper indication method for a computing system; and [0005]     FIGURE 3 is another diagram illustrating an embodiment of a tamper indication method for a computing system.</p>
+    <heading id="h-6">DETAILED DESCRIPTION OF THE DRAWINGS</heading>
+    <p id="p-11" num="11">[0006]     FIGURE 1 is a diagram illustrating an embodiment of a tamper indication system <part-num-ref name="tamper indication system">10.</part-num-ref>
+ In the embodiment illustrated in FIGURE 1, tamper indication system <part-num-ref name="embodiment illustrated in FIGURE 1, tamper indication system">10</part-num-ref>
+ is utilized to determine whether tampering has occurred for a computing system <part-num-ref name="computing system">12.</part-num-ref>
+ In F<confidence value="5">I</confidence>
+GURE 1, tamper indication system <part-num-ref name="computing system 12. In FIGURE 1, tamper indication system">10</part-num-ref>
+ comprises a monitoring system <part-num-ref name="monitoring system">14</part-num-ref>
+ coupled to computing system <part-num-ref name="coupled to computing system">12</part-num-ref>
+ to ascertain whether computing system <part-num-ref name="to ascertain whether computing system">12</part-num-ref>
+ has been subjected to physical tampering. Computing system <part-num-ref name="has been subjected to physical tampering. Computing system">12</part-num-ref>
+ and/or monitoring system <part-num-ref name="and/or monitoring system">14</part-num-ref>
+ may comprise any type of computing device such as, but not limited to, a notebook computer, tablet computer, a media player, a gaming device, a personal digital assistant (PDA), a desktop computer, and a printer.    </p>
+    <boundary-data type="header">200603280-1</boundary-data>
+    <boundary-data type="header">
+      <confidence value="8">2</confidence>
+    </boundary-data>
+    <p id="p-12" num="12">
+      <page-break num="3"/>
+[0007]     In the embodiment illustrated in FIGURE 1, computing system <part-num-ref name="embodiment illustrated in FIGURE 1, computing system">12</part-num-ref>
+ comprises a firmware <part-num-ref name="firmware">20,</part-num-ref>
+ a firmware <part-num-ref name="firmware">22,</part-num-ref>
+ a tamper sensor <part-num-ref name="tamper sensor">24,</part-num-ref>
+ a protected asset <part-num-ref name="protected asset">26,</part-num-ref>
+ an input/output port <part-num-ref name="input/output port">28,</part-num-ref>
+ central processing unit (CPU) <part-num-ref name="input/output port 28, central processing unit (CPU)">30,</part-num-ref>
+ a memory <part-num-ref name="memory">32</part-num-ref>
+ and a power supply <part-num-ref name="power supply">34.</part-num-ref>
+ In FIGURE 1, firmware <part-num-ref name="power supply 34. In FIGURE 1, firmware">20</part-num-ref>
+ is coupled to at least CPU <part-num-ref name="is coupled to at least CPU">30,</part-num-ref>
+ memory <part-num-ref name="is coupled to at least CPU 30, memory">32,</part-num-ref>
+ firmware <part-num-ref name="is coupled to at least CPU 30, memory 32, firmware">22,</part-num-ref>
+ tamper sensor <part-num-ref name="is coupled to at least CPU 30, memory 32, firmware 22, tamper sensor">24</part-num-ref>
+ and power supply <part-num-ref name="and power supply">34.</part-num-ref>
+ Firmware <part-num-ref name="and power supply 34. Firmware">20</part-num-ref>
+ is configured to provide boot-up and/or pre-boot-up functionality for computing system <part-num-ref name="is configured to provide boot-up and/or pre-boot-up functionality for computing system">12.</part-num-ref>
+ For example, in some embodiments, firmware <part-num-ref name="is configured to provide boot-up and/or pre-boot-up functionality for computing system 12. For example, in some embodiments, firmware">20</part-num-ref>
+ executes initial power-on instructions such as configuring CPU <part-num-ref name="executes initial power-on instructions such as configuring CPU">30</part-num-ref>
+ and causing CPU <part-num-ref name="and causing CPU">30</part-num-ref>
+ to begin executing instructions at a predetermined time. Firmware <part-num-ref name="predetermined time. Firmware">20</part-num-ref>
+ may comprise a basic input/output system (BIOS), an Extensible Firmware Interface (E<confidence value="66">FI</confidence>
+) or a Uniform EFI (UEFI). However<confidence value="5">,</confidence>
+ it should be understood that firmware <part-num-ref name="Uniform EFI (UEFI). However, it should be understood that firmware">20</part-num-ref>
+ may comprise other systems or devices for providing boot-up and/or pre-boot-up functionality. Memory <part-num-ref name="may comprise other systems or devices for providing boot-up and/or pre-boot-up functionality. Memory">32</part-num-ref>
+ may comprise volatile memory, non- volatile memory and permanent storage. In FIGURE 1, memory <part-num-ref name="may comprise volatile memory, non- volatile memory and permanent storage. In FIGURE 1, memory">32</part-num-ref>
+ comprises an instance of an operating system (OS) <part-num-ref name="operating system (OS)">36</part-num-ref>
+ that may be loaded and/or otherwise executed by CPU <part-num-ref name="that may be loaded and/or otherwise executed by CPU">30.</part-num-ref>
+ In the embodiment illustrated in FIGURE 1, computing system <part-num-ref name="embodiment illustrated in FIGURE 1, computing system">12</part-num-ref>
+ is shown as comprising a single CPU <part-num-ref name="single CPU">30,</part-num-ref>
+ although it should be understood that a greater quantity of CPUs may be used. Port <part-num-ref name="greater quantity of CPUs may be used. Port">28</part-num-ref>
+ may comprise any type of wired or wireless interface for enabling communications between computing system <part-num-ref name="may comprise any type of wired or wireless interface for enabling communications between computing system">12</part-num-ref>
+ and monitoring system <part-num-ref name="and monitoring system">14.</part-num-ref>
+    </p>
+    <p id="p-13" num="13">[0008]     Firmware 20 is configured to determine a state of sensor <part-num-ref name="state of sensor">24</part-num-ref>
+ (e.g. whether sensor <part-num-ref name="whether sensor">24</part-num-ref>
+ is in a state signifying a tamper event occurred) during boot-up of computing system <part-num-ref name="tamper event occurred) during boot-up of computing system">12.</part-num-ref>
+ Sensor <part-num-ref name="tamper event occurred) during boot-up of computing system 12. Sensor">24</part-num-ref>
+ is coupled, mechanically and/or electrically, to protected asset <part-num-ref name="is coupled, mechanically and/or electrically, to protected asset">26,</part-num-ref>
+ thereby enabling sensor <part-num-ref name="is coupled, mechanically and/or electrically, to protected asset 26, thereby enabling sensor">24</part-num-ref>
+ to sense and/or otherwise detect a change to and/or tampering of protected asset <part-num-ref name="change to and/or tampering of protected asset">26.</part-num-ref>
+ Tamper sensor <part-num-ref name="change to and/or tampering of protected asset 26. Tamper sensor">24</part-num-ref>
+ may be disposed in or coupled to computing system <part-num-ref name="may be disposed in or coupled to computing system">12.</part-num-ref>
+ Protected asset <part-num-ref name="may be disposed in or coupled to computing system 12. Protected asset">26</part-num-ref>
+ may be disposed in or externally coupled to computing system <part-num-ref name="may be disposed in or externally coupled to computing system">12.</part-num-ref>
+ For example, protected asset <part-num-ref name="may be disposed in or externally coupled to computing system 12. For example, protected asset">26</part-num-ref>
+ may comprise a digital media drive (DMD), a battery, an access panel, a circuit, an input/output device, or any other device where it is desired to ascertain whether the particular asset has been subject to tampering. For example, in some embodiments, protected asset <part-num-ref name="particular asset has been subject to tampering. For example, in some embodiments, protected asset">26</part-num-ref>
+ comprises a DMD <part-num-ref name="DMD">40</part-num-ref>
+ and sensor <part-num-ref name="and sensor">24</part-num-ref>
+ comprises a thin wire or optical fiber configured to break if protected asset <part-num-ref name="thin wire or optical fiber configured to break if protected asset">26</part-num-ref>
+ (e.g., DMD <part-num-ref name="DMD">40)</part-num-ref>
+ is removed from computing system <part-num-ref name="is removed from computing system">12.</part-num-ref>
+ By attempting to sense a current, voltage, electrical resistance or optical signal associated with sensor <part-num-ref name="current, voltage, electrical resistance or optical signal associated with sensor">24,</part-num-ref>
+ firmware <part-num-ref name="current, voltage, electrical resistance or optical signal associated with sensor 24, firmware">20</part-num-ref>
+ is configured to determine whether sensor <part-num-ref name="is configured to determine whether sensor">24</part-num-ref>
+ has been broken, thereby indicating that protected asset <part-num-ref name="has been broken, thereby indicating that protected asset">26</part-num-ref>
+ may have been removed and/or replaced. It should be understood that sensor <part-num-ref name="may have been removed and/or replaced. It should be understood that sensor">24</part-num-ref>
+ may comprise any type of sensor with a state determinable by firmware <part-num-ref name="state determinable by firmware">20,</part-num-ref>
+ such as an electrical switch, a magnetic switch, a proximity indicator, and an <page-break num="4"/>
+      <boundary-data type="header">200603280-1</boundary-data>
+      <boundary-data type="header">
+        <confidence value="8">3</confidence>
+      </boundary-data>
+environmental sensor. It should be further understood that other forms of tampering, including opening, inserting a device, substance or signal, and causing changes in configuration or operation, may also be detected by embodiments of sensor <part-num-ref name="device, substance or signal, and causing changes in configuration or operation, may also be detected by embodiments of sensor">24.</part-num-ref>
+    </p>
+    <p id="p-14" num="14">[0009]    In the embodiment illustrated in FIGURE 1, firmware <part-num-ref name="embodiment illustrated in FIGURE 1, firmware">20</part-num-ref>
+ is further configured to report the state of sensor <part-num-ref name="state of sensor">24</part-num-ref>
+ to monitoring system <part-num-ref name="to monitoring system">14</part-num-ref>
+ via port <part-num-ref name="via port">28,</part-num-ref>
+ thereby providing tamper indication for protected asset <part-num-ref name="via port 28, thereby providing tamper indication for protected asset">26</part-num-ref>
+ to a system external to computing system <part-num-ref name="system external to computing system">12.</part-num-ref>
+    </p>
+    <p id="p-15" num="15">In some embodiments, firmware 20 is configured to report and/or otherwise store an indication of the state of sensor <part-num-ref name="state of sensor">24</part-num-ref>
+ to memory <part-num-ref name="to memory">32,</part-num-ref>
+ and CPU <part-num-ref name="to memory 32, and CPU">30</part-num-ref>
+ is configured to report the state of sensor <part-num-ref name="state of sensor">24</part-num-ref>
+ from memory <part-num-ref name="from memory">32</part-num-ref>
+ to monitoring system <part-num-ref name="to monitoring system">14</part-num-ref>
+ via port <part-num-ref name="via port">28.</part-num-ref>
+ In the embodiment illustrated in FIGURE 1, firmware <part-num-ref name="embodiment illustrated in FIGURE 1, firmware">20</part-num-ref>
+ comprises a sensor reader <part-num-ref name="sensor reader">50</part-num-ref>
+ for reading the state of sensor <part-num-ref name="state of sensor">24.</part-num-ref>
+ In FIGURE 1, firmware <part-num-ref name="state of sensor 24. In FIGURE 1, firmware">20</part-num-ref>
+ also comprises a trusted memory <part-num-ref name="trusted memory">52</part-num-ref>
+ having a boot block <part-num-ref name="boot block">54,</part-num-ref>
+ report logic <part-num-ref name="boot block 54, report logic">56</part-num-ref>
+ for generating a report <part-num-ref name="report">60</part-num-ref>
+ indicating the state of sensor <part-num-ref name="state of sensor">24,</part-num-ref>
+ and a previously-recorded measurement <part-num-ref name="previously-recorded measurement">62</part-num-ref>
+ for comparison with a measurement from sensor reader <part-num-ref name="measurement from sensor reader">50.</part-num-ref>
+ As used herein, "trust" or "trusted" means the expectation of consistent operation within a predefined set of rules that is enforced by computing hardware and/or software, such as the definition of "trust" as set forth in the TCG Specification Architecture Overview Specification, Revision 1.2 (Trusted Computing Group, 2004). For example, ensuring that the contents of a certain section of memory, such as memory <part-num-ref name="certain section of memory, such as memory">52</part-num-ref>
+ in firmware <part-num-ref name="in firmware">20,</part-num-ref>
+ contains only information produced by a previously-identified source, defined as a trusted source, enables the trust of that certain section of memory. Sensor reader <part-num-ref name="trust of that certain section of memory. Sensor reader">50</part-num-ref>
+ may either be coupled to or within trusted memory <part-num-ref name="may either be coupled to or within trusted memory">52</part-num-ref>
+ to report the measurement of sensor <part-num-ref name="measurement of sensor">24</part-num-ref>
+ to logic <part-num-ref name="to logic">56.</part-num-ref>
+ Boot block <part-num-ref name="to logic 56. Boot block">54,</part-num-ref>
+ residing in trusted memory <part-num-ref name="to logic 56. Boot block 54, residing in trusted memory">52,</part-num-ref>
+ is generally the initial logic executed by firmware <part-num-ref name="initial logic executed by firmware">20</part-num-ref>
+ when computing system <part-num-ref name="when computing system">12</part-num-ref>
+ is powered on, restarted and/or reset. In some embodiments, boot block <part-num-ref name="is powered on, restarted and/or reset. In some embodiments, boot block">54</part-num-ref>
+ is trusted logic because boot block <part-num-ref name="is trusted logic because boot block">54</part-num-ref>
+ is entirely contained within trusted memory <part-num-ref name="is entirely contained within trusted memory">52.</part-num-ref>
+    </p>
+    <p id="p-16" num="16">[0010]    In the embodiment illustrated in FIGURE 1, firmware <part-num-ref name="embodiment illustrated in FIGURE 1, firmware">22</part-num-ref>
+ is used to render report <part-num-ref name="is used to render report">60</part-num-ref>
+ tamper-evident. For example, in the embodiment illustrated in FIGURE 1, firmware <part-num-ref name="embodiment illustrated in FIGURE 1, firmware">22</part-num-ref>
+ comprises cryptographic logic <part-num-ref name="comprises cryptographic logic">80</part-num-ref>
+ and an encryption key <part-num-ref name="encryption key">82.</part-num-ref>
+ In some embodiments, cryptographic logic <part-num-ref name="encryption key 82. In some embodiments, cryptographic logic">80</part-num-ref>
+ provides cryptographic capability for computing system <part-num-ref name="provides cryptographic capability for computing system">12</part-num-ref>
+ by performing digital signature, encryption, decryption and/or hashing functions. In some embodiments, encryption key <part-num-ref name="by performing digital signature, encryption, decryption and/or hashing functions. In some embodiments, encryption key">82</part-num-ref>
+ comprises a public encryption key suitable for use in digitally signing and/or encrypting report <part-num-ref name="public encryption key suitable for use in digitally signing and/or encrypting report">60.</part-num-ref>
+ In some embodiments encryption key <part-num-ref name="public encryption key suitable for use in digitally signing and/or encrypting report 60. In some embodiments encryption key">82</part-num-ref>
+ is stored in firmware <part-num-ref name="is stored in firmware">20</part-num-ref>
+ and/or memory <part-num-ref name="and/or memory">32.</part-num-ref>
+ In some embodiments, firmware <part-num-ref name="and/or memory 32. In some embodiments, firmware">22</part-num-ref>
+ comprises a Trusted Platform Module (TPM).    </p>
+    <p id="p-17" num="17">However, it should be understood that in some embodiments, the cryptographic functions <page-break num="5"/>
+      <boundary-data type="header">200603280-1</boundary-data>
+      <boundary-data type="header">
+        <confidence value="8">4</confidence>
+      </boundary-data>
+identified in the illustrated embodiment as provided by firmware <part-num-ref name="illustrated embodiment as provided by firmware">22</part-num-ref>
+ may be provided instead by firmware <part-num-ref name="may be provided instead by firmware">20.</part-num-ref>
+    </p>
+    <p id="p-18" num="18">[0011]     In the embodiment illustrated in FIGURE 1, report <part-num-ref name="embodiment illustrated in FIGURE 1, report">60</part-num-ref>
+ comprises a digital signature <part-num-ref name="digital signature">90,</part-num-ref>
+ which renders alteration of and/or tampering with the contents of report <part-num-ref name="contents of report">60</part-num-ref>
+ evident when digital signature <part-num-ref name="evident when digital signature">90</part-num-ref>
+ is verified. In some embodiments, report <part-num-ref name="is verified. In some embodiments, report">60</part-num-ref>
+ may be encrypted in place of or in addition to being digitally signed. Digital signature <part-num-ref name="may be encrypted in place of or in addition to being digitally signed. Digital signature">90</part-num-ref>
+ comprises an alphanumeric sequence generated by firmware <part-num-ref name="alphanumeric sequence generated by firmware">22,</part-num-ref>
+ thereby providing a basis for verifying the integrity of report <part-num-ref name="integrity of report">60.</part-num-ref>
+ For example, digital signature <part-num-ref name="integrity of report 60. For example, digital signature">90</part-num-ref>
+ may comprise a hash value <part-num-ref name="hash value">92</part-num-ref>
+ generated for report <part-num-ref name="generated for report">60.</part-num-ref>
+    </p>
+    <p id="p-19" num="19">Hash value 92 is a number or value uniquely representing the contents of report <part-num-ref name="contents of report">60.</part-num-ref>
+ If report <part-num-ref name="contents of report 60. If report">60</part-num-ref>
+ were altered after digital signature <part-num-ref name="were altered after digital signature">90</part-num-ref>
+ was created, then when report <part-num-ref name="was created, then when report">60</part-num-ref>
+ is subjected to a hash function at a later time, such as, by monitoring system <part-num-ref name="later time, such as, by monitoring system">14,</part-num-ref>
+ the newly calculated hash value will not match the value <part-num-ref name="value">92</part-num-ref>
+ reported in digital signature <part-num-ref name="reported in digital signature">90.</part-num-ref>
+ Further, encryption of report <part-num-ref name="reported in digital signature 90. Further, encryption of report">60</part-num-ref>
+ and/or a portion of digital signature <part-num-ref name="portion of digital signature">90</part-num-ref>
+ using encryption key <part-num-ref name="using encryption key">82</part-num-ref>
+ enables integrity verification of report <part-num-ref name="enables integrity verification of report">60.</part-num-ref>
+    </p>
+    <p id="p-20" num="20">If report 60 and/or digital signature <part-num-ref name="and/or digital signature">90</part-num-ref>
+ were altered after encryption, then a decryption process performed by monitoring system <part-num-ref name="decryption process performed by monitoring system">14</part-num-ref>
+ would return an invalid result that did not match an expected result.    </p>
+    <p id="p-21" num="21">[0012]     In the embodiment illustrated in FIGURE 1, monitoring system <part-num-ref name="embodiment illustrated in FIGURE 1, monitoring system">14</part-num-ref>
+ comprises verification logic <part-num-ref name="comprises verification logic">100</part-num-ref>
+ configured to verify the integrity of report <part-num-ref name="integrity of report">60</part-num-ref>
+ and further to determine the state of sensor <part-num-ref name="state of sensor">24</part-num-ref>
+ from report <part-num-ref name="from report">60.</part-num-ref>
+ In some embodiments, verification logic <part-num-ref name="from report 60. In some embodiments, verification logic">100</part-num-ref>
+ is configured to hash and decrypt report <part-num-ref name="is configured to hash and decrypt report">60</part-num-ref>
+ and compare a hash value <part-num-ref name="hash value">102</part-num-ref>
+ calculated by verification logic <part-num-ref name="calculated by verification logic">100</part-num-ref>
+ with hash value <part-num-ref name="with hash value">92</part-num-ref>
+ calculated by firmware <part-num-ref name="calculated by firmware">22</part-num-ref>
+ and reported as part of digital signature <part-num-ref name="and reported as part of digital signature">90.</part-num-ref>
+ In the illustrated embodiment, monitoring system <part-num-ref name="illustrated embodiment, monitoring system">14</part-num-ref>
+ is coupled to a network <part-num-ref name="network">110,</part-num-ref>
+ thereby enabling monitoring system <part-num-ref name="network 110, thereby enabling monitoring system">14</part-num-ref>
+ to provide a notification or alert to a remote system <part-num-ref name="remote system">120</part-num-ref>
+ regarding the tampering status of computing system <part-num-ref name="tampering status of computing system">12.</part-num-ref>
+ In some embodiments, verification logic <part-num-ref name="tampering status of computing system 12. In some embodiments, verification logic">100</part-num-ref>
+ may reside in remote system <part-num-ref name="may reside in remote system">120.</part-num-ref>
+    </p>
+    <p id="p-22" num="22">[0013]     In operation, for example, in response to a user powering up computing system <part-num-ref name="user powering up computing system">12,</part-num-ref>
+ power supply <part-num-ref name="user powering up computing system 12, power supply">34</part-num-ref>
+ provides power to at least firmware <part-num-ref name="provides power to at least firmware">20.</part-num-ref>
+ Firmware <part-num-ref name="provides power to at least firmware 20. Firmware">20</part-num-ref>
+ begins executing instructions in boot block <part-num-ref name="begins executing instructions in boot block">54</part-num-ref>
+ which is occurring before CPU <part-num-ref name="which is occurring before CPU">30</part-num-ref>
+ is operable to execute OS <part-num-ref name="is operable to execute OS">36</part-num-ref>
+ instructions. Sensor reader <part-num-ref name="instructions. Sensor reader">50</part-num-ref>
+ reads the state of tamper sensor <part-num-ref name="state of tamper sensor">24</part-num-ref>
+ and/or any other tamper sensors coupled to firmware <part-num-ref name="and/or any other tamper sensors coupled to firmware">20,</part-num-ref>
+ and logic <part-num-ref name="and/or any other tamper sensors coupled to firmware 20, and logic">56</part-num-ref>
+ determines the state of tamper sensor <part-num-ref name="state of tamper sensor">24</part-num-ref>
+ by comparing the currently-measured state with previously-recorded measurement <part-num-ref name="currently-measured state with previously-recorded measurement">62.</part-num-ref>
+ Logic <part-num-ref name="currently-measured state with previously-recorded measurement 62. Logic">56</part-num-ref>
+ then generates report <part-num-ref name="then generates report">60,</part-num-ref>
+ which is digitally signed and/or encrypted by firmware <part-num-ref name="then generates report 60, which is digitally signed and/or encrypted by firmware">22,</part-num-ref>
+ thereby rendering report <part-num-ref name="then generates report 60, which is digitally signed and/or encrypted by firmware 22, thereby rendering report">60</part-num-ref>
+ tamper-evident. For example, in the embodiment illustrated in FIGURE 1, <page-break num="6"/>
+      <boundary-data type="header">200603280-1</boundary-data>
+      <boundary-data type="header">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+report <part-num-ref name="embodiment illustrated in FIGURE 1, report">60</part-num-ref>
+ comprises digital signature <part-num-ref name="comprises digital signature">90,</part-num-ref>
+ which renders alteration of and/or tampering with the contents of report <part-num-ref name="contents of report">60</part-num-ref>
+ evident when digital signature <part-num-ref name="evident when digital signature">90</part-num-ref>
+ is verified (e.g., by monitoring system 14). In FIGURE 1, report <part-num-ref name="by monitoring system 14). In FIGURE 1, report">60</part-num-ref>
+ is residing in trusted memory <part-num-ref name="is residing in trusted memory">52</part-num-ref>
+ and is available for export via port <part-num-ref name="and is available for export via port">28</part-num-ref>
+ prior to CPU <part-num-ref name="prior to CPU">30</part-num-ref>
+ being operable to execute instructions. After generation of report <part-num-ref name="being operable to execute instructions. After generation of report">60,</part-num-ref>
+ firmware <part-num-ref name="being operable to execute instructions. After generation of report 60, firmware">20</part-num-ref>
+ continues the boot-up process and directs CPU <part-num-ref name="boot-up process and directs CPU">30</part-num-ref>
+ to begin executing instructions and load OS <part-num-ref name="to begin executing instructions and load OS">36</part-num-ref>
+ from memory <part-num-ref name="from memory">32.</part-num-ref>
+ Thus, by the stage in the power-on/boot-up process that CPU <part-num-ref name="power-on/boot-up process that CPU">30</part-num-ref>
+ is able to execute OS <part-num-ref name="is able to execute OS">36</part-num-ref>
+ instructions, report <part-num-ref name="instructions, report">60</part-num-ref>
+ is already generated and rendered tamper- evident. Therefore, attempting to modify the contents of report <part-num-ref name="contents of report">60</part-num-ref>
+ in trusted memory <part-num-ref name="in trusted memory">52</part-num-ref>
+ using CPU <part-num-ref name="using CPU">30</part-num-ref>
+ would leave evidence that report <part-num-ref name="would leave evidence that report">60</part-num-ref>
+ has been altered.    </p>
+    <p id="p-23" num="23">[0014]     Thus, if protected asset 26 had been tampered with, sensor <part-num-ref name="had been tampered with, sensor">24</part-num-ref>
+ will detect the physical tampering and the evidence of tampering will be reflected in the generation of report <part-num-ref name="generation of report">60.</part-num-ref>
+ If report <part-num-ref name="generation of report 60. If report">60</part-num-ref>
+ is then altered in an attempt to delete any indication of tampering with protected asset <part-num-ref name="attempt to delete any indication of tampering with protected asset">26,</part-num-ref>
+ the alteration of report <part-num-ref name="alteration of report">60</part-num-ref>
+ will be detectable. In some embodiments, monitoring system <part-num-ref name="will be detectable. In some embodiments, monitoring system">14</part-num-ref>
+ is configured to validate and/or otherwise verify the integrity of report <part-num-ref name="integrity of report">60</part-num-ref>
+ by either using digital signature <part-num-ref name="by either using digital signature">90</part-num-ref>
+ and/or analyzing the results of decrypting an encrypted report <part-num-ref name="encrypted report">60.</part-num-ref>
+ If report <part-num-ref name="encrypted report 60. If report">60</part-num-ref>
+ has been tampered with, for example to conceal the tampering of protected asset <part-num-ref name="tampering of protected asset">26,</part-num-ref>
+ monitoring system <part-num-ref name="tampering of protected asset 26, monitoring system">14</part-num-ref>
+ is able to determine that report <part-num-ref name="is able to determine that report">60</part-num-ref>
+ is not reliable. If monitoring system <part-num-ref name="is not reliable. If monitoring system">14</part-num-ref>
+ validates the integrity of report <part-num-ref name="integrity of report">60,</part-num-ref>
+ the contents of report <part-num-ref name="contents of report">60</part-num-ref>
+ may be used to determine whether protected asset <part-num-ref name="may be used to determine whether protected asset">26</part-num-ref>
+ has been tampered with.    </p>
+    <p id="p-24" num="24">[0015]     Accordingly, for example, if computing system 12 comprises a notebook computer being transported through a security checkpoint, monitoring system <part-num-ref name="security checkpoint, monitoring system">14</part-num-ref>
+ may be configured to form part of the checkpoint security system, and remote system <part-num-ref name="checkpoint security system, and remote system">120</part-num-ref>
+ may comprise a computing system located in a remote security office. In response to computing system <part-num-ref name="remote security office. In response to computing system">12</part-num-ref>
+ being subjected to a "power-on" test, firmware <part-num-ref name="&quot;power-on&quot; test, firmware">20</part-num-ref>
+ will generate report <part-num-ref name="will generate report">60.</part-num-ref>
+ Monitoring system <part-num-ref name="will generate report 60. Monitoring system">14,</part-num-ref>
+ located at the security checkpoint, is configured to import report <part-num-ref name="security checkpoint, is configured to import report">60</part-num-ref>
+ from computing system <part-num-ref name="from computing system">12.</part-num-ref>
+ If verification logic <part-num-ref name="from computing system 12. If verification logic">100</part-num-ref>
+ identifies tampering of report <part-num-ref name="identifies tampering of report">60</part-num-ref>
+ and/or report <part-num-ref name="and/or report">60</part-num-ref>
+ indicates tampering of protected asset <part-num-ref name="indicates tampering of protected asset">26,</part-num-ref>
+ a security alert may be generated to appear at monitoring system <part-num-ref name="security alert may be generated to appear at monitoring system">14</part-num-ref>
+ and/or remote system <part-num-ref name="and/or remote system">120.</part-num-ref>
+    </p>
+    <p id="p-25" num="25">[0016]    In some embodiments, protected asset 26 may comprise an asset that is subject to modification, removal or opening during repair, use and upgrading of computing system <part-num-ref name="asset that is subject to modification, removal or opening during repair, use and upgrading of computing system">12.</part-num-ref>
+ In some embodiments, report logic <part-num-ref name="asset that is subject to modification, removal or opening during repair, use and upgrading of computing system 12. In some embodiments, report logic">56</part-num-ref>
+ is further configured to read the state of sensor <part-num-ref name="state of sensor">24</part-num-ref>
+ after an authorized modification, removal or opening of protected asset <part-num-ref name="authorized modification, removal or opening of protected asset">26</part-num-ref>
+ and update measurement <part-num-ref name="and update measurement">62</part-num-ref>
+ in trusted memory <part-num-ref name="in trusted memory">52</part-num-ref>
+ subject to the entry of a security password <page-break num="7"/>
+      <boundary-data type="header">200603280-1</boundary-data>
+      <boundary-data type="header">
+        <confidence value="8">6</confidence>
+      </boundary-data>
+matching a password <part-num-ref name="password">130</part-num-ref>
+ stored in trusted memory <part-num-ref name="stored in trusted memory">52.</part-num-ref>
+ For example, in some embodiments, measurement <part-num-ref name="stored in trusted memory 52. For example, in some embodiments, measurement">62</part-num-ref>
+ comprises an alphanumeric sequence representing information uniquely identifying protected asset <part-num-ref name="alphanumeric sequence representing information uniquely identifying protected asset">26,</part-num-ref>
+ such as a serial number permanently burned into a memory of protected asset <part-num-ref name="memory of protected asset">26</part-num-ref>
+ that is read by sensor <part-num-ref name="that is read by sensor">24.</part-num-ref>
+ Changing protected asset <part-num-ref name="that is read by sensor 24. Changing protected asset">26</part-num-ref>
+ will result in sensor <part-num-ref name="will result in sensor">24</part-num-ref>
+ reading a different alphanumeric sequence. In some embodiments, report logic <part-num-ref name="different alphanumeric sequence. In some embodiments, report logic">56</part-num-ref>
+ is configured to enable measurement <part-num-ref name="is configured to enable measurement">62</part-num-ref>
+ to be updated by an authorized party, for example, a network administrator with knowledge of password <part-num-ref name="network administrator with knowledge of password">130</part-num-ref>
+ [0017]     FIGURE 2 is a diagram illustrating an embodiment of a tamper indication method for a computing system. The method begins at block <part-num-ref name="method begins at block">201,</part-num-ref>
+ where firmware <part-num-ref name="method begins at block 201, where firmware">20</part-num-ref>
+ begins executing boot block <part-num-ref name="begins executing boot block">54.</part-num-ref>
+ At block <part-num-ref name="begins executing boot block 54. At block">203,</part-num-ref>
+ firmware <part-num-ref name="begins executing boot block 54. At block 203, firmware">20</part-num-ref>
+ and/or sensor reader <part-num-ref name="and/or sensor reader">50</part-num-ref>
+ reads sensor <part-num-ref name="reads sensor">24.</part-num-ref>
+    </p>
+    <p id="p-26" num="26">At block 205, report logic 56 in firmware <part-num-ref name="in firmware">20</part-num-ref>
+ compares the read measurement of sensor <part-num-ref name="read measurement of sensor">24</part-num-ref>
+ with previously-recorded measurement <part-num-ref name="with previously-recorded measurement">62.</part-num-ref>
+ At block <part-num-ref name="with previously-recorded measurement 62. At block">207,</part-num-ref>
+ report logic <part-num-ref name="with previously-recorded measurement 62. At block 207, report logic">56</part-num-ref>
+ generates report <part-num-ref name="generates report">60.</part-num-ref>
+ At block <part-num-ref name="generates report 60. At block">209,</part-num-ref>
+ firmware <part-num-ref name="generates report 60. At block 209, firmware">22</part-num-ref>
+ renders report <part-num-ref name="renders report">60</part-num-ref>
+ tamper evident by encrypting report <part-num-ref name="tamper evident by encrypting report">60</part-num-ref>
+ and/or generating/using digital signature <part-num-ref name="and/or generating/using digital signature">90.</part-num-ref>
+ At block <part-num-ref name="and/or generating/using digital signature 90. At block">211,</part-num-ref>
+ report <part-num-ref name="and/or generating/using digital signature 90. At block 211, report">60</part-num-ref>
+ is exported, such as by firmware <part-num-ref name="is exported, such as by firmware">20,</part-num-ref>
+ to monitoring system <part-num-ref name="is exported, such as by firmware 20, to monitoring system">14</part-num-ref>
+ via port <part-num-ref name="via port">28</part-num-ref>
+ (report <part-num-ref name="(report">60</part-num-ref>
+ may also be exported to memory <part-num-ref name="may also be exported to memory">32</part-num-ref>
+ and then exported to monitoring system <part-num-ref name="and then exported to monitoring system">14</part-num-ref>
+ by CPU 30).    </p>
+    <p id="p-27" num="27">[0018]     FIGURE 3 is another diagram illustrating an embodiment of a tamper indication method for a computing system. The method begins at block <part-num-ref name="method begins at block">301,</part-num-ref>
+ where monitoring system <part-num-ref name="method begins at block 301, where monitoring system">14</part-num-ref>
+ imports and/or otherwise receives report <part-num-ref name="imports and/or otherwise receives report">60.</part-num-ref>
+ At block <part-num-ref name="imports and/or otherwise receives report 60. At block">303,</part-num-ref>
+ verification logic <part-num-ref name="imports and/or otherwise receives report 60. At block 303, verification logic">100</part-num-ref>
+ verifies the integrity of report <part-num-ref name="integrity of report">60</part-num-ref>
+ (e.g., by hashing and decrypting report <part-num-ref name="by hashing and decrypting report">60</part-num-ref>
+ and compare a hash value <part-num-ref name="hash value">102</part-num-ref>
+ calculated by verification logic <part-num-ref name="calculated by verification logic">100</part-num-ref>
+ with hash value <part-num-ref name="with hash value">92</part-num-ref>
+ calculated by firmware <part-num-ref name="calculated by firmware">22</part-num-ref>
+ and reported as part of digital signature 90). At decision block <part-num-ref name="and reported as part of digital signature 90). At decision block">305,</part-num-ref>
+ a determination is made if the integrity of report <part-num-ref name="integrity of report">60</part-num-ref>
+ is verified. If the integrity of report <part-num-ref name="integrity of report">60</part-num-ref>
+ is verified, the method proceeds to block <part-num-ref name="method proceeds to block">307,</part-num-ref>
+ where verification logic <part-num-ref name="method proceeds to block 307, where verification logic">100</part-num-ref>
+ reads report <part-num-ref name="reads report">60</part-num-ref>
+ to ascertain whether report <part-num-ref name="to ascertain whether report">60</part-num-ref>
+ indicates tampering of protected asset <part-num-ref name="indicates tampering of protected asset">26.</part-num-ref>
+ At decision block <part-num-ref name="indicates tampering of protected asset 26. At decision block">309,</part-num-ref>
+ a determination is made as to whether report <part-num-ref name="determination is made as to whether report">60</part-num-ref>
+ indicates that tampering of protected asset <part-num-ref name="indicates that tampering of protected asset">24</part-num-ref>
+ has occurred. If an indication of tampering is present, the method proceeds to block <part-num-ref name="method proceeds to block">311,</part-num-ref>
+ where an alarm or other indication of the tampering is generated. If at decision block <part-num-ref name="tampering is generated. If at decision block">309</part-num-ref>
+ it is determined that report <part-num-ref name="it is determined that report">60</part-num-ref>
+ does not indicate tampering, the method ends. If at decision block <part-num-ref name="method ends. If at decision block">309</part-num-ref>
+ the integrity of report <part-num-ref name="integrity of report">60</part-num-ref>
+ is not verified, the method proceeds from decision block <part-num-ref name="method proceeds from decision block">309</part-num-ref>
+ to block <part-num-ref name="to block">311</part-num-ref>
+ where an alarm or other indication of report <part-num-ref name="alarm or other indication of report">60</part-num-ref>
+ tampering is generated.    </p>
+    <p id="p-28" num="28">[0019]     Thus, embodiments of system 10 enable a determination as to whether a computing device has been tampered with by using measurements taken and/or otherwise <page-break num="8"/>
+      <boundary-data type="header">200603280-1</boundary-data>
+      <boundary-data type="header">
+        <confidence value="7">7</confidence>
+      </boundary-data>
+acquired by trusted components of the computing device. It should be understood that in the described methods, certain functions may be omitted, accomplished in a sequence different from that depicted in FIGURE 2, or performed simultaneously. Also, it should be understood that the methods depicted in FIGURES <part-num-ref name="methods depicted in FIGURES">2</part-num-ref>
+ and <part-num-ref name="and">3</part-num-ref>
+ may be altered to encompass any of the other features or aspects as described elsewhere in the specification. Further, embodiments may be implemented in software and can be adapted to run on different pla<confidence value="8">t</confidence>
+forms and operating systems. In particular, functions implemented by logic <part-num-ref name="specification. Further, embodiments may be implemented in software and can be adapted to run on different platforms and operating systems. In particular, functions implemented by logic">56,</part-num-ref>
+ logic <part-num-ref name="specification. Further, embodiments may be implemented in software and can be adapted to run on different platforms and operating systems. In particular, functions implemented by logic 56, logic">80,</part-num-ref>
+ and logic <part-num-ref name="specification. Further, embodiments may be implemented in software and can be adapted to run on different platforms and operating systems. In particular, functions implemented by logic 56, logic 80, and logic">100,</part-num-ref>
+ for example, may be provided as an ordered listing of executable instructions that can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device, and execute the instructions. In the context of this document, a "computer-readable medium" can be any means that can contain, store, communicate, propagate or transport the program for use by or in connection with the instruction execution system, apparatus, or device.    </p>
+    <p id="p-29" num="29">The computer-readable medium can be, for example, but is not limited to, an electronic, magnetic, optical, electro-magnetic, infrared, or semi-conductor system, apparatus, device, or propagation medium.</p>
+  </description>
+</us-patent-application>
+

applicant/11825170.xml

@@ -0,0 +1,558 @@
+<?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>11825170</doc-number>
+        <date>2007-07-05</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <boundary-data type="header">PGS-07-<confidence value="56">O1</confidence>
+ <confidence value="86">US</confidence>
+    </boundary-data>
+    <heading id="h-1">APPLICATION</heading>
+    <heading id="h-2">FOR</heading>
+    <heading id="h-3">UNITED STATES LETTERS PATENT</heading>
+    <heading id="h-4">TITLE: SEISMIC STREAMER HAVING LONGITUDINALLY</heading>
+    <heading id="h-5">SYMMETRICALLY SENSITIVE SENSORS TO</heading>
+    <heading id="h-6">REDUCE EFFECTS OF LONGITUDINALLY</heading>
+    <heading id="h-7">TRAVELING WAVES</heading>
+    <heading id="h-8">INVENTORS: NILS LUNDE, ANDRE STENZEL,</heading>
+    <heading id="h-9">
+      <confidence value="222222">OYVIND</confidence>
+ HILLESUND, STIAN HEGNA    </heading>
+    <heading id="h-10">"EXPRESS MAIL" MAILING LABEL</heading>
+    <p id="p-1" num="1">NUMBER EQ963225075 US DATE OF DEPOSIT July <confidence value="66">5,</confidence>
+ <confidence value="6668">2007</confidence>
+ I hereby certify that this paper or fee is being deposited with the United States Postal Service "EXPRESS MAIL POST OFFICE TO ADDRESSEE<confidence value="5">"</confidence>
+ service under <part-num-ref name="United States Postal Service &quot;EXPRESS MAIL POST OFFICE TO ADDRESSEE&quot; service under">37</part-num-ref>
+ C.F.R. 1.10 on the date indicated above and is addressed to: MAIL STOP PATENT APPLICATION, Commissioner for Patents, P.O. Box <part-num-ref name="date indicated above and is addressed to: MAIL STOP PATENT APPLICATION, Commissioner for Patents, P.O. Box">1450,</part-num-ref>
+ Alexandria, VA 22313- <part-num-ref name="date indicated above and is addressed to: MAIL STOP PATENT APPLICATION, Commissioner for Patents, P.O. Box 1450, Alexandria, VA 22313-">450.</part-num-ref>
+    </p>
+    <p id="p-2" num="2">E. Eug   Thigpen <page-break num="2"/>
+      <boundary-data type="header">PGS-07-<confidence value="55">O1</confidence>
+ <confidence value="88">US</confidence>
+      </boundary-data>
+    </p>
+    <heading id="h-11">SEISMIC STREAMER HAVING LONGITUDINALLY SYMMETRICALLY</heading>
+    <heading id="h-12">SENSITIVE SENSORS TO REDUCE EFFECTS OF LONGITUDINALLY</heading>
+    <heading id="h-13">TRAVELING WAVES</heading>
+    <p id="p-3" num="3">Cross-reference to related applications Not applicable.</p>
+    <p id="p-4" num="4">Statement regarding federally sponsored research or development Not applicable.</p>
+    <p id="p-5" num="5">Background of the Invention Field of the Invention <confidence value="5">[</confidence>
+0001<confidence value="5">]</confidence>
+       The invention relates generally to the field of marine seismic survey apparatus and methods. More specifically, the invention relates to structures for marine seismic streamers that have reduced noise induced by effects of towing such streamers in the water.    </p>
+    <p id="p-6" num="6">Background Art <confidence value="5">[</confidence>
+0002]       In marine seismic surveying, a seismic vessel travels on the surface of a body of water such as a lake or the ocean. The seismic vessel typically contains seismic data acquisition equipment, which includes devices such as navigation control, seismic source control, seismic sensor control, and signal recording devices. The seismic acquisition equipment causes a seismic source towed in the body of water, by the seismic vessel or another vessel, to actuate at selected times. The seismic source may be any type well known in the art of seismic acquisition, including air guns or water guns, or most commonly, arrays of air guns. Seismic streamers, also called seismic cables, are elongate cable-like structures that are towed in the body of water by the seismic survey vessel or by another vessel. Typically, a plurality of seismic streamers is towed behind the seismic <boundary-data type="header">
+        <confidence value="7">1</confidence>
+      </boundary-data>
+      <page-break num="3"/>
+      <boundary-data type="header">PGS-07-<confidence value="68">01</confidence>
+ <confidence value="86">US</confidence>
+      </boundary-data>
+vessel laterally spaced apart from each other. The seismic streamers contain sensors to detect the seismic wavefields initiated by the seismic source and reflected from acoustic impedance boundaries in the subsurface Earth formations below the water bottom.    </p>
+    <p id="p-7" num="7">
+      <confidence value="5">[</confidence>
+0003]       Conventionally, seismic streamers contain pressure-responsive sensors such as hydrophones, but seismic streamers have also been proposed that contain particle motion sensors, such as geophones, in addition to hydrophones. The sensors are typically located at selected intervals along the length of seismic streamers.    </p>
+    <p id="p-8" num="8">
+      <confidence value="5">[</confidence>
+0004]       Seismic streamers also include electronic components, electrical wiring and may include other types of sensors. Seismic streamers are typically assembled from sections, each section being approximately 75 meters in length. A number of such sections are joined end to end, and can extend the assembled streamer to a total length of many thousands of meters. Position control devices, such as depth controllers, paravanes, and tail buoys are affixed to the streamer at selected positions and are used to regulate and monitor the movement of the streamer in the water. During operation, the seismic sources and streamers are typically submerged at a selected depth in the water. The seismic sources are typically operated at a depth of 5-15 meters below the water surface and the seismic streamers are typically operated at a depth of 5-40 meters.    </p>
+    <p id="p-9" num="9">
+      <confidence value="5">[</confidence>
+0005]       A typical streamer section consists of an external jacket, connectors, spacers, and strength members. The external jacket is formed from a flexible, acoustically transparent material such as polyurethane and protects the interior of the streamer section from water intrusion. The connectors are disposed at the ends of each streamer section and link the section mechanically, electrically and/or optically to adjacent streamer sections and, therefore, ultimately link it to the seismic towing vessel. There is at least one, and are usually two or more such strength members in each streamer section that extend the length of each streamer section from one end connector to the other. The strength members provide the streamer section with the capability to carry axial mechanical load.    </p>
+    <p id="p-10" num="10">A wire bundle or cable also extends the length of each streamer section, and can contain electrical power conductors and electrical data communication wires. In some instances, optical fibers for signal communication are included in the wire bundle.</p>
+    <boundary-data type="header">
+      <confidence value="8">2</confidence>
+    </boundary-data>
+    <boundary-data type="header">
+      <confidence value="88">PG</confidence>
+S-07-<confidence value="4586">01US</confidence>
+    </boundary-data>
+    <p id="p-11" num="11">
+      <page-break num="4"/>
+      <confidence value="5">[</confidence>
+0006]       Typically, hydrophones or groups of hydrophones are located within the streamer section. The hydrophones are frequently mounted within corresponding spacers for protection. The distance between hydrophone containing spacers is ordinarily about 0.7 meters. A hydrophone group, typically comprising <part-num-ref name="hydrophone group, typically comprising">16</part-num-ref>
+ hydrophones, thus extends for a length of about 12.5 meters. The hydrophones in a group are typically connected in series to cancel effects of certain types of noise to which the streamer may be exposed.    </p>
+    <p id="p-12" num="12">The interior of the seismic streamers is typically filled with a void filling material to provide buoyancy and desired acoustic properties. Many seismic streamers have been filled with a liquid, such as oil or kerosene.</p>
+    <p id="p-13" num="13">
+      <confidence value="5">[</confidence>
+0007]       Ideally, in a streamer moving at constant speed, all the streamer components including the jacket, the connectors, the spacers, the strength members, wire bundle, sensors and liquid void filling material all move at the same constant speed and do not move relative to each other. Under actual movement conditions, however, transient motion of the streamers takes place, such transient motion being caused by events such as pitching and heaving of the seismic vessel, movement of the paravanes and tail buoys attached to the streamers, strumming of the towing cables attached to the streamers caused by vortex shedding on the cables, and operation of depth-control devices located on the streamers. Any of the foregoing types of transient motion can cause transient motion (stretching) of the strength members. Transient motion of the strength members displaces the spacers or connectors, causing pressure fluctuations in the liquid void filling material that are detected by the hydrophones. Pressure fluctuations radiating away from the spacers or connectors also cause the flexible outer jacket to compress in and bulge out in the form of a traveling wave, giving the phenomenon "bulge waves" its name.    </p>
+    <p id="p-14" num="14">
+      <confidence value="5">[</confidence>
+0008<confidence value="5">]</confidence>
+       In addition, there are other types of noise, often called "flow noise", which can affect the quality of the seismic signal detected by the hydrophones. For example, vibrations of the seismic streamer can cause extensional waves in the outer jacket and resonance transients traveling down the strength members. A turbulent boundary layer created around the outer jacket of the streamer by the act of towing the streamer can also cause pressure fluctuations in the liquid core-filling material. In liquid filled streamer sections, the extensional waves, resonance transients, and turbulence-induced noise are <boundary-data type="header">
+        <confidence value="8">3</confidence>
+      </boundary-data>
+      <page-break num="5"/>
+      <boundary-data type="header">PGS-07-<confidence value="4288">O1US</confidence>
+      </boundary-data>
+typically much smaller in amplitude than the bulge waves, however they do exist and affect the quality of the seismic signals detected by the hydrophones. Bulge waves are usually the largest source of vibration noise because these waves travel in the liquid core material filling the streamer sections and thus act directly on the hydrophones.    </p>
+    <p id="p-15" num="15">[0009<confidence value="5">]</confidence>
+       It is known in the art to replace the liquid core material in a streamer section with a soft, flexible solid core material, such as gel. The introduction of a softer, flexible solid material may block the development of bulge waves compared to a liquid core material.    </p>
+    <p id="p-16" num="16">Using a soft, flexible material will eliminate a substantial portion of the problem with "bulge waves", but the so-called Poisson effect from the strength members can increase.</p>
+    <p id="p-17" num="17">Because of the relatively high tensile stiffness of the strength members, transients generally travel along the strength members at velocities near to or greater than that of the sound velocity in water, such velocities typically in the range of <part-num-ref name="range of">1000</part-num-ref>
+ to <part-num-ref name="to">1500</part-num-ref>
+ meters per second. The actual velocity of transients along the strength members depends mainly on the elastic modulus of the strength member material and the tension applied to the streamer as it is towed in the water. The lower the elastic modulus the more compliant the streamer will be, and thus the more transient energy it will dissipate as heat and the less will pass through the strength member. Special elastic sections are normally placed at either end of a streamer cable to reduce the effects of transients.    </p>
+    <p id="p-18" num="18">
+      <confidence value="5">[</confidence>
+0010<confidence value="5">]</confidence>
+       There is still a need to further improve the attenuation of longitudinal waves transmitted through the strength members of marine seismic streamers.    </p>
+    <p id="p-19" num="19">Summary of the Invention [0011<confidence value="5">]</confidence>
+       One aspect of the invention is a seismic streamer. A seismic streamer according to this aspect of the invention includes a jacket and at least one seismic sensor disposed in a sensor holder inside the jacket. The at least one sensor is oriented inside the sensor holder such that a response of the at least one sensor is substantially longitudinally symmetric<confidence value="8">.</confidence>
+    </p>
+    <p id="p-20" num="20">[0012]       A seismic streamer according to another aspect of the invention includes a jacket covering an exterior of the streamer. At least one strength member extends along the <boundary-data type="header">
+        <confidence value="8">4</confidence>
+      </boundary-data>
+      <page-break num="6"/>
+      <boundary-data type="header">PGS-07-<confidence value="26">01</confidence>
+ <confidence value="86">US</confidence>
+      </boundary-data>
+length of the jacket. The strength member is disposed inside the jacket. At least one array of sensors is disposed inside the jacket along the strength member. Each sensor in the at least one array is disposed in a sensor holder. Each sensor in the array is oriented inside the respective sensor holder such that a response of each sensor is substantially longitudinally symmetric. An acoustically transparent material fills void space in the interior of the jacket.    </p>
+    <p id="p-21" num="21">
+      <confidence value="5">[</confidence>
+0013<confidence value="5">]</confidence>
+      Other aspects and advantages of the invention will be apparent from the description and claims which follow.    </p>
+    <p id="p-22" num="22">Brief Description of the Drawings <confidence value="5">[</confidence>
+0014]      FIG. 1 shows typical marine seismic data acquisition using a streamer according to one embodiment of the invention.    </p>
+    <p id="p-23" num="23">
+      <confidence value="5">[</confidence>
+0015<confidence value="5">]</confidence>
+      FIG. 2 shows a cut away view of one embodiment of a streamer segment according to the invention.    </p>
+    <p id="p-24" num="24">[0016]      FIG. 3 shows one example of a transducer of a seismic sensor.</p>
+    <p id="p-25" num="25">
+      <confidence value="5">[</confidence>
+0017]      FIG. 4 shows another example of a transducer formed from half of the element shown in FIG. 3.    </p>
+    <p id="p-26" num="26">
+      <confidence value="5">[</confidence>
+0018<confidence value="5">]</confidence>
+      FIG. 5 shows an example of a cylindrical hydrophone used in some examples <confidence value="5">[</confidence>
+0019]      FIG. 6 shows another example of a seismic sensor placed in a sensor spacer.    </p>
+    <p id="p-27" num="27">[0020]      FIGS. 7A, 7B, 8A, 8B, 9A and 9B show other arrangements of a seismic sensor placed in a sensor holder, and other examples of a sensor holder.</p>
+    <p id="p-28" num="28">Detailed Description <confidence value="5">[</confidence>
+0021]      FIG. 1 shows an example marine seismic data acquisition system as it is typically used for acquiring seismic data. A seismic vessel <part-num-ref name="seismic vessel">14</part-num-ref>
+ moves along the surface of a body of water <part-num-ref name="body of water">12</part-num-ref>
+ such as a lake or the ocean. The marine seismic survey is intended to detect and record seismic signals related to structure and composition of various subsurface <boundary-data type="header">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+      <page-break num="7"/>
+      <boundary-data type="header">
+        <confidence value="2">-</confidence>
+                                                                                 <confidence value="88">PG</confidence>
+S-07-O<confidence value="6">1</confidence>
+ <confidence value="86">US</confidence>
+      </boundary-data>
+formations <part-num-ref name="marine seismic survey is intended to detect and record seismic signals related to structure and composition of various subsurface formations">21,</part-num-ref>
+ <part-num-ref name="marine seismic survey is intended to detect and record seismic signals related to structure and composition of various subsurface formations 21,">23</part-num-ref>
+ below the water bottom <part-num-ref name="water bottom">20.</part-num-ref>
+ The seismic vessel <part-num-ref name="seismic vessel">14</part-num-ref>
+ includes source actuation, data recording and navigation equipment, shown generally at <part-num-ref name="includes source actuation, data recording and navigation equipment, shown generally at">16</part-num-ref>
+ and referred to for convenience as a "recording system." The seismic vessel <part-num-ref name="seismic vessel">14,</part-num-ref>
+ or a different vessel (not shown), can tow one or more seismic energy sources <part-num-ref name="different vessel (not shown), can tow one or more seismic energy sources">18,</part-num-ref>
+ or arrays of such sources in the water <part-num-ref name="water">12.</part-num-ref>
+ The seismic vessel <part-num-ref name="seismic vessel">14</part-num-ref>
+ or a different vessel tows at least one seismic streamer <part-num-ref name="different vessel tows at least one seismic streamer">10</part-num-ref>
+ near the surface of the water <part-num-ref name="water">12.</part-num-ref>
+ The streamer <part-num-ref name="streamer">10</part-num-ref>
+ is coupled to the vessel <part-num-ref name="vessel">14</part-num-ref>
+ by a lead in cable <part-num-ref name="lead in cable">26.</part-num-ref>
+ A plurality of sensor arrays <part-num-ref name="plurality of sensor arrays">24</part-num-ref>
+ can be disposed at spaced apart locations along the streamer <part-num-ref name="streamer">10.</part-num-ref>
+ The sensor arrays <part-num-ref name="sensor arrays">24,</part-num-ref>
+ as will be explained in more detail below, are formed by mounting a seismic sensor inside each one of a plurality of sensor spacers in a particular manner and disposing the sensor spacers at spaced apart locations along the streamer <part-num-ref name="streamer">10.</part-num-ref>
+    </p>
+    <p id="p-29" num="29">
+      <confidence value="5">[</confidence>
+0022<confidence value="5">]</confidence>
+       During operation, certain equipment (not shown separately) in the recording system <part-num-ref name="recording system">16</part-num-ref>
+ causes the source <part-num-ref name="source">18</part-num-ref>
+ to actuate at selected times. When actuated, the source <part-num-ref name="source">18</part-num-ref>
+ produces seismic energy <part-num-ref name="produces seismic energy">19</part-num-ref>
+ that emanates generally outwardly from the source <part-num-ref name="source">18.</part-num-ref>
+ The energy <part-num-ref name="energy">19</part-num-ref>
+ travels downwardly, through the water <part-num-ref name="water">12,</part-num-ref>
+ and passes, at least in part, through the water bottom <part-num-ref name="water bottom">20</part-num-ref>
+ into the formations <part-num-ref name="formations">21,</part-num-ref>
+ <part-num-ref name="formations 21,">23</part-num-ref>
+ below. Seismic energy <part-num-ref name="below. Seismic energy">19</part-num-ref>
+ is at least partially reflected from one or more acoustic impedance boundaries <part-num-ref name="is at least partially reflected from one or more acoustic impedance boundaries">22</part-num-ref>
+ below the water bottom <part-num-ref name="water bottom">20,</part-num-ref>
+ and travels upwardly whereupon it may be detected by the sensors in each sensor array <part-num-ref name="sensors in each sensor array">24.</part-num-ref>
+ Structure of the formations <part-num-ref name="formations">21,</part-num-ref>
+ <part-num-ref name="formations 21,">23,</part-num-ref>
+ among other properties of the Earth's subsurface, can be inferred by travel time of the energy <part-num-ref name="energy">19</part-num-ref>
+ and by characteristics of the detected energy such as its amplitude and phase.    </p>
+    <p id="p-30" num="30">
+      <confidence value="5">[</confidence>
+0023<confidence value="5">]</confidence>
+       Having explained the general method of operation of a marine seismic acquisition system including at least one streamer, an example embodiment of a streamer segment according to the invention will be explained with reference to FIG. 2. FIG. 2 is a cut away view of a portion (segment) <confidence value="25">10</confidence>
+A of a typical marine seismic streamer <part-num-ref name="typical marine seismic streamer">(10</part-num-ref>
+ in FIG.    </p>
+    <p id="p-31" num="31">1). A streamer as shown in FIG. 1 may extend behind the seismic vessel <part-num-ref name="seismic vessel">(14</part-num-ref>
+ in FIG. 1) for several kilometers, and is typically made from a plurality of streamer segments <confidence value="268">10A</confidence>
+ as shown in FIG. 2 connected end to end behind the vessel <part-num-ref name="vessel">(14</part-num-ref>
+ in FIG. 1).    </p>
+    <boundary-data type="header">
+      <confidence value="8">6</confidence>
+    </boundary-data>
+    <boundary-data type="header">PGS-07-<confidence value="26">01</confidence>
+ <confidence value="86">US</confidence>
+    </boundary-data>
+    <p id="p-32" num="32">
+      <page-break num="8"/>
+      <confidence value="5">[</confidence>
+0024]      The streamer segment <confidence value="45">10</confidence>
+A in the present embodiment may be about <part-num-ref name="present embodiment may be about">75</part-num-ref>
+ meters overall length. A streamer (such as shown at <part-num-ref name="streamer (such as shown at">10</part-num-ref>
+ in FIG. 1) thus may be formed by connecting a selected number of such segments <confidence value="25">10</confidence>
+A end to end. The segment <confidence value="468">10A</confidence>
+ includes a jacket <part-num-ref name="jacket">30,</part-num-ref>
+ which in the present example can be made from 3.5 mm thick transparent polyurethane and has a nominal external diameter of about <part-num-ref name="nominal external diameter of about">62</part-num-ref>
+ millimeters. In each segment 1<confidence value="5">0</confidence>
+A, each axial end of the jacket <part-num-ref name="jacket">30</part-num-ref>
+ may be terminated by a coupling/termination plate <part-num-ref name="coupling/termination plate">36.</part-num-ref>
+ The coupling/termination plate <part-num-ref name="coupling/termination plate">36</part-num-ref>
+ may include rib elements 36A on an external surface of the coupling/termination plate <part-num-ref name="coupling/termination plate">36.</part-num-ref>
+ Such surface is inserted into one end of the jacket <part-num-ref name="jacket">30,</part-num-ref>
+ so as to seal against the inner surface of the jacket <part-num-ref name="jacket">30</part-num-ref>
+ and to grip the coupling/termination plate <part-num-ref name="coupling/termination plate">36</part-num-ref>
+ to the jacket <part-num-ref name="jacket">30,</part-num-ref>
+ when the jacket <part-num-ref name="jacket">30</part-num-ref>
+ is secured by an external clamp (not shown). In the present example, two strength members <part-num-ref name="present example, two strength members">42</part-num-ref>
+ can be coupled to the interior of each coupling/termination plate <part-num-ref name="interior of each coupling/termination plate">36</part-num-ref>
+ and can extend the length of the segment <confidence value="66">10</confidence>
+A. In a particular implementation of the invention, the strength members <part-num-ref name="strength members">42</part-num-ref>
+ may be made from a fiber rope containing or consisting of a fiber sold under the trademark VECTRAN, which is a registered trademark of Hoechst Celanese Corp., New York, NY. The strength members <part-num-ref name="strength members">42</part-num-ref>
+ transmit axial load along the length of the segment 1<confidence value="5">0</confidence>
+A. When one segment <confidence value="55">10</confidence>
+A is coupled end to end to another such segment (not shown in FIG. 2), the mating coupling/termination plates <part-num-ref name="mating coupling/termination plates">36</part-num-ref>
+ are coupled together using any suitable connector, so that the axial force is transmitted through the coupling/termination plates <part-num-ref name="coupling/termination plates">36</part-num-ref>
+ from the strength members <part-num-ref name="strength members">42</part-num-ref>
+ in one segment <confidence value="45">10</confidence>
+A to the strength members in the adjoining segment.    </p>
+    <p id="p-33" num="33">
+      <confidence value="5">[</confidence>
+0025]      The segment <confidence value="25">10</confidence>
+A can include a number of buoyancy spacers <part-num-ref name="number of buoyancy spacers">34</part-num-ref>
+ disposed in the jacket <part-num-ref name="jacket">30</part-num-ref>
+ and coupled to the strength members <part-num-ref name="strength members">42</part-num-ref>
+ at spaced apart locations along their length. The buoyancy spacers <part-num-ref name="buoyancy spacers">34</part-num-ref>
+ may be made from foamed polyurethane or other suitable, selected density material. The buoyancy spacers <part-num-ref name="buoyancy spacers">34</part-num-ref>
+ have a density selected to provide the segment <confidence value="25">10</confidence>
+A preferably with approximately the same overall density as the water <part-num-ref name="water">(12</part-num-ref>
+ in FIG. 1), <confidence value="66">so</confidence>
+ that the streamer <part-num-ref name="streamer">(10</part-num-ref>
+ in FIG. 1) will be substantially neutrally buoyant in the water <part-num-ref name="water">(12</part-num-ref>
+ in FIG. 1). As a practical matter, the buoyancy spacers <part-num-ref name="buoyancy spacers">34</part-num-ref>
+ provide the segment <confidence value="25">b0</confidence>
+A with an overall density very slightly less than that of fresh water. Appropriate overall density may then be adjusted in actual use by adding selected <boundary-data type="header">
+        <confidence value="8">7</confidence>
+      </boundary-data>
+      <page-break num="9"/>
+      <boundary-data type="header">PGS-07-<confidence value="55">O1</confidence>
+ <confidence value="88">US</confidence>
+      </boundary-data>
+buoyancy spacers <part-num-ref name="overall density very slightly less than that of fresh water. Appropriate overall density may then be adjusted in actual use by adding selected buoyancy spacers">34</part-num-ref>
+ and fill media having suitable specific gravity. As will be further explained below, in some examples, the buoyancy spacers <part-num-ref name="buoyancy spacers">34</part-num-ref>
+ may be arranged such that they are equally spaced on either side of one or more sensor holders <part-num-ref name="may be arranged such that they are equally spaced on either side of one or more sensor holders">32.</part-num-ref>
+    </p>
+    <p id="p-34" num="34">
+      <confidence value="5">[</confidence>
+0026<confidence value="5">]</confidence>
+      The segment <confidence value="45">10</confidence>
+A includes a generally centrally located conductor cable <part-num-ref name="generally centrally located conductor cable">40</part-num-ref>
+ which can include a plurality of insulated electrical conductors (not shown separately), and may include one or more optical fibers (not shown). The cable <part-num-ref name="cable">40</part-num-ref>
+ conducts electrical and/or optical signals from the seismic sensors (which will be further explained below) to the recording system <part-num-ref name="recording system">(16</part-num-ref>
+ in FIG. 1). The cable <part-num-ref name="cable">40</part-num-ref>
+ may in some implementations also carry electrical power to various signal processing circuits (not shown separately) disposed in one or more segments 1<confidence value="5">0</confidence>
+A, or disposed elsewhere along the streamer <part-num-ref name="streamer">(10</part-num-ref>
+ in FIG. 1). The length of the conductor cable <part-num-ref name="conductor cable">40</part-num-ref>
+ within a cable segment <confidence value="55">10</confidence>
+A is generally longer than the axial length of the segment <confidence value="55">10</confidence>
+A under the largest expected axial stress on the segment <confidence value="86">10</confidence>
+A, so that the electrical conductors and optical fibers in the cable <part-num-ref name="cable">40</part-num-ref>
+ will not experience any substantial axial stress when the streamer <part-num-ref name="streamer">(10</part-num-ref>
+ in FIG. 1) is towed through the water by a vessel. The conductors and optical fibers in the cable <part-num-ref name="cable">40</part-num-ref>
+ may be terminated in a connector <part-num-ref name="connector">38</part-num-ref>
+ disposed in each coupling/termination plate <part-num-ref name="disposed in each coupling/termination plate">36</part-num-ref>
+ so that when the segments <confidence value="55">10</confidence>
+A are connected end to end, corresponding electrical and/or optical connections may be made between the electrical conductors and optical fibers in the conductor cable <part-num-ref name="conductor cable">40</part-num-ref>
+ in adjoining segments <confidence value="66">10</confidence>
+A. As will be readily appreciated by those skilled in the art, the cable <part-num-ref name="cable">40</part-num-ref>
+ length is such that between sensor holders <part-num-ref name="length is such that between sensor holders">32</part-num-ref>
+ and spacers <part-num-ref name="and spacers">34,</part-num-ref>
+ there is typically a catenary in the cable <part-num-ref name="cable">40</part-num-ref>
+ between spacers <part-num-ref name="between spacers">34</part-num-ref>
+ and sensor holders <part-num-ref name="and sensor holders">32.</part-num-ref>
+    </p>
+    <p id="p-35" num="35">In one example, to be further explained below, the catenary on opposed sides of each sensor holder <part-num-ref name="catenary on opposed sides of each sensor holder">32</part-num-ref>
+ may be substantially the same or substantially symmetric.    </p>
+    <p id="p-36" num="36">
+      <confidence value="5">[</confidence>
+0027]      Sensors, which in the present example may be hydrophones, can each be disposed inside a respective sensor holder, shown in FIG. 2 generally at <part-num-ref name="generally at">32.</part-num-ref>
+ A transducing element in each of the seismic sensors will be further explained with reference to FIGS. 3 and <part-num-ref name="and">4,</part-num-ref>
+ and in the present example can be made from the transducer portion of a hydrophone sold under model number T-2BX by Teledyne Geophysical Instruments, Houston, TX.    </p>
+    <boundary-data type="header">
+      <confidence value="8">8</confidence>
+    </boundary-data>
+    <boundary-data type="header">
+      <confidence value="88">PG</confidence>
+S-07-O<confidence value="586">lUS</confidence>
+    </boundary-data>
+    <p id="p-37" num="37">
+      <page-break num="10"/>
+[0028<confidence value="5">]</confidence>
+      In the present example, each streamer segment <confidence value="55">10</confidence>
+A may include <part-num-ref name="present example, each streamer segment 10A may include">96</part-num-ref>
+ such seismic sensors, disposed in arrays. Each such array may include sixteen individual seismic sensors connected in electrical series (or optical series if the sensors are optical sensors).    </p>
+    <p id="p-38" num="38">It should be understood that in other implementations, the equivalent of a series coupled array may be effected by individually recording the signals from each sensor and summing the recorded signals. The number of sensors in an array is not a limit on the scope of this invention.</p>
+    <p id="p-39" num="39">
+      <confidence value="5">[</confidence>
+0029]      In a particular implementation, there are thus six such arrays, spaced apart from each other at about 12.5 meters in each segment <confidence value="66">10</confidence>
+A. The spacing between individual sensors in each array should be selected so that the axial span of the array is at most equal to about one half the wavelength of the highest frequency seismic energy intended to be detected by the streamer <part-num-ref name="streamer">(10</part-num-ref>
+ in FIG. 1). It should be clearly understood that the types of sensors used, types of sensor spacers/holders used, the electrical and/or optical connections used, the number of such sensors, and the spacing between such sensors are only used to illustrate one particular example of the invention, and are not intended to limit the scope of this invention.    </p>
+    <p id="p-40" num="40">
+      <confidence value="5">[</confidence>
+0030<confidence value="5">]</confidence>
+      In other examples, the sensors may be particle motion sensors such as velocity sensors or accelerometers. A marine seismic streamer having particle motion sensors is described in U.S. Patent Application No. 10/233,266, filed on August <part-num-ref name="marine seismic streamer having particle motion sensors is described in U.S. Patent Application No. 10/233,266, filed on August">30,</part-num-ref>
+ <part-num-ref name="marine seismic streamer having particle motion sensors is described in U.S. Patent Application No. 10/233,266, filed on August 30,">2002,</part-num-ref>
+ entitled, Apparatus and Method for Multicomponent Marine Geophysical Data Gathering, assigned to an affiliated company of the assignee of the present invention and incorporated herein by reference. The sensors may also be optical sensors. Still other sensors may include combined transducing element and signal processing electronic circuitry called an "integrated micro electrical mechanical system." One such sensing system is sold under model designation ADXL-330 by Analog Devices, Inc., Norwood, Mass.    </p>
+    <p id="p-41" num="41">
+      <confidence value="5">[</confidence>
+0031<confidence value="5">]</confidence>
+      At selected positions along the streamer <part-num-ref name="streamer">(10</part-num-ref>
+ in FIG. 1) a compass bird <part-num-ref name="compass bird">44</part-num-ref>
+ may be affixed to the outer surface of the jacket <part-num-ref name="jacket">30.</part-num-ref>
+ The compass bird <part-num-ref name="compass bird">44</part-num-ref>
+ includes a directional sensor (not shown separately) for determining the geographic orientation of the segment <boundary-data type="header">
+        <confidence value="8">9</confidence>
+      </boundary-data>
+      <page-break num="11"/>
+      <boundary-data type="header">PGS-07-<confidence value="68">01</confidence>
+ <confidence value="86">US</confidence>
+      </boundary-data>
+      <confidence value="25">10</confidence>
+A at the location of the compass bird <part-num-ref name="compass bird">44.</part-num-ref>
+ The compass bird <part-num-ref name="compass bird">44</part-num-ref>
+ may include an electromagnetic signal transducer 44A for communicating signals to a corresponding transducer 44B inside the jacket <part-num-ref name="jacket">30</part-num-ref>
+ for communication along the conductor cable <part-num-ref name="conductor cable">40</part-num-ref>
+ to the recording system <part-num-ref name="recording system">(16</part-num-ref>
+ in FIG. 1). Measurements of direction are used, as is known in the art, to infer the position of the various sensors in the segment 1<confidence value="5">0</confidence>
+A, and thus along the entire length of the streamer <part-num-ref name="streamer">(10</part-num-ref>
+ in FIG. 1). Typically, a compass bird will be affixed to the streamer <part-num-ref name="streamer">(10</part-num-ref>
+ in FIG. 1) about every <part-num-ref name="about every">300</part-num-ref>
+ meters (every four segments <confidence value="25">10</confidence>
+A). One type of compass bird is described in U.S. Patent No. 4,481,611 issued to Burrage and incorporated herein by reference.    </p>
+    <p id="p-42" num="42">
+      <confidence value="5">[</confidence>
+0032<confidence value="5">]</confidence>
+       In the present example, the interior space of the jacket <part-num-ref name="jacket">30</part-num-ref>
+ may be filled with a material <part-num-ref name="material">46</part-num-ref>
+ such as buoyancy void filler ("BVF"), which may be a curable, synthetic urethane-based polymer. The BVF <part-num-ref name="BVF">46</part-num-ref>
+ serves to exclude fluid (water) from the interior of the jacket <part-num-ref name="jacket">30,</part-num-ref>
+ to electrically insulate the various components inside the jacket <part-num-ref name="jacket">30,</part-num-ref>
+ to add buoyancy to a streamer section and to transmit seismic energy freely through the jacket <part-num-ref name="jacket">30</part-num-ref>
+ to the sensors (in sensor holders 32). The BVF <part-num-ref name="BVF">46</part-num-ref>
+ in its uncured state is essentially in liquid form. Upon cure, the BVF <part-num-ref name="BVF">46</part-num-ref>
+ no longer flows as a liquid, but instead becomes substantially solid. However, the BVF <part-num-ref name="BVF">46</part-num-ref>
+ upon cure retains some flexibility to bending stress, substantial elasticity, and freely transmits seismic energy to the sensors (in sensor holders 32). It should be understood that the BVF used in the present embodiment only is one example of a gel-like substance that can be used to fill the interior of the streamer.    </p>
+    <p id="p-43" num="43">Other materials could be also used. For example, heating a selected substance, such as a thermoplastic, above its melting point, and introducing the melted plastic into the interior of the jacket <part-num-ref name="jacket">30,</part-num-ref>
+ and subsequent cooling, may also be used in a streamer according to the invention. Oil or similar material may also be used to fill the interior of the streamer.    </p>
+    <p id="p-44" num="44">[0033]       The sensor holders <part-num-ref name="sensor holders">32,</part-num-ref>
+ as explained in the Background section herein, are typically molded from a rigid, dense plastic to better protect the seismic sensors therein from damage during handling and use. An exterior configuration of the sensor holder <part-num-ref name="sensor holder">32</part-num-ref>
+ is preferably such that the sensor holder <part-num-ref name="sensor holder">32</part-num-ref>
+ fits snugly within the jacket <part-num-ref name="jacket">30.</part-num-ref>
+ In some examples of a streamer according to the invention, the sensor spacers may also provide <boundary-data type="header">
+        <confidence value="88">10</confidence>
+      </boundary-data>
+      <page-break num="12"/>
+      <boundary-data type="header">PGS-07-O<confidence value="6">1</confidence>
+ <confidence value="86">US</confidence>
+      </boundary-data>
+directional acoustic isolation between the BVF <part-num-ref name="BVF">46</part-num-ref>
+ and the seismic sensor therein. Other sensor holders may be fully exposed to pressure variations inside the jacket <part-num-ref name="jacket">30.</part-num-ref>
+    </p>
+    <p id="p-45" num="45">
+      <confidence value="5">[</confidence>
+0034]       One example of a seismic sensor that can be used with the invention is shown schematically in FIG. 3. The seismic sensor includes a pair of axially opposed, cylindrically encased piezoelectric transducer elements <part-num-ref name="pair of axially opposed, cylindrically encased piezoelectric transducer elements">62.</part-num-ref>
+ Each transducer element <part-num-ref name="pair of axially opposed, cylindrically encased piezoelectric transducer elements 62. Each transducer element">62</part-num-ref>
+ may be disposed in a flanged, cylindrically shaped brass or bronze enclosure <part-num-ref name="flanged, cylindrically shaped brass or bronze enclosure">64.</part-num-ref>
+ The enclosures <part-num-ref name="enclosures">64</part-num-ref>
+ are shown soldered together at their respective flange faces <part-num-ref name="are shown soldered together at their respective flange faces">66.</part-num-ref>
+ The combined assembly of the two transducer elements <part-num-ref name="two transducer elements">62</part-num-ref>
+ each in its respective enclosure <part-num-ref name="each in its respective enclosure">64</part-num-ref>
+ shown in FIG. 3 into a single transducer is referred to as a "pill" <part-num-ref name="&quot;pill&quot;">56</part-num-ref>
+ because of its shape, which is generally right cylindrical with a short length along its axis. Electrical leads <part-num-ref name="short length along its axis. Electrical leads">68</part-num-ref>
+ from the transducer element <confidence value="5">.</confidence>
+62. inside the enclosure <part-num-ref name="enclosure">64</part-num-ref>
+ project through the wall of the enclosure <part-num-ref name="enclosure">64</part-num-ref>
+ and enable electrical connection of the transducer <part-num-ref name="transducer">62</part-num-ref>
+ signal output to recording and/or telemetry circuitry, such as the recording system (FIG. 1).    </p>
+    <p id="p-46" num="46">[0035]      The pill <part-num-ref name="pill">56</part-num-ref>
+ shown in FIG. 3 is the active transducing element of the Teledyne Geophysical Instruments' T-2BX hydrophone referred to above. As commercially sold, the T-2BX hydrophone includes the pill <part-num-ref name="pill">56</part-num-ref>
+ shown in FIG. 3 enclosed in a housing (not shown in FIG. 3). The housing is somewhat asymmetric in shape with respect to the pill <part-num-ref name="pill">56</part-num-ref>
+ enclosed therein such housing may provide a certain degree of asymmetry (or directionality) to the response of the complete T-2BX hydrophone. Therefore, in some implementations, the pill <part-num-ref name="pill">56</part-num-ref>
+ from a hydrophone, such as shown in FIG. 3, or portions of such pill, may be mounted directly inside a sensor holder, as will be further explained below. Alternatively, such pill <part-num-ref name="sensor holder, as will be further explained below. Alternatively, such pill">56</part-num-ref>
+ can be enclosed in a substantially symmetric housing (not shown), such as a molded plastic housing. Irrespective of the housing or casing configuration used for the seismic sensor's transducing element, it is believed that an enclosure with an axis of symmetry may enable mounting the sensor within a sensor holder <part-num-ref name="sensor holder">(32</part-num-ref>
+ in FIG. 2) such that the sensor response is substantially symmetric with respect to a plane normal to the longitudinal axis of the streamer, called "longitudinally symmetric response" herein for convenience.    </p>
+    <boundary-data type="header">
+      <confidence value="88">11</confidence>
+    </boundary-data>
+    <boundary-data type="header">PGS-07-O<confidence value="6">1</confidence>
+ <confidence value="86">US</confidence>
+    </boundary-data>
+    <p id="p-47" num="47">
+      <page-break num="13"/>
+[0036<confidence value="5">]</confidence>
+      Referring to FIG. 4, in some examples, one or more half-pills, shown at 56A as encased transducer 62 with flange surface 66A, may be used individually, rather than joined at the flange faces as shown in FIG. 3. Irrespective of whether a whole pill <part-num-ref name="whole pill">(56</part-num-ref>
+ in FIG. 3) or one or more half pills 56A is used in any example, the generally right cylindrical shape of the transducer element enclosures shown in FIGS. 3 and <part-num-ref name="and">4</part-num-ref>
+ is believed to have substantially symmetrical response to pressure exerted normal to the cylindrical axis of the transducer case. When suitably mounted in a sensor holder, the combination of such sensor and sensor holder may result in substantially longitudinally symmetric response. It is believed that such longitudinally symmetric response may reduce the sensitivity of a seismic sensor streamer to longitudinally traveling pressure waves in the void filler material e.g., (BVF <part-num-ref name="(BVF">46</part-num-ref>
+ in FIG. 2). The sensor holders shown in FIG. 4 generally provides a chamber for enclosing the seismic sensor that is substantially isolated from longitudinally traveling waves inside the streamer, and provides coupling to waves entering the streamer from outside.    </p>
+    <p id="p-48" num="48">
+      <confidence value="5">[</confidence>
+0037]      Another type of seismic sensor that may be used in some examples as a cylindrical hydrophone. One such hydrophone is sold under model number <confidence value="5">S</confidence>
+Q20 by Sensor Technology Limited, Collingwood, Ontario, Canada L9Y 4K1. A configuration of such cylindrical hydrophone is shown in FIG. 5. The hydrophone <part-num-ref name="hydrophone">156</part-num-ref>
+ includes a substantially cylindrical transducer enclosure <part-num-ref name="substantially cylindrical transducer enclosure">164.</part-num-ref>
+ Signal leads <part-num-ref name="substantially cylindrical transducer enclosure 164. Signal leads">168</part-num-ref>
+ exit the enclosure as shown.    </p>
+    <p id="p-49" num="49">
+      <confidence value="5">[</confidence>
+0038<confidence value="5">]</confidence>
+      Another example of a sensor disposed in a sensor holder is shown in FIG. 6. The sensor holder <part-num-ref name="sensor holder">32</part-num-ref>
+ may be generally in the form of a right cylinder oriented along the longitudinal axis of the streamer <part-num-ref name="streamer">(10</part-num-ref>
+ in FIG. 1). Passages <part-num-ref name="in FIG. 1). Passages">58</part-num-ref>
+ may extend through the sensor holder <part-num-ref name="sensor holder">32</part-num-ref>
+ near the circumferential edges of the holder <part-num-ref name="holder">32</part-num-ref>
+ to provide a place for the cable <part-num-ref name="cable">(40</part-num-ref>
+ in FIG. 2). Other passages <part-num-ref name="in FIG. 2). Other passages">54</part-num-ref>
+ may be provided for the strength members <part-num-ref name="strength members">(42</part-num-ref>
+ in FIG. 2). A central channel <part-num-ref name="central channel">59</part-num-ref>
+ may be disposed roughly in the center of the sensor holder <part-num-ref name="sensor holder">32</part-num-ref>
+ to provide a place for mounting a pill <part-num-ref name="pill">56</part-num-ref>
+ such as explained with reference to FIG. 3.    </p>
+    <p id="p-50" num="50">Preferably the pill <part-num-ref name="pill">56</part-num-ref>
+ is arranged such that the case is symmetrically disposed about a plane normal to the longitudinal axis 32A of the sensor holder <part-num-ref name="sensor holder">32.</part-num-ref>
+ By so arranging the pill <part-num-ref name="pill">56</part-num-ref>
+ in the sensor holder <part-num-ref name="sensor holder">32,</part-num-ref>
+ it is believed that the response of the sensor (pill <part-num-ref name="sensor (pill">56)</part-num-ref>
+ will <boundary-data type="header">
+        <confidence value="88">12</confidence>
+      </boundary-data>
+      <page-break num="14"/>
+      <boundary-data type="header">
+        <confidence value="885">PGS</confidence>
+-07-<confidence value="5586">OlUS</confidence>
+      </boundary-data>
+be substantially longitudinally symmetric (symmetric with respect to a plane normal to the longitudinal axis 32A).    </p>
+    <p id="p-51" num="51">
+      <confidence value="5">[</confidence>
+0039]      Another type of sensor holder is shown in oblique view in FIG. 7A and in end view in FIG. 7B. The sensor holder <part-num-ref name="sensor holder">32</part-num-ref>
+ may be made from plastic as described above.    </p>
+    <p id="p-52" num="52">The shape of the sensor holder <part-num-ref name="sensor holder">32</part-num-ref>
+ may be such that only a small portion of the circumference of the sensor holder traverses a diameter approximately the same as the inner diameter of the jacket <part-num-ref name="jacket">(30</part-num-ref>
+ in FIG. 2). Such portions are shown at <part-num-ref name="in FIG. 2). Such portions are shown at">154</part-num-ref>
+ and are proximate to and surround passages <part-num-ref name="and are proximate to and surround passages">54</part-num-ref>
+ for insertion of the strength members <part-num-ref name="strength members">(42</part-num-ref>
+ in FIG.    </p>
+    <p id="p-53" num="53">2). A central opening <part-num-ref name="central opening">70</part-num-ref>
+ for the seismic sensor <part-num-ref name="seismic sensor">56</part-num-ref>
+ may extend longitudinally along the entire length of the sensor holder <part-num-ref name="sensor holder">32.</part-num-ref>
+ The central opening <part-num-ref name="central opening">70</part-num-ref>
+ may include opposed, longitudinally extending grooves or channels 70A formed into the wall of the central  <confidence value="6">.</confidence>
+    </p>
+    <p id="p-54" num="54">opening 70. The sensor <part-num-ref name="sensor">56</part-num-ref>
+ may be retained in the sensor holder by applying soft elastomer bars <part-num-ref name="sensor holder by applying soft elastomer bars">72</part-num-ref>
+ between the exterior of the sensor <part-num-ref name="sensor">56</part-num-ref>
+ and the grooves 70A. The elastomer bars <part-num-ref name="elastomer bars">72</part-num-ref>
+ may have size selected to provide a friction fit between the sensor holder <part-num-ref name="sensor holder">32</part-num-ref>
+ and the sensor <part-num-ref name="sensor">56.</part-num-ref>
+ The bars <part-num-ref name="bars">72</part-num-ref>
+ may be made from an elastomer having compressibility selected to provide acoustic isolation between the sensor holder <part-num-ref name="sensor holder">32</part-num-ref>
+ and the sensor <part-num-ref name="sensor">56.</part-num-ref>
+ Preferably, the sensor <part-num-ref name="sensor">56</part-num-ref>
+ is disposed in the sensor holder <part-num-ref name="sensor holder">32</part-num-ref>
+ at its longitudinal center and is arranged such that a bisecting plane of the sensor <part-num-ref name="sensor">56</part-num-ref>
+ is substantially parallel to the longitudinal axis of the sensor holder <part-num-ref name="sensor holder">32.</part-num-ref>
+ Such arrangement may result in the acoustic response of the combined sensor and sensor holder being substantially longitudinally symmetric.    </p>
+    <p id="p-55" num="55">
+      <confidence value="5">[</confidence>
+0040]      FIGS. 8A and 8B show another arrangement of sensor disposed in a sensor holder in oblique view and end view, respectively. The sensor holder <part-num-ref name="sensor holder">32</part-num-ref>
+ may be configured substantially the same as the sensor holder shown in FIGS. 7A and 7B. In FIGS. 8A and 8B, however, the seismic sensor <part-num-ref name="seismic sensor">56</part-num-ref>
+ may be disposed in the central opening <part-num-ref name="central opening">70</part-num-ref>
+ such that the sensor's axis of symmetry <part-num-ref name="sensor's axis of symmetry">256</part-num-ref>
+ is substantially coaxial with the longitudinal axis <part-num-ref name="longitudinal axis">270</part-num-ref>
+ of the sensor holder <part-num-ref name="sensor holder">32.</part-num-ref>
+ In FIG. 8B, the sensor <part-num-ref name="sensor">56</part-num-ref>
+ is shown as being retained in the sensor holder <part-num-ref name="sensor holder">32</part-num-ref>
+ using elastomer mounting tabs <part-num-ref name="using elastomer mounting tabs">33</part-num-ref>
+ to retain the sensor <part-num-ref name="sensor">56</part-num-ref>
+ inside the opening <part-num-ref name="opening">70.</part-num-ref>
+ Other examples may use elastomer rings (not shown). As in the previous example of FIGS. 7A and 7B, the sensor <part-num-ref name="sensor">56</part-num-ref>
+ is preferably disposed substantially at the <boundary-data type="header">
+        <confidence value="88">13</confidence>
+      </boundary-data>
+      <page-break num="15"/>
+      <boundary-data type="header">PGS-07-O<confidence value="6">1</confidence>
+ <confidence value="86">US</confidence>
+      </boundary-data>
+longitudinal center of the sensor holder <part-num-ref name="sensor holder">32</part-num-ref>
+ such that the acoustic response of the combined sensor <part-num-ref name="combined sensor">56</part-num-ref>
+ and sensor holder <part-num-ref name="and sensor holder">32</part-num-ref>
+ is substantially longitudinally symmetric.    </p>
+    <p id="p-56" num="56">
+      <confidence value="5">[</confidence>
+0041]      Another arrangement, having a differently configured sensor holder is shown in FIGS. 9A and 9B in oblique view and end view, respectively. The sensor holder <part-num-ref name="sensor holder">32</part-num-ref>
+ may be substantially cylindrically shaped, and have an external diameter substantially the same as the inner diameter of the jacket <part-num-ref name="jacket">(30</part-num-ref>
+ in FIG. 2). The sensor holder <part-num-ref name="sensor holder">32</part-num-ref>
+ may include longitudinal through passages <part-num-ref name="may include longitudinal through passages">58</part-num-ref>
+ proximate the outer edge for passage of the cable <part-num-ref name="cable">(40</part-num-ref>
+ in FIG. 2) other devices in the streamer <part-num-ref name="streamer">(10</part-num-ref>
+ in FIG. 1). The sensor holder may also include longitudinal through passages <part-num-ref name="sensor holder may also include longitudinal through passages">54</part-num-ref>
+ for the strength members <part-num-ref name="strength members">(42</part-num-ref>
+ in FIG. 2). The sensor holder <part-num-ref name="sensor holder">32</part-num-ref>
+ may include a central opening <part-num-ref name="central opening">70</part-num-ref>
+ disposed in the radial center of the sensor holder .32 and extending along the entire length of the sensor holder for disposing the seismic sensor <part-num-ref name="seismic sensor">56.</part-num-ref>
+ The seismic sensor <part-num-ref name="seismic sensor">56</part-num-ref>
+ is shown mounted in substantially the same configuration as shown in FIGS. 8A and 8B, and as explained with reference to such figures may be disposed in the longitudinal center of the central opening <part-num-ref name="central opening">70</part-num-ref>
+ using elastomer tabs <part-num-ref name="using elastomer tabs">33</part-num-ref>
+ or the like and arranged such that the sensor's axis of symmetry is substantially coaxial with the longitudinal axis of the sensor holder <part-num-ref name="sensor holder">32.</part-num-ref>
+ Alternatively, the sensor <part-num-ref name="sensor">56</part-num-ref>
+ may be mounted in a sensor holder as in FIGS. 9A and 9B in the manner explained above with reference to FIGS. 7A and 7B.    </p>
+    <p id="p-57" num="57">
+      <confidence value="5">[</confidence>
+0042<confidence value="5">]</confidence>
+      Referring once again to FIG. 2, another aspect of the invention is to arrange each sensor holder <part-num-ref name="invention is to arrange each sensor holder">32</part-num-ref>
+ so that a longitudinal distance from the sensor holder <part-num-ref name="sensor holder">32</part-num-ref>
+ to an adjacent buoyancy spacer <part-num-ref name="adjacent buoyancy spacer">34</part-num-ref>
+ disposed on each side of the sensor holder <part-num-ref name="sensor holder">32</part-num-ref>
+ is the same. Thus, the arrangement of sensor holder <part-num-ref name="arrangement of sensor holder">32</part-num-ref>
+ and opposed buoyancy spacers <part-num-ref name="and opposed buoyancy spacers">34</part-num-ref>
+ is substantially symmetric with respect to a bisecting plane of the sensor holder <part-num-ref name="sensor holder">32</part-num-ref>
+ perpendicular to the longitudinal axis of the streamer. In another aspect of the invention, the cable <part-num-ref name="cable">40</part-num-ref>
+ may <confidence value="88">be</confidence>
+ arranged such that any catenary in the cable <part-num-ref name="cable">40</part-num-ref>
+ between successive sensor holders <part-num-ref name="between successive sensor holders">32</part-num-ref>
+ and buoyancy spacers <part-num-ref name="and buoyancy spacers">34</part-num-ref>
+ is substantially symmetrically arranged.    </p>
+    <p id="p-58" num="58">
+      <confidence value="5">[</confidence>
+0043]      A streamer made using sensor spacers and sensor arrays as described herein may provide substantially reduced effect of noise related to axial vibrations than streamers made according to structures known in the art prior to the present invention.    </p>
+    <boundary-data type="header">
+      <confidence value="88">14</confidence>
+    </boundary-data>
+    <boundary-data type="header">PGS-07-<confidence value="55">O1</confidence>
+ <confidence value="88">US</confidence>
+    </boundary-data>
+    <p id="p-59" num="59">
+      <page-break num="16"/>
+      <confidence value="5">[</confidence>
+0044<confidence value="5">]</confidence>
+      While the invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of this disclosure, will appreciate that other embodiments can be devised which do not depart from the scope of the invention as disclosed herein. Accordingly, the scope of the invention should be limited only by the attached claims.    </p>
+    <boundary-data type="header">
+      <confidence value="88">15</confidence>
+    </boundary-data>
+  </description>
+</us-patent-application>
+

applicant/12256664.xml

@@ -0,0 +1,793 @@
+<?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>12256664</doc-number>
+        <date>2008-10-23</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <boundary-data type="header">Attorney Docket No.: 20080238                                        Patent</boundary-data>
+    <boundary-data type="header">Ditthavong Mo<confidence value="66">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483    </boundary-data>
+    <heading id="h-1">METHOD AND SYSTEM FOR LOGGING AND STORING</heading>
+    <heading id="h-2">HETEROGENEOUS COMMUNICATION SESSIONS</heading>
+    <heading id="h-3">BACKGROUND INFORMATION</heading>
+    <p id="p-1" num="1">
+      <confidence value="5">1</confidence>
+0001<confidence value="5">1</confidence>
+   Modern communications systems offer a wide variety of mechanisms and devices for conducting a communication session. As a result, users often find themselves engaging in related communication sessions that take place in many different forms over different communication  devices (i.e., heterogeneous communications).  With the increasing sophistication and adoption of communication technologies, users can move from one form of communication to another when addressing a particular topic or issue. For example, a user receives an E-mail message about an urgent matter and follows up on the E-mail message with a telephone call. After the telephone call, the user conducts a video conference to discuss the matter f<confidence value="25">m-</confidence>
+ther.  Unfortunately, the ease of transitioning between different forms of communication can also make it difficult for the user to keep track of all related communications. That is, the user typically would have to track all of the various forms of communications individually to have a complete record of how the user handled the urgent matter.    </p>
+    <p id="p-2" num="2">
+      <confidence value="688882">[00021</confidence>
+   Another problem the user may face is the difficulty of referencing all of the various forms of communications through one designated communication device. The user in the situation of the example above may find it difficult or even impossible to access the full history of communication sessions without having access to all previously used communication devices.    </p>
+    <p id="p-3" num="3">Traditional communications systems have not provided the ability to automatically track all related communication sessions when these communication sessions originate on different devices.</p>
+    <p id="p-4" num="4">
+      <confidence value="5">1</confidence>
+0003<confidence value="5">1</confidence>
+   In parallel, communications service providers are continually challenged to develop new services and features to remain competitive and to develop new sources of revenue.    </p>
+    <boundary-data type="header">
+      <confidence value="8">1</confidence>
+    </boundary-data>
+    <boundary-data type="header">Attorney Docket No.: 20080238                                         Patent</boundary-data>
+    <boundary-data type="header">Ditthavong Mo<confidence value="66">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483    </boundary-data>
+    <p id="p-5" num="5">
+      <page-break num="2"/>
+      <confidence value="4">[</confidence>
+0004<confidence value="2">1</confidence>
+   Therefore, there is a need for an approach that provides for automated logging and retrieval of heterogeneous communication sessions from any user-designated communication device, while creating a new source of revenue for communication service providers.    </p>
+    <boundary-data type="header">
+      <confidence value="8">2</confidence>
+    </boundary-data>
+    <boundary-data type="header">Attorney Docket No.: 20080238                                        Patent</boundary-data>
+    <boundary-data type="header">Ditthavong Mo<confidence value="66">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483    </boundary-data>
+    <heading id="h-4">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
+    <p id="p-6" num="6">
+      <page-break num="3"/>
+      <confidence value="5">1</confidence>
+0005<confidence value="5">1</confidence>
+   Various exempla<confidence value="8">r</confidence>
+y embodiments are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which like reference numerals refer to similar elements and in which:    </p>
+    <p id="p-7" num="7">
+      <confidence value="5">[</confidence>
+0006<confidence value="5">1</confidence>
+   FIG. <confidence value="4">1</confidence>
+ is a diagram of a system capable of creating a workspace and then logging and storing heterogeneous communication sessions within the workspace, according to an exemplary embodiment;    </p>
+    <p id="p-8" num="8">
+      <confidence value="5">1</confidence>
+0007<confidence value="5">1</confidence>
+   FIG. 2 is a diagram of the components of a workspace manager platform, according to an exemplary embodiment;    </p>
+    <p id="p-9" num="9">
+      <confidence value="5">1</confidence>
+0008<confidence value="5">1</confidence>
+   FIG. 3 is a flowchart of a process for creating a workspace and then logging heterogeneous communication sessions within the workspace, according to an exemplary embodiment;    </p>
+    <p id="p-10" num="10">
+      <confidence value="5">1</confidence>
+0009<confidence value="5">1</confidence>
+   FIG. 4 is a flowchart of a process for recording a communication session to a workspace, according to an exemplary embodiment;    </p>
+    <p id="p-11" num="11">
+      <confidence value="4">1</confidence>
+0010<confidence value="5">1</confidence>
+   FIG. 5 is a flowchart of a process for re-homing a workspace to an environment specified by the user, according to an exemplary embodiment;    </p>
+    <p id="p-12" num="12">
+      <confidence value="5">[</confidence>
+0011<confidence value="5">1</confidence>
+   FIG. 6 is a flowchart of a process for allowing access to a workspace by another user, according to an exemplary embodiment;    </p>
+    <p id="p-13" num="13">
+      <confidence value="5">1</confidence>
+0012<confidence value="5">1</confidence>
+   FIG. 7 is a flowchart of a process for obtaining supplemental information about a workspace or communication session, according to an exempla<confidence value="8">r</confidence>
+y embodiment;    </p>
+    <p id="p-14" num="14">
+      <confidence value="5">1</confidence>
+0013<confidence value="5">1</confidence>
+   FIG. 8 is a flowchart of a process for receiving a command from a user to organize, annotate, or search a workspace, according to an exemplary embodiment;    </p>
+    <p id="p-15" num="15">
+      <confidence value="5">[</confidence>
+0014<confidence value="5">1</confidence>
+   FIG. 9 is a flowchart of a process for delivering a workspace to an application, according to an exemplary embodiment;    </p>
+    <boundary-data type="header">
+      <confidence value="8">3</confidence>
+    </boundary-data>
+    <boundary-data type="header">Attorney Docket No.: 20080238                                         Patent</boundary-data>
+    <boundary-data type="header">Ditthavong Mo<confidence value="66">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483    </boundary-data>
+    <p id="p-16" num="16">
+      <page-break num="4"/>
+      <confidence value="5">[</confidence>
+0015<confidence value="5">]</confidence>
+   FIG. 10 is a flowchart of a process for using the workspace manager to record a communication session to a workspace from a user's perspective, according to an exemplary embodiment;    </p>
+    <p id="p-17" num="17">
+      <confidence value="5">1</confidence>
+0016<confidence value="5">1</confidence>
+   FIG. 11 is a flowchart of a process for using a portal to access the functions of the workspace manager from a user's perspective, according to an exemplary embodiment;    </p>
+    <p id="p-18" num="18">
+      <confidence value="5">[</confidence>
+0017<confidence value="4">1</confidence>
+   FIGs. 12A-12C depict exemplary graphical user interfaces (GUIs) for using a portal to access the f<confidence value="8">u</confidence>
+nctions of the workspace manager, according to various embodiments of the present invention; and <part-num-ref name="present invention; and">
+        <confidence value="5">1</confidence>
+0018<confidence value="5">1</confidence>
+      </part-num-ref>
+   FIG. 13 is a diagram of a computer system that can be used to implement various exempla<confidence value="8">r</confidence>
+y embodiments.    </p>
+    <boundary-data type="header">
+      <confidence value="8">4</confidence>
+    </boundary-data>
+    <boundary-data type="header">Attorney Docket No.: 20080238                                        Patent</boundary-data>
+    <boundary-data type="header">Ditthavong Mo<confidence value="66">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483    </boundary-data>
+    <heading id="h-5">DESCRIPTION OF THE PREFERRED EMBODIMENT</heading>
+    <p id="p-19" num="19">
+      <page-break num="5"/>
+      <confidence value="5">1</confidence>
+0019<confidence value="5">1</confidence>
+   A preferred apparatus, method, and system for logging and storing heterogeneous communication sessions are described. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the preferred embodiments of the invention. It is apparent, however, that the preferred embodiments may be practiced without these specific details or with an equivalent arrangement.    </p>
+    <p id="p-20" num="20">In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the preferred embodiments of the invention.</p>
+    <p id="p-21" num="21">
+      <confidence value="5">1</confidence>
+0020<confidence value="5">1</confidence>
+   It is contemplated that the various exemplary embodiments described herein have applicability to any device capable of communicating over a network, such as a multimedia device, a wireless application protocol (WAP) enabled cellular telephone, a home communication terminal (HCT), a digital home communication terminal (DHCT), landline connected to a Public Switched Telephone Network (PSTN), a personal digital assistant (PDA), a television, and/or a personal computer (PC), as well as other like technologies and customer premises equipment (CPE).    </p>
+    <p id="p-22" num="22">
+      <confidence value="5">1</confidence>
+0021<confidence value="5">1</confidence>
+   FIG. <confidence value="5">1</confidence>
+ is a diagram of a system capable of creating a workspace and then logging and storing heterogeneous communication sessions within the workspace, according to an exemplary embodiment.   For the purposes of illustration, a mechanism  for logging and storing heterogeneous communication sessions is described with respect to a communication system <part-num-ref name="communication system">100</part-num-ref>
+ that includes a radio network <part-num-ref name="radio network">101,</part-num-ref>
+ a data network <part-num-ref name="data network">103,</part-num-ref>
+ and a telephony network <part-num-ref name="telephony network">105.</part-num-ref>
+ These networks 101-105 can support various communication sessions, e.g., voice, data, video, E-mail, etc. A workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ provides a capability to log and/or store these heterogeneous communication sessions. As shown, the platform <part-num-ref name="platform">107</part-num-ref>
+ resides within the network side. In addition (or alternatively), the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ may reside within customer premises equipment (CPE) (not shown). Specifically, the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ enables automated and efficient organization of a user's heterogeneous communication sessions by creating a workspace (e.g., an electronic folder) for logging and storing the user's communication sessions for later reference and/or retrieval. The heterogeneous communication <boundary-data type="header">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+      <page-break num="6"/>
+      <boundary-data type="header">Attorney Docket No.: 20080238                                        Patent</boundary-data>
+      <boundary-data type="header">Ditthavong Mo<confidence value="66">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483      </boundary-data>
+sessions may occur in different formats, over different communication devices, and at va<confidence value="8">r</confidence>
+ying ti<confidence value="8">m</confidence>
+es.    </p>
+    <p id="p-23" num="23">
+      <confidence value="5">[</confidence>
+0022<confidence value="2">]</confidence>
+   It is contemplated that the radio network <part-num-ref name="radio network">101</part-num-ref>
+ may be, for example, a cellular network and may employ various technologies including code division multiple access (CDMA), enhanced data rates for global evolution (EDGE), general packet radio service (GPRS), global system for mobile communications (GSM), Internet protocol multimedia subsystem (IMS), universal mobile telecommunications system (<confidence value="2222">UMTS</confidence>
+), etc., as well as any other suitable wireless medium, e.g., microwave access (WiMAX), Long Term Evolution (LTE) networks, wireless fidelity (WiFi), satellite, and the like. In addition, the data network <part-num-ref name="data network">103</part-num-ref>
+ may be any local area network (LAN), metropolitan area network (MAN), wide area network (WAN), the Internet, or any other suitable packet-switched network, such as a commercially owned, proprietary packet- switched network, e.g., a proprietary cable or fiber-optic network.    </p>
+    <p id="p-24" num="24">
+      <confidence value="5">[</confidence>
+0023   As discussed above, a user often employ many different for<confidence value="8">m</confidence>
+s of communications (e.g., voice communication, text-based communication, video communication, multimedia conferencing, or a combination thereof) on many different devices (e.g., home telephone, mobile telephone, work computer, etc.) to execute a particular task or assignment. While having a wide variety of communication options can often be helpful, this poses a challenge when a comprehensive record spanning all the various forms of all communications is needed.    </p>
+    <p id="p-25" num="25">
+      <confidence value="5">1</confidence>
+0024<confidence value="5">1</confidence>
+   A typical scenario involving the use of numerous communication means is as follows.    </p>
+    <p id="p-26" num="26">The user receives a business-related text message on a mobile telephone while at home. The user calls the sender of the E-mail from a home telephone line and determines the need for an immediate video conference. The user conducts the video conference from a home television and leaves for the office after completing the conference. On route to the office, the user makes several related calls from the user's mobile telephone and receives additional related E-mails on the user's E-mail device. The user arrives at the office and wants a "workspace" of all the <confidence value="8">r</confidence>
+elated communication sessions available via the user's work computer. In this case, the workspace would include all the user's activities (i.e., text message, home phone originated call, video conference conducted on home television, E-mail messages, and mobile phone calls) for the business-related issue the user is working on. However, traditionally, little attention has been <boundary-data type="header">
+        <confidence value="8">6</confidence>
+      </boundary-data>
+      <page-break num="7"/>
+      <boundary-data type="header">Attorney Docket No.: 20080238                                        Patent</boundary-data>
+      <boundary-data type="header">Ditthavong Mo<confidence value="66">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483      </boundary-data>
+afforded to giving the user the capability to organize, correlate, and recall heterogeneous communications. Thus, it is apparent that improvements are needed to enable the user to log related heterogeneous communication sessions within a central workspace to facilitate obtaining a comprehensive histo<confidence value="8">r</confidence>
+y of related communications. For instance, the user may want to review the histo<confidence value="8">r</confidence>
+y of communication sessions through a work personal computer even though one or more of the communication sessions may have taken place on any number of devices such as a cellular telephone, a video terminal, or a home telephone.    </p>
+    <p id="p-27" num="27">
+      <confidence value="5">1</confidence>
+0025<confidence value="5">1</confidence>
+   To address this problem, the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ creates one or more workspaces, logs the user's communication sessions into these workspaces, and presents the workspaces to the user on a user-designated communication device. In exemplary embodiments, the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ may also be configured to record the communication sessions into an appropriate workspace. Once the user's communication sessions are logged and/or stored in workspaces, the platform <part-num-ref name="platform">107</part-num-ref>
+ may leverage the resources of the communications network to, for instance, convert the communication sessions into a searchable format, obtain supplemental info<confidence value="77">rm</confidence>
+ation about the communication sessions, re-home the workspace (e.g., by translating the communication sessions stored within the workspace) to other environments or communication devices, control access to the workspace, and deliver the communication sessions stored in a workspace to other applications. In this way, the platform <part-num-ref name="platform">107</part-num-ref>
+ enables the user to easily create a history of related communication sessions and access the history from any communication device.    </p>
+    <p id="p-28" num="28">
+      <confidence value="5">1</confidence>
+0026<confidence value="5">1</confidence>
+   As seen in FIG. <confidence value="5">1</confidence>
+, the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ is connected to a multimedia device <part-num-ref name="multimedia device">109</part-num-ref>
+ (e.g., mobile device, or handset) via a cellular gateway (not shown) over a radio network <part-num-ref name="radio network">101.</part-num-ref>
+ The multimedia device <part-num-ref name="multimedia device">109</part-num-ref>
+ may, for instance, provide access to the services of the workspace manager platform <part-num-ref name="workspace manager platform">107.</part-num-ref>
+ The workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ also has connectivity to a data network <part-num-ref name="data network">103</part-num-ref>
+ that supports an end terminal <part-num-ref name="end terminal">
+        <confidence value="555">111</confidence>
+.      </part-num-ref>
+ End terminal <part-num-ref name="end terminal 111. End terminal">111</part-num-ref>
+ may be any computing device (e.g., Personal Digital Assistant (PDA), personal computer, laptop, etc.) or co<confidence value="8">m</confidence>
+munication device (e.g., a Voice over Internet Protocol (VoIP) station, a video conferencing terminal, a digital home communication terminal (DHCT), a television set-top box (STB)) <boundary-data type="header">
+        <confidence value="8">7</confidence>
+      </boundary-data>
+      <page-break num="8"/>
+      <boundary-data type="header">Attorney Docket No.: 20080238                                         Patent</boundary-data>
+      <boundary-data type="header">Ditthavong Mo<confidence value="66">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483      </boundary-data>
+capable of providing access to the services of the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ and supporting communication sessions over data network <part-num-ref name="and supporting communication sessions over data network">103.</part-num-ref>
+    </p>
+    <p id="p-29" num="29">
+      <confidence value="5">[</confidence>
+0027<confidence value="5">1</confidence>
+   In addition, the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ has connectivity to a telephony network <part-num-ref name="telephony network">105</part-num-ref>
+ through data network <part-num-ref name="through data network">103</part-num-ref>
+ and a telephony gateway <part-num-ref name="telephony gateway">113.</part-num-ref>
+ In this example, the telephony network <part-num-ref name="telephony network">105</part-num-ref>
+ can serve an end terminal <part-num-ref name="end terminal">115,</part-num-ref>
+ which may provide access to the services of the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ and include a voice station for initiating a voice call to other end terminals capable of supporting the voice call. End terminal <part-num-ref name="voice call. End terminal">115</part-num-ref>
+ may, for example, include a home communication terminal (<confidence value="5">H</confidence>
+CT), and other telephonic devices, with connectivity to a Public Switched Telephone Network (PSTN), which may be a part of the telephony network <part-num-ref name="telephony network">105.</part-num-ref>
+    </p>
+    <p id="p-30" num="30">
+      <confidence value="5">[</confidence>
+0028<confidence value="5">1</confidence>
+   The data network <part-num-ref name="data network">103</part-num-ref>
+ additionally permits a host <part-num-ref name="host">117</part-num-ref>
+ to access workspace manager platform <part-num-ref name="to access workspace manager platform">107</part-num-ref>
+ functions and preferences via a graphical user interface (GUI) such as a browser application or any web-based application for multimedia device <part-num-ref name="browser application or any web-based application for multimedia device">109,</part-num-ref>
+ end terminal <part-num-ref name="browser application or any web-based application for multimedia device 109, end terminal">
+        <confidence value="555">111</confidence>
+,      </part-num-ref>
+ and/or end terminal <part-num-ref name="browser application or any web-based application for multimedia device 109, end terminal 111, and/or end terminal">115.</part-num-ref>
+ Under one scenario, it is contemplated that a user can configure workspace manager services, functions, and preferences for multimedia device <part-num-ref name="user can configure workspace manager services, functions, and preferences for multimedia device">109,</part-num-ref>
+ end terminal <part-num-ref name="user can configure workspace manager services, functions, and preferences for multimedia device 109, end terminal">111,</part-num-ref>
+ and/or end terminal <part-num-ref name="user can configure workspace manager services, functions, and preferences for multimedia device 109, end terminal 111, and/or end terminal">115</part-num-ref>
+ using the host <part-num-ref name="host">117</part-num-ref>
+ via a web browser.    </p>
+    <p id="p-31" num="31">
+      <confidence value="2">1</confidence>
+0029<confidence value="5">1</confidence>
+   In one embodiment, the workspace manager service is a managed service, whereby a service provider operates the platform <part-num-ref name="platform">107</part-num-ref>
+ to serve one or more subscribers.    </p>
+    <p id="p-32" num="32">
+      <confidence value="5">1</confidence>
+0030<confidence value="5">1</confidence>
+   FIG. 2 is a diagram of the components of a workspace manager platform, according to an exempla<confidence value="8">r</confidence>
+y embodiment. By way of example, the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ may include one or more of the modules to provide logging and storage of communication sessions.    </p>
+    <p id="p-33" num="33">A workspace creation module 201 is utilized for creating and defining a workspace. A log module <part-num-ref name="log module">203</part-num-ref>
+ permits logging a user's heterogeneous communication sessions within a workspace;    </p>
+    <p id="p-34" num="34">and a recording module <part-num-ref name="recording module">205</part-num-ref>
+ records a communication session to the workspace. A re-homing module <part-num-ref name="re-homing module">207</part-num-ref>
+ enables access to a workspace through a user-specified environment (e.g., a specified communication device). Also, a user access module <part-num-ref name="user access module">209</part-num-ref>
+ controls access to a workspace. A supplemental information module <part-num-ref name="supplemental information module">211</part-num-ref>
+ can obtain additional information (e.g., communication session participants, communication session duration, communication session <boundary-data type="header">
+        <confidence value="8">8</confidence>
+      </boundary-data>
+      <page-break num="9"/>
+      <boundary-data type="header">Attorney Docket No.: 20080238                                        Patent</boundary-data>
+      <boundary-data type="header">Ditthavong Mo<confidence value="66">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483      </boundary-data>
+type, etc.) about a communication session or workspace. An organization module <part-num-ref name="organization module">213</part-num-ref>
+ for interacting (e.g., copying, pasting, renaming, etc.) with a workspace.    </p>
+    <p id="p-35" num="35">
+      <confidence value="2">1</confidence>
+0031<confidence value="5">]</confidence>
+   Further, an annotation module <part-num-ref name="annotation module">215</part-num-ref>
+ allows users to add notes, comments, and/or attachments to a workspace or communication session. A search module <part-num-ref name="search module">217</part-num-ref>
+ is utilized to conduct searches of a workspace and its contents. A content delive<confidence value="8">r</confidence>
+y module <part-num-ref name="content delivery module">219</part-num-ref>
+ for delivering the contents of a workspace to another application.    </p>
+    <p id="p-36" num="36">
+      <confidence value="5">[</confidence>
+0032<confidence value="4">]</confidence>
+   The workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ may also have connectivity to a database <part-num-ref name="database">221</part-num-ref>
+ of user preferences, a database <part-num-ref name="database">223</part-num-ref>
+ of workspace history, and a media session controller such as an IP Multimedia Subsystem (IMS) session/media control platform <part-num-ref name="IP Multimedia Subsystem (IMS) session/media control platform">225.</part-num-ref>
+ The user preferences stored in database <part-num-ref name="user preferences stored in database">221</part-num-ref>
+ may include user settings and configuration information for the workspace manager platform  <part-num-ref name="workspace manager platform">107</part-num-ref>
+ such as whether to automatically record specific communication sessions, types of communication sessions to monitor, and available communication devices. The database <part-num-ref name="database">223</part-num-ref>
+ of workspace histo<confidence value="8">r</confidence>
+y may include workspaces, recorded communication sessions, supplemental information regarding the communication sessions or workspaces, translations of the communication sessions, and/or other information associated with a workspace or communication session.    </p>
+    <p id="p-37" num="37">
+      <confidence value="5">[</confidence>
+0033<confidence value="4">]</confidence>
+   In one embodiment, the IMS session/media control <confidence value="22222222">platfonn</confidence>
+ <part-num-ref name="IMS session/media control platfonn">225</part-num-ref>
+ provides the signaling and communication session controls to invoke the workspace <confidence value="8">m</confidence>
+anager platform <part-num-ref name="workspace manager platform">107.</part-num-ref>
+    </p>
+    <p id="p-38" num="38">Specifically, the IMS platform <part-num-ref name="IMS platform">225</part-num-ref>
+ can detect the initiation of a communication session involving a user and direct the communication session to the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ for processing. The workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ then, for instance, may log and store the communication session in the appropriate workspace based on user preferences.    </p>
+    <p id="p-39" num="39">
+      <confidence value="5">[</confidence>
+0034<confidence value="4">]</confidence>
+   To assist in <confidence value="2222222222">perfonning</confidence>
+ these functions, the IMS platform <part-num-ref name="IMS platform">225</part-num-ref>
+ may include additional IMS components <part-num-ref name="may include additional IMS components">227</part-num-ref>
+ and a media resource f<confidence value="8">u</confidence>
+nction <part-num-ref name="media resource function">229.</part-num-ref>
+ The additional IMS components <part-num-ref name="additional IMS components">227</part-num-ref>
+ can assist the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ in obtaining supplemental information about a communication session or workspace such as communication session participants, participant contact information, participant locations, time and duration of a com<confidence value="8">m</confidence>
+unication session, communication session type, associated media (e.g., messages, audio, and video), etc. By way <boundary-data type="header">
+        <confidence value="8">9</confidence>
+      </boundary-data>
+      <page-break num="10"/>
+      <boundary-data type="header">Attorney Docket No.: 20080238                                        Patent</boundary-data>
+      <boundary-data type="header">Ditthavong Mo<confidence value="66">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483      </boundary-data>
+of example, IMS components <part-num-ref name="messages, audio, and video), etc. By way of example, IMS components">227</part-num-ref>
+ may include a presence server <part-num-ref name="presence server">231</part-num-ref>
+ for determining the presence status of participants in a communication session and a location server <part-num-ref name="location server">233</part-num-ref>
+ for determining their locations. It is contemplated that additional servers, components, and the like may be added to the set of IMS components <part-num-ref name="set of IMS components">227</part-num-ref>
+ available to assist the workspace manager platform <part-num-ref name="workspace manager platform">107.</part-num-ref>
+    </p>
+    <p id="p-40" num="40">10035<confidence value="5">]</confidence>
+   Another important function, in certain exemplary embodiments, of the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ is the ability to access a workspace of stored communication sessions from any designated communication device regardless of the format of the stored communication sessions. In other words, the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ enables a user to "re-home" or move a recorded workspace from one communication device to another. To accomplish this re- <confidence value="885">hom</confidence>
+ing, the workspace manager platform interacts with, for example, the media resource function <part-num-ref name="media resource function">229</part-num-ref>
+ of IMS platform <part-num-ref name="of IMS platform">225</part-num-ref>
+ to selectively translate a communication session or workspace for presentation on a designated communication device. The media resource function <part-num-ref name="media resource function">229</part-num-ref>
+ may include a voice recognition media resource <part-num-ref name="voice recognition media resource">235,</part-num-ref>
+ a text-to-speech media resource <part-num-ref name="text-to-speech media resource">237,</part-num-ref>
+ and/or a video mixing/overlay/closed captioning media resource <part-num-ref name="video mixing/overlay/closed captioning media resource">239</part-num-ref>
+ to translate a communication session and output the session in a format suitable for presentation on the designated device or environment.    </p>
+    <p id="p-41" num="41">10036<confidence value="5">1</confidence>
+   The voice recognition media resource <part-num-ref name="voice recognition media resource">235</part-num-ref>
+ translates incoming speech into text.    </p>
+    <p id="p-42" num="42">Namely, the voice recognition media resource <part-num-ref name="voice recognition media resource">235</part-num-ref>
+ is configured to convert spoken language (analog signal) into textual form (digital signal) by extracting meaning from the user's spoken utterances and producing semantic information in the form of text. The text-to-speech media resource <part-num-ref name="text-to-speech media resource">237</part-num-ref>
+ converts text into speech and also can be used to convert meta-data descriptions contained in arriving multimedia streams to speech. The video mixing/overlay/closed captioning resource <part-num-ref name="video mixing/overlay/closed captioning resource">239</part-num-ref>
+ can present the workspace manager platform 107's output as a textual pop-up window or other form of text output on the display of the user's communication device. If the communication session is video-based (e.g., video communications or multimedia conferencing) or the communication device is video-capable, the resource <part-num-ref name="resource">239</part-num-ref>
+ can insert the workspace manager platform 107's output directly into a video stream that is presented on a specified co<confidence value="8">m</confidence>
+munication device as a video overlay or as closed captioning.    </p>
+    <boundary-data type="header">
+      <confidence value="88">10</confidence>
+    </boundary-data>
+    <boundary-data type="header">Attorney Docket No.: 20080238                                        Patent</boundary-data>
+    <boundary-data type="header">Ditthavong Mo<confidence value="66">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483    </boundary-data>
+    <p id="p-43" num="43">
+      <page-break num="11"/>
+      <confidence value="5">1</confidence>
+0037<confidence value="5">1</confidence>
+   FIG. 3 is a flowchart of a process for creating a workspace and then logging heterogeneous communication sessions within the workspace, according to an exemplary embodiment. In step <part-num-ref name="exemplary embodiment. In step">301,</part-num-ref>
+ the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ creates a workspace for storing information about a user's communication sessions. A workspace can be, for example, an electronic folder stored in the workspace history database <part-num-ref name="workspace history database">221.</part-num-ref>
+ In one embodiment, the workspace creation module <part-num-ref name="workspace creation module">201</part-num-ref>
+ of the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ may create a default workspace (e.g., a folder named using the current date to store communication sessions conducted by the user on that date) or may create a workspace based on user input. If the workspace is based on user input, the user may specify a name for the workspace at the time of creation. In either case, the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ also enables the user to manipulate the workspace (e.g., rename, delete, copy, etc.) at any later point in time.    </p>
+    <p id="p-44" num="44">
+      <confidence value="5">[</confidence>
+0038<confidence value="5">]</confidence>
+   Once a workspace is created for a particular user, the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ begins logging the user's heterogeneous communication sessions per step <part-num-ref name="user's heterogeneous communication sessions per step">303.</part-num-ref>
+ The logging step <part-num-ref name="logging step">303</part-num-ref>
+ begins with the detection of a communication session involving the user. Such detection is independent of the communication device (e.g., multimedia device <part-num-ref name="multimedia device">109,</part-num-ref>
+ end terminal <part-num-ref name="multimedia device 109, end terminal">11,</part-num-ref>
+ or end terminal <part-num-ref name="multimedia device 109, end terminal 11, or end terminal">115)</part-num-ref>
+ and may be facilitated by, for instance, the IMS session/media control platfor<confidence value="8">m</confidence>
+ <part-num-ref name="IMS session/media control platform">225.</part-num-ref>
+ The detection also may be configured to occur either automatically by the IMS platform <part-num-ref name="IMS platform">225</part-num-ref>
+ or manually at the subscriber's command (e.g., after the subscriber enters a key sequence). In certain embodiments, the configuration for the platform's mode of detection may be specified by the subscriber and stored in the user preferences database <part-num-ref name="user preferences database">221.</part-num-ref>
+    </p>
+    <p id="p-45" num="45">10039<confidence value="5">1</confidence>
+   On detection of a communication session, the log module <part-num-ref name="log module">203</part-num-ref>
+ of the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ creates a log entry for the communication session for inclusion in the use<confidence value="8">'</confidence>
+s communication activity log. The log entry may, for example, include information to identify the communication session such as time of the communication session, communication device, etc. In addition, the log module <part-num-ref name="log module">203</part-num-ref>
+ may include supplemental information in the log entry, as discussed below with respect to FIG. 7. The log module <part-num-ref name="log module">203</part-num-ref>
+ stores the log entry for the communication session within the specified workspace in workspace history database <part-num-ref name="specified workspace in workspace history database">221</part-num-ref>
+ (step <part-num-ref name="(step">305)</part-num-ref>
+ and makes the log of communication sessions available for access by the user (step 307).    </p>
+    <boundary-data type="header">
+      <confidence value="88">11</confidence>
+    </boundary-data>
+    <boundary-data type="header">Attorney Docket No.: 20080238                                        Patent</boundary-data>
+    <boundary-data type="header">Ditthavong Mo<confidence value="66">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483    </boundary-data>
+    <p id="p-46" num="46">
+      <page-break num="12"/>
+The workspace manager platform 107 will then continue to log additional communication sessions involving the user.    </p>
+    <p id="p-47" num="47">10040<confidence value="5">1</confidence>
+   FIG. 4 is a flowchart of a process for recording a communication session to a workspace, according to an exemplary embodiment. The workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ enables the user to specify whether to record and store a copy of a communication session along with the log entry for the session. The user may specify (for example, during the workspace manager service initiation and provisioning process) that the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ should automatically include a recording of one or more types of communication sessions with the corresponding log entries. In addition or alternatively, the user may manually initiate a recording of a specific communication session at the start of the communication session by entering a command, key sequence, or other similar instruction on the user's communication device (e.g., multimedia device <part-num-ref name="multimedia device">109,</part-num-ref>
+ end terminal <part-num-ref name="multimedia device 109, end terminal">111,</part-num-ref>
+ or end te<confidence value="88">rm</confidence>
+inal 115).    </p>
+    <p id="p-48" num="48">
+      <confidence value="5">1</confidence>
+0041<confidence value="5">1</confidence>
+   On receiving a command to record a communication session (either automatically or manually), the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ will detect the communication session using the IMS platform <part-num-ref name="IMS platform">225</part-num-ref>
+ as described above (step 401). The recording module <part-num-ref name="recording module">205</part-num-ref>
+ then initiates recording of the communication session (step 403). The mechanism for recording depends on the type of com<confidence value="8">m</confidence>
+unication session being conducted. For example, if the communication session involves audio- and/or video-based media, a recording may reproduce the audio/video media as presented during the communication session (i.e., a recording in the traditional sense of the word). If the communication session is text-based (e.g., an instant messaging chat session, text messaging conversation, E-mail), the recording may include a transcript of the session in addition to any attachments exchanged during the session. In one embodiment, the recording module <part-num-ref name="recording module">205</part-num-ref>
+ may use the media resource function <part-num-ref name="media resource function">229</part-num-ref>
+ of the IMS platform <part-num-ref name="IMS platform">225</part-num-ref>
+ to assist in creating the recording. Per step <part-num-ref name="recording. Per step">405,</part-num-ref>
+ the recording module <part-num-ref name="recording module">205</part-num-ref>
+ stores the completed recording within the corresponding workspace in workspace history database <part-num-ref name="corresponding workspace in workspace history database">221.</part-num-ref>
+    </p>
+    <p id="p-49" num="49">
+      <confidence value="5">1</confidence>
+0042<confidence value="2">1</confidence>
+   FIG. 5 is a flowchart of a process for re-homing a workspace to an environment specified by the user, according to an exemplary embodiment. In exempla<confidence value="8">r</confidence>
+y embodiments, the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ may re-home (i.e., move) a workspace and its contents to a user-designated environment (e.g., a communication device such as a home telephone, an office <boundary-data type="header">
+        <confidence value="88">12</confidence>
+      </boundary-data>
+      <page-break num="13"/>
+      <boundary-data type="header">
+        <confidence value="8">A</confidence>
+ttorney Docket No.: 20080238                                        Patent      </boundary-data>
+      <boundary-data type="header">Ditthavong Mo<confidence value="66">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483      </boundary-data>
+computer, or a mobile telephone) even if the user did not use the environment or device to conduct the original communication session. In step <part-num-ref name="original communication session. In step">501,</part-num-ref>
+ the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ receives an input from the user specifying an environment for accessing a workspace. The user can make this input via, for instance, multimedia device <part-num-ref name="user can make this input via, for instance, multimedia device">109,</part-num-ref>
+ end terminal <part-num-ref name="user can make this input via, for instance, multimedia device 109, end terminal">111,</part-num-ref>
+ or end terminal <part-num-ref name="user can make this input via, for instance, multimedia device 109, end terminal 111, or end terminal">115.</part-num-ref>
+ In response, the re-homing module <part-num-ref name="re-homing module">207</part-num-ref>
+ in conjunction with the media resource f<confidence value="8">u</confidence>
+nction <part-num-ref name="media resource function">229</part-num-ref>
+ of the IMS platform <part-num-ref name="IMS platform">225</part-num-ref>
+ selectively converts the workspace and its contents to a format suitable for the specified environment (step 503). To facilitate the conversion process, the media resource function <part-num-ref name="media resource function">229</part-num-ref>
+ includes a voice recognition media resource <part-num-ref name="voice recognition media resource">235,</part-num-ref>
+ a text-to-speech media resource <part-num-ref name="text-to-speech media resource">237,</part-num-ref>
+ and a video mixing/overlay/closed captioning media resource <part-num-ref name="video mixing/overlay/closed captioning media resource">239.</part-num-ref>
+ For example, the re-homing module may use the voice recognition media resource <part-num-ref name="voice recognition media resource">235</part-num-ref>
+ to convert the verbal component of a voice communication session stored within a workspace to text for presentation in an environment or communication device capable of displaying text. Similarly, the re-ho<confidence value="5">m</confidence>
+ing module <part-num-ref name="re-homing module">207</part-num-ref>
+ in conjunction with the media resource function <part-num-ref name="media resource function">229</part-num-ref>
+ can output a workspace in a visual format (e.g., textual pop-up, video overlay, closed captioning) if the environment or communication device does not allow for audio. It is contemplated that the media resource function <part-num-ref name="media resource function">229</part-num-ref>
+ may include additional modules to facilitate conversion of a communication session.    </p>
+    <p id="p-50" num="50">
+      <confidence value="4">1</confidence>
+0043<confidence value="5">1</confidence>
+   FIG. 6 is a flowchart of a process for allowing access to a workspace by another user, according to an exemplary embodiment. In exempla<confidence value="8">r</confidence>
+y embodiments, the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ enables a user to allow another user to gain access to a previously created workspace and its contents. To enable this functionality, the user access module <part-num-ref name="user access module">209</part-num-ref>
+ of the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ receives an input from specifying another user (step 601). The user access module <part-num-ref name="user access module">209</part-num-ref>
+ then grants the specified user access to the workspace (step <part-num-ref name="workspace (step">603)</part-num-ref>
+ by, for instance, storing the specified user's identity and associated authentication information in the workspace history database <part-num-ref name="workspace history database">221.</part-num-ref>
+ When the specified user seeks to access the workspace, the user access module <part-num-ref name="user access module">209</part-num-ref>
+ can challenge the user for the previously designated authentication information. It is contemplated that any type of authentication process (e.g., password protection, biometric security) can be employed to ensure that access is provided only to the specified user. It is also contemplated that the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ may grant <boundary-data type="header">
+        <confidence value="88">13</confidence>
+      </boundary-data>
+      <page-break num="14"/>
+      <boundary-data type="header">Attorney Docket No.: 20080238                                         Patent</boundary-data>
+      <boundary-data type="header">Ditthavong Mo<confidence value="66">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483      </boundary-data>
+differing levels of access (e.g., read only, f<confidence value="8">u</confidence>
+ll access, access to only certain types of communication sessions, etc.) to the specified user.    </p>
+    <p id="p-51" num="51">
+      <confidence value="5">[</confidence>
+0044<confidence value="4">]</confidence>
+   FIG. 7 is a flowchart of a process for obtaining supplemental information about a workspace or communication session, according to an exemplary embodiment. Following the co<confidence value="8">m</confidence>
+pletion of a monitored communication session, the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ may be configured to obtain supplemental information (e.g., communication session participants, participant contact information, participant locations, time and duration of the communication session, communication session type, and associated media) about the communication session or the associated workspace. In exemplary embodiments, the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ may obtain the supplemental information automatically by using network resources (e.g., IMS components <part-num-ref name="IMS components">227)</part-num-ref>
+ or manually from the user (step 701). To obtain the information automatically, the supplemental information module <part-num-ref name="supplemental information module">211</part-num-ref>
+ of the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ may interact with the IMS components <part-num-ref name="IMS components">227</part-num-ref>
+ such as the presence server <part-num-ref name="presence server">231</part-num-ref>
+ and/or the location server <part-num-ref name="location server">233.</part-num-ref>
+    </p>
+    <p id="p-52" num="52">Under this option, the IMS platform <part-num-ref name="IMS platform">225</part-num-ref>
+ may signal the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ that a communication session has ended.    </p>
+    <p id="p-53" num="53">
+      <confidence value="2">1</confidence>
+0045<confidence value="5">]</confidence>
+   The supplemental information module <part-num-ref name="supplemental information module">211</part-num-ref>
+ then automatically queries the IMS components <part-num-ref name="IMS components">227</part-num-ref>
+ for any available supplemental information. In response, the presence server <part-num-ref name="presence server">231</part-num-ref>
+ may provide, for instance, information on the parties of the communication session and their communication device capabilities. The location server <part-num-ref name="location server">233</part-num-ref>
+ may also provide information on the location of the parties. In addition (or alternatively), the supplemental information module <part-num-ref name="supplemental information module">211</part-num-ref>
+ may obtain some or all of the supplemental information by presenting the user with the option to manually enter the supplemental information. The supplemental information module <part-num-ref name="supplemental information module">211</part-num-ref>
+ then stores the information within the appropriate workspace in the workspace history database <part-num-ref name="workspace history database">223</part-num-ref>
+ (step 703).    </p>
+    <p id="p-54" num="54">
+      <confidence value="5">1</confidence>
+0046<confidence value="5">1</confidence>
+   FIG. 8 is a flowchart of a process for receiving a command from a user to organize, annotate, or search a workspace, according to an exempla<confidence value="8">r</confidence>
+y embodiment. In step <part-num-ref name="exemplary embodiment. In step">801,</part-num-ref>
+ the workspace manager receives an input from a user specifying a workspace command. The user may enter the command via, for example, multimedia device <part-num-ref name="command via, for example, multimedia device">109,</part-num-ref>
+ end terminal <part-num-ref name="command via, for example, multimedia device 109, end terminal">111,</part-num-ref>
+ or end terminal <part-num-ref name="command via, for example, multimedia device 109, end terminal 111, or end terminal">115.</part-num-ref>
+ The input may include a command to organize a workspace, annotate a <boundary-data type="header">
+        <confidence value="88">14</confidence>
+      </boundary-data>
+      <page-break num="15"/>
+      <boundary-data type="header">Attorney Docket No.: 20080238                                         Patent</boundary-data>
+      <boundary-data type="header">Ditthavong Mo<confidence value="66">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483      </boundary-data>
+workspace, or search a workspace. It is contemplated that the workspace manager platform <part-num-ref name="workspace manager platform">1<confidence value="88">07</confidence>
+      </part-num-ref>
+ may be extended to include additional commands for user interaction with a workspace.    </p>
+    <p id="p-55" num="55">Following receipt of the input, the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ performs the requested command per, step <part-num-ref name="requested command per, step">803.</part-num-ref>
+ More specifically, the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ may employ one of three modules (i.e., an organization module <part-num-ref name="organization module">213,</part-num-ref>
+ an annotation module <part-num-ref name="annotation module">215,</part-num-ref>
+ and a search module <part-num-ref name="search module">217)</part-num-ref>
+ to perform the functions.    </p>
+    <p id="p-56" num="56">10047<confidence value="5">1</confidence>
+   The organization module <part-num-ref name="organization module">213</part-num-ref>
+ enables a user to copy, paste, rename, delete, move, merge, and sort both the workspace as well as the information stored within the workspace. For example, the user may move a communication session recorded within one workspace to another more appropriate workspace or delete the communication session altogether. It is contemplated that other organization-related commands and functions may be added to the organization module <part-num-ref name="organization module">213.</part-num-ref>
+    </p>
+    <p id="p-57" num="57">
+      <confidence value="5">1</confidence>
+0048<confidence value="5">1</confidence>
+   The annotation module <part-num-ref name="annotation module">215</part-num-ref>
+ enables the user to add notes, comments, and/or other attachments to a workspace or a specific communication session logged or stored within the workspace. The annotations then become a part of the workspace and are accessible by the user.    </p>
+    <p id="p-58" num="58">
+      <confidence value="5">1</confidence>
+0049<confidence value="5">1</confidence>
+   The search module <part-num-ref name="search module">217</part-num-ref>
+ enables a user to search the information stored within one or more of the user's workspaces including the communication session logs, recorded communication sessions, supplemental information, and annotations.  To provide this functionality, the search module <part-num-ref name="search module">217</part-num-ref>
+ may use the media resource function <part-num-ref name="media resource function">229</part-num-ref>
+ to convert any non-textual information stored within the workspace or workspaces into textual information. As discussed with respect to the re-homing module <part-num-ref name="re-homing module">207</part-num-ref>
+ above, the voice recognition media resource <part-num-ref name="voice recognition media resource">235</part-num-ref>
+ may convert communication sessions or information that is stored as spoken language into textual information. The search module <part-num-ref name="search module">217</part-num-ref>
+ may then scan the converted textual information for a text string specified by the user and present the search results to the user. In exemplary embodiments, it is contemplated that the user may limit searches according to various criteria (e.g., by workspace, by time, by communication type, by participant, etc.).    </p>
+    <p id="p-59" num="59">
+      <confidence value="5">[</confidence>
+0050<confidence value="5">1</confidence>
+   FIG. 9 is a flowchart of a process for delivering a workspace to an application, according to an exempla<confidence value="8">r</confidence>
+y embodiment. In exemplary embodiments, the workspace manager <boundary-data type="header">
+        <confidence value="88">15</confidence>
+      </boundary-data>
+      <page-break num="16"/>
+      <boundary-data type="header">Attorney Docket No.: 20080238                                          Pate<confidence value="68">nt</confidence>
+      </boundary-data>
+      <boundary-data type="header">Ditthavong Mo<confidence value="66">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483      </boundary-data>
+platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ may be configured to deliver a workspace and its contents to another application.    </p>
+    <p id="p-60" num="60">In this way, the user may leverage the information contained within a workspace for use in other applications (e.g., calendar applications, personal web portals, contact management applications, etc.). In step <part-num-ref name="calendar applications, personal web portals, contact management applications, etc.). In step">901,</part-num-ref>
+ the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ receives an input specifying an application to which a workspace should be delivered. The input may be made directly by a user or by an application on behalf of the user. In response to the input, the content delivery module <part-num-ref name="content delivery module">219</part-num-ref>
+ of the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ may verify the authentication credentials of the requesting user or application. As discussed with respect to the user access module <part-num-ref name="user access module">209,</part-num-ref>
+ it is contemplated that any suitable authentication process may be used to verify that a user or application is authorized to request the delivery of a workspace.    </p>
+    <p id="p-61" num="61">
+      <confidence value="5">[</confidence>
+0051<confidence value="5">1</confidence>
+    Following authentication, the content delivery module <part-num-ref name="content delivery module">219</part-num-ref>
+ delivers the requested workspace to the application by, for instance, a content syndication protocol such as Really Simple Syndication (RSS) (step 903). To assist in the delive<confidence value="8">r</confidence>
+y, the content delivery module <part-num-ref name="content delivery module">219</part-num-ref>
+ may use the media resource function <part-num-ref name="media resource function">229</part-num-ref>
+ to convert any non-textual information stored in the workspace into textual information for delivery using the content syndication protocol. For example, a content delive<confidence value="8">r</confidence>
+y module <part-num-ref name="content delivery module">219</part-num-ref>
+ may deliver a workspace as an RSS feed and/or use an RSS widget to integrate the workspace content into a personal web page. Other applications such as personal information manager or contact management application may also use information provided by the workspace RSS feed.    </p>
+    <p id="p-62" num="62">
+      <confidence value="5">1</confidence>
+0052<confidence value="5">1</confidence>
+    FIG. 10 is a flowchart of a process for using the workspace manager to record a communication session to a workspace from a user<confidence value="8">'</confidence>
+s perspective, according to an exemplary embodiment. This process assumes that the user has already setup the workspace manager service. In step <part-num-ref name="workspace manager service. In step">1001,</part-num-ref>
+ a communication session involving the user is initiated by using, for example, multimedia device <part-num-ref name="user is initiated by using, for example, multimedia device">109,</part-num-ref>
+ end terminal <part-num-ref name="user is initiated by using, for example, multimedia device 109, end terminal">111,</part-num-ref>
+ or end terminal <part-num-ref name="user is initiated by using, for example, multimedia device 109, end terminal 111, or end terminal">115.</part-num-ref>
+ The session may either be initiated by the user or be initiated by another party and directed to the user. During the communication session, the user may manually instruct the workspace manager platfor<confidence value="8">m</confidence>
+ <part-num-ref name="workspace manager platform">107</part-num-ref>
+ to record the communication session in a workspace by, for instance, entering a command or key sequence into the user's communication device (step 1003).    </p>
+    <boundary-data type="header">
+      <confidence value="88">16</confidence>
+    </boundary-data>
+    <boundary-data type="header">Attorney Docket No.: 20080238                                           Patent</boundary-data>
+    <boundary-data type="header">Ditthavong Mori &amp; Steiner, P.C. Docket No.: 09710-1483</boundary-data>
+    <p id="p-63" num="63">
+      <page-break num="17"/>
+10053<confidence value="5">1</confidence>
+   In exemplary embodiments, the user also has the option to instruct the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ to automatically record the communication session. When the user has completed the communication session, the user may enter supplemental information or annotate the communication session for later reference (step 1005). It is contemplated that the user may enter the supplemental information or annotations immediately after the communication session or at any later time.    </p>
+    <p id="p-64" num="64">
+      <confidence value="5">1</confidence>
+0054<confidence value="5">1</confidence>
+    FIG. <confidence value="55">11</confidence>
+ is a flowchart of a process for using a portal to access the functions of the workspace manager from a user's perspective, according to an exemplary embodiment. This process is also described with respect to FIG<confidence value="5">s</confidence>
+. 12A-12C which depict exemplary graphical user interfaces for using a portal to access the functions of the workspace manager, according to various embodiments of the present invention. As previously mentioned, the workspace manager platform <part-num-ref name="workspace manager platform">107</part-num-ref>
+ has connectivity to a host <part-num-ref name="host">117</part-num-ref>
+ that enables access to workspace manager platform <part-num-ref name="that enables access to workspace manager platform">107</part-num-ref>
+ functions and preferences via a graphical user interface or a web-based application.    </p>
+    <p id="p-65" num="65">A user may access the graphical user interface portal using multimedia device <part-num-ref name="graphical user interface portal using multimedia device">109,</part-num-ref>
+ end terminal <part-num-ref name="graphical user interface portal using multimedia device 109, end terminal">
+        <confidence value="555">111</confidence>
+,      </part-num-ref>
+ or end terminal <part-num-ref name="graphical user interface portal using multimedia device 109, end terminal 111, or end terminal">115</part-num-ref>
+ (step <part-num-ref name="(step">1101</part-num-ref>
+ of FIG. 11). In exemplary embodiments, the user provides authentication credentials (e.g., password, biometric security) to access the services of the workspace manager platform <part-num-ref name="workspace manager platform">107.</part-num-ref>
+ User interface <part-num-ref name="workspace manager platform 107. User interface">1200</part-num-ref>
+ of FIG. 12A depicts an exemplary user interface screen that requests a user ID <part-num-ref name="user ID">1201</part-num-ref>
+ and password <part-num-ref name="and password">1203</part-num-ref>
+ from the user. The user enters the requested user ID and password and clicks on the "Sign In" button <part-num-ref name="&quot;Sign In&quot; button">1205</part-num-ref>
+ to proceed.    </p>
+    <p id="p-66" num="66">
+      <confidence value="5">1</confidence>
+0055<confidence value="5">1</confidence>
+    After entering valid authentication credentials, the user may access the portal to update user preferences (step <part-num-ref name="portal to update user preferences (step">1103</part-num-ref>
+ of FIG. 11) and/or perform workspace commands (step <part-num-ref name="and/or perform workspace commands (step">1105</part-num-ref>
+ of FIG. 11). User interface <part-num-ref name="of FIG. 11). User interface">1220</part-num-ref>
+ of FIG. 12B depicts an exemplary user interface screen that lists available workspaces <part-num-ref name="exemplary user interface screen that lists available workspaces">1221,</part-num-ref>
+ available commands <part-num-ref name="exemplary user interface screen that lists available workspaces 1221, available commands">1223,</part-num-ref>
+ and a button <part-num-ref name="button">1225</part-num-ref>
+ to access user preferences. The user may update user preferences by selecting the user preferences button <part-num-ref name="user preferences button">1225.</part-num-ref>
+ The user will then be able to update settings and configurations for the workspace manager platfor<confidence value="8">m</confidence>
+ <part-num-ref name="workspace manager platform">107</part-num-ref>
+ such as whether to automatically record specific communication sessions, types of communication sessions to monitor, available communication devices, etc. The user also may select any of the workspace commands <part-num-ref name="workspace commands">1223</part-num-ref>
+ to organize, annotate, or search a workspace.    </p>
+    <boundary-data type="header">
+      <confidence value="88">17</confidence>
+    </boundary-data>
+    <boundary-data type="header">Attorney Docket No.: 20080238                                          Patent</boundary-data>
+    <boundary-data type="header">Ditthavong Mo<confidence value="66">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483    </boundary-data>
+    <p id="p-67" num="67">
+      <page-break num="18"/>
+10056<confidence value="5">1</confidence>
+   By selecting one of the available workspaces <part-num-ref name="available workspaces">1221,</part-num-ref>
+ the user may access the communication sessions and information stored within the workspace. User interface <part-num-ref name="workspace. User interface">1240</part-num-ref>
+ of FIG. 12C depicts an exempla<confidence value="8">r</confidence>
+y screen for displaying the contents of a workspace. The screen lists the name of the workspace <part-num-ref name="workspace">1241</part-num-ref>
+ and provides a log <part-num-ref name="log">1243</part-num-ref>
+ of the communication sessions stored within the workspace. The user may access any available supplemental information or recording of the communication session by selecting the desired entry on the log. The user also may perform a workspace command by selecting one of the command buttons <part-num-ref name="command buttons">1245.</part-num-ref>
+    </p>
+    <p id="p-68" num="68">[0057<confidence value="5">1</confidence>
+   The processes described herein for providing a workspace to log and/or store multiple heterogeneous communication sessions may be implemented via software, hardware (e.g., general processor, Digital Signal Processing (DSP) chip, an Application Specific Integrated Circuit (ASIC), Field Programmable Gate Arrays (FPGAs), etc.), firmware or a combination thereof. Such exemplary hardware for performing the described f<confidence value="77">un</confidence>
+ctions is detailed below.    </p>
+    <p id="p-69" num="69">
+      <confidence value="5">[</confidence>
+0058<confidence value="5">1</confidence>
+   FIG. 13 illustrates computing hardware (e.g., computer system) upon which an embodiment according to the invention can be implemented. The computer system <part-num-ref name="computer system">1300</part-num-ref>
+ includes a bus <part-num-ref name="bus">1301</part-num-ref>
+ or other communication mechanism for communicating information and a processor <part-num-ref name="processor">1303</part-num-ref>
+ coupled to the bus <part-num-ref name="bus">1301</part-num-ref>
+ for processing information. The computer system <part-num-ref name="computer system">1300</part-num-ref>
+ also includes main memory <part-num-ref name="also includes main memory">1305,</part-num-ref>
+ such as random access memo<confidence value="8">r</confidence>
+y (RAM) or other dynamic storage device, coupled to the bus <part-num-ref name="bus">1301</part-num-ref>
+ for storing information and instructions to be executed by the processor <part-num-ref name="processor">1303.</part-num-ref>
+ Main memory <part-num-ref name="processor 1303. Main memory">1305</part-num-ref>
+ also can be used for storing tempora<confidence value="8">r</confidence>
+y variables or other intermediate information during execution of instructions by the processor <part-num-ref name="processor">1303.</part-num-ref>
+ The computer system <part-num-ref name="computer system">1300</part-num-ref>
+ may further include a read only memory (ROM) <part-num-ref name="read only memory (ROM)">1307</part-num-ref>
+ or other static storage device coupled to the bus <part-num-ref name="bus">1301</part-num-ref>
+ for storing static information and instructions for the processor <part-num-ref name="processor">1303.</part-num-ref>
+ A storage device <part-num-ref name="storage device">1309,</part-num-ref>
+ such as a magnetic disk or optical disk, is coupled to the bus <part-num-ref name="bus">1301</part-num-ref>
+ for persistently storing information and instructions.    </p>
+    <p id="p-70" num="70">
+      <confidence value="5">[</confidence>
+0059<confidence value="5">1</confidence>
+    The computer system <part-num-ref name="computer system">1300</part-num-ref>
+ may be coupled via the bus <part-num-ref name="bus">1301</part-num-ref>
+ to a display <part-num-ref name="display">1311,</part-num-ref>
+ such as a cathode ray tube (CRT), liquid crystal display, active matrix display, or plasma display, for displaying information to a computer user. An input device <part-num-ref name="input device">1313,</part-num-ref>
+ such as a keyboard including alphanumeric and other keys, is coupled to the bus <part-num-ref name="bus">1301</part-num-ref>
+ for communicating information and command selections to the processor <part-num-ref name="processor">1303.</part-num-ref>
+ Another type of user input device is a cursor control <boundary-data type="header">
+        <confidence value="88">18</confidence>
+      </boundary-data>
+      <page-break num="19"/>
+      <boundary-data type="header">Attorney Docket No.<confidence value="5">:</confidence>
+ 20080238                                         Patent      </boundary-data>
+      <boundary-data type="header">Ditthavong Mo<confidence value="66">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483      </boundary-data>
+      <part-num-ref name="cursor control">1315,</part-num-ref>
+ such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor <part-num-ref name="processor">1303</part-num-ref>
+ and for controlling cursor movement on the display <part-num-ref name="display">1311.</part-num-ref>
+    </p>
+    <p id="p-71" num="71">
+      <confidence value="5">1</confidence>
+0060<confidence value="5">1</confidence>
+   According to an embodiment of the invention, the processes described herein are performed by the computer system <part-num-ref name="computer system">1300,</part-num-ref>
+ in response to the processor <part-num-ref name="processor">1303</part-num-ref>
+ executing an arrangement of instructions contained in main memo<confidence value="8">r</confidence>
+y <part-num-ref name="arrangement of instructions contained in main memory">1305.</part-num-ref>
+ Such instructions can be read into main memo<confidence value="8">r</confidence>
+y <part-num-ref name="arrangement of instructions contained in main memory 1305. Such instructions can be read into main memory">1305</part-num-ref>
+ from another computer-<confidence value="5">r</confidence>
+eadable medium, such as the storage device <part-num-ref name="storage device">1309.</part-num-ref>
+    </p>
+    <p id="p-72" num="72">Execution of the arrangement of instructions contained in main memory <part-num-ref name="arrangement of instructions contained in main memory">1305</part-num-ref>
+ causes the processor <part-num-ref name="processor">1303</part-num-ref>
+ to perform the process steps described herein. One or more processors in a multi-processing arrangement may also be employed to execute the instructions contained in main memo<confidence value="8">r</confidence>
+y <part-num-ref name="instructions contained in main memory">1305.</part-num-ref>
+ In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the embodiment of the invention. Thus, embodiments of the invention are not limited to any specific combination of hardware circuitry and software.    </p>
+    <p id="p-73" num="73">
+      <confidence value="5">1</confidence>
+0061<confidence value="5">1</confidence>
+   The computer syste<confidence value="8">m</confidence>
+ <part-num-ref name="computer system">1300</part-num-ref>
+ also includes a communication interface <part-num-ref name="communication interface">1317</part-num-ref>
+ coupled to bus <part-num-ref name="coupled to bus">1301.</part-num-ref>
+ The communication interface <part-num-ref name="communication interface">1317</part-num-ref>
+ provides a two-way data communication coupling to a network link <part-num-ref name="network link">1319</part-num-ref>
+ connected to a local network <part-num-ref name="local network">1321.</part-num-ref>
+ For example, the communication interface <part-num-ref name="communication interface">1317</part-num-ref>
+ may be a digital subscriber line (DSL) card or modem, an integrated services digital network (ISDN) card, a cable modem, a telephone modem, or any other communication interface to provide a data communication connection to a corresponding type of communication line. As another example, communication interface <part-num-ref name="corresponding type of communication line. As another example, communication interface">1317</part-num-ref>
+ may be a local area network (LAN) card (e.g. for EthernetTM or an Asynchronous Transfer Model (ATM) network) to provide a data communication connection to a compatible LAN. Wireless links can also be implemented. In any such implementation, communication interface <part-num-ref name="compatible LAN. Wireless links can also be implemented. In any such implementation, communication interface">1317</part-num-ref>
+ sends and receives electrical, electromagnetic, or optical signals that ca<confidence value="88">ry</confidence>
+ digital data streams representing various types of information. Further, the communication interface <part-num-ref name="communication interface">1317</part-num-ref>
+ can include peripheral interface devices, such as a Universal Serial Bus (USB) interface, a PCMCIA (Personal Computer Memory Card International Association) interface, etc. Although a single communication interface <part-num-ref name="single communication interface">1317</part-num-ref>
+ is depicted in FIG. 13, multiple communication interfaces can also be employed.    </p>
+    <boundary-data type="header">
+      <confidence value="88">19</confidence>
+    </boundary-data>
+    <boundary-data type="header">Attorney Docket No.: 20080238                                         Patent</boundary-data>
+    <boundary-data type="header">Ditthavong Mo<confidence value="66">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483    </boundary-data>
+    <p id="p-74" num="74">
+      <page-break num="20"/>
+      <confidence value="5">1</confidence>
+0062<confidence value="5">1</confidence>
+   The network link <part-num-ref name="network link">1319</part-num-ref>
+ typically provides data communication through one or more networ<confidence value="8">k</confidence>
+s to other data devices. For example, the network link <part-num-ref name="network link">1319</part-num-ref>
+ may provide a connection through local network <part-num-ref name="connection through local network">1321</part-num-ref>
+ to a host computer <part-num-ref name="host computer">1323,</part-num-ref>
+ which has connectivity to a network <part-num-ref name="network">1325</part-num-ref>
+ (e.g. a wide area network (WAN) or the global packet data communication network now commonly referred to as the "Internet") or to data equipment operated by a service provider.    </p>
+    <p id="p-75" num="75">The local network 1321 and the network <part-num-ref name="network">1325</part-num-ref>
+ both use electrical, electromagnetic, or optical signals to convey information and instructions. The signals through the various networks and the signals on the network link <part-num-ref name="network link">1319</part-num-ref>
+ and through the communication interface <part-num-ref name="communication interface">1317,</part-num-ref>
+ which com<confidence value="8">m</confidence>
+unicate digital data with the computer system <part-num-ref name="computer system">1300,</part-num-ref>
+ are exemplary forms of carrier waves bearing the information and instructions.    </p>
+    <p id="p-76" num="76">
+      <confidence value="4">1</confidence>
+00631   The computer system <part-num-ref name="computer system">1300</part-num-ref>
+ can send messages and receive data, including program code, through the network(s), the network link <part-num-ref name="network link">1319,</part-num-ref>
+ and the communication interface <part-num-ref name="communication interface">1317.</part-num-ref>
+ In the Internet example, a server (not shown) might transmit requested code belonging to an application program for implementing an embodiment of the invention through the network <part-num-ref name="network">1325,</part-num-ref>
+ the local network <part-num-ref name="local network">1321</part-num-ref>
+ and the communication interface <part-num-ref name="communication interface">1317.</part-num-ref>
+ The processor <part-num-ref name="processor">1303</part-num-ref>
+ may execute the transmitted code while being received and/or store the code in the storage device <part-num-ref name="storage device">1309,</part-num-ref>
+ or other non-volatile storage for later execution. In this manner, the computer system <part-num-ref name="computer system">1300</part-num-ref>
+ may obtain application code in the for<confidence value="8">m</confidence>
+ of a carrier wave.    </p>
+    <p id="p-77" num="77">10064<confidence value="5">1</confidence>
+   The term "computer-readable medium" as used herein refers to any medium that participates in providing instructions to the processor <part-num-ref name="processor">1303</part-num-ref>
+ for execution. Such a medium may take many forms, including but not limited to non-volatile media, volatile media, and transmission media. Non-volatile media include, for example, optical or magnetic disks, such as the storage device <part-num-ref name="storage device">1309.</part-num-ref>
+ Volatile media include dynamic memory, such as main memory <part-num-ref name="storage device 1309. Volatile media include dynamic memory, such as main memory">1305.</part-num-ref>
+    </p>
+    <p id="p-78" num="78">Transmission media include coaxial cables, copper wire and fiber optics, including the wires that comprise the bus <part-num-ref name="bus">1301.</part-num-ref>
+ Transmission media can also take the form of acoustic, optical, or electromagnetic waves, such as those generated during radio frequency (RF) and infrared (IR) data communications. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, CDRW, DVD, any other optical medium, punch cards, paper tape, optical mar<confidence value="8">k</confidence>
+ sheets, any other <boundary-data type="header">
+        <confidence value="88">20</confidence>
+      </boundary-data>
+      <page-break num="21"/>
+      <boundary-data type="header">Attorney Docket No.: 20080238                                        Patent</boundary-data>
+      <boundary-data type="header">Ditthavong Mo<confidence value="68">ri</confidence>
+ &amp; Steiner, P.C. Docket No.: 09710-1483      </boundary-data>
+physical medium with patterns of holes or other optically recognizable indicia, a RAM, a PROM, an EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave, or any other medium from which a computer can read.    </p>
+    <p id="p-79" num="79">10065<confidence value="5">1</confidence>
+   Various forms of computer-readable media may be involved in providing instructions to a processor for execution. For example, the instructions for carrying out at least part of the embodiments of the invention may initially be borne on a magnetic disk of a remote computer.    </p>
+    <p id="p-80" num="80">In such a scenario, the remote computer loads the instructions into main memo<confidence value="8">r</confidence>
+y and sends the instructions over a telephone line using a modem. A modem of a local computer system receives the data on the telephone line and uses an infrared transmitter to convert the data to an infrared signal and transmit the infrared signal to a portable computing device, such as a personal digital assistant (PDA) or a laptop. An infrared detector on the portable computing device receives the information and instructions borne by the infrared signal and places the data on a bus. The bus conveys the data to main memory, from which a processor retrieves and executes the instructions. The instructions received by main memory can optionally be stored on storage device either before or after execution by processor.    </p>
+    <p id="p-81" num="81">
+      <confidence value="5">[</confidence>
+0066<confidence value="5">1</confidence>
+   While certain exemplary embodiments and implementations have been described herein, other embodiments and modifications will be apparent from this description.    </p>
+    <p id="p-82" num="82">Accordingly, the invention is not limited to such embodiments, but rather to the broader scope of the presented claims and various obvious modifications and equivalent arrangements.</p>
+    <boundary-data type="header">
+      <confidence value="88">21</confidence>
+    </boundary-data>
+  </description>
+</us-patent-application>
+

applicant/12364170.xml

@@ -0,0 +1,548 @@
+<?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>12364170</doc-number>
+        <date>2009-02-02</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+    <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+    <boundary-data type="header">
+      <confidence value="88">-1</confidence>
+ <confidence value="8">-</confidence>
+    </boundary-data>
+    <heading id="h-1">DATABASE SYSTEM TESTING USING ROBUSTNESS MAPS</heading>
+    <p id="p-1" num="1">Goetz Graefe Harumi Kuno Janet L. Wiener </p>
+    <heading id="h-2">BACKGROUND</heading>
+    <p id="p-2" num="2">[0001<confidence value="5">]</confidence>
+  A query statement can be compiled into a query plan consisting of query operators. A query operator can be executed in many different ways, for example full table scans, index scans, nested loop joins, hash joins, and others. A query optimizer is a component of a database management system that attempts to determine the most efficient way to execute a query. The query optimizer determines the most efficient way to execute a SQL statement after considering many factors related to the objects referenced and the conditions specified in the query. The determination is a useful step in the processing of any query statement and can greatly affect execution time.    </p>
+    <p id="p-3" num="3">[0002<confidence value="5">]</confidence>
+  The query optimizer compares the available query plans for a target input query and estimates which of plan will be the most efficient in practice.    </p>
+    <p id="p-4" num="4">One type of query optimizer operates on a cost basis and assigns an estimated cost to each possible query plan, for example selecting the plan with the smallest cost. Costs can be used to estimate the runtime cost of evaluating the query in terms of factors such as the number of <confidence value="686">I/O</confidence>
+ operations required, processor load requirements, and other factors which can be set forth in a data structure called a data dictionary which stores statistics used by <page-break num="2"/>
+      <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+      <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+      <boundary-data type="header">
+        <confidence value="888">-2-</confidence>
+      </boundary-data>
+the query optimizer. The set of available query plans that are examined is formed by examining the possible access paths, such as index scan and sequential scan, and join algorithms including sort-merge join, hash join, nested loops, and others. A search space can become very large according to complexity of the query.    </p>
+    <p id="p-5" num="5">[0003<confidence value="5">]</confidence>
+  Performance of a database system during processing of a query depends on the ability of a query optimizer to select an appropriate plan for executing the query under an expected set of conditions (for example, cardinality estimates, resource availability assumptions), and the ability of an executor to process the query using the selected plan under actual runtime conditions.    </p>
+    <p id="p-6" num="6">[0004<confidence value="5">]</confidence>
+  Some approaches to managing database system performance focus on the query optimizer's ability to select an appropriate plan. Even techniques that consider the disparity between expected and actual runtime conditions focus on assisting the query optimizer to pick the best plan with regard to such disparity.    </p>
+    <heading id="h-3">SUMMARY</heading>
+    <p id="p-7" num="7">[0005<confidence value="5">]</confidence>
+  Embodiments of computer-implemented systems and associated operating methods take measurements and landmarks associated with robustness maps and perform tests evaluating the robustness of a database engine's operator implementations and/or query components. The illustrative computer-implemented system comprises logic that receives one or more robustness maps of measured database system performance acquired during database execution in a predetermined range of runtime conditions and uses information from the robustness map or maps to perform regression testing wherein landmarks in the robustness maps are operated upon as a robustness bugs describing conditions under which a predetermined implementation of a database operator or query component degrades in a manner different from a predetermined expected manner.    </p>
+    <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+    <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+    <boundary-data type="header">
+      <confidence value="888">-3-</confidence>
+    </boundary-data>
+    <heading id="h-4">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
+    <p id="p-8" num="8">
+      <page-break num="3"/>
+[0006<confidence value="5">]</confidence>
+  Embodiments of the invention relating to both structure and method of operation may best be understood by referring to the following description and accompanying drawings:    </p>
+    <p id="p-9" num="9">FIGURE 1 is a schematic block diagram showing an embodiment of a computer-implemented system that takes measurements and landmarks associated with robustness maps and performs tests evaluating the robustness of a database engine's operator implementations and/or query components;</p>
+    <p id="p-10" num="10">FIGURE 2 is a schematic block diagram which depicts an embodiment of a computer-implemented system in the form of an article of manufacture that uses measurements and landmarks associated with robustness maps to perform tests evaluating the robustness of a database engine's operator implementations and/or query components;</p>
+    <p id="p-11" num="11">FIGURE 3 is a schematic block diagram illustrating an embodiment of a computer-implemented system that evaluates robustness of a given database system implementation in terms of the robustness of operator implementations and query components of the database system;</p>
+    <p id="p-12" num="12">FIGUREs 4A and 4<confidence value="5">B</confidence>
+ are flow charts that show one or more embodiments or aspects of a computer-executed method for evaluating robustness of a given database system implementation in terms of the robustness of its operator implementations;    </p>
+    <p id="p-13" num="13">FIGURE 5 is a table showing an example list of possible robustness bugs in an embodiment of a test system; and FIGUREs 6A through 6M are pictorial diagrams showing maps of performance under specific runtime conditions.</p>
+    <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+    <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+    <boundary-data type="header">
+      <confidence value="888">-4-</confidence>
+    </boundary-data>
+    <heading id="h-5">DETAILED DESCRIPTION</heading>
+    <p id="p-14" num="14">
+      <page-break num="4"/>
+[0007<confidence value="5">]</confidence>
+  A system tests robustness of a database system.    </p>
+    <p id="p-15" num="15">[0008<confidence value="5">]</confidence>
+  In an illustrative embodiment, a system tests robustness of a database system implementation with regard to a variety of conditions that include resource availability and data characteristics. The system enables tests to be carried out more quickly without loss of coverage. The system can implement a method for comparing between two robustness maps, for example identifying when "dangerous landmarks" change in significant ways (move, disappear, appear). The system can also implement a method for comparing two or more robustness maps produced by two different database systems, for example to identify which system's maps have more "dangerous landmarks" and comparative locations. The system evaluates a database system's robustness in terms of the number and locations of the landmark features on robustness maps for the database system.    </p>
+    <p id="p-16" num="16">[0009<confidence value="5">]</confidence>
+  In various embodiments and applications, performance or robustness maps can be created and used to evaluate the robustness of a given database system implementation in terms of the degree of robustness exhibited when executing a known database benchmark.    </p>
+    <p id="p-17" num="17">[0010<confidence value="5">]</confidence>
+  In various embodiments and applications, measurements and landmarks produced in creation of performance or robustness maps enable production of a system for performing regression tests which evaluate the robustness of a database engine's operator implementations.    </p>
+    <p id="p-18" num="18">[0011<confidence value="5">]</confidence>
+  In various embodiments and applications, robustness of a given database system implementation can be evaluated in terms of the robustness of operator implementations of the implementation. Systems and operating methods disclosed herein can use performance or robustness maps to perform testing of a database system.    </p>
+    <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+    <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+    <boundary-data type="header">
+      <confidence value="888">-5-</confidence>
+    </boundary-data>
+    <p id="p-19" num="19">
+      <page-break num="5"/>
+[0012<confidence value="5">]</confidence>
+  The systems and methods disclosed herein are enabled by recognition that expected conditions often bear little resemblance to actual conditions. These systems and methods thus focus on characterizing, evaluating, and capturing the impact of adverse conditions on the Executor's performance in performance maps, which may be called robustness maps.    </p>
+    <p id="p-20" num="20">The maps graphically identify and characterize performance under specific runtime conditions, coordinates of landmarks on the maps, marked regions of interest on the maps, and coordinates of landmarks of interest that fall within the regions of interest.</p>
+    <p id="p-21" num="21">[0013<confidence value="5">]</confidence>
+  By creating maps of performance under a large range of conditions, the disclosed systems and method enable the analysis, prediction, and characterization of performance and performance degradation. The maps can be created using time as a measurement of performance, or others of a multitude of performance characteristics, for example including execution time, elapsed (wall clock) time, number of <confidence value="5">I</confidence>
+/O's generated, and the like. In various graphical visualizations, data input characterizations can be presented in different way, for example including cardinality, selectivity, average temporary data size, and the like.    </p>
+    <p id="p-22" num="22">[0014<confidence value="5">]</confidence>
+  Referring to FIGURE 1, a schematic block diagram illustrates an embodiment of a computer-implemented system <part-num-ref name="computer-implemented system">100</part-num-ref>
+ that takes measurements <part-num-ref name="that takes measurements">112</part-num-ref>
+ and landmarks <part-num-ref name="and landmarks">110</part-num-ref>
+ associated with robustness maps <part-num-ref name="associated with robustness maps">114</part-num-ref>
+ and performs tests evaluating the robustness of a database engine's operator implementations <part-num-ref name="database engine's operator implementations">108</part-num-ref>
+ and/or query components <part-num-ref name="and/or query components">106.</part-num-ref>
+ The illustrative computer-implemented system <part-num-ref name="illustrative computer-implemented system">100</part-num-ref>
+ comprises logic <part-num-ref name="comprises logic">104</part-num-ref>
+ that receives one or more robustness maps <part-num-ref name="that receives one or more robustness maps">114</part-num-ref>
+ of measured database system performance acquired during database execution in a predetermined range of runtime conditions and uses information from the robustness map or maps <part-num-ref name="robustness map or maps">114</part-num-ref>
+ to perform regression testing wherein landmarks <part-num-ref name="to perform regression testing wherein landmarks">110</part-num-ref>
+ in the robustness maps <part-num-ref name="robustness maps">114</part-num-ref>
+ are operated upon as a robustness bugs <part-num-ref name="robustness bugs">110</part-num-ref>
+ describing conditions under which a predetermined implementation of a database operator <part-num-ref name="database operator">108</part-num-ref>
+ or query component <part-num-ref name="or query component">106</part-num-ref>
+ degrades in a manner different from a predetermined <page-break num="6"/>
+      <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+      <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+      <boundary-data type="header">
+        <confidence value="888">-6-</confidence>
+      </boundary-data>
+expected manner. Regression testing is system testing which attempts to discover regressions that occur when functionality that previously operated correctly stops working as intended. Robustness maps <part-num-ref name="predetermined expected manner. Regression testing is system testing which attempts to discover regressions that occur when functionality that previously operated correctly stops working as intended. Robustness maps">114</part-num-ref>
+ are highly suitable for regression testing since the maps enable visualization of a very large number of parameters and variables in a single view. Effective regression tests generate sufficient execution coverage to exercise all meaningful code branches. Therefore, the combinatorial problem inherent in regression testing is effectively addressed with a multiple-dimensional robustness map.    </p>
+    <p id="p-23" num="23">[0015<confidence value="5">]</confidence>
+  The logic <part-num-ref name="logic">104</part-num-ref>
+ can perform analysis which characterizes the severity of individual robustness bugs <part-num-ref name="severity of individual robustness bugs">110</part-num-ref>
+ in terms of amplitude of the degradation, range of condition span for which the robustness bug <part-num-ref name="robustness bug">110</part-num-ref>
+ is present, and frequency with which robustness bug conditions are historically encountered or expected to be encountered.    </p>
+    <p id="p-24" num="24">[0016<confidence value="5">]</confidence>
+  The logic <part-num-ref name="logic">104</part-num-ref>
+ can also characterize severity of individual robustness bugs in terms of degree to which the degradation can be remedied, estimation of the resources expended to correct the robustness bug, and assessment of risk associated with an action that corrects the robustness bug.    </p>
+    <p id="p-25" num="25">[0017<confidence value="5">]</confidence>
+  In some embodiments, the computer-implemented system <part-num-ref name="computer-implemented system">100</part-num-ref>
+ can further comprise a computer <part-num-ref name="computer">120</part-num-ref>
+ that executes the logic <part-num-ref name="logic">104.</part-num-ref>
+    </p>
+    <p id="p-26" num="26">[0018<confidence value="5">]</confidence>
+  Referring to FIGURE 2, a schematic block diagram illustrates an embodiment of a computer-implemented system <part-num-ref name="computer-implemented system">200</part-num-ref>
+ in the form of an article of manufacture <part-num-ref name="article of manufacture">230</part-num-ref>
+ that uses measurements <part-num-ref name="that uses measurements">212</part-num-ref>
+ and landmarks <part-num-ref name="and landmarks">210</part-num-ref>
+ associated with robustness maps <part-num-ref name="associated with robustness maps">214</part-num-ref>
+ to perform tests evaluating the robustness of a database engine's operator implementations and/or query components. The article of manufacture <part-num-ref name="article of manufacture">230</part-num-ref>
+ comprises a controller-usable medium <part-num-ref name="controller-usable medium">232</part-num-ref>
+ having a computer readable program code <part-num-ref name="computer readable program code">234</part-num-ref>
+ embodied in a controller <part-num-ref name="controller">236</part-num-ref>
+ for testing database system performance. The computer readable program code <part-num-ref name="computer readable program code">234</part-num-ref>
+ further comprises code causing the controller <part-num-ref name="controller">236</part-num-ref>
+ <page-break num="7"/>
+      <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+      <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+      <boundary-data type="header">
+        <confidence value="888">-7-</confidence>
+      </boundary-data>
+to receive one or more robustness maps <part-num-ref name="to receive one or more robustness maps">214</part-num-ref>
+ of measured database system performance acquired during database execution in a predetermined range of runtime conditions. The computer readable program code <part-num-ref name="computer readable program code">234</part-num-ref>
+ further comprises code causing the controller <part-num-ref name="controller">236</part-num-ref>
+ to test performance based on locations and migrations of landmarks <part-num-ref name="to test performance based on locations and migrations of landmarks">210</part-num-ref>
+ on the robustness map or maps <part-num-ref name="robustness map or maps">214.</part-num-ref>
+    </p>
+    <p id="p-27" num="27">[0019<confidence value="5">]</confidence>
+  Referring to FIGURE 3, a schematic block diagram illustrates an embodiment of a computer-implemented system <part-num-ref name="computer-implemented system">300</part-num-ref>
+ that evaluates robustness of a given database system implementation in terms of the robustness of operator implementations <part-num-ref name="robustness of operator implementations">308</part-num-ref>
+ and query components <part-num-ref name="and query components">306</part-num-ref>
+ of the database system <part-num-ref name="database system">328.</part-num-ref>
+ The computer-implemented system <part-num-ref name="computer-implemented system">300</part-num-ref>
+ comprises logic <part-num-ref name="comprises logic">304</part-num-ref>
+ that receives one or more robustness maps <part-num-ref name="that receives one or more robustness maps">314</part-num-ref>
+ of measured database system performance acquired during database execution in a predetermined range of runtime conditions and tests performance based on locations and migrations of landmarks <part-num-ref name="predetermined range of runtime conditions and tests performance based on locations and migrations of landmarks">310</part-num-ref>
+ on the one or more robustness maps <part-num-ref name="one or more robustness maps">314.</part-num-ref>
+    </p>
+    <p id="p-28" num="28">[0020<confidence value="5">]</confidence>
+  The logic <part-num-ref name="logic">304</part-num-ref>
+ can evaluate robustness of a specified database system implementation in terms of degree of robustness exhibited when executing a predetermined database benchmark <part-num-ref name="predetermined database benchmark">324.</part-num-ref>
+ The robustness benchmark <part-num-ref name="robustness benchmark">324</part-num-ref>
+ enables robustness of a database system to be quantified.    </p>
+    <p id="p-29" num="29">[0021<confidence value="5">]</confidence>
+  In some implementations or applications, the logic <part-num-ref name="logic">304</part-num-ref>
+ can analyze measurements <part-num-ref name="can analyze measurements">312</part-num-ref>
+ and landmarks <part-num-ref name="and landmarks">310</part-num-ref>
+ in the robustness map or maps <part-num-ref name="robustness map or maps">314,</part-num-ref>
+ and use the analysis to perform regression tests <part-num-ref name="analysis to perform regression tests">326</part-num-ref>
+ that evaluate robustness of a database engine's operator implementations <part-num-ref name="database engine's operator implementations">308.</part-num-ref>
+    </p>
+    <p id="p-30" num="30">[0022<confidence value="5">]</confidence>
+  Similarly, in some applications the logic <part-num-ref name="logic">304</part-num-ref>
+ can evaluate robustness of a specified database system implementation <part-num-ref name="specified database system implementation">328</part-num-ref>
+ in terms of robustness of operator implementations <part-num-ref name="in terms of robustness of operator implementations">308.</part-num-ref>
+    </p>
+    <p id="p-31" num="31">[0023<confidence value="5">]</confidence>
+  The logic <part-num-ref name="logic">304</part-num-ref>
+ can test performance by visualizing the location and character of performance changes on the one or more robustness map <part-num-ref name="one or more robustness map">314</part-num-ref>
+ <page-break num="8"/>
+      <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+      <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+wherein the robustness map or maps <part-num-ref name="robustness map or maps">314</part-num-ref>
+ are analyzed to detect circumstances under which performance is sensitive to deviations from expected behavior. Based on the analysis, the logic <part-num-ref name="logic">304</part-num-ref>
+ identifies performance anomalies.    </p>
+    <p id="p-32" num="32">[0024<confidence value="5">]</confidence>
+  The logic <part-num-ref name="logic">304</part-num-ref>
+ can detect performance degradation by determining curvature between data points on the robustness map or maps <part-num-ref name="robustness map or maps">314,</part-num-ref>
+ for example by identifying locations on the robustness maps <part-num-ref name="robustness maps">314</part-num-ref>
+ wherein performance degrades by a predetermined amount or performance degrades in a manner different from a predetermined expected manner. The logic <part-num-ref name="logic">304</part-num-ref>
+ can apply a corrective action based on the amount of detected performance degradation.    </p>
+    <p id="p-33" num="33">[0025<confidence value="5">]</confidence>
+  The logic can use robustness maps <part-num-ref name="logic can use robustness maps">314</part-num-ref>
+ to compare performance of an applied query plan and/or operator to a best known query plan <part-num-ref name="best known query plan">316</part-num-ref>
+ and/or operator <part-num-ref name="and/or operator">308.</part-num-ref>
+ The logic <part-num-ref name="logic">304</part-num-ref>
+ can apply a corrective action based on the detected performance comparison.    </p>
+    <p id="p-34" num="34">[0026<confidence value="5">]</confidence>
+  The logic <part-num-ref name="logic">304</part-num-ref>
+ can use robustness maps <part-num-ref name="can use robustness maps">314</part-num-ref>
+ to detect an error condition where performance improves as workload increases or operating resources decrease.    </p>
+    <p id="p-35" num="35">[0027<confidence value="5">]</confidence>
+  Referring to FIGUREs 4A and 4<confidence value="5">B</confidence>
+, flow charts illustrate one or more embodiments or aspects of a computer-executed method for evaluating robustness of a given database system implementation in terms of the robustness of its operator implementations. FIGURE 4A depicts a computer- executed method <part-num-ref name="computer- executed method">400</part-num-ref>
+ for testing <part-num-ref name="for testing">402</part-num-ref>
+ a database system that comprises receiving <part-num-ref name="database system that comprises receiving">404</part-num-ref>
+ one or more robustness maps of measured database system performance acquired during database execution in a predetermined range of runtime conditions, and using <part-num-ref name="predetermined range of runtime conditions, and using">406</part-num-ref>
+ information from the robustness maps to perform regression testing wherein landmarks are operated upon as a robustness bug describing conditions under which a predetermined implementation of a database operator or query component degrades in a manner different from a predetermined expected manner.    </p>
+    <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+    <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+    <boundary-data type="header">
+      <confidence value="888">-9-</confidence>
+    </boundary-data>
+    <p id="p-36" num="36">
+      <page-break num="9"/>
+[0028<confidence value="5">]</confidence>
+  Referring to FIGURE 4<confidence value="5">B</confidence>
+, a method <part-num-ref name="method">410</part-num-ref>
+ for evaluating <part-num-ref name="for evaluating">412</part-num-ref>
+ robustness of the database system implementation can comprise characterizing severity <part-num-ref name="database system implementation can comprise characterizing severity">414</part-num-ref>
+ of individual robustness bugs in terms of amplitude of the degradation, range of condition span <part-num-ref name="degradation, range of condition span">416</part-num-ref>
+ for which the robustness bug is present, frequency <part-num-ref name="robustness bug is present, frequency">418</part-num-ref>
+ with which robustness bug conditions are historically encountered or expected to be encountered, degree <part-num-ref name="with which robustness bug conditions are historically encountered or expected to be encountered, degree">420</part-num-ref>
+ to which the degradation can be remedied, estimation <part-num-ref name="degradation can be remedied, estimation">422</part-num-ref>
+ of the resources expended to correct the robustness bug, assessment <part-num-ref name="robustness bug, assessment">424</part-num-ref>
+ of risk associated with an action that corrects the robustness bug, and other conditions or aspects of operation.    </p>
+    <p id="p-37" num="37">[0029<confidence value="5">]</confidence>
+  In contrast to the illustrative systems <part-num-ref name="illustrative systems">100,</part-num-ref>
+ <part-num-ref name="illustrative systems 100,">200,</part-num-ref>
+ and <part-num-ref name="illustrative systems 100, 200, and">300,</part-num-ref>
+ and methods <part-num-ref name="illustrative systems 100, 200, and 300, and methods">400</part-num-ref>
+ and <part-num-ref name="and">410,</part-num-ref>
+ traditional solutions do not consider the impact of variable runtime conditions, such as resource availability, and do not systematically gather actual performance measurements over a variety of runtime conditions. Furthermore, traditional solutions focus on the selection of optimal query plans for a small range expected conditions, as opposed to the evaluation of database operators under a wide variety of actual conditions.    </p>
+    <p id="p-38" num="38">[0030<confidence value="5">]</confidence>
+  For example, Harista et al. (U.S. Publication No. 2002/0046030) discloses a system that maps how well queries perform relative to one another in terms of estimated (expected) performance in ranges of the selectivity of a simple single-operator query with up to two parameters.    </p>
+    <p id="p-39" num="39">Because the goal in Harista et al. is to reduce the number of plans in the query optimizer's plan search space, actual performance is not modeled and the impact of other conditions such as resource availability is not considered.</p>
+    <p id="p-40" num="40">[0031<confidence value="5">]</confidence>
+  Database regression tests may test the performance of individual operators, sometimes under specific resource availability conditions, but do not evaluate performance across a spectrum of conditions and do not consider performance as a continuous function across a spectrum of conditions. Database regression tests are used to evaluate performance - <page-break num="10"/>
+      <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+      <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+      <boundary-data type="header">
+        <confidence value="8888">-10-</confidence>
+      </boundary-data>
+results are not stored nor later used to calculate an estimate for a specific query's performance under specific conditions.    </p>
+    <p id="p-41" num="41">[0032<confidence value="5">]</confidence>
+  The illustrative systems <part-num-ref name="illustrative systems">100,</part-num-ref>
+ <part-num-ref name="illustrative systems 100,">200,</part-num-ref>
+ and <part-num-ref name="illustrative systems 100, 200, and">300</part-num-ref>
+ can perform regression tests that include analysis of robustness maps, focusing on the areas where small changes have disproportionally big impact on performance. The systems enable tests to be carried out more quickly without loss of coverage, and can also identify when the "dangerous landmarks" change in significant ways (move, disappear, appear).    </p>
+    <p id="p-42" num="42">[0033<confidence value="5">]</confidence>
+  Database physical design advisors evaluate physical design search spaces, often with regard to specific query plans or atomic query plans, but the evaluations do not consider a variety of runtime conditions (for example, resource availability). Furthermore, database physical design advisor comparisons are based completely on query optimizer cost estimates, as opposed to actual performance measurements of the systems <part-num-ref name="systems">100,</part-num-ref>
+ <part-num-ref name="systems 100,">200,</part-num-ref>
+ and <part-num-ref name="systems 100, 200, and">300</part-num-ref>
+ depicted in FIGUREs <part-num-ref name="depicted in FIGUREs">1,</part-num-ref>
+ <part-num-ref name="depicted in FIGUREs 1,">2</part-num-ref>
+ <confidence value="5">,</confidence>
+and <part-num-ref name=",and">3.</part-num-ref>
+    </p>
+    <p id="p-43" num="43">[0034<confidence value="5">]</confidence>
+  Given a set of robustness maps, each landmark can be treated as a robustness bug which describes conditions under which a specific implementation of a database operator or atomic query component suddenly degrades (as opposed to a graceful degradation).    </p>
+    <p id="p-44" num="44">[0035<confidence value="5">]</confidence>
+  The severity of each robustness bug is then characterized in terms of the depth of the degradation, the range of conditions that the bug spans, the frequency with which the conditions have been historically encountered (or are expected to be encountered), the degree to which the degradation can be remedied, an estimation of the resources allocated to fix the bug, an assessment of the risk associated with the proposed fix, and the like.    </p>
+    <p id="p-45" num="45">[0036<confidence value="5">]</confidence>
+  Referring to FIGURE 5, a table shows an example list of possible robustness bugs in an embodiment of a test system. The systems and methods disclosed herein use information about robustness bugs such as those listed to evaluate results of database tests.    </p>
+    <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+    <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+    <boundary-data type="header">
+      <confidence value="8888">-11-</confidence>
+    </boundary-data>
+    <p id="p-46" num="46">
+      <page-break num="11"/>
+[0037<confidence value="5">]</confidence>
+  The graphs shown in FIGUREs 6A through 6M, various embodiments or visualizations of robustness maps enable a test system that identifies places where performance either drops off dramatically or unexpectedly, or performance becomes substantially worse than a best known operator or plan, depending on the component under analysis. The information in the robustness can be used to determine possible improvements.    </p>
+    <p id="p-47" num="47">[0038<confidence value="5">]</confidence>
+  The illustrative systems and methods that use robustness maps for testing substantially increase testing capabilities. Conventional tests can test only a few selected conditions. In contrast, the illustrative testing systems and methods enable analysis of how performance degrades under a wide range of conditions, and enables comparison of a particular implementation with best performance.    </p>
+    <p id="p-48" num="48">[0039<confidence value="5">]</confidence>
+  Referring to FIGURE 6A, a pictorial diagram shows a hypothetical map of performance under specific runtime conditions for a specific implementation of a database operator on a given system configuration. The X axis shows the number of rows of input that are processed during execution (cardinality). The Y axis represents the maximum amount of memory available to the executor for the subject query during execution. Regions of the map can be color-coded or grayscale-coded according to average throughput under particular available memory/input tuples processed conditions. Darker colors indicate higher throughput. A similar graph can be created for conditions such as average CPU load average during the execution of the query or other parameters. Multiple graphs can be combined to compare performance under multiple conditions, for example including aspects of one or more of cardinality, memory availability, CPU load average, average disk busy, and the like. A similar visualization can be created for atomic queries. In addition, the map is annotated to reflect how frequently particular conditions occur. The smaller rectangle marks the region of the most frequently occurring conditions. The larger rectangle marks a region of conditions that occur with 10% probability. Any number of other visualization <page-break num="12"/>
+      <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+      <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+      <boundary-data type="header">
+        <confidence value="8888">-12-</confidence>
+      </boundary-data>
+techniques can be applied to capture the information. For example, the map can be annotated to mark a region of anticipated conditions under which the query is expected to execute.    </p>
+    <p id="p-49" num="49">[0040<confidence value="5">]</confidence>
+  "Robustness" is defined herein as a measure of continuity of the curvature of the function describing performance under varying conditions.    </p>
+    <p id="p-50" num="50">FIGURE 6B shows how "interesting features" can be marked on the map <part-num-ref name="map">600.</part-num-ref>
+    </p>
+    <p id="p-51" num="51">In an example application, areas of interest such as edges and holes where the target query plan's performance drops off precipitously when compared to the best alternative. Thus, where performance does not degrade gracefully.</p>
+    <p id="p-52" num="52">For example, the circled area labeled "cliff<confidence value="5">"</confidence>
+ <part-num-ref name="circled area labeled &quot;cliff&quot;">602</part-num-ref>
+ shows where performance suddenly degrades when a particular ratio of input size of the input to the amount of memory available is exceeded. The map <part-num-ref name="map">600</part-num-ref>
+ can accommodate any number of other types of features.    </p>
+    <p id="p-53" num="53">[0041<confidence value="5">]</confidence>
+  In addition, performance can generally be expected to be a monotonic function. For example performance steadily degrades as the amount of data grows and as the amount of available memory decreases.    </p>
+    <p id="p-54" num="54">The maps can therefore also note areas where performance is other than monotonic. Thus, the circled area labeled "cliff<confidence value="5">"</confidence>
+ can note the coordinates of an area where throughput drops off sharply. Similarly, the circled area labeled "sinkhole" marks a small range of memory and input cardinality values for which throughput drops off sharply, only to resume expected levels of throughput upon exiting the area. Such a robustness map can accommodate any number of other types of features.    </p>
+    <p id="p-55" num="55">[0042<confidence value="5">]</confidence>
+  A query statement can be executed in many different ways, for example full table scans, index scans, nested loops, hash joins, and others. A query optimizer is a component of a database management system that attempts to determine the most efficient way to execute a query. The query optimizer determines the most efficient way to execute a SQL statement after considering many factors related to the objects referenced and the conditions <page-break num="13"/>
+      <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+      <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+      <boundary-data type="header">
+        <confidence value="8888">-13-</confidence>
+      </boundary-data>
+specified in the query. The determination is a useful step in the processing of any query statement and can greatly affect execution time.    </p>
+    <p id="p-56" num="56">[0043<confidence value="5">]</confidence>
+  The query optimizer compares the available query plans for a target input query and estimates which of plan will be the most efficient in practice.    </p>
+    <p id="p-57" num="57">One type of query optimizer operates on a cost basis and assigns an estimated cost to each possible query plan, for example selecting the plan with the smallest cost. Costs can be used to estimate the runtime cost of evaluating the query in terms of factors such as the number of <confidence value="686">I/O</confidence>
+ operations required, processor load requirements, and other factors which can be set forth in a data structure called a data dictionary which stores statistics used by the query optimizer. The set of available query plans that are examined is formed by examining the possible access paths, such as index scan and sequential scan, and join algorithms including sort-merge join, hash join, nested loops, and others. A search space can become very large according to complexity of the query.    </p>
+    <p id="p-58" num="58">[0044<confidence value="5">]</confidence>
+  Considering that performance of a database system during processing of a query depends on the ability of a query optimizer to select an appropriate plan for executing the query under an expected set of conditions (for example, cardinality estimates, resource availability assumptions), and the ability of an executor to process the query using the selected plan under actual runtime conditions, a challenge arises that actual runtime conditions can differ significantly from what is expected, particularly in situations where multiple queries execute simultaneously. For example, data skew can cause cardinality to exceed expectations by multiple orders of magnitude, or an unexpectedly heavyweight query can monopolize memory, leaving only a fraction of expected memory available. In a worst case, actual runtime conditions can be so adverse that the selected query plan can potentially be the worst, as opposed to the best, plan for the given conditions.    </p>
+    <p id="p-59" num="59">[0045<confidence value="5">]</confidence>
+  In addition, database operator implementations are typically tested to verify performance at specific points, as opposed to tested in terms of the <page-break num="14"/>
+      <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+      <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+      <boundary-data type="header">
+        <confidence value="8">-</confidence>
+ <confidence value="888">14-</confidence>
+      </boundary-data>
+continuity of performance degradation over a large range of conditions. Thus, performance can suddenly degrade dramatically and unexpectedly with only a minor change in conditions. Accordingly, the system <part-num-ref name="system">100</part-num-ref>
+ depicted in FIGURE <confidence value="5">1</confidence>
+ and associated functionality, by creating a map of performance under a large range of conditions, enables the prediction and analysis of such performance degradation.    </p>
+    <p id="p-60" num="60">[0046<confidence value="5">]</confidence>
+  The robustness maps in FIGUREs 6A and 6B can be analyzed to detect a condition in which performance improves as work increases or as resources decrease, an indication of drastically incorrect operation since inherent in proper operation is that database performance degrades with increased work and fewer resources. One example of such incorrect operation is shown as the sinkhole <part-num-ref name="sinkhole">604</part-num-ref>
+ in FIGUREs 6A and 6B. In a two- dimensional visualization of absolute performance, incorrect operation can be visualized as lines that slant downward, then upward. (In contrast, in robustness maps for which performance is shown relative to best performance, such behavior is not indicative of incorrect behavior.) [0047<confidence value="5">]</confidence>
+  Referring to FIGURE 6C, a diagram illustrates an example of a two- dimensional parameter space robustness table with single-table, single- predicate selection and shows execution times for selecting rows from a table (Transaction Processing Performance Council (TPC-H) benchmark line items, about 60M rows) for a variety of selectivities (result sizes). Selectivities and execution times both are shown with logarithmic scales. Query result sizes differ by a factor of two between data points. FIGURE 6C shows performance of three query execution plans. One plan is a traditional table scan with performance constant across the entire range of selectivities. For small result sizes, the table scan is unacceptably slow compared to the index scans. A second plan is a traditional index scan, which is unacceptably slow for moderate and large result sizes due to the need to fetch qualifying rows from the table. Cost of the index scan is so high that showing the entire range of selectivities is not possible. The break-even point between table scan and traditional index scan is at about 30K result rows or 2<confidence value="566">-11</confidence>
+ of the rows in the <page-break num="15"/>
+      <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+      <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+      <boundary-data type="header">
+        <confidence value="8888">-15-</confidence>
+      </boundary-data>
+table. A third plan is an improved index scan which combines low latency for small results as well as high bandwidth for moderate result sizes. The cost of the improved index scan remains competitive with the table scan all the way up to about 4M result rows or 2-<confidence value="5">4</confidence>
+ <confidence value="6">o</confidence>
+f the rows in the table. However, the improved index scan, despite improvement over the traditional index scan, has performance that is poor for large results. If all rows in the table satisfy the query predicate, the performance of the improved index scan is about 2<confidence value="5">%</confidence>
+ times worse than a table scan. While a factor of 2<confidence value="5">%</confidence>
+ is undesirable, cost is much less than cost of a traditional index scan which would exceed the cost of a table scan by multiple orders of magnitude.    </p>
+    <p id="p-61" num="61">[0048<confidence value="5">]</confidence>
+  An optimistic insight from FIGURE 6C is that robust execution seems possible. A pessimistic insight is that the improved index scan as implemented in the system is not yet sufficiently robust. One perspective view is that a single query execution plan might eventually be superior or at least competitive across the entire range so that an erroneous choice during compile-time query optimization can be avoided by eliminating selection among alternatives. Another perspective view is that the query execution engine has not yet reached a sufficient level of sophistication and robustness.    </p>
+    <p id="p-62" num="62">Considering the simple techniques that underlie the "improved" plan in FIGURE 6C, appropriate run-time techniques can be used based on the usage of robustness maps analysis.</p>
+    <p id="p-63" num="63">[0049<confidence value="5">]</confidence>
+  Although FIGURE 6C can enable observations, insights, and perspective on a research effort, other visualizations enable additional insights into additional aspects of robustness and are helpful for individual operations such as index scans and for plan fragments such as scans of multiple indexes combined by index intersection. Visual images greatly assist in identifying poor scalability or robustness, discontinuities in actual execution costs, and the like. Thus, the further visualizations help in analyzing and reasoning about query execution algorithms, implementations, entire query execution plans or fragments thereof, and the query execution architecture.    </p>
+    <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+    <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+    <boundary-data type="header">
+      <confidence value="8888">-16-</confidence>
+    </boundary-data>
+    <p id="p-64" num="64">
+      <page-break num="16"/>
+[0050<confidence value="5">]</confidence>
+  The visualizations can be employed by database software vendors to target improvements in query execution, indexing techniques, and query optimization. The visualizations can be used by database administrators to analyze specific query execution plans to address unsatisfactory performance or robustness of query execution. Various visualizations have been found particularly helpful and are disclosed herein.    </p>
+    <p id="p-65" num="65">[0051<confidence value="5">]</confidence>
+  FIGURE 6C is an example of a simple visualization of performance and robustness. One aspect of performance that can be verified by the two- dimensional diagram is that the actual execution cost is monotonic across the parameter space. For example, fetching of rows is expected to become more expensive with additional rows. If cases exist in which fetching more rows is cheaper than fetching fewer rows, some aspect of performance is anomalous.    </p>
+    <p id="p-66" num="66">For example, the governing policy or some implementation mechanisms might be faulty in the algorithms that switch to pre-fetching large pages instead of fetching individual pages as needed. Moreover, the cost curve is expected to flatten, wherein the first derivative of the cost curve should monotonically decrease. Fetching more rows should cost more, but the difference between fetching <part-num-ref name="difference between fetching">100</part-num-ref>
+ and <part-num-ref name="and">200</part-num-ref>
+ rows should not be greater than between fetching 1,000 and 1,100 rows, a condition that is not true for the improved index scan shown in FIGURE 6C since the curve for the improved index scan shows a flat cost growth followed by a steeper cost growth for very large result sizes.    </p>
+    <p id="p-67" num="67">[0052<confidence value="5">]</confidence>
+  FIGURE 6<confidence value="5">D</confidence>
+ is a diagram showing performance of plans for a simple query similar to the query of FIGURE 6C, with two differences. First, performance is shown not in absolute times but relative to the best plan for each point in the parameter space. This type of diagram is most appropriate if the absolute performance varies very widely across the parameter space. In FIGURE 6C for example, the left-most data point still represents an output size of about <part-num-ref name="output size of about">900</part-num-ref>
+ rows (60Mx2<confidence value="2">-</confidence>
+16)<confidence value="5">.</confidence>
+ Even with a logarithmic scale for query execution costs, extending the diagram all the way to one output row would increase diagram height or reduce vertical resolution by a factor of 2<confidence value="668">/2.</confidence>
+    </p>
+    <p id="p-68" num="68">Illustrating the relative performance of all plans may permit better resolution <page-break num="17"/>
+      <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+      <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+      <boundary-data type="header">
+        <confidence value="8888">-17-</confidence>
+      </boundary-data>
+and better use of the space available for a diagram. Second, additional query execution plans are included, specifically multi-index plans that join non- clustered indexes such that the join result covers the query even if no single non-clustered index does. These index joins are performed by alternative join algorithms and using alternative join orders.    </p>
+    <p id="p-69" num="69">[0053<confidence value="5">]</confidence>
+  When comparing query execution plans for a given query, analysis includes determination of which classes of query execution plans to include such as: <part-num-ref name="given query, analysis includes determination of which classes of query execution plans to include such as:">(1)</part-num-ref>
+ only plans actually considered by the system under investigation;    </p>
+    <p id="p-70" num="70">(2) plans that could be forced by some means or other including alternative syntax (for example, index intersection by means of multiple query aliases for the same database table); <part-num-ref name="same database table);">(3)</part-num-ref>
+ plans that could be enabled only by an alternative database design (such as two-column indexes); or <part-num-ref name="alternative database design (such as two-column indexes); or">(4)</part-num-ref>
+ plans that could be realized only with additional implementation effort by the software vendor (such as bitmap indexes, bitmap-driven sorting or intersection). Actual execution costs for the fourth class might be obtained through experiments using a competing database system that is more advanced in specific query execution techniques. The most appropriate class choice depends on whether design and future improvements of system components can be selected. For example, plans enabled by alternative syntax can considered if influence over the rewrite capabilities in the query optimization steps is available.    </p>
+    <p id="p-71" num="71">[0054<confidence value="5">]</confidence>
+  The diagrams can be implemented using either linear or logarithmic scales. Logarithmic scales on both axes permit reasonably detailed insight at both ends of the spectrum of possible parameter values. Curves can be formed to indicate absolute performance or performance relative to the best plan for any one point in the parameter space, where the definition for "best" might include any of the classes of query execution plans.    </p>
+    <p id="p-72" num="72">[0055<confidence value="5">]</confidence>
+  Robustness maps can also display performance in three- dimensional parameter spaces. Limitation to a single dimension within the parameter space both focuses and limits the insights. The interaction of <page-break num="18"/>
+      <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+      <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+      <boundary-data type="header">
+        <confidence value="8888">-18-</confidence>
+      </boundary-data>
+dimensions can also be considered. The number of possible parameters may be very high, including multiple formal query parameters with run-time bindings; resource availability such as memory, processing bandwidth, <confidence value="686">I/O</confidence>
+ bandwidth, and interconnection bandwidth; and intermediate result sizes due to predicates (selection, joins), aggregation (projection, duplicate removal), and set operations (intersection, union, difference). Visualization practically forces consideration of two dimensions at a time and rotation through pairs of dimensions.    </p>
+    <p id="p-73" num="73">[0056<confidence value="5">]</confidence>
+  System tests can use various performance map visualizations to compare performance of an operator or query component to best performance. For example, referring to FIGUREs 6C and 6<confidence value="5">D</confidence>
+, performance is shown compared to best possible performance. FIGUREs 6C and 6<confidence value="5">D</confidence>
+ show measurements resulting from execution of many different methods. For example, as depicted in FIGURE 4C, an performance of an index scan is shown compared to the table scan which is the best performing plan at the end of the graph where selectivity is <part-num-ref name="graph where selectivity is">1,</part-num-ref>
+ and an improved index scan which has a much higher execution time and lower performance. The traditional index scan (fine dotted line) has an execution time that extends off the page so that improvements may be sought to attain better performance. At a cross-over point, the table scan (dashed line) performance meets the traditional index scan (dotted line) so that the traditional scan (dotted line) rapidly and substantially degrades in comparison to the table scan (dashed line). Both the table scan and the traditional index scan perform the same task, but the traditional index scan performs scanning much less efficiently after the cross- over point. Thus, improvements may be sought in the region after the cross- over, for which the degraded performance of the traditional index scan may result from, for example, memory overflow. Improvements may be sought to attain performance similar to the improved index scan (solid line).    </p>
+    <p id="p-74" num="74">[0057<confidence value="5">]</confidence>
+  Referring to FIGURE 6E, a three-dimensional map is shown which displays a parameter, illustratively execution time, in grayscale-coding or color-coding. The mapping shows elapsed times in colors or monochrome <page-break num="19"/>
+      <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+      <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+      <boundary-data type="header">
+        <confidence value="8888">-19-</confidence>
+      </boundary-data>
+shades from green to red and finally black (light gray to black in monochrome) with each color or shade difference indicating an order of magnitude.    </p>
+    <p id="p-75" num="75">FIGURE 6E illustrates two-predicate, single-index selection, showing the execution cost for a query restricting two columns of a table. The query execution plan scans a single-column index and applies the second predicate only after fetching entire rows from the table's main storage structure. The two dimensions shown are the selectivities of the two predicate clauses. The third dimension is execution time, ranging from <part-num-ref name="third dimension is execution time, ranging from">4</part-num-ref>
+ seconds to <part-num-ref name="seconds to">890</part-num-ref>
+ seconds.    </p>
+    <p id="p-76" num="76">[0058<confidence value="5">]</confidence>
+  As shown in FIGURE 6E, the two dimensions have very different effects. In fact, one of the predicates appears to have practically no effect at all wherein the predicate can be evaluated only after fetching entire rows - a result which is predictable because index scans perform as expected and as coded in the cost calculations during query optimization. The actual behavior meets the anticipated behavior (reflected correctly in the cost function used during query optimization). FIGURE 6E shows the robust query execution technology from FIGURE 6C. While barely visible in FIGURE 6E, FIGURE 6C illustrates robustness very succinctly, demonstrating the value of visualizations using a combination of one-dimensional and two-dimensional parameter spaces.    </p>
+    <p id="p-77" num="77">[0059<confidence value="5">]</confidence>
+  Referring to FIGURE 6F, a three-dimensional diagram illustrates operation of a two-index merge join, and shows the execution cost for an alternative query execution plan, specifically scans of two single-column non- clustered indexes combined by a merge join. Other than some measurement flukes in the sub-second range (front left, green), the symmetry in the diagram indicates that the two dimensions have very similar effects. Hash join plans perform better in some cases but do not exhibit symmetry.    </p>
+    <p id="p-78" num="78">[0060<confidence value="5">]</confidence>
+  In addition to the two plans depicted in FIGUREs 6E and 6F, FIGURE 6G illustrates a map acquired by running five additional alternative query execution plans for the simple query. The query execution plans include a no-index table scan (actually, scanning a clustered index organized <page-break num="20"/>
+      <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+      <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+      <boundary-data type="header">
+        <confidence value="8">-</confidence>
+ <confidence value="88">20</confidence>
+ <confidence value="8">-</confidence>
+      </boundary-data>
+on an entirely unrelated column), a plan using a single-column non-clustered index for the other predicate clause, and three other plans combining two single-column non-clustered indexes (using merge join or hash join each in two join orders). The relative performance of each individual plan is plotted compared to the optimal plan at each point in the parameter space. A given plan is optimal if performance is equal to the optimal performance among all plans, so that the quotient of costs is <part-num-ref name="quotient of costs is">1.</part-num-ref>
+ A plan is sub-optimal if the quotient is much higher than <part-num-ref name="quotient is much higher than">1.</part-num-ref>
+    </p>
+    <p id="p-79" num="79">[0061<confidence value="5">]</confidence>
+  Referring to FIGURE 6G, a three-dimensional diagram depicts performance of a single-index can relative to the best of seven plans.    </p>
+    <p id="p-80" num="80">FIGURE 6G shows the same data as FIGURE 6E with performance indicated in terms of the relative difference to the best plan at each point. The diagram enables immediate recognition that the plan is optimal only in a small part of the parameter space. Moreover, the region is not continuous. While the absolute performance shown in FIGURE 6E is fairly smooth, the relative performance shown in FIGURE 6G is not smooth indicating that the costs of best plans are not smooth. In the example, the maximal difference is a factor of 101,000. Thus, while the plan is optimal in some regions of the parameter space, the worst relative performance is so poor that disruption of data center operation is likely.</p>
+    <p id="p-81" num="81">[0062<confidence value="5">]</confidence>
+  Referring to FIGURE 6H, a three-dimensional diagram illustrates relative performance of a system using a two-column index, depicting the relative performance of a plan with a covering two-column index in an a software system different from that analyzed with respect to FIGURE 6G.    </p>
+    <p id="p-82" num="82">Due to multi-version concurrency control applied only to rows in the main table, the plan involves fetching full rows. In other words, the space overhead of multi-version concurrency control seems to have forced the developers of the system to apply concurrency control only to rows in the main representation of the table. Thus, the advantages of covering non-clustered indexes, including joins of multiple non-clustered indexes are disabled.</p>
+    <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+    <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+    <boundary-data type="header">
+      <confidence value="8">-</confidence>
+ <confidence value="88">21</confidence>
+ <confidence value="8">-</confidence>
+    </boundary-data>
+    <p id="p-83" num="83">
+      <page-break num="21"/>
+[0063<confidence value="5">]</confidence>
+  In the query execution plan, rows to be fetched are sorted very efficiently using a bitmap. The plan is close to optimal in this system over a much larger region of the parameter space. Moreover, the plan's worst quotient is not as bad as that of the prior plan shown in FIGURE 6G. Thus, if the actual value of parameters is not known at compile-time, the plan is probably much more desirable even if the plans of FIGURE 6E and FIGURE 6F are judged more efficient at compile-time based on anticipated predicate selectivities. Thus, robustness might well trump performance in those situations.    </p>
+    <p id="p-84" num="84">[0064<confidence value="5">]</confidence>
+  Referring to FIGURE 61, a three-dimensional robustness map shows the most robust plan in a third system. Relative performance is good across the entire parameter space, albeit not optimal. The foundation of consistent performance is a sophisticated scan for multi-column indexes described as multi-dimensional B-tree access. Data points indicate that the plan is the best query execution plan (indicated by a cost factor <part-num-ref name="cost factor">1</part-num-ref>
+ or a light green color or light monochrome shade).    </p>
+    <p id="p-85" num="85">[0065<confidence value="5">]</confidence>
+  The visualization techniques employed to form the diagrams enable rapid verification of expected performance, testing of hypotheses, and insight into absolute and relative performance of alternative query execution plans.    </p>
+    <p id="p-86" num="86">For even a very simple query, a plethora of query execution plans can be used. Investigating many plans over a parameter space with multiple dimensions is possible only with efficient visualizations.</p>
+    <p id="p-87" num="87">[0066<confidence value="5">]</confidence>
+  Other robustness maps can be created to analyze other aspects of performance. For example, worst performance can be mapped to detect particularly dangerous plans and relative performance of plans compared to worst possible performance. In addition, multiple systems and available plans can be compared in combination.    </p>
+    <p id="p-88" num="88">[0067<confidence value="5">]</confidence>
+  Other software development activities can be performed on the basis of the visualizations. For example, a developer can focus on improving the performance of the best plan at some points deemed important within the <page-break num="22"/>
+      <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+      <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+      <boundary-data type="header">
+        <confidence value="8">-</confidence>
+ <confidence value="88">22</confidence>
+ <confidence value="8">-</confidence>
+      </boundary-data>
+parameter space - a traditional focus on achievable performance. Also, a developer can focus on performance of the plan with the broadest region of acceptable performance and then improve performance in the regions of the parameter space where the plan's performance is poor - a focus on robustness of a specific plan and, if that plan is chosen during query optimization, on robustness of query processing as a whole.    </p>
+    <p id="p-89" num="89">[0068<confidence value="5">]</confidence>
+  Another robustness map visualization is a single map showing all possible query execution plans, indicating the best plan for each point and region in the parameter space, perhaps using a color for each plan. One aspect of the map can be the size and the shape of each plan's optimality region. The regions can be continuous, simple shapes.    </p>
+    <p id="p-90" num="90">[0069<confidence value="5">]</confidence>
+  For query execution, analysis can focus on irregular shapes of optimality regions. Often, some implementation idiosyncrasy rather than the algorithm can cause the irregular shape. Removal of such idiosyncrasies may lead to more efficient as well as more robust query execution.    </p>
+    <p id="p-91" num="91">[0070<confidence value="5">]</confidence>
+  Some techniques can enlarge the largest region, possibly even eliminating some smaller regions and thus some plans from the map of optimality. Every plan eliminated from the map implies that query analysis need not consider the eliminated plan. Reducing the plan space in query analysis contributes to the robustness.    </p>
+    <p id="p-92" num="92">[0071<confidence value="5">]</confidence>
+  Referring to FIGURE 6J, a diagram, shows mapping of regions of optimality. Most points in the parameter space have multiple optimal plans (within 0.1 sec measurement error). In fact, when analyzing optimality, all small differences should be neglected. For example, two plans with actual execution costs within 1% of each other are practically equivalent. Whether the tolerance ends at <part-num-ref name="tolerance ends at">1</part-num-ref>
+ % difference, at 20% difference, or at a factor of <part-num-ref name="factor of">2</part-num-ref>
+ depends on a tradeoff between performance and robustness, and thus the tradeoff between the expense of system resources and the expense of human effort for tuning and problem resolution.    </p>
+    <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+    <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+    <boundary-data type="header">
+      <confidence value="8">-</confidence>
+ <confidence value="88">23</confidence>
+ <confidence value="8">-</confidence>
+    </boundary-data>
+    <p id="p-93" num="93">
+      <page-break num="23"/>
+[0072<confidence value="5">]</confidence>
+  Variants of FIGURE 6H and FIGURE 61 can be used to show the region of optimality for a specific plan. Since the number of plans that may cover any one point in the parameter space is large, shading using two colors is typically not sufficient, but a diagram with points shaded in a large number of colors seems more confusing than illuminating. Thus, this type of diagram inherently requires one diagram per plan and thus many diagrams.    </p>
+    <p id="p-94" num="94">[0073<confidence value="5">]</confidence>
+  FIGUREs 6K(1) and 6K(2) illustrate robustness maps for two- predicate index scan implementations. Robustness maps are designed to quantify and visualize how performance degrades as work increases and resources decrease. A plan or operator under test is fixed and performance is measured while forcing execution across a spectrum of conditions with results then plotted in a Euclidean space. The resulting shape illustrates performance degradation patterns. Slope indicates how quickly performance degrades, while curvature indicates how predictably performance degrades.    </p>
+    <p id="p-95" num="95">Areas where the rate of performance rapidly and unpredictably drops are manifest. For example, FIGUREs 6K(1) and 6K(2) compare three- dimensional robustness maps for two different implementations of a given operator, charting performance of an index scan while varying the selectivity of two predicates. Other robustness maps can be used to show how a given plan's performance compares to that of the best plan. Although only two- and three-dimensional maps are depicted herein, the technique can be used with any metric space.</p>
+    <p id="p-96" num="96">[0074<confidence value="5">]</confidence>
+  Robustness maps enable analysis and reasoning about the executor's impact on query robustness. By making visible where and how performance changes, the maps show developers and regression testers the circumstances under which performance is particularly sensitive to small deviations from expected conditions. Developers can then address this sensitivity. Robustness maps thus enable a different view of performance than tests that focus on pure execution time or throughput. Robustness maps enable motivation, tracking, and protection of improvements in query <page-break num="24"/>
+      <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+      <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+      <boundary-data type="header">
+        <confidence value="8">-</confidence>
+ <confidence value="88">24</confidence>
+ <confidence value="8">-</confidence>
+      </boundary-data>
+execution by providing a concrete and intuitive "big picture" of the performance landscape.    </p>
+    <p id="p-97" num="97">[0075<confidence value="5">]</confidence>
+  The robustness map approach can be tested by building robustness maps for simple queries from the TPC-H benchmark. A<confidence value="66">ll</confidence>
+ database instances can be loaded with the same line item table, using the same rows (in the same order). A scale factor <part-num-ref name="scale factor">10</part-num-ref>
+ instance of TPC-H can be used resulting, for example, in 60M rows <part-num-ref name="instance of TPC-H can be used resulting, for example, in 60M rows">(6</part-num-ref>
+ GB). In an example analysis, five indexes are built upon the table including a default clustered index on the primary key, two single column indexes on the query predicate columns, and a pair of two- column indexes on the query predicate columns. A selected number of maps are constructed and analyzed for the three systems. For example, FIGUREs 6K(1,2) show that one implementation of index nested loops join is more resilient than another to variance in input data sizes, a graceful degradation that may result from the first implementation's efficient sort operation.    </p>
+    <p id="p-98" num="98">[0076<confidence value="5">]</confidence>
+  Thus robustness maps can be used to evaluate the robustness of a sort operator. FIGURE 6L shows a three-dimensional robustness map comparing the relative performance of the sort operator while varying selectivity and duplicate values. A dramatic drop in performance occurs when the data input no longer fits in memory. If estimated selectivity were one row short of the amount that would fit into memory, and the actual data size only two rows more, the sort operation would take nearly five times longer than expected.    </p>
+    <p id="p-99" num="99">[0077<confidence value="5">]</confidence>
+  Although such a performance drop or cliff could be considered easily anticipated, since memory availability and cardinality estimates can be checked at compile-time, when the plan is selected. However, a query optimizer bases cost estimates for a sort operation on the amount of configured memory and initial cardinality estimates, both of which are subject to significant change from compile time to run-time. Resource contention can reduce the amount of available memory to a small fraction of that anticipated.    </p>
+    <p id="p-100" num="100">Multiple levels of intermediate results can compound that impact. FIGURE 6M <page-break num="25"/>
+      <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+      <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+      <boundary-data type="header">
+        <confidence value="8">-</confidence>
+ <confidence value="88">25</confidence>
+ <confidence value="8">-</confidence>
+      </boundary-data>
+maps how performance degrades as available memory decreases and shows how memory contention changes the location of the critical point where a small increase in data size causes a major drop in performance.    </p>
+    <p id="p-101" num="101">[0078<confidence value="5">]</confidence>
+  System tests can use various performance map visualizations for identifying anomalies. For example, referring to FIGUREs 6L and 6M, anomalies are shown wherein input that overflows memory by even the slightest amount results in a substantial (for example, <part-num-ref name="substantial (for example,">15</part-num-ref>
+ second or more) penalty in execution time. The performance maps show anomalies that occur for one particular operator on one particular query running on one particular system. Test procedures analyze the performance maps to identify such anomalies. For example, to identify unexpected jumps shown in FIGUREs 6L and 6M, the test procedure analyzes the degree of curvature between data points.    </p>
+    <p id="p-102" num="102">[0079<confidence value="5">]</confidence>
+  Run-time performance of any query plan can vary dramatically depending on execution conditions such as actual predicate selectivity and contention for memory and other resources. Execution conditions vary unpredictably, leading to the unexpectedly long-running queries that plague database users and administrators today. Thus, robust query processing reduces cost of ownership by reducing the need for human intervention.    </p>
+    <p id="p-103" num="103">[0080<confidence value="5">]</confidence>
+  In general, robustness in database query processing can be improved by modifications in query optimization, query execution, workload management, and other components. The systems and techniques disclosed herein focus on query execution. Robustness maps can be used to visualize performance of query execution algorithms and plan fragments, enabling understanding of behavior across a wide range of unexpected situations.    </p>
+    <p id="p-104" num="104">[0081<confidence value="5">]</confidence>
+  Various visualization techniques reveal different insights.    </p>
+    <p id="p-105" num="105">Robustness maps with two- and three-dimensional parameter spaces are introduced, including discussion of robustness map interpretation, a demonstration of how to detect landmarks that appear on the maps, and a discussion of implications for robustness.</p>
+    <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+    <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+    <boundary-data type="header">
+      <confidence value="8">-</confidence>
+ <confidence value="88">26</confidence>
+ <confidence value="8">-</confidence>
+    </boundary-data>
+    <p id="p-106" num="106">
+      <page-break num="26"/>
+[0082<confidence value="5">]</confidence>
+  Visualizing the performance of specific algorithms, associated implementations, and plan fragments using the algorithms enables analysis of strengths and weaknesses. Adaptive techniques during run-time query execution can have as great an impact on robust query processing as plan choices during compile-time query optimization. Adaptive run-time techniques pertain to data volumes, resource availability including memory, and the specifics of the memory hierarchy.    </p>
+    <p id="p-107" num="107">[0083<confidence value="5">]</confidence>
+  Robustness map analysis and its visualization can be extended to additional query execution algorithms including sort, aggregation, join algorithms, and join order. For example, some implementations of sorting spill their entire input to disk if the input size exceeds the memory size by merely a single record. Those sort implementations lacking graceful degradation will show discontinuous execution costs. Other resources may introduce similar effect, such as a sort input exceeding the size of the CPU cache or the size of flash memory.    </p>
+    <p id="p-108" num="108">[0084<confidence value="5">]</confidence>
+  Robustness maps enable visualizations of entire query execution plans including parallel plans. A benchmark can be defined that focuses on robustness of query execution and, more generally, of query processing. The benchmark can be used to identify weaknesses in the algorithms and implementations, track progress against weaknesses, and permit daily regression testing to protect the progress against accidental regression due to other, seemingly unrelated, software changes.    </p>
+    <p id="p-109" num="109">[0085<confidence value="5">]</confidence>
+  Terms "substantially", "essentially", or "approximately", that may be used herein, relate to an industry-accepted tolerance to the corresponding term. Such an industry-accepted tolerance ranges from less than one percent to twenty percent and corresponds to, but is not limited to, functionality, values, process variations, sizes, operating speeds, and the like. The term "coupled", as may be used herein, includes direct coupling and indirect coupling via another component, element, circuit, or module where, for indirect coupling, the intervening component, element, circuit, or module does <page-break num="27"/>
+      <boundary-data type="header">Docket No. 200802156-1</boundary-data>
+      <boundary-data type="header">KB No.: 1015.P282 US</boundary-data>
+      <boundary-data type="header">
+        <confidence value="8">-</confidence>
+ <confidence value="88">27</confidence>
+ <confidence value="8">-</confidence>
+      </boundary-data>
+not modify the information of a signal but may adjust its current level, voltage level, and/or power level. Inferred coupling, for example where one element is coupled to another element by inference, includes direct and indirect coupling between two elements in the same manner as "coupled".    </p>
+    <p id="p-110" num="110">[0086<confidence value="5">]</confidence>
+  The illustrative block diagrams and flow charts depict process steps or blocks that may represent modules, segments, or portions of code that include one or more executable instructions for implementing specific logical functions or steps in the process. Although the particular examples illustrate specific process steps or acts, many alternative implementations are possible and commonly made by simple design choice. Acts and steps may be executed in different order from the specific description herein, based on considerations of function, purpose, conformance to standard, legacy structure, and the like.    </p>
+    <p id="p-111" num="111">[0087<confidence value="5">]</confidence>
+  While the present disclosure describes various embodiments, these embodiments are to be understood as illustrative and do not limit the claim scope. Many variations, modifications, additions and improvements of the described embodiments are possible. For example, those having ordinary skill in the art will readily implement the steps necessary to provide the structures and methods disclosed herein, and will understand that the process parameters, materials, and dimensions are given by way of example only. The parameters, materials, and dimensions can be varied to achieve the desired structure as well as modifications, which are within the scope of the claims. Variations and modifications of the embodiments disclosed herein may also be made while remaining within the scope of the following claims.    </p>
+  </description>
+</us-patent-application>
+

applicant/12429289.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>12429289</doc-number>
+        <date>2010-12-01</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">Application No. 12/429,289 Amendment Accompanying RCE Amendments to the Specification:</p>
+    <p id="p-2" num="2">Page 1, lines 1-2: Replace the title section with the following amended title section:</p>
+    <heading id="h-1">TITLE OF THE INVENTION</heading>
+    <p id="p-3" num="3">Objects having usage rules that exist outside of the <confidence value="2222222222">evirenniet</confidence>
+ document in which the object is used <part-num-ref name="object is used">
+        <confidence value="8">2</confidence>
+      </part-num-ref>
+     </p>
+  </description>
+</us-patent-application>
+

applicant/12582773.xml

@@ -0,0 +1,272 @@
+<?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>12582773</doc-number>
+        <date>2009-10-21</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <boundary-data type="header">22562-257<confidence value="686">/TO</confidence>
+Y2009-093    </boundary-data>
+    <heading id="h-1">VENT ASSEMBLIES</heading>
+    <heading id="h-2">TECHNICAL FIELD</heading>
+    <p id="p-1" num="1">[0001]       The invention relates to vent assemblies, and more particularly, to vent assemblies that retain components during airbag deployment.</p>
+    <heading id="h-3">BACKGROUND</heading>
+    <p id="p-2" num="2">[0002]       During airbag deployment, components may become detached from vent assemblies. Accordingly, vent assemblies that retain detached components during airbag deployment are of continued interest.</p>
+    <heading id="h-4">SUMMARY</heading>
+    <p id="p-3" num="3">[0003]       One embodiment of a vent assembly includes a fin/actuator sub-assembly that includes an aperture, an inner ring that includes a plurality of protrusions, each protrusion including a retention surface, and an annular retaining member, wherein when the annular retaining member is in a retaining engagement with the fin/actuator sub-assembly and the inner ring, a portion of the annular retaining member is disposed within the aperture of the fin/actuator sub-assembly, and portions of the annular retaining member contact the retention surfaces of the protrusions of the inner ring.</p>
+    <p id="p-4" num="4">[0004]       Another embodiment of a vent assembly includes a fin/actuator sub-assembly that includes at least one fin and an actuator, the actuator including an aperture, an inner ring that includes a plurality of tabs, each tab including a retention surface, and an <confidence value="4">O</confidence>
+-ring, wherein when the <confidence value="4">O</confidence>
+-ring is in a retaining engagement with the inner ring and the fin/actuator sub- assembly, a portion of the <confidence value="4">O</confidence>
+-ring is disposed within the aperture of the actuator, and portions of the <confidence value="4">O</confidence>
+-ring contact the retention surfaces of the tabs of the inner ring.    </p>
+    <p id="p-5" num="5">[0005]       Another embodiment of a vent assembly includes a fin/actuator sub-assembly that includes an aperture, an inner ring that includes a plurality of tabs, each tab including a retention surface, a flexible <confidence value="4">O</confidence>
+-ring, an outer ring, and a back ring, wherein when the <confidence value="4">O</confidence>
+-ring is in a retaining engagement with the inner ring and the fin/actuator sub-assembly, a portion of the <confidence value="4">O</confidence>
+-ring is disposed within the aperture of the fin/actuator sub-assembly, and portions of the <confidence value="4">O</confidence>
+-ring contact the retention surfaces of the tabs of the inner ring.    </p>
+    <boundary-data type="header">
+      <confidence value="8">1</confidence>
+    </boundary-data>
+    <boundary-data type="header">22562-257<confidence value="686">/TO</confidence>
+Y2009-093    </boundary-data>
+    <p id="p-6" num="6">
+      <page-break num="2"/>
+[0006]      These and additional features can be more fully understood in view of the following detailed description, in conjunction with the drawings.    </p>
+    <heading id="h-5">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
+    <p id="p-7" num="7">[0007]      While the specification concludes with claims particularly pointing out and distinctly claiming the present invention, it is believed that the same will be better understood from the following description taken in conjunction with the accompanying drawings in which:</p>
+    <p id="p-8" num="8">[0008]      FIG. 1 is an exploded view of an embodiment of a vent assembly;</p>
+    <p id="p-9" num="9">[0009]      FIG. 2 is a front view of an embodiment of a vent assembly;</p>
+    <p id="p-10" num="10">[0010]      FIG. 3 is a rear perspective view of the vent assembly of FIG. 2; and [0011]      FIG. 4 is a rear perspective view of an embodiment of a vent assembly.</p>
+    <heading id="h-6">DETAILED DESCRIPTION</heading>
+    <p id="p-11" num="11">[0012]      Refe<confidence value="66">rr</confidence>
+ing to FIG. 1, embodiments of a vent assembly <part-num-ref name="vent assembly">100</part-num-ref>
+ may include a fin/actuator sub-assembly <part-num-ref name="fin/actuator sub-assembly">400,</part-num-ref>
+ an inner ring <part-num-ref name="inner ring">300</part-num-ref>
+ and an annular retaining member <part-num-ref name="annular retaining member">700.</part-num-ref>
+    </p>
+    <p id="p-12" num="12">Embodiments of vent assembly 100 may also include an outer ring <part-num-ref name="outer ring">200</part-num-ref>
+ and a back ring <part-num-ref name="back ring">500.</part-num-ref>
+    </p>
+    <p id="p-13" num="13">A portion of a headliner <part-num-ref name="headliner">600</part-num-ref>
+ may be disposed between the assembled components of embodiments of vent assembly <part-num-ref name="assembled components of embodiments of vent assembly">100.</part-num-ref>
+    </p>
+    <p id="p-14" num="14">[0013]      Fin/actuator sub-assembly 400 may be circular in shape and may include a plurality of fins <part-num-ref name="plurality of fins">410</part-num-ref>
+ and an actuator <part-num-ref name="actuator">430.</part-num-ref>
+ The illustrated embodiments of vent assembly <part-num-ref name="illustrated embodiments of vent assembly">100</part-num-ref>
+ include a fin/actuator sub-assembly <part-num-ref name="fin/actuator sub-assembly">400</part-num-ref>
+ that has three fins <part-num-ref name="that has three fins">410</part-num-ref>
+ connected by actuator <part-num-ref name="connected by actuator">430.</part-num-ref>
+    </p>
+    <p id="p-15" num="15">Fins 410 function to direct air flowing through the vent assembly, and actuator <part-num-ref name="vent assembly, and actuator">430</part-num-ref>
+ functions to ensure that the plurality of fins are synced in movement. Accordingly, referring to FIG. 2, when a user presses on a designated contact area <part-num-ref name="designated contact area">420</part-num-ref>
+ on the front surface of the fins, or any other portion of the front surface of the fins, the plurality of fins operate in sync. Referring to FIG. 3, fin/actuator sub-assembly <part-num-ref name="plurality of fins operate in sync. Referring to FIG. 3, fin/actuator sub-assembly">400</part-num-ref>
+ may further include an aperture <part-num-ref name="aperture">440</part-num-ref>
+ for the retention of annular retaining member <part-num-ref name="retention of annular retaining member">700.</part-num-ref>
+ The aperture may be disposed at any location on fin/actuator sub-assembly <part-num-ref name="aperture may be disposed at any location on fin/actuator sub-assembly">400.</part-num-ref>
+ The illustrated embodiments of fin/actuator sub-assembly <part-num-ref name="illustrated embodiments of fin/actuator sub-assembly">400</part-num-ref>
+ include aperture <part-num-ref name="include aperture">440</part-num-ref>
+ that is a hole formed on the portion of actuator <part-num-ref name="portion of actuator">430</part-num-ref>
+ that is connected to the middle fin. However, aperture <part-num-ref name="middle fin. However, aperture">440</part-num-ref>
+ may be a hole formed on any other portion of fin/actuator <boundary-data type="header">
+        <confidence value="8">2</confidence>
+      </boundary-data>
+      <page-break num="3"/>
+      <boundary-data type="header">22562-257<confidence value="686">/TO</confidence>
+Y2009-093      </boundary-data>
+sub-assembly <part-num-ref name="hole formed on any other portion of fin/actuator sub-assembly">400,</part-num-ref>
+ including other portions of actuator <part-num-ref name="hole formed on any other portion of fin/actuator sub-assembly 400, including other portions of actuator">440</part-num-ref>
+ and any part of fins <part-num-ref name="and any part of fins">410.</part-num-ref>
+    </p>
+    <p id="p-16" num="16">Moreover, aperture 440 need not be a hole formed on the fin/actuator sub-assembly, and thus may comprise any void on the fin/actuator sub-assembly (e.g., the space between actuator fins <part-num-ref name="space between actuator fins">410</part-num-ref>
+ and actuator 430), or formed by any additional structure disposed on the fin/actuator sub-assembly, such as loop structure formed on actuator <part-num-ref name="fin/actuator sub-assembly, such as loop structure formed on actuator">430</part-num-ref>
+ and/or fins <part-num-ref name="and/or fins">410.</part-num-ref>
+    </p>
+    <p id="p-17" num="17">[0014]       Inner ring 300 may be annular-shaped to correspond to the shape of fin/actuator sub-assembly <part-num-ref name="shape of fin/actuator sub-assembly">400</part-num-ref>
+ and may include a plurality of protrusions <part-num-ref name="plurality of protrusions">310</part-num-ref>
+ (i.e., tabs). The illustrated embodiments of vent assembly <part-num-ref name="illustrated embodiments of vent assembly">100</part-num-ref>
+ include an inner ring <part-num-ref name="inner ring">300</part-num-ref>
+ that has two protrusions <part-num-ref name="that has two protrusions">310</part-num-ref>
+ that are tabs formed through the inclusion of grooves on the outside perimeter of the inner ring. However, any number, size, shape and/or style of protrusions may be included on inner ring <part-num-ref name="inner ring. However, any number, size, shape and/or style of protrusions may be included on inner ring">300.</part-num-ref>
+ Referring to FIG. 2, protrusions <part-num-ref name="inner ring. However, any number, size, shape and/or style of protrusions may be included on inner ring 300. Referring to FIG. 2, protrusions">310</part-num-ref>
+ each include a retention surface <part-num-ref name="retention surface">320</part-num-ref>
+ that functions to contact and retain a portion of annular retaining member <part-num-ref name="portion of annular retaining member">700.</part-num-ref>
+ In some embodiments, retention surface <part-num-ref name="portion of annular retaining member 700. In some embodiments, retention surface">320</part-num-ref>
+ may further include a groove or protrusion to further assist in the retention of annular retaining member <part-num-ref name="retention of annular retaining member">700.</part-num-ref>
+    </p>
+    <p id="p-18" num="18">[0015]       Annular retaining member 700 may function to retain fin/actuator sub- assembly <part-num-ref name="may function to retain fin/actuator sub- assembly">400</part-num-ref>
+ to inner ring <part-num-ref name="to inner ring">300</part-num-ref>
+ during airbag deployment (as further detailed below).    </p>
+    <p id="p-19" num="19">Annular retaining member 700 may be formed from any flexible, elastic or inelastic material known in the art, including, but not limited to, natural and synthetic rubbers, plastics, polymers and fibers. The cross-section of annular retaining member <part-num-ref name="cross-section of annular retaining member">700</part-num-ref>
+ may be any shape and/or size, including, but not limited to, flat, round and square. The illustrated embodiments of vent assembly <part-num-ref name="illustrated embodiments of vent assembly">100</part-num-ref>
+ include annular retaining member <part-num-ref name="include annular retaining member">700</part-num-ref>
+ that is a flexible <confidence value="5">O</confidence>
+-ring that is round in cross-section. However, other types of annular retaining members may be utilized, including various other types of <confidence value="5">O</confidence>
+-rings and bands.    </p>
+    <p id="p-20" num="20">[0016]       Outer ring 200 may be annular-shaped to correspond to the shape of inner ring <part-num-ref name="shape of inner ring">300</part-num-ref>
+ and may also include structure (e.g., tabs, protrusions and recesses) to connect to back ring <part-num-ref name="tabs, protrusions and recesses) to connect to back ring">500.</part-num-ref>
+ Back ring <part-num-ref name="tabs, protrusions and recesses) to connect to back ring 500. Back ring">500</part-num-ref>
+ may also be annular-shaped to correspond to the shape of inner ring <part-num-ref name="shape of inner ring">300</part-num-ref>
+ and may include structure (corresponding to the structure of outer ring <part-num-ref name="structure of outer ring">200)</part-num-ref>
+ to connect to outer ring <part-num-ref name="to connect to outer ring">200.</part-num-ref>
+ A stationary portion of the vehicle interior, such as headliner <part-num-ref name="vehicle interior, such as headliner">600,</part-num-ref>
+ may be disposed between outer ring <part-num-ref name="vehicle interior, such as headliner 600, may be disposed between outer ring">200</part-num-ref>
+ and back ring <part-num-ref name="and back ring">500</part-num-ref>
+ when those two components are connected to one another. The connections/engagements of the above-detailed components in the construction of embodiments of vent assembly <part-num-ref name="construction of embodiments of vent assembly">100</part-num-ref>
+ are described below.    </p>
+    <boundary-data type="header">
+      <confidence value="8">3</confidence>
+    </boundary-data>
+    <boundary-data type="header">22562-257<confidence value="686">/TO</confidence>
+Y2009-093    </boundary-data>
+    <p id="p-21" num="21">
+      <page-break num="4"/>
+[0017]       Embodiments of vent assembly 100 may be partially constructed by connecting fin/actuator sub-assembly <part-num-ref name="may be partially constructed by connecting fin/actuator sub-assembly">400</part-num-ref>
+ to inner ring <part-num-ref name="to inner ring">300.</part-num-ref>
+ In the illustrated embodiments, fin/actuator sub-assembly <part-num-ref name="illustrated embodiments, fin/actuator sub-assembly">400</part-num-ref>
+ and inner ring <part-num-ref name="and inner ring">300</part-num-ref>
+ include corresponding structure to allow these two components to snap together in a locked engagement. Accordingly, when in a locked engagement, fin/actuator sub-assembly <part-num-ref name="locked engagement, fin/actuator sub-assembly">400</part-num-ref>
+ is secured within inner ring <part-num-ref name="is secured within inner ring">300</part-num-ref>
+ and not able to rotate within the inner ring. The connection between fin/actuator sub-assembly <part-num-ref name="connection between fin/actuator sub-assembly">400</part-num-ref>
+ and inner ring <part-num-ref name="and inner ring">300</part-num-ref>
+ may utilize any structure and/or method known in the art. FIGS. 2 and <part-num-ref name="and">3</part-num-ref>
+ illustrate an embodiment of fin/actuator sub-assembly <part-num-ref name="embodiment of fin/actuator sub-assembly">400</part-num-ref>
+ and inner ring <part-num-ref name="and inner ring">300</part-num-ref>
+ in a locked engagement.    </p>
+    <p id="p-22" num="22">[0018]       Once fin/actuator sub-assembly 400 and inner ring <part-num-ref name="and inner ring">300</part-num-ref>
+ are connected in a locked engagement, annular retaining member <part-num-ref name="locked engagement, annular retaining member">700</part-num-ref>
+ may be positioned in a retaining engagement with the fin/actuator sub-assembly and the inner ring. When annular retaining member <part-num-ref name="inner ring. When annular retaining member">700</part-num-ref>
+ is in a retaining engagement with fin/actuator sub-assembly <part-num-ref name="retaining engagement with fin/actuator sub-assembly">400</part-num-ref>
+ and inner ring <part-num-ref name="and inner ring">300,</part-num-ref>
+ a portion of the annular retaining member is disposed through aperture <part-num-ref name="annular retaining member is disposed through aperture">440</part-num-ref>
+ of fin/actuator sub-assembly, and portions of the annular retaining member are in contact with retention surfaces <part-num-ref name="annular retaining member are in contact with retention surfaces">320</part-num-ref>
+ on protrusions <part-num-ref name="on protrusions">310</part-num-ref>
+ of the inner ring. In the illustrated embodiments, annular retaining member <part-num-ref name="illustrated embodiments, annular retaining member">700</part-num-ref>
+ is situated in a retaining engagement with fin/actuator sub- assembly <part-num-ref name="retaining engagement with fin/actuator sub- assembly">400</part-num-ref>
+ and inner ring <part-num-ref name="and inner ring">300</part-num-ref>
+ when a portion of the annular retaining member is put in contact with a first retaining surface (i.e., annular retaining member <part-num-ref name="annular retaining member">700</part-num-ref>
+ is hooked over protrusion 310), a portion of the annular retaining member is disposed through aperture <part-num-ref name="annular retaining member is disposed through aperture">440,</part-num-ref>
+ and a portion of the annular retaining member is put in contact with a second retaining surface (i.e., annular retaining member <part-num-ref name="annular retaining member">700</part-num-ref>
+ is hooked over the other protrusion 310).    </p>
+    <p id="p-23" num="23">[0019]       Embodiments of vent assembly 100 may be further constructed by connecting inner ring <part-num-ref name="may be further constructed by connecting inner ring">300</part-num-ref>
+ to outer ring <part-num-ref name="to outer ring">200.</part-num-ref>
+ In the illustrated embodiments, inner ring <part-num-ref name="illustrated embodiments, inner ring">300</part-num-ref>
+ and outer ring <part-num-ref name="and outer ring">200</part-num-ref>
+ include corresponding structure to allow these components to snap together in a rotating engagement. Accordingly, when in a rotating engagement, inner ring <part-num-ref name="rotating engagement, inner ring">300</part-num-ref>
+ is secured within outer ring <part-num-ref name="is secured within outer ring">200</part-num-ref>
+ and able to rotate in either direction with respect to the outer ring. The connection between inner ring <part-num-ref name="connection between inner ring">300</part-num-ref>
+ and outer ring <part-num-ref name="and outer ring">200</part-num-ref>
+ may utilize any structure and/or method known in the art. FIG. 4 illustrates an embodiment of inner ring <part-num-ref name="embodiment of inner ring">300</part-num-ref>
+ and outer ring <part-num-ref name="and outer ring">200</part-num-ref>
+ in a rotating engagement. When inner ring <part-num-ref name="rotating engagement. When inner ring">300</part-num-ref>
+ and outer ring <part-num-ref name="and outer ring">200</part-num-ref>
+ are snapped together in such a rotating engagement, the combined fin/actuator sub-assembly and inner ring (snapped together in a locked engagement) are secured within the outer ring and able to rotate freely <part-num-ref name="outer ring and able to rotate freely">360</part-num-ref>
+ degrees in either direction with respect to the outer ring. Accordingly, a <boundary-data type="header">
+        <confidence value="8">4</confidence>
+      </boundary-data>
+      <page-break num="5"/>
+      <boundary-data type="header">22562-257<confidence value="686">/TO</confidence>
+Y2009-093      </boundary-data>
+user may grab any part of fin/actuator sub-assembly <part-num-ref name="user may grab any part of fin/actuator sub-assembly">400</part-num-ref>
+ and/or inner ring <part-num-ref name="and/or inner ring">300</part-num-ref>
+ and rotate the combined sub-assembly and inner ring together within outer ring <part-num-ref name="combined sub-assembly and inner ring together within outer ring">200.</part-num-ref>
+    </p>
+    <p id="p-24" num="24">[0020]       The terms "rotate freely" and/or "free rotation" are defined as continued rotation in any direction without an eventual stoppage of the rotation after a number of revolutions in a single direction. In lieu of annular retaining member <part-num-ref name="single direction. In lieu of annular retaining member">700</part-num-ref>
+ connecting fin/actuator sub-assembly <part-num-ref name="connecting fin/actuator sub-assembly">400</part-num-ref>
+ to inner ring <part-num-ref name="to inner ring">300,</part-num-ref>
+ if a tether was utilized to attach the fin/actuator sub-assembly directly to a stationary component of the vent assembly (e.g., the outer ring), the vehicle interior (e.g., the headliner), or the sheet metal behind the interior, the sustained capability of the fin/actuator sub-assembly to rotate freely with respect to the outer ring would be inhibited and/or eliminated. This is because after a number of fin/actuator sub- assembly rotations in any one direction, the tether would become twisted to a degree that would not allow further rotation of the fin/actuator sub-assembly with respect to outer ring <part-num-ref name="fin/actuator sub-assembly with respect to outer ring">200.</part-num-ref>
+ However, embodiments of vent assembly <part-num-ref name="fin/actuator sub-assembly with respect to outer ring 200. However, embodiments of vent assembly">100</part-num-ref>
+ utilize annular retaining member <part-num-ref name="utilize annular retaining member">700</part-num-ref>
+ to connect fin/actuator sub-assembly <part-num-ref name="to connect fin/actuator sub-assembly">400</part-num-ref>
+ to inner ring <part-num-ref name="to inner ring">300,</part-num-ref>
+ and thus, free rotation of the combined fin/actuator sub-assembly and inner ring may continue for any number of revolutions uninhibited. This is because annular retaining member <part-num-ref name="combined fin/actuator sub-assembly and inner ring may continue for any number of revolutions uninhibited. This is because annular retaining member">700</part-num-ref>
+ only connects fin/actuator sub-assembly <part-num-ref name="only connects fin/actuator sub-assembly">400</part-num-ref>
+ a component of vent assembly <part-num-ref name="component of vent assembly">100</part-num-ref>
+ that rotates with the fin/actuator sub-assembly (e.g., inner ring 300).    </p>
+    <p id="p-25" num="25">[0021]       Vent assembly 100 may be further constructed by connecting outer ring <part-num-ref name="may be further constructed by connecting outer ring">200</part-num-ref>
+ to back ring <part-num-ref name="to back ring">500.</part-num-ref>
+ In some embodiments, a portion of a headliner <part-num-ref name="headliner">600</part-num-ref>
+ may be disposed between the connection of outer ring <part-num-ref name="connection of outer ring">200</part-num-ref>
+ and back ring <part-num-ref name="and back ring">500</part-num-ref>
+ to secure the vent assembly on a vehicle interior. Back ring <part-num-ref name="vehicle interior. Back ring">500</part-num-ref>
+ may also be affixed to headliner <part-num-ref name="may also be affixed to headliner">600</part-num-ref>
+ to further secure vent assembly <part-num-ref name="to further secure vent assembly">100</part-num-ref>
+ in place on the vehicle interior. Back ring <part-num-ref name="vehicle interior. Back ring">500</part-num-ref>
+ may be affixed to headliner <part-num-ref name="may be affixed to headliner">600</part-num-ref>
+ through any method known in the art, including, but not limited to, glues, epoxies, rivets and staples. However, back ring <part-num-ref name="art, including, but not limited to, glues, epoxies, rivets and staples. However, back ring">500</part-num-ref>
+ need not be affixed to headliner <part-num-ref name="need not be affixed to headliner">600,</part-num-ref>
+ as the disposition of a portion of the headliner between back ring <part-num-ref name="headliner between back ring">500</part-num-ref>
+ and outer ring <part-num-ref name="and outer ring">200</part-num-ref>
+ may be sufficient to hold vent assembly <part-num-ref name="may be sufficient to hold vent assembly">100</part-num-ref>
+ in place on the vehicle interior. Outer ring <part-num-ref name="vehicle interior. Outer ring">200</part-num-ref>
+ and back ring <part-num-ref name="and back ring">500</part-num-ref>
+ may include corresponding structure to allow the components to connect in a locking engagement.    </p>
+    <p id="p-26" num="26">The connection between outer ring 200 and back ring <part-num-ref name="and back ring">500</part-num-ref>
+ may utilize any structure and/or method known in the art. When outer ring <part-num-ref name="art. When outer ring">200</part-num-ref>
+ and back ring <part-num-ref name="and back ring">500</part-num-ref>
+ are connected in a locking engagement, the outer ring is not able to rotate with respect to the back ring. Due to the disposition of a portion of headliner <part-num-ref name="portion of headliner">600</part-num-ref>
+ (or other stationary portion of the vehicle interior) between outer ring <part-num-ref name="vehicle interior) between outer ring">200</part-num-ref>
+ and back ring <part-num-ref name="and back ring">500,</part-num-ref>
+ the outer ring is also not able to rotate with respect <boundary-data type="header">
+        <confidence value="8">5</confidence>
+      </boundary-data>
+      <page-break num="6"/>
+      <boundary-data type="header">22562-257<confidence value="686">/TO</confidence>
+Y2009-093      </boundary-data>
+to the surrounding vehicle interior. Accordingly, outer ring <part-num-ref name="surrounding vehicle interior. Accordingly, outer ring">200</part-num-ref>
+ of vent assembly <part-num-ref name="of vent assembly">100</part-num-ref>
+ remains locked in place on the vehicle interior due to the placement of a portion of headliner <part-num-ref name="portion of headliner">600</part-num-ref>
+ between back ring <part-num-ref name="between back ring">500</part-num-ref>
+ and the outer ring, but a user may grab any part of fin/actuator sub-assembly <part-num-ref name="user may grab any part of fin/actuator sub-assembly">400</part-num-ref>
+ and/or inner ring <part-num-ref name="and/or inner ring">300</part-num-ref>
+ and rotate the combined sub-assembly and inner ring with respect to the outer ring.    </p>
+    <p id="p-27" num="27">[0022]       During airbag deployment, vent assemblies, or components of vent assemblies, may become detached from the interior of a vehicle. As an example, components of vent assemblies disposed on the headliner of a vehicle may become detached due to the force of deployment of a side-curtain airbag that is located adjacent or under the headliner.</p>
+    <p id="p-28" num="28">When the airbag deploys, it may contact a HVAC duct behind the vent assembly (or directly contact the assembly), compressing the duct and exerting a force on the assembly. With reference to the embodiments of vent assemblies <part-num-ref name="embodiments of vent assemblies">100</part-num-ref>
+ detailed above, the assemblies may be designed so that the force of an airbag deployment breaks the locked engagement of fin/actuator sub-assembly <part-num-ref name="locked engagement of fin/actuator sub-assembly">400</part-num-ref>
+ and inner ring <part-num-ref name="and inner ring">300,</part-num-ref>
+ thus detaching the fin/actuator sub- assembly from the remainder of vent assembly <part-num-ref name="remainder of vent assembly">100.</part-num-ref>
+ Such a design strategy functions to ensure that the entire vent assembly does not detach from the vehicle interior.    </p>
+    <p id="p-29" num="29">[0023]       When the locked engagement between fin/actuator sub-assembly <part-num-ref name="locked engagement between fin/actuator sub-assembly">400</part-num-ref>
+ and inner ring <part-num-ref name="and inner ring">300</part-num-ref>
+ is broken during airbag deployment, annular retaining member <part-num-ref name="is broken during airbag deployment, annular retaining member">700</part-num-ref>
+ that is in retaining engagement with the fin/actuator sub-assembly and the inner ring may retain the fin/actuator sub-assembly to the inner ring. Accordingly, annular retaining member <part-num-ref name="inner ring. Accordingly, annular retaining member">700</part-num-ref>
+ ensures that fin/actuator sub-assembly <part-num-ref name="ensures that fin/actuator sub-assembly">400</part-num-ref>
+ does not completely disconnect from inner ring <part-num-ref name="does not completely disconnect from inner ring">300</part-num-ref>
+ during airbag deployment. Moreover, because inner ring <part-num-ref name="during airbag deployment. Moreover, because inner ring">300</part-num-ref>
+ remains in rotating engagement with outer ring <part-num-ref name="remains in rotating engagement with outer ring">200</part-num-ref>
+ and the outer ring remains in locked engagement with back ring <part-num-ref name="outer ring remains in locked engagement with back ring">500</part-num-ref>
+ and headliner <part-num-ref name="and headliner">600</part-num-ref>
+ during airbag deployment, the inner ring remains secured to the vehicle interior. Therefore, fin/actuator sub-assembly <part-num-ref name="vehicle interior. Therefore, fin/actuator sub-assembly">400,</part-num-ref>
+ which is connected to inner ring <part-num-ref name="vehicle interior. Therefore, fin/actuator sub-assembly 400, which is connected to inner ring">300</part-num-ref>
+ through employment of annular retaining member <part-num-ref name="through employment of annular retaining member">700,</part-num-ref>
+ also remains connected to the vehicle interior.    </p>
+    <p id="p-30" num="30">[0024]       Moreover, in embodiments of vent assembly 100 that utilize a flexible and/or elastic annular retaining member <part-num-ref name="flexible and/or elastic annular retaining member">700,</part-num-ref>
+ the annular retaining member may provide a multi- point shock absorber to assist in reducing the force exerted on inner ring <part-num-ref name="force exerted on inner ring">300</part-num-ref>
+ by detached fin/actuator sub-assembly during airbag deployment. In lieu of annular retaining member <part-num-ref name="by detached fin/actuator sub-assembly during airbag deployment. In lieu of annular retaining member">700</part-num-ref>
+ connecting fin/actuator sub-assembly <part-num-ref name="connecting fin/actuator sub-assembly">400</part-num-ref>
+ to inner ring <part-num-ref name="to inner ring">300,</part-num-ref>
+ if a non-elastic tether was utilized to attach the fin/actuator sub-assembly to the inner ring at a single point, the tether <boundary-data type="header">
+        <confidence value="8">6</confidence>
+      </boundary-data>
+      <page-break num="7"/>
+      <boundary-data type="header">22562-257<confidence value="686">/TO</confidence>
+Y2009-093      </boundary-data>
+may transfer too great of a force from the detached fin/actuator sub-assembly to a single location on the inner ring during airbag deployment, thus breaking the rotating engagement between the inner ring and the outer ring and detaching the inner ring from the vent assembly. However, by utilizing annular retaining member <part-num-ref name="vent assembly. However, by utilizing annular retaining member">700</part-num-ref>
+ that engages a plurality of retention surfaces <part-num-ref name="plurality of retention surfaces">320</part-num-ref>
+ on protrusions <part-num-ref name="on protrusions">310</part-num-ref>
+ of inner ring <part-num-ref name="of inner ring">300,</part-num-ref>
+ the force of detached fin/actuator sub-assembly <part-num-ref name="force of detached fin/actuator sub-assembly">400</part-num-ref>
+ may be distributed to multiple locations on the inner ring, allowing the inner ring to remain in rotating engagement with outer ring <part-num-ref name="inner ring to remain in rotating engagement with outer ring">200.</part-num-ref>
+ Further, the elasticity of an elastic annular retaining member <part-num-ref name="elastic annular retaining member">700</part-num-ref>
+ may further act as a shock absorber to dissipate the force transferred from the detached fin/actuator sub-assembly to the inner ring.    </p>
+    <p id="p-31" num="31">[0025]       While particular embodiments and aspects of the present invention have been illustrated and described herein, various other changes and modifications can be made without departing from the spirit and scope of the invention. Moreover, although various inventive aspects have been described herein, such aspects need not be utilized in combination. It is therefore intended that the appended claims cover all such changes and modifications that are within the scope of this invention.</p>
+    <boundary-data type="header">
+      <confidence value="8">7</confidence>
+    </boundary-data>
+  </description>
+</us-patent-application>
+

applicant/12609706.xml

@@ -0,0 +1,455 @@
+<?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>12609706</doc-number>
+        <date>2009-10-30</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <boundary-data type="header">HP 200903255                                            PATENT</boundary-data>
+    <heading id="h-1">DETERMINING REGIONS OF INFLUENCE OF FLUID MOVING DEVICES</heading>
+    <heading id="h-2">CROSS REFERENCE TO RELATED APPLICATIONS</heading>
+    <p id="p-1" num="1">[0001]    The present application contains similar subject matter and refers to U.S.</p>
+    <p id="p-2" num="2">Patent No. 7,117,129, issued on October 3, 2006 to Cullen E. Bash et al., and entitled "Commissioning of Sensors", and to U.S. Patent No. 7,596,431, issued on September <part-num-ref name="to Cullen E. Bash et al., and entitled &quot;Commissioning of Sensors&quot;, and to U.S. Patent No. 7,596,431, issued on September">29,</part-num-ref>
+ <part-num-ref name="to Cullen E. Bash et al., and entitled &quot;Commissioning of Sensors&quot;, and to U.S. Patent No. 7,596,431, issued on September 29,">2009</part-num-ref>
+ to George Forman et al., and entitled "Method for Assessing Electronic Devices", the disclosures of which are hereby incorporated by reference in their entireties.    </p>
+    <heading id="h-3">BACKGROUND</heading>
+    <p id="p-3" num="3">[0002<confidence value="5">]</confidence>
+    Multiple cooling resources, such as, air conditioning units, are typically deployed and shared among multiple locations that require cooling to dissipate heat generated in infrastructures, such as, data centers. Temperature sensors are also typically positioned throughout the infrastructures, which operate to identify the cooling requirements at the various locations in the infrastructures. Oftentimes, the cooling resources are operated to provide cooling based upon the demand at the various locations in the infrastructures as identified by the temperature sensors. In order to operate the cooling resources efficiently, the "region of influence" of each cooling resource is typically determined. The "region of influence" information identifies which cooling resource to manipulate if the temperature at a particular location changes.    </p>
+    <p id="p-4" num="4">[0003]    The region of influence of each cooling resource differs depending on the locations of the temperature sensors, the configurations of the cooling resources, and the configurations of the paths of the cooling medium supplied bythe cooling resources.</p>
+    <p id="p-5" num="5">The process of discovering the regions of influence of the cooling resources is often called "commissioning" and typically requires varying the actuation level of each cooling resource in turn and measuring its impact at each of the sensor locations. This <boundary-data type="header">
+        <confidence value="5">1</confidence>
+      </boundary-data>
+      <page-break num="2"/>
+      <boundary-data type="header">HP 200903255                                            PATENT</boundary-data>
+commissioning process allows a corresponding sensitivity metric, which indicates the change in temperature value at a particular location as a result of a unit change in the actuation of the cooling resource, to be computed. Although the commissioning process yields accurate determinations of the regions of influence, the commissioning process is typically time-consuming and laborious.    </p>
+    <boundary-data type="header">
+      <confidence value="8">2</confidence>
+    </boundary-data>
+    <boundary-data type="header">HP 200903255                                           PATENT</boundary-data>
+    <heading id="h-4">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
+    <p id="p-6" num="6">
+      <page-break num="3"/>
+[0004]    Features of the present invention will become apparent to those skilled in the art from the following description with reference to the figures, in which:    </p>
+    <p id="p-7" num="7">[0005]    FIG. <confidence value="5">1</confidence>
+ shows a simplified perspective view of a section of an infrastructure <part-num-ref name="infrastructure">100,</part-num-ref>
+ in this instance, a data center, in which a method and analyzer for determining regions of influence of a plurality of fluid moving devices may be implemented, according to an embodiment of the invention;    </p>
+    <p id="p-8" num="8">[0006<confidence value="5">]</confidence>
+    FIG. 2 shows a block diagram of a system for determining regions of influence of a plurality of fluid moving devices in an infrastructure, such as the infrastructure depicted in FIG. 1, according to an embodiment of the invention;    </p>
+    <p id="p-9" num="9">[0007]    FIG. 3 depicts a flow diagram of a method of automatically determining regions of influence of a plurality of fluid moving devices in an infrastructure in an expedient manner, according to an embodiment of the invention;</p>
+    <p id="p-10" num="10">[0008<confidence value="5">]</confidence>
+    FIG. 4 depicts a flow diagram of a method for generating the clusters discussed in the flow diagram depicted in FIG. 3, according to an embodiment of the invention; and [0009]    FIG. 5 illustrates a computer system, which may be employed to perform various functions described herein, according to an embodiment of the invention.    </p>
+    <boundary-data type="header">
+      <confidence value="8">3</confidence>
+    </boundary-data>
+    <boundary-data type="header">
+      <confidence value="88">HP</confidence>
+ 200903255                                           PATENT    </boundary-data>
+    <heading id="h-5">DETAILED DESCRIPTION OF THE INVENTION</heading>
+    <p id="p-11" num="11">
+      <page-break num="4"/>
+[0010<confidence value="5">]</confidence>
+    For simplicity and illustrative purposes, the present invention is described by referring mainly to an exemplary embodiment thereof. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent however, to one of ordinary skill in the art, that the present invention may be practiced without limitation to these specific details. In other instances, well known methods and structures have not been described in detail so as not to unnecessarily obscure the present invention.    </p>
+    <p id="p-12" num="12">[0011]    Disclosed herein are a method and an analyzer for automatically determining regions of influence of a plurality of fluid moving devices in an infrastructure. Also disclosed herein is a computer readable storage medium on which is embedded one or more computer programs storing the disclosed method. As further disclosed herein, the regions of influence are determined through implementation of a cluster analysis on both physical and correlation metrics-based relationships between the fluid moving devices and a plurality of sensors.</p>
+    <p id="p-13" num="13">[0012]    Through implementation of the method, analyzer and computer readable storage medium disclosed herein, the amount of time required to identify the regions of influence of a plurality of fluid moving devices may substantially be reduced as compared with conventional commissioning operations. The amount of time required to identify the regions of influence may substantially be reduced because, as disclosed herein, the regions of influence are identified without requiring the air moving devices be manipulated. In one regard, therefore, the regions of influence may be identified with a minimal amount of disruption to the infrastructure operations.</p>
+    <p id="p-14" num="14">[0013]    With reference first to FIG. 1, there is shown a simplified perspective view of a section of an infrastructure <part-num-ref name="infrastructure">100,</part-num-ref>
+ in this instance, a data center, in which a method and analyzer for determining regions of influence of a plurality of fluid moving devices may be implemented, according to an example. It should be understood that the infrastructure <part-num-ref name="infrastructure">100</part-num-ref>
+ may include additional elements and that some of the elements <boundary-data type="header">
+        <confidence value="8">4</confidence>
+      </boundary-data>
+      <page-break num="5"/>
+      <boundary-data type="header">
+        <confidence value="88">HP</confidence>
+ 200903255                                            PATENT      </boundary-data>
+described herein may be removed and/or modified without departing from a scope of the infrastructure <part-num-ref name="infrastructure">100.</part-num-ref>
+    </p>
+    <p id="p-15" num="15">[0014]    The infrastructure <part-num-ref name="infrastructure">100</part-num-ref>
+ is depicted as having a plurality of racks 102a- <confidence value="5">1</confidence>
+02n, a plurality of fluid moving devices 114a-1<confidence value="5">1</confidence>
+4n, and a plurality of sensors <confidence value="5">1</confidence>
+20a- 120n. As discussed in greater detail herein below, environmental condition information collected by the sensors 120a-120n are used to determine regions of influence in the infrastructure <part-num-ref name="infrastructure">100</part-num-ref>
+ for each of the fluid moving devices 114a-1<confidence value="5">1</confidence>
+4n. More particularly, through implementation of the method and analyzer disclosed herein below, the regions of influence of each of the fluid moving devices 114a-114n are determined without requiring that a relatively lengthy commissioning process be implemented.    </p>
+    <p id="p-16" num="16">[0015]    The racks 102a-102n are positioned on a raised floor <part-num-ref name="raised floor">110</part-num-ref>
+ and house electronic devices <part-num-ref name="and house electronic devices">116</part-num-ref>
+ capable of generating/dissipating heat, for instance, computers, servers, bladed servers, disk drives, displays, etc. As shown in FIG. 1, when the fluid comprises a gas, such as air or a gaseous refrigerant, the fluid is delivered through fluid delivery devices <part-num-ref name="fluid is delivered through fluid delivery devices">118</part-num-ref>
+ in the floor <part-num-ref name="floor">110</part-num-ref>
+ to the racks 102a-102n. In other instances in which the fluid comprises a liquid, such as water, a liquid refrigerant, a multi-state refrigerant, etc., the fluid may be delivered to the racks 102a-102n through a series of pipes (not shown). The fluid moving devices <confidence value="5">1</confidence>
+14a-114n generally operate to supply fluid flow to a space <part-num-ref name="space">112</part-num-ref>
+ beneath the raised floor <part-num-ref name="raised floor">110,</part-num-ref>
+ and in certain instances to cool heated fluid (indicated by the arrows 128). The fluid moving devices 114a-1<confidence value="5">1</confidence>
+4n may comprise widely available, conventional air conditioning (AC) units.    </p>
+    <p id="p-17" num="17">[0016]   In any regard, the cooled fluid contained in the space <part-num-ref name="space">112</part-num-ref>
+ may include cooled fluid supplied by one or more fluid moving devices <confidence value="5">1</confidence>
+14a-114n, and in certain instances, fluid flow recirculated into the space <part-num-ref name="space">112.</part-num-ref>
+ Thus, characteristics of the cooled fluid, such as, temperature, pressure, humidity, flow rate, etc., delivered to various locations in the infrastructure <part-num-ref name="infrastructure">100</part-num-ref>
+ may substantially be affected by the operations of a plurality of the fluid moving devices 114a-1<confidence value="5">1</confidence>
+4n. As such, conditions at various locations in the infrastructure <part-num-ref name="infrastructure">100</part-num-ref>
+ may substantially be affected by the operations of more than one of the fluid moving devices 114a-114n.    </p>
+    <boundary-data type="header">
+      <confidence value="8">5</confidence>
+    </boundary-data>
+    <boundary-data type="header">HP 200903255                                            PATENT</boundary-data>
+    <p id="p-18" num="18">
+      <page-break num="6"/>
+[0017]    The sensors 120a-120n may be networked with an analyzer <part-num-ref name="analyzer">130</part-num-ref>
+ and may be configured to convey detected condition information through any suitable wired or wireless means. As described below, the analyzer <part-num-ref name="analyzer">130</part-num-ref>
+ may employ the condition information received from the sensors 120a-120n to determine the level of influence each of the fluid moving devices 114a-114n has over areas near each of the sensors <confidence value="5">1</confidence>
+20a-120n. The detected conditions may include, for instance, temperature, pressure, fluid flow volume, humidity, etc. Although the analyzer <part-num-ref name="analyzer">130</part-num-ref>
+ is illustrated in FIG. <confidence value="5">1</confidence>
+ as comprising an element separate from the electronic components <part-num-ref name="electronic components">116,</part-num-ref>
+ the analyzer <part-num-ref name="analyzer">130</part-num-ref>
+ may comprise or be integrated with one or more of the electronic components <part-num-ref name="electronic components">116</part-num-ref>
+ without departing from a scope of the data center <part-num-ref name="data center">100</part-num-ref>
+ disclosed herein. In addition, or alternatively, the analyzer <part-num-ref name="analyzer">130</part-num-ref>
+ may comprise software configured to operate on a computing device, for instance, one of the electronic components <part-num-ref name="electronic components">116</part-num-ref>
+ or a separate computing device.    </p>
+    <p id="p-19" num="19">[0018]    Turning now to FIG. 2, there is shown a block diagram <part-num-ref name="block diagram">200</part-num-ref>
+ of a system <part-num-ref name="system">202</part-num-ref>
+ for determining regions of influence of a plurality of fluid moving devices in an infrastructure, such as the infrastructure <part-num-ref name="infrastructure">100</part-num-ref>
+ depicted in FIG. 1, according to an example. It should be understood that the following description of the block diagram <part-num-ref name="block diagram">200</part-num-ref>
+ is but one manner of a variety of different manners in which such a system <part-num-ref name="system">202</part-num-ref>
+ may be configured. In addition, it should be understood that the system <part-num-ref name="system">202</part-num-ref>
+ may include additional components and that some of the components described herein may be removed and/or modified without departing from the scope of the system <part-num-ref name="system">202.</part-num-ref>
+ For instance, the system <part-num-ref name="system">202</part-num-ref>
+ may include any number of sensors, memories, processors, fluid moving devices, etc., as well as other components, which may be implemented in the operations of the system <part-num-ref name="system">202.</part-num-ref>
+    </p>
+    <p id="p-20" num="20">[0019]    As shown, the system <part-num-ref name="system">202</part-num-ref>
+ includes an analyzer <part-num-ref name="analyzer">204,</part-num-ref>
+ which may be equivalent to the analyzer <part-num-ref name="analyzer">130</part-num-ref>
+ depicted in FIG. 1. The analyzer <part-num-ref name="analyzer">204</part-num-ref>
+ is depicted as including an input module <part-num-ref name="input module">206,</part-num-ref>
+ a data collection module <part-num-ref name="data collection module">208,</part-num-ref>
+ a commissioning module <part-num-ref name="commissioning module">210,</part-num-ref>
+ a clustering module <part-num-ref name="clustering module">212,</part-num-ref>
+ a filtering module <part-num-ref name="filtering module">214,</part-num-ref>
+ a region identification module <part-num-ref name="region identification module">216,</part-num-ref>
+ and an output module <part-num-ref name="output module">218.</part-num-ref>
+ Various manners in which the modules 206-218 operate are discussed in detail herein below with respect to the method <part-num-ref name="method">300</part-num-ref>
+ depicted in FIG. 3.    </p>
+    <boundary-data type="header">
+      <confidence value="8">6</confidence>
+    </boundary-data>
+    <boundary-data type="header">HP 200903255                                            PATENT</boundary-data>
+    <p id="p-21" num="21">
+      <page-break num="7"/>
+[0020]    According to an example, the analyzer <part-num-ref name="analyzer">204</part-num-ref>
+ comprises software stored, for instance, in a volatile or non-volatile memory, such as DRAM, EEPROM, MRAM, flash memory, floppy disk, a CD-ROM, a DVD-ROM, or other optical or magnetic media, and the like. In this example, the modules 206-216 comprise software modules stored in the memory, which are executable by a processor <part-num-ref name="processor">230</part-num-ref>
+ of a computing device. According to another example, the analyzer <part-num-ref name="analyzer">204</part-num-ref>
+ comprises a hardware device, such as, a circuit or multiple circuits arranged on a board. In this example, the modules 206-218 comprise circuit components or individual circuits, which may also be controlled by a processor of a computing device. According to a further example, the analyzer <part-num-ref name="analyzer">204</part-num-ref>
+ comprises a combination of hardware and software modules.    </p>
+    <p id="p-22" num="22">[0021]    Generally speaking, the analyzer <part-num-ref name="analyzer">204</part-num-ref>
+ is configured to automatically determine regions of influence of a plurality of fluid moving devices, for instance, the fluid moving devices <confidence value="5">1</confidence>
+14a-114n of the infrastructure <part-num-ref name="infrastructure">100</part-num-ref>
+ depicted in FIG. 1. According to a particular example, the determined regions of influence may be employed in identifying how one or more of the fluid moving devices 114a-1<confidence value="5">1</confidence>
+4n may be manipulated to achieve desired environmental conditions in various locations within the infrastructure.    </p>
+    <p id="p-23" num="23">[0022]    The analyzer <part-num-ref name="analyzer">204</part-num-ref>
+ is configured to evaluate condition information received from the sensors <confidence value="5">1</confidence>
+20a-120n in determining the regions of influence of the plurality of fluid moving devices 114a-114n. In this regard, the analyzer <part-num-ref name="analyzer">204</part-num-ref>
+ may receive the condition information from the sensors <confidence value="5">1</confidence>
+20a-120n over a network <part-num-ref name="network">240</part-num-ref>
+ that operates to couple the various components of the system <part-num-ref name="system">202.</part-num-ref>
+ Although not shown, the processor <part-num-ref name="processor">230</part-num-ref>
+ may be equipped with or have access to software and/or hardware to enable the processor <part-num-ref name="processor">230</part-num-ref>
+ to transmit and receive data over the network <part-num-ref name="network">240.</part-num-ref>
+ The network <part-num-ref name="network">240</part-num-ref>
+ generally represents a wired or wireless structure in the infrastructure for the transmission of data between the various components of the system <part-num-ref name="system">202.</part-num-ref>
+    </p>
+    <p id="p-24" num="24">[0023]    In any regard, the analyzer <part-num-ref name="analyzer">204</part-num-ref>
+ is configured to store the condition information received from the sensors 120a-120n in a data store <part-num-ref name="data store">220,</part-num-ref>
+ which may comprise any reasonably suitable memory upon which the analyzer <part-num-ref name="analyzer">204</part-num-ref>
+ may store data <boundary-data type="header">
+        <confidence value="8">7</confidence>
+      </boundary-data>
+      <page-break num="8"/>
+      <boundary-data type="header">HP 200903255                                           PATENT</boundary-data>
+and from which the analyzer <part-num-ref name="analyzer">204</part-num-ref>
+ may retrieve data. Although the data store <part-num-ref name="data store">220</part-num-ref>
+ has been depicted as forming a separate component from the analyzer <part-num-ref name="analyzer">204,</part-num-ref>
+ it should be understood that the data store <part-num-ref name="data store">220</part-num-ref>
+ may be integrated with the analyzer <part-num-ref name="analyzer">204</part-num-ref>
+ without departing from a scope of the system <part-num-ref name="system">200.</part-num-ref>
+    </p>
+    <p id="p-25" num="25">[0024]    The analyzer <part-num-ref name="analyzer">204</part-num-ref>
+ may also output the determined regions of influence through the output module <part-num-ref name="output module">118.</part-num-ref>
+ Thus, for instance, the determined regions of influence may be outputted a display upon which the outputted information may be displayed, a printer upon which the outputted information may be printed, a connection over which the outputted information may be conveyed to another computing device, a data storage device upon which the outputted information may be stored, etc.    </p>
+    <p id="p-26" num="26">[0025]    According to a particular example where the processor <part-num-ref name="processor">230</part-num-ref>
+ is configured to control operations of the fluid moving devices 114a-1<confidence value="5">1</confidence>
+4n, the processor <part-num-ref name="processor">230</part-num-ref>
+ may receive the determined regions of influence and may transmit instructions over the network <part-num-ref name="network">230</part-num-ref>
+ to the fluid moving devices 114a-1<confidence value="5">1</confidence>
+4n to vary operations of one or more of the fluid moving devices <confidence value="5">1</confidence>
+14a-114n. As shown, the fluid moving devices <confidence value="5">1</confidence>
+14a-114n each includes an actuator A <part-num-ref name="">240</part-num-ref>
+ and an actuator B <part-num-ref name="actuator B">242.</part-num-ref>
+ The actuators <part-num-ref name="actuators">240</part-num-ref>
+ and <part-num-ref name="and">242</part-num-ref>
+ generally comprise devices for controlling different aspects of the fluid flow supplied by the fluid moving devices 114a-114n, which are also actuators.    </p>
+    <p id="p-27" num="27">[0026]    By way of example, the actuators <part-num-ref name="actuators">240</part-num-ref>
+ may comprise fluid flow volume varying devices, such as, variable frequency drives (V<confidence value="5">F</confidence>
+Ds), fans, blowers, etc. In addition, the actuators <part-num-ref name="actuators">242</part-num-ref>
+ may comprise fluid flow temperature varying devices, such as, water-chillers, compressors, valves, etc. The processor <part-num-ref name="processor">230</part-num-ref>
+ may control the actuators <part-num-ref name="actuators">240</part-num-ref>
+ and <part-num-ref name="and">242</part-num-ref>
+ of the fluid moving devices 114a-114n to vary one or more characteristics of the fluid flow detected by the sensors 120a-120n.    </p>
+    <p id="p-28" num="28">[0027]    Various manners in which the modules 204-218 of the analyzer <part-num-ref name="analyzer">204</part-num-ref>
+ may operate are discussed with respect to the methods <part-num-ref name="methods">300</part-num-ref>
+ and <part-num-ref name="and">400</part-num-ref>
+ depicted in FIGS. 3 and <part-num-ref name="and">4.</part-num-ref>
+ FIG. 3, more particularly depicts a flow diagram of a method <part-num-ref name="method">300</part-num-ref>
+ of automatically determining regions of influence of a plurality of fluid moving devices in an infrastructure in an expedient manner, according to an example. FIG. 4, more <boundary-data type="header">
+        <confidence value="5">8</confidence>
+      </boundary-data>
+      <page-break num="9"/>
+      <boundary-data type="header">HP 200903255                                           PATENT</boundary-data>
+particularly depicts a flow diagram of a method <part-num-ref name="method">400</part-num-ref>
+ for generating the clusters discussed in the method <part-num-ref name="method">300,</part-num-ref>
+ according to an example. It should be apparent to those of ordinary skill in the art that the methods discussed below with respect to FIGS. 3 and <part-num-ref name="and">4</part-num-ref>
+ represent generalized illustrations and that other steps may be added or existing steps may be removed, modified or rearranged without departing from the scopes of the methods <part-num-ref name="methods">300</part-num-ref>
+ and <part-num-ref name="and">400.</part-num-ref>
+    </p>
+    <p id="p-29" num="29">[0028]    Although particular reference is made to the analyzer <part-num-ref name="analyzer">204</part-num-ref>
+ depicted in FIG.    </p>
+    <p id="p-30" num="30">2 as performing the steps outlined in the methods <part-num-ref name="methods">300</part-num-ref>
+ and <part-num-ref name="and">400,</part-num-ref>
+ it should be understood that the methods <part-num-ref name="methods">300</part-num-ref>
+ and <part-num-ref name="and">400</part-num-ref>
+ may be performed by a differently configured analyzer without departing from the scopes of the methods <part-num-ref name="methods">300</part-num-ref>
+ and <part-num-ref name="and">400.</part-num-ref>
+    </p>
+    <p id="p-31" num="31">[0029]    At step 302, a commissioning operation is performed on the fluid moving devices 114a-1<confidence value="5">1</confidence>
+4n to discover initial regions of influence of the fluid moving devices 114a-114n, for instance, by the commissioning module <part-num-ref name="commissioning module">210.</part-num-ref>
+ The commissioning process may comprise the commissioning process disclosed in U.S. Patent No.    </p>
+    <p id="p-32" num="32">7,117,129, which has been referenced above. As discussed in that patent, correlation data between sensors and a plurality of actuators are determined based upon conditions detected by the sensors at a plurality of actuator settings.</p>
+    <p id="p-33" num="33">[0030]   In addition, the commissioning operation performed at step <part-num-ref name="commissioning operation performed at step">302</part-num-ref>
+ may be implemented to also identify thermal correlation coefficients (T<confidence value="5">C</confidence>
+Is) between the fluid moving devices 114a-1<confidence value="5">1</confidence>
+4n and the sensors <confidence value="5">1</confidence>
+20a-120n, which are described in detail in U.S. Patent No. 7,596,431, which has also been referenced above. As discussed in that patent, T<confidence value="54">Cl</confidence>
+ is a measure of the relative level of influence a fluid moving device has over a particular area in a room, as identified by the measurements obtained by the sensors placed at various locations in the room. Thus, for instance, the higher the T<confidence value="55">CI</confidence>
+ value at a particular location for a fluid moving device, the greater the influence the fluid moving device has over that location. The following discussion is an excerpt from U.S.    </p>
+    <p id="p-34" num="34">Patent No. 7,596,431.</p>
+    <p id="p-35" num="35">[0031]    Although the T<confidence value="55">CI</confidence>
+ of a fluid moving device may be calculated through any number of suitable correlation algorithms, the following algorithm may be employed to <boundary-data type="header">
+        <confidence value="8">9</confidence>
+      </boundary-data>
+      <page-break num="10"/>
+      <boundary-data type="header">HP 200903255                                            PATENT</boundary-data>
+calculate the T<confidence value="55">CI</confidence>
+ of a fluid moving device and a number of sensor locations (<confidence value="15">I)</confidence>
+ in a room.    </p>
+    <p id="p-36" num="36">
+      <confidence value="5">[</confidence>
+0032]    Equation (1): TC<confidence value="58">I,</confidence>
+  <confidence value="2">N</confidence>
+ <confidence value="6">(</confidence>
+ <confidence value="645">-T)</confidence>
+     </p>
+    <heading id="h-6">
+      <confidence value="7">N</confidence>
+    </heading>
+    <p id="p-37" num="37">[0033]    In Equation (1), T<confidence value="1">y</confidence>
+ is a temperature measurement determined at a first fluid moving device setting and T2 is a temperature measurement determined at a second fluid moving device setting. In addition, N<confidence value="88">is</confidence>
+ the amount <confidence value="88">of</confidence>
+ supply fluid condition change for the fluid moving device between the first temperature measurement and the second temperature measurement.    </p>
+    <p id="p-38" num="38">
+      <confidence value="5">[</confidence>
+0034]    At step 304, a determination that a re-commissioning process is required is made, for instance, by the processor <part-num-ref name="processor">230</part-num-ref>
+ or an operator. For example, the processor <part-num-ref name="processor">230</part-num-ref>
+ or the operator may track the temperatures collected by the sensors 120a-120n and may determine that the temperatures at one or more locations are not changing as expected in response to changes in the fluid delivery conditions to those one or more locations, which may occur when the configuration of components in the infrastructure changes. As another particular example, the processor <part-num-ref name="processor">230</part-num-ref>
+ may employ the T<confidence value="55">CI</confidence>
+ values of the sensors <confidence value="5">1</confidence>
+20a-120n with respect to individual fluid moving devices 114a-1<confidence value="5">1</confidence>
+4n to predict how the conditions at the sensors <confidence value="5">1</confidence>
+20a-120n should be affected by changes in the fluid supply and may determine that a re-commissioning operation is required when an error from the predicted response exceeds a predefined threshold.    </p>
+    <p id="p-39" num="39">[0035]    At step 306, data pertaining to conditions, such as temperature, fluid flow velocity, fluid volume flow rate, etc., sensed by the sensors <confidence value="5">1</confidence>
+20a-120n are collected, for instance, by the data collection module <part-num-ref name="data collection module">208.</part-num-ref>
+ In addition, the locations of the sensors 120a-120n may be identified at step <part-num-ref name="sensors 120a-120n may be identified at step">306</part-num-ref>
+ from, for instance, a database containing information on the locations of the sensors <confidence value="5">1</confidence>
+20a-<confidence value="5">1</confidence>
+20n, the network addresses of the sensors 120a-<confidence value="5">1</confidence>
+20n, etc.    </p>
+    <p id="p-40" num="40">[0036]    At step 308, data pertaining to fluid supplied by each of the fluid moving devices 114a-<confidence value="66">11</confidence>
+4n is also collected, for instance, by the data collection module <part-num-ref name="data collection module">208.</part-num-ref>
+    </p>
+    <boundary-data type="header">
+      <confidence value="88">10</confidence>
+    </boundary-data>
+    <boundary-data type="header">HP 200903255                                            PATENT</boundary-data>
+    <p id="p-41" num="41">
+      <page-break num="11"/>
+The data pertaining to the fluid supplied by each of the fluid moving devices <confidence value="66">11</confidence>
+4a-1<confidence value="588">14n</confidence>
+ may relate to, for instance, the temperatures, the volume flow rates, etc., of the fluid supplied by each of the fluid moving devices <confidence value="5">1</confidence>
+14a-114n. These conditions may be detected by sensors integrated with or separate from the fluid moving devices <confidence value="5">1</confidence>
+14a- <confidence value="8">1</confidence>
+14n.    </p>
+    <p id="p-42" num="42">[0037]    The data sensed by the sensors 120a-120n and pertaining to the fluid supplied by the fluid moving devices 114a-114n may be continuously collected and stored, for instance, in the data store <part-num-ref name="data store">220.</part-num-ref>
+ For example, the data may be collected for a predetermined length of time, for instance, a day, a couple of days, etc. According to a particular example, the data is collected from a point when a relationship change between actuation of one or more of the fluid moving devices 114a-1<confidence value="8">1</confidence>
+4n and sensed data is expected to have occurred.    </p>
+    <p id="p-43" num="43">[0038]    At step 310, a plurality of clusters, each containing a fluid moving device 114a-114n and one or more of the plurality of sensors 120a-120n, is generated, for instance, by the clustering module <part-num-ref name="clustering module">212.</part-num-ref>
+ The clusters may be defined as associating the sensors 120a-120n with the fluid moving devices 114a-1<confidence value="5">1</confidence>
+4n based upon the locations of the sensors <confidence value="5">1</confidence>
+20a-120n with respect to the fluid moving devices 114a-1<confidence value="5">1</confidence>
+4n and the average temperatures detected by the sensors <confidence value="5">1</confidence>
+20a-120n over a period of time and the average temperatures of the fluid supplied by the fluid moving devices 114a-1<confidence value="5">1</confidence>
+4n over the same period of time. According to an example, the clustering module <part-num-ref name="clustering module">212</part-num-ref>
+ is configured to implement a conventional clustering algorithm, such as, hierarchical clustering, K-means clustering, K-medoid clustering, fuzzy c-means clustering, spectral clustering, etc., to generate the clusters, in which, the locations where the fluid supply conditions are detected are the centers of the clusters. In addition, the clustering module <part-num-ref name="clustering module">212</part-num-ref>
+ is configured to identify clusters around each of the locations where the fluid supply conditions are detected in terms of both locations of the sensors <confidence value="5">1</confidence>
+20a-120n and the conditions sensed by the sensors 120a-120n. A more detailed discussion of how the clusters are generated at step <part-num-ref name="clusters are generated at step">310</part-num-ref>
+ is provided below with respect to the method <part-num-ref name="method">400</part-num-ref>
+ depicted in FIG. 4.    </p>
+    <boundary-data type="header">
+      <confidence value="88">11</confidence>
+    </boundary-data>
+    <boundary-data type="header">
+      <confidence value="88">HP</confidence>
+ 200903255                                            PATENT    </boundary-data>
+    <p id="p-44" num="44">
+      <page-break num="12"/>
+[0039]    With particular reference to FIG. 4, which may be implemented by the clustering module <part-num-ref name="clustering module">212,</part-num-ref>
+ and at step <part-num-ref name="clustering module 212, and at step">402,</part-num-ref>
+ the locations in the infrastructure where the data pertaining to the fluid supplied by each of the plurality of fluid moving devices are collected are identified. These locations may be identified manually by an operator or automatically from the network addresses from which the data is collected. In addition, the identified locations may be defined in three dimensional space with x, y, and z-axis coordinates.    </p>
+    <p id="p-45" num="45">[0040]    At step 404, the identified locations of where the fluid supply conditions are collected are used to seed the clusters, and more particularly, are assigned as the centers of the clusters. Thus, a cluster may be generated for each of the locations where the fluid supply conditions are collected.</p>
+    <p id="p-46" num="46">[0041]    At step 406, the physical locations of the sensors 120a-120n are identified. The physical locations of the sensors 120a-120n may be defined in three dimensional space using x, y, and z-axis coordinates. The physical locations of the sensors <confidence value="5">1</confidence>
+20a-120n may also be determined manually by an operator or automatically based upon network address information.    </p>
+    <p id="p-47" num="47">[0042]    At step 408, a correlation metric-based value is computed for each sensor 120a-120n with respect to each fluid supply condition. Generally speaking, the correlation metric-based values are values that signify how related the conditions detected by the sensors 120a-120n are to the fluid supply conditions of the fluid supply devices <confidence value="5">1</confidence>
+14a-114n. In other words, the correlation metric-based values provide information on the dependence of the conditions detected by the sensors 120a-120n to the fluid supply conditions of the fluid supply devices <confidence value="5">1</confidence>
+14a-114n over a time series.    </p>
+    <p id="p-48" num="48">Thus, for instance, the correlation metric-based values may signify how related the temperatures at the sensors <confidence value="5">1</confidence>
+20a-120n are to the temperatures of the fluid supplied by the fluid supply devices 114a-1<confidence value="5">1</confidence>
+4n over a particular time series.    </p>
+    <p id="p-49" num="49">[0043]    Conventional correlation metrics may be employed to compute the correlation metric-based values. Examples of suitable correlation metrics include, <boundary-data type="header">
+        <confidence value="88">12</confidence>
+      </boundary-data>
+      <page-break num="13"/>
+      <boundary-data type="header">HP 200903255                                            PATENT</boundary-data>
+Pearson's correlation coefficient, Spearman's and Kendall's rank correlation coefficient, correlation ratio, mutual information from information theory, etc. By way of particular example, Pearson's correlation coefficient and Spearman's rank correlation coefficient ranks correlations between two quantities between <part-num-ref name="correlation metric-based values. Examples of suitable correlation metrics include, Pearson's correlation coefficient, Spearman's and Kendall's rank correlation coefficient, correlation ratio, mutual information from information theory, etc. By way of particular example, Pearson's correlation coefficient and Spearman's rank correlation coefficient ranks correlations between two quantities between">0</part-num-ref>
+ and <part-num-ref name="and">1,</part-num-ref>
+ in which <part-num-ref name="and 1, in which">0</part-num-ref>
+ indicates a complete lack of dependence and <part-num-ref name="complete lack of dependence and">
+        <confidence value="5">1</confidence>
+      </part-num-ref>
+ indicates complete dependence.    </p>
+    <p id="p-50" num="50">[0044]    At step 410, physical and correlation metric-based relationships are identified between the sensors <confidence value="5">1</confidence>
+20a-120n and the locations where the data pertaining to the fluid supplied by each of the fluid moving devices are collected. Thus, for instance, the physical distances in three dimensions between each of the sensors <confidence value="5">1</confidence>
+20a- <confidence value="5">1</confidence>
+20n and each of the locations where data pertaining to the fluid supplied by each of the fluid moving devices are collected may be identified, for instance, to determine which of the sensors <confidence value="5">1</confidence>
+20a-120n are in the closest proximity to which of the locations where the supply fluid conditions are collected.    </p>
+    <p id="p-51" num="51">[0045]    In addition to the physical distances, the correlation metric-based values of each of the sensors <confidence value="5">1</confidence>
+20a-120n with respect to each of the locations where the supply fluid conditions are collected are identified. Thus, for instance, a sensor 120a having a closer dependence to a particular fluid supply device 114a may be identified as being closer to that particular fluid supply device <confidence value="5">1</confidence>
+14a than to a fluid supply device 114b to which the sensor 120a has a lesser dependence.    </p>
+    <p id="p-52" num="52">[0046]    At step 410, therefore, the distances between different data points are defined in four dimensions, three dimensions for the locations and one dimension for the correlation metric-based relationships. The distances between the different data points may be determined as Euclidean distances, absolute distances, sum of the absolute distances in each of the dimensions, etc.</p>
+    <p id="p-53" num="53">[0047]    According to an embodiment, the values for each of the dimensions that define the physical locations and the correlation metric-based values are normalized with respect to the values in those particular dimensions. Thus, for instance, the distances and correlation metric-based values may be normalized between values of <part-num-ref name="distances and correlation metric-based values may be normalized between values of">0</part-num-ref>
+ and <part-num-ref name="and">
+        <confidence value="5">1</confidence>
+      </part-num-ref>
+ such that both of these values may be considered together. In addition, the <boundary-data type="header">
+        <confidence value="88">13</confidence>
+      </boundary-data>
+      <page-break num="14"/>
+      <boundary-data type="header">HP 200903255                                            PATENT</boundary-data>
+distance measures may be weighed differently from the correlation metric-based values in considering how to cluster the sensors 120a-120n with respect to the fluid moving devices <confidence value="5">1</confidence>
+14a-114n.    </p>
+    <p id="p-54" num="54">[0048]    At step 412, the clusters are generated from the identified physical and correlation metric-based relationships.</p>
+    <p id="p-55" num="55">[0049]    With reference back to FIG. 3, at step 312, the distances between the sensors 120a-120n and respective locations where the supply fluid conditions are collected are analyzed to identify the regions of influence of each of the fluid moving devices 114a-1<confidence value="5">1</confidence>
+4n, for instance, by the region identification module <part-num-ref name="region identification module">216.</part-num-ref>
+ The regions of influence may be identified based upon the results of the clustering generation performed at step <part-num-ref name="clustering generation performed at step">310.</part-num-ref>
+ More particularly, the region identification module <part-num-ref name="region identification module">216</part-num-ref>
+ may analyze the cluster arrangements to determine which of the sensors 120a-120n are assignable to which of the fluid moving devices 114a-114n based upon the cluster arrangements and may determine the regions of influence from the assignments. By way of particular example, the sensors 120a-120n may be assigned to the respective fluid moving devices <confidence value="5">1</confidence>
+14a-114n to which they are most closely clustered.    </p>
+    <p id="p-56" num="56">[0050]    In addition, at step 314, a filtering operation may be implemented to refine the regions of influence identified at step <part-num-ref name="regions of influence identified at step">312,</part-num-ref>
+ for instance, by the filtering module <part-num-ref name="filtering module">214.</part-num-ref>
+    </p>
+    <p id="p-57" num="57">More particularly, the correlation metric-based values for the sensors <confidence value="5">1</confidence>
+20a-120n with respect to each of the fluid supply devices <confidence value="5">1</confidence>
+14a-114n may be analyzed to determine whether the dependencies of one or more of the sensors 120a-120n with respect to the fluid supply devices 114a-1<confidence value="8">1</confidence>
+4n are sufficiently low to warrant removal of the one or more sensors 120a-120n from the clusters of one or more of the fluid supply devices <confidence value="8">1</confidence>
+14a-114n. In other words, for instance, the filtering module <part-num-ref name="filtering module">214</part-num-ref>
+ may determine that the sensors 120a-120n that have correlation metric-based values that fall below a predefined threshold with respect to a particular fluid supply device's cluster are to be removed from that fluid supply device's cluster.    </p>
+    <p id="p-58" num="58">[0051]    The predefined threshold may be based upon a user's experiences or based upon the correlation metric-based values of other relationships. By way of <boundary-data type="header">
+        <confidence value="88">14</confidence>
+      </boundary-data>
+      <page-break num="15"/>
+      <boundary-data type="header">
+        <confidence value="88">HP</confidence>
+ 200903255                                            PATENT      </boundary-data>
+particular example, the sensors <confidence value="5">1</confidence>
+20a-120n having correlation metric-based values that fall within the lowest 10% or 20% of the correlation metric-based values may be considered as failing to be sufficiently dependent on a particular fluid supply device and may thus be filtered out from the clusters. Thus, the filtering operation performed at step <part-num-ref name="filtering operation performed at step">314</part-num-ref>
+ may cause the regions of influence identified at step <part-num-ref name="regions of influence identified at step">312</part-num-ref>
+ to be modified.    </p>
+    <p id="p-59" num="59">[0052]    At step 316, the identified regions of influence of each of the fluid supply devices 114a-114n are outputted, for instance, through the output module <part-num-ref name="output module">218.</part-num-ref>
+ As discussed above, the identified regions of influence may be outputted to a display, printer, or other computing device for analysis by an operator. In addition, or alternatively, the output module <part-num-ref name="output module">218</part-num-ref>
+ may output the identified regions of influence to a controller of the fluid moving devices 114a-1<confidence value="5">1</confidence>
+4n, which may implement this information in determining how to modify the fluid supply device 114a-114n operations as conditions change in the infrastructure.    </p>
+    <p id="p-60" num="60">[0053]    Some or all of the operations set forth in the methods <part-num-ref name="methods">300</part-num-ref>
+ and <part-num-ref name="and">400</part-num-ref>
+ may be contained as utilities, programs, or subprograms, in any desired computer accessible medium. In addition, the methods <part-num-ref name="methods">300</part-num-ref>
+ and <part-num-ref name="and">400</part-num-ref>
+ may be embodied by computer programs, which can exist in a variety of forms both active and inactive. For example, they may exist as software program(s) comprised of program instructions in source code, object code, executable code or other formats. Any of the above may be embodied on a computer readable storage medium.    </p>
+    <p id="p-61" num="61">[0054]    Exemplary computer readable storage media include conventional computer system RAM, ROM, EPROM, EEPROM, and magnetic or optical disks or tapes. Concrete examples of the foregoing include distribution of the programs on a CD ROM or via Internet download. It is therefore to be understood that any electronic device capable of executing the above-described functions may perform those functions enumerated above.</p>
+    <p id="p-62" num="62">[0055]    FIG. 5 illustrates a block diagram of a computing apparatus <part-num-ref name="computing apparatus">500</part-num-ref>
+ configured to implement or execute the methods <part-num-ref name="methods">300</part-num-ref>
+ and <part-num-ref name="and">400</part-num-ref>
+ depicted in FIGS. 3 and <part-num-ref name="and">4,</part-num-ref>
+ according to an example. In this respect, the computing apparatus <part-num-ref name="computing apparatus">500</part-num-ref>
+ may be used <boundary-data type="header">
+        <confidence value="88">15</confidence>
+      </boundary-data>
+      <page-break num="16"/>
+      <boundary-data type="header">HP 200903255                                          PATENT</boundary-data>
+as a platform for executing one or more of the functions described hereinabove with respect to the analyzer <part-num-ref name="analyzer">204.</part-num-ref>
+    </p>
+    <p id="p-63" num="63">
+      <confidence value="5">[</confidence>
+0056]    The computing apparatus <part-num-ref name="computing apparatus">500</part-num-ref>
+ includes a processor <part-num-ref name="processor">502</part-num-ref>
+ that may implement or execute some or all of the steps described in the methods <part-num-ref name="methods">300</part-num-ref>
+ and <part-num-ref name="and">400.</part-num-ref>
+    </p>
+    <p id="p-64" num="64">Commands and data from the processor <part-num-ref name="processor">502</part-num-ref>
+ are communicated over a communication bus <part-num-ref name="communication bus">504.</part-num-ref>
+ The computing apparatus <part-num-ref name="computing apparatus">500</part-num-ref>
+ also includes a main memory <part-num-ref name="main memory">506,</part-num-ref>
+ such as a random access memory (RAM), where the program code for the processor <part-num-ref name="processor">502,</part-num-ref>
+ may <confidence value="88">be</confidence>
+ executed during runtime, and a secondary memory <part-num-ref name="secondary memory">508.</part-num-ref>
+ The secondary memory <part-num-ref name="secondary memory">508</part-num-ref>
+ includes, for example, one or more hard disk drives <part-num-ref name="includes, for example, one or more hard disk drives">510</part-num-ref>
+ and/or a removable storage drive <part-num-ref name="removable storage drive">512,</part-num-ref>
+ representing a floppy diskette drive, a magnetic tape drive, a compact disk drive, etc., where a copy of the program code for the methods <part-num-ref name="methods">300</part-num-ref>
+ and <part-num-ref name="and">400</part-num-ref>
+ may be stored.    </p>
+    <p id="p-65" num="65">[0057<confidence value="5">]</confidence>
+ The removable storage drive <part-num-ref name="removable storage drive">510</part-num-ref>
+ reads from and/or writes to a removable storage unit <part-num-ref name="removable storage unit">514</part-num-ref>
+ in <confidence value="6">a</confidence>
+ well-known manner. User input and output devices may include a keyboard <part-num-ref name="keyboard">516,</part-num-ref>
+ a mouse <part-num-ref name="mouse">518,</part-num-ref>
+ and a display <part-num-ref name="display">520.</part-num-ref>
+ A display adaptor <part-num-ref name="display adaptor">522</part-num-ref>
+ may interface with the communication bus <part-num-ref name="communication bus">504</part-num-ref>
+ and the display <part-num-ref name="display">520</part-num-ref>
+ and may receive display data from the processor <part-num-ref name="processor">502</part-num-ref>
+ and convert the display data into display commands for the display <part-num-ref name="display">520.</part-num-ref>
+ In addition, the processor(s) <part-num-ref name="processor(s)">502</part-num-ref>
+ may communicate over a network, for instance, the Internet, LAN, etc., through a network adaptor <part-num-ref name="network adaptor">524.</part-num-ref>
+    </p>
+    <p id="p-66" num="66">[0058]     It will be apparent to one of ordinary skill in the art that other known electronic components may be added or substituted in the computing apparatus <part-num-ref name="computing apparatus">500.</part-num-ref>
+ It should also be apparent that one or more of the components depicted in FIG. 5 may be optional (for instance, user input devices, secondary memory, etc.).    </p>
+    <p id="p-67" num="67">[0059]     What has been described and illustrated herein is a preferred embodiment of the invention along with some of its variations. The terms, descriptions and figures used herein are set forth by way of illustration only and are not meant as limitations. Those skilled in the art will recognize that many variations are possible within the spirit and scope of the invention, which is intended to be defined by the <boundary-data type="header">
+        <confidence value="88">16</confidence>
+      </boundary-data>
+      <page-break num="17"/>
+      <boundary-data type="header">HP 200903255                                              PATENT</boundary-data>
+following claims -- and their equivalents -- in which all terms are meant in their broadest reasonable sense unless otherwise indicated.    </p>
+    <boundary-data type="header">
+      <confidence value="88">17</confidence>
+    </boundary-data>
+  </description>
+</us-patent-application>
+

applicant/12684442.xml

@@ -0,0 +1,2 @@
+<?xml version="1.0" encoding="utf-8"?><pat:SpecificationDocument xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:pat="urn:us:gov:doc:uspto:patent" xmlns:ent="urn:us:gov:doc:uspto:enterprise" xmlns="urn:us:gov:doc:uspto:patent" xmlns:tbl="http://www.oasis-open.org/tables/exchange/1.0" xmlns:com="http://www.wipo.int/standards/XMLSchema/Common/1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XML_SCHEMAS/V1_3/SpecificationDocument_1_0.xsd" pat:instanceFileName="12684442.09-12-2016.IT0DOYPXRXEAPX0.SPEC.XML" pat:id="IT0DOYPXRXEAPX0">
+<pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001"><pat:ApplicationHeaderDetails><pat:ApplicationNumber>12684442</pat:ApplicationNumber></pat:ApplicationHeaderDetails><pat:PageTotalQuantity>3</pat:PageTotalQuantity><pat:ParagraphTotalQuantity>18</pat:ParagraphTotalQuantity></pat:DocumentHeaderDetails><pat:MailRoomDate>2016-09-12</pat:MailRoomDate><pat:DocumentCreateDateText>2016-09-14</pat:DocumentCreateDateText><pat:Specification><?PageStart number='1'?><pat:P pat:pNumber="1" pat:id="p-1"><pat:BoundaryData><pat:HeaderText>App. Serial No. 12/684,442</pat:HeaderText></pat:BoundaryData></pat:P><pat:P pat:pNumber="2" pat:id="p-2"><pat:BoundaryData><pat:HeaderText>Docket No. GTTE.<pat:OCRConfidenceData pat:levelNumber="66">00</pat:OCRConfidenceData>4PA</pat:HeaderText></pat:BoundaryData></pat:P><pat:P pat:pNumber="3" pat:id="p-3"><pat:BoundaryData><pat:HeaderText>Amendment After Allowance Under 37 C.F.R. <pat:OCRConfidenceData pat:levelNumber="5">§</pat:OCRConfidenceData> 1.312\</pat:HeaderText></pat:BoundaryData><pat:U>In the Specification:</pat:U></pat:P><pat:P pat:pNumber="4" pat:id="p-4">At<pat:PartName pat:idref="PN-00001"> page </pat:PartName><pat:PartNumber pat:id="PN-00001">3</pat:PartNumber>, paragraph [008],<pat:PartName pat:idref="PN-00002"> line </pat:PartName><pat:PartNumber pat:id="PN-00002">13</pat:PartNumber> please amend the paragraph as follows:</pat:P><pat:P pat:pNumber="5" pat:id="p-5">[008] An equivalent 2.4 GHz radio located at the intersection along with associated electronics receives the broadcasted vehicle information. Approaches to the intersection are mapped using either collected GPS readings from a vehicle traversing the approaches or using location information taken from a map database. The vehicle location and direction are used to determine on which of the mapped approaches the vehicle is approaching toward the intersection and the relative proximity to it. The speed and location of the vehicle is used to determine the estimated time of arrival (ETA) at the intersection and the travel distance from the intersection. ETA and travel distances are associated with each intersection approach to determine when a detected vehicle is within range of the intersection and therefore a preemption candidate. Preemption candidates with valid security codes are reviewed with other detected vehicles to determine the highest priority vehicle. Vehicles of equivalent priority are selected <pat:DeletedText>in </pat:DeletedText>on a first come, first served manner. A preemption request is issued to the controller for the approach direction with the highest priority vehicle travelling on it.</pat:P><pat:P pat:pNumber="6" pat:id="p-6">At<pat:PartName pat:idref="PN-00003"> page </pat:PartName><pat:PartNumber pat:id="PN-00003">10</pat:PartNumber>, paragraph [028],<pat:PartName pat:idref="PN-00004"> line </pat:PartName><pat:PartNumber pat:id="PN-00004">3</pat:PartNumber> please amend the paragraph as follows:</pat:P><pat:P pat:pNumber="7" pat:id="p-7">[028] In an example embodiment the<pat:PartName pat:idref="PN-00005"> photodetector circuitry </pat:PartName><pat:PartNumber pat:id="PN-00005">116</pat:PartNumber> may be similar to that used in the OPTICOM emitter-based system, and the<pat:PartName pat:idref="PN-00006"> radio receiver </pat:PartName><pat:PartNumber pat:id="PN-00006">118</pat:PartNumber> and<pat:PartName pat:idref="PN-00007"> antenna </pat:PartName><pat:PartNumber pat:id="PN-00007">122</pat:PartNumber> may be <pat:DeletedText>and </pat:DeletedText>the OPTICOM GPS priority control system.</pat:P><pat:P pat:pNumber="8" pat:id="p-8">At<pat:PartName pat:idref="PN-00008"> page </pat:PartName><pat:PartNumber pat:id="PN-00008">12</pat:PartNumber>-13, paragraph [038],<pat:PartName pat:idref="PN-00009"> line </pat:PartName><pat:PartNumber pat:id="PN-00009">13</pat:PartNumber> please amend the paragraph as follows:</pat:P><pat:P pat:pNumber="9" pat:id="p-9"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8">2</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData></pat:P><?PageStart number='2'?><pat:P pat:pNumber="10" pat:id="p-10"><pat:BoundaryData><pat:HeaderText>App. Serial No. 12/684,442</pat:HeaderText></pat:BoundaryData></pat:P><pat:P pat:pNumber="11" pat:id="p-11"><pat:BoundaryData><pat:HeaderText>Docket No. GTTE.<pat:OCRConfidenceData pat:levelNumber="66">00</pat:OCRConfidenceData>4PA</pat:HeaderText></pat:BoundaryData></pat:P><pat:P pat:pNumber="12" pat:id="p-12"><pat:BoundaryData><pat:HeaderText>Amendment After Allowance Under 37 C.F.R. <pat:OCRConfidenceData pat:levelNumber="5">§</pat:OCRConfidenceData> 1.312\</pat:HeaderText></pat:BoundaryData>[038] The process for selecting a preemption candidate considers a variety of factors in selecting a preemption candidate. Those factors include the relative priorities of the candidates, the relative times that the preemption requests were submitted, and the approaches of the preemption candidates relative to an in-progress preemption. The relative priorities are determined from a class code transmitted in the preemption request signal, and the process recognizes a superset of the class code ranges used in the different systems. For example, the OPTICOM light emitter-based system uses a<pat:PartName pat:idref="PN-00010"> class code range of </pat:PartName><pat:PartNumber pat:id="PN-00010">0</pat:PartNumber><pat:PartName pat:idref="PN-00011"> through </pat:PartName><pat:PartNumber pat:id="PN-00011">9</pat:PartNumber>, while the OPTICOM GPS system uses a<pat:PartName pat:idref="PN-00012"> class code range of </pat:PartName><pat:PartNumber pat:id="PN-00012">1</pat:PartNumber><pat:PartName pat:idref="PN-00013"> through </pat:PartName><pat:PartNumber pat:id="PN-00013">15</pat:PartNumber>. Additionally, the OPTICOM GPS system and compatible network based systems use an agency code to differentiate between agencies or jurisdictions. The<pat:PartName pat:idref="PN-00014"> agency code ranges in value from </pat:PartName><pat:PartNumber pat:id="PN-00014">1</pat:PartNumber><pat:PartName pat:idref="PN-00015"> through </pat:PartName><pat:PartNumber pat:id="PN-00015">254</pat:PartNumber>. The process recognizes a<pat:PartName pat:idref="PN-00016"> class code range of </pat:PartName><pat:PartNumber pat:id="PN-00016">0</pat:PartNumber><pat:PartName pat:idref="PN-00017"> through </pat:PartName><pat:PartNumber pat:id="PN-00017">15</pat:PartNumber>. Preemption requests with no agency code are assumed to have an<pat:PartName pat:idref="PN-00018"> agency code of </pat:PartName><pat:PartNumber pat:id="PN-00018">0</pat:PartNumber>. The combined set of class codes spans all agency codes so that vehicles using light-based emitters can compete with the same classes of vehicles from other agencies using GPS equipment.</pat:P><pat:P pat:pNumber="13" pat:id="p-13">At<pat:PartName pat:idref="PN-00019"> page </pat:PartName><pat:PartNumber pat:id="PN-00019">14</pat:PartNumber>, paragraph [043],<pat:PartName pat:idref="PN-00020"> line </pat:PartName><pat:PartNumber pat:id="PN-00020">9</pat:PartNumber> please amend the paragraph as follows<pat:OCRConfidenceData pat:levelNumber="5">:</pat:OCRConfidenceData></pat:P><pat:P pat:pNumber="14" pat:id="p-14">[043] If the set of preemption candidates is not empty, the process is directed to<pat:PartName pat:idref="PN-00021"> decision step </pat:PartName><pat:PartNumber pat:id="PN-00021">414</pat:PartNumber> in FIG.<pat:PartName pat:idref="PN-00022"> 4-</pat:PartName><pat:PartNumber pat:id="PN-00022">2</pat:PartNumber>.<pat:PartName pat:idref="PN-00023"> Decision step </pat:PartName><pat:PartNumber pat:id="PN-00023">414</pat:PartNumber> checks whether or not there is a preemption request in progress. If so,<pat:PartName pat:idref="PN-00024"> decision step </pat:PartName><pat:PartNumber pat:id="PN-00024">416</pat:PartNumber> checks whether or not the in- progress preemption request is also in the preemption candidate set. Note that a preemption candidate is removed from the set when it is terminated or the intersection preemption arrangement is no longer receiving a preemption request signal for that preemption candidate. If the in-progress preemption request is in the preemption candidate set, the process proceeds to check whether or not the status of the<pat:PartName pat:idref="PN-00025"> preemption request is holding<pat:OCRConfidenceData pat:levelNumber="6"> </pat:OCRConfidenceData></pat:PartName><pat:PartNumber pat:id="PN-00025"><pat:OCRConfidenceData pat:levelNumber="866">418</pat:OCRConfidenceData></pat:PartNumber><pat:U>.</pat:U> If the status is not holding,<pat:PartName pat:idref="PN-00026"> step </pat:PartName><pat:PartNumber pat:id="PN-00026">420</pat:PartNumber> changes the status to holding and starts the hold timer. Otherwise,<pat:PartName pat:idref="PN-00027"> decision step </pat:PartName><pat:PartNumber pat:id="PN-00027">422</pat:PartNumber> checks whether or not the hold timer has expired. While the hold timer has not expired, the<pat:PartName pat:idref="PN-00028"> process continues at decision step </pat:PartName><pat:PartNumber pat:id="PN-00028">424</pat:PartNumber> to check if there are any preemption candidates having a higher priority than the in-progress preemption request. In an example</pat:P><pat:P pat:pNumber="15" pat:id="p-15"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8">3</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData></pat:P><?PageStart number='3'?><pat:P pat:pNumber="16" pat:id="p-16"><pat:BoundaryData><pat:HeaderText>App. Serial No. 12/684,442</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Docket No. GTTE.<pat:OCRConfidenceData pat:levelNumber="66">00</pat:OCRConfidenceData>4PA</pat:HeaderText></pat:BoundaryData></pat:P><pat:P pat:pNumber="17" pat:id="p-17"><pat:BoundaryData><pat:HeaderText>Amendment After Allowance Under 37 C.F.R. <pat:OCRConfidenceData pat:levelNumber="5">§</pat:OCRConfidenceData> 1.312\</pat:HeaderText></pat:BoundaryData>embodiment, the class codes of the preemption candidates are used to determine priorities. For example, a lesser class code value may be used to indicate a higher priority and a greater class code value may indicate a lower priority. If there is a higher priority candidate, the<pat:PartName pat:idref="PN-00029"> in-progress preemption request is terminated at step </pat:PartName><pat:PartNumber pat:id="PN-00029">426</pat:PartNumber>, and the<pat:PartName pat:idref="PN-00030"> process continues at step </pat:PartName><pat:PartNumber pat:id="PN-00030">440</pat:PartNumber> in FIG.<pat:PartName pat:idref="PN-00031"> 4-</pat:PartName><pat:PartNumber pat:id="PN-00031">3</pat:PartNumber></pat:P><pat:P pat:pNumber="18" pat:id="p-18"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8">4</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData></pat:P></pat:Specification></pat:SpecificationDocument>

applicant/12940756.xml

@@ -0,0 +1,225 @@
+<?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>12940756</doc-number>
+        <date>2011-06-01</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <boundary-data type="header">Application No. 12/940,756</boundary-data>
+    <boundary-data type="header">Attorney Docket No. 0941/2480PUS1</boundary-data>
+    <boundary-data type="header">Prelimina<confidence value="8">r</confidence>
+y Amendment    </boundary-data>
+    <boundary-data type="header">Page 2 of 10</boundary-data>
+    <heading id="h-1">AMENDMENTS TO THE SPECIFICATION</heading>
+    <p id="p-1" num="1">Please amend the title as it appears on the first page of the specification and in the U.S.</p>
+    <p id="p-2" num="2">Patent and Trademark Office's records, as follows:</p>
+    <heading id="h-2">--COLOR FILTER OF BAC<confidence value="868554">K-SIDE</confidence>
+ ILLUMINATION IMAGE SENSOR AND    </heading>
+    <heading id="h-3">METHOD FOR FABRICATING THE SAME--</heading>
+    <p id="p-3" num="3">Please amend paragraph [0004] as follows:</p>
+    <p id="p-4" num="4">--[0004] A color filter of an illumination image sensor and method for fabricating the same are provided. An exemplary embodiment of a color filter of an illumination image sensor comprises a light shield portion constructed by <confidence value="566412">a-plur</confidence>
+ality<confidence value="65">-e</confidence>
+f grid photoresist patterns, wherein the light shield portion covers <confidence value="2">a</confidence>
+ <confidence value="6816">baek</confidence>
+ side s<confidence value="88888">urfac</confidence>
+e <confidence value="66">of</confidence>
+ <confidence value="666">the</confidence>
+ <confidence value="1">°</confidence>
+ <confidence value="6652">lice</confidence>
+ <confidence value="56666">wafer</confidence>
+ <confidence value="6">i</confidence>
+ a periphery region of an illumination image sensor chip.-- Please amend paragraph [0005] as follows:    </p>
+    <p id="p-5" num="5">--[0005] A method for fabricating a color filter of an illumination image sensor comprises forming a<confidence value="85125">plura</confidence>
+lity<confidence value="65">-e</confidence>
+f grid photoresist patterns covering <confidence value="2">a</confidence>
+ <confidence value="6826">back</confidence>
+ side s<confidence value="88888">urfac</confidence>
+e <confidence value="66">of</confidence>
+ <confidence value="666">the</confidence>
+ <confidence value="2222222">silieon</confidence>
+ <confidence value="425">waf</confidence>
+ in a periphery region of an illumination image sensor chip.-- Please amend paragraph [0016] as follows:    </p>
+    <p id="p-6" num="6">--[0016] FIG. 2 is a top view showing one exemplary embodiment of a color filter <part-num-ref name="color filter">202</part-num-ref>
+ of an illumination image sensor of the invention. As shown in FIG. 2, one exemplary embodiment of the color filter <part-num-ref name="color filter">202</part-num-ref>
+ may comprise a light shield portion <part-num-ref name="light shield portion">204</part-num-ref>
+ and a sensing portion <part-num-ref name="sensing portion">206.</part-num-ref>
+ The light shield portion <part-num-ref name="light shield portion">204</part-num-ref>
+ of the color filter <part-num-ref name="color filter">202</part-num-ref>
+ covers <confidence value="2">a</confidence>
+ back side <confidence value="6256">safe</confidence>
+ <confidence value="66">of</confidence>
+ <confidence value="666">the</confidence>
+ <confidence value="222222">silion</confidence>
+ wafer <confidence value="6">i</confidence>
+ <confidence value="6">a</confidence>
+ periphery region of an illumination image sensor chip. Also, the sensing portion <part-num-ref name="sensing portion">206</part-num-ref>
+ of the color filter <part-num-ref name="color filter">202</part-num-ref>
+ covers a <confidence value="6626">back</confidence>
+ <confidence value="25266">ieeof</confidence>
+ <confidence value="666">the</confidence>
+ <confidence value="88">si</confidence>
+l<confidence value="8788">icon</confidence>
+ wain     a sensing region of an illumination image sensor chip. In one embodiment, the periphery region is a region where periphery circuits such as logic circuits are disposed therein, and the sensing region is a region where photo diodes are disposed therein to sense light. As shown in FIG. 2, the sensing portion <part-num-ref name="sensing portion">206</part-num-ref>
+ of the color filter <part-num-ref name="color filter">202</part-num-ref>
+ is usually composed of a plurality of grid photoresist patterns 202a including a plurality of red grid photoresist patterns 202R1, green grid photoresist patterns 202G1 and blue grid <page-break num="2"/>
+      <boundary-data type="header">Application No. 12/940,756</boundary-data>
+      <boundary-data type="header">Attorney Docket No. 0941/2480PUS<confidence value="4">1</confidence>
+      </boundary-data>
+      <boundary-data type="header">Preliminary Amendment</boundary-data>
+      <boundary-data type="header">Page 3 of 10</boundary-data>
+photoresist patterns 202<confidence value="5">B</confidence>
+1 arranged as an array according to design, which facilitates the underlying photodiodes to receive filtered light. As shown in FIG. 2, in one embodiment, the light shield portion <part-num-ref name="light shield portion">204</part-num-ref>
+ of the color filter <part-num-ref name="color filter">202</part-num-ref>
+ may be composed of a plurality of grid photoresist patterns 202b similar to the photoresist patterns 202a. The amount of grid photoresist patterns 202b is not limited herein but according to design. In one embodiment, the amount of grid photoresist patterns may be larger than <part-num-ref name="amount of grid photoresist patterns may be larger than">1.</part-num-ref>
+ For example, the grid photoresist patterns 202b may comprise a plurality of photoresist patterns such as red grid photoresist patterns 202R2, green grid photoresist patterns 202G2 and blue grid photoresist patterns 202<confidence value="5">B</confidence>
+2 arranged in an array. In one embodiment, materials of the grid g<confidence value="55">ri</confidence>
+ -photoresist patterns 202b are the same as those of the sensing portion <part-num-ref name="sensing portion">206</part-num-ref>
+ of the color filter <part-num-ref name="color filter">202.</part-num-ref>
+ Additionally, size of the grid photoresist patterns 202R2, 202G2 and 202<confidence value="5">B</confidence>
+2 in the periphery region may be larger, smaller or the same as the grid photoresist patterns 202R1, 202G1 and 202<confidence value="5">B</confidence>
+1 in the sensing region of an illumination image sensor chip. For example, the grid photoresist patterns 202R2, 202G2 and 202<confidence value="5">B</confidence>
+2 may have a size which is larger than 0.4<confidence value="2">p</confidence>
+m. Therefore, the thermal stress of the color filter caused by material mismatch between the sensing portion and the light shield portion during the color filter fabricating process can be reduced.-- Please amend paragraph [0019] as follows:    </p>
+    <p id="p-7" num="7">--[0019] Next, please refer to FIG. 3c, wherein a second photolithography process may be performed to form at least one blue grid photoresist pattern 202<confidence value="5">B</confidence>
+1 in the sensing region <part-num-ref name="sensing region">306,</part-num-ref>
+ covering the silicon wafer <part-num-ref name="silicon wafer">210.</part-num-ref>
+ Also, the second photolithography process may be performed to<confidence value="5">.</confidence>
+    </p>
+    <p id="p-8" num="8">form at least one blue grid photoresist patterns 202<confidence value="5">B</confidence>
+2 in the periphery region <part-num-ref name="periphery region">304,</part-num-ref>
+ covering the metal layer <part-num-ref name="metal layer">214</part-num-ref>
+ on the silicon wafer <part-num-ref name="silicon wafer">210.</part-num-ref>
+ Similar to the red grid photoresist patterns 202R1 and 202R2 as shown in FIG. [[3a]] 3b, the blue grid photoresist patterns 202<confidence value="5">B</confidence>
+1 and 202<confidence value="5">B</confidence>
+2 may have the same or different shapes and sizes. As shown in FIG. 3c, each of the blue grid photoresist patterns 202<confidence value="5">B</confidence>
+1 covers one of the photo diodes 212.-- Please amend paragraph [0020] as follows:    </p>
+    <p id="p-9" num="9">--[0020] Next, please refer to FIG. 3d, wherein a third photolithography process may be performed to form at least one green photoresist pixel 202G1 in the sensing region <part-num-ref name="sensing region">306,</part-num-ref>
+ covering <page-break num="3"/>
+      <boundary-data type="header">Application No. 12/940,756</boundary-data>
+      <boundary-data type="header">Attorney Docket No. 0941/2480PU<confidence value="54">S1</confidence>
+      </boundary-data>
+      <boundary-data type="header">Preliminary Amendment</boundary-data>
+      <boundary-data type="header">Page 4 of 10</boundary-data>
+the silicon wafer <part-num-ref name="silicon wafer">210.</part-num-ref>
+ Also, the third photolithography process may be performed to form at least one green grid photoresist patterns 202G2 in the periphery region <part-num-ref name="periphery region">304,</part-num-ref>
+ covering the metal layer <part-num-ref name="metal layer">214</part-num-ref>
+ on the silicon wafer <part-num-ref name="silicon wafer">210.</part-num-ref>
+ Similar to the red grid photoresist patterns 202R<confidence value="4">1</confidence>
+ and 202R2 and the blue grid photoresist patterns 202<confidence value="5">B</confidence>
+1 and 202<confidence value="5">B</confidence>
+2 as shown in FIGS. 3a and 3b, the green grid photoresist patterns 202G1 and 202G2 may have the same or different shapes and sizes. As shown in FIG. 3d, each of the green grid photoresist patterns 202G1 covers one of the photo diodes <part-num-ref name="photo diodes">212.</part-num-ref>
+ Additionally, in one embodiment as shown in FIG. 3d, the red grid photoresist patterns 202R1, 202R2, the green grid photoresist patterns 202G1, 202G2 and the blue grid photoresist patterns 202<confidence value="5">B</confidence>
+1, 202<confidence value="5">B</confidence>
+2 are formed in the same level. Further, in one embodiment as shown in FIG. 3d, the red, green and blue grid photoresist patterns 202R1, 202<confidence value="5">B</confidence>
+1 and 202G1 in combination form grid photoresist patterns 202a of a sensing portion <part-num-ref name="sensing portion">206</part-num-ref>
+ of a color filter <part-num-ref name="color filter">202.</part-num-ref>
+    </p>
+    <p id="p-10" num="10">Also, the red, green and blue grid photoresist patterns 202R2, 202<confidence value="5">B</confidence>
+2 and 202G2 in combination form grid photoresist patterns 202b of a light shield portion <part-num-ref name="light shield portion">204</part-num-ref>
+ of a color filter <part-num-ref name="color filter">202.</part-num-ref>
+ In one embodiment, materials of the grid photoresist pattern in the light shield portion <part-num-ref name="light shield portion">204</part-num-ref>
+ are the same as those of the grid photoresist pattern in the sensing portion <part-num-ref name="sensing portion">206</part-num-ref>
+ of the color filter covering a sensing region of the <confidence value="222222">silicn</confidence>
+ wafer <confidence value="66">of</confidence>
+ <confidence value="666">the</confidence>
+ <confidence value="6616">baek</confidence>
+ side illumination image sensor chip. Moreover, any two adjacent grid photoresist patterns of the red, green and blue grid photoresist patterns 202R2, 202<confidence value="5">B</confidence>
+2 and 202G2 in the light shield portion of the color filter <part-num-ref name="color filter">202</part-num-ref>
+ may be connected to each other.-- Please amend paragraph [0023] as follows:    </p>
+    <p id="p-11" num="11">--[0023] Note that those skilled in the art should know that one exemplary embodiment of a color filter <part-num-ref name="color filter">202</part-num-ref>
+ uses the same material for the light shield portion <part-num-ref name="light shield portion">204</part-num-ref>
+ (covering the periphery region of the baek<confidence value="6865">-sid</confidence>
+e illumination image sensor) and the sensing portion <part-num-ref name="sensing portion">206</part-num-ref>
+ (covering the photo diodes of the baek<confidence value="66666">-side</confidence>
+ illumination image sensor). Also, the light shield portion of the color filter <part-num-ref name="color filter">202</part-num-ref>
+ may be constructed by a grid photoresist pattern serving as a stress release structure. Therefore, the thermal stress of the color filter caused by material mismatch between the sensing portion and the light shield portion during the color filter fabricating process can be reduced. Additionally, some test items, for example, a dark current, a dark current ring or a blue <page-break num="4"/>
+      <boundary-data type="header">Application No. 12/940,756</boundary-data>
+      <boundary-data type="header">Attorney Docket No. 0941/2480PUS<confidence value="7">1</confidence>
+      </boundary-data>
+      <boundary-data type="header">Preliminary Amendment</boundary-data>
+      <boundary-data type="header">Page 5 of 10</boundary-data>
+channel tail up, may be further used to analyze the performances of an illumination image sensor with an exemplary embodiment of a color filter of the invention.-<confidence value="5">-</confidence>
+ Please amend paragraph [0024] as follows:    </p>
+    <p id="p-12" num="12">
+      <confidence value="5">-</confidence>
+-[0024] FIGS. 5a-<confidence value="5">5</confidence>
+d illustrate a conventional color filter and various exemplary embodiments of a color filter of an illumination image sensor of the invention for testing.    </p>
+    <p id="p-13" num="13">Specifically, FIG. <confidence value="5">5</confidence>
+a shows a conventional color filter 502a having a sensing portion <part-num-ref name="sensing portion">106</part-num-ref>
+ constructed by <confidence value="22222222222222">red/green/blue</confidence>
+ grid photoresist patterns [[102R<confidence value="48848825">i/G1/B1]</confidence>
+] 102R/G/B and a light shield portion 504a constructed by a layer 102M of Cr or black resin. The sensing portions <part-num-ref name="sensing portions">206</part-num-ref>
+ of color filters 502b-502<confidence value="5">d</confidence>
+ as shown in FIGS. 5b-<confidence value="5">5</confidence>
+d are the same as the sensing portion <part-num-ref name="sensing portion">106</part-num-ref>
+ as shown in FIG. 5a, wherein the sensing portions <part-num-ref name="sensing portions">206</part-num-ref>
+ is constructed by a grid photoresist pattern 202a having a plurality of red/green/blue grid photoresist patterns [[202R2/G2<confidence value="5">/</confidence>
+B2]] 202R<confidence value="4861885">1/Gl/B1</confidence>
+ arranged in an array. FIG. <confidence value="5">5</confidence>
+b shows an exemplary embodiment of the color filter 502b, wherein a light shield portion 504b of the color filter 502b is constructed by grid photoresist patterns <part-num-ref name="color filter 502b is constructed by grid photoresist patterns">
+        <confidence value="588">502</confidence>
+      </part-num-ref>
+ similar to that in the sensing portions <part-num-ref name="sensing portions">206,</part-num-ref>
+ with the exception, that the grid photoresist patterns <part-num-ref name="grid photoresist patterns">502</part-num-ref>
+ in the light shield portion 504b are constructed by red/green/blue grid photoresist patterns 502R2/G2/B2 with sizes which are twice as large as those of the red/green/blue grid photoresist patterns [[202R2/G2/B2]] 202R<confidence value="488154">I/G/BI</confidence>
+ in the sensing portion <part-num-ref name="sensing portion">206.</part-num-ref>
+ FIG. <confidence value="5">5</confidence>
+c shows another exemplary embodiment of the color filter 502c, wherein a light shield portion 504c of the color filter 502c is constructed by grid photoresist patterns [[502]] <part-num-ref name="color filter 502c is constructed by grid photoresist patterns [[502]]">5<confidence value="8">0</confidence>
+4      </part-num-ref>
+ similar to that in the sensing portions <part-num-ref name="sensing portions">206,</part-num-ref>
+ with the exception, that the grid photoresist pattern <part-num-ref name="grid photoresist pattern">5<confidence value="8">0</confidence>
+4      </part-num-ref>
+ in the light shield portion 504c has red/green/blue grid photoresist patterns 504R2/G2/B2 with sizes which are about <part-num-ref name="light shield portion 504c has red/green/blue grid photoresist patterns 504R2/G2/B2 with sizes which are about">20</part-num-ref>
+ percent smaller than that of the red/green/blue grid photoresist patterns [[202R2/G<confidence value="66">2/</confidence>
+B2]] 202R<confidence value="4554661">i/GI/B,</confidence>
+ in the sensing portion <part-num-ref name="sensing portion">206.</part-num-ref>
+ FIG. <confidence value="5">5</confidence>
+d shows an exemplary embodiment of the color filter 502d, wherein a light shield portion 504d of the color filter 502d is constructed by a plurality of grid photoresist patterns [[202a]] 202b similarly to that in the sensing portions <part-num-ref name="sensing portions">206,</part-num-ref>
+ with the exception, that the grid photoresist patterns 202b in the light shield portions 504d are constructed by red/green/blue grid photoresist patterns 202R2/G2<confidence value="5">/</confidence>
+B2 with sizes which are the same as that of the red/green/blue grid photoresist patterns 202R<confidence value="4885685">1/G1/B1</confidence>
+ in the sensing portion <part-num-ref name="sensing portion">206.</part-num-ref>
+    The conventional color filter 502a as shown in FIG. <confidence value="5">5</confidence>
+a and various exemplary <page-break num="5"/>
+      <boundary-data type="header">Application No. 12/940,756</boundary-data>
+      <boundary-data type="header">Attorney Docket No. 0941/2480PUS<confidence value="5">1</confidence>
+      </boundary-data>
+      <boundary-data type="header">Preliminary Amendment</boundary-data>
+      <boundary-data type="header">Page 6 of 10</boundary-data>
+embodiments of color filters 502b-502d as shown in FIGS. <confidence value="5885">5b-5</confidence>
+d may be respectively disposed on back sides of illumination image sensors and, therefore, the ba<confidence value="6666656">ek-side</confidence>
+ illumination image sensors may serve as test samples to further analyze the performances of an illumination image sensor.-<confidence value="5">-</confidence>
+ Please amend paragraph [0027] as follows:    </p>
+    <p id="p-14" num="14">
+      <confidence value="5">-</confidence>
+-[0027] Data dots                                602ac<confidence value="2">.</confidence>
+ 602bc<confidence value="5">,</confidence>
+ 602cc and 602d<confidence value="4">c</confidence>
+ shown in FIG. 6c respectively show the testing result of the dark current in the light shield portion (in region 508a/b/c/d) (dark current <part-num-ref name="light shield portion (in region 508a/b/c/d) (dark current">3)</part-num-ref>
+ of the color filters 502b-502d. As shown in FIG.    </p>
+    <p id="p-15" num="15">6c, the color filters 502b-502d show better dark current <part-num-ref name="color filters 502b-502d show better dark current">3</part-num-ref>
+ testing results (Data dots 602bc, 602cc and 602d<confidence value="4">c</confidence>
+) than the conventional color filter 502a (Data dots 602ac). The color filter 502c (Data dots 602cc) shows the smallest dark current <part-num-ref name="smallest dark current">3</part-num-ref>
+ testing result for the color filters 502b-502d (Data dots 602bc, 602cc and 602d<confidence value="5">c</confidence>
+).-<confidence value="5">-</confidence>
+ Please amend paragraph [0029] as follows:    </p>
+    <p id="p-16" num="16">
+      <confidence value="5">-</confidence>
+-[0029] Table 1 shows dark current testing results comparison measured at different wafer level temperature humidity storage stress (T<confidence value="5">H</confidence>
+S) conditions for the conventional color filter 502a and the color filters 502b-502d. Condition T<confidence value="5">O</confidence>
+ means that the samples were tested before performing wafer level T<confidence value="5">H</confidence>
+S dark current testing. Condition 24hrs means that the samples were tested after performing 24hrs wafer level THS dark current testing. It is observed that the dark current values (dark current 1<confidence value="2">~</confidence>
+3) at the condition 24hrs is larger than the condition TO.    </p>
+    <p id="p-17" num="17">Additionally, the dark current <part-num-ref name="dark current">3</part-num-ref>
+ shows a larger variation than the dark current <part-num-ref name="dark current">1</part-num-ref>
+ and <part-num-ref name="and">2.</part-num-ref>
+ Further, the ba<confidence value="586">ek-</confidence>
+side illumination image sensor with the color filter 502c shows better dark current testing result.-<confidence value="5">-</confidence>
+     </p>
+  </description>
+</us-patent-application>
+

applicant/12978755.xml

@@ -0,0 +1,390 @@
+<?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>12978755</doc-number>
+        <date>2010-12-27</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <boundary-data type="header">0201-0311 (P18017-US)</boundary-data>
+    <heading id="h-1">PORTABLE TERMINAL</heading>
+    <heading id="h-2">PRIORITY</heading>
+    <p id="p-1" num="1">[0001<confidence value="5">]</confidence>
+       This application claims the benefit under <part-num-ref name="benefit under">35</part-num-ref>
+ U.S.C. <confidence value="5">§</confidence>
+119(a) of a Korean patent application filed in the Korean Intellectual Property Office on February <part-num-ref name="Korean Intellectual Property Office on February">11,</part-num-ref>
+ <part-num-ref name="Korean Intellectual Property Office on February 11,">2010,</part-num-ref>
+ and assigned Serial No. 10-2010-0012620, the entire disclosure of which is hereby incorporated by reference.    </p>
+    <heading id="h-3">BACKGROUND OF THE INVENTION</heading>
+    <p id="p-2" num="2">1. Field of the Invention:</p>
+    <p id="p-3" num="3">[0002<confidence value="5">]</confidence>
+       The present invention relates to a portable terminal. More particularly, the present invention relates to a coupling structure of cover members constituting a housing of a portable terminal.    </p>
+    <p id="p-4" num="4">2. Description of the Related Art:</p>
+    <p id="p-5" num="5">[0003<confidence value="5">]</confidence>
+       A portable terminal refers to a device carried by a user, which allows using various functions including telecommunication, schedule management, playback of multimedia files, gaming, an electronic dictionary, and the like, and a wireless telecommunication terminal may be an exemplary device thereof. Recently, it has been possible to embody a service provided in a real-time basis, such as a wireless Internet, transmission of video files, broadcasting of digital multimedia, and the like, or a communication of bulk information files using a wireless telecommunication terminal.    </p>
+    <p id="p-6" num="6">[0004<confidence value="5">]</confidence>
+       With the development of these technologies, a user can sufficiently use a variety of functions of the wireless telecommunication terminal or services provided by the same with just one unit of the wireless telecommunication terminal. In other words, besides the voicemail or the multimedia service provided from wireless telecommunication service providers, in the area where a wireless Internet service is available, the user can access the Internet through his/her wireless telecommunication terminal without connecting to the wireless telecommunication service network. Such a telecommunication function allows the user to download whatever contents he/she wants to have through the internet at low cost.    </p>
+    <p id="p-7" num="7">[0005<confidence value="5">]</confidence>
+       Meanwhile, such wireless telecommunication terminals come in different forms where they are either made of one piece of a housing or a pair of housings pivotably or slidably coupled to each other. The respective housings have constructions in which a front <boundary-data type="header">
+        <confidence value="8">-</confidence>
+ <confidence value="8">1</confidence>
+ <confidence value="8">-</confidence>
+      </boundary-data>
+      <page-break num="2"/>
+      <boundary-data type="header">0201-0311 (P18017-US)</boundary-data>
+cover and a rear cover are opposingly joined together so as to install circuit devices therein with ease. Typically, the front cover and the rear cover are coupled with each other using a fastening member, such as a screw. Here, in order to prevent the joining portions of the edges from swelling, clamping structures like a plurality of hooks are disposed along the edges of the front and the rear covers.    </p>
+    <p id="p-8" num="8">[0006<confidence value="5">]</confidence>
+       These clamping structures for the front and rear covers are durably provided without using the screws as to stably maintain the clamping state against impacts caused in a case of dropping the wireless telecommunication terminal on an object, or the like. However, when the front cover and the rear cover need to be separated for repair, such clamping structures become troublesome. In addition, the appearance of the terminal may be damaged in the case of using a tool to separate the clamping structures. Moreover, when an excessive force to separate the front and rear covers is applied during repair, the clamping structures, such as a hook, and the like can be damaged. In addition, it should be noted that after the front and rear covers are joined and secured to each other with the screws, separate finishing works are required to hide the screws, which makes the assembly work burdensome and causes difficulties in polishing the appearance of the terminal.    </p>
+    <p id="p-9" num="9">[0007<confidence value="5">]</confidence>
+       Therefore, a need exists for a portable terminal capable of stably maintaining a clamping state of a front cover and a rear cover, having a structure in which the front and rear covers can be easily separated.    </p>
+    <heading id="h-4">SUMMARY OF THE INVENTION</heading>
+    <p id="p-10" num="10">[0008<confidence value="5">]</confidence>
+       An aspect of the present invention is to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below.    </p>
+    <p id="p-11" num="11">Accordingly, an aspect of the present invention is to provide a portable terminal capable of stably maintaining a clamping state of a front cover and a rear cover, having a structure in which the front and rear covers can be easily separated.</p>
+    <p id="p-12" num="12">[0009<confidence value="5">]</confidence>
+       Another aspect of the present invention is to provide a portable terminal having a structure that can be easily assembled by joining the front and rear covers constituting a housing by means of a case member made from an extrusion process.    </p>
+    <p id="p-13" num="13">[0010<confidence value="5">]</confidence>
+       Still another aspect of the present invention is to provide a portable terminal having a structure in which the front and rear covers can be durably assembled by joining the front and rear covers constituting a housing by means of a case member made from an extrusion process.    </p>
+    <boundary-data type="header">
+      <confidence value="888">-2-</confidence>
+    </boundary-data>
+    <boundary-data type="header">0201-0311 (P18017-US)</boundary-data>
+    <p id="p-14" num="14">
+      <page-break num="3"/>
+[0011<confidence value="5">]</confidence>
+       In accordance with an aspect of the present invention, a portable terminal is provided. The portable terminal includes a housing having a front cover, and a rear cover opposingly coupled with the front cover, a guide rail formed on the opposite lateral surfaces of the front cover and extending in a longitudinal direction of the front cover, a guide groove formed between the guide rail and the lateral surface of the front cover and open to a forward direction of the front cover, and a case member enclosing at least the opposite lateral surfaces and the rear surface of the housing, wherein the case member includes a rail groove to receive the guide rail and a guide rib to be engaged with the guide groove, and wherein the front cover is pressed in a predefined direction to closely contact the rear cover.    </p>
+    <p id="p-15" num="15">[0012<confidence value="5">]</confidence>
+       The portable terminal may include a display window disposed at a front surface of a front cover, a clamping groove formed at an upper or lower side of the display window, and a clamping protrusion formed at the case member to be engaged with the clamping groove, wherein the case member further includes a band member for enclosing the upper or lower side of the display window, and wherein the clamping protrusion is formed at the inner surface of the band member.    </p>
+    <p id="p-16" num="16">[0013<confidence value="5">]</confidence>
+       The clamping groove and the clamping protrusion may be formed in a <confidence value="68">T-</confidence>
+ shaped cross-section.    </p>
+    <p id="p-17" num="17">[0014<confidence value="5">]</confidence>
+       The rail grooves may be recessed at the inner wall of the case member facing each other at the opposite sides of the housing. The terminal may further be provided with grooves which are formed at the inner wall of the rail groove disposed at the front and rear sides of the housing and at least partially enclosed by the guide rib. A portion of the guide rail may be engaged with a groove positioned at the front side of the housing among the grooves.    </p>
+    <p id="p-18" num="18">[0015<confidence value="5">]</confidence>
+       In addition, the terminal may further include a key hole formed on at least one lateral surface of the case member, and a key member received in the key hole to be projected or retreated from the lateral surface of the case member.    </p>
+    <p id="p-19" num="19">[0016<confidence value="5">]</confidence>
+       In the terminal as constructed hereinabove, it is desirable that the case member further includes a stepped surface formed at one side of the rail groove and designed to support the rear cover from the rearward direction of the housing being in close contact with the front cover.    </p>
+    <p id="p-20" num="20">[0017<confidence value="5">]</confidence>
+       Further, the case member may be manufactured from an extrusion process and be slidably coupled from the upper side to the lower side of the housing.    </p>
+    <p id="p-21" num="21">[0018<confidence value="5">]</confidence>
+       Therefore, it should be appreciated that the portable terminal in accordance with exemplary embodiments of the present invention can securely join the front and rear <boundary-data type="header">
+        <confidence value="888">-3-</confidence>
+      </boundary-data>
+      <page-break num="4"/>
+      <boundary-data type="header">0201-0311 (P18017-US)</boundary-data>
+covers by means of the case member without using a fastening member, such as a separate screw, a hook, or a clamping structure. Since the case member can be joined or separated in a slide manner, it is advantageous in that the front and rear covers can be assembled or dissembled with ease. Besides, when the case member is made with a metallic material through an extrusion process, the case member can constitute the corner portion of the terminal housing, which makes it possible to minimize the damage of the front and rear covers when impacts caused in a case of dropping the wireless telecommunication terminal on an object, or the like, is applied thereto. Moreover, when a key is disposed on the lateral surface of the terminal housing, it is possible to install the key member without using a double-sided tape, an ultrasonic fusion-deposited protrusion, or the like, thereby leading to an easy assembly thereof.    </p>
+    <p id="p-22" num="22">[0019<confidence value="5">]</confidence>
+       Other aspects, advantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention.    </p>
+    <heading id="h-5">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
+    <p id="p-23" num="23">[0020<confidence value="5">]</confidence>
+       The above and other aspects, features, and advantages of certain exemplary embodiments of the present invention will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:    </p>
+    <p id="p-24" num="24">[0021<confidence value="5">]</confidence>
+       FIG. <confidence value="5">1</confidence>
+ illustrates an exploded view of a portable terminal according to an exemplary embodiment of the present invention;    </p>
+    <p id="p-25" num="25">[0022<confidence value="5">]</confidence>
+       FIG. 2 illustrates an assembly of a portable terminal according to an exemplary embodiment of the present invention;    </p>
+    <p id="p-26" num="26">[0023<confidence value="5">]</confidence>
+       FIG. 3 illustrates an assembled portable terminal according to an exemplary embodiment of the present invention;    </p>
+    <p id="p-27" num="27">[0024<confidence value="5">]</confidence>
+       FIG. 4 illustrates a partially enlarged view of a case member of a portable terminal according to an exemplary embodiment of the present invention;    </p>
+    <p id="p-28" num="28">[0025<confidence value="5">]</confidence>
+       FIG. 5 illustrates a cross-sectional view of a portable terminal according to an exemplary embodiment of the present invention;    </p>
+    <p id="p-29" num="29">[0026<confidence value="5">]</confidence>
+       FIG. 6 illustrates a key member of a portable terminal according to an exemplary embodiment of the present invention; and [0027<confidence value="5">]</confidence>
+       FIG. 7 illustrates a coupling of a case member with a front cover of a portable terminal according to an exemplary embodiment of the present invention.    </p>
+    <boundary-data type="header">
+      <confidence value="888">-4-</confidence>
+    </boundary-data>
+    <boundary-data type="header">0201-0311 (P18017-US)</boundary-data>
+    <p id="p-30" num="30">
+      <page-break num="5"/>
+[0028<confidence value="5">]</confidence>
+       Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures.    </p>
+    <heading id="h-6">DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS</heading>
+    <p id="p-31" num="31">[0029<confidence value="5">]</confidence>
+       The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.    </p>
+    <p id="p-32" num="32">[0030<confidence value="5">]</confidence>
+       The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the invention. Accordingly, it should be apparent to those skilled in the art that the following description of exemplary embodiments of the present invention is provided for illustration purpose only and not for the purpose of limiting the invention as defined by the appended claims and their equivalents.    </p>
+    <p id="p-33" num="33">[0031<confidence value="5">]</confidence>
+       It is to be understood that the singular forms <confidence value="6666">"a,"</confidence>
+ "an,<confidence value="5">"</confidence>
+ and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to <confidence value="5">"</confidence>
+a component surface<confidence value="5">"</confidence>
+ includes reference to one or more of such surfaces.    </p>
+    <p id="p-34" num="34">[0032<confidence value="5">]</confidence>
+       By the term   "substantially" it is meant that the recited characteristic, parameter, or value need not be achieved exactly, but that deviations or variations, including for example, tolerances, measurement error, measurement accuracy limitations and other factors known to those of skill in the art, may occur in amounts that do not preclude the effect the characteristic was intended to provide.    </p>
+    <p id="p-35" num="35">[0033<confidence value="5">]</confidence>
+       FIG<confidence value="58">s.</confidence>
+ <confidence value="5">1</confidence>
+ through <part-num-ref name="through">7,</part-num-ref>
+ discussed below, and the various exemplary embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way that would limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged communications system. The terms used to describe various embodiments are exemplary. It should be understood that these are provided to merely aid the understanding of the description, and that their use and definitions in no <boundary-data type="header">
+        <confidence value="888">-5-</confidence>
+      </boundary-data>
+      <page-break num="6"/>
+      <boundary-data type="header">0201-0311 (P18017-US)</boundary-data>
+way limit the scope of the invention. Terms first, second, and the like are used to differentiate between objects having the same terminology and are in no way intended to represent a chronological order, unless where explicitly state otherwise. A set is defined as a non-empty set including at least one element.    </p>
+    <p id="p-36" num="36">[0034<confidence value="5">]</confidence>
+       FIG. 1 illustrates an exploded view of a portable terminal according to an exemplary embodiment of the present invention, FIG. 2 illustrates an assembly of a portable terminal according to an exemplary embodiment of the present invention, and FIG. 3 illustrates an assembled portable terminal according to an exemplary embodiment of the present invention.    </p>
+    <p id="p-37" num="37">[0035<confidence value="5">]</confidence>
+       Referring to FIG<confidence value="5">s</confidence>
+. 1 through <part-num-ref name="through">3,</part-num-ref>
+ a portable terminal <part-num-ref name="portable terminal">100</part-num-ref>
+ includes a housing <part-num-ref name="housing">101</part-num-ref>
+ constructed by joining front and rear covers <confidence value="666">101</confidence>
+a and <confidence value="662">101</confidence>
+b, and a case member <part-num-ref name="case member">102</part-num-ref>
+ coupled to enclose at least opposite lateral surfaces of the housing <part-num-ref name="housing">101.</part-num-ref>
+ Here, the case member <part-num-ref name="case member">102</part-num-ref>
+ is made from an extrusion process and coupled with the housing <part-num-ref name="housing">101</part-num-ref>
+ in a slide manner, which presses the front cover <confidence value="666">101</confidence>
+a in a direction to closely contact the same to the rear cover 10<confidence value="588">1b.</confidence>
+    </p>
+    <p id="p-38" num="38">[0036<confidence value="5">]</confidence>
+       The front cover <confidence value="666">101</confidence>
+a is manufactured by an injection molding method with a synthetic resin material or by a die-casting method using a metallic material, having a display device (not shown) therein. Since the case member <part-num-ref name="case member">102</part-num-ref>
+ is manufactured by the injection molding method and coupled to the housing <part-num-ref name="housing">101</part-num-ref>
+ in a slide manner, it is desirable to form the front cover <confidence value="666">101</confidence>
+a through the die-casting method, or the like, using a metallic material. The display device is protected by a window <part-num-ref name="window">111,</part-num-ref>
+ and a voice receiver <part-num-ref name="voice receiver">115</part-num-ref>
+ is provided at the upper side of the display device, i.e., the window <part-num-ref name="window">111.</part-num-ref>
+ Meanwhile, a keypad module <part-num-ref name="keypad module">113</part-num-ref>
+ and a voice transmitter (not shown) are provided at the lower side of the window <part-num-ref name="window">111.</part-num-ref>
+ Formed on the opposite lateral surfaces of the front cover <confidence value="666">101</confidence>
+a are guide rails 117a to be coupled with the case member <part-num-ref name="case member">102.</part-num-ref>
+ At the upper end of the front cover <confidence value="666">101</confidence>
+a, a coupling groove <part-num-ref name="coupling groove">119</part-num-ref>
+ extends in a sliding direction of the case member <part-num-ref name="case member">102.</part-num-ref>
+    </p>
+    <p id="p-39" num="39">[0037<confidence value="5">]</confidence>
+       At this moment, each guide rail 117a extends in the longitudinal direction of the front cover <confidence value="665">10l</confidence>
+a at the opposite lateral surfaces of the front cover <confidence value="665">10l</confidence>
+a, and the coupling groove <part-num-ref name="coupling groove">119</part-num-ref>
+ extends from the upper end of the front cover <confidence value="666">101</confidence>
+a to a location adjacent to the voice receiver <part-num-ref name="voice receiver">115.</part-num-ref>
+ In addition, a guide groove 117b is formed between the guide rail 11<confidence value="88">7a</confidence>
+ and one of the lateral surfaces of the front cover <confidence value="665">10l</confidence>
+a. The guide groove 117b also extends in the longitude direction of the front cover <confidence value="666">101</confidence>
+a and is open to the forward direction of the front cover <confidence value="66688">101a.</confidence>
+    </p>
+    <boundary-data type="header">
+      <confidence value="888">-6-</confidence>
+    </boundary-data>
+    <boundary-data type="header">0201-0311 (P18017-US)</boundary-data>
+    <p id="p-40" num="40">
+      <page-break num="7"/>
+[0038<confidence value="5">]</confidence>
+       Meanwhile, a volume adjusting key, a power button, a hot key for switching to either a camera mode or a digital multimedia broadcasting view mode, and the like, may be installed on the opposite lateral surfaces of the terminal. Moreover, dome sheets 117c corresponding to such keys are formed on the opposite lateral surfaces of the front cover <confidence value="666">101</confidence>
+a. In order to install the dome sheets 117c, a portion of the guide rail 117a may be removed from the opposite lateral surfaces of the front cover <confidence value="66588">10la.</confidence>
+    </p>
+    <p id="p-41" num="41">[0039<confidence value="5">]</confidence>
+       The rear cover <confidence value="666">101</confidence>
+b is joined to the rear surface of the front cover <confidence value="666">101</confidence>
+a to complete the housing <part-num-ref name="housing">101.</part-num-ref>
+ At this point, a portion of the rear cover <confidence value="666">101</confidence>
+b is removed, which enables a portion of the rear surface of the front cover <confidence value="666">101</confidence>
+a to be exposed to the rearward direction of the housing <part-num-ref name="housing">101.</part-num-ref>
+ Accordingly, a mounting recess for receiving a battery pack (not shown) may be provided at the portion of the rear surface of the front cover <confidence value="666">101</confidence>
+a exposed to the rearward direction of the housing <part-num-ref name="housing">101.</part-num-ref>
+    </p>
+    <p id="p-42" num="42">[0040<confidence value="5">]</confidence>
+       Meanwhile, a coupling member <part-num-ref name="coupling member">191</part-num-ref>
+ is provided at the lower end of the housing <part-num-ref name="housing">101.</part-num-ref>
+ The coupling member <part-num-ref name="coupling member">191</part-num-ref>
+ may be provided with a microphone or an antenna module to constitute a voice transmitter therein. In a state where the front cover <confidence value="665">10l</confidence>
+a and the rear cover <confidence value="666">101</confidence>
+b are joined together, the coupling member <part-num-ref name="coupling member">191</part-num-ref>
+ is mounted to enclose the lower end portions of the front cover <confidence value="666">101</confidence>
+a and the rear cover 10<confidence value="5">1</confidence>
+b. Here, the terminal <part-num-ref name="terminal">100</part-num-ref>
+ may be provided with a fastening member (not shown) which is penetrated into the front and rear covers (<confidence value="666">101</confidence>
+a, <confidence value="666">101</confidence>
+b) and coupled with the coupling member <part-num-ref name="coupling member">191.</part-num-ref>
+    </p>
+    <p id="p-43" num="43">[0041<confidence value="5">]</confidence>
+       FIG. 4 illustrates a partially enlarged view of a case member of a portable terminal according to an exemplary embodiment of the present invention, and FIG. 5 illustrates a cross-sectional view of a portable terminal according to an exemplary embodiment of the present invention.    </p>
+    <p id="p-44" num="44">[0042<confidence value="5">]</confidence>
+       Referring to FIG<confidence value="5">s</confidence>
+. 4 and <part-num-ref name="and">5,</part-num-ref>
+ a case member <part-num-ref name="case member">102</part-num-ref>
+ is provided to further enclose opposite lateral surfaces of a housing <part-num-ref name="housing">101</part-num-ref>
+ (i.e., the respective portions of the front and rear surfaces of the housing 101). More particularly, the case member <part-num-ref name="case member">102</part-num-ref>
+ is provided to cover the outer lateral surface of the rear cover 10<confidence value="5">1</confidence>
+b. At this point, a portion among the portions enclosing the rear cover <confidence value="666">101</confidence>
+b is formed with an opening corresponding to the removed portion of the rear cover <confidence value="666">101</confidence>
+b. Hence, after the case member <part-num-ref name="case member">102</part-num-ref>
+ is assembled, the recess for mounting a battery pack of the terminal <part-num-ref name="terminal">100</part-num-ref>
+ is exposed to the outside. In an exemplary implementation, a separate battery pack cover is detachably provided at the opening of the case member <part-num-ref name="case member">102.</part-num-ref>
+    </p>
+    <boundary-data type="header">
+      <confidence value="888">-7-</confidence>
+    </boundary-data>
+    <boundary-data type="header">0201-0311 (P18017-US)</boundary-data>
+    <p id="p-45" num="45">
+      <page-break num="8"/>
+[0043<confidence value="5">]</confidence>
+       The case member <part-num-ref name="case member">102</part-num-ref>
+ is formed with rail grooves 125a extending in the longitudinal direction at the opposite inner walls thereof, which are facing the opposite lateral surfaces of the housing <part-num-ref name="housing">101.</part-num-ref>
+ The rail grooves 125a are designed to receive the respective guide rails 117a to guide the sliding movement of the case member <part-num-ref name="case member">102</part-num-ref>
+ while the case member <part-num-ref name="case member">102</part-num-ref>
+ is being joined with the housing <part-num-ref name="housing">101.</part-num-ref>
+ Thereafter, when the case member <part-num-ref name="case member">102</part-num-ref>
+ is completely joined with the housing <part-num-ref name="housing">101,</part-num-ref>
+ the rail grooves 125a keep the engagement state with the guide rails 117a. At this moment, the entrance side of the rail groove 125a, that is, the inner side of the case member <part-num-ref name="case member">102</part-num-ref>
+ is formed with a guide rib 125c to be engaged with a guide groove 117b. As the guide rib 125c is formed at the entrance side of the rail groove 125a, the respective inner wall of the rail grooves 125a positioned at the front and rear sides of the housing <part-num-ref name="housing">101</part-num-ref>
+ is provided with a groove 125b, a portion of which is enclosed by the guide rib 125c. A portion of the guide rail 117a is engaged with one of the grooves 125b, which are positioned at the forward direction of the housing <part-num-ref name="housing">101.</part-num-ref>
+ The rail groove 125a and the guide rib 125c are respectively engaged with the guide rail 117a and the guide groove 117b to pressurize the front cover <confidence value="666">101</confidence>
+a in a direction closely contacting the same to the rear cover <confidence value="88588">101b.</confidence>
+    </p>
+    <p id="p-46" num="46">[0044<confidence value="5">]</confidence>
+       Meanwhile, a stepped surface 125d supporting the edge portion of the rear cover <confidence value="666">101</confidence>
+b is provided at the inner surface of the case member <part-num-ref name="case member">102.</part-num-ref>
+ In a state where the rear cover <confidence value="666">101</confidence>
+b is supported by the stepped surface 125d, the rail groove 125a and the guide rib 125c press the front cover <confidence value="666">101</confidence>
+a, so that the front cover <confidence value="666">101</confidence>
+a is closely secured to the rear cover 10<confidence value="5">1</confidence>
+b. In addition, since the case member <part-num-ref name="case member">102</part-num-ref>
+ pressurizes the front cover <confidence value="666">101</confidence>
+a in a direction closely contacting the rear cover <confidence value="666">101</confidence>
+b, the case member <part-num-ref name="case member">102</part-num-ref>
+ is closely brought into contact with the front cover <confidence value="666">101</confidence>
+a, which makes it possible to maintain a consistent appearance with the front cover <confidence value="665">10l</confidence>
+a at the opposite sides of the front cover <confidence value="66588">10la.</confidence>
+    </p>
+    <p id="p-47" num="47">[0045<confidence value="5">]</confidence>
+       FIG. 7 illustrates a coupling of a case member with a front cover of a portable terminal according to an exemplary embodiment of the present invention.    </p>
+    <p id="p-48" num="48">[0046<confidence value="5">]</confidence>
+       Referring to FIG. 7, the case member <part-num-ref name="case member">102</part-num-ref>
+ is formed with a coupling protrusion <part-num-ref name="coupling protrusion">129,</part-num-ref>
+ which is engaged with the coupling groove <part-num-ref name="coupling groove">119</part-num-ref>
+ of the front cover <confidence value="666">101</confidence>
+a. The case member <part-num-ref name="case member">102</part-num-ref>
+ is provided with a band member <part-num-ref name="band member">127</part-num-ref>
+ enclosing the upper side of the front cover <confidence value="666">101</confidence>
+a. The coupling protrusion <part-num-ref name="coupling protrusion">129</part-num-ref>
+ is formed at the inner surface of the band member <part-num-ref name="band member">127,</part-num-ref>
+ having a T-shaped cross-section. As the coupling protrusion <part-num-ref name="coupling protrusion">129</part-num-ref>
+ is engaged with the coupling groove <part-num-ref name="coupling groove">119,</part-num-ref>
+ the band member <part-num-ref name="band member">127</part-num-ref>
+ is closely contacted to the front cover <confidence value="666">101</confidence>
+a. In the same manner that the rail groove 125a and the guide rib 125c closely press the front cover <confidence value="666">101</confidence>
+a, so <boundary-data type="header">
+        <confidence value="888">-8-</confidence>
+      </boundary-data>
+      <page-break num="9"/>
+      <boundary-data type="header">0201-0311 (P18017-US)</boundary-data>
+as to make the case member <part-num-ref name="case member">102</part-num-ref>
+ show a consistent appearance with the front cover <confidence value="666">101</confidence>
+a, the band member <part-num-ref name="band member">127</part-num-ref>
+ is also able to maintain a consistent appearance with the front surface of the front cover <confidence value="664">10l</confidence>
+a as the coupling protrusion <part-num-ref name="coupling protrusion">129</part-num-ref>
+ is engaged with the coupling groove <part-num-ref name="coupling groove">119.</part-num-ref>
+    </p>
+    <p id="p-49" num="49">[0047<confidence value="5">]</confidence>
+       Referring back to FIG<confidence value="5">s</confidence>
+. 1 and <part-num-ref name="and">2,</part-num-ref>
+ an exemplary construction is illustrated in which the case member <part-num-ref name="case member">102</part-num-ref>
+ is joined from the upper side to the lower side of the housing <part-num-ref name="housing">101.</part-num-ref>
+ However, it can be understood by those skilled in the art that the case member <part-num-ref name="case member">102</part-num-ref>
+ may be slidably joined from the lower side to the upper side of the housing <part-num-ref name="housing">101,</part-num-ref>
+ provided that the coupling groove <part-num-ref name="coupling groove">119</part-num-ref>
+ can be formed at the lower side of the window <part-num-ref name="window">111,</part-num-ref>
+ i.e., a portion where the keypad module <part-num-ref name="keypad module">113</part-num-ref>
+ is installed. At this point, it is obvious that the coupling member <part-num-ref name="coupling member">191</part-num-ref>
+ should be modified into a construction to be coupled at the upper end of the housing <part-num-ref name="housing">101.</part-num-ref>
+    </p>
+    <p id="p-50" num="50">[0048<confidence value="5">]</confidence>
+       As mentioned above, the terminal <part-num-ref name="terminal">100</part-num-ref>
+ may be provided with a volume adjusting key, a power button, a hot key for switching to either a camera mode or a digital multimedia broadcasting view mode, or the like (referred to as a "function key" hereinafter).    </p>
+    <p id="p-51" num="51">In order to install such a function key, the case member <part-num-ref name="case member">102</part-num-ref>
+ is formed with a key hole <part-num-ref name="key hole">123.</part-num-ref>
+    </p>
+    <p id="p-52" num="52">Each key hole 123 is provided with a key member 121a, which can be projected or retreated from the lateral surface of the case member <part-num-ref name="case member">102.</part-num-ref>
+    </p>
+    <p id="p-53" num="53">[0049<confidence value="5">]</confidence>
+       The case member <part-num-ref name="case member">102</part-num-ref>
+ as such can be made from an extrusion process with a metallic material. Although it requires finishing works at the corner portion or machining works to form a key hole <part-num-ref name="key hole">123,</part-num-ref>
+ or the like, after the extrusion process, it is easy to mass produce products with uniform dimensions by manufacturing the case member <part-num-ref name="case member">102</part-num-ref>
+ through the extrusion process.    </p>
+    <p id="p-54" num="54">[0050<confidence value="5">]</confidence>
+       FIG. 6 illustrates a key member of a portable terminal according to an exemplary embodiment of the present invention.    </p>
+    <p id="p-55" num="55">[0051<confidence value="5">]</confidence>
+       Referring to FIG. 6, a key member 121a is formed with a supporting part 121b extending outwards in a predefined length at its base. The key member 121a may be provided with a coupling piece 121c projecting from the edge of the supporting part 121b. When the key member 121a is installed in the key hole <part-num-ref name="key hole">123,</part-num-ref>
+ the supporting part 121b is supported against the wall surface of the rail groove 125a. If the key member 121a is made from an elastomeric material, such as urethane or silicone, it can firmly deliver the pressing operation by the user to the dome sheet 117c and may be stably positioned in the key hole <part-num-ref name="key hole">123</part-num-ref>
+ without any movements. The key member 121a may be painted on its outer surface or provided with injection moldings or metallic pieces, or the like thereon, so as to maintain a uniform appearance with the case member <part-num-ref name="case member">102.</part-num-ref>
+ The coupling piece 121c is engaged with the rail <boundary-data type="header">
+        <confidence value="888">-9-</confidence>
+      </boundary-data>
+      <page-break num="10"/>
+      <boundary-data type="header">0201-0311 (P18017-US)</boundary-data>
+groove 125a, and the groove 125b is positioned at the rear side of the housing <part-num-ref name="housing">101</part-num-ref>
+ among the grooves 125b, a portion of which is enclosed by the guide rib 125c.    </p>
+    <p id="p-56" num="56">[0052<confidence value="5">]</confidence>
+       As the supporting part 121b is disposed in the rail groove 125a, the case member <part-num-ref name="case member">102</part-num-ref>
+ can interfere with functions of the guide rail 117a when being joined with the housing <part-num-ref name="housing">101.</part-num-ref>
+ To address this issue, each guide rail 117a is formed with an evading hole 11<confidence value="88">7d</confidence>
+ along the path where the supporting part 121b is passing by while the case member <part-num-ref name="case member">102</part-num-ref>
+ is assembled to the housing <part-num-ref name="housing">101.</part-num-ref>
+ In other words, even when the supporting part 121b is positioned within the rail groove 125a, the supporting part 121b maintains its position without interfering with functions of the guide rail 117a.    </p>
+    <p id="p-57" num="57">[0053<confidence value="5">]</confidence>
+       In a state where the case member <part-num-ref name="case member">102</part-num-ref>
+ is completely joined to the housing <part-num-ref name="housing">101,</part-num-ref>
+ a portion of the supporting part 121b is facing the outer wall of the guide rail 117a. As mentioned above, a portion of the guide rail 117a is removed to install the dome sheet 117c, while the key member 121a is disposed correspondingly to the dome sheets 117c. The edge portion of the supporting part 121b is opposing the guide rail 117a and the inner wall of the evading groove 117d, and the supporting part 121b is supported by the inner wall of the evading groove 117d to restore the key member 121a to the initial position, that is, a position protruded to the outer lateral surface of the case member <part-num-ref name="case member">102.</part-num-ref>
+    </p>
+    <p id="p-58" num="58">[0054<confidence value="5">]</confidence>
+       Consequently, it should be noted that the key member 121a can be installed only by arranging it in the key hole <part-num-ref name="key hole">123</part-num-ref>
+ and by locating the coupling piece 121c to be engaged with one of the grooves 125b without using a separate double-sided tape or forming a melting bond protrusion.    </p>
+    <p id="p-59" num="59">[0055<confidence value="5">]</confidence>
+       The terminal <part-num-ref name="terminal">100</part-num-ref>
+ may be provided with a connector for charging, or for connecting to a personal computer, a hands free set, a detachable antenna for viewing digital multimedia broadcasting, or the like, or a socket for a memory card or the like. Such a connector (not shown) or a socket (not shown) is provided at the upper end of the housing, which is protected using a separate cap or a cover and opened for its use, if necessary.    </p>
+    <p id="p-60" num="60">[0056<confidence value="5">]</confidence>
+       In addition to the voice receiver <part-num-ref name="voice receiver">115,</part-num-ref>
+ a separate speaker device to be used in a multimedia function can be installed in the housing <part-num-ref name="housing">101.</part-num-ref>
+ Holes for outputting the sound of such a speaker device may be disposed at the upper end of the housing <part-num-ref name="housing">101.</part-num-ref>
+ At this point, the holes for outputting the sound can be located at the lateral surfaces of the terminal to provide a stereo function, or the like. When the holes for outputting the sound are disposed at the lateral surfaces of the terminal <part-num-ref name="terminal">100,</part-num-ref>
+ the case member <part-num-ref name="case member">102</part-num-ref>
+ also has to be formed with <boundary-data type="header">
+        <confidence value="8">-</confidence>
+ <confidence value="88">10</confidence>
+ <confidence value="8">-</confidence>
+      </boundary-data>
+      <page-break num="11"/>
+      <boundary-data type="header">0201-0311 (P18017-US)</boundary-data>
+additional holes for outputting the sound, or opened to expose the holes for outputting the sound of the speaker device.    </p>
+    <p id="p-61" num="61">[0057<confidence value="5">]</confidence>
+       Since a user opens and uses the connector or the socket according to his/her needs, the upper end portion of the case member <part-num-ref name="case member">102</part-num-ref>
+ is open to the outside. In order to hide the upper end portion of the case member <part-num-ref name="case member">102,</part-num-ref>
+ it is coupled with a cover member <part-num-ref name="cover member">193</part-num-ref>
+ and a decoration cover <part-num-ref name="decoration cover">195.</part-num-ref>
+ The cover member <part-num-ref name="cover member">193</part-num-ref>
+ is assembled and secured to the upper end of the housing <part-num-ref name="housing">101</part-num-ref>
+ through a fastening member, such as screws, while being engaged with the upper end of the case member <part-num-ref name="case member">102.</part-num-ref>
+ Hence, the case member <part-num-ref name="case member">102</part-num-ref>
+ is secured to the housing <part-num-ref name="housing">101.</part-num-ref>
+ Though not shown in the drawings, the cover member <part-num-ref name="cover member">193</part-num-ref>
+ may be provided with holes to expose the connector or the socket, and a cap or a cover to open and close such holes.    </p>
+    <p id="p-62" num="62">Moreover, although the decoration cover <part-num-ref name="decoration cover">195</part-num-ref>
+ is not required to be installed, it is desirable to attach the decoration cover <part-num-ref name="decoration cover">195</part-num-ref>
+ at the outer side of the cover member <part-num-ref name="cover member">193,</part-num-ref>
+ so as to hide the screws fixing the cover member <part-num-ref name="cover member">193</part-num-ref>
+ and polish the outer appearance of the terminal <part-num-ref name="terminal">100.</part-num-ref>
+    </p>
+    <p id="p-63" num="63">When the decoration cover <part-num-ref name="decoration cover">195</part-num-ref>
+ is attached to the cover member <part-num-ref name="cover member">193,</part-num-ref>
+ it is obvious that the decoration cover <part-num-ref name="decoration cover">195</part-num-ref>
+ also has to be formed with holes to expose the connector or the socket.    </p>
+    <p id="p-64" num="64">[0058<confidence value="5">]</confidence>
+       While the invention has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined in the appended claims and their equivalents.    </p>
+    <p id="p-65" num="65">[0059<confidence value="5">]</confidence>
+       For instance, as mentioned above, the case member can be slidably coupled from the lower side to the upper side of the housing. In this case, the coupling member needs to be a modified structure to be assembled at the upper end of the portable terminal.    </p>
+    <p id="p-66" num="66">[0060<confidence value="5">]</confidence>
+       Further, in exemplary embodiments of the present invention, a construction of a bar-type terminal is described. However, in case that the terminal is provided with a housing constructed to join the front cover to the rear cover, the construction to couple the front cover with the rear cover is applicable to a folder-type terminal or a slide-type terminal or the like using the case member in accordance with exemplary embodiments of the present invention.    </p>
+    <boundary-data type="header">
+      <confidence value="8888">-11-</confidence>
+    </boundary-data>
+  </description>
+</us-patent-application>
+

applicant/13146013.xml

@@ -0,0 +1,28 @@
+<?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="13146013.07-23-2011.GQHDJR3APPOPPY2.SPEC.xml" pat:id="GQHDJR3APPOPPY2" 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>13146013</pat:ApplicationNumber></pat:ApplicationHeaderDetails>
+<pat:PageTotalQuantity>1</pat:PageTotalQuantity>
+<pat:ParagraphTotalQuantity>8</pat:ParagraphTotalQuantity>
+</pat:DocumentHeaderDetails>
+<pat:MailRoomDate>2011-07-23</pat:MailRoomDate>
+<pat:Specification pat:id="Specification">
+<?PageStart number="1"?>
+<pat:Heading pat:id="h-1">IN THE SPECIFICATION</pat:Heading>
+<pat:P pat:id="p-1" pat:pNumber="1">At Page <pat:OCRConfidenceData pat:levelNumber="6">1</pat:OCRConfidenceData>, <pat:PartName pat:idref="PN-00001">Line </pat:PartName><pat:PartNumber pat:id="PN-00001">2</pat:PartNumber>, please insert the following paragraphs<pat:OCRConfidenceData pat:levelNumber="5">:</pat:OCRConfidenceData></pat:P>
+<pat:Heading pat:id="h-2">CROSS-REFERENCE TO RELATED APPLICATIONS</pat:Heading>
+<pat:P pat:id="p-2" pat:pNumber="2">This application  is a US    National Stage  of International Application  No.</pat:P>
+<pat:P pat:id="p-3" pat:pNumber="3">PCT/GB2010/000288, filed 18 February 2010, which claims the <pat:PartName pat:idref="PN-00002">benefit of GB 0902957.0, filed </pat:PartName><pat:PartNumber pat:id="PN-00002">20</pat:PartNumber> February 2009, both herein fully incorporated by reference.</pat:P>
+<pat:Heading pat:id="h-3">FIELD OF THE INVENTION</pat:Heading>
+<pat:P pat:id="p-4" pat:pNumber="4">At Page <pat:OCRConfidenceData pat:levelNumber="6">1</pat:OCRConfidenceData>, <pat:PartName pat:idref="PN-00003">Line </pat:PartName><pat:PartNumber pat:id="PN-00003">6</pat:PartNumber>, please insert the following heading<pat:OCRConfidenceData pat:levelNumber="5">:</pat:OCRConfidenceData></pat:P>
+<pat:Heading pat:id="h-4"><pat:OCRConfidenceData pat:levelNumber="88">BA</pat:OCRConfidenceData>CKGROUND OF THE INVENTION</pat:Heading>
+<pat:P pat:id="p-5" pat:pNumber="5">At Page <pat:OCRConfidenceData pat:levelNumber="6">1</pat:OCRConfidenceData>, <pat:PartName pat:idref="PN-00004">Line </pat:PartName><pat:PartNumber pat:id="PN-00004">19</pat:PartNumber>, please insert the following heading:</pat:P>
+<pat:Heading pat:id="h-5">BRIEF SUMMARY OF THE INVENTION</pat:Heading>
+<pat:P pat:id="p-6" pat:pNumber="6">At Page 3, <pat:PartName pat:idref="PN-00005">Line </pat:PartName><pat:PartNumber pat:id="PN-00005">27</pat:PartNumber>, please insert the following heading<pat:OCRConfidenceData pat:levelNumber="5">:</pat:OCRConfidenceData></pat:P>
+<pat:Heading pat:id="h-6">BRIEF DESCRIPTION OF THE DRAWINGS</pat:Heading>
+<pat:P pat:id="p-7" pat:pNumber="7">At Page 4, <pat:PartName pat:idref="PN-00006">before Line </pat:PartName><pat:PartNumber pat:id="PN-00006">4</pat:PartNumber>, please insert the following heading<pat:OCRConfidenceData pat:levelNumber="5">:</pat:OCRConfidenceData></pat:P>
+<pat:Heading pat:id="h-7">DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS</pat:Heading>
+<pat:Heading pat:id="h-8"><pat:OCRConfidenceData pat:levelNumber="885">TRO</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="685">UTM</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="88">AN</pat:OCRConfidenceData></pat:Heading>
+<pat:Heading pat:id="h-9">SANDER<pat:OCRConfidenceData pat:levelNumber="5">S</pat:OCRConfidenceData></pat:Heading>
+<pat:P pat:id="p-8" pat:pNumber="8">2296998v<pat:OCRConfidenceData pat:levelNumber="4">1</pat:OCRConfidenceData>                               5/6</pat:P>
+</pat:Specification></pat:SpecificationDocument>

applicant/13274615.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="13274615.07-12-2013.HJ1SGQYLPXXIFW3.SPEC.xml" pat:id="HJ1SGQYLPXXIFW3" 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>13274615</pat:ApplicationNumber></pat:ApplicationHeaderDetails>
+<pat:PageTotalQuantity>1</pat:PageTotalQuantity>
+<pat:ParagraphTotalQuantity>4</pat:ParagraphTotalQuantity>
+</pat:DocumentHeaderDetails>
+<pat:MailRoomDate>2013-07-12</pat:MailRoomDate>
+<pat:Specification pat:id="Specification">
+<?PageStart number="1"?>
+<pat:P pat:id="p-1" pat:pNumber="1">Amendments to the Substitute Specification (filed November 5<pat:OCRConfidenceData pat:levelNumber="5">,</pat:OCRConfidenceData> 2012) <pat:PartName pat:idref="PN-00001">Page </pat:PartName><pat:PartNumber pat:id="PN-00001">2</pat:PartNumber>, please amend the paragraph spanning lines 21-26 as follows:</pat:P>
+<pat:P pat:id="p-2" pat:pNumber="2">In a further emb<pat:OCRConfidenceData pat:levelNumber="56866866">odiment,</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="66">it</pat:OCRConfidenceData> embodiment, the electric drive can have a further (second) transmission stage. It has also proven advantageous if the transmission of the transmission stage can locally displace the force transmission from the electric drive to the mechanical actuating unit. The transmission stage is thus capable of introducing the force of the electric drive into the mechanical actuating unit at various predeterminable locations.</pat:P>
+<pat:P pat:id="p-3" pat:pNumber="3">Page 7, please amend the paragraph spanning lines 27-30 as follows:</pat:P>
+<pat:P pat:id="p-4" pat:pNumber="4">Even if the invention has been specifically described by means of the illustrated embodiment it will be appreciated that the subject-matter of the application is not limited to that embodiment. Rather features and modifications which serve to carry the idea of the invention into effect are certainly conceivable and wanted. For example, the <pat:PartName pat:idref="PN-00002">electric drive </pat:PartName><pat:PartNumber pat:id="PN-00002">2</pat:PartNumber> can have a <pat:PartName pat:idref="PN-00003">further (second) transmission stage </pat:PartName><pat:PartNumber pat:id="PN-00003">40</pat:PartNumber>.</pat:P>
+<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8">2</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>
+</pat:Specification></pat:SpecificationDocument>

applicant/13366447.xml

@@ -0,0 +1,502 @@
+<?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" file="13366447.2012-02-06.GYBOV9SDPXXIFW3.SPEC.XML">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>13366447</doc-number>
+        <date>2012-02-06</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <boundary-data type="header">67097-1741 PUS<confidence value="5">1</confidence>
+    </boundary-data>
+    <boundary-data type="header">PA-0021171-US-AA</boundary-data>
+    <heading id="h-1">GAS TURBINE ENGINE BUFFER SYSTEM</heading>
+    <heading id="h-2">CROSS-REFERENCE TO RELATED APPLICATIONS</heading>
+    <p id="p-1" num="1">
+      <confidence value="655565">[0001]</confidence>
+ This application claims priority to U.S. Provisional Application No.    </p>
+    <p id="p-2" num="2">61/592,925 which was filed on January 31, 2012.</p>
+    <heading id="h-3">BACKGROUND</heading>
+    <p id="p-3" num="3">[0002<confidence value="5">]</confidence>
+ This disclosure relates to a gas turbine engine, and more particularly to a buffer system that can provide buffer cooling air to cool portions of the gas turbine engine, including at least one shaft of the gas turbine engine.    </p>
+    <p id="p-4" num="4">[0003<confidence value="5">]</confidence>
+ Gas turbine engines typically include at least a compressor section, a combustor section and a turbine section. During operation, air is pressurized in the compressor section and is mixed with fuel and burned in the combustor section to generate hot combustion gases. The hot combustion gases are communicated through the turbine section which extracts energy from the hot combustion gases to power the compressor section and other gas turbine engine modes.    </p>
+    <p id="p-5" num="5">[0004<confidence value="5">]</confidence>
+ Gas turbine engines typically include shafts that support a plurality of airfoil supporting rotors of the compressor section and the turbine section. For example, in a two-spool turbofan engine, an inner shaft (i.e., a low speed shaft) and an outer shaft (i.e., a high speed shaft) can be incorporated. These shafts, in particular the inner shaft, can be exposed to relatively high torque loading and stresses that result from size limitations caused by the need for the shaft to traverse the rotor structure inboard of the radially inner disk bores.    </p>
+    <heading id="h-4">SUMMARY</heading>
+    <p id="p-6" num="6">
+      <confidence value="866666">[0005]</confidence>
+ A gas turbine engine includes a buffer system that communicates a buffer cooling air to at least one bearing structure and at least one shaft of the gas turbine engine. The buffer system includes a first bleed air supply and a conditioning device that conditions the first bleed air supply to render the first buffer supply air at an acceptable temperature to pressurize the at least one bearing structure and cool the at least one shaft.    </p>
+    <boundary-data type="header">
+      <confidence value="8">1</confidence>
+    </boundary-data>
+    <boundary-data type="header">67097-1741 PUS<confidence value="5">1</confidence>
+    </boundary-data>
+    <boundary-data type="header">PA-0021171-US-AA</boundary-data>
+    <p id="p-7" num="7">
+      <page-break num="2"/>
+[0006] In a further embodiment of the foregoing gas turbine engine embodiment, the at least one shaft can be an inner shaft that interconnects a low pressure compressor and a low pressure turbine of the gas turbine engine.    </p>
+    <p id="p-8" num="8">
+      <confidence value="8666">[000</confidence>
+7] In a further embodiment of either of the foregoing gas turbine engine embodiments, the at least one shaft can be an outer shaft that interconnects a high pressure and a high pressure turbine of the gas turbine engine.    </p>
+    <p id="p-9" num="9">
+      <confidence value="86666">[0008</confidence>
+] In a further embodiment of any of the foregoing gas turbine engine embodiments, the at least one shaft can include an outer shaft that surrounds an inner shaft, and the buffer cooling air can be communicated between the inner shaft and the outer shaft.    </p>
+    <p id="p-10" num="10">
+      <confidence value="8555">[000</confidence>
+9] In a further embodiment of any of the foregoing gas turbine engine embodiments, the outer shaft can include a tie shaft.    </p>
+    <p id="p-11" num="11">
+      <confidence value="655565">[00010</confidence>
+] In a further embodiment of any of the foregoing gas turbine engine embodiments, the buffer cooling air can be communicated axially through an inner diameter of the at least one shaft.    </p>
+    <p id="p-12" num="12">[00011] In a further embodiment of any of the foregoing gas turbine engine embodiments, the buffer cooling air can be communicated axially along an outer diameter of the at least one shaft.</p>
+    <p id="p-13" num="13">
+      <confidence value="8666885">[00012]</confidence>
+ In a further embodiment of any of the foregoing gas turbine engine embodiments, the buffer system can include a second bleed air supply and a valve that selects between the first bleed air supply and the second bleed air supply to communicate the buffer cooling air.    </p>
+    <p id="p-14" num="14">
+      <confidence value="8666">[000</confidence>
+13] In a further embodiment of any of the foregoing gas turbine engine embodiments, the buffer system can include a controller that selectively operates the conditioning device.    </p>
+    <p id="p-15" num="15">[00014] In another exemplary embodiment, a gas turbine engine includes a compressor section, a combustor in fluid communication with the compressor section, a turbine section in fluid communication with the combustor, at least one shaft that interconnects the portion of the compressor section and the turbine section, and a bearing structure that supports the at least one shaft. The bearing structure can include a bearing compartment. A buffer system can selectively communicate a buffer cooling air to the bearing structure and axially along the at least one shaft.</p>
+    <boundary-data type="header">
+      <confidence value="8">2</confidence>
+    </boundary-data>
+    <boundary-data type="header">67097-1741 PUS<confidence value="5">1</confidence>
+    </boundary-data>
+    <boundary-data type="header">PA-0021171-US-AA</boundary-data>
+    <p id="p-16" num="16">
+      <page-break num="3"/>
+[00015<confidence value="5">]</confidence>
+ In a further embodiment of the foregoing gas turbine engine embodiment, the buffer system can include a first bleed air supply and a conditioning device that conditions the first bleed air supply to render the buffer cooling air.    </p>
+    <p id="p-17" num="17">[00016] In a further embodiment of either of the foregoing gas turbine engine embodiments, the buffer system can include a first bleed air supply, a second bleed air supply, a valve that selects between the first bleed air supply and the second bleed air supply, and a conditioning device that conditions either the first bleed air supply or the said second bleed air supply to render the buffer cooling air.</p>
+    <p id="p-18" num="18">
+      <confidence value="8666">[000</confidence>
+17] In a further embodiment of any of the foregoing gas turbine engine embodiments, the conditioning device can include either a heat exchanger or an ejector.    </p>
+    <p id="p-19" num="19">
+      <confidence value="8666865">[00018]</confidence>
+ In a further embodiment of any of the foregoing gas turbine engine embodiments, the gas turbine engine can include a high bypass geared aircraft engine having a bypass ratio of greater than about six (6).    </p>
+    <p id="p-20" num="20">
+      <confidence value="8666">[000</confidence>
+19] In a further embodiment of any of the foregoing gas turbine engine embodiments, the gas turbine engine includes a low fan pressure ratio of less than about 1.45.    </p>
+    <p id="p-21" num="21">[00020] In yet another exemplary embodiment, a method of cooling a portion of a gas turbine engine includes communicating a buffer cooling air to at least a bearing structure of the gas turbine engine to pressurize a bearing compartment of the at least one bearing structure. The buffer cooling air can also be communicated axially along at least a portion of at least one shaft of the gas turbine engine.</p>
+    <p id="p-22" num="22">[00021] In a further embodiment of the foregoing method embodiment, the step of communicating the buffer cooling air axially along at least a portion of the at least one shaft can include communicating the buffer cooling air along an outer diameter of the at least one shaft.</p>
+    <p id="p-23" num="23">[00022] In a further embodiment of either of the foregoing method embodiments, the step of communicating the buffer cooling air axially along at least a portion of the at least one shaft can include communicating the buffer cooling air through an inner diameter of the at least one shaft.</p>
+    <p id="p-24" num="24">[00023] In a further embodiment of any of the foregoing method embodiments, the step of communicating the buffer cooling air axially along at least a portion of the at least one shaft can include communicating the buffer cooling air along each of an inner diameter and an outer diameter of the at least one shaft.</p>
+    <boundary-data type="header">
+      <confidence value="8">3</confidence>
+    </boundary-data>
+    <boundary-data type="header">67097-1741 PUS<confidence value="5">1</confidence>
+    </boundary-data>
+    <boundary-data type="header">PA-0021171-US-AA</boundary-data>
+    <p id="p-25" num="25">
+      <page-break num="4"/>
+[00024<confidence value="5">]</confidence>
+ In a further embodiment of any of the foregoing method embodiments, a bleed air supply is cooled prior to communicating the buffer cooling air.    </p>
+    <p id="p-26" num="26">[00025<confidence value="5">]</confidence>
+ The various features and advantages of this disclosure will become apparent to those skilled in the art from the following detailed description. The drawings that accompany the detailed description can be briefly described as follows.    </p>
+    <heading id="h-5">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
+    <p id="p-27" num="27">[00026<confidence value="5">]</confidence>
+ Figure 1 is a cross-section of a gas turbine engine.    </p>
+    <p id="p-28" num="28">
+      <confidence value="8666">[000</confidence>
+27] Figure 2 is a schematic cross-section a gas turbine engine.    </p>
+    <p id="p-29" num="29">[0002<confidence value="66">8]</confidence>
+ Figure 3 is a schematic of an example buffer system of the gas turbine engine.    </p>
+    <p id="p-30" num="30">[00029<confidence value="5">]</confidence>
+ Figure 4 illustrates additional aspects of the buffer system of Figure 3.    </p>
+    <p id="p-31" num="31">[00030<confidence value="5">]</confidence>
+ Figure 5<confidence value="5">i</confidence>
+s a schematic of another example of a buffer system.    </p>
+    <heading id="h-6">DETAILED DESCRIPTION</heading>
+    <p id="p-32" num="32">[00031<confidence value="5">]</confidence>
+ Figure 1 is a cross-section of a gas turbine engine <part-num-ref name="gas turbine engine">20.</part-num-ref>
+ The gas turbine engine <part-num-ref name="gas turbine engine">20</part-num-ref>
+ of this example is a two-spool turbofan engine that generally incorporates a fan section <part-num-ref name="fan section">22,</part-num-ref>
+ a compressor section <part-num-ref name="compressor section">24,</part-num-ref>
+ a combustor section <part-num-ref name="combustor section">26</part-num-ref>
+ and a turbine section <part-num-ref name="turbine section">28.</part-num-ref>
+ Alternative engines might include an augmenter section (not shown) among other systems or features. The fan section <part-num-ref name="fan section">22</part-num-ref>
+ drives air along a bypass flow path while the compressor section <part-num-ref name="compressor section">24</part-num-ref>
+ drives air along a core flow path for compression and communication into the combustor section <part-num-ref name="combustor section">26.</part-num-ref>
+ The hot combustion gases generated in the combustor section <part-num-ref name="combustor section">26</part-num-ref>
+ are expanded through the turbine section <part-num-ref name="turbine section">28.</part-num-ref>
+ Although depicted as a turbofan gas turbine engine in the disclosed non-limiting embodiment, it should be understood that the concepts described herein are not limited to turbofan engines and these teachings could extend to other types of turbine engines, including but not limited to three-spool engine architectures and land based engines.    </p>
+    <p id="p-33" num="33">[00032<confidence value="5">]</confidence>
+ The gas turbine engine <part-num-ref name="gas turbine engine">20</part-num-ref>
+ generally includes a low speed spool <part-num-ref name="low speed spool">30</part-num-ref>
+ and a high speed spool <part-num-ref name="high speed spool">32</part-num-ref>
+ mounted for rotation about an engine centerline longitudinal axis A relative to an engine static structure <part-num-ref name="engine static structure">36</part-num-ref>
+ via several bearing structures <part-num-ref name="via several bearing structures">38.</part-num-ref>
+ It should be understood that various bearing structures <part-num-ref name="understood that various bearing structures">38</part-num-ref>
+ at various locations may alternatively or additionally be provided.    </p>
+    <p id="p-34" num="34">[00033<confidence value="5">]</confidence>
+ The low speed spool <part-num-ref name="low speed spool">30</part-num-ref>
+ generally includes an inner shaft <part-num-ref name="inner shaft">40</part-num-ref>
+ (i.e., a low shaft) that interconnects a fan <part-num-ref name="fan">42,</part-num-ref>
+ a low pressure compressor <part-num-ref name="low pressure compressor">44</part-num-ref>
+ and a low pressure <boundary-data type="header">
+        <confidence value="8">4</confidence>
+      </boundary-data>
+      <page-break num="5"/>
+      <boundary-data type="header">67097-1741 PUS<confidence value="5">1</confidence>
+      </boundary-data>
+      <boundary-data type="header">PA-0021171-US-AA</boundary-data>
+turbine <part-num-ref name="low pressure turbine">46.</part-num-ref>
+ The inner shaft <part-num-ref name="inner shaft">40</part-num-ref>
+ can be connected to the fan <part-num-ref name="fan">42</part-num-ref>
+ through a geared architecture <part-num-ref name="geared architecture">48</part-num-ref>
+ to drive the fan <part-num-ref name="fan">42</part-num-ref>
+ at a lower speed than the low speed spool <part-num-ref name="low speed spool">30.</part-num-ref>
+ The high speed spool <part-num-ref name="high speed spool">32</part-num-ref>
+ includes an outer shaft <part-num-ref name="outer shaft">50</part-num-ref>
+ (i.e., a high shaft) that interconnects a high pressure compressor <part-num-ref name="high pressure compressor">52</part-num-ref>
+ and a high pressure turbine <part-num-ref name="high pressure turbine">54.</part-num-ref>
+ In this example, the inner shaft <part-num-ref name="inner shaft">40</part-num-ref>
+ and the outer shaft <part-num-ref name="outer shaft">50</part-num-ref>
+ are supported at a plurality of axial locations by bearing structures <part-num-ref name="axial locations by bearing structures">38</part-num-ref>
+ that are positioned within the engine static structure <part-num-ref name="engine static structure">36.</part-num-ref>
+    </p>
+    <p id="p-35" num="35">[00034] A combustor <part-num-ref name="combustor">56</part-num-ref>
+ is arranged between the high pressure compressor <part-num-ref name="high pressure compressor">52</part-num-ref>
+ and the high pressure turbine <part-num-ref name="high pressure turbine">54.</part-num-ref>
+ A mid-turbine frame <part-num-ref name="mid-turbine frame">57</part-num-ref>
+ of the engine static structure <part-num-ref name="engine static structure">36</part-num-ref>
+ is arranged generally between the high pressure turbine <part-num-ref name="high pressure turbine">54</part-num-ref>
+ and the low pressure turbine <part-num-ref name="low pressure turbine">46.</part-num-ref>
+ The mid-turbine frame <part-num-ref name="mid-turbine frame">57</part-num-ref>
+ can support one or more bearing structures <part-num-ref name="can support one or more bearing structures">38</part-num-ref>
+ in the turbine section <part-num-ref name="turbine section">28.</part-num-ref>
+ The inner shaft <part-num-ref name="inner shaft">40</part-num-ref>
+ and the outer shaft <part-num-ref name="outer shaft">50</part-num-ref>
+ are concentric and rotate via the bearing structures <part-num-ref name="bearing structures">38</part-num-ref>
+ about the engine centerline longitudinal axis A, which is collinear with their longitudinal axes. The inner shaft <part-num-ref name="inner shaft">40</part-num-ref>
+ and the outer shaft <part-num-ref name="outer shaft">50</part-num-ref>
+ can be either co-rotating or counter-rotating with respect to one another.    </p>
+    <p id="p-36" num="36">[00035] The core airflow is compressed by the low pressure compressor <part-num-ref name="low pressure compressor">44</part-num-ref>
+ and the high pressure compressor <part-num-ref name="high pressure compressor">52,</part-num-ref>
+ is mixed with fuel and burned in the combustor <part-num-ref name="combustor">56,</part-num-ref>
+ and is then expanded over the high pressure turbine <part-num-ref name="high pressure turbine">54</part-num-ref>
+ and the low pressure turbine <part-num-ref name="low pressure turbine">46.</part-num-ref>
+ The mid-turbine frame <part-num-ref name="mid-turbine frame">57</part-num-ref>
+ includes airfoils <part-num-ref name="includes airfoils">59</part-num-ref>
+ which are in the core airflow path.    </p>
+    <p id="p-37" num="37">The high pressure turbine 54 and the low pressure turbine <part-num-ref name="low pressure turbine">46</part-num-ref>
+ rotationally drive the respective low speed spool <part-num-ref name="respective low speed spool">30</part-num-ref>
+ and the high speed spool <part-num-ref name="high speed spool">32</part-num-ref>
+ in response to the expansion.    </p>
+    <p id="p-38" num="38">[00036] In some non-limiting examples, the gas turbine engine <part-num-ref name="gas turbine engine">20</part-num-ref>
+ is a high- bypass geared aircraft engine. In a further example, the gas turbine engine <part-num-ref name="gas turbine engine">20</part-num-ref>
+ bypass ratio is greater than about six (6:1). The geared architecture <part-num-ref name="geared architecture">48</part-num-ref>
+ of the example gas turbine engine <part-num-ref name="example gas turbine engine">20</part-num-ref>
+ includes an epicyclic gear train, such as a planetary gear system or other gear system. The example epicyclic gear train has a gear reduction ratio of greater than about 2.3. The geared architecture <part-num-ref name="geared architecture">48</part-num-ref>
+ enables operation of the low speed spool <part-num-ref name="low speed spool">30</part-num-ref>
+ at higher speeds which can increase the operational efficiency of the low pressure compressor <part-num-ref name="low pressure compressor">44</part-num-ref>
+ and low pressure turbine <part-num-ref name="low pressure turbine">46</part-num-ref>
+ and render increased pressure in a fewer number of stages.    </p>
+    <p id="p-39" num="39">[00037] The low pressure turbine <part-num-ref name="low pressure turbine">46</part-num-ref>
+ pressure ratio is pressure measured prior to inlet of low pressure turbine <part-num-ref name="low pressure turbine">46</part-num-ref>
+ as related to the pressure at the outlet of the low pressure turbine <part-num-ref name="low pressure turbine">46</part-num-ref>
+ of the gas turbine engine <part-num-ref name="gas turbine engine">20.</part-num-ref>
+ In another non-limiting embodiment, <boundary-data type="header">
+        <confidence value="5">5</confidence>
+      </boundary-data>
+      <page-break num="6"/>
+      <boundary-data type="header">67097-1741 PUS<confidence value="5">1</confidence>
+      </boundary-data>
+      <boundary-data type="header">PA-0021171-US-AA</boundary-data>
+the bypass ratio of the gas turbine engine <part-num-ref name="gas turbine engine">20</part-num-ref>
+ is greater than about ten (10:1), the fan diameter is significantly larger than that of the low pressure compressor <part-num-ref name="low pressure compressor">44,</part-num-ref>
+ and the low pressure turbine <part-num-ref name="low pressure turbine">46</part-num-ref>
+ has a pressure ratio that is greater than about <part-num-ref name="greater than about">5</part-num-ref>
+ (5:1). The geared architecture <part-num-ref name="geared architecture">48</part-num-ref>
+ of yet another embodiment is an epicyclic gear train with a gear reduction ratio of greater than about 2.5:1. It should be understood, however, that the above parameters are only exemplary of one embodiment of a geared architecture engine and that the present disclosure is applicable to other gas turbine engines including direct drive turbofans.    </p>
+    <p id="p-40" num="40">[0003<confidence value="66">8]</confidence>
+ In this embodiment of the example gas turbine engine <part-num-ref name="example gas turbine engine">20,</part-num-ref>
+ a significant amount of thrust is provided by a bypass flow B due to the high bypass ratio. The fan section <part-num-ref name="fan section">22</part-num-ref>
+ of the gas turbine engine <part-num-ref name="gas turbine engine">20</part-num-ref>
+ is designed for a particular flight condition-- typically cruise at about 0.8 Mach and about 35,000 feet. This flight condition, with the gas turbine engine <part-num-ref name="gas turbine engine">20</part-num-ref>
+ at its best fuel consumption, is also known as bucket cruise.    </p>
+    <p id="p-41" num="41">TSFC (Thrust Specific Fuel Consumption) is an industry standard parameter of fuel consumption per unit of thrust.</p>
+    <p id="p-42" num="42">[00039<confidence value="5">]</confidence>
+ Fan Pressure Ratio is the pressure ratio across the fan section <part-num-ref name="fan section">22</part-num-ref>
+ without the use of a Fan Exit Guide Vane system. The low Fan Pressure Ratio according to one non-limiting embodiment of the example gas turbine engine <part-num-ref name="example gas turbine engine">20</part-num-ref>
+ is less than 1.45.    </p>
+    <p id="p-43" num="43">[00040<confidence value="5">]</confidence>
+ Low Corrected Fan Tip Speed is the actual fan tip speed divided by an industry standard temperature correction of "T" / 518.70<confidence value="5">5</confidence>
+. T represents the ambient temperature in degrees Rankine. The Low Co<confidence value="66">rr</confidence>
+ected Fan Tip Speed according to one non-limiting embodiment of the example gas turbine engine <part-num-ref name="example gas turbine engine">20</part-num-ref>
+ is less than about <part-num-ref name="less than about">1150</part-num-ref>
+ fps <part-num-ref name="fps">(351</part-num-ref>
+ m<confidence value="5">/</confidence>
+s).    </p>
+    <p id="p-44" num="44">[00041<confidence value="5">]</confidence>
+ Figure 2 illustrates a portion <part-num-ref name="portion">100</part-num-ref>
+ of a gas turbine engine, such as the gas turbine engine <part-num-ref name="gas turbine engine">20.</part-num-ref>
+ The portion <part-num-ref name="portion">100</part-num-ref>
+ can include one or more bearing structures <part-num-ref name="can include one or more bearing structures">38.</part-num-ref>
+    </p>
+    <p id="p-45" num="45">Only one bearing structure 38 is depicted in Figure 2 to schematically illustrate its features, but this is in no way intended to limit this disclosure.</p>
+    <p id="p-46" num="46">[00042<confidence value="5">]</confidence>
+ The bearing structure <part-num-ref name="bearing structure">38</part-num-ref>
+ supports a shaft <part-num-ref name="shaft">61,</part-num-ref>
+ such as the outer shaft <part-num-ref name="outer shaft">50,</part-num-ref>
+ which supports a rotor assembly <part-num-ref name="rotor assembly">63,</part-num-ref>
+ such as a rotor assembly of the compressor section <part-num-ref name="compressor section">24</part-num-ref>
+ or the turbine section <part-num-ref name="turbine section">28,</part-num-ref>
+ through a hub <part-num-ref name="hub">65.</part-num-ref>
+ In this example, the shaft <part-num-ref name="shaft">61</part-num-ref>
+ is a tie shaft that that connects the high pressure compressor <part-num-ref name="high pressure compressor">52</part-num-ref>
+ to the high pressure turbine <part-num-ref name="high pressure turbine">54.</part-num-ref>
+ The rotor assembly <part-num-ref name="rotor assembly">63</part-num-ref>
+ carries at least one airfoil <part-num-ref name="least one airfoil">67</part-num-ref>
+ for adding or extracting energy from the core airflow.    </p>
+    <boundary-data type="header">
+      <confidence value="8">6</confidence>
+    </boundary-data>
+    <boundary-data type="header">67097-1741 PUS<confidence value="5">1</confidence>
+    </boundary-data>
+    <boundary-data type="header">PA-0021171-US-AA</boundary-data>
+    <p id="p-47" num="47">
+      <page-break num="7"/>
+[00043<confidence value="5">]</confidence>
+ The bearing structure <part-num-ref name="bearing structure">38</part-num-ref>
+ defines a bearing compartment B that houses one or more bearings <part-num-ref name="bearing compartment B that houses one or more bearings">71.</part-num-ref>
+ The bearing compartment B contains a lubricant for lubricating (and acting as a cooling medium to) the bearings <part-num-ref name="bearings">71.</part-num-ref>
+ One or more seals <part-num-ref name="bearings 71. One or more seals">73</part-num-ref>
+ (two shown) contain the lubricant within the bearing compartment B. The seals <part-num-ref name="seals">73</part-num-ref>
+ of the bearing compartment B must be pressurized to prevent the lubricant from leaking out during certain flight conditions, both steady state and transient. A buffer system can be used to communicate buffer supply air to the bearing compartment B in order to provide adequate pressurization of the seals <part-num-ref name="seals">73</part-num-ref>
+ without exceeding material and/or lubricant temperature limitations. Example buffer systems that can be used for this and other purposes, including cooling at least one shaft, are detailed below.    </p>
+    <p id="p-48" num="48">[00044<confidence value="5">]</confidence>
+ Figure 3 illustrates an example buffer system <part-num-ref name="example buffer system">60</part-num-ref>
+ that can communicate a buffer cooling air <part-num-ref name="buffer cooling air">62</part-num-ref>
+ to a first portion of the gas turbine engine <part-num-ref name="gas turbine engine">20,</part-num-ref>
+ such one or more bearing structures <part-num-ref name="gas turbine engine 20, such one or more bearing structures">38</part-num-ref>
+ (shown schematically in Figure 3) and a second portion of the gas turbine engine <part-num-ref name="gas turbine engine">20,</part-num-ref>
+ such as to the inner shaft <part-num-ref name="inner shaft">40</part-num-ref>
+ (shown schematically in Figure 4) of the gas turbine engine <part-num-ref name="gas turbine engine">20.</part-num-ref>
+ The buffer cooling air <part-num-ref name="buffer cooling air">62</part-num-ref>
+ pressurizes the outside of the bearing compartment(s) of the bearing structure(s) <part-num-ref name="bearing structure(s)">38</part-num-ref>
+ to maintain sufficient pressure differential between the buffer cavity and the inner bearing compartment cavity and maintain bearing compartment seal leakage inflow at an acceptable temperature. The buffer cooling air <part-num-ref name="buffer cooling air">62</part-num-ref>
+ can also be used to cool the inner shaft <part-num-ref name="inner shaft">40</part-num-ref>
+ (and optionally the outer shaft <part-num-ref name="outer shaft">50,</part-num-ref>
+ see Figure 1) to acceptable operating temperatures. By cooling the inner and outer shafts <part-num-ref name="outer shafts">40,</part-num-ref>
+ <part-num-ref name="outer shafts 40,">50</part-num-ref>
+ with the buffer cooling air <part-num-ref name="buffer cooling air">62,</part-num-ref>
+ the inner and outer shafts <part-num-ref name="outer shafts">40,</part-num-ref>
+ <part-num-ref name="outer shafts 40,">50</part-num-ref>
+ can be manufactured using relatively low temperature capable materials rather than exotic, high cost, and difficult to manufacture alloys. Example low temperature capable materials include steel or stainless steel among other known materials.    </p>
+    <p id="p-49" num="49">[00045<confidence value="5">]</confidence>
+ The buffer system <part-num-ref name="buffer system">60</part-num-ref>
+ of Figure 3 may include a bleed air supply <part-num-ref name="bleed air supply">64</part-num-ref>
+ and a conditioning device <part-num-ref name="conditioning device">80.</part-num-ref>
+ The bleed air supply <part-num-ref name="bleed air supply">64</part-num-ref>
+ may be sourced from the fan section <part-num-ref name="fan section">22,</part-num-ref>
+ the low pressure compressor <part-num-ref name="low pressure compressor">44</part-num-ref>
+ or the high pressure compressor <part-num-ref name="high pressure compressor">52.</part-num-ref>
+ In the illustrated non-limiting example, the bleed air supply <part-num-ref name="bleed air supply">64</part-num-ref>
+ is sourced from a middle stage of the high pressure compressor <part-num-ref name="high pressure compressor">52.</part-num-ref>
+ The conditioning device <part-num-ref name="conditioning device">80</part-num-ref>
+ can cool and/or otherwise condition the bleed air supply <part-num-ref name="bleed air supply">64</part-num-ref>
+ to render a buffer cooling air <part-num-ref name="buffer cooling air">62</part-num-ref>
+ having an acceptable temperature for buffering the environment su<confidence value="66">rr</confidence>
+ounding the bearing structures <part-num-ref name="bearing structures">38</part-num-ref>
+ and the inner shaft <part-num-ref name="inner shaft">40.</part-num-ref>
+ The conditioning device <part-num-ref name="conditioning device">80</part-num-ref>
+ could include an air- to-air heat exchanger, a fuel-to-air heat exchanger, or any other suitable heater exchanger.    </p>
+    <boundary-data type="header">
+      <confidence value="8">7</confidence>
+    </boundary-data>
+    <boundary-data type="header">67097-1741 PUS<confidence value="5">1</confidence>
+    </boundary-data>
+    <boundary-data type="header">PA-0021171-US-AA</boundary-data>
+    <p id="p-50" num="50">
+      <page-break num="8"/>
+[00046<confidence value="5">]</confidence>
+ Referring to Figure 4, the buffer cooling air <part-num-ref name="buffer cooling air">62</part-num-ref>
+ may be communicated from the conditioning device <part-num-ref name="conditioning device">80</part-num-ref>
+ to a bearing structure <part-num-ref name="bearing structure">38,</part-num-ref>
+ then axially along an outer diameter <part-num-ref name="outer diameter">82</part-num-ref>
+ of the inner shaft <part-num-ref name="inner shaft">40</part-num-ref>
+ (i.e., between the inner shaft <part-num-ref name="inner shaft">40</part-num-ref>
+ and the outer shaft 50), and then downstream to the turbine section <part-num-ref name="turbine section">28</part-num-ref>
+ to cool other bearing structures or for turbine ventilation purposes. The outer shaft <part-num-ref name="outer shaft">50,</part-num-ref>
+ which in this example is a tie shaft that interconnects the high pressure compressor <part-num-ref name="high pressure compressor">52</part-num-ref>
+ and the high pressure turbine <part-num-ref name="high pressure turbine">54,</part-num-ref>
+ isolates the inner shaft <part-num-ref name="inner shaft">40</part-num-ref>
+ from potentially hotter compressor ventilation airflow C supplied from the same or different source. The compressor ventilation airflow C may be hotter than the inner shaft <part-num-ref name="inner shaft">40</part-num-ref>
+ as a result of heat transfer with the hardware of the compressor section <part-num-ref name="compressor section">24.</part-num-ref>
+    </p>
+    <p id="p-51" num="51">
+      <confidence value="8666">[000</confidence>
+47] The buffer cooling air <part-num-ref name="buffer cooling air">62</part-num-ref>
+ may also be simultaneously communicated axially along and through an inner diameter <part-num-ref name="inner diameter">84</part-num-ref>
+ of the inner shaft <part-num-ref name="inner shaft">40</part-num-ref>
+ where the inner shaft <part-num-ref name="inner shaft">40</part-num-ref>
+ is hollow. It should be understood that the buffer cooling air <part-num-ref name="buffer cooling air">62</part-num-ref>
+ may be communicated along the outer diameter <part-num-ref name="outer diameter">82,</part-num-ref>
+ along the inner diameter <part-num-ref name="inner diameter">84,</part-num-ref>
+ or both at the same time. The buffer cooling air <part-num-ref name="buffer cooling air">62</part-num-ref>
+ may condition the bearing structures <part-num-ref name="bearing structures">38</part-num-ref>
+ and the inner and outer shafts <part-num-ref name="outer shafts">40,</part-num-ref>
+ <part-num-ref name="outer shafts 40,">50</part-num-ref>
+ as it is communicated along this path. In this example, the buffer cooling air <part-num-ref name="buffer cooling air">62</part-num-ref>
+ is communicated substantially along an entire axial length L<confidence value="5">1</confidence>
+ of the inner shaft <part-num-ref name="inner shaft">40</part-num-ref>
+ and an entire axial length L2 of the outer shaft <part-num-ref name="outer shaft">50.</part-num-ref>
+ However, the buffer cooling air <part-num-ref name="buffer cooling air">62</part-num-ref>
+ could be communicated along only portions of the axial lengths <confidence value="86">L1</confidence>
+, L2 depending on how and where the buffer cooling air <part-num-ref name="buffer cooling air">62</part-num-ref>
+ is piped to the inner shaft <part-num-ref name="inner shaft">40</part-num-ref>
+ and the outer shaft <part-num-ref name="outer shaft">50.</part-num-ref>
+    </p>
+    <p id="p-52" num="52">[0004<confidence value="66">8]</confidence>
+ Although shown schematically, the buffer cooling air <part-num-ref name="buffer cooling air">62</part-num-ref>
+ is communicated between the conditioning device <part-num-ref name="conditioning device">80,</part-num-ref>
+ the bearing structures <part-num-ref name="bearing structures">38</part-num-ref>
+ and the inner and outer shafts <part-num-ref name="outer shafts">40,</part-num-ref>
+ <part-num-ref name="outer shafts 40,">50</part-num-ref>
+ via buffer tubing, conduits, or other passageways. Such tubing, conduits and/or passageways could be routed throughout the gas turbine engine <part-num-ref name="gas turbine engine">20.</part-num-ref>
+ The type, location and configuration of such tubing, conduits and/or passageways are not intended to limit this disclosure.    </p>
+    <p id="p-53" num="53">[00049<confidence value="5">]</confidence>
+ The buffer system <part-num-ref name="buffer system">60</part-num-ref>
+ may also include a controller <part-num-ref name="controller">70.</part-num-ref>
+ The controller <part-num-ref name="controller">70</part-num-ref>
+ can be programmed to selectively command the communication of buffer cooling air <part-num-ref name="buffer cooling air">62</part-num-ref>
+ during certain operating conditions. The controller <part-num-ref name="controller">70</part-num-ref>
+ may also potentially generate a signal to command operation of the conditioning device <part-num-ref name="conditioning device">80</part-num-ref>
+ and/or a source-switching valve. Also, although shown as a separate feature, the controller functionality could be incorporated into the conditioning device <part-num-ref name="conditioning device">80.</part-num-ref>
+ The buffer <boundary-data type="header">
+        <confidence value="8">8</confidence>
+      </boundary-data>
+      <page-break num="9"/>
+      <boundary-data type="header">67097-1741 PUS<confidence value="5">1</confidence>
+      </boundary-data>
+      <boundary-data type="header">PA-0021171-US-AA</boundary-data>
+system <part-num-ref name="buffer system">60</part-num-ref>
+ is operable to communicate buffer cooling air <part-num-ref name="communicate buffer cooling air">162</part-num-ref>
+ for responding to any engine operating condition.    </p>
+    <p id="p-54" num="54">
+      <confidence value="8555555">[00050]</confidence>
+ Figure 5 illustrates another example buffer system <part-num-ref name="illustrates another example buffer system">160</part-num-ref>
+ that may be used to supply a buffer cooling air <part-num-ref name="buffer cooling air">162</part-num-ref>
+ to pressurize a bearing structure <part-num-ref name="bearing structure">38</part-num-ref>
+ and cool the inner and outer shafts <part-num-ref name="outer shafts">40,</part-num-ref>
+ <part-num-ref name="outer shafts 40,">50</part-num-ref>
+ of the gas turbine engine <part-num-ref name="gas turbine engine">20.</part-num-ref>
+ In this example, the buffer system <part-num-ref name="buffer system">160</part-num-ref>
+ is a multi-source buffer system that includes a first bleed air supply <part-num-ref name="first bleed air supply">164</part-num-ref>
+ and a second bleed air supply <part-num-ref name="second bleed air supply">166.</part-num-ref>
+ In the exemplary embodiment, the first bleed air supply <part-num-ref name="first bleed air supply">164</part-num-ref>
+ is a low pressure bleed air supply and the second bleed air supply <part-num-ref name="second bleed air supply">166</part-num-ref>
+ is a high pressure bleed air supply that includes a pressure that is greater than the pressure of the first bleed air supply <part-num-ref name="first bleed air supply">164.</part-num-ref>
+    </p>
+    <p id="p-55" num="55">[00051<confidence value="5">]</confidence>
+ The first bleed air supply <part-num-ref name="first bleed air supply">164</part-num-ref>
+ may be sourced from the fan section <part-num-ref name="fan section">22,</part-num-ref>
+ the low pressure compressor <part-num-ref name="low pressure compressor">44</part-num-ref>
+ or the high pressure compressor <part-num-ref name="high pressure compressor">52.</part-num-ref>
+ In the illustrated non-limiting example, the first bleed air supply <part-num-ref name="first bleed air supply">164</part-num-ref>
+ is sourced from an upstream stage of the high pressure compressor <part-num-ref name="high pressure compressor">52.</part-num-ref>
+ However, the first bleed air supply <part-num-ref name="first bleed air supply">164</part-num-ref>
+ could be sourced from any location that is upstream from the second bleed air supply <part-num-ref name="second bleed air supply">166.</part-num-ref>
+ The second bleed air supply <part-num-ref name="second bleed air supply">166</part-num-ref>
+ may be sourced from the high pressure compressor <part-num-ref name="high pressure compressor">52,</part-num-ref>
+ such as from a middle or downstream stage of the high pressure compressor <part-num-ref name="high pressure compressor">52.</part-num-ref>
+ The second bleed air supply <part-num-ref name="second bleed air supply">166</part-num-ref>
+ could also be sourced from the low pressure compressor <part-num-ref name="low pressure compressor">44</part-num-ref>
+ or the fan section <part-num-ref name="fan section">22</part-num-ref>
+ depending on where the first bleed air supply <part-num-ref name="first bleed air supply">164</part-num-ref>
+ is sourced from.    </p>
+    <p id="p-56" num="56">[00052<confidence value="5">]</confidence>
+ The buffer system <part-num-ref name="buffer system">160</part-num-ref>
+ may also include a valve <part-num-ref name="valve">168</part-num-ref>
+ that is in communication with both the first bleed air supply <part-num-ref name="first bleed air supply">164</part-num-ref>
+ and the second bleed air supply <part-num-ref name="second bleed air supply">166.</part-num-ref>
+ Although shown schematically, the first bleed air supply <part-num-ref name="first bleed air supply">164</part-num-ref>
+ and the second bleed air supply <part-num-ref name="second bleed air supply">166</part-num-ref>
+ can be in fluid communication with the valve <part-num-ref name="valve">168</part-num-ref>
+ via buffer tubing, conduits, or other passageways.    </p>
+    <p id="p-57" num="57">[00053<confidence value="5">1</confidence>
+ In the exemplary embodiment, the valve <part-num-ref name="valve">168</part-num-ref>
+ may select between the first bleed air supply <part-num-ref name="first bleed air supply">164</part-num-ref>
+ and the second bleed air supply <part-num-ref name="second bleed air supply">166</part-num-ref>
+ to communicate a buffer cooling air <part-num-ref name="buffer cooling air">162</part-num-ref>
+ having a desired temperature and pressure to desired portions of the gas turbine engine <part-num-ref name="gas turbine engine">20.</part-num-ref>
+ The valve <part-num-ref name="valve">168</part-num-ref>
+ communicates either the first bleed air supply <part-num-ref name="first bleed air supply">164</part-num-ref>
+ or the second bleed air supply <part-num-ref name="second bleed air supply">168</part-num-ref>
+ to a conditioning device <part-num-ref name="conditioning device">180</part-num-ref>
+ to cool the air supply and render the buffer cooling air <part-num-ref name="buffer cooling air">162.</part-num-ref>
+    </p>
+    <p id="p-58" num="58">[00054<confidence value="5">]</confidence>
+ The valve <part-num-ref name="valve">168</part-num-ref>
+ can be a passive valve or a controller base valve. A passive valve operates like a pressure regulator that can switch between two or more sources without being commanded to do so by a controller, such as an engine control <boundary-data type="header">
+        <confidence value="8">9</confidence>
+      </boundary-data>
+      <page-break num="10"/>
+      <boundary-data type="header">67097-1741 PUS<confidence value="5">1</confidence>
+      </boundary-data>
+      <boundary-data type="header">PA-0021171-US-AA</boundary-data>
+(EEC). The valve <part-num-ref name="valve">168</part-num-ref>
+ of this example uses only a single input which is directly measured to switch between the first bleed air supply <part-num-ref name="first bleed air supply">164</part-num-ref>
+ and the second bleed air supply <part-num-ref name="second bleed air supply">661.</part-num-ref>
+    </p>
+    <p id="p-59" num="59">
+      <confidence value="866666">[00055</confidence>
+] The valve <part-num-ref name="valve">168</part-num-ref>
+ could also be a controller based valve. For example, the buffer system <part-num-ref name="buffer system">160</part-num-ref>
+ could include a controller <part-num-ref name="controller">170</part-num-ref>
+ in communication with the valve <part-num-ref name="valve">168</part-num-ref>
+ for selecting between the first bleed air supply <part-num-ref name="first bleed air supply">164</part-num-ref>
+ and the second bleed air supply <part-num-ref name="second bleed air supply">166.</part-num-ref>
+ The controller <part-num-ref name="controller">170</part-num-ref>
+ is programmed with the necessary logic for selecting between the first bleed air supply <part-num-ref name="first bleed air supply">164</part-num-ref>
+ and the second bleed air supply <part-num-ref name="second bleed air supply">166</part-num-ref>
+ in response to detecting a pre-defined power condition of the gas turbine engine <part-num-ref name="gas turbine engine">20.</part-num-ref>
+ The controller <part-num-ref name="controller">170</part-num-ref>
+ could also be programmed with multiple inputs.    </p>
+    <p id="p-60" num="60">
+      <confidence value="866666">[00056</confidence>
+] The determination of whether to communicate the first bleed air supply <part-num-ref name="first bleed air supply">164</part-num-ref>
+ or the second bleed air supply <part-num-ref name="second bleed air supply">166</part-num-ref>
+ as the buffer cooling air <part-num-ref name="buffer cooling air">162</part-num-ref>
+ is based on a power condition of the gas turbine engine <part-num-ref name="gas turbine engine">20.</part-num-ref>
+ The term "power condition" as used in this disclosure generally refers to an operability condition of the gas turbine engine <part-num-ref name="gas turbine engine">20.</part-num-ref>
+ Gas turbine engine power conditions can include low power conditions and high power conditions. Example low power conditions include, but are not limited to, ground operation, ground idle and descent idle. Example high power conditions include, but are not limited to, takeoff, climb, and cruise conditions. It should be understood that other power conditions are also contemplated as within the scope of this disclosure.    </p>
+    <p id="p-61" num="61">[00057] In one exemplary embodiment, the valve <part-num-ref name="valve">168</part-num-ref>
+ communicates the first bleed air supply <part-num-ref name="first bleed air supply">164</part-num-ref>
+ (which is a relatively lower pressure bleed air supply) to the conditioning device <part-num-ref name="conditioning device">180</part-num-ref>
+ in response to identifying a high power condition of a gas turbine engine <part-num-ref name="gas turbine engine">20.</part-num-ref>
+ The second bleed air supply <part-num-ref name="second bleed air supply">166</part-num-ref>
+ (which is a relatively higher pressure bleed air supply) is selected by the valve <part-num-ref name="valve">168</part-num-ref>
+ and communicated to the conditioning device <part-num-ref name="conditioning device">180</part-num-ref>
+ in response to detecting a low power condition of the gas turbine engine <part-num-ref name="gas turbine engine">20.</part-num-ref>
+ Both sources of bleed air are intended to maintain the same minimum pressure delta across the bearing compartment seals. Low power conditions require a higher pressure stage source to maintain adequate pressure differential, while high power conditions can meet requirements with a lower stage pressure source. Use of the lowest possible compressor stage can to meet the pressure requirements and minimize supply temperature and any negative performance impact to the gas turbine engine <part-num-ref name="gas turbine engine">20.</part-num-ref>
+    </p>
+    <boundary-data type="header">
+      <confidence value="88">10</confidence>
+    </boundary-data>
+    <boundary-data type="header">67097-1741 PUS<confidence value="5">1</confidence>
+    </boundary-data>
+    <boundary-data type="header">PA-0021171-US-AA</boundary-data>
+    <p id="p-62" num="62">
+      <page-break num="11"/>
+      <confidence value="8666666">[00058]</confidence>
+ The conditioning device <part-num-ref name="conditioning device">180</part-num-ref>
+ of the buffer system <part-num-ref name="buffer system">160</part-num-ref>
+ could include a heat exchanger or an ejector. An ejector adds pressure (using a small amount of the second bleed air supply <part-num-ref name="second bleed air supply">166)</part-num-ref>
+ to the first bleed air supply <part-num-ref name="first bleed air supply">164</part-num-ref>
+ to prepare the buffer supply air <part-num-ref name="buffer supply air">162.</part-num-ref>
+    </p>
+    <p id="p-63" num="63">[00059<confidence value="5">]</confidence>
+ Although the different examples have a specific component shown in the illustrations, embodiments of this disclosure are not limited to those particular combinations. It is possible to use some of the components or features from one of the examples in combination with features or components from another one of the examples.    </p>
+    <p id="p-64" num="64">
+      <confidence value="8666655">[0006o]</confidence>
+ The foregoing description shall be interpreted as illustrative and not in any limiting sense. A worker of ordinary skill in the art would understand that certain modifications could come within the scope of this disclosure. For these reasons, the following claims should be studied to determine the true scope and content of this disclosure.    </p>
+    <boundary-data type="header">
+      <confidence value="88">11</confidence>
+    </boundary-data>
+  </description>
+</us-patent-application>
+

applicant/13515664.xml

@@ -0,0 +1 @@
+<?xml version="1.0" encoding="utf-8"?><pat:SpecificationDocument xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:pat="urn:us:gov:doc:uspto:patent" xmlns:ent="urn:us:gov:doc:uspto:enterprise" xmlns="urn:us:gov:doc:uspto:patent" xmlns:tbl="http://www.oasis-open.org/tables/exchange/1.0" xmlns:com="http://www.wipo.int/standards/XMLSchema/Common/1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XML_SCHEMAS/V1_3/SpecificationDocument_1_0.xsd" pat:instanceFileName="13515664.04-02-2013.HF1H1HETPXXIFW3.SPEC.XML" pat:id="HF1H1HETPXXIFW3"><pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001"><pat:ApplicationHeaderDetails><pat:ApplicationNumber>13515664</pat:ApplicationNumber></pat:ApplicationHeaderDetails><pat:PageTotalQuantity>4</pat:PageTotalQuantity><pat:ParagraphTotalQuantity>12</pat:ParagraphTotalQuantity></pat:DocumentHeaderDetails><pat:MailRoomDate>2013-04-02</pat:MailRoomDate><pat:DocumentCreateDateText>2014-09-24</pat:DocumentCreateDateText><pat:DocumentTitle>SPECIFICATION DOCUMENT</pat:DocumentTitle><pat:Specification><?PageStart number='1'?><pat:P pat:pNumber="1" pat:id="p-1"><pat:BoundaryData><pat:HeaderText>SOUTHWELL et al.</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>App<pat:OCRConfidenceData pat:levelNumber='5'>l</pat:OCRConfidenceData>. No. 13/515,664</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>April 2, 2013</pat:HeaderText></pat:BoundaryData>Amendments to the S<pat:OCRConfidenceData pat:levelNumber='5'>p</pat:OCRConfidenceData>ecification: </pat:P><pat:P pat:pNumber="2" pat:id="p-2">Please replace paragraph [040] with the following amended paragraph: </pat:P><pat:P pat:pNumber="3" pat:id="p-3">[040] A <pat:PartName pat:idref='PN-00001'>particularly preferred R-substituted aromatic thioether triaryl sulfonium tetrakis(pentaf<pat:OCRConfidenceData pat:levelNumber='5'>l</pat:OCRConfidenceData>uorophenyl)borate cationic photoinitiator is <pat:OCRConfidenceData pat:levelNumber='511'>tea</pat:OCRConfidenceData>tris</pat:PartName><pat:OCRConfidenceData pat:levelNumber='5'>(</pat:OCRConfidenceData><pat:PartNumber pat:id='PN-00001'><pat:OCRConfidenceData pat:levelNumber='8'>4</pat:OCRConfidenceData></pat:PartNumber><pat:OCRConfidenceData pat:levelNumber='8588'>-(4-</pat:OCRConfidenceData> acet<pat:OCRConfidenceData pat:levelNumber='545'>ylp</pat:OCRConfidenceData>hen<pat:OCRConfidenceData pat:levelNumber='5'>y</pat:OCRConfidenceData>lthio<pat:OCRConfidenceData pat:levelNumber='66'>)p</pat:OCRConfidenceData>hen<pat:OCRConfidenceData pat:levelNumber='686'>yl)</pat:OCRConfidenceData>sulfonium tetrakis(<pat:OCRConfidenceData pat:levelNumber='5'>p</pat:OCRConfidenceData>entafluoro<pat:OCRConfidenceData pat:levelNumber='5'>p</pat:OCRConfidenceData>hen<pat:OCRConfidenceData pat:levelNumber='686'>yl)</pat:OCRConfidenceData>borate. <pat:PartName pat:idref='PN-00002'><pat:OCRConfidenceData pat:levelNumber='568'>F4s</pat:OCRConfidenceData></pat:PartName><pat:OCRConfidenceData pat:levelNumber='6'>{</pat:OCRConfidenceData><pat:PartNumber pat:id='PN-00002'><pat:OCRConfidenceData pat:levelNumber='8'>4</pat:OCRConfidenceData></pat:PartNumber><pat:OCRConfidenceData pat:levelNumber='8588'>-(4-</pat:OCRConfidenceData> <pat:PartName pat:idref='PN-00003'><pat:OCRConfidenceData pat:levelNumber='511'>tea</pat:OCRConfidenceData>tris</pat:PartName><pat:OCRConfidenceData pat:levelNumber='5'>(</pat:OCRConfidenceData><pat:PartNumber pat:id='PN-00003'><pat:OCRConfidenceData pat:levelNumber='8'>4</pat:OCRConfidenceData></pat:PartNumber><pat:OCRConfidenceData pat:levelNumber='8588'>-(4-</pat:OCRConfidenceData> <pat:PartName pat:idref='PN-00004'>acet<pat:OCRConfidenceData pat:levelNumber='545'>ylp</pat:OCRConfidenceData>hen<pat:OCRConfidenceData pat:levelNumber='5'>y</pat:OCRConfidenceData>lthio<pat:OCRConfidenceData pat:levelNumber='66'>)p</pat:OCRConfidenceData>hen<pat:OCRConfidenceData pat:levelNumber='686'>yl)</pat:OCRConfidenceData>sulfonium tetrakis(<pat:OCRConfidenceData pat:levelNumber='5'>p</pat:OCRConfidenceData>entafluoro<pat:OCRConfidenceData pat:levelNumber='5'>p</pat:OCRConfidenceData>hen<pat:OCRConfidenceData pat:levelNumber='686'>yl)</pat:OCRConfidenceData>borate is known commercially as IRGACURE<pat:OCRConfidenceData pat:levelNumber='2'>*</pat:OCRConfidenceData> PAG</pat:PartName>-<pat:PartNumber pat:id='PN-00004'>290</pat:PartNumber> (formerly known by the <pat:PartName pat:idref='PN-00005'>development code <pat:OCRConfidenceData pat:levelNumber='885'>GSI</pat:OCRConfidenceData>D4480</pat:PartName>-<pat:PartNumber pat:id='PN-00005'>1</pat:PartNumber>) and is available from Ciba/BAS<pat:OCRConfidenceData pat:levelNumber='68'>F.</pat:OCRConfidenceData> </pat:P><pat:P pat:pNumber="4" pat:id="p-4">Please replace paragraph [041] with the following amended paragraph: </pat:P><pat:P pat:pNumber="5" pat:id="p-5">[041] The inventors have also discovered that an R-substituted aromatic thioether triaryl sulfonium tetrakis(pentafluorophenyl)borate cationic photoinitiator, for instance, <pat:PartName pat:idref='PN-00006'><pat:OCRConfidenceData pat:levelNumber='511'>tea</pat:OCRConfidenceData>tris</pat:PartName><pat:OCRConfidenceData pat:levelNumber='5'>(</pat:OCRConfidenceData><pat:PartNumber pat:id='PN-00006'><pat:OCRConfidenceData pat:levelNumber='8'>4</pat:OCRConfidenceData></pat:PartNumber><pat:OCRConfidenceData pat:levelNumber='8588'>-(4-</pat:OCRConfidenceData> acet<pat:OCRConfidenceData pat:levelNumber='545'>ylp</pat:OCRConfidenceData>hen<pat:OCRConfidenceData pat:levelNumber='5'>y</pat:OCRConfidenceData>lthio<pat:OCRConfidenceData pat:levelNumber='66'>)p</pat:OCRConfidenceData>hen<pat:OCRConfidenceData pat:levelNumber='686'>yl)</pat:OCRConfidenceData>sulfonium tetrakis(<pat:OCRConfidenceData pat:levelNumber='5'>p</pat:OCRConfidenceData>entafluoro<pat:OCRConfidenceData pat:levelNumber='5'>p</pat:OCRConfidenceData>hen<pat:OCRConfidenceData pat:levelNumber='686'>yl)</pat:OCRConfidenceData>borate, is much more thermally- stable than other cationic photoinitiators. The improved thermal- stability allows liquid radiation curable resins for additive <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='888'>-2-</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>2144784</pat:HeaderText></pat:BoundaryData><?PageStart number='2'?><pat:BoundaryData><pat:HeaderText>SOUTHWELL et al.</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>App<pat:OCRConfidenceData pat:levelNumber='5'>l</pat:OCRConfidenceData>. No. 13/515,664</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>April 2, 2013</pat:HeaderText></pat:BoundaryData>fabrication incorporating a triaryl sulfonium tetrakis(pentafluorophenyl)borate cationic photoinitiator instead of other conventional cationic photoinitiators to retain their viscosity at elevated temperatures for long periods of time. </pat:P><pat:P pat:pNumber="6" pat:id="p-6">Please replace paragraph [042] with the following amended paragraph: </pat:P><pat:P pat:pNumber="7" pat:id="p-7">[042] Furthermore, the inventors have surprisingly found excellent performance in photo-stability of a liquid radiation curable resin for additive fabrication that comprises an R- substituted aromatic thioether triaryl sulfonium tetrakis(pentafluorophenyl)borate cationic photoinitiator, <pat:PartName pat:idref='PN-00007'>for instance <pat:OCRConfidenceData pat:levelNumber='5'>t</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='511'>tea</pat:OCRConfidenceData>tris</pat:PartName><pat:OCRConfidenceData pat:levelNumber='5'>(</pat:OCRConfidenceData><pat:PartNumber pat:id='PN-00007'><pat:OCRConfidenceData pat:levelNumber='8'>4</pat:OCRConfidenceData></pat:PartNumber><pat:OCRConfidenceData pat:levelNumber='8588'>-(4-</pat:OCRConfidenceData> acet<pat:OCRConfidenceData pat:levelNumber='545'>ylp</pat:OCRConfidenceData>hen<pat:OCRConfidenceData pat:levelNumber='5'>y</pat:OCRConfidenceData>lthio<pat:OCRConfidenceData pat:levelNumber='66'>)p</pat:OCRConfidenceData>hen<pat:OCRConfidenceData pat:levelNumber='686'>yl)</pat:OCRConfidenceData>sulfonium tetrakis(<pat:OCRConfidenceData pat:levelNumber='5'>p</pat:OCRConfidenceData>entafluoro<pat:OCRConfidenceData pat:levelNumber='5'>p</pat:OCRConfidenceData>hen<pat:OCRConfidenceData pat:levelNumber='686'>yl)</pat:OCRConfidenceData>borate, in combination with high amounts of inorganic filler, such as silica-based filler. The interaction with light and inorganic filler, such as silica filler, creates added stability problems in highly filled liquid radiation curable resins for additive fabrication. However, use of R- substituted aromatic thioether triaryl sulfonium tetrakis(pentafluorophenyl)borate cationic photoinitiator in a liquid radiation curable resin enables the resin to attain comparable critical energy (Ec, E<pat:OCRConfidenceData pat:levelNumber='66'>10</pat:OCRConfidenceData>) and depth of penetration (Dp) values to a resin incorporating a conventional cationic photoinitiator while achieving much better photo-stability. </pat:P><pat:P pat:pNumber="8" pat:id="p-8"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='888'>-3-</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>2144784</pat:HeaderText></pat:BoundaryData><?PageStart number='3'?><pat:BoundaryData><pat:HeaderText>SOUTHWELL et al.</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>App<pat:OCRConfidenceData pat:levelNumber='5'>l</pat:OCRConfidenceData>. No. 13/515,664</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>April 2, 2013</pat:HeaderText></pat:BoundaryData>Please replace paragraph [048] with the following amended paragraph: </pat:P><pat:P pat:pNumber="9" pat:id="p-9">[048] Preferred mixtures of cationic photoinitiators include a mixture of: bis[4-diphenylsulfoniumphenyl]sulfide bishexafluoroantimonate; <pat:PartName pat:idref='PN-00008'>thiophenoxyphenylsulfonium hexafluoroantimonate (available as Chivacure</pat:PartName> <pat:PartNumber pat:id='PN-00008'>1176</pat:PartNumber> <pat:PartName pat:idref='PN-00009'>from Chitec);<pat:OCRConfidenceData pat:levelNumber='2'>t</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='511'>tea</pat:OCRConfidenceData>tris</pat:PartName><pat:OCRConfidenceData pat:levelNumber='5'>(</pat:OCRConfidenceData><pat:PartNumber pat:id='PN-00009'><pat:OCRConfidenceData pat:levelNumber='8'>4</pat:OCRConfidenceData></pat:PartNumber><pat:OCRConfidenceData pat:levelNumber='8588'>-(4-</pat:OCRConfidenceData> <pat:PartName pat:idref='PN-00010'>acet<pat:OCRConfidenceData pat:levelNumber='545'>ylp</pat:OCRConfidenceData>hen<pat:OCRConfidenceData pat:levelNumber='5'>y</pat:OCRConfidenceData>lthio<pat:OCRConfidenceData pat:levelNumber='66'>)p</pat:OCRConfidenceData>hen<pat:OCRConfidenceData pat:levelNumber='686'>yl)</pat:OCRConfidenceData>sulfonium tetrakis(<pat:OCRConfidenceData pat:levelNumber='5'>p</pat:OCRConfidenceData>entafluoro<pat:OCRConfidenceData pat:levelNumber='5'>p</pat:OCRConfidenceData>hen<pat:OCRConfidenceData pat:levelNumber='686'>yl)</pat:OCRConfidenceData>borate (Irgacure PAG</pat:PartName>-<pat:PartNumber pat:id='PN-00010'>290</pat:PartNumber> or <pat:PartName pat:idref='PN-00011'><pat:OCRConfidenceData pat:levelNumber='885'>GSI</pat:OCRConfidenceData>D4480</pat:PartName>-<pat:PartNumber pat:id='PN-00011'>1</pat:PartNumber> from Ciba/BAS<pat:OCRConfidenceData pat:levelNumber='5'>F</pat:OCRConfidenceData>), iodonium, <pat:PartName pat:idref='PN-00012'>[4-</pat:PartName>(<pat:PartNumber pat:id='PN-00012'>1</pat:PartNumber>- <pat:PartName pat:idref='PN-00013'>methylethyl<pat:OCRConfidenceData pat:levelNumber='8'>)</pat:OCRConfidenceData>phenyl<pat:OCRConfidenceData pat:levelNumber='8'>]</pat:OCRConfidenceData></pat:PartName>(<pat:PartNumber pat:id='PN-00013'>4</pat:PartNumber>-methyl phenyl) <pat:OCRConfidenceData pat:levelNumber='88'>-,</pat:OCRConfidenceData> <pat:PartName pat:idref='PN-00014'>tetrakis(pentafluorophenyl)borate (available as Rhodorsil</pat:PartName> <pat:PartNumber pat:id='PN-00014'>2074</pat:PartNumber> from Rhodia), <pat:PartName pat:idref='PN-00015'>4-[4-</pat:PartName>(<pat:PartNumber pat:id='PN-00015'>2</pat:PartNumber>-chlorobenzoyl)phenylthio]phenylbis(4- <pat:PartName pat:idref='PN-00016'>fluorophenyl)sulfon- ium hexafluoroantimonate (as SP</pat:PartName>-<pat:PartNumber pat:id='PN-00016'>172</pat:PartNumber>) and <pat:PartName pat:idref='PN-00017'>SP</pat:PartName>-<pat:PartNumber pat:id='PN-00017'>300</pat:PartNumber> (both available from Adeka). </pat:P><pat:P pat:pNumber="10" pat:id="p-10">Please replace paragraph [097] with the following amended paragraph: </pat:P><pat:P pat:pNumber="11" pat:id="p-11">[097] As mentioned above, the inventors have found a surprising combination of a triaryl sulfonium tetrakis(pentafluorophenyl)borate cationic photoinitiator, preferably, <pat:PartName pat:idref='PN-00018'><pat:OCRConfidenceData pat:levelNumber='511'>tea</pat:OCRConfidenceData>tris</pat:PartName><pat:OCRConfidenceData pat:levelNumber='5'>(</pat:OCRConfidenceData><pat:PartNumber pat:id='PN-00018'><pat:OCRConfidenceData pat:levelNumber='8'>4</pat:OCRConfidenceData></pat:PartNumber><pat:OCRConfidenceData pat:levelNumber='8588'>-(4-</pat:OCRConfidenceData> acet<pat:OCRConfidenceData pat:levelNumber='545'>ylp</pat:OCRConfidenceData>hen<pat:OCRConfidenceData pat:levelNumber='5'>y</pat:OCRConfidenceData>lthio<pat:OCRConfidenceData pat:levelNumber='66'>)p</pat:OCRConfidenceData>hen<pat:OCRConfidenceData pat:levelNumber='686'>yl)</pat:OCRConfidenceData>sulfonium tetrakis(pentafluorophenyl)borate, and high amounts of inorganic filler, preferably silica filler which comprises greater <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='888'>-4-</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>2144784</pat:HeaderText></pat:BoundaryData><?PageStart number='4'?><pat:BoundaryData><pat:HeaderText>SOUTHWELL et al.</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>App<pat:OCRConfidenceData pat:levelNumber='5'>l</pat:OCRConfidenceData>. No. 13/515,664</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>April 2, 2013</pat:HeaderText></pat:BoundaryData>than 80 wt <pat:OCRConfidenceData pat:levelNumber='5'>%</pat:OCRConfidenceData>, <pat:PartName pat:idref='PN-00019'>more preferably</pat:PartName> <pat:PartNumber pat:id='PN-00019'>90</pat:PartNumber> wt <pat:OCRConfidenceData pat:levelNumber='5'>%</pat:OCRConfidenceData>, <pat:PartName pat:idref='PN-00020'>more preferably</pat:PartName> <pat:PartNumber pat:id='PN-00020'>95</pat:PartNumber> wt <pat:OCRConfidenceData pat:levelNumber='5'>%</pat:OCRConfidenceData> of silica. The combination yields liquid radiation curable resins for additive fabrication that attain excellent photo-stability and thermal-stability. </pat:P><pat:P pat:pNumber="12" pat:id="p-12"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='888'>-5-</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>2144784</pat:HeaderText></pat:BoundaryData></pat:P></pat:Specification></pat:SpecificationDocument>

applicant/13641254.xml

@@ -0,0 +1 @@
+<?xml version="1.0" encoding="utf-8"?><pat:SpecificationDocument xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:pat="urn:us:gov:doc:uspto:patent" xmlns:ent="urn:us:gov:doc:uspto:enterprise" xmlns="urn:us:gov:doc:uspto:patent" xmlns:tbl="http://www.oasis-open.org/tables/exchange/1.0" xmlns:com="http://www.wipo.int/standards/XMLSchema/Common/1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XML_SCHEMAS/V1_3/SpecificationDocument_1_0.xsd" pat:instanceFileName="13641254.02-10-2015.I5ZFVJ2IPXXIFW3.SPEC.XML" pat:id="I5ZFVJ2IPXXIFW3"><pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001"><pat:ApplicationHeaderDetails><pat:ApplicationNumber>13641254</pat:ApplicationNumber></pat:ApplicationHeaderDetails><pat:PageTotalQuantity>1</pat:PageTotalQuantity><pat:ParagraphTotalQuantity>5</pat:ParagraphTotalQuantity></pat:DocumentHeaderDetails><pat:MailRoomDate>2015-02-10</pat:MailRoomDate><pat:Specification><?PageStart number='1'?><pat:P pat:pNumber="1" pat:id="p-1"><pat:BoundaryData><pat:HeaderText>Amendment and Response</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Serial No: 13/641,254</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Docket No.: 324.<pat:OCRConfidenceData pat:levelNumber='666'>000</pat:OCRConfidenceData>3USWO</pat:HeaderText></pat:BoundaryData>Amendments to the Specification Please amend the <pat:PartName pat:idref='PN-00001'>paragraph beginning on page</pat:PartName> <pat:PartNumber pat:id='PN-00001'>11</pat:PartNumber>, <pat:PartName pat:idref='PN-00002'>line</pat:PartName> <pat:PartNumber pat:id='PN-00002'>12</pat:PartNumber> as follows: </pat:P><pat:P pat:pNumber="2" pat:id="p-2">During operation, the gas to be dried first flows through the <pat:PartName pat:idref='PN-00003'>gas-gas area</pat:PartName> <pat:PartNumber pat:id='PN-00003'>17</pat:PartNumber> through the <pat:PartName pat:idref='PN-00004'>first passages</pat:PartName> <pat:PartNumber pat:id='PN-00004'>25</pat:PartNumber> and then through the <pat:PartName pat:idref='PN-00005'>gas-refrigerant agent area</pat:PartName> <pat:PartNumber pat:id='PN-00005'>18</pat:PartNumber>. In the <pat:PartName pat:idref='PN-00006'>gas-refrigerant agent area</pat:PartName> <pat:PartNumber pat:id='PN-00006'>18</pat:PartNumber>, the gas to be dried flows past both the <pat:PartName pat:idref='PN-00007'>meander-shaped refrigerant agent tube</pat:PartName> <pat:PartNumber pat:id='PN-00007'>20</pat:PartNumber> and the <pat:PartName pat:idref='PN-00008'>cold accumulator partial spaces</pat:PartName> <pat:PartNumber pat:id='PN-00008'>23</pat:PartNumber>. After flowing through the <pat:PartName pat:idref='PN-00009'>gas-refrigerant agent area</pat:PartName> <pat:PartNumber pat:id='PN-00009'>18</pat:PartNumber>, the gas to be dried flows through a <pat:PartName pat:idref='PN-00010'>deflecting area</pat:PartName> <pat:PartNumber pat:id='PN-00010'><pat:OCRConfidenceData pat:levelNumber='54'>24</pat:OCRConfidenceData></pat:PartNumber> in which a precipitating condensate can be separated and discharged through a <pat:PartName pat:idref='PN-00011'>condensate drain</pat:PartName> <pat:PartNumber pat:id='PN-00011'>2<pat:OCRConfidenceData pat:levelNumber='4'>4</pat:OCRConfidenceData></pat:PartNumber> 26. The gas to be dried continues to flow from the <pat:PartName pat:idref='PN-00012'>deflecting area</pat:PartName> <pat:PartNumber pat:id='PN-00012'><pat:OCRConfidenceData pat:levelNumber='55'>24</pat:OCRConfidenceData></pat:PartNumber> 27 via an <pat:PartName pat:idref='PN-00013'>inlet</pat:PartName> <pat:PartNumber pat:id='PN-00013'>28</pat:PartNumber> <pat:PartName pat:idref='PN-00014'>through second passages</pat:PartName> <pat:PartNumber pat:id='PN-00014'>29</pat:PartNumber> in the <pat:PartName pat:idref='PN-00015'>gas-gas area</pat:PartName> <pat:PartNumber pat:id='PN-00015'>17</pat:PartNumber> (in a counter-flow to the inflowing gas) to an <pat:PartName pat:idref='PN-00016'>outlet</pat:PartName> <pat:PartNumber pat:id='PN-00016'>30</pat:PartNumber>. The gas to be dried can be supplied via a <pat:PartName pat:idref='PN-00017'>feed line</pat:PartName> <pat:PartNumber pat:id='PN-00017'>31</pat:PartNumber>. </pat:P><pat:P pat:pNumber="3" pat:id="p-3">Please amend the <pat:PartName pat:idref='PN-00018'>paragraph beginning on page</pat:PartName> <pat:PartNumber pat:id='PN-00018'>11</pat:PartNumber>, <pat:PartName pat:idref='PN-00019'>line</pat:PartName> <pat:PartNumber pat:id='PN-00019'>23</pat:PartNumber> as follows: </pat:P><pat:P pat:pNumber="4" pat:id="p-4">The heat exchanger as per <pat:OCRConfidenceData pat:levelNumber='5'>F</pat:OCRConfidenceData>igs. 2 and 3 as a whole is of a sandwiched construction, wherein one of the <pat:PartName pat:idref='PN-00020'>second passages</pat:PartName>-<pat:PartNumber pat:id='PN-00020'><pat:OCRConfidenceData pat:levelNumber='6'>2</pat:OCRConfidenceData></pat:PartNumber><pat:OCRConfidenceData pat:levelNumber='666'>-8-</pat:OCRConfidenceData> 29 extends in a first, third and fifth layer between each of two plates within the <pat:PartName pat:idref='PN-00021'>gas-gas area</pat:PartName> <pat:PartNumber pat:id='PN-00021'>17</pat:PartNumber>, and in each case one of the <pat:PartName pat:idref='PN-00022'>meander-shaped refrigerant agent tubes</pat:PartName> <pat:PartNumber pat:id='PN-00022'>20</pat:PartNumber> is provided within the <pat:PartName pat:idref='PN-00023'>gas-refrigerant agent area</pat:PartName> <pat:PartNumber pat:id='PN-00023'>18</pat:PartNumber> <pat:PartName pat:idref='PN-00024'>with cold accumulator subspaces</pat:PartName> <pat:PartNumber pat:id='PN-00024'>23</pat:PartNumber> being arranged between the <pat:PartName pat:idref='PN-00025'>longitudinal sections</pat:PartName> <pat:PartNumber pat:id='PN-00025'>22</pat:PartNumber> of the <pat:PartName pat:idref='PN-00026'>refrigerant agent tube</pat:PartName> <pat:PartNumber pat:id='PN-00026'>20</pat:PartNumber>. One of the <pat:PartName pat:idref='PN-00027'>first passages</pat:PartName> <pat:PartNumber pat:id='PN-00027'>25</pat:PartNumber> for the inflowing gas to be dried extends in each of a second and fourth layer. The arrangement can basically be of any other configuration, for instance at least three layers of first passages and at least two layers of second passages can be provided. In general, an alternating arrangement of first and second passages is preferred. </pat:P><pat:P pat:pNumber="5" pat:id="p-5"><pat:BoundaryData><pat:HeaderText>Page 2 of 19</pat:HeaderText></pat:BoundaryData></pat:P></pat:Specification></pat:SpecificationDocument>

applicant/13652181.xml

@@ -0,0 +1,335 @@
+<?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" file="13652181.2012-10-15.H8C4Z67FPXXIFW3.SPEC.XML">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>13652181</doc-number>
+        <date>2012-10-15</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <boundary-data type="header">Attorney Docket No. 65662-80<confidence value="8888858">11.US01</confidence>
+    </boundary-data>
+    <heading id="h-1">SYSTEM AND METHOD FOR COMBINING DATA FROM MULTIPLE DEPTH</heading>
+    <heading id="h-2">CAMERAS</heading>
+    <heading id="h-3">BACKGROUND</heading>
+    <p id="p-1" num="1">[0001<confidence value="5">]</confidence>
+    Depth cameras acquire depth images of their environments at interactive, high frame rates. The depth images provide pixel-wise measurements of the distance between objects within the field-of-view of the camera and the camera itself. Depth cameras are used to solve many problems in the general field of computer vision. As an example, depth cameras may be used as components of a solution in the surveillance industry, to track people and monitor access to prohibited areas. As an additional example, the cameras may be applied to HMI (Human-Machine Interface) problems, such as tracking people's movements and the movements of their hands and fingers.    </p>
+    <p id="p-2" num="2">[0002<confidence value="5">]</confidence>
+    Significant advances have been made in recent years in the application of gesture control for user interaction with electronic devices. Gestures captured by depth cameras can be used, for example, to control a television, for home automation, or to enable user interfaces with tablets, personal computers, and mobile phones. As the core technologies used in these cameras continue to improve and their costs decline, gesture control will continue to play an increasing role in human interactions with electronic devices.    </p>
+    <heading id="h-4">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
+    <p id="p-3" num="3">[0003<confidence value="5">]</confidence>
+    Examples of a system for combining data from multiple depth cameras are illustrated in the figures. The examples and figures are illustrative rather than limiting.    </p>
+    <p id="p-4" num="4">[0004<confidence value="5">]</confidence>
+    Figure 1 is a diagram illustrating an example environment in which two cameras are positioned to view an area.    </p>
+    <p id="p-5" num="5">[0005<confidence value="5">]</confidence>
+    Figure 2 is a diagram illustrating an example environment in which multiple cameras are used to capture user interactions.    </p>
+    <boundary-data type="header">65662-8011<confidence value="88858">.USO1</confidence>
+/LEGAL24905239.1  1    </boundary-data>
+    <boundary-data type="header">Attorney Docket No. 65662-8011<confidence value="58856">.US01</confidence>
+    </boundary-data>
+    <p id="p-6" num="6">
+      <page-break num="2"/>
+[0006<confidence value="5">]</confidence>
+    Figure 3 is a diagram illustrating an example environment in which multiple cameras are used to capture interactions by multiple users.    </p>
+    <p id="p-7" num="7">[0007<confidence value="5">]</confidence>
+    Figure 4 is a diagram illustrating two example input images and a composite synthetic image obtained from the input images.    </p>
+    <p id="p-8" num="8">[0008<confidence value="5">]</confidence>
+    Figure 5 is a diagram illustrating an example model of a camera projection.    </p>
+    <p id="p-9" num="9">[0009<confidence value="5">]</confidence>
+    Figure 6 is a diagram illustrating example fields of view of two cameras and a synthetic resolution line.    </p>
+    <p id="p-10" num="10">[0010<confidence value="5">]</confidence>
+    Figure 7 is a diagram illustrating example fields of view of two cameras facing in different directions.    </p>
+    <p id="p-11" num="11">[0011<confidence value="5">]</confidence>
+    Figure 8 is a diagram illustrating an example configuration of two cameras and an associated virtual camera.    </p>
+    <p id="p-12" num="12">[0012<confidence value="5">]</confidence>
+    Figure 9 is a flow diagram illustrating an example process for generating a synthetic image.    </p>
+    <p id="p-13" num="13">[0013<confidence value="5">]</confidence>
+    Figure 10 is a flow diagram illustrating an example process for processing data generated by multiple individual cameras and combining the data.    </p>
+    <p id="p-14" num="14">[0014<confidence value="5">]</confidence>
+    Figure 11 is an example system diagram where input data streams from multiple cameras are processed by a central processor.    </p>
+    <p id="p-15" num="15">[0015<confidence value="5">]</confidence>
+    Figure 12 is an example system diagram where input data streams from multiple cameras are processed by separate processors before being combined by a central processor.    </p>
+    <p id="p-16" num="16">[0016<confidence value="5">]</confidence>
+    Figure 13 is an example system diagram where some camera data streams are processed by a dedicated processor while other camera data streams are processed by a host processor.    </p>
+    <boundary-data type="header">65662-8011<confidence value="88858">.USO1</confidence>
+/LEGAL24905239.1  -2-    </boundary-data>
+    <boundary-data type="header">Attorney Docket No. 65662-80<confidence value="8888858">11.US01</confidence>
+    </boundary-data>
+    <heading id="h-5">DETAILED DESCRIPTION</heading>
+    <p id="p-17" num="17">
+      <page-break num="3"/>
+[0017<confidence value="5">]</confidence>
+    A system and method for combining depth images taken from multiple depth cameras into a composite image are described. The volume of space captured in the composite image is configurable in size and shape depending upon the number of depth cameras used and the shape of the cameras' imaging sensors. Tracking of movements of a person or object can be performed on the composite image. The tracked movements can subsequently be used by an interactive application to render images of the tracked movements on a display.    </p>
+    <p id="p-18" num="18">[0018<confidence value="5">]</confidence>
+    Various aspects and examples of the invention will now be described.    </p>
+    <p id="p-19" num="19">The following description provides specific details for a thorough understanding and enabling description of these examples. One skilled in the art will understand, however, that the invention may be practiced without many of these details. Additionally, some well-known structures or functions may not be shown or described in detail, so as to avoid unnecessarily obscuring the relevant description.</p>
+    <p id="p-20" num="20">[0019<confidence value="5">]</confidence>
+    The terminology used in the description presented below is intended to be interpreted in its broadest reasonable manner, even though it is being used in conjunction with a detailed description of certain specific examples of the technology.    </p>
+    <p id="p-21" num="21">Certain terms may even be emphasized below; however, any terminology intended to be interpreted in any restricted manner will be overtly and specifically defined as such in this Detailed Description section.</p>
+    <p id="p-22" num="22">[0020<confidence value="5">]</confidence>
+    A depth camera is a camera that captures depth images, generally a sequence of successive depth images, at multiple frames per second. Each depth image contains per-pixel depth data, that is, each pixel in the image has a value that represents the distance between a corresponding area of an object in an imaged scene, and the camera. Depth cameras are sometimes referred to as three-dimensional (3D) cameras. A depth camera may contain a depth image sensor, an optical lens, and an illumination source, among other components. The depth image sensor may rely on one of several different sensor technologies. Among these sensor technologies are time-of- flight, known as "TO<confidence value="5">F</confidence>
+", (including scanning TO<confidence value="5">F</confidence>
+ or array TO<confidence value="5">F</confidence>
+), structured light, laser <boundary-data type="header">65662-8011<confidence value="88858">.USO1</confidence>
+/LEGAL24905239.1  3      </boundary-data>
+      <page-break num="4"/>
+      <boundary-data type="header">Attorney Docket No. 65662-8011<confidence value="58856">.US01</confidence>
+      </boundary-data>
+speckle pattern technology, stereoscopic cameras, active stereoscopic sensors, and shape-from-shading technology. Most of these techniques rely on active sensors, in the sense that they supply their own illumination source. In contrast, passive sensor techniques, such as stereoscopic cameras, do not supply their own illumination source, but depend instead on ambient environmental lighting. In addition to depth data, the cameras may also generate color data, in the same way that conventional color cameras do, and the color data can be combined with the depth data for processing.    </p>
+    <p id="p-23" num="23">[0021<confidence value="5">]</confidence>
+    The field-of-view of a camera refers to the region of a scene that a camera captures, and it is a function of several components of the camera, including, for example, the shape and curvature of the camera lens. The resolution of the camera is the number of pixels in each image that the camera captures. For example, the resolution may be 320 x <part-num-ref name="x">240</part-num-ref>
+ pixels, that is, 320 pixels in the horizontal direction, and 240 pixels in the vertical direction. Depth cameras can be configured for different ranges. The range of a camera is the region in front of the camera in which the camera captures data of a minimal quality, and is, generally speaking, a function of the camera's component specifications and assembly. In the case of time-of-flight cameras, for example, longer ranges typically require higher illumination power. Longer ranges may also require higher pixel array resolutions.    </p>
+    <p id="p-24" num="24">[0022<confidence value="5">]</confidence>
+    There is a direct tradeoff between the quality of the data generated by a depth camera, and parameters of the camera such as the field-of-view, resolution, and frame rate. The quality of the data, in turn, determines the level of movement tracking that the camera can support. In particular, the data must conform to a certain level of quality in order to enable robust and highly precise tracking of a user's fine movements.    </p>
+    <p id="p-25" num="25">Since the camera specifications are effectively limited by considerations of cost and size, the quality of the data is likewise limited. Furthermore, there are additional restrictions that also affect the character of the data. For example, the specific geometric shape of the image sensor (generally rectangular) defines the dimensions of the image captured by the camera.</p>
+    <boundary-data type="header">65662-8011<confidence value="5">.</confidence>
+ <confidence value="8845">USO1</confidence>
+ /LEGAL24905239.1  -4-    </boundary-data>
+    <boundary-data type="header">Attorney Docket No. 65662-8011<confidence value="58856">.US01</confidence>
+    </boundary-data>
+    <p id="p-26" num="26">
+      <page-break num="5"/>
+[0023<confidence value="5">]</confidence>
+    An interaction area is the space in front of a depth camera in which a user can interact with an application, and, consequently, the quality of the data generated by the camera should be high enough to support tracking of the user's movements. The interaction area requirements of different applications may not be satisfied by the specifications of the camera. For example, if a developer intends to construct an installation in which multiple users can interact, a single camera's field-of-view may be too limiting to support the entire interaction area necessary for the installation. In another example, the developer may want to work with an interaction space that is different than the shape of the interaction area specified by the camera, such as an L- shape, or a circular-shaped interaction area. The disclosure describes how the data from multiple depth cameras can be combined, via specialized algorithms, so as to enlarge the area of interaction and customize it to fit the particular needs of the application.    </p>
+    <p id="p-27" num="27">[0024<confidence value="5">]</confidence>
+    The term "combining the data" refers to a process that takes data from multiple cameras, each with a view of a portion of the interaction area, and produces a new stream of data that covers the entire interaction area. Cameras having various ranges can be used to obtain the individual streams of depth data, and even multiple cameras that each have a different range can be used. The data, in this context, can refer either to raw data from the cameras, or to the output of tracking algorithms that are individually run on raw camera data. Data from multiple cameras can be combined even if the cameras do not have overlapping fields-of-view.    </p>
+    <p id="p-28" num="28">[0025<confidence value="5">]</confidence>
+    There are many situations in which it is desirable to extend the interaction area for applications that require the use of depth cameras. Refer to Figure 1, which is a diagram of one embodiment, in which a user may have two monitors at his desk, with two cameras, each camera positioned to view the area in front of one screen. Because of both the proximity of the camera to the user's hands, and the quality of the depth data required to support highly precise tracking of the user's fingers, it is not generally possible for one camera's field-of-view to cover the entire desired interaction area.    </p>
+    <p id="p-29" num="29">Rather, the independent data streams from each camera can be combined to generate a single, synthetic data stream, and tracking algorithms can be applied to this synthetic <boundary-data type="header">65662-8011<confidence value="88858">.USO1</confidence>
+/LEGAL24905239.1  -5-      </boundary-data>
+      <page-break num="6"/>
+      <boundary-data type="header">Attorney Docket No. 65662-8011<confidence value="58856">.US01</confidence>
+      </boundary-data>
+data stream. From the perspective of the user, he is able to move his hands from one camera's field-of-view into that of the second camera, and his application reacts seamlessly, as if his hand stayed within the field-of-view of a single camera. For example, the user may pick up a virtual object that is visible on a first screen with his hand, and move his hand in front of the camera associated with a second screen, where he then releases the object, and the object appears on the second screen.    </p>
+    <p id="p-30" num="30">[0026<confidence value="5">]</confidence>
+    Figure 2 is a diagram of another example embodiment in which a standalone device can contain multiple cameras positioned around its periphery, each with a field-of-view that extends outward from the device. The device can be placed, for example, on a conference table, where several people may be seated, and can capture a unified interaction area.    </p>
+    <p id="p-31" num="31">[0027<confidence value="5">]</confidence>
+    In an additional embodiment, several individuals may work together, each on a separate device. Each device may be equipped with a camera. The fields-of-view of the individual cameras can be combined to generate a large, composite interaction area accessible to all the individual users together. The individual devices may even be different kinds of electronic devices, such as laptops, tablets, desktop personal computers, and smart phones.    </p>
+    <p id="p-32" num="32">[0028<confidence value="5">]</confidence>
+    Figure 3 is a diagram of a further example embodiment which is an application designed for simultaneous interaction by multiple users. Such an application might appear, for example, in a museum, or in another type of public space. In this case, there may be a particularly large interaction area for an application designed for multi-user interaction. In order to support this application, multiple cameras can be installed so that their respective fields-of-view overlap with each other, and the data from each one can be combined into a composite synthetic data stream that can be processed by the tracking algorithms. In this way, the interaction area can be made arbitrarily large, to support any such applications.    </p>
+    <p id="p-33" num="33">[0029<confidence value="5">]</confidence>
+    In all of the aforementioned embodiments, the cameras may be depth cameras, and the depth data they generate may be used to enable tracking and gesture recognition algorithms that are able to interpret a user's movements. U.S. Patent <boundary-data type="header">65662-8011<confidence value="88858">.USO1</confidence>
+/LEGAL24905239.1  -6-      </boundary-data>
+      <page-break num="7"/>
+      <boundary-data type="header">Attorney Docket No. 65662-8011<confidence value="58856">.US01</confidence>
+      </boundary-data>
+Application No. 13/532,609, entitled "SYSTEM AND METHOD FOR CLOSE-RANGE MOVEMENT TRACKING", filed June <part-num-ref name="CLOSE-RANGE MOVEMENT TRACKING&quot;, filed June">25,</part-num-ref>
+ <part-num-ref name="CLOSE-RANGE MOVEMENT TRACKING&quot;, filed June 25,">2012,</part-num-ref>
+ describes several types of relevant user interactions based on depth cameras, and is hereby incorporated in its entirety.    </p>
+    <p id="p-34" num="34">[0030<confidence value="5">]</confidence>
+    Figure 4 is a diagram of an example of two input images, <part-num-ref name="two input images,">42</part-num-ref>
+ and 44, captured by separate cameras, positioned a fixed distance apart from each other, and the synthetic image <part-num-ref name="synthetic image">46,</part-num-ref>
+ that is created by combining the data from the two input images using the techniques described in this disclosure. Note that the objects in the individual input images <part-num-ref name="individual input images">42</part-num-ref>
+ and 44 appear in their respective locations in the synthetic image, as well.    </p>
+    <p id="p-35" num="35">[0031<confidence value="5">]</confidence>
+    Cameras view a three-dimensional (3D) scene and project objects from the 3D scene onto a two-dimensional (2D) image plane. In the context of the discussion of the camera projection, "image coordinate system" refers to the 2D coordinate system (x, y) associated with the image plane, and "world coordinate system" refers to the 3D coordinate system (X, Y, Z) associated with the scene that the camera is viewing. In both coordinate systems, the camera is at the origin ((x=0, y=0), or (X=<confidence value="4">0</confidence>
+, Y=<confidence value="4">0</confidence>
+, Z=0)) of the coordinate axes.    </p>
+    <p id="p-36" num="36">[0032<confidence value="5">]</confidence>
+     Refer to Figure 5, which is an example idealized model of a camera projection process, known as a pinhole camera model. Since the model is idealized, for the sake of simplicity, certain characteristics of the camera projection, such as the lens distortion, are ignored. Based on this model, the relation between the 3D coordinate system of the scene, (X, Y, Z), and the 2D coordinate system of the image plane, (x, y), is:    </p>
+    <p id="p-37" num="37">
+      <confidence value="5">X</confidence>
+ <confidence value="2">-</confidence>
+ dis<confidence value="88666">tance</confidence>
+ <confidence value="2">&lt;</confidence>
+  <confidence value="2888">ydis</confidence>
+ <confidence value="888">tan</confidence>
+ <confidence value="88">ce</confidence>
+ <confidence value="528">Z=f</confidence>
+ dis <confidence value="88566">tance</confidence>
+ <boundary-data type="header">65662-8011<confidence value="88858">.USO1</confidence>
+/LEGAL24905239.1  -7-      </boundary-data>
+      <page-break num="8"/>
+      <boundary-data type="header">Attorney Docket No. 65662-8011<confidence value="58856">.US01</confidence>
+      </boundary-data>
+where distance is the distance between the camera center (also called the focal point) and a point on the object, and d is the distance between the camera center and the point in the image corresponding to the projection of the object point. The variable <confidence value="6">f</confidence>
+ <confidence value="88">is</confidence>
+ the focal length and is the distance between the origin of the 2D image plane and the camera center (or focal point). Thus, there is a one-to-one mapping between points in the 2D image plane and points in the 3D world. The mapping from the 3D world coordinate system (the real world scene) to the 2D image coordinate system (the image plane) is referred to as the projection function, and the mapping from the 2D image coordinate system to the 3D world coordinate system is referred to as the back- projection function.    </p>
+    <p id="p-38" num="38">[0033<confidence value="5">]</confidence>
+    The disclosure describes a method of taking two images, captured at nearly the same instant in time, one from each of two depth cameras, and constructing a single image, which we will refer to as the "synthetic image". For the sake of simplicity, the current discussion will focus on the case of two cameras. Obviously, the methods discussed herein are easily extensible to the case in which more than two cameras are used.    </p>
+    <p id="p-39" num="39">[0034<confidence value="5">]</confidence>
+    Initially, the respective projection and back-projection functions for each depth camera are computed.    </p>
+    <p id="p-40" num="40">[0035<confidence value="5">]</confidence>
+    The technique further involves a virtual camera which is used to virtually "capture" the synthetic image. The first step in the construction of this virtual camera is to derive its parameters - its field-of-view, resolution, etc. Subsequently, the projection and back-projection functions of the virtual camera are also computed, so that the synthetic image can be treated as if it were a depth image captured by a single, "real" depth camera. Computation of the projection and back-projection functions for the virtual camera depends on camera parameters such as the resolution and the focal length.    </p>
+    <p id="p-41" num="41">[0036<confidence value="5">]</confidence>
+    The focal length of the virtual camera is derived as a function of the focal lengths of the input cameras. The function may be dependent upon the placement of <boundary-data type="header">65662-8011<confidence value="88858">.USO1</confidence>
+/LEGAL24905239.1  -8-      </boundary-data>
+      <page-break num="9"/>
+      <boundary-data type="header">Attorney Docket No. 65662-8011<confidence value="58856">.US01</confidence>
+      </boundary-data>
+the input cameras, for example, whether the input cameras are facing in the same direction. In one embodiment, the focal length of the virtual camera can be derived as an average of the focal lengths of the input cameras. Typically, the input cameras are of the same type and have the same lenses, so the focal lengths of the input cameras are very similar. In this case, the focal length of the virtual camera is the same as that of the input cameras.    </p>
+    <p id="p-42" num="42">The resolution of a synthetic image, generated by the virtual camera, is derived from the resolutions of the input cameras. The resolution of the input cameras are fixed, so the larger the overlap of the images acquired by the input cameras, the less non- overlapping resolution is available from which to create the synthetic image. Figure 6 is a diagram of two input cameras, A and B, in parallel, so that they are facing in the same direction and positioned a fixed distance apart. The field-of-view of each camera is represented by the cones extending from the respective camera lenses. As an object moves farther away from the camera, a larger region of that object is represented as a single pixel. Thus, the granularity of an object that is farther away is not as fine as the granularity of the object when it is closer to the camera. In order to complete the model of the virtual camera, an additional parameter must be defined, which relates to the depth region of interest for the virtual camera.</p>
+    <p id="p-43" num="43">[0037<confidence value="5">]</confidence>
+    In figure 6 there is a straight line <part-num-ref name="straight line">610</part-num-ref>
+ in the diagram, parallel to the axis on which the two cameras A and B are positioned, which is labeled "synthetic resolution line". The synthetic resolution line intersects the fields-of-view of both cameras. This synthetic resolution line can be adjusted, based on the desired range of the application, but it is defined relative to the virtual camera, for example, as being perpendicular to a ray extending from the center of the virtual camera. For the scenario depicted in figure 6, the virtual camera can be placed at a midpoint, i.e., symmetrically, between the input cameras A and B to maximize the synthetic image that would be captured by the virtual camera. The synthetic resolution line is used to establish the resolution of the synthetic image. In particular, the further away the synthetic resolution line is set from the cameras, the lower the resolution of the synthetic image, since larger regions of the two images overlap. Similarly, as the distance between the synthetic resolution line and the <boundary-data type="header">65662-8011<confidence value="88858">.USO1</confidence>
+/LEGAL24905239.1  -9-      </boundary-data>
+      <page-break num="10"/>
+      <boundary-data type="header">Attorney Docket No. 65662-8011<confidence value="58856">.US01</confidence>
+      </boundary-data>
+virtual camera decreases, the resolution of the synthetic image increases. In the case where the cameras are placed in parallel, and only separated by translation, as in Figure 6, there is a line <part-num-ref name="line">620</part-num-ref>
+ in the diagram denoted as "synthetic resolution = maximum". If the synthetic resolution line of the virtual camera is selected to be line <part-num-ref name="line">620,</part-num-ref>
+ the resolution of the synthetic image is maximal, and it is equal to the sum of the resolutions of cameras A and B. In other words, the maximal possible resolution is obtained where there is a minimum intersection of the fields of view of the input cameras. The synthetic resolution line can be fixed on an ad hoc basis by the user, depending on the region of interest of the application.    </p>
+    <p id="p-44" num="44">[0038<confidence value="5">]</confidence>
+    The synthetic resolution line shown in figure 6 is for a limited case where, for simplicity, it is constrained to be linear and parallel to the axis on which the input cameras and the virtual camera are situated. A synthetic resolution line subject to these constraints is still sufficient for defining the resolution of the virtual camera for many cases of interest. However, more generally, the synthetic resolution line of the virtual camera can be a curve or made up of multiple piecewise linear segments that are not in a straight line.    </p>
+    <p id="p-45" num="45">[0039<confidence value="5">]</confidence>
+    Associated with each of the input cameras, for example, cameras A and B in figure 6, is an independent coordinate system. It is straightforward to compute the transformation between these respective coordinate systems. The transformation maps one coordinate system to another, and provides a way to assign to any point in a first coordinate system, respectively, a value in the second coordinate system.    </p>
+    <p id="p-46" num="46">[0040<confidence value="5">]</confidence>
+     In one embodiment, the input cameras (A and B) have overlapping fields- of-view. However, without any loss of generality, the synthetic image can also be constructed of multiple input images that do not overlap such that there are gaps in the synthetic image. The synthetic image can still be used for tracking movements. In this case, the positions of the input cameras would be need to be computed explicitly because the images generated by the cameras do not overlap.    </p>
+    <p id="p-47" num="47">[0041<confidence value="5">]</confidence>
+     For the case of overlapping images, computing this transformation can be done by matching features between images from the two cameras, and solving the <boundary-data type="header">65662-8011<confidence value="88858">.USO1</confidence>
+/LEGAL24905239.1  -10-      </boundary-data>
+      <page-break num="11"/>
+      <boundary-data type="header">Attorney Docket No. 65662-8011<confidence value="58856">.US01</confidence>
+      </boundary-data>
+correspondence problem. Alternatively, if the cameras' positions are fixed, there can be an explicit calibration phase, in which points appearing in images from both cameras are manually marked, and the transformation between the two coordinate systems can be computed from these matched points. Another alternative is to define the transformation between the respective cameras' coordinate systems explicitly. For example, the relative positions of the individual cameras may be entered by the user as part of the system initialization process, and the transformation between the cameras can be computed. This method of specifying the spatial relationship between the two cameras explicitly, by the user, is useful, for example, in the case when the input cameras, do not have overlapping fields-of-view. No matter which method is used to derive the transformation between different cameras (and their respective coordinate systems), this step only needs to be done once, for example, at the time that the system is configured. As long as the cameras are not moved, the transformation computed between the cameras' coordinate systems is valid.    </p>
+    <p id="p-48" num="48">[0042<confidence value="5">]</confidence>
+    Additionally, identifying the transformations between each of the input cameras defines the input cameras' positions with respect to each other. This information can be used to identify the midpoint or a position that is symmetrical with respect to the positions of the input cameras for the virtual camera to be located.    </p>
+    <p id="p-49" num="49">Alternatively, the input cameras' positions can be used to select any other position for the virtual camera based upon other application-specific requirements for the synthetic image. Once the position of the virtual camera is fixed, and the synthetic resolution line is selected, the resolution of the virtual camera can be derived.</p>
+    <p id="p-50" num="50">[0043<confidence value="5">]</confidence>
+    The input cameras can be placed in parallel, as in Figure 6, or with a more arbitrary relationship, as in Figure 7. Figure 8 is a sample diagram of two cameras, a fixed distance apart, with a virtual camera positioned at the midpoint between the two cameras. However, the virtual camera can be positioned anywhere with respect to the input cameras.    </p>
+    <p id="p-51" num="51">[0044<confidence value="5">]</confidence>
+    In one embodiment, the data from multiple input cameras can be combined to produce the synthetic image, which is an image that is associated with the <boundary-data type="header">65662-8011.US<confidence value="4">O</confidence>
+1/LEGAL24905239.1  <confidence value="5">-</confidence>
+11-      </boundary-data>
+      <page-break num="12"/>
+      <boundary-data type="header">Attorney Docket No. 65662-8011<confidence value="58856">.US01</confidence>
+      </boundary-data>
+virtual camera. Before beginning to process the images from the input cameras, several characteristics of the virtual camera must be computed. First, the virtual camera "specs" - resolution, focal length, projection function, and back-projection function, as described above - are computed. Subsequently, the transformations from the coordinate systems of each of the input cameras to the virtual camera are computed. That is, the virtual camera acts as if it is a real camera, and generates a synthetic image which is defined by the specs of the camera, in a manner similar to the way actual cameras generate images.    </p>
+    <p id="p-52" num="52">[0045<confidence value="5">]</confidence>
+    Figure 9 describes an example workflow for generating a synthetic image from a virtual camera using multiple input images generated by multiple input cameras.    </p>
+    <p id="p-53" num="53">First, at 605, the specifications, e.g. resolution, focal length, synthetic resolution line, etc., of the virtual camera are computed as well as the transformations from the coordinate systems of each of the input cameras to the virtual camera.</p>
+    <p id="p-54" num="54">[0046<confidence value="5">]</confidence>
+    Then at 610, the depth images are captured by each input camera independently. It is assumed that the images are captured at nearly the same instant. If this is not the case, they must be explicitly synchronized to ensure that they both reflect the projection of the scene at the same point in time. For example, checking the timestamp of each image and selecting images with timestamps within a certain threshold can suffice to satisfy this requirement.    </p>
+    <p id="p-55" num="55">[0047<confidence value="5">]</confidence>
+    Subsequently, at 620, each 2D depth image is back-projected to the 3D coordinate system of each camera. Each set of 3D points are then transformed to the coordinate system of the virtual camera at 630 by applying the transformation from the respective camera's coordinate system to the coordinate system of the virtual camera.    </p>
+    <p id="p-56" num="56">The relevant transformation is applied to each data point independently. Based on the determination of the synthetic resolution line, as described above, a collection of three- dimensional points reproducing the area monitored by the input cameras is created at 640. The synthetic resolution line determines the region in which the images from the input cameras overlap <boundary-data type="header">65662-8011<confidence value="88858">.USO1</confidence>
+/LEGAL24905239.1  -12-      </boundary-data>
+      <page-break num="13"/>
+      <boundary-data type="header">Attorney Docket No. 65662-8011<confidence value="58856">.US01</confidence>
+      </boundary-data>
+[0048<confidence value="5">]</confidence>
+    Using the virtual camera's projection function, each of the 3D points is projected onto a 2D synthetic image at 650. Each pixel in the synthetic image corresponds to either a pixel in one of the camera images, or to two pixels in the case of two input cameras, one from each camera image. In the case that the synthetic image pixel corresponds to only a single camera image pixel, it receives the value of that pixel.    </p>
+    <p id="p-57" num="57">In the case that the synthetic image pixel corresponds to two camera image pixels (i.e., the synthetic image pixel is in the region in which the two camera images overlap), the pixel with the minimum value should be selected to construct the synthetic image <part-num-ref name="synthetic image">660.</part-num-ref>
+    </p>
+    <p id="p-58" num="58">The reason is because a smaller depth pixel value means the object is closer to one of the cameras, and this scenario may arise when the camera with the minimum pixel value has a view of an object that the other camera does not have. If both cameras image the same point on the object, the pixel value for each camera for that point, after it is transformed to the virtual camera's coordinate system, should be nearly the same.</p>
+    <p id="p-59" num="59">Alternatively or additionally, any other algorithm, such as an interpolation algorithm, can be applied to the pixel values of the acquired images to help fill in missing data or improve the quality of the synthetic image.</p>
+    <p id="p-60" num="60">[0049<confidence value="5">]</confidence>
+    Depending on the relative positions of the input cameras, the synthetic image may contain invalid, or noisy, pixels, resulting from the limited resolution of the input camera images, and the process of projecting an image pixel to a real-world, 3D point, transforming the point to the virtual camera's coordinate system, and then back- projecting the 3D point to the 2D, synthetic image. Consequently, a post-processing cleaning algorithm should be applied at 670 to clean up the noisy pixel data. Noisy pixels appear in the synthetic image because there are no corresponding 3D points in the data that was captured by the input cameras, after it was transformed to the coordinate system of the virtual camera. One solution is to interpolate between all the pixels in the actual camera images, in order to generate an image of much higher resolution, and, consequently, a much more dense cloud of 3D points. If the 3D point cloud is sufficiently dense, all of the synthetic image pixels will correspond to at least one valid (i.e., captured by an input camera) 3D point. The downside of this approach is <boundary-data type="header">65662-8011<confidence value="88858">.USO1</confidence>
+/LEGAL24905239.1  -13-      </boundary-data>
+      <page-break num="14"/>
+      <boundary-data type="header">Attorney Docket No. 65662-8011<confidence value="58856">.US01</confidence>
+      </boundary-data>
+the cost of sub-sampling to create a very high resolution image from each input camera and the management of a high volume of data.    </p>
+    <p id="p-61" num="61">[0050<confidence value="5">]</confidence>
+    Consequently, in an embodiment of the current disclosure, the following technique is applied to clean up the noisy pixels in the synthetic image. First, a simple 3x3 filter (e.g., a median filter) is applied to all the pixels in the depth image, in order to exclude depth values that are too large. Then, each pixel of the synthetic image is mapped back into the respective input camera images, as follows: each image pixel of the synthetic image is projected into 3D space, the respective reverse transformation is applied to map the 3D point into each input camera, and finally, each input camera's back-projection function is applied to the 3D point, in order to map the point to the input camera image. (Note that this is exactly the reverse of the process that was applied in order to create the synthetic image in the first place.) In this way, either one or two pixel values are obtained, from either one or both input cameras (depending on whether the pixel is on the overlapping region of the synthetic image). If two pixels are obtained (one from each input camera), the minimum value is selected, and, after it is projected, transformed, and back-projected, assigned to the "noisy" pixel of the synthetic image.    </p>
+    <p id="p-62" num="62">[0051<confidence value="5">]</confidence>
+    Once the synthetic image is constructed, at 680, tracking algorithms can be run on it, in the same way that they can be run on standard depth images generated by depth cameras. In one embodiment, tracking algorithms are run on the synthetic image to track the movements of people, or the movements of the fingers and hands, to be used as input to an interactive application.    </p>
+    <p id="p-63" num="63">[0052<confidence value="5">]</confidence>
+    Figure 10 is an example workflow of an alternative method for processing the data generated by multiple individual cameras and to combine the data. In this alternative method, a tracking module is run individually on the data generated by each camera, and the results of the tracking modules are then combined together. Similar to the method described by figure 9, at 705 the specifications of the virtual camera are computed, and the relative positions of the individual cameras are first acquired and the transformations between the input cameras and the virtual camera are derived. Images are captured separately by each input camera at 710, and the tracking algorithms are <boundary-data type="header">65662-8011<confidence value="88858">.USO1</confidence>
+/LEGAL24905239.1  -14-      </boundary-data>
+      <page-break num="15"/>
+      <boundary-data type="header">Attorney Docket No. 65662-8011<confidence value="58856">.US01</confidence>
+      </boundary-data>
+run on each input camera's data at 720. The output of the tracking module includes the 3D positions of the tracked objects. Objects are transformed from the coordinate system of their respective input camera to the coordinate system of the virtual camera, and a 3D composite scene is created synthetically at 730. Note that the 3D composite scene created at 730 is different from the synthetic image that is constructed at 660 in figure 9.    </p>
+    <p id="p-64" num="64">In one embodiment, this composite scene is used to enable interactive applications.</p>
+    <p id="p-65" num="65">This process can similarly be performed for a sequence of images received from each of the multiple input cameras so that a sequence of composite scenes is created synthetically.</p>
+    <p id="p-66" num="66">[0053<confidence value="5">]</confidence>
+    Figure 11 is a diagram of an example system that can apply the techniques discussed herein. In this example, there are multiple ("N") cameras, 760A, 760<confidence value="5">B</confidence>
+, .<confidence value="8">.</confidence>
+.760N imaging a scene. The data streams from each of the cameras are sent to processor <part-num-ref name="processor">770,</part-num-ref>
+ and the combining module <part-num-ref name="combining module">775</part-num-ref>
+ takes the input data streams from the individual cameras and generates a synthetic image from them, using the process described by the flow diagram in figure 9. The tracking module <part-num-ref name="tracking module">778</part-num-ref>
+ applies tracking algorithms to the synthetic image, and the output of the tracking algorithms may be used by the gesture recognition module <part-num-ref name="gesture recognition module">780</part-num-ref>
+ to recognize gestures that have been performed by a user. The output of the tracking module <part-num-ref name="tracking module">778</part-num-ref>
+ and the gesture recognition module <part-num-ref name="gesture recognition module">780,</part-num-ref>
+ are sent to the application <part-num-ref name="application">785,</part-num-ref>
+ which communicates with the display <part-num-ref name="display">790</part-num-ref>
+ to present feedback to the user.    </p>
+    <p id="p-67" num="67">[0054<confidence value="5">]</confidence>
+    Figure 12 is a diagram of an example system in which the tracking modules are run separately on the data streams generated by the individual cameras, and the output of the tracking data is combined to produce the synthetic scene. In this example, there are multiple ("N") cameras, 810A, 810<confidence value="5">B</confidence>
+, ...810N. Each camera is connected to a separate processor, 820A, 820<confidence value="56">B,</confidence>
+ <confidence value="8888">....</confidence>
+820N, respectively. The tracking modules 830A, 830<confidence value="5">B</confidence>
+, .<confidence value="8">.</confidence>
+.830N are run individually on the data streams generated by the respective cameras. Optionally, a gesture recognition module 835A, 835<confidence value="5">B</confidence>
+, ... 835N can also be run on the output of the tracking modules 830A, 830<confidence value="5">B</confidence>
+, .<confidence value="8">.</confidence>
+.830N. Subsequently, the results of the individual tracking modules 830A, 830<confidence value="5">B</confidence>
+, .<confidence value="8">.</confidence>
+.830N and the gesture recognition modules 835A, 835<confidence value="5">B</confidence>
+, ... 835N are transferred to a separate processor, <part-num-ref name="separate processor,">840,</part-num-ref>
+ <boundary-data type="header">65662-8011<confidence value="88858">.USO1</confidence>
+/LEGAL24905239.1  -15-      </boundary-data>
+      <page-break num="16"/>
+      <boundary-data type="header">Attorney Docket No. 65662-8011<confidence value="58856">.US01</confidence>
+      </boundary-data>
+which applies the combining module <part-num-ref name="combining module">850.</part-num-ref>
+ The combining module <part-num-ref name="combining module">850</part-num-ref>
+ receives as input the data generated by the individual tracking modules 830A, 830<confidence value="5">B</confidence>
+, .<confidence value="88">..</confidence>
+830N and creates a synthetic 3D scene, according to the process described in figure 10. The processor <part-num-ref name="processor">840</part-num-ref>
+ may also execute an application <part-num-ref name="application">860</part-num-ref>
+ which receives the input from the combining module <part-num-ref name="combining module">850</part-num-ref>
+ and the gesture recognition modules 835A, 835<confidence value="5">B</confidence>
+, ... 835N and may render images that can be displayed to the user on the display <part-num-ref name="display">870.</part-num-ref>
+    </p>
+    <p id="p-68" num="68">[0055<confidence value="5">]</confidence>
+    Figure 13 is a diagram of an example system in which some tracking modules are run on processors dedicated to individual cameras, and others are run on a "host" processor. Cameras 910A, 910<confidence value="5">B</confidence>
+, ...910N capture images of an environment.    </p>
+    <p id="p-69" num="69">Processors 920A, 920<confidence value="5">B</confidence>
+ receive the images from the cameras 91<confidence value="4">0</confidence>
+A, 91<confidence value="45">0B</confidence>
+, respectively, and tracking modules 930A, 930<confidence value="5">B</confidence>
+ run tracking algorithms, and, optionally, gesture recognition modules 935A, 935<confidence value="5">B</confidence>
+ run gesture recognition algorithms. Some of the cameras 910(N-1), 91<confidence value="5">0</confidence>
+N pass the image data streams directly to the "host" processor <part-num-ref name="&quot;host&quot; processor">940,</part-num-ref>
+ which runs the tracking module <part-num-ref name="tracking module">950,</part-num-ref>
+ and, optionally, the gesture recognition module <part-num-ref name="gesture recognition module">955,</part-num-ref>
+ on the data streams generated by cameras 910(N-1),910N. The tracking module <part-num-ref name="tracking module">950</part-num-ref>
+ is applied to the data streams generated by the cameras that are not connected to a separate processor. The combining module <part-num-ref name="combining module">960</part-num-ref>
+ receives as input the outputs of the various tracking modules 930A, 930<confidence value="5">B</confidence>
+, <part-num-ref name="various tracking modules 930A, 930B,">950,</part-num-ref>
+ and combines them all into a synthetic 3D scene according to the process shown in figure 10. Subsequently, the tracking data and identified gestures may be transferred to an interactive application <part-num-ref name="interactive application">970</part-num-ref>
+ which may use a display <part-num-ref name="display">980</part-num-ref>
+ to present feedback to the user.    </p>
+    <p id="p-70" num="70">Conclusion [0001<confidence value="5">]</confidence>
+   Unless the context clearly requires otherwise, throughout the description and the claims, the words "comprise," "comprising," and the like are to be construed in an inclusive sense (i.e., to say, in the sense of "including, but not limited to"), as opposed to an exclusive or exhaustive sense. As used herein, the terms "connected," "coupled," or any variant thereof means any connection or coupling, either direct or indirect, between two or more elements. Such a coupling or connection between the elements can be physical, logical, or a combination thereof. Additionally, the words <boundary-data type="header">65662-8011<confidence value="88858">.USO1</confidence>
+/LEGAL24905239.1  -16-      </boundary-data>
+      <page-break num="17"/>
+      <boundary-data type="header">Attorney Docket No. 65662-8011<confidence value="58856">.US01</confidence>
+      </boundary-data>
+"herein," "above," "below," and words of similar import, when used in this application, refer to this application as a whole and not to any particular portions of this application.    </p>
+    <p id="p-71" num="71">Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word "or," in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.</p>
+    <p id="p-72" num="72">[0002<confidence value="5">]</confidence>
+   The above Detailed Description of examples of the invention is not intended to be exhaustive or to limit the invention to the precise form disclosed above. While specific examples for the invention are described above for illustrative purposes, various equivalent modifications are possible within the scope of the invention, as those skilled in the relevant art will recognize. While processes or blocks are presented in a given order in this application, alternative implementations may perform routines having steps performed in a different order, or employ systems having blocks in a different order.    </p>
+    <p id="p-73" num="73">Some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or subcombinations. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed or implemented in parallel, or may be performed at different times.</p>
+    <p id="p-74" num="74">Further any specific numbers noted herein are only examples. It is understood that alternative implementations may employ differing values or ranges.</p>
+    <p id="p-75" num="75">[0003<confidence value="5">]</confidence>
+   The various illustrations and teachings provided herein can also be applied to systems other than the system described above. The elements and acts of the various examples described above can be combined to provide further implementations of the invention.    </p>
+    <p id="p-76" num="76">[0004<confidence value="5">]</confidence>
+   Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the invention can be modified, if necessary, to employ the systems, functions, and concepts included in such references to provide further implementations of the invention.    </p>
+    <boundary-data type="header">65662-8011<confidence value="88858">.USO1</confidence>
+/LEGAL24905239.1  -17-    </boundary-data>
+    <boundary-data type="header">Attorney Docket No. 65662-8011<confidence value="58856">.US01</confidence>
+    </boundary-data>
+    <p id="p-77" num="77">
+      <page-break num="18"/>
+[0005<confidence value="5">]</confidence>
+   These and other changes can be made to the invention in light of the above Detailed Description. While the above description describes certain examples of the invention, and describes the best mode contemplated, no matter how detailed the above appears in text, the invention can be practiced in many ways. Details of the system may vary considerably in its specific implementation, while still being encompassed by the invention disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the invention should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the invention with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the invention to the specific examples disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the invention encompasses not only the disclosed examples, but also all equivalent ways of practicing or implementing the invention under the claims.    </p>
+    <p id="p-78" num="78">[0006<confidence value="5">]</confidence>
+   While certain aspects of the invention are presented below in certain claim forms, the applicant contemplates the various aspects of the invention in any number of claim forms. For example, while only one aspect of the invention is recited as a means- plus-function claim under <part-num-ref name="means- plus-function claim under">35</part-num-ref>
+ U.S.C. <confidence value="5">§</confidence>
+ <part-num-ref name="U.S.C. §">112,</part-num-ref>
+ sixth paragraph, other aspects may likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. (Any claims intended to be treated under <part-num-ref name="treated under">35</part-num-ref>
+ U.S.C. <confidence value="5">§</confidence>
+ <part-num-ref name="U.S.C. §">112,</part-num-ref>
+   <part-num-ref name="U.S.C. § 112,">6</part-num-ref>
+ will begin with the words "means for.") Accordingly, the applicant reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the invention.    </p>
+    <boundary-data type="header">65662-8011<confidence value="88858">.USO1</confidence>
+/LEGAL24905239.1  -18-    </boundary-data>
+  </description>
+</us-patent-application>
+

applicant/13725804.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" file="13725804.2012-12-21.HB9AS2SQPXXIFW1.SPEC.XML">
+  <us-bibliographic-data-application lang="EN" country="US">
+    <application-reference appl-type="utility">
+      <document-id>
+        <doc-number>13725804</doc-number>
+        <date>2012-12-21</date>
+      </document-id>
+    </application-reference>
+  </us-bibliographic-data-application>
+  <description id="description">
+    <p id="p-1" num="1">Attorney Docket No<confidence value="5">.</confidence>
+: 0260222C<confidence value="4">1</confidence>
+ In the Specification:    </p>
+    <p id="p-2" num="2">
+      <confidence value="1">*</confidence>
+  Please a<confidence value="5">d</confidence>
+d the following paragraph, on page <part-num-ref name="following paragraph, on page">1,</part-num-ref>
+ below the title:    </p>
+    <p id="p-3" num="3">This application is a Continuation of U.S. Patent Application Serial No. 12/387,751 filed on May <part-num-ref name="U.S. Patent Application Serial No. 12/387,751 filed on May">6,</part-num-ref>
+ <part-num-ref name="U.S. Patent Application Serial No. 12/387,751 filed on May 6,">2009.</part-num-ref>
+    </p>
+    <p id="p-4" num="4">
+      <confidence value="8">2</confidence>
+                  <confidence value="66">09</confidence>
+-DIS<confidence value="6686">-030</confidence>
+-STUDIO<confidence value="5">-</confidence>
+US-CON<confidence value="1">I</confidence>
+     </p>
+  </description>
+</us-patent-application>
+

applicant/13761785.xml

@@ -0,0 +1 @@
+<?xml version="1.0" encoding="utf-8"?><pat:SpecificationDocument xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:pat="urn:us:gov:doc:uspto:patent" xmlns:ent="urn:us:gov:doc:uspto:enterprise" xmlns="urn:us:gov:doc:uspto:patent" xmlns:tbl="http://www.oasis-open.org/tables/exchange/1.0" xmlns:com="http://www.wipo.int/standards/XMLSchema/Common/1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XML_SCHEMAS/V1_3/SpecificationDocument_1_0.xsd" pat:instanceFileName="13761785.02-07-2013.HCWE2Q9MPXXIFW3.SPEC.XML" pat:id="HCWE2Q9MPXXIFW3"><pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001"><pat:ApplicationHeaderDetails><pat:ApplicationNumber>13761785</pat:ApplicationNumber></pat:ApplicationHeaderDetails><pat:PageTotalQuantity>23</pat:PageTotalQuantity><pat:ParagraphTotalQuantity>55</pat:ParagraphTotalQuantity></pat:DocumentHeaderDetails><pat:MailRoomDate>2013-02-07</pat:MailRoomDate><pat:DocumentCreateDateText>2014-09-27</pat:DocumentCreateDateText><pat:DocumentTitle>SPECIFICATION DOCUMENT</pat:DocumentTitle><pat:Specification><?PageStart number='1'?><pat:P pat:pNumber="1" pat:id="p-1"><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData></pat:P><pat:Heading pat:id="h-1">METHOD AND APPARATUS FOR REWORKING STRUCTURES</pat:Heading><pat:Heading pat:id="h-2">BACKGROUND INFORMATION</pat:Heading><pat:P pat:pNumber="2" pat:id="p-2">1.   Field: </pat:P><pat:P pat:pNumber="3" pat:id="p-3">[0001] The  present  disclosure  generally  relates  to equipment and processes for reworking and/or reinforcing structures,  especially   composites,  and  deals   more particularly with a method and apparatus for reworking structures from one side thereof. </pat:P><pat:P pat:pNumber="4" pat:id="p-4">2.   Background: </pat:P><pat:P pat:pNumber="5" pat:id="p-5">[0002] Composite  structures  sometimes have   localized areas containing one or more inconsistencies that may require rework in order to bring the structure within design tolerances, or to reinforce the area. </pat:P><pat:P pat:pNumber="6" pat:id="p-6">[0003] One technique for reworking localized areas of structures involves mechanically fastening a patch over the area, however fasteners may increase aircraft weight and/or drag on the aircraft, and may be esthetically undesirable in some applications. </pat:P><pat:P pat:pNumber="7" pat:id="p-7">[0004] Similarly, bonded rework patches may also require the use of mechanical fasteners to provide secondary load paths forming an arrestment mechanism to limit the growth of an inconsistency. </pat:P><pat:P pat:pNumber="8" pat:id="p-8">[0005] Still another technique for reworking structures, referred to as a wet layup technique, involves hand- layup of wet plies with fiber reinforcement, such as a woven or knitted fabric, and applying wet resin to the plies as they are laid up. The wet layup technique may result in air entrapment within the patch which may form <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='2'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData>undesirable porosities in the reworked area.       These porosities  may  have  an   undesirable  affect  on  the reworked area and may make it difficult to verify that a reworked  area  meets  specifications.  The   wet  layup technique may also be labor intensive, require repair technicians to come into proximity with wet resin, and may require excessive cleanup activity. </pat:P><pat:P pat:pNumber="9" pat:id="p-9">[0006] In  some  applications, the problems discussed above may be avoided by employing resin infusion of a dry fiber preform patch. After placing a dry fiber preform on a structure such as a scarfed skin, resin is infused into the fiber preform from the outer side of the skin, while excess resin is being drawn out from the preform from the inner side of the skin. This technique, while effective, requires physical access to both sides of the structure, for example, to the inner and outer sides of a skin. Consequently, this technique may not be suitable for use in applications where one side of the structure is difficult or impossible to access. </pat:P><pat:P pat:pNumber="10" pat:id="p-10">[0007] Accordingly, there is a need for a method and apparatus   for    reworking    structures,   especially composites, which reduce or eliminate porosities due to air entrapment. There is also a need for a method and apparatus as described above may be adapted for use in applications where access to only one side of the structure is possible. </pat:P><pat:P pat:pNumber="11" pat:id="p-11"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>2</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='3'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData></pat:P><pat:Heading pat:id="h-3"><pat:OCRConfidenceData pat:levelNumber='8855'>SUMM</pat:OCRConfidenceData>ARY</pat:Heading><pat:P pat:pNumber="12" pat:id="p-12">[0008] The disclosed embodiments provide a method and apparatus for reworking structures using resin infusion of a dry fiber preform patch that can be installed and infused with from only one side of the structure, such as from the outside of an aircraft skin. Areas of high pressure within the patch during the resin infusion process are substantially eliminated, thereby avoiding air entrapment and related porosities in reworked area. The embodiments reduce labor, avoid the need for human contact  with  wet  resins  and  allow   rework  of  load carrying composite structural members. The disclosed method may be implemented using controlled atmospheric pressure resin infusion, allowing the properties of the structure to be optimized. </pat:P><pat:P pat:pNumber="13" pat:id="p-13">[0009] According to one disclosed embodiment, a method is provided of reworking an area of a structure. The method comprises    placing a patch on the structure, inserting a vacuum source into the patch from an outer side of the patch, and using the vacuum source to creating a very low pressure area causing the incoming higher pressure resin to flow through the patch to an inner side of the patch. The patch may be a dry fiber patch. The method may further comprise placing a vacuum bag over the outer side of the patch, evacuating the bag thereby  compacting  the   dry  fiber  patch,   and  then infusing the patch with resin by flowing resin into the patch from the outer side thereof. The method may also include removing the vacuum source from the patch after the patch has been infused with resin. The method may further comprise forming a scarf partially through the thickness of the structure, and placing the patch on the <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>3</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='4'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData>structure includes placing the inner side of the patch against a bottom of the scarf.      Inserting the vacuum source includes inserting a hollow needle down through the thickest part of the fiber patch to substantially the bottom of the scarf. Inserting the vacuum source further includes inserting the hollow needle through the vacuum bag, and forming a substantially vacuum tight seal between the hollow needle and the vacuum bag. Removing the vacuum source from the fiber patch includes withdrawing the hollow needle from the fiber patch and from the vacuum bag, and sealing a hole in the vacuum bag resulting from penetration of the vacuum bag by the needle. The method may further comprise compacting the resin infused patch after the needle has been withdrawn from the fiber patch, and the bag has been sealed, by evacuating the vacuum bag. Infusing the patch with resin is performed using differential resin pressure. Flowing resin into the fiber patch from the outer side thereof includes placing a resin distribution tube on the outer side of the fiber patch beneath the vacuum bag, and supplying resin to the resin distribution tube. </pat:P><pat:P pat:pNumber="14" pat:id="p-14">[0010] According to   another disclosed   embodiment, a method is provided of reworking an area of a structure, comprising forming a scarf partially through a thickness of the structure, fabricating a dry fiber patch having an inner side and an outer side, and installing the patch within the scarf, including placing the inner side of the patch against the structure at a bottom of the scarf. The method also includes installing a vacuum bag over the fiber patch, inserting a vacuum device from the outer side of the patch through the patch, evacuating the bag thereby compacting the dry fiber patch, and then infusing the patch with resin, and using the vacuum <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='7'>4</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='5'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData>device to force resin through the patch to the inner side of the patch. The method further includes removing the vacuum device from the patch after the patch has been infused with resin. Inserting the vacuum device through the patch includes inserting a hollow needle through the vacuum bag and the patch until a tip of the vacuum needle has substantially penetrated a thickest part of the patch. The method may further comprise forming a substantially vacuum tight seal between the vacuum bag and the vacuum needle, and withdrawing the vacuum needle from the patch and from the bag after the patch has been infused with resin. The method may also comprise sealing a hole in the vacuum bag resulting from withdrawal of the vacuum needle from the vacuum bag. Infusing   the  patch   with   resin  is   performed   by introducing resin under controlled atmospheric pressure on the outer side of the patch. Introducing the resin includes placing a spiral wrap tube around the periphery of the outer side of the patch, and coupling the spiral wrap tube with a reservoir of resin adapted to supply resin to the spiral wrap tube at partial atmospheric pressure. The   method  may   further  comprise  removing excess resin from the patch through the end of the hollow needle. </pat:P><pat:P pat:pNumber="15" pat:id="p-15">[0011] According to still another embodiment, a method is provided of reworking an area of the composite structure  from  only   one  side  thereof. The    method comprises forming a scarf in one side of the composite structure,  installing  a  fiber patch    in  the  scarf, including placing including an inner side of the patch in contact with the structure, installing a vacuum bag over the patch, and inserting a hollow needle through the vacuum bag and down into the patch until a tip of <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>5</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='6'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData>the needle is near the inner side of the patch. The method further comprises forming a seal between the hollow needle and the vacuum bag, coupling the hollow needle with a vacuum reservoir, infusing the patch with resin by flowing resin into the outer side of the patch, using the hollow needle and the vacuum reservoir to force the resin to the inner side of the fiber patch, and removing excess resin in the fiber patch through the hollow needle. The method also comprises removing the hollow needle from the patch after the patch has been infused with resin. The patch may have an area of maximum thickness.     Inserting the hollow needle is performed by passing a tip of the hollow needle through the area of maximum thickness of the fiber patch. The method further comprises withdrawing the hollow needle from the patch and from the vacuum bag, and sealing a hole in the vacuum bag resulting from the withdrawal of the hollow needle from the vacuum bag.     Flowing resin into the outer side of the patch and using the hollow needle and vacuum reservoir force the resin to the inner side  of   the  fiber  patch   may  be  performed   using controlled partial atmospheric pressure resin infusion. </pat:P><pat:P pat:pNumber="16" pat:id="p-16">[0012] According to a further embodiment, apparatus is provided for reworking an area of a composite structure using resin infusion of a dry fiber patch having inner and outer sides. The apparatus comprises a vacuum bag adapted to be placed over the outer side of the patch for compacting the patch, and a hollow needle passing through the vacuum bag and adapted to extend down through a thickness of the patch. The apparatus also comprises a vacuum seal between the hollow needle and the vacuum bag, and a vacuum line coupled with the hollow needle for generating a vacuum at the inner side <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>6</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='7'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData>of the patch. The apparatus may further comprise a reservoir of resin for supplying resin to the outer side of  the  patch   at  a  controlled  partial   atmospheric pressure, and a vacuum source coupled with the hollow needle for generating a vacuum at the inner side of the patch and forcing excess resin away from the patch. </pat:P><pat:P pat:pNumber="17" pat:id="p-17">[0013] The features, functions, and advantages can be achieved independently in various embodiments of the present disclosure or may be combined in yet other embodiments in which further details can be seen with reference to the following description and drawings. </pat:P><pat:P pat:pNumber="18" pat:id="p-18"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>7</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='8'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData></pat:P><pat:Heading pat:id="h-4">BRIEF DESCRIPTION OF THE DRAWINGS</pat:Heading><pat:P pat:pNumber="19" pat:id="p-19">[0014] The novel features believed characteristic of the illustrative embodiments are set forth in the appended claims.  The illustrative embodiments, however, as well as a preferred mode of use, further objectives and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment  of the present    disclosure  when  read  in conjunction with the accompanying drawings, wherein: </pat:P><pat:P pat:pNumber="20" pat:id="p-20">[0015] Figure 1 is an illustration of a functional block diagram  of  apparatus  for  reworking  an   area  of  a structure from one side thereof. </pat:P><pat:P pat:pNumber="21" pat:id="p-21">[0016] Figure 2 is an illustration of a perspective view of a structure having an area being reworked using the disclosed apparatus. </pat:P><pat:P pat:pNumber="22" pat:id="p-22"><pat:PatentImage pat:id='ID-00002' pat:imageContentCategory='Chemistry' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>13761785.02-07-2013.HCWE2Q9MPXXIFW3.SPEC_29568053.17.402.1925.2076.1965.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.133</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>5.58</com:WidthMeasure><com:ALTText>Chemistry</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage>perspective view of the area shown in Figure 2. </pat:P><pat:P pat:pNumber="23" pat:id="p-23">[0018] Figure 4 is an illustration of a cross-sectional view taken along the <pat:PartName pat:idref='PN-00001'>line</pat:PartName> <pat:PartNumber pat:id='PN-00001'>4</pat:PartNumber>-4 in Figure 2. </pat:P><pat:P pat:pNumber="24" pat:id="p-24"><pat:PatentImage pat:id='ID-00003' pat:imageContentCategory='Drawing' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>13761785.02-07-2013.HCWE2Q9MPXXIFW3.SPEC_29568053.21.402.2434.2086.2474.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.133</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>5.613</com:WidthMeasure><com:ALTText>Drawing</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage>large area of a structure being reworked using an alternate form of the apparatus. </pat:P><pat:P pat:pNumber="25" pat:id="p-25">[0020] Figure 6 is an illustration of a flow diagram of a method of reworking a structure. </pat:P><pat:P pat:pNumber="26" pat:id="p-26">[0021] Figure 7 is an illustration of a flow diagram of a method of reworking a structure from one side thereof. </pat:P><pat:P pat:pNumber="27" pat:id="p-27"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>8</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='9'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData>[0022] Figure 8 is an illustration of a flow diagram of a method of reworking an area of a composite skin using the disclosed method and apparatus. </pat:P><pat:P pat:pNumber="28" pat:id="p-28">[0023] Figure 9 is an illustration of a flow diagram of aircraft production and service methodology. </pat:P><pat:P pat:pNumber="29" pat:id="p-29">[0024] Figure 10 is illustration of a block diagram of an aircraft. </pat:P><pat:P pat:pNumber="30" pat:id="p-30"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>9</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='10'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData><pat:PatentImage pat:id='ID-00004' pat:imageContentCategory='Chemistry' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>13761785.02-07-2013.HCWE2Q9MPXXIFW3.SPEC_29568055.3.402.480.2089.520.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.133</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>5.623</com:WidthMeasure><com:ALTText>Chemistry</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:Heading pat:id="h-5">DETAILED DESCRIPTION</pat:Heading><pat:P pat:pNumber="31" pat:id="p-31">embodiments  relate  to  a  method   and  apparatus  for reworking an <pat:PartName pat:idref='PN-00002'>area</pat:PartName> <pat:PartNumber pat:id='PN-00002'>22</pat:PartNumber> (hereinafter sometimes also called "rework area") of a <pat:PartName pat:idref='PN-00003'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00003'>20</pat:PartNumber> that may contain inconsistencies  (not  shown),  or  which   may  require reinforcement. The <pat:PartName pat:idref='PN-00004'>area</pat:PartName> <pat:PartNumber pat:id='PN-00004'>22</pat:PartNumber> may be reworked using a <pat:PartName pat:idref='PN-00005'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00005'>24</pat:PartNumber> in order to bring the <pat:PartName pat:idref='PN-00006'>area</pat:PartName> <pat:PartNumber pat:id='PN-00006'>22</pat:PartNumber> to within design     or    performance     specifications.     The inconsistencies may comprise, without limitation, impact damage, cracks, fractures or porosities which occur at the time of manufacture, or while the <pat:PartName pat:idref='PN-00007'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00007'>20</pat:PartNumber> is in service. </pat:P><pat:P pat:pNumber="32" pat:id="p-32">[0026] In the illustrated example, the <pat:PartName pat:idref='PN-00008'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00008'>20</pat:PartNumber> comprises a <pat:PartName pat:idref='PN-00009'>composite aircraft skin</pat:PartName> <pat:PartNumber pat:id='PN-00009'>20</pat:PartNumber>, however the disclosed  method  may  be  employed   to  rework  other structures  formed   from  any  of   various  materials, including but not limited to metals, metal composites, and ceramics. </pat:P><pat:P pat:pNumber="33" pat:id="p-33">[0027] The <pat:PartName pat:idref='PN-00010'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00010'>20</pat:PartNumber> <pat:PartName pat:idref='PN-00011'>includes inner side</pat:PartName> <pat:PartNumber pat:id='PN-00011'>34</pat:PartNumber> which may be    difficult    or    impossible   to    access    by maintenance/repair personnel, and an <pat:PartName pat:idref='PN-00012'>outer side</pat:PartName> <pat:PartNumber pat:id='PN-00012'>32</pat:PartNumber> that can be accessed by personnel for purposes of reworking, reinforcing and/or repairing   (collectively hereinafter referred to as "reworking") the <pat:PartName pat:idref='PN-00013'>area</pat:PartName> <pat:PartNumber pat:id='PN-00013'>22</pat:PartNumber> using the <pat:PartName pat:idref='PN-00014'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00014'>24</pat:PartNumber>. As will be discussed below in more detail, the disclosed method and apparatus allow the <pat:PartName pat:idref='PN-00015'>area</pat:PartName> <pat:PartNumber pat:id='PN-00015'>22</pat:PartNumber> to be reworked from only one side of the <pat:PartName pat:idref='PN-00016'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00016'>20</pat:PartNumber>, which in the illustrated example, is the <pat:PartName pat:idref='PN-00017'>outer side</pat:PartName> <pat:PartNumber pat:id='PN-00017'>32</pat:PartNumber> of the <pat:PartName pat:idref='PN-00018'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00018'>20</pat:PartNumber><pat:OCRConfidenceData pat:levelNumber='8'>.</pat:OCRConfidenceData> </pat:P><pat:P pat:pNumber="34" pat:id="p-34"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>10</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='11'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData>[0028] In order to rework the <pat:PartName pat:idref='PN-00019'>area</pat:PartName> <pat:PartNumber pat:id='PN-00019'>22</pat:PartNumber> from the <pat:PartName pat:idref='PN-00020'>outer side</pat:PartName> <pat:PartNumber pat:id='PN-00020'>32</pat:PartNumber>, a portion of the <pat:PartName pat:idref='PN-00021'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00021'>20</pat:PartNumber> containing the inconsistencies may be removed within the <pat:PartName pat:idref='PN-00022'>rework area</pat:PartName> <pat:PartNumber pat:id='PN-00022'>22</pat:PartNumber>, referred to as scarfing, thereby forming a <pat:PartName pat:idref='PN-00023'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00023'>26</pat:PartNumber> having a depth "d" that is less than the thickness "t" of the <pat:PartName pat:idref='PN-00024'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00024'>20</pat:PartNumber>. In other words, the <pat:PartName pat:idref='PN-00025'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00025'>26</pat:PartNumber> only partially penetrates the thickness "t" of the <pat:PartName pat:idref='PN-00026'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00026'>20</pat:PartNumber>. In the illustrated example, the <pat:PartName pat:idref='PN-00027'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00027'>26</pat:PartNumber> <pat:PartName pat:idref='PN-00028'>has tapered sides</pat:PartName> <pat:PartNumber pat:id='PN-00028'>27</pat:PartNumber>, and a <pat:PartName pat:idref='PN-00029'>flat bottom</pat:PartName> <pat:PartNumber pat:id='PN-00029'>30</pat:PartNumber>, however in other applications, <pat:PartName pat:idref='PN-00030'>sides</pat:PartName> <pat:PartNumber pat:id='PN-00030'>27</pat:PartNumber> may not be tapered, and the <pat:PartName pat:idref='PN-00031'>bottom</pat:PartName> <pat:PartNumber pat:id='PN-00031'>30</pat:PartNumber> may not be flat. </pat:P><pat:P pat:pNumber="35" pat:id="p-35">[0029] The <pat:PartName pat:idref='PN-00032'>rework area</pat:PartName> <pat:PartNumber pat:id='PN-00032'>38</pat:PartNumber> having been scarfed from the <pat:PartName pat:idref='PN-00033'>outer side</pat:PartName> <pat:PartNumber pat:id='PN-00033'>32</pat:PartNumber> to a desired depth "d", a <pat:PartName pat:idref='PN-00034'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00034'>24</pat:PartNumber> is fabricated and placed in the <pat:PartName pat:idref='PN-00035'>scarfed cavity</pat:PartName> <pat:PartNumber pat:id='PN-00035'>26</pat:PartNumber>. The <pat:PartName pat:idref='PN-00036'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00036'>24</pat:PartNumber> has an <pat:PartName pat:idref='PN-00037'>inner side</pat:PartName> <pat:PartNumber pat:id='PN-00037'>33</pat:PartNumber> and an <pat:PartName pat:idref='PN-00038'>outer side</pat:PartName> <pat:PartNumber pat:id='PN-00038'>37</pat:PartNumber>. The <pat:PartName pat:idref='PN-00039'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00039'>24</pat:PartNumber> comprises a dry fiber preform fabricated,  for   example,  by  stacking  and   tacking together layers of dry fiber reinforcement which may comprise knitted or woven fabric. The geometry of the <pat:PartName pat:idref='PN-00040'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00040'>24</pat:PartNumber> may match that of the <pat:PartName pat:idref='PN-00041'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00041'>26</pat:PartNumber>. For example, in the illustrated application, the outer edges of the <pat:PartName pat:idref='PN-00042'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00042'>24</pat:PartNumber> may be tapered to match the <pat:PartName pat:idref='PN-00043'>tapered sides</pat:PartName> <pat:PartNumber pat:id='PN-00043'>27</pat:PartNumber> of the <pat:PartName pat:idref='PN-00044'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00044'>26</pat:PartNumber>. In other applications, however, the <pat:PartName pat:idref='PN-00045'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00045'>26</pat:PartNumber> and the <pat:PartName pat:idref='PN-00046'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00046'>24</pat:PartNumber> may have other cross-sectional profiles, including  but  not   limited  to  a   stepped  profile. Furthermore, while a <pat:PartName pat:idref='PN-00047'>dry fiber rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00047'>24</pat:PartNumber> is illustrated, it   may be possible to     carry  out  the disclosed method using a fibrous reinforcement patch that has been tackified or pre-impregnated (pre-preg) with resin. </pat:P><pat:P pat:pNumber="36" pat:id="p-36"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>11</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='12'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData>[0030] A <pat:PartName pat:idref='PN-00048'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00048'>36</pat:PartNumber>, which may be flexible, is placed over the <pat:PartName pat:idref='PN-00049'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00049'>24</pat:PartNumber> and sealed to the <pat:PartName pat:idref='PN-00050'>surface</pat:PartName> <pat:PartNumber pat:id='PN-00050'>38</pat:PartNumber> of the <pat:PartName pat:idref='PN-00051'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00051'>20</pat:PartNumber> on the <pat:PartName pat:idref='PN-00052'>outer side</pat:PartName> <pat:PartNumber pat:id='PN-00052'>32</pat:PartNumber> of the <pat:PartName pat:idref='PN-00053'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00053'>24</pat:PartNumber>. The <pat:PartName pat:idref='PN-00054'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00054'>36</pat:PartNumber> is coupled with a <pat:PartName pat:idref='PN-00055'>suitable vacuum generator</pat:PartName> <pat:PartNumber pat:id='PN-00055'>45</pat:PartNumber> and <pat:PartName pat:idref='PN-00056'>reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00056'>44</pat:PartNumber> which evacuates the <pat:PartName pat:idref='PN-00057'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00057'>36</pat:PartNumber> in order to compact the <pat:PartName pat:idref='PN-00058'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00058'>24</pat:PartNumber> <pat:PatentImage pat:id='ID-00005' pat:imageContentCategory='Table' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>13761785.02-07-2013.HCWE2Q9MPXXIFW3.SPEC_29568057.8.391.819.2087.860.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.137</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>5.653</com:WidthMeasure><com:ALTText>Table</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage>infusion of the <pat:PartName pat:idref='PN-00059'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00059'>24</pat:PartNumber> may be carried out using a resi<pat:PartName pat:idref='PN-00060'>n   infusion  system </pat:PartName> <pat:PartNumber pat:id='PN-00060'>35</pat:PartNumber> comprising a <pat:PartName pat:idref='PN-00061'>controlled pressure resin reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00061'>46</pat:PartNumber>, a <pat:PartName pat:idref='PN-00062'>removable vacuum source</pat:PartName> <pat:PartNumber pat:id='PN-00062'>42</pat:PartNumber> and a <pat:PartName pat:idref='PN-00063'>controlled vacuum reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00063'>44</pat:PartNumber>. Some components of the <pat:PartName pat:idref='PN-00064'>resin infusion system</pat:PartName> <pat:PartNumber pat:id='PN-00064'>35</pat:PartNumber> may be similar to those shown in U.S. Patent No. 7,334,782 issued February 26, 2008, the entire disclosure of which is incorporated by reference  herein.   The  above  mentioned  U.S. Patent discloses   a  controlled   atmospheric  pressure   resin infusion system (CAPRI) in which the <pat:PartName pat:idref='PN-00065'>resin reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00065'>46</pat:PartNumber> is evacuated to a pressure below atmospheric pressure and may be used in combination with cyclic (repeated) compaction by the <pat:PartName pat:idref='PN-00066'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00066'>36</pat:PartNumber> to control a vacuum assisted resin transfer process. It may be possible, however, to carry out the disclosed method using other types  of   resin  infusion  techniques  and   equipment. Moreover, the disclosed method may be carried out within an autoclave. </pat:P><pat:P pat:pNumber="37" pat:id="p-37">[0031] The vac<pat:PartName pat:idref='PN-00067'>uum   source </pat:PartName> <pat:PartNumber pat:id='PN-00067'>42</pat:PartNumber>  is placed beneath    the thickest part of the <pat:PartName pat:idref='PN-00068'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00068'>24</pat:PartNumber>, along the <pat:PartName pat:idref='PN-00069'>inner side of</pat:PartName> <pat:PartNumber pat:id='PN-00069'>33</pat:PartNumber> of the <pat:PartName pat:idref='PN-00070'>repair patch</pat:PartName> <pat:PartNumber pat:id='PN-00070'>24</pat:PartNumber>, near the <pat:PartName pat:idref='PN-00071'>bottom</pat:PartName> <pat:PartNumber pat:id='PN-00071'>30</pat:PartNumber> of the <pat:PartName pat:idref='PN-00072'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00072'>26</pat:PartNumber>. The <pat:PartName pat:idref='PN-00073'>vacuum source</pat:PartName> <pat:PartNumber pat:id='PN-00073'>42</pat:PartNumber> is coupled with the <pat:PartName pat:idref='PN-00074'>vacuum reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00074'>44</pat:PartNumber> by a <pat:PartName pat:idref='PN-00075'>vacuum line</pat:PartName> <pat:PartNumber pat:id='PN-00075'>40</pat:PartNumber> that may pass through the <pat:PartName pat:idref='PN-00076'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00076'>36</pat:PartNumber>. <pat:PartName pat:idref='PN-00077'>Resin from resin reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00077'>46</pat:PartNumber> is supplied through a <pat:PartName pat:idref='PN-00078'>resin supply tube</pat:PartName> <pat:PartNumber pat:id='PN-00078'>48</pat:PartNumber> to the <pat:PartName pat:idref='PN-00079'>outer side</pat:PartName> <pat:PartNumber pat:id='PN-00079'>37</pat:PartNumber> of the <pat:PartName pat:idref='PN-00080'>patch</pat:PartName> <pat:PartNumber pat:id='PN-00080'>24</pat:PartNumber>. The vacuum source <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>12</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='13'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData>42 functions to reduce the pressure along the <pat:PartName pat:idref='PN-00081'>inner side</pat:PartName> <pat:PartNumber pat:id='PN-00081'>33</pat:PartNumber> of the <pat:PartName pat:idref='PN-00082'>patch</pat:PartName> <pat:PartNumber pat:id='PN-00082'>24</pat:PartNumber>, at the <pat:PartName pat:idref='PN-00083'>bottom</pat:PartName> <pat:PartNumber pat:id='PN-00083'>30</pat:PartNumber> of the <pat:PartName pat:idref='PN-00084'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00084'>26</pat:PartNumber>, to a pressure level that is lower than the pressure within the <pat:PartName pat:idref='PN-00085'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00085'>36</pat:PartNumber> at the <pat:PartName pat:idref='PN-00086'>outer side</pat:PartName> <pat:PartNumber pat:id='PN-00086'>37</pat:PartNumber> of the <pat:PartName pat:idref='PN-00087'>patch</pat:PartName> <pat:PartNumber pat:id='PN-00087'>24</pat:PartNumber> produced by the <pat:PartName pat:idref='PN-00088'>vacuum generator</pat:PartName> <pat:PartNumber pat:id='PN-00088'>45</pat:PartNumber>.         The pressure reduction created by the <pat:PartName pat:idref='PN-00089'>vacuum source</pat:PartName> <pat:PartNumber pat:id='PN-00089'>42</pat:PartNumber> along the <pat:PartName pat:idref='PN-00090'>inner side</pat:PartName> <pat:PartNumber pat:id='PN-00090'>33</pat:PartNumber> of the <pat:PartName pat:idref='PN-00091'>patch</pat:PartName> <pat:PartNumber pat:id='PN-00091'>24</pat:PartNumber> results in a pressure differential between the inner and <pat:PartName pat:idref='PN-00092'>outer sides</pat:PartName> <pat:PartNumber pat:id='PN-00092'>33</pat:PartNumber>, 37 respectively of the <pat:PartName pat:idref='PN-00093'>patch</pat:PartName> <pat:PartNumber pat:id='PN-00093'>24</pat:PartNumber>, that forces resin to flow through the entire thickness of the <pat:PartName pat:idref='PN-00094'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00094'>24</pat:PartNumber>. The <pat:PartName pat:idref='PN-00095'>vacuum source</pat:PartName> <pat:PartNumber pat:id='PN-00095'>42</pat:PartNumber> also eliminates high-pressure areas in the thickest part of the <pat:PartName pat:idref='PN-00096'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00096'>24</pat:PartNumber>, near the <pat:PartName pat:idref='PN-00097'>inner side</pat:PartName> <pat:PartNumber pat:id='PN-00097'>33</pat:PartNumber>, which may otherwise result in air entrapment causing porosities. Excess resin flowing through the <pat:PartName pat:idref='PN-00098'>patch</pat:PartName> <pat:PartNumber pat:id='PN-00098'>24</pat:PartNumber> to the <pat:PartName pat:idref='PN-00099'>inner side</pat:PartName> <pat:PartNumber pat:id='PN-00099'>33</pat:PartNumber> of the <pat:PartName pat:idref='PN-00100'>patch</pat:PartName> <pat:PartNumber pat:id='PN-00100'>24</pat:PartNumber> at the <pat:PartName pat:idref='PN-00101'>bottom</pat:PartName> <pat:PartNumber pat:id='PN-00101'>30</pat:PartNumber> of the <pat:PartName pat:idref='PN-00102'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00102'>26</pat:PartNumber> is moved away through the  va<pat:PartName pat:idref='PN-00103'>cuum  line </pat:PartName> <pat:PartNumber pat:id='PN-00103'>40</pat:PartNumber>  into the    va<pat:PartName pat:idref='PN-00104'>cuum  reservoir </pat:PartName> <pat:PartNumber pat:id='PN-00104'>44</pat:PartNumber>. Following resin infusion of the <pat:PartName pat:idref='PN-00105'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00105'>24</pat:PartNumber>, the <pat:PartName pat:idref='PN-00106'>vacuum source</pat:PartName> <pat:PartNumber pat:id='PN-00106'>42</pat:PartNumber> is removed from the <pat:PartName pat:idref='PN-00107'>resin infused patch</pat:PartName> <pat:PartNumber pat:id='PN-00107'>24</pat:PartNumber> and sealed before curing. </pat:P><pat:P pat:pNumber="38" pat:id="p-38">[0032] Attention is now directed to Figures 2, 3 and 4 which illustrate one practical embodiment of apparatus for reworking an <pat:PartName pat:idref='PN-00108'>area</pat:PartName> <pat:PartNumber pat:id='PN-00108'>26</pat:PartNumber> of a <pat:PartName pat:idref='PN-00109'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00109'>20</pat:PartNumber>. In this example, the <pat:PartName pat:idref='PN-00110'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00110'>20</pat:PartNumber> comprises a <pat:PartName pat:idref='PN-00111'>composite laminate skin</pat:PartName> <pat:PartNumber pat:id='PN-00111'>20</pat:PartNumber>, such as those used in the aircraft industry. The <pat:PartName pat:idref='PN-00112'>rework area</pat:PartName> <pat:PartNumber pat:id='PN-00112'>22</pat:PartNumber> <pat:PartName pat:idref='PN-00113'>is scarfed (Figures</pat:PartName> <pat:PartNumber pat:id='PN-00113'>2</pat:PartNumber> and 4) only partially  through   the  thickness   of  the  sk<pat:PartName pat:idref='PN-00114'>in  </pat:PartName> <pat:PartNumber pat:id='PN-00114'>20</pat:PartNumber>, resulting in a <pat:PartName pat:idref='PN-00115'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00115'>26</pat:PartNumber> <pat:PartName pat:idref='PN-00116'>having tapered sides</pat:PartName> <pat:PartNumber pat:id='PN-00116'>27</pat:PartNumber> (see Figure 3) and a <pat:PartName pat:idref='PN-00117'>generally flat bottom</pat:PartName> <pat:PartNumber pat:id='PN-00117'>30</pat:PartNumber>. A <pat:PartName pat:idref='PN-00118'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00118'>24</pat:PartNumber> comprising a dry fiber preform, is fabricated and placed within the <pat:PartName pat:idref='PN-00119'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00119'>26</pat:PartNumber>, with the <pat:PartName pat:idref='PN-00120'>inner side</pat:PartName> <pat:PartNumber pat:id='PN-00120'>33</pat:PartNumber> of the <pat:PartName pat:idref='PN-00121'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00121'>24</pat:PartNumber> in contact with the <pat:PartName pat:idref='PN-00122'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00122'>20</pat:PartNumber>. The <pat:PartName pat:idref='PN-00123'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00123'>24</pat:PartNumber> may have tapered edges <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>13</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='14'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData>29 <pat:PartName pat:idref='PN-00124'>(Figure</pat:PartName> <pat:PartNumber pat:id='PN-00124'>4</pat:PartNumber>) substantially matching the <pat:PartName pat:idref='PN-00125'>tapered sides</pat:PartName> <pat:PartNumber pat:id='PN-00125'>27</pat:PartNumber> of the <pat:PartName pat:idref='PN-00126'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00126'>26</pat:PartNumber>. A <pat:PartName pat:idref='PN-00127'>release ply</pat:PartName> <pat:PartNumber pat:id='PN-00127'>66</pat:PartNumber> is placed over the <pat:PartName pat:idref='PN-00128'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00128'>24</pat:PartNumber>. The <pat:PartName pat:idref='PN-00129'>release ply</pat:PartName> <pat:PartNumber pat:id='PN-00129'>66</pat:PartNumber> allows resin to flow therethrough and may comprise, without <pat:PatentImage pat:id='ID-00006' pat:imageContentCategory='Chemistry' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>13761785.02-07-2013.HCWE2Q9MPXXIFW3.SPEC_29568059.6.395.642.2086.690.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.16</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>5.637</com:WidthMeasure><com:ALTText>Chemistry</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage>exemplary embodiment shown in the figures, the <pat:PartName pat:idref='PN-00130'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00130'>26</pat:PartNumber> and the <pat:PartName pat:idref='PN-00131'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00131'>24</pat:PartNumber> are each substantially circular in shape. However it should be noted that the disclosed method and apparatus may be used to <pat:PartName pat:idref='PN-00132'>rework areas</pat:PartName> <pat:PartNumber pat:id='PN-00132'>22</pat:PartNumber> in which the <pat:PartName pat:idref='PN-00133'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00133'>26</pat:PartNumber> and the <pat:PartName pat:idref='PN-00134'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00134'>24</pat:PartNumber> are not circular, e.g. oval, square etc. </pat:P><pat:P pat:pNumber="39" pat:id="p-39">[0033] One or more plies of a <pat:PartName pat:idref='PN-00135'>porous flow media</pat:PartName> <pat:PartNumber pat:id='PN-00135'>62</pat:PartNumber> (two plies are shown in the drawings) such as, without limitation, fiberglass, cover the <pat:PartName pat:idref='PN-00136'>release ply</pat:PartName> <pat:PartNumber pat:id='PN-00136'>66</pat:PartNumber> and functions to distribute resin over the area of the <pat:PartName pat:idref='PN-00137'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00137'>24</pat:PartNumber>. The flow <pat:PartName pat:idref='PN-00138'>media     </pat:PartName> <pat:PartNumber pat:id='PN-00138'>62</pat:PartNumber> may include a central, generally circular, or <pat:PartName pat:idref='PN-00139'>other shaped cutout</pat:PartName> <pat:PartNumber pat:id='PN-00139'>64</pat:PartNumber> that functions to create a "dead zone" which aids in generating a desired wavefront of resin flow into the <pat:PartName pat:idref='PN-00140'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00140'>24</pat:PartNumber>. In some applications, the <pat:PartName pat:idref='PN-00141'>cutout</pat:PartName> <pat:PartNumber pat:id='PN-00141'>64</pat:PartNumber> may not be necessary where not required by the geometry of the <pat:PartName pat:idref='PN-00142'>patch</pat:PartName> <pat:PartNumber pat:id='PN-00142'>24</pat:PartNumber>. A circularly shaped, spiral wrap, <pat:PartName pat:idref='PN-00143'>resin distribution tube</pat:PartName> <pat:PartNumber pat:id='PN-00143'>60</pat:PartNumber>, which may be formed of a nylon or similar material, is disposed on top of the <pat:PartName pat:idref='PN-00144'>flow media</pat:PartName> <pat:PartNumber pat:id='PN-00144'>62</pat:PartNumber>,  and  extends   around  its  periphery.  The   res<pat:PartName pat:idref='PN-00145'>in distribution  tube  </pat:PartName> <pat:PartNumber pat:id='PN-00145'>60</pat:PartNumber>  may   have  other   geometries, depending upon the application, and is coupled with a <pat:PartName pat:idref='PN-00146'>resin supply tube</pat:PartName> <pat:PartNumber pat:id='PN-00146'>48</pat:PartNumber>. The <pat:PartName pat:idref='PN-00147'>resin supply tube</pat:PartName> <pat:PartNumber pat:id='PN-00147'>48</pat:PartNumber> includes an <pat:PartName pat:idref='PN-00148'>inlet</pat:PartName> <pat:PartNumber pat:id='PN-00148'>54</pat:PartNumber> that is coupled with the <pat:PartName pat:idref='PN-00149'>resin reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00149'>46</pat:PartNumber> (<pat:PartName pat:idref='PN-00150'>Figure </pat:PartName> <pat:PartNumber pat:id='PN-00150'>1</pat:PartNumber>)  which   supplies  resin  under   controlled pressure to the <pat:PartName pat:idref='PN-00151'>resin distribution tube</pat:PartName> <pat:PartNumber pat:id='PN-00151'>60</pat:PartNumber>. The <pat:PartName pat:idref='PN-00152'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00152'>36</pat:PartNumber> covers the <pat:PartName pat:idref='PN-00153'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00153'>24</pat:PartNumber> as well as the <pat:PartName pat:idref='PN-00154'>resin distribution tube</pat:PartName> <pat:PartNumber pat:id='PN-00154'>60</pat:PartNumber>, and is sealed to the outer surface <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>14</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='15'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData>38 of the <pat:PartName pat:idref='PN-00155'>skin</pat:PartName> <pat:PartNumber pat:id='PN-00155'>20</pat:PartNumber> by means of a <pat:PartName pat:idref='PN-00156'>suitable sealant</pat:PartName> <pat:PartNumber pat:id='PN-00156'>70</pat:PartNumber>, which may comprise a sealant tape. </pat:P><pat:P pat:pNumber="40" pat:id="p-40">[0034] The <pat:PartName pat:idref='PN-00157'>vacuum source</pat:PartName> <pat:PartNumber pat:id='PN-00157'>42</pat:PartNumber>, previously discussed in connection with Figure 1, may comprise a vacuum device such as a <pat:PartName pat:idref='PN-00158'>vacuum needle</pat:PartName> <pat:PartNumber pat:id='PN-00158'>50</pat:PartNumber>. A <pat:PartName pat:idref='PN-00159'>tip</pat:PartName> <pat:PartNumber pat:id='PN-00159'>25</pat:PartNumber> on one end of the <pat:PartName pat:idref='PN-00160'>hollow needle</pat:PartName> <pat:PartNumber pat:id='PN-00160'>50</pat:PartNumber> is open while the other end of the <pat:PartName pat:idref='PN-00161'>hollow needle</pat:PartName> <pat:PartNumber pat:id='PN-00161'>50</pat:PartNumber> is coupled with the <pat:PartName pat:idref='PN-00162'>vacuum line</pat:PartName> <pat:PartNumber pat:id='PN-00162'>40</pat:PartNumber>. The <pat:PartName pat:idref='PN-00163'>hollow needle</pat:PartName> <pat:PartNumber pat:id='PN-00163'>50</pat:PartNumber> <pat:PartName pat:idref='PN-00164'>penetrates</pat:PartName> <pat:PartNumber pat:id='PN-00164'>47</pat:PartNumber> the <pat:PartName pat:idref='PN-00165'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00165'>36</pat:PartNumber> and passes through the <pat:PartName pat:idref='PN-00166'>central cutout</pat:PartName> <pat:PartNumber pat:id='PN-00166'>64</pat:PartNumber> in the <pat:PartName pat:idref='PN-00167'>flow media</pat:PartName> <pat:PartNumber pat:id='PN-00167'>62</pat:PartNumber>, down into the <pat:PartName pat:idref='PN-00168'>repair patch</pat:PartName> <pat:PartNumber pat:id='PN-00168'>24</pat:PartNumber>, such that the op<pat:PartName pat:idref='PN-00169'>en tip  </pat:PartName> <pat:PartNumber pat:id='PN-00169'>25</pat:PartNumber>  of   the  holl<pat:PartName pat:idref='PN-00170'>ow   needle  </pat:PartName> <pat:PartNumber pat:id='PN-00170'>50</pat:PartNumber>  is   positioned substantially along the <pat:PartName pat:idref='PN-00171'>inner side</pat:PartName> <pat:PartNumber pat:id='PN-00171'>33</pat:PartNumber> of the thickest part of the <pat:PartName pat:idref='PN-00172'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00172'>24</pat:PartNumber>, at the <pat:PartName pat:idref='PN-00173'>bottom</pat:PartName> <pat:PartNumber pat:id='PN-00173'>30</pat:PartNumber> of the <pat:PartName pat:idref='PN-00174'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00174'>26</pat:PartNumber>. A <pat:PartName pat:idref='PN-00175'>suitable sealant</pat:PartName> <pat:PartNumber pat:id='PN-00175'>52</pat:PartNumber>, which may be similar to <pat:PartName pat:idref='PN-00176'>vacuum bag sealant</pat:PartName> <pat:PartNumber pat:id='PN-00176'>70</pat:PartNumber>, forms a substantially vacuum tight seal between the <pat:PartName pat:idref='PN-00177'>hollow needle</pat:PartName> <pat:PartNumber pat:id='PN-00177'>50</pat:PartNumber> and the <pat:PartName pat:idref='PN-00178'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00178'>36</pat:PartNumber> at the point where the <pat:PartName pat:idref='PN-00179'>hollow needle</pat:PartName> <pat:PartNumber pat:id='PN-00179'>50</pat:PartNumber> <pat:PartName pat:idref='PN-00180'>penetrates</pat:PartName> <pat:PartNumber pat:id='PN-00180'>47</pat:PartNumber> <pat:PartName pat:idref='PN-00181'>(Figure</pat:PartName> <pat:PartNumber pat:id='PN-00181'>4</pat:PartNumber>) the <pat:PartName pat:idref='PN-00182'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00182'>36</pat:PartNumber>. </pat:P><pat:P pat:pNumber="41" pat:id="p-41">[0035] In use, after the <pat:PartName pat:idref='PN-00183'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00183'>24</pat:PartNumber> has been placed in the <pat:PartName pat:idref='PN-00184'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00184'>26</pat:PartNumber>, and the <pat:PartName pat:idref='PN-00185'>resin distribution tube</pat:PartName> <pat:PartNumber pat:id='PN-00185'>60</pat:PartNumber> and <pat:PartName pat:idref='PN-00186'>flow media</pat:PartName> <pat:PartNumber pat:id='PN-00186'>62</pat:PartNumber> have been installed, resin infusion may be commenced and the <pat:PartName pat:idref='PN-00187'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00187'>36</pat:PartNumber> is evacuated to apply compaction pressure to the <pat:PartName pat:idref='PN-00188'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00188'>24</pat:PartNumber>. Resin supplied under pressure from the <pat:PartName pat:idref='PN-00189'>resin reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00189'>46</pat:PartNumber> flows through the <pat:PartName pat:idref='PN-00190'>resin supply tube</pat:PartName> <pat:PartNumber pat:id='PN-00190'>48</pat:PartNumber> and then into the <pat:PartName pat:idref='PN-00191'>resin distribution tube</pat:PartName> <pat:PartNumber pat:id='PN-00191'>60</pat:PartNumber> where it flows onto and through the <pat:PartName pat:idref='PN-00192'>flow media</pat:PartName> <pat:PartNumber pat:id='PN-00192'>62</pat:PartNumber>. The flowing resin covers the <pat:PartName pat:idref='PN-00193'>flow media</pat:PartName> <pat:PartNumber pat:id='PN-00193'>62</pat:PartNumber> which assists in evenly distributing the flowing resin over the upper surface of the <pat:PartName pat:idref='PN-00194'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00194'>24</pat:PartNumber>. The <pat:PartName pat:idref='PN-00195'>vacuum reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00195'>44</pat:PartNumber> generates a <pat:PartName pat:idref='PN-00196'>vacuum in vacuum line</pat:PartName> <pat:PartNumber pat:id='PN-00196'>40</pat:PartNumber> that results in the <pat:PartName pat:idref='PN-00197'>open tip</pat:PartName> <pat:PartNumber pat:id='PN-00197'>25</pat:PartNumber> of the <pat:PartName pat:idref='PN-00198'>hollow needle</pat:PartName> <pat:PartNumber pat:id='PN-00198'>50</pat:PartNumber> reducing the pressure at the thickest part of <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>15</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='16'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData>the <pat:PartName pat:idref='PN-00199'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00199'>24</pat:PartNumber>, near the <pat:PartName pat:idref='PN-00200'>bottom</pat:PartName> <pat:PartNumber pat:id='PN-00200'>30</pat:PartNumber> of the <pat:PartName pat:idref='PN-00201'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00201'>26</pat:PartNumber>. The low pressure area at the <pat:PartName pat:idref='PN-00202'>open tip</pat:PartName> <pat:PartNumber pat:id='PN-00202'>25</pat:PartNumber> is less than the pressure on the incoming resin.        This reduced pressure at the <pat:PartName pat:idref='PN-00203'>open tip</pat:PartName> <pat:PartNumber pat:id='PN-00203'>25</pat:PartNumber> causes any air or other volatiles in the <pat:PartName pat:idref='PN-00204'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00204'>24</pat:PartNumber> to be forced away, while the resin is forced down through the <pat:PartName pat:idref='PN-00205'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00205'>24</pat:PartNumber> to its thickest part. The pressure gradient assures that the <pat:PartName pat:idref='PN-00206'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00206'>24</pat:PartNumber> is fully infused with resin and that air does not become entrapped within the re<pat:PartName pat:idref='PN-00207'>work patch  </pat:PartName> <pat:PartNumber pat:id='PN-00207'>24</pat:PartNumber> during the resin     infusion process. </pat:P><pat:P pat:pNumber="42" pat:id="p-42"><pat:PatentImage pat:id='ID-00007' pat:imageContentCategory='Graph' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>13761785.02-07-2013.HCWE2Q9MPXXIFW3.SPEC_29568061.12.392.1159.2087.1200.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.137</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>5.65</com:WidthMeasure><com:ALTText>Graph</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage>the <pat:PartName pat:idref='PN-00208'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00208'>24</pat:PartNumber>, are moved into the <pat:PartName pat:idref='PN-00209'>tip</pat:PartName> <pat:PartNumber pat:id='PN-00209'>25</pat:PartNumber> and through the <pat:PartName pat:idref='PN-00210'>hollow needle</pat:PartName> <pat:PartNumber pat:id='PN-00210'>50</pat:PartNumber> into the <pat:PartName pat:idref='PN-00211'>vacuum line</pat:PartName> <pat:PartNumber pat:id='PN-00211'>40</pat:PartNumber> which carries the excess resin/air/volatiles to the <pat:PartName pat:idref='PN-00212'>vacuum reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00212'>44</pat:PartNumber>. </pat:P><pat:P pat:pNumber="43" pat:id="p-43">[0036] The <pat:PartName pat:idref='PN-00213'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00213'>24</pat:PartNumber> may be cyclically compacted by using the <pat:PartName pat:idref='PN-00214'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00214'>36</pat:PartNumber>. Here, air is introduced into the dry fiber preform and then evacuated in a cyclical manner, thereby   further compacting the preform. The pressure in the <pat:PartName pat:idref='PN-00215'>resin reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00215'>46</pat:PartNumber> may be varied in relation to the pressure within the <pat:PartName pat:idref='PN-00216'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00216'>36</pat:PartNumber> in order to better control the net compaction pressure applied to the <pat:PartName pat:idref='PN-00217'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00217'>24</pat:PartNumber> as it is being infused with resin. The size of the <pat:PartName pat:idref='PN-00218'>open tip</pat:PartName> <pat:PartNumber pat:id='PN-00218'>25</pat:PartNumber> <pat:PartName pat:idref='PN-00219'>of needle</pat:PartName> <pat:PartNumber pat:id='PN-00219'>50</pat:PartNumber> may be chosen to allow free resin flow through the <pat:PartName pat:idref='PN-00220'>needle</pat:PartName> <pat:PartNumber pat:id='PN-00220'>50</pat:PartNumber> enough to overcome the natural frictional forces on the walls of the <pat:PartName pat:idref='PN-00221'>needle</pat:PartName> <pat:PartNumber pat:id='PN-00221'>50</pat:PartNumber> while minimizing the diameter of the penetration made in the <pat:PartName pat:idref='PN-00222'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00222'>36</pat:PartNumber>. When the <pat:PartName pat:idref='PN-00223'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00223'>24</pat:PartNumber> is nearly fully impregnated with resin, excess resin will begin to flow through the <pat:PartName pat:idref='PN-00224'>hollow needle</pat:PartName> <pat:PartNumber pat:id='PN-00224'>50</pat:PartNumber> <pat:PartName pat:idref='PN-00225'>into vacuum line</pat:PartName> <pat:PartNumber pat:id='PN-00225'>40</pat:PartNumber> and is collected in the v<pat:PartName pat:idref='PN-00226'>acuum  reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00226'>44</pat:PartNumber>. The amount     of vacuum pressure within the <pat:PartName pat:idref='PN-00227'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00227'>36</pat:PartNumber> may be adjusted so as to induce <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>16</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='17'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData>the  flow  of excess resin    into the nee<pat:PartName pat:idref='PN-00228'>dle   </pat:PartName> <pat:PartNumber pat:id='PN-00228'>50</pat:PartNumber>. The pressure within the <pat:PartName pat:idref='PN-00229'>vacuum reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00229'>44</pat:PartNumber> may also be adjusted so as to induce flow of excess resin through the <pat:PartName pat:idref='PN-00230'>hollow needle</pat:PartName> <pat:PartNumber pat:id='PN-00230'>50</pat:PartNumber> and into the <pat:PartName pat:idref='PN-00231'>vacuum reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00231'>44</pat:PartNumber>. Upon completion of resin infusion of the <pat:PartName pat:idref='PN-00232'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00232'>24</pat:PartNumber>, and prior to curing, the <pat:PartName pat:idref='PN-00233'>needle</pat:PartName> <pat:PartNumber pat:id='PN-00233'>50</pat:PartNumber> may be withdrawn from  the  re<pat:PartName pat:idref='PN-00234'>work  patch </pat:PartName> <pat:PartNumber pat:id='PN-00234'>24</pat:PartNumber>  and  a hole    (not  shown) remaining  in   the  vac<pat:PartName pat:idref='PN-00235'>uum  bag  </pat:PartName> <pat:PartNumber pat:id='PN-00235'>36</pat:PartNumber>  due  to   previous penetration by the <pat:PartName pat:idref='PN-00236'>needle</pat:PartName> <pat:PartNumber pat:id='PN-00236'>50</pat:PartNumber> may be sealed using a suitable sealant, such as vacuum bag sealant, in order to maintain vacuum    integrity of the bag <pat:PartName pat:idref='PN-00237'>   </pat:PartName> <pat:PartNumber pat:id='PN-00237'>36</pat:PartNumber> during curing. </pat:P><pat:P pat:pNumber="44" pat:id="p-44">[0037] Depending   upon  the  application,   it  may  be necessary or desirable to <pat:PartName pat:idref='PN-00238'>place more than one vacuum source</pat:PartName> <pat:PartNumber pat:id='PN-00238'>42</pat:PartNumber> <pat:PartName pat:idref='PN-00239'>(Figure</pat:PartName> <pat:PartNumber pat:id='PN-00239'>1</pat:PartNumber>) near thicker parts of a <pat:PartName pat:idref='PN-00240'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00240'>24</pat:PartNumber> having a large area. For example, referring to Figure 5, a <pat:PartName pat:idref='PN-00241'>relatively large area rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00241'>24</pat:PartNumber> <pat:PartName pat:idref='PN-00242'>is provided with multiple hollow needles</pat:PartName> <pat:PartNumber pat:id='PN-00242'>50</pat:PartNumber> at spaced apart locations. <pat:PartName pat:idref='PN-00243'>Seals</pat:PartName> <pat:PartNumber pat:id='PN-00243'>52</pat:PartNumber> seal each of the <pat:PartName pat:idref='PN-00244'>needles</pat:PartName> <pat:PartNumber pat:id='PN-00244'>50</pat:PartNumber> to a <pat:PartName pat:idref='PN-00245'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00245'>36</pat:PartNumber> which covers the entire area of the <pat:PartName pat:idref='PN-00246'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00246'>24</pat:PartNumber>. A <pat:PartName pat:idref='PN-00247'>series of resin exit lines</pat:PartName> <pat:PartNumber pat:id='PN-00247'>40</pat:PartNumber> couple the <pat:PartName pat:idref='PN-00248'>hollow needles</pat:PartName> <pat:PartNumber pat:id='PN-00248'>50</pat:PartNumber> with     a va<pat:PartName pat:idref='PN-00249'>cuum   reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00249'>24</pat:PartNumber> that reduces the internal pressure in the <pat:PartName pat:idref='PN-00250'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00250'>24</pat:PartNumber> at the locations of the <pat:PartName pat:idref='PN-00251'>needles</pat:PartName> <pat:PartNumber pat:id='PN-00251'>50</pat:PartNumber>. Resin is flowed into the  rew<pat:PartName pat:idref='PN-00252'>ork  patch  </pat:PartName> <pat:PartNumber pat:id='PN-00252'>24</pat:PartNumber>  through  a  spira<pat:PartName pat:idref='PN-00253'>l  wrap   resin distribution tube  </pat:PartName> <pat:PartNumber pat:id='PN-00253'>60</pat:PartNumber> that   is coupled with    a <pat:PartName pat:idref='PN-00254'>resin reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00254'>46</pat:PartNumber> by a <pat:PartName pat:idref='PN-00255'>resin supply tube</pat:PartName> <pat:PartNumber pat:id='PN-00255'>48</pat:PartNumber>. </pat:P><pat:P pat:pNumber="45" pat:id="p-45">[0038] Figure 6 shows the overall steps of a method of reworking a <pat:PartName pat:idref='PN-00256'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00256'>20</pat:PartNumber> using a <pat:PartName pat:idref='PN-00257'>vacuum source</pat:PartName> <pat:PartNumber pat:id='PN-00257'>42</pat:PartNumber> that is placed within the <pat:PartName pat:idref='PN-00258'>patch</pat:PartName> <pat:PartNumber pat:id='PN-00258'>24</pat:PartNumber> and used to resin through the <pat:PartName pat:idref='PN-00259'>patch</pat:PartName> <pat:PartNumber pat:id='PN-00259'>24</pat:PartNumber>. <pat:PartName pat:idref='PN-00260'>Beginning at step</pat:PartName> <pat:PartNumber pat:id='PN-00260'>67</pat:PartNumber>, a <pat:PartName pat:idref='PN-00261'>suitable patch</pat:PartName> <pat:PartNumber pat:id='PN-00261'>24</pat:PartNumber> is placed on the <pat:PartName pat:idref='PN-00262'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00262'>20</pat:PartNumber>, with the <pat:PartName pat:idref='PN-00263'>inner side</pat:PartName> <pat:PartNumber pat:id='PN-00263'>33</pat:PartNumber> of <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>17</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='18'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData>the <pat:PartName pat:idref='PN-00264'>patch</pat:PartName> <pat:PartNumber pat:id='PN-00264'>24</pat:PartNumber> in contact with the <pat:PartName pat:idref='PN-00265'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00265'>20</pat:PartNumber>. <pat:PartName pat:idref='PN-00266'>At</pat:PartName> <pat:PartNumber pat:id='PN-00266'>69</pat:PartNumber>, a <pat:PartName pat:idref='PN-00267'>vacuum source</pat:PartName> <pat:PartNumber pat:id='PN-00267'>42</pat:PartNumber> is inserted into the <pat:PartName pat:idref='PN-00268'>patch</pat:PartName> <pat:PartNumber pat:id='PN-00268'>24</pat:PartNumber> from the <pat:PartName pat:idref='PN-00269'>outer side</pat:PartName> <pat:PartNumber pat:id='PN-00269'>37</pat:PartNumber> of the <pat:PartName pat:idref='PN-00270'>patch</pat:PartName> <pat:PartNumber pat:id='PN-00270'>24</pat:PartNumber>. Then, <pat:PartName pat:idref='PN-00271'>at step</pat:PartName> <pat:PartNumber pat:id='PN-00271'>71</pat:PartNumber>, the <pat:PartName pat:idref='PN-00272'>vacuum source</pat:PartName> <pat:PartNumber pat:id='PN-00272'>42</pat:PartNumber> is used to resin through the <pat:PartName pat:idref='PN-00273'>patch</pat:PartName> <pat:PartNumber pat:id='PN-00273'>24</pat:PartNumber> to the <pat:PartName pat:idref='PN-00274'>inner side</pat:PartName> <pat:PartNumber pat:id='PN-00274'>33</pat:PartNumber> of the <pat:PartName pat:idref='PN-00275'>patch</pat:PartName> <pat:PartNumber pat:id='PN-00275'>24</pat:PartNumber>. If desired, an adhesive p<pat:OCRConfidenceData pat:levelNumber='5'>l</pat:OCRConfidenceData>y, <pat:PartName pat:idref='PN-00276'>nominally</pat:PartName> <pat:PartNumber pat:id='PN-00276'>0.005</pat:PartNumber>-0.010 inches in thickness, or other means of enhancing the <pat:PartName pat:idref='PN-00277'>bondline</pat:PartName> <pat:PartNumber pat:id='PN-00277'>39</pat:PartNumber> may be placed between the <pat:PartName pat:idref='PN-00278'>dry fiber patch</pat:PartName> <pat:PartNumber pat:id='PN-00278'>24</pat:PartNumber> and the <pat:PartName pat:idref='PN-00279'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00279'>26</pat:PartNumber>. </pat:P><pat:P pat:pNumber="46" pat:id="p-46"><pat:PatentImage pat:id='ID-00008' pat:imageContentCategory='Drawing' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>13761785.02-07-2013.HCWE2Q9MPXXIFW3.SPEC_29568063.11.402.1160.2086.1200.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.133</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>5.613</com:WidthMeasure><com:ALTText>Drawing</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage>illustrates the overall steps of another method of reworking an area of a <pat:PartName pat:idref='PN-00280'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00280'>20</pat:PartNumber> using a <pat:PartName pat:idref='PN-00281'>resin infused rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00281'>24</pat:PartNumber>. <pat:PartName pat:idref='PN-00282'>Beginning at</pat:PartName> <pat:PartNumber pat:id='PN-00282'>72</pat:PartNumber>, a <pat:PartName pat:idref='PN-00283'>dry fiber rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00283'>24</pat:PartNumber> is placed on the <pat:PartName pat:idref='PN-00284'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00284'>20</pat:PartNumber>, such that an <pat:PartName pat:idref='PN-00285'>inner side</pat:PartName> <pat:PartNumber pat:id='PN-00285'>33</pat:PartNumber> of the <pat:PartName pat:idref='PN-00286'>patch</pat:PartName> <pat:PartNumber pat:id='PN-00286'>24</pat:PartNumber> is in contact with the <pat:PartName pat:idref='PN-00287'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00287'>20</pat:PartNumber>. If desired, an adhesive ply, <pat:PartName pat:idref='PN-00288'>nominally</pat:PartName> <pat:PartNumber pat:id='PN-00288'>0.005</pat:PartNumber>-0.010 inches in thickness, or other means of enhancing the <pat:PartName pat:idref='PN-00289'>bondline</pat:PartName> <pat:PartNumber pat:id='PN-00289'>39</pat:PartNumber>, may be placed between the <pat:PartName pat:idref='PN-00290'>dry fiber patch</pat:PartName> <pat:PartNumber pat:id='PN-00290'>24</pat:PartNumber> and the <pat:PartName pat:idref='PN-00291'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00291'>26</pat:PartNumber>. <pat:PartName pat:idref='PN-00292'>At</pat:PartName> <pat:PartNumber pat:id='PN-00292'>74</pat:PartNumber>, a <pat:PartName pat:idref='PN-00293'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00293'>36</pat:PartNumber> is placed over the <pat:PartName pat:idref='PN-00294'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00294'>24</pat:PartNumber> and is sealed to the <pat:PartName pat:idref='PN-00295'>structure</pat:PartName> <pat:PartNumber pat:id='PN-00295'>20</pat:PartNumber>. The <pat:PartName pat:idref='PN-00296'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00296'>36</pat:PartNumber> may be evacuated to compact the <pat:PartName pat:idref='PN-00297'>dry fiber rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00297'>24</pat:PartNumber> as desired, prior to its infusion with resin. <pat:PartName pat:idref='PN-00298'>At</pat:PartName> <pat:PartNumber pat:id='PN-00298'>76</pat:PartNumber>, a <pat:PartName pat:idref='PN-00299'>vacuum source</pat:PartName> <pat:PartNumber pat:id='PN-00299'>42</pat:PartNumber> is positioned at the <pat:PartName pat:idref='PN-00300'>inner side</pat:PartName> <pat:PartNumber pat:id='PN-00300'>33</pat:PartNumber> of the <pat:PartName pat:idref='PN-00301'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00301'>24</pat:PartNumber>. <pat:PartName pat:idref='PN-00302'>At step</pat:PartName> <pat:PartNumber pat:id='PN-00302'>78</pat:PartNumber>, resin is flowed onto the <pat:PartName pat:idref='PN-00303'>outer side</pat:PartName> <pat:PartNumber pat:id='PN-00303'>37</pat:PartNumber> of the <pat:PartName pat:idref='PN-00304'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00304'>24</pat:PartNumber>, and <pat:PartName pat:idref='PN-00305'>at</pat:PartName> <pat:PartNumber pat:id='PN-00305'>80</pat:PartNumber>, the <pat:PartName pat:idref='PN-00306'>vacuum source</pat:PartName> <pat:PartNumber pat:id='PN-00306'>42</pat:PartNumber> is used to force resin down through the <pat:PartName pat:idref='PN-00307'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00307'>24</pat:PartNumber> to the <pat:PartName pat:idref='PN-00308'>inner side</pat:PartName> <pat:PartNumber pat:id='PN-00308'>33</pat:PartNumber> of the <pat:PartName pat:idref='PN-00309'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00309'>24</pat:PartNumber> while reducing pressure on the <pat:PartName pat:idref='PN-00310'>inner side</pat:PartName> <pat:PartNumber pat:id='PN-00310'>33</pat:PartNumber> of the <pat:PartName pat:idref='PN-00311'>patch</pat:PartName> <pat:PartNumber pat:id='PN-00311'>24</pat:PartNumber>. <pat:PartName pat:idref='PN-00312'>At step</pat:PartName> <pat:PartNumber pat:id='PN-00312'>82</pat:PartNumber>, the <pat:PartName pat:idref='PN-00313'>vacuum source</pat:PartName> <pat:PartNumber pat:id='PN-00313'>42</pat:PartNumber> is removed after infusion of the <pat:PartName pat:idref='PN-00314'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00314'>24</pat:PartNumber> with resin. The <pat:PartName pat:idref='PN-00315'>vacuum bag may</pat:PartName> <pat:PartNumber pat:id='PN-00315'>36</pat:PartNumber> may maintain a desired level of compaction pressure on the <pat:PartName pat:idref='PN-00316'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00316'>24</pat:PartNumber> as it is <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>18</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='19'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData>being <pat:PartName pat:idref='PN-00317'>infused with resin during steps</pat:PartName> <pat:PartNumber pat:id='PN-00317'>78</pat:PartNumber> and 80. <pat:PartName pat:idref='PN-00318'>At step</pat:PartName> <pat:PartNumber pat:id='PN-00318'>84</pat:PartNumber>, the <pat:PartName pat:idref='PN-00319'>resin infused rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00319'>24</pat:PartNumber> may be further compacted by reducing the pressure within the <pat:PartName pat:idref='PN-00320'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00320'>36</pat:PartNumber>. <pat:PartName pat:idref='PN-00321'>At step</pat:PartName> <pat:PartNumber pat:id='PN-00321'>86</pat:PartNumber>, the <pat:PartName pat:idref='PN-00322'>resin infused patch</pat:PartName> <pat:PartNumber pat:id='PN-00322'>24</pat:PartNumber> is cured. </pat:P><pat:P pat:pNumber="47" pat:id="p-47">[0040] Figure 8 illustrates the steps of a method of reworking a <pat:PartName pat:idref='PN-00323'>composite skin</pat:PartName> <pat:PartNumber pat:id='PN-00323'>20</pat:PartNumber> according to the disclosed embodiments. <pat:PartName pat:idref='PN-00324'>At</pat:PartName> <pat:PartNumber pat:id='PN-00324'>88</pat:PartNumber>, a <pat:PartName pat:idref='PN-00325'>dry fiber preform rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00325'>24</pat:PartNumber> is prepared, as by tacking together layers of woven or knitted dry fabric. <pat:PartName pat:idref='PN-00326'>At</pat:PartName> <pat:PartNumber pat:id='PN-00326'>90</pat:PartNumber>, the <pat:PartName pat:idref='PN-00327'>skin</pat:PartName> <pat:PartNumber pat:id='PN-00327'>20</pat:PartNumber> is prepared and cleaned in the <pat:PartName pat:idref='PN-00328'>area</pat:PartName> <pat:PartNumber pat:id='PN-00328'>22</pat:PartNumber> to be reworked, and may be scarfed, as required, to remove inconsistencies and form a <pat:PartName pat:idref='PN-00329'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00329'>26</pat:PartNumber> into which the <pat:PartName pat:idref='PN-00330'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00330'>24</pat:PartNumber> may be placed. <pat:PartName pat:idref='PN-00331'>At step</pat:PartName> <pat:PartNumber pat:id='PN-00331'>92</pat:PartNumber>, the <pat:PartName pat:idref='PN-00332'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00332'>24</pat:PartNumber> is installed in the <pat:PartName pat:idref='PN-00333'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00333'>26</pat:PartNumber>. <pat:OCRConfidenceData pat:levelNumber='6'>.</pat:OCRConfidenceData> If desired, an adhesive ply, <pat:PartName pat:idref='PN-00334'>nominally</pat:PartName> <pat:PartNumber pat:id='PN-00334'>0.005</pat:PartNumber>-0.010 inches in thickness, or other means of enhancing the <pat:PartName pat:idref='PN-00335'>bondline</pat:PartName> <pat:PartNumber pat:id='PN-00335'>39</pat:PartNumber> may be placed between the  dry<pat:PartName pat:idref='PN-00336'>  fiber patch  </pat:PartName> <pat:PartNumber pat:id='PN-00336'>24</pat:PartNumber>  and the   sc<pat:PartName pat:idref='PN-00337'>arf  cavity </pat:PartName> <pat:PartNumber pat:id='PN-00337'>26</pat:PartNumber>. Optionally, a finish ply (not shown) may be applied over the <pat:PartName pat:idref='PN-00338'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00338'>24</pat:PartNumber> <pat:PartName pat:idref='PN-00339'>at step</pat:PartName> <pat:PartNumber pat:id='PN-00339'>94</pat:PartNumber>. <pat:PartName pat:idref='PN-00340'>At step</pat:PartName> <pat:PartNumber pat:id='PN-00340'>96</pat:PartNumber>, separation media such as a <pat:PartName pat:idref='PN-00341'>release ply</pat:PartName> <pat:PartNumber pat:id='PN-00341'>66</pat:PartNumber> is installed, <pat:PartName pat:idref='PN-00342'>following which flow media</pat:PartName> <pat:PartNumber pat:id='PN-00342'>62</pat:PartNumber> <pat:PartName pat:idref='PN-00343'>is installed at step</pat:PartName> <pat:PartNumber pat:id='PN-00343'>98</pat:PartNumber>. <pat:PartName pat:idref='PN-00344'>At step</pat:PartName> <pat:PartNumber pat:id='PN-00344'>100</pat:PartNumber>, a resin supply tube which may comprise a spira<pat:PartName pat:idref='PN-00345'>l wrap  resin  distribution  tube  </pat:PartName> <pat:PartNumber pat:id='PN-00345'>60</pat:PartNumber>  is  installed  and connected with a <pat:PartName pat:idref='PN-00346'>resin reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00346'>46</pat:PartNumber>. <pat:PartName pat:idref='PN-00347'>At</pat:PartName> <pat:PartNumber pat:id='PN-00347'>102</pat:PartNumber>, a <pat:PartName pat:idref='PN-00348'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00348'>36</pat:PartNumber> is installed in sealed over the <pat:PartName pat:idref='PN-00349'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00349'>24</pat:PartNumber>. <pat:PartName pat:idref='PN-00350'>At step</pat:PartName> <pat:PartNumber pat:id='PN-00350'>104</pat:PartNumber>, a <pat:PartName pat:idref='PN-00351'>hollow needle</pat:PartName> <pat:PartNumber pat:id='PN-00351'>50</pat:PartNumber> is inserted through the <pat:PartName pat:idref='PN-00352'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00352'>36</pat:PartNumber> and through the thickest part of the <pat:PartName pat:idref='PN-00353'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00353'>24</pat:PartNumber>, and the <pat:PartName pat:idref='PN-00354'>needle</pat:PartName> <pat:PartNumber pat:id='PN-00354'>50</pat:PartNumber> is sealed to the <pat:PartName pat:idref='PN-00355'>vacuum bag</pat:PartName> <pat:PartNumber pat:id='PN-00355'>36</pat:PartNumber>. During insertion of the <pat:PartName pat:idref='PN-00356'>hollow needle</pat:PartName> <pat:PartNumber pat:id='PN-00356'>50</pat:PartNumber>, an <pat:PartName pat:idref='PN-00357'>open tip</pat:PartName> <pat:PartNumber pat:id='PN-00357'>25</pat:PartNumber> of the <pat:PartName pat:idref='PN-00358'>needle</pat:PartName> <pat:PartNumber pat:id='PN-00358'>50</pat:PartNumber> is positioned at the bottom of the scarf cavity, at a location where the <pat:PartName pat:idref='PN-00359'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00359'>24</pat:PartNumber> has a maximum thickness at the <pat:PartName pat:idref='PN-00360'>inner side</pat:PartName> <pat:PartNumber pat:id='PN-00360'>33</pat:PartNumber> of the <pat:PartName pat:idref='PN-00361'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00361'>24</pat:PartNumber>. </pat:P><pat:P pat:pNumber="48" pat:id="p-48"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>19</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='20'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData>[0041] <pat:PartName pat:idref='PN-00362'>At</pat:PartName> <pat:PartNumber pat:id='PN-00362'>106</pat:PartNumber>, a <pat:PartName pat:idref='PN-00363'>resin exit line</pat:PartName> <pat:PartNumber pat:id='PN-00363'>40</pat:PartNumber> is connected between the <pat:PartName pat:idref='PN-00364'>hollow needle</pat:PartName> <pat:PartNumber pat:id='PN-00364'>50</pat:PartNumber> and a <pat:PartName pat:idref='PN-00365'>vacuum reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00365'>44</pat:PartNumber>. The va<pat:PartName pat:idref='PN-00366'>cuum  bag </pat:PartName> <pat:PartNumber pat:id='PN-00366'>36</pat:PartNumber> is ev<pat:PartName pat:idref='PN-00367'>acuated    at  step </pat:PartName> <pat:PartNumber pat:id='PN-00367'>108</pat:PartNumber> to begin compacting the <pat:PartName pat:idref='PN-00368'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00368'>24</pat:PartNumber>. <pat:PartName pat:idref='PN-00369'>At</pat:PartName> <pat:PartNumber pat:id='PN-00369'>110</pat:PartNumber>, resin flow is commenced by flowing resin from the <pat:PartName pat:idref='PN-00370'>resin reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00370'>46</pat:PartNumber> through the <pat:PartName pat:idref='PN-00371'>resin distribution tube</pat:PartName> <pat:PartNumber pat:id='PN-00371'>60</pat:PartNumber> onto the <pat:PartName pat:idref='PN-00372'>flow media</pat:PartName> <pat:PartNumber pat:id='PN-00372'>62</pat:PartNumber>. <pat:PartName pat:idref='PN-00373'>At</pat:PartName> <pat:PartNumber pat:id='PN-00373'>112</pat:PartNumber>, the flow of resin through the <pat:PartName pat:idref='PN-00374'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00374'>24</pat:PartNumber> is controlled by controlling the relative pressures of the <pat:PartName pat:idref='PN-00375'>resin reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00375'>46</pat:PartNumber> supplying resin to the <pat:PartName pat:idref='PN-00376'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00376'>24</pat:PartNumber>, and the <pat:PartName pat:idref='PN-00377'>vacuum reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00377'>44</pat:PartNumber> used to locally reduce pressure at the thickest part of the <pat:PartName pat:idref='PN-00378'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00378'>24</pat:PartNumber> and move away excess resin. <pat:PartName pat:idref='PN-00379'>At</pat:PartName> <pat:PartNumber pat:id='PN-00379'>114</pat:PartNumber>, the <pat:PartName pat:idref='PN-00380'>hollow needle</pat:PartName> <pat:PartNumber pat:id='PN-00380'>50</pat:PartNumber> is used to apply a vacuum at the <pat:PartName pat:idref='PN-00381'>bottom</pat:PartName> <pat:PartNumber pat:id='PN-00381'>30</pat:PartNumber> of the <pat:PartName pat:idref='PN-00382'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00382'>26</pat:PartNumber> which both reduces pressure at the thickest part of the <pat:PartName pat:idref='PN-00383'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00383'>24</pat:PartNumber> and forces excess resin away from the <pat:PartName pat:idref='PN-00384'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00384'>24</pat:PartNumber> into the <pat:PartName pat:idref='PN-00385'>vacuum reservoir</pat:PartName> <pat:PartNumber pat:id='PN-00385'>44</pat:PartNumber>. The vacuum applied by the <pat:PartName pat:idref='PN-00386'>hollow needle</pat:PartName> <pat:PartNumber pat:id='PN-00386'>50</pat:PartNumber> is lower than the pressure on the incoming resin, thus creating a pressure differential that drives the resin to flow to the bottom of the <pat:PartName pat:idref='PN-00387'>scarf cavity</pat:PartName> <pat:PartNumber pat:id='PN-00387'>26</pat:PartNumber>. A<pat:PartName pat:idref='PN-00388'>t </pat:PartName> <pat:PartNumber pat:id='PN-00388'>116</pat:PartNumber>,  the   resin  infusion  process  is  completed, following which, <pat:PartName pat:idref='PN-00389'>at</pat:PartName> <pat:PartNumber pat:id='PN-00389'>118</pat:PartNumber>, the <pat:PartName pat:idref='PN-00390'>needle</pat:PartName> <pat:PartNumber pat:id='PN-00390'>50</pat:PartNumber> is withdrawn from the <pat:PartName pat:idref='PN-00391'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00391'>24</pat:PartNumber> and a hole remaining in the vacuum bag due to previous penetration by the <pat:PartName pat:idref='PN-00392'>needle</pat:PartName> <pat:PartNumber pat:id='PN-00392'>50</pat:PartNumber> is sealed. The <pat:PartName pat:idref='PN-00393'>rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00393'>24</pat:PartNumber> <pat:PartName pat:idref='PN-00394'>is cured at step</pat:PartName> <pat:PartNumber pat:id='PN-00394'>120</pat:PartNumber>, and <pat:PartName pat:idref='PN-00395'>at</pat:PartName> <pat:PartNumber pat:id='PN-00395'>122</pat:PartNumber> the <pat:PartName pat:idref='PN-00396'>cured rework patch</pat:PartName> <pat:PartNumber pat:id='PN-00396'>24</pat:PartNumber> may be trimmed, cleaned, sanded and smoothed, as necessary. </pat:P><pat:P pat:pNumber="49" pat:id="p-49">[0042] Embodiments of the disclosure may find use in a variety of potential applications, particularly in the transportation   industry,   including    for   example, aerospace, marine, automotive applications and other application where automated layup equipment may be used. </pat:P><pat:P pat:pNumber="50" pat:id="p-50"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>20</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='21'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData>Thus, referring now to Figures 9 and 10, embodiments of the disclosure may be used in the context of an aircraft manufacturing and <pat:PartName pat:idref='PN-00397'>service method</pat:PartName> <pat:PartNumber pat:id='PN-00397'>124</pat:PartNumber> as shown in Figure 9 and an <pat:PartName pat:idref='PN-00398'>aircraft</pat:PartName> <pat:PartNumber pat:id='PN-00398'>126</pat:PartNumber> as shown in Figure 10.    Aircraft applications of the disclosed embodiments may include, for example, without limitation, composite skins and other load carrying structures.   During pre-production, ex<pat:PartName pat:idref='PN-00399'>emplary method  </pat:PartName> <pat:PartNumber pat:id='PN-00399'>124</pat:PartNumber> may   include  specification  and <pat:PartName pat:idref='PN-00400'>design</pat:PartName> <pat:PartNumber pat:id='PN-00400'>128</pat:PartNumber> of the <pat:PartName pat:idref='PN-00401'>aircraft</pat:PartName> <pat:PartNumber pat:id='PN-00401'>126</pat:PartNumber> and <pat:PartName pat:idref='PN-00402'>material procurement</pat:PartName> <pat:PartNumber pat:id='PN-00402'>130</pat:PartNumber>.    During production, component    and  <pat:PartName pat:idref='PN-00403'>subassembly manufacturing</pat:PartName> <pat:PartNumber pat:id='PN-00403'>132</pat:PartNumber> and <pat:PartName pat:idref='PN-00404'>system integration</pat:PartName> <pat:PartNumber pat:id='PN-00404'>134</pat:PartNumber> of the <pat:PartName pat:idref='PN-00405'>aircraft</pat:PartName> <pat:PartNumber pat:id='PN-00405'>126</pat:PartNumber> takes place. Thereafter, the <pat:PartName pat:idref='PN-00406'>aircraft</pat:PartName> <pat:PartNumber pat:id='PN-00406'>126</pat:PartNumber> may go through certification and <pat:PartName pat:idref='PN-00407'>delivery</pat:PartName> <pat:PartNumber pat:id='PN-00407'>136</pat:PartNumber> in order to <pat:PartName pat:idref='PN-00408'>be placed in service</pat:PartName> <pat:PartNumber pat:id='PN-00408'>138</pat:PartNumber>.     While in service by a customer, the <pat:PartName pat:idref='PN-00409'>aircraft</pat:PartName> <pat:PartNumber pat:id='PN-00409'>126</pat:PartNumber> is scheduled for routine maintenance and <pat:PartName pat:idref='PN-00410'>service</pat:PartName> <pat:PartNumber pat:id='PN-00410'>140</pat:PartNumber>, which may also include modification, reconfiguration, refurbishment, and so on. The disclosed method may be employed to rework, repair or reinforce structural areas of the <pat:PartName pat:idref='PN-00411'>aircraft</pat:PartName> <pat:PartNumber pat:id='PN-00411'>126</pat:PartNumber> while in service. </pat:P><pat:P pat:pNumber="51" pat:id="p-51">[0043] Each of the <pat:PartName pat:idref='PN-00412'>processes of method</pat:PartName> <pat:PartNumber pat:id='PN-00412'>124</pat:PartNumber> may be performed or carried out by a system integrator, a third <pat:PatentImage pat:id='ID-00009' pat:imageContentCategory='Chemistry' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>13761785.02-07-2013.HCWE2Q9MPXXIFW3.SPEC_29568066.25.391.2263.2086.2304.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.137</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>5.65</com:WidthMeasure><com:ALTText>Chemistry</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage>purposes of this description, a system integrator may include  without  limitation  any  number   of  aircraft manufacturers and major-system subcontractors; a third party may include without limitation any number of vendors, subcontractors, and suppliers; and an operator may be an airline, leasing company, military entity, service organization, and so on. </pat:P><pat:P pat:pNumber="52" pat:id="p-52">[0044] As shown in Figure 10, the <pat:PartName pat:idref='PN-00413'>aircraft</pat:PartName> <pat:PartNumber pat:id='PN-00413'>126</pat:PartNumber> <pat:PartName pat:idref='PN-00414'>produced by exemplary method</pat:PartName> <pat:PartNumber pat:id='PN-00414'>124</pat:PartNumber> may include an <pat:PartName pat:idref='PN-00415'>airframe</pat:PartName> <pat:PartNumber pat:id='PN-00415'>142</pat:PartNumber> with <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>21</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='22'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData>a  plu<pat:PartName pat:idref='PN-00416'>rality  of  systems </pat:PartName> <pat:PartNumber pat:id='PN-00416'>144</pat:PartNumber>  and   an  i<pat:PartName pat:idref='PN-00417'>nterior </pat:PartName> <pat:PartNumber pat:id='PN-00417'>146</pat:PartNumber>. <pat:PartName pat:idref='PN-00418'>Examples of high-level systems</pat:PartName> <pat:PartNumber pat:id='PN-00418'>144</pat:PartNumber> include one or more of a <pat:PartName pat:idref='PN-00419'>propulsion system</pat:PartName> <pat:PartNumber pat:id='PN-00419'>148</pat:PartNumber>, an <pat:PartName pat:idref='PN-00420'>electrical system</pat:PartName> <pat:PartNumber pat:id='PN-00420'>150</pat:PartNumber>, a <pat:PartName pat:idref='PN-00421'>hydraulic system</pat:PartName> <pat:PartNumber pat:id='PN-00421'>12</pat:PartNumber> to, and an <pat:PartName pat:idref='PN-00422'>environmental system</pat:PartName> <pat:PartNumber pat:id='PN-00422'>154</pat:PartNumber>. Any number of other systems may be included.    Although an aerospace example is shown, the principles of the disclosure may be applied to other industries, such as the marine and automotive industries. </pat:P><pat:P pat:pNumber="53" pat:id="p-53">[0045] Systems  and  methods  embodied  herein  may  be employed during any one or more of the stages of the production  and  ser<pat:PartName pat:idref='PN-00423'>vice  method  </pat:PartName> <pat:PartNumber pat:id='PN-00423'>124</pat:PartNumber>.    For  example, components or subassemblies corresponding to <pat:PartName pat:idref='PN-00424'>production process</pat:PartName> <pat:PartNumber pat:id='PN-00424'>128</pat:PartNumber> may be reworked while the <pat:PartName pat:idref='PN-00425'>aircraft</pat:PartName> <pat:PartNumber pat:id='PN-00425'>126</pat:PartNumber> is in service.    Also, one or more apparatus embodiments, method embodiments, or a combination thereof may be utilized during the <pat:PartName pat:idref='PN-00426'>production stages</pat:PartName> <pat:PartNumber pat:id='PN-00426'>132</pat:PartNumber> and 134, for example, by substantially expediting assembly of or reducing  the maintenance   cost  of  an  a<pat:PartName pat:idref='PN-00427'>ircraft </pat:PartName> <pat:PartNumber pat:id='PN-00427'>126</pat:PartNumber>. Similarly, one or more of apparatus embodiments, method embodiments, or a combination thereof may be utilized while the <pat:PartName pat:idref='PN-00428'>aircraft</pat:PartName> <pat:PartNumber pat:id='PN-00428'>126</pat:PartNumber> is in service, for example and without limitation, to maintenance and <pat:PartName pat:idref='PN-00429'>service</pat:PartName> <pat:PartNumber pat:id='PN-00429'>140</pat:PartNumber>. </pat:P><pat:P pat:pNumber="54" pat:id="p-54">[0046] The description of the different illustrative embodiments   has  been   presented   for  purposes   of illustration and description, and is not intended to be exhaustive or limited to the embodiments in the form disclosed.   Many modifications and variations will be apparent  to  those  of  ordinary  skill   in  the  art. Further, different illustrative embodiments may provide different advantages as compared to other illustrative embodiments. The embodiment or embodiments selected are chosen and described in order to best explain the <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>22</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='23'?><pat:BoundaryData><pat:HeaderText>Docket No. 12-1028-US-NP</pat:HeaderText></pat:BoundaryData>principles    of   the   embodiments,    the   practical application, and to enable others of ordinary skill in the  art  to   understand  the  disclosure  for  various embodiments with various modifications as are suited to the particular use contemplated. </pat:P><pat:P pat:pNumber="55" pat:id="p-55"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>23</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData></pat:P></pat:Specification></pat:SpecificationDocument>

applicant/13809279.xml

@@ -0,0 +1 @@
+<?xml version="1.0" encoding="utf-8"?><pat:SpecificationDocument xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:pat="urn:us:gov:doc:uspto:patent" xmlns:ent="urn:us:gov:doc:uspto:enterprise" xmlns="urn:us:gov:doc:uspto:patent" xmlns:tbl="http://www.oasis-open.org/tables/exchange/1.0" xmlns:com="http://www.wipo.int/standards/XMLSchema/Common/1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XML_SCHEMAS/V1_3/SpecificationDocument_1_0.xsd" pat:instanceFileName="13809279.01-09-2013.HBQWPU6FPXXIFW3.SPEC.XML" pat:id="HBQWPU6FPXXIFW3"><pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001"><pat:ApplicationHeaderDetails><pat:ApplicationNumber>13809279</pat:ApplicationNumber></pat:ApplicationHeaderDetails><pat:PageTotalQuantity>1</pat:PageTotalQuantity><pat:ParagraphTotalQuantity>10</pat:ParagraphTotalQuantity></pat:DocumentHeaderDetails><pat:MailRoomDate>2013-01-09</pat:MailRoomDate><pat:DocumentCreateDateText>2014-10-02</pat:DocumentCreateDateText><pat:DocumentTitle>SPECIFICATION DOCUMENT</pat:DocumentTitle><pat:Specification><?PageStart number='1'?><pat:P pat:pNumber="1" pat:id="p-1"><pat:PatentImage pat:id='ID-00002' pat:imageContentCategory='Drawing' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>13809279.01-09-2013.HBQWPU6FPXXIFW3.SPEC_30571132.1.277.160.2225.245.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.283</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>6.493</com:WidthMeasure><com:ALTText>Drawing</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:Heading pat:id="h-1">AMENDMENTS TO THE SPECIFICATION</pat:Heading><pat:P pat:pNumber="2" pat:id="p-2">Please replace the Title as follows: </pat:P><pat:Heading pat:id="h-2">ELECTRICAL STEEL SHEET AND METHOD FOR MANUFACTURING THE SAME</pat:Heading><pat:P pat:pNumber="3" pat:id="p-3">Page 29 Please amend paragraph [0064] as follows: </pat:P><pat:P pat:pNumber="4" pat:id="p-4">[0064] Details of the <pat:PartName pat:idref='PN-00001'>six kinds of fluorine resins in Table</pat:PartName> <pat:PartNumber pat:id='PN-00001'>2</pat:PartNumber> are as follows. <pat:PartName pat:idref='PN-00002'>[Fluorine resin</pat:PartName> <pat:PartNumber pat:id='PN-00002'>1</pat:PartNumber>] This is the dispersion of a fluorine resin in a polytetrafluoroethylene (PTFE) type, having the <pat:PartName pat:idref='PN-00003'>average particle size of</pat:PartName> <pat:PartNumber pat:id='PN-00003'>0.25</pat:PartNumber> <pat:OCRConfidenceData pat:levelNumber='2'>p</pat:OCRConfidenceData>m, and a <pat:PartName pat:idref='PN-00004'>concentration of</pat:PartName> <pat:PartNumber pat:id='PN-00004'>48</pat:PartNumber> mass%. </pat:P><pat:P pat:pNumber="5" pat:id="p-5">[Fluorine <pat:PartName pat:idref='PN-00005'>resin</pat:PartName> <pat:PartNumber pat:id='PN-00005'>2</pat:PartNumber>] This is the dispersion of a fluorine resin in a fluorinated ethylene propylene (FEP) type, having the <pat:PartName pat:idref='PN-00006'>average particle size of</pat:PartName> <pat:PartNumber pat:id='PN-00006'>0.34</pat:PartNumber> <pat:OCRConfidenceData pat:levelNumber='2'>p</pat:OCRConfidenceData>m, and the <pat:PartName pat:idref='PN-00007'>concentration of</pat:PartName> <pat:PartNumber pat:id='PN-00007'>50</pat:PartNumber> mass%. </pat:P><pat:P pat:pNumber="6" pat:id="p-6">[Fluorine <pat:PartName pat:idref='PN-00008'>resin</pat:PartName> <pat:PartNumber pat:id='PN-00008'>3</pat:PartNumber>] This is the dispersion of a fluorine resin made to be a water dispersion type by a forced emulsification, having the <pat:PartName pat:idref='PN-00009'>average particle size of</pat:PartName> <pat:PartNumber pat:id='PN-00009'>0.12</pat:PartNumber> <pat:OCRConfidenceData pat:levelNumber='2'>p</pat:OCRConfidenceData>m, and the <pat:PartName pat:idref='PN-00010'>concentration of</pat:PartName> <pat:PartNumber pat:id='PN-00010'>60</pat:PartNumber> mass%. </pat:P><pat:P pat:pNumber="7" pat:id="p-7">[Fluorine <pat:PartName pat:idref='PN-00011'>resin</pat:PartName> <pat:PartNumber pat:id='PN-00011'>4</pat:PartNumber>] This is the powder of the fluorine resin in a fluorine rubber type, having the <pat:PartName pat:idref='PN-00012'>average particle size of</pat:PartName> <pat:PartNumber pat:id='PN-00012'>2.5</pat:PartNumber> <pat:OCRConfidenceData pat:levelNumber='288'>pm.</pat:OCRConfidenceData> </pat:P><pat:P pat:pNumber="8" pat:id="p-8">[Fluorine <pat:PartName pat:idref='PN-00013'>resin</pat:PartName> <pat:PartNumber pat:id='PN-00013'>5</pat:PartNumber>] This is the dispersion [[5]] of the fluorine resin in a hydroxyl group grafted type, having the <pat:PartName pat:idref='PN-00014'>average particle size of</pat:PartName> <pat:PartNumber pat:id='PN-00014'>0.06</pat:PartNumber> <pat:OCRConfidenceData pat:levelNumber='2'>p</pat:OCRConfidenceData>m, and the <pat:PartName pat:idref='PN-00015'>concentration of</pat:PartName> <pat:PartNumber pat:id='PN-00015'>48</pat:PartNumber> mass%. </pat:P><pat:P pat:pNumber="9" pat:id="p-9">[Fluorine <pat:PartName pat:idref='PN-00016'>resin</pat:PartName> <pat:PartNumber pat:id='PN-00016'>6</pat:PartNumber>] This is the powder of the fluorine resin compounding PTFE, having the <pat:PartName pat:idref='PN-00017'>average particle size of</pat:PartName> <pat:PartNumber pat:id='PN-00017'>0.33</pat:PartNumber> <pat:OCRConfidenceData pat:levelNumber='2'>p</pat:OCRConfidenceData>m and vinylidene fluoride having the <pat:PartName pat:idref='PN-00018'>average particle size of</pat:PartName> <pat:PartNumber pat:id='PN-00018'>0.25</pat:PartNumber> <pat:OCRConfidenceData pat:levelNumber='588'>pm.</pat:OCRConfidenceData> </pat:P><pat:P pat:pNumber="10" pat:id="p-10">BIRCH, STEWART, KOLASCH &amp;amp; BIRCH, LLP                                   MSW/MSW/erb </pat:P></pat:Specification></pat:SpecificationDocument>

applicant/13900202.xml

@@ -0,0 +1,15 @@
+<?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="13900202.08-26-2013.HKU541HZPXXIFW3.SPEC.xml" pat:id="HKU541HZPXXIFW3" 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>13900202</pat:ApplicationNumber></pat:ApplicationHeaderDetails>
+<pat:PageTotalQuantity>1</pat:PageTotalQuantity>
+<pat:ParagraphTotalQuantity>2</pat:ParagraphTotalQuantity>
+</pat:DocumentHeaderDetails>
+<pat:MailRoomDate>2013-08-26</pat:MailRoomDate>
+<pat:Specification pat:id="Specification">
+<?PageStart number="1"?>
+<pat:BoundaryData><pat:HeaderText>Serial No. 13/900,202</pat:HeaderText></pat:BoundaryData>
+<pat:P pat:id="p-1" pat:pNumber="1">Preliminary Amendment Dated: August 26, 2013 Attorney Docket No. 080437.65597US Specification Submitted herewith is a substitute specification and marked-up version thereof.</pat:P>
+<pat:P pat:id="p-2" pat:pNumber="2">I certify that said substitute specification contains no new matter and includes the changes indicated in the marked-up copy of the original specification.</pat:P>
+<pat:BoundaryData><pat:HeaderText>Page 2 of 12</pat:HeaderText></pat:BoundaryData>
+</pat:Specification></pat:SpecificationDocument>

applicant/14101777.xml

@@ -0,0 +1 @@
+<?xml version="1.0" encoding="utf-8"?><pat:SpecificationDocument xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:pat="urn:us:gov:doc:uspto:patent" xmlns:ent="urn:us:gov:doc:uspto:enterprise" xmlns="urn:us:gov:doc:uspto:patent" xmlns:tbl="http://www.oasis-open.org/tables/exchange/1.0" xmlns:com="http://www.wipo.int/standards/XMLSchema/Common/1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XML_SCHEMAS/V1_3/SpecificationDocument_1_0.xsd" pat:instanceFileName="14101777.12-10-2013.HP1QKSDDPXXIFW3.SPEC.XML" pat:id="HP1QKSDDPXXIFW3"><pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001"><pat:ApplicationHeaderDetails><pat:ApplicationNumber>14101777</pat:ApplicationNumber></pat:ApplicationHeaderDetails><pat:PageTotalQuantity>15</pat:PageTotalQuantity><pat:ParagraphTotalQuantity>6</pat:ParagraphTotalQuantity></pat:DocumentHeaderDetails><pat:MailRoomDate>2013-12-10</pat:MailRoomDate><pat:DocumentCreateDateText>2013-12-10</pat:DocumentCreateDateText><pat:DocumentTitle>SPECIFICATION DOCUMENT</pat:DocumentTitle><pat:Specification><?PageStart number='1'?><pat:P pat:pNumber="1" pat:id="p-1"><pat:BoundaryData><pat:HeaderText>ATTORNEY'S DOCKET                                                PATENT APPLICATION</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>141841 00074</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>(2</pat:OCRConfidenceData>107-MSA-US)</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData></pat:P><pat:Heading pat:id="h-1">SYSTEMS AND METHODS FOR PROVIDING ADAPTIVE PLAYBACK</pat:Heading><pat:Heading pat:id="h-2">EQUALIZATION IN AN AUDIO DEVICE</pat:Heading><pat:Heading pat:id="h-3"><pat:OCRConfidenceData pat:levelNumber='5'>H</pat:OCRConfidenceData>ELD OF DISCLOSURE</pat:Heading><pat:P pat:pNumber="2" pat:id="p-2"><pat:BoundaryData><pat:LineNumber>5</pat:LineNumber></pat:BoundaryData>The present disclosure relates in general to adaptive noise cancellation in connection with an acoustic transducer, and more particularly, to providing for adaptive playback equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation in an audio device <pat:BoundaryData><pat:HeaderText>9649013v 1</pat:HeaderText></pat:BoundaryData><?PageStart number='2'?><pat:BoundaryData><pat:HeaderText>ATTORNEY'S DOCKET                                             PATENT APPLICATION</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>141841 00074</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>(2</pat:OCRConfidenceData>107-MSA-US)</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>2</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData></pat:P><pat:Heading pat:id="h-4">BACKGROUND</pat:Heading><pat:P pat:pNumber="3" pat:id="p-3">Personal audio devices, such as mobile/cellular telephones, cordless telephones, and other consumer audio devices, such as mp3 players, are in widespread use Performance of such devices with respect to <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>tel<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>gibi<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>ty can be improved by provid<pat:OCRConfidenceData pat:levelNumber='668'>ing</pat:OCRConfidenceData> <pat:BoundaryData><pat:LineNumber>5</pat:LineNumber></pat:BoundaryData>noise cance<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>ng us<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g a microphone to measure amb<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>ent acoustic events and then us<pat:OCRConfidenceData pat:levelNumber='668'>ing</pat:OCRConfidenceData> signal process<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g to insert an anti-noise signal <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>to the output of the device to cancel the amb<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>ent acoustic events  Because the acoustic environment around personal audio devices such as wireless telephones can change dramatically, depend<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g on the sources of noise that are present and the position of the device itself, it is des<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>rable to adapt the noise <pat:BoundaryData><pat:LineNumber>10</pat:LineNumber></pat:BoundaryData>cance<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>ng to take into account such environmental changes Some personal audio devices also include equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zers Equalizers typically attempt to apply to a source audio signal an inverse of a response of the electro-acoustic path of the source audio signal through the transducer, in order to reduce the effects of the electro-acoustic path In most traditional approaches, equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation is performed with a <pat:BoundaryData><pat:LineNumber>15</pat:LineNumber></pat:BoundaryData>static equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer However, an adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer may provide better output sound qua<pat:OCRConfidenceData pat:levelNumber='6688'>lity</pat:OCRConfidenceData> than a static equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer, and thus, may be des<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>rable <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> many app<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>cations <pat:BoundaryData><pat:HeaderText>9649013v 1</pat:HeaderText></pat:BoundaryData><?PageStart number='3'?><pat:BoundaryData><pat:HeaderText>ATTORNEY'S DOCKET                                             PATENT APPLICATION</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>141841 00074</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>(2</pat:OCRConfidenceData>107-MSA-US)</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>3</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData></pat:P><pat:Heading pat:id="h-5">SUMMARY</pat:Heading><pat:P pat:pNumber="4" pat:id="p-4">In accordance with the teachings of the present disclosure, the disadvantages and problems associated with improving audio performance of a personal audio device may be reduced or eliminated <pat:BoundaryData><pat:LineNumber>5</pat:LineNumber></pat:BoundaryData>In accordance with embodiments of the present disclosure, a personal audio device may include a personal audio device hous<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g, a transducer, an error microphone, and one or more processing circuits The transducer may be coupled to the hous<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g for reproduc<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g an output audio signal includ<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g an equalized source audio signal for playback to a <pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>stener and an anti-noise signal for counte<pat:OCRConfidenceData pat:levelNumber='5'>n</pat:OCRConfidenceData>ng the effects of amb<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>ent audio <pat:BoundaryData><pat:LineNumber>10</pat:LineNumber></pat:BoundaryData>sounds in an acoustic output of the transducer The error microphone may be coupled to the hous<pat:OCRConfidenceData pat:levelNumber='668'>ing</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> proximity to the transducer for provid<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g an error microphone signal indicative of the acoustic output of the transducer and the amb<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>ent audio sounds at the transducer The one or more processing circuits may implement a noise cancellation system that generates the anti-noise signal to reduce the presence of the amb<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>ent audio <pat:BoundaryData><pat:LineNumber>15</pat:LineNumber></pat:BoundaryData>sounds heard by the <pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>stener based at least on the error microphone signal and an adaptive playback equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation system that generates the equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zed source audio signal from a source audio signal by adapt<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g, based at least on the error microphone signal, a response of the adaptive playback equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation system to minimize a difference between the source audio signal and the error microphone signal <pat:BoundaryData><pat:LineNumber>20</pat:LineNumber></pat:BoundaryData>In accordance with these and other embodiments of the present disclosure, a method may include receiv<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g an error microphone signal <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>dicative of an acoustic output of a transducer and amb<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>ent audio sounds at the acoustic output of the transducer The method may also include generat<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g an anti-noise signal to reduce the presence of the amb<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>ent audio sounds at the acoustic output of the transducer based at least on the error <pat:BoundaryData><pat:LineNumber>25</pat:LineNumber></pat:BoundaryData>microphone signal  The method may further include generating an equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zed source audio signal from a source audio signal by adapt<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g, based at least on the error microphone signal, a response of the adaptive playback equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation system to minimize a difference between the source audio signal and the error microphone signal The method may additionally include comb<pat:OCRConfidenceData pat:levelNumber='6666'>inin</pat:OCRConfidenceData>g the anti-noise signal with the <pat:PartName pat:idref='PN-00001'>equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zed source audio</pat:PartName> <pat:PartNumber pat:id='PN-00001'><pat:OCRConfidenceData pat:levelNumber='8'>3</pat:OCRConfidenceData>0</pat:PartNumber>   signal to generate an audio signal provided to the transducer <pat:BoundaryData><pat:HeaderText>9649013v 1</pat:HeaderText></pat:BoundaryData><?PageStart number='4'?><pat:BoundaryData><pat:HeaderText>ATTORNEY'S DOCKET                                             PATENT APPLICATION</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>141841 00074</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>(2</pat:OCRConfidenceData>107-MSA-US)</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>4</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>In accordance with these and other embodiments of the present disclosure, an <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>tegrated circuit for implement<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g at least a portion of a personal audio device may include an output, an error microphone <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>put, and one or more processing circuits The output may be configured to provide a signal to a transducer including both an equalized <pat:BoundaryData><pat:LineNumber>5</pat:LineNumber></pat:BoundaryData>source audio signal for playback to a <pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>stener and an anti-noise signal for counter<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g the effect of amb<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>ent audio sounds <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> an acoustic output of the transducer  The error microphone may be configured to receive an error microphone signal <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>dicative of the output of the transducer and the amb<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>ent audio sounds at the transducer The one or more process<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g circuits may implement a noise cancellation system that generates the anti- <pat:BoundaryData><pat:LineNumber>10</pat:LineNumber></pat:BoundaryData>noise signal to reduce the presence of the amb<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>ent audio sounds heard by the <pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>stener based at least on the error microphone signal and an adaptive playback equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation system that generates the equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zed source audio signal from a source audio signal by adapt<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g, based at least on the error microphone signal, a response of the adaptive playback equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation system to minimize a difference between the source audio signal <pat:BoundaryData><pat:LineNumber>15</pat:LineNumber></pat:BoundaryData>and the error microphone signal Technical advantages of the present disclosure may be readily apparent to one of ord<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>ary skill <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> the art from the figures, description and claims included herein The objects and advantages of the embodiments will be rea<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zed and achieved at least by the elements, features, and combinations particularly pointed out in the claims <pat:BoundaryData><pat:LineNumber>20</pat:LineNumber></pat:BoundaryData>It is to be understood that both the forego<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g general description and the following detailed des<pat:OCRConfidenceData pat:levelNumber='55'>cn</pat:OCRConfidenceData>ption are examples and explanatory and are not restrictive of the claims set forth <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> this disclosure <pat:BoundaryData><pat:HeaderText>9649013v 1</pat:HeaderText></pat:BoundaryData><?PageStart number='5'?><pat:BoundaryData><pat:HeaderText>ATTORNEY'S DOCKET                                              PATENT APPLICATION</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>141841 00074</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>(2</pat:OCRConfidenceData>107-MSA-US)</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>5</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData></pat:P><pat:Heading pat:id="h-6">BRIEF DESCRIPTION OF THE DRAWINGS</pat:Heading><pat:P pat:pNumber="5" pat:id="p-5">A more complete understanding of the present embodiments and advantages thereof may be acquired by refer<pat:OCRConfidenceData pat:levelNumber='66'>ri</pat:OCRConfidenceData>ng to the following des<pat:OCRConfidenceData pat:levelNumber='55'>cn</pat:OCRConfidenceData>ption taken in conjunction with the accompanying drawings, in which <pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>ke reference numbers indicate <pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>ke features, <pat:BoundaryData><pat:LineNumber>5</pat:LineNumber></pat:BoundaryData>and wherein FIGURE <pat:OCRConfidenceData pat:levelNumber='2'>1</pat:OCRConfidenceData>A is an illustration of an example personal audio device, in accordance with embodiments of the present disclosure, FIGURE <pat:OCRConfidenceData pat:levelNumber='2'>l</pat:OCRConfidenceData>B is an illustration of an example personal audio device with a headphone assembly coupled thereto, in accordance with embodiments of the present <pat:BoundaryData><pat:LineNumber>10</pat:LineNumber></pat:BoundaryData>disclosure, <pat:PartName pat:idref='PN-00002'>FIGURE</pat:PartName> <pat:PartNumber pat:id='PN-00002'>2</pat:PartNumber> is a block diagram of selected circuits within the <pat:PartName pat:idref='PN-00003'>personal audio device depicted in FIGURE</pat:PartName> <pat:PartNumber pat:id='PN-00003'>1</pat:PartNumber>, in accordance with embodiments of the present disclosure, <pat:PartName pat:idref='PN-00004'>FIGURE</pat:PartName> <pat:PartNumber pat:id='PN-00004'>3</pat:PartNumber> is a block diagram depict<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g selected signal processing circuits and functional blocks within an example active noise cance<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>ng (ANC) circuit of a coder- <pat:BoundaryData><pat:LineNumber>15</pat:LineNumber></pat:BoundaryData>decoder <pat:PartName pat:idref='PN-00005'>(CODEC) integrated circuit of FIGURE</pat:PartName> <pat:PartNumber pat:id='PN-00005'>3</pat:PartNumber>, in accordance with embodiments of the present disclosure, <pat:PartName pat:idref='PN-00006'>FIGURE</pat:PartName> <pat:PartNumber pat:id='PN-00006'>4</pat:PartNumber> is a block diagram depict<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g selected signal processing circuits and functional blocks with<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> an example adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation circuit of a <pat:PartName pat:idref='PN-00007'>coder-decoder (CODEC) <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>tegrated circuit of FIGURE</pat:PartName> <pat:PartNumber pat:id='PN-00007'>3</pat:PartNumber>, <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> accordance with embodiments of the <pat:BoundaryData><pat:LineNumber>20</pat:LineNumber></pat:BoundaryData>present disclosure, and <pat:PartName pat:idref='PN-00008'>FIGURE</pat:PartName> <pat:PartNumber pat:id='PN-00008'>5</pat:PartNumber> is a block diagram depict<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g selected signal processing circuits and functional blocks with<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> an example noise <pat:OCRConfidenceData pat:levelNumber='666'>inj</pat:OCRConfidenceData>ection portion of an <pat:PartName pat:idref='PN-00009'>adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation circuit of <pat:OCRConfidenceData pat:levelNumber='5'>H</pat:OCRConfidenceData>GURE</pat:PartName> <pat:PartNumber pat:id='PN-00009'>4</pat:PartNumber>, in accordance with embodiments of the <pat:PartName pat:idref='PN-00010'>present disclosure</pat:PartName> <pat:PartNumber pat:id='PN-00010'><pat:OCRConfidenceData pat:levelNumber='88'>25</pat:OCRConfidenceData></pat:PartNumber> <pat:BoundaryData><pat:HeaderText>9649013v 1</pat:HeaderText></pat:BoundaryData><?PageStart number='6'?><pat:BoundaryData><pat:HeaderText>ATTORNEY'S DOCKET                                             PATENT APPLICATION</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>141841 00074</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>(2</pat:OCRConfidenceData>107-MSA-US)</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>6</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData></pat:P><pat:Heading pat:id="h-7">DETAILED DESCRIPTION</pat:Heading><pat:P pat:pNumber="6" pat:id="p-6">Refe<pat:OCRConfidenceData pat:levelNumber='52'>rn</pat:OCRConfidenceData>ng now to FIGURE <pat:OCRConfidenceData pat:levelNumber='2'>1</pat:OCRConfidenceData>A, a <pat:PartName pat:idref='PN-00011'>personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00011'>10</pat:PartNumber> as illustrated <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> accordance with embodiments of the present disclosure is shown in proximity to a <pat:PartName pat:idref='PN-00012'>human ear</pat:PartName> <pat:PartNumber pat:id='PN-00012'>5</pat:PartNumber> <pat:PartName pat:idref='PN-00013'>Personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00013'>10</pat:PartNumber> is an example of a device in which techniques <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> <pat:BoundaryData><pat:LineNumber>5</pat:LineNumber></pat:BoundaryData>accordance with embodiments of the <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>vention may be employed, but it is understood that not all of the elements or <pat:PartName pat:idref='PN-00014'>configurations embodied in illustrated personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00014'>10</pat:PartNumber>, or <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> the circuits depicted <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> subsequent illustrations, are required in order to practice the <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>vention recited <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> the <pat:PartName pat:idref='PN-00015'>claims Personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00015'>10</pat:PartNumber> may include a <pat:PartName pat:idref='PN-00016'>transducer such as speaker SPKR that reproduces distant speech received by personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00016'>10</pat:PartNumber>, <pat:BoundaryData><pat:LineNumber>10</pat:LineNumber></pat:BoundaryData>along with other local audio events such as nngtones, stored audio program material, <pat:OCRConfidenceData pat:levelNumber='666'>inj</pat:OCRConfidenceData>ection of near-end speech (<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='8'>e</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='5'>,</pat:OCRConfidenceData> the speech of the <pat:PartName pat:idref='PN-00017'>user of personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00017'>10</pat:PartNumber>) to provide a balanced conversational perception, and <pat:PartName pat:idref='PN-00018'>other audio that requires reproduction by personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00018'>10</pat:PartNumber>, such as sources from webpages or <pat:PartName pat:idref='PN-00019'>other network commu<pat:OCRConfidenceData pat:levelNumber='66'>ni</pat:OCRConfidenceData>cations received by personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00019'>10</pat:PartNumber> and audio indications such as a <pat:BoundaryData><pat:LineNumber>15</pat:LineNumber></pat:BoundaryData>low battery <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>dication and other system event notifications A near-speech microphone NS may be provided to capture near-end speech, <pat:PartName pat:idref='PN-00020'>which is transmitted from personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00020'>10</pat:PartNumber> to the <pat:PartName pat:idref='PN-00021'>other conversation participant(s) Personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00021'>10</pat:PartNumber> may include adaptive noise cancellation (ANC) circuits and features that <pat:OCRConfidenceData pat:levelNumber='666'>inj</pat:OCRConfidenceData>ect an anti-noise signal into speaker SPKR to improve <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>tel<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>gibi<pat:OCRConfidenceData pat:levelNumber='6688'>lity</pat:OCRConfidenceData> <pat:BoundaryData><pat:LineNumber>20</pat:LineNumber></pat:BoundaryData>of the distant speech and other audio reproduced by speaker SPKR  A reference microphone R may be provided for measu<pat:OCRConfidenceData pat:levelNumber='5'>n</pat:OCRConfidenceData>ng the amb<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>ent acoustic environment, and may be positioned away from the typical position of a user's mouth, so that the near-end speech may be minimized in the signal produced by reference microphone R Another microphone, e<pat:OCRConfidenceData pat:levelNumber='66'>rr</pat:OCRConfidenceData>or microphone E, may be provided <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> order to further improve the ANC <pat:BoundaryData><pat:LineNumber>25</pat:LineNumber></pat:BoundaryData>operation by provid<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g a measure of the amb<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>ent audio combined with the audio reproduced by speaker SPKR close to <pat:PartName pat:idref='PN-00022'>ear</pat:PartName> <pat:PartNumber pat:id='PN-00022'>5</pat:PartNumber>, <pat:PartName pat:idref='PN-00023'>when personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00023'>10</pat:PartNumber> is <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> close proximity to <pat:PartName pat:idref='PN-00024'>ear</pat:PartName> <pat:PartNumber pat:id='PN-00024'>5</pat:PartNumber> <pat:PartName pat:idref='PN-00025'>Circuit</pat:PartName> <pat:PartNumber pat:id='PN-00025'>14</pat:PartNumber> <pat:PartName pat:idref='PN-00026'>within personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00026'>10</pat:PartNumber> may include an <pat:PartName pat:idref='PN-00027'>audio CODEC <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>tegrated circuit (IC)</pat:PartName> <pat:PartNumber pat:id='PN-00027'>20</pat:PartNumber> that receives the signals from reference microphone R, near-speech microphone NS, and error microphone E, and interfaces with other <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>tegrated <pat:BoundaryData><pat:LineNumber>30</pat:LineNumber></pat:BoundaryData>circuits such as a <pat:PartName pat:idref='PN-00028'>radio-frequency (RF) <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>tegrated circuit</pat:PartName> <pat:PartNumber pat:id='PN-00028'>12</pat:PartNumber> hav<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g a wireless telephone transceiver In some embodiments of the disclosure, the circuits and techniques disclosed <pat:BoundaryData><pat:HeaderText>9649013v 1</pat:HeaderText></pat:BoundaryData><?PageStart number='7'?><pat:BoundaryData><pat:HeaderText>ATTORNEY'S DOCKET                                             PATENT APPLICATION</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>141841 00074</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>(2</pat:OCRConfidenceData>107-MSA-US)</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>7</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>here<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> may be incorporated <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> a s<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>gle <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>tegrated circuit that includes control circuits and other functiona<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>ty for implement<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g the entirety of the personal audio device, such as an MP3 player-on-a-chip <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>tegrated circuit In these and other embodiments, the circuits and techniques disclosed herein may be implemented partially or fully in software and/or <pat:BoundaryData><pat:LineNumber>5</pat:LineNumber></pat:BoundaryData>fir<pat:OCRConfidenceData pat:levelNumber='5'>m</pat:OCRConfidenceData>ware embodied <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> computer-readable media and executable by a controller or other process<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g device In general, ANC techniques of the present disclosure measure amb<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>ent acoustic events (as opposed to the output of speaker SPKR and/or the near-end speech) imping<pat:OCRConfidenceData pat:levelNumber='668'>ing</pat:OCRConfidenceData> on reference microphone R, and by also measur<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g the same amb<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>ent acoustic events <pat:BoundaryData><pat:LineNumber>10</pat:LineNumber></pat:BoundaryData>imp<pat:OCRConfidenceData pat:levelNumber='66866'>ingin</pat:OCRConfidenceData>g on error microphone E, <pat:PartName pat:idref='PN-00029'>ANC process<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g circuits of personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00029'>10</pat:PartNumber> adapt an anti-noise signal generated out the output of speaker SPKR from the output of reference microphone R to have a characte<pat:OCRConfidenceData pat:levelNumber='5'>n</pat:OCRConfidenceData>stic that minimizes the amp<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>tude of the amb<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>ent acoustic events at error microphone E Because acoustic path P(z) extends from reference microphone R to error microphone E, ANC circuits are effectively estimat<pat:OCRConfidenceData pat:levelNumber='668'>ing</pat:OCRConfidenceData> <pat:BoundaryData><pat:LineNumber>15</pat:LineNumber></pat:BoundaryData>acoustic path P(z) while remo<pat:OCRConfidenceData pat:levelNumber='666'>vin</pat:OCRConfidenceData>g effects of an electro-acoustic path <pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData>(z) that represents the response of the <pat:PartName pat:idref='PN-00030'>audio output circuits of CODEC IC</pat:PartName> <pat:PartNumber pat:id='PN-00030'>20</pat:PartNumber> and the acoustic/electric transfer function of speaker SPKR including the coup<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>ng between speaker SPKR and error microphone E <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> the particular acoustic environment, which may be affected by the proximity and <pat:PartName pat:idref='PN-00031'>structure of ear</pat:PartName> <pat:PartNumber pat:id='PN-00031'>5</pat:PartNumber> and other physical objects and human head structures that <pat:BoundaryData><pat:LineNumber>20</pat:LineNumber></pat:BoundaryData>may be <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> proximity to <pat:PartName pat:idref='PN-00032'>personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00032'>10</pat:PartNumber>, <pat:PartName pat:idref='PN-00033'>when personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00033'>10</pat:PartNumber> is not firmly pressed to <pat:PartName pat:idref='PN-00034'>ear</pat:PartName> <pat:PartNumber pat:id='PN-00034'>5</pat:PartNumber> While the <pat:PartName pat:idref='PN-00035'>illustrated personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00035'>10</pat:PartNumber> <pat:OCRConfidenceData pat:levelNumber='666'>inc</pat:OCRConfidenceData>ludes a two- microphone ANC system with a third near-speech microphone NS, some aspects of the present invention may be practiced in a system that does not <pat:OCRConfidenceData pat:levelNumber='666'>inc</pat:OCRConfidenceData>lude separate error and reference microphones, or a wireless telephone that uses near-speech microphone NS to <pat:BoundaryData><pat:LineNumber>25</pat:LineNumber></pat:BoundaryData>perform the function of the reference microphone R Also, <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> personal audio devices designed only for audio playback, near-speech microphone NS will generally not be included, and the near-speech signal paths <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> the circuits described <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> further detail below may be omitted, without chang<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g the scope of the disclosure, other than to <pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>mit the options provided for <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>put to the microphone cove<pat:OCRConfidenceData pat:levelNumber='5'>n</pat:OCRConfidenceData>ng detection schemes In addition, <pat:OCRConfidenceData pat:levelNumber='8'>3</pat:OCRConfidenceData>0    <pat:PartName pat:idref='PN-00036'>although only one reference microphone R is depicted <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> FIGURE</pat:PartName> <pat:PartNumber pat:id='PN-00036'>1</pat:PartNumber>, the circuits and <pat:BoundaryData><pat:HeaderText>9649013v 1</pat:HeaderText></pat:BoundaryData><?PageStart number='8'?><pat:BoundaryData><pat:HeaderText>ATTORNEY'S DOCKET                                             PATENT APPLICATION</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>141841 00074</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>(2</pat:OCRConfidenceData>107-MSA-US)</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>8</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>techniques herein disclosed may be adapted, without chang<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g the scope of the disclosure, to personal audio devices includ<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g a plura<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>ty of reference microphones Refe<pat:OCRConfidenceData pat:levelNumber='52'>rn</pat:OCRConfidenceData>ng now to FIGURE <pat:OCRConfidenceData pat:levelNumber='55'>1B</pat:OCRConfidenceData>, <pat:PartName pat:idref='PN-00037'>personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00037'>10</pat:PartNumber> is depicted having a <pat:PartName pat:idref='PN-00038'>headphone assembly</pat:PartName> <pat:PartNumber pat:id='PN-00038'>13</pat:PartNumber> coupled to <pat:PartName pat:idref='PN-00039'>it via audio port</pat:PartName> <pat:PartNumber pat:id='PN-00039'>15</pat:PartNumber>  <pat:PartName pat:idref='PN-00040'>Audio port</pat:PartName> <pat:PartNumber pat:id='PN-00040'>15</pat:PartNumber> may be <pat:BoundaryData><pat:LineNumber>5</pat:LineNumber></pat:BoundaryData>commu<pat:OCRConfidenceData pat:levelNumber='66'>ni</pat:OCRConfidenceData>catively coupled to <pat:PartName pat:idref='PN-00041'>RF <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>tegrated circuit</pat:PartName> <pat:PartNumber pat:id='PN-00041'>12</pat:PartNumber> <pat:PartName pat:idref='PN-00042'>and/or CODEC IC</pat:PartName> <pat:PartNumber pat:id='PN-00042'>20</pat:PartNumber>, <pat:PartName pat:idref='PN-00043'>thus permitt<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g commu<pat:OCRConfidenceData pat:levelNumber='66'>ni</pat:OCRConfidenceData>cation between components of headphone assembly</pat:PartName> <pat:PartNumber pat:id='PN-00043'>13</pat:PartNumber> and one or <pat:PartName pat:idref='PN-00044'>more of RF integrated circuit</pat:PartName> <pat:PartNumber pat:id='PN-00044'>12</pat:PartNumber> <pat:PartName pat:idref='PN-00045'>and/or CODEC IC</pat:PartName> <pat:PartNumber pat:id='PN-00045'>20</pat:PartNumber>  As shown <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='6'>H</pat:OCRConfidenceData>GURE <pat:OCRConfidenceData pat:levelNumber='568'>1B,</pat:OCRConfidenceData> <pat:PartName pat:idref='PN-00046'>headphone assembly</pat:PartName> <pat:PartNumber pat:id='PN-00046'>13</pat:PartNumber> may include a <pat:PartName pat:idref='PN-00047'>combox</pat:PartName> <pat:PartNumber pat:id='PN-00047'>16</pat:PartNumber>, a left headphone 18A, and a <pat:OCRConfidenceData pat:levelNumber='5'>n</pat:OCRConfidenceData>ght headphone 18B As used <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> this disclosure, the term "headphone" broadly includes any <pat:BoundaryData><pat:LineNumber>10</pat:LineNumber></pat:BoundaryData>loudspeaker and structure associated therewith that is intended to be mecha<pat:OCRConfidenceData pat:levelNumber='66'>ni</pat:OCRConfidenceData>cally held <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> place proximate to a <pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>stener's ear or ear canal, and includes without <pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>mitation earphones, earbuds, and other similar devices  As more specific non-<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>mit<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g examples, "headphone," may refer to <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>tra-canal earphones, <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>tra-concha earphones, supra-concha earphones, and supra-aural earphones <pat:BoundaryData><pat:LineNumber>15</pat:LineNumber></pat:BoundaryData>Combox 16 or <pat:PartName pat:idref='PN-00048'>another portion of headphone assembly</pat:PartName> <pat:PartNumber pat:id='PN-00048'>13</pat:PartNumber> may have a near-speech microphone NS to capture near-end speech <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> addition to or <pat:PartName pat:idref='PN-00049'>in <pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>eu of near-speech microphone NS of personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00049'>10</pat:PartNumber> In addition, each headphone 18A, 18B may include a <pat:PartName pat:idref='PN-00050'>transducer such as speaker SPKR that reproduces distant speech received by personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00050'>10</pat:PartNumber>, along with other local audio events such as r<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>gtones, stored <pat:BoundaryData><pat:LineNumber>20</pat:LineNumber></pat:BoundaryData>audio program material, <pat:OCRConfidenceData pat:levelNumber='666'>inj</pat:OCRConfidenceData>ection of near-end speech (<pat:OCRConfidenceData pat:levelNumber='4'>I</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='8'>e</pat:OCRConfidenceData> , the speech of the <pat:PartName pat:idref='PN-00051'>user of personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00051'>10</pat:PartNumber>) to provide a balanced conversational perception, and <pat:PartName pat:idref='PN-00052'>other audio that requires reproduction by personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00052'>10</pat:PartNumber>, such as sources from webpages or <pat:PartName pat:idref='PN-00053'>other network commu<pat:OCRConfidenceData pat:levelNumber='66'>ni</pat:OCRConfidenceData>cations received by personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00053'>10</pat:PartNumber> and audio <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>dications such as a low battery <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>dication and other system event notifications <pat:BoundaryData><pat:LineNumber>25</pat:LineNumber></pat:BoundaryData>Each headphone 18A, 18B may include a reference microphone R for measu<pat:OCRConfidenceData pat:levelNumber='5'>n</pat:OCRConfidenceData>ng the amb<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>ent acoustic environment and an error microphone E for measu<pat:OCRConfidenceData pat:levelNumber='5'>n</pat:OCRConfidenceData>ng of the amb<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>ent audio comb<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>ed with the audio reproduced by speaker SPKR close to a <pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>stener's ear when such headphone 18A, 18B is engaged with the <pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>stener's ear    In some embodiments, <pat:PartName pat:idref='PN-00054'>CODEC IC</pat:PartName> <pat:PartNumber pat:id='PN-00054'>20</pat:PartNumber> may receive the signals from reference microphone R, near- <pat:BoundaryData><pat:LineNumber>30</pat:LineNumber></pat:BoundaryData>speech microphone NS, and e<pat:OCRConfidenceData pat:levelNumber='66'>rr</pat:OCRConfidenceData>or microphone E of each headphone and pe<pat:OCRConfidenceData pat:levelNumber='5'>r</pat:OCRConfidenceData>form adaptive noise cancellation for each headphone as des<pat:OCRConfidenceData pat:levelNumber='55'>cn</pat:OCRConfidenceData>bed here<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> In other embodiments, a <pat:BoundaryData><pat:HeaderText>9649013v 1</pat:HeaderText></pat:BoundaryData><?PageStart number='9'?><pat:BoundaryData><pat:HeaderText>ATTORNEY'S DOCKET                                             PATENT APPLICATION</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>141841 00074</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>(2</pat:OCRConfidenceData>107-MSA-US)</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>9</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>CODEC IC or <pat:PartName pat:idref='PN-00055'>another circuit may be present with<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> headphone assembly</pat:PartName> <pat:PartNumber pat:id='PN-00055'>13</pat:PartNumber>, commu<pat:OCRConfidenceData pat:levelNumber='66'>ni</pat:OCRConfidenceData>catively coupled to reference microphone R, near-speech microphone NS, and error microphone E, and configured to perform adaptive noise cancellation as described herein <pat:BoundaryData><pat:LineNumber>5</pat:LineNumber></pat:BoundaryData>The va<pat:OCRConfidenceData pat:levelNumber='5'>n</pat:OCRConfidenceData>ous microphones referenced <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> this disclosure, including reference microphones, error microphones, and near-speech microphones, may comprise any system, device, or apparatus configured to convert sound <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>cident at such microphone to an elect<pat:OCRConfidenceData pat:levelNumber='5'>n</pat:OCRConfidenceData>cal signal that may be processed by a controller, and may include without limitation an electrostatic microphone, a condenser microphone, an electret microphone, <pat:BoundaryData><pat:LineNumber>10</pat:LineNumber></pat:BoundaryData>an analog microelectromechanical systems (MEMS) microphone, a digital MEMS microphone, a piezoelectric microphone, a piezo-ceramic microphone, or dynamic microphone Refe<pat:OCRConfidenceData pat:levelNumber='52'>rn</pat:OCRConfidenceData>ng now to <pat:PartName pat:idref='PN-00056'>FIGURE</pat:PartName> <pat:PartNumber pat:id='PN-00056'>2</pat:PartNumber>, <pat:PartName pat:idref='PN-00057'>selected circuits with<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00057'>10</pat:PartNumber>, which <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> other embodiments may be placed <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> whole or part in other locations such as one <pat:BoundaryData><pat:LineNumber>15</pat:LineNumber></pat:BoundaryData>or <pat:PartName pat:idref='PN-00058'>more headphone assemblies</pat:PartName> <pat:PartNumber pat:id='PN-00058'>13</pat:PartNumber>, are shown in a <pat:PartName pat:idref='PN-00059'>block diagram CODEC IC</pat:PartName> <pat:PartNumber pat:id='PN-00059'>20</pat:PartNumber> may include an analog-to-digital conve<pat:OCRConfidenceData pat:levelNumber='66'>rt</pat:OCRConfidenceData>er (ADC) 2<pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData>A for receiving the reference microphone signal and generat<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g a digital representation ref of the reference microphone signal, an ADC 2<pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData>B for receiv<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g the error microphone signal and generat<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g a digital representation err of the error microphone signal, and an ADC 21C for receiv<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g the near <pat:BoundaryData><pat:LineNumber>20</pat:LineNumber></pat:BoundaryData>speech microphone signal and generat<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g a digital representation ns of the <pat:PartName pat:idref='PN-00060'>near speech microphone signal CODEC IC</pat:PartName> <pat:PartNumber pat:id='PN-00060'>20</pat:PartNumber> may generate an output for driv<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g speaker SPK<pat:OCRConfidenceData pat:levelNumber='8'>R</pat:OCRConfidenceData> from an amp<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>fier A<pat:OCRConfidenceData pat:levelNumber='45'>L,</pat:OCRConfidenceData> which may amp<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>fy the output of a <pat:PartName pat:idref='PN-00061'>digital-to-analog converter (DAC)</pat:PartName> <pat:PartNumber pat:id='PN-00061'>23</pat:PartNumber> that receives the output of a <pat:PartName pat:idref='PN-00062'>combiner</pat:PartName> <pat:PartNumber pat:id='PN-00062'>26</pat:PartNumber> <pat:PartName pat:idref='PN-00063'>Comb<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>er</pat:PartName> <pat:PartNumber pat:id='PN-00063'>26</pat:PartNumber> may comb<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>e an <pat:PartName pat:idref='PN-00064'>equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zed source audio signal generated by adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation circuit</pat:PartName> <pat:PartNumber pat:id='PN-00064'>40</pat:PartNumber> from audio <pat:BoundaryData><pat:LineNumber>25</pat:LineNumber></pat:BoundaryData>signals <pat:PartName pat:idref='PN-00065'><pat:OCRConfidenceData pat:levelNumber='2'>i</pat:OCRConfidenceData>a from <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>ternal audio sources</pat:PartName> <pat:PartNumber pat:id='PN-00065'>24</pat:PartNumber> <pat:PartName pat:idref='PN-00066'>and/or down<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>nk speech ds which may be received from radio frequency (RF) integrated circuit</pat:PartName> <pat:PartNumber pat:id='PN-00066'>22</pat:PartNumber>, the <pat:PartName pat:idref='PN-00067'>anti-noise signal generated by ANC circuit</pat:PartName> <pat:PartNumber pat:id='PN-00067'>30</pat:PartNumber>, which by convention has the same polarity as the noise in reference microphone signal ref and <pat:PartName pat:idref='PN-00068'>is therefore subtracted by comb<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>er</pat:PartName> <pat:PartNumber pat:id='PN-00068'>26</pat:PartNumber>, and a portion of near speech microphone signal ns so that the <pat:PartName pat:idref='PN-00069'>user of personal audio device</pat:PartName> <pat:PartNumber pat:id='PN-00069'>10</pat:PartNumber> may hear his or <pat:OCRConfidenceData pat:levelNumber='8'>3</pat:OCRConfidenceData>0   her own voice <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> proper relation to down<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>nk speech ds. Near speech microphone signal <pat:BoundaryData><pat:HeaderText>9649013v 1</pat:HeaderText></pat:BoundaryData><?PageStart number='10'?><pat:BoundaryData><pat:HeaderText>ATTORNEY'S DOCKET                                              PATENT APPLICATION</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>141841 00074</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>(2</pat:OCRConfidenceData>107-MSA-US)</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>10</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>ns may also be provided to <pat:PartName pat:idref='PN-00070'>RF integrated circuit</pat:PartName> <pat:PartNumber pat:id='PN-00070'>22</pat:PartNumber> and may be transmitted as upl<pat:OCRConfidenceData pat:levelNumber='668'>ink</pat:OCRConfidenceData> speech to the service provider via antenna ANT Refe<pat:OCRConfidenceData pat:levelNumber='6655'>rrmn</pat:OCRConfidenceData>g now to <pat:PartName pat:idref='PN-00071'>FIGURE</pat:PartName> <pat:PartNumber pat:id='PN-00071'>3</pat:PartNumber>, <pat:PartName pat:idref='PN-00072'>details of ANC circuit</pat:PartName> <pat:PartNumber pat:id='PN-00072'>30</pat:PartNumber> are shown in accordance with embodiments of the <pat:PartName pat:idref='PN-00073'>present disclosure Adaptive filter</pat:PartName> <pat:PartNumber pat:id='PN-00073'>32</pat:PartNumber> may receive reference <pat:BoundaryData><pat:LineNumber>5</pat:LineNumber></pat:BoundaryData>microphone signal ref and under ideal circumstances, may adapt its transfer function W(z) to be P(z)/S(z) to generate the anti-noise signal, which may be provided to an output combiner that comb<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>es the anti-noise signal with the audio to be reproduced by the transducer, <pat:PartName pat:idref='PN-00074'>as exemp<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>fied by comb<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>er</pat:PartName> <pat:PartNumber pat:id='PN-00074'>26</pat:PartNumber> <pat:PartName pat:idref='PN-00075'>of <pat:OCRConfidenceData pat:levelNumber='5'>H</pat:OCRConfidenceData>GURE</pat:PartName> <pat:PartNumber pat:id='PN-00075'>2</pat:PartNumber> The <pat:PartName pat:idref='PN-00076'>coefficients of adaptive filter</pat:PartName> <pat:PartNumber pat:id='PN-00076'>32</pat:PartNumber> may be controlled by a <pat:PartName pat:idref='PN-00077'>W coefficient control block</pat:PartName> <pat:PartNumber pat:id='PN-00077'>31</pat:PartNumber> that uses a correlation of <pat:BoundaryData><pat:LineNumber>10</pat:LineNumber></pat:BoundaryData>signals to determ<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>e the <pat:PartName pat:idref='PN-00078'>response of adaptive filter</pat:PartName> <pat:PartNumber pat:id='PN-00078'>32</pat:PartNumber>, which generally minimizes the error, <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> a least-mean squares sense, between those components of reference microphone signal ref present <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> error microphone signal err The <pat:PartName pat:idref='PN-00079'>signals compared by W coefficient control block</pat:PartName> <pat:PartNumber pat:id='PN-00079'>31</pat:PartNumber> may be the reference microphone signal ref as shaped by a copy of an estimate of the response of path <pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData>(z) provided by filter 34B and a playback corrected <pat:BoundaryData><pat:LineNumber>15</pat:LineNumber></pat:BoundaryData>error, <pat:PartName pat:idref='PN-00080'>labeled as "PBCE" in FIGURE</pat:PartName> <pat:PartNumber pat:id='PN-00080'>3</pat:PartNumber>, based at least <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> part on error microphone signal err The playback corrected error may be generated as des<pat:OCRConfidenceData pat:levelNumber='55'>cn</pat:OCRConfidenceData>bed <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> greater detail below By transform<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g reference microphone signal ref with a copy of the estimate of the response of path <pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData>(z), response SE<pat:OCRConfidenceData pat:levelNumber='5555868'>copy(z)</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='58'>of</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='666'>fil</pat:OCRConfidenceData>ter 34B, and minimiz<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g the difference between the resultant signal and error microphone signal err, <pat:PartName pat:idref='PN-00081'>adaptive filter</pat:PartName> <pat:PartNumber pat:id='PN-00081'>32</pat:PartNumber> may adapt <pat:BoundaryData><pat:LineNumber>20</pat:LineNumber></pat:BoundaryData>to the desired response of P(z)/S(z) In addition to error microphone signal err, the signal compared to the <pat:PartName pat:idref='PN-00082'>output of filter 34B by W coefficient control block</pat:PartName> <pat:PartNumber pat:id='PN-00082'>31</pat:PartNumber> may include an inverted amount of equalized source audio signal (e<pat:OCRConfidenceData pat:levelNumber='6'>g</pat:OCRConfidenceData> , downl<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>k audio signal ds and/or internal audio signal <pat:OCRConfidenceData pat:levelNumber='4'>t</pat:OCRConfidenceData>a), that has been processed by filter response SE(z), of which response SE<pat:OCRConfidenceData pat:levelNumber='5566868'>copy(z)</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='66'>is</pat:OCRConfidenceData> a copy By <pat:OCRConfidenceData pat:levelNumber='666'>inj</pat:OCRConfidenceData>ect<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g an <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>verted amount of equalized source audio <pat:BoundaryData><pat:LineNumber>25</pat:LineNumber></pat:BoundaryData>signal, <pat:PartName pat:idref='PN-00083'>adaptive filter</pat:PartName> <pat:PartNumber pat:id='PN-00083'>32</pat:PartNumber> may be prevented from adapt<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g to the relatively large amount of equalized source audio signal present in error microphone signal err  However, by transform<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g that <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>verted copy of equalized source audio signal with the estimate of the response of path S(z), the equalized source audio that is removed from error microphone signal err should match the expected version of the equalized source audio signal <pat:BoundaryData><pat:LineNumber>30</pat:LineNumber></pat:BoundaryData>reproduced at error microphone signal err, because the electrical and acoustical path of S(z) is the path taken by the equalized source audio signal to a<pat:OCRConfidenceData pat:levelNumber='666'>rri</pat:OCRConfidenceData>ve at error microphone <pat:BoundaryData><pat:HeaderText>9649013v 1</pat:HeaderText></pat:BoundaryData><?PageStart number='11'?><pat:BoundaryData><pat:HeaderText>ATTORNEY'S DOCKET                                             PATENT APPLICATION</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>141841 00074</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>(2</pat:OCRConfidenceData>107-MSA-US)</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='66'>11</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>E Filter 34B may not be an adaptive filter, per <pat:OCRConfidenceData pat:levelNumber='5'>s</pat:OCRConfidenceData>e, but may have an adjustable response that is tuned to match the response of adaptive filter 34A, so that the response of filter 34B tracks the adapting of adaptive filter 34A To implement the above, adaptive filter 34A may have coefficients controlled by <pat:BoundaryData><pat:LineNumber>5</pat:LineNumber></pat:BoundaryData>SE <pat:PartName pat:idref='PN-00084'>coefficient control block</pat:PartName> <pat:PartNumber pat:id='PN-00084'>33</pat:PartNumber>, which may compare the equalized source audio signal and a playback corrected error The playback corrected error may be equal to error microphone signal err after removal of the equalized source audio signal (as filtered by filter 34A to represent the expected playback audio delivered to error microphone E) by a <pat:PartName pat:idref='PN-00085'>combiner</pat:PartName> <pat:PartNumber pat:id='PN-00085'>36</pat:PartNumber> <pat:PartName pat:idref='PN-00086'>SE coefficient control block</pat:PartName> <pat:PartNumber pat:id='PN-00086'>33</pat:PartNumber> may correlate the actual equalized source <pat:BoundaryData><pat:LineNumber>10</pat:LineNumber></pat:BoundaryData>audio signal with the components of the equalized source audio signal that are present <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> error microphone signal err Adaptive filter 34A may thereby be adapted to generate a secondary estimate signal from the equalized source audio signal, that when subtracted from error microphone signal err to generate the playback corrected error, includes the content of error microphone signal err that is not due to the equalized source audio signal <pat:BoundaryData><pat:LineNumber>15</pat:LineNumber></pat:BoundaryData>Although <pat:PartName pat:idref='PN-00087'>FIGURES</pat:PartName> <pat:PartNumber pat:id='PN-00087'>2</pat:PartNumber> and 3 depict a feedforward ANC system in which an anti- noise signal is generated from a filtered reference microphone signal, any other suitable ANC system employ<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g an error microphone may be used <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> connection with the methods and systems disclosed herein For example, <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> some embodiments, an ANC circuit employ<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g feedback ANC, in which anti-noise is generated from a playback <pat:BoundaryData><pat:LineNumber>20</pat:LineNumber></pat:BoundaryData>corrected error signal, may be used <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>stead of or in addition to feedforward ANC, <pat:PartName pat:idref='PN-00088'>as depicted <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> FIGURES</pat:PartName> <pat:PartNumber pat:id='PN-00088'>2</pat:PartNumber> and 3 Refe<pat:OCRConfidenceData pat:levelNumber='52'>rn</pat:OCRConfidenceData>ng now to <pat:PartName pat:idref='PN-00089'>FIGURE</pat:PartName> <pat:PartNumber pat:id='PN-00089'>4</pat:PartNumber>, <pat:PartName pat:idref='PN-00090'>details of adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer circuit</pat:PartName> <pat:PartNumber pat:id='PN-00090'>40</pat:PartNumber> are shown in accordance with embodiments of the <pat:PartName pat:idref='PN-00091'>present disclosure Adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation filter</pat:PartName> <pat:PartNumber pat:id='PN-00091'>42</pat:PartNumber> may receive the source audio signal (e <pat:OCRConfidenceData pat:levelNumber='8'>g</pat:OCRConfidenceData>, down<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>nk speech ds and/or <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>ternal audio <pat:OCRConfidenceData pat:levelNumber='488'>ta)</pat:OCRConfidenceData> <pat:BoundaryData><pat:LineNumber>25</pat:LineNumber></pat:BoundaryData>and under ideal circumstances, may adapt its transfer function EQ(z) to be Delay/S(z) (wherein Delay is a signal delay added to a <pat:PartName pat:idref='PN-00092'>signal by delay element</pat:PartName> <pat:PartNumber pat:id='PN-00092'>48</pat:PartNumber>, as des<pat:OCRConfidenceData pat:levelNumber='55'>cn</pat:OCRConfidenceData>bed <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> greater detail below) to generate the equalized source audio signal, which may be provided to <pat:PartName pat:idref='PN-00093'>ANC circuit</pat:PartName> <pat:PartNumber pat:id='PN-00093'>30</pat:PartNumber> (as des<pat:OCRConfidenceData pat:levelNumber='55'>cn</pat:OCRConfidenceData>bed above) and provided to an output comb<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>er that combines the anti-noise signal with the equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zed source audio signal to be reproduced by <pat:BoundaryData><pat:LineNumber>30</pat:LineNumber></pat:BoundaryData>the transducer, <pat:PartName pat:idref='PN-00094'>as exemp<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>fied by comb<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>er</pat:PartName> <pat:PartNumber pat:id='PN-00094'>26</pat:PartNumber> <pat:PartName pat:idref='PN-00095'>of <pat:OCRConfidenceData pat:levelNumber='5'>H</pat:OCRConfidenceData>GURE</pat:PartName> <pat:PartNumber pat:id='PN-00095'>2</pat:PartNumber> The <pat:PartName pat:idref='PN-00096'>coefficients of adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation filter</pat:PartName> <pat:PartNumber pat:id='PN-00096'>42</pat:PartNumber> may be controlled by an <pat:PartName pat:idref='PN-00097'>equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer coefficient control block</pat:PartName> <pat:PartNumber pat:id='PN-00097'>41</pat:PartNumber> that <pat:BoundaryData><pat:HeaderText>9649013v 1</pat:HeaderText></pat:BoundaryData><?PageStart number='12'?><pat:BoundaryData><pat:HeaderText>ATTORNEY'S DOCKET                                             PATENT APPLICATION</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>141841 00074</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>(2</pat:OCRConfidenceData>107-MSA-US)</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>12</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>uses a correlation of signals to determ<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>e the <pat:PartName pat:idref='PN-00098'>response EQ(z) of adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation filter</pat:PartName> <pat:PartNumber pat:id='PN-00098'>42</pat:PartNumber>, which generally minimizes the error, <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> a least-mean squares sense, between the delayed source audio signal and the error microphone signal err, as des<pat:OCRConfidenceData pat:levelNumber='55'>cn</pat:OCRConfidenceData>bed <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> greater detail below <pat:BoundaryData><pat:LineNumber>5</pat:LineNumber></pat:BoundaryData>To implement the above, <pat:PartName pat:idref='PN-00099'>adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation filter</pat:PartName> <pat:PartNumber pat:id='PN-00099'>42</pat:PartNumber> <pat:PartName pat:idref='PN-00100'>may have coefficients controlled by equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer coefficient control block</pat:PartName> <pat:PartNumber pat:id='PN-00100'>41</pat:PartNumber>, which may compare a source audio signal and a delay corrected error The source audio signal may include down<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>nk audio signal ds and/or internal audio signal <pat:OCRConfidenceData pat:levelNumber='2'>i</pat:OCRConfidenceData>a The delay corrected error may be equal to error microphone signal err after removal of the source audio signal (as delayed by a delay <pat:BoundaryData><pat:LineNumber>10</pat:LineNumber></pat:BoundaryData>block 48) by a <pat:PartName pat:idref='PN-00101'>comb<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>er</pat:PartName> <pat:PartNumber pat:id='PN-00101'>46</pat:PartNumber> <pat:PartName pat:idref='PN-00102'>Equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation coefficient control block</pat:PartName> <pat:PartNumber pat:id='PN-00102'>41</pat:PartNumber> may correlate the actual source audio signal with the components of the source audio signal that are present in error microphone signal err The <pat:PartName pat:idref='PN-00103'>signals compared by equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer coefficient control block</pat:PartName> <pat:PartNumber pat:id='PN-00103'>41</pat:PartNumber> may be the source audio signal as shaped by a copy of an estimate of the response of path <pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData>(z) provided by filter 34C and a delay corrected error, based at least <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> <pat:BoundaryData><pat:LineNumber>15</pat:LineNumber></pat:BoundaryData>part on error microphone signal err In some embodiments, <pat:PartName pat:idref='PN-00104'>adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation filter</pat:PartName> <pat:PartNumber pat:id='PN-00104'>42</pat:PartNumber> may comprise a shelving filter, as is known <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> the art In such embodiments, at least one of a pole frequency and a zero frequency of the shelv<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g filter may be variable based on the error microphone signal <pat:BoundaryData><pat:LineNumber>20</pat:LineNumber></pat:BoundaryData>As mentioned above, <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> addition to error microphone signal err, the signal compared to the <pat:PartName pat:idref='PN-00105'>output of filter 34C by equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer coefficient control block</pat:PartName> <pat:PartNumber pat:id='PN-00105'>41</pat:PartNumber> may include a delayed amount source audio signal (e<pat:OCRConfidenceData pat:levelNumber='6'>g</pat:OCRConfidenceData> , down<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>nk audio signal ds and/or internal audio signal <pat:OCRConfidenceData pat:levelNumber='4'>t</pat:OCRConfidenceData>a), <pat:PartName pat:idref='PN-00106'>that has been delayed by delay block</pat:PartName> <pat:PartNumber pat:id='PN-00106'>48</pat:PartNumber> By delaying the source audio signal by at least the delay of the secondary path represented by <pat:OCRConfidenceData pat:levelNumber='5'>S</pat:OCRConfidenceData>(z), the system formed <pat:BoundaryData><pat:LineNumber>25</pat:LineNumber></pat:BoundaryData>by <pat:PartName pat:idref='PN-00107'>adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation circuit</pat:PartName> <pat:PartNumber pat:id='PN-00107'>40</pat:PartNumber> may operate as a causal system In some embodiments, a <pat:PartName pat:idref='PN-00108'>noise <pat:OCRConfidenceData pat:levelNumber='666'>inj</pat:OCRConfidenceData>ection portion</pat:PartName> <pat:PartNumber pat:id='PN-00108'>50</pat:PartNumber> <pat:PartName pat:idref='PN-00109'>may <pat:OCRConfidenceData pat:levelNumber='666'>inj</pat:OCRConfidenceData>ect noise <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>to each side of equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer coefficient control block</pat:PartName> <pat:PartNumber pat:id='PN-00109'>41</pat:PartNumber>, <pat:PartName pat:idref='PN-00110'>as shown in FIGURE</pat:PartName> <pat:PartNumber pat:id='PN-00110'>4</pat:PartNumber> For example, <pat:PartName pat:idref='PN-00111'>noise <pat:OCRConfidenceData pat:levelNumber='866'>inj</pat:OCRConfidenceData>ection portion</pat:PartName> <pat:PartNumber pat:id='PN-00111'>50</pat:PartNumber> may i<pat:OCRConfidenceData pat:levelNumber='66'>nj</pat:OCRConfidenceData>ect an x-side i<pat:OCRConfidenceData pat:levelNumber='66'>nj</pat:OCRConfidenceData>ected noise signal into the filtered source audio signal generated by filter 34C (e<pat:OCRConfidenceData pat:levelNumber='6'>g</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='5'>,</pat:OCRConfidenceData> by a comb<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>er which is not exp<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>citly shown) <pat:BoundaryData><pat:LineNumber>30</pat:LineNumber></pat:BoundaryData>and an e-side i<pat:OCRConfidenceData pat:levelNumber='66'>nj</pat:OCRConfidenceData>ected noise signal into the delay corrected error (e<pat:OCRConfidenceData pat:levelNumber='6'>g</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='5'>,</pat:OCRConfidenceData> <pat:PartName pat:idref='PN-00112'>by comb<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>er</pat:PartName> <pat:PartNumber pat:id='PN-00112'>46</pat:PartNumber> or another combiner which is not exp<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>citly shown) <pat:BoundaryData><pat:HeaderText>9649013v 1</pat:HeaderText></pat:BoundaryData><?PageStart number='13'?><pat:BoundaryData><pat:HeaderText>ATTORNEY'S DOCKET                                               PATENT APPLICATION</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>141841 00074</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>(2</pat:OCRConfidenceData>107-MSA-US)</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>13</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>Refe<pat:OCRConfidenceData pat:levelNumber='6655'>rrmn</pat:OCRConfidenceData>g now to <pat:PartName pat:idref='PN-00113'>FIGURE</pat:PartName> <pat:PartNumber pat:id='PN-00113'>5</pat:PartNumber>, details of a <pat:PartName pat:idref='PN-00114'>noise <pat:OCRConfidenceData pat:levelNumber='666'>inj</pat:OCRConfidenceData>ection portion</pat:PartName> <pat:PartNumber pat:id='PN-00114'>50</pat:PartNumber>, <pat:PartName pat:idref='PN-00115'>which may be present in some embodiments of adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer circuit</pat:PartName> <pat:PartNumber pat:id='PN-00115'>40</pat:PartNumber> in or are shown in accordance with embodiments of the <pat:PartName pat:idref='PN-00116'>present disclosure Noise i<pat:OCRConfidenceData pat:levelNumber='66'>nj</pat:OCRConfidenceData>ection portion</pat:PartName> <pat:PartNumber pat:id='PN-00116'>50</pat:PartNumber> may include a <pat:PartName pat:idref='PN-00117'>white noise source</pat:PartName> <pat:PartNumber pat:id='PN-00117'>54</pat:PartNumber> for generat<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g white noise (e<pat:OCRConfidenceData pat:levelNumber='6'>g</pat:OCRConfidenceData> , an audio signal with a <pat:BoundaryData><pat:LineNumber>5</pat:LineNumber></pat:BoundaryData>constant amp<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>tude across all frequencies of <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>terest, such as those frequencies with<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> the range of human hear<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g) A <pat:PartName pat:idref='PN-00118'>frequency shap<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g filter</pat:PartName> <pat:PartNumber pat:id='PN-00118'>56</pat:PartNumber> may generate the x-side i<pat:OCRConfidenceData pat:levelNumber='66'>nj</pat:OCRConfidenceData>ected noise signal by filte<pat:OCRConfidenceData pat:levelNumber='5'>n</pat:OCRConfidenceData>ng the white noise signal, wherein a response of the <pat:PartName pat:idref='PN-00119'>frequency shap<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g filter is shaped by frequency shap<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g filter coefficient control block</pat:PartName> <pat:PartNumber pat:id='PN-00119'>58</pat:PartNumber> <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> conformity with the playback corrected error, response SE(z) of filter 34A, or other <pat:BoundaryData><pat:LineNumber>10</pat:LineNumber></pat:BoundaryData>suitable signal or response  In some embodiments, <pat:PartName pat:idref='PN-00120'>coefficient control block</pat:PartName> <pat:PartNumber pat:id='PN-00120'>58</pat:PartNumber> may implement an adaptive <pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>near prediction coefficient system which estimates a frequency spectrum of the playback corrected error, response SE(z) of filter 34A, or other suitable signal or <pat:PartName pat:idref='PN-00121'>response received by noise <pat:OCRConfidenceData pat:levelNumber='666'>inj</pat:OCRConfidenceData>ection portion</pat:PartName> <pat:PartNumber pat:id='PN-00121'>50</pat:PartNumber> Accord<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>gly, the <pat:PartName pat:idref='PN-00122'>noise signal generated by frequency shap<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g filter</pat:PartName> <pat:PartNumber pat:id='PN-00122'>56</pat:PartNumber> may comprise the white noise signal filtered <pat:BoundaryData><pat:LineNumber>15</pat:LineNumber></pat:BoundaryData>such that the white noise signal <pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>s attenuated or e<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>minated <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> those frequencies with<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> the frequency spectrum of the playback corrected error, such that the <pat:PartName pat:idref='PN-00123'>output of frequency shap<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g filter</pat:PartName> <pat:PartNumber pat:id='PN-00123'>56</pat:PartNumber> has a frequency spectrum with greater mag<pat:OCRConfidenceData pat:levelNumber='66'>ni</pat:OCRConfidenceData>tude content at frequencies in which the playback corrected error, response SE(z) of filter 34A, or other suitable signal or <pat:PartName pat:idref='PN-00124'>response received by noise i<pat:OCRConfidenceData pat:levelNumber='66'>nj</pat:OCRConfidenceData>ection portion</pat:PartName> <pat:PartNumber pat:id='PN-00124'>50</pat:PartNumber> is at or is substantially near zero <pat:BoundaryData><pat:LineNumber>20</pat:LineNumber></pat:BoundaryData>In these and other embodiments, <pat:PartName pat:idref='PN-00125'>noise <pat:OCRConfidenceData pat:levelNumber='666'>inj</pat:OCRConfidenceData>ection portion</pat:PartName> <pat:PartNumber pat:id='PN-00125'>50</pat:PartNumber> may include an adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer filter 42<pat:OCRConfidenceData pat:levelNumber='5'>B</pat:OCRConfidenceData>, which may be a <pat:PartName pat:idref='PN-00126'>copy of adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation filter</pat:PartName> <pat:PartNumber pat:id='PN-00126'>42</pat:PartNumber>, wherein adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer filter 42B app<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>es its response EQ<pat:OCRConfidenceData pat:levelNumber='5566'>copy</pat:OCRConfidenceData>(z) to the x-side <pat:OCRConfidenceData pat:levelNumber='666'>inj</pat:OCRConfidenceData>ection noise, in order to generate the e-side <pat:OCRConfidenceData pat:levelNumber='666'>inj</pat:OCRConfidenceData>ection noise signal The i<pat:OCRConfidenceData pat:levelNumber='66'>nj</pat:OCRConfidenceData>ected noise signals may serve to b<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>as, to below a predetermined maximum, a mag<pat:OCRConfidenceData pat:levelNumber='66'>ni</pat:OCRConfidenceData>tude of the response of adaptive <pat:BoundaryData><pat:LineNumber>25</pat:LineNumber></pat:BoundaryData>equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation <pat:PartName pat:idref='PN-00127'>filter</pat:PartName> <pat:PartNumber pat:id='PN-00127'>42</pat:PartNumber> correspond<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g to a frequency in which the response of secondary path estimate filter 34C is substantially zero In addition to or alternatively to the noise <pat:OCRConfidenceData pat:levelNumber='666'>inj</pat:OCRConfidenceData>ection described above, other approaches may be used <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> order to <pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>mit mag<pat:OCRConfidenceData pat:levelNumber='66'>ni</pat:OCRConfidenceData>tudes of the <pat:PartName pat:idref='PN-00128'>response of adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation filter</pat:PartName> <pat:PartNumber pat:id='PN-00128'>42</pat:PartNumber> at frequencies correspond<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g to nulls in the response SE(z) below a <pat:BoundaryData><pat:LineNumber>30</pat:LineNumber></pat:BoundaryData>predetermined acceptable level  For example, <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> some embodiments, a <pat:PartName pat:idref='PN-00129'>number of coefficients of adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer filter</pat:PartName> <pat:PartNumber pat:id='PN-00129'>42</pat:PartNumber> and <pat:PartName pat:idref='PN-00130'>equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer coefficient control block</pat:PartName> <pat:PartNumber pat:id='PN-00130'>41</pat:PartNumber> may <pat:BoundaryData><pat:HeaderText>9649013v 1</pat:HeaderText></pat:BoundaryData><?PageStart number='14'?><pat:BoundaryData><pat:HeaderText>ATTORNEY'S DOCKET                                             PATENT APPLICATION</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>141841 00074</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>(2</pat:OCRConfidenceData>107-MSA-US)</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>14</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>be selected <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> order to <pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>mit mag<pat:OCRConfidenceData pat:levelNumber='66'>ni</pat:OCRConfidenceData>tudes of the <pat:PartName pat:idref='PN-00131'>response of adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation filter</pat:PartName> <pat:PartNumber pat:id='PN-00131'>42</pat:PartNumber> at frequencies correspond<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g to nulls <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> the response SE(z) below a predetermined acceptable level In these and other embodiments, the <pat:PartName pat:idref='PN-00132'>response of adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer filter</pat:PartName> <pat:PartNumber pat:id='PN-00132'>42</pat:PartNumber> may <pat:BoundaryData><pat:LineNumber>5</pat:LineNumber></pat:BoundaryData>be disabled from adapt<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g when conditions are present that may h<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>der the <pat:PartName pat:idref='PN-00133'>abi<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>ty of adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer filter</pat:PartName> <pat:PartNumber pat:id='PN-00133'>42</pat:PartNumber> to converge or adapt For example, the <pat:PartName pat:idref='PN-00134'>response of adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer filter</pat:PartName> <pat:PartNumber pat:id='PN-00134'>42</pat:PartNumber> may be disabled from adapt<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g when the spectral density of the source audio signal <pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>s lesser than a mi<pat:OCRConfidenceData pat:levelNumber='66'>ni</pat:OCRConfidenceData>mum spectral density As another example, the <pat:PartName pat:idref='PN-00135'>response of adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer filter</pat:PartName> <pat:PartNumber pat:id='PN-00135'>42</pat:PartNumber> may be disabled from adapt<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g when a transducer has been <pat:BoundaryData><pat:LineNumber>10</pat:LineNumber></pat:BoundaryData>removed from a proximity of an ear of a <pat:PartName pat:idref='PN-00136'><pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>stener (which may be determ<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>ed as described in U S Patent App<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>cation Se<pat:OCRConfidenceData pat:levelNumber='5'>n</pat:OCRConfidenceData>al No</pat:PartName> <pat:PartNumber pat:id='PN-00136'>13</pat:PartNumber>/844,602 filed March 15, 2013, entitled "Mo<pat:OCRConfidenceData pat:levelNumber='66'>ni</pat:OCRConfidenceData>tor<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g of Speaker Impedance to <pat:PartName pat:idref='PN-00137'>Detect Pressure App<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>ed Between Mobile Device <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> Ear," as des<pat:OCRConfidenceData pat:levelNumber='55'>cn</pat:OCRConfidenceData>bed <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='8'>U</pat:OCRConfidenceData> S Patent App<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>cation Se<pat:OCRConfidenceData pat:levelNumber='5'>n</pat:OCRConfidenceData>al No</pat:PartName> <pat:PartNumber pat:id='PN-00137'>13</pat:PartNumber>/310,380 filed December 2, 2011, entitled "Ear-Coup<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>ng Detection and Adjustment of Adaptive Response in Noise- <pat:BoundaryData><pat:LineNumber>15</pat:LineNumber></pat:BoundaryData>Cancel<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>ng <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> Personal Audio Devices," or as otherwise known <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> the art)  As an additional example, the <pat:PartName pat:idref='PN-00138'>response of adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer filter</pat:PartName> <pat:PartNumber pat:id='PN-00138'>42</pat:PartNumber> may be disabled from adapt<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g when "c<pat:OCRConfidenceData pat:levelNumber='668866'>lippin</pat:OCRConfidenceData>g" may occur, as <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>dicated by a mag<pat:OCRConfidenceData pat:levelNumber='66'>ni</pat:OCRConfidenceData>tude of the audio output signal driving a transducer be<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g with<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> a predetermined threshold of a mag<pat:OCRConfidenceData pat:levelNumber='66'>ni</pat:OCRConfidenceData>tude of a power supply for driv<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g the output audio signal As a further example, the response of <pat:BoundaryData><pat:LineNumber>20</pat:LineNumber></pat:BoundaryData>adaptive <pat:PartName pat:idref='PN-00139'>equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zer filter</pat:PartName> <pat:PartNumber pat:id='PN-00139'>42</pat:PartNumber> may be disabled from adapting when a physical displacement of a transducer is such that its displacement as a function of the output audio signal driv<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g the transducer is substantially non<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>near In some embodiments, the sequencing of adaptation of response SE(z) of filter 34A and <pat:PartName pat:idref='PN-00140'>response EQ(z) of adaptive equa<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>zation filter</pat:PartName> <pat:PartNumber pat:id='PN-00140'>42</pat:PartNumber> may be configured to ensure <pat:BoundaryData><pat:LineNumber>25</pat:LineNumber></pat:BoundaryData>stabi<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>ty of adaptation of response SE(z) and response EQ(z)  For example, in such embodiments, <pat:PartName pat:idref='PN-00141'>CODEC IC</pat:PartName> <pat:PartNumber pat:id='PN-00141'>20</pat:PartNumber> may be configured to train response SE(z) prior to trai<pat:OCRConfidenceData pat:levelNumber='6688'>ning</pat:OCRConfidenceData> of response EQ(z), as response EQ(z) rel<pat:OCRConfidenceData pat:levelNumber='5'>i</pat:OCRConfidenceData>es on response SE<pat:OCRConfidenceData pat:levelNumber='5566868'>copy(z)</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='66'>fo</pat:OCRConfidenceData>r stabi<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>ty After both responses SE(z) and EQ(z) have been trained, trai<pat:OCRConfidenceData pat:levelNumber='66'>ni</pat:OCRConfidenceData>ng may alternate between the responses As another example, <pat:PartName pat:idref='PN-00142'>CODEC IC</pat:PartName> <pat:PartNumber pat:id='PN-00142'>20</pat:PartNumber> may be configured to <pat:PartName pat:idref='PN-00143'>such that response</pat:PartName> <pat:PartNumber pat:id='PN-00143'>30</pat:PartNumber>    EQ(z) trains only while response SE(z) is trai<pat:OCRConfidenceData pat:levelNumber='66'>ni</pat:OCRConfidenceData>ng, aga<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> because response EQ(z) re<pat:OCRConfidenceData pat:levelNumber='6688'>lies</pat:OCRConfidenceData> <pat:BoundaryData><pat:HeaderText>9649013v 1</pat:HeaderText></pat:BoundaryData><?PageStart number='15'?><pat:BoundaryData><pat:HeaderText>ATTORNEY'S DOCKET                                             PATENT APPLICATION</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>141841 00074</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>(2</pat:OCRConfidenceData>107-MSA-US)</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>15</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>on response SE<pat:OCRConfidenceData pat:levelNumber='5555868'>copy(z)</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='66'>fo</pat:OCRConfidenceData>r stabi<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>ty As a further example, <pat:PartName pat:idref='PN-00144'>CODEC IC</pat:PartName> <pat:PartNumber pat:id='PN-00144'>20</pat:PartNumber> may be configured such that response EQ(z) adapts at a slower rate than response SE(z) This disclosure encompasses all changes, substitutions, va<pat:OCRConfidenceData pat:levelNumber='5'>n</pat:OCRConfidenceData>ations, alterations, and modifications to the example embodiments here<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> that a person having ordinary skill in <pat:BoundaryData><pat:LineNumber>5</pat:LineNumber></pat:BoundaryData>the art would comprehend Similarly, where appropriate, the appended claims encompass all changes, substitutions, va<pat:OCRConfidenceData pat:levelNumber='5'>n</pat:OCRConfidenceData>ations, alterations, and modifications to the example embodiments herein that a person having ordinary skill in the art would comprehend Moreover, reference <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> the appended claims to an apparatus or system or a component of an apparatus or system being adapted to, arranged to, capable of, configured to, enabled <pat:BoundaryData><pat:LineNumber>10</pat:LineNumber></pat:BoundaryData>to, operable to, or operative to perform a particular function encompasses that apparatus, system, or component, whether or not it or that particular function is activated, turned on, or unlocked, as long as that apparatus, system, or component is so adapted, arranged, capable, configured, enabled, operable, or operative All examples and conditional language recited herein are <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>tended for pedagogical <pat:BoundaryData><pat:LineNumber>15</pat:LineNumber></pat:BoundaryData>objects to aid the reader in understanding the <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>vention and the concepts contributed by the <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>ventor to furthe<pat:OCRConfidenceData pat:levelNumber='5'>n</pat:OCRConfidenceData>ng the art, and are construed as be<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g without <pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>mitation to such specifically recited examples and conditions  Although embodiments of the present inventions have been described <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> detail, it should be understood that va<pat:OCRConfidenceData pat:levelNumber='5'>n</pat:OCRConfidenceData>ous changes, substitutions, and alterations could be made hereto without departing from the spirit and <pat:OCRConfidenceData pat:levelNumber='8'>2</pat:OCRConfidenceData>0   scope of the disclosure <pat:BoundaryData><pat:HeaderText>9649013v 1</pat:HeaderText></pat:BoundaryData></pat:P></pat:Specification></pat:SpecificationDocument>

applicant/14102037.xml

@@ -0,0 +1,2 @@
+<?xml version="1.0" encoding="utf-8"?><uspat:SpecificationDocument xmlns:uscom="urn:us:gov:doc:uspto:common" xmlns:uspat="urn:us:gov:doc:uspto:patent" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:com="http://www.wipo.int/standards/XMLSchema/ST96/Common" xmlns:pat="http://www.wipo.int/standards/XMLSchema/ST96/Patent" uscom:vendorName="VASTEC" uscom:createDateTime="2019-10-04T23:32:52Z" com:st96Version="V2_1" com:ipoVersion="US_V7_1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent Patent/V7_1/Schema/USPatent/Document/SpecificationDocument_V7_1.xsd" com:documentFileName="14102037.10-04-2019.K1CQRYFERXEAPX0.SPEC.XML" com:id="K1CQRYFERXEAPX0">
+<uspat:DocumentMetadata com:id="ID0000001"><uscom:DocumentCode>SPEC</uscom:DocumentCode><uscom:ApplicationNumberText uscom:electronicText="14102037">14102037</uscom:ApplicationNumberText><com:PageTotalQuantity>1</com:PageTotalQuantity><uscom:ParagraphTotalQuantity>24</uscom:ParagraphTotalQuantity><uscom:OfficialDate>2019-10-04</uscom:OfficialDate></uspat:DocumentMetadata><?PageStart number='1'?><uscom:P com:pNumber="1" com:id="p-1" uscom:indentationLevelNumber="L3">Application Ser. No. 14/102,037</uscom:P><uscom:P com:pNumber="2" com:id="p-2" uscom:indentationLevelNumber="L3">Attorney Docket No. 7500-008</uscom:P><uscom:P com:pNumber="3" com:id="p-3" uscom:indentationLevelNumber="L4">Client Docket No. P2109US1</uscom:P><uscom:Heading com:id="h-1"><com:U>AMENDMENTS TO THE SPECIFICATION</com:U></uscom:Heading><uscom:P com:pNumber="4" com:id="p-4" uscom:indentationLevelNumber="L2">Please <uscom:PartName com:idrefs="PN-00001">amend </uscom:PartName><uscom:PartNumber com:id="PN-00001">0047</uscom:PartNumber> as follows:</uscom:P><uscom:P com:pNumber="5" com:id="p-5" uscom:indentationLevelNumber="L2">In some cases, a solid state lighting apparatus may be fitted to an installation that does</uscom:P><uscom:P com:pNumber="6" com:id="p-6" uscom:indentationLevelNumber="L1">not have a dimming system. In such cases, it is desirable to provide a solid state lighting</uscom:P><uscom:P com:pNumber="7" com:id="p-7" uscom:indentationLevelNumber="L1">apparatus that can be dimmed even without an external dimming system. That is<uscom:OCRConfidenceData uscom:ocrConfidenceCode="6">,</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="68"><com:U>it</com:U></uscom:OCRConfidenceData> is desirable</uscom:P><uscom:P com:pNumber="8" com:id="p-8" uscom:indentationLevelNumber="L1">to provide a solid state lighting apparatus that can be dimmed absent the presence of a</uscom:P><uscom:P com:pNumber="9" com:id="p-9" uscom:indentationLevelNumber="L1">dimming controller that generates DALI or 0-10V dimming signal, a phase cut dimmer, or</uscom:P><uscom:P com:pNumber="10" com:id="p-10" uscom:indentationLevelNumber="L1">multiple switches needed for step dimming.</uscom:P><uscom:P com:pNumber="11" com:id="p-11"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="88">an</uscom:OCRConfidenceData>ge(<uscom:OCRConfidenceData uscom:ocrConfidenceCode="48">s)</uscom:OCRConfidenceData>  <com:Image com:id="p-00000" com:imageWrappingStyleCategory="Inline" com:orientationCategory="Portrait" com:imageContentCategory="Chemistry"><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:FileName>14102037.10-04-2019.K1CQRYFERXEAPX0.SPEC.1.12.248.1229.388.1283.svg</com:FileName><com:HeightMeasure com:measureUnitCode="In">0.18</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="In">0.467</com:WidthMeasure><com:Alt>Chemistry</com:Alt><com:ColourModeCategory>Black and white</com:ColourModeCategory></com:Image> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="256526656">document,</uscom:OCRConfidenceData>     Pl<com:Sub>eas</com:Sub>e amend   <com:Image com:id="p-00001" com:imageWrappingStyleCategory="Inline" com:orientationCategory="Portrait" com:imageContentCategory="Chemistry"><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:FileName>14102037.10-04-2019.K1CQRYFERXEAPX0.SPEC.1.13.795.1280.893.1352.svg</com:FileName><com:HeightMeasure com:measureUnitCode="In">0.24</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="In">0.327</com:WidthMeasure><com:Alt>Chemistry</com:Alt><com:ColourModeCategory>Black and white</com:ColourModeCategory></com:Image> as follows:</uscom:P><uscom:P com:pNumber="12" com:id="p-12"><com:Image com:id="p-00002" com:imageWrappingStyleCategory="Inline" com:orientationCategory="Portrait" com:imageContentCategory="Chemistry"><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:FileName>14102037.10-04-2019.K1CQRYFERXEAPX0.SPEC.1.14.105.1369.230.1411.svg</com:FileName><com:HeightMeasure com:measureUnitCode="In">0.14</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="In">0.417</com:WidthMeasure><com:Alt>Chemistry</com:Alt><com:ColourModeCategory>Black and white</com:ColourModeCategory></com:Image><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8"><com:Sub>9</com:Sub></uscom:OCRConfidenceData> <com:Sub>201</com:Sub> <com:Sub>9</com:Sub>       The input voltage may be determined to have been toggled if the voltage is switched off</uscom:P><uscom:P com:pNumber="13" com:id="p-13" uscom:indentationLevelNumber="L1">and then back on within a predetermined number of seconds, for example, if the voltage is</uscom:P><uscom:P com:pNumber="14" com:id="p-14" uscom:indentationLevelNumber="L1">switched back on within 1 second e<uscom:OCRConfidenceData uscom:ocrConfidenceCode="4">r</uscom:OCRConfidenceData> <com:U>of</com:U> being switched off. However, the invention is not limited</uscom:P><uscom:P com:pNumber="15" com:id="p-15" uscom:indentationLevelNumber="L1">to any particular toggle delay, and the toggle delay may be user configurable.</uscom:P><uscom:P com:pNumber="16" com:id="p-16" uscom:indentationLevelNumber="L2">Please <uscom:PartName com:idrefs="PN-00002">amend </uscom:PartName><uscom:PartNumber com:id="PN-00002">0058</uscom:PartNumber> as follows:</uscom:P><uscom:P com:pNumber="17" com:id="p-17" uscom:indentationLevelNumber="L2">Figure 4 is a more detailed block diagram of a <uscom:PartName com:idrefs="PN-00003">solid state lighting apparatus </uscom:PartName><uscom:PartNumber com:id="PN-00003">20</uscom:PartNumber> according</uscom:P><uscom:P com:pNumber="18" com:id="p-18" uscom:indentationLevelNumber="L1">to some embodiments. As shown therein, the <uscom:PartName com:idrefs="PN-00004">dimming control circuit </uscom:PartName><uscom:PartNumber com:id="PN-00004">22</uscom:PartNumber> includes an AC detector</uscom:P><uscom:P com:pNumber="19" com:id="p-19" uscom:indentationLevelNumber="L1">224 and a <uscom:PartName com:idrefs="PN-00005">micro controller </uscom:PartName><uscom:PartNumber com:id="PN-00005">226.</uscom:PartNumber> <com:Del>The </com:Del><uscom:PartName com:idrefs="PN-00006">LED driver </uscom:PartName><uscom:PartNumber com:id="PN-00006">24</uscom:PartNumber><com:Del> includes an AC </com:Del><uscom:PartName com:idrefs="PN-00007">line filter </uscom:PartName><uscom:PartNumber com:id="PN-00007">222,</uscom:PartNumber><com:Del> an ACI</com:Del><uscom:OCRConfidenceData uscom:ocrConfidenceCode="68"><com:Del>DC</com:Del></uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="20" com:id="p-20" uscom:indentationLevelNumber="L1"><uscom:PartName com:idrefs="PN-00008">converter </uscom:PartName><uscom:PartNumber com:id="PN-00008">242,</uscom:PartNumber><com:Del> an </com:Del><uscom:PartName com:idrefs="PN-00009">energy storage device </uscom:PartName><uscom:PartNumber com:id="PN-00009">244</uscom:PartNumber><com:Del> and an LED </com:Del><uscom:PartName com:idrefs="PN-00010">current supply circuit </uscom:PartName><uscom:PartNumber com:id="PN-00010">246.</uscom:PartNumber></uscom:P><uscom:P com:pNumber="21" com:id="p-21" uscom:indentationLevelNumber="L2">Please <uscom:PartName com:idrefs="PN-00011">amend </uscom:PartName><uscom:PartNumber com:id="PN-00011">0067</uscom:PartNumber> as follows:</uscom:P><uscom:P com:pNumber="22" com:id="p-22" uscom:indentationLevelNumber="L2">The <uscom:PartName com:idrefs="PN-00012">dimming control circuit </uscom:PartName><uscom:PartNumber com:id="PN-00012">322</uscom:PartNumber> includes a <uscom:PartName com:idrefs="PN-00013">microcontroller </uscom:PartName><uscom:PartNumber com:id="PN-00013">336</uscom:PartNumber> and an AC <uscom:PartName com:idrefs="PN-00014">detector </uscom:PartName><uscom:PartNumber com:id="PN-00014">334.</uscom:PartNumber></uscom:P><uscom:P com:pNumber="23" com:id="p-23" uscom:indentationLevelNumber="L1">The LED driver circuit 324 includes an AC <uscom:PartName com:idrefs="PN-00015">filter </uscom:PartName><uscom:PartNumber com:id="PN-00015">344,</uscom:PartNumber> an <uscom:PartName com:idrefs="PN-00016">AC-DC converter </uscom:PartName><uscom:PartNumber com:id="PN-00016">342</uscom:PartNumber> and an LED</uscom:P><uscom:P com:pNumber="24" com:id="p-24" uscom:indentationLevelNumber="L1"><uscom:PartName com:idrefs="PN-00017">current supply circuit </uscom:PartName><uscom:PartNumber com:id="PN-00017">346.</uscom:PartNumber> The AC <uscom:PartName com:idrefs="PN-00018">f<uscom:OCRConfidenceData uscom:ocrConfidenceCode="8688">ilte</uscom:OCRConfidenceData>r </uscom:PartName><uscom:PartNumber com:id="PN-00018">344</uscom:PartNumber> may receive both a switched line voltage input and</uscom:P></uspat:SpecificationDocument>

applicant/14234560.xml

@@ -0,0 +1 @@
+<?xml version="1.0" encoding="utf-8"?><pat:SpecificationDocument xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:pat="urn:us:gov:doc:uspto:patent" xmlns:ent="urn:us:gov:doc:uspto:enterprise" xmlns="urn:us:gov:doc:uspto:patent" xmlns:tbl="http://www.oasis-open.org/tables/exchange/1.0" xmlns:com="http://www.wipo.int/standards/XMLSchema/Common/1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XML_SCHEMAS/V1_3/SpecificationDocument_1_0.xsd" pat:instanceFileName="14234560.01-29-2014.HR11ZUA2PXXIFW3.SPEC.XML" pat:id="HR11ZUA2PXXIFW3"><pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001"><pat:ApplicationHeaderDetails><pat:ApplicationNumber>14234560</pat:ApplicationNumber></pat:ApplicationHeaderDetails><pat:PageTotalQuantity>2</pat:PageTotalQuantity><pat:ParagraphTotalQuantity>7</pat:ParagraphTotalQuantity></pat:DocumentHeaderDetails><pat:MailRoomDate>2014-01-29</pat:MailRoomDate><pat:DocumentCreateDateText>2014-01-29</pat:DocumentCreateDateText><pat:DocumentTitle>SPECIFICATION DOCUMENT</pat:DocumentTitle><pat:Specification><?PageStart number='1'?><pat:P pat:pNumber="1" pat:id="p-1"><pat:OCRConfidenceData pat:levelNumber='8866'>Seri</pat:OCRConfidenceData>al <pat:PartName pat:idref='PN-00001'>No</pat:PartName> <pat:PartNumber pat:id='PN-00001'>14</pat:PartNumber>/234,560 Second Pre<pat:OCRConfidenceData pat:levelNumber='66866'>limin</pat:OCRConfidenceData>ary Amendment </pat:P><pat:Heading pat:id="h-1"><pat:OCRConfidenceData pat:levelNumber='5'>I</pat:OCRConfidenceData>N THE SPECIFICATION</pat:Heading><pat:P pat:pNumber="2" pat:id="p-2">Please amend the <pat:PartName pat:idref='PN-00002'>paragraph [0037] beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00002'>10</pat:PartNumber>, <pat:PartName pat:idref='PN-00003'>line</pat:PartName> <pat:PartNumber pat:id='PN-00003'>21</pat:PartNumber>, as follows. </pat:P><pat:P pat:pNumber="3" pat:id="p-3">[0037] The <pat:PartName pat:idref='PN-00004'>high-voltage electrode</pat:PartName> <pat:PartNumber pat:id='PN-00004'>3</pat:PartNumber> is arranged on the other ma<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> surface of the dielectric 2b. To be more specific, one ma<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> surface of the <pat:PartName pat:idref='PN-00005'>high-voltage electrode [[4]]</pat:PartName> <pat:PartNumber pat:id='PN-00005'><pat:OCRConfidenceData pat:levelNumber='5'>3</pat:OCRConfidenceData></pat:PartNumber> is <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> contact with the other ma<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> surface of the dielectric 2b A conductive material is, for example, applied, pr<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>ted, or vapor-deposited on the other ma<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> surface of the dielectric 2b One ma<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> surface of the <pat:PartName pat:idref='PN-00006'><pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>sulating plate</pat:PartName> <pat:PartNumber pat:id='PN-00006'>4</pat:PartNumber> is in contact with the other ma<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> surface of the <pat:PartName pat:idref='PN-00007'>high-voltage electrode</pat:PartName> <pat:PartNumber pat:id='PN-00007'>3</pat:PartNumber>. The <pat:PartName pat:idref='PN-00008'>high-pressure coo<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>ng plate</pat:PartName> <pat:PartNumber pat:id='PN-00008'>5</pat:PartNumber> is in contact with the other main surface of the <pat:PartName pat:idref='PN-00009'><pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>sulat<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g plate</pat:PartName> <pat:PartNumber pat:id='PN-00009'>4</pat:PartNumber>. This specification illustrates one example that adopts a stack configuration including the <pat:PartName pat:idref='PN-00010'><pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>sulating plate</pat:PartName> <pat:PartNumber pat:id='PN-00010'>4</pat:PartNumber> and the <pat:PartName pat:idref='PN-00011'>high-pressure cooling plate</pat:PartName> <pat:PartNumber pat:id='PN-00011'>5</pat:PartNumber>, but, needless to say, a stack configuration not includ<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g the <pat:PartName pat:idref='PN-00012'><pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>sulating plate</pat:PartName> <pat:PartNumber pat:id='PN-00012'>4</pat:PartNumber> and the <pat:PartName pat:idref='PN-00013'>high-pressure cooling plate</pat:PartName> <pat:PartNumber pat:id='PN-00013'>5</pat:PartNumber> is also adoptable. </pat:P><pat:P pat:pNumber="4" pat:id="p-4">Please amend the <pat:PartName pat:idref='PN-00014'>paragraph [0063] begin<pat:OCRConfidenceData pat:levelNumber='66'>ni</pat:OCRConfidenceData>ng at page</pat:PartName> <pat:PartNumber pat:id='PN-00014'>17</pat:PartNumber>, <pat:PartName pat:idref='PN-00015'><pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>ne</pat:PartName> <pat:PartNumber pat:id='PN-00015'>22</pat:PartNumber>, as follows [0063] The passage through which the above-described cooling medium (the liquid whose temperature has been adjusted) passes and the <pat:PartName pat:idref='PN-00016'>pipe passage [[76]]</pat:PartName> <pat:PartNumber pat:id='PN-00016'><pat:OCRConfidenceData pat:levelNumber='55'>75</pat:OCRConfidenceData></pat:PartNumber> are separate and different paths. </pat:P><pat:P pat:pNumber="5" pat:id="p-5">Please amend the <pat:PartName pat:idref='PN-00017'>paragraph [0144] beg<pat:OCRConfidenceData pat:levelNumber='68868'>innin</pat:OCRConfidenceData>g at page</pat:PartName> <pat:PartNumber pat:id='PN-00017'>37</pat:PartNumber>, <pat:PartName pat:idref='PN-00018'>line</pat:PartName> <pat:PartNumber pat:id='PN-00018'>4</pat:PartNumber>, as follows <pat:OCRConfidenceData pat:levelNumber='88'>[0</pat:OCRConfidenceData>144] The <pat:PartName pat:idref='PN-00019'>precursor supply part</pat:PartName> <pat:PartNumber pat:id='PN-00019'>201</pat:PartNumber> supp<pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>es the activated gas to the hollow portion 21A of the <pat:PartName pat:idref='PN-00020'>insulat<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g tube</pat:PartName> <pat:PartNumber pat:id='PN-00020'>21</pat:PartNumber>. Thereby, the dissociation of the metal precursor gas <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>to the metal particles caused in the hollow portion 21A and the chemical reaction between the metal particles resulting from the dissociation and the plasma excitation gas caused in the hollow portion [[21]] 21A, are promoted This can efficiently generate a large amount of functional metal material particle gas which is nitrided, oxidized, or the like, in the hollow portion 21A. </pat:P><pat:P pat:pNumber="6" pat:id="p-6"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>2</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='2'?><pat:PatentImage pat:id='ID-00002' pat:imageContentCategory='Graph' com:orientationCategory='Portrait' pat:imageWrappingStyleCategory='Inline'><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:ImageFileName>14234560.01-29-2014.HR11ZUA2PXXIFW3.SPEC_12204891.1.292.140.832.226.svg</com:ImageFileName><com:HeightMeasure com:measureUnitCode='In'>0.287</com:HeightMeasure><com:WidthMeasure com:measureUnitCode='In'>1.8</com:WidthMeasure><com:ALTText>Graph</com:ALTText><com:ColourModeCategory>Black and white</com:ColourModeCategory></pat:PatentImage></pat:P><pat:P pat:pNumber="7" pat:id="p-7">Please amend the <pat:PartName pat:idref='PN-00021'>paragraph [0148] beginning at page</pat:PartName> <pat:PartNumber pat:id='PN-00021'>38</pat:PartNumber>, <pat:PartName pat:idref='PN-00022'><pat:OCRConfidenceData pat:levelNumber='66'>li</pat:OCRConfidenceData>ne</pat:PartName> <pat:PartNumber pat:id='PN-00022'>5</pat:PartNumber>, as follows [0148] The <pat:PartName pat:idref='PN-00023'>metal catalyst filament</pat:PartName> <pat:PartNumber pat:id='PN-00023'>23</pat:PartNumber> is arranged along a direction in which the hollow portion 21A of the <pat:PartName pat:idref='PN-00024'><pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>sulat<pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData>g tube</pat:PartName> <pat:PartNumber pat:id='PN-00024'>21</pat:PartNumber> extends As shown <pat:OCRConfidenceData pat:levelNumber='66'>in</pat:OCRConfidenceData> FIG <pat:PartName pat:idref='PN-00025'>[[1]]</pat:PartName> <pat:PartNumber pat:id='PN-00025'>4</pat:PartNumber>, the <pat:PartName pat:idref='PN-00026'>metal catalyst filament</pat:PartName> <pat:PartNumber pat:id='PN-00026'>23</pat:PartNumber> is provided so as to extend over the substantially entire region of the hollow portion 21A with respect to the direction in which the electrode cells are stacked. The <pat:PartName pat:idref='PN-00027'>metal catalyst filament</pat:PartName> <pat:PartNumber pat:id='PN-00027'>23</pat:PartNumber> faces openings of all the ejection holes 21x <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>3</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData></pat:P></pat:Specification></pat:SpecificationDocument>

applicant/14523741.xml

@@ -0,0 +1 @@
+<?xml version="1.0" encoding="utf-8"?><pat:SpecificationDocument xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:pat="urn:us:gov:doc:uspto:patent" xmlns:ent="urn:us:gov:doc:uspto:enterprise" xmlns="urn:us:gov:doc:uspto:patent" xmlns:tbl="http://www.oasis-open.org/tables/exchange/1.0" xmlns:com="http://www.wipo.int/standards/XMLSchema/Common/1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XML_SCHEMAS/V1_3/SpecificationDocument_1_0.xsd" pat:instanceFileName="14523741.10-24-2014.I1O5PJJSPXXIFW3.SPEC.XML" pat:id="I1O5PJJSPXXIFW3"><pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001"><pat:ApplicationHeaderDetails><pat:ApplicationNumber>14523741</pat:ApplicationNumber></pat:ApplicationHeaderDetails><pat:PageTotalQuantity>10</pat:PageTotalQuantity><pat:ParagraphTotalQuantity>33</pat:ParagraphTotalQuantity></pat:DocumentHeaderDetails><pat:MailRoomDate>2014-10-24</pat:MailRoomDate><pat:DocumentCreateDateText>2014-10-24</pat:DocumentCreateDateText><pat:DocumentTitle>SPECIFICATION DOCUMENT</pat:DocumentTitle><pat:Specification><?PageStart number='1'?><pat:P pat:pNumber="1" pat:id="p-1"><pat:BoundaryData><pat:HeaderText>BOE<pat:OCRConfidenceData pat:levelNumber='4'>0</pat:OCRConfidenceData>1-316-US-CIP (13-2216-US-NP)</pat:HeaderText></pat:BoundaryData></pat:P><pat:Heading pat:id="h-1">FIRE-RETARDING APPARATUS AND METHODS OF THEIR</pat:Heading><pat:Heading pat:id="h-2">MAN<pat:OCRConfidenceData pat:levelNumber='5'>U</pat:OCRConfidenceData>FAC<pat:OCRConfidenceData pat:levelNumber='8688'>TURE</pat:OCRConfidenceData></pat:Heading><pat:Heading pat:id="h-3">CROSS-REFERENCE T<pat:OCRConfidenceData pat:levelNumber='5'>O</pat:OCRConfidenceData> RELATED APPLICATIONS</pat:Heading><pat:P pat:pNumber="2" pat:id="p-2"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>001<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> This application is a <pat:PartName pat:idref='PN-00001'>continuation-in-part application of US Patent Application Serial #</pat:PartName> <pat:PartNumber pat:id='PN-00001'>14</pat:PartNumber>/021,690 <pat:PartName pat:idref='PN-00002'>filed on</pat:PartName> <pat:PartNumber pat:id='PN-00002'>9</pat:PartNumber>/9/2013 and entitled Fire-Retaining Containers, and is also a <pat:PartName pat:idref='PN-00003'>continuation-in-part application of US Patent Application Serial #</pat:PartName> <pat:PartNumber pat:id='PN-00003'>14</pat:PartNumber>/021,542 <pat:PartName pat:idref='PN-00004'>filed on</pat:PartName> <pat:PartNumber pat:id='PN-00004'>9</pat:PartNumber>/9/2013 and entitled Containers For Fire Containment. </pat:P><pat:Heading pat:id="h-4">FIELD OF THE DISCLOSURE</pat:Heading><pat:P pat:pNumber="3" pat:id="p-3"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>002<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> This disclosure relates to fire-retarding apparatus comprising composites and to their methods of manufacture. </pat:P><pat:Heading pat:id="h-5">BACKGROUND</pat:Heading><pat:P pat:pNumber="4" pat:id="p-4"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>003<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> It is sometimes needed to make apparatus fire-retarding. This is of<pat:OCRConfidenceData pat:levelNumber='5'>t</pat:OCRConfidenceData>en done using heavy metal construction using materials such as Steel, Titanium, Inconel, and other materials. However, use of such materials increases weight and expense. This is an important issue in the aircraf<pat:OCRConfidenceData pat:levelNumber='5'>t</pat:OCRConfidenceData> industry where weight and cost reduction is needed. </pat:P><pat:P pat:pNumber="5" pat:id="p-5"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>004<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='8'>A</pat:OCRConfidenceData> fire-retarding apparatus and method of manufacture is needed to resolve one or more issues of one or more current fire-retarding apparatus or methods of manufacture. </pat:P><pat:Heading pat:id="h-6">SUMMARY</pat:Heading><pat:P pat:pNumber="6" pat:id="p-6"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>005<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> In one embodiment, a fire-retarding apparatus is disclosed. The fire-retarding apparatus includes a composite. The composite includes a face layer attached to a fire-retarding layer. </pat:P><pat:P pat:pNumber="7" pat:id="p-7"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='2'?><pat:BoundaryData><pat:HeaderText>BOE<pat:OCRConfidenceData pat:levelNumber='4'>0</pat:OCRConfidenceData>1-316-US-CIP (13-2216-US-NP)</pat:HeaderText></pat:BoundaryData><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>006<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> In another embodiment, a fire-retarding apparatus is disclosed. The fire- retarding apparatus includes a composite. The composite includes a face layer, a fire- retarding layer, a fire-retarding attachment member or fire-retarding attachment layer attaching the face layer to the fire-retarding layer, and a reinforcing layer attached to the fire-retarding layer or reinforcing material embedded in the fire-retarding layer. </pat:P><pat:P pat:pNumber="8" pat:id="p-8"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>007<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> In still another embodiment, a method of manufacturing a fire-retarding apparatus is disclosed. A fire-retarding layer is attached to a face layer to form a composite. </pat:P><pat:P pat:pNumber="9" pat:id="p-9"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>008<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> The scope of the present disclosure is defined solely by the appended claims and is not affected by the statements within this summary. </pat:P><pat:Heading pat:id="h-7">BRIEF DESCRIPTION OF THE DRAWINGS</pat:Heading><pat:P pat:pNumber="10" pat:id="p-10"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>009<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> The disclosure can be better understood with reference to the following drawings and description. The components in the figures are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the disclosure. </pat:P><pat:P pat:pNumber="11" pat:id="p-11"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0010<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> Figure 1 illustrates a perspective view of a fire-retarding apparatus; </pat:P><pat:P pat:pNumber="12" pat:id="p-12"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0011<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> Figure 2 illustrates a <pat:PartName pat:idref='PN-00005'>cross-section view through line</pat:PartName> <pat:PartNumber pat:id='PN-00005'>2</pat:PartNumber>-2 of the fire-retarding apparatus of Figure 1; </pat:P><pat:P pat:pNumber="13" pat:id="p-13"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0012<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> Figure 3 illustrates another embodiment of a <pat:PartName pat:idref='PN-00006'>cross-section view through line</pat:PartName> <pat:PartNumber pat:id='PN-00006'>2</pat:PartNumber>-2 in the fire-retarding apparatus of Figure 1; </pat:P><pat:P pat:pNumber="14" pat:id="p-14"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0013<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> Figure 4 illustrates still another embodiment of a <pat:PartName pat:idref='PN-00007'>cross-section view through line</pat:PartName> <pat:PartNumber pat:id='PN-00007'>2</pat:PartNumber>-2 in the fire-retarding apparatus of Figure 1; </pat:P><pat:P pat:pNumber="15" pat:id="p-15"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0014<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> Figure 5 illustrates yet another embodiment of a <pat:PartName pat:idref='PN-00008'>cross-section view through line</pat:PartName> <pat:PartNumber pat:id='PN-00008'>2</pat:PartNumber>-2 in the fire-retarding apparatus of Figure 1; and <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>2</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='3'?><pat:BoundaryData><pat:HeaderText>BOE<pat:OCRConfidenceData pat:levelNumber='4'>0</pat:OCRConfidenceData>1-316-US-CIP (13-2216-US-NP)</pat:HeaderText></pat:BoundaryData><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0015<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> Figure 6 is a flowchart illustrating one embodiment of a method of manufacturing a fire-retarding apparatus comprising a composite. </pat:P><pat:Heading pat:id="h-8">DETAILED DESCRIPTION</pat:Heading><pat:P pat:pNumber="16" pat:id="p-16"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0016<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> Figure 1 illustrates a perspective view of a <pat:PartName pat:idref='PN-00009'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00009'>10</pat:PartNumber>. The <pat:PartName pat:idref='PN-00010'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00010'>10</pat:PartNumber> may comprise a portion of an aircraft, a portion of a spacecraf<pat:OCRConfidenceData pat:levelNumber='5'>t</pat:OCRConfidenceData>, a portion of a vehicle, or another type of apparatus for which it is desired to be fire-retarding. For instance, in an aircraf<pat:OCRConfidenceData pat:levelNumber='5'>t</pat:OCRConfidenceData>, the <pat:PartName pat:idref='PN-00011'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00011'>10</pat:PartNumber> may comprise any portion of the aircraf<pat:OCRConfidenceData pat:levelNumber='5'>t</pat:OCRConfidenceData> which needs to be made fire-retarding such as the engine cowling, a nacelle which holds the engine, a cargo compartment, a housing which holds an airplane component, a skin of the aircraft, a fuselage, or another portion of the aircraf<pat:OCRConfidenceData pat:levelNumber='5'>t</pat:OCRConfidenceData>. In other embodiments, the <pat:PartName pat:idref='PN-00012'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00012'>10</pat:PartNumber> may further vary. The <pat:PartName pat:idref='PN-00013'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00013'>10</pat:PartNumber> <pat:PartName pat:idref='PN-00014'>may weigh less than</pat:PartName> <pat:PartNumber pat:id='PN-00014'>100</pat:PartNumber> pounds per square foot, and may have a thickness t (shown in Figure <pat:PartName pat:idref='PN-00015'>2) of less than</pat:PartName> <pat:PartNumber pat:id='PN-00015'>3</pat:PartNumber> feet. In other embodiments, the <pat:PartName pat:idref='PN-00016'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00016'>10</pat:PartNumber> <pat:PartName pat:idref='PN-00017'>may weigh less than</pat:PartName> <pat:PartNumber pat:id='PN-00017'>1</pat:PartNumber> pound per square foot, and may have a thickness t (shown in Figure <pat:PartName pat:idref='PN-00018'>2) of less than</pat:PartName> <pat:PartNumber pat:id='PN-00018'>8</pat:PartNumber> inches. In still other embodiments, the weight and thickness of the <pat:PartName pat:idref='PN-00019'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00019'>10</pat:PartNumber> may vary further. </pat:P><pat:P pat:pNumber="17" pat:id="p-17"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0017<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> Figure 2 illustrates a <pat:PartName pat:idref='PN-00020'>cross-section view through line</pat:PartName> <pat:PartNumber pat:id='PN-00020'>2</pat:PartNumber>-2 of the <pat:PartName pat:idref='PN-00021'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00021'>10</pat:PartNumber> of Figure 1. The <pat:PartName pat:idref='PN-00022'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00022'>10</pat:PartNumber> may comprise a <pat:PartName pat:idref='PN-00023'>composite</pat:PartName> <pat:PartNumber pat:id='PN-00023'>12</pat:PartNumber>. The <pat:PartName pat:idref='PN-00024'>composite</pat:PartName> <pat:PartNumber pat:id='PN-00024'>12</pat:PartNumber> may comprise the following attached layers: <pat:PartName pat:idref='PN-00025'>face layer</pat:PartName> <pat:PartNumber pat:id='PN-00025'>14</pat:PartNumber>; <pat:PartName pat:idref='PN-00026'>fire- retarding attachment layer</pat:PartName> <pat:PartNumber pat:id='PN-00026'>16</pat:PartNumber>; <pat:PartName pat:idref='PN-00027'>reinforcing layer</pat:PartName> <pat:PartNumber pat:id='PN-00027'>18</pat:PartNumber>; fire-retarding attachment layer 16a; <pat:PartName pat:idref='PN-00028'>fluid-repelling layer</pat:PartName> <pat:PartNumber pat:id='PN-00028'>20</pat:PartNumber>; <pat:PartName pat:idref='PN-00029'>fire-retarding layer</pat:PartName> <pat:PartNumber pat:id='PN-00029'>22</pat:PartNumber>; fluid-repelling layer 20a; fire- retarding attachment layer 16b; reinforcing layer 18a; fire-retarding attachment layer <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>3</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='4'?><pat:BoundaryData><pat:HeaderText>BOE<pat:OCRConfidenceData pat:levelNumber='4'>0</pat:OCRConfidenceData>1-316-US-CIP (13-2216-US-NP)</pat:HeaderText></pat:BoundaryData>16c; and face layer 14a. In other embodiments, any of the layers may vary in order or number, one or more of the layers may not be present, or one or more additional layers may be used. In still other embodiments, the <pat:PartName pat:idref='PN-00030'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00030'>10</pat:PartNumber> may consist of any combination of the layers including all of the layers or taking away one or more of the layers. </pat:P><pat:P pat:pNumber="18" pat:id="p-18"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0018<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> The <pat:PartName pat:idref='PN-00031'>face layers</pat:PartName> <pat:PartNumber pat:id='PN-00031'>14</pat:PartNumber> and 14a may comprise non-fire-retarding layers. The face layers may comprise sheets of aluminum, composite, metal, non-metallic, polyimide, fluid repelling, or another type of material<pat:OCRConfidenceData pat:levelNumber='5'>.</pat:OCRConfidenceData> In other embodiments, the <pat:PartName pat:idref='PN-00032'>face layers</pat:PartName> <pat:PartNumber pat:id='PN-00032'>14</pat:PartNumber> and 14a may be made of any type of non-fire-retarding or fire-retarding material. </pat:P><pat:P pat:pNumber="19" pat:id="p-19"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0019<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> The <pat:PartName pat:idref='PN-00033'>fire-retarding attachment layers</pat:PartName> <pat:PartNumber pat:id='PN-00033'>16</pat:PartNumber>, 16a, 16b, and 16c may be used to adhere the layers disposed on opposite sides of them together, using a material which is fire-retarding. For purposes of this disclosure, the term "fire-retarding" means that the layer or member is made of a material which retards fire, or which doesn't ignite or contains the fire, which prevents the fire from spreading or penetrating through, and which either suppresses the fire or extinguishes it through containment and/or lack of oxygen. The <pat:PartName pat:idref='PN-00034'>fire-retarding attachment layers</pat:PartName> <pat:PartNumber pat:id='PN-00034'>16</pat:PartNumber>, 16a, 16b, and 16c may comprise an adhesive, paste, solid, or another adhering material which is fire- retarding. The <pat:PartName pat:idref='PN-00035'>fire-retarding attachment layers</pat:PartName> <pat:PartNumber pat:id='PN-00035'>16</pat:PartNumber>, 16a, 16b, and 16c may be made of ceramic, metal, non-metallic, composite, Aramid, aerogel, or polyimide. In other embodiments, the <pat:PartName pat:idref='PN-00036'>fire-retarding attachment layers</pat:PartName> <pat:PartNumber pat:id='PN-00036'>16</pat:PartNumber>, 16a, 16b, and 16c may be made of varying materials which both adhere the layers disposed on opposite sides of them together, and are fire-retarding having fire retarding properties equivalent to <pat:PartName pat:idref='PN-00037'>Underwriter Laboratories (UL) Rating of UL</pat:PartName>-<pat:PartNumber pat:id='PN-00037'>94</pat:PartNumber> <pat:PartName pat:idref='PN-00038'>V</pat:PartName>-<pat:PartNumber pat:id='PN-00038'>0</pat:PartNumber> (does not burn) with an o<pat:PartName pat:idref='PN-00039'>perating temperature range of </pat:PartName>-<pat:PartNumber pat:id='PN-00039'>452</pat:PartNumber> degrees F to 3,600 degrees F. In additional <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>4</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='5'?><pat:BoundaryData><pat:HeaderText>BOE<pat:OCRConfidenceData pat:levelNumber='4'>0</pat:OCRConfidenceData>1-316-US-CIP (13-2216-US-NP)</pat:HeaderText></pat:BoundaryData>embodiments, the <pat:PartName pat:idref='PN-00040'>fire-retarding attachment layers</pat:PartName> <pat:PartNumber pat:id='PN-00040'>16</pat:PartNumber>, 16a, 16b, and 16c may survive a <pat:PartName pat:idref='PN-00041'>fire of</pat:PartName> <pat:PartNumber pat:id='PN-00041'>2</pat:PartNumber>,000 <pat:PartName pat:idref='PN-00042'>degrees Fahrenheit minimum for</pat:PartName> <pat:PartNumber pat:id='PN-00042'>15</pat:PartNumber> minutes without burning through and without burning the back or front sides. In still other embodiments, the <pat:PartName pat:idref='PN-00043'>fire- retarding attachment layers</pat:PartName> <pat:PartNumber pat:id='PN-00043'>16</pat:PartNumber>, 16a, 16b, and 16c may vary further. In one embodiment, the <pat:PartName pat:idref='PN-00044'>fire-retarding attachment layers</pat:PartName> <pat:PartNumber pat:id='PN-00044'>16</pat:PartNumber>, 16a, 16b, and 16c may comprise one or more fire-retarding attachment members which are used to attach layers. The fire-retarding attachment members may comprise fire-retarding fasteners, fire- retarding clamps, fire-retarding securement members, or other types of fire-retarding attachment members. In other embodiments, any of the layers of the <pat:PartName pat:idref='PN-00045'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00045'>10</pat:PartNumber> may be attached to one another through/using pressing, adhesives, tape, threads, screws, bolts, fasteners, rivets, staples, clamps, other mechanical members, or other attachment mechanisms. </pat:P><pat:P pat:pNumber="20" pat:id="p-20"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0020<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> The <pat:PartName pat:idref='PN-00046'>reinforcing layers</pat:PartName> <pat:PartNumber pat:id='PN-00046'>18</pat:PartNumber> and 18a provide reinforcement and strength to the <pat:PartName pat:idref='PN-00047'>fire-retarding layer</pat:PartName> <pat:PartNumber pat:id='PN-00047'>22</pat:PartNumber> to reduce the likelihood of the <pat:PartName pat:idref='PN-00048'>fire-retarding layer</pat:PartName> <pat:PartNumber pat:id='PN-00048'>22</pat:PartNumber> tearing or disintegrating. The <pat:PartName pat:idref='PN-00049'>reinforcing layers</pat:PartName> <pat:PartNumber pat:id='PN-00049'>18</pat:PartNumber> and 18a may be made of metal, non- metallic, ceramic, glass, composite, rubber, foam, Aramid, solid, fibrous material, or porous material<pat:OCRConfidenceData pat:levelNumber='5'>.</pat:OCRConfidenceData> In other embodiments, the <pat:PartName pat:idref='PN-00050'>reinforcing layers</pat:PartName> <pat:PartNumber pat:id='PN-00050'>18</pat:PartNumber> and 18a may be made of varying materials. In one embodiment, the <pat:PartName pat:idref='PN-00051'>reinforcing layers</pat:PartName> <pat:PartNumber pat:id='PN-00051'>18</pat:PartNumber> and 18a have a <pat:PartName pat:idref='PN-00052'>fiber density of</pat:PartName> <pat:PartNumber pat:id='PN-00052'>1.0</pat:PartNumber> to 5 gm<pat:OCRConfidenceData pat:levelNumber='5'>/</pat:OCRConfidenceData>cm3, a <pat:PartName pat:idref='PN-00053'>fiber diameter of</pat:PartName> <pat:PartNumber pat:id='PN-00053'>3</pat:PartNumber> to 20 micron (um), and a <pat:PartName pat:idref='PN-00054'>fiber tensile strength of</pat:PartName> <pat:PartNumber pat:id='PN-00054'>1.0</pat:PartNumber> to 6.0 Gpa (Gigapascal) to provide strength. In other embodiments, the <pat:PartName pat:idref='PN-00055'>reinforcing layers</pat:PartName> <pat:PartNumber pat:id='PN-00055'>18</pat:PartNumber> and 18a may be made of varying materials which provide strength and reinforcement. In other embodiments, instead of using separate reinforcing layers, reinforcing material may be embedded into the <pat:PartName pat:idref='PN-00056'>fire- retarding layer</pat:PartName> <pat:PartNumber pat:id='PN-00056'>22</pat:PartNumber> to provide reinforcement and strength to the <pat:PartName pat:idref='PN-00057'>fire-retarding layer</pat:PartName> <pat:PartNumber pat:id='PN-00057'>22</pat:PartNumber>. </pat:P><pat:P pat:pNumber="21" pat:id="p-21"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>5</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='6'?><pat:BoundaryData><pat:HeaderText>BOE<pat:OCRConfidenceData pat:levelNumber='4'>0</pat:OCRConfidenceData>1-316-US-CIP (13-2216-US-NP)</pat:HeaderText></pat:BoundaryData>The reinforcing material may comprise metal, non-metallic, ceramic, glass, composite, foam, rubber, or Aramid. In other embodiments, the reinforcing material may vary. Throughout this disclosure, any time the term "reinforcing" is used or a reference is made to reinforcement properties, the disclosure of this paragraph applies to the term. </pat:P><pat:P pat:pNumber="22" pat:id="p-22"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0021<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> The <pat:PartName pat:idref='PN-00058'>fluid-repelling layers</pat:PartName> <pat:PartNumber pat:id='PN-00058'>20</pat:PartNumber> and 20a may provide fluid-repelling properties to reduce the likelihood of degradation of the <pat:PartName pat:idref='PN-00059'>fire-retarding layer</pat:PartName> <pat:PartNumber pat:id='PN-00059'>22</pat:PartNumber> and prevent fluid absorption. For purposes of this disclosure, the term "fluid-repelling" is defined as preventing fluid from being absorbed by the base material. The <pat:PartName pat:idref='PN-00060'>fluid-repelling layers</pat:PartName> <pat:PartNumber pat:id='PN-00060'>20</pat:PartNumber> and 20a may comprise silicone, a nano-coating, or another type of fluid-repelling material, coating, or spray. In one embodiment, the <pat:PartName pat:idref='PN-00061'>fluid-repelling layers</pat:PartName> <pat:PartNumber pat:id='PN-00061'>20</pat:PartNumber> and 20a have a fluid repellency requirement to fluid proof test equivalent to or <pat:PartName pat:idref='PN-00062'>better than ASTM D</pat:PartName>-<pat:PartNumber pat:id='PN-00062'>3393</pat:PartNumber> (2009). In other embodiments, the <pat:PartName pat:idref='PN-00063'>fluid-repelling layers</pat:PartName> <pat:PartNumber pat:id='PN-00063'>20</pat:PartNumber> and 2a may have varying fluid repellency. Throughout this disclosure, any time the term "fluid-repelling" is used or a reference is made to fluid-repelling properties, the disclosure of this paragraph applies to the term. </pat:P><pat:P pat:pNumber="23" pat:id="p-23"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0022<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> The <pat:PartName pat:idref='PN-00064'>fire-retarding layer</pat:PartName> <pat:PartNumber pat:id='PN-00064'>22</pat:PartNumber> comprises a material which retards fire, which doesn't ignite and contains the fire, which prevents the fire from spreading or burning through, and which either suppresses the fire or extinguishes it through containment and/or lack of oxygen. The <pat:PartName pat:idref='PN-00065'>fire-retarding layer</pat:PartName> <pat:PartNumber pat:id='PN-00065'>22</pat:PartNumber> may be made of metal, non- metallic, composite, ceramic, aerogel (organic and inorganic), xerogel (organic and inorganic), polyimide, (4, 4-Oxydiphenylene-Pyromellitmide), mineral wool, ceramic paste, ceramic coating, or an inorganic material. In other embodiments, the <pat:PartName pat:idref='PN-00066'>fire- retarding layer</pat:PartName> <pat:PartNumber pat:id='PN-00066'>22</pat:PartNumber> may be made of varying materials, such as a high-temperature paste <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>6</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='7'?><pat:BoundaryData><pat:HeaderText>BOE<pat:OCRConfidenceData pat:levelNumber='4'>0</pat:OCRConfidenceData>1-316-US-CIP (13-2216-US-NP)</pat:HeaderText></pat:BoundaryData>which is applied and cured, which have fire retarding properties equivalent to <pat:PartName pat:idref='PN-00067'>Underwriter Laboratories (UL) Rating of UL</pat:PartName>-<pat:PartNumber pat:id='PN-00067'>94</pat:PartNumber> <pat:PartName pat:idref='PN-00068'>V</pat:PartName>-<pat:PartNumber pat:id='PN-00068'><pat:OCRConfidenceData pat:levelNumber='5'>0</pat:OCRConfidenceData></pat:PartNumber> (does not burn) and an o<pat:PartName pat:idref='PN-00069'>perating temperature range between </pat:PartName>-<pat:PartNumber pat:id='PN-00069'>100</pat:PartNumber> degrees F to 3,600 degrees F. In additional embodiments, the <pat:PartName pat:idref='PN-00070'>fire-retarding layer</pat:PartName> <pat:PartNumber pat:id='PN-00070'>22</pat:PartNumber> may survive a <pat:PartName pat:idref='PN-00071'>fire of</pat:PartName> <pat:PartNumber pat:id='PN-00071'>2</pat:PartNumber>,000 <pat:PartName pat:idref='PN-00072'>degrees Fahrenheit minimum for</pat:PartName> <pat:PartNumber pat:id='PN-00072'>15</pat:PartNumber> minutes without burning through and without burning the back or front sides. In still other embodiments, the <pat:PartName pat:idref='PN-00073'>fire-retarding attachment layer</pat:PartName> <pat:PartNumber pat:id='PN-00073'>22</pat:PartNumber> may vary further. </pat:P><pat:P pat:pNumber="24" pat:id="p-24"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0023<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> Figure 3 illustrates another embodiment of a <pat:PartName pat:idref='PN-00074'>cross-section view through line</pat:PartName> <pat:PartNumber pat:id='PN-00074'>2</pat:PartNumber>-2 in the <pat:PartName pat:idref='PN-00075'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00075'>10</pat:PartNumber> of Figure 1. As shown, in this embodiment the <pat:PartName pat:idref='PN-00076'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00076'>10</pat:PartNumber> comprises a <pat:PartName pat:idref='PN-00077'>composite</pat:PartName> <pat:PartNumber pat:id='PN-00077'>12</pat:PartNumber> which includes the following attached layers: <pat:PartName pat:idref='PN-00078'>face layer</pat:PartName> <pat:PartNumber pat:id='PN-00078'>14</pat:PartNumber>; <pat:PartName pat:idref='PN-00079'>fire-retarding attachment layer</pat:PartName> <pat:PartNumber pat:id='PN-00079'>16</pat:PartNumber>; <pat:PartName pat:idref='PN-00080'>fire-retarding layer</pat:PartName> <pat:PartNumber pat:id='PN-00080'>22</pat:PartNumber>; fire-retarding attachment layer 16c; and face layer 14a. <pat:PartName pat:idref='PN-00081'>Reinforcing layer</pat:PartName> <pat:PartNumber pat:id='PN-00081'>18</pat:PartNumber>, fire- retarding attachment layer 16a, <pat:PartName pat:idref='PN-00082'>fluid-repelling layer</pat:PartName> <pat:PartNumber pat:id='PN-00082'>20</pat:PartNumber>, fluid-repelling layer 20a, fire- retarding attachment layer 16b, and reinforcing layer 18a have been eliminated from the cross-sectional embodiment of Figure 2. In other embodiments, any of the layers may vary in order or number, one or more of the layers may not be present, or one or more additional layers may be used. In still other embodiments, the <pat:PartName pat:idref='PN-00083'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00083'>10</pat:PartNumber> may consist of any combination of the layers including all of the layers or taking away one or more of the layers. </pat:P><pat:P pat:pNumber="25" pat:id="p-25"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0024<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> Figure 4 illustrates still another embodiment of a <pat:PartName pat:idref='PN-00084'>cross-section view through line</pat:PartName> <pat:PartNumber pat:id='PN-00084'>2</pat:PartNumber>-2 in the <pat:PartName pat:idref='PN-00085'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00085'>10</pat:PartNumber> of Figure 1. As shown, in this embodiment the <pat:PartName pat:idref='PN-00086'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00086'>10</pat:PartNumber> comprises a <pat:PartName pat:idref='PN-00087'>composite</pat:PartName> <pat:PartNumber pat:id='PN-00087'>12</pat:PartNumber> which includes the following attached layers: <pat:PartName pat:idref='PN-00088'>fluid-repelling layer</pat:PartName> <pat:PartNumber pat:id='PN-00088'>20</pat:PartNumber>; <pat:PartName pat:idref='PN-00089'>fire-retarding layer</pat:PartName> <pat:PartNumber pat:id='PN-00089'>22</pat:PartNumber>; fluid- repelling layer 20a; fire-retarding attachment layer 16c; and face layer 14a. Face <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>7</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='8'?><pat:BoundaryData><pat:HeaderText>BOE<pat:OCRConfidenceData pat:levelNumber='4'>0</pat:OCRConfidenceData>1-316-US-CIP (13-2216-US-NP)</pat:HeaderText></pat:BoundaryData>layer 14, <pat:PartName pat:idref='PN-00090'>fire-retarding attachment layer</pat:PartName> <pat:PartNumber pat:id='PN-00090'>16</pat:PartNumber>, <pat:PartName pat:idref='PN-00091'>reinforcing layer</pat:PartName> <pat:PartNumber pat:id='PN-00091'>18</pat:PartNumber>, fire-retarding attachment layer 16a, fire-retarding attachment layer 16b, and reinforcing layer 1<pat:OCRConfidenceData pat:levelNumber='88'>8a</pat:OCRConfidenceData> have been eliminated from the cross-sectional embodiment of Figure 2. In other embodiments, any of the layers may vary in order or number, one or more of the layers may not be present, or one or more additional layers may be used. In still other embodiments, the <pat:PartName pat:idref='PN-00092'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00092'>10</pat:PartNumber> may consist of any combination of the layers including all of the layers or taking away one or more of the layers. </pat:P><pat:P pat:pNumber="26" pat:id="p-26"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0025<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> Figure 5 illustrates yet another embodiment of a <pat:PartName pat:idref='PN-00093'>cross-section view through line</pat:PartName> <pat:PartNumber pat:id='PN-00093'>2</pat:PartNumber>-2 in the <pat:PartName pat:idref='PN-00094'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00094'>10</pat:PartNumber> of Figure 1. As shown, in this embodiment the <pat:PartName pat:idref='PN-00095'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00095'>10</pat:PartNumber> comprises a <pat:PartName pat:idref='PN-00096'>composite</pat:PartName> <pat:PartNumber pat:id='PN-00096'>12</pat:PartNumber> which includes the following attached layers: <pat:PartName pat:idref='PN-00097'>fire-retarding layer</pat:PartName> <pat:PartNumber pat:id='PN-00097'>22</pat:PartNumber>; and face layer 14a. <pat:PartName pat:idref='PN-00098'>Face layer</pat:PartName> <pat:PartNumber pat:id='PN-00098'>14</pat:PartNumber>, <pat:PartName pat:idref='PN-00099'>fire-retarding attachment layer</pat:PartName> <pat:PartNumber pat:id='PN-00099'>16</pat:PartNumber>, <pat:PartName pat:idref='PN-00100'>reinforcing layer</pat:PartName> <pat:PartNumber pat:id='PN-00100'>18</pat:PartNumber>, fire-retarding attachment layer 16a, <pat:PartName pat:idref='PN-00101'>fluid-repelling layer</pat:PartName> <pat:PartNumber pat:id='PN-00101'>20</pat:PartNumber>, fluid-repelling layer 20a, fire-retarding attachment layer 16b, reinforcing layer 18a, and fire-retarding attachment layer 16c have been eliminated from the cross-sectional embodiment of Figure 2. In other embodiments, any of the layers may vary in order or number, one or more of the layers may not be present, or one or more additional layers may be used. In still other embodiments, the <pat:PartName pat:idref='PN-00102'>fire-retarding apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00102'>10</pat:PartNumber> may consist of any combination of the layers including all of the layers or taking away one or more of the layers. </pat:P><pat:P pat:pNumber="27" pat:id="p-27"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0026<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> Figure 6 is a flowchart illustrating one embodiment of a <pat:PartName pat:idref='PN-00103'>method</pat:PartName> <pat:PartNumber pat:id='PN-00103'>30</pat:PartNumber> of manufacturing a fire-retarding apparatus comprising a composite. The method may be varied to manufacture any of the embodiments of the fire-retarding apparatus disclosed herein, or varied further to manufacturing varying fire-retarding apparatus having a varying combination of layers. <pat:PartName pat:idref='PN-00104'>In step</pat:PartName> <pat:PartNumber pat:id='PN-00104'>32</pat:PartNumber>, fluid-repelling layers may be <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>8</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='9'?><pat:BoundaryData><pat:HeaderText>BOE<pat:OCRConfidenceData pat:levelNumber='4'>0</pat:OCRConfidenceData>1-316-US-CIP (13-2216-US-NP)</pat:HeaderText></pat:BoundaryData>attached to opposed sides of a fire-retarding layer. <pat:PartName pat:idref='PN-00105'>In step</pat:PartName> <pat:PartNumber pat:id='PN-00105'>34</pat:PartNumber>, fire-retarding attachment layers may be used to attach reinforcing layers to the fluid-repelling layers attached to the opposed sides of the fire-retarding layer. In other embodiments, any of the layers may be attached to one another through<pat:OCRConfidenceData pat:levelNumber='5'>/</pat:OCRConfidenceData>using pressing, adhesives, tape, threads, screws, bolts, fasteners, rivets, staples, clamps, other mechanical members, or other attachment mechanisms. In still other embodiments, rather than attaching fire- retarding attachment layers, a reinforcing material may be embedded within the fire- retarding layer. <pat:PartName pat:idref='PN-00106'>In step</pat:PartName> <pat:PartNumber pat:id='PN-00106'>36</pat:PartNumber>, additional fire-retarding attachment layers may be used to attach face layers to the reinforcing layers. Optionally, fluid-repelling layers may be attached to the face layers. </pat:P><pat:P pat:pNumber="28" pat:id="p-28"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0027<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> In other embodiments, one or more steps of the <pat:PartName pat:idref='PN-00107'>method</pat:PartName> <pat:PartNumber pat:id='PN-00107'>30</pat:PartNumber> may be varied in substance or in order, one or more steps of the <pat:PartName pat:idref='PN-00108'>method</pat:PartName> <pat:PartNumber pat:id='PN-00108'>30</pat:PartNumber> may not be followed, or one or more additional steps may be added to the <pat:PartName pat:idref='PN-00109'>method</pat:PartName> <pat:PartNumber pat:id='PN-00109'>30</pat:PartNumber>. In still other embodiments, the <pat:PartName pat:idref='PN-00110'>method</pat:PartName> <pat:PartNumber pat:id='PN-00110'>30</pat:PartNumber> may be used to manufacture a fire-retarding apparatus having any of the layers varied in order or number, having one or more of the layers not being present, or having one or more additional layers. In additional embodiments, the <pat:PartName pat:idref='PN-00111'>method</pat:PartName> <pat:PartNumber pat:id='PN-00111'>30</pat:PartNumber> may be used to manufacture a fire-retarding apparatus consisting of any combination of the layers including all of the layers or taking away one or more of the layers. </pat:P><pat:P pat:pNumber="29" pat:id="p-29"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0028<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> One or more embodiments of the disclosure may allow for composite apparatus to be made fire-retarding while keeping the fire-retarding composite apparatus low-weight. This is a significant advantage in the airline industry where low weight leads to greater fuel efficiency thereby saving cost. </pat:P><pat:P pat:pNumber="30" pat:id="p-30"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0029<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> The Abstract is provided to allow the reader to quickly ascertain the nature of <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>9</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='10'?><pat:BoundaryData><pat:HeaderText>BOE<pat:OCRConfidenceData pat:levelNumber='4'>0</pat:OCRConfidenceData>1-316-US-CIP (13-2216-US-NP)</pat:HeaderText></pat:BoundaryData>the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in various embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter. </pat:P><pat:P pat:pNumber="31" pat:id="p-31"><pat:OCRConfidenceData pat:levelNumber='5'>[</pat:OCRConfidenceData>0030<pat:OCRConfidenceData pat:levelNumber='5'>]</pat:OCRConfidenceData> While particular aspects of the present subject matter described herein have been shown and described, it will be apparent to those skilled in the art that, based upon the teachings herein, changes and modifications may be made without departing from the subject matter described herein and its broader aspects and, therefore, the appended claims are to encompass within their scope all such changes and modifications as are within the true scope of the subject matter described herein. </pat:P><pat:P pat:pNumber="32" pat:id="p-32">Furthermore, it is to be understood that the disclosure is defined by the appended claims. Accordingly, the disclosure is not to be restricted except in light of the appended claims and their equivalents. </pat:P><pat:P pat:pNumber="33" pat:id="p-33"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>10</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData></pat:P></pat:Specification></pat:SpecificationDocument>

applicant/14548870.xml

@@ -0,0 +1 @@
+<?xml version="1.0" encoding="utf-8"?><pat:SpecificationDocument xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:pat="urn:us:gov:doc:uspto:patent" xmlns:ent="urn:us:gov:doc:uspto:enterprise" xmlns="urn:us:gov:doc:uspto:patent" xmlns:tbl="http://www.oasis-open.org/tables/exchange/1.0" xmlns:com="http://www.wipo.int/standards/XMLSchema/Common/1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XML_SCHEMAS/V1_3/SpecificationDocument_1_0.xsd" pat:instanceFileName="14548870.11-20-2014.I2QKKCWNPXXIFW3.SPEC.XML" pat:id="I2QKKCWNPXXIFW3"><pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001"><pat:ApplicationHeaderDetails><pat:ApplicationNumber>14548870</pat:ApplicationNumber></pat:ApplicationHeaderDetails><pat:PageTotalQuantity>21</pat:PageTotalQuantity><pat:ParagraphTotalQuantity>88</pat:ParagraphTotalQuantity></pat:DocumentHeaderDetails><pat:MailRoomDate>2014-11-20</pat:MailRoomDate><pat:DocumentCreateDateText>2014-11-20</pat:DocumentCreateDateText><pat:DocumentTitle>SPECIFICATION DOCUMENT</pat:DocumentTitle><pat:Specification><?PageStart number='1'?><pat:P pat:pNumber="1" pat:id="p-1"><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData></pat:P><pat:Heading pat:id="h-1">WEAR PROGNOSIS METHOD AND MAINTENANCE METHOD</pat:Heading><pat:Heading pat:id="h-2">BACKGROUND OF THE INVENTION</pat:Heading><pat:P pat:pNumber="2" pat:id="p-2">[0001] In the context of road reconstruction by milling, and the removal of mineral deposits with a surface miner (also by milling), the earth working tools that are used, and in particular the milling bits, are subject to a continuous wear process. Replacement is advisable once the tools reach a specific wear state, since otherwise the ongoing process loses efficiency. A distinction must be made here among a variety of wear states that result in replacement of a milling bit or bit holder: </pat:P><pat:P pat:pNumber="3" pat:id="p-3">1.    Bit replacement because sufficient wear material (in particular carbide metal at the tip) is no longer present. The penetration resistance becomes too high and the efficiency thus decreases (too much frictional loss); the wear is predominantly rotationally symmetrical. </pat:P><pat:P pat:pNumber="4" pat:id="p-4">2.    Bit holder replacement because the wear limit has been reached (wear occurs on the holder at the contact surface between bit and holder). This wear is usually symmetrical. </pat:P><pat:P pat:pNumber="5" pat:id="p-5">3.    Rotationally asymmetrical wear on the bit tip and/or bit head due to insufficient rotational movement of the bit during the milling process. The consequences are a poor milling pattern as well as the risk of tool breakage, since the bracing effect of the bit head is lost. </pat:P><pat:P pat:pNumber="6" pat:id="p-6">4.    The bit holder can furthermore be subject to additional rotationally asymmetrical wear. </pat:P><pat:P pat:pNumber="7" pat:id="p-7">5.    Bit breakage. </pat:P><pat:P pat:pNumber="8" pat:id="p-8">[0002] In addition, worn and/or broken bits can result in secondary damage to the bit holders, and worn bit holders can cause secondary damage to the milling drum. Timely replacement of the bit and/or bit holder is therefore necessary and reduces costs. If the bits and/or bit holders are changed too soon, however, this procedure is likewise not optimum in <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='7'>1</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='2'?><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData>terms of cost, since the bits and bit holders are consumable parts and therefore very cost- intensive. Wear potential that is still available is then not being correctly utilized. The wear state of bits and bit holders has hitherto been assessed by visual inspection by the machine driver. For this purpose the machine operator must shut off the machine (switch off engine and decouple drum from the drive train). He must then open the rear drum hatch so the milling drum can be visually inspected. </pat:P><pat:P pat:pNumber="9" pat:id="p-9">[0003] The milling drum is then rotated by means of a second drive system so that the entire milling drum can be inspected. The drum inspection task can also be handled by a second operator. The wear state of the bit holders is usually assessed by way of so-called <pat:OCRConfidenceData pat:levelNumber='5'>"</pat:OCRConfidenceData>wear markings.<pat:OCRConfidenceData pat:levelNumber='5'>"</pat:OCRConfidenceData> The wear state of the bits can be determined by way of the longitudinal wear and the rotational symmetry of the wear pattern. </pat:P><pat:P pat:pNumber="10" pat:id="p-10">[0004] Monitoring the wear state of bits and holders is very time-intensive, and is unproductive since nothing can be produced during that time. The overall process is disrupted and availability is thus additionally decreased. In addition, because of the highly subjective nature of the assessment, the risk exists that the wear potential of holders and bits will not be optimally utilized. </pat:P><pat:P pat:pNumber="11" pat:id="p-11">[0005] <pat:PartName pat:idref='PN-00001'>DE</pat:PartName> <pat:PartNumber pat:id='PN-00001'>102</pat:PartNumber> 03 732 <pat:PartName pat:idref='PN-00002'>A<pat:OCRConfidenceData pat:levelNumber='5'>l</pat:OCRConfidenceData> (US</pat:PartName> <pat:PartNumber pat:id='PN-00002'>7422391</pat:PartNumber>) discloses an apparatus in which operation can be optimized by monitoring operating states of machine components that participate directly or indirectly in the milling process. Among other factors, the wear state of the bits is also assessed by evaluating a variety of machine parameters and variables. The problem that exists during operation of the milling machine is that the milling process and the substrate itself, whose properties fluctuate considerably, have a large influence on evaluation of the operating state of components. </pat:P><pat:P pat:pNumber="12" pat:id="p-12"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>2</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='3'?><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData>[0006] <pat:PartName pat:idref='PN-00003'>AT</pat:PartName> <pat:PartNumber pat:id='PN-00003'>382</pat:PartNumber> 683 B discloses a mining machine in which the cutting drum is monitored in noncontact fashion, using photoelectric barriers that detect the presence of the bits. A quantitative wear evaluation is not possible with this method. </pat:P><pat:P pat:pNumber="13" pat:id="p-13">[0007] <pat:PartName pat:idref='PN-00004'>DE</pat:PartName> <pat:PartNumber pat:id='PN-00004'>10</pat:PartNumber> 2008 045 470 <pat:PartName pat:idref='PN-00005'>A<pat:OCRConfidenceData pat:levelNumber='5'>l</pat:OCRConfidenceData> (US</pat:PartName> <pat:PartNumber pat:id='PN-00005'>8386196</pat:PartNumber>) discloses a method for quantitative wear identification. Here the position in space of at least point on the earth working tool is sensed. This measurement result is then compared with a reference value so that the wear on the tool can be sensed quantitatively. </pat:P><pat:P pat:pNumber="14" pat:id="p-14">[0008] As already mentioned above, the material properties of the substrate being processed change during the working process. In mining, for example, it can happen that while traveling over a deposit of material to be removed, the hardness of the raw material suddenly rises <pat:OCRConfidenceData pat:levelNumber='66'>("</pat:OCRConfidenceData>hard spot<pat:OCRConfidenceData pat:levelNumber='5'>"</pat:OCRConfidenceData>). Increased wear then occurs on the tools. </pat:P><pat:P pat:pNumber="15" pat:id="p-15">[0009] In order to avoid damage to the cutting equipment due to unpredictable working conditions, for safety reasons the tools are on occasion switched out too soon. </pat:P><pat:Heading pat:id="h-3">SUMMARY OF THE INVENTION</pat:Heading><pat:P pat:pNumber="16" pat:id="p-16">[0010] An object of the invention is to furnish a method that makes possible an economically optimized working process. </pat:P><pat:P pat:pNumber="17" pat:id="p-17">[0011] This object of the invention is achieved with a method for wear prognosis for an earth working machine, in particular a road milling machine, a surface miner, or the like, the current wear state of at least one earth working tool, in particular of a bit and/or a bit holder, being sensed. This can be effected, for example, using the method according to <pat:PartName pat:idref='PN-00006'>DE</pat:PartName> <pat:PartNumber pat:id='PN-00006'>10</pat:PartNumber> 2008 045 470 <pat:PartName pat:idref='PN-00007'>A<pat:OCRConfidenceData pat:levelNumber='5'>l</pat:OCRConfidenceData> (US</pat:PartName> <pat:PartNumber pat:id='PN-00007'>8386196</pat:PartNumber>) described above. From the interim result thereby obtained, according to the invention the residual wear capacity until a predefined wear limit is reached is then ascertained in a further method step. A wear state at which the earth working tool <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>3</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='4'?><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData>must be replaced is consequently defined. By incorporating local conditions, for example, it is then possible, for example, to ascertain the specific remaining service life of the earth working tool. This yields an optimized working process. In particular, the machine operator can now be given specific information that provides him with data regarding the residual wear capacity of the earth working tool. The result is to prevent timely changing of the earth working tool from being neglected, or to avoid premature changing of the earth working tool with the economic disadvantages associated therewith. </pat:P><pat:P pat:pNumber="18" pat:id="p-18">[0012] According to a preferred variant of the invention, provision can be made that the remaining working output of the earth working machine until the wear limit of the earth working tool is reached is ascertained from the residual wear capacity based on at least one characteristic value or on the derivation of at least one characteristic value. What is ascertained as the remaining working output can be, for example, the milling output, in particular the mass of material that can still be milled and/or the volume of material that can still be milled and/or the remaining travel distance for the earth working machine or the remaining working time for the earth working machine. These parameters give the machine operator information that can be unequivocally implemented. </pat:P><pat:P pat:pNumber="19" pat:id="p-19">[0013] An effective wear prognosis can be generated by comparing the current wear state of the earth working tool with a reference value reproducing at least a portion of the earth working tool in the worn state, in order to ascertain the residual wear capacity. The reference value can be, for example, a reference contour (partial contour or complete contour), one or more reference points, a reference volume (partial volume or total volume), or the location or direction of the longitudinal center axis of the earth working tool. </pat:P><pat:P pat:pNumber="20" pat:id="p-20">[0014] The reliability of the working process is additionally improved when provision is further made that the wear state of several or of all earth working tools of the earth working machine is ascertained; and that the earth working tool exhibiting the least residual wear <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>4</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='5'?><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData>capacity is taken into account for ascertaining the remaining working output until the wear limit is reached. For example, a few representative earth working tools can be selected so that a detailed wear statement can be made. If all the earth working tools are monitored, an almost one-hundred-percent wear statement becomes possible. </pat:P><pat:P pat:pNumber="21" pat:id="p-21">[0015] A method according to the present invention for wear prognosis can be characterized in that a working area within which two or more earth working machines are being used is defined; and that the current wear state of at least one earth working tool of an earth working machine is ascertained, and that the at least one characteristic value or the derivation of the one or more characteristic values is derived from the previously produced milling output of said at least one earth working tool and from the wear, corresponding thereto, of the at least one earth working tool. A reference working process is therefore carried out. For example, firstly unworn tools or tools that already exhibit partial wear are used. The working process is then carried out using a working machine of this kind. During this process, various parameters can then be acquired, in particular the milling output produced. The milling output produced can be, for example, as already described above, the mass of material milled, the distance traveled, etc. A correlation can then be arrived at by differential analysis between the previously known wear state and the wear state existing after the working process. This indicates the wear that has occurred on the tools in the context of the working output produced. From this, one or more characteristic values can then be derived. These characteristic values can then be used in order to ascertain, for any given wear state (and residual wear capacity resulting therefrom), the working output still to be produced (for example, until the wear limit is reached). </pat:P><pat:P pat:pNumber="22" pat:id="p-22">[0016] These characteristic values can correspondingly be ascertained and utilized directly on the working machine that is present, or they can be conveyed to at least one further earth working machine that, in particular, is working a comparable substrate. </pat:P><pat:P pat:pNumber="23" pat:id="p-23"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>5</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='6'?><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData>[0017] In another embodiment of the invention, the at least one characteristic value is ascertained in consideration of the material properties, in particular the abrasiveness and/or material hardness, of the substrate to be worked. </pat:P><pat:P pat:pNumber="24" pat:id="p-24">[0018] For practical reasons, the at least one characteristic value can be ascertained preferably in consideration of a material hardness range that contains the material hardness of the substrate being worked. Additionally or alternatively, provision can also be made that the characteristic value is ascertained in consideration of an abrasiveness range that contains the abrasiveness of the substrate to be worked. For example, selective measurements from the sector to be worked can be representatively performed, and the values for material hardness and/or abrasiveness can be determined in that context. </pat:P><pat:P pat:pNumber="25" pat:id="p-25">[0019] In mining it is usual to take samples from an area that is to be worked, in particular to perform sample boring operations. The samples are then investigated and the raw material<pat:OCRConfidenceData pat:levelNumber='68'>'s</pat:OCRConfidenceData> parameters are identified. According to an inventive alternative, these results can also be used directly in the method according to the present invention, so that the characteristic values/material properties for inferring the characteristic values can be ascertained therefrom. </pat:P><pat:P pat:pNumber="26" pat:id="p-26">[0020] It is also conceivable for the machine operator to be able to select, from a list of different substrate categories, the category suitable for the substrate currently to be worked, and for the material properties for ascertaining the at least one characteristic value to be associated with said substrate categories. The result is that the machine operator can simply assess the substrate on site in consideration of his accumulated experience, and can make a corresponding selection. For example, one or more characteristic values are associated with this substrate category in a database. When the substrate category is selected, these characteristic values are then read out from the database and processed via software in order to ascertain the residual wear capacity and thus the remaining working <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>6</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='7'?><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData>output. This method has the advantage that the machine operator can respectively determine the residual wear capacity and the remaining working output directly on site, and can also implement an adaptation in particular as substrate categories change. </pat:P><pat:P pat:pNumber="27" pat:id="p-27">[0021] Alternatively or additionally, it is also conceivable to indirectly sense the material properties of the substrate to be worked. Provision can be made here that the material properties for ascertaining the at least one characteristic value are ascertained during working operation on the basis of machine parameters. For example, the milling depth, machine advance, milling drum rotation speed, torque applied to the processing tools, and/or power output currently being delivered by the drive engine can be ascertained. These machine parameters provide information regarding the material properties, in particular the abrasiveness or hardness, of the substrate to be processed. The rotation speed, torque, and delivered power output can be taken directly from the engine control unit (ECU) of the drive engine. The first two parameters can be furnished by the machine control system. </pat:P><pat:P pat:pNumber="28" pat:id="p-28">[0022] A particularly preferred inventive variant is such that firstly the current wear state and the residual wear capacity are ascertained; and then the working output produced by the earth working machine, in particular the milling output and/or the machine data occurring during that working process, are monitored. The actual wear state of the earth working tool can then be ascertained, for example calculated, continuously during the working process. If, for example, a change in the substrate category then occurs or if a new processing task is undertaken, this most recently ascertained actual wear state can be employed as a current wear state for purposes of the invention, and the residual wear capacity available for the task at hand can then be ascertained. </pat:P><pat:P pat:pNumber="29" pat:id="p-29">[0023] A calculation unit, with which a memory unit is associated, is preferably provided. The one or several characteristic values, or the derivation of the characteristic values, is/are <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>7</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='8'?><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData>stored in the memory unit. The current wear state can be sensed with a sensing device. The remaining working output until the wear limit of the earth working tools is reached can be ascertained by means of the calculation unit using the current wear state, the residual wear capacity resulting therefrom, and the characteristic value or values or the derivation thereof. The residual wear capacity can be ascertained in the calculation unit on the basis of the wear state and the reference contour. The calculation unit and/or the memory unit can be, for example, directly associated with the earth working machine. It is also conceivable, however, for the calculation unit and/or the memory unit to be associated with a separate system unit. When provision is made for separate association, the earth working machine can then be in mutual communication with the system unit via a preferably wireless remote data transfer link. Depending on the whereabouts of the earth working machine, the latter can then be supplied with relevant parameters; in particular, the residual wear capacity and/or remaining working output can be conveyed. Among the advantages of this is the fact that when multiple earth working machines are being used in one working area, they can each individually retrieve the necessary data from the system unit. </pat:P><pat:P pat:pNumber="30" pat:id="p-30">[0024] The characteristic values can be stored in the calculation/memory unit as a function of location. For example, a map of, for example, a mine can be stored, in which map different characteristics values are associated with different locations. The machines can possess GPS, or the operator inputs his location, and the corresponding characteristic values are used. It would also be possible, especially in the context of an external calculation unit, for only the material properties to be stored and for the characteristic values to be ascertained by the machine itself on the basis of those material properties. </pat:P><pat:P pat:pNumber="31" pat:id="p-31">[0025] The object of the invention is also achieved by a maintenance method for an earth working machine, in which a plurality of earth working tools, in particular bits and/or bit holders, are used. In this context, the current wear state of at least one earth working tool is <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='5'>8</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='9'?><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData>sensed. Proceeding from that wear state, the residual wear capacity of the earth working tool is then ascertained. Before the wear limit of the earth working tool is reached, a technician is then informed so that maintenance can be carried out. In the context of this maintenance method, a prognosis regarding the remaining milling output can be created in consideration of the residual wear capacity that is ascertained. A maintenance unit can be informed in timely fashion before said milling output has been entirely produced. This can occur, for example, in automated fashion by means of a signaling device of the earth working machine. This signaling device outputs a corresponding signal that can be conveyed preferably wirelessly to a maintenance station. The working output of the earth working machine remaining until the wear limit of the earth working tool is reached can be signaled in the form of the distance that can still be milled, the volume or mass that can still be milled, and/or the remaining service life. In the context of an earth working machine, for example, it is possible for the residual wear capacity of the earth working tool to be ascertained before a planned working process is undertaken. The maintenance intervals for that working process can then already be predicted or optimized in advance as a function of the predicted wear for the milling task. </pat:P><pat:P pat:pNumber="32" pat:id="p-32">[0026] Whereas the material characteristic values and residual wear capacity can be taken into account in order to ascertain the remaining working output, here conversely the expected bit change is ascertained using the material properties and the remaining working output. </pat:P><pat:Heading pat:id="h-4">BRIEF DESCRIPTION OF THE DRAWINGS</pat:Heading><pat:P pat:pNumber="33" pat:id="p-33">[0027] The invention will be explained in further detail below with reference to an exemplifying embodiment depicted in the drawings, in which: </pat:P><pat:P pat:pNumber="34" pat:id="p-34"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>9</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='10'?><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData>[0028] FIG. 1 is a side view of a bit, namely a round shank bit for a road milling machine, a mining machine, a surface miner, or the like, which is inserted into the holder of a quick- change holder tool for such machines; </pat:P><pat:P pat:pNumber="35" pat:id="p-35">[0029] FIG. 2 is a diagram showing the bit head of the bit according to FIG. 1; </pat:P><pat:P pat:pNumber="36" pat:id="p-36">[0030] FIGS. 3 to 7 are diagrams showing various wear states of the bit head; </pat:P><pat:P pat:pNumber="37" pat:id="p-37">[0031] FIG. 8 is a schematic depiction and side view of a milling machine; </pat:P><pat:P pat:pNumber="38" pat:id="p-38">[0032] FIG. 9 shows a milling drum of the milling machine in accordance with FIG. 8, having an example of a surveying device based on the triangulation principle; </pat:P><pat:P pat:pNumber="39" pat:id="p-39">[0033] FIG. 10 shows the milling drum in accordance with FIG. 8, having an alternative embodiment of the surveying device based on a shadow-casting method; and </pat:P><pat:P pat:pNumber="40" pat:id="p-40">[0034] FIG. 11 schematically depicts a working situation with two milling machines. </pat:P><pat:Heading pat:id="h-5">DETAILED DESCRIPTION</pat:Heading><pat:P pat:pNumber="41" pat:id="p-41">[0035] FIG. 1 shows, as an example of an earth working tool, a <pat:PartName pat:idref='PN-00008'>bit</pat:PartName> <pat:PartNumber pat:id='PN-00008'>10</pat:PartNumber> as known from the existing art and <pat:PartName pat:idref='PN-00009'>described by way of example in DE</pat:PartName> <pat:PartNumber pat:id='PN-00009'>38</pat:PartNumber> 18 213 A<pat:OCRConfidenceData pat:levelNumber='5'>l</pat:OCRConfidenceData>. <pat:PartName pat:idref='PN-00010'>Bit</pat:PartName> <pat:PartNumber pat:id='PN-00010'>10</pat:PartNumber> comprises a <pat:PartName pat:idref='PN-00011'>bit head</pat:PartName> <pat:PartNumber pat:id='PN-00011'>12</pat:PartNumber> and a <pat:PartName pat:idref='PN-00012'>bit shank</pat:PartName> <pat:PartNumber pat:id='PN-00012'>15</pat:PartNumber> shaped integrally thereonto. <pat:PartName pat:idref='PN-00013'>Bit head</pat:PartName> <pat:PartNumber pat:id='PN-00013'>12</pat:PartNumber> carries a <pat:PartName pat:idref='PN-00014'>bit tip</pat:PartName> <pat:PartNumber pat:id='PN-00014'>11</pat:PartNumber> made of a hard material, for example of carbide metal. </pat:P><pat:P pat:pNumber="42" pat:id="p-42">[0036] <pat:PartName pat:idref='PN-00015'>This bit tip</pat:PartName> <pat:PartNumber pat:id='PN-00015'>11</pat:PartNumber> <pat:PartName pat:idref='PN-00016'>is usually soldered onto bit head</pat:PartName> <pat:PartNumber pat:id='PN-00016'>12</pat:PartNumber> along a contact surface. A <pat:PartName pat:idref='PN-00017'>circumferential pull-out groove</pat:PartName> <pat:PartNumber pat:id='PN-00017'>13</pat:PartNumber> <pat:PartName pat:idref='PN-00018'>is recessed into bit head</pat:PartName> <pat:PartNumber pat:id='PN-00018'>12</pat:PartNumber>. This groove serves as a tool receptacle, such that a removal tool can be set in place and <pat:PartName pat:idref='PN-00019'>bit</pat:PartName> <pat:PartNumber pat:id='PN-00019'>10</pat:PartNumber> can be removed from a <pat:PartName pat:idref='PN-00020'>bit holder</pat:PartName> <pat:PartNumber pat:id='PN-00020'>70</pat:PartNumber>. </pat:P><pat:P pat:pNumber="43" pat:id="p-43">[0037] <pat:PartName pat:idref='PN-00021'>Bit shank</pat:PartName> <pat:PartNumber pat:id='PN-00021'>15</pat:PartNumber> carries a <pat:PartName pat:idref='PN-00022'>longitudinally slotted cylindrical clamping sleeve</pat:PartName> <pat:PartNumber pat:id='PN-00022'>21</pat:PartNumber>. <pat:PartName pat:idref='PN-00023'>This is held on bit shank</pat:PartName> <pat:PartNumber pat:id='PN-00023'>15</pat:PartNumber> in lossproof fashion in the direction of the <pat:PartName pat:idref='PN-00024'>longitudinal dimension of bit</pat:PartName> <pat:PartNumber pat:id='PN-00024'>10</pat:PartNumber>, but freely rotatably in the circumferential direction. A <pat:PartName pat:idref='PN-00025'>wear protection washer</pat:PartName> <pat:PartNumber pat:id='PN-00025'>20</pat:PartNumber> is arranged <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>10</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='11'?><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData>in the <pat:PartName pat:idref='PN-00026'>region between clamping sleeve</pat:PartName> <pat:PartNumber pat:id='PN-00026'>21</pat:PartNumber> and <pat:PartName pat:idref='PN-00027'>bit head</pat:PartName> <pat:PartNumber pat:id='PN-00027'>12</pat:PartNumber>. In the installed state, <pat:PartName pat:idref='PN-00028'>wear protection washer</pat:PartName> <pat:PartNumber pat:id='PN-00028'>20</pat:PartNumber> is braced against a countersurface of a <pat:PartName pat:idref='PN-00029'>bit holder</pat:PartName> <pat:PartNumber pat:id='PN-00029'>70</pat:PartNumber> and <pat:PartName pat:idref='PN-00030'>against bit holder</pat:PartName> <pat:PartNumber pat:id='PN-00030'>70</pat:PartNumber>, facing away from the <pat:PartName pat:idref='PN-00031'>underside of bit head</pat:PartName> <pat:PartNumber pat:id='PN-00031'>12</pat:PartNumber>. </pat:P><pat:P pat:pNumber="44" pat:id="p-44">[0038] <pat:PartName pat:idref='PN-00032'>Bit holder</pat:PartName> <pat:PartNumber pat:id='PN-00032'>70</pat:PartNumber> is equipped with a <pat:PartName pat:idref='PN-00033'>projection</pat:PartName> <pat:PartNumber pat:id='PN-00033'>71</pat:PartNumber> into which a <pat:PartName pat:idref='PN-00034'>bit receptacle</pat:PartName> <pat:PartNumber pat:id='PN-00034'>72</pat:PartNumber> in the form of a cylindrical bore is recessed. <pat:PartName pat:idref='PN-00035'>In this bit receptacle</pat:PartName> <pat:PartNumber pat:id='PN-00035'>72</pat:PartNumber>, <pat:PartName pat:idref='PN-00036'>clamping sleeve</pat:PartName> <pat:PartNumber pat:id='PN-00036'>21</pat:PartNumber> is held with its external periphery clamped against the inner wall of the bore. <pat:PartName pat:idref='PN-00037'>Bit receptacle</pat:PartName> <pat:PartNumber pat:id='PN-00037'>72</pat:PartNumber> opens into a <pat:PartName pat:idref='PN-00038'>drift opening</pat:PartName> <pat:PartNumber pat:id='PN-00038'>73</pat:PartNumber>. Through this, a drift punch (not shown) can be introduced for the <pat:PartName pat:idref='PN-00039'>purpose of removing bit</pat:PartName> <pat:PartNumber pat:id='PN-00039'>10</pat:PartNumber>. Said punch acts on the <pat:PartName pat:idref='PN-00040'>end of bit shank</pat:PartName> <pat:PartNumber pat:id='PN-00040'>15</pat:PartNumber> in such a <pat:PartName pat:idref='PN-00041'>way that bit</pat:PartName> <pat:PartNumber pat:id='PN-00041'>10</pat:PartNumber> <pat:PartName pat:idref='PN-00042'>is pushed out of bit receptacle</pat:PartName> <pat:PartNumber pat:id='PN-00042'>72</pat:PartNumber> as the <pat:PartName pat:idref='PN-00043'>clamping force of clamping sleeve</pat:PartName> <pat:PartNumber pat:id='PN-00043'>21</pat:PartNumber> is overcome. </pat:P><pat:P pat:pNumber="45" pat:id="p-45">[0039] As is evident from FIG. 1, <pat:PartName pat:idref='PN-00044'>extension</pat:PartName> <pat:PartNumber pat:id='PN-00044'>71</pat:PartNumber> is equipped in a <pat:PartName pat:idref='PN-00045'>cylindrical region below wear protection washer</pat:PartName> <pat:PartNumber pat:id='PN-00045'>20</pat:PartNumber> with two circumferential grooves. <pat:PartName pat:idref='PN-00046'>These grooves serve as wear markings</pat:PartName> <pat:PartNumber pat:id='PN-00046'>74</pat:PartNumber>. During operational use, <pat:PartName pat:idref='PN-00047'>wear protection washer</pat:PartName> <pat:PartNumber pat:id='PN-00047'>20</pat:PartNumber> rotates and, in that context, can create wear (bit holder wear) on the <pat:PartName pat:idref='PN-00048'>support surface of projection</pat:PartName> <pat:PartNumber pat:id='PN-00048'>71</pat:PartNumber>. When the support surface has been worn away to the extent that the second wear marking has been reached, <pat:PartName pat:idref='PN-00049'>bit holder</pat:PartName> <pat:PartNumber pat:id='PN-00049'>70</pat:PartNumber> is considered to be worn in such a way that it must be replaced. </pat:P><pat:P pat:pNumber="46" pat:id="p-46">[0040] <pat:PartName pat:idref='PN-00050'>Bit holder</pat:PartName> <pat:PartNumber pat:id='PN-00050'>70</pat:PartNumber> comprises an <pat:PartName pat:idref='PN-00051'>insertion projection</pat:PartName> <pat:PartNumber pat:id='PN-00051'>75</pat:PartNumber> that is introducible into an <pat:PartName pat:idref='PN-00052'>insertion receptacle</pat:PartName> <pat:PartNumber pat:id='PN-00052'>82</pat:PartNumber> of a <pat:PartName pat:idref='PN-00053'>base part</pat:PartName> <pat:PartNumber pat:id='PN-00053'>80</pat:PartNumber> and can be clamped there by means of a <pat:PartName pat:idref='PN-00054'>clamping screw</pat:PartName> <pat:PartNumber pat:id='PN-00054'>83</pat:PartNumber>. </pat:P><pat:P pat:pNumber="47" pat:id="p-47">[0041] <pat:PartName pat:idref='PN-00055'>Clamping screw</pat:PartName> <pat:PartNumber pat:id='PN-00055'>83</pat:PartNumber> presses an <pat:PartName pat:idref='PN-00056'>abutment surface</pat:PartName> <pat:PartNumber pat:id='PN-00056'>76</pat:PartNumber> <pat:PartName pat:idref='PN-00057'>of bit holder</pat:PartName> <pat:PartNumber pat:id='PN-00057'>70</pat:PartNumber> onto a <pat:PartName pat:idref='PN-00058'>support surface</pat:PartName> <pat:PartNumber pat:id='PN-00058'>84</pat:PartNumber> <pat:PartName pat:idref='PN-00059'>of base part</pat:PartName> <pat:PartNumber pat:id='PN-00059'>80</pat:PartNumber>. Although this is not depicted in further detail in FIG. 1, <pat:PartName pat:idref='PN-00060'>base part</pat:PartName> <pat:PartNumber pat:id='PN-00060'>80</pat:PartNumber> <pat:PartName pat:idref='PN-00061'>itself is welded via its underside</pat:PartName> <pat:PartNumber pat:id='PN-00061'>81</pat:PartNumber> onto the milling drum tube of a milling drum. </pat:P><pat:P pat:pNumber="48" pat:id="p-48">[0042] <pat:PartName pat:idref='PN-00062'>Noncontact surveying of bit head</pat:PartName> <pat:PartNumber pat:id='PN-00062'>12</pat:PartNumber> is performed in order to ascertain the <pat:PartName pat:idref='PN-00063'>current wear state of bit</pat:PartName> <pat:PartNumber pat:id='PN-00063'>10</pat:PartNumber> installed on the bit holder, a defined point or <pat:PartName pat:idref='PN-00064'>multiple points of bit head</pat:PartName> <pat:PartNumber pat:id='PN-00064'>12</pat:PartNumber> being measured/ascertained as a position value. FIG. 2 is a side view of the contour of an <pat:PartName pat:idref='PN-00065'>unworn bit head</pat:PartName> <pat:PartNumber pat:id='PN-00065'>12</pat:PartNumber>. This contour is illustrated in a diagram, the <pat:PartName pat:idref='PN-00066'>dimension of bit head</pat:PartName> <pat:PartNumber pat:id='PN-00066'>12</pat:PartNumber> in <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>11</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='12'?><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData>the direction of the <pat:PartName pat:idref='PN-00067'>longitudinal bit axis of bit</pat:PartName> <pat:PartNumber pat:id='PN-00067'>10</pat:PartNumber> (X axis) being plotted against the dimension in the width direction (perpendicular to the longitudinal center axis, i.e. Y axis). The <pat:PartName pat:idref='PN-00068'>contour of bit head</pat:PartName> <pat:PartNumber pat:id='PN-00068'>12</pat:PartNumber> <pat:PartName pat:idref='PN-00069'>(including bit tip</pat:PartName> <pat:PartNumber pat:id='PN-00069'>11</pat:PartNumber>) is assembled from a plurality of measured points, and the linear boundary (contour line) represents an interpolation of these position values. </pat:P><pat:P pat:pNumber="49" pat:id="p-49">[0043] Surveying of a <pat:PartName pat:idref='PN-00070'>milling drum</pat:PartName> <pat:PartNumber pat:id='PN-00070'>35</pat:PartNumber> (see FIGS. 9 and <pat:PartName pat:idref='PN-00071'>10) can be performed when bit</pat:PartName> <pat:PartNumber pat:id='PN-00071'>10</pat:PartNumber> is in the unworn, worn-out, or partly worn state. These points, the calculated bit head contour, or even only a single measurement point can then be acquired and stored as a reference value in a memory unit. </pat:P><pat:P pat:pNumber="50" pat:id="p-50">[0044] FIG. 3 shows a variety of measured images of a <pat:PartName pat:idref='PN-00072'>bit</pat:PartName> <pat:PartNumber pat:id='PN-00072'>10</pat:PartNumber>, <pat:PartName pat:idref='PN-00073'>bit head</pat:PartName> <pat:PartNumber pat:id='PN-00073'>12</pat:PartNumber> being depicted in the unworn state and in three measured wear states V<pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData> to V3. Wear state V3 represents the <pat:PartName pat:idref='PN-00074'>state in which bit</pat:PartName> <pat:PartNumber pat:id='PN-00074'>10</pat:PartNumber> is no longer suitable for further processing and must be replaced. The wear can be ascertained by comparing the reference value (contour in the unworn state) with the respectively measured current bit head contour (wear states V<pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData>, V2, or V3) that reproduce the position value. </pat:P><pat:P pat:pNumber="51" pat:id="p-51">[0045] The contours must be aligned with one another. Because of holder wear or other error sources, unworn contour regions are not necessarily located at the same absolute positions (or relative positions with respect to the drum rotation axis). In order to correlate the contours there is a further need for reference features that are uniquely identifiable, occur in the unworn and worn state, and thus permit alignment and conclusive evaluation. <pat:PartName pat:idref='PN-00075'>Pull-out groove</pat:PartName> <pat:PartNumber pat:id='PN-00075'>13</pat:PartNumber>, <pat:PartName pat:idref='PN-00076'>wear markings</pat:PartName> <pat:PartNumber pat:id='PN-00076'>74</pat:PartNumber>, <pat:PartName pat:idref='PN-00077'>wear protection washer</pat:PartName> <pat:PartNumber pat:id='PN-00077'>20</pat:PartNumber>, or other salient regions that are subject to little or no wear can serve as reference features. </pat:P><pat:P pat:pNumber="52" pat:id="p-52">[0046] As illustrated by FIG. 3, the <pat:PartName pat:idref='PN-00078'>length of bit head</pat:PartName> <pat:PartNumber pat:id='PN-00078'>12</pat:PartNumber> decreases during operational use. By differentiating the contour lines in a circuit unit it is possible to generate a statement regarding the wear state, which can be made visible to the user, for example, in a display unit. Instead of surveying the <pat:PartName pat:idref='PN-00079'>entire contour of bit head</pat:PartName> <pat:PartNumber pat:id='PN-00079'>12</pat:PartNumber>, it is also possible to sense only a <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>12</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='13'?><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData>portion of the contour or a single point, in particular the <pat:PartName pat:idref='PN-00080'>front end of bit tip</pat:PartName> <pat:PartNumber pat:id='PN-00080'>11</pat:PartNumber>, as a position value. Further detail in the wear statement can be achieved if the <pat:PartName pat:idref='PN-00081'>wear on bit tip</pat:PartName> <pat:PartNumber pat:id='PN-00081'>11</pat:PartNumber> and <pat:PartName pat:idref='PN-00082'>on bit head</pat:PartName> <pat:PartNumber pat:id='PN-00082'>12</pat:PartNumber> <pat:PartName pat:idref='PN-00083'>(without bit tip</pat:PartName> <pat:PartNumber pat:id='PN-00083'>11</pat:PartNumber>) is sensed separately. </pat:P><pat:P pat:pNumber="53" pat:id="p-53">[0047] This can easily be done using the <pat:PartName pat:idref='PN-00084'>position (attachment point TP/attachment line</pat:PartName> <pat:PartNumber pat:id='PN-00084'>18</pat:PartNumber>), known a priori, <pat:PartName pat:idref='PN-00085'>at which bit tip</pat:PartName> <pat:PartNumber pat:id='PN-00085'>11</pat:PartNumber> attaches to <pat:PartName pat:idref='PN-00086'>bit head</pat:PartName> <pat:PartNumber pat:id='PN-00086'>12</pat:PartNumber> in the unworn state. </pat:P><pat:P pat:pNumber="54" pat:id="p-54">[0048] When the measured wear states V<pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData> to V3 are overlaid on the <pat:PartName pat:idref='PN-00087'>unworn contour of bit head</pat:PartName> <pat:PartNumber pat:id='PN-00087'>12</pat:PartNumber>, as shown in FIG. 2, it is then possible to ascertain the total wear volume by integrating the measured contours along the X axis. In FIG. 4 the wear volume is shown as hatched areas. </pat:P><pat:P pat:pNumber="55" pat:id="p-55">[0049] The wear volume that constitutes a position value can thus be compared with a reference value. The reference value can be constituted by a functional relationship or a characteristics diagram, different wear volumes being correlated with associated wear states (for example, A mm<pat:OCRConfidenceData pat:levelNumber='2'>'</pat:OCRConfidenceData> of wear volume corresponds to B% wear). From the position, known a priori, <pat:PartName pat:idref='PN-00088'>of attachment point TP/attachment line</pat:PartName> <pat:PartNumber pat:id='PN-00088'>18</pat:PartNumber>, the <pat:PartName pat:idref='PN-00089'>tip wear</pat:PartName> <pat:PartNumber pat:id='PN-00089'>16</pat:PartNumber> and <pat:PartName pat:idref='PN-00090'>head wear</pat:PartName> <pat:PartNumber pat:id='PN-00090'>17</pat:PartNumber> can then also be separately ascertained by differentiation. This wear detection process provides the user, for example, with a qualitative statement as to <pat:PartName pat:idref='PN-00091'>whether bit</pat:PartName> <pat:PartNumber pat:id='PN-00091'>10</pat:PartNumber> is still suitable for specific milling tasks. For example, a bit that has not yet reached its wear limit but exhibits some tip wear can no longer be used, for example, for precision milling work. </pat:P><pat:P pat:pNumber="56" pat:id="p-56">[0050] In the method according to FIGS. 3 and 4, the measured position values are overlaid on the reference values. During the working process, <pat:PartName pat:idref='PN-00092'>not only bit head</pat:PartName> <pat:PartNumber pat:id='PN-00092'>12</pat:PartNumber> but also the bit holder becomes worn. The latter wears away in the direction of the <pat:PartName pat:idref='PN-00093'>longitudinal center axis of bit</pat:PartName> <pat:PartNumber pat:id='PN-00093'>10</pat:PartNumber>. Isolated identification of the longitudinal wear on the bit holder in this direction can now easily be achieved by the fact that the magnitude of the displacement of the position value toward the reference value in order obtain the overlays indicated in FIGS. 3 and 4 <pat:PartName pat:idref='PN-00094'>(shifting bit head</pat:PartName> <pat:PartNumber pat:id='PN-00094'>12</pat:PartNumber> in the direction of the X axis, for example until the pull-out grooves of <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>13</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='14'?><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData>the individual wear states are superimposed) yields an absolute value for the wear on the bit holder. The <pat:PartName pat:idref='PN-00095'>total displacement of bit tip</pat:PartName> <pat:PartNumber pat:id='PN-00095'>11</pat:PartNumber>, minus said wear value, then separately indicates the bit wear. </pat:P><pat:P pat:pNumber="57" pat:id="p-57">[0051] FIG. 5 shows a variant method in which a wear statement is arrived at based on surveying one uniquely identifiable feature on the bit. The feature, or the surroundings of said feature, should be subject to little or no wear. According to FIG. 5, <pat:PartName pat:idref='PN-00096'>pull-out groove</pat:PartName> <pat:PartNumber pat:id='PN-00096'>13</pat:PartNumber>, a <pat:PartName pat:idref='PN-00097'>portion of pull-out groove</pat:PartName> <pat:PartNumber pat:id='PN-00097'>13</pat:PartNumber>, or a point (for example the <pat:PartName pat:idref='PN-00098'>groove base) on pull-out groove</pat:PartName> <pat:PartNumber pat:id='PN-00098'>13</pat:PartNumber> is used as a unique feature and reference criterion. </pat:P><pat:P pat:pNumber="58" pat:id="p-58">[0052] The distance from this feature to the position of the <pat:PartName pat:idref='PN-00099'>free end of bit tip</pat:PartName> <pat:PartNumber pat:id='PN-00099'>11</pat:PartNumber> (position value) is then further ascertained. It is then easy to ascertain the longitudinal wear in this manner. If the <pat:PartName pat:idref='PN-00100'>position of bit tip</pat:PartName> <pat:PartNumber pat:id='PN-00100'>11</pat:PartNumber> is known, then once again, as described above, the bit holder wear can also be identified. Alternatively or additionally, as defined in FIG. 4, the wear volume and the associated wear lengths - X<pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData> (currently measured length of partly worn bit), X2 (worn-out length), and Xges (total length of unworn bit) - can also be ascertained. </pat:P><pat:P pat:pNumber="59" pat:id="p-59">[0053] Relative measurement using a uniquely identifiable feature as reference point has the advantage that wear detection can be performed even when a reference measurement is not available, for example because the length of the <pat:PartName pat:idref='PN-00101'>replaced bit</pat:PartName> <pat:PartNumber pat:id='PN-00101'>10</pat:PartNumber>, or the <pat:PartName pat:idref='PN-00102'>wear state of bit</pat:PartName> <pat:PartNumber pat:id='PN-00102'>10</pat:PartNumber> or of the bit holder, is not known. </pat:P><pat:P pat:pNumber="60" pat:id="p-60">[0054] FIG. 3 shows the change in the bit head contour as wear proceeds. The <pat:PartName pat:idref='PN-00103'>decreasing length of bit head</pat:PartName> <pat:PartNumber pat:id='PN-00103'>12</pat:PartNumber> is evident. If the measured bit head contours are respectively shifted to the point of the <pat:PartName pat:idref='PN-00104'>maximum length of bit</pat:PartName> <pat:PartNumber pat:id='PN-00104'>10</pat:PartNumber> (FIG. <pat:OCRConfidenceData pat:levelNumber='5'>6</pat:OCRConfidenceData>), the <pat:PartName pat:idref='PN-00105'>increasing wear state of bit</pat:PartName> <pat:PartNumber pat:id='PN-00105'>10</pat:PartNumber> is evident on the one hand from the change in head angle (the angle becomes flatter as bit wear increases) and on the other hand from the <pat:PartName pat:idref='PN-00106'>increasing volume of bit head</pat:PartName> <pat:PartNumber pat:id='PN-00106'>12</pat:PartNumber> when the area under the contour curve is integrated from the respective tip over a specific length. A functional relationship can thus be created between the head volume/area and the absolute <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>14</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='15'?><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData>bit length for a specific bit type, for example by means of experiments carried out a priori in order to ascertain the reference values. </pat:P><pat:P pat:pNumber="61" pat:id="p-61">[0055] Once this relationship is known, the <pat:PartName pat:idref='PN-00107'>length of bit</pat:PartName> <pat:PartNumber pat:id='PN-00107'>10</pat:PartNumber> can be ascertained by measurement/integration of the respectively current head volume. This method requires, however, <pat:PartName pat:idref='PN-00108'>that bit tip</pat:PartName> <pat:PartNumber pat:id='PN-00108'>11</pat:PartNumber> have a cross section that increases in the longitudinal direction of the bit. The integration path is preferably defined so that integration does not occur into the <pat:PartName pat:idref='PN-00109'>head region even for completely worn-out bits</pat:PartName> <pat:PartNumber pat:id='PN-00109'>10</pat:PartNumber>, since head erosion distorts the result. </pat:P><pat:P pat:pNumber="62" pat:id="p-62">[0056] This method has the advantage of not requiring a reference point that is subject to little wear. Such a reference point sometimes is not present or is very difficult to identify. </pat:P><pat:P pat:pNumber="63" pat:id="p-63">[0057] The average between the upper and lower contour line can, for example, be calculated in order to identify the degree of wear asymmetry. FIG. 7 shows the contour lines, and their averages, for a <pat:PartName pat:idref='PN-00110'>new bit tip</pat:PartName> <pat:PartNumber pat:id='PN-00110'>11</pat:PartNumber> and for one that is worn rotationally symmetrically <pat:OCRConfidenceData pat:levelNumber='885'>(R1</pat:OCRConfidenceData>) and rotationally asymmetrically (R2). It is evident that with the <pat:PartName pat:idref='PN-00111'>asymmetrically worn bit</pat:PartName> <pat:PartNumber pat:id='PN-00111'>10</pat:PartNumber>, the center line M2 of the two contour lines exhibits a certain slope with respect to the longitudinal bit axis. The angular position could easily be evaluated in order to determine the degree of wear asymmetry. The location/deviations of several contour lines could, however, also be identified/ascertained directly. </pat:P><pat:P pat:pNumber="64" pat:id="p-64">[0058] <pat:PartName pat:idref='PN-00112'>Asymmetrical wear on bit head</pat:PartName> <pat:PartNumber pat:id='PN-00112'>12</pat:PartNumber> can be identified using the same method. Usually, however, an <pat:PartName pat:idref='PN-00113'>asymmetrically worn bit tip</pat:PartName> <pat:PartNumber pat:id='PN-00113'>11</pat:PartNumber> will be accompanied by an <pat:PartName pat:idref='PN-00114'>asymmetrically worn bit head</pat:PartName> <pat:PartNumber pat:id='PN-00114'>12</pat:PartNumber>. An <pat:PartName pat:idref='PN-00115'>analysis of bit tip</pat:PartName> <pat:PartNumber pat:id='PN-00115'>11</pat:PartNumber> is thus sufficient. </pat:P><pat:P pat:pNumber="65" pat:id="p-65">[0059] FIG. <pat:OCRConfidenceData pat:levelNumber='5'>8</pat:OCRConfidenceData> symbolically depicts a <pat:PartName pat:idref='PN-00116'>milling machine</pat:PartName> <pat:PartNumber pat:id='PN-00116'>30</pat:PartNumber>, for example a surface miner, a road milling machine, or the like, in which a <pat:PartName pat:idref='PN-00117'>machine body</pat:PartName> <pat:PartNumber pat:id='PN-00117'>32</pat:PartNumber> <pat:PartName pat:idref='PN-00118'>is carried by four columnar drive units</pat:PartName> <pat:PartNumber pat:id='PN-00118'>31</pat:PartNumber>. <pat:PartName pat:idref='PN-00119'>Road milling machine</pat:PartName> <pat:PartNumber pat:id='PN-00119'>30</pat:PartNumber> can be operated from a <pat:PartName pat:idref='PN-00120'>control station</pat:PartName> <pat:PartNumber pat:id='PN-00120'>33</pat:PartNumber>. A <pat:PartName pat:idref='PN-00121'>milling drum</pat:PartName> <pat:PartNumber pat:id='PN-00121'>35</pat:PartNumber> is arranged in a <pat:PartName pat:idref='PN-00122'>milling drum box</pat:PartName> <pat:PartNumber pat:id='PN-00122'>34</pat:PartNumber>. </pat:P><pat:P pat:pNumber="66" pat:id="p-66"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>15</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='16'?><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData>[0060] In order to measure the wear state according to one of the methods described above, a <pat:PartName pat:idref='PN-00123'>light source</pat:PartName> <pat:PartNumber pat:id='PN-00123'>50</pat:PartNumber> and a <pat:PartName pat:idref='PN-00124'>camera</pat:PartName> <pat:PartNumber pat:id='PN-00124'>40</pat:PartNumber> <pat:PartName pat:idref='PN-00125'>are associated with milling drum</pat:PartName> <pat:PartNumber pat:id='PN-00125'>35</pat:PartNumber>. <pat:PartName pat:idref='PN-00126'>Milling drum</pat:PartName> <pat:PartNumber pat:id='PN-00126'>35</pat:PartNumber> is shown more clearly in FIG. 9. A plurality of bit holder quick-change systems, each having a <pat:PartName pat:idref='PN-00127'>bit holder</pat:PartName> <pat:PartNumber pat:id='PN-00127'>70</pat:PartNumber>, are mounted on the surface of a <pat:PartName pat:idref='PN-00128'>milling tube</pat:PartName> <pat:PartNumber pat:id='PN-00128'>35.1</pat:PartNumber> <pat:PartName pat:idref='PN-00129'>of milling drum</pat:PartName> <pat:PartNumber pat:id='PN-00129'>35</pat:PartNumber>. A <pat:PartName pat:idref='PN-00130'>bit</pat:PartName> <pat:PartNumber pat:id='PN-00130'>10</pat:PartNumber> <pat:PartName pat:idref='PN-00131'>is held in each bit holder</pat:PartName> <pat:PartNumber pat:id='PN-00131'>70</pat:PartNumber>. In the present example, <pat:PartName pat:idref='PN-00132'>bit holders</pat:PartName> <pat:PartNumber pat:id='PN-00132'>70</pat:PartNumber> <pat:PartName pat:idref='PN-00133'>are welded directly onto milling drum</pat:PartName> <pat:PartNumber pat:id='PN-00133'>35</pat:PartNumber>. </pat:P><pat:P pat:pNumber="67" pat:id="p-67">[0061] It is also conceivable, however, to use the quick-change bit holder system according to FIG. 1, <pat:PartName pat:idref='PN-00134'>in which case base part</pat:PartName> <pat:PartNumber pat:id='PN-00134'>80</pat:PartNumber> <pat:PartName pat:idref='PN-00135'>is then welded onto milling drum</pat:PartName> <pat:PartNumber pat:id='PN-00135'>35</pat:PartNumber>. </pat:P><pat:P pat:pNumber="68" pat:id="p-68">[0062] An optical system, in which an elevation line of the drum surface is respectively surveyed in a kind of "scanning" operation, is used as an apparatus for surveying the bit contours. The measurement principle that can be used here is, for example, a triangulation method in which the drum surface is illuminated, for example, by a <pat:PartName pat:idref='PN-00136'>light source</pat:PartName> <pat:PartNumber pat:id='PN-00136'>50</pat:PartNumber>, for example a laser line. When the laser line thereby generated is observed by a <pat:PartName pat:idref='PN-00137'>camera</pat:PartName> <pat:PartNumber pat:id='PN-00137'>40</pat:PartNumber> at a different angle, elevation differences on the drum surface (caused, for example, <pat:PartName pat:idref='PN-00138'>by bits</pat:PartName> <pat:PartNumber pat:id='PN-00138'>10</pat:PartNumber>) are evident as shifts of these projection lines. If the <pat:PartName pat:idref='PN-00139'>angular difference between camera</pat:PartName> <pat:PartNumber pat:id='PN-00139'>40</pat:PartNumber> and <pat:PartName pat:idref='PN-00140'>light source</pat:PartName> <pat:PartNumber pat:id='PN-00140'>50</pat:PartNumber> is known, the elevation coordinates can be calculated. <pat:PartName pat:idref='PN-00141'>By rotating milling drum</pat:PartName> <pat:PartNumber pat:id='PN-00141'>35</pat:PartNumber> it is thus possible to create an elevation profile of the drum's enveloping surface, from which profile the contour line of the <pat:PartName pat:idref='PN-00142'>individual bits</pat:PartName> <pat:PartNumber pat:id='PN-00142'>10</pat:PartNumber> can then be read out. A further optical measurement principle for surveying the <pat:PartName pat:idref='PN-00143'>elevation and/or geometry of bits</pat:PartName> <pat:PartNumber pat:id='PN-00143'>10</pat:PartNumber> is the shadow-casting method according to FIG. 10. This method makes use of the <pat:PartName pat:idref='PN-00144'>fact that bits</pat:PartName> <pat:PartNumber pat:id='PN-00144'>10</pat:PartNumber> moving through a light curtain generated by a <pat:PartName pat:idref='PN-00145'>light source</pat:PartName> <pat:PartNumber pat:id='PN-00145'>50</pat:PartNumber> generate a shadow contour that can be observed and evaluated by a <pat:PartName pat:idref='PN-00146'>camera</pat:PartName> <pat:PartNumber pat:id='PN-00146'>40</pat:PartNumber>. The great advantage of this method lies in the fact that it is possible to work with a single camera row, in principle like a document scanner. This means that, in particular, <pat:PartName pat:idref='PN-00147'>even milling drums</pat:PartName> <pat:PartNumber pat:id='PN-00147'>35</pat:PartNumber> having a large diameter and high rotation speeds can be surveyed with sufficient resolution. </pat:P><pat:P pat:pNumber="69" pat:id="p-69"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>16</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='17'?><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData>[0063] The method described with reference to FIG. 10 can be modified in accordance with an alternative variant embodiment of the invention. Here once again a light curtain in the form of a light plane is generated using a <pat:PartName pat:idref='PN-00148'>light source</pat:PartName> <pat:PartNumber pat:id='PN-00148'>50</pat:PartNumber>. This light plane extends parallel to the <pat:PartName pat:idref='PN-00149'>longitudinal center axis of milling drum</pat:PartName> <pat:PartNumber pat:id='PN-00149'>35</pat:PartNumber> and tangentially to the drum surface. The light plane is configured so that in the case of a <pat:PartName pat:idref='PN-00150'>rotating milling drum</pat:PartName> <pat:PartNumber pat:id='PN-00150'>35</pat:PartNumber>, the <pat:PartName pat:idref='PN-00151'>tips of bits</pat:PartName> <pat:PartNumber pat:id='PN-00151'>10</pat:PartNumber> are the first to penetrate through the light plane. </pat:P><pat:P pat:pNumber="70" pat:id="p-70">[0064] They then cast a <pat:PartName pat:idref='PN-00152'>shadow that can be sensed by camera</pat:PartName> <pat:PartNumber pat:id='PN-00152'>40</pat:PartNumber>. <pat:PartName pat:idref='PN-00153'>Bits</pat:PartName> <pat:PartNumber pat:id='PN-00153'>10</pat:PartNumber> are guided through the light plane over a specific drum rotation angle until they then sink again below the light plane. </pat:P><pat:P pat:pNumber="71" pat:id="p-71">[0065] A <pat:PartName pat:idref='PN-00154'>reference measurement can be performed with unworn bits</pat:PartName> <pat:PartNumber pat:id='PN-00154'>10</pat:PartNumber>/bit <pat:PartName pat:idref='PN-00155'>holders</pat:PartName> <pat:PartNumber pat:id='PN-00155'>70</pat:PartNumber>. Here the <pat:PartName pat:idref='PN-00156'>time at which bit</pat:PartName> <pat:PartNumber pat:id='PN-00156'>10</pat:PartNumber> passes through the light plane (entry or exit) is sensed, and the a<pat:PartName pat:idref='PN-00157'>ssociated rotation angle of milling drum </pat:PartName> <pat:PartNumber pat:id='PN-00157'>35</pat:PartNumber> is sensed. After operational use, a corresponding measurement is then performed on the <pat:PartName pat:idref='PN-00158'>partially worn (worn out) bit</pat:PartName> <pat:PartNumber pat:id='PN-00158'>10</pat:PartNumber>. Because of the reduced length as compared with an unworn system, <pat:PartName pat:idref='PN-00159'>bit</pat:PartName> <pat:PartNumber pat:id='PN-00159'>10</pat:PartNumber> passes through the light plane at a later time, and sinks below it sooner. The <pat:PartName pat:idref='PN-00160'>corresponding rotation angle of milling drum</pat:PartName> <pat:PartNumber pat:id='PN-00160'>35</pat:PartNumber> can then be ascertained as a position value. These rotation angles are then compared with the rotation angles for the unworn system (reference value). A calculation of the wear state can then be made from the angle difference by differentiation, or the rotation angle difference is employed directly as a wear criterion. </pat:P><pat:P pat:pNumber="72" pat:id="p-72">[0066] During the milling process, for example in phases during which measurement does not occur, the measurement system is usefully stowed in a corresponding protective apparatus. If a <pat:PartName pat:idref='PN-00161'>second camera</pat:PartName> <pat:PartNumber pat:id='PN-00161'>40</pat:PartNumber> is used, for example, direct surveying of the elevation geometry can be performed without an additional illumination source. </pat:P><pat:P pat:pNumber="73" pat:id="p-73"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>17</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='18'?><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData>[0067] Alternatively, by correspondingly placing a second camera, additional measurements of the contours can be carried out so that the overall information density is increased and the detection probability for asymmetrical wear states is raised. </pat:P><pat:P pat:pNumber="74" pat:id="p-74">[0068] Alternatively, the <pat:PartName pat:idref='PN-00162'>position of bit tip</pat:PartName> <pat:PartNumber pat:id='PN-00162'>11</pat:PartNumber> or the location of the bit head contour can also be sensed in at least one step using other sensor equipment that measures distance (e.g. ultrasonic sensors, proximity switches). </pat:P><pat:P pat:pNumber="75" pat:id="p-75">[0069] As already explained in detail above, the following can be ascertained using the measurement methods described above: </pat:P><pat:P pat:pNumber="76" pat:id="p-76">1.    The current wear state V<pat:OCRConfidenceData pat:levelNumber='5'>,</pat:OCRConfidenceData>, V2, V3 of an <pat:PartName pat:idref='PN-00163'>earth working tool (bit</pat:PartName> <pat:PartNumber pat:id='PN-00163'>10</pat:PartNumber>), 2.    The wear resulting from comparison of a <pat:PartName pat:idref='PN-00164'>reference value (bit</pat:PartName> <pat:PartNumber pat:id='PN-00164'>10</pat:PartNumber> in the unworn or partially worn state) with the current wear state V<pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData>, V2, V3. </pat:P><pat:P pat:pNumber="77" pat:id="p-77">[0070] In order for the wear according to <pat:PartName pat:idref='PN-00165'>item</pat:PartName> <pat:PartNumber pat:id='PN-00165'>2</pat:PartNumber>. above to occur, the earth working machine must have produced a certain milling output. This milling output can be measured, for example as a number of tons milled (milled mass), as a milled volume, and/or as a milled distance, etc. The milling output can in particular be ascertained directly on an earth working machine. If the earth working machine is equipped with a measurement system described above, the <pat:PartName pat:idref='PN-00166'>wear (see</pat:PartName> <pat:PartNumber pat:id='PN-00166'>2</pat:PartNumber>.) can also be sensed directly and the characteristic value or values can be derived in conjunction with the ascertained milling output. </pat:P><pat:P pat:pNumber="78" pat:id="p-78">[0071] Based on the measured current wear state V<pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData>, V2, and with a knowledge of the <pat:PartName pat:idref='PN-00167'>wear limit V3 of bit</pat:PartName> <pat:PartNumber pat:id='PN-00167'>10</pat:PartNumber>, the <pat:PartName pat:idref='PN-00168'>residual wear capacity of bit</pat:PartName> <pat:PartNumber pat:id='PN-00168'>10</pat:PartNumber> can now be ascertained. For example, if the <pat:PartName pat:idref='PN-00169'>measured free end of bit tip</pat:PartName> <pat:PartNumber pat:id='PN-00169'>11</pat:PartNumber> according to FIG. 5 represents the current wear state constituting a position value, the distance to the reference contour R reproducing the wear state, and thus the residual wear length (Xges - X<pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData>), can thus be ascertained as the residual wear capacity by differentiating in the X axis direction. Additionally or alternatively, the residual wear capacity can be ascertained as the <pat:PartName pat:idref='PN-00170'>residual wear volume of bit tip</pat:PartName> <pat:PartNumber pat:id='PN-00170'>11</pat:PartNumber> remaining <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>18</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='19'?><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData>until the wear limit V3 is reached. This is done, for example (see discussion above of FIG. 4), by overlaying the measured wear state V<pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData>, V2 of the bit contour on the reference contour R in the worn state V3. The residual wear volume can then be ascertained by integration along the X axis. </pat:P><pat:P pat:pNumber="79" pat:id="p-79">[0072] The change in wear state is influenced by material properties, for example by the hardness and/or abrasiveness of the milled material. The material properties can be sensed indirectly. For example, samples can be taken (e.g. sample boring operations) in the area to be milled, and can be evaluated. </pat:P><pat:P pat:pNumber="80" pat:id="p-80">[0073] It is also conceivable to use existing mining category systems. General hardness and abrasiveness categories are defined for mines (e.g. <pat:OCRConfidenceData pat:levelNumber='5'>"</pat:OCRConfidenceData>hard, non-abrasive,<pat:OCRConfidenceData pat:levelNumber='6'>"</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='6'>"</pat:OCRConfidenceData>moderate, non- abrasive,<pat:OCRConfidenceData pat:levelNumber='6'>"</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='6'>"</pat:OCRConfidenceData>soft, abrasive,<pat:OCRConfidenceData pat:levelNumber='5'>"</pat:OCRConfidenceData> etc.). From these categories, the category matching the planned route of travel can be selected. </pat:P><pat:P pat:pNumber="81" pat:id="p-81">[0074] The material properties can also be ascertained by evaluating machine data (e.g. rotation speed of the milling drum, torque, advance, and milling depth), since the material properties correlate directly with these machine data. </pat:P><pat:P pat:pNumber="82" pat:id="p-82">[0075] Characteristic values can be ascertained as a function of the milling output and/or the material properties. These characteristic values indicate the change in the wear state which is to be expected for a specific milling output and/or for predefined material properties. </pat:P><pat:P pat:pNumber="83" pat:id="p-83">[0076] Based on the residual wear capacity and in consideration of one or more characteristic values, the remaining working output can then be signaled to the machine operator. He can be informed, for example, as to the milling output that can still be produced (e.g. mass or volume of material that can still be milled, number of truckloads that can still be milled, travel distance that can be milled, or milling time). </pat:P><pat:P pat:pNumber="84" pat:id="p-84"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>19</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='20'?><pat:BoundaryData><pat:HeaderText>012826 (J/0632)</pat:HeaderText></pat:BoundaryData>[0077] If the milling output per unit time for an earth working machine is known, it is also possible in particular to indicate the time remaining until the next tool change. The milling output per unit time can be continuously ascertained on the basis of current machine parameters (advance, milling depth). It can also be previously known based on milling work already carried out at the same location. </pat:P><pat:P pat:pNumber="85" pat:id="p-85">[0078] FIG. 11 illustrates a milling area F, for example a mine, <pat:PartName pat:idref='PN-00171'>in which multiple milling machines</pat:PartName> <pat:PartNumber pat:id='PN-00171'>30</pat:PartNumber> are working. Milling area F contains a raw material deposit, and the material properties change in sub-areas F<pat:OCRConfidenceData pat:levelNumber='5'>,</pat:OCRConfidenceData>, F2, F3. </pat:P><pat:P pat:pNumber="86" pat:id="p-86">[0079] These sub-areas F<pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData>, F2, F3 are associated in mine maps with hardness and abrasion categories (see above). Before work begins, the measurement system (for example, <pat:PartName pat:idref='PN-00172'>camera</pat:PartName> <pat:PartNumber pat:id='PN-00172'>40</pat:PartNumber>) ascertains the current wear state V<pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData>, V2 and conveys this, as well as the current position of the machine, via a transmission and <pat:PartName pat:idref='PN-00173'>reception apparatus</pat:PartName> <pat:PartNumber pat:id='PN-00173'>61</pat:PartNumber> to an <pat:PartName pat:idref='PN-00174'>external system unit</pat:PartName> <pat:PartNumber pat:id='PN-00174'>60</pat:PartNumber>. There, in consideration of the calculated residual wear capacity and of one or more characteristic values, the remaining milling output until the wear limit V3 is reached is ascertained. The characteristic value ideally takes into account the planned route of travel and the various hardness and abrasion categories, associated therewith, in sub-areas F<pat:OCRConfidenceData pat:levelNumber='5'>,</pat:OCRConfidenceData>, F2, F3, as well as the expected wear related to the hardness and abrasion categories. The ascertained working output until the wear limit V3 is reached is signaled back to <pat:PartName pat:idref='PN-00175'>milling machine</pat:PartName> <pat:PartNumber pat:id='PN-00175'>30</pat:PartNumber>. </pat:P><pat:P pat:pNumber="87" pat:id="p-87">[0080] <pat:PartName pat:idref='PN-00176'>Milling machine</pat:PartName> <pat:PartNumber pat:id='PN-00176'>30</pat:PartNumber> depicted on the right in FIG. 11 has already traveled over sub- areas F<pat:OCRConfidenceData pat:levelNumber='5'>1</pat:OCRConfidenceData> and F2 and has acquired measured values in that context. These measured values can be evaluated. For example, it is possible to sense what kind of wear occurs with what milling output. This result, or the characteristic values resulting therefrom, can then be respectively made available to the second milling machine in FIG. 11 in order to improve the quality of the wear prognosis. </pat:P><pat:P pat:pNumber="88" pat:id="p-88"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='88'>20</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='21'?><pat:OCRConfidenceData pat:levelNumber='88'>21</pat:OCRConfidenceData> </pat:P></pat:Specification></pat:SpecificationDocument>

applicant/14873627.xml

@@ -0,0 +1,107 @@
+<?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="14873627.10-02-2015.IFA0A45TPXXIFW3.SPEC.xml" pat:id="IFA0A45TPXXIFW3" 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>14873627</pat:ApplicationNumber></pat:ApplicationHeaderDetails>
+<pat:AttorneyDocketNumber>Attorney Docket No. 10033.025100</pat:AttorneyDocketNumber>
+<pat:PageTotalQuantity>14</pat:PageTotalQuantity>
+<pat:ParagraphTotalQuantity>56</pat:ParagraphTotalQuantity>
+</pat:DocumentHeaderDetails>
+<pat:MailRoomDate>2015-10-02</pat:MailRoomDate>
+<pat:Specification pat:id="Specification">
+<?PageStart number="1"?>
+<pat:BoundaryData><pat:HeaderText>Attorney Docket No. 10033.025100</pat:HeaderText></pat:BoundaryData>
+<pat:Heading pat:id="h-1">DETECTION OF ADVANCED PERSISTENT THREAT ATTACK ON A</pat:Heading>
+<pat:Heading pat:id="h-2">PRIVATE COMPUTER NETWORK</pat:Heading>
+<pat:P pat:id="p-1" pat:pNumber="1">Inventors: Li-Hsiang CHIU, Wei-Ching CHANG, and Shih-Hao WENG <pat:BoundaryData><pat:LineNumber>5   </pat:LineNumber></pat:BoundaryData></pat:P>
+<pat:Heading pat:id="h-3"><pat:U>BACKGROUND OF THE INVENTION</pat:U></pat:Heading>
+<pat:Heading pat:id="h-4">1.   Field of the Invention</pat:Heading>
+<pat:P pat:id="p-2" pat:pNumber="2">The present invention relates generally to computer security, and more particularly but not exclusively to methods and apparatus for detecting advanced persistent threats.</pat:P>
+<pat:P pat:id="p-3" pat:pNumber="3"><pat:BoundaryData><pat:LineNumber>10  </pat:LineNumber></pat:BoundaryData>2.    Description of the Background Art Advanced persistent threat (APT) is a type of cyber attack that is tailored to a particular target, which is typically an organization, such as a business or government.</pat:P>
+<pat:P pat:id="p-4" pat:pNumber="4">Compared to mass attacks, an APT attack is very sophisticated and typically includes several stages. First, the attacker performs information gathering on the target. From <pat:BoundaryData><pat:LineNumber>15  </pat:LineNumber></pat:BoundaryData>the gathered information, the attacker identifies a vulnerability to gain entry into the target's computer network and create a back door that allows communication with an APT command and control server. The attacker then roams the network to obtain higher level permissions (e.g., passwords to critical assets) and to find confidential data, such as intellectual property data, financial data, personally identifiable information, etc.</pat:P>
+<pat:P pat:id="p-5" pat:pNumber="5"><pat:BoundaryData><pat:LineNumber>20   </pat:LineNumber></pat:BoundaryData>The attacker transfers the confidential data out of the target's computer network and may even cover his tracks, such as by deleting programs used to perpetrate the APT attack.</pat:P>
+<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="888">-1-</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>
+<pat:P pat:id="p-6" pat:pNumber="6">
+<?PageStart number="2"?></pat:P>
+<pat:BoundaryData><pat:HeaderText>Attorney Docket No. 10033.025100</pat:HeaderText></pat:BoundaryData>
+<pat:Heading pat:id="h-5"><pat:U>SUMMARY</pat:U></pat:Heading>
+<pat:P pat:id="p-7" pat:pNumber="7">In one embodiment, a system for detecting an advanced persistent threat (APT) attack on a private computer network includes hosts computers that receive network traffic and process the network traffic to identify an access event that indicates access <pat:BoundaryData><pat:LineNumber>5   </pat:LineNumber></pat:BoundaryData>to a critical asset of an organization that owns or maintains the private computer network. The critical asset may be a computer that stores confidential data of the organization. Access events may be stored in an event log as event data. Access events indicated in the event log may be correlated using a set of alert rules to identify an APT attack.</pat:P>
+<pat:P pat:id="p-8" pat:pNumber="8"><pat:BoundaryData><pat:LineNumber>10        </pat:LineNumber></pat:BoundaryData>These and other features of the present invention will be readily apparent to persons of ordinary skill in the art upon reading the entirety of this disclosure, which includes the accompanying drawings and claims.</pat:P>
+<pat:Heading pat:id="h-6"><pat:U>DESCRIPTION OF THE DRAWINGS</pat:U></pat:Heading>
+<pat:P pat:id="p-9" pat:pNumber="9"><pat:BoundaryData><pat:LineNumber>15        </pat:LineNumber></pat:BoundaryData>FIG. <pat:OCRConfidenceData pat:levelNumber="5">1</pat:OCRConfidenceData> shows a block diagram of a computer that may be employed with embodiments of the present invention.</pat:P>
+<pat:P pat:id="p-10" pat:pNumber="10">FIGS. 2 <pat:PartName pat:idref="PN-00001">and </pat:PartName><pat:PartNumber pat:id="PN-00001">3</pat:PartNumber> show block diagrams of a system for detecting an APT attack on a private computer network in accordance with embodiments of the present invention.</pat:P>
+<pat:P pat:id="p-11" pat:pNumber="11">FIG. 4 shows a flow diagram of a method of detecting an APT attack on a private <pat:BoundaryData><pat:LineNumber>20  </pat:LineNumber></pat:BoundaryData>computer network in accordance with an embodiment of the present invention.</pat:P>
+<pat:P pat:id="p-12" pat:pNumber="12">FIGS. 5-7 show example event data that may be logged and transmitted by a network sensor, in accordance with an embodiment of the present invention.</pat:P>
+<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="888">-2-</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>
+<pat:P pat:id="p-13" pat:pNumber="13">
+<?PageStart number="3"?></pat:P>
+<pat:BoundaryData><pat:HeaderText>Attorney Docket No. 10033.025100</pat:HeaderText></pat:BoundaryData>
+<pat:P pat:id="p-14" pat:pNumber="14">FIG. 8 shows an example pseudo code for a rule that may be used by a correlator to detect successful logins that may indicate lateral movement of an APT attack, in accordance with an embodiment of the present invention.</pat:P>
+<pat:P pat:id="p-15" pat:pNumber="15">The use of the same reference label in different drawings indicates the same or <pat:BoundaryData><pat:LineNumber>5   </pat:LineNumber></pat:BoundaryData>like components.</pat:P>
+<pat:Heading pat:id="h-7"><pat:U>DETAILED DESCRIPTION</pat:U></pat:Heading>
+<pat:P pat:id="p-16" pat:pNumber="16">In the present disclosure, numerous specific details are provided, such as examples of apparatus, components, and methods, to provide a thorough <pat:BoundaryData><pat:LineNumber>10   </pat:LineNumber></pat:BoundaryData>understanding of embodiments of the invention. Persons of ordinary skill in the art will recognize, however, that the invention can be practiced without one or more of the specific details. In other instances, well-known details are not shown or described to avoid obscuring aspects of the invention.</pat:P>
+<pat:P pat:id="p-17" pat:pNumber="17">The inventors believe that traditional solutions for detecting network intrusions <pat:BoundaryData><pat:LineNumber>15  </pat:LineNumber></pat:BoundaryData>and ma<pat:OCRConfidenceData pat:levelNumber="5">l</pat:OCRConfidenceData>ware (e.g., computer viruses, Trojans, worms) are ineffective against APT attacks because an APT attack typically involves activities that at a glance appear to be normal. As a particular example, an APT attack may be initiated by sending a so-called <pat:OCRConfidenceData pat:levelNumber="5">"</pat:OCRConfidenceData>spear fishing email<pat:OCRConfidenceData pat:levelNumber="5">"</pat:OCRConfidenceData> that targets low-level personnel who have access to the network.</pat:P>
+<pat:P pat:id="p-18" pat:pNumber="18">The spear phishing email may allow the attacker, i.e., cybercriminal or software <pat:BoundaryData><pat:LineNumber>20   </pat:LineNumber></pat:BoundaryData>perpetrating the APT attack, only limited access to the network using the credentials of low-level personnel. However, once on the network, the attacker may roam the network to find credentials of higher-level personnel and discover network paths to other <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="888">-3-</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>
+<?PageStart number="4"?><pat:BoundaryData><pat:HeaderText>Attorney Docket No. 10033.025100</pat:HeaderText></pat:BoundaryData>computers on the network. This stage of the APT attack is also referred to as "lateral movement" and is relatively difficult to detect because the corresponding network activity of the attacker appears to be normal or authorized. The following stage of the APT attack where the attacker looks for sensitive data, which is referred to as "data <pat:BoundaryData><pat:LineNumber>5   </pat:LineNumber></pat:BoundaryData>discovery", is also relatively difficult to detect for the same reason.</pat:P>
+<pat:P pat:id="p-19" pat:pNumber="19">Referring now to FIG. 1, there is shown a block diagram of a <pat:PartName pat:idref="PN-00002">computer </pat:PartName><pat:PartNumber pat:id="PN-00002">100</pat:PartNumber> that may be employed with embodiments of the present invention. The <pat:PartName pat:idref="PN-00003">computer </pat:PartName><pat:PartNumber pat:id="PN-00003">100</pat:PartNumber> may be employed as a server computer, a client computer, and other computers described below. The <pat:PartName pat:idref="PN-00004">computer </pat:PartName><pat:PartNumber pat:id="PN-00004">100</pat:PartNumber> may have fewer or more components to meet the needs of a <pat:BoundaryData><pat:LineNumber>10  </pat:LineNumber></pat:BoundaryData>particular application. The <pat:PartName pat:idref="PN-00005">computer </pat:PartName><pat:PartNumber pat:id="PN-00005">100</pat:PartNumber> <pat:PartName pat:idref="PN-00006">may include one or more processors </pat:PartName><pat:PartNumber pat:id="PN-00006">101</pat:PartNumber>.</pat:P>
+<pat:P pat:id="p-20" pat:pNumber="20">The computer 100 <pat:PartName pat:idref="PN-00007">may have one or more buses </pat:PartName><pat:PartNumber pat:id="PN-00007">103</pat:PartNumber> coupling its various components.</pat:P>
+<pat:P pat:id="p-21" pat:pNumber="21">The computer 100 <pat:PartName pat:idref="PN-00008">may include one or more user input devices </pat:PartName><pat:PartNumber pat:id="PN-00008">102</pat:PartNumber> (e.g., <pat:PartName pat:idref="PN-00009">keyboard, mouse), one or more data storage devices </pat:PartName><pat:PartNumber pat:id="PN-00009">106</pat:PartNumber> (e.g., hard drive, optical disk, Universal Serial Bus memory), a <pat:PartName pat:idref="PN-00010">display monitor </pat:PartName><pat:PartNumber pat:id="PN-00010">104</pat:PartNumber> (e.g., liquid crystal display, flat panel <pat:BoundaryData><pat:LineNumber>15   </pat:LineNumber></pat:BoundaryData>monitor), a <pat:PartName pat:idref="PN-00011">computer network interface </pat:PartName><pat:PartNumber pat:id="PN-00011">105</pat:PartNumber> (e.g., network adapter, modem), and a <pat:PartName pat:idref="PN-00012">main memory </pat:PartName><pat:PartNumber pat:id="PN-00012">108</pat:PartNumber> (e.g., random access memory). The <pat:PartName pat:idref="PN-00013">computer network interface </pat:PartName><pat:PartNumber pat:id="PN-00013">105</pat:PartNumber> may be coupled to a <pat:PartName pat:idref="PN-00014">computer network </pat:PartName><pat:PartNumber pat:id="PN-00014">109</pat:PartNumber>, which in this example includes the Internet.</pat:P>
+<pat:P pat:id="p-22" pat:pNumber="22">The computer 100 is a <pat:PartName pat:idref="PN-00015">particular machine as programmed with software modules </pat:PartName><pat:PartNumber pat:id="PN-00015">110</pat:PartNumber>. The <pat:PartName pat:idref="PN-00016">software modules </pat:PartName><pat:PartNumber pat:id="PN-00016">110</pat:PartNumber> comprise computer-readable program code stored <pat:BoundaryData><pat:LineNumber>20   </pat:LineNumber></pat:BoundaryData>non-transitory in the <pat:PartName pat:idref="PN-00017">main memory </pat:PartName><pat:PartNumber pat:id="PN-00017">108</pat:PartNumber> for execution by the <pat:PartName pat:idref="PN-00018">processor </pat:PartName><pat:PartNumber pat:id="PN-00018">101</pat:PartNumber>. As an example, the <pat:PartName pat:idref="PN-00019">software modules </pat:PartName><pat:PartNumber pat:id="PN-00019">110</pat:PartNumber> may comprise software modules for detecting an APT attack when the <pat:PartName pat:idref="PN-00020">computer </pat:PartName><pat:PartNumber pat:id="PN-00020">100</pat:PartNumber> is employed as an APT detection server.</pat:P>
+<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="888">-4-</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>
+<pat:P pat:id="p-23" pat:pNumber="23">
+<?PageStart number="5"?></pat:P>
+<pat:BoundaryData><pat:HeaderText>Attorney Docket No. 10033.025100</pat:HeaderText></pat:BoundaryData>
+<pat:P pat:id="p-24" pat:pNumber="24">The computer 100 may be configured to perform its functions by executing the <pat:PartName pat:idref="PN-00021">software modules </pat:PartName><pat:PartNumber pat:id="PN-00021">110</pat:PartNumber>. The <pat:PartName pat:idref="PN-00022">software modules </pat:PartName><pat:PartNumber pat:id="PN-00022">110</pat:PartNumber> may be loaded from the <pat:PartName pat:idref="PN-00023">data storage device </pat:PartName><pat:PartNumber pat:id="PN-00023">106</pat:PartNumber> to the <pat:PartName pat:idref="PN-00024">main memory </pat:PartName><pat:PartNumber pat:id="PN-00024">108</pat:PartNumber>. An article of manufacture may be embodied as computer-readable storage medium including instructions that when <pat:BoundaryData><pat:LineNumber>5   </pat:LineNumber></pat:BoundaryData>executed by the <pat:PartName pat:idref="PN-00025">computer </pat:PartName><pat:PartNumber pat:id="PN-00025">100</pat:PartNumber> causes the <pat:PartName pat:idref="PN-00026">computer </pat:PartName><pat:PartNumber pat:id="PN-00026">100</pat:PartNumber> to be operable to perform the functions of the <pat:PartName pat:idref="PN-00027">software modules </pat:PartName><pat:PartNumber pat:id="PN-00027">110</pat:PartNumber>.</pat:P>
+<pat:P pat:id="p-25" pat:pNumber="25">FIG. 2 shows a block diagram of a system for detecting an APT attack on a private computer network in accordance with an embodiment of the present invention.</pat:P>
+<pat:P pat:id="p-26" pat:pNumber="26">In the example of FIG. 2, the system is deployed in a private computer network, such as <pat:BoundaryData><pat:LineNumber>10  </pat:LineNumber></pat:BoundaryData>that of a large or small organization. For example, the private computer network may be an enterprise network of a small business, large corporation, or a government. In the example of FIG. 2, the <pat:PartName pat:idref="PN-00028">private computer network comprises one or more servers </pat:PartName><pat:PartNumber pat:id="PN-00028">130</pat:PartNumber> (i.e., <pat:PartName pat:idref="PN-00029">130-1, 130-2, 130-3, etc.), one or more client computers </pat:PartName><pat:PartNumber pat:id="PN-00029">132</pat:PartNumber> (i.e., <pat:PartName pat:idref="PN-00030">132-1, 132- </pat:PartName><pat:PartNumber pat:id="PN-00030">2</pat:PartNumber>, etc.), a <pat:PartName pat:idref="PN-00031">router </pat:PartName><pat:PartNumber pat:id="PN-00031">133</pat:PartNumber>, and a <pat:PartName pat:idref="PN-00032">gateway </pat:PartName><pat:PartNumber pat:id="PN-00032">134</pat:PartNumber>. As can be appreciated, a server may <pat:BoundaryData><pat:LineNumber>15  </pat:LineNumber></pat:BoundaryData>comprise one or more computers, and a client computer may comprise a personal computer of a user. A personal computer may comprise a desktop computer, a laptop computer, a tablet, or other user computer. The private computer network may include fewer or more computer devices depending on the size of the network.</pat:P>
+<pat:P pat:id="p-27" pat:pNumber="27">In the example of FIG. 2, a <pat:PartName pat:idref="PN-00033">gateway </pat:PartName><pat:PartNumber pat:id="PN-00033">134</pat:PartNumber> comprises a computer that provides <pat:BoundaryData><pat:LineNumber>20   </pat:LineNumber></pat:BoundaryData>gateway/firewall functionality for the private computer network. In one embodiment, data that are transferred between computers on the private computer network and computers on the Internet (e.g., <pat:PartName pat:idref="PN-00034">computers </pat:PartName><pat:PartNumber pat:id="PN-00034">160)</pat:PartNumber> go through the <pat:PartName pat:idref="PN-00035">gateway </pat:PartName><pat:PartNumber pat:id="PN-00035">134</pat:PartNumber>. The <pat:PartName pat:idref="PN-00036">gateway </pat:PartName><pat:PartNumber pat:id="PN-00036">134</pat:PartNumber> may include conventional computer security modules, including an <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="888">-5-</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>
+<?PageStart number="6"?><pat:BoundaryData><pat:HeaderText>Attorney Docket No. 10033.025100</pat:HeaderText></pat:BoundaryData>antivirus program, an antispam program, etc. However, as previously noted, conventional computer security modules are largely ineffective against APT attacks.</pat:P>
+<pat:P pat:id="p-28" pat:pNumber="28">In the example of FIG. 2, the system for detecting an APT attack on the private computer network comprises an <pat:PartName pat:idref="PN-00037">APT detection server </pat:PartName><pat:PartNumber pat:id="PN-00037">140</pat:PartNumber> and one or more computers <pat:BoundaryData><pat:LineNumber>5  </pat:LineNumber></pat:BoundaryData>that host a <pat:PartName pat:idref="PN-00038">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00038">131</pat:PartNumber>. In the example of FIG. 2, a <pat:PartName pat:idref="PN-00039">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00039">131</pat:PartNumber> may comprise computer-readable program code that is hosted (i.e., running) on a <pat:PartName pat:idref="PN-00040">server </pat:PartName><pat:PartNumber pat:id="PN-00040">130</pat:PartNumber>, a <pat:PartName pat:idref="PN-00041">client computer </pat:PartName><pat:PartNumber pat:id="PN-00041">132</pat:PartNumber>, a <pat:PartName pat:idref="PN-00042">router </pat:PartName><pat:PartNumber pat:id="PN-00042">133</pat:PartNumber>, or other computer device on the private computer network.</pat:P>
+<pat:P pat:id="p-29" pat:pNumber="29">In one embodiment, a <pat:PartName pat:idref="PN-00043">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00043">131</pat:PartNumber> is configured to receive network <pat:BoundaryData><pat:LineNumber>10  </pat:LineNumber></pat:BoundaryData>traffic, parse the network traffic for event data that indicates access events involving critical assets, and forward the event data to the <pat:PartName pat:idref="PN-00044">APT detection server </pat:PartName><pat:PartNumber pat:id="PN-00044">140</pat:PartNumber>. The critical assets may comprise computers that store confidential data, such as servers that contain intellectual property data and personal computers of high-level personnel (e.g., president, network administrator, chief technical officer). For example, a <pat:BoundaryData><pat:LineNumber>15  </pat:LineNumber></pat:BoundaryData><pat:PartName pat:idref="PN-00045">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00045">131</pat:PartNumber> may receive network packets and parse the network packets to identify network packets having destination and/or origin (i.e., sending) addresses of critical assets. The <pat:PartName pat:idref="PN-00046">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00046">131</pat:PartNumber> may forward to the <pat:PartName pat:idref="PN-00047">APT detection server </pat:PartName><pat:PartNumber pat:id="PN-00047">140</pat:PartNumber> the identified network packets along with other related information, such as timestamps, routing information, etc., as event data. In one embodiment, the <pat:PartName pat:idref="PN-00048">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00048">131</pat:PartNumber> <pat:BoundaryData><pat:LineNumber>20   </pat:LineNumber></pat:BoundaryData>may provide the event data in a format that may be readily stored in and read from an event log.</pat:P>
+<pat:P pat:id="p-30" pat:pNumber="30">In one embodiment, the <pat:PartName pat:idref="PN-00049">APT detection server </pat:PartName><pat:PartNumber pat:id="PN-00049">140</pat:PartNumber> <pat:PartName pat:idref="PN-00050">comprises one or more computers that receive event data from network sensors </pat:PartName><pat:PartNumber pat:id="PN-00050">131</pat:PartNumber>, process the event data to <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="888">-6-</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>
+<?PageStart number="7"?><pat:BoundaryData><pat:HeaderText>Attorney Docket No. 10033.025100</pat:HeaderText></pat:BoundaryData>adjust a set of alert rules, and to correlate the event data using the set of alert rules to identify an APT attack. In the example of FIG. 2, the <pat:PartName pat:idref="PN-00051">APT detection server </pat:PartName><pat:PartNumber pat:id="PN-00051">140</pat:PartNumber> is deployed on-premise within the private computer network. The <pat:PartName pat:idref="PN-00052">APT detection server </pat:PartName><pat:PartNumber pat:id="PN-00052">140</pat:PartNumber> may also be deployed outside the private computer network. For example, as <pat:BoundaryData><pat:LineNumber>5   </pat:LineNumber></pat:BoundaryData>shown in FIG. 3, the <pat:PartName pat:idref="PN-00053">APT detection server </pat:PartName><pat:PartNumber pat:id="PN-00053">140</pat:PartNumber> may be deployed on the Internet. In that case, the <pat:PartName pat:idref="PN-00054">sensors </pat:PartName><pat:PartNumber pat:id="PN-00054">131</pat:PartNumber> may provide event data to the <pat:PartName pat:idref="PN-00055">APT detection server </pat:PartName><pat:PartNumber pat:id="PN-00055">140</pat:PartNumber> over the Internet. FIGS. 2 <pat:PartName pat:idref="PN-00056">and </pat:PartName><pat:PartNumber pat:id="PN-00056">3</pat:PartNumber> show the same network except for the location of the <pat:PartName pat:idref="PN-00057">APT detection server </pat:PartName><pat:PartNumber pat:id="PN-00057">140</pat:PartNumber>.</pat:P>
+<pat:P pat:id="p-31" pat:pNumber="31">FIG. 4 shows a flow diagram of a method of detecting an APT attack on a private <pat:BoundaryData><pat:LineNumber>10  </pat:LineNumber></pat:BoundaryData>computer network in accordance with an embodiment of the present invention. The flow diagram of FIG. 4 is explained using the components of the systems of FIGS. 2 <pat:PartName pat:idref="PN-00058">and </pat:PartName><pat:PartNumber pat:id="PN-00058">3</pat:PartNumber>.</pat:P>
+<pat:P pat:id="p-32" pat:pNumber="32">In the example of FIG. 4, a <pat:PartName pat:idref="PN-00059">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00059">131</pat:PartNumber> is hosted by a computer, such as a <pat:PartName pat:idref="PN-00060">client computer </pat:PartName><pat:PartNumber pat:id="PN-00060">132</pat:PartNumber>, a <pat:PartName pat:idref="PN-00061">server </pat:PartName><pat:PartNumber pat:id="PN-00061">130</pat:PartNumber>, a <pat:PartName pat:idref="PN-00062">router </pat:PartName><pat:PartNumber pat:id="PN-00062">133</pat:PartNumber> or other computer on the <pat:PartName pat:idref="PN-00063">private computer network. Only one network sensor </pat:PartName><pat:PartNumber pat:id="PN-00063">131</pat:PartNumber> is shown in FIG. 4 for clarity of <pat:BoundaryData><pat:LineNumber>15  </pat:LineNumber></pat:BoundaryData>illustration. It is to be noted that in a typical deployment, there is a <pat:PartName pat:idref="PN-00064">plurality of network sensors </pat:PartName><pat:PartNumber pat:id="PN-00064">131</pat:PartNumber> on the private computer network.</pat:P>
+<pat:P pat:id="p-33" pat:pNumber="33">In the example of FIG. 4, the <pat:PartName pat:idref="PN-00065">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00065">131</pat:PartNumber> monitors and receives network traffic on the <pat:PartName pat:idref="PN-00066">private computer network (see arrow </pat:PartName><pat:PartNumber pat:id="PN-00066">301)</pat:PartNumber> and processes the network traffic to identify events involving access to critical assets on the private computer <pat:BoundaryData><pat:LineNumber>20   </pat:LineNumber></pat:BoundaryData>network. The <pat:PartName pat:idref="PN-00067">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00067">131</pat:PartNumber> may communicate with remote services, such as a web reputation service, file reputation service, etc. to add additional information to data obtained from received network traffic.</pat:P>
+<pat:BoundaryData><pat:HeaderText>-7-</pat:HeaderText></pat:BoundaryData>
+<pat:P pat:id="p-34" pat:pNumber="34">
+<?PageStart number="8"?></pat:P>
+<pat:BoundaryData><pat:HeaderText>Atto<pat:OCRConfidenceData pat:levelNumber="66">rn</pat:OCRConfidenceData>ey Docket No. 10033.025100</pat:HeaderText></pat:BoundaryData>
+<pat:P pat:id="p-35" pat:pNumber="35">The network sensor 131 may be running on a file server computer that is designated as a critical asset. In that example, the <pat:PartName pat:idref="PN-00068">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00068">131</pat:PartNumber> may monitor and record access to the file server computer. As another example, the <pat:PartName pat:idref="PN-00069">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00069">131</pat:PartNumber> may be running on a router 133; in that case the <pat:PartName pat:idref="PN-00070">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00070">131</pat:PartNumber> may parse <pat:BoundaryData><pat:LineNumber>5   </pat:LineNumber></pat:BoundaryData>network packets passing through the <pat:PartName pat:idref="PN-00071">router </pat:PartName><pat:PartNumber pat:id="PN-00071">133</pat:PartNumber> to identify events involving access to critical assets. The <pat:PartName pat:idref="PN-00072">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00072">131</pat:PartNumber> may format identified events into event data, which the <pat:PartName pat:idref="PN-00073">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00073">131</pat:PartNumber> transmits to the <pat:PartName pat:idref="PN-00074">APT detection server </pat:PartName><pat:PartNumber pat:id="PN-00074">140</pat:PartNumber> (see arrow</pat:P>
+<pat:Heading pat:id="h-8">302).</pat:Heading>
+<pat:P pat:id="p-36" pat:pNumber="36">FIGS. 5-7 show example event data that may be logged and transmitted by the <pat:BoundaryData><pat:LineNumber>10  </pat:LineNumber></pat:BoundaryData><pat:PartName pat:idref="PN-00075">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00075">131</pat:PartNumber>. In the example of FIG. 5, the event data indicate, among other information, a file ("fileName") transmitted by a sending host ("shost") to a destination host ("dhost"), the MAC addresses of the destination ("dmac") and sending ("smac") hosts, and unique ID of the sending host ("suid"). In particular, the even data indicate an event involving a sending host that is identified as "HP6200P" ("suid: HP6200P"). In <pat:BoundaryData><pat:LineNumber>15  </pat:LineNumber></pat:BoundaryData>the example of FIG. 6, the event data identify the same sending host ("suid: HP6200P") as sending malware ("malName: TROJ_SMALL.CPE"). In the example of FIG. 7, the event data identify a successful login by a sending host with an <pat:OCRConfidenceData pat:levelNumber="5">I</pat:OCRConfidenceData>P address of 10.235.3.4 ("endpoint<pat:OCRConfidenceData pat:levelNumber="4">l</pat:OCRConfidenceData>P), which is the same as that involved with the sending host identified in the event data shown in FIGS. 5 <pat:PartName pat:idref="PN-00076">and </pat:PartName><pat:PartNumber pat:id="PN-00076">6</pat:PartNumber>. The examples of FIGS. 5-7 <pat:BoundaryData><pat:LineNumber>20  </pat:LineNumber></pat:BoundaryData>illustrate example data that may be collected by a <pat:PartName pat:idref="PN-00077">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00077">131</pat:PartNumber>. The data to be collected and monitored may be varied depending on the particulars of the APT detection system being implemented.</pat:P>
+<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="888">-8-</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>
+<pat:P pat:id="p-37" pat:pNumber="37">
+<?PageStart number="9"?></pat:P>
+<pat:BoundaryData><pat:HeaderText>Attorney Docket No. 10033.025100</pat:HeaderText></pat:BoundaryData>
+<pat:P pat:id="p-38" pat:pNumber="38">Continuing with FIG. 4, the <pat:PartName pat:idref="PN-00078">APT detection server </pat:PartName><pat:PartNumber pat:id="PN-00078">140</pat:PartNumber> may be deployed on- premise within the private computer network, in which case the <pat:PartName pat:idref="PN-00079">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00079">131</pat:PartNumber> transmits the event data to the <pat:PartName pat:idref="PN-00080">APT detection server </pat:PartName><pat:PartNumber pat:id="PN-00080">140</pat:PartNumber> over the private computer network. In other embodiments, the <pat:PartName pat:idref="PN-00081">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00081">131</pat:PartNumber> transmits the event data to an <pat:BoundaryData><pat:LineNumber>5  </pat:LineNumber></pat:BoundaryData><pat:PartName pat:idref="PN-00082">APT detection server </pat:PartName><pat:PartNumber pat:id="PN-00082">140</pat:PartNumber> that is deployed "in the cloud", i.e., on the Internet. In that case, the <pat:PartName pat:idref="PN-00083">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00083">131</pat:PartNumber> transmits the event data to the <pat:PartName pat:idref="PN-00084">APT detection server </pat:PartName><pat:PartNumber pat:id="PN-00084">140</pat:PartNumber> over the Internet through the <pat:PartName pat:idref="PN-00085">gateway </pat:PartName><pat:PartNumber pat:id="PN-00085">134</pat:PartNumber>.</pat:P>
+<pat:P pat:id="p-39" pat:pNumber="39">In one embodiment, the <pat:PartName pat:idref="PN-00086">APT detection server </pat:PartName><pat:PartNumber pat:id="PN-00086">140</pat:PartNumber> comprises an <pat:PartName pat:idref="PN-00087">event log </pat:PartName><pat:PartNumber pat:id="PN-00087">331</pat:PartNumber>, an <pat:PartName pat:idref="PN-00088">adjustment module </pat:PartName><pat:PartNumber pat:id="PN-00088">332</pat:PartNumber>, a <pat:PartName pat:idref="PN-00089">set of alert rules </pat:PartName><pat:PartNumber pat:id="PN-00089">334</pat:PartNumber>, and a <pat:PartName pat:idref="PN-00090">correlator </pat:PartName><pat:PartNumber pat:id="PN-00090">335</pat:PartNumber>. In the <pat:BoundaryData><pat:LineNumber>10  </pat:LineNumber></pat:BoundaryData>example of FIG. 4, the <pat:PartName pat:idref="PN-00091">APT detection server </pat:PartName><pat:PartNumber pat:id="PN-00091">140</pat:PartNumber> receives and stores event data in an <pat:PartName pat:idref="PN-00092">event log </pat:PartName><pat:PartNumber pat:id="PN-00092">331</pat:PartNumber> (see arrow 302). The <pat:PartName pat:idref="PN-00093">event log </pat:PartName><pat:PartNumber pat:id="PN-00093">331</pat:PartNumber> may comprise a database or other listing of event data.</pat:P>
+<pat:P pat:id="p-40" pat:pNumber="40">In one embodiment, the <pat:PartName pat:idref="PN-00094">adjustment module </pat:PartName><pat:PartNumber pat:id="PN-00094">332</pat:PartNumber> comprises one or more software- or hardware- based tools for reading, viewing, and extracting parameter data <pat:BoundaryData><pat:LineNumber>15  </pat:LineNumber></pat:BoundaryData>for one or more rules of the <pat:PartName pat:idref="PN-00095">set of alert rules </pat:PartName><pat:PartNumber pat:id="PN-00095">334</pat:PartNumber>. The <pat:PartName pat:idref="PN-00096">adjustment module </pat:PartName><pat:PartNumber pat:id="PN-00096">332</pat:PartNumber> may be employed by antivirus researchers or programs (e.g., scripts) to extract from the <pat:PartName pat:idref="PN-00097">event log </pat:PartName><pat:PartNumber pat:id="PN-00097">331</pat:PartNumber> data that may be used to define parameters for the <pat:PartName pat:idref="PN-00098">set of alert rules </pat:PartName><pat:PartNumber pat:id="PN-00098">334</pat:PartNumber>, such as data that identify critical assets, the roles of users of the critical assets, the behavior of users of the critical assets, and when the critical assets are accessed.</pat:P>
+<pat:P pat:id="p-41" pat:pNumber="41"><pat:BoundaryData><pat:LineNumber>20       </pat:LineNumber></pat:BoundaryData>In one embodiment, the <pat:PartName pat:idref="PN-00099">set of alert rules </pat:PartName><pat:PartNumber pat:id="PN-00099">334</pat:PartNumber> comprises one or more rules for identifying an APT attack. In the example of FIG. 4, the <pat:PartName pat:idref="PN-00100">set of alert rules </pat:PartName><pat:PartNumber pat:id="PN-00100">334</pat:PartNumber> may comprise rules for identifying an anomalous access to a critical asset.</pat:P>
+<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="888">-9-</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>
+<pat:P pat:id="p-42" pat:pNumber="42">
+<?PageStart number="10"?></pat:P>
+<pat:BoundaryData><pat:HeaderText>Attorney Docket No. 10033.025100</pat:HeaderText></pat:BoundaryData>
+<pat:P pat:id="p-43" pat:pNumber="43">In the example of FIG. 4, the <pat:PartName pat:idref="PN-00101">set of alert rules </pat:PartName><pat:PartNumber pat:id="PN-00101">334</pat:PartNumber> comprises rules 340-344. The <pat:PartName pat:idref="PN-00102">set of alert rules </pat:PartName><pat:PartNumber pat:id="PN-00102">334</pat:PartNumber> may have fewer or additional rules depending on the particulars of the implementation. In the example of FIG. 4, the <pat:PartName pat:idref="PN-00103">critical asset rules </pat:PartName><pat:PartNumber pat:id="PN-00103">340</pat:PartNumber> identify the critical assets of the organization. Examples of critical assets include servers that are <pat:BoundaryData><pat:LineNumber>5   </pat:LineNumber></pat:BoundaryData>critical to the organization (e.g., servers that store marketing, research and development, or financial data) and personal computers of key personnel (e.g., laptop computers of the president, chief financial officer, etc.). The critical assets may be identified by their internet protocol (IP) address, media access control (MAC) address, host name, and/or fully qualified domain name, for example. Identifiers of the critical <pat:BoundaryData><pat:LineNumber>10   </pat:LineNumber></pat:BoundaryData>assets of the organization may be entered in the <pat:PartName pat:idref="PN-00104">rules </pat:PartName><pat:PartNumber pat:id="PN-00104">340</pat:PartNumber> by the system administrator or other authorized personnel, for example. The identifiers of critical assets indicated in the <pat:PartName pat:idref="PN-00105">rules </pat:PartName><pat:PartNumber pat:id="PN-00105">340</pat:PartNumber> may be provided to the <pat:PartName pat:idref="PN-00106">network sensors </pat:PartName><pat:PartNumber pat:id="PN-00106">131</pat:PartNumber> for monitoring purposes.</pat:P>
+<pat:P pat:id="p-44" pat:pNumber="44">In the example of FIG. 4, the <pat:PartName pat:idref="PN-00107">role-based definition rules </pat:PartName><pat:PartNumber pat:id="PN-00107">341</pat:PartNumber> identify the authorized users of critical assets identified in the <pat:PartName pat:idref="PN-00108">rules </pat:PartName><pat:PartNumber pat:id="PN-00108">340</pat:PartNumber>. Generally speaking, the <pat:BoundaryData><pat:LineNumber>15  </pat:LineNumber></pat:BoundaryData><pat:PartName pat:idref="PN-00109">rules </pat:PartName><pat:PartNumber pat:id="PN-00109">341</pat:PartNumber> identify which computers should only be accessed by which users (e.g., from which account or which host/IP address). The users of critical assets may be authorized based on their roles in the organization. For example, computers that store financial data may only be accessed by the chief financial officer or managers of the finance department. An authorized user of a critical asset may be identified by his <pat:BoundaryData><pat:LineNumber>20   </pat:LineNumber></pat:BoundaryData>password/account name, host or IP address of his computer, or other information that uniquely and positively identify the authorized user. Identifiers of authorized users of critical assets of the organization may be entered in the <pat:PartName pat:idref="PN-00110">rules </pat:PartName><pat:PartNumber pat:id="PN-00110">341</pat:PartNumber> by the system administrator or other authorized personnel, for example.</pat:P>
+<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8888">-10-</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>
+<pat:P pat:id="p-45" pat:pNumber="45">
+<?PageStart number="11"?></pat:P>
+<pat:BoundaryData><pat:HeaderText>Attorney Docket No. 10033.025100</pat:HeaderText></pat:BoundaryData>
+<pat:P pat:id="p-46" pat:pNumber="46">In the example of FIG. 4, the <pat:PartName pat:idref="PN-00111">user-behavior profile rules </pat:PartName><pat:PartNumber pat:id="PN-00111">342</pat:PartNumber> indicate the access behavior profile of authorized users of critical assets. In one embodiment, the <pat:PartName pat:idref="PN-00112">rules </pat:PartName><pat:PartNumber pat:id="PN-00112">342</pat:PartNumber> indicate when a user typically accesses the critical asset (e.g., a user may typically access an asset on the first day of the month etc.), identify the computer typically <pat:BoundaryData><pat:LineNumber>5   </pat:LineNumber></pat:BoundaryData>employed by the user to access the asset (e.g., a user that typically accesses a server with a particular mobile device), and other access behavior of the user. The access behavior of the user may be identified from the <pat:PartName pat:idref="PN-00113">event log </pat:PartName><pat:PartNumber pat:id="PN-00113">331</pat:PartNumber>.</pat:P>
+<pat:P pat:id="p-47" pat:pNumber="47">In the example of FIG. 4, the <pat:PartName pat:idref="PN-00114">schedule definition rules </pat:PartName><pat:PartNumber pat:id="PN-00114">343</pat:PartNumber> indicate the time when the critical assets are normally accessed. Access to the critical assets outside their <pat:BoundaryData><pat:LineNumber>10   </pat:LineNumber></pat:BoundaryData>normal access times may be deemed to be abnormal. For example, a server that has been designated a critical asset may have an indicated normal access time in the <pat:PartName pat:idref="PN-00115">rules </pat:PartName><pat:PartNumber pat:id="PN-00115">343</pat:PartNumber> of between 00:00 hours and 05:00 hours Monday through Friday. Access to that server outside its normal access time (e.g., access to the server at 08:00 hours) may be deemed to be abnormal.</pat:P>
+<pat:P pat:id="p-48" pat:pNumber="48"><pat:BoundaryData><pat:LineNumber>15       </pat:LineNumber></pat:BoundaryData>In the example of FIG. 4, the <pat:PartName pat:idref="PN-00116">weight system rules </pat:PartName><pat:PartNumber pat:id="PN-00116">344</pat:PartNumber> indicate assigned weights to particular access events. More particularly, different access events, such as continuous login failures, multiple logins at the same time, login from a different computer, etc. may be assigned different weights to indicate their relevance in detecting an APT attack. The weights may be employed by the <pat:PartName pat:idref="PN-00117">correlator </pat:PartName><pat:PartNumber pat:id="PN-00117">335</pat:PartNumber> to determine <pat:BoundaryData><pat:LineNumber>20   </pat:LineNumber></pat:BoundaryData>whether or not an anomalous access to a critical asset is an APT attack. The weights for particular access events may be entered in the <pat:PartName pat:idref="PN-00118">rules </pat:PartName><pat:PartNumber pat:id="PN-00118">344</pat:PartNumber> by the system administrator or other authorized personnel, for example.</pat:P>
+<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8">-</pat:OCRConfidenceData> 11 -</pat:HeaderText></pat:BoundaryData>
+<pat:P pat:id="p-49" pat:pNumber="49">
+<?PageStart number="12"?></pat:P>
+<pat:BoundaryData><pat:HeaderText>Atto<pat:OCRConfidenceData pat:levelNumber="66">rn</pat:OCRConfidenceData>ey Docket No. 10033.025100</pat:HeaderText></pat:BoundaryData>
+<pat:P pat:id="p-50" pat:pNumber="50">Prior to normal operation wherein the system of FIG. 4 is employed to detect an APT attack, the system may first undergo an initial learning phase during which the system is operated to collect data for and make adjustments to the <pat:PartName pat:idref="PN-00119">set of alert rules </pat:PartName><pat:PartNumber pat:id="PN-00119">334</pat:PartNumber>. More specifically, prior to normal operation, the system of FIG. 4 may be operated <pat:BoundaryData><pat:LineNumber>5 </pat:LineNumber></pat:BoundaryData>in an initial learning phase during which the <pat:PartName pat:idref="PN-00120">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00120">131</pat:PartNumber> receives network traffic over the private computer network (see arrow 301), the <pat:PartName pat:idref="PN-00121">network sensor </pat:PartName><pat:PartNumber pat:id="PN-00121">131</pat:PartNumber> processes the received network traffic to generate and forward event data to the <pat:PartName pat:idref="PN-00122">APT detection server </pat:PartName><pat:PartNumber pat:id="PN-00122">140</pat:PartNumber> for storage in an <pat:PartName pat:idref="PN-00123">event log </pat:PartName><pat:PartNumber pat:id="PN-00123">331</pat:PartNumber> (see arrow 302), and the <pat:PartName pat:idref="PN-00124">set of alert rules </pat:PartName><pat:PartNumber pat:id="PN-00124">334</pat:PartNumber> are adjusted based on entries in the <pat:PartName pat:idref="PN-00125">event log </pat:PartName><pat:PartNumber pat:id="PN-00125">331</pat:PartNumber> <pat:PartName pat:idref="PN-00126">(see arrows </pat:PartName><pat:PartNumber pat:id="PN-00126">303</pat:PartNumber> and 304).</pat:P>
+<pat:P pat:id="p-51" pat:pNumber="51"><pat:BoundaryData><pat:LineNumber>10 </pat:LineNumber></pat:BoundaryData>During the initial learning phase, the <pat:PartName pat:idref="PN-00127">set of alert rules </pat:PartName><pat:PartNumber pat:id="PN-00127">334</pat:PartNumber> may be qualified, tuned, and adjusted by antivirus personnel for improved APT detection while minimizing false positives. After the initial learning phase, the system of FIG. 4 may be normally operated to detect an APT attack. As can be appreciated, the adjustment and tuning of the <pat:PartName pat:idref="PN-00128">set of alert rules </pat:PartName><pat:PartNumber pat:id="PN-00128">334</pat:PartNumber> may continue during normal operation to ensure that that the <pat:BoundaryData><pat:LineNumber>15 </pat:LineNumber></pat:BoundaryData><pat:PartName pat:idref="PN-00129">set of alert rules </pat:PartName><pat:PartNumber pat:id="PN-00129">334</pat:PartNumber> are continually optimized for the private computer network.</pat:P>
+<pat:P pat:id="p-52" pat:pNumber="52">During normal operation, the <pat:PartName pat:idref="PN-00130">correlator </pat:PartName><pat:PartNumber pat:id="PN-00130">335</pat:PartNumber> may be placed online to scan the <pat:PartName pat:idref="PN-00131">event log </pat:PartName><pat:PartNumber pat:id="PN-00131">331</pat:PartNumber> for entries indicating access to a critical asset (see arrow 305). The <pat:PartName pat:idref="PN-00132">correlator </pat:PartName><pat:PartNumber pat:id="PN-00132">335</pat:PartNumber> may consult the <pat:PartName pat:idref="PN-00133">set of alert rules </pat:PartName><pat:PartNumber pat:id="PN-00133">334</pat:PartNumber> to determine whether the access to the critical asset is normal or anomalous. For example, the <pat:PartName pat:idref="PN-00134">correlator </pat:PartName><pat:PartNumber pat:id="PN-00134">335</pat:PartNumber> may scan the <pat:BoundaryData><pat:LineNumber>20 </pat:LineNumber></pat:BoundaryData><pat:PartName pat:idref="PN-00135">event log </pat:PartName><pat:PartNumber pat:id="PN-00135">331</pat:PartNumber> to identify event data indicating access to a <pat:PartName pat:idref="PN-00136">critical asset (as per critical assets rules </pat:PartName><pat:PartNumber pat:id="PN-00136">340)</pat:PartNumber> outside its normal access time (as per schedule definition 343). The <pat:PartName pat:idref="PN-00137">correlator </pat:PartName><pat:PartNumber pat:id="PN-00137">335</pat:PartNumber> may base its decision on a particular event data or several event data.</pat:P>
+<pat:P pat:id="p-53" pat:pNumber="53">For example, in the just mentioned example, while access to a critical asset outside its <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8">-</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="88">12</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="8">-</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>
+<?PageStart number="13"?><pat:BoundaryData><pat:HeaderText>Attorney Docket No. 10033.025100</pat:HeaderText></pat:BoundaryData>normal access time may not be conclusive enough to declare the access to be an APT attack activity, that event coupled with another access event indicating that the same critical asset is accessed by an unauthorized user (per the <pat:PartName pat:idref="PN-00138">role based definition rules </pat:PartName><pat:PartNumber pat:id="PN-00138">341)</pat:PartNumber> after several login failures (as per other event data in the <pat:PartName pat:idref="PN-00139">event log </pat:PartName><pat:PartNumber pat:id="PN-00139">331)</pat:PartNumber> may <pat:BoundaryData><pat:LineNumber>5   </pat:LineNumber></pat:BoundaryData>indicate anomalous access to the critical asset.</pat:P>
+<pat:P pat:id="p-54" pat:pNumber="54">FIG. 8 shows an example pseudo code for a rule that may be used by the <pat:PartName pat:idref="PN-00140">correlator </pat:PartName><pat:PartNumber pat:id="PN-00140">335</pat:PartNumber> to detect successful logins that may indicate lateral movement of an APT attack. In the example of FIG. 8, the rule looks for successful logins from different machines by the same user (identified by "AccountName" and "ClientAddress"). In <pat:BoundaryData><pat:LineNumber>10  </pat:LineNumber></pat:BoundaryData>the example of FIG. 8, successful logins from five or more computers ("$machine_count") within a predetermined time period ("timewindow") indicates an anomalous access.</pat:P>
+<pat:P pat:id="p-55" pat:pNumber="55">In one embodiment, the <pat:PartName pat:idref="PN-00141">correlator </pat:PartName><pat:PartNumber pat:id="PN-00141">335</pat:PartNumber> deems anomalous access to a critical asset to be a possible APT attack. In that case, the <pat:PartName pat:idref="PN-00142">correlator </pat:PartName><pat:PartNumber pat:id="PN-00142">335</pat:PartNumber> may alert an <pat:BoundaryData><pat:LineNumber>15  </pat:LineNumber></pat:BoundaryData>administrator or other authorized personnel about the anomalous access. The <pat:PartName pat:idref="PN-00143">correlator </pat:PartName><pat:PartNumber pat:id="PN-00143">335</pat:PartNumber> may send an alert by sending an email, displaying a message box, text messaging, raising an audible alarm, etc. The alert may be used to initiate an investigation of the anomalous access, raise security-levels (e.g., temporarily prevent access to critical assets) to prevent or minimize damage from an APT attack in <pat:BoundaryData><pat:LineNumber>20   </pat:LineNumber></pat:BoundaryData>progress, or initiate other responses for dealing with an APT attack.</pat:P>
+<pat:P pat:id="p-56" pat:pNumber="56">Systems and methods for detecting an APT attack on a private computer network have been disclosed. While specific embodiments of the present invention have been provided, it is to be understood that these embodiments are for illustration purposes and <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8888">-13-</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>
+<?PageStart number="14"?><pat:BoundaryData><pat:HeaderText>Attorney Docket No. 10033.025100</pat:HeaderText></pat:BoundaryData>not limiting. Many additional embodiments will be apparent to persons of ordinary skill in the art reading this disclosure.</pat:P>
+<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8">-</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="88">14</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber="8">-</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>
+</pat:Specification></pat:SpecificationDocument>

applicant/14924380.xml

@@ -0,0 +1 @@
+<?xml version="1.0" encoding="utf-8"?><pat:SpecificationDocument xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:pat="urn:us:gov:doc:uspto:patent" xmlns:ent="urn:us:gov:doc:uspto:enterprise" xmlns="urn:us:gov:doc:uspto:patent" xmlns:tbl="http://www.oasis-open.org/tables/exchange/1.0" xmlns:com="http://www.wipo.int/standards/XMLSchema/Common/1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XML_SCHEMAS/V1_3/SpecificationDocument_1_0.xsd" pat:instanceFileName="14924380.10-27-2015.IG9W48FOPXXIFW3.SPEC.XML" pat:id="IG9W48FOPXXIFW3"><pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001"><pat:ApplicationHeaderDetails><pat:ApplicationNumber>14924380</pat:ApplicationNumber></pat:ApplicationHeaderDetails><pat:PageTotalQuantity>17</pat:PageTotalQuantity><pat:ParagraphTotalQuantity>32</pat:ParagraphTotalQuantity></pat:DocumentHeaderDetails><pat:MailRoomDate>2015-10-27</pat:MailRoomDate><pat:DocumentCreateDateText>2015-10-27</pat:DocumentCreateDateText><pat:Specification><?PageStart number='1'?><pat:P pat:pNumber="1" pat:id="p-1"><pat:OCRConfidenceData pat:levelNumber="5">0</pat:OCRConfidenceData>222772  October 27,<pat:PartName pat:idref="PN-00001"> </pat:PartName><pat:PartNumber pat:id="PN-00001">2015</pat:PartNumber></pat:P><pat:Heading pat:id="h-1">CONTENTS SHARING METHOD BETWEEN MOBILE TERMINAL</pat:Heading><pat:Heading pat:id="h-2">AND LOCAL SERVER</pat:Heading><pat:Heading pat:id="h-3"><pat:U>BACKGROUND</pat:U> <pat:U>OF</pat:U> <pat:U>THE</pat:U> <pat:U>INVENTION</pat:U></pat:Heading><pat:P pat:pNumber="2" pat:id="p-2">[01]         This application is a Continuation of U.S. Patent Application  No.<pat:PartName pat:idref="PN-00002"> </pat:PartName><pat:PartNumber pat:id="PN-00002">11</pat:PartNumber>/645,594, filed on December 27,<pat:PartName pat:idref="PN-00003"> </pat:PartName><pat:PartNumber pat:id="PN-00003">2006</pat:PartNumber> in the U.S. Patent and Trademark  Office, which claims the priority of Korean Patent Application No.<pat:PartName pat:idref="PN-00004"> </pat:PartName><pat:PartNumber pat:id="PN-00004">10</pat:PartNumber>-2006-<pat:PartName pat:idref="PN-00005">  </pat:PartName><pat:PartNumber pat:id="PN-00005">0072693</pat:PartNumber>, filed on August 1,<pat:PartName pat:idref="PN-00006"> </pat:PartName><pat:PartNumber pat:id="PN-00006">2006</pat:PartNumber>, in the Korean Intellectual Property Office,  the disclosure of which is incorporated herein in its entirety by reference.</pat:P><pat:P pat:pNumber="3" pat:id="p-3">1.    Field of the Invention  [02]         Methods consistent with present invention relate to contents  sharing between a mobile terminal and a local server, and more particularly to,  sharing contents required by a user using a mobile terminal via another user's  local mobile terminal or a local server.</pat:P><pat:P pat:pNumber="4" pat:id="p-4">2.    Description of the Related Art  [03]         A memory amount of mobile terminals has been increased.</pat:P><pat:P pat:pNumber="5" pat:id="p-5">Mobile terminals store various contents such as bell sound, music files, images,  video, games, various types of data, and so on through data communication.  [04]         Users obtain digital contents by purchasing storage media such  as digital versatile discs (DVDs) or compact disks (CDs), using cyber money  in Internet sites, or downloading peer-to-peer (P2P) software on personal  computers (PCs).</pat:P><pat:P pat:pNumber="6" pat:id="p-6">[05]         However, users must visit stores personally to purchase storage<?PageStart number='2'?>media, and need a PC environment to obtain digital contents via Internet sites  or P2P software, which requires users to log on each Internet site and search  P2P software.</pat:P><pat:Heading pat:id="h-4"><pat:U>SUMMARY</pat:U> <pat:U>OF</pat:U> <pat:U>THE</pat:U> <pat:U>INVENTION</pat:U></pat:Heading><pat:P pat:pNumber="7" pat:id="p-7">[06]        Exemplary embodiments of the present invention overcome the  above disadvantages and other disadvantages not described above. Also, the  present invention is not required to overcome the disadvantages described  above, and an exemplary embodiment of the present invention may not  overcome any of the problems described above.  [07]        The present invention provides a mobile terminal by which a  user can obtain desired contents via a local terminal or a local server.</pat:P><pat:P pat:pNumber="8" pat:id="p-8">[08]        According to an aspect of the present invention, there is  provided a contents sharing method between a client terminal storing metadata  and a server terminal storing the metadata, the method comprising: requesting  the server terminal for a contents share service; and receiving information on  contents corresponding to matching metadata as a result of comparing the  metadata stored in the client terminal and the metadata stored in the server  terminal.</pat:P><pat:P pat:pNumber="9" pat:id="p-9">[09]        New metadata is generated by inputting a keyword signal,  related to the contents, into the client terminal in the form of metadata or  based on previously established metadata and the new metadata is then stored  in the client terminal.</pat:P><pat:P pat:pNumber="10" pat:id="p-10">[10]        The client terminal requests the contents share service from the<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8">2</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='3'?>server terminal using a contents share service protocol.  [11]         The information on the contents includes at least one of  contents corresponding to the matching metadata, unique resource identifier  (URI) information or license information of the contents, and the matching  metadata itself.</pat:P><pat:P pat:pNumber="11" pat:id="p-11">[12]         The method further comprises, when the URI information of  the contents corresponding to the matching metadata is received from the  server terminal, accessing the URI through a wireless LAN, requesting  transmission of the contents, and receiving the contents.  [13]         According to another aspect of the present invention, there is  provided a contents share method between a client terminal storing metadata  and a server terminal storing the metadata, the method comprising: receiving a  request for a contents share service from the client terminal; and selectively  transmitting information on contents corresponding to matching metadata as a  result of comparing the metadata stored in the client terminal and stored  metadata according to the request from the client terminal.  [14]         According to another aspect of the present invention, there is  provided a contents share method between client terminals storing metadata  and server terminals storing the metadata, the method comprising: as a result  of comparing metadata stored in a first client terminal and metadata stored in a  first server terminal, receiving contents information in which contents  <pat:OCRConfidenceData pat:levelNumber="8866">corr</pat:OCRConfidenceData>esponding to matching metadata is stored in an external second server  terminal from the first client terminal; requesting the second server terminal to<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8">3</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='4'?>transmit the contents; and receiving the contents from the second server  terminal.</pat:P><pat:P pat:pNumber="12" pat:id="p-12">[15]         According to another aspect of the present invention, there is  provided a client terminal that shares contents with a server terminal storing  metadata, comprising: a communication module requesting the server terminal  for a contents share service and transmitting metadata stored therein; and a  controller comparing the metadata stored in the client terminal and the  metadata stored in the server terminal and requesting transmission of  information on contents co<pat:OCRConfidenceData pat:levelNumber="66">rr</pat:OCRConfidenceData>esponding to matching metadata.</pat:P><pat:P pat:pNumber="13" pat:id="p-13">[16]         According to another aspect of the present invention, there is  provided a server terminal that shares contents with a client terminal storing  metadata, comprising: a metadata generation module generating metadata of  the contents; a metadata database storing the generated metadata; a  communication module receiving a request for a contents share service from  the client terminal and transmitting metadata stored therein; a metadata  matching module comparing the generated metadata and the metadata  received from the client terminal; and a controller selectively transmitting  information on contents co<pat:OCRConfidenceData pat:levelNumber="66">rr</pat:OCRConfidenceData>esponding to matching metadata.</pat:P><pat:Heading pat:id="h-5"><pat:U>BRIEF</pat:U> <pat:U>DESCRIPTION</pat:U> <pat:U>OF</pat:U> <pat:U>THE</pat:U> <pat:U>DRAWINGS</pat:U></pat:Heading><pat:P pat:pNumber="14" pat:id="p-14">[17]         The above and other features and advantages of the present  invention will become more apparent by describing in detail exemplary  embodiments thereof with reference to the attached drawings in which:  [18]         FIG.<pat:PartName pat:idref="PN-00007"> </pat:PartName><pat:PartNumber pat:id="PN-00007">1</pat:PartNumber> is a block diagram of a mobile terminal according to an<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8">4</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='5'?>exemplary embodiment of the present invention;</pat:P><pat:P pat:pNumber="15" pat:id="p-15">[19]        FIG.<pat:PartName pat:idref="PN-00008"> </pat:PartName><pat:PartNumber pat:id="PN-00008">2</pat:PartNumber> is a block diagram of a contents sharing system using  the mobile terminal according to an exemplary embodiment of the present  invention;</pat:P><pat:P pat:pNumber="16" pat:id="p-16">[20]        FIG.<pat:PartName pat:idref="PN-00009"> </pat:PartName><pat:PartNumber pat:id="PN-00009">3</pat:PartNumber> is a flowchart illustrating a contents sharing method  between the mobile terminal and the local server according to an exemplary  embodiment of the present invention;  [21]        FIG.<pat:PartName pat:idref="PN-00010"> </pat:PartName><pat:PartNumber pat:id="PN-00010">4</pat:PartNumber> is a flowchart illustrating a contents sharing method  between mobile terminals and a local server according to another exemplary  embodiment of the present invention; and  [22]        FIG.<pat:PartName pat:idref="PN-00011"> </pat:PartName><pat:PartNumber pat:id="PN-00011">5</pat:PartNumber> is a flowchart illustrating a contents sharing method  between mobile terminals and a local server according to another exemplary  embodiment of the present invention.</pat:P><pat:Heading pat:id="h-6"><pat:U>DETAILED</pat:U> <pat:U>DESCRIPTION</pat:U> <pat:U>OF</pat:U> <pat:U>EXEMPLARY</pat:U> <pat:U>EMBODIMENTS</pat:U> <pat:U>OF</pat:U></pat:Heading><pat:Heading pat:id="h-7"><pat:U>THE</pat:U> <pat:U>INVENTION</pat:U></pat:Heading><pat:P pat:pNumber="17" pat:id="p-17">[23]        The present invention will now be described more fully with  reference to the accompanying drawings, in which exemplary embodiments of  the invention are shown. Like reference numerals in the drawings denote like  elements.</pat:P><pat:P pat:pNumber="18" pat:id="p-18">[24]        FIG.<pat:PartName pat:idref="PN-00012"> </pat:PartName><pat:PartNumber pat:id="PN-00012">1</pat:PartNumber> is a block diagram of a<pat:PartName pat:idref="PN-00013"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00013">100</pat:PartNumber> according to  an exemplary embodiment of the present invention. Refe<pat:OCRConfidenceData pat:levelNumber="66">rr</pat:OCRConfidenceData>ing to FIG.<pat:PartName pat:idref="PN-00014"> </pat:PartName><pat:PartNumber pat:id="PN-00014">1</pat:PartNumber>, the<pat:PartName pat:idref="PN-00015">  mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00015">100</pat:PartNumber> includes a<pat:PartName pat:idref="PN-00016"> controller </pat:PartName><pat:PartNumber pat:id="PN-00016">10</pat:PartNumber>, a<pat:PartName pat:idref="PN-00017"> metadata generation module </pat:PartName><pat:PartNumber pat:id="PN-00017">20</pat:PartNumber>,  a<pat:PartName pat:idref="PN-00018"> metadata database (DB) </pat:PartName><pat:PartNumber pat:id="PN-00018">30</pat:PartNumber>, a<pat:PartName pat:idref="PN-00019"> metadata matching module </pat:PartName><pat:PartNumber pat:id="PN-00019">40</pat:PartNumber>, and a local<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8">5</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='6'?>communication<pat:PartName pat:idref="PN-00020"> module </pat:PartName><pat:PartNumber pat:id="PN-00020">50</pat:PartNumber></pat:P><pat:P pat:pNumber="19" pat:id="p-19">[25]         The<pat:PartName pat:idref="PN-00021"> controller </pat:PartName><pat:PartNumber pat:id="PN-00021">10</pat:PartNumber> controls the<pat:PartName pat:idref="PN-00022"> metadata generation module </pat:PartName><pat:PartNumber pat:id="PN-00022">20</pat:PartNumber>,  the<pat:PartName pat:idref="PN-00023"> metadata DB </pat:PartName><pat:PartNumber pat:id="PN-00023">30</pat:PartNumber>, the<pat:PartName pat:idref="PN-00024"> metadata matching module </pat:PartName><pat:PartNumber pat:id="PN-00024">40</pat:PartNumber>, and the<pat:PartName pat:idref="PN-00025"> local  communication module </pat:PartName><pat:PartNumber pat:id="PN-00025">50</pat:PartNumber>, and, if metadata information stored in a local  mobile terminal or a local server matches metadata, controls the transmission  of contents corresponding to the matched metadata.  [26]         The<pat:PartName pat:idref="PN-00026"> metadata generation module </pat:PartName><pat:PartNumber pat:id="PN-00026">20</pat:PartNumber> generates metadata  information from the contents to be exchanged with another mobile terminal.  For example, when a user obtains a music file as the contents, the<pat:PartName pat:idref="PN-00027"> metadata  generation module </pat:PartName><pat:PartNumber pat:id="PN-00027">20</pat:PartNumber> can generate metadata such as time when the contents  are generated, a singer, genre, etc.</pat:P><pat:P pat:pNumber="20" pat:id="p-20">[27]         New metadata can be generated by a user by inputting a  keyword signal associated with the contents in the form of metadata in the<pat:PartName pat:idref="PN-00028">  mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00028">100</pat:PartNumber> or based on metadata.  [28]         The<pat:PartName pat:idref="PN-00029"> metadata DB </pat:PartName><pat:PartNumber pat:id="PN-00029">30</pat:PartNumber> stores metadata generated by the<pat:PartName pat:idref="PN-00030"> metadata  generation module </pat:PartName><pat:PartNumber pat:id="PN-00030">20</pat:PartNumber> and can be shared with another mobile terminal. The<pat:PartName pat:idref="PN-00031">  metadata DB </pat:PartName><pat:PartNumber pat:id="PN-00031">30</pat:PartNumber> stores contents information stored in the<pat:PartName pat:idref="PN-00032"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00032">100</pat:PartNumber>  and contents information owned by the user of the<pat:PartName pat:idref="PN-00033"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00033">100</pat:PartNumber> that  are stored on a Web server.</pat:P><pat:P pat:pNumber="21" pat:id="p-21">[29]         The metadata can be stored in the<pat:PartName pat:idref="PN-00034"> metadata DB </pat:PartName><pat:PartNumber pat:id="PN-00034">30</pat:PartNumber> as in the  current exemplary embodiment of the present invention or in the form of an  extensible markup language (XML) document.</pat:P><pat:P pat:pNumber="22" pat:id="p-22">[30]         The<pat:PartName pat:idref="PN-00035"> metadata matching module </pat:PartName><pat:PartNumber pat:id="PN-00035">40</pat:PartNumber> determines whether<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8">6</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='7'?>metadata matches metadata of the local terminal or the local server, and  transmits the metadata or contents.</pat:P><pat:P pat:pNumber="23" pat:id="p-23">[31]         The<pat:PartName pat:idref="PN-00036"> local communication module </pat:PartName><pat:PartNumber pat:id="PN-00036">50</pat:PartNumber> browses a local mobile  terminal or the local server.   The<pat:PartName pat:idref="PN-00037"> local communication module </pat:PartName><pat:PartNumber pat:id="PN-00037">50</pat:PartNumber>  communicates with the local mobile terminal or the local server via bluetooth,  and, if the metadata or contents are stored in a remote controlled Web server,  via a wireless local area network (LAN).  [32]         FIG.<pat:PartName pat:idref="PN-00038"> </pat:PartName><pat:PartNumber pat:id="PN-00038">1</pat:PartNumber> illustrates the<pat:PartName pat:idref="PN-00039"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00039">100</pat:PartNumber> for a server that  transmits generated metadata if the<pat:PartName pat:idref="PN-00040"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00040">100</pat:PartNumber> is requested to  transmit contents. A mobile terminal for client that requests contents using  stored metadata includes the<pat:PartName pat:idref="PN-00041"> controller </pat:PartName><pat:PartNumber pat:id="PN-00041">10</pat:PartNumber> and the<pat:PartName pat:idref="PN-00042"> local communication  module </pat:PartName><pat:PartNumber pat:id="PN-00042">50</pat:PartNumber> whose functions are similar to the ones described above. Thus,  their detailed description is omitted.</pat:P><pat:P pat:pNumber="24" pat:id="p-24">[33]         The operation of the<pat:PartName pat:idref="PN-00043"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00043">100</pat:PartNumber>, which shares  contents information via the local server, will now be described with reference  to FIGS.<pat:PartName pat:idref="PN-00044"> </pat:PartName><pat:PartNumber pat:id="PN-00044">2</pat:PartNumber><pat:PartName pat:idref="PN-00045"> through </pat:PartName><pat:PartNumber pat:id="PN-00045">4</pat:PartNumber></pat:P><pat:P pat:pNumber="25" pat:id="p-25">[34]         FIG.<pat:PartName pat:idref="PN-00046"> </pat:PartName><pat:PartNumber pat:id="PN-00046">2</pat:PartNumber> is a block diagram of a contents sharing system using  the<pat:PartName pat:idref="PN-00047"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00047">100</pat:PartNumber> according to an exemplary embodiment of the present  invention.</pat:P><pat:P pat:pNumber="26" pat:id="p-26">[35]         Refe<pat:OCRConfidenceData pat:levelNumber="66">rr</pat:OCRConfidenceData>ing to FIG.<pat:PartName pat:idref="PN-00048"> </pat:PartName><pat:PartNumber pat:id="PN-00048">2</pat:PartNumber>, the<pat:PartName pat:idref="PN-00049"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00049">100</pat:PartNumber><pat:PartName pat:idref="PN-00050"> can share contents  by matching contents between mobile terminals </pat:PartName><pat:PartNumber pat:id="PN-00050">100</pat:PartNumber> and<pat:PartName pat:idref="PN-00051"> </pat:PartName><pat:PartNumber pat:id="PN-00051">101</pat:PartNumber>, from a<pat:PartName pat:idref="PN-00052"> local  server </pat:PartName><pat:PartNumber pat:id="PN-00052">200</pat:PartNumber>, and by receiving contents location information from the<pat:PartName pat:idref="PN-00053"> mobile  terminal </pat:PartName><pat:PartNumber pat:id="PN-00053">101</pat:PartNumber> or the<pat:PartName pat:idref="PN-00054"> local server </pat:PartName><pat:PartNumber pat:id="PN-00054">200</pat:PartNumber> and obtaining contents from a remote PC<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8">7</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='8'?>400 via a<pat:PartName pat:idref="PN-00055"> web server </pat:PartName><pat:PartNumber pat:id="PN-00055">300</pat:PartNumber></pat:P><pat:P pat:pNumber="27" pat:id="p-27">[36]         To share contents by matching between the<pat:PartName pat:idref="PN-00056"> mobile terminals  </pat:PartName><pat:PartNumber pat:id="PN-00056">100</pat:PartNumber> and<pat:PartName pat:idref="PN-00057"> </pat:PartName><pat:PartNumber pat:id="PN-00057">101</pat:PartNumber>, metadata of contents stored in the<pat:PartName pat:idref="PN-00058"> mobile terminals </pat:PartName><pat:PartNumber pat:id="PN-00058">100</pat:PartNumber> and<pat:PartName pat:idref="PN-00059"> </pat:PartName><pat:PartNumber pat:id="PN-00059">101</pat:PartNumber>  are compared, and, if the metadata match, the contents or contents information  stored in the<pat:PartName pat:idref="PN-00060"> mobile terminals </pat:PartName><pat:PartNumber pat:id="PN-00060">100</pat:PartNumber> and<pat:PartName pat:idref="PN-00061"> </pat:PartName><pat:PartNumber pat:id="PN-00061">101</pat:PartNumber> are exchanged.  [37]         To transmit contents from the<pat:PartName pat:idref="PN-00062"> local server </pat:PartName><pat:PartNumber pat:id="PN-00062">200</pat:PartNumber>, metadata of  contents stored in the<pat:PartName pat:idref="PN-00063"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00063">100</pat:PartNumber> and the<pat:PartName pat:idref="PN-00064"> local server </pat:PartName><pat:PartNumber pat:id="PN-00064">200</pat:PartNumber> are  compared, and, if the metadata match, the contents or contents information  stored in the<pat:PartName pat:idref="PN-00065"> mobile terminals </pat:PartName><pat:PartNumber pat:id="PN-00065">100</pat:PartNumber> and the<pat:PartName pat:idref="PN-00066"> local server </pat:PartName><pat:PartNumber pat:id="PN-00066">200</pat:PartNumber> are exchanged.  [38]         It is assumed that the<pat:PartName pat:idref="PN-00067"> PC </pat:PartName><pat:PartNumber pat:id="PN-00067">400</pat:PartNumber> stores contents and metadata of  the contents and transmits the same to the<pat:PartName pat:idref="PN-00068"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00068">101</pat:PartNumber> or the<pat:PartName pat:idref="PN-00069"> local  server </pat:PartName><pat:PartNumber pat:id="PN-00069">200</pat:PartNumber>. When the metadata stored in the<pat:PartName pat:idref="PN-00070"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00070">101</pat:PartNumber> or the<pat:PartName pat:idref="PN-00071"> local  server </pat:PartName><pat:PartNumber pat:id="PN-00071">200</pat:PartNumber> match the metadata of the<pat:PartName pat:idref="PN-00072"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00072">100</pat:PartNumber>, the<pat:PartName pat:idref="PN-00073"> mobile terminal  </pat:PartName><pat:PartNumber pat:id="PN-00073">100</pat:PartNumber> attempts to access the<pat:PartName pat:idref="PN-00074"> PC </pat:PartName><pat:PartNumber pat:id="PN-00074">400</pat:PartNumber> over the<pat:PartName pat:idref="PN-00075"> web server </pat:PartName><pat:PartNumber pat:id="PN-00075">300</pat:PartNumber> using the wireless  LAN and receives the contents.</pat:P><pat:P pat:pNumber="28" pat:id="p-28">[39]         FIG.<pat:PartName pat:idref="PN-00076"> </pat:PartName><pat:PartNumber pat:id="PN-00076">3</pat:PartNumber> is a flowchart illustrating a contents sharing method  between the<pat:PartName pat:idref="PN-00077"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00077">100</pat:PartNumber> and the<pat:PartName pat:idref="PN-00078"> local server </pat:PartName><pat:PartNumber pat:id="PN-00078">200</pat:PartNumber> according to an  exemplary embodiment of the present invention.</pat:P><pat:P pat:pNumber="29" pat:id="p-29">[40]         For descriptive convenience, the<pat:PartName pat:idref="PN-00079"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00079">100</pat:PartNumber> is a client  terminal that receives contents information and the<pat:PartName pat:idref="PN-00080"> local server </pat:PartName><pat:PartNumber pat:id="PN-00080">200</pat:PartNumber> is a server  terminal that transmits contents information to the<pat:PartName pat:idref="PN-00081"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00081">100</pat:PartNumber>.  [41]         The<pat:PartName pat:idref="PN-00082"> local server </pat:PartName><pat:PartNumber pat:id="PN-00082">200</pat:PartNumber> includes the<pat:PartName pat:idref="PN-00083"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00083">100</pat:PartNumber> and all  the constituents of the<pat:PartName pat:idref="PN-00084"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00084">100</pat:PartNumber>. The<pat:PartName pat:idref="PN-00085"> local server </pat:PartName><pat:PartNumber pat:id="PN-00085">200</pat:PartNumber> searches<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8">8</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='9'?>stored contents, generates metadata for the searched contents, and stores the  metadata in a DB.  [42]         Refe<pat:OCRConfidenceData pat:levelNumber="66">rr</pat:OCRConfidenceData>ing to FIG.<pat:PartName pat:idref="PN-00086"> </pat:PartName><pat:PartNumber pat:id="PN-00086">3</pat:PartNumber>, a user establishes metadata of desired  contents in the<pat:PartName pat:idref="PN-00087"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00087">100</pat:PartNumber><pat:PartName pat:idref="PN-00088"> (Operation S </pat:PartName><pat:PartNumber pat:id="PN-00088">10</pat:PartNumber>).  [43]         Examples of the desired contents are a user's personal profile, a  user's hobby, user's favorite song and real-time news break, writings newly  uploaded on a homepage, video, a specific singer's song or someone else's  contents favorites. That is, the metadata of contents can be direct information  on contents or contents used record or contents favorite information. In  addition, the metadata of contents can be a list of user's contents that can be  exchanged with another person, metadata of contents or personal information  on user's contents used record or favorite, etc.  [44]         The metadata of contents can be personally input by the user or  generated by analyzing user's contents used history using the<pat:PartName pat:idref="PN-00089"> controller </pat:PartName><pat:PartNumber pat:id="PN-00089">10</pat:PartNumber> of  the<pat:PartName pat:idref="PN-00090"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00090">100</pat:PartNumber>.  The metadata of contents can be at least one  keyword that is a kind of index.  [45]         The<pat:PartName pat:idref="PN-00091"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00091">100</pat:PartNumber> browses the<pat:PartName pat:idref="PN-00092"> local server </pat:PartName><pat:PartNumber pat:id="PN-00092">200</pat:PartNumber><pat:PartName pat:idref="PN-00093">  (Operation </pat:PartName><pat:PartNumber pat:id="PN-00093">20</pat:PartNumber>).  [46]         In detail, the<pat:PartName pat:idref="PN-00094"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00094">100</pat:PartNumber> is carried by a user, the<pat:PartName pat:idref="PN-00095">  mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00095">100</pat:PartNumber> browses the<pat:PartName pat:idref="PN-00096"> local server </pat:PartName><pat:PartNumber pat:id="PN-00096">200</pat:PartNumber>, which can exchange and  share the metadata through the<pat:PartName pat:idref="PN-00097"> local communication module </pat:PartName><pat:PartNumber pat:id="PN-00097">50</pat:PartNumber>. The<pat:PartName pat:idref="PN-00098"> local  communication module </pat:PartName><pat:PartNumber pat:id="PN-00098">50</pat:PartNumber> can use a local communication means such as  Bluetooth or a specific protocol, but is not limited to those means.<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8">9</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='10'?>[47]         The<pat:PartName pat:idref="PN-00099"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00099">100</pat:PartNumber> sends a request for a contents share  service to a<pat:PartName pat:idref="PN-00100"> base station </pat:PartName><pat:PartNumber pat:id="PN-00100">500</pat:PartNumber> using an available traffic channel. The<pat:PartName pat:idref="PN-00101"> base  station </pat:PartName><pat:PartNumber pat:id="PN-00101">500</pat:PartNumber> confirms that the<pat:PartName pat:idref="PN-00102"> local server </pat:PartName><pat:PartNumber pat:id="PN-00102">200</pat:PartNumber> is in a service area, requests the  contents share service from the<pat:PartName pat:idref="PN-00103"> local server </pat:PartName><pat:PartNumber pat:id="PN-00103">200</pat:PartNumber> using the traffic channel,  notifies the<pat:PartName pat:idref="PN-00104"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00104">100</pat:PartNumber> if the contents share service is approved, and  connects the contents share service to the<pat:PartName pat:idref="PN-00105"> local server </pat:PartName><pat:PartNumber pat:id="PN-00105">200</pat:PartNumber>.  [48]         The<pat:PartName pat:idref="PN-00106"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00106">100</pat:PartNumber> and the<pat:PartName pat:idref="PN-00107"> local server </pat:PartName><pat:PartNumber pat:id="PN-00107">200</pat:PartNumber> can perform a  local communication in the service area of the<pat:PartName pat:idref="PN-00108"> base station </pat:PartName><pat:PartNumber pat:id="PN-00108">500</pat:PartNumber>.  [49]         The<pat:PartName pat:idref="PN-00109"> base station </pat:PartName><pat:PartNumber pat:id="PN-00109">500</pat:PartNumber> allocates the same traffic channel to the<pat:PartName pat:idref="PN-00110">  mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00110">100</pat:PartNumber> or the<pat:PartName pat:idref="PN-00111"> local server </pat:PartName><pat:PartNumber pat:id="PN-00111">200</pat:PartNumber>, temporarily stores contents  information received from the<pat:PartName pat:idref="PN-00112"> local server </pat:PartName><pat:PartNumber pat:id="PN-00112">200</pat:PartNumber>, and acts as a buffer that  transfers the contents information to the<pat:PartName pat:idref="PN-00113"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00113">100</pat:PartNumber>, which is the  client terminal.  [50]         The contents share service is connected between the<pat:PartName pat:idref="PN-00114"> mobile  terminal </pat:PartName><pat:PartNumber pat:id="PN-00114">100</pat:PartNumber> and the<pat:PartName pat:idref="PN-00115"> local server </pat:PartName><pat:PartNumber pat:id="PN-00115">200</pat:PartNumber>. The<pat:PartName pat:idref="PN-00116"> base station </pat:PartName><pat:PartNumber pat:id="PN-00116">500</pat:PartNumber> allocates the same  traffic channel between the<pat:PartName pat:idref="PN-00117"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00117">100</pat:PartNumber> and the<pat:PartName pat:idref="PN-00118"> local server </pat:PartName><pat:PartNumber pat:id="PN-00118">200</pat:PartNumber>  (Operation S30). The<pat:PartName pat:idref="PN-00119"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00119">100</pat:PartNumber> transmits the metadata to the<pat:PartName pat:idref="PN-00120"> local  server </pat:PartName><pat:PartNumber pat:id="PN-00120">200</pat:PartNumber> according to the relay of the<pat:PartName pat:idref="PN-00121"> base station </pat:PartName><pat:PartNumber pat:id="PN-00121">500</pat:PartNumber> using the allocated  traffic channel.  [51]         In detail, the metadata established by the user or the<pat:PartName pat:idref="PN-00122"> controller  </pat:PartName><pat:PartNumber pat:id="PN-00122">10</pat:PartNumber> is uploaded through the<pat:PartName pat:idref="PN-00123"> local communication module </pat:PartName><pat:PartNumber pat:id="PN-00123">50</pat:PartNumber> of the<pat:PartName pat:idref="PN-00124"> mobile  terminal </pat:PartName><pat:PartNumber pat:id="PN-00124">100</pat:PartNumber> (Operation S40). Therefore, if the metadata is transmitted to the<pat:PartName pat:idref="PN-00125">  base station </pat:PartName><pat:PartNumber pat:id="PN-00125">500</pat:PartNumber> using the traffic channel, the<pat:PartName pat:idref="PN-00126"> base station </pat:PartName><pat:PartNumber pat:id="PN-00126">500</pat:PartNumber> transmits the<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="88">10</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='11'?>metadata to the<pat:PartName pat:idref="PN-00127"> local server </pat:PartName><pat:PartNumber pat:id="PN-00127">200</pat:PartNumber>.  [52]         The<pat:PartName pat:idref="PN-00128"> local server </pat:PartName><pat:PartNumber pat:id="PN-00128">200</pat:PartNumber> compares the metadata of stored contents  with metadata information uploaded from the<pat:PartName pat:idref="PN-00129"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00129">100</pat:PartNumber> (Operation  S50).  [53]         The<pat:PartName pat:idref="PN-00130"> metadata matching module </pat:PartName><pat:PartNumber pat:id="PN-00130">40</pat:PartNumber> of the<pat:PartName pat:idref="PN-00131"> local server </pat:PartName><pat:PartNumber pat:id="PN-00131">200</pat:PartNumber>  browses metadata information that is common to the<pat:PartName pat:idref="PN-00132"> stored metadata DB </pat:PartName><pat:PartNumber pat:id="PN-00132">30</pat:PartNumber>  and the uploaded metadata information.  [54]         For example, when the uploaded metadata information is jazz  music and the<pat:PartName pat:idref="PN-00133"> metadata DB </pat:PartName><pat:PartNumber pat:id="PN-00133">30</pat:PartNumber> of the<pat:PartName pat:idref="PN-00134"> local server </pat:PartName><pat:PartNumber pat:id="PN-00134">200</pat:PartNumber> stores jazz music, the<pat:PartName pat:idref="PN-00135">  metadata matching module </pat:PartName><pat:PartNumber pat:id="PN-00135">40</pat:PartNumber> determines that there is a match.  [55]         When metadata information matches, the<pat:PartName pat:idref="PN-00136"> local server </pat:PartName><pat:PartNumber pat:id="PN-00136">200</pat:PartNumber>  transmits contents information based on the matched metadata information to  the<pat:PartName pat:idref="PN-00137"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00137">100</pat:PartNumber> (Operation S60). The contents information can be  contents themselves, an address for obtaining contents, and/or metadata of  contents.  [56]         If the traffic channel has a sufficient bandwidth and sufficient  time, and desired contents are included in the<pat:PartName pat:idref="PN-00138"> local server </pat:PartName><pat:PartNumber pat:id="PN-00138">200</pat:PartNumber>, then the  contents are directly transmitted or copied.  However, if the above  requirements are not satisfied, then only metadata of contents will be  transferred. The metadata can be a unique resource identifier (URI) of source  used to obtain desired contents, identifier ID information in a P2P network, or  license information of the contents.  [57]         When the<pat:PartName pat:idref="PN-00139"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00139">100</pat:PartNumber> performs a local communication<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="88">11</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='12'?>with another mobile terminal acting as a server instead of the<pat:PartName pat:idref="PN-00140"> local server </pat:PartName><pat:PartNumber pat:id="PN-00140">200</pat:PartNumber>,  the two mobile terminals can communicate, assign, and copy contents  information in the same way as described above.  [58]         Digital rights management (DRM) can be applied to contents  moved from the<pat:PartName pat:idref="PN-00141"> local server </pat:PartName><pat:PartNumber pat:id="PN-00141">200</pat:PartNumber>. In detail, used time, reproduction number,  copy restriction, etc. can be applied to contents to which the DRM is applied.  Therefore, when contents are not reproduced, but moved or copied, the user of  the<pat:PartName pat:idref="PN-00142"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00142">100</pat:PartNumber> that receives the contents can use the contents by  paying an amount of money using the license information or the metadata  transferred with the contents. When the<pat:PartName pat:idref="PN-00143"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00143">100</pat:PartNumber> receives the  metadata or license information of the contents without the contents, the  contents can be obtained using the metadata and license information.  [59]         A contents sharing method by a user wherein the contents  having matched metadata are stored in an external mobile terminal will now  be described with reference to FIGS.<pat:PartName pat:idref="PN-00144"> </pat:PartName><pat:PartNumber pat:id="PN-00144">4</pat:PartNumber> and<pat:PartName pat:idref="PN-00145"> </pat:PartName><pat:PartNumber pat:id="PN-00145">5</pat:PartNumber>.  [60]         FIG.<pat:PartName pat:idref="PN-00146"> </pat:PartName><pat:PartNumber pat:id="PN-00146">4</pat:PartNumber> is a flowchart illustrating a contents sharing method  between mobile terminals and a local server according to another exemplary  embodiment of the present invention.</pat:P><pat:P pat:pNumber="30" pat:id="p-30">[61]         For the descriptive convenience, a<pat:PartName pat:idref="PN-00147"> first mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00147">100</pat:PartNumber>  which is a client terminal receiving contents information supports a wireless  LAN, a<pat:PartName pat:idref="PN-00148"> second mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00148">120</pat:PartNumber> is in a local area from the<pat:PartName pat:idref="PN-00149"> first mobile  terminal </pat:PartName><pat:PartNumber pat:id="PN-00149">110</pat:PartNumber> and corresponds to a local server, a<pat:PartName pat:idref="PN-00150"> third mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00150">130</pat:PartNumber> is  an external home PC or DVD, etc. Some metadata of contents stored in the<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="88">12</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='13'?>third<pat:PartName pat:idref="PN-00151"> mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00151">130</pat:PartNumber> is transmitted to the<pat:PartName pat:idref="PN-00152"> second mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00152">120</pat:PartNumber>  (Operation <pat:OCRConfidenceData pat:levelNumber="5">S</pat:OCRConfidenceData>105).  [62]         As illustrated in FIG.<pat:PartName pat:idref="PN-00153"> </pat:PartName><pat:PartNumber pat:id="PN-00153">3</pat:PartNumber>, a user establishes metadata of desired  contents in the<pat:PartName pat:idref="PN-00154"> first mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00154">110</pat:PartNumber> (Operation <pat:OCRConfidenceData pat:levelNumber="5">S</pat:OCRConfidenceData>110).  [63]         In detail, the metadata can be generated by inputting a keyword  of the desired contents in the form of metadata, or analyzing a user's contents  used history through the<pat:PartName pat:idref="PN-00155"> controller </pat:PartName><pat:PartNumber pat:id="PN-00155">10</pat:PartNumber> of the<pat:PartName pat:idref="PN-00156"> first mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00156">110</pat:PartNumber>.  [64]         The<pat:PartName pat:idref="PN-00157"> first mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00157">110</pat:PartNumber> browses a local mobile terminal  or a local server (Operation <pat:OCRConfidenceData pat:levelNumber="5">S</pat:OCRConfidenceData>120).  [65]         While the user ca<pat:OCRConfidenceData pat:levelNumber="66">rr</pat:OCRConfidenceData>ying the<pat:PartName pat:idref="PN-00158"> first mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00158">110</pat:PartNumber> moves,  the<pat:PartName pat:idref="PN-00159"> first mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00159">110</pat:PartNumber> browses the local server, which can exchange  and share metadata, using the<pat:PartName pat:idref="PN-00160"> local communication module </pat:PartName><pat:PartNumber pat:id="PN-00160">50</pat:PartNumber>. The<pat:PartName pat:idref="PN-00161"> local  communication module </pat:PartName><pat:PartNumber pat:id="PN-00161">50</pat:PartNumber> uses a local communication means such as, for  example, Bluetooth or a specific protocol.  [66]         As illustrated in FIG.<pat:PartName pat:idref="PN-00162"> </pat:PartName><pat:PartNumber pat:id="PN-00162">4</pat:PartNumber>, the<pat:PartName pat:idref="PN-00163"> first mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00163">110</pat:PartNumber> requests a  contents share service from the<pat:PartName pat:idref="PN-00164"> base station </pat:PartName><pat:PartNumber pat:id="PN-00164">500</pat:PartNumber> using an available traffic  channel. The<pat:PartName pat:idref="PN-00165"> base station </pat:PartName><pat:PartNumber pat:id="PN-00165">500</pat:PartNumber> confirms whether the local server is within a  server area. If it is confirmed that the<pat:PartName pat:idref="PN-00166"> second mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00166">120</pat:PartNumber>  <pat:OCRConfidenceData pat:levelNumber="8866">corr</pat:OCRConfidenceData>esponding to the local server is within the service area, the<pat:PartName pat:idref="PN-00167"> base station  </pat:PartName><pat:PartNumber pat:id="PN-00167">500</pat:PartNumber> requests the contents share service from the<pat:PartName pat:idref="PN-00168"> second mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00168">120</pat:PartNumber>  using the traffic channel, notifies the<pat:PartName pat:idref="PN-00169"> first mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00169">110</pat:PartNumber> when the  contents share service is approved, and connects the contents share service to  the<pat:PartName pat:idref="PN-00170"> second mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00170">120</pat:PartNumber><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="88">13</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='14'?>[67]         The contents share service is connected between the<pat:PartName pat:idref="PN-00171"> first  mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00171">110</pat:PartNumber> and the<pat:PartName pat:idref="PN-00172"> second mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00172">120</pat:PartNumber>. The<pat:PartName pat:idref="PN-00173"> base station  </pat:PartName><pat:PartNumber pat:id="PN-00173">500</pat:PartNumber> allocates the same traffic channel between the<pat:PartName pat:idref="PN-00174"> first mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00174">110</pat:PartNumber>  and the<pat:PartName pat:idref="PN-00175"> second mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00175">120</pat:PartNumber> (Operation <pat:OCRConfidenceData pat:levelNumber="5">S</pat:OCRConfidenceData>130).  [68]         Metadata established by the user or the<pat:PartName pat:idref="PN-00176"> controller </pat:PartName><pat:PartNumber pat:id="PN-00176">10</pat:PartNumber> is  uploaded through the<pat:PartName pat:idref="PN-00177"> local communication module </pat:PartName><pat:PartNumber pat:id="PN-00177">50</pat:PartNumber> of the<pat:PartName pat:idref="PN-00178"> first mobile  terminal </pat:PartName><pat:PartNumber pat:id="PN-00178">110</pat:PartNumber><pat:PartName pat:idref="PN-00179"> (Operation </pat:PartName><pat:PartNumber pat:id="PN-00179">140</pat:PartNumber>), and is transmitted to the<pat:PartName pat:idref="PN-00180"> second mobile terminal  </pat:PartName><pat:PartNumber pat:id="PN-00180">120</pat:PartNumber> according to the relay of the<pat:PartName pat:idref="PN-00181"> base station </pat:PartName><pat:PartNumber pat:id="PN-00181">500</pat:PartNumber>.  [69]         The<pat:PartName pat:idref="PN-00182"> second mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00182">120</pat:PartNumber> compares metadata stored in  the<pat:PartName pat:idref="PN-00183"> metadata DB </pat:PartName><pat:PartNumber pat:id="PN-00183">30</pat:PartNumber> with metadata information uploaded from the<pat:PartName pat:idref="PN-00184"> first mobile  terminal </pat:PartName><pat:PartNumber pat:id="PN-00184">110</pat:PartNumber> (Operation <pat:OCRConfidenceData pat:levelNumber="5">S</pat:OCRConfidenceData>150).  [70]         If the matching metadata is metadata of contents stored in the<pat:PartName pat:idref="PN-00185">  third mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00185">130</pat:PartNumber>, the<pat:PartName pat:idref="PN-00186"> second mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00186">120</pat:PartNumber> transmits metadata  information including a URI of the contents stored in the<pat:PartName pat:idref="PN-00187"> third mobile terminal  </pat:PartName><pat:PartNumber pat:id="PN-00187">130</pat:PartNumber>, ID information in a P2P network, etc. to the<pat:PartName pat:idref="PN-00188"> first mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00188">110</pat:PartNumber>  through the<pat:PartName pat:idref="PN-00189"> base station </pat:PartName><pat:PartNumber pat:id="PN-00189">500</pat:PartNumber> (Operation <pat:OCRConfidenceData pat:levelNumber="5">S</pat:OCRConfidenceData>160).  [71]         When the<pat:PartName pat:idref="PN-00190"> first mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00190">110</pat:PartNumber> supports a wireless LAN,  the<pat:PartName pat:idref="PN-00191"> first mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00191">110</pat:PartNumber> requests contents corresponding to the matched  metadata to the<pat:PartName pat:idref="PN-00192"> third mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00192">130</pat:PartNumber> through the wireless LAN, and the<pat:PartName pat:idref="PN-00193">  third mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00193">130</pat:PartNumber> transmits the contents to the<pat:PartName pat:idref="PN-00194"> first mobile terminal  </pat:PartName><pat:PartNumber pat:id="PN-00194">110</pat:PartNumber> through the wireless LAN (Operation <pat:OCRConfidenceData pat:levelNumber="5">S</pat:OCRConfidenceData>170).  [72]         When contents of the matching metadata are stored in an  external terminal, if a client mobile terminal supports the wireless LAN, the<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="88">14</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='15'?>user can receive contents stored in the external terminal using the wireless  LAN.</pat:P><pat:P pat:pNumber="31" pat:id="p-31">[73]         FIG.<pat:PartName pat:idref="PN-00195"> </pat:PartName><pat:PartNumber pat:id="PN-00195">5</pat:PartNumber> is a flowchart illustrating a contents sharing method  between mobile terminals and a local server according to another exemplary  embodiment of the present invention.  [74]         The current embodiment is similar to the previous embodiment  illustrated in FIG.<pat:PartName pat:idref="PN-00196"> </pat:PartName><pat:PartNumber pat:id="PN-00196">4</pat:PartNumber> except that the<pat:PartName pat:idref="PN-00197"> first mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00197">110</pat:PartNumber> does not support  a wireless LAN and the<pat:PartName pat:idref="PN-00198"> fourth mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00198">130</pat:PartNumber> supports the wireless LAN.  Thus, overlapping description is omitted.  [75]         Refe<pat:OCRConfidenceData pat:levelNumber="66">rr</pat:OCRConfidenceData>ing to FIG.<pat:PartName pat:idref="PN-00199"> </pat:PartName><pat:PartNumber pat:id="PN-00199">5</pat:PartNumber>, if the<pat:PartName pat:idref="PN-00200"> first mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00200">110</pat:PartNumber> transmits  established metadata to the<pat:PartName pat:idref="PN-00201"> second mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00201">120</pat:PartNumber> (Operation S140), the<pat:PartName pat:idref="PN-00202">  second mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00202">120</pat:PartNumber> compares metadata information stored in the<pat:PartName pat:idref="PN-00203">  metadata DB </pat:PartName><pat:PartNumber pat:id="PN-00203">30</pat:PartNumber> with metadata information uploaded from the<pat:PartName pat:idref="PN-00204"> first mobile  terminal </pat:PartName><pat:PartNumber pat:id="PN-00204">110</pat:PartNumber> (Operation <pat:OCRConfidenceData pat:levelNumber="5">S</pat:OCRConfidenceData>150). When the matching metadata is metadata of  contents stored in the<pat:PartName pat:idref="PN-00205"> third mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00205">130</pat:PartNumber>, the<pat:PartName pat:idref="PN-00206"> second mobile terminal  </pat:PartName><pat:PartNumber pat:id="PN-00206">120</pat:PartNumber> transmits metadata information including a URI of the contents stored in  the<pat:PartName pat:idref="PN-00207"> third mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00207">130</pat:PartNumber>, ID information of a P2P network, etc. to the<pat:PartName pat:idref="PN-00208">  first mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00208">110</pat:PartNumber> through the<pat:PartName pat:idref="PN-00209"> base station </pat:PartName><pat:PartNumber pat:id="PN-00209">500</pat:PartNumber>. The<pat:PartName pat:idref="PN-00210"> first mobile  terminal </pat:PartName><pat:PartNumber pat:id="PN-00210">110</pat:PartNumber> cannot request contents to the<pat:PartName pat:idref="PN-00211"> third mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00211">130</pat:PartNumber> directly  since it does not support the wireless LAN.  [76]         Therefore, a user transmits the metadata information stored in  the<pat:PartName pat:idref="PN-00212"> first mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00212">110</pat:PartNumber> to the<pat:PartName pat:idref="PN-00213"> fourth mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00213">140</pat:PartNumber> supporting the  wireless LAN using a local communication method such as Bluetooth<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="88">15</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='16'?>(Operation <pat:OCRConfidenceData pat:levelNumber="5">S</pat:OCRConfidenceData>180). For example, if the<pat:PartName pat:idref="PN-00214"> fourth mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00214">140</pat:PartNumber> is a user's  home PC, the user transmits the metadata information stored in the<pat:PartName pat:idref="PN-00215"> first  mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00215">110</pat:PartNumber> to the<pat:PartName pat:idref="PN-00216"> fourth mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00216">140</pat:PartNumber> using Bluetooth.  [77]         The<pat:PartName pat:idref="PN-00217">  fourth   mobile  terminal  </pat:PartName><pat:PartNumber pat:id="PN-00217">140</pat:PartNumber>   requests  contents  <pat:OCRConfidenceData pat:levelNumber="8866">corr</pat:OCRConfidenceData>esponding to the matching metadata from the<pat:PartName pat:idref="PN-00218"> third mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00218">130</pat:PartNumber>  through the wireless LAN, and the<pat:PartName pat:idref="PN-00219"> third mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00219">130</pat:PartNumber> transmits the  contents to the<pat:PartName pat:idref="PN-00220"> fourth mobile terminal </pat:PartName><pat:PartNumber pat:id="PN-00220">140</pat:PartNumber> through the<pat:PartName pat:idref="PN-00221"> wireless LAN  (Operation S </pat:PartName><pat:PartNumber pat:id="PN-00221">190</pat:PartNumber>).  [78]         When the contents of the matching metadata are stored in an  external terminal, if a client mobile terminal does not support the wireless  LAN, the user transmits the metadata information to a terminal supporting the  wireless LAN, and receives contents stored in the external terminal using a  terminal supporting the wireless LAN.  [79]         According to an exemplary embodiment of the present  invention, a local server performs a matching operation of metadata. However,  the matching operation can be performed in a client mobile terminal.  [80]         According to another exemplary embodiment of the present  invention, a contents share service is provided in a local area without a user<pat:OCRConfidenceData pat:levelNumber="68">'s</pat:OCRConfidenceData>  intervention. However, the user can carry a mobile terminal and establish the  content share service at a specific time or in a specific place.  [81]         In another exemplary embodiment, the present invention can  also be implemented as computer-readable code on a computer-readable  recording medium. The computer-readable recording medium is any data<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="88">16</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='17'?>storage device that can store data which can thereafter be read by a computer  system. Examples of the computer-readable recording medium include read-  only memory (ROM), random-access memory (RAM), CD-ROMs, magnetic  tapes, floppy disks, optical data storage devices.  [82]        As described above, according to the exemplary embodiment of  the present invention, a contents share method between a mobile terminal and  a local server matches metadata of stored contents through a communication  between the mobile terminal and the local server, thereby sharing contents  desired by the user without the user's intervention.  [83]        Also, the user can communicate desired contents information  with people in a bus, subway, library, etc., which forms a social network, and  produces a contents flow between mobile terminals, thereby creating a new  business model such as contents resale, promotion, etc.  [84]        While the present invention has been particularly shown and  described with reference to exemplary embodiments thereof, it will be  understood by those of ordinary skill in the art that various changes in form  and details may be made therein without departing from the spirit and scope of  the present invention as defined by the following claims.</pat:P><pat:P pat:pNumber="32" pat:id="p-32"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="88">17</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData></pat:P></pat:Specification></pat:SpecificationDocument>

applicant/15414059.xml

@@ -0,0 +1,2 @@
+<?xml version="1.0" encoding="utf-8"?><uspat:SpecificationDocument xmlns:uscom="urn:us:gov:doc:uspto:common" xmlns:uspat="urn:us:gov:doc:uspto:patent" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:com="http://www.wipo.int/standards/XMLSchema/ST96/Common" xmlns:pat="http://www.wipo.int/standards/XMLSchema/ST96/Patent" uscom:vendorName="VASTEC" uscom:createDateTime="2018-12-07T11:58:14Z" com:st96Version="V2_1" com:ipoVersion="US_V7_1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent Patent/V7_1/Schema/USPatent/Document/SpecificationDocument_V7_1.xsd" com:documentFileName="15414059.12-04-2018.JPCVM3ANLXEAPX0.SPEC.XML" com:id="JPCVM3ANLXEAPX0">
+<uspat:DocumentMetadata com:id="ID0000001"><uscom:DocumentCode>SPEC</uscom:DocumentCode><uscom:ApplicationNumberText uscom:electronicText="15414059">15414059</uscom:ApplicationNumberText><com:PageTotalQuantity>1</com:PageTotalQuantity><uscom:ParagraphTotalQuantity>3</uscom:ParagraphTotalQuantity><uscom:OfficialDate>2018-12-04</uscom:OfficialDate></uspat:DocumentMetadata><?PageStart number='1'?><uscom:P com:pNumber="1" com:id="p-1">Serial No. 15/414,059                -<uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">2</uscom:OCRConfidenceData>-                     <uscom:PartName com:idrefs="PN-00001">Art Unit: </uscom:PartName><uscom:PartNumber com:id="PN-00001">2133</uscom:PartNumber></uscom:P><uscom:P com:pNumber="2" com:id="p-2"><com:U>In the Specification:</com:U></uscom:P><uscom:P com:pNumber="3" com:id="p-3">Change the Title of the Invention to: DELET<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">I</uscom:OCRConfidenceData>NG AN OBJECT FROM AN OBJECT STORAGE SUBSYSTEM FOR MANAGING PAGED METADATA</uscom:P></uspat:SpecificationDocument>

applicant/15445917.xml

@@ -0,0 +1,2 @@
+<?xml version="1.0" encoding="utf-8"?><uspat:SpecificationDocument xmlns:uscom="urn:us:gov:doc:uspto:common" xmlns:uspat="urn:us:gov:doc:uspto:patent" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:com="http://www.wipo.int/standards/XMLSchema/ST96/Common" xmlns:pat="http://www.wipo.int/standards/XMLSchema/ST96/Patent" uscom:vendorName="VASTEC" uscom:createDateTime="2022-11-30T03:43:07Z" com:st96Version="V2_1" com:ipoVersion="US_V7_1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent Patent/V7_1/Schema/USPatent/Document/SpecificationDocument_V7_1.xsd" com:documentFileName="15445917.11-28-2022.LB1KMNCLXBLUEX0.SPEC.XML" com:id="LB1KMNCLXBLUEX0">
+<uspat:DocumentMetadata com:id="ID0000001"><uscom:DocumentCode>SPEC</uscom:DocumentCode><uscom:ApplicationNumberText uscom:electronicText="15445917">15445917</uscom:ApplicationNumberText><com:PageTotalQuantity>1</com:PageTotalQuantity><uscom:ParagraphTotalQuantity>12</uscom:ParagraphTotalQuantity><uscom:OfficialDate>2022-11-28</uscom:OfficialDate></uspat:DocumentMetadata><?PageStart number='1'?><uscom:Heading com:id="h-1">PATENT</uscom:Heading><uscom:P com:pNumber="1" com:id="p-1">Application No.: 15/445,917                        Attorney Docket No.: 0715150.841-US2</uscom:P><uscom:P com:pNumber="2" com:id="p-2"><com:U>Amendments to the Specification:</com:U></uscom:P><uscom:P com:pNumber="3" com:id="p-3" uscom:indentationLevelNumber="L1">Please replace paragraph [0046] with the following amended version of that paragraph:</uscom:P><uscom:P com:pNumber="4" com:id="p-4" uscom:indentationLevelNumber="L2">FIG. 4 is block diagram illustrating a data structure for a <uscom:PartName com:idrefs="PN-00001">lighting map </uscom:PartName><uscom:PartNumber com:id="PN-00001">400</uscom:PartNumber></uscom:P><uscom:P com:pNumber="5" com:id="p-5" uscom:indentationLevelNumber="L1">associated with a user, in accordance with some implementations. In some</uscom:P><uscom:P com:pNumber="6" com:id="p-6" uscom:indentationLevelNumber="L1">implementations, the <uscom:PartName com:idrefs="PN-00002">lighting map </uscom:PartName><uscom:PartNumber com:id="PN-00002">400</uscom:PartNumber> includes at least a <uscom:PartName com:idrefs="PN-00003">device name </uscom:PartName><uscom:PartNumber com:id="PN-00003">402</uscom:PartNumber> or device id or</uscom:P><uscom:P com:pNumber="7" com:id="p-7" uscom:indentationLevelNumber="L1">other mechanism for identifying a particular device associated with a user. The</uscom:P><uscom:P com:pNumber="8" com:id="p-8" uscom:indentationLevelNumber="L1"><uscom:PartName com:idrefs="PN-00004">position </uscom:PartName><uscom:PartNumber com:id="PN-00004">404</uscom:PartNumber> (e.g., GPS location) of the device is <com:Del>includes </com:Del><com:U>included.</com:U> Some devices such as TVs, clocks, and digital picture frame remain relatively static. Other devices such as phones, tablets, and wearable devices (e.g., smart watches) should be queried/confirmed prior to utilizing them to satisfy a user's lighting need. The <uscom:PartName com:idrefs="PN-00005">device's orientation </uscom:PartName><uscom:PartNumber com:id="PN-00005">406</uscom:PartNumber> may also be recorded. In some implementations the orientation includes the directional facing</uscom:P><uscom:P com:pNumber="9" com:id="p-9" uscom:indentationLevelNumber="L1">of a display screen of the device. The <uscom:PartName com:idrefs="PN-00006">device's state </uscom:PartName><uscom:PartNumber com:id="PN-00006">408</uscom:PartNumber> is also recorded (e.g., on/off) in</uscom:P><uscom:P com:pNumber="10" com:id="p-10" uscom:indentationLevelNumber="L1">some implementations, a level of brightness/dimness is also recorded. Additional</uscom:P><uscom:P com:pNumber="11" com:id="p-11" uscom:indentationLevelNumber="L1"><uscom:PartName com:idrefs="PN-00007">information </uscom:PartName><uscom:PartNumber com:id="PN-00007">410</uscom:PartNumber> may also be stored in the lighting map.</uscom:P><uscom:P com:pNumber="12" com:id="p-12" uscom:indentationLevelNumber="L3"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">2</uscom:OCRConfidenceData></uscom:P></uspat:SpecificationDocument>

applicant/15799115.xml

@@ -0,0 +1,126 @@
+<?xml version="1.0" encoding="utf-8"?><uspat:SpecificationDocument xmlns:uscom="urn:us:gov:doc:uspto:common" xmlns:uspat="urn:us:gov:doc:uspto:patent" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:com="http://www.wipo.int/standards/XMLSchema/ST96/Common" xmlns:pat="http://www.wipo.int/standards/XMLSchema/ST96/Patent" uscom:vendorName="VASTEC" uscom:createDateTime="2017-10-31T19:41:55Z" com:st96Version="V2_1" com:ipoVersion="US_V7_1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent Patent/V7_1/Schema/USPatent/Document/SpecificationDocument_V7_1.xsd" com:documentFileName="15799115.10-31-2017.J9FZRZU0RXEAPX4.SPEC.XML" com:id="J9FZRZU0RXEAPX4">
+<uspat:DocumentMetadata com:id="ID0000001"><uscom:DocumentCode>SPEC</uscom:DocumentCode><uscom:ApplicationNumberText uscom:electronicText="15799115">15799115</uscom:ApplicationNumberText><com:PageTotalQuantity>25</com:PageTotalQuantity><uscom:ParagraphTotalQuantity>166</uscom:ParagraphTotalQuantity><uscom:OfficialDate>2017-10-31</uscom:OfficialDate></uspat:DocumentMetadata><?PageStart number='1'?><uscom:P com:pNumber="1" com:id="p-1">Attorney Docket No.                       ORACLE CONFIDENTIAL</uscom:P><uscom:P com:pNumber="2" com:id="p-2">T9049-22733U<uscom:OCRConfidenceData uscom:ocrConfidenceCode="588">S01</uscom:OCRConfidenceData></uscom:P><uscom:Heading com:id="h-1">UNITED STATES PATENT APPLICATION</uscom:Heading><uscom:P com:pNumber="3" com:id="p-3" uscom:indentationLevelNumber="L4">FOR</uscom:P><uscom:Heading com:id="h-2">DEMAND FORECASTING USING WEIGHTED MIXED MACHINE LEARNING</uscom:Heading><uscom:P com:pNumber="4" com:id="p-4" uscom:indentationLevelNumber="L4">MODELS</uscom:P><uscom:Heading com:id="h-3">INVENTORS:</uscom:Heading><uscom:P com:pNumber="5" com:id="p-5" uscom:indentationLevelNumber="L4">Ming LE<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">I</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="6" com:id="p-6" uscom:indentationLevelNumber="L3">Catalin POPESCU PREPARED BY: MILES &amp; STOCKBRIDGE P.C.</uscom:P><uscom:Heading com:id="h-4">ASSIGNEE:  ORACLE INTERNAT<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">I</uscom:OCRConfidenceData>ONAL CORPORATION</uscom:Heading><uscom:P com:pNumber="7" com:id="p-7" uscom:indentationLevelNumber="L2">500 ORACLE PARKWAY REDWOOD SHORES, CA 94065</uscom:P><uscom:P com:pNumber="8" com:id="p-8">Oracle Matter No.<uscom:BoundaryDataReference com:idref="HDR-00001"/></uscom:P><?PageStart number='2'?><uscom:Heading com:id="h-5">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-6">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00002"/>
+<uscom:Heading com:id="h-7">DEMAND FORECASTING USING WEIGHTED MIXED MACHINE LEARNING</uscom:Heading><uscom:P com:pNumber="10" com:id="p-10" uscom:indentationLevelNumber="L4">MODELS</uscom:P><uscom:Heading com:id="h-8">FIELD</uscom:Heading><uscom:P com:pNumber="11" com:id="p-11" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0001] One embodiment is directed generally to a computer system, and in particular to a computer system that forecasts demand.</uscom:P><uscom:Heading com:id="h-9">BACKGROUND INFORMATION</uscom:Heading><uscom:P com:pNumber="12" com:id="p-12" uscom:indentationLevelNumber="L1">[0002] Products are typically delivered to consumers through a network of</uscom:P><uscom:P com:pNumber="13" com:id="p-13">manufacturers, distributors, transporters, retailers, etc. Such a network of facilities that together deliver products to consumers is commonly referred to as a "supply chain" network</uscom:P><uscom:P com:pNumber="14" com:id="p-14" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0003] Suppliers of products (e.g., manufactures, vendors, retailers, etc.) often face the task of forecasting the demand for the products in order to provide a smooth and efficient flow of the products through the supply chain network in the presence of<uscom:BoundaryDataReference com:idref="HDR-00003"/></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00004"/>
+<?PageStart number='3'?><uscom:Heading com:id="h-10">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-11">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00005"/>
+<uscom:P com:pNumber="17" com:id="p-17">constantly-changing market conditions. Overestimating the demand can result in overproduction and increased costs associated with holding inventories (e.g., storage costs, obsolescence, etc.). Underestimating the demand, on the other hand, can result in lost revenues.</uscom:P><uscom:P com:pNumber="18" com:id="p-18" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0004] Further, in the retail industry, retailers need to predict their demand in the future to better manage their inventory or promotion/markdown planning. Retailers may engage in many types of promotion to boost their sales. To generate an accurate forecast, a retailer has to consider all factors which could impact the demand, such as promotions, price, seasonality, weather, etc.</uscom:P><uscom:P com:pNumber="19" com:id="p-19" uscom:indentationLevelNumber="L1">[0005] One technique for forecasting demand for a product is to forecast the</uscom:P><uscom:P com:pNumber="20" com:id="p-20">demand based primarily on historical demand information for that product (e.g., based on past purchase orders, past shipments, past point-of-sales data, and so on). However, such a technique may poorly adapt to the ever-changing market conditions and can result in an inaccurate forecast. Further, with more and more factors to consider, the traditional forecast method such as time series analysis or regression does not work very well.</uscom:P><uscom:Heading com:id="h-12">SUMMARY</uscom:Heading><uscom:P com:pNumber="21" com:id="p-21" uscom:indentationLevelNumber="L1">[0006] Embodiments forecast demand of an item by receiving historical sales</uscom:P><uscom:P com:pNumber="22" com:id="p-22">data for the item for a plurality of past time periods, the historical sales data including a plurality of features that define one or more feature sets. Embodiments use the feature sets as inputs to one or more different algorithms to generate a plurality of different<uscom:BoundaryDataReference com:idref="HDR-00006"/></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00007"/>
+<?PageStart number='4'?><uscom:Heading com:id="h-13">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-14">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00008"/>
+<uscom:P com:pNumber="25" com:id="p-25">models. Embodiments train each of the different models with a same training set to generate a plurality of trained models. Embodiments use each of the trained models to generate a plurality of past demand forecasts for each of some or all of the past time periods and generate a plurality of future demand forecasts for each of future time periods. Embodiments determine a root-mean-square error ("RMSE") for each of the past demand forecasts and, based on the RMSE, determine a weight for each of the trained models and normalize each weight. Embodiments then generate a final demand forecast for the item for each future time period by combining a weighted value for each trained model.</uscom:P><uscom:Heading com:id="h-15">BRIEF DESCRIPTION OF THE DRAWINGS</uscom:Heading><uscom:P com:pNumber="26" com:id="p-26" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0007] Fig. 1 is a block diagram of a computer server/system in accordance with an embodiment of the present invention.</uscom:P><uscom:P com:pNumber="27" com:id="p-27" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0008] Fig. 2 is a flow diagram of the functionality of the demand forecast module of Fig. 1 when determining a demand forecast in accordance with one embodiment.</uscom:P><uscom:P com:pNumber="28" com:id="p-28" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0009] Figs. 3 and 4 illustrate a numerical example of determined demand forecasts for a single SKU in accordance with embodiments of the invention.</uscom:P><uscom:P com:pNumber="29" com:id="p-29" uscom:indentationLevelNumber="L1">[0010] Fig. 5 illustrates an integrated manufacturing, inventory and logistics</uscom:P><uscom:P com:pNumber="30" com:id="p-30">system that includes demand forecasting as disclosed herein in accordance with one embodiment.</uscom:P><uscom:BoundaryDataReference com:idref="HDR-00009"/>
+<uscom:BoundaryDataReference com:idref="HDR-00010"/>
+<?PageStart number='5'?><uscom:Heading com:id="h-16">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-17">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00011"/>
+<uscom:Heading com:id="h-18">DETAILED DESCRIPTION</uscom:Heading><uscom:P com:pNumber="34" com:id="p-34" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0011] One embodiment forecasts a demand of a product by training multiple algorithms/methods and multiple features using historical sales data input resulting in multiple trained models, and then weighting each of the trained models based on an error value. Using the weights and the multiple models, the demand forecast is generated by combining a weighted forecast generated by each of the trained models.</uscom:P><uscom:P com:pNumber="35" com:id="p-35" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0012] Sales and demand forecasting methods can roughly be grouped into judgmental, extrapolation, and causal methods. Extrapolation methods use only the time series data of the activity itself to generate the forecast. Known particular algorithms/methods range from the simpler moving averages and exponential smoothing methods to the more complicated Box-Jenkins approach. While these known methods identify and extrapolate time series patterns of trend, seasonality and autocorrelation successfully, they do not take external factors such as price changes and promotion into account.</uscom:P><uscom:P com:pNumber="36" com:id="p-36" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0013] Vector Auto Regression ("VAR") methods extend the Box-Jenkins methods to include other variables, but their complexity makes estimation difficult. Causal forecasting involves building quantitative models using inputs representing the phenomena that are believed to be drivers of the outcome. The methods can be as simple as a linear regression algorithm with promotion variables. A starting point is a regression model with promotion variables such as price cuts, rebates or advertisements. The idea is that model simplicity helps managers to understand and approve or guide modification of the models, and as they become more knowledgeable<uscom:BoundaryDataReference com:idref="HDR-00012"/></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00013"/>
+<?PageStart number='6'?><uscom:Heading com:id="h-19">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-20">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00014"/>
+<uscom:P com:pNumber="39" com:id="p-39">about a decision aid, they may be ready to implement more sophisticated and complex models.</uscom:P><uscom:P com:pNumber="40" com:id="p-40" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0014] In order to improved demand forecasting, retailers have begun to move to modern machine learning technologies, such as support vector machine ("SVM"), artificial neural network ("ANN"), random forest, and so on. However, typically a retailer will just pick one model for each product/location. As used herein, a retailer can include a single retail store, or can include a large amount of retail stores all integrated and managed by single or multiple logistic operations.</uscom:P><uscom:P com:pNumber="41" com:id="p-41" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0015] Further, for many machine learning algorithms (SVM, ANN, random forest, etc.), retailers will use the feature set to define the data point at the product<uscom:OCRConfidenceData uscom:ocrConfidenceCode="4">/</uscom:OCRConfidenceData>location/calendar intersection. In these algorithms, retailers will train the model with the same feature set as it does for forecasting. Further, the same feature set could be used by several different algorithms for forecast. A "feature set" is the collection of features that impact the demand for an item. Examples of features are price, seasonality, brand, promotions, size, color, pack size, supplier, length, etc. While features such as price and seasonality may be relevant for all types of products, some others are item specific. For example, pack size impacts the demand for yogurts, however the length is insignificant. Conversely, the brand is very important for fashion items, but is much less important for hardware items, such as nails or hammers.</uscom:P><uscom:P com:pNumber="42" com:id="p-42" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0016] In contrast with known approaches for demand forecasting that only select one model for each product<uscom:OCRConfidenceData uscom:ocrConfidenceCode="4">/</uscom:OCRConfidenceData>location, embodiments use multiple different trained models together to predict the demand for the retailer, and then generate weights using novel<uscom:BoundaryDataReference com:idref="HDR-00015"/></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00016"/>
+<?PageStart number='7'?><uscom:Heading com:id="h-21">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-22">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00017"/>
+<uscom:P com:pNumber="45" com:id="p-45">rules/algorithms that are used to combine the results.</uscom:P><uscom:P com:pNumber="46" com:id="p-46" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0017] Fig. 1 is a block diagram of a <uscom:PartName com:idrefs="PN-00001">computer server/system </uscom:PartName><uscom:PartNumber com:id="PN-00001">10</uscom:PartNumber> in accordance with an embodiment of the present invention. Although shown as a single system, the functionality of <uscom:PartName com:idrefs="PN-00002">system </uscom:PartName><uscom:PartNumber com:id="PN-00002">10</uscom:PartNumber> can be implemented as a distributed system. Further, the functionality disclosed herein can be implemented on separate servers or devices that may be coupled together over a network. Further, one or more components of <uscom:PartName com:idrefs="PN-00003">system </uscom:PartName><uscom:PartNumber com:id="PN-00003">10</uscom:PartNumber> may not be included. For example, for functionality of a <uscom:PartName com:idrefs="PN-00004">server, system </uscom:PartName><uscom:PartNumber com:id="PN-00004">10</uscom:PartNumber> may need to include a processor and memory, but may not include one or more of the other components shown in Fig. 1, such as a keyboard or display.</uscom:P><uscom:P com:pNumber="47" com:id="p-47" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0018] <uscom:PartName com:idrefs="PN-00005">System </uscom:PartName><uscom:PartNumber com:id="PN-00005">10</uscom:PartNumber> includes a <uscom:PartName com:idrefs="PN-00006">bus </uscom:PartName><uscom:PartNumber com:id="PN-00006">12</uscom:PartNumber> or other communication mechanism for communicating information, and a <uscom:PartName com:idrefs="PN-00007">processor </uscom:PartName><uscom:PartNumber com:id="PN-00007">22</uscom:PartNumber> coupled to <uscom:PartName com:idrefs="PN-00008">bus </uscom:PartName><uscom:PartNumber com:id="PN-00008">12</uscom:PartNumber> for processing information. <uscom:PartName com:idrefs="PN-00009">Processor </uscom:PartName><uscom:PartNumber com:id="PN-00009">22</uscom:PartNumber> may be any type of general or specific purpose processor. <uscom:PartName com:idrefs="PN-00010">System </uscom:PartName><uscom:PartNumber com:id="PN-00010">10</uscom:PartNumber> further includes a <uscom:PartName com:idrefs="PN-00011">memory </uscom:PartName><uscom:PartNumber com:id="PN-00011">14</uscom:PartNumber> for storing information and instructions to be executed by <uscom:PartName com:idrefs="PN-00012">processor </uscom:PartName><uscom:PartNumber com:id="PN-00012">22.</uscom:PartNumber> <uscom:PartName com:idrefs="PN-00013">Memory </uscom:PartName><uscom:PartNumber com:id="PN-00013">14</uscom:PartNumber> can be comprised of any combination of random access memory ("RAM"), read only memory ("ROM"), static storage such as a magnetic or optical disk, or any other type of computer readable media. <uscom:PartName com:idrefs="PN-00014">System </uscom:PartName><uscom:PartNumber com:id="PN-00014">10</uscom:PartNumber> further includes a <uscom:PartName com:idrefs="PN-00015">communication device </uscom:PartName><uscom:PartNumber com:id="PN-00015">20,</uscom:PartNumber> such as a network interface card, to provide access to a network. Therefore, a user may interface with <uscom:PartName com:idrefs="PN-00016">system </uscom:PartName><uscom:PartNumber com:id="PN-00016">10</uscom:PartNumber> directly, or remotely through a network, or any other method.</uscom:P><uscom:P com:pNumber="48" com:id="p-48" uscom:indentationLevelNumber="L1">[0019] Computer readable media may be any available media that can be</uscom:P><uscom:P com:pNumber="49" com:id="p-49">accessed by <uscom:PartName com:idrefs="PN-00017">processor </uscom:PartName><uscom:PartNumber com:id="PN-00017">22</uscom:PartNumber> and includes both volatile and nonvolatile media, removable and non-removable media, and communication media. Communication media may<uscom:BoundaryDataReference com:idref="HDR-00018"/></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00019"/>
+<?PageStart number='8'?><uscom:Heading com:id="h-23">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-24">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00020"/>
+<uscom:P com:pNumber="52" com:id="p-52">include 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.</uscom:P><uscom:P com:pNumber="53" com:id="p-53" uscom:indentationLevelNumber="L1">[0020] <uscom:PartName com:idrefs="PN-00018">Processor </uscom:PartName><uscom:PartNumber com:id="PN-00018">22</uscom:PartNumber> is further coupled via <uscom:PartName com:idrefs="PN-00019">bus </uscom:PartName><uscom:PartNumber com:id="PN-00019">12</uscom:PartNumber> to a <uscom:PartName com:idrefs="PN-00020">display </uscom:PartName><uscom:PartNumber com:id="PN-00020">24,</uscom:PartNumber> such as a</uscom:P><uscom:P com:pNumber="54" com:id="p-54">Liquid Crystal Display ("LCD"). A <uscom:PartName com:idrefs="PN-00021">keyboard </uscom:PartName><uscom:PartNumber com:id="PN-00021">26</uscom:PartNumber> and a <uscom:PartName com:idrefs="PN-00022">cursor control device </uscom:PartName><uscom:PartNumber com:id="PN-00022">28,</uscom:PartNumber> such as a computer mouse, are further coupled to <uscom:PartName com:idrefs="PN-00023">bus </uscom:PartName><uscom:PartNumber com:id="PN-00023">12</uscom:PartNumber> to enable a user to interface with <uscom:PartName com:idrefs="PN-00024">system </uscom:PartName><uscom:PartNumber com:id="PN-00024">10.</uscom:PartNumber></uscom:P><uscom:P com:pNumber="55" com:id="p-55" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0021] In one <uscom:PartName com:idrefs="PN-00025">embodiment, memory </uscom:PartName><uscom:PartNumber com:id="PN-00025">14</uscom:PartNumber> stores software modules that provide functionality when executed by <uscom:PartName com:idrefs="PN-00026">processor </uscom:PartName><uscom:PartNumber com:id="PN-00026">22.</uscom:PartNumber> The modules include an <uscom:PartName com:idrefs="PN-00027">operating system </uscom:PartName><uscom:PartNumber com:id="PN-00027">15</uscom:PartNumber> that provides operating system functionality for <uscom:PartName com:idrefs="PN-00028">system </uscom:PartName><uscom:PartNumber com:id="PN-00028">10.</uscom:PartNumber> The modules further include a <uscom:PartName com:idrefs="PN-00029">promotion effects module </uscom:PartName><uscom:PartNumber com:id="PN-00029">16</uscom:PartNumber> that determines demand forecasting, and all other functionality disclosed herein. <uscom:PartName com:idrefs="PN-00030">System </uscom:PartName><uscom:PartNumber com:id="PN-00030">10</uscom:PartNumber> can be part of a larger system. Therefore, <uscom:PartName com:idrefs="PN-00031">system </uscom:PartName><uscom:PartNumber com:id="PN-00031">10</uscom:PartNumber> can include one or more additional <uscom:PartName com:idrefs="PN-00032">functional modules </uscom:PartName><uscom:PartNumber com:id="PN-00032">18</uscom:PartNumber> to include the additional functionality, such as a retail management system (e.g., the "Oracle Retail Demand Forecasting System" or the "Oracle Retail Advanced Science Engine" ("ORASE") from Oracle Corp.) or an enterprise resource planning ("ERP") system. A <uscom:PartName com:idrefs="PN-00033">database </uscom:PartName><uscom:PartNumber com:id="PN-00033">17</uscom:PartNumber> is coupled to <uscom:PartName com:idrefs="PN-00034">bus </uscom:PartName><uscom:PartNumber com:id="PN-00034">12</uscom:PartNumber> to provide centralized storage for <uscom:PartName com:idrefs="PN-00035">modules </uscom:PartName><uscom:PartNumber com:id="PN-00035">16 and 18</uscom:PartNumber> and store customer data, product data, transactional data, etc. In one <uscom:PartName com:idrefs="PN-00036">embodiment, database </uscom:PartName><uscom:PartNumber com:id="PN-00036">17</uscom:PartNumber> is a relational database management system ("RDBMS") that can use Structured Query Language ("SQL") to manage the stored data. In one embodiment, a specialized point of <uscom:PartName com:idrefs="PN-00037">sale ("POS") terminal </uscom:PartName><uscom:PartNumber com:id="PN-00037">100</uscom:PartNumber> generates the transactional data and historical sales data (e.g., data concerning transactions of each<uscom:BoundaryDataReference com:idref="HDR-00021"/></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00022"/>
+<?PageStart number='9'?><uscom:Heading com:id="h-25">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-26">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00023"/>
+<uscom:P com:pNumber="58" com:id="p-58">item/SKU at each retail store) used to forecast demand. <uscom:PartName com:idrefs="PN-00038">POS terminal </uscom:PartName><uscom:PartNumber com:id="PN-00038">100</uscom:PartNumber> itself can include additional processing functionality to forecast demand in accordance with one embodiment.</uscom:P><uscom:P com:pNumber="59" com:id="p-59" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0022] In one embodiment, particularly when there are a large number of retail stores, a large number of items, and a large amount of <uscom:PartName com:idrefs="PN-00039">historical data, database </uscom:PartName><uscom:PartNumber com:id="PN-00039">17</uscom:PartNumber> is implemented as an in-memory database ("IMDB"). An IMDB is a database management system that primarily relies on main memory for computer data storage. It is contrasted with database management systems that employ a disk storage mechanism. Main memory databases are faster than disk-optimized databases because disk access is slower than memory access, the internal optimization algorithms are simpler and execute fewer CPU instructions. Accessing data in memory eliminates seek time when querying the data, which provides faster and more predictable performance than disk.</uscom:P><uscom:P com:pNumber="60" com:id="p-60" uscom:indentationLevelNumber="L1">[0023] In one <uscom:PartName com:idrefs="PN-00040">embodiment, database </uscom:PartName><uscom:PartNumber com:id="PN-00040">17,</uscom:PartNumber> when implemented as a IMDB, is</uscom:P><uscom:P com:pNumber="61" com:id="p-61">implemented based on a distributed data grid. A distributed data grid is a system in which a collection of computer servers work together in one or more clusters to manage information and related operations, such as computations, within a distributed or clustered environment. A distributed data grid can be used to manage application objects and data that are shared across the servers. A distributed data grid provides low response time, high throughput, predictable scalability, continuous availability, and information reliability. In particular examples, distributed data grids, such as, e.g., the "Oracle Coherence" data grid from Oracle Corp., store information in-memory to<uscom:BoundaryDataReference com:idref="HDR-00024"/></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00025"/>
+<?PageStart number='10'?><uscom:Heading com:id="h-27">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-28">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00026"/>
+<uscom:P com:pNumber="64" com:id="p-64">achieve higher performance, and employ redundancy in keeping copies of that information synchronized across multiple servers, thus ensuring resiliency of the system and continued availability of the data in the event of failure of a server.</uscom:P><uscom:P com:pNumber="65" com:id="p-65" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0024] In one <uscom:PartName com:idrefs="PN-00041">embodiment, system </uscom:PartName><uscom:PartNumber com:id="PN-00041">10</uscom:PartNumber> is a computing/data processing system including an application or collection of distributed applications for enterprise organizations, and may also implement logistics, manufacturing, and inventory management functionality. The applications and computing <uscom:PartName com:idrefs="PN-00042">system </uscom:PartName><uscom:PartNumber com:id="PN-00042">10</uscom:PartNumber> may be configured to operate with or be implemented as a cloud-based networking system, a software-as-a-service ("<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5885">SaaS</uscom:OCRConfidenceData>") architecture, or other type of computing solution.</uscom:P><uscom:P com:pNumber="66" com:id="p-66" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0025] Embodiments use the multiple trained models generated from one or more different algorithms in order to estimate a sales forecast or a demand forecast. The forecast is an important driver of the supply chain. If a forecast is inaccurate, allocation and replenishment perform poorly, resulting in financial loss for the retailer. Improvements in forecast accuracy for promoted or non-promoted items may be achieved by the embodiments disclosed herein. Further, a better understanding of the impact a promotion has on demand may be achieved. This helps the retailer to more effectively plan promotions with respect to channel, pricing, and customer segments, for example.</uscom:P><uscom:P com:pNumber="67" com:id="p-67" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0026] Embodiments are disclosed from the perspective that, for an item (e.g., a retail item represented by an SKU) sold at a location (e.g., a retail location), the item may be promoted in various ways at various times (i.e., pre-defined retail periods, such as a day, week, month, year, etc.). A retail calendar has many retail periods (e.g.,<uscom:BoundaryDataReference com:idref="HDR-00027"/></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00028"/>
+<?PageStart number='11'?><uscom:Heading com:id="h-29">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-30">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00029"/>
+<uscom:P com:pNumber="70" com:id="p-70">weeks) that are organized in a particular manner (e.g., four (4) thirteen (13) week quarters) over a typical calendar year. A retail period may occur in the past or in the future. Historical sales/performance data may include, for example, a number of units of an item sold in each of a plurality of past retail periods as well as associated promotion data (i.e., for each retail period, which promotions were in effect for that period).</uscom:P><uscom:P com:pNumber="71" com:id="p-71" uscom:indentationLevelNumber="L1">[0027]As disclosed below, embodiments use one or more trained models</uscom:P><uscom:P com:pNumber="72" com:id="p-72">generated from one or more different algorithms and generate weights for the trained models. Trained models used in some embodiments can include trained linear regression models or machine learning techniques, such as decision or regression trees, Support Vector Machines ("SVM") or neural networks.</uscom:P><uscom:P com:pNumber="73" com:id="p-73" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0028] In connection with trained linear regression models, generated from a linear regression algorithm trained with different inputs, the search for a linear relationship between an output variable and multiple input variables has resulted in stepwise selection of input variables in a regression setting. In some embodiments, the goal is to build a function that expresses the output variable as a linear function of the input variables plus a constant. Two general approaches in stepwise regression are forward and backward selection.</uscom:P><uscom:P com:pNumber="74" com:id="p-74" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0029] In forward selection, variables are introduced one at a time based on their contribution to the model according to a pre-determined criterion. In backward selection, all input variables are built into the model to begin with, and then input variables are removed from the regression equation if they are judged as not<uscom:BoundaryDataReference com:idref="HDR-00030"/></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00031"/>
+<?PageStart number='12'?><uscom:Heading com:id="h-31">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-32">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00032"/>
+<uscom:P com:pNumber="77" com:id="p-77">contributing to the model, again based on a predetermined criterion.</uscom:P><uscom:P com:pNumber="78" com:id="p-78" uscom:indentationLevelNumber="L1">[0030] In machine learning, SVMs are supervised learning models with</uscom:P><uscom:P com:pNumber="79" com:id="p-79">associated learning algorithms that analyze data used for classification and regression analysis. Given a set of training examples, each marked as belonging to one or the other of two categories, an SVM training algorithm builds a model that assigns new examples to one category or the other, making it a non-probabilistic binary linear classifier. An SVM model is a representation of the examples as points in space, mapped so that the examples of the separate categories are divided by a clear gap that is as wide as possible. New examples are then mapped into that same space and predicted to belong to a category based on which side of the gap they fall.</uscom:P><uscom:P com:pNumber="80" com:id="p-80" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0031] In addition to classification, SVMs have been successfully applied in sales or demand forecasting, being able to process common metrics, such as sales, as well as price, promotions, external factors such as weather and demographic information.</uscom:P><uscom:P com:pNumber="81" com:id="p-81" uscom:indentationLevelNumber="L1">[0032] SVM and its regression version of Support Vector Regression ("SVR")</uscom:P><uscom:P com:pNumber="82" com:id="p-82">implicitly map instances into a higher dimensional feature space using kernel functions. In its most basic form, SVR ideally seeks to identify a linear function in this space that is within a distance to the mapped output points. This "soft margin formulation" allows and penalizes deviations beyond the pre-determined distance, and minimizes the sum of violations along with the norm of the vector that identifies the linear relationship</uscom:P><uscom:P com:pNumber="83" com:id="p-83" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0033]A regression tree technique partitions the data into smaller subsets in a decision tree format and fits a linear regression model at every leaf that is used to predict the outcome. Alternative model tree approaches differ from each other mainly in<uscom:BoundaryDataReference com:idref="HDR-00033"/></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00034"/>
+<?PageStart number='13'?><uscom:Heading com:id="h-33">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-34">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00035"/>
+<uscom:P com:pNumber="86" com:id="p-86">the choice criteria of the input variable to be branched on, split criteria used, and the models constructed at every leaf of the tree. While trees are transparent in the sense that the prediction for a particular case can be traced back to the conditions in the tree and the regression function that is applicable for cases that satisfy those conditions, trees with many layers are not easy to interpret in a generalizable manner.</uscom:P><uscom:P com:pNumber="87" com:id="p-87" uscom:indentationLevelNumber="L1">[0034] An Artificial Neural Network ("ANN") is an information processing</uscom:P><uscom:P com:pNumber="88" com:id="p-88">paradigm that is inspired by the way biological nervous systems, such as the brain, process information. The key element of this model is the novel structure of the information processing system. It is composed of a large number of highly interconnected processing elements (i.e., neurons) working in unison to solve specific problems. ANNs learn by example. An ANN is configured for a specific application, such as pattern recognition or data classification, through a learning process. Learning in biological systems involves adjustments to the synaptic connections that exist between the neurons. This is true of ANNs as well. Since neural networks are best at identifying patterns or trends in data, they are well suited for prediction or forecasting needs.</uscom:P><uscom:P com:pNumber="89" com:id="p-89" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0035] Fig. 2 is a flow diagram of the functionality of <uscom:PartName com:idrefs="PN-00043">demand forecast module </uscom:PartName><uscom:PartNumber com:id="PN-00043">16</uscom:PartNumber> of Fig. 1 when determining a demand forecast in accordance with one embodiment. In one embodiment, the functionality of the flow diagram of Fig. 2 is implemented by software stored in memory or other computer readable or tangible medium, and executed by a processor. In other embodiments, the functionality may be performed by hardware (e.g., through the use of an application specific integrated circuit ("ASIC"), a<uscom:BoundaryDataReference com:idref="HDR-00036"/></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00037"/>
+<?PageStart number='14'?><uscom:Heading com:id="h-35">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-36">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00038"/>
+<uscom:P com:pNumber="92" com:id="p-92">programmable gate array ("PGA"), <uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">a</uscom:OCRConfidenceData> field programmable gate array ("FPGA"), etc.), or any combination of hardware and software.</uscom:P><uscom:P com:pNumber="93" com:id="p-93" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0036] At 202, historical item sales data is received for all items for all stores for a particular class/category of products. For example, the class/category can be "yogurt", "coffee" or "milk." Each class has one or more subclasses, all the way down to the SKU or Universal Product Code ("UPC") level, which would be each individual item for sale, For example, for the class of yogurt, a sub-class could be each brand of yogurt, and further sub-classes could be flavor, size, type (e.g., Greek or regular), down to an SKU which would correspond to every individual different type of yogurt item sold. Each SKU or UPC would be considered a discrete data point or discrete item.</uscom:P><uscom:P com:pNumber="94" com:id="p-94" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0037] Historical sales and performance data may include, for example, data representing past sales and promotions of an item across a plurality of past retail periods. The historical performance data may be segmented into retail periods of past weeks, with each past week having numerical values assigned to it to indicate the number of items sold for that week. The historical performance data may also include numerical values representing price discounts and values of other promotion components across the retail periods, in accordance with one embodiment. The historical performance data for an item may be accessed at a central location via network communications, in accordance with one embodiment, including being accessed from each <uscom:PartName com:idrefs="PN-00044">POS terminal </uscom:PartName><uscom:PartNumber com:id="PN-00044">100</uscom:PartNumber> at each retail store and/or accessed from <uscom:PartName com:idrefs="PN-00045">database </uscom:PartName><uscom:PartNumber com:id="PN-00045">17.</uscom:PartNumber></uscom:P><uscom:P com:pNumber="95" com:id="p-95" uscom:indentationLevelNumber="L4" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="2.40">[0038] In one example embodiment shown in Figs. 3 and 4, the historical sales<uscom:BoundaryDataReference com:idref="HDR-00039"/></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00040"/>
+<?PageStart number='15'?><uscom:Heading com:id="h-37">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-38">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00041"/>
+<uscom:P com:pNumber="98" com:id="p-98">data is for a single SKU and includes 100 past weeks (i.e., <uscom:PartName com:idrefs="PN-00046">weeks </uscom:PartName><uscom:PartNumber com:id="PN-00046">1-99,</uscom:PartNumber> where week "99" is the last most recent past week of historical data, and week "100" is the first week in the future) of data for a given product<uscom:OCRConfidenceData uscom:ocrConfidenceCode="4">/</uscom:OCRConfidenceData>location (i.e., a single retail location among many retail locations for a multi-location retailer). The goal in this example embodiment is to forecast the demand for the product at the location for the <uscom:PartName com:idrefs="PN-00047">next<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData>future </uscom:PartName><uscom:PartNumber com:id="PN-00047">20</uscom:PartNumber> weeks (i.e., <uscom:PartName com:idrefs="PN-00048">weeks </uscom:PartName><uscom:PartNumber com:id="PN-00048">100-120).</uscom:PartNumber> Fig. 3 only shows <uscom:PartName com:idrefs="PN-00049">past weeks </uscom:PartName><uscom:PartNumber com:id="PN-00049">90-99</uscom:PartNumber> (at 301) (i.e., <uscom:PartName com:idrefs="PN-00050">weeks </uscom:PartName><uscom:PartNumber com:id="PN-00050">1-89</uscom:PartNumber> are not shown).</uscom:P><uscom:P com:pNumber="99" com:id="p-99" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0039] The historical sales data from 202 includes multiple features from which multiple feature sets can be formed/defined and used as input to one or more different algorithms/methods to generate multiple different models. For example, one feature set may include price, brand, and color, and a second feature set may include price, seasonality and supplier.</uscom:P><uscom:P com:pNumber="100" com:id="p-100" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0040] At 204, feature sets defined by the sales history from 202 are used as inputs to generate one or more different algorithms/methods. In the example embodiment shown in Figs. 3 and 4, three types of algorithms are used: <uscom:PartName com:idrefs="PN-00051">Linear regression (row </uscom:PartName><uscom:PartNumber com:id="PN-00051">310),</uscom:PartNumber> <uscom:PartName com:idrefs="PN-00052">SVM (row </uscom:PartName><uscom:PartNumber com:id="PN-00052">311)</uscom:PartNumber> and <uscom:PartName com:idrefs="PN-00053">ANN (row </uscom:PartName><uscom:PartNumber com:id="PN-00053">312).</uscom:PartNumber> Instead of different types of algorithms, a single type of algorithm can be used that uses different feature sets as input and thus, for the purposes of embodiments, would ultimately generate different models. For example, for an SVM, two different models can be used, with one algorithm having 10 features, and one model having 20 features. Or, for an ANN, one model may include 1 hidden layer and 10 nodes, while one model may include 2 hidden layers and 5-7 nodes. Embodiments define a feature set to describe the data points<uscom:BoundaryDataReference com:idref="HDR-00042"/></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00043"/>
+<?PageStart number='16'?><uscom:Heading com:id="h-39">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-40">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00044"/>
+<uscom:P com:pNumber="103" com:id="p-103">which could be used to train/predict the demand forecast for each model of a set of multiple machine learning models ("M"), where the set includes "<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">m</uscom:OCRConfidenceData>" models.</uscom:P><uscom:P com:pNumber="104" com:id="p-104" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0041]At 206, embodiments train each model "i" in the set of models M with the same training data set. For each model, embodiments generate a final trained model T(i). The training data set can include historical information that impacts demand, such as price data, sales data, as well as values of the selected features. For example, if the item is a t-shirt, the features and their values may be: brand: Bo<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">lo</uscom:OCRConfidenceData>, color: pink, size: medium, style: v-neck, price: $15, <uscom:PartName com:idrefs="PN-00054">sales: </uscom:PartName><uscom:PartNumber com:id="PN-00054">13</uscom:PartNumber> units.</uscom:P><uscom:P com:pNumber="105" com:id="p-105" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0042] At 208, embodiments generate the demand forecast for "n" (10 in the example of Figs. 3 and 4) weeks earlier than the supposed <uscom:PartName com:idrefs="PN-00055">forecast start date (week </uscom:PartName><uscom:PartNumber com:id="PN-00055">100</uscom:PartNumber> in the example) using the trained models from 206. To predict the forecast for <uscom:PartName com:idrefs="PN-00056">L weeks (e.g., </uscom:PartName><uscom:PartNumber com:id="PN-00056">100)</uscom:PartNumber> starting at <uscom:PartName com:idrefs="PN-00057">calendar index k (e.g., </uscom:PartName><uscom:PartNumber com:id="PN-00057">100)</uscom:PartNumber> instead of using the set of models to predict the demand time series at week (k, k+1,..,k+L-1), embodiments predict an extra n week start at calendar index k-n (e.g., 100-10=90). Therefore, the predicted forecast time series will be at (k-n, k-n-1,..,k,k+1,...,k+L-1). As shown in Fig.</uscom:P><uscom:P com:pNumber="106" com:id="p-106">3, each <uscom:PartName com:idrefs="PN-00058">trained model (i.e., linear regression (row </uscom:PartName><uscom:PartNumber com:id="PN-00058">310),</uscom:PartNumber> <uscom:PartName com:idrefs="PN-00059">SVM (row </uscom:PartName><uscom:PartNumber com:id="PN-00059">311)</uscom:PartNumber> and <uscom:PartName com:idrefs="PN-00060">ANN (row </uscom:PartName><uscom:PartNumber com:id="PN-00060">312))</uscom:PartNumber> is used to generate a demand forecast for <uscom:PartName com:idrefs="PN-00061">weeks </uscom:PartName><uscom:PartNumber com:id="PN-00061">90-99,</uscom:PartNumber> which are the n weeks for which there is historical sales data (i.e., not a future demand forecast).</uscom:P><uscom:P com:pNumber="107" com:id="p-107" uscom:indentationLevelNumber="L1">[0043] At 210, the demand forecast for future weeks (i.e., <uscom:PartName com:idrefs="PN-00062">weeks </uscom:PartName><uscom:PartNumber com:id="PN-00062">100-120)</uscom:PartNumber> are</uscom:P><uscom:P com:pNumber="108" com:id="p-108">determined using each of the trained models from 206, as shown at the columns of 301 and 302. In general, for each models in the set of models M, the trained model T(i) is applied to predict the forecast F(i) from week k-n to k+L-1 for a given product<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData>location.</uscom:P><uscom:BoundaryDataReference com:idref="HDR-00045"/>
+<uscom:BoundaryDataReference com:idref="HDR-00046"/>
+<?PageStart number='17'?><uscom:Heading com:id="h-41">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-42">PATENT</uscom:Heading><uscom:P com:pNumber="111" com:id="p-111" uscom:indentationLevelNumber="L1" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="3.47"><uscom:BoundaryDataReference com:idref="HDR-00047"/>[0044] At 212, the root-mean-square error ("RMSE") R(i) is determined for each of the forecasts F(i) for the periods from k-n to k-<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData> (i.e., the weeks prior to the forecast period), or <uscom:PartName com:idrefs="PN-00063">weeks </uscom:PartName><uscom:PartNumber com:id="PN-00063">90-99</uscom:PartNumber> in the example of Figs. 3 and 4). In one example, the RMSE is determined by starting the forecast "n" weeks earlier than the present time period (i.e., the last period for which there are sales). Therefore, for these n weeks there is both sales data and a forecast that can be generated. With sales data and the forecast, the RMSE can be calculated using known RMSE calculations. In the example of Figs. 3 and 4, the RMSE determinations for the forecast using the three trained models or methods from <uscom:PartName com:idrefs="PN-00064">week </uscom:PartName><uscom:PartNumber com:id="PN-00064">90</uscom:PartNumber> to <uscom:PartName com:idrefs="PN-00065">week </uscom:PartName><uscom:PartNumber com:id="PN-00065">99</uscom:PartNumber> are as follows:<com:Image com:id="p-00000" com:imageWrappingStyleCategory="Inline" com:orientationCategory="Portrait" com:imageContentCategory="Chemistry"><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:FileName>15799115.10-31-2017.J9FZRZU0RXEAPX4.SPEC.17.13.276.1472.1182.1826.svg</com:FileName><com:HeightMeasure com:measureUnitCode="In">1.18</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="In">3.02</com:WidthMeasure><com:Alt>Chemistry</com:Alt><com:ColourModeCategory>Black and white</com:ColourModeCategory></com:Image>[0045] At 214, a weight is determined/assigned for each method/trained model "i" based on the RMSE determined at 212 as follows: W(i)= 1/R(i).</uscom:P><uscom:P com:pNumber="112" com:id="p-112">Each weight is then normalized as follows:</uscom:P><uscom:P com:pNumber="113" com:id="p-113" uscom:indentationLevelNumber="L5"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="27">.m</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="114" com:id="p-114" uscom:indentationLevelNumber="L2">W'(i) =   <com:Image com:id="p-00001" com:imageWrappingStyleCategory="Inline" com:orientationCategory="Portrait" com:imageContentCategory="Chemistry"><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:FileName>15799115.10-31-2017.J9FZRZU0RXEAPX4.SPEC.17.21.1307.2441.1385.2487.svg</com:FileName><com:HeightMeasure com:measureUnitCode="In">0.153</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="In">0.26</com:WidthMeasure><com:Alt>Chemistry</com:Alt><com:ColourModeCategory>Black and white</com:ColourModeCategory></com:Image> W     <uscom:OCRConfidenceData uscom:ocrConfidenceCode="1">U</uscom:OCRConfidenceData>   <uscom:OCRConfidenceData uscom:ocrConfidenceCode="1">~</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="7">)</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="115" com:id="p-115" uscom:indentationLevelNumber="L5"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="288">j=1</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="116" com:id="p-116">which adds all the weights together, and normalizes the individual weights such that their sum equals to 1.0. For example, there may be two trained models with the corresponding RMSEs being 0.143 and 0.167, respectively. The weights are the<uscom:BoundaryDataReference com:idref="HDR-00048"/></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00049"/>
+<?PageStart number='18'?><uscom:Heading com:id="h-43">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-44">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00050"/>
+<uscom:P com:pNumber="119" com:id="p-119">reciprocal of the RMSE, so 7 and 6, respectively. The weights after normalizing are: <uscom:OCRConfidenceData uscom:ocrConfidenceCode="86">6/</uscom:OCRConfidenceData>(6+7) = 0.462 and 7<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData>(6+7)=0.538. In the example of Figs. 3 and 4, the determined weights are as follows:</uscom:P><uscom:P com:pNumber="120" com:id="p-120" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53"><com:Image com:id="p-00002" com:imageWrappingStyleCategory="Inline" com:orientationCategory="Portrait" com:imageContentCategory="Chemistry"><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:FileName>15799115.10-31-2017.J9FZRZU0RXEAPX4.SPEC.18.7.299.782.1276.1136.svg</com:FileName><com:HeightMeasure com:measureUnitCode="In">1.18</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="In">3.257</com:WidthMeasure><com:Alt>Chemistry</com:Alt><com:ColourModeCategory>Black and white</com:ColourModeCategory></com:Image>[0046] At 216, the final forecast is determined by combining each weighted value for each trained model of the previously determined forecasts. Embodiments combine the final forecast at week "x" as F<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">'</uscom:OCRConfidenceData>(x)=sum(w<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">'</uscom:OCRConfidenceData>(i)* f(i,x)), where x denotes the week index from k to k+L-1, and i denotes the trained model. The final demand forecast is shown in Fig. 4 at <uscom:PartName com:idrefs="PN-00066">row </uscom:PartName><uscom:PartNumber com:id="PN-00066"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8868">401.</uscom:OCRConfidenceData></uscom:PartNumber></uscom:P><uscom:P com:pNumber="121" com:id="p-121" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0047] At 218, the final demand forecast is used for manufacturing production, shipping logistics, and inventory control. The final demand forecast is sent to other specific purpose computers in one embodiment, such as an inventory control system, a manufacturing system, a shipping and logistics system, and a sales assistance system. The final demand forecast in one embodiment is in the form of individual data bits that have been translated from the demand forecast and that are stored and transmitted to other specialized computer systems, where they are stored and utilized by those systems. As a result, additional items may be manufactured, stored, shipped, etc. and items can be optimally priced.</uscom:P><uscom:P com:pNumber="122" com:id="p-122" uscom:indentationLevelNumber="L4" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="2.40">[0048]As disclosed, one goal of embodiments is to select the relevant features<uscom:BoundaryDataReference com:idref="HDR-00051"/></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00052"/>
+<?PageStart number='19'?><uscom:Heading com:id="h-45">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-46">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00053"/>
+<uscom:P com:pNumber="125" com:id="p-125">for items to ultimately maximize forecast accuracy. A good forecast generally receives no credit. Items are always available and they sell at the full price, as opposed to discounted prices. Inventory levels should not be too high, so retailers do not have money tied up in inventory. Retailers and suppliers should be able to reliably plan workforce and production capacity.</uscom:P><uscom:P com:pNumber="126" com:id="p-126" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0049] However, if the forecast is wrong (i.e., not accurate) the picture changes dramatically. The effects can have a negative impact on many business areas. For example, if the forecast is too low, fewer than needed products arrive at the retailer and they sell out. An out of stock situation impacts a retailer through lost revenue and reduced customer satisfaction. A low forecast also impacts suppliers, which have to scale down production, and review their need for the current workforce.</uscom:P><uscom:P com:pNumber="127" com:id="p-127" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0050] If the forecast is too high, there are also negative effects. The retailers will order more than they can sell. If the products are perishable, they may go bad, increasing wastage. Even if they are not perishable, the retailers may sell the extra items at discounted prices, which negatively affects revenue. The retailers may otherwise return the merchandise to the suppliers. This impacts the suppliers because they have extra products for which there is no demand. Further, the manufacturers may waste time and money producing the wrong thing, which negatively affects the supplier's revenue.</uscom:P><uscom:P com:pNumber="128" com:id="p-128" uscom:indentationLevelNumber="L1">[0051] Fig. 5 illustrates an integrated manufacturing, inventory and logistics</uscom:P><uscom:P com:pNumber="129" com:id="p-129"><uscom:PartName com:idrefs="PN-00067">system </uscom:PartName><uscom:PartNumber com:id="PN-00067">500</uscom:PartNumber> that includes demand forecasting as disclosed herein in accordance with one embodiment. As shown in Fig. 5, <uscom:PartName com:idrefs="PN-00068">system </uscom:PartName><uscom:PartNumber com:id="PN-00068">500</uscom:PartNumber> can include a product forecasting<uscom:BoundaryDataReference com:idref="HDR-00054"/></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00055"/>
+<?PageStart number='20'?><uscom:Heading com:id="h-47">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-48">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00056"/>
+<uscom:P com:pNumber="132" com:id="p-132"><uscom:PartName com:idrefs="PN-00069">system </uscom:PartName><uscom:PartNumber com:id="PN-00069">570</uscom:PartNumber> that forecasts future product demand and in some instances forecasts and/or considers future demand for hundreds of thousands of products, or in some applications tens of millions or more products at one or more <uscom:PartName com:idrefs="PN-00070">retail stores </uscom:PartName><uscom:PartNumber com:id="PN-00070">501-504.</uscom:PartNumber> Forecasting <uscom:PartName com:idrefs="PN-00071">system </uscom:PartName><uscom:PartNumber com:id="PN-00071">570</uscom:PartNumber> is in communication through a <uscom:PartName com:idrefs="PN-00072">cloud network </uscom:PartName><uscom:PartNumber com:id="PN-00072">550</uscom:PartNumber> or other type of communications network with one or <uscom:PartName com:idrefs="PN-00073">more inventory systems </uscom:PartName><uscom:PartNumber com:id="PN-00073">520</uscom:PartNumber> and one or <uscom:PartName com:idrefs="PN-00074">more manufacturing systems </uscom:PartName><uscom:PartNumber com:id="PN-00074">580.</uscom:PartNumber></uscom:P><uscom:P com:pNumber="133" com:id="p-133" uscom:indentationLevelNumber="L1">[0052] Forecasting <uscom:PartName com:idrefs="PN-00075">system </uscom:PartName><uscom:PartNumber com:id="PN-00075">570</uscom:PartNumber> generates demand forecasting by implementing</uscom:P><uscom:P com:pNumber="134" com:id="p-134">the functionality disclosed in conjunction with Fig. 2 above. <uscom:PartName com:idrefs="PN-00076">Inventory system </uscom:PartName><uscom:PartNumber com:id="PN-00076">520</uscom:PartNumber> stores inventory and provides transportation logistics to deliver items to <uscom:PartName com:idrefs="PN-00077">stores </uscom:PartName><uscom:PartNumber com:id="PN-00077">501-504</uscom:PartNumber> using <uscom:PartName com:idrefs="PN-00078">trucks </uscom:PartName><uscom:PartNumber com:id="PN-00078">510-513</uscom:PartNumber> or some other transportation mechanisms. <uscom:PartName com:idrefs="PN-00079">Inventory system </uscom:PartName><uscom:PartNumber com:id="PN-00079">520</uscom:PartNumber> in one embodiment implements an Enterprise Resource Planning ("ER<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">P"</uscom:OCRConfidenceData>) specialized computer system or a specialized inventory control system that uses input from <uscom:PartName com:idrefs="PN-00080">forecasting system </uscom:PartName><uscom:PartNumber com:id="PN-00080">510</uscom:PartNumber> to determine levels of inventories and the amount and timing of the delivery of items to <uscom:PartName com:idrefs="PN-00081">stores </uscom:PartName><uscom:PartNumber com:id="PN-00081">501-504.</uscom:PartNumber></uscom:P><uscom:P com:pNumber="135" com:id="p-135" uscom:indentationLevelNumber="L1">[0053] <uscom:PartName com:idrefs="PN-00082">Manufacturing system </uscom:PartName><uscom:PartNumber com:id="PN-00082">580</uscom:PartNumber> manufactures items to be sent to inventory</uscom:P><uscom:P com:pNumber="136" com:id="p-136"><uscom:PartName com:idrefs="PN-00083">system </uscom:PartName><uscom:PartNumber com:id="PN-00083">520</uscom:PartNumber> and provides transportation logistics to deliver the items to <uscom:PartName com:idrefs="PN-00084">inventory system </uscom:PartName><uscom:PartNumber com:id="PN-00084">520</uscom:PartNumber> using a <uscom:PartName com:idrefs="PN-00085">truck </uscom:PartName><uscom:PartNumber com:id="PN-00085">581</uscom:PartNumber> or some other transportation mechanisms. Manufacturing <uscom:PartName com:idrefs="PN-00086">system </uscom:PartName><uscom:PartNumber com:id="PN-00086">580</uscom:PartNumber> in one embodiment implements an ERP specialized computer system or a specialized manufacturing system that uses input from <uscom:PartName com:idrefs="PN-00087">forecasting system </uscom:PartName><uscom:PartNumber com:id="PN-00087">570</uscom:PartNumber> to determine an amount of items to manufacture, inventory of resources that are used for the manufacturing, and the amount and timing of the delivery of items to <uscom:PartName com:idrefs="PN-00088">inventory system </uscom:PartName><uscom:PartNumber com:id="PN-00088">520.</uscom:PartNumber></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00057"/>
+<uscom:BoundaryDataReference com:idref="HDR-00058"/>
+<?PageStart number='21'?><uscom:Heading com:id="h-49">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-50">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00059"/>
+<uscom:P com:pNumber="140" com:id="p-140" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0054] Forecasting <uscom:PartName com:idrefs="PN-00089">system </uscom:PartName><uscom:PartNumber com:id="PN-00089">570</uscom:PartNumber> can utilize information from <uscom:PartName com:idrefs="PN-00090">inventory system </uscom:PartName><uscom:PartNumber com:id="PN-00090">520,</uscom:PartNumber> a sales tracking system (not shown) and/or databases in forecasting demand for products. In forecasting <uscom:PartName com:idrefs="PN-00091">demand, forecasting system </uscom:PartName><uscom:PartNumber com:id="PN-00091">570</uscom:PartNumber> attempts to predict uncharacteristic demand of one or more products that results from events, weather, social demand, economic factors and other factors. Tens, to hundreds to thousands of different variables may be tracked that can have an effect on the demand of one or more products. Changes in these variables can result in uncharacteristic demands. For example, changes in forecasted weather can be tracked, and one or more variables associated with the forecasted weather can be used in determining whether such a change is weather may have an effect on demand, and may further forecast a change in demand.</uscom:P><uscom:P com:pNumber="141" com:id="p-141" uscom:indentationLevelNumber="L1">[0055] In general, the elements of Fig. 5 perform sales, manufacturing, or</uscom:P><uscom:P com:pNumber="142" com:id="p-142">consumption of inventory. <uscom:PartName com:idrefs="PN-00092">Retail locations/stores </uscom:PartName><uscom:PartNumber com:id="PN-00092">501-504</uscom:PartNumber> for direct consumer sales exhibit the most volatile inventory patterns, due to the random nature and external factors affecting sales. However, manufacturing facilities and sites that consume inventory (such as product integrators, <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">i</uscom:OCRConfidenceData>nternet shippers, etc. products used in the local facility) also benefit from demand forecasting as disclosed herein. As disclosed, each <uscom:PartName com:idrefs="PN-00093">retail location </uscom:PartName><uscom:PartNumber com:id="PN-00093">501-504</uscom:PartNumber> sends sales data and historic forecast data to <uscom:PartName com:idrefs="PN-00094">forecasting system </uscom:PartName><uscom:PartNumber com:id="PN-00094">570.</uscom:PartNumber> The sales data includes inventory depletion statistics for each item, or SKU/UPC for each sales period, typically days, in the previous sales cycles (i.e. weeks), typically 4-7 weeks of inventory cycles.</uscom:P><uscom:P com:pNumber="143" com:id="p-143" uscom:indentationLevelNumber="L4" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="2.40">[0056] Forecasting <uscom:PartName com:idrefs="PN-00095">system </uscom:PartName><uscom:PartNumber com:id="PN-00095">570</uscom:PartNumber> stores the sales data in a <uscom:PartName com:idrefs="PN-00096">repository </uscom:PartName><uscom:PartNumber com:id="PN-00096">572,</uscom:PartNumber> and<uscom:BoundaryDataReference com:idref="HDR-00060"/></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00061"/>
+<?PageStart number='22'?><uscom:Heading com:id="h-51">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-52">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00062"/>
+<uscom:P com:pNumber="146" com:id="p-146">employs the sales data for generating orders to replenish inventory. The orders include a set of items and a quantity for each item for maintaining the inventory level at a <uscom:PartName com:idrefs="PN-00097">store </uscom:PartName><uscom:PartNumber com:id="PN-00097">501-504.</uscom:PartNumber></uscom:P><uscom:P com:pNumber="147" com:id="p-147" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0057] Many retail ordering schemes rely on days of the week for sales periods and sales cycles. In one configuration, in an inventory management environment having inventory statistics, in which the inventory statistics are specific to each day of the <uscom:PartName com:idrefs="PN-00098">week, inventory system </uscom:PartName><uscom:PartNumber com:id="PN-00098">520</uscom:PartNumber> determines target inventory levels by gathering, for each day of the week, inventory level statistics from previous sales. Embodiments compute, based on the inventory level statistics, an inventory level for each day of the week, such that the safety stock accommodates variations in inventory between the different days of the week. Embodiments render, for each of a plurality of items, a stocking level indicative of the target inventory level including the safety stock for each day of the week. Embodiments compute an ordering quantity based on a lead time such that the ordered quantity arrives to satisfy the rendered stocking level on the determined day of the week. Identifying the actual stock levels includes identifying stock levels on the day of the week from previous weeks from the history data, thus focusing on the same day of the week over time, rather than an average of all days in the week.</uscom:P><uscom:P com:pNumber="148" com:id="p-148" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0058] In particular configurations, the disclosed embodiments may be employed in conjunction with specialized and/or particularly high volume retail sales environments. In large logistics and distribution operations, it is beneficial to load trucks as full as possible, and in the event deferral of items to a successive trip is needed, to select<uscom:BoundaryDataReference com:idref="HDR-00063"/></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00064"/>
+<?PageStart number='23'?><uscom:Heading com:id="h-53">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-54">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00065"/>
+<uscom:P com:pNumber="151" com:id="p-151">those items which will have a least likely chance of interrupting sales activity. Accordingly, embodiments are operable in conjunction with <uscom:PartName com:idrefs="PN-00099">POS system </uscom:PartName><uscom:PartNumber com:id="PN-00099">100</uscom:PartNumber> to identify high velocity or high turnover items that tend to be sold and replenished faster than other items. A UPC bar code symbol or radio-frequency identification ("RFID") on an item includes a field, designation or value, that alone or in conjunction with a database lookup, designates an item as a high velocity item appropriate for safety stock treatment as defined herein.</uscom:P><uscom:P com:pNumber="152" com:id="p-152" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0059] A high velocity item may be accommodated by identifying, for each of a plurality of items represented in an inventory database, a field for a product identifier and a field denoting a safety stock for the item, and determining, for each of the product identifiers, a product segmentation field based on product velocity indicative of increased product replenishment demands resulting from a sales volume. The disclosed embodiments determine based on the velocity field, whether to compute a safety stock, i.e. whether the overhead and burden to resupply according to the safety stock is worthwhile given the product throughput.</uscom:P><uscom:P com:pNumber="153" com:id="p-153" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0060] In other embodiments, supply logistics may invoke a delivery frequency higher than one truck a day, hence triggering a resupply window with a higher granularity. In such a case, the safety stock may be more specific than an individual day, such as a Monday AM and Monday PM, or to designate multiple delivery or time windows within a particular day of the week, such as 7:00 AM, 11:00 AM and 4:00 PM.</uscom:P><uscom:P com:pNumber="154" com:id="p-154" uscom:indentationLevelNumber="L1">[0061] Embodiments, including the generated demand forecast, may be</uscom:P><uscom:P com:pNumber="155" com:id="p-155" uscom:indentationLevelNumber="L4" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="2.93">employed in implementing supply logistics and designating deliveries (i.e., trucks) and<uscom:BoundaryDataReference com:idref="HDR-00066"/></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00067"/>
+<?PageStart number='24'?><uscom:Heading com:id="h-55">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-56">PATENT</uscom:Heading><uscom:BoundaryDataReference com:idref="HDR-00068"/>
+<uscom:P com:pNumber="158" com:id="p-158">manifest (i.e., contained items) in accordance with demand and profit margins of the transported items. High velocity items might be deemed to have priority space on a particular delivery, but could further be selected based on a profit margin or markup on the included items, and items with the greatest revenue generation potential selected for inclusion.</uscom:P><uscom:P com:pNumber="159" com:id="p-159" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0062] In such a product inventory shipping environment that uses the demand forecast disclosed herein and has a plurality of transport vehicles, each vehicle (e.g., truck) is configured for receiving a fixed payload of items for delivery to a sales location for inventory replenishment. Embodiments can provide guidance in loading a delivery vehicle, by, for each item of a plurality of items including a first item and a second item, computing a safety stock and determining, based on the computed safety stock of the first item and the second item, a quantity of each of the first item and the second item to be loaded into the delivery vehicle. Embodiments recompute a truck loading quantity based on the safety stock if insufficient space is available in the delivery vehicle for the determined quantity of the first item and the second item, meaning that certain items would need to be omitted and deferred to a successive delivery.</uscom:P><uscom:P com:pNumber="160" com:id="p-160" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">[0063]As disclosed, embodiments determine a demand forecast of one or more items for future sales periods. The demand forecast uses a plurality of weighted different trained models that have been trained and weighed based on past sales data. The generated demand forecast is then sent to other specialized systems to control manufacturing, inventory control, logistics and other functions for the forecasted items.</uscom:P><uscom:P com:pNumber="161" com:id="p-161" uscom:indentationLevelNumber="L1">[0064] Several embodiments are specifically illustrated and/or described herein.</uscom:P><uscom:BoundaryDataReference com:idref="HDR-00069"/>
+<uscom:BoundaryDataReference com:idref="HDR-00070"/>
+<?PageStart number='25'?><uscom:Heading com:id="h-57">ORACLE CONFIDENTIAL</uscom:Heading><uscom:Heading com:id="h-58">PATENT</uscom:Heading><uscom:P com:pNumber="164" com:id="p-164" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="4.00"><uscom:BoundaryDataReference com:idref="HDR-00071"/>However, it will be appreciated that modifications and variations of the disclosed embodiments are covered by the above teachings and within the purview of the appended claims without departing from the spirit and intended scope of the invention.</uscom:P><uscom:BoundaryDataReference com:idref="HDR-00072"/>
+<uscom:BoundaryDataReference com:idref="HDR-00073"/>
+<uscom:BoundaryDataBag><uscom:BoundaryData><uscom:HeaderText com:id="HDR-00001">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00002">Docket No.: T9049-22733U<uscom:OCRConfidenceData uscom:ocrConfidenceCode="558">S01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00003"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="888">-1-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00004">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00005">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00006"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="888">-2-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00007">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00008">Docket No.: T9049-22733U<uscom:OCRConfidenceData uscom:ocrConfidenceCode="558">S01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00009"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="888">-3-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00010">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00011">Docket No.: T9049-22733U<uscom:OCRConfidenceData uscom:ocrConfidenceCode="558">S01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00012"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="888">-4-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00013">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00014">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00015"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="888">-5-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00016">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00017">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00018"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="888">-6-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00019">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00020">Docket No.: T9049-22733U<uscom:OCRConfidenceData uscom:ocrConfidenceCode="558">S01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00021"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="888">-7-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00022">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00023">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00024"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="888">-8-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00025">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00026">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00027"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="888">-9-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00028">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00029">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00030"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8888">-10-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00031">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00032">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00033"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="888">-11</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00034">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00035">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00036"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">-</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="888">12-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00037">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00038">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00039"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8888">-13-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00040">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00041">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00042"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">-</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="88">14</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00043">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00044">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00045"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8888">-15-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00046">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00047">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00048"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8888">-16-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00049">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00050">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00051"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8888">-17-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00052">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00053">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00054"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8888">-18-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00055">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00056">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00057"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8888">-19-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00058">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00059">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00060"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8888">-20-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00061">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00062">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00063"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">-</uscom:OCRConfidenceData>21 -</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00064">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00065">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00066"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">-</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="88">22</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00067">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00068">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00069"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8888">-23-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00070">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00071">Docket No.: T9049-22733US<uscom:OCRConfidenceData uscom:ocrConfidenceCode="58">01</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00072"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="888">-24</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">-</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00073">ORA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">1</uscom:OCRConfidenceData>80030-US-NP</uscom:HeaderText>
+</uscom:BoundaryData></uscom:BoundaryDataBag></uspat:SpecificationDocument>

applicant/16256057.xml

@@ -0,0 +1,48 @@
+<?xml version="1.0" encoding="utf-8"?><uspat:SpecificationDocument xmlns:uscom="urn:us:gov:doc:uspto:common" xmlns:uspat="urn:us:gov:doc:uspto:patent" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:com="http://www.wipo.int/standards/XMLSchema/ST96/Common" xmlns:pat="http://www.wipo.int/standards/XMLSchema/ST96/Patent" uscom:vendorName="VASTEC" uscom:createDateTime="2019-02-12T14:17:46Z" com:st96Version="V2_1" com:ipoVersion="US_V7_1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent Patent/V7_1/Schema/USPatent/Document/SpecificationDocument_V7_1.xsd" com:documentFileName="16256057.01-24-2019.JRKYY66FRXEAPX5.SPEC.XML" com:id="JRKYY66FRXEAPX5">
+<uspat:DocumentMetadata com:id="ID0000001"><uscom:DocumentCode>SPEC</uscom:DocumentCode><uscom:ApplicationNumberText uscom:electronicText="16256057">16256057</uscom:ApplicationNumberText><com:PageTotalQuantity>14</com:PageTotalQuantity><uscom:ParagraphTotalQuantity>123</uscom:ParagraphTotalQuantity><uscom:OfficialDate>2019-01-24</uscom:OfficialDate></uspat:DocumentMetadata><?PageStart number='1'?><uscom:BoundaryDataReference com:idref="HDR-00001"/>
+<uscom:Heading com:id="h-1">METHODS AND SYSTEMS FOR MONITORING A BED VIEW FOR A</uscom:Heading><uscom:P com:pNumber="2" com:id="p-2" uscom:indentationLevelNumber="L1">VEHICLE</uscom:P><uscom:Heading com:id="h-2">TECHNICAL FIELD</uscom:Heading><uscom:P com:pNumber="3" com:id="p-3">[0001]       The present specification generally relates to vehicle systems for monitoring a bed</uscom:P><uscom:P com:pNumber="4" com:id="p-4">of a vehicle (e.g., a pickup truck) and, more specifically, to vehicle systems that capture images of the bed of the vehicle and display the captured images for a limited period of time.</uscom:P><uscom:Heading com:id="h-3">BACKGROUND</uscom:Heading><uscom:P com:pNumber="5" com:id="p-5">[0002]       A driver of a vehicle, such as a pickup truck, may wish to view the status of the</uscom:P><uscom:P com:pNumber="6" com:id="p-6">bed of the vehicle while driving. For example, the driver may want to check if objects loaded in a truck bed are tightly fastened. Thus, systems for effectively providing information about the status of the bed of a vehicle may be needed.</uscom:P><uscom:Heading com:id="h-4">SUMMARY</uscom:Heading><uscom:P com:pNumber="7" com:id="p-7">[0003]      In one embodiment, a vehicle includes a display, an input device, a first imaging</uscom:P><uscom:P com:pNumber="8" com:id="p-8">device configured to capture one or more images of a bed of the vehicle, and a controller. The controller receives a first signal indicating a first activation of the input device, determines whether a speed of the vehicle is greater than a threshold in response to a receipt of the first signal, and instructs the display to display an image of the bed captured by the first imaging device for a first predetermined time in response to determining that the vehicle speed is greater than the threshold and in response to the receipt of the first signal.</uscom:P><uscom:P com:pNumber="9" com:id="p-9">[0004]      In another embodiment, a system for monitoring a bed view of a vehicle is</uscom:P><uscom:P com:pNumber="10" com:id="p-10">provided. The system includes one or more processors, one or more memory modules, and machine readable instructions stored in the one or more memory modules that, when executed by the one or more processors, cause the system to: receive a first signal indicating a first activation of an input device of the vehicle; determine whether a speed of the vehicle is greater than a threshold in response to receipt of the first signal; and instruct a display of the vehicle to display a bed view of the vehicle for a first predetermined time in response to determining that the<uscom:BoundaryDataReference com:idref="HDR-00002"/></uscom:P><?PageStart number='2'?><uscom:BoundaryDataReference com:idref="HDR-00003"/>
+<uscom:P com:pNumber="12" com:id="p-12">vehicle speed is greater than the threshold and in response to receipt of the first signal.</uscom:P><uscom:P com:pNumber="13" com:id="p-13">[0005]      In another embodiment, a method for monitoring a bed view of a vehicle is</uscom:P><uscom:P com:pNumber="14" com:id="p-14">provided. The method includes receiving a first signal indicating a first activation of an input device of the vehicle; determining whether a speed of the vehicle is greater than a threshold in response to receipt of the first signal; and displaying, on a display of the vehicle, a bed view of the vehicle for a first predetermined time in response to determining that the vehicle speed is greater than the threshold and in response to receipt of the first signal.</uscom:P><uscom:P com:pNumber="15" com:id="p-15">[0006]       These and additional features provided by the embodiments of the present</uscom:P><uscom:P com:pNumber="16" com:id="p-16">disclosure will be more fully understood in view of the following detailed description, in conjunction with the drawings.</uscom:P><uscom:Heading com:id="h-5">BRIEF DESCRIPTION OF THE DRAWINGS</uscom:Heading><uscom:P com:pNumber="17" com:id="p-17">[0007]       The embodiments set forth in the drawings are illustrative and exemplary in</uscom:P><uscom:P com:pNumber="18" com:id="p-18">nature and not intended to limit the disclosure. The following detailed description of the illustrative embodiments can be understood when read in conjunction with the following drawings, where like structure is indicated with like reference numerals and in which:</uscom:P><uscom:P com:pNumber="19" com:id="p-19">[0008]       FIG. 1 depicts a vehicle having imaging devices for monitoring a bed of the</uscom:P><uscom:P com:pNumber="20" com:id="p-20">vehicle, according to one or more embodiments shown and described herein;</uscom:P><uscom:P com:pNumber="21" com:id="p-21">[0009]       FIG. 2 depicts an internal view of the vehicle, according to one or more</uscom:P><uscom:P com:pNumber="22" com:id="p-22">embodiments shown and described herein;</uscom:P><uscom:P com:pNumber="23" com:id="p-23">[0010]       FIG. 3 depicts a schematic illustration of various components of a system for</uscom:P><uscom:P com:pNumber="24" com:id="p-24">monitoring a bed view of a vehicle, according to one or more embodiments shown and described herein;</uscom:P><uscom:P com:pNumber="25" com:id="p-25">[0011]       FIG. 4 depicts a flowchart for displaying a zoomed bed view of a vehicle in</uscom:P><uscom:P com:pNumber="26" com:id="p-26">response to an actuation of a switch, according to one or more embodiments shown and described herein;</uscom:P><uscom:BoundaryDataReference com:idref="HDR-00004"/>
+<?PageStart number='3'?><uscom:BoundaryDataReference com:idref="HDR-00005"/>
+<uscom:P com:pNumber="29" com:id="p-29">[0012]       FIG. 5 depicts a flowchart for displaying a zoomed bed view of a vehicle in</uscom:P><uscom:P com:pNumber="30" com:id="p-30">response to an actuation of a switch, according to one or more embodiments shown and described herein; and</uscom:P><uscom:P com:pNumber="31" com:id="p-31">[0013]       FIG. 6 depicts operations of a display and a switch versus time, according to one</uscom:P><uscom:P com:pNumber="32" com:id="p-32">or more embodiments shown and described herein.</uscom:P><uscom:Heading com:id="h-6">DETAILED DESCRIPTION</uscom:Heading><uscom:P com:pNumber="33" com:id="p-33">[0014]       The embodiments disclosed herein include vehicle systems for monitoring a bed</uscom:P><uscom:P com:pNumber="34" com:id="p-34">of a vehicle. Referring generally to FIGS. 1 and 3, a vehicle includes a display, an input device, a first imaging device configured to capture one or more images of a bed of the vehicle, and a controller. The controller receives a first signal indicating a first activation of the input device, determines whether a speed of the vehicle is greater than a threshold in response to a receipt of the first signal, and instructs the display to display an image of the bed captured by the first imaging device for a first predetermined time in response to determining that the vehicle speed is greater than the threshold and in response to the receipt of the first signal. According to the present disclosure, when the input device is activated, the display shows the bed view of the vehicle for a limited time such that a driver or passenger of the vehicle can quickly check the status of the bed and keep driving. The display goes back to a default screen (e.g., a navigational map, a radio screen, a navigation screen, etc.) after the predetermined time has passed, so that a duration of potential distraction due to the bed view is limited. Additionally, the image of the bed view may be restricted to the top of the tailgate of the vehicle so that the driver of the vehicle is not able to use the bed view image as a rear view monitor. In this regard, the system of the present disclosure further reduces distracting the driver and allows the driver to only check the bed. Various embodiments of the systems and methods for monitoring a bed view of a vehicle are described in greater detail herein.</uscom:P><uscom:P com:pNumber="35" com:id="p-35">[0015]       FIG. 1 depicts a <uscom:PartName com:idrefs="PN-00001">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00001">10</uscom:PartNumber> having imaging devices for monitoring a bed of the</uscom:P><uscom:P com:pNumber="36" com:id="p-36"><uscom:PartName com:idrefs="PN-00002">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00002">10,</uscom:PartNumber> according to one or more embodiments shown and described herein.      In</uscom:P><uscom:P com:pNumber="37" com:id="p-37">embodiments, the <uscom:PartName com:idrefs="PN-00003">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00003">10</uscom:PartNumber> includes a <uscom:PartName com:idrefs="PN-00004">cargo </uscom:PartName><uscom:PartNumber com:id="PN-00004">110</uscom:PartNumber> for storing items. The <uscom:PartName com:idrefs="PN-00005">cargo </uscom:PartName><uscom:PartNumber com:id="PN-00005">110</uscom:PartNumber> includes a <uscom:PartName com:idrefs="PN-00006">bed </uscom:PartName><uscom:PartNumber com:id="PN-00006">132</uscom:PartNumber> on which cargo may be placed and a <uscom:PartName com:idrefs="PN-00007">tailgate </uscom:PartName><uscom:PartNumber com:id="PN-00007">134.</uscom:PartNumber> The <uscom:PartName com:idrefs="PN-00008">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00008">10</uscom:PartNumber> includes a <uscom:PartName com:idrefs="PN-00009">first imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00009">118</uscom:PartNumber> for monitoring the <uscom:PartName com:idrefs="PN-00010">bed </uscom:PartName><uscom:PartNumber com:id="PN-00010">132</uscom:PartNumber> of the <uscom:PartName com:idrefs="PN-00011">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00011">10.</uscom:PartNumber> The <uscom:PartName com:idrefs="PN-00012">first imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00012">118</uscom:PartNumber><uscom:BoundaryDataReference com:idref="HDR-00006"/></uscom:P><?PageStart number='4'?><uscom:BoundaryDataReference com:idref="HDR-00007"/>
+<uscom:P com:pNumber="39" com:id="p-39">may capture the images of the <uscom:PartName com:idrefs="PN-00013">bed </uscom:PartName><uscom:PartNumber com:id="PN-00013">132.</uscom:PartNumber> In some embodiments, the <uscom:PartName com:idrefs="PN-00014">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00014">10</uscom:PartNumber> may include a <uscom:PartName com:idrefs="PN-00015">second imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00015">120</uscom:PartNumber> that monitors a rear view of the <uscom:PartName com:idrefs="PN-00016">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00016">10</uscom:PartNumber> and captures images of the rear view. While FIG. 1 depicts two <uscom:PartName com:idrefs="PN-00017">imaging devices </uscom:PartName><uscom:PartNumber com:id="PN-00017">118 and 120,</uscom:PartNumber> the <uscom:PartName com:idrefs="PN-00018">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00018">10</uscom:PartNumber> may include additional imaging devices. For example, additional imaging devices may be placed on the side of the vehicle, at the front of the vehicle, or the top of the vehicle. The details of the first and <uscom:PartName com:idrefs="PN-00019">second imaging devices </uscom:PartName><uscom:PartNumber com:id="PN-00019">118 and 120</uscom:PartNumber> will be described in detail below with reference to FIG. 3. The first and <uscom:PartName com:idrefs="PN-00020">second imaging devices </uscom:PartName><uscom:PartNumber com:id="PN-00020">118 and 120</uscom:PartNumber> may transmit captured images to one or <uscom:PartName com:idrefs="PN-00021">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00021">102</uscom:PartNumber> (FIG. 3) of the <uscom:PartName com:idrefs="PN-00022">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00022">10.</uscom:PartNumber></uscom:P><uscom:P com:pNumber="40" com:id="p-40">[0016]      Referring now to FIG. 2, the one or <uscom:PartName com:idrefs="PN-00023">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00023">102</uscom:PartNumber> (FIG. 3) may display the</uscom:P><uscom:P com:pNumber="41" com:id="p-41">captured images on the <uscom:PartName com:idrefs="PN-00024">display </uscom:PartName><uscom:PartNumber com:id="PN-00024">124</uscom:PartNumber> in response to an activation of a <uscom:PartName com:idrefs="PN-00025">switch </uscom:PartName><uscom:PartNumber com:id="PN-00025">126</uscom:PartNumber> such that the driver or passenger of the vehicle may see the bed view or the rear view of the vehicle. For example, the <uscom:PartName com:idrefs="PN-00026">display </uscom:PartName><uscom:PartNumber com:id="PN-00026">124</uscom:PartNumber> of the <uscom:PartName com:idrefs="PN-00027">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00027">10</uscom:PartNumber> may display an image of the <uscom:PartName com:idrefs="PN-00028">bed </uscom:PartName><uscom:PartNumber com:id="PN-00028">132</uscom:PartNumber> captured by the <uscom:PartName com:idrefs="PN-00029">first imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00029">118</uscom:PartNumber> in response to an activation of the <uscom:PartName com:idrefs="PN-00030">switch </uscom:PartName><uscom:PartNumber com:id="PN-00030">126,</uscom:PartNumber> as shown in FIG. 2. The details of the <uscom:PartName com:idrefs="PN-00031">switch </uscom:PartName><uscom:PartNumber com:id="PN-00031">126</uscom:PartNumber> are described below with reference to FIG. 3. In some embodiments, the <uscom:PartName com:idrefs="PN-00032">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00032">10</uscom:PartNumber> may include a <uscom:PartName com:idrefs="PN-00033">second switch </uscom:PartName><uscom:PartNumber com:id="PN-00033">128.</uscom:PartNumber> The <uscom:PartName com:idrefs="PN-00034">display </uscom:PartName><uscom:PartNumber com:id="PN-00034">124</uscom:PartNumber> of the <uscom:PartName com:idrefs="PN-00035">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00035">10</uscom:PartNumber> may display an image of a rear view of the <uscom:PartName com:idrefs="PN-00036">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00036">10</uscom:PartNumber> captured by the <uscom:PartName com:idrefs="PN-00037">second imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00037">120</uscom:PartNumber> in response to an activation of the <uscom:PartName com:idrefs="PN-00038">second switch </uscom:PartName><uscom:PartNumber com:id="PN-00038">128.</uscom:PartNumber> In some embodiments, the <uscom:PartName com:idrefs="PN-00039">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00039">10</uscom:PartNumber> may not include the <uscom:PartName com:idrefs="PN-00040">second switch </uscom:PartName><uscom:PartNumber com:id="PN-00040">128.</uscom:PartNumber></uscom:P><uscom:P com:pNumber="42" com:id="p-42">[0017]      Referring now to FIG. 3, an embodiment of a <uscom:PartName com:idrefs="PN-00041">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00041">100</uscom:PartNumber> is</uscom:P><uscom:P com:pNumber="43" com:id="p-43">schematically depicted. It is noted that, while the <uscom:PartName com:idrefs="PN-00042">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00042">100</uscom:PartNumber> is depicted in isolation, the <uscom:PartName com:idrefs="PN-00043">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00043">100</uscom:PartNumber> may be included within a vehicle in some embodiments. In embodiments in which the <uscom:PartName com:idrefs="PN-00044">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00044">100</uscom:PartNumber> is included within a vehicle, the vehicle may be an automobile or any other passenger or non-passenger vehicle such as, for example, a terrestrial, aquatic, and/or airborne vehicle. In some embodiments, the vehicle is an autonomous vehicle that navigates its environment with limited human input or without human input. In some embodiments, the system may be embedded within a mobile device (e.g., smartphone, laptop computer, etc.) carried by a driver of the vehicle.</uscom:P><uscom:P com:pNumber="44" com:id="p-44">[0018]      The <uscom:PartName com:idrefs="PN-00045">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00045">100</uscom:PartNumber> includes one or <uscom:PartName com:idrefs="PN-00046">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00046">102.</uscom:PartNumber> Each of the</uscom:P><uscom:P com:pNumber="45" com:id="p-45" uscom:indentationLevelNumber="L2" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="3.20">one or <uscom:PartName com:idrefs="PN-00047">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00047">102</uscom:PartNumber> may be any device capable of executing machine readable and<uscom:BoundaryDataReference com:idref="HDR-00008"/></uscom:P><?PageStart number='5'?><uscom:BoundaryDataReference com:idref="HDR-00009"/>
+<uscom:P com:pNumber="47" com:id="p-47">executable instructions. Accordingly, each of the one or <uscom:PartName com:idrefs="PN-00048">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00048">102</uscom:PartNumber> may be a controller, an integrated circuit, a microchip, a computer, or any other computing device. The one or <uscom:PartName com:idrefs="PN-00049">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00049">102</uscom:PartNumber> are coupled to a <uscom:PartName com:idrefs="PN-00050">communication path </uscom:PartName><uscom:PartNumber com:id="PN-00050">104</uscom:PartNumber> that provides signal interconnectivity between various modules of the system. Accordingly, the <uscom:PartName com:idrefs="PN-00051">communication path </uscom:PartName><uscom:PartNumber com:id="PN-00051">104</uscom:PartNumber> may communicatively couple any number of <uscom:PartName com:idrefs="PN-00052">processors </uscom:PartName><uscom:PartNumber com:id="PN-00052">102</uscom:PartNumber> with one another, and allow the modules coupled to the <uscom:PartName com:idrefs="PN-00053">communication path </uscom:PartName><uscom:PartNumber com:id="PN-00053">104</uscom:PartNumber> to operate in a distributed computing environment. Specifically, each of the modules may operate as a node that may send and/or receive data. As used herein, the term "communicatively coupled" means that coupled components are capable of exchanging data signals with one another such as, for example, electrical signals via conductive medium, electromagnetic signals via air, optical signals via optical waveguides, and the like.</uscom:P><uscom:P com:pNumber="48" com:id="p-48">[0019]       Accordingly, the <uscom:PartName com:idrefs="PN-00054">communication path </uscom:PartName><uscom:PartNumber com:id="PN-00054">104</uscom:PartNumber> may be formed from any medium that</uscom:P><uscom:P com:pNumber="49" com:id="p-49">is capable of transmitting a signal such as, for example, conductive wires, conductive traces, optical waveguides, or the like. In some embodiments, the <uscom:PartName com:idrefs="PN-00055">communication path </uscom:PartName><uscom:PartNumber com:id="PN-00055">104</uscom:PartNumber> may facilitate the transmission of wireless signals, such as WiFi, Bluetooth<uscom:OCRConfidenceData uscom:ocrConfidenceCode="4">®</uscom:OCRConfidenceData>, Near Field Communication (NFC) and the like. Moreover, the <uscom:PartName com:idrefs="PN-00056">communication path </uscom:PartName><uscom:PartNumber com:id="PN-00056">104</uscom:PartNumber> may be formed from a combination of mediums capable of transmitting signals. In one embodiment, the <uscom:PartName com:idrefs="PN-00057">communication path </uscom:PartName><uscom:PartNumber com:id="PN-00057">104</uscom:PartNumber> comprises a combination of conductive traces, conductive wires, connectors, and buses that cooperate to permit the transmission of electrical data signals to components such as processors, memories, sensors, input devices, output devices, and communication devices. Accordingly, the <uscom:PartName com:idrefs="PN-00058">communication path </uscom:PartName><uscom:PartNumber com:id="PN-00058">104</uscom:PartNumber> may comprise a vehicle bus, such as for example a <uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">LI</uscom:OCRConfidenceData>N bus, a CAN bus, a VAN bus, and the like. Additionally, it is noted that the term <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">"</uscom:OCRConfidenceData>signal<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">"</uscom:OCRConfidenceData> means a waveform (e.g., electrical, optical, magnetic, mechanical or electromagnetic), such as DC, AC, sinusoidal-wave, triangular-wave, square-wave, vibration, and the like, capable of traveling through a medium.</uscom:P><uscom:P com:pNumber="50" com:id="p-50">[0020]       The <uscom:PartName com:idrefs="PN-00059">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00059">100</uscom:PartNumber> includes one or <uscom:PartName com:idrefs="PN-00060">more memory modules </uscom:PartName><uscom:PartNumber com:id="PN-00060">106</uscom:PartNumber></uscom:P><uscom:P com:pNumber="51" com:id="p-51">coupled to the <uscom:PartName com:idrefs="PN-00061">communication path </uscom:PartName><uscom:PartNumber com:id="PN-00061">104.</uscom:PartNumber> The one or <uscom:PartName com:idrefs="PN-00062">more memory modules </uscom:PartName><uscom:PartNumber com:id="PN-00062">106</uscom:PartNumber> may comprise RAM, ROM, flash memories, hard drives, or any device capable of storing machine readable and executable instructions such that the machine readable and executable instructions can be accessed by the one or <uscom:PartName com:idrefs="PN-00063">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00063">102.</uscom:PartNumber> The machine readable and executable instructions<uscom:BoundaryDataReference com:idref="HDR-00010"/></uscom:P><?PageStart number='6'?><uscom:BoundaryDataReference com:idref="HDR-00011"/>
+<uscom:P com:pNumber="53" com:id="p-53">may comprise logic or algorithm(s) written in any programming language of any generation (e.g., 1GL, 2GL, 3GL, 4GL, or 5GL) such as, for example, machine language that may be directly executed by the processor, or assembly language, object-oriented programming (<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">O</uscom:OCRConfidenceData>OP), scripting languages, microcode, etc., that may be compiled or assembled into machine readable and executable instructions and stored on the one or <uscom:PartName com:idrefs="PN-00064">more memory modules </uscom:PartName><uscom:PartNumber com:id="PN-00064">106.</uscom:PartNumber> Alternatively, the machine readable and executable instructions may be written in a hardware description language (HDL), such as logic implemented via either a field-programmable gate array (FPGA) configuration or an application-specific integrated circuit (ASIC), or their equivalents. Accordingly, the methods described herein may be implemented in any conventional computer programming language, as pre-programmed hardware elements, or as a combination of hardware and software components.</uscom:P><uscom:P com:pNumber="54" com:id="p-54">[0021]      Referring still to FIG. 3, the <uscom:PartName com:idrefs="PN-00065">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00065">100</uscom:PartNumber> comprises the display</uscom:P><uscom:P com:pNumber="55" com:id="p-55">124 for providing visual output such as, for example, maps, navigation, entertainment, images, data received from an external device, or a combination thereof. The <uscom:PartName com:idrefs="PN-00066">display </uscom:PartName><uscom:PartNumber com:id="PN-00066">124</uscom:PartNumber> may output one of an external view including a bed view and a rear view of the vehicle, a navigational map, entertainment, and data received from an external device in response to a selection of the corresponding function. The <uscom:PartName com:idrefs="PN-00067">display </uscom:PartName><uscom:PartNumber com:id="PN-00067">124</uscom:PartNumber> may be coupled to the <uscom:PartName com:idrefs="PN-00068">communication path </uscom:PartName><uscom:PartNumber com:id="PN-00068">104.</uscom:PartNumber> Accordingly, the <uscom:PartName com:idrefs="PN-00069">communication path </uscom:PartName><uscom:PartNumber com:id="PN-00069">104</uscom:PartNumber> communicatively couples the <uscom:PartName com:idrefs="PN-00070">display </uscom:PartName><uscom:PartNumber com:id="PN-00070">124</uscom:PartNumber> to other modules of the <uscom:PartName com:idrefs="PN-00071">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00071">100.</uscom:PartNumber> The <uscom:PartName com:idrefs="PN-00072">display </uscom:PartName><uscom:PartNumber com:id="PN-00072">124</uscom:PartNumber> may include any medium capable of transmitting an optical output such as, for example, a cathode ray tube, light emitting diodes, a liquid crystal display, a plasma display, or the like. Moreover, the <uscom:PartName com:idrefs="PN-00073">display </uscom:PartName><uscom:PartNumber com:id="PN-00073">124</uscom:PartNumber> may be a touchscreen that, in addition to providing optical information, detects the presence and location of a tactile input upon a surface of or adjacent to the display. Accordingly, the display may receive mechanical input directly upon the optical output provided by the display.</uscom:P><uscom:P com:pNumber="56" com:id="p-56">[0022]      The <uscom:PartName com:idrefs="PN-00074">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00074">100</uscom:PartNumber> comprises a <uscom:PartName com:idrefs="PN-00075">switch </uscom:PartName><uscom:PartNumber com:id="PN-00075">126.</uscom:PartNumber> The <uscom:PartName com:idrefs="PN-00076">switch </uscom:PartName><uscom:PartNumber com:id="PN-00076">126</uscom:PartNumber> may be</uscom:P><uscom:P com:pNumber="57" com:id="p-57">a physical knob or button that is manually actuated (e.g., by turning the knob or pressing the button) or an animated knob displayed on the <uscom:PartName com:idrefs="PN-00077">display </uscom:PartName><uscom:PartNumber com:id="PN-00077">124</uscom:PartNumber> that can be touched in order to be activated. In addition, the <uscom:PartName com:idrefs="PN-00078">switch </uscom:PartName><uscom:PartNumber com:id="PN-00078">126</uscom:PartNumber> may be configured to rotate around a center of the <uscom:PartName com:idrefs="PN-00079">switch </uscom:PartName><uscom:PartNumber com:id="PN-00079">126</uscom:PartNumber> to send an analog or digital scale input. In embodiments, in response to the activation of the <uscom:PartName com:idrefs="PN-00080">switch </uscom:PartName><uscom:PartNumber com:id="PN-00080">126,</uscom:PartNumber> the <uscom:PartName com:idrefs="PN-00081">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00081">100</uscom:PartNumber> displays an image of the <uscom:PartName com:idrefs="PN-00082">bed </uscom:PartName><uscom:PartNumber com:id="PN-00082">132</uscom:PartNumber> captured by the first<uscom:BoundaryDataReference com:idref="HDR-00012"/></uscom:P><?PageStart number='7'?><uscom:BoundaryDataReference com:idref="HDR-00013"/>
+<uscom:P com:pNumber="59" com:id="p-59">imaging <uscom:PartName com:idrefs="PN-00083">device </uscom:PartName><uscom:PartNumber com:id="PN-00083">118.</uscom:PartNumber> The image of the <uscom:PartName com:idrefs="PN-00084">bed </uscom:PartName><uscom:PartNumber com:id="PN-00084">132</uscom:PartNumber> may be zoomed in or zoomed out based on the rotation of the <uscom:PartName com:idrefs="PN-00085">switch </uscom:PartName><uscom:PartNumber com:id="PN-00085">126.</uscom:PartNumber> For example, if the <uscom:PartName com:idrefs="PN-00086">switch </uscom:PartName><uscom:PartNumber com:id="PN-00086">126</uscom:PartNumber> is rotated clockwise, the image of the <uscom:PartName com:idrefs="PN-00087">bed </uscom:PartName><uscom:PartNumber com:id="PN-00087">132</uscom:PartNumber> may be zoomed in. If the <uscom:PartName com:idrefs="PN-00088">switch </uscom:PartName><uscom:PartNumber com:id="PN-00088">126</uscom:PartNumber> is rotated counterclockwise, the image of the <uscom:PartName com:idrefs="PN-00089">bed </uscom:PartName><uscom:PartNumber com:id="PN-00089">132</uscom:PartNumber> may be zoomed out. Although the <uscom:PartName com:idrefs="PN-00090">switch </uscom:PartName><uscom:PartNumber com:id="PN-00090">126</uscom:PartNumber> is positioned on the left side of the <uscom:PartName com:idrefs="PN-00091">display </uscom:PartName><uscom:PartNumber com:id="PN-00091">124</uscom:PartNumber> as shown in FIG. 2, the <uscom:PartName com:idrefs="PN-00092">switch </uscom:PartName><uscom:PartNumber com:id="PN-00092">126</uscom:PartNumber> may be positioned at any other suitable locations such as on the right side of the <uscom:PartName com:idrefs="PN-00093">display </uscom:PartName><uscom:PartNumber com:id="PN-00093">124</uscom:PartNumber> when a driver's seat is located on the right side of the <uscom:PartName com:idrefs="PN-00094">display </uscom:PartName><uscom:PartNumber com:id="PN-00094">124</uscom:PartNumber> and/or in the center (e.g., at the top or bottom of the <uscom:PartName com:idrefs="PN-00095">display </uscom:PartName><uscom:PartNumber com:id="PN-00095">124).</uscom:PartNumber></uscom:P><uscom:P com:pNumber="60" com:id="p-60">[0023]      The <uscom:PartName com:idrefs="PN-00096">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00096">100</uscom:PartNumber> comprises a <uscom:PartName com:idrefs="PN-00097">second switch </uscom:PartName><uscom:PartNumber com:id="PN-00097">128.</uscom:PartNumber> The second</uscom:P><uscom:P com:pNumber="61" com:id="p-61"><uscom:PartName com:idrefs="PN-00098">switch </uscom:PartName><uscom:PartNumber com:id="PN-00098">128</uscom:PartNumber> may be similar to the <uscom:PartName com:idrefs="PN-00099">switch </uscom:PartName><uscom:PartNumber com:id="PN-00099">126.</uscom:PartNumber> In embodiments, in response to the activation of the <uscom:PartName com:idrefs="PN-00100">second switch </uscom:PartName><uscom:PartNumber com:id="PN-00100">128,</uscom:PartNumber> the <uscom:PartName com:idrefs="PN-00101">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00101">100</uscom:PartNumber> may display a rear view image of the <uscom:PartName com:idrefs="PN-00102">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00102">10</uscom:PartNumber> captured by the <uscom:PartName com:idrefs="PN-00103">second imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00103">120.</uscom:PartNumber> The <uscom:PartName com:idrefs="PN-00104">second switch </uscom:PartName><uscom:PartNumber com:id="PN-00104">128</uscom:PartNumber> may be configured to rotate around a center of the <uscom:PartName com:idrefs="PN-00105">second switch </uscom:PartName><uscom:PartNumber com:id="PN-00105">128</uscom:PartNumber> to send an analog or digital scale input. The image of the rear view may be zoomed in or zoomed out based on the rotation of the <uscom:PartName com:idrefs="PN-00106">second switch </uscom:PartName><uscom:PartNumber com:id="PN-00106">128.</uscom:PartNumber> For example, if the <uscom:PartName com:idrefs="PN-00107">second switch </uscom:PartName><uscom:PartNumber com:id="PN-00107">128</uscom:PartNumber> is rotated clockwise, the image of the rear view may be zoomed in. If the <uscom:PartName com:idrefs="PN-00108">second switch </uscom:PartName><uscom:PartNumber com:id="PN-00108">128</uscom:PartNumber> is rotated counterclockwise, the image of the rear view may be zoomed out.</uscom:P><uscom:P com:pNumber="62" com:id="p-62">[0024]      The <uscom:PartName com:idrefs="PN-00109">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00109">100</uscom:PartNumber> comprises a satellite antenna 114 coupled to the</uscom:P><uscom:P com:pNumber="63" com:id="p-63"><uscom:PartName com:idrefs="PN-00110">communication path </uscom:PartName><uscom:PartNumber com:id="PN-00110">104</uscom:PartNumber> such that the <uscom:PartName com:idrefs="PN-00111">communication path </uscom:PartName><uscom:PartNumber com:id="PN-00111">104</uscom:PartNumber> communicatively couples the <uscom:PartName com:idrefs="PN-00112">satellite antenna </uscom:PartName><uscom:PartNumber com:id="PN-00112">114</uscom:PartNumber> to other modules of the <uscom:PartName com:idrefs="PN-00113">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00113">100.</uscom:PartNumber> The <uscom:PartName com:idrefs="PN-00114">satellite antenna </uscom:PartName><uscom:PartNumber com:id="PN-00114">114</uscom:PartNumber> is configured to receive signals from global positioning system satellites. Specifically, in one embodiment, the <uscom:PartName com:idrefs="PN-00115">satellite antenna </uscom:PartName><uscom:PartNumber com:id="PN-00115">114</uscom:PartNumber> includes one or more conductive elements that interact with electromagnetic signals transmitted by global positioning system satellites. The received signal is transformed into a data signal indicative of the location (e.g., latitude and longitude) of the <uscom:PartName com:idrefs="PN-00116">satellite antenna </uscom:PartName><uscom:PartNumber com:id="PN-00116">114</uscom:PartNumber> or an object positioned near the <uscom:PartName com:idrefs="PN-00117">satellite antenna </uscom:PartName><uscom:PartNumber com:id="PN-00117">114,</uscom:PartNumber> by the one or <uscom:PartName com:idrefs="PN-00118">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00118">102.</uscom:PartNumber> Additionally, it is noted that the <uscom:PartName com:idrefs="PN-00119">satellite antenna </uscom:PartName><uscom:PartNumber com:id="PN-00119">114</uscom:PartNumber> may include at least one of the one or <uscom:PartName com:idrefs="PN-00120">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00120">102</uscom:PartNumber> and the one or <uscom:PartName com:idrefs="PN-00121">memory modules </uscom:PartName><uscom:PartNumber com:id="PN-00121">106.</uscom:PartNumber> In some embodiments, the <uscom:PartName com:idrefs="PN-00122">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00122">100</uscom:PartNumber> does not include the <uscom:PartName com:idrefs="PN-00123">satellite antenna </uscom:PartName><uscom:PartNumber com:id="PN-00123">114.</uscom:PartNumber></uscom:P><uscom:P com:pNumber="64" com:id="p-64">[0025]      Still referring to FIG. 3, the bed monitoring system may include one or more</uscom:P><uscom:P com:pNumber="65" com:id="p-65"><uscom:PartName com:idrefs="PN-00124">motion sensors </uscom:PartName><uscom:PartNumber com:id="PN-00124">116</uscom:PartNumber> for detecting and measuring motion and changes in motion of the <uscom:PartName com:idrefs="PN-00125">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00125">10.</uscom:PartNumber></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00014"/>
+<?PageStart number='8'?><uscom:BoundaryDataReference com:idref="HDR-00015"/>
+<uscom:P com:pNumber="68" com:id="p-68">Each of the one or <uscom:PartName com:idrefs="PN-00126">more motion sensors </uscom:PartName><uscom:PartNumber com:id="PN-00126">116</uscom:PartNumber> is coupled to the <uscom:PartName com:idrefs="PN-00127">communication path </uscom:PartName><uscom:PartNumber com:id="PN-00127">104</uscom:PartNumber> and communicatively coupled to the one or <uscom:PartName com:idrefs="PN-00128">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00128">102.</uscom:PartNumber> In some embodiments, the <uscom:PartName com:idrefs="PN-00129">motion sensors </uscom:PartName><uscom:PartNumber com:id="PN-00129">116</uscom:PartNumber> include inertial measurement units. In some embodiments, the one or <uscom:PartName com:idrefs="PN-00130">more motion sensors </uscom:PartName><uscom:PartNumber com:id="PN-00130">116</uscom:PartNumber> include one or more accelerometers and one or more gyroscopes. Each of the one or <uscom:PartName com:idrefs="PN-00131">more motion sensors </uscom:PartName><uscom:PartNumber com:id="PN-00131">116</uscom:PartNumber> transforms sensed physical movement of the <uscom:PartName com:idrefs="PN-00132">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00132">10</uscom:PartNumber> into a signal indicative of an orientation, a rotation, a velocity, or an acceleration of the <uscom:PartName com:idrefs="PN-00133">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00133">10.</uscom:PartNumber> Based on the signals from the one or <uscom:PartName com:idrefs="PN-00134">more motion sensors </uscom:PartName><uscom:PartNumber com:id="PN-00134">116,</uscom:PartNumber> the one or <uscom:PartName com:idrefs="PN-00135">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00135">102</uscom:PartNumber> may determine whether the <uscom:PartName com:idrefs="PN-00136">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00136">10</uscom:PartNumber> is moving forward or rearward, accelerating or decelerating, or stopped. In some embodiments, the one or <uscom:PartName com:idrefs="PN-00137">more motion sensors </uscom:PartName><uscom:PartNumber com:id="PN-00137">116</uscom:PartNumber> include one or more wheel speed sensors, the output of which may be used to determine a speed of the <uscom:PartName com:idrefs="PN-00138">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00138">10.</uscom:PartNumber></uscom:P><uscom:P com:pNumber="69" com:id="p-69">[0026]      Still referring to FIG. 3, the <uscom:PartName com:idrefs="PN-00139">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00139">100</uscom:PartNumber> comprises the first</uscom:P><uscom:P com:pNumber="70" com:id="p-70">imaging <uscom:PartName com:idrefs="PN-00140">device </uscom:PartName><uscom:PartNumber com:id="PN-00140">118.</uscom:PartNumber> The <uscom:PartName com:idrefs="PN-00141">first imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00141">118</uscom:PartNumber> is coupled to the <uscom:PartName com:idrefs="PN-00142">communication path </uscom:PartName><uscom:PartNumber com:id="PN-00142">104</uscom:PartNumber> and communicatively coupled to the one or <uscom:PartName com:idrefs="PN-00143">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00143">102.</uscom:PartNumber> The <uscom:PartName com:idrefs="PN-00144">first imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00144">118</uscom:PartNumber> may be any device having an array of sensing devices (e.g., pixels) capable of detecting radiation in an ultraviolet wavelength band, a visible light wavelength band, or an infrared wavelength band. The <uscom:PartName com:idrefs="PN-00145">first imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00145">118</uscom:PartNumber> may have any resolution. The <uscom:PartName com:idrefs="PN-00146">first imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00146">118</uscom:PartNumber> may include an omni-directional camera, or a panoramic camera. In some embodiments, one or more optical components, such as a mirror, fish-eye lens, or any other type of lens may be optically coupled to at least one of the <uscom:PartName com:idrefs="PN-00147">first imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00147">118.</uscom:PartNumber> The <uscom:PartName com:idrefs="PN-00148">first imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00148">118</uscom:PartNumber> may be located on an exterior of the vehicle, e.g., as shown in FIG. 1 to capture an image of the <uscom:PartName com:idrefs="PN-00149">bed </uscom:PartName><uscom:PartNumber com:id="PN-00149">132</uscom:PartNumber> of the <uscom:PartName com:idrefs="PN-00150">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00150">10.</uscom:PartNumber> The <uscom:PartName com:idrefs="PN-00151">first imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00151">118</uscom:PartNumber> may transmit the captured images to the one or <uscom:PartName com:idrefs="PN-00152">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00152">102</uscom:PartNumber> via the <uscom:PartName com:idrefs="PN-00153">communication path </uscom:PartName><uscom:PartNumber com:id="PN-00153">104.</uscom:PartNumber></uscom:P><uscom:P com:pNumber="71" com:id="p-71">[0027]      Still referring to FIG. 3, the <uscom:PartName com:idrefs="PN-00154">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00154">100</uscom:PartNumber> comprises the second</uscom:P><uscom:P com:pNumber="72" com:id="p-72">imaging <uscom:PartName com:idrefs="PN-00155">device </uscom:PartName><uscom:PartNumber com:id="PN-00155">120.</uscom:PartNumber> The <uscom:PartName com:idrefs="PN-00156">second imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00156">120</uscom:PartNumber> is coupled to the <uscom:PartName com:idrefs="PN-00157">communication path </uscom:PartName><uscom:PartNumber com:id="PN-00157">104</uscom:PartNumber> and communicatively coupled to the one or <uscom:PartName com:idrefs="PN-00158">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00158">102.</uscom:PartNumber> The <uscom:PartName com:idrefs="PN-00159">second imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00159">120</uscom:PartNumber> may be similar to the <uscom:PartName com:idrefs="PN-00160">first imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00160">118.</uscom:PartNumber> The <uscom:PartName com:idrefs="PN-00161">second imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00161">120</uscom:PartNumber> may be located on an exterior of the vehicle, e.g., as shown in FIG. 1 to capture a rear view of the <uscom:PartName com:idrefs="PN-00162">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00162">10.</uscom:PartNumber> The <uscom:PartName com:idrefs="PN-00163">second imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00163">120</uscom:PartNumber> may transmit the captured images to the one or <uscom:PartName com:idrefs="PN-00164">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00164">102</uscom:PartNumber> via the <uscom:PartName com:idrefs="PN-00165">communication path </uscom:PartName><uscom:PartNumber com:id="PN-00165">104.</uscom:PartNumber></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00016"/>
+<?PageStart number='9'?><uscom:BoundaryDataReference com:idref="HDR-00017"/>
+<uscom:P com:pNumber="75" com:id="p-75">[0028]       Still referring to FIG. 3, the <uscom:PartName com:idrefs="PN-00166">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00166">100</uscom:PartNumber> can be formed from a</uscom:P><uscom:P com:pNumber="76" com:id="p-76">plurality of modular units, i.e., the <uscom:PartName com:idrefs="PN-00167">display </uscom:PartName><uscom:PartNumber com:id="PN-00167">124,</uscom:PartNumber> the <uscom:PartName com:idrefs="PN-00168">first imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00168">118,</uscom:PartNumber> and the <uscom:PartName com:idrefs="PN-00169">second imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00169">120</uscom:PartNumber> can be formed as modules communicatively coupled form the <uscom:PartName com:idrefs="PN-00170">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00170">100.</uscom:PartNumber> Accordingly, in some embodiments, each of the modules can include at least one of the one or <uscom:PartName com:idrefs="PN-00171">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00171">102</uscom:PartNumber> and/or the one or <uscom:PartName com:idrefs="PN-00172">more memory modules </uscom:PartName><uscom:PartNumber com:id="PN-00172">106.</uscom:PartNumber> Accordingly, it is noted that, while specific modules may be described herein as including the one or <uscom:PartName com:idrefs="PN-00173">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00173">102</uscom:PartNumber> and/or the one or <uscom:PartName com:idrefs="PN-00174">more memory modules </uscom:PartName><uscom:PartNumber com:id="PN-00174">106,</uscom:PartNumber> the embodiments described herein can be implemented with the <uscom:PartName com:idrefs="PN-00175">processors </uscom:PartName><uscom:PartNumber com:id="PN-00175">102</uscom:PartNumber> and <uscom:PartName com:idrefs="PN-00176">memory modules </uscom:PartName><uscom:PartNumber com:id="PN-00176">106</uscom:PartNumber> distributed throughout various communicatively coupled modules.</uscom:P><uscom:P com:pNumber="77" com:id="p-77">[0029]       FIG. 4 depicts a flowchart for displaying a zoomed bed view of the <uscom:PartName com:idrefs="PN-00177">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00177">10</uscom:PartNumber> in</uscom:P><uscom:P com:pNumber="78" com:id="p-78">response to an actuation of a switch, according to one or more embodiments shown and described herein.</uscom:P><uscom:P com:pNumber="79" com:id="p-79">[0030]      In <uscom:PartName com:idrefs="PN-00178">step </uscom:PartName><uscom:PartNumber com:id="PN-00178">410,</uscom:PartNumber> the <uscom:PartName com:idrefs="PN-00179">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00179">100</uscom:PartNumber> receives a first signal indicating a first</uscom:P><uscom:P com:pNumber="80" com:id="p-80">activation of an input device. In embodiments, the <uscom:PartName com:idrefs="PN-00180">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00180">100</uscom:PartNumber> receives a signal indicating the activation of the <uscom:PartName com:idrefs="PN-00181">switch </uscom:PartName><uscom:PartNumber com:id="PN-00181">126</uscom:PartNumber> from the <uscom:PartName com:idrefs="PN-00182">switch </uscom:PartName><uscom:PartNumber com:id="PN-00182">126.</uscom:PartNumber> For example, a driver or a passenger of the <uscom:PartName com:idrefs="PN-00183">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00183">10</uscom:PartNumber> may press or touch the <uscom:PartName com:idrefs="PN-00184">switch </uscom:PartName><uscom:PartNumber com:id="PN-00184">126,</uscom:PartNumber> and the <uscom:PartName com:idrefs="PN-00185">switch </uscom:PartName><uscom:PartNumber com:id="PN-00185">126</uscom:PartNumber> transmits a signal indicating the activation of the <uscom:PartName com:idrefs="PN-00186">switch </uscom:PartName><uscom:PartNumber com:id="PN-00186">126</uscom:PartNumber> to the one or <uscom:PartName com:idrefs="PN-00187">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00187">102.</uscom:PartNumber></uscom:P><uscom:P com:pNumber="81" com:id="p-81">[0031]      In <uscom:PartName com:idrefs="PN-00188">step </uscom:PartName><uscom:PartNumber com:id="PN-00188">420,</uscom:PartNumber> the <uscom:PartName com:idrefs="PN-00189">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00189">100</uscom:PartNumber> determines whether the speed of the</uscom:P><uscom:P com:pNumber="82" com:id="p-82"><uscom:PartName com:idrefs="PN-00190">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00190">10</uscom:PartNumber> is greater than a threshold value. The speed of the <uscom:PartName com:idrefs="PN-00191">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00191">10</uscom:PartNumber> may be measured by the one or <uscom:PartName com:idrefs="PN-00192">more motion sensors </uscom:PartName><uscom:PartNumber com:id="PN-00192">116</uscom:PartNumber> (e.g., by calculating the speed of the <uscom:PartName com:idrefs="PN-00193">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00193">10</uscom:PartNumber> based on an output from the wheel speed sensors in embodiments in which the one or <uscom:PartName com:idrefs="PN-00194">more motion sensors </uscom:PartName><uscom:PartNumber com:id="PN-00194">116</uscom:PartNumber> include one or more wheel speed sensors). The one or <uscom:PartName com:idrefs="PN-00195">more motion sensors </uscom:PartName><uscom:PartNumber com:id="PN-00195">116</uscom:PartNumber> measure the speed of the <uscom:PartName com:idrefs="PN-00196">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00196">10</uscom:PartNumber> and transmit the speed information to the one or <uscom:PartName com:idrefs="PN-00197">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00197">102.</uscom:PartNumber> The one or <uscom:PartName com:idrefs="PN-00198">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00198">102</uscom:PartNumber> may compare the speed of the <uscom:PartName com:idrefs="PN-00199">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00199">10</uscom:PartNumber> to the threshold value. The threshold value may be stored in the one or <uscom:PartName com:idrefs="PN-00200">more memory modules </uscom:PartName><uscom:PartNumber com:id="PN-00200">106.</uscom:PartNumber> The threshold value may be, for example, 70 miles per hour, 65 miles per hour, 55 miles per hour, 45 miles per hour, 35 miles per hour, 35 miles per hour, 25 miles per hour, 10 miles per hour, 5 miles per hour, <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">0</uscom:OCRConfidenceData> miles per hour etc. If the vehicle speed is greater than the threshold value (YES at step<uscom:BoundaryDataReference com:idref="HDR-00018"/></uscom:P><?PageStart number='10'?><uscom:BoundaryDataReference com:idref="HDR-00019"/>
+<uscom:P com:pNumber="84" com:id="p-84">420), the process proceeds to step 430. If the vehicle speed is not greater than the threshold value (NO at <uscom:PartName com:idrefs="PN-00201">step </uscom:PartName><uscom:PartNumber com:id="PN-00201">420),</uscom:PartNumber> the process proceeds to step 440.</uscom:P><uscom:P com:pNumber="85" com:id="p-85">[0032]      In some embodiments, the <uscom:PartName com:idrefs="PN-00202">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00202">100</uscom:PartNumber> may determine whether the</uscom:P><uscom:P com:pNumber="86" com:id="p-86">vehicle moves forward or backward instead of determining whether the speed of the <uscom:PartName com:idrefs="PN-00203">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00203">10</uscom:PartNumber> is greater than a threshold value in <uscom:PartName com:idrefs="PN-00204">step </uscom:PartName><uscom:PartNumber com:id="PN-00204">420.</uscom:PartNumber> For example, the <uscom:PartName com:idrefs="PN-00205">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00205">100</uscom:PartNumber> may determine whether the vehicle moves forward or backward based on signals from the one or <uscom:PartName com:idrefs="PN-00206">more motion sensors </uscom:PartName><uscom:PartNumber com:id="PN-00206">116.</uscom:PartNumber> As another example, the <uscom:PartName com:idrefs="PN-00207">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00207">100</uscom:PartNumber> may determine whether the vehicle moves forward or backward based on signals from a gear transmission of the vehicle. In such alternative embodiments, if it is determined that the vehicle is moving forward, the process proceeds to step 430, but if it is determined that the vehicle is moving rearward, the process proceeds to step 440.</uscom:P><uscom:P com:pNumber="87" com:id="p-87">[0033]      In <uscom:PartName com:idrefs="PN-00208">step </uscom:PartName><uscom:PartNumber com:id="PN-00208">430,</uscom:PartNumber> the <uscom:PartName com:idrefs="PN-00209">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00209">100</uscom:PartNumber> displays a zoomed bed view of the</uscom:P><uscom:P com:pNumber="88" com:id="p-88">vehicle for a first predetermined time. In embodiments, the <uscom:PartName com:idrefs="PN-00210">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00210">100</uscom:PartNumber> displays a zoomed bed view of the <uscom:PartName com:idrefs="PN-00211">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00211">10</uscom:PartNumber> as shown in FIG. 2. The zoomed bed view may be, for example, a predetermined zoomed image of the <uscom:PartName com:idrefs="PN-00212">bed </uscom:PartName><uscom:PartNumber com:id="PN-00212">132</uscom:PartNumber> where the top boundary of the image substantially overlaps with the top of the <uscom:PartName com:idrefs="PN-00213">tailgate </uscom:PartName><uscom:PartNumber com:id="PN-00213">134</uscom:PartNumber> of the vehicle in the image. As another example, the zoomed bed view may be a predetermined zoomed image of the <uscom:PartName com:idrefs="PN-00214">bed </uscom:PartName><uscom:PartNumber com:id="PN-00214">132</uscom:PartNumber> where there is no or minimal predetermined margin between the top of the zoomed image and the top of the <uscom:PartName com:idrefs="PN-00215">tailgate </uscom:PartName><uscom:PartNumber com:id="PN-00215">134</uscom:PartNumber> in the image. The first predetermined time may be stored in the one or <uscom:PartName com:idrefs="PN-00216">more memory modules </uscom:PartName><uscom:PartNumber com:id="PN-00216">106.</uscom:PartNumber> The first predetermined time may be, for example, 5 seconds, 10 seconds, 15 seconds, etc. Displaying the zoomed bed view of for the first predetermined time may allow the driver to temporarily check the status of the <uscom:PartName com:idrefs="PN-00217">bed </uscom:PartName><uscom:PartNumber com:id="PN-00217">132.</uscom:PartNumber> After the <uscom:PartName com:idrefs="PN-00218">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00218">100</uscom:PartNumber> displays the zoomed bed view of the vehicle for the first predetermined time, the <uscom:PartName com:idrefs="PN-00219">display </uscom:PartName><uscom:PartNumber com:id="PN-00219">124</uscom:PartNumber> returns to a display mode before displaying the zoomed bed view, e.g., a navigational map.</uscom:P><uscom:P com:pNumber="89" com:id="p-89">[0034]      In <uscom:PartName com:idrefs="PN-00220">step </uscom:PartName><uscom:PartNumber com:id="PN-00220">440,</uscom:PartNumber> the <uscom:PartName com:idrefs="PN-00221">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00221">100</uscom:PartNumber> displays a view different from the</uscom:P><uscom:P com:pNumber="90" com:id="p-90">zoomed bed view. In embodiments, the <uscom:PartName com:idrefs="PN-00222">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00222">100</uscom:PartNumber> may display a rear view captured by the <uscom:PartName com:idrefs="PN-00223">second imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00223">120</uscom:PartNumber> in FIG. 1. For example, when the <uscom:PartName com:idrefs="PN-00224">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00224">10</uscom:PartNumber> is stopped or moving rearward, in response to the activation of the <uscom:PartName com:idrefs="PN-00225">switch </uscom:PartName><uscom:PartNumber com:id="PN-00225">126,</uscom:PartNumber> the <uscom:PartName com:idrefs="PN-00226">display </uscom:PartName><uscom:PartNumber com:id="PN-00226">124</uscom:PartNumber> may display a rear view captured by the <uscom:PartName com:idrefs="PN-00227">second imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00227">120.</uscom:PartNumber> In some embodiments, the bed<uscom:BoundaryDataReference com:idref="HDR-00020"/></uscom:P><?PageStart number='11'?><uscom:BoundaryDataReference com:idref="HDR-00021"/>
+<uscom:P com:pNumber="92" com:id="p-92">monitoring <uscom:PartName com:idrefs="PN-00228">system </uscom:PartName><uscom:PartNumber com:id="PN-00228">100</uscom:PartNumber> may display the zoomed bed view of the vehicle without time restriction in response to determining that the vehicle speed is not greater than the threshold value. For example, in response to determining that the vehicle speed is not greater than the threshold value, the <uscom:PartName com:idrefs="PN-00229">display </uscom:PartName><uscom:PartNumber com:id="PN-00229">124</uscom:PartNumber> displays the zoomed bed view until the driver or passenger instructs the display to stop displaying the zoomed bed view.</uscom:P><uscom:P com:pNumber="93" com:id="p-93">[0035]       FIG. 5 depicts a flowchart for displaying a zoomed bed view of a vehicle in</uscom:P><uscom:P com:pNumber="94" com:id="p-94">response to an activation of a switch, according to one or more embodiments shown and described herein. In embodiments, the <uscom:PartName com:idrefs="PN-00230">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00230">100</uscom:PartNumber> includes a first timer and a second timer. The first timer sets a first time duration for displaying a zoomed bed view of the <uscom:PartName com:idrefs="PN-00231">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00231">10</uscom:PartNumber> in response to the activation of the switch. The first time duration may be stored in the one or <uscom:PartName com:idrefs="PN-00232">more memory modules </uscom:PartName><uscom:PartNumber com:id="PN-00232">106.</uscom:PartNumber> The first time duration may be a time duration sufficient to allow the driver to temporarily check the status of the bed (e.g., 5 seconds, 10 seconds, 15 seconds, etc.). The second timer sets a second time duration that a driver needs to wait, after a zoomed bed view is displayed, to view the next zoomed bed view. In some embodiments, the second time duration is longer than the first time duration, for example, 1 minute, 2 minutes, etc.</uscom:P><uscom:P com:pNumber="95" com:id="p-95">[0036]       In <uscom:PartName com:idrefs="PN-00233">step </uscom:PartName><uscom:PartNumber com:id="PN-00233">502,</uscom:PartNumber> the <uscom:PartName com:idrefs="PN-00234">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00234">100</uscom:PartNumber> is in an idle state. That is, the bed</uscom:P><uscom:P com:pNumber="96" com:id="p-96">monitoring <uscom:PartName com:idrefs="PN-00235">system </uscom:PartName><uscom:PartNumber com:id="PN-00235">100</uscom:PartNumber> does not receive an input from an input device, e.g., the <uscom:PartName com:idrefs="PN-00236">switch </uscom:PartName><uscom:PartNumber com:id="PN-00236">126</uscom:PartNumber> in FIG. 2. While the <uscom:PartName com:idrefs="PN-00237">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00237">100</uscom:PartNumber> is in an idle state, the <uscom:PartName com:idrefs="PN-00238">display </uscom:PartName><uscom:PartNumber com:id="PN-00238">124</uscom:PartNumber> may display default content, e.g., a navigational map, an audio system interface, entertainment information, etc. For example, by referring to FIG. 6, at time t<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">=</uscom:OCRConfidenceData>0, the <uscom:PartName com:idrefs="PN-00239">display </uscom:PartName><uscom:PartNumber com:id="PN-00239">124</uscom:PartNumber> displays a navigational map.</uscom:P><uscom:P com:pNumber="97" com:id="p-97">[0037]       In <uscom:PartName com:idrefs="PN-00240">step </uscom:PartName><uscom:PartNumber com:id="PN-00240">504,</uscom:PartNumber> the <uscom:PartName com:idrefs="PN-00241">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00241">100</uscom:PartNumber> receives a first signal indicating a first</uscom:P><uscom:P com:pNumber="98" com:id="p-98">activation of the input device. In embodiments, a driver or passenger of the <uscom:PartName com:idrefs="PN-00242">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00242">10</uscom:PartNumber> presses the <uscom:PartName com:idrefs="PN-00243">switch </uscom:PartName><uscom:PartNumber com:id="PN-00243">126,</uscom:PartNumber> and the <uscom:PartName com:idrefs="PN-00244">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00244">100</uscom:PartNumber> receives a signal indicating a first activation of the <uscom:PartName com:idrefs="PN-00245">switch </uscom:PartName><uscom:PartNumber com:id="PN-00245">126.</uscom:PartNumber> For example, by referring to FIG. 6, at time t<uscom:OCRConfidenceData uscom:ocrConfidenceCode="68">=t</uscom:OCRConfidenceData><uscom:OCRConfidenceData uscom:ocrConfidenceCode="6"><com:Sub>i</com:Sub></uscom:OCRConfidenceData>, the <uscom:PartName com:idrefs="PN-00246">switch </uscom:PartName><uscom:PartNumber com:id="PN-00246">126</uscom:PartNumber> is activated.</uscom:P><uscom:P com:pNumber="99" com:id="p-99">[0038]       In <uscom:PartName com:idrefs="PN-00247">step </uscom:PartName><uscom:PartNumber com:id="PN-00247">506,</uscom:PartNumber> the <uscom:PartName com:idrefs="PN-00248">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00248">100</uscom:PartNumber> determines whether the speed of the</uscom:P><uscom:P com:pNumber="100" com:id="p-100"><uscom:PartName com:idrefs="PN-00249">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00249">10</uscom:PartNumber> is greater than a threshold value. The speed of the <uscom:PartName com:idrefs="PN-00250">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00250">10</uscom:PartNumber> may be measured by the one or <uscom:PartName com:idrefs="PN-00251">more motion sensors </uscom:PartName><uscom:PartNumber com:id="PN-00251">116</uscom:PartNumber> as described above. The one or <uscom:PartName com:idrefs="PN-00252">more motion sensors </uscom:PartName><uscom:PartNumber com:id="PN-00252">116</uscom:PartNumber> measure the speed of the <uscom:PartName com:idrefs="PN-00253">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00253">10</uscom:PartNumber> and transmit the speed information to the one or more<uscom:BoundaryDataReference com:idref="HDR-00022"/></uscom:P><?PageStart number='12'?><uscom:BoundaryDataReference com:idref="HDR-00023"/>
+<uscom:P com:pNumber="102" com:id="p-102"><uscom:PartName com:idrefs="PN-00254">processors </uscom:PartName><uscom:PartNumber com:id="PN-00254">102.</uscom:PartNumber> The one or <uscom:PartName com:idrefs="PN-00255">more processors </uscom:PartName><uscom:PartNumber com:id="PN-00255">102</uscom:PartNumber> may compare the speed of the <uscom:PartName com:idrefs="PN-00256">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00256">10</uscom:PartNumber> to the threshold value. The threshold value may be stored in the one or <uscom:PartName com:idrefs="PN-00257">more memory modules </uscom:PartName><uscom:PartNumber com:id="PN-00257">106.</uscom:PartNumber> If the vehicle speed is greater than the threshold value (YES at <uscom:PartName com:idrefs="PN-00258">step </uscom:PartName><uscom:PartNumber com:id="PN-00258">506),</uscom:PartNumber> the process proceeds to step 508. If the vehicle speed is not greater than the threshold value (NO at <uscom:PartName com:idrefs="PN-00259">step </uscom:PartName><uscom:PartNumber com:id="PN-00259">506),</uscom:PartNumber> the process proceeds to step 514.</uscom:P><uscom:P com:pNumber="103" com:id="p-103">[0039]       In <uscom:PartName com:idrefs="PN-00260">step </uscom:PartName><uscom:PartNumber com:id="PN-00260">508,</uscom:PartNumber> the <uscom:PartName com:idrefs="PN-00261">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00261">100</uscom:PartNumber> determines whether the second timer</uscom:P><uscom:P com:pNumber="104" com:id="p-104">expired. If it is determined that the second timer has not been expired, the process returns to step 502, and waits for the next activation of the input device. If it is determined that the second timer has expired (YES at <uscom:PartName com:idrefs="PN-00262">step </uscom:PartName><uscom:PartNumber com:id="PN-00262">508),</uscom:PartNumber> sufficient time has lapsed since the last display of the zoomed bed view, and the process proceeds to step 510.</uscom:P><uscom:P com:pNumber="105" com:id="p-105">[0040]       In <uscom:PartName com:idrefs="PN-00263">step </uscom:PartName><uscom:PartNumber com:id="PN-00263">510,</uscom:PartNumber> the <uscom:PartName com:idrefs="PN-00264">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00264">100</uscom:PartNumber> resets the first timer and the second</uscom:P><uscom:P com:pNumber="106" com:id="p-106">timer and starts the first timer and the second timer. For example, by referring to FIG. 6, the <uscom:PartName com:idrefs="PN-00265">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00265">100</uscom:PartNumber> resets the first timer and the second timer at time <uscom:OCRConfidenceData uscom:ocrConfidenceCode="6">=</uscom:OCRConfidenceData> t<com:Sub>i</com:Sub> when the <uscom:PartName com:idrefs="PN-00266">switch </uscom:PartName><uscom:PartNumber com:id="PN-00266">126</uscom:PartNumber> is pressed. In <uscom:PartName com:idrefs="PN-00267">step </uscom:PartName><uscom:PartNumber com:id="PN-00267">512,</uscom:PartNumber> the <uscom:PartName com:idrefs="PN-00268">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00268">100</uscom:PartNumber> displays a zoomed bed view until the first timer expires. In embodiments, the <uscom:PartName com:idrefs="PN-00269">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00269">100</uscom:PartNumber> displays a zoomed bed view captured by the <uscom:PartName com:idrefs="PN-00270">first imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00270">118</uscom:PartNumber> on the <uscom:PartName com:idrefs="PN-00271">display </uscom:PartName><uscom:PartNumber com:id="PN-00271">124</uscom:PartNumber> for the first time duration set by the first timer. For example, by referring to FIG. 6, the <uscom:PartName com:idrefs="PN-00272">display </uscom:PartName><uscom:PartNumber com:id="PN-00272">124</uscom:PartNumber> displays a zoomed bed view until the first timer expires at time <uscom:OCRConfidenceData uscom:ocrConfidenceCode="6">=</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">t</uscom:OCRConfidenceData><uscom:OCRConfidenceData uscom:ocrConfidenceCode="6"><com:Sub>2</com:Sub></uscom:OCRConfidenceData>. When the first timer expires, the <uscom:PartName com:idrefs="PN-00273">display </uscom:PartName><uscom:PartNumber com:id="PN-00273">124</uscom:PartNumber> switches back to the previous display mode. For example, the <uscom:PartName com:idrefs="PN-00274">display </uscom:PartName><uscom:PartNumber com:id="PN-00274">124</uscom:PartNumber> starts displaying the previous navigational map at time t <uscom:OCRConfidenceData uscom:ocrConfidenceCode="6">=</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">t</uscom:OCRConfidenceData><uscom:OCRConfidenceData uscom:ocrConfidenceCode="6"><com:Sub>2</com:Sub></uscom:OCRConfidenceData> as shown in FIG. 6.</uscom:P><uscom:P com:pNumber="107" com:id="p-107">[0041]       After the <uscom:PartName com:idrefs="PN-00275">display </uscom:PartName><uscom:PartNumber com:id="PN-00275">124</uscom:PartNumber> initiates displaying the zoomed bed view in <uscom:PartName com:idrefs="PN-00276">step </uscom:PartName><uscom:PartNumber com:id="PN-00276">512,</uscom:PartNumber> the</uscom:P><uscom:P com:pNumber="108" com:id="p-108">process returns to step 502 and waits for another activation of the input device. The <uscom:PartName com:idrefs="PN-00277">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00277">100</uscom:PartNumber> may receive a second signal indicating a second activation of the input device in <uscom:PartName com:idrefs="PN-00278">step </uscom:PartName><uscom:PartNumber com:id="PN-00278">504.</uscom:PartNumber> For example, by referring to FIG. 6, the driver of the <uscom:PartName com:idrefs="PN-00279">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00279">10</uscom:PartNumber> may press the <uscom:PartName com:idrefs="PN-00280">switch </uscom:PartName><uscom:PartNumber com:id="PN-00280">126</uscom:PartNumber> and the <uscom:PartName com:idrefs="PN-00281">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00281">100</uscom:PartNumber> may receive the second signal indicating a second activation of the <uscom:PartName com:idrefs="PN-00282">switch </uscom:PartName><uscom:PartNumber com:id="PN-00282">126</uscom:PartNumber> at time t <uscom:OCRConfidenceData uscom:ocrConfidenceCode="6">=</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">t</uscom:OCRConfidenceData><uscom:OCRConfidenceData uscom:ocrConfidenceCode="5"><com:Sub>3</com:Sub></uscom:OCRConfidenceData>. Then, the <uscom:PartName com:idrefs="PN-00283">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00283">100</uscom:PartNumber> again determines whether the vehicle speed is greater than a threshold value in <uscom:PartName com:idrefs="PN-00284">step </uscom:PartName><uscom:PartNumber com:id="PN-00284">506.</uscom:PartNumber> If the vehicle speed is greater than the threshold value (YES at <uscom:PartName com:idrefs="PN-00285">step </uscom:PartName><uscom:PartNumber com:id="PN-00285">506),</uscom:PartNumber> then the <uscom:PartName com:idrefs="PN-00286">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00286">100</uscom:PartNumber> determines whether the second timer has expired in <uscom:PartName com:idrefs="PN-00287">step </uscom:PartName><uscom:PartNumber com:id="PN-00287">508</uscom:PartNumber> in response to the second activation<uscom:BoundaryDataReference com:idref="HDR-00024"/></uscom:P><?PageStart number='13'?><uscom:BoundaryDataReference com:idref="HDR-00025"/>
+<uscom:P com:pNumber="110" com:id="p-110">of the input device. If the <uscom:PartName com:idrefs="PN-00288">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00288">100</uscom:PartNumber> determines that the second timer has not expired (NO at <uscom:PartName com:idrefs="PN-00289">step </uscom:PartName><uscom:PartNumber com:id="PN-00289">508),</uscom:PartNumber> the <uscom:PartName com:idrefs="PN-00290">display </uscom:PartName><uscom:PartNumber com:id="PN-00290">124</uscom:PartNumber> continues displaying what is currently being displayed without changing to a zoomed bed view. For example, by referring to FIG. 6, at time t <uscom:OCRConfidenceData uscom:ocrConfidenceCode="6">=</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">t</uscom:OCRConfidenceData><uscom:OCRConfidenceData uscom:ocrConfidenceCode="5"><com:Sub>3</com:Sub></uscom:OCRConfidenceData>, the second timer is not expired yet, and thus, the <uscom:PartName com:idrefs="PN-00291">display </uscom:PartName><uscom:PartNumber com:id="PN-00291">124</uscom:PartNumber> continues displaying the navigational map even in response to the second activation of the <uscom:PartName com:idrefs="PN-00292">switch </uscom:PartName><uscom:PartNumber com:id="PN-00292">126.</uscom:PartNumber></uscom:P><uscom:P com:pNumber="111" com:id="p-111">[0042]       If the <uscom:PartName com:idrefs="PN-00293">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00293">100</uscom:PartNumber> dete<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">rm</uscom:OCRConfidenceData>ines that the second timer has expired,</uscom:P><uscom:P com:pNumber="112" com:id="p-112">the <uscom:PartName com:idrefs="PN-00294">display </uscom:PartName><uscom:PartNumber com:id="PN-00294">124</uscom:PartNumber> displays a zoomed bed view and the bed monitoring system resets the first timer and the second timer. For example, by referring to FIG. 6, at time t <uscom:OCRConfidenceData uscom:ocrConfidenceCode="6">=</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="85">ts</uscom:OCRConfidenceData>, the switch is pressed, and the second timer expired at time t <uscom:OCRConfidenceData uscom:ocrConfidenceCode="6">=</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">t</uscom:OCRConfidenceData><uscom:OCRConfidenceData uscom:ocrConfidenceCode="6"><com:Sub>4</com:Sub></uscom:OCRConfidenceData>. Then, the <uscom:PartName com:idrefs="PN-00295">display </uscom:PartName><uscom:PartNumber com:id="PN-00295">124</uscom:PartNumber> displays a zoomed bed view and the bed monitoring system resets the first timer and the second timer.</uscom:P><uscom:P com:pNumber="113" com:id="p-113">[0043]       In <uscom:PartName com:idrefs="PN-00296">step </uscom:PartName><uscom:PartNumber com:id="PN-00296">514,</uscom:PartNumber> the <uscom:PartName com:idrefs="PN-00297">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00297">100</uscom:PartNumber> stops a first timer and a second timer</uscom:P><uscom:P com:pNumber="114" com:id="p-114">when it is dete<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">rm</uscom:OCRConfidenceData>ined the vehicle speed is not greater than the threshold value. In <uscom:PartName com:idrefs="PN-00298">step </uscom:PartName><uscom:PartNumber com:id="PN-00298">516,</uscom:PartNumber> the <uscom:PartName com:idrefs="PN-00299">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00299">100</uscom:PartNumber> uses existing camera view logic to display content on the <uscom:PartName com:idrefs="PN-00300">display </uscom:PartName><uscom:PartNumber com:id="PN-00300">124.</uscom:PartNumber> For example, the <uscom:PartName com:idrefs="PN-00301">bed monitoring system </uscom:PartName><uscom:PartNumber com:id="PN-00301">100</uscom:PartNumber> displays a default camera view, e.g., a rear view of the <uscom:PartName com:idrefs="PN-00302">vehicle </uscom:PartName><uscom:PartNumber com:id="PN-00302">10</uscom:PartNumber> captured by the <uscom:PartName com:idrefs="PN-00303">second imaging device </uscom:PartName><uscom:PartNumber com:id="PN-00303">120.</uscom:PartNumber></uscom:P><uscom:P com:pNumber="115" com:id="p-115">[0044]       It should be understood that embodiments described herein are directed to</uscom:P><uscom:P com:pNumber="116" com:id="p-116">systems for monitoring a bed view of a vehicle. A vehicle system includes a display, an input device, a first imaging device configured to capture one or more images of a bed of the vehicle, and a controller configured to receive a first signal indicating a first activation of the input device, dete<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">rm</uscom:OCRConfidenceData>ine whether a speed of the vehicle is greater than a threshold in response to a receipt of the first signal, and instruct the display to display an image of the bed captured by the first imaging device for a first predete<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">rm</uscom:OCRConfidenceData>ined time in response to determining that the vehicle speed is greater than the threshold and in response to the receipt of the first signal. According to the present disclosure, when the input device is activated, the display displays a bed view for a limited time such that a driver or passenger of the vehicle can quickly check the status of the bed and keep driving. The display returns to a default screen (e.g., a navigational map, a radio screen, a navigation screen, etc.) after the predetermined time has passed, so that a duration of potential distraction is limited. Additionally, the image of the bed view may be restricted to the top of the tailgate of the vehicle so that a driver of the vehicle is not able to use the bed view<uscom:BoundaryDataReference com:idref="HDR-00026"/></uscom:P><?PageStart number='14'?><uscom:BoundaryDataReference com:idref="HDR-00027"/>
+<uscom:P com:pNumber="118" com:id="p-118">image as a rear view monitor. In this regard, the system of the present disclosure further reduces distracting the driver and allows the driver to only check the bed.</uscom:P><uscom:P com:pNumber="119" com:id="p-119">[0045]       It is noted that the terms <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">"</uscom:OCRConfidenceData>substantially<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">"</uscom:OCRConfidenceData> and <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">"</uscom:OCRConfidenceData>about<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">"</uscom:OCRConfidenceData> may be utilized herein to</uscom:P><uscom:P com:pNumber="120" com:id="p-120">represent the inherent degree of uncertainty that may be attributed to any quantitative comparison, value, measurement, or other representation. These terms are also utilized herein to represent the degree by which a quantitative representation may vary from a stated reference without resulting in a change in the basic function of the subject matter at issue.</uscom:P><uscom:P com:pNumber="121" com:id="p-121">[0046]        While particular embodiments have been illustrated and described herein, it</uscom:P><uscom:P com:pNumber="122" com:id="p-122">should be understood that various other changes and modifications may be made without departing from the spirit and scope of the claimed subject matter. Moreover, although various aspects of the claimed subject matter have been described herein, such aspects need not be utilized in combination. It is therefore intended that the appended claims cover all such changes and modifications that are within the scope of the claimed subject matter.</uscom:P><uscom:BoundaryDataReference com:idref="HDR-00028"/>
+<uscom:BoundaryDataBag><uscom:BoundaryData><uscom:HeaderText com:id="HDR-00001">22562-2843 / 2018-1001</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00002"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">1</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00003">22562-2843 / 2018-1001</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00004"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">2</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00005">22562-2843 / 2018-1001</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00006"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">3</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00007">22562-2843 / 2018-1001</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00008"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">4</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00009">22562-2843 / 2018-1001</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00010"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">5</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00011">22562-2843 / 2018-1001</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00012"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">6</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00013">22562-2843 / 2018-1001</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00014"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">7</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00015">22562-2843 / 2018-1001</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00016"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">8</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00017">22562-2843 / 2018-1001</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00018"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">9</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00019">22562-2843 / 2018-1001</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00020"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="88">10</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00021">22562-2843 / 2018-1001</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00022"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="88">11</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00023">22562-2843 / 2018-1001</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00024"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="88">12</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00025">22562-2843 / 2018-1001</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00026"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="88">13</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00027">22562-2843 / 2018-1001</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00028"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="88">14</uscom:OCRConfidenceData></uscom:HeaderText>
+</uscom:BoundaryData></uscom:BoundaryDataBag></uspat:SpecificationDocument>

applicant/16373619.xml

@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="utf-8"?><uspat:SpecificationDocument xmlns:uscom="urn:us:gov:doc:uspto:common" xmlns:uspat="urn:us:gov:doc:uspto:patent" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:com="http://www.wipo.int/standards/XMLSchema/ST96/Common" xmlns:pat="http://www.wipo.int/standards/XMLSchema/ST96/Patent" uscom:vendorName="VASTEC" uscom:createDateTime="2020-09-12T16:52:49Z" com:st96Version="V2_1" com:ipoVersion="US_V7_1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent Patent/V7_1/Schema/USPatent/Document/SpecificationDocument_V7_1.xsd" com:documentFileName="16373619.09-11-2020.KEYT5J57RXEAPX0.SPEC.XML" com:id="KEYT5J57RXEAPX0">
+<uspat:DocumentMetadata com:id="ID0000001"><uscom:DocumentCode>SPEC</uscom:DocumentCode><uscom:ApplicationNumberText uscom:electronicText="16373619">16373619</uscom:ApplicationNumberText><com:PageTotalQuantity>13</com:PageTotalQuantity><uscom:ParagraphTotalQuantity>276</uscom:ParagraphTotalQuantity><uscom:OfficialDate>2020-09-11</uscom:OfficialDate></uspat:DocumentMetadata><?PageStart number='1'?><uscom:P com:pNumber="1" com:id="p-1">TrackMy Solutions - TrackMy Implants Utility Patent Application</uscom:P><uscom:P com:pNumber="2" com:id="p-2"><com:U>Specification</com:U></uscom:P><uscom:P com:pNumber="3" com:id="p-3">Title of Invention</uscom:P><uscom:P com:pNumber="4" com:id="p-4">System and method for using unique identifying data for precautionary determination to send</uscom:P><uscom:P com:pNumber="5" com:id="p-5"><uscom:BoundaryDataReference com:idref="LNR-00085"/> notifications to a user to reduce potential negative health outcomes related to implantable devices and recall, adverse event data</uscom:P><uscom:P com:pNumber="6" com:id="p-6">Cross-Reference to Related Applications- This application claims the benefit of U.S. Provisional Application No. 62656975 filed 4/10/18.</uscom:P><uscom:Heading com:id="h-1">Background Information -</uscom:Heading><uscom:P com:pNumber="7" com:id="p-7"><uscom:BoundaryDataReference com:idref="LNR-00086"/> In the health care industry, there is a large desire to increase patient safety through the use of</uscom:P><uscom:P com:pNumber="8" com:id="p-8">data-driven solutions. Consumer-driven health care and interoperability, along with full access</uscom:P><uscom:P com:pNumber="9" com:id="p-9">to an individual's health record is becoming a vital need and reality to lead to better care for</uscom:P><uscom:P com:pNumber="10" com:id="p-10">patients. It is the right of the patient to have full access to their data. Our invention supports</uscom:P><uscom:P com:pNumber="11" com:id="p-11">these factors, and allows a user/patient to access their data, and make this data actionable to<uscom:BoundaryDataReference com:idref="LNR-00087"/> increase their safety.</uscom:P><uscom:P com:pNumber="12" com:id="p-12">To denote some reasoning that led to our invention, and the need for this patent protection -</uscom:P><uscom:P com:pNumber="13" com:id="p-13" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> Recent studies show there has been an increase of device recalls year over year (citing a</uscom:P><uscom:P com:pNumber="14" com:id="p-14" uscom:indentationLevelNumber="L2">report from the FDA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData>CDRH - 97% from <uscom:PartName com:idrefs="PN-00001">FY </uscom:PartName><uscom:PartNumber com:id="PN-00001">2003</uscom:PartNumber> to 2012 for example)</uscom:P><uscom:P com:pNumber="15" com:id="p-15" uscom:indentationLevelNumber="L4" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="0.27">o  Recalls continue to happen at an alarming rate year over year. There is a lot of<uscom:BoundaryDataReference com:idref="LNR-00088"/> good that comes from implantable devices, yet a lot of harm as well. This</uscom:P><uscom:P com:pNumber="16" com:id="p-16" uscom:indentationLevelNumber="L4">invention helps increase safety and hold accountable appropriate parties should complications arise.</uscom:P><uscom:P com:pNumber="17" com:id="p-17" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> Inefficient Recall Strategy for Device Manufacturers</uscom:P><uscom:P com:pNumber="18" com:id="p-18" uscom:indentationLevelNumber="L3">o  The average number of days from firm awareness to recall posting ranged</uscom:P><uscom:P com:pNumber="19" com:id="p-19" uscom:indentationLevelNumber="L4"><uscom:BoundaryDataReference com:idref="LNR-00089"/> between 233.7 - 256.6 days. Our patient outcome tracker invention immediately</uscom:P><uscom:P com:pNumber="20" com:id="p-20" uscom:indentationLevelNumber="L4">notifies Health systems/EMR vendors and patients when a recall happens. We have created a patient list in order for the Health systems to be able to directly<uscom:BoundaryDataReference com:idref="HDR-00001"/></uscom:P><?PageStart number='2'?><uscom:P com:pNumber="21" com:id="p-21" uscom:indentationLevelNumber="L4">communicate with the patients of a device recall and plan next steps (along with allowing the patients next steps via the features within the invention/application).</uscom:P><uscom:P com:pNumber="22" com:id="p-22" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> Lack of Patient and Public Health Awareness around implant tracking</uscom:P><uscom:P com:pNumber="23" com:id="p-23" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> Patient fatalities related to defective implantable devices</uscom:P><uscom:P com:pNumber="24" com:id="p-24" uscom:indentationLevelNumber="L1"><uscom:BoundaryDataReference com:idref="LNR-00085"/> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  This application supports the Recall Process Improvement that was kicked off CDRH</uscom:P><uscom:P com:pNumber="25" com:id="p-25" uscom:indentationLevelNumber="L2">(Center for Devices and Radiological Health) and the FDA (Food and Drug</uscom:P><uscom:P com:pNumber="26" com:id="p-26" uscom:indentationLevelNumber="L2">Administration) in 2010</uscom:P><uscom:P com:pNumber="27" com:id="p-27" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> Per past articles and research there are over <uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>2000 device recalls in the US Annually</uscom:P><uscom:P com:pNumber="28" com:id="p-28" uscom:indentationLevelNumber="L3">o  Due to these device recalls, they cause an undefined amount of issues with a</uscom:P><uscom:P com:pNumber="29" com:id="p-29" uscom:indentationLevelNumber="L4"><uscom:BoundaryDataReference com:idref="LNR-00086"/> given patient (our application can start to better track this data, and push public</uscom:P><uscom:P com:pNumber="30" com:id="p-30" uscom:indentationLevelNumber="L4">health to the forefront especially as <uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">~</uscom:OCRConfidenceData>10,000 baby boomers retire daily (reference Washington Post article from 2016) as of 2016, and a lot of this generation have device implants for varying reasons). These issues comprise of device malfunctions, poor design of devices and can be cut down upon use of our<uscom:BoundaryDataReference com:idref="LNR-00087"/> invention. Being built to the Smart on FHIR specifications, this invention can be</uscom:P><uscom:P com:pNumber="31" com:id="p-31" uscom:indentationLevelNumber="L4">scalable to pull data from EMRs and be able to do a lot of things with it in conjunction with the CMS (Centers for Medicare/Medicaid) push to capture this data. Better overall communication plans of device recalls and notification of patients of high-risk items</uscom:P><uscom:P com:pNumber="32" com:id="p-32" uscom:indentationLevelNumber="L1"><uscom:BoundaryDataReference com:idref="LNR-00088"/> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  In today's marketplace, the leading comparable approach to this invention is mass</uscom:P><uscom:P com:pNumber="33" com:id="p-33" uscom:indentationLevelNumber="L2">advertising through outlets like television networks. Attorneys will discover a recall and start to run mass advertisements through larger TV networks trying to target patients that</uscom:P><uscom:P com:pNumber="34" com:id="p-34" uscom:indentationLevelNumber="L2">have these recalled devices.</uscom:P><uscom:P com:pNumber="35" com:id="p-35" uscom:indentationLevelNumber="L2" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="0.27"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> At times a person will be tech-savvy enough to sign up for email alerts, or hear about a<uscom:BoundaryDataReference com:idref="LNR-00089"/> recall through the news as noted above. Herein lies the issue, if this person does not</uscom:P><uscom:P com:pNumber="36" com:id="p-36" uscom:indentationLevelNumber="L2">actually know what exact device they (or a loved one/family member etc) has there is no</uscom:P><uscom:P com:pNumber="37" com:id="p-37" uscom:indentationLevelNumber="L2">way to positively identify a given recall is on the actual device they have implanted.</uscom:P><uscom:P com:pNumber="38" com:id="p-38" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> Someone in theory (either a user or a healthcare worked), could also manually monitor</uscom:P><uscom:P com:pNumber="39" com:id="p-39" uscom:indentationLevelNumber="L2">the FDA website for recalls. But even if this information is available, the person/worker<uscom:BoundaryDataReference com:idref="LNR-00090"/> must still reference/consult another set of information- specifically a list derived from a</uscom:P><uscom:P com:pNumber="40" com:id="p-40" uscom:indentationLevelNumber="L6" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="5.07">medical record or elsewhere that would need to be at a detailed enough level to compare<uscom:BoundaryDataReference com:idref="HDR-00002"/></uscom:P><?PageStart number='3'?><uscom:P com:pNumber="41" com:id="p-41" uscom:indentationLevelNumber="L2">to any FDA posted recall information. This effort of looking up or "cross-checking" is</uscom:P><uscom:P com:pNumber="42" com:id="p-42" uscom:indentationLevelNumber="L2">subject to human error, very time consuming, thus negatively impacting the efficiency of a health care process that can impact the livelihood of an individual. In summary, cross- checking becomes increasingly complex to ensure a positive identity of a person, to a</uscom:P><uscom:P com:pNumber="43" com:id="p-43" uscom:indentationLevelNumber="L2"><uscom:BoundaryDataReference com:idref="LNR-00085"/> device, to a recall.</uscom:P><uscom:P com:pNumber="44" com:id="p-44" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  These noted processes are not effective, and we are doing patients/users a dis-service</uscom:P><uscom:P com:pNumber="45" com:id="p-45" uscom:indentationLevelNumber="L2">through this process. Our invention augments this, and allows for direct communication</uscom:P><uscom:P com:pNumber="46" com:id="p-46" uscom:indentationLevelNumber="L2">with implant patients/users to increase patient safety.</uscom:P><uscom:Heading com:id="h-2">Summary of the Invention</uscom:Heading><uscom:P com:pNumber="47" com:id="p-47"><uscom:BoundaryDataReference com:idref="LNR-00086"/> System and method are implemented for using unique identifying data for precautionary</uscom:P><uscom:P com:pNumber="48" com:id="p-48">determination to send notifications to a user to reduce potential negative health outcomes related</uscom:P><uscom:P com:pNumber="49" com:id="p-49">to implantable devices and recall, adverse event data. In this way, incidents of recalls/adverse</uscom:P><uscom:P com:pNumber="50" com:id="p-50">events are tracked, and patient safety increases along with positive clinical outcomes.</uscom:P><uscom:P com:pNumber="51" com:id="p-51">In one perspective of the invention, data is stored by user manually using a User Interface<uscom:BoundaryDataReference com:idref="LNR-00087"/> (Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y Implants Application) to search and save an Implantable device.</uscom:P><uscom:P com:pNumber="52" com:id="p-52">This method includes the user using the Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y user interface to search through a search bar that is connected to a general device database (GUDID API endpoint) for a given device, and</uscom:P><uscom:P com:pNumber="53" com:id="p-53">once they find the device they are looking for, click save and this is stored in the Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="68">My</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="54" com:id="p-54">control server/database.</uscom:P><uscom:P com:pNumber="55" com:id="p-55"><uscom:BoundaryDataReference com:idref="LNR-00088"/> In one perspective of the invention, data is stored by capturing of unique device data through the</uscom:P><uscom:P com:pNumber="56" com:id="p-56">use of Smart on FH<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">I</uscom:OCRConfidenceData>R integration with electronic medical records. This is further defined in the</uscom:P><uscom:P com:pNumber="57" com:id="p-57">detail section, yet herein this process is as follows - user clicks a button on a webpage to launch a</uscom:P><uscom:P com:pNumber="58" com:id="p-58">given EMR Authentication API (this is normally a patient portal login or the like; also some</uscom:P><uscom:P com:pNumber="59" com:id="p-59">EMRs use Google Identity verification), the consents to share medical data with Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y, and<uscom:BoundaryDataReference com:idref="LNR-00089"/> FHIR data for the given positively identified user loads on the webpage. FH<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">I</uscom:OCRConfidenceData>R device data, and</uscom:P><uscom:P com:pNumber="60" com:id="p-60">any necessary corresponding data is then stored on the Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y control server/database for</uscom:P><uscom:P com:pNumber="61" com:id="p-61">tracking. This populates the device-person table.</uscom:P><uscom:P com:pNumber="62" com:id="p-62">In one perspective of the invention, data is stored by the direct interface of unique device data to server (Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y) through an HL7 establised interface with another healthcare related technology</uscom:P><uscom:BoundaryDataReference com:idref="HDR-00003"/>
+<?PageStart number='4'?><uscom:P com:pNumber="64" com:id="p-64">system. This data would be positively identified through a unique user identifier, and data stored</uscom:P><uscom:P com:pNumber="65" com:id="p-65">on the Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y control server/database for tracking. This populates the device-person table.</uscom:P><uscom:P com:pNumber="66" com:id="p-66">In one perspective of the invention, data is stored by the manual upload<uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">/</uscom:OCRConfidenceData>data entry into the</uscom:P><uscom:P com:pNumber="67" com:id="p-67">device-person table by an individual or through an automated scanning process. In some</uscom:P><uscom:P com:pNumber="68" com:id="p-68"><uscom:BoundaryDataReference com:idref="LNR-00085"/> scenarios, agreements will be worked out between data providers and Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y to manually enter the user device data directly into Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y control server/database by an individual or through an</uscom:P><uscom:P com:pNumber="69" com:id="p-69">automated scanning process. This populates the device-person table.</uscom:P><uscom:Heading com:id="h-3">Brief Description of the Drawings -</uscom:Heading><uscom:P com:pNumber="70" com:id="p-70" uscom:indentationLevelNumber="L2">In referring to the drawings,</uscom:P><uscom:P com:pNumber="71" com:id="p-71" uscom:indentationLevelNumber="L2"><uscom:BoundaryDataReference com:idref="LNR-00086"/> Fig. 1 provides a block diagram of the operation of the invention;</uscom:P><uscom:P com:pNumber="72" com:id="p-72" uscom:indentationLevelNumber="L2">Fig. 2 provides a block diagram of the invention during manual usage; and,</uscom:P><uscom:P com:pNumber="73" com:id="p-73" uscom:indentationLevelNumber="L2">Fig. 3 provides a block diagram of the invention integrating with electronic medical</uscom:P><uscom:P com:pNumber="74" com:id="p-74">records.</uscom:P><uscom:P com:pNumber="75" com:id="p-75" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">The same reference numerals refer to the same parts throughout the various figures.Detailed Description -</uscom:P><uscom:P com:pNumber="76" com:id="p-76">Our invention is an application and website that notifies patients of applicable active and inactive recalls impacting their implantable devices. Securely collate data around patients, their implanted devices, and any recalls and adverse effects in order to offer solicitations that the user would find</uscom:P><uscom:P com:pNumber="77" com:id="p-77"><uscom:BoundaryDataReference com:idref="LNR-00091"/> relevant</uscom:P><uscom:P com:pNumber="78" com:id="p-78"><uscom:PartName com:idrefs="PN-00002">Core Features: </uscom:PartName><uscom:PartNumber com:id="PN-00002">1.)</uscom:PartNumber> Application and website (hereafter referred to as A&amp;W) to meet HIPAA</uscom:P><uscom:P com:pNumber="79" com:id="p-79">certification guidelines. 2.) A&amp;W shares user database and content. Adding a device to a user profile in either A or W synchronizes across both and any future platforms. 3.) A&amp;W permits</uscom:P><uscom:P com:pNumber="80" com:id="p-80">access to i<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">O</uscom:OCRConfidenceData>S and Android technology platforms as well as common web browsers.<uscom:BoundaryDataReference com:idref="LNR-00089"/> Data Population Processes -</uscom:P><uscom:P com:pNumber="81" com:id="p-81" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  The user manually using a User Interface (Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y Implants Application) to search and</uscom:P><uscom:P com:pNumber="82" com:id="p-82" uscom:indentationLevelNumber="L6" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="5.07">save an Implantable device or<uscom:BoundaryDataReference com:idref="HDR-00004"/></uscom:P><?PageStart number='5'?><uscom:P com:pNumber="83" com:id="p-83" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> The capturing of unique device data through the use of Smart on FH<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">I</uscom:OCRConfidenceData>R integration with</uscom:P><uscom:P com:pNumber="84" com:id="p-84" uscom:indentationLevelNumber="L2">electronic medical records or</uscom:P><uscom:P com:pNumber="85" com:id="p-85" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> The direct interface of unique device data to server (Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y) through an HL7 establised</uscom:P><uscom:P com:pNumber="86" com:id="p-86" uscom:indentationLevelNumber="L2">interface with another healthcare related technology system or</uscom:P><uscom:P com:pNumber="87" com:id="p-87" uscom:indentationLevelNumber="L1"><uscom:BoundaryDataReference com:idref="LNR-00085"/> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> The manual upload<uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">/</uscom:OCRConfidenceData>data entry into the device-person table by an individual or through an</uscom:P><uscom:P com:pNumber="88" com:id="p-88" uscom:indentationLevelNumber="L2">automated scanning process</uscom:P><uscom:P com:pNumber="89" com:id="p-89">Detailed Data Population Processes -</uscom:P><uscom:P com:pNumber="90" com:id="p-90">-Software application details/process steps for user manually using Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y User Interface to</uscom:P><uscom:P com:pNumber="91" com:id="p-91">populate the device-person table:</uscom:P><uscom:P com:pNumber="92" com:id="p-92" uscom:indentationLevelNumber="L2"><uscom:BoundaryDataReference com:idref="LNR-00086"/> 1.) Software application allows Device search from the FDA "DeviceUD<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">I</uscom:OCRConfidenceData>" API dataset.</uscom:P><uscom:P com:pNumber="93" com:id="p-93" uscom:indentationLevelNumber="L2">The API is being called from the FDA through the mobile application using one of three</uscom:P><uscom:P com:pNumber="94" com:id="p-94" uscom:indentationLevelNumber="L2">search types (see Device Search screenshot in Visual tab section):</uscom:P><uscom:P com:pNumber="95" com:id="p-95" uscom:indentationLevelNumber="L2">App Search field name App Display field name DeviceUD<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">I</uscom:OCRConfidenceData> API field name Device ID</uscom:P><uscom:P com:pNumber="96" com:id="p-96" uscom:indentationLevelNumber="L2">Primary DI Number "results<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">__</uscom:OCRConfidenceData>identifiers<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">__</uscom:OCRConfidenceData>id" Name Brand Name<uscom:BoundaryDataReference com:idref="LNR-00087"/> "results<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">__</uscom:OCRConfidenceData>brand_name" Company Name  <com:Image com:id="p-000000" com:imageWrappingStyleCategory="Inline" com:orientationCategory="Portrait" com:imageContentCategory="Chemistry"><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:FileName>16373619.09-11-2020.KEYT5J57RXEAPX0.SPEC.5.15.1275.1652.1476.1692.svg</com:FileName><com:HeightMeasure com:measureUnitCode="In">0.133</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="In">0.67</com:WidthMeasure><com:Alt>Chemistry</com:Alt><com:ColourModeCategory>Black and white</com:ColourModeCategory></com:Image> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="6">_</uscom:OCRConfidenceData>companyname"</uscom:P><uscom:P com:pNumber="97" com:id="p-97" uscom:indentationLevelNumber="L2">2.) In addition to the App Display field names shown above, two additional fields are displayed to the user. App Display field name DeviceUD<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">I</uscom:OCRConfidenceData> API field name Regulation</uscom:P><uscom:P com:pNumber="98" com:id="p-98" uscom:indentationLevelNumber="L2">Number  <com:Image com:id="p-000001" com:imageWrappingStyleCategory="Inline" com:orientationCategory="Portrait" com:imageContentCategory="Chemistry"><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:FileName>16373619.09-11-2020.KEYT5J57RXEAPX0.SPEC.5.18.628.1945.1782.1990.svg</com:FileName><com:HeightMeasure com:measureUnitCode="In">0.15</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="In">3.847</com:WidthMeasure><com:Alt>Chemistry</com:Alt><com:ColourModeCategory>Black and white</com:ColourModeCategory></com:Image> Device Description</uscom:P><uscom:P com:pNumber="99" com:id="p-99" uscom:indentationLevelNumber="L2">"results<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">__</uscom:OCRConfidenceData>device_description <uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">"</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="100" com:id="p-100" uscom:indentationLevelNumber="L2"><uscom:BoundaryDataReference com:idref="LNR-00088"/> 3.) Once the user has saved the appropriate devices to their profile, the devices are</uscom:P><uscom:P com:pNumber="101" com:id="p-101" uscom:indentationLevelNumber="L2">checked against the "Device-Recall" Parsed out table nightly (the recall check process is</uscom:P><uscom:P com:pNumber="102" com:id="p-102" uscom:indentationLevelNumber="L2"><com:Del>ran </com:Del><com:U>ru</com:U><uscom:OCRConfidenceData uscom:ocrConfidenceCode="86"><com:U>n </com:U></uscom:OCRConfidenceData>every 24 hours) using the Device Identifier value. The Device-Recall table is created through TrackMy triggering a pull from the OpenFDA Device Enforcement</uscom:P><uscom:P com:pNumber="103" com:id="p-103" uscom:indentationLevelNumber="L2">Report API, and we then parse out the "codeinfo" field to pull out Device Identifiers<uscom:BoundaryDataReference com:idref="LNR-00089"/> through an algorithm and rules we have created.</uscom:P><uscom:P com:pNumber="104" com:id="p-104" uscom:indentationLevelNumber="L2">4.) If a recall match is found, then the user receives a notification through the application.</uscom:P><uscom:P com:pNumber="105" com:id="p-105" uscom:indentationLevelNumber="L2">Along with a text message (if the user saved their contact information), and a phone</uscom:P><uscom:P com:pNumber="106" com:id="p-106" uscom:indentationLevelNumber="L6" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="5.07">message automated call notification as well<uscom:BoundaryDataReference com:idref="HDR-00005"/></uscom:P><?PageStart number='6'?><uscom:P com:pNumber="107" com:id="p-107" uscom:indentationLevelNumber="L2">In addition to using the recall and device data, we are leveraging Device Adverse Event</uscom:P><uscom:P com:pNumber="108" com:id="p-108" uscom:indentationLevelNumber="L2">data to derive the needs for a notification, additional details on adverse events are as</uscom:P><uscom:P com:pNumber="109" com:id="p-109" uscom:indentationLevelNumber="L2">follows -</uscom:P><uscom:P com:pNumber="110" com:id="p-110" uscom:indentationLevelNumber="L4">Detailed description of Adverse Event usage - Adverse Events impact devices</uscom:P><uscom:P com:pNumber="111" com:id="p-111" uscom:indentationLevelNumber="L4"><uscom:BoundaryDataReference com:idref="LNR-00085"/> that have not yet been recalled. They indicate that something has happened</uscom:P><uscom:P com:pNumber="112" com:id="p-112" uscom:indentationLevelNumber="L4">involving a particular device, but the device itself has not yet been identified as causing the incident. This information may be available months or years in advance of a recall. As such, sharing of such information with patients must be handled lightly. Methods of joining "DeviceUD<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">I</uscom:OCRConfidenceData>" to "Adverse Event" are<uscom:BoundaryDataReference com:idref="LNR-00086"/> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">'</uscom:OCRConfidenceData>results<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">__</uscom:OCRConfidenceData>device<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">__</uscom:OCRConfidenceData>catalognumber' or <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">'</uscom:OCRConfidenceData>results<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">__</uscom:OCRConfidenceData>device<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">__</uscom:OCRConfidenceData>model_number'</uscom:P><uscom:P com:pNumber="113" com:id="p-113">-The capturing of unique device data through the use of Smart on FHIR integration with</uscom:P><uscom:P com:pNumber="114" com:id="p-114">electronic medical records</uscom:P><uscom:P com:pNumber="115" com:id="p-115" uscom:indentationLevelNumber="L2">1.) To assist users in building their device profiles, the use of Smart on FHIR APIs are</uscom:P><uscom:P com:pNumber="116" com:id="p-116" uscom:indentationLevelNumber="L2">leveraged. This allows the user to connect to their EHR records and download their</uscom:P><uscom:P com:pNumber="117" com:id="p-117" uscom:indentationLevelNumber="L2"><uscom:BoundaryDataReference com:idref="LNR-00087"/> implantable device data into TMS database (this is further defined in Model C below and</uscom:P><uscom:P com:pNumber="118" com:id="p-118" uscom:indentationLevelNumber="L2">in the drawings for Model C).</uscom:P><uscom:P com:pNumber="119" com:id="p-119" uscom:indentationLevelNumber="L2">2.) In addition, we will be offering patient education tied to the user's device list (patient</uscom:P><uscom:P com:pNumber="120" com:id="p-120" uscom:indentationLevelNumber="L2">education content company to be named TBD; ex- UpToDate)</uscom:P><uscom:P com:pNumber="121" com:id="p-121" uscom:indentationLevelNumber="L2">3.) Users should be contacted by email as well as push notification along with phone<uscom:BoundaryDataReference com:idref="LNR-00088"/> messages</uscom:P><uscom:P com:pNumber="122" com:id="p-122" uscom:indentationLevelNumber="L2">4.) Load article links in app to push to users. Linking WordPress blog so that as we post</uscom:P><uscom:P com:pNumber="123" com:id="p-123" uscom:indentationLevelNumber="L2">to the blog, link to user.</uscom:P><uscom:P com:pNumber="124" com:id="p-124" uscom:indentationLevelNumber="L2">This is further detailed in the following sections.</uscom:P><uscom:P com:pNumber="125" com:id="p-125">-The direct interface of unique device data to server (Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y) through an HL7 establised<uscom:BoundaryDataReference com:idref="LNR-00089"/> interface with another healthcare related technology system or</uscom:P><uscom:P com:pNumber="126" com:id="p-126" uscom:indentationLevelNumber="L2">1.) An established relationship would be built between Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y and a given client (i.e.- Hospital); a unique identifying data element - i.e. - SSN, Patient ID, etc., would be</uscom:P><uscom:P com:pNumber="127" com:id="p-127" uscom:indentationLevelNumber="L2">exchanged between Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y and Client to positively identify a given patient.</uscom:P><uscom:BoundaryDataReference com:idref="HDR-00006"/>
+<?PageStart number='7'?><uscom:P com:pNumber="129" com:id="p-129" uscom:indentationLevelNumber="L2">2.) Once this is done, Client can send patient data (once patient has went in and</uscom:P><uscom:P com:pNumber="130" com:id="p-130" uscom:indentationLevelNumber="L2">consented) to TrackMy to be loaded on the device-person table.</uscom:P><uscom:P com:pNumber="131" com:id="p-131">-The manual upload<uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">/</uscom:OCRConfidenceData>data entry into the device-person table by an individual or through an</uscom:P><uscom:P com:pNumber="132" com:id="p-132">automated scanning process</uscom:P><uscom:P com:pNumber="133" com:id="p-133" uscom:indentationLevelNumber="L1"><uscom:BoundaryDataReference com:idref="LNR-00085"/> 1.) For this process/data upload, this assumes patient consent has been established upon</uscom:P><uscom:P com:pNumber="134" com:id="p-134" uscom:indentationLevelNumber="L2">account creation.</uscom:P><uscom:P com:pNumber="135" com:id="p-135" uscom:indentationLevelNumber="L1">2.) Patient/User allows Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y to work with Surgeon/Provider to upload Device Identifier</uscom:P><uscom:P com:pNumber="136" com:id="p-136" uscom:indentationLevelNumber="L2">data into database and load on the device-person table</uscom:P><uscom:P com:pNumber="137" com:id="p-137">Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y Implants Architecture</uscom:P><uscom:P com:pNumber="138" com:id="p-138"><uscom:BoundaryDataReference com:idref="LNR-00086"/> As currently notated, there are three models for the architecture.</uscom:P><uscom:P com:pNumber="139" com:id="p-139">Model A, <com:U>as shown in Figure </com:U>1 is as follows -</uscom:P><uscom:P com:pNumber="140" com:id="p-140">Fig. 1 - Model A - Manual - TrackMy Technology Patent is being submitted to cover all of</uscom:P><uscom:P com:pNumber="141" com:id="p-141">these model flows, as we reserve the right to leverage enhancements to technology for optimal performance for our end-user community as well as there is more than one way to get data into<uscom:BoundaryDataReference com:idref="LNR-00087"/> the Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y database/servers.</uscom:P><uscom:P com:pNumber="142" com:id="p-142">Fig. 1 utilizes the following reference characters shown in index form:</uscom:P><uscom:P com:pNumber="143" com:id="p-143">100   Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y Implants Website</uscom:P><uscom:P com:pNumber="144" com:id="p-144">110   TrackMy Implants App</uscom:P><uscom:P com:pNumber="145" com:id="p-145">120   Open FDA API Recall UDI<uscom:BoundaryDataReference com:idref="LNR-00088"/> 130   Open FDA API Device UDI</uscom:P><uscom:P com:pNumber="146" com:id="p-146">140   TrackMy Database</uscom:P><uscom:P com:pNumber="147" com:id="p-147">10    line between 100 and 120, call recall API by Device Details, recall returned if matched</uscom:P><uscom:P com:pNumber="148" com:id="p-148">11    line between 100 and 130, recall process</uscom:P><uscom:P com:pNumber="149" com:id="p-149">40    line between 100 and 140, flow</uscom:P><uscom:P com:pNumber="150" com:id="p-150"><uscom:BoundaryDataReference com:idref="LNR-00089"/> 41    line between 100 and 110, like user experience</uscom:P><uscom:P com:pNumber="151" com:id="p-151">42    line between 110 and 120, user search call to API, user search results returned from API,</uscom:P><uscom:P com:pNumber="152" com:id="p-152" uscom:indentationLevelNumber="L6" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="5.60">bidirectional dataflow<uscom:BoundaryDataReference com:idref="HDR-00007"/></uscom:P><?PageStart number='8'?><uscom:P com:pNumber="153" com:id="p-153" uscom:indentationLevelNumber="L2"><uscom:BoundaryDataReference com:idref="LNR-00092"/> line between 110 and 130, user search call to API, user search results returned from API,</uscom:P><uscom:P com:pNumber="154" com:id="p-154" uscom:indentationLevelNumber="L3"><uscom:BoundaryDataReference com:idref="LNR-00093"/> dataflow</uscom:P><uscom:P com:pNumber="155" com:id="p-155" uscom:indentationLevelNumber="L2"><uscom:BoundaryDataReference com:idref="LNR-00094"/> line between 110 and 140, flow</uscom:P><uscom:P com:pNumber="156" com:id="p-156"><uscom:BoundaryDataReference com:idref="LNR-00085"/> Flow <uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">-</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="157" com:id="p-157" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData>  User has downloaded TrackMy Implants technology or logged in via Web App</uscom:P><uscom:P com:pNumber="158" com:id="p-158" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData>  User Signs in with Email address, Single Sign On with Facebook, Google, or Creates a</uscom:P><uscom:P com:pNumber="159" com:id="p-159" uscom:indentationLevelNumber="L2">New Account</uscom:P><uscom:P com:pNumber="160" com:id="p-160" uscom:indentationLevelNumber="L2" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="0.27"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData>  User clicks search button (see on app visual tab), enters data to search (only can search<uscom:BoundaryDataReference com:idref="LNR-00086"/> what API allows today (leads to Model B)) and it evokes the API call to Device UDI</uscom:P><uscom:P com:pNumber="161" com:id="p-161" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData>  User sees information on device (see on app visual tab) and saves device</uscom:P><uscom:P com:pNumber="162" com:id="p-162" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData>  Recall API call runs nightly and triggers on saved device information</uscom:P><uscom:P com:pNumber="163" com:id="p-163" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData>  If Recall Match takes place, push notification and text message and phone call (if have</uscom:P><uscom:P com:pNumber="164" com:id="p-164" uscom:indentationLevelNumber="L1" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.27">data) is sent to user (see recall visual)<uscom:BoundaryDataReference com:idref="LNR-00087"/> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData>  TrackMy Database <uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">-</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="165" com:id="p-165" uscom:indentationLevelNumber="L4" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="0.27">o User Data Saved to Database; Saved Devices Show to User from Database; Alerts saved to Database once triggered o Every 24 hours, we look for new data by repulling the API data, normalizing it, and reloading into our Database Schema<uscom:BoundaryDataReference com:idref="LNR-00088"/> o The Following Open<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">F</uscom:OCRConfidenceData>DA APIs we are pulling into our Database, normalizing and</uscom:P><uscom:P com:pNumber="166" com:id="p-166" uscom:indentationLevelNumber="L4">allowing for a more robust user search<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData>recall process</uscom:P><uscom:P com:pNumber="167" com:id="p-167" uscom:indentationLevelNumber="L5" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="0.27"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> OpenFDA APIs we are using, are all that exist today at -<com:U> https://open.fda.</com:U><uscom:OCRConfidenceData uscom:ocrConfidenceCode="54"><com:U> g</com:U></uscom:OCRConfidenceData><com:U>ov/device/</com:U></uscom:P><uscom:P com:pNumber="168" com:id="p-168" uscom:indentationLevelNumber="L4"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> https://open.fda.gov/device/event<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData><uscom:BoundaryDataReference com:idref="LNR-00089"/> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> https://open.fda.gov/device/classification<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="169" com:id="p-169" uscom:indentationLevelNumber="L4"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> https://open.fda.gov/device/<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="8686">10k/</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="170" com:id="p-170" uscom:indentationLevelNumber="L4"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> https://open.fda.gov/device/pma<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="171" com:id="p-171" uscom:indentationLevelNumber="L4"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> https://open.fda.gov/device/registrationlisting/</uscom:P><uscom:P com:pNumber="172" com:id="p-172" uscom:indentationLevelNumber="L4"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> https://open.fda.gov/device/recal<uscom:OCRConfidenceData uscom:ocrConfidenceCode="52">l/</uscom:OCRConfidenceData><uscom:BoundaryDataReference com:idref="LNR-00090"/> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="2"><com:Sup>m</com:Sup></uscom:OCRConfidenceData> https://open.fda.gov/device/enforcement<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData><uscom:BoundaryDataReference com:idref="HDR-00008"/></uscom:P><?PageStart number='9'?><uscom:P com:pNumber="173" com:id="p-173" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="1.07"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> https://open.fda.gov/device/udi/ The application and website hit the OpenFDA APIs on demand, store retrieved information in a</uscom:P><uscom:P com:pNumber="174" com:id="p-174">user profile database shared across all A&amp;W platforms. As noted above, the profile would also</uscom:P><uscom:P com:pNumber="175" com:id="p-175">eventually include information retrieved from the user's Electronic Health Records (EHR),</uscom:P><uscom:P com:pNumber="176" com:id="p-176"><uscom:BoundaryDataReference com:idref="LNR-00085"/> which would be used to trigger the Recall API. The Recall API is called at least nightly for all user devices in the database. The Device API will continue to be called on demand by manual</uscom:P><uscom:P com:pNumber="177" com:id="p-177">search. Exception reports would be enabled on a weekly or daily basis to ensure that all devices in the database can be matched to records from the Device API (ensuring data integrity for items</uscom:P><uscom:P com:pNumber="178" com:id="p-178">added through EHR integration).</uscom:P><uscom:P com:pNumber="179" com:id="p-179"><uscom:BoundaryDataReference com:idref="LNR-00086"/> Model B, as shown in Figure 2 is as follows -</uscom:P><uscom:P com:pNumber="180" com:id="p-180">Fig. 2 utilizes the following reference characters shown in index form:</uscom:P><uscom:P com:pNumber="181" com:id="p-181">100   Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y Implants Website</uscom:P><uscom:P com:pNumber="182" com:id="p-182">110   TrackMy Implants App</uscom:P><uscom:P com:pNumber="183" com:id="p-183">140   TrackMy Database</uscom:P><uscom:P com:pNumber="184" com:id="p-184"><uscom:BoundaryDataReference com:idref="LNR-00087"/> 150   Open FDA API</uscom:P><uscom:P com:pNumber="185" com:id="p-185">12    line between 100 and 140, call database for recall by device details 13    line between 110 and 140, call database for recall by device details</uscom:P><uscom:P com:pNumber="186" com:id="p-186">40    line between 100 and 140, flow</uscom:P><uscom:P com:pNumber="187" com:id="p-187">41    line between 100 and 110, like user experience</uscom:P><uscom:P com:pNumber="188" com:id="p-188"><uscom:BoundaryDataReference com:idref="LNR-00088"/> 44    line between 110 and 140, user search call to API, user search results returned from API,</uscom:P><uscom:P com:pNumber="189" com:id="p-189">bidirectional dataflow</uscom:P><uscom:P com:pNumber="190" com:id="p-190">49      line between 140 and 150, flow</uscom:P><uscom:P com:pNumber="191" com:id="p-191">Flow -</uscom:P><uscom:P com:pNumber="192" com:id="p-192" uscom:indentationLevelNumber="L1"><uscom:BoundaryDataReference com:idref="LNR-00089"/> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData>  User has downloaded TrackMy Implants technology or logged in via Web Application</uscom:P><uscom:P com:pNumber="193" com:id="p-193" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData> User Signs in with Email address, Single Sign On with Facebook, Google, or Creates a</uscom:P><uscom:P com:pNumber="194" com:id="p-194" uscom:indentationLevelNumber="L6" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="5.07">New Account<uscom:BoundaryDataReference com:idref="HDR-00009"/></uscom:P><?PageStart number='10'?><uscom:P com:pNumber="195" com:id="p-195" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData> User clicks search button (see on app visual tab), enters data to search (this search is</uscom:P><uscom:P com:pNumber="196" com:id="p-196" uscom:indentationLevelNumber="L2">controlled by TrackMy and is from our database, where we can provide an improved user</uscom:P><uscom:P com:pNumber="197" com:id="p-197" uscom:indentationLevelNumber="L2">search)</uscom:P><uscom:P com:pNumber="198" com:id="p-198" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData>  User sees information on device (see on app visual tab) and saves device</uscom:P><uscom:P com:pNumber="199" com:id="p-199" uscom:indentationLevelNumber="L1"><uscom:BoundaryDataReference com:idref="LNR-00085"/> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData>   Recall Match Process call runs nightly and triggers on saved device information</uscom:P><uscom:P com:pNumber="200" com:id="p-200" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData>  If Recall Match takes place, push notification and text message and phone call (if have</uscom:P><uscom:P com:pNumber="201" com:id="p-201" uscom:indentationLevelNumber="L2">data) is sent to user (see recall visual)TrackMy Database -</uscom:P><uscom:P com:pNumber="202" com:id="p-202" uscom:indentationLevelNumber="L4" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="0.27">o User Data Saved to Database; Saved Devices Show to User from Database; Alerts saved to Database once triggered<uscom:BoundaryDataReference com:idref="LNR-00086"/> o  Every 24 hours, we look for new data by repulling the API data, normalizing it,</uscom:P><uscom:P com:pNumber="203" com:id="p-203" uscom:indentationLevelNumber="L3" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.27">and reloading into our Database Schema o  The Following Open<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">F</uscom:OCRConfidenceData>DA APIs we are pulling into our Database, normalizing and allowing for a more robust user search<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData>recall process</uscom:P><uscom:P com:pNumber="204" com:id="p-204" uscom:indentationLevelNumber="L5" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="0.27"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> OpenFDA APIs we are using, are all that exist today at -<uscom:BoundaryDataReference com:idref="LNR-00087"/> <com:U>https://open.fda.</com:U><uscom:OCRConfidenceData uscom:ocrConfidenceCode="5"><com:U>g</com:U></uscom:OCRConfidenceData><com:U>ov/device/</com:U></uscom:P><uscom:P com:pNumber="205" com:id="p-205" uscom:indentationLevelNumber="L4"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  https://open.fda.gov/device/event<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="206" com:id="p-206" uscom:indentationLevelNumber="L4"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  https://open.fda.gov/device/classification<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="207" com:id="p-207" uscom:indentationLevelNumber="L4"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  https://open.fda.gov/device/<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="8686">10k/</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="208" com:id="p-208" uscom:indentationLevelNumber="L4"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  https://open.fda.gov/device/pma<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData><uscom:BoundaryDataReference com:idref="LNR-00088"/> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="2"><com:Sup>m</com:Sup></uscom:OCRConfidenceData>   https://open.fda.gov/device/registrationlisting/</uscom:P><uscom:P com:pNumber="209" com:id="p-209" uscom:indentationLevelNumber="L4"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  https://open.fda.gov/device/recal<uscom:OCRConfidenceData uscom:ocrConfidenceCode="52">l/</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="210" com:id="p-210" uscom:indentationLevelNumber="L4"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  https://open.fda.gov/device/enforcement<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="211" com:id="p-211" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="1.07"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  https://open.fda.gov/device/udi/ Directing all query calls to a hosted database containing all available API content from the FDA.<uscom:BoundaryDataReference com:idref="LNR-00089"/> The FDA makes these datafiles available on a daily basis, thus giving TrackMy more control</uscom:P><uscom:P com:pNumber="212" com:id="p-212">over the data and reduce our API calls to the FDA by regularly downloading the files. This</uscom:P><uscom:P com:pNumber="213" com:id="p-213">allows flexibility to add additional API datasets should they become available (potentially in the</uscom:P><uscom:P com:pNumber="214" com:id="p-214">Medicare Claims space).</uscom:P><uscom:P com:pNumber="215" com:id="p-215">Model C, as shown in Figure 3 is as follows -</uscom:P><uscom:P com:pNumber="216" com:id="p-216"><uscom:BoundaryDataReference com:idref="LNR-00090"/> Fig. 3 utilizes the following reference characters shown in index form:</uscom:P><uscom:BoundaryDataReference com:idref="HDR-00010"/>
+<?PageStart number='11'?><uscom:P com:pNumber="218" com:id="p-218" uscom:indentationLevelNumber="L2"><uscom:BoundaryDataReference com:idref="LNR-00095"/> Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y Implants Website</uscom:P><uscom:P com:pNumber="219" com:id="p-219" uscom:indentationLevelNumber="L2"><uscom:BoundaryDataReference com:idref="LNR-00096"/> TrackMy Implants App</uscom:P><uscom:P com:pNumber="220" com:id="p-220" uscom:indentationLevelNumber="L2"><uscom:BoundaryDataReference com:idref="LNR-00097"/> TrackMy Database</uscom:P><uscom:P com:pNumber="221" com:id="p-221" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53"><uscom:BoundaryDataReference com:idref="LNR-00098"/> Open FDA API<uscom:BoundaryDataReference com:idref="LNR-00085"/> 160   Authentication<uscom:BoundaryDataReference com:idref="LNR-00099"/> EMR Integration Smart on FHIR API</uscom:P><uscom:P com:pNumber="222" com:id="p-222" uscom:indentationLevelNumber="L2"><uscom:BoundaryDataReference com:idref="LNR-00100"/> Electronic Medical Record</uscom:P><uscom:P com:pNumber="223" com:id="p-223" uscom:indentationLevelNumber="L2"><uscom:BoundaryDataReference com:idref="LNR-00101"/> line between 100 and 140, call database for recall by device details, recall returned if</uscom:P><uscom:P com:pNumber="224" com:id="p-224"><uscom:BoundaryDataReference com:idref="LNR-00086"/> 13    line between 110 and 140, call database for recall by device details, recall returned if</uscom:P><uscom:P com:pNumber="225" com:id="p-225" uscom:indentationLevelNumber="L2"><uscom:BoundaryDataReference com:idref="LNR-00102"/> line between 110 and 160, flow</uscom:P><uscom:P com:pNumber="226" com:id="p-226" uscom:indentationLevelNumber="L2"><uscom:BoundaryDataReference com:idref="LNR-00103"/> line between 100 and 140, augmented device details, search</uscom:P><uscom:P com:pNumber="227" com:id="p-227" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53"><uscom:BoundaryDataReference com:idref="LNR-00104"/> line between 100 and 160, bidirectional flow<uscom:BoundaryDataReference com:idref="LNR-00087"/> 47    line between 160 and 170, bidirectional flow</uscom:P><uscom:P com:pNumber="228" com:id="p-228" uscom:indentationLevelNumber="L2"><uscom:BoundaryDataReference com:idref="LNR-00105"/> line between 170 and 180, bidirectional flow</uscom:P><uscom:P com:pNumber="229" com:id="p-229" uscom:indentationLevelNumber="L2"><uscom:BoundaryDataReference com:idref="LNR-00106"/> line between 140 and 150, flow</uscom:P><uscom:Heading com:id="h-4">-</uscom:Heading><uscom:P com:pNumber="230" com:id="p-230" uscom:indentationLevelNumber="L1"><uscom:BoundaryDataReference com:idref="LNR-00093"/> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData> User has downloaded TrackMy Implants technology or logged in via Web Application<uscom:BoundaryDataReference com:idref="LNR-00088"/> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData>  User Signs in with Email address, Single Sign On with Facebook, Google, or Creates a</uscom:P><uscom:P com:pNumber="231" com:id="p-231" uscom:indentationLevelNumber="L2">New Account</uscom:P><uscom:P com:pNumber="232" com:id="p-232" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData> User Authenticates through Identity Provider of Healthcare Organization (ie - Patient</uscom:P><uscom:P com:pNumber="233" com:id="p-233" uscom:indentationLevelNumber="L2">Portal Credentials; Oauth Process)</uscom:P><uscom:P com:pNumber="234" com:id="p-234" uscom:indentationLevelNumber="L2" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="0.27"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData>  User is presented with Available Medical Device Data from Electronic Health Record<uscom:BoundaryDataReference com:idref="LNR-00089"/> Vendor (ie - Allscripts; dependent who is connected to our business)</uscom:P><uscom:P com:pNumber="235" com:id="p-235" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData>  User Accepts Medical Device Data and Signs Patient Consent to save data into Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="68">My</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="236" com:id="p-236" uscom:indentationLevelNumber="L2">Database</uscom:P><uscom:P com:pNumber="237" com:id="p-237" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData>  Recall Match Process call runs nightly and triggers on saved device information</uscom:P><uscom:P com:pNumber="238" com:id="p-238" uscom:indentationLevelNumber="L2" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="0.27"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData>  If Recall Match takes place, push notification and text message and phone call (if have<uscom:BoundaryDataReference com:idref="LNR-00090"/> data) is sent to user (see recall visual)<uscom:BoundaryDataReference com:idref="HDR-00011"/></uscom:P><?PageStart number='12'?><uscom:P com:pNumber="239" com:id="p-239" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">"</uscom:OCRConfidenceData> TrackMy Database <uscom:OCRConfidenceData uscom:ocrConfidenceCode="8">-</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="240" com:id="p-240" uscom:indentationLevelNumber="L4" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="0.27">o User Data Saved to Database; Saved Devices Show to User from Database; Alerts saved to Database once triggered o  Every 24 hours, we look for new data by repulling the API data, normalizing it,</uscom:P><uscom:P com:pNumber="241" com:id="p-241" uscom:indentationLevelNumber="L4"><uscom:BoundaryDataReference com:idref="LNR-00085"/> and reloading into our Database Schema</uscom:P><uscom:P com:pNumber="242" com:id="p-242" uscom:indentationLevelNumber="L4" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="0.27">o  The Following Open<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">F</uscom:OCRConfidenceData>DA APIs we are pulling into our Database, normalizing and allowing for a more robust user search<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData>recall process</uscom:P><uscom:P com:pNumber="243" com:id="p-243" uscom:indentationLevelNumber="L5" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="0.27"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> OpenFDA APIs we are using, are all that exist today at -<com:U> https://open.fda.</com:U><uscom:OCRConfidenceData uscom:ocrConfidenceCode="54"><com:U> g</com:U></uscom:OCRConfidenceData><com:U>ov/device/</com:U></uscom:P><uscom:P com:pNumber="244" com:id="p-244" uscom:indentationLevelNumber="L4"><uscom:BoundaryDataReference com:idref="LNR-00086"/> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="2"><com:Sup>m</com:Sup></uscom:OCRConfidenceData>  https://open.fda.gov/device/event<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="245" com:id="p-245" uscom:indentationLevelNumber="L4"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  https://open.fda.gov/device/classification<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="246" com:id="p-246" uscom:indentationLevelNumber="L4"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  https://open.fda.gov/device/<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="8686">10k/</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="247" com:id="p-247" uscom:indentationLevelNumber="L4"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  https://open.fda.gov/device/pma<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="248" com:id="p-248" uscom:indentationLevelNumber="L4"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  https://open.fda.gov/device/registrationlisting/<uscom:BoundaryDataReference com:idref="LNR-00087"/> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  https://open.fda.gov/device/recal<uscom:OCRConfidenceData uscom:ocrConfidenceCode="52">l/</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="249" com:id="p-249" uscom:indentationLevelNumber="L4"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  https://open.fda.gov/device/enforcement<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="250" com:id="p-250" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="1.07"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  https://open.fda.gov/device/udi/ Replaces the Manual search and save by adding in the Smart on FH<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">I</uscom:OCRConfidenceData>R Integration with varying</uscom:P><uscom:P com:pNumber="251" com:id="p-251">Electronic Medical Records (ie - Allscripts). There still is an augmented search tied into the<uscom:BoundaryDataReference com:idref="LNR-00088"/> FHI<uscom:OCRConfidenceData uscom:ocrConfidenceCode="86">R/</uscom:OCRConfidenceData>EMR Integration should relevant data not be brought fully in via the EMR Integration.</uscom:P><uscom:P com:pNumber="252" com:id="p-252">There is an authentication process the user has to complete using OAuth and authenticating through the Identity Provider (in this case an example is the Hospital Systems/organizations</uscom:P><uscom:P com:pNumber="253" com:id="p-253">Patient Portal). The recall process remains <com:Del>in tact </com:Del><com:U>intact/the</com:U> same for all Models. This</uscom:P><uscom:P com:pNumber="254" com:id="p-254">technology is not limited to a particular Electronic Medical Record Vendor (ie Allscripts), our<uscom:BoundaryDataReference com:idref="LNR-00089"/> technology is vendor agnostic and we will determine through agreements between various EMR</uscom:P><uscom:P com:pNumber="255" com:id="p-255">vendors and</uscom:P><uscom:P com:pNumber="256" com:id="p-256">TrackMy; based on business needs and ongoing partnerships etc.</uscom:P><uscom:P com:pNumber="257" com:id="p-257">Any architectural model used must accommodate three stakeholder groups. 1.) The patients who</uscom:P><uscom:P com:pNumber="258" com:id="p-258">log into the application are assured they maintain control of their data. 2.) Admin ability to</uscom:P><uscom:P com:pNumber="259" com:id="p-259" uscom:indentationLevelNumber="L6" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="5.60"><uscom:BoundaryDataReference com:idref="LNR-00090"/> monitor changes in data and resolve exceptions where stored user devices cannot be reconciled<uscom:BoundaryDataReference com:idref="HDR-00012"/></uscom:P><?PageStart number='13'?><uscom:P com:pNumber="260" com:id="p-260">against the DeviceUD<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">I</uscom:OCRConfidenceData> dataset. 3.) Third Party options to pay for leads to patients impacted by</uscom:P><uscom:P com:pNumber="261" com:id="p-261">Recalls (initially) and Adverse Effects (later). Users may not be contacted without providing</uscom:P><uscom:P com:pNumber="262" com:id="p-262">permission first; at minimum this will require an agreement checkbox or opt out capability.</uscom:P><uscom:P com:pNumber="263" com:id="p-263">Further discussion will be required to determine the nature of these solicitations, but</uscom:P><uscom:P com:pNumber="264" com:id="p-264"><uscom:BoundaryDataReference com:idref="LNR-00085"/> development has proceeded with this objective in mind.</uscom:P><uscom:P com:pNumber="265" com:id="p-265">Examples of how it will be used:</uscom:P><uscom:P com:pNumber="266" com:id="p-266" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> Patients can/will use technology to track and receive alerts of recalled medical devices</uscom:P><uscom:P com:pNumber="267" com:id="p-267" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> Patients can/will receive electronic patient education through technology</uscom:P><uscom:P com:pNumber="268" com:id="p-268" uscom:indentationLevelNumber="L2" uscom:indentationMeasureUnitCode="In" uscom:hangingIndentationNumber="0.27"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> Attorney usage - through patient consent be able to communicate to patients with<uscom:BoundaryDataReference com:idref="LNR-00086"/> potential recalls</uscom:P><uscom:P com:pNumber="269" com:id="p-269" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  Device Manufacturers - partner with Track<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">M</uscom:OCRConfidenceData>y technology to improve their recall</uscom:P><uscom:P com:pNumber="270" com:id="p-270" uscom:indentationLevelNumber="L2">strategy</uscom:P><uscom:P com:pNumber="271" com:id="p-271" uscom:indentationLevelNumber="L1"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData> Surgery Centers/Physicians - use technology to notify their patient population of medical</uscom:P><uscom:P com:pNumber="272" com:id="p-272" uscom:indentationLevelNumber="L2">device recalls/adverse events based on what devices they have FDA<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">/</uscom:OCRConfidenceData>CDRH - use</uscom:P><uscom:P com:pNumber="273" com:id="p-273" uscom:indentationLevelNumber="L2"><uscom:BoundaryDataReference com:idref="LNR-00087"/> technology to better enforce recall strategy and track what patients have been notified -</uscom:P><uscom:P com:pNumber="274" com:id="p-274" uscom:indentationLevelNumber="L1" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.27">leading to an increase public health- <uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  This software will increase patient safety and lead to an overall improved public health <uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  This software has real potential save a patient's life through real-time notifications This</uscom:P><uscom:P com:pNumber="275" com:id="p-275" uscom:indentationLevelNumber="L1" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.27">software allows a user to better manage their overall health through better information<uscom:BoundaryDataReference com:idref="LNR-00088"/> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">-</uscom:OCRConfidenceData>  This software educates a user of a device recall they have on a saved device</uscom:P><uscom:BoundaryDataReference com:idref="HDR-00013"/>
+<uscom:BoundaryDataBag><uscom:BoundaryData><uscom:LineNumber com:id="LNR-00085">5</uscom:LineNumber>
+<uscom:LineNumber com:id="LNR-00086">10</uscom:LineNumber>
+<uscom:LineNumber com:id="LNR-00087">15</uscom:LineNumber>
+<uscom:LineNumber com:id="LNR-00088">20</uscom:LineNumber>
+<uscom:LineNumber com:id="LNR-00089">25</uscom:LineNumber>
+<uscom:HeaderText com:id="HDR-00001">Page 1 of 17</uscom:HeaderText>
+<uscom:LineNumber com:id="LNR-00090">30</uscom:LineNumber>
+<uscom:HeaderText com:id="HDR-00002">Page 2 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00003">Page 3 of 17</uscom:HeaderText>
+<uscom:LineNumber com:id="LNR-00091">2</uscom:LineNumber>
+<uscom:HeaderText com:id="HDR-00004">Page 4 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00005">Page 5 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00006">Page 6 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00007">Page 7 of 17</uscom:HeaderText>
+<uscom:LineNumber com:id="LNR-00092">43</uscom:LineNumber>
+<uscom:LineNumber com:id="LNR-00093">0</uscom:LineNumber>
+<uscom:LineNumber com:id="LNR-00094">44</uscom:LineNumber>
+<uscom:HeaderText com:id="HDR-00008">Page 8 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00009">Page 9 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00010">Page 10 of 17</uscom:HeaderText>
+<uscom:LineNumber com:id="LNR-00095">100</uscom:LineNumber>
+<uscom:LineNumber com:id="LNR-00096">110</uscom:LineNumber>
+<uscom:LineNumber com:id="LNR-00097">140</uscom:LineNumber>
+<uscom:LineNumber com:id="LNR-00098">150</uscom:LineNumber>
+<uscom:LineNumber com:id="LNR-00099">170</uscom:LineNumber>
+<uscom:LineNumber com:id="LNR-00100">180</uscom:LineNumber>
+<uscom:LineNumber com:id="LNR-00101">12</uscom:LineNumber>
+<uscom:LineNumber com:id="LNR-00102">41</uscom:LineNumber>
+<uscom:LineNumber com:id="LNR-00103">45</uscom:LineNumber>
+<uscom:LineNumber com:id="LNR-00104">46</uscom:LineNumber>
+<uscom:LineNumber com:id="LNR-00105">48</uscom:LineNumber>
+<uscom:LineNumber com:id="LNR-00106">49</uscom:LineNumber>
+<uscom:HeaderText com:id="HDR-00011">Page 11 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00012">Page 12 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00013">Page 13 of 17</uscom:HeaderText>
+</uscom:BoundaryData></uscom:BoundaryDataBag></uspat:SpecificationDocument>

applicant/16744213.xml

@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="utf-8"?><uspat:SpecificationDocument xmlns:uscom="urn:us:gov:doc:uspto:common" xmlns:uspat="urn:us:gov:doc:uspto:patent" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:com="http://www.wipo.int/standards/XMLSchema/ST96/Common" xmlns:pat="http://www.wipo.int/standards/XMLSchema/ST96/Patent" uscom:vendorName="VASTEC" uscom:createDateTime="2020-01-21T11:53:11Z" com:st96Version="V2_1" com:ipoVersion="US_V7_1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent Patent/V7_1/Schema/USPatent/Document/SpecificationDocument_V7_1.xsd" com:documentFileName="16744213.01-16-2020.K5NSYXM8LXEAPX3.SPEC.XML" com:id="K5NSYXM8LXEAPX3">
+<uspat:DocumentMetadata com:id="ID0000001"><uscom:DocumentCode>SPEC</uscom:DocumentCode><uscom:ApplicationNumberText uscom:electronicText="16744213">16744213</uscom:ApplicationNumberText><com:PageTotalQuantity>14</com:PageTotalQuantity><uscom:ParagraphTotalQuantity>114</uscom:ParagraphTotalQuantity><uscom:OfficialDate>2020-01-16</uscom:OfficialDate></uspat:DocumentMetadata><?PageStart number='1'?><uscom:BoundaryDataReference com:idref="HDR-00001"/>
+<uscom:BoundaryDataReference com:idref="HDR-00002"/>
+<uscom:Heading com:id="h-1">SCANNING UNIT FOR AN ANGLE-MEASURING DEVICE</uscom:Heading><uscom:Heading com:id="h-2">CROSS-REFERENCE TO PRIOR APPLICATIONS</uscom:Heading><uscom:P com:pNumber="3" com:id="p-3">[0001<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Priority is claimed to European Patent Application No. <uscom:PartName com:idrefs="PN-00001">EP </uscom:PartName><uscom:PartNumber com:id="PN-00001">19</uscom:PartNumber> 152 247.3, filed on January 17, 2019, the entire disclosure of which is hereby incorporated by reference herein.</uscom:P><uscom:Heading com:id="h-3">FIELD</uscom:Heading><uscom:P com:pNumber="4" com:id="p-4">[0002<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Angle-measuring devices are used, for example, in rotary encoders to determine the angular position of two relatively rotatable machines parts.</uscom:P><uscom:Heading com:id="h-4">BACKGROUND</uscom:Heading><uscom:P com:pNumber="5" com:id="p-5">[0003<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> In scanning units of inductive angle-measuring devices, it is common to apply excitation coils and receiver coils in the form of conductive traces to a common circuit board that is fixedly attached to, for example, a stator of a rotary encoder. Located opposite this circuit board is a further component which has an angular scale in the form of electrically conductive regions formed thereon at periodic intervals as a graduation structure and which is non-rotatably connected to the rotor of the rotary encoder. When an electric excitation field is applied to the excitation coils, then angular-position-dependent output signals are generated in the receiving coils during relative rotation between rotor and stator. These output signals are then further processed in evaluation electronics.</uscom:P><uscom:P com:pNumber="6" com:id="p-6">[0004<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> A fundamental distinction is made between angle-measuring devices with integral bearings and angle-measuring devices without integral bearings, hereinafter referred to as bearingless angle-measuring devices. Angle-measuring devices with integral bearing typically have relatively small rolling-element bearings, so that the relatively rotatable component groups are disposed in a defined axial and radial position relative to each other within the respective angle-measuring device. In contrast, in the case of bearingless angle- measuring devices, care must be taken to ensure that the relatively rotatable component<uscom:BoundaryDataReference com:idref="HDR-00003"/></uscom:P><?PageStart number='2'?><uscom:BoundaryDataReference com:idref="HDR-00004"/>
+<uscom:BoundaryDataReference com:idref="HDR-00005"/>
+<uscom:P com:pNumber="9" com:id="p-9">groups are fixed in the correct position, in particular at the correct axial distance relative to one another, while being mounted on a machine.</uscom:P><uscom:P com:pNumber="10" com:id="p-10">[0005<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> The Applicant's German Patent Application DE 10 2008 046 741 Al describes an angle-measuring device having a scanning unit with a connector. Furthermore, EP 0 845 659 A2 describes a scanning unit that is attached to a drive mechanism.</uscom:P><uscom:Heading com:id="h-5">SUMMARY</uscom:Heading><uscom:P com:pNumber="11" com:id="p-11">[0006<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> In an embodiment, the present invention provides a scanning unit for determining a relative angular position of an angular scale that is rotatable about an axis relative to the scanning unit. The scanning unit includes a circuit board having a first surface and a second surface, as well as evaluation electronics. A detector assembly is disposed in a manner that enables scanning of the angular scale located opposite the first surface of the circuit board. A contact carrier encloses electrical contacts for creating a plug-and-socket connection. The contact carrier has an outer wall and is mounted on the second surface of the circuit board such that the electrical contacts extend in a direction having an axial component. A housing body is provided with an opening having an inner wall, the contact carrier extending into the opening. A first elastic element is disposed under radial preload between the inner wall of the opening and the outer wall of the contact carrier such that the contact carrier is centered with respect to the inner wall of the opening. The circuit board is torsionally rigidly attached to the housing body such that the circuit board is radially spaced from the housing body by a first gap.</uscom:P><uscom:Heading com:id="h-6">BRIEF DESCRIPTION OF THE DRAWINGS</uscom:Heading><uscom:P com:pNumber="12" com:id="p-12">[0007<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Embodiments of the present invention will be described in even greater detail below based on the exemplary figures. The present invention is not limited to the exemplary embodiments. All features described and/or illustrated herein can be used alone or combined in different combinations in embodiments of the present invention. The features and advantages of various embodiments of the present invention will become apparent by reading the following detailed description with reference to the attached drawings which illustrate the following:<uscom:BoundaryDataReference com:idref="HDR-00006"/></uscom:P><?PageStart number='3'?><uscom:BoundaryDataReference com:idref="HDR-00007"/>
+<uscom:BoundaryDataReference com:idref="HDR-00008"/>
+<uscom:P com:pNumber="15" com:id="p-15">[0008<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> FIG. 1 is a side view showing a circuit board with a contact carrier as part of the scanning unit;</uscom:P><uscom:P com:pNumber="16" com:id="p-16">[0009<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> FIG. 2 is a perspective view showing the circuit board with the contact carrier;</uscom:P><uscom:P com:pNumber="17" com:id="p-17">[0010<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> FIG. 3 is a cross-sectional view showing a housing body;</uscom:P><uscom:P com:pNumber="18" com:id="p-18">[0011<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> FIG. 4 is a cross-sectional view showing a housing body with the circuit board and the contact carrier;</uscom:P><uscom:P com:pNumber="19" com:id="p-19">[0012<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> FIG. 5 is a perspective view showing the scanning unit;</uscom:P><uscom:P com:pNumber="20" com:id="p-20">[0013<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> FIG. 6 is a cross-sectional view showing an angle-measuring device with the scanning unit in the mounted condition; and</uscom:P><uscom:P com:pNumber="21" com:id="p-21">[0014<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> FIG. 7 is a perspective view showing a scanning unit according to a second exemplary embodiment.</uscom:P><uscom:Heading com:id="h-7">DETAILED DESCRIPTION</uscom:Heading><uscom:P com:pNumber="22" com:id="p-22">[0015<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> In an embodiment, the present invention provides a scanning unit for an, in particular bearingless, inductive angle-measuring device which scanning unit can be precisely manufactured with relatively little effort.</uscom:P><uscom:P com:pNumber="23" com:id="p-23">[0016<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Accordingly, an embodiment of the present invention encompasses a scanning unit for determining a relative angular position of an angular scale that is rotatable about an axis relative to the scanning unit. The scanning unit includes a circuit board having a first surface and a second surface. The scanning unit further includes at least one detector assembly which is disposed in manner that enables scanning of the angular scale located axially opposite the first surface of the circuit board. The scanning unit also includes evaluation electronics, which is typically composed of a plurality of electronic components and often has an integrated circuit (ASIC component). In addition, the scanning unit has a contact car<uscom:OCRConfidenceData uscom:ocrConfidenceCode="6688">rier</uscom:OCRConfidenceData> which encloses electrical contacts for creating a plug-and-socket connection and which is<uscom:BoundaryDataReference com:idref="HDR-00009"/></uscom:P><?PageStart number='4'?><uscom:BoundaryDataReference com:idref="HDR-00010"/>
+<uscom:BoundaryDataReference com:idref="HDR-00011"/>
+<uscom:P com:pNumber="26" com:id="p-26">mounted on the second surface of the circuit board, so that the contacts extend in a direction having an axial component. In particular, the contact carrier has a cylindrical outer wall whose axis of symmetry is the axis around which the angular scale is rotatable. Finally, the scanning unit includes a housing body with an opening having an inner wall. The contact carrier extends into the opening, a first elastic element being disposed under radial preload between the inner wall of the opening and the outer wall of the contact carrier, so that the contact carrier is centered with respect to the inner wall of the opening. The circuit board is torsionally rigidly attached to the housing body such that it is radially spaced therefrom by a first gap.</uscom:P><uscom:P com:pNumber="27" com:id="p-27">[0017<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> The detector assembly may be mounted, for example, on the first surface of the circuit board. If the detector assembly is embodied as one or a plurality of receiver windings or as magnetoresistive conductive traces, the detector assembly may also have disposed thereon a thin layer which in particular has insulating properties and provides mechanical protection. The detector assembly is capable of generating angle-dependent output signals, which can be further processed in the evaluation electronics. Angle-dependent output signals are in particular signals which contain information about the relative angular position between the angular scale and the scanning unit.</uscom:P><uscom:P com:pNumber="28" com:id="p-28">[0018<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> In an embodiment of the present invention, the first gap is filled with an adhesive.</uscom:P><uscom:P com:pNumber="29" com:id="p-29">[0019<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Advantageously, the first elastic element takes the form of an <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">O</uscom:OCRConfidenceData>-ring which is disposed centrally with respect to the axis and which, in particular, is deformed due to the radial preload.</uscom:P><uscom:P com:pNumber="30" com:id="p-30">[0020<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Advantageously, the circuit board is torsionally rigidly attached to the housing body such that it is axially spaced therefrom by a second gap, which second gap may also be filled with an adhesive.</uscom:P><uscom:P com:pNumber="31" com:id="p-31">[002<uscom:OCRConfidenceData uscom:ocrConfidenceCode="86">1]</uscom:OCRConfidenceData> In an embodiment of the present invention, the outer wall of the contact carrier is geometrically shaped as a cylindrical shell.</uscom:P><uscom:BoundaryDataReference com:idref="HDR-00012"/>
+<?PageStart number='5'?><uscom:BoundaryDataReference com:idref="HDR-00013"/>
+<uscom:BoundaryDataReference com:idref="HDR-00014"/>
+<uscom:P com:pNumber="35" com:id="p-35">[0022<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Furthermore, the opening may have a rotationally symmetric inner surface, the above- mentioned axis being the axis of symmetry of the inner surface. For example, the inner surface may be the inner contour of a hollow cylinder.</uscom:P><uscom:P com:pNumber="36" com:id="p-36">[0023<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Advantageously, the housing body has a bottom. Furthermore, the circuit board is mounted to the housing body in such a way that the evaluation electronics; i.e., electronic components of the evaluation electronics are located between the bottom and the circuit board. In this case, the bottom may have a hole in which is mounted a sleeve to receive the contact carrier. A particularly economical design can be achieved by using a standardized housing coupling as the sleeve. In a possible alternative design, no additional component is used, so that the contact carrier extends directly into a (threaded) hole in the bottom.</uscom:P><uscom:P com:pNumber="37" com:id="p-37">[0024<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Advantageously, a second elastic element, which may in particular take the form of an <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">O</uscom:OCRConfidenceData>-ring, is provided between the sleeve and hole.</uscom:P><uscom:P com:pNumber="38" com:id="p-38">[0025<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Advantageously, the housing body has slots extending circumferentially about the axis and lands extending axially and circumferentially between two slots. In particular, the slots and lands are configured such that the housing body is axially flexible but torsionally and radially rigid. Moreover, the bottom is disposed axially between the slots and the circuit board, so that in particular the evaluation electronics is accommodated in a protected position between the slots and the circuit board.</uscom:P><uscom:P com:pNumber="39" com:id="p-39">[0026<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> In the following, the term "lands" is used to refer to the land- or strip-shaped regions of the housing body that run or extend with an axial directional component. Each land is located between two slots, so that, in particular in the circumferential direction, a slot is disposed on each side of a land.</uscom:P><uscom:P com:pNumber="40" com:id="p-40">[0027<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> The housing body is torsionally rigid, which means that it does not deform, or deforms only to an extremely small extent, in response to the introduction of tangentially directed forces. In addition, the housing body may be rigid in a radial direction.</uscom:P><uscom:P com:pNumber="41" com:id="p-41">[0028<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Advantageously, the scanning unit has lands with a slot disposed axially therebetween, so that these lands are axially offset from one another. In particular, the<uscom:BoundaryDataReference com:idref="HDR-00015"/></uscom:P><?PageStart number='6'?><uscom:BoundaryDataReference com:idref="HDR-00016"/>
+<uscom:BoundaryDataReference com:idref="HDR-00017"/>
+<uscom:P com:pNumber="44" com:id="p-44">respective lands may be disposed in alignment with one another; i.e., such that they are not offset from one another in the circumferential direction.</uscom:P><uscom:P com:pNumber="45" com:id="p-45">[0029<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> In an embodiment of the present invention, the scanning unit has a first pair of lands, the lands of this first pair being offset from one another in the circumferential direction. For example, the lands may be offset by 180<uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">0</uscom:OCRConfidenceData> or 120<uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">0</uscom:OCRConfidenceData> in the circumferential direction. With regard to the definition of the offset angle, which is in particular a central angle about axis A, the center of a land (with respect to the circumferential direction) may in each case be taken as a reference line.</uscom:P><uscom:P com:pNumber="46" com:id="p-46">[0030<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Advantageously, the scanning unit has a first pair of lands, these lands being disposed in a geometric plane whose normal vector is oriented parallel to the axis.</uscom:P><uscom:P com:pNumber="47" com:id="p-47">[0031<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Furthermore, the scanning unit may have a second pair of lands. In this case, the lands of the first pair may be axially offset relative to the lands of the second pair. In addition, the lands of the first pair may be offset in the circumferential direction relative to the lands of the second pair. Advantageously, the lands of the first pair are each offset by the same angle relative to respective lands of the second pair in the circumferential direction. In particular, the respective lands may be offset from one another by 60<uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">0</uscom:OCRConfidenceData> or by 72<uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">0</uscom:OCRConfidenceData> or by 90<uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">0</uscom:OCRConfidenceData> or by 120<uscom:OCRConfidenceData uscom:ocrConfidenceCode="28">0.</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="48" com:id="p-48">[0032<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> In an embodiment of the present invention, the scanning unit has a first pair of slots. Advantageously, the scanning unit then has a second pair of slots, the slots of the first pair being axially offset relative to the slots of the second pair. In particular, the slots of the first pair may be offset in the circumferential direction relative to the slots of the second pair.</uscom:P><uscom:P com:pNumber="49" com:id="p-49">[0033<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Advantageously, at least one of the slots extends over a circumferential angle of atleast 70<uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">0</uscom:OCRConfidenceData>, in particular over a circumferential angle of at least 100<uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">0</uscom:OCRConfidenceData> or at least 140<uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">0</uscom:OCRConfidenceData> <com:Image com:id="p-00000" com:imageWrappingStyleCategory="Inline" com:orientationCategory="Portrait" com:imageContentCategory="Chemistry"><com:ImageFormatCategory>SVG</com:ImageFormatCategory><com:FileName>16744213.01-16-2020.K5NSYXM8LXEAPX3.SPEC.6.24.1921.2443.1946.2476.svg</com:FileName><com:HeightMeasure com:measureUnitCode="In">0.11</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="In">0.083</com:WidthMeasure><com:Alt>Chemistry</com:Alt><com:ColourModeCategory>Black and white</com:ColourModeCategory></com:Image> It is alsoadvantageous if all slots extend over a circumferential angle of the same magnitude or if at least the slots of a pair extend over a circumferential angle of the same magnitude.</uscom:P><uscom:P com:pNumber="50" com:id="p-50">[0034<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> The term "pair" means a group of two elements; i.e., here two slots or two lands. This wording does not rule out the possibility that the respective regions of the housing body may have one or more further such elements (slot, land) in addition to the two elements.</uscom:P><uscom:BoundaryDataReference com:idref="HDR-00018"/>
+<?PageStart number='7'?><uscom:BoundaryDataReference com:idref="HDR-00019"/>
+<uscom:BoundaryDataReference com:idref="HDR-00020"/>
+<uscom:P com:pNumber="54" com:id="p-54">[0035<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Advantageously, the housing body is elastically deformable in the direction of the axis over a range of at least 0.5 mm, in particular at least 1.0 mm, and preferably at least 1.5 mm.</uscom:P><uscom:P com:pNumber="55" com:id="p-55">[0036<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Advantageously, the housing body has a stop surface having a normal which has a directional component parallel to the axis. The object of this is in particular to allow the housing body to rest axially against the stop surface.</uscom:P><uscom:P com:pNumber="56" com:id="p-56">[0037<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Advantageously, the housing body is designed such that the bottom and the lands are monolithically formed from a single piece; i.e., machined out of a single piece. For example, the entire housing body may be monolithically formed or include at least one monolithic sub- body including the bottom and the lands as integral parts thereof.</uscom:P><uscom:P com:pNumber="57" com:id="p-57">[0038<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> The angle-measuring device may be designed as an inductive angle-measuring device or may be based on an optical, magnetic or capacitive principle. Furthermore, the angle- measuring device, which has an angular scale, a scanning unit and evaluation electronics, is preferably designed as a bearingless angle-measuring device.</uscom:P><uscom:P com:pNumber="58" com:id="p-58">[0039<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Advantageous embodiments of the present invention will be apparent from the dependent claims.</uscom:P><uscom:P com:pNumber="59" com:id="p-59">[0040<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Other details and advantages of the scanning unit according to the present invention will be apparent from the following description of two exemplary embodiments, taken in conjunction with the accompanying drawings.</uscom:P><uscom:P com:pNumber="60" com:id="p-60">[0041<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> A portion of a scanning unit intended for use in an angle-measuring device is shown in a side view in FIG. 1 and in a perspective view in FIG. 2. Accordingly, the scanning unit includes, among other things, a disc-shaped or <uscom:PartName com:idrefs="PN-00002">circular circuit board </uscom:PartName><uscom:PartNumber com:id="PN-00002">1</uscom:PartNumber> on the basis of a rigid, fiberglass-reinforced epoxy resin. <uscom:PartName com:idrefs="PN-00003">Circuit board </uscom:PartName><uscom:PartNumber com:id="PN-00003">1</uscom:PartNumber> naturally has a first surface 1.1 and a second surface 1.2 opposite the first surface 1.<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">1.</uscom:OCRConfidenceData> In the exemplary embodiment presented here, the scanning unit is based on an inductive measurement principle. Accordingly, a <uscom:PartName com:idrefs="PN-00004">detector assembly </uscom:PartName><uscom:PartNumber com:id="PN-00004">2</uscom:PartNumber> disposed on first surface 1.1 is embodied as a plurality of receiver windings. Also disposed on first surface 1.1 are a plurality of <uscom:PartName com:idrefs="PN-00005">excitation traces </uscom:PartName><uscom:PartNumber com:id="PN-00005">10.</uscom:PartNumber></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00021"/>
+<?PageStart number='8'?><uscom:BoundaryDataReference com:idref="HDR-00022"/>
+<uscom:BoundaryDataReference com:idref="HDR-00023"/>
+<uscom:P com:pNumber="64" com:id="p-64">[0042<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Second surface 1.2 has mounted thereon, among other things, electronic components 3.1 of <uscom:PartName com:idrefs="PN-00006">evaluation electronics </uscom:PartName><uscom:PartNumber com:id="PN-00006">3.</uscom:PartNumber> A <uscom:PartName com:idrefs="PN-00007">contact carrier </uscom:PartName><uscom:PartNumber com:id="PN-00007">4</uscom:PartNumber> is also mounted on second surface 1.2 of <uscom:PartName com:idrefs="PN-00008">circuit board </uscom:PartName><uscom:PartNumber com:id="PN-00008">1,</uscom:PartNumber> for example with the aid of surface-mount technology (SMT). <uscom:PartName com:idrefs="PN-00009">Contact carrier </uscom:PartName><uscom:PartNumber com:id="PN-00009">4</uscom:PartNumber> encloses electrical contacts 4.1 (FIG. 2) suitable for creating a plug-and-socket connection, the contacts 4.1 extending in a direction parallel to an axis A. <uscom:PartName com:idrefs="PN-00010">Contact carrier </uscom:PartName><uscom:PartNumber com:id="PN-00010">4</uscom:PartNumber> has an outer <uscom:OCRConfidenceData uscom:ocrConfidenceCode="8866">wall</uscom:OCRConfidenceData> 4.2 or outer surface which geometrically corresponds substantially to a cylindrical curved surface. Outer wa<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">ll</uscom:OCRConfidenceData> 4.2 has a circumferential groove in which is disposed a first <uscom:PartName com:idrefs="PN-00011">elastic element </uscom:PartName><uscom:PartNumber com:id="PN-00011">6,</uscom:PartNumber> here an <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">O</uscom:OCRConfidenceData>-ring.</uscom:P><uscom:P com:pNumber="65" com:id="p-65">[0043<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> The scanning unit further has a <uscom:PartName com:idrefs="PN-00012">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00012">5,</uscom:PartNumber> as shown, for example, in FIG. 3. <uscom:PartName com:idrefs="PN-00013">Housing body </uscom:PartName><uscom:PartNumber com:id="PN-00013">5</uscom:PartNumber> includes a bottom 5.1 disposed within and integrally formed with a rigid annular portion of <uscom:PartName com:idrefs="PN-00014">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00014">5.</uscom:PartNumber> The bottom has a hole centrally formed therein with respect to axis A, the hole having a sleeve 5.11 threadedly received therein. A second <uscom:PartName com:idrefs="PN-00015">elastic element </uscom:PartName><uscom:PartNumber com:id="PN-00015">7</uscom:PartNumber> is disposed axially between a flange of sleeve 5.11 and bottom 5.1. Here, second <uscom:PartName com:idrefs="PN-00016">elastic element </uscom:PartName><uscom:PartNumber com:id="PN-00016">7</uscom:PartNumber> is also embodied as an <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">O</uscom:OCRConfidenceData>-ring. Sleeve 5.11 has a through-opening H and, accordingly, an inner wa<uscom:OCRConfidenceData uscom:ocrConfidenceCode="88">ll</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="6666">5.11</uscom:OCRConfidenceData>1. Inner wa<uscom:OCRConfidenceData uscom:ocrConfidenceCode="88">ll</uscom:OCRConfidenceData> <uscom:OCRConfidenceData uscom:ocrConfidenceCode="6666">5.11</uscom:OCRConfidenceData>1 has a concave hollow-cylindrical geometry whose axis of symmetry is axis A. <uscom:PartName com:idrefs="PN-00017">Housing body </uscom:PartName><uscom:PartNumber com:id="PN-00017">5</uscom:PartNumber> has a substantially hollow-cylindrical shape axially on both sides of bottom 5.1. <uscom:PartName com:idrefs="PN-00018">Housing body </uscom:PartName><uscom:PartNumber com:id="PN-00018">5</uscom:PartNumber> further has a machined stop surface 5.4 at an annular end face thereof.</uscom:P><uscom:P com:pNumber="66" com:id="p-66">[0044<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> In the exemplary embodiment presented here, to allow for axial deformation of <uscom:PartName com:idrefs="PN-00019">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00019">5,</uscom:PartNumber> a plurality of slots 5.21, 5.22, 5.23, 5.24 are machined into the <uscom:PartName com:idrefs="PN-00020">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00020">5,</uscom:PartNumber> each over a respective portion of its circumference. These extend radially completely through the wall of <uscom:PartName com:idrefs="PN-00021">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00021">5,</uscom:PartNumber> as can be seen, for example, in FIGS. 3 and 4 in the regions between the hatched cross-sectional areas. Axially extending lands 5.31, 5.32, 5.33,</uscom:P><uscom:P com:pNumber="67" com:id="p-67">5.34 are located between these slots 5.21, 5.22, 5.23, 5.24 in the circumferential direction. Slots 5.21, 5.22, 5.23, 5.24 may be created, in particular, by a sawing process, leaving the axially extending lands 5.31, 5.32, 5.33, 5.34. <uscom:PartName com:idrefs="PN-00022">Housing body </uscom:PartName><uscom:PartNumber com:id="PN-00022"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData></uscom:PartNumber> is then configured such that the non-removed regions have a meandering shape. Accordingly, lands 5.31, <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData>.32, <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData>.33, <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData>.34 are those regions of the remaining material which extend in a direction having an axial component.</uscom:P><uscom:BoundaryDataReference com:idref="HDR-00024"/>
+<?PageStart number='9'?><uscom:BoundaryDataReference com:idref="HDR-00025"/>
+<uscom:BoundaryDataReference com:idref="HDR-00026"/>
+<uscom:P com:pNumber="71" com:id="p-71">[0045<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Slots 5.21, 5.22, 5.23, 5.24 can be grouped into pairs. In the figures, slots whose reference numerals have the same last digit are part of a pair (thus, there are always two slots with the same reference numeral). In the exemplary embodiment presented here, <uscom:PartName com:idrefs="PN-00023">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00023"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData></uscom:PartNumber> has four pairs of slots 5.21, 5.22, 5.23 and 5.24, respectively.</uscom:P><uscom:P com:pNumber="72" com:id="p-72">[0046<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> For example, a first pair of slots has the slots 5.21, which are arranged symmetrically about a point on axis A. The same holds for slots 5.22, which can be considered as being part of a second pair of slots, and for the third and fourth pairs.</uscom:P><uscom:P com:pNumber="73" com:id="p-73">[0047<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> As can be seen from FIG. 5, the slots 5.21 of the first pair of slots are here axially offset from the slots 5.22 of the second pair of slots and circumferentially offset therefrom by about 90<uscom:OCRConfidenceData uscom:ocrConfidenceCode="28">°.</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="74" com:id="p-74">[0048<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Slots 5.21, 5.22, 5.23, 5.24 extend over a circumferential angle <uscom:OCRConfidenceData uscom:ocrConfidenceCode="4">p</uscom:OCRConfidenceData> of about 170<uscom:OCRConfidenceData uscom:ocrConfidenceCode="28">°.</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="75" com:id="p-75">[0049<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> The slots 5.21 of the first pair of slots are located in a first geometric plane and the slots 5.22 of the second pair of slots are located in a second geometric plane that is axially offset from the first geometric plane. Both the first geometric plane and the second geometric plane are arranged such that the respective normal vector of the respective plane is oriented parallel to axis A. In the exemplary embodiment presented here, the same considerations apply also to the third and fourth pairs of slots 5.23; 5.24.</uscom:P><uscom:P com:pNumber="76" com:id="p-76">[0050<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Similarly, lands 5.31, 5.32, 5.33, 5.34 can be grouped into four pairs. Here, <uscom:PartName com:idrefs="PN-00024">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00024"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData></uscom:PartNumber> has a total of eight lands 5.31, 5.32, 5.33, 5.34, of which six are visible in FIG. 5. A first pair of lands includes the lands 5.31, which are arranged symmetrically about a point on axis A. The lands 5.31 of the first pair are offset from one another by an angle a = 180<uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">0</uscom:OCRConfidenceData> in the circumferential direction. The same holds for lands 5.32, which can be considered as being part of a second pair of lands, and for the lands 5.33, 5.34 of the third and fourth pairs. The lands <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData>.31 of the first pair of lands are axially offset from the lands <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData>.32 of the second pair of lands and circumferentially offset therefrom by a circumferential angle y, here 90<uscom:OCRConfidenceData uscom:ocrConfidenceCode="2">°</uscom:OCRConfidenceData>. In the exemplary embodiment presented here, four pairs of lands <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData>.31, <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData>.32, <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData>.33, <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData>.34 are axially offset from one another. Here, the lands 5.31, <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData>.33 of the first and third pairs are offset from the lands <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData>.32, <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData>.34 of the second and fourth pairs by the same circumferential angle y.</uscom:P><uscom:BoundaryDataReference com:idref="HDR-00027"/>
+<?PageStart number='10'?><uscom:BoundaryDataReference com:idref="HDR-00028"/>
+<uscom:BoundaryDataReference com:idref="HDR-00029"/>
+<uscom:P com:pNumber="80" com:id="p-80">[0051<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Furthermore, <uscom:PartName com:idrefs="PN-00025">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00025">5</uscom:PartNumber> is configured to have a first pair of lands, whose lands</uscom:P><uscom:P com:pNumber="81" com:id="p-81">5.31 are disposed in an imaginary plane whose normal vector is oriented parallel to axis A. In other words, axis A orthogonally intersects the aforesaid plane. The same considerations apply also to the lands 5.32 of the second pair of lands, the plane in which these lands 5.32 are located being axially offset from the respective plane of the first pair of lands.</uscom:P><uscom:P com:pNumber="82" com:id="p-82">[0052<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> The scanning unit has lands 5.31, 5.32, 5.33, 5.34 with a slot 5.21, 5.22, 5.23, 5.24 disposed axially therebetween, so that these lands 5.31, 5.32, 5.33, 5.34 are axially offset from one another. In particular, slot 5.22 is disposed between the aligned and axially offset lands 5.31, 5.33. Similarly, slot 5.23 is disposed between the aligned and axially offset lands</uscom:P><uscom:P com:pNumber="83" com:id="p-83">5.32, 5.34.</uscom:P><uscom:P com:pNumber="84" com:id="p-84">[0053<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> In the exemplary embodiment presented here, <uscom:PartName com:idrefs="PN-00026">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00026"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData></uscom:PartNumber> is formed as a single piece or component, except for sleeve 5.1<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">1.</uscom:OCRConfidenceData> In <uscom:PartName com:idrefs="PN-00027">particular, housing body </uscom:PartName><uscom:PartNumber com:id="PN-00027"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData></uscom:PartNumber> is made from an aluminum material.</uscom:P><uscom:P com:pNumber="85" com:id="p-85">[0054<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> During assembly of the <uscom:PartName com:idrefs="PN-00028">scanning unit, circuit board </uscom:PartName><uscom:PartNumber com:id="PN-00028">1,</uscom:PartNumber> together with <uscom:PartName com:idrefs="PN-00029">contact carrier </uscom:PartName><uscom:PartNumber com:id="PN-00029">4</uscom:PartNumber> and first <uscom:PartName com:idrefs="PN-00030">elastic element </uscom:PartName><uscom:PartNumber com:id="PN-00030">6,</uscom:PartNumber> is assembled with <uscom:PartName com:idrefs="PN-00031">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00031">5,</uscom:PartNumber> forming an assembly such as is shown, for example, in Fig. 4. <uscom:PartName com:idrefs="PN-00032">Elastic element </uscom:PartName><uscom:PartNumber com:id="PN-00032">6</uscom:PartNumber> is disposed between inner wa<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">ll</uscom:OCRConfidenceData> 5.111 of opening H and outer wa<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">ll</uscom:OCRConfidenceData> 4.2 of <uscom:PartName com:idrefs="PN-00033">contact carrier </uscom:PartName><uscom:PartNumber com:id="PN-00033">4</uscom:PartNumber> under radial preload; i.e., such that it is radially compressed. This preload causes <uscom:PartName com:idrefs="PN-00034">contact carrier </uscom:PartName><uscom:PartNumber com:id="PN-00034">4</uscom:PartNumber> to be centered with respect to inner <uscom:OCRConfidenceData uscom:ocrConfidenceCode="8866">wall</uscom:OCRConfidenceData> 5.111 of opening H without further action. Due to the design of <uscom:PartName com:idrefs="PN-00035">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00035"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData></uscom:PartNumber> and the dimensioning of <uscom:PartName com:idrefs="PN-00036">circuit board </uscom:PartName><uscom:PartNumber com:id="PN-00036">1,</uscom:PartNumber> <uscom:PartName com:idrefs="PN-00037">circuit board </uscom:PartName><uscom:PartNumber com:id="PN-00037">1</uscom:PartNumber> is radially spaced from <uscom:PartName com:idrefs="PN-00038">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00038"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData></uscom:PartNumber> by a first gap Gr (FIG. 4).</uscom:P><uscom:P com:pNumber="86" com:id="p-86">[0055<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> To ensure accurate operation of the entire angle-measuring device, it is not only important that the <uscom:PartName com:idrefs="PN-00039">circuit board </uscom:PartName><uscom:PartNumber com:id="PN-00039">1</uscom:PartNumber> with <uscom:PartName com:idrefs="PN-00040">detector assembly </uscom:PartName><uscom:PartNumber com:id="PN-00040">2</uscom:PartNumber> be centered with respect to axis A, but it is also important in this connection to establish a defined axial position of circuit board</uscom:P><uscom:P com:pNumber="87" com:id="p-87"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">1.</uscom:OCRConfidenceData> In the exemplary embodiment presented here, first surface 1.1 of <uscom:PartName com:idrefs="PN-00041">circuit board </uscom:PartName><uscom:PartNumber com:id="PN-00041">1</uscom:PartNumber> is mounted flush with stop surface <uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData>.4 of <uscom:PartName com:idrefs="PN-00042">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00042">5.</uscom:PartNumber></uscom:P><uscom:BoundaryDataReference com:idref="HDR-00030"/>
+<?PageStart number='11'?><uscom:BoundaryDataReference com:idref="HDR-00031"/>
+<uscom:BoundaryDataReference com:idref="HDR-00032"/>
+<uscom:P com:pNumber="91" com:id="p-91">[0056<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> To this end, initially, <uscom:PartName com:idrefs="PN-00043">circuit board </uscom:PartName><uscom:PartNumber com:id="PN-00043">1</uscom:PartNumber> is pushed into <uscom:PartName com:idrefs="PN-00044">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00044">5</uscom:PartNumber> as far as possible; i.e., as far as it will go. Then, an <uscom:PartName com:idrefs="PN-00045">adhesive </uscom:PartName><uscom:PartNumber com:id="PN-00045">8</uscom:PartNumber> is introduced into circumferential gap Gr. Subsequently, stop surface 5.4 is pressed onto a plane surface. Then, <uscom:PartName com:idrefs="PN-00046">contact carrier </uscom:PartName><uscom:PartNumber com:id="PN-00046">4</uscom:PartNumber> is moved relative to opening H until <uscom:PartName com:idrefs="PN-00047">circuit board </uscom:PartName><uscom:PartNumber com:id="PN-00047">1</uscom:PartNumber> contacts the plane surface and the above- mentioned flush arrangement is obtained. In this connection, it may be advantageous to press <uscom:PartName com:idrefs="PN-00048">contact carrier </uscom:PartName><uscom:PartNumber com:id="PN-00048">4</uscom:PartNumber> toward <uscom:PartName com:idrefs="PN-00049">circuit board </uscom:PartName><uscom:PartNumber com:id="PN-00049">1</uscom:PartNumber> using an auxiliary mounting tool<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">.</uscom:OCRConfidenceData> In this position, second surface 1.2 of <uscom:PartName com:idrefs="PN-00050">circuit board </uscom:PartName><uscom:PartNumber com:id="PN-00050">1</uscom:PartNumber> does not contact <uscom:PartName com:idrefs="PN-00051">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00051">5,</uscom:PartNumber> but rather an axial second gap Ga is present, as a result of which the not yet cured adhesive 8 creeps into this second gap Ga due to capillary effects. Due to the axial preloading of <uscom:PartName com:idrefs="PN-00052">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00052">5</uscom:PartNumber> and the axial compressive force on <uscom:PartName com:idrefs="PN-00053">contact carrier </uscom:PartName><uscom:PartNumber com:id="PN-00053">4,</uscom:PartNumber> it is ensured that <uscom:PartName com:idrefs="PN-00054">circuit board </uscom:PartName><uscom:PartNumber com:id="PN-00054">1</uscom:PartNumber> and stop surface</uscom:P><uscom:P com:pNumber="92" com:id="p-92">5.4 remain in an exactly flush position. Thus, in this phase, first gap Gr and second gap Ga are filled with an <uscom:PartName com:idrefs="PN-00055">adhesive </uscom:PartName><uscom:PartNumber com:id="PN-00055">8</uscom:PartNumber> (FIG. 6), the <uscom:PartName com:idrefs="PN-00056">adhesive </uscom:PartName><uscom:PartNumber com:id="PN-00056">8</uscom:PartNumber> subsequently being cured, for example, in a heating furnace. After curing of <uscom:PartName com:idrefs="PN-00057">adhesive </uscom:PartName><uscom:PartNumber com:id="PN-00057">8,</uscom:PartNumber> <uscom:PartName com:idrefs="PN-00058">circuit board </uscom:PartName><uscom:PartNumber com:id="PN-00058">1</uscom:PartNumber> is rigidly and, in particular, torsionally rigidly attached to <uscom:PartName com:idrefs="PN-00059">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00059">5,</uscom:PartNumber> so that the axial preloading of <uscom:PartName com:idrefs="PN-00060">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00060">5</uscom:PartNumber> now can be removed. Thus, electronic components 3.1 are effectively shielded from external influences, such as from ingress of lubricants or moisture, as well as from mechanical influences.</uscom:P><uscom:P com:pNumber="93" com:id="p-93">[0057<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> The scanning unit of FIGS. 3 through 5 and an <uscom:PartName com:idrefs="PN-00061">angular scale </uscom:PartName><uscom:PartNumber com:id="PN-00061">9</uscom:PartNumber> together form an angle- measuring device as shown in FIG. 6 , which is here embodied as an inductive angle- measuring device, and thus is based on an inductive measurement principle. In the exemplary embodiment presented here, <uscom:PartName com:idrefs="PN-00062">angular scale </uscom:PartName><uscom:PartNumber com:id="PN-00062">9</uscom:PartNumber> is configured as an annular circuit board on which conductive and non-conductive regions; i.e., regions of different electrical conductivity, are provided in a periodic sequence and at identical graduation steps. <uscom:PartName com:idrefs="PN-00063">Angular scale </uscom:PartName><uscom:PartNumber com:id="PN-00063">9</uscom:PartNumber> is non-rotatably connected to a <uscom:PartName com:idrefs="PN-00064">hub </uscom:PartName><uscom:PartNumber com:id="PN-00064">15.</uscom:PartNumber></uscom:P><uscom:P com:pNumber="94" com:id="p-94">[0058<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> FIG. 6 shows an angle-measuring device which is equipped with the inductive scanning unit and mounted to a motor. The motor is provided in its stator portion with a brake including an <uscom:PartName com:idrefs="PN-00065">armature plate </uscom:PartName><uscom:PartNumber com:id="PN-00065">12.</uscom:PartNumber> The motor further has a <uscom:PartName com:idrefs="PN-00066">shaft </uscom:PartName><uscom:PartNumber com:id="PN-00066">13</uscom:PartNumber> which is rotatable relative to a housing of the motor and relative to <uscom:PartName com:idrefs="PN-00067">armature plate </uscom:PartName><uscom:PartNumber com:id="PN-00067">12.</uscom:PartNumber> <uscom:PartName com:idrefs="PN-00068">Hub </uscom:PartName><uscom:PartNumber com:id="PN-00068">15</uscom:PartNumber> is non-rotatably connected to shaft 13 in such a way that a precisely adjusted air gap having a gap width D is provided between <uscom:PartName com:idrefs="PN-00069">circuit board </uscom:PartName><uscom:PartNumber com:id="PN-00069">1</uscom:PartNumber> and <uscom:PartName com:idrefs="PN-00070">angular scale </uscom:PartName><uscom:PartNumber com:id="PN-00070">9.</uscom:PartNumber> To this <uscom:PartName com:idrefs="PN-00071">end, shaft </uscom:PartName><uscom:PartNumber com:id="PN-00071">13</uscom:PartNumber> has a first internal thread 13.1 that can mesh with an external thread of <uscom:PartName com:idrefs="PN-00072">hub </uscom:PartName><uscom:PartNumber com:id="PN-00072">15.</uscom:PartNumber> This allows <uscom:PartName com:idrefs="PN-00073">hub </uscom:PartName><uscom:PartNumber com:id="PN-00073">15</uscom:PartNumber> to be axially<uscom:BoundaryDataReference com:idref="HDR-00033"/></uscom:P><?PageStart number='12'?><uscom:BoundaryDataReference com:idref="HDR-00034"/>
+<uscom:BoundaryDataReference com:idref="HDR-00035"/>
+<uscom:P com:pNumber="97" com:id="p-97">displaced relative to <uscom:PartName com:idrefs="PN-00074">shaft </uscom:PartName><uscom:PartNumber com:id="PN-00074">13</uscom:PartNumber> through suitable relative rotation between <uscom:PartName com:idrefs="PN-00075">shaft </uscom:PartName><uscom:PartNumber com:id="PN-00075">13</uscom:PartNumber> and <uscom:PartName com:idrefs="PN-00076">hub </uscom:PartName><uscom:PartNumber com:id="PN-00076">15.</uscom:PartNumber> During mounting of <uscom:PartName com:idrefs="PN-00077">hub </uscom:PartName><uscom:PartNumber com:id="PN-00077">15</uscom:PartNumber> to shaft 13, initially, <uscom:PartName com:idrefs="PN-00078">hub </uscom:PartName><uscom:PartNumber com:id="PN-00078">15</uscom:PartNumber> is screwed into <uscom:PartName com:idrefs="PN-00079">shaft </uscom:PartName><uscom:PartNumber com:id="PN-00079">13,</uscom:PartNumber> the spacing or gap width D (here, for example, 1.4 mm) between the top edge of <uscom:PartName com:idrefs="PN-00080">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00080">5</uscom:PartNumber> and the top surface of <uscom:PartName com:idrefs="PN-00081">angular scale </uscom:PartName><uscom:PartNumber com:id="PN-00081">9</uscom:PartNumber> being precisely set using an auxiliary tool. Once this position is reached, a <uscom:PartName com:idrefs="PN-00082">central bolt </uscom:PartName><uscom:PartNumber com:id="PN-00082">16</uscom:PartNumber> is turned into a second (smaller) internal thread 13.2 of <uscom:PartName com:idrefs="PN-00083">shaft </uscom:PartName><uscom:PartNumber com:id="PN-00083">13.</uscom:PartNumber> As a result, the threads of <uscom:PartName com:idrefs="PN-00084">shaft </uscom:PartName><uscom:PartNumber com:id="PN-00084">13</uscom:PartNumber> and <uscom:PartName com:idrefs="PN-00085">hub </uscom:PartName><uscom:PartNumber com:id="PN-00085">15</uscom:PartNumber> are clamped against one another, whereupon the <uscom:PartName com:idrefs="PN-00086">angular scale </uscom:PartName><uscom:PartNumber com:id="PN-00086">9</uscom:PartNumber> carrying the graduation structure is non-rotatably fixed to shaft 13.</uscom:P><uscom:P com:pNumber="98" com:id="p-98">[0059<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> After that, the scanning unit, in <uscom:PartName com:idrefs="PN-00087">particular housing body </uscom:PartName><uscom:PartNumber com:id="PN-00087">5,</uscom:PartNumber> is mounted to the <uscom:PartName com:idrefs="PN-00088">armature plate </uscom:PartName><uscom:PartNumber com:id="PN-00088">12</uscom:PartNumber> of the motor. To prevent relative rotation of <uscom:PartName com:idrefs="PN-00089">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00089">5</uscom:PartNumber> with respect to <uscom:PartName com:idrefs="PN-00090">armature plate </uscom:PartName><uscom:PartNumber com:id="PN-00090">12,</uscom:PartNumber> <uscom:PartName com:idrefs="PN-00091">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00091">5</uscom:PartNumber> has a <uscom:PartName com:idrefs="PN-00092">key </uscom:PartName><uscom:PartNumber com:id="PN-00092">16</uscom:PartNumber> (FIG. 5), which is inserted into a groove of a <uscom:PartName com:idrefs="PN-00093">so-called coil carrier </uscom:PartName><uscom:PartNumber com:id="PN-00093">14</uscom:PartNumber> provided on the stator. In <uscom:PartName com:idrefs="PN-00094">addition, housing body </uscom:PartName><uscom:PartNumber com:id="PN-00094">5</uscom:PartNumber> is axially preloaded, so that <uscom:PartName com:idrefs="PN-00095">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00095">5</uscom:PartNumber> is elastically deformed and the axial gap widths of slots 5.21, 5.22, 5.23, 5.24 are reduced as compared to the relaxed state. In accordance with FIG. 6, a <uscom:PartName com:idrefs="PN-00096">circumferential retaining ring </uscom:PartName><uscom:PartNumber com:id="PN-00096">11</uscom:PartNumber> (here a circlip) is installed in order to maintain this axial preload. This ensures that the scanning unit will permanently rest with the stop surface 5.4 of <uscom:PartName com:idrefs="PN-00097">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00097">5</uscom:PartNumber> against the <uscom:PartName com:idrefs="PN-00098">armature plate </uscom:PartName><uscom:PartNumber com:id="PN-00098">12</uscom:PartNumber> of the motor. Lifting of stop surface 5.4 off the <uscom:PartName com:idrefs="PN-00099">armature plate </uscom:PartName><uscom:PartNumber com:id="PN-00099">12</uscom:PartNumber> is impossible, even in the presence of relatively strong vibrations of the motor or upon the occurrence of shocks. Because <uscom:PartName com:idrefs="PN-00100">circuit board </uscom:PartName><uscom:PartNumber com:id="PN-00100">1</uscom:PartNumber> is disposed flush with stop surface 5.4, the distance between <uscom:PartName com:idrefs="PN-00101">circuit board </uscom:PartName><uscom:PartNumber com:id="PN-00101">1</uscom:PartNumber> and <uscom:PartName com:idrefs="PN-00102">angular scale </uscom:PartName><uscom:PartNumber com:id="PN-00102">9</uscom:PartNumber> is equal to the previously set gap width <uscom:OCRConfidenceData uscom:ocrConfidenceCode="88">D.</uscom:OCRConfidenceData></uscom:P><uscom:P com:pNumber="99" com:id="p-99">[0060<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Due to the <uscom:PartName com:idrefs="PN-00103">above-described design, housing body </uscom:PartName><uscom:PartNumber com:id="PN-00103"><uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">5</uscom:OCRConfidenceData></uscom:PartNumber> is axially flexible but torsionally and radially rigid.</uscom:P><uscom:P com:pNumber="100" com:id="p-100">[0061<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> During operation of the angle-measuring device, angular <uscom:PartName com:idrefs="PN-00104">scale </uscom:PartName><uscom:PartNumber com:id="PN-00104">9</uscom:PartNumber> rotates about axis A relative to the scanning unit. The angle-measuring device under consideration has no integral bearing (i.e., no rolling-element bearing or sliding bearing) to achieve relative rotatability, so that, in the exemplary embodiment presented here, it is a bearingless angle-measuring device.</uscom:P><uscom:P com:pNumber="101" com:id="p-101">[0062<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> Thus, <uscom:PartName com:idrefs="PN-00105">angular scale </uscom:PartName><uscom:PartNumber com:id="PN-00105">9</uscom:PartNumber> and the scanning unit are rotatable relative to each other, the <uscom:PartName com:idrefs="PN-00106">angular scale </uscom:PartName><uscom:PartNumber com:id="PN-00106">9</uscom:PartNumber> attached to sha<uscom:OCRConfidenceData uscom:ocrConfidenceCode="66">ft</uscom:OCRConfidenceData> 13 rotating during operation of the angle-measuring device. Thus, the relative rotational speed between <uscom:PartName com:idrefs="PN-00107">angular scale </uscom:PartName><uscom:PartNumber com:id="PN-00107">9</uscom:PartNumber> and the scanning unit is also the<uscom:BoundaryDataReference com:idref="HDR-00036"/></uscom:P><?PageStart number='13'?><uscom:BoundaryDataReference com:idref="HDR-00037"/>
+<uscom:BoundaryDataReference com:idref="HDR-00038"/>
+<uscom:P com:pNumber="104" com:id="p-104">rotational speed between <uscom:PartName com:idrefs="PN-00108">shaft </uscom:PartName><uscom:PartNumber com:id="PN-00108">13</uscom:PartNumber> and <uscom:PartName com:idrefs="PN-00109">stationary housing body </uscom:PartName><uscom:PartNumber com:id="PN-00109">5.</uscom:PartNumber> During operation of the angle-measuring device, the non-rotating excitation coils 10 of the stationary scanning unit generate a homogeneous alternating field which is modulated by <uscom:PartName com:idrefs="PN-00110">angular scale </uscom:PartName><uscom:PartNumber com:id="PN-00110">9</uscom:PartNumber> as a function of the angular position or angle of rotation of <uscom:PartName com:idrefs="PN-00111">shaft </uscom:PartName><uscom:PartNumber com:id="PN-00111">13.</uscom:PartNumber> The modulated electromagnetic field generates angle-dependent signals in <uscom:PartName com:idrefs="PN-00112">detector assembly </uscom:PartName><uscom:PartNumber com:id="PN-00112">2,</uscom:PartNumber> which is also located on the scanning unit. The signals generated by <uscom:PartName com:idrefs="PN-00113">detector assembly </uscom:PartName><uscom:PartNumber com:id="PN-00113">2;</uscom:PartNumber> i.e., here the receiver windings, are further processed by <uscom:PartName com:idrefs="PN-00114">evaluation electronics </uscom:PartName><uscom:PartNumber com:id="PN-00114">3</uscom:PartNumber> so as to determine a relative angular position between the scanning unit and <uscom:PartName com:idrefs="PN-00115">angular scale </uscom:PartName><uscom:PartNumber com:id="PN-00115">9.</uscom:PartNumber> The connector located in <uscom:PartName com:idrefs="PN-00116">housing body </uscom:PartName><uscom:PartNumber com:id="PN-00116">5;</uscom:PartNumber> i.e., contacts 4.1 are brought into contact with a connecting cable, which is connected to subsequent electronics.</uscom:P><uscom:P com:pNumber="105" com:id="p-105">[0063<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> It can generally be stated that the measurement system also responds to variations in the actual scanning distance D. Scanning distance D contains information as to whether or not the brake disposed in the stator is engaged. This allows the scanning unit to determine the current state of the brake (engaged or released) at any one time.</uscom:P><uscom:P com:pNumber="106" com:id="p-106">[0064<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> In the exemplary embodiment presented here, the angle-measuring device is designed according to what is known as "all-round scanning." This means, in particular, that the scanning unit is configured such that <uscom:PartName com:idrefs="PN-00117">angular scale </uscom:PartName><uscom:PartNumber com:id="PN-00117">9</uscom:PartNumber> can be scanned by the scanning unit or by <uscom:PartName com:idrefs="PN-00118">detector assembly </uscom:PartName><uscom:PartNumber com:id="PN-00118">2</uscom:PartNumber> over almost the entire circumference thereof<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">,</uscom:OCRConfidenceData> thus allowing generation of angle-dependent output signals. Accordingly, the scanning unit scans nearly the entire graduation structure of <uscom:PartName com:idrefs="PN-00119">angular scale </uscom:PartName><uscom:PartNumber com:id="PN-00119">9</uscom:PartNumber> to obtain a position signal.</uscom:P><uscom:P com:pNumber="107" com:id="p-107">[0065<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> FIG. 7 illustrates a second exemplary embodiment, which differs from the first by an alternative configuration of a housing body 5<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">'</uscom:OCRConfidenceData>. This variant allows the scanning unit to be mounted by clamping action. Housing body 5<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">'</uscom:OCRConfidenceData> has two axially extending slits 5.5 as well as wedge-shaped elements 5.6, which can be displaced in the axial direction by clamping screws</uscom:P><uscom:P com:pNumber="108" com:id="p-108">5.7. This allows the outer contour of housing body 5<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">'</uscom:OCRConfidenceData> to be urged radially outward in this area, which results in permanent clamping of housing body 5<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">'</uscom:OCRConfidenceData>, given suitable dimensioning of the motor housing.</uscom:P><uscom:P com:pNumber="109" com:id="p-109">[0066<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> While embodiments of the invention have been illustrated and described in detail in the drawings and foregoing description, such illustration and description are to be considered<uscom:BoundaryDataReference com:idref="HDR-00039"/></uscom:P><?PageStart number='14'?><uscom:BoundaryDataReference com:idref="HDR-00040"/>
+<uscom:BoundaryDataReference com:idref="HDR-00041"/>
+<uscom:P com:pNumber="112" com:id="p-112">illustrative or exemplary and not restrictive. It will be understood that changes and modifications may be made by those of ordinary skill within the scope of the following claims. In particular, the present invention covers further embodiments with any combination of features from different embodiments described above and below. Additionally, statements made herein characterizing the invention refer to an embodiment of the invention and not necessarily all embodiments.</uscom:P><uscom:P com:pNumber="113" com:id="p-113">[0067<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> The terms used in the claims should be construed to have the broadest reasonable interpretation consistent with the foregoing description. For example, the use of the article "a" or "the" in introducing an element should not be interpreted as being exclusive of a plurality of elements. Likewise, the recitation of "or" should be interpreted as being inclusive, such that the recitation of "A or B" is not exclusive of "A and B," unless it is clear from the context or the foregoing description that only one of A and B is intended. Further, the recitation of "at least one of A, B and C" should be interpreted as one or more of a group of elements consisting of A, B and C, and should not be interpreted as requiring at least one of each of the listed elements A, B and C, regardless of whether A, B and C are related as categories or otherwise. Moreover, the recitation of "A, B and/or C" or "at least one of A, B or C" should be interpreted as including any singular entity from the listed elements, e.g., A, any subset from the listed elements, e.g., A and B, or the entire list of elements A, B and C.</uscom:P><uscom:BoundaryDataReference com:idref="HDR-00042"/>
+<uscom:BoundaryDataBag><uscom:BoundaryData><uscom:HeaderText com:id="HDR-00001">Attorney Docket No. 817326</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00002">(Client ref<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">.</uscom:OCRConfidenceData> P2039-US/CD)</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00003">Page 1 of <uscom:OCRConfidenceData uscom:ocrConfidenceCode="68">17</uscom:OCRConfidenceData></uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00004">Attorney Docket No. 817326</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00005">(Client ref<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">.</uscom:OCRConfidenceData> P2039-US/CD)</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00006">Page 2 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00007">Attorney Docket No. 817326</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00008">(Client ref<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">.</uscom:OCRConfidenceData> P2039-US/CD)</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00009">Page 3 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00010">Attorney Docket No. 817326</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00011">(Client ref<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">.</uscom:OCRConfidenceData> P2039-US/CD)</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00012">Page 4 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00013">Attorney Docket No. 817326</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00014">(Client ref<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">.</uscom:OCRConfidenceData> P2039-US/CD)</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00015">Page 5 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00016">Attorney Docket No. 817326</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00017">(Client ref<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">.</uscom:OCRConfidenceData> P2039-US/CD)</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00018">Page 6 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00019">Attorney Docket No. 817326</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00020">(Client ref<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">.</uscom:OCRConfidenceData> P2039-US/CD)</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00021">Page 7 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00022">Attorney Docket No. 817326</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00023">(Client ref<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">.</uscom:OCRConfidenceData> P2039-US/CD)</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00024">Page 8 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00025">Attorney Docket No. 817326</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00026">(Client ref<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">.</uscom:OCRConfidenceData> P2039-US/CD)</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00027">Page 9 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00028">Attorney Docket No. 817326</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00029">(Client ref<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">.</uscom:OCRConfidenceData> P2039-US/CD)</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00030">Page 10 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00031">Attorney Docket No. 817326</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00032">(Client ref<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">.</uscom:OCRConfidenceData> P2039-US/CD)</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00033">Page 11 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00034">Attorney Docket No. 817326</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00035">(Client ref<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">.</uscom:OCRConfidenceData> P2039-US/CD)</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00036">Page 12 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00037">Attorney Docket No. 817326</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00038">(Client ref<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">.</uscom:OCRConfidenceData> P2039-US/CD)</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00039">Page 13 of 17</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00040">Attorney Docket No. 817326</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00041">(Client ref<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">.</uscom:OCRConfidenceData> P2039-US/CD)</uscom:HeaderText>
+<uscom:HeaderText com:id="HDR-00042">Page 14 of 17</uscom:HeaderText>
+</uscom:BoundaryData></uscom:BoundaryDataBag></uspat:SpecificationDocument>