<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ep-patent-document PUBLIC "-//EPO//EP PATENT DOCUMENT 1.4//EN" "ep-patent-document-v1-4.dtd">
<ep-patent-document id="EP13305148A1" file="EP13305148NWA1.xml" lang="en" country="EP" doc-number="2765567" kind="A1" date-publ="20140813" status="n" dtd-version="ep-patent-document-v1-4">
<SDOBI lang="en"><B000><eptags><B001EP>ATBECHDEDKESFRGBGRITLILUNLSEMCPTIESILTLVFIROMKCYALTRBGCZEEHUPLSKBAHRIS..MTNORSMESM..................</B001EP><B005EP>J</B005EP><B007EP>DIM360 Ver 2.41 (21 Oct 2013) -  1100000/0</B007EP></eptags></B000><B100><B110>2765567</B110><B120><B121>EUROPEAN PATENT APPLICATION</B121></B120><B130>A1</B130><B140><date>20140813</date></B140><B190>EP</B190></B100><B200><B210>13305148.2</B210><B220><date>20130207</date></B220><B240><B241><date>20130207</date></B241></B240><B250>en</B250><B251EP>en</B251EP><B260>en</B260></B200><B400><B405><date>20140813</date><bnum>201433</bnum></B405><B430><date>20140813</date><bnum>201433</bnum></B430></B400><B500><B510EP><classification-ipcr sequence="1"><text>G08G   1/00        20060101AFI20131014BHEP        </text></classification-ipcr></B510EP><B540><B541>de</B541><B542>Verfahren, Vorrichtung und Empfänger zur Verarbeitung eines Videos</B542><B541>en</B541><B542>A method, a device and a receiver for processing video</B542><B541>fr</B541><B542>Procédé, dispositif et récepteur pour un traitement vidéo</B542></B540><B590><B598>1</B598></B590></B500><B700><B710><B711><snm>Alcatel Lucent</snm><iid>101190217</iid><irf>812287</irf><adr><str>3, avenue Octave Gréard</str><city>75007 Paris</city><ctry>FR</ctry></adr></B711></B710><B720><B721><snm>Weigmann, Walter</snm><adr><str>Alcatel-Lucent Deutschland AG
Thurn-und-Taxis-Strasse 10</str><city>90411 Nuernberg</city><ctry>DE</ctry></adr></B721><B721><snm>Templ, Wolfgang</snm><adr><str>Alcatel-Lucent Deutschland AG
Lorenzstraße 10</str><city>70435 Stuttgart</city><ctry>DE</ctry></adr></B721></B720><B740><B741><snm>Kröhnert, Michael</snm><iid>101346732</iid><adr><str>Alcatel-Lucent Deutschland AG 
Intellectual Property &amp; Standards 
Lorenzstrasse 10</str><city>70435 Stuttgart</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>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><B845EP><ctry>ME</ctry></B845EP></B844EP></B800></SDOBI>
<abstract id="abst" lang="en">
<p id="pa01" num="0001">The invention concerns a device (103, 110) and method for creating a video in a vehicle (100) in particular for sending to a receiver, comprising an analyzer (110) adapted to assess a traffic situation from a captured image of the outside of the vehicle (100), and a multiplexer (103) adapted to join the captured image with recorded audio from a passenger compartment of the vehicle (100) and information about the assessed traffic situation as the video. Furthermore the invention concerns a receiver (107, 109) and method for playing a video comprising an output (109) adapted to output a video, wherein the receiver comprises a de-multiplexer (107) adapted to separate information about an assessed traffic situation from the video, and to determine whether to send an assistive message to the output (109) or not depending on the information about the assessed traffic situation.
<img id="iaf01" file="imgaf001.tif" wi="111" he="100" img-content="drawing" img-format="tif"/></p>
</abstract>
<description id="desc" lang="en"><!-- EPO <DP n="1"> -->
<heading id="h0001"><b><u>Field of the invention</u></b></heading>
<p id="p0001" num="0001">The invention relates to a method, a device and a receiver for processing video.</p>
<heading id="h0002"><b><u>Background</u></b></heading>
<p id="p0002" num="0002">Modern cars are equipped with cameras, mainly for viewing the car environment while parking or while entering a crossing or for reading traffic signs.</p>
<p id="p0003" num="0003">Modern cars comprise communication assistance systems for the driver or passenger to make voice calls through the communication network.</p>
<p id="p0004" num="0004">In many situations, driving and communicating at the same time is not an issue. However critical situations exist, in which for safety sake the focus should be on driving rather than communicating.</p>
<heading id="h0003"><b><u>Summary</u></b></heading>
<p id="p0005" num="0005">The object of the invention is thus to automatically improve safety while driving.</p>
<p id="p0006" num="0006">The main idea of the invention is a device comprising an analyzer adapted to assess a traffic situation from a captured image of the outside of a vehicle, and a sender adapted to send information about the assessed traffic situation.</p>
<p id="p0007" num="0007">Advantageously the device comprises a multiplexer adapted to join the captured image with recorded audio from a passenger<!-- EPO <DP n="2"> --> compartment of the vehicle.</p>
<p id="p0008" num="0008">Advantageously the device comprises a microphone for recording audio of the passenger compartment of the vehicle.</p>
<p id="p0009" num="0009">Advantageously the device comprises a camera for capturing the image of the outside of the vehicle.</p>
<p id="p0010" num="0010">The invention also concerns a vehicle comprising such device and a second device comprising a receiver and an output, wherein the receiver is adapted to receive information about an assessed traffic situation and adapted to determine whether to send an assistive message to the output or not depending on the information about the assessed traffic situation.</p>
<p id="p0011" num="0011">In the second device preferably the assistive message is determined from the information about the assessed traffic situation.</p>
<p id="p0012" num="0012">Further developments of the invention can be gathered from dependent claims and the following description.</p>
<heading id="h0004"><b><u>Brief description of the figures</u></b></heading>
<p id="p0013" num="0013">In the following the invention will be explained further making reference to the attached drawings.
<ul id="ul0001" list-style="none">
<li><figref idref="f0001">Fig. 1</figref> schematically shows a first part of a system according to a first embodiment.</li>
<li><figref idref="f0002">Fig. 2</figref> schematically shows a flow chart of a first method.</li>
<li><figref idref="f0003">Fig. 3</figref> schematically shows a flow chart of a second method.</li>
</ul></p>
<heading id="h0005"><u><b>Description of</b> the <b>embodiments</b></u></heading>
<p id="p0014" num="0014">
<ul id="ul0002" list-style="none">
<li><figref idref="f0001">Figure 1</figref> shows part of a system comprising an embodiment of the invention.</li>
<li><figref idref="f0001">Figure 1</figref> depicts a vehicle 100 and a device for creating a<!-- EPO <DP n="3"> --> video in the vehicle in particular for sending to a receiver. The device comprises an analyzer 110 adapted to assess a traffic situation from a captured image of the outside of the vehicle, and a multiplexer 103 adapted to code or join the captured image with recorded audio from a passenger compartment of the vehicle and information about the assessed traffic situation as the video.</li>
</ul></p>
<p id="p0015" num="0015">Passenger compartment in case of the vehicle is the inside of the vehicle. More generally the area where the driver or the passengers sit is the passenger compartment, even when the vehicle has no closed interior room.</p>
<p id="p0016" num="0016">Furthermore the device may comprise a sender 104 adapted to send the video. Alternatively the device is connectable to the sender 104.</p>
<p id="p0017" num="0017">The analyzer 110 and the multiplexer 103 are adapted to interact for joining information about the assessed traffic situation to the video, e.g. via a data link or data bus.</p>
<p id="p0018" num="0018"><figref idref="f0001">Figure 1</figref> depicts also the receiver comprising an output 109 adapted to output the video received from aforementioned device and a de-multiplexer 107 adapted to decode the video or separate the information about the assessed traffic situation from the video, to determine an assistive message from the information, and to interact with the output 109 to output the assistive message on the output 109. The output 109 for example comprises a display and speaker to output images and audio of the video respectively.</p>
<p id="p0019" num="0019">The sender 104 is adapted to connect to the receiver via a data link including in the example of <figref idref="f0001">figure 1</figref> an antenna 105 and a computer network 108. The data link for example includes a local area network (LAN), wireless local area network (WLAN, 802.11n) or wide area network (WAN). The connection is for<!-- EPO <DP n="4"> --> example according to the well known internet protocol (IP), user datagram protocol (UDP), transmission control protocol (TCP) or stream control transmission protocol (SCTP). Signaling is for example according to the well known session initiation protocol (SIP) or Internet Protocol Multimedia Subsystem (IMS). Addressing may be done using the well known uniform resource locators (URL), uniform resource identifiers (URI).</p>
<p id="p0020" num="0020">Furthermore the data link between the sender 104 and the antenna 105 is in the example according to the Long Term Evolution standard, well known as LTE.</p>
<p id="p0021" num="0021">Any other type of data link suitable to connect the sender 104 of the vehicle 100 to the receiver may be used. For example a Global System for Mobile Communications link may be used.</p>
<p id="p0022" num="0022">Furthermore the multiplexer 103 and the de-multiplexer 107 operate in the example according to the well known H.263 Codec. Any other type of video coding/decoding may be used. For example any of the well known MPEG-4 compatible video-codec may be used.</p>
<p id="p0023" num="0023">The multiplexer 103 is adapted to receive the audio from the microphone 102, the image from the camera 101 and join audio and image into the video using the codec.</p>
<p id="p0024" num="0024">To that end the camera 101 and the microphone 102 are adapted to send audio and images to the multiplexer 103 continuously while the multiplexer 103 creates the video stream.</p>
<p id="p0025" num="0025">Furthermore the multiplexer 103 is adapted to receive information about the assessed traffic situation from the analyzer 110 and add it to the video.</p>
<p id="p0026" num="0026">The analyzer 110 for example is adapted to determine the distance or the change of the distance between the vehicle 100 and other objects captured by the camera 101 in the image. For example two consecutive images from the camera 101 are compared<!-- EPO <DP n="5"> --> to decide from the size difference between the same object in both images the approximate change in distance. In an example in case the distance changes too quickly, the sentence "Heavy traffic Warning" is determined by the analyzer 110. Likewise in case an object moves from a position outside of the lane closer to a position in the lane of the vehicle 100, the sentence "Proximity Warning" is determined. The information about the assessed traffic situation is for example a text image indicating the warning as the word "Warning" or a situation dependent text explaining the reason, such as "Heavy traffic Warning" or "Proximity Warning".</p>
<p id="p0027" num="0027">Additionally or alternatively to text an audio signal playing the word "Warning" or the sentence "Heavy traffic Warning" or "Proximity Warning" may be generated as information about the assessed traffic situation by the analyzer 110.</p>
<p id="p0028" num="0028">The analyzer 110 is adapted to output the information about the assessed traffic situation to the multiplexer 103.</p>
<p id="p0029" num="0029">This way the multiplexer 103 determines a video stream from the input by the camera 101, the microphone 102 and the analyzer 110.</p>
<p id="p0030" num="0030">The recording of the audio, the capturing of the images, the assessment of the traffic situation and the joining to the video is in the example started upon detection of a request to establish a connection between the sender 104 and the receiver. For example a person in the passenger compartment of the vehicle 110 speaks a number as user input requesting a connection to the receiver. The number may be a telephone number or a short cut, like a name, mapped to a telephone number.</p>
<p id="p0031" num="0031">Likewise a Session Initiation Protocol connection request message to the sender 104 from the receiver may trigger the<!-- EPO <DP n="6"> --> start.</p>
<p id="p0032" num="0032">The sender 104 in the example is adapted to establish the data link according the Long Term Evolution standard from the sender 104 to the antenna 105 and further to the receiver upon detection of the number by the analyzer 110.</p>
<p id="p0033" num="0033">In the example this is detected by the analyzer 110 by monitoring input from the microphone 102 via speech recognition. Alternatively a keyboard may be used to dial the number as indication of the request. In the example an internet protocol connection to the receiver is set up via the Long Term Evolution link, the analyzer 110 is adapted to determine the address of the receiver according to the used data link.</p>
<p id="p0034" num="0034">Furthermore the multiplexer 103 is connected to the sender 104 and adapted to output the video to the sender 104 via the connection. The video in the example is coded using the H.263 standard. The sender 104 is adapted to send the coded video to the receiver upon receipt of the coded video, e.g. using the internet protocol address of the receiver.</p>
<p id="p0035" num="0035">The antenna 105 is connected to the receiver via the computer network 105 and adapted to forward the coded video.</p>
<p id="p0036" num="0036">The receiver is adapted to receive the coded video via an interface. In the example the interface is according to the part of the de-multiplexer 107.</p>
<p id="p0037" num="0037">Upon receipt of the video, the de-multiplexer 107 is adapted to separate the information about the assessed traffic situation from the coded video. In the example the decoder uses the H.263 standard to decode the video. For example the warning information is separated from the video. Furthermore the warning information is used to determine an assistive message.</p>
<p id="p0038" num="0038">The assistive message may comprise of text instructions to be displayed on the output 109 via the display or audio<!-- EPO <DP n="7"> --> instructions output by the speaker.</p>
<p id="p0039" num="0039">For example from the sentence "Heavy traffic Warning" it is determined that the conversation with the user at the sender 104 is to be interrupted. In this case, for example the multiplexer 107 interacts with the output 109 to display only the sentence "Heavy traffic Warning" rather than the images of the video.</p>
<p id="p0040" num="0040">Likewise the audio may be muted.</p>
<p id="p0041" num="0041">A first method for communicating is explained below making reference to <figref idref="f0002">figure 2</figref>.</p>
<p id="p0042" num="0042">The first method for example starts whenever the request to establish the connection between the sender 104 and the receiver is detected.</p>
<p id="p0043" num="0043">After the start a step 201 is executed.</p>
<p id="p0044" num="0044">In step 201 the image of the outside of the vehicle 100 is captured. Afterwards a step 202 is executed.</p>
<p id="p0045" num="0045">In step 202 the audio of the passenger compartment of the vehicle 100 is recorded.</p>
<p id="p0046" num="0046">Steps 201 and 202 may be performed simultaneously.</p>
<p id="p0047" num="0047">Afterwards a step 203 is executed.</p>
<p id="p0048" num="0048">In step 203 the traffic situation is assessed from the captured image. For example the change of the distance between the vehicle 100 and an object is determined from two consecutively captured images. This means that the traffic situation is assessed from a captured image of the outside of the vehicle. The assessment is for example stored as text "Heavy traffic Warning" in a variable. Afterwards a step 204 is executed.</p>
<p id="p0049" num="0049">In step 204 the information on about the assessed traffic<!-- EPO <DP n="8"> --> situation is determined for example from the variable. The information is determined for example from the variable containing the sentence "Heavy traffic Warning" as the equivalent text image or audio. In case no warning is determined, the information about the assessed traffic situation is for example "normal". Afterwards a step 205 is executed.</p>
<p id="p0050" num="0050">In step 205 the captured image, the recorded audio and the information about the assessed traffic situation are joined to the video. This means that the captured image is joined with recorded audio from the passenger compartment of the vehicle and information about the assessed traffic situation as the video. The video may be compressed or coded as well. For example the video is compressed or coded according to the H.263 standard. This means that several captured images, recorded audio are joined with the information about the assessed traffic situation.</p>
<p id="p0051" num="0051">Afterwards a step 206 is executed.</p>
<p id="p0052" num="0052">In step 206 the video signal or the coded video signal is sent.</p>
<p id="p0053" num="0053">Afterwards a step 207 is executed.</p>
<p id="p0054" num="0054">In the step 207 a test is performed to determine whether the connection between the sender 104 and the receiver is active, or whether at least one of the devices is switched off. In case the connection is active, the step 201 is executed. Otherwise the first method ends.</p>
<p id="p0055" num="0055">The vehicle 100 for example has the aforementioned device integrated permanently. Permanently means that once mounted, the individual parts are fixed as part of the vehicle. Instead of permanently mounting the parts to the vehicle, the device may be integrated into a single housing, e.g. a smart phone. In<!-- EPO <DP n="9"> --> this case the mounting may be via a special bracket or clamp that guarantees the mounting position while the smart phone is mounted. The system according to another embodiment comprises of the same devices. However in this other embodiment, the analyzer 110 or the multiplexer 107 are not in the vehicle 100 but in the network, e.g. as part of a computing cloud.</p>
<p id="p0056" num="0056">In this case the steps of the first method are for example executed in the same order however on the respective device. To that end additional steps of sending the audio, the images or the information are performed before the step of joining (205).</p>
<p id="p0057" num="0057">A second method for playing the video is explained below making reference to <figref idref="f0003">figure 3</figref>.</p>
<p id="p0058" num="0058">The second method for example starts whenever reception of the video starts at the receiver.</p>
<p id="p0059" num="0059">After the start a step 301 is executed.</p>
<p id="p0060" num="0060">In the step 301 the information about the assessed traffic situation is separated from the video. In the example the received video is decoded according to the H.263 standard and the text or audio containing the information about the assessed traffic situation is separated from the image or audio. For example a variable is set to the text "Heavy traffic Warning". In case the information about the assessed traffic situation is indicating "normal", in the video, the variable is set to "normal".</p>
<p id="p0061" num="0061">Afterwards a step 302 is executed.</p>
<p id="p0062" num="0062">In step 302 a test is performed to determine whether the information about the assessed traffic situation indicates "normal". In case the information indicates "normal" a step 305 is executed. Otherwise a step 303 is executed. For example in case the variable contains the text "normal" the step 305 is executed. This means that it is determined whether to send an assistive<!-- EPO <DP n="10"> --> message to the output 109 or not depending on the information about the assessed traffic situation.</p>
<p id="p0063" num="0063">In step 303 an assistive message is determined from the information. In the example of the message "Heavy traffic Warning" for example an assistive message corresponding to a request to mute is created. This is for example a text "please mute audio" or a respective symbol is used This means that the assistive message is determined from the information about the assessed traffic situation. Afterwards a step 304 is executed.</p>
<p id="p0064" num="0064">In step 304 the assistive message is output. For example the text "please mute audio" or the symbol is displayed on the display. Optionally or alternatively a corresponding audio signal may be played. Afterwards the method ends.</p>
<p id="p0065" num="0065">Step 304 may be repeated before the end of the second method for one or several times until the connection is ended.</p>
<p id="p0066" num="0066">In step 305 the video is output without the information about the assessed traffic situation. The image is for example displayed on the display and the audio played via the speaker.</p>
<p id="p0067" num="0067">Afterwards step 301 is executed.</p>
<p id="p0068" num="0068">Preferably in the implementation of the device the vehicle receiver or the methods described above, the information about the traffic situation, the image of the video or the audio of the video coincide with one or more of the other.</p>
<p id="p0069" num="0069">Preferably in the implementation of the device the vehicle receiver or the methods described above the image of the video, the audio of the video or the video are live image, live audio or live video respectively.</p>
<p id="p0070" num="0070">The description and drawings merely illustrate the principles of the invention. It will thus be appreciated that those skilled in the art will be able to devise various arrangements<!-- EPO <DP n="11"> --> that, although not explicitly described or shown herein, embody the principles of the invention and are included within its spirit and scope. Furthermore, all examples recited herein are principally intended expressly to be only for pedagogical purposes to aid the reader in understanding the principles of the invention and the concepts contributed by the inventors to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions. Moreover, all statements herein reciting principles, aspects, and embodiments of the invention, as well as specific examples thereof, are intended to encompass equivalents thereof.</p>
<p id="p0071" num="0071">The functions of the various elements shown in the figures, including any functional blocks labeled as multiplexer, de-multiplexer, sender, receiver or analyzer, may be provided through the use of dedicated hardware as well as hardware capable of executing software in association with appropriate software. When provided by a processor, the functions may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared. Moreover, explicit use of the term 'processor' or 'controller' should not be construed to refer exclusively to hardware capable of executing software, and may implicitly include, without limitation, digital signal processor (DSP) hardware, network processor, application specific integrated circuit (ASIC), field programmable gate array (FPGA), read only memory (ROM) for storing software, random access memory (RAM), and non volatile storage. Other hardware, conventional and/or custom, may also be included. Similarly, any switches shown in the figures are conceptual only. Their function may be carried out through the operation of program logic, through dedicated logic, through the<!-- EPO <DP n="12"> --> interaction of program control and dedicated logic, or even manually, the particular technique being selectable by the implementer as more specifically understood from the context.</p>
<p id="p0072" num="0072">It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative circuitry embodying the principles of the invention. Similarly, it will be appreciated that the flow charts represent various processes which may be substantially represented in computer readable medium and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.</p>
<p id="p0073" num="0073">A person of skill in the art would readily recognize that steps of various above-described methods can be performed by programmed computers. Herein, some embodiments are also intended to cover program storage devices, e.g., digital data storage media, which are machine or computer readable and encode machine-executable or computer-executable programs of instructions, wherein said instructions perform some or all of the steps of said above-described methods. The program storage devices may be, e.g., digital memories, magnetic storage media such as a magnetic disks and magnetic tapes, hard drives, or optically readable digital data storage media. The embodiments are also intended to cover computers programmed to perform said steps of the above-described methods.</p>
</description>
<claims id="claims01" lang="en"><!-- EPO <DP n="13"> -->
<claim id="c-en-0001" num="0001">
<claim-text>A first device (110, 103) comprising an analyzer (110) adapted to assess (203) a traffic situation from a captured image of the outside of a vehicle (100) and a sender (104) adapted to send (206) information about the assessed traffic situation.</claim-text></claim>
<claim id="c-en-0002" num="0002">
<claim-text>The device (110, 103) according to claim 1, comprising a multiplexer (103) adapted to join (205) the captured image with recorded audio from a passenger compartment of the vehicle (100).</claim-text></claim>
<claim id="c-en-0003" num="0003">
<claim-text>The device (110, 103) according to claim 1 or 2, a microphone (102) for recording (202) audio of the passenger compartment of the vehicle (100).</claim-text></claim>
<claim id="c-en-0004" num="0004">
<claim-text>The device (110, 103) according to claim 1 to 3, comprising a camera (101) for capturing (201) the image of the outside of the vehicle (100).</claim-text></claim>
<claim id="c-en-0005" num="0005">
<claim-text>A vehicle (100) comprising a device (101, 102, 103) according to any of the aforementioned claims.</claim-text></claim>
<claim id="c-en-0006" num="0006">
<claim-text>A second device comprising a receiver (105) and an output (109), wherein the receiver (105) is adapted to receive information about an assessed traffic situation and adapted to determine whether to send an assistive message to the output (109) or not depending on the information about the assessed traffic situation.</claim-text></claim>
<claim id="c-en-0007" num="0007">
<claim-text>The device according to claim 6, wherein the assistive message is determined from the information about the assessed traffic situation.</claim-text></claim>
<claim id="c-en-0008" num="0008">
<claim-text>A method comprising assessing (203) a traffic situation from a captured image of the outside of a vehicle (100),<!-- EPO <DP n="14"> --> and sending (206)the information about the assessed traffic situation.</claim-text></claim>
<claim id="c-en-0009" num="0009">
<claim-text>The method according to claim 8, comprising joining (205) the captured image with recorded audio from a passenger compartment of the vehicle (100) and information about the assessed traffic situation.</claim-text></claim>
<claim id="c-en-0010" num="0010">
<claim-text>The method according to claim 8 or 9, comprising capturing (201) the image of the outside of the vehicle (100).</claim-text></claim>
<claim id="c-en-0011" num="0011">
<claim-text>The method to claims 8 to 9, comprising recording (202) the audio of the passenger compartment of the vehicle (100).</claim-text></claim>
<claim id="c-en-0012" num="0012">
<claim-text>A method comprising receiving information about a assessed traffic situation, and determining whether to send an assistive message or not depending on the information about the assessed traffic situation.</claim-text></claim>
<claim id="c-en-0013" num="0013">
<claim-text>The method according to claim 12, wherein the assistive message is determined depending on the received assessed traffic situation.</claim-text></claim>
<claim id="c-en-0014" num="0014">
<claim-text>The device (110, 103) according to claims 1 to 4, the vehicle (100) according to claim 5, the receiver (107, 109) according to claims 6 and 7, or the method according to claims 8 to 13, wherein the information about the traffic situation, the image or the audio of coincide with one or more of the other.</claim-text></claim>
<claim id="c-en-0015" num="0015">
<claim-text>The device (110, 103) according to claims 1 to 4, the vehicle (100) according to claim 5, the receiver (107, 109) according to claims 6 and 7, or the method according to claims 8 to 13, wherein the image or the audio are live image or live audio respectively.</claim-text></claim>
</claims>
<drawings id="draw" lang="en"><!-- EPO <DP n="15"> -->
<figure id="f0001" num="1"><img id="if0001" file="imgf0001.tif" wi="165" he="191" img-content="drawing" img-format="tif"/></figure><!-- EPO <DP n="16"> -->
<figure id="f0002" num="2"><img id="if0002" file="imgf0002.tif" wi="165" he="99" img-content="drawing" img-format="tif"/></figure><!-- EPO <DP n="17"> -->
<figure id="f0003" num="3"><img id="if0003" file="imgf0003.tif" wi="165" he="170" 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="161" he="233" type="tif"/><doc-page id="srep0002" file="srep0002.tif" wi="160" he="233" type="tif"/></search-report-data><search-report-data date-produced="20131011" 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>812287</file-reference-id><application-reference><document-id><country>EP</country><doc-number>13305148.2</doc-number></document-id></application-reference><applicant-name><name>Alcatel Lucent</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>DH</text></addressbook></srep-office><date-search-report-mailed><date>20131018</date></date-search-report-mailed></srep-info-admin></srep-info><srep-for-pub><srep-fields-searched><minimum-documentation><classifications-ipcr><classification-ipcr><text>G08G</text></classification-ipcr></classifications-ipcr></minimum-documentation></srep-fields-searched><srep-citations><citation id="sr-cit0001"><patcit dnum="US2009207007A1" id="sr-pcit0001" url="http://v3.espacenet.com/textdoc?DB=EPODOC&amp;IDX=US2009207007&amp;CY=ep"><document-id><country>US</country><doc-number>2009207007</doc-number><kind>A1</kind><name>FLICK BERND [DE] ET AL</name><date>20090820</date></document-id></patcit><category>X</category><rel-claims>1-15</rel-claims><rel-passage><passage>* paragraph [0008]; figure 1 *</passage></rel-passage></citation><citation id="sr-cit0002"><patcit dnum="US2002115423A1" id="sr-pcit0002" url="http://v3.espacenet.com/textdoc?DB=EPODOC&amp;IDX=US2002115423&amp;CY=ep"><document-id><country>US</country><doc-number>2002115423</doc-number><kind>A1</kind><name>HATAE YASUHIKO [JP] ET AL</name><date>20020822</date></document-id></patcit><category>X</category><rel-claims>1-15</rel-claims><rel-passage><passage>* paragraphs [0014],  [0019],  [0022]; figures 4,5 *</passage></rel-passage></citation><citation id="sr-cit0003"><patcit dnum="EP2463842A2" id="sr-pcit0003" url="http://v3.espacenet.com/textdoc?DB=EPODOC&amp;IDX=EP2463842&amp;CY=ep"><document-id><country>EP</country><doc-number>2463842</doc-number><kind>A2</kind><name>SCANIA CV AB [SE]</name><date>20120613</date></document-id></patcit><category>A</category><rel-claims>1-15</rel-claims><rel-passage><passage>* paragraph [0016] *</passage></rel-passage></citation><citation id="sr-cit0004"><patcit dnum="FR2887064A1" id="sr-pcit0004" url="http://v3.espacenet.com/textdoc?DB=EPODOC&amp;IDX=FR2887064&amp;CY=ep"><document-id><country>FR</country><doc-number>2887064</doc-number><kind>A1</kind><name>PEUGEOT CITROEN AUTOMOBILES SA [FR]</name><date>20061215</date></document-id></patcit><category>A</category><rel-claims>1-15</rel-claims><rel-passage><passage>* the whole document *</passage></rel-passage></citation><citation id="sr-cit0005"><patcit dnum="US2006257024A1" id="sr-pcit0005" url="http://v3.espacenet.com/textdoc?DB=EPODOC&amp;IDX=US2006257024&amp;CY=ep"><document-id><country>US</country><doc-number>2006257024</doc-number><kind>A1</kind><name>HAHN WOLFGANG [DE] ET AL</name><date>20061116</date></document-id></patcit><category>A</category><rel-claims>1-15</rel-claims><rel-passage><passage>* paragraphs [0037],  [0041] *</passage></rel-passage></citation><citation id="sr-cit0006"><patcit dnum="JP2009214838A" id="sr-pcit0006" url="http://v3.espacenet.com/textdoc?DB=EPODOC&amp;IDX=JP2009214838&amp;CY=ep"><document-id><country>JP</country><doc-number>2009214838</doc-number><kind>A</kind><name>FUJI HEAVY IND LTD</name><date>20090924</date></document-id></patcit><category>A</category><rel-claims>1-15</rel-claims><rel-passage><passage>* abstract *</passage></rel-passage></citation></srep-citations><srep-admin><examiners><primary-examiner><name>Créchet, Patrick</name></primary-examiner></examiners><srep-office><addressbook><text>The Hague</text></addressbook></srep-office><date-search-completed><date>20131011</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>US</country><doc-number>2009207007</doc-number><kind>A1</kind><date>20090820</date></document-id></priority-application><family-member><document-id><country>AT</country><doc-number>445212</doc-number><kind>T</kind><date>20091015</date></document-id></family-member><family-member><document-id><country>AU</country><doc-number>2005318322</doc-number><kind>A1</kind><date>20060629</date></document-id></family-member><family-member><document-id><country>CN</country><doc-number>101084533</doc-number><kind>A</kind><date>20071205</date></document-id></family-member><family-member><document-id><country>DE</country><doc-number>102004061399</doc-number><kind>A1</kind><date>20060706</date></document-id></family-member><family-member><document-id><country>EP</country><doc-number>1831854</doc-number><kind>A1</kind><date>20070912</date></document-id></family-member><family-member><document-id><country>ES</country><doc-number>2333894</doc-number><kind>T3</kind><date>20100302</date></document-id></family-member><family-member><document-id><country>JP</country><doc-number>2008524733</doc-number><kind>A</kind><date>20080710</date></document-id></family-member><family-member><document-id><country>KR</country><doc-number>20070086433</doc-number><kind>A</kind><date>20070827</date></document-id></family-member><family-member><document-id><country>US</country><doc-number>2009207007</doc-number><kind>A1</kind><date>20090820</date></document-id></family-member><family-member><document-id><country>WO</country><doc-number>2006067008</doc-number><kind>A1</kind><date>20060629</date></document-id></family-member></patent-family><patent-family><priority-application><document-id><country>US</country><doc-number>2002115423</doc-number><kind>A1</kind><date>20020822</date></document-id></priority-application><family-member><document-id><country>EP</country><doc-number>1233387</doc-number><kind>A2</kind><date>20020821</date></document-id></family-member><family-member><document-id><country>US</country><doc-number>2002115423</doc-number><kind>A1</kind><date>20020822</date></document-id></family-member></patent-family><patent-family><priority-application><document-id><country>EP</country><doc-number>2463842</doc-number><kind>A2</kind><date>20120613</date></document-id></priority-application><family-member><document-id><country>EP</country><doc-number>2463842</doc-number><kind>A2</kind><date>20120613</date></document-id></family-member><family-member><document-id><country>SE</country><doc-number>1051311</doc-number><kind>A1</kind><date>20120614</date></document-id></family-member></patent-family><patent-family><priority-application><document-id><country>FR</country><doc-number>2887064</doc-number><kind>A1</kind><date>20061215</date></document-id></priority-application><text>NONE</text></patent-family><patent-family><priority-application><document-id><country>US</country><doc-number>2006257024</doc-number><kind>A1</kind><date>20061116</date></document-id></priority-application><family-member><document-id><country>CN</country><doc-number>1867954</doc-number><kind>A</kind><date>20061122</date></document-id></family-member><family-member><document-id><country>DE</country><doc-number>10348109</doc-number><kind>A1</kind><date>20050519</date></document-id></family-member><family-member><document-id><country>EP</country><doc-number>1673751</doc-number><kind>A1</kind><date>20060628</date></document-id></family-member><family-member><document-id><country>ES</country><doc-number>2280049</doc-number><kind>T3</kind><date>20070901</date></document-id></family-member><family-member><document-id><country>JP</country><doc-number>4512595</doc-number><kind>B2</kind><date>20100728</date></document-id></family-member><family-member><document-id><country>JP</country><doc-number>2007515853</doc-number><kind>A</kind><date>20070614</date></document-id></family-member><family-member><document-id><country>US</country><doc-number>2006257024</doc-number><kind>A1</kind><date>20061116</date></document-id></family-member><family-member><document-id><country>WO</country><doc-number>2005038743</doc-number><kind>A1</kind><date>20050428</date></document-id></family-member></patent-family><patent-family><priority-application><document-id><country>JP</country><doc-number>2009214838</doc-number><kind>A</kind><date>20090924</date></document-id></priority-application><family-member><document-id><country>JP</country><doc-number>5185663</doc-number><kind>B2</kind><date>20130417</date></document-id></family-member><family-member><document-id><country>JP</country><doc-number>2009214838</doc-number><kind>A</kind><date>20090924</date></document-id></family-member></patent-family></srep-patent-family></srep-for-pub></search-report-data>
</ep-patent-document>
