Server, charging server, and charging system including the charging server
The server and charging system unify PnC charging methods by integrating charging information and managing user authentication and payment, enabling PnC charging for vehicles that do not support the technology.
Patent Information
- Application Number
- JP2025525369
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2022-11-09
- Filing Date
- 2023-10-12
- Publication Date
- 2025-10-30
AI Technical Summary
Existing PnC charging methods are limited to vehicles that support the technology, and vehicles that do not support PnC cannot utilize this charging method.
A server and charging system that integrates communication circuits and controllers to manage and control the connection between chargers and target devices, enabling the unification of PnC charging by collecting and integrating charging information from both supported and unsupported vehicles, and managing user authentication and payment.
Enables PnC charging for vehicles that do not support the method by unifying charging protocols across different systems, allowing for seamless authentication and billing processes.
Smart Images

Figure 2025535994000001_ABST
Abstract
Description
[Technical Field]
[0001] The present invention claims the benefit of priority based on Korean Patent Application No. 10-2022-0149083, filed on November 9, 2022, and all contents disclosed in the documents of this Korean patent application are incorporated herein by reference.
[0002] SUMMARY OF THE INVENTION The embodiments disclosed herein relate to a server and a charging system including the server. [Background technology]
[0003] As environmental issues become more important, the use of environmentally friendly electric vehicles is expanding. Accordingly, infrastructure for the use of electric vehicles (e.g., chargers or charging stations) is being increasingly built. For example, charging systems are becoming more widespread, in which users of electric vehicles authenticate themselves using an external identification means (EIM) system based on an RFID card or QR code (registered trademark), or a plug and charge (PnC) system based on a certificate in the electric vehicle. Once authentication is complete, the electric vehicle is charged with power provided by a charger.
[0004] Meanwhile, the PnC method refers to a charging technology in which authentication and payment are performed automatically when charging an electric vehicle. The advantage of PnC charging is that users do not have to go through various processes to identify themselves, but the disadvantage is that it can only be used in vehicles that support PnC, and even in vehicles that support PnC, a charger that is linked to the vehicle must be used. Summary of the Invention [Problem to be solved by the invention]
[0005] An object of the embodiments disclosed in this document is to provide a server, a charging server, and a charging system that are capable of unifying the PnC charging method.
[0006] An object of the embodiments disclosed in this document is to provide a server, a charging server, and a charging system that enable PnC charging even for vehicles that do not support PnC.
[0007] The technical problems of the embodiments described in this document are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person of ordinary skill in the art to which the present invention belongs from the following description. [Means for solving the problem]
[0008] In one embodiment disclosed in this document, the server includes a communication circuit that receives first charging information from an information collection device connected to a target device and receives second charging information transmitted from a charger corresponding to the target device from a charging server, and a controller that manages the connection between the charger and the target device and costs associated with using the charger based on the first charging information and the second charging information.
[0009] According to one embodiment, the controller can recognize an information collection device connected to the target device and confirm user authentication information and payment information of the target device based on identification information of the recognized information collection device.
[0010] According to one embodiment, the communication circuitry can communicate charging authorization information and billing completion information to the charging server.
[0011] According to one embodiment, the communication circuitry may communicate the charging approval information and the billing completion information to the information collection device via an LTE communication network.
[0012] According to one embodiment, the first charging information may include connection information between the charger and the target device recognized by the information collection device, and the second charging information may include connection information between the charger and the target device recognized by the charger.
[0013] According to one embodiment, the first charging information may include charging status information of the target device.
[0014] According to one embodiment, the first charging information may include a power usage capacity of the charger recognized by the information collection device, and the second charging information may include a power usage capacity of the charger recognized by the charger.
[0015] In one embodiment, the controller may use the first charging information and the second charging information to determine a cost to be charged to a user of the target device.
[0016] A charging server according to one embodiment disclosed in this document includes a communication circuit that transmits second charging information received from a charger to a management server and receives control information regarding the operation of the charger from the management server, and a controller that controls the operation of the charger based on the control information.
[0017] According to one embodiment, the controller can control the charger to charge the target device based on the control information.
[0018] According to one embodiment, when the communication circuit receives charging completion information from the management server, the communication circuit can transmit the charging completion information to the charger.
[0019] A charging system according to one embodiment disclosed in this document includes a management server that receives first charging information from an information collection device connected to a target device, and a charging server that receives second charging information from a charger corresponding to the target device and transmits the second charging information to the management server, and the management server integrates the first charging information and the second charging information to manage costs associated with the connection of the target device and the use of the charger.
[0020] According to one embodiment, the management server transmits control information regarding the operation of the charger to the charging server, and the charging server can control the operation of the charger based on the control information.
[0021] According to one embodiment, the management server can recognize the information collection device connected to the target device and confirm the user authentication information and payment information of the target device based on the identification information of the recognized information collection device.
[0022] Specific details of other embodiments are included in the detailed description and drawings. [Effects of the Invention]
[0023] The server, charging server, and charging system according to the embodiments disclosed in this document enable the unification of the PnC charging method.
[0024] According to the server, charging server, and charging system according to the embodiments disclosed herein, even vehicles that do not support PnC can utilize PnC charging. [Brief explanation of the drawings]
[0025] [Figure 1] FIG. 1 is a block diagram illustrating an embodiment of a charging system disclosed herein. [Figure 2] FIG. 1 is a block diagram illustrating an administration server according to one embodiment disclosed herein. [Figure 3] FIG. 1 is a block diagram illustrating an embodiment of a charging server disclosed herein. [Figure 4] 1 is a flowchart illustrating a charging method according to one embodiment disclosed herein. [Figure 5] 5 is a flowchart specifically illustrating an operation for authenticating a user of the target device of FIG. 4. [Figure 6] 5 is a flowchart specifically showing the operation of charging a user of the target device of FIG. 4. DETAILED DESCRIPTION OF THE INVENTION
[0026] Hereinafter, the embodiments disclosed in this document will be described in detail with reference to the exemplary drawings. When assigning reference numerals to components in each drawing, it should be noted that the same reference numerals are used for the same components even if they appear in different drawings. Furthermore, when describing the embodiments disclosed in this document, if a detailed description of related known structures or functions is deemed to hinder understanding of the embodiments disclosed in this document, such detailed description will be omitted.
[0027] When describing components of the embodiments disclosed herein, terms such as "first," "second," etc. may be used. Such terms are merely used to distinguish the component from other components and do not limit the nature, order, or sequence of the components. Furthermore, unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which the embodiments disclosed herein belong. Terms defined in commonly used dictionaries should be interpreted to have a meaning consistent with the meaning given in the context of the relevant art, and should not be interpreted in an idealized or overly formal sense unless expressly defined in this application.
[0028] FIG. 1 is a block diagram illustrating an embodiment of a charging system disclosed herein.
[0029] Referring to FIG. 1 , a charging system 10 according to one embodiment of the present invention may include a target device 100 , a charger 200 , an information collection device 300 , a management server 400 , and a charging server 500 .
[0030] The target device 100 may be a device that is driven by being charged by the charger 200. That is, the target device 100 may be charged by power provided from the charger 200. The target device 100 may be directly or indirectly connected to the charger 200 for charging, and may be separated from the charger 200 and driven independently. According to an embodiment, the target device 100 may be an electric vehicle (EV).
[0031] The charger 200 can charge the target device 100. The charger 200 can provide power to the target device 100 to charge the target device 100. According to an embodiment, the charger 200 can supply power to the target device 100 or stop supplying power to the target device 100 in accordance with control of the charging server 500. That is, the charger 200 can be driven based on control information received from the charging server 500.
[0032] The charger 200 may generate second connection information. The charger 200 may recognize the target device 100 connected to the charger 200 through at least one power cable included in the power line of the charger 200. According to an embodiment, the charger 200 may acquire information about the target device 100 through the power line. The charger 200 may generate second connection information based on the acquired information about the target device 100. The second connection information may include whether the charger 200 and the target device 100 are connected, the connection time, and SoC (State of Charge) information. The SoC indicates the remaining capacity of the battery, and is a value obtained by dividing the currently usable battery capacity by the total capacity and expressed as a percentage.
[0033] The charger 200 may generate second charging information. According to an embodiment, the charger 200 may store the amount of power used to charge the target device 100. The charger 200 may generate the second charging information based on the amount of power used. The second charging information may include the amount of power used by the charger 200. According to an embodiment, the second charging information may include charging status information of the target device 100.
[0034] The charger 200 can transmit the second connection information and the second charging information to the charging server 500.
[0035] The information collecting device 300 may generate first connection information. The information collecting device 300 may collect information related to the target device 100. The information collecting device 300 may collect information generated from various sensors and controllers in the target device 100. That is, the first connection information may include information related to the target device 100. According to an embodiment, the first connection information may include whether the target device 100 and the charger 200 are connected, the connection time, SoC information, and the like, collected by the information collecting device 300. According to an embodiment, the information collecting device 300 may include an OBD device.
[0036] The information collecting device 300 may generate first charging information. According to an embodiment, the information collecting device 300 may store the amount of power provided from the charger 200 to the target device 100. According to another embodiment, the information collecting device 300 may store the amount of power used by the charger 200 to charge the target device 100. The information collecting device 300 may generate the first charging information based on the amount of power used. The first charging information may include the amount of power used by the charger 200 or the amount of power provided from the charger 200 to the target device 100. According to an embodiment, the first charging information may include charging status information of the target device 100.
[0037] The information collection device 300 can transmit the first connection information and the first charging information to the management server 400.
[0038] The management server 400 can integrate information related to charging of the target device 100. That is, the management server 400 can integrate the first connection information, the second connection information, the first charging information, and the second charging information.
[0039] According to an embodiment, the management server 400 may receive first connection information from the information collection device 300 and second connection information from the charging server 500. The management server 400 may match the first connection information with the second connection information and integrate the first connection information with the second connection information. The management server 400 may compare the connection status, connection time, and SoC information of the target device 100 and the charger 200 included in the first connection information with the connection status, connection time, and SoC information of the charger 200 and the target device 100 included in the second connection information.
[0040] According to the embodiment, the management server 400 can receive first charging information from the information collection device 300 and second charging information from the charging server 500. The management server 400 can match the first charging information with the second charging information and integrate the first charging information with the second charging information. The management server 400 can integrate the power usage capacity of the charger 200 included in the first charging information with the power usage capacity of the charger 200 included in the second charging information.
[0041] The management server 400 can confirm the user authentication information and payment information of the target device 100. According to the embodiment, the management server 400 can recognize the information collection device 300 connected to the target device 100 and identify the user of the target device 100 based on the identification information of the recognized information collection device 300. Furthermore, the management server 400 can confirm the user authentication information and payment information of the identified user.
[0042] The management server 400 can manage the charging of the target device 100 by the charger 200. The management server 400 can control the charging server 500. The management server 400 can transmit control information to the charging server 500 based on the first connection information and the second connection information. According to an embodiment, the control information can include charging approval information, charging start information, and billing completion information. According to an embodiment, the management server 400 may transmit the charging approval information, charging start information, and billing completion information to the information collection device 300.
[0043] The management server 400 can manage the costs associated with the use of the charger 200 by the target device 100. The management server 400 can calculate the charging costs based on the first charging information and the second charging information. The management server 400 can calculate the charging costs based on the power usage capacity of the charger 200 obtained by integrating the first charging information and the second charging information.
[0044] The management server 400 can charge the user of the target device 100 a charging fee using a preset payment method. The management server 400 can recognize the information collection device 300 to identify the user, and extract data related to the identified user from the stored user data. The management server 400 can charge the user a fee based on the extracted data.
[0045] The management server 400 can unify the PnC charging methods by controlling the information collection device 300 and the charging server 500 to manage the charging of the target device 100. That is, the protocol of the management server 400 and the charging server 500 can unify the PnC charging methods of various chargers and charging servers into one method, instead of using different methods for each individual charging server 500.
[0046] Furthermore, not only vehicles that support the PnC charging method, but also vehicles that do not support the PnC charging method can use the PnC charging method by installing the information collection device 300.
[0047] The charging server 500 can transmit and receive information to and from the management server 400 and the charger 200. The charging server 500 can receive information from the charger 200 and transmit information to the charger 200. The charging server 500 can receive second connection information and second charging information from the charger 200. The charging server 500 can transmit control information to the charger 200. The charger 200 can start charging the target device 100 based on the control information. That is, the control information can include charging approval information.
[0048] Meanwhile, the charging server 500 can transmit information to the management server 400 and receive information from the management server 400. The charging server 500 can transmit the second connection information and second charging information received from the charger 200 to the management server 400. The charging server 500 can receive control information related to the operation of the charger 200 from the management server 400.
[0049] The charging server 500 can control the operation of the charger 200. The charging server 500 can control the charger 200 to charge the target device 100. According to an embodiment, the charging server 500 transmits control information to the charger 200, and the charger 200 can start charging the target device 100 based on the control information received from the charging server 500.
[0050] FIG. 2 is a block diagram illustrating a management server according to one embodiment disclosed herein.
[0051] Referring to FIG. 2, the management server 400 may include a first communication circuit 410 and a first controller 420 .
[0052] The first communication circuit 410 can transmit and receive information related to charging of the target device 100. According to the embodiment, the first communication circuit 410 can receive first connection information and first charging information from the information collection device 300, and can receive second connection information and second charging information from the charging server 500.
[0053] According to the embodiment, the first communication circuit 410 can transmit control information to the charging server 500. The control information transmitted by the first communication circuit 410 to the charging server 500 can include charging approval information, charging start information, and billing completion information. That is, the first communication circuit 410 can transmit the charging approval information, charging start information, and billing completion information to the charging server 500.
[0054] In addition, the first communication circuit 410 can transmit the charging approval information, the charging start information, and the billing completion information to the information collection device 300. According to an embodiment, the first communication circuit 410 may transmit the charging approval information, the charging start information, and the billing completion information to the information collection device 300 via an LTE communication network.
[0055] The first communication circuit 410 can transmit the received first connection information, first charging information, second connection information, and second charging information to the first controller 420.
[0056] The first controller 420 can integrate information related to charging of the target device 100. That is, the first controller 420 can integrate the first connection information, the second connection information, the first charging information, and the second charging information. The first controller 420 can receive the first connection information, the second connection information, the first charging information, and the second charging information transmitted from the first communication circuit 410. To this end, the first controller 420 can be connected to the first communication circuit 410. The first controller 420 can match the first connection information with the second connection information and integrate the first connection information with the second connection information.
[0057] The first controller 420 can compare the connection status, connection time, and SoC information of the target device 100 and the charger 200 included in the first connection information with the connection status, connection time, and SoC information of the charger 200 and the target device 100 included in the second connection information.
[0058] The first controller 420 can match the first charging information with the second charging information and integrate the first charging information with the second charging information. The first controller 420 can integrate the power usage capacity of the charger 200 included in the first charging information with the power usage capacity of the charger 200 included in the second charging information.
[0059] The first controller 420 can check the user authentication information and payment information of the target device 100. According to the embodiment, the first controller 420 can recognize the information collection device 300 connected to the target device 100 and identify the user of the target device 100 based on the identification information of the recognized information collection device 300.
[0060] The first controller 420 can recognize the information collection device 300 that transmits information to the first communication circuit 410 via the first communication circuit 410. The first controller 420 can confirm the identification information of the recognized information collection device 300. The first controller 420 can identify the user of the target device 100 to which the information collection device 300 is connected, based on the identification information of the information collection device 300. The first controller 420 can confirm the user authentication information and payment information of the identified user.
[0061] The first controller 420 can manage costs related to the use of the charger 200 of the target device 100. The first controller 420 can calculate the charging cost based on the first charging information and the second charging information. The first controller 420 can calculate the charging cost based on the power usage amount obtained by integrating the first charging information and the second charging information.
[0062] The first controller 420 can charge the user of the target device 100 a charging fee using a preset payment method. The first controller 420 can recognize the information collection device 300 that transmits information to the first communication circuit 410, identify the user, and extract data related to the identified user from the stored user data. The first controller 420 can charge the user a fee based on the extracted data.
[0063] FIG. 3 is a block diagram illustrating a charging server according to one embodiment disclosed herein.
[0064] Referring to FIG. 3, the charging server 500 may include a second communication circuit 510 and a second controller 520.
[0065] The second communication circuit 510 can transmit and receive information to and from the first communication circuit 410 and the charger 200. The second communication circuit 510 can receive information from the charger 200 and transmit information to the charger 200. The second communication circuit 510 can receive second connection information and second charging information from the charger 200. The second communication circuit 510 can transmit control information to the charger 200. The charger 200 can start charging the target device 100 based on the control information. That is, the control information can include charging approval information.
[0066] Meanwhile, the second communication circuit 510 can transmit information to the first communication circuit 410 and receive information from the first communication circuit 410. The second communication circuit 510 can transmit the second connection information and second charging information received from the charger 200 to the first communication circuit 410. The second communication circuit 510 can receive control information related to the operation of the charger 200 from the first communication circuit 410. The control information received by the second communication circuit 510 from the first communication circuit 410 can include charging approval information, charging start information, and billing completion information.
[0067] The second communication circuit 510 can transmit billing completion information to the charger 200.
[0068] The second controller 520 can control the operation of the charger 200. The second controller 520 can control the charger 200 to charge the target device 100 based on the control information. According to the embodiment, the second controller 520 can receive the control information transmitted from the second communication circuit 510. The second controller 520 can convert the transmitted control information into control information that can be recognized by the charger 200.
[0069] The second controller 520 can control the operation of the charger 200. The second controller 520 can control the second communication circuit 510 and transmit control information to the charger 200. The charger 200 can start charging the target device 100 based on the control information received from the second controller 520. That is, the first controller 420 can control the operation of the charger 200 via the second controller 520.
[0070] FIG. 4 is a flowchart illustrating a charging method according to one embodiment disclosed herein.
[0071] Referring to FIG. 4, a charging method according to one embodiment may include an operation of authenticating a user of the target device 100 (S110), an operation of charging the target device 100 (S120), and an operation of charging the user of the target device 100 (S130).
[0072] Operations S110 to S130 will be specifically described below with reference to FIG.
[0073] In operation S110, the management server 400 can authenticate the user of the target device 100. When the target device 100 and the charger 200 are connected, the information collection device 300 can transmit information regarding the connection of the charger 200 to the management server 400. Furthermore, the charger 200 can transmit information regarding the connection of the charger 200 to the charging server 500, and the charging server 500 can transmit information received from the charger 200 to the management server 400. The management server 400 can identify the information collection device 300 that transmitted information to the management server 400 and authenticate the user. Furthermore, the management server 400 can approve charging by integrating the information received from the information collection device 300 and the charging server 500. Operation S110 will be described in detail later with reference to FIG. 5.
[0074] After operation S110, operation S120 may be performed.
[0075] In operation S120, the charger 200 can charge the target device 100. The management server 400 transmits control information to the charging server 500, and the charging server 500 can convert the control information received from the management server 400. The charging server 500 can transmit the control information to the charger 200. The control information may include charging authorization information. The charger 200 receives the control information from the charging server 500 and can start charging the target device 100. When charging of the target device 100 is completed, the charger 200 can end charging.
[0076] After operation S120, operation S130 may be performed.
[0077] In operation S130, the management server 400 can bill the user of the target device 100. When charging is completed, the information collection device 300 can transmit information regarding the charging completion and the amount of power used to the management server 400. Furthermore, the charger 200 can transmit information regarding the charging completion and the amount of power used to the charging server 500, and the charging server 500 can transmit the information received from the charger 200 to the management server 400. The management server 400 can calculate the charging cost by integrating the information received from the information collection device 300 and the charging server 500. That is, the management server 400 can calculate the charging cost based on the amount of power used received from the information collection device 300 and the charging server 500.
[0078] The management server 400 can charge the charging fee to the user. The management server 400 can charge the charging fee to the user identified in operation S110 using a pre-stored payment method. Operation S130 will be described in detail later with reference to FIG. 6.
[0079] FIG. 5 is a flowchart specifically illustrating the operation of authenticating a user of the target device of FIG.
[0080] The embodiment shown in FIG. 5 is only one embodiment, and the order of operations in various embodiments of the present invention may differ from that shown in FIG. 5, and some steps shown in FIG. 5 may be omitted, the order of steps may be changed, or steps may be combined.
[0081] Referring to FIG. 5, the operation of authenticating the user of the target device 100 may include an operation of connecting the target device 100 and the charger 200 (S111), an operation of the information collection device 300 transmitting first connection information to the management server 400 (S112), an operation of the management server 400 recognizing the information collection device 300 and acquiring user authentication information (S113), an operation of the charger 200 transmitting second connection information to the charging server 500 (S114), an operation of the charging server 500 transmitting the second connection information to the management server 400 (S115), an operation of determining whether the first connection information and the second connection information match (S116), an operation of approving (S117), and an operation of not approving (S118).
[0082] In operation S111, the target device 100 and the charger 200 may be connected. According to an embodiment, a plug or a power line of the charger 200 may be coupled to the target device 100, but is not limited thereto. After operation S111, operation S112 and operation S114 may be performed.
[0083] In operation S112, the information collection device 300 may transmit first connection information to the management server 400. When the target vehicle and the charger 200 are connected, the information collection device 300 may recognize the connection of the charger 200. The information collection device 300 may generate the first connection information. According to an embodiment, the first connection information may include information collected by the information collection device 300, such as whether the target device 100 and the charger 200 are connected, the connection time, and SoC information. The information collection device 300 may transmit the first connection information to the management server 400. After operation S112, operation S113 may be performed.
[0084] In operation S113, the management server 400 can recognize the information collection device 300 and acquire user authentication information. When the information processing device transmits the first connection information to the management server 400, the management server 400 can store the first connection information. Meanwhile, the management server 400 can recognize the information collection device 300 and identify the user of the target device 100 based on the identification information of the recognized information collection device 300. Furthermore, the management server 400 can acquire user authentication information of the identified user. After operation S113, operation S116 may be performed.
[0085] In operation S114, the charger 200 may generate second connection information and transmit the second connection information to the charging server 500. The charger 200 may recognize the target device 100 connected to the charger 200 through at least one power cable included in the power line of the charger 200. According to an embodiment, the charger 200 may acquire information about the target device 100 through the power line. The charger 200 may generate the second connection information based on the acquired information about the target device 100. The second connection information may include whether the charger 200 and the target device 100 are connected, the connection time, SoC (State of Charge) information, etc. The charger 200 may transmit the generated second connection information to the charging server 500. Operation S115 may be performed after operation S114.
[0086] In operation S115, the charging server 500 may transmit the second connection information to the management server 400. According to an embodiment, the charging server 500 may convert the second connection information received from the charger 200, but is not limited thereto. After operation S115, operation S116 may be performed.
[0087] In operation S116, the management server 400 may determine whether the first connection information and the second connection information match. The management server 400 may store the first connection information received from the information collection device 300 and the second connection information received from the charging server 500. The management server 400 may also integrate the first connection information and the second connection information. According to an embodiment, the management server 400 may compare the first connection information and the second connection information. If the management server 400 determines that the first connection information and the second connection information match, operation S117 may be performed. If the management server 400 determines that the first connection information and the second connection information do not match, operation S118 may be performed.
[0088] In operation S117, the management server 400 may approve the charging of the charger 200. After operation S117, operation S120 may be performed.
[0089] In operation S118, the management server 400 may not approve the charging of the charger 200. According to an embodiment, the management server 400 may terminate the charging of the target device 100 of the charger 200 via the charging server 500.
[0090] FIG. 6 is a flowchart specifically showing the operation of charging the user of the target device of FIG.
[0091] The embodiment shown in FIG. 6 is only one embodiment, and the order of operations in various embodiments of the present invention may differ from that shown in FIG. 6, and some steps shown in FIG. 6 may be omitted, the order of steps may be changed, or steps may be combined.
[0092] Referring to FIG. 6, the operation of charging the user of the target device 100 may include an operation of the information collection device 300 transmitting first charging information to the management server 400 (S131), an operation of the charger 200 transmitting second charging information to the charging server 500 (S132), an operation of the charging server 500 transmitting the second charging information to the management server 400 (S133), an operation of the management server 400 integrating the first charging information and the second charging information to calculate the cost (S134), and an operation of charging the cost to the user (S135).
[0093] In operation S131, the information collecting device 300 may transmit first charging information to the management server 400. The information collecting device 300 may generate the first charging information. According to an embodiment, the information collecting device 300 may store the amount of power provided from the charger 200 to the target device 100. According to another embodiment, the information collecting device 300 may store the amount of power used by the charger 200 to charge the target device 100. The information collecting device 300 may generate the first charging information based on the amount of power used. The first charging information may include the amount of power used by the charger 200 or the amount of power provided from the charger 200 to the target device 100. The information collecting device 300 may transmit the generated first charging information to the management server 400. After operation S131, operation S134 may be performed.
[0094] In operation S132, the charger 200 may transmit second charging information to the charging server 500. The charger 200 may generate the second charging information. According to an embodiment, the charger 200 may store the amount of power used to charge the target device 100. The charger 200 may generate the second charging information based on the amount of power used. The second charging information may include the amount of power used by the charger 200. According to an embodiment, the second charging information may include charging status information of the target device 100. The charger 200 may transmit the generated second charging information to the charging server 500. After operation S132, operation S133 may be performed.
[0095] In operation S133, the charging server 500 may transmit the second charging information to the management server 400. The charging server 500 may transmit the second charging information to the management server 400. According to an embodiment, the charging server 500 may convert the second charging information received from the charger 200, but is not limited thereto. After operation S133, operation S134 may be performed.
[0096] In operation S134, the management server 400 can calculate the cost by integrating the first charging information and the second charging information. The management server 400 can calculate the charging cost based on the first charging information and the second charging information. The management server 400 can calculate the charging cost based on the power usage amount obtained by integrating the first charging information and the second charging information. After operation S134, operation S135 can be performed.
[0097] In operation S135, the management server 400 can charge a fee to the user of the target device 100. The management server 400 can charge a charging fee to the user of the target device 100 using a preset payment method. The management server 400 can recognize the information collection device 300 to identify the user, and extract data related to the identified user from the stored user data. The management server 400 can charge a fee to the user based on the extracted data.
[0098] The above description is merely an illustrative example of the technical ideas disclosed in this document, and a person having ordinary skill in the art to which the embodiments disclosed in this document belong may make various modifications and variations without departing from the essential characteristics of the embodiments disclosed in this document.
[0099] Therefore, the embodiments disclosed in this document are intended to illustrate, not limit, the technical ideas disclosed in this document, and the scope of the technical ideas disclosed in this document is not limited by such embodiments. The scope of protection of the technical ideas disclosed in this document should be interpreted by the scope of the attached claims, and all technical ideas within the scope equivalent thereto should be interpreted as being included in the scope of rights of this document. [Explanation of symbols]
[0100] 10 Charging System 100 Target Device 200 charger 300 Information Gathering Device 400 Management Server 410 First Communication Circuit 420 First Controller 500 charging servers 510 Second Communication Circuit 520 Second Controller
Claims
1. a communication circuit that receives first charging information from an information collection device connected to a target device and receives second charging information transmitted from a charger corresponding to the target device from a charging server; a controller that manages a connection between the charger and the target device and a cost associated with use of the charger based on the first charging information and the second charging information.
2. The server according to claim 1 , wherein the controller recognizes an information collection device connected to the target device, and verifies user authentication information and payment information of the target device based on identification information of the recognized information collection device.
3. The server according to claim 2 , wherein the communication circuit transmits charging approval information and billing completion information to the charging server.
4. The server according to claim 3 , wherein the communication circuit transmits the charging approval information and the billing completion information to the information collection device via an LTE communication network.
5. the first charging information includes connection information between the charger and the target device recognized by the information collection device, The server according to claim 1 , wherein the second charging information includes connection information between the charger and the target device recognized by the charger.
6. The server of claim 1 , wherein the first charging information includes charging status information of the target device.
7. the first charging information includes a power usage capacity of the charger recognized by the information collection device, The server according to claim 1 , wherein the second charging information includes a power consumption capacity of the charger recognized by the charger.
8. The server of claim 7 , wherein the controller uses the first charging information and the second charging information to calculate a cost to be charged to a user of the target device.
9. a communication circuit that transmits second charging information received from the charger to a management server and receives control information related to the operation of the charger from the management server; a controller that controls an operation of the charger based on the control information.
10. The charging server according to claim 9 , wherein the controller controls the charger to charge the target device based on the control information.
11. The charging server according to claim 9, wherein the communication circuit, when receiving charging completion information from the management server, transmits the charging completion information to the charger.
12. a management server that receives first charging information from an information collection device connected to the target device; a charging server that receives second charging information from a charger corresponding to the target device and transmits the second charging information to the management server; The management server integrates the first charging information and the second charging information to manage costs associated with connection of the target device and use of the charger.
13. The charging system according to claim 12, wherein the management server transmits control information relating to an operation of the charger to the charging server, and the charging server controls the operation of the charger based on the control information.
14. 13. The charging system according to claim 12, wherein the management server recognizes an information collection device connected to the target device, and confirms user authentication information and payment information of the target device based on identification information of the recognized information collection device.
Citation Information
Patent Citations
controller
JP2019198156A
method for charging electric vehicle
KR1020130006949A
Object detection method and apparatus of radar system
KR1020200040172A