Description:TECHNICAL FIELD

[001] The present disclosure generally relates to the field of data transmission and analysis, and more particularly to a system and method for selectively transmitting data to a cloud.

BACKGROUND

[002] Generally, data processing refers to manipulation, transformation, and analysis of raw data to extract meaningful information and insights. The data processing involves various operations performed on the raw data to convert the raw data into a useful form for decision-making, reporting, storage, and other purposes. With the advancement of communication and technology, organizations often store and process their data in cloud for reasons such as scalability, accessibility, reliability, and security. For example, cloud allows businesses to easily scale their storage and processing resources based on changing needs, while also providing remote access to data from anywhere with an internet connection. However, despite the benefits of cloud storage, some challenges persist, such as the lack of technology to simplify the process of filtering data before sending it to the cloud. Hence, the raw data is directly transmitted to the cloud, where filtering and other preprocessing steps are performed.

[003] Transmitting the raw data directly to the cloud has several disadvantages and challenges. For example, transmitting large volumes of raw data to the cloud often consumes significant network bandwidth, leading to increased costs. Bandwidth limitations may also cause delays in data transmission, impacting real-time processing requirements. Further, depending on the internet connection speed and network latency, transmitting large volumes of data to the cloud may result in slower data transfer speeds. Furthermore, filtering the data in cloud cause data redundancy, resource wastage, and data transfer limits at telemetry devices.

[004] In the context of electric vehicles (EVs), data transmission to the cloud plays a crucial role in enabling various functionalities and services. For example, the EVs are equipped with telematics systems that collect and transmit data about vehicle performance, battery status, charging history, and driving behavior to the cloud. Such data enables remote monitoring and management of EV fleets, allowing fleet operators to track vehicle health, optimize maintenance schedules, and ensure efficient operation. Further, by transmitting diagnostic data to the cloud, EVs may undergo remote diagnostics and predictive maintenance. Furthermore, the vehicle data collected in the cloud are used for various other purposes such as but not limited to research, planning, deriving customer insights, and energy management. However, due to the lack of technology to simplify the process of filtering data before sending it to the cloud, telemetry devices of the EVs transmit the raw data directly to the cloud, where filtering and other preprocessing steps are performed.

[005] One such prior art discloses a method and a system for updating a CAN analysis parameter dynamically based on a database in a field of Internet of Vehicles. The database used for storing CAN application message analysis parameters are included, and the method comprises the steps of analysing a CAN application message by using the CAN application message analysis parameter in the database, when the database has an update and succeeds in downloading the update, comparing a CAN application message analysis parameter table in a new database with a CAN application message analysis parameter table in the stored initial database, and after the comparison, updating the CAN application message analysis parameter table, and analysing the CAN application message by using the updated CAN application message analysis parameter table after the system is restarted. According to the method and the system for updating the CAN analysis parameter dynamically based on the database, the same vehicle-mounted T-Box terminal can adapt to different types of vehicles or the possibility of analysing the user driving behaviour by a TSP cloud platform in the later period can be realized.

[006] In the context of EVs, transmitting the raw data directly to the cloud has several disadvantages and challenges. For example, transmitting large volumes of data from EVs to the cloud may strain network bandwidth and increase data transmission costs, particularly in areas with limited or expensive internet connectivity. Further, bandwidth constraints may lead to delays in data transmission, affecting real-time monitoring, remote diagnostics, and over-the-air updates for EVs. Furthermore, the speed and reliability of data transfer between EVs and the cloud may impact the responsiveness of remote monitoring, diagnostics, and software updates.

[007] To summarize, pushing all data to the cloud results in resource wastage, including storage space, processing power, and network bandwidth. Storing and processing of unnecessary or irrelevant data in the cloud consumes valuable resources that could be better utilized for more critical tasks or analysis. Further, storing and processing large volumes of data in the cloud may result in increased costs, especially if the data is not efficiently managed or if unnecessary data is being stored. Furthermore, storing all data in the cloud without proper data management strategies often leads to data redundancy. The duplicate or unnecessary data can occupy valuable storage space and complicate the data analysis efforts.

[008] Hence, there is a need for a solution for an optimized and cost-effective data transmission system.

BRIEF SUMMARY

[001] This summary is provided to introduce a selection of concepts in a simple manner that is further described in the detailed description of the disclosure. This summary is not intended to identify key or essential inventive concepts of the subject matter nor is it intended for determining the scope of the disclosure.

[002] To overcome or mitigate at least one of the problems mentioned above, there exists a for a system and a method for transmitting data to a cloud.

[003] A system for transmitting data to a cloud is disclosed. The system includes an Electronic Control Unit (ECU), and a telemetry device communicatively connected to the ECU and to the cloud. The telemetry device is configured to receive the raw data transmitted by the ECU. Upon receiving the raw data from the ECU, the telemetry device parses the raw data, determines the data to be transmitted to the cloud, and transmits the data to the cloud, using a wireless communication interface. In one implementation, the telemetry device determines the data to be transmitted to the cloud based on one or more definitions for transmitting the data to the cloud. Hence, the system disclosed in the present disclosure filters or preprocesses the raw data before transmitting to the cloud.

[004] Further disclosed is a method for transmitting data to a cloud. The method includes, receiving, by a telemetry device, raw data transmitted by an ECU, parsing, by the telemetry device, the raw data received from the ECU, determining, by a telemetry device, the data to be transmitted to the cloud and transmitting, by a telemetry device, the data to the cloud using a wireless communication interface. In one implementation, the telemetry device determines the data to be transmitted to the cloud based on one or more definitions for transmitting the data to the cloud.

[005] The system and the method disclosed in the present disclosure parses the raw data received from the one or more ECUs, determines, or filters the data to be transmitted to the cloud based on the one or more definitions for transmitting the data to the cloud stored in the database file. Filtering the data at the telemetry device facilitates reducing duplicate and unnecessary data being transmitted to the cloud, thereby conserving network bandwidth. Filtering the data at the telemetry device also facilitates in reducing the storage and the processing bandwidth within the cloud. Further, filtering the data at the telemetry device and transmitted the data to the cloud eliminates the data parsing cost at the cloud, and reduces the computational overhead associated with parsing and processing large volumes of data in the cloud. Furthermore, the database file having one or more definitions for communication and the one or more definitions for transmitting data to the cloud ensures consistency and accuracy in data interpretation and transmission within the system.

[006] To further clarify advantages and features of the present disclosure, a more particular description of the disclosure will be rendered by reference to specific embodiments thereof, which is illustrated in the appended figures. It is to be appreciated that these figures depict only typical embodiments of the disclosure and are therefore not to be considered limiting of its scope. The disclosure will be described and explained with additional specificity and detail with the accompanying figures.

BRIEF DESCRIPTION OF THE FIGURES

[007] The disclosed method and system will be described and explained with additional specificity and detail with the accompanying figures in which:
[008] Figure 1 illustrates an electric automotive ecosystem comprising an electric vehicle and a charging infrastructure connected to the electric vehicle;

[009] Figure 2A depicts a block diagram illustrating the system for selectively transmitting data to a cloud, in accordance with an embodiment of the preset disclosure;

[0010] Figure 2B depicts a simplified block diagram illustrating the system having a single electronic control unit, in accordance with an embodiment of the present disclosure; and

[0011] Figure 3 illustrates a flowchart depicting a method for selectively transmitting data to the cloud, in accordance with an embodiment of the present disclosure.

[0012] Further, persons skilled in the art to which this disclosure belongs will appreciate that elements in the figures are illustrated for simplicity and may not have been necessarily drawn to scale. Furthermore, in terms of the construction of the joining ring and one or more components of the bearing assembly may have been represented in the figures by conventional symbols, and the figures may show only those specific details that are pertinent to understanding the embodiments of the present disclosure so as not to obscure the figures with details that will be readily apparent to those of ordinary skill in the art having benefit of the description herein.

DETAILED DESCRIPTION

[0013] For the purpose of promoting an understanding of the principles of the present disclosure, reference will now be made to the various embodiments and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the present disclosure is thereby intended, such alterations and further modifications in the illustrated system, and such further applications of the principles of the present disclosure as illustrated therein being contemplated as would normally occur to one skilled in the art to which the present disclosure relates.

[0014] It will be understood by those skilled in the art that the foregoing general description and the following detailed description are explanatory of the present disclosure and are not intended to be restrictive thereof.

[0015] Whether or not a certain feature or element was limited to being used only once, it may still be referred to as “one or more features” or “one or more elements” or “at least one feature” or “at least one element.” Furthermore, the use of the terms “one or more” or “at least one” feature or element do not preclude there being none of that feature or element, unless otherwise specified by limiting language including, but not limited to, “there needs to be one or more…” or “one or more elements is required.”

[0016] Reference is made herein to some “embodiments.” It should be understood that an embodiment is an example of a possible implementation of any features and/or elements of the present disclosure. Some embodiments have been described for the purpose of explaining one or more of the potential ways in which the specific features and/or elements of the proposed disclosure fulfil the requirements of uniqueness, utility, and non-obviousness.

[0017] Use of the phrases and/or terms including, but not limited to, “a first embodiment,” “a further embodiment,” “an alternative embodiment,” “one embodiment,” “an embodiment,” “multiple embodiments,” “some embodiments,” “other embodiments,” “further embodiment”, “furthermore embodiment”, “additional embodiment” or other variants thereof do not necessarily refer to the same embodiments. Unless otherwise specified, one or more particular features and/or elements described in connection with one or more embodiments may be found in one embodiment, or may be found in more than one embodiment, or may be found in all embodiments, or may be found in no embodiments. Although one or more features and/or elements may be described herein in the context of only a single embodiment, or in the context of more than one embodiment, or in the context of all embodiments, the features and/or elements may instead be provided separately or in any appropriate combination or not at all. Conversely, any features and/or elements described in the context of separate embodiments may alternatively be realized as existing together in the context of a single embodiment.

[0018] Any particular and all details set forth herein are used in the context of some embodiments and therefore should not necessarily be taken as limiting factors to the proposed disclosure.

[0019] The terms “comprises”, “comprising”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such process or method. Similarly, one or more devices or sub-systems or elements or structures or components proceeded by “comprises... a” does not, without more constraints, preclude the existence of other devices or other sub-systems or other elements or other structures or other components or additional devices or additional sub-systems or additional elements or additional structures or additional components.

[0020] Embodiments of the present disclosure will be described below in detail with reference to the accompanying drawings.

[0021] For the sake of clarity, the first digit of a reference numeral of each component of the present disclosure is indicative of the Figure number, in which the corresponding component is shown. For example, reference numerals starting with digit “1” are shown at least in Figure 1. Similarly, reference numerals starting with digit “2” are shown at least in Figure 2.

[0022] Embodiments of the present disclosure disclose a system and a method for transmitting data to a cloud. In one embodiment of the present disclosure, the system disclosed in the present disclosure includes an electronic control unit and a telemetry device which receives raw data from the electronic control unit or any electronic sensors or devices. The telemetry device parses the raw data, determines the data to be transmitted to the cloud and transmits the data to the cloud using a a wireless communication interface. In one embodiment, the telemetry device determines the data to be transmitted based on one or more definitions for transmitting the data to the cloud. The one or more definitions for transmitting the data to the cloud are stored in a database file of the telemetry device. Further, the one or more definitions for transmitting the data to the cloud includes but not limited to a sampling rate, precision, severity definitions, and data transmission criteria.

[0023] It is important to note that while the elements of the system and functionalities discussed are presented in the context of an electric vehicle, the system and method disclosed herein may be implemented with any systems or devices that require data transmission to a cloud. This versatility allows for the adaptation and utilization of the disclosed system and method in diverse domains and applications beyond the electric vehicles. For instance, the system and the method disclosed could be applied to internet of thing (IoT) devices, industrial machinery, healthcare equipment, smart home appliances, and more.

[0024] As the system and its functionalities are discussed within the framework of electric vehicles, Figure 1 is presented to establish this context. Figure 1 illustrates an electric automotive ecosystem including an electric vehicle and a charging infrastructure connected to the electric vehicle. In construction, the electric vehicle (EV) 100 typically includes a battery or battery pack 105 enclosed within a battery casing and includes a Battery Management System (BMS), an on-board charger 110, a Motor Controller Unit (MCU), an electric motor 115 and an electric transmission system 120. The primary functions of the above-mentioned elements are detailed in the following paragraphs: The battery of an EV 100 (also known as Electric Vehicle Battery (EVB) or traction battery) is re-chargeable and is the primary source of energy required for the operation of the EV, wherein the battery 105 is typically charged using the electric power from the grid through a charging infrastructure 125. The battery may be charged using Alternating Current (AC) or Direct Current (DC), wherein, in case of AC input, the on-board charger 110 converts the AC power to DC power after which the DC power is transmitted to the battery through the BMS. However, in case of DC charging, the on-board charger 110 may be bypassed, and the current transmitted directly to the battery through the BMS. Additionally, the EV 100 may also be equipped with wired or wireless or wired and wireless infrastructure such as, but not limited to Bluetooth, Wi-Fi, controller area network (CAN), Ethernet, Universal Serial Bus (USB), universal asynchronous receiver/transmitter (UART), Local Area network (LIN), Inter-Integrated Circuit (I2C), serial peripheral interface (SPI), Synchronous Serial Interface (SSI) and so on to facilitate wireless communication with the charging infrastructure 125, other EVs or the cloud.

[0025] The battery 105 is made up of a plurality of cells which are grouped into a plurality of modules. The terms “battery”, and “battery pack” may be used interchangeably and may refer to any of a variety of different rechargeable cell compositions and configurations including, but not limited to, lithium-ion (e.g., lithium iron phosphate, lithium cobalt oxide, other lithium metal oxides, etc.), lithium-ion polymer, nickel metal hydride, nickel cadmium, nickel hydrogen, nickel-zinc, silver zinc, or other battery types or configurations. The term “battery pack” as used herein may refer to multiple individual batteries enclosed within a single structure or multi-piece structure. The individual batteries may be electrically interconnected to achieve a desired voltage and current capacity for a desired application. The Battery Management System (BMS) is an electronic system, the primary function of which is to ensure that the battery 105 is operating safely and efficiently. The BMS continuously monitors different parameters of the battery such as temperature, voltage, current and so on, and communicates these parameters to the Electronic Control Unit (ECU) and the Motor Controller Unit (MCU) in the EV using one or more protocols including but not limited to, Controller Area Network (CAN) bus protocol which facilitates the communication between the ECU and MCU and other peripheral elements of the EV 100 without the requirement of a host computer.

[0026] The MCU primarily controls or regulates the operation of the electric motor based on the power transmitted from the vehicle’s battery, wherein the primary functions of the MCU include starting the electric motor 115, stopping the electric motor 115, controlling the speed of the electric motor 115, enabling the vehicle to move in the reverse direction and protect the electric motor 115 from premature wear and tear. The primary function of the electric motor 115 is to convert electrical energy into mechanical energy, wherein the converted mechanical energy is subsequently transferred to the transmission system of the EV to facilitate movement of the EV. Additionally, the electric motor 115 also acts as a generator during regenerative braking (that is, kinetic energy of the EV in motion is converted into electrical energy and stored in the battery of the EV). The types of motors generally employed in EVs include, but are not limited to DC series motor, Brushless DC motor (also known as BLDC motors), Permanent Magnet Synchronous Motor (PMSM), Three Phase AC Induction Motors and Switched Reluctance Motor (SRM).

[0027] The transmission system 120 of the EV 100 facilitates the transfer of the generated mechanical energy by the electric motor 115 to the wheels (130a, 130b) of the EV. Generally, the transmission systems 120 used in EVs include single speed transmission system and multi-speed (i.e., two-speed) transmission system, wherein the single speed transmission system includes a single gear pair whereby the EV runs at a constant speed ratio between the motor rotational speed and the wheel rotational speed. However, the multi-speed/two-speed transmission system includes different gear ratios which facilitates higher torque and vehicle speed depending on the selected gear ratio.

[0028] In one embodiment, all data pertaining to the EV 100 or charging infrastructure 125 or both, are collected and processed using a remote server (known as cloud) 135, wherein the processed data is indicated to the rider of the EV 100 through a display unit present in the dashboard 140 of the EV 100. In an embodiment, the display unit may be an interactive or touch sensitive display unit. In another embodiment, the display unit may be a non-interactive display unit. It is noteworthy that the electric vehicle, as described with reference to Figure 1, provides a context in which various embodiments of the present disclosure may be described and observed. Subsequently, the embodiments of the present disclosure are described by referring to the essential elements and the structure of an electric vehicle.

[0029] As described, the EV 100 includes the battery or battery pack 105 with Battery Management System (BMS), Motor Controller Unit, transmission systems, etc. Further, the EV 100 includes one or more electronic control units for managing and controlling various functions of the EV 100 to ensure optimal performance, efficiency, and safety. The one or more electronic control units are further configured to transmit the data pertaining to the EV 100 to the remote server 135 (hereinafter referred to as cloud) for processing, storage, and analysis.

[0030] Figure 2A depicts a block diagram illustrating the system for transmitting data to a cloud, in accordance with an embodiment of the preset disclosure. It is to be noted that the system 200 may be implemented with the EV 100 depicted in Figure 1 to facilitate the transmission of data of the EV 100 to the cloud. Referring to Figure 2A, the system 200 includes one or more electronic control units 205-1 to 205-N, a telemetry device 210 and a remote server 215 (hereinafter referred to as a cloud 215). The cloud 215 may correspond to the cloud 135 (the remote server) illustrated in Figure 1 or maybe any other cloud service communicatively connected with the telemetry device 210. As shown, the one or more electronic control units 205-1 to 205-N are communicatively connected to the telemetry device 210 through wired or wireless or combination of wired and wireless communication networks. Further, the telemetry device 210 is communicatively connected to the cloud 215 through a communication network such as the Internet (not depicted in the Figure 2A), which may include a combination of wired and wireless communication devices.

[0031] As described, the one or more electronic control units 205-1 to 205-N are configured for managing and controlling various functions of the EV 100 to ensure optimal performance, efficiency, and safety. For example, the ECU 205-1 may be a BMS ECU configured for monitoring and managing the battery pack in the EV 100. For example, the ECU 205-1 monitors and manages battery charging, discharging, cell balancing, temperature control, and state of charge (SoC) estimation to ensure optimal battery performance, longevity, and safety. Further, the ECU 205-2 may be a motor controller ECU configured for controlling the operation of the electric motor, regulating the speed, torque, and power output. Typically, the motor controller ECU receives input from sensors such as throttle position sensors, wheel speed sensors, and motor temperature sensors to adjust motor performance accordingly. Furthermore, the ECU 205-3 may be a charging controller ECU configured for managing the charging process. The ECU 205-3 may communicate with external charging stations, regulate charging voltage, and current, and monitor charging status to ensure safe and efficient charging of the battery 105. Furthermore, the ECU 205-N may be a vehicle control unit which serves as the central control unit for the entire EV 100, integrating and coordinating the operation of various subsystems and ECUs. For example, the ECU 205-N may be configured to receive data from various sensors configured for measuring parameters such as battery voltage, current, temperature, motor speed, and throttle position. As depicted in Figure 2A, the one or more ECUs 205-1 to 205-N are communicatively connected to the telemetry device 210 for transmitting the raw data to the telemetry device 210.

[0032] Figure 2B depicts a simplified block diagram illustrating the system with a single electronic control unit, in accordance with an embodiment of the present disclosure. It is important to note that the depiction in Figure 2B focuses on the system 100 featuring a single electronic control unit (ECU) 205 (hereinafter referred to as ECU 205) for explanatory purposes. However, the broader system configuration, as depicted in Figure 2A, allows for the transmission of data from multiple ECUs 205-1 to 205-N to the cloud 215.

[0033] Referring to Figure 2B, the ECU 205 may be configured to receive data from various sensors. The sensors are configured to measure parameters such as battery voltage, current, temperature, motor speed, and throttle position. The ECU 205 may include but not limited to a microcontroller or a microprocessor, a memory module, an input/output interface, an analog to digital convert (ADC), a digital to analog converter (DAC), and a communication interface such as Controller Area Network (CAN), Local Interconnect Network (LIN), etc. Typically, the ECU 205 communicates with other ECUs and the telemetry device 210 using a CAN communication protocol which is reliable communication protocol specifically developed for automotive applications. In one embodiment of the present disclosure, the ECU 205 includes a database file 220 storing one or more definitions for communication 225 between the ECU 205, the other ECUs, and the telemetry device 210. As described, the ECU 205 transmits the raw data to the telemetry device 210 using the CAN protocol. The raw data as described herein may include but not limited to battery parameters such as state of charge (SoC), battery voltage, and battery temperature, and motor parameters such as motor speed, motor toque, motor temperature, and motor controller parameters. The raw data may further include power electronics parameters such as inverter temperature, DC-DC converter status, and charger status, and vehicle parameters such as vehicle speed, acceleration and deceleration data, regenerative and braking data. The values of the various parameters are measured using one or more sensors connected to the ECU 205. In one embodiment, the ECU 205 uses the one or more definitions for communication 225 stored in the database file 220 to transmit the raw data to the telemetry device 210. It is to be noted that the values of the one or more parameters may be encoded and communicated through a single CAN message based on the one or more definitions for communication 225 stored in the database file 220.

[0034] The one or more definitions for communication 225 stored in the database file 220 include but not limited to definitions for message identifiers, signal definitions, message signal and mapping definitions. For example, the definitions for the message identifiers specify the message IDs used by the ECUs, along with associated message names and descriptions. The signal definitions define the signals transmitted within each message, including the names, start bit, length, byte order, scaling factors, and units. Further, the message signal and mapping definitions specify which signals are included within each message and their respective bit positions. Hence, the ECU 205 encodes the raw data in the CAN message based on the one or more definitions for communication 225 stored in the database file 220. Then, the ECU 205 transmits CAN message including the raw data to the telemetry device 210 through a CAN bus, for example.

[0035] The telemetry device 210 is configured for receiving raw data from various ECUs 205 and transmitting the data to the cloud 215 and various other subsystems of the EV 100, such as dashboard. The telemetry device 210 typically includes a microcontroller or a microprocessor, memory module, power circuit, wireless communication module for transmitting the data to other devices or external sources such as cloud 215, and communication interface such as Controller Area Network (CAN), Local Interconnect Network (LIN), etc. In one embodiment, the telemetry device 210 communicates with other ECU 205 using a CAN communication protocol which is reliable communication protocol specifically developed for automotive applications.

[0036] In one embodiment of the present disclosure, on receiving the raw data from the ECU 205, the telemetry device 210 parses the raw data received from the ECU 205, determines the data to be transmitted to the cloud 215, and transmits the data to the cloud 215 using a wireless communication interface. Referring to Figure 2B, the telemetry device 210 includes a communication interface 230, a data parsing module 235, a processor 240, a wireless communication module 245 and a memory module 250. It is to be noted that only the essential components of the telemetry device 210 are shown. However, the telemetry device 210 may include other elements as described above.

[0037] In one embodiment of the present disclosure, the telemetry device 210 receives the raw data from the ECU 205 through the communication interface 230, for example CAN interface. On receiving the raw data from the ECU 205, the data parsing module 235 parses the raw data to derive the values of the one or more parameters. In one embodiment of the present disclosure, the telemetry device 210 also includes the database file 220 stored in the memory module 250. The data parsing module 235 uses the one or more definitions for communication 235 stored in the database file 220 for parsing the raw data received from the ECU 205. As described, the values of the one or more parameters may be encoded and transmitted through the single CAN message. data parsing module 235 parses the raw data received from the ECU 205 for deriving the values of the one or more parameters from the CAN message. For example, the raw data received may include the values associated with the state of charge (SoC), the battery voltage, and the battery temperature. The data parsing module 235 parses the raw data to derive the values of the raw data using the one or more definitions for communication 225 stored in the database file 220.

[0038] On parsing the raw data, the processor 240 determines the data to be transmitted to the cloud 215. In one embodiment of the present disclosure, the database file 220 includes one or more definitions 255 for transmitting the data to the cloud 215. The one or more definitions 255 for transmitting the data to the cloud 215 as described herein refers to one or more definitions for filtering and pre-processing the raw data so as to select the data to be transmitted to the cloud 215. Hence, the one or more definitions 255 for transmitting the data to the cloud 215 include at least a sampling rate and precision. The sampling rate as described herein refers to a rate at which the raw data is to be transmitted to the cloud 215. For instance, with a sampling rate of ten for the battery temperature, only every tenth value from the ECU 205 is transmitted to the cloud 215 through the wireless communication interface 245. Consequently, the processor 240 discards nine received values from the ECU 205 and transmits only the tenth value to the cloud 215. This approach reduces the volume of data sent to the cloud 215, aiding bandwidth conservation and optimizing data transmission efficiency. Similarly, with a sampling rate of fifteen for the battery voltage, only every fifteenth value from the ECU 205 is transmitted to the cloud 215. Hence, database file 220 of the telemetry device 210 includes the one or more definitions 255 for transmitting data to the cloud 215 and definitions are defined for each data type. For example, as described, sampling rate is defined for each type of data such as battery temperature, battery voltage, SoC, etc.

[0039] Further, the precision as described herein refers to a level of accuracy with which data is to be transmitted to the cloud 215. The precision value defined in the database file 220 describes the number of digits or bits used to express a data value, indicating the resolution or granularity of the data to be transmitted. For example, consider a scenario where a temperature sensor is configured to measure the battery temperature of EV 100 with high precision, providing readings to three decimal places, such as 33.123°C. This data is transmitted by the ECU 205 to the telemetry device 210. However, if the precision defined in the database file 220 for battery temperature is set to one decimal place, the processor 240 adjusts the transmitted value accordingly. In this case, the battery temperature value sent to the cloud 215 will be 33.1°C. By employing this approach, the volume of data transmitted to the cloud 215 is reduced, thereby contributing to decreased storage requirements and alleviating processing resources in the cloud 215.

[0040] As described, the one or more definitions 255 for transmitting the data to the cloud 215 include at least the sampling rate and the precision. In one embodiment, the one or more definitions 255 for transmitting the data to the cloud 215 further includes frequency, severity definitions, sampling bit, etc. The definition frequency as described herein refers to how often the data is to be transmitted to the cloud 215. Further, the severity definition defines the severity of the data to prioritize critical data for transmission to the cloud 215. For example, battery temperature data may be given higher priority than the regenerative and braking data, and when the telemetry device 210 receives values for both, the processor 240 priorities the battery temperature data over the regenerative and braking data and transmits the battery temperature data the cloud 215. Similarly, high severity data related to safety-critical systems may be given precedence over comparatively less critical telemetry data. It is to be noted that the processor 240 may determine the data to be transmitted to the cloud 215 based on combination of two or more definitions 255 for transmitting the data to the cloud. For example, the processor 140 may prioritize the battery temperature data over battery voltage data based on the severity definition. Further, the processor 140 may limit the battery temperature value to a single decimal point based on the precision value defined in the database file 220.

[0041] As described, the data parsing module 235 parses the raw data received from the ECU 205 (only one ECU is shown in Figure 2B) based on the one or more definitions for communication 225 stored in the database file 220, determines the data to be transmitted to the cloud 215 based on the one or more definitions 255 for transmitting the data to the cloud 215, and transmits the data to the cloud 215 through the wireless communication interface 245 using a predefined transmission protocol, such as but not limited to Hypertext Transfer Protocol (HTTP), Message Queuing Telemetry Transport (MQTT) and WebSocket. In one embodiment of the present disclosure, the processor 140 is further configured for structuring the data before transmitting to the cloud 215 based on the predefined transmission protocol. For example, on determining the data to be transmitted to the cloud 215, the processor 140 generates packets including the data based on the predefined transmission protocol and transmits the data to the cloud 215 for further processing, analysis, and storage.

[0042] Upon receiving the data from the telemetry device 210, the server associated with the cloud 215 parses the data according to the predefined transmission protocol. In one embodiment of the present disclosure, the cloud 215 includes the database file 220 and uses the one or more definitions 255 stored in the database file 220 for parsing the data received from the telemetry device 210. The data is parsed for subsequent processing, analysis, and storage of the data. It is to be noted that the data is formatted and packaged according to cloud transmission requirements, ensuring compatibility with cloud-based data processing and storage systems.

[0043] Figure 3 illustrates a flowchart depicting a method for transmitting data to the cloud, in accordance with an embodiment of the present disclosure. As indicated, in step 305, the telemetry device 210 receives the raw data from the ECU 205. As described, the raw data refers to the values of the one or more parameters of the EV 100 and the raw data is received through the CAN protocol.

[0044] In step 310, the data parsing module 235 of the telemetry device 210 parses the raw data to derive the values of the one or more parameters. In one embodiment of the present disclosure, the parsing module 235 parses the raw data based on the one or more definitions for communication 225 stored in the database file 220 associated with the telemetry device 210.

[0045] In step 315, the processor 240 of the telemetry device 210 determines the data to be transmitted to the cloud 215. In one embodiment of the present disclosure, the processor 240 determines the the data to be transmitted to the cloud 215 based on the one or more definitions 255 stored in the database file 220. The one or more definitions 255 are specifically defined for transmitting the data from the telemetry device 210 to the cloud 215.

[0046] In step 320, the processor 240 transmits the data to the cloud 215 using the wireless communication interface 245 which utilizes the predefined protocol. The predefined protocol may include but not limited to HTTP, MQTT and WebSocket. Hence the data transmitted to the cloud 215 only includes the data determined by the processor 240, which is based on the one or more definitions 255 for transmitting the data to the cloud 215.

[0047] As described, the system and the method disclosed in the present disclosure parses the raw data received from the one or more ECUs, determines, or filters the data to be transmitted to the cloud 115 based on the one or more definitions 255 for transmitting the data to the cloud 215 stored in the database file 220. Filtering the data at the telemetry device 210 facilitates in reducing duplicate and unnecessary data being transmitted to the cloud 215, thereby conserving network bandwidth. Filtering the data at the telemetry device 210 also facilitates in reducing the storage and the processing bandwidth within the cloud 215.

[0048] Further, filtering the data at the telemetry device 210 and transmitted the data to the cloud 215 eliminates the data parsing cost at the cloud 215, and reduces the computational overhead associated with parsing and processing large volumes of data in the cloud 215.

[0049] Furthermore, the database file 220 having one or more definitions for communication 225 and the one or more definitions 255 for transmitting data to the cloud 215 ensures consistency and accuracy in data interpretation and transmission within the system 100.

[0050] While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person skilled in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein.

[0051] The figures and the foregoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein. Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts necessarily need to be performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples. Numerous variations, whether explicitly given in the specification or not, such as differences in structure, dimension, and use of material, are possible. The scope of embodiments is at least as broad as given by the following claims.

List of reference numerals:
Components Reference numerals
Vehicle 100
Battery or Battery pack 105
On-board charger 110
Electric motor 115
Transmission system 120
Charging infrastructure 125
Wheels 130a and 130b
Remote server 135
Dashboard 140
A system for transmitting data to a cloud 200
Electronic control units 205-1 to 205-N
Telemetry device 210
Cloud 215
Database file 220
Definitions for communication stored in the database file 225
Communication interface 230
Data parsing module 235
Processor 240
Wireless communication interface 245
Memory module 250
Definitions for transmitting data to the cloud 255 , Claims:1. A system for selectively transmitting data to a cloud, the system (200) comprising:
an electronic control unit (205); and
a telemetry device (210) communicatively connected to the electronic control unit (205) and to a cloud (215), wherein the telemetry device (210) is configured to:
receive raw data transmitted by the electronic control unit (205);
parse the raw data received from the electronic control unit (205) using a data parsing module (235);
determine the data to be transmitted to the cloud (215) using a processor (240); and
transmit the data to the cloud (215) using a wireless communication interface (245).

2. The system (200) as claimed in claim 1, wherein the electronic control unit (205) and the telemetry device (210) comprise database files (220) for storing one or more definitions for communication (225) between the electronic control unit (205) and the telemetry device (210).

3. The system (200) as claimed in claim 2, wherein the electronic control unit (205) is configured to use the one or more definitions for communication (225) to transmit the raw data to the telemetry device (210).

4. The system (200) as claimed in claim 2, wherein the telemetry device (210) is configured to use the one or more definitions for communication (225) to parse the raw data received from the electronic control unit (205).

5. The system (200) as claimed in claim 2, wherein the database file (220) of the telemetry device (210) comprises one or more definitions (255) for transmitting the data to the cloud (215).

6. The system (200) as claimed in claim 5, wherein the one or more definitions (255) for transmitting the data to the cloud (215) comprise at least a sampling rate and precision.

7. The system (200) as claimed in claim 5, wherein the one or more definitions (255) for transmitting the data to the cloud (215) comprise severity definitions.

8. The system (200) as claimed in claim 7, wherein the telemetry device (210) is configured to use the severity definitions to prioritize the data for transmission to the cloud (215).

9. The system (200) as claimed in claim 1, wherein the telemetry device (210) is configured to structure the data before transmitting to the cloud (215).

10. A method for transmitting data to a cloud (215), the method comprising:
receiving, by a telemetry device (210), raw data transmitted by an electronic control unit (205);
parsing, by the data parsing module (235) of the telemetry device (210), the raw data received from the electronic control unit (205);
determining, by the processor (240) of telemetry device (210), the data to be transmitted to the cloud (215); and
transmitting, by the telemetry device (210), the data to the cloud (215), using a wireless communication interface (245).

11. The method as claimed in claim 10, wherein the electronic control unit (205) and the telemetry device (210) comprise database files (220) respectively storing one or more definitions for communication (225) between the electronic control unit (205) and the telemetry device (210).

12. The method as claimed in claim 11, comprising using, by the electronic control unit (205), the one or more definitions for communication (225) to transmit the raw data to the telemetry device (210).

13. The method as claimed in claim 11, comprising using, by the telemetry device (210), the one or more definitions for communication (225) to parse the raw data received from the electronic control unit (205).

14. The method as claimed in claim 11, wherein the database file (220) of the telemetry device (210) comprises one or more definitions (255) for transmitting the data to the cloud (215).

15. The method as claimed in claim 14, wherein the one or more definitions (255) for transmitting the data to the cloud (215) comprise at least a sampling rate and precision.

16. The method as claimed in claim 14, wherein the one or more definitions (225) for transmitting the data to the cloud (215) comprise severity definitions.

17. The method as claimed in claim 16, comprising using, by the telemetry device (210), the severity definitions to prioritize the data for transmission to the cloud (215).

18. The method as claimed in claim 10, comprising transforming, by the telemetry device (210), the data into structured data before transmitting to the cloud (215).