FORM 2
THE PATENTS ACT 1970
[39 OF 1970]
&
THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
[See section 10; Rule 13]
TITLE: “METHOD AND SYSTEM FOR ACCESSING AT LEAST ONE VIDEO
FROM A VEHICLE ”
Name and Address of the Applicant: TATA MOTORS LIMITED,
Bombay House, 24 Homi Mody Street, Hutatma Chowk, Mumbai 400 001, Maharashtra Nationality: Indian
The following Specification particularly describes the new or original invention and the complete manner in which it is to be performed.

TECHNICAL FIELD
[0001] The present disclosure relates, in general, to automobiles and more particularly, the present disclosure relates to a telematics control unit (TCU) for accessing video data from a vehicle.
BACKGROUND
[0002] Driver monitoring is a means of evaluating driving performance in order to establish a driver’s risk level. Fleet owners and insurance firms frequently employ driver monitoring system (DMS) to assign a risk rating to a driver, which is then used to calculate the driver’s insurance rate, etc. The DMS is an automobile safety system mounted on a vehicle that evaluates the driver’s awareness and if necessary, warns the driver about lapse in attention. If the driver fails to pay attention to the road ahead and a possible risky scenario is recognized, the DMS alerts the driver and also records a video to capture the risky scenario as evidence.
[0003] The DMS has been used as Driver drowsiness and distraction alert system to capture and store driver distraction and drowsiness videos that can be accessed and streamed if required by the fleet owner of the vehicles. Traditional DMS has a modem and a separate SIM card for streaming the evidence videos directly on a client device of the fleet owner, which leads to increase in the cost of the DMS.
[0004] Presently, every vehicle has a Telematics Control Unit (TCU) embedded in the vehicle. The TCU contains a cellular modem that provides connectivity to the TCU with the insertion slot for a SIM card. The TCU is an integrated onboard system that manages wireless tracking, diagnostics, and communication to and from the vehicle. The TCU is also utilized in accident notification, digital tolling, vehicle tracking, and among other applications. Therefore, a vehicle having DMS and TCU shall essentially comprise two SIM cards, which adds on to the cost of the vehicle.
[0005] In view of the above, there exists a need to provide a device/apparatus and method which overcomes the above-mentioned problems of the additional cost by eliminating the extra modem and SIM card.

[0006] The information disclosed in this background of the disclosure section is only for enhancement of understanding of the general background of the invention and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.
SUMMARY
[0007] The present disclosure overcomes one or more shortcomings of the prior art and provides additional advantages discussed throughout the present disclosure. Additional features and advantages are realized through the techniques of the present disclosure. Other aspects and aspects of the disclosure are described in detail herein.
[0008] In an aspect of the present disclosure, a Telematic Control Unit (TCU) for accessing at least one video from a vehicle is disclosed. The TCU comprises a memory, a communication module comprising a sim card module, a wireless fidelity (Wi-Fi) module, and a controller area network (CAN) transceiver. Further, the TCU also comprises at least one controller in communication with the memory, the communication module, the Wi-Fi module and the CAN transceiver. The at least one controller is configured to receive, via the communication module, a request for video streaming from a user. The at least one controller is also configured to transmit, via the CAN transceiver, the request to a driver monitoring system (DMS) through a CAN communication channel. Further, the at least one controller is configured to receive, via the Wi-Fi module, at least video from the DMS through a Wi-Fi channel. Lastly, the at least one controller is also configured to transmit, via the communication module, the at least one video to the video server to stream the at least one video on a user device.
[0009] In an aspect of the present disclosure, the TCU receives the at least one video from the DMS such that in order to receive the video, the at least one controller is configured to receive, via the CAN transceiver, a request to send (RTS) signal from the DMS through the CAN communication channel. In response, the at least one controller is configured to transmit, via the CAN transceiver, a clear to send (CTS) signal to the DMS over the CAN communication channel. The CTS signal indicates to the DMS to transmit the at least one video over the Wi-Fi channel.

[0010] In an aspect of the present disclosure, the at least one controller is configured to transmit, the at least one video to the server based on a secure file over transfer protocol (SFTP).
[0011] In an aspect of the present disclosure, the TCU is configured such that the at least one video is streamed from the DMS to the server using real time transfer message protocol streaming (RTMPS).
[0012] In an aspect of the present disclosure, the at least one video includes a pre-stored video or a real-time video.
[0013] In another aspect, a method for accessing at least one video data from a vehicle is disclosed. The method being performed at a telematic control unit (TCU). The method comprises receiving a request for video streaming from a user and transmitting the request to a driver monitoring system (DMS) through a controller area network (CAN) communication channel. The method further comprises receiving at least one video from the DMS through a wireless fidelity (Wi-Fi) channel and transmitting the at least one video to a server for streaming the at least one video on a user device.
[0014] In an aspect of the present disclosure, the method further involves receiving, the at least one video from the DMS through a wireless fidelity (Wi-Fi) channel wherein the receiving of the at least one video comprises receiving a request to send (RTS) signal from the DMS through the CAN communication channel. Further, the receiving of the at least one video also involves transmitting a clear to send (CTS) signal to the DMS over the CAN communication channel, wherein the CTS signal indicates to the DMS to transmit the at least one video over the Wi-Fi channel.
[0015] In an aspect of the present disclosure, the method also includes transmitting, by the TCU, the at least one video to the server wherein the at least one video is transmitted to the server based on a secure file over transfer protocol (SFTP).
[0016] The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, aspects, and features described above, further aspects, aspects, and features will become apparent by reference to the drawings and the following detailed description.

BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS
[0017] The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary aspects and, together with the description, explain the disclosed principles. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the figures to reference features and components. Some aspects of system and/or methods in accordance with aspects of the present subject matter are now described, by way of example only, and regarding the accompanying figures, in which:
[0012] FIG. 1 illustrates an example representation of an environment for accessing video from a vehicle, in accordance with some aspects of the present disclosure;
[0013] FIG. 2 shows a block diagram of a Telematics Control Unit (TCU) for accessing at least one video from a vehicle, in accordance with some aspects of the present disclosure;
[0014] FIG. 3A illustrates a signal diagram for accessing a video from a driver monitoring system (DMS) present in a vehicle, in accordance with some aspects of the present disclosure;
[0015] FIG. 3B illustrates a signal diagram for streaming a real time video being captured by a driver monitoring system (DMS) present in a vehicle, in accordance with some aspects of the present disclosure; and
[0016] FIG. 4 shows a flowchart illustrating a method performed by a telematic control unit (TCU) for accessing at least one video data from a vehicle, in accordance with some aspects of the present disclosure.
[0017] It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and executed by a computer or processor, whether such computer or processor is explicitly shown.
DETAILED DESCRIPTION

[0018] In the present document, the word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect or implementation of the present subject matter described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.
[0019] While the disclosure is susceptible to various modifications and alternative forms, specific aspect thereof has been shown by way of example in the drawings and will be described in detail below. It should be understood, however that it is not intended to limit the disclosure to the specific forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternative falling within the scope of the disclosure.
[0020] The terms “comprises”, “comprising”, “includes”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device, or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus proceeded by “comprises… a” does not, without more constraints, preclude the existence of other elements or additional elements in the system or method.
[0021] In the following detailed description of the aspects of the disclosure, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific aspects in which the disclosure may be practiced. These aspects are described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other aspects may be utilized and that changes may be made without departing from the scope of the present disclosure. The following description is, therefore, not to be taken in a limiting sense.
[0022] The term ‘vehicle’ as used herein refers to passenger vehicles or commercial vehicles such as, but not limited to, cars, buses, trucks, and the like.
[0023] The term “video”, “at least one video”, “video data” and “at least one video data” have same meaning and have been alternatively used throughout the specification.
[0024] The term “server” and “video server” have same meaning and have been alternatively used throughout the specification.

[0025] The term “CVP” and “cloud vehicle platform” have same meaning and have been alternatively used throughout the specification.
[0026] The term “Driver Monitoring System” and “DMS” have same meaning and have been alternatively used throughout the specification.
[0027] The term “client device” and “user device” have same meaning and have been alternatively used throughout the specification.
[0028] The term “client” and “user” have same meaning and have been alternatively used throughout the specification.
[0029] The term “client application” and “application” have same meaning and have been alternatively used throughout the specification
[0030] FIG. 1 illustrates an example representation of an environment 100 for accessing video from a vehicle 101, in accordance with some aspects of the present disclosure.
[0031] In an aspect of the present disclosure, the environment 100 includes a vehicle 101 driven by a driver. The vehicle 101 may comprise a Telematic Control Unit (TCU) 102, a driver monitoring system (DMS) 103, and one or more cameras or image sensors 104 connected to the DMS 103. The DMS 103 may be configured to detect one or more events and capture a plurality of videos. The one or more events may comprise scenarios such as drowsiness and distraction of driver, over speeding of vehicle, sudden shock, etc. However, the one or more events are not limited to the above example, and any other scenarios that needs to be monitored by the DMS 103 is well within the scope of the present disclosure. The DMS 103 may comprise one or more processors communicatively coupled with one or more sensors of the vehicle including the image sensors/cameras 104 to determine occurrence of one or more events. In one non-limiting aspect, determination of drowsiness and distraction of driver may be carried out by applying any image processing technique known to a person skilled in the art. In another non-limiting aspect, the detection of drowsiness and distraction may also be done by monitoring body vitals of the driver of the vehicle. However, the techniques for detection of drowsiness and distraction of the driver are not limited to above example and any other technique known for such determination is well within the scope of present disclosure.

[0032] The environment 100 further includes a cloud vehicle platform 105 and a video server 108. The cloud vehicle platform 105 is a network of vehicles through which one or more communications are pushed towards the vehicle 101. The cloud vehicle platform 105 may be in communications with a plurality of vehicles at the same time. The video server 108 may be used for storing the videos of the vehicle and may also be used to stream videos on the client device 106.
[0033] In one non-limiting aspect, the cloud vehicle platform 105 and the video server 108 may form a single server. The environment 100 further includes a client device 106 being operated by a client 109 for streaming videos of the vehicle 101. The videos may be streamed on an application installed on the client device 106. In another aspect, the client 106 may be the driver of the vehicle who requests the video from the DMS. In one non-limiting aspect, the client device 106 may include a smartphone, tablet computing device, desktop computer, laptop, or like.
[0034] The client device may generate a video streaming request to access video data from the DMS 103. In one non-limiting aspect, the video streaming request includes a request to stream real time video or a pre-stored video. The client device 106 sends video streaming request to the CVP 105 through internet. Further, the CVP 105 may transmit the video streaming request to the TCU 102 of the vehicle 101. The TCU 102 of the vehicle is communicatively coupled with the CVP 105 and may receive the video streaming request from the CVP 105.
[0035] In an aspect of the present disclosure, the TCU 102 may first establish a Controller area Network (CAN) communication channel with the DMS 103 and send the video streaming request to access the video data of the DMS 103. The TCU 102 is configured to communicate the video streaming request to the DMS 103 via CAN protocol. In one non-limiting aspect. the DMS 103 may comprise a local memory for storing the one or more videos data captured by the one or more image sensors 104.
[0036] The DMS 103 may receive the video streaming request and may retrieve the desired video requested by the client device 106. In one non-limiting aspect, the video data may be retrieved from the local memory of the DMS 103. In another non-limiting aspect, the video data may be real time video being captured by the one or more image sensors of the vehicle.
[0037] The DMS 103 may transmit the requested video data to the TCU 102 over a wireless fidelity (Wi-Fi) channel. The Wi-Fi channel may be established before the transmission of the

video data to the TCU 102. Upon completion of the transmission of the video data, the DMS 103 may delete the shared video data from the local memory. In one non-limiting aspect, the TCU 102 may inform the successful transmission for the DMS 103 to delete the transmitted video. The TCU 102 will inform the Cloud Vehicle Platform 105 of the video data available for sending to the client 109 and the TCU 102 shall send the video data of the driver to the video server 108. The video server 108 may make the video data available for viewing on the client device 106 via the client application.
[0038] FIG. 2 shows a block diagram of a Telematics Control Unit (TCU) 102 for accessing at least one video from a vehicle, in accordance with some aspects of the present disclosure.
[0039] The TCU 102 may include at least one controller 206, a memory 207, a Control Area Network (CAN) transceiver 204, a wireless fidelity (Wi-fi) module 205 and a communication module 201 in communication with each other. However, the TCU 102 is not limited to above hardware components and may comprise any other component for various other functions known to a person skilled in the art
[0040] In one non-limiting aspect, the communication module 201 may comprise a SIM card module 210. The SIM card module 210 further comprises a modem 202 and a SIM card 203. The SIM card module 210 may be configured to connect the TCU 102 with one or more external components over internet. The communication module 201 may be configured to send and receive data via the internet connection established by the SIM card module 210. The communication module 201 is not limited to above components, and any other components providing internet connection in a vehicle is well within the scope of the present disclosure.
[0041] The CAN transceiver 204 may be coupled to the DMS 103 through a CAN bus. The CAN transceiver 204 may be configured to exchange one or more commands to and from the DMS 103 via a CAN communication channel. The at least one Wi-Fi module 205 is used to establish a Wi-Fi channel between the TCU 102 and the DMS 103. The Wi-Fi module may be configured by the at least one controller 206 to send and receive video data through the Wi-Fi channel.
[0042] In an aspect of the present disclosure, the at least one controller 206 may be configured to receive a request for video streaming from a user. The user may be a fleet owner or the owner of the vehicle. The request for video streaming may be generated from the client device of the

user and may be communicated to the TCU 102 via the CVP platform 105, as discussed in the above aspect.
[0043] In one non-limiting aspect, the request for video streaming includes a request to stream real time video or a pre-stored video, which is discussed in further detail in the explanation of the fig. 3A and 3B in below aspect. In case the request relates to prestored video, the request may also comprise a time stamp of the prestored video. The at least one controller 105 may also be configured to establish a CAN connection with the DMS 103 via the CAN transceiver 204 to transmit the request to the DMS 103. The DMS 103 may process the request and retrieve the requested video from the local memory as discussed in above aspect.
[0044] To transmit the requested video, the DMS may first establish a Wi-Fi channel between the DMS 103 and the TCU 102. The at least one controller 206 may then be configured to receive, via the CAN transceiver (204), a request to send (RTS) signal from the DMS 103 through the CAN communication channel. The RTS signal may be received from the DMS 103. The at least one controller 206 may check the channel for possible collisions and transmit a clear to send (CTS) signal to the DMS 103 over the CAN communication channel. The CTS signal may indicate the DMS 103 to transmit the at least one video data over the Wi-Fi channel. On the receipt of the CTS signal, the DMS may transmit the requested video to the TCU 102. The at least one controller 206 may be configured to receive video from the DMS 103 through the Wi-Fi module 205.
[0045] In an aspect of the present disclosure, the at least one controller 206 may be then configured to transmit the at least one video to a server to stream the at least one video data on a user device. In one non-limiting aspect, the at least one controller 206 may be configured to transmit the at least one video data to the server based on a secure file over transfer protocol (SFTP) to ensure the video data security.
[0046] In case of real time video request from the user, the video data is streamed from the DMS 103 to the server 108 using real time transfer message protocol streaming (RTMPS). However, the video data streaming is not limited to above protocol and any other protocol used for real time streaming of video data is well within the scope of the present disclosure.
[0047] Thus, the TCU unit 102 facilitates secure connection between DMS 103 and TCU 102 over the Wi-Fi channel instead of implementing the additional SIM card and modem in DMS

103. Thus, the TCU unit 102 facilitates access to a video from a vehicle/DMS, thereby avoiding the additional cost incurred by the additional SIM or modem of the DMS 103.
[0048] In one aspect, the at least one controller 206 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and one or more single core processors. For example, the at least one controller 206 may be embodied as one or more of various processing devices, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing circuitry with or without an accompanying DSP, or various other processing devices including, a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like.
[0049] In one aspect, the memory 207 is capable of storing machine executable instructions. In an aspect, the at least one controller 206 is embodied as an executor of software instructions. As such, the at least one controller 206 is capable of executing the instructions stored in the memory 207 to perform one or more operations described herein. The memory 207 is also capable of storing video for sending to a video server 108. The memory 207 can be any type of storage accessible to the at least one controller 206 to perform respective functionalities. For example, the memory 207 may include one or more volatile or non-volatile memories, or a combination thereof. For example, the memory 207 may be embodied as semiconductor memory, such as flash memory, mask ROM, PROM (programmable ROM), EPROM (erasable PROM), RAM (random access memory), etc. and the like.
[0050] FIG. 3A illustrates a signal diagram 300a for accessing a video from a driver monitoring system (DMS) present in a vehicle, in accordance with some aspects of the present disclosure.
[0018] As shown in Fig 3A, the client device 106 sends a request for accessing a video to a Cloud Vehicle Platform 105 (as shown by step S1). The request may relate to accessing a pre¬recorded video data stored on the local memory of the DMS 103 and the request may comprise details for identifying the video data, such as label or time stamp of the video. In one non-limiting aspect, the communication between the client device 106 and the Cloud Vehicle Platform 105 can take place over an internet connection. Upon receipt of the request to access the video, the Cloud Vehicle Platform 105 may forward the request to the TCU 102 of the vehicle 101 (as shown by step S2). The TCU 102 of the vehicle may communicate with the Cloud Vehicle Platform 105 via the communication module 201, as discussed in above aspects.

[0051] In response to the receipt of the request to access the video, the TCU 102 may first establish a CAN communication channel with the DMS 103 and may send a request via the CAN communication channel to the DMS 103 (as shown by step S3). Upon receiving the request, the DMS 103 may send a communication to the TCU 102 via the CAN communication channel to indicate that the DMS 103 is ready to send the video specified in the request over the Wi-Fi channel (as shown by step S4). In response, the TCU 102 verifies whether the Wi-Fi channel is not communicating with other components of the vehicle and the Wi-Fi channel is clear for receiving the video. The TCU 102 then sends a clear to send communication via the CAN communication channel to the DMS 103 to indicate that the TCU 102 is ready to receive the requested video from the DMS 103 over the Wi-Fi channel (as shown by step S5). The TCU 102 may also send a reject request communication to the DMS 103 if the Wi-Fi channel of the TCU 102 is not available (as shown by step S5’).
[0052] In response to the receipt of the clear to send communication from the TCU 102, the DMS 103 sends the requested video to the TCU 102 over the Wi-Fi channel (as shown by step S6). Upon completion of sending, the DMS 103 may delete the video from its local memory to free-up space in the local memory of the DMS 103. In one non-limiting aspect, the TCU 102 may inform the successful transmission for the DMS 103 to delete the transmitted video. Upon receipt of the video, the TCU 102 will check the signal strength to ensure that the TCU 102 has sufficient internet connection to send the video.
[0053] The TCU 102 sends a video upload request to the Cloud Vehicle Platform 105 for establishing a connection with the Video Server 108 via internet connection (as shown in step S7). Upon successful connection establishment, the TCU 102 sends the video to the video server 108 via internet connection (as shown by step S7). In a non-limiting aspect, the TCU 102 transmits the at least one video to the video server 108 based on a secure file over transfer protocol (SFTP). Lastly, the video server 108 sends the video to the client device for viewing (as shown by step S9).
[0054] FIG. 3B illustrates a signal diagram 300 b for streaming a real time video being captured by a driver monitoring system (DMS) present in a vehicle, in accordance with some aspects of the present disclosure.
[0055] As shown in Fig 3B, a client device 106 may send a real time video stream request to a Cloud Vehicle Platform 105. The request may be sent to access a video from a vehicle being

captured in real time by one or more image sensors present on the vehicle (as shown by step S1). In one non-limiting aspect, the request may be for accessing a video being captured in real time by the DMS 103. In one non-limiting aspect, the communication between the client device 106 and the Cloud Vehicle Platform 105 may be over an internet connection. Upon receipt of real time video stream request, the Cloud Vehicle Platform 105 may forward the request to the TCU 102 of the vehicle 101 (as shown by step S2). The TCU 102 of the vehicle may receive the request from the Cloud Vehicle Platform 105 via the communication module 201.
[0056] In response to the receipt of the request to access the video, the TCU 102 may first establish a CAN communication channel with the DMS 103 and may send a real time video stream request via the CAN communication channel to the DMS 103 (as shown by step S3). Upon receiving the request, the DMS 103 may send a communication to the TCU 102 via the Wi-Fi communication channel to request a secure Wi-Fi connection between the DMS 103 and the TCU 102 (as shown by step S4). The TCU 102 may send a Reject Real time Stream Request to the Cloud Vehicle Platform 105 if the TCU 102 fails to establish the secure Wi-Fi connection with the DMS 103 or if the TCU 102 does not have the required signal strength to stream the real time video stream (as shown by step S5’).
[0057] Following the establishment of the connection with the DMS 103, the TCU 102 may send an accept real time stream request communication to the Cloud Vehicle Platform 105 indicating that the TCU 102 is ready to stream the real time video and has the signal strength for streaming the real time video. (as shown by Step 5)
[0058] Upon receipt of the accept real time stream request communication, the Cloud Vehicle Platform 105 sends a success of real time video streaming communication to the client device 106 indicating that the real time video may be available for streaming. However, if the real time video is not available for streaming, the Cloud Vehicle Platform 105 sends a Failure of Real Time Video Streaming communication to the client device 106 (as shown by Step 7).
[0059] The DMS 103 sends a real time stream of the video to the TCU 102 via Wi-Fi communication. (as shown by step 8). In a non-limiting aspect, real time video is streamed from the DMS to the TCU 102 using real time transfer message protocol streaming (RTMPS). The DMS 103 sends the Video Streaming status to the TCU 102, indicating if the entire real time video stream has been successfully completed (as shown by Step 9). Upon receiving the video, the TCU 102 sends the real time video stream to the video server 108 via internet

connection (as shown by Step 10). In a non-limiting aspect, the TCU 102 transmits the real time video to the video server 108 based on a secure file over transfer protocol (SFTP). Lastly, the video server 108 sends the real time video stream to the client device 106 for viewing (as shown by Step 10).
[0060] FIG. 4 shows a flowchart illustrating a method 400 performed by a telematic control unit (TCU) for accessing at least one video data from a vehicle.
[0061] As shown in Fig. 4, at step 401, the method 400 discloses receiving, at the telematics control unit (TCU) 102 of a vehicle 101, a video streaming request from a client 109. The video streaming request may be sent by the client device 106 via the Cloud Vehicle Platform 105. In one aspect, the TCU receives the video streaming request at the Communication module 201 of the TCU 102 via an internet connection.
[0062] At step 402, the method 400 further discloses transmitting the request to a driver monitoring system (DMS) 103 through a controller area network (CAN) communication channel, as discussed in above aspects. In one non-limiting aspect, the TCU 102 may initially establish a connection with the DMS 103 via the CAN transceiver 204 of the TCU 102 before transmitting the request to the DMS 103.
[0063] At step 403, the method 400 discloses receiving at least one video from the DMS 103 through a wireless fidelity (Wi-Fi) channel, as discussed in above aspect. For receiving at least one video from the DMS 103, the method further comprises receiving a request to send (RTS) signal from the DMS through the CAN communication channel. If the TCU 102 has the signal strength to receive the at least one video and the TCU 102 is ready to receive the at least one video from the DMS 103, the method 400 further includes transmitting a clear to send (CTS) signal to the DMS 103 over the CAN communication channel. The CTS signal indicates to the DMS 103 to transmit the at least one video over the Wi-Fi channel. In one aspect, the at least one video is streamed from the DMS to the TCU using real time transfer message protocol streaming (RTMPS).
[0064] At step 403, the method 400 discloses transmitting the at least one video to a server 108 for streaming the at least one video on a user device 106, as discussed in above aspects. The streamed video is sent to the client device 106 by the server 108 via internet connection. Moreover, the at least one video is transmitted to the server by the TCU 10 based on a secure file over transfer protocol (SFTP).

[0065] Thus, the method 400 facilitates secure connection between DMS and TCU over the Wi-Fi channel instead of implementing the additional SIM card and modem in DMS. Further, the method 400 facilitates access to a video from a vehicle/DMS, thereby avoiding the additional cost incurred by the additional SIM or modem of the DMS 103.
[0066] The method 400 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform specific functions or implement specific abstract data types.
[0067] The order in which the method 400 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.
[0068] The disclosed method 400 with reference to FIG. 4, or one or more operations of the flow diagram 400 may be implemented using software including computer-executable instructions stored on one or more computer-readable media (e.g., non-transitory computer-readable media, such as one or more optical media discs, volatile memory components (e.g., DRAM or SRAM), or non-volatile memory or storage components (e.g., hard drives or solid-state non-volatile memory components, such as Flash memory components) and executed on a computer (e.g., any suitable computer, such as a laptop computer, net book, Web book, tablet computing device, smart phone, or other mobile computing device). Such software may be executed, for example, on a single local computer.
[0069] Furthermore, one or more computer-readable storage media may be utilized in implementing aspects consistent with the present disclosure. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the aspects described herein. The term “computer-readable medium” should be understood to include tangible items and exclude carrier waves and transient signals, i.e., be non-transitory. Examples include Random Access Memory

(RAM), Read-Only Memory (ROM), volatile memory, non-volatile memory, hard drives, CD (Compact Disc) ROMs, DVDs, flash drives, disks, and any other known physical storage media.
[0070] The terms "an aspect", "aspect", "aspects", "the aspect", "the aspects", "one or more aspects", "some aspects", and "one aspect" mean "one or more (but not all) aspects of the invention(s)" unless expressly specified otherwise.
[0071] The terms "including", "comprising", “having” and variations thereof mean "including but not limited to", unless expressly specified otherwise.
[0072] The enumerated listing of items does not imply that any or all the items are mutually exclusive, unless expressly specified otherwise. The terms "a", "an" and "the" mean "one or more", unless expressly specified otherwise.
[0073] A description of an aspect with several components in communication with each other does not imply that all such components are required. On the contrary, a variety of optional components are described to illustrate the wide variety of possible aspects of the invention.
[0074] When a single device or article is described herein, it will be clear that more than one device/article (whether they cooperate) may be used in place of a single device/article. Similarly, where more than one device/article is described herein (whether they cooperate), it will be clear that a single device/article may be used in place of the more than one device/article or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality and/or features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other aspects of invention need not include the device itself.
[0075] Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter.
[0076] While various aspects and aspects have been disclosed herein, other aspects and aspects will be apparent to those skilled in the art. The various aspects and aspects disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the detailed description.

WE CLAIM:
1. A Telematic Control Unit (TCU) (102) for accessing at least one video data from a
vehicle (101), the TCU (102) comprising:
a memory (207);
a communication module (201) comprising a sim card module (210); a wireless fidelity (Wi-Fi) module (205); a controller area network (CAN) transceiver (204); at least one controller (206) in communication with the memory (207), the communication module (201), the Wi-Fi module (205) and the CAN transceiver (204), wherein the at least one controller (206) is configured to:
receive, via the communication module (201), a request for video streaming from a user (109);
transmit, via the CAN transceiver (204), the request to a driver monitoring system (DMS) (103) through a CAN communication channel;
receive, via the Wi-Fi module (205), at least video data from the DMS (103) through a Wi-Fi channel; and
transmit, via the communication module (201), the at least one video to a server (108) to stream the at least one video data on a user device (106).
2. The TCU (102) as claimed in claim 1, wherein to receive the at least one video data
from the DMS (103), the at least one controller (206) is configured to:
receive, via the CAN transceiver (204), a request to send (RTS) signal from the DMS (103) through the CAN communication channel; and
transmit, via the CAN transceiver (204), a clear to send (CTS) signal to the DMS (103) over the CAN communication channel, wherein the CTS signal indicates the DMS (103) to transmit the at least one video data over the Wi-Fi channel.
3. The TCU (102) as claimed in claim 1, wherein the at least one controller (206) is configured to transmit, the at least one video data to the server (108) based on a secure file over transfer protocol (SFTP).
4. The TCU (102) as claimed in claim 1, wherein the at least one video data is streamed from the DMS (103) to the server (108) using real time transfer message protocol streaming (RTMPS).

5. The TCU (102) as claimed in claim 1, wherein the at least one video data includes a pre-stored video or a real-time video.
6. A method (400) for accessing at least one video data from a vehicle (101), the method (400), being performed at a telematic control unit (TCU) (102) of the vehicle (101) comprising:
receiving (401) a request for video streaming from a user (109);
transmitting (402) the request to a driver monitoring system (DMS) (103) through a controller (206) area network (CAN) communication channel;
receiving (403) at least one video data from the DMS (103) through a wireless fidelity (Wi-Fi) channel; and
transmitting (404) the at least one video data to a server (108) for streaming the at least one video data on a user device (106).
7. The method (400) as claimed in claim 6, wherein receiving (403) the at least one video
data from the DMS (103) through a wireless fidelity (Wi-Fi) channel comprises:
receiving a request to send (RTS) signal from the DMS (103) through the CAN communication channel; and
transmitting a clear to send (CTS) signal to the DMS (103) over the CAN communication channel, wherein the CTS signal indicates the DMS (103) to transmit the at least one video data over the Wi-Fi channel.
8. The method (400) as claimed in claim 6, wherein transmitting (404) the at least one video data to the server (108) comprises transmitting the at least one video data to the server (108) based on a secure file over transfer protocol (SFTP).
9. The method (400) as claimed in claim 6, wherein the at least one video data is streamed from the DMS (103) to the server (108) using real time transfer message protocol streaming (RTMPS).
10. The method (400) as claimed in claim 6, wherein the at least one video data includes a pre-stored video or a real-time video. ftjJv