CN110609945A - Method, device and system for inquiring second-hand car service data - Google Patents

Abstract

The embodiment of the application shows a method, a device and a system for inquiring second-hand car service data, wherein the method comprises the following steps: acquiring a service request, wherein the service request comprises a query condition and service data; converting the service data into an array set; and traversing the array set based on the query condition to generate a query result. The method disclosed by the embodiment of the application acquires the service request in advance in the query process, the service data comprise data tables related to query, the data tables are converted into array sets in a key-value form, finally, the array sets are traversed based on the query conditions, and query results are generated.

Description

Method, device and system for inquiring second-hand car service data

Technical Field

The invention relates to the technical field of computers, in particular to a method, a device and a system for inquiring second-hand car service data.

Background

In recent years, the rapid development of Chinese economy, the rapid growth of vehicle reserves, more and more prosperity of trading and buying of the used-hand vehicles, and the use-hand vehicle service platform is generated along with the gradual prosperity of trading and buying of the used-hand vehicles. Generally, a second-hand vehicle service platform acquires vehicle source information through a plurality of channels, stores the vehicle source information in a database, and queries and/or counts the vehicle source information in the database according to different service requirements.

Generally, in the process of inquiring and/or counting vehicle source information in a database by a second-hand vehicle service platform, the acquired vehicle source information is clustered according to a certain dimension in advance; and then storing the clustered vehicle source information in corresponding data tables respectively. For example, the vehicle source data is clustered and stored according to two dimensions of color and manufacturer in advance, and a color list and a manufacturer list are obtained respectively. When the second-hand vehicle service platform needs to count the number of red and Audi vehicles, the second-hand vehicle service platform firstly traverses the color list to screen out red vehicles, then traverses the manufacturer list to screen out the Audi vehicles, finally establishes a connection between the color list and the manufacturer list, and finally counts the number of the red and Audi vehicles.

Therefore, in the service platform for the second-hand car shown in the prior art, in the process of searching service data, a related data list needs to be traversed, then, a connection is established between the data list, and finally, a search result is generated. In the list traversal process, the second-hand vehicle service platform is in a waiting state for a long time, so that the utilization rate of resources such as system bandwidth and a database is reduced.

Disclosure of Invention

The invention aims to provide a method, a device and a system for inquiring used car service data, so as to solve the technical problem that the used car service platform shown in the prior art is in a waiting state for a long time in the data inquiring process, and the utilization rate of resources such as system bandwidth and a database is reduced.

A first aspect of an embodiment of the present application shows a method for querying used vehicle service data, where the method includes:

acquiring a service request, wherein the service request comprises a query condition and service data;

converting the service data into an array set;

and traversing the array set based on the query condition to generate a query result.

Optionally, the step of converting the service data into an array set includes:

determining the type of the service data, wherein the service data comprises: HTTP service traffic data, and, GRPC service traffic data;

if the service data is HTTP service data, converting the HTTP service data parameterization setting into a request entity;

judging whether the request entity meets a preset verification rule;

if yes, determining the request entity as an array set;

and if not, sending an error report to the service end.

Optionally, the step of traversing the array set based on the query condition to generate the query result includes:

converting the query condition into an es query statement, wherein the es query statement is a query statement supported by an es search engine;

and traversing the array set based on the es query statement to generate a query result.

Optionally, the step of converting the query condition into an es query statement includes:

cutting the query condition to obtain a cut field;

judging whether the cut field is a preset query field;

if the preset query field is met, converting the cutting query condition into an es query statement;

and if the preset query field is not satisfied, directly deleting the cut field.

Optionally, the error report records the error type of each record in the requesting entity and is marked with a highlighted font.

A second aspect of the embodiment of the present application shows an apparatus for querying used vehicle service data, where the apparatus includes:

an obtaining unit, configured to obtain a service request, where the service request includes a query condition and service data;

the conversion unit is used for converting the service data into an array set;

and the generating unit is used for traversing the array set based on the query condition to generate a query result.

Optionally, the conversion unit comprises:

a determining unit, configured to determine a type of the service data, where the service data includes: HTTP service traffic data, and, GRPC service traffic data;

the parameterization setting unit is used for converting the parameterization setting of the HTTP service business data into a request entity if the business data is HTTP service business data;

the judging unit is used for judging whether the requesting entity meets the preset verification rule or not;

a first determining unit, configured to determine that the requesting entity is an array set if the request is satisfied;

and the sending unit is used for sending the error report to the service end if the error report does not meet the requirement.

Optionally, the generating unit includes:

the conversion unit is used for converting the query condition into an es query statement, and the es query statement is a query statement supported by an es search engine;

and the first generation unit is used for traversing the array set based on the es query statement to generate a query result.

Optionally, the conversion unit includes:

the cutting unit is used for cutting the query condition to obtain a cut field;

the first judging unit is used for judging whether the cut field is a preset query field;

the first conversion unit is used for converting the cutting query condition into an es query statement if a preset query field is met;

and the deleting unit is used for directly deleting the cut fields if the preset query fields are not satisfied.

A third aspect of the embodiment of the present application shows a system for querying used vehicle service data, where the system includes:

the system comprises an application platform server and a data storage server connected with the application platform server, wherein the data storage server is arranged inside the application platform server or independently arranged, and the application platform server is connected with a service end through the Internet;

the service end is used for sending a service request;

the application platform server is used for realizing the method shown in the embodiment of the application;

and the data storage server is used for storing related data.

According to the technical scheme, the embodiment of the application shows a method, a device and a system for inquiring second-hand vehicle service data, wherein the method comprises the following steps: acquiring a service request, wherein the service request comprises a query condition and service data; converting the service data into an array set; and traversing the array set based on the query condition to generate a query result. The method disclosed by the embodiment of the application acquires the service request in advance in the query process, the service data comprise data tables related to query, the data tables are converted into array sets in a key-value form, finally, the array sets are traversed based on the query conditions, and query results are generated.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.

Fig. 1-1 is a block diagram illustrating a query system for used vehicle service data according to a preferred embodiment;

fig. 1-2 are block diagrams illustrating a query system for used vehicle service data according to another preferred embodiment;

fig. 2 is a flowchart illustrating a method for querying used vehicle service data according to a preferred embodiment;

FIG. 3 is a detailed flowchart of step S102, shown in accordance with a preferred embodiment;

FIG. 4 is a detailed flowchart of step S103, shown in accordance with a preferred embodiment;

FIG. 5 is a detailed flowchart of step S1031 shown in accordance with a preferred embodiment;

fig. 6 is a block diagram illustrating a structure of a used vehicle service data query device according to a preferred embodiment;

FIG. 7 is a block diagram illustrating the structure of a translation unit in accordance with a preferred embodiment;

FIG. 8 is a block diagram of a generation unit shown in accordance with a preferred embodiment;

FIG. 9 is a block diagram illustrating the structure of a conversion unit in accordance with a preferred embodiment;

fig. 10 is a block diagram illustrating a configuration of a server according to a preferred embodiment.

Detailed Description

The technical solutions in the embodiments of the present invention will be described clearly and completely with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Example 1:

the embodiment of the present application shows a second-hand vehicle service data query system, please refer to fig. 1-1 and fig. 1-2, the system includes:

the system comprises an application platform server 31 and a data storage server 32 connected with the application platform server 31, wherein the data storage server 32 is arranged inside the application platform server 31 or independently arranged, and the application platform server 31 is connected with a service terminal 33 through the Internet;

the service end 33 is configured to send a service request;

the service data comprises: HTTP service traffic data, and, GRPC service traffic data;

the HTTP service business data are general business data in the industry, and for some businesses with low data throughput, the existing HTTP service business data are directly adopted. For some data with larger data throughput, the HTTP service data is stored in JSON format data, and occupies more memory, so that the HTTP service data is stored in a binary mode, the occupancy rate of the system memory is reduced, and the real-time performance of the system is improved.

The application platform server 31 is configured to implement the method shown in the embodiment of the present application;

the method comprises the steps of (1) obtaining a service request, wherein the service request comprises a query condition and service data;

the service data comprises: HTTP service traffic data, and, GRPC service traffic data; wherein, the data in the HTTP service business data is generally stored in a JSON structure; for example:

color table:

JSON data table first layer: color;

a second layer: VIN code: 1, color: red; VIN code: 2, color: red; VIN code: 3, color: blue; VIN code: 4, color: yellow; VIN code: 5, color: violet.

The manufacturer table:

JSON data table first layer: a manufacturer;

a second layer: VIN code: 1, manufacturer: audi; VIN code: 2, manufacturer: audi; VIN code: 4, manufacturer: speed is galloping; VIN code: 5, manufacturer: audi; VIN code: 9, manufacturer: another.

In the prior art, a service party counts the number of red and Audi vehicles, firstly traverses a color table, and finally establishes a relation between tables after traversing a manufacturer table, a VIN code of the vehicle is a unique identification for determining the vehicle, and finally counts the number of the red Audi vehicles by establishing the relation between the two tables through the VIN code.

(2) Converting the service data into an array set;

converting the service data into data to combine:

VIN code

1

2

3

4

5

6

7

8

9

Colour(s)

Red wine

Red wine

Blue (B)

Yellow colour

Purple pigment

～

～

～

～

Manufacturer of the product

Audi (Audi)

Audi (Audi)

～

Benz Chi

Audi (Audi)

～

～

～

Buick

(3) Traversing the array set based on the query condition to generate a query result:

generating a query result based on the array combination: the number of red audi cars is: 2;

and finally, returning the query result to the service party.

And the data storage server is used for storing related data.

The system shown in the embodiment of the application is used for pre-acquiring a service request in a query process by using a platform server, wherein the service data comprises data tables related to query, then converting the data tables into an array set in a key-value form, and finally traversing the array set based on the query condition to generate a query result.

Example 2:

a second aspect of the embodiment of the present application shows a method for querying used vehicle service data, please refer to fig. 2, where the method includes:

s101, acquiring a service request, wherein the service request comprises a query condition and service data;

the service data comprises: HTTP service traffic data, and, GRPC service traffic data; wherein, the data in the HTTP service business data is generally stored in a JSON structure; for example:

color table:

JSON data table first layer: color;

a second layer: VIN code: 1, color: red; VIN code: 2, color: red; VIN code: 3, color: blue; VIN code: 4, color: yellow; VIN code: 5, color: violet.

The manufacturer table:

JSON data table first layer: a manufacturer;

a second layer: VIN code: 1, manufacturer: audi; VIN code: 2, manufacturer: audi; VIN code: 4, manufacturer: speed is galloping; VIN code: 5, manufacturer: audi; VIN code: 9, manufacturer: another.

In the prior art, a service party counts the number of red and Audi vehicles, firstly traverses a color table, and finally establishes a relation between tables after traversing a manufacturer table, a VIN code of the vehicle is a unique identification for determining the vehicle, and finally counts the number of the red Audi vehicles by establishing the relation between the two tables through the VIN code.

S102, converting the service data into an array set;

converting the service data into data to combine:

VIN code

1

2

3

4

5

6

7

8

9

Colour(s)

Red wine

Red wine

Blue (B)

Yellow colour

Purple pigment

～

～

～

～

Manufacturer of the product

Audi (Audi)

Audi (Audi)

～

Benz Chi

Audi (Audi)

～

～

～

Buick

S103, traversing the array set based on the query condition to generate a query result.

The method disclosed by the embodiment of the application acquires the service request in advance in the query process, the service data comprise data tables related to query, the data tables are converted into array sets in a key-value form, finally, the array sets are traversed based on the query conditions, and query results are generated.

Example 3:

in order to avoid that erroneous service data transmitted by a service end occupies too many resources of an application platform server, an embodiment of the present application shows a method for verifying service data, and specifically, please refer to fig. 3;

embodiment 3 has similar steps with embodiment 2, and the only difference is that embodiment 2 shows that step S102 in the technical solution includes the following steps:

s1021, determining a type of the service data, where the service data includes: HTTP service traffic data, and, GRPC service traffic data;

data in the HTTP service traffic data is typically stored in a JSON structure; the data source of the technical party shown in the embodiment of the application is mainly HTTP service data, and the HPPT service data is a data source commonly used by the service party;

however, for some services with high data throughput, GRPC service is usually configured, and GRPC service data is stored in a binary manner.

S1022, if the service data is HTTP service data, the HTTP service data parameterization setting is converted into a request entity;

for example:

color table:

JSON data table first layer: color;

a second layer: VIN code: 1, color: red; VIN code: 2, color: red; VIN code: 3, color: blue; VIN code: 4, color: yellow; VIN code: 5, color: violet.

The manufacturer table:

JSON data table first layer: a manufacturer;

a second layer: VIN code: 1, manufacturer: audi; VIN code: 2, manufacturer: audi; VIN code: 4, manufacturer: speed is galloping; VIN code: 5, manufacturer: audi; VIN code: 9, manufacturer: another.

In the prior art, a service party counts the number of red and Audi vehicles, firstly traverses a color table, and finally establishes a relation between tables after traversing a manufacturer table, a VIN code of the vehicle is a unique identification for determining the vehicle, and finally counts the number of the red Audi vehicles by establishing the relation between the two tables through the VIN code.

Converting the service data into a request entity:

VIN code

1

2

3

4

5

6

7

8

9

Colour(s)

Red wine

Red wine

Blue (B)

Yellow colour

Purple pigment

～

～

～

～

Manufacturer of the product

Audi (Audi)

Audi (Audi)

～

Benz Chi

Audi (Audi)

～

～

～

Buick

S1023 judges whether the request entity meets the preset verification rule;

the method shown in the embodiment of the application judges whether the request entity meets the preset verification rule in the following ways:

judging whether the data type of the request entity meets a preset verification rule:

for example, for a vehicle delivery date, the validation rule is preset, the format of data corresponding to the delivery date is specified as characters, and if the type of data returned by the service end is the type of date, the data type of the request entity is determined to be not in accordance with the preset validation rule;

for another example, the preset validation rule specifies that each piece of service data corresponds to a service index, and the service index is used for guiding the application platform server to return the final query result to the corresponding service end;

the application platform server firstly judges whether the service index exists in the request entity or the GRPC service data, if the service index does not exist, the request entity or the GRPC service data is determined not to conform to the preset verification rule.

For another example, the reg delivered by the service end must carry a parameter, and if the reg delivered by the service end does not carry the parameter, the service data of the requesting entity or the GRPC service is determined not to conform to the preset validation rule.

If yes, S1024 determines that the requesting entity is an array set;

the embodiment of the application only describes preset verification rules exemplarily, and in practical application, all the rules which can judge that the business data ratio can be identified by the application platform server are within the protection range of the method disclosed by the embodiment of the application, and the rules are not necessarily described due to limited space;

if not, S1025 sends an error report to the service end.

Optionally, the error report records the error type of each record in the requesting entity and is marked with a highlighted font.

In order to facilitate the service end to quickly find out the location of the error of the sent service request, the method shown in the embodiment of the present application records the error type of each record in the requesting entity or HTTP service data in the error report, and marks the error type with a font with a highlight color.

For example: the reg parameter is null and the corresponding error report is "error parameter, error: must have parameters, reg cannot be empty "

For another example: a service index is absent in a certain request entity or HTTP service data, and a corresponding error report is "error type indexName: the index name cannot be null.

Through the error report shown in the embodiment of the application, the service end can quickly locate the error of the sent service request, timely modify the service request and send the modified service request to the application platform server. And the application platform server processes the service request again.

According to the method disclosed by the embodiment of the application, the error type of each piece of data is calculated through the detailed table, so that the error searching time of the service end is shortened, the waiting time of the application platform server is further shortened, and the bandwidth of the system and the utilization rate of resources are improved.

The method shown in the embodiment of the application firstly verifies whether the GRPC service data or the request entity meets the preset verification rule, and then directly returns the service end if the GRPC service data or the request entity does not meet the preset verification rule, so that the problem that some service data which do not meet the preset verification rule occupy the resources of the application platform server is avoided, and the bandwidth of the system and the utilization rate of the resources are further improved.

Example 4:

in order to further improve the efficiency of querying data of the method shown in the embodiment of the present application, the embodiment of the present application shows an ElasticSearch method. Specifically, please refer to fig. 4;

embodiment 4 has similar steps with the technical solution shown in embodiment 2, and the only difference is that step S103 in the technical solution shown in embodiment 2 includes the following steps:

s1031 converts the query conditions into es query statements, wherein the es query statements are query statements supported by an es search engine;

the process of converting the query condition into an es query statement is as follows: the query conditions shown in the prior art are sql queries:

the retrieval mode provided by the client is complex and difficult to understand, the query conditions required for developing different service scenes are variable, and the process of realizing query by different development languages is very difficult;

the method shown in the embodiment of the application directly converts the complex SQL query condition into the specific conversion result of the es query statement as follows:

1. converts the normal majority group of precision requests into a must search,

example (c): the accurate query type according to type 1ortype 2 is converted into:

query.Must(elastic.NewTermsQuery("type",GetFloat64ToInterfaceArray(param.Type)...))

2. verifying the multi-keyword retrieval request and converting the multi-keyword retrieval request into a should search;

example (c): searching in multiple intervals according to saletime selling time;

ery.Should(elastic.NewTermsQuery("saleTime",GetFloat64ToInterfaceArray(param.Sal eTimeLowerArray)...),elastic.NewTermsQuery("saleTime",GetFloat64ToInterfaceArray(param.SaleTimeHighArray)...))

3. converting the common like search into wildcard search, and converting the word segmentation search into match search;

example (c): fuzzy match like "% abc%" according to vin "

4. The orderby is converted into the sorter,

example (c): arranging according to the sorting names in a positive sequence or a negative sequence;

5. converting the single-condition non-functional grouping into termsAggregation;

grouping only by a certain condition

newagg＝elastic.NewTermsAggregation().Field(param.AggregationData[0]).Size(int(para m.PageSize))；

6. Converting the multi-condition non-functional grouping into multi-subAggregation;

such as: grouping according to multiple keywords;

7. converting the multi-condition functional group into corresponding avg, max, count, min and sum to search and realize the paging display of the grouped data;

and converting the single condition function type grouping into corresponding avg, max, count, min and sum search to realize the paging display of the grouping data:

s1032 traverses the array set based on the es query statement, and generates a query result.

The method disclosed by the embodiment of the application can solve the problems that the retrieval mode provided by the client is complex and difficult to understand, the query conditions required for developing different service scenes are variable, the query process is very difficult to realize by different development languages, the number of required connections is too large and the like by designing the es query statement.

Example 5:

embodiment 5 has similar steps with embodiment 4, and the only difference is that the step S1031 of the technical solution shown in embodiment 4 includes the following steps:

specifically, please refer to fig. 5:

s10311, cutting the query condition to obtain a cut field;

for the query conditions: chinese BMW automobile;

firstly, cutting query conditions into the following parts: china, bmw, car;

generally, the method shown in the embodiment of the application adopts noun cutting; in practical application, the cutting can also be carried out in a guest moving mode;

for example: the query conditions are as follows: the number of vehicles whose roof is updated;

the fields after cutting are: roof update, number, vehicles;

s10312, judging whether the cut field is a preset query field;

the fields after cutting are: roof update, number, vehicles;

generally, a data storage server in an application platform server stores query data in advance, where the query data includes: the vocabulary, phrases, and, fields of the query;

then, the cut fields and the cut fields collide with query data, and if the collision is successful, whether the cut fields are preset query fields is proved;

the fields after cutting are: roof update, number, and collision results for the vehicle are:

the effective collisions are: updating the car roof and quantity;

where the vehicle is unable to make an effective collision, it is not queried based on "vehicle.

If the preset query field is met, S10313 converts the cutting query condition into an es query statement;

and if the preset query field is not satisfied, directly deleting the cut field in S10314.

Optionally, the error report records the error type of each record in the requesting entity and is marked with a highlighted font.

The method shown in the embodiment of the application cuts the query conditions in advance, and filters some useless query information, so that on one hand, the accurate query is ensured, on the other hand, the data processing amount of the application platform server in the query process is reduced, the system bandwidth is improved, and the resource utilization rate is increased. The efficiency of inquiry is improved.

Example 6:

referring to fig. 6, a third aspect of the embodiments of the present application illustrates an apparatus for querying used vehicle service data, where the apparatus includes:

an obtaining unit 21, configured to obtain a service request, where the service request includes a query condition and service data;

a conversion unit 22, configured to convert the service data into an array set;

and the generating unit 23 is configured to traverse the array set based on the query condition to generate a query result.

Example 7:

referring to fig. 7, an embodiment shows that in the technical solution, the conversion unit 22 includes:

a determining unit 221, configured to determine a type of the service data, where the service data includes: HTTP service traffic data, and, GRPC service traffic data;

a parameterization setting unit 222, configured to, if the service data is HTTP service data, convert the parameterization setting of the HTTP service data into a request entity;

a judging unit 223, configured to judge whether the requesting entity satisfies a preset verification rule;

a first determining unit 224, configured to determine that the requesting entity is an array set if satisfied;

a sending unit 225, configured to send an error report to the service end if the error report is not satisfied.

Example 8:

referring to fig. 8, in the technical solution shown in embodiment 6, the generating unit 23 includes:

a conversion unit 231, configured to convert the query condition into an es query statement, where the es query statement is a query statement supported by an es search engine;

the first generating unit 232 is configured to traverse the array set based on the es query statement, and generate a query result.

Example 9:

referring to fig. 9, in the technical solution shown in embodiment 8, the converting unit 231 includes:

a cutting unit 2311, configured to cut the query condition to obtain a cut field;

a first judging unit 2312, configured to judge whether the cut field is a preset query field;

a first converting unit 2313, configured to convert the cutting of the query condition into an es query statement if a preset query field is satisfied;

a deleting unit 2314, configured to directly delete the cut field if the preset query field is not satisfied.

A fourth aspect of the present embodiment shows a server, referring to fig. 10, where the server includes:

one or more processors 41;

a memory 42 for storing one or more programs;

when executed by the one or more processors 41, cause the one or more processors 41 to implement the methods of the embodiments of the present application.

According to the technical scheme, the query method, the query device and the query system for the second-hand vehicle service data, which are disclosed by the embodiment of the application, are characterized in that:

GRPC (rpc channel service) - > goserver monitoring service) - > go filters illegal requests- > go analyzes requests, converts query- > connection pool request elastic search cluster- > result set encapsulation- > returns to client;

the following advantages can be achieved:

supporting business multi-language development (java, net, php, etc.), and providing a universal unified interface program meeting the specification.

And the grpc service is provided for the business party with high real-time requirement and high throughput.

The business side does not need to concern the complex query request and condition conversion of the elasticserver, and simultaneously supports the query of multi-array, multi-keyword retrieval, like, word segmentation, various functions and the like.

And a high-performance stable and reliable connection pool service is provided for a business party.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It is noted that, in specific implementations, the present application also provides a computer storage medium, where the computer storage medium may store a program, and the program may include some or all of the steps in each embodiment of the service providing method for user identity or the user registration method provided by the present application when executed. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a Random Access Memory (RAM).

Those skilled in the art will clearly understand that the techniques in the embodiments of the present application may be implemented by way of software plus a required general hardware platform. Based on such understanding, the technical solutions in the embodiments of the present application may be essentially implemented or a part contributing to the prior art may be embodied in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the embodiments or some parts of the embodiments of the present application.

The same and similar parts in the various embodiments in this specification may be referred to each other. Especially, for the embodiment of the service providing device of the user identity or the user registration device, since it is basically similar to the method embodiment, the description is simple, and the related points can be referred to the description in the method embodiment.

The above-described embodiments of the present application do not limit the scope of the present application.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims (10)

1. A method for inquiring second-hand vehicle service data is characterized by comprising the following steps:

acquiring a service request, wherein the service request comprises a query condition and service data;

converting the service data into an array set;

and traversing the array set based on the query condition to generate a query result.

2. The method of claim 1, wherein the step of converting the service data into an array set comprises:

determining the type of the service data, wherein the service data comprises: HTTP service traffic data, and, GRPC service traffic data;

if the service data is HTTP service data, converting the HTTP service data parameterization setting into a request entity;

judging whether the request entity meets a preset verification rule;

if yes, determining the request entity as an array set;

and if not, sending an error report to the service end.

3. The method of claim 1, wherein traversing the set of arrays based on the query condition to generate the query result comprises:

converting the query condition into an es query statement, wherein the es query statement is a query statement supported by an es search engine;

and traversing the array set based on the es query statement to generate a query result.

4. The method of claim 3, wherein the step of converting the query condition into an es query statement comprises:

cutting the query condition to obtain a cut field;

judging whether the cut field is a preset query field;

if the preset query field is met, converting the cutting query condition into an es query statement;

and if the preset query field is not satisfied, directly deleting the cut field.

5. The method of claim 2, wherein the error report describes the type of error for each record in the requesting entity and is marked with a highlighted font.

6. An inquiry device for second-hand vehicle service data, which is characterized in that the device comprises:

an obtaining unit, configured to obtain a service request, where the service request includes a query condition and service data;

the conversion unit is used for converting the service data into an array set;

and the generating unit is used for traversing the array set based on the query condition to generate a query result.

7. The apparatus of claim 6, wherein the conversion unit comprises:

a determining unit, configured to determine a type of the service data, where the service data includes: HTTP service traffic data, and, GRPC service traffic data;

the parameterization setting unit is used for converting the parameterization setting of the HTTP service business data into a request entity if the business data is HTTP service business data;

the judging unit is used for judging whether the requesting entity meets the preset verification rule or not;

a first determining unit, configured to determine that the requesting entity is an array set if the request is satisfied;

and the sending unit is used for sending the error report to the service end if the error report does not meet the requirement.

8. The apparatus of claim 6, wherein the generating unit comprises:

the conversion unit is used for converting the query condition into an es query statement, and the es query statement is a query statement supported by an es search engine;

and the first generation unit is used for traversing the array set based on the es query statement to generate a query result.

9. The apparatus of claim 8, wherein the conversion unit comprises:

the cutting unit is used for cutting the query condition to obtain a cut field;

the first judging unit is used for judging whether the cut field is a preset query field;

the first conversion unit is used for converting the cutting query condition into an es query statement if a preset query field is met;

and the deleting unit is used for directly deleting the cut fields if the preset query fields are not satisfied.

10. A query system for used vehicle service data, the system comprising:

the system comprises an application platform server and a data storage server connected with the application platform server, wherein the data storage server is arranged inside the application platform server or independently arranged, and the application platform server is connected with a service end through the Internet;

the service end is used for sending a service request;

the application platform server for implementing the method of any one of claims 1-5;

and the data storage server is used for storing related data.