SE1650103A1 - Method and entity for matching a vehicle with a trailer - Google Patents

Abstract

Method (300) and vehicle external entity (250) for composing a vehicle combination (120) of a vehicle (100) and a trailer (110-1). The method (300) comprises: collecting (301) odometer data and vehicle ID of the vehicle (100); collecting (302) odometer data and trailer ID of each trailer (110-1, 110-2, 110-3) in a set of trailers (130); storing (303) the odometer data in a database (280), associated with the respective vehicle/ trailer ID; determining (304) service interval for the vehicle (100)/ trailers (110-1, 110-2, 110-3); determining (305) when service is due for the vehicle (100) and each respective trailer (110-1, 110-2, 110-3), based on collected (301, 302) odometer data and the determined (304) service intervals; matching (307) the vehicle (100) with one trailer (110-1, 110-2, 110-3), based on correspondence in the determined (305) respective moment when service is due; and outputting (308) a recommendation concerning which trailer (110-1, 110-2, 110-3) to utilise.(Publ. Fig. 2)

Description

METHOD AND ENTITY FOR MATCHING A VEHICLE WITH A TRAILER TECHNICAL FIELD This document discloses a vehicle external entity and a method. I\/|ore particularly, a vehicleexternal entity and a method is provided, for composing a vehicle combination of a vehicleand a trailer.

BACKGROUND A vehicle combination comprises one vehicle and one or more trailers. However, the vehicle/truck and the trailer typically have different service intervals. The trailer may not require ser-vice as frequently as the truck. Thus the driver normally has to drive the vehicle combinationtwice to service, firstly for service at the vehicle and at a later moment for service at thetrailer. This reduces the operative time of the vehicle combination.

Alternatively, service and maintenance may be made earlier than required for being morerational (not having to return to the workshop twice). However, seen over a longer time pe-riod, this means that more service and maintenance is made than actually required, also reducing the operative time of the vehicle combination.

Further, trailers often do not have any odometer. Thus the service interval of the trailer maybe made based on a time period (e.g. every second year), while the vehicle has a serviceinterval counted in mileage. Alternatively, the service interval may be only roughly estimated.

Document US 2013/0338855 A1 discloses a system for processing fleet vehicle operationinformation. However, the document does not discuss matching of vehicle and truck, based on coinciding service intervals.

Document DE102012023968 discloses a system for transferring information, such as e.g.mileage, from a trailer via a truck to a global database. However, the document does notdiscuss matching of vehicle and truck based on coinciding service intervals. lt appears that further improvement may be made for increasing the operative time of a ve- hicle combination.

SUMMARY lt is therefore an object of this invention to solve at least some of the above problems andprovide a method for composing a vehicle combination of a vehicle and a trailer.

According to a first aspect of the invention, this objective is achieved by a method for com-posing a vehicle combination of a vehicle and a trailer. The method comprises coilectingodometer data and vehicle identification data of the vehicle. Further the method comprisescoilecting odometer data and trailer identification data of each trailer in a set of trailers. Themethod also comprises storing the collected odometer data in a database, associated withthe respective vehicle/ trailer identification data. ln addition, the method also comprises de-termining service interval for the vehicle and the trailers in the set of trailers. Further themethod comprises determining a moment when service is due for the vehicle and each re-spective trailer, based on the collected odometer data and the determined service intervals.The method also comprises matching the vehicle with one trailer from the set of trailers,based on correspondence in the determined respective moment when service is due. Also,the method comprises outputting a recommendation to the driver of the vehicle concerningwhich trailer to utilise when composing the vehicle combination, based on the matching.

According to a second aspect of the invention, this objective is achieved by a vehicle externalentity, configured for composing a vehicle combination comprising a vehicle and a trailer.The vehicle external entity comprises a receiver, configured for coilecting odometer data andvehicle identification data of the vehicle, and for coilecting odometer data and trailer identifi-cation data of each trailer in a set of trailers. Further the vehicle external entity comprises adatabase configured for storing the collected odometer data, associated with the respectivevehicle/ trailer identification data. ln addition, the vehicle external entity comprises a compu-ting unit, configured for determining service interval for the vehicle and the trailers, and fordetermining a moment when service is due for the vehicle and each respective trailer, basedon the collected odometer data and the determined service intervals, and configured formatching the vehicle with one trailer from the set of trailers, based on correspondence in thedetermined respective moment when service is due. The vehicle external entity in additioncomprises a transmitter configured for outputting a recommendation to the driver of the ve-hicle concerning which trailer to utilise when composing the vehicle combination, based onthe matching.

Thanks to the described aspects, by estimating remaining period to the next service occasionfor the vehicle as well as for the available trailer, and put together a combination of vehicleand trailer that have a coinciding next service occasion (within a time interval), service couldbe made at the same occasion on both the vehicle and the trailer. Thereby, it could beavoided that the vehicle combination has to be brought to service at two different occasions.Thus the operational time period of the vehicle combination is extended.

Other advantages and additional novel features will become apparent from the subsequentdetailed description.

FIGURES Embodiments of the invention will now be described in further detail with reference to the accompanying figures, in which: Figure 1A illustrates an embodiment of a vehicle combination; Figure 1B illustrates an embodiment of a vehicle combination; Figure 2 illustrates a vehicle interior according to an embodiment; Figure 3 is a flow chart illustrating an embodiment of the method; Figure 4 is an illustration depicting a system according to an embodiment.

DETAILED DESCRIPTION Embodiments of the invention described herein are defined as a vehicle external entity anda method, which may be put into practice in the embodiments described below. These em-bodiments may, however, be exemplified and realised in many different forms and are not tobe limited to the examples set forth herein; rather, these illustrative examples of embodi-ments are provided so that this disclosure will be thorough and complete.

Still other objects and features may become apparent from the following detailed description,considered in conjunction with the accompanying drawings. lt is to be understood, however,that the drawings are designed solely for purposes of illustration and not as a definition ofthe limits of the herein disclosed embodiments, for which reference is to be made to theappended claims. Further, the drawings are not necessarily drawn to scale and, unless oth-en/vise indicated, they are merely intended to conceptually illustrate the structures and pro-cedures described herein.

Figure 1A illustrates a vehicle combination 120 of a vehicle 100 and a trailer 110-1.ln some embodiments, the vehicle combination 120 may comprise one vehicle 100 and aplurality of trailers 110-1, such as e.g. 2, 3, etc. The vehicle 100 may be a truck or similar vehicle and the attached trailer 110-1 may be arranged for transportation on a road.

However, the vehicle combination 120 may alternatively be running on rails, and comprise a train and a railway wagon; a tram with attached wagons; a subway train; a cargo tram, etc.

The vehicle 100 may be driver controlled or driverless autonomously controlled vehicles indifferent embodiments. However, for enhanced clarity, the vehicle 100 is subsequently de-scribed as having a driver.

The vehicle 100 and the trailer 110-1 are exchanging information over a datalink, e.g. via abus such as e.g. a Controller Area Network (CAN) bus, a Media Oriented Systems Transport(MOST) bus, or similar. However, the datalink may alternatively be made over a wirelessconnection comprising, or at least be inspired by wireless communication technology suchas Wi-Fi, Wireless Local Area Network (WLAN), Ultra Mobile Broadband (UI\/IB), Bluetooth(BT), Near Field Communication (NFC), Radio-Frequency Identification (RFID), optical com-munication such as lnfrared Data Association (lrDA) or infrared transmission to name but a few possible examples of wireless communications in some embodiments. ln some embodiments, the communication between the vehicle 100 and the trailer 110-1 inthe vehicle combination 120 may be performed via vehicle-to-vehicle (V2V) communication,e.g. based on Dedicated Short-Range Communications (DSRC) devices. DSRC may workin 5.9 GHz band with bandwidth of 75 l\/IHz and approximate range of 1000 m in some em-bodiments.

The wireless communication may alternatively be made according to any IEEE standard forwireless vehicular communication like e.g. a special mode of operation of IEEE 802.11 forvehicular networks called Wireless Access in Vehicular Environments (WAVE). IEEE802.11p is an extension to 802.11 Wireless LAN medium access layer (l\/IAC) and physicallayer (PHY) specification. ln some cases, the trailer 110-1 may have an own odometer for measuring driving distanceof the trailer 110-1. This odometer data may be exchanged via the data link, together withan identification reference of the trailer 110-1.

Further, the vehicle 100 may have a global wireless connection, e.g. comprising any of theabove mentioned wireless communication interfaces, where information concerning vehicles 100, trailers 110-1, including also other vehicles and trailers and/ or databases are enabled.

Thus the vehicle 100 may read the odometer data from the trailer 110-1, together with theidentification reference of the trailer 110-1, and thereafter storing this information in a globaldatabase, e.g. togetherwith the odometer data/ identification reference of the vehicle 100. ln some cases, the trailer 110-1 may not have an odometer. However, according to someembodiments, the vehicle 100 may measure distance travelled of the trailer 110-1, from themoment of engagement and until disengagement of the trailer 110-1. The measured traveldistance may then be stored together with the identification reference of the trailer 110-1 inthe global database. Thus odometer data of the trailer 110-1 may be accumulated and storedin the database, also when the trailer 110-1 is engaged with different vehicles, also when thetrailer 110-1 does not have any own odometer. ln case the accumulated travelled distance of the trailer 110-1 is not known the first timewhen the trailer 110-1 is engaged with the vehicle 100, the driver may make an estimationand enter this information into the database via an input device in the vehicle 100 such ase.g. a touch screen.

Figure 1B illustrates the vehicle 100 and a plurality of trailers 110-1, 110-2, 110-3 in a set oftrailers 130.

Information concerning odometer data of both vehicles 100 and trailers 110-1, 110-2, 110-3are stored together with the respective identification reference in a vehicle external database.This database storage update may be made continuously or at predetermined or configura-ble time intervals in different embodiments. Alternatively, an update may be made, initiatedby the driver of the vehicle 100, or when the vehicle 100/ trailer 110-1, 110-2, 110-3 is situ-ated at a workshop, a transport centre or garage.

Further, a matching may be made, for matching service interval and remaining mileage/ timeto the next service, in order to compose a vehicle combination 120, where the vehicle 100and the trailer 110-1 could be driven to the workshop for service and maintenance simulta-neously. A recommendation may be provided to the driver of the vehicle 100, which trailer110-1, 110-2, 110-3 in the set 130 to select. Thereby, the operative time of the vehicle com-bination 120 is increased, as the vehicle 100 and the trailer 110-1 go to service simultane- ously.

The service as discussed herein may comprise e.g. maintenance of the vehicle 100/ trailer110-1, 110-2, 110-3; periodic motor vehicle inspection; safety inspection; vehicle cleaning; tire pressure filling; brake maintenance, or similar.

Further, in some embodiments, the future distance the vehicle 100/ vehicle combination 120will travel during the next mission, based on navigation data extracted from a navigator inthe vehicle 100.

Figure 2 illustrates an example of a scenario as it may be perceived by the driver of thevehicle 100 at a moment when the driver desires to compose a vehicle combination 120when preparing a transport mission.

The vehicle 100 comprises a communication unit 210. The communication unit 210 is con-figured for communication with a vehicle external entity 250. The vehicle external entity 250comprises a communication unit 260, a computing unit 270 and a database 280.

The communication between the communication unit 210 of the vehicle 100 and the com-munication unit 260 of the vehicle external entity 250 may be made via a wireless communi-cation interface, e.g. any of the previously mentioned, or at least partly be based on or in-spired by radio access technologies such as, e.g., 3rd Generation Partnership Project(SGPP) Long Term Evolution (LTE), LTE-Advanced, Evolved Universal Terrestrial Radio Ac-cess Network (E-UTRAN), Universal Mobile Telecommunications System (UMTS), Wide-band Code Division Multiple Access (WCDMA), etc.

Alternatively, the communication between the communication unit 210 of the vehicle 100 andthe communication unit 260 of the vehicle external entity 250 may be made via a wired com-munication interface, e.g. when the vehicle 100 is situated at a transportation garage,transport centre or similar.

As described above, odometer data of vehicles 100 and trailers 110-1, 110-2, 110-3 in a setof trailers 130 belonging to the same carrier are continuously collected and stored in thedatabase 280, together with identification data of the respective vehicle 100/ trailer 110-1,110-2, 110-3. Possibly in some embodiments, an indication may be stored associated withthe identification data of each trailer 110-1, 110-2, 110-3, indicating which vehicles 100 it fitsto. Vehicles 100 may have different types (sizes) of drawbars, which may not be compatiblewith all trailers 110-1, 110-2, 110-3 in the set 130. Further, some trailers 110-1, 110-2, 110-3 may not be available due to e.g. that they are occupied by another vehicle, temporarily on service or malfunctioning.

Further the database 280 comprises information regarding service interval of each respec-tive vehicle 100 and trailer 110-1, 110-2, 110-3, respectively. The service internal may be in mileage and/ or in time.

The service may be e.g. maintenance of the vehicle 100 and trailer 110-1, 110-2, 110-3,respectively; periodic motor vehicle inspection; safety inspection; vehicle cleaning; tire pres-sure filling and/ or brake maintenance, etc.

When the driver of the vehicle 100 sends a request to the vehicle external entity 250 (whichmay be explicit or implicit), the computing unit 270 extracts the stored odometer data andservice interval from the database 280. The computing unit 270 may then compute the re-maining period (in mileage or time) to the next service for the vehicle 100.

A computation may then be made by the computing unit 270, for finding a trailer 1 10-1, 110-2, 110-3 having a corresponding remaining period (in mileage or time) to the next service asthe vehicle 100.

A recommendation may then be transmitted to the vehicle 100, to be received via the com-munication unit 210 in the vehicle 100. The received recommendation may be presented tothe driver e.g. on a display 230, via a loudspeaker 240, via a plurality of devices 230, 240 or in a similar manner.

Further, the vehicle 100 may comprise a navigator 220. ln some embodiments, the compu-ting unit 270 may further be configured for extracting a distance for a subsequent round triptravel of the vehicle 100 from the vehicle navigator 220. Thereby, the matching betweenvehicle 100 and trailer 110-1, 110-2, 110-3 may be made such that it is avoided that serviceis due while driving on the extracted distance.

Figure 3 illustrates an example of a method 300 according to an embodiment, for composinga vehicle combination 120 of a vehicle 100 and a trailer 110-1. The method 300 aims atcomposing the vehicle combination 120 in such a way that the next service occasion for thevehicle 100 and the trailer 110-1 coincide (within a predetermined or configurable interval indistance or time).

The vehicle 100 may comprise any kind of means for conveyance, such as e.g. a truck, abus, a car, a train, a tram, a trolley car, or similar.

The vehicle combination 120 may comprise one vehicle 100 and one trailer 110-1, 110-2,110-3, or alternatively a plurality of trailers 110-1, 110-2, 110-3. ln order to compose the vehicle combination 120, the method 300 may comprise a numberof steps 301-308. However, some of these steps 301-308 may be performed solely in some alternative embodiments, like e.g. step 306. Further, the described steps 301-308 may beperformed in a somewhat different chronological order than the numbering suggests. Themethod 300 may comprise the subsequent steps: Step 301 comprises collecting odometer data and vehicle identification data of the vehicle100.

The collection may be triggered or initiated by the driver of the vehicle 100 in some embodi-ments, when the driver desires to compose the vehicle combination 120 by selecting one ormore trailers 110-1, 110-2, 110-3.

The odometer data and vehicle identification data of the vehicle 100 is collected by a vehicleexternal entity 250 over a wired or wireless connection as previously exemplified, continu-ously or at certain moments or when arriving to certain places such as a driving central, garage or similar.

Step 302 comprises collecting odometer data and trailer identification data of each trailer110-1, 110-2, 110-3 in a set of trailers 130.

Odometer data of the trailer 1 10-1, 110-2, 110-3 may be collected by collecting 301 odometerdata from an odometer of a vehicle 100 engaged with the trailer 110-1, 110-2, 110-3, from a moment of engagement until a moment of disengagement.

Thereby, mileage of the trailer 110-1, 110-2, 110-3 may be collected and stored in additionto previously stored odometer data, measured by another vehicle, in some embodiments.

The odometer data and trailer identification data of the trailers 110-1, 110-2, 110-3 may becollected by the vehicle external entity 250, e.g. continuously and/ or by sending a requestto each trailer 110-1, 110-2, 110-3 in the set of trailers 130.

Step 303 comprises storing the collected 301, 302 odometer data in a database 280, asso-ciated with the respective vehicle/ trailer identification data.

The odometer data of the trailer 110-1, 110-2, 110-3 may be stored in the database 280associated with the trailer identity, in case the trailer 110-1, 110-2, 110-3 lacks an odometer.

Accumulated odometer data of the trailer 110-1, 110-2, 110-3 may be estimated and storedin the database 280 the first time the trailer 110-1, 110-2, 110-3 is engaged with the vehicle100.

Step 304 comprises determining service interval for the vehicle 100 and the trailers 110-1,110-2, 110-3 in the set of trailers 130.

The service interval of the vehicle 100 and the trailers 110-1, 110-2, 110-3 in the set of trailers130 may be determined by distance travelled and/ or time interval.

Step 305 comprises determining a moment when service is due for the vehicle 100 and eachrespective trailer 110-1, 110-2, 110-3, based on the collected 301, 302 odometer data andthe determined 304 service intervals.

The service may comprise maintenance of the vehicle 100/ trailer 110-1, 110-2, 110-3; peri-odic motor vehicle inspection; safety inspection; vehicle cleaning; tire pressure filling; brake maintenance or similar.

Step 306 which may be performed only in some embodiments, comprises extracting a dis-tance for a subsequent round trip travel of the vehicle 100. lt may thereby be planned that the service for both the vehicle 100 and the trailer 110-1, 110-2, 110-3 is due at the return from the travel.

Step 307 comprises matching the vehicle 100 with one trailer 110-1, 110-2, 110-3 from theset of trailers 130, based on correspondence in the determined 305 respective moments when service is due.

Further, in some embodiments, the matching may be made for avoiding that service is duewhile driving on the extracted distance.

Step 308 comprises outputting a recommendation to the driver of the vehicle 100 concerningwhich trailer 110-1, 110-2, 110-3 to utilise when composing the vehicle combination 120,based on the matching 307.

Figure 4 illustrates an embodiment of a vehicle external entity 250. The vehicle externalentity 250 may perform at least some of the previously described steps 301-308 accordingto the method 300 described above and illustrated in Figure 3. Thus the vehicle external entity 250 aims at composing the vehicle combination 120 in such a way that the next serviceoccasion for the vehicle 100 and the trailer 110-1 coincide.

The vehicle external entity 250 is configured for composing a vehicle combination 120 com-prising the vehicle 100 and at least one trailer 110-1, 110-2, 110-3. The vehicle externalentity 250 comprises a receiver 260 configured for collecting odometer data and vehicleidentification data of the vehicle 100, and for collecting odometer data and trailer identifica-tion data of each trailer 110-1, 110-2, 110-3 in a set of trailers 130.

Further the vehicle external entity 250 comprises a database 280 configured for storing thecollected odometer data, associated with the respective vehicle/ trailer identification data. ln addition the vehicle external entity 250 comprises a computing unit 270, configured fordetermining service interval for the vehicle 100 and the trailers 110-1, 110-2, 110-3, and fordetermining a moment when service is due for the vehicle 100 and each respective trailer110-1, 110-2, 110-3, based on the collected odometer data and the determined service in-tervals, and configured for matching the vehicle 100 with one trailer 1 10-1, 110-2, 110-3 fromthe set of trailers 130, based on correspondence in the determined respective moment when service is due.

Additionally, the vehicle external entity 250 comprises a transmitter 260 configured for out-putting a recommendation to the driver of the vehicle 100 concerning which trailer 110-1,110-2, 110-3 to utilise when composing the vehicle combination 120, based on the matching.

The described receiver/ transmitter 260 may comprise one combined physical unit, i.e. atransceiver 260, in some embodiments.

The computing unit 270 may further be configured for extracting a distance for a subsequentround trip travel of the vehicle 100 from a vehicle navigator 220. Further, according to someembodiments, the computing unit 270 may also be configured for making the matching suchthat it is avoided that service is due while driving on the extracted distance. ln some embodiments, the computing unit 270 may be configured for collecting odometerdata of the trailer 110-1, 110-2, 110-3 by collecting odometer data from an odometer of avehicle 100 engaged with the trailer 110-1, 110-2, 110-3, from a moment of engagement until a moment of disengagement. 11 The computing unit 270 may comprise a processor. Such processor may comprise one ormore instances of a processing circuit, i.e. a Central Processing Unit (CPU), a processingunit, an Application Specific Integrated Circuit (ASIC), a microprocessor, or other processinglogic that may interpret and execute instructions. The herein utilised expression “processor”may thus represent a processing circuitry comprising a p|ura|ity of processing circuits, suchas, e.g., any, some or all of the ones enumerated above.

Further, the computing unit 270 may further comprise a memory in some embodiments. Theoptional memory may comprise a physical device utilised to store data or programs, i.e.,sequences of instructions, on a temporary or permanent basis. According to some embodi-ments, the memory may comprise integrated circuits comprising silicon-based transistors.The memory may comprise e.g. a memory card, a flash memory, a USB memory, a harddisc, or another similar volatile or non-volatile storage unit for storing data such as e.g. ROIVI(Read-Only Memory), PROIVI (Programmable Read-Only Memory), EPROIVI (ErasablePROIVI), EEPROIVI (Electrically Erasable PROIVI), etc. in different embodiments.

The database 280 may be configured for storing odometer data of the trailer 110-1, 110-2,110-3 in the database 280 associated with the trailer identity, in case the trailer 110-1, 110-2, 110-3 lacks an odometer, in some embodiments.

The accumulated odometer data of the trailer 110-1, 110-2, 110-3 may be estimated andstored in the database 280 the first time the trailer 110-1, 110-2, 110-3 is engaged with thevehicle 100, in some embodiments, e.g. by the driver of the vehicle 100.

The previously described steps 301-308 to be performed in the vehicle external entity 250,may be implemented through the one or more processors in the computing unit 270, togetherwith computer program product for performing at least some of the functions of the steps301 -308. Thus a computer program product, comprising instructions for performing the steps301-308 in the vehicle external entity 250 may perform the method 300 comprising at leastsome of the steps 301 -308 for composing the vehicle combination 120 comprising the vehicle100 and at least one trailer 110-1, 110-2, 110-3, when the computer program is loaded intothe one or more processors of the computing unit 270 of the vehicle external entity 250.

The described steps 301-308 thus may be performed by a computer algorithm, a machineexecutable code, a non-transitory computer-readable medium, or a software instructions pro-grammed into a suitable programmable logic such as the processor in the computing unit270. 12 The computer program product mentioned above may be provided for instance in the formof a data carrier carrying computer program code for performing at least some of the step301-308 according to some embodiments when being loaded into the one or more proces-sors of the vehicle external entity 250. The data carrier may be, e.g., a hard disk, a CD ROIVIdisc, a memory stick, an optical storage device, a magnetic storage device or any otherappropriate medium such as a disk or tape that may hold machine readable data in a non-transitory manner. The computer program product may furthermore be provided as computerprogram code on a server and downloaded to the computing unit 270 remotely, e.g., over an Internet or an intranet connection.

The terminology used in the description of the embodiments as illustrated in the accompa-nying drawings is not intended to be limiting of the described method 300, vehicle externalentity 250 and/ or computer program. Various changes, substitutions and/ or alterations maybe made, without departing from invention embodiments as defined by the appended claims.

As used herein, the term "and/ or" comprises any and all combinations of one or more of theassociated listed items. The term “or” as used herein, is to be interpreted as a mathematicalOR, i.e., as an inclusive disjunction; not as a mathematical exclusive OR (XOR), unless ex-pressly stated otherwise. ln addition, the singular forms "a", "an" and "the" are to be inter-preted as “at least one", thus also possibly comprising a plurality of entities of the same kind,unless expressly stated othen/vise. lt will be further understood that the terms "includes","comprises", "including" and/ or "comprising", specifies the presence of stated features, ac-tions, integers, steps, operations, elements, and/ or components, but do not preclude thepresence or addition of one or more other features, actions, integers, steps, operations, ele-ments, components, and/ or groups thereof. A single unit such as e.g. a processor may fulfilthe functions of several items recited in the claims. The mere fact that certain measures arerecited in mutually different dependent claims does not indicate that a combination of thesemeasures cannot be used to advantage. A computer program may be stored/ distributed ona suitable medium, such as an optical storage medium or a solid-state medium suppliedtogether with or as part of other hardware, but may also be distributed in other forms such as via Internet or other Wired or wireless communication system.

Claims (12)

1. A method (300) for composing a vehicle combination (120) of a vehicle (100) and atrailer (110-1), which method (300) comprises: collecting (301) odometer data and vehicle identification data of the vehicle (100); collecting (302) odometer data and trailer identification data of each trailer (110-1,110-2, 110-3) in a set of trailers (130); storing (303) the collected (301 , 302) odometer data in a database (280), associatedwith the respective vehicle/ trailer identification data; determining (304) service interval for the vehicle (100) and the trailers (110-1, 110-2, 110-3) in the set of trailers (130); determining (305) a moment when service is due for the vehicle (100) and eachrespective trailer (110-1, 110-2, 110-3), based on the collected (301, 302) odometer dataand the determined (304) service intervals; matching (307) the vehicle (100) with one trailer (110-1, 110-2, 110-3) from the setof trailers (130), based on correspondence in the determined (305) respective moment whenservice is due; and outputting (308) a recommendation to the driver of the vehicle (100) concerningwhich trailer (110-1, 110-2, 110-3) to utilise when composing the vehicle combination (120),based on the matching (307).

2. The method (300) according to claim 1, further comprising: extracting (306) a distance for a subsequent round trip travel of the vehicle (100);and wherein the matching (307) is made for avoiding that service is due while driving on theextracted distance.

3. The method (300) according to any of claim 1 or claim 2, wherein odometer data ofthe trailer (110-1, 110-2, 110-3) is collected (302) by collecting (301) odometer data from anodometer of a vehicle (100) engaged with the trailer (110-1, 110-2, 110-3), from a momentof engagement until a moment of disengagement; which odometer data of the trailer (1 10-1,1 10-2, 1 10-3) is stored (303) in the database (280) associated with the trailer identity, in casethe trailer (110-1, 110-2, 110-3) lacks an odometer.

4. The method (300) according to claim 3, wherein accumulated odometer data of thetrailer (1 10-1, 110-2, 110-3) is estimated and stored (303) in the database (280) the first timethe trailer (110-1, 110-2, 110-3) is engaged with the vehicle (100).

5. The method (300) according to any of claims 1-4, wherein the vehicle combination(120) comprises one vehicle (100) and a plurality of trailers (110-1, 110-2, 110-3). 14

6. The method (300) according to any of claims 1-5, wherein the service interval of thevehicle (100) and the trailers (110-1, 110-2, 110-3) in the set of trailers (130) is determined(304) by distance travelled and/ or time interval.

7. The method (300) according to any of claims 1-6, wherein the service comprises:maintenance of the vehicle (1 00)/ trailer (1 1 0-1, 110-2, 110-3); periodic motor vehicle inspec-tion; safety inspection; vehicle cleaning; tire pressure filling; brake maintenance.

8. A vehicle external entity (250), configured for composing a vehicle combination(120) comprising a vehicle (100) and a trailer (110-1, 110-2, 110-3), which vehicle externalentity (250) comprises: a receiver (260) configured for collecting odometer data and vehicle identificationdata of the vehicle (100), and for collecting odometer data and trailer identification data ofeach trailer (110-1, 110-2, 110-3) in a set of trailers (130); a database (280) configured for storing the collected odometer data, associated withthe respective vehicle/ trailer identification data; a computing unit (270), configured for determining service interval for the vehicle(100) and the trailers (110-1, 110-2, 110-3), and for determining a moment when service isdue for the vehicle (100) and each respective trailer (110-1, 110-2, 110-3), based on thecollected odometer data and the determined service intervals, and configured for matchingthe vehicle (100) with one trailer (110-1, 110-2, 110-3) from the set of trailers (130), basedon correspondence in the determined respective moment when service is due; and a transmitter (260) configured for outputting a recommendation to the driver of thevehicle (100) concerning which trailer (110-1, 110-2, 110-3) to utilise when composing thevehicle combination (120), based on the matching.

9. The vehicle external entity (250) according to claim 8 wherein the computing unit(270) is further configured for extracting a distance for a subsequent round trip travel of thevehicle (100) from a vehicle navigator (220); and also configured for making the matchingsuch that it is avoided that service is due while driving on the extracted distance.

10.computing unit (270) is further configured for collecting odometer data of the trailer (110-1, The vehicle external entity (250) according to any of claim 8 or claim 9 wherein the 110-2, 110-3) by collecting odometer data from an odometer of a vehicle (100) engaged withthe trailer (110-1, 110-2, 110-3), from a moment of engagement until a moment of disen-gagement; and wherein the database (280) is further configured for storing odometer data of the trailer (110-1, 110-2, 110-3) in the database (280) associated with the trailer identity,in case the trailer (110-1, 110-2, 110-3) lacks an odometer.

11. The vehicle external entity (250) according to claim 10 wherein accumulated odom-5 eter data of the trailer (110-1, 110-2, 110-3) is estimated and stored in the database (280)the first time the trailer (110-1, 110-2, 110-3) is engaged with the vehicle (100).

12. A computer program comprising program code for performing a method (300) ac-cording to any of claims 1-7, when the computer program is executed in a vehicle external10 entity (250) according to any of claims 8-11.