<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ep-patent-document PUBLIC "-//EPO//EP PATENT DOCUMENT 1.6//EN" "ep-patent-document-v1-6.dtd">
<!-- This XML data has been generated under the supervision of the European Patent Office -->
<ep-patent-document id="EP23160952A1" file="EP23160952NWA1.xml" lang="en" country="EP" doc-number="4242071" kind="A1" date-publ="20230913" status="n" dtd-version="ep-patent-document-v1-6">
<SDOBI lang="en"><B000><eptags><B001EP>ATBECHDEDKESFRGBGRITLILUNLSEMCPTIESILTLVFIROMKCYALTRBGCZEEHUPLSKBAHRIS..MTNORSMESMMAKHTNMD..........</B001EP><B005EP>J</B005EP><B007EP>2.0.21 -  1100000/0</B007EP></eptags></B000><B100><B110>4242071</B110><B120><B121>EUROPEAN PATENT APPLICATION</B121></B120><B130>A1</B130><B140><date>20230913</date></B140><B190>EP</B190></B100><B200><B210>23160952.0</B210><B220><date>20230309</date></B220><B240><B241><date>20230309</date></B241></B240><B250>en</B250><B251EP>en</B251EP><B260>en</B260></B200><B300><B310>202217692615</B310><B320><date>20220311</date></B320><B330><ctry>US</ctry></B330></B300><B400><B405><date>20230913</date><bnum>202337</bnum></B405><B430><date>20230913</date><bnum>202337</bnum></B430></B400><B500><B510EP><classification-ipcr sequence="1"><text>B60S   1/56        20060101AFI20230803BHEP        </text></classification-ipcr><classification-ipcr sequence="2"><text>B60S   1/08        20060101ALI20230803BHEP        </text></classification-ipcr><classification-ipcr sequence="3"><text>G02B  27/00        20060101ALN20230803BHEP        </text></classification-ipcr></B510EP><B520EP><classifications-cpc><classification-cpc sequence="1"><text>G02B  27/0006      20130101 LA20230727BHEP        </text></classification-cpc><classification-cpc sequence="2"><text>B60S   1/56        20130101 LA20230727BHEP        </text></classification-cpc><classification-cpc sequence="3"><text>G03B  17/00        20130101 LI20230804BHEP        </text></classification-cpc><classification-cpc sequence="4"><text>G01S  17/00        20130101 LI20230804BHEP        </text></classification-cpc><classification-cpc sequence="5"><text>H04N  23/52        20230101 LA20230804BHEP        </text></classification-cpc></classifications-cpc></B520EP><B540><B541>de</B541><B542>SENSORABSCHIRMUNG UND VERFAHREN</B542><B541>en</B541><B542>SENSOR SHIELD AND METHOD</B542><B541>fr</B541><B542>BLINDAGE DE CAPTEUR ET PROCÉDÉ</B542></B540><B590><B598>1</B598></B590></B500><B700><B710><B711><snm>International Truck Intellectual 
Property Company, LLC</snm><iid>101345494</iid><irf>IN14R76</irf><adr><str>2701 Navistar Drive</str><city>Lisle, IL 60532</city><ctry>US</ctry></adr></B711></B710><B720><B721><snm>REIS, Caio</snm><adr><city>Aurora, 60502</city><ctry>US</ctry></adr></B721><B721><snm>WONG, Peter S.</snm><adr><city>Naperville, 60565</city><ctry>US</ctry></adr></B721></B720><B740><B741><snm>Kuhnen &amp; Wacker 
Patent- und Rechtsanwaltsbüro PartG mbB</snm><iid>101158360</iid><adr><str>Prinz-Ludwig-Straße 40A</str><city>85354 Freising</city><ctry>DE</ctry></adr></B741></B740></B700><B800><B840><ctry>AL</ctry><ctry>AT</ctry><ctry>BE</ctry><ctry>BG</ctry><ctry>CH</ctry><ctry>CY</ctry><ctry>CZ</ctry><ctry>DE</ctry><ctry>DK</ctry><ctry>EE</ctry><ctry>ES</ctry><ctry>FI</ctry><ctry>FR</ctry><ctry>GB</ctry><ctry>GR</ctry><ctry>HR</ctry><ctry>HU</ctry><ctry>IE</ctry><ctry>IS</ctry><ctry>IT</ctry><ctry>LI</ctry><ctry>LT</ctry><ctry>LU</ctry><ctry>LV</ctry><ctry>MC</ctry><ctry>ME</ctry><ctry>MK</ctry><ctry>MT</ctry><ctry>NL</ctry><ctry>NO</ctry><ctry>PL</ctry><ctry>PT</ctry><ctry>RO</ctry><ctry>RS</ctry><ctry>SE</ctry><ctry>SI</ctry><ctry>SK</ctry><ctry>SM</ctry><ctry>TR</ctry></B840><B844EP><B845EP><ctry>BA</ctry></B845EP></B844EP><B848EP><B849EP><ctry>KH</ctry></B849EP><B849EP><ctry>MA</ctry></B849EP><B849EP><ctry>MD</ctry></B849EP><B849EP><ctry>TN</ctry></B849EP></B848EP></B800></SDOBI>
<abstract id="abst" lang="en">
<p id="pa01" num="0001">A sensor shield for protecting a sensor having an input surface on a vehicle with a controlling computer and on the vehicle, the sensor shield comprises a sensor-maintenance unit operatively attached to the sensor input surface. Shield implementation devices, each having a bottom surface, are oppositely disposed adjacent the sensor. A shield source is located adjacent the bottom surfaces of the shield implementation devices, and has a surface that covers the input surface of the sensor.
<img id="iaf01" file="imgaf001.tif" wi="78" he="106" img-content="drawing" img-format="tif"/></p>
</abstract>
<description id="desc" lang="en"><!-- EPO <DP n="1"> -->
<heading id="h0001">BACKGROUND</heading>
<p id="p0001" num="0001">In some vehicles, a multitude of sensors are utilized to provide information for those vehicles. Input of these sensors may be obscured due to dirt, debris, road chemicals, biomass, or other contaminants on a lens or surfaces that are used to sense ambient environment. It may be desirable to safeguard the sensors from these contaminants.</p>
<p id="p0002" num="0002">Manual wiping may be used to reduce contaminants on vehicle sensors. However, various non-manual methods and devices may be used for removing contaminants from a sensor. For example, some sensor surfaces may have specialty coatings that act in a passive manner to lessen impact of the contaminants. If there is air movement on the sensor surface, the coatings can facilitate removal of contaminants from the sensor surface.</p>
<p id="p0003" num="0003">Some sensors may be enclosed in compartments or domes that rotate around one axis and incorporate a wiping element to remove contaminants from the sensor surface. Sometimes, rotation of the sensor enclosure in conjunction with vehicle speed may remove contaminants without physical contact from the wiping element. Some automated methods to remove contaminants from sensors include wipers or employment of pressurized air across the sensor surface.</p>
<p id="p0004" num="0004">Developing a shield source for a sensor that allows a vehicle computer system to automatically index the shield source in order to improve performance of a sensor system is relevant for industries that use sensors. Therefore, it is desirable to provide a shield source for protecting the sensor system of a vehicle from degraded performance.</p>
<heading id="h0002">SUMMARY</heading>
<p id="p0005" num="0005">This disclosure includes embodiments of a sensor shield for protecting a sensor of a vehicle. One embodiment provides a sensor shield for protecting a sensor having an input surface on a vehicle with a controlling computer and on the vehicle. The sensor shield comprises a sensor-maintenance unit operatively attached to the sensor input surface. Shield implementation devices, each having a bottom surface, are oppositely disposed adjacent the sensor. A shield source is located adjacent the bottom surfaces of the shield implementation devices, and has a surface that covers the input surface of the sensor.<!-- EPO <DP n="2"> --></p>
<heading id="h0003">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
<p id="p0006" num="0006">
<ul id="ul0001" list-style="none" compact="compact">
<li><figref idref="f0001"><b>FIG. 1</b></figref> is a flow chart showing a sensor shield described herein;</li>
<li><figref idref="f0002"><b>FIG. 2</b></figref> is a flow chart showing response of a computer system of a vehicle to a sensor surface condition;</li>
<li><figref idref="f0003"><b>FIG. 3</b></figref> illustrates one embodiment of a sensor shield;</li>
<li><figref idref="f0004"><b>FIG. 4</b></figref> illustrates another embodiment of a sensor shield; and</li>
<li><figref idref="f0005"><b>FIG. 5</b></figref> illustrates a further embodiment of a sensor shield.</li>
</ul></p>
<heading id="h0004">DETAILED DESCRIPTION</heading>
<p id="p0007" num="0007">The following detailed description is a contemplated mode of carrying out a sensor shield and process described herein. Although the sensor shield process is explained in relation to illustrated embodiments, it is to be understood that many other possible modifications and variations can be made without departing from the spirit and scope of the disclosure. Therefore, a sensor shield may be used to protect various types of sensors including a camera, sonar, laser, radar, and a plurality of other sensors. These sensors may be used to scan and to record information from an external environment and/or an internal environment of stationary or non-stationary vehicle such as a truck, an aircraft, a boat, a train and the like, or in a stationary environment such as on a wall, a seating arrangement in a public area, a hallway, an entryway, and in any environment where a sensor can be used for detecting and identifying environmental conditions.</p>
<p id="p0008" num="0008">It is understood that the term vehicle as described herein includes an electric vehicle, a truck, a passenger vehicle, a hybrid vehicle, a sport utility vehicle, a bus, a water vehicle, a commercial vehicle, a fuel-driven vehicle and the like.</p>
<p id="p0009" num="0009">It is further understood that a sensor shield <b>10</b> and method of use thereof may be a part of an external vehicle monitoring system which can be in wireless communication with a sensor <b>12</b> on a vehicle <b>14.</b> For example, <figref idref="f0001"><b>FIGS. 1</b></figref> and <figref idref="f0002"><b>2</b></figref> are flow charts showing interoperability of the sensor shield <b>10</b> with a computer system, not shown for clarity, associated with the vehicle <b>14.</b> Such a computer system can include external vehicle monitoring systems such as a command center, a truck monitoring station, a vehicle integrated computer system and the like that communicate wirelessly with the vehicle 14.</p>
<p id="p0010" num="0010"><figref idref="f0003"><b>FIG. 3</b></figref> shows one embodiment of the sensor shield <b>10</b> for protecting the sensor <b>12</b> of the vehicle <b>14.</b> The sensor <b>12</b> of the vehicle <b>14</b> has an input surface <b>16</b> and at least one<!-- EPO <DP n="3"> --> sensor-maintenance unit <b>18</b> operatively attached to the input surface 16. The sensor <b>12</b> of the vehicle <b>14</b> communicates with the computer system of the vehicle <b>14.</b> The computer system of the vehicle <b>14</b> is controllably connected with and controls the sensor-maintenance unit <b>18</b> of the vehicle <b>14</b> and the sensor shield <b>10.</b></p>
<p id="p0011" num="0011">In the illustrated embodiments, the sensor shield <b>10</b> has at least a first shield implementation device <b>22</b> and a second shield implementation device <b>24,</b> oppositely disposed adjacent the sensor <b>12.</b> Both the first shield implementation device <b>22</b> and the second shield implementation device <b>24</b> have a top surface <b>26</b> and a bottom surface <b>28</b> for receiving a shield source <b>32</b> located adjacent the bottom surface <b>28</b> of both the first shield implementation device <b>22</b> and the second shield implementation device <b>24.</b> The first shield implementation device <b>22</b> and the second shield implementation device <b>24</b> can be rotatable devices such as a roller, a revolving cylinder, a spool holder, a carousel, a rotatable ring, a disk, a wheel and the like for engaging the shield source <b>32.</b> The shield source <b>32</b> can include a shield, a cover, a guard, and the like having a size and a surface <b>34</b> for covering the input surface 16 of the sensor <b>12.</b></p>
<p id="p0012" num="0012">In one embodiment, the shield source <b>32</b> is constructed of a flexible sheet of transparent material, such as a plastic or other material that can be coated to protect the input surface 16 of the sensor <b>12</b> from a contaminant. The first shield implementation device <b>22</b> and the second shield implementation device <b>24</b> are mounted to the vehicle <b>14</b> and are provided adjacent a side <b>36</b> of the sensor <b>12.</b> In the embodiments shown in <figref idref="f0003 f0004 f0005">Figs. 3 through 5</figref>, the first shield implementation device <b>22</b> and the second shield implementation device <b>24</b> have an electrical connection with a motor and a motor driver that advance the shield source <b>32</b> in accordance with at least one advancement sequence. Both the first shield implementation device <b>22</b> and the second shield implementation device <b>24</b> have a controller configured to receive communication from the computer system of the vehicle <b>14.</b> The computer system of the vehicle <b>14</b> is configured to send a command to the first implantation device <b>22</b> and the second shield implementation device <b>24.</b> At least one command from the computer system regulates advancement of the shield source <b>32</b> in accordance with detection of at least a first sensor surface condition and the sensor-maintenance unit <b>18</b> performing at least one sensor-maintenance sequence. With advancement of the shield source <b>32,</b> the sensor <b>12</b> communicates with the computer system of the vehicle <b>14</b> to direct removal of the shield source <b>32</b> and the provision of a new shield source <b>32.</b></p>
<p id="p0013" num="0013">The sensor <b>12</b> detects at least the first sensor surface condition and the computer system of the vehicle <b>14</b> enables the sensor-maintenance unit <b>18</b> to change the first sensor surface<!-- EPO <DP n="4"> --> condition. The computer system of the vehicle 14 further enables the first shield implementation device 22 and the second shield implementation device <b>24</b> to advance the shield source <b>32</b> in response to first deployment of the sensor-maintenance unit <b>18</b> if the first sensor surface condition is outside of a specified range. A first sensor surface condition can include presence of a contaminant, such as salt, snow, dirt, dust, and other types of environmental contamination. The sensor-maintenance unit <b>18</b> can include a wiper, pressurized air or any commercially available sensor-maintenance unit that removes a contaminant from a sensor. The advancement sequence comprises the first shield implementation device <b>22</b> receiving the shield source <b>32</b> in an undeployed. i.e. rolled, configuration and the second shield implementation device <b>24</b> accommodating advanced portions of the shield source <b>32.</b></p>
<p id="p0014" num="0014">The motor driver regulates intermittent release of the shield source <b>32</b> according to at least a first sensor surface condition. The motor driver establishes a reeling start and a reeling end of the shield source 32. The motor driver can immobilize the shield source <b>32</b> based on a signal from the sensor <b>12.</b> The sensor shield <b>10</b> thereby transmits information identifying location of the shield source <b>32</b> adjacent the input surface 16 of the sensor. The shield implementation device <b>22</b> and the shield implementation device <b>24</b> permit the shield source <b>32</b> to be balanced and to calibrate any imbalance of the shield source <b>32</b> through advancement of the shield source <b>32.</b></p>
<p id="p0015" num="0015">The shield source <b>32</b> extends over the sensor <b>12</b> and is positioned to abut the input surface <b>16</b> and to be frictionally fitted thereover to obstruct a contaminant from coming between the sensor <b>12</b> and the shield source <b>32</b> while allowing for movement of the shield source <b>32.</b> This allows for decontamination, repair, maintenance, and/or replacement of the shield source <b>32.</b></p>
<p id="p0016" num="0016">Once deployed, the shield source <b>32</b> operates as a second input surface for protecting the input surface 14 of the sensor <b>12.</b> This also improves performance of the sensor <b>12</b> by reducing performance degradation due to dirt, snow, salt, and other contaminants that are encountered by a vehicle <b>14.</b></p>
<p id="p0017" num="0017">In a particular embodiment shown in <figref idref="f0004"><b>FIG. 4</b></figref><b>,</b> the shield source <b>32</b> comprises a plurality of equally partitioned segments <b>38</b> provided in a rolled up configuration on the first shield implementation device <b>22</b> and the second shield implementation device <b>24.</b> Each individual shield source <b>32</b> of the plurality of equally partitioned segments <b>38</b> can be connected to opposing longitudinal edges for a rolling connection to the shield implementation device <b>22</b> and the shield implementation device <b>24</b> and for traversing the sensor <b>12.</b> The opposing longitudinal edges can be constructed of a flexible sheet of<!-- EPO <DP n="5"> --> transparent material and could function as retainer engaging the top surface 26 of the shield implementation device 22 and bottom surface <b>28</b> of the shield implementation device <b>24.</b> An individual segment of the plurality of equally partitioned segments <b>38</b> can provide frictional engagement with the top surface 26 of the shield implementation device 22 and bottom surface <b>28</b> of the shield implementation device <b>24</b> to continuously sustain a holding and rotatable state therebetween. The shield implementation device <b>22</b> and the shield implementation device <b>24</b> can advance the plurality of equally partitioned segments <b>38</b> consecutively across the sensor <b>12.</b> At least one command of the computer system regulates advancement of each of the plurality of equally partitioned segments <b>38</b> in accordance with performance data of the sensor <b>12.</b> The computer system can identify advancement of all of the plurality of equally partitioned segments <b>38.</b> Each individual shield source <b>32</b> of the plurality of equally partitioned segments 3 8can be removed, replaced, cleaned and reused. The plurality of equally partitioned segments <b>38</b> can comprise a plurality of shapes, sizes, and thickness to facilitate proper maintenance and/or operation of the sensor <b>12.</b></p>
<p id="p0018" num="0018">In a further embodiment shown in <figref idref="f0004"><b>FIG. 4</b></figref><b>,</b> the shield implementation device <b>22</b> and the shield implementation device <b>24</b> may be located adjacent two opposing sides <b>36</b> of the sensor <b>12.</b> The shield source <b>32</b> is included on the first shield implementation device <b>22</b> and the second shield implementation device <b>24</b> in a conveyor belt configuration. Therefore in this embodiment, the shield source <b>32</b> is rotatable about the sides 36 of the sensor 12 depending on position of the shield implementation device <b>22</b> and shield implementation device 24. This shield implementation device arrangement can include support an element, a magnet, a belt and the like at a position adjacent the top surfaces <b>26</b> and the bottom surfaces <b>28</b> of the shield implementation device <b>22</b> and the shield implementation devices <b>24</b> to hold the shield source <b>32</b> in place during and after deployment.</p>
</description>
<claims id="claims01" lang="en"><!-- EPO <DP n="6"> -->
<claim id="c-en-0001" num="0001">
<claim-text>A sensor shield for protecting a sensor of a vehicle, the sensor shield comprising:
<claim-text>at least one sensor-maintenance unit operatively attached to the input surface of the sensor;</claim-text>
<claim-text>a first shield implementation device having a top surface and a bottom surface and a second shield implementation device having a top surface and a bottom surface, the first shield implementation device and the second shield implementation device oppositely disposed adjacent the sensor; and</claim-text>
<claim-text>a shield source located adj acent the bottom surface of both the first shield implementation device and the second shield implementation device, the shield source having a surface that covers the input surface of the sensor.</claim-text></claim-text></claim>
<claim id="c-en-0002" num="0002">
<claim-text>The sensor shield defined in claim 1 wherein the first shield implementation device receives the shield source in a rolled configuration.</claim-text></claim>
<claim id="c-en-0003" num="0003">
<claim-text>The sensor shield defined in claim 1 wherein the shield source is included on the first shield implementation device and the second shield implementation device in a conveyor belt configuration.</claim-text></claim>
<claim id="c-en-0004" num="0004">
<claim-text>The sensor shield defined in claim 1 wherein the shield source comprises a plurality of segments.</claim-text></claim>
<claim id="c-en-0005" num="0005">
<claim-text>The sensor shield defined in claim 4 wherein the segments are equally partitioned.</claim-text></claim>
</claims>
<drawings id="draw" lang="en"><!-- EPO <DP n="7"> -->
<figure id="f0001" num="1"><img id="if0001" file="imgf0001.tif" wi="116" he="157" img-content="drawing" img-format="tif"/></figure><!-- EPO <DP n="8"> -->
<figure id="f0002" num="2"><img id="if0002" file="imgf0002.tif" wi="141" he="160" img-content="drawing" img-format="tif"/></figure><!-- EPO <DP n="9"> -->
<figure id="f0003" num="3"><img id="if0003" file="imgf0003.tif" wi="121" he="144" img-content="drawing" img-format="tif"/></figure><!-- EPO <DP n="10"> -->
<figure id="f0004" num="4"><img id="if0004" file="imgf0004.tif" wi="118" he="128" img-content="drawing" img-format="tif"/></figure><!-- EPO <DP n="11"> -->
<figure id="f0005" num="5"><img id="if0005" file="imgf0005.tif" wi="77" he="93" img-content="drawing" img-format="tif"/></figure>
</drawings>
<search-report-data id="srep" lang="en" srep-office="EP" date-produced=""><doc-page id="srep0001" file="srep0001.tif" wi="157" he="233" type="tif"/><doc-page id="srep0002" file="srep0002.tif" wi="155" he="233" type="tif"/></search-report-data><search-report-data date-produced="20230729" id="srepxml" lang="en" srep-office="EP" srep-type="ep-sr" status="n"><!--
 The search report data in XML is provided for the users' convenience only. It might differ from the search report of the PDF document, which contains the officially published data. The EPO disclaims any liability for incorrect or incomplete data in the XML for search reports.
 -->

<srep-info><file-reference-id>IN14R76</file-reference-id><application-reference><document-id><country>EP</country><doc-number>23160952.0</doc-number></document-id></application-reference><applicant-name><name>International Truck IntellectualProperty Company, LLC</name></applicant-name><srep-established srep-established="yes"/><srep-invention-title title-approval="yes"/><srep-abstract abs-approval="yes"/><srep-figure-to-publish figinfo="by-applicant"><figure-to-publish><fig-number>1</fig-number></figure-to-publish></srep-figure-to-publish><srep-info-admin><srep-office><addressbook><text>MN</text></addressbook></srep-office><date-search-report-mailed><date>20230809</date></date-search-report-mailed></srep-info-admin></srep-info><srep-for-pub><srep-fields-searched><minimum-documentation><classifications-ipcr><classification-ipcr><text>B60S</text></classification-ipcr><classification-ipcr><text>G02B</text></classification-ipcr><classification-ipcr><text>H04N</text></classification-ipcr></classifications-ipcr></minimum-documentation></srep-fields-searched><srep-citations><citation id="sr-cit0001"><patcit dnum="EP2669123A1" id="sr-pcit0001" url="http://v3.espacenet.com/textdoc?DB=EPODOC&amp;IDX=EP2669123&amp;CY=ep"><document-id><country>EP</country><doc-number>2669123</doc-number><kind>A1</kind><name>NISSAN MOTOR MFG UK LTD [GB]</name><date>20131204</date></document-id></patcit><category>X</category><rel-claims>1,2,4,5</rel-claims><rel-passage><passage>* paragraphs [0001],  [0022],  [0036],  [0078] *</passage><passage>* figures 2-4 *</passage></rel-passage></citation><citation id="sr-cit0002"><patcit dnum="DE102017221496A1" id="sr-pcit0002" url="http://v3.espacenet.com/textdoc?DB=EPODOC&amp;IDX=DE102017221496&amp;CY=ep"><document-id><country>DE</country><doc-number>102017221496</doc-number><kind>A1</kind><name>BOSCH GMBH ROBERT [DE]</name><date>20190606</date></document-id></patcit><category>X</category><rel-claims>1,3</rel-claims><rel-passage><passage>* paragraphs [0005],  [0011] *</passage><passage>* figures 1-5 *</passage></rel-passage></citation><citation id="sr-cit0003"><patcit dnum="US2021227113A1" id="sr-pcit0003" url="http://v3.espacenet.com/textdoc?DB=EPODOC&amp;IDX=US2021227113&amp;CY=ep"><document-id><country>US</country><doc-number>2021227113</doc-number><kind>A1</kind><name>HELMRICH HARRY J [US]</name><date>20210722</date></document-id></patcit><category>X</category><rel-claims>1,2</rel-claims><rel-passage><passage>* paragraphs [0014],  [0070],  [0078] *</passage><passage>* figures 3-5, 7,8 *</passage></rel-passage></citation><citation id="sr-cit0004"><patcit dnum="DE2926768A1" id="sr-pcit0004" url="http://v3.espacenet.com/textdoc?DB=EPODOC&amp;IDX=DE2926768&amp;CY=ep"><document-id><country>DE</country><doc-number>2926768</doc-number><kind>A1</kind><name>MESSERSCHMITT BOELKOW BLOHM</name><date>19810115</date></document-id></patcit><category>X</category><rel-claims>1,2</rel-claims><rel-passage><passage>* figure 1 *</passage></rel-passage></citation><citation id="sr-cit0005"><patcit dnum="EP0648044A1" id="sr-pcit0005" url="http://v3.espacenet.com/textdoc?DB=EPODOC&amp;IDX=EP0648044&amp;CY=ep"><document-id><country>EP</country><doc-number>0648044</doc-number><kind>A1</kind><name>DORNIER IREN [ES]</name><date>19950412</date></document-id></patcit><category>X</category><rel-claims>1,2</rel-claims><rel-passage><passage>* figure 1 *</passage></rel-passage></citation><citation id="sr-cit0006"><patcit dnum="US2015298657A1" id="sr-pcit0006" url="http://v3.espacenet.com/textdoc?DB=EPODOC&amp;IDX=US2015298657&amp;CY=ep"><document-id><country>US</country><doc-number>2015298657</doc-number><kind>A1</kind><name>KANTER PASCAL [DE] ET AL</name><date>20151022</date></document-id></patcit><category>A</category><rel-claims>1-5</rel-claims><rel-passage><passage>* figures 1-2 *</passage></rel-passage></citation></srep-citations><srep-admin><examiners><primary-examiner><name>Hillmayr, Heinrich</name></primary-examiner></examiners><srep-office><addressbook><text>Munich</text></addressbook></srep-office><date-search-completed><date>20230729</date></date-search-completed></srep-admin><!--							The annex lists the patent family members relating to the patent documents cited in the above mentioned European search report.							The members are as contained in the European Patent Office EDP file on							The European Patent Office is in no way liable for these particulars which are merely given for the purpose of information.							For more details about this annex : see Official Journal of the European Patent Office, No 12/82						--><srep-patent-family><patent-family><priority-application><document-id><country>EP</country><doc-number>2669123</doc-number><kind>A1</kind><date>20131204</date></document-id></priority-application><family-member><document-id><country>EP</country><doc-number>2669123</doc-number><kind>A1</kind><date>20131204</date></document-id></family-member><family-member><document-id><country>GB</country><doc-number>2502567</doc-number><kind>A</kind><date>20131204</date></document-id></family-member></patent-family><patent-family><priority-application><document-id><country>DE</country><doc-number>102017221496</doc-number><kind>A1</kind><date>20190606</date></document-id></priority-application><text>NONE</text></patent-family><patent-family><priority-application><document-id><country>US</country><doc-number>2021227113</doc-number><kind>A1</kind><date>20210722</date></document-id></priority-application><family-member><document-id><country>US</country><doc-number>2021227113</doc-number><kind>A1</kind><date>20210722</date></document-id></family-member><family-member><document-id><country>WO</country><doc-number>2021150499</doc-number><kind>A1</kind><date>20210729</date></document-id></family-member></patent-family><patent-family><priority-application><document-id><country>DE</country><doc-number>2926768</doc-number><kind>A1</kind><date>19810115</date></document-id></priority-application><text>NONE</text></patent-family><patent-family><priority-application><document-id><country>EP</country><doc-number>0648044</doc-number><kind>A1</kind><date>19950412</date></document-id></priority-application><family-member><document-id><country>DE</country><doc-number>4345147</doc-number><kind>A1</kind><date>19950420</date></document-id></family-member><family-member><document-id><country>EP</country><doc-number>0648044</doc-number><kind>A1</kind><date>19950412</date></document-id></family-member></patent-family><patent-family><priority-application><document-id><country>US</country><doc-number>2015298657</doc-number><kind>A1</kind><date>20151022</date></document-id></priority-application><family-member><document-id><country>CN</country><doc-number>104822568</doc-number><kind>A</kind><date>20150805</date></document-id></family-member><family-member><document-id><country>DE</country><doc-number>102012222126</doc-number><kind>A1</kind><date>20140605</date></document-id></family-member><family-member><document-id><country>US</country><doc-number>2015298657</doc-number><kind>A1</kind><date>20151022</date></document-id></family-member><family-member><document-id><country>WO</country><doc-number>2014086760</doc-number><kind>A1</kind><date>20140612</date></document-id></family-member></patent-family></srep-patent-family></srep-for-pub></search-report-data>
</ep-patent-document>
