Multi-network ev charger with support for multiple OCPP websocket connections

Abstract

The present invention introduces a multi-network EV charger capable of supporting multiple OCPP WebSocket connections using a dynamic data processing algorithm. The system enables direct integration with multiple CMS platforms and thus eliminates the need for OCPI-based implementations. The system achieves seamless multi-network connectivity, simplified architecture, and reduced costs by leveraging dynamic data processing. The system comprises an EV charger, a multi-connection WebSocket interface, a dynamic data processing algorithm, and a network management module. The charger acts as the core device, facilitating power delivery and communication. The WebSocket interface establishes and manages simultaneous OCPP connections with multiple CMS platforms. The dynamic data processing algorithm processes incoming and outgoing data streams in real time, ensuring efficient communication and minimising latency. The network management module oversees the connectivity, prioritises tasks, and ensures system stability by dynamically allocating resources to active connections.

Description

MULTI-NETWORK EV CHARGER WITH SUPPORT FOR MULTIPLE OCPP WEBSOCKET CONNECTIONSFIELD OF THE INVENTION

[0001] The present invention relates to the field of embedded communication architecture within an electric vehicle (EV) charger that enables execution multiple independent OCPP protocol stacks and persistent WebSocket connections to a plurality of Charging Management Systems (CMS), implemented natively within the charger firmware.BACKGROUND

[0002] The usage of eco-friendly transportation such as Electric vehicles (EVs) has seen significant growth in recent years. As the number of EVs on the road continues to rise, the demand for accessible, efficient, and user-friendly charging solutions grows as well. One of the key components of EV infrastructure is the Charging Management System (CMS), which plays a crucial role in managing and coordinating the operation of EV chargers. However, the traditional approach to CMS integration poses several challenges that hinder the growth and efficiency of the EV charging ecosystem.

[0003] In the current landscape of EV charging infrastructure, most chargers are designed to connect to a single Charging Management System (CMS) using the Open Charge Point Protocol (OCPP). This architecture limits the charger to participation in a single backend network at a time.

[0004] To enable multi-network participation, interoperability is typically achieved at the backend level through CMS-to-CMS communication mechanisms, including protocols such as the Open Charge Point Interface (OCPI). Such backend mediation introduces additional architectural layers and operational dependencies, as the charger itself does not natively support simultaneous connections to multiple CMS platforms.

[0005] While backend interoperability protocols such as the Open Charge Point Interface (OCPI) enable communication between different CMS platforms, such integration occurs at the backend level and does not provide native multi-CMS connectivity within the charger itself.

[0006] Backend-level interoperability typically requires additional software layers, synchronization mechanisms, and data mediation between CMS platforms, resulting in increased architectural complexity and operational overhead. The charger remains limited to a single CMS connection, while multi-network participation is managed externally through backend coordination.

[0007] European patent application EP2016062400 discloses a charging station for electric vehicles as well as interface device in such a charging station for communication of a control unit in a charging station with a control unit in an external charging station. Here a a first protocol is implemented in the operator interface for communication with the control centre and a second protocol is used for communication with an external control unit.

[0008] Patent application WO2024213927A1 discloses a system for managing the distributed electrical power resources of an electrical infrastructure including vehicle charging systems. It utilizes a hub connected to Common Services Electrical Board by means of electrical wiring and communication protocols. This helps in reducing the number of isolated proprietary electrical boards and stakeholders involved in the adaptation and provides a local management system for multiple proprietary charging points.

[0009] US patent application US2024174117 techniques for managing charging stations with diverse communication capabilities. This invention utilizes a communication adapter communicatively coupled with a first, second, and third communication controller which is configured for connectivity between a first and second EVSE charger.

[0010] However, in existing architectures, interoperability between multiple CMS platforms is typically achieved at the backend level through roaming or protocol mediationmechanisms. Conventional EV chargers themselves remain configured to establish a single OCPP connection to one CMS at a time.

[0011] As a result, routing or broadcasting of charger- originated messages to multiple CMS platforms is not performed natively within the charger but instead relies on backendlevel coordination. This device-level limitation restricts the charger from independently participating in multiple CMS networks simultaneously.

[0012] To address these issues, the EV charging ecosystem needs a solution that can support simultaneous connections to multiple CMS platforms without relying on centralized systems or cumbersome integration protocols like OCPI. The ideal solution would enable chargers to communicate directly with multiple CMSs, allowing operators to manage their charging infrastructure more efficiently and providing users with greater access to a wider range of networks and services.

[0013] A system that supports multiple simultaneous OCPP WebSocket connections provides a promising approach to solving this problem. The Open Charge Point Protocol (OCPP) is a widely adopted standard for communication between EV chargers and CMSs, and the WebSocket variant allows for persistent, real-time communication. However, traditional chargers are limited to a single OCPP WebSocket connection, thereby restricting their ability to interact with more than one CMS.OBJECTIVES OF THE INVENTION

[0014] One objective of the invention is to enable an EV charger to establish and maintain multiple concurrent OCPP WebSocket connections with different Charging Management Systems (CMS) directly from within the charger firmware, thereby eliminating reliance on external interoperability middleware or centralized protocol mediation systems.

[0015] Yet another objective of the invention is to leverage dynamic data processing to achieve seamless multi-network connectivity, simplified architecture, and reduced costs.

[0016] Another objective of the invention is to enable session-specific selection of a CMS platform while maintaining concurrent persistent connections to other CMS platforms.

[0017] Another objective of the invention is to provide an embedded message routing and arbitration mechanism configured to selectively route or broadcast OCPP messages among multiple CMS connections.

[0018] Another objective of the invention is to enforce logical and memory-level data isolation between CMS connections within the charger to prevent cross -platform data access.

[0019] Another objective of the invention is to dynamically allocate processing and memory resources among multiple active CMS connections to maintain stable charger performance under varying communication loads.

[0020] Another objective of the invention is to ensure continued operation of remaining CMS connections in the event of failure of any one CMS connection.

[0021] Other objects and advantages of the present invention will be more apparent from the following description when read in conjunction with the accompanying figures, which are not intended to limit the scope of the invention.SUMMARY

[0022] The present invention introduces a multi-network EV charger capable of supporting multiple OCPP WebSocket connections using a dynamic data processing algorithm. Unlike conventional chargers limited to a single CMS, this innovation enables direct integration with multiple CMS platforms, eliminating reliance on external interoperability middleware or centralized protocol mediation systems. By leveraging dynamic data processing, the system achieves seamless multi-network connectivity, simplified architecture, and reduced costs. This advancement enhances compatibility across various mobile applications, promotes scalability, and improves the operational efficiency of EV charging infrastructure.

[0023] The system comprises an EV charger, a multi-connection WebSocket interface, a dynamic data processing algorithm, and a network management module. The charger acts as the core device facilitating power delivery and communication. The WebSocket interface establishes and manages simultaneous OCPP connections with multiple CMS platforms. The dynamic data processing algorithm processes incoming and outgoing data streams in real time, ensuring efficient communication and minimizing latency. The network management module oversees the connectivity, prioritizes tasks, and ensures system stability by dynamically allocating resources to active connections.

[0024] These elements work in unison to achieve seamless multi-network integration while ensuring data security. The WebSocket interface facilitates real-time communication with multiple CMS platforms, while the dynamic data processing algorithm ensures efficient handling of concurrent data streams. The network management module coordinates the overall operation, dynamically balancing workloads and optimizing resource allocation. Crucially, the system is designed to prevent data sharing between CMS platforms, ensuring that sensitive information remains isolated and secure. This unique combination of multinetwork support, dynamic processing, and stringent data integrity makes the invention a groundbreaking advancement in EV charging technology.

[0025] The arrangement of the present invention has other features and advantages that will be apparent from or are set forth in more detail in the accompanying drawings, which are incorporated herein, and the following brief description, which together serve to explain certain principles of the present invention.BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The present invention will be better understood fully from the detailed description that is given herein below with reference to the accompanying drawings of the preferred embodiments of the present invention, which, however, should not be deemed to be a limitation to the invention to the specific embodiments, but are for the purpose of explanation and understanding only.

[0027] Figure 1: Block diagram of EV charger with multi-connection web-socket interface.DETAILED DESCRIPTION OF THE INVENTION

[0028] The embodiments herein and the various features and advantageous details thereof are explained with reference to the non-limiting embodiments and drawings in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0029] The invention is a multi-network EV charger capable of supporting multiple OCPP WebSocket connections using a dynamic data processing algorithm. This enables the charger to interface directly with multiple Charging Management Systems (CMS). The charger leverages its innovative architecture to process and manage data dynamically, ensuring seamless multi-network connectivity while maintaining compatibility with diverse mobile applications. A critical aspect of the invention is its focus on data security and integrity, ensuring that data is never shared between CMS platforms, thus safeguarding sensitive information and maintaining trust.

[0030] In conventional OCPP implementations, a single CMS endpoint URL is configured within the charger, upon which the charger initiates a WebSocket connection to the configured CMS and maintains a persistent communication channel.

[0031] In the present invention, the charger firmware supports configuration of a plurality of CMS endpoint URLs, each associated with corresponding authentication credentials and security parameters. Upon initialization, the charger establishes independent WebSocket connections to each configured CMS endpoint.

[0032] The charger classifies outgoing OCPP messages into broadcast-type messages and session-specific messages. Broadcast-type messages, including heartbeat, boot notification acknowledgments, and status notifications, are transmitted to all connected CMS platforms to maintain visibility across multiple networks.

[0033] Session-specific messages, including transaction initiation, meter values, authorization responses, and transaction termination messages, are routed exclusively to the CMS platform associated with the charging session.

[0034] Each charging session is logically bound to a selected CMS platform at session initiation, and all transaction-related OCPP communication for that session is restricted to the selected CMS while other CMS connections remain active but passive.

[0035] The charger securely stores multiple CMS endpoint URLs, authentication credentials, and cryptographic certificates in non-volatile memory, each mapped to an independent communication instance.

[0036] The system comprises an EV charger, a multi-connection WebSocket interface, a dynamic data processing algorithm, and a network management module, as shown in Fig.1. The charger acts as the core device facilitating power delivery and communication. The WebSocket interface establishes and manages simultaneous OCPP connections with multiple CMS platforms. The dynamic data processing algorithm processes incoming and outgoing data streams in real-time, ensuring efficient communication and minimizing latency. The network management module oversees the connectivity, prioritizes tasks, and ensures system stability by dynamically allocating resources to active connections.

[0037] The core of the invention is the charger. The charger is responsible for providing power delivery to the EV and simultaneously facilitate communication with the vehicle. It is integrated with a communication protocol stack that enables the exchange of crucial data such as charging status, energy consumption, and payment details. This data is then sent to the CMS platforms for processing, creating an link between the charging station and the charging management systems.

[0038] In one embodiment the system includes a multi-connection WebSocket interface. This interface is designed to enable the charger to maintain persistent, real-time WebSocket connections with multiple CMS platforms at once. The charger can continue to interface with each CMS platform without interruption for continuous updates and communication. The charger dynamically selects which CMS to communicate with based on the user’s preferences during a session. It allows for switching between different CMS platforms, which is particularly useful when a user wishes to select a specific CMS for a particular session, making the overall system more versatile and adaptable.

[0039] A dynamic data processing algorithm is utilized to handle data streams in real time, ensuring that the charger processes incoming and outgoing data efficiently. By dynamically managing the data flow, the algorithm prioritizes essential information and minimizes unnecessary data transmission. This reduces the load on the system and ensures that only the most relevant data is processed thus optimizing the performance of the charger. Furthermore, the algorithm prevents the sharing of information between CMS platforms, maintaining a high level of security. This is particularly important when dealing with sensitive user data, as it guarantees that personal and financial information remains private and is not inadvertently shared across different networks.

[0040] In one embodiment, prevention of data sharing between CMS platforms is achieved through logical isolation mechanisms implemented within the embedded firmware.

[0041] Each CMS connection operates within an independent communication context comprising a dedicated protocol state machine, message buffer, authentication credentials, and session mapping entries. These data structures are stored in memory regions that are referenced only by the corresponding CMS connection instance.

[0042] The routing engine accesses session data exclusively through a session binding registry that maps each charging session to a single CMS identifier. Transaction-related messages are constructed and transmitted only within the memory context of the associated CMS instance.

[0043] The data isolation module enforces cryptographic separation and memory partitioning between CMS sessions. No shared transaction identifiers, authentication tokens, or session metadata are exposed across CMS communication contexts. Broadcasttype system messages are replicated independently for each CMS connection rather than forwarded between CMS instances.

[0044] As a result, session-specific and credential-related information originating from one CMS is neither stored nor transmitted in the communication context of another CMS, thereby preventing cross-platform data leakage.

[0045] In one embodiment the system includes a network management module. The network management module coordinates the entire communication process. It is responsible for monitoring and controlling the different WebSocket connections. The network management module dynamically allocates resources to active connections. It does this by balancing the workload across all connections. This resource allocation is significant for maintaining the performance and reliability of the charger, particularly in environments where network conditions may fluctuate, such as in locations with heavy traffic or varying levels of signal strength.

[0046] The network management module also ensures the stability of the system by dynamically adjusting to different usage patterns. For example, if one CMS platform experiences higher levels of traffic or demand, the network management module can allocate more resources to that connection for it to remain responsive and operational. Similarly, if certain CMS platforms experience lower traffic, the module can adjust resources accordingly to prevent unnecessary load on the system. The module is also responsible for managing the routing of messages between the charger and the CMS platforms. The combination of the charger, multi-connection WebSocket interface, dynamic data processing algorithm, and network management module creates a robust and flexible system that supports multi-network EV charging.

[0047] In various embodiments, the multi-network electric vehicle (EV) charger comprises a power delivery module configured to deliver electrical energy to an electric vehicle, andan embedded communication controller. The embedded communication controller includes a plurality of Open Charge Point Protocol (OCPP) stacks instantiated therein and a multi-WebSocket interface configured to establish and maintain simultaneous persistent WebSocket connections with a plurality of Charging Management Systems (CMS). The EV charger further comprises a message routing engine configured to selectively route, replicate, or restrict OCPP messages between the EV charger and one or more CMS platforms, and a data isolation module configured to prevent the sharing of session-specific data between CMS platforms, wherein the EV charger natively supports simultaneous communication with multiple CMS platforms.

[0048] In one embodiment, each CMS WebSocket connection is monitored independently through a connection health monitoring module within the embedded controller. Upon detection of disconnection due to network failure, CMS unavailability, or communication timeout, the charger initiates an autonomous periodic reconnection attempt specific to the disconnected CMS without interrupting other active CMS connections.

[0049] In one embodiment, the embedded controller comprises a microprocessor or microcontroller unit (MCU) integrated within the EV charger, including volatile memory (RAM), non-volatile memory (Flash or EEPROM), and at least one network interface module selected from Ethernet, cellular, or Wi-Fi communication modules.

[0050] The controller executes firmware instructions stored in non-volatile memory to implement the multi-CMS communication framework, including independent OCPP protocol stack instances and routing logic.

[0051] In one embodiment, each CMS WebSocket connection is associated with an independent connection state variable and retry timer maintained by the embedded controller.

[0052] Disconnection is detected based on WebSocket close events, heartbeat timeout expiration, or network communication errors. Upon detection of a disconnection event for a specific CMS, the connection state is updated to a disconnected status.

[0053] A retry scheduler associated with that CMS instance initiates reconnection attempts at predefined time intervals. The retry interval may be fixed or progressively increased based on a backoff policy.

[0054] Each CMS connection maintains an independent retry timer and state machine, such that reconnection attempts for one CMS do not block or suspend communication tasks associated with other active CMS connections.

[0055] During reconnection attempts, message queues and protocol states associated with other CMS connections remain operational and unaffected.

[0056] The reconnection mechanism operates independently for each CMS using separate retry timers and state management processes, thereby ensuring that failure of one CMS connection does not affect ongoing communication with other CMS platforms.

[0057] In one embodiment, the embedded controller of the charger includes a message routing and arbitration module implemented as a firmware-level software component executing on the charger microprocessor.

[0058] The routing module comprises:(a) a message classifier,(b) a session ownership registry,(c) a routing decision engine, and(d) a command arbitration controller.

[0059] The message classifier inspects each outgoing and incoming OCPP message and determines its category based on message type identifiers defined in the OCPP protocol specification. The classifier distinguishes among Broadcast-type messages (e.g., Heartbeat, StatusNotification, BootNotification), Session-specific messages (e.g., Authorize, StartTransaction, StopTransaction, MeterValues) and Configuration or control commands (e.g., ChangeAvailability, RemoteStartTransaction)

[0060] The charger maintains an internal session ownership registry stored in volatile memory, mapping each active charging session to a specific CMS connection instance. Upon initiation of a charging session, the selected CMS is registered as the session owner. All transaction-related OCPP messages for that session are bound to the corresponding CMS connection until session termination.

[0061] The routing decision engine applies predefined routing rules based on message classification and session ownership mapping. Broadcast-type messages are replicated and transmitted to all active CMS WebSocket connections. Session-specific messages are transmitted exclusively to the CMS identified in the session ownership registry. Nonsession system events may be routed based on configurable policy rules.

[0062] The command handling module processes incoming OCPP control commands received from each connected CMS platform in accordance with the OCPP protocol specification. Upon initiation of a charging session, the charger binds the session to the CMS that initiated or authorized the session. The session ownership information is stored in the session registry. For commands relating to an active charging session, the charger validates whether the originating CMS corresponds to the session owner. If the originating CMS does not match the session owner, the command is rejected or ignored. CMS platforms that are not associated with an active charging session remain capable of initiating new sessions or issuing non-session-specific commands as permitted under the OCPP protocol.

[0063] In one embodiment, each CMS connection operates within an independent communication thread or event-driven task context. The routing and arbitration module interacts with these contexts through message queues associated with each CMS connection instance.

[0064] Each CMS connection instance maintains independent buffers, protocol state machines, and transaction identifiers. The routing engine accesses these buffers through isolated memory references to prevent cross-connection state contamination.

[0065] In one embodiment, the embedded controller of the charger implements a multi-CMS communication framework comprising a connection manager, independent OCPP protocol stack instances, a session binding registry, and a routing and validation engine.

[0066] The connection manager maintains a list of configured CMS endpoint URLs and establishes independent WebSocket connections to each CMS. Each connection operates with an isolated protocol state and message buffer.

[0067] The charger maintains an in-memory session binding registry mapping each active charging session to a specific CMS connection. When a session is initiated, the originating CMS is recorded as the session owner.

[0068] Outgoing OCPP messages are processed according to predefined routing rules. Non-transactional system messages are broadcast to all connected CMS platforms, whereas transaction-specific messages are routed exclusively to the CMS identified in the session binding registry.

[0069] Incoming commands from CMS platforms are validated against the session binding registry. Only the CMS associated with the active session is permitted to issue sessionspecific control commands, while other CMS connections remain operational but restricted from affecting that session.

[0070] The routing and validation logic is executed within the embedded firmware through internal message queues, ensuring concurrent and isolated handling of multiple CMS connections.

[0071] In one embodiment, each CMS WebSocket connection operates as an independent communication instance within the embedded controller. Failure, timeout, or unavailability of any one CMS connection does not interrupt or suspend other active CMS connections. The charger continues normal operation with remaining connected CMS platforms while isolating the failed connection.

[0072] The system architecture thereby eliminates single-point-of-failure conditions associated with centralized or single-backend communication models.

[0073] In one embodiment, the charger supports concurrent communication with CMS platforms implementing different versions of the Open Charge Point Protocol (OCPP). The embedded communication controller includes CMS -specific adaptation logic to accommodate variations in OCPP implementations among different CMS platforms. The embedded communication controller is configured to instantiate independent protocol stacks corresponding to different OCPP versions. Each CMS connection operates using its respective protocol version without affecting the operation of other CMS connections using different protocol versions.

[0074] In one embodiment, the embedded controller maintains independent OCPP protocol stack instances corresponding to the version configured for each CMS connection. Each CMS endpoint configuration includes an associated OCPP version identifier.

[0075] Upon establishment of a WebSocket connection, the charger activates the protocol stack instance corresponding to the configured OCPP version (e.g., OCPP 1.6 or OCPP 2.0.1). Each protocol stack maintains its own message schema definitions, state machine logic, transaction handling rules, and feature set as defined by the respective OCPP version.

[0076] The routing engine interfaces with the appropriate protocol stack instance based on the CMS connection context, thereby allowing concurrent execution of different OCPP versions without cross-version interference.

[0077] Version-specific message encoding and decoding are handled within the respective protocol stack instance, ensuring protocol compliance for each CMS connection independently.

[0078] The charger further includes a version-aware message handling module configured to process and generate protocol-compliant messages based on the specific OCPP version associated with each CMS connection.

[0079] The number of CMS connections supported by the charger is not inherently limited by the architecture but is determined by the processing capability, memory capacity, and network bandwidth of the embedded controller. The communication framework is designed to scale to multiple concurrent CMS connections subject to available system resources and implementation constraints.

[0080] Yet another feature of the system includes real-time monitoring, which enables users to track the status of their charging sessions as they happen. With this capability, users can receive live updates of important metrics through mobile applications such as charging progress, time remaining, and energy consumption. This feature improves the user experience and allows individuals to plan and manage their time more effectively.

[0081] Another important aspect of the system relates to communication security. Each CMS WebSocket connection may be established using either standard WebSocket (ws) or secure WebSocket (wss) protocols based on configuration.

[0082] In configurations utilizing secure WebSocket (wss), Transport Layer Security (TLS) is employed to encrypt data exchanged between the charger and the respective CMS platform. Each CMS connection may use independent security credentials, certificates, and authentication parameters as defined by the corresponding configuration.

[0083] The system may be integrated with smart grid technology, which would enhance its efficiency and flexibility. Through this integration, the charger can adjust its power usage based on the demand from the grid or the availability of renewable energy sources. For example, during periods of high grid demand, the system could reduce the power drawn by the charger to help prevent strain on the grid. Conversely, when renewable energy sources such as solar or wind are abundant, the charger could increase its energy usage. This feature helps in balancing energy loads.

[0084] The process to achieve multiple web-socket connections involves the following steps:

[0085] Stepl: Initialization- Upon connection of the EV to the charger, the system initializes the charger and establishes WebSocket connections with multiple CMS platforms, maintaining persistent connections.

[0086] Step2: User Selection- The user selects the CMS they wish to interact with for the current charging session. The charger identifies the selected CMS and prepares to send relevant OCPP messages to that platform.

[0087] Step 3: Dynamic Data Processing- The dynamic data processing algorithm processes incoming and outgoing data for the selected CMS in real time, ensuring efficient communication and minimal latency.

[0088] Step 4: Network Management- The network management module ensures that the WebSocket connections remain stable, resources are allocated dynamically, and all active sessions are supported without interruption.

[0089] Step 5: Data Exchange- Real-time data exchange occurs between the charger and the selected CMS, with the charger sending only relevant OCPP messages to the chosen platform.

[0090] Step 6: Completion- Once the charging session is complete, the charger terminates the transaction workflow associated with the selected CMS and clears the corresponding session binding entry. The underlying WebSocket connections to all configured CMS platforms, including the CMS associated with the completed session, remain active.

[0091] Several alternate embodiments of the invention can be implemented to meet different needs and environments as given below:

[0092] 1. Single Network Focused Version: A simplified version where the charger connects to only one CMS at a time, still using persistent WebSocket connections but only activating one connection per session.

[0093] 2. Multi-Focused Network Version: In another embodiment, the charger operates in a fully multi-network active mode wherein multiple CMS connections are concurrently active and capable of initiating charging sessions from any of the connected CMS.

[0094] 3. Load-Balanced Multi-Connection: In this embodiment, the system could support load balancing, where the charger dynamically selects the CMS based on network load, ensuring optimal performance across multiple platforms.

[0095] 4. Cloud-Based Management: The dynamic data processing and network management modules could be hosted in the cloud, allowing for scalable, remote management of chargers and CMS connections.

[0096] 5. Offline Mode: The charger could store data locally when disconnected from the CMS and sync with the CMS platforms once the network is restored, maintaining data integrity.

[0097] The invention could incorporate several advanced technologies such as Al-powered data optimization, cross-platform integration, blockchain technology etc. The system could integrate Al to optimize data processing and network resource allocation based on realtime data and usage patterns. Cross-platform integration could allow seamless interaction with a variety of loT devices, such as home automation systems or fleet management solutions. Incorporating blockchain technology provides an immutable ledger for transaction and usage data, enhancing trust and transparency.Examples

[0098] Example 1: An EV charger installed in a public charging station maintains persistent WebSocket connections to multiple CMS platforms. When a user arrives, they select their preferred CMS through a mobile app, and the charger communicates with that CMS throughout the session, sending relevant OCPP messages. The charger ensures that no data is shared between the CMS platforms, maintaining data privacy and integrity.

[0099] Example 2: A fleet of electric delivery vehicles uses chargers that support multiple CMS platforms. The fleet manager can select the appropriate CMS for each vehicle's charging session through a central management system, while the chargers maintain open WebSocket connections to all CMS platforms. Data remains secure and isolated between platforms, and charging sessions are monitored in real-time.

[0100] The invention offers several key advantages over existing technologies:

[0101] Expanded Network Reach and Charger Visibility: By maintaining simultaneous connectivity with multiple CMS platforms, the EV charger becomes discoverable across multiple independent charging networks. This increases the operational visibility of the charger to a broader pool of EV users registered on different CMS platforms, thereby improving the probability of charger utilization.

[0102] Improved Utilization Efficiency: The ability to interface directly with multiple CMS platforms enables the charger to receive charging session requests from a wider set of user bases without backend interoperability dependencies, thereby increasing effective infrastructure usage.

[0103] Enhanced Operational Revenue Potential: By enabling participation in multiple charging networks concurrently at the device level, the charger supports improved session throughput and optimized infrastructure monetization potential.

[0104] Multi-Network Connectivity: Unlike conventional EV chargers that connect to a single CMS, this invention supports simultaneous connections to multiple CMS platforms, enhancing flexibility and accessibility.

[0105] Persistent WebSocket Connections: The charger maintains continuous WebSocket connections to all CMS platforms, ensuring seamless communication without the need for reconnection during or after each charging session.

[0106] User-Selected CMS: Users can select their preferred CMS for each session, enabling greater control and personalization of the charging experience.

[0107] Data Security and Integrity: The system ensures that no data is shared between CMS platforms, maintaining the security and privacy of user information.

[0108] Reduced Complexity: By eliminating the need for OCPI integration, the invention simplifies the system architecture and reduces implementation costs for service providers.

[0109] Dynamic Data Processing: The dynamic data processing algorithm optimizes realtime communication, ensuring efficient data handling and minimal latency.

[0110] Scalability: The system can easily scale to accommodate more CMS platforms or charging stations without compromising performance.

[0111] Improved Compatibility: The charger can interface with various mobile applications, making it adaptable to different user needs and service providers. This innovation significantly enhances the functionality, efficiency, and security of EV charging infrastructure compared to traditional systems

[0112] While the foregoing written description of the invention enables one of ordinary skill to make and use what is considered presently to be the best mode thereof, those of ordinary skill will understand and appreciate the existence of variations, combinations, and equivalents of the specific embodiment, method, and examples herein. The invention should therefore not be limited by the above-described embodiment, method, and examples, but by all embodiments and methods within the scope of the invention as claimed.

Claims

We Claim:

1. A multi-network electric vehicle (EV) charger comprising:a. a power delivery module configured to deliver electrical energy to an electric vehicle;b. an embedded communication controller;c. a plurality of Open Charge Point Protocol (OCPP) stacks instantiated within the embedded communication controller;d. a multi-WebSocket interface configured to establish and maintain simultaneous persistent WebSocket connections with a plurality of Charging Management Systems (CMS);e. a message routing engine configured to selectively route, replicate, or restrict OCPP messages between the EV charger and one or more CMS platforms; and f. a data isolation module configured to prevent the sharing of session-specific data between CMS platforms,wherein the EV charger natively supports simultaneous communication with multiple CMS platforms.

2. The EV charger as claimed in claim 1 , wherein each CMS connection operates through an independent OCPP state machine implemented within the embedded firmware of the charger.

3. The EV charger as claimed in claim 1, wherein the message routing engine is configured to broadcast non-session-specific messages to multiple CMS platforms while restricting session-specific messages to a selected CMS.

4. The EV charger as claimed in claim 1 , wherein the embedded communication controller includes CMS-specific adaptation logic to accommodate variations in OCPP implementations among different CMS platforms.

5. The EV charger as claimed in claim 1, wherein the charger dynamically allocates processing resources and memory to each active CMS connection based on communication load.

6. The EV charger as claimed in claim 1, wherein the data isolation module enforces cryptographic separation and memory partitioning between CMS sessions.

7. The EV charger as claimed in claim 1 , wherein if one CMS connection fails, the remaining CMS connections continue operating without interruption.

8. The EV charger as claimed in claim 1, wherein the charger allows selection of a CMS platform on a per-charging-session basis.

9. The EV charger as claimed in claim 1 , further comprising a local data buffer configured to temporarily store session data during network disruption and synchronise the stored data with the corresponding CMS upon restoration of connectivity.

10. The EV charger as claimed in claim 1 , wherein one or more CMS connections are each associated with a configured OCPP protocol version, and the charger supports concurrent operation of CMS connections using the same or different OCPP protocol versions.

11. A method for operating a multi-network EV charger comprising:a. establishing, by the charger, multiple concurrent OCPP WebSocket connections with different CMS platforms;b. maintaining independent OCPP protocol states for each CMS connection;c. receiving a charging session initiation request;d. dynamically selecting a target CMS for the charging session;e. routing session-specific OCPP messages exclusively to the selected CMS while maintaining other CMS connections active; andf. enforcing logical data separation between CMS platforms.

Images