Service device for vehicle
The vehicle service device addresses smart key loss and battery monitoring issues by integrating a control PCB with charging and communication features, enabling remote battery management and keyless service usage.
Patent Information
- Application Number
- JP2024196240
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-07-16
- Filing Date
- 2024-11-08
- Publication Date
- 2026-01-28
- Estimated Expiration
- 2044-11-08
AI Technical Summary
The frequent loss of smart keys and the inability to monitor vehicle battery charge outside the vehicle, especially during extended non-operation periods, cause inconvenience and inefficiency in vehicle services.
A vehicle service device with a case, lid, locker, and support base, containing a control PCB that measures battery charge and temperature, communicates with a driver's terminal, and operates without external power, featuring a charging module, battery remaining capacity measurement module, and temperature sensor to predict battery discharge.
Prevents smart key loss and allows remote monitoring of battery condition, ensuring timely action to avoid discharge, simplifying vehicle service usage by eliminating the need for key exchange and enhancing battery management.
Smart Images

Figure 2026013341000001_ABST
Abstract
Description
[Technical Field]
[0001] The present invention relates to a vehicle service device, and more particularly to a vehicle service device that can check the remaining charge of a vehicle battery. [Background technology]
[0002] As vehicle ownership rates increase, smart key systems for vehicles are becoming more common. Smart keys allow drivers to open and close doors and trunks from outside the vehicle without using a vehicle key. When the smart key is detected as being inside the vehicle, the vehicle can be started using the start button without operating the smart key.
[0003] The smart key is linked to the vehicle's interior antenna via an encrypted radio frequency, and the vehicle can be operated in response to the operation of the smart key only if the wirelessly transmitted encryption code matches that of the smart key and the interior antenna.
[0004] The demand for smart key systems is increasing due to the convenience of opening, closing and starting doors, and various similar products have been released.
[0005] However, the driver must always carry the smart key. Because smart keys are small, drivers often do not check to see if they have the smart key when they are not operating the vehicle. This has led to the problem of frequent smart key loss incidents.
[0006] In addition, there are various vehicle-related services such as designated driving services, car wash services, maintenance services, etc. Hereinafter, services provided to vehicles will be referred to as "vehicle services."
[0007] To use such vehicle services, the vehicle owner must leave the smart key with the service provider or service operator.
[0008] Additionally, the smart key must always be returned on-site after the service is completed.
[0009] For example, if a person wants to use a designated driving service, they must wait at the vehicle's location until the designated driver arrives. Therefore, if the vehicle owner is far away from the vehicle, they cannot use the pickup service.
[0010] Furthermore, when using a vehicle maintenance service, the vehicle owner must wait in the vehicle until the vehicle maintenance company comes to collect the vehicle. Furthermore, when the vehicle maintenance company returns the vehicle to the owner, the vehicle owner must wait at the return location. In other words, when using a vehicle maintenance service, the vehicle owner must constantly coordinate meeting schedules between the vehicle owner and the vehicle maintenance company when leaving the vehicle for repair and when returning the vehicle, which is inconvenient. To avoid this inconvenience, the vehicle owner may leave the smart key in the vehicle when leaving the vehicle for repair. In other words, due to this inconvenience, the vehicle owner may also return the vehicle without retrieving the smart key and leave the smart key there.
[0011] In addition, recent vehicles are equipped with a function that checks the remaining battery charge and notifies the driver when the battery is low, but this is limited to notifications within the vehicle, and there is a problem in that it is not possible to check the vehicle's battery in situations where the vehicle will not be operated for an extended period of time, making it impossible to perform preemptive battery management. [Prior art documents] [Patent documents]
[0012] [Patent Document 1] Korean Patent No. 10-1101293 (Announced on January 4, 2012) [Patent Document 2] Korean Patent Publication No. 10-2016-0051284 (Published on May 11, 2016) Summary of the Invention [Problem to be solved by the invention]
[0013] The present invention is intended to solve the problems of the prior art described above, and its purpose is to provide a vehicle service device that can prevent the smart key from being lost, and to provide a device that allows the vehicle battery condition to be easily checked using the vehicle service device.
[0014] Another object of the present invention is to provide a vehicle service device that can be used for various vehicle-specific smart keys.
[0015] Another object of the present invention is to provide a vehicle service device that is easy to assemble.
[0016] Another object of the present invention is to provide a vehicle service device that can operate without an external power source.
[0017] Another object of the present invention is to provide a vehicle service device that can be easily fixed to a vehicle.
[0018] Another object of the present invention is to eliminate the need to provide and collect a vehicle smart key when using a vehicle service. [Means for solving the problem]
[0019] In order to achieve the above object, the vehicle service device of the present invention includes a case, a lid, a locker, and a support base, wherein the case includes a case body, a locker groove, a lid connecting portion, a support base mounting portion, a PCB fixing portion, a battery mounting portion, a control PCB, and a battery, wherein the case body accommodates the control PCB and the battery in an accommodation space formed therein, one side of the case body is open to mount the support base, and the other side is formed with a locker groove into which the locker is fitted, and the control PCB includes a charging module that charges the battery using power from the vehicle battery, a battery remaining capacity measurement module that detects the charging state of the battery, a PCB control unit that controls the charging module using the detection result of the battery remaining capacity measurement module and estimates the state of the vehicle battery, and a communication unit that transmits the estimation result of the PCB control unit to a driver's terminal.
[0020] In an embodiment of the present invention, the control PCB further includes a temperature sensor that detects the temperature of the battery, and when the temperature detected by the temperature sensor is equal to or higher than a reference temperature, the control PCB can operate a heat dissipation fan and transmit temperature information of the battery to the terminal via the communication unit.
[0021] In an embodiment of the present invention, the PCB control unit may estimate the state of the vehicle battery based on the charge amount of the battery charged during a reference time.
[0022] In an embodiment of the present invention, the PCB control unit can estimate the state of the vehicle battery as "normal," "slightly bad," "bad," or "very bad" by dividing the battery charging rate based on the rate at which the battery is normally charged within a set reference time.
[0023] In an embodiment of the present invention, the control PCB may further include a display unit for displaying a result of the vehicle battery state estimation by the PCB control unit.
[0024] In an embodiment of the present invention, the control PCB may charge the battery using the charging module according to the charge level of the battery confirmed by the battery remaining capacity measurement module.
[0025] In an embodiment of the present invention, when the remaining battery charge detected by the battery remaining charge measuring module reaches a lower reference value, the charging module charges the battery using power supplied from the vehicle battery, and when the battery's charge state reaches an upper reference value, the charging module stops charging to prevent the battery from being overcharged. [Effects of the Invention]
[0026] The vehicle service device of the present invention includes a battery remaining capacity measurement module, which detects the battery state of the vehicle and notifies the driver's terminal when the remaining battery capacity is below a reference value.
[0027] The effect is to send a warning so that necessary measures can be taken before the vehicle battery is completely discharged.
[0028] In particular, the present invention predicts the time when a vehicle battery will be fully discharged and provides the prediction result to the driver's terminal, thereby informing the driver of the time that the driver must restart the vehicle after turning it off before discharging. This has the effect of ensuring reliability in battery management and preventing economic and time losses due to the battery being fully discharged.
[0029] Furthermore, by installing a vehicle service device with a built-in vehicle smart key inside the vehicle, the present invention allows the vehicle to be controlled using a user's terminal via wireless communication, thereby preventing the vehicle smart key from being lost.
[0030] In addition, the present invention is provided with a PCB fixing base compatible with various vehicle-specific smart keys, and has versatility for various vehicle-specific smart keys by using a holder that can be attached and detached to the support base.
[0031] Furthermore, the present invention enables easy assembly without the need for skilled workers by connecting PCBs built into vehicle service devices by fitting them together, thereby preventing damage to PCBs that may occur during the process of connecting PCBs (e.g., soldering).
[0032] In addition, the present invention has a battery installed inside the vehicle service device, allowing it to operate without external power and preventing battery discharge by charging the battery using power supplied from the vehicle, thereby preventing situations in which the vehicle smart key becomes unusable due to discharge of the smart key.
[0033] In addition, the present invention has a rocker groove formed on one surface of the case, and the rocker groove is fitted into a rocker provided inside the vehicle, making it possible to easily fix the vehicle service device inside the vehicle.
[0034] In addition, the present invention can be expected to have the effect of eliminating the need to provide and collect a vehicle smart key when using a vehicle service by sharing a virtual key with a vehicle service provider when using a vehicle service. [Brief explanation of the drawings]
[0035] [Figure 1] 1 is a diagram for explaining a vehicle control system according to the present invention; [Figure 2] 1 is a perspective view of a vehicle service device according to the present invention; [Figure 3] 1 is a rear perspective view of a vehicle service device according to the present invention; [Figure 4] FIG. 1 is an exploded rear perspective view of a case and rocker according to the present invention. [Figure 5] FIG. 3 is an exploded perspective view of FIG. 2. [Figure 6] 1 is an exploded cross-sectional view of a vehicle service device according to the present invention; [Figure 7] FIG. 7 is an enlarged view of A shown in FIG. 6. [Figure 8] FIG. 8 is an enlarged view of B shown in FIG. [Figure 9a] FIG. 2 is a perspective view of a connection pin according to the present invention. [Figure 9b] 1 is a cross-sectional view of a connection pin according to the present invention with an electric wire inserted therein; [Figure 9c] 1 is a cross-sectional view of a connection pin according to the present invention to which an electric wire is fixed. [Figure 10] FIG. 10 is a block diagram of a control PCB 170 according to another embodiment of the present invention. [Figure 11] 1 is a schematic diagram of a vehicle service system according to the present invention; [Figure 12] FIG. 12 is a functional block diagram of the first terminal of FIG. [Figure 13] FIG. 12 is a functional block diagram of the first service device of FIG. [Figure 14] FIG. 12 is a functional block diagram of the second service device of FIG. [Figure 15] FIG. 12 is a functional block diagram of the second terminal of FIG. [Figure 16] 12 is a flowchart showing a vehicle service providing method in the vehicle service system of FIG. 11. DETAILED DESCRIPTION OF THE INVENTION
[0036] Since the present invention can be modified in various ways and can have various embodiments, specific embodiments will be illustrated in the drawings and described in detail. However, it should be understood that this does not limit the present invention to the specific embodiments, but includes modifications, equivalents, and alternatives within the spirit and technical scope of the present invention.
[0037] In describing the drawings, like reference numerals are used for like elements. When describing the present invention, if it is determined that a detailed description of related known technology may obscure the gist of the present invention, the detailed description will be omitted.
[0038] Terms such as "first" and "second" may be used to describe various components, but the components should not be limited by these terms. These terms are only used to distinguish one component from another.
[0039] For example, a first component could be termed a second component, and similarly, a second component could be termed a first component, without departing from the scope of the present invention.
[0040] The term "and / or" includes a combination of two or more associated listed items or any item of two or more associated listed items.
[0041] When a component is referred to as being "coupled" or "connected" to another component, it should be understood that the component may be directly coupled or connected to the other component, but there may also be other components intervening between the components.
[0042] In contrast, when an element is referred to as being "directly coupled" or "directly connected" to another element, it should be understood that there are no intervening elements between the elements.
[0043] The terms used in this application are merely used to describe particular embodiments and are not intended to limit the present invention.
[0044] The singular expression includes the plural expression unless the context clearly dictates otherwise. In this application, the terms "comprise" or "have" and the like indicate the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, and should be understood not to preclude the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.
[0045] Unless otherwise defined, all terms used herein, including technical and scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs.
[0046] Terms defined in commonly used dictionaries should be interpreted to have a meaning consistent with the meaning they have in the context of the relevant art, and not in an idealized or overly formal sense unless expressly defined in this application.
[0047] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A vehicle service device according to a preferred embodiment of the present invention will be described in detail below with reference to the drawings.
[0048] Fig. 1 is a diagram for explaining a vehicle control system according to the present invention, Fig. 2 is a perspective view of a vehicle service device according to the present invention, Fig. 3 is a rear perspective view of the vehicle service device according to the present invention, Fig. 4 is an exploded rear perspective view of a case and locker according to the present invention, Fig. 5 is an exploded perspective view of Fig. 2, Fig. 6 is an exploded cross-sectional view of the vehicle service device according to the present invention, Fig. 7 is an enlarged view of A shown in Fig. 6, Fig. 8 is an enlarged view of B shown in Fig. 7, Fig. 9a is a perspective view of a connection pin according to the present invention, Fig. 9b is a cross-sectional view of a connection pin according to the present invention with an electric wire inserted therein, and Fig. 9c is a cross-sectional view of a connection pin according to the present invention with an electric wire fixed therein. Hereinafter, descriptions of conventionally known matters will be omitted or simplified in order to clarify the gist of the present invention.
[0049] First, a vehicle service device that is applied to the vehicle service system of the present invention will be described.
[0050] Referring to FIG. 1, a vehicle control system 1 to which the present invention is applied may include a vehicle service device 10 , a communication network 20 , and a terminal 30 .
[0051] Specific details of the vehicle service device 10 of the present invention will be described later.
[0052] The communication network 20 may be a connection means for connecting the vehicle service device 10 and the terminal 30, and preferably may be a wireless connection. The communication network 20 for connecting the vehicle service device 10 and the terminal 30 may be a connection using a short-range communication method such as Bluetooth, ZigBee, Wi-Fi, or NFC, and at least one of the short-range communication connection methods may be selectively applied.
[0053] The terminal 30 is not limited to a smartphone or PDA owned by the user, as long as it can be connected to the vehicle service device 10 via the communication network 20. However, it is preferable that the terminal 30 is a smartphone that the user uses on a daily basis and checks whether or not the user has the smartphone.
[0054] Referring to FIG. 2, the vehicle service device 10 may include a case 100 and a lid 200 .
[0055] The case 100 may have an internal storage space and may have one open side. A cover 200 may be coupled to the open side of the case 100.
[0056] The cover 200 may be coupled to one side of the case 100 to form an accommodation space therein. The cover 200 may close the open side of the case 100. The cover 200 may be opened and closed separately from the case 100. Alternatively, the cover 200 may be coupled to one side of the case 100 with a hinge and may be opened and closed in a rotating manner. This prevents dust or foreign matter from entering the inside of the case 100, thereby preventing errors and malfunctions of components accommodated inside the case 100 and preventing damage due to external forces.
[0057] Here, there is no limitation on the form of the lid 200. For example, the lid 200 may be of a form that allows it to be opened and closed from the case 100, such as a slide-opening type.
[0058] 3 and 4, the vehicle service device 10 may include a case 100, a lid 200, and a locker 300.
[0059] The case 100 may include a case body 110 and a rocker groove 120 .
[0060] The case body 110 may have an accommodation space formed therein and may have an open side.
[0061] The rocker groove 120 may be formed on the other surface of the case body 110, and the rocker 300 may be fitted therein.
[0062] The rocker 300 may be provided inside the vehicle and may be formed in a shape corresponding to the rocker groove 120 formed on the other surface of the case body 110. As a result, the rocker 300 is fitted into the rocker groove 120 formed on the other surface of the case body 110, so that the vehicle service device 10 can be easily fixed inside the vehicle.
[0063] 5 to 8, the vehicle service device 10 may include a case 100, a lid 200, a locker 300, and a support base 400.
[0064] The case 100 may include a case body 110 , a rocker groove 120 , a cover coupling portion 130 , a support mounting portion 140 , a PCB fixing portion 150 , a battery mounting portion 160 , a control PCB 170 and a battery 180 .
[0065] The case body 110 may accommodate a control PCB 170 and a battery 180 in an accommodation space formed therein. One side of the case body 110 may be open to accommodate the support 400. The case body 110 may have a rocker groove 120 formed on the other side thereof into which the rocker 300 is fitted.
[0066] The rocker groove 120 may be formed on the other surface of the case body 110, and a rocker 300 provided in the vehicle may be fitted therein, thereby allowing the case 100 to be easily fixed inside the vehicle.
[0067] The lid coupling part 130 may be provided on the inner surface of the case 100. The lid coupling part 130 may be formed in a shape corresponding to the coupling means 220 formed on the lid 200 so that the lid 200 can be coupled thereto, and is not limited to a specific shape or configuration as long as it is possible to couple the case 100 and the lid 200 together. However, in order to easily assemble the lid 200 without using additional tools, it is preferable that the lid coupling part 130 be formed in a shape that allows them to be fitted together.
[0068] The support mounting portion 140 may be formed to protrude from the inner surface of the case body 110 by a predetermined thickness, and the other surface of the support 400 may be mounted thereon.
[0069] The PCB fixing part 150 may be formed to protrude from the support base mounting part 140 by a predetermined length, and by fixing the control PCB 170 housed in the case body 110, it can prevent it from moving back and forth or left and right.
[0070] The battery mounting portion 160 can mount the battery 180 housed inside the case body 110, and can be formed to correspond to the shape of the housed battery 180 to prevent the battery 180 from moving due to external force.
[0071] Here, the battery mounting unit 160 is shown in the drawings to have a shape corresponding to a commonly used cylindrical battery, but is not limited thereto. For example, if a button-type battery or a small battery is used, the battery mounting unit 160 may be omitted. That is, it may be selectively formed according to the shape of the battery, and if a button-type battery or a small battery is used, the battery mounting unit 160 may be omitted, thereby reducing the size of the vehicle service device 10.
[0072] The control PCB 170 may include a control PCB board 171 , a connection section 172 , a communication section 173 , a PCB control section 174 , and a power supply section 175 .
[0073] The control PCB board 171 can be housed inside the case 100 and fixed by the PCB fixing part 150, thereby preventing it from moving back and forth or left and right.
[0074] The connection part 172 may include a number of connection terminals 172 a, which may be connected to the test terminals 443 of the smart key PCB 440 via a number of connection lines EL and a plurality of connection pins 450, respectively.
[0075] The communication unit 173 may provide communication with the terminal 30, for example, a smartphone, and may receive a control signal provided from the smartphone. In this case, a wireless communication standard such as Bluetooth may be applied to the communication between the communication unit 173 and the terminal 30.
[0076] The PCB control unit 174 receives a control signal for each function of the tactile switch 442 from the terminal 30 via the communication unit 173, analyzes the control signal, and provides an electrical signal corresponding to the turning-on of the tactile switch 442 to the test terminal 443. To this end, the PCB control unit 174 converts power supplied from the power supply unit 175 into an electrical signal level corresponding to the turning-on of the tactile switch 442, and then supplies the converted electrical signal to the connection terminal 172a corresponding to the function of the tactile switch 442 recognized by the control signal. At this time, an electrical signal corresponding to the turning-on of the tactile switch 442 can be provided to the test terminal 443 via the connection terminal 172a, the connection line EL, and the connection pin 450. At this time, the turning-on of the tactile switch 442 can be recognized by a control unit on the smart key PCB 440, and the control unit on the smart key PCB 440 can send a control command corresponding to the tactile switch 442 to a main controller (not shown) in the vehicle.
[0077] The power supply unit 175 can receive power from the battery 180 and supply the power to the PCB control unit 174 .
[0078] The battery 180 may be mounted in the battery mounting portion 160 and may be connected to the control PCB 170 to supply power. This allows the vehicle service device 10 to operate using its own power even when the vehicle starter is turned off. The battery 180 may be charged using power supplied from the vehicle, thereby preventing the battery 180 from being discharged and making the vehicle service device 10 unusable. A charging port (not shown) may be provided on one side of the case body 110 to charge the battery using power supplied from the vehicle.
[0079] Here, the battery 180 is illustrated as a commonly used cylindrical battery, but is not limited thereto.
[0080] That is, it can be replaced with various types of batteries such as button batteries and square batteries.
[0081] The cover 200 can accommodate the support 400 in an accommodation space formed therein, and can be coupled to one side of the case 100. By being coupled to one side of the case 100, the cover 200 can prevent the support 400 from coming off from its original position due to vibration or movement of the vehicle. This can prevent the control PCB 170 and the battery 180, which are provided between the case 100 and the support 400, from being subjected to impact or being damaged.
[0082] The cover 200 may have a lamp groove 210 formed at a predetermined position, and a lamp may be inserted into the lamp groove 210. The lamp L may be turned on under the control of the control PCB 170. For example, the lamp L may indicate the presence or absence of an abnormality such as a malfunction or error in the operation of the vehicle control system 1 under the control of the control PCB 170, and the presence or absence of an abnormality in the vehicle service system 1, such as a lack of a built-in battery, may be visually confirmed through the lamp L.
[0083] The lamp L can indicate the error in different colors depending on whether there is an abnormal operation or not, so that the user can take immediate measures to address the cause of the abnormality.
[0084] Since the cover 200 is coupled to one side of the case 100, a coupling means 220 corresponding to the shape of the cover coupling portion 130 of the case 100 may be formed on one side of the cover 200 that is to be coupled to the case 100. The coupling means 220 is not limited to any particular shape or configuration as long as it can be coupled to the cover coupling portion 130. However, it is preferable that the coupling means 220 be formed in a shape that can be fitted together to facilitate assembly without using additional tools.
[0085] The rocker 300 can be attached and fixed inside the vehicle, and can be formed to correspond to the shape of the rocker groove 120 to be fitted into the rocker groove 120 formed on the other surface of the case body 110. This allows the vehicle service device 10 to be easily fixed inside the vehicle.
[0086] The support 400 may include a support body 410 , a battery receiving portion 420 , a holder 430 , a smart key PCB 440 and a connection pin 450 .
[0087] The support body 410 may be provided on one side of the case 100, i.e., the open side of the case 100. The holder 430, to which the smart key PCB 440 is coupled, may be detachably coupled to one side of the support body 410, and the other side may be mounted on the support mount 140. The support body 410 may have a coupling hole 411 formed in a predetermined shape corresponding to the coupling plate 431 of the holder 430 so that the holder 430 can be detachably coupled to one side. The means for assembling the holder 430 to the support body 410 is not limited. For example, when the holder 430 is mounted on the support body 410, a method may be used in which a first screw hole 412 formed in the support body 410 and a second screw hole 435 formed in the outer circumferential surface of the holder 430 at a position corresponding to the first screw hole 412 are coupled with a screw bolt V.
[0088] The battery receiving part 420 may be formed on one side of the support body 410 to correspond to the shape of the battery 180, and may receive the battery 180 received inside the case body 110. The battery receiving part 420 may be coupled to the battery mounting part 160 to receive the battery 180 and prevent the battery 180 from moving due to an external force.
[0089] Here, the battery receiving unit 420, like the battery mount 160, is illustrated in a shape corresponding to a commonly used cylindrical battery, but is not limited thereto. For example, when a button-type battery or a compact battery is used, the battery receiving unit 420 may be eliminated together with the battery mount 160. That is, it may be selectively formed according to the shape of the battery, and when a button-type battery or a compact battery is used, the battery mount 160 and the battery receiving unit 420 may be eliminated, thereby reducing the size of the vehicle service device 10.
[0090] The holder 430 may include a coupling plate 431 , a PCB fixing base 432 , a through hole 433 and a protruding support 434 .
[0091] The connecting plate 431 may be formed in a shape corresponding to the connecting hole 411 formed in the support body 410 and may be detachably connected to the connecting hole 411 .
[0092] The PCB fixing base 432 may be formed on one surface of the coupling plate 431 to have a shape corresponding to the smart key PCB 440 and protrude to a predetermined height, and the smart key PCB 440 may be fitted into the PCB fixing base 432.
[0093] The through-holes 433 may be formed through the coupling plate 431 at positions corresponding to the positions of the test terminals 443 provided on the smart key PCB 440. In addition, the through-holes 433 may have connection pins 450 inserted therein and fixed thereto.
[0094] The protruding support portion 434 may be formed to protrude by a predetermined height from one surface of the coupling plate 431 at a position corresponding to the position of the through hole 433, and may be hollow with the same diameter as the through hole 433. The protruding support portion 434 may receive the connection pin 450 passing through the through hole 433 and support the inserted connection pin 450 to prevent the head 452 of the connection pin 450 from coming off the test terminal 443 to which it is connected. In addition, the protruding support portion 434 may prevent the connection pin 450 from coming off in the direction opposite to the insertion and fixation direction, as a hook 455 formed on a side of the inserted connection pin 450 is fixed by an inner surface of the protruding support portion 434.
[0095] The smart key PCB 440 can be obtained by disassembling a user's existing smart key. The smart key PCB 440 can include a smart key PCB board 441, a tactile switch 442, and a test terminal 443.
[0096] The smart key PCB board 441 may be fitted into a PCB fixing base 432 formed to correspond to the shape of the smart key PCB board 441. The smart key PCB board 441 may have a tactile switch 442 on one side and a test terminal 443 on the other side for electrical connection.
[0097] The tactile switch 442 may be provided on one side of the smart key PCB 441, and as is well known, may perform an ON / OFF operation by pushing and returning in response to a user's operation. The tactile switch 442 may transmit a control command for performing an operation (door lock, unlock, and trunk unlock) assigned to the switch in response to the ON / OFF operation to a main controller (Electronic Control Unit (ECU), not shown) in the vehicle via a control unit on the smart PCB 440. This allows the vehicle's doors to be locked, unlocked, and the trunk to be unlocked.
[0098] The test terminals 443 may be provided on the other side of the smart key PCB board 441, and when the smart key PCB 440 is coupled to the PCB fixing base 432, the test terminals 443 may be crimped and fixed to the connection pins 450, thereby electrically connecting with the connection pins 450. The test terminals 443 may be provided to determine whether the smart key PCB 440 is defective during the manufacturing process, and may be provided corresponding to the tactile switches 442 having the respective functions (LOCK, UNLOCK, TRUNK, ALARM, etc.) of the vehicle smart key.
[0099] The test terminal 443 is located between the tactile switch 442 and a control unit (not shown) and may be located on a path that provides a corresponding electrical signal to the control unit when the tactile switch 442 is turned on. Therefore, by transmitting an electrical signal corresponding to the tactile switch 442 being turned on to the test terminal 443 and then checking the operation of the control unit, it is possible to determine whether the smart key PCB is normal or defective.
[0100] After the control PCB 170 receives a control signal for each function of the tactile switch 442 from the terminal 30, the test terminal 443 analyzes the control signal and receives an electrical signal from the control PCB 170 corresponding to the turning on of the tactile switch 442. When the test terminal 443 receives an electrical signal from the control PCB 170 corresponding to the turning on of the tactile switch 442, the control unit on the smart key PCB 440 recognizes that the tactile switch 442 is turned on, and the control unit on the smart key PCB 440 can send a control command corresponding to the tactile switch 442 to the main controller in the vehicle. As a result, the function corresponding to the tactile switch 442 can be performed.
[0101] The connection pin 450 may be inserted through the through-hole 433 and the protruding support portion 434, and one end of the inserted connection pin 450 may be connected to the test terminal 443 of the smart key PCB 440, while the other end may be connected to the connection portion 172 of the control PCB 170. The connection pin 450 may be made of a conductive material with high electrical conductivity to electrically connect the control PCB 170 and the smart key PCB 440, and the shape of the connection pin 450 is not limited as long as it can electrically connect the control PCB 170 and the smart key PCB 440. The connection pin 450 may be connected to the control PCB 170 and the smart key PCB 440 by soldering, or may be connected by soldering to one of the control PCB 170 and the smart key PCB 440 and directly connecting the other. In other words, the method for connecting the control PCB 170 and the smart key PCB 440 is not limited.
[0102] However, when soldering the connection pins 450 to connect the control PCB 170 and the smart key PCB 440, the skilled technique of an expert is required, which increases the work time and poses the risk of damaging the PCB even when the soldering is performed by an expert.
[0103] Next, a connection pin 450 according to a preferred embodiment for solving such problems will be specifically described.
[0104] Referring to FIGS. 9a to 9c, the connection pin 450 may include a body 451, a head 452, a mounting portion 453, a protrusion 454, and a hook 455.
[0105] The body 451 may be inserted through the through-hole 433 and the protruding support portion 434 and may be supported by the protruding support portion 434. An insertion groove 451a having a predetermined depth may be formed on one side of the body 451, and an elastic member 451b may be embedded in the insertion groove 451a.
[0106] One side of the head 452 can be inserted into the insertion groove 451a, and the inserted head 452 can be firmly connected to the test terminal 443 of the smart key PCB 440 by the elastic member 451b.
[0107] When the smart key PCB 440 is fitted to the PCB fixing base 432 and the head 452 is pressed and pushed into the insertion groove 451a, the elastic member 451b tends to return to its original position due to its elasticity, so that the elastic member 451b can be firmly connected to the test terminal 443 of the smart key PCB 440.
[0108] Here, the elastic member 451b can be made of any material, but it is preferable to use a conductive material such as a spring to prevent a decrease in electrical conductivity between the control PCB 170 and the smart key PCB 440.
[0109] The head 452 may be formed on one side of the body 451, and one end thereof may be inserted into an insertion groove 451a provided on one side of the body 451. The head 452 may be pressed by the smart key PCB 440 fitted to the PCB fixing base 432 and pushed into the insertion groove 451a, and when the head 452 is pushed into the insertion groove 451a, it may be firmly connected to the test terminal 443 due to the elasticity of an elastic member 451b provided inside the insertion groove 451a.
[0110] The mounting portion 453 may be provided on the other side of the body 451 and may have a diameter larger than that of the body 451. The mounting portion 453 serves to mount the body 451 in the through-hole 433 when the body 451 is inserted into the through-hole 433, and may also serve as a stopper to allow the body 451 to be inserted only to a predetermined depth.
[0111] The protrusion 454 may be protruded from one side of the mounting part 453, and may be connected to the connection line EL or directly connected to the control PCB 170. The protrusion 454 may have a fixing groove 454a formed in the axial direction on one side, and the connection line EL may be inserted and fixed in the fixing groove 454a.
[0112] The fixing groove 454a can be soldered with the connecting wire EL inserted therein, but the connecting wire EL can also be fixed by squashing the protruding portion 454 with the connecting wire EL inserted therein. This allows the connecting wire EL to be fixed and connected without the skilled technique of an expert.
[0113] One side of the connecting line EL can be inserted into the fixing groove 454a, and the other side can be connected to the control PCB 170. The other side of the connecting line EL can be soldered to the control PCB 170, but is formed in a mating shape and can be mated with a connecting portion 172 formed on one surface of the control PCB 170 in a shape corresponding to the other side of the connecting line EL.
[0114] This allows the user to easily assemble the entire vehicle service device 10 simply by fitting together the components without any soldering work.
[0115] The hooks 455 may be formed on the side of the body 451, and may be formed a predetermined distance away from the mounting portion 453 in a direction in which the body 451 is inserted into the through-hole 433 and the protruding support portion 434. When the body 451 is fitted into the through-hole 433 and the protruding support portion 434, the hooks 455 are fixed to the inner surfaces of the through-hole 433 and the protruding support portion 434, thereby preventing the body 451 from being separated in the opposite direction.
[0116] The hooks 455 may be formed on the side of the body 451 so as to surround the entire outer surface of the body 451, and at least one hook may be formed at predetermined intervals. The shape of the hooks 455 may be formed to have a triangular cross section as shown in the drawing, but is not limited thereto as long as the hooks 455 have a shape that can be inserted into the through-holes 433 and the protruding support portions 434 and prevent separation in the opposite direction.
[0117] FIG. 10 is a block diagram of a control PCB 170 according to another embodiment of the present invention.
[0118] Referring to FIG. 10, in addition to the control PCB board 171, connection unit 172, communication unit 173, PCB control unit 174, and power supply unit 175 described above, the control PCB 170 of the present invention may include a battery remaining capacity measurement module 176 that can check the remaining capacity of the vehicle battery depending on the charge level of the battery 180, a charging module 179 that controls the charging of the battery 180 and prevents overcharging, a temperature sensor 177 that detects at least the temperature of the battery 180, and a heat dissipation fan 178 that is driven depending on the temperature detection result of the temperature sensor 177.
[0119] The configuration and operation of the control PCB 170 configured as described above and applied to the present invention will now be described in more detail.
[0120] First, as mentioned above, the battery 180 is charged using power provided by the vehicle, and is charged by receiving power from the vehicle's battery (not shown) for continuous use of the vehicle service device 10.
[0121] For this reason, the charging port may be provided on one side of the case body 110 as described above.
[0122] Using power supplied from the vehicle battery to charge the battery 180 in this manner may cause problems with the discharge, lifespan, and performance of the vehicle battery.
[0123] Furthermore, since the device has a built-in battery and it is impossible to check the remaining battery power, the device must be kept constantly charged, which may result in the aforementioned discharge of the vehicle battery.
[0124] The above-mentioned problems may cause a situation in which the vehicle cannot be used due to discharge of the battery 180 of the vehicle service device 10, and may also cause the battery of the vehicle to be discharged.
[0125] In the present invention, a battery fuel gauge module 176 is used to detect the condition of the vehicle's battery.
[0126] The battery remaining capacity measurement module 176 does not directly detect the vehicle battery status, but detects the charging speed and charge amount of the battery 180 built into the vehicle service device 10, and uses this to estimate the vehicle battery status.
[0127] The estimation at this time is performed in accordance with the settings given by the PCB control unit 174.
[0128] When charging the battery 180 using the power of the vehicle battery via a power supply device such as a cigarette lighter jack of the vehicle, the charge amount within a reference time is detected via the battery remaining charge measurement module 176, and the detection result is confirmed by the PCB control unit 174, so that the state of the vehicle battery can be predicted or estimated.
[0129] If the normal range is set to 20-30% charging of the battery 180 within a reference time, when the actual charging of the battery 180 is between 10% and 20%, the PCB control unit 174 can determine that the condition of the vehicle battery is slightly bad, when the charging is between 5% and 10%, the PCB control unit 174 can determine that the condition of the vehicle battery is bad, and when the charging is between 1% and 5%, the PCB control unit 174 can determine that the condition of the vehicle battery is very bad.
[0130] When the PCB control unit 174 determines that the condition of the vehicle battery is "slightly bad," "bad," or "very bad," it transmits the vehicle battery condition information to the driver's terminal 30 via the communication unit 173, and the vehicle battery condition can be displayed on the driver's terminal 30.
[0131] Furthermore, the PCB control unit 174 can display the state of the vehicle battery through a display means such as an LED that is provided so as to be distinguishable.
[0132] As another example, the battery 180 can be charged using the charging module 179 depending on the charge level of the battery 180 confirmed by the battery remaining capacity measuring module 176 .
[0133] That is, by charging the battery 180 using the charging module 179, the vehicle battery is not constantly used and the battery 180 can be prevented from being overcharged.
[0134] When the remaining charge of the battery 180 detected by the battery remaining charge measuring module 176 reaches a lower reference value, the charging module 179 charges the battery 180 using power supplied from the vehicle battery.
[0135] When the battery 180 is charged and reaches an upper reference value, the charging module 179 can stop charging to prevent the battery 180 from being overcharged.
[0136] At this time, the charging module 179 can be controlled by the PCB control unit 174.
[0137] The PCB control unit 174 can transmit information on the state of the battery 180 and whether it is being charged via the communication unit 173 to the terminal 30 .
[0138] In particular, the PCB control unit 174 can estimate the time remaining until the vehicle battery is completely discharged based on the above-mentioned vehicle battery state detection result and transmit the estimated time to the terminal 30 via the communication unit 173.
[0139] For example, if the condition of the vehicle battery is slightly bad, the time remaining until discharge is estimated as X hours, if it is bad, the time remaining until discharge is estimated as Y hours (less than X), and if it is very bad, the time remaining until discharge is Z hours (less than Y). The estimated results are provided to the terminal 3 so that the driver (user) can check the time remaining until the vehicle battery is completely discharged and take necessary measures.
[0140] The necessary measures at this time may be to charge the battery by starting the vehicle, or to replace the battery.
[0141] The fully discharged state indicates a battery condition in which the vehicle cannot be started using the vehicle battery.
[0142] In this way, the battery remaining capacity measuring module 176 and the charging module 179 can be used to check the state of the vehicle battery and take measures to prevent performance degradation of the vehicle battery, and by controlling the charging of the battery 180, it is possible to prevent the battery 180 from being damaged or causing a fire due to overcharging.
[0143] The control PCB 170 includes a temperature sensor 177, which can directly detect the temperature of the battery 180.
[0144] When a vehicle is parked outdoors in the summer, the temperature inside the vehicle can rise rapidly, and high temperatures can increase the risk of a fire in the Battery 180.
[0145] To prevent this, the temperature of the battery 180 is detected using a temperature sensor 177, and the detected temperature is confirmed by the PCB control unit 174. If the temperature is above a reference temperature, the heat dissipation fan 178 is operated to lower the temperature of the battery 180.
[0146] In addition, if the temperature detected by the temperature sensor 177 is equal to or higher than the reference temperature, the PCB control unit 174 transmits the currently detected temperature information to the terminal 30 via the communication unit 173, so that the driver can check the current temperature and take measures to lower the interior temperature of the vehicle by moving and parking the vehicle or by opening the door or window.
[0147] In this way, the present invention can perform the functions of maintaining the performance and safety of the vehicle's battery as well as its own battery 180.
[0148] A vehicle service system to which the present invention is applied will be described below with reference to Figures 11 to 15. In the following, the description of the above-mentioned matters will be omitted or simplified.
[0149] Referring to FIG. 11, a vehicle service system to which the present invention is applied may include a vehicle service device 1000, a local area network 2000, a first terminal 3000, a first service device 4000, a second service device 5000, a second terminal 6000, and a mobile communication network 7000. The first terminal 3000 may perform the same function as the terminal 30 of FIG. 1. The first terminal 3000 may be a terminal of a vehicle owner equipped with a vehicle control device. The second terminal 6000 may be a terminal owned by an entity that provides vehicle service requested by the owner of the first terminal 3000. The first terminal 3000 and the first service device 4000, and the second service device 5000 and the second terminal 6000 may communicate via the mobile communication network 7000. The first service device 4000 and the second service device 5000 may communicate via an Internet network (not shown).
[0150] Referring to FIG. 12, the first terminal 3000 may include a virtual key 3100, a service user interface (UI) 3200, and a communication unit 3300.
[0151] The virtual key 3100 can provide an interface for controlling the vehicle service device 1000. The virtual key 3100 can be an application running on the processor of the first terminal 3000. The virtual key 3100 can receive user commands related to vehicle locking and unlocking (hereinafter referred to as "user's vehicle control commands") via the screen of the first terminal 3000. For example, the virtual key 3100 can provide vehicle door lock / unlock and trunk unlock buttons.
[0152] The virtual key 3100 can be linked with the vehicle service apparatus 1000 via a local area network 2000. Here, the local area network 2000 may be the same as the communication network 20 in FIG. 1. When the virtual key 3100 connects to the vehicle service apparatus 1000 via the local area network 2000, a security connection method may be used. In this case, the virtual key 3100 can be authenticated by the vehicle service apparatus 1000 by providing at least one of a security key, a security code, and an identifier (ID) of the virtual key 3100 to the vehicle service apparatus 1000. When the authentication procedure is successfully completed, the vehicle service apparatus 1000 and the virtual key 3100 can be connected (e.g., paired using the Bluetooth standard).
[0153] When the virtual key 3100 receives a user's vehicle control command, it can transmit the user's vehicle control command to the vehicle service device 1000 via the communication unit 3300. At this time, the vehicle service device 1000 that receives the user's vehicle control command can perform a vehicle control operation (e.g., lock / unlock vehicle doors, unlock trunk, etc.) according to the user's vehicle control command. The vehicle service device 1000 may be the same as the vehicle service device 10 of FIG. 1. The PCB control unit 174 (see FIG. 5) in the vehicle service device 1000 can receive the user's vehicle control command from the first terminal 3000 via the communication unit 173 (see FIG. 5). The PCB control unit 174 can read the received user's vehicle control command. The PCB control unit 174 can then supply power to a test terminal 443 (see FIG. 5) corresponding to the read user's vehicle control command. As a result, the smart key PCB 440 (see FIG. 5) can recognize that the tactile switch 442 (see FIG. 5) corresponding to the user's vehicle control command has been operated.
[0154] The smart key PCB 440 (see FIG. 5) can then send a control command corresponding to the tactile switch 442 (see FIG. 5) to a main controller (not shown) inside the vehicle. At this time, the main controller inside the vehicle can perform vehicle control operations corresponding to the control command via an electrical signal.
[0155] The service user interface (UI) 3200 may provide a user with a UI for vehicle services. The service UI 3200 may be an application executed on the processor of the first terminal 3000. The service UI 3200 may provide a user interface for applying for and using vehicle services. A service application may be executed on the first terminal 3000. In this case, the service UI 3200 may be provided via the screen of the first terminal 3000. A user may request a service through the service UI 3200. In this case, information for searching for a service provider may be provided to the first service device 4000. For example, when a user requests vehicle maintenance, information for searching for a service provider may include the vehicle model, model year, oil type, etc. When a user requests a designated driver, information for searching for a service provider may include a departure location, an arrival location, a cost, etc. In addition, when a service is requested, the service UI 3200 may provide information identifying the vehicle service desired by the user to the first service device 4000.
[0156] The service UI 3200 may receive service provider information from the first service device 4000. The service provider information may include information on at least one service provider. In this case, the service UI 3200 may provide a UI that allows the user to select a service provider. When the user selects a service provider through the service UI 3200, the service UI 3200 may provide information on the selected service provider to the first service device 4000.
[0157] The communication unit 3300 can communicate with the vehicle service device 1000 via the local area network 2000. At this time, a security connection method can be used. The communication unit 3300 can connect to the vehicle control device 1000 using at least one of a security key, a security code, and a virtual key identifier (ID). The communication unit 3300 can communicate with the first service device 4000 via the mobile communication network 7000.
[0158] The first service device 4000 may include a first service providing unit 4100, a virtual key management unit 4200, and a communication unit 4300.
[0159] The first service providing unit 4100 may receive a service request from the first terminal 3000. In this case, the first service providing unit 4100 may identify a vehicle service desired by the user. The first service providing unit 4100 may request service provider information from the second service device 5000 related to the identified vehicle service. Here, the second service device 5000 may be a server operated by a provider or company of a vehicle service desired by the user. Alternatively, the second service device 5000 may be a server operated by an operator of a vehicle service information providing platform in which the provider or company of the vehicle service is a member. When the service provider information is requested, the first service providing unit 4100 may provide information for searching for a service provider received from the first terminal 3000 to the second service device 5000.
[0160] The first service providing unit 4100 may request service provision information from the second service device 5000. When requesting the service provider information, the first service providing unit 4100 may provide service provider search criteria to the second service device 5000.
[0161] The service provider search criteria may be the same as or include a part of the information for searching for a service provider.
[0162] The first service providing unit 4100 can receive the service provider information provided by the second service device 5000.
[0163] Furthermore, the first service providing unit 4100 can provide the service provider information received from the second service device 5000 to the first terminal 3000 .
[0164] The virtual key management unit 4200 can provide a virtual key to a terminal 6000 (hereinafter referred to as a "second terminal") owned by a service provider selected by the user. In this case, the virtual key management unit 4200 can provide security information (e.g., a security key, a security code, and a virtual key identifier, where the virtual key identifier is a virtual key identifier of the first terminal) required when the second terminal 6000 connects to the vehicle service device 1000 to the second terminal 6000. The virtual key management unit 4200 can provide an application for generating a virtual key in the terminal to the terminal. The virtual key management unit 4200 can also manage security information (e.g., an identifier for each virtual key application, a security code, and a security key) used for the virtual key to connect to the vehicle service device.
[0165] The virtual key management unit 4200 can retrieve the virtual key when a service end report is received from the second terminal 6000.
[0166] At this time, the virtual key management unit 4200 can transmit a virtual key deletion command to the second terminal 6000. The virtual key installed in the second terminal 6000 that has received the virtual key deletion command can delete the security information required to connect to the vehicle service device 1000 received from the first service device 4000. Alternatively, in response to the second terminal 6000 automatically or manually recognizing that the vehicle service provider has ended the service, the virtual key on the second terminal 6000 can automatically delete the security information required to connect to the vehicle service device 1000. Here, the second terminal 6000 automatically recognizes that the vehicle service has ended when it recognizes via GPS that the vehicle has arrived at the driving service destination, when it receives a notification from an external device (e.g., the first service device) that the service has been completed, or when it submits a service completion report.
[0167] The communication unit 4300 can communicate with the first terminal 3000 via a mobile communication network, and can communicate with the second service device 5000 via the Internet network.
[0168] The second service device 5000 may be a server operated by a provider or company of a vehicle service desired by the user. Alternatively, the second service device 5000 may be a server operated by an operator of a vehicle service providing platform in which the provider or company of the vehicle service is a member. The first service device 4000 and the second service device 5000 may be operated by the same entity. The second service device 5000 may be a Kakao driving service server or an 8282 driving service server. The second service device 5000 may be one of a plurality of servers operated by vehicle services or service providers. That is, there may be at least one second service device 5000, and the second service device 5000 may be a server operated by a provider that has a business agreement with the operator of the first service device 4000.
[0169] The second service device 5000 may include a second service providing unit 5100 and a communication unit 5200 .
[0170] The second service providing unit 5100 may receive a service provider information request from the first service device 4000. The second service providing unit 5100 may search for a service provider according to service provider search criteria included in the service provider information request. To this end, the second service device 5000 may operate a service provider database (not shown).
[0171] Here, the "service provider" may be an individual or a company. When searching for a service provider, the service provider search criteria presented by the user and received from the first service device 4000 can be used. Alternatively, when searching for a service provider, search conditions other than the service provider search criteria (for example, the geographical distance between the user and the service provider) can be used.
[0172] The second service providing unit 5100 can transmit the searched service provider information to the first service device 4000.
[0173] The communication unit 5200 can communicate with the first service device 4000 via the Internet network.
[0174] The second terminal 6000 may be a terminal owned by a service provider. The second terminal 6000 may be a terminal that supports mobile communication and application installation. For example, the second terminal 6000 may be a smartphone or a PDA.
[0175] The second terminal 6000 may include a virtual key 6100, a service UI 6200, and a communication unit 6300. The virtual key 6100 and the service UI 6200, which will be described later, are already installed in the second terminal, and may be set in the step of providing vehicle services only for matters requested in the step of providing vehicle services using the virtual key. For example, the virtual key 6100 and the service UI 6200, which will be described later, are already installed in the second terminal, and may be set in the step of providing vehicle services only for information for securely connecting to a vehicle service device installed in a vehicle that has requested vehicle services.
[0176] The virtual key 6100 can provide an interface for controlling the vehicle service device 1000. The virtual key 6100 can be an application running on the processor of the second terminal 6000. The virtual key 6100 can receive user commands related to vehicle locking and unlocking (hereinafter referred to as "user's vehicle control commands") via the screen of the second terminal 6000. For example, the virtual key 6100 can provide vehicle door lock / unlock and trunk unlock buttons.
[0177] The virtual key 6100 can be linked with the vehicle service apparatus 1000 via a local area network 2000. Here, the local area network 2000 may be the same as the communication network 20 in FIG. 1 . When the virtual key 6100 connects to the vehicle service apparatus 1000 via the local area network 2000, a security connection method may be used. At this time, the virtual key 6100 can be authenticated by the vehicle service apparatus 1000 by providing at least one of a security key, a security code, and an identifier (ID) of the virtual key 3100 to the vehicle service apparatus 1000. When the authentication procedure is successfully completed, the vehicle service apparatus 1000 and the virtual key can be connected (e.g., paired according to the Bluetooth standard). Security information, such as the security key, the security code, and the identifier (ID) of the virtual key 3100, used when the second terminal 6000 connects to the vehicle service apparatus 1000 may be received from the first service apparatus 4000.
[0178] When the virtual key 6100 receives a user's vehicle control command, it can transmit the user's vehicle control command to the vehicle service device 1000 via the communication unit 6300. At this time, the vehicle service device 1000 that receives the user's vehicle control command can perform a vehicle control operation (e.g., lock / unlock vehicle doors, unlock the trunk, etc.) according to the user's vehicle control command. The vehicle service device 1000 may be the same as the vehicle service device 10 of FIG. 1. The PCB control unit 174 (see FIG. 5) in the vehicle service device 1000 can receive the user's vehicle control command from the second terminal 6000 via the communication unit 173 (see FIG. 5). The PCB control unit 174 can read the received user's vehicle control command. The PCB control unit 174 can also supply power to a test terminal 443 (see FIG. 5) corresponding to the read user's vehicle control command. This allows the smart key PCB 440 (see FIG. 5) to recognize that the tactile switch 442 (see FIG. 5) corresponding to the user's vehicle control command has been operated.
[0179] The smart key PCB 440 (see FIG. 5) can then send a control command corresponding to the tactile switch 442 (see FIG. 5) to a main controller (not shown) inside the vehicle. The main controller inside the vehicle can then perform a vehicle control operation corresponding to the control command via an electrical signal. When the virtual key 6100 receives a virtual key deletion command from the first service device 4000, it can delete security information (such as a security code, a security key, and a virtual key application identifier of the first terminal user) received from the first service device 4000 and used to connect to the vehicle control device 1000 in the vehicle owned by the user who requested the vehicle service via a local area network. In response to the second terminal 6000 automatically or manually recognizing that the vehicle service provider has terminated the vehicle service, the virtual key 6100 can automatically delete security information required for the virtual key on the second terminal 6000 to connect to the vehicle control device 1000. Here, the second terminal 6000 automatically determines that the vehicle service has ended when it recognizes via GPS that the vehicle has arrived at the designated driving destination, when it receives notification from an external device (e.g., the first service device) that the service has been completed, or when it provides a service completion report.
[0180] The service user interface (UI) 6200 may provide a UI for vehicle services to the second terminal user. The service UI 6200 may be an application running on the processor of the second terminal 6000.
[0181] The service UI 6200 can provide an interface that enables the user of the second terminal 6000 to perform a procedure for receiving a virtual key from the first service device 4000 (in other words, a procedure for receiving security information for connecting to a vehicle service device) and a procedure for submitting a service completion report. The second terminal 6000 can report to the first service device 4000 that the vehicle service requested by the user of the first terminal 3000 has been completed. At this time, the first service providing unit 4100 can settle the payment for the vehicle service.
[0182] The communication unit 6300 can communicate with the vehicle service device 1000 via the local area network 2000. At this time, a security connection method can be used. The communication unit 6300 can connect to the vehicle control device 1000 using at least one of a security key, a security code, and a virtual key identifier (ID). The communication unit 3300 can communicate with the first service device 4000 via the mobile communication network 7000.
[0183] A vehicle service providing method in a vehicle service system to which the present invention is applied will be described below. The following description will help clarify the configuration of the above-mentioned system.
[0184] First, a vehicle service application is executed on the first terminal 3000, and a service UI 3200 for vehicle services can be provided to a user (S151).
[0185] At this time, the user of the first terminal 3000 may make a vehicle service request through the service UI 3200 (S152). At this time, the first terminal 3000 may provide information for searching for a service provider to the first service device 4000. For example, when a user requests vehicle maintenance, the information for searching for a service provider may include the vehicle model, model year, oil type, etc. When a user requests a designated driver, the information for searching for a service provider may include the departure location, arrival location, cost, etc. Then, when a service request is made, the service UI 3200 may provide information identifying the vehicle service desired by the user to the first service device 4000.
[0186] When receiving a service request from the first terminal 3000, the first service providing unit 4100 may identify a vehicle service desired by the user. Then, the first service providing unit 4100 may request service provider information from the second service device 5000 related to the identified vehicle service (S153). Here, the second service device 5000 may be a server operated by a provider or company of the vehicle service desired by the user. Alternatively, the second service device 5000 may be a server operated by an operator of a vehicle service information providing platform in which the provider or company of the vehicle service is a member. When requesting service provider information, the first service providing unit 4100 may provide information for searching for a service provider received from the first terminal 3000 to the second service device 5000.
[0187] When receiving the service provider information request from the first service device 4000, the second service providing unit 5100 may search for a service provider according to the service provider search criteria included in the service provider information request (S154). To this end, the second service device 5000 may operate a service provider database (not shown). Here, the "service provider" may be an individual or a company. When searching for a service provider, the service provider search criteria presented by the user and received from the first service device 4000 may be used. Alternatively, when searching for a service provider, search conditions other than the service provider search criteria (e.g., the geographical distance between the user and the service provider) may be used.
[0188] The second service providing unit 5100 may transmit the searched service provider information to the first service device 4000 (S155). The searched service provider information may include at least one person or company that provides the vehicle service requested by the user of the first terminal 3000. The service provider information may also include service conditions (cost, location area, etc.) of each person or company that provides the vehicle service requested by the user.
[0189] The first service providing unit 4100 can provide the service provider information received from the second service device 5000 to the first terminal 3000 (S156).
[0190] At this time, the user of the first terminal 3000 can select one service provider from the service provider information received via the service UI 3200 (S157).
[0191] The first terminal 3000 can transmit information about the selected service provider to the first service device 4000 (S158).
[0192] At this time, the virtual key management unit 4200 can provide a virtual key to one terminal 6000 (hereinafter referred to as the "second terminal") owned by the service provider selected by the user (S159). At this time, the virtual key management unit 4200 can provide the second terminal 6000 with security information (e.g., a security key, a security code, a virtual key identifier, etc., where the virtual key identifier is the virtual key identifier of the first terminal) required when the second terminal 6000 connects to the vehicle service device 1000.
[0193] Then, the user of the second terminal 6000 can connect to the vehicle service device 1000 using the security information received from the virtual key management unit 4200, control the vehicle, and provide the vehicle service requested by the user (S160).
[0194] Furthermore, when the vehicle service requested by the user is completed, the service UI 6200 can report the completion of the vehicle service to the first service providing unit 4100. At this time, the service UI 6200 can provide a service completion report to the first service providing unit 4100 in accordance with a preset format (S161).
[0195] The virtual key management unit 4200 can collect the virtual key when receiving a service completion report from the second terminal 6000 (S162). At this time, the virtual key management unit 4200 can transmit a virtual key deletion command to the second terminal 6000. The virtual key installed in the second terminal 6000 that has received the virtual key deletion command can delete security information required to connect to the vehicle service device 1000 received from the first service device 4000. Alternatively, in response to the second terminal 6000 automatically or manually recognizing that the vehicle service provider has ended the service, the virtual key on the second terminal 6000 can automatically delete security information required to connect to the vehicle service device 1000. Here, the second terminal 6000 can automatically determine that the vehicle service has ended when it recognizes via GPS that the vehicle has arrived at the driving service destination, when it receives a notification that the service has been completed from an external device (e.g., the first service device), or when it submits a service completion report.
[0196] Although specific embodiments have been described in the detailed description of the present invention, it should be understood that various modifications can be made without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined by the following claims and their equivalents. [Explanation of symbols]
[0197] 1. Vehicle control system 10, 1000 Vehicle control device 20, 2000 communication network 30 devices 100 cases 171 Control PCB board 172 Connection 173 Communications Department 174 PCB Control Unit 175 Power supply section 176 Battery Fuel Gauge Module 177 Temperature Sensor 178 Heat dissipation fan 179 Charging Module 180 Battery 200 lids 300 lockers 400 Support stand 3000 Terminal 1 4000 First Service Device 5000 Second service device 6000 Terminal 2 7000 communication network
Claims
1. Including a case, a lid, a rocker and a support base, The case includes a case body, a locking groove, a cover coupling part, a support mounting part, a PCB fixing part, a battery mounting part, a control PCB and a battery; The case body accommodates a control PCB and a battery in an accommodation space formed therein. The case body has an open side on which a support base is placed, and a rocker groove in which a rocker is fitted is formed on the other side. The control PCB includes: a charging module that charges a vehicle battery using power from the battery; a battery remaining capacity measurement module that detects the state of charge of the battery; a PCB control unit that controls the charging module using the detection result of the battery remaining capacity measurement module and estimates the state of the vehicle battery; and a communication unit that transmits the estimation result of the PCB control unit to a driver's terminal, The PCB control unit A vehicle service device, characterized in that the state of a vehicle battery is estimated based on the amount of charge of the battery charged during a reference time.
2. The control PCB includes: further comprising a temperature sensor for detecting the temperature of the battery; 2. The vehicle service device according to claim 1, wherein when the temperature detected by the temperature sensor is equal to or higher than a reference temperature, the device operates a heat dissipation fan and transmits temperature information of the battery to the terminal via the communication unit.
3. The PCB control unit Based on the percentage of battery charging that is performed normally within a set time, 2. The vehicle service device according to claim 1, wherein the state of the vehicle battery is estimated as "normal," "slightly poor," "poor," or "very poor" by dividing the charging rate of the battery.
4. The control PCB includes:
2. The vehicle service device according to claim 1, further comprising a display unit for displaying a result of the vehicle battery state estimation by the PCB control unit.
5. The control PCB includes:
2. The vehicle service device according to claim 1, wherein the battery is charged using the charging module in accordance with the charge level of the battery confirmed by the battery remaining capacity measuring module.
6. When the remaining battery charge detected by the battery remaining charge measuring module reaches a lower reference value, the charging module charges the battery using power supplied from the vehicle battery; 6. The vehicle service device according to claim 5, wherein when the state of charge of the battery reaches an upper reference value, the charging module stops charging to prevent the battery from being overcharged.
Citation Information
Patent Citations
Control device for vehicle, and control system for vehicle
JP2011230601A
Remote operation system of in-vehicle equipment
JP2014125098A
Battery test reporting system and method
JP2018509707A
Portable device and electronic key system for vehicles
JP2019131967A
Battery status determination system and battery status determination method
JP2021086654A