MULTI-OPERATOR ELECTRIC VEHICLE CHARGING SYSTEM AND METHOD

Abstract

The invention relates to a multi-operator charging system and method that enables the execution of charging sessions belonging to multiple charging network operators on a single physical electric vehicle charger, separated from each other at the local control unit level. The system operates on a physical charger containing a local control unit, power electronics module, power control unit, energy metering unit, charging socket, user authentication interface hardware, user interface hardware, and communication interface hardware; the local control unit itself houses a multi-CPO management unit, user authentication module, CPO identification module, session routing unit, session ownership management unit, communication management unit, power management unit, data isolation unit, and log management unit. Thus, control commands, power allocations, meter data, and technical logs for sessions belonging to different CPOs are executed on the same physical charger without interference.

Description

MULTI-OPERATOR ELECTRIC VEHICLE CHARGING SYSTEM AND METHOD TECHNICAL FIELD The invention relates to electric vehicle (EV) charging infrastructure, embedded systems architectures, and confined physical environments. Multi-tenant dynamic management of power supply and network virtualization technologies It is related to their fields. More specifically, the invention involves at least one physical electric vehicle charger, with local control. Local Control Unit (LCU), power electronics module, power control unit, energy measuring unit, at least one charging socket, user authentication interface hardware, user a charger that includes interface hardware and communication interface hardware on it, multiple embedded software modules executed by the LCU charging sessions belonging to multiple charging network operators (CPOs) are separated from each other. with a multi-operator electric charging system and method that enables its management It is related. The invention specifically includes: a multi-CPO management unit, a user authentication module, and a CPO. Identity verification module, session routing unit, session ownership management unit, socket allocation unit, power management unit, communication management unit, data Isolation unit, record management unit, multi-license management unit, system monitoring area, hierarchical authorization module, CPO-based external service integration module, embedded user interface management module and management interface module software architecture; one or more remote CPO servers and third parties systems and operations that can communicate with external service systems. It is related to the method. STATE OF THE ART With the increasing popularity of electric vehicles, electric vehicle charging The number of these infrastructures is rapidly increasing. These infrastructures generally consist of charging networks. They are established by Charge Point Operators (CPOs) and is operated. In current practices, each CPO provides services to its own users. In order to provide this, it is creating an independent charging infrastructure; accordingly charger, power electronics, communication infrastructure, energy metering system, local the control unit and backend software systems are independent of each other. They organize it in this way. Therefore, different CPOs operating in the same location, often separate physical systems that perform technically similar tasks. They are forced to establish it. In current systems, each charger will typically be operated by a single CPO. It is designed in this way. In other words, a charger's operating system, communication infrastructure, user authentication mechanisms, energy management The system and energy consumption recording / meter reading processes are all managed by a single CPO. It is configured specifically for its intended use. Therefore, the same physical charge the simultaneous use of the device by multiple independent CPOs an architecture built into the vast majority of known applications that enable this. It is not included. This primarily leads to unnecessary duplication of infrastructure investments. This is the situation. Different CPOs who want to provide services in the same location each have their own... from installing the physical charger, power electronics, power connection, cabling, basic construction works, protective equipment, communication infrastructure and maintenance systems It is created separately for each operator. As a result, the same service In order to achieve this, largely similar physical infrastructures are being duplicated and the total Investment costs are increasing significantly. Another significant technical problem is the inefficiency of network connection capacity. This stems from its use. In the current structures, each CPO is assigned to itself. It can only use the acquired energy capacity for its own users. The CPO's charger would occasionally be completely empty, while the charger in the same location... There may be congestion on another CPO's device. However, the current Energy capacity in architectures is redefined in real-time among operators. Since it cannot be allocated, unused energy capacity remains idle, while... Capacity shortages occur in systems that are used intensively. Thus... The total network connection capacity is not being utilized effectively. 3 Another significant shortcoming of current systems is the lack of multiple operators at the hardware level. Their inability to provide support. The charger control software is limited to a single CPO. Because it was developed to work in conjunction with other operators, different operators can use the same device. The ability to independently manage their own users is a technical issue in existing architectures. It is a powerful tool. Multiple operators sharing the same physical hardware. If operational, user authentication information, charging sessions, and energy measurement. records, pricing information and communication sessions risk becoming intertwined. This is emerging. The main reason for this is that in current control architectures, operators are given hardware-based or an isolation mechanism with access-controlled logical data fields It is the absence of it. OCPP-based communication structures used in existing charging infrastructures are also essential. Communication between a single CPO and a single charger is the primary basis for this. It has been improved. Therefore, the same physical charger can have multiple different OCPPs. a built-in system that enables simultaneous and independent communication with its server The control mechanism is not widely adopted in practical applications. Therefore... External routing is usually required to enable multi-operator usage. Systems or roaming platforms are needed. Roaming systems allow users of different CPOs to use each other's charging networks. while enabling access to the service, these systems do not include a physical charger. It is also operated by a single CPO. The other operators provide technical support on the device. In that sense, it does not mean becoming a CPO, but only user authentication and Payment information is shared through a centralized platform. Therefore, roaming systems allow multiple independent chargers to use the same physical charger. Simultaneous operation by the CPO does not solve the problem. Neutral Host and Network Slicing architectures used in the telecommunications field, multiple operators providing services independently on a single infrastructure This makes it possible. However, these architectures utilize the electromagnetic field of the shared resource. It is based on the assumption that there is spectrum and data capacity, and operator 4 It performs the separation at the network layer. Physical electrical power When shared, energy is a measurable and limited physical resource. Because of this, the operator distinction is not only at the network layer but also at the hardware and energy level. It is also mandatory to implement this at the management level. Furthermore, it applies to every business owner. Independent measurement and reporting of energy consumption, existing Neutral Host This constitutes a technical requirement that is not reflected in their architecture. Therefore... Current Neutral Host and Network Slicing architectures utilize a very large physical power source. It cannot be directly applied to business management. In addition, in current systems, charging sessions are hardware-based on an operator basis. There is no mechanism that ensures isolation at this level. A charge When a session is initiated, user information and energy measurement data related to that session are displayed. Authorization records and control commands can only be used by the relevant operator. a built-in session ownership mechanism that guarantees its management Since it is not available, data will be needed when switching to multi-operator operation. preserving integrity and ensuring secure separation between operators This presents significant technical difficulties. From an energy management perspective, existing systems also have limited capabilities. The total power capacity allocated to the charger is logically determined among the operators. It cannot be divided as such, and the unused capacity is instantly transferred to other parts. Dynamic resource management that enables transfer to operators This is not possible. As a result, the use of energy infrastructure is limited. efficiency is decreasing, a significant portion of network connection capacity is being used over time. Time is being wasted. In addition, if different operators can use the same physical device, each operator's energy consumption records, CPO identity / authorization profile, technical operation records and reports required to be kept under legislation They need to be created independently of each other. However, the only one currently exists. Operator-based architectures do not have the technical infrastructure to meet this need, Independent record generation and reporting on an operator-by-operator basis is not possible. Consequently, the charging infrastructures currently in use operate on a single operator basis. They are designed to allow multiple independent CPOs on the same physical device. their failure to allow it to operate locally, hardware between operators Their inability to provide source isolation at this level reduces energy capacity dynamically. Their inability to share data as a session will ensure multi-operator data security. They do not have processing area isolation and operator-independent licensing. High investment costs due to their lack of support for reporting processes, low infrastructure usage efficiency, unnecessary infrastructure duplication, and limited This leads to significant technical problems such as scalability. For these reasons... a new system and method that will enable the resolution of these problems It is needed. With current technology, each CPO independently develops its own hardware and infrastructure. They have to establish it. This situation leads to low capacity utilization rates and high infrastructure. This leads to waste (CAPEX) and inefficient use of grid power. (Source: Energy Market Regulatory Authority (EPDK), sector report dated April 2026) The data shows the average capacity of charging infrastructure across the country during the relevant period. (The usage rate has been reported as approximately 2.6%). Multiple operators currently available. Their solutions are generally cloud-based "roaming" systems. These systems rely on operator differentiation not at the device (hardware) level, It is performed on central servers. In current charging infrastructures, different charging services are provided on the same physical device. technically guarantees the isolation of operator data from the system operator. There is also no established mechanism in place. The party operating the infrastructure, the device user data and session content belonging to operators operating on the platform or blocks access to transaction logs at the hardware level and only limiting the system health parameters through measuring the total energy consumption of the device. A technical decomposition layer is not present in the current systems. This situation, Data privacy and security requirements in multi-enterprise infrastructures. It remains technically unsolvable. 6 In conclusion, due to the drawbacks described above and the current usage Due to its shortcomings, it has become necessary to make improvements in the relevant technical field. For these reasons, physical energy will be needed to solve these problems. a system capable of managing resources in a multi-tenant manner, and managing CPO and user data. existing Neutral Host architectures that isolate from the operator at the hardware level as well. implementing and operator-independent integrity to the physical energy infrastructure. A new system and method is needed that can produce preserved energy measurement records. It is heard. DEFINITION OF INVENTION The invention involves multiple CPO (Customer Power Supply) devices on a single physical electric vehicle charger. in an isolated manner and without the need for any external roaming platform many that allow them to operate locally simultaneously without being notified It relates to the tenant charging system and method. The main purpose of the invention is to enable multiple operators to have separate infrastructures in the same location. high investment costs resulting from its establishment (Capital Expedition - The aim is to prevent waste of grid power (CAPEX). The system utilizes limited grid power. dynamic according to Service Level Agreements (SLAs) between operators inability to share, inability to isolate operator data at the hardware level and integrity-preserved energy measurement of a single device under different licensed CPOs. It provides solutions to technical problems such as the inability to report the record. The invention enables multiple CPOs (Customer Points) in electric vehicle charging infrastructures using the same physical charger. multi-operator system that allows them to provide services independently of each other. The invention relates to an electric vehicle charging system and method. More specifically, the invention; The physical charger sources are logically controlled by the local control unit. separation, creation of isolated work areas for each operator, charging Dynamically routing sessions to the relevant operator, energy capacity distribution among operators according to priority rules and each operator's own integrated system that enables the independent creation of technical records It encompasses a system architecture. 7 The system described in the invention consists of three main component groups: 1. The hardware components that make up a physical electric vehicle charger, 2. Embedded software modules running on the local control unit and 3. External / non-device components that exchange data with the system. Hardware components include: physical charger housing, local control unit, embedded processor, processing memory, permanent data storage unit, power electronics module, power control unit, energy measurement unit, charging socket, charging socket connector lock mechanism, vehicle control pilot signal detection circuit, user verification interface hardware, user interface hardware, and communication interface It includes the hardware. The local control unit also features multiple CPO management. unit, user authentication module, CPO identity verification module, session routing unit, session ownership management unit, socket allocation unit, power management unit, communication management unit, data isolation unit, records management unit, Multiple license management unit, system monitoring area, hierarchical authorization module, CPO-based external service integration module, user interface management module, and The management interface module is operational. The system also supports one or more remote access points. The CPO server will be able to communicate with third-party external service systems. It can be configured. The charger included in the invention differs from traditional systems in that it has specific characteristics. It does not operate in a way that is specific to a CPO; it runs on the same physical hardware. enabling multiple CPOs to operate simultaneously It has a built-in multi-operator architecture. For this, local control is required. Communication information and authorization details for each CPO within the unit. parameters, user management, pricing information, and business rules They are stored in independent logical spaces, and each operator has its own The system can operate as if it were being used by a single individual. This allows different CPOs to... This prevents the data, commands, and processing operations from interfering with each other. The technical contribution of the invention is not the commercial sharing of charging services; it is a single... The charging socket found within a physical electric vehicle charger is related to power electronics and energy. physical and embedded systems such as measurement units, communication interfaces, and processing memory 8 their sources associated with the CPO identity by the local control unit It is the separation into independent study contexts. The invention includes determining CPO, creating session ownership records, and socket allocation (Socket Allocation and power set value calculation processes are performed externally via roaming or centrally located. on the local control unit before being sent to the coordination platform This is done. Therefore, there may be a delay or in a central system belonging to a CPO. Communication disruption occurs, active charging in other CPO work contexts. their sessions include socket allocation, power set value update, and meter registration processes. It does not stop. A separate message queue and communication link profile for each CPO. Because it is being held, a CPO server's timeout does not affect messages belonging to other CPOs. It does not block processing. This structure reduces local decision-making time and error. It limits its spread. The invention also combines known multi-tenant software + known load balancing + This isn't just a typical OCPP combination; it involves physical power inside the charger, the socket, The counter, the OCPP instruction, and memory access are all managed through the same session ownership register. It is locked into an embedded control architecture. One of the key technical features of the invention is the logical arrangement of physical resources. It is the separation of components. This includes charging sockets, power capacity, and communication. connections, user sessions, and processing resources are directly linked to physical hardware. not as individual connected resources, but as virtual resources managed by a local control unit. They are considered as resources. The local control unit distributes these resources differently. allocating according to the rules defined between operators and when necessary It restructures them. Thus, they are different from each other on the same physical hardware. Multiple independent business environments are being created. One of the most important technical advantages offered by this approach is that the physical hardware The advantage is that it can be used much more efficiently. In current systems, each CPO has its own charging system. Because he has to set up his device, there are numerous similar infrastructures in the same location. It is being established. Thanks to the invention, a single physical charger can be used by multiple operators. It can be used jointly by all. As a result, power electronics, 9 power connection, cabling, communication infrastructure, control equipment and field There is no need to reinstall the equipment; the same infrastructure is used for numerous projects. It can be used jointly by the operator. Thus, physical infrastructure investments While significantly reduced, the efficiency of using existing infrastructure is also increased. Another important technical effect of the invention is the dynamic increase in energy capacity. It is manageable. The local control unit measures the total energy supplied from the grid. Instead of allocating capacity to specific sockets in a fixed manner, active operators It allocates energy into logical energy slices according to their needs. For each operator. defined service levels (SLAs), instantaneous user load, available power Energy distribution in real time, taking into account capacity and system priorities. It is being reorganized as follows: Unused energy capacity to another... thanks to the fact that it can be transferred to the operator, much of the total network connection capacity Higher efficiency is achieved and energy infrastructure remains idle. This prevents capacity from being wasted during periods of high demand. By ensuring controlled management, it increases system stability. Another technical advantage of the invention is that it provides complete isolation between operators. It is the working architecture. Independent operation for each operator within the local control unit. Fields are being created; user authentication information, charging sessions, meter data, Energy records and communication sessions are only logical and belong to the respective operator. It is processed in the work area. Thus, in the software of any operator. Any errors, delays, or communication interruptions that may occur are the responsibility of other operators. It does not affect the work processes. This structure only enhances data security. not only does it not remain, but it also significantly improves system reliability and operational continuity. It increases it to a certain extent. Another key technical contribution of the invention is that it is exclusive to the system operator. hardware or access from allocated and CPO-owned workspaces It is an isolated system management area, isolated by controlled logical data spaces. The field only measures the total energy consumption of the device and its instantaneous power capacity status. They have access to hardware health parameters and system fault logs. Operators have access to user ID data, charging session content, and pricing information. Technically, no access to information and transaction records is possible from this area. No; the restriction in question is related to operator session ownership of the OCPP protocol. mechanisms and hardware in the local control unit's process memory or memory allocation provided by access-controlled logical data fields It is secured through the layer. Within the scope of this invention, the management of charging sessions also differs from traditional systems. This is done using the user's RFID card, mobile application, Plug & Play. including accessing the system via Charge or similar authentication methods Transactions will be handled through interfaces dedicated to the CPO and the relevant charging session will be processed. It will be initiated directly on that operator's system. Including session initiation. All commands, energy measurements, and transaction logs relating to the session are only accessible to the relevant parties. It can be managed by the operator. As a result, data integrity is ensured. While being protected, the reliability of user transactions is also increased. The invention also allows for the dynamic management of how charging sockets are used. This allows the local control unit to assign each charging socket to a specific operator. It can allocate the same socket continuously, or multiple sockets can be used if needed. It can be made available for the operator's use. Usage intensity, time schedule, priority. operating mode of sockets taking into account rules or operating policies They can be automatically switched. Thus, from existing physical sockets Maximizing benefits while responding faster to user requests. It can be provided. The invention also includes the user interface of the charger, to which the active charging session is connected. dynamic at session start according to the operator's visual identity parameters. it configures and at the end of the session the previous configuration remains as a remnant It includes a user interface management module that cleans up without interruption. Within the scope of the invention, the approval of the main licensee operator and the system operator is required. through its mechanism specific charging sockets or defined time periods It can delegate software-based operations to sub-operators (sub-CPOs); sub-operator operation 11 as an isolated logical space independent of the main operator's workspace It also includes the hierarchical sub-operator authorization module that was created. The invention also triggers charging session initiation and completion events. using these signals in an isolated manner specific to the relevant operator's area of ​​operation. transmitting to third-party service providers via the integration channel and External data packets / third-party service data directed to the user are only relevant to the user. CPO-based external service integration that enables delivery through the operator's channel. It includes the module. One of the invention's significant technical contributions is its compliance with regulatory requirements. It supports an operator-based record structure. The local control unit, for each CPO. independent energy consumption records, CPO identity / authorization profiles, transaction It creates records and reporting data. Thus, on the same physical device When multiple CPOs are operating, the technical records for each operator are different from each other. can be created independently and required under the relevant legislation. Reporting can be done separately. This structure is suitable for multi-operator businesses. a key component that makes it technically feasible It constitutes. Another technical advantage offered by the invention is scalability. Local control. Adding a new CPO to the system thanks to the unit's logical resource management No additional physical charger needs to be installed. New The operator is logically defined within the existing system and is required. The service is available on the same physical device once authorization information is uploaded. It can start providing. Thus, the system can add new operators. In this case, it can grow without requiring additional hardware investment and infrastructure. Expansion costs are significantly reduced. In conclusion, the invention logically integrates physical charger sources. virtualization, ensuring secure resource isolation on a CPO basis, energy Dynamic management of capacity, charging sessions based on CPO. routing, ensuring multi-operator data security and 12 on a CPO basis Thanks to the creation of independent records, the infrastructure encountered in the current technology... repetitions, low capacity utilization, resource waste, data clutter, and single It offers an integrated technical solution that eliminates CPO dependency. This In this way, both the physical infrastructure is used more efficiently and the same hardware a secure, scalable and high-performance multi-operator charging system The infrastructure is being implemented. DETAILED EXPLANATION OF THE INVENTION The invention relates to the physical electrical power infrastructure, divided into logical segments on a CPO basis. a multilayered embedded system architecture that adapts the decoupling architecture It offers multi-tenant resource management in network virtualization technologies. The fundamental difference from these principles is that the shared resource is measurable, not its data capacity. It is physical electrical power; this situation makes CPO differentiation not only at the network layer but also This also makes it necessary to implement it at the hardware and energy management level. The system's hardware-level isolation is achieved through the "Operator Sandbox Architecture". This architecture provides each operator with their own user data, commands, and Counter information is stored hardware-wise in the processor's temporary memory (RAM) or via access. processing data in isolated fields separated by controlled logical data fields It maximizes security. User identity (RFID, Application or When Plug&Charge is offered, the Dynamic Session Routing Engine (Dynamic The Session Router processes this data in the local database and assigns the session to the relevant operator. OCPP connects to the backend system in real-time. The sockets are specific to a particular system. "Exclusive" mode or usage permanently assigned to the operator They can change the CPO according to the intensity in "shared" mode. It can switch autonomously. Additionally, it has a multi-license management unit. Thanks to this, a separate license ID and energy meter record is generated for each socket, thus different Legal reporting can be done in the name of CPO / operator profiles. The data isolation unit is a memory protection unit connected to the processor of the local control unit. memory management unit, address range access table, separate task / thread contexts or memory access provided by the real-time operating system 13 Separate process memory for each CPO through at least one of the control mechanisms. It defines the region. Each CPO's work context includes user authentication tokens and ad-hoc communication. buffers, OCPP message queues, session status, counter intermediate values, and temporary Memory space is allocated for control commands when a CPO context is active. The processor only provides read / write access to the relevant CPO memory area. Others Memory areas belonging to CPOs are inaccessible in this context. Common temporary buffers are cleared during context switching, returning to the previous CPO. Temporary data belonging to this group is not transferred to the next CPO context. Unauthorized memory access. When this attempt is detected, the relevant process is stopped and an error log is created. In traditional electric vehicle charging systems, each physical charger can only be used by one person. It is configured to be operated by the CPO. Therefore, the device internal processing resources, communication infrastructure, energy management mechanisms, user authentication system and control software to a single operator. It is designed to provide the same service. The invention, however, changes this approach by... multiple independent logical operating areas within a physical device It thus constitutes a single device, although technically unique. A virtual charging infrastructure is being created that operates independently for each CPO. For this purpose, the system is placed between physical resources and operator services. It includes a virtualization and resource management layer. This layer, Instead of allocating physical hardware resources directly to a single operator transforming these into logical resources and in accordance with the established rules It assigns them to the relevant operators. Thus, the same physical processor, the same power electronics, The same communication infrastructure and the same charging sockets are provided by different operators. They can be used without affecting each other. This architecture allows operators to share physical infrastructure even though it is commonly used. The work environments are completely separated. In other words, the operators sharing only the hardware; user information, pricing policies, 14 Authorization processes, energy records, communication sessions, and transaction data. They are managed completely independently of each other. The first technical impact of this approach is the shared use of physical resources. However, the key is to maintain functional independence. This is common in existing systems. Data interference, communication conflicts, and command issues can occur if hardware is used. Conflicts and session errors can occur. In the invention, however, for each CPO... These problems arise because separate logical working areas are created. It is not coming out. Another technical effect is the more efficient use of processor resources. Similarly... processor and the same local control unit, multiple CPOs instead of just a single CPO Since the operator can perform the operations, the hardware capacity is more efficient. is used. Thus, an additional control card, an additional communication module or additional System capacity can be increased without the need to use a processor. The invention involves the following hardware components mounted on a local control unit: It includes working embedded software modules and external components. As hardware components: at least one physical electric vehicle charger; at least one at least an embedded processor, processing memory (RAM), and persistent data storage unit. a local control unit (LCU); power electronics module; power control unit; energy measuring unit (meter); at least one charging socket; to the relevant charging socket at least one connector locking mechanism; vehicle connection signal (Control Pilot) at least one circuit that detects; at least one user authentication interface hardware (RFID) reader, QR / square code reader, mobile application connection interface and / or Plug & Play Charge hardware; user interface hardware (screen, touch panel, indicator); and at least one communication interface hardware (Ethernet, cellular modem, (wireless network module). As embedded software modules running on the local control unit: multiple CPOs Management unit (native multi-tenancy architecture); User authentication module; CPO identity verification module; session redirection 15 unit (Dynamic Session Router); session ownership management unit (Session Ownership Manager; Socket Allocation Unit; Power Management Unit (virtual power slicing and prioritization functions) Executing unit); Communication management unit (OCPP communication module); Data isolation unit (hardware-based or access-controlled logical data fields with CPO) Isolation layer separating working contexts – Operator Sandbox Architecture); Registration management unit; multi-license management unit; system monitoring area; hierarchical Authorization module (sub-CPO support); CPO-based external service integration. module; user interface management module; and management interface module. External / External components include: one or more remote CPO servers (OCPP) (backend systems) and third-party external service systems. These components by constantly exchanging data with each other, the system works in a coordinated manner. provides. The system monitoring area displays the CPO's operation in the local control unit's process memory. from fields either as hardware-based or access-controlled logical data fields an isolated memory separated and exclusively allocated to the system operator This area only displays the total amount of energy the device has consumed up to that point. Current power capacity status, hardware failure logs, and system health. Parameters are being processed. User credentials belonging to operators, charging session Commands, energy consumption records, and transaction data are technically located in this area. inaccessible; the access restriction in question is due to the OCPP protocol's CPO session ownership. mechanism and memory allocation layer at the hardware level It is implemented. The system monitoring area involves monitoring the overall status of the device, Identifying technical malfunctions and aggregated data for the device, regardless of CPO (Computer-Positioned Power) distinction. It is possible to obtain a measurement of the total energy consumption calculated as follows. while structurally safeguarding CPO and user privacy. The user interface management module is the user interface located on the charger. screen display, touch panel output, indicator by controlling the hardware status or similar user-facing visual / auditory outputs active charging It is configured according to the CPO to whom the session is assigned, and the charger screen presentation, mobile application interface or web-based interface session 16 in the operator's identity management area as determined by the routing unit defined visual parameters — brand name, logotype, color palette, language preference and Pricing display format — dynamically based on session startup time. It configures the interface for each session according to the respective operator. It is kept as an isolated contextual object tied to the workspace; session Once completed, this configuration is cleaned up without leaving any residue, and the device It is being made neutral for the next user. The hierarchical sub-operator authorization module allows the main licensee operator to... one or more of the charging sockets allocated to it or defined time zones, subordinate through the system operator's approval mechanism It allows for the software-based transfer of ownership to operators. Sub-operator for the main operator workspace in the local control unit memory and the system An isolated sub-workspace is created, independent of the monitoring area. Sub User identification data, energy consumption records, and transaction data belonging to the operator are the main It is kept separate from the operator's records. The sub-operating area authorization period has expired. In the event of termination or cancellation, all configuration and sessions in that area will be affected. data is processed by the system without being made accessible to the main operator. is being terminated. The operator-based third-party integration module is handled by the session management unit. triggers the generated charging session start, resume and completion events. It receives these signals as isolated signals specific to the operator's field of operation. It is transmitted to third-party service providers via an integration channel; External data packets / third-party service data directed to the user are only relevant to the user. from the operator's integration channel and the relevant operator's user interface It is presented within this context. Content from an operator's integration channel. another operator accessing a user session or system monitoring area It is technically blocked. The integration channel will be completed when the session is finished. is being shut down and the content data processed through this channel is being transferred outside the relevant work area. It is cleaned without leaving any residue. 17 When attempting to initiate a charging session, user authentication data is first required from the user. The verification interface is received by the hardware; then the user This is processed by the verification module. User verification module The verification data processed by the system is transferred to the CPO identity verification module; the module in question from the validation data, validation channel, connection By identifying the CPO ID from their profile or local peering record, you can identify the relevant CPO. It activates the working context. Then session redirection. The unit will create the charging session within the defined CPO work context. It directs. The socket allocation unit then examines the available physical charging sockets and determines the appropriate one. It determines which socket the session will be conducted through. If the socket... In "dedicated" mode, only the designated CPO can be used. If the socket is in "shared" mode, only the relevant connection can be accessed during the session. It is assigned to the operator. Once the charging process begins, the Virtual Power Slicing Engine will activate, reducing the total... It divides the grid capacity into logical energy slices. These energy slices, operators' service level agreements (SLAs), current load status, instantaneous power. It is allocated dynamically, taking into account needs and system priorities. Thus, unused capacity can be used by other operators. the utilization rate of the total connection capacity can be evaluated. It is being upgraded. During the charging period, the Session Ownership Manager This ensures that the active session can only be managed by the relevant CPO. Same The data isolation unit, in the process memory, provides isolated workspaces allocated to each operator. protecting their areas; data packets, control commands and transaction logs This prevents other operators from encroaching on their areas. In this way, any a software error, communication delay or system failure on the operator's side This malfunction does not affect the charging operations of other operators. This structure is in the system. providing fault containment and deterministic operational continuity. It is a significant technical effect. 18 Once the charging process is complete, the data management unit activates and monitors energy consumption. counter information, session logs, CPO ID / authorization profiles, and others. It creates separate technical records for each relevant CPO. Thus, the same physical technical records are created. Despite the use of devices, each CPO operates independently, as if running their own infrastructure. It obtains technical records. In conclusion, the system architecture separates the physical hardware from the CPO services. Thanks to the virtualization layers that separate them, a single charger can be used by multiple devices simultaneously. secure, isolated, dynamic and highly efficient by multiple independent CPOs This makes it possible to operate the equipment. Thus, both hardware resources... This increases the efficiency of use and also addresses the issues that arise in traditional single-operator architectures. The resulting infrastructure duplications, idle capacity, data clutter, and management challenges are technical. It is being eliminated as such. The invention includes multiple CPO management units within the same physical electric vehicle. the charger is independently controlled by multiple CPOs It is the fundamental control component that enables its use. This unit is the physical hardware. by preventing resources from being allocated to a single operator, for each CPO It creates logically separated, independent work environments. Thus Although the system physically consists of a single device, in terms of each CPO It functions like a standalone charger under its own control. The built-in multiple CPO management unit is run by the local control unit. as a management layer running within embedded software This is implemented by the unit in question, which includes a processor, memory, and persistent data storage. It operates in constant data exchange with the unit. Each operator has its own data stored in memory. configuration information, credentials, communication parameters, security certificates, authorization rules, pricing information, license definitions, available charging sockets, priority levels, and service parameters They are stored as independent datasets. These datasets share a common thread. Although they are located within the database, each dataset only contains the relevant 19 Since it is associated with the operator's logical identity, other operators' Access to the data is technically blocked. The built-in multiple CPO management unit is primarily registered during system startup. all configuration information belonging to the operators is stored in the permanent data storage unit. It reads the information and transfers it to working memory. Then, a separate one is created for each CPO. It creates a working context. The working context is the system of the relevant operator. all the technical resources and communication sessions that it can use within it, It is a logical operating environment containing safety information and control parameters. This allows multiple independent processes to run simultaneously on the same processor. The context is being created. Thanks to this approach, any business owner The operational data of other operators is not affected while these processes are being carried out. When a charging session is initiated, authentication is managed by the CPO. Verification data from the channel reaches the local control unit. Built-in Multiple CPO management units analyze the CPO ID within this data to identify the relevant It defines the working context of the business. All subsequent processes... This is carried out solely within the context of this study; user information, session Data and control commands are exclusively transmitted to the relevant CPO's OCPP server. The process takes place within the CPO's isolated workspace. This allows different tasks to be performed simultaneously. Even if users belong to different CPOs, each user has control over their own CPO. It operates within the realm of logical reasoning. The built-in multi-CPO management unit is only activated during the user verification phase. not only, but also actively involved in all technical processes performed during the charging process. It is involved in the process. Energy measurement records created during the charging process are recorded by the meter. information, error logs, status messages, remote control commands, and charging session The information is first evaluated by this unit. Then the relevant The data is routed to the logical operational domain of the operator to which it belongs. Thus, energy consumption data or transaction information belonging to any operator can be obtained. The process of writing records into another operator's records is prevented. The built-in multiple CPO management unit handles various decision-making processes. It utilizes control algorithms. The main purpose of these algorithms is... Identifying which operator each incoming request belongs to the system and the relevant The goal is to direct the request to the correct working context. To do this, first of all, the message... the connection profile, session ID, socket ID, message queue or local received The CPO ID is read from the CPO tag, then the CPO found in memory is retrieved. The records are compared with the relevant operator's records. When a match is found, the relevant operator's records are used. The working context is selected and the process is carried out within that context. If If the CPO information for the incoming request cannot be found or the authorization cannot be verified The request is rejected, and an error message is entered into the system security logs. Thus, unauthorized access attempts can use system resources. is being prevented. One of the significant technical impacts provided by the built-in multiple CPO management unit is the CPO The goal is to provide complete source insulation at the level of the existing technology, with the same physical properties. If the device is attempted to be used by different operators, the processor memory, communication buffers, or data storage areas are commonly used. Because data is used in this way, data interference can occur. In the invention, however, each CPO Since a separate working context is created for each, the processor is not on the same physical hardware. Despite this, logically independent systems are created. This prevents data confusion, and each CPO only handles their own processes. This allows us to see the problem, and system reliability is significantly increased. Another technical benefit provided by the built-in multiple CPO management unit is, It provides scalability. An additional charge is applied when a new CPO is added to the system. The device does not need to be installed. Instead, it belongs to the new operator. Configuration information is being recorded in the database and multiple CPO management units A new working context is being created for this CPO. Thus The system will switch to the new operator without any physical hardware changes. This is becoming a supportive mechanism. As a result, both investment costs are decreasing. Moreover, the utilization rate of the existing infrastructure is increasing significantly. 21 The integrated multi-CPO management unit is also in constant communication with all other control units. They communicate, particularly regarding session information coming from the session routing unit. It receives information from the power management unit about which operator is requesting energy. reporting active session status from the session ownership management unit learning and working with the data isolation unit on each operator's process It ensures the protection of these areas. Thus, all controls within the system The mechanisms are operated simultaneously under a single management logic. In conclusion, multiple CPO management units can be used on the same physical charger. By creating independent, logical workspaces, each operator can have their own all the technical aspects belonging to the operators that enable it to function as if it were using their own infrastructure separating data, dynamically managing system resources, and others Coordination between control units and multi-operator operation. It is the fundamental technical component that makes its architecture possible. The system described in the invention is a single physical electric vehicle charger that can accommodate multiple CPOs (Call to Point of Purchase). an integrated system that allows them to be used independently by each other It consists of a control architecture. The system comprises physical hardware components and their components. It is based on the principle of the embedded control software managing the system working together. In this context, the system basically consists of; a local control unit and multiple CPO management units. (built-in multi-tenant architecture), user authentication module, CPO identity verification. module, session routing unit, session ownership management unit, socket allocation unit, power management unit (virtual power slicing and prioritization functions) (implementing unit), data isolation unit, records management unit, multi-license management unit, communication management unit, system monitoring area, hierarchical authorization module, CPO-based external service integration module, user interface management module, and It consists of a management interface module. The system's hardware components... These also include a power electronics module, a power control unit, and an energy measurement unit. (meter), charging sockets, user authentication interface hardware, user interface It includes hardware and communication interface hardware. 22 The entire operation of the system is managed by the local control unit. Local a system using a control unit, processor, memory and data storage unit It ensures the coordination of all the components within it. User Authentication processes performed by [the company / individual], use of charging sockets status, energy consumption information, CPO records, communication messages, and active charging. Information regarding their sessions is continuously monitored by the local control unit. It is being monitored. The local control unit evaluates this information and determines which determining which physical resource the operator will use and the relevant control It sends commands to other units of the system. Thus, within the system... Since all decisions are managed from a single center, timing differences between different units are not affected. This prevents incompatibilities from occurring and ensures the system operates stably. Multiple CPO management units, operating under the local control unit, are integrated into the system. It manages the technical information for all registered CPOs. Each Operator identification information, contact addresses, security information, CPO ID / authorization profiles, pricing rules, authorization parameters, and Service settings are stored in independent data areas in memory. When a new CPO is defined in the system, the information belonging to this operator is included in the existing data. It is added to a new record area independent of its structure. Thus, the same physical operators operating on the device accessing each other's data This is being prevented, and each CPO is acting independently as if they are using their own system. It can operate. Thanks to this structure, data security is increased while operators This also prevents data confusion from occurring between them. User information is required if a user wishes to initiate the charging process. The dynamic session is transferred to the session redirection unit. This unit, the user Based on the verification information, we can determine which CPO the user is registered with. It determines this. The determined CPO information is located in a multi-CPO management unit. The records are compared and the working environment of the relevant operator is activated. is brought in. Then all control commands relating to the charging session are only given. It is redirected to the relevant operator's processing area. Thus, different operators can operate simultaneously. Even if users belonging to the operators receive services from the same physical device, each user It operates solely under the control of its own operator. This is 23 As a result, user operations are carried out completely independently of each other. This prevents transaction records belonging to different operators from getting mixed up. Session ownership after the dynamic session redirection process is complete The management unit is activated. This unit, for each charging session initiated... creating a unique session log and sharing this session with the relevant CPO It correlates them. As long as the charging process continues, energy measurement data is transmitted remotely. The control commands sent initiate, stop, or stop charging. All operations, such as termination, are based solely on the record of this session. This is carried out. Thus, an active charging session is managed by another CPO. checking or performing simultaneous actions within the same session This is being prevented. This structure, in particular, aims to protect data integrity and ensure reliability. This creates a significant technical impact in terms of providing session management. The socket allocation unit determines which CPO will use the physical charging sockets. It determines this. Every charging socket in the system is constantly monitored and The socket's status (empty, in use, or standby) is determined. New When a charging request comes in, available sockets are evaluated and the relevant one is used. It is allocated to the operator. When the charging process is complete, the socket is shared again. It is being added to the usage pool and made ready for use by another operator. This ensures that physical sockets are permanently tied to a specific operator. not remaining, but operated by different operators depending on the need. This allows for more than one source from the same physical hardware. This ensures usability and reduces the need to install an additional charger. The virtual power slicing engine determines the total electrical power drawn from the grid within the system. It ensures dynamic distribution among the active charging processes available. This unit displays instantaneous power information received from the energy metering unit to the active user. numbers, priority information for operators, and charging requests all together. By evaluating the situation, it calculates the amount of power to be allocated to each operator. The calculated power values ​​are transmitted to the power control unit and then to the corresponding charging socket. is applied. One of the charging processes ends or a new charging process begins. The power distribution is recalculated when the process begins. Thus, 24 Unused power capacity is immediately made available to other active users. This structure allows for a more efficient use of the existing network connection capacity. is being used, unnecessary capacity allocations are prevented, and from the same infrastructure More users can be served. The amount of power to be allocated to each operator will be determined using the following parameters: The following are calculated: total available grid power, number of active charging sessions, and Instantaneous power demand of each session, maximum current capacity of sockets, CPO priority coefficient and SLA weight, safety limits defined in the system. A new session. Calculations are made when the session starts, ends, or when the instantaneous power demand changes. The values ​​are updated and transmitted to the power control unit. Low SLA power slice allocated to the weighted operator, high SLA weighted operator It can be redistributed instantly to meet demand. Each power set value calculated by the power management unit is directly transmitted to a Not the CPO itself, but the CPO ID that is jointly identified in the session ownership record, the session The ID and socket ID are assigned to the trio. The power control unit receives the set transmitted to it. before applying its value, check the target socket's current active session ownership record. Compares the CPO and session information in the set value. If no match is found... The power set value is not applied and an error log is created. Thus, it belongs to an operator. Applying the power allocation decision to another operator's socket is technically It is blocked. The energy metering unit displays the meter's initial value when the charging session begins, charging The interim measurement values ​​are displayed throughout the session, and the counter ends when the session is terminated. It transmits the value to the local control unit. The local control unit transmits these values ​​to the relevant session. The ownership record includes the CPO ID, session ID, and socket ID along with the time. It records it with a stamp. The records management unit records the energy consumed at the end of the session. The amount is calculated as the difference between the meter's final value and its starting value. The calculations and results are only entered into the technical log area within the relevant CPO work context. The author writes: Thus, even if the same physical energy measurement infrastructure is used, each consumption It is not technically guaranteed which CPO and which charging session the recording belongs to. is done. 25 The isolated processing area is independent for each CPO operating within the system. It creates a working environment. In this working environment, the user belonging to the operator information, charging sessions, power logs, error logs, and communication data. It is stored in a way that is accessible only to the relevant operator. The processor is the same. Although it operates on physical hardware, thanks to memory management, it can be used in every way. The data space used by the operator is separated from each other. Thus, any a software error on the operator's part or an unexpected data change, other This prevents the system from affecting the operations of businesses. As a result, the system... reliability is increased and multiple operators can work seamlessly on the same device. This ensures that the service is provided in this way. Communication management unit, local control unit and central management belonging to the operators. It manages all data communication between the systems. User authentication. requests, charging start and stop commands, energy consumption information, error Records and status information are transmitted to the relevant operator through this unit. The communications management unit identifies which operator each incoming message belongs to. It identifies and directs the message only to the relevant operator's processing area. Thus, although the same physical communication infrastructure is used, it belongs to the operators. Data streams are separated from each other. The communication management unit sends each OCPP message to the relevant operator's defined connection. It associates it with the profile — CPO ID, session ID, and socket ID. Outgoing messages are routed only to the relevant operator's OCPP server; In the incoming commands, the CPO and session ID to which the message belongs are verified. Commands that fail to validate or do not match the corresponding session ID. It is rejected and recorded in the system security logs. Thus, the same physical OCPP traffic from different operators can be separated from each other via the communication interface. They are technically separated. The multi-licensing management unit ensures that each operator's legal obligations are handled independently. This enables it to fulfill its function. After the charging process is complete... energy consumption data, transaction logs, user information, and necessary technical records They are created separately for the respective CPO. Thus, 26 can be created from the same physical device. Although services are provided, each CPO operates under their own license. It is able to obtain independent records that appear to show otherwise. This situation is both technical. ensuring the accuracy of records as well as commercial and other businesses belonging to different operators. It allows operational information to be separated from each other. As a result, these technical elements that make up the system constantly exchange data with each other. working within it involves the shared use of physical resources, and transactions belonging to the operators. the independent execution of processes, and the dynamic increase in energy capacity managing and ensuring charging operations are carried out safely. This provides a separate physical charging infrastructure for each CPO in the current technology. The structure requiring its installation is eliminated, on the same physical charger. where multiple operators can provide services in a safe, independent and efficient manner A new system architecture is being implemented. The invention describes a multi-operator electric vehicle charging system consisting of a single physical charger. allowing multiple CPOs to serve independently. In order to provide this, follow the steps described below: He is working. In the first step, the local control unit performs the system startup process. At this stage, the local control unit accesses the CPO recorded in the data storage unit. information, system configuration parameters, security information, license records, descriptions of charging sockets and energy management parameters It loads into memory. It also has multiple CPO management units for each CPO. Independent logical working areas are created by this. Thus, the system is ready for multi-operator operation even before a user request arrives. is being transformed into this state. In the second process step, the RFID card is used via the user authentication interface hardware. Verification data via mobile application, QR code or Plug & Charge method. This is collected. The user authentication module processes this authentication data and converts it to CPO. It is being sent to the identity verification module. 27 In the third step, the CPO identity verification module uses the verification data, CPO from authentication channel, connection profile, or local peering record It identifies the individual and activates the relevant CPO work context. In the fourth step of the process, the session redirection unit activates the CPO operation. Depending on the context, the charging session will be created and assigned to the correct operator. It redirects. At this stage, the system redirects to the operator the user is connected to. communication information, authorization rules and service parameters by ensuring the charging session is managed only by the relevant CPO This allows you to have devices from different operators on the same physical device. Even if there are users, each user is within the scope of their own operator's service. It is being processed. In an additional step following the fourth process step ('process step 4A'), the CPO works immediately after the context is enabled and before socket allocation is performed, User interface management module, visual representation of the CPO to which the active session is connected. by uploading identity, brand information and authorized third-party service content It configures the user interface based on the ID of the relevant CPO. In the fifth step of the process, the socket allocation unit uses the physical charging sockets. It is examining its condition. The charging socket is found to be in usable condition. It is determined and allocated to the relevant charging session. If predetermined If there are terms of use, these rules are taken into consideration; otherwise, the appropriate course of action is taken. Any available charging socket can be assigned to the user. Thus, the physical Sockets are used as shared resources without being permanently tied to a specific operator. It is used. In connection with the socket allocation unit allocating the relevant charging socket to the session, The user physically connects their electric vehicle to the system via the socket in question. connection, Control Pilot (CP) signal or equivalent vehicle communication signal This signal is detected by the local control unit via ('5A process step'); 28 as a prerequisite to confirm that the vehicle is connected and ready to charge It is evaluated. In the sixth step of the process, the charging session created by the session ownership management unit It is associated with the relevant CPO. A unique session ID for the session. is being generated and all subsequent control commands, energy measurement data, Error logs and transaction logs are tracked using this session ID. Thus, an active charging session can be managed by another CPO or The mixing of transaction records with records belonging to different operators is technically... It is being blocked. In an additional step after the session ownership record is created ('step 6A'), The power control unit activates the locking mechanism of the corresponding charging socket. The connector is physically locked; this locking is especially important for direct current (DC) fast charging. It is implemented as a safety measure in applications. Energy measurement unit, Immediately after the lockout is complete, the counter value for that moment is returned to the counter start. It is recorded in the session ownership log as a value. In the seventh processing step, the virtual power slicing engine is activated. This unit, instantaneous power information received from the energy measurement unit, the number of active charging sessions, each the operator's power requirements and the priority parameters defined in the system together By evaluating the situation, it calculates the amount of power to be allocated to each operator. The calculated power values ​​are transmitted to the power control unit, and the charging process begins there. This is done according to the values. Power requirements during charging processes If the power distribution changes, the calculation process is repeated and the dynamics are adjusted accordingly. It is being updated accordingly. Thus, the existing network connection capacity is made as efficient as possible. It is used in this way. In the eighth step of the process, the data isolation unit contains user information for each operator, Energy consumption records, error records, and transaction data are only accessible to the relevant operator. It enables processing within the logical working space. The same processor and memory... Despite its use, memory management allows each operator to manage the data they use. The areas are separated from each other. Thus, any transaction belonging to any operator 29 This prevents data from mixing with data from another operator, and the system... Reliability is increased. This separation provided by the data isolation unit is unique. This is not a one-time process step, but starts from the beginning of the charging session. a background that remains continuously active until its termination The plan is a protection mechanism. In the ninth step of the process, the communication management unit monitors the charging process. generated status information, energy consumption records, error messages, and control data. It transmits this information to the relevant operator's central management system. Same Despite the use of communication infrastructure, each data packet contains the CPO information to which it belongs. Since they are routed together, data flows belonging to different operators are separated from each other. It is conducted independently. This data exchange is continuous throughout the charging session. is in operation; remotely sent from the relevant CPO's OCPP backend system. Stop, power limit, or status check commands, before being executed CPO ID in the relevant session ownership record by the communications management unit and verified by comparing it with the session ID; if verification fails, the command... It is rejected and an incident report is created. In the tenth step of the process; the charging process is terminated by the user, relevant The CPO sending a remote stop command from the OCPP backend system or one of the triggers for the battery to reach its target charge level Upon this occurrence, the local control unit stops the charging process. Session The ownership management unit is closing the relevant charging session, energy metering unit. The final consumption information generated is transferred to the records management unit. In the eleventh step of the process, the records management unit records the energy consumption for the relevant charging process. information, transaction records, user information and necessary technical records related to the CPO It creates each one separately for each name. Then the socket allocation unit assigns the corresponding charging socket. adding it back to the shared pool and the system is processing a new user request. It is being prepared for use. In the twelfth step of the process, the CPO-based external service integration module, session Upon detecting the start or completion event, the relevant operator shall 30 Activating the integration channel; from a third-party service provider by processing the received content only in the relevant operator's workspace memory region transmitting the content to the user interface and closing the channel upon session termination. It cleans the data. By performing these steps in sequence multiple CPOs separated from each other on a single physical electric vehicle charger being able to provide services independently, charging sessions to the correct operator redirection, dynamic management of energy capacity, belonging to operators secure separation of transaction data and high-level physical infrastructure It is ensured that it is used efficiently. The system described in the invention involves four key actors: (i) the physical charger from operational continuity of shared hardware resources, to system health monitoring, from device-level configuration to the creation of CPO work contexts (ii) the system operator responsible for the related high-level authorization processes; It offers charging services to its users, and has its own logical operating context. OCPP backend connection with charging network operator (CPO); (iii) main Socket and / or time zone resources delegated to him / her by the CPO within, an isolated sub-field of work independent of the main CPO work context (iv) operating sub-operator (sub-CPO); and (iv) user authentication interface The user is the one who creates the charging request via the hardware. The local control unit, the word The topic is the interaction between four actors: access rights, session ownership, sockets. allocation, power allocation, communication routing, and record separation rules It manages by implementing. The system operator manages the common hardware resources of the physical charger. is the top administrative actor ensuring continuity; the initial configuration of the device, CPO work establishing contexts, defining system-level resource limits, device They are responsible for monitoring health information and carrying out care procedures. The system operator only monitors total energy consumption, system health parameters, and They can access fault logs; user credentials belonging to any CPO, They cannot access charging sessions, pricing data, or transaction logs. 31 The system operator also has information regarding the embedded software of the local control unit. Update (firmware update) operations are performed through the management interface module. can initiate; active CPO work during the update in question the contexts are safely suspended and the update is complete. then the relevant working contexts are reloaded without data loss. It is secured by an isolation unit and a multiple CPO management unit. The system operator creates a new charging network via the management interface module. When the operator (CPO) is defined in the system, the relevant information is displayed on the local control unit. An independent work context is created for the CPO. This work context includes... communication profiles, authorization parameters, user authentication information, OCPP connection information, security certificates, service level (SLA) parameters, Power priorities and operating rules exist independently in logical data spaces. This allows the work of existing CPOs to be stored. Thus, when a new CPO is added to the system, the work of the existing CPOs is also stored. Their contexts are not affected. When a CPO needs to be removed from the system, the system operator will identify the relevant CPO. This disables the working context via the management interface module; At this stage, it is confirmed that there is no active session belonging to the relevant CPO; active session If available, the sessions in question are securely terminated, multiple The CPO management unit stores the configuration information belonging to the relevant CPO in persistent data storage. It deletes data from the unit and the data isolation unit allocates working memory to the relevant working context. by cleaning up the area and assigning the source in question to a new CPO designation. makes it usable. User authentication is obtained by the user authentication module before the charging session is initiated. The relevant CPO ID is determined from the verification data obtained, and only that CPO's ID is recognized. The working context is activated. The local control unit activates the user's subscription or It does not make the commercial authorization decision; it only assigns the designated CPO identity. by selecting the correct working context accordingly, with the relevant CPO backend system. It initiates communication. 32 For safety purposes, fire, overcurrent, hardware failure, maintenance mode or In mandatory security situations arising from legislation, the system operator, local Safely manage active charging sessions via the control unit. It can terminate the process. This operation only stops the transfer of energy. This includes any CPO's access to user data or session content. It does not provide access. The security intervention carried out is related to the CPO's work. It is transferred to the context as an event log. The inability to identify any CPO ID from the user authentication data, The validation failed, the relevant working context could not be activated, in case a suitable socket cannot be found or a communication timeout occurs The local control unit does not initiate the charging session; the cause of the error is the user interface. It is reported via the system and recorded by the event log management unit. The process of defining a sub-CPO belonging to the main CPO in the system is as follows: This is done in sequence: the main CPO, from the sockets allocated to it and / or management requested that some of the time periods be transferred to a subcontractor. It creates the request through the interface module; this request is transmitted to the system operator and the system It is approved or rejected by the operator; if approved, the hierarchical structure... The authorization module is located within the main CPO work context and the system monitoring area. It creates an independent, isolated sub-workspace; multiple CPO management units, sub- Operator authorization parameters, OCPP connection information, power priority This sub-work covers the parameters and delegated socket / time zone definitions. loads into the area; CPO when user authentication data belonging to the sub-operator is received. The identity verification module activates the relevant sub-work context, and then... The charging session is executed through the same process steps as the main CPO sessions; However, session records are available with both the sub-operator and the main CPO license identities. They are created separately by the multi-license management unit by being linked together. in this context, the creation of a sub-workspace within the hierarchical authorization module and while responsible for enforcing the authorization period / resource limit, multiple licensing The management unit is solely responsible for license-based registration and reporting belonging to the sub-operator. It is responsible for the separation; the functions of these two units are independent of each other. 33 The resources allocated to the sub-CPO are part of the resource pool defined for the main CPO. It is defined as a subset; the power demands of the sub-operator are for the main CPO. by the power management unit so as not to exceed the defined upper power limit It is evaluated. When the sub-CPO's work context expires or their authority ends. When removed, it prevents the initiation of new charging sessions; active sessions remain active. completed according to predefined safety rules or securely It is terminated; after the authorization period expires, the sub-workspace is only for archival records. It is closed in a way that leaves it accessible. After the CPO identity is determined and the relevant work context is activated User interface management module, visual identity, branding information and for the active CPO. by loading authorized third-party service content, the user interface It configures this dynamically; this information is cleared when the charging session ends. The system is restored to its default state. The context of the study includes user information and authentication data belonging to a specific CPO. configuration parameters, communication information, session data, and operation software execution where the rules are logically isolated from other CPOs It describes the environment.

Claims

1- The invention allows multiple charging network operators (CPOs) to charge the same physical electric vehicle. enabling them to provide services independently via the charger. It is a multi-operator electric vehicle charging system, and its feature is; • Users and authorizations belonging to multiple charging network operators (CPOs), Communication, charging session, and transaction data are independent of each other in logical order. managing the same physical charger with multiple operators in workspaces at least one local control unit (LCU) that enables it to be operated as such, • The electrical energy that will be transferred to the electric vehicle is generated by the local control unit. At least one power electronics module controlled by the (LCU), • available power capacity from the grid during active charging sessions and at least one that dynamically allocates among charging network operators (CPOs) power control unit, • by measuring energy consumption data for each charging session, the operator at least one energy measurement that enables the creation of independent records on a per-rate basis unit, • at least one charging socket that allows the electric vehicle to be connected to the system, • at least one that enables the retrieval and verification of user credentials User authentication interface, • Showing the user information about the charging process and the user at least one user interface that enables interaction to take place, • local control unit (LCU) with at least one remote CPO server and / or third party at least one of the external service systems that enables data communication between the parties. communication interface • Depending on user authentication information, the relevant charging session will be charged appropriately. Identifying at least one CPO that directs to the network operator (CPO). module, • Charging session at the designated charging network operator's (CPO) work area Initiating at least one session redirection that directs to the relevant CPO server. unit, • by associating each charging session with its respective charging network operator (CPO) at least one session ownership management unit that manages session ownership, 35 • User data and energy logs for each charging network operator (CPO), communication data and transaction logs from other charging network operators at least one data isolation unit that enables independent processing, • Energy consumption records for each charging network operator (CPO), processing the most It contains a small record management unit.

2. According to Claim 1, it is a multi-operator electric vehicle charging system, characterized by its local User authentication for each charging network operator (CPO) of the control unit (LCU). information, communication parameters, authorization information, pricing their information and operating rules in independent, logical working areas. by storing the same physical charger independently for each charging network operator (CPO). It must include at least one multi-CPO management unit that enables it to operate as such.

3. A multi-operator electric vehicle charging system according to claim 1 or 2, with the following features: User credentials obtained from the user authentication interface, RFID card, mobile application, Plug & Charge or similar authentication methods Verification using at least one method and the relevant charging network based on the verification result. At least one user authentication module that enables the identification of the Chief Operating Officer (CPO). It includes.

4. Multi-operator electric vehicle charging system according to any of claims 1-3. Its feature is that it associates the charging network operator with verified user information. (CPO) determines that the relevant charging session can only be used by the designated charging network operator. At least one CPO identification module that directs to the (CPO) workspace. It includes.

5. Multi-operator electric vehicle charging system according to any of claims 1-4. Its feature is that it provides user information and energy measurements for each charging session. data, control commands and communication processes to the relevant charging network operator By associating it with (CPO), only the charging session in question will be able to be used during the session. at least one session that allows it to be managed by the relevant charging network operator (CPO) The ownership includes a management unit. 36 6. Multi-operator electric vehicle charging system according to any of claims 1-5. Its feature is that the local control unit (LCU) selects the available charging sockets for a specific number of charging sockets. multiple with continuously assigned operating mode to the charging network operator (CPO) Dynamically allocated operating mode among charging network operators (CPOs) at least one socket allocated that allows for switching between them according to operating rules. It includes the unit.

7. Multi-operator electric vehicle charging system according to any of claims 1-6. Its feature is that it distributes the total power capacity supplied from the grid to active charging sessions. power demands, service level for each charging network operator (CPO) Service agreements (SLAs), available power capacity, and system priority rules taking into account the power values ​​to be allocated to each charging network operator (CPO) calculates, transmits those power values ​​to the power electronics module, and charges at least one power management unit that updates power allocation values ​​throughout the process. It includes.

8. Multi-operator electric vehicle charging system according to any of claims 1-7. Its feature is that it contains user authentication data for each charging network operator (CPO). user authorization information, communication data, charging session information, energy measurement data, meter records, and transaction records are independent of each other. operating in logical fields, reading and writing about the data in question. operations are performed only within the workspace allocated to the relevant charging network operator (CPO). It must contain at least one data isolation unit that performs the function within it.

9. According to claim 8, it is a multi-operator electric vehicle charging system, characterized by its data. the isolation unit, the memory protection unit connected to the local control unit's processor, memory management unit, address range access table, separate task or thread contexts and real-time memory access provided by the operating system. through at least one of the monitoring mechanisms each charging network operator (CPO) creates separate process memory regions for each process memory region. User authentication tokens belonging to the relevant charging network operator (CPO), communication buffers, OCPP message queues, session status information, counter intermediate 37 assigning values ​​and temporary control commands within each process context At least one memory access point that allows access only to the relevant process memory region. It includes a management mechanism.

10. Multi-operator electric vehicle charging system according to any of claims 1-9. Its feature is that it provides a separate communication link for each charging network operator (CPO). Communication profiles created for each charging network operator (CPO) each charging network operator managing their sessions independently Remote CPO that processes OCPP messages belonging to the CPO in separate message queues. Data exchange with servers is handled by the relevant charging network operator (CPO). conducted through the work area and relating to each communication session at least one that enables messages to be routed to the relevant charging network operator (CPO) It includes a communications management unit.

11. Multi-operator electric vehicle charging system according to any of claims 1-10. Its feature is that it records the energy consumption data of each charging network operator (CPO). energy measurement data, transaction logs, authorization information, and reporting. by associating the data with the relevant charging network operator (CPO) in separate records. It must contain at least one record management unit that creates and stores records.

12. Multi-operator electric vehicle charging system according to any of claims 1-11. Its feature is that it identifies a different license ID for each charging socket. sessions that associate energy with the relevant license ID, for each license ID independently generating consumption records and separate for each license ID. It must include at least one multi-licensing management unit that prepares reporting data.

13. Multi-operator electric vehicle charging system according to any of claims 1-12. Its feature is that it displays the device's total energy consumption information and instantaneous power capacity. system that monitors data, hardware health information, and system failure logs performs management operations belonging to the operator and belongs to the system operator The processing area includes user information belonging to the charging network operator (CPO), charging session at least one that manages data separately from pricing information and transaction records It includes a system monitoring area. 38 14. Multi-operator electric vehicle charging system according to any of claims 1-13. Its characteristic is that it depends on the authorization information of the main charging network operator (CPO). as specific charging sockets and / or specific time periods sub-charging network the main charging network for each sub-charging network operator, which allocates to its operators and At least one hierarchical structure managing access permissions for sub-charge network operators. It includes an authorization module.

15. Multi-operator electric vehicle charging system according to any of claims 1-14. Its feature is that it detects the events of starting and ending the charging session. The data regarding these incidents is the work of the relevant charging network operator (CPO). transmitting data to third-party external service systems via the domain, third-party service The data received from the systems is used in the work of the relevant charging network operator (CPO). operating in the field and creating data exchange for the relevant charging network operator (CPO). at least one CPO-based external service operating over the communication channel It includes an integration module.

16. Multi-operator electric vehicle charging system according to any of claims 1-15. Its feature is the visual identification of the charging network operator (CPO) for the active charging session. determining their information, and designing the user interface according to that visual identity information. configuring the user interface during the charging session, related to the charging network. Managing and charging in accordance with the visual identity information of the operator (CPO). The user interface returns to its previous state upon the end of the session. By clearing session data resulting from the configuration, starting from the beginning It must include at least one user interface management module that reverts to its previous state.

17. Multi-operator electric vehicle charging system according to any of claims 1-16. Its feature is that it contains user authentication data for each charging network operator (CPO). control commands, communication data, energy measurement data, and process each of which processes its records in independent workspaces in working memory. memory access for a workspace belongs to the relevant charging network operator (CPO). Access to data transfer between workspaces is limited by the transaction context. 39 at least one operator managing the sandbox management unit according to the control rules. It includes.

18. Multi-operator electric vehicle charging system according to any of claims 1-17. Its feature is that it uses identity data obtained from user authentication information locally. processing in the control unit and identifying the relevant charging network operator (CPO), Activating the charging network operator's (CPO) workspace, connecting the charging session to the relevant directing to the work area and communication regarding the charging session in question. At least one dynamic session that associates its connection with the relevant remote CPO server. It includes a directional unit.

19. Multi-operator electric vehicle charging system according to any of claims 1-18. Its feature is that each charging socket is continuously assigned to a specific charging network operator (CPO). allocated operating mode or multiple charging network operators (CPO) usage intensity, associated with the shared work mode that has been made available for use. taking into account at least one of the following: time schedule, business policies or priority rules by receiving at least one that manages the switching processes between these operating modes The socket's operating mode includes a management unit.

20. Multi-operator electric vehicle charging system according to any of claims 1-19. Its characteristic is that when the transaction context is changed between charging network operators (CPOs). clearing shared temporary communication buffers, previous process prevents temporary data belonging to one context from being transferred to the next processing context. Activates the memory space for the new process context and allows the process context to change. It must include at least one context management unit that creates related records.

21. Multi-operator electric vehicle charging system according to any of claims 1-20. Its characteristic feature is that it monitors memory accesses performed in process memory, and detects unauthorized accesses. memory access attempts, detected unauthorized access attempts halting related operations and recording error logs regarding those access attempts. It must contain at least one memory access control unit. 40 22. Multi-operator electric vehicle charging system according to any of claims 1-21. Its feature is that it only contains the total data of the device within the management area belonging to the system operator. energy consumption data, real-time power capacity information, hardware health processing parameters and system fault logs, user identity data, charging session data, pricing information, and charging network at least one isolated instance that restricts access to transaction records belonging to the Chief Operating Officer (CPO) It includes a system administration area.

23. Multi-operator electric vehicle charging system according to any of claims 1-22. Its features include user authentication and identification of the charging network operator (CPO). Creating a session owner record, allocating a charging socket, and charging Local control procedures for determining the power value to be applied for the operation performing operations on the unit (LCU) and transmitting these operations through an external circulation (roaming) without transferring to a platform or central coordination system It must include at least one local session management unit.

24. Multi-operator electric vehicle charging system according to any of claims 1-23. Its characteristic is that when a new charging network operator (CPO) is defined in the system, The subject is user authentication information and communication information belonging to the charging network operator. parameters, authorization information and operating rules of the local control unit (LCU) assigns the independent logical workspace created on it and the relevant charging network operator provides service via existing physical electric vehicle charging stations. It must contain at least one operator configuration unit that enables it to deliver.

25. Multi-operator electric vehicle charging system according to any of claims 1-24. Its feature is that it provides users for each charging network operator's (CPO) workspace. verification processes, communication processes, charging session processes, energy measurement processes and record keeping processes independently of each other carrying out, separately managing the operational resources for each area of ​​work, and at least one multi-workspace that performs access control between work areas The area includes a management unit. 41 26. Multi-operator electric vehicle charging system according to any of claims 1-25. Its feature is that it combines the measurement data received from the energy measurement unit with the relevant charging session. associating, identifying the charging network operator (CPO) for that charging session. and energy consumption records in the data area belonging to the relevant charging network operator (CPO). It must contain at least one energy record association unit.

27. Multiple charging network operators (CPOs) sharing the same physical electric vehicle charging station. multiple devices that enable each other to provide services independently. It is an operator-assisted electric vehicle charging method; its feature is: • User credentials via user authentication interface taking, • Verification of received identity information by the local control unit (LCU), • Charging network for the relevant charging session, depending on verified credentials designation of the Chief Operating Officer (CPO), • the logical working area of ​​the designated charging network operator (CPO) activation, • Logical operation of the charging session belonging to the relevant charging network operator (CPO) being directed to the area, • Creating a session ownership record for the relevant charging session, • At least one charging socket must be allocated to each charging session, • Active charging sessions using available power capacity from the grid, Service level agreements (SLAs), available power capacity, and system priority. Allocated to the relevant charging network operator (CPO) taking into account the rules, • Measurement of energy consumption data during the charging process and the relevant charging session being associated with, • user authentication data, communication data, energy measurement data and transaction records belonging to each charging network operator (CPO) processing in independent logical workspaces, • charging via the communication link of the relevant charging network operator (CPO) data exchange regarding the session and • Energy consumption records are generated after the charging process is complete. records and reporting data with the relevant charging network operator (CPO) It involves creating a system by associating the steps involved. 42 28. According to claim 27, it is a multi-operator electric vehicle charging method, characterized by the fact that each User authentication data belonging to a charging network operator (CPO), user authorization information, communication data, charging session information, energy Measurement data, meter records, and transaction records are independent of each other. processing in logical workspaces, reading and processing of the data in question write operations are allocated only to the relevant charge network operator (CPO) to be carried out within the logical workspace and each logical work restricting access to the process memory belonging to that area to the relevant process context. It includes the steps.

29. A multi-operator electric vehicle charging method according to claim 27 or 28, feature; charging network related to evaluating user authentication information. The designation of the charging network operator (CPO), belonging to the designated charging network operator (CPO) Enabling the logical workspace, session ownership for the charging session. registration, allocation of the charging socket, and procedures to be followed for the charging process. power value determination and communication with the relevant charging network operator (CPO). The establishment of the connection is carried out by the local control unit (LCU) through an external authority. roaming platform or central coordination system It involves steps that can be carried out without transferring anything.

30. Multi-operator electric vehicle charging method according to any of claims 27-29. Its characteristic is that when the transaction context is changed between charging network operators (CPOs). Cleaning shared temporary communication buffers, previous process transferring temporary data belonging to the context to the subsequent processing context blocking, enabling the process memory region belonging to the new process context, Monitoring access to process memory, unauthorized memory access detection of attempts, procedures related to unauthorized access attempts stopping and error logs regarding said access attempts It includes the steps involved in creating it.

31. Multi-operator electric vehicle charging system according to any of claims 1-26. and its feature is that a new charging network operator (CPO) 43 is appointed by the system operator. identification in the system and the operational context of the relevant charging network operator. enabled by a charge network operator (CPO) removed from the system. deleting the configuration information from the persistent data storage unit and the related process At least one management interface module that enables clearing the memory region. It includes.

32. Multi-operator electric vehicle charging system according to any of claims 1-26. Its feature is that the connector belonging to the relevant charging socket is connected to an active charging socket. locking it when it is allocated to a charging session and the charging process at least one socket lock that allows it to be released after termination The Control Pilot signal indicates that the vehicle is connected to the relevant charging socket via this mechanism or at least one circuit that detects a communication signal from a similar vehicle. It includes.