A communication system that performs data exchange between different domains based on the OCPP protocol stack.

Abstract

This system provides a communication system that enables data exchange between different domains based on the OCPP protocol stack. [Solution] The communication system of this invention comprises an OCPP cloud server, an authentication system, a charging management system, and at least one electric vehicle charging device. The communication system further comprises at least one independent gateway, or the gateway is integrated into the electric vehicle charging device. The gateway comprises a main control unit, a network unit, an IoT unit, a storage unit, and a power supply unit, with the main control unit connected to the network unit, IoT unit, storage unit, and power supply unit, respectively. The network unit is connected to the OCPP cloud server, the electric vehicle charging device is connected to the main control unit, and the IoT unit is configured to communicate with a local IoT device or electric vehicle. In this way, by introducing a gateway and utilizing the resources of an existing Electric Vehicle Charging Protocol (OCPP) cloud server, it is possible to manage and control IoT devices in different domains.

Description

Technical Field

[0001] The present invention relates to the technology in the field of remote management of vehicle charging equipment, and particularly to a communication system that performs data communication between different regions based on the OCPP protocol stack.

Background Art

[0002] The OCPP protocol is widely used in the field of remote management of vehicle charging facilities. Especially in the application of remote monitoring and control of electric vehicle charging stations, it is necessary to use a dedicated cloud server for management. Currently, many electric vehicle charging management companies already have OCPP cloud servers for managing their own operations. OCPP usually combines the WebSocket protocol and JSON-formatted messages for data exchange (refer to the OCPP v2.0.1 specification). In this protocol, various operation types are defined. Among them, the Data Transfer command (usable in v1.6 or v2.0.1) and customData, which is a user-defined data item allowed within each command (usable in v2.0.1), are flexible data transmission mechanisms that enable the transmission of custom information that is not standardized but requires corresponding handling from the server to the charging station or from the charging station to the server.

[0003] With the popularization of distributed power generation, energy storage equipment, and electric vehicles, it has become difficult to meet the need for coordinated management of various energy data such as power generation, power purchase, and power sales by only managing charging behavior. In recent years, as smart devices penetrate all aspects of life, IoT technology has been widely used in places such as homes, offices, and factories, and the demand for highly intelligent management in home, enterprise, and industrial environments has been increasing. IoT devices usually communicate using various protocols such as ModBus RTU, CAN, ZigBee (refer to ETSI TS 103 397 for support of IoT protocols). However, the following problems exist in the application of these current technologies. (1) It is necessary to independently develop and maintain a dedicated IoT platform. (2) Data transmission requires an additional protocol conversion layer, complicating the system. Conventional OCPP cloud servers are primarily used for centralized management of the operating status and business processes of electric vehicle charging stations, and data exchange is limited to communication requirements related to charging stations. In other words, existing OCPP cloud servers are mainly specialized for EV charging management, making it difficult to directly support IoT control commands and data transmission requests in non-charging operations. Due to the lack of data format compatibility, OCPP cloud servers cannot directly handle the data structures and semantics of IoT protocols. Electric vehicle charging devices and smart devices must each be managed by independent, dedicated platforms. As a result, the operational and maintenance costs and complexity of each platform increase significantly, and data exchange between platforms also becomes more complex. Given these circumstances, new technological solutions are needed to solve the aforementioned problems. [Overview of the Initiative] [Problems that the invention aims to solve]

[0004] As mentioned above, in light of the shortcomings of current technology, the main objective of this invention is to provide a communication system that enables data exchange between different domains based on the OCPP protocol stack. By introducing a gateway and utilizing the resources of an existing electric vehicle charging protocol (OCPP) cloud server, the management and control of IoT devices in different domains can be realized. [Means for solving the problem]

[0005] To achieve the aforementioned objectives, this invention employs the following technical means. The communication system for performing data exchange between different domains based on the OCPP protocol stack of this invention includes an OCPP cloud server, an authentication system, a charging management system, and at least one electric vehicle charging device.

[0006] The communication system includes at least one independent gateway or a gateway integrated into the electric vehicle charging device. The gateway comprises a main control unit, a network unit, an IoT unit, a storage unit, and a power supply unit, with the main control unit connected to the network unit, IoT unit, storage unit, and power supply unit, respectively.

[0007] The network unit is configured to communicate with the OCPP cloud server, the electric vehicle charging device is configured to communicate with the main control unit, and the IoT unit is configured to communicate with local IoT devices or electric vehicles.

[0008] This invention has clearly superior advantages and beneficial effects compared to existing art. Specifically, as can be understood from the aforementioned technical means, The solution is primarily implemented by introducing a separate gateway or integrating a gateway within the electric vehicle charging device. By utilizing the resources of existing Electric Vehicle Charging Protocol (OCPP) cloud servers, OCPP-supporting cloud servers can be seamlessly extended to IoT control in the smart home / smart office domain, enabling data sharing and coordinated control between devices. This eliminates the need to build a new, dedicated IoT service platform, ensuring security while achieving cross-domain smart applications and enabling the management and control of IoT devices belonging to different domains.

[0009] In order to more clearly explain the structural features and effects of this invention, the invention will be described in detail below with reference to the attached drawings and specific embodiments. [Brief explanation of the drawing]

[0010] [Figure 1] This is a diagram of a communication system (independent gateway method) that performs data exchange between different domains based on the OCPP protocol stack, according to an embodiment of the present invention. [Figure 2] This is a diagram illustrating the configuration of a communication system that performs data exchange between different domains based on the OCPP protocol stack, according to an embodiment of the present invention (a method in which an electric vehicle charging device is modified to provide gateway functionality). [Figure 3] This is a time-series diagram of the cross-domain data transmission flow in a communication system that performs data exchange between different domains based on an OCPP protocol stack, according to an embodiment of the present invention. [Modes for carrying out the invention]

[0011] Figures 1 to 3 illustrate a specific configuration according to an embodiment of the present invention. This invention relates to a communication system that performs data exchange between different domains based on the OCPP protocol stack. It primarily utilizes existing electric vehicle charging protocol (OCPP) cloud server resources and extends the charging station management cloud server into the IoT service domain, thereby enabling the management and control of IoT devices belonging to different domains. Unlike conventional methods that require the construction of separate IoT cloud platforms to manage IoT devices, this invention directly utilizes existing OCPP cloud servers without relying on additional IoT cloud servers or independent IoT management platforms, and configures them as a unified data storage and management platform. Typically, the OCPP cloud server is communicated with an authentication system and a charging management system. The OCPP cloud server receives status information of charging stations and transmits remote control commands (start / stop charging). The charging management system records charging data (time, power consumption, charges, etc.) and supports order generation and payment. The OCPP cloud server, authentication system, and charging management system form a closed loop through standardized protocols and data flows.

[0012] This invention does not modify or replace the OCPP protocol itself, but rather enables data exchange between different domains within the scope of the extension mechanisms permitted by the OCPPv1.6 / v2.0.1 specification.

[0013] The communication system for data exchange between different domains based on the OCPP protocol stack of this invention is also an extended application communication system based on data transmission commands, and includes an OCPP cloud server and at least one electric vehicle charging device for managing electric vehicle charging stations. Here, the OCPP cloud server includes a functional module that operates on an existing OCPP protocol stack (the functional module is configured to receive and process messages such as local IoT or electric vehicle status information and control command feedback transmitted from the gateway, and generate a corresponding business logic response based on that), and communicates with the aforementioned device via data transmission commands. The communication system may further include at least one independent gateway, or the electric vehicle charging device may be modified to have gateway functionality, i.e., the gateway may be integrated inside the electric vehicle charging device. The gateway is configured to decode standard data transmission commands transmitted from the OCPP cloud server and map their contents to various local IoT network environments (supporting protocols such as Modbus RTU, MBus, Wi-Fi, and ECHONET-Lite). Simultaneously, it can receive information and control commands from second-domain devices other than electric vehicle charging devices (e.g., home smart devices, office sensors, factory monitoring points, etc.) and reliably upload them to the OCPP cloud server using the same OCPP communication mechanism.

[0014] The communication system further includes at least one communication hub (the electric vehicle charging device side supports the communication hub interface) for connecting various local IoT devices or electric vehicles. The gateway receives data transmission commands sent from the OCPP cloud server, converts them into messages conforming to the communication protocol format with the communication hub and the IoT devices or electric vehicles connected to the communication hub, and transmits the messages to the communication hub. The data transmission commands include control information and / or status requests. The conversion to messages conforming to the communication protocol format with IoT devices or electric vehicles includes at least the following steps: that is, mapping the data transmission commands received from the OCPP cloud server to specific actions such as local I / O control and / or sensor readings. The gateway also has the function of acquiring information from local IoT devices or electric vehicles, packaging it as a message conforming to the data transmission command format, and sending it to the OCPP cloud server. Typically, the gateway and local IoT devices or electric vehicles connect or communicate via at least one specific communication protocol from the following: Wi-Fi, LAN, Modbus RTU, ECHONET-Lite, ZigBee, CAN, UART, or RS485. These protocols can be added through software updates.

[0015] An independent gateway includes a chassis (defined as the first chassis) and a main control unit (main control chip), network unit, IoT unit, storage unit, and power supply unit located inside it. The main control unit is connected to the network unit, IoT unit, storage unit, and power supply unit, respectively. The electric vehicle charging device is located outside the chassis and communicates with the main control unit. The IoT unit includes one or more communication interfaces. The communication interfaces include one or more of the following: Wi-Fi interface, LAN interface, CAN interface, and RS485 interface.

[0016] On the other hand, an electric vehicle charging device with an integrated gateway includes a housing (defined as the second housing), an electric vehicle charging module, a main control unit (main control chip), a network unit, an IoT unit, a storage unit, and a power supply unit, all located inside the housing. The main control unit is connected to the electric vehicle charging module, network unit, IoT unit, storage unit, and power supply unit, respectively, and the electric vehicle charging device is connected to the main control unit.

[0017] The aforementioned communication system can operate in both connected and disconnected states of the power system. Under normal conditions, it communicates data with the cloud server via the OCPP protocol. In emergency situations, it manages data locally and resynchronizes the local data with the cloud server after system recovery.

[0018] A communication system that performs data exchange between different domains based on the aforementioned OCPP protocol stack includes the following steps: (a) Authentication establishment stage. The gateway uses standard EV user authentication information to register and authenticate with the charging operator's OCPP cloud server. It is sufficient to use existing user authentication methods (ID / password method, etc.). (b) Data relay process. When the gateway receives a data transmission command from the OCPP cloud server, it transfers control information to IoT devices in the local IoT network based on the specifications included in the data transmission command, collects response data from the IoT devices, and transfers it according to the data transmission command protocol. (c) The gateway adds IoT device control functionality while retaining all the existing management and monitoring functions for electric vehicle charging devices via the OCPP cloud server.

[0019] As can be seen from Figures 1 and 2, the basic configuration of this data transmission command-based extended application type communication system consists of the following three core parts. (1) OCPP Server Module. It is a standard OCPP cloud service deployed by existing charging operators and supports data transmission command operations (v1.6 and above). (2) Smart Gateway or an electric vehicle charging device with gateway functionality. It has an RS-485 / UART interface for connecting to the OCPP communication network, supports standard OCPP communication interfaces (such as v1.6 or v2.0.1), and multiple IoT protocols, and has functions such as protocol conversion, security enhancement, and network management. The gateway has various modules and interfaces (selectively installed) for supporting IoT protocols and connects to various local IoT devices through, for example, Wi-Fi, LAN (RJ45), Bluetooth, Wi-SUN, ModBus RTU, etc. On the other hand, the gateway connects to the Internet via wired / wireless modules such as LTE, Wi-Fi, LAN (RJ45), etc. and communicates with the OCPP cloud server. (3) Local IoT Device Network. It includes various device bus interfaces such as ZigBee, ModBus, CAN, etc. and is applicable to diverse applications such as smart meters, environmental sensors, and electric vehicles.

[0020] The OCPP cloud server adds IoT device management functionality. Furthermore, it monitors various IoT devices connected to the gateway and enables smart management using the OCPP protocol's DataTransfer.req and DataTransfer.conf commands (v1.6 or v2.0.1 compatible), or the user-defined data item customData (v2.0.1 compatible) permitted by each command. Additionally, by using the OCPP DataTransfer command (v1.6 or v2.0.1 compatible) or the user-defined data item customData (v2.0.1 compatible), CAN signals can be sent to the vehicle via the gateway, allowing the server to remotely diagnose the vehicle and return the diagnostic results to the server. Because the server directly transfers control commands for IoT devices or electric vehicles using the DataTransfer command or the user-defined data item customData within the command, the gateway does not need to process the actual content of the control commands and directly sends the commands from the gateway interface to the IoT device or electric vehicle. Conversely, data transmitted from IoT devices is transparently sent directly to the server using the DataTransfer command or the user-defined data item customData within the command, requiring no processing by the gateway. This operation significantly reduces the computational load on the gateway and improves the gateway's compatibility with various IoT devices.

[0021] The gateway can connect to existing OCPP cloud servers using a standard user authentication mechanism, requiring no additional registration or modifications. The gateway is granted server access as a "trusted" device. Furthermore, the gateway, as an independent deployment unit, features a standard interface and scalability. Based on the OCPP communication protocol, the gateway has remote or local software update capabilities, allowing updates to increase the types of IoT devices it can support and enhance system scalability.

[0022] The external cloud server is the same cloud management server that operates on the existing OCPP protocol stack. In addition, electric vehicles and local IoT devices include at least one smart device used in scenarios such as home smartening, office automation, and industrial monitoring. This enables electric vehicle charging service providers to expand their existing mature cloud infrastructure to new IoT fields and meet additional business needs without investing additional resources to build an independent service platform. Existing users can realize smart applications such as device interconnection, automation control, and remote monitoring through remote software updates, and potential new users can connect to the IoT ecosystem, improving operational efficiency and expanding service value.

[0023] Referring to Figure 3, the data transmission flow will be described. (1) Transmission of charging service data. Use the standard OCPP mechanism and follow the conventional charging station management flow. (2) Transmission of custom IoT control information. When a user operates an IoT device (such as lighting on / off, air conditioner settings, etc.) on the charging service provider's management platform, it is processed according to the following flow. (a) User operates the IoT device through the Web interface or the interface of the smartphone app → OCPP cloud server (using the standard data transmission mechanism) → Smart gateway (extracts the device control signal from the data transmission request and sends it to the IoT device via the interface) → IoT device (response signal) → Smart gateway packages the response signal and returns it to the OCPP cloud server → OCPP cloud server. (b) IoT device status update → IoT device sends a status signal → Smart gateway packages the status signal and returns it to the OCPP cloud server → OCPP cloud server responds to the status update or sends an additional operation signal → Smart gateway → IoT device (operation signal).

[0024] Naturally, the method of this invention can be applied to a variety of smart environment fields, for example, in the following three areas. (1) Smart Home. Charging and diagnostics of electric vehicles in the garage are performed via an existing OCPP cloud server, while simultaneously sending commands to smart devices within the home. Examples include adjusting lighting and reading data from temperature sensors. (2) Office building management. The OCPP cloud server manages the charging of electric vehicles in the office building parking lot, and at the same time controls smart systems and equipment such as curtains in the office based on occupancy status or schedule via a gateway. (3) Smart factory automation (using IoT as an example). The gateway collects the operating status of local equipment (devices connected via CAN / ModBus / PLC, etc.), uploads the data to the cloud for analysis, and makes optimization suggestions.

[0025] As described above, the communication system that performs data exchange between different domains based on the OCPP protocol stack of this invention achieves the following novel features by utilizing the OCPP data transmission mechanism. (1) Based on the OCPP protocol, it provides a technical route to realize the coordinated control of IoT and electric vehicles without rebuilding cloud services, and reduces operational and capital investment costs by reusing existing OCPP infrastructure facilities. (2) Provide a unified connection point to simplify data conversion and communication across various IoT protocols. Based on the existing OCPP protocol, it enables bidirectional extension of the data transmission mechanism, builds a flexibly configurable data transmission flow, and supports a variety of IoT or electric vehicle communication protocols. (3) Combine charging operation services with smart home / office applications to form a hybrid service platform model and enhance value-added services (e.g., smart home integration and electric vehicle management) provided by charging operators. (4) Provide a unified security authentication framework to ensure the security of communication between different devices. For example, by utilizing the OCPP DataTransfer mechanism or the user-defined data item customData in the directive, data format compatibility, security, unified management, and interoperability can be improved. customData is an important component of the protocol's flexible design and is used to send and receive custom data and extensions other than standard messages between charging points and the central system. This mechanism allows equipment manufacturers and operators to transmit non-standard information based on specific business needs such as regional policies, hardware characteristics, and third-party integrations, while maintaining protocol subject compatibility.

[0026] Through the above configuration design, this invention centrally arranges data linkage functions between different domains at the system configuration level and fixes these inter-domain linkage functions to a configuration node called a gateway, thereby improving the overall versatility, scalability, and compatibility of the system.

Claims

1. A communication system that performs data exchange between different domains based on an OCPP protocol stack, including an OCPP cloud server, an authentication system, a charging management system, and at least one electric vehicle charging device, The communication system further comprises at least one independent gateway, or is configured to integrate a gateway within the electric vehicle charging device. The gateway comprises a main control unit, a network unit, an IoT unit, a storage unit, and a power supply unit, and the main control unit is connected to the network unit, the IoT unit, the storage unit, and the power supply unit, respectively. A communication system that performs data exchange between different domains based on an OCPP protocol stack, characterized in that the network unit is connected to the OCPP cloud server, the electric vehicle charging device is connected to the main control unit, and the IoT unit is connected to a local IoT device or an electric vehicle.

2. A communication system for performing data exchange between different domains based on the OCPP protocol stack according to claim 1, characterized in that the independent gateway comprises a first housing, the main control unit, the network unit, the IoT unit, the storage unit, and the power supply unit are arranged inside the first housing, and the electric vehicle charging device is arranged outside the first housing.

3. A communication system for performing data exchange between different domains based on the OCPP protocol stack according to claim 1, characterized in that an electric vehicle device with an internally integrated gateway comprises a second housing, and the electric vehicle device, the main control unit, the network unit, the IoT unit, the storage unit, and the power supply unit are all located within the second housing.

4. The communication system further comprises at least one communication hub for connecting local IoT devices or electric vehicles, and the gateway receives a data transmission command transmitted from the OCPP cloud server, converts the command into a message conforming to the communication protocol format for communication with the communication hub and IoT devices or electric vehicles connected to the communication hub, and transmits the message to the communication hub, characterized in that it performs data exchange between different domains based on the OCPP protocol stack according to claim 1.

5. A communication system that performs data exchange between different domains based on the OCPP protocol stack according to claim 1, characterized in that the IoT unit connects to or communicates with a local IoT device or electric vehicle using at least one type of communication protocol, and the communication protocol includes one of the following: Wi-Fi communication protocol, LAN communication protocol, Modbus RTU communication protocol, ECHONET Lite communication protocol, ZigBee communication protocol, CAN communication protocol, UART communication protocol, and RS485 communication protocol.

6. A communication system that performs data exchange between different domains based on the OCPP protocol stack according to claim 1, characterized in that the IoT unit is provided with one or more communication interfaces.

7. A communication system that performs data exchange between different domains based on the OCPP protocol stack according to claim 6, characterized in that the communication interface includes one or more of the following: Wi-Fi interface, LAN interface, CAN interface, and RS485 interface.

8. A communication system for performing data exchange between different domains based on the OCPP protocol stack according to claim 1, characterized in that the network unit is equipped with a wired or wireless communication interface and the OCPP cloud server is connected to the wired or wireless communication interface.

Images