Charging interaction system, charging method, equipment, storage medium and product
By interacting with charging piles and internal enterprise systems through the billing interaction system, user characteristic information and enterprise billing rules are obtained, solving the problem that existing charging pile systems cannot meet personalized billing needs and realizing a flexible enterprise billing solution.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-01-26
- Publication Date
- 2026-03-24
AI Technical Summary
The existing charging pile system uses the same billing service model, which makes it difficult to meet the personalized billing needs of different companies.
A billing interaction system is provided, including account management, data interaction, data synchronization and billing modules. Through interaction with charging piles and internal enterprise systems, it obtains user characteristic information and enterprise billing rules, and performs personalized billing based on employee information.
It enables flexible billing based on different companies' employee information and billing rules, meeting companies' personalized billing needs and improving the flexibility and security of charging services.
Smart Images
Figure CN121725548A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of Internet of Things (IoT) technology, and in particular to a billing interaction system, billing method, device, storage medium, and product. Background Technology
[0002] With the increasing popularity and adoption of electric vehicles, companies have introduced charging station systems to facilitate employees' daily travel and standardize internal charging management. This system not only optimizes the efficient use of charging resources and reduces unnecessary energy waste, but also further contributes to the company's sustainable development.
[0003] However, most existing charging pile systems are standardized and universal solutions that use the same billing service model for different companies, making it difficult to meet the differentiated and personalized billing needs of enterprises. Summary of the Invention
[0004] This application provides a billing interaction system, billing method, device, storage medium and product to solve the problem that the existing technology uses the same billing service model for different enterprises, which is difficult to meet the differentiated and personalized billing needs of enterprises.
[0005] To achieve the above objectives, embodiments of this application provide a billing interaction system, including: The account management module is used to authenticate logged-in users. Once authentication is successful, the logged-in user is allowed to log in. The data interaction module is used to interact with the charging pile, control the charging pile to charge the successfully logged-in user, and obtain the charging information and characteristic information of the successfully logged-in user; it is also used to interact with the enterprise's internal system to obtain the enterprise's billing rules for the successfully logged-in user. The data synchronization module is used to synchronize employee information with the enterprise's internal system, establish a mapping relationship between user characteristic information and user employee information; it is also used to obtain employee information of successfully logged-in users based on the mapping relationship. The billing module is used to calculate charging fees based on the charging information of successfully logged-in users, employee information, and enterprise billing rules.
[0006] As an improvement to the above solution, the data interaction module is also used for: According to the charging pile communication mechanism, a long connection is established with the charging pile to interact with the charging pile through the long connection; The charging pile communication mechanism is used to define the communication protocol, data interaction interface and data communication message format between the data interaction module and the charging pile.
[0007] As an improvement to the above scheme, the data communication message format is used to specify that the communication packet includes: a preamble, a charging pile device number, a destination address, a data packet length, a data packet, and a checksum.
[0008] As an improvement to the above scheme, the data packet includes a command code and a data code.
[0009] As an improvement to the above solution, the billing module is specifically used for: Based on the enterprise's billing rules, obtain all billing rules that match the employee information of the successfully logged-in user; Based on preset filtering rules, all billing rules that match the employee information of successfully logged-in users are filtered to obtain the billing rules applicable to the successfully logged-in users this time. The charging fee is calculated by using the applicable billing rules and charging information of the successfully logged-in user.
[0010] As an improvement to the above solution, the billing module is also used for: Before billing, the employee information and account information of successfully logged-in users are verified to confirm the charging fee deduction mode that can be provided to successfully logged-in users, so as to deduct the charging fee from the employee's internal enterprise account through the charging fee deduction mode.
[0011] To achieve the above objectives, embodiments of this application also provide a billing method applied to the aforementioned billing interaction system, comprising: Authenticate the logged-in user; if the authentication is successful, the logged-in user is allowed to log in. After controlling the charging pile to charge a successfully logged-in user, obtain the charging information and characteristic information of the successfully logged-in user; Retrieve the enterprise billing rules for successfully logged-in users; Obtain employee information from the company's internal systems and establish a mapping relationship between user characteristic information and user employee information; Retrieve employee information of successfully logged-in users based on the mapping relationship; Charging fees are calculated based on the charging information of successfully logged-in users, employee information, and enterprise billing rules.
[0012] To achieve the above objectives, embodiments of this application also provide a billing device, including a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor implements the billing method as described above when executing the computer program.
[0013] To achieve the above objectives, embodiments of this application also provide a computer-readable storage medium, the computer-readable storage medium including a stored computer program; wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to perform the billing method as described above.
[0014] To achieve the above objectives, embodiments of this application also provide a computer program product, including a computer program / instructions, which, when executed by a processor, implement the billing method as described above.
[0015] Compared with existing technologies, the billing interaction system, billing method, device, storage medium, and product provided in this application embodiment include: an account management module for authenticating logged-in users, allowing them to log in upon successful authentication; a data interaction module for interacting with charging piles to control charging for successfully logged-in users and to obtain their charging and characteristic information; it also interacts with internal enterprise systems to obtain enterprise billing rules for successfully logged-in users; a data synchronization module for synchronizing data with employee information in the enterprise's internal system, establishing a mapping relationship between user characteristic information and user employee information; and it also obtains employee information for successfully logged-in users based on the mapping relationship; and a billing module for billing charging based on the successfully logged-in user's charging information, employee information, and enterprise billing rules to obtain the charging fee. Therefore, this application embodiment, by connecting the data interaction module to the enterprise's internal system's enterprise billing rules and combining the mapping relationship between user characteristic information and user employee information established by the data synchronization module, can flexibly match the billing rules of different enterprise employees, thereby replacing the generalized unified billing model and meeting the personalized billing needs of different enterprises. Attached Figure Description
[0016] Figure 1 This is a structural block diagram of a billing interaction system provided in an embodiment of this application; Figure 2 This is a format diagram of a communication packet provided in an embodiment of this application; Figure 3 This is a format diagram of a data packet provided in an embodiment of this application; Figure 4 This is a format diagram of an enterprise billing rule provided in an embodiment of this application; Figure 5 This is a flowchart of a billing method provided in an embodiment of this application; Figure 6 This is a flowchart of a billing interaction provided in an embodiment of this application; Figure 7 This is a structural block diagram of a billing device provided in an embodiment of this application. Detailed Implementation
[0017] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.
[0018] In the description of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0019] In this application description, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.
[0020] In this application description, the terms "first," "second," etc., are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus. The term "based on" means "at least partially based on." The term "according to" means "at least partially according to." The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments." The term "and / or" means at least one of the connected objects, such as A and / or B, indicating three cases: including only A, only B, and both A and B. Unless otherwise stated, the term "multiple" means two or more.
[0021] See Figure 1 , Figure 1 This is a structural block diagram of a billing interaction system provided in an embodiment of this application. The billing interaction system includes: Account management module 11 is used to authenticate logged-in users. If the authentication is successful, the logged-in user is allowed to log in. It's worth noting that the account management module creates user accounts for enterprise users within the billing interaction system for login. When an enterprise user logs in to the billing interaction system via the charging terminal app by entering their username and password, this user is referred to as a logged-in user. The account management module then authenticates the user; successful authentication allows the user to log in, and this user is referred to as a successfully logged-in user. Once a successfully logged-in user has logged in, the charging terminal app sends a charging permission notification to them. When the successfully logged-in user clicks "Start Charging," the billing interaction system responds by initiating a charging request to the charging station, and the charging station begins charging the successfully logged-in user's device.
[0022] In addition, the account management module provides basic functions such as basic account information, recharge history, consumption history, and historical transaction records. It also provides data querying for internal enterprise systems through an API (Application Programming Interface).
[0023] The data interaction module 12 is used to interact with the charging pile, control the charging pile to charge the successfully logged-in user, and obtain the charging information and characteristic information of the successfully logged-in user; it is also used to interact with the enterprise's internal system to obtain the enterprise's billing rules for the successfully logged-in user. It's worth noting that the data interaction module is primarily used to receive and report charging pile data (e.g., charging information and characteristic information of successfully logged-in users) via the charging pile API interface, and to remotely control charging start / stop (i.e., control the charging pile to charge successfully logged-in users); as well as to perform billing and deduction operations for internal enterprise accounts and query transaction records via the enterprise's internal system API interface. Details are as follows: (1) The interaction functions with the charging pile (specifically the charging pile) include: The billing interaction system collects basic information about the charging pile, such as its location, model, and parameters. The billing interaction system monitors the charging pile's survival status in real time; The billing and interaction system monitors the charging process information of the charging pile in real time; The billing interaction system requests charging start and charging end commands from the charging station; The billing interaction system reports the charging information of successfully logged-in users, such as charging energy consumption, charging start time, and charging end time. The billing interaction system reports the characteristic information of successfully logged-in users, such as IC (Integrated Circuit Card) card number, mobile phone NFC (Near Field Communication) number, APP (Application) IMEI (International Mobile Equipment Identity) unique value, fingerprint feature code, facial feature code, custom feature code, etc.
[0024] (2) Interaction functions with internal enterprise systems (such as existing intranet systems like enterprise or company OA systems, smart card systems, welfare platforms, etc.) include: The enterprise's internal system queries the user account of the billing interaction system for transaction records; The enterprise's internal system submits change requests such as account opening, account closing, and account loss reporting to the user account of the billing interaction system; The enterprise's internal system submits requests for cash top-ups, points top-ups, etc., to the user accounts of the billing interaction system; The billing interaction system reads the enterprise's billing rules from its internal system. These rules can be pre-set by the enterprise, supporting various billing rules to meet diverse and customized billing needs. This goes beyond a single, user-indiscriminate billing model for charging stations, satisfying the internal management requirements of different enterprises. For example, pre-set billing discount rates based on employee information such as organizational affiliation, basic employee information, job position, and performance. When a successfully logged-in user matches the corresponding employee information, the appropriate discount rate is selected for charging billing. The billing interaction system synchronizes user account charging transaction data with the enterprise's internal systems.
[0025] Data synchronization module 13 is used to synchronize data with employee information in the enterprise's internal system, establish a mapping relationship between user characteristic information and user employee information; it is also used to obtain employee information of successfully logged-in users based on the mapping relationship. It is worth noting that the data synchronization module is mainly used to keep employee information such as organizational information, basic employee information, job information, and performance information within this system consistent with the employee information in the enterprise's internal system. Through the API interface with the enterprise's internal system, it completes the data synchronization between this system and the enterprise's internal system, ensuring that this employee information is consistent between this system and the enterprise's internal system, thereby identifying user identity.
[0026] Specifically, after data synchronization is completed, a mapping relationship between user feature information and user employee information can be established. Based on this mapping relationship and the feature information of the successfully logged-in user obtained by the data interaction module, the employee information of the successfully logged-in user can be obtained.
[0027] The billing module 14 is used to calculate the charging fee based on the charging information of successfully logged-in users, employee information, and enterprise billing rules.
[0028] It is worth noting that the billing module calculates the charging fee for successfully logged-in users based on their charging information, employee information, and enterprise billing rules. This allows for flexible matching of billing rules for employees of different enterprises, thus replacing the generalized billing model and meeting the personalized billing needs of different enterprises.
[0029] Furthermore, the billing interaction system also includes: The security control and management module is used to encrypt various types of information.
[0030] This application embodiment encrypts various types of information to prevent data leakage, especially sensitive information that needs to be transmitted, such as charging information between charging piles and the system, employee information, and billing transaction records. This prevents such information from being illegally stolen or tampered with during transmission. Simultaneously, this encryption also covers the information storage stage, reducing the risk of unauthorized access to stored data. This not only effectively protects the company's internal information assets and employee privacy, avoiding information risks or compliance issues caused by data leakage, but also makes the entire system more compliant with data security regulations, further enhancing the system's security and reliability, and increasing the company's trust in the system's data security.
[0031] Furthermore, the billing interaction system also includes: The system monitoring module is used to monitor the status of the charging piles.
[0032] This application provides a status monitoring system for charging piles, so that various problems and faults during system operation can be quickly reported, responded to, and resolved, ensuring the long-term stable operation of the system.
[0033] It is worth noting that the system's interaction with charging piles and internal enterprise systems relies on various API interfaces. The following is a description of these API interfaces: (1) API interface with charging piles 1. Basic Information API of Charging Pile Host Based on the TCP (Transmission Control Protocol) / IP (Internet Protocol) protocol, the Socket interface provides detailed information such as charging pile identification, location, type, power, current status (availability), pricing unit information, and supported charging standards.
[0034] 2. Charging Pile Startup API The Socket interface based on the TCP / IP protocol initiates a request to start the charging service at the charging station, and queries data such as charging start confirmation information, estimated charging time, and metering estimates.
[0035] 3. Charging station charging completion API Based on the TCP / IP protocol, the Socket interface initiates a request to end the charging service at the charging station, and queries information such as the charging end confirmation receipt, actual charging amount, charging duration, and total charging metering.
[0036] 4. Charging Pile Status Monitoring API The TCP / IP-based Socket interface provides long-polling monitoring of the charging pile's availability status, as well as charging and power-off requests.
[0037] (2) API interface with the company's existing internal systems 1. Enterprise Organizational Structure API Based on the HTTP protocol interface, it provides the ability to query organizational information such as company name, company code, company type, company level, organization name, organization code, organization level, and main and secondary responsible persons of the organization.
[0038] 2. Employee Basic Information API Based on the HTTP (Hypertext Transfer Protocol) interface, it provides the ability to query basic employee information such as employee name, employee code, employee account, employee position, employee level, and employee type.
[0039] 3. Employee Position Information API Based on the HTTP protocol interface, it provides a way to query job information such as job title, job responsibilities, department, job level, and job status.
[0040] 4. Employee Performance Information API Based on the HTTP protocol interface, it provides performance information such as performance scores, assessment cycles, key performance indicators (KPI) completion status, superior evaluations, and reward and punishment records.
[0041] 5. Employee Consumption Account Inquiry API Based on the HTTP protocol interface, it provides basic information such as querying employee account balance, employee arrears, account status, consumption history, and recharge history.
[0042] 6. Employee Consumption Account Transaction API Based on the HTTP protocol interface, it provides functions for employee account top-up and account deduction.
[0043] In an optional embodiment, the data interaction module is further configured to: According to the charging pile communication mechanism, a long connection is established with the charging pile to interact with the charging pile through the long connection; The charging pile communication mechanism is used to define the communication protocol, data interaction interface and data communication message format between the data interaction module and the charging pile.
[0044] It is worth noting that when this system is deployed and put into operation, a long-lived connection needs to be established according to the charging pile communication mechanism. This is to enable the acquisition of basic information about the charging pile, remote control of charging pile initiation and termination, and real-time reporting of charging pile charging process information by utilizing the charging pile host basic information API, charging pile charging start API, charging pile charging end API, and charging pile status monitoring API. The specific charging pile communication mechanism is defined as follows: ① Communication protocol between the data interaction module and the charging pile The TCP / IP protocol is used to provide reliable data transmission services, ensuring that data packets arrive accurately from the sender to the receiver. Data integrity is guaranteed through acknowledgment mechanisms, retransmission mechanisms, and error detection.
[0045] ② Data interaction interface between the data interaction module and the charging pile The system uses a Socket interface to send and receive data packets with the charging pile.
[0046] ③ Data communication message format between the data interaction module and the charging pile The data communication message format defines the internal structure of the communication packet. A communication packet refers to all the bytes transmitted in a single upload or download operation.
[0047] In one optional embodiment, the data communication message format is used to specify that the communication packet includes: a preamble, a charging pile device number, a destination address, a data packet length, a data packet, and a checksum.
[0048] In this embodiment of the application, the maximum length of a typical communication packet is 1024 bytes, and the communication packet format is as follows: Figure 2The specific lengths of each component are as follows: Preamble: 1 byte; Charging pile device number: 1 byte; Destination address: 2 bytes; Data packet length: 2 bytes; Data packet: Variable length, specified by the data packet length; Checksum: 2 bytes, which can be obtained based on the destination address and data packet. For example, the CRC16 (Cyclic Redundancy Check 16) code from the destination address to the last byte of the data packet can be calculated as the checksum, using the CCITT (International Telegraph and Telephone Consultative Committee) standard.
[0049] Furthermore, the data packet format is as follows: Figure 3 It includes command codes and data codes (including data code 1, data code 2, ..., data code n). Among them, the command code can occupy 1 byte; the data code is the data content.
[0050] This system communicates with the charging pile based on the aforementioned communication packets. The roles of sender and receiver can be interchanged. That is, the sender assembles the communication packet according to the above message requirements and sends it to the receiver through the Socket interface. The receiver receives the message and, after verifying the integrity and accuracy of the message, parses the data packet for subsequent related business processing, and finally assembles a communication packet to respond to the sender.
[0051] The communication packets sent by the sender must be transmitted continuously. After receiving a complete communication packet, the receiver will check the correctness of each part of the packet and respond accordingly. Specific situations include: (1) When the preamble, destination address, data packet length, or checksum of the communication packet is incorrect, the receiver shall not respond. (2) When the communication packet is correct, the data packet in the response packet from the receiver contains only one command code. The possible results of the command code are as follows: 0x81 indicates normal reception; A command code followed by some uploaded data indicates a normal response; 0x82 indicates a request to resend; 0x84 indicates invalid data; 0x85 indicates that all data has been uploaded; (3) When the communication packet verification is correct, the data packet is parsed, the corresponding business processing is performed, and the response data packet is assembled into a complete communication packet for reply. Different messages in the communication packet represent different business processes. The detailed interface specifications are defined in the interface document of the charging pile.
[0052] In one optional embodiment, the billing module is specifically used for: Based on the enterprise's billing rules, obtain all billing rules that match the employee information of the successfully logged-in user; Based on preset filtering rules, all billing rules that match the employee information of successfully logged-in users are filtered to obtain the billing rules applicable to the successfully logged-in users this time. The charging fee is calculated by using the applicable billing rules and charging information of the successfully logged-in user.
[0053] It is worth noting that in this application embodiment, the employee information of a successfully logged-in user may match multiple billing rules within the enterprise billing rules. These multiple billing rules will be filtered to select the applicable billing rule for this application. For example, the billing rule with the highest rule weight will be selected as the applicable billing rule for this application. In this way, the applicable billing rule and charging information will be used for charging billing.
[0054] In one specific embodiment, the specific structure of the enterprise billing rules is as follows: Figure 4 The parameter input section consists of employee information (u), which supports user organizational information, employee level information, job information, performance information, and flexibly definable expansion attributes. Billing rules include data domains, data values, and rule conditions. The matching results include the rule weight and billing discount rate (z) of this billing rule. The data domains support multi-dimensional data areas synchronized from internal enterprise systems, such as organizational information, employee level information, job information, and performance information. Custom expansion attributes are also provided as personalized data domains.
[0055] Therefore, in the calculation formula of the charging transaction fee F(m2) = (e, t[t2-t1], z{R[i->u]}), the charging energy consumption e and charging time t are fixed, while the charging discount rate (z) is dynamically calculated in real time based on the billing rule R(u) matched with the employee information. Thus, unlike the standard billing mode of existing charging pile systems, this system achieves different billing discount rates (z) for different enterprise user identities u, ultimately resulting in a billing result F(m2), which meets the company's refined management needs regarding employee welfare and benefits.
[0056] In an optional embodiment, the billing module is further configured to: Before billing, the employee information and account information of successfully logged-in users are verified to confirm the charging fee deduction mode that can be provided to successfully logged-in users, so as to deduct the charging fee from the employee's internal enterprise account through the charging fee deduction mode.
[0057] It's worth noting that before billing, the billing module verifies employee information through the employee consumption account query API, performing a secondary verification of the user's identity and account information. This confirms that the payment deduction for this transaction is eligible for the charging fee deduction mode provided to successfully logged-in users. The deduction is made from the user's internal company account, which not only alleviates concerns about employees holding large amounts of credit in their internal accounts but also allows the company to distribute benefits to users' internal accounts through employee welfare programs, thus increasing employee loyalty.
[0058] Optionally, the billing module offers two pre-set billing modes: real-time deduction when balance is sufficient and deduction on an outstanding balance when balance is insufficient. This allows users to complete charging even when their account balance is low, improving the convenience of the charging service and the user experience. Furthermore, the billing module can provide rules for other personalized billing modes to adapt to the diverse consumption needs of different user groups.
[0059] See Figure 5 , Figure 5 This is a flowchart of a billing method provided in an embodiment of this application, the billing method including: S31. Authenticate the logged-in user. If the authentication is successful, the logged-in user is allowed to log in. S32. After controlling the charging pile to charge the successfully logged-in user, obtain the charging information and characteristic information of the successfully logged-in user; S33. Obtain the enterprise billing rules for successfully logged-in users; S34. Obtain employee information from the enterprise's internal systems and establish a mapping relationship between user characteristic information and user employee information; S35. Obtain employee information of successfully logged-in users according to the mapping relationship; S36. Calculate charging fees based on the charging information of successfully logged-in users, employee information, and enterprise billing rules.
[0060] It is worth noting that the working process of the billing method described in this application embodiment can refer to the working process of each module in the billing interaction system described in the above embodiment, and achieve the same beneficial effect, which will not be repeated here.
[0061] In one specific embodiment, the interaction process between the billing interaction system and the charging pile, as well as the enterprise's internal systems, is as follows: Figure 6 .
[0062] Step S0: The system establishes a long-lived communication connection during initialization upon going online.
[0063] Step S1: Enter username and password: Enterprise users enter their username and password in the charging terminal app to complete login verification before charging transactions.
[0064] Step S2: Enter username and password: The charging terminal App transmits the username and password entered by the enterprise user to this system for login authentication.
[0065] Step S3: Return authentication result: This system completes the login authentication of the charging user and returns the authentication result to the enterprise user.
[0066] Step S4: Click to start charging: A successfully logged-in enterprise user (i.e., a successfully logged-in user) sends a request to start charging.
[0067] Step S5: Request to start charging: The charging terminal app submits a charging start request to this system.
[0068] Step S6: Assemble the feature information of the successfully logged-in user and remotely control the start-up: This system assembles the feature information of the user who successfully logged in for this charging transaction using the username parameter, and initiates a charging pile start-up service request through the charging pile start-up API interface to remotely control the charging pile to start charging.
[0069] Step S7: Charging Started: The charging station has started charging.
[0070] Step S8: Charging Start Response: The charging pile responds to the charging start API interface request, notifying the system that the data message verification was successful, the charging pile has successfully started charging, and the charging pile starts timing and metering at the same time.
[0071] Step S9: Reporting real-time monitoring data: The charging pile will synchronize the charging data status to this system in real time through the charging pile status monitoring API.
[0072] Step S10: Push charging information: This system parses and processes the raw charging information reported by the charging pile, transforms it into charging information that users can understand, and pushes it to the charging terminal App.
[0073] Step S11: Display the charging process: The charging terminal app displays the charging process so that users can keep track of the charging status.
[0074] Step S12: Click to end charging: Enterprise users send a request to end charging.
[0075] Step S13: Request to end charging: The charging terminal app submits a charging end request to this system.
[0076] Step S14: Remote Control Shutdown: This system initiates a charging pile shutdown service request through the charging pile charging end API interface, and remotely controls the charging pile to stop charging.
[0077] Step S15: Charging stopped: The charging station has stopped charging.
[0078] Step S16: End of charging response reply: The charging pile responds to the API interface request for the end of charging, notifying the system that the data message verification was successful, the charging pile has successfully ended charging, and the timing and metering of this charging transaction has ended.
[0079] Step S17: Parsing the charging end response message: This system parses the characteristic information of the successfully logged-in user, charging energy consumption, and charging end time of this charging transaction through the charging end API interface message returned by the charging pile. Finally, it obtains the employee information, charging energy consumption, and charging duration of the successfully logged-in user, which are used to participate in the subsequent billing process of this charging transaction.
[0080] The billing formula is: F(m2) = (e, t[t2-t1], z{R[i->u]}); In the formula, F(m2) represents the charging cost of this transaction; m2: Payment amount (virtual currency) in the employee's internal company account (specifically, the company's internal virtual settlement account). Payments can be completed by deducting virtual currency from the company's internal virtual settlement account.
[0081] e: represents the energy consumption of this charging.
[0082] t: represents the duration of this charging session.
[0083] t1: Represents the start time of this charging session.
[0084] t2: Represents the end time of this charging session.
[0085] i: Represents the characteristic information of a successfully logged-in user; u: Represents employee information for successfully logged-in users; R: Represents the billing rules applicable to the successfully logged-in user for this transaction; z: Represents the billing discount rate applicable to the successfully logged-in user for this transaction.
[0086] This step involves parsing the charging completion response message. It uses the charging completion API interface message returned by the charging pile to parse the user's characteristic information (i), charging energy consumption (e), and charging completion time (t2) for this charging transaction. The specific implementation principle is as follows: Taking a specific charging transaction involving 10 kWh of energy consumption as an example, the charging pile will establish a long-lived communication connection during the system's initialization process. It will then report the completed charging transaction via a TCP / IP protocol-based Socket interface. The specific content of the communication packet for a 10 kWh energy consumption transaction will be explained below: FE 01 00 01 00 0A 63 01 44 63 3E 00 00 00 00 64 25 89 After receiving the above message returned by the charging pile, the system first verifies the integrity and correctness of the message according to the CRC16 / CCITT technical standard; then it extracts the data packet from the communication packet and finally parses the data packet.
[0087] The message meaning after parsing according to the communication packet data specification is as follows: FE: Preamble; 01: Charging station No. 1; 00 01: Destination address; 00 0A: The length of this data packet is 10 bytes; 63 01 44 63 3E 00 00 00 00 64: This communication data packet has a length of 10 bytes. 25 89: CRC16 message checksum; After verifying the integrity and correctness of the communication packet based on the CRC16 / CCITT technical standard and the checksum in this transaction message, the following data packet is obtained: 63 01 44 63 3E 00 00 00 00 64 The data packet information is parsed according to the charging pile charging completion API interface specification as follows: 63: This communication command code 63 represents a charging transaction instruction; 01 44 63 3E: User's characteristic information (i); 00: This communication event code 00 represents a normal reduction event; 00 00 00 64: Energy consumption metering 10 kWh (e).
[0088] Step S18: Find the mapping relationship between user characteristic information and user employee information to obtain the employee information of successfully logged-in users, such as their department, job level, employee type, account points, and other employee information.
[0089] Step S19: Verify employee information and account information.
[0090] Step S20: Calculate charging costs and generate personalized bills.
[0091] Step S21: Personalized billing pushed out, awaiting settlement: This system will push the final calculated charging bill to the user for confirmation and payment.
[0092] Step S22: The charging terminal app displays the bill and prompts the user to confirm and pay.
[0093] Step S23: Employee internal account billing: User confirms and completes payment.
[0094] Step S24: Virtual account settlement and deduction: This system deducts fees from the account.
[0095] Step S25: Generate personalized transaction records: This system generates detailed transaction logs.
[0096] Step S26: Push settlement result: This system pushes the payment result to the charging terminal App.
[0097] Step S27: The payment result is displayed on the charging terminal app.
[0098] Furthermore, this application also provides a computer-readable storage medium, which includes a stored computer program; wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to perform the billing interaction system as described in any of the above embodiments.
[0099] Furthermore, this application also provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the billing interaction system as described in any of the above embodiments.
[0100] See Figure 7 , Figure 7This is a structural block diagram of a billing device provided in an embodiment of this application. The billing device includes: a processor 21, a memory 22, and a computer program stored in the memory 22 and executable on the processor 21. When the processor 21 executes the computer program, it implements the steps in the above-described billing interaction system embodiment. Alternatively, when the processor 21 executes the computer program, it implements the functions of each module / unit in the above-described device embodiments.
[0101] For example, the computer program may be divided into one or more modules / units, which are stored in the memory 22 and executed by the processor 21 to complete this application. The one or more modules / units may be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program in the billing device.
[0102] The billing device may include, but is not limited to, processor 21 and memory 22. Those skilled in the art will understand that the schematic diagram is merely an example of a billing device and does not constitute a limitation on the billing device. It may include more or fewer components than illustrated, or combine certain components, or different components. For example, the billing device may also include input / output devices, network access devices, buses, etc.
[0103] The processor 21 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor. The processor 21 is the control center of the billing device, connecting all parts of the billing device via various interfaces and lines.
[0104] The memory 22 can be used to store the computer programs and / or modules. The processor 21 implements various functions of the billing device by running or executing the computer programs and / or modules stored in the memory 22 and calling the data stored in the memory 22. The memory 22 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the mobile phone (such as audio data, phonebook, etc.). In addition, the memory 22 may include high-speed random access memory, and may also include non-volatile memory, such as hard disk, memory, plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.
[0105] If the modules / units integrated into the billing device are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by the processor 21, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc.
[0106] It should be noted that the device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Furthermore, in the accompanying drawings of the device embodiments provided in this application, the connection relationships between modules indicate that they have communication connections, which can be specifically implemented as one or more communication buses or signal lines. Those skilled in the art can understand and implement this without any creative effort.
[0107] The above description is the preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications are also considered to be within the scope of protection of this application.
Claims
1. A billing interaction system, characterized in that, include: The account management module is used to authenticate logged-in users. Once authentication is successful, the logged-in user is allowed to log in. The data interaction module is used to interact with the charging pile, control the charging pile to charge the successfully logged-in user, and obtain the charging information and characteristic information of the successfully logged-in user. It is also used to interact with internal enterprise systems to obtain the enterprise billing rules for successfully logged-in users; The data synchronization module is used to synchronize employee information with the enterprise's internal systems and establish a mapping relationship between user characteristic information and user employee information; It is also used to obtain employee information of successfully logged-in users based on the mapping relationship; The billing module is used to calculate charging fees based on the charging information of successfully logged-in users, employee information, and enterprise billing rules.
2. The billing interaction system as described in claim 1, characterized in that, The data interaction module is also used for: According to the charging pile communication mechanism, a long connection is established with the charging pile to interact with the charging pile through the long connection; The charging pile communication mechanism is used to define the communication protocol, data interaction interface and data communication message format between the data interaction module and the charging pile.
3. The billing interaction system as described in claim 2, characterized in that, The data communication message format specifies that the communication packet includes: a preamble, charging pile device number, destination address, data packet length, data packet, and checksum.
4. The billing interaction system as described in claim 3, characterized in that, The data packet includes command code and data code.
5. The billing interaction system as described in claim 1, characterized in that, The billing module is specifically used for: Based on the enterprise's billing rules, obtain all billing rules that match the employee information of the successfully logged-in user; Based on preset filtering rules, all billing rules that match the employee information of successfully logged-in users are filtered to obtain the billing rules applicable to the successfully logged-in users this time. The charging fee is calculated by using the applicable billing rules and charging information of the successfully logged-in user.
6. The billing interaction system as described in claim 1, characterized in that, The billing module is also used for: Before billing, the employee information and account information of successfully logged-in users are verified to confirm the charging fee deduction mode that can be provided to successfully logged-in users, so as to deduct the charging fee from the employee's internal enterprise account through the charging fee deduction mode.
7. A billing method, characterized in that, Applied to the billing interaction system as described in claim 1, comprising: Authenticate the logged-in user; if the authentication is successful, the logged-in user is allowed to log in. After controlling the charging pile to charge a successfully logged-in user, obtain the charging information and characteristic information of the successfully logged-in user; Retrieve the enterprise billing rules for successfully logged-in users; Obtain employee information from the company's internal systems and establish a mapping relationship between user characteristic information and user employee information; Retrieve employee information of successfully logged-in users based on the mapping relationship; Charging fees are calculated based on the charging information of successfully logged-in users, employee information, and enterprise billing rules.
8. A billing device, characterized in that, It includes a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor implements the billing method as described in claim 7 when executing the computer program.
9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored computer program; wherein, when the computer program is executed, it controls the device on which the computer-readable storage medium is located to perform the billing method as described in claim 7.
10. A computer program product, characterized in that, Includes a computer program / instruction that, when executed by a processor, implements the billing method as described in claim 7.