Api on-demand charging method and system based on multi-modal field analysis of internet of vehicles protocol

Abstract

This invention provides an API on-demand billing method and system based on multimodal field parsing of vehicle networking protocols. The method includes the following steps: S1: Generate vehicle data records; S2: Parse request parameters and identify query modalities; S3: Obtain multi-dimensional billing parameters; S4: Data retrieval and effective data volume statistics; S5: Generate the single fee for this query; S6: Fee execution and result return. This invention uses field-level and effective data count for pricing, matching resource consumption and costs to solve the pricing discrepancy problem; through field-level hierarchical billing, it supports on-demand field selection for payment, avoiding invalid costs; it can identify multimodal queries and match tiered discounts to achieve differentiated and accurate billing.

Description

Technical Field

[0001] This invention relates to the field of vehicle networking technology, and to an API on-demand billing method and system based on multimodal field parsing of vehicle networking protocols. Background Technology

[0002] The connected vehicle industry has entered the "data assetization" development stage, and the industry generally adopts a three-layer architecture of "cloud-pipe-terminal": the vehicle terminal reports vehicle status data periodically through 4G / 5G cellular networks according to the established communication protocol; the cloud platform completes data reception, protocol parsing, persistent storage and real-time calculation; upper-layer business systems and third-party partners obtain data services through API interfaces; Under the trend of API economy, automakers and third-party service providers are transforming from function subscriptions to on-demand data service access, opening up vehicle data as a measurable, priced, and settleable digital asset; the current mainstream API billing models are mainly divided into two categories: The first is communication resource-based billing: billing is based on the number of API calls (QPS) or the amount of data returned (bytes), with the basic billing module of the cloud service provider's API gateway as a typical implementation method; Second, there is the subscription-based billing: a fixed fee is charged monthly or annually, which is tied to specific data packages such as basic vehicle data packages. If the quota is exceeded, the flow will be limited or additional charges will be applied. The existing technology has the following drawbacks: 1. The billing granularity is coarse, and the pricing is seriously mismatched with the resource consumption: The existing solution uses a single API call as the smallest billing unit and does not distinguish the differences in resource consumption between different requests; querying a single field and a single value only requires a small amount of cache access, while batch multi-field queries require a large amount of I / O, computing and bandwidth resources. The difference in consumption between the two can be hundreds of times, but they are billed according to the same standard, which leads to a serious discrepancy between the pricing and the actual cost. 2. Failure to reflect field-level value differences, resulting in unreasonable user payment costs: The commercial value of fields returned by the same API interface varies significantly. High-value fields such as GPS coordinates and fault codes are not distinguished from auxiliary fields such as terminal version numbers and verification codes. The existing solution does not support on-demand field selection and payment, and users have to bear the cost for data they do not need. 3. Lack of adaptable billing for multimodal query formats: In real-world scenarios, there are various input parameter formats such as single-field queries, multi-field combination queries, and batch vehicle set queries. The existing billing engine only counts the number of calls and cannot identify differences in query structure and execute differentiated billing, nor can it set reasonable tiered discounts for batch queries. Summary of the Invention

[0003] The purpose of this invention is to address the shortcomings of existing technologies by proposing an API on-demand billing method and system based on multimodal field parsing of vehicle networking protocols.

[0004] To achieve the above objectives, the present invention adopts the following technical solution: An API-based on-demand billing system based on multimodal field parsing of vehicle networking protocols, the system includes an in-vehicle terminal layer, a cloud data access and disk storage layer, a real-time / offline computing layer, a big data storage layer, a billing rule engine layer, and an API gateway and billing execution layer; The vehicle terminal layer consists of multiple vehicle terminals and has an embedded protocol identifier injection module. The cloud data access and disk persistence layer includes a protocol parsing module, a field extraction module, a metadata generation module, a data quality verification module, and a data persistence module. The real-time / offline computing layer includes a real-time stream computing engine and a virtual field computing module; The big data storage layer includes a real-time data area, an offline data area, and a billing field metadata index table. The real-time data area and the offline data area contain corresponding vehicle data records. The billing field metadata index table stores the vehicle unique identifier (VIN), query fields, and timestamp. The billing field metadata index table is associated one-to-one with vehicle data records in the real-time data area and the offline data area through the vehicle unique identifier (VIN), query fields, and timestamp. The billing rule engine layer includes a field billing configuration table, a payment mode configuration table, a tiered discount configuration table, and a multimodal billing rule matching module; The field billing configuration table predefines the protocol field names, billing categories, and base unit prices within the vehicle network communication protocol; the billing categories include high-value, medium-value, low-value, and no-billing categories; wherein, each protocol field name corresponds to a unique billing category, and each billing category corresponds to a unique base unit price; The payment mode configuration table stores the unique identifiers and configuration records of each external caller. The configuration records include payment methods and quota information. The payment methods include five modes: prepayment, postpayment, monthly subscription, per-use subscription, and tiered pricing. The quota information includes available account balance, remaining query counts, allowed query fields for the package, package validity period, and cumulative usage. The tiered discount configuration table stores the tiered range of query quantity and the discount coefficient, with each tiered range of query quantity corresponding to a unique tiered discount coefficient; The API gateway and billing execution layer include an input parameter parsing module, a multimodal field parsing engine, a data retrieval and effective data volume statistics module, a cost calculation module, a payment mode execution module, and a response return and cost detail injection module.

[0005] This invention also proposes an API on-demand billing method based on multimodal field parsing of vehicle networking protocols, including the following steps: S1: Generate vehicle data records; S11: Vehicle terminal data acquisition and protocol identifier injection; The vehicle terminal layer collects vehicle operation data and the vehicle's unique identifier (VIN), synchronously generates a collection timestamp, injects the identifier, and reports it periodically. The vehicle terminal layer consists of multiple vehicle terminals. Each vehicle terminal has an embedded protocol identifier injection module, which adds a protocol type identifier to the vehicle operation data. According to the pre-agreed communication protocol, the vehicle terminal encapsulates the vehicle operation data, the vehicle unique identifier (VIN), and the collection timestamp to obtain data packets and periodically reports them to the cloud data access and disk layer. S12: Data parsing, verification, and vehicle data record generation; The cloud data access and disk layer receives data packets reported by the vehicle terminal. The protocol parsing module matches the corresponding protocol specification based on the protocol type identifier in the data packet, and splits the data packet based on the protocol specification to extract vehicle operation data. The field extraction module extracts the corresponding business fields from the vehicle operation data and constructs business key-value pairs. The business fields include vehicle speed, mileage, engine speed, etc.; business key-value pairs are constructed using the field name of the business field as the key and the corresponding value as the value. The metadata generation module generates a metadata record for each business field. The metadata record includes the collection timestamp, the field name of the business field, and the vehicle unique identifier (VIN). The data quality verification module performs timeliness and numerical compliance checks on business key-value pairs. If the verification passes, a normal data status flag is generated; if the verification fails, an abnormal status flag is generated and the data quality flag is added to the corresponding metadata record. The data storage module merges business key-value pairs and metadata records into the big data storage layer to generate vehicle data records.

[0006] S2: Parse request parameters and identify query modality; The API gateway and billing execution layer receive vehicle network data query requests initiated by external callers through the system's external API gateway entry point; The input parameter parsing module parses the request message carried in the vehicle network data query request and extracts the request parameters; the request parameters include the vehicle unique identifier (VIN), query fields, etc.; the query fields are the set of vehicle data field names to be queried specified by the external caller in the request. The multimodal field parsing engine parses the request parameters and identifies the query modality based on the query fields and the vehicle unique identifier (VIN). When the query fields contain only one field, it is determined to be a single-field query modality; When the query fields contain two or more fields, it is determined to be a multi-field combination query mode; When there are multiple Vehicle Identifiers (VINs), it is determined to be a batch single-field set query mode.

[0007] The multimodal field parsing engine encapsulates the identified query modality, vehicle unique identifier (VIN), and query fields into billing tuples, and then transmits the billing tuples to the billing rule engine layer.

[0008] S3: Obtain multi-dimensional billing parameters; S31: Obtain the billing category and base unit price corresponding to the protocol field name; The multimodal billing rule matching module of the billing rule engine layer receives the billing tuple and performs consistency matching between the query field fields in the billing tuple and the protocol field name in the field billing configuration table. If the match is successful, the billing category and base unit price corresponding to the protocol field name are obtained, and the process proceeds to step S32. If the match fails, it is determined to be an illegal query field, the current billing process is terminated, and an invalid field query prompt is returned to the caller. S32: Obtain the corresponding payment method and amount information; The multimodal billing rule matching module matches the unique identifier of the external caller corresponding to this vehicle network data query request with the unique identifier of the external caller stored in the payment mode configuration table. If the match is successful, the module obtains the configuration record with the same identifier and extracts the corresponding payment method and amount information from the configuration record. If the match fails, the module determines that the caller's identity is abnormal, terminates the current billing process, and returns an invalid identity verification message. S33: Obtain the corresponding tiered discount coefficient; The multimodal billing rule matching module extracts the number of Vehicle Unique Identifiers (VINs) from the billing tuple and compares them one by one with the query quantity tier intervals in the tiered discount configuration table. It matches the query quantity tier interval to which the current number of VINs belongs. If the match is successful, it obtains the tiered discount coefficient corresponding to the query quantity tier interval; if the match fails, it executes billing according to the default discount coefficient.

[0009] S4: Data retrieval and statistics of effective data volume; The data retrieval and effective data volume statistics module initiates a data retrieval to the big data storage layer based on the vehicle unique identifier (VIN) and query fields in the billing tuple; using the vehicle unique identifier (VIN) and query fields as search conditions, it retrieves matching vehicle data records from the associated real-time data area or offline data area; the vehicle data record includes the vehicle unique identifier (VIN), protocol field name, and field value; the protocol field name is the vehicle data name, and the field value is the corresponding data content; The data retrieval and valid data volume statistics module determines the validity of the acquired vehicle data records. If the vehicle unique identifier (VIN) exists legally, the field value is not empty, and the field value is within the preset valid range, it is determined to be valid data; otherwise, it is determined to be invalid data. The system counts the number of valid data entries corresponding to each protocol field name in this query, and transmits the valid data and the number of valid data entries for each protocol field to the cost calculation module.

[0010] S5: Generate the cost per query for this query; The cost calculation module obtains the query modality of the billing tuple. If the current vehicle network data query request meets two or more query modalities at the same time, the final billing will be determined according to the pre-configured charging rules in the management backend, whether it is a single-field query modality, a multi-field combination query modality, or a batch single-field set query modality. The cost calculation module calculates the cost per query based on the final determined query modality, the corresponding base unit price, the number of valid data entries in each protocol field, and the tiered discount coefficient. The cost per transaction is the sum of the product of the base unit price of each protocol field and the number of valid data entries in each protocol field, multiplied by the tiered discount factor.

[0011] S6: Cost execution and result return; The payment mode execution module deducts fees, reduces the amount, or records bills based on the payment method and amount information obtained in step S32 for the single fee obtained in step S5. The response return and fee details injection module returns valid data to the external caller and injects information such as the fee details and remaining credit limit of this query into the response result.

[0012] Compared with the prior art, the beneficial effects of the present invention are as follows: This method uses field-level and valid data count as the basis for pricing, which can clearly distinguish the difference in system resource consumption between single-field lightweight queries and batch multi-field heavy queries, so that the billing amount is highly matched with the actual computing and bandwidth resources used, solving the problem of serious discrepancy between pricing and cost, and achieving a fair correspondence between resource consumption and cost expenditure. This method predefines the billing category and base unit price of each field in the vehicle network communication protocol by configuring a field billing configuration table at the billing rule engine layer. Fields are divided into high-value, medium-value, low-value, and non-billing categories, clearly distinguishing high-value fields from auxiliary fields. The input parameter parsing module extracts the specified query fields from the request. The system only performs data retrieval, statistics, and billing on the fields selected by the caller. Fields not selected do not participate in the return and billing, so that users do not have to pay for data they do not need, and achieve reasonable payment based on field value and actual needs. This method automatically identifies three input parameter forms—single-field query, multi-field combination query, and batch vehicle set query—through a multimodal field parsing engine. It then matches the corresponding discount coefficients with a tiered discount configuration table and performs differentiated billing based on different query modalities and batch sizes. This accurately adapts to various query structures and provides reasonable tiered discounts for batch queries, solving the problem that existing billing methods cannot adapt to multimodal queries. Attached Figure Description

[0013] Figure 1 This is a flowchart illustrating the steps of the API on-demand billing method based on the parsing of multimodal fields in the vehicle networking protocol. Detailed Implementation

[0014] To provide a further understanding of the purpose, structure, features, and functions of the present invention, detailed descriptions are provided below with reference to specific embodiments.

[0015] An API-based on-demand billing system based on multimodal field parsing of vehicle networking protocols, the system includes an in-vehicle terminal layer, a cloud data access and disk storage layer, a real-time / offline computing layer, a big data storage layer, a billing rule engine layer, and an API gateway and billing execution layer; The vehicle terminal layer consists of multiple vehicle terminals and has an embedded protocol identifier injection module. The cloud data access and disk persistence layer includes a protocol parsing module, a field extraction module, a metadata generation module, a data quality verification module, and a data persistence module. The real-time / offline computing layer includes a real-time stream computing engine and a virtual field computing module; The big data storage layer includes a real-time data area, an offline data area, and a billing field metadata index table. The real-time data area and the offline data area contain corresponding vehicle data records. The billing field metadata index table stores the vehicle unique identifier (VIN), query fields, and timestamp. The billing field metadata index table is associated one-to-one with vehicle data records in the real-time data area and the offline data area through the vehicle unique identifier (VIN), query fields, and timestamp. The billing rule engine layer includes a field billing configuration table, a payment mode configuration table, a tiered discount configuration table, and a multimodal billing rule matching module; The field billing configuration table predefines the protocol field names, billing categories, and base unit prices within the vehicle network communication protocol; the billing categories include high-value, medium-value, low-value, and no-billing categories; wherein, each protocol field name corresponds to a unique billing category, and each billing category corresponds to a unique base unit price; The payment mode configuration table stores the unique identifiers and configuration records of each external caller. The configuration records include payment methods and quota information. The payment methods include five modes: prepayment, postpayment, monthly subscription, per-use subscription, and tiered pricing. The quota information includes available account balance, remaining query counts, allowed query fields for the package, package validity period, and cumulative usage. The tiered discount configuration table stores the tiered range of query quantity and the discount coefficient, with each tiered range of query quantity corresponding to a unique tiered discount coefficient; The API gateway and billing execution layer include an input parameter parsing module, a multimodal field parsing engine, a data retrieval and effective data volume statistics module, a cost calculation module, a payment mode execution module, and a response return and cost detail injection module.

[0016] Please refer to the reference. Figure 1 This invention also proposes an API on-demand billing method based on multimodal field parsing of vehicle networking protocols, including the following steps: S1: Generate vehicle data records; S11: Vehicle terminal data acquisition and protocol identifier injection; The vehicle terminal layer collects vehicle operation data and the vehicle's unique identifier (VIN), synchronously generates a collection timestamp, injects the identifier, and reports it periodically. The vehicle terminal layer consists of multiple vehicle terminals. Each vehicle terminal has an embedded protocol identifier injection module, which adds a protocol type identifier to the vehicle operation data. According to the pre-agreed communication protocol, the vehicle terminal encapsulates the vehicle operation data, the vehicle unique identifier (VIN), and the collection timestamp to obtain data packets and periodically reports them to the cloud data access and disk layer. S12: Data parsing, verification, and vehicle data record generation; The cloud data access and disk layer receives data packets reported by the vehicle terminal. The protocol parsing module matches the corresponding protocol specification based on the protocol type identifier in the data packet, and splits the data packet based on the protocol specification to extract vehicle operation data. The field extraction module extracts the corresponding business fields from the vehicle operation data and constructs business key-value pairs. The business fields include vehicle speed, mileage, engine speed, etc.; business key-value pairs are constructed using the field name of the business field as the key and the corresponding value as the value. The metadata generation module generates a metadata record for each business field. The metadata record includes the collection timestamp, the field name of the business field, and the vehicle unique identifier (VIN). The data quality verification module performs timeliness and numerical compliance checks on business key-value pairs. If the verification passes, a normal data status flag is generated; if the verification fails, an abnormal status flag is generated and the data quality flag is added to the corresponding metadata record. The data storage module merges business key-value pairs and metadata records into the big data storage layer to generate vehicle data records; Furthermore, the real-time / offline computing layer includes a real-time stream computing engine and a virtual field computing module. The real-time stream computing engine performs data aggregation and statistical analysis on vehicle data records in the big data storage layer to extract vehicle operating characteristics and mine driving status and safety risk information. Based on the aggregation and analysis results, the virtual field computing module generates virtual fields such as driving behavior scores and thermal runaway risk indices, and writes the virtual fields into the real-time data area of ​​the big data storage layer to enrich the queryable data content. S2: Parse request parameters and identify query modality; The API gateway and billing execution layer receive vehicle network data query requests initiated by external callers through the system's external API gateway entry point; The input parameter parsing module parses the request message carried in the vehicle network data query request and extracts the request parameters; the request parameters include the vehicle unique identifier (VIN), query fields, etc.; the query fields are the set of vehicle data field names to be queried specified by the external caller in the request. The multimodal field parsing engine parses the request parameters and identifies the query modality based on the query fields and the vehicle unique identifier (VIN). When the query fields contain only one field, it is determined to be a single-field query modality; When the query fields contain two or more fields, it is determined to be a multi-field combination query mode; When there are multiple Vehicle Identifiers (VINs), it is determined to be a batch single-field set query mode.

[0017] The multimodal field parsing engine encapsulates the identified query modality, vehicle unique identifier (VIN), and query fields into billing tuples, and then transmits the billing tuples to the billing rule engine layer.

[0018] S3: Obtain multi-dimensional billing parameters; S31: Obtain the billing category and base unit price corresponding to the protocol field name; The multimodal billing rule matching module of the billing rule engine layer receives the billing tuple and performs consistency matching between the query field fields in the billing tuple and the protocol field name in the field billing configuration table. If the match is successful, the billing category and base unit price corresponding to the protocol field name are obtained, and the process proceeds to step S32. If the match fails, it is determined to be an illegal query field, the current billing process is terminated, and an invalid field query prompt is returned to the caller. S32: Obtain the corresponding payment method and amount information; The multimodal billing rule matching module matches the unique identifier of the external caller corresponding to this vehicle network data query request with the unique identifier of the external caller stored in the payment mode configuration table. If the match is successful, the module obtains the configuration record with the same identifier and extracts the corresponding payment method and amount information from the configuration record. If the match fails, the module determines that the caller's identity is abnormal, terminates the current billing process, and returns an invalid identity verification message. S33: Obtain the corresponding tiered discount coefficient; The multimodal billing rule matching module extracts the number of Vehicle Unique Identifiers (VINs) from the billing tuple and compares them one by one with the query quantity tier intervals in the tiered discount configuration table. It matches the query quantity tier interval to which the current number of VINs belongs. If the match is successful, it obtains the tiered discount coefficient corresponding to the query quantity tier interval; if the match fails, it executes billing according to the default discount coefficient.

[0019] S4: Data retrieval and statistics of effective data volume; The data retrieval and effective data volume statistics module initiates a data retrieval to the big data storage layer based on the vehicle unique identifier (VIN) and query fields in the billing tuple; using the vehicle unique identifier (VIN) and query fields as search conditions, it retrieves matching vehicle data records from the associated real-time data area or offline data area; the vehicle data record includes the vehicle unique identifier (VIN), protocol field name, and field value; the protocol field name is the vehicle data name, and the field value is the corresponding data content; The data retrieval and valid data volume statistics module determines the validity of the acquired vehicle data records. If the vehicle unique identifier (VIN) exists legally, the field value is not empty, and the field value is within the preset valid range, it is determined to be valid data; otherwise, it is determined to be invalid data. The system counts the number of valid data entries corresponding to each protocol field name in this query, and transmits the valid data and the number of valid data entries for each protocol field to the cost calculation module.

[0020] S5: Generate the cost per query for this query; The cost calculation module obtains the query modality of the billing tuple. If the current vehicle network data query request meets two or more query modalities at the same time, the final billing will be determined according to the pre-configured charging rules in the management backend, whether it is a single-field query modality, a multi-field combination query modality, or a batch single-field set query modality. The cost calculation module calculates the cost per query based on the final determined query modality, the corresponding base unit price, the number of valid data entries in each protocol field, and the tiered discount coefficient. The cost per transaction is the sum of the product of the base unit price of each protocol field and the number of valid data entries in each protocol field, multiplied by the tiered discount factor.

[0021] S6: Cost execution and result return; The payment mode execution module deducts fees, reduces the amount, or records bills based on the payment method and amount information obtained in step S32 for the single fee obtained in step S5. The response return and fee details injection module returns valid data to the external caller and injects information such as the fee details and remaining credit limit of this query into the response result.

[0022] This method natively supports five payment models: prepayment, postpayment, monthly subscription, per-use subscription, and tiered payment. It also enables hot loading and dynamic switching of rules through a payment model configuration table. This allows for quick adaptation to the business cooperation and settlement requirements of different customers without modifying the code or restarting the service. It replaces the traditional manual offline reconciliation method, significantly reducing business connection costs, improving settlement efficiency, and reducing accounting disputes.

[0023] This method performs a validity check on the data before billing, and only bills valid data with valid VINs, non-empty field values ​​and within the valid range. It automatically removes invalid data such as missing data, delayed reporting, and abnormal values, so as to avoid users paying for empty or bad data. While protecting the rights of the caller, it also incentivizes the data provider to improve data quality.

[0024] The present invention has been described in the above-described embodiments; however, these embodiments are merely examples for implementing the present invention. It must be noted that the disclosed embodiments do not limit the scope of the present invention. Conversely, any modifications and refinements made without departing from the spirit and scope of the present invention are within the scope of patent protection of the present invention.

Claims

1. An API on-demand billing method based on multimodal field parsing of vehicle networking protocols, characterized in that: Includes the following steps: S1: Generate vehicle data records; S11: Vehicle terminal data acquisition and protocol identifier injection; S12: Data parsing, verification, and vehicle data record generation; S2: Parse request parameters and identify query modality; The API gateway and billing execution layer receive vehicle network data query requests initiated by external callers through the system's external API gateway entry point; Extract request parameters, parse the request parameters, and identify the query modality; S3: Obtain multi-dimensional billing parameters; S31: Obtain the billing category and base unit price corresponding to the protocol field name; S32: Obtain the corresponding payment method and amount information; S33: Obtain the corresponding tiered discount coefficient; S4: Data retrieval and statistics of effective data volume; The data retrieval and effective data volume statistics module initiates a data retrieval to the big data storage layer to obtain matching vehicle data records from the relevant real-time data area or offline data area; Count the number of valid data entries corresponding to each protocol field name in this query, and transmit the valid data and the number of valid data entries for each protocol field to the cost calculation module; S5: Generate the cost per query for this query; The cost calculation module calculates the cost per query based on the final determined query modality, the corresponding base unit price, the number of valid data entries in each protocol field, and the tiered discount coefficient. S6: Cost execution and result return; The payment mode execution module deducts fees, reduces the amount, or records bills based on the payment method and amount information obtained in step S32 for the single fee obtained in step S5. The response return and cost details injection module returns valid data to the external caller.

2. The API on-demand billing method based on multimodal field parsing of the vehicle networking protocol as described in claim 1, characterized in that: The specific details of step S1 are as follows: S11: Vehicle terminal data acquisition and protocol identifier injection; The vehicle terminal layer collects vehicle operation data and the vehicle's unique identifier (VIN), synchronously generates a collection timestamp, injects the identifier, and reports it periodically. The vehicle terminal layer consists of multiple vehicle terminals. Each vehicle terminal has an embedded protocol identifier injection module, which adds a protocol type identifier to the vehicle operation data. According to the pre-agreed communication protocol, the vehicle terminal encapsulates the vehicle operation data, the vehicle unique identifier (VIN), and the collection timestamp to obtain data packets and periodically reports them to the cloud data access and disk layer. S12: Data parsing, verification, and vehicle data record generation; The cloud data access and disk layer receives data packets reported by the vehicle terminal. The protocol parsing module matches the corresponding protocol specification based on the protocol type identifier in the data packet, and splits the data packet based on the protocol specification to extract vehicle operation data. The field extraction module extracts the corresponding business fields from the vehicle operation data and constructs business key-value pairs; it constructs business key-value pairs using the field name of the business field as the key and the corresponding value as the value. The metadata generation module generates a metadata record for each business field. The metadata record includes the collection timestamp, the field name of the business field, and the vehicle unique identifier (VIN). The data quality verification module verifies the business key-value pairs. If the verification passes, it generates a normal data status flag. If the verification fails, an abnormal status flag is generated and a data quality flag is added to the corresponding metadata record; The data storage module merges business key-value pairs and metadata records into the big data storage layer to generate vehicle data records.

3. The API on-demand billing method based on multimodal field parsing of the vehicle networking protocol as described in claim 1, characterized in that: In step S2, the API gateway and the billing execution layer receive vehicle network data query requests initiated by external callers through the system's external API gateway entry point; The input parameter parsing module parses the request message carried in the vehicle network data query request and extracts the request parameters; the request parameters include the vehicle unique identifier (VIN) and the query fields. The query fields are a set of vehicle data field names to be queried, specified by the external caller in the request. The multimodal field parsing engine parses the request parameters and identifies the query modality based on the query fields and the vehicle unique identifier (VIN). When the query fields contain only one field, it is determined to be a single-field query modality; When the query fields contain two or more fields, it is determined to be a multi-field combination query mode; When there are multiple Vehicle Identifiers (VINs), it is determined to be a batch single-field set query mode.

4. The multimodal field parsing engine encapsulates the identified query modality, vehicle unique identifier (VIN), and query fields into billing tuples, and then transmits the billing tuples to the billing rule engine layer. The API on-demand billing method based on multimodal field parsing of the vehicle networking protocol as described in claim 1 is characterized in that: The specific details of step S3 are as follows: S31: Obtain the billing category and base unit price corresponding to the protocol field name; The multimodal billing rule matching module of the billing rule engine layer receives the billing tuple and performs consistency matching between the query field fields in the billing tuple and the protocol field name in the field billing configuration table. If the match is successful, the billing category and base unit price corresponding to the protocol field name are obtained, and the process proceeds to step S32. If the match fails, it is determined to be an illegal query field, the current billing process is terminated, and an invalid field query prompt is returned to the caller. S32: Obtain the corresponding payment method and amount information; The multimodal billing rule matching module matches the unique identifier of the external caller corresponding to this vehicle network data query request with the unique identifier of the external caller stored in the payment mode configuration table. If the match is successful, the module obtains the configuration record with the same identifier and extracts the corresponding payment method and amount information from the configuration record. If the match fails, the caller's identity is determined to be abnormal, the current billing process is terminated, and an invalid identity verification message is returned. S33: Obtain the corresponding tiered discount coefficient; The multimodal billing rule matching module extracts the number of Vehicle Unique Identifiers (VINs) from the billing tuple and compares them one by one with the query quantity tier intervals in the tiered discount configuration table. It matches the query quantity tier interval to which the current number of VINs belongs. If the match is successful, it obtains the tiered discount coefficient corresponding to the query quantity tier interval; if the match fails, it executes billing according to the default discount coefficient.

5. The API on-demand billing method based on multimodal field parsing of the vehicle networking protocol as described in claim 1, characterized in that: The specific details of step S4 are as follows: The data retrieval and effective data volume statistics module initiates a data retrieval to the big data storage layer based on the vehicle unique identifier (VIN) and query fields in the billing tuple; using the vehicle unique identifier (VIN) and query fields as search conditions, it retrieves matching vehicle data records from the associated real-time data area or offline data area; the vehicle data record includes the vehicle unique identifier (VIN), protocol field name, and field value; the protocol field name is the vehicle data name, and the field value is the corresponding data content; The data retrieval and valid data volume statistics module determines the validity of the acquired vehicle data records. If the vehicle unique identifier (VIN) exists legally, the field value is not empty, and the field value is within the preset valid range, it is determined to be valid data; otherwise, it is determined to be invalid data. The system counts the number of valid data entries corresponding to each protocol field name in this query, and transmits the valid data and the number of valid data entries for each protocol field to the cost calculation module.

6. The API on-demand billing method based on multimodal field parsing of the vehicle networking protocol as described in claim 1, characterized in that: The specific details of step S5 are as follows: The cost calculation module obtains the query modality of the billing tuple. If the current vehicle network data query request meets two or more query modalities at the same time, the final billing will be determined according to the pre-configured charging rules in the management backend, whether it is a single-field query modality, a multi-field combination query modality, or a batch single-field set query modality. The cost calculation module calculates the cost per query based on the final determined query modality, the corresponding base unit price, the number of valid data entries in each protocol field, and the tiered discount coefficient. The cost per transaction is the sum of the product of the base unit price of each protocol field and the number of valid data entries in each protocol field, multiplied by the tiered discount factor.

7. An API on-demand billing system based on multimodal field parsing of vehicle networking protocols for implementing the method of any one of claims 1-6, characterized in that: It includes the vehicle terminal layer, cloud data access and disk storage layer, real-time / offline computing layer, big data storage layer, billing rule engine layer, API gateway and billing execution layer; The vehicle terminal layer consists of multiple vehicle terminals and has an embedded protocol identifier injection module. The cloud data access and disk persistence layer includes a protocol parsing module, a field extraction module, a metadata generation module, a data quality verification module, and a data persistence module. The real-time / offline computing layer includes a real-time stream computing engine and a virtual field computing module; The big data storage layer includes a real-time data area, an offline data area, and a billing field metadata index table. The real-time data area and the offline data area contain corresponding vehicle data records. The billing rule engine layer includes a field billing configuration table, a payment mode configuration table, a tiered discount configuration table, and a multimodal billing rule matching module; The API gateway and billing execution layer include an input parameter parsing module, a multimodal field parsing engine, a data retrieval and effective data volume statistics module, a cost calculation module, a payment mode execution module, and a response return and cost detail injection module.

Images