US20200342691A1 - Method and control unit for transferring information to and/or from a vehicle - Google Patents

Method and control unit for transferring information to and/or from a vehicle Download PDF

Info

Publication number
US20200342691A1
US20200342691A1 US16/956,999 US201816956999A US2020342691A1 US 20200342691 A1 US20200342691 A1 US 20200342691A1 US 201816956999 A US201816956999 A US 201816956999A US 2020342691 A1 US2020342691 A1 US 2020342691A1
Authority
US
United States
Prior art keywords
vehicle
add
information
communication unit
interface
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
US16/956,999
Other languages
English (en)
Inventor
Alexander SAERS
Henrik FELIXSON
Simon Wretblad
Magnus Eriksson
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Scania CV AB
Original Assignee
Scania CV AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Scania CV AB filed Critical Scania CV AB
Publication of US20200342691A1 publication Critical patent/US20200342691A1/en
Assigned to SCANIA CV AB reassignment SCANIA CV AB ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: WRETBLAD, Simon, FELIXSON, Henrik, ERIKSSON, MAGNUS
Assigned to SCANIA CV AB reassignment SCANIA CV AB ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: SAERS, Alexander
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/382—Information transfer, e.g. on bus using universal interface adapter
    • G06F13/387—Information transfer, e.g. on bus using universal interface adapter for adaptation of different data processing systems to different peripheral devices, e.g. protocol converters for incompatible systems, open system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • G06F9/44526—Plug-ins; Add-ons
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/541—Interprogram communication via adapters, e.g. between incompatible applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60L—PROPULSION OF ELECTRICALLY-PROPELLED VEHICLES; SUPPLYING ELECTRIC POWER FOR AUXILIARY EQUIPMENT OF ELECTRICALLY-PROPELLED VEHICLES; ELECTRODYNAMIC BRAKE SYSTEMS FOR VEHICLES IN GENERAL; MAGNETIC SUSPENSION OR LEVITATION FOR VEHICLES; MONITORING OPERATING VARIABLES OF ELECTRICALLY-PROPELLED VEHICLES; ELECTRIC SAFETY DEVICES FOR ELECTRICALLY-PROPELLED VEHICLES
    • B60L2270/00—Problem solutions or means not otherwise provided for
    • B60L2270/40—Problem solutions or means not otherwise provided for related to technical updates when adding new parts or software

Definitions

  • the present invention relates to a method for transferring information to and/or from a vehicle.
  • the present invention also relates to a control unit arranged for transferring information to and/or from a vehicle.
  • the present invention also relates to a computer program and a computer-readable medium comprising instruction for carrying out the method according to the invention.
  • Vehicle manufacture may be conducted in a variety of ways. In for example the car industry, the manufacturer usually produces vehicles that are complete and intended for direct delivery to final customers.
  • the heavy vehicle industry commonly also employs other kinds of production methods.
  • Manufacturers of heavy vehicles may, as in the car industry, produce vehicles intended for delivery directly to final customers or final users of the vehicles.
  • heavy vehicles produced by the manufacturer are only partly manufactured, i.e. are only completed to a certain extent, including vehicle internal systems, in view of being subsequently completed by another part than the manufacturer, for example a user or a customer of the manufacturer, e.g. a third-party supplier, in such a way as to meet specific requirements of the final customers or users.
  • the vehicle although substantially completed by its manufacturer, will be provided with further functionalities and/or systems, in this document denoted add-on systems, e.g. by another party such as a third-party supplier, a customer, or a final user, before it is put into use.
  • add-on systems e.g. by another party such as a third-party supplier, a customer, or a final user
  • add-on systems e.g. by another party
  • add-on systems e.g. by another party
  • add-on systems e.g. by another party
  • add-on systems e.g. by another party
  • add-on systems e.g. by another party
  • add-on systems e.g. by another party
  • the vehicle although substantially completed by its manufacturer, will be provided with further functionalities and/or systems, in this document denoted add-on systems, e.g. by another party such as a third-party supplier, a customer, or a final user, before it is put into use.
  • vehicle manufacturers
  • chassis produced by a vehicle manufacturer may be designed to be usable in any desired way as bases for building on in order to construct mobile homes, fire vehicles, ambulances, concrete mixer trucks, refrigerated vehicles, or any other especially adapted vehicle.
  • a bus chassis may be produced by the vehicle manufacturer with little or no bodywork, with the intention to complete the vehicle with subsequent building-on performed by a bus bodybuilder.
  • a bodybuilder installs/adds one or more add-on systems, i.e. does bodywork, on a vehicle after its original manufacture.
  • the building-on and/or addition of one or more systems and/or functionalities carried out by another party may be very extensive, and at least some building-on is also very common in the case of heavy vehicles. For this reason, the vehicle manufacturer often also prepares the vehicle in such a way as to facilitate subsequent building-on.
  • one or more power takeoffs are often included in the vehicle by the manufacturer, e.g. so that add-on systems may be connected for example to the vehicle's engine and/or gearbox to enable them to be provided with driving power from the vehicle. There may also be connections to make it possible to use, for example, the vehicle's electrical system, hydraulic system and/or pneumatic system for implementation of add-on functions.
  • a vehicle may thus be provided with a plurality of power takeoffs, and the power takeoff requirement may vary depending on the kinds of applications built onto the vehicle. Certain applications may for example require power which is constantly available when the engine of the vehicle is running, irrespective of whether the vehicle is moving or not, e.g. in the case of concrete mixer trucks, refrigeration units in refrigerated vehicles.
  • the one or more add-on systems being implemented in the vehicle are often unknown for the vehicle internal systems, i.e. for the internal systems being provided by the manufacturer.
  • the one or more add-on systems may be unknown for manufacturer of the vehicle, and therefore also initially for the add-on interface of the vehicle.
  • the manufacturer cannot, already when the vehicle is produced, know which add-on systems that will be added to the vehicle later on, and the vehicle can therefore obviously also not possibly be equipped to interact with such unknown add-on systems.
  • the unknown add-on systems are not initially defined in the add-on interface, it may be impossible for off-board entities, such as e.g. bodywork entities/interfaces, diagnosis entities/interfaces and/or manufacturer entities/interfaces, to communicate with the add-on systems, since they may be incompatible with each other.
  • off-board entities such as e.g. bodywork entities/interfaces, diagnosis entities/interfaces and/or manufacturer entities/interfaces
  • the object is achieved by a method for transferring information to and/or from a vehicle, the vehicle including:
  • the method includes:
  • the second information format may be used by both the at least one vehicle internal system and the at least one add-on system.
  • the add-on interface By configuring the add-on interface such that the add-on interface has knowledge of the relationship between the first information/data format and the second information/data format, the add-on interface is able to convert information/data between the first information format and the second information format.
  • the add-on interface is able to convert information/data between the first information format and the second information format.
  • the first information format may be used by an offboard entity, such as a diagnosis tool/interface, a bodywork interface, a manufacturer interface, or any other suitable offboard entity being related to the vehicle.
  • the first information format may also be used for the transfer of information to and/or from the vehicle, i.e. may be used for the connection/communication of information between the at least one internal communication unit and the at least one external communication unit.
  • the first information format may also be used for onboard transfer of information between the add-on interface and the at least one internal communication unit.
  • the first information format may be characterized by one or more information related features, such as for example including a representation of the information, comprising e.g.
  • the first information format may also be characterized by one or more presentation related features, such as for example how the information is divided into packets being transferred, and/or the size and/or the contents/fields of packets carrying the information.
  • the second information format may be used by the onboard transfer of information between the add-on interface, and the at least one vehicle internal system and/or at least one add-on system.
  • the add-on interface By configuring the add-on interface such that it may perform the conversion between the first and second information format, a reliable and secure communication between the offboard and onboard entities is provided. This configuration of the add-on interface may be achieved remotely, without having to take the vehicle into a work shop, as is explained more in detail below.
  • the second information format may be characterized by one or more information related features, such as for example including a representation of the information, comprising e.g.
  • the second information format may also be characterized by one or more presentation related features, such as for example how the information is divided into packets being transferred, and/or the size and/or the contents/fields of packets carrying the information.
  • add-on systems may easily and cost-efficiently be added/implemented in the vehicle after its manufacture, since communication with these added add-on system is easily achieved, without causing vehicle off road time periods.
  • a vehicle being very flexible from a bodywork point of view is provided by usage of the present invention.
  • the add-on systems being added to the vehicle may use the communication provided already by the manufacturer, i.e. may communicate with the offboard entities/systems using a communication subscription already available from the manufacture of the vehicle, which of course reduces the costs.
  • an uplink transmission of information/data i.e. transmission of information/data from systems onboard the vehicle to any entity offboard the vehicle.
  • the onboard systems and the offboard entities may thus communicate with each other although they use differing information formats. This is made possible by the conversion performed by the add-on interface.
  • the configuring further includes defining at least one trigger condition, the trigger condition indicating when the transmitting of the information should be performed.
  • the add-on interface may be configured to execute uplink transmission of information/data when the at least one trigger condition is fulfilled.
  • the uplink flow of information/data may be regulated such that it is matched to the needs and/or capabilities of the onboard systems providing the information/data and/or of the offboard entities receiving the information/data.
  • the trigger conditions may be made very simple, or may be composed of more complex conditions. Trigger conditions of essentially any complexity level may be utilized, which increases the flexibility of the communication.
  • the definition of the trigger condition is related to one or more of:
  • any signals, states, parameters and/or conditions of one or more onboard systems may be taken into consideration when triggering the uplink transmission from the vehicle, which provides for a flexible way of controlling the uplink information flow.
  • the at least one trigger condition is defined based on input provided by one or more of:
  • the trigger condition may be flexibly updated/configured based on input information provided by a number of sources. Essentially anyone with knowledge of the add-on and/or vehicle internal systems may provide this input, which provides for a very flexible control of the uplink transmissions.
  • a downlink transmission of information/data i.e. transmission of information/data from offboard entities/systems to systems onboard the vehicle.
  • the onboard systems and the offboard entities may thus communicate with each other although they use differing information formats. This is made possible by the conversion performed by the add-on interface.
  • the definition of the relationship between the first information format and the second information format is based on input provided by one or more of:
  • the add-on interface may be flexibly updated/configured based on configuration information including the definition of the relationship between the first information format and the second information format provided by a number of sources.
  • configuration information including the definition of the relationship between the first information format and the second information format provided by a number of sources.
  • anyone with knowledge of the offboard systems and/or of the onboard internal and/or add-on systems may be able to update the add-on interface, wherefore the vehicle does not have to go to the workshop for the update/configuration.
  • the vehicle off road time and the update costs are hereby greatly reduced.
  • control system arranged for transferring information to and/or from a vehicle, the vehicle including:
  • the control unit is arranged for:
  • the control unit has advantages corresponding to the advantages mentioned above for the method.
  • the object is also achieved by the above-mentioned computer program and computer-readable medium.
  • FIG. 1 is a schematic illustration of a non-limiting example of a vehicle in which the embodiments of the present invention may be implemented
  • FIG. 2 shows a flow chart diagram for some embodiments of the present invention
  • FIG. 3 schematically illustrates a vehicle including onboard systems comprising an add-on interface and an offboard entity/system
  • FIG. 4 schematically illustrates a non-limiting example of a system, in which embodiments of the present invention may be implemented.
  • FIG. 5 is a schematic illustration of a control unit according to some embodiments of the present invention.
  • FIG. 1 schematically illustrates a power train in a vehicle 100 , in which the embodiments of the present invention may be implemented.
  • the illustrated vehicle 100 has only one axle 104 , 105 with tractive/drive wheels 110 , 111 , but the invention is also applicable to vehicles which have more than one axle provided with tractive wheels.
  • the power train comprises a combustion engine 101 which in a conventional way, via an output shaft 102 of the engine, usually via a flywheel, is connected to a gearbox 103 via a clutch 106 and an input shaft 109 connected to the gearbox 103 .
  • the engine may be controlled by the vehicle's control system via a control unit 115 .
  • the clutch 106 which may for example take the form of an automatically controlled clutch, and/or the gearbox 103 , which may for example be a conventional automatic gearbox, may also be controlled by means of one or more suitable control units, generally depicted as the control unit 115 in FIG. 1 .
  • the function of the control unit 115 may be provided by two or more control units, as is mentioned more in detail below.
  • the vehicle 100 may further include at least one internal communication unit 116 , being associated/connected to one or more control units 115 of the vehicle.
  • the at least one internal communication unit 116 may be included in a control system network of the vehicle 100 .
  • the control system network may, as is described below, essentially include any suitable communication interface facilitating communication between control units/devices/entities in the vehicle 100 .
  • the communication interface connects the one or more vehicle internal systems 120 with each other, including connecting the at least one internal communication unit 116 with the control unit 115 and other internal systems 120 of the vehicle 100 .
  • Such a communication interface many for example, include a controller area network (CAN), an Ethernet connection, a Flexray bus, a local interconnect network (LIN) bus and/or a WiFi connection.
  • CAN controller area network
  • LIN local interconnect network
  • the at least one internal communication unit 116 is arranged for communication with at least one vehicle external communication unit 161 , i.e. arranged for transmitting information to and/or receiving information from the at least one vehicle external communication unit 161 .
  • the at least one vehicle external communication unit 161 is arranged outside of the vehicle 100 , and may be included in and/or associated/connected to essentially any suitable external device/node/apparatus/entity 162 , such as e.g. at least one web and/or internet related unit, at least one internet cloud 160 related unit, at least one infrastructure unit, at least one external communication entity included in at least one other vehicle, at least one server and/or at least one database.
  • the at least one vehicle external communication unit 161 may also be included in and/or associated/connected to essentially one or more of the units/devices/entities 411 , 412 , 413 , 141 , 420 , 430 , 440 of an add-on/bodybuilder network 410 , as is described more in detail below.
  • the communication between the at least one internal 116 and at least one external 161 communication units may be performed by usage of a wireless connection 117 , e.g. a connection working according to essentially any suitable wireless standard, specification and/or protocol, such as according to the Global System for Mobile communications (GSM) standard, the General Packet Radio Service (GPRS) standard, the Bluetooth standard, any suitable wireless local area networking (WiFi) standard, any suitable generation of a broadband cellular technology (3G, LTE, 4G, 5G) standard, and/or any other suitable wireless standard.
  • the connection 117 may also be a wired connection, including usage of at least one cable or other wiring equipment.
  • an output shaft 107 from the gearbox 103 drives the tractive wheels 110 , 111 via a final gear 108 , e.g. a conventional differential, and driveshafts 104 , 105 which are connected to the final gear.
  • a final gear 108 e.g. a conventional differential, and driveshafts 104 , 105 which are connected to the final gear.
  • the engine 101 , the clutch 106 and the gearbox 103 may be examples of vehicle internal systems 120 .
  • the vehicle may include a large number of such vehicle internal systems 120 , i.e. systems arranged in the vehicle 100 when it was produced by the manufacturer.
  • vehicle internal system 120 parts, systems and/or functionalities being included/arranged in the vehicle already at vehicle manufacture/production by the manufacturer.
  • parts, systems and/or functionalities being included/arranged in the vehicle after the manufacture/production by the manufacturer is commonly denoted add-on systems 130 in this document.
  • the manufacturer is in this document defined as a producer of the original/initial vehicle, being partly completed with at least one vehicle internal system 120 but lacking the later added at least one add-on system 130 .
  • the manufacturer of the partly completed vehicle may also be denoted as original equipment manufacturer (OEM).
  • OEM original equipment manufacturer
  • the one or more add-on systems 130 may be provided by another party, which in this document means a party which may be another and/or independent of the vehicle manufacturer, and to which a vehicle produced by the vehicle manufacturer is directly or indirectly delivered after being manufactured/produced.
  • the other party may be a customer or a final user, but may also be a third-party supplier, which carries out building-on, i.e. addition of one or more add-on systems 130 , before delivery to a final customer.
  • FIG. 1 is merely one example of how the vehicle might be configured, as the embodiments of the invention are applicable to all types of vehicles, e.g. those with hybrid power trains, electric vehicles and/or other kinds of axle configurations, other types of gearboxes with or without clutches etc.
  • the one or more add-on systems 130 illustrated in FIG. 1 may be provided with power form one or more takeoffs 150 , which may be situated at various locations in the vehicle 100 .
  • the one or more add-on systems 130 may be of various kinds, e.g. one might comprise activation of a crane function via a power takeoff, whereas another might comprise illumination of a certain warning lamp at the vehicle driver's location.
  • the one or more add-on systems 130 may be of a simple kind, i.e. have a low complexity, but may also have substantially any desired functionality, and thus also any complexity.
  • the one or more add-on systems 130 may need, i.e. may have a demand for, power to be provided to the add-on systems 130 .
  • the one or more add-on systems 130 may also need, i.e. may have a demand for, being able to communicate with an internal control system of the vehicle, in order to be provided with one or more signals, parameters and/or control signals available in the internal control system, and/or to be able to provide one or more signals, parameters and/or control signals to the one or more vehicle internal systems 120 via the vehicle internal control system.
  • the one or more add-on systems 130 may also need, i.e. may have a demand for, being able to communicate with one or more nodes/devices/entities/equipment external from the vehicle.
  • an add-on interface 140 may be arranged or provided in the vehicle 100 as an interface between the at least one vehicle internal system 120 and the at least one add-on system 130 .
  • Power needed by the one or more add-on systems 130 may e.g. be provided by the above mentioned one or more power takeoffs 150 and/or may be provided by the add-on interface 140 arranged for providing communication between the one or more vehicle internal systems 120 and the one or more add-on systems 130 .
  • the communication between the one or more vehicle internal systems 120 and the one or more add-on systems 130 is facilitated by the add-on interface 140 .
  • the add-on interface communicates one or more signals, parameters and/or control signals between the one or more vehicle internal systems 120 and the one or more add-on systems 130 .
  • the add-on interface 140 is provided as a general interface between the at least one vehicle internal system 120 and the at least one add-on system 130 .
  • the add-on interface includes one or more inputs/outputs, for example input/output pins, to which systems, such as e.g. add-on systems, may be connected. Via these inputs/outputs, signals are received/transmitted to the systems connected to the add-on interface 140 .
  • the one or more add-on systems may be connected to one or more inputs of the add-on interface, and may provide signals of any suitable signaling format, which is often related to the specific add-on system providing the signal, to the one or more inputs.
  • any signaling format mentioned in this document may be received at the one or more inputs.
  • signals may also be output on the one or more outputs of the add-on interface 140 , on a suitable signaling format.
  • the at least one internal communication unit 116 may be included in a control system network of the vehicle 100 , which may include the above-mentioned communication interface connecting the one or more vehicle internal systems 120 with each other.
  • a communication interface many for example, include a controller area network (CAN), an Ethernet connection, a Flexray bus, a local interconnect network (LIN) bus and/or a WiFi connection.
  • CAN controller area network
  • LIN local interconnect network
  • WiFi connection a wireless local interconnect network
  • Such a communication interface may be generally used for connecting units/devices/entities/interfaces in the vehicle 100 , such as connecting the add-on systems 130 to the add-on interface 140 .
  • the at least one add-on system 130 may be connected to an external control system network input, e.g.
  • an external controller area network (CAN) input 149 of an interface/control unit 148 including the add-on interface 140 .
  • CAN controller area network
  • a connection between the one or more add-on systems 130 and the communication interface, such as e.g. the controller area network (CAN) is provided, which is used for connecting the one or more add-on systems 130 to the one or more vehicle internal systems 120 , via the communication interface, e.g. via the controller area network (CAN).
  • the one or more add-on systems 130 may need/use various information to be provided to them, from within the vehicle and/or from outside of the vehicle, and may therefore have a demand for communication abilities.
  • the one or more add-on systems 130 may also demand resources from the vehicle, such as e.g. status signals from the vehicle, i.e. the signal state of appropriate outputs of the interface/control unit 148 including/implementing the add-on interface 140 .
  • the resources which the one or more add-on systems demand for their functions may for example take the form of a demand for mechanical power, electric power, hydraulic power and/or pneumatic power, and/or may take the form of a demand for at least one signal and/or at least one function of the control system of the vehicle.
  • a demanded power, requiring activation of a power takeoff 150 has to be demanded from the internal control system of the vehicle 100 . Where resources are demanded, they are often not constantly demanded, and are also often not constantly available.
  • Vehicle manufacturers are reluctant for some other party, e.g. a third-party supplier, to effect changes directly in the internal control system of the vehicle, since this may affect the performance of the vehicle in ways which are both undesirable and difficult to predict. This is also why the vehicle manufacturer provides the add-on interface 140 , i.e. a signaling interface which can be used for an add-on system for communication with the internal control system of the vehicle.
  • a third-party supplier e.g. a third-party supplier
  • the add-on interface 140 may be of various kinds, and may include a number of inputs and outputs, which each may have a certain function assigned to it.
  • One output might for example represent activation of a vehicle internal system 120 , e.g. a parking brake activation, and when the parking brake is applied this output might for example be set to a high level, in order thereby to communicate the activation of the internal system, e.g. the parking brake, to the one or more add-on systems 130 .
  • a large number of other examples of functions, whose status may be signaled in a similar way may be provided by the add-on interface 140 . These signals may then be used by the one or more add-on systems 130 , but subject for example to various conditions which usually have to be fulfilled for a certain function to be activated.
  • the vehicle manufacturer may provide a building-on interface to enable communication between the internal systems 120 and the add-on system 130 .
  • the add-on interface 140 may for example comprise one or more terminal blocks having a number of inputs/outputs, such that high/low/numerical signals on an output may for example represent a status of a certain function, and this information may be used as a control signal for conditional control of add-on system functions.
  • the add-on systems may communicate their status, e.g. whether the function is active or inactive, by applying a voltage to an input on the add-on interface 140 , which will be communicated further to the internal control system and/or vehicle internal systems 120 by the add-on interface 140 .
  • the internal communication system and/or the vehicle internal systems 120 will thus also be aware that add-on systems 130 exist and their status.
  • Control systems in modern vehicles usually comprise a communication bus system comprising of one or more communication buses arranged for connecting together a number of electronic control units (ECUs), e.g. the control units, or controllers, and various systems/components/devices on board the vehicle.
  • ECUs electronice control units
  • Such a control system may comprise a large number of control units and the responsibility for a specific function may be spread over more than one of them.
  • FIG. 1 shows only some such control units 115 , 140 .
  • parts of the present invention may be implemented in any suitable control unit, e.g. the control units 115 , 140 , or wholly or partly in one or more other control units on board the vehicle 100 .
  • Control units of the kind depicted are normally adapted to receiving sensor signals from various parts and/or control units of the vehicle.
  • Control units are also usually adapted to delivering control signals to various parts and components of the vehicle, e.g. the control units 115 , 140 may deliver signals to suitable actuators for activation of power takeoffs and/or for activation of other vehicle internal systems 120 .
  • the control unit 115 is in FIG. 1 schematically illustrated as receiving signals and/or providing control signals from and/or to the engine 101 , the clutch 106 and/or the gearbox 103 .
  • the control system 120 may, also receive and/or provide control signals to and/or from other internal systems/devices 120 in the vehicle 100 .
  • the interface control unit 148 including/implementing the add-on interface 140 may comprise configuration means 141 arranged for configuring an add-on interface, e.g. a first configuration unit 141 , conversion means 142 arranged for converting between information formats, e.g. a conversion unit 142 , and transfer means 143 arranged for transferring information/data, e.g. a transfer unit 143 .
  • configuration means 141 arranged for configuring an add-on interface e.g. a first configuration unit 141
  • conversion means 142 arranged for converting between information formats, e.g. a conversion unit 142
  • transfer means 143 arranged for transferring information/data, e.g. a transfer unit 143 .
  • FIG. 2 shows a flow chart diagram for a method 200 according to an embodiment of the present invention, i.e. a method for transferring information to and/or from a vehicle 100 .
  • the method steps of FIG. 2 may be performed in another order than illustrated in FIG. 2 , as long as the information needed for performing a method step is available when the step is to be performed.
  • an add-on interface 140 of the vehicle 100 is configured by defining at least a relationship between a first information format used by the at least one internal communication unit 116 , and a second information format used by one or more of the at least one vehicle internal system 120 and the at least one add-on system 130 , e.g. by use of a below described configuration unit/means 141 .
  • the first information format is different from the second information format.
  • the first information format may be used by an offboard entity, may be used for the transfer of information to and/or from the vehicle and/or may be used for onboard transfer of information between the add-on interface and the at least one internal communication unit.
  • the second information format may be used by the onboard transfer of information between the add-on interface, and the at least one vehicle internal system and/or at least one add-on system.
  • a second step 220 of the method according to the present invention information is converted by usage of the configured add-on interface 140 , between the first information format and the second information format, e.g. by use of a below described conversion unit/means 142 .
  • the information is transferred to and/or from the vehicle 100 , by usage of the at least one internal communication unit 116 , the at least one vehicle external communication unit 161 , and the first information format, e.g. by use of a below described transfer unit/means 143 .
  • the information transfer in the first information format may be performed in the uplink and/or downlink direction.
  • the add-on interface By configuring the add-on interface such that it is able to convert information/data between the first information format and the second information format, a communication between essentially any offboard entity, and the at least one vehicle internal system and/or the at least one add-on system is made possible. Hereby information may reliably and securely be transferred between offboard and onboard entities/system.
  • This configuration of the add-on interface may be achieved remotely, without having to take the vehicle into a work shop, which provides for a flexible and cost-effective handling of add-on systems.
  • the definition of the relationship between the first information format and the second information format may be based on input provided by essentially anyone having knowledge of the add-on systems and/or of the vehicle internal systems, e.g. a final user of the vehicle, at least one other part than the manufacturer providing and/or having knowledge of the at least one add-on system, and/or the manufacturer of the vehicle.
  • the add-on interface may be remotely and flexibly updated/configured based on the input configuration information, wherefore the vehicle does not have to go to the workshop for the update/configuration.
  • the vehicle off road time and the update costs are hereby greatly reduced.
  • an uplink (UL) transfer of information/data is provided.
  • information/data from one or more of the at least one vehicle internal system 120 and the at least one add-on system is transmitted/transferred offboard the vehicle to at least one offboard entity/system.
  • the conversion 220 then includes receiving 221 , to the add-on interface 140 , onboard information on the second information format from the at least one vehicle internal system 120 and/or from the at least one add-on system 130 .
  • the conversion 220 further includes converting 222 , by usage of the configured add-on interface 140 , the information to the first information format from the second information format.
  • the transmission 230 includes transmitting 231 the information from the at least one internal communication unit 116 to the at least one vehicle external communication unit 161 on the first information format, i.e. transmitting 231 the information on the first information format offboard to at least one offboard entity/system.
  • the uplink transfer of information/data may also, according to an embodiment of the present invention, include in the configuration 210 a definition of at least one trigger condition indicating when the information should be transmitted 231 uplink offboard the vehicle 100 to at least one offboard entity/system.
  • the trigger condition used for triggering the uplink transmission 231 of the information, may be related to essentially anything onboard, e.g. any action, parameter, condition, signal related to the at least one vehicle internal system 120 and/or the at least one add-on system 130 in the vehicle.
  • the at least one trigger condition may be defined based on input provided by a final user of the vehicle 100 , at least one other part than the manufacturer, the at least one other part providing the at least one add-on system 130 or having knowledge of the at least one add-on system 130 , and/or the manufacturer.
  • uplink transmission of information/data i.e. transmission of information/data from systems onboard the vehicle to any entity offboard the vehicle.
  • the add-on interface may execute uplink transmission of information/data when the at least one trigger condition is fulfilled, whereby a controlled uplink transmission rate/flow matching the needs and/or capabilities of the onboard systems providing the information/data and/or of the offboard entities receiving the information/data is provided.
  • a downlink (DL) transfer of information/data is provided.
  • information/data from at least one offboard entity/system is transmitted/transferred onboard to the at least one vehicle internal system 120 and/or the at least one add-on system 130 .
  • the transfer 230 of information includes receiving 232 to the at least one internal communication unit 116 information on the first information format from the at least one external communication unit 161 , i.e. from at least one offboard entity/system.
  • the conversion 220 of the information formats, performed by the add-on interface 140 includes converting 223 the information from the first information format to the second information format.
  • the conversion 220 further includes providing 224 the information onboard on the second information format from the add-on interface 140 to the at least one vehicle internal system 120 and/or the at least one add-on system 130 .
  • a downlink transmission of information/data i.e. transmission of information/data from offboard entities/systems to systems onboard the vehicle, is provided.
  • FIG. 3 schematically illustrates a non-limiting example of an embodiment of the present invention.
  • An interface control unit 148 implementing/including the add-on interface 140 is shown.
  • a non-limiting example of a function block 145 is illustrated.
  • Signals carrying information on the second information format are received/provided by the add-on interface from/to a vehicle internal system 120 and/or an add-on system 130 .
  • the add-on system 130 may be connected to the add-on interface 140 by a signal connection to an input 149 of the interface control unit 148 , e.g. an external CAN input pin 149 .
  • At least one of the vehicle internal 120 and/or add-on 130 system may include e.g. an instrument 310 , arranged for displaying information/signals provided to it on the second information format.
  • the add-on interface 140 e.g. the function block 145 of the interface control unit 148 , is configured such that it has knowledge of the relationship between the first information/data format and the second information/data format. Therefore, the add-on interface is able to convert information/data between the first information format and the second information format.
  • the add-on interface is able to convert information/data between the first information format and the second information format, a communication between essentially any offboard entity 414 , 420 , 430 , 440 , and the at least one vehicle internal system 120 and/or the at least one add-on system 130 is made possible.
  • the configuration of the add-on interface 140 may be based on configuration information provided remotely from an offboard entity 414 , 420 , 430 , 440 , such as an add-on interface configuration tool 414 , e.g. provided by a final user and/or a customer. As mentioned above, the configuration may be provided to the add-on interface via at least one external communication unit 161 and at least one internal communication unit 116 .
  • FIG. 4 schematically illustrates a system facilitating a general platform for handling vehicles including one or more add-on systems 130 .
  • FIG. 4 for pedagogical reasons only shows some of the units/devices/entities/nodes in such a system. Essentially, only the units/devices/entities/nodes useful for explaining the concept are schematically illustrated in FIG. 4 .
  • a vehicle 100 includes one or more vehicle internal systems 120 , including at least one internal communication unit 116 and an interface/control unit 148 including an add-on interface 140 .
  • the vehicle 100 further includes one or more add-on systems 130 , connected to the one or more vehicle internal systems 120 via the add-on interface 140 , as described above.
  • the at least one internal communication unit 116 may communicate with at least one external communication unit 161 , which may be located essentially anywhere outside of the vehicle, e.g. in another vehicle and/or in one or more nodes 411 , 412 , 413 , 414 , 420 , 430 , 440 of an add-on/bodybuilder network 410 .
  • the one or more nodes 411 , 412 , 413 , 414 , 420 , 430 , 440 of the add-on/bodybuilder network 410 may be located e.g. in a web/internet/cloud related unit, in an infrastructure unit, in a server and/or in a database, as mentioned above.
  • the add-on/bodybuilder network 410 may be implemented as an internet cloud 160 related solution.
  • the one or more nodes 411 , 412 , 413 , 414 , 420 , 430 , 440 of an add-on/bodybuilder network 410 are in FIG. 4 for pedagogic reasons illustrated as separate nodes. However, these nodes may be implemented less nodes than illustrated in FIG. 4 .
  • the add-on interface 140 utilized for the embodiments of the present invention may be an advanced and flexible interface provided with advanced logical functionality and possibilities for flexible definition of interface inputs and/or outputs.
  • the logical functionality providable by the add-on interface 140 includes essentially any useful logical, numerical and/or mathematical operations, that may be operated on one or more signals input to the add-on interface 140 .
  • the input signals may here, according to various embodiments, include essentially any kind of signal, such as digital and/or analog signals, comprising well defined signal value levels and/or numerical signal values.
  • the add-on interface 140 used by the embodiments of the present invention may be considerably more advanced than conventional add-on interfaces are, including e.g. processing of numerical signals, representation of physical values as numerical values, and/or performing numerical operations on the numerical values/signals.
  • the add-on interface 140 may also easily be configured such that it is able to interpret the signals/information being input to it from the one or more add-on systems 130 , e.g. via an external control system network input, such as an external controller area network (CAN) input, of the interface/control unit 148 including the add-on interface 140 .
  • the add-on interface 140 may also easily be configured to output signals/information to the one or more add-on systems 130 , via the external controller area network (CAN), such that the signals/information may be interpreted/used by the add-on systems 130 .
  • CAN external controller area network
  • the add-on interface 140 may be arranged for converting signaling/information formats being used by the one or more add-on systems 130 to signaling/information formats being used by the one or more vehicle internal systems 120 , and vice versa.
  • the one or more add-on systems 130 may communicate with the one or more vehicle internal systems 120 , and possibly also with other systems, such as systems related to, or being included in the add-on/bodybuilder network 410 .
  • the add-on interface 140 may also be easily configured for interpreting sensor signals being provided by the one or more add-on systems 130 , such that a flexibility regarding addition of sensors is achieved for the vehicle.
  • any type of sensor providing any type of sensor signal having essentially any features, e.g. indicating any type of physical quantity unit may be implemented in the one or more add-on systems 130 , whereby the add-on interface 140 is configured to process the provided sensor signal accordingly.
  • the add-on interface 140 may also be easily configured to output a processed sensor signal having suitable features to the one or more vehicle internal systems 120 , such as e.g.
  • the add-on interface 140 may for example be configured for outputting sensor signals adapted for being displayed in any suitable vehicle instrument.
  • the add-on network 410 may further include an add-on interface configuration tool 414 , which may include an external communication unit 161 arranged for communicating with the at least one internal communication unit 116 included in the vehicle.
  • an add-on interface configuration tool 414 By use of the add-on interface configuration tool 414 , the add-on interface 140 may easily be configured and/or defined, as is described in this document.
  • Information related to how the add-on interface 140 is to be configured/defined may be provided based on input to a manufacturer interface entity 420 and/or a client/user interface entity 430 by a manufacturer and/or a client/user.
  • One or more of the manufacturer interface entity 420 and the client/user interface entity 430 may be implemented as an application (APP) program, as an interface portal, as an interface program, or as any suitable equipment arranged for presenting information and/or for receiving input of information.
  • APP application
  • An add-on/bodybuilder network 410 may be arranged, e.g. in an internet cloud 160 configuration, for communication and/or configuration of the one or more add-on systems 130 , and/or for communication with the manufacturer interface entity 420 and/or the client/user interface entity 430 .
  • the add-on network 410 may include a communication node 411 , which may include an external communication unit 161 arranged for communicating with the at least one internal communication unit 116 included in the vehicle.
  • Information transmitted to and/or from the vehicle 100 may have one or more features related to one or more configured functions of the add-on interface 140 and/or related to a configured signaling format used for the connection between the at least one internal communication unit 116 and the at least one external communication unit 161 .
  • an immutable and unique identifier ID may be created based on, and assigned to, the specific configuration of the add-on interface functions and/or of the used signaling.
  • the add-on interface configuration tool 414 , the manufacturer interface entity 420 and/or the client/user interface entity 430 is normally unaware of the features of the one or more add-on systems 130 and/or of the configuration of the add-on interface 140 . Therefore, the add-on interface configuration tool 414 , the manufacturer interface entity 420 and/or the client/user interface entity 430 are often also unaware of how to interpret information provided by the one or more add-on systems 130 to them. The immutable and unique identifier ID may therefore be added, e.g. as included in a packet header, to information sent from the one or more add-on systems 130 .
  • the information may then be decoded, in a codec 413 connected to the communication node 411 , by usage of this immutable and unique identifier ID.
  • the immutable and unique identifier ID may, after having been previously provided by the add-on interface 140 and/or by the add-on interface configuration tool 414 , be stored in a register 412 of the add-on network 410 .
  • the codec 413 is arranged for encoding and/or decoding information transmitted from and/or to the vehicle 100 , e.g. by usage of the immutable and unique identifier ID, which is then provided to the codec 413 by the register 412 .
  • the codec 413 may detect the immutable and unique identifier ID in a packet header of information transmitted from the vehicle 100 , and may therefore be able to determine the specific configuration of the add-on interface 140 and how to detect the information in the packets.
  • the immutable and unique identifier ID may also be added, e.g. in a packet header, to information transmitted to the vehicle 100 .
  • the add-on interface 140 may then, based on the immutable and unique identifier ID, easily identify to which one or more add-on systems 130 and/or one or more vehicle internal systems 120 the information is intended to be transferred.
  • One or more diagnosis equipment 440 may be arranged in the add-on network 410 to process diagnosis related information. Such one or more diagnosis equipment may for example be included in the manufacturer interface entity 420 and/or in the client/user interface entity 430 , or may be implemented in a separate diagnosis equipment 440 .
  • the one or more diagnosis equipment 440 is normally unaware of the features of the possibly unknown one or more add-on systems 130 and/or of the configuration of the add-on interface 140 . Therefore, in order to provide a generic diagnosis system, diagnostic identifiers are created based on, and assigned to, the specific configuration of the add-on interface 140 and/or the one or more add-on systems 130 .
  • the diagnosis equipment 440 may be able to provide a reliable diagnosis also for all add-on systems 130 , also for the ones being unknown for the diagnosis equipment.
  • a method for transferring information to and/or from a vehicle according to the present invention may also be implemented in a computer program, which, when it is executed in a computer, instructs the computer to execute the method.
  • the computer may be included in the herein described system and/or may be coupled/connected to the herein described system.
  • the computer program is usually constituted by a computer program product 503 stored on a non-transitory/non-volatile digital storage medium, in which the computer program is incorporated in the computer-readable medium of the computer program product.
  • the computer-readable medium comprises a suitable memory, such as, for example: ROM (Read-Only Memory), PROM (Programmable Read-Only Memory), EPROM (Erasable PROM), Flash memory, EEPROM (Electrically Erasable PROM), a hard disk unit, etc.
  • ROM Read-Only Memory
  • PROM PROM
  • EPROM Erasable PROM
  • Flash memory EEPROM (Electrically Erasable PROM), a hard disk unit, etc.
  • FIG. 5 shows in schematic representation a control unit/system/means 500 / 115 / 148 .
  • the vehicle 100 may include one or more control units 115 .
  • the add-on interface 140 may be implemented as a control unit.
  • the control unit/system/means 500 / 115 / 148 comprises a computing unit 501 , which may be constituted by essentially any suitable type of processor or microcomputer, for example a circuit for digital signal processing (Digital Signal Processor, DSP), or a circuit having a predetermined specific function (Application Specific Integrated Circuit, ASIC).
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • the computing unit 501 is connected to a memory unit 502 arranged in the control unit/system/means 500 / 115 / 148 , which memory unit provides the computing unit 501 with, for example, the stored program code and/or the stored data which the computing unit 501 requires to be able to perform computations.
  • the computing unit 501 is also arranged to store partial or final results of computations in the memory unit 502 .
  • control unit/system/means 500 / 115 / 148 is provided with devices 511 , 512 , 513 , 514 for receiving and transmitting input and output signals.
  • These input and output signals may comprise waveforms, impulses, or other attributes which, by the devices 511 , 513 for the reception of input signals, can be detected as information and can be converted into signals which can be processed by the computing unit 501 . These signals are then made available to the computing unit 501 .
  • the devices 512 , 514 for the transmission of output signals are arranged to convert signals received from the computing unit 501 in order to create output signals by, for example, modulating the signals, which can be transmitted to other parts of and/or systems within or outside the vehicle 100 .
  • Each of the connections to the devices for receiving and transmitting input and output signals can be comprise one or more of a cable; a data bus, such as a CAN bus (Controller Area Network bus), a MOST bus (Media Orientated Systems Transport bus), or some other bus configuration; or by a wireless connection.
  • a data bus such as a CAN bus (Controller Area Network bus), a MOST bus (Media Orientated Systems Transport bus), or some other bus configuration
  • a wireless connection such as a Wi-Fi connection
  • CAN bus Controller Area Network bus
  • MOST bus Media Orientated Systems Transport bus
  • Control systems in modern vehicles commonly comprise communication bus systems including one or more communication buses for linking a number of electronic control units (ECU's), or controllers, and various components located on the vehicle.
  • ECU's electronice control units
  • Such a control system may comprise a large number of control units/means and the responsibility for a specific function can be divided amongst more than one control unit/means.
  • Vehicles of the shown type thus often comprise significantly more control units/means than are shown in FIGS. 1 and 5 , which is well known to the person skilled in the art within this technical field.
  • the present invention is implemented in the control unit/system/means 500 / 115 / 148 .
  • the invention can also, however, be implemented wholly or partially in one or more other control units/systems/means already present in the vehicle, or in some control unit/system/means dedicated to the present invention.
  • a control unit 140 arranged for transferring information to and/or from a vehicle.
  • the control unit 140 includes a configuration unit/means 141 , arranged for configuring 210 an add-on interface 140 of the vehicle 100 by defining at least a relationship between a first information format used by the at least one internal communication unit 116 and a second information format used by one or more of the at least one vehicle internal system 120 and the at least one add-on system 130 , as described above.
  • the control system further includes a conversion unit/means 142 , arranged for converting 220 , by usage of the configured add-on interface 140 , information between the first information format and the second information format, as described above.
  • the control system 120 also includes a transfer unit/means 143 , arranged for transferring 230 the information to and/or from the vehicle 100 , by usage of the at least one internal communication unit 116 , the at least one vehicle external communication unit 161 , and the first information format, as described above.
  • units/means are often described as being arranged for performing steps of the method according to the invention. This also includes that the units/means are designed to and/or configured to perform these method steps.
  • the at least one interface control unit/system/means 148 is in FIG. 1 illustrated as including separately illustrated units/means 141 , 142 , 143 .
  • the control system/means 140 may include or be coupled to e.g. other device/means 115 .
  • These means/units/devices 141 , 142 , 143 , 148 , 115 may, however, be at least to some extent logically separated but implemented in the same physical unit/device.
  • These means/units/devices 141 , 142 , 143 , 148 , 115 may also be part of a single logic unit which is implemented in at least two different physical units/devices.
  • These means/units/devices 141 , 142 , 143 , 148 , 115 may also be at least to some extent logically separated and implemented in at least two different physical means/units/devices. Further, these means/units/devices 141 , 142 , 143 , 148 , 115 may be both logically and physically arranged together, i.e. be part of a single logic unit which is implemented in a single physical means/unit/device.
  • These means/units/devices 141 , 142 , 143 , 148 , 115 may for example correspond to groups of instructions, which can be in the form of programming code, that are input into, and are utilized by at least one processor when the units/means are active and/or are utilized for performing its method step, respectively.
  • the interface control system/means 148 may be implemented at least partly within the vehicle 100 and/or at least partly outside of the vehicle 100 , e.g. in a server, computer, processor or the like located separately from the vehicle 100 .
  • the units 141 , 142 , 143 described above correspond to the claimed means 141 , 142 , 143 arranged for performing the embodiments of the present invention, and the present invention as such.
  • control system can be arranged for performing all of the above, in the claims, and in the herein described embodiments method steps.
  • the system is hereby provided with the above described advantages for each respective embodiment.
  • the present invention is also related to a vehicle 100 , such as a truck, a bus or a car, including the herein described interface control unit 148 arranged for transferring information to and/or from a vehicle.
  • vehicle 100 such as a truck, a bus or a car
  • interface control unit 148 arranged for transferring information to and/or from a vehicle.
  • inventive method, and embodiments thereof, as described above may at least in part be performed with/using/by at least one device.
  • the inventive method, and embodiments thereof, as described above may be performed at least in part with/using/by at least one device that is suitable and/or adapted for performing at least parts of the inventive method and/or embodiments thereof.
  • a device that is suitable and/or adapted for performing at least parts of the inventive method and/or embodiments thereof may be one, or several, of a control unit, an electronic control unit (ECU), an electronic circuit, a computer, a computing unit and/or a processing unit.
  • ECU electronice control unit
  • inventive method and embodiments thereof, as described above, may be referred to as an, at least in part, computerized method.
  • the method being, at least in part, computerized meaning that it is performed at least in part with/using/by the at least one device that is suitable and/or adapted for performing at least parts of the inventive method and/or embodiments thereof.
  • inventive method and embodiments thereof, as described above, may be referred to as an, at least in part, automated method.
  • the method being, at least in part, automated meaning that it is performed with/using/by the at least one device that is suitable and/or adapted for performing at least parts of the inventive method and/or embodiments thereof.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Computer Security & Cryptography (AREA)
  • Traffic Control Systems (AREA)
  • Small-Scale Networks (AREA)
US16/956,999 2017-12-27 2018-12-11 Method and control unit for transferring information to and/or from a vehicle Pending US20200342691A1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
SE1751651A SE542467C2 (en) 2017-12-27 2017-12-27 Method and control unit for transferring information to and / or from a vehicle
SE1751651-9 2017-12-27
PCT/SE2018/051281 WO2019132755A1 (en) 2017-12-27 2018-12-11 Method and control unit for transferring information to and/or from a vehicle

Publications (1)

Publication Number Publication Date
US20200342691A1 true US20200342691A1 (en) 2020-10-29

Family

ID=67064017

Family Applications (1)

Application Number Title Priority Date Filing Date
US16/956,999 Pending US20200342691A1 (en) 2017-12-27 2018-12-11 Method and control unit for transferring information to and/or from a vehicle

Country Status (7)

Country Link
US (1) US20200342691A1 (ko)
EP (1) EP3732579A4 (ko)
KR (1) KR102402629B1 (ko)
CN (1) CN111527482A (ko)
BR (1) BR112020011641A2 (ko)
SE (1) SE542467C2 (ko)
WO (1) WO2019132755A1 (ko)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230298403A1 (en) * 2019-09-20 2023-09-21 Sonatus, Inc. System, method, and apparatus for managing vehicle data collection
US11943109B2 (en) 2019-09-20 2024-03-26 Sonatus, Inc. System, method, and apparatus for extra vehicle communications control
EP4421760A1 (en) * 2023-02-27 2024-08-28 Volvo Truck Corporation A bodybuilder module for data logging and a data logging method
US12094259B2 (en) 2020-03-06 2024-09-17 Sonatus, Inc. System, method, and apparatus for managing vehicle automation
US12103479B2 (en) 2020-03-06 2024-10-01 Sonatus, Inc. System, method, and apparatus for managing vehicle automation
US12119996B2 (en) 2019-09-20 2024-10-15 Sonatus, Inc. System, method, and apparatus to execute vehicle communications using a zonal architecture

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113194441A (zh) * 2021-04-30 2021-07-30 江苏徐工工程机械研究院有限公司 一种工程机械车辆通信系统、方法及远程升级方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080247576A1 (en) * 2002-12-11 2008-10-09 Ira Marlowe Multimedia Device Integration System
US20130332844A1 (en) * 2012-06-11 2013-12-12 Mark Rutledge Method and system to configure an aftermarket interface module using a graphical user interface
US20160031388A1 (en) * 2014-07-30 2016-02-04 GM Global Technology Operations LLC Apparatus for integrating data functions in a motion control system for a vehicle

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7020289B1 (en) * 1998-11-17 2006-03-28 P. B. Clarke & Associates Remote control interface for replacement vehicle stereos
US6449541B1 (en) * 2000-10-17 2002-09-10 Microsoft Corporation Application-to-component communications helper in a vehicle computer system
US7489786B2 (en) * 2002-12-11 2009-02-10 Ira Marlowe Audio device integration system
CN101283522A (zh) * 2005-07-14 2008-10-08 斯科奇工业公司 用于与车辆数据总线上的设备通信的无线媒体源
US7596636B2 (en) * 2005-09-23 2009-09-29 Joseph Gormley Systems and methods for implementing a vehicle control and interconnection system
US7971145B2 (en) * 2006-05-22 2011-06-28 Sap Ag Systems and methods for adapting service interface behaviors
US8296007B2 (en) * 2010-05-05 2012-10-23 Ford Global Technologies, Llc Embedded vehicle data recording tools for vehicle servicing
US8880654B2 (en) * 2012-01-04 2014-11-04 Dearborn Group, Inc. Protocol adapter for passing diagnostic messages between vehicle networks and a host computer
KR20150011223A (ko) * 2013-07-22 2015-01-30 엘에스산전 주식회사 차량 제어장치 및 그 방법
DE102015208242A1 (de) * 2015-05-05 2016-11-10 Volkswagen Aktiengesellschaft Fahrzeug, Vorrichtungen, Verfahren und Computerprogramme zur Kontrolle eines Datenverkehrs und einer Datenübertragung an Fahrzeugkomponenten
CN106357499A (zh) * 2016-09-08 2017-01-25 深圳华汽车科技有限公司 汽车总线异构网络数据共享系统及方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080247576A1 (en) * 2002-12-11 2008-10-09 Ira Marlowe Multimedia Device Integration System
US20130332844A1 (en) * 2012-06-11 2013-12-12 Mark Rutledge Method and system to configure an aftermarket interface module using a graphical user interface
US20160031388A1 (en) * 2014-07-30 2016-02-04 GM Global Technology Operations LLC Apparatus for integrating data functions in a motion control system for a vehicle

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12058003B2 (en) 2019-09-20 2024-08-06 Sonatus, Inc. System, method, and apparatus to support mixed network communications on a vehicle
US12003374B2 (en) 2019-09-20 2024-06-04 Sonatus, Inc. System, method, and apparatus for extra vehicle communications control
US20230298403A1 (en) * 2019-09-20 2023-09-21 Sonatus, Inc. System, method, and apparatus for managing vehicle data collection
US11943109B2 (en) 2019-09-20 2024-03-26 Sonatus, Inc. System, method, and apparatus for extra vehicle communications control
US12073665B2 (en) * 2019-09-20 2024-08-27 Sonatus, Inc. System, method, and apparatus for managing vehicle data collection
US12046086B2 (en) 2019-09-20 2024-07-23 Sonatus, Inc. System, method, and apparatus for managing vehicle data collection
US12046085B2 (en) * 2019-09-20 2024-07-23 Sonatus, Inc. System, method, and apparatus for managing vehicle data collection
US12073664B2 (en) 2019-09-20 2024-08-27 Sonatus, Inc. System, method, and apparatus for managing vehicle data collection
US20230298404A1 (en) * 2019-09-20 2023-09-21 Sonatus, Inc. System, method, and apparatus for managing vehicle data collection
US20230298405A1 (en) * 2019-09-20 2023-09-21 Sonatus, Inc. System, method, and apparatus for managing vehicle data collection
US12047238B2 (en) 2019-09-20 2024-07-23 Sonatus, Inc. System, method, and apparatus to support mixed network communications on a vehicle
US12118830B2 (en) 2019-09-20 2024-10-15 Sonatus, Inc. System, method, and apparatus for managing vehicle data collection
US12095622B2 (en) 2019-09-20 2024-09-17 Sonatus, Inc. System, method, and apparatus for extra vehicle communications control
US12119996B2 (en) 2019-09-20 2024-10-15 Sonatus, Inc. System, method, and apparatus to execute vehicle communications using a zonal architecture
US12103479B2 (en) 2020-03-06 2024-10-01 Sonatus, Inc. System, method, and apparatus for managing vehicle automation
US12094259B2 (en) 2020-03-06 2024-09-17 Sonatus, Inc. System, method, and apparatus for managing vehicle automation
EP4421760A1 (en) * 2023-02-27 2024-08-28 Volvo Truck Corporation A bodybuilder module for data logging and a data logging method

Also Published As

Publication number Publication date
CN111527482A (zh) 2020-08-11
EP3732579A4 (en) 2021-09-15
SE1751651A1 (en) 2019-06-28
EP3732579A1 (en) 2020-11-04
SE542467C2 (en) 2020-05-12
WO2019132755A1 (en) 2019-07-04
BR112020011641A2 (pt) 2020-11-17
KR20200100125A (ko) 2020-08-25
KR102402629B1 (ko) 2022-05-26

Similar Documents

Publication Publication Date Title
US20200342691A1 (en) Method and control unit for transferring information to and/or from a vehicle
US11518396B2 (en) Method and control unit for facilitating diagnosis for a vehicle
US11579900B2 (en) Method and control unit for configuring an addon interface
US11663857B2 (en) Method and control unit for communicating with a vehicle
US11593089B2 (en) Method and control unit for configuring an add-on interface of a vehicle
US11661071B2 (en) Method and control unit for updating at least one functionality of a vehicle
EP3732580A1 (en) Method and control unit for configuring an add-on interface of a vehicle

Legal Events

Date Code Title Description
STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

AS Assignment

Owner name: SCANIA CV AB, SWEDEN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FELIXSON, HENRIK;WRETBLAD, SIMON;ERIKSSON, MAGNUS;SIGNING DATES FROM 20200623 TO 20200914;REEL/FRAME:054667/0827

Owner name: SCANIA CV AB, SWEDEN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SAERS, ALEXANDER;REEL/FRAME:054668/0091

Effective date: 20180129

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER